A pin management method, communication device and communication system

Abstract

Embodiments of the present application provide a PIN management method, a communication device and a communication system. The method comprises: a PIN network function network element receiving a first request message, the first request message comprising identification information of a first terminal device; the PIN network function network element sending a first query message to a unified data management network element; the PIN network function network element receiving a first query result, the first query result indicating that the first terminal device is authorized to be used as a PIN management network element; and the PIN network function network element sending a first notification message to the first terminal device, the first notification message comprising first indication information and identification information of a PIN, the first indication information indicating that the first terminal device is used as a PIN management network element in the PIN. The scheme defines a configuration process of a PIN management network element in the PIN, helps reasonable use of the PIN, realizes reasonable management of the PIN, meets user demand, and helps improve user experience.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a PIN management method, communication device and communication system. Background Technology

[0002] The 3rd Generation Partnership Project (3GPP) proposes that 5th generation (5G) networks need to be aware of Internet of Things (IoT) devices. Users can create their own Personal IoT Networks (PINs).

[0003] How to manage a PIN remains to be solved. Summary of the Invention

[0004] This application provides a PIN management method, communication device, and communication system to achieve reasonable PIN management.

[0005] In a first aspect, embodiments of this application provide a PIN management method, which can be executed by a PIN network function element or a module (such as a chip) within the PIN network function element. Taking the execution of the method by a PIN network function element as an example, the method includes: the PIN network function element receiving a first request message, the first request message including identification information of a first terminal device, the first request message being used to request the first terminal device to act as a PIN management element; the PIN network function element sending a first query message to a unified data management element, the first query message including identification information of the first terminal device, the first query message being used to query whether the first terminal device is authorized to act as a PIN management element; the PIN network function element receiving a first query result from the unified data management element, the first query result indicating that the first terminal device is authorized to act as a PIN management element; the PIN network function element sending a first notification message to the first terminal device, the first notification message including first indication information and PIN identification information, the first indication information indicating that the first terminal device is acting as a PIN management element within the PIN.

[0006] The above scheme defines the configuration process of the PIN management network element within the PIN. This PIN management network element can act as the administrator within the PIN to manage the devices within the PIN, which helps to ensure the proper use of the PIN, realizes the proper management of the PIN, meets user needs, and helps to improve the user experience.

[0007] In one possible implementation, the first request message may further include identification information of the PIN; or, the method may further include: the PIN network function element assigning the identification information of the PIN.

[0008] In one possible implementation, the PIN network function element sends the identification information of the PIN to the application function element.

[0009] In one possible implementation, the PIN network function element receiving the first request message includes: the PIN network function element receiving the first request message from the first terminal device; or, the PIN network function element receiving the first request message from an application function element.

[0010] In one possible implementation, the PIN network function element receives a second request message, which includes the identification information of a second terminal device, and is used to request the second terminal device to act as a PIN gateway element; the PIN network function element sends a second query message to the unified data management element, which includes the identification information of the second terminal device, and is used to query whether the second terminal device is authorized to act as a PIN gateway element; the PIN network function element receives a second query result from the unified data management element, which indicates that the second terminal device is authorized to act as a PIN gateway element; the PIN network function element sends a second notification message to the second terminal device, which includes second indication information, the identification information of the PIN management element, and the identification information of the PIN, wherein the second indication information indicates that the second terminal device is acting as a PIN gateway element within the PIN, and the identification information of the PIN management element is the identification information of the first terminal device.

[0011] The above scheme defines the configuration process of the PIN gateway network element within the PIN. This PIN gateway network element can act as a gateway within the PIN, enabling message relay between devices within the PIN and the network. This facilitates the rational use and management of the PIN, meets user needs, and helps improve the user experience.

[0012] In one possible implementation, the PIN network function element receiving the second request message includes: the PIN network function element receiving the second request message from the second terminal device, the application function element, or the first terminal device.

[0013] In one possible implementation, the PIN network function element receives a first update message from the second terminal device. The first update message includes the identification information of the PIN gateway element and the identification information of the PIN. The identification information of the PIN gateway element is the identification information of the second terminal device. The PIN network function element updates the PIN information to obtain first PIN information, which includes the identification information of the PIN, the identification information of the PIN management element, and the identification information of the PIN gateway.

[0014] In one possible implementation, the PIN network function element receives a second update message from the second terminal device. The second update message includes the identification information of the PIN, the identification information of the PINE, and the PINE number corresponding to the PINE. The identification information of the PINE is the identification information of the third terminal device. The PIN network function element updates the first PIN information to obtain second PIN information. The second PIN information includes the identification information of the PIN, the identification information of the PIN management element, the identification information of the PIN gateway, the identification information of the PINE, and the PINE number.

[0015] The above scheme defines the process of adding a PINE within a PIN. This PINE can communicate with other PINEs, PEMCs, or PEGCs within the PIN, which helps to ensure the proper use and management of the PIN, meets user needs, and improves the user experience.

[0016] In one possible implementation, the PIN network function element receives a third request message from a third terminal device. This third request message includes the identification information of the third terminal device, the identification information of the PIN, and a join request, whereby the join request is used to request to join the PIN. The PIN network function element sends the identification information of the third terminal device and the join request to the first terminal device via the second terminal device. The PIN network function element receives the identification information of the PINE and the PINE number corresponding to the PINE from the first terminal device via the second terminal device. The identification information of the PINE is the identification information of the third terminal device. The PIN network function element updates the first PIN information to obtain second PIN information, which includes the identification information of the PIN, the identification information of the PIN management element, the identification information of the PIN gateway, the identification information of the PINE, and the PINE number.

[0017] The above scheme defines the process of adding a PINE within a PIN. This PINE can communicate with other PINEs, PEMCs, or PEGCs within the PIN, which helps to ensure the proper use and management of the PIN, meets user needs, and improves the user experience.

[0018] In one possible implementation, the PIN network function element receives a fourth request message from the first terminal device. The fourth request message includes the identification information and management instructions of the PIN, as well as the identification information of the fourth terminal device or the PINE number corresponding to the fourth terminal device. The PIN network function element sends the management instructions to the fourth terminal device through the second terminal device.

[0019] In the above scheme, when the PIN management network element wants to manage a certain PINE within the PIN, the PIN management network element can send management commands to the PINE through the PIN network function network element and the PIN gateway network element, thus realizing remote PIN management, meeting user needs, and helping to improve user experience.

[0020] In one possible implementation, the PIN network function element receives a fifth request message from the fifth terminal device, the fifth request message including the identification information of the PIN and the identification information of the fifth terminal device; the PIN network function element sends a third query message to the unified data management element, the third query message including the identification information of the fifth terminal device, the third query message being used to query whether the fifth terminal device is authorized to be used as a PIN management element; the PIN network function element receives a third query result from the unified data management element, the third query result indicating that the fifth terminal device is authorized to be used as a PIN management element; the PIN network function element sends a third indication message and the identification information of the PIN to the fifth terminal device, the third indication message indicating that the fifth terminal device is a PIN management element within the PIN.

[0021] The above scheme defines the update process of PEMC within the PIN, realizes reasonable PIN management, meets user needs, and helps improve user experience.

[0022] In one possible implementation, the PIN network function element sends a third notification message to the first terminal device. The third notification message includes fourth indication information and identification information of the fifth terminal device. The fourth indication information indicates that the fifth terminal device is a PIN management element within the PIN.

[0023] Secondly, embodiments of this application provide a PIN management method, which can be executed by a first terminal device or a module (such as a chip) within the first terminal device. The first terminal device can also be referred to as a PIN management network element. Taking the execution of this method by the first terminal device as an example, the method includes: the first terminal device sending a first request message to a PIN network function network element, the first request message including identification information of the first terminal device, the first request message being used to request the first terminal device to act as a PIN management network element; the first terminal device receiving a first notification message from the PIN network function network element, the first notification message including first indication information and PIN identification information, the first indication information indicating that the first terminal device acts as a PIN management network element within the PIN.

[0024] The above scheme defines the configuration process of the PIN management network element within the PIN. This PIN management network element can act as the administrator within the PIN to manage the devices within the PIN, which helps to ensure the proper use of the PIN, realizes the proper management of the PIN, meets user needs, and helps to improve the user experience.

[0025] In one possible implementation, the first request message also includes identification information for the PIN.

[0026] In one possible implementation, the first terminal device receives a second request message from the second terminal device, the second request message including the identification information of the second terminal device and the identification information of the PIN, the second request message being used to request the addition of the PIN; the first terminal device sends a response message to the second terminal device, the response message indicating whether to agree to the second terminal device adding the PIN or to refuse the second terminal device adding the PIN.

[0027] In one possible implementation, the first terminal device receives a third request message from a third terminal device, the third request message including the identification information of the third terminal device and the identification information of the PIN, the third request message being used to request to join the PIN; the first terminal device assigns a PINE number to the third terminal device; the first terminal device sends the identification information of the PIN, the identification information of the PINE, and the PINE number to the PIN network function element, the identification information of the PINE being the identification information of the third terminal device.

[0028] The above scheme defines the process of adding a PINE within a PIN. This PINE can communicate with other PINEs, PEMCs, or PEGCs within the PIN, which helps to ensure the proper use and management of the PIN, meets user needs, and improves the user experience.

[0029] In one possible implementation, before receiving the third request message from the third terminal device, the first terminal device also sends a broadcast message including its own identification information and the identification information of the PIN. Thus, the third terminal device can obtain the identification information of the first terminal device and the identification information of the PIN. When the third terminal device wishes to add the PIN, it sends a request message carrying the PIN's identification information and its own identification information to the first terminal device.

[0030] In one possible implementation, after receiving a third request message from a third terminal device, and before assigning a PINE number to the third terminal device, the first terminal device further determines that it is allowed to add the PIN. One method is as follows: the first terminal device sends a query message to a unified data management network element. This query message includes the identification information of the third terminal device and is used to query whether the third terminal device is authorized to use as a PINE. The unified data management network element sends the query result to the first terminal device. If the query result indicates that the third terminal device is authorized to use as a PINE, the first terminal device determines that it is allowed to add the PIN; otherwise, if the query result indicates that the third terminal device is not authorized to use as a PINE, the UE1 determines that it is not allowed to add the PIN.

