KR20230051017A - Communication method and apparatus in wireless communication system supporting uncrewed aerial system service - Google Patents

Abstract

The present disclosure relates to a communication method and apparatus in a wireless communication system supporting unmanned aerial system services. According to an embodiment of the present disclosure, the communication method of a first network entity, responsible for a network exposure function in a wireless communication system supporting unmanned aerial system services, comprises the processes of: when an event related to a change in aerial joining information of a terminal using the unmanned aerial system service occurs, receiving a first request message requiring a notification on the event from a second network entity performing an authentication procedure of the terminal; when the aerial joining information is changed, receiving a first notification message containing the changed content of the aerial joining information from a third network entity responsible for mobility management and receiving the notification request for the event; and based on the received notification message, transmitting a second notification message containing the changed content of the aerial joining information to the second network entity. The present disclosure provides a method and an apparatus for stably managing unmanned aerial system services in a wireless communication system.

Description

Communication method and apparatus in a wireless communication system supporting unmanned aerial system service

The present disclosure relates to an apparatus and method for providing an unmanned aerial vehicle system service in a wireless communication system.

Efforts are being made to develop an improved 5G communication system or pre-5G communication system to meet the growing demand for wireless data traffic after the commercialization of the 4G communication system. For this reason, the 5G communication system or pre-5G communication system is being called a Beyond 4G Network communication system or a Post LTE system. The 5G communication system defined by 3GPP is called the New Radio (NR) system.

In order to achieve a high data rate, the 5G communication system is being considered for implementation in a mmWave band (eg, a 60 gigabyte (60 GHz) band). In order to mitigate the path loss of radio waves and increase the propagation distance of radio waves in the ultra-high frequency band, beamforming, massive MIMO, and Full Dimensional MIMO (FD-MIMO) are used in 5G communication systems. ), array antenna, analog beam-forming, and large scale antenna technologies have been discussed and applied to NR systems.

In addition, to improve the network of the system, in the 5G communication system, an evolved small cell, an advanced small cell, a cloud radio access network (cloud RAN), and an ultra-dense network , Device to Device communication (D2D), wireless backhaul, moving network, cooperative communication, Coordinated Multi-Points (CoMP), and interference cancellation etc. are being developed.

In addition, in the 5G system, advanced coding modulation (Advanced Coding Modulation: ACM) methods FQAM (Hybrid FSK and QAM Modulation) and SWSC (Sliding Window Superposition Coding), advanced access technologies FBMC (Filter Bank Multi Carrier), NOMA (non-orthogonal multiple access), SCMA (sparse code multiple access), and the like are being developed.

On the other hand, the Internet is evolving from a human-centered connection network in which humans create and consume information to an Internet of Things (IoT) network in which information is exchanged and processed between distributed components such as things. 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, technical elements such as sensing technology, wired/wireless communication and network infrastructure, service interface technology, and security technology are required, and recently, sensor networks for connection between objects and machine to machine , M2M), and MTC (Machine Type Communication) technologies are being studied. In the IoT environment, intelligent IT (Internet Technology) services that create new values in human life by collecting and analyzing data generated from connected objects can be provided. IoT is a field of smart home, smart building, smart city, smart car or connected car, smart grid, health care, smart home appliances, advanced medical service, etc. can be applied to

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

In addition, as described above, with the development of the wireless communication system, the wireless communication system can provide various services, and among the various services, in relation to the unmanned aerial vehicle (UAV) service proposed in the 3GPP standard, There is a demand for a method of signaling authentication-related control information generated due to mobility.

The present disclosure provides a method and apparatus for stably managing an unmanned aerial vehicle system service in a wireless communication system.

In addition, the present disclosure provides a method and apparatus for managing subscription information related to authentication in a wireless communication system supporting an unmanned aerial vehicle system service.

In addition, the present disclosure provides a method and apparatus for notifying the occurrence of a change in air subscription information in a wireless communication system supporting an unmanned aerial vehicle system service.

According to an embodiment of the present disclosure, a communication method of a first network entity responsible for a network exposure function in a wireless communication system supporting an unmanned aerial vehicle system service is related to a change in aviation subscription information of a terminal using the unmanned aerial vehicle system service. When an event occurs, receiving a first request message for requesting notification of the event from a second network entity that performs an authentication procedure of the terminal; A process of receiving a first notification message including changes in the air subscription information from a third network entity in charge of mobility management that has received the notification request for the notification; and based on the received notification message, the first notification message 2 sending a second notification message including the changed contents of the air subscription information to a network entity;

In addition, according to an embodiment of the present disclosure, a first network entity responsible for a network exposure function in a wireless communication system supporting an unmanned aerial vehicle system service includes a transceiver and, through the transceiver, a terminal using the unmanned aerial vehicle system service. When an event related to a change in subscription information occurs, a first request message requesting notification of the event is received from a second network entity performing an authentication procedure of the terminal, and the air subscription information is received through the transceiver. When a change in the event occurs, a first notification message including the change in the air subscription information is received from a third network entity in charge of mobility management that has received the notification request for the event, and through the transceiver. , a processor configured to send a second notification message including the change in the air subscription information to the second network entity based on the received notification message.

1A is a diagram showing an example of a communication system including 5GS and EPS for UAV according to an embodiment of the present disclosure;
1B is a diagram illustrating a structure of a wireless communication system supporting interworking between 5GS and EPS according to an embodiment of the present disclosure;
2A and 2B are diagrams illustrating an example of a UUAA revocation procedure for notifying a change in air subscription information using an Event Exposure service of UDM in a wireless communication system according to an embodiment of the present disclosure;
3A and 3B are diagrams illustrating an example of a UUAA revocation procedure for notifying a change in air subscription information using an SDM service of UDM in a wireless communication system according to an embodiment of the present disclosure;
4A and 4B are diagrams illustrating an example of a UUAA revocation procedure for notifying a change in aviation subscription information using SDM and Event Exposure services of UDM and AMF in a wireless communication system according to an embodiment of the present disclosure;
5A and 5B are diagrams illustrating an example of a UUAA revocation procedure for notifying a change of air subscription information using SDM service and Event Exposure service of UDM and SMF in a wireless communication system according to an embodiment of the present disclosure; and
6 is a diagram illustrating an example of a configuration of a network entity according to an embodiment of the present disclosure.

Hereinafter, preferred embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. At this time, it should be noted that the same components in the accompanying drawings are indicated by the same reference numerals as much as possible. In addition, detailed descriptions of well-known functions and configurations that may obscure the subject matter of the present disclosure will be omitted.

In describing the embodiments in this specification, descriptions of technical contents that are well known in the art 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 without obscuring it by omitting unnecessary description.

For the same reason, in the accompanying drawings, some components are exaggerated, omitted, or schematically illustrated. Also, the size of each component does not entirely reflect the actual size. In each figure, the same reference number is assigned to the same or corresponding component.

Advantages and features of the present disclosure, and methods for achieving them, will become clear with reference to embodiments described below in detail in conjunction with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below and may be implemented in various different forms, only the present embodiments make the disclosure of the present disclosure complete, and the common knowledge in the art to which the present disclosure belongs It is provided to fully inform the possessor of the scope of the disclosure, and the disclosure is only defined by the scope of the claims. Like reference numbers designate like elements throughout the specification.

At this time, it will be understood that each block of the process flow chart diagrams and combinations of the flow chart diagrams can be performed by computer program instructions. These computer program instructions may be embodied in a processor of a general purpose computer, special purpose computer, or other programmable data processing equipment, so that the instructions executed by the processor of the computer or other programmable data processing equipment are described in the flowchart block(s). It creates means to perform functions. These computer program instructions may also be stored in a computer usable or computer readable memory that can be directed to a computer or other programmable data processing equipment to implement functionality in a particular way, such that the computer usable or computer readable memory The instructions stored in are also capable of producing an article of manufacture containing instruction means that perform the functions described in the flowchart block(s). The computer program instructions can also be loaded on a computer or other programmable data processing equipment, so that a series of operational steps are performed on the computer or other programmable data processing equipment to create a computer-executed process to generate computer or other programmable data processing equipment. Instructions for performing processing equipment may also provide steps for performing the functions described in the flowchart block(s).

Additionally, each block may represent a module, segment, or portion of code that includes one or more executable instructions for executing specified logical function(s). It should also be noted that in some alternative implementations it is possible for the functions mentioned in the blocks to occur out of order. For example, two blocks shown in succession may in fact be executed substantially concurrently, or the blocks may sometimes be executed in reverse order depending on their function.

At this time, the term '~unit' used in this embodiment means software or a hardware component such as a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC), and '~unit' refers to certain roles. carry out However, '~ part' is not limited to software or hardware. '~bu' may be configured to be in an addressable storage medium and may be configured to reproduce one or more processors. Therefore, 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, circuitry, data, databases, data structures, tables, arrays, and variables. Functions provided within components and '~units' may be combined into smaller numbers of components and '~units' or further separated into additional components and '~units'. In addition, components and '~units' may be implemented to play one or more CPUs in a device or a secure multimedia card.

In embodiments of the present disclosure, a base station is a subject that allocates resources of user equipment (UE), and includes gNode B, gNB, eNode B, eNB, Node B, BS, radio access unit, base station controller, Alternatively, it may be at least one of nodes on the network. In addition, the base station includes an Integrated Access and Backhaul-donor (IAB-donor), which is a gNB that provides network access to the terminal (s) through a network of backhaul and access links in the NR system, and the terminal (s) ) and an IAB-node, which is a radio access network (RAN) node supporting NR backhaul links to the IAB-donor or other IAB-nodes. . The terminal is wirelessly connected through the IAB-node and can transmit and receive data with an IAB-donor connected to at least one IAB-node through a backhaul link.

In addition, the UE may include a terminal, a mobile station (MS), a cellular phone, a smart phone, a computer, or various devices capable of performing communication functions. In the present disclosure, downlink (DL) is a radio transmission path of a signal transmitted from a base station to a terminal, and uplink (UL) refers to a radio transmission path of a signal transmitted from a terminal to a base station.

In the specific description of the embodiments of the present disclosure, New RAN (NR), a radio access network on the 5G communication standard specified by the 3rd Generation Partnership Project (3GPP), a wireless communication standardization organization, and the packet core (5G System, or 5G Core Network, or NG Core: Next Generation Core), but the main gist of the present disclosure is to provide a slight It can be applied as a modification, which will be possible with the judgment of those skilled in the art of the present disclosure.

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

Hereinafter, the present disclosure may also be applied to a wireless communication system for providing interworking of network slices (or network slicing) in a wireless communication system. Specifically, 5G providing a network slice function in a wireless communication system through the present disclosure The present disclosure may also be applied to an interworking structure between a network system and an EPS network system. In the present disclosure, the 5G network system may be referred to as a first wireless communication system and the EPS network system may be referred to as a second wireless communication system, and the two The system may also be collectively referred to as a wireless communication system.

In the following description, terms referring to signals, terms referring to channels, terms referring to control information, terms referring to network entities, terms referring to components of a device, etc. are used for convenience of description. it is exemplified In addition, terms for identifying nodes, terms for messages, terms for interfaces between network entities, terms for various information, and the like used in the following description are illustrated for convenience of description. Accordingly, the present disclosure is not limited to the terms described below, and other terms having equivalent technical meanings may be used.

