Route reporting method and device

Abstract

[Solution] An embodiment of the present disclosure discloses a route reporting method and apparatus applicable to the communication technology field, the method being performed by a terminal device and including the step of reporting flight route information to a network side device in response to satisfying a trigger condition, thereby supporting the terminal device to report flight route information, improving the reliability of mobility configuration, and avoiding cell switching failures.

Description

[Technical Field]

[0001] The present disclosure relates to the field of communications technology, and more particularly to a route reporting method and apparatus. [Background technology]

[0002] In recent years, there has been a surge in global attention on UAV (Unmanned Aerial Vehicle, or drone)-based services, including diverse drone operations, personal entertainment for flight experiences, cargo delivery, etc. As the foundation of these services, remote control and data transmission capabilities are key aspects of their enhancement.

[0003] In the related art, a UAV terminal device can fly along a fixed flight path, and considering that mobility enhancement is possible when the flight path of the terminal device is fixed, a network side device can perform mobility management based on the flight path information of the terminal device. However, at present, there is a lack of a method for the terminal device to report flight path information, which is a problem that needs to be solved urgently. Summary of the Invention [Problem to be solved by the invention]

[0004] An embodiment of the present disclosure provides a route reporting method and apparatus, which supports a terminal device to report flight route information, which can improve the reliability of mobility configuration and avoid cell switching failures. [Means for solving the problem]

[0005] In a first aspect, an embodiment of the present disclosure provides a route reporting method, the method being executed by a terminal device, the method including reporting flight route information to a network side device in response to satisfying a trigger condition.

[0006] In this technical solution, the terminal device reports flight path information to the network side device in response to meeting a trigger condition, thereby supporting the terminal device to report flight path information, improving the reliability of mobility configuration, and avoiding cell switching failure.

[0007] In a second aspect, an embodiment of the present disclosure provides another route reporting method, the method being performed by a network side device, the method including receiving flight route information reported by a terminal device when a trigger condition is satisfied.

[0008] In a third aspect, an embodiment of the present disclosure provides a communication device, which implements part or all of the functions of the terminal device of the method according to the first aspect. For example, the functions of the communication device may include part or all of the functions of the embodiments of the present disclosure, or may include the function of independently implementing any embodiment of the present disclosure. The functions may be implemented by hardware, or may be implemented by executing corresponding software by hardware. The hardware or software may include units or modules corresponding to one or more of the above functions.

[0009] In an implementation, the structure of the communication device may include a transceiver module and a processing module, the processing module being configured to support the communication device to perform functions corresponding to the above-mentioned method. The transceiver module is used to support communication between the communication device and other devices. The communication device may further include a storage module, coupled to the transceiver module and the processing module, for storing computer programs and data required for the communication device.

[0010] In an implementation, the communication device includes a transceiver module configured to report flight path information to a network side device in response to satisfying a trigger condition.

[0011] In a fourth aspect, an embodiment of the present disclosure provides another communication device, which implements part or all of the functions of the network side device in the example of the method described in the second aspect. For example, the function of the communication device may include part or all of the functions of the embodiments of the present disclosure, or may include the function of independently implementing any embodiment of the present disclosure. The functions may be implemented by hardware, or may be implemented by executing corresponding software by hardware. The hardware or software includes units or modules corresponding to one or more of the above functions.

[0012] In an implementation, the structure of the communication device may include a transceiver module and a processing module, the processing module being configured to support the communication device to perform functions corresponding to the above-mentioned method. The transceiver module is used to support communication between the communication device and other devices. The communication device may further include a storage module, coupled to the transceiver module and the processing module, for storing computer programs and data required for the communication device.

[0013] In an implementation, the communication apparatus includes a transceiver module configured to receive flight path information reported by a terminal device when a trigger condition is met.

[0014] In a fifth aspect, an embodiment of the present disclosure provides a communication device, the communication device including a processor, the communication device executing the method according to the first aspect when the processor invokes a computer program stored in a memory.

[0015] In a sixth aspect, an embodiment of the present disclosure provides a communication device, the communication device including a processor, the communication device performing the method according to the second aspect when the processor invokes a computer program stored in a memory.

[0016] In a seventh aspect, an embodiment of the present disclosure provides a communication device, the communication device including a processor and a memory, wherein a computer program is stored in the memory, and the processor executes the computer program stored in the memory to cause the communication device to perform the method of the first aspect.

[0017] In an eighth aspect, an embodiment of the present disclosure provides a communication device, the communication device including a processor and a memory, wherein a computer program is stored in the memory, and the processor executes the computer program stored in the memory to cause the communication device to perform the method of the second aspect.

[0018] In a ninth aspect, an embodiment of the present disclosure provides a communication device, the device including a processor and an interface circuit, the interface circuit being used to receive and transmit code instructions to the processor, the processor being used to execute the code instructions to cause the device to perform the method of the first aspect.

[0019] In a tenth aspect, an embodiment of the present disclosure provides a communication device, the device including a processor and an interface circuit, the interface circuit being used to receive and transmit code instructions to the processor, the processor being used to execute the code instructions to cause the device to perform the method of the second aspect.

[0020] In an eleventh aspect, an embodiment of the present disclosure provides a random access system, the system including a communication device according to the third aspect and a communication device according to the fourth aspect, or the system including a communication device according to the fifth aspect and a communication device according to the sixth aspect, or the system including a communication device according to the seventh aspect and a communication device according to the eighth aspect, or the system including a communication device according to the ninth aspect and a communication device according to the tenth aspect.

[0021] In a twelfth aspect, an embodiment of the present invention provides a computer-readable storage medium, used to store instructions for use in a terminal device as defined above, which, when executed, cause the terminal device to perform a method as defined in the first aspect.

[0022] In a thirteenth aspect, an embodiment of the present invention provides a readable storage medium, used to store instructions for use in the network side device, which, when executed, cause the network side device to perform the method of the second aspect.

[0023] In a fourteenth aspect, the present disclosure further provides a computer program product comprising a computer program which, when executed on a computer, causes the computer to perform the method according to the first aspect above.

[0024] In a fifteenth aspect, the present disclosure further provides a computer program product comprising a computer program which, when executed on a computer, causes the computer to perform the method according to the second aspect above.

[0025] In a sixteenth aspect, the present disclosure provides a chip system, the chip system including at least one processor and an interface, for use in supporting a terminal device to realize the function according to the first aspect, for example, determining or processing at least one of data and information according to the above-described method. In a possible design, the chip system further includes a memory, the memory being used to store computer programs and data required by the terminal device. The chip system may be composed of chips or may include chips and other discrete devices.

[0026] In a seventeenth aspect, the present disclosure provides a chip system, the chip system including at least one processor and an interface, for use in supporting a network side device to implement the functionality according to the second aspect, for example, determining or processing at least one of the data and information according to the above-described method. In a possible design, the chip system further includes a memory, the memory being used to store computer programs and data required by the network side device. The chip system may be comprised of a chip or may include chips and other discrete devices.

[0027] In an eighteenth aspect, the present disclosure provides a computer program which, when executed on a computer, causes the computer to perform the method according to the first aspect above.

[0028] In a nineteenth aspect, the present disclosure provides a computer program which, when executed on a computer, causes the computer to perform the method according to the second aspect above. [Brief explanation of the drawings]

[0029] In order to more clearly describe the technical solutions in the embodiments or background art of the present application, the following describes the drawings that need to be used in the embodiments or background art of the present application. [Figure 1] 1 is an architecture diagram of a communication system provided by an embodiment of the present disclosure. [Figure 2] 1 is a flowchart of a route reporting method provided by an embodiment of the present disclosure. [Figure 3] 1 is a flowchart of another route reporting method provided by an embodiment of the present disclosure. [Figure 4] 1 is a flowchart of another route reporting method provided by an embodiment of the present disclosure. [Figure 5] 1 is a flowchart of another route reporting method provided by an embodiment of the present disclosure. [Figure 6]1 is a flowchart of another route reporting method provided by an embodiment of the present disclosure. [Figure 7] 1 is a flowchart of another route reporting method provided by an embodiment of the present disclosure. [Figure 8] 1 is a flowchart of another route reporting method provided by an embodiment of the present disclosure. [Figure 9] 1 is a flowchart of another route reporting method provided by an embodiment of the present disclosure. [Figure 10] 1 is a flowchart of another route reporting method provided by an embodiment of the present disclosure. [Figure 11] 1 is a flowchart of another route reporting method provided by an embodiment of the present disclosure. [Figure 12] 1 is a flowchart of another route reporting method provided by an embodiment of the present disclosure. [Figure 13] 1 is a flowchart of another route reporting method provided by an embodiment of the present disclosure. [Figure 14] 1 is a flowchart of another route reporting method provided by an embodiment of the present disclosure. [Figure 15] 1 is a flowchart of another route reporting method provided by an embodiment of the present disclosure. [Figure 16] 1 is a flowchart of another route reporting method provided by an embodiment of the present disclosure. [Figure 17] FIG. 1 is a configuration diagram of a communication device provided by an embodiment of the present disclosure. [Figure 18] FIG. 10 is a block diagram of another communication device provided by an embodiment of the present disclosure. [Figure 19] 1 is a schematic diagram of a chip provided by an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0030] To better understand the route reporting method and apparatus disclosed in the embodiments of the present disclosure, the following first describes a communication system applicable to the embodiments of the present disclosure.

[0031] Referring to Figure 1, Figure 1 shows the architecture of a communication system provided by an embodiment of the present application. The communication system may include, but is not limited to, one network device and one terminal device. The number and configuration of devices shown in Figure 1 are merely examples and do not constitute limitations on the embodiment of the present application. In actual applications, the system may include two or more network devices and two or more terminal devices. The communication system shown in Figure 1 takes a network-side device 101 and a terminal device 102 as an example.

[0032] It should be noted that the technical solutions of the embodiments of the present disclosure may be applied to various communication systems, such as a long term evolution (LTE) system, a fifth generation (5G) mobile communication system, a 5G new radio (NR) system, or other future new mobile communication systems. The sidelink in the embodiments of the present disclosure may also be referred to as a sidelink or a pass-through link.

[0033] The network side device 101 in the embodiments of the present application is a network-side entity for transmitting and receiving signals. For example, the network side device 101 may be an evolved base station (eNB), a transmission reception point (TRP), a next generation base station (gNB) in an NR system, a base station in other future mobile communication systems, or an access point in a wireless fidelity (WiFi) system. The embodiments of the present application do not limit the specific technology and specific device form used for the base station. The base station provided in the embodiments of the present application may be composed of a central unit (CU) and distributed units (DUs), where the CU is also called a control unit. Using the CU-DU structure, the protocol layer of the base station, for example, can be divided, with some protocol layer functions centrally controlled by the CU and some or all of the remaining protocol layer functions distributed to the DUs, and the DUs centrally controlled by the CU.

[0034] The terminal device 102 in the embodiments of the present application is a user-side entity for transmitting and receiving signals, such as a mobile phone. The terminal device may also be called a terminal, user equipment (UE), mobile station (MS), mobile terminal (MT), etc. The terminal device may be an automobile with communication capabilities, a smart car, a mobile phone, a wearable device, a tablet, a personal computer with wireless transmission and reception capabilities, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical surgery, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, a wireless terminal device in a smart home, etc. The embodiments of the present application do not limit the specific technology and specific device form used for the terminal device.

[0035] It should be noted that the communication system described in the embodiments of the present application is intended to more clearly illustrate the technical solutions of the embodiments of the present application, and does not limit the technical solutions provided by the embodiments of the present application. As those skilled in the art will appreciate, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions provided by the embodiments of the present application can also be applied to similar technical problems.

[0036] The following describes in detail the route reporting method and apparatus provided by the present disclosure in combination with the drawings.

[0037] In R15, UAV studies will be carried out, and the feasibility and necessary enhancements for UAV connectivity via terrestrial cellular systems will already be verified, with LTE making corresponding enhancements in terms of uplink and downlink interference and mobility.

[0038] In NR, the applications applied to UAVs are becoming more diverse, and there are higher latency and transmission speed requirements for UAV terminal devices. Therefore, NR UAVs need to be extended based on LTE UAVs.

[0039] To enhance mobility, LTE UAVs require terminal devices (drones) to report their planned flight paths to a network side device (eNB) via Radio Resource Control (RRC) messages, allowing the terminal device to indicate its future planned location. For the terminal device's mobility, the network side device can integrate this information to perform mobility management, such as switching the terminal device's settings. For example, based on this information, the network side device can predict which cell will be suitable for future access by the terminal device, i.e., the terminal device's target cell. The terminal device flies along a pre-planned path, and before its location approaches or reaches the serving cell edge, it can begin preparations for switching between the network side device to which the serving cell belongs and the network side device to which the adjacent target cell belongs. For example, the network side device to which the target cell belongs at the next point on the flight path belongs can be selected, the terminal device context can be transferred in advance, radio resources can be pre-configured for the terminal device in the network side device to which the target cell belongs, and a switching command can be sent to the terminal device under high-quality radio link conditions. This significantly reduces the probability of a cell switch failure when the terminal device performs a cell switch on its flight path.

[0040] In LTE UAV, the UAV terminal device reports its flight path based on the network device's request information: Reception of the UE Information Request message (when the terminal device receives the UEInformationRequest sent by the network) 1) if flightPathInfoRed field is present and the UE has flight path information available: 2) include the flightPathInfoReport and set it to include the list of waypoints along the flight path; 2) if the includeTimeStamp is set to TRUE: 3) set the field timeStamp to the time when the UE intends to arrive to each waypoint if this information is available at the UE; UEInformationRequest: UEInformationRequest-v15xy-IEs ::=SEQUENCE{ FlightPathInfoReq-r15 FlightPathInfoReportConfig-r15 OPTIONAL, --Need ON nonCriticalExtension SEQUENCE{} OPTIONAL } FlightPathInfoReportConfig-r15 ::=SEQUENCE{ maxWayPointNumber-r15 INTEGER(1..maxWayPoint-r15), IncludeTimeStamp-r15 ENUMERATED{true} OPTIONAL } --ASNISTOP FlightPathInfoReportConfig field descriptions maxWayPointNumber (maximum number of points) include the maximum number of way points the UE can include in the flight path information report if this information is available at the UE. includeTimeStamp (include timestamp) Indicates whether the time stamp of each way point can be reported in the flight path information report if time stamp information is available at the UE. UEInformationResponse-v15xy-IEs ::=SEQUENCE{ FlightPathInfoReort-r15 FlightPathInfoReport-r15 OPTIONAL, nonCriticalExtension SEQUENCE{} OPTIONAL } UEInformationResponse: (The terminal device sends the reply information to the network side device, which contains the flight path) FlightPathInfoReport-r15 ::=SEQUENCE{ FlightPath-r15 SEQUENCE(SIZE(1..maxWayPoint-r15)) OF WayPointLocation-r15 OPTIONAL, nonCriticalExtension SEQUENCE{} OPTIONAL } WayPointLocation-r15 ::=SEQUENCE{ WayPointLocation-r15 LocationInfo-r10, TimeStamp-r15 AbsoluteTimeInfo-r10 OPTIONAL } timeStamp Includes time stamps for the waypoints that describe planned locations for the UE. TraceRecordingSessionRef Parameter Trace Recording Session Reference: See TS 32.422

[58] . Waypoint location Includes location coordinates for a UE for Aerial UE operation. The waypoints describe planned locations for the UE. In the related art, there is still a lack of a method for a terminal device to report flight path information, which is a problem that needs to be solved urgently.

[0041] Based on this, an embodiment of the present disclosure provides a route reporting method and apparatus, which can report flight route information to a network side device when a terminal device meets a trigger condition, supports the terminal device to report flight route information, can improve the reliability of mobility configuration, and can avoid cell switching failure.

[0042] It should be noted that the embodiments of the present disclosure provide multiple implementation methods to clearly explain the technical solutions of the embodiments of the present disclosure. Of course, those skilled in the art can understand that the multiple implementations provided by the embodiments of the present disclosure can be implemented independently, can be implemented in combination with methods of other embodiments of the embodiments of the present disclosure, and can be implemented independently or in combination with some methods of other related technologies, and the embodiments of the present disclosure are not limited thereto.

[0043] Please refer to FIG. 2, which is a flowchart of a route reporting method provided by an embodiment of the present disclosure.

[0044] As shown in FIG. 2, the method is performed by a terminal device, and the method may include, but is not limited to, the following steps: S21: In response to satisfying the trigger condition, report flight path information to a network side device.

[0045] In the embodiment of the present disclosure, when the terminal device meets the trigger condition, it can actively trigger the reporting of flight path information to the network side device.

[0046] The terminal device may determine the trigger condition based on a protocol agreement, or may determine the trigger condition based on the implementation of the terminal device, or may determine the trigger condition based on a network-side device instruction, or may jointly determine the trigger condition based on the implementation of the terminal device and the protocol agreement, or may jointly determine the trigger condition based on the implementation of the terminal device and the network-side device instruction, or may jointly determine the trigger condition based on the protocol agreement and the network-side device instruction, and the embodiments of the present disclosure are not limited thereto.

[0047] Illustratively, the trigger condition or a parameter corresponding to the trigger condition may be set by the network, may be specified by a protocol, or may be determined based on the implementation of the terminal.

[0048] Illustratively, the terminal may determine whether the trigger condition is met based on the terminal's implementation or network configuration or protocol specification.

[0049] Illustratively, a terminal may determine whether to report flight path information based on the implementation of the terminal.

[0050] In a possible implementation, the trigger condition is different from a request for a flight path report sent by a network side device, and the reporting of flight path information is not triggered based on a request for a flight path report sent by a network side device, but is actively triggered and reported by the terminal device.

