Method and apparatus for notifying a user equipment device of an update in an air subscription for an unmanned aerial system service

Abstract

A method performed by a first network entity is provided, the method including determining that there has been a change to the subscription information of a device such that the device is permitted to use an air service. The method further includes sending, to the device, a message comprising an indication that the device's changed subscription information permits the device to use the air service.

Description

Technical Field

[0001] The subject matter disclosed in this specification generally relates to the field of implementing methods and apparatuses for notifying a user equipment device of updates in an aerial subscription for an unmanned aerial system service. This specification defines methods executed by network entities, methods executed by devices, network entities, and devices.

Background Art

[0002] 3GPP (registered trademark) defines an architecture extension for Uncrewed Aerial Vehicles (UAVs) with the following functionality in 3GPP TS23.256 v17.3.0. - Authentication and authorization of a UAV with an Uncrewed Aerial System Service Supplier (USS) during 5GS initial registration. - Authentication and authorization of a UAV with an USS during 5GS mobility registration. - Authentication and authorization of a UAV with an USS during Protocol Data Unit (PDU) session establishment and Packet Data Network (PDN) connection establishment. - Support for USS authorization of command and control (C2) communication. - A reference model for UAV tracking that supports the following three UAV tracking modes. 1. UAV Location Reporting Mode, 2. UAV Presence Monitoring Mode, and 3. Unknown UAV Tracking Mode.

[0003] The 3GPP system supports the geofencing functionality (for in-flight UAVs) and the geocaging functionality (for ground UAVs intended / preparing to fly) within the USS by providing enabling capabilities such as location services, event notifications, etc. to the subscribing USSs.

Summary of the Invention

Problems to be Solved by the Invention

[0004] The geofencing / geocaging mechanism is an air traffic control functionality executed by the USS and is outside the scope of 3GPP. The 3GPP system provides enabling capabilities such as location services, enabling C2 connectivity, and event notifications to subscribing USSs, etc. to support the geofencing / geocaging functionality in the USS. However, the detailed geofencing / geocaging mechanism is not defined within the 3GPP.

Means for Solving the Problems

[0005] Procedures for notifying a user equipment device of an update in air subscription for an unmanned aerial system service are disclosed herein. The procedures may be implemented by the devices disclosed herein.

[0006] In one aspect, a method executed by a first network entity is provided. The method includes determining that there has been a change to the subscription information of a device such that the device is permitted to use an air service. The method further includes transmitting, to the device, a message comprising an indication that the changed subscription information of the device permits the device to use the air service.

[0007] In another aspect, a method executed by a device is provided. The method includes receiving, from a first network entity, a message comprising an indication that the subscription information of the device has been changed to permit the device to use an air service. The method further includes, in response to receiving the message, sending a request for a mobility registration update procedure to the first network entity.

[0008] In another aspect, a first network entity is provided. The first network entity includes a processor configured to determine that there has been a change to the subscription information of a device to permit the device to use an air service. The first network entity further includes a transmitter configured to send, to the device, a message comprising an indication that the changed subscription information of the device permits the device to use an air service.

[0009] In another aspect, a device is provided. The device includes a receiver configured to receive, from a first network entity, a message comprising an indication that the subscription information of the device has been changed to permit the device to use an air service. The device further includes a transmitter configured to send, in response to receiving the message, a request for a mobility registration update procedure to the first network entity.

[0010] To explain the manner in which the advantages and features of the present disclosure can be obtained, the description of the present disclosure is presented by reference to specific devices and methods illustrated in the accompanying drawings. Each of these drawings shows only a particular aspect of the present disclosure and, therefore, should not be regarded as limiting its scope. The drawings may be simplified for clarity and are not necessarily drawn to scale.

[0011] A method and apparatus for notifying a user equipment device of an update in airworthiness for an unmanned aircraft system service will now be described by way of example only with reference to the accompanying drawings.

Brief Description of the Drawings

[0012]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Best Mode for Carrying Out the Invention

[0013] As will be appreciated by those skilled in the art, aspects of the present disclosure may be embodied as a system, apparatus, method, or program product. Accordingly, the configurations described herein may be implemented in entirely hardware form, entirely software form (including firmware, resident software, microcode, etc.), or in a form combining software aspects and hardware aspects.

[0014] For example, the disclosed methods and apparatuses may be implemented as a hardware circuit comprising off-the-shelf semiconductors such as custom very-large-scale integration (VLSI) circuits or gate arrays, logic chips, transistors, or other discrete components. The disclosed methods and apparatuses may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices, etc. As another example, the disclosed methods and apparatuses may include one or more physical or logical blocks of executable code that may be organized, for example, as objects, procedures, or functions.

[0015] Furthermore, the methods and apparatuses may take the form of a program product embodied in one or more computer-readable storage devices storing machine-readable code, computer-readable code, and / or program code, referred to hereinafter as code. The storage device may be tangible, non-transitory, and / or non-transmissive. The storage device may not embody a signal. In certain configurations, the storage device may employ only signals for accessing the code.

[0016] Any combination of one or more computer-readable media may be utilized. The computer-readable media may be computer-readable storage media. The computer-readable storage media may be a storage device that stores code. The storage device may be, for example, but not limited to, electronic, magnetic, optical, electromagnetic, infrared, holographic, micro-mechanical, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing.

[0017] More specific examples (non-exhaustive list) of storage devices would include the following, namely, electrical connections having one or more wires, portable computer diskettes, hard disks, random-access memory ("RAM"), read-only memory ("ROM"), erasable programmable read-only memory ("EPROM") or flash memory, portable compact disc read-only memory ("CD-ROM"), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing. In the context of this specification, a computer-readable storage media may be any tangible media that can contain or store a program for use by or in connection with an instruction execution system, apparatus, or device.

[0018] References throughout this specification to an example of a particular method or apparatus, or similar language, mean that a particular feature, structure, or characteristic described in connection with that example is included in at least one implementation of the methods and apparatuses described herein. Thus, references to features of an example of a particular method or apparatus, or similar language, may, but do not necessarily, refer to the same example, and may mean "one or more, but not all, examples" unless otherwise specified. The terms "including," "comprising," "having," and variations thereof mean "including, but not limited to" unless otherwise specified. An enumerated listing of items does not imply that any or all of the items are mutually exclusive unless otherwise specified. The terms "a," "an," and "the" also refer to "one or more" unless otherwise specified.

