Personal internet of things network creation method, device, and storage medium

Abstract

The application provides a personal Internet of Things network creation method, device and storage medium, which is applied to a resident gateway, the resident gateway is in communication connection with an electronic device; the electronic device is a device capable of serving as a PEMC; the resident gateway is a gateway capable of serving as a PEGC and being connected to a core network through a wired network or a wireless network; the method comprises the following steps: determining that the resident gateway has been registered as a PEGC in the core network and that the electronic device has been registered as a PEMC in the core network; sending a gateway identifier to the electronic device based on gateway request information sent by the electronic device; and receiving a network identifier sent by the electronic device; the network identifier is used for indicating that the personal Internet of Things network creation is successful, so that the personal Internet of Things network can be created in the case that the network quality is poor.

Description

Technical Field

[0001] This application relates to the field of communication technology, specifically to a method, device, and storage medium for creating a personal Internet of Things (IoT) network. Background Technology

[0002] In related technologies, Personal IoT Networks (PINs) can be applied to scenarios such as healthcare, education, homes, and industry. However, in indoor scenarios where there is no 5G signal coverage or poor signal quality, 5G User Equipment (5G UEs) with PIN Element with Gateway Capability (PEMC) capabilities cannot directly connect to the 5G Core Network (5GC) for registration. This results in the PIN network failing to establish itself, thus compromising the normal operation of network services. Currently, there is no effective solution to this problem. Summary of the Invention

[0003] In view of this, embodiments of this application provide a method, device, and storage medium for creating a personal Internet of Things (IoT) network, which aims to effectively solve the problem of creating a personal IoT network under poor network quality conditions.

[0004] The technical solution of this application embodiment is implemented as follows:

[0005] In a first aspect, embodiments of this application provide a method for creating a personal Internet of Things (IoT) network, applied to a resident gateway, wherein the resident gateway is communicatively connected to an electronic device; the electronic device is a device capable of functioning as a Personal Internet of Things (PEMC) with management capabilities; the resident gateway is a Personal Internet of Things (PEGC) capable of functioning as a gateway and a gateway capable of accessing the core network via a wired or wireless network; the method includes:

[0006] It is determined that the resident gateway has been registered as a PEGC in the core network, and the electronic device has been registered as a PEMC in the core network;

[0007] Based on the gateway request information sent by the electronic device, send a gateway identifier to the electronic device;

[0008] Receive the network identifier sent by the electronic device; the network identifier is used to indicate that the personal Internet of Things network has been successfully created.

[0009] In some implementations, determining that the resident gateway has registered as a PEGC in the core network and that the electronic device has registered as a PEMC in the core network includes:

[0010] Send a first registration request to the core network;

[0011] The core network receives configuration information sent based on the first registration request; the configuration information indicates that the resident gateway has registered as a PEGC in the core network.

[0012] The second registration request sent by the electronic device is forwarded to the core network; the second registration request is used to request the electronic device to register as a PEMC in the core network.

[0013] The registration success information sent by the core network is sent to the electronic device; the registration success information indicates that the electronic device has registered as a PEMC in the core network.

[0014] In some implementations, the first registration request includes the first identifier information and PEGC capability information of the resident gateway; the configuration information includes at least the gateway type of the resident gateway; and forwarding the second registration request sent by the electronic device to the core network includes:

[0015] Receive the gateway type sent by the core network based on the first identifier information;

[0016] Based on the capability indication information of the electronic device and the gateway type, determine the access method for the electronic device to access the core network;

[0017] Based on the access method, the second registration request is forwarded to the core network.

[0018] In some implementations, determining the access method of the electronic device to access the core network based on the capability indication information of the electronic device and the gateway type includes:

[0019] If the capability indication information indicates that the electronic device has PEMC capability, and the gateway type indicates the subscription type that allows the electronic device to access, then the access method of the electronic device is determined to be the first access method.

[0020] The first access method indicates that the second registration request sent by the electronic device to the resident gateway can be forwarded to the core network, and the electronic device can register as a PEMC in the core network.

[0021] In some implementations, the second registration request includes at least the second identifier information and PEMC capability information of the electronic device; before determining the access method of the electronic device to access the core network based on the capability indication information of the electronic device and the gateway type, the method further includes:

[0022] The instruction request corresponding to the second registration request is sent to the core network; the instruction request includes at least the second identifier information and PEMC capability information from the second registration request.

[0023] The core network receives capability indication information based on the second identifier information and the PEMC capability information; the capability indication information represents the indication information corresponding to the PEMC capability information.

[0024] Secondly, embodiments of this application provide a method for creating a personal Internet of Things (IoT) network, applied to an electronic device connected to a resident gateway; the resident gateway is a gateway capable of functioning as a PEGC (Personal Internet of Things Controlled Network) and capable of accessing the core network via a wired or wireless network; the electronic device is a device capable of functioning as a PEMC (Personal Internet of Things Controlled Network); the method includes:

[0025] It is determined that the resident gateway has been registered as a PEGC in the core network, and the electronic device has been registered as a PEMC in the core network;

[0026] Receive the gateway identifier sent by the resident gateway based on the gateway request information;

[0027] The core network receives a network identifier sent by the personal IoT server based on a creation request information; the creation request information includes at least the management identifier of the electronic device and the gateway identifier; the network identifier is used to indicate that the personal IoT network has been successfully created.

[0028] Send the network identifier to the resident gateway;

[0029] The resident gateway is designated as the PEGC of the personal IoT network based on the gateway identifier.

[0030] In some implementations, determining that the electronic device has been registered as a PEMC in the core network includes:

[0031] The electronic device sends a second registration request to the core network through the resident gateway; the second registration request is used to request the electronic device to register as a PEMC in the core network.

[0032] The system receives a registration success message sent by the resident gateway; the registration success message indicates that the electronic device has registered as a PEMC in the core network.

[0033] In some implementations, the method further includes:

[0034] Broadcasting network information of the personal Internet of Things network; the network information includes at least the network identifier;

[0035] Receive network access request information sent by the Internet of Things terminal in response to the network information;

[0036] If it is determined that the IoT terminal has joined the network, a terminal identifier corresponding to the IoT terminal is generated based on the network joining request information.

[0037] Thirdly, embodiments of this application provide a method for creating a personal Internet of Things (IoT) network, applied to a core network, wherein the core network is connected to an electronic device and a resident gateway; the electronic device is a device capable of functioning as a PEMC; the gateway is a gateway capable of functioning as a PEMC and capable of accessing the core network via a wired or wireless network; the method includes:

[0038] It is determined that the resident gateway has been registered as a PEGC in the core network, and the electronic device has been registered as a PEMC in the core network; the creation request information sent by the electronic device is forwarded to the personal IoT server; the creation request information includes at least the management identifier of the electronic device and the gateway identifier of the gateway;

[0039] The network identifier sent by the personal IoT server based on the management identifier and the gateway identifier is forwarded to the electronic device; the network identifier is used to indicate that the personal IoT network has been successfully created.

[0040] In some implementations, determining that the resident gateway has registered as a PEGC in the core network and that the electronic device has registered as a PEMC in the core network includes:

[0041] Receive the first registration request sent by the resident gateway;

