Communication method and communication apparatus

Abstract

Embodiments of the present application provide a communication method and a communication apparatus. The method is applied to a scenario in which an unmanned aerial vehicle switches from a source server to a target server. The method comprises: a first device acquires information about the target server, the information about the target server being used for creating a connection between the unmanned aerial vehicle and the target server; and the first device sends the information about the target server. In this way, in a scenario in which an unmanned aerial vehicle switches from a source server to a target server, a first device acquires information about the target server and sends the information to a related network element to create a connection between the unmanned aerial vehicle and a target server, thereby ensuring that service and management of the unmanned aerial vehicle are not interrupted.

Description

Communication method and communication apparatus

[0001] The present application claims priority to the Chinese patent application No. 202410673934.5, filed on May 27, 2024, and entitled "Communication method and communication apparatus", the content of which is incorporated herein by reference in its entirety. TECHNICAL FIELD

[0002] The present application relates to the field of communication, in particular to a communication method and a communication apparatus. BACKGROUND

[0003] In recent years, the application of unmanned aerial vehicles (UAVs) based on the fifth generation (5G) communication system is becoming more and more popular. When the UAV flies in the service area corresponding to the unmanned aerial system service supplier (USS), the UAV can create a service connection with the USS through the 5G network, and then the USS can better serve and manage the UAV through the 5G network.

[0004] However, when the UAV cannot be served by the source USS, how to switch to another target USS through the 5G network to continue to serve and manage the UAV remains to be studied. SUMMARY

[0005] The communication method and the communication apparatus provided by the embodiments of the present application can solve the problem of obtaining the information of the target server and sending it to the related network element to create a connection between the UAV and the target server in the scenario of switching from the source server to the target server, and ensure that the service and management of the UAV are not interrupted.

[0006] To achieve the above-mentioned purpose, the embodiments of the present application adopt the following technical solutions:

[0007] In a first aspect, a communication method is provided. The method can be executed by components of a first device, such as a processor, a chip, or a chip system of the first device, and can also be realized by a logic module or software that can realize all or part of the first device. The method is applied in the scenario of switching from a source server to a target server by a UAV, and includes: obtaining, by the first device, information of the target server, the information of the target server being used to create a connection between the UAV and the target server; and sending, by the first device, the information of the target server.

[0008] In the embodiment, the source server can be a server of a source unmanned aerial system service provider, and the target server can be a server of a target unmanned aerial system service provider. In the source server to target server switching scenario, the first device can obtain the information of the target server, and then send the information of the target server to other network elements, so as to create a connection from the unmanned aerial vehicle to the target server, and ensure that the service and management of the unmanned aerial vehicle are not interrupted.

[0009] In a possible implementation, the method further includes: the first device sending the information of the target server to the unmanned aerial vehicle. That is, the first device can send the information of the target server to the unmanned aerial vehicle, for the unmanned aerial vehicle to create a connection to the target server.

[0010] In a possible implementation, the first device is a source server, and the first device sending the information of the target server includes: the source server sending the information of the target server to the first network device. That is, as one of the first devices, the source server can determine the information of the target server, and further send the information of the target server to the first network device, for the first network device to create a connection from the unmanned aerial vehicle to the target server.

[0011] In a possible implementation, the first device sending the information of the target server to the unmanned aerial vehicle includes: the source server sending the information of the target server to the unmanned aerial vehicle through an application layer path or a network layer path. That is, as one of the first devices, the source server can discover the information of the target server, and then send the information of the target server to the unmanned aerial vehicle through an application layer path or a network layer path, for the unmanned aerial vehicle to create a connection to the target server.

[0012] In a possible implementation, the first device is a first network device, and the first device sending the information of the target server includes: the first network device sending the information of the target server to the source server. That is, as one of the first devices, the first network device can determine the information of the target server, and further send the information of the target server to the source server, for the source server to create a connection from the unmanned aerial vehicle to the target server.

[0013] In a possible implementation, the first device sending the information of the target server to the unmanned aerial vehicle includes: the first network device sending the information of the target server to the unmanned aerial vehicle through a network layer path; or the first network device sending the information of the target server to the unmanned aerial vehicle through the source server. That is, as one of the first devices, the first network device sends the information of the target server to the unmanned aerial vehicle through a network layer path; or the first network device sends the information of the target server to the unmanned aerial vehicle through the source server, for the unmanned aerial vehicle to create a connection to the target server.

[0014] In a possible implementation, the first device acquires the information of the target server, including: the first device acquires the information of the target server according to the position information of the UAV and configuration information on the first device, and the configuration information includes a mapping relationship between the position information of the UAV and the information of the target server. That is, the first device can determine the information of the target server according to the position information of the UAV and the local configuration information, and the configuration information includes a mapping relationship between the position information of the UAV and the information of the target server.

[0015] In a possible implementation, the first device acquires the information of the target server, including: the first device sends a first request to the second device, the first request is used to request the information of the target server, and the first request includes the position information of the UAV; and the first device receives the information of the target server from the second device. That is, the first device sends a first request to the second device, the first request is used to request the information of the target server, and the first request includes the position information of the UAV.

[0016] In a possible implementation, the second device can be a network storage function network element in an operator network, or can be a domain name server of a third-party management and control server for addressing a UAV system service provider.

[0017] In a possible implementation, the first device sends the information of the target server, including: the first device sends the information of the target server and first indication information, and the first indication information is used to instruct the UAV to switch from the source server to the target server. It should be understood that if the first device is the source server, the source server can send the first indication information used to instruct the UAV to switch from the source server to the target server at the same time when the source server sends the information of the target server to the first network device and / or the UAV, so that one or more of the source server, the first network device and the UAV can create a connection between the UAV and the target server, ensuring that the service and management of the UAV are not interrupted; if the first device is the first network device, the first network device can send the first indication information used to instruct the UAV to switch from the source server to the target server at the same time when the first network device sends the information of the target server to the source server and / or the UAV, so that one or more of the source server, the first network device and the UAV can create a connection between the UAV and the target server, ensuring that the service and management of the UAV are not interrupted.

[0018] In a possible implementation, the first device sends the information of the target server, including: the first device sends the information of the target server and second indication information, the second indication information being used to indicate to create a connection between the drone and the target server. It should be understood that if the first device is the source server, the source server can send the second indication information used to indicate to create the connection between the drone and the target server at the same time when the source server sends the information of the target server to the first network device and / or the drone, so that one or more of the source server, the first network device and the drone can create the connection between the drone and the target server, ensuring that the service and management of the drone are not interrupted; if the first device is the first network device, the first network device can send the second indication information used to indicate to create the connection between the drone and the target server at the same time when the first network device sends the information of the target server to the source server and / or the drone, so that one or more of the source server, the first network device and the drone can create the connection between the drone and the target server, ensuring that the service and management of the drone are not interrupted.

[0019] In a possible implementation, the first network device is one or more of the following network elements: an access and mobility management function (AMF) network element, a session management function (SMF) network element, a drone air system network function (UAS NF) network element, and a network exposure function (NEF) network element.

[0020] In a second aspect, a communication apparatus is provided for implementing the methods in the above aspects and / or possible implementations. The communication apparatus can be the first device in any of the above aspects and / or possible implementations, or a device including the first device, or a device included in the first device, such as a chip. The communication apparatus includes modules, units, or means for implementing the corresponding functions of the above methods, which can be implemented by hardware, software, or by executing corresponding software with hardware. The hardware or software includes one or more modules or units corresponding to the above functions.

[0021] In some possible designs, the communication apparatus can include a processing module and a transceiver module. The transceiver module, which can also be referred to as a transceiver unit, is configured to implement the functions of sending and / or receiving in any of the above aspects and / or possible implementations. The transceiver module can be composed of a transceiver circuit, a transceiver, a transceiver chip, or a communication interface. The processing module can be configured to implement the processing functions in any of the above aspects and / or possible implementations.

[0022] In some possible designs, the transceiver module includes a sending module and a receiving module, which are configured to implement the functions of sending and receiving in any of the above aspects and / or possible implementations, respectively.

[0023] In a third aspect, a communication apparatus is provided, which comprises at least one processor; the processor is configured to execute computer programs or instructions to enable the communication apparatus to perform the method in any of the preceding aspects.

[0024] In a possible implementation, the communication apparatus further comprises the memory. Optionally, the memory is coupled with the processor, the memory can be integrated with the processor, or the memory can be independent of the processor. Optionally, the processor is configured to execute the computer programs or instructions stored in the memory.