In addition, although the present disclosure describes various embodiments using terms used in some communication standards (eg, 3rd Generation Partnership Project (3GPP)), this is only an example for explanation. Various embodiments of the present disclosure may be easily modified and applied to other communication systems.

The 3GPP standard standardizes the system architecture and procedures of the 5G network, and mobile operators can provide various services in the 5G network. In order to provide each service, a mobile communication service provider needs to satisfy different service requirements (for example, delay time, communication range, data rate, bandwidth, reliability, etc.) for each service.

In addition, the 5G system supports network slicing, and traffic for different network slices can be processed by different protocol data unit (PDU) sessions. The PDU session may mean an association between a data network providing a PDU connection service and a terminal. The network slicing is a set of network functions (NFs) to support various services having different characteristics, such as broadband communication service, mission critical service such as massive IoT, V2X, etc., logically It can be understood as a technique for configuring and separating different network slices. Therefore, even if a communication failure occurs in a certain network slice, communication in other network slices is not affected, so that stable communication service can be provided. In the present disclosure, "slice" may be used interchangeably as a term meaning "network slice". In such a network environment, a terminal can access multiple network slices when receiving various services. The network function (NF) may be implemented as a network element as a software instance running on hardware or a virtualized function instantiated on an appropriate platform.

A mobile communication service provider may configure the network slice and allocate network resources suitable for a specific service for each network slice or set of network slices. The network resource may mean an NF, a logical resource provided by the NF, or radio resource allocation of a base station.

For example, a mobile communication operator may configure network slice A to provide mobile broadband service, network slice B to provide vehicle communication service, and network slice C to provide IoT service. That is, in the 5G network as described above, a corresponding service can be efficiently provided to a terminal through a network slice specialized to suit the characteristics of each service.

A mobile operator can operate both a 5G network and an EPS (or LTE-based network or 4G network) network together. After accessing the 5G network and using the service, the terminal may move to the EPS network. Alternatively, the terminal may access the EPS network and use the service, then move to the 5G network. Interworking between networks (between systems) related to movement of such a terminal may be referred to as 5G core (5GC)-EPC interworking or 5G system (5GS)-EPS interworking.

Network technology in the present disclosure may refer to standards defined by the International Telecommunication Union (ITU) or 3GPP (eg, TS 23.501, TS 23.502, TS 23.503, etc.), and the network structure of FIGS. 1A and 1B Each component included in may mean a physical entity, or may mean software that performs an individual function or hardware combined with software. In FIGS. 1A and 1B, reference numerals denoted as Nx, such as N1, N2, N3, ..., represent known interfaces between NFs in a 5G core network (CN), and related descriptions are based on standard specifications (TS 23.501). , so a detailed description thereof will be omitted.

Hereinafter, 3GPP standards will be described for a communication method and apparatus for supporting operation of an unmanned aerial vehicle in a wireless communication system according to embodiments of the present disclosure.

The present disclosure relates to a wireless communication system providing an unmanned aerial vehicle system service, and specifically, an unmanned aerial vehicle (UAV) in a 5G system, an unmanned aerial vehicle controller (UAVC) for controlling the UAV, and the UAV and UAS traffic management (UTM), which is a network entity that controls an unmanned aerial system (UAS) including at least one of a UAVC, related to authentication caused by the mobility of a UAV. We propose a method for signaling information stably/efficiently. In addition, in the present disclosure, in communication between the UAS and the UTM, the UAS may subscribe to the UTM for transmission and reception of control information and/or user data. When the UAS/UAV subscribes to the UTM, if there is only a subscription exposure setting, the communication connection of the UAV may be interrupted/disconnected, and a method for solving this problem is proposed.

In the present disclosure, the UAV may be various unmanned mobile devices equipped with a communication device, such as a drone. It should be noted that the UAV of the present disclosure is not limited to drones. Currently, in a communication method for operating a drone, a method using a cellular network represented by mobile communication is not supported. Most drone operation methods generally use a method of operating a drone and a drone controller using a protocol provided by a manufacturer through a short-range wireless communication network such as RF (Radio Frequency), Bluetooth, and Wi-Fi. Therefore, in order to control the UAV in the wireless communication system, it is necessary to study problems and improvements related to the mobility of drones and problems that could not be predicted in the existing short-range communication network.

In the present disclosure, a UAV can fly, such as a hobby or commercial drone that can be controlled at a short distance and an unmanned reconnaissance aircraft that operates through a specific orbit, and is operated remotely or autonomously to perform a purpose without a pilot boarding the aircraft body. collectively In addition, the UAV to which the present disclosure is applied is equipped with a device capable of communication such as a mobile communication network, Wi-Fi, and Bluetooth, so that a controller of the UAV, a UAV capable of short-range communication, and / or located outside such as a control center Communication through wireless communication between entities may be possible.

In the present disclosure, a terminal may include at least one of a UAV and a UAVC for controlling the UAV, and a form capable of operating a UAV including the UAV and the UAVC will be referred to as a UAS. In addition, the terminal may include a mobile equipment (ME). In the present disclosure, the terminal may be referred to by various names such as UAV, UAVC (or UAV controller), UAS, and UAV/UAVC. In addition, the terminal may include a wireless device capable of accessing various wireless networks such as a 5G system or a Wi-Fi network.

The UAVC may be a hardware device or may be a form of software operated in a cloud network or server. It can have the ability to access 3GPP networks through LTE (Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access), GERAN (GSM/EDGE Radio Access Network), UTRA), 5G networks or Non-3GPP networks. there is.

Referring to 3GPP standard, TS 22.125, UAS includes a UAV and a UAV controller corresponding to UAVC. In addition, the UAS is connected to the UTM or USS (UAS Service Supplier) system responsible for managing the UAS(s), and the UTM or USS is responsible for UAS authentication, UAV and UAV controller verification and certification, and unmanned aerial vehicle coordination. It can provide various functions such as provision of static or real-time information required for flight, route permission through flight route purpose confirmation, and forced transfer of UAS control authority in case of emergency. Also, in the present disclosure, the USS may include the UTM function. In a wireless communication system, it is necessary to support network connectivity of UAVs and UAV controllers constituting UAS, and to efficiently provide network services so that devices constituting each UAS can be controlled through UTM/USS.

In addition, in the present disclosure, the wireless communication system considers the UAV as a general terminal and performs a registration procedure for the general terminal for the UAV, and additionally, the UTM or USS located outside may perform an authentication procedure related to the flight of the UAV. The UTM or USS may revoke the authentication result or update related data.

1A is a diagram illustrating an example of a communication system including 5GS and EPS for a UAV according to an embodiment of the present disclosure. Here, 5GS refers to a 5G system defined by the 3GPP standard, and evolved packet system (EPS) refers to an LTE system defined by the 3GPP standard. The 5GS includes an NG-RAN corresponding to a base station and a 5GC corresponding to a core network, and the EPS includes a (R) AN corresponding to a base station and an evolved packet core (EPC) corresponding to a core network. In FIG. 1A , UE 110 may receive UAS service through 5GS 120 or EPS 130 .

Referring to FIG. 1A, a UE 110 may include at least one of a UAV and a UAVC (or UAV controller) as described above. In addition, the terminal 110 may include a mobile equipment (ME) capable of performing communication by accessing the 5GS 120 or the EPS 130. The ME may be understood as a device excluding a UMTS Subscriber Identity Module (USIM) in a general UE. Accordingly, the UE 110 may be a network entity including at least one of UAV, UAVC, USS, or ME.

In FIG. 1A, the 5GS 120 includes a radio access network (NG-RAN) and a 5G core network (5GC), and the NG-RAN is a base station (e.g., gNB or IAB (Integrated Access and Backhaul), etc.). The base station transmits control information and/or data received from the terminal 110 to other entity(s) included in the 5GC by interacting with the core network (i.e., 5GC) to transmit the control information and/or data received from the terminal 110 to the terminal 110 from the 5GC. settings, transmit/receive control information and/or data between the terminal 110 and 5GC, or perform various procedure(s) for management including authentication of the terminal 110. In addition, the terminal 110 is not connected to the base station of the NG-RAN, and a technology using a side link such as Prose (Proximity Service) for direct communication between the terminal 110 and other terminals or Non-3GPP wireless access such as WiFi and Bluetooth Technology can be used to connect with data networks.

As defined in the 3GPP NR standard, the 5GC may include network entities such as Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), and Unified Data Management (UDM).

The AMF is an entity for managing access and mobility of the terminal 110 in the 5G system. The AMF may serve as a terminal-core network endpoint through which the terminal 110 connects to other entity(s) of 5GC through the NG-RAN. For example, the AMF may perform network functions such as registration, connection, reachability, mobility management, access confirmation, authentication, and mobility event generation of the terminal 110 .

The SMF may perform a management function for a PDU (Protocol Data Unit) session of the terminal 110 . For example, SMF is a session management function through establishment, modification, and release of a session and maintaining a tunnel between a UPF and a base station necessary for this, a terminal IP (Internet Protocol) address allocation and management function, an ARP Proxy (Proxy Address Resolution Protocol) function, It can perform network functions such as user plane selection and control, traffic processing control in UPF, and billing data collection control.

The UPF serves to process user data of the terminal 110, delivers packets generated by the terminal 110 to the external data network 150, or transfers data introduced from the external data network 150 to the terminal ( 110) to process packets so that they can be delivered to. For example, the UPF serves as an anchor between radio access technologies (RATs), provides a connection between a PDU session and an external data network 150, packet routing and forwarding, packet inspection, and user plane policy. It can perform network functions such as application, traffic usage reporting, buffering, etc.

The UDM generates AKA (Authentication and Key Agreement) authentication information for 3GPP security, processes a user identifier (User ID), reverse conceals a secured user identifier (Subscriber Concealed ID, SUPI), supports the current terminal 110 It is possible to perform network functions such as managing a list of network functions (NF) to be performed and managing subscription information. A Unified Data Repository (UDR) may perform a function of storing and providing subscription information managed by the UDM, structured data for exposure, NEF, or application data related to a service.

In FIG. 1A, the NEF 140 may be in charge of transmitting or receiving events occurring in the 5G system and supporting capabilities to the outside. For example, NEF provides functions such as the ability to safely supply external application information to the core network (5GC), conversion of internal/external information, storage of information received from other NFs in UDR (not shown) and redistribution, etc. Network functions can be performed. In one example of the present disclosure, NEF 140 may perform a network function of exposing services provided by 5GS 120 to USS 151 . USS 151 may exist outside (or inside) 5GS 120. USS 151 cancels UAV flight permit and/or UAV flight permit, pairing permit between UAV and UAVC, and/or cancellation of pairing permit between UAV and UAVC through services provided by 5GS 120 through NEF 140 , QoS for location reporting, command and control (C2) communication for UAV and/or UAVC, and/or traffic management. In the present disclosure, the NEF may be referred to as UAS NF.

In the present disclosure, the UAS Service Supplier (USS) 151 may be included in the data network 150 and may transmit and receive data to and from the terminal 110 . When the terminal 110 wants to use the UAS service, 5GC is a procedure for authenticating and authorizing the terminal 110 (or UAV) to communicate with the USS 151 through a wireless communication system A UAV USS authentication and authorization procedure (UUAA) may be performed.