[0042] Send configuration information to the resident gateway; the configuration information indicates that the resident gateway has registered as a PEGC in the core network;

[0043] The electronic device receives a second registration request from the resident gateway; the second registration request is used to request the electronic device to register as a PEMC in the core network.

[0044] The registration success information generated based on the second registration request is sent to the resident gateway; the registration success information indicates that the electronic device has registered as a PEMC in the core network.

[0045] In some implementations, the first registration request includes the first identifier information and PEGC capability information of the resident gateway; after receiving the first registration request sent by the resident gateway, the method further includes:

[0046] The PEGC capability information is stored;

[0047] The configuration information corresponding to the resident gateway is determined based on the first identifier information.

[0048] In some implementations, the second registration request includes at least the first identifier information and PEMC capability information of the electronic device; receiving the second registration request sent by the electronic device through the resident gateway includes:

[0049] Receive an indication request sent by the resident gateway; the indication request corresponds to a second registration request sent by the electronic device; the indication request includes at least the second identifier information and PEMC capability information from the second registration request;

[0050] Capability indication information is determined based on the second identifier information and the PEMC capability information; the capability indication information represents the indication information corresponding to the PEMC capability information.

[0051] Send the capability indication information to the resident gateway;

[0052] Receive the second registration request sent by the resident gateway based on the capability indication information.

[0053] Fourthly, embodiments of this application provide a resident gateway, including: a first processor and a first memory for storing a computer program capable of running on the first processor.

[0054] Wherein, when the first processor is used to run the computer program, it executes the steps of the method described in the first aspect of the embodiments of this application.

[0055] Fifthly, embodiments of this application provide an electronic device, including: a second processor and a second memory for storing a computer program capable of running on the second processor.

[0056] Wherein, when the second processor is used to run the computer program, it executes the steps of the method described in the second aspect of the embodiments of this application.

[0057] Sixthly, embodiments of this application provide a network device, including: a third processor and a third memory for storing a computer program capable of running on the third processor.

[0058] When the third processor runs the computer program, it executes the steps of the method described in the third aspect of the embodiments of this application.

[0059] In a seventh aspect, embodiments of this application provide a storage medium having a computer program stored thereon. When the computer program is executed by a processor, it implements the steps of the method described in the first aspect of embodiments of this application, or the steps of the method described in the second aspect of embodiments of this application, or the steps of the method described in the third aspect of embodiments of this application.

[0060] This application provides a method, device, and storage medium for creating a personal Internet of Things (IoT) network, applied to a resident gateway, which is communicatively connected to an electronic device. The electronic device is a Personal IoT Network Component (PEMC) capable of management. The resident gateway is a Personal IoT Network Component (PEGC) with gateway functionality and can access the core network via a wired or wireless network. The method includes: determining that the resident gateway has registered as a PEGC in the core network and that the electronic device has registered as a PEMC in the core network; sending a gateway identifier to the electronic device based on a gateway request message sent by the electronic device; and receiving a network identifier sent by the electronic device. The network identifier is used to indicate that the personal IoT network has been successfully created. Using the technical solution of this application, the resident gateway can register as a PEGC in the core network; the electronic device can register as a PEMC in the core network through the resident gateway; the gateway identifier of the resident gateway is sent to the electronic device, and the network identifier indicating successful creation of the personal IoT network is received from the electronic device, enabling the creation of a personal IoT network even under poor network conditions. Attached Figure Description

[0061] Figure 1 This is a schematic diagram illustrating the implementation process of the method for creating a personal Internet of Things network on the gateway side in this application embodiment;

[0062] Figure 2 This is a schematic diagram illustrating the implementation process of the method for creating a personal Internet of Things network on the electronic device side in an embodiment of this application.

[0063] Figure 3 This is a schematic diagram illustrating the implementation process of the method for creating a personal Internet of Things network on the network device side in an embodiment of this application.

[0064] Figure 4 This is a schematic diagram of the PIN network registration management process under 5G fixed-mobile convergence conditions in an embodiment of this application;

[0065] Figure 5 This is a schematic diagram illustrating the process of registering PEGC capability from 5G-RG to 5GC in an embodiment of this application.

[0066] Figure 6 This is a schematic diagram illustrating the process of a 5G UE registering PEMC capability via 5G-RG in an embodiment of this application.

[0067] Figure 7 This is a schematic diagram of the PIN creation process in an embodiment of this application;

[0068] Figure 8 This is a schematic diagram of the structure of the resident gateway in an embodiment of this application;

[0069] Figure 9 This is a schematic diagram of the structure of the electronic device according to an embodiment of this application;

[0070] Figure 10 This is a schematic diagram of the network device according to an embodiment of this application. Detailed Implementation

[0071] The present application will now be described in further detail with reference to the accompanying drawings and embodiments.

[0072] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application.

[0073] Among related technologies, 5G, as a next-generation communication technology, leverages its high bandwidth, low latency, high reliability, and wide connectivity to provide essential network infrastructure support for vertical industry applications. Meanwhile, vertical industries have widely deployed local area networks (LANs) and Internet of Things (IoT) based on various network types, including wireless communication technologies (Wi-Fi), Bluetooth, wired connections, Zigbee, and Long Range Radio (Lora). Due to considerations such as cost and usage habits, it's impossible for various industries to completely replace their existing networks with 5G networks in the short term. Therefore, 5G networks will coexist with other network types for a long time within various industries. If 5G network terminals are isolated from terminals on other networks, the goal of 5G's interconnectivity of everything will not be achieved; therefore, the integration of 5G with other network types is imperative.

[0074] In related technologies, 3GPP first defined PINs in mobile standards. Unlike commercial IoT devices, IoT devices within a PIN are typically less robust, with battery life usually lasting only a few days or weeks. User plane traffic is typically forwarded within a confined environment (e.g., around the body or indoors), i.e., within the PIN, and notifications of events occurring within the PIN can be received on smartphones or other management devices. PIN devices can communicate within the PIN using various non-3GPP-based wireless technologies such as Wi-Fi, Z-Wave, Zigbee, and Bluetooth to allow user interaction and control. PINs offer two main benefits: first, because IoT devices generate less user plane traffic, traditional cellular operators don't need to reserve dedicated resources for IoT devices in their networks, thus saving bandwidth; second, the traffic generated by IoT devices can remain locally via a dedicated network, facilitating user management and usage.

[0075] The 5G system has a mechanism to identify PINs and PIN elements. A PIN should contain at least one PEGC and at least one PEMC. Among them: (1) PEGC: A PIN element that can provide access to and from the 5G network for other PIN elements, or provide relay for communication between PIN elements; (2) PEMC: A PIN element with the ability to manage PINs, which contains a list of PIN elements, manages the behavior of each PIN element, and has access rights to the PIN elements.

[0076] The PEMC stores the following information about the managed PIN elements: a) the unique identifier of the PIN element within the PIN; b) the connection types supported by the PIN element; c) the applications running on it (such as application ID); d) related metadata (such as event occurrence, event type, timestamp, etc.); e) the security credentials of the PIN element, etc.

[0077] In related technologies, fixed-mobile convergence, also known as wireless and wired convergence, is the integration and cooperation between fixed and mobile networks to achieve the operation of full-service and converged services, providing users with diverse and high-quality communication, information and entertainment services, regardless of their terminals, networks, applications and locations.

