Method and apparatus for forming a pin

Abstract

The embodiment of the application discloses a PIN construction method and device, and belongs to the communication technical field.The PIN construction method comprises the following steps: a terminal sends network group request information to a PIN server, wherein the network group request information is used for requesting to construct a PIN; the terminal receives network group response information from the PIN server, wherein the network group response information comprises construction success information or construction failure information, the construction success information indicates that the PIN is successfully constructed, and the construction failure information indicates that the PIN fails to be constructed.

Description

Technical Field

[0001] This application belongs to the field of communication technology, specifically relating to a method and device for constructing a Personal IoT Network (PIN). Background Technology

[0002] Various devices exist in settings such as homes and offices. These devices include wearable devices (such as cameras, headphones, watches, and health monitors) and IoT devices (such as smart lights, cameras, thermostats, door sensors, voice assistants, speakers, refrigerators, and washing machines). Multiple devices can form a PIN (Connecting Point) to enable interconnection, communication, and service access. However, current technologies lack specific solutions for establishing PINs, making it difficult to meet the communication needs between devices. Summary of the Invention

[0003] This application provides a method and apparatus for constructing a PIN, which can solve the problem in related technologies where the inability to construct a PIN prevents the fulfillment of communication requirements between devices.

[0004] In a first aspect, a method for constructing a PIN is provided, comprising: a terminal sending a network request message to a PIN server, the network request message being used to request the construction of a PIN; the terminal receiving a network response message from the PIN server, the network response message including a successful construction message or a failed construction message, the successful construction message indicating that the PIN was successfully constructed, and the failed construction message indicating that the PIN was failed to be constructed.

[0005] Secondly, a method for constructing a PIN is provided, comprising: a PIN server receiving network request information from a terminal, the network request information being used to request the construction of a PIN; the PIN server sending network response information to the terminal, the network response information including successful construction information or failed construction information, the successful construction information indicating that the PIN was successfully constructed, and the failed construction information indicating that the PIN was failed to be constructed.

[0006] Thirdly, a method for constructing a PIN is provided, comprising: a terminal establishing a communication connection with a PEMC via a non-3GPP access method; the terminal sending a first registration request message to the PEMC, the first registration request message being used to request to become the PEGC in the PIN; the terminal receiving a first registration response message from the PEMC, the first registration response message including registration success information or registration failure information, the registration success information indicating that the first registration request message has been verified successfully, and the registration failure information indicating that the first registration request message has failed to be verified.

[0007] Fourthly, a method for constructing a PIN is provided, comprising: a terminal establishing a communication connection with a PEMC via a non-3GPP access method; the terminal sending a second registration request to the PEMC, the second registration request being used to request to become a PIN network element in the PIN; the terminal receiving a second registration response from the PEMC, the second registration response including registration success information or registration failure information, the registration success information indicating that the second registration request has been verified, and the registration failure information indicating that the second registration request has failed to be verified.

[0008] Fifthly, a PIN creation apparatus is provided, comprising: a sending module for sending network creation request information to a PIN server, the network creation request information being used to request the creation of a PIN; and a receiving module for receiving network creation response information from the PIN server, the network creation response information including successful creation information or failed creation information, the successful creation information indicating that the PIN was successfully created, and the failed creation information indicating that the PIN was failed to be created.

[0009] Sixthly, a PIN creation apparatus is provided, comprising: a receiving module for receiving network creation request information from a terminal, the network creation request information being used to request the creation of a PIN; and a sending module for sending network creation response information to the terminal, the network creation response information including successful creation information or failed creation information, the successful creation information indicating that the PIN was successfully created, and the failed creation information indicating that the PIN was failed to be created.

[0010] In a seventh aspect, a PIN assembly apparatus is provided, comprising: a communication establishment module for establishing a communication connection with a PEMC via a non-3GPP access method; a sending module for sending first registration request information to the PEMC, the first registration request information being used to request to become a PEGC in the PIN; and a receiving module for receiving first registration response information from the PEMC, the first registration response information including registration success information or registration failure information, the registration success information indicating that the first registration request information has been verified successfully, and the registration failure information indicating that the first registration request information has failed to be verified.

[0011] Eighthly, a PIN assembly apparatus is provided, comprising: a communication establishment module for establishing a communication connection with a PEMC via a non-3GPP access method; a sending module for sending second registration request information to the PEMC, the second registration request information being used to request to become a PIN network element in a PIN; and a receiving module for receiving second registration response information from the PEMC, the second registration response information including registration success information or registration failure information, the registration success information indicating that the second registration request information has been verified successfully, and the registration failure information indicating that the second registration request information has failed to be verified.

[0012] A ninth aspect provides a terminal including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the methods described in the first, third, or fourth aspects.

[0013] In a tenth aspect, a terminal is provided, including a processor and a communication interface, wherein the communication interface is used to implement the steps of the method described in the first, third, or fourth aspects.

[0014] Eleventhly, a network-side device is provided, the network-side device including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as described in the second aspect.

[0015] In a twelfth aspect, a network-side device is provided, including a processor and a communication interface, wherein the communication interface is used to implement the steps of the method described in the second aspect.

[0016] In a thirteenth aspect, a PIN assembly system is provided, comprising: a terminal and a network-side device, wherein the terminal is configured to perform the steps of the method described in the first, third, or fourth aspect, and the network-side device is configured to perform the steps of the method described in the second aspect.

[0017] In a fourteenth aspect, a readable storage medium is provided, on which a program or instructions are stored, which, when executed by a processor, implement the steps of the method as described in the first, second, third, or fourth aspect.

[0018] In a fifteenth aspect, a chip is provided, the chip including a processor and a communication interface coupled to the processor, the processor being configured to run programs or instructions to implement the steps of the methods described in the first, second, third, or fourth aspects.

[0019] In a sixteenth aspect, a computer program / program product is provided, the computer program / program product being stored in a storage medium, the computer program / program product being executed by at least one processor to implement the steps of the method as described in the first aspect, second aspect, third aspect, or fourth aspect.

[0020] In this embodiment, the terminal sends a network creation request to the PIN server, which requests the creation of a PIN. The terminal receives a network creation response, which includes information indicating successful or failed PIN creation. In other words, the PIN server can approve or disapprove the terminal's network creation request after verifying the network creation request. This embodiment enables the terminal to create a PIN, which facilitates communication between devices via PINs. Attached Figure Description

[0021] Figure 1 This is a schematic diagram of a wireless communication system according to an embodiment of this application;

[0022] Figure 2 This is a schematic flowchart of a PIN assembly method according to an embodiment of this application;

[0023] Figure 3 This is a schematic flowchart of a PIN assembly method according to an embodiment of this application;

[0024] Figure 4 This is a schematic flowchart of a PIN assembly method according to an embodiment of this application;

[0025] Figure 5 This is a schematic flowchart of a PIN assembly method according to an embodiment of this application;

[0026] Figure 6 This is a schematic flowchart of a PIN assembly method according to an embodiment of this application;

[0027] Figure 7 This is a schematic flowchart of a PIN assembly method according to an embodiment of this application;

[0028] Figure 8 This is a schematic flowchart of a PIN assembly method according to an embodiment of this application;

[0029] Figure 9 This is a schematic flowchart of a PIN assembly method according to an embodiment of this application;

[0030] Figure 10 This is a schematic flowchart of a PIN assembly method according to an embodiment of this application;

[0031] Figure 11 This is a schematic diagram of the structure of a PIN assembly apparatus according to an embodiment of this application;

[0032] Figure 12 This is a schematic diagram of the structure of a PIN assembly apparatus according to an embodiment of this application;

[0033] Figure 13 This is a schematic diagram of the structure of a PIN assembly apparatus according to an embodiment of this application;

[0034] Figure 14 This is a schematic diagram of the structure of a PIN assembly apparatus according to an embodiment of this application;

[0035] Figure 15 This is a schematic diagram of the structure of a communication device according to an embodiment of this application;

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

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

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

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

