CN117643079A

CN117643079A - Management method, device, equipment and storage medium of Internet of things equipment

Info

Publication number: CN117643079A
Application number: CN202280002506.9A
Authority: CN
Inventors: 吴锦花
Original assignee: Beijing Xiaomi Mobile Software Co Ltd
Current assignee: Beijing Xiaomi Mobile Software Co Ltd
Priority date: 2022-06-30
Filing date: 2022-06-30
Publication date: 2024-03-01
Also published as: WO2024000435A1

Abstract

The invention provides a management method, a device, equipment and a storage medium for Internet of things equipment, and relates to the technical field of wireless communication. The method comprises the following steps: the method comprises the steps that a first core network functional entity receives first information from a second core network functional entity, wherein the first information comprises subscription data of Internet of things equipment for positioning services; the first core network functional entity performs at least one of: according to the first information, mobility management is conducted on the Internet of things equipment; and sending the first information to a third core network functional entity, wherein the first information is also used for session management of the Internet of things equipment by the third core network functional entity. The support of the mobile network to the Internet of things equipment for the positioning service can be realized.

Description

Management method, device, equipment and storage medium of Internet of things equipment

Technical Field

The disclosure relates to the technical field of wireless communication, and in particular relates to a management method, a device, equipment and a storage medium of internet of things equipment.

Background

The internet of things (internet of things, ioT) is a huge network formed by combining various information sensing devices with the network on the basis of the internet, so that the interconnection and the intercommunication of people, machines and objects at any time and any place are realized. The internet of things devices are of different types and can provide various services in different scenarios. Among the many types of internet of things devices, there is a type of internet of things device that can be used to implement a positioning function. Such internet of things devices may also be referred to as internet of things locating devices.

With the continuous development of wireless communication technology, mobile networks are also required to be able to support location services of internet of things devices, thereby further implementing location-based services.

How to support the internet of things device for location services in a mobile network is a problem to be solved.

Disclosure of Invention

The disclosure provides a management method, a device, equipment and a storage medium of internet of things equipment to realize support of a mobile network to the internet of things equipment for positioning service.

In a first aspect, the present disclosure provides a method for managing an internet of things device. The method may be applied to a first core network device. The method comprises the following steps: the method comprises the steps that a first core network functional entity receives first information from a second core network functional entity, wherein the first information comprises subscription data of Internet of things equipment for positioning services; the first core network functional entity performs at least one of: according to the first information, mobility management is conducted on the Internet of things equipment; and sending the first information to a third core network functional entity, wherein the first information is also used for session management of the Internet of things equipment by the third core network functional entity.

In some possible embodiments, 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, wherein the first request message is used for requesting subscription data; the first core network functional entity receives a first response message sent by the second core network functional entity, wherein the first response message carries subscription data.

In some possible embodiments, 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 signs a first event of the Internet of things equipment to the second core network functional entity; and under the condition that the first event meets the first reporting condition, the first core network functional entity receives the subscription data sent by the second core network functional entity.

In some possible embodiments, the above method may further comprise: the first core network functional entity receives a second request message sent by the Internet of things device, wherein the second request message carries a first device identifier, and the first device identifier is used for indicating the Internet of things device.

In some possible implementations, the second request message may be a registration request message.

In some possible embodiments, 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 sends a third request message to the third core network functional entity, wherein the third request message carries subscription data.

In some possible implementations, the third request message may create a request message for the session management context.

In a second aspect, the present disclosure provides a method of managing an internet of things device. The method may be applied to a third core network device. The method comprises the following steps: the third core network functional entity receives first information, wherein the first information comprises subscription data of the Internet of things equipment for positioning service; and the third core network functional entity performs session management on the Internet of things equipment according to the first information.

In some possible embodiments, 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, wherein the third request message carries subscription data.

In some possible embodiments, 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 equipment to the first core network functional entity; and under the condition that the second event meets the second reporting condition, the third core network functional entity receives the subscription data sent by the first core network functional entity.

In some possible embodiments, 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, wherein the fourth request message is used for requesting subscription data; the third core network functional entity receives a fourth response message sent by the second core network functional entity, wherein the fourth response message carries subscription data.

In some possible embodiments, the operation of the third core network functional entity receiving the first information may include: a third core network functional entity signs a third event of the internet of things device to the second core network functional entity; and under the condition that the third event meets a third reporting condition, the third core network functional entity receives the subscription data sent by the second core network functional entity.

In a third aspect, the present disclosure provides a management apparatus for an internet of things device. The device may be the first core network functional entity or a chip or a system on chip therein, and may also be a functional module in the first core network functional entity for implementing the method described in the above aspects. The device can realize the functions executed by the first core network functional entity in the aspects, and the functions can be realized by hardware executing corresponding software. Such hardware or software includes one or more modules corresponding to the functions described above. The device comprises: the receiving module is configured to receive first information from the second core network functional entity, wherein the first information comprises subscription data of the internet of things equipment for positioning services. The apparatus further comprises at least one of: the processing module is configured to perform mobility management on the Internet of things equipment according to the first information; the sending module is configured to send the first information to the third core network functional entity, and the first information is also used for session management of the internet of things equipment by the third core network functional entity.

