Ground-based detection and avoidance of aerial objects for locations

Abstract

The first communication device may determine (410) that the second communication device is within the area. The first communication device may determine (420) an identifier of the second communication device. The first communication device may send (440) a message to the second communication device using the identifier.

Description

Technical Field

[0001] The present disclosure relates to wireless communication systems and, more particularly, to ground-based detection and avoidance of airborne objects for a location, such as an event venue. Background Art

[0002] Figure 1 An example of a new radio (“NR”) network (e.g., a 5th generation (“5G”) network) is shown, which includes a 5G core (“5GC”) network 130, network nodes 120a-b (e.g., 5G base stations (“gNBs”)), and multiple communication devices 110 (also referred to as user equipment (“UE”)).

[0003] The management and control of drones may be referred to as Unmanned Air Traffic Management ("UTM"). Government regulators (e.g., the Federal Aviation Administration ("FAA")) along with industry parties have investigated the regulation of drones in the international Global UTM Association ("GUTMA") organization and the joint activities of GUTMA and the Global System for Mobile Communications ("ACJA") organization.

[0004] Commercial applications and opportunities for Unmanned Aircraft Systems (“UAS”) operations, particularly at low latitudes, spanning a multitude of domains from inspection, to survey, to surveillance, to package delivery, provide highly compelling incentives and business cases for an operating structure that permits these operations within a regulatory, operational, and technical environment that includes the National Airspace System (“NAS”). UAS operational demand and anticipated benefits are driving a public and private stakeholder partnership led by the FAA and the National Aeronautics and Space Administration (“NASA”) to develop and continually refine a concept of operations (“ConOps”) for UTM. This vision for UAS operations has sparked a shared desire to enable innovative solutions through public-private partnerships and the use of technology to support emerging opportunities, while ensuring that safety protections, security measures, efficiency, and fairness across the NAS are maintained to the highest standards. Summary of the invention

[0005] According to some embodiments, a method of operating a first communication device is provided. The method includes determining that a second communication device is within a region. The method further includes determining an identifier of the second communication device. The method further includes sending a message to the second communication device using the identifier.

[0006] According to other embodiments, a method of operating a second communication device is provided. The method includes receiving a first message from a first communication device associated with a region. The method further includes sending a portion of the first message to a third communication device. The method further includes receiving a second message from the third communication device in response to sending the portion of the first message. The method further includes modifying the operation of the second communication device based on the second message.

[0007] According to other embodiments, a method of operating a third communication device is provided. The method may include receiving a first message from a first communication device associated with a region. The method may also include, in response to receiving the first message, determining instructions for operating a second communication device in the region based on the first message. The method further includes sending a second message to the second communication device, the second message including the instructions.

[0008] According to other embodiments, a communication device, a network node, a system, a host, a computer program or a computer program product is provided to perform one of the above methods.

[0009] According to other embodiments, a ground-based system may provide information associated with a particular area to an unmanned aircraft system ("UAS"), including an unmanned aerial vehicle ("UAV"), that is in the particular area. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] The accompanying drawings are included to provide a further understanding of the present disclosure and are incorporated in and constitute a part of this application, and illustrate certain non-limiting embodiments of the inventive concept. In the drawings:

[0011] Figure 1 is a schematic diagram illustrating an example of a fifth generation ("5G") network;

[0012] Figure 2 is a block diagram illustrating an example of a 5G network for ground-based detect and avoid ("DAA") in accordance with some embodiments;

[0013] Figure 3 is a signal flow diagram illustrating an example of a ground-based DAA according to some embodiments;

[0014] Figure 4 is a flow chart illustrating an example of operations performed by a first communication device (e.g., an Area Airspace Manager (“AAM”)) according to some embodiments;

[0015] Figure 5 is a flow chart illustrating an example of operations performed by a second communication device (e.g., an unmanned aerial vehicle ("UAV")) according to some embodiments;

[0016] Figure 6 is a flow chart illustrating an example of operations performed by a third communication device (e.g., a UAV controller ("UAV-C")) according to some embodiments;

[0017] Figure 7 is a block diagram illustrating a communication system according to some embodiments;

[0018] Figure 8 is a block diagram illustrating a user equipment according to some embodiments;

[0019] Fig. 9 is a block diagram illustrating a network node according to some embodiments;

[0020] Fig.10 is a block diagram of a host communicating with a user device according to some embodiments;

[0021] Fig.11 is a block diagram of a virtualization environment according to some embodiments; and

[0022] Fig.12 is a block diagram of a host communicating with a user device via a base station over a partially wireless connection according to some embodiments. DETAILED DESCRIPTION

[0023] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. The embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art, wherein examples of embodiments of the inventive concept are shown. However, the inventive concept can be embodied in many different forms and should not be construed as being limited to the embodiments described herein. On the contrary, these embodiments are provided so that the present disclosure is comprehensive and complete and will fully convey the scope of the inventive concept to those skilled in the art. It should also be noted that these embodiments are not mutually exclusive. The components of one embodiment may be defaulted to being present / used in another embodiment.

[0024] There are some challenges. In some examples, unmanned aerial system traffic management ("UTM") can handle a large number of unmanned aerial systems ("UAS") across a large area. However, UTM cannot provide precise instructions to UAS based on the small area in which the UAS is flying.