[0040] It is worth noting that the technologies described in this application are not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency Division Multiple Access (SC-FDMA), and other systems. The terms "system" and "network" in this application are often used interchangeably, and the described technologies can be used with the systems and radio technologies mentioned above, as well as with other systems and radio technologies. The following description describes New Radio (NR) systems for illustrative purposes, and NR terminology is used in most of the following description; however, these technologies can also be applied to applications beyond NR systems, such as 6th generation (6G) radio systems. th Generation 6G communication system.

[0041] Figure 1This diagram illustrates a block diagram of a wireless communication system applicable to embodiments of this application. The wireless communication system includes a terminal 11 and a network-side device 12. Terminal 11 can be a mobile phone, tablet computer, laptop computer, personal digital assistant (PDA), handheld computer, netbook, ultra-mobile personal computer (UMPC), mobile internet device (MID), augmented reality (AR) / virtual reality (VR) device, robot, wearable device, vehicle-mounted device (VUE), pedestrian terminal (PUE), smart home (home devices with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), game console, personal computer (PC), ATM, or self-service machine, etc. Wearable devices include: smartwatches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart chains, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. It should be noted that the specific type of terminal 11 is not limited in this embodiment. Network-side equipment 12 may include access network equipment or core network equipment. Access network equipment may also be referred to as radio access network equipment, radio access network (RAN), radio access network function, or radio access network unit. Access network equipment may include base stations, WLAN access points, or WiFi nodes, etc. Base stations may be referred to as Node B, evolved Node B (eNB), access point, base transceiver station (BTS), radio base station, radio transceiver, Basic Service Set (BSS), Extended Service Set (ESS), home B node, home evolved B node, Transmitting Receiving Point (TRP), or any other suitable term in the field, as long as the same technical effect is achieved. The base station is not limited to specific technical terms. It should be noted that in this embodiment, only a base station in an NR system is used as an example for description, and the specific type of base station is not limited.Core network equipment may include, but is not limited to, at least one of the following: core network node, core network function, Mobility Management Entity (MME), Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Policy Control Function (PCF), Policy and Charging Rules Function (PCRF), Edge Application Server Discovery Function (EASDF), Unified Data Management (UDM), Unified Data Repository (UDR), Home Subscriber Server (HSS), Centralized network configuration (CNC), Network Repository Function (NRF), Network Exposure Function (NEF), Local NEF (or L-NEF), Binding Support Function (BSF), and Application Function. Function (AF), etc. It should be noted that the embodiments of this application only use the core network equipment in the NR system as an example for introduction, and do not limit the specific type of core network equipment.

[0042] The method for constructing a PIN provided in this application will be described in detail below with reference to the accompanying drawings and through some embodiments and application scenarios.

[0043] like Figure 2 As shown in the figure, this application embodiment provides a PIN assembly method 200, which can be executed by a terminal. In other words, the method can be executed by software or hardware installed on the terminal, and the method includes the following steps.

[0044] S202: The terminal sends a network request message to the PIN server, the network request message being used to request the formation of a PIN.

[0045] S204: The terminal receives network response information from the PIN server. The network response information includes successful network setup information or failed network setup information. The successful network setup information indicates that the PIN setup was successful, and the failed network setup information indicates that the PIN setup failed.

[0046] In this embodiment, the terminal can be a Personal Internet of Things (PIN) element with management capability (PEMC), specifically an enabler layer on the PEMC, such as an application (APP) or an enabler client on the PEMC. Before this embodiment is executed, the terminal has already signed up with an operator and become a user of the operator; it has obtained the identity of the PEMC; and it has also obtained the IP address of the PIN server. In one implementation, a network request can only be triggered after obtaining the identity of the PEMC.

[0047] Optionally, prior to S202, the method further includes the following steps: the terminal sends a subscription request to the PIN server, the subscription request request requesting at least one of the following: becoming a PEMC; registering or subscribing to an operator's network; the terminal receives subscription success information from the PIN server, the subscription success information indicating that the terminal has become a PEMC and can be assigned a new PEMC ID. Subscription failure indicates that the PEMC failed to register and subscribe successfully, and has not obtained the PEMC role. Simultaneously, the PIN server must indicate the reason for this subscription failure.

[0048] Optionally, the aforementioned subscription request information includes at least one of the following: a) the application ID on the PEMC, which, if the terminal is a PEMC, is the same as the application ID on the terminal; b) the terminal's Subscription Permanent Identifier (SUPI); c) the terminal's Generic Public Subscription Identifier (GPSI); e) the terminal's IP address; f) the PEMC client IP address, which, if the terminal is a PEMC, is the same as the terminal's client IP address; g) a security certificate.

[0049] The PIN creation method provided in this application embodiment involves a terminal sending a network creation request to a PIN server. This request requests the creation of a PIN. The terminal receives a network creation response, which includes either successful or failed creation information. In other words, the PIN server can approve or disapprove the terminal's network creation request after verifying the request. This application embodiment enables terminals to create PINs, facilitating communication between devices through PINs. The failed creation information indicates that the network creation request was not approved, and the PIN server can indicate the reason for the failure.

[0050] Furthermore, the embodiments of this application can also solve the following technical problem: Since different IoT devices are developed by different manufacturers, have different access methods, and different design structures, there is currently no unified architecture and process that allows devices from multiple manufacturers to form PINs. The embodiments of this application enable different IoT devices to form PINs, which is beneficial for meeting the communication needs between devices through PINs.

[0051] Based on embodiment 200, optionally, the network request information may include at least one of the following 1) to 6):

[0052] 1) The lifecycle information of the PIN, which indicates the time during which the PIN is active or exists.

[0053] 2) The terminal-related identification information. Optionally, the terminal-related identification information includes at least one of the following: a) the PEMC ID in the PIN, where the PEMC ID is the terminal ID if the terminal is a PEMC; b) the terminal's enable layer ID; c) the terminal's SUPI; d) the terminal's GPSI; e) the application ID on the PEMC in the PIN, where the application ID on the PEMC is the terminal's application ID if the terminal is a PEMC; f) the enabled client ID of the PEMC in the PIN, where the enabled client ID of the PEMC is the terminal's enabled client ID if the terminal is a PEMC.

[0054] 3) The IP address or port number of the terminal.

[0055] 4) Information about the PIN element that the terminal wishes to add to the PIN. The PIN element may be a terminal. Optionally, the information of the PIN element includes at least one of the following: the ID of the PIN element, the enable layer ID of the PIN element, the terminal ID of the PIN element, the application ID on the PEMC in the PIN, the IP address of the PIN element, and the enable layer IP address of the PIN element.

[0056] It is understandable that when the terminal is a PEMC, the PEMC may have already determined some PIN network elements before PIN formation, so the network formation request information may include information about these PIN network elements. In other embodiments, the PIN network elements in the PIN may be added after PIN formation, therefore, the network formation request information may not include the information about the PIN network elements.

[0057] 5) Information of the Personal Internet of Things element with Gateway Capability (PEGC) in the PIN. The PEGC may be a terminal. The PEGC is a PIN element with gateway capability, primarily acting as a gateway for interaction between the PIN and the user plane of the target network system (such as a 5G system). Optionally, the information of the PEGC includes at least one of the following: the PEGC ID, the PEGC enable layer ID, the PEGC terminal ID, the PEGC application ID, and the PEGC IP address.

[0058] It is understood that when the terminal is a PEMC, the PEMC may have already determined the PEGC in the PIN before PIN formation, therefore the network formation request information may include the PEGC information. In other embodiments, the PEGC in the PIN may be determined after PIN formation, therefore the network formation request information may not include the PEGC information. Optionally, the PEMC and PEGC in the PIN may be the same terminal.

[0059] 6) Security certificate.

[0060] In the preceding embodiments, the successful assembly information includes at least one of the following:

[0061] 1) The ID of the PIN. That is, after the PIN is successfully formed, each PIN has an identifier assigned by the network side.

[0062] 2) Information about the PEGC in the PIN.

[0063] 3) The PIN contains access control information configured in the PEGC. This access control information controls whether the PIN network element in the PIN can access or connect to the target network, which can be a 5G network. Optionally, the access control information includes at least one of the following: username, account, password, Service Set Identifier (SSID), and Basic Service Set Identifier (BSSID). The PIN element can access the target network via Wi-Fi (e.g., via SSID) using the user plane, account, password, etc., assigned by the network side. The target network can be a 5G network or the Internet.