In some possible implementations, the sending module may be further configured to: sending a first request message to a second core network functional entity, wherein the first request message is used for requesting subscription data; the receiving module may be configured to: and receiving a first response message sent by the second core network functional entity, wherein the first response message carries subscription data.

In some possible implementations, the sending module may be configured to: signing the first time of the internet of things device to the second core network functional entity; the receiving module may be configured to: and under the condition that the first event meets the first reporting condition, receiving the subscription data sent by the second core network functional entity.

In some possible implementations, the receiving module may be further configured to: and receiving a second request message sent by the Internet of things equipment, wherein the second request message carries a first equipment identifier, and the first equipment identifier is used for indicating the Internet of things equipment.

In some possible implementations, the sending module may be configured to: and sending a third request message to a third core network functional entity, wherein the third request message carries subscription data.

In a fourth aspect, the present disclosure provides a management apparatus for an internet of things device. The device may be a third core network functional entity or a chip or a system on chip therein, and may also be a functional module in the third core network functional entity for implementing the method described in the above aspects. The device can realize the functions executed by the third core network functional entity in the aspects, and the functions can be realized by hardware executing corresponding software. Such hardware or software includes one or more modules corresponding to the functions described above. The device comprises: the receiving module is configured to receive first information, wherein the first information comprises subscription data of the internet of things equipment for positioning service; and the processing module is used for carrying out session management on the Internet of things equipment according to the first information.

In some possible implementations, the receiving module may be configured to: and receiving a third request message from the first core network functional entity, wherein the third request message carries subscription data.

In some possible embodiments, the apparatus may further include: the sending module is configured to sign up a second event of the internet of things equipment to the first core network functional entity; the receiving module may be configured to: and receiving the subscription data sent by the first core network functional entity under the condition that the second event meets the second reporting condition.

In some possible embodiments, the apparatus may further include: the sending module is configured to send a fourth request message to the second core network functional entity, wherein the fourth request message is used for requesting subscription data; the receiving module may be configured to: and receiving a fourth response message sent by the second core network functional entity, wherein the fourth response message carries subscription data.

In some possible embodiments, the apparatus may further include: the sending module is configured to sign up a third event of the internet of things equipment to the second core network functional entity; the receiving module may be configured to: and receiving the subscription data sent by the second core network functional entity under the condition that the third event meets the third reporting condition.

In a fifth aspect, the present disclosure provides an electronic device. The electronic device includes: a memory; a processor, coupled to the memory, configured to execute computer-executable instructions stored on the memory to implement the method as claimed in any one of the first aspect, the second aspect and possible implementations thereof.

In a sixth aspect, the present disclosure provides a computer storage medium. The computer storage medium stores computer-executable instructions. Computer-executable instructions, when executed by a processor, enable the implementation of the method as claimed in any one of the first aspect, the second aspect and possible implementations thereof.

In the present disclosure, a core network functional entity in a mobile network may obtain subscription data of an internet of things device, and the subscription data is subscription data for a location service; the core network functional entity can manage the internet of things equipment based on the subscription data, or send the subscription data to another core network functional entity to manage the internet of things equipment. In this way, the mobile network can support the internet of things device for the location service, and thus can implement the location service for the internet of things device.

It should be understood that, the third to sixth aspects of the present disclosure are consistent with the technical solutions of the first to second aspects of the present disclosure, and the advantages obtained by each aspect and the corresponding possible embodiments are similar, and are not repeated.

Drawings

Fig. 1 is a schematic structural diagram of a communication system in an embodiment of the present disclosure;

fig. 2 is a flow chart of a method for managing an internet of things device in an embodiment of the disclosure;

Fig. 3 is a flow chart of another method for managing internet of things devices according to an embodiment of the disclosure;

fig. 4 is a schematic structural diagram of a management device of an internet of things device in an embodiment of the disclosure;

fig. 5 is a schematic structural diagram of a management device of another internet of things device in an embodiment of the disclosure;

fig. 6 is a schematic structural diagram of a functional entity of a core network in an embodiment of the disclosure.

Detailed Description

Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the embodiments of the present disclosure. Rather, they are merely examples of apparatus and methods consistent with aspects of embodiments of the present disclosure as detailed in the accompanying claims.

The terminology used in the embodiments of the disclosure is for the purpose of describing particular embodiments only and is not intended to be limiting of the embodiments of the disclosure. As used in this disclosure of embodiments and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any or all possible combinations of one or more of the associated listed items.

It should be understood that although the terms "first," "second," "third," etc. may be used in embodiments of the present disclosure to describe various elements, these elements should not be limited to these terms. These terms are only used to distinguish one element of the same type from another. For example, a "first" element could also be termed a "second" element, and, similarly, a "second" element could also be termed a "first" element, without departing from the scope of embodiments of the present disclosure. The word "if" as used herein may be interpreted as "at … …" or "at … …" or "responsive to a determination", depending on the context.

Further, in the description of the embodiments of the present disclosure, "and/or" is merely one association relationship describing the association object, indicating that three relationships may exist. For example, a and/or B may represent: a exists alone, A and B exist together, and B exists alone. In addition, in the description of the embodiments of the present disclosure, "plurality" may refer to two or more than two.

