WO2020147681A1 - 终端设备的标签管理方法和装置 - Google Patents

终端设备的标签管理方法和装置 Download PDF

Info

Publication number
WO2020147681A1
WO2020147681A1 PCT/CN2020/071790 CN2020071790W WO2020147681A1 WO 2020147681 A1 WO2020147681 A1 WO 2020147681A1 CN 2020071790 W CN2020071790 W CN 2020071790W WO 2020147681 A1 WO2020147681 A1 WO 2020147681A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal device
type
network
label
information
Prior art date
Application number
PCT/CN2020/071790
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 EP20741824.5A priority Critical patent/EP3910973A4/en
Priority to AU2020208514A priority patent/AU2020208514A1/en
Publication of WO2020147681A1 publication Critical patent/WO2020147681A1/zh
Priority to US17/378,169 priority patent/US20210344410A1/en

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W8/00Network data management
    • H04W8/02Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04BTRANSMISSION
    • H04B7/00Radio transmission systems, i.e. using radiation field
    • H04B7/14Relay systems
    • H04B7/15Active relay systems
    • H04B7/185Space-based or airborne stations; Stations for satellite systems
    • H04B7/18502Airborne stations
    • H04B7/18506Communications with or from aircraft, i.e. aeronautical mobile service
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04BTRANSMISSION
    • H04B7/00Radio transmission systems, i.e. using radiation field
    • H04B7/14Relay systems
    • H04B7/15Active relay systems
    • H04B7/185Space-based or airborne stations; Stations for satellite systems
    • H04B7/18502Airborne stations
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W24/00Supervisory, monitoring or testing arrangements
    • H04W24/10Scheduling measurement reports ; Arrangements for measurement reports
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W48/00Access restriction; Network selection; Access point selection
    • H04W48/02Access restriction performed under specific conditions
    • H04W48/04Access restriction performed under specific conditions based on user or terminal location or mobility data, e.g. moving direction, speed
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W8/00Network data management
    • H04W8/02Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08Mobility data transfer