[0064] 4) The routing information configured in the PIN to the PEGC is used by the PEGC or the PIN network element in the PIN to access a target network, which may be a 5G network. Optionally, the routing information includes at least one of the following: the IP address of the User Plane Function (UPF), the port number of the UPF, the Fully Qualified Domain Name (FQDN) of the UPF, and the data network (DN) connected through the UPF; wherein the PEGC accesses the target network through the UPF, and the target network may be a 5G network.

[0065] The preceding embodiments mainly introduced how the terminal constructs the PIN. The following will introduce how the terminal determines the PEGC in the PIN.

[0066] There are several ways for a terminal (such as a PEMC) to add a PEGC to a PIN: One method is that the PEGC has a direct connection to the PEMC, such as a wired or wireless connection. In this case, after communication between the two parties, the PEGC can interact with the PEMC and register on the PEMC, allowing the PEMC to set it as the PIN's gateway. Another method is that after the PEGC powers on, it directly interacts with the PIN server to register, thereby obtaining a gateway role from the operator. Then, when the PEMC triggers a PIN networking request, the PIN server assigns the PEGC as the gateway to the networking request or the PIN. In this way, the PEMC obtains the gateway's IP address, and during the communication process, the PEGC registers with the PEMC, with both parties using the same PIN.

[0067] Optionally, the terminal determines the PEGC in the PIN by at least one of the following methods:

[0068] 1) The PEGC is signed or registered to the terminal. In this example, the terminal can be a PEMC, and the PEGC in the PIN can be determined through the signing or registration process between the PEGC and the PEMC.

[0069] 2) The successful assembly information includes PEGC information. In this example, the PIN server can specify the PEGC in the PIN.

[0070] 3) The PIN network element managed by the terminal accesses the target network through the PEGC in the determined PIN. In this example, the PIN network element can access the target network through a certain PEGC, and the terminal, such as PEMC, can designate this PEGC as the PEGC in the PIN.

[0071] In one embodiment, when the PEGC is signed up or registered with the terminal, the method further includes the following steps: 1) The terminal and the PEGC establish a communication connection through a non-3GPP access method, such as establishing a communication connection through a hotspot direct connection; 2) The terminal receives a first registration request information from the PEGC; 3) The terminal verifies the first registration request information and sends a first registration response information, the first registration response information including registration success information or registration failure information, the registration success information indicating that the first registration request information has been verified successfully, and the registration failure information indicating that the first registration request information has failed to be verified. If the first registration request information verification fails, it means that the PEGC has failed to register and sign up successfully. The terminal (or PEGC) must also indicate the reason for this registration failure.

[0072] Optionally, the first registration request information includes at least one of the following: the ID of the PEGC, the enable layer ID of the PEGC, the terminal ID, the application ID on the PEGC, the IP address of the PEGC, the security certificate, access control information, and routing information.

[0073] Optionally, the first registration response information includes at least one of the following: registration ID, registration termination time information, and the context ID of the PEGC.

[0074] The preceding embodiments mainly introduced how the terminal constructs the PIN and how the terminal determines the PEGC in the PIN. The following will introduce how the terminal adds PIN network elements to the PIN.

[0075] Once the PIN is successfully created, it will contain both the PEMC and PEGC. At this point, other IoT devices may want to join the PIN. There are two methods to add IoT devices to the PIN. One method is for the PEMC to open its own hotspot. The PIN network element can then access this hotspot and register with the PEMC. The PEMC can then add the device to a PIN as a member. Another method is for the PIN network element itself to be a terminal. In this case, the PIN network element can also open its own hotspot for the PEMC to access. After interaction between the PEMC and the PIN network element, since each PIN network element has a different hotspot (e.g., SSID), the PEMC can distinguish between the different PIN network elements and ultimately add these PIN network elements to the PIN as members.

[0076] Optionally, the foregoing embodiments further include the following step: the terminal adds a PIN network element to the PIN.

[0077] The terminal adds a PIN network element to the PIN by: 1) the terminal and the PIN network element establishing a communication connection through a non-3GPP access method, such as establishing a communication connection through a hotspot direct connection; 2) the terminal receiving a second registration request information from the PIN network element; 3) the terminal adding the PIN network element to the PIN if the second registration request is verified; and 4) the terminal sending a second registration response information.

[0078] Optionally, the second registration request information includes at least one of the following: the ID of the PIN network element, the enable layer ID of the PIN network element, the ID of the application on the PIN network element, the IP address of the PIN network element, and a security certificate.

[0079] Optionally, the second registration response information includes at least one of the following: registration ID, registration termination time information, the context ID of the PIN network element, and the ID of the PIN. If the second registration request verification fails, the terminal must provide the reason for the registration failure.

[0080] When a PIN network element is added to the terminal, the method further includes: the terminal determining the permissions of the PIN network element; these permissions include, for example, whether it can access 5G via PEGC, and whether it can access other service servers via the 5G network. The second registration response information further includes at least one of the following:

[0081] 1) The IP address of the PEGC in the PIN.

[0082] 2) The port number of the PEGC in the PIN.

[0083] 3) The access permissions of the PIN network element, including whether the PIN network element supports accessing the target network through the PEGC in the PIN, and the target network may be a 5G network.

[0084] Optionally, the access permission of the PIN network element is obtained by the terminal from the PIN server, or determined by the terminal based on the PEGC registration information. For example, the PIN network element can access the target network via PEGC using the username, account, password, Service Set Identifier (SSID), Basic Service Set Identifier (BSSID), etc., issued by the PEMC.

[0085] The above combination Figure 2 The method for constructing a PIN according to embodiments of this application is described in detail below. Figure 3 A method for constructing a PIN according to another embodiment of this application is described in detail. It will be understood that the description from the PIN server side is different from... Figure 2 The terminal-side descriptions in the methods shown are the same or corresponding; to avoid repetition, relevant descriptions are omitted as appropriate.

[0086] Figure 3 This is a schematic diagram illustrating the implementation flow of a PIN creation method according to an embodiment of this application, which can be applied to the PIN server side. For example... Figure 3 As shown, the method 300 includes the following steps.

[0087] S302: The PIN server receives a network formation request from a terminal, the network formation request being used to request the formation of a PIN. The PIN server is used to verify or approve the PIN network formation request.

[0088] S304: The PIN server sends a network formation response message to the terminal. The network formation response message includes a successful formation message or a failed formation message. The successful formation message indicates that the PIN has been successfully formed, and the failed formation message indicates that the PIN has failed to be formed.

[0089] The PIN creation method provided in this application embodiment involves a PIN server receiving a network creation request, which requests the creation of a PIN. The PIN server then sends a network creation response to the terminal, including either successful or failed creation information. In other words, the PIN server can approve or disapprove the terminal's network creation request after verifying the network creation request. This application embodiment enables terminals to create PINs, facilitating communication between devices through PINs. The failed creation information indicates that the network creation request was not approved, and the PIN server can indicate the reason for the failure.

[0090] Optionally, as an embodiment, the network request information includes at least one of the following: 1) the lifecycle information of the PIN, which indicates the time when the PIN is effective or exists; 2) the identification information related to the terminal; 3) the IP address or port number of the terminal; 4) the information of the PIN network element that the terminal wishes to add to the PIN; 5) the PEGC information in the PIN; 6) the security certificate.

[0091] Optionally, as an embodiment, the terminal-related identification information includes at least one of the following: the PEMC ID in the PIN, the enable layer ID of the terminal, the SUPI of the terminal, the GPSI of the terminal, the application ID on the PEMC in the PIN, and the enable client ID of the PEMC.

[0092] Optionally, as an embodiment, the information of the PIN network element includes at least one of the following: the ID of the PIN network element, the enable layer ID of the PIN network element, the terminal ID of the PIN network element, the application ID on the PEMC in the PIN, the IP address of the PIN network element, and the enable layer IP address of the PIN network element.

[0093] Optionally, as an embodiment, the information of the PEGC includes at least one of the following: the ID of the PEGC, the enable layer ID of the PEGC, the terminal ID of the PEGC, the application ID on the PEGC, and the IP address of the PEGC.