The internet of things is a huge network formed by combining various information sensing devices with a network on the basis of the internet, and the interconnection and intercommunication of people, machines and objects at any time and any place are realized. As one terminal device, the internet of things device may have different types, and may provide various services in different scenes. Among the many types of internet of things devices, there is a type of internet of things device that can be used to implement a positioning function. Such internet of things devices may also be referred to as internet of things locating devices. In fact, among such internet of things devices, a part of the internet of things devices is only used to implement a positioning function. The internet of things device of this part may for example comprise: GPS location tracking devices, RFID tracking devices, and the like. The internet of things equipment can report the position of the internet of things equipment by being connected to access equipment such as a gateway and the like, so that the positioning function is realized. In addition, the other part of the internet of things equipment can provide other functions while realizing the positioning function.

With the continuous development of wireless communication technology, mobile networks are also required to be able to support location services of internet of things devices, thereby further implementing location-based services. In order to support the location services of the internet of things device, the core network functional entity in the mobile network should be able to manage the internet of things device.

The embodiment of the disclosure provides a communication system which can support positioning service of equipment of the Internet of things. The communication system may be a 5G communication system or a future evolution communication system. In the architecture of the communication system, there are a terminal, an access network function entity (may also be described as an access network device, an access network element, an access network function component, an access network function module, etc.), and at least one core Network Function (NF) entity (may also be described as a core network device, a core network element, a core network function component, a core network function module, etc.). At least one core network functional entity is located in the core network (i.e. 5 GC).

Fig. 1 is a schematic structural diagram of a communication system in an embodiment of the present disclosure. As shown in fig. 1, the communication system 100 may include a 5G Access Network (AN) and a 5G core network (5 GC). The 5G access network may include, among other things, a next generation radio access network (next generation radio access network, NG RAN) 101, the NG RAN 101 communicating with the terminal device 102 over a Uu interface. The 5G core network 103 may include: access and mobility management functions (access and mobility management function, AMF) 1031, user plane functions (user plane function, UPF) 1032, session management functions (session management function, SMF) 1033, policy control functions (policy control function, PCF) 1034, unified data management (unified data management, UDM) 1035, and the like.

In the embodiment of the present disclosure, the communication system may further include other network elements, which is not specifically limited in the embodiment of the present disclosure.

Wherein in the above communication system, the terminal device may access the 5G core network through third generation partnership project (3rd generation partnership project,3GPP) technology. Specifically, the terminal device may access the 5G core network through the 3GPP access network device.

In the above communication system, the UDM 1035 has a function of unified data management. The method is mainly responsible for managing subscription data, user access authorization and other functions.

PCF 1034 has policy control functions and is mainly responsible for charging policies for sessions, traffic flows, quality of service (quality of service, qoS) bandwidth guarantees, policy decisions related to policies, etc. In this architecture, PCFs 1034 connected to AMF 1031 and SMF 1033 may correspond to AM PCFs (PCF for access and mobility control) and SM PCFs (PCF for session management), respectively, which may not be the same PCF entity in an actual deployment scenario.

The SMF 1033 has a session management function, and mainly performs functions such as session management, execution of control policy issued by the PCF 1034, selection of the UPF 1032, and internet protocol (internet protocol, IP) address assignment of the terminal device 102.

The AMF 1031 has access and mobility management functions, and mainly performs mobility management, access authentication/authorization, and other functions. In addition, it is responsible for passing user policies between terminal device 102 and PCF 1034.

The UPF 1032 is a user plane function entity, and serves as an interface with a data network to complete functions of User Plane (UP) data forwarding, session/flow-level based charging statistics, bandwidth limitation, and the like.

Wherein each interface function is described as follows:

n7: an interface between PCF 1034 and SMF 1033 is used to issue control policies for Packet Data Unit (PDU) session granularity and traffic data flow granularity.

And N3: communication interface between UPF 1032 and NG RAN 101.

N15: the interface between PCF 1034 and AMF 1031 is used to issue terminal device policies and access control related policies.

N4: the interface between the SMF 1033 and the UPF 1032 is used for transferring information between the control plane and the UP, including controlling the issue of forwarding rules, qoS control rules, traffic statistics rules, etc. for the UP and the information reporting for the UP.

N11: an interface between the SMF 1033 and the AMF 1031 is used to transfer PDU session tunnel information between the NG RAN 101 and the UPF 1032, transfer control messages sent to the terminal device, transfer radio resource control information sent to the NG RAN 101, and so on.

N2: an interface between the AMF 1031 and the NG RAN 101 is used to transfer radio bearer control information and the like from the core network side to the NG RAN 101.

N1: the interface between the AMF 1031 and the terminal device 102 is independent of access, and is used for delivering QoS control rules and the like to the terminal device 102.

N8: the interface between the AMF 1031 and the UDM 1035 is used for the AMF 1031 to obtain the subscription data and authentication data related to access and mobility management from the UDM 1034, and the AMF 1031 registers the current mobility management related information of the terminal device 102 from the UDM 1034.

N10: the interface between the SMF 1033 and the UDM 1034 is used for the SMF 1033 to obtain session management related subscription data from the UDM 1034, and the SMF 1033 registers current session related information of the terminal device 102 from the UDM 1034.

