A method for personal internet of things network pin element registration and a communication device

Abstract

The disclosure provides a personal Internet of Things network PIN element registration method and a communication device, which can be applied to mobile communication technology. The method comprises the following steps: sending a registration request comprising PIN information to an access network device. Thus, the terminal device can register with the core network without knowing its role in the PIN, and the registration process is simple and efficient.

Description

Technical Field

[0001] This disclosure relates to the field of communication technology, and in particular to a method and communication device for registering a PIN element in a personal Internet of Things (IoT) network. Background Technology

[0002] A personal internet of things (PIN) network consists of PIN elements (PINEs) that communicate via direct PIN connections or direct network connections. In related technologies, terminal devices can register with a PIN server to subscribe to PIN services, and after subscribing, register with the core network based on their role within the PIN. Summary of the Invention

[0003] The first aspect of this disclosure provides a method for registering a personal Internet of Things (IoT) network PIN element, the method being performed by a terminal device, the method comprising:

[0004] Send a registration request to the access network device, wherein the registration request includes the PIN information of the terminal device.

[0005] A second aspect of this disclosure provides a method for registering a PIN element in a personal Internet of Things (IoT) network, the method being performed by an access network device, the method comprising:

[0006] Receive a first registration request sent by a terminal device, wherein the first registration request includes the PIN information of the terminal device;

[0007] A second registration request is sent to the Access and Mobility Management Function (AMF) network element, wherein the second registration request includes the PIN information of the terminal device.

[0008] A third aspect of this disclosure provides a method for registering a PIN element in a personal Internet of Things (IoT) network, the method being performed by an AMF (Active Network Function) element, the method comprising:

[0009] Receive a registration request sent by an access network device, and / or receive subscription data associated with a terminal device sent by a Unified Data Management (UDM) network element, wherein the registration request includes the PIN information of the terminal device;

[0010] The decision to accept the registration request is based on at least one of the following: the registration request, the contract data, the preset policy, and the core network capability information.

[0011] A fourth aspect of this disclosure provides a method for registering a personal Internet of Things (IoT) network PIN element, the method being performed by a UDM network element, the method comprising:

[0012] Send the subscription data associated with the terminal device to the Access and Mobility Management Function (AMF) network element.

[0013] A fifth aspect of this disclosure provides a communication device, including:

[0014] The transceiver module is used to send a registration request to the access network device, wherein the registration request includes the PIN information of the terminal device.

[0015] The sixth aspect of this disclosure provides another communication device, including:

[0016] Receive a registration request sent by a terminal device, wherein the registration request includes the PIN information of the terminal device;

[0017] The registration request is sent to the Access and Mobility Management Function (AMF) network element.

[0018] The seventh aspect of this disclosure provides another communication device, including:

[0019] The transceiver module is used to receive registration requests sent by access network devices, and / or receive subscription data associated with terminal devices sent by Unified Data Management (UDM) network elements, wherein the registration request includes the PIN information of the terminal device;

[0020] The decision to accept the registration request is based on at least one of the following: the registration request, the contract data, the preset policy, and the core network capability information.

[0021] An eighth aspect embodiment of this disclosure provides another communication device, including:

[0022] Send the subscription data associated with the terminal device to the Access and Mobility Management Function (AMF) network element.

[0023] A ninth aspect of this disclosure provides a communication device including a processor that, when the processor invokes a computer program in memory, executes the method described in the first aspect.

[0024] A tenth aspect embodiment of this disclosure provides a communication device including a processor that, when the processor invokes a computer program in memory, executes the method described in the second aspect above.

[0025] The eleventh aspect of this disclosure provides a communication device including a processor that, when the processor invokes a computer program in memory, executes the method described in the third aspect above.

[0026] A twelfth aspect of this disclosure provides a communication device including a processor that, when the processor invokes a computer program in memory, executes the method described in the fourth aspect above.

[0027] A thirteenth aspect of this disclosure provides a communication device including a processor and a memory storing a computer program; the processor executes the computer program stored in the memory to cause the communication device to perform the method described in the first aspect above.

[0028] A fourteenth aspect of this disclosure provides a communication device including a processor and a memory storing a computer program; the processor executes the computer program stored in the memory to cause the communication device to perform the method described in the second aspect above.

[0029] A fifteenth aspect of this disclosure provides a communication device including a processor and a memory storing a computer program; the processor executes the computer program stored in the memory to cause the communication device to perform the method described in the third aspect above.

[0030] A sixteenth aspect of this disclosure provides a communication device including a processor and a memory storing a computer program; the processor executes the computer program stored in the memory to cause the communication device to perform the method described in the fourth aspect above.

[0031] The seventeenth aspect of this disclosure provides another communication device, which includes a processor and an interface circuit for receiving code instructions and transmitting them to the processor, which executes the code instructions to cause the device to perform the method described in the first aspect above.

[0032] The eighteenth aspect of this disclosure provides another communication device, which includes a processor and an interface circuit for receiving code instructions and transmitting them to the processor, which executes the code instructions to cause the device to perform the method described in the second aspect above.

[0033] The nineteenth aspect of this disclosure provides another communication device, which includes a processor and an interface circuit for receiving code instructions and transmitting them to the processor, which executes the code instructions to cause the device to perform the method described in the third aspect above.

[0034] The twentieth aspect of this disclosure provides another communication device, which includes a processor and an interface circuit for receiving code instructions and transmitting them to the processor, which executes the code instructions to cause the device to perform the method described in the fourth aspect above.

[0035] The twenty-first aspect of this disclosure provides a communication system including the communication apparatus described in aspects five to eight above; or including the communication apparatus described in aspects nine to twelfth above; or including the communication apparatus described in aspects thirteen to sixteenth above; or including the communication apparatus described in aspects seventeen to twentieth above.

[0036] The twenty-second embodiment of this disclosure provides a computer-readable storage medium for storing instructions for use by the communication device described above, which, when executed, cause the communication device to perform the method described in the first aspect.

[0037] The twenty-third embodiment of this disclosure provides a computer-readable storage medium for storing instructions for use by the communication device described above, which, when executed, cause the communication device to perform the method described in the second aspect above.

[0038] The twenty-fourth embodiment of this disclosure provides a computer-readable storage medium for storing instructions for use by the communication device described above, which, when executed, cause the communication device to perform the method described in the third aspect above.

[0039] The twenty-fifth embodiment of this disclosure provides a computer-readable storage medium for storing instructions for use by the communication device described above, which, when executed, cause the communication device to perform the method described in the fourth aspect above.

[0040] The twenty-sixth aspect of this disclosure also provides a computer program product including a computer program that, when run on a computer, causes the computer to perform the method described in the first aspect above.

[0041] The twenty-seventh aspect of this disclosure also provides a computer program product including a computer program that, when run on a computer, causes the computer to perform the method described in the second aspect above.

[0042] The twenty-eighth aspect of this disclosure also provides a computer program product including a computer program that, when run on a computer, causes the computer to perform the method described in the third aspect above.

[0043] The twenty-ninth aspect of this disclosure also provides a computer program product including a computer program that, when run on a computer, causes the computer to perform the method described in the fourth aspect above.

[0044] A thirtieth aspect embodiment of this disclosure provides a chip system including at least one processor and an interface for supporting a communication device in implementing the functions involved in the first aspect, such as determining or processing at least one of the data and information involved in the above methods. In one possible design, the chip system further includes a memory for storing computer programs and data necessary for the communication device. The chip system may be composed of chips or may include chips and other discrete devices.

[0045] This disclosure provides a chip system comprising at least one processor and an interface for supporting a communication device in implementing the functions involved in the second aspect, such as determining or processing at least one of the data and information involved in the above-described methods. In one possible design, the chip system further includes a memory for storing computer programs and data necessary for the communication device. The chip system may be composed of chips or may include chips and other discrete devices.

[0046] This disclosure, in its thirty-second aspect, provides a chip system including at least one processor and an interface for supporting a communication device in implementing the functions involved in the third aspect, such as determining or processing at least one of the data and information involved in the above methods. In one possible design, the chip system further includes a memory for storing computer programs and data necessary for the communication device. The chip system may be composed of chips or may include chips and other discrete devices.

[0047] This disclosure provides a chip system comprising at least one processor and an interface for supporting a communication device in implementing the functions involved in the fourth aspect, such as determining or processing at least one of the data and information involved in the above methods. In one possible design, the chip system further includes a memory for storing computer programs and data necessary for the communication device. The chip system may be composed of chips or may include chips and other discrete devices.

[0048] The thirty-fourth aspect of this disclosure also provides a computer program that, when run on a computer, causes the computer to perform the method described in the first aspect.