[0078] To achieve 5G fixed-mobile convergence, the 3GPP specification defines two types of gateways: Residential Gateway (RG) and Wireline Access Gateway Function (W-AGF), deployed on the user side and network side respectively, to address the convergence issue at these two locations.

[0079] (1) RG is located between the terminal and the access network, and is further divided into 5G Residential Gateway (5G-RG) and Fixed Network Gateway (FN-RG). 5G-RG has 5G communication capabilities and can be connected to the Next Generation Radio Access Network (NG RAN) or the wired access network; while FN-RG can only be connected to the wired access network.

[0080] (2) W-AGF is located between the wired access network and 5GC, and together with the wired access network, it forms the wired 5G access network (W-5GAN). It connects with 5GC through the standard 3GPP N2 and N3 interfaces.

[0081] "RG+W-AGF" is the foundation for realizing 5G fixed-mobile convergence. Based on the fixed-mobile convergence network architecture of 5G-RG+W-AGF, the terminal first accesses 5G-RG through a non-3GPP network (e.g., WLAN, wired, Bluetooth, etc.), and then indirectly accesses the 5G core network through 5G-RG.

[0082] In related technologies, PIN networks can be applied to scenarios such as healthcare, education, home, and industry. When applied to smart healthcare scenarios in the medical industry, 5G smartphones, such as 5G User Equipment (5G UE), can act as PEMC devices, and personal health monitoring devices can act as PIN elements. Patient data is then provided to the hospital server via the 5G network through a fixed terminal device, PEGC. In smart ward scenarios, devices carried and worn by patients can discover each other with other devices in the smart ward. The 5G UE acts as a PEMC device, and the 5G smart bed in the ward can be configured as a PEGC device, together forming a PIN network. Data from the patient's wearable devices can be transmitted to the hospital system via the PEGC through the 5G network for health monitoring.

[0083] This application provides a method, device, and storage medium for creating a personal Internet of Things (IoT) network. The method for creating a personal IoT network based on this application can solve the problem of creating a personal IoT network when the network quality is poor.

[0084] In a first aspect, embodiments of this application provide a method for creating a personal Internet of Things (IoT) network, applied to a resident gateway, which is communicatively connected to an electronic device; the electronic device is a device capable of functioning as a Personal IoT Network Component (PEMC) with management capabilities; the resident gateway is a Personal IoT Network Component (PEGC) capable of functioning as a gateway, and a gateway capable of accessing the core network via a wired or wireless network; such as Figure 1 As shown, the method includes:

[0085] Step 101: Determine that the resident gateway has been registered as a PEGC in the core network, and that the electronic device has been registered as a PEMC in the core network.

[0086] For example, the host gateway can be a 5G-RG, the electronic device can be a 5G UE, and the core network can be a 5GC. This method for creating a personal IoT network can be applied to 5G fixed-mobile convergence scenarios. The host gateway and the electronic device can be connected via wired or wireless means. Specifically, the electronic device can access the host gateway via a non-3GPP network (e.g., WLAN, wired, Bluetooth, etc.).

[0087] This application embodiment creates a PIN network in a 5G fixed-mobile convergence scenario through signaling interaction between a 5G UE with PEMC capability, a 5G-RG with PEGC capability, and a 5GC. Specifically, the 5G UE with PEMC capability accesses the 5GC through a 5G fixed-mobile convergence method (e.g., 5G-RG). The 5G-RG has PEGC capability; after PEGC registration with the 5GC, the 5G UE performs PEMC registration, and then enters the PIN creation process. This process solves the problem of the inability to create a PIN in current 5G fixed-mobile convergence scenarios.

[0088] Step 102: Based on the gateway request information sent by the electronic device, send the gateway identifier to the electronic device.

[0089] For example, the resident gateway receives gateway request information sent by the electronic device and sends its own gateway identifier to the electronic device according to the gateway request information.

[0090] Step 103: Receive the network identifier sent by the electronic device; the network identifier is used to indicate that the personal Internet of Things network has been successfully created.

[0091] In one application example, determining that the resident gateway has registered as a PEGC in the core network, and that the electronic device has registered as a PEMC in the core network, includes:

[0092] Send the first registration request to the core network;

[0093] Receive configuration information sent by the core network based on the first registration request; the configuration information indicates that the resident gateway has registered as a PEGC in the core network;

[0094] The second registration request sent by the electronic device is forwarded to the core network; the second registration request is used to request the electronic device to register as a PEMC in the core network;

[0095] The registration success message sent by the core network is sent to the electronic device; the registration success message indicates that the electronic device has registered as a PEMC in the core network.

[0096] Understandably, the first registration request is used to request the resident gateway to register as a PEGC in the core network. The first registration request may include at least one of the following: the resident gateway's first registration type information, first identifier information, and PEGC capability information. The first registration type information can indicate the registration type to which the resident gateway belongs. As an example, the 3GPP standards (TS23.501, 23.502, 33.501) have four registration types: initial registration, mobility registration, periodic registration, and emergency registration. The first identifier information can characterize the resident gateway's identity. As an example, the first identifier information may include SUCI, 5G-GUTI, or PEI in 3GPP. The PEGC capability information may include a gateway identifier (PEGCID), a supported first slice identifier (first slice ID), etc.

[0097] It is understandable that after receiving the configuration information sent by the core network, the corresponding service status configuration is performed based on the configuration information.

[0098] For example, the configuration information may include PEGC capability indication, PEGC subscription type, and PIN network types supported by PEGC. The PEGC subscription type may include a first subscription type, such as a PEGC-only type; a second subscription type, such as a PEGC-enabled type; or a third subscription type, such as a PEGC-disabled type, where ordinary terminals are allowed to access but the resident gateway must be informed that it cannot be used as a PEGC.

[0099] For example, the PEGC capability indicator is used to indicate the identity information of the PEGC carried by the 5G-RG. It can be implemented in various ways such as bit, boolean, and string. For example, a bit type value of "1" indicates that it has PEGC capability; a boolean type value of "true" indicates that it has PEGC capability; and a string type value of "PEGCcapable" indicates that it has PEGC capability.

[0100] For example, the PEGC subscription type is used to indicate the subscription type of PEGC in the unified data management of the core network. It can be implemented in various ways such as bitmap and string. For example, when using bitmap, "00" means PEGC-enabled, "01" means PEGC-only, and "10" means PEGC-disabled. When using string, it includes but is not limited to PEGC-enabled, PEGC-only, and PEGC-disabled.

[0101] In this context, PEGC-enabled indicates that the 5G-RG has signed up for PEGC functionality and can be used as a PEGC in a PIN network, while also supporting access for non-PIN devices. PEGC-only indicates that the 5G-RG has signed up for PEGC functionality and can only be used as a PEGC in a PIN network; non-PIN devices cannot access it. Specifically, this 5G-RG can only connect to devices that meet one of the following conditions: 1) possess PEMC capabilities and have passed 5GC certification; 2) have applied to join a PIN and have passed PMEC certification corresponding to that PIN. PEGC-disabled indicates that the 5G-RG has not signed up for PEGC functionality or that PEGC functionality is disabled, and can only be used as a regular 5G-RG.