[0094] Optionally, as an embodiment, the successful assembly information includes at least one of the following: 1) the identifier ID of the PIN; 2) the PEGC information in the PIN; 3) the access control information configured to the PEGC in the PIN, the access control information being used to control whether the PIN network element in the PIN can access or connect to the target network; 4) the routing information configured to the PEGC in the PIN, the routing information being used by the PEGC or the PIN network element in the PIN to access the target network.

[0095] Optionally, as an embodiment, the access control information includes at least one of the following: username, account, password, SSID, BSSID, and / or the routing information includes at least one of the following: the IP address of the UPF, the port number of the UPF, the FQDN of the UPF, and the DN data network connected through the UPF; wherein, the PEGC accesses the target network by accessing the UPF.

[0096] Optionally, as an embodiment, the method further includes: the PIN server sending the PEGC information in the PIN to the terminal.

[0097] Figure 4 This is a schematic diagram illustrating the implementation flow of the PIN assembly method according to an embodiment of this application, which can be applied to a terminal such as a PEGC side. Figure 4 As shown, the method 400 includes the following steps.

[0098] S402: The terminal establishes a communication connection with the PEMC through a non-3GPP access method.

[0099] S404: The terminal sends a first registration request to the PEMC, the first registration request being used to request to become the PEGC in the PIN.

[0100] S406: The terminal receives first registration response information from the PEMC. The first registration response information includes registration success information or registration failure information. The registration success information indicates that the first registration request information has been verified successfully, and the registration failure information indicates that the first registration request information has failed to be verified. The verification failure indicates that the registration request has not been approved, and the PEMC can indicate the reason for this registration failure.

[0101] The PIN construction method provided in this application embodiment allows the terminal to apply to become the PEGC in the PIN. The PEGC enables the PIN network element in the PIN to access the 5G network or access other service servers via the 5G network, which is beneficial for meeting the communication needs of the device through the PIN.

[0102] Optionally, as an embodiment, the first registration request information includes at least one of the following: the terminal's ID, the terminal's enable layer ID, the application ID on the terminal, the terminal's IP address, security certificate, access control information, routing information, and / or, the first registration response information includes at least one of the following: registration ID, registration termination time information, and the terminal's context ID.

[0103] Figure 5 This is a schematic diagram illustrating the implementation flow of the PIN assembly method according to an embodiment of this application, which can be applied to a terminal such as a PIN network element. Figure 4 As shown, the method 500 includes the following steps.

[0104] S502: The terminal establishes a communication connection with the PEMC through a non-3GPP access method.

[0105] S504: The terminal sends a second registration request to the PEMC, the second registration request being used to request to become a PIN network element in the PIN.

[0106] S506: The terminal receives a second registration response message from the PEMC. The second registration response message includes registration success information or registration failure information. The registration success information indicates that the second registration request information has been verified successfully, and the registration failure information indicates that the second registration request information has failed to be verified. The verification failure indicates that the registration request has not been approved, and the PEMC can indicate the reason for this registration failure.

[0107] The PIN construction method provided in this application embodiment allows a terminal to apply to become a PIN network element in the PIN. This PIN network element can access the 5G network or other service servers via the 5G network through the PEGC in the PIN, which is beneficial for meeting communication needs.

[0108] Optionally, as an embodiment, the second registration request information includes at least one of the following: the terminal's ID, the terminal's enable layer ID, the application ID on the terminal, the terminal's IP address, a security certificate, and / or, the second registration response information includes at least one of the following: a registration ID, registration termination time information, the terminal's context ID, and the terminal's ID.

[0109] Optionally, as an embodiment, the second registration response information further includes at least one of the following: 1) the IP address of the PEGC in the PIN; 2) the port number of the PEGC in the PIN; 3) the access permission of the terminal, wherein the access permission includes whether the terminal supports accessing the target network through the PEGC in the PIN.

[0110] To illustrate in detail the PIN construction method provided in the embodiments of this application, the following will describe it in conjunction with several specific embodiments.

[0111] Example 1

[0112] This example will illustrate how a PEMC signs contracts with operators, such as... Figure 6 As shown, this embodiment includes the following steps.

[0113] Step 1: A terminal (UE), or the PEMC enabler on the UE, or a client on the UE, triggers a subscription request to the PIN server. The PIN server is controlled by the operator. This subscription request is used to request to become a PEMC, that is, a PIN network element with management capabilities.

[0114] The signing request may include at least one of the following: PEMC client ID, SUPI or GPSI, UE IP address, PEMC client IP address, security credentials, etc.

[0115] The UE or PEMC enabler typically needs to know the PIN server's IP address in advance. This process can also be understood as the PIN client registering with the PIN server.

[0116] Step 2: After receiving the signing request, the PIN server verifies the request and the security certificate. This ensures that the signing request originates from a legitimate device and verifies its validity.

[0117] Step 3: The PIN server sends a success or failure response to the UE.

[0118] If the response is successful, it means that the PEMC has successfully registered and signed the agreement, and has become a PEMC member.

[0119] If the response is a failure, it means that the PEMC failed to register and sign up successfully, and did not obtain the PEMC role. The PIN server should also indicate the reason for the signing failure.

[0120] Example 2

[0121] This example will describe the network request triggered by the PEMC. At this point, a certain UE has already signed up with a carrier and obtained the PEMC's identity; it has also obtained the IP address of the PIN server. For example... Figure 7 As shown, this embodiment includes the following steps.

[0122] Step 1: The terminal, or PEMC or PEMC enabler, sends a network request to the PIN server to establish a PIN.

[0123] The network configuration request here may include the following:

[0124] 1) Safety credentials.

[0125] 2) PIN lifecycle information, which indicates the duration of the PIN's validity or existence.

[0126] 3) Also includes the PEMC ID, PEMC enabler ID, UE ID, the application ID on the PEMC, and the current PEMC's own IP address.

[0127] 4) It may also include other information that the PEMC wants to add to this PIN network, such as: PIN element ID, PINE enabler ID, UE ID (SUPI, etc.), application ID on the PEMC, and IP address of the PIN element or PINE enabler.

[0128] 5) It may also include information about PEGCs that have been registered with PEMC, such as: PEGC ID, PEGC enablerID, UE ID, application ID on the PEGC, and the current IP address of the PEGC itself.

[0129] In other words, when a PEMC triggers a networking request, it may not have a PIN member, or it may already have a PIN member, such as a PEGC or PIN element.

[0130] Step 2: After receiving this networking request, the PIN server verifies the request and the security certificate. This ensures that the networking request comes from a legitimate device and verifies its validity.

[0131] Step 3: The PIN server sends a success or failure response to the PEMC.

[0132] If the response is successful, it means the network setup was successful.

[0133] The PIN server issues the PIN ID.

[0134] The PIN server sends PEGC information to the PEMC, including the PEGC ID, PEMC enabler ID, UE ID, application ID on the PEMC, and the current PEMC's IP address and port number.

[0135] At the same time, the PIN server also sends relevant access control information and routing information to PEGC.

[0136] The aforementioned access control information includes: username, account, password, SSID, BSSID, etc., of those who can access or communicate with 5G.

[0137] The aforementioned routing information includes the routing information used to access 5G. For example, if PEGC needs to access the UPF user plane to access 5G, it includes the UPF's IP address, port number, etc.

[0138] If the response is negative, it means the network request was not approved. The PIN server should also indicate the reason for the network failure.

[0139] Example 3

[0140] This embodiment will describe how to add PEGC to a PIN, and will be described in two sub-embodiments below.

[0141] Example 3-1: Direct connection method.

[0142] In this embodiment, the PEGC can be directly connected to the PEMC, for example, via wired or wireless means. For instance, in a wireless connection: the PEMC provides a Wi-Fi hotspot, and the PEGC connects to the Wi-Fi, verifies its username, account, and password, and then signs up or registers with the PEMC. Alternatively, the PEGC also provides a Wi-Fi hotspot, and the PEMC selects which PEGC to use. Figure 8 As shown, this embodiment includes the following steps.

[0143] This embodiment describes the process of registering PEGC to PEMC, provided that PEGC and PEMC have already established communication and interaction.

[0144] Step 1: The PEGC or PEGC enabler initiates a first registration request to the PEMC. The first registration request may include at least one of the following: PEGC ID, PEGC enabler ID, UE ID, the ID of the application on the PEGC, and the current PEGC's own IP address and security certificate.

