Individual Internet of Things network identifier distribution method and device, and network side equipment

Abstract

The invention discloses an identification distribution method and device of an Internet of Things network and network side equipment, and the method comprises the steps that a first network element distributes a PIN identification for a target Internet of Things network PIN, and the PIN identification is unique in the first network element; and the first network element sends or configures the PIN identifier of the target PIN to a second network element.

Description

Technical Field

[0001] The present application belongs to the field of communication technology, and specifically relates to a method, device and network-side equipment for allocating identifiers of a personal Internet of Things network. Background Art

[0002] A personal IoT network (PIN) is a network based on, composed of, and derived from a large number of consumer IoT devices. Users mainly use all these personal IoT devices at home or around their bodies to create a personal IoT network, such as wearable devices and IoT devices at home. Generally speaking, PINs are generally used in scenarios such as homes and offices. IoT devices deployed in these scenarios can be interconnected, communicate with each other, and obtain services. At the same time, the IoT devices in the PIN can access the 5G network, access other servers on the network, or complete services through a PIN element with gateway capability (PEGC) in the PIN through a certain mechanism. When PEGC uses the User Equipment (UE) Route Selection Policy (URSP) protocol to route the data traffic of the PIN to the Protocol Data Unit (PDU) session, it needs to be routed according to the PIN identifier. However, the relevant technology does not provide a method for allocating the PIN identifier, so it is impossible to route the PIN data traffic. Summary of the invention

[0003] The embodiments of the present application provide a method, apparatus and network-side equipment for allocating identities of a personal Internet of Things network, which can implement PIN identity allocation.

[0004] In a first aspect, a method for allocating an identifier of a personal Internet of Things network is provided, the method comprising: a first network element allocating a PIN identifier to a target PIN, wherein the PIN identifier is unique within the first network element; and the first network element sending or configuring the PIN identifier of the target PIN to a second network element.

[0005] In a second aspect, a personal Internet of Things network identifier allocation device is provided, which is applied to a first network element. The device includes: an allocation module, which is used to allocate a PIN identifier to a target PIN, wherein the PIN identifier is unique within the first network element; and a processing module, which is used to send or configure the PIN identifier of the target PIN to a second network element.

[0006] In a third aspect, a network side device is provided, which includes a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the program or instructions are executed by the processor, the steps of the method described in the first aspect are implemented.

[0007] In a fourth aspect, a readable storage medium is provided, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the method described in the first aspect are implemented.

[0008] In a fifth aspect, a chip is provided, comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the steps of the method described in the first aspect.

[0009] In an embodiment of the present application, a PIN identifier is allocated to a target PIN by a first network element, wherein the PIN identifier is unique within the first network element; then the first network element sends or configures the PIN identifier of the target PIN to a second network element. Since the PIN identifier is unique within the first network element, the first network element sends or configures the PIN identifier of the target PIN to the second network element, thereby enabling the second network element to identify the target PIN. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] Figure 1 A block diagram showing a wireless communication system to which the embodiments of the present application can be applied;

[0011] Figure 2 A schematic diagram showing a flow chart of a method for allocating identifiers of a personal Internet of Things network provided in an embodiment of the present application is shown;

[0012] Figure 3 A schematic diagram showing the structure of an identification allocation device for a personal Internet of Things network provided by an embodiment of the present application is shown;

[0013] Figure 4 A schematic diagram showing the structure of a communication device provided in an embodiment of the present application is shown;

[0014] Figure 5 A schematic diagram of the hardware structure of a network side device provided in an embodiment of the present application is shown. DETAILED DESCRIPTION

[0015] The following will be combined with the drawings in the embodiments of the present application to clearly describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field belong to the scope of protection of this application.

[0016] The terms "first", "second", etc. of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way are interchangeable where appropriate, so that the embodiments of the present application can be implemented in an order other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of one type, and the number of objects is not limited, for example, the first object can be one or more. In addition, "or" in the present application represents at least one of the connected objects. For example, "A or B" covers three schemes, namely, Scheme 1: including A but not including B; Scheme 2: including B but not including A; Scheme 3: including both A and B. The character " / " generally indicates that the objects associated with each other are in an "or" relationship.

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

