WO2024000435A1 - 物联网设备的管理方法、装置、设备和存储介质 - Google Patents

物联网设备的管理方法、装置、设备和存储介质 Download PDF

Info

Publication number
WO2024000435A1
WO2024000435A1 PCT/CN2022/102901 CN2022102901W WO2024000435A1 WO 2024000435 A1 WO2024000435 A1 WO 2024000435A1 CN 2022102901 W CN2022102901 W CN 2022102901W WO 2024000435 A1 WO2024000435 A1 WO 2024000435A1
Authority
WO
WIPO (PCT)
Prior art keywords
core network
functional entity
network functional
information
internet
Prior art date
Application number
PCT/CN2022/102901
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 CN202280002506.9A priority Critical patent/CN117643079A/zh
Priority to PCT/CN2022/102901 priority patent/WO2024000435A1/zh
Publication of WO2024000435A1 publication Critical patent/WO2024000435A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/02—Services making use of location information

Definitions

  • the present disclosure relates to the field of wireless communication technology, and in particular, to a management method, device, equipment and storage medium for an Internet of Things device.
  • IoT Internet of Things
  • IoT devices come in different types and can provide various services in different scenarios.
  • IoT devices there is a type of IoT devices that can be used to implement positioning functions. This type of IoT device may also be called an IoT positioning device.
  • mobile networks also need to be able to support positioning services for IoT devices to further implement location-based services.
  • the present disclosure provides a management method, device, equipment and storage medium for an Internet of Things device, so as to realize mobile network support for Internet of Things devices used for positioning services.
  • the present disclosure provides a management method for Internet of Things devices.
  • This method can be applied to the first core network device.
  • the above method includes: the first core network functional entity receives first information from the second core network functional entity, where the first information includes contract data for positioning services of the Internet of Things device; the first core network functional entity performs at least one of the following : Perform mobility management on the Internet of Things device according to the first information; send the first information to the third core network functional entity, and the first information is also used by the third core network functional entity to perform session management on the Internet of Things device.
  • the operation of the first core network functional entity receiving the first information from the second core network functional entity may include: the first core network functional entity sends a first request message to the second core network functional entity, The first request message is used to request subscription data; the first core network functional entity receives the first response message sent by the second core network functional entity, and the first response message carries the subscription data.
  • the operation of the first core network functional entity receiving the first information from the second core network functional entity may include: the first core network functional entity contracts the second core network functional entity for the third Internet of Things device. An event; when the first event satisfies the first reporting condition, the first core network functional entity receives the subscription data sent by the second core network functional entity.
  • the above method may further include: the first core network functional entity receives a second request message sent by the Internet of Things device, the second request message carries a first device identifier, and the first device identifier is used to indicate the object.
  • the first core network functional entity receives a second request message sent by the Internet of Things device, the second request message carries a first device identifier, and the first device identifier is used to indicate the object. Internet-connected devices.
  • the second request message may be a registration request message.
  • the operation of the first core network functional entity sending the first information to the third core network functional entity may include: the first core network functional entity sending a third request message to the third core network functional entity,
  • the third request message carries contract data.
  • the third request message may be a session management context creation request message.
  • the present disclosure provides a management method for Internet of Things devices.
  • This method can be applied to third core network equipment.
  • the above method includes: the third core network functional entity receives the first information, the first information includes the contract data of the Internet of Things device for positioning service; the third core network functional entity performs session management on the Internet of Things device according to the first information.
  • the operation of the third core network functional entity receiving the first information may include: the third core network functional entity receives a third request message from the first core network functional entity, and the third request message carries the contract data.
  • the third request message may be a session management context creation request message.
  • the operation of the third core network functional entity receiving the first information may include: the third core network functional entity signs a second event of the Internet of Things device to the first core network functional entity; when the second event satisfies In the case of the second reporting condition, the third core network functional entity receives the contract data sent by the first core network functional entity.
  • the operation of the third core network functional entity receiving the first information may include: the third core network functional entity sends a fourth request message to the second core network functional entity, and the fourth request message is used to request a subscription. data; the third core network functional entity receives a fourth response message sent by the second core network functional entity, and the fourth response message carries contract data.
  • the operation of the third core network functional entity receiving the first information may include: the third core network functional entity signs a third event of the Internet of Things device to the second core network functional entity; when the third event satisfies In the case of the third reporting condition, the third core network functional entity receives the contract data sent by the second core network functional entity.
  • the present disclosure provides a management device for Internet of Things devices.
  • the device may be the first core network functional entity or a chip or system-on-chip therein, or may be a functional module in the first core network functional entity for implementing the methods described in the above aspects.
  • the device can realize the functions performed by the first core network functional entity in the above aspects, and these functions can be realized by hardware executing corresponding software.
  • These hardware or software include one or more modules corresponding to the above functions.
  • the above device includes: a receiving module configured to receive first information from the second core network functional entity, where the first information includes subscription data for positioning services of the Internet of Things device.
  • the device also includes at least one of the following: a processing module configured to perform mobility management on the Internet of Things device according to the first information; a sending module configured to send the first information to the third core network functional entity, the first information It is also used by the third core network functional entity to perform session management on IoT devices.
  • the sending module may also be configured to: send a first request message to the second core network function entity, where the first request message is used to request subscription data; the receiving module may be configured to: receive the second core network function entity The first response message sent by the entity carries the contract data.
  • the sending module may be configured to: contract the Internet of Things device to the second core network functional entity for the first time; the receiving module may be configured to: when the first event satisfies the first reporting condition, receive Contract data sent by the second core network functional entity.
  • the receiving module may also be configured to: receive a second request message sent by the Internet of Things device, where the second request message carries a first device identifier, and the first device identifier is used to indicate the Internet of Things device.
  • the second request message may be a registration request message.
  • the sending module may be configured to: send a third request message to the third core network functional entity, where the third request message carries the subscription data.
  • the third request message may be a session management context creation request message.
  • the present disclosure provides a management device for Internet of Things devices.
  • the device may be a third core network functional entity or a chip or a system-on-chip therein, or may be a functional module in the third core network functional entity for implementing the methods described in the above aspects.
  • the device can realize the functions performed by the third core network functional entity in the above aspects, and these functions can be realized by hardware executing corresponding software.
  • These hardware or software include one or more modules corresponding to the above functions.
  • the above-mentioned device includes: a receiving module configured to receive first information, where the first information includes contract data for positioning services of the Internet of Things device; and a processing module configured to perform session management on the Internet of Things device according to the first information.
  • the receiving module may be configured to: receive a third request message from the first core network functional entity, where the third request message carries the subscription data.
  • the third request message may be a session management context creation request message.
  • the above device may further include: a sending module configured to sign a second event of the Internet of Things device to the first core network functional entity; the receiving module may be configured to: when the second event satisfies the second reporting condition In the case of receiving the subscription data sent by the first core network functional entity.
  • the above device may further include: a sending module configured to send a fourth request message to the second core network functional entity, where the fourth request message is used to request subscription data; the receiving module may be configured to: receive the third A fourth response message sent by the second core network functional entity, the fourth response message carries contract data.
  • the above device may further include: a sending module configured to sign a third event of the Internet of Things device to the second core network functional entity; the receiving module may be configured to: when the third event satisfies the third reporting condition In the case of receiving the subscription data sent by the second core network functional entity.
  • the present disclosure provides an electronic device.
  • the electronic device includes: a memory; a processor, connected to the memory, and configured to execute computer-executable instructions stored on the memory to implement any one of the first aspect, the second aspect, and possible implementations thereof. Methods.
  • the present disclosure provides a computer storage medium.
  • the computer storage medium stores computer-executable instructions. After being executed by the processor, the computer-executable instructions can implement the method described in any one of the first aspect, the second aspect and their possible implementations.
  • the core network functional entity in the mobile network can obtain the contract data of the Internet of Things device, and the contract data is contract data for positioning services; the core network functional entity can manage the Internet of Things device based on the contract data. , or sent to another core network functional entity for management of IoT devices.
  • the mobile network can support IoT devices for location services, thereby enabling location services for IoT devices.
  • Figure 1 is a schematic structural diagram of a communication system in an embodiment of the present disclosure
  • Figure 2 is a schematic flowchart of a management method for an Internet of Things device in an embodiment of the present disclosure
  • FIG. 3 is a schematic flowchart of another management method for Internet of Things devices in an embodiment of the present disclosure
  • Figure 4 is a schematic structural diagram of a management device for an Internet of Things device in an embodiment of the present disclosure
  • FIG. 5 is a schematic structural diagram of another management device for Internet of Things equipment in an embodiment of the present disclosure.
  • Figure 6 is a schematic structural diagram of a core network functional entity in an embodiment of the present disclosure.
  • first, second, third, etc. may be used to describe various elements in the embodiments of the present disclosure, these elements should not be limited to these terms. These terms are only used to distinguish elements of the same type from each other. For example, without departing from the scope of the embodiments of the present disclosure, a “first” element may also be called a “second” element, and similarly, a “second” element may also be called a “first” element.
  • the word “if” as used herein may be interpreted as “when” or “when” or “in response to determining.”
  • IoT devices can be of different types and can provide various services in different scenarios.
  • IoT devices there is a type of IoT devices that can be used to implement positioning functions.
  • This type of IoT device may also be called an IoT positioning device.
  • IoT devices some IoT devices are only used to implement positioning functions.
  • This part of IoT devices may include, for example: GPS location tracking devices, RFID tracking devices, etc.
  • mobile networks also need to be able to support positioning services for IoT devices to further implement location-based services.
  • the core network functional entity in the mobile network should be able to manage IoT devices.
  • Embodiments of the present disclosure provide a communication system that can support positioning services for Internet of Things devices.
  • the communication system may be a 5G communication system or a future evolution communication system.
  • access network functional entities which can also be described as access network equipment, access network elements, access network functional components, access network functional modules, etc.
  • core network Function (network function, NF) entity can also be described as core network equipment, core network element, core network functional component, core network functional module, etc.
  • At least one core network functional entity is located in the core network (ie 5GC).
  • FIG. 1 is a schematic structural diagram of a communication system in an embodiment of the present disclosure.
  • the above-mentioned communication system 100 may include a 5G access network (AN) and a 5G core network (5GC).
  • the 5G access network may include a next generation radio access network (NG RAN) 101.
  • the NG RAN 101 communicates with the terminal device 102 through the Uu interface.
  • the 5G core network 103 may include: access and mobility management function (AMF) 1031, user plane function (UPF) 1032, session management function (SMF) 1033, policy Policy control function (PCF) 1034, unified data management (UDM) 1035, etc.
  • AMF access and mobility management function
  • UPF user plane function
  • SMF session management function
  • PCF policy Policy control function
  • UDM unified data management
  • the above communication system may also include other network elements, which is not specifically limited in the embodiment of the present disclosure.
  • terminal equipment can access the 5G core network through the third generation partnership project (3GPP) technology. Specifically, terminal equipment can access the 5G core network through 3GPP access network equipment.
  • 3GPP third generation partnership project
  • UDM 1035 has the function of unified data management. Mainly responsible for managing contract data, user access authorization and other functions.
  • PCF 1034 has a policy control function and is mainly responsible for policy decisions related to billing strategies for sessions and business flows, quality of service (QoS) bandwidth guarantees and policies, etc.
  • PCF 1034 connected to AMF 1031 and SMF 1033 can correspond to AM PCF (PCF for access and mobility control) and SM PCF (PCF for session management) respectively.
  • AM PCF and SM PCF may not be The same PCF entity.
  • SMF 1033 has a session management function, and mainly performs session management, execution of control policies issued by PCF 1034, selection of UPF 1032, Internet Protocol (IP) address allocation of terminal device 102 and other functions.
  • PCF 1034 execution of control policies issued by PCF 1034
  • UPF 1032 selection of UPF 1032
  • IP Internet Protocol
  • AMF 1031 has access and mobility management functions, mainly performing mobility management, access authentication/authorization and other functions. In addition, it is also responsible for transmitting user policies between the terminal device 102 and the PCF 1034.
  • UPF 1032 is the user plane functional entity, which serves as the interface with the data network and completes functions such as user plane (UP) data forwarding, session/flow level-based billing statistics, bandwidth limitation, etc.
  • UP user plane
  • N7 The interface between PCF 1034 and SMF 1033, used to issue control policies for packet data unit (packet data unit, PDU) session granularity and business data flow granularity.
  • packet data unit packet data unit, PDU
  • N3 Communication interface between UPF 1032 and NG RAN 101.
  • N15 The interface between PCF 1034 and AMF 1031, used to deliver terminal device policies and access control related policies.
  • N4 The interface between SMF 1033 and UPF 1032. It is used to transfer information between the control plane and UP, including controlling the distribution of forwarding rules, QoS control rules, traffic statistics rules, etc. for UP and reporting of UP information.
  • N11 The interface between SMF 1033 and AMF 1031, used to transfer PDU session tunnel information between NG RAN 101 and UPF 1032, transfer control messages sent to terminal equipment, transfer wireless resource control information sent to NG RAN 101, etc. .
  • N2 The interface between AMF 1031 and NG RAN 101, used to transmit wireless bearer control information from the core network side to NG RAN 101, etc.
  • N1 The interface between AMF 1031 and terminal device 102, has nothing to do with access, and is used to transmit QoS control rules to terminal device 102, etc.
  • N8 The interface between AMF 1031 and UDM 1035, used for AMF 1031 to obtain access and mobility management-related subscription data and authentication data from UDM 1034, and for AMF 1031 to register terminal device 102 current mobility management-related information with UDM 1034, etc. .
  • N10 The interface between SMF 1033 and UDM 1034, used for SMF 1033 to obtain session management-related contract data from UDM 1034, and for SMF 1033 to register terminal device 102 current session-related information with UDM 1034.
  • the above terminal device may be a terminal device with a wireless communication function, and may also be called user equipment (UE).
  • Terminal devices can be deployed on land, including indoors or outdoors, handheld, wearable or vehicle-mounted; they can also be deployed on water (such as ships, etc.); they can also be deployed in the air (such as aircraft, balloons, satellites, etc.).
  • the above-mentioned terminal equipment can be a mobile phone (mobile phone), tablet computer (Pad), computer with wireless transceiver function, virtual reality (VR) terminal device, augmented reality (AR) terminal device, industrial control (industrial) Wireless terminals in control, wireless terminals in self-driving, wireless terminals in remote medical, wireless terminals in smart grid, and transportation safety Wireless terminals, wireless terminals in smart cities, wireless terminals in smart homes, etc.
  • the terminal device may also be a handheld device with wireless communication capabilities, a vehicle-mounted device, a wearable device, a computing device, or other processing device connected to a wireless modem, etc.
  • the terminal device can also be called by different names in different networks, for example: terminal device, access terminal, subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile equipment, user terminal , terminal, wireless communication equipment, user agent or user device, cellular phone, cordless phone, session initiation protocol (session initiation protocol, SIP) phone, wireless local loop (wireless local loop, WLL) station, personal digital processing (personal digital) assistant, PDA), 5G network or terminal equipment in future evolution networks, etc.
  • terminal device access terminal, subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile equipment, user terminal , terminal, wireless communication equipment, user agent or user device, cellular phone, cordless phone, session initiation protocol (session initiation protocol, SIP) phone, wireless local loop (wireless local loop, WLL) station, personal digital processing (personal digital) assistant, PDA), 5G network or terminal equipment in future evolution networks, etc.
  • SIP session initiation protocol
  • WLL wireless local loop
  • PDA personal digital processing
  • the above-mentioned access network equipment may be equipment used by the access network side to support terminal access to the wireless communication system.
  • it can be the next generation base station (next generation NodeB, gNB), transmission reception point (TRP), relay node (relay node), access point (AP) in the 5G access technology communication system )wait.
  • next generation base station next generation NodeB, gNB
  • TRP transmission reception point
  • relay node relay node
  • AP access point
  • each device is only exemplary, and not all functions of each device are necessary when used in embodiments of the present disclosure. All or part of the equipment of the core network may be physical equipment or virtualized equipment, which is not limited here. Of course, the communication system in the embodiment of the present disclosure may also include other devices not shown in Figure 1, which are not limited here.
  • embodiments of the present disclosure provide a management method for Internet of Things devices.
  • FIG. 2 is a schematic flowchart of a management method for an Internet of Things device in an embodiment of the present disclosure.
  • This communication method can be applied to the above communication system.
  • the terminal device may be a UE
  • the access network functional entity may be a gNB
  • the first core network functional entity may be an AMF
  • the second core network functional entity may be a UDM.
  • the above method may include: S201 to S204.
  • AMF receives a registration request from the UE.
  • the registration request may carry at least one of the following: registration type, UE identification, and security parameters. It should be noted that the registration request may also carry other information, which is not specifically limited in the embodiments of this application.
  • Registration type can be used to represent the type of registration.
  • the registration type may include: initial registration, mobility registration update, periodic registration update, emergency registration, or other types.
  • the UE identity (which may also be called the first device identity) may be SUCI, 5G-GUTI or PEI, and is used to identify the terminal device.
  • Security parameters can be used for authentication and integrity protection.
  • the registration request is sent by the UE to the AMF via the gNB.
  • the registration request may be carried in a registration request message (which may also be called a second request message).
  • the gNB may forward the registration request from the UE to the AMF.
  • the UE can send a registration request to the gNB through the Uu interface; then, the gNB can send a registration request to the AMF through the N2 interface.
  • the registration request sent by the UE to the gNB can be carried in the AN message; and the registration request sent by the gNB to the AMF can be carried in the N2 message.
  • the registration request message may include an AN message and an N2 message.
  • the RAN message and the N2 message may also carry other information, which is not specifically limited in the embodiment of the present application.
  • the gNB may transparently transmit the registration request sent by the UE to the AMF.
  • the UE can send a registration request to the AMF through the N1 interface.
  • the registration request message may be an N1 message.
  • the registration request can be carried in the N1 message.
  • the N1 message may also carry other information, which is not specifically limited in the embodiments of this application.
  • AMF retrieves the first information.
  • the first information may include the subscription data of the UE.
  • the AMF may first determine whether the UE's information is stored locally and/or whether the local first information is the latest. If so, the AMF can directly obtain the first information locally. If not, the AMF may obtain the first information from another core network functional entity.
  • the UE's subscription data may be access and mobility subscription data.
  • the access and mobility subscription data may include subscription data of the IoT device dedicated to positioning.
  • the access and mobility subscription data may include subscription data dedicated to positioning for the IoT device, and may also include other subscriptions. data.
  • the first information can be stored on UDM.
  • the AMF can retrieve the first information through the service between the AMF and the UDM.
  • the AMF retrieving the first information may include: the AMF may send a first request message to the UDM; in response to the first request message, the UDM may send a first response message to the AMF.
  • the first request message may be used to request subscription data.
  • the first response message may carry contract data.
  • the subscription data is obtained locally by UDM in response to the first response message.
  • the AMF may retrieve the first information through the Nudm_SDM_Get service.
  • the first request message may be a Nudm_SDM_Get request message
  • the first response message may be a Nudm_SDM_Get response message.
  • the AMF may retrieve the first information through the Nudm_SDM_Subscribe service.
  • the first request message may be a Nudm_SDM_Subscribe request message
  • the first response message may be a Nudm_SDM_Subscribe response message.
  • the AMF retrieving the first information may include: the AMF may subscribe to the UDM for the first event of the UE; and if the first event satisfies the first reporting condition, the AMF may receive the subscription data from the UDM.
  • the first event may be time-triggered.
  • the first reporting condition may be that the first time period is reached after the UDM obtains the contract data.
  • the UDM may send the subscription data to the AMF.
  • the first reporting condition may be the second duration. In this case, the UDM sends the subscription data to the AMF each time a timer in the UDM reaches the second duration.
  • the first event may be event triggered.
  • the first reporting condition may be that UDM obtains contract data.
  • the UDM can send the subscription data to the AMF.
  • the first information may also include at least one of the following: SMF selection subscription data, UE context in SMF data, location service mobile origin (LCS mobile origin, location service mobile origin). It should be noted that the first information may also include other information, which is not specifically limited in the embodiments of the present application.
  • AMF notifies the UE that the registration is completed.
  • the AMF may notify the UE that the registration is completed.
  • the AMF can send a registration response to the UE to notify the UE that the registration is completed.
  • the registration response can carry at least one of the following: 5G-GUTI, registration area.
  • the registration area is used to represent the available tracking area, and can include allowed NSSAI (network slice selection assistance information, network slice selection assistance information) and S-NSSAI (single network slice selection assistance information, single network slice selection assistance information).
  • NSSAI network slice selection assistance information
  • S-NSSAI single network slice selection assistance information, single network slice selection assistance information
  • the registration response can be carried in the registration accept message (registration accept message) (which can also be called the second response message). It should be noted that the registration acceptance message may also carry other information, which is not specifically limited in the embodiments of this application.
  • the AMF can authenticate and authorize the UE before the AMF notifies the UE that the registration is complete.
  • the AMF performs mobility management on the UE.
  • the AMF can perform mobility management on the UE.
  • the AMF may perform mobility management on the UE according to the first information. It should be noted that the AMF can also perform other management on the UE, which is not specifically limited in the embodiments of this application.
  • FIG. 3 is a schematic flowchart of another management method for an Internet of Things device in an embodiment of the present disclosure.
  • This communication method can be applied to the above communication system.
  • the terminal device may be a UE
  • the access network functional entity may be a gNB
  • the first core network functional entity may be an AMF
  • the second core network functional entity may be a UDM
  • the third core network functional entity may be a UDM.
  • the entity can be SMF.
  • the above method may include: S301 to S310.
  • the UE sends a PDU session establishment request to the AMF.
  • the PDU session establishment request (PDU session establishment request) is used to initiate the PDU session establishment process.
  • the UE can send a NAS message (which can also be called a second request message) to the AMF, and the NAS message carries a PDU session establishment request.
  • a NAS message (which can also be called a second request message)
  • the NAS message carries a PDU session establishment request.
  • the PDU session establishment request may be carried in a NAS message, such as a PDU session establishment request message.
  • the PDU session establishment request message is encapsulated in the N1SM container (N1SM container) in the uplink non-access layer message (UL NAS message).
  • N1SM container N1SM container
  • UL NAS message uplink non-access layer message
  • other information may also be included in the UL NAS message, and this embodiment of the present disclosure does not limit this.
  • AMF selects SMF.
  • the AMF After receiving the PDU session establishment request in S302, the AMF selects the SMF according to the PDU session establishment request. Specific details can be found in 3GPP TS 23.502 and will not be described in detail here.
  • S303 AMF sends a session management context creation request to SMF.
  • the session management context creation request (which may also be called the third request message) is used to request the creation of a PDU session.
  • the AMF can store the first information.
  • the first information includes subscription data of the UE.
  • the subscription data may be access and mobility subscription data.
  • the first information may be carried in the session management context creation request message, or may be sent by the AMF to the SMF in other ways.
  • the subscription data may include subscription data of the Internet of Things device dedicated to positioning.
  • the subscription data may include subscription data dedicated to positioning of the IoT device, and may also include other subscription data.
  • the contract data can be obtained in advance by AMF.
  • the AMF can obtain subscription data from the UDM during the UE's registration process.
  • the first information may be carried in the session management context creation request message.
  • AMF may send an Nsmf_PDUSession_CreateSMContext request to SMF.
  • session management context creation request message can also carry other information, such as SUPI, DNN (data network name, data network name), S-NSSAI, N1 SM container.
  • the SMF may sign the UE's second event to the AMF.
  • the AMF may send the UE's subscription data to the SMF.
  • the second event may be time-triggered.
  • the second reporting condition may be that the third period of time has passed since AMF obtained the contract data.
  • the AMF may send the subscription data to the SMF.
  • the second reporting condition may be the fourth duration. In this case, the AMF sends the subscription data to the SMF each time a timer in the AMF reaches the fourth duration.
  • the second event may be event triggered.
  • the second reporting condition may be that the AMF obtains the contract data. In this case, when the AMF obtains the subscription data of the UE, the AMF may send the subscription data to the SMF.
  • the second reporting condition may be that the AMF receives a request from the SMF. In this case, the AMF may send the subscription data to the SMF when the AMF receives the request.
  • S304 SMF retrieves the first information.
  • the first information may include the subscription data of the UE.
  • the AMF can first determine whether the session management subscription data corresponding to SUPI, DNN, and S-NSSAI of HPLMN (home public land mobile network, local public land mobile network) is available. If so, use the session management subscription data. If not, it means that SMF needs to obtain new session management subscription data.
  • SMF can retrieve the first information.
  • the subscription data in the first information is session subscription data.
  • SMF can retrieve the first information through the service between SMF and UDM.
  • the SMF retrieving the first information may include: the SMF may send a fourth request message to the UDM; in response to the fourth request message, the UDM may send a fourth response message to the SMF.
  • the fourth request message may be used to request subscription data.
  • the fourth response message may carry contract data.
  • the subscription data is obtained locally by UDM in response to the fourth response message.
  • the SMF may retrieve the first information through the Nudm_SDM_Get service.
  • the fourth request message may be a Nudm_SDM_Get request message
  • the fourth response message may be a Nudm_SDM_Get response message.
  • the SMF may retrieve the first information through the Nudm_SDM_Subscribe service.
  • the fourth request message may be a Nudm_SDM_Subscribe request message
  • the fourth response message may be a Nudm_SDM_Subscribe response message.
  • the SMF retrieving the first information may include: the SMF may subscribe to the UDM for the third event of the UE; and if the third event satisfies the third reporting condition, the SMF may receive the subscription data from the UDM.
  • the third event may be time triggered.
  • the third reporting condition may be that the fifth time period has passed since UDM obtained the contract data.
  • the UDM may send the subscription data to the SMF.
  • the third reporting condition may be the sixth duration. In this case, the UDM sends the subscription data to the SMF every time a timer in the UDM reaches the sixth duration.
  • the third event may be event triggered.
  • the third reporting condition may be that UDM obtains contract data.
  • the UDM can send the subscription data to the SMF.
  • the first information may be stored on the UDM, or may be obtained by the UDM from the UDR.
  • UDM can obtain subscription data from UDR through Nudr_DM_Query service or Nudr_DM_subscribe service.
  • S304 is not necessary. As mentioned above, S304 needs to be executed only when the AMF can first determine that the session management subscription data corresponding to HPLMN's SUPI, DNN, and S-NSSAI are unavailable.
  • S305 SMF sends a session management context creation response to AMF.
  • the session management context creation response (also called the third response message) is used to indicate that SMF successfully created the session management context (SM context).
  • the session management context creation response carries the session management context representation (SM context ID), which is used to identify the created session management context.
  • SM context ID session management context representation
  • S306 SMF initiates the N4 session establishment process to UPF.
  • the N4 session establishment process is used to establish a PDU session for the UE.
  • the N4 session establishment process may specifically include: SMF sends an N4 session establishment request to UPF, and receives an N4 session establishment response from UPF.
  • SMF sends Namf_Communication_N1N2Message Transfer to AMF.
  • Namf_Communication_N1N2Message Transfer carries the IP address assigned to the UE. This IP address is used to implement the UE's PDU session.
  • AMF sends an N2 PDU session request to gNB.
  • N2 PDU session request (N2 PDU session request) can be carried in the NAS message.
  • the N2 PDU session request includes the IP address assigned to the UE.
  • S309 gNB notifies the UE that the PDU session establishment is completed.
  • gNB notifies the completion of PDU session establishment by sending a PDU session establishment accept message.
  • the PDU session establishment accept message may be carried in the NAS message forwarded by the gNB and includes the IP address assigned to the UE.
  • S310 SMF performs session management on the UE.
  • SMF can perform session management on the UE.
  • the SMF can perform session management on the UE according to the first information. It should be noted that the SMF can also perform other management on the UE, which is not specifically limited in the embodiments of this application.
  • the core network functional entity in the mobile network can obtain the contract data of the Internet of Things device, and the contract data is the contract data for positioning service; the core network functional entity can perform the Internet of Things device based on the contract data. management, or sent to another core network functional entity for management of IoT devices.
  • the mobile network can support IoT devices for location services, thereby enabling location services for IoT devices.
  • the present disclosure provides a management method for Internet of Things devices.
  • This method can be applied to the first core network device, for example, the AMF.
  • the above method includes: the first core network functional entity receives first information from the second core network functional entity, where the first information includes contract data for positioning services of the Internet of Things device; the first core network functional entity performs at least one of the following : Perform mobility management on the Internet of Things device according to the first information; send the first information to the third core network functional entity, and the first information is also used by the third core network functional entity to perform session management on the Internet of Things device.
  • the operation of the first core network functional entity receiving the first information from the second core network functional entity may include: the first core network functional entity sends a first request message to the second core network functional entity, The first request message is used to request subscription data; the first core network functional entity receives the first response message sent by the second core network functional entity, and the first response message carries the subscription data.
  • the operation of the first core network functional entity receiving the first information from the second core network functional entity may include: the first core network functional entity contracts the second core network functional entity for the third Internet of Things device. An event; when the first event satisfies the first reporting condition, the first core network functional entity receives the subscription data sent by the second core network functional entity.
  • the above method may further include: the first core network functional entity receives a second request message sent by the Internet of Things device, the second request message carries a first device identifier, and the first device identifier is used to indicate the object.
  • the first core network functional entity receives a second request message sent by the Internet of Things device, the second request message carries a first device identifier, and the first device identifier is used to indicate the object. Internet-connected devices.
  • the second request message may be a registration request message.
  • the operation of the first core network functional entity sending the first information to the third core network functional entity may include: the first core network functional entity sending a third request message to the third core network functional entity,
  • the third request message carries contract data.
  • the third request message may be a session management context creation request message.
  • the present disclosure provides a management method for Internet of Things devices.
  • This method can be applied to third core network equipment, for example, SMF.
  • the above method includes: the third core network functional entity receives the first information, the first information includes the contract data of the Internet of Things device for positioning service; the third core network functional entity performs session management on the Internet of Things device according to the first information.
  • the operation of the third core network functional entity receiving the first information may include: the third core network functional entity receives a third request message from the first core network functional entity, and the third request message carries the contract data.
  • the third request message may be a session management context creation request message.
  • the operation of the third core network functional entity receiving the first information may include: the third core network functional entity signs a second event of the Internet of Things device to the first core network functional entity; when the second event satisfies In the case of the second reporting condition, the third core network functional entity receives the contract data sent by the first core network functional entity.
  • the operation of the third core network functional entity receiving the first information may include: the third core network functional entity sends a fourth request message to the second core network functional entity, and the fourth request message is used to request a subscription. data; the third core network functional entity receives a fourth response message sent by the second core network functional entity, and the fourth response message carries contract data.
  • the operation of the third core network functional entity receiving the first information may include: the third core network functional entity signs a third event of the Internet of Things device to the second core network functional entity; when the third event satisfies In the case of the third reporting condition, the third core network functional entity receives the contract data sent by the second core network functional entity.
  • the present disclosure provides a management device for Internet of Things devices.
  • the device may be a first core network functional entity (such as an AMF) or a chip or system-on-chip therein, or may be a functional module in the first core network functional entity for implementing the methods described in the above aspects.
  • the device can realize the functions performed by the first core network functional entity in the above aspects, and these functions can be realized by hardware executing corresponding software.
  • These hardware or software include one or more modules corresponding to the above functions.
  • FIG. 4 is a schematic structural diagram of a management device for an Internet of Things device in an embodiment of the present disclosure.
  • the above-mentioned apparatus 400 includes: a receiving module 401 configured to receive first information from the second core network functional entity, where the first information includes subscription data for positioning services of the Internet of Things device.
  • the device also includes at least one of the following: a processing module 402 configured to perform mobility management on the Internet of Things device according to the first information; a sending module 403 configured to send the first information to the third core network functional entity.
  • One information is also used by the third core network functional entity to perform session management on IoT devices.
  • the sending module 403 can also be configured to: send a first request message to the second core network functional entity, where the first request message is used to request subscription data; the receiving module 401 can be configured to: receive the second core network functional entity The first response message sent by the network function entity, the first response message carries the subscription data.
  • the sending module 403 may be configured to: contract the Internet of Things device to the second core network functional entity for the first time; the receiving module 401 may be configured to: when the first event satisfies the first reporting condition , receiving the contract data sent by the second core network functional entity.
  • the receiving module 401 may also be configured to: receive a second request message sent by the Internet of Things device, where the second request message carries a first device identifier, and the first device identifier is used to indicate the Internet of Things device.
  • the second request message may be a registration request message.
  • the sending module 403 may be configured to: send a third request message to the third core network functional entity, where the third request message carries the subscription data.
  • the third request message may be a session management context creation request message.
  • the present disclosure provides a management device for Internet of Things devices.
  • the device may be a third core network functional entity (such as SMF) or a chip or system-on-chip therein, or may be a functional module in the third core network functional entity for implementing the methods described in the above aspects.
  • the device can realize the functions performed by the third core network functional entity in the above aspects, and these functions can be realized by hardware executing corresponding software.
  • These hardware or software include one or more modules corresponding to the above functions.
  • FIG. 5 is a schematic structural diagram of another management device for Internet of Things equipment in an embodiment of the present disclosure.
  • the above-mentioned device 500 includes: a receiving module 501 configured to receive first information, where the first information includes contract data for positioning services of the Internet of Things device; a processing module 502, based on the first information, The device performs session management.
  • the receiving module 501 may be configured to: receive a third request message from the first core network functional entity, where the third request message carries subscription data.
  • the third request message may be a session management context creation request message.
  • the above-mentioned apparatus 500 may also include: a sending module 503 configured to sign a second event of the Internet of Things device to the first core network functional entity; the receiving module 501 may be configured to: when the second event satisfies the first In the case of the second reporting condition, receive the contract data sent by the first core network functional entity.
  • the above device 500 may also include: a sending module 503 configured to send a fourth request message to the second core network functional entity, where the fourth request message is used to request subscription data; the receiving module may be configured as: Receive a fourth response message sent by the second core network functional entity, where the fourth response message carries subscription data.
  • the above-mentioned apparatus 500 may also include: a sending module 503 configured to sign a third event of the Internet of Things device to the second core network functional entity; the receiving module 501 may be configured to: when the third event satisfies the third event In the case of three reporting conditions, the contract data sent by the second core network functional entity is received.
  • embodiments of the present disclosure provide a network functional entity that is consistent with the core network functional entity in one or more of the above embodiments.
  • FIG. 6 is a schematic structural diagram of a network functional entity in an embodiment of the present disclosure.
  • network functional entity 600 may include a processing component 601, which further includes one or more processors, and memory resources represented by memory 602 for storing instructions, such as applications, that may be executed by processing component 601. program.
  • An application program stored in memory 602 may include one or more modules, each of which corresponds to a set of instructions.
  • the processing component 601 is configured to execute instructions to perform any of the foregoing methods applied to the network function entity.
  • the network function entity 600 may also include a power supply component 603 configured to perform power management of the network function entity 600, a wired or wireless network interface 604 configured to connect the network function entity 600 to the network, and an input/output (I/O ) interface 605.
  • Network function entity 600 may operate based on an operating system stored in memory 602, such as Windows ServerTM, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM or similar.
  • inventions of the present disclosure also provide an electronic device.
  • the electronic device includes: a memory; a processor, connected to the memory, configured to execute computer-executable instructions stored on the memory to execute the first core network functional entity or the third core network function in one or more of the above embodiments. Entity methods.
  • embodiments of the present disclosure also provide a computer-readable storage medium. Instructions are stored in the computer-readable storage medium; when the instructions are run on the computer, they are used to execute the first step in one or more of the above embodiments.
  • embodiments of the present disclosure also provide a computer program or computer program product.
  • the computer program product When the computer program product is executed on a computer, the computer implements the first core network functional entity or the first core network functional entity in one or more of the above embodiments. Method of the third core network functional entity.