[0145] Step 2: After receiving the first registration request, PEMC verifies the request and the security certificate. This ensures that the first registration request comes from a legitimate device and verifies its validity.

[0146] Step 3: PEMC sends the first registration response to PEGC.

[0147] If registration is successful, PEMC sends to PEGC: registration ID, expiration time (i.e., when this registration expires), and PEGC context ID.

[0148] If registration fails, provide the reason for the failure.

[0149] Example 3-2: Using a PIN server.

[0150] In this method, the PEGC registers with the PIN server, which can also be called PEGC signing up with the PIN server. Then, when a PEMC triggers a network request, the PIN server creates a PIN and specifies the PEGC. This process can be described in Example 2, which is similar to the process of a terminal or PEMC registering with the PIN server, and will not be elaborated here.

[0151] Example 4

[0152] This embodiment will show how to add a PIN network element to a PIN, which will be described in two sub-embodiments below.

[0153] Example 4-1: PIN element as a hotspot. For example... Figure 9 As shown, this embodiment includes the following steps.

[0154] Step 1: The PIN element can be used to turn on the hotspot.

[0155] Step 2: The PEMC communicates with the PIN element through the PIN element's hotspot. Since the PIN elements are different at this point, and their hotspots are also different, the PEMC can distinguish them from each other.

[0156] Step 3: Register the PIN element or PIN element enabler to the PEMC and send a second registration request.

[0157] The second registration request includes: PIN element enabler ID, PIN element ID, UE ID, the application ID on the PIN element, the current PIN element's own IP address, and the security certificate.

[0158] Step 4: If registration is successful, PEMC sends a second registration response to the PIN element, which may include the following: registration ID, expiration time (i.e., when this registration expires), and PIN element context ID.

[0159] In this embodiment, PEMC can also determine the permissions of the PIN element, and the second registration response can also include the IP address, port number, and access permissions of PEMC.

[0160] The access permission refers to the permission to access the 5G network, which may include the following access control information and routing information.

[0161] Access control information includes: username, account, password, SSID, BSSID, etc., of those who can access or communicate with 5G.

[0162] The routing information includes: the PEGC's IP address and port number. This is because the PIN element needs to access the 5G network or a public server through a gateway.

[0163] At the same time, PEMC adds the PIN element to a PIN and sends the PIN ID to that PIN element.

[0164] Example 4-2: PEMC as a hotspot. For example... Figure 10 As shown, this embodiment includes the following steps.

[0165] Step 1: PEMC can enable hotspot.

[0166] Step 2: Communicate with the PEMC via its hotspot. Since the PIN elements are different at this point, but the PEMC hotspot is the same, the PEMC cannot distinguish between the different PIN elements, so registration is necessary.

[0167] Step 3: Register the PIN element or PINE enabler to the PEMC and send a second registration request.

[0168] The second registration request includes: PIN element enabler ID, PIN element ID, UE ID, the application ID on the PIN element, the current PIN element's own IP address, and the security certificate.

[0169] Step 4: If registration is successful, PEMC sends a second registration response to the PIN element, which may include the following: registration ID, expiration time (i.e., when this registration expires), and PIN element context ID.

[0170] In this embodiment, PEMC can also determine the permissions of the PIN element, and the second registration response can also include the IP address, port number, and access permissions of PEMC.

[0171] The access permission refers to the permission to access the 5G network, which may include the following access control information and routing information.

[0172] Access control information includes: username, account, password, SSID, BSSID, etc., of those who can access or communicate with 5G.

[0173] The routing information includes: the PEGC's IP address and port number. This is because the PIN element needs to access the 5G network or a public server through a gateway.

[0174] At the same time, PEMC adds the PIN element to a PIN and sends the PIN ID to that PIN element.

[0175] If registration fails, provide the reason for the failure.

[0176] The PIN assembly method provided in this application can be executed by a PIN assembly device. This application uses a PIN assembly device executing the PIN assembly method as an example to illustrate the PIN assembly device provided in this application.

[0177] Figure 11 This is a schematic diagram of a PIN assembly device according to an embodiment of this application. This device may correspond to a terminal in other embodiments, such as a PEMC. Figure 11 As shown, the device 1100 includes the following modules.

[0178] The sending module 1102 is used to send network request information to the PIN server, the network request information being used to request the formation of a PIN.

[0179] The receiving module 1104 is used to receive network response information from the PIN server. The network response information includes successful network formation information or failed network formation information. The successful network formation information indicates that the PIN was successfully formed, and the failed network formation information indicates that the PIN was not successfully formed.

[0180] The PIN creation apparatus provided in this application embodiment includes a sending module that sends a network creation request to a PIN server. This request requests the creation of a PIN. A receiving module receives a network creation response, which includes either successful or failed creation information. In other words, the PIN server can approve or disapprove the network creation request after verifying it. This embodiment enables terminals to create PINs, facilitating communication between devices through PINs. The failed creation information indicates that the network creation request was not approved, and the PIN server can indicate the reason for the failure.

[0181] Optionally, as an embodiment, the network request information includes at least one of the following: 1) the lifecycle information of the PIN, which indicates the time when the PIN is effective or exists; 2) the identification information related to the device; 3) the IP address or port number of the device; 4) the information of the PIN network element that the device wishes to add to the PIN; 5) the PEGC information in the PIN; 6) the security certificate.

[0182] Optionally, as an embodiment, the device-related identification information includes at least one of the following: the identifier ID of the PEMC in the PIN, the enable layer ID of the device, the SUPI of the device, the GPSI of the device, the application ID on the PEMC in the PIN, and the enable client ID of the PEMC in the PIN.

[0183] Optionally, as an embodiment, the information of the PIN network element includes at least one of the following: the ID of the PIN network element, the enable layer ID of the PIN network element, the terminal ID of the PIN network element, the application ID on the PEMC in the PIN, the IP address of the PIN network element, and the enable layer IP address of the PIN network element.

[0184] Optionally, as an embodiment, the information of the PEGC includes at least one of the following: the ID of the PEGC, the enable layer ID of the PEGC, the terminal ID of the PEGC, the application ID on the PEGC, and the IP address of the PEGC.

[0185] Optionally, as an embodiment, the successful assembly information includes at least one of the following: 1) the identifier ID of the PIN; 2) the PEGC information in the PIN; 3) the access control information configured to the PEGC in the PIN, the access control information being used to control whether the PIN network element in the PIN can access or connect to the target network; 4) the routing information configured to the PEGC in the PIN, the routing information being used by the PEGC or the PIN network element in the PIN to access the target network.

[0186] Optionally, as an embodiment, the access control information includes at least one of the following: username, account, password, SSID, BSSID, and / or the routing information includes at least one of the following: the IP address of the UPF, the port number of the UPF, the FQDN of the UPF, and the DN of the data network connected through the UPF; wherein, the PEGC accesses the target network by accessing the UPF.

[0187] Optionally, as an embodiment, the device determines the PEGC in the PIN by at least one of the following methods: 1) the PEGC is signed or registered to the device; 2) the PEGC information is included in the successful setup information; 3) the PIN network element in the PIN managed by the device accesses the target network through the determined PEGC in the PIN.

[0188] Optionally, as an embodiment, when the PEGC is signed or registered to the device, the device and the PEGC establish a communication connection through a non-3GPP access method; the receiving module 1104 is further configured to receive first registration request information from the PEGC; and verify the first registration request information; the sending module 1102 is configured to send first registration response information, the first registration response information including registration success information or registration failure information, the registration success information indicating that the first registration request information has been verified, and the registration failure information indicating that the first registration request information has failed to be verified.

[0189] Optionally, as an embodiment, the first registration request information includes at least one of the following: the ID of the PEGC, the enable layer ID of the PEGC, the terminal ID, the application ID on the PEGC, the IP address of the PEGC, the security certificate, access control information, routing information, and / or, the first registration response information includes at least one of the following: the registration ID, the registration termination time information, and the context ID of the PEGC.

[0190] Optionally, as an embodiment, the device is also used to add a PIN network element to the PIN.