The UUAA procedure is performed by the AMF (UUAA-MM procedure) during the registration procedure of the terminal 110, or the PDU session establishment procedure of the terminal 110 (PDU Session Establishment) or PDN connection establishment procedure (PDN connection It may be performed (UUAA-SM procedure) by SMF+PGW-C (i.e. combo node of SMF and PGW-C) during establishment). UAS service through EPC may be provided based on the SMF+PGW-C node. In the UUAA procedure, the terminal 110 uses a CAA (Civil Aviation Administration)-Level UAV ID (identifier (ID) assigned by the USS 151 to the terminal 110 (or UAV) so that the UAS service can be used) in the 5GS and if the UDM has air subscription information for the terminal 110 (or UAV) (that is, aerial subscription data, subscriber information provided by a communication service provider so that the UAS service can be used through a wireless communication system), authentication and The licensing process is successful.

While the terminal 110 (or UAV) that has succeeded in the UUAA procedure is using the UAS service through the wireless communication system, the UDM changes the aviation subscription information for the terminal 110 (or UAV), and the corresponding communication service provider When the UAS service cannot be provided, the wireless communication system must be able to notify the USS 151 and the terminal 110 that the authentication result according to the previous UUAA procedure for the terminal 110 (or UAV) has been cancelled. Otherwise, even though the terminal 110 (or UAV) is disconnected/released from the 5GS and the control plane and/or user plane, the USS 151 interrupts/releases the connection It may not be recognized and may not be able to continuously transmit control information and data to the terminal 110 (or UAV). Therefore, in the present disclosure, while the terminal 110 (or UAV) is using the UAS service in a wireless communication system through a UUAA procedure, the air subscription information for the terminal 110 (or UAV) is changed in UDM, so that the terminal 110 is no longer ) (or UAV) is unable to use the UAS service, the wireless communication system informs the USS 151 and the terminal 110 of the change of the aviation subscription information, and the successful terminal 110 (or UAV) A method of stably managing the UAS service by canceling the previous UUAA result is proposed, and specific embodiments will be described later.

In the present disclosure, embodiments are described on the assumption that the USS 151 includes the UTM 151a, but the UTM may be configured separately from the USS 151 or the data network 150. Accordingly, it should be noted that the embodiments of the present disclosure are not limited to that the USS 151 includes the UTM 151a. For convenience of description, the USS including UTM will be briefly referred to as USS.

In FIG. 1A, the USS 151 may serve to control the traffic of the UAV. Here, traffic includes network traffic, and traffic control may include controlling the operation of actual physical UAVs. The USS 151 authenticates the connection of the terminal 110 (or UAV), authenticates the configuration of the terminal 110 (or UAV), provides information for efficient operation of the UAV, authenticates the UAV to be operated, and confirms the route, and the current UAV It can perform functions such as route and location check and UAV control in case of emergency. An entity that manages the USS 151 may be a business operator or a government or public institution. In the present disclosure, the USS 151 may provide information related to UAV operation to the control plane through the NEF 140. Communication between the USS 151 and the NEF 140 may use the N33 interface defined in the 3GPP standard. Interfaces indicated as Nx, Sx, and SGi in FIG. 1A are examples of interfaces defined in the 3GPP standard, and information exchange and control information exchange between network entities use procedures, interfaces, and protocols defined in the related 3GPP standard. can be performed However, the present disclosure is not limited to the interfaces illustrated in FIG. 1A , and it is also possible to use a new interface replacing the illustrated interfaces.

In FIG. 1A, a Third Party Authorized Entity (TPAE) 160 is a device that requests and receives information about the terminal 110 (or UAV and/or UAVC) from outside the wireless communication system. For example, the TPAE 160 may be various communication devices for controlling police officers, civil servants, and UAV traffic. TPAE 160 may communicate with the wireless communication system of FIG. 1A over the Internet or other network.

1B is a diagram illustrating the structure of a wireless communication system supporting interworking between 5GS and EPS according to an embodiment of the present disclosure. An unmanned aerial vehicle system service according to an embodiment of the present disclosure may also be applied to an interworking structure between a 5GS and an EPS as shown in FIG. 1B.

1B shows an example of an interworking structure of 5GS and EPS in a non-roaming situation. 5GS may include an NR base station (NG-RAN) or next generation node B (gNB) for radio access of the terminal 110, SMF, UPF, PCF, NSSF, UDM, UDR, and the like. EPS is an E-UTRA base station (Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN), or evolved node B (eNB)), MME, serving gateway (SGW), packet data network gateway (PGW) -U and PGW-C), PCRF (policy and charging rule function), HSS (home subscriber server), etc.

The AMF and MME are NFs that manage wireless network access and mobility for the terminal 110. The SMF, SGW, and PGW are NFs that manage a session for the terminal, and the session information includes quality of service (QoS) information, charging information, and packet processing information. The UPF and PGW are NFs that process user plane traffic (eg, user plane traffic) and are controlled by SMF and SGW. The PCF and PCRF are NFs that manage operator policy and/or PLMN policy for providing services in a wireless communication system. In addition, the PCF can be divided into a PCF in charge of AM (Access and Mobility) policy and UE policy and a PCF in charge of SM (Session Management) policy. The PCF in charge of AM/UE policy and the PCF in charge of SM policy may be logically or physically separated NFs or logically or physically one NF. UDM and HSS are NFs that store and manage UE subscriber information (UE subscription). UDR is an NF or database (Database, DB) that stores and manages data. The UDR may store subscription information of the terminal and provide the subscription information of the terminal to the UDM. In addition, the UDR may store operator policy information and provide the operator policy information to the PCF. The NSSF may be an NF that performs a function of selecting network slice instances serving the terminal or determining Network Slice Selection Assistance Information (NSSAI).

In the instance, NF exists in the form of software code, and in order to perform the function of NF in a physical computing system (eg, a specific computing system existing on a core network), a physical or / And it may mean a state in which the functions of the NF can be executed by receiving logical resources. For example, AMF Instance, SMF Instance, NSSF Instance, etc. mean a state in which physical or/and logical resources are allocated and used for the operation of AMF, SMF, NSSF, etc. from a specific computing system existing on the core network, respectively. can Therefore, AMF Instance, SMF Instance, and NSSF Instance that are allocated and used physical or/and logical resources for AMF, SMF, and NSSF operations from a specific computing system existing on the network and when physical AMF, SMF, and NSSF devices exist. can perform the same operation.

UDM of 5GS and HSS of EPS can be composed of one combo node (referred to as UDM+HSS). The UDM+HSS node may store subscriber information of the terminal 110 . The SMF of 5GS and PGW-C of EPS can be composed of one combo node (referred to as SMF+PGW-C). Instead of the PCF shown in FIG. 1B, the PCF of 5GS and the PCRF of EPS may be composed of one combo node (referred to as PCF+PCRF). UPF of 5GS and PGW-U of EPS can be composed of one combo node (referred to as UPF+PGW-C). The terminal 110 may use the EPS network service by accessing the MME of the EPS through the E-UTRA base station. In addition, the terminal can access the 5GS AMF through the NR base station and use the 5GS network service.

In this way, one NF or network entity can simultaneously support different network systems, and these NFs, network nodes or network entities can be referred to as the above-described combo node, combo NF, combined node, combined NF, interworking It may be referred to as (interworking) node, interworking NF, and the like. In addition, the function of NF exemplified by the combo node may be implemented through interworking between two or more network entities. In addition, for convenience of illustration and description, NFs that simultaneously support different network systems may be indicated by using a “+” sign or a “/” sign. For example, when SMF and PGW-C are configured as one combo node, they may be expressed as PGW-C/SMF, PGW-C+SMF, SMF/PGW-C, or SMF+PGW-C.

A terminal accesses a data network (eg, a network providing Internet service) through a 5GS or EPS system to establish a session, using identifiers such as DNN (Data Network Name) or APN (Access Point Name) Each data network can be distinguished. For data network distinction, DNN can be used in 5GS and APN can be used in EPS. The DNN and APN may be used to determine NFs related to a user plane, interfaces between NFs, and operator policies when a terminal connects a network system and a session. The DNN and APN may be understood as equivalent information and may deliver the same information. The DNN may be used, for example, to select SMF and UPF(s) for a PDU session, and may be used to select an interface (eg, N6 interface)(s) between a data network and a UPF for a PDU session. . In addition, the DNN may be used to determine a policy of a mobile communication operator to apply to a PDU session.

Also, in 5GS, the terminal 110 may be connected to one data network through at least one network slice. When a UE moves to EPS after establishing a PDU session connection through a plurality of network slices for a certain data network in 5GS, it selects one network slice according to the decision of the SMF+PGW-C node and connects to the corresponding data network. A PDN session can be established.

Also in the present disclosure, NEF 140 may be connected to PCF, SMF+PGW-C, and/or AMF to perform a network exposure function.

When there is a change in the subscription information of a terminal using the wireless airborne system service by establishing a session connection in EPS or 5GS, we propose a network operation that allows the change to be applied to the session being connected. Here, the terminal may be a terminal registered as a subscriber to EPS or 5GS.

Basic operations of the network entities UE, AMF, SMF, UPF, UDM, NEF, and USS in the embodiments of FIGS. 2 to 5 are the same as those of the corresponding network entities in FIGS. 1A and 1B, so a detailed description will be omitted. In the following description, the term “UAV UE” may be understood as a UE including at least one of a UAV and a UAVC as described in the example of FIG. 1A. In the embodiments of FIGS. 2 to 5 , service names of messages transmitted and received between network entities may refer to names defined in the 3GPP standard (TS 23.502).

2A and 2B illustrate an example of a UUAA revocation procedure for notifying a change in air subscription information using an Event Exposure service of UDM in a wireless communication system according to an embodiment of the present disclosure.

Step 200: The NEF can store the UUAA context of the UAV UE when the UUAA procedure (UUAA-MM procedure or UUAA-SM procedure), which is a procedure for authenticating and authorizing the UAV UE to communicate with the USS through the wireless communication system, succeeds. there is.

Step 201: The USS may transmit a subscription request to notify the NEF of a change in air subscription information for the UAV UE in step 200. USS may send a Nnef_EventExposure_Subsrcribe Request message. The USS may provide the NEF with a Nnef_EventExposure_Subsrcribe Request message including an event that the UDM can detect according to a change in GPSI (Generic Public Subscription Identifier), CAA-Level UAV ID, and aviation subscription information. The GPSI is an identifier used to process 5G system subscription in another network outside the 5G system, and can be used inside and outside the 5G system. A detailed definition of GPSI may refer to TS 23.501 in the 3GPP NR standard.

An example of the event that the UDM can recognize according to the change of air subscription information may include the "Change of aerial subscription" event shown in [Table 1] below. [Table 1] exemplifies the List of events for monitoring capability, and for convenience, one table has been described by dividing it into [Table 1a] to [Table 1d], and [Table 1a] to [Table 1d] are [Table 1] can be collectively referred to as

[Table 1a]

[Table 1b]

[Table 1c]

[Table 1d]