Landscapes

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

Abstract

提供涉及无线通信技术领域，尤其涉及一种物联网设备的管理方法、装置、设备和存储介质。方法包括：第一核心网功能实体接收来自第二核心网功能实体的第一信息，第一信息包括物联网设备的用于定位服务的签约数据；第一核心网功能实体执行以下至少之一：根据第一信息，对物联网设备进行移动性管理；将第一信息发送给第三核心网功能实体，第一信息还用于第三核心网功能实体对物联网设备进行会话管理。能够实现移动网络对用于定位服务的物联网设备的支持。

Description

物联网设备的管理方法、装置、设备和存储介质 技术领域
本公开涉及无线通信技术领域，尤其涉及一种物联网设备的管理方法、装置、设备和存储介质。
背景技术
物联网(internet of things，IoT)是在互联网的基础上，将各种信息传感设备与网络结合起来而形成的一个巨大网络，实现任何时间、任何地点，人、机、物的互联互通。物联网设备具有不同的类型，并且可以在不同的场景中提供各种服务。在众多类型的物联网设备中，有一类物联网设备能够用于实现定位功能。这类物联网设备也可以被称为物联网定位设备。
随着无线通信技术的不断发展，移动网络也需要能够支持物联网设备的定位服务，从而进一步实现基于位置的服务。
那么，如何在移动网络中支持用于定位服务的物联网设备是一个亟待解决的问题。
发明内容
本公开提供了一种物联网设备的管理方法、装置、设备和存储介质，以实现移动网络对用于定位服务的物联网设备的支持。
在第一方面，本公开提供一种物联网设备的管理方法。该方法可以应用于第一核心网设备。上述方法包括：第一核心网功能实体接收来自第二核心网功能实体的第一信息，第一信息包括物联网设备的用于定位服务的签约数据；第一核心网功能实体执行以下至少之一：根据第一信息，对物联网设备进行移动性管理；将第一信息发送给第三核心网功能实体，第一信息还用于第三核心网功能实体对物联网设备进行会话管理。
在一些可能的实施方式中，第一核心网功能实体接收来自第二核心网功能实体的第一信息的操作可以包括：第一核心网功能实体向第二核心网功能实体发送第一请求消息，第一请求消息用于请求签约数据；第一核心网功能实体接收第二核心网功能实体发送的第一响应消息，第一响应消息中携带有签约数据。
在一些可能的实施方式中，第一核心网功能实体接收来自第二核心网功能实体的第一信息的操作可以包括：第一核心网功能实体向第二核心网功能实体签约物联网设备的第一事件；在第一事件满足第一上报条件的情况下，第一核心网功能实体接收第二核心网功能实体发送的签约数据。
在一些可能的实施方式中，上述方法还可以包括：第一核心网功能实体接收物联网设备发送的第二请求消息，第二请求消息携带有第一设备标识，第一设备标识用于指示物联网设备。
在一些可能的实施方式中，第二请求消息可以为注册请求消息。
在一些可能的实施方式中，第一核心网功能实体将第一信息发送给第三核心网功能实体的操作可以 包括：第一核心网功能实体向第三核心网功能实体发送第三请求消息，第三请求消息携带有签约数据。
在一些可能的实施方式中，第三请求消息可以为会话管理上下文创建请求消息。
在第二方面，本公开提供一种物联网设备的管理方法。该方法可以应用于第三核心网设备。上述方法包括：第三核心网功能实体接收第一信息，第一信息包括物联网设备的用于定位服务的签约数据；第三核心网功能实体根据第一信息，对物联网设备进行会话管理。
在一些可能的实施方式中，第三核心网功能实体接收第一信息的操作可以包括：第三核心网功能实体接收来自第一核心网功能实体的第三请求消息，第三请求消息携带有签约数据。
在一些可能的实施方式中，第三请求消息可以为会话管理上下文创建请求消息。
在一些可能的实施方式中，第三核心网功能实体接收第一信息的操作可以包括：第三核心网功能实体向第一核心网功能实体签约物联网设备的第二事件；在第二事件满足第二上报条件的情况下，第三核心网功能实体接收第一核心网功能实体发送的签约数据。
在一些可能的实施方式中，第三核心网功能实体接收第一信息的操作可以包括：第三核心网功能实体向第二核心网功能实体发送第四请求消息，第四请求消息用于请求签约数据；第三核心网功能实体接收第二核心网功能实体发送的第四响应消息，第四响应消息中携带有签约数据。
在一些可能的实施方式中，第三核心网功能实体接收第一信息的操作可以包括：第三核心网功能实体向第二核心网功能实体签约物联网设备的第三事件；在第三事件满足第三上报条件的情况下，第三核心网功能实体接收第二核心网功能实体发送的签约数据。
在第三方面，本公开提供一种物联网设备的管理装置。该装置可以为第一核心网功能实体或者其中的芯片或者片上系统，还可以为第一核心网功能实体中用于实现上述各个方面所述的方法的功能模块。该装置可以实现上述各方面中第一核心网功能实体所执行的功能，这些功能可以通过硬件执行相应的软件实现。这些硬件或软件包括一个或多个上述功能相应的模块。上述装置包括：接收模块，配置为接收来自第二核心网功能实体的第一信息，第一信息包括物联网设备的用于定位服务的签约数据。所述装置还包括以下至少之一：处理模块，配置为根据第一信息，对物联网设备进行移动性管理；发送模块，配置为将第一信息发送给第三核心网功能实体，第一信息还用于第三核心网功能实体对物联网设备进行会话管理。
在一些可能的实施方式中，发送模块还可以配置为：向第二核心网功能实体发送第一请求消息，第一请求消息用于请求签约数据；接收模块可以配置为：接收第二核心网功能实体发送的第一响应消息，第一响应消息中携带有签约数据。
在一些可能的实施方式中，发送模块可以配置为：向第二核心网功能实体签约物联网设备的第一时间；接收模块可以配置为：在第一事件满足第一上报条件的情况下，接收第二核心网功能实体发送的签约数据。
在一些可能的实施方式中，接收模块还可以配置为：接收物联网设备发送的第二请求消息，第二请求消息携带有第一设备标识，第一设备标识用于指示物联网设备。
在一些可能的实施方式中，第二请求消息可以为注册请求消息。
在一些可能的实施方式中，发送模块可以配置为：向第三核心网功能实体发送第三请求消息，第三 请求消息携带有签约数据。
在一些可能的实施方式中，第三请求消息可以为会话管理上下文创建请求消息。
在第四方面，本公开提供一种物联网设备的管理装置。该装置可以为第三核心网功能实体或者其中的芯片或者片上系统，还可以为第三核心网功能实体中用于实现上述各个方面所述的方法的功能模块。该装置可以实现上述各方面中第三核心网功能实体所执行的功能，这些功能可以通过硬件执行相应的软件实现。这些硬件或软件包括一个或多个上述功能相应的模块。上述装置包括：接收模块，配置为接收第一信息，第一信息包括物联网设备的用于定位服务的签约数据；处理模块，根据第一信息，对物联网设备进行会话管理。
在一些可能的实施方式中，接收模块可以配置为：接收来自第一核心网功能实体的第三请求消息，第三请求消息携带有签约数据。
在一些可能的实施方式中，第三请求消息可以为会话管理上下文创建请求消息。
在一些可能的实施方式中，上述装置还可以包括：发送模块，配置为向第一核心网功能实体签约物联网设备的第二事件；接收模块可以配置为：在第二事件满足第二上报条件的情况下，接收第一核心网功能实体发送的签约数据。
在一些可能的实施方式中，上述装置还可以包括：发送模块，配置为向第二核心网功能实体发送第四请求消息，第四请求消息用于请求签约数据；接收模块可以配置为：接收第二核心网功能实体发送的第四响应消息，第四响应消息中携带有签约数据。
在一些可能的实施方式中，上述装置还可以包括：发送模块，配置为向第二核心网功能实体签约物联网设备的第三事件；接收模块可以配置为：在第三事件满足第三上报条件的情况下，接收第二核心网功能实体发送的签约数据。
在第五方面，本公开提供一种电子设备。该电子设备包括：存储器；处理器，与存储器连接，被配置为执行存储在存储器上的计算机可执行指令，以实现如第一方面、第二方面及其可能的实施方式中任一项所述的方法。
在第六方面，本公开提供一种计算机存储介质。该计算机存储介质存储有计算机可执行指令。计算机可执行指令被处理器执行后能够实现如第一方面、第二方面及其可能的实施方式中任一项所述的方法。
在本公开中，移动网络中的核心网功能实体可以获得物联网设备的签约数据，并且该签约数据是用于定位服务的签约数据；核心网功能实体可以基于该签约数据进行物联网设备的管理，或者发送给另一核心网功能实体进行物联网设备的管理。以此方式，移动网络能够支持用于定位服务的物联网设备，进而能够实现针对物联网设备的定位服务。
应当理解的是，本公开的第三至第六方面与本公开的第一至第二方面的技术方案一致，各方面及对应的可行实施方式所取得的有益效果相似，不再赘述。
附图说明
图1为本公开实施例中的通信系统的结构示意图；
图2为本公开实施例中的一种物联网设备的管理方法的流程示意图；
图3为本公开实施例中的另一种物联网设备的管理方法的流程示意图；
图4为本公开实施例中的一种物联网设备的管理装置的结构示意图；
图5为本公开实施例中的另一种物联网设备的管理装置的结构示意图；
图6为本公开实施例中的一种核心网功能实体的结构示意图。
具体实施方式
这里将详细地对示例性实施例进行说明，其示例表示在附图中。下面的描述涉及附图时，除非另有表示，不同附图中的相同数字表示相同或相似的要素。以下示例性实施例中所描述的实施方式并不代表与本公开实施例相一致的所有实施方式。相反，它们仅是与如所附权利要求书中所详述的、本公开实施例的一些方面相一致的装置和方法的例子。
在本公开实施例使用的术语是仅仅出于描述特定实施例的目的，而非旨在限制本公开实施例。在本公开实施例和所附权利要求书中所使用的单数形式的“一种”和“该”也旨在包括多数形式，除非上下文清楚地表示其他含义。还应当理解，本文中使用的术语“和/或”是指并包含一个或多个相关联的列出项目的任何或所有可能组合。
应当理解，尽管在本公开实施例可能采用术语“第一”、“第二”、“第三”等来描述各种元素，但这些元素不应限于这些术语。这些术语仅用来将同一类型的元素彼此区分开。例如，在不脱离本公开实施例范围的情况下，“第一”元素也可以被称为“第二”元素，类似地，“第二”元素也可以被称为“第一”元素。取决于语境，如在此所使用的词语“如果”可以被解释成为“在……时”或“当……时”或“响应于确定”。
进一步地，在本公开实施例的描述中，“和/或”仅仅是一种描述关联对象的关联关系，表示可以存在三种关系。例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，在本公开实施例的描述中，“多个”可以指两个或多于两个。
物联网是在互联网的基础上，将各种信息传感设备与网络结合起来而形成的一个巨大网络，实现任何时间、任何地点，人、机、物的互联互通。作为一种终端设备，物联网设备可以具有不同的类型，并且可以在不同的场景中提供各种服务。在众多类型的物联网设备中，有一类物联网设备能够用于实现定位功能。这类物联网设备也可以被称为物联网定位设备。实际上，在这类物联网设备中，一部分物联网设备仅仅用于实现定位功能。这一部分的物联网设备例如可以包括：GPS位置追踪设备、RFID追踪设备等。这些物联网设备通过连接到网关等接入设备，可以将自身位置进行上报，从而实现定位功能。此外，另一部分物联网设备在实现定位功能的同时，也能够提供其他功能。
随着无线通信技术的不断发展，移动网络也需要能够支持物联网设备的定位服务，从而进一步实现基于位置的服务。为了能够对物联网设备的定位服务进行支持，移动网络中的核心网功能实体应当能够对物联网设备进行管理。
本公开实施例提供一种通信系统，该通信系统能够支持实现物联网设备的定位服务。该通信系统可以是5G通信系统或未来演进通信系统。在该通信系统的架构中，存在终端、接入网功能实体(也可以 描述为接入网设备、接入网网元、接入网功能组件、接入网功能模块等)以及至少一个核心网功能(network function，NF)实体(也可以描述为核心网设备、核心网网元、核心网功能组件、核心网功能模块等)。至少一个核心网功能实体位于核心网(即5GC)中。
图1为本公开实施例中的通信系统的结构示意图。如图1所示，上述通信系统100可以包括5G接入网(AN)和5G核心网(5GC)。其中，5G接入网可以包括下一代无线接入网(next generation radio access network，NG RAN)101，NG RAN 101通过Uu接口与终端设备102通信。5G核心网103可以包括：接入和移动性管理功能(access and mobility management function，AMF)1031、用户面功能(user plane function，UPF)1032、会话管理功能(session management function，SMF)1033、策略控制功能(policy control function，PCF)1034、统一数据管理(unified data management，UDM)1035等。
在本公开实施例中，上述通信系统还可以包括其他网元，本公开实施例对此不作具体限定。
其中，在上述通信系统中，终端设备可以通过第三代伙伴计划(3rd generation partnership project，3GPP)技术接入5G核心网。具体的，终端设备可以通过3GPP接入网设备接入5G核心网。
在上述通信系统中，UDM 1035具有统一数据管理的功能。主要负责管理签约数据、用户接入授权等功能。
PCF 1034具有策略控制功能，主要负责针对会话、业务流的计费策略、服务质量(quality of service，QoS)带宽保障及策略等相关的策略决策。该架构中，与AMF 1031和SMF 1033所连接的PCF 1034可以分别对应AM PCF(PCF for access and mobility control)和SM PCF(PCF for session management)，在实际部署场景中AM PCF和SM PCF可能不是同一个PCF实体。
SMF 1033具有会话管理功能，主要进行会话管理、PCF 1034下发控制策略的执行、UPF 1032的选择、终端设备102的互联网协议(internet protocol，IP)地址分配等功能。
AMF 1031具有接入和移动性管理功能，主要进行移动性管理、接入鉴权/授权等功能。此外，还负责在终端设备102与PCF 1034间传递用户策略。
UPF 1032为用户面功能实体，作为和数据网络的接口，完成用户面(UP)数据转发、基于会话/流级的计费统计，带宽限制等功能。
其中各接口功能描述如下：
N7：PCF 1034与SMF 1033之间的接口，用于下发分组数据单元(packet data unit，PDU)会话粒度以及业务数据流粒度的控制策略。
N3：UPF 1032与NG RAN 101之间的通信接口。
N15：PCF 1034与AMF 1031之间的接口，用于下发终端设备策略及接入控制相关策略。
N4：SMF 1033与UPF 1032之间的接口，用于控制面与UP之间传递信息，包括控制面向UP的转发规则、QoS控制规则、流量统计规则等的下发以及UP的信息上报。
N11：SMF 1033与AMF 1031之间的接口，用于传递NG RAN 101和UPF 1032之间的PDU会话隧道信息、传递发送给终端设备的控制消息、传递发送给NG RAN 101的无线资源控制信息等。
N2：AMF 1031与NG RAN 101之间的接口，用于传递核心网侧至NG RAN 101的无线承载控制信息等。
N1：AMF 1031与终端设备102之间的接口，与接入无关，用于向终端设备102传递QoS控制规则等。
N8：AMF 1031与UDM 1035间的接口，用于AMF 1031向UDM 1034获取接入与移动性管理相关签约数据与鉴权数据，以及AMF 1031向UDM 1034注册终端设备102当前移动性管理相关信息等。
N10：SMF 1033与UDM 1034间的接口，用于SMF 1033向UDM 1034获取会话管理相关签约数据，以及SMF 1033向UDM 1034注册终端设备102当前会话相关信息等。
上述终端设备可以是一种具有无线通信功能的终端设备，也可以称为用户设备(user equipment，UE)。终端设备可以部署在陆地上，包括室内或室外、手持、可穿戴或车载；也可以部署在水面上(如轮船等)；还可以部署在空中(例如飞机、气球和卫星上等)。上述终端设备可以是手机(mobile phone)、平板电脑(Pad)、带无线收发功能的电脑、虚拟现实(virtual reality，VR)终端装置、增强现实(augmented reality，AR)终端装置、工业控制(industrial control)中的无线终端、无人驾驶(self-driving)中的无线终端、远程医疗(remote medical)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端等等。终端设备也可以是具有无线通信功能的手持设备、车载设备、可穿戴设备、计算设备或连接到无线调制解调器的其它处理设备等。可选的，在不同的网络中终端装置还可以叫做不同的名称，例如：终端装置、接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置、蜂窝电话、无绳电话、会话启动协议(session initiation protocol，SIP)电话、无线本地环路(wireless local loop，WLL)站、个人数字处理(personal digital assistant，PDA)、5G网络或未来演进网络中的终端设备等。
上述接入网设备可以为接入网侧用于支持终端接入无线通信系统的设备。例如，可以是5G接入技术通信系统中的下一代基站(next generation NodeB，gNB)、发送接收点(transmission reception point，TRP)、中继节点(relay node)、接入点(access point，AP)等。
需要说明的是，在图1所示的通信系统中，各设备的功能以及接口仅为示例性的，各个设备在应用于本公开实施例中时，并非全部功能都是必需的。核心网的全部或者部分设备可以是物理上的实体设备，也可以是虚拟化的设备，在此不做限定。当然，本公开实施例中的通信系统还可以包括未在图1中示出的其他设备，在此不做限定。
为了解决上述问题，结合上述通信系统，本公开实施例提供一种物联网设备的管理方法。
图2为本公开实施例中的一种物联网设备的管理方法的流程示意图。该通信方法可以应用于上述通信系统中。示例性的，如图2所示，终端设备可以为UE，接入网功能实体可以为gNB，第一核心网功能实体可以为AMF，第二核心网功能实体可以为UDM。上述方法可以包括：S201至S204。
S201，AMF接收来自UE的注册请求。
其中，注册请求可以携带有以下至少之一：注册类型，UE标识，安全性参数。需要注意的是，注册请求还可以携带有其他信息，本申请实施例对此不作具体限定。
注册类型可以用于表示注册的类型。例如，注册类型可以包括：初始注册(initial registration)、移动性注册更新(mobility registration update)、周期性注册更新(periodic registration update)、紧急注册 (emergency registration)或者其他类型。UE标识(也可以称为第一设备标识)可以是SUCI或5G-GUTI或PEI，用于标识终端设备。安全性参数可以用于认证和完整性保护。
在实际应用中，注册请求是由UE经由gNB发送给AMF的。注册请求可以携带在注册请求消息(也可以称为第二请求消息)中。
在一实施例中，gNB可以将来自UE的注册请求转发给AMF。具体来说，UE可以通过Uu接口向gNB发送注册请求；之后，gNB可以通过N2接口向AMF发送注册请求。在此情况下，UE向gNB发送的注册请求可以携带在AN消息中；并且gNB向AMF发送的注册请求可以携带在N2消息中。此时，注册请求消息可以包括AN消息和N2消息。需要注意的是，RAN消息和N2消息中分别还可以携带有其他信息，本申请实施例对此不作具体限定。
在另一实施例中，gNB可以对UE发送给AMF的注册请求进行透传。具体来说，UE可以通过N1接口向AMF发送注册请求。此时，注册请求消息可以是N1消息。在此情况下，注册请求可以携带在N1消息中。需要注意的是，N1消息中还可以携带有其他信息，本申请实施例对此不作具体限定。
S202，AMF检索第一信息。
其中，第一信息可以包括UE的签约数据。
可以理解的，在接收到来自UE的注册请求之后，AMF可以首先确定本地是否存储有UE的信息和/或本地的第一信息是否是最新的。若是，则AMF可以直接在本地获得第一信息。若否，则AMF可以从另一核心网功能实体获得第一信息。
在一实施例中，UE的签约数据可以是接入和移动性签约数据。在一示例中，在UE为专用于定位的物联网设备的情况下，接入和移动性签约数据可以包括该物联网设备的、专用于定位的签约数据。在另一示例中，在UE为包括定位功能以及其他功能的物联网设备的情况下，接入和移动性签约数据可以包括该物联网设备的、专用于定位的签约数据，也可以包括其他签约数据。
在实际应用中，第一信息可以存储在UDM上。相应地，AMF可以通过AMF与UDM之间的服务检索第一信息。
在一实施例中，AMF检索第一信息可以包括：AMF可以向UDM发送第一请求消息；响应于第一请求消息，UDM可以向AMF发送第一响应消息。第一请求消息可以用于请求签约数据。第一响应消息可以携带有签约数据。签约数据是UDM响应于第一响应消息，在本地查找得到的。
在一示例中，AMF可以通过Nudm_SDM_Get服务检索第一信息。具体地，第一请求消息可以是Nudm_SDM_Get请求消息，并且第一响应消息可以是Nudm_SDM_Get响应消息。在另一示例中，AMF可以通过Nudm_SDM_Subscribe服务检索第一信息。具体地，第一请求消息可以是Nudm_SDM_Subscribe请求消息，并且第一响应消息可以是Nudm_SDM_Subscribe响应消息。
在另一实施例中，AMF检索第一信息可以包括：AMF可以向UDM签约UE的第一事件；在第一事件满足第一上报条件的情况下，AMF可以接收来自UDM的签约数据。
在一示例中，第一事件可以是时间触发的。例如，第一上报条件可以是UDM得到签约数据之后达到第一时长。在此情况下，在UDM得到UE的签约数据之后达到第一时长时，UDM可以将签约数据发送给AMF。又例如，第一上报条件可以是第二时长。在此情况下，在UDM中的一计时器每次达到 第二时长时，UDM将签约数据发送给AMF。
在另一示例中，第一事件可以是事件触发的。例如，第一上报条件可以是UDM得到签约数据。在此情况下，在UDM得到UE的签约数据时，UDM可以将签约数据发送给AMF。
可以理解的，第一信息还可以包括以下至少之一：SMF选择签约数据(SMF selection subscription data)、SMF中的UE上下文数据(UE context in SMF data)、位置服务移动来源(LCS mobile origination，location service mobile origination)。需要注意的是，第一信息还可以包括其他信息，本申请实施例对此不作具体限定。
S203，AMF通知UE注册完成。
其中，在S202中检索到第一信息之后，AMF可以通知UE注册完成。
可以理解的，AMF可以向UE发送注册响应，以通知UE注册完成。其中，注册响应可以携带有以下至少之一：5G-GUTI、注册区域(registration area)。注册区域用于表示可用的跟踪区域，并且可以包括允许的NSSAI(network slice selection assistance information，网络切片选择辅助信息)以及其中的S-NSSAI(single network slice selection assistance information，单网络切片选择辅助信息)。需要注意的是，注册响应还可以携带有其他信息，本申请实施例对此不作具体限定。
需要说明的是，注册响应可以携带在注册接受消息(registration accept message)(也可以被称为第二响应消息)中。需要注意的是，注册接受消息中还可以携带有其他信息，本申请实施例对此不作具体限定。
此外，在AMF通知UE注册完整之前，AMF可以对UE进行认证和授权。
S204，AMF对UE进行移动性管理。
可以理解的，在S203之后，UE注册完成，并且AMF获得第一信息。由此，AMF可以对UE进行移动性管理。在一实施例中，AMF可以根据第一信息对UE进行移动性管理。需要注意的是，AMF还可以对UE进行其他管理，本申请实施例对此不作具体限定。
至此，通过S201至S204，便完成了AMF对UE的移动性管理的过程。
图3为本公开实施例中的另一种物联网设备的管理方法的流程示意图。该通信方法可以应用于上述通信系统中。示例性的，如图3所示，终端设备可以为UE，接入网功能实体可以为gNB，第一核心网功能实体可以为AMF，第二核心网功能实体可以为UDM，第三核心网功能实体可以为SMF。上述方法可以包括：S301至S310。
S301，UE向AMF发送PDU会话建立请求。
其中，PDU会话建立请求(PDU session establishment request)用于发起PDU会话建立过程。
可以理解的，UE可以向AMF发送NAS消息(也可以称为第二请求消息)，NAS消息中携带有PDU会话建立请求。
其中，PDU会话建立请求可以携带在NAS消息，如PDU会话建立请求消息中。在一实施例中，PDU会话建立请求消息封装于上行非接入层消息(UL NAS message)中的N1SM容器(N1SM container)中。当然，在UL NAS消息中还可以包括其他信息，本公开实施例对此不做限制。
S302，AMF选择SMF。
其中，在S302中接收到PDU会话建立请求之后，AMF根据PDU会话建立请求选择SMF。具体细节可以参见3GPP TS 23.502，在此不做赘述。
S303，AMF向SMF发送会话管理上下文创建请求。
其中，会话管理上下文创建请求(也可以称为第三请求消息)用于请求创建PDU会话。
可以理解的，AMF可以存储有第一信息。第一信息包括UE的签约数据。例如，该签约数据可以是接入和移动性签约数据。第一信息可以携带在会话管理上下文创建请求消息中，也可以以其他方式由AMF发送给SMF。
在一示例中，在UE为专用于定位的物联网设备的情况下，签约数据可以包括该物联网设备的、专用于定位的签约数据。在另一示例中，在UE为包括定位功能以及其他功能的物联网设备的情况下，签约数据可以包括该物联网设备的、专用于定位的签约数据，也可以包括其他签约数据。
在实际应用中，签约数据可以是AMF预先获取的。例如，AMF可以在UE的注册过程中从UDM获取签约数据。
在一实施例中，第一信息可以携带在会话管理上下文创建请求消息中。具体地，AMF可以向SMF发送Nsmf_PDUSession_CreateSMContext请求。
可以理解的，会话管理上下文创建请求消息还可以携带有其他信息，例如，SUPI、DNN(data network name，数据网名称)、S-NSSAI、N1 SM container。
在另一实施例中，SMF可以向AMF签约UE的第二事件。在此情况下，当第二时间满足第二上报条件，则AMF可以向SMF发送UE的签约数据。
在一示例中，第二事件可以是时间触发的。例如，第二上报条件可以是AMF得到签约数据之后达到第三时长。在此情况下，在AMF得到UE的签约数据之后达到第三时长时，AMF可以将签约数据发送给SMF。又例如，第二上报条件可以是第四时长。在此情况下，在AMF中的一计时器每次达到第四时长时，AMF将签约数据发送给SMF。
在另一示例中，第二事件可以是事件触发的。例如，第二上报条件可以是AMF得到签约数据。在此情况下，在AMF得到UE的签约数据时，AMF可以将签约数据发送给SMF。又例如，第二上报条件可以是AMF接收到来自SMF的请求。在此情况下，在AMF接收到请求时，AMF可以将签约数据发送给SMF。
S304，SMF检索第一信息。
其中，第一信息可以包括UE的签约数据。
可以理解的，在接收到来自SMF的第一信息之后，AMF可以首先确定HPLMN(home public land mobile network，本地公共陆地移动网络)的SUPI、DNN、S-NSSAI对应的会话管理签约数据是否可用。若是，则使用该会话管理签约数据。若否，则意味着SMF需要得到新的会话管理签约数据。
在后一种情况下，SMF可以检索第一信息。此时，第一信息中的签约数据为会话签约数据。
可以理解的，SMF可以通过SMF与UDM之间的服务检索第一信息。
在一实施例中，SMF检索第一信息可以包括：SMF可以向UDM发送第四请求消息；响应于第四请求消息，UDM可以向SMF发送第四响应消息。第四请求消息可以用于请求签约数据。第四响应消 息可以携带有签约数据。签约数据是UDM响应于第四响应消息，在本地查找得到的。
在一示例中，SMF可以通过Nudm_SDM_Get服务检索第一信息。具体地，第四请求消息可以是Nudm_SDM_Get请求消息，并且第四响应消息可以是Nudm_SDM_Get响应消息。在另一示例中，SMF可以通过Nudm_SDM_Subscribe服务检索第一信息。具体地，第四请求消息可以是Nudm_SDM_Subscribe请求消息，并且第四响应消息可以是Nudm_SDM_Subscribe响应消息。
在另一实施例中，SMF检索第一信息可以包括：SMF可以向UDM签约UE的第三事件；在第三事件满足第三上报条件的情况下，SMF可以接收来自UDM的签约数据。
在一示例中，第三事件可以是时间触发的。例如，第三上报条件可以是UDM得到签约数据之后达到第五时长。在此情况下，在UDM得到UE的签约数据之后达到第五时长时，UDM可以将签约数据发送给SMF。又例如，第三上报条件可以是第六时长。在此情况下，在UDM中的一计时器每次达到第六时长时，UDM将签约数据发送给SMF。
在另一示例中，第三事件可以是事件触发的。例如，第三上报条件可以是UDM得到签约数据。在此情况下，在UDM得到UE的签约数据时，UDM可以将签约数据发送给SMF。
在实际应用中，第一信息可以存储在UDM上，或者可以由UDM从UDR获得。在后一种情况下，UDM可以通过Nudr_DM_Query服务或者Nudr_DM_subscribe服务从UDR获得签约数据。
需要说明的是，S304并不是必须的。如前文所述，在AMF可以首先确定HPLMN的SUPI、DNN、S-NSSAI对应的会话管理签约数据不可用的情况下，才需要执行S304。
S305，SMF向AMF发送会话管理上下文创建响应。
其中，会话管理上下文创建响应(也可以称为第三响应消息)用于表示SMF成功创建了会话管理上下文(SM context)。
由此，会话管理上下文创建响应中携带有会话管理上下文表示(SM context ID)，用于标识所创建的会话管理上下文。
S306，SMF向UPF发起N4会话建立流程。
其中，N4会话建立流程用于建立针对UE的PDU会话。
N4会话建立流程具体可以包括：SMF向UPF发送N4 session establishment request，并且接收来自UPF的N4 session establishment response。
S307，SMF向AMF发送Namf_Communication_N1N2Message Transfer。
其中，Namf_Communication_N1N2Message Transfer携带有分配给UE的IP地址。该IP地址用于实现UE的PDU会话。
S308，AMF向gNB发送N2 PDU会话请求。
其中，N2 PDU会话请求(N2 PDU session request)可以携带在NAS消息中。N2 PDU会话请求中包括分配给UE的IP地址。
S309，gNB向UE通知PDU会话建立完成。
其中，gNB通过发送PDU会话建立接受消息来通知PDU会话建立完成。PDU会话建立接受消息可以携带于由gNB转发的NAS消息中，并且包括分配给UE的IP地址。
需要说明的是，S305至S309的具体细节可以参见3GPP TS 23.502，在此不做赘述。
S310，SMF对UE进行会话管理。
可以理解的，在S310之后，UE的PDU会话建立完成，并且SMF获得第一信息。由此，SMF可以对UE进行会话管理。在一实施例中，SMF可以根据第一信息对UE进行会话管理。需要注意的是，SMF还可以对UE进行其他管理，本申请实施例对此不作具体限定。
至此，通过S301至S310，便完成了SMF对UE的会话管理的过程。
可以理解的，在图2和图3对应的是实施例中，还可以包括其他操作和/或流程。这些操作和/或流程的具体细节可以参见3GPP TS 23.502，在此不做赘述。
在本公开实施例中，移动网络中的核心网功能实体可以获得物联网设备的签约数据，并且该签约数据是用于定位服务的签约数据；核心网功能实体可以基于该签约数据进行物联网设备的管理，或者发送给另一核心网功能实体进行物联网设备的管理。以此方式，移动网络能够支持用于定位服务的物联网设备，进而能够实现针对物联网设备的定位服务。
基于相同的发明构思，本公开提供一种物联网设备的管理方法。该方法可以应用于第一核心网设备，例如，AMF。上述方法包括：第一核心网功能实体接收来自第二核心网功能实体的第一信息，第一信息包括物联网设备的用于定位服务的签约数据；第一核心网功能实体执行以下至少之一：根据第一信息，对物联网设备进行移动性管理；将第一信息发送给第三核心网功能实体，第一信息还用于第三核心网功能实体对物联网设备进行会话管理。
在一些可能的实施方式中，第一核心网功能实体接收来自第二核心网功能实体的第一信息的操作可以包括：第一核心网功能实体向第二核心网功能实体发送第一请求消息，第一请求消息用于请求签约数据；第一核心网功能实体接收第二核心网功能实体发送的第一响应消息，第一响应消息中携带有签约数据。
在一些可能的实施方式中，第一核心网功能实体接收来自第二核心网功能实体的第一信息的操作可以包括：第一核心网功能实体向第二核心网功能实体签约物联网设备的第一事件；在第一事件满足第一上报条件的情况下，第一核心网功能实体接收第二核心网功能实体发送的签约数据。
在一些可能的实施方式中，上述方法还可以包括：第一核心网功能实体接收物联网设备发送的第二请求消息，第二请求消息携带有第一设备标识，第一设备标识用于指示物联网设备。
在一些可能的实施方式中，第二请求消息可以为注册请求消息。
在一些可能的实施方式中，第一核心网功能实体将第一信息发送给第三核心网功能实体的操作可以包括：第一核心网功能实体向第三核心网功能实体发送第三请求消息，第三请求消息携带有签约数据。
在一些可能的实施方式中，第三请求消息可以为会话管理上下文创建请求消息。
基于相同的发明构思，本公开提供一种物联网设备的管理方法。该方法可以应用于第三核心网设备，例如，SMF。上述方法包括：第三核心网功能实体接收第一信息，第一信息包括物联网设备的用于定位服务的签约数据；第三核心网功能实体根据第一信息，对物联网设备进行会话管理。
在一些可能的实施方式中，第三核心网功能实体接收第一信息的操作可以包括：第三核心网功能实体接收来自第一核心网功能实体的第三请求消息，第三请求消息携带有签约数据。
在一些可能的实施方式中，第三请求消息可以为会话管理上下文创建请求消息。
在一些可能的实施方式中，第三核心网功能实体接收第一信息的操作可以包括：第三核心网功能实体向第一核心网功能实体签约物联网设备的第二事件；在第二事件满足第二上报条件的情况下，第三核心网功能实体接收第一核心网功能实体发送的签约数据。
在一些可能的实施方式中，第三核心网功能实体接收第一信息的操作可以包括：第三核心网功能实体向第二核心网功能实体发送第四请求消息，第四请求消息用于请求签约数据；第三核心网功能实体接收第二核心网功能实体发送的第四响应消息，第四响应消息中携带有签约数据。
在一些可能的实施方式中，第三核心网功能实体接收第一信息的操作可以包括：第三核心网功能实体向第二核心网功能实体签约物联网设备的第三事件；在第三事件满足第三上报条件的情况下，第三核心网功能实体接收第二核心网功能实体发送的签约数据。
基于相同的发明构思，本公开提供一种物联网设备的管理装置。该装置可以为第一核心网功能实体(如AMF)或者其中的芯片或者片上系统，还可以为第一核心网功能实体中用于实现上述各个方面所述的方法的功能模块。该装置可以实现上述各方面中第一核心网功能实体所执行的功能，这些功能可以通过硬件执行相应的软件实现。这些硬件或软件包括一个或多个上述功能相应的模块。
图4为本公开实施例中的一种物联网设备的管理装置的结构示意图。如图4所示，上述装置400包括：接收模块401，配置为接收来自第二核心网功能实体的第一信息，第一信息包括物联网设备的用于定位服务的签约数据。所述装置还包括以下至少之一：处理模块402，配置为根据第一信息，对物联网设备进行移动性管理；发送模块403，配置为将第一信息发送给第三核心网功能实体，第一信息还用于第三核心网功能实体对物联网设备进行会话管理。
在一些可能的实施方式中，发送模块403还可以配置为：向第二核心网功能实体发送第一请求消息，第一请求消息用于请求签约数据；接收模块401可以配置为：接收第二核心网功能实体发送的第一响应消息，第一响应消息中携带有签约数据。
在一些可能的实施方式中，发送模块403可以配置为：向第二核心网功能实体签约物联网设备的第一时间；接收模块401可以配置为：在第一事件满足第一上报条件的情况下，接收第二核心网功能实体发送的签约数据。
在一些可能的实施方式中，接收模块401还可以配置为：接收物联网设备发送的第二请求消息，第二请求消息携带有第一设备标识，第一设备标识用于指示物联网设备。
在一些可能的实施方式中，第二请求消息可以为注册请求消息。
在一些可能的实施方式中，发送模块403可以配置为：向第三核心网功能实体发送第三请求消息，第三请求消息携带有签约数据。
在一些可能的实施方式中，第三请求消息可以为会话管理上下文创建请求消息。
需要说明的是，接收模块401、处理模块402和发送模块403的具体实现过程可参考图2和图3实施例的详细描述，为了说明书的简洁，这里不再赘述。
基于相同的发明构思，本公开提供一种物联网设备的管理装置。该装置可以为第三核心网功能实体(如SMF)或者其中的芯片或者片上系统，还可以为第三核心网功能实体中用于实现上述各个方面所 述的方法的功能模块。该装置可以实现上述各方面中第三核心网功能实体所执行的功能，这些功能可以通过硬件执行相应的软件实现。这些硬件或软件包括一个或多个上述功能相应的模块。
图5为本公开实施例中的另一种物联网设备的管理装置的结构示意图。如图5所示，上述装置500包括：接收模块501，配置为接收第一信息，第一信息包括物联网设备的用于定位服务的签约数据；处理模块502，根据第一信息，对物联网设备进行会话管理。
在一些可能的实施方式中，接收模块501可以配置为：接收来自第一核心网功能实体的第三请求消息，第三请求消息携带有签约数据。
在一些可能的实施方式中，第三请求消息可以为会话管理上下文创建请求消息。
在一些可能的实施方式中，上述装置500还可以包括：发送模块503，配置为向第一核心网功能实体签约物联网设备的第二事件；接收模块501可以配置为：在第二事件满足第二上报条件的情况下，接收第一核心网功能实体发送的签约数据。
在一些可能的实施方式中，上述装置500还可以包括：发送模块503，配置为向第二核心网功能实体发送第四请求消息，第四请求消息用于请求签约数据；接收模块可以配置为：接收第二核心网功能实体发送的第四响应消息，第四响应消息中携带有签约数据。
在一些可能的实施方式中，上述装置500还可以包括：发送模块503，配置为向第二核心网功能实体签约物联网设备的第三事件；接收模块501可以配置为：在第三事件满足第三上报条件的情况下，接收第二核心网功能实体发送的签约数据。
需要说明的是，接收模块501、处理模块502和发送模块503的具体实现过程可参考图2和图3实施例的详细描述，为了说明书的简洁，这里不再赘述。
基于相同的发明构思，本公开实施例提供一种网络功能实体，该网络功能实体与上述一个或者多个实施例中的核心网功能实体一致。
图6为本公开实施例中的一种网络功能实体的结构示意图。如图6所示，网络功能实体600可以包括处理组件601，其进一步包括一个或多个处理器，以及由存储器602所代表的存储器资源，用于存储可由处理组件601的执行的指令，例如应用程序。存储器602中存储的应用程序可以包括一个或一个以上的每一个对应于一组指令的模块。此外，处理组件601被配置为执行指令，以执行上述方法前述应用在网络功能实体的任一方法。
网络功能实体600还可以包括一个电源组件603被配置为执行网络功能实体600的电源管理，一个有线或无线网络接口604被配置为将网络功能实体600连接到网络，和一个输入输出(I/O)接口605。网络功能实体600可以操作基于存储在存储器602的操作系统，例如Windows Server TM，Mac OS XTM，UnixTM，LinuxTM，FreeBSDTM或类似。
基于相同的发明构思，本公开实施例还提供一种电子设备。该电子设备包括：存储器；处理器，与存储器连接，被配置为执行存储在存储器上的计算机可执行指令，以执行上述一个或者多个实施例中第一核心网功能实体或第三核心网功能实体的方法。
基于相同的发明构思，本公开实施例还提供一种计算机可读存储介质，计算机可读存储介质中存储有指令；当指令在计算机上运行时，用于执行上述一个或者多个实施例中第一核心网功能实体或第三核 心网功能实体的方法。
基于相同的发明构思，本公开实施例还提供一种计算机程序或计算机程序产品，当计算机程序产品在计算机上被执行时，使得计算机实现上述一个或者多个实施例中第一核心网功能实体或第三核心网功能实体的方法。
本领域技术人员在考虑说明书及实践这里公开的发明后，将容易想到本发明的其它实施方案。本公开旨在涵盖本发明的任何变型、用途或者适应性变化，这些变型、用途或者适应性变化遵循本发明的一般性原理并包括本公开未公开的本技术领域中的公知常识或惯用技术手段。说明书和实施例仅被视为示例性的，本发明的真正范围和精神由下面的权利要求指出。
应当理解的是，本发明并不局限于上面已经描述并在附图中示出的精确结构，并且可以在不脱离其范围进行各种修改和改变。本发明的范围仅由所附的权利要求来限制。