[0191] Optionally, as an embodiment, the device is further configured to establish a communication connection with the PIN network element via a non-3GPP access method; the receiving module 1104 is configured to receive second registration request information from the PIN network element; and if the second registration request is verified, add the PIN network element to the PIN; and the sending module 1102 is configured to send second registration response information.

[0192] Optionally, as an embodiment, the second registration request information includes at least one of the following: the ID of the PIN network element, the enable layer ID of the PIN network element, the ID of the application on the PIN network element, the IP address of the PIN network element, a security certificate, and / or, the second registration response information includes at least one of the following: a registration ID, registration termination time information, the context ID of the PIN network element, and the ID of the PIN.

[0193] Optionally, as an embodiment, the device is further configured to determine the permissions of the PIN network element; wherein the second registration response information further includes at least one of the following: 1) the IP address of the PEGC in the PIN; 2) the port number of the PEGC in the PIN; 3) the access permissions of the PIN network element, wherein the access permissions include whether the PIN network element supports accessing the target network through the PEGC in the PIN.

[0194] Optionally, as an embodiment, the access permission of the PIN network element is obtained by the device from the PIN server, or determined by the device based on the PEGC registration information.

[0195] Optionally, as an embodiment, the sending module 1102 is used to send subscription request information to the PIN server, the subscription request information being used to request at least one of the following: becoming a PEMC; registering or subscribing to an operator network; the receiving module 1104 is used to receive subscription success information from the PIN server, the subscription success information indicating that the device becomes a PEMC.

[0196] Optionally, as an embodiment, the subscription request information includes at least one of the following: the application ID on the PEMC, the SUPI of the device, the GPSI of the device, the IP address of the device, the IP address of the PEMC client, and the security certificate.

[0197] The apparatus 1100 according to the embodiments of this application can refer to the flow of the method 200 corresponding to the embodiments of this application. Furthermore, each unit / module in the apparatus 1100 and the other operations and / or functions described above are respectively for implementing the corresponding flow in the method 200 and can achieve the same or equivalent technical effects. For the sake of brevity, they will not be described in detail here.

[0198] Figure 12 This is a schematic diagram of a PIN assembly apparatus according to an embodiment of this application. This apparatus may correspond to a PIN server in other embodiments. Figure 12 As shown, the device 1200 includes the following modules.

[0199] The receiving module 1202 is used to receive networking request information from the terminal, wherein the networking request information is used to request the formation of a PIN.

[0200] The sending module 1204 is used to send network response information to the terminal. The network response information includes successful network formation information or failed network formation information. The successful network formation information indicates that the PIN has been successfully formed, and the failed network formation information indicates that the PIN has failed to be formed.

[0201] The PIN creation method provided in this application embodiment involves a device 1200 receiving a network creation request message for requesting PIN creation. The device 1200 then sends a network creation response message to a terminal, which includes either successful or failed creation information. In other words, after verifying the network creation request message, the device 1200 can either agree to or disagree with the terminal's network creation request. This application embodiment enables terminals to create PINs, facilitating communication between devices through PINs. The failed creation information indicates that the network creation request was not agreed to, and the device 1200 can indicate the reason for the failure.

[0202] Optionally, as an embodiment, the network request information includes at least one of the following: 1) the lifecycle information of the PIN, which indicates the time when the PIN is effective or exists; 2) the identification information related to the terminal; 3) the IP address or port number of the terminal; 4) the information of the PIN network element that the terminal wishes to add to the PIN; 5) the PEGC information in the PIN; 6) the security certificate.

[0203] Optionally, as an embodiment, the terminal-related identification information includes at least one of the following: the PEMC ID in the PIN, the enable layer ID of the terminal, the SUPI of the terminal, the GPSI of the terminal, the application ID on the PEMC in the PIN, and the enable client ID of the PEMC.

[0204] Optionally, as an embodiment, the information of the PIN network element includes at least one of the following: the ID of the PIN network element, the enable layer ID of the PIN network element, the terminal ID of the PIN network element, the application ID on the PEMC in the PIN, the IP address of the PIN network element, and the enable layer IP address of the PIN network element.

[0205] Optionally, as an embodiment, the information of the PEGC includes at least one of the following: the ID of the PEGC, the enable layer ID of the PEGC, the terminal ID of the PEGC, the application ID on the PEGC, and the IP address of the PEGC.

[0206] Optionally, as an embodiment, the successful assembly information includes at least one of the following: 1) the identifier ID of the PIN; 2) the PEGC information in the PIN; 3) the access control information configured to the PEGC in the PIN, the access control information being used to control whether the PIN network element in the PIN can access or connect to the target network; 4) the routing information configured to the PEGC in the PIN, the routing information being used by the PEGC or the PIN network element in the PIN to access the target network.

[0207] Optionally, as an embodiment, the access control information includes at least one of the following: username, account, password, SSID, BSSID, and / or the routing information includes at least one of the following: the IP address of the UPF, the port number of the UPF, the FQDN of the UPF, and the DN data network connected through the UPF; wherein, the PEGC accesses the target network by accessing the UPF.

[0208] Optionally, as an embodiment, the sending module 1204 is used to send the PEGC information in the PIN to the terminal.

[0209] The apparatus 1200 according to the embodiments of this application can refer to the flow of the method 300 corresponding to the embodiments of this application. Furthermore, each unit / module in the apparatus 1200 and the other operations and / or functions described above are respectively for implementing the corresponding flow in the method 300 and can achieve the same or equivalent technical effects. For the sake of brevity, they will not be described in detail here.

[0210] Figure 13 This is a schematic diagram of a PIN assembly apparatus according to an embodiment of this application. This apparatus may correspond to a terminal in other embodiments, such as a PEGC. Figure 13 As shown, the device 1300 includes the following modules.

[0211] The communication establishment module 1302 is used to establish a communication connection with the PEMC via a non-3GPP access method.

[0212] The sending module 1304 is used to send a first registration request information to the PEMC, the first registration request information being used to request to become the PEGC in the PIN.

[0213] The receiving module 1306 is configured to receive first registration response information from the PEMC. The first registration response information includes registration success information or registration failure information. The registration success information indicates that the first registration request information has been verified successfully, and the registration failure information indicates that the first registration request information has failed to be verified. Verification failure indicates that the registration request has not been approved, and the PEMC can indicate the reason for this registration failure.

[0214] The PIN assembly apparatus provided in this application embodiment can be applied for as a PEGC in the PIN. The PEGC enables the PIN network element in the PIN to access the 5G network or access other service servers via the 5G network, which is beneficial for meeting the communication needs of the device through the PIN.

[0215] Optionally, as an embodiment, the first registration request information includes at least one of the following: the device ID, the device enable layer ID, the application ID on the device, the device IP address, security certificate, access control information, routing information, and / or, the first registration response information includes at least one of the following: registration ID, registration termination time information, and the device context ID.

[0216] The apparatus 1300 according to the embodiments of this application can refer to the flow of the method 400 corresponding to the embodiments of this application. Furthermore, each unit / module in the apparatus 1300 and the other operations and / or functions described above are for implementing the corresponding flow in the method 400 and can achieve the same or equivalent technical effects. For the sake of brevity, they will not be described in detail here.

[0217] Figure 14 This is a schematic diagram of a PIN assembly apparatus according to an embodiment of this application. This apparatus may correspond to a terminal in other embodiments, such as a PIN network element. Figure 14 As shown, the device 1400 includes the following modules.

[0218] The communication establishment module 1402 is used to establish a communication connection with the PEMC via a non-3GPP access method.

[0219] The sending module 1404 is used to send a second registration request information to the PEMC, the second registration request information being used to request to become a PIN network element in the PIN.

[0220] The receiving module 1406 is configured to receive second registration response information from the PEMC. The second registration response information includes registration success information or registration failure information. The registration success information indicates that the second registration request information has been verified successfully, and the registration failure information indicates that the second registration request information has failed to be verified. Verification failure indicates that the registration request has not been approved, and the PEMC can indicate the reason for this registration failure.

[0221] The PIN assembly apparatus provided in this application embodiment can be applied for as a PIN network element in the PIN. This PIN network element can access the 5G network through the PEGC in the PIN or access other service servers through the 5G network, which is beneficial to meeting communication needs.

