KR20210039949A - Apparatus and method for mobility management of unmanned aerial vehicle using flight mission and route in mobile communication system - Google Patents

Abstract

The present disclosure relates to a communication technique that converges a 5G communication system for supporting a higher data rate after a 4G system with IoT technology and a system thereof. The present disclosure can be applied to intelligent services based on 5G communication technology and IoT-related technology (e.g., smart home, smart building, smart city, smart car or connected car, healthcare, digital education, retail, security and safety-related services, etc.). In consideration of the communication characteristics of an unmanned aerial vehicle, the present disclosure provides a technique for considering terminal mobility restrictions and registration areas of a mobile communication network in consideration of the purpose and route of a terminal to efficiently support a communication service with the unmanned aerial vehicle.

Description

A mobility management method and device that considers the purpose and route of the unmanned aerial vehicle in a mobile communication system {APPARATUS AND METHOD FOR MOBILITY MANAGEMENT OF UNMANNED AERIAL VEHICLE USING FLIGHT MISSION AND ROUTE IN MOBILE COMMUNICATION SYSTEM}

The present disclosure relates to a wireless communication system, and specifically, an unmanned aerial vehicle in a mobile communication system, an unmanned aerial vehicle controller that controls it, and an unmanned aerial vehicle (UTM) that controls UAS. Traffic Management) An apparatus and method for controlling the movement path of UAS through information exchange between systems.

Efforts are being made to develop an improved 5G communication system or a pre-5G communication system in order to meet the increasing demand for wireless data traffic after the commercialization of 4G communication systems. For this reason, a 5G communication system or a pre-5G communication system is called a Beyond 4G Network communication system or an LTE system and a Post LTE system. In order to achieve a high data rate, the 5G communication system is being considered for implementation in the ultra-high frequency (mmWave) band (eg, such as the 60 Giga (60 GHz) band). In order to mitigate the path loss of radio waves in the ultra-high frequency band and increase the transmission distance of radio waves, 5G communication systems include beamforming, massive MIMO, and Full Dimensional MIMO (FD-MIMO). ), array antenna, analog beam-forming, and large scale antenna technologies are being discussed. In addition, in order to improve the network of the system, in 5G communication system, evolved small cell, advanced small cell, cloud radio access network (cloud RAN), ultra-dense network , Device to Device communication (D2D), wireless backhaul, moving network, cooperative communication, CoMP (Coordinated Multi-Points), and interference cancellation And other technologies are being developed. In addition, in 5G systems, advanced coding modulation (ACM) methods such as Hybrid FSK and QAM Modulation (FQAM) and SWSC (Sliding Window Superposition Coding), advanced access technologies such as Filter Bank Multi Carrier (FBMC), NOMA (non orthogonal multiple access), and sparse code multiple access (SCMA) have been developed.

Meanwhile, the Internet is evolving from a human-centered connection network in which humans create and consume information, to an Internet of Things (IoT) network that exchanges and processes information between distributed components such as objects. IoE (Internet of Everything) technology, which combines IoT technology with big data processing technology through connection with cloud servers, etc., is also emerging. In order to implement IoT, technological elements such as sensing technology, wired/wireless communication and network infrastructure, service interface technology, and security technology are required. , M2M), and MTC (Machine Type Communication) technologies are being studied. In the IoT environment, intelligent IT (Internet Technology) services that create new value in human life by collecting and analyzing data generated from connected objects can be provided. IoT is the field of smart home, smart building, smart city, smart car or connected car, smart grid, healthcare, smart home appliance, advanced medical service, etc. through the convergence and combination of existing IT (information technology) technology and various industries. Can be applied to.

Accordingly, various attempts have been made to apply a 5G communication system to an IoT network. For example, technologies such as sensor network, machine to machine (M2M), and machine type communication (MTC) are implemented by techniques such as beamforming, MIMO, and array antenna. There is. The application of a cloud radio access network (cloud RAN) as the big data processing technology described above can be said as an example of the convergence of 5G technology and IoT technology.

On the other hand, there is an unmanned aerial vehicle as a form of terminal that is expected to receive improved service using a mobile communication network in the near future. Currently, in operating a drone, a method of using a cellular network represented by mobile communication is not supported. Most of the current operation methods generally use a method of operating through a drone and a drone controller using a protocol provided by a manufacturer through a short-range wireless communication network such as RF, Bluetooth, and Wi-Fi. Therefore, in order to control the unmanned aerial vehicle using a mobile communication network, it is necessary to study problems that do not occur in the existing local area network, problems related to the mobility of drones, and improvements.

Various embodiments of the present disclosure include a method of supporting the operation of an Unmanned Aerial System (UAS) through a mobile communication system.

The technical problems to be achieved in the present invention are not limited to the technical problems mentioned above, and other technical problems that are not mentioned will be clearly understood by those of ordinary skill in the technical field to which the present invention belongs from the following description. I will be able to.

In a wireless communication system according to an embodiment of the present invention, a method performed by a policy control function (PCF) entity for an unmanned aerial system (UAS) service is a request to subscribe to a network capability from a server managing the UAS service. Receiving a message-The request message includes information on a flight event, based on the information on the flight event, checking the network capability including information on mobility restrictions, and managing the UAS service And transmitting a notification message including the network capability to the server.

In a wireless communication system according to an embodiment of the present invention, a policy control function (PCF) entity for an unmanned aerial system (UAS) service is a request message for subscribing to network capabilities from a transmission/reception unit and a server managing the UAS service. -The request message includes information on a flight event, based on the information on the flight event, checks the network capability including information on mobility restrictions, and to a server that manages the UAS service , It may include a control unit for controlling to transmit a notification message including the network capability.

Currently, the number of terminals using a mobile communication network and the number of services and applications to support it are increasing exponentially. In addition, in order to improve the quality of mobile communication networks, the design and operation of wireless networks and core networks are becoming increasingly sophisticated. In this situation, not only terminals using voice calls and data services, but also new types of terminals such as factories, unmanned aerial vehicles, robots, cars, and airplanes are emerging. It is expected that the number of these new types of terminals will continue to increase, and mobile communication networks are also expected to continue to evolve services in order to effectively support their purpose.

While the purposes and types of various terminals are changing, mobile communication networks currently share radio resources with all terminals, and the core network is generally operated in a form shared by all terminals. Since each terminal has a different type and purpose, it brings a difference in interaction with the network according to the type of operation and the service to be used. Therefore, in order to effectively support each type of terminal, the mobile communication network must maintain an optimized configuration by analyzing the purpose and service requirements of each terminal. In addition, in order to effectively support each terminal and services, it is necessary to determine the characteristics of each terminal and set it so that it does not affect other terminals and services through optimization and automation of configuration and management.

An object of the present invention is to support a new type of mobile communication terminal called an unmanned aerial vehicle, rather than a type of terminal used on the ground represented by an existing smart phone. In the current situation, unmanned aerial vehicles have different operational purposes and routes depending on time, and unnecessary exchange of control signals and communication quality that can occur when unmanned aerial vehicles are operated or set in the same form as existing ground-based smartphones. Deterioration, in some cases, the unmanned aerial vehicle is in a state of inability to communicate while performing a mission, resulting in an uncontrollable situation. In order to solve this problem, various embodiments of the present invention minimize control signals within a path supported by a network service when an unmanned aerial vehicle initially establishes a path and exchanges control signals with a mobile communication network, and continuously communicates. It can have a supporting effect.

In addition, in the present invention, information on regions that affect other terminals in the network or in which the unmanned aerial vehicle should avoid operation such as densely populated regions, and predictions for each region and time for network configuration and quality information that are changed in real time By providing a value, you can support the safe operation of the unmanned aerial vehicle. In addition, it is possible to prevent problems in which quality deterioration or service failure occurs when users use the network in the past due to the indiscriminate operation of the unmanned aerial vehicle.

The effects that can be obtained in the present invention are not limited to the above-mentioned effects, and other effects not mentioned can be clearly understood by those of ordinary skill in the art from the following description. will be.

1 shows the configuration of a mobile communication system and an entity located outside the network for the disclosure of the present invention.
2 shows a UAS authentication data delivery method using Parameter Provision according to an embodiment of the present invention.
3 shows a UAS authentication data delivery method extending Expected UE Behavior according to an embodiment of the present invention.
4 shows a UAS authentication data delivery method using a Service Parameter service according to an embodiment of the present invention.
5 shows a method of modifying UTM authentication supporting a core network according to an embodiment of the present invention.
6 shows the structure of a network entity according to an embodiment of the present invention.
7 shows a method of a first entity performing a policy control function (PCF) in a mobile communication system according to an embodiment of the present invention.
FIG. 8 is a diagram illustrating a procedure for transmitting information on an operable area or an unoperable area of an unmanned aerial vehicle using a PCF according to an embodiment of the present invention.
9 is a diagram illustrating a procedure for delivering information on an operable area or an impossible area that satisfies a requested communication quality requirement using NWDAF according to an embodiment of the present invention.
10 is a diagram illustrating a procedure for transmitting information on an operable area or an impossible area that satisfies a requested communication quality requirement using a PCF and an NWDAF according to an embodiment of the present invention.
11 shows the structure of an entity according to an embodiment of the present invention.
12 illustrates a method of a first entity performing a policy control function (PCF) in a mobile communication system according to an embodiment of the present invention.
13 shows a method of a first entity method of performing a network data analysis function (NWDAF) in a mobile communication system according to an embodiment of the present invention.

Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings.

In describing the embodiments, descriptions of technical contents that are well known in the technical field to which the present disclosure pertains and are not directly related to the present disclosure will be omitted. This is to more clearly convey the gist of the present disclosure by omitting unnecessary description.

For the same reason, some elements in the accompanying drawings are exaggerated, omitted, or schematically illustrated. In addition, the size of each component does not fully reflect the actual size. The same reference numerals are assigned to the same or corresponding components in each drawing.

Advantages and features of the present disclosure, and a method of achieving them will be apparent with reference to the embodiments described below in detail together with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below, but may be implemented in a variety of different forms, and only these embodiments make the present disclosure complete, and those skilled in the art to which the present disclosure pertains. It is provided to fully inform the person of the scope of the present disclosure, and the present disclosure is only defined by the scope of the claims. The same reference numerals refer to the same elements throughout the specification.

At this time, it will be appreciated that each block of the flowchart diagrams and combinations of the flowchart diagrams may be executed by computer program instructions. Since these computer program instructions can be mounted on the processor of a general purpose computer, special purpose computer or other programmable data processing equipment, the instructions executed by the processor of the computer or other programmable data processing equipment are described in the flowchart block(s). It creates a means to perform functions. These computer program instructions can also be stored in computer-usable or computer-readable memory that can be directed to a computer or other programmable data processing equipment to implement a function in a particular way, so that the computer-usable or computer-readable memory It is also possible for the instructions stored in the flow chart to produce an article of manufacture containing instruction means for performing the functions described in the flowchart block(s). Since computer program instructions can also be mounted on a computer or other programmable data processing equipment, a series of operating steps are performed on a computer or other programmable data processing equipment to create a computer-executable process to create a computer or other programmable data processing equipment. It is also possible for instructions to perform processing equipment to provide steps for executing the functions described in the flowchart block(s).

In addition, each block may represent a module, segment, or part of code that contains one or more executable instructions for executing the specified logical function(s). In addition, it should be noted that in some alternative execution examples, the functions mentioned in the blocks may occur out of order. For example, two blocks shown in succession may in fact be executed substantially simultaneously, or the blocks may sometimes be executed in the reverse order depending on the corresponding function.

In this case, the term'~ unit' used in this embodiment refers to software or hardware components such as FPGA or ASIC, and'~ unit' performs certain roles. However,'~ part' is not limited to software or hardware. The'~ unit' may be configured to be in an addressable storage medium, or may be configured to reproduce one or more processors. Thus, as an example,'~ unit' refers to components such as software components, object-oriented software components, class components, and task components, processes, functions, properties, and procedures. , Subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. Components and functions provided in the'~ units' may be combined into a smaller number of elements and'~ units', or may be further separated into additional elements and'~ units'. In addition, components and'~ units' may be implemented to play one or more CPUs in a device or a security multimedia card. In addition, in an embodiment, the'~ unit' may include one or more processors.

In the detailed description of the embodiments of the present disclosure, the wireless access network New RAN (NR) according to the 5G mobile communication standard specified by 3GPP, a mobile communication standard standardization body, and a packet core (5G System, or 5G Core Network, or NG Core: Next Generation Core) is the main target, but the main subject of the present disclosure is applicable to other communication systems having a similar technical background with slight modifications within the scope of the present disclosure. It will be possible at the judgment of a person with skilled technical knowledge in the technical field of the present disclosure.

For convenience of description below, some terms and names defined in the 3rd Generation Partnership Project Long Term Evolution (3GPP) standard (5G, NR, LTE, or similar system standard) may be used. However, the present disclosure is not limited by the terms and names, and may be equally applied to systems conforming to other standards.

In addition, terms for identifying access nodes used in the following description, terms for network entities, terms for messages, terms for interfaces between network entities, various identification information Terms and the like that refer to them are exemplified for convenience of description. Therefore, it is not limited to the terms used in the present disclosure, and other terms that refer to objects having an equivalent technical meaning may be used.

The present disclosure relates to a method for supporting the operation of an unmanned aerial vehicle in a mobile communication system conforming to the 3GPP standard, and devices or objects described below may interact to achieve the object of the invention.

In this disclosure, a terminal refers to an unmanned aerial vehicle and an unmanned aerial vehicle controller, and the form of these two terminals is composed of UAS (Unmanned Aerial Vehicle). System).

In the present disclosure, the unmanned aerial vehicle is capable of flying, such as a hobby or commercial drone that can be controlled at a short distance, and an unmanned reconnaissance aircraft operated through a specific track, and the pilot is operated remotely or autonomously to perform the purpose without boarding the aircraft body. Collectively. In addition, the unmanned aerial vehicle subject to the present disclosure is equipped with a device capable of communication such as a mobile communication network, Wi-Fi, and Bluetooth, so that it is external to the remote controller of the unmanned aerial vehicle, an unmanned aerial vehicle capable of short-range communication, or a control center. It is possible to communicate with the located entity via wireless.

In the present disclosure, the unmanned aerial vehicle controller may refer to a specific physical device, or may be a form of software running on a cloud or a specific server. It has the function of accessing the 3GPP network through LTE (E-UTRA, GERAN, UTRA), 5G NR, and Non-3GPP networks. ) May be used to communicate between short-range terminals. In addition, in order to perform a role as a terminal conforming to the 3GPP standard, an apparatus and protocol for communicating with a base station and a core network must be supported. In the unmanned aerial vehicle, a human aviator does not board an aircraft and receives an operation-related signal using a communication network, and is operated accordingly.

Unmanned aerial vehicles may temporarily enter an area where communication is not possible, cause interference to other terminals operating on the ground due to high altitude, or a situation in which communication becomes unstable due to interference. Therefore, the mobile communication system must provide a method to maintain high connectivity for the safe operation of such unmanned aerial vehicles. In areas where communication is temporarily unavailable, it is necessary to communicate with buildings, aircraft, other unmanned aerial vehicles, or objects floating in the air. We also need a way to avoid collisions from the same thing.

Meanwhile, various embodiments of the present disclosure include, for example, a method of supporting the operation of an Unmanned Aerial System (UAS) through a mobile communication system conforming to the 3GPP standard.

