WO2021174464A1 - Procédé et dispositif d'attribution d'identité, et dispositif de communication - Google Patents

Procédé et dispositif d'attribution d'identité, et dispositif de communication Download PDF

Info

Publication number
WO2021174464A1
WO2021174464A1 PCT/CN2020/077842 CN2020077842W WO2021174464A1 WO 2021174464 A1 WO2021174464 A1 WO 2021174464A1 CN 2020077842 W CN2020077842 W CN 2020077842W WO 2021174464 A1 WO2021174464 A1 WO 2021174464A1
Authority
WO
WIPO (PCT)
Prior art keywords
uav
information
utm
message
core network
Prior art date
Application number
PCT/CN2020/077842
Other languages
English (en)
Inventor
Chenho Chin
Yang Xu
Original Assignee
Guangdong Oppo Mobile Telecommunications Corp., Ltd.
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 Guangdong Oppo Mobile Telecommunications Corp., Ltd. filed Critical Guangdong Oppo Mobile Telecommunications Corp., Ltd.
Priority to PCT/CN2020/077842 priority Critical patent/WO2021174464A1/fr
Publication of WO2021174464A1 publication Critical patent/WO2021174464A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
    • H04W8/24—Transfer of terminal data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/02—Services making use of location information
    • H04W4/029—Location-based management or tracking services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/30—Services specially adapted for particular environments, situations or purposes
    • H04W4/40—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P]
    • H04W4/44—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P] for communication between vehicles and infrastructures, e.g. vehicle-to-cloud [V2C] or vehicle-to-home [V2H]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/12—Setup of transport tunnels