[0018] Figure 1A block diagram of a wireless communication system applicable to an embodiment of the present application is shown. The wireless communication system includes a terminal 11 and a network side device 12. Among them, the terminal 11 can be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer), a notebook computer, a personal digital assistant (Personal Digital Assistant, PDA), a handheld computer, a netbook, an ultra-mobile personal computer (Ultra-mobile Personal Computer, UMPC), a mobile Internet device (Mobile Internet Device, MID), an augmented reality (Augmented Reality, AR), a virtual reality (Virtual Reality, VR) device, a robot, a wearable device (Wearable Device), an aircraft (flight vehicle), a vehicle-mounted device (Vehicle User Equipment, VUE), a ship-mounted device, a pedestrian terminal (Pedestrian User Equipment, PUE), a smart home (home appliances with wireless communication functions, such as refrigerators, televisions, washing machines or furniture, etc.), a game console, a personal computer (Personal Computer, PC), a teller machine or a self-service machine and other terminal side devices. Wearable devices include: smart watches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart bracelets, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among them, the vehicle-mounted device can also be called a vehicle-mounted terminal, a vehicle-mounted controller, a vehicle-mounted module, a vehicle-mounted component, a vehicle-mounted chip or a vehicle-mounted unit, etc. It should be noted that the specific type of the terminal 11 is not limited in the embodiment of the present application. The network side device 12 may include an access network device or a core network device, wherein the access network device may also be referred to as a radio access network (Radio Access Network, RAN) device, a radio access network function or a radio access network unit. The access network device may include a base station, a wireless local area network (Wireless Local Area Network, WLAN) access point (Access Point, AS) or a wireless fidelity (Wireless Fidelity, WiFi) node, etc.Among them, the base station may be referred to as a Node B (NB), an evolved Node B (eNB), a next generation Node B (gNB), a New Radio Node B (NR Node B), an access point, a Relay Base Station (RBS), a Serving Base Station (SBS), a Base Transceiver Station (BTS), a radio base station, a radio transceiver, a Basic Service Set (BSS), an Extended Service Set (ESS), a Home Node B (HNB), a Home Evolved Node B, a Transmission Reception Point (TRP) or other appropriate terms in the field. As long as the same technical effect is achieved, the base station is not limited to specific technical terms. It should be noted that in the embodiments of the present application, only the base station in the NR system is used as an example for introduction, and the specific type of the base station is not limited.

[0019] The core network equipment may include but is not limited to at least one of the following: core network node, core network function, mobility management entity (Mobility Management Entity, MME), access mobility management function (Access and Mobility Management Function, AMF), session management function (Session Management Function, SMF), user plane function (User Plane Function, UPF), policy control function (Policy Control Function, PCF), policy and charging rules function unit (Policy and Charging Rules Function, PCRF), edge application service discovery function (Edge Application Server Discovery Function, EASDF), unified data management (Unified Data Management, UDM), unified data storage (Unified Data Repository, UDR), home user server (Home Subscriber Server, HSS), centralized network configuration (CNC), network storage function (Network Repository Function, NRF), network exposure function (Network Exposure Function, NEF), local NEF (Local NEF, or L-NEF), binding support function (Binding Support Function, BSF), application function (Application Function, AF), etc. It should be noted that in the embodiments of the present application, only the core network device in the NR system is introduced as an example, and the specific type of the core network device is not limited.

[0020] In conjunction with the accompanying drawings, the following describes in detail the identification allocation method, apparatus and network-side equipment for the personal Internet of Things network provided by the embodiments of the present application through some embodiments and their application scenarios.

[0021] Figure 2 A flow chart of a method for allocating identifiers of a personal Internet of Things network provided in an embodiment of the present application is shown as follows: Figure 2 As shown, the method may include the following steps.

[0022] S202: The first network element allocates a PIN identifier to a target PIN, wherein the PIN identifier is unique within the first network element.

[0023] In an embodiment of the present application, the first network element may include a target network element in a public land mobile network (PLMN), for example, the target network element may be at least one of the following: a unified data management function (UDM) and a network open function (NEF). The PLMN may be a PLMN that provides 5G services for the target PIN. In other words, the UDM or NEF in the PLMN may allocate a PIN identifier to the target PIN.