[0102] For example, supported PIN network types: This indicates which PIN network types PEGC supports. The implementation can be bitmap, string, etc. When using bitmap, "00" represents Private PIN, "01" represents Public PIN, and "10" represents Personal Body area PIN. When using string, it includes, but is not limited to, "PrivatePIN", "Public PIN" and "Personal Body area PIN".

[0103] Private PIN indicates that the PIN network is a private PIN network, such as a PIN network at home. Public PIN indicates that the PIN network is a public PIN network, such as a PIN network in a shopping mall or supermarket. Personal Body area PIN indicates that the PIN network is a PIN network around the body, such as a PIN network in smartwatches or smart glasses.

[0104] Understandably, the resident gateway can determine the access method of the electronic device based on the second registration request, and then forward the second registration request to the core network according to the access method. By determining the access method of the electronic device, the second registration request information of electronic devices that cannot access the core network can be prevented from being forwarded by the resident gateway, further reducing the amount of information received and processed by the core network due to access failures.

[0105] In one application example, the first registration request includes the first identifier information and PEGC capability information of the residing gateway; the configuration information includes at least the gateway type of the residing gateway; the method further includes:

[0106] The gateway type receiving the core network based on the first identifier information;

[0107] Based on the capability indication information of the electronic device and the gateway type, determine the access method for the electronic device to access the core network;

[0108] The second registration request is forwarded to the core network based on the access method.

[0109] In one application example, based on the electronic device's capability indication information and gateway type, the access method for the electronic device to access the core network is determined, including:

[0110] If the capability indication information indicates that the electronic device has PEMC capability, and the gateway type indicates the type of subscription that the electronic device is allowed to access, then the access method of the electronic device is determined to be the first access method.

[0111] The first access method indicates that the second registration request sent by the electronic device to the resident gateway can be forwarded to the core network, and the electronic device can register as a PEMC in the core network.

[0112] For example, the gateway type can be the PEGC subscription type, used to indicate the PEGC subscription type in the unified data management of the core network. Based on the electronic device's capability indication information and the gateway type, the access method for the electronic device to access the core network is determined. As an example, if the capability indication information indicates that the electronic device has PEMC capabilities, and the gateway type is a first subscription type, a second subscription type, or a third subscription type, the access method for the electronic device is determined to be the first access method. The first access method indicates that the second registration request sent by the electronic device to the residing gateway can be forwarded to the core network, and the device can register as a PEMC in the core network.

[0113] As another example, when the capability indication information indicates that the electronic device does not have PEMC capability, and the gateway type indicates that electronic devices without PEMC capability are allowed to access, and the gateway type is a second subscription type or a third subscription type, the access method of the electronic device can be determined to be the second access method; wherein, the second access method indicates that the second registration request sent by the electronic device to the resident gateway can be forwarded to the core network, but cannot be registered as a PEMC in the core network.

[0114] As another example, if the capability indication information indicates that the electronic device does not have PEMC capability, and the gateway type indicates that electronic devices without PEMC capability are not allowed to access, and the gateway type is the first subscription type, then the access method of the electronic device can be determined to be the third access method; wherein, the third access method indicates that the second registration request sent by the electronic device to the resident gateway cannot be forwarded to the core network, and cannot be registered as a PEMC in the core network.

[0115] Understandably, the resident gateway can forward the second registration request to the core network based on the first access method and / or the second access method.

[0116] In one application example, the second registration request includes at least the electronic device's second identifier information and PEMC capability information; before determining the access method for the electronic device to access the core network based on the electronic device's capability indication information and gateway type, the method further includes:

[0117] Send the instruction request corresponding to the second registration request to the core network; the instruction request includes at least the second identifier information and PEMC capability information from the second registration request.

[0118] The core network receives capability indication information based on the second identifier information and PEMC capability information; the capability indication information represents the indication information corresponding to the PEMC capability information.

[0119] It is understandable that the capability indication information can be a PEMC capability indication. The resident gateway generates an indication request corresponding to the electronic device based on the second registration request, and this indication request is used to obtain the PEMC capability indication of the electronic device.

[0120] For example, PEMC capability indication: used to indicate the identity information of the PEMC carried by the 5G UE, and can be implemented in various ways such as bit, boolean, string, etc. For example: a bit type value of "1" represents having PEMC capability; a boolean type value of "true" represents having PEMC capability; a string type value of "PEMCcapable" represents having PEMC capability.

[0121] Secondly, embodiments of this application provide a method for creating a personal Internet of Things (IoT) network, applied to an electronic device, wherein the electronic device is connected to a resident gateway; the resident gateway is a gateway capable of functioning as a PEGC (Personal Internet of Things Control Center) and capable of accessing the core network via a wired or wireless network; the electronic device is a device capable of functioning as a PEMC (Personal Internet of Things Control Center); such as Figure 2 As shown, the method includes:

[0122] Step 201: Determine that the resident gateway has been registered as a PEGC in the core network, and that the electronic device has been registered as a PEMC in the core network.

[0123] Step 202: Receive the gateway identifier sent by the resident gateway based on the gateway request information.

[0124] For example, the gateway request information may be information sent by an electronic device to a resident gateway, which instructs the resident gateway to send its own gateway identifier to the electronic device.

[0125] Step 203: Receive the network identifier sent by the personal IoT server based on the creation request information through the core network; the creation request information includes at least the management identifier and gateway identifier of the electronic device; the network identifier is used to indicate that the personal IoT network has been successfully created.

[0126] For example, the electronic device sends a creation request to the core network and receives a network identifier sent by a personal IoT server based on the creation request. The personal IoT server can be a Personal IoT Application Function (PIN AF); the network identifier can be a Personal IoT Network Identifier (PIN ID).

[0127] Step 204: Send the network identifier to the resident gateway.

[0128] Step 205: Designate the resident gateway as the PEGC of the Personal IoT Network based on the gateway identifier.

[0129] For example, the gateway identifier can be used as specified information, and the electronic device, as a PEMC, can save the specified information, thereby realizing the PEGC of the resident gateway as a personal IoT network.

[0130] In this embodiment of the application, an electronic device that has completed PEMC registration in the core network can directly send creation request information, including the management identifier of the electronic device and the gateway identifier of the gateway, to the core network by obtaining the gateway identifier of the resident gateway that has completed PEMC registration in the core network.

[0131] In one application example, determining that an electronic device has registered as a PEMC in the core network includes:

[0132] The second registration request is sent to the core network through the resident gateway; the second registration request is used to request the electronic device to register as a PEMC in the core network;

[0133] Receive registration success information sent by the resident gateway; registration success information indicates that the electronic device has registered as a PEMC in the core network.

[0134] It is understood that the second registration request may include at least one of the following: second registration type information for the electronic device, second identifier information, and PEMC capability information. The description of the second registration type information can be referenced from the first registration type information and will not be repeated here. The second identifier information can be used to characterize the electronic device's identity; the specific details can be found in the description of the first identifier information. The PEMC capability information may include a management identifier (PEMC ID), a supported second slice identifier (second slice ID), etc.

