Individual Internet of Things network creation method and device, and storage medium

Abstract

The invention provides an Internet of Things network creation method and device and a storage medium, applied to a resident gateway, and the resident gateway is in communication connection with an electronic device. The electronic equipment can be used as PEMC equipment; the resident gateway is a gateway which can be used as a PEGC and can be accessed to the core network through a wired network or a wireless network; the method comprises the following steps: determining that a resident gateway is registered as a PEGC in a core network and an electronic device is registered as a PEMC in the core network; sending a gateway identifier to the electronic equipment based on gateway request information sent by the electronic equipment; receiving a network identifier sent by the electronic equipment; the network identifier is used for representing that the individual Internet of Things network is successfully created, so that the individual Internet of Things network is created under the condition that the network quality is poor.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a method, device and storage medium for establishing a personal Internet of Things network. Background Art

[0002] In the related technology, the Personal IoT Network (PIN) can be applied to medical, educational, family, industrial and other scenarios. However, if there are areas with no 5G signal coverage or poor signal quality in indoor scenarios, the 5G User Equipment (5G UE) with the Personal IoT Network Element with Gateway Capability (PEMC) cannot directly connect to the 5G Core Network (5GC) for the registration process, resulting in the failure to establish the PIN network normally. At this time, the normal operation of network services cannot be guaranteed. There is currently no effective solution to this problem. Summary of the invention

[0003] In view of this, the embodiments of the present application provide a method, device and storage medium for creating a personal Internet of Things network, aiming to effectively solve the problem of creating a personal Internet of Things network when the network quality is poor.

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

[0005] In a first aspect, an embodiment of the present application provides a method for creating a personal Internet of Things network, which is applied to a resident gateway, wherein the resident gateway is communicatively connected to an electronic device; the electronic device is a device that can be used as a personal Internet of Things network element PEMC with management capabilities; the resident gateway is a personal Internet of Things network element PEGC that can be used as a gateway function, and a gateway that can access a core network through a wired network or a wireless network; the method includes:

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

[0007] Sending a gateway identifier to the electronic device based on the gateway request information sent by the electronic device;

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

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

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

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

[0012] Forwarding a second registration request sent by the electronic device 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 is registered in the core network as a PEMC.

[0014] In some embodiments, 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] receiving a gateway type sent by the core network based on the first identifier information;

[0016] Determining, according to the capability indication information of the electronic device and the gateway type, an access mode for the electronic device to access the core network;

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

[0018] In some implementation schemes, determining, according to the capability indication information of the electronic device and the gateway type, an access mode for the electronic device to access the core network includes:

[0019] When the capability indication information indicates that the electronic device has PEMC capability and the gateway type indicates a subscription type that allows the electronic device to access, determining that the access mode of the electronic device is the first access mode;

[0020] The first access mode 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 be registered in the core network as a PEMC.

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

[0022] Sending an indication request corresponding to the second registration request to the core network; the indication request at least includes the second identifier information and the PEMC capability information in the second registration request;

[0023] 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 indication information corresponding to the PEMC capability information.

[0024] In a second aspect, an embodiment of the present application provides a method for creating a personal Internet of Things network, which is applied to an electronic device, wherein the electronic device is connected to a resident gateway; the resident gateway is a gateway that can serve as a PEGC and can access a core network through a wired network or a wireless network; the electronic device is a device that can serve as a PEMC; the method includes:

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

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

[0027] Receiving, through the core network, a network identifier sent by the personal Internet of Things server based on the creation request information; the creation request information at least includes the management identifier of the electronic device and the gateway identifier; the network identifier is used to indicate that the personal Internet of Things network is successfully created;

[0028] Sending the network identification to the resident gateway;

[0029] The resident gateway is used as the PEGC of the personal Internet of Things network based on the gateway identifier.

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

[0031] Sending 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] Receive registration success information sent by the resident gateway; the registration success information indicates that the electronic device is registered in the core network as a PEMC.

[0033] In some embodiments, the method further comprises:

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

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

[0036] If it is determined that the Internet of Things terminal has accessed the network, a terminal identifier corresponding to the Internet of Things terminal is generated based on the network access request information.

[0037] In a third aspect, an embodiment of the present application provides a method for creating a personal Internet of Things network, which is applied to a core network, wherein the core network is connected to an electronic device and a resident gateway respectively; the electronic device is a device that can serve as a PEMC; the gateway is a gateway that can serve as a PEGC and can access the core network through a wired network or a wireless network; the method includes:

[0038] 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; forward the creation request information sent by the electronic device to the personal Internet of Things 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 Internet of Things 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 Internet of Things network is successfully created.

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

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

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

[0043] receiving, through the resident gateway, a second registration request sent by the electronic device; the second registration request is used to request the electronic device to register as a PEMC in the core network;

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

[0045] In some embodiments, 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] Storing the PEGC capability information;

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

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

[0049] receiving 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 at least includes the second identifier information and the PEMC capability information in the second registration request;

[0050] Determine capability indication information based on the second identifier information and the PEMC capability information; the capability indication information represents indication information corresponding to the PEMC capability information;

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