[0031] In one possible implementation, the first terminal device sends a fourth request message to the PIN network function element. The fourth request message includes the identification information and management instructions of the PIN, as well as the identification information of the fourth terminal device or the PINE number corresponding to the fourth terminal device.

[0032] In the above scheme, when the PIN management network element (i.e., the first terminal device) wants to manage a certain PINE within the PIN, the PIN management network element can send management commands to the PINE through the PIN network function network element and the PIN gateway network element, thus realizing remote PIN management, meeting user needs, and helping to improve user experience.

[0033] In one possible implementation, the first terminal device receives a second notification message from the PIN network function element. The second notification message includes second indication information and identification information of the fifth terminal device. The second indication information indicates that the fifth terminal device is a PIN management element within the PIN.

[0034] In one possible implementation, the first terminal device sends a fifth request message to the PIN network function element. The fifth request message includes the identification information of the first terminal device and the identification information of the PIN. The fifth request message is used to request the first terminal device to act as a PIN gateway element.

[0035] The first terminal device receives third indication information from the PIN network function element, the third indication information indicating that the first terminal device is a PIN gateway element within the PIN.

[0036] In one possible implementation, the first indication information is also used to indicate that the first terminal device is a PIN gateway network element within the PIN.

[0037] In one possible implementation, the first terminal device sends a sixth request message to the PIN network function element. The sixth request message includes the identification information of the sixth terminal device and is used to request the sixth terminal device to act as a PIN gateway element. The first terminal device receives a third notification message from the PIN network function element. The third notification message includes fourth indication information and the identification information of the PIN. The fourth indication information indicates that the sixth terminal device acts as a PIN gateway element within the PIN.

[0038] The above scheme defines the configuration process of the PIN gateway network element within the PIN. This PIN gateway network element can act as a gateway within the PIN, enabling message relay between devices within the PIN and the network. This facilitates the rational use and management of the PIN, meets user needs, and helps improve the user experience.

[0039] Thirdly, embodiments of this application provide a PIN management method, which can be executed by a first terminal device or a module (such as a chip) within the first terminal device. The first terminal device can also be referred to as a PIN gateway network element. Taking the execution of this method by the first terminal device as an example, the method includes: the first terminal device sending a first request message to a PIN network function network element, the first request message including the identification information of the first terminal device; the first terminal device receiving a first notification message from the PIN network function network element, the first notification message including indication information and the identification information of the PIN, the indication information indicating that the first terminal device is a PIN gateway network element within the PIN; the first terminal device sending a second request message to a PIN management network element, the second request message including the identification information of the first terminal device and the identification information of the PIN, the second request message being used to request joining the PIN; the first terminal device receiving a response message from the PIN management network element, the response message indicating agreement to the first terminal device joining the PIN, or rejection of the first terminal device joining the PIN.

[0040] The above scheme defines the configuration process of the PIN gateway network element within the PIN. This PIN gateway network element can act as a gateway within the PIN, enabling message relay between devices within the PIN and the network. This facilitates the rational use and management of the PIN, meets user needs, and helps improve the user experience.

[0041] In one possible implementation, when the response message indicates agreement for the first terminal device to join the PIN, the first terminal device sends an update message to the PIN network function element. The update message includes the identification information of the PIN gateway element and the identification information of the PIN, wherein the identification information of the PIN gateway element is the identification information of the first terminal device.

[0042] In one possible implementation, the first terminal device receives a third request message, which includes a PINE number and a management instruction; the first terminal device then sends the management instruction to the terminal device corresponding to the PINE number.

[0043] In one possible implementation, the first terminal device receives a fourth request message, which includes the identification information of the second terminal device and a join request, the join request being used to request to join the PIN; the first terminal device sends a fifth request message to the PIN management network element, the fifth request message including the identification information of the second terminal device and the join request.

[0044] In one possible implementation, the first terminal device receives a sixth request message from a third terminal device, the sixth request message including the identification information of the third terminal device and the identification information of the PIN, the sixth request message being used to request the addition of the PIN; the first terminal device sends a seventh request message to the PIN management network element, the seventh request message including the identification information of the third terminal device and the identification information of the PIN, the seventh request message being used to request the addition of the PIN.

[0045] In one possible implementation, before the first terminal device receives the sixth request message from the third terminal device, the first terminal device also sends a broadcast message, which includes the identification information of the first terminal device and the identification information of the PIN. Thus, the third terminal device can obtain the identification information of the first terminal device and the identification information of the PIN. When the third terminal device wishes to add the PIN, it sends a request message carrying the identification information of the PIN and the identification information of the third terminal device to the first terminal device.

[0046] In one possible implementation, the first terminal device receives a response message from the PIN management network element in response to the seventh request message, the response message including the PINE number assigned to the third terminal device by the PIN management network element. Correspondingly, the first terminal device may send a response message to the third terminal device in response to the sixth request message, the response message including PIN identification information and the PINE number of the third terminal device.

[0047] In one possible implementation, the first terminal device receives a response message from the PIN management network element in response to the seventh request message. The response message includes PIN identification information, third terminal device identification information, and indication information. The indication information indicates that the third terminal device is allowed to join the PIN. Then, the first terminal device assigns a PINE number to the third terminal device. The first terminal device can then send a response message to the third terminal device in response to the sixth request message. The response message includes PIN identification information and the third terminal device's PINE number.

[0048] In one possible implementation, the first terminal device or PEMC management network element sends an update message to the PIN management function network element. The update message includes the PIN identification information, the identification information of the third terminal device, and the PINE number of the third terminal device.

[0049] Fourthly, embodiments of this application provide a communication device, which may be a PIN network function element or a module (such as a chip) within a PIN network function element. This device has the function of implementing any of the implementation methods described in the first aspect. This function can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the aforementioned function.

[0050] Fifthly, embodiments of this application provide a communication device, which may be a first terminal device or a module (such as a chip) within the first terminal device. This device has the function of implementing any of the methods described in the second aspect above. This function can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the aforementioned functions.

[0051] Sixthly, embodiments of this application provide a communication device, which may be a first terminal device or a module (such as a chip) within the first terminal device. This device has the function of implementing any of the methods described in the third aspect above. This function can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the aforementioned functions.

[0052] In a seventh aspect, embodiments of this application provide a communication device including a processor coupled to a memory, the processor being configured to invoke a program stored in the memory to execute any of the implementation methods described in the first to third aspects above. The memory may be located within or outside the device. Furthermore, the processor may be one or more.

[0053] Eighthly, embodiments of this application provide a communication device, including a processor and an interface circuit. The processor is configured to communicate with other devices via the interface circuit and execute any of the implementation methods described in the first to third aspects. The processor may include one or more devices.

[0054] Ninthly, embodiments of this application provide a communication device, including a processor and a memory; the memory is used to store computer instructions, and when the device is running, the processor executes the computer instructions stored in the memory to cause the device to perform any of the implementation methods in the first to third aspects described above.

[0055] In a tenth aspect, embodiments of this application provide a communication apparatus, including units or means for performing various steps of any of the implementation methods in the first to third aspects described above.

[0056] Eleventhly, embodiments of this application also provide a computer-readable storage medium storing instructions that, when executed on a communication device, cause any of the implementation methods of the first to third aspects described above to be executed.

[0057] In a twelfth aspect, embodiments of this application also provide a computer program product, which includes a computer program or instructions that, when executed by a communication device, cause any of the implementation methods in the first to third aspects described above to be executed.

[0058] In a thirteenth aspect, embodiments of this application also provide a chip system, including: a processor for executing any of the implementation methods in the first to third aspects described above.

[0059] In a fourteenth aspect, embodiments of this application also provide a communication system, including a unified data management network element and a PIN network function network element for performing any method of the first aspect. The unified data management network element is configured to receive a first query message from the PIN network function network element, the first query message including identification information of a first terminal device, the first query message being used to query whether the first terminal device is authorized to be used as a PIN management network element; and to send a first query result to the PIN network function network element, the first query result indicating that the first terminal device is authorized to be used as a PIN management network element. Attached Figure Description

[0060] Figure 1 This is a schematic diagram of a 5G network architecture based on a service-oriented architecture.

[0061] Figure 2 This is a schematic diagram of a PIN architecture;

[0062] Figure 3 A schematic diagram of the PEMC configuration process provided in this application embodiment;

[0063] Figure 4 A schematic diagram illustrating the configuration process of PEGC provided in this application embodiment;

[0064] Figure 5(a) is a schematic diagram of the PINE addition process provided in the embodiment of this application;

[0065] Figure 5(b) is a schematic diagram of the PINE addition process provided in the embodiment of this application;

[0066] Figure 6 A schematic diagram of the PEMC change process provided in the embodiments of this application;

[0067] Figure 7 A schematic diagram of the PINE management method provided in the embodiments of this application;

[0068] Figure 8 A schematic diagram of the PINE addition process provided in an embodiment of this application;

[0069] Figure 9 A schematic diagram of a communication device provided in an embodiment of this application;

[0070] Figure 10 This is a schematic diagram of a communication device provided in an embodiment of this application. Detailed Implementation

[0071] Figure 1 This is a schematic diagram of a 5G network architecture based on a service-oriented architecture. Figure 1 The 5G network architecture shown includes a data network (DN) and a carrier network. The functions of some of these network elements are briefly described below.

[0072] The operator network may include one or more of the following network elements: Authentication Server Function (AUSF) network element (not shown in the figure), Unified Data Management (UDM) network element, Unified Data Repository (UDR) network element, Network Repository Function (NRF) network element (not shown in the figure), Network Exposure Function (NEF) network element (not shown in the figure), Application Function (AF) network element, Policy Control Function (PCF) network element, PIN Network Function (PNF) network element, Access and Mobility Management Function (AMF) network element, Session Management Function (SMF) network element, UPF network element, and Radio Access Network (RAN) equipment. In the above operator network, network elements or equipment other than RAN equipment can be referred to as core network elements or core network equipment.