Definitions

  • Embodiments of the present disclosure relate to the field of mobile communication technologies, and in particular to a method and device for allocating an identity and a communication device.
  • UAV Unmanned Aerial Vehicle
  • UAS Unmanned Aerial System
  • UVS Unmanned Aerial System
  • UAV controller e.g., a telephone number of a pilot of the drone.
  • the UAV is not just a physical aerial equipment, i.e., a piece of equipment that flies (called a flying kit) , but also User Equipment (UE) .
  • the UE is a Mobile Equipment (ME) and a User Service Identity Module (USIM) , where the ME has an International Mobile Equipment Identity (IMEI) /Permanent Equipment Identifier (PEI) .
  • IMEI International Mobile Equipment Identity
  • PEI Permanent Equipment Identifier
  • Embodiments of the present disclosure provide a method and device for allocating an identity, a communication device, a chip, a computer readable storage medium, a computer program product, and a computer program.
  • the embodiments of the present disclosure provide a method for allocating an identity (ID) , which may include the following operations.
  • An Unmanned Aerial Vehicle transmits first information to an Unmanned Aerial System Traffic Management (UTM) , here, the first information includes at least one characteristic of the UAV.
  • the UAV receives second information from the UTM, here, the second information includes a first assigned ID (or session ID) for the UAV.
  • the embodiments of the present disclosure provide a method for allocating an identity (ID) , which may include the following operations.
  • a UTM receives first information from a UAV, here, the first information includes at least one characteristic of the UAV.
  • the UTM transmits second information to the UAV, here, the second information includes a first assigned ID (or session ID) for the UAV.
  • the embodiments of the present disclosure provide a device for allocating an identity (ID) , the device is for use in a UAV, and may include a sending unit and a receiving unit.
  • ID an identity
  • the sending unit is configured to transmit first information to a UTM, here, the first information includes at least one characteristic of the UAV.
  • the receiving unit is configured to receive second information from the UTM, here, second information includes a first assigned ID (or session ID) for the UAV.
  • the embodiments of the present disclosure provide a device for allocating an identity (ID) , the device is for use in a UTM, and may include a receiving unit and a sending unit.
  • ID an identity
  • the receiving unit is configured to receive first information from a UAV, here, the first information includes at least one characteristic of the UAV.
  • the sending unit is configured to send second information to the UAV, here, second information includes a first assigned ID (or session ID) for the UAV.
  • the embodiments of the present disclosure provide a communication device, which may include a processor and a memory.
  • the memory is configured to store computer programs
  • the processor is configured to call and execute the computer programs stored in the memory, to perform the method for allocating the identity (ID) in the above embodiments.
  • the embodiments of the present disclosure provide a chip for implementing the method for allocating the identity (ID) in the above embodiments.
  • the chip may include a processor configured to call and execute computer programs in a memory, to enable a device installed with the chip to perform the method for allocating the identity (ID) in the above embodiments.
  • a processor configured to call and execute computer programs in a memory, to enable a device installed with the chip to perform the method for allocating the identity (ID) in the above embodiments.
  • the embodiments of the present disclosure provide a computer readable storage medium for storing computer programs, and the computer programs cause a computer to perform the method for allocating the identity (ID) in the above embodiments.
  • the embodiments of the present disclosure provide a computer program product including computer program instructions, and the computer programs cause a computer to perform the method for allocating the identity (ID) in the above embodiments.
  • the embodiments of the present disclosure provide a computer program that, when run on a computer, causes the computer to perform the method for allocating the identity (ID) in the above embodiments.
  • FIG. 1 is a diagram of architecture of a communication system according to the embodiments of the present disclosure.
  • FIG. 2 is a diagram of a UAS model in a 3GPP ecosystem according to the embodiments of the present disclosure.
  • FIG. 3 is a diagram of a 3GPP’s UAS reference architecture according to the embodiments of the present disclosure.
  • FIG. 4 is a flowchart of a method for allocating an identity (ID) according to the embodiments of the present disclosure.
  • FIG. 5 is a flowchart of allocation of an identity based on a registration procedure according to the embodiments of the present disclosure.
  • FIG. 6 is another flowchart of allocation of an identity based on a registration procedure according to the embodiments of the present disclosure.
  • FIG. 7 is a flowchart of allocation of an identity based on a user plane connection according to the embodiments of the present disclosure.
  • FIG. 8 is a first structural diagram of a device for allocating an identity according to the embodiments of the present disclosure.
  • FIG. 9 is a second structural diagram of a device for allocating an identity according to the embodiments of the present disclosure.
  • FIG. 10 is a structural diagram of a communication device according to the embodiments of the present disclosure.
  • FIG. 11 is a structural diagram of a chip according to the embodiments of the present disclosure.
  • FIG. 12 is a block diagram of a communication system according to the embodiments of the present disclosure.
  • the technical solutions of the embodiments of the present disclosure may be applied to various communication systems, for example, a Long Term Evolution (LTE) system, a LTE Frequency Division Duplex (FDD) system, a LTE Time Division Duplex (TDD) system, a 5 th Generation (5G) communication system or a future communication system.
  • LTE Long Term Evolution
  • FDD Frequency Division Duplex
  • TDD Time Division Duplex
  • 5G 5 th Generation
  • the technical solutions of the embodiments of the present disclosure may also be applied as enhancements to 3GPP's 4G system (such as System Architecture Evolution (SAE) /LTE) or other mobile or fixed communication systems.
  • SAE System Architecture Evolution
  • FIG. 1 is a diagram of architecture of a communication system 100 used by the embodiments of the present disclosure.
  • the communication system 100 may include a network device 110.
  • the network device 110 may be a device that communicates with a terminal 120 (or called a communication terminal or terminal) .
  • the network device 110 may provide communication coverage for a specific geographic area, and may communicate with terminals within the coverage area.
  • the network device 110 may be an Evolutional Node B (eNB or eNodeB) in an LTE system or a wireless controller in a Cloud Radio Access Network (CRAN) ; or the network device may be a mobile switching center, a relay station, an access point, a vehicle-mounted device, a wearable device, a hub, a switch, a network bridge, a router, a network-side device in a 5G network, or a network device in a future communication system etc.
  • eNB or eNodeB Evolutional Node B
  • CRAN Cloud Radio Access Network
  • the communication system 100 may also include at least one terminal 120 within the coverage of the network device 110.
  • the terminal used herein may include, but is not limited to, a device that is configured to receive/transmit communication signals via a wired connection (such as via a Public Switched Telephone Networks (PSTN) , Digital Subscriber Line (DSL) , digital cable, direct cable connection, and/or another data connection/network) and/or via a wireless interface with, for example, a cellular network, a Wireless Local Area Network (WLAN) , a Digital TV network such as Digital Video Broadcasting Handheld (DVB-H) network, a satellite network, an Amplitude Modulation (AM) -Frequency Modulation (FM) broadcast transmitter and/or another communication terminal; and an Internet of Things (IoT) device.
  • PSTN Public Switched Telephone Networks
  • DSL Digital Subscriber Line
  • WLAN Wireless Local Area Network
  • DVD-H Digital Video Broadcasting Handheld
  • AM Amplitude Modulation
  • FM Frequency Mod
  • a terminal configured to communicate over a wireless interface may be called “awireless communication terminal” , “awireless terminal” or “amobile terminal” .
  • the mobile terminal may include, but are not limited to, a satellite or cellular phone; a personal communications system (PCS) terminal that can combine a cellular radio telephone with data processing, facsimile, and data communication capabilities; a Personal Digital Assistant (PDA) that can include a radiotelephone, a pager, an Internet/intranet access, a Web browser, a notebook, calendar and/or a Global Positioning System (GPS) receiver; and a conventional laptop and/or palmtop receiver, or other electronic devices including radiotelephone transceivers.
  • PCS personal communications system
  • PDA Personal Digital Assistant
  • GPS Global Positioning System
  • the terminal may be an access terminal, User Equipment (UE) , a user unit, a user station, a mobile station, a mobile platform, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device and a user proxy or user device.
  • UE User Equipment
  • the access terminal may be a cellular phone, a cordless telephone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA) , a handheld device having a wireless communication function, a computing device or other processing devices connected to a wireless modem, a vehicle-amounted device, a wearable device, a terminal in a 5G network, or a terminal in a future evolved Public Land Mobile Network (PLMN) .
  • SIP Session Initiation Protocol
  • WLL Wireless Local Loop
  • PDA Personal Digital Assistant
  • a direct Device to Device (D2D) communication may be performed between the terminals 120.
  • D2D Device to Device
  • the 5G communication system or 5G network may also be called a New Radio (NR) system or NR network.
  • NR New Radio
  • FIG. 1 exemplarily illustrates one network device and two terminals.
  • the communication system 100 may include multiple network devices and other numbers of terminals may be within the coverage of each network device. This is not limited in the embodiments of the present disclosure.
  • the communication system 100 may further include other network entities such as a network controller, a mobility management entity and the like. This is not limited in the embodiments of the present disclosure.
  • a communication device may include a network device 110 and a terminal 120 having a communication function; and the network device 110 and the terminal 120 may be specific devices described above, and are not described herein again.
  • the communication device may also include other devices in the communication system 100, such as other network entities such as a network controller and a mobile management entity, which are not limited in the embodiments of the present disclosure.
  • system and “network” in the present disclosure are usually used interchangeably.
  • the term “and/or” in the present disclosure is only an association relationship describing associated objects and represents that three relationships may exist.
  • a and/or B may represent three conditions: i.e., independent existence of A, existence of both A and B and independent existence of B.
  • character "/" in the present disclosure usually represents that previous and next associated objects form an "or" relationship.
  • Drones or UAVs are getting more and more used, not just commercially but also by private persons. Even first responder organizations are making more use of such UAVs, e.g., to investigate an incident before sending in human personnel.
  • use of UAVs have from time to time caused disruptions to normal public way of life due to them being in air space they should not be in or being mis-operated by human owners or a host of other wrong or misguided use. Such incidents have caused general public concerns and civil aviation authorities the world over are discussing how to bring such situations under control.
  • a mobile communication system such as 3GPP's 5G system (or 3GPP's LTE/System Architecture Evolution (SAE) system, i.e., 3GPP's 4G system) could provide a cellular connectivity between the UAVs, its controllers (UAV Controllers, UAVC) and the authorities who can verify, register such UAVs, authorize their flights etc..
  • SAE System Architecture Evolution
  • UAV Controllers UAV Controllers
  • authorities can be (loosely) grouped as the UTM entity.
  • 3GPP has started work to look into providing such connectivity and 3GPP TSG SA WorkGroup 1 (a.k.a. SA1) has in 3GPP TS 22.125 put together 3GPP's Stage 1 requirements for a UAS.
  • Figure 2 illustrates a SA1's model of this UAS.
  • 3GPP TSG SA WorkGroup 2 (a.k.a. SA2) has also started its study phase into implementing 3GPP UAS and a system reference architecture for that study has been adopted and documented in TR 23.754.
  • Figure 3 illustrates the 3GPP's UAS reference architecture as extract.
  • SA1's TS 22.125 is not the only service requirements that SA2 has to consider in its system and architecture studies.
  • the FAA Federal Aviation authorities
  • the FAA has on its public website much public information.
  • the FAA has put out a set of requirements on identification of UAVs, or more precisely what UAVs must do as part of remotely providing Identification of itself.
  • ASTM F38 committee a standard (to be published as F3411) in ASTM F38 committee aiming to satisfy the growing demand for better identification and tracking of unmanned aircraft systems in airspace systems worldwide, called the Remote Identification (ID) .
  • ID Remote Identification
  • the Remote ID standard supports technology that allows the general public and public safety officials to identify a drone using an assigned ID, while preserving privacy of the operator's personal identifiable information.
  • the Remote ID outlines how drones can transmit the assigned ID, location, speed, and direction by broadcasting over the air and/or sending over a wireless internet connection to a UAS service supplier (USS) .
  • USS UAS service supplier
  • the FAA made a proposed rule regarding Remote Identification of Unmanned of Aircraft Systems.
  • This proposed rule would require a unique identifier as part of the message elements used to remotely identify a UAS.
  • a serial number is a unique number assigned to an aircraft typically at the time of production, and does not change in case of a sale or transfer of ownership.
  • the proposed revision of Part 48 would require the provision of an unmanned aircraft's serial number at the time of registration.
  • This proposed requirement is essential for the remote identification framework proposed in the Notice of Proposed Rule Making (NPRM) .
  • the serial number requirement would enable the FAA to correlate the data broadcast or transmitted by the UAS with the registration data in the Aircraft Registry to associate an unmanned aircraft with its registered owner.
  • the requirement would also allow the FAA to distinguish one unmanned aircraft from another operating in the airspace of the United States and would facilitate the identification of non-registered unmanned aircraft flying in the airspace of the United States, which may warrant additional oversight or action by the FAA, national security agencies, or law enforcement agencies.
  • the FAA is also proposing to revise ⁇ 48.100 (a) to require a serial number for every small unmanned aircraft. Consistent with the proposed changes in Part 47, ⁇ 48.100 (a) (5) would require the owner of any standard remote identification unmanned aircraft or limited remote identification unmanned aircraft to list in the Certificate of Aircraft Registration the serial number issued by the manufacturer of the unmanned aircraft in accordance with the production requirements of part 89. Per the production requirements in proposed ⁇ 89.505, such serial number would have to comply with the ANSI/CTA-2063-A serial number standard.
  • the FAA is proposing to update the registration information requirements to include one or more telephone number (s) for the applicant.
  • registration data corresponds to the owner of the unmanned aircraft rather than the operator, the FAA believes that due to the nature and scope of most small UAS operations, it is reasonable to expect a significant number of unmanned aircraft owners to also be the operators of the aircraft or in close contact with the operators of the aircraft.
  • Requiring owners of unmanned aircraft to provide their telephone number (s) as part of the registration process would assist the FAA and law enforcement to disseminate safety and security-related information to the registrant in near real-time. This additional information would be retained by the FAA and only disclosed as needed to authorized law enforcement or Federal agencies.
  • the FAA is proposing the minimum message elements necessary for the remote identification of UAS. These message elements contain the data required to meet the objectives of the proposed rule. Although the message elements are designed specifically to meet remote identification requirements, the FAA anticipates that the proposed message elements would also support future UTM services.
  • the message elements for the limited remote identification UAS would include: (1) The UAS Identification; (2) an indication of the control station's latitude and longitude; (3) an indication of the control station's barometric pressure altitude; (4) a time mark; and (5) an indication of the emergency status of the UAS.
  • the message elements for the standard remote identification UAS would include the same message elements required for the limited remote identification UAS plus (1) an indication of the unmanned aircraft's latitude and longitude, and (2) an indication of the unmanned aircraft's barometric pressure altitude.
  • the UAS Identification message element establishes the unique identity of UAS operating in the airspace of the United States. This message element would consist of one of the following:
  • a session identification number (session ID) assigned by a Remote ID USS.
  • a serial number is a unique identifier issued by the UAS producer to identify and differentiate individual aircraft.
  • the serial number is preferable as a unique identifier in a remote identification message because it would be encoded into the unmanned aircraft system during production whereas a registration number is provided to the owner of the unmanned aircraft and may change for the unmanned aircraft if the unmanned aircraft is resold.
  • a registration number is assigned by the FAA only after a UAS owner applies for one, whereas a serial number would be assigned prior to the UAS being purchased and would provide a means for the UAS to send out a remote identification message, even if it is not registered.
  • the FAA anticipates that a UAS would be designed to broadcast and transmit, as appropriate, its serial number regardless of whether the unmanned aircraft has been registered or not.
  • the FAA is proposing an option for UAS operators to be able to use a session ID assigned by a Remote ID USS as the UAS Identification, instead of the unmanned aircraft serial number. This would provide a layer of operational privacy.
  • the association between a given session ID and the unmanned aircraft serial number would not be available to the public through the broadcast message. This association would be available to the issuing Remote ID USS, the FAA, and other authorized entities, such as law enforcement.
  • the FAA recognizes that there could be concerns with the transmission of the serial number from UAS conducting routine or repetitive operations. For example, some businesses operating UAS may be concerned with the collection and analysis of flight information by their competitors in a manner that reveals sensitive business practices, such as the flight profile of an individual UAS over time.
  • a session ID instead of a serial number would provide operational privacy to these operators without adversely impacting the safety and security needs of the FAA, national security agencies, and law enforcement.
  • the FAA and authorized entities would have the means to correlate the session ID to the UAS serial number and would consequently be able to correlate the UAS serial number to its registration data.
  • the FAA is proposing in ⁇ 89.310 (j) (1) to require the standard remote identification UAS to use the same remote identification message elements, including the same UAS Identification, when transmitting to a Remote ID USS and broadcasting directly from the unmanned aircraft.
  • the FAA considers that the UAS Identification should be required to be identical because a lack of consistency regarding this message element could create confusion as to who is flying in the airspace of the United States. If the broadcast message and the transmission to the Remote ID USS contain different UAS Identifications, it may potentially appear as if there are two different aircraft in the airspace instead of one in a particular location.
  • Tier 1 -Direct broadcast locally or Network publish: UAS in this tier would be required to direct broadcast both ID and tracking information so that any compatible receiver nearby can receive and decode the ID and tracking data. If a network is available, network publishing to an FAA-approved internet-based database satisfies this requirement. A UAS would fall into Tier 1 if it does not qualify for an exemption from remote identification and tracking requirements (exempt UAS are referred to as Tier 0) and does not meet the conditions for Tier 2 or Tier 3. For example, a UAS conducting most Part 107 operations would fit into Tier 1.
  • Tier 2 -Direct broadcast (locally) and Network publish UAS in this tier would be required to broadcast (locally) ID and tracking data and network publish ID and tracking data to an FAA-approved internet-based database.
  • An example of UAS that may fall into Tier 2 would be UAS that are conducting waivered operations that deviate from certain Part 107 operating rules, and where the FAA determines that Tier 2 ID and tracking are required as a condition of the waiver.
  • Tier 3 -Flight under Part 91 rules UAS in this tier would have to adhere to the rules of manned aircraft as defined in 14 CFR Part 91.
  • This tier is intended for aircraft that are integrated into the manned aircraft airspace.
  • An example of UAS that may fall into Tier 3 are those whose unmanned aircraft weighs above 55 pounds and operating BVLOS, in IFR conditions, or operating in controlled airspace.
  • the registration of the UAV or the Drone with the UTM requires a serial number of the drone (or some kind of equipment-specific numeration/identification) and [some] unique linkage to the UAVC of the drone, e.g., a telephone number of a pilot of the drone.
  • a serial number of the drone or some kind of equipment-specific numeration/identification
  • [some] unique linkage to the UAVC of the drone e.g., a telephone number of a pilot of the drone.
  • Such requirements could extend to the identifying of operators of the UAS, which could be the UAVC itself or the pilot himself/herself in the UAS of a limited size.
  • the UAV is not just a physical aerial equipment, i.e., a piece of equipment that flies (called a flying kit) , but also the UE.
  • the UE is the ME and the USIM, where the ME has the IMEI/PEI.
  • the identity of the UAV cannot be fully covered by either the serial number of the drone or the IMEI of the UE.
  • the UAV When the UAV requests to register itself with the UTM for operations (e.g., register to obtain flight allowance, authorization to operate/fly) , after authorization and security checks and when the UTM provides approval to the UAV for its operations, the UTM provides back to the UAV a registration approval indication.
  • this is thought to be a Session Identity (ID) or an Assigned Identity (ID) which the UTM and third party security organizations (such as, a police) can use to track and know of that UAV.
  • ID Session Identity
  • ID Assigned Identity
  • the UAV With the Tiered Approach to UAV needing to support Remote Identification (one of the purposes of Remote Identification is for tracking the UAV) , the UAV is required to either locally broadcast such Remote Identification or publish such Remote Identification to a data base, the latter known as Network Publishing.
  • FIG. 4 is a flowchart of a method for allocating an identity (ID) according to the embodiments of the present disclosure. As illustrated in FIG. 4, the method includes the following operations.
  • a UAV transmits first information to a UTM, and the UTM receives the first information from the UAV, here, the first information includes at least one characteristic of the UAV.
  • the first information includes at least one of the following characteristics: a serial number of the UAV or a UE identifier of the UAV. Further, optionally, the first information further includes at least one of the following characteristics: a weight of the UAV, a power class of the UAV, a type of engine of the UAV, a flight range of the UAV, a maximum attainable altitude of the UAV, onboard equipment of the UAV, or a type of communication supported by the UAV.
  • the first information which is transmitted by a sending side (e.g., UAV) to a receiving side (e.g., UTM) includes at least the identity characteristic, and can further include other characteristics presently known or in future defined.
  • the UTM transmits second information to the UAV, and the UAV receives the second information from the UTM, here, the second information includes an assigned ID for the UAV.
  • the second information includes the assigned ID for the UAV. Further, optionally, the second information further includes at least one of: an outcome of registration of the UAV or flight configuration information of the UAV. Optionally, the second information further includes at least one of: location information of a secure database or internet server where remote identification and tracking information is to be published by the UAV, or security credentials to allow access to the secure database or internet server where the remote identification and tracking information is to be published by the UAV.
  • the flight configuration information of the UAV includes at least one of: a flight plan for the UAV, a geographical area of operation by the UAV, tracking information provided by the UAV in operation, a frequency of providing tracking information by the UAV, or flight path height limits of the UAV.
  • the transmission of the first information and the second information between the UAV and the UTM may be implemented by one of the following manners.
  • the UAV transmits an uplink Non-Access Stratum (NAS) message to a core network, the uplink NAS message carries the first information, and the first information is forwarded to the UTM by the core network.
  • the UAV receives a downlink NAS message from the core network, the downlink NAS message carries the second information, and the second information is determined by the UTM and is transmitted to the core network.
  • the UTM receives the first information from the core network, and the first information is transmitted by the UAV to the core network through the uplink NAS message; the UTM transmits the second information to the core network, and the second information is transmitted by the core network to the UAV through the downlink NAS message.
  • the uplink NAS message carries a first Information Element (IE) or a first payload container, and the first IE or the first payload container is used for carrying the first information.
  • the downlink NAS message carries a second Information Element (IE) or a second payload container, and the second IE or the second payload container is used for carrying the second information.
  • the uplink NAS message carries the first IE and the downlink NAS message carries the second IE.
  • the first IE is used for carrying the first information and the second IE is used for carrying the second information.
  • the first IE and the second IE are visible to the 3GPP system (that is, the core network in the 3GPP system can obtain or process the first IE and the second IE) .
  • the first IE may be a UAV Classmark IE
  • the second IE may be a UTM Validation IE.
  • the first IE and the second IE may also be any other new IE or existing IE of the 3GPP system.
  • the technical solutions in the embodiments of the present disclosure do not limit the names used by the first IE and the second IE.
  • the uplink NAS message carries a first payload container and the downlink NAS message carries a second payload container.
  • the first payload container is used for carrying the first information
  • the second payload container is used for carrying the second information.
  • the first payload container and the second payload container are invisible or transparent to the 3GPP system (that is, the core network in the 3GPP system cannot obtain or process the first payload container and the second payload container) .
  • the implementation of the uplink NAS message and the downlink NAS message includes, but is not limited to, one of the following.
  • the uplink NAS message is a registration request message, and the downlink NAS message is a registration accept message.
  • the uplink NAS message is a service request message, and the downlink NAS is a service accept message.
  • the uplink NAS message is a registration update message
  • the downlink NAS message is a registration update accept message.
  • the uplink NAS message is a session establishment request message, and the downlink NAS message is a session establishment accept message.
  • the uplink NAS message is a session modification message
  • the downlink NAS message is a session modification accept message.
  • the UAV establishes a user plane connection with the UTM, here, the user plane connection includes a first user plane connection between the UAV and the core network and a second user plane connection between the core network and the UTM.
  • the user plane connection includes at least one of: a session, a data flow, or a bearer.
  • the UAV transmits the first information to the core network through the first user plane connection, and the first information is transmitted by the core network to the UTM through the second user plane connection.
  • the UAV receives the second information from the core network through the first user plane connection, and the second information is determined by the UTM and is transmitted to the core network by the UTM through the second user plane connection.
  • the UTM receives the first information from the core network through the second user plane connection, and the first information is transmitted by the UAV to the core network through the first user plane connection; the UTM transmits the second information to the core network through the second user plane connection, and the second information is transmitted by the core network to the UAV through the first the user plane connection.
  • the core network after the second information is transmitted by the UTM to the core network through the second user plane connection, the core network generates a profile of the UAV based on the second information.
  • first and second user planes the embodiments applies equally for the second user plane being the concatenation of the first user plane or vice versa.
  • first and second user planes can be logically one user plane.
  • the UTM transmits location information of a secure database or internet server to the UAV, and the UAV receives the location information of the secure database or internet server from the UTM; the UAV publishes remote identification and tracking information of the UAV to the secure database or internet server based on the location information.
  • the remote identification and tracking information of the UAV may include the first assigned ID of the UAV.
  • the UTM can provide an internet address of the UTM's database or UTM's approved internet database (i.e., the location information of the secure database or internet server) that the UAV uses for Remote Identification process by Direct Broadcast or Network Publishing means.
  • the address/location information of the Network Publishing database or server includes, but is not limited, an Internet Protocol (IP) address.
  • IP Internet Protocol
  • the address information can also be a FQDN (Fully Qualified Domain Name) or a Uniform Resource Locator (URL) or any text or word string that can allow the UAV to publish information that is required as part of Remote Identification process.
  • security credential for access to the secure database or internet server for Network Publishing can also be provided by the UTM to the UAV, and the UAV receives the security credential for access to the secure database or internet server for Network Publishing.
  • the UAV may obtain, through the above technical solutions in the embodiments of the present application, the first assigned ID allocated by the UTM.
  • the first assigned ID can be updated or refreshed.
  • the UTM transmits third information to the UAV, and the UAV receives the third information from the UTM, here, the third information includes a second assigned ID for the UAV; and the UAV updates the first assigned ID with the second assigned ID.
  • the UAV may obtain, through the above technical solutions in the embodiments of the present application, the location information of the secure database or internet server and the security credentials for access to such secure database or internet server, which are allocated by the UTM.
  • the location information of the secure database or internet server and the security credentials for access to such secure database or internet server can also be updated.
  • the UTM transmits the third information to the UAV, and the UAV receives the third information from the UTM, here, the third information includes at least one of: update (i.e., a new location) of the location information of the secure database or internet server where remote identification and tracking information is to be published by the UAV, or update (i.e., new security credentials) of the security credentials for access to the secure database or internet server where remote identification and tracking information is to be published by the UAV.
  • update i.e., a new location
  • update i.e., new security credentials
  • the third information is carried in at least one of: a downlink configuration update message, a registration update accept message, a service accept message, a session modification accept message, or a configuration update message. It is not even excluded that a new NAS message is specifically designed for this purpose.
  • the interaction procedure is for example a registration procedure.
  • the technical solution related to the embodiments of the present application is not limited to being implemented in the registration procedure, or can also be implemented in other procedures.
  • the embodiments of the present disclosure introduce to the registration procedure in the 3GPP system, an Information Element (IE) dedicated to transport the characteristics of the UAV, and for want of a term, this is the UAV Classmark IE.
  • IE Information Element
  • This UAV Classmark IE will be used to transport from the UAV to the UTM (which encompasses the USS) the characteristics of the UAV such as but not limited to the serial number of the UAV, the IMEI or PEI of the UE (if there is one and is required to be provided) .
  • the weight or class of the flying kit could also be part of this UAV Classmark. In this method, there is no exhaustive list of characteristics of the UAV that cannot be included in the UAV Classmark. It is even possible that the UAV includes information for the 5G system (5GS) to locate the UTM.
  • 5GS 5G system
  • the UAV Classmark can further include, for example, the weight of the drone (or its weight class) , the type of engine of the drone, the flight range of the drone, the maximum attainable altitude of the drone, onboard equipment such as detection equipment and/or video cameras of the drone, a type of communication supported by the drone.
  • This listing is by means of illustration and does not limit what can be in or added to the UAV Classmark.
  • the name UAV Classmark is but a term chosen for description in the embodiments of the present disclosure. Calling this collection of UAV characteristics by any other name is immaterial to the embodiments of the present disclosure.
  • the UTM provides back to the UAV an indication that the registration is approved.
  • this is amongst other information, an assigned identity (assigned ID) which the UTM and third party security organizations (such as, a police) can use to track and know of that UAV.
  • This Assigned ID can be transported in an IE and for want of a term, be called UTM Validation IE (or USS Validation IE) .
  • UTM Validation IE can also be used to transport the data/information that the UTM wish to send back to the registering UAV.
  • the UTM Validation IE may be, but is not limited to, the outcome of the registration of the UAV.
  • Other information can be information associated with the outcome of the registration, or other information such as the flight plan for the UAV (or UAVC) , the geographical area of operation by the UAV, tracking information that UAV has to provide while in operation, a frequency of providing such tracking information by the UAV, flight path height limits of the UAV including maximum and minimum height. What is so far indicated is not an exhaustive list which the embodiments of the present disclosure can be used to provide in the UTM Validation IE from UTM to the UAV.
  • FIG. 5 is a flowchart of allocation of an identity based on a registration procedure according to the embodiments of the present disclosure.
  • transmission of first information and second information is performed between a UAV and a UTM.
  • the flows include the following operations.
  • the UAV transmits a registration request message to a 5G core network (5GC) , the registration request message carries the first information.
  • 5GC 5G core network
  • the first information can be carried in a UAV Classmark IE or a payload container.
  • the first information includes characteristics such as a serial number of the UAV, at least one of a weight or power class of the UAV, controller/pilot contact details of the UAV.
  • the 5GC does not process the first information, but passes it through to the UTM.
  • the 5GC does the authentication and security checks of the UAV’s access request. Upon successful checks, the 5FC sets a security mode so that there after signaling and information exchanges with the UAV is secure.
  • the 5GC needs to authenticate the UAV and set the security mode between the 5GC and the UAV or UAVC or UAS, so that the information or signaling between the UAV and the 5GC is exchanged in a secure environment.
  • the authentication and secure checks may be any authentication and secure checks method presently known.
  • the 5GC transmits a UAV request registration message to the UTM, the UAV request registration message carries the first information.
  • the 5GC can make use of some of the information provided in the UAV Classmark IE, for instance to link the UAV to a profile 5GC keeps about the UAV and its access for 5GS services.
  • the UTM decides on the UAV’s request. If registration is allowed, the UTM issues a corresponding identification.
  • the corresponding identification is an assigned ID allocated by the UTM to the UAV.
  • the UTM transmits a UAV registration OK message to the 5GC, the UAV registration OK message carries the second information.
  • the second information can be carried in a UTM Validation IE or a payload container.
  • the 5GC transmits a registration accept message to the UAV, the registration accept message carries the second information.
  • the second information can be carried in the UTM Validation IE or the payload container.
  • the second information includes, for example, the assigned ID for the UAV, a registration outcome for the UAV, flight information of the UAV.
  • the second information provided to the UAV can be securely provided as meantime the 5GC has set the security mode so as to safeguard exchange of signaling and information.
  • FIG. 6 is another flowchart of allocation of an identity based on a registration procedure according to the embodiments of the present disclosure.
  • the UAV transmits a registration request message to a 5G core network (5GC) .
  • 5GC 5G core network
  • the 5GC initiates an authentication procedure.
  • the 5GC transmits an authentication request message to the UAV.
  • the UAV transmits au authentication response message to the 5GC, the authentication response message carries the first information.
  • the first information can be carried in a UAV Classmark IE or a payload container.
  • the first information includes characteristics such as a serial number of the UAV, at least one of a weight or power class of the UAV, controller/pilot contact details.
  • the 5GC transmits a UAV request registration message to the UTM, the UAV request registration message carries the first information.
  • the UTM decides on the UAV’s request. If registration is allowed, the UTM issues a corresponding identification.
  • the corresponding identification is an assigned ID allocated by the UTM to the UAV.
  • the UTM transmits a UAV registration OK message to the 5GC, the UAV registration OK message carries the second information.
  • the second information is carried in a UTM Validation IE or a payload container.
  • the 5GC transmits a registration accept message to the UAV, the registration accept message carries the second information.
  • the second information is carried in the UTM Validation IE or the payload container.
  • the second information includes, for example, the assigned ID for the UAV, a registration outcome for the UAV, flight information of the UAV.
  • the UAV Classmark can be passed (from the UE/UAV to the UTM) in any other appropriate Uplink (UL) NAS message, e.g., a Registration Request, Service Request, UL NAS Transport, Registration Updating messages or even 5GSM messages such as Packet Data Unit (PDU) Session Establishment or Modification messages.
  • UL Uplink
  • NAS message e.g., a Registration Request, Service Request, UL NAS Transport, Registration Updating messages or even 5GSM messages such as Packet Data Unit (PDU) Session Establishment or Modification messages.
  • PDU Packet Data Unit
  • the UTM's allocation of the Assigned ID can be passed to the UE/UAV through any Downlink (DL) NAS message, e.g., a Service Accept, Registration Updating Accept messages, DL NAS Transport (e.g., UE Configuration Update messages) or even 5GSM messages such as PDU Session Management messages including e.g., PDU Session Establishment Accept and PDU Session Modification Accept.
  • DL Downlink
  • DL NAS Transport e.g., UE Configuration Update messages
  • PDU Session Management messages including e.g., PDU Session Establishment Accept and PDU Session Modification Accept.
  • UAV Classmark Whilst the above have explicitly named a new Information Element UAV Classmark to carry (between UAV and UTM) UAS registration information, e.g., Serial Number, Pilot personal contacts like telephone numbers, Session Number/ID, (UAV's ) Assigned Identity as assigned by UTM, the above works as well with using any other new or existing IEs of the 3GPP system. The above works as well, if instead of using the IE of the 3GPP system, a payload container (transparent to the 3GPP system) is used instead.
  • the UTM could provide, as part of information back to the UAV/UE (e.g., as part of UTM Validation IE back to UE/UAV or any other chosen Information Element or fields of existing or new IEs) , an internet address (i.e., an IP address) of the UTM's database or UTM's approved internet database which the UAV/UE uses for Remote Identification process by Direct Broadcast or Network Publishing means. Security credentials for access to such database for Network Publishing can likewise be provided.
  • an internet address i.e., an IP address
  • a location of the Network Publishing database must be an IP address.
  • the location can be a FQDN (Fully Qualified Domain Name) or a URL or any text or word string that can allow the UAV to publish information that is required as part of Remote Identification process.
  • the provision of information to the UAV is over a control plane via control plane (or NAS signaling) protocols and procedures.
  • control plane or NAS signaling
  • UTM including USS
  • UTM provided information or interactions with the UTM (or USS or any entities that are part of the UTM) could be through a user plane established for such exchange of information.
  • Session Management procedures are used to establish a PDU Session and furthermore allocate user plane bearers (or Data Radio Bearers (DRBs) ) where one or more of such DRBs could be the bearer (s) for exchange of required information between the UTM and the UAV, where one of the things UTM can provide to the UAV is the Assigned ID (or Session Identity) for use as part of Remote Identification by the UAV.
  • DRBs Data Radio Bearers
  • FIG. 7 provides an illustration of this solution, i.e., illustrates a flowchart of allocation of an identity based on a user plane connection according to the embodiments of the present disclosure. As illustrated in FIG. 7, the flows include the following operations.
  • the UAV registers with a 5G system through 3GPP registration procedures.
  • the 3GPP registration procedures mainly include that the UAV transmits a registration request message to the 5GC; and the 5GC transmits a registration accept message to the UAV.
  • a UE establishes a PDU session indicating (for example by a PDU Session Type) the session is for a connection to the UTM.
  • a user plane is allocated between the UE and the 5G system.
  • the PDU session establishment mainly includes that the UAV transmits a PDU session establishment request message to the 5GC; and the 5GC transmits a PDU session establishment accept message to the UAV.
  • the user plane thus exists between the UAV and the 5GC, and a data connection is from the 5GC to the UTM.
  • a data connection is from the 5GC to the UTM.
  • transmission of the first information and the second information can be performed between the UAV and the UTM over this user plane.
  • the UAV transmits a Request Registration message (for the UAS) to the UTM, this message carries the first information, and the first information includes, for example, a serial number of the UAV, pilot’s contact details of the UAV, at least one of a weight or power class of the UAV.
  • the UTM transmits a Registration Approved message (for the UAS) to the UAV, this message carries the second information, and the second information includes, for example, an assigned ID for the UAV, flight path information of the UAV, maximum and minimum heights of the UAV, a maximum allowable speed of the UAV, allocated operation time of the UAV.
  • the second information includes, for example, an assigned ID for the UAV, flight path information of the UAV, maximum and minimum heights of the UAV, a maximum allowable speed of the UAV, allocated operation time of the UAV.
  • the "Session ID" associated with the PDU Session is not to be mixed with the "Session ID” assigned by the UTM (or USS) to the UAV for purposes of Remote Identification and Tracking, wherein in this disclosure the term “Assigned ID” is often used.
  • the "Session ID” in the embodiments of the present disclosure refers to the session ID the UTM or USS issues to the UAV.
  • the term “Assigned ID” is used instead of "Session ID” to illustrate that the term chosen does not change the solutions put forward in embodiments of the present disclosure.
  • the UTM upon approving the UAV registration request and providing the UAV with the assigned ID, can by itself provide that assigned ID to the 5GC.
  • This addition can be used by 5GC to form a relationship between the UAV, the PDU Session (s) of the UAV, the DRBs for the UAV and the connection to the UTM, i.e., forming the UAV's profile (or the subscription profile) that the 5GC keeps.
  • This assigned ID could then be used as the reference between the UTM and the 5GC should UTM request certain actions be done to the UAV on its behalf, e.g., report of UAV's location or status, e.g., set up DRBs to transmit video clips from the UAV, e.g., intercept communications between UAV and its UAVC (e.g., channel communications between UAV and its UAVC) to a third party first responder unit.
  • UTM report of UAV's location or status, e.g., set up DRBs to transmit video clips from the UAV, e.g., intercept communications between UAV and its UAVC (e.g., channel communications between UAV and its UAVC) to a third party first responder unit.
  • UAVC e.g., channel communications between UAV and its UAVC
  • the provision of the assigned ID by the UTM direct to the 5GS has the advantage that what get exchanged between the UTM and the UAV need not have the intervention of the 5GS. So what goes between the UTM and the UAV (and vice versa) can be payload data, with the 5GS (and 5GC in particular) acting as just the conduit for such data exchange even if that exchange consist of signaling between the UTM and the UAV.
  • the location details or address or IP address of the database or server for Network Publishing of UAV's Remote Identification and Tracking can be provided to the UAV over the user plane (or allocated DRBs) .
  • security credentials for access to such database or server for Network Publishing be provided by UTM to UAV.
  • UTM User Equipment Controller
  • the UAV at time of its request to the UTM (or USS, which is in part an entity of the UTM) to operate provides its previously assigned ID (or session ID) if one is available. It may be that in a previous registration, one such assigned ID was given to the UAV which is still present in the UAV for whatever reason not associated with the present disclosure.
  • the UAV can in the above solutions of the embodiments of the present disclosure provide that available assigned ID. It will then be up to the UTM to decide either to allocate a new assigned ID or reuse the existing assigned ID.
  • the UTM can decide to allocate a new assigned ID or refresh the assigned ID with another assigned ID.
  • This re-allocation or refresh/renew of an assigned ID to the UAV can be realized by the above solutions of the embodiments of the present disclosure.
  • the DL Configuration Update message, or the Registration Update Accept message or the Service Accept from the network side can carry the replacement Assigned ID.
  • the PDU Modification procedure can be the carrier of the new (the replacement) Assigned ID.
  • the UTM can also update to the UAV a new location of the database or server to which remote identification and tracking information is to be published, along with updating the security credentials for access to such database or server.
  • the embodiments of the present disclosure introduce means and methods to provide the UAV (or Drone) an assigned ID (or session ID) for use by it in Remote Identification and Tracking process and reporting.
  • the embodiments of the present disclosure propose solutions for the provision of the assigned ID to the UAV by the UTM.
  • This solution encompasses that from the start of one registration procedure, information and characteristics of the UAV needed by the UTM to decide on the UAV's request and UTM's granting and allocating the assigned ID (to the UAV) can all be provided as part of one process. Thus by completion of registration the assigned ID is available to the UAV.
  • the delivery of UAV request and information about the UAV to UTM and later on the provision of the assigned ID from the UTM to the UAV can all be done not only securely but also speedily and efficiently as it is in one process (i.e., the registration process, noting that this registration process takes in the 5GC authenticating the UAV and setting the security mode between the 5GC and the UAV or UAVC or UAS) .
  • the solutions of using the control plane also allows the UAV to provide its characteristics in a containerized manner and be tailored for what UAV characteristics the 5GC or 5GS might need or can pass alone acting as a conduit between the UAV and the UTM. These solutions further do not confine that the UAV provides just its characteristics.
  • the UAV could provide information that allows or assist the 5GC to locate the UTM, e.g. the UTM's destination or address.
  • the UAV could provide information that allows or assist the 5GC to locate the UTM, e.g. the UTM's destination or address.
  • information passed from the UTM to the UAV of which one main piece of information is the assigned ID (but not limited to just that piece of information) .
  • the location for which the UAV can publish information as part of Remote Identification, can by these solutions be provided from the UTM to the UAV.
  • the UAV's wish to register with the UTM (for UAS operations) and characteristics of the UAV are performed through a 5GS established user plane.
  • the UTM response i.e., the acceptance of UAV's request for UAS operations and the assigned ID
  • UAV's weight class is provided to the UTM also through the user plane.
  • Such solution of utilizing the user plane also allows the UTM to respond to the UAV's request for UAS operations and for the UTM to provide the assigned ID along with other information, e.g., a flight path of the UAV, maximum and minimum flight heights of the UAV and a flight speed of the UAV.
  • other information e.g., a flight path of the UAV, maximum and minimum flight heights of the UAV and a flight speed of the UAV.
  • what is identified information in the present disclosure does not limit other as yet unidentified information to be passed between the UAV and the UTM and vice versa.
  • the solution of utilizing the user plane allow the 5GS (and 5GC in particular) to have a more transport role, i.e., a bearer for the UAS, a bearer between the UAV and the UTM, thus easing the impacts and role the 5GS and 5GC has to play to support the UAS.
  • This assigned ID can also be made know to the 5GC for eventual use as reference to its provision of connectivity and service between the UAV and the UTM, i.e., the assigned ID can be part of the UE profile the 5G system (and the 5GC) keeps of the UEs registered with it. Having the assigned ID in the UE's profile gives further benefit of linking the UAV's registration status, connection status, service states and service and subscriptions rights, 5GS identities (such as, the 5G-GUTI, IMEI, PEI, SUPI) to internal connections and external connection to UTM.
  • 5GS identities such as, the 5G-GUTI, IMEI, PEI, SUPI
  • the UAV provides, when it requests the UTM for right to operate (i.e., initiate its registration to UTM to operate UAS operations) , to the UTM its previously provisioned assigned ID, if that is still available in the UAV. For example, this may be the case when the UAV wants to renew or extend its operational rights.
  • the UTM can update to the UAV a new (or replacement) ASSIGNED ID. For example this may be when UTM decides that the present assigned ID has been compromised or risk being compromised or due to its time in use needs to be refreshed.
  • the UTM can also update to the UAV a new location of the database or server to which remote identification and tracking information is to be published, along with updating the security credentials for access to such database or server.
  • FIG. 8 is a first structural diagram of a device for allocating an identity (ID) according to the embodiments of the present disclosure.
  • the device is for use in a UAV.
  • the device includes a sending unit 801 and a receiving unit 802.
  • the sending unit 801 is configured to transmit first information to a UTM, here, the first information includes at least one characteristic of the UAV.
  • the receiving unit 802 is configured to receive second information from the UAV, here, the second information includes a first assigned ID for the UAV.
  • the first information includes at least one of (but not limited to) the following characteristics: a serial number of the UAV or a UE identifier of the UAV.
  • the first information further includes at least one of (but not limited to) the following characteristics: a weight of the UAV, a power class of the UAV, a type of engine of the UAV, a flight range of the UAV, a maximum attainable altitude of the UAV, onboard equipment of the UAV, or a type of communication supported by the UAV.
  • the second information further includes at least one of (but not limited to) : an outcome of registration of the UAV or flight configuration information of the UAV.
  • the flight configuration information of the UAV includes at least one of (but not limited to) : a flight plan for the UAV, a geographical area of operation by the UAV, tracking information provided by the UAV in operation, a frequency of providing tracking information by the UAV, or flight path height limits of the UAV.
  • the second information further comprises at least one of (but not limited to) : location information of a secure database or internet server where remote identification and tracking information is to be published by the UAV, or security credentials to allow access to the secure database or internet server where the remote identification and tracking information is to be published by the UAV.
  • the sending unit 801 is configured to transmit an uplink Non-Access Stratum (NAS) message to a core network, the uplink NAS message carries the first information, and the first information is forwarded to the UTM by the core network; and the receiving unit 802 is configured to receive a downlink NAS message from the core network, the downlink NAS message carries the second information, and the second information is determined by the UTM and is transmitted to the core network.
  • NAS Non-Access Stratum
  • the uplink NAS message carries a first Information Element (IE) or a first payload container, and the first IE or the first payload container is used for carrying the first information.
  • the downlink NAS message carries a second Information Element (IE) or a second payload container, and the second IE or the second payload container is used for carrying the second information.
  • the uplink NAS message and the downlink NAS message includes one of the following.
  • the uplink NAS message is a registration request message
  • the downlink NAS message is a registration accept message.
  • the uplink NAS message is a service request message
  • the downlink NAS is a service accept message.
  • the uplink NAS message is a registration update message
  • the downlink NAS message is a registration update accept message.
  • the uplink NAS message is a session establishment request message
  • the downlink NAS message is a session establishment accept message.
  • the uplink NAS message is a session modification message
  • the downlink NAS message is a session modification accept message
  • the device further includes an establishment unit 803, configured to establish a user plane connection with the UTM, here, the user plane connection includes a first user plane connection between the UAV and the core network and a second user plane connection between the core network and the UTM.
  • the user plane connection includes a first user plane connection between the UAV and the core network and a second user plane connection between the core network and the UTM.
  • the sending unit 801 is configured to transmit the first information to the core network through the first user plane connection, and the first information is transmitted by the core network to the UTM through the second user plane connection.
  • the receiving unit 802 is configured to receive the second information from the core network through the first user plane connection, and the second information is determined by the UTM and is transmitted to the core network through the second user plane connection.
  • the second information is used by the core network to generate a profile of the UAV.
  • the user plane connection includes at least one of: a session, a data flow, or a bearer.
  • the receiving unit 802 is configured to receive location information of a secure server or internet server from the UTM; and the sending unit 801 is configured to publish remote identification information of the UAV to the secure database or internet server based on the location information.
  • the receiving unit 802 is configured to receive, from the UTM, security credentials to allow access to the secure database or internet server to publish remote identification and tracking information of the UAV.
  • the receiving unit 802 is configured to receive third information from the UTM, here, the third information include a second assigned ID for the UAV.
  • the device further includes an updating unit, configured to update the first assigned ID with the second assigned ID.
  • the receiving unit 802 is configured to receive third information from the UTM, here, the third information includes at least one of: update of location information of a secure database or internet server where remote identification and tracking information is to be published by the UAV, or update of security credentials for access to the secure database or internet server where the remote identification and tracking information is to be published by the UAV.
  • the third information is carried in at least one of: a downlink configuration update message, a registration update accept message, a service accept message, a session modification accept message, or a configuration update message.
  • FIG. 9 is a second structural diagram of a device for allocating an identity according to the embodiments of the present disclosure.
  • the device is for use in a UTM.
  • the device includes a receiving unit 901 and a sending unit 902.
  • the receiving unit 901 is configured to receive first information from a UAV, here, the first information includes at least one characteristic of the UAV.
  • the sending unit 902 is configured to transmit second information to the UAV, here, the second information includes a first assigned ID for the UAV.
  • the first information includes at least one of (but not limited to) the following characteristics: a serial number of the UAV or a UE identifier of the UAV.
  • the first information further includes at least one of (but not limited to) the following characteristics: a weight of the UAV, a power class of the UAV, a type of engine of the UAV, a flight range of the UAV, a maximum attainable altitude of the UAV, onboard equipment of the UAV, or a type of communication supported by the UAV.
  • the second information further includes at least one of (but not limited to) : an outcome of registration of the UAV or flight configuration information of the UAV.
  • the flight configuration information of the UAV includes at least one of (but not limited to) : a flight plan for the UAV, a geographical area of operation by the UAV, tracking information provided by the UAV in operation, a frequency of providing tracking information by the UAV, or flight path height limits of the UAV.
  • the second information further comprises at least one of (but not limited to) : location information of a secure database or internet server where remote identification and tracking information is to be published by the UAV, or security credentials to allow access to the secure database or internet server where the remote identification and tracking information is to be published by the UAV.
  • the receiving unit 901 is configured to receive the first information from a core network, and the first information is transmitted to the core network by the UAV through an uplink NAS message; the sending unit 902 is configured to transmit the second information to the core network, and the second information is transmitted to the UAV by the core network through a downlink NAS message.
  • the uplink NAS message carries a first Information Element (IE) or a first payload container, and the first IE or the first payload container is used for carrying the first information.
  • the downlink NAS message carries a second Information Element (IE) or a second payload container, and the second IE or the second payload container is used for carrying the second information.
  • the uplink NAS message and the downlink NAS message includes one of the following.
  • the uplink NAS message is a registration request message
  • the downlink NAS message is a registration accept message.
  • the uplink NAS message is a service request message
  • the downlink NAS is a service accept message.
  • the uplink NAS message is a registration update message
  • the downlink NAS message is a registration update accept message.
  • the uplink NAS message is a session establishment request message
  • the downlink NAS message is a session establishment accept message.
  • the uplink NAS message is a session modification message
  • the downlink NAS message is a session modification accept message
  • a user plane connection is established between the UAV and the UTM, here, the user plane connection includes a first user plane connection between the UAV and the core network and a second user plane connection between the core network and the UTM.
  • the receiving unit 901 is configured to receive the first information from the core network through the second user plane connection, and the first information is transmitted by the UAV to the core network through the first user plane connection.
  • the sending unit 902 is configured to transmit the second information to the core network through the second user plane connection, and the second information is transmitted to the UAV by the core network through the first user plane connection.
  • the second information is used by the core network to generate a profile of the UAV.
  • the user plane connection includes at least one of: a session, a data flow, or a bearer.
  • the sending unit 902 is configured to transmit location information of a secure database or internet server to the UAV, the location information of the secure database or internet server being used by the UAV to publish remote identification information of the UAV.
  • the sending unit 902 is configured to transmit, to the UAV, security credentials to allow access to the secure database or internet server to publish remote identification and tracking information of the UAV.
  • the sending unit 902 is configured to transmit third information to the UAV, here, the third information include a second assigned ID for the UAV, and the second assigned ID is used for updating the first the first assigned ID.
  • the sending unit 902 is configured to transmit third information to the UAV, the third information comprising at least one of: update of location information of a secure database or internet server where remote identification and tracking information is to be published by the UAV, or update of security credentials for access to the secure database or internet server where the remote identification and tracking information is to be published by the UAV.
  • the third information is carried in at least one of: a downlink configuration update message, a registration update accept message, a service accept message, a session modification accept message, or a configuration update message.
  • FIG. 10 is a structural diagram of a communication device 1000 according to the embodiments of the present disclosure.
  • the communication device may be a UAV or a UE, or may be a network device (e.g., a UTM) .
  • the communication device 1000 as illustrated in FIG. 10 includes a processor 1010 configured to call and execute computer programs in a memory to perform the methods in the embodiments of the present disclosure.
  • the communication device 1000 further includes a memory 1020.
  • the processor 1010 may be configured to call and execute computer programs in the memory 1020 to perform the methods in the embodiments of the present disclosure.
  • the memory 1020 may be a separate device independent of the processor 1010, or may be integrated into the processor 1010.
  • the communication device 1000 further includes a transceiver 1030.
  • the processor 1010 may control the transceiver 1030 to perform communication with another device, so as to transmit information or data to the another device or receive information or data from the another device.
  • the transceiver 1030 may include a transmitter and a receiver.
  • the transceiver 1030 may further include an antenna, and the number of antennas may be one or more.
  • the communication device 1000 may be a network device in the embodiments of the present disclosure, and the communication device 1000 may implement the corresponding processes implemented by the network device in various methods of the embodiments of the present disclosure. For simplicity, details are not described herein again.
  • the communication device 1000 may be a mobile terminal/terminal device in the embodiments of the present disclosure, and the communication device 1000 may implement the corresponding processes implemented by the mobile terminal/terminal device in various methods of the embodiments of the present disclosure. For simplicity, details are not described herein again.
  • FIG. 11 is a structural diagram of a chip according to the embodiments of the present disclosure. As illustrated in FIG. 11, the chip 1100 includes a processor 1110 configured to call and execute computer programs in a memory to perform the methods in the embodiments of the present disclosure.
  • a processor 1110 configured to call and execute computer programs in a memory to perform the methods in the embodiments of the present disclosure.
  • the chip 1100 further includes a memory 1120.
  • the processor 1110 may be configured to call and execute computer programs in the memory 1120 to perform the methods in the embodiments of the present disclosure.
  • the memory 1120 may be a separate device independent of the processor 1110, or may be integrated into the processor 1110.
  • the chip 1100 may further include an input interface 1130.
  • the processor 1110 may control the input interface 1130 to communicate with another device or chip, so as to obtain information or data from the another device or chip.
  • the chip 1100 may further include an output interface 1140.
  • the processor 1110 may control the output interface 1140 to communicate with another device or chip, so as to output information or data to the another device or chip.
  • the chip may be applied to the network device in the embodiments of the present disclosure, and the chip may implement the corresponding processes implemented by the network device in various methods of the embodiments of the present disclosure. For simplicity, details are not described herein again.
  • the chip may be applied to the mobile terminal/terminal device in the embodiments of the present disclosure, and the chip may implement the corresponding processes implemented by the mobile terminal/terminal device in various methods of the embodiments of the present disclosure. For simplicity, details are not described herein again.
  • the chip in the embodiments of the present application may also be called as a system-level chip, a system chip, a chip system or a system-on-chip.
  • FIG. 12 is a block diagram of a communication system 1200 according to the embodiments of the present disclosure. As illustrated in FIG. 12, the communication system 1200 includes a terminal device 1210 and a network device 1220.
  • the terminal device 1210 may be configured to perform the corresponding functions implemented by the terminal device in the above methods; and the network device 1220 may be configured to perform the corresponding functions implemented by the network device in the above methods. For simplicity, details are not described herein again.
  • the processor in the embodiments of the disclosure may be an integrated circuit chip and has a signal processing capability.
  • each operation of the foregoing method embodiments may be completed by an integrated logic circuit of hardware in a processor or instructions in a form of software in a processor.
  • the above processor may be a general-purpose processor, a Digital Signal Processor (DSP) , an Application Specific Integrated Circuit (ASIC) , a Field Programmable Gate Array (FPGA) or another Programming logic devices, a discrete gate or transistor logic device, a discrete hardware component, or the like.
  • DSP Digital Signal Processor
  • ASIC Application Specific Integrated Circuit
  • FPGA Field Programmable Gate Array
  • Various methods, operations, and logical blocks disclosed in the embodiments of the present disclosure can be implemented or executed.
  • a general-purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
  • the operations of the methods disclosed in combination with the embodiments of the present disclosure may be directly implemented by a hardware decoding processor, or may be implemented by a combination of hardware and software modules in the decoding processor.
  • the software modules may be located in a mature storage medium in the art, such as a Random Access Memory (RAM) , a flash memory, a Read-Only Memory (ROM) , a Programmable Read-Only Memory (PROM) , an Erasable Programmable Read-Only Memory (EPROM) , an Electrically Erasable Programmable Read-Only Memory (EEPROM) , a register, and the like.
  • RAM Random Access Memory
  • ROM Read-Only Memory
  • PROM Programmable Read-Only Memory
  • EPROM Erasable Programmable Read-Only Memory
  • EEPROM Electrically Erasable Programmable Read-Only Memory
  • the memory in the embodiments of the present disclosure may be a volatile memory or a non-volatile memory, or may include the volatile memory and the non-volatile memory.
  • the non-volatile memory may be a ROM, a PROM, an EPROM, EEPROM or a flash memory, or the like.
  • the volatile memory may be a RAM, which is used as an external cache.
  • RAMs such as a Static Random Access Memory (SRAM) , a Dynamic RAM (DRAM) , a Synchronous DRAM (SDRAM) , a Double Data Rate SDRAM (DDR SDRAM) , an Enhanced SDRAM (ESDRAM) , a Synchlink DRAM (SLDRAM) , and a Direct Rambus RAM (DR RAM) .
  • SRAM Static Random Access Memory
  • DRAM Dynamic RAM
  • SDRAM Synchronous DRAM
  • DDR SDRAM Double Data Rate SDRAM
  • ESDRAM Enhanced SDRAM
  • SLDRAM Synchlink DRAM
  • DR RAM Direct Rambus RAM
  • the memory in the embodiments of the present disclosure may also be a Static RAM (SRAM) , a Dynamic RAM (DRAM) , Synchronous dynamic random access memory (synchronous DRAM, SDRAM) , double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM) , enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM) , synchronous connection Dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM) , etc. That is, the memories in the embodiments of the present application are intended to include, but not limited to, these and any other suitable types of memories.
  • the embodiments of the present disclosure further provide a computer-readable storage medium for storing computer programs.
  • the computer-readable storage medium may be applied to the network device in the embodiments of the present disclosure, and the computer programs cause a computer to execute the corresponding processes implemented by the network device in each method in the embodiments of the present disclosure. For simplicity, details are not described herein again.
  • the computer-readable storage medium may be applied to the mobile terminal/terminal device in the embodiments of the present disclosure, and the computer programs cause a computer to execute the corresponding processes implemented by the mobile terminal/terminal device in each method in the embodiments of the present disclosure.
  • the computer programs cause a computer to execute the corresponding processes implemented by the mobile terminal/terminal device in each method in the embodiments of the present disclosure.
  • the embodiments of the present disclosure further provide a computer program product including computer program instructions.
  • the computer program product can be applied to the network device in the embodiments of the present disclosure, and the computer program instructions cause a computer to execute the corresponding processes implemented by the network device in each method in the embodiments of the present disclosure.
  • the computer program instructions cause a computer to execute the corresponding processes implemented by the network device in each method in the embodiments of the present disclosure. For simplicity, details are not described herein again.
  • the computer program product can be applied to the mobile terminal/terminal device in the embodiments of the present disclosure, and the computer program instructions cause a computer to execute the corresponding processes implemented by the mobile terminal/terminal device in each method in the embodiments of the present disclosure.
  • the computer program instructions cause a computer to execute the corresponding processes implemented by the mobile terminal/terminal device in each method in the embodiments of the present disclosure. For simplicity, details are not described herein again.
  • the embodiments of the present disclosure further provide a computer program.
  • the computer program can be applied to the network device in the embodiments of the present disclosure, and when run on a computer, causes the computer to execute the corresponding processes implemented by the network device in each method in the embodiments of the present disclosure.
  • the computer program can be applied to the network device in the embodiments of the present disclosure, and when run on a computer, causes the computer to execute the corresponding processes implemented by the network device in each method in the embodiments of the present disclosure.
  • details are not described herein again.
  • the computer program can be applied to the mobile terminal/terminal device in the embodiments of the present disclosure, and when run on a computer, causes the computer to execute the corresponding processes implemented by the mobile terminal/terminal device in each method in the embodiments of the present disclosure. For simplicity, details are not described herein again.
  • the disclosed system, device, and method may be implemented in other manners.
  • the described device embodiments are merely examples.
  • the unit division is merely logical function division.
  • a plurality of units or components may be combined or integrated into another system, or some features may be ignored or not performed.
  • the displayed or discussed mutual couplings or direct couplings or communication connections may be implemented through some interfaces.
  • the indirect couplings or communication connections between the devices or units may be implemented in electronic, mechanical, or other forms.
  • the units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one position, or may be distributed on a plurality of network units. Some or all of the units may be selected based on actual requirements to achieve the solutions of the embodiments of the disclosure.
  • functional units in the embodiments of the present disclosure may be integrated into one processing unit, or each of the units may exist alone physically, or two or more units are integrated into one unit.
  • the functions When the functions are implemented in the form of a software functional unit and sold or used as an independent product, the functions may be stored in a computer-readable storage medium.
  • the software product is stored in a storage medium, and includes several instructions for instructing a computer device (which may be a personal computer, a server, or a network device, or the like) to perform all or some of the operations described in the embodiments of the disclosure.
  • the foregoing storage medium includes: any medium that can store program codes, such as a USB flash drive, a removable hard disk, a ROM, a RAM, a magnetic disk, or a compact disc.