Step 202: Upon receiving the request of step 201, the NEF may request a subscription to a change event of air subscription information from the UDM. The NEF may send a Nudm_EventExposure_Subscribe Request message to the UDM. The NEF may provide the NEF with an event that the UDM can detect according to a change in SUPI (Subscription Permanent Identifier) and/or GPSI, and air subscription information. The SUPI is secured identification information and is a unique identifier assigned to each subscriber of the 5G system and can be used within the 5G system. A specific definition of SUPI may refer to TS 23.501 in the 3GPP NR standard.

Step 203: Upon receiving the request of step 202, the UDM may transmit the result of the request to the NEF. For example, if the UDM accepts the NEF request, a Nudm_EventExposure_Subscription Response message including an identifier (Subscription Correlation ID) for the NEF request in step 202 and/or an expiry time according to the policy of the communication service provider can be provided to the NEF.

Step 204: Upon receiving the result of step 203, the NEF may transmit the result of the request of the USS in step 201 to the USS. For example, if the UDM accepts the NEF's request in step 203 and the NEF accepts the USS's request, the identifier (Subscription Correlation ID) for the USS's request in step 201 and/or the carrier's policy An Nnef_EventExposure_Subscription Response message including expiry time may be provided to the USS.

Step 205: The UDM that has accepted the subscription request in step 202 can recognize that a change has occurred in the aviation subscription information of the UAV UE based on the subscription information of the terminal managed by the UDM, such as the example of [Table 2] below. . For example, when the air subscription information is changed, the value of the air subscription information (ie aerial subscription data) is changed from 'authorized' to 'not authorized' or from 'allowed' to 'not allowed' in [Table 2] below. It may be subject to change. An example of a data key for accessing aerial subscription information of a UAV UE of UDM may be defined as SUPI as shown in [Table 3] below. The following [Table 2] shows an example of configuration of subscription information of a terminal managed by the UDM, and the subscription information of the terminal may include air subscription information according to an embodiment of the present disclosure.

Table 2 below shows the information for UAS service when the air subscription information is included in the "access and mobility subscription data" subfield among the subscription data types managed by the UDM and in the "session management data" subfield. This is an example of a case where a new subscription data type is defined. In each case, as shown in [Table 3] below, the data key required for data access may be defined differently, and the time at which access is possible may vary depending on whether it is during a registration procedure or during a session establishment procedure.

[Table 2] exemplifies UE subscription data types, and for convenience, one table has been described by dividing it into [Table 2a] to [Table 2i], and [Table 2a] to [Table 2i] are collectively referred to as [Table 2]. It can be.

[Table 2a]

[Table 2b]

[Table 2c]

[Table 2d]

[Table 2e]

[Table 2f]

[Table 2g]

[Table 2h]

[Table 2i]

[Table 3] UE Subscription data types keys

Step 206a: Upon recognizing that a change has occurred in the air subscription information of the UAV UE in step 205, the UDM may notify the NEF that requested the subscription in step 202. UDM may send a Nudm_EventExposure_Notify message. The UDM may provide the NEF with a Nudm_EventExposure_Notify message including SUPI and/or GPSI and changes in aerial subscription information identified in step 205 above. In addition, the Nudm_EventExposure_Notify message may further include time stamp for providing notification of occurrence of a change event of air subscription information.

Step 206b: When the UDM notifies the occurrence of an event in step 206a, when time information (time stamp) is provided together, the NEF may request the UDR to store the event occurrence information and time information. The NEF may transmit a Nudr_DM_Create or Nudr_DM_Update message including the event occurrence information and time information to the UDR.

Step 207: The NEF notified of the occurrence of an aerial subscription change event from the UDM in step 206a may notify the USS that requested the subscription in step 201 of the change event. The NEF may send a Nnef_EventExposure_Notify message to the USS. The NEF may provide the USS with a Nnef_EventExposure_Notify message including GPSI, CAA-Level UAV ID, and the contents of the aerial subscription change in step 206a.

Step 208: The NEF notified of the occurrence of an aerial subscription change event from the UDM in step 206a may determine whether the UUAA result for the UAV UE in step 200 is revocation. For example, when aerial subscription information for the UAV UE is changed from allowed to not allowed, the NEF may determine that the UUAA result for the UAV UE is cancelled. If the NEF determines that the UUAA result for the UAV UE is cancelled, it can check the target NF that performed the UUAA procedure in the UUAA Context of the UAV UE stored in step 200 above. For example, the AMF ID of the corresponding AMF when the UUAA-MM procedure is performed and the SMF ID of the corresponding SMF when the UUAA-SM procedure is performed may be information indicating the target NF. If the NEF does not know the AMF ID where the UUAA-MM procedure was performed, it may receive the corresponding AMF ID by providing the GPSI to the UDM (At this time, a Nudm_UECM_Get Request/Response message may be used).

Step 209a: If the target NF is identified as AMF in step 208, the NEF may notify the corresponding AMF that the UUAA result of the UAV UE has been cancelled. NEF may send an Nnef_Auth_Notification message to AMF. NEF may provide AMF with a Nnef_Auth_Notification message including SUPI and/or GPSI and the cause of revocation. The reason for the cancellation may include aerial subscription is not allowed or aerial subscription removal.

Step 209b: When the target NF is identified as the SMF in step 208, the NEF may notify the corresponding SMF that the UUAA result of the UAV UE has been cancelled. NEF may send Nnef_Auth_Notification message to SMF. The NEF may provide the SMF with a Nnef_Auth_Notification message including the SUPI and/or GPSI, PDU Session IP address, and the cause of revocation. The reason for the cancellation may include aerial subscription is not allowed or aerial subscription removal.

Step 209a or step 209b may be selectively performed depending on whether the target NF is AMF or SMF.

Step 210a: When the NEF makes a subscription request for a reachability event of the UAV UE to the AMF in the UUAA procedure prior to step 200, the NEF may request unsubscribe of the corresponding subscription request. The NEF may have requested subscription to the Mobility Event Exposure in which the value of the Event ID is displayed as a Reachability Filter for the AMF. NEF and AMF may have used Namf_EventExposure_Subscribe Request and Response messages, and NEF may request cancellation of the subscription request for the accessibility event by providing the assigned Subscription Correlation ID to AMF. When requesting the cancellation, the NEF may use a Namf_EventExposure_Unsubscribe Request message. The UE's accessibility event can be defined as UE Reachability in [Table 1] above.

Step 210b: The AMF, which has been requested to cancel the subscription request for the accessibility event of the UAV UE in step 210a, may transmit an acknowledgment confirming that the request has been received to the NEF. In its acknowledgment, AMF may use the Namf_EventExposure_Unsubscribe Response message.

Step 211: When the UAV UE is in an idle state, the target NF (AMF or SMF) determined based on the AMF ID or SMF ID in step 208 may perform a Network Trigger Service Request procedure.

Step 212a: When it is determined that the UUAA-MM procedure has been performed in step 208, the corresponding AMF may notify the UE that the UUAA result has been canceled based on the network policy. The AMF may notify the UE of the cancellation of the UUAA result by performing the UE Configuration Update procedure. In addition, AMF may initiate a procedure for releasing PDU Session (s) for related UAS service (s).

Step 212b: When it is determined that the UUAA-MM procedure has been performed in step 208, the corresponding AMF may initiate a de-registration procedure based on a network policy.

Step 212c: When it is determined that the UUAA-SM procedure has been performed in step 208, the corresponding SMF may initiate a procedure for releasing related PDU Session(s).

Step 213a: When the NEF makes a subscription request for an event to the SMF in the UUAA procedure prior to step 200, the NEF may request unsubscribe of the corresponding subscription request. NEF may have requested subscription to the PDU Session Status event in [Table 1] to the SMF. NEF and SMF may have used the Nsmf_EventExposure_Subscribe Request and Response message when requesting and responding to subscription to the PDU Session Status event, and NEF provides the assigned Subscription Correlation ID to SMF to cancel the subscription request for the PDU Session Status event. can request When requesting unsubscribe, the NEF MAY use the Nsmf_EventExposure_Unsubscribe Request message.

Step 213b: The SMF requested to cancel the subscription request for the event in step 213a may transmit an acknowledgment confirming that the request has been received to the NEF. In response to acknowledgment, the SMF MAY use the Nsmf_EventExposure_Unsubscribe Response message.

3A and 3B illustrate an example of a UUAA revocation procedure for notifying a change in air subscription information using a Subscription Data Management (SDM) service of UDM in a wireless communication system according to an embodiment of the present disclosure.

Step 300: Same as step 200 in FIG. 2A. The NEF may store the UUAA context of the UAV UE when the UUAA procedure, which is a procedure for authenticating and authorizing the UAV UE to communicate with the USS through the wireless communication system, succeeds.

Step 301: The NEF may request a subscription to notify the UDM of a change in air subscription information for the UAV UE in step 300. The NEF may send a Nudm_SDM_Subscribe Request message to the UDM. The NEF may provide the UDM with a Nudm_SDM_Subscribe Request message including SUPI and/or GPSI and information indicating that the subscription request target is air subscription information.

Step 302: Same as step 201 in FIG. 2 . The USS may transmit a subscription request to notify the NEF when a change occurs in air subscription information for the UAV UE in step 300 above.

Step 303: Upon receiving the request of step 302, the NEF may transmit the result of the request to the USS. For example, if the NEF accepts the USS request, the Nnef_EventExposure_Subscription Response message including the identifier (Subscription Correlation ID) for the USS request in step 302 and/or the expiry time according to the policy of the communication service provider is sent. Can be provided to USS.

Step 304: Same as step 205 in FIG. 2A. The UDM that has accepted the subscription request in step 201 can recognize that a change has occurred in the aviation subscription information of the UAV UE based on the subscription information of the terminal as in the example of [Table 2] managed by the UDM.

Step 305: Upon recognizing that a change has occurred in the aerial subscription of the UAV UE in step 304, the UDM may notify the NEF that requested the subscription in step 301. UDM may send a Nudm_SDM_Notification message. The UDM may provide the NEF with a Nudm_SDM_Notification message including SUPI and/or GPSI and changes in aerial subscription information identified in step 304 above.

Step 306: Upon receiving the changed air subscription information from the UDM in the step 305, the NEF may notify the USS that requested the subscription in the step 302. NEF may send a Nnef_EventExposure_Notify message. The NEF may provide the USS with a Nnef_EventExposure_Notify message including GPSI, CAA-Level UAV ID, and the change contents of the aerial subscription information received in step 305 above.

Steps 307 to 312b: Same as steps 208 to 213b in FIGS. 2A and 2B. In other words, the NEF notified of the change in aviation subscription information can determine whether the UUAA result for the UAV UE has been revocationd. inform And the target NF (AMF or SMF) can process the subscription request cancellation for the reachability event of the UAV UE. In addition, the AMF may inform the UAV UE of the cancellation of the UUAA result and perform a deregistration procedure, and the SMF may perform a procedure for releasing the PDU Session (s).

4A and 4B illustrate an example of a UUAA revocation procedure for notifying a change in air subscription information using SDM and Event Exposure services of UDM and AMF in a wireless communication system according to an embodiment of the present disclosure.

Step 400: Same as step 200 in FIG. 2A. The NEF may store the UUAA context of the UAV UE when the UUAA procedure, which is a procedure for authenticating and authorizing the UAV UE to communicate with the USS through the wireless communication system, succeeds.