According to the current 3GPP standard document, UAS is composed of UAV (Unmanned Aerial Vehicle) and UAV Controller, and UAV refers to an aircraft that is operated without a person on board. The UAV constituting the UAS and the UAV Controller do not have to be in a one-to-one relationship. In addition, UAS is connected to the UTM (Unmanned Aerial Traffic Management) system, which is responsible for controlling UASs, and performs legitimate user verification procedures through verification of UAS authentication, UAV and UAV controller security keys, and static necessary for unmanned aerial control. Or, it can provide various functions such as providing real-time information, route approval through confirmation of flight route purpose, and forced transfer of UAS control authority according to an emergency situation. Therefore, the 3GPP mobile communication system must support the network connectivity of UAVs and UAV controllers constituting the UAS, and provide network services efficiently so that devices constituting each UAS can be controlled through UTM. The role of 3GPP is not simply to provide connectivity between UAS terminals or UTMs, but additional network services may be provided. Representatively, the subject of UAS authentication is UTM, and in this process, the core network of the mobile communication system additionally authenticates the UAS terminals and transmits the result to the UTM to reinforce the authentication process. Second, 3GPP can improve the accuracy and reliability of the location of the UAS terminal by additionally using the location information of the terminal transmitted by the core network, not only the location information sent by the UAS terminals. Some embodiments of the present disclosure also include a method capable of helping to calculate the final movement path of the unmanned aerial vehicle by additionally utilizing information such as a service restricted area of mobile communication transmitted from the core network. In the present disclosure, when operating an initial unmanned aerial vehicle through a mobile communication network, a method of optimizing control signals that may occur in the mobile communication network does not generate unnecessary signals in the operation of the unmanned aerial vehicle is included. In addition, it moves in the air at a high speed. It includes a method of estimating the location of an aircraft to perform and a method of reducing the probability of paging failure through the method. In addition, it also includes a method of supporting the purpose of the unmanned aerial vehicle to achieve special purposes conducive to the public interest such as long-term transportation and fire suppression by dynamically changing service restricted areas according to the purpose of the unmanned aerial vehicle. Is a method of optimally allocating the service restricted area and registration area of the terminal in consideration of the operation purpose and route of each UAS in order to effectively support the mobility of the terminal moving in the air in the mobile communication system when operating the UAS in the above situation. Includes. If the service restriction area of the terminal is not properly allocated, the communication service of the terminal may be cut off because the terminal cannot use a communication service in a specific area or handover to a specific base station is not possible. In the case of a registration area, it is an arbitrary area for the terminal to determine its approximate location, and the terminal can use the service only within the registration area allocated at the time of registration. In the case of a terminal that has moved out of the registration area, the registration procedure must be performed again to receive and update the new registration area of the terminal, and in this process, unnecessary exchange of control signals between the mobile communication core network and the terminal may occur. In this disclosure, the service restriction area is changed in consideration of the operation purpose and route of UAS, and the registration area considering the route is allocated in the changed service restriction area to minimize the control signal between the network and the terminal, through which the terminal can communicate stably. Includes a way to get services provided.

1 shows each terminal, device, and objects for implementing the present disclosure. Referring to FIG. 1, as entities for implementing the present disclosure, a UAV 101, a UAV controller 102, a terminal device (ME) 103 that shares a UAV or service, and a UAS 104 composed of a UAV and a UAV controller. ), base station 105, AMF (106), SMF (107), PCF (108), NEF (109), UDM or UDR (110), UPF (111), and/or unmanned aerial vehicle traffic supporting wireless communication A control system (UTM) 112 may be included, and the configuration and function of each entity will be exemplarily described below.

(R)AN (Radio Access Network) refers to a technology used for wireless communication between a base station and a terminal, such as 5G-NR, E-UTRAN, UTRAN, and GERAN, and the terminal uses mobile communication radio technology for wireless communication. A supported base station connects to an eNB or gNB to receive communication services. The base station may interact with the core network and transmit the control signal or data received from the terminals to the device located in the core network to receive configuration, transmit/receive data, or perform procedures for management. In addition, the terminal can be connected to the data network by using a side link technology such as Prose (Proximity Service) that performs direct communication between the terminal and the terminal without being connected to the base station, or by using a non-3GPP wireless access technology such as WiFi and Bluetooth. .

Hereinafter, among various elements constituting the core network, devices directly related to the present disclosure will be exemplarily described.

AMF (Access and Mobility Management Function) is a device for managing access and mobility of a terminal, and serves as a terminal-core network endpoint through which the terminal connects to other devices in the core network via the RAN. Functions provided by AMF may include, for example, functions such as terminal registration, connection, reachability, mobility management, access confirmation/authentication, and mobility event generation.

SMF (Session Management Function) performs a PDU session management function of the terminal. For example, SMF establishes, modifies and releases sessions and manages sessions through tunnel maintenance between UPF and AN required for this, IP address allocation and management function of the terminal, ARP proxy function, user plane selection, and Functions such as control, traffic processing control in UPF, and charging data collection control can be performed.

PCF (Policy Control Function) plays the role of determining and dropping policies for access/mobility and session management applied by AMF and SMF. For example, the PCF manages the behavior of the entire network and can provide policies to be implemented to NFs (Network Functions) constituting the control plane. In addition, the PCF can access information related to policy decisions by accessing the Unified Data Repository (UDR).

NEF (Network Exposure Function) is in charge of transmitting or receiving events occurring in the mobile communication network and capabilities to be erased to the outside. For example, NEF performs functions such as safe provisioning of external application information in the core network, internal/external information conversion, and redistribution after storing functions received from other NFs in UDR.

UDM (Unified Data Management) and UDR (Unified Data Repository) are independent network functions, but in this embodiment, their functions and roles are similarly used and described at the same time. UDM is, for example, generation of AKA authentication information for 3GPP security, processing of user IDs, inverse concealment of secured user IDs (Subscriber Concealed ID, SUPI), list management of NFs currently supporting the UE, subscriber information (subscription) management, SMS management, etc. can be performed. The UDR may perform a function of storing and providing subscriber information managed by the UDM, structured data for exposure, and application data related to NEF or service.

UPF (User Plane Function) performs the role of processing actual user data, and processes packets to deliver packets generated by the terminal to the external data network or to deliver data from the external data network to the terminal. Carry out. The main functions provided by UPF include, for example, acting as an anchor between radio access technologies, providing connectivity with PDU sessions and external data networks, packet routing and forwarding, packet inspection, and user plane policy. Features such as application, traffic usage report generation, buffering, etc. may be included.

NWDAF (Network Data Analytics Function) collects events or information occurring within the network and uses tools such as analysis tools or machine learning to provide statistics, predictions, and recommendations related to specific information. It can be delivered to NF, AF, and OAM. For example, the NWDAF may perform functions such as collecting data from NF/AF/OAM, registering NWDAF services and exposing metadata, and providing network analysis information to NF/AF.

UTM performs the role of controlling the traffic of unmanned aerial vehicles, where traffic includes the role of controlling the actual operation of physical unmanned aerial vehicles, not network traffic. The main functions provided by UTM include, for example, authentication of UAVs and UAV controllers, authentication of UAS configurations, provision of information for efficient operation of unmanned aerial vehicles, authentication and route confirmation of unmanned aerial vehicles scheduled to be operated, and current route and location of unmanned aerial vehicles. In case of an emergency, functions such as control of unmanned aerial vehicles may be included. The entity that manages the UTM can be a government or public institution, and an agent delegated by them can operate the UTM. In the present disclosure, the UTM may serve as an application function (AF) or interlock with AF to provide information related to the operation of the unmanned aerial vehicle to the control plane through NEF of the 3GPP mobile communication network. In addition, in mobile communication networks, AF is a device or entity that communicates with the 3GPP core network to support specific services, and the currently supported functions provide information on traffic routing (Application influence on traffic routing), access to NEF and service or terminal related functions. It can perform functions such as providing information and providing necessary information to the PCF. In the present disclosure, when the UTM is operated from a provider that the mobile communication network operator can trust, it may be regarded as a trusted AF (Trusted AF).

The information exchange and control signal exchange between the above-described entities use procedures, interfaces, and protocols defined in the 3GPP standard specification document. However, all terms included in the present disclosure are not limited by the 3GPP terms and names, and may be equally applied to systems and devices conforming to other standards. In describing the embodiments of the present disclosure in detail, the communication standard defined by the 3GPP will be the main target, but the main subject of the present disclosure does not significantly depart from the scope of the present disclosure to other communication systems having a similar technical background. It can be applied with slight modifications in the range of, and this will be possible by judgment of a person having ordinary technical knowledge in the technical field of the present disclosure.

In the various embodiments of the present invention described below, at least one embodiment may be performed independently or in association with each other.

[First Embodiment]-UAS authentication data delivery method using Parameter Provision

Mobile communication systems, such as UAVs and UAV controllers using 5G mobile communication systems, undergo a registration process in the same way as a terminal using a general 3GPP mobile communication network, and receive authentication and authorization related to the use of the mobile communication network. . In this process, the core network supports the terminals constituting the UAS to communicate with the UTM. The communication process with the UTM is 1) transmitting UAS-related information to the UTM through the user plane using a PDU session, 2) transmitting through the Secondary DN authentication defined in the 3GPP standard during the PDU session creation process, or 3) NAS (Non Access Stratum) can be used to support communication to support authentication between the UAS component device and the UTM through the control plane. In the present disclosure, it is assumed that the terminal is authenticated to the 3GPP network or that information exchange for authentication is performed between the performing UAS and the UTM during the authentication procedure. In addition, the UAS and UTM may exchange authentication-related information through a separate method other than the above-described method to deliver additional information to the 3GPP core network.

The authentication between the UAS component device and the UTM is based on UAS operation by considering the legitimate user, correct route, normal device status, flight availability, flight purpose confirmation, flight paths and/or schedules of other unmanned aerial vehicles or other vehicles. Verify flight operation.

UAV is for UTM authentication, for example, Unique Identity, UAV UE Capability of the UAV, Make & model, Serial Number, and Take-off weight. ), Position, Owner Identity, Owner Address, Owner Contact details, Owner certification, Take-off location and time, Flight purpose (Mission type), route (Route data), and / or operating status (Operating status), etc. can be transmitted to the UTM as authentication information (data). In this case, the UAV may deliver the authentication information to the UTM through the 3GPP core network.

UAV Controller is for UTM authentication, for example, Unique Identity, UAV controller UE Capability of the UAV controller, Position, Owner Identity, Owner Address, Owner Owenr Contact details, Owner certification, the identity of the UAV operator who operate the UAV controller, and/or UAV operator license and certification. ), etc. can be transmitted to the UTM as authentication information (data). In this case, the UAV Controller may deliver the authentication information to the UTM through the 3GPP core network.

When the 3GPP core network delivers the authentication information of the UAV or UAV controller to the UTM, for example, IMSI (International Mobile Subscriber Identity), IMEI (International Mobile Equipment Identity), MSISDN (Mobile Station International Subscriber Directory Number) and GPSI (Generic Public Subscription Identifier) can be additionally delivered to UTM, which can be used to authenticate UAS components.

Hereinafter, with reference to FIG. 2, a first embodiment of the present disclosure will be exemplarily described.

FIG. 2 includes a method of optimizing a service restricted area and a registered area of a UAS terminal by a UTM (AF) authenticating the UAS operation and transmitting the UAS operation information acquired in this process to the 3GPP core network.

Step 1-The UAV 201 or UAV controller 201 transmits an initial registration request message to the AMF 203 in the same way as a general terminal in order to use the 3GPP mobile communication network. At this time, the behavior of the initial terminal (UE) for transmission of the registration message, connection with the base station 202, and signal transmission procedures of the base station follow the procedures defined in the 3GPP standard. Through the registration procedure, the terminal is successfully registered in 3GPP mobile communication and receives information related to the use of the terminal. In addition, it is possible to use procedures such as NAS transport for transmitting signals to the control plane and establishing a PDU session for data transmission through the user plane afterwards. During the registration process, the AMF may establish an AM Policy Association to obtain the terminal's access and mobility-related policies from the PCF 204. Additionally, when the AMF determines that the terminal is a UAS terminal through the subscriber information of the terminal, it can establish an AM Policy Association with the PCF. At this time, the PCF applies for an event-related subscription to the UDM in order to receive an event related to SDM (Subscriber Data Management) that may occur in a later step. During the registration process, the AMF can selectively apply to the UDM for SDM subscription to the terminal in order to obtain the subscriber information of the terminal from the UDM and to determine the change. If the AMF recognizes that the terminal sending the registration request is the UAS terminal, and it is recognized at the stage of importing the SDM, and has not requested subscription to the SDM change, the AMF subscribes to the UDM to detect the change of subscriber information. Can be requested.

The state of the terminal immediately after registration is successfully completed is a state in which only the 3GPP registration procedure has been completed, and the authentication related to the operation of the unmanned aerial vehicle through the UTM 207 has not been completed. Accordingly, the terminal may not be able to communicate through an external data network according to a mobile communication network operation policy or a service contract between the mobile communication operator and the UTM operator.

Step 2-When the terminal is successfully registered in the 3GPP system, the terminal performs authentication of the UAV, the UAV controller, and the UAS composed of the UAV and the UAS controller through the UTM. In this process, each terminal delivers the information necessary for the above-described authentication to the UTM. Additionally, it can be seen that the core network is a device that can be configured as a UAS based on subscriber information of UAV and UAV controller, and that UTM and additional authentication procedures can occur. Through this, the core network can provision a path through which control signals or data traffic occurring later in the UTM can be transmitted to the UTM. At this time, data transfer between the terminal and the UTM is as described above: 1) authentication data is transmitted to the UTM as general data through the user plane using a PDU session, and 2) authentication through Secondary DN authentication in the process of authenticating the PDU session. Data delivery, 3) delivery through the NAS Transport method through NEF using the control plane can be used. In the present disclosure, at least one of three methods may be supported. In the process of transmitting the authentication data of the UAS terminal to the UTM through the above method, the 3GPP core network is the identifier and location information used by 3GPP such as IMEI, IMSI, and MSISDN, and the terminal communication status (access radio communication technology, radio access capability), etc. The additional information of can be delivered to the UTM together with the UAS authentication data transmitted by the terminal.

Upon receiving UAS authentication information from the UTM terminal and the 3GPP core network, the UTM may permit or reject UAS flight in consideration of the received information, internal policies, current regional conditions, and routes. In the case of rejection, the UTM can communicate the cause of the rejection failure to the terminal. For example, the UTM may recognize that the flight is not permitted on a specific route, and may include in the flight rejection message that the flight prohibition route of the terminal is included. If the reason for rejection is correctable by recognizing the reason for rejection, the terminal may transmit a new authentication message to UTM through repetition of step 2 to receive a new authentication procedure.

For detailed authentication-related technologies and procedures, although outside the scope of the present invention, generally used authentication technologies may be applied.

Step 3-When the authentication of the terminal constituting the UAS is successfully performed through the UTM, the UTM may inform the 3GPP (or 3GPP core network) of the authentication result through the NEF 206. At this time, the UTM may be the same as the AF, or the UTM may transmit authentication-related information through the NEF of 3GPP through an intermediate device supporting AF. For example, the UTM may transmit information related to the UAS terminal to the NEF by using the Nnef_ParameterProvision_Update Request provided by NEF. The transmitted authentication data may be contained in a data container named, for example, UAS Authorization Data and transmitted to NEF through UTM (AF). UAS Authorization Data (UAS Authorization Data Container) includes the external identifier of the terminal (GPSI), UTM authentication success/failure status (Authorization Status), UAV type (UAV Type), operation purpose (UAV mission), route, and flight. Information including flight time, owner information, and/or pilot information may be included, which may be transmitted to NEF. In this process, if the UTM knows the IMSI, IMEI, and MSISDN of the terminal, it may be transmitted as an identifier of the terminal instead of GPSI. In this disclosure, the UAS Authorization data container is used to store and transmit UAS authentication-related information. However, if the transmitted information (data) is the same or similar, each data is transmitted to NEF without using a container to obtain the same effect. May be.