Claims (17)

  1. 一种物联网设备的管理方法，包括：
    第一核心网功能实体接收来自第二核心网功能实体的第一信息，所述第一信息包括物联网设备的用于定位服务的签约数据；
    所述第一核心网功能实体执行以下至少之一：
    根据所述第一信息，对所述物联网设备进行移动性管理；
    将所述第一信息发送给第三核心网功能实体，所述第一信息还用于所述第三核心网功能实体对所述物联网设备进行会话管理。
  2. 根据权利要求1所述的方法，其中，所述第一核心网功能实体接收来自第二核心网功能实体的第一信息，包括：
    所述第一核心网功能实体向所述第二核心网功能实体发送第一请求消息，所述第一请求消息用于请求所述签约数据；
    所述第一核心网功能实体接收所述第二核心网功能实体发送的第一响应消息，所述第一响应消息中携带有所述签约数据。
  3. 根据权利要求1所述的方法，其中，所述第一核心网功能实体接收来自第二核心网功能实体的第一信息，包括：
    所述第一核心网功能实体向所述第二核心网功能实体签约所述物联网设备的第一事件；
    在所述第一事件满足第一上报条件的情况下，所述第一核心网功能实体接收所述第二核心网功能实体发送的所述签约数据。
  4. 根据权利要求1所述的方法，其中，所述方法还包括：
    所述第一核心网功能实体接收所述物联网设备发送的第二请求消息，所述第二请求消息携带有第一设备标识，所述第一设备标识用于指示所述物联网设备。
  5. 根据权利要求4所述的方法，其中，所述第二请求消息为注册请求消息。
  6. 根据权利要求1所述的方法，其中，所述第一核心网功能实体将所述第一信息发送给第三核心网功能实体，包括：
    所述第一核心网功能实体向所述第三核心网功能实体发送所述第三请求消息，所述第三请求消息携带有所述签约数据。
  7. 根据权利要求6所述的方法，其中，所述第三请求消息为会话管理上下文创建请求消息。
  8. 一种物联网设备的管理方法，包括：
    第三核心网功能实体接收第一信息，所述第一信息包括物联网设备的用于定位服务的签约数据；
    所述第三核心网功能实体根据所述第一信息，对所述物联网设备进行会话管理。
  9. 根据权利要求8所述的方法，其中，所述第三核心网功能实体接收第一信息，包括：
    所述第三核心网功能实体接收来自第一核心网功能实体的第三请求消息，所述第三请求消息携带有所述签约数据。
  10. 根据权利要求9所述的方法，其中，所述第三请求消息为会话管理上下文创建请求消息。
  11. 根据权利要求8所述的方法，其中，所述第三核心网功能实体接收第一信息，包括：
    所述第三核心网功能实体向所述第一核心网功能实体签约所述物联网设备的第二事件；
    在所述第二事件满足第二上报条件的情况下，所述第三核心网功能实体接收所述第一核心网功能实体发送的所述签约数据。
  12. 根据权利要求8所述的方法，其中，所述第三核心网功能实体接收第一信息，包括：
    所述第三核心网功能实体向第二核心网功能实体发送第四请求消息，所述第四请求消息用于请求所述签约数据；
    所述第三核心网功能实体接收所述第二核心网功能实体发送的第四响应消息，所述第四响应消息中携带有所述签约数据。
  13. 根据权利要求8所述的方法，其中，所述第三核心网功能实体接收第一信息，包括：
    所述第三核心网功能实体向所述第二核心网功能实体签约所述物联网设备的第三事件；
    在所述第三事件满足第三上报条件的情况下，所述第三核心网功能实体接收所述第二核心网功能实体发送的所述签约数据。
  14. 一种物联网设备的管理装置，包括：
    接收模块，配置为接收来自第二核心网功能实体的第一信息，所述第一信息包括物联网设备的用于定位服务的签约数据；
    所述装置还包括以下至少之一：
    处理模块，配置为根据所述第一信息，对所述物联网设备进行移动性管理；
    发送模块，配置为将所述第一信息发送给第三核心网功能实体，所述第一信息还用于所述第三核心网功能实体对所述物联网设备进行会话管理。
  15. 一种物联网设备的管理装置，包括：
    接收模块，配置为接收第一信息，所述第一信息包括物联网设备的用于定位服务的签约数据；
    处理模块，根据所述第一信息，对所述物联网设备进行会话管理。
  16. 一种电子设备，其特征在于，包括：存储器；处理器，与所述存储器连接，被配置为执行存储在所述存储器上的计算机可执行指令，以实现如权利要求1至7、或者权利要求8至13中任一项所述的方法。
  17. 一种计算机存储介质，所述计算机存储介质存储有计算机可执行指令，其特征在于，所述计算机可执行指令被处理器执行后能够实现如权利要求1至7、或者权利要求8至13中任一项所述的方法。