[0222] Optionally, as an embodiment, the second registration request information includes at least one of the following: the device ID, the device enable layer ID, the application ID on the device, the device IP address, a security certificate, and / or, the second registration response information includes at least one of the following: a registration ID, registration termination time information, the context ID of the terminal, and the terminal ID.

[0223] Optionally, as an embodiment, the second registration response information further includes at least one of the following: 1) the IP address of the PEGC in the PIN; 2) the port number of the PEGC in the PIN; 3) the access permission of the device, wherein the access permission includes whether the device supports accessing the target network through the PEGC in the PIN.

[0224] The apparatus 1400 according to the embodiments of this application can refer to the flow of the method 500 corresponding to the embodiments of this application. Furthermore, each unit / module in the apparatus 1400 and the other operations and / or functions described above are respectively for implementing the corresponding flow in the method 500 and can achieve the same or equivalent technical effects. For the sake of brevity, they will not be described in detail here.

[0225] The PIN assembly device in this application embodiment can be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or a chip. The electronic device can be a terminal, or other devices besides a terminal. For example, the terminal can include, but is not limited to, the type of terminal 11 listed above; other devices can be servers, network attached storage (NAS), etc., and this application embodiment does not specifically limit the type.

[0226] The PIN assembly apparatus provided in this application embodiment can achieve Figures 2 to 10 The various processes implemented in the method embodiments achieve the same technical effect, and will not be described again here to avoid repetition.

[0227] Optional, such as Figure 15 As shown, this application embodiment also provides a communication device 1500, including a processor 1501 and a memory 1502. The memory 1502 stores a program or instructions that can run on the processor 1501. For example, when the communication device 1500 is a terminal, the program or instructions executed by the processor 1501 implement the various steps of the above-described PIN assembly method embodiment and achieve the same technical effect. When the communication device 1500 is a network-side device, the program or instructions executed by the processor 1501 implement the various steps of the above-described PIN assembly method embodiment and achieve the same technical effect. To avoid repetition, further details are omitted here.

[0228] This application embodiment also provides a terminal, including a processor and a communication interface, the communication interface being used to implement... Figure 2 , Figure 4 or Figure 5The steps of the method in the illustrated embodiment are shown. This terminal embodiment corresponds to the terminal-side method embodiment described above. All implementation processes and methods of the above method embodiments can be applied to this terminal embodiment and achieve the same technical effect. Specifically, Figure 16 A schematic diagram of the hardware structure of a terminal to implement an embodiment of this application.

[0229] The terminal 1600 includes, but is not limited to, at least some of the following components: radio frequency unit 1601, network module 1602, audio output unit 1603, input unit 1604, sensor 1605, display unit 1606, user input unit 1607, interface unit 1608, memory 1609, and processor 1610.

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

[0231] It should be understood that, in this embodiment, the input unit 1604 may include a graphics processing unit (GPU) 16041 and a microphone 16042. The GPU 16041 processes image data of still images or videos obtained by an image capture device (such as a camera) in video capture mode or image capture mode. The display unit 1606 may include a display panel 16061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 1607 includes at least one of a touch panel 16071 and other input devices 16072. The touch panel 16071 is also called a touch screen. The touch panel 16071 may include a touch detection device and a touch controller. Other input devices 16072 may include, but are not limited to, physical keyboards, function keys (such as volume control buttons, power buttons, etc.), trackballs, mice, and joysticks, which will not be described in detail here.

[0232] In this embodiment, after receiving downlink data from the network-side device, the radio frequency unit 1601 can transmit it to the processor 1610 for processing; in addition, the radio frequency unit 1601 can send uplink data to the network-side device. Typically, the radio frequency unit 1601 includes, but is not limited to, antennas, amplifiers, transceivers, couplers, low-noise amplifiers, duplexers, etc.

[0233] The memory 1609 can be used to store software programs or instructions, as well as various data. The memory 1609 may primarily include a first storage area for storing programs or instructions and a second storage area for storing data. The first storage area may store the operating system, application programs or instructions required for at least one function (such as sound playback, image playback, etc.). Furthermore, the memory 1609 may include volatile memory or non-volatile memory, or both. The non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct memory bus RAM (DRRAM). The memory 1609 in this embodiment includes, but is not limited to, these and any other suitable types of memory.

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

[0235] The radio frequency unit 1601 can be used to implement... Figure 2 , Figure 4 or Figure 5 Steps of the method in the illustrated embodiment

[0236] The terminal 1600 provided in this application embodiment can also implement the various processes of the above-described PIN assembly method embodiment and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0237] This application also provides a network-side device, including a processor and a communication interface, the communication interface being used for implementing... Figure 3 The steps of the method in the illustrated embodiment are shown. This network-side device embodiment corresponds to the network-side device method embodiment described above. All implementation processes and methods of the above method embodiments can be applied to this network-side device embodiment and achieve the same technical effects.

[0238] Specifically, embodiments of this application also provide a network-side device. For example... Figure 17 As shown, the network-side device 1700 includes a processor 1701, a network interface 1702, and a memory 1703. The network interface 1702 is, for example, a common public radio interface (CPRI).

[0239] Specifically, the network-side device 1700 of this embodiment further includes: instructions or programs stored in memory 1703 and executable on processor 1701, wherein processor 1701 calls the instructions or programs in memory 1703 to execute. Figure 12 The methods executed by each module shown achieve the same technical effect, and to avoid repetition, they will not be described in detail here.

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

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

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

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

[0244] This application also provides a computer program / program product, which is stored in a storage medium and executed by at least one processor to implement the various processes of the above-described PIN assembly method embodiments, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0245] This application also provides a PIN creation system, including: a terminal and a network-side device, wherein the terminal can be used to perform the steps of the PIN creation method described above, and the network-side device can be used to perform the steps of the PIN creation method described above.

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

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

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

Claims

1. A method for constructing a personal Internet of Things (IoT) network PIN, characterized in that, include: The terminal sends a network formation request information to the PIN server. The terminal is a Personal Internet of Things (PEMC) with management capabilities. The network formation request information is used to request the formation of a PIN. The terminal receives network response information from the PIN server. The network response information includes successful network formation information or failed network formation information. The successful network formation information indicates that the PIN was successfully formed, and the failed network formation information indicates that the PIN was not successfully formed. The network request information includes at least one of the following: The terminal-related identification information; The terminal's IP address or port number; The terminal wants to add information about the PIN network element to the PIN; Security certificate; The terminal-related identification information includes at least one of the following: the PEMC identifier ID in the PIN, the enable layer ID of the terminal, the subscription permanent identifier SUPI of the terminal, the general public subscription identifier GPSI of the terminal, the application ID on the PEMC in the PIN, and the enable client ID of the PEMC in the PIN.

2. The method according to claim 1, characterized in that, The network request information also includes at least one of the following: The PIN's lifecycle information, which indicates the duration of the PIN's validity or existence; The PIN contains information about the Personal Internet of Things (IoT) element PEGC with gateway capabilities.

3. The method according to claim 1, characterized in that, The information of the PIN network element includes at least one of the following: the ID of the PIN network element, the enable layer ID of the PIN network element, the terminal ID of the PIN network element, the application ID on the PEMC in the PIN, the IP address of the PIN network element, and the enable layer IP address of the PIN network element.

4. The method according to claim 2, characterized in that, The information of the PEGC includes at least one of the following: the ID of the PEGC, the enable layer ID of the PEGC, the terminal ID of the PEGC, the application ID on the PEGC, and the IP address of the PEGC.

5. The method according to any one of claims 1 to 4, characterized in that, The successful assembly information includes at least one of the following: The PIN's identifier ID; Information about PEGC in the PIN; The PIN is configured with access control information for the PEGC. The access control information is used to control whether the PIN network element in the PIN can access or connect to the target network. The routing information configured in the PIN to the PEGC is used by the PEGC or the PIN network element in the PIN to access the target network.

6. The method according to claim 5, characterized in that, The access control information includes at least one of the following: username, account, password, service set identifier (SSID), basic service set identifier (BSSID); and / or The routing information includes at least one of the following: the IP address of the User Plane Function (UPF), the port number of the UPF, the FQDN of the UPF, and the DN of the data network connected through the UPF; wherein the PEGC accesses the target network by accessing the UPF.