[0025] In a possible implementation, the memory is independent of the communication apparatus.

[0026] In a possible implementation, the communication apparatus further comprises a communication interface configured to communicate with modules outside the communication apparatus.

[0027] The communication apparatus can be the first device in any of the preceding aspects or any of the implementations thereof, or an apparatus comprising the first device, or an apparatus comprised in the first device, such as a chip.

[0028] In a fourth aspect, a computer readable storage medium is provided, which stores computer programs or instructions, when executed on a communication apparatus, enable the communication apparatus to perform the method in any of the preceding aspects or any of the implementations thereof.

[0029] In a fifth aspect, a computer program product is provided, which comprises instructions, when executed on a communication apparatus, enable the communication apparatus to perform the method in any of the preceding aspects or any of the implementations thereof.

[0030] In a sixth aspect, a communication apparatus (for example, the communication apparatus can be a chip or a chip system) is provided, which comprises a processor configured to implement the functions involved in any of the preceding aspects or any of the implementations thereof.

[0031] In some possible designs, the communication apparatus comprises a memory configured to store necessary program instructions and data.

[0032] In some possible designs, when the apparatus is a chip system, the apparatus can be composed of a chip, or can comprise a chip and other discrete devices.

[0033] It can be understood that, when the communication apparatus in any of the second aspect to the sixth aspect is a chip, the sending action / functionality can be understood as output, and the receiving action / functionality can be understood as input.

[0034] The technical effects of any of the design methods in aspects two through six can be found in the technical effects of the different design methods in aspect one above, and will not be repeated here.

[0035] A seventh aspect provides a communication system comprising: a source server and a first network device as described in any of the above aspects or any implementation thereof. Attached Figure Description

[0036] Figure 1 is a schematic diagram of the architecture of a communication system provided in an embodiment of this application;

[0037] Figure 2 is a schematic diagram of the architecture of another communication system provided in an embodiment of this application;

[0038] Figure 3 illustrates a schematic diagram of an application scenario applicable to an embodiment of this application;

[0039] Figure 4 is a flowchart illustrating an information transmission method provided in an embodiment of this application;

[0040] Figure 5 is a schematic flowchart of an information transmission method provided in an embodiment of this application;

[0041] Figure 6 is a flowchart illustrating an information transmission method according to an embodiment of this application.

[0042] Figure 7 is a flowchart illustrating an information transmission method according to an embodiment of this application;

[0043] Figure 8 is a schematic diagram of a communication device structure provided in an embodiment of this application;

[0044] Figure 9 is a schematic diagram of a communication device structure provided in an embodiment of this application. Detailed Implementation

[0045] The technical solutions in this application will now be described with reference to the accompanying drawings.

[0046] The technical solutions of this application embodiment can be applied to various communication systems, such as wireless network systems, vehicle-to-everything (V2X) communication systems, device-to-device (D2D) communication systems, vehicle-to-everything (V2X) communication systems, 4G mobile communication systems such as long term evolution (LTE) systems, worldwide interoperability for microwave access (WiMAX) communication systems, 5G mobile communication systems such as new radio (NR) systems, and future communication systems, etc.

[0047] In the embodiments of the present application, the indication can include direct indication and indirect indication, and can also include explicit indication and implicit indication. If a certain information (such as the first indication information, the second indication information, or the third indication information, etc. below) is indicated by the information indicated by the information, the information to be indicated is referred to as the to-be-indicated information. In the specific implementation process, there are many ways to indicate the to-be-indicated information, for example, but not limited to, the to-be-indicated information can be directly indicated, such as the to-be-indicated information itself or the index of the to-be-indicated information, etc. The to-be-indicated information can also be indirectly indicated by indicating other information, where the other information and the to-be-indicated information have an association relationship. The to-be-indicated information can also be indicated only by a part of the to-be-indicated information, and the other part of the to-be-indicated information is known or agreed in advance. For example, the indication of a specific information can also be achieved by means of the arrangement order of each information agreed in advance (for example, a protocol stipulates), thereby reducing the indication overhead to a certain extent. At the same time, the common part of each information can be identified and uniformly indicated, so as to reduce the indication overhead caused by separately indicating the same information.

[0048] In addition, the specific indication manner can also be various existing indication manners, for example, but not limited to, the above-mentioned indication manners and various combinations thereof, etc. The specific details of various indication manners can refer to the prior art, and will not be described herein. As can be seen from the above, for example, when multiple information of the same type needs to be indicated, the indication manner of different information can be different. In the specific implementation process, the required indication manner can be selected according to the specific needs, and the selected indication manner is not limited in the embodiments of the present application. In this way, the indication manner involved in the embodiments of the present application should be understood as covering various methods that can enable the to-be-indicated party to know the to-be-indicated information.

[0049] The predefinition or pre-configuration can be achieved by pre-saving the corresponding code, table or other information that can be used to indicate the related information in the device, and the specific implementation manner thereof is not limited in the embodiments of the present application. The saving can be saved in one or more memories. The one or more memories can be separately set, or can be integrated in the encoder or decoder, processor, or communication device. The one or more memories can be part of the separately set, and part of the integrated in the decoder, processor, or communication device. The type of the memory can be any form of storage medium, and the present application is not limited thereto.

[0050] The protocol involved in the embodiments of the present application can refer to the protocol family in the communication field, the standard protocol similar to the protocol family frame structure, or the related protocol applied to the future communication system, and the present application is not limited thereto.

[0051] In the embodiments of the present application, "when", "in the case of", "if" and the like all refer to the device making corresponding processing under certain objective circumstances, and are not limited to time, and do not require the device to have a judgment action when implemented, nor does it mean that there are other limitations.

[0052] In the description of the embodiments of the present application, unless otherwise specified, " / " represents that the objects before and after the " / " are in an "or" relationship, for example, A / B can represent A or B; "and / or" in the embodiments of the present application is only a description of the association relationship of the associated objects, which means that there can be three relationships, for example, A and / or B can represent: A exists alone, A and B exist simultaneously, and B exists alone, where A and B can be singular or plural. In addition, in the description of the embodiments of the present application, unless otherwise specified, "multiple" means two or more than two. "At least one of the following" or the like means any combination of the items, including any combination of single item or multiple items. For example, at least one of a, b or c can represent: a, b, c, a-b, a-c, b-c, or a-b-c, where a, b, and c can be single or multiple. In addition, in order to clearly describe the technical solutions of the embodiments of the present application, in the embodiments of the present application, "first", "second", and the like are used to distinguish the same items or similar items with basically the same function and effect. Those skilled in the art can understand that "first", "second", and the like do not limit the quantity and execution order, and "first", "second", and the like do not necessarily mean different. At the same time, in the embodiments of the present application, "exemplary" or "for example" means to serve as an example, illustration or description. Any embodiment or design scheme described as "exemplary" or "for example" in the embodiments of the present application should not be interpreted as more preferred or more advantageous than other embodiments or design schemes. Rather, "exemplary" or "for example" is used to present the relevant concept in a specific manner, and to facilitate understanding.

[0053] The network architecture and service scenarios described in the embodiments of the present application are used to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided by the embodiments of the present application. Those skilled in the art can know that, as the network architecture evolves and new service scenarios appear, the technical solutions provided by the embodiments of the present application are also applicable to similar technical problems.

[0054] For the convenience of understanding the embodiments of the present application, FIG. 1 is a 5G network architecture based on a service interface provided by the embodiments of the present application. The architecture includes terminal devices (user equipment, UE), radio access network devices (radio access network, RAN), operation / administration and maintenance (operation administration and maintenance, OAM), access and mobility management functions (access and mobility management function, AMF), session management functions (session management function, SMF), user plane functions (user plane function, UPF), policy control functions (policy control function, PCF), unified data management (unified data management, UDM), NRF, NWDAF, NEF, AF, and the like.

[0055] wherein,

[0056] UE: can be located within the beam / cell coverage range of the access network device, and the access network device can provide communication services for the terminal device.

[0057] In FIG. 1, the UE can be a device with wireless transceiver function or a chip or chip system that can be provided in the device, and can allow a user to access a network, which is a device used to provide voice and / or data connectivity to a user. The UE can also be referred to as a terminal device, a subscriber unit, a terminal, or a mobile station (MS) or a mobile terminal (MT), etc.