[0049] The thirty-fifth aspect of this disclosure also provides a computer program that, when run on a computer, causes the computer to perform the method described in the second aspect above.

[0050] The thirty-sixth aspect of this disclosure also provides a computer program that, when run on a computer, causes the computer to perform the method described in the third aspect above.

[0051] The thirty-seventh aspect of this disclosure also provides a computer program that, when run on a computer, causes the computer to perform the method described in the fourth aspect above. Attached Figure Description

[0052] To more clearly illustrate the technical solutions in the embodiments or background art of this disclosure, the accompanying drawings used in the embodiments or background art of this disclosure will be described below.

[0053] Figure 1 This is a schematic diagram of the architecture of a communication system provided in an embodiment of the present disclosure;

[0054] Figure 2 This diagram illustrates the authorization and management process of the PIN and PIN element provided in the embodiments of this disclosure.

[0055] Figure 3 This is a schematic diagram illustrating the PEGC registration process with the core network provided in an embodiment of this disclosure;

[0056] Figure 4 This is a flowchart illustrating a method for registering a personal Internet of Things (IoT) network PIN element according to an embodiment of this disclosure;

[0057] Figure 5 This is a flowchart illustrating another method for registering a personal Internet of Things (IoT) network PIN element provided in an embodiment of this disclosure;

[0058] Figure 6 This is a flowchart illustrating another method for registering a personal Internet of Things (IoT) network PIN element provided in an embodiment of this disclosure;

[0059] Figure 7 This is a flowchart illustrating another method for registering a personal Internet of Things (IoT) network PIN element provided in an embodiment of this disclosure;

[0060] Figure 8 This is a flowchart illustrating another method for registering a personal Internet of Things (IoT) network PIN element provided in an embodiment of this disclosure;

[0061] Figure 9 This is a flowchart illustrating another method for registering a personal Internet of Things (IoT) network PIN element provided in an embodiment of this disclosure;

[0062] Figure 10 This is a flowchart illustrating another method for registering a personal Internet of Things (IoT) network PIN element provided in an embodiment of this disclosure;

[0063] Figure 11This is a flowchart illustrating another method for registering a personal Internet of Things (IoT) network PIN element provided in an embodiment of this disclosure;

[0064] Figure 12 This is a flowchart illustrating another method for registering a personal Internet of Things (IoT) network PIN element provided in an embodiment of this disclosure;

[0065] Figure 13 This is an interactive schematic diagram of a method for registering a personal Internet of Things (IoT) network PIN element according to an embodiment of this disclosure;

[0066] Figure 14 This is a schematic diagram of the structure of a communication device provided in an embodiment of this disclosure;

[0067] Figure 15 This is a schematic diagram of another communication device provided in an embodiment of this disclosure;

[0068] Figure 16 This is a schematic diagram of the chip structure provided in an embodiment of this disclosure. Detailed Implementation

[0069] To better understand the method and apparatus for registering a personal Internet of Things (IoT) network PIN element disclosed in this disclosure, the communication system to which this disclosure applies will be described first.

[0070] It should be noted that the term "includes" in this disclosure can mean either direct inclusion or indirect indication. For example, if A includes B, it can mean that A directly includes B, or it can mean that certain information in A can indirectly indicate B. This disclosure does not limit this.

[0071] Please see Figure 1 , Figure 1 This is a schematic diagram of the architecture of a communication system provided in an embodiment of this disclosure. The communication system may include, but is not limited to, an access network device, one or more core network devices, and a terminal device. Figure 1 The number and form of the devices shown are for illustrative purposes only and do not constitute a limitation on the embodiments of this disclosure. In actual applications, it may include two or more access network devices and two or more terminal devices. Figure 1 The communication system shown is an example comprising an access network device 11, a terminal device 12, an access and mobility management function (AMF) network element 13, and two core network devices, a unified data management (UDM) device 14.

[0072] It should be noted that the technical solutions of this disclosure can be applied to various communication systems. For example, Long Term Evolution (LTE) systems, 5th Generation (5G) mobile communication systems, 5G New Radio (NR) systems, or other future new mobile communication systems.

[0073] The access network device 11 in this disclosure is an entity on the access network side used for transmitting or receiving signals. For example, the access network device 11 can be an evolved NodeB (eNB), a transmission reception point (TRP), a next-generation NodeB (gNB) in an NR system, a base station in other future mobile communication systems, or an access node in a wireless fidelity (WiFi) system. This disclosure does not limit the specific technology or device form used in the access network device. The access network device provided in this disclosure can be composed of a central unit (CU) and a distributed unit (DU). The CU can also be called a control unit. Using a CU-DU structure, the protocol layer of the access network device, such as a base station, can be separated. Some protocol layer functions are centrally controlled by the CU, while the remaining part or all protocol layer functions are distributed in the DU, which is centrally controlled by the CU.

[0074] The terminal device in this disclosure is a user-side entity used to receive or transmit signals and possessing Internet of Things (IoT) functionality. Examples include mobile phones, wearable devices, smart home devices, smart office equipment, etc. Terminal devices can also be referred to as terminal equipment (UE), user equipment (UE), mobile station (MS), mobile terminal device (MT), etc. Terminal devices can be communication-enabled vehicles, smart cars, mobile phones, wearable devices, tablets, computers with wireless transceiver capabilities, virtual reality (VR) terminal devices, augmented reality (AR) terminal devices, wireless terminal devices in industrial control, wireless terminal devices in self-driving, wireless terminal devices in remote medical surgery, wireless terminal devices in smart grids, wireless terminal devices in transportation safety, wireless terminal devices in smart cities, wireless terminal devices in smart homes, etc. The embodiments disclosed herein do not limit the specific technology or device form used in the terminal device.

[0075] In this embodiment, AMF network element 13 is a logical node functional network element on the core network side. It serves as the core network control plane access point for terminal devices and wireless communication. It receives all connection and session-related information from the terminal devices and performs registration, connection, reachability, and mobility management. UDM network element 14 is a network element on the core network side used for data storage and management. It is responsible for the management of user identifiers, subscription data, authentication data, and the registration management of user service network elements (such as AMFs).

[0076] This disclosure does not limit the names of AMF network elements and UDM network elements. Based on having the above-mentioned functions of AMF network elements or UDM network elements, their names can be adjusted arbitrarily as needed.

[0077] It is understood that the communication system described in the embodiments of this disclosure is for the purpose of more clearly illustrating the technical solutions of the embodiments of this disclosure, and does not constitute a limitation on the technical solutions provided in the embodiments of this disclosure. As those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this disclosure are also applicable to similar technical problems.

[0078] Figure 2This is a schematic diagram illustrating the authorization and management process of PINs and PIN elements provided in embodiments of this disclosure.

[0079] like Figure 2 As shown, assuming the PIN element can communicate with the PIN application server (PIN AS) via the Internet, then as follows: Figure 2 Steps 1, 2, and 3, shown in the dashed box, are the process of registering various PIN elements, such as PINE, PIN element with gateway capability (PEGC), and PIN element with management capability (PEMC), to the PIN AS. This includes PIN element authentication and authorization, reporting the PIN element identifier (ID) and PIN element configuration file to the PIN AS, etc.

[0080] Step 4, create a PIN.

[0081] After successful registration, PEMC can send a request to PINAS to create a PIN. The PIN ID can be assigned to PEMC by PINAS.

[0082] Step 5: Add PEGC to the PIN.

[0083] PEMC can then request PIN AS to add PEGC to PIN. If PEGC accepts the invitation, PIN AS updates PIN's configuration file and context data, and PIN AS sends configuration and parameters to PEGC for PIN communication.

[0084] Step 6: The PIN AS provides PIN service parameters to the unified data repository (UDR) functional network element for PEGC policy control. For example, it can provide the PIN ID, default Quality of Service (QoS) requirements, and the validity period of PIN communication.

[0085] Optionally, the PIN AS can provide PIN service parameters to the UDR through the network exposure function (NEF) network element.

[0086] Step 7: PEMC requests PIN AS to add PINE to PIN.

[0087] This includes PINE communication requirements, such as the associated PEGC, whether the PINE is authorized to access the network system through the PEGC, and QoS requirements. If the PIN accepts the invitation, the PIN AS will update the PIN profile and context data. The PIN AS sends configuration and parameters to the PINE and PEGC for PIN communication.

[0088] Step 8: PIN AS updates the PIN service parameters to UDR (via NEF).

[0089] Used for associating PINE with PEGC. This includes providing the PINE ID, default QoS requirements, and the effective duration of communication between the PINE and the communication system.