PCT/CN2022/102901 2022-06-30 2022-06-30 物联网设备的管理方法、装置、设备和存储介质 WO2024000435A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202280002506.9A CN117643079A (zh) 2022-06-30 2022-06-30 物联网设备的管理方法、装置、设备和存储介质
PCT/CN2022/102901 WO2024000435A1 (zh) 2022-06-30 2022-06-30 物联网设备的管理方法、装置、设备和存储介质

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/102901 WO2024000435A1 (zh) 2022-06-30 2022-06-30 物联网设备的管理方法、装置、设备和存储介质

Publications (1)

Publication Number Publication Date
WO2024000435A1 true WO2024000435A1 (zh) 2024-01-04

Family

ID=89383797

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/102901 WO2024000435A1 (zh) 2022-06-30 2022-06-30 物联网设备的管理方法、装置、设备和存储介质

Country Status (2)

Country Link
CN (1) CN117643079A (zh)
WO (1) WO2024000435A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190053010A1 (en) * 2017-08-14 2019-02-14 Qualcomm Incorporated Systems and methods for 5g location support using service based interfaces
WO2021032907A1 (en) * 2019-08-22 2021-02-25 Nokia Technologies Oy Providing location information
CN113303025A (zh) * 2019-01-18 2021-08-24 苹果公司 基于受支持的蜂窝物联网(ciot)特征选择核心网络
US20210400437A1 (en) * 2020-06-23 2021-12-23 T-Mobile Usa, Inc. System and method for registration of a network enabled location tracking device
CN114531641A (zh) * 2020-10-31 2022-05-24 华为技术有限公司 一种通信方法及通信装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190053010A1 (en) * 2017-08-14 2019-02-14 Qualcomm Incorporated Systems and methods for 5g location support using service based interfaces
CN113303025A (zh) * 2019-01-18 2021-08-24 苹果公司 基于受支持的蜂窝物联网(ciot)特征选择核心网络
WO2021032907A1 (en) * 2019-08-22 2021-02-25 Nokia Technologies Oy Providing location information
US20210400437A1 (en) * 2020-06-23 2021-12-23 T-Mobile Usa, Inc. System and method for registration of a network enabled location tracking device
CN114531641A (zh) * 2020-10-31 2022-05-24 华为技术有限公司 一种通信方法及通信装置