Step 401: The AMF may request a subscription to notify the UDM of a change in air subscription information for the UAV UE in the step 400. AMF may transmit a Nudm_SDM_Subscribe Request message to UDM. AMF may provide UDM with a Nudm_SDM_Subscribe Request message including SUPI and/or GPSI, PLMN ID, and information indicating that the subscription request target is air subscription information included in "Access and Mobility Subscription data" in [Table 2] above. there is. For example, the air subscription information may correspond to "AerialUESubscriptionInfo" in [Table 2].

Step 402: Same as step 201 in FIG. 2A. The USS may transmit a subscription request to notify the NEF of a change in air subscription information for the UAV UE in step 400.

Step 403: Same as step 202 in FIG. 2A. Upon receiving the request in step 402, the NEF may request a subscription to a change event of air subscription information from the UDM.

Step 404a: When the UDM receiving the request of step 403 wants to provide NEF with an event about a change in air subscription information (ie, "AerialUESubscriptionInfo") included in "Access and Mobility Subscription data" in [Table 2] , A subscription request may be made to the AMF in step 401 for this purpose. UDM may transmit a Namf_EventExposure_Subscribe Request message. The UDM is SUPI and/or GPSI, an event that the UDM can detect according to a change in air subscription information ("AerialUESubscriptionInfo") in "Access and Mobility Subscription data" in [Table 2], and an NEF identifier (end A Namf_EventExposure_Subscribe Request message including point of NEF) may be provided to AMF.

Step 404b: Upon receiving the request of step 404a, the AMF may transmit the result of the request to the UDM. For example, if the AMF accepts the UDM request, a Namf_EventExposure_Subscription Response message including an identifier (Subscription Correlation ID) for the UDM request in step 404a and/or an expiration time (Expiry time) according to the policy of the communication service provider can be provided to the UDM.

Step 405: Upon receiving the result of step 404b, the UDM may transmit the result of the request of the NEF of step 403 to the NEF. For example, if the AMF accepts the UDM request in step 404b and the UDM accepts the NEF request, the identifier (Subscription Correlation ID) for the NEF request in step 403 and/or according to the policy of the communication service provider A Nudm_EventExposure_Subscription Response message including an expiry time may be provided to the NEF.

Step 406: Upon receiving the result of step 405, the NEF may transmit the result of the request of the USS of step 402 to the USS. For example, if the UDM accepts the NEF's request in step 405 and the NEF accepts the USS's request, the identifier (Subscription Correlation ID) for the USS's request in step 402 and/or validity according to the carrier's policy A Nnef_EventExposure_Subscription Response message including expiry time may be provided to the USS.

Step 407: The UDM that has accepted the subscription request in step 401 may recognize that a change has occurred in air subscription information ("AerialUESubscriptionInfo") of "Access and Mobility Subscription data" in [Table 2] of the UAV UE. For example, a case in which the value of "AerialUESubscriptionInfo" is changed from 'authorized' to 'not authorized' or 'allowed' to 'not allowed' may be applicable. The data key for accessing the "Aerial subscription of Access and Mobility Subscription data" information of UDM may include the SUPI and Serving PLMN ID exemplified in Table 3 above.

Step 408: Upon recognizing that a change has occurred in the air subscription information (“AerialUESubscriptionInfo”) of the “Access and Mobility Subscription data” of the UAV UE in step 407, the UDM notifies the AMF that made the subscription request in step 401. can UDM may send a Nudm_SDM_Notification message. UDM may provide SUPI and/or GPSI, PLMN ID, and the changed air subscription information of “Access and Mobility Subscription data” in step 407 to AMF.

Step 409a: Upon receiving the changed air subscription information from UDM in step 408, the AMF uses the NEF indicator provided by the UDM in the subscription request in step 404a to subscribe the changed air subscription to the NEF that made the subscription request in step 403. can provide information. AMF may send a Namf_EventExposure_Notify message to NEF. The AMF may provide changes in air subscription information to the NEF based on SUPI and/or GPSI and the changed air subscription information received in step 408 above.

Step 409b: When the AMF notifies the occurrence of an event in step 409a, when time stamp is also provided, the NEF may request the UDR to store the event occurrence information and time information. The NEF may transmit a Nudr_DM_Create or Nudr_DM_Update message including the event occurrence information and time information to the UDR.

Step 410: The NEF notified of the occurrence of a change event of air subscription information from the AMF in step 409a may notify the USS that requested the subscription in step 402 of the occurrence of the change event. NEF may send a Nnef_EventExposure_Notify message. The NEF may provide the USS with a Nnef_EventExposure_Notify message including the GPSI, CAA-Level UAV ID, and the change of air subscription information of step 409a above.

Steps 411 to 416b: The same as steps 208 to 213b in FIGS. 2A and 2B. In other words, the NEF notified of the change in aviation subscription information can determine whether the UUAA result for the UAV UE has been revocationd. inform And the target NF (AMF or SMF) can process the subscription request cancellation for the reachability event of the UAV UE. In addition, the AMF may inform the UAV UE of the cancellation of the UUAA result and perform a deregistration procedure, and the SMF may perform a procedure for releasing the PDU Session (s).

5A and 5B illustrate an example of a UUAA revocation procedure for notifying a change in air subscription information using SDM and Event Exposure services of UDM and SMF in a wireless communication system according to an embodiment of the present disclosure.

Step 500: Same as step 200 in FIG. 2A. The NEF may store the UUAA context of the UAV UE when the UUAA procedure, which is a procedure for authenticating and authorizing the UAV UE to communicate with the USS through the wireless communication system, succeeds.

Step 501: The SMF may request a subscription to notify the UDM of a change in air subscription information for the UAV UE in the step 500. The SMF may transmit a Nudm_SDM_Subscribe Request message to the UDM. SMF is SUPI and / or GPSI, S-NSSAI (Single-Network Slice Selection Assistance Information), DNN (data network name), PLMN (Public Land Mobile Network) ID, and subscription request target is "Session Information indicating that it is air subscription information included in "Management Subscription data" may be provided to the UDM. The S-NSSAI is an identifier for identifying network slices, and the DNN can be used to select SMF and UPF. For example, the air subscription information may correspond to "Aerial service indication" in [Table 2].

Step 502: Same as step 201 in FIG. 2A. The USS may transmit a subscription request to notify the NEF of a change in air subscription information for the UAV UE in step 500 above.

Step 503: Same as step 202 in FIG. 2A. Upon receiving the request in step 502, the NEF may request a subscription to a change event of air subscription information from the UDM.

Step 504a: Upon receiving the request of step 503, the UDM intends to provide NEF with an event about a change in air subscription information (ie, "Aerial service indication") included in "Session Management Subscription data" in [Table 2]. In this case, a subscription request may be made to the SMF in step 501 for this purpose. UDM may transmit Nsmf_EventExposure_Subscribe Request message. UDM is SUPI and / or GPSI, an event that the UDM can detect according to a change in air subscription information ("Aerial service indication") in "Session Management Subscription data" in [Table 2], and an NEF identifier ( The Nsmf_EventExposure_Subscribe Request message including the end point of NEF) may be provided to the SMF.

Step 504b: The SMF receiving the request of step 504a may transmit the result of the request to the UDM. For example, if the SMF accepts the UDM request, the Nsmf_EventExposure_Subscription Response message including the identifier (Subscription Correlation ID) for the UDM request in step 504a and/or the expiry time according to the policy of the communication service provider can be provided to the UDM.

Step 505: Upon receiving the result of step 504b, the UDM may transmit the result of the request of the NEF of step 503 to the NEF. For example, if the SMF accepts the UDM's request in step 504b and the UDM accepts the NEF's request, the NEF's request identifier (Subscription Correlation ID) in step 503 and/or validity according to the carrier's policy A Nudm_EventExposure_Subscription Response message including an expiry time may be provided to the NEF.

Step 506: Upon receiving the result of step 505, the NEF may transmit the result of the request of the USS of step 502 to the USS. For example, if the UDM accepts the NEF's request in step 505 and the NEF accepts the USS's request, the identifier (Subscription Correlation ID) for the USS request in step 502 and/or validity according to the carrier's policy A Nnef_EventExposure_Subscription Response message including expiry time may be provided to the USS.

Step 507: The UDM that has accepted the subscription request in step 501 may recognize that a change has occurred in air subscription information ("Aerial service indication") of "Session Management Subscription data" in [Table 2] of the UAV UE. For example, a case in which the value of "Aerial service indication" is changed from 'authorized' to 'not authorized' or 'allowed' to 'not allowed' may be applicable. The data key for accessing the "aerial subscription of Session Management Subscription data" information of UDM may include the SUPI, S-NSSAI, DNN, and Serving PLMN IDs exemplified in Table 3 above.

Step 508: Upon recognizing that a change has occurred in the air subscription information ("Aerial service indication") of the "Session Management Subscription data" of the UAV UE in step 507, the UDM notifies the SMF that requested the subscription in step 501. can do. UDM may send a Nudm_SDM_Notification message. The UDM may provide the SUPI and/or GPSI, S-NSSAI, DNN, PLMN ID, and the changed air subscription information of "Session Management Subscription data" in step 507 to the SMF.

Step 509a: The SMF, having received the changed air subscription information from the UDM in step 508, uses the NEF indicator provided by the UDM in the subscription request in step 504a to subscribe the changed air subscription to the NEF that made the subscription request in step 503. can provide information. The SMF may send a Namf_EventExposure_Notify message to the NEF. The SMF may provide the NEF with changes in air subscription information based on SUPI and/or GPSI and the changed air subscription information in step 8 above.

Step 509b: When the SMF notifies the occurrence of an event in step 509a, when time information (time stamp) is also provided, the NEF may request the UDR to store the event occurrence information and time information. The NEF may transmit a Nudr_DM_Create or Nudr_DM_Update message including the event occurrence information and time information to the UDR.

Step 510: The NEF notified of the occurrence of a change event in air subscription information from the SMF in step 509a may notify the USS that requested the subscription in step 502 of the occurrence of the change event. NEF may send a Nnef_EventExposure_Notify message. The NEF may provide the USS with a Nnef_EventExposure_Notify message including the GPSI, CAA-Level UAV ID, and the change of air subscription information of step 509a above.

Steps 511 to 516b: The same as steps 208 to 213b in FIGS. 2A and 2B. In other words, the NEF notified of the change in aviation subscription information can determine whether the UUAA result for the UAV UE has been revocationd. inform And the target NF (AMF or SMF) can process the subscription request cancellation for the reachability event of the UAV UE. In addition, the AMF may inform the UAV UE of the cancellation of the UUAA result and perform a deregistration procedure, and the SMF may perform a procedure for releasing the PDU Session (s).

Meanwhile, in the embodiments of FIGS. 3A, 4A, and 5A, the operation sequence of steps 301, 401, and 501 is not limited to the examples of FIGS. 3A, 4A, and 5A. For example, the operations of steps 301, 401 and 501 are performed after the operations of steps 302, 402 and 502 respectively, or before the operations of steps 300, 400 and 500, or at the same time when the UUAA procedure is performed. /can be run in parallel.

In addition, in the above-described or later embodiments, the information indicating the change of air subscription information may be composed of various types of information indicating, for example, a change from permitted/approved/authorized to not permitted/authorized/unauthorized. can In this regard, the air subscription information (contents of change) transmitted and received by each network entity in the above-described embodiments is identically expressed according to the configuration of a specific field of a message processed by each network entity, but the information configuration is in various forms. can be configured.