[0090] PIN element through Figure 2 As shown, after PIN AS completes registration, the PEGC terminal device in the PIN can then register with the core network. Figure 3 This is a schematic diagram illustrating the PEGC registration process to the core network provided in an embodiment of this disclosure. Figure 3 As shown, the registration process includes:

[0091] 1. PEGC sends a registration request to the access network equipment.

[0092] This request is used to indicate that the terminal device is a PIN element with network management capabilities.

[0093] Optionally, the access network equipment can be an eNB, gNB, etc., but this disclosure does not limit it.

[0094] 2. The access network device sends the registration request to the AMF.

[0095] 3. AMF obtains the contract data of PEGC terminal devices from UDM.

[0096] Optionally, the contract data may include information such as the maximum number of PINE / PINs running, PIN duration, and permitted services.

[0097] 4. If the contracted data allows the terminal device to act as a PEGC, the AMF returns a registration acceptance message to the access network device.

[0098] Optionally, the received message may include parameters for the PIN service, such as PIN duration and allowed services.

[0099] 5. The access network device returns a registration acceptance message to the terminal device.

[0100] Optionally, if the signed data does not run the terminal device charging PEGC, the AMF returns a registration rejection message to the access network device.

[0101] Optionally, the registration rejection message may also include information such as the reason for rejection.

[0102] In other words, after a terminal device completes registration with the PIN AS and knows its role in the PIN, it can register with the core network through the above process.

[0103] This disclosure proposes a method for registering a PIN element with the core network. Terminal devices can also register with the core network using the method provided in this disclosure, whether they have signed up for a PIN service or not, and even if they do not know their role in the PIN.

[0104] The following description, in conjunction with the accompanying drawings, details a method and apparatus for registering a personal Internet of Things (IoT) network PIN element provided in this disclosure.

[0105] It should be noted that the following embodiments and optional embodiments of this disclosure can be combined with each other to implement the PIN element registration process, provided that there is no contradiction. Furthermore, when combining the embodiments, the order of the steps can be changed, provided there is no contradiction.

[0106] Please see Figure 4 , Figure 4 This is a flowchart illustrating a method for registering a personal Internet of Things (IoT) network PIN element according to an embodiment of this disclosure. This method is executed by a terminal device. Figure 4 As shown, the method may include, but is not limited to, the following steps:

[0107] Step 401: Send a registration request to the access network device, wherein the registration request includes the PIN information of the terminal device.

[0108] In this disclosure, the terminal device can be PINE, or PEGC, or PEMC; this disclosure does not limit the type of device.

[0109] Optionally, when sending a registration request, the terminal device is unaware of its role in the PIN. That is, the terminal device is unaware that it acts as a PEGC, a PEMC, or both in the PIN.

[0110] In some possible implementations, the terminal device may have already signed up for the PIN service or may not have signed up for the PIN service when sending the registration request; this disclosure does not limit this.

[0111] In some possible implementations, the PIN information includes at least one of the following: PIN capability indication information, PIN element management function PEMC indication information, and PIN element gateway function PEGC indication information.

[0112] Optional, PIN capability indication information, used to indicate whether the terminal device supports PIN capability.

[0113] Optionally, the PIN information may directly include PIN capability indication information. For example, a specific bit in the PIN information is used to indicate the PIN capability of the terminal device. When the specific bit is a first value, it indicates that the terminal device supports PIN capability. When the specific bit is a second value, it indicates that the terminal device does not support PIN capability. The first value and the second value can be any different values, and this disclosure does not limit them.

[0114] Optionally, the PIN information may not directly contain PIN capability indication information, but may indirectly indicate the PIN capability indication information through other information. For example, if the PIN information contains PEGC indication information, and this indication information indicates that the terminal device has PEGC capability, then it indirectly indicates that the terminal device supports PIN capability, etc. This disclosure does not limit this.

[0115] Optional, PIN element management function PEMC indication information, used to indicate whether the terminal device has PEMC capability.

[0116] In some possible implementations, the PIN information may directly include PEMC indication information. For example, a specific bit in the PIN information may be used to represent PEMC indication information. When the specific bit is a third value, it indicates that the terminal device supports PEMC capability; when the specific bit is a fourth value, it indicates that the terminal device does not support PEMC capability. The third and fourth values ​​can be any different values, and this disclosure does not limit this. Alternatively, the PIN information may not directly include PEMC indication information, but may indirectly indicate PEMC indication information through other information.

[0117] Optionally, PIN element gateway function PEGC indication information is used to indicate whether the terminal device has PEGC capability.

[0118] In some possible implementations, the PIN information may directly include PEGC indication information. For example, a specific bit in the PIN information may be used to represent the PEGC indication information. When the specific bit is the fifth value, it indicates that the terminal device supports PEGC capability; when the specific bit is the sixth value, it indicates that the terminal device does not support PEGC capability. The fifth and sixth values ​​can be any different values, and this disclosure does not limit this. Alternatively, the PIN information may not directly include the PEGC indication information, but may indirectly indicate it through other information.

[0119] In some possible implementations, the first, second, third, fourth, fifth, and sixth values ​​mentioned above may all be different, or they may include the same value. For example, the first, third, and fifth values ​​may be the same, and the second, fourth, and sixth values ​​may be the same; or the first, fourth, and fifth values ​​may be the same, and the second, third, and sixth values ​​may be the same, etc. This disclosure does not limit this. The above values ​​may be configured, pre-configured, or agreed upon by the access network equipment, and this disclosure does not limit this.

[0120] This embodiment can be arbitrarily combined with other embodiments without contradiction, and can be combined with optional embodiments from other embodiments, and the order of steps in the combination can be interchanged without contradiction. The optional embodiments in this embodiment can also be arbitrarily combined with other embodiments of this disclosure, or with optional embodiments from other embodiments, without contradiction.

[0121] In this embodiment of the disclosure, the terminal device can complete the registration with the core network by sending a registration request to the access network device, which includes information indicating its PIN. The registration process does not require the terminal device to know its role in the PIN, thus improving registration efficiency and saving registration time.

[0122] Please see Figure 5 , Figure 5 This is a flowchart illustrating another method for registering a personal Internet of Things (IoT) network PIN element according to an embodiment of this disclosure, which is executed by a terminal device. Figure 5 As shown, the method may include, but is not limited to, the following steps:

[0123] Step 501: Send a registration request to the access network device, wherein the registration request includes the PIN information of the terminal device.

[0124] Optionally, the PIN information includes at least one of the following: PIN capability indication information, PIN element management function PEMC indication information, and PIN element gateway function PEGC indication information.

[0125] The specific implementation of step 501 above can be found in the detailed description of any embodiment of this disclosure, and will not be repeated here.

[0126] Step 502: Receive the registration response returned by the access network device.

[0127] In some possible implementations, the registration response is generated by the AMF and sent to the terminal device through the access network device, which can be used to indicate to the terminal device whether the core network accepts the terminal device's registration request.

[0128] In some possible implementations, the registration response includes at least one of the following: a PIN service support indication, a PEMC permission indication, or a PEGC permission indication. The PIN service support indication can be used to indicate that the network supports PIN services.

[0129] Optionally, when the AMF accepts a registration request from a terminal device, the registration response may include at least one of the following: PIN service support indication, PEMC permission indication, or PEGC permission indication.

[0130] Optionally, the registration response may include indication information that directly tells the AMF whether to accept the registration request of the terminal device.

[0131] Alternatively, the registration response can indirectly indicate to the AMF whether it accepts the terminal device's registration request through the information it contains. Therefore, if the registration response includes at least one of the above indications after the terminal device receives it, it can be determined that its registration request has been accepted by the core network; otherwise, it can be determined that its registration request has been rejected by the core network.

[0132] Optionally, the registration response can directly include an indication of PIN service support. For example, a specific bit in the registration response can indicate that the network supports PIN service when it takes a first specific value. Conversely, when the specific bit takes a value other than the first specific value, it indicates that the network does not support PIN service.

[0133] Optionally, the registration response may not directly include the PIN service support instruction, but may indirectly indicate the PIN service support instruction through other information; this disclosure does not limit this.

[0134] In some possible implementations, the PEMC allows indications that the terminal device is permitted to act as the PEMC in the PIN, as indicated in the terminal device's subscription information.

[0135] Optionally, the registration response may directly include a PEMC permission indication. For example, if a specific bit in the registration response takes a second specific value, it indicates that the subscription information allows it to act as a PEMC. Conversely, if the specific bit takes a value other than the second specific value, it indicates that the subscription information does not allow it to act as a PEMC. Alternatively, the registration response may not directly include a PEMC permission indication, but may indirectly indicate it through other information; this disclosure does not limit this approach.