Optionally, if the authentication fails, there is no need to proceed with the subsequent process.

Step 3a-optional process. NEF verifies that the data sent by UTM is normal, and verifies that the message is from UTM with legitimate use and access rights. If it is confirmed that the message is normally transmitted by UTM, NEF converts the information that needs to be converted into information used inside 3GPP among the transmitted authentication data into a form used inside the core network. For example, GPSI can be converted into SUPI and IMSI used in the core network, and route information can be converted into a list of TAI. In addition, when the state is represented by an encoding method for concise expression of information, such information may be converted. For example, if Authorization status="True", it can be converted into information in a form used by internal devices and objects such as Authorization status=1 for concise expression.

Step 4-NEF stores the UTM authentication-related information delivered in Step 3 in the UDM. UDM can internally store authentication data in UDR using services provided by UDR such as Nudr_DM_Query and Nudr_DM_Update. When storing data in UDM, the UAS Authorization data container can be directly saved, and each component inside each container can be saved as a separate field. If there is a field corresponding to the type of subscriber information according to the manager's policy, the corresponding field of the subscriber information or the terminal context can be updated. The method of directly storing the container, storing each data, and updating a specific field of subscriber information may be selectively used, and may be used simultaneously or in combination for reliability according to a policy. When saving, the UDM can additionally store the UTM's AF ID and Transaction Reference ID information to find the UTM that delivered the message separately from the UAS Authorization data container. When the storage of the requested information is completed, the UDM can deliver a notification that the requested parameter provision has been completed to the NEF.

Step 5-When receiving a response for provisioning from UDM, NEF may transmit a response for ParameterProvision to UTM. For example, NEF may transmit a response to ParameterProvision to UTM using Nnef_ParameterProvision_Update Response provided by NEF.

If there is a change in subscriber-related information or terminal context due to the UAS Authorization data stored in Step 6-Step 4, the UDM notifies NFs that have subscribed to the event that the UAS Authorization data is newly provisioned and that the subscriber information has been changed. For example, PCF and AMF subscribed to the event in step 1 may correspond to these NFs. Therefore, the AMF and PCF supporting the UAS terminal can know that the UAS Authorization data has been newly updated through the SDM Notification event sent by the UDM, and the UAS Authorization data is delivered to the PCF and AMF within a notification message (e.g., Nudm_SDM_notification_notify). do.

Step 7-The PCF receiving the UAS Authorization data from the UDM is the UTM authentication success/failure status of the UAS terminal in the data (Authorization Status), UAV type (UAV Type), operation purpose (UAV mission), route, and flight. Flight time, owner information, and/or pilot information can be known. Through this, the PCF may change the mobility restriction of the UAS terminal according to an internal policy or a contract with the UTM operator in advance. Mobility restrictions defined in 3GPP largely utilize a combination of Radio Access Technology (RAT) restrictions (RAT Restriction), Forbidden Area, Service Area Restrictions, and Core Network Type Restriction. do.

RAT restriction prohibits access to the PLMN using a specific RAT defined by 3GPP. The prohibited area prohibits all attempts to communicate to a specific PLMN within the area included in the prohibited area list. Service Area Restrictions can be broadly divided into two types of areas, which can be divided into Non-allowed areas and Allowed Areas, and are organized in the form of a list for each area. Can be. A general communication service can be used within the service allowed area, and within the service unlicensed area, the terminal is not allowed to make a service request or SM signaling to the core network. Finally, the restriction on access to the core network prohibits restrictions on certain types of core networks, such as EPC or 5GC.

The PCF receiving UAS Authorization data from UTM may refer to this and create a new mobility restriction-related policy. For example, the PCF may temporarily change the list of out-of-service or out-of-service areas through a contractual relationship with UTM or recognized for its specific purpose, such as fire suppression or long-term transport. At this time, in order to consider whether the PCF is allowed or not, the UTM authentication success/failure status (Authorization Status), UAV type (UAV Type), operation purpose (UAV mission), route, flight time (Flight time), owner information , And/or pilot information may be considered in combination. This allows the unmanned aerial vehicle to temporarily release or change certain mobility restrictions during the operation in order to achieve its purpose. These allowances may be allowed for a specific period through a specific timer, or temporarily applied during this registration period.

Step 8-The PCF delivers the newly created mobility-related policy to the AMF currently supporting the UAS terminal through Npcf_AMPolicyControl_UpdateNotify.

Step 9-Upon receiving the new mobility-related policy from the PCF, the AMF updates the information related to access and mobility in the existing UE context with the received information. Additionally, the PCF may create a new registration area of the terminal based on the updated mobility-related policy. In the newly created registration area, an area in which the control signal can be optimized within the operating range of the unmanned aerial vehicle is calculated using the UE's path and flight time information provided in the previous step.

Step 10-The AMF delivers the updated mobility restriction policy and registration area to the UE through a mobility related UE configuration procedure defined by 3GPP in order to update the newly transmitted mobility related policy and registration area to the UE. If necessary, the terminal can perform a new registration procedure. In this process, the AMF may deliver RAN support information (Core Network Assisted Ran Parameters) related to the behavior of the terminal. This information includes Expected UE Behavior, Expected Handover Behavior, Expected UE Mobility, Stationary or Mobile, Expected UE Trajectory, and/or Expected UE Behavior information of the terminal excluding the path may be included. Such information can be generated by AMF using UAS Authorization data.

[Second Embodiment]-UAS authentication data delivery method extending Expected UE Behavior

The present disclosure includes a method of transmitting the flight purpose, time, and route of an unmanned aerial vehicle certified by UTM by extending Expected UE Behavior defined in the current 3GPP standard. A method of extending the expected terminal behavior to include the UTM authentication method is possible in the form of Tables 1 and 2. In the case of Table 1, UAS Authorization data is expanded as one field (UAS Authorization data is added as a new field), and Table 2 is expanded by mapping each data of authentication information to one field (UAS Authorization data added for each factor). ). The information contained in both methods is the same.

Expected UE Behavior parameter Description Expected UE Moving Trajectory Identifies the UE's expected geographical movement Example: A planned path of movement Stationary Indication Identifies whether the UE is stationary or mobile [optional] Communication Duration Time Indicates for how long the UE will normally stay in CM-Connected for data transmission.Example: 5 minutes.
[optional] Periodic Time Interval Time of periodic communication Example: every hour.
[optional] Scheduled Communication Time Time and day of the week when the UE is available for communication.Example: Time: 13:00-20:00, Day: Monday.
[optional] Battery Indication Identifies power consumption criticality for the UE: if the UE is battery powered with not rechargeable/not replaceable battery, battery powered with rechargeable/replaceable battery, or not battery powered.[optional] Traffic Profile Identifies the type of data transmission: single packet transmission (UL or DL), dual packet transmission (UL with subsequent DL or DL with subsequent UL), multiple packets transmission[optional] Scheduled Communication Type Indicates that the Scheduled Communication Type is Downlink only or Uplink only or Bi-directional [To be used together with Scheduled Communication Time] Example: <Scheduled Communication Time>, DL only.
[optional] UAS authorization data Contains information of scheduled UAS flight operation. It can include authorization status, UAV type, UAV mission, route, flight time, owner information, operator information.

Expected UE Behavior parameter Description Expected UE Moving Trajectory Identifies the UE's expected geographical movement Example: A planned path of movement Stationary Indication Identifies whether the UE is stationary or mobile [optional] Communication Duration Time Indicates for how long the UE will normally stay in CM-Connected for data transmission.Example: 5 minutes.
[optional] Periodic Time Interval Time of periodic communication Example: every hour.
[optional] Scheduled Communication Time Time and day of the week when the UE is available for communication.Example: Time: 13:00-20:00, Day: Monday.
[optional] Battery Indication Identifies power consumption criticality for the UE: if the UE is battery powered with not rechargeable/not replaceable battery, battery powered with rechargeable/replaceable battery, or not battery powered.[optional] Traffic Profile Identifies the type of data transmission: single packet transmission (UL or DL), dual packet transmission (UL with subsequent DL or DL with subsequent UL), multiple packets transmission[optional] Scheduled Communication Type Indicates that the Scheduled Communication Type is Downlink only or Uplink only or Bi-directional [To be used together with Scheduled Communication Time] Example: <Scheduled Communication Time>, DL only.
[optional] UAS authorization status Indicate the UE has been authorized by UTM UAV type Identifies the type of UAV UAV mission Identifies the mission of UAV. It can be represented as categories such as emergency, logistics, patrol, sensing, etc. Route The scheduled route of UAV. Flight time The scheduled flight time of UAV Owner and operator information The contact or detailed information about UAV owner or operator.

Hereinafter, a second embodiment of the present disclosure will be exemplarily described with reference to FIG. 3.

Step 1-The UAV 301 or the UAV controller 301 transmits an initial registration request message to the AMF 303 in the same way as a general terminal in order to use the 3GPP mobile communication network. At this time, the initial UE behavior for registration message delivery, connection with the base station 302, and signal delivery procedures of the base station follow the procedures defined in the 3GPP standard. Through the registration procedure, the terminal is successfully registered in 3GPP mobile communication and receives information related to the use of the terminal. In addition, it is possible to use procedures such as NAS transport for transmitting signals to the control plane and establishing a PDU session for data transmission through the user plane. During the registration process, the AMF may establish an AM Policy Association to obtain the terminal's access and mobility-related policies from the PCF (304). Additionally, when the AMF determines that the terminal is a UAS terminal through the subscriber information of the terminal, it can establish an AM Policy Association with the PCF. At this time, the PCF applies for an event-related subscription to the UDM in order to receive an event related to SDM (Subscriber Data Management) that may occur in a later step. During the registration process, the AMF can selectively apply to the UDM for SDM subscription to the terminal in order to obtain the subscriber information of the terminal from the UDM and to determine the change. If AMF recognizes the UAS terminal and the terminal that sent the registration request is aware of the UAS terminal, and has not subscribed to the SDM change, the AMF will request SDM subscription to the UDM to detect the change of subscriber information. I can.

The state of the terminal immediately after registration is successfully completed is a state in which only the 3GPP registration procedure has been completed, and the authentication related to the operation of the unmanned aerial vehicle through the UTM 307 has not been completed. Accordingly, the terminal may not be able to communicate through an external data network according to a mobile communication network operation policy or a service contract between the mobile communication operator and the UTM operator.

Step 2-When the terminal is successfully registered in the 3GPP system, the terminal performs authentication of the UAV, the UAV controller, and the UAS composed of the UAV and the UAS controller through the UTM. In this process, each terminal delivers the information necessary for the above-described authentication to the UTM. Additionally, it can be seen that the core network is a device that can be configured as a UAS based on subscriber information of UAV and UAV controller, and that UTM and additional authentication procedures can occur. Through this, the core network can provision a path through which control signals or data traffic occurring later in the UTM can be transmitted to the UTM. At this time, data transfer between the terminal and the UTM is as described above: 1) authentication data is transmitted to the UTM as general data through the user plane using a PDU session, and 2) authentication through Secondary DN authentication in the process of authenticating the PDU session. Data delivery, 3) delivery through the NAS Transport method through the NEF 306 using the control plane may be used. In the present disclosure, at least one of three methods may be supported. In the process of transmitting the authentication data of the UAS terminal to the UTM through the above method, the 3GPP core network is the identifier and location information used by 3GPP such as IMEI, IMSI, and MSISDN, and the terminal communication status (access radio communication technology, radio access capability), etc. The additional information of can be delivered to the UTM together with the UAS authentication data transmitted by the terminal.

Upon receiving UAS authentication information from the UTM terminal and the 3GPP core network, the UTM may permit or reject UAS flight in consideration of the received information, internal policies, current regional conditions, and routes. In the case of rejection, the UTM can communicate the cause of the rejection failure to the terminal. For example, the UTM may recognize that the flight is not permitted on a specific route, and may include in the flight rejection message that the flight prohibition route of the terminal is included. If the reason for rejection is correctable by recognizing the reason for rejection, the terminal may transmit a new authentication message to UTM through repetition of step 2 to receive a new authentication procedure.

UAV is for UTM authentication, for example, Unique Identity, UAV UE Capability of the UAV, Make & Model, Serial Number, and Flight Weight (Take-off). weight), Position, Owner Identity, Owner Address, Owenr Contact details, Owner certification, Take-off location and time , Flight purpose (Mission type), route (Route data), and / or operating status (Operating status), etc. can be transmitted.

UAV Controller for UTM authentication, for example, Unique Identity, UAV controller UE Capability of the UAV controller, Position, Owner Identity, Owner Address, Owenr Contact details, Owner certification, the identity of the UAV operator who operate the UAV controller, and/or UAV operator license and certificate. certification).

The 3GPP core network delivers the authentication information of the UAV or UAV controller described above to the UTM, so that the unique identifier of the terminal used in 3GPP is IMSI (International Mobile Subscriber Identity), IMEI (International Mobile Equipment Identity), MSISDN (Mobile Station International). Subscriber Directory Number), and/or a Generic Public Subscription Identifier (GPSI) may additionally be transmitted to the UTM, which may be used to authenticate the UAS configuration device.

For detailed authentication related technologies and procedures, although outside the scope of the present invention, generally used authentication technologies may be applied.

Step 3-When the authentication of the terminal constituting the UAS is successfully performed through the UTM, the UTM may inform the 3GPP core network of the authentication result through the NEF 206. At this time, the UTM may be the same as the AF, or the UTM may transmit authentication-related information through the NEF of 3GPP through an intermediate device supporting AF. For example, the UTM may transmit information related to the UAS terminal to the NEF by using the Nnef_ParameterProvision_Update Request provided by NEF. The transmitted data is an Expected UE Behavior factor, and the transmitted data follows the factors in Table 1 or 2, for example. The terminal expected behavior factor is determined in consideration of the authentication result of the terminal, and may be transmitted to NEF through UTM (AF). Among the transmitted data, UAV related factors are the external identifier of the terminal (GPSI), UTM authentication success/failure status (Authorization Status), UAV type (UAV Type), operation purpose (UAV mission), route, flight time Flight time), owner information, and/or pilot information, and this information can be communicated to NEF. In this process, if the UTM knows the IMSI, IMEI, and MSISDN of the terminal, it can transmit it as the identifier of the terminal instead of GPSI. In FIG. 3, UAS-related factors are added by extending the terminal behavior factor, but it is also possible to transmit UAS authentication-related information using a UAS Authorization data container as shown in Table 1. In addition, additional behavioral information or network configuration parameters related to the terminal may be additionally calculated and transmitted. The network configuration factor defined in 3GPP may include a maximum response time, a maximum latency, and/or a suggested number of downlink packets.

Optionally, if the authentication fails, there is no need to proceed with the subsequent process.

Step 3a-optional process. NEF verifies that the data sent by UTM is normal, and verifies that the message is from UTM with legitimate use and access rights. If it is confirmed that the message is normally transmitted by UTM, NEF converts the information that needs to be converted into information used inside 3GPP among the transmitted authentication data into a form used inside the core network. For example, GPSI can be converted into SUPI and IMSI used in the core network, and route information can be converted into a list of TAI. In addition, when the state is expressed in an encoding method for concise expression of information, such information may be converted. For example, if Authorization status="True", it can be converted into information in a form used by internal devices and objects such as Authorization status=1 for concise expression.