[0073] Wireless access network equipment can be a base station, an evolved NodeB (eNodeB), a transmission reception point (TRP), a next-generation NodeB (gNB) in a 5G mobile communication system, a next-generation base station in a 6th-generation (6G) mobile communication system, a base station in a future mobile communication system, or an access node in a wireless fidelity (WiFi) system; it can also be a module or unit that performs some of the functions of a base station, for example, it can be a central unit (CU) or a distributed unit (DU). Wireless access network equipment can be a macro base station, a micro base station, an indoor station, a relay node, or a donor node, etc. The embodiments of this application do not limit the specific technology or equipment form used in the wireless access network equipment. For ease of explanation, the embodiments of this application use a base station as an example of a wireless access network equipment for illustration.

[0074] Terminal equipment communicating with the RAN can also be called a terminal, user equipment (UE), mobile station, mobile terminal, etc. Terminal equipment can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), Internet of Things (IoT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, smart cities, etc. Terminals can be mobile phones, tablets, computers with wireless transceiver capabilities, wearable devices, vehicles, drones, helicopters, airplanes, ships, robots, robotic arms, smart home devices, etc. The embodiments of this application do not limit the specific technology or form of the terminal equipment.

[0075] Wireless access network equipment and terminal equipment can be fixed or mobile. They can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; on water; or in the air on aircraft, balloons, and satellites. The embodiments of this application do not limit the application scenarios of the wireless access network equipment and terminal equipment.

[0076] Mobility management network elements (AMFs) are control plane network elements provided by the operator's network, responsible for access control and mobility management of terminal equipment accessing the operator's network. These functions include mobility state management, allocation of temporary user identities, authentication, and authorization. In 5G, AMFs can be used. In future communications such as the 6th generation (6G), AMFs may still be used, or they may have other names; this application does not limit the specific name.

[0077] The session management network element is a control plane network element provided by the operator's network, responsible for managing the protocol data unit (PDU) sessions of terminal equipment. A PDU session is a channel used to transmit PDUs; terminal equipment needs to exchange PDUs with the DN (Radio Access Network) through PDU sessions. The SMF (Service Management Frame) network element is responsible for establishing, maintaining, and deleting PDU sessions. The session management network element includes session management (such as session establishment, modification, and release, including tunnel maintenance between user plane network elements and radio access network equipment), user plane network element selection and control, Service and Session Continuity (SSC) mode selection, roaming, and other session-related functions. In 5G, the session management network element can be an SMF network element; in future communications such as 6G, the session management network element can still be an SMF network element, or have other names; this application does not limit this.

[0078] User plane network elements are gateways provided by the operator, serving as the gateway for communication between the operator's network and the DN (Digital Network Provider). UPF (User Plane Provider) network elements include user plane-related functions such as packet routing and transmission, packet inspection, service usage reporting, Quality of Service (QoS) processing, lawful interception, uplink packet inspection, and downlink packet storage. In 5G, user plane network elements can be UPF network elements. In future communications such as 6G, user plane network elements can still be UPF network elements, or may have other names; this application does not impose any limitations.

[0079] The data management network element is a control plane network element provided by the operator, responsible for storing information such as the subscriber permanent identifier (SUPI), credential, security context, and subscription data of subscribed users in the operator's network. This information stored by the data management network element can be used for authentication and authorization of terminal devices accessing the operator's network. In 5G, the data management network element can be a UDM network element. In future communications such as 6G, the data management network element can still be a UDM network element, or it may have other names; this application does not limit this.

[0080] A unified database network element is a control plane network element provided by the operator, which includes the function of storing and retrieving data of various types, such as subscription data, policy data, and application data. In 5G, the unified database network element can be a UDR network element. In future communications such as 6G, the unified database network element can still be a UDR network element, or it may have other names. This application does not limit this.

[0081] Open network elements are control plane network elements provided by operators. They securely expose the operator's network interface to third parties. When a session management network element needs to communicate with a third-party network element, the open network element can act as a relay for this communication. As a relay, the open network element can translate the identification information of subscribed users and third-party network elements. For example, when the open network element sends a subscribed user's SUPI from the operator's network to a third party, it can translate the SUPI into its corresponding external identity (ID). Conversely, when the open network element sends an external ID (the third party's network element ID) to the operator's network, it can translate it into a SUPI. In 5G, the open network element can be a NEF (Network Element for Front-End) network element. In future communications such as 6G, the open network element can still be a NEF network element, or it may have other names; this application does not limit this.

[0082] Application function network elements are used to convey application-side requirements to the network side, such as QoS requirements or user state event subscriptions. Application function network elements can be third-party functional entities or application servers deployed by operators. In 5G, application function network elements can be AF (Active Front-End) network elements. In future communications such as 6G, application function network elements can still be AF network elements, or have other names; this application does not limit their scope.

[0083] The policy control network element is a control plane function provided by the operator, used to provide policies for PDU sessions to the session management network element. Policies may include charging-related policies, QoS-related policies, and authorization-related policies. In 5G, the policy control network element can be a PCF network element. In future communications such as 6G, the policy control network element may still be a PCF network element, or may have other names; this application does not limit its scope.

[0084] Network storage function network elements can provide network element discovery capabilities, offering network element information corresponding to the network element type based on requests from other network elements. Network storage function network elements also provide network element management services, such as network element registration, updating, deregistration, and network element status subscription and push. In 5G, network storage function network elements can be NRF network elements. In future communications such as 6G, network storage function network elements can still be NRF network elements, or have other names; this application does not impose any limitations.

[0085] The PIN network function element can create a PIN, assign PIN identification information, and store PIN information based on a received PIN creation request. In 5G, the PIN network function element can be a PNF network element. In future communications such as 6G, the PIN network function element can still be a PNF network element, or it may have other names; this application does not limit this.

[0086] A Domain Provider (DN) is a network located outside of the carrier's network. A carrier's network can connect to multiple DNs, and various services can be deployed on a DN, providing data and / or voice services to terminal devices. For example, a DN might be the private network of a smart factory. Sensors installed in the workshop can act as terminal devices, and a control server for these sensors is deployed within the DN. The control server provides services to the sensors. Sensors can communicate with the control server, receive instructions from it, and transmit the collected sensor data back to the control server accordingly. Another example is a DN serving as an internal office network for a company. Employees' mobile phones or computers can act as terminal devices, accessing information and data resources on the company's internal office network.

[0087] Figure 1 Npcf, Nufr, Nudm, Naf, Namf, Nsmf, and Npnf are the service interfaces provided by the aforementioned PCF, UDR, UDM, AF, AMF, SMF, and PNF network elements, respectively, used to invoke the corresponding service operations. N1, N2, N3, N4, and N6 are interface sequence numbers, with the following meanings:

[0088] 1) N1: The interface between the AMF network element and the UE, which can be used to transmit non-access stratum (NAS) signaling (such as QoS rules from the AMF network element) to the UE.

[0089] 2) N2: The interface between the AMF network element and the wireless access network equipment, which can be used to transmit wireless bearer control information from the core network side to the wireless access network equipment.

[0090] 3) N3: The interface between the wireless access network device and the UPF network element, mainly used to transmit uplink user plane data and / or downlink user plane data between the wireless access network device and the UPF network element.

[0091] 4) N4: The interface between SMF network elements and UPF network elements. It can be used to transmit information between the control plane and the user plane, including the distribution of forwarding rules, QoS rules, traffic statistics rules, etc. from the control plane to the user plane, as well as the reporting of information from the user plane.

[0092] 5) N6: The interface between the UPF network element and the DN, used to transmit uplink user data streams and / or downlink user data streams between the UPF network element and the DN.

[0093] It is understood that the aforementioned network element or function can be a network component in a hardware device, a software function running on dedicated hardware, or a virtualized function instantiated on a platform (e.g., a cloud platform). Optionally, the aforementioned network element or function can be implemented by one device, multiple devices working together, or a functional module within a single device; this application embodiment does not specifically limit this.

[0094] Figure 2 This is a schematic diagram of the PIN architecture. A PIN contains one or more PIN management network elements, one or more PIN gateway network elements, and one or more PIN element (PINE) network elements. Figure 2 The example uses a PIN containing one PIN management network element, one PIN gateway network element, and two PINEs.

[0095] The PIN management network element, also known as the PIN elements with management capability (PEMC) network element, is hereinafter referred to as PEMC. The PEMC is responsible for managing the addition, removal, and resource allocation of elements (such as PINEs and PEGCs) within the PIN, and can assign PINE numbers to PINEs within the PIN. In specific implementations, the PEMC can be a 3GPP terminal device. The PINE number is the identification information of the PINE within the PIN.

[0096] PIN gateway network elements, also known as PIN elements with gateway capability (PEGC) network elements, hereinafter referred to as PEGC, have gateway functions and act as a relay node between the PIN and the network side. On the one hand, they are responsible for passing messages from the network (such as the 5G core network) to the PEMC or PINE, and on the other hand, they pass messages from the PEMC or PINE to the network. In specific implementations, PEGC can be a 3GPP terminal device.

[0097] A PINE network element, often simply referred to as a PINE, can communicate with other PINEs, PEMCs, or PEGCs within the same PIN. This communication can be device-to-device (D2D) communication, such as PC5 connectivity, Bluetooth, or Wireless Fidelity (WiFi), or it can be based on 3GPP. In specific implementations, a PINE can be a 3GPP terminal device or a non-3GPP terminal device.

[0098] It should be noted that PEMC not only has PIN management functionality but can also function as a regular PINE, possessing the same PINE functionality. Similarly, PEGC not only has PIN management functionality but can also function as a regular PINE, possessing the same PINE functionality.