[0136] In some possible implementations, PEGC allows indications that the terminal device is permitted to act as a PEGC in the PIN within the terminal device's subscription information.

[0137] Optionally, the registration response may directly include a PEGC permission indication. For example, when a specific bit in the registration response takes a third specific value, it indicates that the contract information allows it to act as a PEGC. When the specific bit takes a value other than the third specific value, it indicates that it is not allowed to act as a PEGC. Alternatively, the registration response may not directly include the PEGC permission indication, but may indirectly indicate the PEGC permission indication through other information. This disclosure does not limit this approach.

[0138] In some possible implementations, when the registration request of the terminal device is not accepted, the registration response may include at least one of the following: indication that PIN service is not supported, indication that PEMC does not allow it, and indication that PEGC does not allow it. Alternatively, it may include other indication information, such as the reason for rejection. This disclosure does not limit this.

[0139] In some possible implementations, the aforementioned specific bits may be the same bits in the registration response, or they may be different bits in the registration response; this disclosure does not limit this.

[0140] This embodiment, or any step thereof, can be arbitrarily combined with other embodiments without contradiction, and can be combined with optional embodiments of other embodiments. Furthermore, the order of steps in the combination can be interchanged without contradiction. Optional embodiments in this embodiment can also be arbitrarily combined with other embodiments of this disclosure, or with optional embodiments of other embodiments, without contradiction.

[0141] In this embodiment of the disclosure, the terminal device can request registration with the core network by sending a registration request, including its PIN information, to the access network device, and determine whether the network has accepted the registration request based on the registration response returned by the access network device. The terminal device can register with the core network not only without knowing its role in the PIN, but also can determine whether its registration request has been accepted, making the registration process simple.

[0142] Please see Figure 6 , Figure 6 This is a flowchart illustrating another method for registering a personal Internet of Things (IoT) network PIN element according to an embodiment of this disclosure, which is executed by an access network device. Figure 6 As shown, the method may include, but is not limited to, the following steps:

[0143] Step 601: Receive a first registration request sent by the terminal device, wherein the first registration request includes the PIN information of the terminal device.

[0144] Optionally, the PIN information includes at least one of the following: PIN capability indication information, PIN element management function PEMC indication information, and PIN element gateway function PEGC indication information.

[0145] The possible forms of the above registration request and PIN information can be described in detail with reference to any embodiment of this disclosure, and will not be repeated here.

[0146] Step 602: Send a second registration request to the AMF network element, wherein the second registration request includes the PIN information of the terminal device.

[0147] Optionally, the second registration request may also include the identifier of the access network device.

[0148] After receiving the first registration request from the terminal device, the access network device can send a second registration request to the AMF network element on the core network side based on the first registration request, so as to send the PIN information in the first registration request to the AMF network element.

[0149] This embodiment, or any step thereof, can be arbitrarily combined with other embodiments without contradiction, and can be combined with optional embodiments of other embodiments. Furthermore, the order of steps in the combination can be interchanged without contradiction. Optional embodiments in this embodiment can also be arbitrarily combined with other embodiments of this disclosure, or with optional embodiments of other embodiments, without contradiction.

[0150] In this embodiment of the disclosure, after receiving the registration request sent by the terminal device, the access network device can forward the registration request to the core network device, thereby realizing the registration of the terminal device to the core network. The registration process is simple and consumes less resources of the access network device.

[0151] Please see Figure 7 , Figure 7 This is a flowchart illustrating another method for registering a personal Internet of Things (IoT) network PIN element according to an embodiment of this disclosure, which is executed by an access network device. Figure 7 As shown, the method may include, but is not limited to, the following steps:

[0152] Step 701: Receive a first registration request sent by the terminal device, wherein the first registration request includes the PIN information of the terminal device.

[0153] Step 702: Send a second registration request to the AMF network element, wherein the second registration request includes the PIN information of the terminal device.

[0154] Optionally, the PIN information includes at least one of the following: PIN capability indication information, PIN element management function PEMC indication information, and PIN element gateway function PEGC indication information.

[0155] The specific implementation of steps 701 and 702 above, as well as the PIN information, can be found in the detailed description of other embodiments of this disclosure, and will not be repeated here.

[0156] Step 703: Receive the first registration response returned by the AMF network element.

[0157] Step 704: Send a second registration response to the terminal device.

[0158] Optionally, the first registration response and the second registration response are used to indicate whether the AMF accepts the registration request of the terminal device.

[0159] Optionally, the first registration response and the second registration response may contain indication information that directly indicates whether the AMF accepts the registration request of the terminal device; or, the first registration response and the second registration response may indirectly indicate whether the AMF accepts the registration request of the terminal device through the information contained therein.

[0160] Optionally, if the registration request is accepted, the first registration response and the second registration response may include at least one of the following: PIN service support indication, PEMC permission indication, and PEGC permission indication.

[0161] The implementation form of the registration response can be referred to in the detailed description of other embodiments of this disclosure, and will not be repeated here.

[0162] This embodiment, or any step thereof, can be arbitrarily combined with other embodiments without contradiction, and can be combined with optional embodiments of other embodiments. Furthermore, the order of steps in the combination can be interchanged without contradiction. Optional embodiments in this embodiment can also be arbitrarily combined with other embodiments of this disclosure, or with optional embodiments of other embodiments, without contradiction.

[0163] In this embodiment of the disclosure, during the registration process of the terminal device, the access network device only needs to forward the registration request and registration response. The access network device consumes fewer resources, and the registration process is fast and efficient.

[0164] Please see Figure 8 , Figure 8 This is a flowchart illustrating another method for registering a personal Internet of Things (IoT) network PIN element according to an embodiment of this disclosure, which is executed by an AMF network element. Figure 8 As shown, the method may include, but is not limited to, the following steps:

[0165] Step 801: Receive a registration request sent by the access network device, and / or receive subscription data associated with the terminal device sent by the UDM network element, wherein the registration request includes the PIN information of the terminal device.

[0166] In some possible implementations, the registration request is sent by the terminal device to the access network device, and then forwarded by the access network device to the AMF.

[0167] Optionally, the PIN information includes at least one of the following: PIN capability indication information, PIN element management function PEMC indication information, and PIN element gateway function PEGC indication information.

[0168] The specific implementation of the PIN information can be found in the detailed description of other embodiments of this disclosure, and will not be repeated here.

[0169] In some possible implementations, if the terminal device has already completed PIN signing, the AMF can obtain the terminal device's signing data from the UDM. This signing data may include at least one of the following: PEMC permission indication, PEGC permission indication.

[0170] The meanings of the PEMC allow indication and the PEGC allow indication can be found in the detailed description of other embodiments of this disclosure, and will not be repeated here.

[0171] In some possible implementations, if the terminal device does not have a signed PIN, the AMF will not obtain the terminal device's signed PIN from the UDM.

[0172] Step 802: Determine whether to accept the registration request based on at least one of the following: registration request, contract data, pre-configured policies, or core network capability information.

[0173] Optionally, the preset policy can be a policy based on protocol agreements or a policy pre-configured in the AMF. This may include information such as whether the region currently registered to the terminal device allows PIN services. Core network capability information may include information such as whether the core network has the capability to support PIN services.

[0174] In some possible implementations, after receiving a registration request and / or subscription data associated with the terminal device, the AMF can determine whether to accept the registration request based on one or more of the following: the registration request, the subscription data, the pre-configured policies, and the core network's capability information.

[0175] For example, if the AMF does not receive the contract data but has pre-configured policies and core network capability information locally, the AMF can determine whether to accept the registration request based on the registration request, the pre-configured policies, and the core network capability information. Alternatively, if the AMF does not receive the contract data but has core network capability information locally, the AMF can determine whether to accept the registration request based on the registration request and the core network capability information.

[0176] In some possible implementations, if the registration request indicates that the terminal device has PEMC capability, the subscription data allows the terminal device to act as a PEMC in the PIN, the preset policy indicates that the area currently registered by the terminal device allows PIN services, and the core network capability information indicates that the network supports PIN services, then the AMF can determine to accept the registration request.

[0177] In some possible implementations, if the registration request indicates that the terminal device has PEMC capability and the subscription data does not allow the terminal device to act as a PEMC in the PIN, then the AMF can determine that it will not accept the registration request.

[0178] In some possible implementations, if the registration request includes PIN capability indication information, but the core network capability information indicates that the core network does not support PIN services, then the AMF can determine not to accept the registration request, and so on.