Step 4-NEF stores the UTM authentication-related information delivered in Step 3 in the UDM. UDM can internally store authentication data in UDR using services provided by UDR such as Nudr_DM_Query and Nudr_DM_Update. When saving, the UDM can additionally store the UTM's AF ID and Transaction Reference ID information to find the UTM that delivered the message separately from the UAS Authorization data container. When the storage of the requested information is completed, the UDM can deliver a notification that the requested parameter provision has been completed to the NEF.

Step 5-When receiving a response for provisioning from UDM, NEF may transmit a response for ParameterProvision to UTM. For example, NEF may transmit a response to ParameterProvision to UTM using Nnef_ParameterProvision_Update Response provided by NEF.

Step 6-When there is a change in subscriber-related information due to the terminal expected behavior data stored in Step 4, the UDM notifies NFs that have subscribed to the event that the subscriber information or the terminal information has been changed by newly provisioning the data. For example, PCF and AMF subscribed to the event in step 1 may correspond to these NFs. Therefore, the AMF and PCF supporting the UAS terminal can be informed through the SDM Notification event that the UDM sends that the terminal expected behavior has been newly updated, and the terminal behavior information is delivered to the PCF and AMF within a notification message (eg, Nudm_SDM_notification_notify) do.

Step 7-The PCF, which received the terminal expected behavior data from the UDM, is the UAS terminal's UTM authentication success/failure status (Authorization Status), UAV type (UAV Type), operation purpose (UAV mission), route, and Flight time, owner information, and/or pilot information can be known. Through this, the PCF may change the mobility restriction of the UAS terminal according to an internal policy or a contract with the UTM operator in advance. Mobility restrictions defined in 3GPP largely utilize a combination of RAT Restriction, Forbidden Area, Service Area Restrictions, and Core Network Type Restriction.

RAT restriction prohibits access to the PLMN using a specific RAT defined by 3GPP. The prohibited area prohibits all attempts to communicate to a specific PLMN within the area included in the prohibited area list. Service Area Restrictions can be broadly divided into two types of areas, which can be divided into Non-allowed areas and Allowed Areas, and can be organized in the form of a list for each area. I can. A general communication service can be used within the service allowed area, and within the service unlicensed area, the terminal is not allowed to make a service request or SM signaling to the core network. Finally, the restriction on access to the core network prohibits restrictions on certain types of core networks, such as EPC or 5GC.

The PCF receiving the terminal expected behavior data from the UTM may refer to this and create a new mobility restriction-related policy. For example, the PCF may temporarily change the list of out-of-service or out-of-service areas through a contractual relationship with UTM or recognized for its specific purpose, such as fire suppression or long-term transport. At this time, in order to consider whether the PCF is allowed or not, the UTM authentication success/failure status (Authorization Status), UAV type (UAV Type), operation purpose (UAV mission), route, flight time (Flight time), owner information , And/or pilot information may be considered in combination. This allows the unmanned aerial vehicle to temporarily release or change certain mobility restrictions during the operation in order to achieve its purpose. These allowances may be allowed for a specific period through a specific timer, or temporarily applied during this registration period.

Step 8-The PCF delivers the newly created mobility-related policy to the AMF currently supporting the UAS terminal through Npcf_AMPolicyControl_UpdateNotify.

Step 9-Upon receiving the new mobility-related policy from the PCF, the AMF updates the information related to access and mobility in the existing UE context with the received information. Additionally, the PCF may create a new registration area of the terminal based on the updated mobility-related policy. In the newly created registration area, an area in which the control signal can be optimized within the operating range of the unmanned aerial vehicle is calculated using the UE's path and flight time information provided in the previous step.

Step 10-The AMF delivers the updated mobility restriction policy and registration area to the UE through a mobility related UE configuration procedure defined by 3GPP in order to update the newly transmitted mobility related policy and registration area to the UE. If necessary, the terminal can perform a new registration procedure. In this process, the AMF may deliver RAN support information (Core Network Assisted Ran Parameters) related to the behavior of the terminal. This information includes Expected UE Behavior, Expected Handover Behavior, Expected UE Mobility, Stationary or Mobile, Expected UE Trajectory, and/or Expected UE Behavior information of the terminal excluding the path may be included. Such information can be generated by AMF using UAS Authorization data.

[Third Embodiment]-UAS authentication data delivery method using Service Parameter service

In the current 3GPP, the AF 407 delivers service-related factors to the terminal when setting up an additional terminal such as a vehicle or a terminal supporting a vehicle to support V2X (Vehicle to everything) or when data provisioning to the terminal is required. The procedure to do was defined. In the present disclosure, using this procedure, a method for transmitting information related to UAS authentication and operation, and optimizing mobility limitation and mobility management information of a terminal is included. The authentication between the UAS component device and the UTM is based on UAS operation by considering the legitimate user, correct route, normal device status, flight availability, flight purpose confirmation, flight paths and/or schedules of other unmanned aerial vehicles or other vehicles. Verify flight operation.

Hereinafter, a third embodiment of the present disclosure will be exemplarily described with reference to FIG. 4.

FIG. 4 includes a method of optimizing a service restricted area and a registered area of a UAS terminal by a UTM (AF) authenticating the UAS operation and transmitting the UAS operation information acquired in this process to the 3GPP core network.

Step 1-The UAV 401 or UAV controller 401 transmits an initial registration request message to the AMF 403 in the same way as a general terminal in order to use the 3GPP mobile communication network. At this time, the behavior of the initial terminal (UE) for transmission of the registration message, connection with the base station 402, and signal transmission procedures of the base station follow the procedures defined in the 3GPP standard. Through the registration procedure, the terminal is successfully registered in 3GPP mobile communication and receives information related to the use of the terminal. In addition, it is possible to use procedures such as NAS transport for transmitting signals to the control plane and establishing a PDU session for data transmission through the user plane. During the registration process, the AMF can establish an AM Policy Association to obtain the terminal's access and mobility-related policies from the PCF (404). Additionally, when the AMF determines that the terminal is a UAS terminal through the subscriber information of the terminal, it can establish an AM Policy Association with the PCF. At this time, the PCF recognizes that there is delivery of service-related information through the UDR 405, which may occur in a later step, and makes a service-related information subscription request (Nudr_DM_Subscribe) to the UDR.

The state of the terminal immediately after registration is successfully completed is a state in which only the 3GPP registration procedure has been completed, and the authentication related to the operation of the unmanned aerial vehicle through the UTM 407 has not been completed. Accordingly, the terminal may not be able to communicate through an external data network according to a mobile communication network operation policy or a service contract between the mobile communication operator and the UTM operator.

Step 2-When the terminal is successfully registered in the 3GPP system, the terminal performs authentication of the UAV, the UAV controller, and the UAS composed of the UAV and the UAS controller through the UTM. In this process, each terminal delivers the information necessary for the above-described authentication to the UTM. Additionally, it can be seen that the core network is a device that can be configured as a UAS based on subscriber information of UAV and UAV controller, and that UTM and additional authentication procedures can occur. Through this, the core network can provision a path through which control signals or data traffic occurring later in the UTM can be transmitted to the UTM. At this time, data transfer between the terminal and the UTM is as described above: 1) authentication data is transmitted to the UTM as general data through the user plane using a PDU session, and 2) authentication through Secondary DN authentication in the process of authenticating the PDU session. Data delivery, 3) delivery through the NAS Transport method through NEF using the control plane can be used. In the present disclosure, at least one of three methods may be supported. In the process of transmitting the authentication data of the UAS terminal to the UTM through the above method, the 3GPP core network is the identifier and location information used by 3GPP such as IMEI, IMSI, and MSISDN, and the terminal communication status (access radio communication technology, radio access capability), etc. The additional information of can be delivered to the UTM together with the UAS authentication data transmitted by the terminal.

Upon receiving UAS authentication information from the UTM terminal and the 3GPP core network, the UTM may permit or reject UAS flight in consideration of the received information, internal policies, current regional conditions, and routes. In the case of rejection, the UTM can communicate the cause of the rejection failure to the terminal. For example, the UTM may recognize that the flight is not permitted on a specific route, and may include in the flight rejection message that the flight prohibition route of the terminal is included. If the reason for rejection is correctable by recognizing the reason for rejection, the terminal may transmit a new authentication message to UTM through repetition of step 2 to receive a new authentication procedure.

UAV is for UTM authentication, for example, Unique Identity, UAV UE Capability of the UAV, Make & Model, Serial Number, and Flight Weight (Take-off). weight), Position, Owner Identity, Owner Address, Owenr Contact details, Owner certification, Take-off location and time , Flight purpose (Mission type), route (Route data), and / or operating status (Operating status), etc. can be transmitted.

UAV Controller for UTM authentication, for example, Unique Identity, UAV controller UE Capability of the UAV controller, Position, Owner Identity, Owner Address, Owenr Contact details, Owner certification, the identity of the UAV operator who operate the UAV controller, and/or UAV operator license and certificate. certification).

The 3GPP core network delivers the authentication information of the UAV or UAV controller described above to the UTM, so that the unique identifier of the terminal used in 3GPP is IMSI (International Mobile Subscriber Identity), IMEI (International Mobile Equipment Identity), MSISDN (Mobile Station International). Subscriber Directory Number), and/or a Generic Public Subscription Identifier (GPSI) may additionally be transmitted to the UTM, which may be used to authenticate the UAS configuration device.

For detailed authentication-related technologies and procedures, although outside the scope of the present invention, generally used authentication technologies may be applied.

Step 3-When the authentication of the terminal constituting the UAS is successfully performed through the UTM, the UTM may inform the 3GPP core network of the authentication result through the NEF 206. At this time, the UTM may be the same as the AF, or the UTM may transmit authentication-related information through the NEF of 3GPP through an intermediate device supporting AF. For example, the UTM may transmit information related to the UAS terminal to the NEF by using the Nnef_ServiceParameter Create/Update/Delete Request provided by NEF. The Nnef_ServiceParameter operation depends on the information of the currently provisioned UE, and when the information of the UAS-related terminal is transmitted for the first time, Create, Update when changing, and Delete when deleting can be used. The transmitted authentication data may be contained in a data container named, for example, UAS Authorization Data and transmitted to NEF through UTM (AF). UAS Authorization Data (UAS Authorization Data Container) includes the external identifier of the terminal (GPSI), UTM authentication success/failure status (Authorization Status), UAV type (UAV Type), operation purpose (UAV mission), route, and flight. Information including flight time, owner information, and/or pilot information may be included, which may be transmitted to NEF. In this process, if the UTM knows the IMSI, IMEI, and MSISDN of the terminal, it may be transmitted as an identifier of the terminal instead of GPSI. In the present disclosure, it has been described that UAS authentication-related information is stored and transmitted using a UAS Authorization data container. However, if the transmitted information is the same or similar, each data may be transmitted to NEF without using a container to obtain the same effect.

Optionally, if the authentication fails, there is no need to proceed with the subsequent process.

Step 3a-optional process. NEF verifies that the data sent by UTM is normal, and verifies that the message is from UTM with legitimate use and access rights. If it is confirmed that the message is normally transmitted by UTM, NEF converts the information that needs to be converted into information used inside 3GPP among the transmitted authentication data into a form used inside the core network. For example, GPSI can be converted into SUPI and IMSI used in the core network, and route information can be converted into a list of TAI. In addition, when the state is represented by an encoding method for concise expression of information, such information may be converted. For example, if Authorization status="True", it can be converted into information in a form used by internal devices and objects such as Authorization status=1 for concise expression.

Step 4-NEF stores the UTM authentication-related information delivered in Step 3 in the UDR. When storing data in UDR, the UAS Authorization data container can be stored directly, and each component inside each container can be stored as a separate field. If there is a field corresponding to the type of subscriber information according to the manager's policy, the corresponding field of the subscriber information or the terminal context can be updated. The method of directly storing the container, storing each data, and updating a specific field of subscriber information may be selectively used, and may be used simultaneously or in combination for reliability according to a policy. When saving, the UDR can additionally store the UTM's AF ID and Transaction Reference ID information to find the UTM that delivered the message separately from the UAS Authorization data container. When the storage of the requested information is completed, the UDR can deliver a notification that the requested Service Parameter provision has been completed to NEF.

Step 5-When receiving a response for provisioning from the UDR, NEF may transmit a response to the ServiceParameter to the UTM. For example, NEF can deliver a response to a ServiceParameter to UTM using Nnef_ServiceParameter_Create/Update/Delete Response provided by NEF.

Step 6-When the UAS Authorization data stored in Step 4 is updated for the UAS terminal, the UDR notifies NFs that have subscribed to a DM (Data Management) related event that the UAS Authorization data has been newly provisioned or changed. For example, a PCF that subscribes to an event in step 1 may correspond to this NF. Accordingly, the PCF supporting the UAS terminal can know that the UAS Authorization data has been newly updated through the DM Notification data event sent by the UDR, and the UAS Authorization data is delivered to the PCF in a notification message (e.g., Nudr_DM_notify).

Step 7-The PCF that received the UAS Authorization data from the UDR is the UTM authentication success/failure status of the UAS terminal in the data (Authorization Status), UAV type (UAV Type), operation purpose (UAV mission), route, and flight. Flight time, owner information, and/or pilot information can be known. Through this, the PCF may change the mobility restriction of the UAS terminal according to an internal policy or a contract with the UTM operator in advance. Mobility restrictions defined in 3GPP largely utilize a combination of RAT Restriction, Forbidden Area, Service Area Restrictions, and Core Network Type Restriction.

RAT restriction prohibits access to the PLMN using a specific RAT defined by 3GPP. The prohibited area prohibits all attempts to communicate to a specific PLMN within the area included in the prohibited area list. Service Area Restrictions can be broadly divided into two types of areas, which can be divided into Non-allowed areas and Allowed Areas, and can be organized in the form of a list for each area. I can. A general communication service can be used within the service allowed area, and within the service unlicensed area, the terminal is not allowed to make a service request or SM signaling to the core network. Finally, the restriction on access to the core network prohibits restrictions on certain types of core networks, such as EPC or 5GC.

The PCF receiving UAS Authorization data from UTM may refer to this and create a new mobility restriction-related policy. For example, the PCF may temporarily change the list of out-of-service or out-of-service areas through a contractual relationship with UTM or recognized for its specific purpose, such as fire suppression or long-term transport. At this time, in order to consider whether the PCF is allowed or not, the UTM authentication success/failure status (Authorization Status), UAV type (UAV Type), operation purpose (UAV mission), route, flight time (Flight time), owner information , And/or pilot information may be considered in combination. This allows the unmanned aerial vehicle to temporarily release or change certain mobility restrictions during the operation in order to achieve its purpose. These allowances may be allowed for a specific period through a specific timer, or temporarily applied during this registration period.

Step 8-The PCF delivers the newly created mobility-related policy to the AMF currently supporting the UAS terminal through Npcf_AMPolicyControl_UpdateNotify.

Step 9-Upon receiving the new mobility-related policy from the PCF, the AMF updates the information related to access and mobility in the existing UE context with the received information. Additionally, the PCF may create a new registration area of the terminal based on the updated mobility-related policy. In the newly created registration area, an area in which the control signal can be optimized within the operating range of the unmanned aerial vehicle is calculated using the UE's path and flight time information provided in the previous step.