[0099] In this embodiment, the PEGC and PEMC within the PIN support the PIN element function (PEF) defined between the transport and application layers. The PINE may or may not support PEF. When the PINE does not support PEF, it can still request to join the PIN. However, if the PINE receives a PEF-related message, it cannot parse it. The PINE needs to send the message to the PEMC / PEGC, which will then perform protocol conversion, such as converting it into a message that the underlying protocol can decipher. Finally, the PINE / PEGC / PEMC will send the converted message to other PINEs.

[0100] Figure 3 This is a schematic diagram of the PEMC configuration process provided in the embodiments of this application. In the following process, the interaction between UE1 and PNF can be that UE1 interacts with PNF through the base station and AMF, that is, UE1 sends messages to PNF through the base station and AMF, and PNF sends messages to UE1 through AMF and base station.

[0101] The method includes the following steps:

[0102] Step 301: UE1 or AF sends a request message to PNF.

[0103] The request message includes the UE1 ID, which is the identification information of terminal device 1. This request message is used to request UE1 to act as a PEMC. Optionally, the request message may also include a PIN ID.

[0104] It should be noted that in practical applications, the request message may not be sent to the PNF by UE1 or AF, but by other network elements. This application does not impose any restrictions on this.

[0105] Optionally, the request message can also be used to request the establishment of a PIN. Alternatively, prior to step 301, UE1 or AF may send another request message to PNF requesting a PIN.

[0106] Step 302a: The PNF sends a query message to the UDM, which includes the UE1 ID. This query message is used to request whether UE1 is authorized to be used as a PEMC.

[0107] For example, if the identification information of one or more UEs that have been authorized by the operator to be used as PEMC is stored in the UDM in advance, the PNF can find out whether a certain UE is authorized to be used as PEMC by querying the UDM.

[0108] The identification information of one or more UEs that can be used as PEMCs, stored in the UDM, can be registered to the UDM by the UE during the registration process. Specifically, during the registration process, the UE registers indication information indicating whether the UE has been authorized by the operator to be used as a PEMC to the UDM, so that the UDM can know whether the UE has been authorized by the operator to be used as a PEMC. Then, the UDM stores the identification information of one or more UEs that have been authorized by the operator to be used as a PEMC.

[0109] Step 302b: UDM sends the query results to PNF.

[0110] The query result indicates whether UE1 is authorized to be used as a PEMC or not.

[0111] Step 303: PNF records PIN information.

[0112] When the query result indicates that UE1 is authorized to be used as a PEMC, the PIN information recorded by the PNF includes the PEMC ID and the PIN ID. The PEMC ID is the same as the UE1 ID, and the PIN ID can be assigned by the PNF or carried in the request message of step 301 above.

[0113] Step 303 is an optional step.

[0114] Step 304: PNF sends a notification message to AF.

[0115] The notification message includes a PIN ID, and optionally, it also includes a PEMC ID, which is the UE1ID.

[0116] Step 304 is an optional step.

[0117] Step 305: PNF sends a notification message to UE1.

[0118] The notification message includes a PIN ID and an indication message indicating that UE1 is a PEMC.

[0119] The above scheme defines the configuration process of the PEMC within the PIN. The PEMC can act as the administrator within the PIN to manage the devices within the PIN, which helps to make the PIN more reasonable, realizes the reasonable management of the PIN, meets user needs, and helps to improve the user experience.

[0120] Figure 4 This is a schematic diagram of the PEGC configuration process provided in the embodiments of this application. In the following process, the interaction between UE2 and PNF can be that UE2 interacts with PNF through the base station and AMF, that is, UE2 sends messages to PNF through the base station and AMF, and PNF sends messages to UE2 through AMF and base station.

[0121] Should Figure 4 The embodiments described above are as follows. Figure 3 The implementation will be executed after the previous implementation is completed, that is, UE1 has been configured as the PEMC in the PIN.

[0122] The method includes the following steps:

[0123] Step 401: UE2 or AF sends a request message to PNF.

[0124] The request message includes the UE2 ID and is used to request UE2 as a PEGC.

[0125] It should be noted that in practical applications, the request message may not be sent to the PNF by UE2 or AF, but by other network elements; this application does not impose any restrictions on this.

[0126] Step 402a, the PNF sends a query message to the UDM, which includes the UE2 ID and is used to request whether UE2 is authorized to be used as a PEGC.

[0127] For example, if the identification information of one or more UEs that have been authorized by the operator to be used as PEGC is stored in the UDM in advance, the PNF can find out whether a certain UE is authorized to be used as PEGC by querying the UDM.

[0128] The identification information of one or more UEs that can be used as PEGC stored in the UDM can be registered to the UDM by the UE during the registration process. Specifically, during the registration process, the UE registers indication information indicating whether the UE has been authorized by the operator to be used as PEGC to the UDM, so that the UDM can know whether the UE has been authorized by the operator to be used as PEGC. Then the UDM stores the identification information of one or more UEs that have been authorized by the operator to be used as PEGC.

[0129] Step 402b: UDM sends the query results to PNF.

[0130] The query result indicates whether UE2 is authorized to be used as PEGC, or whether UE2 is not authorized to be used as PEGC.

[0131] Step 403: PNF sends a notification message to UE2.

[0132] When the query result indicates that UE2 is authorized to be used as a PEGC, the notification message includes a PIN ID, a PEMC ID, and an indication that UE2 is the PEGC. The PEMC ID is the same as the UE1 ID.

[0133] Step 404: UE2 sends a request message to UE1 (i.e. PEMC). The request message includes UE2 ID and PIN ID. The request message is used to request to join the PIN.

[0134] Step 405, UE1 sends a response message to UE2, which indicates whether to agree to UE2 joining the PIN or to refuse UE2 joining the PIN.

[0135] Step 406: UE2 sends an update message to PNF.

[0136] When the response message in step 405 indicates that UE2 is allowed to join the PIN, the update message includes the PEGC ID and the PIN ID. The update message is used to request an update of the PIN information in the PNF record. The PEGC ID is the UE2 ID.

[0137] If the response message in step 405 indicates that UE2 is refused to join the PIN, then steps 406 and 407 can be skipped.

[0138] Step 407: PNF updates PIN information.

[0139] PNF updates the recorded PIN information based on the PEGC ID and PIN ID in the update message. The updated PIN includes the PIN ID, PEMC ID, and PEGC ID.

[0140] Steps 406 and 407 above are optional steps.

[0141] The above scheme defines the configuration process of the PEGC within the PIN. The PEGC can act as a gateway within the PIN to realize message relay between devices within the PIN and the network, which helps to make reasonable use of the PIN, realizes reasonable management of the PIN, meets user needs, and helps to improve user experience.

[0142] The above Figure 4 In this embodiment, the UE configured as PEMC (i.e., UE1) and the UE configured as PEGC (i.e., UE2) are different UEs. In another method, the PEMC and PEGC within the PIN can also be the same UE, such as UE1 as described above. In this scenario, it is not necessary to execute the above. Figure 4 The embodiments described above, but in the above-mentioned Figure 3Based on the previous implementation, UE1 is also configured as a PEGC. In one implementation, the request message in step 301 is further used to request UE1 to be a PEGC, the query message in step 302a is further used to query whether UE1 is authorized to be used as a PEGC, the query result in step 302b is further used to indicate that UE1 is authorized to be used as a PEGC, the PIN information recorded in step 303 also includes the PEGC identification information (i.e., the UE1 identification information), the indication information in step 305 is further used to indicate that UE1 is a PEGC, or the notification message in step 305 also includes another indication information to indicate that UE1 is a PEGC. In another implementation, after step 305, UE1 or AF sends another request message to PNF to request UE1 to be a PEGC, and then PNF sends a query message to UDM, which includes the UE1 ID and is used to request whether UE1 is authorized to be used as a PEGC. Then UDM sends a query result to PNF, which indicates that UE1 is authorized to be used as PEGC. PNF then sends a notification message to UE1, which includes PINID, PEGC ID and indication information, which indicates that UE1 is the PEGC and that the PEGC ID is the UE1 ID.

[0143] In another implementation, the PEMC can select a UE as the PEGC. For example, the PEMC selects a UE, taking UE4 as an example. UE4 can have already established a communication connection with the PEMC (e.g., WiFi, Bluetooth) or it can have not established a communication connection with the PEMC. Then, the PEMC sends a request message to the PNF to request UE4 to be used as the PEGC. The PNF sends a query message to the UDM, which includes the UE4 ID and requests whether UE4 is authorized to be used as the PEGC. The UDM then sends the query result to the PNF, indicating that UE4 is authorized to be used as the PEGC. The PNF then sends a notification message to both UE4 and the PEMC. This notification message includes a PIN ID, a PEGC ID, and indication information, indicating that UE4 is the PEGC, and the PEGC ID is the same as the UE4 ID.

[0144] Figure 5(a) is a schematic diagram of the PINE joining process provided in the embodiment of this application. In the following process, the interaction between UE2 and PNF can be that UE2 interacts with PNF through the base station and AMF, that is, UE2 sends messages to PNF through the base station and AMF, and PNF sends messages to UE2 through AMF and base station.

[0145] The embodiment shown in Figure 5(a) is based on the above. Figure 3 , Figure 4The implementation is executed after the previous one is completed, that is, UE1 has been configured as PEMC in the PIN and UE2 has been configured as PEGC in the PIN. In the embodiment of Figure 5(a), UE1, UE2 and UE3 are all in the same PIN range and communicate with each other in a D2D manner.

[0146] The method includes the following steps:

[0147] Step 501a: UE3 sends a request message to UE1 (i.e. PEMC). The request message includes UE3 ID and PIN ID. The request message is used to request UE3 to add a PIN.

[0148] The UE3 can be a 3GPP terminal device or a non-3GPP terminal device.

[0149] As one implementation method, UE1 broadcasts the PEMC ID (i.e., UE1 ID) and PIN ID to the outside world, so that UE3 can obtain the PEMC ID and PIN ID. When UE3 determines that it wants to join the PIN, it sends a request message carrying the PIN ID and UE3 ID to UE1 based on the PEMC ID.

