WO2020143569A1 - 无线网络通信方法、网络设备和终端 - Google Patents

无线网络通信方法、网络设备和终端 Download PDF

Info

Publication number
WO2020143569A1
WO2020143569A1 PCT/CN2020/070443 CN2020070443W WO2020143569A1 WO 2020143569 A1 WO2020143569 A1 WO 2020143569A1 CN 2020070443 W CN2020070443 W CN 2020070443W WO 2020143569 A1 WO2020143569 A1 WO 2020143569A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal
drone
authorization
request
control
Prior art date
Application number
PCT/CN2020/070443
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 EP20738073.4A priority Critical patent/EP3902304A4/en
Publication of WO2020143569A1 publication Critical patent/WO2020143569A1/zh
Priority to US17/372,958 priority patent/US20210345117A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/50—Secure pairing of devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/14—Relay systems
    • H04B7/15—Active relay systems
    • H04B7/185—Space-based or airborne stations; Stations for satellite systems
    • H04B7/18502—Airborne stations
    • H04B7/18506—Communications with or from aircraft, i.e. aeronautical mobile service
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/06—Authentication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/60—Context-dependent security
    • H04W12/63—Location-dependent; Proximity-dependent
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/12—Setup of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/22—Manipulation of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/04—Large scale networks; Deep hierarchical networks
    • H04W84/06—Airborne or Satellite Networks