The terminal device may be a terminal device having a wireless communication function, and may also be referred to as a User Equipment (UE). The terminal device may be deployed on land, including indoor or outdoor, handheld, wearable or vehicle-mounted; can also be deployed on the water surface (such as ships, etc.); but may also be deployed in the air (e.g., on aircraft, balloon, satellite, etc.). The terminal device may be a mobile phone (mobile phone), a tablet computer (Pad), a computer with a wireless transceiving function, a Virtual Reality (VR) terminal device, an augmented reality (augmented reality, AR) terminal device, a wireless terminal in industrial control (industrial control), a wireless terminal in unmanned (self-driving), a wireless terminal in remote medical (remote medical), a wireless terminal in smart grid (smart grid), a wireless terminal in transportation security (transportation safety), a wireless terminal in smart city (smart city), a wireless terminal in smart home (smart home), or the like. The terminal device may also be a handheld device, an in-vehicle device, a wearable device, a computing device, or other processing device connected to a wireless modem, etc. with wireless communication capabilities. Alternatively, the terminal devices in different networks may also be called different names, for example: a terminal device, an access terminal, a subscriber unit, a subscriber station, a mobile station, a remote terminal, a mobile device, a user terminal, a wireless communication device, a user agent or user device, a cellular telephone, a cordless telephone, a session initiation protocol (session initiation protocol, SIP) phone, a wireless local loop (wireless local loop, WLL) station, a personal digital assistant (personal digital assistant, PDA), a terminal device in a 5G network or future evolution network, and the like.

The access network device may be a device on the access network side for supporting the terminal to access the wireless communication system. For example, a next generation base station (gNB), a transmission/reception point (transmission reception point, TRP), a relay node (relay node), an Access Point (AP), and the like in the 5G access technology communication system may be mentioned.

It should be noted that, in the communication system shown in fig. 1, functions and interfaces of each device are merely exemplary, and not all functions of each device are necessary when the devices are applied to the embodiments of the present disclosure. All or part of the devices of the core network may be physical entity devices or virtualized devices, which are not limited herein. Of course, the communication system in the embodiment of the present disclosure may further include other devices not shown in fig. 1, which is not limited herein.

In order to solve the above problems, in combination with the above communication system, an embodiment of the present disclosure provides a management method for an internet of things device.

Fig. 2 is a flow chart of a management method of an internet of things device in an embodiment of the disclosure. The communication method can be applied to the communication system. For example, as shown in fig. 2, 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, and the second core network functional entity may be a UDM. The method may include: s201 to S204.

S201, the AMF receives a registration request from the UE.

Wherein the registration request may carry at least one of: registration type, UE identity, security parameters. It should be noted that the registration request may also carry other information, which is not specifically limited in the embodiments of the present application.

The registration type may be used to represent the type of registration. For example, registration types may include: initial registration (initial registration), mobility registration update (mobility registration update), periodic registration update (periodic registration update), emergency registration (emergency registration), or other types. The UE identity (which may also be referred to as a first device identity) may be a sui or 5G-GUTI or PEI for identifying the terminal device. The security parameters may be used for authentication and integrity protection.

In practical applications, 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 referred to as a second request message).

In an embodiment, the gNB may forward the registration request from the UE to the AMF. Specifically, the UE may send a registration request to the gNB over the Uu interface; thereafter, the gNB may send a registration request to the AMF via the N2 interface. In this case, the registration request sent by the UE to the gNB may be carried in AN message; and the registration request sent by the gNB to the AMF may be carried in an N2 message. At this time, the registration request message may include AN message and AN N2 message. It should be noted that, the RAN message and the N2 message may also carry other information, which is not specifically limited in the embodiments of the present application.

In another embodiment, the gNB may transparently transmit a registration request sent by the UE to the AMF. Specifically, the UE may send a registration request to the AMF through the N1 interface. At this time, the registration request message may be an N1 message. In this case, the registration request may be carried in an N1 message. It should be noted that other information may also be carried in the N1 message, which is not specifically limited in the embodiment of the present application.

S202, the AMF retrieves the first information.

Wherein the first information may include subscription data of the UE.

It will be appreciated that upon receiving a registration request from a UE, the AMF may first determine whether information of the UE is stored locally and/or whether the local first information is up-to-date. If so, the AMF may obtain the first information directly locally. If not, the AMF may obtain the first information from another core network functional entity.

In an embodiment, the subscription data of the UE may be access and mobility subscription data. In an example, where the UE is a location-specific internet of things device, the access and mobility subscription data may include location-specific subscription data for the internet of things device. In another example, in the case where the UE is an internet of things device including a positioning function and other functions, the access and mobility subscription data may include subscription data of the internet of things device that is dedicated to positioning, and may also include other subscription data.

In practical applications, the first information may be stored on the UDM. Accordingly, the AMF may retrieve the first information through a service between the AMF and the UDM.

In an embodiment, 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 for requesting subscription data. The first response message may carry subscription data. The subscription data is obtained by the UDM in response to the first response message by looking up locally.

In one example, the AMF may retrieve the first information through a Nudm_SDM_get service. Specifically, the first request message may be a nudm_sdm_get request message, and the first response message may be a nudm_sdm_get response message. In another example, the AMF may retrieve the first information through a Nudm_SDM_Subscribe service. Specifically, the first request message may be a nudm_sdm_subscnibe request message, and the first response message may be a nudm_sdm_subscnibe response message.