[0135] For example, PEMC ID: a unique identifier for a device with PEMC capability in a PIN network, which can be implemented in ways including but not limited to: MSISDN, IMSI, SUPI, SUCI, IP address, MAC address, PEI.

[0136] Understandably, after receiving the registration success message from the resident gateway, the electronic device, acting as the PEMC, creates a PIN network. Specifically, the electronic device, as the PEMC, obtains the gateway identifier of the resident gateway from the resident gateway.

[0137] In one application example, the method also includes:

[0138] Broadcasting network information of a personal Internet of Things (IoT) network; the network information includes at least a network identifier;

[0139] Receive network access request information from IoT terminals in response to network information transmission;

[0140] If it is determined that an IoT terminal is to be registered with the network, a terminal identifier corresponding to the IoT terminal is generated based on the network registration request information.

[0141] For example, network information may also include name information for the personal IoT network. It is understood that network identifier and name information can respectively represent the identity information of the personal IoT network from the identifier dimension and the name dimension.

[0142] For example, when an IoT terminal receives network information, the IoT terminal will send a network access request to the electronic device; the network access request may include network identifier, identity identifier (device ID) and type information (PINE type).

[0143] For example, the electronic device acting as the PEMC can determine whether an IoT terminal is allowed to join a personal IoT network. The determination process can be determined according to the actual situation and is not limited here. The terminal identifier can be a type identifier (PINEID).

[0144] Thirdly, embodiments of this application provide a method for creating a personal Internet of Things (IoT) network, applied to a core network, wherein the core network is connected to an electronic device and a resident gateway; the electronic device is a device capable of functioning as a PEMC (Personal Internet of Things Controller); the gateway is a gateway capable of functioning as a PEMC and capable of accessing the core network via a wired or wireless network; such as Figure 3 As shown, the method includes:

[0145] Step 301: Determine that the resident gateway has been registered as a PEGC in the core network, and that the electronic device has been registered as a PEMC in the core network.

[0146] For example, the core network may include an Access and Mobility Management Function (AMF), an Authentication Server Function (AUSF), and Unified Data Management (UDM).

[0147] Step 302: Forward the creation request information sent by the electronic device to the personal IoT server; the creation request information includes at least the management identifier of the electronic device and the gateway identifier of the gateway.

[0148] Step 303: Forward the network identifier sent by the personal IoT server based on the management identifier and gateway identifier to the electronic device; the network identifier is used to indicate that the personal IoT network has been successfully created.

[0149] In one application example, determining that the resident gateway has registered as a PEGC in the core network, and that the electronic device has registered as a PEMC in the core network, includes:

[0150] Receive the first registration request sent by the resident gateway;

[0151] Send configuration information to the resident gateway; the configuration information indicates that the resident gateway has registered as a PEGC in the core network;

[0152] The system receives a second registration request from an electronic device through a resident gateway; the second registration request is used to request the electronic device to register as a PEMC in the core network.

[0153] The registration success information generated based on the second registration request is sent to the resident gateway; the registration success information indicates that the electronic device has registered as a PEMC in the core network.

[0154] It should be noted that when the AMF (Advanced Management Function) of the core network receives the first registration request, it forwards the request to the AUSF (Automatic Access Default Server) of the core network. The AUSF then authenticates the residing gateway based on the first identifier information in the first registration request, obtaining the first authentication result. Specifically, it can query the AUSF to determine if the residing gateway is a legitimate user. If it is, authentication succeeds; otherwise, authentication fails. The AUSF pre-stores information on whether each residing gateway is a legitimate or illegitimate user.

[0155] If the first authentication result indicates that the resident gateway authentication has failed, a first failure message is generated and sent to the AMF in the core network. If the first authentication result indicates that the resident gateway authentication has succeeded, a first success message is generated and sent to the AMF in the core network.

[0156] The AMF of the core network can forward the first failure information to the resident gateway, or it can choose not to forward the first failure information. That is, if the resident gateway receives the first failure information or does not receive a reply message from the AMF of the core network after a preset interval, it is determined that the resident gateway registration has failed.

[0157] After receiving the first success message, the AMF of the core network generates a subscription request information for the resident gateway based on the first registration request; and sends the subscription request information and the first registration request to the UDM of the core network.

[0158] In one application example, the first registration request includes the first identifier information and PEGC capability information of the residing gateway; after receiving the first registration request sent by the residing gateway, the method further includes:

[0159] Store PEGC capability information;

[0160] The configuration information corresponding to the resident gateway is determined based on the first identifier information.

[0161] It should be noted that after the core network's UDM receives the subscription request information and the first registration request sent by the core network's AMF, it saves the PEGC capability information in the first registration request; and queries the configuration information corresponding to the resident gateway based on the first identifier information.

[0162] It should be noted that after the core network's UDM queries the configuration information corresponding to the resident gateway, it generates the registration result of the resident gateway, sends the registration result to the resident gateway, and the registration result carries the configuration information.

[0163] It should be noted that the core network can also register electronic devices based on their access method, thus making the electronic devices registered as PEMCs. The registration process can be determined according to the actual situation and is not limited here. As an example, electronic devices can be registered in 5G according to the 5G UE registration process in 3GPP.

[0164] In one application example, the second registration request includes at least the first identifier information and PEMC capability information of the electronic device; the method further includes receiving the second registration request sent by the electronic device through a resident gateway:

[0165] Receive an indication request sent by the resident gateway; the indication request corresponds to a second registration request sent by the electronic device; the indication request includes at least the second identifier information and PEMC capability information from the second registration request;

[0166] Capability indication information is determined based on the second identifier information and PEMC capability information; the capability indication information represents the indication information corresponding to the PEMC capability information.

[0167] Send capability indication information to the resident gateway;

[0168] Receive the second registration request sent by the resident gateway based on capability indication information.

[0169] It should be noted that the AMF (Advanced Functions Provider) of the core network receives the instruction request and forwards it to the AUSF (Authorization and Authentication Service) of the core network. The AUSF of the core network authenticates the electronic device based on the second identifier information in the instruction request and obtains a second authentication result. Specifically, it can query the AUSF of the core network to determine whether the electronic device is a legitimate user. If it is a legitimate user, authentication succeeds; otherwise, authentication fails. The AUSF of the core network pre-stores information on whether each electronic device is a legitimate or illegitimate user.

[0170] If the second authentication result indicates that the electronic device authentication has failed, a second failure message is generated and sent to the AMF (Authentication, Authorization, and Function) of the core network. If the second authentication result indicates that the electronic device authentication has succeeded, a second success message is generated and sent to the AMF of the core network. After receiving the second success message, the AMF of the core network will forward the instruction request to the UDM (User Device Management) of the core network.

[0171] After receiving the indication request from the AMF in the core network, the UDM in the core network queries the capability indication information corresponding to the electronic device based on the second identifier information, and then sends the capability indication information to the AMF in the core network. Upon receiving the capability indication information, the AMF in the core network forwards it to the resident gateway.

[0172] The AMF of the core network can forward the second failure information to the electronic device, or it can choose not to forward the second failure information. That is, if the electronic device receives the second failure information or does not receive a reply message from the AMF of the core network after a preset interval, the registration of the electronic device is determined to have failed.