[0150] After step 501a, either method one (involving steps 502a to 506a) or method two (involving steps 507a to 512a) can be performed. The main difference between method one and method two is that in method one, the PINE number is assigned to the PINE by the PEMC, while in method two, the PINE number is assigned to the PINE by the PEGC.

[0151] Step 502a: If UE1 allows UE3 to add a PIN, then assign a PINE number to UE3.

[0152] The PINE number is the identification information of the PINE within the PIN. Therefore, assigning a PINE number to UE3 means assigning a unique identifier to UE3 within the PIN.

[0153] As one implementation method, UE1 determines whether to allow UE3 to join the PIN based on the following approach: UE1 sends a query message to UDM, which includes the UE3 ID. This query message is used to check whether UE3 is authorized to be used as a PINE. UDM sends the query result to UE1. If the query result indicates that UE3 is authorized to be used as a PINE, then UE1 determines that UE3 is allowed to join the PIN; otherwise, if the query result indicates that UE3 is not authorized to be used as a PINE, then UE1 determines that UE3 is not allowed to join the PIN.

[0154] Step 503a: UE1 sends a response message to UE3, which includes the PINE number and PIN ID.

[0155] Step 504a: UE1 sends an update message to UE2 (i.e., PEGC), which includes PIN ID, PINE ID and PINE number.

[0156] This PINE ID is the same as the UE3 ID.

[0157] Step 505a: UE1 or UE2 sends an update message to the PNF, which includes the PIN ID, PINE ID and PINE number.

[0158] Step 506a: PNF updates PIN information.

[0159] PNF updates the recorded PIN information based on the PIN ID, PINE ID, and PINE number in the update message. The updated PIN includes the PIN ID, PEMC ID, PEGC ID, PINE ID (i.e., UE3 ID), and the UE3's PINE number.

[0160] Steps 504a to 506a above are optional steps.

[0161] In step 507a, if UE1 allows UE3 to add a PIN, it sends an update message to PEGC. This update message includes the PIN ID and the PINE ID, which is the UE3 ID.

[0162] The method by which UE1 determines whether UE3 is allowed to add a PIN is described in step 502a.

[0163] Step 508a, PEGC assigns a PINE number to UE3.

[0164] The PINE number is the identification information of the PINE within the PIN. Therefore, assigning a PINE number to UE3 means assigning a unique identifier to UE3 within the PIN.

[0165] Step 509a: PEGC sends the PINE number of UE3 to PEMC.

[0166] Step 510a: UE1 sends a response message to UE3, which includes the PINE number and PIN ID.

[0167] Step 511a: UE1 or UE2 sends an update message to the PNF, which includes the PIN ID, PINE ID and PINE number.

[0168] Step 512a: PNF updates PIN information.

[0169] PNF updates the recorded PIN information based on the PIN ID, PINE ID, and PINE number in the update message. The updated PIN includes the PIN ID, PEMC ID, PEGC ID, PINE ID (i.e., UE3 ID), and the UE3's PINE number.

[0170] Steps 511a to 512a above are optional steps.

[0171] When other UEs, such as UE4 and UE5, want to join the PIN, they can use the method described above to request to join the PIN, which will not be repeated here.

[0172] The above scheme defines the process of adding a PINE within a PIN. This PINE can communicate with other PINEs, PEMCs, or PEGCs within the PIN, which helps to ensure the proper use and management of the PIN, meets user needs, and improves the user experience.

[0173] Figure 5(b) is a schematic diagram of the PINE joining process provided in the embodiment of this application. In the following process, the interaction between UE2 and PNF can be that UE2 interacts with PNF through the base station and AMF, that is, UE2 sends messages to PNF through the base station and AMF, and PNF sends messages to UE2 through AMF and base station.

[0174] The embodiment shown in Figure 5(b) is based on the above. Figure 3 , Figure 4 The implementation is executed after the previous one is completed, that is, UE1 has been configured as PEMC in the PIN and UE2 has been configured as PEGC in the PIN. In the embodiment of Figure 5(b), UE1, UE2 and UE3 are all in the same PIN range and communicate with each other in a D2D manner.

[0175] The method includes the following steps:

[0176] Step 501b: UE3 sends a request message to UE2 (i.e., PEGC). The request message includes UE3 ID and PIN ID. The request message is used to request UE3 to add a PIN.

[0177] The UE3 can be a 3GPP terminal device or a non-3GPP terminal device.

[0178] As one implementation method, UE2 broadcasts its PEGC ID (i.e., UE2 ID) and PIN ID to the outside world, so that UE3 can obtain the PEGC ID and PIN ID. When UE3 determines that it wants to join the PIN, it sends a request message carrying the PIN ID and UE3 ID to UE2 based on the PEGC ID.

[0179] Step 502b: UE2 sends a request message to UE1 (i.e., PEMC). The request message includes UE3 ID and PIN ID, and requests UE3 to add a PIN.

[0180] After step 502b, either Method 1 (involving steps 503b to 507b) or Method 2 (involving steps 508b to 513b) can be performed. The main difference between Method 1 and Method 2 is that in Method 1, the PINE number is assigned by PEMC, while in Method 2, the PINE number is assigned by PEGC.

[0181] In step 503b, if UE1 allows UE3 to add a PIN, then assign a PINE number to UE3.

[0182] The PINE number is the identification information of the PINE within the PIN. Therefore, assigning a PINE number to UE3 means assigning a unique identifier to UE3 within the PIN.

[0183] The method by which UE1 determines whether UE3 is allowed to add a PIN is described in step 502a.

[0184] Step 504b: UE1 sends a response message to UE2, which includes PINE ID, PINE number and PIN ID.

[0185] This PINE ID is the same as the UE3 ID.

[0186] In step 505b, UE2 sends a response message to UE3, which includes the PIN ID and PINE number.

[0187] Step 506b: UE1 or UE2 sends an update message to the PNF, which includes the PIN ID, PINE ID, and PINE number.

[0188] Step 507b: PNF updates PIN information.

[0189] PNF updates the recorded PIN information based on the PIN ID, PINE ID, and PINE number in the update message. The updated PIN includes the PIN ID, PEMC ID, PEGC ID, PINE ID (i.e., UE3 ID), and the UE3's PINE number.

[0190] Steps 506b to 507b above are optional steps.

[0191] In step 508b, UE1 allows UE3 to add a PIN, and then sends a response message to UE2 (i.e., PEGC). The response message includes a PIN ID and a PINE ID, which is the UE3 ID.

[0192] The method by which UE1 determines whether UE3 is allowed to add a PIN is described in step 502a.

[0193] Optionally, the response message may also include indication information to indicate that UE3 is allowed to join the PIN.

[0194] Step 509b: UE2 assigns a PINE number to UE3.

[0195] The PINE number is the identification information of the PINE within the PIN. Therefore, assigning a PINE number to UE3 means assigning a unique identifier to UE3 within the PIN.

[0196] Step 510b: UE2 sends the PINE number of UE3 to UE1.

[0197] In step 511b, UE2 sends a response message to UE3, which includes the PINE number and PIN ID.

[0198] Step 512b: UE1 or UE2 sends an update message to the PNF, which includes the PIN ID, PINE ID and PINE number.

[0199] Step 513b: PNF updates PIN information.

[0200] PNF updates the recorded PIN information based on the PIN ID, PINE ID, and PINE number in the update message. The updated PIN includes the PIN ID, PEMC ID, PEGC ID, PINE ID (i.e., UE3 ID), and the UE3's PINE number.

[0201] Steps 512b to 513b above are optional steps.

[0202] When other UEs, such as UE4 and UE5, want to join the PIN, they can use the method described above to request to join the PIN, which will not be repeated here.

[0203] The above scheme defines the process of adding a PINE within a PIN. This PINE can communicate with other PINEs, PEMCs, or PEGCs within the PIN, which helps to ensure the proper use and management of the PIN, meets user needs, and improves the user experience.

[0204] Figure 6 This is a schematic diagram of the PEMC modification process provided in the embodiments of this application. In the following process, the interaction between the UE (such as UE1, UE2, UE3) and the PNF can be that the UE interacts with the PNF through the base station and AMF, that is, the UE sends messages to the PNF through the base station and AMF, and the PNF sends messages to the UE through the AMF and base station.

[0205] Should Figure 6 The embodiments described above are as follows. Figure 3 This is executed after the previous implementation has finished executing, that is, UE1 is the current PEMC, and then through... Figure 6 The embodiment updates PEMC from UE1 to UE3.

[0206] The method includes the following steps:

[0207] Step 601, UE3 sends a request message to PNF, which includes UE3 ID and PIN ID, and is used to request UE3 to act as PEMC.

[0208] Step 602a: The PNF sends a query message to the UDM, which includes the UE3 ID. This query message is used to request whether UE3 is authorized to be used as a PEMC.

[0209] Step 602b: UDM sends the query result to PNF.

[0210] The query result indicates that UE3 is authorized to be used as a PEMC, or that UE3 is not authorized to be used as a PEMC.

[0211] Step 603: PNF updates PIN information.

[0212] When the query result indicates that UE3 is authorized to be used as PEMC, the PNF updates the PIN information of the record. The updated PIN includes at least the PIN ID and the PEMC ID, which is the UE3 ID.

[0213] Step 604: PNF sends a response message to UE3.

[0214] The response message includes a PIN ID and an indication message indicating that UE3 is acting as a PEMC.

[0215] Step 605: PNF sends a notification message to UE2.

[0216] The notification message includes a PIN ID, a PEMC ID, and an indication message. The PEMC ID is the UE3 ID, and the indication message indicates that UE3 is the PEMC.

[0217] Step 606: PNF sends a notification message to UE1.

[0218] The notification message includes a PIN ID, a PEMC ID, and an indication message. The PEMC ID is the UE3 ID, and the indication message indicates that UE3 is the PEMC.

[0219] The above scheme defines the update process of PEMC within the PIN, realizes reasonable PIN management, meets user needs, and helps improve user experience.