[0052] A second registration request is received, which is sent by the resident gateway based on the capability indication information.

[0053] In a fourth aspect, an embodiment of the present application provides a resident gateway, comprising: a first processor and a first memory for storing a computer program that can be run on the first processor,

[0054] Among them, 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 embodiment of the present application.

[0055] In a fifth aspect, an embodiment of the present application provides an electronic device, comprising: a second processor and a second memory for storing a computer program that can be run on the second processor,

[0056] Among them, 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 embodiment of the present application.

[0057] In a sixth aspect, an embodiment of the present application provides a network device, comprising: a third processor and a third memory for storing a computer program that can be run on the third processor,

[0058] Among them, the third processor is used to execute the steps of the method described in the third aspect of the embodiment of the present application when running the computer program.

[0059] In the seventh aspect, an embodiment of the present application provides a storage medium on which a computer program is stored. When the computer program is executed by a processor, the steps of the method described in the first aspect of the embodiment of the present application are implemented, or the steps of the method described in the second aspect of the embodiment of the present application are implemented, or the steps of the method described in the third aspect of the embodiment of the present application are implemented.

[0060] The embodiment of the present application provides a method, device and storage medium for creating a personal Internet of Things network, which is applied to a resident gateway, wherein the resident gateway is connected to an electronic device in communication; the electronic device is a device that can be used as a personal Internet of Things network element PEMC with management capabilities; the resident gateway is a personal Internet of Things network element PEGC that can be used as a gateway function, and a gateway that can access the core network through a wired network or a wireless network; the method includes: 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; based on the gateway request information sent by the electronic device, sending a gateway identifier to the electronic device; receiving a network identifier sent by the electronic device; the network identifier is used to indicate that the personal Internet of Things network is successfully created. By adopting the technical solution of the embodiment of the present application, the resident gateway can be registered as a PEGC in the core network; the electronic device can be registered 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 sent by the electronic device indicating that the personal Internet of Things network is successfully created is received, so as to achieve the creation of a personal Internet of Things network under poor network quality. BRIEF DESCRIPTION OF THE DRAWINGS

[0061] Figure 1 This is a schematic diagram of the implementation process of the method for creating a personal Internet of Things network on the resident gateway side according to an embodiment of the present application;

[0062] Figure 2 This is a schematic diagram of the implementation process of the method for creating a personal Internet of Things network on the electronic device side according to an embodiment of the present application;

[0063] Figure 3 This is a schematic diagram of the implementation process of the method for creating a personal Internet of Things network on the network device side according to an embodiment of the present application;

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

[0065] Figure 5 This is a flow chart of the process of 5G-RG registering PEGC capability with 5GC in an embodiment of the present application;

[0066] Figure 6 This is a flow chart of a 5G UE registering PEMC capability through a 5G-RG in an embodiment of the present application;

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

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

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

[0070] Fig.10 This is a schematic diagram of the structure of the network device according to an embodiment of the present application. DETAILED DESCRIPTION

[0071] The present application is further described in detail below in conjunction with the accompanying drawings and embodiments.

[0072] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as those commonly understood by those skilled in the art to which this application belongs. The terms used herein in the specification of this application are only for the purpose of describing specific embodiments and are not intended to limit this application.

[0073] In the related technologies, 5G, as a new generation of communication technology, uses its large bandwidth, low latency, high reliability, and wide connection characteristics to provide the necessary network infrastructure support for vertical industry applications. At the same time, vertical industries have generally deployed local area networks and the Internet of Things based on wireless communication technologies (Wi-Fi), Bluetooth, wired, Zigbee, long-range radio (Lora) and other network types. Due to cost, usage habits and other considerations, it is impossible for various industries to completely replace existing networks with 5G networks in the short term. Therefore, in various industries, 5G networks and other types of networks will coexist for a long time. If the terminals of the 5G network and the terminals of other networks are in an isolated state, the goal of 5G Internet of Everything will not be achieved, so the integration of 5G and other types of networks is imperative.

[0074] In the related technology, 3GPP first defined PIN in the mobile standard. It is very different from commercial IoT devices. IoT devices in PIN are usually not so sturdy, and the battery life is usually a few days or weeks. User plane traffic is usually forwarded in a restricted environment (such as around the body or indoors), that is, 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 a variety of non-3GPP-based wireless technologies such as wireless local area network (WLAN), short-range wireless communication technology (Z-Wave), Zigbee, Bluetooth, etc., to allow users to interact and control. PIN can bring two benefits. First, due to the small amount of user plane traffic generated by IoT devices, traditional cellular operators do not need to reserve resources specifically for IoT devices in the network, thereby saving bandwidth resources; second, the traffic generated by IoT devices can be kept locally through the private network, which is convenient for users to manage and use.

[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 other PIN elements with connections to and from the 5G network, or provide relays for communications 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 controls the access rights of PIN elements.

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

[0077] In related technologies, fixed-mobile convergence refers to the convergence of fixed and mobile networks, also known as wireless and wired convergence. It is achieved through the integration and cooperation between fixed networks and mobile networks, thereby realizing the operation of full services and integrated services, providing users with a variety of high-quality communication, information, entertainment and other 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), which are deployed on the user side and the network side respectively to solve the convergence problem at the two locations:

[0079] (1) RG is located between the terminal and the access network, and is divided into 5G resident gateway (5G-RG) and fixed network gateway (Fixed Network RG, FN-RG). 5G-RG has 5G communication capabilities and can connect to the next generation radio access network (NG RAN) and the wired access network; while FN-RG can only connect 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 forms the wired 5G access network (W-5GAN). It is connected to 5GC through standard 3GPP N2 and N3 interfaces.

[0081] "RG+W-AGF" is the basis for realizing 5G fixed-mobile convergence. Based on the fixed-mobile convergence network architecture of 5G-RG+W-AGF, the terminal first accesses the 5G-RG through a non-3GPP network (for example, 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 medical, educational, family, industrial and other scenarios. When applied to smart health care scenarios in the medical industry, 5G smartphones, such as 5G User Equipment (5G UE), can be used as PEMC devices, and personal health monitoring devices can be used as PIN elements, with the help of fixed terminal devices PEGC to provide patient data to hospital servers through the 5G network. In the smart ward scenario, the devices carried and worn by patients can discover each other with the devices in the smart ward. 5G UE is used as a PEMC device, and the 5G smart bed in the ward can be configured as a PEGC device, together forming a PIN network. The data of patients' wearable devices can be sent to the hospital system for health monitoring via PEGC access to the 5G network.

[0083] The embodiments of the present application provide a method, device and storage medium for creating a personal Internet of Things network. The method for creating a personal Internet of Things network based on the embodiments of the present application can solve the problem of creating a personal Internet of Things network when the network quality is poor.

[0084] In a first aspect, an embodiment of the present application provides a method for creating a personal Internet of Things network, which is applied to a resident gateway, and the resident gateway is communicatively connected with an electronic device; the electronic device is a device that can be used as a personal Internet of Things network element PEMC with management capabilities; the resident gateway is a personal Internet of Things network element PEGC that can be used as a gateway function, and a gateway that can access a core network through a wired network or a wireless network; Figure 1 As shown, the method includes:

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

[0086] Exemplarily, the resident gateway may be a 5G-RG, the electronic device may be a 5G UE, the core network may be a 5GC, and the personal IoT network creation method may be applied to a 5G fixed-mobile convergence scenario. The resident gateway and the electronic device may be connected in a wired or wireless manner, and specifically, the electronic device may access the resident gateway in a non-3GPP network (e.g., WLAN, wired, Bluetooth, etc.).

[0087] The embodiment of the present application 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, a 5G UE with PEMC capability accesses a 5GC through a 5G fixed-mobile convergence method (e.g., 5G-RG). The 5G-RG has PEGC capability and needs to complete PEGC registration in 5GC. After that, the 5G UE performs PEMC registration and then enters the PIN creation process. This process can solve the problem that a PIN cannot be created in the current 5G fixed-mobile convergence scenario.

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

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

[0090] Step 103: Receive 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.

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

[0092] Sending a first registration request to the core network;

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

[0094] Forwarding the second registration request sent by the electronic device 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 information sent by the core network is sent to the electronic device; the registration success information indicates that the electronic device is registered in the core network as a PEMC.

[0096] It can be understood that 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 first registration type information, the first identifier information, and the PEGC capability information of the resident gateway. Among them, the first registration type information can be used to indicate the registration type to which the resident gateway belongs. As an example, the registration types in the 3GPP standard (TS23.501\23.502\33.501) include initial registration, mobility registration, periodic registration, and emergency registration. The first identifier information can be used to characterize the identity of the resident gateway. 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), and the like.

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

[0098] Exemplarily, the configuration information may include a PEGC capability indication, a PEGC subscription type, a PIN network type supported by PEGC, etc. The PEGC subscription type may include a first subscription type, for example, a type that only allows PEGC access (PEGC-only); a second subscription type, for example, a type that allows PEGC and ordinary terminals to access (PEGC-enabled); and a third subscription type, for example, a type that allows ordinary terminals to access but requires that the resident gateway be informed that it cannot be used as a PEGC (PEGC-disabled).

[0099] Exemplarily, PEGC capability indication: used to indicate the identity information and other content of PEGC carried by 5G-RG, and the implementation method can be bit, boolean, string, etc. For example: the bit type value "1" represents PEGC capability; the boolean type value "true" represents PEGC capability; the string type value "PEGCcapable" represents PEGC capability.

[0100] Exemplarily, the subscription type of PEGC: is used to indicate the subscription type of PEGC in the unified data management of the core network. The implementation method can be bitmap, string, etc. For example: when bitmap is used, "00" means PEGC-enabled, "01" means PEGC-only, and "10" means PEGC-disabled; when the string method is used, it includes but is not limited to PEGC-enabled, PEGC-only, and PEGC-disabled.