[0179] It should be noted that the above-mentioned possible forms are merely illustrative descriptions of the process by which the AMF determines whether to accept a registration request based on at least one of the following: registration request, contract data, pre-set policies, and core network capability information. They should not be construed as restrictive descriptions of the AMF's determination of whether to accept a registration request.

[0180] This embodiment, or any step thereof, can be arbitrarily combined with other embodiments without contradiction, and can be combined with optional embodiments of other embodiments. Furthermore, the order of steps in the combination can be interchanged without contradiction. Optional embodiments in this embodiment can also be arbitrarily combined with other embodiments of this disclosure, or with optional embodiments of other embodiments, without contradiction.

[0181] In this embodiment of the disclosure, after receiving a registration request sent by the access network device and / or subscription data sent by the UDM, the AMF can determine whether to accept the registration request based on at least one of the registration request, subscription data, preset policies, and core network capability information. The registration process does not require the terminal device to report its role in the PIN, and the registration process is simple.

[0182] Please see Figure 9 , Figure 9This is a flowchart illustrating another method for registering a personal Internet of Things (IoT) network PIN element according to an embodiment of this disclosure, which is executed by an AMF network element. Figure 9 As shown, the method may include, but is not limited to, the following steps:

[0183] Step 901: Receive a registration request sent by the access network device, wherein the registration request includes the PIN information of the terminal device.

[0184] Optionally, the PIN information includes at least one of the following: PIN capability indication information, PIN element management function PEMC indication information, and PIN element gateway function PEGC indication information.

[0185] The specific implementation of step 901 and the PIN information can be found in the detailed description of other embodiments of this disclosure, and will not be repeated here.

[0186] Step 902: Send a subscription data acquisition request to the UDM network element, wherein the subscription data acquisition request includes the identifier of the terminal device.

[0187] Step 903: Receive the subscription data associated with the terminal device sent by the UDM network element.

[0188] In some possible implementations, if the terminal device has already completed PIN signing, the AMF can obtain the terminal device's signing data from the UDM. This signing data may include at least one of the following: PEMC permission indication, PEGC permission indication.

[0189] The meanings of the PEMC allow indication and the PEGC allow indication can be found in the detailed description of other embodiments of this disclosure, and will not be repeated here.

[0190] In some possible implementations, if the terminal device does not have a signed PIN, the AMF will not obtain the terminal device's signed PIN from the UDM.

[0191] Step 904: Determine whether to accept the registration request based on at least one of the following: registration request, contract data, pre-configured policies, core network capability information.

[0192] The specific implementation of step 904 above can be found in the detailed description of other embodiments of this disclosure, and will not be repeated here.

[0193] This embodiment, or any step thereof, can be arbitrarily combined with other embodiments without contradiction, and can be combined with optional embodiments of other embodiments. Furthermore, the order of steps in the combination can be interchanged without contradiction. Optional embodiments in this embodiment can also be arbitrarily combined with other embodiments of this disclosure, or with optional embodiments of other embodiments, without contradiction.

[0194] In this disclosure, after receiving a registration request from a terminal device forwarded by an access network device, the AMF can send a subscription data acquisition request to the UDM. After acquiring the subscription data associated with the terminal device, the AMF can determine whether to accept the registration request based on at least one of the registration request, the subscription data, the preset policy, and the core network capability information. This registration process only requires a small amount of AMF resources and is simple.

[0195] Please see Figure 10 , Figure 10 This is a flowchart illustrating another method for registering a personal Internet of Things (IoT) network PIN element according to an embodiment of this disclosure, which is executed by the AMF. Figure 10 As shown, the method may include, but is not limited to, the following steps:

[0196] Step 1001: Receive a registration request sent by the access network device, wherein the registration request includes the PIN information of the terminal device.

[0197] Optionally, the PIN information includes at least one of the following: PIN capability indication information, PIN element management function PEMC indication information, and PIN element gateway function PEGC indication information.

[0198] Step 1002: Send a subscription data acquisition request to the UDM network element, wherein the subscription data acquisition request includes the identifier of the terminal device.

[0199] Step 1003: Receive the subscription data associated with the terminal device sent by the UDM network element.

[0200] In some possible implementations, if the terminal device has already completed PIN signing, the AMF can obtain the terminal device's signing data from the UDM. This signing data may include at least one of the following: PEMC permission indication, PEGC permission indication.

[0201] The meanings of the PEMC allow indication and the PEGC allow indication can be found in the detailed description of other embodiments of this disclosure, and will not be repeated here.

[0202] In some possible implementations, if the terminal device does not have a signed PIN, the AMF will not obtain the terminal device's signed PIN from the UDM.

[0203] Step 1004: Determine whether to accept the registration request based on at least one of the following: registration request, contract data, pre-configured policies, core network capability information.

[0204] The specific implementation of steps 1001 to 1004 above can be found in the detailed description of any embodiment of this disclosure, and will not be repeated here.

[0205] Step 1005: Send a registration response to the access network device.

[0206] In some possible implementations, after determining whether to accept the registration request, the AMF can also send a registration response to the access network device to synchronize the processing result of the registration request to the terminal device.

[0207] Optionally, the registration response may include indication information that directly indicates whether the AMF accepts the registration request of the terminal device, or the registration response may indirectly indicate whether the AMF accepts the registration request of the terminal device through the information contained therein.

[0208] Optionally, if the AMF determines that the registration request is accepted, the registration response may include at least one of the following: a PEMC permission indication or a PEGC permission indication.

[0209] Optionally, the core network capability information indicates that the core network has the capability to support the PIN service, and the registration response also includes a PIN service support indication.

[0210] The meanings and possible implementations of the PEMC allow indication, PEGC allow indication, and PIN service support indication can be found in the detailed descriptions of other embodiments of this disclosure, and will not be repeated here.

[0211] This embodiment, or any step thereof, can be arbitrarily combined with other embodiments without contradiction, and can be combined with optional embodiments of other embodiments. Furthermore, the order of steps in the combination can be interchanged without contradiction. Optional embodiments in this embodiment can also be arbitrarily combined with other embodiments of this disclosure, or with optional embodiments of other embodiments, without contradiction.

[0212] In this embodiment of the disclosure, after receiving the registration request of the terminal device forwarded by the access network device, the AMF can send a subscription data acquisition request to the UDM. After acquiring the subscription data associated with the terminal device, the AMF can determine whether to accept the registration request based on at least one of the registration request, the subscription data, the preset policy, and the core network capability information, and send a registration response to the access network device to synchronize the result of the registration request to the terminal device. This registration process can be implemented without the terminal device reporting its role in the PIN, which consumes less resources and is simple to implement.

[0213] Please see Figure 11 , Figure 11 This is a flowchart illustrating another method for registering a personal Internet of Things (IoT) network PIN element according to an embodiment of this disclosure, which is executed by a UDM network element. Figure 11 As shown, the method may include, but is not limited to, the following steps:

[0214] Step 1101: Send the subscription data associated with the terminal device to the AMF network element.

[0215] Optionally, the contract data may include at least one of the following: PEMC permission indication, PEGC permission indication.

[0216] The meaning and possible implementation of the above-mentioned PEMC allow indication and PEGC allow indication can be found in the detailed description of other embodiments of this disclosure, and will not be repeated here.

[0217] Optionally, UDM can proactively send the subscription data to AMF after determining the subscription data associated with the terminal device.

[0218] Alternatively, the UDM may send subscription data to the AMF after the transmission conditions are met. These transmission conditions can be a preset time interval, a triggering mechanism from other devices, etc., and this disclosure does not limit the specifics.

[0219] This embodiment, or any step thereof, can be arbitrarily combined with other embodiments without contradiction, and can be combined with optional embodiments of other embodiments. Furthermore, the order of steps in the combination can be interchanged without contradiction. Optional embodiments in this embodiment can also be arbitrarily combined with other embodiments of this disclosure, or with optional embodiments of other embodiments, without contradiction.

[0220] In this embodiment of the disclosure, the UDM sends the subscription data associated with the terminal device to the AMF to assist the AMF in determining whether to accept the registration request of the terminal device.

[0221] Please see Figure 12 , Figure 12This is a flowchart illustrating another method for registering a personal Internet of Things (IoT) network PIN element according to an embodiment of this disclosure, which is executed by a UDM. Figure 12 As shown, the method may include, but is not limited to, the following steps:

[0222] Step 1201: Receive a subscription data acquisition request sent by the AMF network element, wherein the subscription data acquisition request includes the identifier of the terminal device.

[0223] Step 1202: Send the subscription data associated with the terminal device to the AMF network element.