[0051] It can be understood that after the terminal device reports a flight path to the network side device, a change in the flight path may occur, and the network side device cannot know the changed flight path information of the terminal device, and the terminal device will always perform mobility configuration according to the flight path previously reported, which will affect the reliability of the subsequent mobility configuration of the network side device and may cause cell switching failure.

[0052] Similarly, the flight of the terminal device can further be converted from being flown according to a plan to being controlled by an operator, and the flight path previously reported by the terminal device will also become invalid, so at this time the terminal device needs to further inform the network side device, otherwise the network side device may make subsequent mobility configurations for the terminal device based on the flight path reported by the terminal device, thereby affecting the reliability of the subsequent mobility configurations and possibly causing cell switching failures.

[0053] In an embodiment of the present disclosure, the terminal device can actively report flight path information to the network side device if a trigger condition is met, and the trigger condition may be any condition that can indicate that the previously reported flight path is invalid or needs to be updated.

[0054] Exemplarily, the trigger condition may be that the flight path last reported by the terminal device is invalid, or the flight path last reported is updated, or the terminal device converts from flying according to a planned path to being controlled by an operator, or there is an offset between the current flight path and the flight path last reported, etc.

[0055] Of course, the trigger conditions are not limited to the above examples, and any trigger condition that can indicate that the previously reported flight path is invalid or needs to be updated falls within the scope of protection of the embodiments of the present disclosure, and the embodiments of the present disclosure are not limited in this regard.

[0056] In an embodiment of the present disclosure, when the terminal device meets a trigger condition, it reports flight path information to the network side device, and the flight path information is used to assist the network side device in performing mobility management.

[0057] For example, the flight path information may be a flight path (an updated flight path or a new flight path), or a flight direction (an updated flight direction or a new flight direction), or a flight path validity indication information for indicating that the previously reported flight path is accurate, or a flight path invalidity indication information for indicating that the previously reported flight path is incorrect (already invalid), etc.

[0058] Illustratively, the flight path invalidation indication may be a display indication or an implicit indication.

[0059] Implicit indication information includes any information or message that can implicitly indicate said meaning.

[0060] For example, when the flight path information is a flight path, the flight path may be a planned flight path, and the planned flight path may be a path planned to be flown within a certain time in the future, that is, the terminal device may inform the network side device and may be a flight path planned by the terminal device within a certain time in the future, and the network side device may perform mobility configuration based on the flight path information reported by the terminal device, for example, determine which cell is suitable for the terminal device to access at a certain time in the future based on the flight path information reported by the terminal device, and the terminal device may perform cell switching in advance to transfer the context of the terminal device, etc.

[0061] It can be understood that when the flight path information is a flight path, the terminal device meets the trigger condition, and the trigger condition being the invalidity of the flight path can be understood to be the invalidity of the previously reported flight path, and based on this, the terminal device can report flight path information which is a flight path to the network side device when the previously reported flight path is invalid, and the flight path information is a flight path, and the reported flight path is different from the previously reported flight path.

[0062] It can be understood that when the flight path information is a flight path, the terminal device meets the trigger condition, and the trigger condition is flight path update, it can be understood that the terminal device updates a new flight path based on the flight path previously reported, and based on this, the terminal device can report flight path information, which is a flight path, to the network side device if the flight path previously reported has already been updated, and the flight path information is a flight path, and the reported flight path is different from the flight path previously reported.

[0063] In addition, the terminal device can update the flight route of the previously reported network side device based on the implementation, the configuration of the network side device, or the protocol agreement, etc., and the terminal device can determine whether an update has occurred to the flight route of the previously reported network side device. After the terminal device updates the flight route of the previously reported network side device, it can obtain the updated flight route.

[0064] In an embodiment of the present disclosure, when the terminal device determines that the previously reported flight path is no longer applicable, the terminal device can actively report flight path information to the network side device, thereby supporting the terminal device to actively trigger the reporting of flight path information, allowing the network side device to perform mobility management based on the flight path information, preventing the network side device from performing mobility configuration according to the incorrect flight path previously reported by the terminal device, improving the reliability of mobility configuration, and avoiding cell switching failure of the terminal device.

[0065] In an embodiment of the present disclosure, the trigger condition may be one or more measurement reporting events, and when the terminal device meets the measurement reporting event, it can report a measurement report to the network side device, and the measurement report may include flight path information.

[0066] In an embodiment of the present disclosure, the trigger condition may be a condition that triggers reporting of the auxiliary information of the auxiliary information, and when the terminal device satisfies the condition that triggers reporting of the auxiliary information, it can report the auxiliary information to the network side device, and the auxiliary information may include flight path information.

[0067] Based on this, the terminal device supports actively reporting flight path information, and the network side device can perform mobility management based on the flight path information, which can prevent the network side device from performing mobility configuration according to the incorrect flight path previously reported by the terminal device, improve the reliability of the mobility configuration, and avoid cell switching failure of the terminal device.

[0068] In some embodiments, the flight path information includes at least one of a flight path valid indication, a flight path invalid indication, a flight path, and a flight direction.

[0069] In the embodiment of the present disclosure, when the terminal device meets the trigger condition, it reports flight path information to the network side device, and the flight path information may be valid indication information of the flight path.

[0070] It can be understood that the terminal device reports flight path validity indication information to the network side device to indicate that the previously reported flight path is valid, and based on this, the network side device can continuously perform mobility management based on the flight path previously reported by the terminal device.

[0071] In an embodiment of the present disclosure, when the terminal device meets the trigger condition, it reports flight path information to the network side device, and the flight path information may be flight path invalid indication information.

[0072] It can be understood that the terminal device reports flight path invalid indication information to the network side device, indicating that the previously reported flight path is already invalid; based on this, the network side device can stop or cancel the terminal device from performing mobility management based on the previously reported flight path, thereby preventing the network side device from performing mobility configuration according to the incorrect flight path previously reported by the terminal device, thereby improving the reliability of the mobility configuration and avoiding cell switching failure of the terminal device.

[0073] The trigger condition is that if the terminal device determines that the last reported flight path is invalid, and / or the last reported flight path is updated, and / or the terminal device converts from flying according to a planned path to being controlled by an operator, and / or there is an offset between the current flight path and the last reported flight path, then the terminal device can report flight path invalid indication information to the network side device, indicating that the last reported flight path is already invalid.

[0074] In an embodiment of the present disclosure, when the terminal device meets the trigger condition, it reports flight path information to the network side device, and the flight path information may be a flight path (a new flight path or an updated flight path).

[0075] It can be understood that the terminal device reports a flight path to the network side device to indicate the flight path of the terminal device within a certain period of time in the future, and based on this, the network side device can determine the flight path of the terminal device and perform mobility management based on the flight path.

[0076] The trigger condition is that the terminal device's previously reported flight path is invalid, and / or the previously reported flight path has been updated, and / or the terminal device has converted from flying according to a planned path to being controlled by an operator, and / or there is an offset between the current flight path and the previously reported flight path. If it is determined that the terminal device satisfies the trigger condition, it can report the flight path to the network side device and instruct the updated flight path, and the updated flight path is different from the previously reported flight path, thereby preventing the network side device from performing mobility configuration according to the incorrect flight path previously reported by the terminal device, thereby improving the reliability of the mobility configuration and avoiding cell switching failure of the terminal device.

[0077] In an embodiment of the present disclosure, when the terminal device meets the trigger condition, it reports flight path information to the network side device, and the flight path information may be a flight direction (a new flight direction or an updated flight direction).

[0078] It should be noted that the above-described embodiments are not particularly limiting but merely serve as examples of some of the embodiments, and the above-described embodiments can be implemented singly or in combination with one another. The above-described embodiments are merely examples and do not specifically limit the scope of protection of the embodiments of the present disclosure.

[0079] In some embodiments, the flight path includes at least one of a flight waypoint, a plurality of flight waypoints, a timestamp, and a plurality of timestamps.

[0080] In an embodiment of the present disclosure, when the terminal device meets a trigger condition, it reports flight path information to the network side device, and the flight path information may be a flight path, and the flight path includes one flight waypoint.

[0081] In an embodiment of the present disclosure, when the terminal device meets a trigger condition, it reports flight path information to the network side device, and the flight path information may be a flight path, and the flight path includes a plurality of flight waypoints.

[0082] In an embodiment of the present disclosure, when the terminal device meets the trigger condition, it reports flight path information to the network side device, and the flight path information may be a flight path, and the flight path includes a timestamp.

[0083] In an embodiment of the present disclosure, when the terminal device meets a trigger condition, it reports flight path information to the network side device, and the flight path information may be a flight path, and the flight path includes multiple timestamps.

[0084] It should be noted that the above-described embodiments are not particularly limiting but merely serve as examples of some of the embodiments, and the above-described embodiments can be implemented singly or in combination with one another. The above-described embodiments are merely examples and do not specifically limit the scope of protection of the embodiments of the present disclosure.

[0085] In some embodiments, the timestamp is the difference between the time when the terminal device arrives at the corresponding flight waypoint and the current time, or the time when the terminal device arrives at the corresponding flight waypoint (e.g., UTC time), or the difference between the time when the terminal device arrives at the corresponding flight waypoint and the previous flight waypoint.

[0086] In an embodiment of the present disclosure, the timestamp is the difference between the time when the terminal device arrives at the corresponding flight waypoint and the current time.