[0058] For example, the UE in FIG. 1 can be a mobile phone, a tablet computer, or a computer with wireless transceiver function. The terminal device can also be a user station, a mobile station, a remote station, a remote terminal device, a mobile terminal device, a user terminal device, a wireless communication device, a user agent, a user device, a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a handheld device with wireless communication function, a computing device, a processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in Internet of Things, a household appliance, a virtual reality (VR) terminal, an augmented reality (AR) terminal, a wireless terminal in industrial control, a wireless terminal in unmanned, a wireless terminal in telemedicine, a wireless terminal in smart grid, a wireless terminal in smart city, a wireless terminal in smart home, a vehicle with vehicle-to-vehicle (V2V) communication capability, a smart connected vehicle, a drone with unmanned aerial vehicle to unmanned aerial vehicle (U2U) communication capability, a terminal device in future network, or a terminal device in future evolved public land mobile network (PLMN), etc., without limitation.

[0059] RAN: can be any kind of device deployed in an access network that can communicate with a terminal device wirelessly, and can also be a chip or chip system that can be provided in the above device, and can also be a logical node or a logical module or a function implemented in software, and can be used to implement functions such as wireless physical control function, resource scheduling and wireless resource management, wireless access control, and mobility management. Specifically, the network device can be a device supporting wired access, or a device supporting wireless access.

[0060] An access network device can be composed of one or more access network (AN) / radio access network (RAN) nodes, for example. The AN / RAN nodes can be: a gNB, a transmission reception point (TRP), an evolved NodeB (eNB), a radio network controller (RNC), a NodeB, a base station controller (BSC), a base transceiver station (BTS), a home base station (for example, home eNodeB, or home NodeB, HNB), a base band unit (BBU), or a wireless fidelity (Wi-Fi) access point (AP), etc.

[0061] In yet another example, a radio access network device can also be a device including a centralized unit (CU) node, or including a distributed unit (DU) node, or including a CU node and a DU node. For example, an access network device can be logically divided into a CU and a DU, with the functions of part of the protocol layers being centrally controlled in the CU, and the rest of the protocol layers being distributed in the DU, which is centrally controlled by the CU. Further, the centralized unit CU can also be divided into a control plane (CU-CP) and a user plane (CU-UP). In different systems, the CU (including CU-CP or CU-UP), or the DU can also have different names, for example, in an open radio access network (O-RAN) system, the CU can also be referred to as an O-CU (open CU), the DU can also be referred to as an O-DU, the CU-CP can also be referred to as an O-CU-CP, and the CU-UP can also be referred to as an O-CU-UP.

[0062] NWDAF network element: with functions of data collection, model training, data analysis, model inference, etc., which can be used to collect relevant data from network function network elements, third-party service servers, terminal devices or network management systems (such as OAM), make data analysis or model training based on relevant data, and provide data analysis results to network function network elements, third-party service servers, terminal devices or network management systems, or provide trained models to other data analysis function network elements. Network data analysis function network elements can be divided into analysis logic function and model training logic function according to functions. Among them, the analysis logic function is a logical function in the network data analysis function network element, which is used to perform model inference, derive analysis results (i.e. derive statistical or predicted analysis results according to the request of analysis consumer), and open analysis results. The model training logic function is a logical function in the network data analysis function network element, which is used to train models and open training services (such as providing trained models). A network data analysis function network element may only contain analysis logic function or only contain model training logic function, or may contain both analysis logic function and model training logic function, which is not limited in the embodiments of the present application.

[0063] AMF network element: mainly responsible for access authentication of terminal devices, mobility management, signaling interaction between various function network elements, termination of non-access layer (NAS) layer signaling security, etc. Such as: management of user registration state, reachability state, N1 / N2 interface signaling transmission, access authentication and authorization, user connection state, user registration into network, tracking area update, cell handover user authentication, key security, etc.

[0064] SMF network element: mainly provides session management of terminal device session (such as session establishment, modification and release), internet protocol (IP) address allocation and management, and selection and control of user plane network element, etc.

[0065] UPF network element: responsible for packet routing and forwarding, policy implementation, traffic reporting, quality of service (QoS) processing, etc.

[0066] UDM network element: manages user subscription, access authorization, authentication information generation, etc.

[0067] NRF network element: provides registration and discovery capabilities of network elements in the network.

[0068] PCF network element: mainly responsible for generating terminal device access policy and quality of service flow control policy, and can also provide generated policy to access and mobility management function network element or session management function network element, etc.

[0069] OAM: mainly complete daily network and service analysis, prediction, planning and configuration, and test and fault management of network and its service, etc. OAM can interact with RAN to obtain UE location information measured by RAN or reported by UE.

[0070] AF network element: mainly provides an intermediate function entity for interaction between application server in data network (DN) and network element in core network, and transmits demand of application side to network side (such as quality of service demand or user state event subscription, etc.), so that the application server can realize dynamic control of network quality of service and charging, obtain running information of certain network element in core network, etc. In the embodiments of the present application, the application function network element can be a function entity deployed by an operator, that is, a trusted AF, or a function entity deployed by a service provider, which can be a third-party service provider (corresponding to an untrusted AF), or an internal service provider of the operator (corresponding to a trusted AF), without limitation.

[0071] NEF network element: mainly responsible for providing network capabilities and event exposure to external access entities (such as untrusted AF network elements), and receiving related external information (such as receiving information provided by untrusted AF network elements).

[0072] As can be seen from FIG. 1, the interfaces between the various control plane network elements in FIG. 1 are service interfaces.

[0073] For example, Nnef, Nnrf, Nnwdaf, Namf, Npcf, Nsmf and Nudm in FIG. 1 are service interfaces provided by the above-mentioned NEF, NRF, NWDAF, AMF, PCF, SMF and UDM, respectively, for invoking corresponding service operations. N1, N2, N3, N4, N6 and N9 are interface serial numbers. The meanings of these interface serial numbers can be referred to the meanings defined in the 3GPP standard protocol, which are not limited here.

[0074] Service enables the 5G core network to form a flat architecture, and through the signaling bus of the control plane, the control plane network function entities of the same network slice can discover each other through the NRF network element, obtain the access address information of the other party, and then directly communicate with each other through the control plane signaling bus.

[0075] It should be noted that the interfaces between the various control plane network elements in FIG. 1 can also be point-to-point interfaces, which are not described here.

[0076] It can be understood that the above-mentioned network elements or functions can be network elements in hardware devices, or software functions running on special hardware, or virtualized functions instantiated on a platform (such as a cloud platform).

[0077] The above "network element" can also be referred to as "functional network element", "functional entity", "entity", "node", "device" or "apparatus", etc., and the present application does not make any limitation. In actual deployment, network elements can be combined, and when two network elements are combined, the interaction between the two network elements provided by the embodiments of the present application becomes internal operation of the combined network element or can be omitted.

[0078] For the convenience of description, hereinafter, the access and mobility management function network element is taken as an AMF network element, and the session management function network element is taken as an SMF network element for example. Further, the AMF network element is simply referred to as AMF, and the SMF network element is simply referred to as SMF. That is, the AMF described hereinafter can be replaced by an access and mobility management function network element, and the SMF can be replaced by a session management function network element.

[0079] It should be noted that the names of the various network elements and communication interfaces between the network elements involved in FIG. 1 are simply described by taking the current protocol as an example, but the embodiments of the present application are not limited to only being applicable to the currently known communication system. Therefore, the standard names appearing when described by taking the current protocol as an example are all functional descriptions, and the specific names of the network elements, interfaces or signaling are not limited by the present application, and only the functions of the network elements, interfaces or signaling are indicated, which can be extended to other systems, such as 5G or future communication systems.

[0080] In addition, it should also be noted that in some network architectures, the network function network element entities such as the AMF network element, the SMF network element, the PCF network element, the AF network element and the UDM network element are all referred to as network function (network function, NF) network elements; or in other network architectures, the set of network elements such as the AMF network element, the SMF network element, the PCF network element, the AF network element and the UDM network element can be referred to as a control plane function network element.

[0081] FIG. 1 is a communication system to which the embodiments of the present application are applicable. In recent years, on the basis of the communication system shown in FIG. 1, unmanned aerial vehicles (uncrewed aerial vehicle, UAV) as a kind of terminal equipment are applied more and more popularly, for example, in the civil field, from small unmanned aerial vehicles for personal entertainment to various unmanned aerial vehicles with economic value (such as plant protection unmanned aerial vehicles, disaster relief unmanned aerial vehicles, fire fighting unmanned aerial vehicles, express delivery unmanned aerial vehicles) and the like, which are various.