[0224] Optionally, the contract data may include at least one of the following: PEMC permission indication, PEGC permission indication.

[0225] The meaning and possible implementation of the above-mentioned PEMC allow indication and PEGC allow indication can be found in the detailed description of other embodiments of this disclosure, and will not be repeated here.

[0226] Optionally, if the UDM receives a subscription request from the AMF but it does not contain subscription data from the terminal device, it can also send empty subscription data to the AMF network element.

[0227] This embodiment, or any step thereof, can be arbitrarily combined with other embodiments without contradiction, and can be combined with optional embodiments of other embodiments. Furthermore, the order of steps in the combination can be interchanged without contradiction. Optional embodiments in this embodiment can also be arbitrarily combined with other embodiments of this disclosure, or with optional embodiments of other embodiments, without contradiction.

[0228] In this embodiment of the disclosure, after receiving the subscription data acquisition request sent by the AMF, the UDM can send the subscription data associated with the terminal device to the AMF, thereby providing auxiliary conditions for the registration process of the terminal device.

[0229] To facilitate understanding of the method for registering a personal Internet of Things (IoT) network PIN element disclosed herein, the following is combined with... Figure 13 The illustrated embodiments will be further explained. Figure 13 This is an interactive schematic diagram of a method for registering a personal Internet of Things (IoT) network PIN element according to an embodiment of this disclosure.

[0230] Figure 13 The illustrated embodiment assumes that the UE (terminal device) is unaware of its role (acting as PEGC or PEMC or both) when sending the registration request, and that the UE may or may not sign up for the PIN service.

[0231] The method includes the following steps:

[0232] Step 1301: The UE sends a registration request to the gNB.

[0233] Optionally, the registration request may include a PIN capability indication, PEGC capability, and / or PEMC capability.

[0234] Step 1302: gNB sends a registration request to AMF.

[0235] This includes the PIN capability indication from step 1.

[0236] Step 1303: AMF sends a subscription data acquisition request to UDM to obtain the UE's subscription data.

[0237] Optionally, the contract data retrieval request can be Nudm_Get_SDM, which may include the identifier of the terminal device.

[0238] Step 1304: UDM sends a Nudm_Get_SDM response to AMF, including the UE's subscription data.

[0239] The contract data may include PIN information, for example, indicating the UE as PEMC or / and PEGC.

[0240] Step 1305: The AMF determines whether to accept the registration request based on the UE request and / or UE subscription data from the UDM and / or pre-configured policies and / or core network capability information.

[0241] If the network has the capability to support PIN services, the AMF will accept a PIN service support instruction in the registration request.

[0242] When the PIN information provided by the UDM indicates that the UE can act as a PEGC or / and PEMC, the registration acceptance message will include additional information, such as indications of PEGC permission and / or PEMC permission.

[0243] Step 1306: AMF sends a registration acceptance message to gNB.

[0244] It should be noted that if the AMF determines that it does not accept the registration request, it will send a registration request rejection message to the gNB.

[0245] Step 1307: gNB sends a registration acceptance message to UE.

[0246] The registration acceptance message may include the parameters carried in step 1305.

[0247] This embodiment, or any step thereof, can be arbitrarily combined with other embodiments without contradiction, and can be combined with optional embodiments of other embodiments. Furthermore, the order of steps in the combination can be interchanged without contradiction. Optional embodiments in this embodiment can also be arbitrarily combined with other embodiments of this disclosure, or with optional embodiments of other embodiments, without contradiction.

[0248] Please see Figure 14 , Figure 14 This is a schematic diagram of the structure of a communication device provided in an embodiment of this disclosure. Figure 14 The communication device 1400 shown may include a processing module 1401 and a transceiver module 1402. The transceiver module 1402 may include a sending module and / or a receiving module. The sending module is used to implement the sending function, and the receiving module is used to implement the receiving function. The transceiver module 1402 can implement both sending and / or receiving functions.

[0249] It is understandable that the communication device 1400 can be a terminal device, a device within a terminal device, or a device that can be used in conjunction with a terminal device.

[0250] The communication device 1400 is on the terminal equipment side, wherein:

[0251] The transceiver module 1402 is used to send a registration request to the access network device, wherein the registration request includes the PIN information of the terminal device.

[0252] Optionally, the transceiver module 1402 is also used to receive the registration response returned by the access network device.

[0253] Optionally, the PIN information includes at least one of the following: PIN capability indication information, PIN element management function PEMC indication information, and PIN element gateway function PEGC indication information.

[0254] Optionally, the registration response includes at least one of the following:

[0255] PIN service support indication, PEMC permission indication, PEGC permission indication.

[0256] In this disclosure, a terminal device can request registration with the core network by sending a registration request to an access network device, including a PIN information indicating its PIN, and determine whether the network has accepted the registration request based on the registration response returned by the access network device. The terminal device can register with the core network not only without knowing its role in the PIN, but also can determine whether its registration request has been accepted, making the registration process simple.

[0257] It is understood that the communication device 1400 can be an access network device, a device within an access network device, or a device that can be used in conjunction with an access network device.

[0258] Communication device 1400 is located on the access network equipment side, wherein:

[0259] The transceiver module 1402 is configured to receive a first registration request sent by a terminal device, wherein the first registration request includes the PIN information of the terminal device; and send a second registration request to an Access and Mobility Management Function (AMF) network element, wherein the second registration request includes the PIN information of the terminal device.

[0260] Optionally, the transceiver module 1402 is further configured to:

[0261] Receive the first registration response returned by the AMF network element;

[0262] Send a second registration response to the terminal device.

[0263] The PIN information includes at least one of the following:

[0264] Optional information includes PIN capability indication, PIN element management function PEMC indication, and PIN element gateway function PEGC indication.

[0265] Optionally, the first registration response and the second registration response may include at least one of the following: PIN service support indication, PEMC permission indication, and PEGC permission indication.

[0266] In this embodiment of the disclosure, during the registration process of the terminal device, the access network device only needs to forward the registration request and registration response. The access network device consumes fewer resources, and the registration process is fast and efficient.

[0267] It is understandable that the communication device 1400 can be an AMF network element, a device within an AMF network element, or a device that can be used in conjunction with an AMF network element.

[0268] Communication device 1400 is located on the AMF network element side, wherein:

[0269] The transceiver module 1402 is used to receive a registration request sent by an access network device, and / or to receive subscription data associated with a terminal device sent by a unified data management function (UDM) network element, wherein the registration request includes the PIN information of the terminal device;

[0270] The processing module 1401 is configured to determine whether to accept the registration request based on at least one of the following: the registration request, the contract data, the preset policy, and the core network capability information.

[0271] Optionally, the transceiver module 1402 is further configured to send a subscription data acquisition request to the UDM network element, wherein the subscription data acquisition request includes the identifier of the terminal device.

[0272] Optionally, the transceiver module 1402 is also used to send a registration response to the access network device.

[0273] Optionally, the PIN information includes at least one of the following:

[0274] PIN capability indication information, PIN element management function PEMC indication information, PIN element gateway function PEGC indication information;

[0275] The contract data includes at least one of the following: PEMC permission indication, PEGC permission indication.

[0276] Optionally, the registration response includes at least one of the following:

[0277] PEMC allows indication, PEGC allows indication.

[0278] Optionally, the core network capability information indicates the core network's ability to support the PIN service, and the registration response also includes a PIN service support indication.

[0279] In this disclosure, after receiving a registration request from a terminal device forwarded by an access network device, the AMF can send a subscription data acquisition request to the UDM. After acquiring the subscription data associated with the terminal device, the AMF can determine whether to accept the registration request based on at least one of the registration request, the subscription data, the preset policy, and the core network capability information, and send a registration response to the access network device to synchronize the result of the registration request to the terminal device. This registration process can be implemented without the terminal device reporting its role in the PIN, consuming few resources and simplifying the registration process.

[0280] It is understandable that the communication device 1400 can be a UDM network element, a device within a UDM network element, or a device that can be used in conjunction with a UDM network element.

[0281] Communication device 1400 is located on the UDM network element side, wherein:

[0282] The transceiver module 1402 is used to send subscription data associated with the terminal device to the Access and Mobility Management Function (AMF) network element.

[0283] Optionally, the transceiver module 1402 is further configured to receive a subscription data acquisition request sent by the AMF network element, wherein the subscription data acquisition request includes the identifier of the terminal device.

[0284] Optionally, the contract data may include at least one of the following: PEMC permission indication, PEGC permission indication.

[0285] In this embodiment of the disclosure, after receiving the subscription data acquisition request sent by the AMF, the UDM can send the subscription data associated with the terminal device to the AMF, thereby providing auxiliary conditions for the registration process of the terminal device.