7A to 7D illustrate an example of a procedure in which UUAA revocation is performed by a network in a wireless communication system according to an embodiment of the present disclosure. The embodiments of FIGS. 7A to 7D are based on a combination of the embodiments of FIGS. 4A and 4B and the embodiments of FIGS. 5A and 5B, and an operation of updating UUAA results in AMF, SMF, and NEF is added. In addition, the term authentication notification in the embodiments of FIGS. 7A to 7D may be understood as equivalent to the term “event exposure” in the above-described embodiments.

Step 700: Same as step 200 in FIG. 2A. NEF can store the UUAA context of the UAV UE when the UUAA procedure (UUAA-MM procedure or UUAA-SM procedure), which is a procedure for authenticating and authorizing the UAV UE to communicate with the USS through the wireless communication system, succeeds.

Step 701a: The AMF may request a subscription to notify the UDM of a change in air subscription information for the UAV UE in step 700. At this time, the AMF may transmit a Nudm_SDM_Subscribe Request message to the UDM. The AMF sends a Nudm_SDM_Subscribe Request message including at least one of SUPI and/or GPSI, PLMN ID, and information indicating that the subscription request target is the air subscription information included in “Access and Mobility Subscription data” in [Table 2] above to the UDM. can provide For example, the air subscription information may correspond to “” in [Table 2] above.

Step 701b: The SMF may request a subscription to notify the UDM of a change in air subscription information for the UAV UE in step 700. At this time, the SMF may transmit a Nudm_SDM_Subscribe Request message to the UDM. SMF is SUPI and / or GPSI, S-NSSAI (Single-Network Slice Selection Assistance Information), DNN (data network name), PLMN (Public Land Mobile Network) ID, and subscription request targets are “Access” in [Table 2] above. and Mobility Subscription data” or information indicating that it is air subscription information included in “UE context in SMF data” or air subscription information included in “Session Management Subscription data” or airlines managed by UDM A Nudm_SDM_Subscribe Request message including at least one of subscription information information may be provided to the UDM. The S-NSSAI is an identifier for identifying network slices, and the DNN can be used to select SMF and UPF. For example, the air subscription information may correspond to “AerialUESubscriptionInfo” or “Aerial service indication” in [Table 2]. In this embodiment, as at least one of steps 701a and 701b is performed, at least one of steps 706a and 706b to be described below may be performed.

Step 702: Similar to step 201 of FIG. 2A, the USS may transmit a subscription request to notify the NEF of a change in information related to authentication and/or authorization results of the UAV UE. USS may send a Naf_Authentication_Notification Subscribe message. Messages indicated as Naf_Authentication_Notification_xxx in embodiments of the present disclosure may be referred to as Nnef_Authentication_Notification_xxx messages. The USS may provide the NEF with a Generic Public Subscription Identifier (GPSI), a CAA-Level UAV ID, and/or a PDU Session IP address. In addition, the USS may notify the NEF that the reason for the subscription request corresponds to a change in air subscription information of the terminal. The GPSI is an identifier used to process 5G system subscription in another network outside the 5G system, and can be used inside and outside the 5G system. A detailed definition of GPSI may refer to TS 23.501 in the 3GPP NR standard. The CAA-Level UAV ID is a unique identifier assigned by USS or UTM to identify one UAV, and a specific definition of the CAA-Level UAV ID may refer to TS 23.256 in the 3GPP NR standard.

Step 703: The NEF receiving the request of step 702 can check the target NF that performed the UUAA procedure in the UUAA Context of the UAV UE stored in step 700. For example, when the UUAA-MM procedure is performed, the AMF ID of the corresponding AMF and / or the SMF ID of the corresponding SMF when the UUAA-SM procedure is performed may be information indicating the target NF. If the NEF does not know the AMF ID where the UUAA-MM procedure was performed, it may receive the corresponding AMF ID by providing the GPSI to the UDM (At this time, a Nudm_UECM_Get Request/Response message may be used). In this embodiment, at least one of steps 704a and 704b to be described later may be performed according to the target NF identified in the operation of step 703, and at least one of steps 707a and 707b to be described later may be performed.

Step 704a: When it is determined that the UUAA-MM procedure has been performed for the UAV UE in step 703 above, the NEF subscribes the AMF to notify the AMF of a change in information related to the certification and/or licensing result of the UAV UE. request can be sent. NEF may send a Nnef_Authentication_Notification Subscribe message. The NEF may provide the AMF with GPSI and/or SUPI, and other indicators that may specify authentication and/or authorization results of the UAV UE. In addition, when the NEF receives the reason for the subscription request from the USS in step 702, it may provide it to the AMF.

Step 704b: When it is determined that the UUAA-SM procedure has been performed for the UAV UE in step 703 above, the NEF subscribes the SMF to notify the SMF of a change in information related to the authentication and/or authorization result of the UAV UE. request can be sent. NEF may send a Nnef_Authentication_Notification Subscribe message. The NEF may provide the SMF with GPSI and/or SUPI, an indicator that can specify the authentication and/or authorization result of other UAV UEs, and the PDU Session IP address. In addition, when the NEF receives the reason for the subscription request from the USS in step 702, it may provide it to the SMF.

Step 705: The UDM may recognize that a change has occurred in the aviation subscription information of the UAV UE based on the subscription information of the UE managed by the UDM. For example, when the air subscription information is changed, the value of the air subscription information (ie aerial subscription data) is changed from 'authorized' to 'not authorized' or from 'allowed' to 'not allowed' in [Table 2] below. It may be subject to change. An example of a data key for accessing aerial subscription information of a UAV UE of UDM may be defined as SUPI as shown in Table 3 above. [Table 2] shows an example of the configuration of subscription information of a terminal managed by the UDM, and the subscription information of the terminal may include air subscription information according to an embodiment of the present disclosure.

Step 706a: Upon recognizing that a change has occurred in the air subscription information of the UAV UE in step 705, the UDM may notify the AMF that made the subscription request in step 701a. UDM may send a Nudm_SDM_Notification message. UDM may provide SUPI and/or GPSI, PLMN ID, and changed air subscription information to AMF.

Step 706b: Upon recognizing that a change has occurred in the air subscription information of the UAV UE in step 705, the UDM may notify the SMF that made the subscription request in step 701b. UDM may send a Nudm_SDM_Notification message. UDM may provide SUPI and/or GPSI, S-NSSAI, DNN, PLMN ID, and changed air subscription information to AMF. The operations of steps 706a and 706b may be selectively performed or all may be performed depending on whether the operations of steps 701a and 701b are performed.

Step 707a: Upon receiving the changed air subscription information from the UDM in step 706a, the AMF may determine whether the changed air subscription information causes a change in information related to authentication and/or authorization results of the UAV UE. For example, if the UE can no longer use aviation services, the AMF can determine that the authentication and/or licensing results of the UAV UE have become invalid, and the UUAA Revocation procedure must be performed. can judge whether In addition, when the AMF receives changes in subscriber information other than air subscription information (eg, information on network slices allowed to the terminal, information on DNNs allowed to the terminal, etc.) from the UDM, the UAV based on this It may be determined whether information related to authentication and/or authorization results of the UE is changed. When the AMF determines that the information related to the authentication and/or licensing results of the UAV UE needs to be changed, the NEF that requested the subscription in step 704a is notified that the information related to the authentication and/or licensing results of the UAV UE has changed. can do. At this time, the AMF may transmit a Nnef_Authentication_Notification Notify message. The AMF may provide the NEF with a Nnef_Authentication_Notification Notification message including at least one of GPSI and/or SUPI, and other indicators that may specify authentication and/or authorization results of the UAV UE. In addition, when the AMF determines that the authentication and / or authorization result of the UAV UE has become invalid, it can notify the NEF. If the AMF determines that the UUAA revocation procedure must be performed, it may provide the cause of revocation to the NEF. The cause of revocation may include change of air subscription information, deletion of air subscription information, and the like. In the embodiments of the present disclosure, “Cause of revocation” in at least one of the messages including “Cause of revocation” may be understood as a reason for a request related to a reason for cancellation (“Cause of invocation”).

Step 707b: Upon receiving the changed air subscription information from the UDM in step 706b, the SMF may determine whether the changed air subscription information causes a change in information related to authentication and/or authorization results of the UAV UE. For example, if the terminal is no longer able to use aviation services, the SMF can determine that the certification and/or licensing results of the UAV UE have become invalid, and the UUAA Revocation procedure must be performed. can judge whether In addition, when the SMF receives changes in subscriber information other than air subscription information (eg, information on network slices allowed to the terminal, information on DNNs allowed to the terminal, etc.) from the UDM, the UAV based on this It may be determined whether information related to authentication and/or authorization results of the UE is changed. When the SMF determines that the information related to the authentication and/or licensing results of the UAV UE needs to be changed, the NEF that requested the subscription in step 704b is notified that the information related to the authentication and/or licensing results of the UAV UE has changed. can do. At this time, the SMF may transmit a Nnef_Authentication_Notification Notify message. The SMF may provide the NEF with an Nnef_Authentication_Notification Notification message including at least one of an indicator capable of specifying a result of authentication and/or authorization of GPSI and/or SUPI, other UAV UEs, and a PDU Session IP address. In addition, when the SMF determines that the authentication and / or authorization result of the UAV UE is invalid, it may notify the NEF. If the SMF determines that the UUAA Revocation procedure must be performed, it may provide the cause of revocation to the NEF. The cause of revocation may include change of air subscription information, deletion of air subscription information, and the like.

Step 708: The NEF, notified that information related to the authentication and/or licensing result of the UAV UE has been changed in steps 707a and 707b, sends the USS that requested the subscription in step 702 the authentication and/or licensing of the UAV UE. Information related to the result may be notified that a change has occurred. The NEF may determine whether a procedure for canceling UUAA results should be performed due to a change in information related to authentication and/or licensing results of a UAV UE. The NEF may determine that the procedure for canceling the UUAA result should be performed when the reason for the cancellation of the UUAA result is provided by the AMF or SMF. At this time, the NEF may transmit a Naf_Authentication_Notification Notification message to the USS. The NEF may provide the USS with a Naf_Authentication_Notification Notification message including at least one of GPSI, CAA-Level UAV ID, and/or PDU Session IP address. The NEF may inform the USS that the reason for the change in information related to the result of authentication and/or authorization of the UAV UE corresponds to the change in aviation subscription information of the UE. In addition, when the NEF determines that the UUAA result cancellation procedure should be performed, it may provide an indicator (or indication) notifying the USS that the UUAA result cancellation procedure should be performed. The NEF may provide a cause of revocation to the USS for cancellation of UUAA results, and may include change of air subscription information, deletion of air subscription information, and the like.