[0082] In addition, the unmanned aerial vehicle can also provide temporary communication services, that is, the unmanned aerial vehicle is loaded with a wireless access node, which is commonly used in major events such as live broadcast of football matches, or emergency events such as earthquake and tsunami scenes. The current 3GPP is discussing the related issues of UAV networking, which can solve the problems of identification, authorization and tracking when remotely controlling the UAV.

[0083] In a possible manner, a UAV system service supplier (USS) provides services for safe and efficient use of airspace by UAVs, is responsible for authentication and authorization of UAVs, authentication and authorization of command and control (C2) communication, identification and tracking of UAVs, and the like. The UAV is a kind of UE, and can also be referred to as a UE. The UAS is an uncrewed aerial system (UAS).

[0084] For ease of understanding, the following describes the UAV, the USS, the UAS, and the like in combination with FIG. 2.

[0085] As an example, FIG. 2 shows a schematic diagram of an architecture of another communication system to which embodiments of the present application are applicable, and is also a schematic diagram of a logical architecture of a UAV in a 5G system and a 4G system. The network architecture can include, but is not limited to, the following network elements (or referred to as functional network elements, functional entities, nodes, devices, and the like):

[0086] The UAV (i.e., the UE), the 4G access network ((R)AN), the 5G access network NG-RAN, the 5G core (5G core, 5GC), the 4G core network (evolved packet core, EPC), the USS, the UAS network function (UAS network function, UAS NF), the DN, and the third party authorized entity (third party authorized entity, TPAE).

[0087] The following briefly describes the related network elements or devices shown in FIG. 2:

[0088] 1. UAV: a drone, which can also be referred to as an unmanned aircraft or an aerial robot, is an unmanned aircraft that can complete aerial flight tasks and various load tasks under unmanned conditions by using radio remote control equipment and self-provided program control devices. The drone in embodiments of the present application can be an unmanned helicopter, a fixed-wing aircraft, a multi-rotor aircraft, an unmanned airship, an unmanned parafoil aircraft, and the like. The drone can also include near-space aircraft such as stratospheric airships, high-altitude balloons, and solar-powered drones. The drone can also be a multi-form unmanned aircraft such as a four-axis, six-axis, single-axis, and vector control unmanned aircraft. The drone in embodiments of the present application can be used in the fields of industry, civil use, agriculture, construction, film and television, environmental protection, and the like, and in special industries using the drone for operation, for example, for patrol, aerial photography, environmental monitoring, border control, express delivery, power inspection, right confirmation, flood control and drought resistance, post-disaster rescue, and the like. The drone can also be regarded as a kind of UE type device. Embodiments of the present application do not limit the name and form of the drone.

[0089] It should be understood that the specific type of UAV is not limited herein. With the development of intelligence, the name of the device with the function of unmanned aerial vehicle may be different for application in different scenarios or completion of different aerial flight tasks. For the convenience of description, the above-mentioned device with the function of unmanned aerial vehicle is collectively referred to as UAV in all embodiments of the present application.

[0090] 2、UAS: UAV aviation system, which can include one or more UAV controllers (UAVC) and one or more UAVs. For example, one UAV controller can control one or more UAVs, one UAV can be controlled by one or more UAV controllers, and multiple UAV controllers can cooperatively control multiple UAVs, and the embodiments of the present application do not limit this.

[0091] 3、USS: UAV system service provider, which provides services to the operator or pilot of the UAV to meet the operation requirements of the UAV, and provides support for safe and efficient use of airspace. The USS can provide any functional subset to meet the business objectives of the provider, for example, the USS can be responsible for functions such as authentication and authorization of UAVs, authentication and authorization of C2 communication, identification and tracking of UAVs, etc.

[0092] It should be noted that the naming of USS is only for the convenience of representing its function, and should not constitute any limitation on the present application, and the present application does not exclude the possibility of using other names in future standards.

[0093] 4、UTM: UAS Traffic Management, UAV aviation driving system traffic management, UTM is a system that can safely and effectively integrate UAVs in flight with other airspace users, and is a set of functions and services for managing a series of automatic device operations (such as UAV authentication, UAV service authorization, UAV policy management, airspace UAV traffic control, etc.). The USS and UTM can be the same network element or entity, and can be in a containing or contained relationship, or in a parallel relationship, and the present application does not limit this. In the embodiments of the present application, USS, UTM, USS / UTM refer to the same network element or the same entity, which can be a server, an application server, or a service entity, etc.

[0094] 5. UAS NF: The UAS network function is supported by the NEF, which is used for the USS to expose services externally. The UAS NF uses the existing NEF service exposure service (interface Nnef in FIG. 1) for drone authentication / authorization, drone flight authorization, drone-drone pairing authorization, and related re-authentication / re-authorization and revocation; for location reporting, state monitoring, obtaining a list of aerial terminals in a geographic area, and QoS / traffic filtering control for C2 communication.

[0095] In addition, a dedicated NEF can also be deployed, which can provide UAS NF functions, that is, support UAS-specific features / application programming interfaces (APIs) and NEF-specific features / APIs, for providing capability exposure services to the USS, etc. In the embodiments of the present application, UAS NF, NEF, UAS NF / NEF refer to the same network element or the same entity, and the name thereof can be a network function entity, etc.

[0096] 6. TPAE: Third-party authorization entity, which can identify and / or track UAVs and check whether there are illegal UAVs within a certain range.

[0097] As shown in FIG. 2, taking the 5G system as an example, the USS can communicate with the 5GC through the UAS NF / NEF on the one hand, and can also connect the UPF through the N6 interface to transmit data on the other hand.

[0098] FIG. 3 shows a schematic diagram of an application scenario applicable to the embodiments of the present application. As an example, as shown in FIG. 3, the drone can fly from the service area #1 responsible by the USS #1 to the service area #2 responsible by the USS #2, and accordingly, the USS providing services for the drone is also switched from the USS #1 to the USS #2.

[0099] In the scenario where the USS providing services for the drone is switched from the source USS (i.e., the USS #1) to the target USS (i.e., the USS #2), how to discover the target USS and then create a connection between the drone and the target server to ensure the continuity of the flight service of the drone becomes a technical problem to be solved.

[0100] In view of the above problems, the present application proposes a communication method, which is applied in the scenario where the drone is switched from the source server to the target server. The first device can obtain the information of the target server and then send it to other devices, which is used to create a connection between the drone and the target server, thereby ensuring the continuity of the flight service of the drone.

[0101] The interaction process between the network elements / devices in the communication system will be specifically introduced below by a method embodiment in combination with FIG. 4. The information transmission method provided by the embodiments of the present application can be applied to the communication systems shown in FIG. 1 and FIG. 2.

[0102] FIG. 4 is a flowchart of an information transmission method according to an embodiment of the present application.

[0103] S401, the source server acquires information of a target server, and the information of the target server is used to create a connection between the UAV and the target server.

[0104] It should be understood that the source server can be a server of a source UAV system service provider, and correspondingly, the target server is a server of a target UAV system service provider.

[0105] It should be understood that the information of the target server includes identification information or address information of the target server.

[0106] In a possible implementation, the source server acquires the information of the target server, including: the source server acquires the information of the target server according to the location information of the UAV and configuration information on the source server, and the configuration information includes a mapping relationship between the location information of the UAV and the information of the target server.

[0107] In a possible implementation, the source server acquires the information of the target server, including: the source server sends a first request to the second device, the first request is used to request the information of the target server, and the first request includes the location information of the UAV; and the first device receives the information of the target server from the second device.

[0108] S402, the source server sends the information of the target server to a first network device.

[0109] It should be understood that the first network device is one or more of the following network elements: an access and mobility management function network element, a session management function network element, a UAV air system network function network element, and a network exposure function network element.

[0110] In a possible implementation, the source server sends the information of the target server to the first network device, including: the source server sends the information of the target server and first indication information to the first network device, and the first indication information is used to indicate that the UAV switches from the source server to the target server.

[0111] In a possible implementation, the source server sends the information of the target server to the first network device, including: the source server sends the information of the target server and second indication information to the first network device, and the first indication information is used to indicate that the UAV switches from the source server to the target server.

[0112] In a possible implementation, the information sent by the source server to the first network device further comprises a current authentication result with the source server, such as success or failure. The failed authentication result can be used to indicate that the current authentication result of the UAV with the source server fails, and can trigger the UAV to initiate the authentication and authorization process again.

[0113] S403, the source server sends the information of the target server to the UAV. Specifically, there can be two optional paths as follows:

[0114] a) Network layer path: the source server sends the information of the target server to the first network device, and then the first network device further sends the information of the target server to the UAV through network service operation and / or network message.