[0019] As used herein, a list accompanied by the conjunction “and / or” includes any single item in the list, or any combination of items in the list. For example, the list of A, B, and / or C includes only A, only B, only C, the combination of A and B, the combination of B and C, the combination of A and C, or the combination of A, B, and C. As used herein, a list using the term “one or more of” includes any single item in the list, or any combination of items in the list. For example, one or more of A, B, and C includes only A, only B, only C, the combination of A and B, the combination of B and C, the combination of A and C, or the combination of A, B, and C. As used herein, a list using the term “one of” includes only one unique item among any single items in the list. For example, “one of A, B, and C” includes only A, only B, or only C, and excludes the combination of A, B, and C. As used herein, “a member selected from the group consisting of A, B, and C” includes only one unique item among A, B, or C, and excludes the combination of A, B, and C. As used herein, “a member selected from the group consisting of A, B, and C, and combinations thereof” includes only A, only B, only C, the combination of A and B, the combination of B and C, the combination of A and C, or the combination of A, B, and C.

[0020] Furthermore, the features, structures, or characteristics described herein may be combined in any suitable manner. In the following description, numerous specific details are provided, such as examples of programming, software modules, user selections, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., to provide a thorough understanding of the present disclosure. However, one of ordinary skill in the art will recognize that the disclosed methods and apparatuses may be practiced without one or more of the specific details, or with other methods, components, materials, etc. In other instances, well-known structures, materials, or operations are not illustrated or described in detail to avoid obscuring aspects of the present disclosure.

[0021] Aspects of the disclosed methods and apparatuses are described below with reference to schematic flowcharts and / or schematic block diagrams of methods, apparatuses, systems, and program products. It will be understood that each block of the schematic flowcharts and / or schematic block diagrams, and combinations of blocks in the schematic flowcharts and / or schematic block diagrams, can be implemented by code. This code may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the instructions executed via the processor of the computer or other programmable data processing apparatus create means for implementing the functions / acts specified in the schematic flowcharts and / or schematic block diagrams.

[0022] The code may also be stored in a memory device that can direct a computer, other programmable data processing apparatus, or other device to function in a particular manner, such that the instructions stored in the memory device produce a manufacture including instructions for implementing the functions / acts specified in the schematic flowcharts and / or schematic block diagrams.

[0023] The code may also be loaded onto a computer, other programmable apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus, or other device in order to generate a computer-implemented process, whereby the code executed on the computer or other programmable apparatus provides a process for implementing the functions / acts specified in the schematic flowchart diagrams and / or the schematic block diagrams.

[0024] The schematic flowchart diagrams and / or schematic block diagrams in the drawings illustrate the architecture, functionality, and operation of possible implementations of apparatus, systems, methods, and program products. In this regard, each block in the schematic flowchart diagrams and / or schematic block diagrams may represent a module, segment, or portion of code that includes one or more executable instructions for implementing the specified logical function.

[0025] It should also be noted that in some alternative implementations, the functions recited in the blocks may occur out of the order noted in the figures. For example, two blocks shown in succession may in fact be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. Other steps and methods may be conceived that are equivalent in function, logic, or effect to one or more blocks or portions thereof of the illustrated figures.

[0026] The description of the elements in each drawing may refer to the elements of the preceding drawings. Like numbers refer to like elements throughout the drawings.

[0027] Figure 1 is, ## <title>shows an embodiment of a wireless communication system 100. In one embodiment, the wireless communication system 100 includes a remote unit 102 and a network unit 104. Although a specific number of remote units 102 and network units 104 are shown in FIG. 1, those skilled in the art will recognize that any number of remote units 102 and network units 104 may be included in the wireless communication system 100.< / title>

[0028] In one embodiment, the remote unit 102 may include computing devices such as a desktop computer, a laptop computer, a personal digital assistant (PDA), a tablet computer, a smartphone, a smart television (e.g., a television connected to the Internet), a set-top box, a game console, a security system (including a security camera), a vehicle-mounted computer, a network device (e.g., a router, a switch, a modem), an aerial vehicle, a drone, etc. In some embodiments, the remote unit 102 may include wearable devices such as a smartwatch, a fitness band, an optical head-mounted display, etc. Moreover, the remote unit 102 may be referred to as a subscriber unit, a mobile, a mobile station, a user, a terminal, a mobile terminal, a fixed terminal, a subscriber station, a UE, a user terminal, a device, or by other terms used in the art. The remote unit 102 may communicate directly with one or more of the network units 104 via UL communication signals. In certain embodiments, the remote unit 102 may communicate directly with other remote units 102 via sidelink communication.

[0029] The network unit 104 may be distributed across a geographical area. In certain embodiments, the network unit 104 may also be referred to as an access point, access terminal, base, base station, Node B, eNB, gNB, home Node B, relay node, device, core network, air server, radio access node, AP, NR, network entity, Access and Mobility Management Function (AMF), Unified Data Management Function (UDM), Unified Data Repository (UDR), UDM / UDR, Policy Control Function (PCF), Radio Access Network (RAN), Network Slice Selection Function (NSSF), or by any other term used in the art. The network unit 104 is generally part of a radio access network that includes one or more controllers communicatively coupled to one or more corresponding network units 104. The radio access network is generally communicatively coupled to one or more core networks, which may in turn be coupled to other networks such as the Internet and the public switched telephone network within the network. These and other elements of the radio access and core networks are not shown but are generally well known to those skilled in the art.

[0030] In one implementation, the wireless communication system 100 complies with the New Radio (NR) protocol standardized by 3GPP. The network unit 104 transmits on the downlink (DL) using an Orthogonal Frequency Division Multiplexing (OFDM) modulation scheme, and the remote unit 102 transmits on the uplink (UL) using a Single Carrier Frequency Division Multiple Access (SC-FDMA) scheme or an OFDM scheme. However, more specifically, the wireless communication system 100 may implement some other open or proprietary communication protocols, such as WiMAX, IEEE 802.11 variants, GSM, GPRS, UMTS, LTE variants, CDMA2000, Bluetooth (registered trademark), ZigBee, Sigfox among the protocols. The present disclosure is not limited to any specific wireless communication system architecture or protocol implementation.

[0031] The network unit 104 may serve several remote units 102 within a serving area, e.g., within a cell or a cell sector, via a wireless communication link. The network unit 104 transmits a DL communication signal to serve the remote unit 102 in the time domain, frequency domain, and / or spatial domain.