In another embodiment, the AMF retrieving the first information may include: the AMF may sign up to the UDM for a first event of the UE; in case the first event satisfies the first reporting condition, the AMF may receive subscription data from the UDM.

In an example, the first event may be time-triggered. For example, the first reporting condition may be that the UDM reaches a first time period after obtaining the subscription data. In this case, the UDM may transmit the subscription data to the AMF when the first time period is reached after the UDM obtains the subscription data of the UE. For another example, the first reporting condition may be a 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.

In another example, the first event may be event-triggered. For example, the first reporting condition may be that the UDM obtains subscription data. In this case, when the UDM obtains the subscription data of the UE, the UDM may transmit the subscription data to the AMF.

It will be appreciated that the first information may also include at least one of: the SMF selects subscription data (SMF selection subscription data), UE context data in the SMF (UE context in SMF data), location services mobile sources (LCS mobile origination, location service mobile origination). It should be noted that the first information may further include other information, which is not specifically limited in the embodiments of the present application.

S203, the AMF informs the UE that the registration is completed.

Wherein, after retrieving the first information in S202, the AMF may inform the UE that registration is completed.

It is appreciated that the AMF may send a registration response to the UE to inform the UE that registration is complete. Wherein the registration response may carry at least one of: 5G-GUTI, registration area (registration area). The registration area is used to represent the available tracking area and may include allowed nsais (network slice selection assistance information ) and S-nsais therein (single network slice selection assistance information, single network slice selection assistance information). It should be noted that the registration response may also carry other information, which is not specifically limited in the embodiments of the present application.

Note that the registration response may be carried in a registration accept message (registration accept message) (may also be referred to as a second response message). It should be noted that other information may also be carried in the registration accept message, which is not specifically limited in the embodiment of the present application.

Furthermore, the AMF may authenticate and authorize the UE before the AMF informs the UE that registration is complete.

S204, the AMF performs mobility management on the UE.

It can be appreciated that after S203, the UE registration is completed, and the AMF obtains the first information. Thus, the AMF may perform mobility management for the UE. In an embodiment, the AMF may perform mobility management for the UE according to the first information. It should be noted that the AMF may also perform other management on the UE, which is not specifically limited in the embodiments of the present application.

Up to this point, the procedure of mobility management of the UE by the AMF is completed through S201 to S204.

Fig. 3 is a flow chart of another management method of an internet of things device in an embodiment of the disclosure. The communication method can be applied to the communication system. For example, as shown in fig. 3, 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, and the third core network functional entity may be an SMF. The method may include: s301 to S310.

S301, the UE sends a PDU session establishment request to the AMF.

Wherein the PDU session establishment request (PDU session establishment request) is used to initiate a PDU session establishment procedure.

It is appreciated that the UE may send a NAS message (also referred to as a second request message) to the AMF, where the NAS message carries the PDU session establishment request.

The PDU session establishment request may be carried in a NAS message, such as a PDU session establishment request message. In one embodiment, the PDU session establishment request message is encapsulated in an N1SM container (N1 SM container) in an uplink non-access stratum message (UL NAS message). Of course, other information may also be included in the UL NAS message, which is not limited by the embodiments of the present disclosure.

S302, AMF selects SMF.

Wherein, after receiving the PDU session establishment request in S302, the AMF selects the SMF according to the PDU session establishment request. Specific details may be found in 3gpp TS 23.502, which is not described here in detail.

S303, the AMF sends a session management context creation request to the SMF.

Wherein a session management context creation request (which may also be referred to as a third request message) is used to request creation of a PDU session.

It is understood that the AMF may store the first information. The first information includes subscription data of the UE. The subscription data may be, for example, access and mobility subscription data. The first information may be carried in a session management context creation request message or may be otherwise sent by the AMF to the SMF.

In an example, in the case where the UE is an internet of things device dedicated for positioning, the subscription data may include subscription data of the internet of things device dedicated for positioning. In another example, in the case that the UE is an internet of things device including a positioning function and other functions, the subscription data may include subscription data of the internet of things device, which is dedicated to positioning, and may also include other subscription data.

In practical applications, the subscription data may be acquired in advance by the AMF. For example, the AMF may obtain subscription data from the UDM during registration of the UE.

In an embodiment, the first information may be carried in a session management context creation request message. Specifically, the AMF may send an nsmf_pduse_createsmcontext request to the SMF.

It will be appreciated that the session management context creation request message may also carry other information, such as SUPI, DNN (data network name ), S-NSSAI, N1 SM container.

In another embodiment, the SMF may sign up to the AMF for the second event of the UE. In this case, when the second time satisfies the second reporting condition, the AMF may transmit the subscription data of the UE to the SMF.

In an example, the second event may be time-triggered. For example, the second reporting condition may be that the AMF reaches a third duration after obtaining the subscription data. In this case, the AMF may transmit the subscription data to the SMF when the third duration is reached after the AMF obtains the subscription data of the UE. For another example, the second reporting condition may be a fourth time period. In this case, the AMF sends the subscription data to the SMF every time a timer in the AMF reaches the fourth time period.