[0115] It should be understood that the step of sending the information of the target server to the first network device by the source server is step S402, or can be a new step independent of step S402, and the present application does not make any limitation in the embodiments.

[0116] In a possible implementation, the first network device can send the information of the target server to the UAV through network service operation and / or network message of other intermediate network devices.

[0117] b) Application layer path: the source server sends the information of the target server to the UAV through application layer service operation and / or application layer message.

[0118] In a possible implementation, the source server sends the information of the target server to the UAV, including: the source server sends the information of the target server to the UAV and first indication information, the first indication information being used to instruct the UAV to switch from the source server to the target server.

[0119] In a possible implementation, the source server sends the information of the target server to the UAV, including: the source server sends the information of the target server to the UAV and second indication information, the first indication information being used to instruct the UAV to switch from the source server to the target server.

[0120] In path a) or b), the information of the target server can be address information of the target server and / or a UAV identifier allocated to the UAV by the target server.

[0121] It should be understood that in the embodiments of the present application shown in FIG. 4, the source server sends the information of the target server to the first network device and / or the UAV (and the first indication information, or / and, and the second indication information), so that one or more of the source server, the first network device and the UAV can create a connection between the UAV and the target server, and ensure that the service and management of the UAV are not interrupted.

[0122] FIG. 5 is a flow diagram of another information transmission method according to an embodiment of the present application.

[0123] S501, the first network device obtains information of a target server, the information of the target server being used for creating or indicating to create a connection between the UAV and the target server.

[0124] It should be understood that the first network device is one or more of the following network elements: an access and mobility management function network element, a session management function network element, a UAV air system network function network element, and a network exposure function network element.

[0125] It should be understood that the target server is a server of a target UAV system service provider.

[0126] In a possible implementation, the first network device obtains the information of the target server, including: the first network device obtains the information of the target server according to the location information of the UAV and configuration information on the first network device, the configuration information including a mapping relationship between the location information of the UAV and the information of the target server.

[0127] In a possible implementation, the first network device obtains the information of the target server, including: the first network device sends a first request to a second device, the first request being used for requesting the information of the target server, the first request including the location information of the UAV; and the first network device receives the information of the target server from the second device.

[0128] S502, the first network device sends the information of the target server to a source server.

[0129] It should be understood that the source server is a server of a source UAV system service provider.

[0130] In a possible implementation, the first network device sends the information of the target server to the source server, including: the first network device sends the information of the target server and first indication information to the source server, the first indication information being used for indicating the UAV to switch from the source server to the target server.

[0131] In a possible implementation, the first network device sends the information of the target server to the source server, including: the first network device sends the information of the target server and second indication information to the source server, the first indication information being used for indicating the UAV to switch from the source server to the target server.

[0132] S503, the first network device sends the information of the target server to the UAV. Specifically, there can be two optional paths as follows:

[0133] a) Network layer path: the first network device sends the information of the target server to the UAV through network service operation and / or network message.

[0134] In a possible implementation, the first network device can send the information of the target server to the UAV through network service operation and / or network message of other intermediate network device.

[0135] b) Application layer path: the first network device sends the information of the target server to the source server, and the source server sends the information of the target server to the UAV through application layer service operation and / or application layer message.

[0136] It should be understood that the step of sending the information of the target server to the source server by the first network device is step S502, or a new step independent of step S502, and the present application does not limit the embodiments.

[0137] In a possible implementation, the first network device sends the information of the target server to the UAV, including: the first network device sends the information of the target server and first indication information to the UAV, and the first indication information is used to instruct the UAV to switch from the source server to the target server.

[0138] In a possible implementation, the first network device sends the information of the target server to the UAV, including: the first network device sends the information of the target server and second indication information to the UAV, and the first indication information is used to instruct the UAV to switch from the source server to the target server.

[0139] It should be understood that in the embodiments of the present application shown in FIG. 5, the first network device sends the information of the target server (and the first indication information, or, and the second indication information) to the source server and / or the UAV, so that one or more of the source server, the first network device and the UAV can create a connection between the UAV and the target server, ensuring that the service and management of the UAV are not interrupted.

[0140] As a specific implementation of the embodiment shown in FIG. 4, FIG. 6 is a flowchart of a method for transmitting information according to an embodiment of the present application, which is provided in combination with the architecture shown in FIG. 1 and FIG. 2. Specifically, the UAV is UAV, the source server is Source USS (i.e., S-USS), the target server is Target USS (i.e., T-USS), the first network device is UAS NF / NEF, and the intermediate network device is AMF / SMF.

[0141] S601, the S-USS acquires information of the T-USS for the UAV, wherein the S-USS is a source USS serving the UAV, the T-USS is a target USS serving the UAV, and the information of the T-USS is used to create a connection between the UAV and the T-USS.

[0142] It should be understood that the S-USS can acquire the information of the T-USS when it is determined that the S-USS cannot serve or manage the UAV.

[0143] In a possible implementation, the S-USS determines that the S-USS cannot serve or manage the UAV, including that the S-USS determines that the S-USS cannot serve or manage the UAV according to that the UAV moves out of or is about to move out of a service area of the S-USS, or the S-USS determines that the S-USS cannot serve or manage the UAV according to that a load of the S-USS exceeds a certain threshold.

[0144] In a possible implementation, the information of the T-USS is a T-USSID and / or a T-USS Address (for example, an IP address, a port number, a protocol number, and the like of the T-USS).

[0145] In a possible implementation, the S-USS acquires the information of the T-USS for the UAV, including that the S-USS acquires the information of the target T-USS according to a relationship between service area information of a USS locally configured by the S-USS according to location information of the UAV and the information of the USS. Here, the USS includes the S-USS and the T-USS.

[0146] In a possible implementation, the S-USS acquires the information of the T-USS for the UAV, including that the S-USS sends a first request message to a second device, the first request message is used to request the information of the T-USS, wherein the first request message includes the location information of the UAV, and then the S-USS receives the information of the T-USS from the second device.

[0147] It should be understood that the second device can be a network repository function (NRF) network element of a 5GS or a third-party domain name server (DNS) that manages a domain used for USS addressing.

[0148] It should be understood that the location information of the UAV can include one or more of the following information: a cell identity (Cell ID) or a cell identity list (Cell ID list) or a tracking area identity (TAI) of the UAV, whether the UAV is in an area of interest, the area of interest can be set as a service area of each USS, or a tracking area identity list (TAI list) or global positioning system (GPS) location information, etc. It should be noted that the location information of the UAV or the location information of the UAV involved in other places of the embodiments of the present application can refer to the description of the location information of the UAV herein, and will not be repeated.

[0149] In a possible implementation, before the S-USS obtains the information of the T-USS for the UAV, the S-USS obtains the location information of the UAV. It should be understood that the S-USS can obtain the location information of the UAV from the UAV through an application layer, or the S-USS triggers a positioning process of the UAV to obtain the location information of the UAV, or the S-USS subscribes to the AMF through the UAS NF / NEF to obtain the location information of the UAV.

[0150] S602, the S-USS sends the context information of the UAV to the T-USS.

[0151] It should be understood that the S-USS sends the context information of the UAV to the T-USS according to the information of the T-USS.

[0152] In a possible implementation, the context information of the UAV includes one or more of the following information: identification information of the UAV, location information of the UAV, open network element NEF information of the UAV, and authentication result of the UAV.

[0153] It should be understood that the identification information of the UAV includes one or more of the following: an international mobile subscriber identity (IMSI) of the UAV, a subscription permanent identifier (SUPI) of the UAV, an international mobile equipment identity (IMEI) of the UAV, a permanent equipment identifier (PEI) of the UAV, a generic public subscription identifier (GPSI) of the UAV, and a civil aviation administration level UAV identification (CAA-Level UAV ID) of the UAV. It should be noted that the description of the identification information of the UAV or the identification information of the UAV in other places of the embodiments of the present application can be referred to the description of the identification information of the UAV herein, and will not be repeated.