[0032] A user equipment apparatus (UE) may be registered in the 5GS without being authenticated and authorized for UAS services. When the UE updates its airworthiness for accessing UAS services, the UE may indicate or instruct that the Application Management Function (AMF) or the Session Management Function (SMF) should trigger the USS UAV Authorization / Authentication (UUAA). Since it may not be clear when the change in the UE's airworthiness is implemented in the network, the UE may not be aware of when to indicate to the AMF or SMF to trigger the UUAA. One solution to this problem could be for the UE, configured with the Single Network Slice Selection Assistance Information (S-NSSAI) / Data Network Name (DNN) for UAS services, to perform trial and error by means of initial registration, mobility registration, or PDU session establishment. However, this is not recommended to avoid wasting network resources. Rather, it is desirable for the UE to be informed when the network updates the UE's airworthiness to permit the UE to access UAS services. This application presents a solution to this problem.

[0033] Figure 2 shows a UE 200 that may be used to implement the method described herein. The UE 200 is used to implement one or more of the solutions described herein. The UE 200 conforms to one or more of the UEs described in the embodiments herein. The UE 200 may conform to the remote unit 102. The UE 200 includes a processor 205, a memory 210, an input device 215, an output device 220, and a transceiver 225.

[0034] The input device 215 and the output device 220 may be combined into a single device such as a touch screen. In some implementations, the UE 200 does not include any input device 215 and / or output device 220. The UE 200 may include one or more of the processor 205, the memory 210, and the transceiver 225, and may not include the input device 215 and / or the output device 220.

[0035] As shown in the figure, the transceiver 225 includes at least one transmitter 230 and at least one receiver 235. The transceiver 225 may communicate with one or more cells (i.e., wireless coverage areas) supported by one or more base units. The transceiver 225 may be operable on unlicensed spectrum. Moreover, the transceiver 225 may include a plurality of UE panels that support one or more beams. Additionally, the transceiver 225 may support at least one network interface 240 and / or an application interface 245. The application interface 245 may support one or more APIs. The network interface 240 may support 3GPP reference points such as Uu, N1, PC5, etc. As will be understood by those skilled in the art, other network interfaces 240 may be supported.

[0036] Processor 205 may include any known controller capable of executing computer-readable instructions and / or performing logical operations. For example, processor 205 may be a microcontroller, a microprocessor, a central processing unit (CPU), a graphics processing unit (GPU), an auxiliary processing unit, a field programmable gate array (FPGA), or a similar programmable controller. Processor 205 may execute instructions stored in memory 210 to perform the methods and routines described herein. Processor 205 is communicatively coupled to memory 210, input device 215, output device 220, and transceiver 225.

[0037] Processor 205 may control UE 200 to implement the UE behavior described herein. Processor 205 may include an application processor (also known as the "main processor") that manages application domain and operating system (OS) functions, as well as a baseband processor (also known as the "baseband radio processor") that manages radio functions.

[0038] Memory 210 may be a computer-readable storage medium. Memory 210 may include a volatile computer storage medium. For example, Memory 210 may include RAM, including dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM), and / or static RAM (SRAM). Memory 210 may include a non-volatile computer storage medium. For example, Memory 210 may include a hard disk drive, flash memory, or any other suitable non-volatile computer storage device. Memory 210 may include both a volatile computer storage medium and a non-volatile computer storage medium.

[0039] Memory 210 may store data related to implementing a traffic category field as described herein. Memory 210 may also store program code and related data, such as an operating system or other controller algorithms operating on device 200.

[0040] Input device 215 may include any known computer input device, including a touch panel, buttons, keyboard, stylus, microphone, etc. Input device 215 may be integrated with output device 220, for example, as a touch screen or similar touch-sensitive display. Input device 215 may include a touch screen such that text can be input using a virtual keyboard displayed on the touch screen and / or by handwriting on the touch screen. Input device 215 may include two or more different devices, such as a keyboard and a touch panel.

[0041] The output device 220 may be designed to output visual signals, audible signals, and / or tactile signals. The output device 220 may include an electronically controllable display or display device capable of outputting visual data to the user. For example, the output device 220 may include, without limitation, a liquid crystal display (LCD), a light-emitting diode (LED) display, an organic LED (OLED) display, a projector, or a similar display device capable of outputting images, text, etc. to the user. As another non-limiting example, the output device 220 may include a wearable display such as a smartwatch, smart glasses, a head-up display, etc., which is separate from but communicatively coupled to the rest of the UE200. Further, the output device 220 may be a component such as a smartphone, a mobile information terminal, a television, a table computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, etc.

[0042] The output device 220 may include one or more speakers for generating sound. For example, the output device 220 may generate an acoustic alarm or notification (e.g., a beep or chime). The output device 220 may include one or more tactile devices for generating vibration, movement, or other tactile feedback. All or part of the output device 220 may be integrated with the input device 215. For example, the input device 215 and the output device 220 may form a touch screen or a similar touch-sensitive display. The output device 220 may be located near the input device 215.

[0043] The transceiver 225 communicates with one or more network functions of a mobile communication network via one or more access networks. The transceiver 225 operates under the control of the processor 205 to transmit messages, data, and other signals and, similarly, to receive messages, data, and other signals. For example, the processor 205 may selectively activate the transceiver 225 (or a portion thereof) at a particular time to send and receive messages.

[0044] The transceiver 225 includes at least one transmitter 230 and at least one receiver 235. One or more transmitters 230 may be used to provide an uplink communication signal to a base unit of a wireless communication network. Similarly, one or more receivers 235 may be used to receive a downlink communication signal from the base unit. Although only one transmitter 230 and one receiver 235 are shown, the UE 200 may have any suitable number of transmitters 230 and receivers 235. Further, the transmitters 230 and receivers 235 may be of any suitable type of transmitter and receiver. The transceiver 225 may include a first transmitter / receiver pair used to communicate with a mobile communication network via an authorized radio spectrum and a second transmitter / receiver pair used to communicate with a mobile communication network via an unlicensed radio spectrum.

[0045] The first transmitter / receiver pair may be used to communicate with a mobile communication network via an authorized radio spectrum, and a second transmitter / receiver pair used to communicate with the mobile communication network via an unlicensed radio spectrum may be combined with a single transceiver unit, e.g., a single chip that performs functions for use with both the authorized and unlicensed radio spectrums. The first transmitter / receiver pair and the second transmitter / receiver pair may share one or more hardware components. For example, some transceivers 225, transmitters 230, and receivers 235 may be implemented as physically separate components that access shared hardware resources and / or software resources, such as a network interface 240.