[0101] Among them, PEGC-enabled means that the 5G-RG has signed a contract for the PEGC function and can be used as the PEGC of the PIN network, but it can also support the access of non-PIN devices. PEGC-only means that the 5G-RG has signed a contract for the PEGC function and can only be used as the PEGC of the PIN network. Non-PIN devices cannot access it, that is, the 5G-RG can only access devices that meet one of the following conditions: 1) It has PEMC capabilities and has passed the certification of 5GC; 2) It has applied to join the PIN and has passed the certification of the PMEC corresponding to the PIN. PEGC-disabled means that the 5G-RG has not signed a contract for the PEGC function or the PEGC function is disabled, and it can only be used as a normal 5G-RG.

[0102] Exemplarily, supported PIN network types: used to indicate which PIN network types PEGC supports, and the implementation method can be bitmap, string, etc. When bitmap is used, "00" represents Private PIN, "01" represents Public PIN, and "10" represents Personal Body area PIN; when string method is used, it includes but is not limited to "Private PIN", "Public PIN" and "Personal Body area PIN".

[0103] Among them, Private PIN means that the PIN network is a private PIN network, such as a PIN network at home. PublicPIN means that the PIN network is a public PIN network, such as a PIN network in shopping malls, supermarkets and other places. Personal Body areaPIN means that the PIN network is a PIN network around the body, such as a PIN network in smart watches, smart glasses and other places.

[0104] It is understandable that the resident gateway can determine the access mode of the electronic device according to the second registration request, and forward the second registration request to the core network according to the access mode. By determining the access mode of the electronic device, it is possible to avoid the second registration request information of the electronic device that cannot access the core network being forwarded by the resident gateway, further avoiding the core network from receiving more information and processing more information that cannot be accessed.

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

[0106] Receiving a gateway type sent by the core network based on the first identifier information;

[0107] Determine the access method of the electronic device to the core network according to the capability indication information of the electronic device and the gateway type;

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

[0109] In an application example, determining an access mode for an electronic device to access a core network according to capability indication information of the electronic device and a gateway type includes:

[0110] When the capability indication information indicates that the electronic device has PEMC capability and the gateway type indicates a subscription type that allows the electronic device to access, determining that the access mode of the electronic device is the first access mode;

[0111] The first access mode 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 be registered in the core network as a PEMC.

[0112] Exemplarily, the gateway type may be a PEGC subscription type, which is used to indicate the PEGC subscription type in the unified data management of the core network. According to the capability indication information of the electronic device and the gateway type, the access method of the electronic device to the core network is determined. As an example, when the capability indication information indicates that the electronic device has PEMC capability and the gateway type is the first subscription type, the second subscription type or the third subscription type, the access method of the electronic device is determined to be the first access method; wherein 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 can be registered as 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 access by electronic devices that do not have PEMC capability is allowed, and the gateway type is the second contract type or the third contract type, the access mode of the electronic device is determined to be the second access mode; wherein the second access mode indicates that a second registration request sent by the electronic device to the resident gateway can be forwarded to the core network, but cannot be registered as PEMC in the core network.

[0114] As another example, when the capability indication information indicates that the electronic device does not have PEMC capability, and the gateway type indicates that access by electronic devices that do not have PEMC capability is not allowed, and the gateway type is the first contract type, the access mode of the electronic device is determined to be the third access mode; wherein the third access mode indicates that a 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] It can be understood that the resident gateway can forward the second registration request to the core network according to the first access method and / or the second access method.

[0116] In an application example, the second registration request includes at least the second identifier information and PEMC capability information of the electronic device; before determining the access mode of the electronic device to access the core network according to the capability indication information and the gateway type of the electronic device, the method further includes:

[0117] Sending an indication request corresponding to the second registration request to the core network; the indication request at least includes the second identifier information and the PEMC capability information in the second registration request;

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

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

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

[0121] In a second aspect, an embodiment of the present application provides a method for creating a personal Internet of Things network, which is applied to an electronic device, wherein the electronic device is connected to a resident gateway; the resident gateway is a gateway that can serve as a PEGC and can access a core network through a wired network or a wireless network; the electronic device is a device that can serve as a PEMC; Figure 2 As shown, the method includes:

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

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

[0124] Exemplarily, the gateway request information may be information sent by the electronic device to the resident gateway, and is used to instruct the resident gateway to send its own gateway identification to the electronic device.

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

[0126] Exemplarily, the electronic device sends the creation request information to the core network, and receives the network identifier sent by the personal Internet of Things server based on the creation request information through the core network. The personal Internet of Things server can be a personal Internet of Things application function (PIN Application Function, PIN AF); the network identifier can be a personal Internet of Things network identifier (PIN ID).

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

[0128] Step 205: Based on the gateway identifier, the resident gateway is used as the PEGC of the personal Internet of Things network.

[0129] Exemplarily, the gateway identifier can be used as designated information, and the electronic device as a PEMC can save the designated information, thereby realizing the resident gateway as a PEGC of a personal Internet of Things network.

[0130] In an embodiment of the present application, an electronic device that has completed PEMC registration in the core network can directly send a creation request message 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 PEGC registration in the core network.

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

[0132] Sending 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;

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