[0154] Optionally, the S-USS can request the T-USS to allocate identification information of the UAV to the T-USS, and then send the identification information to the UAV through a network layer or an application layer path.

[0155] In S603, the S-USS sends a first notification message to the UAS NF / NEF, and the first notification message carries the identification of the UAV and the information of the T-USS.

[0156] It should be understood that the identification of the UAV and the information of the T-USS are used to create a connection between the UAV and the T-USS.

[0157] In a possible implementation, before sending the first notification message to the UAS NF / NEF, the S-USS receives a first subscription message from the UAS NF / NEF, and the first subscription message is used to subscribe to changed USS information corresponding to a change of a USS serving the UAV, or the first subscription message is used to subscribe to information of a USS serving the UAV, wherein the first subscription message includes identification information of the UAV.

[0158] It should be understood that if the first subscription message only includes the identification information of the UAV, the first notification message can only include the information of the T-USS serving the UAV.

[0159] S604, optionally, the UAS NF / NEF stores the information of the UAV and the T-USS.

[0160] It should be understood that the information of the UAV and the T-USS stored by the UAS NF / NEF is used to create the connection between the UAV and the T-USS.

[0161] In a possible implementation, the UAS NF / NEF stores the information of the UAV and the T-USS, including: the UAS NF / NEF stores or configures a mapping relationship between the information of the UAV and the T-USS.

[0162] S605a, the UAS NF / NEF sends the indication information to the UAV through the SMF / AMF network element, instructing the UAV to create the connection with the T-USS.

[0163] In a possible implementation, the indication information is the information of the T-USS. The information of the T-USS can be the identification information of the T-USS and / or the identification information allocated to the UAV by the T-USS.

[0164] In a possible implementation, as an alternative implementation, the indication information instructs the UAV to re-create the connection with the USS. It should be understood that in this case, the UAV is not aware of the switching behavior from the S-USS to the T-USS by the network side or the application provider.

[0165] In a possible implementation, the UAS NF / NEF sends the indication information to the UAV through the SMF / AMF network element, including: the UAS NF / NEF can first send the indication information to the SMF or the AMF through the service operation of the SMF or the AMF, and then the SMF or the AMF sends the indication information to the UAV through a non-access stratum (NAS) message.

[0166] S605b, the S-USS sends the indication information to the UAV through the application layer, instructing the UAV to create the connection with the T-USS.

[0167] In a possible implementation, the indication information is the information of the T-USS.

[0168] In a possible implementation, as an alternative implementation, the indication information instructs the UAV to re-create the connection with the USS. It should be understood that in this case, the UAV is not aware of the switching behavior from the S-USS to the T-USS by the network side or the application provider.

[0169] S606, the UAV sends a NAS message to the SMF / SMF for creating a connection between the UAV and the T-USS, wherein the NAS message includes an identity of the UAV.

[0170] S607, the UAV sends an authentication and authorization message to the UAS NF / NEF for creating a connection between the UAV and the T-USS, wherein the authentication and authorization message includes the identity of the UAV.

[0171] S608, the UAV NF / NEF obtains the T-USS serving the UAV according to the identity of the UAV.

[0172] In a possible implementation, the UAV NF / NEF determines the T-USS serving the UAV according to the identity of the UAV and a mapping relationship between the identity of the UAV and information of the T-USS configured or stored on the UAV NF / NEF.

[0173] S609, the UAV NF / NEF sends an authentication and authorization message to the T-USS for creating a connection between the UAV and the T-USS, wherein the NAS message includes the identity of the UAV.

[0174] At this point, the T-USS can create a connection between the UAV and the T-USS upon receiving the authentication and authorization message (including the identity of the UAV) from the UAV NF / NEF, and then serve or manage the UAV. In a possible implementation, the T-USS can confirm a default USS of the UAV through the identity of the UAV reported by the UAV, and the default USS can indicate a USS that allocates the identity of the UAV. The T-USS requests an authentication result of the UAV from the default USS, and optionally, carries the identity information of the UAV. The authentication result of the UAV can be success or failure. In another possible implementation, the T-USS can obtain the authentication result of the UAV by requesting the authentication result of the UAV from the S-USS or obtaining the context of the UAV from the S-USS.

[0175] It is worth noting that the execution of step S602 has the following two modes:

[0176] Mode one, the S-USS actively sends the context information of the UAV to the T-USS after determining the information of the T-USS serving the UAV;

[0177] Mode two, the T-USS requests the context information of the UAV from the S-USS after receiving the authentication and authorization message (including the identity of the UAV) from the UAS-NEF.

[0178] As an optional implementation of the second approach, the T-USS obtains the information (ID or Address) of the S-USS from the UAS NF / NEF or the S-USS or the second device.

[0179] It should be understood that in the step S603, the step S605a or the step S605b, an indicator 1 for indicating the switching of the UAV from the S-USS to the T-USS or an indicator 2 for indicating the creation of the connection between the UAV and the T-USS can also be included.

[0180] It should be understood that in the embodiments of the present application shown in FIG. 6, the S-USS sends the information of the T-USS (and the indicator 1, or, and the indicator 2) to the UAS NF / NEF and / or the UAV, so that one or more of the S-USS, the UAS NF / NEF and the UAV can create the connection between the UAV and the T-USS, ensuring that the service and management of the UAV are not interrupted.

[0181] As a specific implementation of the embodiment shown in FIG. 5, FIG. 7 is a flowchart of a fourth information transmission method according to an embodiment of the present application, which is provided in combination with the architecture shown in FIG. 1 and FIG. 2. Specifically, the UAV is a UAV, the source server is a Source USS (i.e., S-USS), the target server is a Target USS (i.e., T-USS), the first network device is a UAS NF / NEF, and the intermediate network device is an AMF / SMF.

[0182] In the step S701, the UAS NF / NEF obtains the information of the T-USS for the UAV, wherein the T-USS is a target USS serving the UAV, and the information of the T-USS is used to create a connection between the UAV and the T-USS.

[0183] It should be understood that the UAS NF / NEF can obtain the information of the T-USS when it is determined that the S-USS cannot provide service or management for the UAV.

[0184] In a possible implementation, the UAS NF / NEF determines that the S-USS cannot provide service or management for the UAV, including: the UAS NF / NEF determines that the S-USS cannot provide service or management for the UAV according to the UAV moving out of or about to move out of the service area of the S-USS, or the UAS NF / NEF determines that the S-USS cannot provide service or management for the UAV according to the load of the S-USS exceeding a certain threshold.

[0185] In a possible implementation, the UAS NF / NEF configures a mapping relationship between information (ID or Address) of the USS and a service area of the USS. It should be understood that the USS herein includes the S-USS and the T-USS.

[0186] In a possible implementation, the UAS NF / NEF sends a second subscription message to the USS or a network repository function (NRF), where the second subscription message is used to subscribe to load information of the USS; and the UAS NF / NEF receives a second response message from the USS or the NRF, where the second response message includes the load information of the USS. It should be understood that the USS herein includes the S-USS and the T-USS.

[0187] In a possible implementation, the UAS NF / NEF obtains information of the T-USS for the UAV, including that the UAS NF / NEF obtains information of a target T-USS according to location information of the UAV and a relationship between area information of the USS and information of the USS that is locally configured. It should be understood that the USS herein includes the S-USS and the T-USS.

[0188] In a possible implementation, the UAS NF / NEF obtains information of the T-USS for the UAV, including that the UAS NF / NEF sends a first request message to a second device, where the first request message is used to request information of the T-USS, and the first request message includes location information of the UAV, and then the UAS NF / NEF receives the information of the T-USS from the second device.

[0189] It should be understood that the second device can be a network repository function (NRF) network element of the 5GS or a third-party domain name server (DNS) that manages a domain for addressing the USS.

[0190] In a possible implementation, before the UAS NF / NEF obtains information of the T-USS for the UAV, the S-USS obtains location information of the UAV. It should be understood that the UAS NF / NEF can obtain the location information of the UAV from the UAV through an application layer between the S-USS and the UAV, or the UAS NF / NEF triggers a positioning procedure of the UAV to obtain the location information of the UAV, or the S-USS subscribes to the AMF to obtain the location information of the UAV.

[0191] S702, the UAS NF / NEF sends a second notification message to the S-USS, where the second notification message carries an identifier of the UAV and information of the T-USS.