[0024] For example, a user signs a contract for a PIN service (wearable service, home IoT device service, etc.) with an operator. The operator allocates a PIN identifier based on the signed PIN service. Specifically, the UDM or NEF that provides services to the user may allocate the PIN identifier.

[0025] Alternatively, the first network element may also include an AF. That is, the AF may allocate a PIN identifier to the target PIN.

[0026] In actual applications, the user may sign a contract for one or more PINs on the network side. After the user signs a contract for one or more PINs, the first network element may allocate a PIN identifier to each PIN.

[0027] In an implementation manner, the PIN identifier may include: a first character string, where the first character string is allocated by the first network element and is unique in the first network element.

[0028] In one implementation, the PIN identifier further includes: a second string, wherein the first string and the second string are connected by a preset symbol. For example, the second string may be a domain name or an AF ID, and the AF ID is an AF identifier assigned to the first string.

[0029] Optionally, the preset symbol may include an English period, for example, <string1> . <string2>Alternatively, the default symbol can also include @, for example, <string1> @ <string2>.

[0030] S204: The first network element sends or configures the PIN identifier of the target PIN to the second network element.

[0031] In the embodiment of the present application, the first network element may send the PIN identifier of the target PIN to the second network element, or the PIN identifier of the target PIN may be preconfigured to the second network element. Specific embodiments of the present application are not limited thereto.

[0032] In an embodiment of the present application, when the first network element is a target network element in a PLMN, the second network element may be an AF or a PCF or a UE. When the second network element is an AF, the AF may be sent to the PCF or the UE directly or through other network elements.

[0033] When the first network element is an AF, the second network element may be a PCF or a UE.

[0034] Among them, the above-mentioned UE can be the UE associated with the target PIN contract.

[0035] In an embodiment of the present application, the UE mentioned in the present application may be a PEGC in a PIN scenario.

[0036] After obtaining the PIN identifier of the target PIN, the PCF can generate a user routing selection policy for the target PIN based on the PIN identifier, and send the user routing selection policy to the UE for use. Based on the user routing selection policy, the UE can normally route the data traffic of the target PIN based on the PIN identifier of the target PIN.

[0037] In an embodiment of the present application, a PIN identifier is allocated to a target PIN by a first network element, wherein the PIN identifier of the target PIN is unique within the first network element, and then the first network element sends or configures the PIN identifier of the target PIN to a second network element. Since the PIN identifier is unique within the first network element, the first network element sends or configures the PIN identifier of the target PIN to the second network element, so that the second network element can identify the target PIN, and a corresponding URSP can be generated according to the PIN identifier and sent to the UE for use, or the first network element can directly configure it into the URSP after allocating the PIN ID, and then configure it to the UE, so that the UE can correctly route the data traffic of the target PIN according to the PIN identifier.

[0038] In an implementation manner, when the first network element includes a target network element in a PLMN that provides services for the target PIN, the first character string may include: a group identifier of the target PIN.

[0039] In the above implementation, the external group identifier of the target PIN is used as the PIN ID. For example, the PIN identifier may be in the form of groupname@domain name, where groupname is the PIN name.

[0040] In one implementation, the group identified by the external group identifier may be a PIN (The group can be a PIN) or an external group identifier may also identify a PIN (An External Group Identifier also identifies a PIN).

[0041] In one implementation, the format of the external group identifier is as follows:

[0042] Example 1: Group1@domain.com;

[0043] Example 2: PIN1@domain.com.

[0044] In another implementation, when the first network element includes a target network element in a PLMN that provides services for the target PIN, the first character string may include: a PIN name generated by the first network element. That is, in this implementation, the first network element may generate a new PIN name for the target PIN instead of reusing an existing identifier. The PIN name generated by the first network element may be a label or a string of labels, for example, PIN1.

[0045] In one implementation, when the first network element includes a target network element in a PLMN providing services for the target PIN, and when the PIN identifier includes a second string, the second string includes: a domain name identifier. The domain name identifier may be a domain name identifier registered by the target PIN.