[0046] One or more transmitters 230 and / or one or more receivers 235 may be implemented and / or integrated within a single hardware component, such as a multi-transceiver chip, a system-on-chip, an application-specific integrated circuit (ASIC), or other type of hardware component. One or more transmitters 230 and / or one or more receivers 235 may be implemented and / or integrated within a multi-chip module. Other components, such as a network interface 240 or other hardware components / circuits, may be integrated within a single chip with any number of transmitters 230 and / or receivers 235. The transmitters 230 and receivers 235 may be logically configured as transceivers 225 that use another common control signal, or as modular transmitters 230 and receivers 235 implemented within the same hardware chip or multi-chip module.

[0047] Figure 3 shows a network node 300 that can be used to implement the methods described herein. The network node 300 may be an implementation of an entity within a wireless communication network, for example, within one or more of the wireless communication networks described herein. The network node 300 may be, for example, the UE200 described above, or the network unit 104, or a Network Function (NF) or Application Function (AF), or another entity of one or more of the wireless communication networks of the embodiments described herein. The network node 300 includes a processor 305, a memory 310, an input device 315, an output device 320, and a transceiver 325.

[0048] The input device 315 and the output device 320 may be combined into a single device, such as a touch screen. In some implementations, the network node 300 does not include any input device 315 and / or output device 320. The network node 300 may include one or more of the processor 305, the memory 310, and the transceiver 325, and may not include the input device 315 and / or the output device 320.

[0049] As shown, the transceiver 325 includes at least one transmitter 330 and at least one receiver 335. Here, the transceiver 325 communicates with one or more remote units 200. Additionally, the transceiver 325 may support at least one network interface 340 and / or an application interface 345. The application interface 345 may support one or more APIs. The network interface 340 may support 3GPP reference points such as Uu, N1, N2, and N3. As will be understood by those skilled in the art, other network interfaces 340 may be supported.

[0050] The processor 305 may include any known controller capable of executing computer-readable instructions and / or performing logical operations. For example, the processor 305 may be a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, an FPGA, or a similar programmable controller. The processor 305 may execute instructions stored in the memory 310 to perform the methods and routines described herein. The processor 305 is communicatively coupled to the memory 310, the input device 315, the output device 320, and the transceiver 325.

[0051] The memory 310 may be a computer-readable storage medium. The memory 310 may include a volatile computer storage medium. For example, the memory 310 may include RAM, including dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM), and / or static RAM (SRAM). The memory 310 may include a non-volatile computer storage medium. For example, the memory 310 may include a hard disk drive, a flash memory, or any other suitable non-volatile computer storage device. The memory 310 may include both a volatile computer storage medium and a non-volatile computer storage medium.

[0052] The memory 310 may store data related to establishing a multipath unicast link and / or mobile operation. For example, the memory 310 may store parameters, configurations, resource allocations, policies, etc., as described herein. The memory 310 may also store program code and related data, such as an operating system or other controller algorithms operating on the network node 300.

[0053] The input device 315 may include any known computer input device, including a touch panel, buttons, keyboard, stylus, microphone, etc. The input device 315 may be integrated with the output device 320, for example, as a touch screen or a similar touch-sensitive display. The input device 315 may include a touch screen such that text can be input using a virtual keyboard displayed on the touch screen and / or by handwriting on the touch screen. The input device 315 may include two or more different devices, such as a keyboard and a touch panel.

[0054] The output device 320 may be designed to output visual signals, audible signals, and / or tactile signals. The output device 320 may include an electronically controllable display or display device that can output visual data to the user. For example, the output device 320 may include, without limitation, an LCD display, an LED display, an OLED display, a projector, or a similar display device that can output images, text, etc. to the user. As another non-limiting example, the output device 320 may include a wearable display that is separate from but communicably coupled to the rest of the network node 300, such as a smartwatch, smart glasses, a head-up display, etc. Further, the output device 320 may be a component such as a smartphone, a mobile information terminal, a television, a table computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, etc.

[0055] The output device 320 may include one or more speakers for generating sound. For example, the output device 320 may generate an acoustic alarm or notification (e.g., beep or chime). The output device 320 may include one or more haptic devices for generating vibration, movement, or other haptic feedback. All or part of the output device 320 may be integrated with the input device 315. For example, the input device 315 and the output device 320 may form a touch screen or similar touch-sensitive display. The output device 320 may be located near the input device 315.

[0056] The transceiver 325 includes at least one transmitter 330 and at least one receiver 335. One or more transmitters 330 may be used to communicate with a UE as described herein. Similarly, one or more receivers 335 may be used to communicate with network functions within a PLMN and / or RAN as described herein. Although only one transmitter 330 and one receiver 335 are illustrated, the network node 300 may have any suitable number of transmitters 330 and receivers 335. Further, the transmitters 330 and receivers 335 may be of any suitable type of transmitter and receiver.

[0057] Although not yet defined, a Network Remote (NR) capable of UAC services can support functionality similar to that specified in 3GPP TS 36.300 v17.1.0 for an Evolved Packet System (EPS) capable of UAV services. These functionalities are as follows. - Height reporting when the UE's altitude exceeds a network-configured reference altitude threshold, - Interference detection based on a measurement report triggered when a plurality of configured cells simultaneously meet a trigger criterion, - Signaling of flight path information from the UE to NR - Location information reports, including reports on the horizontal and vertical speeds of the UE. - Open-loop power control extensions, including UE-specific path loss compensation factors and nominal target received power for an extended range.

[0058] The UAV uses 3GPP access (i.e., EPS and 5GS) for 3GPP UAV-related operations.

[0059] Figure 4 shows an architecture 400 in which functions as defined in 3GPP TS23.501 v17.7.1 are implemented by the SMF and the PDN gateway C (PGW-C). Specifically, the SMF and the PGW-C - Trigger the UUAA-SM procedure for a UE that requires UAV authentication and authorization by the USS when requesting user plane resources for UAV operations or when the USS / Uncrewed Aerial System Traffic Management (UTM) triggers re-authentication, - May trigger the authorization of pairing between the UAV and a networked UAVC or a UAVC connected to the UAV via Internet connectivity during the establishment of a PDN connection / PDU session for C2 communication. The SMF and the PGW-C also have access to the HSS and the UDM and can access the UE's aviation subscription information from the HSS via the UDM.