Step 10-The AMF delivers the updated mobility restriction policy and registration area to the UE through a mobility related UE configuration procedure defined by 3GPP in order to update the newly transmitted mobility related policy and registration area to the UE. If necessary, the terminal can perform a new registration procedure. In this process, the AMF may deliver RAN support information (Core Network Assisted Ran Parameters) related to the behavior of the terminal. This information includes Expected UE Behavior, Expected Handover Behavior, Expected UE Mobility, Stationary or Mobile, Expected UE Trajectory, and/or Expected UE Behavior information of the terminal excluding the path may be included. Such information can be generated by AMF using UAS Authorization data.

[Embodiment 4]-Core network support UTM authentication correction method

Since UTM uses the information collected by the UAS terminal itself during the flight authentication process, authentication is impossible in consideration of factors that affect the operation of the UAS terminal by the mobile communication network. Typically, communication service may not be possible outside the service range of the mobile communication network on the movement path of the unmanned aerial vehicle. In addition, military areas, densely populated areas, areas where service is prohibited due to management policy, or areas where communication is not permitted may be located on the route. In this case, the UTM must be able to modify the flight certification status, flight path, or flight time in consideration of the purpose and operational situation of the UAV.

In this embodiment, when the PCF receives data related to the authentication and operation of the unmanned aerial vehicle using the preceding embodiments from the UTM, a warning is issued when a place or time in which normal service is unavailable is included in the flight path of the unmanned aerial vehicle. Includes how to send to UTM.

Hereinafter, a fourth embodiment of the present disclosure will be exemplarily described with reference to FIG. 5.

5 shows a method of sending a warning to UTM when the PCF transmits UAS operation information acquired in the UTM (AF) authentication process to the 3GPP core network, and when the PCF includes a region and time in which normal service of the UAS terminal is not possible. Includes.

Step 1-The UAV 501 or UAV controller 501 transmits an initial registration request message to the AMF 503 in the same way as a general terminal in order to use the 3GPP mobile communication network. At this time, the behavior of the initial terminal (UE) for transmission of the registration message, connection with the base station, and signal transmission procedures of the base station follow the procedures defined in the 3GPP standard standard. Through the registration procedure, the terminal is successfully registered in 3GPP mobile communication and receives information related to the use of the terminal. In addition, it is possible to use procedures such as NAS transport for transmitting signals to the control plane and establishing a PDU session for data transmission through the user plane. During the registration process, the AMF can establish an AM Policy Association to obtain the terminal's access and mobility-related policies from the PCF 503. Additionally, when the AMF determines that the terminal is a UAS terminal through the subscriber information of the terminal, it can establish an AM Policy Association with the PCF. At this time, the PCF requests an event-related subscription from the UDM 504 in order to receive an event related to SDM (Subscriber Data Management) that may occur in a later step. During the registration process, the AMF can selectively apply to the UDM for SDM subscription to the terminal in order to obtain the subscriber information of the terminal to the UDM and to identify changes. If AMF recognizes the UAS terminal and the terminal that sent the registration request is aware of the UAS terminal, and has not subscribed to the SDM change, the AMF will request SDM subscription to the UDM to detect the change of subscriber information. I can.

The state of the terminal immediately after the registration is successfully completed is a state in which only the 3GPP registration procedure has been completed, and the authentication related to the operation of the unmanned aerial vehicle through the UTM 206 has not been completed. Accordingly, the terminal may not be able to communicate through an external data network according to a mobile communication network operation policy or a service contract between the mobile communication operator and the UTM operator.

Step 2-When the terminal is successfully registered in the 3GPP system, the terminal performs authentication of the UAV, the UAV controller, and the UAS composed of the UAV and the UAS controller through the UTM. In this process, each terminal delivers the information necessary for the above-described authentication to the UTM. Additionally, it can be seen that the core network is a device that can be configured as a UAS based on subscriber information of UAV and UAV controller, and that UTM and additional authentication procedures can occur. Through this, the core network can provision a path through which control signals or data traffic occurring later in the UTM can be transmitted to the UTM. At this time, data transfer between the terminal and the UTM is as described above: 1) authentication data is transmitted to the UTM as general data through the user plane using a PDU session, and 2) authentication through Secondary DN authentication in the process of authenticating the PDU session. Data delivery, 3) delivery through the NAS Transport method through NEF using the control plane can be used. In the present disclosure, at least one of three methods may be supported. In the process of transmitting the authentication data of the UAS terminal to the UTM through the above method, the 3GPP core network is the identifier and location information used by 3GPP such as IMEI, IMSI, and MSISDN, and the terminal communication status (access radio communication technology, radio access capability), etc. The additional information of can be delivered to the UTM together with the UAS authentication data transmitted by the terminal.

Upon receiving UAS authentication information from the UTM terminal and the 3GPP core network, the UTM may permit or reject UAS flight in consideration of the received information, internal policies, current regional conditions, and routes. In the case of rejection, the UTM can communicate the cause of the rejection failure to the terminal. For example, the UTM may recognize that the flight is not permitted on a specific route, and may include in the flight rejection message that the flight prohibition route of the terminal is included. If the reason for rejection is correctable by recognizing the reason for rejection, the terminal may transmit a new authentication message to UTM through repetition of step 2 to receive a new authentication procedure.

UAV is for UTM authentication, for example, Unique Identity, UAV UE Capability of the UAV, Make & Model, Serial Number, and Flight Weight (Take-off). weight), Position, Owner Identity, Owner Address, Owenr Contact details, Owner certification, Take-off location and time , Flight purpose (Mission type), route (Route data), and / or operating status (Operating status), etc. can be transmitted.

UAV Controller for UTM authentication, for example, Unique Identity, UAV controller UE Capability of the UAV controller, Position, Owner Identity, Owner Address, Owenr Contact details, Owner certification, the identity of the UAV operator who operate the UAV controller, and/or UAV operator license and certificate. certification).

The 3GPP core network delivers the authentication information of the UAV or UAV controller described above to the UTM, so that the unique identifier of the terminal used in 3GPP is IMSI (International Mobile Subscriber Identity), IMEI (International Mobile Equipment Identity), MSISDN (Mobile Station International). Subscriber Directory Number), and/or a Generic Public Subscription Identifier (GPSI) may additionally be transmitted to the UTM, which may be used to authenticate the UAS configuration device.

For detailed authentication-related technologies and procedures, although outside the scope of the present invention, generally used authentication technologies may be applied.

Step 3-When the authentication of the terminal constituting the UAS is successfully performed through the UTM, the UTM may inform the 3GPP core network of the authentication result through the NEF 505. At this time, the UTM may be the same as the AF, or the UTM may transmit authentication-related information through the NEF of 3GPP through an intermediate device supporting AF. For example, the UTM may transmit information related to the UAS terminal to the NEF by using the Nnef_ParameterProvision_Update Request provided by NEF. The transmitted authentication data may be contained in a data container named, for example, UAS Authorization Data and transmitted to NEF through UTM (AF). UAS Authorization Data (UAS Authorization Data Container) includes the external identifier of the terminal (GPSI), UTM authentication success/failure status (Authorization Status), UAV type (UAV Type), operation purpose (UAV mission), route, and flight. Information including flight time, owner information, and/or pilot information may be included, which may be transmitted to NEF. In this process, if the UTM knows the IMSI, IMEI, and MSISDN of the terminal, it may be transmitted as an identifier of the terminal instead of GPSI. In this disclosure, the UAS Authorization data container is used to store and transmit UAS authentication-related information. However, if the transmitted information (data) is the same or similar, each data is transmitted to NEF without using a container to obtain the same effect. May be.

In the process of delivering UAS Authorization data, UTM can subscribe to events to receive events related to the verification result by PCF of UAS Authorization data at the same time. In the process of explicitly receiving a PCF-related event through step 3a below or delivering a Nnef_ParameterProvision_Update message, a subscription request can be made using one field. In FIG. 5, a new parameter called event_subscription is added to the Nnef_ParameterProvision_Update request message, and the request is sent to NEF. After that, when an event related to UAS Authorization data occurs, NEF delivers the related event to UTM.

Optionally, if the authentication fails, there is no need to proceed with the subsequent process.

This embodiment schematically illustrates a method of transmitting UAS Authorization data using Nnef_ParameterProvision_Update used in Embodiments 1 and 2, but the same can be applied to Nnef_ServiceParameter Create/Update/Delete used in Embodiment 3.

Step 3a-optional process. This process transfers UAS authentication and operation related information to PCF or AMF, and requests subscription to receive related events that may occur in the mobile communication network based on the information received by each NF. UTM sends a UAS-related event information subscription request message to NEF using Nnef_EventExposure_subscribe Request. At this time, the NEF and the PCF generating the actual event use "UAV Authorization" as the Event ID for processing the event, and designate the target UAS terminal. In this process, additional event reporting and filter-related factors can be transmitted together. The "UAV Authorization" event is an event that sends an event related to the PCF or AMF about the authentication and operation information of the UAS terminal transmitted by the UTM. In the event that the same service is expected to be disconnected at a specific time in a specific area, such as an area where service is not available, an area where communication is not permitted, etc., it is an event that the UAS terminal communicates to the UTM that communication service is not possible in a specific route. .

Upon receiving the event subscription request, the NEF can find the PCF supporting the terminal and subscribe to the related event.

Step 4-Optional process. NEF verifies that the data sent by UTM is normal, and verifies that the message is from UTM with legitimate use and access rights. If it is confirmed that the message is normally transmitted by UTM, NEF converts the information that needs to be converted into information used inside 3GPP among the transmitted authentication data into a form used inside the core network. For example, GPSI can be converted into SUPI and IMSI used in the core network, and route information can be converted into a list of TAI. In addition, when the state is represented by an encoding method for concise representation of the information, such information may be converted. For example, if Authorization status="True", it can be converted into information in a form used by internal devices and objects such as Authorization status=1 for concise expression.

Step 5-NEF stores the UTM authentication-related information delivered in Step 3 in the UDM. UDM can internally store authentication data in UDR using services provided by UDR such as Nudr_DM_Query and Nudr_DM_Update. When storing data in UDM, the UAS Authorization data container can be directly saved, and each component inside each container can be saved as a separate field. If there is a field corresponding to the type of subscriber information according to the manager's policy, the corresponding field of the subscriber information or the terminal context can be updated. The method of directly storing the container, storing each data, and updating a specific field of subscriber information may be selectively used, and may be used simultaneously or in combination for reliability according to a policy. When saving, the UDM can additionally store the UTM's AF ID and Transaction Reference ID information to find the UTM that delivered the message separately from the UAS Authorization data container. When the storage of the requested information is completed, the UDM can deliver a notification that the requested parameter provision has been completed to the NEF.

In this step, the UDM is used to store and notify UAS Authorization data, but the same can be applied to the case of using UDR as in the third embodiment (third embodiment).

Step 6-When receiving a response for provisioning from UDM or UDR, NEF may transmit a response to ParameterProvision or ServiceParmeter to UTM. For example, NEF may use the Nnef_ParameterProvision_Update Response provided by NEF to deliver the response to the UTM.

Step 7-The UAS Authorization data stored in Step 4 is transferred to the PCF by the UDM or UDR. For example, the UDM or UDR may transmit this data to the PCF using Nudm_SDM_notification notify.

Step 8-The PCF receiving the UAS Authorization data from the data is the UTM authentication success/failure status of the UAS terminal (Authorization Status), UAV type (UAV Type), operation purpose (UAV mission), route, and flight time ( Flight time), owner information, and/or pilot information. Through this, the PCF may change the mobility restriction of the UAS terminal through an internal policy or a contract with the UTM operator in advance. Mobility restrictions defined in 3GPP largely utilize a combination of RAT Restriction, Forbidden Area, Service Area Restrictions, and Core Network Type Restriction. In this case, it is impossible to change the mobility restriction according to laws or regulations, but the route of the unmanned aerial vehicle may include an area where service is not available. When an unmanned aerial vehicle enters such an area, an event related to that communication service may not be possible is transmitted to NEF. The event information may include information related to an area and reason for which the communication service is not supported. In addition, when communication service in a specific area is not possible at a specific time period, information related to the inability to support communication service may be expressed by a combination of the area and time.

Step 9-The PCF forwards the event related to the created communication unavailable area to NEF. For example, the PCF may transmit an event related to a communication unavailable area generated using Nnef_EventExposure notify to NEF.

Step 10-Optional process. The UTM, which received information about the area and time related to the area where communication is unavailable from NEF, can cancel the certification of the operation of the UAV terminal in consideration of the characteristics of the terminal and the purpose of operation, or change the route to a service connection through route correction. . In addition, if it is an unmanned aerial vehicle that does not require continuous connectivity, it can operate without changing the existing route as it is. If there is a change in information related to authentication and operation, it is possible to confirm whether or not the route is configured to support service of the mobile communication network by repeating the process of step 1 and transmitting the changed data to the 3GPP core network. It is possible to minimize control signals that may occur between the network and the UAV through the optimization of mobility restrictions and registration areas by utilizing the examples through the third embodiments.

6 shows the structure of a network entity according to an embodiment of the present invention. The network entity of FIG. 6 may be, for example, any one of the entities of FIG. 1. For example, the entity is a UAV, a UAV controller, a terminal device (ME) that shares a UAV or service, a UAS consisting of a UAV and a UAV controller, a base station supporting wireless communication, AMF, SMF, PCF, NWDAF, NEF, UDM Alternatively, it may be one of UDR, UPF, unmanned aerial vehicle traffic control system (UTM), or OAM.

Referring to FIG. 6, the network entity may include a transmission/reception unit 610, a control unit 620, and a storage unit 630. In the present invention, the control unit may be defined as a circuit or an application-specific integrated circuit or at least one processor.

The transceiver 610 may transmit and receive signals with other network entities. The transceiver 610 may receive system information from, for example, a base station, and may receive a synchronization signal or a reference signal.

The controller 620 may control the overall operation of the network entity according to the embodiment proposed in the present invention. For example, the controller 620 may control a signal flow between blocks to perform an operation according to the above-described procedure with reference to FIGS. 2 to 5. For example, the controller 620 may control an operation proposed by the present invention to generate a mobility restriction-related policy based on authentication information in a mobile communication system according to an embodiment of the present invention.

The storage unit 630 may store at least one of information transmitted and received through the transmission/reception unit 610 and information generated through the control unit 620. For example, the storage unit 630 may store authentication information required to generate a mobility restriction-related policy according to the above-described embodiment.

7 shows a method of a first entity performing a policy control function (PCF) in a mobile communication system according to an embodiment of the present invention. In FIG. 7, descriptions overlapping with those described above in the embodiments of FIGS. 2 to 4 will be omitted.

Referring to FIG. 7, a first entity performing a policy control function (PCF) may receive authentication information for an unmanned aerial vehicle from a second entity performing a data storage or management function (S710). As an embodiment, the authentication information may be provided by a fourth entity (eg, UTM) that performs unmanned aerial vehicle traffic management.

The first entity may generate a policy related to mobility restriction for the unmanned aerial vehicle based on the authentication information (S720).

The first entity is a third entity that performs an access and mobility management function (AMF) and may transmit the mobility restriction-related policy (S720).

As an embodiment, the mobility restriction-related policy may be used by the third entity to generate new registration area information for the unmanned aerial vehicle.

As an embodiment, the authentication information may include information on the purpose of operation of the unmanned aerial vehicle and information on the owner of the unmanned aerial vehicle.

As an embodiment, the authentication information includes at least one of the type information of the unmanned aerial vehicle, the authentication state information of the unmanned aerial vehicle, the route information of the unmanned aerial vehicle, the flight time information of the unmanned aerial vehicle, or the pilot information of the unmanned aerial vehicle. It may contain more.