[0192] It should be understood that the identity of the UAV and the information of the T-USS are used to create a connection between the UAV and the T-USS.

[0193] In a possible implementation, before sending the second notification message to the S-USS, the UAS NF / NEF receives a second subscription message from the S-USS, the second subscription message is used to subscribe to changed USS information corresponding to a change of a USS serving the UAV, or the second subscription message is used to subscribe to information of a USS serving the UAV, wherein the second subscription message comprises identity information of the UAV.

[0194] It should be understood that if the second subscription message only comprises identity information corresponding to one UAV, the second notification message can only comprise information of a T-USS serving the UAV.

[0195] S703, the S-USS sends context information of the UAV to the T-USS.

[0196] It should be understood that the S-USS sends the context information of the UAV to the T-USS according to the information of the T-USS.

[0197] In a possible implementation, the context information of the UAV comprises one or more of the following: identity information of the UAV, location information of the UAV, open network element NEF information of the UAV, and authentication result of the UAV.

[0198] S704a, the UAS NF / NEF sends indication information to the UAV through an SMF / AMF network element, instructing the UAV to create a connection with the T-USS.

[0199] In a possible implementation, the indication information is information of the T-USS. The information of the T-USS can be identity information of the T-USS and / or identity information allocated to the UAV by the T-USS.

[0200] In a possible implementation, as an alternative implementation, the indication information instructs the UAV to re-create a connection with the USS. It should be understood that in this case, the UAV is unaware of the switching behavior from the S-USS to the T-USS by the network side or the application provider.

[0201] In a possible implementation, the UAS NF / NEF sends the indication information to the UAV through an SMF / AMF network element, comprising: the UAS NF / NEF can first send the indication information to the SMF or the AMF through a service operation of the SMF or the AMF, and then the SMF or the AMF sends the indication information to the UAV through a non-access stratum (NAS) message.

[0202] S704b, the S-USS sends indication information to the UAV through the application layer, instructing the UAV to create a connection between the UAV and the T-USS.

[0203] In a possible implementation, the indication information is information of the T-USS. The information of the T-USS can be identification information of the T-USS and / or identification information allocated to the UAV by the T-USS.

[0204] In a possible implementation, as an alternative implementation, the indication information instructs the UAV to re-create a connection between the UAV and the USS. It should be understood that, in this case, the UAV is not aware of the switching behavior of the network side or the application provider from the S-USS to the T-USS.

[0205] S705-S708, same as steps S606-S609 in the embodiment flowchart of FIG. 6, and will not be described again.

[0206] So far, the T-USS can create a connection between the UAV and the T-USS in the case of receiving an authentication authorization message (including the identification of the UAV) from the UAV NF / NEF, and then serve or manage the UAV by the T-USS.

[0207] It should be noted that, the execution of step S703 has the following two modes:

[0208] Mode one, the S-USS actively sends the context information of the UAV to the T-USS after determining the information of the T-USS serving the UAV;

[0209] Mode two, the T-USS requests the S-USS to obtain the context information of the UAV after receiving the authentication authorization message (including the identification of the UAV) from the UAS-NEF.

[0210] As an optional implementation of mode two, the T-USS obtains the information (ID or Address) of the S-USS from the UAS NF / NEF or the S-USS or the second device.

[0211] It should be understood that, in step S702, step S704a or step S704b, indicator 1 for instructing the UAV to switch from the S-USS to the T-USS or indicator 2 for instructing to create a connection between the UAV and the T-USS can also be included.

[0212] It should be understood that in the embodiment of this application shown in Figure 7, the UAS NF / NEF sends information about the T-USS (and indicator 1, or indicator 2) to the S-USS and / or UAV, so that one or more of the S-USS, UAS NF / NEF and UAV can create a connection between the UAV and the T-USS, ensuring that the service and management of the UAV are not interrupted.

[0213] It should be understood that the scenario described in this invention is a situation where a drone switches from a source server to a target server. The existing technology presented in this invention can also be used for a drone's initial connection to a server, where the server may be the drone's default server but not the serving server corresponding to the drone's current service area. The default server can be the server that assigns the drone identifier to the drone. In one possible implementation, the drone can initially connect to the default server, which determines the serving server corresponding to the drone's current service area and initiates a server switch for the drone. In another possible implementation, when a drone's creation request reaches the UAS NF / NEF, the UAS NF / NEF can determine the serving server corresponding to the drone's current service area using the method mentioned in this invention and send the drone's creation / authentication request to the serving server corresponding to the drone's current service area. Specific method details are the same as above and will not be elaborated further.

[0214] The above mainly describes the solutions provided by the embodiments of this application from the perspective of interaction between various network elements. Correspondingly, the embodiments of this application also provide a communication device for implementing the various methods described above. This communication device can be the source server in the above method embodiments, or a device containing the source server, or a component usable in the source server device; or, the communication device can be the first network device in the above method embodiments, or a device containing the first network device, or a component usable in the first network device. It is understood that, in order to achieve the above functions, the communication device includes hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art should readily recognize that, in conjunction with the units and algorithm steps of the various examples described in the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed by hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0215] The embodiments of the present application can divide the functional modules of the communication device according to the method embodiments, for example, each functional module can be divided according to each function, or two or more functions can be integrated in one processing module. The integrated module can be realized in the form of hardware or in the form of a software functional module. It should be noted that the division of the modules in the embodiments of the present application is illustrative, and is only a logical functional division. In actual implementation, another division manner can be used.

[0216] Taking the communication device as the source server or the first network device in the method embodiments, FIG. 8 is a structural schematic diagram of a communication device provided by the embodiments of the present application. As shown in FIG. 8, the communication device 800 includes a processing module 801 and a transceiver module 802. The processing module 801 is configured to perform the processing functions of the source server or the first network device in the method embodiments. The transceiver module 802 is configured to perform the transceiving functions of the source server or the first network device in the method embodiments.

[0217] The above method embodiments involve all related contents of each step, which can be referred to the function description of the corresponding functional module, and will not be repeated here.

[0218] Since the communication device 800 provided by the embodiments can perform the above information transmission method, the technical effects that can be obtained are referable to the above method embodiments, and will not be repeated here.

[0219] In a possible design, the transceiver module 802 can include a receiving module and a sending module (not shown in FIG. 8). The transceiver module is configured to implement the sending function and the receiving function of the communication device 800.

[0220] In a possible design, the communication device 800 can further include a storage module (not shown in FIG. 8), which stores programs or instructions. When the processing module 801 executes the programs or instructions, the communication device 800 can perform the functions of the source server or the first network device in any method shown in FIGS. 4-7.

[0221] It should be understood that the processing module 801 involved in the communication device 800 can be realized by a processor or a processor-related circuit component, and can be a processor or a processing unit. The transceiver module 802 can be realized by a transceiver or a transceiver-related circuit component, and can be a transceiver or a transceiving unit.

[0222] Exemplarily, FIG. 9 is a structural schematic diagram of another communication apparatus provided by the embodiments of the present application. The communication apparatus can be a source server or a first network device, or a chip (system) or other components or assemblies that can be arranged in the source server or the first network device. As shown in FIG. 9, the communication apparatus 900 can include a processor 901. In a possible design, the communication apparatus 900 can further include a memory 902 and / or a transceiver 903. The processor 901 is coupled with the memory 902 and the transceiver 903, for example, through a communication bus.

[0223] The components of the communication apparatus 900 will be described in detail below in combination with FIG. 9.

[0224] The processor 901 is the control center of the communication apparatus 900, which can be one processor or collectively refer to multiple processing elements. For example, the processor 901 can be one or more central processing units (CPUs), application specific integrated circuits (ASICs), or one or more integrated circuits configured to implement one or more of the embodiments of the present application, such as one or more digital signal processors (DSPs), or one or more field programmable gate arrays (FPGAs).

[0225] In a possible design, the processor 901 can perform various functions of the communication apparatus 900 by running or executing software programs stored in the memory 902 and calling data stored in the memory 902.

[0226] In a specific implementation, as an example, the processor 901 can include one or more CPUs, for example, CPU0 and CPU1 shown in FIG. 9.

[0227] In a specific implementation, as an example, the communication apparatus 900 can also include multiple processors, for example, the processor 901 and the processor 904 shown in FIG. 9. Each of the processors can be a single-CPU or a multi-CPU. The processor herein can refer to one or more devices, circuits, and / or processing cores for processing data (for example, computer program instructions).