[0173] The following example illustrates the method for creating a personal Internet of Things (IoT) network according to an embodiment of this application, specifically a method for creating a PIN network in a 5G fixed-mobile convergence scenario.

[0174] like Figure 4 As shown, the innovative technical solution proposed in this application is implemented through three processes, specifically including the following steps:

[0175] Step 401: The process of 5G-RG registering PEGC capability with 5GC: In this process, 5G-RG with PEGC capability is registered with 5GC. After 5GC authenticates the identity of 5G-RG, it returns the PEGC subscription configuration information stored in UDM to 5G-RG.

[0176] Step 402: The process of 5G UE registering PEMC capability with 5GC through 5G-RG: In this process, 5G UE registers with 5GC through 5G-RG to achieve 5G fixed-mobile convergence, carrying PEMC capability information; after receiving the 5G UE registration request, 5G-RG first initiates identity authentication and PEMC capability authentication of 5G UE with 5GC; then, if the 5G UE identity authentication is successful and it has PEMC capability, 5G UE performs the normal PEMC registration process through 5G-RG.

[0177] Step 403: PIN Creation Process: After completing the PEGC capability registration of 5G-RG and the PEMC capability registration of 5G UE, 5G UE, as PEMC, obtains PEGC information from 5G-RG and enters the PIN network creation process.

[0178] like Figure 5 As shown, a 5G-RG configured with PEGC capabilities initiates a registration process with the 5GC to authenticate its identity and obtain subscription configuration information. The process of a 5G-RG registering its PEGC capabilities with the 5GC specifically includes the following steps:

[0179] Step 501: Send a registration request (carrying PEGC capability). The 5G-RG sends a registration request to the 5GC. The request includes parameters such as registration type, user identifier (SUCI, 5G-GUTI, or PEI in 3GPP), requested slice, and PEGC capability information. The PEGC capability information includes, but is not limited to, PEGCID and supported slice IDs.

[0180] Step 502: Authentication and Authorization. The AMF receives the registration information and authenticates the 5G-RG with the AUSF based on parameters such as the user identifier provided by the 5G-RG. The AUSF authenticates the 5G-RG's identity. If the authentication is successful, proceed to step 503; if the authentication fails, reply to the AMF with "Authentication failed, the user is an unauthorized user".

[0181] Step 503: Obtain PEGC Subscription Information. The UDM receives the "Obtain 5G-RG PEGC Subscription Information" request sent by the AMF, saves the PEGC capability information, and queries the PEGC subscription configuration information based on the PEGC ID provided by the 5G-RG, including but not limited to the PEGC capability indicator, the PEGC subscription type, and the PIN network types supported by the PEGC. The PEGC subscription types include, but are not limited to, PEGC-enabled, PEGC-only, and PEGC-disabled; the supported PIN network types include, but are not limited to, Private PIN, Public PIN, and Personal Body area PIN.

[0182] Step 504: Registration complete, registration result returned. After the 5GC registration process is completed, the registration result is returned to 5G-RG, carrying information such as the PEGC contract type and the PIN network types supported by the PEGC.

[0183] After the above process is completed, 5G-RG will determine the corresponding service status based on the contract information returned by 5GC.

[0184] like Figure 6 As shown, when a 5G UE is in an area with weak 5G signal and cannot directly connect to the 5GC for registration, the 5G UE can access the 5GC for registration via 5G-RG using a 5G fixed-mobile convergence method. The process of a 5G UE registering PEMC capabilities with the 5GC via 5G-RG specifically includes the following steps:

[0185] Step 601: Send a registration request (carrying PEMC capability information). The 5G UE initiates a registration request to the 5GC through the 5G-RG, including user parameters such as registration type, user identifier slice, and PEMC capability information. The PEMC capability information includes, but is not limited to, PEMC ID and supported slice IDs.

[0186] Step 602: Initiate a "Get PEMC Capability Indicator of 5G UE" request. After receiving the 5G UE registration request and obtaining the PEMC capability information of the 5G UE, the 5G-RG initiates a "Get PEMC Capability Indicator of 5G UE" request to the 5GC, which carries information such as the 5G UE's user identifier and PEMC ID.

[0187] Step 603: User authentication. The AMF receives the 5G-RG request from Step 2 and initiates user authentication for the UE to the AMF. The AMF checks whether the UE is a legitimate user based on the UE's user identifier. If yes, it returns "The UE is a legitimate user" to the AMF and proceeds to Step 4; otherwise, the AMF returns "Query failed, the user is an illegitimate user and registration is not allowed" to the AMF.

[0188] Step 604: Obtain the "PEMC Capability Indicator" information of the 5G UE. The AMF requests the UDM to obtain the "PEMC Capability Indicator" information of the 5G UE. The UDM queries based on the PEMC ID and returns the query result to the AMF.

[0189] Step 605: Return "PEMC Capability Indication" information. AMF returns the query results from UDM to 5G-RG. Based on its PEGC type and the PEMC capability indication information of the 5G UE, 5G-RG obtains the PEGC judgment result.

[0190] Step 606: Forward the 5G UE's registration request. As shown in Table 1, if the PEGC judgment result is Case 1, Case 2, Case 3, Case 5, or Case 6, then the 5G-RG forwards the 5G UE's registration request. However, the 5G UE can only register its PEMC capability under Case 1, Case 2, and Case 3. Subsequent registration procedures refer to the current 5G UE registration process in 3GPP.

[0191] After the above process is completed, the 5G UE completes PEMC capability registration and enters the PIN network creation process.

[0192] Table 1 lists the correspondences between PEGC types and PEMC capability indicators.

[0193]

[0194]

[0195] like Figure 7 As shown, in this scheme, after completing the PEGC capability registration of the 5G-RG and the PEMC capability registration of the 5G UE, the PEMC initiates the PIN creation process to the 5GC. The PIN creation process specifically includes the following steps:

[0196] Step 701: Obtain PEGC ID. The 5G UE, acting as the PEMC, obtains the PEGC ID information from the 5G-RG.

[0197] Step 702: Request the establishment of a PIN network and obtain the PIN ID from the PIN AS. The 5G UE initiates the creation of a PIN network with the 5GC, carrying information such as PEMC ID and PEGC ID, and obtains the PIN ID from the PIN AF.

[0198] Step 703: Send PIN ID and designate 5G-RG as the PEGC PIN. The 5G UE (i.e., PEMC) sends the PIN ID to the PEGC (i.e., 5G-RG) and designates 5G-RG as the PEGC in the PIN network.

[0199] Step 704: PIN device adds PIN. PEMC broadcasts PIN network information, including PIN ID, PIN name, etc.

[0200] If an IoT terminal device discovers a PIN network, it requests to join the PIN network from the PEMC, carrying information including but not limited to PIN ID, device ID, PINE type, etc.; the PEMC decides whether to join the PIN and assigns a PINE ID to the device.

[0201] The slice type indicator supported in this application embodiment is used to indicate the network slice type supported by PEGC or PEMC. The implementation method can be bitmap, string, etc. When bitmap is used, it is represented by 6-bit binary number, "000000" represents slice A, "000001" represents slice B; when string is used, "NSSAI A" indicates that slice A is supported, "NSSAI B" indicates that slice B is supported.