[0060] The SMF + PGW-C also has access to the Home Subscriber Server (HSS) and the Unified Data Management (UDM), thereby enabling access to the UE's aviation subscription information from the HSS via the UDM.

[0061] FIG. 4 is useful to those skilled in the art when providing an overview of architecture 400 for interacting between 5GS and an Evolved Packet Core (EPC) / Evolved Universal Terrestrial Radio Access Network (E-UTRAN).

[0062] The method and apparatus according to the present invention may include the following features.

[0063] Due to the registration of the AMF, for the notification by the UDM of the status of access and mobility subscription data, - The aerial registration status of the UE, - The S-NSSAI for accessing the UAS service, or - To the DNN for accessing the UAS service, Upon any change or update, the AMF is notified thereof by the UDM. The reason for this is that the Nudm_SubscriberDataManagement service API used for this notification supports a data model with an AccessAndMobilitySubscriptionData type that includes the following. - The aerial registration information of the UE as the attribute aerialUeSubInfo, - The list of UEs of the subscribed S-NSSAI as the attribute NSSAI, and - The list of UEs of the subscribed DNN as the attribute subscribedDnnList.

[0064] This support is outlined in 3GPP TS29.503 v17.7.0.

[0065] Due to the lack of aviation subscription, the UE may update without using the UUAA with the UE's aviation subscription information and the S-NSSAI related to the UAS service. The UE may indicate or confirm the UUAA in the following ways. - Executing the registration procedure for mobility registration and including the Civil Aviation Administration (CAA) level UAV ID and related UAS services in the registration message, or - Establishing a PDU session and including the CAA level UAV ID and related parameters for the UAS service in the PDU session establishment message.

[0066] Figure 5, which is the same as Figure 5.2.2.1-1 in 3GPP TS23.256 v17.3.0, shows the known UUAA procedure 500 at the time of initial registration.

[0067] In architecture 510, which includes UE 512, AMF 514, UDM 516, Network Slice Specific Authentication and Authorization Function (NSSAAF) 518, Authentication, Authorization and Accounting (AAA) proxy, or Authentication, Authorization and Accounting (AAA) server 520, UAS network function (UAS-NF) 522, and USS 524, procedure 500 may be executed.

[0068] In step s530, UE 512 sends a registration request to AMF 514.

[0069] In step s540, UE 512, AMF 514, and UDM 516 receive the primary authentication as per Figure 4.2.2.2.2-1 - Step 9 in 3GPP TS23.502 v17.5.0.

[0070] In step s550, the AMF 514 determines whether a UUAA is required for the UAV service.

[0071] In step s560, the AMF 514 sends a registration acceptance message to the UE 512.

[0072] In step s570, the UE 512 sends a registration completion message to the AMF 514.

[0073] In step s580, according to 3GPP TS23.502 v17.5.0, Figure 4.2.2.2.2-1 - Step 25, the NSSAA procedure is executed.

[0074] In step s590, the actual UUAA is executed, and such UUAA may fail due to the absence of a permitted S-NSSAI and DNN for the UAS service in the list of subscribed S-NSSAI and DNN and the absence of an aviation subscription.

[0075] According to 3GPP TS23.256 v17.3.0, if the procedure for UUAA fails due to the local network policy, the AMF 514 may register the UE 512, but the UE 512 shall not be permitted to access any aviation service. Specifically, if the UUAA fails based on the local network policy, as described in step 7 of Section 5.2.2.2, the AMF 514 may decide to deregister the UE 512 using an appropriate cause value in the deregistration request message, or to hold the registered UE in the UE context together with the failed UUAA result, thereby ensuring that the UE 512 is not permitted to access any aviation service based on the DNN / S-NSSAI value, as clarified by 3GPP TS23.256 v17.3.0.

[0076] In such a case, since AMF 514 does not permit the use of the S-NSSAI and DNN by UE 512, UE 512 is not permitted to establish a PDU session for the UAS service. Therefore, it may be necessary to change the UE's airworthiness so that UE 512 can re-trigger the UUAA procedure s580. Additionally, the S-NSSAI needs to be an allowed S-NSSAI in the Public Land Mobile Network (PLMN) where UE 512 is located.

[0077] For example, due to the lack of airworthiness, there may be a case where UE 512 is registered in the 5GS network without being authenticated and authorized for the UAS service. When UE 512 receives information indicating that the network knows about the updated airworthiness of the UE when the UE's subscription information is updated, UE 512 may start the UUAA procedure s580.

[0078] UE 512 without a valid airworthiness may still be registered in 5GS for other services. Figure 6 shows a procedure 600 executable by an architecture 510 in which AMF 514 provides information to UE 512 indicating that UE 512 is permitted to trigger UUAA or cause AMF 514 or SMF 602 to trigger UUAA due to a change in the airworthiness status.

[0079] In this embodiment, the architecture 510 further includes a UDM 604.

[0080] As a prerequisite for procedure 600, in step s610, UE 512 is registered to 5GS in accordance with section 4.2.2.2.2 of 3GPP TS 23.502 v17.5.0. Since UE 512 has no air subscription for UAS services, UE 512 may be registered only for default services, for example, may have default IP access using a default S-NSSAI and a default DNN.

[0081] In step s615, an update in the UE's air subscription information is made at UDM 604, thereby permitting UE 512 to access UAS services. For example, this update may be made as an operator incentive, or the user may have made a payment for one or more of the UAS services to be activated.

[0082] In step s620, since AMF 514 participates in the subscription data management for UE 512 and the UE's air subscription information and the list of UEs with subscribed DNN / S-NSSAI are part of the UE's subscription data management, AMF 514 is notified of a change in the UE's subscription information data. AMF 514 may return an acknowledgement message following the notification in step s625.

[0083] In step s630, AMF 514 updates the access and mobility subscription data of UE 512, and the data comprises attributes related to the UE's air subscription information. Thus, AMF 514 updates the UE's air subscription information so that UE 512 is permitted to use one or more of the UAS services later.