Landscapes

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

Abstract

L'invention concerne un procédé et un dispositif d'attribution d'une identité, et un dispositif de communication. Le procédé comprend les étapes suivantes : un véhicule aérien sans pilote (UAV) transmet des premières informations à un système de gestion du trafic (UTM) de système aérien sans pilote (UAS), les premières informations comprenant au moins une caractéristique de l'UAV ; et l'UAV reçoit des secondes informations de l'UTM, les secondes informations comprenant une première identité (ID) attribuée pour l'UAV.
PCT/CN2020/077842 2020-03-04 2020-03-04 Procédé et dispositif d'attribution d'identité, et dispositif de communication WO2021174464A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/077842 WO2021174464A1 (fr) 2020-03-04 2020-03-04 Procédé et dispositif d'attribution d'identité, et dispositif de communication

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/077842 WO2021174464A1 (fr) 2020-03-04 2020-03-04 Procédé et dispositif d'attribution d'identité, et dispositif de communication

Publications (1)

Publication Number Publication Date
WO2021174464A1 true WO2021174464A1 (fr) 2021-09-10

Family

ID=77613773

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/077842 WO2021174464A1 (fr) 2020-03-04 2020-03-04 Procédé et dispositif d'attribution d'identité, et dispositif de communication

Country Status (1)