As an embodiment, the second entity may be an entity performing an integrated data management (UDM) function or an entity performing an integrated data storage (UDR) function.

As an embodiment, the authentication information may be provided by the fourth entity using an authentication information container in a parameter provisioning update message.

As an embodiment, the authentication information may be provided by the fourth entity using an expected UE behavior parameter in a parameter provisioning update message.

As an embodiment, the authentication information may be provided by the fourth entity using an authentication information container in a service parameter message.

[Fifth Embodiment]-Provision of information on areas where communication cannot be provided using PCF

Mobile communication systems, such as UAVs and UAV controllers using 5G mobile communication systems, undergo a registration process in the same way as a terminal using a general 3GPP mobile communication network, and receive authentication and authorization related to the use of the mobile communication network. . In this process, the core network supports the terminals constituting the UAS to communicate with the UTM. After that, the UTM performs the authentication of the UAS terminal, and at the same time, the UAS pilot, owner, flight path, and/or flight objectives may be comprehensively considered to give the terminal aviation permission. In the present disclosure, it is assumed that the terminal is authenticated to the 3GPP network or that information exchange for authentication is performed between the performing UAS and the UTM during the authentication procedure.

UAV is for UTM authentication, for example, Unique Identity, UAV UE Capability of the UAV, Make & model, Serial Number, and Take-off weight. ), Position, Owner Identity, Owner Address, Owner Contact details, Owner certification, Take-off location and time, Flight purpose (Mission type), route (Route data), and / or operating status (Operating status), etc. can be transmitted to the UTM as authentication information (data). In this case, the UAV may deliver the authentication information to the UTM through the 3GPP core network.

UAV Controller is for UTM authentication, for example, Unique Identity, UAV controller UE Capability of the UAV controller, Position, Owner Identity, Owner Address, Owner Owenr Contact details, Owner certification, the identity of the UAV operator who operate the UAV controller, and/or UAV operator license and certification. ), etc. can be transmitted to the UTM as authentication information (data). In this case, the UAV Controller may deliver the authentication information to the UTM through the 3GPP core network.

When the 3GPP core network delivers the authentication information of the UAV or UAV controller to the UTM, for example, IMSI (International Mobile Subscriber Identity), IMEI (International Mobile Equipment Identity), MSISDN (Mobile Station International Subscriber Directory Number) and GPSI (Generic Public Subscription Identifier) can be additionally delivered to UTM, which can be used to authenticate UAS components.

UTM performs authentication related to aviation authorization based on the information transmitted by UAS and directly collected information. However, since the information held by UAS and UTM does not include information on the status (or status) and quality of the mobile communication network, communication-related problems that may occur during the operation of the unmanned aerial vehicle cannot be considered. In order to solve this problem, the present disclosure includes a method of calculating a route of an unmanned aerial vehicle by transmitting information related to network conditions and quality to UTM in a core network. At this time, the transmitted network status and quality information may vary according to the flight purpose and flight altitude according to the operation status of the unmanned aerial vehicle. Such information may be included as filter information in a message that UTM requests information from the core network and transmitted, and the core network provides information on the network status according to the requested region and time in consideration of this additional information (or Function).

In this disclosure, the information transmitted by UAS for UTM authentication and aviation authorization, network information transmitted by the 3GPP mobile communication network, and UTM's self-collected or set policies are used to permit the operation of the terminal or change the operation route and time. Includes a way to do it.

Hereinafter, a fifth embodiment of the present disclosure will be exemplarily described with reference to FIG. 8.

FIG. 8 (FIGS. 8A and 8B) shows a procedure for transmitting information on an operable area or an inoperable area of an unmanned aerial vehicle using a PCF. FIG. 8 includes a method of permitting a final operation permit and route of a UAS terminal by using network-related information received from a core network in the process of UTM (AF) authenticating the operation of UAS. In this case, a method of modifying the route or flight time according to the UTM's internal policy may be used.

Step 0-The PCF 803 may subscribe or request information on the current mobile communication network from the OAM 802. The information received from OAM includes, for example, the location and service provision area of each base station, the provision area of the entire telecommunication network, whether each base station is currently operating and operating, and the base station operation and network service area, including measurement values for each base station. It may include at least one of information about. In addition, in relation to the core network, the operation status and load of each NF, the number of terminals registered by region, and service status may be transmitted to the PCF. In addition, the PCF may receive information in advance about a policy or region that induces mobility restrictions through OAM or an internal method. The PCF may generate information related to mobility restriction of terminals in consideration of information received from OAM and an internal policy.

Mobility restrictions defined in 3GPP largely utilize a combination of Radio Access Technology (RAT) restrictions (RAT Restriction), Forbidden Area, Service Area Restrictions, and Core Network Type Restriction. do. RAT restriction prohibits access to the PLMN using a specific RAT defined by 3GPP. The prohibited area prohibits all attempts to communicate to a specific PLMN within the area included in the prohibited area list. Service Area Restrictions can be broadly divided into two types of areas, which can be divided into Non-allowed areas and Allowed Areas, and are organized in the form of a list for each area. Can be. A general communication service can be used within the service allowed area, and within the service unlicensed area, the terminal is not allowed to make a service request or SM signaling to the core network. Finally, the restriction on access to the core network can prohibit restrictions on certain types of core networks, such as EPC or 5GC.

Step 1-The UTM 805 may apply for an event subscription related to the current network service area to the core network through the NEF 804. UTM is a device located outside the mobile communication network and can internally perform a role as an AF defined in 3GPP, or send a request to NEF through another device that plays the role of AF.

A message (eg, Nnef_EventExposure_Subscription request) for which UTM sends an event subscription request to NEF may include an event ID to be subscribed to, a filter, and/or values related to event reporting. In the present disclosure, an event subscription is requested for information related to situation information of a network by region, and the event identifier requests subscription to an allowed operational area as an event identifier. Filter types used when limiting or more detailed information on network status information on permitted operating areas is desired include: Device Type, UE Capability, Operation Purpose (Mission), Time, Owner information, operator information, departure point (Departure), destination (Destination), waypoints (Waypoints), altitude (Altitude), and / or area (Area), and the like may be included. In this case, the UTM may limit the area where information is desired to be received according to the filter interest area and the type and purpose of the UAV. If the filter is not included, the network status for the entire area providing network service can be provided according to the internal policy of the mobile communication network.

All of the factors used in the filter are optional, and a filter can be configured with a combination of each factor. The device type may include information related to the device configuration of the UAV, such as the UAV type, UAV model, and UAV manufacturer. In the UE capability, it is possible to express the wireless access technologies supported by the unmanned aerial vehicle and the functions that can be supported by the core network. The flight purpose (mission) expresses the purpose of operation of the unmanned aerial vehicle, and may be expressed as a general string, or the purpose may be expressed in a pre-arranged category or code. Owner information and pilot information can be used for the purpose of confirming related contracts between the telecommunication operator and the UAV owner or pilot in relation to the operation of a specific UAV. The origin, destination, and stopover information are used for the purpose of limiting the region including the origin, destination, and stopover, and if this information is not provided, the core network can provide the network status for the entire service area. The altitude information indicates the main altitude at which each terminal will fly, and is transmitted to take into account network conditions that vary depending on altitude. Coordinate values for a specific area may be transmitted as area information. There may be various ways of expressing this coordinate, but the area can be expressed in various ways, such as a center value, a diameter, and a rectangular coordinate expressed by two points. Alternatively, the name of the area on the actual jurisdiction may be transmitted as area information.

Depending on the embodiment, for example, when the UTM is classified as a reliable AF, the UTM may apply for a subscription to an event related to the current network service area directly through the PCF without going through NEF.

Step 2-NEF can change some or all of the information received from UTM from the form of information used outside to the form of information used inside the network. For example, NEF can convert methods of expressing longitude and latitude used in GPS, or other local information, into TAI (Tracking Area ID) or Cell ID used inside the network. The functions of the UE can also be converted into the UE's radio capability and core network capability, and if the related functions are expressed in a specific code, each such function can be converted into a code and transmitted. have.

Step 3-NEF requests a subscription request of the converted UTM to the PCF. To this end, NEF may transmit a message (eg, Npcf_EventExposure_Subscription request) for a converted event subscription request to the PCF. The type of the factor transmitted through the message may be the same as the message transmitted by the UTM, and in the case of the converted factor, the value may be different from the value of the factor included in the message transmitted by the UTM.

Step 4-In order to process the event subscription request, the PCF is based on the information received from OAM, internal policy, and/or the content of the requested filter, in the area where the unmanned aerial vehicle that satisfies the condition can receive communication service ( For example, it is calculated for the type of equipment and per service area (per service area). As a result of the calculation, it is possible to express the area as an operable area or an area that cannot be operated. If the area is expressed as an area that cannot be operated, information on the reason for the inability to be operated can be expressed for each detailed area. For example, the causes of prohibited areas, densely populated areas, out of range of service, and disability may be expressed. When the use is not possible due to a failure or temporary network configuration change, a detailed region and time zone in which the communication service is not provided may be included in a message for a response or notification of the PCF to be described later in step 5. For example, the detailed area and time zone may be included in the list of available or non-operable areas in the message. For example, in the case of a list of operational areas, detailed regions and operational time zones for operational areas may be included. Alternatively, in the case of a list of non-operational areas, detailed regions and non-operational time zones for the non-operational areas may be included. Information on an operable area or an inoperable area may be expressed as a set of detailed areas. In addition, the detailed area can be expressed as TAI, Cell ID, etc. used inside the mobile communication network. In addition, there may be various expression methods for information related to the region, but the expression form of the information representing the region may be included in a message for a response or notification of the PCF, which will be described later in step 5. When expressed as an operable area, the recommended maximum number of unmanned aerial vehicles may be included in a message for a response or notification of the PCF, which will be described later in step 5.

Step 5-The PCF communicates to NEF a list of operational or non-operable areas. To this end, the PCF may transmit a response or notification message (response or notification message (eg, Npcf_EventExposure_notify) to the NEF) to the message (second request message) of step 3. In this case, the message (second notification message) may be delivered to the NEF. The message) may include a list of available or non-operable areas (list of service areas) In addition, the second notification message may further include information indicating the number of devices recommended in the corresponding service area.

Step 6-NEF converts the information on the operable or non-operable area received to the PCF into information that can be known from the outside. On the other hand, when provided without conversion, the UTM may be considered a case where the mapping information for the TAI or Cell ID is provided from the mobile communication network operator and can be interpreted.

Step 7-NEF delivers the converted operational or non-operable area information to the UTM. To this end, the NEF may transmit a response or notification message (response or notification message (eg, Npcf_EventExposure_notify) to the UTM) to the message (first request message) of step 1. In this case, the message (first response) The message) may include a list of available or non-operable areas (list of service areas) In addition, the first response message may further include information indicating the number of devices recommended in the corresponding service area.

Step 8-The UAV or UAV controller 801 transmits information related to authentication and operation of the unmanned aerial vehicle to the UTM.

Step 9-UTM decides whether to authenticate UAS and permit aviation based on information transmitted by UAS, network status information received from the above-described core network, information collected by itself, and/or policy. In this process, UTM can determine whether the UAS is flying, operating time, and route through the process of modifying the route of UAS in its own way. Alternatively, the UTM may determine the UAS request path as the UAS path.

Step 10-UTM passes authentication and flight authorization information to UAS. UAS performs normal operation according to the authentication result.

Step 11-When the situation of the network is changed (changed), the OAM and/or PCF may recognize the change in the network configuration. There may be various cases in which the network situation changes. For example, changes in the service provision area through temporary base station installation, changes in the provision area due to power off of the base station to save power, changes in the network protection area due to the movement of the terminal, and the occurrence of failures, etc., can act as causes of change in the network situation. I can.

Step 12-The PCF detects changes in the network situation and calculates information related to the available or non-operable area of the new unmanned aerial vehicle (eg, information on the new device type and service area for each operation purpose). The format of information presentation may be the same as in step 4.

Step 13-The PCF communicates the newly calculated operational or non-operable area information to NEF. To this end, the PCF may transmit the information to the NEF by using the message of step 5. The message may further include information indicating the number of devices recommended in the new service area.

Step 14-NEF converts the information on the operable or non-operable area transmitted to the PCF into information that can be known from the outside. On the other hand, when provided without conversion, the UTM may be considered a case where the mapping information for the TAI or Cell ID is provided from the mobile communication network operator and can be interpreted.

Step 15-NEF communicates the converted operational or non-operable area information to the UTM. To this end, the PCF may transmit the information to the NEF using the message of step 7. The message may further include information indicating the number of devices recommended in the new service area.

Step 16-UTM decides whether it is necessary to change UTS authentication, flight authorization, route, and flight time based on information previously transmitted by UAS, network status information newly transmitted, information collected by itself, and/or policy. do.

Step 17-In the event of a need to cancel authorization or to change flight-related information, UTM notifies UAS of the information regarding the change.

On the other hand, as a process that occurs additionally according to the change of the network situation in the process after Step 11, it may be selectively performed according to the policy, or may not be performed when the event report related information is already satisfied in Step 1.

[Sixth Embodiment]-Providing area information capable of satisfying communication quality requirements using NWDAF

In consideration of the characteristics of the unmanned aerial vehicle, the correction of the route has characteristics different from that of the ground terminal. While flying, it may be impossible to modify the route to reach the destination due to battery and route constraints. Therefore, in order to solve this situation, when initially setting the route of the unmanned aerial vehicle, it is necessary to select a route that satisfies the communication quality requirements required by the unmanned aerial vehicle and establish the route. In order to support this route setting, the network provides information on the area that satisfies the quality requirements for each terminal, and the UTM or UAS can refer to this information to set the route to move to areas of the level required for service use or provision. have.

3GPP has defined the Network Data Analytics Function (NWDAF), a function that provides analysis of network-related information through collection of network information. In the existing NWDAF, as part of a method for supporting communication service for vehicles, when the network service quality level of the terminal is expected to drop below a certain level, the function of delivering an event to the server or network function providing the service has been defined. However, in the case of such an event, in the case of unmanned aerial vehicles, if the network quality service is expected to be degraded or disconnected, it may not be possible to modify the route. I can bring it up. Therefore, in order to solve this situation, the terminal must be able to utilize information on an area that can satisfy the required communication quality requirements when initially setting a path.

This disclosure includes a method of providing information on an expected network quality level for a specific region and time by extending the functions provided by the NWDAF. UTM or UAS can use this information to set the route of the unmanned aerial vehicle by using information on the area before the unmanned aerial vehicle operates, network quality information by time, and information about the area where communication is impossible.

Hereinafter, a sixth embodiment of the present disclosure will be exemplarily described with reference to FIG. 9.

9 (FIG. 9A and FIG. 9B) shows a procedure for delivering information on an operable area or an impossible area that satisfies the requested communication quality requirement using the NWDAF.

Step 0-The NWDAF 903 may subscribe or request information on the current mobile communication network from the OAM 902. Information received from OAM includes, for example, the location and service provision area of each base station, the provision area of the entire telecommunication network, whether each base station is currently operating and operating, and the base station operation and network service area, including measurement values for each base station. It may include at least one of information on. In addition, in relation to the core network, the operation status and load of each NF, the number of registered terminals by region, and service status may be transmitted to the NWDAF. The NWDAF can collect information received from OAM and collected from AMF, SMF, PCF, etc. The information collected by the NWDAF may include, for example, information such as the location of specific terminals, mobility restrictions, the PDU session status of the terminal, the communication status of the terminal, the user plane usage status of the terminal, and/or the service usage rate of the terminals. In addition, NWDAF can collect information such as service quality and service experience from externally located servers such as AF. For example, the NWDAF may collect the above-described information for UAS terminals that have previously operated (providing a record of the UAS operation past) and nearby ground networks.