[0084] Due to the addition of aviation access and the update of the new list of subscribed S-NSSAIs, AMF514 then triggers a configuration update procedure to send a newly configured NSSAI with the updated subscribed S-NSSAI (and, if applicable, the mapped HPLMN S-NSSAI value) to UE512. Additionally, AMF514 may send a new indication to UE512 that aviation services / aviation access are enabled, as per Section 5.1 of 3GPP TS23.502 v17.5.0. Specifically, AMF514 starts the UE configuration update procedure by constructing a configuration update command message as defined in 3GPP TS24.501 v17.7.1, which includes a configured NSSAI IE containing the S-NSSAI and / or an indication that aviation services are enabled for UE512. AMF514 may include a configuration update indication information element (IE) set to the value "Registration Required".

[0085] Therefore, in step s635, AMF514 sends a configuration update command message towards UE512 and may start timer T3555 if AMF514 sets the acknowledgment response bit in the configuration update indication IE to the value "Acknowledgment Response Required" to request an acknowledgment response from UE512.

[0086] If an acknowledgment response is required by AMF514, UE512 sends a configuration update complete message to AMF514 in step s640, as defined in 3GPP TS24.501 v17.7.1. AMF514 stops timer T3555 upon receiving the configuration update complete message. T3555 is a timer used in the UE configuration update procedure when the AMF requests an acknowledgment response. During its duration, the AMF expects an acknowledgment response, and if not, the AMF resends the configuration update command message. T3555 for 5G is 6 seconds.

[0087] Procedure 600 further includes a mobility registration procedure 650 updated by the UE using the S-NSSAI within the configured NSSAI.

[0088] Since the UE 512 receives an indication that the subscription is updated or that the air service is enabled as described herein, the UE 512 may decide to initiate a new registration procedure 650 and may include the CAA level UAV ID in the registration request message. Since the UE 512 understands that the S-NSSAI is for UAS services, in step s655, the UE 512 sends a registration request message with the configured NSSAI having the S-NSSAI to the AMF 514 and may provide the CAA level UAV ID to instruct or indicate to the AMF 514 to trigger the UUAA-MM. The UE 512 may also provide the USS address to the AMF 514.

[0089] When providing the CAA level UAV ID to instruct or indicate the AMF 514 to trigger the UUAA, in step s660, the AMF 514 - checks whether the UE 512 has valid air subscription information, - whether the local policy permits the execution of the UUAA during registration, and - whether there is no successful UUAA result from the previous UUAA-MM procedure to determine whether the UUAA is required for the UE 512.

[0090] When AMF514 confirms that UUAA-MM is required, AMF514 provides the hold UUAA indication to UE512 in step s665 by including a service level AA hold indication IE in the registration acceptance message as described in 3GPP TS24.501 v17.7.1. The hold indication is interpreted by UE512 as requiring UE512 to wait for the completion of the UUAA procedure without attempting to register for the UAS service or establish user plane connectivity to USS524 or UAV-C. AMF514 stores the UUAA hold notification in the UE context.

[0091] In step s670 of the mobility registration procedure 650, UE512 completes the transaction by sending a registration completion towards AMF514.

[0092] In the first example indicated by reference number 680A, when AMF514 knows that UE512 supports network specific-slice authentication and authorization (NSSAA) as shown in the 5GMM IE (as described in 3GPP TS24.501 v17.7.1), AMF514 may initiate the NSSAA procedure for the S-NSSAI for accessing the UAS service as described in section 4.2.9.2 of 3GPP TS23.502 v17.5.0 based on the change of the aviation subscription information. Specifically, in step s685A, AMF514 sends a network slice specific authentication command message comprising the following. - An EAP message IE set in an extensible authentication protocol (EAP) request message, and - An S-NSSAI IE including the S-NSSAI for the UAS service.

[0093] When the AMF 514 sends a network slice specific authentication command message in step s685A, it starts T3575 as described in 3GPP TS24.501 v17.7.1. T3575 is a timer used in the network slice specific authorization and authentication procedures. During its duration, the AMF expects an acknowledgment response, and if not, the AMF re - sends the network slice specific authentication command message. T3575 for 5G is 15 seconds. Specifically, the AMF 514 receives a network slice specific authentication completion message from the UE 512 in step s690A.

[0094] The network slice specific authentication completion message comprises the following. - An EAP message IE set in the EAP response message, and - An S - NSSAI information element including the S - NSSAI for the UAS service.

[0095] When the AMF 514 receives a network slice specific authentication completion message in step s690A, it stops the timer T3575 and reports the output to the NSSAA 518 or the AAA - P / AAA - S 520.

[0096] The transmission of the network slice specific authentication command message (in step s685A) and the network slice specific authentication completion message (in step s690A) may be executed multiple times.

[0097] When the authentication procedure is successful, the network sends a network slice specific authentication result message to the UE 512 in step s695A.

[0098] In another example, indicated by reference number 680B, when the AMF 514 knows that the UE 512 does not support NSSAA because the UE 512 does not indicate such support in the 5GMM IE as described in 3GPP TS 24.501 v17.7.1. The UE context information may include the S-NSSAI, one or more HPLMN S-NSSAIs corresponding to the permitted NSSAI.

[0099] If the S-NSSAI for the UAS service is part of the permitted NSSAI and the AMF 514 triggers the UUAA-MM, then the UUAA-MM is executed in step s700 as described in section 5.2.2.2 of 3GPP TS 23.256 v17.3.0. When the UUAA-MM procedure for the UAV is successfully completed, the AMF 514 stores the successful UUAA result, indicates that the UUAA is no longer pending, and updates the UE context to further indicate the authorized CAA level UAV ID if provided by the USS 524. According to step 6 in Figure 5.2.2.1-1 of 3GPP TS 23.256 v17.3.0, the AMF 514 triggers the UE configuration update procedure as described in section 4.2.4.2 of 3GPP TS 23.502 v17.5.0 to deliver the UUAA result and related information to the USS 524.

[0100] If the UE 512 does not indicate UUAA-MM in the registration request message at step s655, or if the AMF 514 is not permitted to trigger UUAA-MM according to the local policy, and the S-NSSAI for the UAS service is part of the permitted NSSAI, the UE 512 may first instruct or indicate to the SMF 602 to trigger UUAA-SM by the UE 512 in step s705 of establishing the PDU session. In the PDU session establishment request, the UE 512 may provide the UAV's CAA level UAV ID and provide other necessary information for the UAS service, such as the USS address for instructing or indicating the SMF 602 to trigger UUAA-SM. The AMF 514 checks the airworthiness and S-NSSAI / DNN for the UAS service and forwards the message towards the SMF 602.