Step 709: The USS receiving the information from the NEF in step 708 may determine whether a UUAA result cancellation procedure should be performed due to a change in information related to the authentication and/or authorization result of the UAV UE. In the above step 708, when the NEF provides an indicator (or indication) notifying the USS that the cancellation procedure for UUAA results should be performed and/or a reason for performing the cancellation procedure for UUAA results (Cause of revocation), the USS may determine that cancellation procedures for UUAA results should be performed. If the USS determines that cancellation procedures for UUAA results must be carried out, it may request the NEF to cancel the UUAA results. At this time, the USS may transmit a Naf_Authentication_Notification Request including at least one of GPSI, CAA-Level UAV ID, and/or PDU Session IP address to NEF. In addition, the USS may provide a reason for canceling the UUAA result to the NEF through the Naf_Authentication_Notification Request. In the above step 708, when the NEF provides an indicator (or indication) notifying the USS that the cancellation procedure for UUAA results should be performed and/or a reason for performing the cancellation procedure for UUAA results (Cause of revocation), the USS may omit the operation of step 709 for recognizing that the procedure for canceling the UUAA result has been initiated by the network and requesting the NEF to cancel the UUAA result.

Step 710: The NEF can check the target NF that performed the UUAA procedure in the UUAA Context of the UAV UE stored in step 700 above. For example, when the UUAA-MM procedure is performed, the AMF ID of the corresponding AMF and / or the SMF ID of the corresponding SMF when the UUAA-SM procedure is performed may be information indicating the target NF. If the NEF does not know the AMF ID where the UUAA-MM procedure was performed, it may receive the corresponding AMF ID by providing the GPSI to the UDM (At this time, a Nudm_UECM_Get Request/Response message may be used).

Step 711a-1: If it is determined in step 710 that the UUAA-MM procedure has been performed for the UAV UE, the NEF may notify the corresponding AMF that the authentication and/or authorization result of the UAV UE has been revoked. At this time, the NEF may transmit a Nnef_Auth_Notification Request message to the AMF. The NEF may provide the AMF with a Nnef_Auth_Notification Request message including at least one of GPSI and/or SUPI, and other indicators that may specify authentication and/or authorization results of the UAV UE. In addition, the NEF may provide a reason for canceling the authentication and/or authorization result of the UAV UE. The reasons for the cancellation of the certification and/or licensing of the UAV UE include: the UAV is not authorized anymore; aerial subscription is not allowed; Alternatively, aerial subscription removal may be included.

Step 711a-2: Upon receiving the request of step 711a-1, the AMF may update information related to authentication and/or authorization results stored for the corresponding UAV UE. Updating information related to authentication and/or authorization results may include changing the UUAA-MM status value for the corresponding UAV UE to 'PENDING' or 'FAILED'. Also, the update may include deleting the UUAA-MM status field.

Step 711a-3: The AMF may respond to the NEF that it has recognized the fact that the authentication and/or authorization result of the UAV UE has been revoked. At this time, the AMF may transmit a Nnef_Auth_Notification Response message to the NEF.

Step 711b-1: If it is determined in step 710 that the UUAA-SM procedure has been performed for the UAV UE, the NEF may notify the corresponding SMF that the authentication and/or authorization result of the UAV UE has been revoked. At this time, the NEF may transmit a Nnef_Auth_Notification Request message to the SMF. The NEF may provide the SMF with a Nnef_Auth_Notification Request message including at least one of a PDU Session IP address and an indicator capable of specifying GPSI and/or SUPI, other UAV UE authentication and/or authorization results. In addition, the NEF may provide a reason for canceling the authentication and/or authorization result of the UAV UE. The reasons for the cancellation of the certification and/or licensing of the UAV UE include: the UAV is not authorized anymore; aerial subscription is not allowed; Alternatively, aerial subscription removal may be included.

Step 711b-2: Upon receiving the request of step 711b-1, the SMF may update information related to authentication and/or authorization results stored for the corresponding UAV UE. Updating information related to authentication and/or authorization results may include changing the UUAA-SM status value for the corresponding UAV UE to 'PENDING' or 'FAILED'. Also, the update may include deleting the UUAA-SM status field. Also, the update may include deleting a successful UUAA result.

Step 711b-3: The SMF may respond to the NEF that it has recognized the fact that the authentication and/or authorization result of the UAV UE has been revoked. At this time, the SMF may transmit a Nnef_Auth_Notification Response message to the NEF.

Step 712: The NEF receiving the response from the AMF or SMF in step 711a-3 or 711b-3 may modify the stored UUAA Context of the UAV UE. UUAA Context modification may include deletion of UUAA Context.

Step 713: The NEF may inform the USS that the authentication of the UAV UE and/or the cancellation of the authorization result of the UAV UE in the network has been completed. The NEF may respond to the request from the USS in step 709. At this time, the NEF may transmit a Naf_Authentication_Notification Response message to the USS.

Step 714a: When the NEF makes a subscription request for a reachability event of the UAV UE to the AMF in the UUAA procedure prior to step 700, the NEF may request unsubscribe of the corresponding subscription request. The NEF may have requested subscription to the Mobility Event Exposure in which the value of the Event ID is displayed as a Reachability Filter for the AMF. NEF and AMF may have used Namf_EventExposure_Subscribe Request and Response messages, and NEF may request cancellation of the subscription request for the accessibility event by providing the assigned Subscription Correlation ID to AMF. When requesting the cancellation, the NEF may use a Namf_EventExposure_Unsubscribe Request message. The UE's accessibility event can be defined as UE Reachability in [Table 1] above.

Step 710b: The AMF, which has been requested to cancel the subscription request for the accessibility event of the UAV UE in step 710a, may transmit an acknowledgment confirming that the request has been received to the NEF. In its acknowledgment, AMF may use the Namf_EventExposure_Unsubscribe Response message.

Step 715: When the UAV UE is in an idle state, a Network Trigger Service Request procedure specified in 3GPP standard TS 23.502 may be performed.

Step 716a: When it is determined that the UUAA-MM procedure has been performed in step 710, the corresponding AMF may notify the UE that the UUAA result has been canceled based on the network policy. The AMF may notify the UE of the cancellation of the UUAA result by performing the UE Configuration Update (UCU) procedure specified in 3GPP standard TS 23.502. In addition, AMF may initiate a procedure for releasing PDU Session (s) for related UAS service (s).

Step 716b: When it is determined that the UUAA-MM procedure has been performed in step 710, the corresponding AMF may initiate a de-registration procedure specified in 3GPP standard TS 23.502 based on network policy. .

Step 716c: When it is determined that the UUAA-SM procedure has been performed in step 710, the corresponding SMF performs the Network Initiated PDU Session Release procedure specified in TS 23.502 of the 3GPP standard as a procedure for releasing the related PDU Session(s). can start

Step 716a: When the NEF makes a subscription request for an event to the SMF in the UUAA procedure prior to step 700, the NEF may request unsubscribe of the corresponding subscription request. NEF may have requested subscription to the PDU Session Status event in [Table 1] to the SMF. NEF and SMF may have used the Nsmf_EventExposure_Subscribe Request and Response message when requesting and responding to subscription to the PDU Session Status event, and NEF provides the assigned Subscription Correlation ID to SMF to cancel the subscription request for the PDU Session Status event. can request When requesting unsubscribe, the NEF MAY use the Nsmf_EventExposure_Unsubscribe Request message.

Step 716b: The SMF, which has been requested to cancel the subscription request for the event in step 716a, may transmit an acknowledgment of receipt of the request to the NEF. In response to acknowledgment, the SMF MAY use the Nsmf_EventExposure_Unsubscribe Response message.

8A and 8B illustrate an example of a procedure in which UUAA revocation is performed by a USS in a wireless communication system according to an embodiment of the present disclosure. The procedures of FIGS. 8A and 8B are procedures in which the operations of steps 702 to 708 in the embodiments of FIGS. 7A to 7D are not performed. In addition, the term authentication notification in the embodiments of FIGS. 8A and 8B may be understood as equivalent to the term “event exposure” in the above-described embodiments.

Step 800: Same as step 200 in FIG. 2A. NEF can store the UUAA context of the UAV UE when the UUAA procedure (UUAA-MM procedure or UUAA-SM procedure), which is a procedure for authenticating and authorizing the UAV UE to communicate with the USS through the wireless communication system, succeeds.

Step 801a: The AMF may request a subscription to notify the UDM of a change in air subscription information for the UAV UE in step 800. AMF may transmit a Nudm_SDM_Subscribe Request message to UDM. The AMF sends a Nudm_SDM_Subscribe Request message including at least one of SUPI and/or GPSI, PLMN ID, and information indicating that the subscription request target is the air subscription information included in “Access and Mobility Subscription data” in [Table 2] above to the UDM. can provide For example, the air subscription information may correspond to “” in [Table 2] above.

Step 801b: The SMF may request a subscription to notify the UDM of a change in air subscription information for the UAV UE in step 800. At this time, the SMF may transmit a Nudm_SDM_Subscribe Request message to the UDM. SMF is SUPI and / or GPSI, S-NSSAI (Single-Network Slice Selection Assistance Information), DNN (data network name), PLMN (Public Land Mobile Network) ID, and subscription request targets are “Access” in [Table 2] above. and Mobility Subscription data” or information indicating that it is air subscription information included in “UE context in SMF data” or air subscription information included in “Session Management Subscription data” or airlines managed by UDM A Nudm_SDM_Subscribe Request message including at least one of subscription information information may be provided to the UDM. The S-NSSAI is an identifier for identifying network slices, and the DNN can be used to select SMF and UPF. For example, the air subscription information may correspond to “AerialUESubscriptionInfo” or “Aerial service indication” in [Table 2].

Step 802: The USS may determine whether a procedure for canceling a UUAA result should be performed due to a change in information related to a result of authentication and/or authorization of a UAV UE. If the USS determines that cancellation procedures for UUAA results must be carried out, it may request the NEF to cancel the UUAA results. USS to NEF NEF may transmit Naf_Authentication_Notification Request including at least one of GPSI, CAA-Level UAV ID, and/or PDU Session IP address to USS. In addition, the USS may provide the reason for canceling the UUAA result to the NEF through the Naf_Authentication_Notification Request. Step 803: The NEF may check the target NF for which the UUAA procedure was performed in the UUAA Context of the UAV UE stored in step 800. there is. For example, when the UUAA-MM procedure is performed, the AMF ID of the corresponding AMF and / or the SMF ID of the corresponding SMF when the UUAA-SM procedure is performed may be information indicating the target NF. If the NEF does not know the AMF ID where the UUAA-MM procedure was performed, it may receive the corresponding AMF ID by providing the GPSI to the UDM (At this time, a Nudm_UECM_Get Request/Response message may be used). In this embodiment, according to the target NF identified in the operation of step 803, all or selective operations of at least one of AMF and SMF may be performed.

Step 804a-1: If it is determined in step 803 that the UUAA-MM procedure has been performed for the UAV UE, the NEF may inform the corresponding AMF that the authentication and/or authorization result of the UAV UE has been revoked. At this time, the NEF may transmit a Nnef_Auth_Notification Request message to the AMF. The NEF may provide the AMF with a Nnef_Auth_Notification Request message including at least one of GPSI and/or SUPI, and other indicators that may specify authentication and/or authorization results of the UAV UE. In addition, through the Nnef_Auth_Notification Request message, the NEF may provide a reason for canceling the authentication and/or authorization result of the UAV UE. The reasons for the cancellation of the certification and/or licensing of the UAV UE include: the UAV is not authorized anymore; aerial subscription is not allowed; Alternatively, aerial subscription removal may be included.

