WO2023184172A1 - 创建pin的方法、装置、通信设备及存储介质 - Google Patents

创建pin的方法、装置、通信设备及存储介质 Download PDF

Info

Publication number
WO2023184172A1
WO2023184172A1 PCT/CN2022/083806 CN2022083806W WO2023184172A1 WO 2023184172 A1 WO2023184172 A1 WO 2023184172A1 CN 2022083806 W CN2022083806 W CN 2022083806W WO 2023184172 A1 WO2023184172 A1 WO 2023184172A1
Authority
WO
WIPO (PCT)
Prior art keywords
pin
information
request information
terminal
request
Prior art date
Application number
PCT/CN2022/083806
Other languages
English (en)
French (fr)
Inventor
刘建宁
Original Assignee
北京小米移动软件有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 北京小米移动软件有限公司 filed Critical 北京小米移动软件有限公司
Priority to CN202280001012.9A priority Critical patent/CN117158108A/zh
Priority to PCT/CN2022/083806 priority patent/WO2023184172A1/zh
Publication of WO2023184172A1 publication Critical patent/WO2023184172A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup

Definitions

  • the present disclosure relates to the field of wireless communication technology but is not limited to the field of wireless communication technology, and in particular, to a method, device, communication device and storage medium for creating a PIN.
  • a Personal IoT Network consists of PIN elements that communicate using PIN direct connections or direct network connections and is managed locally (using PIN elements with management capabilities). Examples of PINs include wearable device networks, smart home and/or smart office devices. Through a PIN element with gateway capabilities, the PIN element can access network services and can communicate with PIN elements that are not in scope to connect directly using the PIN.
  • a PIN includes at least one PIN element with gateway capabilities and at least one PIN element with management capabilities. In the related technology, no solution is provided on how to create a PIN.
  • the embodiments of the present disclosure disclose a method, device, communication device and storage medium for creating a PIN.
  • a method for creating a personal IoT network PIN is provided, wherein the method is executed by a core network element, and the method includes:
  • the request information is used to request creation of the PIN.
  • the request information includes at least one of the following information:
  • the attribute information includes at least one of the following:
  • the information of the PIN element includes at least one of the following:
  • the request information sent by the receiving application function AF includes:
  • the request information sent by the AF is received through the network opening function NEF.
  • the method further includes:
  • creating the PIN includes:
  • Update the subscription data of the terminal where the updated subscription data includes data of PIN information contained in the request information and/or data of PIN parameters generated by the core network element.
  • the method further includes:
  • PIN information includes: PIN information contained in the request information and information on PIN parameters generated by the core network element.
  • sending PIN information to the terminal includes:
  • the PIN information is sent to the terminal through a user parameter update UPU process or a terminal configuration update UCU process.
  • the PIN information includes that the terminal may be configured as a personal IoT network element PINE, a personal IoT network element PEMC with management functions, and/or a personal IoT network element PEGC with gateway management functions.
  • the method further includes:
  • the method further includes:
  • sending a response message for creating the PIN to the AF includes:
  • sending a response message for creating the PIN to the AF includes:
  • a response message to create the PIN is sent to the AF through NEF.
  • a method of creating a personal IoT network PIN is provided, wherein the method is executed by AF, and the method includes:
  • the request information is used to request creation of the PIN.
  • the request information includes at least one of the following information:
  • the attribute information includes at least one of the following:
  • the information of the PIN element includes at least one of the following:
  • sending request information to core network elements includes:
  • the method further includes:
  • a response message for creating the PIN is received, wherein the response message is at least one of a response message for accepting the requested information and a response message for rejecting the requested information.
  • the receiving a response message for creating the PIN includes:
  • a response message to create the PIN is received via NEF.
  • a method of creating a personal Internet of Things network PIN is provided, wherein the method is executed by a terminal, and the method includes:
  • Receive PIN information sent by a core network element where the PIN information includes: PIN information contained in the request information and/or information on PIN parameters generated by the core network element.
  • receiving the PIN information sent by the core network element includes:
  • the PIN information includes that the terminal may be configured as a personal IoT network element PINE, a personal IoT network element PEMC with management functions, and/or a personal IoT network element PEGC with gateway management functions.
  • the method further includes:
  • Feedback information is sent to the core network element, where the feedback information is used to indicate that the PIN information has been received or that the PIN information has not been received.
  • a device for creating a personal Internet of Things network PIN includes:
  • a receiving module configured to receive request information sent by the application function AF
  • the request information is used to request creation of the PIN.
  • a device for creating a personal Internet of Things network PIN includes:
  • the sending module is configured to send request information to the core network element
  • the request information is used to request creation of the PIN.
  • a device for creating a personal Internet of Things network PIN includes:
  • the receiving module is configured to receive PIN information sent by the core network element, where the PIN information includes: PIN information contained in the request information and information on PIN parameters generated by the core network element.
  • a communication device includes:
  • memory for storing instructions executable by the processor
  • the processor is configured to implement the method described in any embodiment of the present disclosure when running the executable instructions.
  • a computer storage medium stores a computer executable program.
  • the executable program is executed by a processor, the method described in any embodiment of the present disclosure is implemented.
  • request information sent by the application function AF is received; wherein the request information is used to request creation of the PIN.
  • the core network element receives the request information sent by the application function AF, it can create the PIN based on the request information. Compared with the situation where the PIN cannot be created according to the request, it can be adapted to create the PIN. According to the needs, the PIN can be flexibly created to provide users with services to meet the application needs in various scenarios.
  • Figure 1 is a schematic structural diagram of a wireless communication system according to an exemplary embodiment.
  • FIG. 2 is a schematic flowchart of a method for creating a personal IoT network PIN according to an exemplary embodiment.
  • Figure 3 is a schematic flowchart of a method for creating a personal IoT network PIN according to an exemplary embodiment.
  • Figure 4 is a schematic flowchart of a method for creating a personal IoT network PIN according to an exemplary embodiment.
  • Figure 5 is a schematic flowchart of a method for creating a personal IoT network PIN according to an exemplary embodiment.
  • Figure 6 is a schematic flowchart of a method for creating a personal IoT network PIN according to an exemplary embodiment.
  • FIG. 7 is a schematic flowchart of a method for creating a personal IoT network PIN according to an exemplary embodiment.
  • FIG. 8 is a schematic flowchart of a method for creating a personal IoT network PIN according to an exemplary embodiment.
  • FIG. 9 is a schematic flowchart of a method for creating a personal IoT network PIN according to an exemplary embodiment.
  • FIG. 10 is a schematic flowchart of a method for creating a personal IoT network PIN according to an exemplary embodiment.
  • Figure 11 is a schematic flowchart of a method for creating a personal IoT network PIN according to an exemplary embodiment.
  • Figure 12 is a schematic flowchart of a method for creating a personal IoT network PIN according to an exemplary embodiment.
  • Figure 13 is a schematic flowchart of a method for creating a personal IoT network PIN according to an exemplary embodiment.
  • Figure 14 is a schematic flowchart of a method for creating a personal IoT network PIN according to an exemplary embodiment.
  • Figure 15 is a schematic diagram of a device for creating a personal IoT network PIN according to an exemplary embodiment.
  • Figure 16 is a schematic diagram of a device for creating a personal IoT network PIN according to an exemplary embodiment.
  • Figure 17 is a schematic diagram of a device for creating a personal IoT network PIN according to an exemplary embodiment.
  • Figure 18 is a schematic structural diagram of a terminal according to an exemplary embodiment.
  • Figure 19 is a block diagram of a base station according to an exemplary embodiment.
  • first, second, third, etc. may be used to describe various information in the embodiments of the present disclosure, the information should not be limited to these terms. These terms are only used to distinguish information of the same type from each other.
  • first information may also be called second information, and similarly, the second information may also be called first information.
  • word “if” as used herein may be interpreted as "when” or "when” or "in response to determining.”
  • this article uses the terms “greater than” or “less than” when characterizing the size relationship. However, those skilled in the art can understand that the term “greater than” also encompasses the meaning of “greater than or equal to”, and “less than” also encompasses the meaning of “less than or equal to”.
  • FIG. 1 shows a schematic structural diagram of a wireless communication system provided by an embodiment of the present disclosure.
  • the wireless communication system is a communication system based on mobile communication technology.
  • the wireless communication system may include several user equipments 110 and several base stations 120.
  • user equipment 110 may be a device that provides voice and/or data connectivity to a user.
  • the user equipment 110 may communicate with one or more core networks via a Radio Access Network (RAN).
  • RAN Radio Access Network
  • the user equipment 110 may be an Internet of Things user equipment, such as a sensor device, a mobile phone, and a computer with an Internet of Things user equipment. , for example, it can be a fixed, portable, pocket-sized, handheld, computer-built-in or vehicle-mounted device.
  • the user equipment 110 may also be equipment of an unmanned aerial vehicle.
  • the user equipment 110 may also be a vehicle-mounted device, for example, it may be an on-board computer with a wireless communication function, or a wireless user equipment connected to an external on-board computer.
  • the user equipment 110 may also be a roadside device, for example, it may be a streetlight, a signal light or other roadside device with a wireless communication function.
  • the base station 120 may be a network-side device in a wireless communication system.
  • the wireless communication system can be the 4th generation mobile communication technology (the 4th generation mobile communication, 4G) system, also known as the Long Term Evolution (LTE) system; or the wireless communication system can also be a 5G system, Also called new air interface system or 5G NR system.
  • the wireless communication system may also be a next-generation system of the 5G system.
  • the access network in the 5G system can be called NG-RAN (New Generation-Radio Access Network).
  • the base station 120 may be an evolved base station (eNB) used in the 4G system.
  • the base station 120 may also be a base station (gNB) that adopts a centralized distributed architecture in the 5G system.
  • eNB evolved base station
  • gNB base station
  • the base station 120 adopts a centralized distributed architecture it usually includes a centralized unit (central unit, CU) and at least two distributed units (distributed unit, DU).
  • the centralized unit is equipped with a protocol stack including the Packet Data Convergence Protocol (PDCP) layer, the Radio Link Control protocol (Radio Link Control, RLC) layer, and the Media Access Control (Media Access Control, MAC) layer; distributed
  • PDCP Packet Data Convergence Protocol
  • RLC Radio Link Control
  • MAC Media Access Control
  • the unit is provided with a physical (Physical, PHY) layer protocol stack, and the embodiment of the present disclosure does not limit the specific implementation of the base station 120.
  • a wireless connection may be established between the base station 120 and the user equipment 110 through a wireless air interface.
  • the wireless air interface is a wireless air interface based on the fourth generation mobile communication network technology (4G) standard; or the wireless air interface is a wireless air interface based on the fifth generation mobile communication network technology (5G) standard, such as
  • the wireless air interface is a new air interface; alternatively, the wireless air interface may also be a wireless air interface based on the next generation mobile communication network technology standard of 5G.
  • an E2E (End to End, end-to-end) connection can also be established between user equipments 110 .
  • V2V vehicle to vehicle, vehicle to vehicle
  • V2I vehicle to infrastructure, vehicle to roadside equipment
  • V2P vehicle to pedestrian, vehicle to person
  • the above user equipment can be considered as the terminal equipment of the following embodiments.
  • the above-mentioned wireless communication system may also include a network management device 130.
  • the network management device 130 may be a core network device in a wireless communication system.
  • the network management device 130 may be a mobility management entity (Mobility Management Entity) in an evolved packet core network (Evolved Packet Core, EPC). MME).
  • the network management device can also be other core network devices, such as serving gateway (Serving GateWay, SGW), public data network gateway (Public Data Network GateWay, PGW), policy and charging rules functional unit (Policy and Charging Rules) Function, PCRF) or Home Subscriber Server (HSS), etc.
  • serving gateway Serving GateWay, SGW
  • public data network gateway Public Data Network GateWay, PGW
  • Policy and Charging Rules Policy and Charging Rules
  • PCRF Policy and Charging Rules
  • HSS Home Subscriber Server
  • the embodiments of the present disclosure enumerate multiple implementations to clearly describe the technical solutions of the embodiments of the present disclosure.
  • the multiple embodiments provided in the embodiments of the present disclosure can be executed alone or in combination with the methods of other embodiments in the embodiments of the present disclosure. They can also be executed alone or in combination. It is then executed together with some methods in other related technologies; the embodiments of the present disclosure do not limit this.
  • PIN elements and management of PINs include management of different types of PIN elements and configuration of PINs.
  • PIN elements with management capabilities PEMC, PIN Element with Management Capability
  • PEMC can add a PIN Element with Gateway Capability (PEGC, PIN Element with Gateway Capability) to the PIN, or remove the PEGC from the PIN, as well as add the PIN element to the PIN and associate the PIN element to the PIN that has been added to the PIN. some PEGC in, or remove the PIN element from the PIN.
  • time validity for example, a PIN is valid for 30 minutes, a PIN is valid from 15:00 to 23:00
  • PIN elements in the PIN for example, a personal IoT network member ( PINE, PIN Element) will be a PIN member for 1 hour, PIN Element will be a PIN member from 16:00 to 17:00).
  • the PIN element can also be understood as the PIN member of the PIN network.
  • this embodiment provides a method for creating a personal IoT network PIN, where the method is executed by a core network element and includes:
  • Step 21 Receive the request information sent by the application function AF;
  • the request information is used to request the creation of a PIN.
  • the terminals involved in this disclosure may be, but are not limited to, mobile phones, wearable devices, vehicle-mounted terminals, roadside units (RSU, Road Side Unit), smart home terminals, industrial sensing equipment and/or medical equipment, etc.
  • the terminal may be a Redcap terminal or a predetermined version of a new air interface NR terminal (for example, an R17 NR terminal).
  • the base station involved in the present disclosure may be various types of base stations, such as base stations of the third generation mobile communication (3G) network, base stations of the fourth generation mobile communication (4G) network, and base stations of the fifth generation mobile communication (5G) network. base station or other evolved base station.
  • base stations of the third generation mobile communication (3G) network such as base stations of the third generation mobile communication (3G) network, base stations of the fourth generation mobile communication (4G) network, and base stations of the fifth generation mobile communication (5G) network.
  • base station or other evolved base station.
  • the network elements involved in this disclosure can be Access Control And Mobility Management Function (AMF), Network Exposure Function (NEF), Unified Data Management (UDM), etc. .
  • AMF Access Control And Mobility Management Function
  • NEF Network Exposure Function
  • UDM Unified Data Management
  • the network element is not limited to the above examples, and can also be any network element that has a creation PIN.
  • the network element capable of creating a PIN can be deployed as a communication node alone, or can be deployed uniformly in an existing network element.
  • a network element capable of creating a PIN can be understood as a logical node that can be flexibly deployed in a network, and is not limited here.
  • the core network element may be a UDM.
  • the authorized predetermined terminal of the application function AF triggers the creation of a PIN; the AF sends request information to the UDM, where the request information is used to request the creation of a PIN; the UDM receives the request information sent by the AF; determines that the request information is received, and the UDM Create a PIN.
  • the application function AF is authorized by a predetermined terminal to trigger the creation of a PIN; the AF sends request information to the UDM through the NEF, where the request information is used to request the creation of a PIN; the UDM receives the request information sent by the AF; and determines that the request information is received , UDM creates PIN.
  • AF can be authorized in advance to create a PIN network.
  • user A needs to create a PIN on the N floor of the school.
  • User A can use the mobile phone (predetermined terminal) authorized by AF to send instruction information to AF.
  • the instruction information can include the name of the network to be created and the services provided by the network. , service length and PIN member information. It should be noted that the instruction information is not limited to the above information.
  • the AF sends request information to the UDM, where the request information is used to request the creation of a PIN, and the request information may include the information contained in the instruction information.
  • UDM receives the request information sent by AF. Confirming that the request information has been received, UDM creates a PIN.
  • the request information includes at least one of the following PIN information:
  • the terminal identification includes a universal external identification. It should be noted that after UDM successfully creates a PIN, PIN information will be sent to the terminal indicated by the terminal identifier.
  • the attribute information of the PIN to be created includes at least one of the following: PIN name (information readable by the user), PIN service (services provided by PINE, such as printers, lights, cameras, etc.) and PIN validity time (Used to define how long the PIN can work, e.g. 30 minutes).
  • the information of the PIN element included in the PIN to be created includes at least one of the following: PIN element identification (unique ID within the PIN assigned by PEMC), PIN element type (indicating whether it is PEMC, PEGC, or ordinary PINE), service information (what services the PIN element can provide, such as a printer, light, or camera, etc.) and PIN element name (human-readable information, such as a printer for the bedroom or a light for the living room).
  • PIN element identification unique ID within the PIN assigned by PEMC
  • PIN element type indicating whether it is PEMC, PEGC, or ordinary PINE
  • service information what services the PIN element can provide, such as a printer, light, or camera, etc.
  • PIN element name human-readable information, such as a printer for the bedroom or a light for the living room.
  • the authorized predetermined terminal of the application function AF triggers the creation of a PIN; the AF sends request information to the UDM, where the request information is used to request the creation of a PIN; the UDM receives the request information sent by the AF; determines that the request information is received, and the UDM Create a PIN. After determining that the PIN is successfully created, UDM will send PIN information to the target terminal.
  • the PIN information includes: the PIN information contained in the request information and the PIN parameter information generated by UDM.
  • the target terminal may be a terminal that is determined by the AF in advance and can serve as a PEMC.
  • the AF may determine the identity ID of the target terminal in advance.
  • the authorized predetermined terminal of the application function AF triggers the creation of a PIN; the AF sends request information to the UDM, where the request information is used to request the creation of a PIN; the UDM receives the request information sent by the AF; determines that the request information is received, and the UDM Creating a PIN; creating a PIN includes: updating the subscription data of the terminal, where the updated subscription data includes the data of the PIN information contained in the request information and/or the data of the PIN parameters generated by the core network element. After determining that the PIN is successfully created, UDM will send PIN information to the target terminal.
  • the PIN information includes: the PIN information contained in the request information and the PIN parameter information generated by UDM.
  • the target terminal may be a terminal that is determined by the AF in advance and can serve as a PEMC.
  • the AF may determine the identity ID of the target terminal in advance.
  • the authorized predetermined terminal of the application function AF triggers the creation of a PIN; the AF sends request information to the UDM, where the request information is used to request the creation of a PIN; the UDM receives the request information sent by the AF; determines that the request information is received, and the UDM Create a PIN.
  • UDM After determining that the PIN is successfully created, UDM will send PIN information to the target terminal through the user update process (UPU, User Parameter Update) or terminal configuration update (UCU, UE Configuration Update) process.
  • the PIN information includes: the PIN information contained in the request information and Information about PIN parameters generated by UDM.
  • the target terminal may be a terminal that is determined by the AF in advance and can serve as a PEMC.
  • the AF may determine the identity ID of the target terminal in advance.
  • the application function AF is authorized by a predetermined terminal to trigger the creation of a PIN; the AF sends request information to the UDM through the NEF, where the request information is used to request the creation of a PIN; the UDM receives the request information sent by the AF; and determines that the request information is received , UDM creates PIN. It is determined that the PIN is successfully created and a response message for creating the PIN is sent to AF.
  • the application function AF is authorized by a predetermined terminal to trigger the creation of a PIN; the AF sends request information to the UDM through the NEF, where the request information is used to request the creation of a PIN; the UDM receives the request information sent by the AF; and determines that the request information is received , UDM creates PIN. After determining that the PIN is successfully created, the PIN information is sent to the terminal, where the PIN information includes: the PIN information contained in the request information and the PIN parameter information generated by the core network element. Receive feedback messages sent by the terminal. It is determined that the received feedback message indicates that the PIN has been received, and a response message for creating the PIN is sent to the AF.
  • the request information sent by the application function AF is received; wherein the request information is used to request the creation of a PIN.
  • the core network element receives the request information sent by the application function AF, it can create a PIN based on the request information. Compared with the situation where the PIN cannot be created according to the request, it can adapt to the needs of creating a PIN and create a PIN flexibly. Provide services to users to meet application needs in various scenarios.
  • this embodiment provides a method for creating a personal IoT network PIN, where the method is executed by a core network element and includes:
  • Step 31 Receive the request information sent by the AF through the network opening function NEF.
  • the application function AF is authorized by a predetermined terminal to trigger the creation of a PIN; the AF sends request information to the UDM through the NEF, where the request information is used to request the creation of a PIN; the UDM receives the request information sent by the AF; and determines that the request information is received , UDM creates PIN. After determining that the PIN is successfully created, UDM will send PIN information to the target terminal.
  • the PIN information includes: the PIN information contained in the request information and the PIN parameter information generated by UDM.
  • the UDM also sends a response message to the AF for the requested information. For example, it is determined that the PIN is successfully created, and a response message accepting the request information is sent to the AF; or, it is determined that the PIN is not successfully created, and a response message rejecting the request information is sent to the AF.
  • this embodiment provides a method for creating a personal IoT network PIN, where the method is executed by a core network element and includes:
  • Step 41 Confirm that the request information is received and create a PIN.
  • the authorized predetermined terminal of the application function AF triggers the creation of a PIN; the AF sends request information to the UDM, where the request information is used to request the creation of a PIN; the UDM receives the request information sent by the AF; determines that the request information is received, and the UDM Creating a PIN; creating a PIN includes: updating the subscription data of the terminal, where the updated subscription data includes the data of the PIN information contained in the request information and/or the data of the PIN parameters generated by the core network element. After determining that the PIN is successfully created, UDM will send PIN information to the target terminal.
  • the PIN information includes: the PIN information contained in the request information and the PIN parameter information generated by UDM.
  • the target terminal may be a terminal that is determined by the AF in advance and can serve as a PEMC.
  • the AF may determine the identity ID of the target terminal in advance.
  • this embodiment provides a method for creating a personal IoT network PIN, where the method is executed by a core network element and includes:
  • Step 51 Update the subscription data of the terminal, where the updated subscription data includes the data of the PIN information contained in the request information and/or the data of the PIN parameters generated by the core network element.
  • the PIN parameter data generated by the network element may be the network parameters of the created PIN, such as delay and service quality.
  • step 51 please refer to step 41 for details, and will not be repeated here.
  • this embodiment provides a method for creating a personal IoT network PIN, where the method is executed by a core network element and includes:
  • Step 61 Confirm that the PIN is successfully created, and send the PIN information to the terminal, where the PIN information includes: the PIN information included in the request information and the PIN parameter information generated by the core network element.
  • PIN information is sent to the terminal, where the PIN information includes: PIN information contained in the request information and information on PIN parameters generated by the core network element.
  • Receive feedback information sent by the terminal It is determined that the feedback message received indicates that the PIN is received, and a response message accepting the request information is sent to the AF; or, it is determined that the feedback message is not received, indicating that the PIN is not received, and a response message rejecting the request information is sent to the AF.
  • this embodiment provides a method for creating a personal IoT network PIN, where the method is executed by a core network element and includes:
  • Step 71 Send PIN information to the terminal, where the PIN information includes that the terminal can be configured as a personal IoT network element PINE, a personal IoT network element PEMC with management functions, and/or a personal IoT network element PEGC with gateway management functions. .
  • the terminal After the terminal receives the PIN information, it can be determined that the terminal is configured as a personal IoT network element PINE, a personal IoT network element PEMC with management functions, and/or a personal IoT network element PEGC with gateway management functions.
  • the terminal You can perform the corresponding function.
  • this embodiment provides a method for creating a personal IoT network PIN, where the method is executed by a core network element and includes:
  • Step 81 Send a PIN creation response message to AF.
  • the application function AF is authorized by a predetermined terminal to trigger the creation of a PIN; the AF sends request information to the UDM through the NEF, where the request information is used to request the creation of a PIN; the UDM receives the request information sent by the AF; and determines that the request information is received , UDM creates PIN. After determining that the PIN is successfully created, UDM will send PIN information to the target terminal.
  • the PIN information includes: the PIN information contained in the request information and the PIN parameter information generated by UDM.
  • the UDM also sends a response message to the AF via NEF for the requested information.
  • the PIN is successfully created, and a response message accepting the request information is sent to the AF; or, it is determined that the PIN is not successfully created, and a response message rejecting the request information is sent to the AF; or it is determined that the received feedback message indicates that the PIN is received, Send a response message accepting the request information to the AF; or, determine that no feedback information has been received indicating that the PIN has not been received, and send a response message rejecting the request information to the AF.
  • this embodiment provides a method for creating a personal IoT network PIN, where the method is executed by AF and includes:
  • Step 91 Send the request information to the core network element
  • the request information is used to request creation of the PIN.
  • the terminals involved in this disclosure may be, but are not limited to, mobile phones, wearable devices, vehicle-mounted terminals, roadside units (RSU, Road Side Unit), smart home terminals, industrial sensing equipment and/or medical equipment, etc.
  • the terminal may be a Redcap terminal or a predetermined version of a new air interface NR terminal (for example, an R17 NR terminal).
  • the base station involved in the present disclosure may be various types of base stations, such as base stations of the third generation mobile communication (3G) network, base stations of the fourth generation mobile communication (4G) network, and base stations of the fifth generation mobile communication (5G) network. base station or other evolved base station.
  • base stations of the third generation mobile communication (3G) network such as base stations of the third generation mobile communication (3G) network, base stations of the fourth generation mobile communication (4G) network, and base stations of the fifth generation mobile communication (5G) network.
  • base station or other evolved base station.
  • the network elements involved in this disclosure can be Access Control And Mobility Management Function (AMF), Network Exposure Function (NEF), Unified Data Management (UDM), etc. .
  • AMF Access Control And Mobility Management Function
  • NEF Network Exposure Function
  • UDM Unified Data Management
  • the network element is not limited to the above examples, and can also be any network element that has a creation PIN.
  • the network element capable of creating a PIN can be deployed as a communication node alone, or can be deployed uniformly in an existing network element.
  • a network element capable of creating a PIN can be understood as a logical node that can be flexibly deployed in a network, and is not limited here.
  • the core network element may be a UDM.
  • the authorized predetermined terminal of the application function AF triggers the creation of a PIN; the AF sends request information to the UDM, where the request information is used to request the creation of a PIN; the UDM receives the request information sent by the AF; determines that the request information is received, and the UDM Create a PIN.
  • the application function AF is authorized by a predetermined terminal to trigger the creation of a PIN; the AF sends request information to the UDM through the NEF, where the request information is used to request the creation of a PIN; the UDM receives the request information sent by the AF; and determines that the request information is received , UDM creates PIN.
  • AF can be authorized in advance to create a PIN network.
  • user A needs to create a PIN on the N floor of the school.
  • User A can use the mobile phone (predetermined terminal) authorized by AF to send instruction information to AF.
  • the instruction information can include the name of the network to be created and the services provided by the network. , service length and PIN member information. It should be noted that the instruction information is not limited to the above information.
  • the AF sends request information to the UDM, where the request information is used to request the creation of a PIN, and the request information may include the information contained in the instruction information.
  • UDM receives the request information sent by AF. Confirming that the request information has been received, UDM creates a PIN.
  • the request information includes at least one of the following PIN information:
  • the terminal identification includes a universal external identification. It should be noted that after UDM successfully creates a PIN, PIN information will be sent to the terminal indicated by the terminal identifier.
  • the attribute information of the PIN to be created includes at least one of the following: PIN name (information readable by the user), PIN service (services provided by PINE, such as printers, lights, cameras, etc.) and PIN validity Time (used to define how long the PIN can work, e.g. 30 minutes).
  • the information of the PIN element included in the PIN to be created includes at least one of the following: PIN element identification (unique ID within the PIN assigned by PEMC), PIN element type (indicating whether it is PEMC, PEGC, or ordinary PINE), service information (what services the PIN element can provide, such as a printer, light, or camera, etc.) and PIN element name (human-readable information, such as a printer for the bedroom or a light for the living room).
  • PIN element identification unique ID within the PIN assigned by PEMC
  • PIN element type indicating whether it is PEMC, PEGC, or ordinary PINE
  • service information what services the PIN element can provide, such as a printer, light, or camera, etc.
  • PIN element name human-readable information, such as a printer for the bedroom or a light for the living room.
  • the authorized predetermined terminal of the application function AF triggers the creation of a PIN; the AF sends request information to the UDM, where the request information is used to request the creation of a PIN; the UDM receives the request information sent by the AF; determines that the request information is received, and the UDM Create a PIN. After determining that the PIN is successfully created, UDM will send PIN information to the target terminal.
  • the PIN information includes: the PIN information contained in the request information and the PIN parameter information generated by UDM.
  • the target terminal may be a terminal that is determined by the AF in advance and can serve as a PEMC.
  • the AF may determine the identity ID of the target terminal in advance.
  • the authorized predetermined terminal of the application function AF triggers the creation of a PIN; the AF sends request information to the UDM, where the request information is used to request the creation of a PIN; the UDM receives the request information sent by the AF; determines that the request information is received, and the UDM Creating a PIN; creating a PIN includes: updating the subscription data of the terminal, where the updated subscription data includes the data of the PIN information contained in the request information and/or the data of the PIN parameters generated by the core network element. After determining that the PIN is successfully created, UDM will send PIN information to the target terminal.
  • the PIN information includes: the PIN information contained in the request information and the PIN parameter information generated by UDM.
  • the target terminal may be a terminal that is determined by the AF in advance and can serve as a PEMC.
  • the AF may determine the identity ID of the target terminal in advance.
  • the authorized predetermined terminal of the application function AF triggers the creation of a PIN; the AF sends request information to the UDM, where the request information is used to request the creation of a PIN; the UDM receives the request information sent by the AF; determines that the request information is received, and the UDM Create a PIN.
  • UDM After determining that the PIN is successfully created, UDM will send PIN information to the target terminal through the user update process (UPU, User Parameter Update) or terminal configuration update (UCU, UE Configuration Update) process.
  • the PIN information includes: the PIN information contained in the request information and Information about PIN parameters generated by UDM.
  • the target terminal may be a terminal that is determined by the AF in advance and can serve as a PEMC.
  • the AF may determine the identity ID of the target terminal in advance.
  • the application function AF is authorized by a predetermined terminal to trigger the creation of a PIN; the AF sends request information to the UDM through the NEF, where the request information is used to request the creation of a PIN; the UDM receives the request information sent by the AF; and determines that the request information is received , UDM creates PIN. It is determined that the PIN is successfully created and a response message for creating the PIN is sent to AF.
  • the application function AF is authorized by a predetermined terminal to trigger the creation of a PIN; the AF sends request information to the UDM through the NEF, where the request information is used to request the creation of a PIN; the UDM receives the request information sent by the AF; and determines that the request information is received , UDM creates PIN. After determining that the PIN is successfully created, the PIN information is sent to the terminal, where the PIN information includes: the PIN information contained in the request information and the PIN parameter information generated by the core network element. Receive feedback messages sent by the terminal. It is determined that the received feedback message indicates that the PIN has been received, and a response message for creating the PIN is sent to the AF.
  • this embodiment provides a method for creating a personal IoT network PIN, where the method is executed by AF and includes:
  • Step 101 Send request information to the core network element through the network opening function NEF.
  • the application function AF is authorized by a predetermined terminal to trigger the creation of a PIN; the AF sends request information to the UDM through the NEF, where the request information is used to request the creation of a PIN; the UDM receives the request information sent by the AF; and determines that the request information is received , UDM creates PIN.
  • this embodiment provides a method for creating a personal IoT network PIN, where the method is executed by AF and includes:
  • Step 111 Receive a response message for creating a PIN, where the response message is at least one of a response message for accepting the request information and a response message for rejecting the request information.
  • the create PIN response message is received via NEF.
  • the application function AF is authorized by a predetermined terminal to trigger the creation of a PIN; the AF sends request information to the UDM through the NEF, where the request information is used to request the creation of a PIN; the UDM receives the request information sent by the AF; and determines that the request information is received , UDM creates PIN. After determining that the PIN is successfully created, UDM will send PIN information to the target terminal.
  • the PIN information includes: the PIN information contained in the request information and the PIN parameter information generated by UDM.
  • the UDM also sends a response message to the AF via NEF for the requested information.
  • the PIN is successfully created, and a response message accepting the request information is sent to the AF; or, it is determined that the PIN is not successfully created, and a response message rejecting the request information is sent to the AF; or it is determined that the received feedback message indicates that the PIN is received, Send a response message accepting the request information to the AF; or, determine that no feedback information has been received indicating that the PIN has not been received, and send a response message rejecting the request information to the AF.
  • this embodiment provides a method for creating a personal IoT network PIN, where the method is executed by a terminal and includes:
  • Step 121 Receive PIN information sent by the core network element, where the PIN information includes: PIN information contained in the request information and/or PIN parameter information generated by the core network element.
  • the request information includes at least one of the following PIN information:
  • the terminal identification includes a universal external identification. It should be noted that after UDM successfully creates a PIN, PIN information will be sent to the terminal indicated by the terminal identifier.
  • the attribute information of the PIN to be created includes at least one of the following: PIN name (information readable by the user), PIN service (services provided by PINE, such as printers, lights, cameras, etc.) and PIN validity Time (used to define how long the PIN can work, e.g. 30 minutes).
  • the information of the PIN element included in the PIN to be created includes at least one of the following: PIN element identification (unique ID within the PIN assigned by PEMC), PIN element type (indicating whether it is PEMC, PEGC, or ordinary PINE), service information (what services the PIN element can provide, such as a printer, light, or camera, etc.) and PIN element name (human-readable information, such as a printer for the bedroom or a light for the living room).
  • PIN element identification unique ID within the PIN assigned by PEMC
  • PIN element type indicating whether it is PEMC, PEGC, or ordinary PINE
  • service information what services the PIN element can provide, such as a printer, light, or camera, etc.
  • PIN element name human-readable information, such as a printer for the bedroom or a light for the living room.
  • the authorized predetermined terminal of the application function AF triggers the creation of a PIN; the AF sends request information to the UDM, where the request information is used to request the creation of a PIN; the UDM receives the request information sent by the AF; determines that the request information is received, and the UDM Creating a PIN; creating a PIN includes: updating the subscription data of the terminal, where the updated subscription data includes the data of the PIN information contained in the request information and/or the data of the PIN parameters generated by the core network element. After determining that the PIN is successfully created, UDM will send PIN information to the terminal.
  • the PIN information includes: the PIN information contained in the request information and the PIN parameter information generated by UDM.
  • the terminal receives the PIN information.
  • the terminal may be a terminal that has been determined by the AF in advance and can act as a PEMC.
  • the AF may determine the identity ID of the terminal in advance.
  • the PIN information includes that the terminal may be configured as a personal IoT network element PINE, a personal IoT network element PEMC with management functions, and/or a personal IoT network element PEGC with gateway management functions.
  • the terminal After the terminal receives the PIN information, it can be determined that the terminal is configured as a personal IoT network element PINE, a personal IoT network element PEMC with management functions, and/or a personal IoT network element PEGC with gateway management functions.
  • the terminal You can perform the corresponding function.
  • this embodiment provides a method for creating a personal IoT network PIN, where the method is executed by a terminal and includes:
  • Step 131 Send feedback information to the core network element, where the feedback information is used to indicate that PIN information has been received or that PIN information has not been received.
  • the application function AF is authorized by a predetermined terminal to trigger the creation of a PIN; the AF sends request information to the UDM through the NEF, where the request information is used to request the creation of a PIN; the UDM receives the request information sent by the AF; and determines that the request information is received , UDM creates PIN. After determining that the PIN is successfully created, UDM will send PIN information to the target terminal.
  • the PIN information includes: the PIN information contained in the request information and the PIN parameter information generated by UDM.
  • the UDM also sends a response message to the AF via NEF for the requested information.
  • the feedback message received indicates that the PIN is received, and a response message accepting the request information is sent to the AF; or, it is determined that the feedback information is not received, indicating that the PIN is not received, and a response message rejecting the request information is sent to the AF.
  • Example 1 In order to better understand the embodiments of the present disclosure, the technical solution of the present disclosure is further described below through an exemplary embodiment: Example 1
  • this embodiment provides a method for creating a personal IoT network PIN, where the method is executed by a terminal and includes:
  • Step 141. AF sends request information (PIN create request[UE ID,PIN info ⁇ PIN name,PIN services,PINE list ⁇ ) to UDM through NEF, where the request information is used to request to create a PIN.
  • the request information can include the name of the created network, services provided by the network, service duration and PIN member information.
  • Step 142 Confirm that the request information is received, and UDM creates a PIN.
  • Step 143 Confirm that the PIN is successfully created, and UDM sends a response message to create a PIN (PIN create response[result,optional ⁇ PIN info ⁇ ]) to AF.
  • Step 144 UDM updates the subscription data of the terminal, where the updated subscription data includes the data of the PIN information contained in the request information and/or the data of the PIN parameters generated by the core network element.
  • Step 145 UDM sends PIN information (Nudm_SDM_Notification[PIN info ⁇ PIN ID,PIN name,PINE list ⁇ ]) to AMF.
  • PIN information includes: the PIN information contained in the request information and the PIN parameters generated by the core network element. information.
  • Step 146 AMF sends PIN information (DL NAS TRANSPORT[UPU container ⁇ PIN info ⁇ ]) to the terminal.
  • PIN information DL NAS TRANSPORT[UPU container ⁇ PIN info ⁇ ]
  • Step 147 Confirm that the PIN information is received, and the terminal updates the local PIN information.
  • Step 148 The terminal sends feedback information (UL NAS TRANSPORT [UPU ACK]) to the AMF.
  • Step 149 AMF sends feedback information (Nudm_SDM_Info) to UDM.
  • Step 150 UDM sends feedback information (PIN create response[result,optional ⁇ PIN info ⁇ ]) to AF.
  • this embodiment provides a device for creating a personal IoT network PIN, where the device includes:
  • the receiving module 151 is configured to receive the request information sent by the application function AF;
  • the request information is used to request the creation of a PIN.
  • this embodiment provides a device for creating a personal IoT network PIN, where the device includes:
  • the sending module 161 is configured to send request information to the core network element
  • the request information is used to request the creation of a PIN.
  • this embodiment provides a device for creating a personal IoT network PIN, where the device includes:
  • the receiving module 171 is configured to receive PIN information sent by the core network element, where the PIN information includes: PIN information contained in the request information and PIN parameter information generated by the core network element.
  • An embodiment of the present disclosure provides a communication device.
  • the communication device includes:
  • Memory used to store instructions executable by the processor
  • the processor is configured to: when executing executable instructions, implement the method applied to any embodiment of the present disclosure.
  • the processor may include various types of storage media, which are non-transitory computer storage media that can continue to memorize information stored on the communication device after the communication device is powered off.
  • the processor can be connected to the memory through a bus, etc., and is used to read the executable program stored in the memory.
  • An embodiment of the present disclosure also provides a computer storage medium, wherein the computer storage medium stores a computer executable program, and when the executable program is executed by a processor, the method of any embodiment of the present disclosure is implemented.
  • one embodiment of the present disclosure provides a structure of a terminal.
  • the terminal 800 may be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a game console, a tablet device, a medical device, a fitness device, a personal digital assistant, etc. .
  • the terminal 800 may include one or more of the following components: a processing component 802, a memory 804, a power supply component 806, a multimedia component 808, an audio component 810, an input/output (I/O) interface 812, a sensor component 814, and communications component 816.
  • Processing component 802 generally controls the overall operations of terminal 800, such as operations associated with display, phone calls, data communications, camera operations, and recording operations.
  • the processing component 802 may include one or more processors 820 to execute instructions to complete all or part of the steps of the above method.
  • processing component 802 may include one or more modules that facilitate interaction between processing component 802 and other components.
  • processing component 802 may include a multimedia module to facilitate interaction between multimedia component 808 and processing component 802.
  • Memory 804 is configured to store various types of data to support operations at device 800 . Examples of such data include instructions for any application or method operating on the terminal 800, contact data, phonebook data, messages, pictures, videos, etc.
  • Memory 804 may be implemented by any type of volatile or non-volatile storage device, or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EEPROM), Programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disk.
  • SRAM static random access memory
  • EEPROM electrically erasable programmable read-only memory
  • EEPROM erasable programmable read-only memory
  • EPROM Programmable read-only memory
  • PROM programmable read-only memory
  • ROM read-only memory
  • magnetic memory flash memory, magnetic or optical disk.
  • Power supply component 806 provides power to various components of terminal 800.
  • Power component 806 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to terminal 800.
  • Multimedia component 808 includes a screen that provides an output interface between terminal 800 and the user.
  • the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from the user.
  • the touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. A touch sensor can not only sense the boundaries of a touch or swipe action, but also detect the duration and pressure associated with the touch or swipe action.
  • multimedia component 808 includes a front-facing camera and/or a rear-facing camera.
  • the front camera and/or the rear camera may receive external multimedia data.
  • Each front-facing camera and rear-facing camera can be a fixed optical lens system or have a focal length and optical zoom capabilities.
  • Audio component 810 is configured to output and/or input audio signals.
  • audio component 810 includes a microphone (MIC) configured to receive external audio signals when terminal 800 is in operating modes, such as call mode, recording mode, and voice recognition mode. The received audio signal may be further stored in memory 804 or sent via communication component 816 .
  • audio component 810 also includes a speaker for outputting audio signals.
  • the I/O interface 812 provides an interface between the processing component 802 and a peripheral interface module, which may be a keyboard, a click wheel, a button, etc. These buttons may include, but are not limited to: Home button, Volume buttons, Start button, and Lock button.
  • Sensor component 814 includes one or more sensors that provide various aspects of status assessment for terminal 800 .
  • the sensor component 814 can detect the open/closed state of the device 800, the relative positioning of components, such as the display and keypad of the terminal 800, the sensor component 814 can also detect the position change of the terminal 800 or a component of the terminal 800, the user The presence or absence of contact with the terminal 800, the terminal 800 orientation or acceleration/deceleration and the temperature change of the terminal 800.
  • Sensor assembly 814 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact.
  • Sensor assembly 814 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications.
  • the sensor component 814 may also include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.
  • the communication component 816 is configured to facilitate wired or wireless communication between the terminal 800 and other devices.
  • the terminal 800 can access a wireless network based on a communication standard, such as Wi-Fi, 2G or 3G, or a combination thereof.
  • the communication component 816 receives broadcast signals or broadcast related information from an external broadcast management system via a broadcast channel.
  • communications component 816 also includes a near field communications (NFC) module to facilitate short-range communications.
  • NFC near field communications
  • the NFC module can be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology and other technologies.
  • RFID radio frequency identification
  • IrDA infrared data association
  • UWB ultra-wideband
  • Bluetooth Bluetooth
  • the terminal 800 may be configured by one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable Gate array (FPGA), controller, microcontroller, microprocessor or other electronic components are implemented for executing the above method.
  • ASICs application specific integrated circuits
  • DSPs digital signal processors
  • DSPDs digital signal processing devices
  • PLDs programmable logic devices
  • FPGA field programmable Gate array
  • controller microcontroller, microprocessor or other electronic components are implemented for executing the above method.
  • non-transitory computer-readable storage medium including instructions, such as a memory 804 including instructions, which can be executed by the processor 820 of the terminal 800 to complete the above method is also provided.
  • non-transitory computer-readable storage media may be ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, etc.
  • an embodiment of the present disclosure shows the structure of a base station.
  • the base station 900 may be provided as a network side device.
  • base station 900 includes a processing component 922, which further includes one or more processors, and memory resources represented by memory 932 for storing instructions, such as application programs, executable by processing component 922.
  • the application program stored in memory 932 may include one or more modules, each corresponding to a set of instructions.
  • the processing component 922 is configured to execute instructions to perform any of the foregoing methods applied to the base station.
  • Base station 900 may also include a power supply component 926 configured to perform power management of base station 900, a wired or wireless network interface 950 configured to connect base station 900 to a network, and an input/output (I/O) interface 958.
  • Base station 900 may operate based on an operating system stored in memory 932, such as Windows ServerTM, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM or the like.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本公开实施例提供了一种创建个人物联网网络PIN的方法，其中，所述方法由核心网网元执行，所述方法包括：接收应用功能AF发送的请求信息；其中，所述请求信息用于请求创建所述PIN。