In another example, the second event may be event-triggered. For example, the second reporting condition may be that the AMF obtains subscription data. In this case, when the AMF obtains the subscription data of the UE, the AMF may transmit the subscription data to the SMF. For another example, the second reporting condition may be that the AMF receives a request from the SMF. In this case, when the AMF receives the request, the AMF may transmit the subscription data to the SMF.

S304, the SMF retrieves the first information.

Wherein the first information may include subscription data of the UE.

It will be appreciated that after receiving the first information from the SMF, the AMF may first determine whether the session management subscription data corresponding to SUPI, DNN, S-NSSAI of the HPLMN (home public land mobile network, local public land mobile network) is available. If yes, the session management subscription data is used. If not, it means that the SMF needs to obtain new session management subscription data.

In the latter case, the SMF may retrieve the first information. At this time, the subscription data in the first information is session subscription data.

It will be appreciated that the SMF may retrieve the first information through a service between the SMF and the UDM.

In an embodiment, 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 subscription data. The subscription data is obtained by the UDM in response to the fourth response message by looking up locally.

In one example, the SMF may retrieve the first information through the nudm_sdm_get service. Specifically, the fourth request message may be a nudm_sdm_get request message, and the fourth response message may be a nudm_sdm_get response message. In another example, the SMF may retrieve the first information through the nudm_sdm_subscnibe service. Specifically, the fourth request message may be a nudm_sdm_subscnibe request message, and the fourth response message may be a nudm_sdm_subscnibe response message.

In another embodiment, the SMF retrieving the first information may include: the SMF may sign up to the UDM for a third event for the UE; in case the third event fulfils a third reporting condition, the SMF may receive subscription data from the UDM.

In an example, the third event may be time-triggered. For example, the third reporting condition may be that the UDM reaches a fifth duration after obtaining the subscription data. In this case, when the fifth duration is reached after the UDM obtains the subscription data of the UE, the UDM may transmit the subscription data to the SMF. For another example, the third reporting condition may be a sixth time period. In this case, the UDM sends the subscription data to the SMF each time a timer in the UDM reaches the sixth duration.

In another example, the third event may be event-triggered. For example, the third reporting condition may be that the UDM gets subscription data. In this case, when the UDM obtains the subscription data of the UE, the UDM may transmit the subscription data to the SMF.

In practical applications, the first information may be stored on the UDM or may be obtained by the UDM from the UDR. In the latter case, the UDM may obtain subscription data from the UDR through the nudr_dm_query service or the nudr_dm_subscnibe service.

It should be noted that S304 is not necessary. As described previously, S304 need not be performed until the AMF can first determine that session management subscription data corresponding to SUPI, DNN, S-NSSAI of the HPLMN is not available.

S305, the SMF sends a session management context creation response to the AMF.

Wherein a session management context creation response (which may also be referred to as a third response message) is used to indicate that the SMF successfully created a session management context (SM context).

Thus, the session management context creation response carries a session management context representation (SM context ID) for identifying the created session management context.

S306, SMF initiates an N4 session establishment flow to UPF.

The N4 session establishment procedure is used for establishing a PDU session for the UE.

The N4 session establishment procedure may specifically include: the SMF sends N4 session establishment request to the UPF and receives N4 session establishment response from the UPF.

S307, the SMF sends namf_communication_n1n2message Transfer to the AMF.

Wherein, the namf_communication_n1n2message Transfer carries the IP address allocated to the UE. The IP address is used to enable PDU sessions for the UE.

S308, the AMF sends an N2 PDU session request to the gNB.

Wherein the N2 PDU session request (N2 PDU session request) may be carried in a NAS message. The N2 PDU session request includes an IP address assigned to the UE.

S309, the gNB notifies the UE of PDU session establishment completion.

Wherein, the gNB notifies PDU session establishment completion by sending a PDU session establishment acceptance message. The PDU session establishment acceptance message may be carried in a NAS message forwarded by the gNB and include the IP address assigned to the UE.

It should be noted that, specific details of S305 to S309 may be referred to 3gpp TS 23.502, and are not described herein.

S310, the SMF performs session management on the UE.

It can be appreciated that after S310, the PDU session establishment of the UE is completed and the SMF obtains the first information. Thus, the SMF can perform session management for the UE. In an embodiment, the SMF may perform session management for the UE according to the first information. It should be noted that the SMF may also perform other management on the UE, which is not specifically limited in the embodiments of the present application.

So far, through S301 to S310, the session management process of the SMF to the UE is completed.

It will be appreciated that in the embodiments illustrated in fig. 2 and 3, other operations and/or flows may be included. Specific details of these operations and/or flows may be found in 3gpp TS 23.502, which is not described here in detail.

In the embodiment of the present disclosure, a core network functional entity in a mobile network may obtain subscription data of an internet of things device, where the subscription data is subscription data for a positioning service; the core network functional entity can manage the internet of things equipment based on the subscription data, or send the subscription data to another core network functional entity to manage the internet of things equipment. In this way, the mobile network can support the internet of things device for the location service, and thus can implement the location service for the internet of things device.