Step 804a-2: Upon receiving the request of step 804a-1, the AMF may update information related to authentication and/or authorization results stored for the corresponding UAV UE. Updating information related to authentication and/or authorization results may include changing the UUAA-MM status value for the corresponding UAV UE to 'PENDING' or 'FAILED'. Also, the update may include deleting the UUAA-MM status field.

Step 804a-3: The AMF may respond to the NEF that it has recognized the fact that the authentication and/or authorization result of the UAV UE has been revoked. At this time, the AMF may transmit a Nnef_Auth_Notification Response message to the NEF.

Step 804b-1: If it is determined in step 803 that the UUAA-SM procedure has been performed for the UAV UE, the NEF may inform the corresponding SMF that the authentication and/or authorization result of the UAV UE has been revoked. At this time, the NEF may transmit a Nnef_Auth_Notification Request message to the SMF. The NEF may provide the SMF with a Nnef_Auth_Notification Request message including at least one of a PDU Session IP address and an indicator capable of specifying GPSI and/or SUPI, other UAV UE authentication and/or authorization results. In addition, the NEF may provide a reason for canceling the authentication and/or authorization result of the UAV UE. The reasons for the cancellation of the certification and/or licensing of the UAV UE include: the UAV is not authorized anymore; aerial subscription is not allowed; Alternatively, aerial subscription removal may be included.

Step 804b-2: Upon receiving the request of step 804b-1, the SMF may update information related to authentication and/or authorization results stored for the corresponding UAV UE. Updating information related to authentication and/or authorization results may include changing the UUAA-SM status value for the corresponding UAV UE to 'PENDING' or 'FAILED'. Also, the update may include deleting the UUAA-SM status field. Also, the update may include deleting a successful UUAA result.

Step 804b-3: The SMF may respond to the NEF that it has recognized the fact that the authentication and/or authorization result of the UAV UE has been revoked. At this time, the SMF may transmit a Nnef_Auth_Notification Response message to the NEF.

Step 805: The NEF receiving the response from the AMF or SMF in step 804a-3 or 804b-3 may modify the stored UUAA Context of the UAV UE. UUAA Context modification may include deletion of UUAA Context.

Step 806: The NEF may inform the USS that the authentication of the UAV UE and/or the cancellation of the authorization result of the UAV UE in the network has been completed. The NEF may respond to the request of the USS in step 802. At this time, the NEF may transmit a Naf_Authentication_Notification Response message to the USS.

Step 807a: When the NEF makes a subscription request for a reachability event of the UAV UE to the AMF in the UUAA procedure prior to step 800, the NEF may request unsubscribe of the corresponding subscription request. The NEF may have requested subscription to the Mobility Event Exposure in which the value of the Event ID is displayed as a Reachability Filter for the AMF. NEF and AMF may have used Namf_EventExposure_Subscribe Request and Response messages, and NEF may request cancellation of the subscription request for the accessibility event by providing the assigned Subscription Correlation ID to AMF. When requesting the cancellation, the NEF may use a Namf_EventExposure_Unsubscribe Request message. The UE's accessibility event can be defined as UE Reachability in [Table 1] above.

Step 807b: The AMF, which has been requested to cancel the subscription request for the accessibility event of the UAV UE in step 807a, may transmit an acknowledgment confirming that the request has been received to the NEF. In its acknowledgment, AMF may use the Namf_EventExposure_Unsubscribe Response message.

Step 808: When the UAV UE is in an Idle state, a Network Trigger Service Request procedure specified in 3GPP standard TS 23.502 may be performed.

Step 809a: When it is determined that the UUAA-MM procedure has been performed in step 803, the corresponding AMF may notify the UE that the UUAA result has been canceled based on the network policy. The AMF may notify the UE of the cancellation of the UUAA result by performing the UE Configuration Update (UCU) procedure specified in 3GPP standard TS 23.502. In addition, AMF may initiate a procedure for releasing PDU Session (s) for related UAS service (s).

Step 809b: When it is determined that the UUAA-MM procedure has been performed in step 803, the corresponding AMF may initiate a de-registration procedure specified in 3GPP standard TS 23.502 based on network policy. .

Step 809c: If it is determined that the UUAA-SM procedure has been performed in step 803, the SMF performs the Network Initiated PDU Session Release procedure specified in TS 23.502 of the 3GPP standard as a procedure for releasing the related PDU Session(s). can start

Step 810a: When the NEF makes a subscription request for an event to the SMF in the UUAA procedure prior to step 800, the NEF may request unsubscribe of the corresponding subscription request. NEF may have requested subscription to the PDU Session Status event in [Table 1] to the SMF. NEF and SMF may have used the Nsmf_EventExposure_Subscribe Request and Response message when requesting and responding to subscription to the PDU Session Status event, and NEF provides the assigned Subscription Correlation ID to SMF to cancel the subscription request for the PDU Session Status event. can request When requesting unsubscribe, the NEF MAY use the Nsmf_EventExposure_Unsubscribe Request message.

Step 810b: The SMF, which has been requested to cancel the subscription request for the event in step 810a, may transmit an acknowledgment of receipt of the request to the NEF. In response to acknowledgment, the SMF MAY use the Nsmf_EventExposure_Unsubscribe Response message.

Meanwhile, the operation sequence of steps 701a and 701b and steps 801a and 801b in the embodiment of FIGS. 7A and 8A is not limited to the example of FIGS. 7A and 8A. For example, the operations of steps 701a and 701b and steps 801a and 801b are performed after the operations of steps 702 and 802 respectively, or before the operations of steps 700 and 800, or performed simultaneously/parallel when performing the UUAA procedure. It could be.

6 is a diagram illustrating an example of a configuration of a network entity according to an embodiment of the present disclosure.

The network entity of FIG. 6 may be one of network functions (NF) such as UDM, NEF, USS, SMF, and AMF described in the embodiments of FIGS. 1A to 8B.

A network entity according to an embodiment of the present disclosure may include a processor 601 controlling overall operations of the network entity, a transceiver 603 including a transmitter and a receiver, and a memory 605. Of course, it is not limited to the above example, and the network entity may include more or fewer components than the configuration shown in FIG. 6 .

According to an embodiment of the present disclosure, the transceiver 603 may transmit/receive a signal with at least one of other network entities or a terminal including a UAV/UAVC. A signal transmitted/received with at least one of other network entities or terminals may include control information and data.

According to an embodiment of the present disclosure, the processor 601 may generally control the operation of a corresponding network entity to perform an operation according to one or a combination of two or more of the above-described embodiments of FIGS. 1A to 8B there is. Meanwhile, the processor 601, the memory 605, and the transceiver 603 do not necessarily have to be implemented as separate modules, but may be implemented as a single component in the form of a single chip. Also, the processor 601 and the transceiver 603 may be electrically connected. Also, the processor 601 may be an application processor (AP), a communication processor (CP), a circuit, an application-specific circuit, or at least one processor. The transceiver 603 may include a communication interface for transmitting and receiving signals to and from other network entities wired/wireless.

According to an embodiment of the present disclosure, the memory 605 may store data such as a basic program for operation of a corresponding network entity, an application program, and setting information. Also, the memory 605 provides stored data according to a request of the processor 1201 . The memory 605 may include a storage medium such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD, or a combination of storage media. Also, the number of memories 605 may be plural. Also, the processor 601 may perform at least one of the above-described embodiments based on a program for performing an operation according to at least one of the above-described embodiments of the present disclosure stored in the memory 605 .

In addition, the program may be performed through a communication network such as the Internet, an Intranet, a Local Area Network (LAN), a Wide LAN (WLAN), or a Storage Area Network (SAN), or a communication network composed of a combination thereof. It can be stored on an attachable storage device that can be accessed. Such a storage device may be connected to a device performing an embodiment of the present disclosure through an external port. In addition, a separate storage device on a communication network may be connected to a device performing an embodiment of the present disclosure.

It should be noted that the above configuration diagram, exemplary diagram of a control/data signal transmission method, operational procedure exemplary diagram, and configuration diagram are not intended to limit the scope of the present disclosure. That is, all components, network entities, or operational steps described in the embodiments of the present disclosure should not be interpreted as being essential components for the implementation of the disclosure, and the scope in which the essence of the disclosure is not impaired even if only some components are included is included. can be implemented within In addition, each embodiment can be operated in combination with each other as needed. For example, a network entity and a terminal may be operated by combining parts of the methods proposed in the present disclosure.

In the specific embodiments of the present disclosure described above, components included in the disclosure are expressed in singular or plural numbers according to the specific embodiments presented. However, singular or plural expressions are selected appropriately for the presented situation for convenience of explanation, and the present disclosure is not limited to singular or plural components, and even components expressed in plural are composed of the singular number or singular. Even the expressed components may be composed of a plurality.

The embodiments disclosed in the specification and drawings above are only presented as specific examples to easily explain the contents of the present disclosure and aid understanding, and are not intended to limit the scope of the present disclosure. Therefore, the scope of the present disclosure should be construed as including all changes or modifications derived based on the present disclosure in addition to the embodiments disclosed herein.

Claims (10)

A communication method of a first network entity responsible for a network exposure function in a wireless communication system supporting an unmanned aerial vehicle system service,
When an event related to a change in air subscription information of a terminal using the unmanned aerial vehicle system service occurs, receiving a first request message requesting notification of the event from a second network entity performing an authentication procedure of the terminal procedure;
When the air subscription information is changed, receiving a first notification message including changes in the air subscription information from a third network entity in charge of mobility management that has received the notification request for the event. ; and
and transmitting a second notification message including the change in the air subscription information to the second network entity based on the received notification message.
According to claim 1,
The communication method of the first network entity further comprising transmitting a second request message requesting notification of the event to a fourth network entity that manages subscription information of the terminal, based on the first request message.
According to claim 1,
The first notification message further includes secured identification information for accessing the air subscription information.
According to claim 1,
The change content includes information indicating that the air subscription information is changed from permitted to not permitted.
According to claim 1,
A communication method of a first network entity in which the first network entity checks whether a UAV USS authentication and authorization procedure (UUAA) result for authentication of the terminal is revoked based on the received first notification message. .
In a first network entity responsible for a network exposure function in a wireless communication system supporting an unmanned aerial vehicle system service,
transceiver; and
When an event related to a change in air subscription information of a terminal using the unmanned aerial vehicle system service occurs through the transceiver, a first request message requesting notification of the event is transmitted to a second request message for performing an authentication procedure of the terminal. receive from a network entity;
When the change of the air subscription information occurs through the transceiver, a first notification including changes in the air subscription information is received from a third network entity in charge of mobility management that has received the notification request for the event. receive messages,
A first network entity comprising a processor configured to transmit, via the transceiver, a second notification message including the change in the air subscription information to the second network entity based on the received notification message.
According to claim 6,
The processor is further configured to transmit a second request message requesting notification of the event to a fourth network entity that manages subscription information of the terminal, based on the first request message, through the transceiver. network entity.
According to claim 6,
The first notification message further comprises secured identification information for accessing the air subscription information.
According to claim 6,
The change contents include information indicating that the air subscription information is changed from permitted to not permitted.
According to claim 6,
The processor, based on the received first notification message, a first network entity configured to check whether a UAV USS authentication and authorization procedure (UUAA) result for authentication of the terminal is revoked.

Images