[0220] Figure 7 This is a schematic flowchart of a PINE management method provided in an embodiment of this application. In this embodiment, a PIN has been established, where UE1 acts as the PEMC, UE2 as the PEGC, and UE3 as the PINE. Because the PEMC has moved, it has left the D2D communication range. When the PEMC wants to manage a specific PINE (such as UE3) within the PIN, the PEMC sends a management command to UE3 via the PNF and PEGC.

[0221] The method includes the following steps:

[0222] Step 701, UE1 (i.e. PEMC) sends a request message to PNF, which includes PIN ID and management instructions, as well as UE3's PINE number or UE3 ID.

[0223] The UE3 can be a 3GPP terminal device or a non-3GPP terminal device.

[0224] In one implementation, the management instruction is a move-out instruction, which instructs UE3 to be moved out of the PIN.

[0225] In one implementation, the management instruction is an activation instruction, which instructs UE3 to be activated.

[0226] In one implementation, the management instruction is a deactivation instruction, which instructs UE3 to be deactivated.

[0227] In one implementation method, the management instructions include the management policy of UE1 for UE3.

[0228] Step 702: The PNF sends a request message to the AMF, which includes the PEGC ID and management instructions, as well as the UE3 ID or PINE number.

[0229] The PNF obtains the PEGC ID corresponding to the PIN ID in the request message.

[0230] Step 703: The AMF sends a request message to the base station, which includes the PEGC ID and management instructions, as well as the UE3 ID or PINE number.

[0231] Step 704: The base station sends a request message to the PEGC based on the PEGC ID. The request message includes management instructions and also includes the UE3 ID or PINE number.

[0232] Step 705: PEGC sends a management command to UE3 based on the PINE number or UE3 ID.

[0233] Step 706: UE3 executes management instructions.

[0234] For example, if the management command is a move-out command, then UE3 will exit the PIN.

[0235] For example, if the management command is an activation command, then UE3 will activate the PIN-related functions.

[0236] For example, if the management command is to deactivate the command, then UE3 will deactivate the PIN-related functions.

[0237] For example, if the management command includes the management policy of UE1 to UE3, then UE3 will execute the management policy.

[0238] Step 707: PEGC sends a response message to the base station, which includes a PIN ID and a PINE number including UE3 ID or UE3.

[0239] For example, if the management command is a move-out command, then the response message indicates that UE3 has been moved out of the PIN.

[0240] For example, if the management command is an activation command, then the response message indicates that UE3 has activated the PIN.

[0241] For example, if the management command is a deactivation command, then the response message indicates that UE3 has deactivated the PIN.

[0242] For example, if the management instruction includes the management policy of UE1 for UE3, then the response message indicates that UE3 has executed the management policy.

[0243] Step 708: The base station sends a response message to the AMF, which includes a PIN ID and a PINE number including the UE3 ID or UE3.

[0244] The function of this response message is the same as that of the response message in step 707 above.

[0245] Step 709, the AMF sends a response message to the PNF, which includes the PIN ID and the PINE number including the UE3 ID or UE3.

[0246] The function of this response message is the same as that of the response message in step 707 above.

[0247] Step 710: PNF updates PIN information.

[0248] For example, if the response message in step 709 indicates that UE3 has been removed from the PIN, then the relevant information of UE3 will be deleted from the PIN information stored locally.

[0249] For example, if the response message in step 709 indicates that UE3 has activated the PIN, then the PIN information stored locally records that UE3 has been activated.

[0250] For example, if the response message in step 709 indicates that UE3 has deactivated the PIN, then the PIN information stored locally records that UE3 has been deactivated.

[0251] For example, if the response message in step 709 indicates that UE3 has executed the management policy, then the PIN will record in the locally stored PIN information that UE3 has executed the management policy.

[0252] Steps 707 to 710 above are all optional steps.

[0253] In the above scheme, the PEMC in the PIN is moved out of the D2D communication range. When the PEMC wants to manage a certain PINE in the PIN, the PEMC sends management commands to the PINE through PNF and PEGC, realizing remote management of the PIN, meeting user needs and helping to improve user experience.

[0254] Figure 8 This is a schematic diagram of the PINE joining process provided in an embodiment of this application. In this embodiment, a PIN has been established, with UE1 acting as PEMC and UE2 as PEGC. When UE3, which is not within the D2D communication range of this PIN, wishes to join the PIN, UE3 requests to join the PIN via PNF.

[0255] The method includes the following steps:

[0256] Step 801: UE3 sends a request message to PNF. The request message includes UE3 ID, PIN ID and join request. The join request is used to request that UE3 be added to the PIN.

[0257] Step 802: The PNF sends a request message to the AMF, which includes the PEGC ID, UE3 ID, and a join request.

[0258] The PNF obtains the PEGC ID corresponding to the PIN ID in the request message.

[0259] Step 803: The AMF sends a request message to the base station, which includes the PEGC ID, UE3 ID, and a join request.

[0260] Step 804: The base station sends a request message to UE2 (i.e., PEGC) based on the PEGC ID. The request message includes the UE3 ID and the join request.

[0261] Step 805: PEGC sends a request message to UE1 (i.e., PEMC), which includes the UE3 ID and a join request.

[0262] Step 806: If UE1 allows UE3 to add a PIN, then assign a PINE number to UE3.

[0263] Step 807: UE1 sends a response message to UE2 (i.e., PEGC), which includes PIN ID, PINE ID and UE3's PINE number.

[0264] This PINE ID is the same as the UE3 ID.

[0265] Step 808: UE2 sends a response message to the base station, which includes PIN ID, PINE ID and PINE number.

[0266] Step 809: The base station sends a response message to the AMF, which includes the PIN ID, PINE ID, and PINE number.

[0267] Step 810: AMF sends a response message to PNF, which includes PIN ID, PINE ID and PINE number.

[0268] Step 811, PNF updates PIN information.

[0269] PNF adds a PINE ID and a PINE number to the PIN information corresponding to the PIN ID. This PINE ID is the UE3 ID.

[0270] Step 812: PNF sends a response message to UE3, which includes the PINE number.

[0271] In the above scheme, when a UE outside the D2D communication range of the PIN wants to join the PIN, the UE requests to join the PIN through PNF, which realizes joining the PIN over a long distance, meets user needs, and helps to improve user experience.

[0272] It is understood that, in order to achieve the functions in the above embodiments, the PIN network function element or terminal device includes hardware structures and / or software modules corresponding to each function. Those skilled in the art should readily recognize that, based on the units and method steps of the various examples described in conjunction with the embodiments disclosed in this application, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application scenario and design constraints of the technical solution.

[0273] Figure 9 and Figure 10 The diagram illustrates the possible communication devices provided in the embodiments of this application. These communication devices can be used to implement the functions of PIN network function elements or terminal devices in the above method embodiments, and thus can also achieve the beneficial effects of the above method embodiments. In the embodiments of this application, the communication device can be a PIN network function element or a terminal device, or it can be a module (such as a chip) in a PIN network function element or a module (such as a chip) in a terminal device.

[0274] Figure 9 The communication device 900 shown includes a processing unit 910 and a transceiver unit 920. The communication device 900 is used to implement the functions of the PIN network function element or terminal device in the above method embodiments. The transceiver unit 920 can be used to implement corresponding communication functions. The transceiver unit 920 can also be referred to as a communication interface or communication unit. The processing unit 910 can be used to implement corresponding processing functions. Optionally, the communication device 900 further includes a storage unit, which can be used to store instructions and / or data. The processing unit 910 can read the instructions and / or data from the storage unit to enable the communication device 900 to implement the operations of the PIN network function element or terminal device in the aforementioned method embodiments.

[0275] When the communication device 900 is used to implement the function of the PIN network function element in the above method embodiment, the transceiver unit 920 is used to receive a first request message, the first request message including the identification information of the first terminal device, the first request message being used to request the first terminal device to act as a PIN management element; send a first query message to the unified data management element, the first query message including the identification information of the first terminal device, the first query message being used to query whether the first terminal device is authorized to act as a PIN management element; receive a first query result from the unified data management element, the first query result indicating that the first terminal device is authorized to act as a PIN management element; and send a first notification message to the first terminal device, the first notification message including first indication information and PIN identification information, the first indication information indicating that the first terminal device acts as a PIN management element within the PIN.

[0276] In one possible implementation, the first request message may also include identification information of the PIN; or, the processing unit 910 may be used to allocate the identification information of the PIN.

[0277] In one possible implementation, the transceiver unit 920 is also used to send the identification information of the PIN to the application function network element.

[0278] In one possible implementation, the transceiver unit 920 is configured to receive the first request message from the first terminal device; or, to receive the first request message from an application function network element.

[0279] In one possible implementation, the transceiver unit 920 is further configured to receive a second request message, the second request message including identification information of a second terminal device, the second request message being used to request the second terminal device to act as a PIN gateway network element; send a second query message to the unified data management network element, the second query message including identification information of the second terminal device, the second query message being used to query whether the second terminal device is authorized to act as a PIN gateway network element; receive a second query result from the unified data management network element, the second query result indicating that the second terminal device is authorized to act as a PIN gateway network element; and send a second notification message to the second terminal device, the second notification message including second indication information, identification information of the PIN management network element, and identification information of the PIN, the second indication information indicating that the second terminal device acts as a PIN gateway network element within the PIN, the identification information of the PIN management network element being the identification information of the first terminal device.

[0280] In one possible implementation, the transceiver unit 920 is configured to receive the second request message from the second terminal device, the application function network element, or the first terminal device.

[0281] In one possible implementation, the transceiver unit 920 is further configured to receive a first update message from the second terminal device, the first update message including the identification information of the PIN gateway network element and the identification information of the PIN, the identification information of the PIN gateway network element being the identification information of the second terminal device; the processing unit 910 is configured to update the PIN information to obtain first PIN information, the first PIN information including the identification information of the PIN, the identification information of the PIN management network element and the identification information of the PIN gateway.