[0087] For example, if the time when the terminal device will arrive at the corresponding flight waypoint is 11 AM (11 o'clock in the morning) and the current time is 8 AM, the timestamp is the difference of 4 hours between the time when the terminal device will arrive at the corresponding flight waypoint (11 AM) and the current time (8 AM).

[0088] In an embodiment of the present disclosure, the timestamp is the time at which the terminal device arrives at the corresponding flight waypoint.

[0089] Illustratively, if the time when the terminal device arrives at the corresponding flight waypoint is 11 AM (11 o'clock in the morning), the timestamp is the time when the terminal device arrives at the corresponding flight waypoint, which is 11 AM.

[0090] In an embodiment of the present disclosure, the timestamp is the difference between the time when the terminal device arrives at the corresponding flight waypoint and the time when it arrives at the previous flight waypoint.

[0091] For example, if the time at which the terminal device arrives at the corresponding flight waypoint is 11 AM (11 a.m.) and the time at which the terminal device arrives at the previous flight waypoint is 10 AM, the timestamp is the 1-hour difference between the time at which the terminal device arrives at the corresponding flight waypoint (11 AM) and the time at which the terminal device arrives at the previous flight waypoint (10 AM).

[0092] In some embodiments, the trigger condition includes at least one of a flight path invalidation, a flight path update, the terminal device converting from flying according to a planned path to being controlled by an operator, and an offset existing between the current flight path and the reported flight path.

[0093] In an embodiment of the present disclosure, when the terminal device meets a trigger condition, it reports flight path information to the network side device, and the trigger condition is that the flight path is invalid, so that when the terminal device meets that the flight path is invalid, it can report flight path information to the network side device.

[0094] In an embodiment of the present disclosure, when a terminal device meets a trigger condition, it reports flight path information to a network side device, and the trigger condition is a flight path update, so that when the terminal device meets the flight path update, it can report flight path information to the network side device.

[0095] In an embodiment of the present disclosure, when the terminal device satisfies a trigger condition, it reports flight path information to the network side device, and the trigger condition is that the terminal device is converted from flying according to a planned route to being controlled by an operator, so that when the terminal device satisfies that the terminal device is converted from flying according to a planned route to being controlled by an operator, it can report flight path information to the network side device.

[0096] In an embodiment of the present disclosure, when the terminal device satisfies a trigger condition, it reports flight path information to the network side device, and the trigger condition is that there is an offset between the current flight path and the reported flight path, so that when the terminal device satisfies that there is an offset between the current flight path and the reported flight path, it can report flight path information to the network side device.

[0097] It should be noted that the above-described embodiments are not particularly limiting but merely serve as examples of some of the embodiments, and the above-described embodiments can be implemented singly or in combination with one another. The above-described embodiments are merely examples and do not specifically limit the scope of protection of the embodiments of the present disclosure.

[0098] In some examples, the existence of an offset between the current flight path and the reported flight path includes at least one of: a distance between flight waypoints corresponding to the same time point for the current flight path and the previously reported flight path is greater than a first threshold; a time difference between reaching the same flight waypoint for the current flight path and the previously reported flight path is greater than a second threshold; an absolute value of a difference in flight speed for the same time point for the current flight path and the previously reported flight path is greater than a third threshold; and a change in flight direction for the same time point for the current flight path and the previously reported flight path.

[0099] In an embodiment of the present disclosure, the terminal device may report an updated flight path to the network side device in response to the existence of an offset between the current flight path and the reported flight path, and may report the updated flight path to the network side device if the distance between flight waypoints corresponding to the same time point for the current flight path and the previously reported flight path is greater than a first threshold.

[0100] The flight waypoints may be three-dimensional position information of the terminal device, and the distances between flight waypoints corresponding to the same time point may be distances in 3D space.

[0101] In an embodiment of the present disclosure, the terminal device may report an updated flight path to the network side device in response to the existence of an offset between the current flight path and the reported flight path, and may report the updated flight path to the network side device if the time difference between reaching the same flight waypoint for the current flight path and the previously reported flight path is greater than a second threshold.

[0102] In an embodiment of the present disclosure, the terminal device may report an updated flight path to the network side device in response to the existence of an offset between the current flight path and the reported flight path, and may report the updated flight path to the network side device if the absolute value of the difference in flight speed at the same time between the current flight path and the previously reported flight path is greater than a third threshold.

[0103] In an embodiment of the present disclosure, the terminal device may report an updated flight path to the network side device in response to the existence of an offset between the current flight path and the reported flight path, and may report the updated flight path to the network side device if a change occurs in the flight direction at the same time for the current flight path and the previously reported flight path.

[0104] It can be understood that the flight direction changes at the same time for the current flight path and the previously reported flight path, for example, the aspect in which the flight direction has changed is greater than the fourth threshold.

[0105] It should be noted that the above-described embodiments are not particularly limiting but merely serve as examples of some of the embodiments, and the above-described embodiments can be implemented singly or in combination with one another. The above-described embodiments are merely examples and do not specifically limit the scope of protection of the embodiments of the present disclosure.

[0106] In some embodiments, the trigger condition may be stipulated by a protocol, and the trigger condition parameters (the first threshold and / or the second threshold and / or the third threshold and / or the fourth threshold) corresponding to the trigger condition may be set by the network side device or may be stipulated by the protocol.

[0107] In some embodiments, the terminal device receives configuration information sent by the network-side device, and the configuration information includes at least one of a trigger condition, a report content instruction, and a trigger condition parameter.

[0108] In an embodiment of the present disclosure, the terminal device receives configuration information sent by the network-side device, and the configuration information includes a trigger condition.

[0109] In an embodiment of the present disclosure, the terminal device receives configuration information sent by the network-side device, and the configuration information includes a report content instruction.

[0110] In an embodiment of the present disclosure, the terminal device receives configuration information sent by the network-side device, and the configuration information includes a trigger condition parameter.

[0111] Illustratively, the trigger condition parameter is a first threshold value.

[0112] Illustratively, the trigger condition parameter is a second threshold value.

[0113] Illustratively, the trigger condition parameter is a third threshold value.

[0114] Illustratively, the trigger condition parameter is a fourth threshold value.

[0115] It should be noted that the above-described embodiments are not particularly limiting but merely serve as examples of some of the embodiments, and the above-described embodiments can be implemented singly or in combination with one another. The above-described embodiments are merely examples and do not specifically limit the scope of protection of the embodiments of the present disclosure.

[0116] For example, the setting information may be display instruction information or implicit instruction information.

[0117] Implicit indication information includes any information or message that can implicitly indicate said meaning.

[0118] In some examples, the reporting content instructions include at least one of: report a flight path, do not report a flight path, a maximum number of reportable waypoints, a timestamp must be reported, a timestamp does not need to be reported, a flight path validity indication must be reported, and a flight path validity indication does not need to be reported.

[0119] In an embodiment of the present disclosure, the terminal device receives configuration information sent by the network-side device, the configuration information includes a report content instruction, and the report content instruction includes reporting a flight path.

[0120] In an embodiment of the present disclosure, the terminal device receives configuration information sent by the network side device, the configuration information includes a report content instruction, and the report content instruction includes not reporting a flight path.

[0121] In an embodiment of the present disclosure, the terminal device receives configuration information sent by the network-side device, the configuration information includes a report content instruction, and the report content instruction includes the number of maximum reportable waypoints.

[0122] In an embodiment of the present disclosure, the terminal device receives configuration information sent by the network-side device, the configuration information includes a report content instruction, and the report content instruction includes that a timestamp needs to be reported.

[0123] In an embodiment of the present disclosure, the terminal device receives configuration information sent by the network-side device, the configuration information includes a report content instruction, and the report content instruction includes that a timestamp does not need to be reported.

[0124] In an embodiment of the present disclosure, the terminal device receives configuration information sent by the network side device, the configuration information includes a reporting content instruction, and the reporting content instruction includes that flight path validity instruction information needs to be reported.

[0125] In an embodiment of the present disclosure, the terminal device receives configuration information sent by the network side device, the configuration information includes a reporting content instruction, and the reporting content instruction includes that there is no need to report flight path validity instruction information.

[0126] It should be noted that the above-described embodiments are not particularly limiting but merely serve as examples of some of the embodiments, and the above-described embodiments can be implemented singly or in combination with one another. The above-described embodiments are merely examples and do not specifically limit the scope of protection of the embodiments of the present disclosure.

[0127] In some embodiments, the terminal device determines trigger conditions and / or determines that it is configured to require reporting of flight path information based on the configuration information.

[0128] In an embodiment of the present disclosure, a terminal device receives configuration information sent by a network-side device, and the configuration information includes a trigger condition, so that the terminal device can determine the trigger condition based on the configuration information.

[0129] In an embodiment of the present disclosure, a terminal device receives configuration information sent by a network-side device, and the configuration information includes a trigger condition parameter, so that the terminal device can determine the trigger condition parameter corresponding to the setting of the trigger condition based on the configuration information, and determine the trigger condition.

[0130] The terminal device can determine the setting of the trigger condition based on the protocol agreement, and determines the trigger condition parameters corresponding to the setting of the trigger condition based on the setting information to determine the trigger condition.

[0131] For example, the terminal device may determine, based on the protocol agreement, that the setting of the trigger condition is that the distance between flight waypoints corresponding to the same time point for the current flight path and the previously reported flight path is greater than a first threshold; determine a trigger condition parameter corresponding to the setting of the trigger condition based on the setting information; and if it determines that the first threshold is 50 cm, it may determine that the trigger condition is that the distance between flight waypoints corresponding to the same time point for the current flight path and the previously reported flight path is greater than 50 cm.

[0132] In an embodiment of the present disclosure, the terminal device receives setting information sent by the network side device, and the setting information includes a trigger condition and a report content instruction, so that the terminal device can determine, based on the setting information, the trigger condition and whether to report flight path information when the trigger condition is met.

[0133] In an embodiment of the present disclosure, the terminal device receives setting information sent by the network side device, and the setting information includes a reporting content instruction, so that the terminal device can determine whether it is configured to require reporting of flight path information based on the setting information.

[0134] In an embodiment of the present disclosure, a terminal device receives setting information sent by a network-side device, the setting information includes a reporting content instruction, and the reporting content instruction includes reporting a flight path, whereby the terminal device can determine, based on the setting information, that it is configured to require reporting flight path information.

[0135] The configuration information may be a Radio Resource Control (RRC) message sent by the network side device, and the RRC message may be an RRC reconfiguration message, or may be configured via other configuration information (otherConfig).

[0136] The terminal device can release the above-mentioned configuration information upon RRC reestablishment or RRC recovery.

[0137] In an embodiment of the present disclosure, a terminal device receives configuration information sent by a network-side device, the configuration information includes a reporting content instruction, and the reporting content instruction includes a need to report a timestamp, so that the terminal device can determine, based on the configuration information, that it is configured to need to report flight path information when it reaches a need to report a timestamp.

[0138] In an embodiment of the present disclosure, a terminal device receives setting information sent by a network-side device, the setting information includes a report content instruction, and the report content instruction includes a maximum number of reportable waypoints, so that the terminal device can determine, based on the setting information, that it is configured to need to perform flight path information reporting, and can report flight path information of the maximum number of reportable waypoints.

[0139] In an embodiment of the present disclosure, a terminal device receives setting information sent by a network-side device, the setting information includes a reporting content instruction, and the reporting content instruction includes a need to report flight path validity indication information, and the terminal device can determine that it is configured to need to report flight path validity indication information, i.e., it needs to report indication information of whether the flight path is valid.

[0140] In an embodiment of the present disclosure, a terminal device receives setting information sent by a network-side device, the setting information includes a reporting content instruction, and the reporting content instruction includes that there is no need to report flight path validity indication information, and the terminal device can determine that it is not configured to need to report flight path validity indication information, i.e., there is no need to report indication information of whether the flight path is valid.

[0141] It should be noted that the above-described embodiments are not particularly limiting but merely serve as examples of some of the embodiments, and the above-described embodiments can be implemented singly or in combination with one another. The above-described embodiments are merely examples and do not specifically limit the scope of protection of the embodiments of the present disclosure.

[0142] In some embodiments, reporting flight path information to the network side device in response to the terminal device satisfying the trigger condition includes reporting flight path invalid instruction information to the network side device in response to flight path invalidation, or reporting flight path invalid instruction information to the network side device in response to a flight path update, or reporting flight path invalid instruction information to the network side device in response to the terminal device converting from flight according to a planned route to operator control.

[0143] In an embodiment of the present disclosure, the terminal device responds to the invalidation of the flight path by reporting invalid indication information of the flight path to the network side device.

[0144] It can be understood that the terminal device can determine flight path invalidity and determine that the current flight path for the terminal device is different (there is a deviation) from the flight path previously reported.

[0145] In an embodiment of the present disclosure, the terminal device reports invalid indication information of the flight path to the network side device in response to updating the flight path.

[0146] It can be understood that when the terminal device decides to update the flight path, it can re-update a new flight path, and the updated new flight path may differ (there may be deviations) from the previously reported flight path.

[0147] In an embodiment of the present disclosure, the terminal device reports flight path invalid instruction information to the network side device in response to the terminal device converting flight from following the planned path to operator control.

[0148] In some embodiments, reporting flight path information to the network side device in response to the terminal device satisfying the trigger condition includes reporting the updated flight path to the network side device in response to an update of the flight path, or reporting the updated flight path to the network side device in response to an offset existing between the current flight path and the reported flight path.

[0149] In an embodiment of the present disclosure, the terminal device responds to the flight route update by reporting the updated flight route to the network side device.

[0150] It can be understood that when the terminal device decides to update the flight path, it can re-update a new flight path, and the updated new flight path may differ (there may be deviations) from the previously reported flight path.

[0151] In an embodiment of the present disclosure, the terminal device reports an updated flight path to the network side device in response to the existence of an offset between the current flight path and the reported flight path.

[0152] In some embodiments, the step of reporting flight path information to the network side device in response to the terminal device satisfying the trigger condition includes: reporting a flight direction to the network side device in response to the terminal device converting from flight following a planned path to control by an operator.

[0153] In an embodiment of the present disclosure, the terminal device reports a flight direction to the network-side device in response to the terminal device converting from flight according to a planned route to control by an operator.

[0154] It can be understood that determining that the terminal device has converted from flying according to a planned path by the terminal device to being controlled by an operator can be determined based on the implementation of the terminal device, and illustratively can be determined based on the settings of the terminal device itself.

[0155] In some embodiments, the terminal device determines whether the trigger condition is met based on the implementation.

[0156] In some embodiments, the terminal device further reports location information to the network side device.

[0157] In the embodiment of the present disclosure, when the terminal device meets the trigger condition, it can also report the flight direction to the network side device and report the location information to the network side device.

[0158] In an embodiment of the present disclosure, the location information may be three-dimensional location information of the terminal device.

[0159] In some embodiments, the trigger condition is a measurement reporting event.

[0160] In the embodiment of the present disclosure, when the terminal device meets a measurement reporting event, it can report flight path information to the network side device.

[0161] Illustratively, the trigger condition may be one or more measurement reporting events.

[0162] Illustratively, measurement reporting events include, for example, A1-A6, B1-B2, D1, T1, etc., where A series events are used for intra-system mobility management, and B series events are used for inter-system mobility management. D1 and T1 are used for satellite system mobility management. The A series reporting events are as follows: Event A1: Serving becomes better than absolute threshold; Event A2: Serving becomes worse than absolute threshold; Event A3: Neighbor becomes better than PCell / PSCell (event A3: signal quality of neighbor cell + offset amount is better than signal quality of primary cell); Event A4: Neighbor becomes better than absolute threshold; Event A5: PCell / PSCell becomes worse than absolute threshold1 AND Neighbor / SCell becomes better than another absolute threshold2 (Event A5: The signal quality of the primary cell is lower than threshold1, and at the same time, the signal quality of the neighbor cell is higher than threshold2); Event A6: Neighbor becomes amount of offset better than SCell.

[0163] Illustratively, the measurement reporting event may also be a condition used to trigger a route report, such as one or more of the following conditions: the flight route last reported by the terminal device is invalid, or the flight route last reported is updated, or the terminal device converts from flying according to a planned route to being controlled by an operator, or there is an offset between the current flight route and the flight route last reported.

[0164] Of course, the measurement reporting events are not limited to the above examples, and any trigger condition that can indicate that the previously reported flight path is invalid or needs to be updated is within the scope of protection of the embodiments of the present disclosure, and the embodiments of the present disclosure are not limited in this regard.

[0165] In some embodiments, the step of reporting flight path information to the network side device in response to the terminal device satisfying a trigger condition includes the step of reporting a measurement report to the network side device in response to the terminal device satisfying a measurement reporting event, the measurement report including the flight path information.

[0166] In an embodiment of the present disclosure, the trigger condition may be a measurement reporting event, and when the terminal device meets the measurement reporting event, it can report a measurement report to the network side device, and the measurement report may include flight path information.

[0167] In some embodiments, the trigger condition is a condition that triggers reporting of the auxiliary information.

[0168] In the embodiment of the present disclosure, if the terminal device meets a trigger condition, it can report flight path information to the network side device, and the trigger condition may be a condition that triggers reporting auxiliary information.

[0169] In the embodiment of the present disclosure, when the terminal device meets the condition that triggers reporting the assistance information, it reports the assistance information to the network side device.

[0170] Illustratively, the condition for the triggering auxiliary information may be one or more of the following conditions: The flight path last reported by the terminal device is invalid, or the flight path last reported has been updated, or the terminal device has converted from flying along a planned path to being controlled by the operator, or there is an offset between the current flight path and the flight path last reported.

[0171] Of course, the conditions that trigger the reporting of auxiliary information are not limited to the above examples, and any trigger condition that can indicate that the previously reported flight path is invalid or needs to be updated falls within the scope of protection of the embodiments of the present disclosure, and the embodiments of the present disclosure are not limited in this regard.

[0172] In some examples, the step of reporting the flight path information to the network side device in response to the terminal device satisfying the trigger condition includes reporting the auxiliary information to the network side device in response to satisfying a condition that triggers reporting the auxiliary information, wherein the auxiliary information includes the flight path information.

[0173] Illustratively, the configuration information of the network side device is received, and the terminal is configured to provide flight path related information, or the network side device is configured to report the flight path.

[0174] Illustratively, the flight path report is configured via an RRC message, which may be an RRC reconfiguration message, and can be configured by otherConfig.

[0175] Illustratively, upon RRC reestablishment or RRC recovery, the UE releases the flight path reporting configuration.

[0176] In an embodiment of the present disclosure, the trigger condition may be a condition that triggers reporting of the auxiliary information of the auxiliary information, and when the terminal device satisfies the condition that triggers reporting of the auxiliary information, it can report the auxiliary information to the network side device, and the auxiliary information may include flight path information.

[0177] In some examples, the step of reporting the flight path information to the network side device in response to the terminal device satisfying the trigger condition is configured to require reporting of the flight path information by the terminal device, and includes a step of not reporting auxiliary information including the flight path information to the network side device, and in response to satisfying the trigger condition, starting reporting of the auxiliary information to the network side device, wherein the auxiliary information includes the flight path information.

[0178] In an embodiment of the present disclosure, the trigger condition may be configured to require the terminal device to report flight path information, and it is determined that the trigger condition is not to report auxiliary information including flight path information to the network side device, and the trigger condition is met, and the terminal device is configured to require the terminal device to report flight path information, and if the terminal device does not report auxiliary information including flight path information to the network side device, and the trigger condition is met, the terminal device can report auxiliary information to the network side device, and the auxiliary information can include flight path information.

[0179] In some examples, the step of reporting the flight path information to the network side device in response to the terminal device satisfying the trigger condition is configured to require reporting of the flight path information by the terminal device, and includes the step of initiating reporting of auxiliary information to the network side device in response to the satisfying of the trigger condition, wherein the auxiliary information includes the flight path information.

[0180] In an embodiment of the present disclosure, the trigger condition may be configured to require the terminal device to report flight path information, and the trigger condition may be satisfied; if it is determined that the terminal device is configured to require the terminal device to report flight path information, and the trigger condition is satisfied, auxiliary information may be reported to the network side device, and the auxiliary information may include flight path information.

[0181] Based on this, the terminal device supports actively reporting flight path information, and the network side device can perform mobility management based on the flight path information, which can prevent the network side device from performing mobility configuration according to the incorrect flight path previously reported by the terminal device, improve the reliability of the mobility configuration, and avoid cell switching failure of the terminal device.

[0182] Please refer to FIG. 3, which is a flowchart of another route reporting method provided by an embodiment of the present disclosure.

[0183] As shown in FIG. 3, the method is performed by a terminal device, and the method may include, but is not limited to, the following steps: S31: Receive the setting information sent by the network side device.

[0184] S32: Based on the setting information, it is determined that the system is configured to require reporting of flight path information.

[0185] In an embodiment of the present disclosure, the terminal device receives the setting information sent by the network side device, and the setting information includes a reporting content instruction, so that the terminal device can determine whether it is configured to need to report flight path information based on the setting information.

[0186] The configuration information includes report content instructions.

[0187] In some examples, the reporting content instructions include at least one of: report a flight path; do not report a flight path; a maximum number of reportable waypoints; a timestamp must be reported; a timestamp does not need to be reported; a flight path validity indication must be reported; and a flight path validity indication does not need to be reported.

[0188] In an embodiment of the present disclosure, a terminal device receives configuration information sent by a network-side device, the configuration information includes a reporting content instruction, the reporting content instruction includes reporting a flight path, and the terminal device can determine that it is configured to require reporting flight path information.

[0189] In an embodiment of the present disclosure, a terminal device receives configuration information sent by a network-side device, the configuration information includes a reporting content instruction, the reporting content instruction includes not reporting a flight path, and the terminal device can determine that it is not configured to require reporting of flight path information.

[0190] In an embodiment of the present disclosure, a terminal device receives setting information sent by a network-side device, the setting information includes a report content instruction, the report content instruction includes a maximum number of reportable waypoints, the terminal device can determine that it is configured to need to perform flight path information reporting, and can determine to report flight path information of the maximum number of reportable waypoints.

[0191] In an embodiment of the present disclosure, a terminal device receives setting information sent by a network-side device, the setting information includes a reporting content instruction, the reporting content instruction includes a need to report a timestamp, and the terminal device can determine that it is configured to report flight path information when it reaches the need to report the timestamp.

[0192] In an embodiment of the present disclosure, a terminal device receives setting information sent by a network-side device, the setting information includes a reporting content instruction, and the reporting content instruction includes that a timestamp does not need to be reported, and the terminal device can determine that it is configured not to report flight path information when a timestamp does not need to be reported.

[0193] In an embodiment of the present disclosure, a terminal device receives setting information sent by a network-side device, the setting information includes a reporting content instruction, and the reporting content instruction includes a need to report flight path validity indication information, and the terminal device can determine that it is configured to need to report flight path validity indication information, i.e., it needs to report indication information of whether the flight path is valid.

[0194] In an embodiment of the present disclosure, a terminal device receives setting information sent by a network-side device, the setting information includes a reporting content instruction, and the reporting content instruction includes that there is no need to report flight path validity indication information, and the terminal device can determine that it is not configured to need to report flight path validity indication information, i.e., there is no need to report indication information of whether the flight path is valid.

[0195] It should be noted that the above-described embodiments are not particularly limiting but merely serve as examples of some of the embodiments, and the above-described embodiments can be implemented singly or in combination with one another. The above-described embodiments are merely examples and do not specifically limit the scope of protection of the embodiments of the present disclosure.

[0196] The setting information includes trigger condition parameters.

[0197] Illustratively, the trigger condition parameter is a first threshold value.

[0198] Illustratively, the trigger condition parameter is a second threshold value.

[0199] Illustratively, the trigger condition parameter is a third threshold value.

[0200] Illustratively, the trigger condition parameter is a fourth threshold value.

[0201] In some embodiments, the trigger condition includes at least one of a flight path invalidation, a flight path update, the terminal device converting from flying according to a planned path to being controlled by an operator, and an offset existing between the current flight path and the reported flight path.

[0202] In some examples, the existence of an offset between the current flight path and the reported flight path includes at least one of: the distance between flight waypoints corresponding to the same time point for the current flight path and the previously reported flight path is greater than a first threshold; the time difference to reach the same flight waypoint for the current flight path and the previously reported flight path is greater than a second threshold; the absolute value of the difference in flight speed for the same time point for the current flight path and the previously reported flight path is greater than a third threshold; and a change in flight direction for the same time point for the current flight path and the previously reported flight path.

[0203] It can be understood that the flight direction changes at the same time for the current flight path and the previously reported flight path, for example, the aspect in which the flight direction has changed is greater than the fourth threshold.

[0204] The setting information includes trigger condition parameters.

[0205] Illustratively, the trigger condition parameter is a first threshold value in the trigger condition.

[0206] Illustratively, the trigger condition parameter is the second threshold value in the trigger condition.

[0207] Illustratively, the trigger condition parameter is the third threshold value in the above-mentioned trigger condition.

[0208] Illustratively, the trigger condition parameter is the fourth threshold value in the above-mentioned trigger condition.

[0209] S33: In response to satisfying the trigger condition, report the flight path information to the network side device.

[0210] In the embodiments of the present disclosure, the terminal device may determine the trigger condition based on a protocol agreement, or may determine the trigger condition based on the implementation of the terminal device.

[0211] For the relevant description of S33, please refer to the relevant description in the above embodiment, and no further description will be given here.

[0212] It should be noted that in the embodiments of the present disclosure, S31 and S33 can be implemented independently, or can be combined with any other step in the embodiments of the present disclosure and implemented together, for example, S21 in the embodiments of the present disclosure and implemented together, and the embodiments of the present disclosure are not limited thereto.

[0213] By implementing the embodiments of the present disclosure, the terminal device receives the configuration information sent by the network side device, determines based on the configuration information that it is configured to require reporting of flight path information, and reports the flight path information to the network side device in response to satisfying a trigger condition, thereby supporting the terminal device to actively report flight path information, enabling the network side device to perform mobility management based on the flight path information, preventing the network side device from configuring mobility according to an incorrect flight path previously reported by the terminal device, improving the reliability of the mobility configuration, and avoiding cell switching failure of the terminal device.

[0214] Please refer to FIG. 4, which is a flowchart of another route reporting method provided by an embodiment of the present disclosure.

[0215] As shown in FIG. 4, the method is performed by a terminal device, and the method may include, but is not limited to, the following steps: S41: Receive configuration information sent by a network-side device, where the configuration information includes a trigger condition and / or a trigger condition parameter.

[0216] S42: Based on the setting information, the trigger condition is determined.

[0217] In an embodiment of the present disclosure, a terminal device receives configuration information sent by a network-side device, and the configuration information includes a trigger condition and / or a trigger condition parameter, so that the terminal device can determine the trigger condition based on the configuration information.

[0218] In an embodiment of the present disclosure, a terminal device receives configuration information sent by a network-side device, and the configuration information includes a trigger condition parameter, so that the terminal device can determine the trigger condition parameter corresponding to the setting of the trigger condition based on the configuration information, and determine the trigger condition.

[0219] The terminal device can determine the setting of the trigger condition based on the protocol agreement, and determines the trigger condition parameters corresponding to the setting of the trigger condition based on the setting information to determine the trigger condition.

[0220] For example, the terminal device may determine, based on the protocol agreement, that the setting of the trigger condition is that the distance between flight waypoints corresponding to the same time point for the current flight path and the previously reported flight path is greater than a first threshold; determine a trigger condition parameter corresponding to the setting of the trigger condition based on the setting information; and if it determines that the first threshold is 50 cm, it may determine that the trigger condition is that the distance between flight waypoints corresponding to the same time point for the current flight path and the previously reported flight path is greater than 50 cm.

[0221] In some embodiments, the trigger condition includes at least one of a flight path invalidation, a flight path update, the terminal device being converted from flying according to a planned path to being controlled by an operator, and an offset existing between the current flight path and the reported flight path.

[0222] In the embodiment of the present disclosure, the configuration information sent by the network-side device may include the above-mentioned trigger conditions.

[0223] In some examples, the existence of an offset between the current flight path and the reported flight path includes at least one of: the distance between flight waypoints corresponding to the same time point for the current flight path and the previously reported flight path is greater than a first threshold; the time difference to reach the same flight waypoint for the current flight path and the previously reported flight path is greater than a second threshold; the absolute value of the difference in flight speed for the same time point for the current flight path and the previously reported flight path is greater than a third threshold; and a change in flight direction for the same time point for the current flight path and the previously reported flight path.

[0224] In the embodiment of the present disclosure, the configuration information sent by the network-side device may include the above-mentioned trigger condition parameters.

[0225] Illustratively, the trigger condition parameter is a first threshold value.

[0226] Illustratively, the trigger condition parameter is a second threshold value.

[0227] Illustratively, the trigger condition parameter is a third threshold value.

[0228] Illustratively, the trigger condition parameter is a fourth threshold value.

[0229] Of course, the terminal device can also jointly determine the above-mentioned trigger conditions based on the protocol agreement and the trigger condition parameters set by the network side device.

[0230] S43: In response to satisfying the trigger condition, report the flight path information to the network side device.

[0231] For the relevant description of S43, please refer to the relevant description in the above embodiment, and no further description will be given here.

[0232] It should be noted that in the embodiments of the present disclosure, S41 and S43 can be implemented independently, or can be combined with any other step in the embodiments of the present disclosure and implemented together, for example, S21 in the embodiments of the present disclosure and implemented together, and the embodiments of the present disclosure are not limited thereto.

[0233] By implementing the embodiments of the present disclosure, the terminal device receives configuration information sent by the network side device, determines the trigger condition based on the configuration information, including a trigger condition, and reports flight path information to the network side device in response to satisfying the trigger condition, thereby supporting the terminal device to actively report flight path information, enabling the network side device to perform mobility management based on the flight path information, preventing the network side device from configuring mobility according to an incorrect flight path previously reported by the terminal device, improving the reliability of the mobility configuration, and preventing the terminal device from failing to switch cells.

[0234] Please refer to FIG. 5, which is a flowchart of another route reporting method provided by an embodiment of the present disclosure.

[0235] As shown in FIG. 5, the method is performed by a terminal device, and the method may include, but is not limited to, the following steps: S51: In response to the flight route being invalid, report flight route invalid instruction information to the network side device.

[0236] In an embodiment of the present disclosure, the terminal device responds to the invalidation of the flight path by reporting invalid indication information of the flight path to the network side device.

[0237] It can be understood that the terminal device can determine the invalidity of the flight path, and determine that the current flight path for the terminal device is different (there is a deviation) from the flight path previously reported, and the flight path previously reported can no longer be applied to the current flight process.

[0238] It can be understood that the network side device receives the invalid indication information of the flight path reported by the terminal device, and can determine that the flight path reported by the terminal device is already invalid, and can cancel the mobility configuration according to the incorrect flight path reported last time, and further can improve the reliability of the mobility configuration and avoid the cell switching failure of the terminal device.

[0239] It should be noted that in the embodiments of the present disclosure, S51 can be performed alone, or can be combined with any other step in the embodiments of the present disclosure, for example, S21 and / or S31 and S33 and / or S41 and S43 in the embodiments of the present disclosure, and the embodiments of the present disclosure are not limited thereto.

[0240] By implementing the embodiments of the present disclosure, the terminal device reports flight path invalid indication information to the network side device in response to the invalidation of the flight path, thereby supporting the terminal device to actively report flight path information, allowing the network side device to perform mobility management based on the flight path information, preventing the network side device from performing mobility configuration according to the incorrect flight path previously reported by the terminal device, improving the reliability of mobility configuration, and avoiding cell switching failure of the terminal device.

[0241] Please refer to FIG. 6, which is a flowchart of another route reporting method provided by an embodiment of the present disclosure.

[0242] As shown in FIG. 6, the method is performed by a terminal device, and the method may include, but is not limited to, the following steps: S61: In response to the flight route update, report flight route invalid instruction information to the network side device.

[0243] In an embodiment of the present disclosure, the terminal device reports invalid indication information of the flight path to the network side device in response to updating the flight path.

[0244] It can be understood that when the terminal device decides to update the flight path, it can re-update a new flight path, and the updated new flight path may differ (there may be deviations) from the previously reported flight path.

[0245] It can be understood that the network side device receives the invalid indication information of the flight path reported by the terminal device, and can determine that the flight path reported by the terminal device is already invalid, and can cancel the mobility configuration according to the incorrect flight path reported last time, and further can improve the reliability of the mobility configuration and avoid the cell switching failure of the terminal device.

[0246] It should be noted that in the embodiments of the present disclosure, S61 can be performed alone, or can be combined and performed together with any other step in the embodiments of the present disclosure, for example, S21 and / or S31 and S33 and / or S41 and S43 in the embodiments of the present disclosure, and the embodiments of the present disclosure are not limited thereto.

[0247] By implementing the embodiments of the present disclosure, the terminal device reports invalid indication information of the flight path to the network side device in response to updating the flight path, thereby supporting the terminal device to actively report flight path information, allowing the network side device to perform mobility management based on the flight path information, preventing the network side device from configuring mobility according to the incorrect flight path previously reported by the terminal device, improving the reliability of the mobility configuration, and preventing the terminal device from failing to switch cells.

[0248] Please refer to FIG. 7, which is a flowchart of another route reporting method provided by an embodiment of the present disclosure.

[0249] As shown in FIG. 7, the method is performed by a terminal device, and the method may include, but is not limited to, the following steps: S71: In response to a change from flight according to a planned route to control by an operator by a terminal device, report invalid instruction information of the flight route to a network side device.

[0250] In an embodiment of the present disclosure, the terminal device reports flight path invalid instruction information to the network side device in response to the terminal device converting flight from following the planned path to operator control.

[0251] It can be understood that the terminal device converts flight according to a planned path to control by the operator, and since the operator controls the flight path of the terminal device, it may differ significantly from the flight path reported by the terminal device.

[0252] It can be understood that the network side device receives the invalid indication information of the flight path reported by the terminal device, and can determine that the flight path reported by the terminal device is already invalid, and can cancel the mobility configuration according to the incorrect flight path reported last time, and further can improve the reliability of the mobility configuration and avoid the cell switching failure of the terminal device.

[0253] It should be noted that in the embodiments of the present disclosure, S71 can be performed alone or in combination with any other step in the embodiments of the present disclosure, for example, S21 and / or S31 and S33 and / or S41 and S43 in the embodiments of the present disclosure, and the embodiments of the present disclosure are not limited thereto.

[0254] By implementing the embodiments of the present disclosure, the terminal device reports invalid flight path instruction information to the network side device in response to the terminal device changing from flight according to a planned path to control by an operator, thereby supporting the terminal device to actively report flight path information, allowing the network side device to perform mobility management based on the flight path information, preventing the network side device from performing mobility configuration according to the incorrect flight path previously reported by the terminal device, improving the reliability of mobility configuration, and preventing the terminal device from failing to switch cells.

[0255] Please refer to FIG. 8, which is a flowchart of another route reporting method provided by an embodiment of the present disclosure.

[0256] As shown in FIG. 8, the method is performed by a terminal device, and the method may include, but is not limited to, the following steps: S81: In response to the flight route update, report the updated flight route to the network side device.

[0257] In an embodiment of the present disclosure, the terminal device responds to the flight route update by reporting the updated flight route to the network side device.

[0258] It can be understood that when the terminal device decides to update the flight path, it can re-update a new flight path, and the updated new flight path may differ (there may be deviations) from the previously reported flight path.

[0259] It can be understood that the network side device can receive the updated flight path reported by the terminal device, determine the updated flight path by the terminal device, cancel the mobility configuration according to the previously reported incorrect flight path, and configure mobility according to the updated flight path, thereby improving the reliability of the mobility configuration and avoiding cell switching failure of the terminal device.

[0260] In some embodiments, the flight path includes at least one of a flight waypoint, a plurality of flight waypoints, a timestamp, and a plurality of timestamps.

[0261] In an embodiment of the present disclosure, when the terminal device meets a trigger condition, it reports flight path information to the network side device, and the flight path information may be a flight path, and the flight path includes one flight waypoint.

[0262] In an embodiment of the present disclosure, when the terminal device meets a trigger condition, it reports flight path information to the network side device, and the flight path information may be a flight path, and the flight path includes a plurality of flight waypoints.

[0263] In an embodiment of the present disclosure, when the terminal device meets the trigger condition, it reports flight path information to the network side device, and the flight path information may be a flight path, and the flight path includes a timestamp.

[0264] In an embodiment of the present disclosure, when the terminal device meets a trigger condition, it reports flight path information to the network side device, and the flight path information may be a flight path, and the flight path includes multiple timestamps.

[0265] It should be noted that the above-described embodiments are not particularly limiting but merely serve as examples of some of the embodiments, and the above-described embodiments can be implemented singly or in combination with one another. The above-described embodiments are merely examples and do not specifically limit the scope of protection of the embodiments of the present disclosure.

[0266] In some embodiments, the timestamp is the difference between the time when the terminal device arrives at the corresponding flight waypoint and the current time, or the time when the terminal device arrives at the corresponding flight waypoint, or the difference between the time when the terminal device arrives at the corresponding flight waypoint and the time when the terminal device arrives at the previous flight waypoint.

[0267] In an embodiment of the present disclosure, the timestamp is the difference between the time when the terminal device arrives at the corresponding flight waypoint and the current time.

[0268] For example, if the time when the terminal device will arrive at the corresponding flight waypoint is 11 AM (11 o'clock in the morning) and the current time is 8 AM, the timestamp is the difference of 4 hours between the time when the terminal device will arrive at the corresponding flight waypoint (11 AM) and the current time (8 AM).

[0269] In an embodiment of the present disclosure, the timestamp is the time at which the terminal device arrives at the corresponding flight waypoint.

[0270] Illustratively, if the time when the terminal device arrives at the corresponding flight waypoint is 11 AM (11 o'clock in the morning), the timestamp is the time when the terminal device arrives at the corresponding flight waypoint, which is 11 AM.

[0271] In an embodiment of the present disclosure, the timestamp is the difference between the time when the terminal device arrives at the corresponding flight waypoint and the time when it arrives at the previous flight waypoint.

[0272] For example, if the time at which the terminal device arrives at the corresponding flight waypoint is 11 AM (11 a.m.) and the time at which the terminal device arrives at the previous flight waypoint is 10 AM, the timestamp is the 1-hour difference between the time at which the terminal device arrives at the corresponding flight waypoint (11 AM) and the time at which the terminal device arrives at the previous flight waypoint (10 AM).

[0273] It should be noted that in the embodiments of the present disclosure, S81 can be performed alone, or can be combined and performed together with any other step in the embodiments of the present disclosure, for example, S21 and / or S31 and S33 and / or S41 and S43 in the embodiments of the present disclosure, and the embodiments of the present disclosure are not limited thereto.

[0274] By implementing the embodiments of the present disclosure, the terminal device reports the updated flight path to the network side device in response to updating the flight path, thereby supporting the terminal device to actively report flight path information, allowing the network side device to perform mobility management based on the flight path information, preventing the network side device from configuring mobility according to the incorrect flight path previously reported by the terminal device, improving the reliability of the mobility configuration, and preventing the terminal device from failing to switch cells.

[0275] Please refer to FIG. 9, which is a flowchart of another route reporting method provided by an embodiment of the present disclosure.

[0276] As shown in FIG. 9, the method is performed by a terminal device, and the method may include, but is not limited to, the following steps: S91: In response to an offset between the current flight path and the reported flight path, report an updated flight path to the network side device.

[0277] In an embodiment of the present disclosure, the terminal device reports an updated flight path to the network side device in response to the existence of an offset between the current flight path and the reported flight path.

[0278] It can be understood that the network side device can receive the updated flight path reported by the terminal device, determine the updated flight path by the terminal device, cancel the mobility configuration according to the previously reported incorrect flight path, and configure mobility according to the updated flight path, thereby improving the reliability of the mobility configuration and avoiding cell switching failure of the terminal device.

[0279] In an embodiment of the present disclosure, the existence of an offset between the current flight path and the reported flight path includes at least one of: the distance between flight waypoints corresponding to the same time point for the current flight path and the previously reported flight path is greater than a first threshold; the time difference to reach the same flight waypoint for the current flight path and the previously reported flight path is greater than a second threshold; the absolute value of the difference in flight speed at the same time point for the current flight path and the previously reported flight path is greater than a third threshold; and the flight direction at the same time point for the current flight path and the previously reported flight path has changed.

[0280] In an embodiment of the present disclosure, the terminal device may report an updated flight path to the network side device in response to the existence of an offset between the current flight path and the reported flight path, and may report the updated flight path to the network side device if the distance between flight waypoints corresponding to the same time point for the current flight path and the previously reported flight path is greater than a first threshold.

[0281] In an embodiment of the present disclosure, the terminal device may report an updated flight path to the network side device in response to the existence of an offset between the current flight path and the reported flight path, and may report the updated flight path to the network side device if the time difference between reaching the same flight waypoint for the current flight path and the previously reported flight path is greater than a second threshold.

[0282] In an embodiment of the present disclosure, the terminal device may report an updated flight path to the network side device in response to the existence of an offset between the current flight path and the reported flight path, and may report the updated flight path to the network side device if the absolute value of the difference in flight speed at the same time between the current flight path and the previously reported flight path is greater than a third threshold.

[0283] In an embodiment of the present disclosure, the terminal device may report an updated flight path to the network side device in response to the existence of an offset between the current flight path and the reported flight path, and may report the updated flight path to the network side device if a change occurs in the flight direction at the same time for the current flight path and the previously reported flight path.

[0284] It can be understood that the flight direction changes at the same time for the current flight path and the previously reported flight path, for example, the aspect in which the flight direction has changed is greater than the fourth threshold.

[0285] It should be noted that the above-described embodiments are not particularly limiting but merely serve as examples of some of the embodiments, and the above-described embodiments can be implemented singly or in combination with one another. The above-described embodiments are merely examples and do not specifically limit the scope of protection of the embodiments of the present disclosure.

[0286] In the embodiments of the present disclosure, the relevant description of the flight path can be referred to the relevant description in the above embodiments, and will not be further described here.

[0287] It should be noted that in the embodiments of the present disclosure, S91 can be performed alone, or can be combined with any other step in the embodiments of the present disclosure, for example, S21 and / or S31 and S33 and / or S41 and S43 in the embodiments of the present disclosure, and the embodiments of the present disclosure are not limited thereto.

[0288] By implementing the embodiments of the present disclosure, the terminal device reports an updated flight path to the network side device in response to the existence of an offset between the current flight path and the reported flight path, thereby supporting the terminal device to actively report flight path information, allowing the network side device to perform mobility management based on the flight path information, preventing the network side device from performing mobility configuration according to the incorrect flight path previously reported by the terminal device, improving the reliability of the mobility configuration, and preventing the terminal device from failing to switch cells.

[0289] Please refer to FIG. 10, which is a flowchart of another route reporting method provided by an embodiment of the present disclosure.

[0290] As shown in FIG. 10, the method is performed by a terminal device, and the method may include, but is not limited to, the following steps: S101: In response to a terminal device converting flight from following a planned route to control by an operator, report a flight direction to a network-side device.

[0291] In an embodiment of the present disclosure, the terminal device reports a flight direction to the network-side device in response to the terminal device converting from flight according to a planned route to control by an operator.

[0292] It can be understood that the network side device can determine that the flight direction reported by the receiving terminal device, the flight path reported by the terminal device is already invalid, and can cancel the mobility configuration according to the incorrect flight path reported last time, so that the network side device can avoid the terminal device from configuring mobility according to the incorrect flight path reported last time, thereby improving the reliability of the mobility configuration and avoiding cell switching failure of the terminal device.

[0293] In an embodiment of the present disclosure, the terminal device, in response to the terminal device converting from flight following a planned route to control by an operator, reports a flight direction to the network side device and reports position information to the network side device.

[0294] It should be noted that in the embodiments of the present disclosure, S101 can be performed alone, or can be combined and performed together with any other step in the embodiments of the present disclosure, for example, S21 and / or S31 and S33 and / or S41 and S43 in the embodiments of the present disclosure, and the embodiments of the present disclosure are not limited thereto.

[0295] By implementing the embodiments of the present disclosure, the terminal device reports a flight direction to the network side device in response to the terminal device changing from flight according to a planned route to control by an operator, thereby supporting the terminal device to actively report flight route information, allowing the network side device to perform mobility management based on the flight route information, preventing the network side device from performing mobility configuration according to an incorrect flight route previously reported by the terminal device, improving the reliability of mobility configuration, and preventing the terminal device from failing to switch cells.

[0296] Please refer to FIG. 11, which is a flowchart of another route reporting method provided by an embodiment of the present disclosure.

[0297] As shown in FIG. 11, the method is performed by a terminal device, and the method may include, but is not limited to, the following steps: S111: In response to meeting a measurement reporting event, report a measurement report to a network side device.

[0298] In an embodiment of the present disclosure, if the terminal device meets a trigger condition, it can report flight path information to the network side device, and the trigger condition may be a measurement reporting event.

[0299] Illustratively, measurement reporting events include, for example, A1-A6, B1-B2, D1, T1, etc., where A series events are used for intra-system mobility management, and B series events are used for inter-system mobility management. D1 and T1 are used for satellite system mobility management. The A series reporting events are as follows: Event A1: Serving becomes better than absolute threshold; Event A2: Serving becomes worse than absolute threshold; Event A3: Neighbor becomes better than PCell / PSCell (event A3: signal quality of neighbor cell + offset amount is better than signal quality of primary cell); Event A4: Neighbor becomes better than absolute threshold; Event A5: PCell / PSCell becomes worse than absolute threshold1 AND Neighbor / SCell becomes better than another absolute threshold2 (Event A5: The signal quality of the primary cell is lower than threshold1, and at the same time, the signal quality of the neighbor cell is higher than threshold2); Event A6: Neighbor becomes amount of offset better than SCell.

[0300] In an embodiment of the present disclosure, the trigger condition may be a measurement reporting event, and when the terminal device meets the measurement reporting event, it can report a measurement report to the network side device, and the measurement report may include flight path information.

[0301] It can be understood that the network side device can receive the flight path information reported by the terminal device, determine the flight path reported by the terminal device, perform mobility configuration based on the flight path reported by the terminal device, improve the reliability of the mobility configuration, and avoid cell switching failure of the terminal device.

[0302] It should be noted that in the embodiments of the present disclosure, S111 can be performed alone, or can be combined with any other step in the embodiments of the present disclosure, for example, S21 and / or S31 and S33 and / or S41 and S43 in the embodiments of the present disclosure, and the embodiments of the present disclosure are not limited thereto.

[0303] By implementing the embodiment of the present disclosure, in response to a terminal device measurement reporting event being satisfied, a step of reporting a measurement report to a network side device, the measurement report including flight path information, thereby supporting the terminal device to actively report flight path information, allowing the network side device to perform mobility management based on the flight path information, preventing the network side device from performing mobility configuration according to an incorrect flight path previously reported by the terminal device, improving the reliability of mobility configuration, and preventing the terminal device from failing to switch cells.

[0304] Referring to FIG. 12, FIG. 12 is a flowchart of another route reporting method provided by an embodiment of the present disclosure.

[0305] As shown in FIG. 12, the method is performed by a terminal device, and the method may include, but is not limited to, the following steps: S121: In response to satisfying a condition that triggers reporting the auxiliary information, report the auxiliary information to a network side device, where the auxiliary information includes flight path information.

[0306] In an embodiment of the present disclosure, when the terminal device meets a condition that triggers reporting auxiliary information, it can report the auxiliary information to the network side device, where the auxiliary information includes flight path information.

[0307] It can be understood that the network side device can receive the flight path information reported by the terminal device, determine the flight path reported by the terminal device, perform mobility configuration based on the flight path reported by the terminal device, improve the reliability of the mobility configuration, and avoid cell switching failure of the terminal device.

[0308] It should be noted that in the embodiments of the present disclosure, S121 can be performed alone, or can be combined with any other step in the embodiments of the present disclosure, for example, S21 and / or S31 and S33 and / or S41 and S43 in the embodiments of the present disclosure, and the embodiments of the present disclosure are not limited thereto.

[0309] By implementing the embodiments of the present disclosure, in response to satisfying a condition triggering the terminal device to report auxiliary information, the auxiliary information includes flight path information, thereby supporting the terminal device to actively report flight path information, allowing the network side device to perform mobility management based on the flight path information, preventing the network side device from performing mobility configuration according to an incorrect flight path previously reported by the terminal device, improving the reliability of mobility configuration, and preventing the terminal device from failing to switch cells.

[0310] Please refer to FIG. 13, which is a flowchart of another route reporting method provided by an embodiment of the present disclosure.

[0311] As shown in FIG. 13, the method is performed by a terminal device, and the method may include, but is not limited to, the following steps: S131: Configured to require reporting of flight path information by a terminal device, and in response to not reporting auxiliary information including the flight path information to the network side device and satisfying a trigger condition, start reporting auxiliary information to the network side device, where the auxiliary information includes the flight path information.

[0312] For the relevant description of the auxiliary information, please refer to the relevant description in the above embodiment, and no further description will be given here.

[0313] In an embodiment of the present disclosure, it is determined that the terminal device is configured to require reporting of flight path information by the terminal device, and if the terminal device does not report auxiliary information including flight path information to the network side device and a trigger condition is met, the terminal device can start reporting auxiliary information to the network side device, where the auxiliary information includes flight path information.

[0314] It can be understood that the network side device can receive the flight path information reported by the terminal device, determine the flight path reported by the terminal device, perform mobility configuration based on the flight path reported by the terminal device, improve the reliability of the mobility configuration, and avoid cell switching failure of the terminal device.

[0315] It should be noted that in the embodiments of the present disclosure, S131 can be performed alone, or can be combined with any other step in the embodiments of the present disclosure, for example, S21 and / or S31 and S33 and / or S41 and S43 in the embodiments of the present disclosure, and the embodiments of the present disclosure are not limited thereto.

[0316] By implementing an embodiment of the present disclosure, a terminal device is configured to require the terminal device to report flight path information, does not report auxiliary information including flight path information to a network side device, and starts reporting auxiliary information to the network side device in response to satisfying a trigger condition, where the auxiliary information includes flight path information, thereby supporting the terminal device to actively report flight path information, enabling the network side device to perform mobility management based on the flight path information, preventing the network side device from performing mobility configuration according to an incorrect flight path previously reported by the terminal device, improving the reliability of mobility configuration, and avoiding cell switch failure of the terminal device.

[0317] Referring to FIG. 14, FIG. 14 is a flowchart of another route reporting method provided by an embodiment of the present disclosure.

[0318] As shown in FIG. 14, the method is performed by a terminal device, and the method may include, but is not limited to, the following steps: S141: Configured to require reporting of flight path information by a terminal device, and in response to satisfying a trigger condition, start reporting auxiliary information to a network side device, where the auxiliary information includes flight path information.

[0319] For the relevant description of the auxiliary information, please refer to the relevant description in the above embodiment, and no further description will be given here.

[0320] In an embodiment of the present disclosure, when it is determined that the terminal device is configured to require flight path information reporting by the terminal device and a trigger condition is met, the terminal device can start reporting auxiliary information to the network side device, where the auxiliary information includes flight path information.

[0321] It can be understood that the network side device can receive the flight path information reported by the terminal device, determine the flight path reported by the terminal device, perform mobility configuration based on the flight path reported by the terminal device, improve the reliability of the mobility configuration, and avoid cell switching failure of the terminal device.

[0322] It should be noted that in the embodiments of the present disclosure, S141 can be performed alone, or can be combined with any other step in the embodiments of the present disclosure, for example, S21 and / or S31 and S33 and / or S41 and S43 in the embodiments of the present disclosure, and the embodiments of the present disclosure are not limited thereto.

[0323] By implementing an embodiment of the present disclosure, a terminal device is configured to require the terminal device to report flight path information, and starts reporting auxiliary information to a network side device in response to satisfying a trigger condition, where the auxiliary information includes flight path information, thereby supporting the terminal device to actively report flight path information, allowing the network side device to perform mobility management based on the flight path information, preventing the network side device from performing mobility configuration according to an incorrect flight path previously reported by the terminal device, improving the reliability of mobility configuration, and avoiding cell switching failure of the terminal device.

[0324] Referring to FIG. 15, FIG. 15 is a flowchart of another route reporting method provided by an embodiment of the present disclosure.

[0325] As shown in FIG. 15 , the method is performed by a network side device, and the method may include, but is not limited to, the following steps: S151: Receive flight path information reported by a terminal device when a trigger condition is met.

[0326] In the embodiment of the present disclosure, when the terminal device meets the trigger condition, it can actively report the flight path information to the network side device.

[0327] The terminal device may determine the trigger condition based on a protocol agreement, or may determine the trigger condition based on the implementation of the terminal device, or may determine the trigger condition based on a network-side device instruction, or may jointly determine the trigger condition based on the implementation of the terminal device and the protocol agreement, or may jointly determine the trigger condition based on the implementation of the terminal device and the network-side device instruction, or may jointly determine the trigger condition based on the protocol agreement and the network-side device instruction, and the embodiments of the present disclosure are not limited thereto.

[0328] Exemplarily, the trigger condition or trigger condition parameter may be set by the network side device, or may be specified by a protocol, or may be determined based on the implementation of the terminal device.

[0329] Illustratively, the terminal device may determine whether the trigger condition is met based on the terminal implementation or the network side setting or the protocol specification.

[0330] Illustratively, the terminal device may determine whether to report flight path information based on the implementation of the terminal.

[0331] For example, the trigger condition setting may be stipulated by a protocol, the setting information sent by the network side device may include a threshold or related parameter corresponding to the trigger condition setting, and the terminal device may determine the trigger condition based on the trigger condition setting and the threshold or related parameter corresponding to the trigger condition setting.

[0332] Illustratively, a trigger condition setting may be stipulated by a protocol, and a threshold or related parameter corresponding to the trigger condition setting may be stipulated by the protocol.

[0333] It can be understood that after the terminal device reports a flight path to the network side device, a change in the flight path may occur, and the network side device cannot know the changed flight path information of the terminal device, and the terminal device will always perform mobility configuration according to the flight path previously reported, which will affect the reliability of the subsequent mobility configuration of the network side device and may cause cell switching failure.

[0334] Similarly, the flight of the terminal device can further be converted from being flown according to a plan to being controlled by an operator, and the flight path previously reported by the terminal device will also become invalid, so at this time the terminal device needs to further inform the network side device, otherwise the network side device may make subsequent mobility configurations for the terminal device based on the flight path reported by the terminal device, thereby affecting the reliability of the subsequent mobility configurations and possibly causing cell switching failures.

[0335] In an embodiment of the present disclosure, the terminal device can actively report flight path information to the network side device if a trigger condition is met, and the trigger condition may be any condition that can indicate that the previously reported flight path is invalid or needs to be updated.

[0336] Exemplarily, the trigger condition may be that the flight path last reported by the terminal device is invalid, or the flight path last reported is updated, or the terminal device converts from flying according to a planned path to being controlled by an operator, or there is an offset between the current flight path and the flight path last reported, etc.

[0337] Of course, the trigger conditions are not limited to the above examples, and any trigger condition that can indicate that the previously reported flight path is invalid or needs to be updated falls within the scope of protection of the embodiments of the present disclosure, and the embodiments of the present disclosure are not limited in this regard.

[0338] In an embodiment of the present disclosure, if the terminal device meets the trigger condition, it reports the flight path information to the network side device.

[0339] For example, the flight path information may be a flight path (an updated flight path or a new flight path), or a flight direction (an updated flight direction or a new flight direction), or a flight path validity indication information for indicating that the previously reported flight path is accurate, or a flight path invalidity indication information for indicating that the previously reported flight path is incorrect (already invalid), etc.

[0340] Illustratively, the flight path invalidation indication may be a display indication or an implicit indication.

[0341] Implicit indication information includes any information or message that can implicitly indicate said meaning.

[0342] For example, when the flight path information is a flight path, the flight path may be a planned flight path, and the planned flight path may be a flight path for a certain time in the future, that is, the terminal device can inform the network side device of the flight path of the terminal device within a certain time in the future, and the network side device can perform mobility configuration based on the flight path information reported by the terminal device, for example, determine which cell is suitable for the terminal device to access at a certain time in the future based on the flight path information reported by the terminal device, and the terminal device performs cell switching in advance to transfer the context of the terminal device, etc.

[0343] It can be understood that when the flight path information is a flight path, the terminal device meets the trigger condition, and the trigger condition being the invalidity of the flight path can be understood to be the invalidity of the previously reported flight path, and based on this, the terminal device can report flight path information which is a flight path to the network side device when the previously reported flight path is invalid, and the flight path information is a flight path, and the reported flight path is different from the previously reported flight path.

[0344] It can be understood that when the flight path information is a flight path, the terminal device meets the trigger condition, and the trigger condition is flight path update, it can be understood that the terminal device updates a new flight path based on the flight path previously reported, and based on this, the terminal device can report flight path information, which is a flight path, to the network side device if the flight path previously reported has already been updated, and the flight path information is a flight path, and the reported flight path is different from the flight path previously reported.

[0345] In addition, the terminal device can update the flight route of the previously reported network side device based on the implementation, the configuration of the network side device, or the protocol agreement, etc., and the terminal device can determine whether an update has occurred to the flight route of the previously reported network side device. After the terminal device updates the flight route of the previously reported network side device, it can obtain the updated flight route.

[0346] In an embodiment of the present disclosure, when the terminal device determines that the previously reported flight path is no longer applicable, the terminal device can actively report flight path information to the network side device, thereby supporting the terminal device to actively report flight path information, allowing the network side device to perform mobility management based on the flight path information, preventing the network side device from configuring mobility according to the incorrect flight path previously reported by the terminal device, improving the reliability of mobility configuration, and avoiding cell switching failure of the terminal device.

[0347] In an embodiment of the present disclosure, the trigger condition may be one or more measurement reporting events, and when the terminal device meets the measurement reporting event, it can report a measurement report to the network side device, and the measurement report may include flight path information.

[0348] In an embodiment of the present disclosure, the trigger condition may be a condition that triggers reporting of the auxiliary information of the auxiliary information, and when the terminal device satisfies the condition that triggers reporting of the auxiliary information, it can report the auxiliary information to the network side device, and the auxiliary information may include flight path information.

[0349] Based on this, the terminal device supports actively reporting flight path information, and the network side device can perform mobility management based on the flight path information, which can prevent the network side device from performing mobility configuration according to the incorrect flight path previously reported by the terminal device, improve the reliability of the mobility configuration, and avoid cell switching failure of the terminal device.

[0350] In some embodiments, the flight path information includes at least one of a flight path valid indication, a flight path invalid indication, a flight path, and a flight direction.

[0351] In the embodiment of the present disclosure, when the terminal device meets the trigger condition, it reports flight path information to the network side device, and the flight path information may be valid indication information of the flight path.

[0352] It can be understood that the terminal device reports flight path validity indication information to the network side device to indicate that the previously reported flight path is valid, and based on this, the network side device can continuously perform mobility management based on the flight path previously reported by the terminal device.

[0353] In an embodiment of the present disclosure, when the terminal device meets the trigger condition, it reports flight path information to the network side device, and the flight path information may be flight path invalid indication information.

[0354] It can be understood that the terminal device reports flight path invalid indication information to the network side device, indicating that the previously reported flight path is already invalid; based on this, the network side device can stop or cancel the terminal device from performing mobility management based on the previously reported flight path, thereby preventing the network side device from performing mobility configuration according to the incorrect flight path previously reported by the terminal device, thereby improving the reliability of the mobility configuration and avoiding cell switching failure of the terminal device.

[0355] The trigger condition is that if the terminal device determines that the last reported flight path is invalid, and / or the last reported flight path is updated, and / or the terminal device converts from flying according to a planned path to being controlled by an operator, and / or there is an offset between the current flight path and the last reported flight path, then the terminal device can report flight path invalid indication information to the network side device, indicating that the last reported flight path is already invalid.

[0356] In an embodiment of the present disclosure, when the terminal device meets the trigger condition, it reports flight path information to the network side device, and the flight path information may be a flight path (a new flight path or an updated flight path).

[0357] It can be understood that the terminal device reports a flight path to the network side device to indicate the flight path of the terminal device within a certain period of time in the future, and based on this, the network side device can determine the flight path of the terminal device and perform mobility management based on the flight path.

[0358] The trigger condition is that the terminal device's previously reported flight path is invalid, and / or the previously reported flight path has been updated, and / or the terminal device has converted from flying according to a planned path to being controlled by an operator, and / or there is an offset between the current flight path and the previously reported flight path. If it is determined that the terminal device satisfies the trigger condition, it can report the flight path to the network side device and instruct the updated flight path, and the updated flight path is different from the previously reported flight path, thereby preventing the network side device from performing mobility configuration according to the incorrect flight path previously reported by the terminal device, thereby improving the reliability of the mobility configuration and avoiding cell switching failure of the terminal device.

[0359] In an embodiment of the present disclosure, when the terminal device meets the trigger condition, it reports flight path information to the network side device, and the flight path information may be a flight direction (a new flight direction or an updated flight direction).

[0360] It should be noted that the above-described embodiments are not particularly limiting but merely serve as examples of some of the embodiments, and the above-described embodiments can be implemented singly or in combination with one another. The above-described embodiments are merely examples and do not specifically limit the scope of protection of the embodiments of the present disclosure.

[0361] In some embodiments, the flight path includes at least one of a flight waypoint, a plurality of flight waypoints, a timestamp, and a plurality of timestamps.

[0362] In an embodiment of the present disclosure, when the terminal device meets a trigger condition, it reports flight path information to the network side device, and the flight path information may be a flight path, and the flight path includes one flight waypoint.

[0363] In an embodiment of the present disclosure, when the terminal device meets a trigger condition, it reports flight path information to the network side device, and the flight path information may be a flight path, and the flight path includes a plurality of flight waypoints.

[0364] In an embodiment of the present disclosure, when the terminal device meets the trigger condition, it reports flight path information to the network side device, and the flight path information may be a flight path, and the flight path includes a timestamp.

[0365] In an embodiment of the present disclosure, when the terminal device meets a trigger condition, it reports flight path information to the network side device, and the flight path information may be a flight path, and the flight path includes multiple timestamps.

[0366] It should be noted that the above-described embodiments are not particularly limiting but merely serve as examples of some of the embodiments, and the above-described embodiments can be implemented singly or in combination with one another. The above-described embodiments are merely examples and do not specifically limit the scope of protection of the embodiments of the present disclosure.

[0367] In some embodiments, the timestamp is the difference between the time when the terminal device arrives at the corresponding flight waypoint and the current time, or the time when the terminal device arrives at the corresponding flight waypoint (e.g., UTC time), or the difference between the time when the terminal device arrives at the corresponding flight waypoint and the previous flight waypoint.

[0368] In an embodiment of the present disclosure, the timestamp is the difference between the time when the terminal device arrives at the corresponding flight waypoint and the current time.

[0369] For example, if the time when the terminal device will arrive at the corresponding flight waypoint is 11 AM (11 o'clock in the morning) and the current time is 8 AM, the timestamp is the difference of 4 hours between the time when the terminal device will arrive at the corresponding flight waypoint (11 AM) and the current time (8 AM).

[0370] In an embodiment of the present disclosure, the timestamp is the time at which the terminal device arrives at the corresponding flight waypoint.

[0371] Illustratively, if the time when the terminal device arrives at the corresponding flight waypoint is 11 AM (11 o'clock in the morning), the timestamp is the time when the terminal device arrives at the corresponding flight waypoint, which is 11 AM.

[0372] In an embodiment of the present disclosure, the timestamp is the difference between the time when the terminal device arrives at the corresponding flight waypoint and the time when it arrives at the previous flight waypoint.

[0373] For example, if the time at which the terminal device arrives at the corresponding flight waypoint is 11 AM (11 a.m.) and the time at which the terminal device arrives at the previous flight waypoint is 10 AM, the timestamp is the 1-hour difference between the time at which the terminal device arrives at the corresponding flight waypoint (11 AM) and the time at which the terminal device arrives at the previous flight waypoint (10 AM).

[0374] In some embodiments, the trigger condition includes at least one of a flight path invalidation, a flight path update, the terminal device converting from flying according to a planned path to being controlled by an operator, and an offset existing between the current flight path and the reported flight path.

[0375] In an embodiment of the present disclosure, when the terminal device meets a trigger condition, it reports flight path information to the network side device, and the trigger condition is that the flight path is invalid, so that when the terminal device meets that the flight path is invalid, it can report flight path information to the network side device.

[0376] In an embodiment of the present disclosure, when a terminal device meets a trigger condition, it reports flight path information to a network side device, and the trigger condition is a flight path update, so that when the terminal device meets the flight path update, it can report flight path information to the network side device.

[0377] In an embodiment of the present disclosure, when the terminal device satisfies a trigger condition, it reports flight path information to the network side device, and the trigger condition is that the terminal device is converted from flying according to a planned route to being controlled by an operator, so that when the terminal device satisfies that the terminal device is converted from flying according to a planned route to being controlled by an operator, it can report flight path information to the network side device.

[0378] In an embodiment of the present disclosure, when the terminal device satisfies a trigger condition, it reports flight path information to the network side device, and the trigger condition is that there is an offset between the current flight path and the reported flight path, so that when the terminal device satisfies that there is an offset between the current flight path and the reported flight path, it can report flight path information to the network side device.

[0379] It should be noted that the above-described embodiments are not particularly limiting but merely serve as examples of some of the embodiments, and the above-described embodiments can be implemented singly or in combination with one another. The above-described embodiments are merely examples and do not specifically limit the scope of protection of the embodiments of the present disclosure.

[0380] In some examples, the existence of an offset between the current flight path and the reported flight path includes at least one of: the distance between flight waypoints corresponding to the same time point for the current flight path and the previously reported flight path is greater than a first threshold; the time difference to reach the same flight waypoint for the current flight path and the previously reported flight path is greater than a second threshold; the absolute value of the difference in flight speed for the same time point for the current flight path and the previously reported flight path is greater than a third threshold; and a change in flight direction for the same time point for the current flight path and the previously reported flight path.

[0381] In an embodiment of the present disclosure, the terminal device may report an updated flight path to the network side device in response to the existence of an offset between the current flight path and the reported flight path, and may report the updated flight path to the network side device if the distance between flight waypoints corresponding to the same time point for the current flight path and the previously reported flight path is greater than a first threshold.

[0382] The flight waypoints may be three-dimensional position information of the terminal device, and the distances between flight waypoints corresponding to the same time point may be distances in 3D space.

[0383] In an embodiment of the present disclosure, the terminal device may report an updated flight path to the network side device in response to an offset between the current flight path and the reported flight path, and may report the updated flight path to the network side device if a time difference between the current flight path and the previously reported flight path to reach the same flight waypoint is greater than a second threshold. In an embodiment of the present disclosure, the terminal device may report an updated flight path to the network side device in response to an offset between the current flight path and the reported flight path, and may report the updated flight path to the network side device if an absolute value of a difference in flight speed at the same time between the current flight path and the previously reported flight path is greater than a third threshold.

[0384] In an embodiment of the present disclosure, the terminal device may report an updated flight path to the network side device in response to the existence of an offset between the current flight path and the reported flight path, and may report the updated flight path to the network side device if a change occurs in the flight direction at the same time for the current flight path and the previously reported flight path.

[0385] It can be understood that the flight direction changes at the same time for the current flight path and the previously reported flight path, for example, the aspect in which the flight direction has changed is greater than the fourth threshold.

[0386] It should be noted that the above-described embodiments are not particularly limiting but merely serve as examples of some of the embodiments, and the above-described embodiments can be implemented singly or in combination with one another. The above-described embodiments are merely examples and do not specifically limit the scope of protection of the embodiments of the present disclosure.

[0387] In some embodiments, the network side device sends configuration information to the terminal device, where the configuration information includes at least one of a trigger condition, a report content indication, and a trigger condition parameter.

[0388] In an embodiment of the present disclosure, the network side device sends configuration information to the terminal device, and the configuration information includes a trigger condition, so that the terminal device can determine the trigger condition based on the configuration information.

[0389] In an embodiment of the present disclosure, the network side device sends configuration information to the terminal device, and the configuration information includes a report content instruction.

[0390] In an embodiment of the present disclosure, the network side device sends configuration information to the terminal device, and the configuration information includes a trigger condition parameter.

[0391] Illustratively, the trigger condition parameter is a first threshold value.

[0392] Illustratively, the trigger condition parameter is a second threshold value.

[0393] Illustratively, the trigger condition parameter is a third threshold value.

[0394] Illustratively, the trigger condition parameter is a fourth threshold value.

[0395] It should be noted that the above-described embodiments are not particularly limiting but merely serve as examples of some of the embodiments, and the above-described embodiments can be implemented singly or in combination with one another. The above-described embodiments are merely examples and do not specifically limit the scope of protection of the embodiments of the present disclosure.

[0396] For example, the setting information may be display instruction information or implicit instruction information.

[0397] Implicit indication information includes any information or message that can implicitly indicate said meaning.

[0398] In some examples, the reporting content instructions include at least one of: report a flight path; do not report a flight path; a maximum number of reportable waypoints; a timestamp must be reported; a timestamp does not need to be reported; a flight path validity indication must be reported; and a flight path validity indication does not need to be reported.

[0399] In an embodiment of the present disclosure, the network side device sends configuration information to the terminal device, where the configuration information includes a report content instruction, and the report content instruction includes reporting a flight path.

[0400] In an embodiment of the present disclosure, the network side device sends configuration information to the terminal device, where the configuration information includes a report content instruction, and the report content instruction includes not reporting the flight path.

[0401] In an embodiment of the present disclosure, the network side device sends configuration information to the terminal device, where the configuration information includes a report content instruction, and the report content instruction includes the number of maximum reportable waypoints.

[0402] In an embodiment of the present disclosure, the network side device sends configuration information to the terminal device, where the configuration information includes a report content instruction, and the report content instruction includes that a timestamp needs to be reported.

[0403] In an embodiment of the present disclosure, the network side device sends configuration information to the terminal device, where the configuration information includes a report content instruction, and the report content instruction includes that a timestamp does not need to be reported.

[0404] In an embodiment of the present disclosure, the network side device sends configuration information to the terminal device, where the configuration information includes a report content instruction, and the report content instruction includes that flight path validity instruction information needs to be reported.

[0405] In an embodiment of the present disclosure, the network side device sends configuration information to the terminal device, where the configuration information includes a reporting content instruction, and the reporting content instruction includes that there is no need to report flight path validity indication information.

[0406] It should be noted that the above-described embodiments are not particularly limiting but merely serve as examples of some of the embodiments, and the above-described embodiments can be implemented singly or in combination with one another. The above-described embodiments are merely examples and do not specifically limit the scope of protection of the embodiments of the present disclosure.

[0407] In an embodiment of the present disclosure, a terminal device receives configuration information sent by a network-side device, and the configuration information includes a trigger condition, so that the terminal device can determine the trigger condition based on the configuration information.

[0408] In an embodiment of the present disclosure, a terminal device receives configuration information sent by a network-side device, and the configuration information includes trigger conditions and report content instructions, so that the terminal device can determine the trigger conditions based on the configuration information.

[0409] In an embodiment of the present disclosure, a terminal device receives setting information sent by a network-side device, the setting information includes a reporting content instruction, and the reporting content instruction includes reporting a flight path, whereby the terminal device can determine, based on the setting information, that it is configured to require reporting flight path information.

[0410] The configuration information may be a Radio Resource Control (RRC) message sent by the network side device, and the RRC message may be an RRC reconfiguration message, or may be configured via other configuration information (otherConfig).

[0411] The terminal device can release the above-mentioned configuration information upon RRC reestablishment or RRC recovery.

[0412] In an embodiment of the present disclosure, a terminal device receives configuration information sent by a network-side device, the configuration information includes a reporting content instruction, and the reporting content instruction includes a need to report a timestamp, thereby allowing the terminal device to determine, based on the configuration information, that it is configured to need to report flight path information.

[0413] In an embodiment of the present disclosure, a terminal device receives configuration information sent by a network-side device, the configuration information includes a reporting content instruction, and the reporting content instruction includes a maximum number of reportable waypoints, whereby the terminal device can determine, based on the configuration information, that it is configured to require reporting of flight path information.

[0414] It should be noted that the above-described embodiments are not particularly limiting but merely serve as examples of some of the embodiments, and the above-described embodiments can be implemented singly or in combination with one another. The above-described embodiments are merely examples and do not specifically limit the scope of protection of the embodiments of the present disclosure.

[0415] In some embodiments, the step of the network side device receiving the flight path information reported by the terminal device when the trigger condition is satisfied includes receiving invalidation indication information for the reported flight path when the flight path is invalidated by the terminal device; The method includes receiving invalid indication information for a reported flight path when the flight path is updated by the terminal device, or receiving invalid indication information for a reported flight path when the terminal device converts from flight according to a planned path to control by an operator.

[0416] In an embodiment of the present disclosure, the network side device receives invalid indication information of the flight path reported when the flight path is invalidated by the terminal device.

[0417] It can be understood that the terminal device can determine flight path invalidity and determine that the current flight path for the terminal device is different (there is a deviation) from the flight path previously reported.

[0418] In an embodiment of the present disclosure, the network side device receives invalid indication information of the reported flight path when the flight path is updated by the terminal device.

[0419] It can be understood that when the terminal device decides to update the flight path, it can re-update a new flight path, and the updated new flight path may differ (there may be deviations) from the previously reported flight path.

[0420] In an embodiment of the present disclosure, the network side device receives flight path invalidation indication information reported when the terminal device converts flight from following a planned path to operator control.

[0421] In some embodiments, the step of the network side device receiving the flight path information reported by the terminal device when the trigger condition is satisfied includes receiving an updated flight path reported when the flight path is updated by the terminal device, or receiving an updated flight path reported by the terminal device when there is an offset between the current flight path and the reported flight path.

[0422] In an embodiment of the present disclosure, the network side device receives the updated flight path reported when the flight path is updated by the terminal device.

[0423] It can be understood that when the terminal device decides to update the flight path, it can re-update a new flight path, and the updated new flight path may differ (there may be deviations) from the previously reported flight path.

[0424] In an embodiment of the present disclosure, the network side device receives an updated flight path reported by the terminal device when there is an offset between the current flight path and the reported flight path.

[0425] In some embodiments, the step of the network side device receiving flight path information reported by the terminal device when the trigger condition is satisfied includes receiving a flight direction reported by the terminal device when the terminal device converts from flying according to a planned path to being controlled by an operator.

[0426] In an embodiment of the present disclosure, when the terminal device is converted from flying according to a planned route to being controlled by an operator, the terminal device reports the flight direction to the network-side device.

[0427] It can be understood that determining that the terminal device has converted from flying according to a planned path by the terminal device to being controlled by an operator can be determined based on the implementation of the terminal device, and illustratively can be determined based on the settings of the terminal device itself.

[0428] In some embodiments, the terminal device determines whether the trigger condition is met based on the implementation.

[0429] In some embodiments, the network side device further receives location information reported by the terminal device.

[0430] In the embodiment of the present disclosure, when the terminal device meets the trigger condition, it can also report the flight direction to the network side device and report the location information to the network side device.

[0431] In an embodiment of the present disclosure, the location information may be three-dimensional location information of the terminal device.

[0432] In some embodiments, the trigger condition is a measurement reporting event.

[0433] In the embodiment of the present disclosure, when the terminal device meets a measurement reporting event, it can report flight path information to the network side device.

[0434] Illustratively, the trigger condition may be one or more measurement reporting events.

[0435] Illustratively, measurement reporting events include, for example, A1-A6, B1-B2, D1, T1, etc., where A series events are used for intra-system mobility management, and B series events are used for inter-system mobility management. D1 and T1 are used for satellite system mobility management. The A series reporting events are as follows: Event A1: Serving becomes better than absolute threshold; Event A2: Serving becomes worse than absolute threshold; Event A3: Neighbor becomes better than PCell / PSCell (event A3: signal quality of neighbor cell + offset amount is better than signal quality of primary cell); Event A4: Neighbor becomes better than absolute threshold; Event A5: PCell / PSCell becomes worse than absolute threshold1 AND Neighbor / SCell becomes better than another absolute threshold2 (Event A5: The signal quality of the primary cell is lower than threshold1, and at the same time, the signal quality of the neighbor cell is higher than threshold2); Event A6: Neighbor becomes amount of offset better than SCell.

[0436] Illustratively, the measurement reporting event may also be a condition used to trigger a route report, such as one or more of the following conditions: the flight route last reported by the terminal device is invalid, or the flight route last reported is updated, or the terminal device converts from flying according to a planned route to being controlled by an operator, or there is an offset between the current flight route and the flight route last reported.

[0437] Of course, the measurement reporting events are not limited to the above examples, and any trigger condition that can indicate that the previously reported flight path is invalid or needs to be updated is within the scope of protection of the embodiments of the present disclosure, and the embodiments of the present disclosure are not limited in this regard.

[0438] In some embodiments, the step of the network side device receiving flight path information reported by the terminal device when a trigger condition is satisfied includes the step of receiving a measurement report reported by the terminal device when a measurement reporting event is satisfied, the measurement report including the flight path information.

[0439] In an embodiment of the present disclosure, the trigger condition may be a measurement reporting event, and when the terminal device meets the measurement reporting event, it can report a measurement report to the network side device, and the measurement report may include flight path information.

[0440] In some embodiments, the trigger condition is a condition that triggers reporting of the auxiliary information.

[0441] In the embodiment of the present disclosure, if the terminal device meets a trigger condition, it can report flight path information to the network side device, and the trigger condition may be a condition that triggers reporting auxiliary information.

[0442] In the embodiment of the present disclosure, when the terminal device meets the condition that triggers reporting the assistance information, it reports the assistance information to the network side device.

[0443] Illustratively, the conditions for triggering auxiliary information may be one or more of the following conditions: the flight path last reported by the terminal device is invalid, or the flight path last reported has been updated, or the terminal device has converted from flying according to a planned path to being controlled by an operator, or there is an offset between the current flight path and the flight path last reported, etc.

[0444] Of course, the conditions that trigger the reporting of auxiliary information are not limited to the above examples, and any trigger condition that can indicate that the previously reported flight path is invalid or needs to be updated falls within the scope of protection of the embodiments of the present disclosure, and the embodiments of the present disclosure are not limited in this regard.

[0445] In some embodiments, the step of receiving flight path information reported by the terminal device when a trigger condition is satisfied by the network side device includes receiving the reported auxiliary information when the terminal device satisfies a condition that triggers reporting the auxiliary information, wherein the auxiliary information includes flight path information.

[0446] In an embodiment of the present disclosure, the trigger condition may be a condition that triggers reporting of the auxiliary information of the auxiliary information, and when the terminal device satisfies the condition that triggers reporting of the auxiliary information, it can report the auxiliary information to the network side device, and the auxiliary information may include flight path information.

[0447] Illustratively, the terminal device receives configuration information of the network-side device, and configures the terminal to provide flight path-related information, or the network-side device configures flight path reporting.

[0448] Illustratively, the flight path report is configured via an RRC message, which may be an RRC reconfiguration message, and can be configured by otherConfig.

[0449] Illustratively, upon RRC reestablishment or RRC recovery, the UE releases the flight path reporting configuration.

[0450] In some embodiments, the step of receiving flight path information reported by the terminal device when the trigger condition is satisfied by the network side device is configured to require reporting of the flight path information by the terminal device, and includes a step of not reporting auxiliary information including the flight path information to the network side device and receiving the reported auxiliary information when the trigger condition is satisfied, wherein the auxiliary information includes the flight path information.

[0451] Illustratively, if the terminal is configured to provide flight path-related information, and since it is configured to provide flight path-related information, if the terminal has not transmitted terminal auxiliary information including the flight path-related information, the terminal initiates an auxiliary information transmission flow and transmits the flight path-related information.

[0452] In an embodiment of the present disclosure, the trigger condition may be configured to require the terminal device to report flight path information, not report auxiliary information including flight path information to the network side device, and satisfy the trigger condition; if the terminal device is determined to be configured to require the terminal device to report flight path information, not report auxiliary information including flight path information to the network side device, and satisfy the trigger condition, it can report auxiliary information to the network side device, and the auxiliary information may include flight path information.

[0453] Illustratively, the terminal device is configured to provide flight path-related information, and when a trigger condition or an auxiliary information reporting condition exists, the terminal device initiates an auxiliary information transmission flow and transmits the flight path-related information.

[0454] In some embodiments, the step of receiving flight path information reported by the terminal device when the trigger condition is satisfied by the network side device is configured to require reporting of the flight path information by the terminal device, and includes receiving auxiliary information reported when the trigger condition is satisfied, wherein the auxiliary information includes the flight path information.

[0455] Illustratively, the terminal device initiates an auxiliary information transmission flow, and transmitting the flight path related information includes the flight path related information being included in the terminal device auxiliary information. In an embodiment of the present disclosure, the trigger condition may be configured to require the terminal device to report flight path information, and the trigger condition may be satisfied; if it is determined that the terminal device is configured to require the terminal device to report flight path information, and the trigger condition is satisfied, auxiliary information may be reported to the network side device, and the auxiliary information may include flight path information.

[0456] Based on this, the terminal device supports actively reporting flight path information, and the network side device can perform mobility management based on the flight path information, which can prevent the network side device from performing mobility configuration according to the incorrect flight path previously reported by the terminal device, improve the reliability of the mobility configuration, and avoid cell switching failure of the terminal device.

[0457] Please refer to FIG. 16, which is a flowchart of another route reporting method provided by an embodiment of the present disclosure.

[0458] As shown in FIG. 16 , the method is performed by a network side device, and the method may include, but is not limited to, the following steps: S161: Send setting information to a terminal device, where the setting information includes at least one of the trigger condition, the report content instruction, and the trigger condition parameter.

[0459] In an embodiment of the present disclosure, the network side device sends configuration information to the terminal device, and the configuration information includes a trigger condition.

[0460] In some embodiments, the trigger condition includes at least one of a flight path invalidation, a flight path update, the terminal device converting from flying according to a planned path to being controlled by an operator, and an offset existing between the current flight path and the reported flight path.

[0461] In some examples, the existence of an offset between the current flight path and the reported flight path includes at least one of: the distance between flight waypoints corresponding to the same time point for the current flight path and the previously reported flight path is greater than a first threshold; the time difference to reach the same flight waypoint for the current flight path and the previously reported flight path is greater than a second threshold; the absolute value of the difference in flight speed for the same time point for the current flight path and the previously reported flight path is greater than a third threshold; and a change in flight direction for the same time point for the current flight path and the previously reported flight path.

[0462] It can be understood that the flight direction changes at the same time for the current flight path and the previously reported flight path, for example, the aspect in which the flight direction has changed is greater than the fourth threshold.

[0463] In an embodiment of the present disclosure, the network side device sends configuration information to the terminal device, and the configuration information includes a report content instruction.

[0464] In some examples, the reporting content instructions include at least one of: report a flight path, do not report a flight path, a maximum number of reportable waypoints, a timestamp must be reported, a timestamp does not need to be reported, a flight path validity indication must be reported, and a flight path validity indication does not need to be reported.

[0465] In an embodiment of the present disclosure, the terminal device receives configuration information sent by the network-side device, the configuration information includes a report content instruction, and the report content instruction includes reporting a flight path.

[0466] In an embodiment of the present disclosure, the terminal device receives configuration information sent by the network side device, the configuration information includes a report content instruction, and the report content instruction includes not reporting a flight path.

[0467] In an embodiment of the present disclosure, the terminal device receives configuration information sent by the network-side device, the configuration information includes a report content instruction, and the report content instruction includes the number of maximum reportable waypoints.

[0468] In an embodiment of the present disclosure, the terminal device receives configuration information sent by the network-side device, the configuration information includes a report content instruction, and the report content instruction includes that a timestamp needs to be reported.

[0469] In an embodiment of the present disclosure, the terminal device receives configuration information sent by the network-side device, the configuration information includes a report content instruction, and the report content instruction includes that a timestamp does not need to be reported.

[0470] In an embodiment of the present disclosure, the terminal device receives configuration information sent by the network side device, the configuration information includes a reporting content instruction, and the reporting content instruction includes that flight path validity instruction information needs to be reported.

[0471] In an embodiment of the present disclosure, the terminal device receives configuration information sent by the network side device, the configuration information includes a reporting content instruction, and the reporting content instruction includes that there is no need to report flight path validity instruction information.

[0472] It should be noted that the above-described embodiments are not particularly limiting but merely serve as examples of some of the embodiments, and the above-described embodiments can be implemented singly or in combination with one another. The above-described embodiments are merely examples and do not specifically limit the scope of protection of the embodiments of the present disclosure.

[0473] In an embodiment of the present disclosure, the network side device sends configuration information to the terminal device, and the configuration information includes a trigger condition parameter.

[0474] The setting information includes trigger condition parameters.

[0475] Illustratively, the trigger condition parameter is a first threshold value.

[0476] Illustratively, the trigger condition parameter is a second threshold value.

[0477] Illustratively, the trigger condition parameter is a third threshold value.

[0478] Illustratively, the trigger condition parameter is a fourth threshold value.

[0479] Illustratively, the trigger condition parameter is a first threshold value in the trigger condition.

[0480] Illustratively, the trigger condition parameter is the second threshold value in the trigger condition.

[0481] Illustratively, the trigger condition parameter is the third threshold value in the above-mentioned trigger condition.

[0482] Illustratively, the trigger condition parameter is the fourth threshold value in the above-mentioned trigger condition.

[0483] It should be noted that the above-described embodiments are not particularly limiting but merely serve as examples of some of the embodiments, and the above-described embodiments can be implemented singly or in combination with one another. The above-described embodiments are merely examples and do not specifically limit the scope of protection of the embodiments of the present disclosure.

[0484] For example, the setting information may be display instruction information or implicit instruction information.

[0485] Implicit indication information includes any information or message that can implicitly indicate said meaning.

[0486] It should be noted that in the embodiments of the present disclosure, S161 can be performed alone, or can be combined with any other step in the embodiments of the present disclosure, for example, S151 in the embodiments of the present disclosure, and the embodiments of the present disclosure are not limited thereto.

[0487] In the above-described embodiments of the present disclosure, the methods provided by the embodiments of the present disclosure are described from the perspectives of a terminal device and a network-side device. To realize the functions of the methods provided by the above-described embodiments of the present disclosure, the terminal device and the network-side device may include hardware structures and software modules, and the functions are realized in the form of a hardware structure, a software module, or a hardware structure plus a software module. Some of the functions can be implemented in the form of a hardware structure, a software module, or a hardware structure plus a software module.

[0488] 17 is a schematic configuration diagram of a communication device 1 provided by an embodiment of the present disclosure. The communication device 1 shown in FIG. 17 may include a transceiver module 11 and a processing module 12. The transceiver module may include a transmitting module and / or a receiving module, where the transmitting module is used to realize a transmitting function, the receiving module is used to realize a receiving function, and the transceiver module may realize a transmitting function and / or a receiving function.

[0489] The communication device 1 may be a terminal device, a device in a terminal device, or a device that can be used in conjunction with a terminal device, or the communication device 1 may be a network-side device, a device in a network-side device, or a device that can be used in conjunction with a network-side device.

[0490] The communication device 1 may be a terminal device, which includes a transceiver module 11 .

[0491] The transceiver module 11 is configured to report the flight path information to the network side device in response to satisfying the trigger condition.

[0492] In some embodiments, the flight path information includes at least one of a flight path valid indication, a flight path invalid indication, a flight path, and a flight direction.

[0493] In some embodiments, the trigger condition includes at least one of a flight path invalidation, a flight path update, the terminal device converting from flying according to a planned path to being controlled by an operator, and an offset existing between the current flight path and the reported flight path.

[0494] In some examples, the existence of an offset between the current flight path and the reported flight path includes at least one of: the distance between flight waypoints corresponding to the same time point for the current flight path and the previously reported flight path is greater than a first threshold; the time difference to reach the same flight waypoint for the current flight path and the previously reported flight path is greater than a second threshold; the absolute value of the difference in flight speed for the same time point for the current flight path and the previously reported flight path is greater than a third threshold; and a change in flight direction for the same time point for the current flight path and the previously reported flight path.

[0495] In some embodiments, the transceiver module 11 is further configured to receive configuration information sent by the network-side device, where the configuration information includes at least one of a trigger condition, a report content instruction, and a trigger condition parameter.

[0496] In some examples, the reporting content instructions include at least one of: report a flight path; do not report a flight path; a maximum number of reportable waypoints; a timestamp must be reported; a timestamp does not need to be reported; a flight path validity indication must be reported; and a flight path validity indication does not need to be reported.

[0497] In some embodiments, the processing module 12 is further configured to determine trigger conditions and / or determine that reporting of flight path information is configured to be required based on the configuration information.

[0498] In some embodiments, the transceiver module 11 is further configured to report flight path invalid instruction information to the network side device in response to flight path invalidation, or to report flight path invalid instruction information to the network side device in response to a flight path update, or to report flight path invalid instruction information to the network side device in response to a conversion by the terminal device from flight according to a planned path to operator control.

[0499] In some embodiments, the transceiver module 11 is further configured to report the updated flight path to the network side device in response to updating the flight path, or to report the updated flight path to the network side device in response to an offset between the current flight path and the reported flight path.

[0500] In some embodiments, the transceiver module 11 is further configured to report a flight direction to the network side device in response to a conversion by the terminal device from flight following a planned route to control by an operator.

[0501] In some embodiments, the transceiving module 11 is further configured to report the location information to the network-side device.

[0502] In some embodiments, the flight path includes at least one of a flight waypoint, a plurality of flight waypoints, a timestamp, and a plurality of timestamps.

[0503] In some embodiments, the timestamp is the difference between the time when the terminal device arrives at the corresponding flight waypoint and the current time, or the time when the terminal device arrives at the corresponding flight waypoint, or the difference between the time when the terminal device arrives at the corresponding flight waypoint and the time when the terminal device arrives at the previous flight waypoint.

[0504] In some embodiments, the trigger condition is a measurement reporting event.

[0505] In some embodiments, the transceiver module 11 is further configured to report a measurement report to the network side device in response to meeting the measurement reporting event, the measurement report including flight path information.

[0506] In some embodiments, the trigger condition is a condition that triggers reporting of the auxiliary information.

[0507] In some embodiments, the transceiver module 11 is further configured to report the aiding information to the network side device in response to satisfying a condition that triggers reporting the aiding information, where the aiding information includes flight path information.

[0508] In some embodiments, the transceiver module 11 is further configured to require reporting of flight path information by the terminal device, and to start reporting the auxiliary information to the network side device in response to not reporting auxiliary information including the flight path information to the network side device and satisfying a trigger condition, where the auxiliary information includes the flight path information.

[0509] In some embodiments, the transceiver module 11 is further configured to require reporting of flight path information by the terminal device, and to initiate reporting of auxiliary information to the network side device in response to satisfying a trigger condition, where the auxiliary information includes the flight path information.

[0510] The communication device 1 is a network-side device, and includes a transceiver module 11 .

[0511] The transceiver module 11 is configured to receive flight path information reported by the terminal device when a trigger condition is met.

[0512] In some embodiments, the flight path information includes at least one of a flight path valid indication, a flight path invalid indication, a flight path, and a flight direction.

[0513] In some embodiments, the trigger condition includes at least one of a flight path invalidation, a flight path update, the terminal device converting from flying according to a planned path to being controlled by an operator, and an offset existing between the current flight path and the reported flight path.

[0514] In some examples, the existence of an offset between the current flight path and the reported flight path includes at least one of: the distance between flight waypoints corresponding to the same time point for the current flight path and the previously reported flight path is greater than a first threshold; the time difference to reach the same flight waypoint for the current flight path and the previously reported flight path is greater than a second threshold; the absolute value of the difference in flight speed for the same time point for the current flight path and the previously reported flight path is greater than a third threshold; and a change in flight direction for the same time point for the current flight path and the previously reported flight path.

[0515] In some embodiments, the transceiver module 11 further transmits configuration information to the terminal device configured to, the configuration information including at least one of a trigger condition, a report content instruction, and a trigger condition parameter.

[0516] In some examples, the reporting content instructions include at least one of: report a flight path; do not report a flight path; a maximum number of reportable waypoints; a timestamp must be reported; a timestamp does not need to be reported; a flight path validity indication must be reported; and a flight path validity indication does not need to be reported.

[0517] In some embodiments, the transceiver module 11 is further configured to receive flight path invalidation indication information reported when the flight path is invalidated by the terminal device, or when the flight path is updated by the terminal device, or when the terminal device converts from flying according to a planned path to being controlled by an operator.

[0518] In some embodiments, the transceiver module 11 is further configured to receive an updated flight path reported when the flight path is updated by the terminal device, or to receive an updated flight path reported by the terminal device when there is an offset between the current flight path and the reported flight path.

[0519] In some embodiments, the transceiver module 11 is further configured to receive a reported flight direction when converted by the terminal device from flight according to a planned path to control by an operator.

[0520] In some embodiments, the transceiver module 11 is further configured to receive location information reported by the terminal device.

[0521] In some embodiments, the flight path includes at least one of a flight waypoint, a plurality of flight waypoints, a timestamp, and a plurality of timestamps.

[0522] In some embodiments, the timestamp is the difference between the time when the terminal device arrives at the corresponding flight waypoint and the current time, or the time when the terminal device arrives at the corresponding flight waypoint, or the difference between the time when the terminal device arrives at the corresponding flight waypoint and the time when the terminal device arrives at the previous flight waypoint.

[0523] In some embodiments, the trigger condition is a measurement reporting event.

[0524] In some embodiments, the transceiver module 11 is further configured to receive a measurement report reported by the terminal device when a measurement reporting event is met, where the measurement report includes flight path information.

[0525] In some embodiments, the trigger condition is a condition that triggers reporting of the auxiliary information.

[0526] In some embodiments, the transceiver module 11 is further configured to receive reported auxiliary information when the terminal device meets a condition that triggers reporting the auxiliary information, where the auxiliary information includes flight path information.

[0527] In some embodiments, the transceiver module 11 is further configured to require reporting of flight path information by the terminal device, and to receive the reported auxiliary information when the terminal device does not report auxiliary information including the flight path information to the network side device and meets a trigger condition, where the auxiliary information includes the flight path information.

[0528] In some embodiments, the transceiver module 11 is further configured to require reporting of flight path information by the terminal device and to receive reported auxiliary information when a trigger condition is met, where the auxiliary information includes the flight path information.

[0529] Regarding the communication device 1 of the above embodiment, the specific manner in which each module therein performs its operation has already been described in detail in the embodiment relating to the method, and will not be described in detail here.

[0530] The communication device 1 provided by the above-mentioned embodiments of the present disclosure has the same or similar beneficial effects as the route reporting method obtained by some of the above-mentioned embodiments, which will not be further described here.

[0531] 18, which is a schematic diagram of the configuration of another communication device 1000 provided by an embodiment of the present disclosure. The communication device 1000 may be a network-side device or a terminal device, and the network-side device may be a chip, chip system, processor, etc. that supports the implementation of the above-mentioned method, and the terminal device may be a chip, chip system, processor, etc. that supports the implementation of the above-mentioned method. The device can be used to implement the methods described in the above-mentioned method embodiments, and for details, please refer to the description of the above-mentioned method embodiments.

[0532] The communication device 1000 may include one or more processors 1001. The processor 1001 may be a general-purpose processor or a special-purpose processor. For example, the processor 1001 may be a baseband processor or a central processor. The baseband processor may be used to process communication protocols and communication data, and the central processor may be used to control the communication device (e.g., a network side device, a baseband chip, a terminal device, a terminal device chip, a DU or CU, etc.), execute computer programs, and process data of the computer programs.

[0533] Optionally, the communication device 1000 may include one or more memories 1002 having stored therein a computer program 1004 that executes the computer program 1004 to cause the communication device 1000 to perform the method described in the method embodiments above. Optionally, the memory 1002 may store data. The communication device 1000 and the memory 1002 may be provided separately or integrated together.

[0534] Optionally, the communication device 1000 may further include a transceiver 1005 and an antenna 1006. The transceiver 1005 may also be referred to as a transceiver unit, transceiver, or transceiver circuit, and is used to realize a transmission and reception function. The transceiver may include a receiver and a transmitter, and the transceiver 1005 may also be referred to as a receiving device or receiving circuit, and is used to realize a reception function, and the transmitter may also be referred to as a transmitting device or transmitting circuit, and is used to realize a transmission function.

[0535] Optionally, the communication device 1000 may further include one or more interface circuits 1007. The interface circuits 1007 are used to receive and transmit code instructions to the processor 1001. The processor 1001 executes the code instructions, thereby causing the communication device 1000 to perform the methods described in the above method embodiments.

[0536] The communication device 1000 is a first terminal device, and the transceiver 1005 is used to execute S21 of Figure 2; S31 and S33 of Figure 3; S41 and S43 of Figure 4; S51 of Figure 5; S61 of Figure 6; S71 of Figure 7; S81 of Figure 8; S91 of Figure 9; S101 of Figure 10; S111 of Figure 11; S121 of Figure 12; S131 of Figure 13; and S141 of Figure 14, and the processor 1001 is used to execute S32 of Figure 3; and S42 of Figure 4.

[0537] The communication device 1000 is a network-side device, and the transceiver 1005 is used to execute S151 in FIG. 15 and S161 in FIG.

[0538] In one implementation, the processor 1001 may include a transceiver for implementing receiving and transmitting functions. For example, the transceiver may be a transceiver circuit, an interface, or an interface circuit. The transceiver circuit, interface, or interface circuit for implementing receiving and transmitting functions may be separate or integrated. The transceiver circuit, interface, or interface circuit may be used to read and write code / data, or the transceiver circuit, interface, or interface circuit may be used to transmit or convey signals.

[0539] In one implementation, the processor 1001 may store a computer program 113, which, when executed by the processor 1001, enables the communication device 1000 to perform the methods described in the above method embodiments. The computer program 113 may be embedded in the processor 1001, in which case the processor 1001 may be implemented in hardware.

[0540] In one implementation, the communications device 1000 may include circuitry capable of implementing the transmit, receive, or communication functions of the method embodiments described above. The processors and transceivers described in this disclosure may be integrated into an integrated circuit (IC), an analog IC, a radio frequency integrated circuit (RFIC), a mixed-signal IC, an application specific integrated circuit (ASIC), a printed circuit board (PCB), an electronic device, or the like. The processors and transceivers may be fabricated using a variety of IC process technologies, such as complementary metal oxide semiconductor (CMOS), n-type metal oxide semiconductor (nMOS), p-type metal oxide semiconductor (PMOS), bipolar junction transistor (BJT), bipolar CMOS (BiCMOS), silicon germanium (SiGe), gallium arsenide (GaAs), and the like.

[0541] The communication device in the above embodiment description may be a terminal device, but the scope of the communication device described in this disclosure is not limited thereto, and the structure of the communication device may not be limited by Figure 18. The communication device may be an independent device or part of a larger device. For example, the communication device may be as follows: (1) An independent integrated circuit IC or chip, or a chip system or subsystem; (2) a set having one or more integrated circuits, optionally including a memory component for storing data, computer programs; (3) ASIC, e.g., modem, (4) Modules that can be embedded into other devices; (5) Receivers, terminal devices, intelligent terminal devices, cellular phones, wireless devices, handhelds, mobile units, vehicle-mounted devices, base stations, cloud devices, artificial intelligence devices, etc. (6)Others.

[0542] For the case where the communication device is a chip or chip system, refer to FIG. 19, which is a block diagram of a chip provided according to an embodiment of the present disclosure.

[0543] The chip 1100 includes a processor 1101 and an interface 1103. The number of processors 1101 may be one or more, and the number of interfaces 1103 may be more than one.

[0544] When the chip is used to realize the functions of the network side device of the embodiment of the present disclosure: The interface 1103 is used to receive and transmit code instructions to the processor.

[0545] The processor 1101 is used to execute code instructions to perform the path reporting method described in the above several embodiments.

[0546] When the chip is used to realize the functions of the terminal device of the embodiment of the present disclosure: The interface 1103 is used to receive and transmit code instructions to the processor.

[0547] The processor 1101 is used to execute code instructions to perform the path reporting method described in the above several embodiments.

[0548] Optionally, the chip 1100 further includes a memory 1102, which is used to store necessary computer programs and data.

[0549] As will be appreciated by those skilled in the art, the various illustrative logical blocks and steps enumerated in the embodiments of the present disclosure can be realized by electronic hardware, computer software, or a combination of both. Whether such functions are realized by hardware or software depends on the specific application and the overall system design requirements. Those skilled in the art can realize the functions using various methods for each specific application, but such realization should not be understood as exceeding the scope of protection of the embodiments of the present disclosure.

[0550] An embodiment of the present disclosure further provides a route reporting system, the system including a communication device serving as a terminal device in the embodiment of Figure 17 and a communication device serving as a network side device, or the system including a communication device serving as a terminal device in the embodiment of Figure 18 and a communication device serving as a network side device.

[0551] The present disclosure further provides a readable storage medium having instructions stored thereon, which when executed by a computer implement the functions of any one of the above method embodiments.

[0552] The present disclosure further provides a computer program product, which, when executed by a computer, implements the functions of any one of the above method embodiments.

[0553] In the above embodiments, all or a portion thereof can be implemented in software, hardware, firmware, or any combination thereof. When implemented using software, all or a portion thereof can be implemented in the form of a computer program product. The computer program product includes one or more computer programs. When the computer programs are loaded and executed on a computer, the computer programs generate, in whole or in part, the flow or functions described in the embodiments of the present disclosure. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer programs may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer program may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, radio, microwave, etc.) methods. The computer-readable storage medium may be any available medium accessible to a computer, or a data storage device such as a server, data center, or the like, integrating one or more available media. The usable medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a high-density digital video disc (DVD)), or a semiconductor medium (e.g., a solid state disk (SSD)).

[0554] As will be appreciated by those skilled in the art, the various numerals, such as first, second, etc., used in the present disclosure are used for ease of explanation and do not limit the scope of the embodiments of the present disclosure, but also represent a priority order.

[0555] "At least one" in the present disclosure may be explained as "one or more," and "more" may be two, three, four or more, and is not limited by the present disclosure. In the embodiments of the present disclosure, for one technical feature, "first," "second," "third," "A," "B," "C," and "D" are used to distinguish technical features in the same category, and there is no priority or size order between the technical features explained by "first," "second," "third," "A," "B," "C," and "D."

[0556] The correspondences shown in each table in the present disclosure may be set or defined in advance. The possible values ​​of information in each table are merely examples and may be set to other values ​​and are not limited by the present disclosure. When setting the correspondences between information and each parameter, it is not necessary to set all of the correspondences shown in each table. For example, in the tables of the present disclosure, the correspondences shown in some rows may not be set. Furthermore, the tables may be appropriately modified or adjusted, such as by splitting or merging. The names of the parameters shown in the themes of each table may also be called other names understandable to the communication device, and the possible values ​​or display methods of the parameters may also be other possible values ​​or display methods understandable to the communication device. When implementing each of the tables, other data structures, such as arrays, queues, containers, stacks, linear lists, pointers, linked lists, trees, graphs, structures, classes, heaps, and hash tables, may be used.

[0557] Predefined in this disclosure may be understood as defined, predefined, stored, pre-stored, predefined, pre-set, hardened, or pre-baked.

[0558] As can be understood by those skilled in the art, the units and algorithm steps of each example described in the embodiments disclosed herein can be implemented in electronic hardware or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can implement the described functions using different methods for each specific application, and such implementation should not be considered as going beyond the scope of the present disclosure.

[0559] As can be clearly understood by those skilled in the art, for convenience and simplification of explanation, the specific working processes of the systems, devices and units described above are to be referred to the corresponding processes in the aforementioned method embodiments, and detailed descriptions thereof will be omitted here.

[0560] The above description is merely a specific embodiment of the present disclosure, and the scope of protection of the present disclosure is not limited thereto. Any changes or substitutions that can be easily thought of by a person skilled in the art without departing from the technical scope disclosed in the present disclosure should be included in the scope of protection of the present disclosure. Therefore, the scope of protection of the present disclosure should be pursuant to the claims.

Claims

1. 1. A route reporting method performed by a terminal device, comprising: reporting flight path information to a network side device in response to satisfying a trigger condition; the flight path information includes at least one of flight path valid indication information and flight path invalid indication information; The trigger condition includes at least one of: a distance between flight waypoints for the current flight path and the previously reported flight path is greater than a first threshold; a time difference between flight waypoints for the current flight path and the previously reported flight path is greater than a second threshold; an absolute value of a difference in flight speed at the same time point for the current flight path and the previously reported flight path is greater than a third threshold; and a change in flight direction at the same time point for the current flight path and the previously reported flight path. A route reporting method comprising:

2. The flight path information is Flight path, and [0023] Further comprising at least one of: a flight direction; 2. The method of claim 1, wherein the route reporting is performed by the first route reporting unit.

3. The trigger condition is: invalid flight path, Flight path updates, and the terminal device has been converted from flying according to a planned route to being controlled by an operator; 2. The method of claim 1, wherein the route reporting is performed by the first route reporting unit.

4. The method comprises: The method further includes receiving configuration information sent by the network-side device, wherein the configuration information includes: the trigger condition, Instructions on report content, and trigger condition parameters, The report content instructions are: reporting flight paths; Failure to report flight paths; Maximum number of reportable waypoints, that the timestamp must be reported, that timestamps do not need to be reported, The need to report flight path validity indication information; and [0033] not being required to report flight path validity indication information; 2. The method of claim 1, wherein the route reporting is performed by the first route reporting unit.

5. The method comprises: determining the trigger condition and / or determining that the flight path information is configured to require reporting based on the setting information; 5. The method of claim 4, wherein the route reporting is performed by the first route reporting unit.

6. In response to satisfying the trigger condition, reporting flight path information to a network side device includes: In response to the flight path being invalid, reporting flight path invalid indication information to the network side device; or In response to updating the flight path, reporting flight path invalid indication information to the network side device; or reporting flight path invalid instruction information to the network side device in response to the terminal device converting flight according to a planned route to control by an operator; In response to satisfying the trigger condition, reporting flight path information to a network side device includes: In response to updating the flight path, reporting the updated flight path to the network side device; or reporting an updated flight path to the network side device in response to an offset between the current flight path and the reported flight path; In response to satisfying the trigger condition, reporting flight path information to a network side device includes: reporting a flight direction to the network side device in response to the terminal device converting the flight from following a planned route to control by an operator; 4. The method of claim 3, wherein the route reporting is performed by the first route reporting unit.

7. The method comprises: further comprising reporting location information to the network side device; 2. The method of claim 1, wherein the route reporting is performed by the first route reporting unit.

8. The flight path is: One flight waypoint, Multiple flight waypoints, one timestamp, and a plurality of timestamps, The timestamp is a difference between the time when the terminal device arrives at the corresponding flight waypoint and the current time, or a time when the terminal device arrives at the corresponding flight waypoint, or a difference between the time when the terminal device arrives at the corresponding flight waypoint and the time when the terminal device arrives at the previous flight waypoint; 3. The method of claim 2, wherein the route reporting is performed by the first route reporting unit.

9. The trigger condition is a condition that triggers a measurement reporting event or reporting of auxiliary information.

2. The method of claim 1, wherein the route reporting is performed by the first route reporting unit.

10. In response to satisfying the trigger condition, reporting flight path information to a network side device includes: In response to satisfying a measurement reporting event, reporting a measurement report to the network side device, wherein the measurement report includes the flight path information; or In response to satisfying a condition that triggers reporting of auxiliary information, reporting auxiliary information to the network side device, wherein the auxiliary information includes the flight path information; or a step of requiring the terminal device to report the flight path information, and starting to report the auxiliary information to the network side device in response to not reporting auxiliary information including the flight path information to the network side device and satisfying a condition for triggering reporting of the auxiliary information, wherein the auxiliary information includes the flight path information; or configured to require reporting of the flight path information by the terminal device, and in response to satisfying the trigger condition, starting reporting auxiliary information to the network side device, wherein the auxiliary information includes the flight path information.

2. The method of claim 1, wherein the route reporting is performed by the first route reporting unit.

11. A route reporting method executed by a network-side device, comprising: receiving flight path information reported by a terminal device when a trigger condition is met; the flight path information includes at least one of flight path valid indication information and flight path invalid indication information; The trigger condition includes at least one of: a distance between flight waypoints for the current flight path and the previously reported flight path is greater than a first threshold; a time difference between flight waypoints for the current flight path and the previously reported flight path is greater than a second threshold; an absolute value of a difference in flight speed at the same time point for the current flight path and the previously reported flight path is greater than a third threshold; and a change in flight direction at the same time point for the current flight path and the previously reported flight path. A route reporting method comprising:

12. The flight path information is Flight path, and a flight direction; The flight path is: One flight waypoint, Multiple flight waypoints, one timestamp, and at least one of a plurality of timestamps; The timestamp is a difference between the time when the terminal device arrives at the corresponding flight waypoint and the current time, or a time when the terminal device arrives at the corresponding flight waypoint, or a difference between the time when the terminal device arrives at the corresponding flight waypoint and the time when the terminal device arrives at the previous flight waypoint; 12. The method of claim 11, wherein the route reporting is performed by the first route reporting method.

13. The trigger condition is: invalid flight path, Flight path updates, and the terminal device has been converted from flying according to a planned route to being controlled by an operator; 12. The method of claim 11, wherein the route reporting is performed by the first route reporting method.

14. The method comprises: further comprising the step of transmitting configuration information to the terminal device; The setting information is the trigger condition, Instructions on report content, and at least one of the trigger condition parameters; The report content instructions are: reporting flight paths; Failure to report flight paths; Maximum number of reportable waypoints, that the timestamp must be reported, that timestamps do not need to be reported, The need to report flight path validity indication information; and [0033] not being required to report flight path validity indication information; 12. The method of claim 11, wherein the route reporting is performed by the first route reporting method.

15. receiving flight path information reported by the terminal device when a trigger condition is met, receiving flight path invalidation indication information reported by the terminal device when the flight path is invalidated; or receiving invalid indication information of the reported flight path when the flight path is updated by the terminal device; or receiving flight path invalidation indication information reported when the terminal device is converted from flying according to a planned path to being controlled by an operator; or receiving an updated flight path reported by the terminal device if the flight path is updated; or receiving an updated flight path reported by the terminal device if there is an offset between the current flight path and the reported flight path; or receiving a reported flight direction when the terminal device converts from flight according to a planned route to control by an operator; 14. The method of claim 13, wherein:

16. The method comprises: receiving location information reported by the terminal device; 12. The method of claim 11, wherein the route reporting is performed by the first route reporting method.

17. The trigger condition is a condition that triggers a measurement reporting event or reporting of auxiliary information.

12. The method of claim 11, wherein the route reporting is performed by the first route reporting method.

18. receiving flight path information reported by the terminal device when a trigger condition is met, receiving a measurement report reported by the terminal device when a measurement reporting event is satisfied, the measurement report including the flight path information; or receiving reported auxiliary information when the terminal device satisfies a condition that triggers reporting of the auxiliary information, the auxiliary information including the flight path information; or a step of requiring the terminal device to report the flight path information, not reporting auxiliary information including the flight path information to the network side device, and receiving reported auxiliary information when the trigger condition is satisfied, the auxiliary information including the flight path information; or receiving auxiliary information configured to require reporting of the flight path information by a terminal device and reported when the trigger condition is satisfied, the auxiliary information including the flight path information; 12. The method of claim 11, wherein the route reporting is performed by the first route reporting method.

19. A communication device, a transceiver module configured to report flight path information to a network-side device in response to satisfying a trigger condition; the flight path information includes at least one of flight path valid indication information and flight path invalid indication information; The trigger condition includes at least one of: a distance between flight waypoints for the current flight path and the previously reported flight path is greater than a first threshold; a time difference between flight waypoints for the current flight path and the previously reported flight path is greater than a second threshold; an absolute value of a difference in flight speed at the same time point for the current flight path and the previously reported flight path is greater than a third threshold; and a change in flight direction at the same time point for the current flight path and the previously reported flight path. A communication device comprising:

20. A communication device, a transceiver module configured to receive flight path information reported by a terminal device when a trigger condition is met; the flight path information includes at least one of flight path valid indication information and flight path invalid indication information; The trigger condition includes at least one of: a distance between flight waypoints for the current flight path and the previously reported flight path is greater than a first threshold; a time difference between flight waypoints for the current flight path and the previously reported flight path is greater than a second threshold; an absolute value of a difference in flight speed at the same time point for the current flight path and the previously reported flight path is greater than a third threshold; and a change in flight direction at the same time point for the current flight path and the previously reported flight path. A communication device comprising:

21. A communication device, a processor and a memory, wherein a computer program is stored in the memory, and the processor executes the computer program stored in the memory to cause the communication device to perform the method according to any one of claims 1 to 10, or the processor executes the computer program stored in the memory to cause the communication device to perform the method according to any one of claims 11 to 18; A communication device comprising:

22. A communication device, a processor and an interface circuit; the interface circuit receives and transmits code instructions to the processor; The processor executes the code instructions to perform the method according to any one of claims 1 to 10, or executes the code instructions to perform the method according to any one of claims 11 to 18. A communication device comprising:

23. A computer-readable storage medium having instructions stored thereon, When said instructions are executed, the method according to any one of claims 1 to 10 is realized, or when said instructions are executed, the method according to any one of claims 11 to 18 is realized. A computer-readable storage medium comprising:

Images