[0134] It is understandable that the second registration request may include at least one of the second registration type information of the electronic device, the second identifier information, and the PEMC capability information. Among them, the description of the second registration type information can refer to the first registration type information, which will not be repeated here. The second identifier information can be used to characterize the identity of the electronic device, and the specific description can refer to 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] Exemplarily, PEMC ID: used to represent the unique identity of a device with PEMC capabilities in a PIN network, and implementation methods include but are not limited to: MSISDN, IMSI, SUPI, SUCI, IP address, MAC address, and PEI.

[0136] It is understandable that after receiving the registration success information sent by the resident gateway, the electronic device, as a PEMC, creates a PIN network. Specifically, the electronic device, as a PEMC, obtains the gateway identifier of the resident gateway from the resident gateway.

[0137] In an application example, the method further includes:

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

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

[0140] If it is determined that the IoT terminal is connected to the network, a terminal identifier corresponding to the IoT terminal is generated based on the network access request information.

[0141] Exemplarily, the network information may also include name information of the personal Internet of Things network. It is understandable that the network identification and name information may represent the identity information of the personal Internet of Things network from the identification dimension and the name dimension respectively.

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

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

[0144] In a third aspect, an embodiment of the present application provides a method for creating a personal Internet of Things network, which is applied to a core network, wherein the core network is connected to an electronic device and a resident gateway respectively; the electronic device is a device that can serve as a PEMC; the gateway is a gateway that can serve as a PEGC and can access the core network through a wired network or a wireless network; Figure 3 As shown, the method includes:

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

[0146] Exemplarily, the core network may include an access and mobility management function (AMF), an authentication server function (AUSF) and a unified data management (UDM).

[0147] Step 302: forwarding the creation request information sent by the electronic device to the personal Internet of Things server; the creation request information at least includes 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 Internet of Things server based on the management identifier and the gateway identifier to the electronic device; the network identifier is used to indicate that the personal Internet of Things network is successfully created.

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

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

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

[0152] Receiving, through the resident gateway, a second registration request sent by the electronic device; the second registration request is used to request the electronic device to register in the core network as a PEMC;