[0101] In step s710, the SMF 602 starts the UUAA-SM procedure. Specifically, the SMF 602 uses the DNN / S-NSSAI and / or UE-provided identification information, such as the USS address, to identify the UAS NF 522 / NEF based on the local configuration or by the NF discovery procedure. Depending on the authentication method used by the USS 524, multiple round-trip messages may be required. The steps outlined in section 5.2.3.2 of 3GPP TS23.256 v17.3.0 describe the UUAA-SM procedure by which the UUAA result and the authorized CAA level UAV ID are sent by the SMF 602 to the UE 512.

[0102] Therefore, a procedure 600 for USS UAV authorization / authentication is provided, including the mobility registration procedure (UUAA-MM) and the PDU session establishment procedure (UUAA-SM).

[0103] In one embodiment of procedure 600, there is a change in the subscription. In this embodiment, the AMF 514 may include an NSSAI IE as defined in 3GPP TS 24.501 v17.7.1, where the value is set to "network slicing subscription is changed" in the configuration update command message (sent in step s635). This may require, for example, that the configuration update indication IE, whose value is automatically set to "registration is required" as per 3GPP TS 24.501 v17.7.1, be included in the configuration update command message.

[0104] Due to the configured new NSSAI and the UE 512's knowledge of this updated NSSAI, the UE 512 may initiate a mobility registration update procedure (as per s700) and may include the S-NSSAI related to the UAS service in the required NSSAI IE in the registration request message (sent in s655). The UE 512 may also instruct the AMF 514 by including a service level AA container IE containing the service level AA device ID set to the value of the UE 512's CAA level UAV ID, such that the AMF 514 triggers the UUAA-MM when permitted by the local policy.

[0105] In another embodiment of procedure 600, the AMF 514 may include a service level AA container IE in the configuration update command message to indicate that the aviation subscription is enabled. This indication may be a new IE and may be a type 1 IE as specified in 3GPP TS 24.007 v17.3.0. The service level AA container IE is defined in 3GPP TS 24.501 v17.7.1.

[0106] Figure 7 shows the service level AA container IE 700. The service level AA container IE 700 comprises a service level AA container information element identifier IEI 702, a service level AA container content length 704, and a service level AA container content 706.

[0107] Figure 8 shows the service level AA container content 706 having the number of octets n.

[0108] The service level AA container IE defined in 3GPP TS24.501 v17.7.1 and referenced for the above-mentioned procedure 600 has a content with a length of 5 octets.

[0109] The new AMF indication for activated subscription may be called the service level AA subscription indication IE, which is an IE of type 1 and is defined as shown in Figure 9.

[0110] Figure 9 shows the service level AA subscription indication 900.

[0111] When the UE512 receives the service level AA container IE in which the service level AA subscription indication SLASI is set to the value "service level AA subscription is activated", the UE512 may start the mobility registration update procedure and may include the S-NSSAI related to the UAS service in the requested NSSAI IE in the registration request message. The UE512 may also, when permitted by the local policy (in step s700), instruct the AMF514 by including the service level AA container IE700 having the service level AA device ID set to the value of the CAA level UAV ID of the UE512 so that the AMF514 triggers the UUAA-MM procedure.

[0112] Figure 10 is a process flowchart showing the steps of method 1000 to be executed by the first network entity, for example, the AMF514 of the above-described embodiment.

[0113] Method 1000 includes, in step s1000, determining that there has been a change to the subscription information of a device (e.g., UE512) such that the device is permitted to use the air service.

[0114] Method 1000 includes, at step s1010, sending to the device a message comprising an indication that the device's changed subscription information permits the device to use an air service.

[0115] The indication may comprise a new S-NSSAI for the air service and / or a service level AA subscription indication.

[0116] The first network entity may be an AMF (e.g., by the AMF 514), and the device may be a UE (e.g., by the UE 512).

[0117] The S-NSSAI may be part of a configured NSSAI.

[0118] The air service may be a UAS service (e.g., according to the above embodiments).

[0119] The subscription information may comprise air subscription information.

[0120] The method may further comprise subscribing to the device's subscription information.

[0121] The first network entity may subscribe to the subscription information with a second network entity, e.g., the UDM 604 of the above embodiments.

[0122] The second network entity may be a UDM (e.g., UDM 604).

[0123] The first network entity may subscribe to the subscription information at the time of registration of the device to 5GS via the first network entity.

[0124] The subscription information may be access and mobility subscription data or may include access and mobility subscription data.

[0125] Accordingly, a method 1000 is provided for notifying a device of an update in airworthiness for an unmanned aerial system service.

[0126] FIG. 11 is a process flow chart showing steps of a further method 1100, executed by a device, e.g., the UE 512 of the above embodiment.

[0127] The further method 1100 includes, at step s1100, receiving, from a first network entity (e.g., the AMF 514), a message comprising an indication that the subscription information of the device has been changed to permit the device to use an air service.

[0128] The further method 1100 further includes, at step s1110, in response to receiving the message, sending a request for a mobility registration update procedure to the first network entity.

[0129] The request may comprise an indicator for the first network entity to trigger a first authorization and authentication procedure for the air service.

[0130] The request may comprise a requested NSSAI comprising an S-NSSAI for subscription to the air service.

[0131] The first authorization and authentication procedure for the air service may be UUAA-MM (e.g., according to the above embodiment).

[0132] The device may request PDU session establishment by indicating to a third network entity (e.g., the SMF 602) to trigger a second authorization and authentication procedure for the air service.

[0133] Accordingly, a further method 1100 is provided for the device to request, i.e., initiate, a mobility registration update procedure.

[0134] In one embodiment, a first network entity, such as the AMF 514 according to the above embodiment, is provided that includes a processor configured to determine that there has been a change to the subscription information of a device (e.g., UE 512) such that the device is permitted to use an aviation service.

[0135] In this embodiment, the first network entity further includes a transmitter configured to transmit to the device a message comprising an indication that the device's changed subscription information permits the device to use an aviation service.

[0136] In another embodiment, a device, such as the UE 512 according to the above embodiment, is provided that includes a receiver configured to receive from a first network entity (e.g., AMF 514) a message comprising an indication that the device's subscription information has been changed to permit the device to use an aviation service.

[0137] In this embodiment, the device further includes a transmitter configured to transmit to the first network entity, in response to receiving the message, a request for a mobility registration update procedure.