[0282] In one possible implementation, the transceiver unit 920 is further configured to receive a second update message from the second terminal device, the second update message including the identification information of the PIN, the identification information of the PINE, and the PINE number corresponding to the PINE, wherein the identification information of the PINE is the identification information of the third terminal device; the processing unit 910 is configured to update the first PIN information to obtain second PIN information, the second PIN information including the identification information of the PIN, the identification information of the PIN management network element, the identification information of the PIN gateway, the identification information of the PINE, and the PINE number.

[0283] In one possible implementation, the transceiver unit 920 is further configured to receive a third request message from a third terminal device, the third request message including the identification information of the third terminal device, the identification information of the PIN, and a join request, the join request being used to request to join the PIN; send the identification information of the third terminal device and the join request to the first terminal device through the second terminal device; receive the identification information of the PINE and the PINE number corresponding to the PINE from the first terminal device through the second terminal device, the identification information of the PINE being the identification information of the third terminal device; and the processing unit 910 is configured to update the first PIN information to obtain second PIN information, the second PIN information including the identification information of the PIN, the identification information of the PIN management network element, the identification information of the PIN gateway, the identification information of the PINE, and the PINE number.

[0284] In one possible implementation, the transceiver unit 920 is further configured to receive a fourth request message from the first terminal device, the fourth request message including the identification information and management instructions of the PIN, and also including the identification information of the fourth terminal device or the PINE number corresponding to the fourth terminal device; and send the management instructions to the fourth terminal device through the second terminal device.

[0285] In one possible implementation, the transceiver unit 920 is further configured to receive a fifth request message from the fifth terminal device, the fifth request message including the identification information of the PIN and the identification information of the fifth terminal device; send a third query message to the unified data management network element, the third query message including the identification information of the fifth terminal device, the third query message being used to query whether the fifth terminal device is authorized to be used as a PIN management network element; receive a third query result from the unified data management network element, the third query result indicating that the fifth terminal device is authorized to be used as a PIN management network element; and send a third indication message and the identification information of the PIN to the fifth terminal device, the third indication message indicating that the fifth terminal device is a PIN management network element within the PIN.

[0286] In one possible implementation, the transceiver unit 920 is further configured to send a third notification message to the first terminal device, the third notification message including fourth indication information and identification information of the fifth terminal device, the fourth indication information indicating that the fifth terminal device is a PIN management network element within the PIN.

[0287] When the communication device 900 is used to implement the function of the first terminal device, the transceiver unit 920 is used to send a first request message to the Personal Internet of Things PIN network function element. The first request message includes the identification information of the first terminal device and is used to request the first terminal device to act as a PIN management element. The transceiver unit 920 also receives a first notification message from the PIN network function element. The first notification message includes first indication information and the identification information of the PIN. The first indication information indicates that the first terminal device acts as a PIN management element within the PIN.

[0288] In one possible implementation, the first request message also includes identification information for the PIN.

[0289] In one possible implementation, the transceiver unit 920 is further configured to receive a second request message from a second terminal device, the second request message including the identification information of the second terminal device and the identification information of the PIN, the second request message being used to request to join the PIN; and to send a response message to the second terminal device, the response message indicating whether to agree to allow the second terminal device to join the PIN or to refuse the second terminal device to join the PIN.

[0290] In one possible implementation, the transceiver unit 920 is further configured to receive a third request message from a third terminal device, the third request message including the identification information of the third terminal device and the identification information of the PIN, the third request message being used to request the addition of the PIN; the processing unit 910 is configured to assign a PINE number to the third terminal device; the transceiver unit 920 is further configured to send the identification information of the PIN, the identification information of the PINE, and the PINE number to the PIN network function element, the identification information of the PINE being the identification information of the third terminal device.

[0291] In one possible implementation, the transceiver unit 920 is further configured to send a fourth request message to the PIN network function element. The fourth request message includes the identification information and management instructions of the PIN, as well as the identification information of the fourth terminal device or the PINE number corresponding to the fourth terminal device.

[0292] In one possible implementation, the transceiver unit 920 is further configured to receive a second notification message from the PIN network function element, the second notification message including second indication information and identification information of the fifth terminal device, the second indication information indicating that the fifth terminal device is a PIN management element within the PIN.

[0293] In one possible implementation, the transceiver unit 920 is further configured to send a fifth request message to the PIN network function element, the fifth request message including the identification information of the first terminal device and the identification information of the PIN, the fifth request message being used to request the first terminal device to act as a PIN gateway element; and to receive third indication information from the PIN network function element, the third indication information indicating that the first terminal device acts as a PIN gateway element within the PIN.

[0294] In one possible implementation, the first indication information is also used to indicate that the first terminal device is a PIN gateway network element within the PIN.

[0295] In one possible implementation, the transceiver unit 920 is further configured to send a sixth request message to the PIN network function element, the sixth request message including identification information of a sixth terminal device, the sixth request message being used to request the sixth terminal device to act as a PIN gateway element; and to receive a third notification message from the PIN network function element, the third notification message including fourth indication information and identification information of the PIN, the fourth indication information indicating that the sixth terminal device acts as a PIN gateway element within the PIN.

[0296] When the communication device 900 is used to implement the function of the first terminal device, the transceiver unit 920 is used to send a first request message to a personal Internet of Things (IoT) PIN network function element, the first request message including the identification information of the first terminal device; receive a first notification message from the PIN network function element, the first notification message including indication information and the identification information of the PIN, the indication information indicating that the first terminal device is a PIN gateway element within the PIN; send a second request message to a PIN management element, the second request message including the identification information of the first terminal device and the identification information of the PIN, the second request message being used to request joining the PIN; and receive a response message from the PIN management element, the response message indicating whether to agree to the first terminal device joining the PIN or to refuse the first terminal device joining the PIN.

[0297] In one possible implementation, the transceiver unit 920 is further configured to send an update message to the PIN network function element when the response message indicates that the first terminal device is agreed to join the PIN. The update message includes the identification information of the PIN gateway element and the identification information of the PIN, wherein the identification information of the PIN gateway element is the identification information of the first terminal device.

[0298] In one possible implementation, the transceiver unit 920 is further configured to receive a third request message, which includes a PINE number and a management instruction; and send the management instruction to the terminal device corresponding to the PINE number.

[0299] In one possible implementation, the transceiver unit 920 is further configured to receive a fourth request message, which includes the identification information of the second terminal device and a join request, the join request being used to request to join the PIN; and send a fifth request message to the PIN management network element, the fifth request message including the identification information of the second terminal device and the join request.

[0300] A more detailed description of the processing unit 910 and the transceiver unit 920 can be obtained directly from the relevant descriptions in the above method embodiments, and will not be repeated here.

[0301] like Figure 10 As shown, the communication device 1000 includes a processor 1010 and an interface circuit 1020. The processor 1010 and the interface circuit 1020 are coupled to each other. It is understood that the interface circuit 1020 can be a transceiver or an input / output interface. Optionally, the communication device 1000 may also include a memory 1030 for storing instructions executed by the processor 1010, or storing input data required by the processor 1010 to execute instructions, or storing data generated after the processor 1010 executes instructions.

[0302] When the communication device 1000 is used to implement the above method embodiment, the processor 1010 is used to implement the function of the processing unit 910, and the interface circuit 1020 is used to implement the function of the transceiver unit 920.

[0303] It is understood that the processor in the embodiments of this application may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. A general-purpose processor may be a microprocessor or any conventional processor.

[0304] The method steps in the embodiments of this application can be implemented in hardware or by a processor executing software instructions. The software instructions can consist of corresponding software modules, which can be stored in random access memory, flash memory, read-only memory, programmable read-only memory, erasable programmable read-only memory, electrically erasable programmable read-only memory, registers, hard disks, portable hard disks, CD-ROMs, or any other form of storage medium known in the art. An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and storage medium can reside in an ASIC. Alternatively, the processor and storage medium can exist as discrete components in a base station or terminal.

[0305] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of this application are performed entirely or partially. The computer can be a general-purpose computer, a special-purpose computer, a computer network, a base station, a user equipment, or other programmable device. The computer program or instructions can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program or instructions can be transferred from one website, computer, server, or data center to another website, computer, server, or data center via wired or wireless means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; it can also be an optical medium, such as a digital video optical disc; or it can be a semiconductor medium, such as a solid-state drive. The computer-readable storage medium may be a volatile or non-volatile storage medium, or may include both types of storage media.

[0306] In the various embodiments of this application, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of different embodiments are consistent and can be referenced by each other. The technical features of different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0307] In this application, "at least one" means one or more, and "more than one" means two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. In the textual description of this application, the character " / " generally indicates an "or" relationship between the preceding and following related objects; in the formulas of this application, the character " / " indicates a "division" relationship between the preceding and following related objects.

[0308] It is understood that the various numerical designations used in the embodiments of this application are merely for descriptive convenience and are not intended to limit the scope of the embodiments of this application. The order of the process numbers described above does not imply the order of execution; the execution order of each process should be determined by its function and internal logic.

Claims

1. A PIN management method, characterized in that, include: A personal IoT PIN network function network element receives a first request message, the first request message including the identification information of a first terminal device, the first request message being used to request the first terminal device to act as a PIN management network element; The PIN network function element sends a first query message to the unified data management element. The first query message includes the identification information of the first terminal device. The first query message is used to query whether the first terminal device is authorized to be used as a PIN management element. The PIN network function element receives a first query result from the unified data management element, wherein the first query result indicates that the first terminal device is authorized to be used as a PIN management element. The PIN network function element sends a first notification message to the first terminal device. The first notification message includes first indication information and PIN identification information. The first indication information indicates that the first terminal device is the PIN management network element within the PIN.

2. The method as described in claim 1, characterized in that, The first request message also includes the identification information of the PIN; or, The method further includes: the PIN network function element assigning identification information to the PIN.

3. The method as described in claim 1 or 2, characterized in that, Also includes: The PIN network function element sends the PIN identification information to the application function element.