[0202] Fourthly, based on the hardware implementation of the above-mentioned program modules, and in order to implement the method of residing on the gateway side in the embodiments of this application, the embodiments of this application provide a residing gateway. Figure 8 This is only an exemplary structure of the resident gateway, not the entire structure; implementation is possible as needed. Figure 8 The structure shown may be part or all of the structure.

[0203] like Figure 8 As shown, the resident gateway 800 provided in this embodiment includes at least one processor 801, a memory 802, and a user interface 803. The various components in the resident gateway 800 are coupled together via a bus system 804. It can be understood that the bus system 804 is used to implement communication between these components. In addition to a data bus, the bus system 804 also includes a power bus, a control bus, and a status signal bus. However, for clarity, in... Figure 8 The general labeled all buses as Bus System 804.

[0204] The user interface 803 may include a monitor, keyboard, mouse, trackball, click wheel, buttons, touchpad, or touch screen.

[0205] The memory 802 in this embodiment is used to store various types of data to support the operation of the resident gateway. Examples of such data include any computer program used to operate on the resident gateway.

[0206] The method for creating a personal IoT network for a resident gateway disclosed in this application can be applied to or implemented by a processor 801. The processor 801 may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the method for creating a personal IoT network for a resident gateway can be completed by integrated logic circuits in the hardware of the processor 801 or by instructions in software form. The processor 801 can be a general-purpose processor, a digital signal processor (DSP), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The processor 801 can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. A general-purpose processor can be a microprocessor or any conventional processor, etc. The steps of the method disclosed in the embodiments of this application can be directly manifested as execution by a hardware decoding processor, or execution by a combination of hardware and software modules in the decoding processor. The software modules can be located in a storage medium, specifically memory 802. The processor 801 reads information from memory 802 and, in conjunction with its hardware, completes the steps of the method for creating a personal IoT network for a resident gateway provided in the embodiments of this application.

[0207] In an exemplary embodiment, the resident gateway 800 may be implemented by one or more application-specific integrated circuits (ASICs), DSPs, programmable logic devices (PLDs), complex programmable logic devices (CPLDs), field-programmable gate arrays (FPGAs), general-purpose processors, controllers, microcontrollers (MCUs), microprocessors, or other electronic components to perform the aforementioned methods.

[0208] Fifthly, based on the hardware implementation of the above-mentioned program modules, and in order to implement the method on the electronic device side of the embodiments of this application, the embodiments of this application provide an electronic device. Figure 9 The diagram shows only an exemplary structure of the electronic device, not the entire structure; implementation is possible as needed. Figure 9 The structure shown may be part or all of the structure.

[0209] like Figure 9As shown, the electronic device 900 provided in this application embodiment includes at least one processor 901, a memory 902, and a user interface 903. The various components in the electronic device 900 are coupled together via a bus system 904. It can be understood that the bus system 904 is used to implement communication between these components. In addition to a data bus, the bus system 904 also includes a power bus, a control bus, and a status signal bus. However, for clarity, in... Figure 9 The general designated all buses as Bus System 904.

[0210] The user interface 903 may include a monitor, keyboard, mouse, trackball, click wheel, buttons, touchpad, or touch screen.

[0211] The memory 902 in this embodiment is used to store various types of data to support the operation of the electronic device. Examples of such data include any computer program used to operate on the electronic device.

[0212] The method for creating a personal Internet of Things (IoT) network for an electronic device disclosed in this application can be applied to or implemented by a processor 901. The processor 901 may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the method for creating a personal IoT network for an electronic device can be completed by integrated logic circuits in the hardware of the processor 901 or by instructions in software form. The processor 901 can be a general-purpose processor, a DSP, or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The processor 901 can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. A general-purpose processor can be a microprocessor or any conventional processor, etc. The steps of the method disclosed in the embodiments of this application can be directly manifested as execution by a hardware decoding processor, or execution by a combination of hardware and software modules in the decoding processor. The software modules can be located in a storage medium, specifically a memory 902. The processor 901 reads information from the memory 902 and, in conjunction with its hardware, completes the steps of the method for creating a personal IoT network for an electronic device provided in the embodiments of this application.

[0213] In an exemplary embodiment, the electronic device 900 may be implemented by one or more ASICs, DSPs, PLDs, CPLDs, FPGAs, general-purpose processors, controllers, MCUs, microprocessors, or other electronic components to perform the aforementioned method.

[0214] Sixthly, based on the hardware implementation of the above-mentioned program modules, and in order to implement the method on the network device side of the embodiments of this application, the embodiments of this application provide a network device. Figure 10This is only an exemplary structure of the network device, not the entire structure; implementation is possible as needed. Figure 10 The structure shown may be part or all of the structure.

[0215] like Figure 10 As shown, the network device 1000 provided in this embodiment includes at least one processor 1001, a memory 1002, and a user interface 1003. The various components in the network device 1000 are coupled together via a bus system 1004. It can be understood that the bus system 1004 is used to implement communication between these components. In addition to a data bus, the bus system 1004 also includes a power bus, a control bus, and a status signal bus. However, for clarity, in… Figure 10 The general labeled all buses as Bus System 1004.

[0216] The user interface 1003 may include a monitor, keyboard, mouse, trackball, click wheel, buttons, touchpad, or touch screen.

[0217] The memory 1002 in this embodiment is used to store various types of data to support the operation of the network device. Examples of such data include any computer program used to operate on the network device.

[0218] The method for creating a personal Internet of Things (IoT) network for a network device disclosed in this application can be applied to or implemented by a processor 1001. The processor 1001 may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the method for creating a personal IoT network for a network device can be completed by integrated logic circuits in the hardware of the processor 1001 or by instructions in software form. The processor 1001 can be a general-purpose processor, a DSP, or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The processor 1001 can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. A general-purpose processor can be a microprocessor or any conventional processor, etc. The steps of the method disclosed in the embodiments of this application can be directly manifested as execution by a hardware decoding processor, or execution by a combination of hardware and software modules in the decoding processor. The software modules can be located in a storage medium, specifically memory 1002. The processor 1001 reads information from memory 1002 and, in conjunction with its hardware, completes the steps of the method for creating a personal IoT network for a network device provided in the embodiments of this application.

[0219] In an exemplary embodiment, the network device 1000 may be implemented by one or more ASICs, DSPs, PLDs, CPLDs, FPGAs, general-purpose processors, controllers, MCUs, microprocessors, or other electronic components to perform the aforementioned method.

[0220] It is understood that the memory (memory 802, memory 902, memory 1002) can be volatile memory or non-volatile memory, or both. Non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), ferromagnetic random access memory (FRAM), flash memory, magnetic surface memory, optical disc, or compact disc read-only memory (CD-ROM); magnetic surface memory can be disk storage or magnetic tape storage. Volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Synchronous Static Random Access Memory (SSRAM), 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), SyncLink Dynamic Random Access Memory (SLDRAM), and Direct Rambus Random Access Memory (DRRAM).The memories described in the embodiments of this application are intended to include, but are not limited to, these and any other suitable types of memories.

[0221] It should be noted that terms such as "first" and "second" are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence.

[0222] Furthermore, the technical solutions described in the embodiments of this application can be combined arbitrarily without conflict.