[0025] Certain aspects of the present disclosure and embodiments thereof may provide solutions to these or other challenges. Various embodiments herein describe establishing direct communications between a ground system and one or more UAS based on remote identifiers ("IDs") of one or more UAS. In some examples, the ground system is associated with a specific location (e.g., an event venue or a specific area). After communications are established, the ground system can affect the manipulation and control of each UAS (e.g., helping the UAS detect and avoid obstacles). A UAS may refer to a pair of entities, such as a flying drone (e.g., an unmanned aerial vehicle ("UAV")) and an associated drone controller (e.g., a UAV controller ("UAV-C").

[0026] In some embodiments, regulations require that UASs must have a remote ID that is detectable by observers.

[0027] In additional or alternative embodiments, the ground system is able to communicate with the UAS even if the UAS is outside of the 3rd Generation Partnership Project ("3GPP") coverage. It is sufficient for the ground system (sometimes referred to herein as an Area Airspace Manager ("AAM") to have a (fixed) Internet connection to a UAS Service Provider ("USS"), which may have a repository of remote IDs and their current / last known locations.

[0028] In some embodiments, the term "unmanned aerial vehicle ("UAV") to everything ("U2X") communications" is used to refer to communications that support U2X services utilizing the Uu interface and / or PC5 (e.g., sidelink) reference point. U2X services are implemented by various types of U2X applications (e.g., UAV to UAV ("U2U") and UAV to network ("U2N")).

[0029] In additional or alternative embodiments, the term "U2X message" is used to refer to a dedicated messaging type of U2X service (eg, a broadcast remote identifier ("ID") message).

[0030] In additional or alternative embodiments, the term "U2X service type" is used herein to refer to a U2X service type, which is identified by, for example, an intelligent transportation system application identifier ("ITS-AID"), a provider service identifier ("PSID"), or an application identifier ("AID").

[0031] Various embodiments herein provide a network-assisted (e.g., ground-based) detect and avoid ("DAA") process. In some examples, the process is applicable to specific areas, such as stadiums or event venues where drones are used (e.g., for filming events). In some embodiments, a ground-based entity detects UAVs in an area such as a stadium / event venue and provides local policies to the UAS, for example, to avoid UAVs colliding with each other, rooftops, or structures. In additional or alternative embodiments, a ground-based entity detects UAVs in an area such as a stadium / event venue and provides local policies to the UAS to indicate permitted flight areas. In some examples, the operation is applicable to specific outdoor areas (e.g., events) where specific measures are locally established to avoid collisions between drones.

[0032] Figure 2 An example of a fifth generation system (“5GS”) is shown for a ground-based system, an Area Airspace Manager (“AAM”) 210 , for evasive detection and avoidance of drones 220 in a particular area.

[0033] In some embodiments, the event venue / area has a ground-based entity (e.g., AAM 210). AAM 210 may include one or more communication devices (sometimes referred to herein as user equipment ("UE")) capable of using PC5. AAM 210 may also have a direct connection to a data network ("DN") (250).

[0034] In additional or alternative embodiments, for applicable airspace of an area / venue, the AAM 210 may define local DAA rules for corresponding located UAVs 220. The local DAA rules may be based, for example, on detailed information of facilities and maps in the area / venue and knowledge of current usage requirements of the airspace.

[0035] In additional or alternative embodiments, local DAA rules must comply with policies for PC5 operation received from a fifth generation core ("5GC") or pre-configured in the UE.

[0036] In additional or alternative embodiments, AAM 210 can scan the airspace of an area / event venue for drones (e.g., UAV 220) by using upward-pointing radars and cameras.

[0037] In additional or alternative embodiments, the detected UAV is identified by its coordinates and a remote ID such as retrieved by a broadcast remote ID ("BRID") or network remote ID ("NRID") mechanism. In additional or alternative embodiments, the remote ID is retrieved from a UAS service provider ("USS") 240 based on the coordinates of the UAV 220.

[0038] In additional or alternative embodiments, the AAM establishes PC5 communications with each detected UAV 220 based on the retrieved remote ID.

[0039] In an additional or alternative embodiment, the AAM 210 provides a local DAA policy for each UAS present in the event venue / area using the PC 5. This can be used, for example, to prevent new drones from colliding with each other or entering the facility details.

[0040] In additional or alternative embodiments, a UAV 220 that receives a local DAA-related policy from an AAM 210 via a PC5 may forward the policy to its UAV-C 230. The policy may be provided to the UAV 220 as a transparent container, with the UAV-C 230 being the ultimate recipient. In some examples, the UAV-C 230 that receives the DAA local policy from the AAM 210 may manipulate the UAV 220 accordingly by using command and control (“C2”) communications in order to enforce the local policy and avoid collisions. In additional or alternative examples, the UAV-C that receives the DAA local policy from the AAM 210 may notify the AAM 210 of its network address (e.g., an Internet Protocol (“IP”) address or a Uniform Resource Locator (“URL”)) to enable direct AAM to UAV-C 230 communication via the DN 250.

[0041] In additional or alternative embodiments, UAVs 220 using different public land mobile networks PLMNs may be supported. In additional or alternative embodiments, both Long Term Evolution ("LTE") PC5 and New Radio ("NR") PC5 are supported.

[0042] In additional or alternative embodiments, the UAS (eg, UAV 220 and its UAV-C 230) may use direct communication through PC 5 or Uu communication through a 3GPP system for C2 communication.

[0043] Figure 3 Examples of signals transmitted as part of the DAA process are shown.

[0044] At block 310, AAM 210 scans the airspace above the area to find a drone (e.g., UAV 220) and detect its coordinates. For example, AAM 210 determines the coordinates of UAV 220 by using an upward pointing radar and camera.

[0045] At blocks 320a-b, the AAM 210 determines a remote ID ("RID") associated with the detected UAV 220. At block 320a, the AAM 210 receives the RID directly from the UAV 220 using PC5 or other means, such as a broadcast remote ID ("BRID"). At block 320b, the AAM 210 determines the ID by querying the USS 240 (RID repository) based on the coordinates of the detected UAV 220.

[0046] At block 330 , the AAM 210 establishes PC5 communications with the UAV 220 based on the RID.

[0047] At block 340, the AAM 210 provides information to the UAV 220 via the PC5 interface. In some embodiments, the information includes a local DAA strategy for the detected UAV 220 based on current UAV traffic conditions and local information and plans for the area / venue. At block 342, the UAV 220 may then forward the information to the UAV-C 230. In some examples, the information may be provided to the UAV as a transparent container.

[0048] At block 350 , the UAV-C 320 considers the local policy received from the AAM 210 and provides instructions (eg, maneuvering instructions) to the UAV 220 via C2 communications.

[0049] At blocks 360 and 362, UAV-C 320 may inform AAM 210 of its address (e.g., an Internet Protocol (“IP”) address or a Universal Resource Locator (“URL”)) to enable AAM 210 to communicate directly with UAV-C 230 over a data network. As shown, in some examples, UAV-C 230 may send the address to AAM 210 via UAV 220. In other examples, AAM 210 may have provided UAV-C 230 with the address of AAM 210 (e.g., in blocks 340, 342), and UAV-C 230 may provide the address of UAV-C 230 directly to AAM 210. In some embodiments, AAM 210 may provide subsequent information directly to UAV-C 230.

[0050] In the following description, although the communication device may be a wireless device 712A, 712B, a wired or wireless device UE 712C, UE 712D, UE 800, virtualized hardware 1104, virtual machines 1108A, 1108B, UE 1206, AAM 210, UAV 220, or UAV-C 230, UE 800 (also referred to herein as communication device 800) will be used to describe the functionality of the operation of the communication device. Now, according to some embodiments of the present inventive concept, reference will be made to Figure 4-6 The flowchart discusses the operation of the communication device 800 (using Figure 8 For example, the modules can be stored in Figure 8 The modules are stored in the memory 810, and these modules can provide instructions, so that when the instructions of the modules are executed by the corresponding communication device processing circuit 802, the processing circuit 802 performs the corresponding operations of the flowchart.

[0051] Figure 4 Examples of operations performed by a first communications device, such as a regional airspace manager ("AAM"), are shown.

[0052] At block 410, the processing circuit 802 determines that the second communications device is within the area. In some embodiments, determining that the second communications device is within the area includes scanning the area using at least one of: a radar system; and a camera system.

[0053] At block 420, the processing circuit 802 determines an identifier of the second communication device. In some embodiments, determining the identifier of the second communication device includes receiving a message from the second communication device, the message including the identifier. In additional or alternative embodiments, receiving the message includes receiving the message via at least one of: a broadcast message; and a short-range wireless message.

[0054] In additional or alternative embodiments, determining the identifier of the second communication device includes: determining the location of the second communication device; sending a first message to a database via a communication network, the first message including an indication of the location and a request for the identifier; and in response to sending the first message, receiving a second message from the database, the second message including an indicator of the identifier.

[0055] At block 430, the processing circuit 802 determines information associated with the area. In some embodiments, the information associated with the area includes at least one of: information associated with other communication devices in the area; information associated with structures and / or obstacles in the area; information associated with an operating strategy in the area; and a local detect and avoid DAA strategy.

[0056] At block 440, the processing circuit 802 sends a message to the second communication device via the communication interface 812 using the identifier. In some embodiments, sending the message includes sending an indication that the second communication device forwards the message to a third communication device associated with the second communication device. In additional or alternative embodiments, sending the message includes sending the information to the second communication device using the identifier of the second communication device. In some examples, sending the information to the second communication device includes sending the information to the second communication device via the PC5 interface.

[0057] At block 450, the processing circuit 802 receives a second message from the third communication device via the communication interface 812. In some embodiments, the second message includes an indication of an address associated with the third communication device.

[0058] In additional or alternative embodiments, receiving the second message includes receiving the second message from a third communication device via the second communication device.

[0059] In additional or alternative embodiments, the first message includes an indication of an address of the first communication device, and receiving the second message includes receiving the second message from a third communication device via a path through the communication network, the path not including the second communication device.

[0060] At block 460 , the processing circuit 802 sends the information associated with the region to the third communication device via the communication interface 812 .

[0061] In some embodiments, the first communication device comprises an AAM. In additional or alternative embodiments, the second communication device comprises a UAV. In additional or alternative embodiments, the third communication device comprises a UAV-C. In additional or alternative embodiments, the UAV-C and the UAV are part of an unmanned aerial system UAS. In additional or alternative embodiments, the area comprises at least one of: an event venue; and an event space.

[0062] Figure 4 Various operations may be optional. For example, regarding the following embodiment 1, Figure 4 Blocks 430, 450, and 460 may be optional.

[0063] Figure 5 Examples of operations performed by a second communication device, such as an unmanned aerial vehicle ("UAV"), are shown.

[0064] At block 510, the processing circuit 802 determines that the second communications device moves into an area associated with the first communications device.

[0065] At block 520, the processing circuit 802 transmits an indication of an identifier of the second communications device to the first communications device via the communications interface 812. In some embodiments, transmitting the identifier comprises transmitting the indication of the identifier using at least one of: a broadcast message; and a short range wireless message.

[0066] At block 530, processing circuit 802 receives a first message from a first communication device associated with the region via communication interface 812. In some embodiments, receiving the first message includes receiving the first message in response to sending the identifier. In additional or alternative embodiments, receiving the first message includes receiving the first message via a PC5 interface.

[0067] At block 540 , the processing circuit 802 sends a portion of the first message to the third communication device via the communication interface 812 .

[0068] At block 550, the processing circuit 802 receives a second message from the third communication device via the communication interface 812. In some embodiments, the second message includes at least one of: information associated with other communication devices in the area; information associated with structures and / or obstacles in the area; information associated with an operating strategy in the area; and a local detect and avoid DAA strategy.

[0069] At block 560, the processing circuit 802 modifies the operation of the second communications device based on the second message.

[0070] In some embodiments, the first communication device comprises an AAM. In additional or alternative embodiments, the second communication device comprises a UAV. In additional or alternative embodiments, the third communication device comprises a UAV-C. In additional or alternative embodiments, the UAV-C and the UAV are part of an unmanned aerial system UAS. In additional or alternative embodiments, the area comprises at least one of: an event venue; and an event space.

[0071] Figure 5 Various operations may be optional. For example, regarding the following embodiment 1, Figure 5 Blocks 510 and 520 may be optional.

[0072] Figure 6 An example of operations performed by a third communication device (e.g., a UAV controller ("UAV-C")) is shown.

[0073] At block 610, the processing circuit 802 receives a first message from a first communication device associated with the zone via the communication interface 812. In some embodiments, receiving the first message from the first communication device includes receiving the first message from the first communication device via a second communication device.

[0074] In additional or alternative embodiments, the first message includes information associated with the area. In some examples, the information includes at least one of: information associated with other communication devices in the area; information associated with structures and / or obstacles in the area; information associated with an operating strategy in the area; and a local detect and avoid (DAA) strategy.

[0075] At block 620, the processing circuit 802 determines instructions for a second communication device in the area based on the first message.

[0076] At block 630 , the processing circuit 802 sends a second message to the second communication device via the communication interface 812 , the second message including the instruction.

[0077] In some embodiments, the first communication device comprises an AAM. In additional or alternative embodiments, the second communication device comprises a UAV. In additional or alternative embodiments, the third communication device comprises a UAV-C. In additional or alternative embodiments, the UAV-C and the UAV are part of an unmanned aerial system UAS. In additional or alternative embodiments, the area comprises at least one of: an event venue; and an event space.

[0078] Figure 6 Various operations may be optional.

[0079] Figure 7 An example of a communication system 700 is shown in accordance with some embodiments.

[0080] In this example, the communication system 700 includes a telecommunications network 702, which includes an access network 704 (e.g., a radio access network (RAN)) and a core network 706 (which includes one or more core network nodes 708). The access network 704 includes one or more access network nodes, such as network nodes 710a and 710b (one or more of which may be generally referred to as network nodes 710), or any other similar third generation partnership project (3GPP) access node or non-3GPP access point. The network node 710 facilitates direct or indirect connection of user equipment (UE), such as connecting UE 712a, 712b, 712c, and 712d (one or more of which may be generally referred to as UE 712) to the core network 706 via one or more wireless connections.

[0081] Example wireless communications over wireless connections include sending and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Additionally, in various embodiments, the communication system 700 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals, whether via a wired or wireless connection. The communication system 700 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar types of systems.

[0082] UE 712 may be any of a variety of communication devices, including wireless devices that are arranged, configured and / or operable to wirelessly communicate with network node 710 and other communication devices. Similarly, network node 710 is arranged, capable, configured and / or operable to communicate directly or indirectly with UE 712 and / or other network nodes or devices in telecommunication network 702 to enable and / or provide network access (e.g., wireless network access) and / or perform other functions (e.g., management in telecommunication network 702).

[0083] In the illustrated example, the core network 706 connects the network node 710 to one or more hosts (e.g., host 716). These connections may be direct or indirect via one or more intermediate networks or devices. In other examples, the network node may be directly coupled to the host. The core network 706 includes one or more core network nodes (e.g., core network node 708), which are composed of hardware and software components. The features of these components may be substantially similar to those described for the UE, network node, and / or host, so that their description is generally applicable to the corresponding components of the core network node 708. The example core network node includes the functions of one or more of the following: a mobile switching center (MSC), a mobility management entity (MME), a home subscriber server (HSS), an access and mobility management function (AMF), a session management function (SMF), an authentication server function (AUSF), a subscription identifier decryption function (SIDF), a unified data management (UDM), a security edge protection proxy (SEPP), a network open function (NEF), and / or a user plane function (UPF).

[0084] The host 716 may be owned or controlled by a service provider other than the operator or provider of the access network 704 and / or the telecommunications network 702, and may be operated by or on behalf of the service provider. The host 716 may host various applications to provide one or more services. Examples of such applications include real-time and pre-recorded audio / video content, data collection services (e.g., retrieval and compilation of data of various environmental conditions detected by multiple UEs), analytical functions, social media, functions for controlling or otherwise interacting with remote devices, functions for alarm and monitoring centers, or any other such functions performed by a server.

[0085] Overall, Figure 7 The communication system 700 enables connections between UEs, network nodes, and hosts. In this sense, the communication system can be configured to operate according to predefined rules or procedures, such as, but not limited to, specific standards including: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standards (e.g., 6G); Wireless Local Area Network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard (WiFi); and / or any other suitable wireless communication standards, such as Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and / or any Low Power Wide Area Network (LPWAN) standards, such as LoRa and Sigfox.

[0086] In some examples, the telecommunication network 702 is a cellular network that implements 3GPP standardized features. Thus, the telecommunication network 702 can support network slicing to provide different logical networks to different devices connected to the telecommunication network 702. For example, the telecommunication network 702 can provide ultra-reliable low-latency communication (URLLC) services to some UEs while providing enhanced mobile broadband (eMBB) services to other UEs, and / or provide massive machine type communication (mMTC) / massive IoT services to other UEs.

[0087] In some examples, UE 712 is configured to send and / or receive information without direct human interaction. For example, the UE can be designed to send information to access network 704 according to a predetermined schedule, when triggered by an internal or external event, or in response to a request from access network 704. In addition, the UE can be configured to operate in a single RAT or multi-RAT or multi-standard mode. For example, the UE can operate using any one or any combination of Wi-Fi, NR (New Radio) and LTE, that is, configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved UMTS Terrestrial Radio Access Network) New Radio-Dual Connectivity (EN-DC).

[0088] In this example, the hub 714 communicates with the access network 704 to facilitate indirect communication between one or more UEs (e.g., UE 712c and / or 712d) and a network node (e.g., network node 710b). In some examples, the hub 714 can be a controller, a router, a content source and analysis, or any other communication device described herein with respect to the UE. For example, the hub 714 can be a broadband router that enables the UE to access the core network 706. As another example, the hub 714 can be a controller that sends commands or instructions to one or more actuators in the UE. The command or instruction can be received from the UE, the network node 710, or received by an executable code, script, process or other instruction in the hub 714. As another example, the hub 714 can be a data collector that acts as a temporary storage of UE data, and in some embodiments, analysis or other processing of the data can be performed. As another example, the hub 714 can be a content source. For example, for a UE that is a VR headset, display, speaker, or other media delivery device, the hub 714 can retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, and then provide it directly to the UE after performing local processing, and / or adding additional local content. In another example, the hub 714 acts as a proxy server or coordinator for the UE, especially if one or more of the UEs are low-energy IoT devices.

[0089] The hub 714 may have a constant / persistent or intermittent connection with the network node 710b. The hub 714 may also allow different communication schemes and / or scheduling between the hub 714 and the UE (e.g., UE 712c and / or 712d) and between the hub 714 and the core network 706. In other examples, the hub 714 is connected to the core network 706 and / or one or more UEs via a wired connection. In addition, the hub 714 may be configured to be connected to the M2M service provider and / or to another UE via a direct connection via the access network 704. In some cases, the UE may establish a wireless connection with the network node 710, while still being connected via the hub 714 via a wired or wireless connection. In some embodiments, the hub 714 may be a dedicated hub, i.e., the following hub: its main function is to route communication from the network node 710b to the UE, or from the UE to the network node 710b. In other embodiments, the hub 714 may be a non-dedicated hub, ie, a device operable to route communications between UEs and the network node 710b, but which is additionally capable of operating as a communications origin and / or endpoint for certain data channels.

[0090] Figure 8 UE 800 according to some embodiments is shown. As used herein, UE refers to a device capable of, configured, arranged and / or operable to wirelessly communicate with a network node and / or other UEs. Examples of UEs include, but are not limited to, smartphones, mobile phones, cellular phones, voice over IP (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, game consoles or devices, music storage devices, playback devices, wearable terminal devices, wireless endpoints, mobile stations, tablet computers, laptops, notebook embedded devices (LEEs), notebook mounted devices (LMEs), smart devices, wireless client equipment (CPEs), in-vehicle or vehicle embedded / integrated wireless devices, etc. Other examples include any UE identified by the Third Generation Partnership Project (3GPP), including narrowband Internet of Things (NB-IoT) UEs, machine type communications (MTC) UEs, and / or enhanced MTC (eMTC) UEs.

[0091] The UE may support device-to-device (D2D) communications, for example, by implementing 3GPP standards for: sidelink communications, dedicated short-range communications (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and / or operates the associated device. Instead, a UE may represent a device that is intended to be sold to or operated by a human user, but may not be associated with a specific human user, or may not initially be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended to be sold to or operated by an end user, but may be associated with or operated for the benefit of a user (e.g., a smart meter).

[0092] UE 800 includes a processing circuit 802, which is operatively coupled to an input / output interface 806, a power supply 808, a memory 810, a communication interface 812, and / or any other components, or any combination thereof, via a bus 804. Some UEs may use Figure 8 All or part of the components shown in . The degree of integration between components may vary from UE to UE. In addition, some UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0093] The processing circuit 802 is configured to process instructions and data, and may be configured to implement any sequential state machine that is operable to execute instructions stored in the memory 810 as a machine-readable computer program. The processing circuit 802 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors (e.g., microprocessors or digital signal processors (DSPs)) together with appropriate software; or any combination of the above. For example, the processing circuit 802 may include multiple central processing units (CPUs).

[0094] In this example, the input / output interface 806 can be configured to provide one or more interfaces to an input device, an output device, or one or more input and / or output devices. Examples of output devices include speakers, sound cards, video cards, displays, monitors, printers, actuators, transmitters, smart cards, another output device, or any combination thereof. An input device can allow a user to capture information into the UE 800. Examples of input devices include touch-sensitive or presence-sensitive displays, cameras (e.g., digital cameras, digital video cameras, web cameras, etc.), microphones, sensors, mice, trackballs, directional keys, trackpads, scroll wheels, smart cards, etc. A presence-sensitive display can include a capacitive or resistive touch sensor to sense input from a user. The sensor can be, for example, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biosensor, etc., or any combination thereof. An output device can use an interface port of the same type as an input device. For example, a universal serial bus (USB) port can be used to provide input devices and output devices.

[0095] In some embodiments, the power supply 808 is configured as a battery or a battery pack. Other types of power supplies may be used, such as an external power supply (e.g., a power outlet), a photovoltaic device, or a battery. The power supply 808 may also include a power supply circuit for delivering power from the power supply 808 itself and / or an external power supply to various parts of the UE 800 through an input circuit or interface (e.g., a power cable). The delivered power may be used, for example, to charge the power supply 808. The power supply circuit may perform any formatting, conversion, or other modification on the power from the power supply 808 so that the power is suitable for supplying power to various components of the UE 800.

[0096] The memory 810 may be or be configured to include a memory such as a random access memory (RAM), a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a magnetic disk, an optical disk, a hard disk, a removable cartridge, a flash drive, etc. In one example, the memory 810 includes one or more application programs 814, such as an operating system, a web browser application, a widget, a gadget engine, or other applications, and corresponding data 816. The memory 810 may store any of a variety of operating systems or a combination of operating systems for use by the UE 800.

[0097] The memory 810 may be configured to include multiple physical drive units, such as a redundant array of independent disks (RAID), a flash memory, a USB flash drive, an external hard drive, a thumb drive, a pen drive, a key drive, a high-density digital versatile disc (HD-DVD) optical drive, an internal hard drive, a Blu-ray optical drive, a holographic digital data storage (HDDS) optical drive, an external micro dual in-line memory module (DIMM), a synchronous dynamic random access memory (SDRAM), an external micro DIMM SDRAM, a smart card memory (e.g., a tamper-proof module in the form of a universal integrated circuit card (UICC), including one or more subscriber identity modules (SIMs), such as USIM and / or ISIM), other memories, or any combination thereof. The UICC may be an embedded UICC (eUICC), an integrated UICC (iUICC), or a removable UICC commonly referred to as a "SIM card". The memory 810 may allow the UE 800 to access instructions, applications, etc. stored on a temporary or non-temporary memory medium to offload data or upload data. An article of manufacture (eg, an article of manufacture utilizing a communication system) may be tangibly embodied as or in memory 810, which may be or include a device-readable storage medium.

[0098] The processing circuit 802 may be configured to communicate with an access network or other network using a communication interface 812. The communication interface 812 may include one or more communication subsystems and may include or be communicatively coupled to an antenna 822. The communication interface 812 may include one or more transceivers for communication, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or network node in the access network). Each transceiver may include a transmitter 818 and / or a receiver 820 suitable for providing network communications (e.g., optical, electrical, frequency allocation, etc.). In addition, the transmitter 818 and the receiver 820 may be coupled to one or more antennas (e.g., antenna 822) and may share circuit components, software or firmware, or may be implemented separately.

[0099] In the illustrated embodiment, the communication functions of the communication interface 812 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communication (e.g., Bluetooth), near field communication, location-based communication (e.g., using a global positioning system (GPS) to determine location), other similar communication functions, or any combination thereof. Communication may be implemented according to one or more communication protocols and / or standards, such as IEEE 802.11, code division multiple access (CDMA), wideband code division multiple access (WCDMA), GSM, LTE, new radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / Internet protocol (TCP / IP), synchronous optical network (SONET), asynchronous transfer mode (ATM), QUIC, hypertext transfer protocol (HTTP), etc.

[0100] Regardless of the sensor type, the UE may provide an output of data captured by its sensor to a network node via a wireless connection through its communication interface 812. The data captured by the UE's sensor may be transmitted to the network node via another UE via a wireless connection. The output may be periodic (e.g., every 15 minutes if it reports sensed temperature), random (e.g., to balance the reporting load from multiple sensors), in response to a trigger event (e.g., sending an alarm when moisture is detected), in response to a request (e.g., a user-initiated request), or a continuous stream (e.g., a live video feed of a patient).

[0101] As another example, the UE includes an actuator, motor, or switch associated with a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input, the state of the actuator, motor, or switch can change. For example, the UE can include a motor that adjusts a control surface or rotor of a drone in flight based on the received input, or adjusts a robotic arm performing a medical procedure based on the received input.

[0102] When the UE is in the form of an Internet of Things (IoT) device, the UE may be a device for one or more application areas including, but not limited to, urban wearable technology, extended industrial applications, and healthcare. Non-limiting examples of such IoT devices include the following devices or devices embedded in the following devices: connected refrigerators or freezers, televisions, connected lighting devices, electricity meters, robotic vacuum cleaners, voice-controlled smart speakers, home security cameras, motion detectors, thermostats, smoke detectors, door / window sensors, flood / humidity sensors, electric door locks, connected doorbells, air conditioning systems (such as heat pumps), self-driving cars, surveillance systems, weather monitoring devices, vehicle parking monitoring devices, electric vehicle charging stations, smart watches, fitness trackers, head-mounted displays for augmented reality (AR) or virtual reality (VR), wearable devices for tactile enhancement or sensory enhancement, sprinklers, animal or item tracking devices, sensors for monitoring plants or animals, industrial robots, unmanned aerial vehicles (UAVs), and any type of medical equipment (such as heart rate monitors or teleoperated surgical robots). In addition to including UEs in the form of IoT devices, UEs in the form of IoT devices include: Figure 8 In addition to the other components described in relation to the UE 800 shown in FIG. 8 , the UE 800 further includes circuits and / or software depending on the intended application of the IoT device.

[0103] As another specific example, in an IoT scenario, a UE may represent a machine or other device that performs monitoring and / or measurements and sends the results of such monitoring and / or measurements to another UE and / or a network node. In this case, the UE may be an M2M device, which may be referred to as an MTC device in the 3GPP context. As a specific example, a UE may implement the 3GPP NB-IoT standard. In other scenarios, a UE may represent a vehicle, such as a car, bus, truck, ship, and airplane, or other device capable of monitoring and / or reporting its operating status or other functions related to its operation.

[0104] In practice, any number of UEs may be used together for a single use case. For example, a first UE may be a drone or integrated into a drone and provide the drone's speed information (obtained via a speed sensor) to a second UE, which is a remote controller that operates the drone. When a user makes changes from the remote controller, the first UE may adjust the throttle on the drone (e.g., by controlling an actuator) to increase or decrease the drone's speed. The first UE and / or the second UE may also include more than one of the above-described functionalities. For example, a UE may include sensors and actuators, and handle communications for data for both the speed sensor and the actuator.

[0105] Fig. 9A network node 900 according to some embodiments is shown. As used herein, a network node refers to a device capable of, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or devices in a telecommunications network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., wireless access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs), and NR Node Bs (gNBs)).