Country Link
WO (1) WO2021174464A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023186479A1 (fr) * 2022-03-30 2023-10-05 Sony Group Corporation Véhicules aériens sans pilote et procédés de fonctionnement de véhicules aériens sans pilote

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3422598A1 (fr) * 2017-06-29 2019-01-02 Deutsche Telekom AG Véhicule aérien sans équipage commutable à un signal de direction d'un client supérieur
CN109716418A (zh) * 2018-12-18 2019-05-03 北京小米移动软件有限公司 飞行申报方法及装置
CN109792786A (zh) * 2018-12-17 2019-05-21 北京小米移动软件有限公司 用户设备配对的方法及装置

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3422598A1 (fr) * 2017-06-29 2019-01-02 Deutsche Telekom AG Véhicule aérien sans équipage commutable à un signal de direction d'un client supérieur
CN109792786A (zh) * 2018-12-17 2019-05-21 北京小米移动软件有限公司 用户设备配对的方法及装置
CN109716418A (zh) * 2018-12-18 2019-05-03 北京小米移动软件有限公司 飞行申报方法及装置

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023186479A1 (fr) * 2022-03-30 2023-10-05 Sony Group Corporation Véhicules aériens sans pilote et procédés de fonctionnement de véhicules aériens sans pilote

Similar Documents