The NWDAF, which has collected information from OAM, NF, and AF, collects records of such collected information and internally analyzes and predicts information related to network failure, congestion, and communication quality that may occur in specific regions and under certain circumstances. It can be analyzed through methods such as algorithms or machine learning.

Step 1-The UTM 905 may apply to the core network to subscribe to network analysis information related to the current network service area through the NEF 904. UTM is a device located outside the mobile communication network and can internally perform a role as an AF defined in 3GPP, or send a request to NEF through another device that plays the role of AF.

A message (e.g., Nnef_AnalyticsExposure_Subscription) for which UTM sends an analysis information subscription request to NEF may include an analysis information identifier (Analytics ID) to be subscribed to, a filter, and/or values related to reporting analysis information. In the present disclosure, an event subscription is requested for information related to situation information of a regional network, and the analysis information identifier requests a subscription to an Allowed Operational Area with QoS Requirements as an analysis information identifier. Filter types used when limiting or more detailed information on network status information on permitted operating areas is desired include: Device Type, UE Capability, Operation Purpose (Mission), Time, Owner information, operator information, departure point (Departure), destination (Destination), waypoints (Waypoints), altitude (Altitude), and / or area (Area), and the like may be included. In this case, the UTM may additionally transmit information related to the quality of service requirements according to the purpose of operation of the unmanned aerial vehicle or the unmanned aerial vehicle (QoS requirements). Typical factors for quality of service requirements include bandwidth, delay, error rate, packet loss, peak transmission rate, and/or packet delay budget. Budget). In addition, the UTM may limit the area in which information is desired to be received according to the filter region of interest and the type and purpose of the UAV. If the filter is not included, the network status for the entire area providing network service can be provided according to the internal policy of the mobile communication network.

All of the factors used in the filter are optional, and a filter can be configured with a combination of each factor. The device type may include information related to the device configuration of the UAV, such as the UAV type, UAV model, and UAV manufacturer. In the UE capability, it is possible to express the wireless access technologies supported by the unmanned aerial vehicle and the functions that can be supported by the core network. The purpose of operation expresses the purpose of operation of the unmanned aerial vehicle, and may be expressed as a general string, or the purpose may be expressed in a pre-arranged category or code. Owner information and pilot information may be used for the purpose of confirming related contracts between the telecommunication operator and the UAV owner or pilot in relation to the operation of a specific UAV. The origin, destination, and stopover information are used for the purpose of limiting the region including the origin, destination, and stopover, and if this information is not provided, the core network can provide the network status for the entire service area. The altitude information indicates the main altitude at which each terminal will fly, and is transmitted to take into account network conditions that vary according to altitude. Coordinate values for a specific area may be transmitted as area information. There may be various ways of expressing this coordinate, but the area can be expressed in various ways, such as a center value, a diameter, and a rectangular coordinate expressed by two points. Alternatively, the name of the area on the actual jurisdiction may be transmitted as area information.

Depending on the embodiment, for example, when UTM is classified as a reliable AF. UTM can subscribe to events related to the current network service area through NWDAF directly without going through NEF.

Step 2-NEF can change some or all of the information received from UTM from the form of information used outside to the form of information used inside the network. For example, NEF can convert methods of expressing longitude and latitude used in GPS, or other local information, into TAI (Tracking Area ID) or Cell ID used inside the network. The functions of the UE can also be converted into the UE's radio capability and core network capability, and if the related functions are expressed in a specific code, each such function can be converted into a code and transmitted. have.

Step 3-NEF transmits a request for analysis of the converted UTM subscription request to the NWDAF. To this end, the NEF may transmit a message for the converted subscription request (eg, Nnwdaf_AnalyticsSubscription request) to the NWDAF. The type of the factor transmitted through the message may be the same as the message transmitted by the UTM, and in the case of the converted factor, the value may be a value converted from the value of the factor included in the message transmitted by the UTM.

Step 4-NWDAF satisfies the requested network quality condition based on information received from OAM, internal policies, filters requested, and/or information collected past and present from AF/NF in order to process analysis information subscription requests. An area in which an unmanned aerial vehicle can receive communication services (eg, a service area per device type and operation purpose that satisfies the requested communication service requirements) is calculated. As a result of the calculation, the service area can be expressed as an operable area or an area that cannot be operated. At this time, if information related to mobility limitation is collected from the PCF, the unavailable area may be determined in consideration of whether or not mobility is restricted. If the area is expressed as an area that cannot be operated, information on the reason for the inability to be operated can be expressed for each detailed area. For example, forbidden areas, densely populated areas, out of range of service, causes of disability, etc., and inability to satisfy quality requirements may be expressed. When a service cannot be provided or quality is not satisfied due to a failure or a temporary change in network configuration, a detailed region and time zone in which communication is not provided may be included in a message for a response or notification of the PCF to be described later in step 5. For example, the detailed area and time zone may be included in the list of available or non-operable areas in the message. For example, in the case of a list of operational areas, detailed regions and operational time zones for operational areas may be included. Alternatively, in the case of a list of non-operational areas, detailed regions and non-operational time zones for the non-operational areas may be included. Information on an operable area or an inoperable area may be expressed as a set of detailed areas. In addition, the detailed area can be expressed as TAI, Cell ID, etc. used inside the mobile communication network. In addition, there may be various expression methods for information related to the region, but the expression form of the information representing the region may be included in a message for a response or notification of the PCF, which will be described later in step 5. When expressed as an operable area, the recommended maximum number of unmanned aerial vehicles may be included in a message for a response or notification from the PCF, which will be described later in step 5.

Step 5-The NWDAF delivers to NEF a list of operational or non-operable areas that meet the requested communication service requirements. To this end, the NWDAF may transmit a message (response or notification message (eg, Nnwdaf_AnalyticsSubscription notify) to NEF) for a response or notification to the message (second request message) of step 3. In this case, the message (second request message) may be delivered to the NEF. The notification message) may include a list of available or non-operable areas satisfying the requested communication service requirements (service area list) In addition, the second notification message includes the number of devices recommended in the service area. It may further include information indicating.

Step 6-NEF converts the information on the operable or non-operable area that satisfies the network quality requirements delivered to the NWDAF into information that can be known from the outside. On the other hand, when provided without conversion, the UTM may be considered a case where the mapping information for the TAI or Cell ID is provided from the mobile communication network operator and can be interpreted.

Step 7-NEF delivers the information on the operational or non-operable area that satisfies the converted quality requirements to the UTM. To this end, the NWDAF may transmit a message (response or notification message (eg, Nnwdaf_AnalyticsExposure notify) to NEF) for response or notification to the message (first request message) of step 1. In this case, the message (first request message) may be delivered to the NEF. Response message) may include a list of operable or non-operable areas (service area list) that satisfy the converted quality requirement In addition, the first response message indicates the number of devices recommended in the corresponding service area. Indicative information may be further included.

Step 8-The UAV or UAV controller 901 transmits information related to authentication and operation of the unmanned aerial vehicle to the UTM.

Step 9-UTM decides whether to authenticate UAS and permit aviation based on information transmitted by UAS, network status information received from the above-described core network, information collected by itself, and/or policy. In this process, UTM can determine whether the UAS is flying, operating time, and route through the process of modifying the route of UAS in its own way. Alternatively, the UTM may determine the UAS request path as the UAS path.

Step 10-UTM passes authentication and flight authorization information to UAS. UAS performs normal operation according to the authentication result.

Step 11-When the situation of the network changes (changes), the NWDAF can recognize the change in the network configuration. Recognition of this change can be analyzed by itself through continuous information collection from the OAM/AF/NF devices. There can be many cases in which the network situation changes. For example, changes in the service provision area through temporary base station installation, changes in the provision area due to power off of the base station to save power, changes in the network protection area due to the movement of the terminal, and the occurrence of failures, etc., can act as causes of change in the network situation. I can.

Step 12-The NWDAF detects changes in the network situation and calculates information related to the available or non-operable area of the new UAV (eg, information on the new device type and service area for each operation purpose). The format of information presentation may be the same as in step 4.

Step 13-The NWDAF communicates the newly calculated operational or non-operable area information to NEF. To this end, the NWDAF may transmit the information to the NEF by using the message of step 5. The message may further include information indicating the number of devices recommended in the new service area.

Step 14-NEF converts the information on the operable or non-operable area transmitted to the NWDAF into information that can be known from the outside. On the other hand, when provided without conversion, the UTM may be considered a case where the mapping information for the TAI or Cell ID is provided from the mobile communication network operator and can be interpreted.

Step 15-NEF communicates the converted operational or non-operable area information to the UTM. To this end, the NEF may transmit the information to the UTM using the message of step 7. The message may further include information indicating the number of devices recommended in the new service area.

Step 16-UTM decides whether it is necessary to change UTS authentication, flight authorization, route, and flight time based on information previously transmitted by UAS, network status information newly transmitted, information collected by itself, and/or policy. do.

Step 17-In the event of a need to cancel authorization or to change flight-related information, UTM notifies UAS of the information regarding the change.

On the other hand, as a process that occurs additionally according to the change of the network situation in the process after Step 11, it may be selectively performed according to the policy, or may not be performed when the event report related information is already satisfied in Step 1.

[Embodiment 7]-Provision of area information capable of satisfying communication quality requirements using PCF

The exposure and calculation of information related to the mobility limitation of the terminal is the PCF's unique decision capability, and can be determined by comprehensively considering the base station status, core network status, and internal policy. In this case, the analysis information of network failure status and communication quality level by region and time provided by NWDAF also acts as a factor in determining the mobility limitation of the terminal, and finally, decisions related to the mobility limitation of the unmanned aerial vehicle or terminal can be made. . In the present disclosure, in order for the PCF to make a decision related to the mobility limitation of a terminal more efficiently, it is possible to calculate an operable area or an unoperable area of an unmanned aerial vehicle in consideration of network quality and situation information for each area and time provided by NWDAF. In this disclosure, when the PCF receives a request for information on an operational area (or non-operational area) for an unmanned aerial vehicle from an external UTM or UAS, it determines the mobility limitation of the terminal in consideration of the network analysis information provided by the NWDAF. Including the method.

Hereinafter, a seventh embodiment of the present disclosure will be exemplarily described with reference to FIG. 10.

10 (FIGS. 10A and 10B) shows a procedure for transmitting information on an operable area or an impossible area that satisfies the requested communication quality requirements using the PCF and the NWDAF.

Step 0-The PCF 1004 and the NWDAF 1003 may subscribe or request information on the current mobile communication network from the OAM 1002. The information received from OAM includes, for example, the location and service provision area of each base station, the provision area of the entire telecommunication network, whether each base station is currently operating and operating, and the base station operation and network service area, including measurement values for each base station. It may include at least one of information about. In addition, the operation status and load of each NF in relation to the core network, the number of registered terminals and service status by region, etc. may be transmitted to the PCF and NWDADF. In addition, the PCF may receive information in advance about a policy or region that induces mobility restrictions through OAM or an internal method. The PCF may generate information related to mobility restriction of terminals in consideration of information received from OAM and an internal policy.

As described above, mobility restrictions defined in 3GPP largely utilize a combination of RAT Restriction, Forbidden Area, Service Area Restrictions, and Core Network Type Restriction. . RAT restriction prohibits access to the PLMN using a specific RAT defined by 3GPP. The prohibited area prohibits all attempts to communicate to a specific PLMN within the area included in the prohibited area list. Service Area Restrictions can be broadly divided into two types of areas, which can be divided into Non-allowed areas and Allowed Areas, and can be organized in the form of a list for each area. I can. A general communication service can be used within the service allowed area, and within the service unlicensed area, the terminal is not allowed to make a service request or SM signaling to the core network. Finally, the restriction on access to the core network can prohibit restrictions on certain types of core networks, such as EPC or 5GC.

As described above, the NWDAF may collect information collected from AMF, SMF, PCF, etc., information received from OAM. The information collected by the NWDAF may include, for example, information such as the location of specific terminals, mobility restrictions, the PDU session status of the terminal, the communication status of the terminal, the user plane usage status of the terminal, and/or the service usage rate of the terminals. In addition, NWDAF can collect information such as service quality and service experience from externally located servers such as AF. For example, the NWDAF may collect the above-described information for UAS terminals that have previously operated (providing a record of the UAS operation past) and nearby ground networks. The NWDAF, which has collected information from OAM, NF, and AF, collects records of such collected information and internally analyzes and predicts information related to network failure, congestion, and communication quality that may occur in specific regions and under certain circumstances. It can be analyzed through methods such as algorithms or machine learning.

Step 1-The UTM 1006 may apply to the core network to subscribe to event information related to the current network service area through the NEF 1005. UTM is a device located outside the mobile communication network and can internally perform a role as an AF defined in 3GPP, or send a request to NEF through another device that plays the role of AF.

A message (eg, Nnef_EventExposure_Subscription) for which the UTM sends an event subscription request to NEF may include an event identifier (Event ID) to be subscribed, a filter, and/or values related to event reporting. In the present disclosure, an event subscription is requested for information related to situation information of a network by region, and the event identifier requests subscription to an allowed operational area as an event identifier. Filter types used when limiting or more detailed information on network status information on permitted operating areas is desired include: Device Type, UE Capability, Operation Purpose (Mission), Time, Owner information, operator information, departure point (Departure), destination (Destination), waypoints (Waypoints), altitude (Altitude), and / or area (Area), and the like may be included. At this time, the UTM may additionally transmit information related to the quality of service requirements according to the purpose of operation of the unmanned aerial vehicle or the unmanned aerial vehicle (QoS requirements). Typical factors for service quality requirements include bandwidth, delay, error rate, packet loss, peak transmission rate, and packet delay budget. May be included. In addition, the UTM may limit the area in which information is desired to be received according to the filter region of interest and the type and purpose of the UAV. If the filter is not included, the network status for the entire area providing network service can be provided according to the internal policy of the mobile communication network.

All of the factors used in the filter are optional, and a filter can be configured with a combination of each factor. The device type may include information related to the device configuration of the UAV, such as the UAV type, UAV model, and UAV manufacturer. In the UE capability, it is possible to express the wireless access technologies supported by the unmanned aerial vehicle and the functions that can be supported by the core network. The purpose of operation expresses the purpose of operation of the unmanned aerial vehicle, and may be expressed as a general string, or the purpose may be expressed in a pre-arranged category or code. Owner information and pilot information can be used for the purpose of confirming related contracts between the telecommunication operator and the UAV owner or pilot in relation to the operation of a specific UAV. The origin, destination, and stopover information are used for the purpose of limiting the region including the origin, destination, and stopover, and if this information is not provided, the core network can provide the network status for the entire service area. The altitude information indicates the main altitude at which each terminal will fly, and is transmitted to take into account network conditions that vary according to altitude. Coordinate values for a specific area may be transmitted as area information. There may be various ways of expressing this coordinate, but the area can be expressed in various ways, such as a center value, a diameter, and a rectangular coordinate expressed by two points. Alternatively, the name of the area on the actual jurisdiction may be transmitted as area information.

Depending on the embodiment, for example, when the UTM is classified as a reliable AF, the UTM may apply for a subscription to an event related to the current network service area directly through the PCF without going through NEF.

Step 2-NEF can change some or all of the information received from UTM from the form of information used outside to the form of information used inside the network. For example, methods of expressing longitude and latitude used in GPS or other local information can be converted into TAI (Tracking Area ID) or Cell ID used inside the network. The functions of the UE can also be converted into the UE's radio capability and core network capability, and if the related functions are expressed in a specific code, each such function can be converted into a code and transmitted. have.