Based on the same inventive concept, the present disclosure provides a management method of an internet of things device. The method may be applied to a first core network device, e.g. an AMF. The method comprises the following steps: the method comprises the steps that a first core network functional entity receives first information from a second core network functional entity, wherein the first information comprises subscription data of Internet of things equipment for positioning services; the first core network functional entity performs at least one of: according to the first information, mobility management is conducted on the Internet of things equipment; and sending the first information to a third core network functional entity, wherein the first information is also used for session management of the Internet of things equipment by the third core network functional entity.

Based on the same inventive concept, the present disclosure provides a management method of an internet of things device. The method may be applied to a third core network device, e.g. an SMF. The method comprises the following steps: the third core network functional entity receives first information, wherein the first information comprises subscription data of the Internet of things equipment for positioning service; and the third core network functional entity performs session management on the Internet of things equipment according to the first information.

Based on the same inventive concept, the present disclosure provides a management apparatus of an internet of things device. The device may be a first core network functional entity (such as an AMF) or a chip or a system on a chip therein, and may also be a functional module in the first core network functional entity for implementing the method described in the above aspects. The device can realize the functions executed by the first core network functional entity in the aspects, and the functions can be realized by hardware executing corresponding software. Such hardware or software includes one or more modules corresponding to the functions described above.

Fig. 4 is a schematic structural diagram of a management device of an internet of things device in an embodiment of the disclosure. As shown in fig. 4, the apparatus 400 includes: the receiving module 401 is configured to receive first information from the second core network functional entity, where the first information includes subscription data of the internet of things device for the positioning service. The apparatus further comprises at least one of: the processing module 402 is configured to perform mobility management on the internet of things device according to the first information; the sending module 403 is configured to send the first information to the third core network functional entity, where the first information is further used for session management of the internet of things device by the third core network functional entity.

In some possible implementations, the sending module 403 may be further configured to: sending a first request message to a second core network functional entity, wherein the first request message is used for requesting subscription data; the receiving module 401 may be configured to: and receiving a first response message sent by the second core network functional entity, wherein the first response message carries subscription data.

In some possible implementations, the sending module 403 may be configured to: signing the first time of the internet of things device to the second core network functional entity; the receiving module 401 may be configured to: and under the condition that the first event meets the first reporting condition, receiving the subscription data sent by the second core network functional entity.

In some possible implementations, the receiving module 401 may be further configured to: and receiving a second request message sent by the Internet of things equipment, wherein the second request message carries a first equipment identifier, and the first equipment identifier is used for indicating the Internet of things equipment.

In some possible implementations, the sending module 403 may be configured to: and sending a third request message to a third core network functional entity, wherein the third request message carries subscription data.

It should be noted that, the specific implementation processes of the receiving module 401, the processing module 402, and the sending module 403 may refer to the detailed descriptions of the embodiments of fig. 2 and fig. 3, and are not repeated herein for brevity of description.

Based on the same inventive concept, the present disclosure provides a management apparatus of an internet of things device. The device may be a third core network functional entity (such as SMF) or a chip or a system on a chip therein, and may also be a functional module in the third core network functional entity for implementing the method described in the above aspects. The device can realize the functions executed by the third core network functional entity in the aspects, and the functions can be realized by hardware executing corresponding software. Such hardware or software includes one or more modules corresponding to the functions described above.

Fig. 5 is a schematic structural diagram of a management apparatus of another internet of things device in an embodiment of the disclosure. As shown in fig. 5, the apparatus 500 includes: a receiving module 501 configured to receive first information, where the first information includes subscription data of an internet of things device for a location service; and the processing module 502 performs session management on the internet of things equipment according to the first information.

In some possible implementations, the receiving module 501 may be configured to: and receiving a third request message from the first core network functional entity, wherein the third request message carries subscription data.

In some possible embodiments, the apparatus 500 may further include: a sending module 503 configured to sign up a second event of the internet of things device to the first core network functional entity; the receiving module 501 may be configured to: and receiving the subscription data sent by the first core network functional entity under the condition that the second event meets the second reporting condition.

In some possible embodiments, the apparatus 500 may further 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 to: and receiving a fourth response message sent by the second core network functional entity, wherein the fourth response message carries subscription data.

In some possible embodiments, the apparatus 500 may further include: a sending module 503 configured to sign up a third event of the internet of things device to the second core network functional entity; the receiving module 501 may be configured to: and receiving the subscription data sent by the second core network functional entity under the condition that the third event meets the third reporting condition.

It should be noted that, the specific implementation processes of the receiving module 501, the processing module 502 and the sending module 503 may refer to the detailed descriptions of the embodiments of fig. 2 and fig. 3, and are not repeated herein for brevity of description.

Based on the same inventive concept, embodiments of the present disclosure provide a network functional entity that is identical to the core network functional entity in one or more of the embodiments described above.

Fig. 6 is a schematic structural diagram of a network functional entity in an embodiment of the disclosure. As shown in fig. 6, network function entity 600 may include a processing component 601 that further includes one or more processors and memory resources represented by memory 602 for storing instructions, such as applications, executable by processing component 601. The application program stored in the memory 602 may include one or more modules each corresponding to a set of instructions. Furthermore, the processing component 601 is configured to execute instructions to perform any of the methods described above as applied to network functional entities.