[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 is registered in the core network as a PEMC.

[0154] It should be noted that the AMF of the core network receives the first registration request and sends the first registration request to the AUSF of the core network. The AUSF of the core network authenticates the resident gateway based on the first identifier information in the first registration request to obtain a first authentication result. Among them, it is possible to query in the AUSF of the core network whether the resident gateway is a legal user based on the first identifier information. If it is a legal user, the authentication is successful; if it is an illegal user, the authentication fails. The AUSF of the core network pre-stores whether each resident gateway is a legal user or an illegal user.

[0155] In the case where the first authentication result indicates that the authentication of the resident gateway fails, a first failure message is generated; the first failure message is sent to the AMF of the core network. In the case where the first authentication result indicates that the authentication of the resident gateway succeeds, a first success message is generated; the first success message is sent to the AMF of the core network.

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

[0157] After receiving the first success information, the AMF of the core network generates the subscription request information of 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 an application example, the first registration request includes 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:

[0159] Storing PEGC capability information;

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

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

[0162] It should be noted that after the UDM of the core network queries the configuration information corresponding to the resident gateway, it generates a registration result of the resident gateway and 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 the electronic device according to the access method of the electronic device, so that the electronic device is registered as a PEMC. Among them, the registration process can be determined according to the actual situation and is not limited here. As an example, the electronic device can be registered in 5G according to the 5G UE registration process in 3GPP.

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

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

[0166] Determine capability indication information based on the second identifier information and the PEMC capability information; the capability indication information represents indication information corresponding to the PEMC capability information;

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

[0168] A second registration request is received, which is sent by the resident gateway based on the capability indication information.

[0169] It should be noted that the AMF of the core network receives the indication request and forwards the indication request to the AUSF of the core network. The AUSF of the core network authenticates the electronic device based on the second identifier information in the indication request to obtain a second authentication result. Among them, the AUSF of the core network can be queried based on the second identifier information to see whether the electronic device is a legitimate user. If it is a legitimate user, the authentication is successful; if it is an illegal user, the authentication fails. The AUSF of the core network pre-stores whether each electronic device is a legitimate user or an illegal user.

[0170] If the second authentication result indicates that the electronic device authentication failed, a second failure message is generated; and the second failure message is sent to the AMF of the core network. If the second authentication result indicates that the electronic device authentication succeeded, a second success message is generated; and the second success message is sent to the AMF of the core network. After receiving the second success message, the AMF of the core network forwards the indication request to the UDM of the core network.

[0171] After receiving the indication request sent by the AMF of the core network, the UDM of the core network queries the capability indication information corresponding to the electronic device according to the second identifier information, and sends the capability indication information to the AMF of the core network. After receiving the capability indication information, the AMF of the core network forwards the capability indication information to the resident gateway.

[0172] Among them, the AMF of the core network can forward the second failure information to the electronic device, or it may not forward the second failure information. That is, if the electronic device receives the second failure information or still does not receive the AMF reply message from the core network after a preset time interval, it is determined that the registration of the electronic device has failed.

[0173] The following is an example of an application example to illustrate the method for creating a personal Internet of Things network in an embodiment of the present application, which can be 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 the embodiment of the present application is carried out through three processes, specifically including the following steps:

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

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

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

[0178] like Figure 5 As shown in the figure, the 5G-RG configured with PEGC capability initiates the registration process to 5GC, performs identity authentication and obtains the contract configuration information. The process of 5G-RG registering PEGC capability with 5GC specifically includes the following steps:

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

[0180] Step 502: Authentication. AMF receives the registration information and authenticates AUSF based on the user identifier and other parameters provided by 5G-RG. AUSF authenticates 5G-RG. If the authentication is successful, it proceeds to step 503; if the authentication fails, it replies to AMF "Authentication failed, the user is an illegal user".

[0181] Step 503: Get PEGC contract information. UDM receives the "Get PEGC contract information of 5G-RG" request sent by AMF, saves PEGC capability information, and queries PEGC contract configuration information according to the PEGC ID provided by 5G-RG, including but not limited to PEGC capability indication, PEGC contract type, and PEGC supported PIN network type. Among them, PEGC contract types include but are not limited to PEGC-enabled, PEGC-only, and PEGC-disabled; supported PIN network types include but are not limited to Private PIN, Public PIN, and Personal Body area PIN.

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

[0183] After the above process is completed, 5G-RG performs the corresponding service status according to the contract information returned by 5GC.

[0184] like Figure 6 As shown in the figure, when the 5G UE is in an area with weak 5G signals and cannot directly connect to the 5GC for registration, the 5G UE can register with the 5GC in a 5G fixed-mobile convergence mode through the 5G-RG. The process of the 5G UE registering the PEMC capability with the 5GC through the 5G-RG 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, where the PEMC capability information includes but is not limited to PEMC ID and supported slice ID.

[0186] Step 602: Initiate a request to "obtain PEMC capability indication of 5G UE". 5G-RG receives the 5G UE registration request and obtains the PEMC capability information of the 5G UE. At this time, 5G-RG initiates a request to "obtain PEMC capability indication of 5G UE" to 5GC, which carries the user identifier, PEMC ID and other information of the 5G UE.

[0187] Step 603: User identity authentication. AMF receives the 5G-RG request in step 2 and initiates user identity authentication for the UE to AUSF. AUSF checks whether the UE is a legitimate user based on the user identifier of the UE. If so, AUSF returns "The UE is a legitimate user" to AMF and proceeds to step 4; if not, AUSF returns a message "Query failed, the user is an illegal user, registration is not allowed" to AMF.

[0188] Step 604: Get the "PEMC capability indication" information of the 5G UE. The AMF requests the UDM to obtain the "PEMC capability indication" 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 result in UDM to 5G-RG, and 5G-RG obtains the PEGC judgment result based on the type of its PEGC and the capability indication information of PEMC of 5G UE.

[0190] Step 606: Forward the registration request of the 5G UE. As shown in Table 1, if the PEGC judgment result is case 1, case 2, case 3, case 5, and case 6, the 5G-RG forwards the registration request of the 5G UE, where the 5G UE can register its PEMC capability only under the conditions of case 1, case 2, and case 3. The subsequent registration process refers to the 5G UE registration process in the current 3GPP.

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

[0192] Table 1 is a list of PEGC types and PEMC capability indicators.

[0193]

[0194]

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

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

[0197] Step 702: Apply to establish a PIN network and obtain a PIN ID from the PIN AS. The 5G UE initiates the creation of a PIN network to the 5GC, carries information such as the 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 PEGC to join PIN. 5G UE (ie PEMC) sends PIN ID to PEGC (ie 5G-RG) and designates 5G-RG as PEGC in the PIN network.

[0199] Step 704: The PIN device joins the PIN. The PEMC broadcasts the PIN network information, including the PIN ID, PIN name and other information.

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

[0201] The slice type indication supported in the embodiment of the present application 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, a 6-bit binary number is used, "000000" represents slice A, and "000001" represents slice B; when the string method is used, "NSSAI A" indicates support for A slices, and "NSSAI B" indicates support for B slices.

[0202] In a fourth aspect, based on the hardware implementation of the above program module, and in order to implement the method of the resident gateway side of the embodiment of the present application, the embodiment of the present application provides a resident gateway, Figure 8 Only an exemplary structure of the resident gateway is shown, not all structures, and can be implemented as needed. Figure 8 Partial or complete structure shown.

[0203] like Figure 8 As shown, the resident gateway 800 provided in the embodiment of the present application 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 through a bus system 804. It can be understood that the bus system 804 is used to realize the connection and communication between these components. In addition to the data bus, the bus system 804 also includes a power bus, a control bus and a status signal bus. However, for the sake of clarity, in Figure 8 Various buses are labeled as bus system 804 .

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

[0205] The memory 802 in the embodiment of the present application 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 Internet of Things network of a resident gateway disclosed in the embodiment of the present application can be applied to the processor 801, or implemented by the processor 801. The processor 801 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the method for creating a personal Internet of Things network of a resident gateway can be completed by an integrated logic circuit of hardware or software instructions in the processor 801. The above-mentioned processor 801 can be a general-purpose processor, a digital signal processor (DSP, Digital Signal Processor), or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc. The processor 801 can implement or execute the various methods, steps and logic block diagrams disclosed in the embodiments of the present application. The general-purpose processor can be a microprocessor or any conventional processor, etc. In combination with the steps of the method disclosed in the embodiment of the present application, it can be directly embodied as a hardware decoding processor to execute, or it can be executed by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium, which is located in the memory 802. The processor 801 reads the information in the memory 802 and completes the steps of the method for creating a personal Internet of Things network of a resident gateway provided in the embodiment of the present application in combination with its hardware.

[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 execute the aforementioned method.

[0208] In a fifth aspect, based on the hardware implementation of the above program module, and in order to implement the method on the electronic device side of the embodiment of the present application, the embodiment of the present application provides an electronic device, Fig. 9 Only an exemplary structure of the electronic device is shown, not all structures, and it can be implemented as needed. Fig. 9 Partial or complete structure shown.

[0209] like Fig. 9As shown, the electronic device 900 provided in the embodiment of the present application 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 through a bus system 904. It can be understood that the bus system 904 is used to realize the connection and communication between these components. In addition to the data bus, the bus system 904 also includes a power bus, a control bus and a status signal bus. However, for the sake of clarity, in Fig. 9 Various buses are labeled as bus system 904.

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

[0211] The memory 902 in the embodiment of the present application 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 network of an electronic device disclosed in the embodiment of the present application can be applied to the processor 901, or implemented by the processor 901. The processor 901 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the method for creating a personal Internet of Things network of an electronic device can be completed by an integrated logic circuit of hardware in the processor 901 or instructions in the form of software. The above-mentioned processor 901 can be a general-purpose processor, a DSP, or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc. The processor 901 can implement or execute the various methods, steps and logic block diagrams disclosed in the embodiments of the present application. The general-purpose processor can be a microprocessor or any conventional processor, etc. In combination with the steps of the method disclosed in the embodiment of the present application, it can be directly embodied as a hardware decoding processor to execute, or it can be executed by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium, which is located in the memory 902. The processor 901 reads the information in the memory 902 and completes the steps of the method for creating a personal Internet of Things network of an electronic device provided in the embodiment of the present application in combination with its hardware.

[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 methods.

[0214] In a sixth aspect, based on the hardware implementation of the above program module, and in order to implement the method on the network device side of the embodiment of the present application, the embodiment of the present application provides a network device, Fig.10Only an exemplary structure of the network device is shown, not all structures, and can be implemented as needed. Fig.10 Partial or complete structure shown.

[0215] like Fig.10 As shown, the network device 1000 provided in the embodiment of the present application 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 through a bus system 1004. It can be understood that the bus system 1004 is used to realize the connection and communication between these components. In addition to the data bus, the bus system 1004 also includes a power bus, a control bus and a status signal bus. However, for the sake of clarity, Fig.10 Various buses are labeled as bus system 1004 .

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

[0217] The memory 1002 in the embodiment of the present application 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 network of a network device disclosed in the embodiment of the present application can be applied to the processor 1001, or implemented by the processor 1001. The processor 1001 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the method for creating a personal Internet of Things network of a network device can be completed by an integrated logic circuit of hardware in the processor 1001 or by instructions in the form of software. The above-mentioned processor 1001 can be a general-purpose processor, a DSP, or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc. The processor 1001 can implement or execute the various methods, steps and logic block diagrams disclosed in the embodiments of the present application. The general-purpose processor can be a microprocessor or any conventional processor, etc. In combination with the steps of the method disclosed in the embodiment of the present application, it can be directly embodied as a hardware decoding processor to execute, or it can be executed by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium, which is located in the memory 1002. The processor 1001 reads the information in the memory 1002 and completes the steps of the method for creating a personal Internet of Things network of a network device provided in the embodiment of the present application in combination with its hardware.

[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 methods.

[0220] It can be understood that the memory (memory 802, memory 902, memory 1002) can be a volatile memory or a non-volatile memory, and can also include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a magnetic random access memory (FRAM), a flash memory, a magnetic surface memory, an optical disk, or a compact disc read-only memory (CD-ROM); the magnetic surface memory can be a disk memory or a tape memory. The volatile memory can be a random access memory (RAM), which is used as an external cache. By way of example and 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), synchronous link dynamic random access memory (SLDRAM, SyncLink Dynamic Random Access Memory), and direct RAMbus random access memory (DRRAM, Direct Rambus Random Access Memory).The memories described in the embodiments of the present application are intended to include, but are not limited to, these and any other suitable types of memories.

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

[0222] In addition, the technical solutions described in the embodiments of the present application can be combined arbitrarily without conflict.

[0223] The above are only specific implementations of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A method for establishing a personal Internet of Things network, characterized in that: Applied to a resident gateway, the resident gateway is communicatively connected with an electronic device; the electronic device is a device that can be used as a personal Internet of Things network element PEMC with management capabilities; the resident gateway is a personal Internet of Things network element PEGC that can be used as a gateway function, and a gateway that can be connected to a core network through a wired network or a wireless network; the method includes: Determining that the resident gateway has been registered in the core network as a PEGC, and that the electronic device has been registered in the core network as a PEMC; Sending a gateway identifier to the electronic device based on the gateway request information sent by the electronic device; Receive a network identifier sent by the electronic device; the network identifier is used to indicate that the personal Internet of Things network is successfully created.

2. The method according to claim 1, characterized in that The determining that the resident gateway has been registered in the core network as a PEGC, and the electronic device has been registered in the core network as a PEMC, comprises: Sending a first registration request to the core network; Receiving configuration information sent by the core network based on the first registration request; the configuration information indicates that the resident gateway is registered in the core network as a PEGC; Forwarding a second registration request sent by the electronic device 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 is registered in the core network as a PEMC.

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 forwarding the second registration request sent by the electronic device to the core network includes: receiving a gateway type sent by the core network based on the first identifier information; Determining, according to the capability indication information of the electronic device and the gateway type, an access mode for the electronic device to access the core network; The second registration request is forwarded to the core network based on the access mode.

4. The method according to claim 3, characterized in that The determining, according to the capability indication information of the electronic device and the gateway type, an access mode for the electronic device to access the core network includes: When the capability indication information indicates that the electronic device has PEMC capability and the gateway type indicates a subscription type that allows the electronic device to access, determining that the access mode of the electronic device is the first access mode; The first access mode 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 be registered in the core network as a PEMC.

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 mode of the electronic device to access the core network according to the capability indication information of the electronic device and the gateway type, the method further includes: Sending an indication request corresponding to the second registration request to the core network; the indication request at least includes the second identifier information and the PEMC capability information in 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 indication information corresponding to the PEMC capability information.

6. A method for establishing a personal Internet of Things network, characterized in that: Applied to an electronic device, the electronic device is connected to a resident gateway; the resident gateway is a gateway that can serve as a PEGC and can access a core network through a wired network or a wireless network; The electronic device is a device capable of serving as a PEMC; the method comprises: Determining that the resident gateway has been registered in the core network as a PEGC, and that the electronic device has been registered in the core network as a PEMC; Receiving a gateway identifier sent by the resident gateway based on the gateway request information; Receiving, through the core network, a network identifier sent by the personal Internet of Things server based on the creation request information; the creation request information at least includes the management identifier of the electronic device and the gateway identifier; the network identifier is used to indicate that the personal Internet of Things network is successfully created; Sending the network identification to the resident gateway; The resident gateway is used as the PEGC of the personal Internet of Things network based on the gateway identifier.

7. The method according to claim 6, characterized in that The determining that the electronic device has been registered in the core network as a PEMC includes: Sending 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; Receive registration success information sent by the resident gateway; the registration success information indicates that the electronic device is registered in the core network as a PEMC.

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

9. A method for establishing a personal Internet of Things network, characterized in that: Applied to a core network, the core network is connected to an electronic device and a resident gateway respectively; the electronic device is a device capable of serving as a PEMC; The gateway is a gateway that can serve as a PEGC and can access the core network through a wired network or a wireless network; the method includes: 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; forward the creation request information sent by the electronic device to the personal Internet of Things server; the creation request information includes at least the management identifier of the electronic device and the gateway identifier of the gateway; The network identifier sent by the personal Internet of Things 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 Internet of Things network is successfully created.

10. The method according to claim 9, characterized in that The determining that the resident gateway has been registered in the core network as a PEGC, and the electronic device has been registered in the core network as a PEMC, comprises: Receiving a first registration request sent by the resident gateway; Sending configuration information to the resident gateway; the configuration information indicates that the resident gateway is registered in the core network as a PEGC; receiving, through the resident gateway, a second registration request sent by the electronic device; the second registration request is used to request the electronic device to register as a PEMC in the core network; Sending registration success information generated based on the second registration request to the resident gateway; the registration success information indicates that the electronic device is registered as a PEMC in the core network.

11. The method according to claim 10, 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: Storing the PEGC capability information; Configuration information corresponding to the resident gateway is determined based on the first identifier information.

12. The method according to claim 10, characterized in that The second registration request at least includes the first identifier information and PEMC capability information of the electronic device; and the receiving, by the resident gateway, the second registration request sent by the electronic device includes: receiving 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 at least includes the second identifier information and the PEMC capability information in the second registration request; Determine capability indication information based on the second identifier information and the PEMC capability information; the capability indication information represents indication information corresponding to the PEMC capability information; sending the capability indication information to the resident gateway; A second registration request is received, which is sent by the resident gateway based on the capability indication information.

13. A resident gateway, characterized in that: include: a first processor and a first memory for storing a computer program executable on said first processor, Wherein, when the first processor is used to run the computer program, the steps of the method described in any one of claims 1 to 5 are executed.

14. An electronic device, characterized in that: include: a second processor and a second memory for storing a computer program executable on said second processor, Wherein, when the second processor is used to run the computer program, the steps of the method described in any one of claims 5 to 8 are executed.

15. A network device, characterized in that: include: a third processor and a third memory for storing a computer program executable on said third processor, Wherein, the third processor is used to execute the steps of the method described in any one of claims 9 to 12 when running the computer program.

16. 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 described in any one of claims 1 to 6, or implements the steps of the method described in any one of claims 6 to 8, or implements the steps of the method described in any one of claims 9 to 12.

Images