Definitions

  • This application relates to communication technology, and in particular to a method and device for label management of terminal equipment.
  • Unmanned aircraft is abbreviated as "UAV", which is an unmanned aircraft operated by radio remote control equipment and self-provided program control devices. In order to regulate the operation and flight of UAVs, it is necessary to supervise UAVs.
  • the mobile communication network can be used to supervise drones.
  • terminal equipment such as smart phones and on-board equipment in the mobile communication network.
  • the premise of supervising drones is to identify drones.
  • This application provides a method and device for label management of terminal equipment to avoid repetitive identification of the type of terminal equipment.
  • the first aspect of the present application provides a label management method for terminal equipment, including:
  • the first network device obtains the type of the terminal device, and the type of the terminal device includes a drone, a non-UAV, or an undetermined type;
  • the first network device sends a request message to the label management device, the request message is used to request the label management device to create a type label for the terminal device, and the request message includes the identification of the terminal device.
  • the first network device acquiring the type of the terminal device includes:
  • the first network device receives a report message sent by a second network device, where the report message is used to report the type of the terminal device.
  • the first network device acquiring the type of the terminal device includes:
  • the first network device obtains the type of the terminal device according to the information of the terminal device.
  • the information of the terminal device includes one or more of the following information: capability information of the terminal device, subscription information of the terminal device, type label information of the terminal device, and The measurement information of the terminal device, the location information of the terminal device, and the type of cell that the terminal device accesses.
  • the method before the first network device obtains the type of the terminal device, the method further includes:
  • the acquiring, by the first network device, the type of the terminal device includes:
  • the first network device obtains the type of the associated terminal device according to the identification instruction message.
  • the method before the first network device obtains the type of the terminal device, the method further includes:
  • the first network device receives an identification instruction message from a second network device, the identification instruction message includes the identification of the terminal device, and the identification instruction message is used to instruct the first network device to respond to the terminal device Type of identification;
  • the acquiring, by the first network device, the type of the terminal device includes:
  • the first network obtains the type of the terminal device according to the identification instruction message.
  • the first network device acquiring the type of terminal device includes:
  • the first network device determines the type of the terminal device according to the type model and the measurement characteristic data.
  • the request message further includes type information of the terminal device.
  • the method further includes:
  • the first network device receives a response message sent by the label management device, and the response message includes a label creation result.
  • the method further includes:
  • the first network device receives a tag query response sent by the tag management device, and the tag query response includes a type tag of the terminal device.
  • the method further includes:
  • the first network device sends a report message to the UTM, and the report message includes the identification and location information of the terminal device.
  • the first network device is a mobility management entity MME, a base station, an access and mobility management function AMF network element, or a network data analysis function NWDAF network element.
  • the first network equipment mobility management entity MME, and the second network equipment is a base station; or,
  • the first network device is an access and mobility management function AMF network element
  • the second network device is an NWDAF network element or a base station.
  • a second aspect of the present application provides a label management method for terminal equipment, including:
  • the label management device receives a request message sent by the first network device, the request message is used to request the label management device to create a type label for the terminal device, and the request message includes the identification of the terminal device;
  • the tag management device creates a type tag for the terminal device according to the request message, and the type tag of the terminal device includes a drone, a non-UAV, or an undetermined type tag.
  • the request message further includes type information of the terminal device.
  • the method further includes:
  • the label management device sends a response message to the first network device, and the response message includes a label creation result.
  • the label management device sends a label query response to the first network device, and the label query response includes the type label of the terminal device.
  • the first network device is a mobility management entity MME, a base station, an access and mobility management function AMF network element, or a network data analysis function NWDAF network element.
  • the third aspect of the present application provides a label management method for terminal equipment, including:
  • the first network device obtains the type of the terminal device, and the type of the terminal device includes a drone, a non-UAV, or an undetermined type;
  • the first network device sends a report message to the second network device, where the report message is used to report the type of the terminal device.
  • the first network device acquiring the type of the terminal device includes:
  • the first network device receives a report message sent by a second network device, where the report message is used to report the type of the terminal device.
  • the first network device acquiring the type of the terminal device includes:
  • the first network device obtains the type of the terminal device according to the information of the terminal device.
  • the information of the terminal device includes one or more of the following information: capability information of the terminal device, subscription information of the terminal device, type label information of the terminal device, and The measurement information of the terminal device, the location information of the terminal device, and the type of cell that the terminal device accesses.
  • the method before the first network device obtains the type of the terminal device, the method further includes:
  • the acquiring, by the first network device, the type of the terminal device includes:
  • the first network device obtains the type of the associated terminal device according to the identification instruction message.
  • the method before the first network device obtains the type of the terminal device, the method further includes:
  • the first network device receives an identification instruction message from a second network device, the identification instruction message includes the identification of the terminal device, and the identification instruction message is used to instruct the first network device to respond to the terminal device Type of identification;
  • the acquiring, by the first network device, the type of the terminal device includes:
  • the first network obtains the type of the terminal device according to the identification instruction message.
  • the second network device is a mobility management entity MME or a mobility management function AMF network element; or,
  • the second network device is an AMF network element.
  • a fourth aspect of the present application provides a label management method for terminal equipment, including:
  • the first network device obtains the type of the terminal device, and the type of the terminal device includes a drone, a non-UAV, or an undetermined type;
  • the first network device sends a request message to a label management device, the request message is used to request the label management device to create a type label for the terminal device, and the request message includes an identifier of the terminal device;
  • the tag management device creates a type tag for the terminal device according to the request message, and the type tag of the terminal device includes a drone, a non-UAV, or an undetermined type tag.
  • the first network device acquiring the type of the terminal device includes:
  • the first network device obtains the type of the terminal device according to the information of the terminal device.
  • the first network device acquiring the type of the terminal device includes:
  • the first network device receives a report message sent by a second network device, where the report message is used to report the type of the terminal device.
  • the method further includes:
  • the second network device recognizes the instruction message to the first network device, where the recognition instruction message is used to instruct the first network device to recognize the type of the associated terminal device;
  • acquiring the type of the terminal device by the first network device includes:
  • the first network device obtains the type of the associated terminal device according to the identification instruction message.
  • the method further includes:
  • the second network device identifies an instruction message to the first network device, the identification instruction message includes the identification of the terminal device, and the identification instruction message is used to instruct the first network device to identify the type of the terminal device ;
  • acquiring the type of the terminal device by the first network device includes:
  • the first network obtains the type of the terminal device according to the identification instruction message.
  • the first network device acquiring the type of the terminal device includes:
  • the first network device determines the type of the terminal device according to the type model and the measurement characteristic data.
  • the request message further includes type information of the terminal device.
  • the method further includes:
  • the label management device sends a response message to the first network device, and the response message includes a label creation result.
  • the method further includes:
  • the label management device sends a label query response to the first network device, and the label query response includes the type label of the terminal device.
  • the method further includes:
  • the first network device sends a report message to the UTM, and the report message includes the identification and location information of the terminal device.
  • a fifth aspect of the present application provides a label management method for terminal equipment, including:
  • the first network device obtains the type of the terminal device, and the type of the terminal device includes a drone, a non-UAV, or an undetermined type;
  • the second network device sends the report message to the drone server.
  • the first network device acquiring the type of the terminal device includes:
  • the first network device receives a report message sent by a second network device, where the report message is used to report the type of the terminal device.
  • the method further includes:
  • the second network device sends an identification instruction message to the first network device, where the identification instruction message is used to instruct the first network device to identify the type of associated terminal device;
  • the acquiring, by the first network device, the type of the terminal device includes:
  • the first network device obtains the type of the associated terminal device according to the identification instruction message.
  • the method further includes:
  • the second network device sends an identification instruction message to the first network device, where the identification instruction message includes the identification of the terminal device, and the identification instruction message is used to instruct the first network device to control the terminal device Type recognition;
  • the acquiring, by the first network device, the type of the terminal device includes:
  • the first network device obtains the type of the terminal device according to the identification instruction message.
  • a sixth aspect of this application provides a network device, including:
  • the acquisition module is used to acquire the type of terminal equipment, the type of the terminal equipment includes drone, non-UAV or undetermined type;
  • the sending module is configured to send a request message to the label management device, the request message is used to request the label management device to create a type label for the terminal device, and the request message includes the terminal device identifier.
  • the obtaining module is specifically configured to:
  • the obtaining module is specifically configured to:
  • the information of the terminal device includes one or more of the following information: capability information of the terminal device, subscription information of the terminal device, type label information of the terminal device, and The measurement information of the terminal device, the location information of the terminal device, and the type of cell that the terminal device accesses.
  • the device further includes:
  • a receiving module configured to receive an identification instruction message from a second network device, where the identification instruction message is used to instruct the first network device to identify the type of associated terminal device;
  • the obtaining module is specifically used for:
  • the device further includes:
  • the receiving module is configured to receive an identification instruction message from a second network device, the identification instruction message includes the identification of the terminal device, and the identification instruction message is used to instruct the first network device to contact the terminal device Type recognition;
  • the obtaining module is specifically used for:
  • the obtaining module is specifically configured to:
  • the type of the terminal device is determined.
  • the request message further includes type information of the terminal device.
  • the device further includes:
  • the receiving module is configured to receive a response message sent by the label management device, and the response message includes the label creation result.
  • the device further includes:
  • the sending module is further configured to send a label query request to the label management device, and the label query request includes the identification of the terminal device;
  • the receiving module is configured to receive a label query response sent by the label management device, and the label query response includes the type label of the terminal device.
  • the sending module is further used for:
  • the network equipment is a mobility management entity MME, a base station, an access and mobility management function AMF network element, or a network data analysis function NWDAF network element.
  • the network equipment mobility management entity MME, and the second network equipment is a base station; or,
  • the network device is an access and mobility management function AMF network element
  • the second network device is an NWDAF network element or a base station.
  • a seventh aspect of the present application provides a label management device, including:
  • a receiving module configured to receive a request message sent by a first network device, where the request message is used to request the label management device to create a type label for the terminal device, and the request message includes the identification of the terminal device;
  • the creation module is configured to create a type label for the terminal device according to the request message, and the type label of the terminal device includes a drone, a non-drone or an undetermined type label.
  • the request message further includes type information of the terminal device.
  • the method further includes:
  • the label management device sends a response message to the first network device, and the response message includes a label creation result.
  • it further includes a sending module
  • the receiving module is further configured to receive a tag query request sent by the first network device, where the tag query request includes the identification of the terminal device;
  • the sending module is configured to send a label query response to the first network device, and the label query response includes the type label of the terminal device.
  • the first network device is a mobility management entity MME, a base station, an access and mobility management function AMF network element, or a network data analysis function NWDAF network element.
  • the eighth aspect of the present application provides a network device, including:
  • the acquisition module is used to acquire the type of terminal equipment, the type of the terminal equipment includes drone, non-UAV or undetermined type;
  • the sending module is configured to send a report message to the second network device, where the report message is used to report the type of the terminal device.
  • the obtaining module is specifically configured to:
  • the acquiring module is specifically configured to:
  • the information of the terminal device includes one or more of the following information: capability information of the terminal device, subscription information of the terminal device, type label information of the terminal device, and The measurement information of the terminal device, the location information of the terminal device, and the type of cell that the terminal device accesses.
  • the device further includes:
  • a receiving module configured to receive an identification instruction message from a second network device, where the identification instruction message is used to instruct the first network device to identify the type of associated terminal device;
  • the obtaining module is specifically used for:
  • the device further includes:
  • the receiving module is configured to receive an identification instruction message from a second network device, the identification instruction message includes the identification of the terminal device, and the identification instruction message is used to instruct the first network device to contact the terminal device Type recognition;
  • the obtaining module is specifically used for:
  • the first network obtains the type of the terminal device according to the identification instruction message.
  • the second network device is a mobility management entity MME or a mobility management function AMF network element; or,
  • the second network device is an AMF network element.
  • a ninth aspect of the present application provides a network device, including a processor, a memory, and a transceiver.
  • the memory is used to store instructions
  • the transceiver is used to communicate with other devices
  • the processor is used to execute data stored in the memory. Instructions to make the network device execute the method according to any one of the first aspect of the present application.
  • a tenth aspect of the present application provides a label management device, including a processor, a memory, and a transceiver.
  • the memory is used to store instructions
  • the transceiver is used to communicate with other devices
  • the processor is used to execute storage in the memory.
  • An eleventh aspect of the present application provides a network device, including a processor, a memory, and a transceiver.
  • the memory is used to store instructions
  • the transceiver is used to communicate with other devices
  • the processor is used to execute storage in the memory.
  • a twelfth aspect of the present application provides a computer-readable storage medium that stores instructions that, when executed, cause a computer to execute the method described in any one of the first aspects of the present application .
  • a thirteenth aspect of the present application provides a computer-readable storage medium, the computer-readable storage medium stores instructions, and when the instructions are executed, the computer executes the method according to any one of the second aspects of the present application .
  • a fourteenth aspect of the present application provides a computer-readable storage medium that stores instructions that, when executed, cause a computer to execute the method described in any one of the third aspect of the present application .
  • a fifteenth aspect of the present application provides a computer program product.
  • the computer program product includes instructions that, when executed, cause a computer to execute the method according to any one of the first aspects of the present application.
  • a sixteenth aspect of the present application provides a computer program product.
  • the computer program product includes instructions that, when executed, cause a computer to execute the method according to any one of the second aspects of the present application.
  • a seventeenth aspect of the present application provides a computer program product.
  • the computer program product includes instructions that, when executed, cause a computer to execute the method according to any one of the third aspects of the present application.
  • the eighteenth aspect of the present application provides a system on a chip or a system chip, which can be applied to a network device, and the system on a chip or a system chip includes: at least one communication interface, at least one processor, At least one memory, the communication interface, the memory, and the processor are interconnected by a bus, and the processor executes the instructions stored in the memory so that the network device can execute any one of the first aspect and the third aspect of the present application The method described in the aspect.
  • a nineteenth aspect of the present application provides a system on a chip or a system chip, which can be applied to a label management device, and the system on a chip or a system chip includes: at least one communication interface, at least one processor At least one memory, the communication interface, the memory, and the processor are interconnected by a bus, and the processor executes the instructions stored in the memory to enable the label management device to execute the method described in the second aspect of the present application.
  • the twentieth aspect of the present application provides a communication system, including a first network device and a label management device, the first network device is configured to execute the method according to any one of the first aspect of the present invention, and the label management device uses To implement the method described in any one of the second aspect of the present application.
  • the communication system further includes a terminal device and the aforementioned second network device.
  • the communication system further includes the aforementioned UAV server.
  • This application provides a method and device for label management of terminal devices.
  • the method includes: a first network device obtains the type of the terminal device, the type of the terminal device includes a drone, a non-drone or an undetermined type, and the first network
  • the device sends a request message to the label management device, the request message is used to request the label management device to create a type label for the terminal device, and the request message includes the identification of the terminal device.
  • the label management device creates and saves the type label for the terminal device, and subsequently the first network device or other device can query the type label of the terminal device through the identification of the terminal device, thereby avoiding repeated identification of the type of the terminal device.
  • Figure 1 is a schematic diagram of an existing 5G network architecture
  • Figure 2 is a schematic diagram of a 5G network architecture based on a service-oriented interface
  • Figure 3 is a schematic diagram of a 5G network architecture based on terminal device positioning
  • FIG. 4 is a schematic diagram of an LTE network architecture
  • Figure 5 is a schematic diagram of an LTE network architecture based on terminal device positioning
  • Figure 6 is another schematic diagram of a 5G network architecture based on a service-oriented interface
  • FIG. 7 is another schematic diagram of the LTE network architecture
  • FIG. 8 is a flowchart of a method for label management of a terminal device according to Embodiment 1 of this application;
  • FIG. 9 is a flowchart of a method for label management of a terminal device according to Embodiment 2 of this application.
  • FIG. 10 is a signaling flow chart of a method for label management of a terminal device according to Embodiment 3 of this application;
  • FIG. 11 is a signaling flow chart of a method for label management of a terminal device according to Embodiment 4 of this application;
  • FIG. 12 is a signaling flowchart of a method for label management of a terminal device according to Embodiment 5 of this application;
  • FIG. 13 is a signaling flow chart of a method for label management of terminal equipment according to Embodiment 6 of this application;
  • FIG. 14 is a signaling flowchart of a method for label management of terminal equipment according to Embodiment 7 of the application;
  • FIG. 16 is a schematic structural diagram of a network device provided in Embodiment 9 of this application.
  • FIG. 17 is a schematic structural diagram of a label management device provided by Embodiment 10 of this application.
  • FIG. 18 is a schematic structural diagram of a network device provided in Embodiment 11 of this application.
  • FIG. 19 is a schematic structural diagram of a network device provided in Embodiment 12 of this application.
  • FIG. 20 is a schematic structural diagram of a label management device provided by Embodiment 13 of this application.
  • This application provides a method for label management of terminal equipment.
  • the method of this application can be applied to the fifth generation mobile communication (5 Generation, 5G) system, and can also be applied to the long term evolution (Long Term Evolution, LTE).
  • 5G system is also called It is a new wireless communication system, new access technology (New Radio, NR) or next-generation mobile communication system.
  • FIG. 1 is a schematic diagram of an existing 5G network architecture.
  • the 5G network architecture includes terminal equipment, access network (AN), core network and data network (DN).
  • the access network device is mainly used to implement wireless physical layer functions, resource scheduling and wireless resource management, wireless access control, and mobility management;
  • the core network equipment can include management equipment and gateway equipment, and the management equipment is mainly used for terminals Device registration, security authentication, mobility management and location management of the device.
  • the gateway device is mainly used to establish a channel with the terminal device, and forward the data packet between the terminal device and the external data network on the channel;
  • the data network can include the network Equipment (such as servers, routers and other equipment), data networks are mainly used to provide a variety of data business services for terminal equipment.
  • the access network in the 5G system can be a radio access network (radio access network, (R)AN, and the (R)AN device in the 5G system can be composed of multiple 5G-(R)AN nodes.
  • the 5G-(R)AN ) AN nodes may include: non-3GPP access networks such as WiFi network access points (access points, AP), next-generation base stations (collectively referred to as next-generation radio access network nodes (NG-RAN nodes), where:
  • the first generation of base stations includes new air interface base stations (NR nodeB, gNB), new generation evolved base stations (NG-eNB), central unit (CU) and distributed unit (DU) separated forms of gNB, etc.), transceiver Point (transmission receive point, TRP), transmission point (transmission point, TP) or other nodes.
  • the 5G core network (5G core/new generation core, 5GC/NGC) includes access and mobility management function (Access and Mobility Management Function, AMF) network elements, session management function (Session Management Function, SMF) network elements, and user plane Function (User Plane Function, UPF) network element, Authentication Server Function (Authentication Server Function, AUSF) network element, Policy Control Function (PCF) network element, Application Function (AF) network element, unified Multiple functional units such as data management function (unified data management, UDM) network elements and network slice selection function (Network Slice Selection Function, NSSF) network elements.
  • AMF Access and Mobility Management Function
  • SMF Session Management Function
  • UPF User Plane Function
  • UPF User Plane Function
  • PCF Policy Control Function
  • AF Application Function
  • unified Multiple functional units such as data management function (unified data management, UDM) network elements and network slice selection function (Network Slice Selection Function, NSSF) network elements.
  • the AMF network element is mainly responsible for services such as mobility management and access management.
  • the SMF network element is mainly responsible for session management, dynamic host configuration protocol functions, selection and control of user plane functions, etc.
  • the UPF network element is mainly responsible for externally connected to the data network (DN) and user plane data packet routing and forwarding, message filtering, and performing quality of service (QoS) control related functions.
  • AUSF is mainly responsible for the authentication function of terminal equipment.
  • the PCF network element is mainly responsible for providing a unified policy framework for network behavior management, providing policy rules for control plane functions, and obtaining registration information related to policy decisions.
  • control and mobility management functions such as access authentication, security encryption, location registration for terminal devices, and users Session management functions such as the establishment, release, and change of the surface transmission path.
  • the functional units in the 5GC can communicate through the next generation network (NG) interface.
  • the UE can transmit control plane messages with the AMF network element through the NG interface 1 (N1 for short), and the RAN equipment can communicate through the NG interface.
  • Interface 3 (abbreviated as N3) establishes a user plane data transmission channel with UPF.
  • AN/RAN equipment can establish a control plane signaling connection with AMF network elements through NG interface 2 (abbreviated as N2), and UPF can communicate with UPF via NG interface 4 (abbreviated as N4).
  • UPF can exchange user plane data with data network DN through NG interface 6 (abbreviated as N6)
  • AMF network elements can exchange information with SMF network elements through NG interface 11 (abbreviated as N11)
  • SMF network elements can The NG interface 7 (abbreviated as N7) exchanges information with the PCF network element
  • the AMF network element can exchange information with the AUSF via the NG interface 12 (abbreviated as N12).
  • FIG. 1 is only an exemplary architecture diagram.
  • the network architecture may also include other functional units.
  • FIG. 2 is a schematic diagram of a 5G network architecture based on a service interface. As shown in Figure 2, under the architecture of a service interface, the core network of the 5G system also includes the Network Exposure Function (NEF) and network storage Function (Network Repository Function, NRF) network element.
  • NEF Network Exposure Function
  • NRF Network Repository Function
  • some network elements in the 5G core network are connected by bus, as shown in Figure 2, AUSF network elements, AMF network elements, SMF network elements, AF network elements, UDM, PCF network elements, NRF Network elements, NEF network elements, and NSSF network elements are interconnected via a bus.
  • AUSF network elements AMF network elements
  • SMF network elements SMF network elements
  • AF network elements AF network elements
  • UDM PCF network elements
  • NRF Network elements NRF Network elements
  • NEF network elements NEF network elements
  • NSSF network elements are interconnected via a bus.
  • AUSF network elements are connected to the bus through Nausf interfaces
  • AMF network elements use Namf interfaces Connected to the bus
  • SMF network elements are connected to the bus through the Nsmf interface
  • AF network elements are connected to the bus through the Naf interface
  • UDM is connected to the bus through the Nudm interface
  • PCF network elements are connected to the bus through the Npcf interface
  • NRF through the Nnrf The interface is connected to the bus
  • NEF is connected to the bus through the Nnef interface
  • the NSSF is connected to the bus through the Nnssf interface.
  • FIG 3 is a schematic diagram of a 5G network architecture based on terminal equipment positioning.
  • the network architecture includes: terminal equipment, RAN, core network, and external clients.
  • the core network elements include: AMF, UDM, Location Management Function (LMF), Gateway Mobile Location Center (GMLC), and Location Get the function entity (Location Retrieval Function, LRF).
  • LMF Location Management Function
  • GMLC Gateway Mobile Location Center
  • LRF Location Get the function entity
  • GLMC is used to support the location service of the 3GPP network. It is the first node of the external location program to access the network, performs registration authorization checks and requests routing information from UDM, and completes the registration. After the authorization check, the positioning request is sent to the AMF, and the final location estimate is received.
  • the LMF is used to determine the location of the terminal device, obtain downlink measurement information (location measurement) or the terminal device obtain location estimation, and obtain the uplink location measurement and non-terminal device-related auxiliary information from the RAN.
  • LRF is used to obtain location information related to terminal equipment for external clients, including the entity that requires location, temporary location information, initial location information, and updated location information.
  • LRF can interact with a separate GMLC, or it can be integrated with GMLC to obtain positioning information.
  • LRF can also interact or integrate with other types of location servers to obtain location information.
  • FIG 4 is a schematic diagram of the LTE network architecture.
  • the access network equipment in the LTE system is the eNB
  • the core network of the LTE system is the Evolved Packet Core (EPC).
  • the EPC includes: mobile Mobility management entity (MME), packet data gateway (packet data network gateway, P-GW), service gateway (Serving Gateway, S-GW), home network server (Home Subscriber Server, HSS), etc.
  • MME mobile Mobility management entity
  • P-GW packet data gateway
  • S-GW service gateway
  • HSS home network server
  • HSS is used to store user subscription information, including user service information, authentication information, location management information, etc.
  • MME is responsible for terminal access control, mobility management, session management, and network element selection (such as S-GW/P-GW Select) and other functions
  • SGW is the mobility anchor point for handover between eNBs, responsible for the routing and forwarding of user plane data
  • PGW is responsible for Internet Protocol (IP) address allocation, packet data filtering, rate control and billing The execution of rules and legal monitoring and other functions.
  • IP Internet Protocol
  • the terminal equipment in the 5G system and the LTE system is also called User Equipment (UE).
  • the terminal equipment can be a mobile phone, a computer, a cellular phone, a cordless phone, or a session initiation protocol (SIP) phone.
  • Smart phones wireless local loop (wireless local loop, WLL) stations, personal digital assistants (personal digital assistants, PDAs), computers, laptop computers, handheld communication devices, handheld computing devices, satellite wireless devices, wireless Modem cards, TV set top boxes (STB), in-vehicle devices, wearable devices, smart home devices, and other devices used to communicate on wireless systems, etc.
  • WLL wireless local loop
  • PDAs personal digital assistants
  • STB TV set top boxes
  • STB TV set top boxes
  • FIG. 5 is a schematic diagram of an LTE network architecture based on terminal device positioning.
  • the functions of GMLC and LRF are the same as those in the 5G network.
  • E-SMLC converts the location requirements requested by the client into corresponding E-UTRAN measurement parameters, and selects the location for the terminal device The method is to calculate the position estimation to obtain the final position information of the terminal device.
  • UAV control function UAV control function
  • UCF can support the following services: configure communication parameters to drones, obtain and distribute drone no-fly zones from UTM, drone flight assistance authorization, and receive UTM drone services (drone recognition, drone Position tracking, etc.) subscribe, and interact with other core network elements (MME, GMLC, etc.) to provide UTM with subscription drone services.
  • MME mobile mobile equipment
  • GMLC mobile virtualization control
  • the network element may also be a control network element added to the LTE system and the 5G system for providing services for application services: a service control function (SCF), which implements the function of UCF.
  • SCF service control function
  • the drone server is responsible for business management related to drone applications, and can include drone supervision related businesses, such as drone registration, flight plan approval, flight operation authorization, flight monitoring, flight warning, flight control, etc. It can also include the control and management of UAV application services, such as UAV data collection and video data management.
  • UAV application services such as UAV data collection and video data management.
  • the drone server can also include other value-added services, such as data analysis, weather notifications, etc.
  • the drone server can be regarded as an instance of an application function (AF) in the 5G system, or the drone server can be located in the DN as a third-party server.
  • AF application function
  • the drone server may also be referred to as the drone service provider USS (UAS service supplier), the drone traffic service UTS (UAS traffic service) or UTM server, or the drone traffic management platform.
  • USS UAS service supplier
  • UTS UTS traffic service
  • UTM server UTM server
  • FIG. 6 is another schematic diagram of a 5G network architecture based on a service-oriented interface. As shown in Figure 6, this embodiment has more UCF than the 5G network architecture shown in Figure 3. UCF communicates with other network elements in the network through a bus. Connect communication, UTM is integrated in DN.
  • Fig. 7 is another schematic diagram of the LTE network architecture. As shown in Fig. 7, this embodiment has more UCF network elements than the LTE network architecture shown in Fig. 4. The UCF network elements are compared with terminal equipment, MME and UAV respectively. Server connection.
  • Embodiment 1 of the present application provides a method for label management of terminal devices.
  • FIG. 8 is a flowchart of the method for label management of terminal devices according to Embodiment 1 of this application, as shown in FIG. 8 As shown, the method provided in this embodiment includes the following steps:
  • Step S101 The first network device obtains the type of the terminal device.
  • the type of the terminal device includes a drone, a non-UAV, or an undetermined type.
  • the first network device may be a base station or MME in an LTE system, or a base station, an AMF network element, or a network data analysis function (NWDAF) network element in a 5G system.
  • the first network device can obtain the type of terminal device in the following ways:
  • Manner 1 The first network device obtains the type of the terminal device according to the information of the terminal device.
  • the first network device Before the first network device obtains the type of the terminal device according to the information of the terminal device, it needs to obtain the information of the terminal device.
  • the information of the terminal device includes one or more of the following information: capability information of the terminal device, Contract information, terminal equipment type label information, terminal equipment measurement information, terminal equipment location information, and the type of cell the terminal equipment accesses.
  • the capability information of the terminal device may be carried in a radio resource control (Radio Resource Control, RRC) connection reconfiguration message or a non-access stratum (non-access stratum, NAS) message.
  • the capability information of the terminal device is used to indicate the type of the terminal device.
  • the capability information of the terminal device may be air communication capability indication information, drone type indication information, flight capability indication information, and general UE indication information on the ground.
  • the first network device can identify the type of the terminal device according to other information of the terminal device. If the capability information of the terminal device indicates that the type of the terminal device is a drone type, the first network device determines that the type of the terminal device is a drone type.
  • the eNB receives the tag information of the terminal device from the MME.
  • the tag information may include the type tag of the terminal device. If the tag type of the terminal device included in the tag information is a drone type Or non-drone type, the first network device determines that the type of the terminal device is a drone type or a non-drone type, and does not perform the subsequent steps, if the tag type of the terminal device included in the tag information is an uncertain type , The first network device can identify the type of the terminal device through other information of the terminal device.
  • the tag information of the terminal equipment may be carried in the S1 AP Initial Context Setup Request (S1 AP Initial Context Setup Request) sent by the MME to the eNB.
  • the eNB requests the MME for the subscription information of the terminal device in the S1 AP Initial Context Setup response (S1 AP initial context setup response), and the MME sends it to the eNB in the S1-AP UE Context Modification Request (S1-AP UE context modification request) .
  • the label information of the terminal device may also be carried in the handover request response message, or other signaling messages sent by the MME to the eNB, which is not limited in this embodiment.
  • the gNB receives the label information of the terminal device from the AMF network element, and obtains the type of the terminal device according to the label information of the terminal device.
  • the specific acquisition method refer to the way the eNB obtains the type of the terminal device .
  • the AMF network element may carry the label information of the terminal device in an N2 message and send it to the gNB.
  • the N2 message is, for example, an N2 PDU session request or an N2 session request.
  • the AMF network element can also carry the tag information of the terminal device in the N2 message sent to the gNB in other processes such as the registration process, the service request process, or the handover process.
  • the eNB receives the subscription information of the terminal device from the MME.
  • the subscription information of the terminal device includes the indication information of whether the terminal device has subscribed to the UAV service. If the indication information indicates the terminal If the device subscribes to the UAV service, the eNB determines that the type of the terminal device is the UAV type. If the indication information indicates that the terminal device does not subscribe to the UAV service, the eNB can use other information of the terminal device to determine the type of the terminal device. Recognition.
  • the eNB receives the contract information of the terminal device from the AMF network element, and obtains the type of the terminal device according to the contract information of the terminal device, and the specific acquisition method refers to the method of the eNB.
  • the first network device can obtain the type of the terminal device based on the measurement information of the terminal device.
  • the measurement information of the terminal device may include the number and identity of the neighboring cells of the terminal device, etc.
  • the first network device determines the type of the terminal device It is a drone type.
  • the first network device can identify the type of the terminal device through other information of the terminal device.
  • the communication feature of the terminal device may be the measurement feature data of the terminal device.
  • the first network device obtains the measurement feature data of the terminal device, and inputs the measurement feature data of the terminal device into a pre-trained type model to obtain the type of the terminal device.
  • the measurement information of the terminal device may also include measurement characteristic data including multipath delay, Doppler frequency shift, reference signal receiving power (Reference Signal Receiving Power, RSRP) size or change trend, signal and interference addition
  • RSRP Reference Signal Receiving Power
  • SINR Signal to Interference plus Noise Ratio
  • the first network device can determine whether the type of the terminal device is a drone type according to the size of the multipath delay of the terminal device.
  • the first network device can determine whether the type of the terminal device is a drone type according to the size of the Doppler frequency shift of the terminal device.
  • the type of terminal device can be obtained based on the location information of the terminal device. For example, when the location information of the terminal device indicates that the terminal device is in the air, the first network device determines that the type of the terminal device is a drone type. When the location information of the terminal device indicates that the terminal device is on the ground, the first network device can pass through the terminal Other information of the device identifies the type of terminal device.
  • the access network node may obtain the location information of the terminal device in the Minimization of Drive Test (MDT) report.
  • MDT Minimization of Drive Test
  • the first network device can obtain the terminal device information according to the type of cell the terminal device accesses. Types of. For example, if the cell accessed by the terminal device is a cell served by a drone type terminal, the type of the terminal device is determined to be the drone type. If the cell accessed by the terminal device is a common cell, the type of the terminal device is determined to be non-none The type of man-machine, or other information of the terminal device to identify the type of the terminal device.
  • Manner 2 When the first network device is an MME or AMF network element, the first network device receives a report message sent by the second network device, and the report message is used to report the type of the terminal device.
  • the second network device When the first network device is an MME, the second network device may be a base station, and when the first network device is an AMF, the second network device may be a base station or an NWDAF network element.
  • the first network device when the first network device is a base station, after the first network device obtains the type of the terminal device, the first network device may send the report message to the MME or AMF network element.
  • the first network device is an NWDAF network element, after the first network device obtains the type of the terminal device, the first network device sends the report message to the AMF.
  • the report information is used to report the type of the terminal device identified.
  • the report message includes the identification of the terminal device and/or the location information of the terminal device.
  • the report message may be a UAV report, and the report message may use an existing message between the first network device and the second network device, such as an S1 AP UE context response message, or a newly defined message.
  • the second network device can identify the type of terminal device according to the capability information of the terminal device.
  • the specific method for the second network device to identify the type of terminal device is the same as the method for the first network device to identify the type of terminal device.
  • the specific method for the device to identify the type of the terminal device will not be repeated here.
  • the first network device's identification of the type of the terminal device may be periodic or triggered based on an event.
  • the period may be a preset time period pre-configured in the first network device, such as 10:00 to 18:00 every day.
  • the event can be that the position of the terminal device is higher than the preset height, the cell type that the terminal device accesses is an air cell, the number of cells reported by the terminal device exceeds the preset value, the terminal device switches frequently, or the terminal device is switched Request messages from other devices.
  • the first network device receives an identification instruction message from the second network device, where the identification instruction message is used to instruct the first network device to identify the type of the associated terminal device.
  • the first network device recognizes the type of the associated terminal device according to the identification instruction message to obtain the type of the associated terminal device.
  • the manner in which the first network device obtains the type of each terminal device refers to the methods described in the foregoing manner 1 and manner 2, which will not be repeated here.
  • the identification indication message may be an unmanned aerial vehicle (UAV) identification request message.
  • UAV unmanned aerial vehicle
  • the first network device receives the identification instruction message, it determines to obtain the associated terminal device (which can be understood as all the terminal devices connected to the first network device. For example, for an access network node, it can be all terminal devices connected to the access.
  • the terminal equipment of the network node for example, for a mobility management network element, may be a type of terminal equipment connected to the mobility management network element with control plane signaling.
  • the identification instruction message includes an identification of the terminal device, and the identification instruction message is used to instruct the first network device to identify the type of the terminal device corresponding to the identification of the terminal device.
  • the identification of the terminal device included in the identification instruction message may be one or more.
  • the second network device may send the identification indication message to the first network device under the following conditions: when the second network device determines that the position of the terminal device is higher than the preset height according to the statistical information, the cell type that the terminal device accesses is an air cell , The number of cells reported by the terminal device exceeds a preset value or the terminal device frequently switches, etc., then the identification instruction message is sent to the first network device.
  • the first network device obtains the type of the terminal device according to the single information of the terminal device as an example. It can be understood that the first network device can also combine the capability information of the terminal device, the contract information of the terminal device, and the type label of the terminal device. The information, the measurement information of the terminal device, the location information of the terminal device, and the type of the cell that the terminal device accesses can acquire the type of the terminal device.
  • the first network device obtains the measurement characteristic data of the terminal device, and determines the type of the terminal device according to the type model and the measurement characteristic data.
  • the measurement characteristic data includes multipath delay, Doppler frequency shift, RSRP size or change trend, SINR size or change trend.
  • Step S102 The first network device sends a request message to the label management device.
  • the request message is used to request the label management device to create a type label for the terminal device.
  • a label management device is added to the existing network elements of the LTE system and the 5G system.
  • the label management device is used to create a type label for the terminal device and save the type label of the terminal device.
  • the label management device may be an independent network element, or it may be integrated in an existing network element, for example, integrated in a UCF network element, a SCEF network element, a NEF network element, HSS, UDM, or UDR.
  • Creating a type label for a terminal device can be understood as generating an association relationship between the terminal device and the type label, and saving the type label of the terminal device can be understood as saving the association relationship between the terminal device identifier and the type label.
  • the base station may forward the request message to the label management device through the MME.
  • the base station or NWDAF network element may forward the request message to the label management device through the AMF network element.
  • the MME or AMF network element may directly send the request message to the label management device.
  • the request message includes the identification of the terminal device to instruct the label management device for which terminal device to create a type label.
  • the request message may also include type information of the terminal device, where the type information indicates the type label to be created by the request, and the type information may or may not be a type label.
  • the type information is not a type tag, multiple bits can be used to indicate the type of the terminal device. For example, two bits of information indicate the type of the terminal device. 00 indicates that the type of the terminal device is a drone type, and 01 indicates the type of the terminal device. It is a non-UAV type, and 11 indicates that the type of terminal equipment is an undetermined type.
  • the type information of the terminal device is carried to display and instruct the label management device to create what type of label for the terminal device.
  • the tag management device When the type information is a type tag, the tag management device saves the association relationship between the terminal device identifier and the type tag. When the type information is not the type tag, the tag management device generates the type tag of the terminal device according to the type information, and saves the association relationship between the terminal device identifier and the type tag.
  • the type of the terminal device can be implicitly indicated through a different message name or message type, for example, drones, non-drones, or undetermined types are passed through three different types.
  • Request messages to create different types of tags such as drone tag creation request messages, non-drone tag creation request messages, and undetermined type tag creation request messages.
  • a UAV type tag is created for the terminal device by default.
  • the label management device is a dedicated network element for drones, and after receiving the request message, the label management device creates a drone type label for the terminal device by default.
  • the label management device After the label management device creates the type label for the terminal device, it sends a response message corresponding to the request message to the first network device, and the first network device receives the response message sent by the label management device.
  • the response message includes the label creation result, where
  • the label creation result may include creation success, update success, creation failure, or update failure.
  • the first network device sends a label query request to the label management device, where the label query request includes the identification of the terminal device, and the label query request is used to request to query the type label of the terminal device.
  • the tag management device queries the type tag of the terminal device according to the identification of the terminal device included in the tag query request, and sends a tag query response to the first network device, and the tag query response includes the query result. If the type label of the terminal device is queried, the query result is the type label of the terminal device. If the type label of the terminal device is not queried, the query result is that the terminal device does not have a corresponding type label.
  • the first network device After the first network device learns that the terminal device does not have a corresponding type label according to the query result, it can create a type label for the terminal device using the method of this embodiment.
  • the first network device acquires the label type of the terminal, the first network device initiates an identification process for the terminal device according to the acquired terminal type, so that the label of the terminal device can be updated. For example, when the acquired tag type is an undetermined type, the first network device initiates identification of the terminal device. If the terminal is identified as a drone device this time, the first network device may update the tag type of the terminal.
  • the first network device also sends an identification report message to the drone server, where the identification report message is used to indicate that the drone has been identified.
  • the identification report message may include the identification and location information of the terminal device, so that the UAV server can manage the terminal device according to it.
  • the first network device obtains the type of the terminal device.
  • the type of the terminal device includes drone, non-drone, or undetermined type.
  • the first network device sends a request message to the label management device, and the request message is used to request.
  • the label management device creates a type label for the terminal device, and the request message includes the identification of the terminal device.
  • the label management device creates and saves the type label for the terminal device, and subsequently the first network device or other device can query the type label of the terminal device through the identification of the terminal device, avoiding repeated identification of the type of the terminal device.
  • FIG. 9 is a flowchart of a method for label management of a terminal device provided in Embodiment 2 of the application. As shown in FIG. 9, the method provided in this embodiment includes the following steps:
  • Step S201 The label management device receives a request message sent by the first network device.
  • the request message is used to request the label management device to create a type label for the terminal device, and the request message includes the identification of the terminal device.
  • the request message also includes type information of the terminal device, where the type information indicates the type tag to be created by the request, and the type information may or may not be a type tag.
  • the first network device can implicitly indicate the type of the terminal device through a different message name or message type, such as drones, non-drones, or undetermined types.
  • a different message name or message type such as drones, non-drones, or undetermined types.
  • Three different request messages to create different types of tags such as a drone tag creation request message, a non-drone tag creation request message, and an undetermined type tag creation request message.
  • the base station may forward the request message to the label management device through the MME.
  • the base station or NWDAF network element may forward the request message to the label management device through the AMF network element.
  • the MME or AMF network element may directly send the request message to the label management device.
  • Step S202 The label management device creates a type label for the terminal device according to the request message.
  • the tag management device determines the type of the tag created for the terminal device according to the request message or the type information of the terminal device included in the request message.
  • the type tag of the terminal device includes UAV, non-UAV, or undetermined type tags. Creating a type label for a terminal device can be understood as generating the association relationship between the terminal device and the type label, and saving the type label of the terminal device can be understood as saving the association relationship between the terminal device and the type label.
  • the label management device After receiving the request message, the label management device queries whether a type label has been created for the terminal device according to the identification of the terminal device, and if the type label has not been created for the terminal device, the association relationship between the identification of the terminal device and the type label is generated If the type label has been created for the terminal device, the type label of the terminal device is updated.
  • the tag management device When the request message includes the type information of the terminal device, if the type information is a type tag, the tag management device saves the association relationship between the terminal device identifier and the type tag. If the type information is not a type label, the label management device generates a type label of the terminal device according to the type information, and saves the association relationship between the terminal device identification and the type label.
  • the type label is not created repeatedly for the terminal device.
  • the repeated creation scenario can be applied to the following scenarios: the type of the terminal device recognized for the first time is an undetermined type, and the type of the terminal device is subsequently recognized as a drone Or when it is not a drone, update the type label of the terminal device.
  • the tag management device is a dedicated network element for drones, the tag management device only needs to save the identification of the terminal device, and does not need to save the correspondence between the identification of the terminal device and the type tag.
  • the label management device After the label management device creates a type label for the terminal device, it sends a response message to the first network device.
  • the response message includes a label creation result.
  • the label creation result can be successful creation, creation failure, successful update, or update failure. .
  • the label management device receives a label query request sent by the first network device, the label query request includes the identification of the terminal device, the label management device queries the type label of the terminal device, and carries the query result in the label query response and sends it to The first network equipment. If the type label of the terminal device is queried, the query result is the type label of the terminal device. If the type label of the terminal device is not queried, the query result is that the terminal device does not have a corresponding type label.
  • the label management device receives a request message sent by the first network device.
  • the request message is used to request the label management device to create a type label for the terminal device.
  • the request message includes the identification of the terminal device.
  • the label management device is The terminal device creates a type label.
  • the type label of the terminal device includes UAV, non-UAV or undetermined type tags.
  • the label management device creates and saves the type label for the terminal device, and subsequently the first network device or other device can query the type label of the terminal device through the identification of the terminal device, thereby avoiding repeated identification of the type of the terminal device.
  • FIG. 10 is a signaling flow chart of a method for label management of terminal equipment provided in Embodiment 3 of the application.
  • This embodiment takes a 5G system as an example for description.
  • the method provided in this embodiment includes the following steps:
  • Step S301 The gNB obtains information of the terminal device.
  • the information of the terminal device includes one or more of the following information: the capability information of the terminal device, the contract information of the terminal device, the type label information of the terminal device, the measurement information of the terminal device, the location information of the terminal device, and the terminal device access information The type of cell.
  • Step S302 The AMF network element sends an identification instruction message to the gNB.
  • the identification indication message may be a UVA identification request.
  • the identification indication message includes the identification of the terminal device.
  • the AMF network element discovers that the terminal device frequently switches, the cell where the user resides frequently switches, receives drone recognition request messages or drone recognition service subscription messages from other nodes according to statistical information, or the AMF network element initially recognizes the terminal When the device is a suspicious drone, it may periodically send identification instructions to the gNB.
  • the AMF network element may also send an identification indication message to the gNB at other times, which will not be repeated in this application.
  • Step S302 is an optional step, and step S302 can also be performed before step 301.
  • Step S303 The gNB determines to identify the type of the terminal device.
  • the gNB may periodically determine to identify the type of terminal device, and may also determine the type of terminal device based on an event trigger. For a specific manner, refer to the description of Embodiment 1, which will not be repeated here.
  • Step S304 The gNB identifies the type of the terminal device according to the information of the terminal device.
  • Step S305 The gNB sends a report message to the AMF network element.
  • the report information is used to report an identification event that the AMF network element recognizes the type of the terminal device.
  • the report message includes the identification of the terminal device and/or the location information of the terminal device.
  • the report message may be a UAV report, and the report message may be an existing message between the gNB and the AMF network element, such as the S1 AP UE context response message, or a newly defined message.
  • Step S306 The AMF network element sends the report message to the NEF/UCF network element.
  • this step is optional.
  • Step S307 The NEF/UCF network element sends the report message to the UAV server.
  • this step is optional.
  • Step S308 The gNB sends a request message to the AMF network element.
  • the request message is used to request the label management device to create a type label for the terminal device.
  • the request message includes the identification of the terminal device.
  • the request message also includes the type information of the terminal device.
  • the request message can be UAV label creation request.
  • steps S305 and S308 are executed in no order, and they can also be executed simultaneously.
  • Step S309 The AMF network element sends the request message to the label management device.
  • Step S310 The label management device creates a type label for the terminal device.
  • Step S311 The label management device sends a response message to the AMF network element.
  • the response message includes the creation result, and the response message may be UAV label creation response.
  • Step S312 The AMF network element sends a response message to the gNB.
  • the process of this embodiment can also be applied to the LTE system.
  • the gNB is replaced with the eNB, and the AMF network element is replaced with the MME, and the creation process remains unchanged, and the detailed description is omitted here.
  • FIG. 11 is a signaling flow chart of a label management method for terminal equipment provided in Embodiment 4 of this application.
  • This embodiment takes a 5G system as an example for description.
  • the method provided in this embodiment includes the following steps:
  • Step S401 The gNB obtains information of the terminal device.
  • the information of the terminal device includes one or more of the following information: the capability information of the terminal device, the contract information of the terminal device, the type label information of the terminal device, the measurement information of the terminal device, the location information of the terminal device, and the terminal device access information The type of cell.
  • Step S402 The AMF network element sends an identification instruction message to the gNB.
  • This step is optional and can also be executed before step S401.
  • step S403 the gNB determines to recognize the type of the terminal device.
  • the gNB may periodically determine to identify the type of terminal device, or determine the type of terminal device based on an event trigger. For a specific manner, refer to the description of Embodiment 1, which will not be repeated here.
  • Step S404 The gNB identifies the type of the terminal device according to the information of the terminal device.
  • Step S405 The gNB sends a report message to the AMF network element.
  • the report message contains the identification of the terminal device, can also contain the type information of the terminal device, and can also contain the location information of the terminal device.
  • Step S406 The AMF network element sends the report message to NEF/UCF.
  • this step is optional.
  • Step S407 The NEF/UCF network element sends the report message to the UAV server.
  • this step is optional.
  • Step S408 The AMF network element sends the request message to the label management device.
  • Step S409 The label management device creates a type label for the terminal device.
  • Step S410 The label management device sends a response message to the AMF network element.
  • Step S411 The AMF network element sends a response message to the gNB.
  • the third embodiment after the gNB recognizes the type of the terminal device, it sends a request message to the label management device to trigger the creation of the type label.
  • the AMF network element receives the report message, Send a request message to the label management device to trigger the creation of the type label.
  • the report message sent by the gNB to the AMF network element must include the identification of the terminal device, so that the AMF network element subsequently determines which terminal device to create the type label for.
  • the report message can Does not carry the identification of the terminal device. The other steps are the same as in the third embodiment, and will not be repeated here.
  • the process of this embodiment can also be applied to the LTE system.
  • the gNB is replaced with the eNB, and the AMF network element is replaced with the MME, and the creation process remains unchanged, and the detailed description is omitted here.
  • FIG. 12 is a signaling flowchart of a label management method for terminal equipment provided in Embodiment 5 of this application.
  • This embodiment takes a 5G system as an example for description.
  • the method provided in this embodiment includes the following steps:
  • Step S501 The NWDAF network element obtains the tag data and/or contract data of the terminal device.
  • the NWDAF network element can obtain the contract data of the terminal device from the UDM, UTM, UCF network element or the NEF network element, and can obtain the label data of the terminal device from the label management device.
  • the tag data of the terminal device is used to indicate whether a type tag is created for the terminal device. If a type tag is created, the tag data includes the type tag of the terminal device. The MWDAF may subsequently determine whether to identify the type of the terminal device according to the tag data and/or contract data of the terminal device.
  • NWDAF determines to identify the type of the terminal device. Or, if the tag data indicates that a type tag is created, and the type tag is an uncertain type or a non-UAV type, then NWDAF determines to identify the type of the terminal device. If the tag data indicates that a type tag is created, and the type tag is a drone type, NWDAF determines not to recognize the type of terminal device.
  • NWDAF determines to recognize the type of the terminal device. If the contract data indicates that the terminal device subscribes to the drone service, NWDAF determines not to recognize the type of terminal device.
  • the contract data indicates that the terminal device does not subscribe to the drone service, and the tag data indicates that the type of the terminal device is an uncertain type, then it is determined to identify the type of the terminal device. In order to avoid missing drones, if the contract data indicates that the terminal device does not subscribe to the drone service, and the tag data indicates that the type of the terminal device is a non-drone type, it can also be determined to identify the type of the terminal device.
  • Step S502 The NWDAF network element obtains training data of the terminal device.
  • the training data may include measurement feature data of a large number of terminal devices, and the NWDAF network element may obtain the training data from gNB or operation and management (Operation Administration and Maintenance, OAM) devices.
  • gNB or operation and management (Operation Administration and Maintenance, OAM) devices.
  • OAM Opera and management
  • Step S503 The NWDAF network element trains the training data to obtain a type model.
  • this type model is used to identify the type of terminal equipment.
  • Steps S502 and S503 are optional steps.
  • Step S504 The AMF network element sends an identification instruction message to the NWDAF network element.
  • This step is optional.
  • Step S505 The NWDAF network element sends a request/subscribe message for measuring characteristic data to the gNB/OAM.
  • the subscription message may be UE measurement data subscribe, and the subscription message includes the identification of the terminal device.
  • Step S506 The gNB/OAM sends a request/subscription response message to the NWDAF network element.
  • the request/subscription response message includes measurement characteristic data of the terminal device, and the request/subscription response message may be UE measurement data notification.
  • Step S507 The NWDAF network element determines the type of the terminal device according to the type model and the measurement characteristic data of the terminal device.
  • NWDAF inputs the measured characteristic data of the terminal equipment into a pre-trained type model to obtain the type of the terminal equipment.
  • Step S508 The NWDAF network element sends a report message to the UAV server.
  • This step is optional.
  • the report message includes the identification of the terminal device and/or the location information of the terminal device.
  • the NWDAF network element can forward the report message to the UAV server through the NEF/UCF network element.
  • Step S509 The NWDAF network element sends an identification response message to the AMF network element.
  • This step is optional.
  • the identification response message is used to respond to the identification instruction message sent by the AMF network element. If the identification instruction message includes the identification of the terminal device, the identification response message also includes the identification of the terminal device. Optionally, the identification response message may also Including the location information of the terminal device. If the identification instruction message does not include the identification of the terminal device, the identification response message does not include the identification of the terminal device.
  • Step S510 The NWDAF network element sends a request message to the label management device.
  • the request message is used to request the label management device to create a type label for the terminal device.
  • Step S511 The label management device creates a type label for the terminal device.
  • Step S512 The label management device sends a response message to the NWDAF network element.
  • the response message includes the creation result.
  • the NWDAF network element obtains the type model through big data analysis, and subsequently inputs the measurement characteristic data of the terminal device into the pre-trained type model to obtain the type of the terminal device, so that the recognition result is more accurate.
  • FIG. 13 is a signaling flow chart of a label management method for terminal equipment provided in Embodiment 6 of this application.
  • This embodiment takes a 5G system as an example for description. As shown in FIG. 13, the method provided in this embodiment includes the following steps:
  • Step S601 The NWDAF network element obtains the tag data and/or contract data of the terminal device.
  • Step S602 The NWDAF network element obtains training data of the terminal device.
  • Step S603 The NWDAF network element trains the training data to obtain a type model.
  • Step S604 The AMF network element sends an identification instruction message to the NWDAF network element.
  • This step is optional.
  • Step S605 The NWDAF network element sends a request/subscribe message for measuring characteristic data to the gNB/OAM.
  • Step S606 The gNB/OAM sends a request/subscription response message to the NWDAF network element.
  • Step S607 The NWDAF network element determines the type of the terminal device according to the type model and the measurement characteristic data of the terminal device.
  • Step S608 The NWDAF network element sends a report message to the drone server.
  • This step is optional.
  • Step S609 The NWDAF network element sends an identification response message to the AMF network element.
  • This step is optional.
  • Step S610 The AMF network element sends a request message to the label management device.
  • Step S611 The label management device creates a type label for the terminal device.
  • Step S612 The label management device sends a response message to the NWDAF network element.
  • the difference between this embodiment and the fifth embodiment is: after the NWDAF network element in the fifth embodiment recognizes the type of the terminal device, the NWDAF network element sends a request message to the label management device to trigger the establishment of the type label.
  • the AMF After receiving the report message, the network element sends a request message to the label management device to trigger the establishment of the type label.
  • the other processes are the same as in the fifth embodiment, and refer to the related description of the fifth embodiment, which will not be repeated here.
  • FIG. 14 is a signaling flowchart of a label management method for terminal equipment provided in Embodiment 7 of this application. As shown in FIG. 14, the method provided in this embodiment includes the following steps:
  • Step S701 The mobility management node sends a label query request to the label management device.
  • the tag query request includes the identification of the terminal device to inform the tag management device of the identification of the terminal device to be inquired.
  • the mobility management node can check the type label of the terminal device when the following situations occur: the terminal device is registered to the network, the terminal device requests a service from the mobility management node, the location information of the terminal device indicates that the terminal device is in the air, The terminal equipment switches from the ground cell to the air cell, and the terminal equipment switches frequently. In this process, the mobility management node can detect the type label of the terminal device by interacting with the access network node.
  • the mobility management node can be an MME or AMF network element, and the access network node can be an eNB or a gNB.
  • Step S702 The label management device sends a label query response to the mobility management node.
  • the label query response includes the query result.
  • the query result may indicate that no type label has been created for the terminal device, or may include the type label of the terminal device.
  • Step S703 When the type tag of the terminal device is included in the tag query response, and the type tag indicates that the type is a drone type, trigger position tracking of the terminal device and/or drone event reporting.
  • FIG. 15 is a flowchart of a method for label management of a terminal device provided in Embodiment 8 of this application. As shown in FIG. 15, the method provided in this embodiment includes the following steps:
  • Step S801 The first network device obtains the type of the terminal device.
  • the type of the terminal device includes a drone, a non-UAV, or an undetermined type.
  • acquiring the type of terminal device can be understood as identifying the type of terminal device.
  • Step S802 The first network device sends a report message to the second network device, and the report message is used to report the type of the terminal device.
  • the first network device may be a base station or MME in an LTE system, or may be a base station, AMF network element, or NWDAF network element in a 5G system.
  • the first network device can obtain the type of terminal device in the following ways:
  • Manner 1 The first network device obtains the type of the terminal device according to the information of the terminal device.
  • the first network device Before the first network device obtains the type of the terminal device according to the information of the terminal device, it needs to obtain the information of the terminal device.
  • the information of the terminal device includes one or more of the following information: capability information of the terminal device, Contract information, terminal equipment type label information, terminal equipment measurement information, terminal equipment location information, and the type of cell the terminal equipment accesses.
  • the capability information of the terminal device can be carried in the RRC connection reconfiguration message or the NAS message.
  • the capability information of the terminal device is used to indicate the type of the terminal device.
  • the capability information of the terminal device may be air communication capability indication information, drone type indication information, flight capability indication information, and general UE indication information on the ground.
  • the first network device can identify the type of the terminal device according to other information of the terminal device. If the capability information of the terminal device indicates that the type of the terminal device is a drone type, the first network device determines that the type of the terminal device is a drone type.
  • the eNB receives the tag information of the terminal device from the MME.
  • the tag information may include the type tag of the terminal device. If the tag type of the terminal device included in the tag information is a drone type Or non-drone type, the first network device determines that the type of the terminal device is a drone type or a non-drone type, and does not perform the subsequent steps, if the tag type of the terminal device included in the tag information is an uncertain type , The first network device can identify the type of the terminal device through other information of the terminal device.
  • the tag information of the terminal equipment may be carried in the S1 AP Initial Context Setup Request sent by the MME to the eNB.
  • the eNB requests the MME for the subscription information of the terminal equipment in the S1 AP Initial Context Setup response, and the MME sends it to the eNB in the S1-AP UE Context Modification Request.
  • the label information of the terminal device may also be carried in the handover request response message, or other signaling messages sent by the MME to the eNB, which is not limited in this embodiment.
  • the gNB receives the label information of the terminal device from the AMF network element, and obtains the type of the terminal device according to the label information of the terminal device.
  • the specific acquisition method refer to the way the eNB obtains the type of the terminal device .
  • the AMF network element may carry the label information of the terminal device in an N2 message and send it to the gNB.
  • the N2 message is, for example, an N2 PDU session request or an N2 session request.
  • the AMF network element can also carry the tag information of the terminal device in the N2 message sent to the gNB in other processes such as the registration process, the service request process, or the handover process.
  • the eNB receives the subscription information of the terminal device from the MME.
  • the subscription information of the terminal device includes the indication information of whether the terminal device has subscribed to the UAV service. If the indication information indicates the terminal If the device subscribes to the UAV service, the eNB determines that the type of the terminal device is the UAV type. If the indication information indicates that the terminal device does not subscribe to the UAV service, the eNB can use other information of the terminal device to determine the type of the terminal device. Recognition.
  • the eNB receives the contract information of the terminal device from the AMF network element, and obtains the type of the terminal device according to the contract information of the terminal device, and the specific acquisition method refers to the method of the eNB.
  • the first network device can obtain the type of the terminal device based on the measurement information of the terminal device.
  • the measurement information of the terminal device may include the number and identity of the neighboring cells of the terminal device, etc.
  • the first network device determines the type of the terminal device It is a drone type.
  • the first network device can identify the type of the terminal device through other information of the terminal device.
  • the communication feature of the terminal device may be the measurement feature data of the terminal device.
  • the first network device obtains the measurement feature data of the terminal device, and inputs the measurement feature data of the terminal device into a pre-trained type model to obtain the type of the terminal device.
  • the measurement information of the terminal device may also include measurement characteristic data, the measurement characteristic data including multipath delay, Doppler frequency shift, RSRP size or change trend, signal to interference plus noise ratio SINR size or change trend.
  • the first network device can determine whether the type of the terminal device is a drone type according to the size of the multipath delay of the terminal device.
  • the first network device can determine whether the type of the terminal device is a drone type according to the size of the Doppler frequency shift of the terminal device.
  • the type of terminal device can be obtained based on the location information of the terminal device. For example, when the location information of the terminal device indicates that the terminal device is in the air, the first network device determines that the type of the terminal device is a drone type. When the location information of the terminal device indicates that the terminal device is on the ground, the first network device can pass through the terminal Other information of the device identifies the type of terminal device.
  • the access network node may obtain the location information of the terminal device in the Minimization of Drive Test (MDT) report.
  • MDT Minimization of Drive Test
  • the first network device can obtain the terminal device information according to the type of cell the terminal device accesses. Types of. For example, if the cell accessed by the terminal device is a cell served by a drone type terminal, the type of the terminal device is determined to be the drone type. If the cell accessed by the terminal device is a common cell, the type of the terminal device is determined to be non-none The type of man-machine, or other information of the terminal device to identify the type of the terminal device.
  • Manner 2 When the first network device is an MME or AMF network element, the first network device receives a report message sent by the second network device, and the report message is used to report the type of the terminal device.
  • the second network device When the first network device is an MME, the second network device may be a base station, and when the first network device is an AMF network element, the second network device may be a base station or an NWDAF network element.
  • the first network device when the first network device is a base station, after the first network device obtains the type of the terminal device, the first network device may send the report message to the MME or AMF network element.
  • the first network device is NWDAF, after the first network device obtains the type of the terminal device, the first network device sends the report message to the AMF network element.
  • the report information is used to report that the first network device recognizes the type of the terminal device itself.
  • the report message includes the identification of the terminal device and/or the location information of the terminal device.
  • the report message may be a UAV report, and the report message may use an existing message between the first network device and the second network device, such as an S1 AP UE context response message, or a newly defined message.
  • the second network device can identify the type of terminal device according to the capability information of the terminal device.
  • the specific method for the second network device to identify the type of terminal device is the same as the method for the first network device to identify the type of terminal device.
  • the specific method for the device to identify the type of the terminal device will not be repeated here.
  • the first network device's identification of the type of the terminal device may be periodic or triggered based on an event.
  • the period may be a preset time period pre-configured in the first network device, such as 10:00 to 18:00 every day.
  • the event can be that the position of the terminal device is higher than the preset height, the cell type that the terminal device accesses is an air cell, the number of cells reported by the terminal device exceeds the preset value, the terminal device switches frequently, or the terminal device is switched Request messages from other devices.
  • the first network device receives an identification instruction message from the second network device, where the identification instruction message is used to instruct the first network device to identify the type of the associated terminal device .
  • the first network device recognizes the device type of the associated terminal device according to the identification instruction message to obtain the type of the associated terminal device.
  • the identification indication message may be a UAV identification request message.
  • the first network device receives the identification instruction message, it recognizes the associated terminal device (which can be understood as all terminal devices connected to the first network device.
  • the terminal equipment of the node for example, for a mobility management network element, may be a type of terminal equipment connected to the mobility management network element with control plane signaling.
  • the first network device receives an identification instruction message from the second network device.
  • the identification instruction message includes the identification of the terminal device, and the identification instruction message is used to indicate the first
  • the network device identifies the type of the terminal device corresponding to the identification of the terminal device, and the first network identifies the type of the terminal device according to the identification instruction message, and obtains the type of the terminal device.
  • the identification of the terminal device included in the identification instruction message may be one or more.
  • the second network device may send the identification indication message to the first network device under the following conditions: when the second network device determines that the position of the terminal device is higher than the preset height according to the statistical information, the cell type that the terminal device accesses is an air cell , The number of cells reported by the terminal device exceeds a preset value or the terminal device frequently switches, etc., then the identification instruction message is sent to the first network device.
  • the first network device obtains the type of the terminal device according to the single information of the terminal device as an example. It can be understood that the first network device can also combine the capability information of the terminal device, the contract information of the terminal device, and the type label of the terminal device. The information, the measurement information of the terminal device, the location information of the terminal device, and the type of the cell that the terminal device accesses can acquire the type of the terminal device.
  • the first network device obtains the measurement characteristic data of the terminal device, and determines the type of the terminal device according to the type model and the measurement characteristic data.
  • the measurement characteristic data includes multipath delay, Doppler frequency shift, RSRP size or change trend, SINR size or change trend.
  • the report message includes the identification of the terminal device and/or the location information of the terminal device.
  • the second network device may be an MME or AMF network element, and when the first network device is a NWDAF network element, the second network device may be an AMF network element.
  • Fig. 16 is a schematic diagram of the structure of the network device provided in the ninth embodiment of the application. As shown in Fig. 16, the network device includes:
  • the obtaining module 11 is used to obtain the type of terminal device, the type of the terminal device includes drone, non-drone or undetermined type;
  • the sending module 12 is configured to send a request message to a label management device, where the request message is used to request the label management device to create a type label for the terminal device, and the request message includes the identification of the terminal device.
  • the obtaining module 11 is specifically configured to:
  • the obtaining module 11 is specifically configured to:
  • the information of the terminal device includes one or more of the following information: capability information of the terminal device, subscription information of the terminal device, type label information of the terminal device, and The measurement information of the terminal device, the location information of the terminal device, and the type of cell that the terminal device accesses.
  • the device further includes:
  • a receiving module configured to receive an identification instruction message from a second network device, where the identification instruction message is used to instruct the first network device to identify the type of associated terminal device;
  • the acquiring module 11 is specifically used for:
  • the device further includes:
  • the receiving module is configured to receive an identification instruction message from a second network device, the identification instruction message includes the identification of the terminal device, and the identification instruction message is used to instruct the first network device to contact the terminal device Type recognition;
  • the acquiring module 11 is specifically used for:
  • the obtaining module 11 is specifically configured to:
  • the type of the terminal device is determined.
  • the request message further includes type information of the terminal device.
  • the device further includes:
  • the receiving module is configured to receive a response message sent by the label management device, and the response message includes the label creation result.
  • the device further includes a receiving module
  • the sending module is further configured to send a label query request to the label management device, and the label query request includes the identification of the terminal device;
  • the receiving module is configured to receive a label query response sent by the label management device, and the label query response includes the type label of the terminal device.
  • the sending module is further used for:
  • the network equipment is a mobility management entity MME, a base station, an access and mobility management function AMF network element, or a network data analysis function NWDAF network element.
  • the network equipment mobility management entity MME, and the second network equipment is a base station; or,
  • the network device is an access and mobility management function AMF network element
  • the second network device is an NWDAF network element or a base station.
  • the network device in this embodiment can be used to execute the method executed by the first network device in the first to seventh embodiments of the above method.
  • the specific implementation manner and technical effect are similar, and details are not described herein again.
  • FIG. 17 is a schematic structural diagram of a label management device provided by Embodiment 10 of this application. As shown in FIG. 17, the label management device includes:
  • the receiving module 21 is configured to receive a request message sent by a first network device, the request message is used to request the label management device to create a type label for the terminal device, and the request message includes the identification of the terminal device;
  • the creation module 22 is configured to create a type label for the terminal device according to the request message.
  • the type label of the terminal device includes a drone, a non-UAV or an undetermined type label.
  • the request message further includes type information of the terminal device.
  • the method further includes:
  • the label management device sends a response message to the first network device, and the response message includes a label creation result.
  • a sending module 23 is further included;
  • the receiving module 21 is further configured to receive a tag query request sent by the first network device, where the tag query request includes the identification of the terminal device;
  • the sending module 23 is configured to send a label query response to the first network device, and the label query response includes the type label of the terminal device.
  • the first network device is a mobility management entity MME, a base station, an access and mobility management function AMF network element, or a network data analysis function NWDAF network element.
  • the label management device of this embodiment can be used to execute the methods executed by the label management device in the first to seventh embodiments of the foregoing method.
  • the specific implementation and technical effects are similar, and details are not described herein again.
  • FIG. 18 is a schematic structural diagram of a network device provided in Embodiment 11 of this application. As shown in FIG. 18, the network device includes:
  • the obtaining module 31 is used to obtain the type of terminal device, the type of the terminal device includes drone, non-drone or undetermined type;
  • the sending module 32 is configured to send a report message to the second network device, where the report message is used to report the type of the terminal device.
  • the obtaining module 31 is specifically configured to:
  • the obtaining module 31 is specifically configured to:
  • the information of the terminal device includes one or more of the following information: capability information of the terminal device, subscription information of the terminal device, type label information of the terminal device, and The measurement information of the terminal device, the location information of the terminal device, and the type of cell that the terminal device accesses.
  • the device further includes:
  • a receiving module configured to receive an identification instruction message from a second network device, where the identification instruction message is used to instruct the first network device to identify the type of associated terminal device;
  • the obtaining module 31 is specifically configured to:
  • the device further includes:
  • the receiving module is configured to receive an identification instruction message from a second network device, the identification instruction message includes the identification of the terminal device, and the identification instruction message is used to instruct the first network device to contact the terminal device Type recognition;
  • the obtaining module 31 is specifically configured to:
  • the first network obtains the type of the terminal device according to the identification instruction message.
  • the second network device is a mobility management entity MME or a mobility management function AMF network element; or,
  • the second network device is an AMF network element.
  • the network device of this embodiment can be used to execute the method described in Embodiment 8.
  • the specific implementation manner and technical effect are similar, and details are not described herein again.
  • FIG. 19 is a schematic structural diagram of a network device provided by Embodiment 12 of this application.
  • the network device includes: a processor 41, a memory 42 and a transceiver 43.
  • the memory 42 is used to store instructions.
  • the transceiver 43 is used to communicate with other devices, and the processor 41 is used to execute instructions stored in the memory 42, so that the network device 41 executes the first network device or the first network device in the first to eighth embodiments. 2.
  • the method implemented by the network device is not limited to the network device.
  • FIG. 20 is a schematic structural diagram of a label management device according to Embodiment 13 of the application.
  • the label management device includes a processor 51, a memory 52, and a transceiver 53, where the memory 52 is used to store instructions, The transceiver 53 is used to communicate with other devices, and the processor 51 is used to execute instructions stored in the memory 52, so that the network device 51 executes the label management device in the first to eighth embodiments above. Methods.
  • the processor used in the network device or label management device in the embodiment of the present application may be a central processing unit (CPU), a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), and field programmable Gate array (FPGA) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof. It can implement or execute various exemplary logical blocks, modules and circuits described in conjunction with the disclosure of the present application.
  • the processor may also be a combination for realizing computing functions, for example, a combination of one or more microprocessors, a combination of a DSP and a microprocessor, and so on.
  • the bus described in the embodiments of this application may be an Industry Standard Architecture (ISA) bus, Peripheral Component (PCI) bus, or Extended Industry Standard Architecture (EISA) bus, etc. .
  • ISA Industry Standard Architecture
  • PCI Peripheral Component
  • EISA Extended Industry Standard Architecture
  • the bus can be divided into address bus, data bus, control bus and so on.
  • the buses in the drawings of this application are not limited to only one bus or one type of bus.
  • the disclosed device and method may be implemented in other ways.
  • the device embodiments described above are only schematic.
  • the division of the unit is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical, or other forms.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware, or in the form of hardware plus software functional units.
  • the above-mentioned integrated unit implemented in the form of a software functional unit may be stored in a computer readable storage medium.
  • the above-mentioned software functional unit is stored in a storage medium, and includes several instructions to make a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor execute the method described in each embodiment of the present application Part of the steps.
  • the foregoing storage media include: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk or optical disk and other media that can store program code .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Physics & Mathematics (AREA)
  • Astronomy & Astrophysics (AREA)
  • Aviation & Aerospace Engineering (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Security & Cryptography (AREA)
  • Databases & Information Systems (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请提供一种终端设备的标签管理方法和装置,所述方法包括:第一网络设备获取终端设备的类型,终端设备的类型包括无人机、非无人机或未确定类型,第一网络设备向标签管理设备发送请求消息,请求消息用于请求标签管理设备为终端设备创建类型标签,请求消息中包括终端设备的标识。标签管理设备通过为终端设备创建并保存类型标签,后续第一网络设备或者其他设备可以通过终端设备的标识查询终端设备的类型标签,避免了重复对终端设备的类型进行识别。

Description

终端设备的标签管理方法和装置
本申请要求于2019年1月18日提交中国专利局、申请号为2019101089176、申请名称为“终端设备的标签管理方法和装置”的中国专利申请的优先权,其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术,尤其涉及一种终端设备的标签管理方法和装置。
背景技术
无人驾驶飞机简称“无人机”,是利用无线电遥控设备和自备的程序控制装置操纵的不载人飞机,为了规范无人机的运营和飞行,需要对无人机进行监管。可以利用移动通信网络对无人机进行监管,在移动通信网络中除了无人机还有智能手机、车载设备等其他类型的终端设备,对无人机进行监管的前提是识别无人机。
现有技术中,对无人机的识别不准确,且现有的识别无人机的方法均为一次性识别,导致对于已经识别过的终端设备,会重复识别,对非无人机类型的终端会造成影响,同时造成无线资源和网络资源的浪费。
发明内容
本申请提供一种终端设备的标签管理方法和装置,避免重复对终端设备的类型进行识别。
本申请第一方面提供一种终端设备的标签管理方法,包括:
第一网络设备获取终端设备的类型,所述终端设备的类型包括无人机、非无人机或未确定类型;
所述第一网络设备向标签管理设备发送请求消息,所述请求消息用于请求所述标签管理设备为所述终端设备创建类型标签,所述请求消息中包括所述终端设备的标识。
一种示例性的方式中,所述第一网络设备获取终端设备的类型,包括:
所述第一网络设备接收第二网络设备发送的报告消息,所述报告消息用于报告所述终端设备的类型。
又一种示例性的方式中,所述第一网络设备获取终端设备的类型,包括:
所述第一网络设备根据所述终端设备的信息获取所述终端设备的类型。
一种示例性的方式中,所述终端设备的信息包括以下信息中的一个或者多个:所述终端设备的能力信息、所述终端设备的签约信息、所述终端设备的类型标签信息、所述终端设备的测量信息、所述终端设备的位置信息和所述终端设备接入的小区的类型。
一种示例性的方式中,,所述第一网络设备获取所述终端设备的类型之前还包括:
所述第一网络设备接收来自第二网络设备的识别指示消息,所述识别指示消息用 于指示所述第一网络设备对关联的终端设备的类型进行识别;
所述第一网络设备获取所述终端设备的类型,包括:
所述第一网络设备根据所述识别指示消息获取所述关联的终端设备的类型。
又一种示例性的方式中,所述第一网络设备获取所述终端设备的类型之前还包括:
所述第一网络设备接收来自第二网络设备的识别指示消息,所述识别指示消息中包括所述终端设备的标识,所述识别指示消息用于指示所述第一网络设备对所述终端设备的类型进行识别;
所述第一网络设备获取所述终端设备的类型,包括:
所述第一网络根据所述识别指示消息获取所述终端设备的类型。
再一种示例性的方式中,所述第一网络设备获取终端设备的类型,包括:
所述第一网络设备获取所述终端设备的测量特征数据;
所述第一网络设备根据类型模型和所述测量特征数据,确定所述终端设备的类型。
一种示例性的方式中,所述请求消息中还包括所述终端设备的类型信息。
一种示例性的方式中,所述第一网络设备向标签管理设备发送请求消息之后,所述方法还包括:
所述第一网络设备接收所述标签管理设备发送的响应消息,所述响应消息中包括标签创建结果。
一种示例性的方式中,所述方法还包括:
所述第一网络设备向所述标签管理设备发送标签查询请求,所述标签查询请求中包括所述终端设备的标识;
所述第一网络设备接收所述标签管理设备发送的标签查询响应,所述标签查询响应中包括所述终端设备的类型标签。
一种示例性的方式中,所述方法还包括:
所述第一网络设备向UTM发送报告消息,所述报告消息中包括所述终端设备的标识和位置信息。
一种示例性的方式中,所述第一网络设备为移动管理实体MME、基站、接入与移动性管理功能AMF网元或网络数据分析功能NWDAF网元。
一种示例性的方式中,所述第一网络设备移动管理实体MME,所述第二网络设备为基站;或者,
所述第一网络设备为接入与移动性管理功能AMF网元,所述第二网络设备为NWDAF网元或基站。
本申请第二方面提供一种终端设备的标签管理方法,包括:
标签管理设备接收第一网络设备发送的请求消息,所述请求消息用于请求所述标签管理设备为所述终端设备创建类型标签,所述请求消息中包括所述终端设备的标识;
所述标签管理设备根据所述请求消息,为所述终端设备创建类型标签,所述终端设备的类型标签包括无人机、非无人机或未确定类型标签。
一种示例性的方式中,所述请求消息中还包括所述终端设备的类型信息。
一种示例性的方式中,所述标签管理设备根据所述请求消息,为所述终端设备创建类型标签之后,还包括:
所述标签管理设备向所述第一网络设备发送响应消息,所述响应消息中包括标签创建结果。
一种示例性的方式中,还包括:
所述标签管理设备接收所述第一网络设备发送的标签查询请求,所述标签查询请求中包括所述终端设备的标识;
所述标签管理设备向所述第一网络设备发送标签查询响应,所述标签查询响应中包括所述终端设备的类型标签。
一种示例性的方式中,所述第一网络设备为移动管理实体MME、基站、接入与移动性管理功能AMF网元或网络数据分析功能NWDAF网元。
本申请第三方面提供一种终端设备的标签管理方法,包括:
第一网络设备获取终端设备的类型,所述终端设备的类型包括无人机、非无人机或未确定类型;
所述第一网络设备向第二网络设备发送报告消息,所述报告消息用于报告所述终端设备的类型。
一种示例性的方式中,所述第一网络设备获取终端设备的类型,包括:
所述第一网络设备接收第二网络设备发送的报告消息,所述报告消息用于报告所述终端设备的类型。
又一种示例性的方式中,所述第一网络设备获取终端设备的类型,包括:
所述第一网络设备根据所述终端设备的信息获取所述终端设备的类型。
一种示例性的方式中,所述终端设备的信息包括以下信息中的一个或者多个:所述终端设备的能力信息、所述终端设备的签约信息、所述终端设备的类型标签信息、所述终端设备的测量信息、所述终端设备的位置信息和所述终端设备接入的小区的类型。
一种示例性的方式中,所述第一网络设备获取所述终端设备的类型之前还包括:
所述第一网络设备接收来自第二网络设备的识别指示消息,所述识别指示消息用于指示所述第一网络设备对关联的终端设备的类型进行识别;
所述第一网络设备获取所述终端设备的类型,包括:
所述第一网络设备根据所述识别指示消息获取所述关联的终端设备的类型。
又一种示例性的方式中,所述第一网络设备获取所述终端设备的类型之前还包括:
所述第一网络设备接收来自第二网络设备的识别指示消息,所述识别指示消息中包括所述终端设备的标识,所述识别指示消息用于指示所述第一网络设备对所述终端设备的类型进行识别;
所述第一网络设备获取所述终端设备的类型,包括:
所述第一网络根据所述识别指示消息获取所述终端设备的类型。
一种示例性的方式中,当所述第一网络设备为基站时,所述第二网络设备为移动管理实体MME或移动性管理功能AMF网元;或者,
当所述第一网络设备为网络数据分析功能NWDAF网元时,所述第二网络设备为AMF网元。
本申请第四方面提供一种终端设备的标签管理方法,包括:
第一网络设备获取终端设备的类型,所述终端设备的类型包括无人机、非无人机或未确定类型;
所述第一网络设备向标签管理设备发送请求消息,所述请求消息用于请求所述标签管理设备为所述终端设备创建类型标签,所述请求消息中包括所述终端设备的标识;
所述标签管理设备根据所述请求消息,为所述终端设备创建类型标签,所述终端设备的类型标签包括无人机、非无人机或未确定类型标签。
一种示例性的方式中,所述第一网络设备获取终端设备的类型,包括:
所述第一网络设备根据所述终端设备的信息获取所述终端设备的类型。
一种示例性的方式中,所述第一网络设备获取终端设备的类型,包括:
所述第一网络设备接收第二网络设备发送的报告消息,所述报告消息用于报告所述终端设备的类型。
一种示例性的方式中,所述方法还包括:
第二网络设备向第一网络设备识别指示消息,所述识别指示消息用于指示所述第一网络设备对关联的终端设备的类型进行识别;
相应的,所述第一网络设备获取所述终端设备的类型,包括:
所述第一网络设备根据所述识别指示消息获取所述关联的终端设备的类型。
一种示例性的方式中,所述方法还包括:
第二网络设备向第一网络设备识别指示消息,所述识别指示消息中包括所述终端设备的标识,所述识别指示消息用于指示所述第一网络设备对所述终端设备的类型进行识别;
相应的,所述第一网络设备获取所述终端设备的类型,包括:
所述第一网络根据所述识别指示消息获取所述终端设备的类型。
一种示例性的方式中,所述第一网络设备获取终端设备的类型,包括:
所述第一网络设备获取所述终端设备的测量特征数据;
所述第一网络设备根据类型模型和所述测量特征数据,确定所述终端设备的类型。
一种示例性的方式中,所述请求消息中还包括所述终端设备的类型信息。
一种示例性的方式中,所述方法还包括:
所述标签管理设备向所述第一网络设备发送响应消息,所述响应消息中包括标签创建结果。
一种示例性的方式中,所述方法还包括:
所述第一网络设备向所述标签管理设备发送标签查询请求,所述标签查询请求中包括所述终端设备的标识;
所述标签管理设备向所述第一网络设备发送标签查询响应,所述标签查询响应中包括所述终端设备的类型标签。
一种示例性的方式中,所述方法还包括:
所述第一网络设备向UTM发送报告消息,所述报告消息中包括所述终端设备的标识和位置信息。
本申请第五方面提供一种终端设备的标签管理方法,包括:
第一网络设备获取终端设备的类型,所述终端设备的类型包括无人机、非无人机 或未确定类型;
所述第一网络设备向第二网络设备发送报告消息,所述报告消息用于报告所述终端设备的类型;
所述第二网络设备向无人机服务器发送所述报告消息。
一种示例性的方式中,所述第一网络设备获取终端设备的类型,包括:
所述第一网络设备接收第二网络设备发送的报告消息,所述报告消息用于报告所述终端设备的类型。
一种示例性的方式中,所述方法还包括:
第二网络设备向所述第一网络设备发送识别指示消息,所述识别指示消息用于指示所述第一网络设备对关联的终端设备的类型进行识别;
所述第一网络设备获取所述终端设备的类型,包括:
所述第一网络设备根据所述识别指示消息获取所述关联的终端设备的类型。
又一种示例性的方式中,所述方法还包括:
第二网络设备向所述第一网络设备发送识别指示消息,所述识别指示消息中包括所述终端设备的标识,所述识别指示消息用于指示所述第一网络设备对所述终端设备的类型进行识别;
所述第一网络设备获取所述终端设备的类型,包括:
所述第一网络设备根据所述识别指示消息获取所述终端设备的类型。
本申请第六方面提供一种网络设备,包括:
获取模块,用于获取终端设备的类型,所述终端设备的类型包括无人机、非无人机或未确定类型;
发送模块,用于向标签管理设备发送请求消息,所述请求消息用于请求所述标签管理设备为所述终端设备创建类型标签,所述请求消息中包括所述终端设备的标识。
一种示例性的方式中,所述获取模块具体用于:
接收第二网络设备发送的报告消息,所述报告消息用于报告所述终端设备的类型。
一种示例性的方式中,所述获取模块具体用于:
根据所述终端设备的信息获取所述终端设备的类型。
一种示例性的方式中,所述终端设备的信息包括以下信息中的一个或者多个:所述终端设备的能力信息、所述终端设备的签约信息、所述终端设备的类型标签信息、所述终端设备的测量信息、所述终端设备的位置信息和所述终端设备接入的小区的类型。
一种示例性的方式中,所述设备还包括:
接收模块,用于接收来自第二网络设备的识别指示消息,所述识别指示消息用于指示所述第一网络设备对关联的终端设备的类型进行识别;
所述获取模块具体用于:
根据所述识别指示消息获取所述关联的终端设备的类型。
一种示例性的方式中,所述设备还包括:
接收模块,用于接收来自第二网络设备的识别指示消息,所述识别指示消息中包括所述终端设备的标识,所述识别指示消息用于指示所述第一网络设备对所述终端设 备的类型进行识别;
所述获取模块具体用于:
根据所述识别指示消息获取所述终端设备的类型。
一种示例性的方式中,所述获取模块具体用于:
获取所述终端设备的测量特征数据;
根据类型模型和所述测量特征数据,确定所述终端设备的类型。
一种示例性的方式中,所述请求消息中还包括所述终端设备的类型信息。
一种示例性的方式中,所述设备还包括:
接收模块,用于接收所述标签管理设备发送的响应消息,所述响应消息中包括标签创建结果。
一种示例性的方式中,所述设备还包括:
所述发送模块,还用于向所述标签管理设备发送标签查询请求,所述标签查询请求中包括所述终端设备的标识;
接收模块,用于接收所述标签管理设备发送的标签查询响应,所述标签查询响应中包括所述终端设备的类型标签。
一种示例性的方式中,所述发送模块还用于:
向UTM发送报告消息,所述报告消息中包括所述终端设备的标识和位置信息。
一种示例性的方式中,所述网络设备为移动管理实体MME、基站、接入与移动性管理功能AMF网元或网络数据分析功能NWDAF网元。
一种示例性的方式中,所述网络设备移动管理实体MME,所述第二网络设备为基站;或者,
所述网络设备为接入与移动性管理功能AMF网元,所述第二网络设备为NWDAF网元或基站。
本申请第七方面提供一种标签管理设备,包括:
接收模块,用于接收第一网络设备发送的请求消息,所述请求消息用于请求所述标签管理设备为所述终端设备创建类型标签,所述请求消息中包括所述终端设备的标识;
创建模块,用于根据所述请求消息,为所述终端设备创建类型标签,所述终端设备的类型标签包括无人机、非无人机或未确定类型标签。
一种示例性的方式中,所述请求消息中还包括所述终端设备的类型信息。
一种示例性的方式中,所述标签管理设备根据所述请求消息,为所述终端设备创建类型标签之后,还包括:
所述标签管理设备向所述第一网络设备发送响应消息,所述响应消息中包括标签创建结果。
一种示例性的方式中,还包括发送模块;
所述接收模块,还用于接收所述第一网络设备发送的标签查询请求,所述标签查询请求中包括所述终端设备的标识;
所述发送模块,用于向所述第一网络设备发送标签查询响应,所述标签查询响应中包括所述终端设备的类型标签。
一种示例性的方式中,所述第一网络设备为移动管理实体MME、基站、接入与移动性管理功能AMF网元或网络数据分析功能NWDAF网元。
本申请第八方面提供一种网络设备,包括:
获取模块,用于获取终端设备的类型,所述终端设备的类型包括无人机、非无人机或未确定类型;
发送模块,用于向第二网络设备发送报告消息,所述报告消息用于报告所述终端设备的类型。
一种示例性的方式中,所述获取模块具体用于:
接收第二网络设备发送的报告消息,所述报告消息用于报告所述终端设备的类型。
又一种示例性的方式中,所述获取模块具体用于:
根据所述终端设备的信息获取所述终端设备的类型。
一种示例性的方式中,所述终端设备的信息包括以下信息中的一个或者多个:所述终端设备的能力信息、所述终端设备的签约信息、所述终端设备的类型标签信息、所述终端设备的测量信息、所述终端设备的位置信息和所述终端设备接入的小区的类型。
一种示例性的方式中,所述设备还包括:
接收模块,用于接收来自第二网络设备的识别指示消息,所述识别指示消息用于指示所述第一网络设备对关联的终端设备的类型进行识别;
所述获取模块具体用于:
根据所述识别指示消息获取所述关联的终端设备的类型。
又一种示例性的方式中,所述设备还包括:
接收模块,用于接收来自第二网络设备的识别指示消息,所述识别指示消息中包括所述终端设备的标识,所述识别指示消息用于指示所述第一网络设备对所述终端设备的类型进行识别;
所述获取模块具体用于:
所述第一网络根据所述识别指示消息获取所述终端设备的类型。
一种示例性的方式中,当所述第一网络设备为基站时,所述第二网络设备为移动管理实体MME或移动性管理功能AMF网元;或者,
当所述第一网络设备为网络数据分析功能NWDAF网元时,所述第二网络设备为AMF网元。
本申请第九方面提供一种网络设备,包括处理器、存储器和收发器,所述存储器用于存储指令,所述收发器用于和其他设备通信,所述处理器用于执行所述存储器中存储的指令,以使所述网络设备执行如本申请第一方面任一项所述的方法。
本申请第十方面提供一种标签管理设备,包括处理器、存储器和收发器,所述存储器用于存储指令,所述收发器用于和其他设备通信,所述处理器用于执行所述存储器中存储的指令,以使所述标签管理设备执行如本申请第二方面任一项所述的方法。
本申请第十一方面提供一种网络设备,包括处理器、存储器和收发器,所述存储器用于存储指令,所述收发器用于和其他设备通信,所述处理器用于执行所述存储器中存储的指令,以使所述网络设备执行如本申请第三方面任一项所述的方法。
本申请第十二方面提供一种计算机可读存储介质,所述计算机可读存储介质存储有指令,当所述指令被执行时,使得计算机执行如本申请第一方面任一项所述的方法。
本申请第十三方面提供一种计算机可读存储介质,所述计算机可读存储介质存储有指令,当所述指令被执行时,使得计算机执行如本申请第二方面任一项所述的方法。
本申请第十四方面提供一种计算机可读存储介质,所述计算机可读存储介质存储有指令,当所述指令被执行时,使得计算机执行如本申请第三方面任一项所述的方法。
本申请第十五方面提供一种计算机程序产品,所述计算机程序产品包括指令,当所述指令被执行时,使得计算机执行如本申请第一方面任一项所述的方法。
本申请第十六方面提供一种计算机程序产品,所述计算机程序产品包括指令,当所述指令被执行时,使得计算机执行如本申请第二方面任一项所述的方法。
本申请第十七方面提供一种计算机程序产品,所述计算机程序产品包括指令,当所述指令被执行时,使得计算机执行如本申请第三方面任一项所述的方法。
本申请第十八方面提供一种芯片上系统或系统芯片,所述芯片上系统或系统芯片可应用于网络设备,所述芯片上系统或系统芯片包括:至少一个通信接口,至少一个处理器,至少一个存储器,所述通信接口、存储器和处理器通过总线互联,所述处理器通过执行所述存储器中存储的指令,使得所述网络设备可执行本申请第一方面和第三方面中任一方面所述的方法。
本申请第十九方面提供一种芯片上系统或系统芯片,所述芯片上系统或系统芯片可应用于标签管理设备,所述芯片上系统或系统芯片包括:至少一个通信接口,至少一个处理器,至少一个存储器,所述通信接口、存储器和处理器通过总线互联,所述处理器通过执行所述存储器中存储的指令,使得所述标签管理设备执行本申请第二方面所述的方法。
本申请第二十方面提供一种通信系统,包括第一网络设备和标签管理设备,所述第一网络设备用于执行本发明第一方面任一项所述的方法,所述标签管理设备用于执行本申请第二方面任一项所述的方法。
可选的,该通信系统还包括终端设备和上述的第二网络设备。
可选的,该通信系统还包括上述的无人机服务器。
本申请提供一种终端设备的标签管理方法和设备,所述方法包括:第一网络设备获取终端设备的类型,终端设备的类型包括无人机、非无人机或未确定类型,第一网络设备向标签管理设备发送请求消息,请求消息用于请求标签管理设备为终端设备创建类型标签,请求消息中包括终端设备的标识。标签管理设备通过为终端设备创建并保存类型标签,后续第一网络设备或者其他设备可以通过终端设备的标识查询终端设备的类型标签,避免了重复对终端设备的类型进行识别。
附图说明
图1为现有的5G网络架构的一种示意图;
图2为基于服务化接口的5G网络架构的一种示意图;
图3为基于终端设备定位的5G网络架构的一种示意图;
图4为LTE网络架构的一种示意图;
图5为基于终端设备定位的LTE网络架构的一种示意图;
图6为基于服务化接口的5G网络架构的另一种示意图;
图7为LTE网络架构的另一种示意图;
图8为本申请实施例一提供的终端设备的标签管理方法的流程图;
图9为本申请实施例二提供的终端设备的标签管理方法的流程图;
图10为本申请实施例三提供的终端设备的标签管理方法的信令流程图;
图11为本申请实施例四提供的终端设备的标签管理方法的信令流程图;
图12为本申请实施例五提供的终端设备的标签管理方法的信令流程图;
图13为本申请实施例六提供的终端设备的标签管理方法的信令流程图;
图14为本申请实施例七提供的终端设备的标签管理方法的信令流程图;
图15为本申请实施例八提供的终端设备的标签管理方法的流程图;
图16为本申请实施例九提供的网络设备的结构示意图;
图17为本申请实施例十提供的标签管理设备的结构示意图;
图18为本申请实施例十一提供的网络设备的结构示意图;
图19为本申请实施例十二提供的网络设备的结构示意图;
图20为本申请实施例十三提供的标签管理设备的结构示意图。
具体实施方式
本申请提供终端设备的标签管理方法,本申请的方法可以应用在第五代移动通信(5 Generation,5G)系统中,也可以应用在长期演进(Long Term Evolution,LTE)中,5G系统也称为新无线通信系统、新接入技术(New Radio,NR)或者下一代移动通信系统。
图1为现有的5G网络架构的一种示意图,5G网络架构包括终端设备、接入网(access network,AN)、核心网和数据网络(Data Network,DN)。其中,接入网装置主要用于实现无线物理层功能、资源调度和无线资源管理、无线接入控制以及移动性管理等功能;核心网设备可以包含管理设备和网关设备,管理设备主要用于终端设备的设备注册、安全认证、移动性管理和位置管理等,网关设备主要用于与终端设备间建立通道,在该通道上转发终端设备和外部数据网络之间的数据包;数据网络可以包含网络设备(如:服务器、路由器等设备),数据网络主要用于为终端设备提供多种数据业务服务。
5G系统中的接入网可以是无线接入网(radio access network,(R)AN,5G系统中的(R)AN设备可以由多个5G-(R)AN节点组成,该5G-(R)AN节点可以包括:非3GPP的接入网络如WiFi网络的接入点(access point,AP)、下一代基站(可统称为新一代无线接入网节点(NG-RAN node),其中,下一代基站包括新空口基站(NR nodeB,gNB)、新一代演进型基站(NG-eNB)、中心单元(central unit,CU)和分布式单元(distributed unit,DU)分离形态的gNB等)、收发点(transmission receive point, TRP)、传输点(transmission point,TP)或其它节点。
5G核心网(5G core/new generation core,5GC/NGC)包括接入和移动性管理功能(Access and Mobility Management Function,AMF)网元、会话管理功能(Session Management Function,SMF)网元、用户面功能(User Plane Function,UPF)网元、鉴权服务器功能(Authentication Server Function,AUSF)网元、策略控制功能(Policy Control Function,PCF)网元、应用功能(Application Function,AF)网元、统一数据管理功能(unified data management,UDM)网元、网络切片选择功能(Network Slice Selection Function,NSSF)网元等多个功能单元。
AMF网元主要负责移动性管理、接入管理等服务。SMF网元主要负责会话管理、动态主机配置协议功能、用户面功能的选择和控制等。UPF网元主要负责对外连接到数据网络(data network,DN)以及用户面的数据包路由转发、报文过滤、执行服务质量(quality of service,QoS)控制相关功能等。AUSF主要负责对终端设备的认证功能等。PCF网元主要负责为网络行为管理提供统一的策略框架、提供控制面功能的策略规则、获取与策略决策相关的注册信息等。需要说明的是,这些功能单元可以独立工作,也可以组合在一起实现某些控制功能,如对终端设备的接入鉴权、安全加密、位置注册等接入控制和移动性管理功能,以及用户面传输路径的建立、释放和更改等会话管理功能。
5GC中各功能单元之间可以通过下一代网络(next generation,NG)接口进行通信,如:UE可以通过NG接口1(简称N1)与AMF网元进行控制面消息的传输,RAN设备可以通过NG接口3(简称N3)与UPF建立用户面数据传输通道,AN/RAN设备可以通过NG接口2(简称N2)与AMF网元建立控制面信令连接,UPF可以通过NG接口4(简称N4)与SMF网元进行信息交互,UPF可以通过NG接口6(简称N6)与数据网络DN交互用户面数据,AMF网元可以通过NG接口11(简称N11)与SMF网元进行信息交互,SMF网元可以通过NG接口7(简称N7)与PCF网元进行信息交互,AMF网元可以通过NG接口12(简称N12)与AUSF进行信息交互。
需要说明的是,图1仅为示例性架构图,除图1中所示功能单元之外,该网络架构还可以包括其他功能单元。
图2为基于服务化接口的5G网络架构的一种示意图,如图2所示,基于服务化接口的架构下,5G系统的核心网还包括网络开放功能(Network Exposure Function,NEF)和网络存储功能(Network Repository Function,NRF)网元。
基于服务化接口的架构下,5G核心网中的部分网元通过总线方式连接,如图2所示,AUSF网元、AMF网元、SMF网元、AF网元、UDM、PCF网元、NRF网元、NEF网元和NSSF网元通过总线互连,所述网元在通过总线互连时,采用服务化接口,例如,AUSF网元通过Nausf接口连接到总线上,AMF网元采用Namf接口连接到总线上,SMF网元通过Nsmf接口连接到总线上,AF网元采用Naf接口连接到总线上,UDM采用Nudm接口连接到总线上,PCF网元通过Npcf接口连接到总线上,NRF通过Nnrf接口连接到总线上,NEF通过Nnef接口连接到总线上,NSSF通过Nnssf接口连接到总线上。
图3为基于终端设备定位的5G网络架构的一种示意图,如图3所示,该网络架 构包括:终端设备、RAN、核心网和外部客户端。其中,RAN的实现方式参照图1所示架构的描述,核心网网元包括:AMF、UDM、位置管理功能(Location Management Function,LMF)、网关移动位置中心(Gateway Mobile Location Centre,GMLC)和位置获取功能实体(Location Retrieval Function,LRF)。
AMF和UDM的功能参照图1所示架构的描述,GLMC用于支持3GPP网络的定位服务,是外部位置程序访问网络的第一个节点,执行注册授权检查和从UDM请求路由信息,执行完注册授权检查后,将定位请求发送给AMF,并接收最终的位置估计(Location estimate)。LMF用于确定终端设备的位置,获取下行测量信息(location measurement)或终端设备获取位置估计,从RAN获取上行位置测量以及非终端设备相关的辅助信息。
LRF用于为外部客户端获取与终端设备有关的位置信息,包括要求定位的实体、临时位置信息、初始定位信息和更新的定位信息。LRF可以与单独的GMLC交互,也可以与GMLC集成以获得定位信息。LRF也可以与其他类型的位置服务器(Location Server)交互或集成来获得位置信息。
图4为LTE网络架构的一种示意图,如图4所示,LTE系统中的接入网设备为eNB,LTE系统的核心网为演进分组核心网(Evolved Packet Core,EPC),EPC包括:移动性管理实体(mobility management entity,MME)、分组数据网关(packet data network gateway,P-GW)、业务网关(Serving Gateway,S-GW)、归属网络服务器(Home Subscriber Server,HSS)等。
其中,HSS用于存储用户签约信息,包括用户业务信息、鉴权信息、位置管理信息等;MME负责终端接入控制、移动性管理、会话管理、网元选择(如S-GW/P-GW选择)等功能;SGW是eNB之间切换的移动性锚点,负责用户面数据的路由转发等功能;PGW则负责网际协议(Internet Protocol,IP)地址分配、分组数据过滤、速率控制和计费规则的执行以及合法监听等功能。
5G系统和LTE系统中的终端设备也称为用户设备(User Equipment,UE),终端设备可以是:手机、电脑,还可以为蜂窝电话、无绳电话、会话发起协议(session initiation protocol,SIP)电话、智能电话、无线本地环路(wireless local loop,WLL)站、个人数字助理(personal digital assistant,PDA)、电脑、膝上型计算机、手持式通信设备、手持式计算设备、卫星无线设备、无线调制解调器卡、电视机顶盒(set top box,STB)、车载设备、可穿戴设备、智能家居设备、用于在无线系统上进行通信的其它设备等。
图5为基于终端设备定位的LTE网络架构的一种示意图。GMLC和LRF的功能与5G网络中的功能相同,参照图3所示网络架构的相关描述,E-SMLC将客户端请求的位置要求转换为相应的E-UTRAN测量参数,并为终端设备选择定位方法,对位置估计进行计算得到终端设备最终的位置信息。
为了在移动通信网络中支持无人机通信和监管,可以在LTE系统和5G系统中增加一个专门用于处理无人机业务的核心网网元:无人机业务控制网元(UAV control function,UCF)。UCF可以支持以下业务:向无人机配置通信参数,从UTM获取无人机禁飞区域并分发,无人机的飞行辅助授权,接收UTM的无人机服务(无人机识 别,无人机位置追踪等)订阅,并与其他核心网网元(MME,GMLC等)交互为UTM提供订阅的无人机服务等。该网元也可以是LTE系统和5G系统中增加的用于为应用业务提供服务的控制网元:业务控制网元(service control function,SCF),该控制网元实现了UCF的功能。
无人机服务器负责无人机应用相关的业务管理,可以包括无人机监管相关的业务,如无人机的登记注册、飞行计划审批、飞行操作授权、飞行监视、飞行告警、飞行管制等,还可以包括无人机应用业务的控制和管理,如无人机数据采集,视频数据管理等。无人机服务器还可以包括其他一些增值业务,如数据分析,天气情况通知等。
本申请中,无人机服务器可是看作是5G系统中的应用功能(application function,AF)的一个实例(instance),或者无人机服务器可以作为第三方服务器位于DN中。
本申请中无人机服务器也可以称为无人机服务提供商USS(UAS service supplier)、无人机交通服务UTS(UAS traffic service)或UTM服务器,或无人机交通管理平台。
图6为基于服务化接口的5G网络架构的另一种示意图,如图6所示,本实施例与图3所示5G网络架构相比多了UCF,UCF通过总线与网络中的其他网元连接通信,UTM集成在DN中。
图7为LTE网络架构的另一种示意图,如图7所示,本实施例与图4所示LTE网络架构相比多了UCF网元,UCF网元分别与终端设备、MME以及无人机服务器连接。
基于图1-图7所示的网络结构,本申请实施例一提供一种终端设备的标签管理方法,图8为本申请实施例一提供的终端设备的标签管理方法的流程图,如图8所示,本实施例提供的方法包括以下步骤:
步骤S101、第一网络设备获取终端设备的类型,终端设备的类型包括无人机、非无人机或未确定类型。
该第一网络设备可以为LTE系统中的基站或者MME,也可以为5G系统中的基站、AMF网元或者网络数据分析功能(Network Data Analytics Function,NWDAF)网元。第一网络设备可以通过如下几种方式获取终端设备的类型:
方式一、第一网络设备根据终端设备的信息获取终端设备的类型。
第一网络设备根据终端设备的信息获取终端设备的类型之前,需要获取终端设备的信息,可选的,终端设备的信息包括以下信息中的一个或者多个:终端设备的能力信息、终端设备的签约信息、终端设备的类型标签信息、终端设备的测量信息、终端设备的位置信息和终端设备接入的小区的类型。
终端设备的能力信息可以携带在无线资源控制(Radio Resource Control,RRC)连接重配置消息中,或者非接入层(non-access stratum,NAS)消息中。终端设备的能力信息用于指示终端设备的类型,终端设备的能力信息可以为空中通信能力指示信息、无人机类型指示信息、飞行能力指示信息和地面普通UE指示信息等。
如果终端设备的能力信息表明终端的类型为非无人机类型,则第一网络设备可以根据终端设备的其他信息识别终端设备的类型。如果终端设备的能力信息表明终端设备的类型为无人机类型,则第一网络设备确定终端设备的类型为无人机类型。
当第一网络设备为LTE系统中的eNB时,eNB从MME接收终端设备的标签信息, 标签信息中可以包括终端设备的类型标签,如果标签信息中包括的终端设备的标签类型为无人机类型或者非无人机类型,第一网络设备确定终端设备的类型为无人机类型或者非无人机类型,并且不执行后续的步骤,如果标签信息中包括的终端设备的标签类型为不确定类型,则第一网络设备可以通过终端设备的其他信息对终端设备的类型进行识别。
终端设备的标签信息可以携带在MME发送给eNB的S1 AP Initial Context Setup Request(S1 AP初始上下文建立请求)中。或者,eNB在S1 AP Initial Context Setup response(S1 AP初始上下文建立响应)中向MME请求终端设备的签约信息,MME在S1-AP UE Context Modification Request(S1-AP UE上下文修改请求)中发送给eNB。终端设备的标签信息还可以携带在切换请求响应消息中,或其他MME发给eNB的信令消息中,本实施例不对此进行限制。
当第一网络设备为5G系统中的gNB时,gNB从AMF网元接收终端设备的标签信息,根据终端设备的标签信息获取终端设备的类型,具体的获取方式参照eNB获取终端设备的类型的方式。
AMF网元可以将终端设备的标签信息携带在N2消息中发给gNB,N2消息例如为N2 PDU会话请求或N2会话请求。AMF网元还可以在注册流程、服务请求流程或切换流程等其他流程中将终端设备的标签信息携带在发给gNB的N2消息中。
当第一网络设备为LTE系统中的eNB时,eNB从MME接收终端设备的签约信息,终端设备的签约信息中包括了终端设备是否签约了无人机业务的指示信息,如果该指示信息指示终端设备签约了无人机业务,则eNB确定终端设备的类型为无人机类型,如果该指示信息指示终端设备没有签约无人机业务,则eNB可以通过终端设备的其他信息对终端设备的类型进行识别。
当第一网络设备为5G系统中的gNB时,eNB从AMF网元接收终端设备的签约信息,根据终端设备的签约信息获取终端设备的类型,具体的获取方式参照eNB的方式。
非无人机类型的终端设备由于业务不同,很多情况下位置比较固定或者移动速度较慢,因此,相邻小区的数量较少,且固定,而无人机由于移动速度较快,小区之间切换比较频繁,因此,相邻小区的数目较多。因此,第一网络设备可以基于终端设备的测量信息获取终端设备的类型。
终端设备的测量信息可以包括终端设备的相邻小区的数目和标识等,当终端设备的相邻小区的数目较多,例如,大于预设的数量阈值时,第一网络设备确定终端设备的类型为无人机类型,当终端设备的相邻小区的数目小于该数量阈值时,第一网络设备可以通过终端设备的其他信息对终端设备的类型进行识别。
终端设备的通信特征可以为终端设备的测量特征数据,第一网络设备获取终端设备的测量特征数据,将终端设备的测量特征数据输入预先训练得到的类型模型,得到终端设备的类型。
终端设备的测量信息还可以包括测量特征数据,该测量特征数据包括多径时延、多普勒频移、参考信号接收功率(Reference Signal Receiving Power,RSRP)的大小或者变化趋势、信号与干扰加噪声比(Signal to Interference plus Noise Ratio,SINR)的 大小或者变化趋势。
无人机由于采用视距(Line-of-sight,LOS)传播,无人机的多径时延扩展相对于其他类型的终端设备较小。因此,第一网络设备根据终端设备的多径时延的大小可以确定终端设备的类型是否为无人机类型。
无人机由于高速移动,使得无人机的多普勒频移比其他类型的终端设备的多普勒频移大。第一网络设备根据终端设备的多普勒频移的大小可以确定终端设备的类型是否为无人机类型。
无人机通常情况在空中飞行,而非无人机类型的终端设备位于地面,因此,可以基于终端设备的位置信息获取终端设备的类型。例如,当终端设备的位置信息表明终端设备位于空中时,第一网络设备确定终端设备的类型为无人机类型,当终端设备的位置信息表明终端设备位于地面时,第一网络设备可以通过终端设备的其他信息对终端设备的类型进行识别。
其中,当第一网络设备为接入网节点时,接入网节点可以在路测的最小化(MDT)报告中获取终端设备的位置信息。
在一些场景中,某些小区只处理特定的业务,只有具有该特定业务的终端设备才会接入该小区,因此,第一网络设备可以根据终端设备接入的小区的类型,获取终端设备的类型。例如,终端设备接入的小区为无人机类型终端服务的小区,则确定终端设备的类型为无人机类型,如果终端设备接入的小区为普通小区,则确定终端设备的类型为非无人机类型,或者通过终端设备的其他信息对终端设备的类型进行识别。
方式二、当第一网络设备为MME或者AMF网元时,第一网络设备接收第二网络设备发送的报告消息,该报告消息用于报告终端设备的类型。当第一网络设备为MME时,第二网络设备可以为基站,当第一网络设备为AMF时,第二网络设备可以为基站或者NWDAF网元。
可选地,当第一网络设备为基站时,当第一网络设备获取终端设备的类型后,该第一网络设备可以向MME或AMF网元发送该报告消息。当第一网络设备为NWDAF网元时,当第一网络设备获取终端设备的类型后,该第一网络设备向AMF发送该报告消息。
该报告信息用于报告识别出终端设备的类型,可选的,该报告消息中包括终端设备的标识和/或终端设备的位置信息。该报告消息可以为UAV report,该报告消息可以采用第一网络设备和第二网络设备之间的现有消息,例如S1 AP UE context response消息,也可以采用新定义的消息。
其中,第二网络设备可以根据终端设备的能力信息识别终端设备的类型,第二网络设备识别终端设备的类型的具体方法与第一网络设备识别终端设备的类型的方法相同,参照上述第一网络设备识别终端设备的类型的具体方法,这里不再赘述。
为了节约网络资源,提高获取终端设备的类型的准确程度,第一网络设备对终端设备的类型的识别,可以是周期性的,还可以基于事件触发的。其中,对于周期性的识别,周期可以是预配置在第一网络设备的预设时间段,如每天10:00至18:00。对于事件触发的识别,事件可以是终端设备的位置高于预设的高度、终端设备接入的小区类型为空中小区、终端设备上报的小区数目超过预设数值、终端设备切换频繁、或者 接受到其他设备的请求消息。
可选的,第一网络设备获取终端设备的类型之前,第一网络设备接收来自第二网络设备的识别指示消息,识别指示消息用于指示第一网络设备对关联的终端设备的类型进行识别。相应的,第一网络设备根据该识别指示消息,对关联的终端设备的类型进行识别,得到关联的终端设备的类型。其中,第一网络设备获取每个终端设备的类型的方式参照上述方式一和方式二描述的方法,这里不再赘述。
该识别指示消息可以为无人机识别请求(unmanned aerial vehicle,UAV)identification request消息。第一网络设备收到该识别指示消息后,确定获取关联的终端设备(可以理解为所有连接到该第一网络设备的终端设备,如对于接入网节点,可以是所有接入到该接入网节点的终端设备,再如对于移动性管理网元,可以是和该移动性管理网元的有控制面信令连接的终端设备)的类型。
可选的,该识别指示消息中包括终端设备的标识,该识别指示消息用于指示第一网络设备对该终端设备的标识对应的终端设备的类型进行识别。可选的,该识别指示消息中包括的终端设备的标识可以为一个或者多个。
第二网络设备可以在以下情况下向第一网络设备发送该识别指示消息:当第二网络设备根据统计信息确定终端设备的位置高于预设的高度、终端设备接入的小区类型为空中小区、终端设备上报的小区数目超过预设数值或终端设备频繁切换等等,则向第一网络设备发送该识别指示消息。
上述例子以第一网络设备根据终端设备的单个信息获取终端设备的类型为例进行说明,可以理解,第一网络设备也可以结合终端设备的能力信息、终端设备的签约信息、终端设备的类型标签信息、终端设备的测量信息、终端设备的位置信息和终端设备接入的小区的类型中的多个信息获取终端设备的类型。
方式三、第一网络设备获取终端设备的测量特征数据,根据类型模型和测量特征数据,确定终端设备的类型。该测量特征数据包括多径时延、多普勒频移、RSRP的大小或者变化趋势、SINR的大小或者变化趋势。
步骤S102、第一网络设备向标签管理设备发送请求消息,请求消息用于请求标签管理设备为终端设备创建类型标签。
本申请实施例在LTE系统和5G系统现有网元的基础上增加了标签管理设备,标签管理设备用于为终端设备创建类型标签,保存终端设备的类型标签。
标签管理设备可以为一个独立的网元,还可以集成在已有网元中,例如,集成在UCF网元、SCEF网元、NEF网元、HSS、UDM或者UDR中。为终端设备创建类型标签可以理解为生成该终端设备和类型标签的关联关系,保存终端设备的类型标签可以理解为保存该终端设备标识和类型标签的关联关系。
本实施例中,当第一网络设备为LTE系统中的基站时,基站可以通过MME向标签管理设备转发该请求消息。当第一网络设备为5G系统中的基站或者NWDAF网元时,基站或NWDAF网元可以通过AMF网元向标签管理设备转发该请求消息。当第一网络设备为MME或者AMF网元时,MME或者AMF网元可以直接向标签管理设备发送该请求消息。
该请求消息中包括终端设备的标识,以指示标签管理设备为哪个终端设备创建类 型标签。可选的,该请求消息中还可以包括终端设备的类型信息,其中类型信息指示请求创建的类型标签,类型信息可以为类型标签,也可以不是类型标签。当类型信息不是类型标签时,可以通过多个比特位指示终端设备的类型,例如,通过两比特信息指示终端设备的类型,00表示终端设备的类型为无人机类型,01表示终端设备的类型为非无人机类型,11表示终端设备的类型为未确定类型。通过携带终端设备的类型信息以显示指示标签管理设备为终端设备创建什么类型的标签。
当类型信息为类型标签时,标签管理设备保存该终端设备标识和类型标签的关联关系。当类型信息不是类型标签时,标签管理设备根据类型信息生成终端设备的类型标签,并保存该终端设备标识和类型标签的关联关系。
当该请求消息中不包括终端设备的类型信息时,可以通过不同的消息名称或消息类型隐式指示终端设备的类型,例如无人机、非无人机或未确定类型分别通过三种不同的请求消息以创建不同的类型标签,例如无人机标签创建请求消息、非无人机标签创建请求消息、未确定类型标签创建请求消息。
或者,当该请求消息中不包括终端设备的类型信息时,默认为终端设备创建无人机类型的标签。
或者,该标签管理设备为无人机专用网元,标签管理设备接收到请求消息后,默认为终端设备创建无人机类型的标签。
可选的,标签管理设备为终端设备创建类型标签后,向第一网络设备发送请求消息对应的响应消息,第一网络设备接收标签管理设备发送的响应消息,响应消息中包括标签创建结果,其中标签创建结果可以包括创建成功、更新成功、创建失败或更新失败。
可选的,第一网络设备向标签管理设备发送标签查询请求,该标签查询请求中包括终端设备的标识,标签查询请求用于请求查询终端设备的类型标签。
标签管理设备根据标签查询请求中包括的终端设备的标识查询终端设备的类型标签,并向第一网络设备发送标签查询响应,标签查询响应中包括查询结果。如果查询到终端设备的类型标签,则查询结果为终端设备的类型标签。如果没有查询到终端设备的类型标签,则查询结果为终端设备没有对应的类型标签。
当第一网络设备根据查询结果获知终端设备没有对应的类型标签后,则可以通过本实施例的方法为该终端设备创建类型标签。当第一网络设备获取到该终端的标签类型时,第一网络设备根据获取的该终端类型发起对终端设备的识别过程,以便可以更新该终端设备的标签。例如,当获取到的标签类型为未确定类型,则第一网络设备对该终端设备发起识别,若这次识别该终端是无人机设备,则第一网络设备可以更新该终端的标签类型。
可选的,第一网络设备还向无人机服务器发送识别报告消息,识别报告消息用于指示识别到了无人机。其中识别报告消息中可以包括终端设备的标识和位置信息,以便于无人机服务器根据对终端设备进行管理。
本实施例中,第一网络设备获取终端设备的类型,终端设备的类型包括无人机、非无人机或未确定类型,第一网络设备向标签管理设备发送请求消息,请求消息用于请求标签管理设备为终端设备创建类型标签,请求消息中包括终端设备的标识。标签 管理设备通过为终端设备创建并保存类型标签,后续第一网络设备或者其他设备可以通过终端设备的标识查询终端设备的类型标签,避免了重复对终端设备的类型进行识别。
图9为本申请实施例二提供的终端设备的标签管理方法的流程图,如图9所示,本实施例提供的方法包括以下步骤:
步骤S201、标签管理设备接收第一网络设备发送的请求消息,请求消息用于请求标签管理设备为终端设备创建类型标签,请求消息中包括终端设备的标识。
可选的,该请求消息中还包括终端设备的类型信息,其中类型信息指示请求创建的类型标签,类型信息可以为类型标签,也可以不是类型标签。
当该请求消息中不包括终端设备的类型信息时,第一网络设备可以通过不同的消息名称或消息类型隐式指示终端设备的类型,例如无人机、非无人机或未确定类型分别通过三种不同的请求消息以创建不同的类型标签,例如无人机标签创建请求消息、非无人机标签创建请求消息、未确定类型标签创建请求消息。
本实施例中,当第一网络设备为LTE系统中的基站时,基站可以通过MME向标签管理设备转发该请求消息。当第一网络设备为5G系统中的基站或者NWDAF网元时,基站或NWDAF网元可以通过AMF网元向标签管理设备转发该请求消息。当第一网络设备为MME或者AMF网元时,MME或者AMF网元可以直接向标签管理设备发送该请求消息。
步骤S202、标签管理设备根据请求消息,为终端设备创建类型标签。
标签管理设备根据请求消息或者请求消息中包括的终端设备的类型信息,确定为终端设备创建的标签的类型,终端设备的类型标签包括无人机、非无人机或未确定类型标签。为终端设备创建类型标签可以理解为生成该终端设备和类型标签的关联关系,保存终端设备的类型标签可以理解为保存该终端设备和类型标签的关联关系。
标签管理设备接收到请求消息后,根据终端设备的标识查询是否已经为该终端设备创建过类型标签,如果没有为该终端设备创建过类型标签,则生成该终端设备的标识和类型标签的关联关系,如果已经为该终端设备创建过类型标签,则更新终端设备的类型标签。
当该请求消息中包括终端设备的类型信息时,如果类型信息为类型标签,则标签管理设备保存该终端设备标识和类型标签的关联关系。如果类型信息不是类型标签,则标签管理设备根据类型信息生成终端设备的类型标签,并保存该终端设备标识和类型标签的关联关系。
通常情况下不会重复为终端设备创建类型标签,重复创建的场景可以适用于以下场景:第一次识别出的终端设备的类型为未确定类型,后续在识别出终端设备的类型为无人机或者非无人机时,更新终端设备的类型标签。
如果标签管理设备为无人机专用网元,那么标签管理设备只需要保存终端设备的标识即可,不需要保存终端设备的标识和类型标签的对应关系。
可选的,标签管理设备为所述终端设备创建类型标签之后,向第一网络设备发送响应消息,响应消息中包括标签创建结果,标签创建结果可以为创建成功、创建失败、 更新成功或者更新失败。
可选的,标签管理设备接收第一网络设备发送的标签查询请求,标签查询请求中包括终端设备的标识,标签管理设备查询终端设备的类型标签,并将查询结果携带在标签查询响应中发送给第一网络设备。如果查询到终端设备的类型标签,则查询结果为终端设备的类型标签。如果没有查询到终端设备的类型标签,则查询结果为终端设备没有对应的类型标签。
本实施例中,标签管理设备接收第一网络设备发送的请求消息,请求消息用于请求标签管理设备为终端设备创建类型标签,请求消息中包括终端设备的标识,标签管理设备根据请求消息,为终端设备创建类型标签,终端设备的类型标签包括无人机、非无人机或未确定类型标签。标签管理设备通过为终端设备创建并保存类型标签,后续第一网络设备或者其他设备可以通过终端设备的标识查询终端设备的类型标签,避免了重复对终端设备的类型进行识别。
图10为本申请实施例三提供的终端设备的标签管理方法的信令流程图,本实施例以5G系统为例进行说明,如图10所示,本实施例提供的方法包括以下步骤:
步骤S301、gNB获取终端设备的信息。
终端设备的信息包括以下信息中的一个或者多个:终端设备的能力信息、终端设备的签约信息、终端设备的类型标签信息、终端设备的测量信息、终端设备的位置信息和终端设备接入的小区的类型。
步骤S302、AMF网元向gNB发送识别指示消息。
该识别指示消息可以为UVA identification request,可选的,该识别指示消息中包括终端设备的标识。当AMF网元根据统计信息发现该终端设备频繁切换、者驻留的小区频繁切换、收到其他节点的无人机识别请求消息或无人机识别服务订阅消息、或AMF网元初步识别该终端设备为可疑无人机时,或周期性向gNB发送识别指示消息。AMF网元也可以在其他时机向gNB发送识别指示消息,本申请不再赘述。
步骤S302为可选步骤,步骤S302也可以在步骤301之前进行。
步骤S303、gNB确定对终端设备的类型进行识别。
gNB可以周期性确定对终端设备的类型进行识别,也可以基于事件触发确定对中终端设备的类型进行识别,具体方式参照实施例一的描述,这里不再赘述。
步骤S304、gNB根据终端设备的信息识别终端设备的类型。
步骤S305、gNB向AMF网元发送报告消息。
该步骤为可选步骤,该报告信息用于报告AMF网元自己识别出终端设备的类型的识别事件,可选的,该报告消息中包括终端设备的标识和/或终端设备的位置信息。
该报告消息可以为UAV report,该报告消息可以采用gNB和AMF网元之间的现有消息,例如S1 AP UE context response消息,也可以为新定义的消息。
步骤S306、AMF网元向NEF/UCF网元发送该报告消息。
其中,该步骤可选步骤。
步骤S307、NEF/UCF网元向无人机服务器发送该报告消息。
其中,该步骤为可选步骤。
步骤S308、gNB向AMF网元发送请求消息。
请求消息用于请求标签管理设备为终端设备创建类型标签,请求消息中包括终端设备的标识,可选的,该请求消息中还包括终端设备的类型信息。该请求消息可以为UAV label creat request。
需要说明的是,步骤S305和S308在执行时并没有先后顺序,也可以同时执行。
步骤S309、AMF网元向标签管理设备发送该请求消息。
步骤S310、标签管理设备为终端设备创建类型标签。
步骤S311、标签管理设备向AMF网元发送响应消息。
该响应消息中包括创建结果,该响应消息可以为UAV label creat response。
步骤S312、AMF网元向gNB发送响应消息。
本实施例的流程也可以应用在LTE系统中,应用在LTE系统时,将gNB替换为eNB,将AMF网元替换为MME,创建流程不变,这里不再详细说明。
本实施例的具体实现方式参照实施例一和实施例二的相关描述,这里不再赘述。
图11为本申请实施例四提供的终端设备的标签管理方法的信令流程图,本实施例以5G系统为例进行说明,如图11所示,本实施例提供的方法包括以下步骤:
步骤S401、gNB获取终端设备的信息。
终端设备的信息包括以下信息中的一个或者多个:终端设备的能力信息、终端设备的签约信息、终端设备的类型标签信息、终端设备的测量信息、终端设备的位置信息和终端设备接入的小区的类型。
步骤S402、AMF网元向gNB发送识别指示消息。
该步骤为可选步骤,也可以在步骤S401之前执行。
步骤S403、gNB确定对终端设备的类型进行识别。
gNB可以周期性确定对终端设备的类型进行识别,也可以基于事件触发确定对中终端设备的类型进行识别就,具体方式参照实施例一的描述,这里不再赘述。
步骤S404、gNB根据终端设备的信息识别终端设备的类型。
步骤S405、gNB向AMF网元发送报告消息。
该报告消息中包含终端设备的标识,还可以包含终端设备的类型信息,还可以包含终端设备的位置信息。
步骤S406、AMF网元向NEF/UCF发送该报告消息。
其中,该步骤可选步骤。
步骤S407、NEF/UCF网元向无人机服务器发送该报告消息。
其中,该步骤可选步骤。
步骤S408、AMF网元向标签管理设备发送该请求消息。
步骤S409、标签管理设备为终端设备创建类型标签。
步骤S410、标签管理设备向AMF网元发送响应消息。
步骤S411、AMF网元向gNB发送响应消息。
与实施例三不同的是,实施例三中由gNB识别出终端设备的类型后,向标签管理设备发送请求消息,触发类型标签的创建,本实施例中由AMF网元接收到报告消息 后,向标签管理设备发送请求消息,触发类型标签的创建。相应的,本实施例中,gNB向AMF网元发送的报告消息中必须包括终端设备的标识,以便于AMF网元后续确定为哪个终端设备创建类型标签,而实施例三中该报告消息中可以不携带终端设备的标识。其他步骤与实施例三相同,这里不再赘述。
本实施例的流程也可以应用在LTE系统中,应用在LTE系统时,将gNB替换为eNB,将AMF网元替换为MME,创建流程不变,这里不再详细说明。
本实施例的具体实现方式参照实施例一和实施例二的相关描述,这里不再赘述。
图12为本申请实施例五提供的终端设备的标签管理方法的信令流程图,本实施例以5G系统为例进行说明,如图12所示,本实施例提供的方法包括以下步骤:
步骤S501、NWDAF网元获取终端设备的标签数据和/或签约数据。
NWDAF网元可以从UDM、UTM、UCF网元或NEF网元获取终端设备的签约数据,可以从标签管理设备获取终端设备的标签数据。
终端设备的标签数据用于指示是否为终端设备创建了类型标签,如果创建了类型标签,则标签数据中包括终端设备的类型标签。MWDAF后续可以根据终端设备的标签数据和/或签约数据,确定是否对终端设备的类型进行识别。
如果标签数据指示没有创建类型标签,则NWDAF确定对终端设备的类型进行识别。或者,标签数据指示创建了类型标签,且类型标签为不确定类型或者非无人机类型,则NWDAF确定对终端设备的类型进行识别。如果标签数据指示创建了类型标签,且类型标签为无人机类型,则NWDAF确定不对终端设备的类型进行识别。
如果签约数据指示终端设备没有签约无人机业务,则NWDAF确定对终端设备的类型进行识别,如果签约数据指示终端设备签约了无人机业务,则NWDAF确定不对终端设备的类型进行识别。
如果签约数据指示终端设备没有签约无人机业务,并且标签数据指示终端设备的类型为不确定类型,则确定对该终端设备的类型进行识别。为了避免遗漏无人机,如果签约数据指示终端设备没有签约无人机业务,并且标签数据指示终端设备的类型为非无人机类型,也可以确定对终端设备的类型进行识别。
步骤S502、NWDAF网元获取终端设备的训练数据。
该训练数据可以包括大量的终端设备的测量特征数据,NWDAF网元可以从gNB或者运营和管理(Operation Administration and Maintenance,OAM)设备获取该训练数据。
步骤S503、NWDAF网元对训练数据进行训练得到类型模型。
其中,该类型模型用于识别终端设备的类型。
步骤S502和S503为可选步骤。
步骤S504、AMF网元向NWDAF网元发送识别指示消息。
该步骤为可选步骤。
步骤S505、NWDAF网元向gNB/OAM发送测量特征数据的请求/订阅消息。
该订阅消息可以为UE measurement data subscribe,该订阅消息中包括终端设备的标识。
步骤S506、gNB/OAM向NWDAF网元发送请求/订阅响应消息。
该请求/订阅响应消息中包括终端设备的测量特征数据,该请求/订阅响应消息可以为UE measurement data notify。
步骤S507、NWDAF网元根据类型模型和终端设备的测量特征数据,确定终端设备的类型。
NWDAF将终端设备的测量特征数据输入预先训练得到的类型模型,得到终端设备的类型。
步骤S508、NWDAF网元向无人机服务器发送报告消息。
该步骤为可选步骤。
可选的,该报告消息中包括终端设备的标识和/或终端设备的位置信息。NWDAF网元可以通过NEF/UCF网元将报告消息转发给无人机服务器。
步骤S509、NWDAF网元向AMF网元发送识别响应消息。
该步骤为可选步骤。
该识别响应消息用于响应AMF网元发送的识别指示消息,如果识别指示消息中包括终端设备的标识,则该识别响应消息中也包括终端设备的标识,可选的,识别响应消息中还可以包括终端设备的位置信息。如果识别指示消息中不包括终端设备的标识,则该识别响应消息中不包括终端设备的标识。
步骤S510、NWDAF网元向标签管理设备发送请求消息。
请求消息用于请求标签管理设备为终端设备创建类型标签。
步骤S511、标签管理设备为终端设备创建类型标签。
步骤S512、标签管理设备向NWDAF网元发送响应消息。
其中,响应消息中包括创建结果。
本实施例中,NWDAF网元通过大数据分析得到类型模型,后续将终端设备的测量特征数据输入预先训练得到的类型模型,得到终端设备的类型,使得识别结果更加准确。
本实施例的具体实现方式参照实施例一和实施例二的相关描述,这里不再赘述。
图13为本申请实施例六提供的终端设备的标签管理方法的信令流程图,本实施例以5G系统为例进行说明,如图13所示,本实施例提供的方法包括以下步骤:
步骤S601、NWDAF网元获取终端设备的标签数据和/或签约数据。
步骤S602、NWDAF网元获取终端设备的训练数据。
步骤S603、NWDAF网元对训练数据进行训练得到类型模型。
步骤S604、AMF网元向NWDAF网元发送识别指示消息。
该步骤为可选步骤。
步骤S605、NWDAF网元向gNB/OAM发送测量特征数据的请求/订阅消息。
步骤S606、gNB/OAM向NWDAF网元发送请求/订阅响应消息。
步骤S607、NWDAF网元根据类型模型和终端设备的测量特征数据,确定终端设备的类型。
步骤S608、NWDAF网元向无人机服务器发送报告消息。
该步骤为可选步骤。
步骤S609、NWDAF网元向AMF网元发送识别响应消息。
该步骤为可选步骤。
步骤S610、AMF网元向标签管理设备发送请求消息。
步骤S611、标签管理设备为终端设备创建类型标签。
步骤S612、标签管理设备向NWDAF网元发送响应消息。
本实施例与实施例五的区别为:实施例五中NWDAF网元识别出终端设备的类型后,由NWDAF网元向标签管理设备发送请求消息,触发类型标签的建立,本实施例中由AMF网元接收报告消息后,向标签管理设备发送请求消息,触发类型标签的建立。其他流程与实施例五相同,参照实施例五的相关描述,这里不再赘述。
本实施例的具体实现方式参照实施例一和实施例二的相关描述,这里不再赘述。
图14为本申请实施例七提供的终端设备的标签管理方法的信令流程图,如图14所示,本实施例提供的方法包括以下步骤:
步骤S701、移动性管理节点向标签管理设备发送标签查询请求。
该标签查询请求中包括终端设备的标识,以告知标签管理设备需要查询哪个终端设备的标识。
移动性管理节点可以在以下几种情况发生时检查终端设备的类型标签:终端设备注册到网络、终端设备向移动性管理节点请求服务(service request)、终端设备的位置信息指示终端设备位于空中、终端设备从地面小区切换到空中小区、终端设备切换频繁。该过程中移动性管理节点可以通过与接入网节点交互以检测终端设备的类型标签,该移动性管理节点可以为MME或AMF网元,该接入网节点可以为eNB或gNB。
步骤S702、标签管理设备向移动性管理节点发送标签查询响应。
标签查询响应中包括查询结果,查询结果可能指示还没有为终端设备创建类型标签,也可能包括终端设备的类型标签。
步骤S703、当标签查询响应中包括终端设备的类型标签,且类型标签指示类型为无人机类型时,触发对终端设备的位置跟踪和/或无人机事件上报。
图15为本申请实施例八提供的终端设备的标签管理方法的流程图,如图15所示,本实施例提供的方法包括以下步骤:
步骤S801、第一网络设备获取终端设备的类型,终端设备的类型包括无人机、非无人机或未确定类型。
其中,获取终端设备的类型,可以理解为识别终端设备的类型。
步骤S802、第一网络设备向第二网络设备发送报告消息,报告消息用于报告终端设备的类型。
该第一网络设备可以为LTE系统中的基站或者MME,也可以为5G系统中的基站、AMF网元或者NWDAF网元。第一网络设备可以通过如下几种方式获取终端设备的类型:
方式一、第一网络设备根据终端设备的信息获取终端设备的类型。
第一网络设备根据终端设备的信息获取终端设备的类型之前,需要获取终端设备的信息,可选的,终端设备的信息包括以下信息中的一个或者多个:终端设备的能力信息、终端设备的签约信息、终端设备的类型标签信息、终端设备的测量信息、终端设备的位置信息和终端设备接入的小区的类型。
终端设备的能力信息可以携带在RRC连接重配置消息中,或者NAS消息中。终端设备的能力信息用于指示终端设备的类型,终端设备的能力信息可以为空中通信能力指示信息、无人机类型指示信息、飞行能力指示信息和地面普通UE指示信息等。
如果终端设备的能力信息表明终端的类型为非无人机类型,则第一网络设备可以根据终端设备的其他信息识别终端设备的类型。如果终端设备的能力信息表明终端设备的类型为无人机类型,则第一网络设备确定终端设备的类型为无人机类型。
当第一网络设备为LTE系统中的eNB时,eNB从MME接收终端设备的标签信息,标签信息中可以包括终端设备的类型标签,如果标签信息中包括的终端设备的标签类型为无人机类型或者非无人机类型,第一网络设备确定终端设备的类型为无人机类型或者非无人机类型,并且不执行后续的步骤,如果标签信息中包括的终端设备的标签类型为不确定类型,则第一网络设备可以通过终端设备的其他信息对终端设备的类型进行识别。
终端设备的标签信息可以携带在MME发送给eNB的S1 AP Initial Context Setup Request中。或者,eNB在S1 AP Initial Context Setup response中向MME请求终端设备的签约信息,MME在S1-AP UE Context Modification Request中发送给eNB。终端设备的标签信息还可以携带在切换请求响应消息中,或其他MME发给eNB的信令消息中,本实施例不对此进行限制。
当第一网络设备为5G系统中的gNB时,gNB从AMF网元接收终端设备的标签信息,根据终端设备的标签信息获取终端设备的类型,具体的获取方式参照eNB获取终端设备的类型的方式。
AMF网元可以将终端设备的标签信息携带在N2消息中发给gNB,N2消息例如为N2 PDU会话请求或N2会话请求。AMF网元还可以在注册流程、服务请求流程或切换流程等其他流程中将终端设备的标签信息携带在发给gNB的N2消息中。
当第一网络设备为LTE系统中的eNB时,eNB从MME接收终端设备的签约信息,终端设备的签约信息中包括了终端设备是否签约了无人机业务的指示信息,如果该指示信息指示终端设备签约了无人机业务,则eNB确定终端设备的类型为无人机类型,如果该指示信息指示终端设备没有签约无人机业务,则eNB可以通过终端设备的其他信息对终端设备的类型进行识别。
当第一网络设备为5G系统中的gNB时,eNB从AMF网元接收终端设备的签约信息,根据终端设备的签约信息获取终端设备的类型,具体的获取方式参照eNB的方式。
非无人机类型的终端设备由于业务不同,很多情况下位置比较固定或者移动速度较慢,因此,相邻小区的数量较少,且固定,而无人机由于移动速度较快,小区之间切换比较频繁,因此,相邻小区的数目较多。因此,第一网络设备可以基于终端设备的测量信息获取终端设备的类型。
终端设备的测量信息可以包括终端设备的相邻小区的数目和标识等,当终端设备的相邻小区的数目较多,例如,大于预设的数量阈值时,第一网络设备确定终端设备的类型为无人机类型,当终端设备的相邻小区的数目小于该数量阈值时,第一网络设备可以通过终端设备的其他信息对终端设备的类型进行识别。
终端设备的通信特征可以为终端设备的测量特征数据,第一网络设备获取终端设备的测量特征数据,将终端设备的测量特征数据输入预先训练得到的类型模型,得到终端设备的类型。
终端设备的测量信息还可以包括测量特征数据,该测量特征数据包括多径时延、多普勒频移、RSRP的大小或者变化趋势、信号与干扰加噪声比SINR的大小或者变化趋势。
无人机由于采用视距LOS传播,无人机的多径时延扩展相对于其他类型的终端设备较小。因此,第一网络设备根据终端设备的多径时延的大小可以确定终端设备的类型是否为无人机类型。
无人机由于高速移动,使得无人机的多普勒频移比其他类型的终端设备的多普勒频移大。第一网络设备根据终端设备的多普勒频移的大小可以确定终端设备的类型是否为无人机类型。
无人机通常情况在空中飞行,而非无人机类型的终端设备位于地面,因此,可以基于终端设备的位置信息获取终端设备的类型。例如,当终端设备的位置信息表明终端设备位于空中时,第一网络设备确定终端设备的类型为无人机类型,当终端设备的位置信息表明终端设备位于地面时,第一网络设备可以通过终端设备的其他信息对终端设备的类型进行识别。
其中,当第一网络设备为接入网节点时,接入网节点可以在路测的最小化(MDT)报告中获取终端设备的位置信息。
在一些场景中,某些小区只处理特定的业务,只有具有该特定业务的终端设备才会接入该小区,因此,第一网络设备可以根据终端设备接入的小区的类型,获取终端设备的类型。例如,终端设备接入的小区为无人机类型终端服务的小区,则确定终端设备的类型为无人机类型,如果终端设备接入的小区为普通小区,则确定终端设备的类型为非无人机类型,或者通过终端设备的其他信息对终端设备的类型进行识别。
方式二、当第一网络设备为MME或AMF网元时,第一网络设备接收第二网络设备发送的报告消息,该报告消息用于报告终端设备的类型。当第一网络设备为MME时,第二网络设备可以为基站,当第一网络设备为AMF网元时,第二网络设备可以为基站或者NWDAF网元。
可选地,当第一网络设备为基站时,当第一网络设备获取终端设备的类型后,该第一网络设备可以向MME或AMF网元发送该报告消息。当第一网络设备为NWDAF时,当第一网络设备获取终端设备的类型后,该第一网络设备向AMF网元发送该报告消息。
该报告信息用于报告第一网络设备自己识别出终端设备的类型,可选的,该报告消息中包括终端设备的标识和/或终端设备的位置信息。该报告消息可以为UAV report,该报告消息可以采用第一网络设备和第二网络设备之间的现有消息,例如S1 AP UE  context response消息,也可以采用新定义的消息。
其中,第二网络设备可以根据终端设备的能力信息识别终端设备的类型,第二网络设备识别终端设备的类型的具体方法与第一网络设备识别终端设备的类型的方法相同,参照上述第一网络设备识别终端设备的类型的具体方法,这里不再赘述。
为了节约网络资源,提高获取终端设备的类型的准确程度,第一网络设备对终端设备的类型的识别,可以是周期性的,还可以基于事件触发的。其中,对于周期性的识别,周期可以是预配置在第一网络设备的预设时间段,如每天10:00至18:00。对于事件触发的识别,事件可以是终端设备的位置高于预设的高度、终端设备接入的小区类型为空中小区、终端设备上报的小区数目超过预设数值、终端设备切换频繁、或者接受到其他设备的请求消息。
可选的,第一网络设备获取终端设备的类型之前,第一网络设备接收来自第二网络设备的识别指示消息,该识别指示消息用于指示第一网络设备对关联的终端设备的类型进行识别,第一网络设备根据识别指示消息对关联的终端设备的设备类型进行识别,得到关联的终端设备的类型。
该识别指示消息可以为UAV identification request消息。第一网络设备收到该识别指示消息后,识别关联的终端设备(可以理解为所有连接到该第一网络设备的终端设备,如对于接入网节点,可以是所有接入到该接入网节点的终端设备,再如对于移动性管理网元,可以是和该移动性管理网元的有控制面信令连接的终端设备)的类型。
可选的,第一网络设备获取终端设备的类型之前,第一网络设备接收来自第二网络设备的识别指示消息,该识别指示消息中包括终端设备的标识,该识别指示消息用于指示第一网络设备对终端设备的标识对应的终端设备的类型进行识别,第一网络根据所述识别指示消息对该终端设备类型进行识别,并获取终端设备的类型。
可选的,该识别指示消息中包括的终端设备的标识可以为一个或者多个。
第二网络设备可以在以下情况下向第一网络设备发送该识别指示消息:当第二网络设备根据统计信息确定终端设备的位置高于预设的高度、终端设备接入的小区类型为空中小区、终端设备上报的小区数目超过预设数值或终端设备频繁切换等等,则向第一网络设备发送该识别指示消息。
上述例子以第一网络设备根据终端设备的单个信息获取终端设备的类型为例进行说明,可以理解,第一网络设备也可以结合终端设备的能力信息、终端设备的签约信息、终端设备的类型标签信息、终端设备的测量信息、终端设备的位置信息和终端设备接入的小区的类型中的多个信息获取终端设备的类型。
方式三、第一网络设备获取终端设备的测量特征数据,根据类型模型和测量特征数据,确定终端设备的类型。该测量特征数据包括多径时延、多普勒频移、RSRP的大小或者变化趋势、SINR的大小或者变化趋势。
在步骤S802中,可选的,该报告消息中包括终端设备的标识和/或终端设备的位置信息。当第一网络设备为基站时,第二网络设备可以为MME或AMF网元,当第一网络设备为NWDAF网元时,第二网络设备可以为AMF网元。
图16为本申请实施例九提供的网络设备的结构示意图,如图16所示,该网络设 备包括:
获取模块11,用于获取终端设备的类型,所述终端设备的类型包括无人机、非无人机或未确定类型;
发送模块12,用于向标签管理设备发送请求消息,所述请求消息用于请求所述标签管理设备为所述终端设备创建类型标签,所述请求消息中包括所述终端设备的标识。
一种示例性的方式中,所述获取模块11具体用于:
接收第二网络设备发送的报告消息,所述报告消息用于报告所述终端设备的类型。
一种示例性的方式中,所述获取模块11具体用于:
根据所述终端设备的信息获取所述终端设备的类型。
一种示例性的方式中,所述终端设备的信息包括以下信息中的一个或者多个:所述终端设备的能力信息、所述终端设备的签约信息、所述终端设备的类型标签信息、所述终端设备的测量信息、所述终端设备的位置信息和所述终端设备接入的小区的类型。
一种示例性的方式中,所述设备还包括:
接收模块,用于接收来自第二网络设备的识别指示消息,所述识别指示消息用于指示所述第一网络设备对关联的终端设备的类型进行识别;
所述获取模块11具体用于:
根据所述识别指示消息获取所述关联的终端设备的类型。
一种示例性的方式中,所述设备还包括:
接收模块,用于接收来自第二网络设备的识别指示消息,所述识别指示消息中包括所述终端设备的标识,所述识别指示消息用于指示所述第一网络设备对所述终端设备的类型进行识别;
所述获取模块11具体用于:
根据所述识别指示消息获取所述终端设备的类型。
一种示例性的方式中,所述获取模块11具体用于:
获取所述终端设备的测量特征数据;
根据类型模型和所述测量特征数据,确定所述终端设备的类型。
一种示例性的方式中,所述请求消息中还包括所述终端设备的类型信息。
一种示例性的方式中,所述设备还包括:
接收模块,用于接收所述标签管理设备发送的响应消息,所述响应消息中包括标签创建结果。
一种示例性的方式中,所述设备还包括接收模块;
所述发送模块,还用于向所述标签管理设备发送标签查询请求,所述标签查询请求中包括所述终端设备的标识;
所述接收模块,用于接收所述标签管理设备发送的标签查询响应,所述标签查询响应中包括所述终端设备的类型标签。
一种示例性的方式中,所述发送模块还用于:
向UTM发送报告消息,所述报告消息中包括所述终端设备的标识和位置信息。
一种示例性的方式中,所述网络设备为移动管理实体MME、基站、接入与移动性 管理功能AMF网元或网络数据分析功能NWDAF网元。
一种示例性的方式中,所述网络设备移动管理实体MME,所述第二网络设备为基站;或者,
所述网络设备为接入与移动性管理功能AMF网元,所述第二网络设备为NWDAF网元或基站。
本实施例的网络设备,可用于执行上述方法实施例一至实施例七中第一网络设备执行的方法,具体实现方式和技术效果类似,这里不再赘述。
图17为本申请实施例十提供的标签管理设备的结构示意图,如图17所示,该标签管理设备包括:
接收模块21,用于接收第一网络设备发送的请求消息,所述请求消息用于请求所述标签管理设备为所述终端设备创建类型标签,所述请求消息中包括所述终端设备的标识;
创建模块22,用于根据所述请求消息,为所述终端设备创建类型标签,所述终端设备的类型标签包括无人机、非无人机或未确定类型标签。
一种示例性的方式中,所述请求消息中还包括所述终端设备的类型信息。
一种示例性的方式中,所述标签管理设备根据所述请求消息,为所述终端设备创建类型标签之后,还包括:
所述标签管理设备向所述第一网络设备发送响应消息,所述响应消息中包括标签创建结果。
一种示例性的方式中,还包括发送模块23;
所述接收模块21,还用于接收所述第一网络设备发送的标签查询请求,所述标签查询请求中包括所述终端设备的标识;
所述发送模块23,用于向所述第一网络设备发送标签查询响应,所述标签查询响应中包括所述终端设备的类型标签。
一种示例性的方式中,所述第一网络设备为移动管理实体MME、基站、接入与移动性管理功能AMF网元或网络数据分析功能NWDAF网元。
本实施例的标签管理设备,可用于执行上述方法实施例一至实施例七中标签管理设备执行的方法,具体实现方式和技术效果类似,这里不再赘述。
图18为本申请实施例十一提供的网络设备的结构示意图,如图18所示,该网络设备包括:
获取模块31,用于获取终端设备的类型,所述终端设备的类型包括无人机、非无人机或未确定类型;
发送模块32,用于向第二网络设备发送报告消息,所述报告消息用于报告所述终端设备的类型。
一种示例性的方式中,所述获取模块31具体用于:
接收第二网络设备发送的报告消息,所述报告消息用于报告所述终端设备的类型。
又一种示例性的方式中,所述获取模块31具体用于:
根据所述终端设备的信息获取所述终端设备的类型。
一种示例性的方式中,所述终端设备的信息包括以下信息中的一个或者多个:所述终端设备的能力信息、所述终端设备的签约信息、所述终端设备的类型标签信息、所述终端设备的测量信息、所述终端设备的位置信息和所述终端设备接入的小区的类型。
一种示例性的方式中,所述设备还包括:
接收模块,用于接收来自第二网络设备的识别指示消息,所述识别指示消息用于指示所述第一网络设备对关联的终端设备的类型进行识别;
所述获取模块31具体用于:
根据所述识别指示消息获取所述关联的终端设备的类型。
又一种示例性的方式中,所述设备还包括:
接收模块,用于接收来自第二网络设备的识别指示消息,所述识别指示消息中包括所述终端设备的标识,所述识别指示消息用于指示所述第一网络设备对所述终端设备的类型进行识别;
所述获取模块31具体用于:
所述第一网络根据所述识别指示消息获取所述终端设备的类型。
一种示例性的方式中,当所述第一网络设备为基站时,所述第二网络设备为移动管理实体MME或移动性管理功能AMF网元;或者,
当所述第一网络设备为网络数据分析功能NWDAF网元时,所述第二网络设备为AMF网元。
本实施例的网络设备,可用于执行实施例八所述的方法,具体实现方式和技术效果类似,这里不再赘述。
图19为本申请实施例十二提供的网络设备的结构示意图,如图19所示,该网络设备包括:处理器41、存储器42和收发器43,所述存储器42用于存储指令,所述收发器43用于和其他设备通信,所述处理器41用于执行所述存储器42中存储的指令,以使所述网络设备41执行如上述实施例一至实施例八中第一网络设备或第二网络设备执行的方法。
图20为本申请实施例十三提供的标签管理设备的结构示意图,如图20所示,该标签管理设备包括:处理器51、存储器52和收发器53,所述存储器52用于存储指令,所述收发器53用于和其他设备通信,所述处理器51用于执行所述存储器52中存储的指令,以使所述网络设备51执行如上述实施例一至实施例八中标签管理设备执行的方法。
可以理解,本申请实施例中网络设备或者标签管理设备中使用的处理器可以是中央处理器(CPU),通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC),现场可编程门阵列(FPGA)或者其他可编程逻辑器件、晶体管逻辑器件,硬件部件或者其任意组合。其可以实现或执行结合本申请公开内容所描述的各种示例性的逻辑方框,模块和电路。所述处理器也可以是实现计算功能的组合,例如包含一个或多个微处理器组合,DSP和微处理器的组合等等。
本申请实施例所述的总线可以是工业标准体系结构(Industry Standard Architecture,ISA)总线、外部设备互连(Peripheral Component,PCI)总线或扩展工业标准体系结构(Extended Industry Standard Architecture,EISA)总线等。总线可以分为地址总线、数据总线、控制总线等。为便于表示,本申请附图中的总线并不限定仅有一根总线或一种类型的总线。
在本申请所提供的几个实施例中,应该理解到,所揭露的装置和方法,可以通过其它的方式实现。例如,以上所描述的装置实施例仅仅是示意性的,例如,所述单元的划分,仅仅为一种逻辑功能划分,实际实现时可以有另外的划分方式,例如多个单元或组件可以结合或者可以集成到另一个系统,或一些特征可以忽略,或不执行。另一点,所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口,装置或单元的间接耦合或通信连接,可以是电性,机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的,作为单元显示的部件可以是或者也可以不是物理单元,即可以位于一个地方,或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外,在本申请各个实施例中的各功能单元可以集成在一个处理单元中,也可以是各个单元单独物理存在,也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现,也可以采用硬件加软件功能单元的形式实现。
上述以软件功能单元的形式实现的集成的单元,可以存储在一个计算机可读取存储介质中。上述软件功能单元存储在一个存储介质中,包括若干指令用以使得一台计算机设备(可以是个人计算机,服务器,或者网络设备等)或处理器(processor)执行本申请各个实施例所述方法的部分步骤。而前述的存储介质包括:U盘、移动硬盘、只读存储器(Read-Only Memory,ROM)、随机存取存储器(Random Access Memory,RAM)、磁碟或者光盘等各种可以存储程序代码的介质。

Claims (28)

  1. 一种终端设备的标签管理方法,其特征在于,包括:
    第一网络设备获取终端设备的类型,所述终端设备的类型包括无人机、非无人机或未确定类型;
    所述第一网络设备向标签管理设备发送请求消息,所述请求消息用于请求所述标签管理设备为所述终端设备创建类型标签,所述请求消息中包括所述终端设备的标识。
  2. 根据权利要求1所述的方法,其特征在于,所述第一网络设备获取终端设备的类型,包括:
    所述第一网络设备接收第二网络设备发送的报告消息,所述报告消息用于报告所述终端设备的类型。
  3. 根据权利要求1所述的方法,其特征在于,所述第一网络设备获取终端设备的类型,包括:
    所述第一网络设备根据所述终端设备的信息获取所述终端设备的类型。
  4. 根据权利要求3所述的方法,其特征在于,所述终端设备的信息包括以下信息中的一个或者多个:所述终端设备的能力信息、所述终端设备的签约信息、所述终端设备的类型标签信息、所述终端设备的测量信息、所述终端设备的位置信息和所述终端设备接入的小区的类型。
  5. 根据权利要求1-4任一项所述的方法,其特征在于,所述第一网络设备获取所述终端设备的类型之前还包括:
    所述第一网络设备接收来自第二网络设备的识别指示消息,所述识别指示消息用于指示所述第一网络设备对关联的终端设备的类型进行识别;
    所述第一网络设备获取所述终端设备的类型,包括:
    所述第一网络设备根据所述识别指示消息获取所述关联的终端设备的类型。
  6. 根据权利要求1-4任一项所述的方法,其特征在于,所述第一网络设备获取所述终端设备的类型之前还包括:
    所述第一网络设备接收来自第二网络设备的识别指示消息,所述识别指示消息中包括所述终端设备的标识,所述识别指示消息用于指示所述第一网络设备对所述终端设备的类型进行识别;
    所述第一网络设备获取所述终端设备的类型,包括:
    所述第一网络根据所述识别指示消息获取所述终端设备的类型。
  7. 根据权利要求1所述的方法,其特征在于,所述第一网络设备获取终端设备的类型,包括:
    所述第一网络设备获取所述终端设备的测量特征数据;
    所述第一网络设备根据类型模型和所述测量特征数据,确定所述终端设备的类型。
  8. 根据权利要求1-7任一项所述的方法,其特征在于,所述请求消息中还包括所述终端设备的类型信息。
  9. 根据权利要求1-7任一项所述的方法,其特征在于,所述第一网络设备向标签管理设备发送请求消息之后,还包括:
    所述第一网络设备接收所述标签管理设备发送的响应消息,所述响应消息中包括 标签创建结果。
  10. 根据权利要求1-9任一项所述的方法,其特征在于,还包括:
    所述第一网络设备向所述标签管理设备发送标签查询请求,所述标签查询请求中包括所述终端设备的标识;
    所述第一网络设备接收所述标签管理设备发送的标签查询响应,所述标签查询响应中包括所述终端设备的类型标签。
  11. 根据权利要求1-10任一项所述的方法,其特征在于,还包括:
    所述第一网络设备向UTM发送报告消息,所述报告消息中包括所述终端设备的标识和位置信息。
  12. 根据权利要求1-11任一项所述的方法,其特征在于,所述第一网络设备为移动管理实体MME、基站、接入与移动性管理功能AMF网元或网络数据分析功能NWDAF网元。
  13. 根据权利要求2所述的方法,其特征在于,所述第一网络设备移动管理实体MME,所述第二网络设备为基站;或者,
    所述第一网络设备为接入与移动性管理功能AMF网元,所述第二网络设备为NWDAF网元或基站。
  14. 一种网络设备,其特征在于,包括:
    获取模块,用于获取终端设备的类型,所述终端设备的类型包括无人机、非无人机或未确定类型;
    发送模块,用于向标签管理设备发送请求消息,所述请求消息用于请求所述标签管理设备为所述终端设备创建类型标签,所述请求消息中包括所述终端设备的标识。
  15. 根据权利要求14所述的设备,其特征在于,所述获取模块具体用于:
    接收第二网络设备发送的报告消息,所述报告消息用于报告所述终端设备的类型。
  16. 根据权利要求14所述的设备,其特征在于,所述获取模块具体用于:
    根据所述终端设备的信息获取所述终端设备的类型。
  17. 根据权利要求16所述的设备,其特征在于,所述终端设备的信息包括以下信息中的一个或者多个:所述终端设备的能力信息、所述终端设备的签约信息、所述终端设备的类型标签信息、所述终端设备的测量信息、所述终端设备的位置信息和所述终端设备接入的小区的类型。
  18. 根据权利要求14-17任一项所述的设备,其特征在于,还包括:
    接收模块,用于接收来自第二网络设备的识别指示消息,所述识别指示消息用于指示所述第一网络设备对关联的终端设备的类型进行识别;
    所述获取模块具体用于:
    根据所述识别指示消息获取所述关联的终端设备的类型。
  19. 根据权利要求14-17任一项所述的设备,其特征在于,还包括:
    接收模块,用于接收来自第二网络设备的识别指示消息,所述识别指示消息中包括所述终端设备的标识,所述识别指示消息用于指示所述第一网络设备对所述终端设备的类型进行识别;
    所述获取模块具体用于:
    根据所述识别指示消息获取所述终端设备的类型。
  20. 根据权利要求14所述的设备,其特征在于,所述获取模块具体用于:
    获取所述终端设备的测量特征数据;
    根据类型模型和所述测量特征数据,确定所述终端设备的类型。
  21. 根据权利要求14-20任一项所述的设备,其特征在于,所述请求消息中还包括所述终端设备的类型信息。
  22. 根据权利要求14-20任一项所述的设备,其特征在于,还包括:
    接收模块,用于接收所述标签管理设备发送的响应消息,所述响应消息中包括标签创建结果。
  23. 根据权利要求14-22任一项所述的设备,其特征在于,还包括:
    所述发送模块,还用于向所述标签管理设备发送标签查询请求,所述标签查询请求中包括所述终端设备的标识;
    接收模块,用于接收所述标签管理设备发送的标签查询响应,所述标签查询响应中包括所述终端设备的类型标签。
  24. 根据权利要求14-23任一项所述的设备,其特征在于,所述发送模块还用于:
    向UTM发送报告消息,所述报告消息中包括所述终端设备的标识和位置信息。
  25. 根据权利要求14-24任一项所述的设备,其特征在于,所述网络设备为移动管理实体MME、基站、接入与移动性管理功能AMF网元或网络数据分析功能NWDAF网元。
  26. 根据权利要求15所述的设备,其特征在于,所述网络设备移动管理实体MME,所述第二网络设备为基站;或者,
    所述网络设备为接入与移动性管理功能AMF网元,所述第二网络设备为NWDAF网元或基站。
  27. 一种网络设备,其特征在于,包括处理器、存储器和收发器,所述存储器用于存储指令,所述收发器用于和其他设备通信,所述处理器用于执行所述存储器中存储的指令,以使所述网络设备执行如权利要求1-13任一项所述的方法。
  28. 一种计算机可读存储介质,其特征在于,所述计算机可读存储介质存储有指令,当所述指令被执行时,使得计算机执行如权利要求1-13任一项所述的方法。
PCT/CN2020/071790 2019-01-18 2020-01-13 终端设备的标签管理方法和装置 WO2020147681A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
EP20741824.5A EP3910973A4 (en) 2019-01-18 2020-01-13 LABEL MANAGEMENT METHOD AND FACILITIES FOR TERMINAL DEVICE
AU2020208514A AU2020208514A1 (en) 2019-01-18 2020-01-13 Label management method and apparatus for terminal device
US17/378,169 US20210344410A1 (en) 2019-01-18 2021-07-16 Label management method and apparatus for terminal device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910108917.6A CN111464995A (zh) 2019-01-18 2019-01-18 终端设备的标签管理方法和装置
CN201910108917.6 2019-01-18

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/378,169 Continuation US20210344410A1 (en) 2019-01-18 2021-07-16 Label management method and apparatus for terminal device

Publications (1)

Publication Number Publication Date
WO2020147681A1 true WO2020147681A1 (zh) 2020-07-23

Family

ID=71614392

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/071790 WO2020147681A1 (zh) 2019-01-18 2020-01-13 终端设备的标签管理方法和装置

Country Status (5)

Country Link
US (1) US20210344410A1 (zh)
EP (1) EP3910973A4 (zh)
CN (1) CN111464995A (zh)
AU (1) AU2020208514A1 (zh)
WO (1) WO2020147681A1 (zh)

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111770490B (zh) * 2019-04-02 2022-08-05 大唐移动通信设备有限公司 一种确定终端行为分析的方法和设备
US11924662B2 (en) * 2020-11-13 2024-03-05 At&T Intellectual Property I, L.P. Remote user plane deployment and configuration
CN113872802B (zh) * 2021-09-17 2024-01-19 支付宝(杭州)信息技术有限公司 检测网元的方法和装置
CN116528216A (zh) * 2022-01-20 2023-08-01 华为技术有限公司 一种通信方法、装置和系统
CN117376893A (zh) * 2022-06-30 2024-01-09 华为技术有限公司 一种终端的接入方法及装置
CN117768974A (zh) * 2022-09-26 2024-03-26 华为技术有限公司 管理标签状态的方法和通信装置
WO2024065698A1 (zh) * 2022-09-30 2024-04-04 Oppo广东移动通信有限公司 通信方法、装置、设备、存储介质、芯片、产品及程序
CN116611664B (zh) * 2023-06-13 2024-02-13 杭州派迩信息技术有限公司 一种地服标签管理系统及其装置、方法

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101115228A (zh) * 2007-08-26 2008-01-30 上海华为技术有限公司 短消息处理方法及其系统
CN104113880A (zh) * 2014-06-06 2014-10-22 深圳市深信服电子科技有限公司 数据流控制方法和系统
US20180019801A1 (en) * 2016-07-14 2018-01-18 At&T Intellectual Property I, L.P. Method and System to Dynamically Identify and Control a UAV With Emitting Instruments
CN108700894A (zh) * 2018-05-22 2018-10-23 北京小米移动软件有限公司 无人机控制方法、装置、基站和无人机
CN108810941A (zh) * 2017-05-05 2018-11-13 华为技术有限公司 一种网络接入方法、网络设备及终端

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9776716B2 (en) * 2012-12-19 2017-10-03 Elwah LLC Unoccupied flying vehicle (UFV) inter-vehicle communication for hazard handling
US10229329B2 (en) * 2016-11-08 2019-03-12 Dedrone Holdings, Inc. Systems, methods, apparatuses, and devices for identifying, tracking, and managing unmanned aerial vehicles
US9766621B2 (en) * 2016-01-12 2017-09-19 The Boeing Company Aircraft information retrieval using onboard RFID tags
CN105528595A (zh) * 2016-02-01 2016-04-27 成都通甲优博科技有限责任公司 在无人机航拍图像中对输电线路绝缘子的识别定位方法
JP7088953B2 (ja) * 2017-03-21 2022-06-21 エスゼット ディージェイアイ テクノロジー カンパニー リミテッド 無人航空機(uav)を監視する方法、システム、プログラム、及び記録媒体
CN107273944A (zh) * 2017-05-16 2017-10-20 北京元视觉科技有限公司 自主社交的智能设备、自主交互方法及存储介质
WO2019028902A1 (en) * 2017-08-11 2019-02-14 Lenovo (Beijing) Limited IDENTIFICATION OF AERIAL VEHICLES

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101115228A (zh) * 2007-08-26 2008-01-30 上海华为技术有限公司 短消息处理方法及其系统
CN104113880A (zh) * 2014-06-06 2014-10-22 深圳市深信服电子科技有限公司 数据流控制方法和系统
US20180019801A1 (en) * 2016-07-14 2018-01-18 At&T Intellectual Property I, L.P. Method and System to Dynamically Identify and Control a UAV With Emitting Instruments
CN108810941A (zh) * 2017-05-05 2018-11-13 华为技术有限公司 一种网络接入方法、网络设备及终端
CN108700894A (zh) * 2018-05-22 2018-10-23 北京小米移动软件有限公司 无人机控制方法、装置、基站和无人机

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
ANONYMOUS: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Remote Identification of Unmanned Aerial Systems; Stage 1 (Release 16)", 3GPP STANDARD; TECHNICAL REPORT; 3GPP TR 22.825, no. V1.0.0, 30 September 2018 (2018-09-30), pages 1 - 22, XP051475199 *
HUAWEI; ORANGE; CHINA UNICOM: "ID_UAS - Use case of UAV type identification", 3GPP DRAFT; S1-182732, 24 August 2018 (2018-08-24), West Palm Beach, pages 1 - 2, XP051535136 *
See also references of EP3910973A4

Also Published As

Publication number Publication date
AU2020208514A1 (en) 2021-08-19
EP3910973A4 (en) 2022-03-16
CN111464995A (zh) 2020-07-28
US20210344410A1 (en) 2021-11-04
EP3910973A1 (en) 2021-11-17

Similar Documents

Publication Publication Date Title
WO2020147681A1 (zh) 终端设备的标签管理方法和装置
EP3843333B1 (en) Communication method and apparatus
KR102323696B1 (ko) 서비스 가입 방법 및 장치
EP3952599A1 (en) Method for establishing communication bearer, device and system
US20230328520A1 (en) Aerial Service
US11570739B2 (en) Uplink data indication
US20220150784A1 (en) Handover method and apparatus
WO2020119653A1 (zh) 识别终端的方法、装置
US20210092673A1 (en) Application specific location discovery
WO2020063655A1 (zh) 飞行器的控制方法及装置
EP4192094A1 (en) Service traffic shunting method and apparatus
US20240073848A1 (en) Network Slice in a Wireless Network
AU2020246484B2 (en) Terminal management and control method, apparatus, and system
WO2020119795A1 (zh) 一种通信方法及装置
US20230115431A1 (en) Communication method and device in wireless communication system supporting unmanned aerial system service
KR102244539B1 (ko) 라디오 유닛 단위 기반의 단말 위치정보 획득 방법 및 그 장치
WO2023083153A1 (zh) 获取安全分级结果的方法及通信装置
WO2023035872A1 (zh) 确定用户面路径的方法及通信装置
US20240031929A1 (en) Connection Establishment
US20230422293A1 (en) Network Slice Based Priority Access
US20230337089A1 (en) Aerial Service
EP4207850A1 (en) Data analysis method and apparatus
WO2022077184A1 (zh) 请求prs配置的方法、装置、通信设备及存储介质
US20240179647A1 (en) Timing Service Type for Timing Resiliency Service
WO2023165425A1 (zh) 一种通信方法、装置及设备

Legal Events

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

Ref document number: 20741824

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2020208514

Country of ref document: AU

Date of ref document: 20200113

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2020741824

Country of ref document: EP

Effective date: 20210809