Definitions

  • Embodiments of the present application relate to the field of communications, and more specifically, to a wireless network communication method, network device, and terminal.
  • Unmanned aerial system is composed of unmanned aerial controller and unmanned aerial vehicle (UAV).
  • UAS unmanned aerial vehicle
  • the current application areas of drones are mostly short-distance scenarios.
  • the drones controller and drones can be paired and connected through wireless fidelity (WIFI) technology or Bluetooth low energy (BLE) technology.
  • WIFI wireless fidelity
  • BLE Bluetooth low energy
  • connection method cannot meet the communication requirements of the UAV system at long distances, especially in non-line-of-sight scenarios.
  • the embodiments of the present application provide a wireless network communication method, network equipment and terminal, which can solve the problem of network authorization and matching of the drone controller and the drone, and are beneficial to realize the long distance between the drone controller and the drone Communication.
  • a wireless communication method including: a drone traffic management entity receives an authorization request; the drone traffic management entity sends an authorization response; wherein, the authorization request is used to request an authorized terminal to control the drone Control, the authorization response is used to indicate whether the terminal is allowed to control the drone; or, the authorization request is used to request the authorization terminal to match the drone controller, and the authorization response is used to Indicate whether to allow the terminal to match with the drone controller.
  • Using the UAV traffic management entity in the mobile communication network to authorize or match the UAV controller with the UAV is conducive to achieving long-distance communication between the UAV controller and the UAV.
  • receiving the authorization request by the drone traffic management entity includes: the drone traffic management entity receives the authorization request from the terminal; the unmanned The sending of an authorization response by the aircraft traffic management entity includes: the drone traffic management entity sending the authorization response to the terminal.
  • the authorization or matching problem of the drone controller and the drone is solved, which is beneficial to realize the long-distance communication between the drone controller and the drone.
  • Direct interaction with drone traffic management entities can increase efficiency.
  • the receiving of an authorization request by the drone traffic management entity includes: the drone traffic management entity receiving the authorization request from the access and mobility management function network element AMF Authorization request; sending an authorization response by the drone traffic management entity includes: the drone traffic management entity sending the authorization response to the AMF.
  • the authorization request is carried in a non-access stratum message.
  • receiving the authorization request by the drone traffic management entity includes: the drone traffic management entity receives the authorization request from the session management function network element SMF;
  • the sending of an authorization response by the drone traffic management entity includes: the drone traffic management entity sending the authorization response to the SMF.
  • the process of requesting network authorization and matching between the UAV controller and the UAV can be completed in other existing processes, which solves the authorization or matching problem of the UAV system more conveniently.
  • the authorization request is carried in a protocol data unit PDU session establishment message
  • the authorization response is carried in a PDU session establishment acceptance message.
  • the authorization request is carried in a protocol data unit PDU session modification message
  • the authorization response is carried in a PDU session modification acceptance message.
  • the authorization request is carried in a service request message
  • the authorization response is carried in a service acceptance message
  • the method further includes: the drone traffic management entity according to the information in the authorization request, the contract information of the terminal, and the drone traffic management entity's One or more of the local configuration information generates the authorization response.
  • the authorization request includes information about the drone controlled by the terminal request; or, the authorization request includes information about the drone controller matched by the terminal request information.
  • the authorization request includes an identifier of the drone that the terminal requests to control; or, the authorization request includes the matching UAV controller of the terminal request Logo.
  • the authorization response includes information of a drone that is allowed to be controlled by the terminal; or, the authorization response includes information of a drone controller that allows the terminal to be matched information.
  • the authorization response includes an identification of a drone that is allowed to be controlled by the terminal; or, the authorization response includes a UAV controller that allows the terminal to be matched Logo.
  • the authorization response includes an identification of an unmanned aerial system composed of an unmanned aerial vehicle and an unmanned aerial vehicle controller.
  • a wireless network communication method including: a terminal sending an authorization request to a drone traffic management entity; the terminal receiving an authorization response from the drone traffic management entity; wherein the authorization request is used to Requesting authorization of the terminal to control the drone, the authorization response is used to indicate whether the terminal is allowed to control the drone; or, the authorization request is used to request authorization of the terminal and the drone
  • the controller performs matching, and the authorization response is used to indicate whether the terminal is allowed to match with the drone controller.
  • the authorization or matching problem of the drone controller and the drone is solved, which is beneficial to realize the long-distance communication between the drone controller and the drone.
  • Direct interaction with drone traffic management entities can increase efficiency.
  • the authorization request includes information about the drone controlled by the terminal request; or, the authorization request includes information about the drone controller matched by the terminal request information.
  • the authorization request includes an identifier of the drone that the terminal requests to control; or, the authorization request includes the matching UAV controller of the terminal request Logo.
  • the authorization response includes information of a drone that is allowed to be controlled by the terminal; or, the authorization response includes information of a drone controller that allows the terminal to be matched information.
  • the authorization response includes an identification of a drone that is allowed to be controlled by the terminal; or, the authorization response includes a UAV controller that allows the terminal to be matched Logo.
  • the authorization response includes an identification of a drone system composed of a drone and a drone controller that are allowed to match.
  • a wireless network communication method which includes: during registration of a terminal, the terminal sends instruction information to an access and mobility management function network element AMF; the terminal receives a registration response from the AMF; Wherein, the instruction information is used to instruct the terminal to request control of the drone, and the registration response is used to indicate whether the terminal is allowed to control the drone; or, the instruction information is used to indicate The terminal request matches with the drone controller, and the registration response is used to indicate whether the terminal is allowed to match with the drone controller.
  • the method further includes: the terminal sends to the AMF information about the drone that the terminal requests to control; or, the terminal sends the terminal to the AMF Request information about the matching drone controller.
  • the method further includes: the terminal sending the identity of the drone that the terminal requests to control to the AMF; or, the terminal sending the terminal to the AMF Request the matching UAV controller ID.
  • the registration response is used to refuse the terminal to register.
  • the registration response is used to indicate that the terminal is successfully registered, and indicates that the terminal is not allowed Control the drone.
  • the registration response is used to indicate that the terminal is successfully registered, and indicates that the terminal is allowed to control no Man-machine, and/or indicate whether the terminal is allowed to control the drone.
  • the indication information is also used to indicate whether the terminal is only used to control the drone, and when the indication information indicates that the terminal is only used to control the drone , And when the AMF determines that the terminal is not allowed to control the drone, the registration response is used to refuse the terminal to register; or, when the instruction information indicates that the terminal is not only used to control the drone, And when the AMF determines that the terminal is not allowed to control the drone, the registration response is used to indicate that the terminal is successfully registered, and indicates that the terminal is not allowed to control the drone.
  • the terminal can also have other functions in addition to the function of the drone controller.
  • the technical solution of the present application solves the problem of no one by indicating whether the terminal is only used to control the drone during the registration process when the terminal requests network authorization
  • the issue of the authorization of the aircraft controller also solves the registration problem of different types of UAV controllers.
  • the registration response includes information about a drone that is allowed to be controlled by the terminal; or, the registration response includes information about a drone controller that allows the terminal to be matched information.
  • the registration response includes an identification of a drone that is allowed to be controlled by the terminal; or, the registration response includes a UAV controller that allows the terminal to be matched Logo.
  • the registration response further includes an identification of a drone system that is configured to allow matching of the drone and the drone controller.
  • a wireless network communication method including: a core network element sends an authorization request to a drone traffic management entity; the core network element receives an authorization response from the drone traffic management entity; wherein, The authorization request is used to request an authorized terminal to control the drone, and the authorization response is used to indicate whether the terminal is allowed to control the drone; or, the authorization request is used to request an authorized terminal and no The man-machine controller performs matching, and the authorization response is used to indicate whether to allow the terminal to perform matching with the drone controller.
  • the method further includes: receiving instruction information sent by the terminal; wherein, the instruction The information is used to instruct the terminal to request control of the drone; or, the instruction information is used to instruct the terminal to match the drone controller.
  • the method further includes: the core network element generates a registration response according to the authorization response, wherein when the authorization response indicates that the terminal is allowed to control the drone, all The registration response is used to indicate that the terminal is successfully registered, and indicates that the terminal is allowed to control the drone, and/or indicates whether the terminal is allowed to control the drone.
  • the registration response is used to refuse the terminal to register.
  • the registration response is used to indicate that the terminal is successfully registered, and indicates that the terminal is not allowed The terminal controls the drone.
  • the indication information is also used to indicate whether the terminal is only used to control the drone, and when the indication information indicates that the terminal is only used to control the drone And the authorization response indicates that the terminal is not allowed to control the drone, the registration response is used to refuse the terminal to register; or when the instruction information indicates that the terminal is not only used to control the drone, And when the authorization response indicates that the terminal is not allowed to control the drone, the registration response is used to indicate that the terminal is successfully registered and indicates that the terminal is not allowed to control the drone.
  • the registration authorization and matching process of the drone controller or drone is completed, and the problem of the drone system accessing the network is solved.
  • the problem of registration authorization for different types of drone controllers on the network side is solved.
  • the core network element is an access and mobility management function network element AMF or a session management function network element SMF.
  • the method further includes: the core network element receives from the terminal information of the drone that the terminal requests to control; or, the core network element The terminal receives the information of the unmanned aerial controller matched by the terminal request.
  • the method further includes: the core network element receives the identifier of the drone that the terminal requests to control from the terminal; or, the core network element The terminal receives the identifier of the drone controller matched by the terminal request.
  • the authorization request includes information about the drone controlled by the terminal request; or, the authorization request includes information about the drone controller matched by the terminal request information.
  • the authorization request includes an identifier of the drone that the terminal requests to control; or, the authorization request includes the matching UAV controller of the terminal request Logo.
  • the authorization response includes information of a drone that is allowed to be controlled by the terminal; or, the authorization response includes information of a drone controller that allows the terminal to be matched information.
  • the authorization response includes an identification of a drone that is allowed to be controlled by the terminal; or, the authorization response includes a UAV controller that allows the terminal to be matched Logo.
  • the authorization response further includes an identification of an unmanned aerial system constituted by a matching unmanned aerial vehicle and unmanned aerial vehicle controller.
  • a wireless network communication method including: a terminal sending an authorization request to a drone traffic management entity; the drone traffic management entity sending an authorization response to a terminal; wherein the authorization request is used to request authorization The terminal controls the drone, and the authorization response is used to indicate whether the terminal is allowed to control the drone; or the authorization request is used to request authorization for the terminal to perform control with the drone controller Matching, the authorization response is used to indicate whether the terminal is allowed to match with the drone controller.
  • the authorization request includes an identifier of the drone controlled by the terminal request; or the authorization request includes an identifier of the drone controller matched by the terminal request .
  • the authorization response includes an identification of a drone that is allowed to be controlled by the terminal; or, the authorization response includes a UAV controller that allows the terminal to be matched Logo.
  • the authorization request includes information of the terminal.
  • the authorization response includes an identification of an unmanned aerial system composed of an unmanned aerial vehicle and an unmanned aerial vehicle controller.
  • the method further includes: the drone traffic management entity sends a message requesting to obtain the contract information of the terminal to a unified data management function network element; the unified data management function The network element sends the contract information of the terminal to the drone traffic management entity.
  • a wireless network communication method including: a core network element sends an authorization request to a drone traffic management entity; the drone flow management entity sends an authorization response to the core network element; wherein, The authorization request is used to request an authorized terminal to control the drone, and the authorization response is used to indicate whether the terminal is allowed to control the drone; or, the authorization request is used to request an authorized terminal and no The man-machine controller performs matching, and the authorization response is used to indicate whether to allow the terminal to perform matching with the drone controller.
  • the authorization request includes an identifier of the drone controlled by the terminal request; or the authorization request includes an identifier of the drone controller matched by the terminal request .
  • the authorization response includes an identification of a drone that is allowed to be controlled by the terminal; or, the authorization response includes a UAV controller that allows the terminal to be matched Logo.
  • the authorization request includes information of the terminal.
  • the authorization response includes an identification of a drone system composed of a drone and a drone controller that are allowed to match.
  • the core network element is an access and mobility management function element AMF or a session management function element SMF.
  • the method further includes: the drone traffic management entity sends a message to the unified data management function network element requesting to obtain contract information of the terminal; the unified data management function The network element sends the contract information of the terminal to the drone traffic management entity.
  • a wireless network communication method including: a terminal sends first information to a core network element; a core network element sends second information to the terminal; wherein the first information is used to request an authorized terminal pair UAV control, the second information is used to indicate whether the terminal is allowed to control the UAV; or, the first information is used to request the authorized terminal to match the UAV controller, so The second information is used to indicate whether to allow the terminal to match the drone controller.
  • the first information includes an identifier of a drone requested by the terminal to control; or the first information includes a drone controller matched by the terminal request Logo.
  • the second information includes an identification of a drone that is allowed to be controlled by the terminal; or, the second information includes a drone control that allows the terminal to be matched The identifier of the device.
  • the core network element is an access and mobility management function network element AMF or a session management function network element SMF.
  • the first information is a registration request
  • the second information is a registration response
  • the method further includes: the core network element sends an authorization request to the drone traffic management entity; the drone flow management entity sends an authorization response to the core network element ; Wherein, the authorization request is used to request an authorized terminal to control the drone, and the authorization response is used to indicate whether the terminal is allowed to control the drone; or, the authorization request is used to request authorization The terminal matches with the drone controller, and the authorization response is used to indicate whether the terminal is allowed to match with the drone controller.
  • the authorization request includes an identifier of the drone controlled by the terminal request; or the authorization request includes an identifier of the drone controller matched by the terminal request .
  • the authorization response includes an identification of a drone that is allowed to be controlled by the terminal; or, the authorization response includes a UAV controller that allows the terminal to be matched Logo.
  • the method further includes: the drone traffic management entity sends a message to the unified data management function network element requesting to obtain contract information of the terminal; the unified data management function The network element sends the contract information of the terminal to the drone traffic management entity.
  • An eighth aspect provides a wireless communication method, including: a first core network element sends third information to a second core network element; the second core network element sends fourth information to the first core network element Wherein the third information is used to request an authorized terminal to control the drone, and the fourth information is used to indicate whether the terminal is allowed to control the drone; or, the third information is used Requesting authorization to match the terminal with the drone controller, the fourth information is used to indicate whether the terminal is allowed to match with the drone controller.
  • the third information includes an identifier of the drone requested by the terminal to control; or the third information includes a drone controller matched by the terminal request Logo.
  • the fourth information includes an identification of a drone that is allowed to be controlled by the terminal; or, the fourth information includes a drone control that allows the terminal to be matched The identifier of the device.
  • the method further includes: the second core network element sends fifth information to a third core network element; the third core network element sends the second information to the second The core network element sends sixth information; wherein, the fifth information is used to request an authorized terminal to control the drone, and the sixth information is used to indicate whether the terminal is allowed to control the drone; or, The fifth information is used to request an authorized terminal to match with the drone controller, and the sixth information is used to indicate whether to allow the terminal to match with the drone controller.
  • the fifth information includes an identifier of the drone requested by the terminal to control; or the fifth information includes a drone controller matched by the terminal request Logo.
  • the sixth information includes an identifier of a drone that is allowed to be controlled by the terminal; or, the sixth information includes a drone control that allows the terminal to be matched The identifier of the device.
  • a network device including a module for performing the above method or step or operation or function performed by a drone traffic management entity.
  • a terminal including a module for performing the above method, step, operation or function performed by the terminal.
  • a network device which executes the above method or step or operation or function module performed by a core network element.
  • a communication device includes: at least one processor and a communication interface.
  • the communication interface is used for information interaction between the communication device and other communication devices.
  • the communication device realizes the functions of the above drone flow management entity.
  • a communication device includes: at least one processor and a communication interface.
  • the communication interface is used for information exchange between the communication device and other communication devices.
  • the communication device realizes the functions of the above terminal.
  • a communication device includes: at least one processor and a communication interface.
  • the communication interface is used for information interaction between the communication device and other communication devices.
  • the communication device realizes the functions of the above core network element.
  • a computer program storage medium having program instructions, when the program instructions are directly or indirectly executed, so that the functions of the above drone flow management entity can be realized.
  • a computer program storage medium having program instructions, when the program instructions are directly or indirectly executed, so that the functions of the above terminal can be realized.
  • a computer program storage medium has program instructions.
  • the program instructions are executed directly or indirectly, the functions of the core network element in the foregoing are realized.
  • a chip system includes at least one processor, and when the program instructions are executed in the at least one processor, the functions of the drone flow management entity described above are realized.
  • a chip system in a nineteenth aspect, includes at least one processor, and when program instructions are executed in the at least one processor, the functions of the above terminal are realized.
  • a chip system includes at least one processor, and when program instructions are executed in the at least one processor, the above-mentioned functions of the core network element are realized.
  • a computer program product which includes program instructions.
  • program instructions When the program instructions are directly or indirectly executed, the functions of the above drone flow management entity are realized.
  • a computer program product which includes program instructions, and when the program instructions are directly or indirectly executed, the functions of the above terminal can be realized.
  • a computer program product which includes program instructions.
  • program instructions When the program instructions are executed directly or indirectly, the functions of the core network element in the above are realized.
  • a communication system including the terminal and the drone traffic management entity above.
  • the terminal is used to send an authorization request to the drone traffic management entity;
  • the drone flow management entity is used to send an authorization response to the terminal; wherein, the authorization request is used to request the terminal to authorize Control, the authorization response is used to indicate whether the terminal is allowed to control the drone; or the authorization request is used to request authorization to match the terminal with the drone controller, and the authorization response is used to Indicate whether to allow the terminal to match with the drone controller.
  • the communication system may further include a unified data management function network element.
  • a communication system including the core network element and the drone traffic management entity.
  • the core network element is used to send an authorization request to the drone traffic management entity;
  • the drone flow management entity is used to send an authorization response to the core network element; wherein the authorization request is used to request the authorization terminal to UAV control, the authorization response is used to indicate whether the terminal is allowed to control the UAV; or, the authorization request is used to request the authorization terminal to match the UAV controller, the authorization The response is used to indicate whether to allow the terminal to match the drone controller.
  • the system also includes a unified data management function network element.
  • a communication system including the above terminal and core network element.
  • the terminal is used to send the first information to the core network element; the core network element is used to send the second information to the terminal; wherein the first information is used to request an authorized terminal to control the drone, the second The information is used to indicate whether the terminal is allowed to control the drone; or, the first information is used to request an authorized terminal to match the drone controller, and the second information is used to indicate whether the terminal is allowed to be controlled.
  • the terminal matches the UAV controller.
  • the communication system may further include the above-mentioned drone flow management entity.
  • the communication system may further include the above unified data management function network element.
  • a communication system including the first core network element and the second core network element above.
  • the first core network element is used to send third information to the second core network element;
  • the second core network element is used to send fourth information to the first core network element; wherein the third information is used to Requesting an authorized terminal to control the drone, the fourth information is used to indicate whether the terminal is allowed to control the drone; or, the third information is used to request the authorized terminal and the drone controller For matching, the fourth information is used to indicate whether to allow the terminal to match with the drone controller.
  • the communication system may further include the above-mentioned third core network element.
  • FIG. 1 is a schematic diagram of a network system architecture according to an embodiment of the present application.
  • FIG. 2 is a schematic diagram of an application scenario of an embodiment of the present application.
  • FIG. 3 is a schematic flowchart of a wireless network communication method according to an embodiment of the present application.
  • FIG. 4 is a schematic flowchart of a wireless network communication method according to another embodiment of the present application.
  • FIG. 5 is a schematic flowchart of a wireless network communication method according to another embodiment of the present application.
  • FIG. 6 is a schematic structural diagram of a network device according to an embodiment of the present application.
  • FIG. 7 is a schematic structural diagram of a communication device according to an embodiment of the present application.
  • FIG. 8 is a schematic structural diagram of a terminal provided by another embodiment of the present application.
  • FIG. 9 is a schematic structural diagram of a communication device according to another embodiment of the present application.
  • FIG. 10 is a schematic structural diagram of a terminal according to still another embodiment of the present application.
  • FIG. 11 is a schematic structural diagram of a communication device according to another embodiment of the present application.
  • FIG. 12 is a schematic structural diagram of a network device provided by another embodiment of the present application.
  • FIG. 13 is a schematic structural diagram of a communication device according to another embodiment of the present application.
  • the communication scenarios between drone controllers and drones have also changed.
  • short-distance control for example, in the short-distance scenarios currently used by civil drones, the drone controller and the drone can be paired and connected through short-range wireless technologies such as WIFI or Bluetooth to achieve Two-way communication between UAV controller and UAV.
  • short-range wireless technology has been unable to meet the communication needs of UAV controllers and UAVs in long-range, especially non-line-of-sight scenarios.
  • the 3rd Generation Partnership Project (3GPP) network has ubiquitous coverage, high reliability and quality of service (QoS) performance, robust security protection, and seamless mobility Sex.
  • the unmanned aerial system will be paired and connected through the access network or the core network to achieve long-distance communication.
  • FIG. 1 shows a schematic diagram of a network architecture according to an embodiment of the present application.
  • the network architecture may specifically include the following network elements:
  • UE User equipment
  • AN access network
  • UPF user plane function
  • AMF access and mobility management function
  • SMF session management function
  • PCF policy control function
  • UDM unified data management
  • data network data, network, DN
  • the UE 101 may also be called a terminal.
  • the terminal may communicate with one or more core networks (CN) via the AN device 102.
  • a terminal may be called an access terminal, terminal, subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, wireless network device, user agent, or user device.
  • Terminals can be cellular phones, cordless phones, session initiation protocol (SIP) phones, smart phones, smart local loop (wireless local loop, WLL) stations, personal digital processing (personal digital) assistant, PDA), handheld device with wireless communication function, computing device or other device connected to a wireless modem, in-vehicle device, wearable device, drone device or Internet of Things, terminal in the Internet of Vehicles, and future network such as fifth Any form of terminal in a fifth generation (5G) network, a relay user equipment, or a terminal in a public land mobile communication network (PLMN) that will evolve in the future, where the relay user equipment is, for example, It may be a 5G residential gateway (RG).
  • 5G fifth generation
  • PLMN public land mobile communication network
  • PLMN public land mobile communication network
  • This embodiment of the present application is not limited thereto.
  • the devices mentioned above are collectively referred to as terminals.
  • the AN device 102 may also be referred to as an access device, and the access device refers to a device that can access the core network, for example, a radio access network (radio access network (RAN) device).
  • the RAN device may also be referred to as a network device, which is an access device that a terminal accesses to a mobile communication system in a wireless manner.
  • An example of a RAN device is a base station (BS), which may also be referred to as a base station device.
  • the wireless access network equipment may be a transmission and reception point (TRP) in a new radio technology (NR) system, a next generation node (base station, gNB) in the 5G system, a long-term Base station in evolved node B (evolved node B, eNB), global mobile communication (GSM) or code division multiple access (CDMA) in long term evolution (LTE)
  • Transceiver station base transceiver station, BTS
  • RNC radio network controller
  • node B node B
  • base station controller base station controller
  • BBU home base station
  • AP small base station equipment
  • pico future
  • this article does not limit the specific types of network devices.
  • the names of devices with network device functions may be different.
  • the above-mentioned apparatuses that provide wireless communication functions for terminals are collectively referred to as access network equipment.
  • Different access network devices may be located in the same cell or in different cells, which is not specifically limited herein.
  • the UPF network element 103 has functions such as packet forwarding, encapsulation, and statistics of the terminal, and is responsible for user data forwarding.
  • the interface between the AN device 102 and the UPF network element 103 may be an N3 interface.
  • the UPF network elements are specifically divided into intermediate-UPF (intermediate-UPF, I-UPF) and anchor UPF (anchor-UPF, A-UPF), where I-UPF is connected to the access network RAN, A- UPF is a UFP for session anchor, and A-UPF may also be called PDU session anchor UPF (PDU session anchor UPF, PSA), which is not limited in the embodiment of the present application.
  • I-UPF intermediate-UPF
  • anchor UPF anchor-UPF
  • PSA PDU session anchor UPF
  • the AMF network element 104 is responsible for terminal access and mobility management, and has functions such as user authentication, handover, and location update.
  • the interface between UE 101 and AMF network element 104 may be an N1 interface
  • the interface between AN device 102 and AMF network element 104 may be an N2 interface.
  • the SMF network element 105 is responsible for the selection and reselection of the UPF network element 103, the allocation of Internet protocol (IP) addresses, etc., and can also be responsible for the establishment, modification, and release of sessions.
  • the interface between can be N4 interface.
  • SMF network elements can be specifically divided into two types: intermediate SMF (intermediate-SMF, I-SMF) network elements and anchor SMF (anchor-SMF, A-SMF) network elements, where I-SMF network elements A user plane function (UPF) network element (ie I-UPF) that controls and accesses the network interface, and an A-SMF network element controls the session anchor UPF network element (ie A-UPF).
  • intermediate SMF intermediate-SMF
  • I-SMF anchor-SMF
  • A-SMF anchor-SMF
  • I-SMF A user plane function
  • I-UPF user plane function
  • A-SMF network element controls the session anchor UPF network element (ie A-UPF).
  • the PCF network element 106 is used to implement a unified policy framework that includes management of network behavior, to provide the control plane with policy rules to be executed, and to obtain subscription information related to policy decisions. It includes both mobility-related strategies and protocol data units ( protocol, data, unit (PDU) session related strategies, such as quality of service (QoS) strategy, charging strategy, etc.
  • protocol data units protocol, data, unit (PDU) session related strategies, such as quality of service (QoS) strategy, charging strategy, etc.
  • QoS quality of service
  • UDM network element 107 is used to store user's subscription data.
  • the DN108 refers to an operator network that provides data transmission services for UEs.
  • the DN may be a network that provides IP multimedia services (IP multi-media, IMS), Internet services, and other services, and the interface between the UPF network element 103 and the DN 108 may be an N6 interface.
  • FIG. 1 only the terminal is used as an example for the UE.
  • the interface names between the network elements in FIG. 1 are only an example.
  • the interface names of the system architecture may also be Other names are not specifically limited in this embodiment of the present application.
  • a communication system to which the communication method of the embodiments of the present application can be applied may include more or fewer network elements or devices.
  • the device or network element in FIG. 1 may be hardware, software divided by functions, or a combination of the two.
  • the devices or network elements in FIG. 1 can communicate through other devices or network elements.
  • the drone system is composed of a drone controller and a drone. Due to the special nature of drones that need to occupy airspace, regulatory authorities need to identify and control them in a timely manner.
  • the 3GPP network introduces a new entity, the unmanned aerial traffic management entity (UTM).
  • UTM can store UAV controller and UAV related data, such as identification information, owner information, path information, current location, operating status, etc.
  • UTM can be used for pairing UAV controller and UAV, identifying no
  • the man-machine system is authorized to operate the drone system, and can also manage and intervene in the communication between the drone controller and the drone.
  • FIG. 2 shows a schematic diagram of an application scenario of an embodiment of the present application.
  • the UAS 200 can carry out information exchange and wireless communication with the network system with UTM203, which is a UAV traffic management entity.
  • the drone controller 201 or the drone 202 can interact with the access network (radio access network, RAN) 204, core network (CN) 205, and can also access the access network 204 or core network 205 interacts with UTM203;
  • UAV controller 201 can also interact with drone 202 through access network 204 or core network 205, and can also interact with drone 202 through UTM203.
  • drone controller 201 and the drone 202 may be in the same access network or core network, or may be in different access networks or core networks, which is not limited in the embodiments of the present application.
  • Unmanned aerial vehicle UAV202 also known as unmanned aircraft and aerial robots, is an unmanned aircraft that uses radio remote control equipment and self-provided program control devices. It can complete air missions and various tasks under unmanned conditions. Load tasks.
  • the unmanned aerial vehicle in the embodiments of the present application may be an unmanned helicopter, a fixed-wing aircraft, a multi-rotor aircraft, an unmanned airship, an unmanned umbrella-wing aircraft; it may also include an adjacent space vehicle, such as a stratospheric airship, high-altitude balloon, solar Man-machine, etc.; can also be four-axis, six-axis, single-axis, vector control and other forms of UAV.
  • the drones in the embodiments of the present application can be used in military, industrial, civil, agricultural, construction, film and television, environmental protection and other fields and special industries that use drones for operations, such as military reconnaissance, patrol, Aerial photography, environmental monitoring, border monitoring, delivery and courier, power inspection, power confirmation, flood prevention and drought relief, disaster relief, etc.
  • This embodiment of the present application is not limited thereto.
  • drones are examples of devices with drone functions.
  • the names of devices with drone functions may be different in order to be applied to different scenarios or complete different air flight missions.
  • the above-mentioned devices capable of unmanned aircraft functions are collectively referred to as drones.
  • UAV 202 can be equipped with a variety of sensors or functional modules, such as gyroscope (flight attitude perception), accelerometer, geomagnetic induction, barometric pressure sensor (rough hover height control), ultrasonic sensor (precise control at low altitude or obstacle avoidance) , Optical flow sensor (precise determination of hovering horizontal position), GPS module (rough positioning of horizontal position and height), control circuit, compass, etc., by collecting the angular rate, attitude, position, acceleration, altitude and airspeed of the UAV, It can automatically maintain the normal flying attitude of the UAV.
  • sensors or functional modules such as gyroscope (flight attitude perception), accelerometer, geomagnetic induction, barometric pressure sensor (rough hover height control), ultrasonic sensor (precise control at low altitude or obstacle avoidance) , Optical flow sensor (precise determination of hovering horizontal position), GPS module (rough positioning of horizontal position and height), control circuit, compass, etc., by collecting the angular
  • each function module may also have other names, which is not limited in this embodiment of the present application.
  • the drone in the embodiment of the present application may also have more or less functional modules, and may also realize more or less functions, etc.
  • the embodiment of the present application does not make any limitation on this.
  • the UAV controller (UAV controller 201) is used to control the UAV 202, for example, to control the flight status or flight actions of the UAV.
  • UAV controllers can be smart phones, tablets, laptops, smart watches or smart remote controls, traditional remote controls, dedicated remote controllers, etc., and can also be bracelets, rings, gloves, armbands, watches, etc. can be used for gestures
  • the device for controlling the drone can also be a headgear or other head-mounted device that can be used to control the drone, or a smart jacket, coat, etc. that can be used for the user's body movement to control the drone.
  • UAV controller is not limited in this article.
  • the names and forms of devices with UAV controller functions may be different.
  • the above-mentioned devices capable of having the function of a drone controller or capable of controlling a drone are collectively called a drone controller.
  • the drone controller 201 can control the flight status of the drone 202.
  • the drone controller can control the direction, aileron, lift, tilt, speed, throttle, flaps, etc. of the drone.
  • the actions of the UAV such as turning, climbing, diving, rolling, hovering, taking off, and landing are not limited in this embodiment of the present application.
  • the drone system 200 may include one or more drone controllers 201 and one or more drone 202.
  • one drone controller can control one or more drones, one drone can also be controlled by one or more drone controllers, and multiple drone controllers can also control multiple Man-machine, this embodiment of the present application does not limit this.
  • the drone 202 in the drone system 200 may be any one or more types mentioned above, and the drone controller 201 may also be any one or more types mentioned above, this application The embodiment does not make any limitation on this.
  • the UAV system 200 can achieve long-distance communication by accessing a 3GPP network.
  • the problem of how the network authorizes and matches the UAV and the UAV controller has not yet been solved. The following describes the embodiments of the present application in detail with reference to FIG. 3.
  • FIG. 3 shows a schematic flowchart of a wireless network communication method according to an embodiment of the present application. As shown in FIG. 3, the method may include steps S310 to S320.
  • step S310 the core network element sends an authorization request to the drone traffic management entity UTM.
  • step S320 the drone traffic management entity sends an authorization response to the core network element.
  • the terminal may be a drone controller, such as UE 101 shown in FIG. 1 or UAV controller 201 shown in FIG. 2.
  • the terminal may be used to control the drone only, or not only to control the drone.
  • the terminal may have other functions besides controlling the drone.
  • the smartphone when a smartphone can control a drone, the smartphone is a drone controller.
  • the smartphone In addition to the drone controller function, the smartphone also has other functions such as communication, photographing, and entertainment.
  • the terminal When the terminal is a drone controller, it can have the function of a drone controller and can control the drone.
  • the authorization request may be understood as an authorization request corresponding to the UAV controller.
  • the authorization request is used to request authorization of the terminal to control the UAV, or may be understood as a terminal requesting authorization to use the UAV controller function.
  • the authorization response can be understood as the authorization response corresponding to the drone controller.
  • the authorization response is used to indicate whether the drone controller is allowed to control the drone.
  • the authorization response can also indicate whether the terminal is allowed to use the drone controller.
  • the process of the UAV controller sending an authorization request can also be understood as the process of requesting to match the drone, that is, the drone controller requests to match the drone .
  • the drone controller may match the drone during the request to control the drone.
  • the drone controller may also request matching with the drone first, and request control of the drone at other moments.
  • the process of the UAV controller requesting to match the UAV and the process of the UAV controller requesting to control the UAV can be performed separately or simultaneously.
  • the process of requesting the control of the drone by the drone controller in this application when it is performed simultaneously may also include the request of the drone controller to match with the drone.
  • the authorization request corresponding to the drone controller may also include information about the drone that the drone controller requests to control, for example, the identity or list of the drone that the drone controller requests to control.
  • the UAV logo may be a unique logo in the 3GPP system, or a unique logo in the drone industry, or any other logo that can be used to uniquely determine the drone, which is not limited in the embodiments of the present application .
  • the authorization request includes information about the drone that the drone controller requests to control, and it can be understood that the drone controller requests to control the specified drone.
  • the authorization request corresponding to the drone controller may also include information about the drone controller, such as the unique identifier of the drone controller, the UE capabilities of the drone controller, the location, and the owner identification, Owner address, owner contact information, owner qualification certificate, identifier of the drone operator operating the drone controller, license and qualification certificate of the drone operator and other related to the drone controller Data, etc.
  • the authorization request may include some or all of the above information, or other unexhausted data related to the UAV controller, etc., which is not limited in this application.
  • the authorization response corresponding to the drone controller may include the information of the drone that is allowed to be controlled by the drone controller, for example, the UAV ID or ID list that the UTM allows the drone controller to control can be understood as UTM allows the drone controller to control the designated drone.
  • the authorization response corresponding to the drone controller may include information about the drone that is controlled by the drone controller, for example, UTM rejects the drone ID or the ID list controlled by the drone controller.
  • the authorization response corresponding to the drone controller may also include information about the drone that is allowed to be controlled by the drone controller and information about the drone that is controlled by the drone controller, such as no Human-machine logo, or may include one of them.
  • the request-controlled UAV identification or identification list included in the authorization request and the UAV controller-controlled UAV identification or identification list included in the authorization response may be the same or different. Both the authorization request and the authorization response may include the above-mentioned corresponding UAV identification or identification list, or not all or none.
  • the authorization request may include a drone identifier or list of identifiers requested by the drone controller, and the authorization response may include confirmation information to confirm that the drone controller is allowed to control the drone it requests to control. .
  • the authorization request may include a drone identification or identification list that the drone controller requests to control
  • the authorization response may include a drone identification or identification list that allows the drone controller to control, or from In the list of UAV IDs requested for control, select the UAV IDs that the UAV controller can control.
  • the UAV identifier or the identifier list allowed to be controlled by the UAV controller may be determined by the network according to the terminal's subscription information or local configuration information.
  • the authorization request may not include the information of the drone that the drone controller requests to control, and the authorization response may include the identification or list of identification of the drone determined by the system to allow the control of the drone controller. Or the default or pre-configured UAV ID or ID list that can be controlled by the UAV controller in the contract information or local configuration information.
  • the authorization response corresponding to the drone controller may also include the identifier of the UAS composed of the drone controller and the drone that is allowed to be controlled by the drone controller.
  • the identifier may be used for multiple Broadcast and other scenes.
  • the terminal may also be a drone, such as UE 101 shown in FIG. 1 or drone 202 shown in FIG. 2.
  • the terminal When the terminal is a drone, it can have a drone function and can be matched with the drone control. It can be understood as the authorization request corresponding to the drone.
  • the authorization request is used to authorize the terminal to match the drone controller. It can be understood that the terminal requests authorization to use the drone function; the authorization response can be understood as the drone correspondence.
  • the authorization response is used to indicate whether the drone is allowed to match the drone control.
  • the authorization response can also indicate that the terminal is allowed to have the drone function.
  • the authorization request corresponding to the drone may also include information about the drone controller that the drone expects to match, such as an identifier or a list of identifiers of the drone controller that controls the drone.
  • the identifier of the drone controller may be a unique identifier in the 3GPP system, may be a unique identifier in the drone industry, or may be any other identifier used to uniquely determine the drone controller. No limitation.
  • the authorization request includes the information of the drone controller matched by the drone request, and it can be understood that the drone request matches the specified drone controller.
  • the authorization request corresponding to the drone may also include information about the drone, such as a unique identifier, the UE capabilities of the drone, specifications and model, serial number, takeoff quality, location, owner identification, owner address , Owner contact information, owner qualification certificate, take-off location and time, mission type, route data, operating status and other data related to the drone, etc., the authorization request may include some or all of the above information, or other
  • the exhaustive UAV related data is not limited in this application.
  • the authorization response corresponding to the drone may include information of a drone controller that allows the drone to match, for example, a UAV controller ID or a list of IDs that the UTM allows the drone to match, can be understood as UTM allows the drone to be matched with a designated drone controller.
  • the UAV controller identification or identification list included in the authorization request and required for matching may be the same or different from the UAV controller identification or identification list included in the authorization response that allows the UAV to perform matching.
  • Both the authorization request and the authorization response may include the corresponding corresponding UAV controller ID or ID list, or may not include both or neither.
  • the authorization request may include a matching UAV controller ID or ID list of the UAV request
  • the authorization response may include confirmation information to confirm that the UAV is allowed to perform with the UAV controller that it expects to match. match.
  • the authorization request may include the UAV controller identification or identification list matched by the drone request
  • the authorization response may include the UAV controller identification or identification list allowed to match the drone, or from Select the matching UAV controller ID from the list of matching UAV controller IDs.
  • the drone identification or identification list that allows the drone to be matched may be determined by the network according to the contract information or local configuration information of the terminal.
  • the authorization request may not include the information of the drone controller matched by the drone request, and the authorization response may include the identifier or list of identifiers of the drone controller determined by the system to allow the drone to match. Or the default, pre-configured UAV controller ID or ID list that can be matched with the UAV in the contract information or local configuration information.
  • the authorization response corresponding to the drone may also include information about the drone controller that allows the drone to match and information about the drone controller that refuses to match the drone, for example, no one.
  • the identification of the machine controller may also include information about the drone controller that allows the drone to match and information about the drone controller that refuses to match the drone, for example, no one. The identification of the machine controller.
  • drone request matching the drone controller can be understood that the drone can be controlled by the drone controller.
  • the authorization response corresponding to the drone may also include an identifier of the UAS composed of the drone and a drone controller that allows the drone to be matched, and the identifier may be used in scenarios such as multicast.
  • the core network element may be a network element located in the core network 204 shown in FIG. 2, such as an access and mobility management function network element, a session management function network element, etc., as shown in FIG. AMF network element 104 and SMF network element 105 shown.
  • the core network element may also be other network elements that can interact with UTM.
  • the UTM traffic management entity UTM receives the authorization request process through different processes. For example, it may be an authorization request process initiated by the terminal after the terminal completes registration, or it may request authorization from the network during the terminal registration process. Regarding an example of requesting authorization in the terminal registration process, the following will be described in conjunction with specific embodiments, which will not be detailed here.
  • the UTM traffic management entity UTM can receive authorization requests in multiple ways.
  • the terminal may be a drone or a drone controller.
  • the terminal uses the terminal to describe the two types of terminals: a drone or a drone controller.
  • the terminal may send the authorization request to the core network element, and the core network element forwards the authorization request to the drone traffic management entity.
  • the terminal may send an indication message to the core network element.
  • the indication information may instruct the terminal to request control of the drone or the terminal request to match the drone controller.
  • the core network element according to the indication information
  • the authorization request sent to the UTM can be generated by itself.
  • the authorization request can be understood as an authorization request corresponding to the terminal.
  • the authorization request is used to request authorization to use the drone controller function or the drone function by the terminal.
  • the authorization request may include one or more of the information that may be included in the authorization request mentioned above.
  • the authorization request corresponding to the terminal may be carried in a service request message, a protocol data unit (protocol data unit (PDU) session establishment message, a PDU session modification message, or a non-access-stratum (NAS) message Can also be carried in newly added signaling or other messages.
  • PDU protocol data unit
  • NAS non-access-stratum
  • the authorization response corresponding to the terminal may be carried in the service acceptance message, the PDU session establishment acceptance message, the PDU session modification acceptance message, or newly added signaling or other messages.
  • the terminal may send the authorization request to the SMF, and the SMF may forward the authorization request or the information in the authorization request to the UTM, or the SMF may also send The information in the authorization request is parsed, and a new message is generated by itself and sent to UTM. The new message is used to request authorization from UTM.
  • the terminal may send the indication information or authorization request to the AMF, and the AMF forwards the authorization request or the information in the authorization request to the UTM, or the AMF generates according to the analysis of the authorization request A new message is sent to UTM, and the new message is used to request authorization from the UTM to the terminal, for example, to request authorization of the terminal to use the drone function or use the drone controller function.
  • the terminal may request authorization from the UTM through different core network elements, or may send the authorization request in different processes.
  • the UAV system interacts with the network through the core network elements to solve the network authorization and matching problems of the UAV system, and further enables the UAV controller and UAV to communicate through the network to achieve long-distance communication.
  • UTM may not receive the authorization request corresponding to the terminal from the core network element, but may directly receive the authorization request sent by the terminal, that is, the terminal may directly initiate the authorization request process separately.
  • the terminal may directly initiate the authorization request process separately.
  • FIG. 4 shows a schematic flowchart of a wireless network communication method according to an embodiment of the present application.
  • the method may include steps S410 to S430.
  • step S410 the terminal sends an authorization request to the drone traffic management entity.
  • the terminal transparently transmits the authorization request to UTM.
  • the terminal may be a drone controller or a drone
  • the authorization request may include one or more of the information that may be included in the authorization request mentioned above.
  • the authorization request please refer to the authorization The description of the request is concise and will not be repeated here.
  • step S420 the drone traffic management entity requests the unified data management UDM for contract information about the terminal to obtain data for authorization.
  • UTM can obtain data for authorization in multiple ways.
  • UTM can generate authorization responses in multiple ways.
  • UTM may generate an authorization response based on the information in the authorization request, such as a list of unmanned aircraft identifiers requested by the terminal for control or a list of matched UAV controller identifiers requested by the terminal, or related information of the terminal.
  • UTM may generate an authorization response according to the contract information of the terminal. For example, if there is no information about the UAV controller (or UAV) function in the contract information, the terminal will refuse to use the UAV controller (or UAV) function in the authorization response; if there is no one in the contract information Information related to the function of the aircraft controller (or drone), UTM can determine the information of the drone that is allowed to be controlled by the drone controller (or the information of the drone controller that allows the drone to match), etc., and contains In the authorization response.
  • UTM can generate an authorization response based on local configuration information.
  • the UTM may generate an authorization response according to one or more of the information in the authorization request, the contract information of the terminal, or the local configuration information of the UTM.
  • step S430 the drone traffic management entity sends an authorization response to the terminal.
  • the authorization request sent by the terminal to the UTM and the authorization request sent by the terminal to the UTM may be carried in existing message signaling, or may be carried in a newly added message or signaling, the existing or newly added message signaling It may be sent directly by the terminal to UTM.
  • step S420 may also be applied to the wireless communication method shown in FIG. 3, which may be performed after step S320.
  • the authorization response may include one or more of the above-mentioned information that the authorization response may include.
  • the authorization response may include one or more of the above-mentioned information that the authorization response may include.
  • the direct interaction between the terminal and UTM solves the problem of the drone controller obtaining authorization to control the drone or the problem of matching the drone and the drone controller, so that the drone can be controlled
  • the drone and drone can communicate through the network, which is beneficial to realize the long-distance control of the drone by the drone controller.
  • the terminal may also request authorization from the network during the registration process, which will be described below in conjunction with the embodiment of FIG. 5.
  • FIG. 5 shows a schematic flowchart of a wireless network communication method according to an embodiment of the present application.
  • the method may include steps S510 to S550.
  • the core network element may be an AMF network element.
  • step S510 the terminal sends a registration request to the AMF network element.
  • the registration request may include function indication information.
  • the instruction information can instruct the terminal to request to control the drone or to use the drone controller function; when the terminal can have a drone function, the instruction information can indicate the The terminal request has the UAV function or the terminal request is matched with the UAV controller.
  • the function indication information can be carried in the NAS message, parallel to the registration request.
  • the registration request may be carried in a NAS message, and the NAS message further includes an authorization request of the terminal, and the authorization request is parallel to the registration request.
  • the registration request and the authorization request may be carried in the NAS message, and the authorization request may further include function indication information.
  • the terminal may also send information requesting authorization by the terminal or related information of the terminal to the AMF network element.
  • the terminal may also send the AMF network element an identifier or list of identifiers of the drone that the terminal requests to control, or others may be used to determine or uniquely identify the drone Information; when the terminal requests authorization to use the drone function, the terminal can also send to the AMF network element the identification or identification list of the drone controller that the terminal expects to match, or other information that can be used to determine or uniquely identify the drone control Information.
  • the terminal may also send the drone controller information or related data to the AMF network element, where the related data may be the drone mentioned above Part or all of the controller information, or other unlisted information related to the drone controller; when the terminal requests authorization to use the drone function, the terminal can also send the drone information or AMF network element Relevant data.
  • the relevant data here may be part or all of the drone information mentioned above, or other unlisted information related to the drone.
  • the information that the terminal requests authorization or related information of the terminal may be carried in one or more of a registration request, an authorization request, a NAS message, or other messages.
  • step S520 the AMF network element sends an authorization request to UTM.
  • the form and content of the authorization request can have many possible ways. As an example rather than a limitation, the following lists several possible implementation ways.
  • the authorization request may be an authorization request sent by the terminal to the AMF.
  • AMF forwards the authorization request sent by the terminal to UTM.
  • the authorization request may be generated by the AMF, and the authorization request may include information sent by the terminal to the AMF.
  • the AMF parses the information for authorization sent by the terminal and generates an authorization request containing the above information.
  • the authorization request may be generated by AMF, and the information used in the authorization request to request authorization may be generated by AMF.
  • the AMF may generate other information for requesting authorization by itself.
  • the information and the instruction information may have different forms, but the content may be information for requesting network authorization.
  • step S530 after receiving the authorization request, UTM requests subscription information about the terminal from the UDM to obtain data for authorization.
  • obtaining relevant data for authorization may be obtained through local configuration information of UTM.
  • step S540 UTM sends an authorization response to AMF.
  • the authorization response is used to indicate whether the terminal is allowed to control the drone or to authorize the terminal to use the drone controller function; or the terminal requests authorization to use the unmanned controller function Machine function, the authorization response is used to indicate whether to allow the terminal to match with the drone controller, or to authorize the terminal to use the drone function.
  • the authorization response uses a terminal as a drone controller as an example.
  • UTM may generate the authorization response according to the information in the authorization request sent by AMF.
  • the authorization request includes the instruction information of the terminal requesting to control the drone, and the UTM may refuse the terminal to control the drone in the authorization response, or allow or confirm that the terminal can control the drone.
  • the authorization request includes the drone information that the terminal requests to control, such as a drone ID or a list of identifiers, etc.
  • UTM can reject the terminal to control the drone in the authorization response based on the information of the drone, or It is allowed to confirm that the terminal controls the drone, or include the relevant information of the drone allowed to be controlled by the terminal in the authorization response, for example, the identity or list of the drone allowed to be controlled by the terminal.
  • the identification or identification list of the drone may be a part or all of the selected drone information controlled by the terminal included in the authorization request.
  • UTM may generate the authorization response according to the contract information or local configuration information.
  • the authorization request may include the instruction information of the terminal requesting to control the drone, and UTM may determine the relevant information of the drone that is allowed to be controlled by the terminal according to the contract information or local configuration information, such as the identity of the drone that is allowed to be controlled by the terminal or ID list, etc., or if there is no information related to the UAV controller of the terminal in the subscription information or local configuration information, UTM can refuse the terminal to use the UAV controller function in the authorization response.
  • the contract information or local configuration information such as the identity of the drone that is allowed to be controlled by the terminal or ID list, etc.
  • UTM may generate the authorization response based on a variety of information in the authorization request, contract information, or local configuration information.
  • the authorization request may include the drone information that the terminal requests to control, such as the drone identification or identification list, etc.
  • UTM may determine whether to allow the terminal to control the unmanned person it requests to control based on the information and the contract information of the terminal Or determine which drones can be controlled by the terminal among the drones it requests to control; or re-determine the drones that are allowed to be controlled by the terminal for the terminal.
  • an identifier can also be assigned to the terminal and the drone system that the terminal can control the drone, and include it in the authorization response in.
  • the identifier can be used in a multicast scenario.
  • the network can simultaneously notify multiple unmanned aerial vehicles or unmanned aerial vehicle systems to which the unmanned aerial vehicle controller belongs.
  • the above example is only described by taking the terminal as a drone controller as an example.
  • the terminal is a drone
  • the above exemplary method is also applicable, and for simplicity, it will not be repeated here.
  • the UTM may also save the information of the terminal.
  • the authorization request sent by AMF to UTM includes the relevant data of the terminal
  • UTM can save the relevant data of the terminal, such as saving the identifier, location, and ownership of the drone controller or drone Address and contact information, etc., the relevant data of the terminal can be referred to above.
  • step S550 the AMF sends a registration response to the terminal.
  • the AMF determines whether to allow the terminal to register with the network, such as a 3GPP network.
  • the registration in the embodiments of the present application is not limited to the successful registration of the terminal to the network, but also includes the authorization of the terminal to obtain UTM, which may also be understood as the registration of the terminal to UTM.
  • the registration response may indicate that the terminal registration is rejected, or may indicate that the terminal registration is successful.
  • the terminal there are many ways for the terminal to generate a registration response. As an example rather than a limitation, the following gives an example.
  • the AMF may include information that the terminal's registration is rejected in the registration response.
  • the AMF may generate the registration response according to the information in the authorization response or local configuration information.
  • the AMF can respond to the terminal registration success in the registration response.
  • the registration response may also include the information included in the authorization response, such as the information of the drone that is allowed to be controlled by the terminal or the identification of the drone system.
  • AMF can choose to respond to the successful registration of the terminal in the registration response according to the local configuration information, and indicate that the terminal does not allow the use of the drone control function Or UAV function; or AMF can directly refuse the terminal registration in the authorization response.
  • the AMF may also generate a registration response according to the information in the registration request, the information in the authorization request, or the local configuration information.
  • the following uses the terminal as the UAV controller for example.
  • AMF can respond to the terminal registration success in the registration response; AMF can also receive the authorization response Information is sent to the terminal.
  • AMF can respond to the terminal registration success in the registration response according to the local configuration information and indicate that the terminal is not allowed Control the drone; or AMF directly refuses the terminal registration in the registration response.
  • the AMF may reject the terminal registration in the registration response.
  • the registration request indicates that the terminal is only used to control the drone, and the authorization response allows the terminal to control the drone.
  • AMF can respond to the successful registration of the terminal in the registration response; AMF can also receive the information in the received authorization response Send to the terminal.
  • the AMF responds to the successful registration of the terminal in the registration response, and instructs the terminal not to control the drone.
  • AMF responds to the terminal registration success in the registration response; AMF can also receive the information in the received authorization response Send to the terminal.
  • indication information can be used to indicate whether the terminal is only used to control the drone, for example, using bit 1 (or 0) to indicate that the terminal is only used to control the drone, or to indicate by other means, this application
  • bit 1 or 0
  • the embodiment does not make any limitation.
  • the AMF may indicate in the registration response whether the terminal is allowed to control the drone that it requests to control.
  • the AMF may include the authorization response in the registration response and send it to the terminal, or send the authorization response to the terminal separately.
  • the AMF sending the registration response to the terminal may include the above two or other form.
  • the terminal requests authorization from the network during the registration process, which solves the problem of how the terminal interacts with the network to obtain authorization to control the drone and the problem of matching the drone controller with the drone, which is beneficial to realize the drone controller and unmanned Long-distance communication.
  • the UAV controller provides indication information in the registration process whether it is only used to control the drone.
  • the core network element can determine whether to allow the UAV controller to register according to the instruction information and the authorization response, which solves the network How to deal with the registration problem of different types of UAV controllers.
  • the core network element may also be other network elements or devices.
  • the terminal may send the first information to the core network element; the terminal receives the second information sent by the core network element, where the first information is used to request authorization for the terminal to control the drone, and the second information is used to Indicates whether the terminal is allowed to control the drone; or the first information is used to request authorization to match the terminal with the drone controller, and the second information is used to indicate whether the terminal is allowed to match with the drone controller.
  • the core network element can interact with other core network elements or with UTM.
  • the information in the second information may be received by the core network element from other core network elements or UTM and forwarded to the terminal, or may be generated by the core network element.
  • the network device 600 of FIG. 6 may be the drone traffic management entity mentioned above, such as the UTM203 shown in FIG. 2.
  • the network device 600 may be used to implement the above steps performed by the drone traffic management entity, such as the steps performed by the drone traffic management entity in the methods shown in FIGS. 3 to 5.
  • the network device 600 includes a receiving module 610 and a sending module 620.
  • the receiving module 610 is used to receive an authorization request
  • the sending module 620 is used to send an authorization response
  • the terminal has the function of a drone controller, the authorization request is used to request the authorized terminal to control the drone, and the authorization response is used to indicate whether the terminal is allowed to control the drone; or, the terminal has no one
  • the authorization request is used to request the authorization terminal to match the drone controller, and the authorization response is used to indicate whether the terminal is allowed to match the drone controller.
  • the receiving module 610 is used to receive the authorization request from the terminal.
  • the sending module 620 is used to send the authorization response to the terminal.
  • the receiving module 610 is configured to receive the authorization request from the access and mobility management function network element AMF.
  • the sending module 620 is used to send the authorization response to the access and mobility management function network element AMF.
  • the first receiving module 610 is configured to receive the authorization request from the session management function network element SMF.
  • the first sending module 620 is used to send the authorization response to the session management function network element SMF.
  • the network device 600 may further include: a generation module for the network device 600 according to one of the information in the authorization request, the contract information of the terminal, and the local configuration information of the drone traffic management entity or Multiple types, generate the authorization response.
  • a generation module for the network device 600 according to one of the information in the authorization request, the contract information of the terminal, and the local configuration information of the drone traffic management entity or Multiple types, generate the authorization response.
  • the authorization request includes the identity of the drone that the terminal requests to control.
  • the authorization request includes the identification of the matching drone controller requested by the terminal.
  • the authorization response includes an identification of a drone that is allowed to be controlled by the terminal.
  • the authorization response includes an identification of a drone controller that allows the terminal to match.
  • the authorization response includes an identification of the unmanned aerial system composed of a matching unmanned aerial vehicle and unmanned aerial vehicle controller.
  • the communication device 700 shown in FIG. 7 may correspond to the drone traffic management entity described above.
  • the communication device 700 may include: at least one processor 710 and a communication interface 720.
  • the communication interface 720 may be used for the information exchange between the communication device 700 and other communication devices.
  • program instructions are executed in the at least one processor 710, the The communication device 700 implements the various steps or methods or operations or functions performed by the drone flow management entity in the foregoing.
  • FIG. 8 is a schematic structural diagram of a terminal provided by an embodiment of the present application.
  • the terminal 800 of FIG. 8 may be the above-mentioned terminal, such as the UE 101 shown in FIG. 1 and the UAV control 201 or UAV 202 shown in FIG. 2.
  • the terminal 800 may be used to implement the steps performed by the terminal in the method shown in FIG. 4 above.
  • the terminal 800 may send a module 810 and a receiving module 820.
  • the sending module 810 is used to send an authorization request to the drone traffic management entity
  • the receiving module 820 is used to receive an authorization response from the drone traffic management entity
  • the authorization request is used to request authorization of the terminal to control the drone, and the authorization response is used to indicate whether the terminal is allowed to control the drone; or, the authorization request is used to request authorization of the terminal and no one.
  • the authorization response is used to indicate whether the terminal is allowed to match with the drone controller.
  • the authorization request includes the identity of the drone that the terminal requests to control.
  • the authorization request includes the identification of the matching drone controller requested by the terminal.
  • the authorization response includes an identification of a drone that is allowed to be controlled by the terminal.
  • the authorization response includes an identification of a drone controller that allows the terminal to match.
  • the authorization response includes an identification of the unmanned aerial system composed of a matching unmanned aerial vehicle and unmanned aerial vehicle controller.
  • the communication device 900 shown in FIG. 9 may correspond to the terminal described above.
  • the communication device 900 may include: at least one processor 910 and a communication interface 920.
  • the communication interface 920 may be used for the information exchange between the communication device 900 and other communication devices.
  • program instructions are executed in the at least one processor 910, the The communication device 900 implements the various steps or methods or operations or functions performed by the terminal in the foregoing.
  • the terminal 1000 of FIG. 10 may be the terminal mentioned above, for example, the UE 101 shown in FIG. 1, the UAV control 201 or UAV 202 shown in FIG. 2.
  • the terminal 1000 may be used to implement the steps performed by the terminal in the method shown in FIG. 5 above, for example.
  • the terminal 1000 includes a sending module 1010 and a receiving module 1020.
  • the sending module 1010 is used to send instruction information to the access and mobility management function network element AMF during the terminal registration process;
  • the receiving module 1020 is used to receive a registration response from the AMF
  • the instruction information is used to indicate that the terminal desires to control the drone, and the registration response is used to indicate whether the terminal is allowed to control the drone; or, the instruction information is used to indicate that the terminal expects to be unmanned The controller matches, and the registration response is used to indicate whether the terminal is allowed to match the drone controller.
  • the sending module 1010 is configured to send the identity of the drone that the terminal requests to control to the AMF.
  • the sending module 1010 is configured to send to the AMF the identifier of the drone controller that the terminal request matches.
  • the registration response is used to refuse the terminal to register.
  • the registration response is used to indicate that the terminal is successfully registered, and indicates that the terminal is not allowed to control the drone.
  • the registration response is used to indicate that the terminal is successfully registered, and instructs the terminal to allow control of the drone.
  • the instruction information is also used to indicate whether the terminal is only used to control the drone, when the instruction information indicates that the terminal is only used to control the drone, and the AMF determines that the terminal is not allowed to control the drone ,
  • the registration response is used to refuse the terminal to register; or, when the instruction information indicates that the terminal is not only used to control the drone, and the AMF determines that the terminal is not allowed to control the drone, the registration response is used to indicate The terminal is successfully registered and indicates that the terminal is not allowed to control the drone.
  • the registration response includes an identification of a drone that is allowed to be controlled by the terminal.
  • the registration response includes an identification of a drone controller that allows the terminal to match.
  • the registration response includes an identification of a drone system composed of a matching drone and drone controller.
  • the communication device 1100 shown in FIG. 11 may correspond to the terminal described above.
  • the communication device 1100 may include: at least one processor 1110 and a communication interface 1120.
  • the communication interface 1120 may be used for the information exchange between the communication device 1100 and other communication devices.
  • program instructions are executed in the at least one processor 1110, the The communication device 1100 implements the various steps or methods or operations or functions performed by the terminal in the foregoing.
  • the network device 1200 of FIG. 12 may be the core network element mentioned above, such as the AMF network element 104 or the SMF network element 105 in FIG. 1.
  • the network device 1200 may be used to implement the above steps performed by the core network element, for example, the steps performed by the AMF in the method shown in FIG. 5.
  • the network device 1200 may include a sending module 1210 and a receiving module 1220.
  • the sending module 1210 is used to send an authorization request to the drone flow entity
  • the receiving module 1220 is used to receive an authorization response from the drone flow entity
  • the authorization request is used to request the authorized terminal to control the drone, and the authorization response is used to indicate whether the terminal is allowed to control the drone; or, the authorization request is used to request the authorized terminal and the drone to control Match, the authorization response is used to indicate whether the terminal is allowed to match the drone controller.
  • the receiving module 1220 is further configured to receive indication information sent by the terminal before the core network element sends an authorization request to the drone traffic entity, where the indication information is used to indicate that the terminal expects to deal with the drone Control; or, the instruction information is used to indicate that the terminal expects to match with the drone controller.
  • the network device 1200 further includes a generation module for generating a registration response according to the authorization response, and when the authorization response indicates that the terminal is allowed to control the drone, the registration response is used to indicate that the terminal has successfully registered and indicates the The terminal allows control of the drone.
  • a generation module for generating a registration response according to the authorization response, and when the authorization response indicates that the terminal is allowed to control the drone, the registration response is used to indicate that the terminal has successfully registered and indicates the The terminal allows control of the drone.
  • the registration response is used to refuse the terminal to register.
  • the registration response is used to indicate that the terminal is successfully registered and indicates that the terminal is not allowed to control the drone.
  • the indication information is also used to indicate whether the terminal is only used to control the drone, when the indication information indicates that the terminal is only used to control the drone, and the authorization response indicates that the terminal is not allowed to control the drone ,
  • the registration response is used to refuse the terminal to register; or, when the instruction information indicates that the terminal is not only used to control the drone, and the authorization response indicates that the terminal is not allowed to control the drone, the registration response is used It indicates that the terminal is successfully registered and that the terminal is not allowed to control the drone.
  • the core network element is an access and mobility management function element AMF or a session management function element SMF.
  • the receiving module 1220 is further configured to receive the identity of the drone that the terminal requests to control from the terminal.
  • the receiving module 1220 is further configured to receive from the terminal the identity of the drone controller that the terminal requests to match.
  • the authorization request includes the identity of the drone that the terminal requests to control.
  • the authorization request includes the identification of the matching drone controller requested by the terminal.
  • the authorization response includes an identification of a drone that is allowed to be controlled by the terminal.
  • the authorization response includes an identification of a drone controller that allows the terminal to match.
  • the authorization response includes an identification of the unmanned aerial system composed of a matching unmanned aerial vehicle and unmanned aerial vehicle controller.
  • the communication device 1300 shown in FIG. 13 may correspond to the core network element described above.
  • the communication device 1300 may include: at least one processor 1310 and a communication interface 1320.
  • the communication interface 1320 may be used for the information exchange between the communication device 1300 and other communication devices.
  • program instructions are executed in the at least one processor 1310, the The communication device 1300 implements the various steps or methods or operations or functions performed by the core network element in the foregoing.
  • the disclosed system, 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 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 function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium.
  • the technical solution of the present application essentially or part of the contribution to the existing technology or part of the technical solution can be embodied in the form of a software product
  • the computer software product is stored in a storage medium, including Several instructions are used to enable a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in the embodiments of the present application.
  • the foregoing storage media include: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk or optical disk and other media that can store program codes .

Abstract

本申请提供了一种无线网络通信方法、网络设备和终端。该方法包括无人机流量管理实体接收授权请求；无人机流量管理实体发送授权响应；其中，授权请求用于请求授权终端对无人机进行控制，授权响应用于指示是否允许终端对无人机进行控制；或者，授权请求用于请求授权终端与无人机控制器进行匹配，授权响应用于指示是否允许终端与无人机控制器进行匹配。用移动通信网络中的无人机流量管理实体对无人机控制器与无人机进行授权或匹配，有利于实现无人机控制器和无人机的远距离通信。

Description

无线网络通信方法、网络设备和终端
本申请要求于2019年1月11日提交中国专利局、申请号为201910028742.8、申请名称为“无线网络通信方法、网络设备和终端”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请实施例涉及通信领域，并且更具体地，涉及一种无线网络通信方法、网络设备和终端。
背景技术
无人机系统(unmanned aerial system，UAS)由无人机控制器和无人机(unmanned aerial vehicle，UAV)组成。随着无人机行业的迅速发展，无人机控制器与无人机之间的通信场景也在发生着变化。
当前无人机应用领域多为短距离场景，无人机控制器与无人机可以通过无线保真(wireless fidelity，WIFI)技术或低功耗蓝牙(bluetooth low energy，BLE)技术进行配对连接，以实现无人机和作为控制装置的无人机控制器进行双向通讯。
然而，这种连接方式无法满足无人机系统在远距离特别是非视距场景下的通信需求。
发明内容
本申请实施例提供一种无线网络通信方法、网络设备和终端，能够解决无人机控制器和无人机的网络授权与匹配问题，有利于实现无人机控制器与无人机的远距离通信。
第一方面，提供一种无线通信方法，包括：无人机流量管理实体接收授权请求；所述无人机流量管理实体发送授权响应；其中，所述授权请求用于请求授权终端对无人机进行控制，所述授权响应用于指示是否允许所述终端对所述无人机进行控制；或者，所述授权请求用于请求授权终端与无人机控制器进行匹配，所述授权响应用于指示是否允许所述终端与所述无人机控制器进行匹配。
用移动通信网络中的无人机流量管理实体对无人机控制器与无人机进行授权或匹配，有利于实现无人机控制器和无人机的远距离通信。
结合第一方面，在一种可能的实现方式中，所述无人机流量管理实体接收授权请求，包括：所述无人机流量管理实体从所述终端接收所述授权请求；所述无人机流量管理实体发送授权响应，包括：所述无人机流量管理实体向所述终端发送所述授权响应。
通过终端与无人机流量管理实体的直接交互，解决了无人机控制器与无人机的授权或匹配问题，有利于实现无人机控制器和无人机的远距离通信，同时由于终端与无人机流量管理实体直接交互，可以提高效率。
结合第一方面，在一种可能的实现方式中，所述无人机流量管理实体接收授权请求， 包括：所述无人机流量管理实体从接入和移动性管理功能网元AMF接收所述授权请求；所述无人机流量管理实体发送授权响应，包括：所述无人机流量管理实体向所述AMF发送所述授权响应。
结合第一方面，在一种可能的实现方式中，所述授权请求承载于非接入层消息中。
结合第一方面，在一种可能的实现方式中，所述无人机流量管理实体接收授权请求，包括：所述无人机流量管理实体从会话管理功能网元SMF接收所述授权请求；所述无人机流量管理实体发送授权响应，包括：所述无人机流量管理实体向所述SMF发送所述授权响应。
无人机控制器与无人机请求网络授权和匹配的过程可以在现有的其他流程中完成，更为方便地解决了无人机系统的授权或匹配问题。
结合第一方面，在一种可能的实现方式中，所述授权请求承载于协议数据单元PDU会话建立消息，所述授权响应承载于PDU会话建立接受消息。
结合第一方面，在一种可能的实现方式中，所述授权请求承载于协议数据单元PDU会话修改消息，所述授权响应承载于PDU会话修改接受消息。
结合第一方面，在一种可能的实现方式中，所述授权请求承载于服务请求消息，所述授权响应承载于服务接受消息。
结合第一方面，在一种可能的实现方式中，还包括：所述无人机流量管理实体根据所述授权请求中的信息、所述终端的签约信息以及所述无人机流量管理实体的本地配置信息中的一种或多种，生成所述授权响应。
结合第一方面，在一种可能的实现方式中，所述授权请求包括所述终端请求控制的无人机的信息；或者，所述授权请求包括所述终端请求匹配的无人机控制器的信息。
结合第一方面，在一种可能的实现方式中，所述授权请求包括所述终端请求控制的无人机的标识；或者，所述授权请求包括所述终端请求匹配的无人机控制器的标识。
结合第一方面，在一种可能的实现方式中，所述授权响应包括允许所述终端控制的无人机的信息；或者，所述授权响应包括允许所述终端匹配的无人机控制器的信息。
结合第一方面，在一种可能的实现方式中，所述授权响应包括允许所述终端控制的无人机的标识；或者，所述授权响应包括允许所述终端匹配的无人机控制器的标识。
结合第一方面，在一种可能的实现方式中，所述授权响应包括允许匹配的无人机和无人机控制器所构成的无人机系统的标识。
第二方面，提供一种无线网络通信方法，包括：终端向无人机流量管理实体发送授权请求；所述终端从所述无人机流量管理实体接收授权响应；其中，所述授权请求用于请求授权所述终端对无人机进行控制，所述授权响应用于指示是否允许所述终端对所述无人机进行控制；或者，所述授权请求用于请求授权所述终端与无人机控制器进行匹配，所述授权响应用于指示是否允许所述终端与所述无人机控制器进行匹配。
通过终端与无人机流量管理实体的直接交互，解决了无人机控制器与无人机的授权或匹配问题，有利于实现无人机控制器和无人机的远距离通信，同时由于终端与无人机流量管理实体直接交互，可以提高效率。
结合第二方面，在一种可能的实现方式中，所述授权请求包括所述终端请求控制的无人机的信息；或者，所述授权请求包括所述终端请求匹配的无人机控制器的信息。
结合第二方面，在一种可能的实现方式中，所述授权请求包括所述终端请求控制的无人机的标识；或者，所述授权请求包括所述终端请求匹配的无人机控制器的标识。
结合第二方面，在一种可能的实现方式中，所述授权响应包括允许所述终端控制的无人机的信息；或者，所述授权响应包括允许所述终端匹配的无人机控制器的信息。
结合第二方面，在一种可能的实现方式中，所述授权响应包括允许所述终端控制的无人机的标识；或者，所述授权响应包括允许所述终端匹配的无人机控制器的标识。
结合第二方面，在一种可能的实现方式中，所述授权响应包括允许匹配的无人机和无人机控制器所构成的无人机系统的标识。
第三方面，提供一种无线网络通信方法，包括：在终端的注册过程中，所述终端向接入和移动性管理功能网元AMF发送指示信息；所述终端从所述AMF接收注册响应；其中，所述指示信息用于指示所述终端请求对无人机进行控制，所述注册响应用于指示是否允许所述终端对所述无人机进行控制；或者，所述指示信息用于指示所述终端请求与无人机控制器进行匹配，所述注册响应用于指示是否允许所述终端与所述无人机控制器进行匹配。
在终端的注册流程中完成无人机控制器和无人机和网络授权或匹配过程，解决了无人机系统的网络授权和匹配问题，有利于实现无人机控制器和无人机的远距离通信，还提高了效率。
结合第三方面，在一种可能的实现方式中，还包括：所述终端向所述AMF发送所述终端请求控制的无人机的信息；或者，所述终端向所述AMF发送所述终端请求匹配的无人机控制器的信息。
结合第三方面，在一种可能的实现方式中，还包括：所述终端向所述AMF发送所述终端请求控制的无人机的标识；或者，所述终端向所述AMF发送所述终端请求匹配的无人机控制器的标识。
结合第三方面，在一种可能的实现方式中，当所述AMF确定不允许所述终端控制无人机时，所述注册响应用于拒绝所述终端进行注册。
结合第三方面，在一种可能的实现方式中，当所述AMF确定不允许所述终端控制无人机时，所述注册响应用于指示所述终端注册成功，且指示不允许所述终端控制无人机。
结合第三方面，在一种可能的实现方式中，当所述AMF确定允许所述终端控制无人机时，所述注册响应用于指示所述终端注册成功，且指示允许所述终端控制无人机，和/或指示是否允许所述终端控制所述无人机。
结合第三方面，在一种可能的实现方式中，所述指示信息还用于指示所述终端是否仅用于控制无人机，当所述指示信息指示所述终端仅用于控制无人机，且所述AMF确定不允许所述终端控制无人机时，所述注册响应用于拒绝所述终端进行注册；或，当所述指示信息指示所述终端不仅仅用于控制无人机，且所述AMF确定不允许所述终端控制无人机时，所述注册响应用于指示所述终端注册成功，且指示不允许所述终端控制无人机。
终端除了可以具有无人机控制器功能外，还可以具有其他功能，本申请的技术方案通过在注册流程中，终端请求网络授权时指示终端是否仅仅用于控制无人机，解决了对无人机控制器进行授权的问题，还解决了不同的无人机控制器类型的注册问题。
结合第三方面，在一种可能的实现方式中，所述注册响应包括允许所述终端控制的无 人机的信息；或者，所述注册响应包括允许所述终端匹配的无人机控制器的信息。
结合第三方面，在一种可能的实现方式中，所述注册响应包括允许所述终端控制的无人机的标识；或者，所述注册响应包括允许所述终端匹配的无人机控制器的标识。
结合第三方面，在一种可能的实现方式中，所述注册响应还包括允许匹配的无人机和无人机控制器所构成的无人机系统的标识。
第四方面，提供一种无线网络通信方法，包括：核心网网元向无人机流量管理实体发送授权请求；所述核心网网元从所述无人机流量管理实体接收授权响应；其中，所述授权请求用于请求授权终端对无人机进行控制，所述授权响应用于指示是否允许所述终端对所述无人机进行控制；或者，所述授权请求用于请求授权终端与无人机控制器进行匹配，所述授权响应用于指示是否允许所述终端与所述无人机控制器进行匹配。
结合第四方面，在一种可能的实现方式中，在所述核心网网元向无人机流量管理实体发送授权请求之前，还包括：接收所述终端发送的指示信息；其中，所述指示信息用于指示所述终端请求对无人机进行控制；或者，所述指示信息用于指示所述终端请求与无人机控制器进行匹配。
结合第四方面，在一种可能的实现方式中，还包括：所述核心网网元根据所述授权响应生成注册响应，其中当所述授权响应指示允许所述终端控制无人机时，所述注册响应用于指示所述终端注册成功，且指示允许所述终端控制无人机，和/或指示是否允许所述终端控制所述无人机。
结合第四方面，在一种可能的实现方式中，当所述授权响应指示不允许所述终端控制无人机时，所述注册响应用于拒绝所述终端进行注册。
结合第四方面，在一种可能的实现方式中，当所述授权响应指示不允许所述终端控制无人机时，所述注册响应用于指示所述终端注册成功，且指示不允许所述终端控制无人机。
结合第四方面，在一种可能的实现方式中，所述指示信息还用于指示所述终端是否仅用于控制无人机，当所述指示信息指示所述终端仅用于控制无人机，且所述授权响应指示不允许所述终端控制无人机时，所述注册响应用于拒绝所述终端进行注册；或当所述指示信息指示所述终端不仅仅用于控制无人机，且所述授权响应指示不允许所述终端控制无人机时，所述注册响应用于指示所述终端注册成功，且指示不允许所述终端控制无人机。
通过终端的注册流程，完成无人机控制器或无人机的注册授权以及匹配的过程，解决了无人机系统接入网络的问题。同时，通过在注册流程中指示该终端是否仅用于控制无人机，解决了网络侧为不同类型的无人机控制器进行注册授权的问题。
结合第四方面，在一种可能的实现方式中，所述核心网网元为接入和移动性管理功能网元AMF或会话管理功能网元SMF。
结合第四方面，在一种可能的实现方式中，还包括：所述核心网网元从所述终端接收所述终端请求控制的无人机的信息；或者，所述核心网网元从所述终端接收所述终端请求匹配的无人机控制器的信息。
结合第四方面，在一种可能的实现方式中，还包括：所述核心网网元从所述终端接收所述终端请求控制的无人机的标识；或者，所述核心网网元从所述终端接收所述终端请求匹配的无人机控制器的标识。
结合第四方面，在一种可能的实现方式中，所述授权请求包括所述终端请求控制的无 人机的信息；或者，所述授权请求包括所述终端请求匹配的无人机控制器的信息。
结合第四方面，在一种可能的实现方式中，所述授权请求包括所述终端请求控制的无人机的标识；或者，所述授权请求包括所述终端请求匹配的无人机控制器的标识。
结合第四方面，在一种可能的实现方式中，所述授权响应包括允许所述终端控制的无人机的信息；或者，所述授权响应包括允许所述终端匹配的无人机控制器的信息。
结合第四方面，在一种可能的实现方式中，所述授权响应包括允许所述终端控制的无人机的标识；或者，所述授权响应包括允许所述终端匹配的无人机控制器的标识。
结合第四方面，在一种可能的实现方式中，所述授权响应还包括允许匹配的无人机和无人机控制器所构成的无人机系统的标识。
第五方面，提供一种无线网络通信方法，包括：终端向无人机流量管理实体发送授权请求；所述无人机流量管理实体向终端发送授权响应；其中，所述授权请求用于请求授权所述终端对无人机进行控制，所述授权响应用于指示是否允许所述终端对所述无人机进行控制；或者所述授权请求用于请求授权所述终端与无人机控制器进行匹配，所述授权响应用于指示是否允许所述终端与所述无人机控制器进行匹配。
结合第五方面，在一种可能的实现方式中，所述授权请求包括所述终端请求控制的无人机的标识；或者所述授权请求包括所述终端请求匹配的无人机控制器的标识。
结合第五方面，在一种可能的实现方式中，所述授权响应包括允许所述终端控制的无人机的标识；或者，所述授权响应包括允许所述终端匹配的无人机控制器的标识。
结合第五方面，在一种可能的实现方式中，所述授权请求包括所述终端的信息。
结合第五方面，在一种可能的实现方式中，所述授权响应包括允许匹配的无人机和无人机控制器所构成的无人机系统的标识。
结合第五方面，在一种可能的实现方式中，还包括：所述无人机流量管理实体向统一数据管理功能网元发送请求获取所述终端的签约信息的消息；所述统一数据管理功能网元向所述无人机流量管理实体发送所述终端的签约信息。
第六方面，提供一种无线网络通信方法，包括：核心网网元向无人机流量管理实体发送授权请求；所述无人机流量管理实体向所述核心网网元发送授权响应；其中，所述授权请求用于请求授权终端对无人机进行控制，所述授权响应用于指示是否允许所述终端对所述无人机进行控制；或者，所述授权请求用于请求授权终端与无人机控制器进行匹配，所述授权响应用于指示是否允许所述终端与所述无人机控制器进行匹配。
结合第六方面，在一种可能的实现方式中，所述授权请求包括所述终端请求控制的无人机的标识；或者所述授权请求包括所述终端请求匹配的无人机控制器的标识。
结合第六方面，在一种可能的实现方式中，所述授权响应包括允许所述终端控制的无人机的标识；或者，所述授权响应包括允许所述终端匹配的无人机控制器的标识。
结合第六方面，在一种可能的实现方式中，所述授权请求包括所述终端的信息。
结合第六方面，在一种可能的实现方式中，所述授权响应包括允许匹配的无人机和无人机控制器所构成的无人机系统的标识。
结合第六方面，在一种可能的实现方式中，核心网网元为接入和移动性管理功能网元AMF或会话管理功能网元SMF。
结合第六方面，在一种可能的实现方式中，还包括：所述无人机流量管理实体向统一 数据管理功能网元发送请求获取所述终端的签约信息的消息；所述统一数据管理功能网元向所述无人机流量管理实体发送所述终端的签约信息。
第七方面，提供一种无线网络通信方法，包括：终端向核心网网元发送第一信息；核心网网元向所述终端发送第二信息；其中所述第一信息用于请求授权终端对无人机进行控制，所述第二信息用于指示是否允许所述终端对所述无人机进行控制；或者，所述第一信息用于请求授权终端与无人机控制器进行匹配，所述第二信息用于指示是否允许所述终端与所述无人机控制器进行匹配。
结合第七方面，在一种可能的实现方式中，所述第一信息包括所述终端请求控制的无人机的标识；或者所述第一信息包括所述终端请求匹配的无人机控制器的标识。
结合第七方面，在一种可能的实现方式中，所述第二信息包括允许所述终端控制的无人机的标识；或者，所述第二信息包括允许所述终端匹配的无人机控制器的标识。
结合第七方面，在一种可能的实现方式中，所述核心网网元为接入和移动性管理功能网元AMF或会话管理功能网元SMF。
结合第七方面，在一种可能的实现方式中，所述第一信息为注册请求，所述第二信息为注册响应。
结合第七方面，在一种可能的实现方式中，还包括：核心网网元向无人机流量管理实体发送授权请求；所述无人机流量管理实体向所述核心网网元发送授权响应；其中，所述授权请求用于请求授权终端对无人机进行控制，所述授权响应用于指示是否允许所述终端对所述无人机进行控制；或者，所述授权请求用于请求授权终端与无人机控制器进行匹配，所述授权响应用于指示是否允许所述终端与所述无人机控制器进行匹配。
结合第七方面，在一种可能的实现方式中，所述授权请求包括所述终端请求控制的无人机的标识；或者所述授权请求包括所述终端请求匹配的无人机控制器的标识。
结合第七方面，在一种可能的实现方式中，所述授权响应包括允许所述终端控制的无人机的标识；或者，所述授权响应包括允许所述终端匹配的无人机控制器的标识。
结合第七方面，在一种可能的实现方式中，还包括：所述无人机流量管理实体向统一数据管理功能网元发送请求获取所述终端的签约信息的消息；所述统一数据管理功能网元向所述无人机流量管理实体发送所述终端的签约信息。
第八方面，提供一种无线通信方法，包括：第一核心网网元向第二核心网网元发送第三信息；所述第二核心网网元向第一核心网网元发送第四信息；其中所述第三信息用于请求授权终端对无人机进行控制，所述第四信息用于指示是否允许所述终端对所述无人机进行控制；或者，所述第三信息用于请求授权终端与无人机控制器进行匹配，所述第四信息用于指示是否允许所述终端与所述无人机控制器进行匹配。
结合第八方面，在一种可能的实现方式中，所述第三信息包括所述终端请求控制的无人机的标识；或者所述第三信息包括所述终端请求匹配的无人机控制器的标识。
结合第八方面，在一种可能的实现方式中，所述第四信息包括允许所述终端控制的无人机的标识；或者，所述第四信息包括允许所述终端匹配的无人机控制器的标识。
结合第八方面，在一种可能的实现方式中，还包括：所述第二核心网网元向第三核心网网元发送第五信息；所述第三核心网网元向所述第二核心网网元发送第六信息；其中，第五信息用于请求授权终端对无人机进行控制，所述第六信息用于指示是否允许所述终端 对所述无人机进行控制；或者，所述第五信息用于请求授权终端与无人机控制器进行匹配，所述第六信息用于指示是否允许所述终端与所述无人机控制器进行匹配。
结合第八方面，在一种可能的实现方式中，所述第五信息包括所述终端请求控制的无人机的标识；或者所述第五信息包括所述终端请求匹配的无人机控制器的标识。
结合第八方面，在一种可能的实现方式中，所述第六信息包括允许所述终端控制的无人机的标识；或者，所述第六信息包括允许所述终端匹配的无人机控制器的标识。
第九方面，提供一种网络设备，包括用于执行上文中的由无人机流量管理实体执行的方法或步骤或操作或功能的模块。
第十方面，提供一种终端，包括用于执行上文中的由终端执行的方法或步骤或操作或功能的模块。
第十一方面，提供一种网络设备，执行上文中的由核心网网元执行的方法或步骤或操作或功能的模块。
第十二方面，提供一种通信装置，所述通信装置包括：至少一个处理器和通信接口，所述通信接口用于所述通信装置与其他通信装置进行信息交互，当程序指令在所述至少一个处理器中执行时，使得所述通信装置实现上文中的无人机流量管理实体的功能。
第十三方面，提供一种通信装置，所述通信装置包括：至少一个处理器和通信接口，所述通信接口用于所述通信装置与其他通信装置进行信息交互，当程序指令在所述至少一个处理器中执行时，使得所述通信装置实现上文中的终端的功能。
第十四方面，提供一种通信装置，所述通信装置包括：至少一个处理器和通信接口，所述通信接口用于所述通信装置与其他通信装置进行信息交互，当程序指令在所述至少一个处理器中执行时，使得所述通信装置实现上文中的核心网网元的功能。
第十五方面，提供一种计算机程序存储介质，所述计算机程序存储介质具有程序指令，当所述程序指令被直接或者间接执行时，使得上文中的无人机流量管理实体的功能得以实现。
第十六方面，提供一种计算机程序存储介质，所述计算机程序存储介质具有程序指令，当所述程序指令被直接或者间接执行时，使得上文中的终端的功能得以实现。
第十七方面，提供一种计算机程序存储介质，所述计算机程序存储介质具有程序指令，当所述程序指令被直接或者间接执行时，使得上文中的核心网网元的功能得以实现。
第十八方面，提供一种芯片系统，所述芯片系统包括至少一个处理器，当程序指令在所述至少一个处理器中执行时，使得上文中的无人机流量管理实体的功能得以实现。
第十九方面，提供一种芯片系统，所述芯片系统包括至少一个处理器，当程序指令在所述至少一个处理器中执行时，使得上文中的终端的功能得以实现。
第二十方面，提供一种芯片系统，所述芯片系统包括至少一个处理器，当程序指令在所述至少一个处理器中执行时，使得上文中的核心网网元的功能得以实现。
第二十一方面，提供一种计算机程序产品，包括程序指令，当所述程序指令被直接或者间接执行时，使得上文中的无人机流量管理实体的功能得以实现。
第二十二方面，提供一种计算机程序产品，包括程序指令，当所述程序指令被直接或者间接执行时，使得上文中的终端的功能得以实现。
第二十三方面，提供一种计算机程序产品，包括程序指令，当所述程序指令被直接或 者间接执行时，使得上文中的核心网网元的功能得以实现。
第二十四方面，提供一种通信系统，包括上文中的终端和无人机流量管理实体。所述终端用于向无人机流量管理实体发送授权请求；所述无人机流量管理实体用于向终端发送授权响应；其中，所述授权请求用于请求授权所述终端对无人机进行控制，所述授权响应用于指示是否允许所述终端对所述无人机进行控制；或者所述授权请求用于请求授权所述终端与无人机控制器进行匹配，所述授权响应用于指示是否允许所述终端与所述无人机控制器进行匹配。
可选地，所述通信系统还可以包括统一数据管理功能网元。
第二十五方面，提供一种通信系统，包括上文中的核心网网元和无人机流量管理实体。核心网网元用于向无人机流量管理实体发送授权请求；所述无人机流量管理实体用于向所述核心网网元发送授权响应；其中，所述授权请求用于请求授权终端对无人机进行控制，所述授权响应用于指示是否允许所述终端对所述无人机进行控制；或者，所述授权请求用于请求授权终端与无人机控制器进行匹配，所述授权响应用于指示是否允许所述终端与所述无人机控制器进行匹配。
可选地，所述系统还包括统一数据管理功能网元。
第二十六方面，提供一种通信系统，包括上文中的终端和核心网网元。终端用于向核心网网元发送第一信息；核心网网元用于向所述终端发送第二信息；其中所述第一信息用于请求授权终端对无人机进行控制，所述第二信息用于指示是否允许所述终端对所述无人机进行控制；或者，所述第一信息用于请求授权终端与无人机控制器进行匹配，所述第二信息用于指示是否允许所述终端与所述无人机控制器进行匹配。
可选地，所述通信系统还可以包括上文中的无人机流量管理实体。
可选地，所述通信系统还可以包括上文中的统一数据管理功能网元。
第二十七方面，提供一种通信系统，包括上文中的第一核心网网元和第二核心网网元。第一核心网网元用于向第二核心网网元发送第三信息；所述第二核心网网元用于向第一核心网网元发送第四信息；其中所述第三信息用于请求授权终端对无人机进行控制，所述第四信息用于指示是否允许所述终端对所述无人机进行控制；或者，所述第三信息用于请求授权终端与无人机控制器进行匹配，所述第四信息用于指示是否允许所述终端与所述无人机控制器进行匹配。
可选地，所述通信系统还可以包括上文中的第三核心网网元。
附图说明
图1是本申请实施例的网络系统架构示意图。
图2是本申请实施例的应用场景的示意图。
图3是本申请一个实施例的无线网络通信方法的示意性流程图。
图4是本申请另一实施例的无线网络通信方法的示意性流程图。
图5是本申请又一实施例的无线网络通信方法的示意性流程图。
图6是本申请一个实施例提供的一种网络设备的示意性结构图。
图7是本申请一个实施例提供的一种通信装置的示意性结构图。
图8是本申请另一个实施例提供的终端的示意性结构图。
图9是本申请另一个实施例提供的通信装置的示意性结构图。
图10是本申请又一个实施例提供的一种终端的示意性结构图。
图11是本申请又一个实施例提供的一种通信装置的示意性结构图。
图12是本申请又一个实施例提供的网络设备的示意性结构图。
图13是本申请又一个实施例提供的一种通信装置的示意性结构图。
具体实施方式
下面将结合附图，对本申请实施例中的技术方案进行描述。
近年来，随着无人机行业的迅速发展，无人机控制器与无人机之间的通信场景也在发生着变化。对于短距离的控制，例如在当前民用无人机所应用的短距离场景中，无人机控制器与无人机之间可以通过短距离无线技术例如WIFI或蓝牙等方式进行配对连接，以实现无人机控制器与无人机之间的双向通讯。然而随着无人机应用场景的扩增，短距离无线技术已经无法满足无人机控制器与无人机在长距离特别是非视距场景中的通讯需求。
第三代合作伙伴计划(the 3rd generation partner project，3GPP)网络具有无处不在的覆盖范围，较高的可靠性和服务质量(quality of service，QoS)性能、健壮的安全防护以及无缝的移动性。未来无人机系统通过接入网或核心网进行配对连接，可以实现远距离通信。
图1示出了本申请实施例的网络架构的示意图，如图1所示，该网络架构中具体可以包括下列网元：
用户设备(user equipment，UE)101、接入网(access network，AN)设备102、用户面功能(user plane function，UPF)网元103、接入和移动性管理功能(access and mobility management function，AMF)网元104、会话管理功能(session management function，SMF)网元105、策略控制功能(policy control function，PCF)网元106、统一数据管理(unified data management，UDM)网元107和数据网络(data network，DN)108。
UE101也可以称为终端(terminal)。终端可以经AN设备102与一个或多个核心网(core network，CN)进行通信。终端可称为接入终端、终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、无线网络设备、用户代理或用户装置。终端可以是蜂窝电话(cellular phone)、无绳电话、会话启动协议(session initiation protocol，SIP)电话、智能电话(smart phone)、无线本地环路(wireless localloop，WLL)站、个人数字处理(personal digital assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它设备、车载设备、可穿戴设备、无人机设备或物联网、车联网中的终端以及未来网络例如第五代移动通信(fifth generation，5G)网络中的任意形态的终端、中继用户设备或者未来演进的公用陆地移动通信网络(public land mobile network，PLMN)中的终端等，其中，中继用户设备例如可以是5G家庭网关(residential gateway，RG)。本申请实施例对此并不限定。为方便描述，本申请中，上面提到的设备统称为终端。
AN设备102也可以称之为接入设备，该接入设备指的是可以接入核心网的设备，例如可以是无线接入网(radio access network，RAN)设备。RAN设备也可称之为网络设备，是终端通过无线方式接入到移动通信系统中的接入设备，RAN设备的一种示例是基站 (base station，BS)，也可以称为基站设备。
无线接入网设备可以是新无线技术(new radio access technology，NR)系统中的传输接收点(transmission reception point，TRP)、5G系统中的下一代基站节点(next generation node basestation，gNB)、长期演进(long term evolution，LTE)中的演进型节点B(evolved node B，eNB)、全球移动通讯(global system of mobile communication，GSM)或码分多址(code division multiple access，CDMA)中的基站收发台(base transceiver station,BTS)，还可以是无线网络控制器(radio network controller，RNC)、节点B(node B，NB)、基站控制器(base station controller，BSC)、家庭基站(例如，home evolved nodeB，或home node B，HNB)、基带单元(base band unit，BBU)，或Wifi接入点(access point，AP)，或小基站设备(pico)，或者未来5G网络中的网络设备等。
应理解，本文对网络设备的具体类型不作限定。采用不同无线接入技术的系统中，具备网络设备功能的设备的名称可能会有所不同。为方便描述，本申请所有实施例中，上述为终端提供无线通信功能的装置统称为接入网设备。不同的接入网设备可以位于同一个小区，也可以位于不同的小区，具体的在此不做限定。
UPF网元103具有终端的报文转发、封装和统计等功能，负责用户数据的转发，AN设备102和UPF网元103之间的接口可以为N3接口。
可选地，UPF网元具体分为中间-UPF(intermediate-UPF，I-UPF)和锚点UPF(anchor-UPF，A-UPF)，其中，I-UPF与接入网RAN连接，A-UPF为会话锚点的UFP，A-UPF又可以称为PDU会话锚点UPF(PDU session anchor UPF，PSA)，本申请实施例对此不作限定。
AMF网元104负责终端的接入和移动性管理，具有对用户进行认证、切换、位置更新等功能。例如，负责UE位置更新、UE注册网络或UE切换等，UE101和AMF网元104之间的接口可以为N1接口，AN设备102和AMF网元104之间的接口可以为N2接口。
SMF网元105负责UPF网元103的选择、重选，互联网协议(internet protocol，IP)地址的分配等，还可以负责会话的建立、修改和释放等，SMF网元105和UPF网元103之间的接口可以为N4接口。
可选地，SMF网元具体可以分为中间SMF(intermediate-SMF，I-SMF)网元和锚点SMF(anchor-SMF，A-SMF)网元两种类型，其中，I-SMF网元控制与接入网络接口的用户面功能(user plane function，UPF)网元(即I-UPF)，A-SMF网元控制会话锚点UPF网元(即A-UPF)。
PCF网元106用于实现包括管理网络行为的统一策略框架、为控制面提供需要执行的策略规则以及获取与策略决策相关的订阅信息等功能，既包括移动性相关策略，也包括协议数据单元(protocol data unit，PDU)会话相关策略，例如，服务质量(quality of service，QoS)策略、计费策略等。
UDM网元107用于存储用户的签约数据。
DN108是指为UE提供数据传输服务的运营商网络。例如，DN可以是提供IP多媒体业务(IP multi-media，IMS)、互联网业务等业务的网络，UPF网元103和DN108之间的接口可以为N6接口。
需要说明的是，图1中仅以终端为UE作出了示例性说明，图1中的各个网元之间的接口名称仅仅是一个示例，在具体实现中，该系统架构的接口名称还可能为其他名称，本申请实施例对此不做具体限定。
应理解，本申请实施例并不限于图1所示的系统架构中。例如，可以应用本申请实施例的通信方法的通信系统中可以包括更多或更少的网元或设备。图1中的设备或网元可以是硬件，也可以是从功能上划分的软件或者以上二者的结合。图1中的设备或网元之间可以通过其他设备或网元通信。
无人机系统由无人机控制器与无人机组成。由于无人机需要占用空域的特殊性，监管部门需要及时识别和管控，3GPP网络引入一个新的实体，即无人机流量管理实体(unmanned aerial vehicle traffic management，UTM)。UTM可以存储无人机控制器和无人机相关数据，例如标识信息、拥有者信息、路径信息、当前位置、操作状态等等，UTM可用于无人机控制器与无人机配对，标识无人机系统，授权对于无人机系统的操作，还可以管理、干预无人机控制器与无人机之间的通信等。
图2示出了本申请实施例的应用场景示意图。如图2所示，无人机系统UAS200可以与带有无人机流量管理实体UTM203的网络系统进行信息交互和无线通信。例如，无人机控制器201或无人机202可以与接入网(radio access network，RAN)204、核心网(core network，CN)205进行信息交互，还可以通过接入网204或核心网205与UTM203进行信息交互；无人机控制器201还可以通过接入网204或核心网205与无人机202进行信息交互，还可以通过UTM203与无人机202进行信息交互。
应理解，无人机控制器201与无人机202可以处于同一接入网或核心网中，也可以处于不同的接入网或核心网中，本申请实施例对此并不限定。
无人机UAV202，还可以称为无人驾驶飞机、空中机器人，是利用无线电遥控设备和自备的程序控制装置的不载人飞机，可以在无人驾驶的条件下完成空中飞行任务和各种负载任务。本申请实施例中的无人机可以是无人直升机、固定翼机、多旋翼飞行器、无人飞艇、无人伞翼机；还可以包括临近空间飞行器，例如平流层飞艇、高空气球、太阳能无人机等；还可以是四轴、六轴、单轴、矢量控制等多种形式的无人机。本申请实施例中的无人机可以用于军事、工业、民用、农业、建筑、影视、环保等领域以及用到无人机作业的特种行业，例如用无人机来进行军事侦察、巡视、航拍、环境监测、边防监控、送快递、电力巡检、确权、防汛抗旱、灾后救援等等。本申请实施例对此并不限定。
应理解，本文对无人机的具体类型不作限定。随着智能化的发展，为应用于不同的场景或完成不同的空中飞行任务，具备无人驾驶飞机功能的设备的名称可能会有所不同。为方便描述，本申请所有实施例中，上述能够具备无人驾驶飞机功能的装置统称为无人机。
无人机202可以配备有多种传感器或功能模块，例如陀螺仪(飞行姿态感知)、加速计、地磁感应、气压传感器(悬停高度粗略控制)、超声波传感器(低空高度精确控制或避障)、光流传感器(悬停水平位置精确确定)、GPS模块(水平位置高度粗略定位)、控制电路、指南针等，通过采集无人机的角速率、姿态、位置、加速度、高度和空速等，能够实现自动保持无人机的正常飞行姿态。
应理解，上述无人机配置的模块或硬件名称仅仅是一个示例，在具体实现中，各个功能模块还可以有其他的名称，本申请实施例对此并不限定。本申请实施例中的无人机还可 以具有更多或更少的功能模块，也可以实现更多或更少的功能等，本申请实施例对此也不做任何限定。
无人机控制器(UAV controller)201用于对无人机202进行控制，例如控制无人机的飞行状态或飞行动作等。无人机控制器可以是智能手机、平板、手提电脑、智能手表或智能遥控器、传统遥控器、专用远程控制器等，还可以是手环、指环、手套、臂带、手表等可用于手势控制无人机的装置，还可以是头套等可用于意念控制无人机的头戴设备，还可以是智能夹克、外套等可用于用户身体动作控制无人机的装置等。
应理解，本文对无人机控制器的具体类型不作限定。随着智能化的发展，具备无人机控制器功能的设备的名称和形式可能会有所不同。为方便描述，本申请所有实施例中，上述能够具备无人机控制器功能或能够控制无人机的装置统称为无人机控制器。
无人机控制器201可以对无人机202的飞行状态进行控制，例如无人机控制器可以控制无人机的方向、副翼、升降、倾斜、速度、油门、襟翼等，还可以控制无人机的转弯、爬升、俯冲、横滚、悬停、起飞、落地等动作，本申请实施例对此不做任何限定。
还应理解，无人机系统200可以包括一个或多个无人机控制器201和一个或多个无人机202。例如，一个无人机控制器可以控制一个或多个无人机，一个无人机也可以被一个或多个无人机控制器控制，多个无人机控制器也可以协同控制多个无人机，本申请实施例对此不做限定。
无人机系统200中的无人机202可以是上文提到的任意一种或多种类型，无人机控制器201也可以是上文提到的任意一种或多种类型，本申请实施例对此不做任何限定。
上文提到无人机系统200可以通过接入3GPP网络实现远距离通信，然而目前还没有解决网络如何对无人机和无人机控制器进行授权和匹配的问题。下面结合图3，对本申请实施例进行详细描述。
图3示出了本申请实施例的无线网络通信方法的示意性流程图。如图3所示，该方法可以包括步骤S310至步骤S320。
在步骤S310，核心网网元向无人机流量管理实体UTM发送授权请求。
在步骤S320，无人机流量管理实体向核心网网元发送授权响应。
该终端可以是无人机控制器，例如图1所示的UE101或图2所示的UAV控制器201。该终端可以仅用于控制无人机，也可以不仅仅用于控制无人机，换句话说，该终端除了可以控制无人机外，可以还具有其他的功能。例如当智能手机可以控制无人机时，该智能手机即是一个无人机控制器，智能手机除了具有无人机控制器功能外，还具有通讯、拍照、娱乐等其他功能。
当该终端为无人机控制器时，其可以具有无人机控制器功能，可以对无人机进行控制。授权请求可以理解为无人机控制器对应的授权请求，该授权请求用于请求授权该终端对无人机进行控制，也可以理解为终端请求授权使用无人机控制器功能。授权响应可以理解为无人机控制器对应的授权响应，该授权响应用于指示是否允许无人机控制器对无人机进行控制，授权响应还可以指示是否允许该终端使用无人机控制器功能。
可选地，当该终端为无人机控制器时，无人机控制器发送授权请求的过程也可以理解为请求匹配无人机的过程，即无人机控制器请求与无人机进行匹配。
在某些实施例中，无人机控制器可以在请求控制无人机的过程中与无人机进行匹配。
在某些实施例中，无人机控制器还可以先请求与无人机进行匹配，而在其他时刻请求控制无人机。
换句话说，无人机控制器请求与无人机匹配的过程与无人机控制器请求控制无人机的过程可以分开进行，也可以同时进行。当同时进行时，本申请中的无人机控制器请求控制无人机的过程，也可以包括无人机控制器请求与无人机进行匹配。
该无人机控制器对应的授权请求中还可以包括该无人机控制器请求控制的无人机的信息，例如无人机控制器请求控制的无人机标识或标识列表。该无人机标识可以是3GPP系统中的唯一标识，也可以是无人机行业特有的标识，也可以是其他任何能够用于唯一确定无人机的标识，本申请实施例对此不做限定。授权请求中包括该无人机控制器请求控制的无人机的信息，可以理解为无人机控制器请求对指定的无人机进行控制。
该无人机控制器对应的授权请求中还可以包括该无人机控制器的信息，例如该无人机控制器的唯一标识符，无人机控制器的UE能力，位置，拥有者标识，拥有者地址，拥有者联系方式，拥有者资格证书，操作无人机控制器的无人机操作者的标识符，无人机操作者的许可和资格证书以及其他与无人机控制器相关的数据等，授权请求中可以包括上述部分或全部的信息，或其他未穷尽的无人机控制器相关数据等，本申请对此不做限定。
该无人机控制器对应的授权响应中可以包括允许该无人机控制器控制的无人机的信息，例如UTM允许该无人机控制器控制的无人机标识或标识列表，可以理解为UTM允许该无人机控制器控制指定的无人机。该无人机控制器对应的授权响应中可以包括拒绝该无人机控制器控制的无人机的信息，例如UTM拒绝该无人机控制器控制的无人机标识或标识列表。
可选地，该无人机控制器对应的授权响应中还可以包括允许该无人机控制器控制的无人机的信息和拒绝该无人机控制器控制的无人机的信息，例如无人机的标识，或者可以包括其中一个。
应理解，授权请求中包括的请求控制的无人机标识或标识列表与授权响应中包括的允许无人机控制器控制的无人机标识或标识列表可以相同，也可以不同。授权请求和授权响应中可以都包括上述对应的无人机标识或标识列表，也可以不都包括或都不包括。
作为一个示例，授权请求中可以包括无人机控制器请求控制的无人机标识或标识列表，授权响应中可以包括确认信息，以确认允许该无人机控制器控制其请求控制的无人机。
作为另一个示例，授权请求中可以包括无人机控制器请求控制的无人机标识或标识列表，授权响应中可以包括允许该无人机控制器控制的无人机标识或标识列表，或从请求控制的无人机标识列表中选择该无人机控制器可以控制的无人机标识。其中，允许该无人机控制器控制的无人机标识或标识列表可以是网络根据终端的签约信息或本地配置信息确定的。
作为再一个示例，授权请求中可以不包括无人机控制器请求控制的无人机的信息，授权响应中可以包括系统确定的允许该无人机控制器控制的无人机标识或标识列表，或签约信息或本地配置信息中默认的、预配置的可被该无人机控制器控制的无人机标识或标识列表。
另外，无人机控制器对应的授权响应中，还可以包括该无人机控制器和允许该无人机控制器控制的无人机所构成的UAS的标识符，该标识符可以用于多播等场景。
该终端还可以是无人机，例如图1所示的UE101或图2所示的无人机202。
当该终端为无人机时，其可以具有无人机功能，可以与无人机控制进行匹配。可以理解为无人机对应的授权请求，该授权请求用于请求授权该终端与无人机控制器进行匹配，可以理解为终端请求授权使用无人机功能；授权响应可以理解为无人机对应的授权响应，该授权响应用于指示是否允许无人机与无人机控制进行匹配，授权响应还可以指示允许该终端具有无人机功能。
该无人机对应的授权请求中还可以包括无人机期望匹配的无人机控制器的信息，例如控制无人机的无人机控制器的标识或标识列表。该无人机控制器的标识可以是3GPP系统中的唯一标识，可以是无人机行业特有的标识，还可以是其他任何用于唯一确定无人机控制器的标识，本申请实施例对此不做限定。授权请求中包括该无人机请求匹配的无人机控制器的信息，可以理解为无人机请求与指定的无人机控制器进行匹配。
该无人机对应的授权请求中还可以包括该无人机的信息，例如唯一标识符，无人机的UE能力，规格和型号，序列号，起飞质量，位置，拥有者标识，拥有者地址，拥有者联系方式，拥有者资格证书，起飞位置和时间，任务类型，路径数据，操作状态以及其他与无人机相关的数据等，授权请求中可以包括上述部分或全部的信息，或其他未穷尽的无人机相关数据，本申请对此不做限定。
该无人机对应的授权响应中可以包括允许该无人机进行匹配的无人机控制器的信息，例如UTM允许该无人机进行匹配的无人机控制器标识或标识列表，可以理解为UTM允许该无人机与指定的无人机控制器进行匹配。
应理解，授权请求中包括的请求进行匹配的无人机控制器标识或标识列表与授权响应中包括的允许无人机进行匹配的无人机控制器标识或标识列表可以相同，也可以不同。授权请求和授权响应中可以都包括上述对应的无人机控制器标识或标识列表，也可以不都包括或都不包括。
作为一个示例，授权请求中可以包括无人机请求匹配的无人机控制器标识或标识列表，授权响应中可以包括确认信息，以确认允许该无人机与其期望匹配的无人机控制器进行匹配。
作为另一个示例，授权请求中可以包括无人机请求匹配的无人机控制器标识或标识列表，授权响应中可以包括允许该无人机匹配的无人机控制器标识或标识列表，或从请求匹配的无人机控制器标识列表中选择该无人机可以匹配的无人机控制器标识。其中，允许该无人机进行匹配的无人机标识或标识列表可以是网络根据终端的签约信息或本地配置信息确定的。
作为再一个示例，授权请求中可以不包括无人机请求匹配的无人机控制器的信息，授权响应中可以包括系统确定的允许该无人机匹配的无人机控制器标识或标识列表，或签约信息或本地配置信息中默认的、预配置的可与该无人机进行匹配的无人机控制器标识或标识列表。
可选地，该无人机对应的授权响应中还可以同时包括允许该无人机匹配的无人机控制器的信息和拒绝该无人机匹配的无人机控制器的信息，例如无人机控制器的标识。
应理解，无人机请求匹配的无人机控制器，可以理解为该无人机可以被该无人机控制器控制。
另外，无人机对应的授权响应中，还可以包括该无人机和允许该无人机匹配的无人机控制器所构成的UAS的标识符，该标识符可以用于多播等场景。
还应理解，本申请对无人机控制器或无人机的类型不做任何限定。
在步骤S310和步骤S320中，核心网网元可以是位于图2所示的核心网204中的网元，例如接入和移动性管理功能网元、会话管理功能网元等，如图1所示的AMF网元104、SMF网元105。核心网网元还可以是其他的与UTM可进行信息交互的网元。
无人机流量管理实体UTM接收授权请求过程可以通过不同的流程来进行，例如可以是在终端完成注册后，由终端单独发起的授权请求过程，也可以是在终端注册过程中向网络请求授权。关于在终端注册过程中请求授权的示例，下面会结合具体的实施例进行描述，此处暂不详述。
无人机流量管理实体UTM接收授权请求可以有多种实现方式。这里，终端可以是无人机或无人机控制器，为简洁，以下统一用终端来对无人机或无人机控制器两种终端类型进行描述。
作为一个示例，终端可以向核心网网元发送该授权请求，由核心网网元将该授权请求转发给无人机流量管理实体。
作为另一个示例，终端可以向核心网网元发送一个指示信息，该指示信息可以指示终端请求对无人机进行控制或终端请求与无人机控制器进行匹配，核心网网元根据该指示信息可以自行生成向UTM发送的授权请求，该授权请求即可以理解为终端对应的授权请求，该授权请求用于请求授权该终端使用无人机控制器功能或无人机功能。
应理解，上述列举的示例中，授权请求中可以包括上文提到的授权请求中可以包括的信息中的一种或多种。
可选地，该终端对应的授权请求可以承载于服务请求消息、协议数据单元(protocol data unit，PDU)会话建立消息、PDU会话修改消息或非接入层(non-access-stratum，NAS)消息中，也可以承载于新增的信令或其他的消息中。
相应地，该终端对应的授权响应可以承载于服务接受消息、PDU会话建立接受消息、PDU会话修改接受消息或新增的信令或其他的消息中。
示例性的，若授权请求承载于PDU会话建议消息或PDU会话修改消息中，终端可以向SMF发送授权请求，由SMF将该授权请求或该授权请求中的信息转发给UTM，或者SMF还可以将授权请求中的信息解析出来，自行生成一个新的消息，发送给UTM，该新的消息用来向UTM请求授权。
示例性的，若授权请求承载于NAS消息中，终端可以向AMF发送指示信息或授权请求，由AMF将该授权请求或授权请求中的信息转发给UTM，或AMF根据对授权请求的解析，生成新的消息发送给UTM，该新的消息用来向UTM请求对终端的授权，例如请求授权该终端使用无人机功能或使用无人机控制器功能。
在本申请实施例中，终端可以通过不同的核心网网元向UTM请求授权，也可以在不同的流程中发送授权请求。无人机系统通过核心网网元与网络交互，解决了无人机系统的网络授权和匹配问题，进一步地可以使无人机控制器和无人机通过网络进行通讯，实现远距离通信。
作为再一个示例，UTM可以不从核心网网元处接收终端对应的授权请求，而可以直 接接收该终端发送的授权请求，也就是终端可以直接单独发起授权请求流程。下面结合图4进行详细描述。
图4示出了本申请实施例的无线网络通信方法的示意性流程图。该方法可以包括步骤S410至步骤S430。
在步骤S410，终端向无人机流量管理实体发送授权请求。
在该步骤中，可以理解为终端向UTM透传该授权请求。
应理解，所述终端可以为无人机控制器或无人机，授权请求中可以包括上文提到的授权请求中可以包括的信息中的一种或多种，具体可参见上文中对授权请求的描述，为简洁，在此不再赘述。
在步骤S420，无人机流量管理实体向统一数据管理UDM请求关于该终端的签约信息，以获取用于授权的数据。
该步骤为可选步骤，UTM获取用于授权的数据可以有多种方式，换句话说，UTM生成授权响应可以有多种方式。
作为一种可能的实现方式，UTM可以根据授权请求中的信息，例如终端请求控制的无人机标识列表或请求匹配的无人机控制器标识列表，或终端的相关信息，生成授权响应。
作为另一种可能的实现方式，UTM可以根据终端的签约信息生成授权响应。例如，若签约信息中没有无人机控制器(或无人机)功能的相关信息，则授权响应中拒绝终端使用无人机控制器(或无人机)功能；若签约信息中有无人机控制器(或无人机)功能相关信息，则UTM可以确定允许无人机控制器控制的无人机信息(或允许无人机进行匹配的无人机控制器的信息)等，并包含在授权响应中。
作为再一种可能的实现方式，UTM可以根据本地配置信息生成授权响应。
作为又一种可能的实现方式，UTM可以根据授权请求中的信息、终端的签约信息或UTM的本地配置信息中的一种或多种，生成授权响应。
在步骤S430，无人机流量管理实体向该终端发送授权响应。
在该步骤中，可以理解为UTM向终端透传该授权响应。
终端向UTM发送的授权请求和终端接收UTM发送的授权请求可以承载于现有的消息信令中，也可以承载于新增的消息或信令中，该现有的或新增的消息信令可以是终端直接向UTM发送的。
需要说明的是，步骤S420也可以应用于在图3所示的无线通信方法，其可以在步骤S320后执行。
应理解，该授权响应中可以包括上文提到的授权响应可以包括的信息中的一种或多种，具体参见上文中对授权响应的描述，为简洁，在此不再赘述。
本申请实施例中，通过终端与UTM的直接交互，解决了无人机控制器获得授权控制无人机的问题或无人机与无人机控制器匹配的问题，从而可以使无人机控制器和无人机能够通过网络进行通信，有利于实现无人机控制器对无人机的远距离控制。
上文中提到终端还可以在进行注册的过程中向网络请求授权，下面将结合图5的实施例进行描述。
图5示出了本申请实施例的无线网络通信方法的示意性流程图。该方法可以包括步骤S510至步骤S550。
示例性的，在该实施例中，核心网网元可以为AMF网元。
在步骤S510，终端向AMF网元发送注册请求。
可选地，该注册请求中可以包括功能指示信息。对于终端可以具有无人机控制器功能时，该指示信息可以指示该终端请求控制无人机或请求使用无人机控制器功能；对于终端可以具有无人机功能时，该指示信息可以指示该终端请求具有无人机功能或该终端请求与无人机控制器进行匹配。
可选地，该功能指示信息可以承载于NAS消息中，与注册请求并列。
可选地，该注册请求可以承载于NAS消息中，该NAS消息中还包括终端的授权请求，该授权请求与注册请求并列。
可选地，注册请求和授权请求可以承载于NAS消息中，授权请求还可以包括功能指示信息。
作为一种可能的实现方式，在步骤S510中，终端还可以向AMF网元发送该终端请求授权的信息或该终端的相关信息。
示例性的，对于终端请求授权使用无人机控制器功能时，终端还可以向AMF网元发送终端请求控制的无人机的标识或标识列表，或其他可以用于确定或唯一识别无人机的信息；对于终端请求授权使用无人机功能时，终端还可以向AMF网元发送终端期望匹配的无人机控制器的标识或标识列表，或其他可以用于确定或唯一识别无人机控制器的信息。
示例性的，对于终端请求授权使用无人机控制器功能时，终端还可以向AMF网元发送无人机控制器的信息或相关数据，这里的相关数据可以是上文提到的无人机控制器信息中的部分或全部，或其他未列出的与无人机控制器相关的信息；对于终端请求授权使用无人机功能时，终端还可以向AMF网元发送无人机的信息或相关数据，这里的相关数据可以是上文提到的无人机信息中的部分或全部，或其他未列出的与无人机相关的信息。
可选地，该终端请求授权的信息或该终端的相关信息可以承载于注册请求、授权请求、NAS消息或其他消息的一种或几种中。
在步骤S520中，AMF网元向UTM发送授权请求。
授权请求的形式和内容可以有多种可能的方式，作为示例而非限定，下面列举几种可能的实现方式。
可选地，该授权请求可以是终端发送给AMF的授权请求。例如，AMF将终端发送的授权请求转发给UTM。
可选地，该授权请求可以是由AMF生成，授权请求中可以包括终端发送给AMF的信息。例如，AMF将终端发送的用于授权的信息解析后，生成包含上述信息的授权请求。
可选地，该授权请求可以是由AMF生成，授权请求中的用于请求授权的信息可以是由AMF生成的。例如，AMF接收到终端发送的指示信息后，可以自行生成其他用于请求授权的信息，该信息与指示信息的形式可以是不同的，但是内容可以是用于请求网络授权的信息。
在步骤S530，UTM接收到授权请求后，向UDM请求关于该终端的签约信息，以获取用于授权的数据。
作为另一种可能的实现方式，获取用于授权的相关数据可以通过UTM的本地配置信息获取。
在步骤S540，UTM向AMF发送授权响应。
当该终端请求授权使用无人机控制器功能时，该授权响应用于指示是否允许该终端控制无人机，或指示授权该终端使用无人机控制器功能；或该终端请求授权使用无人机功能，该授权响应用于指示是否允许该终端与无人机控制器进行匹配，或指示授权该终端使用无人机功能。
该授权响应的生成方式有多种，作为示例而非限定，下面以终端为无人机控制器为例进行说明。
作为一种示例，UTM可以根据AMF发送的授权请求中的信息生成该授权响应。
例如，该授权请求中包括终端请求控制无人机的指示信息，UTM可以在授权响应中拒绝终端控制无人机，或允许或确认该终端可以控制无人机。
又如，该授权请求中包括终端请求控制的无人机信息，如无人机标识或标识列表等，UTM可以根据该无人机的信息，在授权响应中拒绝该终端控制无人机，或允许确认该终端控制无人机，或在授权响应中包括允许该终端控制的无人机的相关信息，例如允许该终端控制的无人机标识或标识列表。该无人机的标识或标识列表可以是在授权请求中包括的终端请求控制的无人机信息中选择的一部分，也可以是全部。
作为另一种示例，UTM可以根据签约信息或本地配置信息生成该授权响应。
例如，该授权请求中可以包括终端请求控制无人机的指示信息，UTM可以根据签约信息或本地配置信息确定允许该终端控制的无人机的相关信息，例如允许终端控制的无人机标识或标识列表等，或若签约信息或本地配置信息中没有该终端的无人机控制器相关的信息，UTM可以在授权响应中拒绝该终端使用无人机控制器功能。
作为再一种示例，UTM可以根据授权请求中的信息、签约信息或本地配置信息中的多种生成该授权响应。
例如，授权请求中可以包括终端请求控制的无人机信息，如无人机标识或标识列表等，UTM可以根据该信息和该终端的签约信息，确定是否允许该终端控制其请求控制的无人机；或确定其请求控制的无人机中，哪些无人机可以被该终端控制；或为该终端重新确定允许该终端控制的无人机。
可选地，当UTM允许该终端具有无人机控制器功能时，还可以为该终端和该终端可以控制的无人机所构成的无人机系统分配标识符，并将其包含在授权响应中。该标识符可以用于多播场景，例如，网络可以同时通知该无人机系统中的多个无人机或无人机控制器所属的无人机系统。
应理解，上述示例仅以终端为无人机控制器为例进行说明，对于终端为无人机的情况，上述示例性方法同样适用，为简洁，在此不再赘述。
可选地，当UTM对终端授权成功，该UTM还可以保存该终端的信息。例如，当AMF发送给UTM的授权请求中包括该终端的相关数据时，授权成功后，UTM可以保存该终端的相关数据，如保存无人机控制器或无人机的标识符、位置、拥有者地址和联系方式等，该终端的相关数据可参见上文所述。
在步骤S550，AMF向终端发送注册响应。
AMF接收到授权响应后，确定是否允许该终端注册到网络，例如3GPP网络。
应理解，本申请实施例中的注册不仅仅限定于终端成功注册到网络，还包括终端获得 UTM的授权，也可以理解为终端注册到UTM。
该注册响应可以指示拒绝该终端注册，也可指示该终端注册成功。
该终端生成注册响应的方式有多种，作为示例而非限定，下面举例说明。
作为一种可能的实现方式，当因鉴权失败等原因导致终端无法注册到网络，AMF可以在注册响应中包括拒绝终端的注册的信息。
作为另一种可能的实现方式，AMF可以根据授权响应中的信息或本地配置信息生成注册响应。
例如，若授权响应中允许终端使用无人机控制器功能或无人机功能，AMF可以在注册响应中回应该终端注册成功。该注册响应中还可以包括授权响应中包括的信息，例如允许该终端控制的无人机的信息或无人机系统的标识等。
例如，若授权响应中不允许终端使用无人机控制器功能或无人机功能，AMF可以根据本地配置信息选择在注册响应中回应该终端注册成功，并指示终端不允许使用无人机控制功能或无人机功能；或AMF可以直接在授权响应中拒绝该终端注册。
作为又一种可能的实现方式，AMF还可以根据注册请求中的信息、授权请求中的信息或本地配置信息生成注册响应。下面以终端为无人机控制器为例说明。
例如，若注册请求中没有指示终端是否仅仅用于控制无人机，且授权响应中允许终端控制无人机，AMF可以在注册响应中回应终端注册成功；AMF还可以将接收到的授权响应中的信息发送给终端。
例如，若注册请求中没有指示终端是否仅仅用于控制无人机，且授权响应中不允许终端控制无人机，AMF可以根据本地配置信息在注册响应中回应终端注册成功，并指示终端不允许控制无人机；或AMF直接在注册响应中拒绝该终端注册。
又如，若注册请求中指示终端仅仅用于控制无人机，且授权响应中不允许UE控制无人机，AMF可以在注册响应中拒绝该终端注册。
又如，注册请求中指示终端仅仅用于控制无人机，且授权响应中允许终端控制无人机，AMF可以在注册响应中回应终端注册成功；AMF还可以将接收到的授权响应中的信息发送给终端。
再如，若注册请求中指示终端不仅用于控制无人机，且授权响应中不允许UE控制无人机，AMF在注册响应中回应终端注册成功，并指示终端不允许控制无人机。
再如，若注册请求中指示终端不仅用于控制无人机，且授权响应中允许终端控制无人机，AMF在注册响应中回应终端注册成功；AMF还可以将接收到的授权响应中的信息发送给终端。
可选地，可以通过多种形式的指示信息来指示终端是否仅仅用于控制无人机，例如用比特1(或0)表示终端仅用于控制无人机，或通过其他方式指示，本申请实施例不做任何限定。
可选地，当授权响应中允许终端控制无人机时，AMF可以在注册响应中指示是否允许终端控制其请求控制的无人机。
应理解，当授权成功时，AMF可以将授权响应包括在注册响应中发送给终端，也可以将授权响应单独发送给终端，本申请实施例中AMF向终端发送注册响应可以包括上述两种或其他的形式。
终端在注册流程中向网络请求授权，解决了终端如何与网络交互获得授权控制无人机的问题以及无人机控制器与无人机匹配的问题，有利于实现无人机控制器与无人机的远距离通信。
进一步地，无人机控制器在注册流程中提供是否仅用于控制无人机的指示信息，核心网网元可以根据该指示信息与授权响应确定是否允许无人机控制器注册，解决了网络侧如何处理不同类型的无人机控制器的注册问题。
可选地，该核心网网元也可以是其他的网元或设备。
示例性的，终端可以向核心网网元发送第一信息；终端接收核心网网元发送的第二信息，其中第一信息用于请求授权该终端对无人机进行控制，第二信息用于指示是否允许该终端对无人机进行控制；或者第一信息用于请求授权该终端与无人机控制器进行匹配，第二信息用于指示是否允许该终端与无人机控制器进行匹配。该核心网网元可以与其他核心网网元进行交互，或者与UTM交互。第二信息中的信息可以是核心网网元从其他核心网网元或UTM接收后转发给终端的，也可以是该核心网网元生成的。
上文中结合图1至图5，详细描述了本申请实施例的方法实施例，下面将结合图6至图13，详细描述本申请实施例的装置实施例。应理解，方法实施例的描述与装置实施例的描述相互对应，因此，未详细描述的部分可以参见前面方法实施例。
图6是本申请实施例提供的网络设备的示意性结构图。图6的网络设备600可以是上文提及的无人机流量管理实体，例如图2所示的UTM203。网络设备600可用于实现上文中的由无人机流量管理实体执行的步骤，如图3至图5所示的方法中无人机流量管理实体所执行的步骤。网络设备600包括接收模块610和发送模块620。
接收模块610用于接收授权请求；
发送模块620用于发送授权响应；
其中，终端具有无人机控制器功能，该授权请求用于请求授权终端对无人机进行控制，该授权响应用于指示是否允许该终端对该无人机进行控制；或者，终端具有无人机功能，该授权请求用于请求授权终端与无人机控制器进行匹配，该授权响应用于指示是否允许该终端与该无人机控制器进行匹配。
可选地，该接收模块610用于从该终端接收该授权请求。
可选地，该发送模块620用于向该终端发送该授权响应。
可选地，该接收模块610用于从接入和移动性管理功能网元AMF接收该授权请求。
可选地，该发送模块620用于向接入和移动性管理功能网元AMF发送该授权响应。
可选地，该第一接收模块610用于从会话管理功能网元SMF接收该授权请求。
可选地，该第一发送模块620用于向会话管理功能网元SMF发送该授权响应。
可选地，网络设备600还可包括：生成模块，用于该网络设备600根据该授权请求中的信息、该终端的签约信息以及该无人机流量管理实体的本地配置信息中的一种或多种，生成该授权响应。
可选地，该授权请求包括该终端请求控制的无人机的标识。
可选地，该授权请求包括该终端请求匹配的无人机控制器的标识。
可选地，该授权响应包括允许该终端控制的无人机的标识。
可选地，该授权响应包括允许该终端匹配的无人机控制器的标识。
可选地，该授权响应包括允许匹配的无人机和无人机控制器所构成的无人机系统的标识。
图7是本申请一个实施例提供的通信装置的示意性结构图。图7所示的通信装置700可对应于前文描述的无人机流量管理实体。通信装置700可包括：至少一个处理器710和通信接口720，该通信接口720可用于该通信装置700与其他通信装置进行信息交互，当程序指令在该至少一个处理器710中执行时，使得该通信装置700实现前文中的由无人机流量管理实体执行的各个步骤或方法或操作或功能。
图8是本申请实施例提供的终端的示意性结构图。图8的终端800可以是上文提及的终端，例如图1所示的UE101，图2所示的UAV控制201或UAV202。终端800可用于实现上文中如图4所示的方法中由终端执行的步骤。终端800可以发送模块810和接收模块820。
发送模块810用于向无人机流量管理实体发送授权请求；
接收模块820用于从该无人机流量管理实体接收授权响应；
其中，该授权请求用于请求授权该终端对无人机进行控制，该授权响应用于指示是否允许该终端对该无人机进行控制；或者，该授权请求用于请求授权该终端与无人机控制器进行匹配，该授权响应用于指示是否允许该终端与该无人机控制器进行匹配。
可选地，该授权请求包括该终端请求控制的无人机的标识。
可选地，该授权请求包括该终端请求匹配的无人机控制器的标识。
可选地，该授权响应包括允许该终端控制的无人机的标识。
可选地，该授权响应包括允许该终端匹配的无人机控制器的标识。
可选地，该授权响应包括允许匹配的无人机和无人机控制器所构成的无人机系统的标识。
图9是本申请一个实施例提供的通信装置的示意性结构图。图9所示的通信装置900可对应于前文描述的终端。通信装置900可包括：至少一个处理器910和通信接口920，该通信接口920可用于该通信装置900与其他通信装置进行信息交互，当程序指令在该至少一个处理器910中执行时，使得该通信装置900实现前文中的由终端执行的各个步骤或方法或操作或功能。
图10是本申请实施例提供的终端的示意性结构图。图10的终端1000可以是上文提及的终端，例如图1所示的UE101，图2所示的UAV控制201或UAV202。终端1000可用于实现上文中例如图5所示的方法中由终端执行的步骤。终端1000包括发送模块1010和接收模块1020。
发送模块1010用于在终端的注册过程中，向接入和移动性管理功能网元AMF发送指示信息；
接收模块1020用于从该AMF接收注册响应；
其中，该指示信息用于指示该终端期望对无人机进行控制，该注册响应用于指示是否允许该终端对该无人机进行控制；或者，该指示信息用于指示该终端期望与无人机控制器进行匹配，该注册响应用于指示是否允许该终端与该无人机控制器进行匹配。
可选地，发送模块1010用于向该AMF发送该终端请求控制的无人机的标识。
可选地，发送模块1010用于向该AMF发送该终端请求匹配的无人机控制器的标识。
可选地，当该AMF确定不允许该终端控制无人机时，该注册响应用于拒绝该终端进行注册。
可选地，当该AMF确定不允许该终端控制无人机时，该注册响应用于指示该终端注册成功，且指示该终端不允许控制该无人机。
可选地，当该AMF确定允许该终端控制无人机时，该注册响应用于指示该终端注册成功，且指示该终端允许控制该无人机。
可选地，该指示信息还用于指示该终端是否仅用于控制无人机，当该指示信息指示该终端仅用于控制无人机，且该AMF确定不允许该终端控制无人机时，该注册响应用于拒绝该终端进行注册；或，当该指示信息指示该终端不仅仅用于控制无人机，且该AMF确定不允许该终端控制无人机时，该注册响应用于指示该终端注册成功，且指示该终端不允许控制无人机。
可选地，该注册响应包括允许该终端控制的无人机的标识。
可选地，该注册响应包括允许该终端匹配的无人机控制器的标识。
可选地，该注册响应包括允许匹配的无人机和无人机控制器所构成的无人机系统的标识。
图11是本申请一个实施例提供的通信装置的示意性结构图。图11所示的通信装置1100可对应于前文描述的终端。通信装置1100可包括：至少一个处理器1110和通信接口1120，该通信接口1120可用于该通信装置1100与其他通信装置进行信息交互，当程序指令在该至少一个处理器1110中执行时，使得该通信装置1100实现前文中的由终端执行的各个步骤或方法或操作或功能。
图12是本申请实施例提供的网络设备示意性结构图。图12的网络设备1200可以是上文提及的核心网网元，例如图1中的AMF网元104或SMF网元105。网络设备1200可用于实现上文中的由核心网网元执行的步骤，例如图5所示的方法中由AMF执行的步骤。网络设备1200可以包括发送模块1210和接收模块1220。
发送模块1210用于向无人机流量实体发送授权请求；
接收模块1220用于从该无人机流量实体接收授权响应；
其中，该授权请求用于请求授权终端对无人机进行控制，该授权响应用于指示是否允许该终端对该无人机进行控制；或者，该授权请求用于请求授权终端与无人机控制器进行匹配，该授权响应用于指示是否允许该终端与该无人机控制器进行匹配。
可选地，接收模块1220还用于在该核心网网元向无人机流量实体发送授权请求之前，接收该终端发送的指示信息，其中，该指示信息用于指示该终端期望对无人机进行控制；或者，该指示信息用于指示该终端期望与无人机控制器进行匹配。
可选地，网络设备1200还包括生成模块，用于根据该授权响应生成注册响应，当该授权响应指示允许该终端控制无人机时，该注册响应用于指示该终端注册成功，且指示该终端允许控制该无人机。
可选地，当该授权响应指示不允许该终端控制无人机时，该注册响应用于拒绝该终端进行注册。
可选地，当该授权响应指示不允许该终端控制无人机时，该注册响应用于指示该终端注册成功，且指示该终端不允许控制无人机。
可选地，该指示信息还用于指示该终端是否仅用于控制无人机，当该指示信息指示该终端仅用于控制无人机，且该授权响应指示不允许该终端控制无人机时，该注册响应用于拒绝该终端进行注册；或，当该指示信息指示该终端不仅仅用于控制无人机，且该授权响应指示不允许该终端控制无人机时，该注册响应用于指示该终端注册成功，且指示该终端不允许控制无人机。
可选地，该核心网网元为接入和移动性管理功能网元AMF或会话管理功能网元SMF。
可选地，接收模块1220还用于从该终端接收该终端请求控制的无人机的标识。
可选地，接收模块1220还用于从该终端接收该终端请求匹配的无人机控制器的标识。
可选地，该授权请求包括该终端请求控制的无人机的标识。
可选地，该授权请求包括该终端请求匹配的无人机控制器的标识。
可选地，该授权响应包括允许该终端控制的无人机的标识。
可选地，该授权响应包括允许该终端匹配的无人机控制器的标识。
可选地，该授权响应包括允许匹配的无人机和无人机控制器所构成的无人机系统的标识。
图13是本申请一个实施例提供的通信装置的示意性结构图。图13所示的通信装置1300可对应于前文描述的核心网网元。通信装置1300可包括：至少一个处理器1310和通信接口1320，该通信接口1320可用于该通信装置1300与其他通信装置进行信息交互，当程序指令在该至少一个处理器1310中执行时，使得该通信装置1300实现前文中的由核心网网元执行的各个步骤或方法或操作或功能。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现 有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(read-only memory，ROM)、随机存取存储器(random access memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (35)

  1. 一种无线网络通信方法，其特征在于，包括：
    无人机流量管理实体接收授权请求；
    所述无人机流量管理实体发送授权响应；
    其中，所述授权请求用于请求授权终端对无人机进行控制，所述授权响应用于指示是否允许所述终端对所述无人机进行控制；或者，
    所述授权请求用于请求授权终端与无人机控制器进行匹配，所述授权响应用于指示是否允许所述终端与所述无人机控制器进行匹配。
  2. 根据权利要求1所述的方法，其特征在于，所述无人机流量管理实体接收授权请求，包括：
    所述无人机流量管理实体从所述终端接收所述授权请求；
    所述无人机流量管理实体发送授权响应，包括：
    所述无人机流量管理实体向所述终端发送所述授权响应。
  3. 根据权利要求1所述的方法，其特征在于，所述无人机流量管理实体接收授权请求，包括：
    所述无人机流量管理实体从接入和移动性管理功能网元AMF或会话管理功能网元SMF接收所述授权请求；
    所述无人机流量管理实体发送授权响应，包括：
    所述无人机流量管理实体向所述AMF或所述SMF发送所述授权响应。
  4. 根据权利要求1至3中任一项所述的方法，其特征在于，还包括：
    所述无人机流量管理实体根据所述授权请求中的信息、所述终端的签约信息以及所述无人机流量管理实体的本地配置信息中的一种或多种，生成所述授权响应。
  5. 根据权利要求1至4中任一项所述的方法，其特征在于，所述授权请求包括所述终端请求控制的无人机的标识；或者，所述授权请求包括所述终端请求匹配的无人机控制器的标识。
  6. 根据权利要求1至5中任一项所述的方法，其特征在于，所述授权响应包括允许所述终端控制的无人机的标识；或者，所述授权响应包括允许所述终端匹配的无人机控制器的标识。
  7. 一种无线网络通信方法，其特征在于，包括：
    终端向无人机流量管理实体发送授权请求；
    所述终端从所述无人机流量管理实体接收授权响应；
    其中，所述授权请求用于请求授权所述终端对无人机进行控制，所述授权响应用于指示是否允许所述终端对所述无人机进行控制；或者，
    所述授权请求用于请求授权所述终端与无人机控制器进行匹配，所述授权响应用于指示是否允许所述终端与所述无人机控制器进行匹配。
  8. 根据权利要求7所述的方法，其特征在于，所述授权请求包括所述终端请求控制的无人机的标识；或者，所述授权请求包括所述终端请求匹配的无人机控制器的标识。
  9. 根据权利要求7或8所述的方法，其特征在于，所述授权响应包括允许所述终端控制的无人机的标识；或者，所述授权响应包括允许所述终端匹配的无人机控制器的标识。
  10. 一种无线网络通信方法，其特征在于，包括：
    在终端的注册过程中，所述终端向接入和移动性管理功能网元AMF发送指示信息；
    所述终端从所述AMF接收注册响应；
    其中，所述指示信息用于指示所述终端请求对无人机进行控制，所述注册响应用于指示是否允许所述终端对所述无人机进行控制；或者，
    所述指示信息用于指示所述终端请求与无人机控制器进行匹配，所述注册响应用于指示是否允许所述终端与所述无人机控制器进行匹配。
  11. 根据权利要求10所述的方法，其特征在于，还包括：
    所述终端向所述AMF发送所述终端请求控制的无人机的标识；或者，
    所述终端向所述AMF发送所述终端请求匹配的无人机控制器的标识。
  12. 根据权利要求10或11所述的方法，其特征在于，当所述AMF确定不允许所述终端控制无人机时，所述注册响应用于拒绝所述终端进行注册。
  13. 根据权利要求10或11所述的方法，其特征在于，当所述AMF确定不允许所述终端控制无人机时，所述注册响应用于指示所述终端注册成功，且指示不允许所述终端控制无人机。
  14. 根据权利要求10至13中任一项所述的方法，其特征在于，当所述AMF确定允许所述终端控制无人机时，所述注册响应用于指示所述终端注册成功，且指示允许所述终端控制无人机，和/或指示是否允许所述终端控制所述无人机。
  15. 根据权利要求10至14中任一项所述的方法，其特征在于，所述指示信息还用于指示所述终端是否仅用于控制无人机，
    当所述指示信息指示所述终端仅用于控制无人机，且所述AMF确定不允许所述终端控制无人机时，所述注册响应用于拒绝所述终端进行注册；或，
    当所述指示信息指示所述终端不仅仅用于控制无人机，且所述AMF确定不允许所述终端控制无人机时，所述注册响应用于指示所述终端注册成功，且指示不允许所述终端控制无人机。
  16. 根据权利要求10至15中任一项所述的方法，其特征在于，所述注册响应包括允许所述终端控制的无人机的标识；或者，所述注册响应包括允许所述终端匹配的无人机控制器的标识。
  17. 一种无线网络通信方法，其特征在于，包括：
    核心网网元向无人机流量管理实体发送授权请求；
    所述核心网网元从所述无人机流量管理实体接收授权响应；
    其中，所述授权请求用于请求授权终端对无人机进行控制，所述授权响应用于指示是否允许所述终端对所述无人机进行控制；或者，
    所述授权请求用于请求授权终端与无人机控制器进行匹配，所述授权响应用于指示是否允许所述终端与所述无人机控制器进行匹配。
  18. 根据权利要求17所述的方法，其特征在于，在所述核心网网元向无人机流量管理实体发送授权请求之前，还包括：
    接收所述终端发送的指示信息；
    其中，所述指示信息用于指示所述终端请求对无人机进行控制；或者，
    所述指示信息用于指示所述终端请求与无人机控制器进行匹配。
  19. 根据权利要求17或18所述的方法，其特征在于，还包括：
    所述核心网网元根据所述授权响应生成注册响应，其中
    当所述授权响应指示允许所述终端控制无人机时，所述注册响应用于指示所述终端注册成功，且指示允许所述终端控制无人机，和/或指示是否允许所述终端控制所述无人机。
  20. 根据权利要求17至19中任一项所述的方法，其特征在于，
    当所述授权响应指示不允许所述终端控制无人机时，所述注册响应用于拒绝所述终端进行注册。
  21. 根据权利要求17至19中任一项所述的方法，其特征在于，
    当所述授权响应指示不允许所述终端控制无人机时，所述注册响应用于指示所述终端注册成功，且指示不允许所述终端控制无人机。
  22. 根据权利要求17至21中任一项所述的方法，其特征在于，所述指示信息还用于指示所述终端是否仅用于控制无人机，
    当所述指示信息指示所述终端仅用于控制无人机，且所述授权响应指示不允许所述终端控制无人机时，所述注册响应用于拒绝所述终端进行注册；或
    当所述指示信息指示所述终端不仅仅用于控制无人机，且所述授权响应指示不允许所述终端控制无人机时，所述注册响应用于指示所述终端注册成功，且指示不允许所述终端控制无人机。
  23. 根据权利要求17至22中任一项所述的方法，其特征在于，所述核心网网元为接入和移动性管理功能网元AMF或会话管理功能网元SMF。
  24. 根据权利要求17至23中任一项所述的方法，其特征在于，还包括：
    所述核心网网元从所述终端接收所述终端请求控制的无人机的标识；或者
    所述核心网网元从所述终端接收所述终端请求匹配的无人机控制器的标识。
  25. 根据权利要求17至24中任一项所述的方法，其特征在于，所述授权请求包括所述终端请求控制的无人机的标识；或者，
    所述授权请求包括所述终端请求匹配的无人机控制器的标识。
  26. 根据权利要求17至25中任一项所述的方法，其特征在于，所述授权响应包括允许所述终端控制的无人机的标识；或者，
    所述授权响应包括允许所述终端匹配的无人机控制器的标识。
  27. 一种无线网络通信方法，其特征在于，包括：
    终端向无人机流量管理实体发送授权请求；
    所述无人机流量管理实体向所述终端发送授权响应；
    其中，所述授权请求用于请求授权所述终端对无人机进行控制，所述授权响应用于指示是否允许所述终端对所述无人机进行控制；或者，
    所述授权请求用于请求授权所述终端与无人机控制器进行匹配，所述授权响应用于指示是否允许所述终端与所述无人机控制器进行匹配。
  28. 一种无线网络通信方法，其特征在于，包括：
    终端向核心网网元发送第一信息；
    所述核心网网元向所述终端发送第二信息；
    其中所述第一信息用于请求授权所述终端对无人机进行控制，所述第二信息用于指示是否允许所述终端对所述无人机进行控制；或者，
    所述第一信息用于请求授权所述终端与无人机控制器进行匹配，所述第二信息用于指示是否允许所述终端与所述无人机控制器进行匹配。
  29. 一种无线网络通信方法，其特征在于，包括：
    核心网网元向无人机流量管理实体发送授权请求；
    所述无人机流量管理实体向所述核心网网元发送授权响应；
    其中，所述授权请求用于请求授权所述终端对无人机进行控制，所述授权响应用于指示是否允许所述终端对所述无人机进行控制；或者，
    所述授权请求用于请求授权所述终端与无人机控制器进行匹配，所述授权响应用于指示是否允许所述终端与所述无人机控制器进行匹配。
  30. 一种网络设备，其特征在于，包括用于执行如权利要求1至6中任一项所述的方法的模块。
  31. 一种终端，其特征在于，包括用于执行如权利要求7至16中任一项所述的方法的模块。
  32. 一种网络设备，其特征在于，包括用于执行如权利要求17至26中任一项所述的方法的模块。
  33. 一种通信系统，其特征在于，包括终端和无人机流量管理实体，
    所述终端用于向所述无人机流量管理实体发送授权请求；
    所述无人机流量管理实体用于向所述终端发送授权响应；
    其中，所述授权请求用于请求授权所述终端对无人机进行控制，所述授权响应用于指示是否允许所述终端对所述无人机进行控制；或者，
    所述授权请求用于请求授权所述终端与无人机控制器进行匹配，所述授权响应用于指示是否允许所述终端与所述无人机控制器进行匹配。
  34. 一种通信系统，其特征在于，包括终端和核心网网元，
    所述终端用于向所述核心网网元发送第一信息；
    所述核心网网元用于向所述终端发送第二信息；
    其中所述第一信息用于请求授权所述终端对无人机进行控制，所述第二信息用于指示是否允许所述终端对所述无人机进行控制；或者，
    所述第一信息用于请求授权所述终端与无人机控制器进行匹配，所述第二信息用于指示是否允许所述终端与所述无人机控制器进行匹配。
  35. 一种通信系统，其特征在于，包括核心网网元和无人机流量管理实体，
    所述核心网网元用于向所述无人机流量管理实体发送授权请求；
    所述无人机流量管理实体用于向所述核心网网元发送授权响应；
    其中，所述授权请求用于请求授权所述终端对无人机进行控制，所述授权响应用于指示是否允许所述终端对所述无人机进行控制；或者，
    所述授权请求用于请求授权所述终端与无人机控制器进行匹配，所述授权响应用于指 示是否允许所述终端与所述无人机控制器进行匹配。
PCT/CN2020/070443 2019-01-11 2020-01-06 无线网络通信方法、网络设备和终端 WO2020143569A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP20738073.4A EP3902304A4 (en) 2019-01-11 2020-01-06 WIRELESS NETWORK COMMUNICATION METHOD, NETWORK DEVICE AND TERMINAL
US17/372,958 US20210345117A1 (en) 2019-01-11 2021-07-12 Wireless Network Communication Method, Network Device, and Terminal

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910028742.8A CN111436050B (zh) 2019-01-11 2019-01-11 无线网络通信方法、网络设备和终端
CN201910028742.8 2019-01-11

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/372,958 Continuation US20210345117A1 (en) 2019-01-11 2021-07-12 Wireless Network Communication Method, Network Device, and Terminal

Publications (1)

Publication Number Publication Date
WO2020143569A1 true WO2020143569A1 (zh) 2020-07-16

Family

ID=71520435

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/070443 WO2020143569A1 (zh) 2019-01-11 2020-01-06 无线网络通信方法、网络设备和终端

Country Status (4)

Country Link
US (1) US20210345117A1 (zh)
EP (1) EP3902304A4 (zh)
CN (1) CN111436050B (zh)
WO (1) WO2020143569A1 (zh)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021041214A1 (en) * 2019-08-23 2021-03-04 Idac Holdings, Inc. Methods and apparatuses for unmanned aerial system (uas) identification, binding and pairing
WO2022022837A1 (en) * 2020-07-31 2022-02-03 Nokia Technologies Oy Method, apparatus and computer program for enabling a communication session
WO2022029635A1 (en) * 2020-08-03 2022-02-10 Lenovo (Singapore) Pte. Ltd. Authorizing and configuring pairing of unmanned aerial system
WO2022260569A1 (en) * 2021-06-07 2022-12-15 Telefonaktiebolaget Lm Ericsson (Publ) Methods for uav communications over sidelink
EP4090061A4 (en) * 2020-12-14 2023-04-26 Guangdong Oppo Mobile Telecommunications Corp., Ltd. WIRELESS COMMUNICATION METHOD, TERMINAL DEVICE AND NETWORK ELEMENT

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113613234A (zh) * 2019-02-19 2021-11-05 华为技术有限公司 一种策略管理的方法及装置
WO2022126329A1 (zh) * 2020-12-14 2022-06-23 Oppo广东移动通信有限公司 目标信息获取方法、发送方法、装置、设备及存储介质
CN115996393A (zh) * 2021-10-19 2023-04-21 华为技术有限公司 一种通信方法及通信装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105025014A (zh) * 2015-06-18 2015-11-04 顺丰科技有限公司 无人机启用方法、系统及装置
CN105225540A (zh) * 2015-10-21 2016-01-06 杨珊珊 无人飞行器的飞行区域监控装置及其监控方法
WO2018144761A1 (en) * 2017-02-01 2018-08-09 Interdigital Patent Holdings, Inc. Assurance driven mobility management

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP6423521B2 (ja) * 2015-03-31 2018-11-14 エスゼット ディージェイアイ テクノロジー カンパニー リミテッドＳｚ Ｄｊｉ Ｔｅｃｈｎｏｌｏｇｙ Ｃｏ．，Ｌｔｄ 無人航空機を制御するシステム
CN106226780B (zh) * 2016-07-26 2019-02-05 南京航空航天大学 基于激光扫描雷达的多旋翼室内定位系统及实现方法
WO2018066799A1 (ko) * 2016-10-07 2018-04-12 엘지전자(주) 무선 통신 시스템에서 세션 및 서비스 연속성 모드 선택 방법 및 이를 위한 장치
EP3602519A1 (en) * 2017-03-31 2020-02-05 Telefonaktiebolaget LM Ericsson (PUBL) Methods and systems for using network location services in a unmanned aircraft systems traffic management framework
CN108811000B (zh) * 2017-05-05 2021-02-26 华为技术有限公司 一种参数的确定方法及通信实体
CN108334108A (zh) * 2017-06-21 2018-07-27 深圳大漠大智控技术有限公司 基于软差分的无人机编队表演控制系统
US11178194B2 (en) * 2018-02-19 2021-11-16 Electronics And Telecommunications Research Institute Packet data unit session establishment method and network entity performing the same
WO2020033905A1 (en) * 2018-08-10 2020-02-13 Intel Corporation Systems and methods for using unmanned aerial systems in cellular networks

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105025014A (zh) * 2015-06-18 2015-11-04 顺丰科技有限公司 无人机启用方法、系统及装置
CN105225540A (zh) * 2015-10-21 2016-01-06 杨珊珊 无人飞行器的飞行区域监控装置及其监控方法
WO2018144761A1 (en) * 2017-02-01 2018-08-09 Interdigital Patent Holdings, Inc. Assurance driven mobility management

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
HUAWEI: "ID_UAS – enhancement on initial UAV authorization operation", 3GPP TSG-SA WG1 MEETING #83, S1-182199, 10 August 2018 (2018-08-10), XP051534676 *
RAPPORTEURQUALCOMM: "3GPP TR 22.8de V1.0.0(2018-05) 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Remote Identification of Unmanned Aerial Systems; Stage 1(Release 16)", 3GPP TSG-SA WG1 MEETING #83, S1-182355, 30 August 2018 (2018-08-30), XP051534831 *
See also references of EP3902304A4 *

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021041214A1 (en) * 2019-08-23 2021-03-04 Idac Holdings, Inc. Methods and apparatuses for unmanned aerial system (uas) identification, binding and pairing
WO2022022837A1 (en) * 2020-07-31 2022-02-03 Nokia Technologies Oy Method, apparatus and computer program for enabling a communication session
WO2022029635A1 (en) * 2020-08-03 2022-02-10 Lenovo (Singapore) Pte. Ltd. Authorizing and configuring pairing of unmanned aerial system
EP4090061A4 (en) * 2020-12-14 2023-04-26 Guangdong Oppo Mobile Telecommunications Corp., Ltd. WIRELESS COMMUNICATION METHOD, TERMINAL DEVICE AND NETWORK ELEMENT
WO2022260569A1 (en) * 2021-06-07 2022-12-15 Telefonaktiebolaget Lm Ericsson (Publ) Methods for uav communications over sidelink

Also Published As

Publication number Publication date
CN111436050A (zh) 2020-07-21
US20210345117A1 (en) 2021-11-04
EP3902304A4 (en) 2022-01-26
EP3902304A1 (en) 2021-10-27
CN111436050B (zh) 2022-04-05

Similar Documents

Publication Publication Date Title
WO2020143569A1 (zh) 无线网络通信方法、网络设备和终端
US11812490B2 (en) Method for performing communication related to packet switch (PS) data off
US20220078857A1 (en) Method for transmitting/receiving pdb-related signal in wireless communication system and device therefor
WO2020156127A1 (zh) 无线通信的方法和通信设备
US11906962B2 (en) Unmanned aerial vehicle tracking and control
US20220295337A1 (en) Operation method of ue related to pfi in wireless communication system, and apparatus therefor
WO2020220820A1 (zh) 一种建立通信承载的方法、设备及系统
US20230319634A1 (en) Traffic control
WO2022170911A1 (zh) 认证授权的方法与通信装置
EP4124122A1 (en) Communication related to network slice
US20230094211A1 (en) Support of service continuity between snpn and plmn
US20230112312A1 (en) Support of service continuity for handover between snpn and plmn
KR20220123261A (ko) Ps 데이터 오프와 관련된 통신
WO2020061907A1 (zh) 无人机飞行路径提供方法、装置及系统
WO2022156627A1 (zh) 一种无人机通信管理方法及装置
WO2020042117A1 (zh) 无人机飞行路径提供方法、获取方法、装置及系统
EP4057766A1 (en) Method and device for controlling configuration related to sidelink communication in wireless communication system
US20230084683A1 (en) Pws service method in npn
WO2022193903A1 (zh) 发现服务实体的方法和通信装置
WO2022206532A1 (zh) 一种服务质量QoS更新的方法、装置和系统
KR20220130181A (ko) 무선 통신 시스템에서 수동 폐쇄 접속 그룹 선택을 위한 방법 및 장치
US20210059003A1 (en) Method for transmitting signal relating to pdu in wireless communication system and device therefor
KR20210039737A (ko) 이동통신 네트워크에서 네트워크 간섭을 피하여 무인 항공기 경로를 설정하는 방법 및 장치
US20230189190A1 (en) Method and apparatus for communication services
WO2023065826A1 (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: 20738073

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: 2020738073

Country of ref document: EP

Effective date: 20210723