Publication Publication Date Title
US20220277657A1 (en) Methods and Apparatus for Enhancing Unmanned Aerial Vehicle Management Using a Wireless Network
KR102367135B1 (ko) 무선 통신 네트워크의 seal 시스템에서 서비스 간 통신을 프로비저닝하기 위한 seal 시스템 및 방법
EP3349085B1 (fr) Contrôle sécurisé des véhicules sans pilote
US20210099870A1 (en) Method and apparatus for performing authorization for unmanned aerial system service in wireless communication system
CN115762240A (zh) 用于无人驾驶航空系统(uas)业务管理(utm)的协议设计
EP4144117A1 (fr) Procédés d'utilisation d'un système de sécurité fondé sur un certificat avec identité et diffusion de drone
CN113785601A (zh) 使用v2x通信进行车辆位置跟踪的方法和系统
Belwafi et al. Unmanned aerial vehicles’ remote identification: A tutorial and survey
US11184344B2 (en) Authorization of user equipment for mobile communications network that has previously been authorized by trusted traffic authority
US20230102300A1 (en) A mechanism for unmanned vehicle authorization for operation over cellular networks
US20210343164A1 (en) Trajectory determining method and related device
CN115516820A (zh) 向无人飞行器提供安全凭证
Tomaszewski et al. Integration of U-space and 5GS for UAV services
WO2021174464A1 (fr) Procédé et dispositif d'attribution d'identité, et dispositif de communication
US20220345321A1 (en) Managing An Unmanned Aerial Vehicle Identity
US11670177B2 (en) Unmanned aerial vehicle remote identification, command and control
WO2022013601A1 (fr) Prestation de vol de drone dans des réseaux 5g
EP4128709A1 (fr) Procédé et dispositif de fourniture automatisée de données à partir de multiples capteurs à l'intérieur d'un réseau de services d'urgence
WO2021179132A1 (fr) Procédé et dispositif de contrôle d'accès
CN112584344B (zh) 无人机的身份标识认证方法、相关装置及系统
US20240224352A1 (en) Mobility edge network systems and methods
Zhao et al. drip S. Card Internet-Draft A. Wiethuechter Intended status: Informational AX Enterprize Expires: April 28, 2022 R. Moskowitz HTT Consulting
US20220312205A1 (en) Communication method and device for supporting authentication of unmanned aerial vehicle in wireless communication system
Zhao et al. drip S. Card Internet-Draft A. Wiethuechter Intended status: Informational AX Enterprize Expires: June 17, 2022 R. Moskowitz HTT Consulting
Wiethuechter et al. RFC 9153: Drone Remote Identification Protocol (DRIP) Requirements and Terminology

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20922803

Country of ref document: EP

Kind code of ref document: A1