[0138] According to the above embodiment, when the AMF becomes aware, from the subscription data management (e.g., its modification) for the UE in the UDM, that there is an update in the UE's aviation subscription information that permits the UE to use the UAS service, the AMF transmits to the UE (by means of a configuration update command message) a configured NSSAI IE with a new indication that the S-NSSAI for the UAS service and / or aviation service / aviation subscription is enabled for the UE. Advantageously, the methods and apparatuses described herein do not require the UE to perform trial and error to subscribe to the UAS service, but rather serve to enable the UE to be actively informed of a network update that will enable the UE to use the UAS service. Thus, it helps to conserve, i.e., not waste, network resources in ineffective periodic authorization attempts.

[0139] According to the above embodiment, when the UE receives a configuration update command message comprising a configured NSSAI IE including a new indication that the S-NSSAI for the UAS service and / or aviation service / aviation subscription is enabled for the UE, the UE can recognize the S-NSSAI associated with the UAS service. Thus, the UE may indicate the CAA level UAV ID to the AMF by performing a mobility registration (e.g., according to Section 5.2.2.2 in 3GPP TS23.256 v17.3.0) based on the indication that the aviation service / aviation subscription is enabled for the UE. If the UE so chooses, or if the network policy does not permit UUAA-MM, the UE may command the SMF to trigger UUAA-SM by performing a mobility registration update and, after obtaining confirmation that the S-NSSAI associated with the UAS service is part of the permitted NSSAI, establishing a PDU session through the UE according to Section 5.2.3.2 in 3GPP TS23.256 v17.3.0.

[0140] Note that the above methods and apparatuses are illustrative rather than limiting the present invention, and those skilled in the art can design many alternative configurations without departing from the scope of the appended claims. The term "comprising" does not exclude the presence of elements or steps other than those listed in the claims, "a" or "an" does not exclude a plurality, and a single processor or other unit may perform the functions of several units described in the claims. Any reference signs in the claims shall not be construed as limiting their scope.

[0141] Furthermore, although examples are given in the context of specific communication standards, these examples are not intended to limit the communication standards to which the disclosed methods and apparatuses can be applied. For example, although specific examples are given in the context of a given 3GPP, the principles disclosed herein can also be applied to other wireless communication systems and, in fact, any communication system that uses routing rules.

[0142] The method may also be embodied in a set of instructions stored on a computer-readable medium that, when loaded into a computer processor, a digital signal processor (DSP), or the like, causes the processor to execute the method described above.

[0143] The methods and apparatuses described may be practiced in other specific forms. The methods and apparatuses described should be regarded as illustrative rather than restrictive in all respects. Accordingly, the scope of the present invention is indicated by the appended claims rather than by the above description. All changes that fall within the meaning and scope of the equivalents of the claims should be embraced within their scope.

Description of Reference Signs

[0144] 100 Wireless communication system 102 Remote unit 104 Network unit 200 User Equipment (UE) 205 Processor 210 Memory 215 Input Device 220 Output Device 225 Transceiver 230 Transmitter 235 Receiver 240 Network Interface 245 Application Interface 300 Network Node 305 Processor 310 Memory 315 Input Device 320 Output Device 325 Transceiver 330 Transmitter 335 Receiver 340 Network Interface 345 Application Interface 400 Architecture 512 UE 514 Application Management Function (AMF) 516 Unified Data Management Function (UDM) 518 Network Slice Specific Authentication and Authorization Function (NSSAAF) 520 Authentication, Authorization, and Accounting (AAA) Proxy, Authentication, Authorization, and Accounting (AAA) Server 522 UAS Network Function (UAS-NF) 524 Unmanned Aerial System Service Supplier (USS) 602 Session Management Function (SMF) 604 Unified Data Management Function (UDM) 700 Service Level AA Container IE 702 Service Level AA Container Information Element Identifier IEI 704 Service Level AA Container Content Length 706 Service Level AA Container Content 900 Service Level AA Subscription Indication

Claims

1. A method performed by a first network entity, comprising: determining that there has been a change to the subscription information of the device such that the device is permitted to use an air service; sending, to the device, a message comprising an indication that the changed subscription information of the device permits the device to use the air service. The method according to claim 1, further comprising:

2. The method according to claim 1, wherein the indication comprises a new S-NSSAI for the air service and / or a service level AA subscription indication.

3. The method according to claim 1 or 2, wherein the first network entity is an AMF and the device is a UE.

4. The method according to any one of claims 1 to 3, wherein the S-NSSAI is part of a configured NSSAI.

5. The method according to any one of claims 1 to 4, wherein the air service is a UAS service.

6. The method according to any one of claims 1 to 5, wherein the subscription information comprises air subscription information.

7. The method according to any one of claims 1 to 6, further comprising subscribing to the subscription information of the device. The method according to any one of claims 1 to 6, further comprising subscribing to the subscription information of the device.

8. The method according to claim 6, wherein the first network entity subscribes to the subscription information with a second network entity.

9. The method according to claim 8, wherein the second network entity is a UDM.

10. The method according to any one of claims 7 to 9, wherein the first network entity subscribes to the subscription information at the time of registration of the device to 5GS via the first network entity.

11. The method according to any one of claims 1 to 10, wherein the subscription information is access and mobility subscription data.

12. A method performed by a device, comprising: receiving, from a first network entity, a message comprising an indication that there has been a change to the subscription information of the device such that the device is permitted to use an air service; in response to receiving the message, sending a request for a mobility registration update procedure to the first network entity. The method according to claim 12, further comprising:

13. The method according to claim 12, wherein the request comprises an indicator for the first network entity to trigger a first authorization and authentication procedure for the air service.

14. The method according to claim 12 or 13, wherein the request comprises a required NSSAI comprising an S-NSSAI for subscription to the air service.

15. The method according to claim 13 or 14, wherein the first authorization and authentication procedure for the air service is UUAA-MM.

16. The method according to any one of claims 12 to 15, wherein the device requests PDU session establishment by indicating to a third network entity to trigger a second authorization and authentication procedure for the air service.

17. A processor configured to determine that there has been a change to the subscription information of the device so that the device is permitted to use the air service; and A transmitter configured to send to the device a message comprising an indication that the changed subscription information of the device permits the device to use the air service A first network entity comprising.

18. A receiver configured to receive from a first network entity a message comprising an indication that there has been a change to the subscription information of the device so that the device is permitted to use the air service; and A transmitter configured to send to the first network entity a request for a mobility registration update procedure in response to receipt of the message A device comprising.

Images