7. The method according to claim 1, characterized in that, The terminal determines the PEGC in the PIN by at least one of the following methods: The PEGC is signed or registered to the terminal; The successful assembly information includes information about PEGC; The PIN network element in the PIN managed by the terminal accesses the target network through the PEGC in the determined PIN.

8. The method according to claim 7, characterized in that, In the case where the PEGC is signed or registered on the terminal, the method further includes: The terminal establishes a communication connection with the PEGC via a non-3GPP access method. The terminal receives a first registration request information from the PEGC; The terminal verifies the first registration request information and sends a first registration response information. The first registration response information includes registration success information or registration failure information. The registration success information indicates that the first registration request information has been verified, and the registration failure information indicates that the first registration request information has failed to be verified.

9. The method according to claim 8, characterized in that, The first registration request information includes at least one of the following: the ID of the PEGC, the enable layer ID of the PEGC, the terminal ID, the application ID on the PEGC, the IP address of the PEGC, a security certificate, access control information, routing information; and / or The first registration response information includes at least one of the following: registration ID, registration termination time information, and the context ID of the PEGC.

10. The method according to claim 1, characterized in that, The method further includes: The terminal adds a PIN network element to the PIN.

11. The method according to claim 10, characterized in that, The terminal adds a PIN network element to the PIN, including: The terminal and the PIN network element establish a communication connection through a non-3GPP access method. The terminal receives a second registration request information from the PIN network element; If the second registration request is verified, the terminal adds the PIN network element to the PIN; The terminal sends a second registration response message.

12. The method according to claim 11, characterized in that, The second registration request information includes at least one of the following: the ID of the PIN network element, the enable layer ID of the PIN network element, the ID of the application on the PIN network element, the IP address of the PIN network element, and a security certificate; and / or The second registration response information includes at least one of the following: registration ID, registration termination time information, the context ID of the PIN network element, and the ID of the PIN.

13. The method according to claim 12, characterized in that, The method further includes: the terminal determining the permissions of the PIN network element; wherein the second registration response information further includes at least one of the following: The IP address of the PEGC in the PIN; The port number of the PEGC in the PIN; The access permissions of the PIN network element include whether the PIN network element supports accessing the target network through the PEGC in the PIN.

14. The method according to claim 13, characterized in that, The access permission of the PIN network element is obtained by the terminal from the PIN server, or determined by the terminal based on the PEGC registration information.

15. The method according to claim 1, characterized in that, Before the terminal sends the network request information to the PIN server, the method further includes: The terminal sends a subscription request information to the PIN server, the subscription request information being used to request at least one of the following: becoming a PEMC; registering or subscribing to an operator network; The terminal receives a successful signing message from the PIN server, which indicates that the terminal has become a PEMC.

16. The method according to claim 15, characterized in that, The subscription request information includes at least one of the following: the application ID on the PEMC, the SUPI of the terminal, the GPSI of the terminal, the IP address of the terminal, the IP address of the PEMC client, and the security certificate.

17. A method for assembling a PIN, characterized in that, include: The PIN server receives networking request information from a terminal, which is a Personal Internet of Things (PEMC) with management capabilities. The networking request information is used to request the formation of a PIN. The PIN server sends a network formation response message to the terminal. The network formation response message includes a successful formation message or a failed formation message. The successful formation message indicates that the PIN has been successfully formed, and the failed formation message indicates that the PIN has failed to be formed. The network request information includes at least one of the following: The terminal-related identification information; The terminal's IP address or port number; The terminal wants to add information about the PIN network element to the PIN; Security certificate; The terminal-related identification information includes at least one of the following: the PEMC identifier ID in the PIN, the enable layer ID of the terminal, the subscription permanent identifier SUPI of the terminal, the general public subscription identifier GPSI of the terminal, the application ID on the PEMC in the PIN, and the enable client ID of the PEMC in the PIN.

18. The method according to claim 17, characterized in that, The network request information also includes at least one of the following: The PIN's lifecycle information, which indicates the duration of the PIN's validity or existence; The PEGC information in the PIN.

19. The method according to claim 17, characterized in that, The terminal-related identification information includes at least one of the following: the PEMC identifier ID in the PIN, the terminal's enable layer ID, the terminal's SUPI, the terminal's GPSI, the application ID on the PEMC in the PIN, and the PEMC's enable client ID.

20. The method according to claim 17, characterized in that, The information of the PIN network element includes at least one of the following: the ID of the PIN network element, the enable layer ID of the PIN network element, the terminal ID of the PIN network element, the application ID on the PEMC in the PIN, the IP address of the PIN network element, and the enable layer IP address of the PIN network element.

21. The method according to claim 18, characterized in that, The information of the PEGC includes at least one of the following: the ID of the PEGC, the enable layer ID of the PEGC, the terminal ID of the PEGC, the application ID on the PEGC, and the IP address of the PEGC.

22. The method according to any one of claims 17 to 21, characterized in that, The successful assembly information includes at least one of the following: The PIN's identifier ID; Information about PEGC in the PIN; The PIN is configured with access control information for the PEGC. The access control information is used to control whether the PIN network element in the PIN can access or connect to the target network. The routing information configured in the PIN to the PEGC is used by the PEGC or the PIN network element in the PIN to access the target network.

23. The method according to claim 22, characterized in that, The access control information includes at least one of the following: username, account, password, SSID, BSSID; and / or The routing information includes at least one of the following: the IP address of the UPF, the port number of the UPF, the FQDN of the UPF, and the DN data network connected through the UPF; wherein the PEGC accesses the target network by accessing the UPF.

24. The method according to claim 17, characterized in that, The method further includes: The PIN server sends the PEGC information in the PIN to the terminal.

25. A PIN assembly device, applied to a terminal, characterized in that, include: The sending module is used to send network request information to the PIN server, wherein the network request information is used to request the formation of a PIN; The receiving module is used to receive network response information from the PIN server. The network response information includes successful network formation information or failed network formation information. The successful network formation information indicates that the PIN has been successfully formed, and the failed network formation information indicates that the PIN has failed to be formed. The terminal is a Personal Internet of Things (PEMC) network element with management capabilities; The network request information includes at least one of the following: The terminal-related identification information; The terminal's IP address or port number; The terminal wants to add information about the PIN network element to the PIN; Security certificate; The terminal-related identification information includes at least one of the following: the PEMC identifier ID in the PIN, the enable layer ID of the terminal, the subscription permanent identifier SUPI of the terminal, the general public subscription identifier GPSI of the terminal, the application ID on the PEMC in the PIN, and the enable client ID of the PEMC in the PIN.

26. A PIN assembly device, applied to a PIN server, characterized in that, include: The receiving module is used to receive networking request information from the terminal, wherein the terminal is a Personal Internet of Things (PEMC) with management capabilities, and the networking request information is used to request the formation of a PIN. The sending module is used to send network response information to the terminal. The network response information includes successful network formation information or failed network formation information. The successful network formation information indicates that the PIN has been successfully formed, and the failed network formation information indicates that the PIN has failed to be formed. The network request information includes at least one of the following: The terminal-related identification information; The terminal's IP address or port number; The terminal wants to add information about the PIN network element to the PIN; Security certificate; The terminal-related identification information includes at least one of the following: the PEMC identifier ID in the PIN, the enable layer ID of the terminal, the subscription permanent identifier SUPI of the terminal, the general public subscription identifier GPSI of the terminal, the application ID on the PEMC in the PIN, and the enable client ID of the PEMC in the PIN.

27. A terminal, characterized in that, It includes a processor and a memory, the memory storing a program or instructions that can run on the processor, the program or instructions being executed by the processor to implement the steps of the PIN assembly method as described in any one of claims 1 to 16.

28. A network-side device, characterized in that, It includes a processor and a memory, the memory storing a program or instructions that can run on the processor, the program or instructions being executed by the processor to implement the steps of the PIN assembly method as described in any one of claims 17 to 24.

29. A readable storage medium, characterized in that, The readable storage medium stores a program or instructions that, when executed by a processor, implement the steps of the PIN assembly method as described in any one of claims 1 to 24.

Images