Also Published As

Publication number Publication date
CN117643079A (zh) 2024-03-01

Similar Documents

Publication Publication Date Title
EP3571890B1 (en) Network registration and network slice selection system and method
CN111586771B (zh) 网络节点选择方法及装置
WO2022257549A1 (zh) 网络切片方法、设备及存储介质
WO2019184651A1 (zh) 一种通信方法及装置
WO2020156116A1 (zh) 上下文存储方法及装置
WO2020224622A1 (zh) 一种信息配置方法及装置
WO2019020117A1 (zh) 一种激活session的方法、设备及系统
US11729599B2 (en) Communication system
JP7099536B2 (ja) コアネットワーク装置、通信端末、コアネットワーク装置の方法、プログラム、及び通信端末の方法
US20210306381A1 (en) Method and Apparatus for Determining Security Protection Mode
WO2018137152A1 (zh) 短消息传输方法、设备和系统
WO2021132096A1 (ja) Ａｍｆノード及びその方法
WO2018214762A1 (zh) 一种获取寻呼参数的方法及装置
WO2021047454A1 (zh) 位置信息获取、位置服务配置方法和通信设备
WO2024000435A1 (zh) 物联网设备的管理方法、装置、设备和存储介质
WO2020034972A1 (zh) 会话迁移的方法和装置
WO2019095379A1 (zh) 一种业务激活及去激活的方法、装置、计算机存储介质
WO2023197320A1 (zh) 上行定位参考信号的配置方法、装置、设备及存储介质
WO2022016338A1 (zh) 一种通信方法及装置
WO2023201733A1 (zh) 无线通信的方法和设备
WO2022160275A1 (zh) 无线通信方法、设备及存储介质
WO2024032552A1 (zh) 通信方法、装置及存储介质
WO2021138784A1 (zh) 一种接入网络的方法、装置及系统
WO2024032157A1 (zh) 通信方法及装置
CN114982311B (zh) 数据关闭方法、装置、设备及存储介质

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 202280002506.9

Country of ref document: CN

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

Ref document number: 22948540

Country of ref document: EP

Kind code of ref document: A1