Step 3-NEF forwards the converted UTM subscription request to the PCF. To this end, NEF may transmit a message (eg, Npcf_EventExposure_Subscription request) for a converted event subscription request to the PCF. The type of the factor transmitted through the message may be the same as the message transmitted by the UTM, and in the case of the converted factor, the value may be different from the value of the factor included in the message transmitted by the UTM.

Step 4-The PCF may send an analysis information subscription request to the NWDAF to check information on an area that satisfies the communication service quality requirements of the unmanned aerial vehicle or the requested terminal. To this end, the PCF may transmit a message for this subscription request (eg, Nnwdaf_AnalyticsSubscription request) to the NWDAF. The type of the factor transmitted through the message may be the same as the message transmitted by the UTM, and in the case of the converted factor, the value may be different from the value of the factor included in the message transmitted by the UTM.

Step 5-NWDAF satisfies the requested network quality condition based on the information received from OAM, internal policy, requested filter, and/or information collected past and present from AF/NF in order to process analysis information subscription request. An area in which the unmanned aerial vehicle can receive communication service (eg, an operation area that satisfies the requested communication service requirement) is calculated. As a result of the calculation, the operation area can be expressed as an operable area or a non-operational area. When a service cannot be provided or quality is not satisfied due to a failure or a temporary change in network configuration, a detailed region and time zone in which communication is not provided may be included in a message for a response or notification of the PCF to be described later in step 5. For example, the detailed area and time zone may be included in the list of available or non-operable areas in the message. For example, in the case of a list of operational areas, detailed regions and operational time zones for operational areas may be included. Alternatively, in the case of a list of non-operational areas, detailed regions and non-operational time zones for the non-operational areas may be included. Information on an operable area or an inoperable area may be expressed as a set of detailed areas. In addition, the detailed area can be expressed as TAI, Cell ID, etc. used inside the mobile communication network. In addition, there may be various expression methods for information related to the region, but the expression form of the information representing the region may be included in a message for a response or notification of the PCF, which will be described later in step 5. When expressed as an operable area, the recommended maximum number of unmanned aerial vehicles may be included in a message for a response or notification of the PCF, which will be described later in step 5.

Step 6-The NWDAF delivers the results of analysis on the operational and non-operable areas that meet the communication quality requirements to the PCF. To this end, the NWDAF may transmit a response or notification message (response or notification message (eg, Nnwdaf_AnalyticsSubscription notify) to the PCF) to the message (third request message) of step 4. In this case, the message (third request message) may be delivered to the PCF. The notification message) may include a list of available or non-operable areas satisfying the requested communication service requirements (service area list) In addition, the third notification message includes the number of devices recommended in the service area. It may further include information indicating.

Step 7-In order to process the event subscription request, the PCF is based on the information received from OAM and NWDAF, internal policies, and/or the contents of the requested filter, so that the unmanned aerial vehicle that satisfies the condition can receive communication service It is calculated for an area (eg, a service area that satisfies the requested communication service requirements). As a result of the calculation, the service area can be expressed as an operable area or an area that cannot be operated. If the area is expressed as an area that cannot be operated, information on the reason for the inability to be operated can be expressed for each detailed area. For example, the causes of prohibited areas, densely populated areas, out of range of service, and disability may be expressed. When the use is not possible due to a failure or temporary network configuration change, a detailed region and time zone in which the communication service is not provided may be included in a message for a response or notification of the PCF to be described later in step 5. For example, the detailed area and time zone may be included in the list of available or non-operable areas in the message. For example, in the case of a list of operational areas, detailed regions and operational time zones for operational areas may be included. Alternatively, in the case of a list of non-operational areas, detailed regions and non-operational time zones for the non-operational areas may be included. Information on an operable area or an inoperable area may be expressed as a set of detailed areas. In addition, the detailed area can be expressed as TAI, Cell ID, etc. used inside the mobile communication network. In addition, there may be various expression methods for information related to the region, but the expression form of the information representing the region may be included in a message for a response or notification of the PCF, which will be described later in step 5. When expressed as an operable area, the recommended maximum number of unmanned aerial vehicles may be included in a message for a response or notification of the PCF, which will be described later in step 5.

Step 8-The PCF delivers to NEF a list of available or unavailable areas that meet the requested communication service requirements. To this end, the PCF may transmit a message (response or notification message (eg, Npcf_EventExposure_notify) to NEF) for response or notification to the message of step 3 (the second request message), in this case, the message (third notification). The message) may include a list of available or non-operable areas (list of service areas) In addition, the second notification message may further include information indicating the number of devices recommended in the corresponding service area.

Step 9-NEF converts the information on the available or non-operable area that satisfies the network quality requirements delivered to the PCF into information that can be known from the outside. On the other hand, when provided without conversion, the UTM may be considered a case where the mapping information for the TAI or Cell ID is provided from the mobile communication network operator and can be interpreted.

Step 10-NEF delivers the information on the operational or non-operable area that satisfies the converted quality requirements to the UTM. To this end, the NEF may transmit a response or notification message (response or notification message (eg, Npcf_EventExposure_notify) to the UTM) to the message (first request message) of step 1. In this case, the message (first response) The message) may include a list of available or non-operable areas (list of service areas) In addition, the first response message may further include information indicating the number of devices recommended in the corresponding service area.

Step 11-The UAV or UAV controller 1001 transmits information related to authentication and operation of the unmanned aerial vehicle to the UTM.

Step 12-UTM decides whether to authorize UTS and permit aviation based on information transmitted by UAS, network status information received from the above-described core network, information collected by itself, and/or policy. In this process, UTM can determine whether the UAS is flying, operating time, and route through the process of modifying the route of UAS in its own way. Alternatively, the UTM may determine the UAS request path as the UAS path.

Step 13-UTM passes authentication and flight authorization information to UAS. UAS performs normal operation according to the authentication result.

The process after step 13 may be the same as the process after step 11 of the first embodiment or the second embodiment described above. This is a process that occurs additionally according to the change of the network situation, and may be selectively performed according to the policy, or may not be performed if the event report-related information is already satisfied in step 1.

[Eighth Example]

In the above-described embodiment 5-7, when a 5G Core Network is used, communication methods that can be used by the unmanned aerial vehicle may vary. For example, in the 5G core network, a gNB supporting NR and an eNB supporting E-UTRA used in LTE can support the RAT type. In addition, in addition to a method of communicating with the core network through a communication interface that can be used by the UAV, there may be cases where proximity service (D2D) using a sidelink is required. Accordingly, in the above-described embodiments, when 5GC provides the UTM with the communicable area and each expected quality of service, additionally provided values may be different according to the RAT type, CN (core network) type, and interface.

As described above, according to the communication method used by the UAV, the present disclosure can distinguish between a service available area provided to the UTM and the provision of information on an expected service quality for each area. In the above-described embodiment 5-7, the UTM additionally provides the following filters, e.g., RAT type, CN Type, Interface, and Frequency, in the step of sending a request to provide each information to 5GC (ex.subscription request). can do. The RAT type refers to a communication technology with a base station used by the UAV, and representatively, NR, E-UTRA, and GERAN may be used. CN Type is the type of core network that UAV uses for communication, and 5GC and EPC are representative. The interface may include the use of a Uu interface or a sidelink interface through which the UAV communicates with the core network. Frequency refers to a frequency band used for communication, and may be expressed as a numerical band or high, low in the case of 5G. Upon receiving the request including the additional filter information, the PCF or the NWDAF may differentiate information on whether a service corresponding to the filter is allowed and the expected communication quality and provide the information to the UTM.

In addition, when the UTM knows in advance information on a RAT/Frequency Selection Priority (RFSP) index preferred or supported by each UAV, the above filter information may be replaced by using the RFSP index value as a filter value. For example, if RFSP index = 1 is assigned as data centric, the service corresponding to each RFSP index value by inferring the RAT type, CN Type, Interface, and Frequency expected to be used for data communication in each region. Information on whether to allow or not and expected communication quality can be distinguished and provided.

11 shows the structure of a network entity according to an embodiment of the present invention. The network entity of FIG. 11 may be, for example, any one of the entities of FIG. 1. For example, the entity is a UAV, a UAV controller, a terminal device (ME) that shares a UAV or service, a UAS consisting of a UAV and a UAV controller, a base station supporting wireless communication, AMF, SMF, PCF, NWDAF, NEF, UDM Alternatively, it may be one of UDR, UPF, unmanned aerial vehicle traffic control system (UTM), or OAM. The network entity illustrated in FIG. 11 is a network entity used to implement the first to seventh embodiments described above, and may be the same or different entity from the network entity illustrated in FIG. 6.

Referring to FIG. 11, the network entity may include a transmission/reception unit 1110, a control unit 1120, and a storage unit 1130. In the present invention, the control unit may be defined as a circuit or an application-specific integrated circuit or at least one processor.

The transceiver 1110 may transmit and receive signals with other network entities. The transceiver 1110 may receive system information from, for example, a base station, and may receive a synchronization signal or a reference signal.

The controller 1120 may control the overall operation of the network entity according to the embodiment proposed in the present invention. For example, the controller 1120 may control a signal flow between blocks to perform an operation according to the above-described procedure with reference to FIGS. 8 to 10. For example, the controller 1120 may control an operation proposed in the present invention to provide service detection in a mobile communication system according to an embodiment of the present invention.

The storage unit 1130 may store at least one of information transmitted and received through the transmission/reception unit 1110 and information generated through the control unit 1120. For example, the storage unit 1130 may store information required for service detection according to the above-described embodiment.

12 illustrates a method of a first entity performing a policy control function (PCF) in a mobile communication system according to an embodiment of the present invention. In FIG. 12, descriptions overlapping with those described above in the embodiments of FIGS. 8 to 10 are omitted.

Referring to FIG. 12, a first entity performing a policy control function (PCF) is a request message for requesting information related to a service area for an unmanned aerial vehicle from a second entity performing unmanned aerial vehicle traffic management. Can receive (S1210).

As an embodiment, the request message may include filter information used to generate information related to the service area, and the filter information may include device type information of the unmanned aerial vehicle and flight purpose information of the unmanned aerial vehicle. .

As an embodiment, the filter information may further include information on quality of service (QoS) requirements for the unmanned aerial vehicle.

In an embodiment, the filter information includes device performance information of the unmanned aerial vehicle, owner information of the unmanned aerial vehicle, owner information of the unmanned aerial vehicle, pilot information of the unmanned aerial vehicle, information about the origin of the unmanned aerial vehicle, and destination of the unmanned aerial vehicle. It may further include at least one of information, stopover information of the unmanned aerial vehicle, time information associated with the navigation of the unmanned aerial vehicle, area information associated with the navigation of the unmanned aerial vehicle, or altitude information associated with the navigation of the unmanned aerial vehicle.

As an example, the information related to the service area may include a list of an operable area or an unoperable area for the unmanned aerial vehicle.

As an embodiment, the information related to the service area may include a list of an operable area or an unoperable area for the unmanned aerial vehicle that satisfies the service quality requirement.

The first entity may generate information related to the service area based on the request message (S1220).

The first entity may transmit a response message including information related to the service area (S1230).

13 shows a method of a first entity performing a network data analysis function (NWDAF) in a mobile communication system according to an embodiment of the present invention. In FIG. 13, descriptions overlapping with those described above in the embodiments of FIGS. 9 to 10 will be omitted.

Referring to FIG. 13, a first entity performing a policy control function (PCF) is a service area that satisfies a quality of service (QoS) requirement for an unmanned aerial vehicle from a second entity performing unmanned aerial vehicle traffic management. A request message for requesting information related to) may be received (S1310).

As an embodiment, the request message may include filter information used to generate information related to the service area, and the filter information may include device type information of the unmanned aerial vehicle and flight purpose information of the unmanned aerial vehicle. .

As an embodiment, the filter information further comprises information on quality of service (QoS) requirements for the unmanned aerial vehicle.

In an embodiment, the filter information includes device performance information of the unmanned aerial vehicle, owner information of the unmanned aerial vehicle, owner information of the unmanned aerial vehicle, pilot information of the unmanned aerial vehicle, information about the origin of the unmanned aerial vehicle, and destination of the unmanned aerial vehicle. It may further include at least one of information, stopover information of the unmanned aerial vehicle, time information associated with the navigation of the unmanned aerial vehicle, area information associated with the navigation of the unmanned aerial vehicle, or altitude information associated with the navigation of the unmanned aerial vehicle.

As an embodiment, the information related to the service area includes a list of an operable area or an unoperable area for the unmanned aerial vehicle.

As an embodiment, the information related to the service area may include a list of an operable area or an unoperable area for the unmanned aerial vehicle that satisfies the service quality requirement.

The first entity may generate information related to the service area based on the request message (S1320).

The first entity may transmit a response message including information related to the service area (S1330).

The embodiments disclosed in the present specification and the drawings above are merely specific examples for easy explanation and understanding of the present invention, and are not intended to limit the scope of the present invention. In addition, it goes without saying that one or more of the above-described various embodiments may be combined and performed. Accordingly, the scope of the present invention should be construed that all changes or modifications derived from the present disclosure in addition to the embodiments disclosed herein are included in the scope of the present invention.

Claims (14)

In a method performed by a policy control function (PCF) entity for an unmanned aerial system (UAS) service in a wireless communication system,
Receiving, from a server managing the UAS service, a request message for subscribing to network capabilities-the request message includes information on a flight event;
Checking the network capability including information on mobility restrictions based on the information on the flight event; And
And transmitting a notification message including the network capability to a server that manages the UAS service. The method of claim 1,
The information on the flight event includes at least one of information on a device type, information on a flight time, information on a flight path, information on a flight purpose, and information on a flight altitude. The method of claim 2,
The information on the flight path, characterized in that it comprises information on a departure point, a destination, and a stopover point. The method of claim 1,
The information on the mobility restriction includes at least one of list information of allowed areas and list information of disallowed areas. The method of claim 2,
The flight path information is translated into a list of cell IDs or tracking area IDs, and the translated information is transmitted from a network exposure function (NEF) entity or received from a server managing the UAS service. How to do it. The method of claim 1,
The method of claim 1, wherein the network capability further includes network coverage information. The method of claim 6,
The network coverage information, characterized in that it comprises at least one of information on a network coverage state and information on network quality. In a policy control function (PCF) entity for UAS (unmanned aerial system) service in a wireless communication system,
A transmission/reception unit; And
Receiving a request message for subscribing to network capabilities from the server managing the UAS service-the request message includes information on a flight event,
Based on the information on the flight event, check the network capability including information on mobility restrictions,
PCF entity comprising a control unit for controlling to transmit a notification message including the network capability to the server managing the UAS service. The method of claim 8,
The information on the flight event includes at least one of information about a device type, information about a flight time, information about a flight path, information about a flight purpose, and information about a flight altitude. The method of claim 9,
The information on the flight path, PCF entity, characterized in that it includes information on a departure point, a destination, and a stopover point. The method of claim 8,
The information on the mobility restriction, the PCF entity, characterized in that it includes at least one of the list information of the allowed area and the list information of the disallowed area. The method of claim 9,
The flight path information is translated into a list of cell IDs or tracking area IDs, and the translated information is transmitted from a network exposure function (NEF) entity or received from a server managing the UAS service. PCF entity. The method of claim 8,
The PCF entity, wherein the network capability further includes network coverage information. The method of claim 13,
Wherein the network coverage information includes at least one of information on a network coverage state and information on a network quality.

Images