[0286] Please see Figure 15 , Figure 15 This is a schematic diagram of another communication device provided in this embodiment. The communication device 1500 can be a terminal device, an access network device, an AMF network element, or a UDM network element. It can also be a chip, chip system, or processor that supports the terminal device in implementing the above methods, or a chip, chip system, or processor that supports the access network device, AMF network element, or UDM network element in implementing the above methods. This device can be used to implement the methods described in the above method embodiments; please refer to the description in the above method embodiments for details.

[0287] The communication device 1500 may include one or more processors 1501. The processor 1501 may be a general-purpose processor or a dedicated processor, such as a baseband processor or a central processing unit (CPU). The baseband processor can be used to process communication protocols and communication data, while the CPU can be used to control the communication device (e.g., base station, baseband chip, terminal equipment, terminal equipment chip, DU or CU, etc.), execute computer programs, and process data from the computer programs.

[0288] Optionally, the communication device 1500 may further include one or more memories 1502, which may store a computer program 1504. The processor 1501 executes the computer program 1503 to cause the communication device 1500 to perform the method described in the above method embodiments. Optionally, the memory 1502 may also store data. The communication device 1500 and the memory 1502 may be provided separately or integrated together.

[0289] Optionally, the communication device 1500 may further include a transceiver 1505 and an antenna 1506. The transceiver 1505 may be referred to as a transceiver unit, transceiver, or transceiver circuit, etc., and is used to implement the transmission and reception functions. The transceiver 1505 may include a receiver and a transmitter. The receiver may be referred to as a receiver or receiving circuit, etc., and is used to implement the receiving function; the transmitter may be referred to as a transmitter or transmitting circuit, etc., and is used to implement the transmitting function.

[0290] Optionally, the communication device 1500 may further include one or more interface circuits 1507. The interface circuits 1507 are used to receive code instructions and transmit them to the processor 1501. The processor 1501 executes the code instructions to cause the communication device 1500 to perform the methods described in the above method embodiments.

[0291] The transceiver 1505 in the communication device 1500 can be used to perform the transmission and reception steps in the above method embodiments.

[0292] In one implementation, the processor 1501 may include a transceiver for implementing receive and transmit functions. For example, the transceiver may be a transceiver circuit, an interface, or an interface circuit. The transceiver circuit, interface, or interface circuit for implementing receive and transmit functions may be separate or integrated. The aforementioned transceiver circuit, interface, or interface circuit can be used for reading and writing code / data, or it can be used for transmitting or relaying signals.

[0293] In one implementation, processor 1501 may store computer program 1503, which runs on processor 1501 and causes communication device 1500 to perform the methods described in the above method embodiments. Computer program 1503 may be embedded in processor 1501; in this case, processor 1501 may be implemented in hardware.

[0294] In one implementation, the communication device 1500 may include circuitry capable of performing the functions of transmitting, receiving, or communicating as described in the foregoing method embodiments. The processor and transceiver described in this disclosure can be implemented on integrated circuits (ICs), analog ICs, radio frequency integrated circuits (RFICs), mixed-signal ICs, application-specific integrated circuits (ASICs), printed circuit boards (PCBs), electronic devices, etc. The processor and transceiver can also be manufactured using various IC process technologies, such as complementary metal-oxide-semiconductor (CMOS), n-metal-oxide-semiconductor (NMOS), positive-channel metal-oxide-semiconductor (PMOS), bipolar junction transistors (BJTs), bipolar CMOS (BiCMOS), silicon-germanium (SiGe), gallium arsenide (GaAs), etc.

[0295] The communication device described in the above embodiments may be an access network device, a terminal device, an AMF network element, or a UDM network element, but the scope of the communication device described in this disclosure is not limited thereto, and the structure of the communication device may vary. Figure 15 The communication device may be a standalone device or part of a larger device. For example, the communication device may be:

[0296] (1) Independent integrated circuit IC, or chip, or chip system or subsystem;

[0297] (2) A collection of one or more ICs, optionally including storage components for storing data and computer programs;

[0298] (3) ASIC, such as modem;

[0299] (4) Modules that can be embedded in other devices;

[0300] (5) Receivers, terminal equipment, smart terminal equipment, cellular phones, wireless equipment, handheld devices, mobile units, vehicle-mounted equipment, access network equipment, core network equipment (such as AMF network elements, UDM network elements), cloud equipment, artificial intelligence equipment, etc.

[0301] (6) Others, etc.

[0302] For cases where the communication device can be a chip or a chip system, please refer to [link / reference]. Figure 16 The diagram shows the structure of the chip. Figure 16 The chip shown includes a processor 1601 and an interface 1602. There can be one or more processors 1601, and multiple interfaces 1602.

[0303] Interface 1602 in the chip is used to perform the transmit and receive steps in the above method embodiments.

[0304] Optionally, the chip also includes a memory 1603 for storing necessary computer programs and data.

[0305] Those skilled in the art will also understand that the various illustrative logical blocks and steps listed in the embodiments of this disclosure can be implemented by electronic hardware, computer software, or a combination of both. Whether such functionality is implemented in hardware or software depends on the specific application and the overall system design requirements. Those skilled in the art can implement the described functionality using various methods for each specific application, but such implementation should not be construed as exceeding the scope of protection of the embodiments of this disclosure.

[0306] This disclosure also provides a readable storage medium having instructions stored thereon that, when executed by a computer, implement the functions of any of the above method embodiments.

[0307] This disclosure also provides a computer program product that, when executed by a computer, implements the functions of any of the above method embodiments.

[0308] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer programs. When the computer program is loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this disclosure are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer program can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program can be transferred from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., high-density digital video discs (DVDs)), or semiconductor media (e.g., solid-state disks (SSDs)).

[0309] Those skilled in the art will understand that the various numerical designations such as "first," "second," etc., used in this disclosure are merely for the convenience of description and are not intended to limit the scope of the embodiments of this disclosure, nor do they indicate the order of events.

[0310] At least one of the features described in this disclosure can also be described as one or more, and multiple features can be two, three, four or more, and this disclosure does not impose any limitations. In the embodiments of this disclosure, for a technical feature, the technical features in that technical feature are distinguished by "first", "second", "third", "A", "B", "C" and "D", etc., and there is no sequential order or size order among the technical features described by "first", "second", "third", "A", "B", "C" and "D".

[0311] The correspondences shown in the tables of this disclosure can be configured or predefined. The values ​​of the information in each table are merely examples and can be configured to other values; this disclosure is not limiting. When configuring the correspondences between information and parameters, it is not necessarily required to configure all the correspondences shown in each table. For example, the correspondences shown in some rows of the tables in this disclosure may not be configured. Furthermore, appropriate modifications and adjustments can be made based on the above tables, such as splitting, merging, etc. The names of the parameters shown in the headers of the above tables can also use other names that the communication device can understand, and the values ​​or representations of the parameters can also be other values ​​or representations that the communication device can understand. In the implementation of the above tables, other data structures can also be used, such as arrays, queues, containers, stacks, linear lists, pointers, linked lists, trees, graphs, structures, classes, heaps, hash tables, or hash tables, etc.

Claims

1. A method for registering a personal Internet of Things (IoT) network PIN element, characterized in that, The method, executed by a terminal device, includes: The terminal device, having not determined its role in the PIN, sends a registration request to the access network device. The registration request includes the terminal device's PIN information, which includes at least one of the following: PIN capability indication information, indicating whether the terminal device supports PIN capability; PIN element management function (PEMC) indication information, indicating whether the terminal device has PEMC capability; and PIN element gateway function (PEGC) indication information, indicating whether the terminal device has PEGC capability. Receive a registration response returned by the access network device, the registration response including at least one of the following: PIN service support indication, PEMC allow indication, PEGC allow indication; Wherein, the PIN service support indication is used to indicate that the network supports the PIN service; the PEMC allow indication is used to indicate that the terminal device's subscription information allows the terminal device to act as the PEMC in the PIN; and the PEGC allow indication is used to indicate that the terminal device's subscription information allows the terminal device to act as the PEGC in the PIN.