[0223] The above are merely specific embodiments of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for creating a personal Internet of Things (IoT) network, characterized in that, The method is applied to a resident gateway, which is communicatively connected to an electronic device; the electronic device is a Personal Internet of Things (PEMC) device capable of being managed; the resident gateway is a PEMC capable of being a gateway device and a gateway capable of accessing the core network via a wired or wireless network; the method includes: It is determined that the resident gateway has been registered as a PEGC in the core network, and the electronic device has been registered as a PEMC in the core network; the resident gateway is 5G-RG; Based on the gateway request information sent by the electronic device, send a gateway identifier to the electronic device; Receives a network identifier sent by the electronic device; the network identifier is used to indicate that the personal Internet of Things network has been successfully created. Determining that an electronic device has been registered as a PEMC in the core network includes: The second registration request sent by the electronic device is forwarded to the core network; the second registration request is used to request the electronic device to register as a PEMC in the core network. The registration success information sent by the core network is sent to the electronic device; the registration success information indicates that the electronic device has registered as a PEMC in the core network.

2. The method according to claim 1, characterized in that, The step of determining that the resident gateway has registered as a PEGC in the core network includes: Send a first registration request to the core network; The configuration information sent by the core network based on the first registration request is received; the configuration information indicates that the resident gateway has registered as a PEGC in the core network.

3. The method according to claim 2, characterized in that, The first registration request includes the first identifier information and PEGC capability information of the resident gateway; the configuration information includes at least the gateway type of the resident gateway; The step of forwarding the second registration request sent by the electronic device to the core network includes: Receive the gateway type sent by the core network based on the first identifier information; Based on the capability indication information of the electronic device and the gateway type, determine the access method for the electronic device to access the core network; Based on the access method, the second registration request is forwarded to the core network.

4. The method according to claim 3, characterized in that, The step of determining the access method for the electronic device to access the core network based on the capability indication information of the electronic device and the gateway type includes: If the capability indication information indicates that the electronic device has PEMC capability, and the gateway type indicates the subscription type that allows the electronic device to access, then the access method of the electronic device is determined to be the first access method. The first access method indicates that the second registration request sent by the electronic device to the resident gateway can be forwarded to the core network, and the electronic device can register as a PEMC in the core network.

5. The method according to claim 3, characterized in that, The second registration request includes at least the second identifier information and PEMC capability information of the electronic device; before determining the access method of the electronic device to access the core network based on the capability indication information of the electronic device and the gateway type, the method further includes: The instruction request corresponding to the second registration request is sent to the core network; the instruction request includes at least the second identifier information and PEMC capability information from the second registration request. Receive capability indication information sent by the core network based on the second identifier information and the PEMC capability information; The capability indication information represents the indication information corresponding to the PEMC capability information.

6. A method for creating a personal Internet of Things (IoT) network, characterized in that, This is applied to electronic devices connected to a resident gateway; the resident gateway is a gateway that can act as a PEGC and can access the core network via a wired or wireless network. The electronic device is a device capable of functioning as a PEMC; the method includes: It is determined that the resident gateway has been registered as a PEGC in the core network, and the electronic device has been registered as a PEMC in the core network; the resident gateway is 5G-RG; Receive the gateway identifier sent by the resident gateway based on the gateway request information; The core network receives a network identifier sent by the personal IoT server based on a creation request information; the creation request information includes at least the management identifier of the electronic device and the gateway identifier; the network identifier is used to indicate that the personal IoT network has been successfully created. Send the network identifier to the resident gateway; The resident gateway is designated as the PEGC of the personal IoT network based on the gateway identifier; The determination that the electronic device has been registered as a PEMC in the core network includes: The electronic device sends a second registration request to the core network through the resident gateway; the second registration request is used to request the electronic device to register as a PEMC in the core network. The system receives a registration success message sent by the resident gateway; the registration success message indicates that the electronic device has registered as a PEMC in the core network.

7. The method according to claim 6, characterized in that, The method further includes: Broadcasting network information of the personal Internet of Things network; the network information includes at least the network identifier; Receive network access request information sent by the Internet of Things terminal in response to the network information; If it is determined that the IoT terminal has joined the network, a terminal identifier corresponding to the IoT terminal is generated based on the network joining request information.

8. A method for creating a personal Internet of Things (IoT) network, characterized in that, It is applied to the core network, which is connected to electronic devices and resident gateways respectively; the electronic devices are devices that can act as PEMCs. The gateway is a gateway capable of functioning as a PEGC and capable of accessing the core network via a wired or wireless network; the method includes: It is determined that the resident gateway has been registered as a PEGC in the core network, and the electronic device has been registered as a PEMC in the core network; the creation request information sent by the electronic device is forwarded to the personal IoT server; the creation request information includes at least the management identifier of the electronic device and the gateway identifier of the gateway; the resident gateway is 5G-RG; The network identifier sent by the personal IoT server based on the management identifier and the gateway identifier is forwarded to the electronic device; the network identifier is used to indicate that the personal IoT network has been successfully created. Determining that an electronic device has been registered as a PEMC in the core network includes: The electronic device receives a second registration request from the resident gateway; the second registration request is used to request the electronic device to register as a PEMC in the core network. The registration success information generated based on the second registration request is sent to the resident gateway; the registration success information indicates that the electronic device has registered as a PEMC in the core network.

9. The method according to claim 8, characterized in that, The step of determining that the resident gateway has registered as a PEGC in the core network includes: Receive the first registration request sent by the resident gateway; Send configuration information to the resident gateway; the configuration information indicates that the resident gateway has registered as a PEGC in the core network.

10. The method according to claim 9, characterized in that, The first registration request includes the first identifier information and PEGC capability information of the resident gateway; after receiving the first registration request sent by the resident gateway, the method further includes: The PEGC capability information is stored; The configuration information corresponding to the resident gateway is determined based on the first identifier information.

11. The method according to claim 8, characterized in that, The second registration request includes at least the first identifier information and PEMC capability information of the electronic device; receiving the second registration request sent by the electronic device through the resident gateway includes: Receive an indication request sent by the resident gateway; the indication request corresponds to a second registration request sent by the electronic device; the indication request includes at least the second identifier information and PEMC capability information from the second registration request; Capability indication information is determined based on the second identifier information and the PEMC capability information; the capability indication information represents the indication information corresponding to the PEMC capability information. Send the capability indication information to the resident gateway; Receive the second registration request sent by the resident gateway based on the capability indication information.

12. A resident gateway, characterized in that, include: A first processor and a first memory for storing computer programs capable of running on the first processor. Wherein, when the first processor is used to run the computer program, it performs the steps of the method according to any one of claims 1 to 5.

13. An electronic device, characterized in that, include: A second processor and a second memory for storing computer programs capable of running on the second processor. Wherein, when the second processor is used to run the computer program, it performs the steps of the method according to any one of claims 6 to 7.

14. A network device, characterized in that, include: A third processor and a third memory for storing computer programs capable of running on the third processor. When the third processor runs the computer program, it performs the steps of the method according to any one of claims 8 to 11.

15. A storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 5, or the steps of the method according to any one of claims 6 to 7, or the steps of the method according to any one of claims 8 to 11.

Images