4. The method according to any one of claims 1 to 3, characterized in that, The PIN network function element receives a first request message, including: The PIN network function element receives the first request message from the first terminal device; or... The PIN network function element receives the first request message from the application function element.

5. The method according to any one of claims 1 to 4, characterized in that, The PIN network function element receives a second request message, which includes the identification information of the second terminal device. The second request message is used to request the second terminal device to act as a PIN gateway element. The PIN network function element sends a second query message to the unified data management element. The second query message includes the identification information of the second terminal device. The second query message is used to query whether the second terminal device is authorized to be used as a PIN gateway element. The PIN network function element receives a second query result from the unified data management element, wherein the second query result indicates that the second terminal device is authorized to be used as a PIN gateway element. The PIN network function element sends a second notification message to the second terminal device. The second notification message includes second indication information, the identification information of the PIN management element, and the identification information of the PIN. The second indication information indicates that the second terminal device is a PIN gateway element within the PIN, and the identification information of the PIN management element is the identification information of the first terminal device.

6. The method as described in claim 5, characterized in that, The PIN network function element receives a second request message, including: The PIN network function element receives the second request message from the second terminal device, the application function element, or the first terminal device.

7. The method as described in claim 5 or 6, characterized in that, Also includes: The PIN network function element receives a first update message from the second terminal device. The first update message includes the identification information of the PIN gateway element and the identification information of the PIN. The identification information of the PIN gateway element is the identification information of the second terminal device. The PIN network function element updates the PIN information to obtain first PIN information, which includes the identification information of the PIN, the identification information of the PIN management element, and the identification information of the PIN gateway.

8. The method as described in claim 7, characterized in that, Also includes: The PIN network function element receives a second update message from the second terminal device. The second update message includes the identification information of the PIN, the identification information of the PINE, and the PINE number corresponding to the PINE. The identification information of the PINE is the identification information of the third terminal device. The PIN network function element updates the first PIN information to obtain the second PIN information, which includes the identification information of the PIN, the identification information of the PIN management element, the identification information of the PIN gateway, the identification information of the PINE, and the number of the PINE.

9. The method as described in claim 7, characterized in that, Also includes: The PIN network function element receives a third request message from a third terminal device. The third request message includes the identification information of the third terminal device, the identification information of the PIN, and a join request. The join request is used to request to join the PIN. The PIN network function element sends the identification information of the third terminal device and the joining request to the first terminal device through the second terminal device; The PIN network function element receives the identification information of the PINE and the PINE number corresponding to the PINE from the first terminal device through the second terminal device, wherein the identification information of the PINE is the identification information of the third terminal device; The PIN network function element updates the first PIN information to obtain the second PIN information, which includes the identification information of the PIN, the identification information of the PIN management element, the identification information of the PIN gateway, the identification information of the PINE, and the number of the PINE.

10. The method according to any one of claims 5 to 9, characterized in that, Also includes: The PIN network function element receives a fourth request message from the first terminal device. The fourth request message includes the identification information and management instructions of the PIN, and also includes the identification information of the fourth terminal device or the PINE number corresponding to the fourth terminal device. The PIN network function element sends the management command to the fourth terminal device through the second terminal device.

11. The method according to any one of claims 1 to 9, characterized in that, Also includes: The PIN network function element receives a fifth request message from a fifth terminal device, the fifth request message including the identification information of the PIN and the identification information of the fifth terminal device; The PIN network function element sends a third query message to the unified data management element. The third query message includes the identification information of the fifth terminal device. The third query message is used to query whether the fifth terminal device is authorized to be used as a PIN management element. The PIN network function element receives a third query result from the unified data management element, wherein the third query result indicates that the fifth terminal device is authorized to be used as a PIN management element. The PIN network function element sends a third instruction message and the identification information of the PIN to the fifth terminal device. The third instruction message instructs the fifth terminal device to act as the PIN management network element within the PIN.

12. The method as described in claim 11, characterized in that, Also includes: The PIN network function element sends a third notification message to the first terminal device. The third notification message includes fourth indication information and identification information of the fifth terminal device. The fourth indication information indicates that the fifth terminal device is the PIN management network element within the PIN.

13. A PIN management method, characterized in that, include: The first terminal device sends a first request message to the Personal Internet of Things PIN Network Function Network Element. The first request message includes the identification information of the first terminal device and is used to request the first terminal device to act as the PIN management network element. The first terminal device receives a first notification message from the PIN network function element. The first notification message includes first indication information and PIN identification information. The first indication information indicates that the first terminal device is a PIN management element within the PIN.

14. The method as described in claim 13, characterized in that, The first request message also includes the identification information of the PIN.

15. The method as described in claim 13 or 14, characterized in that, Also includes: The first terminal device receives a second request message from the second terminal device. The second request message includes the identification information of the second terminal device and the identification information of the PIN. The second request message is used to request the addition of the PIN. The first terminal device sends a response message to the second terminal device, the response message indicating whether to agree to allow the second terminal device to add the PIN, or to refuse the second terminal device to add the PIN.

16. The method according to any one of claims 13 to 15, characterized in that, Also includes: The first terminal device receives a third request message from a third terminal device. The third request message includes the identification information of the third terminal device and the identification information of the PIN. The third request message is used to request the addition of the PIN. The first terminal device assigns a PINE number to the third terminal device; The first terminal device sends the identification information of the PIN, the identification information of the PINE, and the PINE number to the PIN network function element, wherein the identification information of the PINE is the identification information of the third terminal device.

17. The method according to any one of claims 13 to 16, characterized in that, Also includes: The first terminal device sends a fourth request message to the PIN network function element. The fourth request message includes the identification information and management instructions of the PIN, and also includes the identification information of the fourth terminal device or the PINE number corresponding to the fourth terminal device.

18. The method according to any one of claims 13 to 17, characterized in that, Also includes: The first terminal device receives a second notification message from the PIN network function element. The second notification message includes second indication information and identification information of the fifth terminal device. The second indication information indicates that the fifth terminal device is the PIN management element within the PIN.

19. The method as described in claim 13 or 14, characterized in that, Also includes: The first terminal device sends a fifth request message to the PIN network function element. The fifth request message includes the identification information of the first terminal device and the identification information of the PIN. The fifth request message is used to request the first terminal device to act as a PIN gateway element. The first terminal device receives third indication information from the PIN network function element, the third indication information indicating that the first terminal device is a PIN gateway element within the PIN.

20. The method as described in claim 13 or 14, characterized in that, Also includes: The first indication information is also used to indicate that the first terminal device is a PIN gateway network element within the PIN.

21. The method according to any one of claims 13 to 20, characterized in that, Also includes: The first terminal device sends a sixth request message to the PIN network function element. The sixth request message includes the identification information of the sixth terminal device and is used to request the sixth terminal device to act as a PIN gateway element. The first terminal device receives a third notification message from the PIN network function element. The third notification message includes fourth indication information and the identification information of the PIN. The fourth indication information indicates that the sixth terminal device is the PIN gateway element within the PIN.

22. A PIN management method, characterized in that, include: The first terminal device sends a first request message to the Personal Internet of Things PIN Network Function Network Element. The first request message includes the identification information of the first terminal device and is used to request the first terminal device to act as a PIN gateway network element. The first terminal device receives a first notification message from the PIN network function element. The first notification message includes indication information and PIN identification information. The indication information indicates that the first terminal device is a PIN gateway element within the PIN. The first terminal device sends a second request message to the PIN management network element. The second request message includes the identification information of the first terminal device and the identification information of the PIN. The second request message is used to request to add the PIN. The first terminal device receives a response message from the PIN management network element, the response message indicating whether to agree to allow the first terminal device to join the PIN, or to refuse the first terminal device to join the PIN.

23. The method as described in claim 22, characterized in that, Also includes: When the response message indicates that the first terminal device is allowed to join the PIN, the first terminal device sends an update message to the PIN network function element. The update message includes the identification information of the PIN gateway element and the identification information of the PIN. The identification information of the PIN gateway element is the identification information of the first terminal device.

24. The method as described in claim 22 or 23, characterized in that, Also includes: The first terminal device receives a third request message, which includes a PINE number and management instructions; The first terminal device sends the management command to the terminal device corresponding to the PINE number.

25. The method according to any one of claims 22 to 24, characterized in that, Also includes: The first terminal device receives a fourth request message, which includes the identification information of the second terminal device and a join request, wherein the join request is used to request the addition of the PIN; The first terminal device sends a fifth request message to the PIN management network element. The fifth request message includes the identification information of the second terminal device and the joining request.

26. A communication device, characterized in that, include: Processor and memory; The memory is used to store computer instructions. When the communication device is running, the processor executes the computer instructions stored in the memory to cause the communication device to perform the method as described in any one of claims 1 to 12, or the method as described in any one of claims 13 to 21, or the method as described in any one of claims 22 to 25.

27. A communication device, characterized in that, The device includes a processor and an interface circuit. The interface circuit is used to receive signals from other communication devices besides the communication device and transmit them to the processor, or to send signals from the processor to other communication devices besides the communication device. The processor is used to implement the method as described in any one of claims 1 to 12, or the method as described in any one of claims 13 to 21, or the method as described in any one of claims 22 to 25, through logic circuits or execution code instructions.

28. A communication system, characterized in that, It includes a unified data management network element and a PIN network function network element for performing the method as described in any one of claims 1 to 12; The unified data management network element is used to receive a first query message from the PIN network function network element. The first query message includes the identification information of the first terminal device. The first query message is used to query whether the first terminal device is authorized to be used as a PIN management network element. Send a first query result to the PIN network function element, wherein the first query result indicates that the first terminal device is authorized to be used as a PIN management network element.

29. A computer program product, characterized in that, Includes a computer program that, when executed by a communication device, implements the method as described in any one of claims 1 to 25.

30. A computer-readable storage medium, characterized in that, The storage medium stores a computer program or instructions, which, when executed by a communication device, implement the method as described in any one of claims 1 to 25.

Images