[0046] For example, the PIN identifier of the target PIN may be:<PIN name> .<domain name> , domain name is a domain name identifier, and the domain name identifier and the PIN name can be connected by an English period. The PIN name can be the above-mentioned group identifier, or it can be a PIN name generated by the first network element.

[0047] In one implementation, the above-mentioned step 202 may include: the first network element assigns the PIN identifier to the target PIN based on the data network name (Data Network Name, DNN) dedicated to the target PIN or the single network slice selection assistance information (S-NSSAI) .

[0048] In this embodiment, the first network element may include UDM or NEF, and the UDM or NEF allocates a PIN identifier to the target PIN according to the DNN or S-NSSAI dedicated to the target PIN. Since the DNN or S-NSSAI is dedicated to the target PIN, a PIN can be identified according to the DNN or S-NSSAI. The first network element can allocate a unique PIN identifier to the target PIN according to the DNN or S-NSSAI, and then send or configure the PIN identifier to the second network element. The second network element can generate a corresponding URSP according to the PIN identifier and send it to the UE (in the PIN scenario, the UE is PEGC) for use, so as to enable the UE to perform correct routing according to the PIN identifier.

[0049] In one implementation, the second network element includes one of the following: an application function (Application Function, AF), a policy control function entity (Policy Control Function, PCF).

[0050] In an embodiment of the present application, the first network element may include UDM and NEF, and the second network element may include AF and PCF. The UDM or NEF assigns a PIN identifier to the target PIN, and then sends or configures the PIN identifier to the AF or PCF, so that the AF or PCF generates a corresponding URSP according to the PIN identifier of the target PIN, and sends it to the UE (in the PIN scenario, the UE is PEGC) for use, so as to enable the UE to perform correct routing according to the PIN identifier.

[0051] In one implementation, when the first network element is AF, the PIN identifier of the target PIN may be in the form of, for example, a first string (PIN name) + AF identifier, the PIN name is unique within the AF, and the AF identifier is also unique within the PLMN, therefore, the first string is unique within the PLMN.

[0052] In one implementation, when the first network element includes an AF, the first character string may be an identifier of a PLMN. For example, the PIN identifier may be:<PLMN ID> .<AF ID> ; or the first character string may be a temporary identifier allocated by the first network element, for example, a PIN identifier may be:<temporary identity> .<AF ID> ,or<temporary identity> @ <afid>Alternatively, the first character string may be an identifier of the first network element. For example, the PIN identifier may be:<AF ID> . <temporaryidentity>.

[0053] In one implementation, the PLMN identifier is a unique identifier of the PLMN where the AF is located, and the second character string may be an identifier of the AF, wherein the identifier of the AF is a unique identifier of the PLMN where the AF is located, thereby ensuring the uniqueness of the PIN identifier when the AF allocates the target PIN.

[0054] In an implementation manner, when the first network element includes an AF and the PIN identifier includes a second character string, the second character string includes: an identifier of the first network element and a temporary identifier allocated by the first network element.

[0055] For example, when the first character string and the second character string of the PIN identifier are connected by an English period, the form of the PIN identifier may be:<temporary identity> .<AF ID> ,or,<AF ID> . <temporaryidentity>Alternatively, you can also connect via @:<temporary identity> @<AF ID> .

[0056] In one implementation, when the first network element includes an AF, the second network element may include a PCF or a UE.

[0057] In an embodiment of the present application, the first network element may include an AF, and the second network element may include a PCF or a UE. The AF allocates a PIN identifier to a target PIN, and then sends or configures the PIN identifier to the PCF or the UE directly or indirectly through other network elements, so that the PCF generates a corresponding URSP according to the PIN identifier of the target PIN, and sends it to the UE (in the PIN scenario, the UE is a PEGC) for use, or after allocating the PIN ID, the AF directly configures it into the URSP, and then configures it to the UE, so that the UE can perform correct routing according to the PIN identifier.

[0058] In one or more implementations, the length of the PIN identifier is not fixed. That is, the length of the PIN identifier can be changed according to different first network elements or second network elements to adapt to the current network element, ensure the uniqueness of the PIN identifier, and thus ensure that the UE performs correct routing according to the PIN identifier.