The network function entity 600 may also include a power 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 a network, and an input output (I/O) interface 605. The network function entity 600 may operate based on an operating system stored in the memory 602, such as Windows Server TM, mac OS XTM, unixTM, linuxTM, freeBSDTM or the like.

Based on the same inventive concept, the embodiment of the disclosure also provides an electronic device. The electronic device includes: a memory; a processor coupled to the memory and configured to execute computer-executable instructions stored on the memory to perform the method of the first core network functional entity or the third core network functional entity of one or more embodiments described above.

Based on the same inventive concept, the embodiments of the present disclosure also provide a computer-readable storage medium having instructions stored therein; the instructions, when executed on a computer, are configured to perform the method of the first core network functional entity or the third core network functional entity of one or more embodiments described above.

Based on the same inventive concept, the embodiments of the present disclosure also provide a computer program or a computer program product, which when executed on a computer, causes the computer to implement the method of the first core network functional entity or the third core network functional entity in one or more embodiments described above.

Other embodiments of the invention will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of the invention following, in general, the principles of the invention and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the invention being indicated by the following claims.

It is to be understood that the invention is not limited to the precise arrangements and instrumentalities shown in the drawings, which have been described above, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the invention is limited only by the appended claims.

Claims

A method for managing internet of things devices, comprising:

the method comprises the steps that a first core network functional entity receives first information from a second core network functional entity, wherein the first information comprises subscription data of Internet of things equipment for positioning services;

the first core network functional entity performs at least one of:

according to the first information, mobility management is conducted on the Internet of things equipment;

and sending the first information to a third core network functional entity, wherein the first information is also used for session management of the Internet of things equipment by the third core network functional entity.
The method of claim 1, wherein the first core network functional entity receiving the first information from the second core network functional entity comprises:

the first core network functional entity sends a first request message to the second core network functional entity, wherein the first request message is used for requesting the subscription data;

The first core network functional entity receives a first response message sent by the second core network functional entity, wherein the first response message carries the subscription data.
The method of claim 1, wherein the first core network functional entity receiving the first information from the second core network functional entity comprises:

the first core network functional entity signs up a first event of the Internet of things equipment to the second core network functional entity;

and under the condition that the first event meets a first reporting condition, the first core network functional entity receives the subscription data sent by the second core network functional entity.
The method of claim 1, wherein the method further comprises:

the first core network functional entity receives a second request message sent by the Internet of things device, wherein the second request message carries a first device identifier, and the first device identifier is used for indicating the Internet of things device.
The method of claim 4, wherein the second request message is a registration request message.
The method of claim 1, wherein the first core network functional entity sending the first information to a third core network functional entity comprises:

The first core network functional entity sends the third request message to the third core network functional entity, wherein the third request message carries the subscription data.
The method of claim 6, wherein the third request message is a session management context creation request message.
A method for managing internet of things devices, comprising:

the third core network functional entity receives first information, wherein the first information comprises subscription data of the Internet of things equipment for positioning service;

and the third core network functional entity performs session management on the Internet of things equipment according to the first information.
The method of claim 8, wherein the third core network functional entity receives first information, comprising:

the third core network functional entity receives a third request message from the first core network functional entity, wherein the third request message carries the subscription data.
The method of claim 9, wherein the third request message is a session management context creation request message.
The method of claim 8, wherein the third core network functional entity receives first information, comprising:

The third core network functional entity signs up a second event of the Internet of things device to the first core network functional entity;

and under the condition that the second event meets a second reporting condition, the third core network functional entity receives the subscription data sent by the first core network functional entity.
The method of claim 8, wherein the third core network functional entity receives first information, comprising:

the third core network functional entity sends a fourth request message to the second core network functional entity, wherein the fourth request message is used for requesting the subscription data;

the third core network functional entity receives a fourth response message sent by the second core network functional entity, wherein the fourth response message carries the subscription data.
The method of claim 8, wherein the third core network functional entity receives first information, comprising:

the third core network functional entity signs up a third event of the Internet of things device to the second core network functional entity;

and under the condition that the third event meets a third reporting condition, the third core network functional entity receives the subscription data sent by the second core network functional entity.
A management apparatus of an internet of things device, comprising:

the receiving module is configured to receive first information from a second core network functional entity, wherein the first information comprises subscription data of the Internet of things equipment for positioning service;

the apparatus further comprises at least one of:

the processing module is configured to perform mobility management on the Internet of things equipment according to the first information;

the sending module is configured to send the first information to a third core network functional entity, and the first information is also used for session management of the internet of things equipment by the third core network functional entity.
A management apparatus of an internet of things device, comprising:

the device comprises a receiving module, a processing module and a processing module, wherein the receiving module is configured to receive first information, and the first information comprises subscription data of the internet of things equipment, which is used for positioning service;

and the processing module is used for carrying out session management on the Internet of things equipment according to the first information.
An electronic device, comprising: a memory; a processor, coupled to the memory, configured to execute computer-executable instructions stored on the memory to implement the method of any one of claims 1 to 7, or claims 8 to 13.
A computer storage medium storing computer executable instructions which, when executed by a processor, are capable of carrying out the method of any one of claims 1 to 7 or 8 to 13.