2. A method for registering a personal Internet of Things (IoT) network PIN element, characterized in that, Performed by an access network device, the method includes: A first registration request is received from a terminal device, wherein the first registration request includes the PIN information of the terminal device, the terminal device has not determined its role in the PIN, and the PIN information includes at least one of the following: PIN capability indication information, used to indicate whether the terminal device supports PIN capability; PIN element management function PEMC indication information, used to indicate whether the terminal device has PEMC capability; PIN element gateway function PEGC indication information, used to indicate whether the terminal device has PEGC capability. Send a second registration request to the Access and Mobility Management Function (AMF) network element, wherein the second registration request includes the PIN information of the terminal device; Receive the first registration response returned by the AMF network element; Send a second registration response to the terminal device; The first registration response and the second registration response include at least one of the following: PIN service support indication, PEMC permission indication, and PEGC permission indication; Wherein, the PIN service support indication is used to indicate that the network supports the PIN service; the PEMC allow indication is used to indicate that the terminal device's subscription information allows the terminal device to act as the PEMC in the PIN; and the PEGC allow indication is used to indicate that the terminal device's subscription information allows the terminal device to act as the PEGC in the PIN.

3. A method for registering a personal Internet of Things (IoT) network PIN element, characterized in that, The method, performed by the Access and Mobility Management Function (AMF) network element, includes: The system receives a registration request from an access network device and / or receives subscription data associated with a terminal device from a Unified Data Management (UDM) network element. The registration request includes the PIN information of the terminal device, where the terminal device's role in the PIN is not determined. The PIN information includes at least one of the following: PIN capability indication information, indicating whether the terminal device supports PIN capability; PIN element management function (PEMC) indication information, indicating whether the terminal device has PEMC capability; and PIN element gateway function (PEGC) indication information, indicating whether the terminal device has PEGC capability. The decision to accept the registration request is based on at least one of the following: the registration request, the contract data, the preset policy, and the core network capability information. Send a registration response to the access network device, the registration response including at least one of the following: PIN service support indication, PEMC allow indication, PEGC allow indication; Wherein, the PIN service support indication is used to indicate that the network supports the PIN service; the PEMC allow indication is used to indicate that the terminal device's subscription information allows the terminal device to act as the PEMC in the PIN; and the PEGC allow indication is used to indicate that the terminal device's subscription information allows the terminal device to act as the PEGC in the PIN.

4. The method as described in claim 3, characterized in that, Before receiving the subscription data associated with the terminal device sent by the Unified Data Management (UDM) network element, the method further includes: Send a subscription data acquisition request to the UDM network element, wherein the subscription data acquisition request includes the identifier of the terminal device.

5. A method for registering a personal Internet of Things (IoT) network PIN element, characterized in that, The method, executed by the Unified Data Management (UDM) network element, includes: The terminal device sends subscription data associated with the terminal device to the Access and Mobility Management Function (AMF) network element. The terminal device, whose role in the PIN is not determined, sends a registration request to the access network device and receives a registration response from the access network device. The registration request includes the terminal device's PIN information, which includes at least one of the following: PIN capability indication information, indicating whether the terminal device supports PIN capability; PIN Element Management Function (PEMC) indication information, indicating whether the terminal device has PEMC capability; and PIN Element Gateway Function (PEGC) indication information, indicating whether the terminal device has PEGC capability. The registration response includes at least one of the following: PIN service support indication, PEMC permission indication, and PEGC permission indication. The PIN service support indication indicates that the network supports PIN service; the PEMC permission indication indicates that the terminal device's subscription information allows the terminal device to act as a PEMC in the PIN; and the PEGC permission indication indicates that the terminal device's subscription information allows the terminal device to act as a PEGC in the PIN.

6. The method as described in claim 5, characterized in that, Before sending the subscription data associated with the terminal device to the Access and Mobility Management Function (AMF) network element, the method further includes: The system receives a subscription data acquisition request sent by the AMF network element, wherein the subscription data acquisition request includes the identifier of the terminal device.

7. A communication device, characterized in that, include: The transceiver module is used to send a registration request to the access network device. The registration request includes the PIN information of the terminal device, where the terminal device's role in the PIN is not determined. The PIN information includes at least one of the following: PIN capability indication information, indicating whether the terminal device supports PIN capability; PIN element management function (PEMC) indication information, indicating whether the terminal device has PEMC capability; and PIN element gateway function (PEGC) indication information, indicating whether the terminal device has PEGC capability. The transceiver module is also used to receive a registration response returned by the access network device, wherein the registration response includes at least one of the following: PIN service support indication, PEMC allow indication, and PEGC allow indication; Wherein, the PIN service support indication is used to indicate that the network supports the PIN service; the PEMC allow indication is used to indicate that the terminal device's subscription information allows the terminal device to act as the PEMC in the PIN; and the PEGC allow indication is used to indicate that the terminal device's subscription information allows the terminal device to act as the PEGC in the PIN.

8. A communication device, characterized in that, include: A transceiver module is configured to receive a first registration request sent by a terminal device, wherein the first registration request includes the PIN information of the terminal device, the terminal device has not determined its role in the PIN, and the PIN information includes at least one of the following: PIN capability indication information, used to indicate whether the terminal device supports PIN capability; PIN element management function PEMC indication information, used to indicate whether the terminal device has PEMC capability; PIN element gateway function PEGC indication information, used to indicate whether the terminal device has PEGC capability. The transceiver module is further configured to send a second registration request to the Access and Mobility Management Function (AMF) network element, wherein the second registration request includes the PIN information of the terminal device; receive a first registration response returned by the AMF network element; and send a second registration response to the terminal device. The first registration response and the second registration response include at least one of the following: PIN service support indication, PEMC permission indication, and PEGC permission indication; Wherein, the PIN service support indication is used to indicate that the network supports the PIN service; the PEMC allow indication is used to indicate that the terminal device's subscription information allows the terminal device to act as the PEMC in the PIN; and the PEGC allow indication is used to indicate that the terminal device's subscription information allows the terminal device to act as the PEGC in the PIN.

9. A communication device, characterized in that, include: The transceiver module is used to receive registration requests sent by access network devices, and / or receive subscription data associated with terminal devices sent by Unified Data Management (UDM) network elements. The registration request includes the PIN information of the terminal device, where the terminal device's role in the PIN is not determined. The PIN information includes at least one of the following: PIN capability indication information, indicating whether the terminal device supports PIN capability; PIN element management function (PEMC) indication information, indicating whether the terminal device has PEMC capability; and PIN element gateway function (PEGC) indication information, indicating whether the terminal device has PEGC capability. The processing module is configured to determine whether to accept the registration request based on at least one of the following: the registration request, the contract data, the preset policy, and the core network capability information; The transceiver module is further configured to send a registration response to the access network device, wherein the registration response includes at least one of the following: PIN service support indication, PEMC allow indication, and PEGC allow indication; Wherein, the PIN service support indication is used to indicate that the network supports the PIN service; the PEMC allow indication is used to indicate that the terminal device's subscription information allows the terminal device to act as the PEMC in the PIN; and the PEGC allow indication is used to indicate that the terminal device's subscription information allows the terminal device to act as the PEGC in the PIN.

10. A communication device, characterized in that, include: The transceiver module is used to send subscription data associated with the terminal device to the Access and Mobility Management Function (AMF) network element. The terminal device, whose role in the PIN is not yet determined, sends a registration request to the access network device and receives a registration response from the access network device. The registration request includes the terminal device's PIN information, which includes at least one of the following: PIN capability indication information, indicating whether the terminal device supports PIN capability; PIN Element Management Function (PEMC) indication information, indicating whether the terminal device has PEMC capability; and PIN Element Gateway Function (PEGC) indication information, indicating whether the terminal device has PEGC capability. The registration response includes at least one of the following: PIN service support indication, PEMC permission indication, and PEGC permission indication. The PIN service support indication indicates that the network supports PIN service; the PEMC permission indication indicates that the terminal device's subscription information allows the terminal device to act as a PEMC in the PIN; and the PEGC permission indication indicates that the terminal device's subscription information allows the terminal device to act as a PEGC in the PIN.

11. A communication device, characterized in that, The device includes a processor and a memory, the memory storing a computer program, the processor executing the computer program stored in the memory to cause the device to perform the method as claimed in claim 1, or the method as claimed in claim 2, or the method as claimed in any one of claims 3-4, or the method as claimed in any one of claims 5-6.

12. A communication system, characterized in that, The communication system includes terminal equipment, access network equipment, AMF network elements, and UDM network elements; Wherein, the terminal device is used to perform the method as described in claim 1, the access network device is used to perform the method as described in claim 2, the AMF network element is used to perform the method as described in any one of claims 3-4, and the UDM network element is used to perform the method as described in any one of claims 5 to 6.

13. A computer-readable storage medium for storing instructions that, when executed, cause the method of claim 1 to be implemented, or the method of claim 2 to be implemented, or the method of any one of claims 3-4 to be implemented, or the method of any one of claims 5-6 to be implemented.

Images