[0059] The identification allocation method for a personal Internet of Things network provided in the embodiment of the present application can be executed by an identification allocation device for a personal Internet of Things network. In the embodiment of the present application, the identification allocation method for a personal Internet of Things network performed by an identification allocation device for a personal Internet of Things network is taken as an example to illustrate the identification allocation device for a personal Internet of Things network provided in the embodiment of the present application.

[0060] Figure 3 A schematic diagram showing the structure of an identification allocation device for a personal Internet of Things network provided in an embodiment of the present application is shown. The device is applied to a first network element. Figure 3 The identity allocation device 300 of the personal Internet of Things network may include an allocation module 31 and a processing module 32.

[0061] Among them, the allocation module 31 is used to allocate a PIN identifier for the target personal Internet of Things network PIN, wherein the PIN identifier is unique within the first network element; the processing module 32 is used to send or configure the PIN identifier of the target PIN to the second network element.

[0062] In an implementation manner, the PIN identifier includes: a first character string, which is a character string allocated by the first network element and is unique in the first network element.

[0063] In an implementation manner, the PIN identifier further includes: a second character string, and the first character string and the second character string are connected by a preset symbol.

[0064] In one implementation, the first network element includes: a target network element in a public land mobile network PLMN that provides services for the target PIN, wherein the target network element includes at least one of the following: a unified data management function and a network open function.

[0065] In one implementation, the first character string includes one of the following: a group identifier of the target PIN, and a PIN name generated by the first network element.

[0066] In an implementation manner, when the PIN identifier includes a second character string, the second character string includes: a domain name identifier.

[0067] In one implementation, the above-mentioned allocation module 31 can be used to allocate the PIN identifier to the target PIN based on the data network name or single network slice selection auxiliary information S-NSSAI dedicated to the target PIN.

[0068] In one implementation, the second network element includes one of the following: an application function AF, a policy control function entity PCF, and a UE.

[0069] In one implementation, the first network element includes: an application function AF.

[0070] In one implementation, the first character string includes one of the following: an identifier of a PLMN, a temporary identifier allocated by the first network element, and an identifier of the first network element, and the temporary identifier is unique within the first network element.

[0071] In one implementation, the identifier of the PLMN is a unique identifier of the PLMN where the AF is located.

[0072] In an implementation manner, when the PIN identifier includes a second character string, the second character string includes: an identifier of the first network element and a temporary identifier allocated by the first network element.

[0073] In one implementation, the second network element includes a PCF or a UE.

[0074] In one implementation, the length of the PIN identifier is not fixed.

[0075] The identification allocation device for the personal Internet of Things network provided in the embodiment of the present application can achieve Figure 2 The various processes implemented by the method embodiment and achieving the same technical effect are not described here to avoid repetition.

[0076] like Figure 4 As shown, an embodiment of the present application further provides a communication device 400, including a processor 401 and a memory 402, and the memory 402 stores programs or instructions that can be executed on the processor 401. For example, when the communication device 400 is a network side device, the program or instruction is executed by the processor 401 to implement the various steps of the embodiment of the identification allocation method for the above-mentioned personal Internet of Things network, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0077] The embodiment of the present application also provides a network side device, including a processor and a communication interface, the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the various steps of the above-mentioned personal Internet of Things network identification allocation method embodiment. This network side device embodiment corresponds to the above-mentioned network side device method embodiment, and each implementation process and implementation method of the above-mentioned method embodiment can be applied to the network side device embodiment, and can achieve the same technical effect.

[0078] Specifically, the embodiment of the present application also provides a network side device. Figure 5 As shown, the network side device 500 includes: a processor 501, a network interface 502 and a memory 503. The network interface 502 is, for example, a common public radio interface (CPRI).

[0079] Specifically, the network side device 500 of the embodiment of the present application also includes: instructions or programs stored in the memory 503 and executable on the processor 501. The processor 501 calls the instructions or programs in the memory 503 to execute the various steps of the embodiment of the identification allocation method for the above-mentioned personal Internet of Things network and achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0080] The embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, each process of the embodiment of the identification allocation method for the above-mentioned personal Internet of Things network is implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0081] The processor is the processor in the terminal described in the above embodiment. The readable storage medium includes a computer readable storage medium, such as a computer read-only memory ROM, a random access memory RAM, a magnetic disk or an optical disk. In some examples, the readable storage medium may be a non-transient readable storage medium.