[0106] Base stations can be classified according to the amount of coverage they provide (or in other words, their transmit power level), and therefore can be called femto base stations, pico base stations, micro base stations or macro base stations, depending on the amount of coverage provided. A base station can be a relay node or a relay donor node that controls a relay. A network node may also include one or more (or all) parts of a distributed radio base station, such as a centralized digital unit and / or a remote radio unit (RRU), sometimes referred to as a remote radio head (RRH). Such a remote radio unit may or may not be integrated with an antenna as an antenna-integrated radio. The parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).

[0107] Other examples of network nodes include multi-transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment (e.g., MSRBS), network controllers (e.g., radio network controllers (RNC) or base station controllers (BSC)), base transceiver stations (BTS), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCEs), operations and maintenance (O&M) nodes, operations support system (OSS) nodes, self-organizing network (SON) nodes, positioning nodes (e.g., evolved serving mobile positioning center (E-SMLC) and / or minimization of drive tests (MDT)).

[0108] The network node 900 includes a processing circuit 902, a memory 904, a communication interface 906, and a power supply 908. The network node 900 may be composed of multiple physically independent components (e.g., a NodeB component and an RNC component, or a BTS component and a BSC component, etc.), each of which may have its own components. In certain scenarios where the network node 900 includes multiple independent components (e.g., BTS and BSC components), one or more of the independent components may be shared between multiple network nodes. For example, a single RNC may control multiple NodeBs. In this case, each unique NodeB and RNC pair may be considered a single independent network node in some cases. In some embodiments, the network node 900 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be repeated (e.g., separate memories 904 for different RATs), and some components may be reused (e.g., the same antenna 910 may be shared by different RATs). The network node 900 may also include multiple sets of various illustrated components for different wireless technologies, such as GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, radio frequency identification (RFID), or Bluetooth wireless technologies, integrated into the network node 900. These wireless technologies may be integrated into the same or different chips or chipsets and other components within the network node 900.