Description

创建PIN的方法、装置、通信设备及存储介质 技术领域
本公开涉及无线通信技术领域但不限于无线通信技术领域，尤其涉及一种创建PIN的方法、装置、通信设备及存储介质。
背景技术
个人物联网网络(PIN，Personal IoT Network)由使用PIN直接连接或直接网络连接进行通信的PIN元素组成，并在本地进行管理(使用具有管理能力的PIN元素)。PIN的示例包括可穿戴设备网络、智能家居和/或智能办公设备。通过具有网关功能的PIN元素，PIN元素可以访问网络服务，并且可以与不在范围内的PIN元素进行通信以使用PIN直接连接。一个PIN包括至少一个具有网关能力的PIN元素和至少一个具有管理能力的PIN元素。相关技术中，如何创建PIN并未给出解决方案。
发明内容
本公开实施例公开了一种创建PIN的方法、装置、通信设备及存储介质。
根据本公开实施例的第一方面，提供一种创建个人物联网网络PIN的方法，其中，所述方法由核心网网元执行，所述方法包括：
接收应用功能AF发送的请求信息；
其中，所述请求信息用于请求创建所述PIN。
在一个实施例中，所述请求信息包含以下至少之一的信息：
终端标识；
待创建的PIN的属性信息；
以及，待创建的PIN包括的PIN元素的信息。
在一个实施例中，所述属性信息包括以下至少之一：
PIN名称；
PIN服务的信息；
以及，PIN的有效时间。
在一个实施例中，所述PIN元素的信息包括以下至少之一：
PIN元素标识；
PIN元素类型；
PIN服务的信息；
以及，PIN元素名称。
在一个实施例中，所述接收应用功能AF发送的的请求信息，包括：
通过网络开放功能NEF接收所述AF发送的所述请求信息。
在一个实施例中，所述方法还包括：
确定接收到所述请求信息，创建所述PIN。
在一个实施例中，所述创建所述PIN，包括：
更新终端的签约数据，其中，更新后的所述签约数据包括所述请求信息包含的PIN信息的数据和/或所述核心网网元生成的PIN参数的数据。
在一个实施例中，所述方法还包括：
确定成功创建所述PIN，向终端发送PIN信息，其中，PIN信息包括：所述请求信息包含的PIN信息和所述核心网网元生成的PIN参数的信息。
在一个实施例中，所述向终端发送PIN信息，包括：
通过用户参数更新UPU流程或者终端配置更新UCU流程向所述终端发送所述PIN信息。
在一个实施例中，所述PIN信息包括所述终端可以被配置为个人物联网网络元素PINE、具有管理功能的个人物联网网络元素PEMC和/或具有网关管理功能的个人物联网网络元素PEGC。
在一个实施例中，所述方法还包括：
接收所述终端发送的反馈消息。
在一个实施例中，所述方法还包括：
向所述AF发送创建所述PIN的响应消息。
在一个实施例中，所述向所述AF发送创建所述PIN的响应消息，包括：
确定成功创建所述PIN，向所述AF发送接受所述请求信息的响应消息；
或者，
确定未成功创建所述PIN，向所述AF发送拒绝所述请求信息的响应消息；
或者，
确定接收到的所述反馈消息指示接收到所述PIN，向所述AF发送接受所述请求信息的响应消息；
或者，
确定未接收到所述反馈信息指示未接收到所述PIN，向所述AF发送拒绝所述请求信息的响应消息。
在一个实施例中，所述向所述AF发送创建所述PIN的响应消息，包括：
通过NEF向所述AF发送创建所述PIN的响应消息。
根据本公开实施例的第二方面，提供一种创建个人物联网网络PIN的方法，其中，所述方法由AF执行，所述方法包括：
向核心网网元发送请求信息；
其中，所述请求信息用于请求创建所述PIN。
在一个实施例中，所述请求信息包含以下至少之一的信息：
终端标识；
待创建的PIN的属性信息；
以及，待创建的PIN包括的PIN元素的信息。
在一个实施例中，所述属性信息包括以下至少之一：
PIN名称；
PIN服务的信息；
以及，PIN的有效时间。
在一个实施例中，所述PIN元素的信息包括以下至少之一：
PIN元素标识；
PIN元素类型；
PIN服务的信息；
以及，PIN元素名称。在一个实施例中，所述向核心网网元发送请求信息，包括：
通过网络开放功能NEF向核心网网元发送请求信息。
在一个实施例中，所述方法还包括：
接收创建所述PIN的响应消息，其中，所述响应消息为接受所述请求信息的响应消息和拒绝所述请求信息中的至少一种。
在一个实施例中，所述接收创建所述PIN的响应消息，包括：
通过NEF接收创建所述PIN的响应消息。
根据本公开实施例的第三方面，提供一种创建个人物联网网络PIN的方法，其中，所述方法由终端执行，所述方法包括：
接收核心网网元发送的PIN信息，其中，PIN信息包括：所述请求信息包含的PIN信息和/或所述核心网网元生成的PIN参数的信息。
在一个实施例中，所述接收核心网网元发送的PIN信息，包括：
通过用户参数更新UPU流程接收所述核心网网元发送的PIN信息。
在一个实施例中，所述PIN信息包括所述终端可以被配置为个人物联网网络元素PINE、具有管理功能的个人物联网网络元素PEMC和/或具有网关管理功能的个人物联网网络元素PEGC。
在一个实施例中，所述方法还包括：
向核心网网元发送反馈信息，其中，所述反馈信息用于指示接收到所述PIN信息或者未接收到所述PIN信息。
根据本公开实施例的第四方面，提供一种创建个人物联网网络PIN的装置，其中，所述装置包括：
接收模块，被配置为接收应用功能AF发送的请求信息；
其中，所述请求信息用于请求创建所述PIN。
根据本公开实施例的第五方面，提供一种创建个人物联网网络PIN的装置，其中，所述装置包括：
发送模块，被配置为向核心网网元发送请求信息；
其中，所述请求信息用于请求创建所述PIN。
根据本公开实施例的第六方面，提供一种创建个人物联网网络PIN的装置，其中，所述装置包括：
接收模块，被配置为接收核心网网元发送的PIN信息，其中，PIN信息包括：所述请求信息包含的PIN信息和所述核心网网元生成的PIN参数的信息。
根据本公开实施例的第七方面，提供一种通信设备，所述通信设备，包括：
处理器；
用于存储所述处理器可执行指令的存储器；
其中，所述处理器被配置为：用于运行所述可执行指令时，实现本公开任意实施例所述的方法。
根据本公开实施例的第八方面，提供一种计算机存储介质，所述计算机存储介质存储有计算机可执行程序，所述可执行程序被处理器执行时实现本公开任意实施例所述的方法。
在本公开实施例中，接收应用功能AF发送的请求信息；其中，所述请求信息用于请求创建所述PIN。这里，核心网网元在接收到应用功能AF发送的请求信息后，就可以基于所述请求信息创建所述PIN，相较于不能根据请求创建所述PIN的情况，可以适应于创建所述PIN的需求，灵活地创建所述PIN，给用户提供服务，满足各类场景下的应用需求。
附图说明
图1是根据一示例性实施例示出的一种无线通信系统的结构示意图。
图2是根据一示例性实施例示出的一种创建个人物联网网络PIN的方法的流程示意图。
图3是根据一示例性实施例示出的一种创建个人物联网网络PIN的方法的流程示意图。
图4是根据一示例性实施例示出的一种创建个人物联网网络PIN的方法的流程示意图。
图5是根据一示例性实施例示出的一种创建个人物联网网络PIN的方法的流程示意图。
图6是根据一示例性实施例示出的一种创建个人物联网网络PIN的方法的流程示意图。
图7是根据一示例性实施例示出的一种创建个人物联网网络PIN的方法的流程示意图。
图8是根据一示例性实施例示出的一种创建个人物联网网络PIN的方法的流程示意图。
图9是根据一示例性实施例示出的一种创建个人物联网网络PIN的方法的流程示意图。
图10是根据一示例性实施例示出的一种创建个人物联网网络PIN的方法的流程示意图。
图11是根据一示例性实施例示出的一种创建个人物联网网络PIN的方法的流程示意图。
图12是根据一示例性实施例示出的一种创建个人物联网网络PIN的方法的流程示意图。
图13是根据一示例性实施例示出的一种创建个人物联网网络PIN的方法的流程示意图。
图14是根据一示例性实施例示出的一种创建个人物联网网络PIN的方法的流程示意图。
图15是根据一示例性实施例示出的一种创建个人物联网网络PIN的装置示意图。
图16是根据一示例性实施例示出的一种创建个人物联网网络PIN的装置示意图。
图17是根据一示例性实施例示出的一种创建个人物联网网络PIN的装置示意图。
图18是根据一示例性实施例示出的一种终端的结构示意图。
图19是根据一示例性实施例示出的一种基站的框图。
具体实施方式
这里将详细地对示例性实施例进行说明，其示例表示在附图中。下面的描述涉及附图时，除非另有 表示，不同附图中的相同数字表示相同或相似的要素。以下示例性实施例中所描述的实施方式并不代表与本公开实施例相一致的所有实施方式。相反，它们仅是与如所附权利要求书中所详述的、本公开实施例的一些方面相一致的装置和方法的例子。
在本公开实施例使用的术语是仅仅出于描述特定实施例的目的，而非旨在限制本公开实施例。在本公开实施例和所附权利要求书中所使用的单数形式的“一种”和“该”也旨在包括多数形式，除非上下文清楚地表示其他含义。还应当理解，本文中使用的术语“和/或”是指并包含一个或多个相关联的列出项目的任何或所有可能组合。
应当理解，尽管在本公开实施例可能采用术语第一、第二、第三等来描述各种信息，但这些信息不应限于这些术语。这些术语仅用来将同一类型的信息彼此区分开。例如，在不脱离本公开实施例范围的情况下，第一信息也可以被称为第二信息，类似地，第二信息也可以被称为第一信息。取决于语境，如在此所使用的词语“如果”可以被解释成为“在……时”或“当……时”或“响应于确定”。
出于简洁和便于理解的目的，本文在表征大小关系时，所使用的术语为“大于”或“小于”。但对于本领域技术人员来说，可以理解：术语“大于”也涵盖了“大于等于”的含义，“小于”也涵盖了“小于等于”的含义。
请参考图1，其示出了本公开实施例提供的一种无线通信系统的结构示意图。如图1所示，无线通信系统是基于移动通信技术的通信系统，该无线通信系统可以包括：若干个用户设备110以及若干个基站120。
其中，用户设备110可以是指向用户提供语音和/或数据连通性的设备。用户设备110可以经无线接入网(Radio Access Network，RAN)与一个或多个核心网进行通信，用户设备110可以是物联网用户设备，如传感器设备、移动电话和具有物联网用户设备的计算机，例如，可以是固定式、便携式、袖珍式、手持式、计算机内置的或者车载的装置。例如，站(Station，STA)、订户单元(subscriber unit)、订户站(subscriber station)，移动站(mobile station)、移动台(mobile)、远程站(remote station)、接入点、远程用户设备(remote terminal)、接入用户设备(access terminal)、用户装置(user terminal)、用户代理(user agent)、用户设备(user device)、或用户设备(user equipment)。或者，用户设备110也可以是无人飞行器的设备。或者，用户设备110也可以是车载设备，比如，可以是具有无线通信功能的行车电脑，或者是外接行车电脑的无线用户设备。或者，用户设备110也可以是路边设备，比如，可以是具有无线通信功能的路灯、信号灯或者其它路边设备等。
基站120可以是无线通信系统中的网络侧设备。其中，该无线通信系统可以是第四代移动通信技术(the 4th generation mobile communication，4G)系统，又称长期演进(Long Term Evolution，LTE)系统；或者，该无线通信系统也可以是5G系统，又称新空口系统或5G NR系统。或者，该无线通信系统也可以是5G系统的再下一代系统。其中，5G系统中的接入网可以称为NG-RAN(New Generation-Radio Access Network，新一代无线接入网)。
其中，基站120可以是4G系统中采用的演进型基站(eNB)。或者，基站120也可以是5G系统中采用集中分布式架构的基站(gNB)。当基站120采用集中分布式架构时，通常包括集中单元(central unit，CU)和至少两个分布单元(distributed unit，DU)。集中单元中设置有分组数据汇聚协议(Packet Data  Convergence Protocol，PDCP)层、无线链路层控制协议(Radio Link Control，RLC)层、媒体访问控制(Media Access Control，MAC)层的协议栈；分布单元中设置有物理(Physical，PHY)层协议栈，本公开实施例对基站120的具体实现方式不加以限定。
基站120和用户设备110之间可以通过无线空口创建无线连接。在不同的实施方式中，该无线空口是基于第四代移动通信网络技术(4G)标准的无线空口；或者，该无线空口是基于第五代移动通信网络技术(5G)标准的无线空口，比如该无线空口是新空口；或者，该无线空口也可以是基于5G的更下一代移动通信网络技术标准的无线空口。
在一些实施例中，用户设备110之间还可以创建E2E(End to End，端到端)连接。比如车联网通信(vehicle to everything，V2X)中的V2V(vehicle to vehicle，车对车)通信、V2I(vehicle to Infrastructure，车对路边设备)通信和V2P(vehicle to pedestrian，车对人)通信等场景。
这里，上述用户设备可认为是下面实施例的终端设备。
在一些实施例中，上述无线通信系统还可以包含网络管理设备130。
若干个基站120分别与网络管理设备130相连。其中，网络管理设备130可以是无线通信系统中的核心网设备，比如，该网络管理设备130可以是演进的数据分组核心网(Evolved Packet Core，EPC)中的移动性管理实体(Mobility Management Entity，MME)。或者，该网络管理设备也可以是其它的核心网设备，比如服务网关(Serving GateWay，SGW)、公用数据网网关(Public Data Network GateWay，PGW)、策略与计费规则功能单元(Policy and Charging Rules Function，PCRF)或者归属签约用户服务器(Home Subscriber Server，HSS)等。对于网络管理设备130的实现形态，本公开实施例不做限定。
为了便于本领域内技术人员理解，本公开实施例列举了多个实施方式以对本公开实施例的技术方案进行清晰地说明。当然，本领域内技术人员可以理解，本公开实施例提供的多个实施例，可以被单独执行，也可以与本公开实施例中其他实施例的方法结合后一起被执行，还可以单独或结合后与其他相关技术中的一些方法一起被执行；本公开实施例并不对此作出限定。
为了更好地理解本公开任一个实施例所描述的技术方案，首先，对相关技术中的应用场景进行说明：
在一个实施例中，PIN元素和PIN的管理包括不同类型的PIN元素的管理和PIN的配置。网络运营商和授权的第三方3方等具有管理能力的PIN元素(PEMC，PIN Element with Management Capability)都可以创建和配置PIN及PIN元素。创建PIN后，PEMC可以将具备网关功能的元素(PEGC，PIN Element with Gateway Capability)添加到PIN中，或从PIN中删除PEGC，以及将PIN元素添加到PIN并将PIN元素关联到已添加到PIN中的一些PEGC，或从PIN中删除PIN元素。
第五代移动通信网络系统中主要研究如下方面：
1、如何支持网络运营商或授权的第三方(例如，PEMC)的PIN管理机制，例如，创建、修改、删除、激活或者停用PIN等。
2、如何支持对PIN元素的管理，包括：添加或者删除PIN元素，以及PEGC与其他PIN元素的关联。
3、如何支持创建和执行PIN的有效期、时间有效性(例如，PIN的有效期为30分钟，PIN有 效期为从15:00至23:00)和PIN中的PIN元素(例如，个人IoT网络成员(PINE，PIN Element)将成为PIN成员1小时，PIN元素将在16:00至17：00时成为PIN成员)。
需要说明的是，PIN元素也可以理解为PIN网络的PIN成员。
如图2所示，本实施例中提供一种创建个人物联网网络PIN的方法，其中，方法由核心网网元执行，方法包括：
步骤21、接收应用功能AF发送的请求信息；
其中，请求信息用于请求创建PIN。
这里，本公开所涉及的终端可以是但不限于是手机、可穿戴设备、车载终端、路侧单元(RSU，Road Side Unit)、智能家居终端、工业用传感设备和/或医疗设备等。在一些实施例中，该终端可以是Redcap终端或者预定版本的新空口NR终端(例如，R17的NR终端)。
本公开中涉及的基站可以为各种类型的基站，例如，第三代移动通信(3G)网络的基站、第四代移动通信(4G)网络的基站、第五代移动通信(5G)网络的基站或其它演进型基站。
本公开中涉及的网元可以是接入和移动性管理功能实体(AMF，Access Control And Mobility Management Function)、网络开放功能(NEF，Network Exposure Function)和统一数据管理(UDM，Unified Data Management)等。需要说明的是，网元并不限于上述例举，也可以是任一具备创建PIN的网元。在本公开的一些实施方式中，具备创建PIN的网元可以单独作为一个通信节点部署，也可以统一部署在已有网元内。总之，可以将具备创建PIN的网元理解为一个网络中可以灵活部署的逻辑节点，在此不做限定。
在一个实施例中，核心网网元可以是UDM。
在一个实施例中，应用功能AF被授权的预定终端触发创建PIN；AF向UDM发送请求信息，其中，请求信息用于请求创建PIN；UDM接收AF发送的请求信息；确定接收到请求信息，UDM创建PIN。
在一个实施例中，应用功能AF被授权的预定终端触发创建PIN；AF通过NEF向UDM发送请求信息，其中，请求信息用于请求创建PIN；UDM接收AF发送的请求信息；确定接收到请求信息，UDM创建PIN。
需要说明的是AF可以事先被授权可以创建PIN网络。
在一个场景实施例中，A用户需要在学校的N楼层创建PIN，A用户可以利用被AF授权的手机(预定终端)向AF发出指示信息，指示信息可以包含创建网络的名称、网络提供的服务、服务时长和PIN成员的信息，需要说明的是，指示信息并不限于上述信息。AF在接收到指示信息后，向UDM发送请求信息，其中，请求信息用于请求创建PIN，请求信息可以包含指示信息包含的信息。UDM接收AF发送的请求信息。确定接收到请求信息，UDM创建PIN。
在一个实施例中，请求信息包含以下至少之一的PIN信息：
终端标识；
待创建的PIN的属性信息；
待创建的PIN包括的PIN元素的信息。
在一个实施例中，终端标识包括通用的外部标识。需要说明的是，在UDM创建PIN成功后，会向该终端标识指示的终端发送PIN信息。
在一个实施例中，待创建的PIN的属性信息包括以下至少之一：PIN名称(是用户可读的信息)、PIN服务(PINE提供的服务，例如打印机、灯、相机等)和PIN有效时间(用于定义PIN可以工作多长时间，例如30分钟)。
在一个实施例中，待创建的PIN包括的PIN元素的信息包括以下至少之一：PIN元素标识(由PEMC分配的PIN内的唯一ID)、PIN元素类型(指示是PEMC，还是PEGC，还是普通PINE)、服务信息(PIN元素可以提供什么服务，例如打印机、灯或相机等)和PIN元素名称(人可读信息，例如，卧室的打印机或客厅的灯)。
在一个实施例中，应用功能AF被授权的预定终端触发创建PIN；AF向UDM发送请求信息，其中，请求信息用于请求创建PIN；UDM接收AF发送的请求信息；确定接收到请求信息，UDM创建PIN。确定成功创建PIN，UDM会向目标终端发送PIN信息，其中，PIN信息包括：请求信息包含的PIN信息和UDM生成的PIN参数的信息。这里，目标终端可以是AF事先确定的能够充当PEMC的终端，示例性地，AF可以事先确定该目标终端的身份标识ID。
在一个实施例中，应用功能AF被授权的预定终端触发创建PIN；AF向UDM发送请求信息，其中，请求信息用于请求创建PIN；UDM接收AF发送的请求信息；确定接收到请求信息，UDM创建PIN；创建PIN，包括：更新终端的签约数据，其中，更新后的签约数据包括请求信息包含的PIN信息的数据和/或核心网网元生成的PIN参数的数据。确定成功创建PIN，UDM会向目标终端发送PIN信息，其中，PIN信息包括：请求信息包含的PIN信息和UDM生成的PIN参数的信息。这里，目标终端可以是AF事先确定的能够充当PEMC的终端，示例性地，AF可以事先确定该目标终端的身份标识ID。
在一个实施例中，应用功能AF被授权的预定终端触发创建PIN；AF向UDM发送请求信息，其中，请求信息用于请求创建PIN；UDM接收AF发送的请求信息；确定接收到请求信息，UDM创建PIN。确定成功创建PIN，UDM会通过用户更新流程(UPU，User Parameter Update)或者终端配置更新(UCU，UE Configuration Update)流程向目标终端发送PIN信息，其中，PIN信息包括：请求信息包含的PIN信息和UDM生成的PIN参数的信息。这里，目标终端可以是AF事先确定的能够充当PEMC的终端，示例性地，AF可以事先确定该目标终端的身份标识ID。
在一个实施例中，应用功能AF被授权的预定终端触发创建PIN；AF通过NEF向UDM发送请求信息，其中，请求信息用于请求创建PIN；UDM接收AF发送的请求信息；确定接收到请求信息，UDM创建PIN。确定成功创建PIN，向AF发送创建PIN的响应消息。
在一个实施例中，应用功能AF被授权的预定终端触发创建PIN；AF通过NEF向UDM发送请求信息，其中，请求信息用于请求创建PIN；UDM接收AF发送的请求信息；确定接收到请求信息，UDM创建PIN。确定成功创建PIN，向终端发送PIN信息，其中，PIN信息包括：请求信息包含的PIN信息和核心网网元生成的PIN参数的信息。接收终端发送的反馈消息。确定接收到的反馈消息指示接收到PIN，向AF发送创建PIN的响应消息。
在本公开实施例中，接收应用功能AF发送的请求信息；其中，请求信息用于请求创建PIN。这里， 核心网网元在接收到应用功能AF发送的请求信息后，就可以基于请求信息创建PIN，相较于不能根据请求创建PIN的情况，可以适应于创建PIN的需求，灵活地创建PIN，给用户提供服务，满足各类场景下的应用需求。
需要说明的是，本领域内技术人员可以理解，本公开实施例提供的方法，可以被单独执行，也可以与本公开实施例中一些方法或相关技术中的一些方法一起被执行。
如图3所示，本实施例中提供一种创建个人物联网网络PIN的方法，其中，方法由核心网网元执行，方法包括：
步骤31、通过网络开放功能NEF接收AF发送的请求信息。
在一个实施例中，应用功能AF被授权的预定终端触发创建PIN；AF通过NEF向UDM发送请求信息，其中，请求信息用于请求创建PIN；UDM接收AF发送的请求信息；确定接收到请求信息，UDM创建PIN。确定成功创建PIN，UDM会向目标终端发送PIN信息，其中，PIN信息包括：请求信息包含的PIN信息和UDM生成的PIN参数的信息。UDM还会向AF发送针对请求信息的响应消息。示例性地，确定成功创建PIN，向AF发送接受请求信息的响应消息；或者，确定未成功创建PIN，向AF发送拒绝请求信息的响应消息。
需要说明的是，本领域内技术人员可以理解，本公开实施例提供的方法，可以被单独执行，也可以与本公开实施例中一些方法或相关技术中的一些方法一起被执行。
如图4所示，本实施例中提供一种创建个人物联网网络PIN的方法，其中，方法由核心网网元执行，方法包括：
步骤41、确定接收到请求信息，创建PIN。
在一个实施例中，应用功能AF被授权的预定终端触发创建PIN；AF向UDM发送请求信息，其中，请求信息用于请求创建PIN；UDM接收AF发送的请求信息；确定接收到请求信息，UDM创建PIN；创建PIN，包括：更新终端的签约数据，其中，更新后的签约数据包括请求信息包含的PIN信息的数据和/或核心网网元生成的PIN参数的数据。确定成功创建PIN，UDM会向目标终端发送PIN信息，其中，PIN信息包括：请求信息包含的PIN信息和UDM生成的PIN参数的信息。这里，目标终端可以是AF事先确定的能够充当PEMC的终端，示例性地，AF可以事先确定该目标终端的身份标识ID。
需要说明的是，本领域内技术人员可以理解，本公开实施例提供的方法，可以被单独执行，也可以与本公开实施例中一些方法或相关技术中的一些方法一起被执行。
如图5所示，本实施例中提供一种创建个人物联网网络PIN的方法，其中，方法由核心网网元执行，方法包括：
步骤51、更新终端的签约数据，其中，更新后的签约数据包括请求信息包含的PIN信息的数据和/或核心网网元生成的PIN参数的数据。
这里，网元生成的PIN参数的数据可以是创建后的PIN的网络参数，例如，时延和服务质量等。
步骤51部分的描述请具体参见步骤41部分，在此不再赘述。
需要说明的是，本领域内技术人员可以理解，本公开实施例提供的方法，可以被单独执行，也可以与本公开实施例中一些方法或相关技术中的一些方法一起被执行。
如图6所示，本实施例中提供一种创建个人物联网网络PIN的方法，其中，方法由核心网网元执行，方法包括：
步骤61、确定成功创建PIN，向终端发送PIN信息，其中，PIN信息包括：请求信息包含的PIN信息和核心网网元生成的PIN参数的信息。
在一个实施例中，确定成功创建PIN，向终端发送PIN信息，其中，PIN信息包括：请求信息包含的PIN信息和核心网网元生成的PIN参数的信息。接收终端发送的反馈信息。确定接收到的反馈消息指示接收到PIN，向AF发送接受请求信息的响应消息；或者，确定未接收到反馈信息指示未接收到PIN，向AF发送拒绝请求信息的响应消息。
需要说明的是，本领域内技术人员可以理解，本公开实施例提供的方法，可以被单独执行，也可以与本公开实施例中一些方法或相关技术中的一些方法一起被执行。
如图7所示，本实施例中提供一种创建个人物联网网络PIN的方法，其中，方法由核心网网元执行，方法包括：
步骤71、向终端发送PIN信息，其中，PIN信息包括终端可以被配置为个人物联网网络元素PINE、具有管理功能的个人物联网网络元素PEMC和/或具有网关管理功能的个人物联网网络元素PEGC。
如此，在终端接收到PIN信息后，就可以确定终端被配置为个人物联网网络元素PINE、具有管理功能的个人物联网网络元素PEMC和/或具有网关管理功能的个人物联网网络元素PEGC，终端就可以执行对应的功能。
需要说明的是，本领域内技术人员可以理解，本公开实施例提供的方法，可以被单独执行，也可以与本公开实施例中一些方法或相关技术中的一些方法一起被执行。
如图8所示，本实施例中提供一种创建个人物联网网络PIN的方法，其中，方法由核心网网元执行，方法包括：
步骤81、向AF发送创建PIN的响应消息。
在一个实施例中，应用功能AF被授权的预定终端触发创建PIN；AF通过NEF向UDM发送请求信息，其中，请求信息用于请求创建PIN；UDM接收AF发送的请求信息；确定接收到请求信息，UDM创建PIN。确定成功创建PIN，UDM会向目标终端发送PIN信息，其中，PIN信息包括：请求信息包含的PIN信息和UDM生成的PIN参数的信息。UDM还会通过NEF向AF发送针对请求信息的响应消息。示例性地，确定成功创建PIN，向AF发送接受请求信息的响应消息；或者，确定未成功创建PIN，向AF发送拒绝请求信息的响应消息；或者，确定接收到的反馈消息指示接收到PIN，向AF发送接受请求信息的响应消息；或者，确定未接收到反馈信息指示未接收到PIN，向AF发送拒绝请求信息的响 应消息。
需要说明的是，本领域内技术人员可以理解，本公开实施例提供的方法，可以被单独执行，也可以与本公开实施例中一些方法或相关技术中的一些方法一起被执行。
如图9所示，本实施例中提供一种创建个人物联网网络PIN的方法，其中，方法由AF执行，方法包括：
步骤91、向核心网网元发送请求信息；
其中，所述请求信息用于请求创建所述PIN。
这里，本公开所涉及的终端可以是但不限于是手机、可穿戴设备、车载终端、路侧单元(RSU，Road Side Unit)、智能家居终端、工业用传感设备和/或医疗设备等。在一些实施例中，该终端可以是Redcap终端或者预定版本的新空口NR终端(例如，R17的NR终端)。
本公开中涉及的基站可以为各种类型的基站，例如，第三代移动通信(3G)网络的基站、第四代移动通信(4G)网络的基站、第五代移动通信(5G)网络的基站或其它演进型基站。
本公开中涉及的网元可以是接入和移动性管理功能实体(AMF，Access Control And Mobility Management Function)、网络开放功能(NEF，Network Exposure Function)和统一数据管理(UDM，Unified Data Management)等。需要说明的是，网元并不限于上述例举，也可以是任一具备创建PIN的网元。在本公开的一些实施方式中，具备创建PIN的网元可以单独作为一个通信节点部署，也可以统一部署在已有网元内。总之，可以将具备创建PIN的网元理解为一个网络中可以灵活部署的逻辑节点，在此不做限定。
在一个实施例中，核心网网元可以是UDM。
在一个实施例中，应用功能AF被授权的预定终端触发创建PIN；AF向UDM发送请求信息，其中，请求信息用于请求创建PIN；UDM接收AF发送的请求信息；确定接收到请求信息，UDM创建PIN。
在一个实施例中，应用功能AF被授权的预定终端触发创建PIN；AF通过NEF向UDM发送请求信息，其中，请求信息用于请求创建PIN；UDM接收AF发送的请求信息；确定接收到请求信息，UDM创建PIN。
需要说明的是AF可以事先被授权可以创建PIN网络。
在一个场景实施例中，A用户需要在学校的N楼层创建PIN，A用户可以利用被AF授权的手机(预定终端)向AF发出指示信息，指示信息可以包含创建网络的名称、网络提供的服务、服务时长和PIN成员的信息，需要说明的是，指示信息并不限于上述信息。AF在接收到指示信息后，向UDM发送请求信息，其中，请求信息用于请求创建PIN，请求信息可以包含指示信息包含的信息。UDM接收AF发送的请求信息。确定接收到请求信息，UDM创建PIN。
在一个实施例中，请求信息包含以下至少之一的PIN信息：
终端标识；
待创建的PIN的属性信息；
待创建的PIN包括的PIN元素的信息。
在一个实施例中，终端标识包括通用的外部标识。需要说明的是，在UDM创建PIN成功后，会向该终端标识指示的终端发送PIN信息。
在一个实施例中，待创建的PIN的属性信息包括以下至少之一：PIN名称(是用户可读的信息)、PIN服务(PINE提供的服务，例如打印机、灯、相机等)和PIN有效是时间(用于定义PIN可以工作多长时间，例如30分钟)。
在一个实施例中，待创建的PIN包括的PIN元素的信息包括以下至少之一：PIN元素标识(由PEMC分配的PIN内的唯一ID)、PIN元素类型(指示是PEMC，还是PEGC，还是普通PINE)、服务信息(PIN元素可以提供什么服务，例如打印机、灯或相机等)和PIN元素名称(人可读信息，例如，卧室的打印机或客厅的灯)。
在一个实施例中，应用功能AF被授权的预定终端触发创建PIN；AF向UDM发送请求信息，其中，请求信息用于请求创建PIN；UDM接收AF发送的请求信息；确定接收到请求信息，UDM创建PIN。确定成功创建PIN，UDM会向目标终端发送PIN信息，其中，PIN信息包括：请求信息包含的PIN信息和UDM生成的PIN参数的信息。这里，目标终端可以是AF事先确定的能够充当PEMC的终端，示例性地，AF可以事先确定该目标终端的身份标识ID。
在一个实施例中，应用功能AF被授权的预定终端触发创建PIN；AF向UDM发送请求信息，其中，请求信息用于请求创建PIN；UDM接收AF发送的请求信息；确定接收到请求信息，UDM创建PIN；创建PIN，包括：更新终端的签约数据，其中，更新后的签约数据包括请求信息包含的PIN信息的数据和/或核心网网元生成的PIN参数的数据。确定成功创建PIN，UDM会向目标终端发送PIN信息，其中，PIN信息包括：请求信息包含的PIN信息和UDM生成的PIN参数的信息。这里，目标终端可以是AF事先确定的能够充当PEMC的终端，示例性地，AF可以事先确定该目标终端的身份标识ID。
在一个实施例中，应用功能AF被授权的预定终端触发创建PIN；AF向UDM发送请求信息，其中，请求信息用于请求创建PIN；UDM接收AF发送的请求信息；确定接收到请求信息，UDM创建PIN。确定成功创建PIN，UDM会通过用户更新流程(UPU，User Parameter Update)或者终端配置更新(UCU，UE Configuration Update)流程向目标终端发送PIN信息，其中，PIN信息包括：请求信息包含的PIN信息和UDM生成的PIN参数的信息。这里，目标终端可以是AF事先确定的能够充当PEMC的终端，示例性地，AF可以事先确定该目标终端的身份标识ID。
在一个实施例中，应用功能AF被授权的预定终端触发创建PIN；AF通过NEF向UDM发送请求信息，其中，请求信息用于请求创建PIN；UDM接收AF发送的请求信息；确定接收到请求信息，UDM创建PIN。确定成功创建PIN，向AF发送创建PIN的响应消息。
在一个实施例中，应用功能AF被授权的预定终端触发创建PIN；AF通过NEF向UDM发送请求信息，其中，请求信息用于请求创建PIN；UDM接收AF发送的请求信息；确定接收到请求信息，UDM创建PIN。确定成功创建PIN，向终端发送PIN信息，其中，PIN信息包括：请求信息包含的PIN信息和核心网网元生成的PIN参数的信息。接收终端发送的反馈消息。确定接收到的反馈消息指示接收到PIN，向AF发送创建PIN的响应消息。
需要说明的是，本领域内技术人员可以理解，本公开实施例提供的方法，可以被单独执行，也可以 与本公开实施例中一些方法或相关技术中的一些方法一起被执行。
如图10所示，本实施例中提供一种创建个人物联网网络PIN的方法，其中，方法由AF执行，方法包括：
步骤101、通过网络开放功能NEF向核心网网元发送请求信息。
在一个实施例中，应用功能AF被授权的预定终端触发创建PIN；AF通过NEF向UDM发送请求信息，其中，请求信息用于请求创建PIN；UDM接收AF发送的请求信息；确定接收到请求信息，UDM创建PIN。
需要说明的是，本领域内技术人员可以理解，本公开实施例提供的方法，可以被单独执行，也可以与本公开实施例中一些方法或相关技术中的一些方法一起被执行。
如图11所示，本实施例中提供一种创建个人物联网网络PIN的方法，其中，方法由AF执行，方法包括：
步骤111、接收创建PIN的响应消息，其中，响应消息为接受请求信息的响应消息和拒绝请求信息中的至少一种。
在一个实施例中，通过NEF接收创建PIN的响应消息。
在一个实施例中，应用功能AF被授权的预定终端触发创建PIN；AF通过NEF向UDM发送请求信息，其中，请求信息用于请求创建PIN；UDM接收AF发送的请求信息；确定接收到请求信息，UDM创建PIN。确定成功创建PIN，UDM会向目标终端发送PIN信息，其中，PIN信息包括：请求信息包含的PIN信息和UDM生成的PIN参数的信息。UDM还会通过NEF向AF发送针对请求信息的响应消息。示例性地，确定成功创建PIN，向AF发送接受请求信息的响应消息；或者，确定未成功创建PIN，向AF发送拒绝请求信息的响应消息；或者，确定接收到的反馈消息指示接收到PIN，向AF发送接受请求信息的响应消息；或者，确定未接收到反馈信息指示未接收到PIN，向AF发送拒绝请求信息的响应消息。
需要说明的是，本领域内技术人员可以理解，本公开实施例提供的方法，可以被单独执行，也可以与本公开实施例中一些方法或相关技术中的一些方法一起被执行。
如图12所示，本实施例中提供一种创建个人物联网网络PIN的方法，其中，方法由终端执行，方法包括：
步骤121、接收核心网网元发送的PIN信息，其中，PIN信息包括：请求信息包含的PIN信息和/或核心网网元生成的PIN参数的信息。
在一个实施例中，请求信息包含以下至少之一的PIN信息：
终端标识；
待创建的PIN的属性信息；
待创建的PIN包括的PIN元素的信息。
在一个实施例中，终端标识包括通用的外部标识。需要说明的是，在UDM创建PIN成功后，会向该终端标识指示的终端发送PIN信息。
在一个实施例中，待创建的PIN的属性信息包括以下至少之一：PIN名称(是用户可读的信息)、PIN服务(PINE提供的服务，例如打印机、灯、相机等)和PIN有效是时间(用于定义PIN可以工作多长时间，例如30分钟)。
在一个实施例中，待创建的PIN包括的PIN元素的信息包括以下至少之一：PIN元素标识(由PEMC分配的PIN内的唯一ID)、PIN元素类型(指示是PEMC，还是PEGC，还是普通PINE)、服务信息(PIN元素可以提供什么服务，例如打印机、灯或相机等)和PIN元素名称(人可读信息，例如，卧室的打印机或客厅的灯)。
在一个实施例中，应用功能AF被授权的预定终端触发创建PIN；AF向UDM发送请求信息，其中，请求信息用于请求创建PIN；UDM接收AF发送的请求信息；确定接收到请求信息，UDM创建PIN；创建PIN，包括：更新终端的签约数据，其中，更新后的签约数据包括请求信息包含的PIN信息的数据和/或核心网网元生成的PIN参数的数据。确定成功创建PIN，UDM会向终端发送PIN信息，其中，PIN信息包括：请求信息包含的PIN信息和UDM生成的PIN参数的信息。终端接收PIN信息。这里，终端可以是AF事先确定的能够充当PEMC的终端，示例性地，AF可以事先确定该终端的身份标识ID。
在一个实施例中，PIN信息包括终端可以被配置为个人物联网网络元素PINE、具有管理功能的个人物联网网络元素PEMC和/或具有网关管理功能的个人物联网网络元素PEGC。
如此，在终端接收到PIN信息后，就可以确定终端被配置为个人物联网网络元素PINE、具有管理功能的个人物联网网络元素PEMC和/或具有网关管理功能的个人物联网网络元素PEGC，终端就可以执行对应的功能。
需要说明的是，本领域内技术人员可以理解，本公开实施例提供的方法，可以被单独执行，也可以与本公开实施例中一些方法或相关技术中的一些方法一起被执行。
如图13所示，本实施例中提供一种创建个人物联网网络PIN的方法，其中，方法由终端执行，方法包括：
步骤131、向核心网网元发送反馈信息，其中，反馈信息用于指示接收到PIN信息或者未接收到PIN信息。
在一个实施例中，应用功能AF被授权的预定终端触发创建PIN；AF通过NEF向UDM发送请求信息，其中，请求信息用于请求创建PIN；UDM接收AF发送的请求信息；确定接收到请求信息，UDM创建PIN。确定成功创建PIN，UDM会向目标终端发送PIN信息，其中，PIN信息包括：请求信息包含的PIN信息和UDM生成的PIN参数的信息。UDM还会通过NEF向AF发送针对请求信息的响应消息。示例性地，确定接收到的反馈消息指示接收到PIN，向AF发送接受请求信息的响应消息；或者，确定未接收到反馈信息指示未接收到PIN，向AF发送拒绝请求信息的响应消息。
需要说明的是，本领域内技术人员可以理解，本公开实施例提供的方法，可以被单独执行，也可以与本公开实施例中一些方法或相关技术中的一些方法一起被执行。
为了更好地理解本公开实施例，以下通过1个示例性实施例对本公开技术方案进行进一步说明：、示例1
如图14所示，本实施例中提供一种创建个人物联网网络PIN的方法，其中，方法由终端执行，方法包括：
步骤141、AF通过NEF向UDM发送请求信息(PIN create request[UE ID,PIN info{PIN name,PIN services,PINE list{})，其中，请求信息用于请求创建PIN。请求信息可以包含创建网络的名称、网络提供的服务、服务时长和PIN成员的信息。
步骤142、确定接收到请求信息，UDM创建PIN。
步骤143、确定成功创建PIN，UDM向AF发送创建PIN的响应消息(PIN create response[result,optional{PIN info}])。
步骤144、UDM更新终端的签约数据，其中，更新后的签约数据包括请求信息包含的PIN信息的数据和/或核心网网元生成的PIN参数的数据。
步骤145、UDM向AMF发送PIN信息(Nudm_SDM_Notification[PIN info{PIN ID,PIN name,PINE list{}])，其中，PIN信息包括：请求信息包含的PIN信息和核心网网元生成的PIN参数的信息。
步骤146、AMF向终端发送PIN信息(DL NAS TRANSPORT[UPU container{PIN info}])。
步骤147、确定接收到PIN信息，终端更新本地PIN信息。
步骤148、终端向AMF发送反馈信息(UL NAS TRANSPORT[UPU ACK])。
步骤149、AMF向UDM发送反馈信息(Nudm_SDM_Info)。
步骤150、UDM向AF发送反馈信息(PIN create response[result,optional{PIN info}])。
如图15所示，本实施例中提供一种创建个人物联网网络PIN的装置，其中，装置包括：
接收模块151，被配置为接收应用功能AF发送的请求信息；
其中，请求信息用于请求创建PIN。
需要说明的是，本领域内技术人员可以理解，本公开实施例提供的方法，可以被单独执行，也可以与本公开实施例中一些方法或相关技术中的一些方法一起被执行。
如图16所示，本实施例中提供一种创建个人物联网网络PIN的装置，其中，装置包括：
发送模块161，被配置为向核心网网元发送请求信息；
其中，请求信息用于请求创建PIN。
需要说明的是，本领域内技术人员可以理解，本公开实施例提供的方法，可以被单独执行，也可以与本公开实施例中一些方法或相关技术中的一些方法一起被执行。
如图17所示，本实施例中提供一种创建个人物联网网络PIN的装置，其中，装置包括：
接收模块171，被配置为接收核心网网元发送的PIN信息，其中，PIN信息包括：请求信息包含的 PIN信息和核心网网元生成的PIN参数的信息。
需要说明的是，本领域内技术人员可以理解，本公开实施例提供的方法，可以被单独执行，也可以与本公开实施例中一些方法或相关技术中的一些方法一起被执行。
本公开实施例提供一种通信设备，通信设备，包括：
处理器；
用于存储处理器可执行指令的存储器；
其中，处理器被配置为：用于运行可执行指令时，实现应用于本公开任意实施例的方法。
其中，处理器可包括各种类型的存储介质，该存储介质为非临时性计算机存储介质，在通信设备掉电之后能够继续记忆存储其上的信息。
处理器可以通过总线等与存储器连接，用于读取存储器上存储的可执行程序。
本公开实施例还提供一种计算机存储介质，其中，计算机存储介质存储有计算机可执行程序，可执行程序被处理器执行时实现本公开任意实施例的方法。
关于上述实施例中的装置，其中各个模块执行操作的具体方式已经在有关该方法的实施例中进行了详细描述，此处将不做详细阐述说明。
如图18所示，本公开一个实施例提供一种终端的结构。
参照图18所示终端800本实施例提供一种终端800，该终端具体可是移动电话，计算机，数字广播终端，消息收发设备，游戏控制台，平板设备，医疗设备，健身设备，个人数字助理等。
参照图18，终端800可以包括以下一个或多个组件：处理组件802，存储器804，电源组件806，多媒体组件808，音频组件810，输入/输出(I/O)的接口812，传感器组件814，以及通信组件816。
处理组件802通常控制终端800的整体操作，诸如与显示，电话呼叫，数据通信，相机操作和记录操作相关联的操作。处理组件802可以包括一个或多个处理器820来执行指令，以完成上述的方法的全部或部分步骤。此外，处理组件802可以包括一个或多个模块，便于处理组件802和其他组件之间的交互。例如，处理组件802可以包括多媒体模块，以方便多媒体组件808和处理组件802之间的交互。
存储器804被配置为存储各种类型的数据以支持在设备800的操作。这些数据的示例包括用于在终端800上操作的任何应用程序或方法的指令，联系人数据，电话簿数据，消息，图片，视频等。存储器804可以由任何类型的易失性或非易失性存储设备或者它们的组合实现，如静态随机存取存储器(SRAM)，电可擦除可编程只读存储器(EEPROM)，可擦除可编程只读存储器(EPROM)，可编程只读存储器(PROM)，只读存储器(ROM)，磁存储器，快闪存储器，磁盘或光盘。
电源组件806为终端800的各种组件提供电力。电源组件806可以包括电源管理系统，一个或多个电源，及其他与为终端800生成、管理和分配电力相关联的组件。
多媒体组件808包括在终端800和用户之间的提供一个输出接口的屏幕。在一些实施例中，屏幕可以包括液晶显示器(LCD)和触摸面板(TP)。如果屏幕包括触摸面板，屏幕可以被实现为触摸屏，以 接收来自用户的输入信号。触摸面板包括一个或多个触摸传感器以感测触摸、滑动和触摸面板上的手势。触摸传感器可以不仅感测触摸或滑动动作的边界，而且还检测与触摸或滑动操作相关的持续时间和压力。在一些实施例中，多媒体组件808包括一个前置摄像头和/或后置摄像头。当设备800处于操作模式，如拍摄模式或视频模式时，前置摄像头和/或后置摄像头可以接收外部的多媒体数据。每个前置摄像头和后置摄像头可以是一个固定的光学透镜系统或具有焦距和光学变焦能力。
音频组件810被配置为输出和/或输入音频信号。例如，音频组件810包括一个麦克风(MIC)，当终端800处于操作模式，如呼叫模式、记录模式和语音识别模式时，麦克风被配置为接收外部音频信号。所接收的音频信号可以被进一步存储在存储器804或经由通信组件816发送。在一些实施例中，音频组件810还包括一个扬声器，用于输出音频信号。
I/O接口812为处理组件802和外围接口模块之间提供接口，上述外围接口模块可以是键盘，点击轮，按钮等。这些按钮可包括但不限于：主页按钮、音量按钮、启动按钮和锁定按钮。
传感器组件814包括一个或多个传感器，用于为终端800提供各个方面的状态评估。例如，传感器组件814可以检测到设备800的打开/关闭状态，组件的相对定位，例如组件为终端800的显示器和小键盘，传感器组件814还可以检测终端800或终端800一个组件的位置改变，用户与终端800接触的存在或不存在，终端800方位或加速/减速和终端800的温度变化。传感器组件814可以包括接近传感器，被配置用来在没有任何的物理接触时检测附近物体的存在。传感器组件814还可以包括光传感器，如CMOS或CCD图像传感器，用于在成像应用中使用。在一些实施例中，该传感器组件814还可以包括加速度传感器，陀螺仪传感器，磁传感器，压力传感器或温度传感器。
通信组件816被配置为便于终端800和其他设备之间有线或无线方式的通信。终端800可以接入基于通信标准的无线网络，如Wi-Fi，2G或3G，或它们的组合。在一个示例性实施例中，通信组件816经由广播信道接收来自外部广播管理系统的广播信号或广播相关信息。在一个示例性实施例中，通信组件816还包括近场通信(NFC)模块，以促进短程通信。例如，在NFC模块可基于射频识别(RFID)技术，红外数据协会(IrDA)技术，超宽带(UWB)技术，蓝牙(BT)技术和其他技术来实现。
在示例性实施例中，终端800可以被一个或多个应用专用集成电路(ASIC)、数字信号处理器(DSP)、数字信号处理设备(DSPD)、可编程逻辑器件(PLD)、现场可编程门阵列(FPGA)、控制器、微控制器、微处理器或其他电子元件实现，用于执行上述方法。
在示例性实施例中，还提供了一种包括指令的非临时性计算机可读存储介质，例如包括指令的存储器804，上述指令可由终端800的处理器820执行以完成上述方法。例如，非临时性计算机可读存储介质可以是ROM、随机存取存储器(RAM)、CD-ROM、磁带、软盘和光数据存储设备等。
如图19所示，本公开一实施例示出一种基站的结构。例如，基站900可以被提供为一网络侧设备。参照图19，基站900包括处理组件922，其进一步包括一个或多个处理器，以及由存储器932所代表的存储器资源，用于存储可由处理组件922的执行的指令，例如应用程序。存储器932中存储的应用程序可以包括一个或一个以上的每一个对应于一组指令的模块。此外，处理组件922被配置为执行指令，以执行上述方法前述应用在所述基站的任意方法。
基站900还可以包括一个电源组件926被配置为执行基站900的电源管理，一个有线或无线网络接口950被配置为将基站900连接到网络，和一个输入输出(I/O)接口958。基站900可以操作基于存储在存储器932的操作系统，例如Windows Server TM，Mac OS XTM，UnixTM，LinuxTM，FreeBSDTM或类似。
本领域技术人员在考虑说明书及实践这里公开的发明后，将容易想到本发明的其它实施方案。本公开旨在涵盖本发明的任何变型、用途或者适应性变化，这些变型、用途或者适应性变化遵循本发明的一般性原理并包括本公开未公开的本技术领域中的公知常识或惯用技术手段。说明书和实施例仅被视为示例性的，本发明的真正范围和精神由下面的权利要求指出。
应当理解的是，本发明并不局限于上面已经描述并在附图中示出的精确结构，并且可以在不脱离其范围进行各种修改和改变。本发明的范围仅由所附的权利要求来限制。

Claims (30)

  1. 一种创建个人物联网网络PIN的方法，其中，所述方法由核心网网元执行，所述方法包括：
    接收应用功能AF发送的请求信息；
    其中，所述请求信息用于请求创建所述PIN。
  2. 根据权利要求1所述的方法，其中，所述请求信息包含以下至少之一的信息：
    终端标识；
    待创建的PIN的属性信息；
    以及，待创建的PIN包括的PIN元素的信息。
  3. 根据权利要求2所述的方法，其中，所述属性信息包括以下至少之一：
    PIN名称；
    PIN服务的信息；
    以及，PIN的有效时间。
  4. 根据权利要求2所述的方法，其中，所述PIN元素的信息包括以下至少之一：
    PIN元素标识；
    PIN元素类型；
    PIN服务的信息；
    以及，PIN元素名称。
  5. 根据权利要求1所述的方法，其中，所述接收应用功能AF发送的的请求信息，包括：
    通过网络开放功能NEF接收所述AF发送的所述请求信息。
  6. 根据权利要求1所述的方法，其中，所述方法还包括：
    确定接收到所述请求信息，创建所述PIN。
  7. 根据权利要求6所述的方法，其中，所述创建所述PIN，包括：
    更新终端的签约数据，其中，更新后的所述签约数据包括所述请求信息包含的PIN信息的数据和/或所述核心网网元生成的PIN参数的数据。
  8. 根据权利要求6所述的方法，其中，所述方法还包括：
    确定成功创建所述PIN，向终端发送PIN信息，其中，PIN信息包括：所述请求信息包含的PIN信息和所述核心网网元生成的PIN参数的信息。
  9. 根据权利要求8所述的方法，其中，所述向终端发送PIN信息，包括：
    通过用户参数更新UPU流程或者终端配置更新UCU流程向所述终端发送所述PIN信息。
  10. 根据权利要求8所述的方法，其中，所述PIN信息包括所述终端可以被配置为个人物联网网络元素PINE、具有管理功能的个人物联网网络元素PEMC和/或具有网关管理功能的个人物联网网络元素PEGC。
  11. 根据权利要求8所述的方法，其中，所述方法还包括：
    接收所述终端发送的反馈消息。
  12. 根据权利要求6或者11所述的方法，其中，所述方法还包括：
    向所述AF发送创建所述PIN的响应消息。
  13. 根据权利要求12所述的方法，其中，所述向所述AF发送创建所述PIN的响应消息，包括：
    确定成功创建所述PIN，向所述AF发送接受所述请求信息的响应消息；
    或者，
    确定未成功创建所述PIN，向所述AF发送拒绝所述请求信息的响应消息；
    或者，
    确定接收到的所述反馈消息指示接收到所述PIN，向所述AF发送接受所述请求信息的响应消息；
    或者，
    确定未接收到所述反馈信息指示未接收到所述PIN，向所述AF发送拒绝所述请求信息的响应消息。
  14. 根据权利要求12所述的方法，其中，所述向所述AF发送创建所述PIN的响应消息，包括：
    通过NEF向所述AF发送创建所述PIN的响应消息。
  15. 一种创建个人物联网网络PIN的方法，其中，所述方法由AF执行，所述方法包括：
    向核心网网元发送请求信息；
    其中，所述请求信息用于请求创建所述PIN。
  16. 根据权利要求15所述的方法，其中，所述请求信息包含以下至少之一的信息：
    终端标识；
    待创建的PIN的属性信息；
    以及，待创建的PIN包括的PIN元素的信息。
  17. 根据权利要求16所述的方法，其中，所述属性信息包括以下至少之一：
    PIN名称；
    PIN服务的信息；
    以及，PIN的有效时间。
  18. 根据权利要求16所述的方法，其中，所述PIN元素的信息包括以下至少之一：
    PIN元素标识；
    PIN元素类型；
    PIN服务的信息；
    以及，PIN元素名称。
  19. 根据权利要求15所述的方法，其中，所述向核心网网元发送请求信息，包括：
    通过网络开放功能NEF向核心网网元发送请求信息。
  20. 根据权利要求15所述的方法，其中，所述方法还包括：
    接收创建所述PIN的响应消息，其中，所述响应消息为接受所述请求信息的响应消息和拒绝所述请求信息中的至少一种。
  21. 根据权利要求20所述的方法，其中，所述接收创建所述PIN的响应消息，包括：
    通过NEF接收创建所述PIN的响应消息。
  22. 一种创建个人物联网网络PIN的方法，其中，所述方法由终端执行，所述方法包括：
    接收核心网网元发送的PIN信息，其中，PIN信息包括：所述请求信息包含的PIN信息和/或所述核心网网元生成的PIN参数的信息。
  23. 根据权利要求22所述的方法，其中，所述接收核心网网元发送的PIN信息，包括：
    通过用户参数更新UPU流程接收所述核心网网元发送的PIN信息。
  24. 根据权利要求23所述的方法，其中，所述PIN信息包括所述终端可以被配置为个人物联网网络元素PINE、具有管理功能的个人物联网网络元素PEMC和/或具有网关管理功能的个人物联网网络元素PEGC。
  25. 根据权利要求22所述的方法，其中，所述方法还包括：
    向核心网网元发送反馈信息，其中，所述反馈信息用于指示接收到所述PIN信息或者未接收到所述PIN信息。
  26. 一种创建个人物联网网络PIN的装置，其中，所述装置包括：
    接收模块，被配置为接收应用功能AF发送的请求信息；
    其中，所述请求信息用于请求创建所述PIN。
  27. 一种创建个人物联网网络PIN的装置，其中，所述装置包括：
    发送模块，被配置为向核心网网元发送请求信息；
    其中，所述请求信息用于请求创建所述PIN。
  28. 一种创建个人物联网网络PIN的装置，其中，所述装置包括：
    接收模块，被配置为接收核心网网元发送的PIN信息，其中，PIN信息包括：所述请求信息包含的PIN信息和所述核心网网元生成的PIN参数的信息。
  29. 一种通信设备，其中，包括：
    存储器；
    处理器，与所述存储器连接，被配置为通过执行存储在所述存储器上的计算机可执行指令，并能够实现权利要求1至14、15至21或者22至25任一项所述的方法。
  30. 一种计算机存储介质，所述计算机存储介质存储有计算机可执行指令，所述计算机可执行指令被处理器执行后能够实现权利要求1至14、15至21或者22至25任一项所述的方法。
PCT/CN2022/083806 2022-03-29 2022-03-29 创建pin的方法、装置、通信设备及存储介质 WO2023184172A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202280001012.9A CN117158108A (zh) 2022-03-29 2022-03-29 创建pin的方法、装置、通信设备及存储介质
PCT/CN2022/083806 WO2023184172A1 (zh) 2022-03-29 2022-03-29 创建pin的方法、装置、通信设备及存储介质

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/083806 WO2023184172A1 (zh) 2022-03-29 2022-03-29 创建pin的方法、装置、通信设备及存储介质

Publications (1)

Publication Number Publication Date
WO2023184172A1 true WO2023184172A1 (zh) 2023-10-05

Family

ID=88198452

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/083806 WO2023184172A1 (zh) 2022-03-29 2022-03-29 创建pin的方法、装置、通信设备及存储介质

Country Status (2)

Country Link
CN (1) CN117158108A (zh)
WO (1) WO2023184172A1 (zh)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106797407A (zh) * 2014-10-03 2017-05-31 瑞典爱立信有限公司 物联系统中的唯一标识符的动态生成
US20210368341A1 (en) * 2020-08-10 2021-11-25 Ching-Yu LIAO Secure access for 5g iot devices and services

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106797407A (zh) * 2014-10-03 2017-05-31 瑞典爱立信有限公司 物联系统中的唯一标识符的动态生成
US20210368341A1 (en) * 2020-08-10 2021-11-25 Ching-Yu LIAO Secure access for 5g iot devices and services

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on Personal Internet of Things (PIoT) networks (Release 18)", 3GPP TR 22.859, no. V18.2.0, 24 December 2021 (2021-12-24), pages 1 - 51, XP052083487 *
SA WG1: "New WID on Study on Personal IoT Networks (from S1-202287)", 3GPP TSG SA MEETING # 88E SP-200577, 24 June 2020 (2020-06-24), XP051905865 *
SAHOO BISWA P. S.; MOHANTY SARAJU P.; PUTHAL DEEPAK; PILLAI PRASHANT: "Personal Internet of Things (PIoT): What Is It Exactly?", IEEE CONSUMER ELECTRONICS MAGAZINE, IEEE, PISCATAWAY, NJ, USA, vol. 10, no. 6, 14 May 2021 (2021-05-14), Piscataway, NJ, USA , pages 58 - 60, XP011882484, ISSN: 2162-2248, DOI: 10.1109/MCE.2021.3077721 *

Also Published As

Publication number Publication date
CN117158108A (zh) 2023-12-01

Similar Documents

Publication Publication Date Title
WO2023130472A1 (zh) 提早识别的方法、装置、通信设备及存储介质
WO2023184172A1 (zh) 创建pin的方法、装置、通信设备及存储介质
WO2022032540A1 (zh) Uav飞行控制、管控策略处理方法及装置、设备及介质
WO2024031399A1 (zh) Ue加入pin的方法及装置、通信设备及存储介质
WO2024031390A1 (zh) 个人物联网信息更新方法、装置、通信设备及存储介质
WO2023178703A1 (zh) 个人物联网网络建立方法及装置、网元、ue及存储介质
WO2024031392A1 (zh) 个人物联网信息更新方法、装置、通信设备及存储介质
WO2024055329A1 (zh) 邻近服务ProSe的无线通信方法、装置、通信设备及存储介质
WO2023220893A1 (zh) 中继通信方法、装置、通信设备及存储介质
WO2023070509A1 (zh) 信息处理方法及装置、通信设备及存储介质
WO2023065080A1 (zh) 测距能力开放的方法、装置、通信设备及存储介质
WO2023077524A1 (zh) 一种寻呼过滤的方法、装置、通信设备及存储介质
WO2024016349A1 (zh) 提供感知服务的方法、装置、通信设备及存储介质
WO2024092800A1 (zh) 信息传输方法、装置、通信设备和存储介质
WO2024031400A1 (zh) 确定激活或去激活辅小区的方法、装置及存储介质
WO2024026893A1 (zh) 事件报告允许区域设置方法及装置、通信设备及存储介质
WO2024031640A1 (zh) 一种信息传输方法、装置、通信设备及存储介质
WO2023245588A1 (zh) 信息处理方法、装置、通信设备及存储介质
WO2023070560A1 (zh) 信息传输方法、装置、通信设备和存储介质
WO2024036530A1 (zh) 态势感知的处理方法、装置、通信设备及存储介质
WO2022160105A1 (zh) 一种应用功能会话处理方法、装置及存储介质
WO2024021095A1 (zh) 设备定位方法、系统及装置、通信设备及存储介质
WO2022236607A1 (zh) 选网信息的传输方法、装置、通信设备及存储介质
WO2024044916A1 (zh) 上报bsr的方法、装置、通信设备及存储介质
WO2023184105A1 (zh) 获取终端位置的方法、装置、通信设备及存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22934028

Country of ref document: EP

Kind code of ref document: A1