[0082] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the various processes of the embodiment of the identification allocation method for the above-mentioned personal Internet of Things network, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0083] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0084] It should be noted that, in this article, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the presence of other identical elements in the process, method, article or device including the element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in reverse order according to the functions involved. For example, the described method may be performed in an order different from that described, and various steps may also be added, omitted or combined. In addition, the features described with reference to certain examples may be combined in other examples.

[0085] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of a computer software product plus a necessary general hardware platform, and of course, can also be implemented by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, disk, CD, etc.), including several instructions to enable a terminal or a network-side device to execute the methods described in each embodiment of the present application.

[0086] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of the present application, ordinary technicians in this field can also make many forms of implementation methods without departing from the purpose of the present application and the scope of protection of the claims, and these implementation methods are all within the protection of the present application.< / temporaryidentity> < / temporaryidentity> < / afid> < / string1> < / string1>

Claims

1. A method for allocating identifiers for a personal Internet of Things network, characterized in that: include: The first network element allocates a PIN identifier for a target personal Internet of Things network PIN, wherein the PIN identifier is unique within the first network element; The first network element sends or configures the PIN identifier of the target PIN to the second network element.

2. The method according to claim 1, characterized in that The PIN identifier includes: a first character string, which is a character string allocated by the first network element and is unique in the first network element.

3. The method according to claim 2, characterized in that The PIN identifier further includes: a second character string, and the first character string and the second character string are connected by a preset symbol.

4. The method according to claim 2 or 3, characterized in that: The first network element includes: a target network element in a public land mobile network PLMN that provides services for the target PIN, wherein the target network element includes at least one of the following: a unified data management function and a network opening function.

5. The method according to claim 4, characterized in that The first character string includes one of the following: a group identifier of the target PIN, and a PIN name generated by the first network element.

6. The method according to claim 4, characterized in that In the case where the PIN identifier includes a second character string, the second character string includes: a domain name identifier.

7. The method according to any one of claims 3 to 6, characterized in that: The first network element allocates a PIN identifier for a target personal Internet of Things network PIN, including: The first network element allocates the PIN identifier to the target PIN based on the data network name or single network slice selection auxiliary information S-NSSAI dedicated to the target PIN.

8. The method according to any one of claims 3 to 6, characterized in that: The second network element includes one of the following: an application function AF, a policy control function entity PCF, and a user equipment UE.

9. The method according to claim 2 or 3, characterized in that: The first network element includes: an application function AF.

10. The method according to claim 9, characterized in that The first character string includes one of the following: an identifier of a PLMN, a temporary identifier allocated by the first network element, and an identifier of the first network element, wherein the temporary identifier is unique within the first network element.

11. The method according to claim 10, characterized in that The identifier of the PLMN is a unique identifier of the PLMN where the AF is located.

12. The method according to any one of claims 9 to 11, characterized in that: In the case where the PIN identifier includes a second character string, the second character string includes: an identifier of the first network element and a temporary identifier allocated by the first network element.

13. The method according to any one of claims 9 to 11, characterized in that: The second network element includes one of the following: PCF, UE.

14. The method according to any one of claims 1 to 13, characterized in that: The length of the PIN identifier is not fixed.

15. An identification allocation device for a personal Internet of Things network, applied to a first network element, characterized in that: The device comprises: An allocation module, configured to allocate a PIN identifier to a target personal Internet of Things network PIN, wherein the PIN identifier is unique within the first network element; The processing module is used to send or configure the PIN identifier of the target PIN to the second network element.

16. A network side device, characterized in that: It includes a processor and a memory, the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the identity allocation method for a personal Internet of Things network as described in any one of claims 1 to 14 are implemented.

17. A readable storage medium, characterized in that: The readable storage medium stores a program or instruction, and when the program or instruction is executed by the processor, the steps of the method for allocating an identifier of a personal Internet of Things network as described in any one of claims 1 to 14 are implemented.

Images