[0109] The processing circuit 902 may include a microprocessor, a controller, a microcontroller, a central processing unit, a digital signal processor, an application specific integrated circuit, a field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic that is operable to provide network node 900 functionality alone or in combination with other network node 900 components (e.g., memory 904).

[0110] In some embodiments, processing circuitry 902 includes a system on chip (SOC). In some embodiments, processing circuitry 902 includes one or more of radio frequency (RF) transceiver circuitry 912 and baseband processing circuitry 914. In some embodiments, radio frequency (RF) transceiver circuitry 912 and baseband processing circuitry 914 may be located on separate chips (or chipsets), boards, or units, such as a radio unit and a digital unit. In alternative embodiments, part or all of RF transceiver circuitry 912 and baseband processing circuitry 914 may be located on the same chip or chipset, board, or unit.

[0111] The memory 904 may include any form of volatile or non-volatile computer-readable memory, including but not limited to persistent memory, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (e.g., hard disk), removable storage media (e.g., flash drive, compact disk (CD) or digital video disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory device that stores information, data and / or instructions that can be used by the processing circuit 902. The memory 904 may store any suitable instructions, data or information, including computer programs, software, applications, applications (including one or more of logic, rules, codes, tables) and / or other instructions that can be executed by the processing circuit 902 and used by the network node 900. The memory 904 may be used to store any calculations made by the processing circuit 902 and / or any data received via the communication interface 906. In some embodiments, the processing circuit 902 and the memory 904 are integrated.

[0112] The communication interface 906 is used for wired or wireless communication of signaling and / or data between network nodes, access networks and / or UEs. As shown, the communication interface 906 includes a port / terminal 916, for example, to send data to the network and receive data from the network via a wired connection. The communication interface 906 further includes a radio front-end circuit 918, which may be coupled to the antenna 910, or in some embodiments is a part of the antenna 910. The radio front-end circuit 918 includes a filter 920 and an amplifier 922. The radio front-end circuit 918 may be connected to the antenna 910 and the processing circuit 902. The radio front-end circuit may be configured to adjust the signal transmitted between the antenna 910 and the processing circuit 902. The radio front-end circuit 918 may receive digital data to be sent to other network nodes or UEs via a wireless connection. The radio front-end circuit 918 may use a combination of a filter 920 and / or an amplifier 922 to convert the digital data into a radio signal with appropriate channel and bandwidth parameters. The radio signal may then be sent via the antenna 910. Similarly, when receiving data, antenna 910 may collect radio signals, which may then be converted to digital data by radio front end circuitry 918. The digital data may be passed to processing circuitry 902. In other embodiments, the communication interface may include different components and / or different combinations of components.

[0113] In some alternative embodiments, the network node 900 does not include a separate radio front end circuit 918, but rather, the processing circuit 902 includes the radio front end circuit and is connected to the antenna 910. Similarly, in some embodiments, all or part of the RF transceiver circuit 912 is part of the communication interface 906. In other embodiments, the communication interface 906 includes one or more ports or terminals 916, the radio front end circuit 918, and the RF transceiver circuit 912 as part of a radio unit (not shown), and the communication interface 906 communicates with the baseband processing circuit 914, which is part of the digital unit (not shown).

[0114] Antenna 910 may include one or more antennas or antenna arrays configured to send and / or receive wireless signals. Antenna 910 may be coupled to radio front end circuitry 918 and may be any type of antenna capable of wirelessly sending and receiving data and / or signals. In some embodiments, antenna 910 is separate from network node 900 and may be connected to network node 900 via an interface or port.

[0115] The antenna 910, the communication interface 906 and / or the processing circuit 902 may be configured to perform any receiving operation and / or certain obtaining operations performed by the network node described herein. Any information, data and / or signal may be received from the UE, another network node and / or any other network device. Similarly, the antenna 910, the communication interface 906 and / or the processing circuit 902 may be configured to perform any sending operation performed by the network node described herein. Any information, data and / or signal may be sent to the UE, another network node and / or any other network device.

[0116] The power supply 908 provides power to the various components of the network node 900 in a form suitable for the various components (e.g., at the voltage and current levels required by each component). The power supply 908 may also include or be coupled to a power management circuit to provide power to the components of the network node 900 for performing the functions described herein. For example, the network node 900 may be connected to an external power source (e.g., a power grid, a power outlet) via an input circuit or interface (e.g., a cable), so that the external power source supplies power to the power circuit of the power supply 908. As a further example, the power supply 908 may include a power source in the form of a battery or a battery pack, which is connected to the power circuit or is integrated in the power circuit. If the external power source fails, the battery can provide backup power.

[0117] Embodiments of network node 900 may include Fig. 9Additional components beyond those shown in the figure are used to provide certain aspects of the network node functionality, including any functionality described herein and / or any functionality required to support the subject matter described herein. For example, the network node 900 may include a user interface device to allow information to be input into the network node 900 and to allow information to be output from the network node 900. This may allow a user to perform diagnostics, maintenance, repair, and other management functions on the network node 900.

[0118] Fig.10 is a block diagram of a host 1000 according to various aspects described herein, which may be Figure 7 1000 is an embodiment of a host 716. As used herein, the host 1000 may be or include various combinations of hardware and / or software, including processing resources in a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, a container, or a server farm. The host 1000 may provide one or more services to one or more UEs.

[0119] Host 1000 includes processing circuitry 1002, which is operably coupled to input / output interface 1006, network interface 1008, power supply 1010, and memory 1012 via bus 1004. Other components may be included in other embodiments. The features of these components may be similar to those described with respect to previous figures (e.g., Figure 8 and 9 ) have substantially similar features to the devices described in the drawings, so that their descriptions are generally applicable to corresponding components of the host 1000.

[0120] The memory 1012 may include one or more computer programs, including one or more host applications 1014 and data 1016, which may include user data, such as data generated by a UE for the host 1000 or data generated by the host 1000 for the UE. An embodiment of the host 1000 may utilize only a subset or all of the components shown. The host application 1014 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for a variety of different categories, types, or implementations of UE (e.g., mobile phones, desktop computers, wearable display systems, head-up display systems). The host application 1014 may also provide user authentication and license checks, and may periodically report health status, routing, and content availability to a central node (e.g., a device in a core network or on the edge). Thus, the host 1000 may select and / or indicate a different host for an over-the-top service for the UE. The host application 1014 may support various protocols, such as HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc.

[0121] Fig.11 1100 is a block diagram showing a virtualized environment, in which the functions implemented by certain embodiments can be virtualized. In this context, virtualization means creating a virtual version of a device or equipment, which may include a virtualized hardware platform, storage device, and network resources. As used herein, virtualization can be applied to any device or component thereof described herein, and relates to the implementation of at least a portion of the functions being implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components performed by one or more virtual machines (VMs), which are implemented in one or more virtual environments 1100 hosted by one or more hardware nodes (e.g., hardware computing devices operating as network nodes, UEs, core network nodes, or hosts). In addition, in embodiments where a virtual node does not require a radio connection (e.g., a core network node or host), the node may be fully virtualized.

[0122] Application 1102 (which may be alternatively referred to as a software instance, a virtual device, a network function, a virtual node, a virtual network function, etc.) runs in a virtualized environment Q400 to implement some features, functions and / or advantages of some embodiments disclosed herein.

[0123] The hardware 1104 includes processing circuits, memory, etc., and the memory stores software and / or instructions that can be executed by the hardware processing circuits and / or other hardware devices (e.g., network interfaces, input / output interfaces, etc.) as described herein. The processing circuits can execute software to instantiate one or more virtualization layers 1106 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 1108a and 1108b (one or more of which may be collectively referred to as VMs 1108) and / or perform any functions, features, and / or advantages associated with some embodiments described herein. The virtualization layer 1106 can present a virtual operating platform to the VMs 1108 that looks like network hardware.

[0124] The VM 1108 includes virtual processing, virtual memory, virtual networks or interfaces, and virtual storage, and can be run by a corresponding virtualization layer 1106. Different embodiments of instances of virtual devices 1102 can be implemented on one or more VMs 1108 and can be implemented in different ways. Virtualization of hardware is sometimes referred to as network function virtualization (NFV). NFV can be used to consolidate many network device types onto industry-standard high-capacity server hardware, physical switches, and physical storage, which can be located in data centers and client devices.

[0125] In the context of NFV, a VM 1108 may be a software implementation of a physical machine that runs programs as if they were running on a physical, non-virtualized machine. Each VM 1108 and a portion of the hardware 1104 on which the VM runs (whether dedicated to the VM or shared with other VMs) form a separate virtual network element. Still in the context of NFV, a virtual network function is responsible for handling a specific network function running in one or more VMs 1108 on top of the hardware 1104 and corresponds to an application 1102.

[0126] The hardware 1104 may be implemented in a standalone network node with general or specific components. The hardware 1104 may implement some functions via virtualization. Alternatively, the hardware 1104 may be part of a larger hardware cluster (e.g., in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 1110, which, among other things, oversees the lifecycle management of the application 1102. In some embodiments, the hardware 1104 is coupled to one or more radio units, each of which includes one or more transmitters and one or more receivers that may be coupled to one or more antennas. The radio unit may communicate directly with other hardware nodes via one or more appropriate network interfaces, and may be used in conjunction with virtual components to provide radio functions to virtual nodes, such as radio access nodes or base stations. In some embodiments, a control system 1112 may be used to provide some signaling, which may be used alternatively for communication between hardware nodes and radio units.

[0127] Fig.12 A communication diagram is shown in which a host 1202 communicates with a UE 1206 via a network node 1204 over a partial wireless connection according to some embodiments. According to various embodiments, reference will now be made to Fig.12 Describe the UE discussed in the previous paragraphs (e.g. Figure 7 UE 712a and / or Figure 8 UE 800), network node (e.g. Figure 7 The network node 710a and / or Fig. 9 network node 900) and a host (e.g. Figure 7 Host 716 and / or Fig.10 An example implementation of host 1000).

[0128] As with host 1000, embodiments of host 1202 include hardware, such as a communication interface, processing circuitry, and memory. Host 1202 further includes software that is stored in or accessible by host 1202 and that is executable by processing circuitry. The software includes a host application that is operable to provide services to a remote user, such as a UE 1206 connected via an over-the-top (OTT) connection 1250 extending between UE 1206 and host 1202. In providing services to a remote user, the host application can provide user data sent using OTT connection 1250.

[0129] The network node 1204 includes hardware that enables it to communicate with the host 1202 and the UE 1206. The connection 1260 can be direct or through a core network (such as Figure 7The core network 706 of the present invention) and / or one or more other intermediate networks (e.g., one or more public, private, or managed networks). For example, the intermediate network can be a backbone network or the Internet.

[0130] UE 1206 includes hardware and software, which is stored in or accessible by UE 1206 and can be executed by the processing circuit of UE. The software includes a client application, such as a web browser or an operator-specific "application", which is operable to provide services to human or non-human users via UE 1206 with the support of host 1202. In host 1202, the running host application can communicate with the running client application through an OTT connection 1250 terminated at UE 1206 and host 1202. In providing services to users, the client application of the UE can receive request data from the host application of the host and provide user data in response to the request data. The OTT connection 1250 can transmit the request data and the user data. The client application of the UE can interact with the user to generate user data, which is provided to the host application through the OTT connection 1250.

[0131] The OTT connection 1250 may extend via a connection 1260 between the host 1202 and the network node 1204 and via a wireless connection 1270 between the network node 1204 and the UE 1206 to provide connectivity between the host 1202 and the UE 1206. The connection 1260 and the wireless connection 1270 through which the OTT connection 1250 may be provided have been drawn abstractly to illustrate communications between the host 1202 and the UE 1206 via the network node 1204, without explicit reference to any intermediate devices and the precise routing of messages via those devices.

[0132] As an example of sending data via OTT connection 1250, in step 1208, host 1202 provides user data, which can be performed by running a host application. In some embodiments, the user data is associated with a specific human user interacting with UE 1206. In other embodiments, the user data is associated with UE 1206 that shares data with host 1202 without explicit human interaction. In step 1210, host 1202 initiates a transmission carrying user data to UE 1206. Host 1202 may initiate the transmission in response to a request sent by UE 1206. The request may be caused by human interaction with UE 1206, or by the operation of a client application running on UE 1206. According to the teachings of the embodiments described in the present disclosure, the transmission may pass through network node 1204. Therefore, in step 1212, according to the teachings of the embodiments described in the present disclosure, network node 1204 sends the user data carried in the transmission initiated by host 1202 to UE 1206. In step 1214 , UE 1206 receives user data carried in a transmission, which may be performed by a client application running on UE 1206 that is associated with a host application running on host 1202 .

[0133] In some examples, UE 1206 runs a client application that provides user data to host 1202. The user data may be provided as a reaction or response to data received from host 1202. Thus, in step 1216, UE 1206 may provide the user data, which may be performed by running the client application. In providing the user data, the client application may also take into account user input received from a user via an input / output interface of UE 1206. Regardless of the specific manner in which the user data is provided, UE 1206 initiates transmission of the user data to host 1202 via network node 1204 in step 1218. In step 1220, network node 1204 receives user data from UE 1206 and initiates transmission of the received user data to host 1202 in accordance with the teachings of the embodiments described in the present disclosure. In step 1222, host 1202 receives the user data carried in the transmission initiated by UE 1206.

[0134] One or more of the various embodiments improves the performance of OTT services provided to UE 1206 using OTT connection 1250, with wireless connection 1270 forming the last leg. More specifically, the teachings of these embodiments may allow a ground-based system to provide information associated with a particular area to a UAS, including a UAV in a particular area.

[0135] In an example scenario, host 1202 may collect and analyze plant status information. As another example, host 1202 may process audio and video data that may have been retrieved from a UE for use in creating a map. As another example, host 1202 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, host 1202 may store surveillance videos uploaded by a UE. As another example, host 1202 may store or control access to media content (e.g., video, audio, VR, or AR) that may be broadcast, multicast, or unicast to a UE. As other examples, host 1202 may be used for energy pricing, remote control of non-time-critical electrical loads to balance power generation demand, location services, presentation services (e.g., compiling charts from data collected from remote devices, etc.), or any other function that collects, retrieves, stores, analyzes, and / or transmits data.

[0136] In some examples, a measurement process may be provided for monitoring data rates, delays, and other factors that are improved by one or more embodiments. There may also be an optional network function for reconfiguring the OTT connection 1250 between the host 1202 and the UE 1206 in response to changes in the measurement results. The measurement process and / or the network function for reconfiguring the OTT connection may be implemented in the software and hardware of the host 1202 and / or the UE 1206. In some embodiments, sensors (not shown) may be deployed in or associated with other devices through which the OTT connection 1250 passes; the sensors may participate in the measurement process by providing the values ​​of the monitoring quantities exemplified above or providing the values ​​of other physical quantities, and the software may calculate or estimate the monitoring quantities from other physical quantities. The reconfiguration of the OTT connection 1250 may include message formats, retransmission settings, preferred routes, etc.; the reconfiguration does not require direct changes to the operation of the network node 1204. Such processes and functions may be known and practiced in the art. In some embodiments, the measurement may involve proprietary UE signaling, which facilitates the host 1202 to measure throughput, propagation time, delay, etc. Measurements may be implemented in that the software sends a message, in particular an empty message or a "dummy" message, using the OTT connection 1250 while monitoring propagation time, errors, etc.

[0137] Although the computing devices (e.g., UE, network node, host) described herein may include a combination of the hardware components shown, other embodiments may include computing devices with different combinations of components. It should be understood that these computing devices may include any suitable combination of hardware and / or software required to perform the tasks, features, functions and methods disclosed herein. The determination, calculation, acquisition or similar operations described herein may be performed by a processing circuit, which may process information by, for example, converting the acquired information into other information, comparing the acquired information or the converted information with the information stored in the network node, and / or performing one or more operations based on the acquired information or the converted information, and making a determination based on the result of the processing. In addition, although the components are depicted as a single box located within a larger box or nested within multiple boxes, in practice, a computing device may include multiple different physical components constituting a single illustrated component, and functions may be divided between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functions of the components may be divided between a processing circuit and a communication interface. In another example, the non-computationally intensive functions of any such component may be implemented in software or firmware, while the computationally intensive functions may be implemented in hardware.

[0138] In some embodiments, some or all of the functionality described herein may be provided by a processing circuit executing instructions stored in a memory, which in some embodiments may be a computer program product in the form of a non-temporary computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by a processing circuit (e.g., in a hardwired manner) without executing instructions stored on a separate or discrete device-readable storage medium. In any of these particular embodiments, the processing circuit may be configured to perform the described functionality, regardless of whether instructions stored on a non-temporary computer-readable storage medium are executed. The benefits provided by such functionality are not limited to processing circuits or other components of a computing device, but are generally enjoyed by the entire computing device and / or end users and wireless networks.

Claims

1. A method of operating a first communication device, the method comprising: Determining (410) that a second communication device is within the area; determining (420) an identifier of the second communication device; as well as A message is sent (440) to the second communication device using the identifier.

2. The method according to claim 1, wherein: The first communication device comprises an area airspace manager AAM, Wherein, the second communication device comprises an unmanned aerial vehicle UAV, and The area includes at least one of the following: Event venues; and Event space.

3. The method according to any one of claims 1 to 2, wherein: Determining that the second communication device is within the area includes scanning the area using at least one of: Radar systems; and Camera system.

4. The method according to any one of claims 1 to 3, wherein: Determining the identifier of the second communication device comprises: A message is received from the second communication device, the message including the identifier.

5. The method according to claim 4, wherein: Receiving the message includes receiving the message via at least one of: Broadcast messages; and Short range wireless messaging.

6. The method according to any one of claims 1 to 3, wherein: Determining the identifier of the second communication device comprises: determining a location of the second communication device; sending a first message to a database via a communications network, the first message comprising an indication of the location and a request for the identifier; and In response to sending the first message, a second message is received from the database, the second message including an indicator of the identifier.

7. The method according to any one of claims 1 to 6, wherein: Sending the message includes sending an indication that the second communication device forwards the message to a third communication device associated with the second communication device.

8. The method according to any one of claims 1 to 7, wherein: The message comprises a first message, The method further comprises: A second message is received (450) from a third communication device associated with the second communication device, the second message including an indication of an address associated with the third communication device.

9. The method according to claim 8, wherein: Receiving the second message includes receiving the second message from the third communication device via the second communication device.

10. The method according to claim 8, wherein: the first message comprises an indication of an address of the first communications device, and Wherein, receiving the second message comprises: receiving the second message from the third communication device via a path through a communication network, wherein the path does not include the second communication device.

11. The method according to any one of claims 8 to 10, further comprising: determining (430) information associated with the region; as well as Information associated with the zone is sent (460) to the third communication device using the address associated with the third communication device.

12. The method according to any one of claims 7 to 11, wherein: The third communication device comprises an unmanned aerial vehicle controller UAV-C, the UAV-C and the UAV being part of an unmanned aerial system UAS.

13. The method according to any one of claims 1 to 6, further comprising: determining (430) information associated with the region, The sending of the message includes: sending information to the second communication device using the identifier.

14. The method according to claim 13, wherein: Sending the information to the second communication device includes: sending the information to the second communication device via a PC5 interface.

15. The method according to any one of claims 11 to 14, wherein: The information associated with the area includes at least one of the following: information associated with other communication devices within the area; information associated with structures and / or obstacles in the area; information associated with an operating strategy in the area; as well as Local detect and avoid DAA strategy.

16. A method of operating a second communication device, the method comprising: receiving (530) a first message from a first communication device associated with the zone; sending (540) a portion of the first message to a third communication device; receiving (550) a second message from the third communication device in response to sending the portion of the first message; as well as Operation of the second communication device is modified (560) based on the second message.

17. The method according to claim 16, wherein: The first communication device comprises an area airspace manager AAM, Wherein, the second communication device comprises an unmanned aerial vehicle UAV, wherein the third communication device comprises an unmanned aerial vehicle controller UAV-C, the UAV-C and the UAV are part of an unmanned aerial system UAS, and The area includes at least one of the following: Event venues; and Event space.

18. The method according to any one of claims 16-7, further comprising: moving (510) to the area associated with the first communication device; as well as sending (520) to the first communication device an indication of an identifier of the second communication device, Receiving the first message includes: receiving the first message in response to sending the identifier.

19. The method according to claim 18, wherein: Sending the identifier includes sending the indication of the identifier using at least one of: Broadcast messages; and Short range wireless messaging.

20. The method according to any one of claims 16 to 19, wherein: Receiving the first message includes: receiving the first message via a PC5 interface.

21. The method according to any one of claims 16 to 20, wherein: The second message includes at least one of the following: information associated with other communication devices within the area; information associated with structures and / or obstacles within the area; information associated with an operating strategy within the region; as well as Local detect and avoid DAA strategy.

22. A method of operating a third communication device, the method comprising: receiving (610) a first message from a first communication device associated with a zone; In response to receiving the first message, determining (620) instructions for operating a second communication device in the area based on the first message; as well as A second message is sent (630) to the second communication device, the second message including the instruction.

23. The method according to claim 22, wherein: The first communication device comprises an area airspace manager AAM, Wherein, the second communication device comprises an unmanned aerial vehicle UAV, wherein the third communication device comprises an unmanned aerial vehicle controller UAV-C, the UAV-C and the UAV are part of an unmanned aerial system UAS, and The area includes at least one of the following: Event venues; and Event space.

24. The method according to any one of claims 22-23, wherein: Receiving the first message from the first communication device includes receiving the first message from the first communication device via the second communication device.

25. The method according to any one of claims 22 to 24, wherein: The first message includes information associated with the area, the information including at least one of the following: information associated with other communication devices within the area; information associated with structures and / or obstacles in the area; information associated with an operating strategy in the area; and Local detect and avoid DAA strategy.

26. A communication device (800), the network node comprising: Processing circuit (802); as well as A memory (810) coupled to the processing circuit and having stored therein instructions that are executed by the processing circuit to cause the communication device to perform operations including any of the operations of claims 1-25.

27. A computer program comprising program code to be executed by processing circuitry (802) of a communication device (800), whereby execution of the program code causes the communication device to perform operations including any of the operations of claims 1-25.

28. A computer program product comprising a non-transitory storage medium (810) comprising program code to be executed by a processing circuit (802) of a communication device (800), wherein: Execution of the program code causes the communication device to perform operations including any of the operations of claims 1-25.

29. A non-transitory computer-readable medium having instructions stored therein, the instructions being executed by processing circuitry (802) of the communication device (800) to cause the communication device to perform operations including any of the operations of claims 1-25.

Images