[0228] The memory 902 is configured to store software programs for implementing the solutions of the present application, and the processor 901 controls the execution. The specific implementation manner can refer to the above method embodiments, which will not be described herein again.

[0229] In a possible design, the memory 902 can be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (RAM) or other type of dynamic storage device that can store information and instructions, an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disk storage, an optical disk storage (including a compact disc, a laser disc, an optical disc, a digital versatile disc, a Blu-ray disc, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited to this. The memory 902 can be integrated with the processor 901, or exist independently and be coupled to the processor 901, and the embodiments of the present application do not make a specific limitation in this regard.

[0230] The transceiver 903 is configured to communicate with other communication devices. For example, the communication device 900 is a source server, and the transceiver 903 can be configured to communicate with a first network device, or a drone, etc. For another example, the communication device 900 is a first network device, and the transceiver 903 can be configured to communicate with a source server, or a drone, etc.

[0231] In a possible design, the transceiver 903 can include a receiver and a transmitter (not shown in FIG. 9). The receiver is configured to implement the receiving function, and the transmitter is configured to implement the transmitting function.

[0232] In a possible design, the transceiver 903 can be an input / output interface or an interface circuit, configured to input and / or output a signal.

[0233] In a possible design, the transceiver 903 can be integrated with the processor 901, or exist independently and be coupled to the processor 901, and the embodiments of the present application do not make a specific limitation in this regard.

[0234] It should be noted that the structure of the communication device 900 shown in FIG. 9 does not constitute a limitation on the communication device, and the actual communication device can include more or fewer components than those shown, or combine certain components, or have a different arrangement of components.

[0235] In addition, the communication apparatus 900 can perform the information transmission method described above, and thus the technical effects that can be achieved by the communication apparatus 900 can refer to the technical effects of the method embodiments described above, which will not be described herein again.

[0236] In a possible implementation, the embodiments of the present application further provide a computer readable storage medium, which stores a computer program or instructions, and the computer program or instructions, when executed by a computer, implement the functions of the method embodiments described above.

[0237] In a possible implementation, the embodiments of the present application further provide a computer program product, which, when executed by a computer, implements the functions of the method embodiments described above.

[0238] In a possible implementation, the embodiments of the present application further provide a communication system, which includes the first network element and the second network element described in the method embodiments described above.

[0239] In a possible implementation, the communication system further includes the third network element described in the method embodiments described above.

[0240] In a possible implementation, the embodiments of the present application further provide a communication method, which includes the method described in any of the method embodiments described above or any implementation thereof.

[0241] In the embodiments described above, all or part of the embodiments can be implemented by software, hardware, firmware, or any combination thereof. When implemented by software, all or part of the embodiments can be implemented in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions according to the embodiments of the present application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center through a wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) manner. The computer readable storage medium can be any available medium that can be accessed by a computer or data storage device such as one or more servers, data centers, etc. that can be integrated with the medium. The available medium can be a magnetic medium (such as a floppy disk, a hard disk, a magnetic tape), an optical medium, or a semiconductor medium (such as a solid state drive (SSD)), etc.

[0242] Those skilled in the art can clearly understand that the units and algorithm steps of each example described in combination with the embodiments disclosed herein can be realized by electronic hardware or a combination of computer software and electronic hardware. Whether the functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the present application.

[0243] Those skilled in the art can clearly understand that, for the convenience and brevity of the description, the specific working processes of the above-described system, device and unit can refer to the corresponding processes in the foregoing method embodiments, which will not be repeated here.

[0244] In several embodiments provided in the present application, it should be understood that the disclosed system, device and method can be implemented in other ways. For example, the above-described device embodiments are only schematic, for example, the division of the units is only a logical function division, and actual implementation can have another division manner, for example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the units shown or discussed can be indirect coupling or communication connection through some interface, device or unit, and can be electrical, mechanical or other forms.

[0245] The units described as separate components can or can not be physically separated, and the components shown as units can or can not be physical units, that is, they can be located in one place, or can be distributed on a plurality of network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the embodiment.

[0246] In addition, each functional unit in each embodiment of the present application can be integrated into a processing unit, or each unit can exist physically independently, or two or more units can be integrated into one unit.

[0247] If the functions are implemented in the form of software function units and sold or used as independent products, they can be stored in a computer readable storage medium. Based on this understanding, the technical solutions of the present application essentially or the parts that contribute to the prior art or parts of the technical solutions can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and various program code storage media.

[0248] Although the present application is described herein in conjunction with various embodiments, those skilled in the art, with the benefit of the drawings, the disclosure, and the appended claims, can understand and appreciate other variations of the disclosed embodiments that fall within the scope of the claimed application. In the claims, the word "comprising" does not exclude other components or steps, and the indefinite article "a" or "an" does not exclude a plurality. A single processor or other unit can implement several functions listed in the claims. Measures recited in mutually different dependent claims can be combined and can be realized by a combination of measures.

[0249] Although the present application is described in conjunction with specific features and embodiments thereof, it is evident that many alternatives, modifications and variations will be apparent to those skilled in the art in light of the foregoing description. Accordingly, it is intended to embrace all alternatives, modifications and variations that fall within the scope of the claims appended hereto. It will be apparent to those skilled in the art that various modifications and variations can be made to the present application without departing from the scope of the present application. Thus, it is intended to include within the scope of the present application all such modifications and variations as can reasonably and customarily fall within the scope of the appended claims and their equivalents.

Claims

1. A communication method, characterized in that, The method, applicable to scenarios where a drone switches from a source server to a target server, includes: The first device acquires information about the target server, and the information about the target server is used to create a connection between the drone and the target server. The first device sends information to the target server.

2. The method according to claim 1, characterized in that, The method further includes: The first device sends the target server information to the drone.

3. The method according to claim 1 or 2, characterized in that, The first device is the source server, and the first device sends information about the target server, including: The source server sends the target server's information to the first network device.

4. The method according to claim 2 or 3, characterized in that, The first device sends information about the target server to the drone, including: The source server sends the target server information to the drone via an application layer path or a network layer path.

5. The method according to claim 1 or 2, characterized in that, The first device is a first network device, and the first device sends information about the target server, including: The first network device sends the target server information to the source server.

6. The method according to claim 2 or 5, characterized in that, The first device sends information about the target server to the drone, including: The first network device sends the target server information to the drone via a network layer path; or... The first network device sends the target server information to the drone through the source server.

7. The method according to any one of claims 1 to 6, characterized in that, The first device obtains information about the target server, including: The first device obtains the target server information based on the location information of the drone and the configuration information on the first device. The configuration information includes the mapping relationship between the location information of the drone and the information of the target server.

8. The method according to any one of claims 1 to 6, characterized in that, The first device obtains information about the target server, including: The first device sends a first request to the second device. The first request is used to request information from the target server, and the first request includes the location information of the drone. The first device receives information from the target server from the second device.

9. The method according to any one of claims 1 to 8, characterized in that, The first device sends information to the target server, including: The first device sends information about the target server and first instruction information, the first instruction information being used to instruct the drone to switch from the source server to the target server.

10. The method according to any one of claims 1 to 8, characterized in that, The first device sends information to the target server, including: The first device sends information about the target server and second instruction information, the second instruction information being used to instruct the creation of a connection between the drone and the target server.

11. The method according to any one of claims 1-10, characterized in that, The first network device is one or more of the following network elements: Access and Mobility Management Function (AMF) network element, Session Management Function (SMF) network element, Unmanned Aerial Vehicle System Network Function (UAS) NF network element, and Network Open Function (NEF) network element.

12. A communication device, characterized in that, The communication device includes a module or unit for performing the method according to any one of claims 1-11.

13. A communication device, characterized in that, The communication device includes a processor configured to cause the communication device to perform the method according to any one of claims 1-11 by means of logic circuits and / or executing instructions.

14. The communication device according to claim 13, characterized in that, The communication device further includes a memory for storing the instructions.

15. The communication device according to claim 13 or 14, characterized in that, The communication device further includes a communication interface for inputting and / or outputting signaling and / or data.

16. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes instructions that, when executed by a processor, cause the method according to any one of claims 1-11 to be implemented.

17. A computer program product, characterized in that, The computer program product includes instructions that, when executed on a computer, cause the computer to perform the method according to any one of claims 1-11.

Images