Communication method and device

Abstract

The present application provides a communication method and apparatus. In the method, a first device determines that a first condition is met and restricts a non-unmanned aircraft service of a terminal device and / or restricts a first control plane procedure of the terminal device. The first condition includes one or more of the following conditions: the terminal device is authorized for the unmanned aircraft service, the terminal device initiates establishment of a first session corresponding to the unmanned aircraft service, or the terminal device is in an airborne state. The first control plane procedure is not a procedure specific to the unmanned aircraft service. According to the present application, the first device conditionally restricts the non-unmanned aircraft service of the terminal device, thereby reducing attacks that an attacker may launch against the terminal device by using the non-unmanned aircraft service and improving the security of the terminal device. The first device conditionally restricts the first control plane procedure of the terminal device, freeing resources required to execute the first control plane procedure, thereby providing more available resources for the unmanned aircraft service.

Description

[Technical Field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims priority to Chinese Patent Application No. 202210752034.0, filed with the State Intellectual Property Office of China on June 28, 2022, entitled "Communication Method and Apparatus," which is incorporated herein by reference in its entirety.

[0002] TECHNICAL FIELD This application relates to the field of communications technology, and more particularly to communications methods and devices. [Background technology]

[0003] An unmanned aerial system (UAS) includes an unmanned aerial vehicle (UAV) and an unmanned aerial vehicle remote control (UAVC). The unmanned aerial vehicle remote control may be simply referred to as a remote control, a remote control device, or the like. The unmanned aerial vehicle may fly autonomously or may fly according to control commands from the remote control. Specifically, the unmanned aerial vehicle and the remote control may communicate with each other. For example, the remote control may send control commands to the unmanned aerial vehicle, which may then transmit captured photos or videos to the remote control after aerial photography.

[0004] By combining with a mobile communication network, an unmanned aerial system can fully utilize the advantages of the mobile communication network, such as wide area coverage, high reliability, and support for high-speed mobile services, and can extend the unmanned aerial system to implement highly reliable flight beyond the line of sight (remote), resulting in more widespread use and sales of the unmanned aerial system. In other words, an unmanned aerial system simultaneously plays two roles: a terminal in a mobile communication network and an unmanned aerial system that can fly in an unmanned aerial system. With regard to the mobile communication network, the mobile communication network not only provides the unmanned aerial system with services enjoyed by common terminals (e.g., multimedia communication or data services), but also provides the unmanned aerial system with services specific to the unmanned aerial system (e.g., remote positioning or no-fly zones).

[0005] Due to the two roles of unmanned aerial vehicles, they face the following problem: During the flight of an unmanned aerial vehicle, an attacker may use a mobile communication network to launch a denial of service (DoS) attack against the unmanned aerial vehicle. For example, an attacker may transmit a large amount of data from a non-unmanned aerial vehicle service to the unmanned aerial vehicle, intentionally occupying the unmanned aerial vehicle's resources (such as network resources, computing resources, and battery resources), thereby affecting the normal operation of the unmanned aerial vehicle. As a result, the unmanned aerial vehicle may deviate from its route and fail to reach its expected destination address, or the unmanned aerial vehicle may even malfunction. Therefore, how to mitigate attacks that attackers launch against unmanned aerial vehicles by using non-unmanned aerial vehicle services is an urgent problem to be solved. Summary of the Invention

[0006] SUMMARY OF THE INVENTION Embodiments of the present application provide communication methods and apparatus for mitigating attacks that attackers may perform against unmanned aerial vehicles by using non-unmanned aerial vehicle services, improving the safety of unmanned aerial vehicles.

[0007] According to a first aspect, the present application provides a communication method. The method may be performed by a first device or a component (e.g., a chip) of the first device. In the method, the first device determines that a first condition is met, where the first condition includes one or more of the following conditions: the terminal device is authorized for unmanned aerial vehicle service, the terminal device initiates establishment of a first session corresponding to the unmanned aerial vehicle service, or the terminal device is in an airborne state; and the first device restricts non-unmanned aerial vehicle services of the terminal device and / or restricts a first control plane procedure of the terminal device, where the first control plane procedure is not a procedure specific to the unmanned aerial vehicle service.

[0008] In this embodiment of the present application, the first device conditionally restricts the non-unmanned aerial vehicle services of the terminal device, so that attacks that an attacker can launch against the terminal device by using the non-unmanned aerial vehicle services can be reduced and the security of the terminal device can be improved. The first device conditionally restricts the first control plane procedure of the terminal device, so that resources required to execute the first control plane procedure can be released and more available resources can be provided for the unmanned aerial vehicle services.

[0009] For example, if a terminal device is authorized for unmanned aircraft services, it means that the terminal device supports simultaneous execution of unmanned aircraft services and non-unmanned aircraft services. In this case, the first device restricts the non-unmanned aircraft services of the terminal device to reduce attacks that an attacker can launch against the terminal device by using the non-unmanned aircraft services and to prevent the non-unmanned aircraft services from occupying resources of the unmanned aircraft services. Alternatively, if the terminal device is authorized for unmanned aircraft services, the first device may restrict the first control plane procedure to release resources required to perform the first control plane procedure, so that more resources available for the authorized unmanned aircraft services may be reserved for the terminal device.

[0010] In another example, when a terminal device initiates establishment of a first session corresponding to an unmanned aircraft service, it means that the terminal device executes the unmanned aircraft service. In this case, the first device restricts the non-unmanned aircraft service of the terminal device to reduce attacks that an attacker may launch against the terminal device by using the non-unmanned aircraft service in the process of executing the unmanned aircraft service by the terminal device, and to prevent the non-unmanned aircraft service from occupying resources of the unmanned aircraft service in the process of executing the unmanned aircraft service by the terminal device. Alternatively, when the terminal device initiates establishment of a first session corresponding to the unmanned aircraft service, the first device restricts the first control plane procedure, so that resources required to execute the first control plane procedure can be released, thereby increasing resources available for the unmanned aircraft service.

[0011] In another example, the terminal device is in a flight state, and the first device restricts the non-unmanned aerial vehicle services of the terminal device to reduce attacks that an attacker can launch against the flight terminal services by using the non-unmanned aerial vehicle services. This can avoid a problem in which the non-unmanned aerial vehicle services occupy a large amount of resources on the terminal device, or the like, causing the terminal device to deviate from its route and be unable to reach its expected destination address, thereby improving the safety of the terminal device. Alternatively, the terminal device is in a flight state, and the first device restricts the first control plane procedures, so that more resources available to the unmanned aerial vehicle services can be reserved for the flight terminal services, thereby avoiding a problem in which the flight terminal services cannot function properly or even crash due to insufficient resources or the like.

[0012] In a possible implementation, the first device restricting the non-unmanned aircraft service of the terminal device may specifically be any one of the following: the first device is a first session management function device, and the first device releases all or part of a session corresponding to the non-unmanned aircraft service managed by the first device, and / or prohibits the establishment or modification of a session corresponding to the non-unmanned aircraft service; or the first device is a short message service service center, and the first device does not send or suspends transmission of a first message to the terminal device, where the first message is used to request the establishment or modification of a session corresponding to the non-unmanned aircraft service; or the first device is a terminal device, and the first device does not send or suspends transmission of a first message to the first session management function device, where the first message is used to request the establishment or modification of a session corresponding to the non-unmanned aircraft service.

[0013] In the above implementation, the first device may restrict the non-unmanned aerial vehicle services of the terminal device in multiple manners, such as releasing a session corresponding to the non-unmanned aerial vehicle service, prohibiting the establishment or modification of a session corresponding to the non-unmanned aerial vehicle service, or skipping sending to the terminal device or session management function device a message used to request the establishment or modification of a session corresponding to the non-unmanned aerial vehicle service.

[0014] In a possible implementation, if the first device determines that the terminal device is approved for unmanned aircraft services and / or that the terminal device is in an airborne state, before the first device restricts the non-unmanned aircraft services of the terminal device and / or restricts the first control plane procedure, the method may further include: the first device receiving a second message from the terminal device, wherein the second message is used to request establishing a first session; and the first device determining, based on the second message, that the first session belongs to a session corresponding to the unmanned aircraft service.

[0015] In the above implementation, if the terminal device is authorized for the unmanned aircraft service and / or is in a flight state, the first device may determine whether the received session establishment request message is used to establish a session corresponding to the unmanned aircraft service. For example, if the first session belongs to a session corresponding to the unmanned aircraft service, the first device may restrict the unmanned aircraft service and / or restrict the first control plane procedure. In another example, if the first session belongs to a session corresponding to a non-unmanned aircraft service, it means that the first device has released the session corresponding to the non-unmanned aircraft service and / or the terminal device has not established the first session corresponding to the unmanned aircraft service and that resources are sufficient. In this case, the first device may not restrict the non-unmanned aircraft service and / or the first control plane procedure, which may result in improved resource utilization while reducing the impact on the unmanned aircraft service.

[0016] In a possible implementation, the method may further include: the first device sending a third message to the second device, wherein the third message is used to request restricting non-unmanned aerial vehicle services of the terminal device.

[0017] In the above implementation, after determining to restrict the non-unmanned aerial vehicle service of the terminal device, the first device may send a third message to the second device, so that the second device restricts the non-unmanned aerial vehicle service of the terminal device.

[0018] In a possible implementation, the method may further include: the first device receiving first instruction information from the second device, where the first instruction information instructs the first device to release one or more sessions corresponding to the non-unmanned aerial vehicle service. Correspondingly, the first device restricting the non-unmanned aerial vehicle service of the terminal device may be: the first device releasing one or more sessions corresponding to the non-unmanned aerial vehicle service based on the first instruction information.

[0019] In another possible implementation, the first device restricting the non-unmanned aircraft services of the terminal device includes the first device releasing all or a portion of the sessions corresponding to the non-unmanned aircraft services managed by the first device, and the method may further include: the first device determining that N is greater than M, where N is the number of sessions corresponding to the non-unmanned aircraft services managed by the first device, and M is the number of sessions corresponding to the non-unmanned aircraft services that are allowed to be established on the first device when the terminal device executes the unmanned aircraft service; and the first device determining to release H sessions corresponding to the non-unmanned aircraft services, where H is a positive integer greater than or equal to (NM).

[0020] In the above implementation, the first device may release one or more sessions corresponding to the non-unmanned aerial vehicle services based on the instruction information of the second device, or may release one or more sessions corresponding to the non-unmanned aerial vehicle services based on N and M. The implementation is flexible.

[0021] In a possible implementation, the first device restricting the non-unmanned aerial vehicle service of the terminal device may be: the first device sending second instruction information to the terminal device, where the second instruction information indicates that establishment of a session corresponding to the non-unmanned aerial vehicle service is prohibited.

[0022] In the above implementation, the first device indicates to the terminal device that establishment of a session corresponding to a non-unmanned aerial vehicle service is prohibited. In this manner, the terminal device may not initiate a session corresponding to the non-unmanned aerial vehicle service, thereby restricting the non-unmanned aerial vehicle service of the terminal device.

[0023] In a possible implementation, the first control plane procedure includes one or more of a primary authentication procedure, a deregistration procedure, a slice authentication procedure, or a secondary authentication procedure.

[0024] In a possible implementation, the first device restricting the first control plane procedure of the terminal device may be: the first device suspending or terminating the first control plane procedure.

[0025] In the above implementation, the first device may suspend or terminate the first control plane procedure, where the first control plane procedure is not specific to the unmanned aircraft service. In this manner, the suspension or termination of the first control plane procedure is not related to the performance of the unmanned aircraft service, and resources required to perform the first control plane procedure may be freed up, thereby providing more available resources to the unmanned aircraft service, thereby facilitating the performance of the unmanned aircraft service.

[0026] In a possible implementation, after the first device suspends the first control plane procedure, the method further includes: the first device starting a first timer; the first device determining that the terminal device satisfies a first condition while the first timer is running; and the first device terminating the first control plane procedure when the execution of the first timer ends.

[0027] In the above implementation, the first device may first suspend the first control plane procedure. If the terminal device satisfies the first condition while the timer is running, the first device may terminate the first control plane procedure. If the terminal device does not satisfy the first condition while the timer is running, the first device may perform the first control plane procedure.

[0028] In a possible implementation, the method may further include: the first device receiving a fourth message from the third device, where the fourth message is used to request that the first control plane procedure be performed; and the first device sending a fifth message to the third device, where the fifth message includes a reason for not performing the first control plane procedure.

[0029] In the above implementation, when the first device suspends or terminates the first control plane procedure, the first device may feed back to the third device the reason for not performing the first control plane procedure. For example, the reason for not performing the first control plane procedure may be that the terminal device satisfies a first condition.

[0030] In a possible implementation, the first device determining that the terminal device is in a flight state may be: the first device receives third indication information from the access and mobility management function device, where the third indication information indicates that the terminal device is in a flight state. Optionally, the first device sends a sixth message to the access and mobility management function network element, where the sixth message is used to obtain a status of the terminal device, and the status of the terminal device includes a flight state and / or a non-flight state.

[0031] In the above implementation, the first device can obtain the status of the terminal device from the access and mobility management function device. The status of the terminal device can be actively pushed by the access and mobility management function device, or can be obtained by the first device by subscribing to the status of the terminal device from the access and mobility management function device. The implementation is flexible.

[0032] In a possible implementation, the first device is an access and mobility management function device; the first device determining that the terminal device is in a flight state may specifically mean: the first device receiving fourth instruction information from the fourth device, where the fourth instruction information indicates that the terminal device is in a flight state; or the first device determining that the terminal device is in a flight state based on the mobility information of the terminal device and / or the flight information of the terminal device.

[0033] In the above implementation, the access and mobility management function device may recognize that the terminal device is in a flight state from the fourth device, or may determine that the terminal device is in a flight state based on the mobility information and / or flight information of the terminal device.

[0034] In a possible implementation, the first device is a terminal device; the first device determining that the terminal device is in a flight state may be: the first device determining that the terminal device is in a flight state based on mobility information and / or fifth instruction information from the application layer, where the fifth instruction information instructs the terminal device to enter flight mode.

[0035] In the above implementation, the terminal device may determine whether the terminal device is in a flight state.

[0036] In a possible implementation, the method may further include: the first device determining that a second condition is met, wherein the second condition includes one or more of the following conditions: authorization for the unmanned aircraft service is revoked from the terminal device, the terminal device is not authorized for the unmanned aircraft service, the unmanned aircraft service of the terminal device is deregistered, or the terminal device releases the last session corresponding to the unmanned aircraft service.

[0037] The first device is a first session management function device, and the first device receives a seventh message from the terminal device and establishes or modifies a session corresponding to the non-unmanned aerial vehicle service based on the seventh message, where the seventh message is used to request establishing or modifying a session corresponding to the non-unmanned aerial vehicle service.

[0038] Alternatively, the first device is a short message service service center, and the first device sends an eighth message to the terminal device, where the eighth message is used to request establishing or modifying a session corresponding to a non-unmanned aerial vehicle service.

[0039] Alternatively, the first device is a terminal device, and the first device sends an eighth message to the first session management function device, where the eighth message is used to request establishing or modifying a session corresponding to the non-unmanned aerial vehicle service.

[0040] In the above implementation, when the first device determines that the second condition is met, the first device suspends the restriction on the terminal device's non-unmanned aerial vehicle services, so that the first device can perform non-unmanned aerial vehicle services, thereby improving compatibility.

[0041] In a possible implementation, the method may further include: a step of the first device determining that a second condition is met, where the second condition includes one or more of the following conditions: approval for the unmanned aircraft service is revoked from the terminal device, the terminal device is not approved for the unmanned aircraft service, the unmanned aircraft service of the terminal device is deregistered, or the terminal device releases the last session corresponding to the unmanned aircraft service; a step of the first device receiving a fourth message from the third device, where the fourth message is used to request that a first control plane procedure be performed; and a step of the first device performing the first control plane procedure.

[0042] In the above implementation method, when the first device determines that the second condition is met, the first device ceases to restrict the first control plane procedure, so that the first device can execute the first control plane procedure, thereby improving compatibility.

[0043] According to a second aspect, the present application provides a communication method. The method may be performed by a second device or a component (e.g., a chip) of the second device. In the method, the second device receives a message from a first session management function device used to request restriction of a non-unmanned aerial vehicle service of a terminal device; the second device determines, based on the message, that the second session management function device manages a session corresponding to the non-unmanned aerial vehicle service of the terminal device; and the second device sends instruction information to the second session management function device, where the instruction information instructs the second session management function device to release all or part of the session corresponding to the non-unmanned aerial vehicle service managed by the second session management function device and / or instructs the second device to prohibit establishment or modification of the session corresponding to the non-unmanned aerial vehicle service.

[0044] In this embodiment of the present application, in response to the message restricting the non-unmanned aerial vehicle service of the terminal device, the second device determines a session management function device that manages a session corresponding to the non-unmanned aerial vehicle service of the terminal device, and sends instruction information to the session management function device to instruct the session management function device to restrict the non-unmanned aerial vehicle service of the terminal device, thereby reducing attacks that an attacker may perform on an unmanned aerial vehicle by using the non-unmanned aerial vehicle service and preventing the non-unmanned aerial vehicle service from occupying resources of the unmanned aerial vehicle service.

[0045] In a possible implementation, the method may further include: the second device sending first instruction information to the first session management function device, wherein the first instruction information instructs the second device to release one or more sessions corresponding to the non-unmanned aerial vehicle service.

[0046] In a possible implementation, the method may further include: the second device receiving N from the first session management capability device, where N is the number of sessions corresponding to non-unmanned aircraft services managed by the first session management capability device; and the second device determining, based on the number of sessions corresponding to non-unmanned aircraft services established by the terminal device, N and M, that the first session management capability device needs to release one or more sessions corresponding to the non-unmanned aircraft services, where M is the number of sessions corresponding to non-unmanned aircraft services that are allowed to be established on the first session management capability device when the terminal device executes the unmanned aircraft service.

[0047] In the above implementation method, the second device may maintain the number of sessions corresponding to non-unmanned aerial vehicle services established by the terminal device, and may refer to N and M to determine the number of sessions corresponding to non-unmanned aerial vehicle services that need to be released by each of the one or more session management function devices corresponding to the terminal device.

[0048] According to a third aspect, the present application provides a communication device configured to perform the method according to the first aspect and any one of the possible implementations of the first aspect, the communication device being, for example, a first device or a functional module in the first device, for example, a baseband device or a chip system.

[0049] In one possible implementation, the communication device includes a baseband device and a radio frequency device. In another possible implementation, the communication device includes a processing unit (sometimes also referred to as a processing module) and a transceiver unit (sometimes also referred to as a transceiver module). The transceiver unit may implement a transmitting function and a receiving function. When the transceiver unit implements a transmitting function, the transceiver unit may be referred to as a transmitting unit (sometimes also referred to as a transmitting module). When the transceiver unit implements a receiving function, the transceiver unit may be referred to as a receiving unit (sometimes also referred to as a receiving module). The transmitting unit and the receiving unit may be the same functional unit, and the functional unit is referred to as a transceiver unit. The functional unit may implement a transmitting function and a receiving function. Alternatively, the transmitting unit and the receiving unit may be different functional units, and the transceiver unit is a collective term for these functional units.

[0050] According to a fourth aspect, the present application provides a communications device configured to perform the method according to the second aspect and any one of the possible implementations of the second aspect, the communications device being, for example, a second device or a functional module in the second device, for example, a baseband device or a chip system.

[0051] In one possible implementation, the communication device includes a baseband device and a radio frequency device. In another possible implementation, the communication device includes a processing unit (sometimes also referred to as a processing module) and a transceiver unit (sometimes also referred to as a transceiver module). The transceiver unit may implement a transmitting function and a receiving function. When the transceiver unit implements a transmitting function, the transceiver unit may be referred to as a transmitting unit (sometimes also referred to as a transmitting module). When the transceiver unit implements a receiving function, the transceiver unit may be referred to as a receiving unit (sometimes also referred to as a receiving module). The transmitting unit and the receiving unit may be the same functional unit, and the functional unit is referred to as a transceiver unit. The functional unit may implement a transmitting function and a receiving function. Alternatively, the transmitting unit and the receiving unit may be different functional units, and the transceiver unit is a collective term for these functional units.

[0052] According to a fifth aspect, the present application provides a communication device. The communication device may include one or more processors. Optionally, the communication device may further include a memory. The memory is configured to store one or more computer programs or instructions. The one or more processors are configured to execute the one or more computer programs or instructions stored in the memory, such that the communication device performs the method according to the first aspect and any one of the possible implementations of the first aspect.

[0053] According to a sixth aspect, the present application provides a communications device. The communications device may include one or more processors. Optionally, the communications device may further include a memory. The memory is configured to store one or more computer programs or instructions. The one or more processors are configured to execute the one or more computer programs or instructions stored in the memory, such that the communications device performs the method according to the second aspect and any one of the possible implementations of the second aspect.

[0054] According to a seventh aspect, the present application provides a communication system, comprising a communication device according to the fifth aspect and / or a communication device according to the sixth aspect.

[0055] According to an eighth aspect, the present application provides a computer-readable storage medium configured to store a computer program or instructions that, when executed, implement a method according to the first aspect and any one of its possible implementations, or a method according to the second aspect and any one of its possible implementations.

[0056] According to a ninth aspect, the present application provides a computer program product comprising instructions, which when run on a computer, implement a method according to the first aspect and any one of its possible implementations, or a method according to the second aspect and any one of its possible implementations.

[0057] According to a tenth aspect, the present application further provides a chip, coupled to a memory and configured to read and execute program instructions in the memory, such that an apparatus in which the chip is disposed implements the method according to the first aspect and any one of its possible implementations, or the method according to the second aspect and any one of its possible implementations. Optionally, a chip system may include the chip, or may include the chip and another discrete component.

[0058] For technical effects that can be achieved in any one of the third to tenth aspects and possible implementations of the third to tenth aspects, please refer to the corresponding technical effects that can be achieved in any one of the first and second aspects and possible implementations of the first and second aspects, and details will not be described again here. [Brief explanation of the drawings]

[0059] [Figure 1] FIG. 1 is a diagram of a network architecture. [Figure 2] FIG. 2 is another diagram of a network architecture. [Figure 3]FIG. 1 is a diagram of unmanned aerial vehicle services and non-unmanned aerial vehicle services. [Figure 4] 1 is a schematic flowchart of a communication method according to an embodiment of the present application; [Figure 5] 4 is another schematic flowchart of a communication method according to an embodiment of the present application; [Figure 6] 4 is another schematic flowchart of a communication method according to an embodiment of the present application; [Figure 7] 4 is another schematic flowchart of a communication method according to an embodiment of the present application; [Figure 8] 4 is another schematic flowchart of a communication method according to an embodiment of the present application; [Figure 9] 4 is another schematic flowchart of a communication method according to an embodiment of the present application; [Figure 10] 4 is another schematic flowchart of a communication method according to an embodiment of the present application; [Figure 11] 4 is another schematic flowchart of a communication method according to an embodiment of the present application; [Figure 12] 4 is another schematic flowchart of a communication method according to an embodiment of the present application; [Figure 13] 4 is another schematic flowchart of a communication method according to an embodiment of the present application; [Figure 14] 1 is a diagram of the structure of a communication device according to an embodiment of the present application; [Figure 15] FIG. 2 is another diagram of the structure of a communication device according to an embodiment of the present application. DETAILED DESCRIPTION OF THE INVENTION

[0060] To clarify the objectives, technical solutions, and advantages of the embodiments of the present application, the following first describes some terms used in the embodiments of the present application. (1) A terminal device may also be referred to as a user equipment (UE), an access terminal, a terminal, a subscriber unit, a subscriber station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a user agent, a user equipment, or the like. The terminal device may be, for example, a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a smartphone, a mobile phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), or the like. Alternatively, the terminal device may be a handheld device with wireless communication capabilities, a computing device or another device connected to a wireless modem, an in-vehicle device, a wearable device, an unmanned aerial vehicle, a terminal in the Internet of Things or Internet of Vehicles, any form of terminal in a 5G network and a future network, a relay user equipment, a terminal in a future evolved 6G network, or the like. The type, category, or the like of the terminal device is not limited in the embodiments of the present application.

[0061] The functionality of the terminal device may be implemented by using hardware components within the terminal device, which may be a processor and / or a programmable chip within the terminal device. Optionally, the chip may be implemented by an application-specific integrated circuit (ASIC) or a programmable logic device (PLD). The PLD may be any one of a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL), and a system on a chip (SOC), or any combination thereof.

[0062] Additionally, to facilitate understanding of the embodiments of the present application, the following description will use an example in which the terminal device is an unmanned aircraft. (2) Unmanned aircraft services are services specific to unmanned aircraft that are enjoyed by unmanned aircraft. Unmanned aircraft services may be communication services provided by a network for unmanned aircraft on the control plane and / or user plane. For example, unmanned aircraft services may be control plane procedures (such as unmanned aircraft authentication, authorization, or flight path approval), command and control (C2) communications, remote unmanned aircraft identification, remote positioning, no-fly zone, or flight map download services that are dedicated to or specific to unmanned aircraft. However, the type of unmanned aircraft service is not limited in the embodiments of the present application. (3) Non-unmanned aircraft services are services other than unmanned aircraft services that may be enjoyed by a common terminal device. Non-unmanned aircraft services may be, for example, multimedia communication services, data services, or Internet services. However, the type of non-unmanned aircraft services is not limited in the embodiments of the present application.

[0063] Note that an unmanned aerial vehicle may be considered a common terminal device when the network cannot identify the type of the unmanned aerial vehicle (e.g., when the network identifies the unmanned aerial vehicle as a common terminal) or when the unmanned aerial vehicle service is not authorized. In this case, the service provided by the network for the unmanned aerial vehicle is a non-unmanned aerial vehicle service. (4) In the embodiments of this application, "multiple" means two or more. In light of this, "multiple" in the embodiments of this application may also be understood as "at least two." "At least one" may be understood as one or more, for example, one, two, or more. For example, "including at least one" means "including one, two, or more," without limiting which is included. For example, "including at least one of A, B, and C" may mean "including A, B, or C," "including A and B, A and C, or B and C," or "including A, B, and C." The term "and / or" describes a relationship between related objects and indicates that three relationships may exist. For example, A and / or B may indicate the following three cases: only A is present, both A and B are present, and only B is present. In addition, the symbol " / " generally indicates an "or" relationship between associated objects unless otherwise specified. The terms "system" and "network" in the embodiments of the present application may be used interchangeably.

[0064] Unless otherwise specified, ordinal numbers such as "first" and "second" in the embodiments of the present application are used to distinguish between multiple objects and are not used to limit the order, chronological order, priority, or importance of the multiple objects. For example, the terms "first device," "second device," "third device," and "fourth device" in the embodiments of the present application are used to distinguish between multiple devices and are not used to limit the priority or importance of the multiple devices. In another example, the terms "first message," "second message," "third message," "fourth message," and the like in the embodiments of the present application are used to distinguish between multiple messages and are not used to limit the order, chronological order, priority, or importance of the multiple messages.

[0065] Additionally, in the embodiments of this application, the term "example" is used to mean serving as an example, illustration, or explanation. Any embodiment or design manner described herein as an "example" should not be construed as preferred or having more advantages than another embodiment or design manner. Specifically, the term "example" is used to present concepts in a concrete manner.

[0066] All aspects, embodiments, or features are presented herein by describing systems that may include multiple devices, components, modules, and the like. It is expressly understood that each system may include other devices, components, modules, etc. and / or may not include all of the devices, components, modules, etc. described with reference to the accompanying drawings. Additionally, combinations of these solutions may be used.

[0067] The above explains some terms in the embodiments of the present application. The following explains a communication system to which the embodiments of the present application are applicable.

[0068] It should be noted that the network architecture and service scenarios described in the embodiments of the present application are intended to more clearly explain the technical solutions in the embodiments of the present application, and do not constitute limitations on the technical solutions provided in the embodiments of the present application. Those skilled in the art may recognize that with the development of network architecture and the application of new service scenarios, the technical solutions provided in the embodiments of the present application can also be applied to similar technical problems.

[0069] The technical solutions in the embodiments of the present application may be applied to various communication systems. In a communication system, a part operated by an operator may be referred to as a public land mobile network (PLMN) (also referred to as an operator network, a mobile communication network, or the like). A PLMN is a network established and operated by a government or an operator authorized by a government to provide land mobile communication services to the public, and is primarily a public network through which a mobile network operator (MNO) provides mobile broadband access services to users. The PLMN described in this application may specifically be a network conforming to the requirements of the 3rd generation partnership project (3GPP®) standard, referred to as a 3GPP® network for short. A 3GPP® network typically includes, but is not limited to, a fifth-generation (5G) mobile communication network (5G network for short), a fourth-generation (4G) mobile communication network (4G network for short), and other future communication systems such as a 6G network. For ease of explanation, a PLMN or a 5G network is used as an example for explanation in the embodiments of this application.

[0070] 1 is a diagram of a network architecture according to an embodiment of the present application. A 5G network architecture based on a service-based architecture in a non-roaming scenario defined in the 3GPP standardization process is used as an example. The network architecture may include three parts: a terminal device part, a data network (DN) part, and a PLMN part.

[0071] The terminal device portion may include a terminal device 110, which may establish a connection with an operator network through an interface (e.g., N1) provided by the operator network and use services such as data and / or voice provided by the operator network. The terminal device 110 may further access a data network 120 through the operator network and use operator services deployed on the data network 120 and / or services provided by a third party. The third party may be a service provider other than the operator network and the terminal device 110, and may provide other services such as data and / or voice to the terminal device 110. The specific expression form of the third party may be specifically determined based on actual application scenarios and is not limited in this specification. For the description of the terminal device 110, please refer to the description of the terminal device in the above terminology section. Details will not be described again here.

[0072] The data network 120 may also be referred to as a packet data network (PDN), and is typically a network outside the operator network, such as a third-party network. The operator network may have access to multiple data networks 120, and multiple services may be deployed on the data network 120 to provide services such as data and / or voice to the terminal devices 110. For example, the data network 120 may be a private network of a smart factory, and sensors installed in the workshops of the smart factory may be terminal devices 110, and control servers for the sensors may be deployed on the data network 120, and the control servers may provide services to the sensors. The sensors may communicate with the control server to obtain instructions from the control server, transmit collected sensor data to the control server according to the instructions, and so on. In another example, the data network 120 may be an internal network of a company, and the mobile phones or computers of the company's employees may be terminal devices 110, and the employee's mobile phones or computers may access information and data resources, etc., on the internal network of the company.

[0073] The PLMN may include, but is not limited to, a network exposure function (NEF) 131, a network repository function (NRF) 132, a policy control function (PCF) 133, a unified data management (UDM) 134, an unmanned / uncrewed aerial system (UAS) function 135, an authentication server function (AUSF) 136, an access and mobility management function (AMF) 137, a session management function (SMF) 138, a user plane function (UPF) 139, a (radio) access network ((R)AN) 140, an application function (AF) 141, a network slice specific authentication and authorization function (NSSAAF) 142, and the like. In a PLMN, the part other than the (radio) access network 140 part may be referred to as the core network (CN) part.

[0074] For example, the following briefly describes network functions that may be used in the embodiments of the present application: In addition, Figure 1 also relates to other network elements, the details of which will not be described herein.

[0075] The AN 140, also referred to as a Radio AN, can be regarded as a subnet of an operator network and is an implementation system between a service node in the operator network and the terminal device 110. To access the operator network, the terminal device 110 can first pass through the (R)AN 140 and then connect to a service node in the operator network through the (R)AN 140. An access network device (RAN device) in the embodiment of the present application is a device that provides wireless communication functions to the terminal device 110 and can also be referred to as a network device. RAN devices include, but are not limited to, next generation node base stations (gNBs) in 5G systems, evolved NodeBs (eNBs) in long term evolution (LTE), radio network controllers (RNCs), NodeBs (NBs), base station controllers (BSCs), base transceiver stations (BTSs), home base stations (e.g., home evolved NodeBs or Home NodeBs (HNBs)), baseband units (BBUs), transmitting and receiving points (TRPs), transmitting points (TPs), pico base station devices (pico), mobile switching centers, network devices in future networks, or the like. In systems using different radio access technologies, devices with the functionality of access network devices may have different names. For ease of description, in all embodiments of the present application, the above-mentioned devices that provide wireless communication capabilities to the terminal device 110 are collectively referred to as access network devices, or abbreviated as RAN or AN. It should be understood that the specific type of access network device is not limited herein.

[0076] The network publication function 131 is a control plane function provided by an operator and configured to enable third parties to use services provided by the network. For example, in a 5G communication system, the network publication function 131 may be a NEF as shown in FIG. 1. In future communication systems such as a 6G communication system, the network publication function 131 may still be a NEF or may have another name. This is not limited in the embodiments of the present application.

[0077] The network repository function 132 is a control plane function provided by an operator and may be configured to maintain real-time information of all network function services in the network. For example, in a 5G communication system, the network repository function 132 may be an NRF as shown in FIG. 1. In future communication systems such as a 6G communication system, the network repository function 132 may still be an NRF or may have another name. This is not limited to the embodiments of the present application.

[0078] The policy control function 133 is a control plane function provided by an operator that governs network behavior and supports a unified policy framework that provides policy rules and subscription information related to policy decisions for other control functions. For example, in a 5G communication system, the policy control function 133 may be a PCF as shown in FIG. 1. In future communication systems such as a 6G communication system, the policy control function 133 may still be a PCF or may have another name. This is not limited in the embodiments of the present application.

[0079] The unified data management 134 is a control plane function provided by an operator and is responsible for storing information such as a subscriber permanent identifier (SUPI), a subscriber's generic public subscription identifier (GPSI), credentials, and the like, of a subscriber in the operator network. The SUPI is first encrypted during transmission, and the encrypted SUPI is called a subscription concealed identifier (SUCI). The information stored in the unified data management 134 can be used for authentication and authorization of the terminal device 110 to access the operator network. A subscriber in the operator network may specifically be a user who uses a service provided by the operator network, such as a user who uses a China Telecom SIM card or a user who uses a China Mobile SIM card. The subscriber's credentials may be a long-term key stored in the SIM card or a small stored file, such as information related to SIM card encryption, used for authentication and / or authorization. For ease of explanation, it should be noted that information such as a permanent identifier, credentials, security context, authentication data (cookies), and tokens related to verification / authentication and authorization are not limited or distinguished in the embodiments of the present application. For example, in a 5G communication system, the unified data management 134 may be a UDM as shown in FIG. 1. In future communication systems such as a 6G communication system, the unified data management 134 may still be a UDM or may have another name. This is not limited in the embodiments of the present application.

[0080] Unmanned aerial system functions 135 are control plane functions provided by operators that serve unmanned aerial systems and are responsible for exposing unmanned aerial system service capabilities supported by the network to external networks. For example, unmanned aerial system functions 135 may expose unmanned aerial system authentication / authorization services, unmanned aerial system flight authorization services, pairing authorization between unmanned aerial systems and remote controls, unmanned aerial system recertification / authorization / revoke, unmanned aerial system location reporting, unmanned aerial system quality of service (QoS) control, traffic filtering for command and control (C2) communications, and the like. Unmanned aerial system functions 135 may be instances created by network publishing function 131, subfunctions of common network publishing function 131, or independent functions specifically used to provide unmanned aerial system services, and therefore generally referred to as UAS NF / NEF. However, embodiments of the present application are not limited thereto.

[0081] The authentication server function 136 is a control plane function provided by an operator, and is typically for primary authentication, i.e., network authentication between the terminal device 110 (subscriber) and the PLMN. After receiving an authentication request initiated by a subscriber, the authentication server function 136 may perform authentication and / or authorization for the subscriber by using authentication information and / or authorization information stored in the integrated data management 134, or may generate authentication information and / or authorization information for the subscriber by using the integrated data management 134. The authentication server function 136 may feed back the authentication information and / or authorization information to the subscriber. For example, in a 5G communication system, the authentication server function 136 may be an AUSF, as shown in FIG. 1 . In future communication systems, such as a 6G communication system, the authentication server function 136 may still be an AUSF, or may have another name. This is not limited to the embodiments of the present application.

[0082] The access and mobility management function 137 is a control plane network function provided by the PLMN, and is responsible for access control and mobility management for the terminal device 110 to access the PLMN, including functions such as mobility status management, temporary user identity allocation, and user authentication and authorization. For example, in a 5G communication system, the access and mobility management function 137 may be an AMF as shown in Figure 1. In future communication systems such as a 6G communication system, the access and mobility management function 137 may still be an AMF or may have another name. This is not limited in the embodiments of the present application.

[0083] The session management function 138 is a control plane network function provided by the PLMN and is responsible for managing protocol data units (PDUs) of the terminal device 110. A PDU session is a channel for transmitting PDUs, and the terminal device and the DN 120 need to transmit data to each other through the PDU session. The session management function 138 may be responsible for establishing, maintaining, deleting, and the like of PDU sessions. The session management function 138 includes session-related functions such as session management (such as session establishment, modification, and release, including tunnel maintenance between the user plane function 139 and the AN 140), selection and control of the user plane function 139, service and session continuity (SSC) mode selection, and roaming. For example, in a 5G communication system, the session management function 138 may be an SMF, as shown in FIG. 1. In future communication systems, such as a 6G communication system, the session management function 138 may still be an SMF or may have another name. This is not limited to the embodiments of the present application.

[0084] The user plane function 139 is a gateway provided by the PLMN for communicating with the data network DN 120. The user plane function 139 includes user plane-related functions such as data packet routing and transmission, data packet detection, service utilization reporting, quality of service (QoS) processing, lawful interception, uplink data packet detection, and downlink data packet storage. For example, in a 5G communication system, the user plane function 139 may be a UPF as shown in FIG. 1. In future communication systems such as a 6G communication system, the user plane function 139 may still be a UPF or may have another name. This is not limited in the embodiments of the present application.

[0085] The application function 141 is a control plane function and may be deployed by an operator or an external third party. The application function 141 interacts with other network functions of the core network to support services such as traffic routing control, interaction with the policy control function 133, and access network function exposure. For example, in a 5G communication system, the application function 141 may be an AF as shown in FIG. 1 . In future communication systems such as a 6G communication system, the application function 141 may still be an AF or may have another name. This is not limited to the embodiments of the present application.

[0086] The network slice-specific authentication and authorization function 142 is a control plane network function provided by the PLMN and configured to support slice authentication performed between the terminal device 110 and the data network 120. For example, in a 5G communication system, the network slice-specific authentication and authorization function 142 may be an NSSAAF as shown in FIG. 1. In future communication systems such as a 6G communication system, the network slice-specific authentication and authorization function NSSAAF may still be an SMF or may have another name. This is not limited to the embodiments of the present application.

[0087] A network function in a PLMN may be a network element implemented on dedicated hardware, or may be a software instance running on dedicated hardware, or may be an instance of a virtualization function on an appropriate platform. For example, the virtualization platform may be a cloud platform. In addition, each network function in a PLMN may also be referred to as a network element, a functional entity, or a device. For example, an access and mobility management function may also be referred to as an access and mobility management function network element, an access and mobility management function entity, an access and mobility management function device, or the like, and a session management function may also be referred to as a session management function network element, a session management function entity, a session management function device, or the like. Details will not be listed one by one in this specification.

[0088] The network functions in the PLMN shown in Figure 1 may include further network functions. For example, the PLMN may further include a unified data repository (UDR) or the like (not shown in Figure 1). The other network functions included in the PLMN are not limited in the embodiments of the present application. In addition, the names of the network functions shown in Figure 1 are used herein merely as examples for explanation and are not intended to limit the network functions included in the network architecture to which the methods in the embodiments of the present application are applicable. The names of devices implementing network functions in systems of different access technologies may be different. This is not limited in the embodiments of the present application.

[0089] In FIG. 1, Nnef, Nnrf, Npcf, Nudm, Nausf, Namf, Nsmf, Nnssaaf, Naf, N1, N2, N3, N4, and N6 are interface serial numbers. For example, for the meaning of the interface serial numbers, please refer to the meaning defined in the 3GPP (registered trademark) standard protocol. The meaning of the interface serial numbers is not limited in this application. Please note that the names of the interfaces between network functions in FIG. 1 are merely examples. In a specific implementation, the names of the interfaces in the system architecture may alternatively be different names. This is not limited in this application.

[0090] It should be noted that the network architecture shown in Fig. 1 does not constitute a limitation on the communication system to which the embodiments of the present application are applicable. The network architecture shown in Fig. 1 is a 5G system architecture. Optionally, in addition to the 5G system, the technical solutions provided in the embodiments of the present application may also be applied to the 4th generation mobile communication technology (4G) system, for example, the LTE system, or may also be applied to a next-generation mobile communication system or another similar communication system. This is not specifically limited.

[0091] Based on the network architecture shown in Figure 1, Figure 2 is a diagram in which a 5G mobile network and an unmanned aerial system are combined. As shown in Figure 2, a network entity of an unmanned aerial system service supplier (UAS service supplier, USS) 121 is added in Figure 2. The network entity typically does not belong to an operator network but is deployed in a third-party data network 120. However, embodiments of the present application are not limited thereto. The unmanned aerial system service 121 communicates with an unmanned aerial system function 135 in a 3GPP network through an N33 interface.

[0092] The unmanned aerial system service 121 may store information related to the UAS, such as authentication information of the UAS. Based on this information, the unmanned aerial system service 121 may perform identity authentication, flight authorization, and the like for the unmanned aerial vehicle. The oversight department of the UAS may further use the unmanned aerial system service 121 to oversee the operation of the UAS and ensure the safety of unmanned aerial vehicle flight control and public safety. The unmanned aerial system service 121 may also establish a channel with another oversight or flight safety department to obtain flight-related information. In some application scenarios, in addition to communicating with the unmanned aerial vehicle / remote control through the operator network, the unmanned aerial system service 121 may also have a function for remotely controlling the flight of the unmanned aerial vehicle. This is not limited here. Note that the unmanned aerial system service 121 may also represent an unmanned aerial system traffic management (UTM) entity or an entity that integrates the USS and UTM. This is not limited here.

[0093] In the mobile communication network-based remote-controlled UAS shown in FIG. 2 , an unmanned aerial vehicle can simultaneously play two roles: a terminal in an operator network (i.e., referred to as a PLMN or mobile communication network) and an unmanned aerial vehicle that can fly in the UAS. In terms of services provided by the operator network, the operator network not only provides the unmanned aerial vehicle with services enjoyed by common terminals (such as multimedia communication, data services, or the Internet), but also provides the unmanned aerial vehicle with services specific to unmanned aerial vehicles, such as certification and authorization for unmanned aerial vehicle types (including dedicated unmanned aerial vehicle certification and authorization, flight path approval, or the like), C2 communication, remote unmanned aerial vehicle identification, remote positioning, no-fly zones, and flight map downloads. For ease of explanation, hereinafter, services specific to unmanned aerial vehicles are referred to as unmanned aerial vehicle services, and services not specific to unmanned aerial vehicles are referred to as non-unmanned aerial vehicle services. For details, please refer to the terminology section above. Details will not be repeated here.

[0094] Because unmanned aerial vehicles can simultaneously fulfill two roles, they are exposed to potential safety risks from denial of service (DoS) attacks. Specifically, during the flight of an unmanned aerial vehicle, an attacker may use the unmanned aerial vehicle's non-unmanned aerial vehicle services to transmit large amounts of video, internet data, and the like unrelated to the unmanned aerial vehicle service to the unmanned aerial vehicle, intentionally consuming the unmanned aerial vehicle's resources (network resources, computing resources, battery resources, and the like) and occupying the resources required by the unmanned aerial vehicle to perform the unmanned aerial vehicle service, thereby affecting the normal operation of the unmanned aerial vehicle (e.g., causing the unmanned aerial vehicle to delay responses to C2 communication commands or causing rapid battery drain). As a result, the unmanned aerial vehicle may deviate from its flight direction, fail to arrive as expected, or even experience a safety incident such as a crash.

[0095] FIG. 3 is used as an example. FIG. 3 illustrates the relationship between PDU sessions and DNs. As shown in FIG. 3, DN1 is a DN specifically used for unmanned aircraft services and supports only the unmanned aircraft service session (PDU session 1). DN2 is a DN specifically used for unmanned aircraft services and non-unmanned aircraft services and supports both the unmanned aircraft service PDU session (PDU session 2) and the non-unmanned aircraft service PDU session (PDU session 3). DN3 is a DN specifically used for non-unmanned aircraft services and supports only the non-unmanned aircraft service PDU session (PDU session 4). As shown in FIG. 3, during the flight process of an unmanned aircraft, a large amount of the unmanned aircraft's resources are consumed by the non-unmanned aircraft services, which in turn consumes a large amount of the unmanned aircraft's battery resources, making it impossible to ensure that the unmanned aircraft has sufficient battery resources to reach its destination. In addition, the non-unmanned aircraft services occupy a large amount of the unmanned aircraft's computing resources. This delays the computing results of the unmanned aircraft service, causing failure to respond correctly and promptly to remote control commands. As a result, there are potential risks such as errors in the actual flight route, delays in the arrival of the unmanned aerial vehicle, and flight accidents.

[0096] In view of this, embodiments of the present application provide a communication method and apparatus. In the method, if it is determined that a condition is met, a first device restricts a non-unmanned aircraft service of a terminal device and / or restricts a first control plane procedure of the terminal device. The first control plane procedure is not a procedure specific to the unmanned aircraft service. The first condition includes at least one of: the terminal device being authorized for the unmanned aircraft service, the terminal device initiating establishment of a first session corresponding to the unmanned aircraft service, or the terminal device being in a flight state. In this way, the first device conditionally restricts the non-unmanned aircraft service of the terminal device to reduce attacks that an attacker may launch against the terminal device by using the non-unmanned aircraft service and to prevent the non-unmanned aircraft service from occupying resources of the unmanned aircraft service. In addition, the first device conditionally restricts the first control plane procedure, freeing up resources required to execute the first control plane procedure, so that more available resources can be reserved for the unmanned aircraft service, thereby avoiding problems such as the terminal device being unable to function normally or even a crash due to insufficient resources, or the like.

[0097] In order to better explain the embodiments of the present application, the methods provided in the embodiments of the present application will be described below with reference to the accompanying drawings. In the accompanying drawings corresponding to the embodiments of the present application, all optional steps are represented by dotted lines. All the methods provided in the embodiments of the present application can be applied to the communication system shown in Figure 1 or Figure 2.

[0098] It should be noted that in the embodiment of the present application, the unmanned aircraft service and the non-unmanned aircraft service of the terminal device are used as an example. The non-unmanned aircraft service and / or the first control plane procedure are restricted to prevent the non-unmanned aircraft service from occupying the resources of the unmanned aircraft service and to reserve more available resources for the unmanned aircraft service. It should be understood that the unmanned aircraft service can be replaced with a first type of service of the terminal device, and the non-unmanned aircraft service can be replaced with a second type of service of the terminal device. This is also applicable to the embodiment of the present application. In other words, in the embodiment of the present application, the first type of service is not limited to the unmanned aircraft service, and the second type of service is not limited to the non-unmanned aircraft service. For example, the first type of service is a service having high reliability requirements and low latency requirements, and the second type of service is a service without high reliability or low latency requirements. Procedures specific to the second type of service and / or not specific to the first type of service are restricted to prevent the second type of service from occupying resources of the first type of service and to reserve more available resources for the first type of service, thereby ensuring successful execution of the first type of service. In another example, the first type of service is a high priority service and the second type of service is a low priority service.

[0099] It should be noted that the embodiments of the present application relate to a first device, a second device, a third device, and a fourth device. The first device may be a session management function device, a short message service-service center (SMS-SC), a terminal device, a security anchor function (SEAF) device, an access and mobility management function device, an integrated data management device, an authentication server function device, or an authentication credential repository and processing function (ARPF) device, or may be another device including the functions of the above devices, or may be a component (such as a chip or a functional module) in the above devices. The specific implementation form of the first device is not limited in the embodiments of the present application.

[0100] The second device may be an integrated data management device, an integrated data repository device, or a policy control function device, or may be another device including the functions of the above devices, or may be a component (such as a chip or a functional module) in the above devices. The specific implementation form of the second device is not limited in the embodiments of the present application.

[0101] The third device may be a security anchor function device, an access and mobility management function device, an integrated data management device, a network slice-specific authentication and authorization function device, an authentication, authorization, and accounting server (AAA-S), or a data network, or may be another device including the functions of the above devices, or may be a component (such as a chip or a functional module) in the above devices. The specific implementation form of the third device is not limited to the embodiments of the present application.

[0102] The fourth device may be a terminal device, an access network device, an unmanned aerial system service, or an unmanned aerial system function device, or may be another device including the function of the above device, or may be a component (such as a chip or a function module) in the above device. The specific implementation form of the fourth device is not limited to the embodiments of the present application.

[0103] For ease of explanation, in the following embodiments, the session management function device is replaced by an SMF, the short message service service center is replaced by an SMS-SC, the terminal device is replaced by a UE, the security anchor function device is replaced by a SEAF, the access and mobility management function device is replaced by an AMF, the integrated data management device is replaced by a UDM, the authentication server function device is replaced by an AUSF, the authentication visual information repository and processing function device is replaced by an ARPF, the integrated data repository device is replaced by a UDR, the policy control function device is replaced by a PCF, the network slice-specific authentication and authorization function device is replaced by an NSSAAF, authentication, authorization and charging is replaced by an AAA-S, the data network is replaced by a DN, the access network device is replaced by a RAN, the unmanned aerial system service is replaced by a USS, the unmanned aerial system function device is replaced by a UAS NF / NEF or a UAS NF, and the application function device is replaced by an AF.

[0104] It should be noted that in the embodiment of the present application, multiple session management function devices can be supported to simultaneously manage sessions of a UE. For ease of understanding, the embodiment of the present application uses an example in which a first session management function device and a second session management function device can simultaneously manage sessions of a UE. For ease of explanation, in the following embodiment, the first session management function device is replaced by SMF1, and the second session management function device is replaced by SMF2. In addition, the session in the embodiment of the present application may be a PDU session or another session. The specific implementation form of the session is not limited in the embodiment of the present application.

[0105] 4 is a schematic flowchart of a communication method according to an embodiment of the present application. As shown in FIG. 4, the method may include the following contents:

[0106] S401: A first device determines that a first condition is met.

[0107] The first condition includes one or more of the following conditions: the UE is authorized for the unmanned aircraft service, the UE initiates establishment of a first session corresponding to the unmanned aircraft service, or the UE is in an airborne state.

[0108] In an example, the first device may determine that the UE is authorized for unmanned aerial vehicle service. Authorization of the UE for unmanned aerial vehicle service may be understood as one or more of registration authorization for the UE to serve as an unmanned aerial vehicle, session authorization corresponding to the unmanned aerial vehicle service, pairing authorization, or flight authorization. However, embodiments of the present application are not limited thereto.

[0109] Registration approval for a UE serving as an unmanned aerial vehicle may be understood as the UE serving as an unmanned aerial vehicle obtaining approval from the USS during a registration procedure. Session approval corresponding to unmanned aerial vehicle service may be understood as the UE obtaining approval from the USS during a session establishment or modification procedure for the UE to serve as an unmanned aerial vehicle. Pairing approval may be understood as the USS approving a pairing relationship between a UE and a corresponding remote control and permitting communication between the paired UE and the remote control, for example, transmission of C2 information between the UE and the remote control. It should be understood that pairing approval may be performed during the session establishment or modification procedure or in a separate procedure. This is not a limitation in this application. Flight approval means that the USS approves flight-related information, such as the UE's flight route and flight plan. Flight approval may be performed during the session establishment or modification procedure or in a separate procedure. This is not a limitation in this application.

[0110] After the UE is authorized for the unmanned aerial vehicle service, the USS may notify the network of the authorization result indicating that the UE is authorized for the unmanned aerial vehicle service. Thus, a device, for example, a first device in the network, may obtain the authorization result.

[0111] For example, when a UE is authorized for unmanned aerial vehicle service, this is registration approval for the UE serving as an unmanned aerial vehicle. In the registration procedure for the UE serving as an unmanned aerial vehicle, the AMF initiates an authentication and authorization procedure between the unmanned aerial vehicle and the USS (through the UAS NF) to the USS. The USS may complete authentication and authorization for the UE (i.e., complete registration approval for the unmanned aerial vehicle) and send an authorization result to the UAS NF and / or AMF in the network indicating that registration approval for the UE serving as an unmanned aerial vehicle has been successful. Optionally, the AMF or UAS NF may send the authorization result to the SMF. Thus, a first device in the network (such as the SMF or AMF) may determine that the UE has obtained registration approval from the USS based on the authorization result and store the authorization result.

[0112] For example, a UE being authorized for an unmanned aerial vehicle service is a session authorization corresponding to the unmanned aerial vehicle service. In a session establishment or modification procedure in which the UE serves as an unmanned aerial vehicle, the SMF initiates a session authorization procedure for the unmanned aerial vehicle service between the unmanned aerial vehicle and the USS (through the UAS NF) to the USS. The USS may complete session authorization for the UE and send an authorization result to the UAS NF and / or the SMF. Optionally, the SMF or UAS NF may send an authorization result to the AMF indicating that the session corresponding to the unmanned aerial vehicle service is authorized. Thus, the first device (such as the SMF or AMF) may determine that the UE has obtained unmanned aerial vehicle session authorization from the USS based on the authorization result and store the authorization result.

[0113] For example, a UE being authorized for unmanned aerial vehicle services is a pairing authorization. In a session establishment or modification procedure in which the UE serves as an unmanned aerial vehicle, the SMF initiates a session authorization procedure for unmanned aerial vehicle services between the unmanned aerial vehicle and the USS (through the UAS NF) to the USS. The USS determines whether the UE is authorized to perform pairing with the corresponding remote control based on the pairing information in the message sent by the SMF or the pairing information stored in the USS, and sends the pairing authorization result to the UAS NF and / or the SMF. Optionally, the SMF or the UAS NF may send the pairing authorization result to the AMF. Thus, the first device (such as the SMF or the AMF) may determine based on the pairing authorization result that the UE has obtained USS pairing authorization for the UE and the corresponding remote control, and store the pairing authorization result.

[0114] For example, when a UE is authorized for unmanned aerial vehicle service, flight authorization is obtained. In a session establishment or modification procedure in which the UE serves as an unmanned aerial vehicle, the SMF initiates a session authorization procedure for unmanned aerial vehicle service between the unmanned aerial vehicle and the USS (through the UAS NF) to the USS. The USS determines whether to approve the UE's flight route (and / or flight plan) based on information about the UE's flight route (and / or information such as a flight plan), and transmits the flight authorization result to the UAS NF and / or SMF. The information about the flight route and / or flight plan may be information from the UE or information stored in the USS. This is not limited to the embodiments of the present application. Optionally, the SMF or UAS NF may transmit the flight authorization result to the AMF. Therefore, the first device (such as the SMF or AMF) may determine that the UE has obtained flight authorization from the USS for the unmanned aerial vehicle based on the flight authorization result, and store the flight authorization result.

[0115] It should be noted that the above authorization procedure may be a procedure initiated by the network side (such as the SMF or AMF) or may be a procedure initiated by the USS. This is not limited in the present application. In addition, the above pairing authorization or flight authorization performed in a session establishment or modification procedure is used as an example. However, the embodiment of the present application is not limited thereto. For example, pairing authorization or flight authorization may alternatively be performed in a registration procedure. In addition, the above description is used as an example to describe a specific implementation process in which the first device determines that the UE is authorized for unmanned aircraft service. However, it should be understood that in this embodiment of the present application, the specific method and procedure in which the UE is authorized for unmanned aircraft service and the first device determines that the UE is authorized for unmanned aircraft service are not limited thereto.

[0116] In another example, a first device may determine that a UE initiates establishment of a first session corresponding to an unmanned aircraft service. For example, the first device is SMF1, and SMF1 may determine whether the UE initiates establishment of a first session corresponding to an unmanned aircraft service based on stored UE information (such as UE context information). The UE context information may include sessions established by the UE corresponding to different services. For example, SMF1 receives a message used to request establishment of a session (e.g., indicated as a second message, where the second message is used to request establishment of the first session) from the UE. SMF1 may determine whether the first session is a first session corresponding to the unmanned aircraft service of the UE based on the UE context information. For example, SMF1 may determine whether the first session belongs to a session corresponding to an unmanned aircraft service, and when determining that the first session belongs to a session corresponding to the unmanned aircraft service, determine whether the first session is a first session corresponding to the unmanned aircraft service of the UE based on the UE context information. For example, if the first session belongs to a session corresponding to a non-unmanned aircraft service, or if the first session belongs to a session corresponding to an unmanned aircraft service but the context information of the UE includes another session corresponding to the unmanned aircraft service, the SMF1 may determine that the second message is not a message used to establish the first session corresponding to the unmanned aircraft service. In another example, if the first session belongs to a session corresponding to an unmanned aircraft service and the context information of the UE does not include a session corresponding to the unmanned aircraft service, the SMF1 may determine that the second message is used to request the UE to establish a first session corresponding to the unmanned aircraft service, i.e., that the UE initiates the establishment of the first session corresponding to the unmanned aircraft service.

[0117] Optionally, the SMF1 may determine whether the first session belongs to a session corresponding to an unmanned aerial vehicle service. For example, the SMF1 may determine whether the first session belongs to a session corresponding to an unmanned aerial vehicle service based on the second message. The second message may include one or more of the following information: UE type indication information, a UAV identifier (ID), a data network name (DNN), USS address information, a USS ID, a single network slice selection assistance information (S-NSSAI) identifier, an AF ID, a session service type, or the like. It should be understood that the information may be included in the second message and sent to the SMF1, or may be included in another message and sent to the SMF1. This is not limited to this embodiment of the present application. The information will be described below. (1) The UE type indication information may indicate that the UE is an unmanned aerial vehicle or a common UE. For example, the second message includes UE type indication information, and the UE type indication information indicates that the UE is an unmanned aerial vehicle. The SMF1 may determine, based on the second message, that the first session belongs to a session corresponding to an unmanned aircraft service. In another example, the second message includes UE type indication information, where the UE type indication information indicates that the UE is a common UE. The SMF1 may determine, based on the second message, that the first session belongs to a session corresponding to a non-unmanned aircraft service. (2) The UAV ID may be an ID of the unmanned aircraft registered by the UE, or an ID of the unmanned aircraft assigned to the UE by the USS. If the second message includes a UAV ID, the SMF1 may determine, based on the second message, that the first session belongs to a session corresponding to an unmanned aircraft service. (3) The DNN may indicate a DN corresponding to the first session. The DN may be a DN associated with an unmanned aircraft service or a DN associated with a non-unmanned aircraft service. This is not limited to this embodiment of the present application.For example, the second message may include a DNN, and the DN indicated by the DNN is a DN associated with an unmanned aircraft service. The SMF1 may determine, based on the second message, that the first session belongs to a session corresponding to the unmanned aircraft service. In another example, the second message may include a DNN, and the DN indicated by the DNN is a DN associated with a non-unmanned aircraft service. The SMF1 may determine, based on the second message, that the first session belongs to a session corresponding to a non-unmanned aircraft service. (4) The USS address information or USS ID may indicate a USS providing a service to the first session. If the second message includes the USS address information and / or USS ID, the SMF1 may determine, based on the second message, that the first session belongs to a session corresponding to an unmanned aircraft service. (5) The S-NSSAI identifier may indicate a slice service type associated with the first session. The slice service type may be a slice service associated with an unmanned aircraft service or a slice service associated with a non-unmanned aircraft service. This is not limited to this embodiment of the present application. For example, the second message includes an S-NSSAI, and the S-NSSAI indicates a sliced ​​service corresponding to an unmanned aircraft service. The SMF1 may determine, based on the second message, that the first session belongs to a session corresponding to the unmanned aircraft service. In another example, the second message includes an S-NSSAI, and the S-NSSAI indicates a sliced ​​service corresponding to a non-unmanned aircraft service. The SMF1 may determine, based on the second message, that the first session belongs to a session corresponding to the non-unmanned aircraft service. (6) The AF ID may indicate a corresponding AF that initiates establishment of the first session. The AF may be an AF associated with the unmanned aircraft service or an AF associated with a non-unmanned aircraft service. This is not limited to this embodiment of the present application. For example, the second message includes an AF ID, and the AF indicated by the AF ID is an AF associated with the unmanned aircraft service. The SMF1 may determine, based on the second message, that the first session belongs to a session corresponding to the unmanned aircraft service.In another example, the second message includes an AF ID, and the AF indicated by the AF ID is an AF associated with a non-unmanned aircraft service. The SMF1 may determine, based on the second message, that the first session belongs to a session corresponding to a non-unmanned aircraft service. (7) The session service type may indicate a service type corresponding to the first session. The service type may be, for example, an unmanned aircraft service or a non-unmanned aircraft service. This is not limited to this embodiment of the present application. For example, the second message includes a session service type, and the session service type indicates an unmanned aircraft service. The SMF1 may determine, based on the second message, that the first session belongs to a session corresponding to an unmanned aircraft service. In another example, the second message includes a session service type, and the session service type indicates a non-unmanned aircraft service. The SMF1 may determine, based on the second message, that the first session belongs to a session corresponding to a non-unmanned aircraft service.

[0118] It should be noted that the SMF1 may alternatively determine whether the first session belongs to a session corresponding to an unmanned aircraft service based on a combination of the above information. For example, the second message includes a DNN and an S-NSSAI, and the combination of the DNN and the S-NSSAI indicates an unmanned aircraft service. The SMF1 may determine, based on the second message, that the first session belongs to a session corresponding to an unmanned aircraft service. In another example, the second message includes a DNN and an S-NSSAI, and the combination of the DNN and the S-NSSAI indicates a non-unmanned aircraft service. The SMF1 may determine, based on the second message, that the first session belongs to a session corresponding to a non-unmanned aircraft service. In addition, the SMF1 may alternatively determine whether the first session belongs to a session corresponding to an unmanned aircraft service based on a combination of two or more other types of information in the above information. In this embodiment of the present application, details will not be listed one by one.

[0119] In the above example, the first device is SMF1, and SMF1 may determine whether the UE will initiate the establishment of a first session corresponding to the unmanned aircraft service based on UE information (e.g., UE context information) stored in SMF1. Of course, the first device may alternatively be SMF2 or another SMF. For implementation information, please refer to the related content in which the first device is SMF1. Details will not be described again here. In another possible implementation, the first device is not an SMF, and the first device may determine whether the UE will initiate the establishment of a first session corresponding to the unmanned aircraft service from the SMF. For example, the first device may send to the SMF a message used to request subscribe to or obtain UE session information from the SMF. After the SMF determines that the UE will initiate the establishment of a first session corresponding to the unmanned aircraft service, the SMF may send to the first device indication information instructing the UE to initiate the establishment of a first session corresponding to the unmanned aircraft service. The first device receives the instruction information and determines, based on the instruction information, that the UE initiates the establishment of a first session corresponding to the unmanned aerial vehicle service.

[0120] The above describes how the first device determines that the UE is authorized for the unmanned aerial vehicle service and determines that the UE initiates the establishment of a first session corresponding to the unmanned aerial vehicle service. The following describes how the first device determines that the UE is in a flight state.

[0121] In an example, the first device is a UE, and the first device may determine that the UE is in a flight state based on the mobility information, or the fifth instruction information from the application layer, or the mobility information and the fifth instruction information from the application layer. The mobility information may include height and / or movement speed. For example, the UE may measure the horizontal height of the UE. If the measured horizontal height is greater than or equal to a height threshold, the UE may determine that the UE is in a flight state. The height threshold may be preset. This is not limited to this embodiment of the present application. In another example, the UE may measure the movement speed of the UE. If the measured movement speed is greater than or equal to a speed threshold, the UE may determine that the UE is in a flight state. The speed threshold may be preset. This is not limited to this embodiment of the present application. The fifth instruction information may instruct the UE to enter a flight mode.

[0122] In another example, the first device is an AMF, and the first device may maintain the status of the UE. The status of the UE includes a flight state and / or a non-flight state. For example, the first device may periodically or aperiodically acquire the status of the UE. For example, the first device may receive fourth indication information from the fourth device, where the fourth indication information indicates that the UE is in a flight state. Furthermore, the first device may determine that the UE is in a flight state based on the fourth indication information. The fourth device may actively send the fourth indication information to the first device, or may send the fourth indication information to the first device after receiving a message from the first device used to request the status of the UE. This is not limited to this embodiment of the present application. In another example, the first device may determine that the UE is in a flight state based on UE mobility information, or UE flight information, or UE mobility information and UE flight information. For example, the first device may obtain mobility information of the UE from a device such as a base station, a gateway mobile location center (GMLC), or a location management function (LMF) device. For example, if the moving speed (or height) in the mobility information of the UE is greater than or equal to a device threshold, the first device determines that the UE is in a flight state. Otherwise, the first device determines that the UE is in a non-flight state. For example, the first device may obtain flight information of the UE from a USS. The flight information may include a flight path, a flight schedule, and the like. For example, the first device may determine whether the current time and current location of the UE match the flight path and flight schedule. If the current time and current location of the UE match the flight path and flight schedule, the first device determines that the UE is in a flight state; or if the current time and current location of the UE do not match the flight path and flight schedule, the first device determines that the UE is in a non-flight state.

[0123] In another example, the first device may obtain the status of the UE from the AMF. For example, the first device may receive third instruction information from the AMF, where the third instruction information indicates that the UE is in a flight state. Furthermore, the first device may determine that the UE is in a flight state based on the third instruction information. For example, the AMF may actively push the status of the UE to the first device, or the AMF may send the status of the UE to the first device after receiving a message (e.g., shown as a sixth message) sent by the first device used to subscribe to (or request) the status of the UE. This is not limited to this embodiment of the present application.

[0124] S402: The first device restricts a non-unmanned aerial vehicle service of the UE and / or restricts a first control plane procedure of the UE.

[0125] At S402, the first device restricts the non-unmanned aerial vehicle services of the UE, or restricts a first control plane procedure of the UE, or restricts the non-unmanned aerial vehicle services of the UE and restricts a first control plane procedure of the UE. For example, the first device may restrict the non-unmanned aerial vehicle services of the UE in one or more of the following manners:

[0126] Method 1: The first device is SMF1, and the first device releases a session corresponding to the UE's non-unmanned aerial vehicle service managed by SMF1, or prohibits (or denies) the establishment or modification of a session corresponding to the UE's non-unmanned aerial vehicle service, or releases a session corresponding to the UE's non-unmanned aerial vehicle service managed by SMF1 and prohibits the establishment or modification of a session corresponding to the UE's non-unmanned aerial vehicle service.

[0127] For example, the first device may release all sessions corresponding to non-unmanned aerial vehicle services of the UE managed by SMF1, or the first device may release a portion of the sessions corresponding to non-unmanned aerial vehicle services of the UE managed by SMF1. SMF1 may actively trigger a release procedure for the session corresponding to the non-unmanned aerial vehicle service. For example, SMF1 may release an IP address assigned to the session corresponding to the non-unmanned aerial vehicle service or send a session release message to the UPF used to release the session corresponding to the non-unmanned aerial vehicle service, so that the UPF releases resources related to the session corresponding to the non-unmanned aerial vehicle service (e.g., discard remaining data packets corresponding to the session corresponding to the non-unmanned aerial vehicle service and release corresponding tunnel resources and stored contexts). Furthermore, SMF1 notifies the corresponding AMF, so that the AMF releases resources (e.g., session IDs or SMF IDs) related to the session corresponding to the non-unmanned aerial vehicle service and notifies the AN to release AN resources related to the session corresponding to the non-unmanned aerial vehicle service. It should be understood that the specific implementation solution for the SMF to release the session corresponding to the non-unmanned aerial vehicle service is not limited to this embodiment of the present application.

[0128] For example, the first device may determine that N is greater than M and determine to release all or some of the sessions corresponding to the non-unmanned aircraft services of the UE managed by SMF1. N may be the number of sessions corresponding to the non-unmanned aircraft services of the UE managed by SMF1. For example, the first device may determine N based on UE context information stored in the first device, or may obtain N from the UDM, UDR, or AMF. The manner of obtaining N is not limited in this embodiment of the present application. M may be the number of sessions corresponding to the non-unmanned aircraft services that the UE is permitted to establish on SMF1 when executing the unmanned aircraft services. M may be pre-set, configured by the PCF, or obtained from the UDM, UDR, or AMF. The implementation of M is not limited in this embodiment of the present application. Optionally, the first device may determine to release H sessions corresponding to the non-unmanned aircraft services, where H may be a positive integer greater than or equal to (NM).

[0129] In another example, the first device may prohibit the establishment of some or all of the sessions corresponding to the UE's non-unmanned aerial vehicle services (including prohibiting the modification of some of the sessions corresponding to the UE's unmanned aerial vehicle services to sessions corresponding to the non-unmanned aerial vehicle services), or may prohibit the modification of some or all of the sessions corresponding to the UE's non-unmanned aerial vehicle services.

[0130] The first device prohibiting the UE from establishing or modifying a session corresponding to a non-unmanned aerial vehicle service may be understood as the first device rejecting a message from the UE used to request the establishment or modification of a session corresponding to a non-unmanned aerial vehicle service; or the first device rejecting a message from the UE used to request the modification of a session corresponding to a unmanned aerial vehicle service to a session corresponding to a non-unmanned aerial vehicle service; or the first device not responding to or refusing to respond to a message from the AF used to request the establishment or modification of a session corresponding to a unmanned aerial vehicle service to a session corresponding to a non-unmanned aerial vehicle service; or the first device deleting or discarding a message from the UE or the AF used to request the establishment or modification of a session corresponding to a non-unmanned aerial vehicle service; or the first device deleting or discarding a message from the UE or the AF used to request the modification of a session corresponding to a unmanned aerial vehicle service to a session corresponding to a non-unmanned aerial vehicle service; or the like. For example, the first device may receive a message from a UE or an AF used to request the establishment or modification of a session, and determine whether the session the message requests the establishment or modification of belongs to a session corresponding to an unmanned aerial vehicle service, but the embodiments of the present application are not limited thereto.If the session requested to be established or modified by the message belongs to a session corresponding to an unmanned aircraft service (it should be noted that, according to the above understanding, modifying a session corresponding to an unmanned aircraft service in this application further includes modifying a session corresponding to a non-unmanned aircraft service to a session corresponding to an unmanned aircraft service, and a repeated explanation will not be provided below), the first device continues to perform a session establishment or modification procedure based on the message. If the session requested to be established or modified by the message belongs to a session corresponding to a non-unmanned aircraft service (it should be noted that, according to the above understanding, modifying a session corresponding to a non-unmanned aircraft service in this application further includes modifying a session corresponding to an unmanned aircraft service to a session corresponding to a non-unmanned aircraft service, and a repeated explanation will not be provided below), the first device rejects the request or does not respond to the message. For the first device's determination of whether a session belongs to a session corresponding to an unmanned aircraft service, please refer to the relevant content of S401. Details will not be described again here.

[0131] Method 2: The first device is an AMF or another device (e.g., a UDM or a PCF), and the first device triggers or notifies the SMF to release all or part of a session corresponding to a non-unmanned aerial vehicle service of the UE that is managed by the SMF, or prohibits (or denies) the establishment or modification of all or part of a session corresponding to a non-unmanned aerial vehicle service of the UE.

[0132] For example, the first device determines to restrict the non-unmanned aerial vehicle service of the UE, determines an SMF (e.g., SMF1 and / or SMF2) that manages the sessions of the UE, and sends a notification message to the SMF to release all or part of the sessions corresponding to the non-unmanned aerial vehicle service of the UE managed by the SMF. Optionally, the first device determines an SMF that manages the sessions corresponding to the non-unmanned aerial vehicle service of the UE, and sends a notification message to the SMF. For a specific implementation of releasing the sessions corresponding to the non-unmanned aerial vehicle service of the UE, please refer to the related description in Scheme 1 above. Details will not be described in this specification.

[0133] Method 3: The first device is an SMS-SC, and the first device does not send or withholds sending to the UE a message (e.g., denoted as a first message) used to request establishing or modifying a session corresponding to a non-unmanned aerial vehicle service.

[0134] The first message may be, for example, an SMS message. However, the specific implementation form of the first message is not limited to this embodiment of the present application. The first message may be from the AF. For example, the AF may determine that a session corresponding to the UE's non-unmanned aerial vehicle service needs to be established or modified based on application requirements (e.g., actively pushing video or data to the UE), application requirements of the UE, or the like, and generate and send the first message to the SMS-SC (so that, after receiving the first message, the SMS-SC notifies the UE, and the UE sends a request message to establish or modify a session corresponding to the UE's non-unmanned aerial vehicle service). After receiving the first message, the SMS-SC determines that the first condition is met and does not send the first message to the UE or suspends sending the first message.

[0135] Method 4: The first device is a UE, and the first device does not send or suspends sending a first message to the SMF 1. The first message is used to request establishing or modifying a session corresponding to a non-unmanned aerial vehicle service.

[0136] For example, the AF may determine, based on an application requirement (e.g., actively pushing video data or image data to the UE), the UE's application requirement, or the like, that a session corresponding to the UE's non-unmanned aerial vehicle service needs to be established or modified, generate a request message used to trigger the UE to request that a session corresponding to the UE's non-unmanned aerial vehicle service be established or modified, and send the request message to the SMS-SC. After receiving the request message, the SMS-SC forwards the request message to the UE. After receiving the request message, the UE determines that a first condition is met and does not send or postpones sending the first message to the SMF1. In this manner, the first message is used to request that a session corresponding to the non-unmanned aerial vehicle service be established or modified.

[0137] Manner 5: The first device may send second instruction information to the UE. The second instruction information may indicate that establishment of a session corresponding to a non-unmanned aerial vehicle service is prohibited. Thus, based on the second instruction information, the UE may not initiate establishment or modification of a session corresponding to a non-unmanned aerial vehicle service.

[0138] The above describes how the first device restricts the non-unmanned aerial vehicle service of the UE. The following describes how the first device restricts the first control plane procedure of the UE.

[0139] The first control plane procedure is not a procedure specific to unmanned aircraft services. The fact that the first control plane procedure is not a procedure specific to unmanned aircraft services may be understood as meaning that non-execution of the first control plane procedure does not adversely affect the unmanned aircraft services of the UE; or that non-execution of the first control plane procedure does not affect the normal execution of the unmanned aircraft services of the UE; or that the first control plane procedure is not a procedure necessary for the normal execution of the unmanned aircraft services of the UE; or that execution of the first control plane procedure not only affects the unmanned aircraft services of the UE but also affects the non-unmanned aircraft services of the UE; or that execution of the first control plane procedure is not only a procedure necessary for the normal execution of the unmanned aircraft services of the UE but is also a procedure necessary for the normal execution of the non-unmanned aircraft services of the UE; or something similar. This is not limited to this embodiment of the present application.

[0140] For example, the first control plane procedure may include one or more of the following procedures: a primary authentication procedure, a deregistration procedure, a slice authentication procedure, a secondary authentication procedure, or the like, which is not limited to this embodiment of the present application.

[0141] For example, the first device may implement a restriction on the first control plane procedure by suspending or terminating the first control plane procedure. For example, the first device may receive a fourth message from the third device, where the fourth message is used to request performing the first control plane procedure; the first device may determine that the first condition is met and suspend or terminate the first control plane procedure. Optionally, the first device may send a fifth message to the third device, where the fifth message includes a reason for not performing (or not performing) the first control plane procedure. For example, the reason for not performing the first control plane procedure may be that the first condition is met or a timeout occurs. This is not limited to this embodiment of the present application. Optionally, the first device may start a first timer after suspending the first control plane procedure, and determine whether the UE satisfies the first condition while the first timer is running (or when the execution ends). If the first device determines that the UE satisfies the first condition while the first timer is running (or when the timer expires), the first device may terminate the first control plane procedure when the first timer expires. If the first device determines that the UE does not satisfy the first condition while the first timer is running, the first device may perform the first control plane procedure.

[0142] In a possible implementation, in S401, the first condition determined by the first device includes that the UE is authorized for the unmanned aircraft service and / or that the UE is in a flight state. Furthermore, the first device may further receive a second message from the UE and determine whether a first session requested to be established by using the second message belongs to a session corresponding to the unmanned aircraft service. If the first device determines that the first session belongs to a session corresponding to the unmanned aircraft service, the first device may perform the content shown in S402; or, if the first device determines that the first session belongs to a session corresponding to a non-unmanned aircraft service, the first device may not perform the content shown in S402. For the first device's determination of whether the first session belongs to a session corresponding to the unmanned aircraft service, please refer to the relevant content of S401. Details will not be described again here. In this implementation, when the UE is authorized for unmanned aircraft services and / or the UE is in a flight state, if the first session requested to be established by using the second message belongs to a session corresponding to the unmanned aircraft service, it means that the UE executes the unmanned aircraft service. The first device restricts the UE's non-unmanned aircraft services and / or restricts the UE's first control plane procedure, so that the non-unmanned aircraft service can be prevented from occupying resources for the unmanned aircraft service and more available resources can be reserved for the unmanned aircraft service. Alternatively, if the first session requested to be established by using the second message belongs to a session corresponding to the non-unmanned aircraft service, it means that the UE did not execute the unmanned aircraft service. In this case, the first device allows the execution of the non-unmanned aircraft service and allows the execution of the first control plane procedure, so that resource utilization and compatibility can be improved.

[0143] In another possible implementation, the first condition determined by the first device in S401 includes that the UE is authorized for the unmanned aircraft service and / or that the UE is in a flight state. Furthermore, the first device may further receive a second message from the UE and determine whether the first session requested to be established by using the second message belongs to a session corresponding to the unmanned aircraft service. If the first device determines that the first session belongs to a session corresponding to the unmanned aircraft service, the first device may not perform the content shown in S402. In another example, if the first device determines that the first session belongs to a session corresponding to a non-unmanned aircraft service, the first device may reject the request to establish the first session. For information about the first device determining whether the first session belongs to a session corresponding to the unmanned aircraft service, please refer to the relevant content of S401. Details will not be described again here. In this implementation, when the UE is authorized for unmanned aircraft services and / or the UE is in an airborne state, if the first session requested to be established by using the second message belongs to a session corresponding to the unmanned aircraft service, the first device does not perform S402. However, when the first session belongs to a session corresponding to a non-unmanned aircraft service, the first device denies establishment of the session corresponding to the non-unmanned aircraft service. In this manner, existing (or currently executing) non-unmanned aircraft services and the first control plane procedure can be executed when the unmanned aircraft service is executed, thereby improving resource utilization. Additionally, denial of establishment of a new session corresponding to the non-unmanned aircraft service can prevent an attacker from attacking the UE by using a new non-unmanned aircraft service.

[0144] In another possible implementation, in S401, the first condition determined by the first device includes that the UE is authorized for the unmanned aircraft service and / or that the UE is in an airborne state. Furthermore, the first device may further receive a second message from the UE and determine whether the first session requested to be established by using the second message is a first session corresponding to the unmanned aircraft service initiated by the UE. For example, the first device may determine whether the first session is a first session corresponding to the unmanned aircraft service initiated by the UE based on context information of the UE stored in the first device. For example, if the first device stores session information corresponding to the unmanned aircraft service, the first device may determine that the first session is not a first session corresponding to the unmanned aircraft service initiated by the UE; or, if the first device does not store session information corresponding to the unmanned aircraft service, the first device may determine that the first session is a first session corresponding to the unmanned aircraft service initiated by the UE. Optionally, the first device may send a request to the SMF, the UDR, or the UDM to obtain information about whether the UE has established a session corresponding to the unmanned aircraft service. If the UE has established a session corresponding to the unmanned aircraft service, the first session may be determined to be a UE-initiated first session corresponding to the unmanned aircraft service; or if the UE has not established a session corresponding to the unmanned aircraft service, the first session may be determined to be a UE-initiated first session corresponding to the unmanned aircraft service. If the first session is not a UE-initiated first session corresponding to the unmanned aircraft service, it means that the UE's session corresponding to a non-unmanned aircraft service was released before the first device received the first session establishment request (i.e., when the first session corresponding to the unmanned aircraft service was established).In this case, the first device does not need to repeatedly request restricting non-unmanned aircraft services and / or restricting the first control plane procedure, thereby avoiding unnecessary message exchanges and improving resource utilization. Specifically, if the first device determines that the first session is not a first session initiated by the UE corresponding to an unmanned aircraft service, the first device may not perform the content shown in S402; or, if the first device determines that the first session is a first session initiated by the UE corresponding to an unmanned aircraft service, the first device may perform the content shown in S402.

[0145] In a possible implementation, the first device may send a message (e.g., shown as a third message) to the second device used to request (or notify) that the UE's non-unmanned aerial vehicle services be restricted, i.e., to perform the content shown in S403.

[0146] S403: The first device sends a third message to the second device, and the second device receives the third message in response.

[0147] S403 is an optional step. The third message may be used to request (or notify) the UE to restrict non-unmanned aerial vehicle services.

[0148] S404: The second device determines that SMF2 manages a session corresponding to the non-unmanned aerial vehicle service of the UE.

[0149] S404 is an optional step. For example, after receiving the third message, the second device may determine an SMF that manages a session of the UE. Optionally, the second device determines an SMF that manages a session corresponding to a non-unmanned aerial vehicle service of the UE. For example, the second device may determine an SMF that manages a session of the UE or an SMF that manages a session corresponding to a non-unmanned aerial vehicle service of the UE based on stored UE context information and / or UE context information obtained from a UDM, a UDR, or a PCF. For example, the PCF may send a message to the UDM (or UDR) used to request UE session information or SMF-related information; and receive the UE session information (including the SMF-related information) or the SMF-related information from the UDM (or UDR). The UE context information may include information about the association between the UE and the SMF. The information about the association between the UE and the SMF may include an identifier of the SMF that manages a session corresponding to a non-unmanned aerial vehicle service of the UE or an identifier of the SMF that manages a session of the UE. Optionally, the information about the association between the UE and the SMF may further include an identifier of the SMF that manages the session corresponding to the unmanned aerial vehicle service of the UE. In this embodiment of the present application, an example is used in which both SMF1 and SMF2 manage the session of the non-unmanned aerial vehicle service of the UE. In this case, in S404, the second device may determine that SMF2 manages the session corresponding to the non-unmanned aerial vehicle service of the UE.

[0150] S405: The second device sends sixth indication information to the SMF 2. In response, the SMF 2 receives the sixth indication information.

[0151] S405 is an optional step. The sixth instruction information instructs to release a session managed by SMF2 corresponding to the non-unmanned aerial vehicle service of the UE, or to prohibit establishment or modification of a session corresponding to the non-unmanned aerial vehicle service of the UE, or to release a session managed by SMF2 corresponding to the non-unmanned aerial vehicle service of the UE and prohibit establishment or modification of a session corresponding to the non-unmanned aerial vehicle service of the UE. Optionally, the sixth instruction information may instruct to release all or part of the sessions corresponding to the non-unmanned aerial vehicle service of the UE managed by SMF2.

[0152] In S402, the first device determines to release all or some of the sessions corresponding to the non-unmanned aircraft services of the UE managed by SMF1. In another possible implementation, the first device receives first instruction information from the second device and, based on the first instruction information, releases one or more sessions corresponding to the non-unmanned aircraft services of the UE managed by SMF1. The first instruction information may instruct to release one or more sessions corresponding to the non-unmanned aircraft services. For example, after receiving the third message, the second device determines an SMF that manages sessions corresponding to the non-unmanned aircraft services of the UE and determines the number of sessions corresponding to the non-unmanned aircraft services of the UE to be released by the SMF. SMF1 is used as an example. The second device receives N from SMF1 and, based on the number of sessions corresponding to the non-unmanned aircraft services established by the UE, N and M, determines that SMF1 needs to release one or more sessions corresponding to the non-unmanned aircraft services, or determines the number of sessions corresponding to the non-unmanned aircraft services of the UE that need to be (or are to be) released by SMF1.

[0153] In a possible implementation, the first device may discontinue the restriction on non-unmanned aircraft services and / or discontinue the restriction on the first control plane procedure. For example, if the first device determines that the second condition is met, the first device may discontinue the restriction on non-unmanned aircraft services and / or discontinue the restriction on the first control plane procedure. For example, if the first device is an SMF1, the first device determines that the second condition is met, receives a seventh message from the UE, and establishes or modifies a session corresponding to the non-unmanned aircraft service based on the seventh message, where the seventh message is used to request the establishment or modification of a session corresponding to the non-unmanned aircraft service. In another example, the first device is an SMS-SC, the first device determines that the second condition is met, receives an eighth message from the AF, and sends the eighth message to the UE, where the eighth message is used to request the establishment or modification of a session corresponding to the non-unmanned aircraft service. In another example, the first device is a UE, and the first device determines that the second condition is met, receives an eighth message from the SMS-SC, and sends the eighth message to the SMF1, where the eighth message is used to request establishing or modifying a session corresponding to a non-unmanned aerial vehicle service. In another example, the first device determines that the second condition is met, receives a message from a third device (e.g., shown as a fourth message) used to request performing a first control plane procedure, and performs the first control plane procedure.

[0154] The second condition includes one or more of the following conditions: authorization for the unmanned aircraft service is revoked from the UE, the UE is not authorized for the unmanned aircraft service, the UE's unmanned aircraft service is deregistered, the UE releases the last session corresponding to the unmanned aircraft service, or the like. For example, when the USS prepares to revoke authorization for the unmanned aircraft service from the UE, the USS may send a revocation request (through the UAS NF) to the AMF (or SMF), which then performs an authorization revocation procedure for the UE's unmanned aircraft service. The revocation result is sent to the UE through the AMF (or SMF). The AMF and the SMF may mutually subscribe to authorization information, i.e., may receive authorization revocation results from each other. Thus, the first device (e.g., the UE, the SMF, or the AMF) may determine that authorization for the unmanned aircraft service is revoked from the UE. However, embodiments of the present application are not limited thereto. For example, when a UE needs to be deregistered, the AMF receives a deregistration request and performs a deregistration procedure with the UE. Thus, the AMF and the UE may obtain information indicating that the deregistration procedure is completed. In addition, the SMF may obtain the UE's deregistration information through the AMF (the SMF subscribes to a notification service for related information). However, the embodiments of the present application are not limited thereto. For example, the first device is an SMF, and the first device may determine whether the UE releases the last session corresponding to the unmanned aerial vehicle service based on stored UE context information. In another example, the first device is not an SMF, and the first device may know from the SMF whether the UE releases the last session corresponding to the unmanned aerial vehicle service.

[0155] In S401, the AMF may maintain the status of the UE. Referring to Figure 5, the following describes an implementation in which the AMF obtains the status of the UE.

[0156] 5 is a schematic flowchart of a communication method according to an embodiment of the present application. In this embodiment, the first device is an AMF, and the fourth device is a RAN or a UE or a USS or a UAS NF / NEF. The AMF may obtain the status of the UE in one or more of four manners shown in FIG. 5. Scheme 1 includes steps S501 to S503, Scheme 2 includes S504 and S505, Scheme 3 includes steps S506 to S508, and Scheme 4 includes steps S509 to S511. As shown in FIG. 5, the method may further include the following steps:

[0157] S501: The AMF sends a 9th message to the RAN, and correspondingly, the RAN receives the 9th message from the AMF.

[0158] S501 is an optional step. For example, the AMF may send a ninth message to the RAN to obtain the status of the UE; or the RAN may actively report the status of the UE to the AMF. This is not limited to this embodiment of the present application.

[0159] S502: The RAN determines the status of the UE based on the mobility information of the UE.

[0160] The mobility information includes one or more of height, movement speed, location, and movement trajectory. For example, the RAN may measure the UE to obtain the mobility information of the UE. In another example, the RAN may receive the mobility information from the UE. It should be understood that a specific implementation in which the RAN obtains the mobility information is not limited to this embodiment of the present application. Furthermore, the RAN may determine whether the UE is in an airborne state or a non-airborne state based on the mobility information of the UE. For example, if the height is greater than or equal to a height threshold, the RAN may determine that the UE is in an airborne state. The height threshold may be preset. This is not limited to this embodiment of the present application. In another example, if the movement speed is greater than or equal to a speed threshold, the RAN may determine that the UE is in an airborne state. The speed threshold may be preset. This is not limited to this embodiment of the present application.

[0161] S503: The RAN sends fourth instruction information to the AMF, and correspondingly, the AMF receives fourth instruction information from the RAN.

[0162] The fourth indication information may indicate that the UE is in a flight state or may indicate that the UE is in a non-flight state. The RAN may send the fourth indication information to the AMF to indicate the status of the UE. For ease of understanding, FIG. 5 uses an example in which the fourth indication information indicates that the UE is in a flight state.

[0163] In this way, the AMF completes obtaining the status of the UE in Scheme 1. The following describes how the AMF obtains the status of the UE in Scheme 2.

[0164] S504: The UE determines the status of the UE based on the mobility information and / or the fifth indication information.

[0165] For example, the UE may measure one or more of the UE's height, moving speed, location, or moving trajectory, or may measure radio signals received from the RAN to calculate the UE's mobility information. For an explanation of the mobility information and the UE's determining the UE's status based on the mobility information, please refer to the description of S502. Details will not be repeated here. The fifth instruction information may be from an application layer of the UE. For example, the application layer may trigger the UE to enter flight mode. The application layer may generate the fifth instruction information, which instructs the UE to enter flight mode. Furthermore, the UE determines that the UE is in flight based on the fifth instruction information.

[0166] S505: The UE sends fourth instruction information to the AMF, and correspondingly, the AMF receives fourth instruction information from the UE.

[0167] For the specific implementation process of S505, please refer to S503, and the details will not be repeated here.

[0168] In this way, the AMF completes obtaining the UE status in Scheme 2. The following describes how the AMF obtains the UE status in Scheme 3.

[0169] S506: The AMF obtains the mobility information of the UE.

[0170] For example, the AMF may acquire the mobility information of the UE from the RAN and / or the GMLC (or the LMF). For example, the RAN may actively report the mobility information of the UE to the AMF; or the RAN may send the mobility information of the UE to the AMF after receiving a message from the AMF used to request to acquire the mobility information of the UE. In another example, the GMLC (or the LMF) may actively push the mobility information of the UE to the AMF; or the GMLC (or the LMF) may send the mobility information of the UE to the AMF after receiving a message from the AMF used to request to acquire the mobility information of the UE. It should be understood that the specific implementation in which the AMF acquires the mobility information of the UE is not limited to this embodiment of the present application.

[0171] S507: AMF acquires UE flight information.

[0172] The flight information may include, for example, a flight route and / or a flight time. For example, the AMF may obtain the UE's flight information from the UAS NF / NEF (or USS). For example, the UAS NF / NEF (or USS) may actively push the UE's flight information to the AMF; or the UAS NF / NEF (or USS) may send the UE's flight information to the AMF after receiving a message from the AMF used to request the UE's flight information. The specific implementation in which the AMF obtains the UE's flight information is not limited to this embodiment of the present application.

[0173] S508: The AMF determines the status of the UE based on the mobility information and flight information.

[0174] For example, the AMF may determine whether the current time and current location of the UE match the flight route and flight schedule. If the current time and current location of the UE match the flight route and flight schedule, the AMF determines that the UE is in a flight state; or if the current time and current location of the UE do not match the flight route and flight schedule, the AMF determines that the UE is in a non-flight state. In another example, the AMF may determine the status of the UE based on mobility information. For example, if the height is greater than or equal to a height threshold, the AMF may determine that the UE is in a flight state; or if the moving speed is greater than or equal to a speed threshold, the AMF may determine that the UE is in a flight state. In another example, the AMF may send a request message to another device (e.g., a network data analytics function (NWDAF) device) to obtain the status of the UE. The NWDAF may determine the status of the UE based on collected UE-related information (such as mobility information and / or flight information) and send the status of the UE to the AMF. Optionally, the AMF may send the mobility information and / or flight information acquired by the AMF to the NWDAF. The NWDAF determines the status of the UE based on the received mobility information and / or flight information, and sends the status of the UE to the AMF. In Figure 5, an example is used in which the AMF determines the status of the UE based on the mobility information and flight information.

[0175] In this way, the AMF completes the acquisition of the UE status in scheme 3. The following describes how the AMF acquires the UE status in scheme 4.

[0176] S509: The AMF sends the 9th message to the UAS NF / NEF, and correspondingly, the UAS NF / NEF receives the 9th message from the AMF.

[0177] S509 is an optional step. For example, the AMF may send the ninth message to the UAS NF / NEF (or USS) to obtain the status of the UE; or the UAS NF / NEF (or USS) may actively push the status of the UE to the AMF. This is not limited to this embodiment of the present application.

[0178] Note that the portions performed by the UAS NF / NEF may alternatively be performed by the USS.

[0179] S510: The UAS NF / NEF determines the status of the UE.

[0180] For example, the UAS NF / NEF may obtain the UE's status stored locally, or the UAS NF / NEF may obtain the UE's status from the USS, e.g., by sending a request message to the USS to obtain the UE's status. The USS may obtain the UE's status based on the content of communications between the USS and the UE, or the USS may determine the UE's status based on the UE's flight authorization information, flight schedule, or the like. For example, there may be a dedicated communication channel (e.g., C2 communications) between the USS and a UE used as an unmanned aerial vehicle, and the USS may obtain the UE's status based on the content of communications on the communication channel. In another example, the USS may determine the UE's status based on stored information, such as the UE's flight authorization information and / or flight schedule.

[0181] S511: The UAS NF / NEF sends fourth instruction information to the AMF, and correspondingly, the AMF receives fourth instruction information from the UAS NF / NEF.

[0182] For the specific implementation process of S511, please refer to S503, and the details will not be repeated here.

[0183] In this way, the AMF completes the acquisition of the UE status in method 4.

[0184] In the procedure shown in Figure 5, the AMF may determine the status of the UE based on the mobility information and flight information, or may obtain the status of the UE from the RAN, UE, UAS NF / NEF, or USS. The implementation is flexible and has strong adaptability. Furthermore, the AMF may maintain (or store) the status of the UE and send the status of the UE to another device (such as the SMF, SMS-SC, UDM, AUSF, ARPF, or NSSAAF) so that the other device can determine whether the UE is in a flight state.

[0185] Figure 5 shows that the AMF acquires the status of the UE in multiple ways. The procedure shown in Figure 4 will be described below with reference to Figures 6 to 13.

[0186] 6 is another schematic flowchart of a communication method according to an embodiment of the present application. In this embodiment, the first device is an SMF1, and the SMF1 releases all sessions corresponding to non-unmanned aerial vehicle services of the UE managed by the SMF1. The second device is a PCF, a UDM, a UDR, or an AMF. As shown in FIG. 6, the method may include the following steps:

[0187] S601: The UE sends a second message to SMF1, and correspondingly, SMF1 receives a second message from the UE.

[0188] S601 is an optional step. Specifically, the SMF1 may determine whether the first condition is met in response to the second message, or the SMF1 may periodically or aperiodically determine whether the first condition is met. This is not limited in this embodiment of the present application. The second message is used to request establishing the first session, and the second message may be, for example, a PDU session establishment request message. Alternatively, the second message may be used to request modifying the first session, and the second message may be, for example, a PDU session modification request message. The name of the second message is not limited in this embodiment of the present application.

[0189] S602: SMF1 determines that the first condition is met.

[0190] The first condition includes one or more of the following conditions: the UE is authorized for the unmanned aircraft service, the UE initiates establishment of a first session corresponding to the unmanned aircraft service, or the UE is in a flight state. In S602, the SMF1 may determine whether the first condition is met. For example, the SMF1 may determine whether the UE is authorized for the unmanned aircraft service based on stored UE context information. For example, the SMF1 may recognize from the AMF whether the UE is authorized for the unmanned aircraft service (when the AMF's service for the UE's unmanned aircraft authorization status is subscribed and the unmanned aircraft is authorized, the AMF may notify the SMF1; or the SMF1 sends a request message to the AMF to obtain the UE's unmanned aircraft service authorization status). In another example, the SMF1 may determine whether the first session is a first session corresponding to the unmanned aircraft service initiated by the UE for establishment based on the UE's context information. In another example, the SMF1 may obtain the status of the UE from the AMF and determine whether the UE is in a flight state based on the status of the UE. For the specific implementation process of S602, please refer to the relevant content of S401. The details will not be described again here. In Figure 6, an example in which the SMF1 satisfies the first condition is used.

[0191] S603: SMF1 determines that the first session belongs to a session corresponding to an unmanned aerial vehicle service, and determines that the first session is the first session corresponding to the unmanned aerial vehicle service of the UE.

[0192] S603 is an optional step. For example, the first condition determined by SMF1 in S602 includes that the UE is authorized for the unmanned aerial vehicle service and / or that the UE is in a flight state. After executing S602, SMF1 may execute S603, or may not execute S603. In another example, if the first condition determined by SMF1 in S602 includes that the UE initiates establishment of a first session corresponding to the unmanned aerial vehicle service, S603 and S602 may be understood as one step, and SMF1 does not need to execute S603.

[0193] In the example, the second message is used to request creation of a first session. The SMF1 determines that the first session belongs to a session corresponding to an unmanned aircraft service and determines whether the first session is a first session corresponding to an unmanned aircraft service. If the first session is a first session corresponding to an unmanned aircraft service, the SMF1 may perform the contents shown in S604 to S609; or if the first session is not a first session corresponding to an unmanned aircraft service, the SMF1 does not perform the contents shown in S604 to S609.

[0194] In another example, the second message is used to request modifying the first session. The SMF1 may determine that the first session belongs to a session corresponding to a non-unmanned aircraft service, and determine whether the modified first session is a first session corresponding to an unmanned aircraft service. If the modified first session is a first session corresponding to an unmanned aircraft service, the SMF1 performs steps S604 to S609; or if the modified first session is not a first session corresponding to an unmanned aircraft service, the SMF1 does not perform steps S604 to S609.

[0195] In another example, the second message is used to request modifying the first session. The SMF1 determines that the first session belongs to a session corresponding to an unmanned aircraft service. Furthermore, the SMF1 may further determine whether the second message requests modifying the session corresponding to the unmanned aircraft service to a session corresponding to a non-unmanned aircraft service. If the second message requests modifying the session corresponding to the unmanned aircraft service to a session corresponding to a non-unmanned aircraft service, the SMF1 performs the contents shown in S604 to S609; or if the second message does not request modifying the session corresponding to the unmanned aircraft service to a session corresponding to a non-unmanned aircraft service, the SMF1 does not perform the contents shown in S604 to S609.

[0196] For the specific implementation process of S603, please refer to the relevant content of S401. The details will not be described again here. In addition, in FIG. 6, an example is used in which the first session belongs to a session corresponding to an unmanned aerial vehicle service, and the first session is the first session corresponding to an unmanned aerial vehicle service.

[0197] S604: SMF1 releases sessions corresponding to non-unmanned aerial vehicle services of the UE managed by SMF1 and / or prohibits the establishment or modification of sessions corresponding to non-unmanned aerial vehicle services.

[0198] In this embodiment, SMF1 may release all sessions corresponding to non-unmanned aerial vehicle services of the UE managed by SMF1, or prohibit the establishment or modification of corresponding sessions of non-unmanned aerial vehicle services, or release all sessions corresponding to non-unmanned aerial vehicle services of the UE managed by SMF1 and prohibit the establishment or modification of sessions corresponding to non-unmanned aerial vehicle services. For example, SMF1 may initiate a session release procedure and notify associated NFs, network elements (such as UPF, AMF, or RAN), the UE, and the like to release resources related to the session.

[0199] Optionally, SMF1 may configure a policy for prohibiting the establishment or modification of a session corresponding to a non-unmanned aerial vehicle service. When SMF1 receives a request message from a UE used to establish or modify a session, SMF1 may determine whether the session belongs to a session corresponding to a non-unmanned aerial vehicle service. If the session belongs to a session corresponding to an unmanned aerial vehicle service, SMF1 establishes or modifies the session; or, if the session belongs to a session corresponding to a non-unmanned aerial vehicle service, SMF1 may suspend or terminate the establishment or modification of the session. Optionally, if SMF1 determines that the second condition is met after suspending the establishment or modification of the session, SMF1 continues to establish or modify the session.

[0200] In step S603, if it is determined that the first session belongs to a session corresponding to a non-unmanned aircraft service, the SMF1 may reject the request to establish the first session or the request to modify the first session. Optionally, if the second message is a request to modify the first session to a session corresponding to an unmanned aircraft service, the SMF1 may not reject the request. The SMF1 determines whether the first session is a first session corresponding to an unmanned aircraft service. If the first session is a first session corresponding to an unmanned aircraft service, the contents shown in S605 to S609 may be executed; or if the first session is not a first session corresponding to an unmanned aircraft service, the contents shown in S605 to S609 are not executed.

[0201] In step S603, if it is determined that the first session belongs to a session corresponding to an unmanned aerial vehicle service and that the second message is used to request creating the first session, SMF1 determines whether the first session is a first session corresponding to an unmanned aerial vehicle service. If the first session is a first session corresponding to an unmanned aerial vehicle service, the contents shown in S605 to S609 may be executed; or if the first session is not a first session corresponding to an unmanned aerial vehicle service, the contents shown in S605 to S609 are not executed.

[0202] In step S603, if it is determined that the first session belongs to a session corresponding to an unmanned aerial vehicle service and that the second message is used to request modifying the first session, SMF1 determines whether the request is to modify the session corresponding to the unmanned aerial vehicle service to a session corresponding to a non-unmanned aerial vehicle service. If the request is to modify the session corresponding to the unmanned aerial vehicle service to a session corresponding to a non-unmanned aerial vehicle service, SMF1 may reject the request; or if the request is not to modify the session corresponding to the unmanned aerial vehicle service to a session corresponding to a non-unmanned aerial vehicle service, SMF1 may perform the contents shown in S605 to S609.

[0203] S605: SMF1 sends second indication information to the UE, and correspondingly, the UE receives second indication information from SMF1.

[0204] S605 is an optional step. The SMF1 may send second instruction information to the UE, where the second instruction information may indicate that the UE is prohibited from establishing a session corresponding to a non-unmanned aircraft service, or may indicate that the UE is prohibited from establishing a session corresponding to a non-unmanned aircraft service on the SMF1. After receiving the second instruction information, before initiating session establishment, the UE may first determine whether the session belongs to a session corresponding to an unmanned aircraft service. If the session belongs to a session corresponding to an unmanned aircraft service, the UE may initiate a procedure for establishing the session; or, if the session belongs to a session corresponding to a non-unmanned aircraft service, the UE may refrain from initiating the procedure for establishing the session. For example, if the UE receives instruction information from the SMF1 indicating that establishment of a session corresponding to a non-unmanned aircraft service is permitted, the UE may initiate a procedure for establishing the session. For the UE's determination of whether a session belongs to a session corresponding to an unmanned aircraft service, please refer to the relevant content of the SMF1's determination of whether a first session belongs to a session corresponding to an unmanned aircraft service. Details will not be repeated here.

[0205] The second instruction information sent by the SMF1 may further indicate that modifying the session corresponding to the unmanned aircraft service to a session corresponding to a non-unmanned aircraft service is prohibited. Thus, after receiving the second instruction information, before initiating the session modification procedure, the UE may first determine whether the session modification request is to modify the session corresponding to the unmanned aircraft service to a session corresponding to a non-unmanned aircraft service. If the session modification request is not to modify the session corresponding to the unmanned aircraft service to a session corresponding to a non-unmanned aircraft service, the UE may initiate the session modification procedure; or, if the session modification request is to modify the session corresponding to the unmanned aircraft service to a session corresponding to a non-unmanned aircraft service, the UE may refrain from initiating the session modification procedure. For example, if the UE receives instruction information from the SMF1 indicating that establishment of a session corresponding to a non-unmanned aircraft service is permitted, the UE may initiate the session modification procedure. For the UE's determination of whether a session belongs to a session corresponding to an unmanned aircraft service, please refer to the relevant content of the SMF1's determination of whether a first session belongs to a session corresponding to an unmanned aircraft service. Details will not be described again here.

[0206] In this way, SMF1 completes the restriction on non-unmanned aerial vehicle services. Optionally, SMF1 may further execute the contents shown in S606.

[0207] S606: SMF1 sends a third message to PCF, and correspondingly, PCF receives a third message from SMF1.

[0208] The third message may be used to request or notify the UE to restrict a session corresponding to a non-unmanned aerial vehicle service. Note that in this embodiment, the steps performed by the PCF may alternatively be performed by a UDM, a UDR, or an AMF.

[0209] S607: The PCF determines that the SMF2 manages the session corresponding to the non-unmanned aerial vehicle service of the UE.

[0210] After receiving the third message, the PCF may determine an SMF that manages a session corresponding to the non-unmanned aerial vehicle service of the UE, or the PCF determines an SMF that manages a session of the UE (FIG. 6 takes an example in which the PCF determines that SMF2 manages a session corresponding to the non-unmanned aerial vehicle service of the UE). For example, the PCF may determine an SMF that manages a session corresponding to the non-unmanned aerial vehicle service of the UE based on context information of the UE and / or information about the association between the UE and the SMF obtained from the UDM or UDR. Optionally, the PCF may determine an SMF that manages a session of the UE based on context information of the UE and / or information about the association between the UE and the SMF obtained from the UDM or UDR. It should be noted that if the PCF determines that SMF2 manages the session of the UE but does not determine whether SMF2 manages the session corresponding to the non-unmanned aerial vehicle service of the UE, SMF2 may determine in step S609 whether SMF2 manages the session corresponding to the non-unmanned aerial vehicle service of the UE and perform corresponding operations.

[0211] For the specific implementation process of S607, please refer to S404, and the details will not be repeated here.

[0212] S608: The PCF sends sixth indication information to the SMF2, and correspondingly, the SMF2 receives sixth indication information from the PCF.

[0213] In this embodiment, the sixth instruction information may instruct (or notify) the release of all sessions corresponding to non-unmanned aircraft services of the UE managed by SMF2, or may instruct the prohibition of establishment or modification of sessions corresponding to non-unmanned aircraft services, or may instruct the release of all sessions corresponding to non-unmanned aircraft services of the UE managed by SMF2 and the prohibition of establishment or modification of sessions corresponding to non-unmanned aircraft services.

[0214] S609: SMF2 releases sessions corresponding to non-unmanned aerial vehicle services of the UE managed by SMF2 and / or prohibits the establishment or modification of sessions corresponding to non-unmanned aerial vehicle services.

[0215] Based on the sixth instruction information, the SMF2 may release all sessions corresponding to non-unmanned aerial vehicle services of the UE managed by the SMF2 and / or prohibit the establishment or modification of sessions corresponding to non-unmanned aerial vehicle services. For a specific implementation process, see S604. Details will not be described again here. Optionally, the SMF2 may send instruction information to the UE indicating that the establishment of sessions corresponding to non-unmanned aerial vehicle services is prohibited (or prohibited on the SMF2).

[0216] 7 is another schematic flowchart of a communication method according to an embodiment of the present application. In this embodiment, the first device is an SMF1, and the SMF1 releases a part of a session corresponding to a non-unmanned aerial vehicle service of the UE managed by the SMF1. The second device is a PCF, a UDM, a UDR, or an AMF. As shown in FIG. 6, the method may include the following steps:

[0217] S701 to S703, S706, S707, and S711 in Fig. 7 are respectively the same as S601 to S603, S606, S607, and S605 in Fig. 6. The differences are as follows.

[0218] S704: SMF1 determines that N is greater than M.

[0219] S704 is an optional step. For example, the SMF1 may determine the number of sessions to be released corresponding to the non-unmanned aerial vehicle service of the UE based on N and M, i.e., perform the contents shown in S704 and S705. Alternatively, the SMF1 may determine the number of sessions to be released corresponding to the non-unmanned aerial vehicle service of the UE based on the first instruction information from the PCF, i.e., perform the contents shown in S706, S708, and S709.

[0220] N may be the number of sessions corresponding to non-unmanned aerial vehicle services of the UE managed by SMF1. For example, the first device may determine N based on context information of the UE, or may obtain N from the UDM or UDR. The manner of obtaining N is not limited in this embodiment of the present application. M may be the number of sessions corresponding to non-unmanned aerial vehicle services that the UE is permitted to establish on SMF1 when executing the unmanned aerial vehicle service. M may be pre-configured, configured by the PCF, or obtained from the UDM or UDR. The implementation of M is not limited in this embodiment of the present application.

[0221] In S704, SMF1 may determine whether N is greater than M. If N is less than or equal to M and step S701 is executed, a procedure for establishing or modifying a first session is executed. If N is less than or equal to M and step S701 is not executed, the procedure ends. If N is greater than M, SMF1 executes the contents shown in S705.

[0222] S705: SMF1 determines to release the session of H corresponding to the non-unmanned aerial vehicle service.

[0223] H is a positive integer greater than or equal to (NM). For example, SMF1 may determine to release H sessions corresponding to non-unmanned aircraft services among the N sessions corresponding to non-unmanned aircraft services. For example, SMF1 may randomly select H sessions corresponding to non-unmanned aircraft services from the N sessions corresponding to non-unmanned aircraft services. In another example, SMF1 may select H sessions corresponding to non-unmanned aircraft services based on the priorities of the N sessions corresponding to non-unmanned aircraft services, e.g., H low-priority sessions corresponding to non-unmanned aircraft services among the N sessions corresponding to non-unmanned aircraft services. In another example, SMF1 may select H sessions corresponding to non-unmanned aircraft services, e.g., H sessions corresponding to non-unmanned aircraft services with a relatively long (or relatively short) establishment time, or H sessions corresponding to non-unmanned aircraft services with a relatively large (or relatively small) resource consumption, from the N sessions corresponding to non-unmanned aircraft services based on session establishment times and / or resources consumed by the sessions. It should be understood that the selection of sessions in H corresponding to non-unmanned aerial vehicle services is not limited in this embodiment of the present application.

[0224] S708: The PCF determines that SMF1 releases the session of H corresponding to the non-unmanned aerial vehicle service, and that SMF2 releases the session of Q corresponding to the non-unmanned aerial vehicle service.

[0225] In a possible implementation, SMF1 may send N to the PCF, for example, include N in a third message and send the third message to the PCF. The PCF may determine, based on N and M, that N is greater than M and determine that SMF1 releases the sessions of H corresponding to the UE's non-unmanned aerial vehicle services.

[0226] In another possible implementation, the PCF maintains the number of sessions corresponding to non-unmanned aerial vehicle services established by the UE. For example, the PCF receives N from SMF1 and receives from SMF2 the number of sessions corresponding to the UE's non-unmanned aerial vehicle services managed by SMF2. The PCF may determine whether the SMF releases the sessions corresponding to the UE's non-unmanned aerial vehicle services based on the number of sessions corresponding to the non-unmanned aerial vehicle services established by the UE (e.g., denoted as X, where X is a positive integer) and the number of sessions corresponding to the non-unmanned aerial vehicle services that are allowed to be established when the UE performs the unmanned aerial vehicle service (e.g., denoted as Y, where Y is a positive integer). Y may be predefined. This is not limited to this embodiment of the present application. If X is less than or equal to Y, the PCF may determine that the SMF will not release sessions corresponding to the UE's non-unmanned aerial vehicle services; or if X is greater than Y, the PCF may determine that the SMF will release (XY) or more sessions corresponding to the UE's non-unmanned aerial vehicle services. Further, the PCF may determine that SMF1 will release one or more (e.g., denoted as H) sessions corresponding to the UE's non-unmanned aerial vehicle services managed by SMF1, and that SMF2 will release Q (Q is a positive number) sessions corresponding to the UE's non-unmanned aerial vehicle services managed by SMF2. For example, the PCF may determine that SMF1 will release H sessions corresponding to the UE's non-unmanned aerial vehicle services managed by SMF1 based on X, Y, N, and M.

[0227] It should be noted that the determination by the PCF that SMF2 will release Q sessions corresponding to non-unmanned aerial vehicle services refers to the implementation process of the PCF determining that SMF1 will release H sessions corresponding to non-unmanned aerial vehicle services. Details will not be described again here. In addition, the number of sessions to be released corresponding to non-unmanned aerial vehicle services determined by SMF1 based on N and M may be the same as or different from the number of sessions to be released corresponding to non-unmanned aerial vehicle services determined by the PCF based on N and M or based on X, Y, N, and M. This is not a limitation in this embodiment of the present application.

[0228] It should be noted that the steps performed by the PCF may alternatively be performed by the UDM, UDR, or AMF.

[0229] S709: The PCF sends first indication information to the SMF1, and correspondingly, the SMF1 receives first indication information from the PCF.

[0230] In this embodiment, the first instruction information instructs the UE to release a session of H corresponding to a non-unmanned aerial vehicle service.

[0231] S710: SMF1 releases the session of H corresponding to the non-unmanned aerial vehicle service of the UE managed by SMF1.

[0232] In S710, SMF1 releases a session of H corresponding to a non-unmanned aerial vehicle service of the UE managed by SMF1, and / or prohibits the establishment or modification of a session corresponding to a non-unmanned aerial vehicle service. For a specific implementation process, please refer to the related description of S604. Details will not be described again here. For ease of explanation, FIG. 7 uses an example in which SMF1 releases a session of H corresponding to a non-unmanned aerial vehicle service of the UE managed by SMF1.

[0233] S712: The PCF sends sixth indication information to the SMF2, and correspondingly, the SMF2 receives sixth indication information from the PCF.

[0234] The sixth instruction information may instruct to release a session of Q corresponding to a non-unmanned aerial vehicle service of the UE managed by SMF2 and / or may instruct to prohibit establishment or modification of a session corresponding to a non-unmanned aerial vehicle service. For ease of explanation, an example in Figure 7 is used in which the sixth instruction information instructs to release a session of Q corresponding to a non-unmanned aerial vehicle service of the UE managed by SMF2.

[0235] In S713, SMF2 releases Q's sessions corresponding to non-unmanned aerial vehicle services of the UE managed by SMF2 and / or prohibits the establishment or modification of sessions corresponding to non-unmanned aerial vehicle services.

[0236] In S713, the SMF2 releases the session of Q corresponding to the non-unmanned aerial vehicle service of the UE managed by the SMF2, and / or prohibits the establishment or modification of the session corresponding to the non-unmanned aerial vehicle service. For a specific implementation process, please refer to the related description of S604. The details will not be described again here. For ease of explanation, FIG. 7 uses an example in which the SMF2 releases the session of Q corresponding to the non-unmanned aerial vehicle service of the UE managed by the SMF2.

[0237] 8 is another schematic flowchart of a communication method according to an embodiment of the present application. In this embodiment, the first device is a UE, and the UE does not send or refrains from sending a request to SMF1 to establish or modify a session corresponding to a non-unmanned aerial vehicle service. As shown in FIG. 8, the method may include the following steps:

[0238] S801: The AF sends a tenth message to the SMS-SC. In response, the SMS-SC receives a tenth message from the AF.

[0239] The tenth message is used to trigger the UE to request to establish or modify the second session. The tenth message may be, for example, an SMS message. However, the specific implementation form of the tenth message is not limited to this embodiment of the present application. For example, the AF may determine to trigger the UE to initiate the establishment or modification of the second session, generate the tenth message, and send the tenth message to the SMS-SC. For example, the AF may determine to trigger the UE to initiate a procedure to establish or modify the second session based on an application requirement (e.g., actively pushing video data to the UE), an application requirement of the UE, or the like.

[0240] Optionally, the AF sends the tenth message to the SMS-SC, and the tenth message can reach the SMS-SC through the NEF and UDM. The NEF and UDM can verify the AF and determine that the receiving end device of the tenth message is the SMS-SC. It should be understood that the transmission path of the tenth message is not limited in this embodiment of the present application.

[0241] S802: The SMS-SC sends the 11th message to the UE. In response, the UE receives the 11th message from the SMS-SC.

[0242] After receiving the tenth message, the SMS-SC sends an eleventh message to the UE, where the eleventh message is used to notify the UE to trigger a procedure to establish or modify a second session.

[0243] Optionally, the SMS-SC may send a response message to the AF, where the response message indicates that the eleventh message has been sent to the UE.

[0244] S803: The UE determines that a first condition is met.

[0245] The first condition may include one or more of the following conditions: the UE is authorized for the unmanned aircraft service, the UE initiates establishment of a first session corresponding to the unmanned aircraft service, or the UE is in a flight state. For example, the UE may determine whether the UE is authorized for the unmanned aircraft service based on the stored context information or the unmanned aircraft authorization status. In another example, the UE may determine that the session establishment to be initiated is for the first session corresponding to the unmanned aircraft service based on the stored context information or the session status. In another example, the UE may determine that the UE is in a flight state based on the mobility information and / or the fifth instruction information. For a specific implementation process of S803, please refer to the relevant content of S401. Details will not be described again here.

[0246] S804: The UE determines whether the second session belongs to a session corresponding to a non-unmanned aerial vehicle service.

[0247] S804 is an optional step. For example, after determining that the first condition is met, the UE may not send or refrain from sending the twelfth message to the SMF1, where the twelfth message is used to request the establishment or modification of the second session. In another example, the UE may determine whether the second session belongs to a session corresponding to a non-unmanned aerial vehicle service based on the eleventh message. The eleventh message may include one or more of the following information: UE type indication information, a UAV ID, a DNN, USS address information, a USS ID, an S-NSSAI identifier, an AF ID, a session service type, or the like. For an implementation in which the UE determines whether the second session belongs to a session corresponding to a non-unmanned aerial vehicle service based on the eleventh message, please refer to the related description in S401. Details will not be described again here.

[0248] Optionally, the eleventh message may include a UE identifier (e.g., a generic public subscription identifier (GPSI), a SUPI, or a UAV ID) and / or an AF identifier. The UE may determine a service type of the second session based on the UE identifier and / or the AF identifier. For example, if the UE identifier is a common terminal identifier rather than an unmanned aerial vehicle identifier (e.g., a UAV ID), the UE may determine that the second session belongs to a session corresponding to a non-unmanned aerial vehicle service. In another example, if the AF indicated by the AF identifier is an AF of a non-unmanned aerial vehicle service, or if the AF is not an AF of an unmanned aerial vehicle service (does not belong to a USS), the UE may determine that the second session belongs to a session corresponding to a non-unmanned aerial vehicle service.

[0249] If the UE determines that the second session belongs to a session corresponding to an unmanned aircraft service, the UE performs the content shown in S805; or if the UE determines that the second session belongs to a session corresponding to a non-unmanned aircraft service, the UE performs the content shown in S806. In another optional implementation, if the UE determines that the second session belongs to a session corresponding to an unmanned aircraft service and triggers modifying the session to a session corresponding to a non-unmanned aircraft service, the content shown in S806 is performed; or if the UE determines that the second session belongs to a session corresponding to a non-unmanned aircraft service and triggers modifying the session to a session corresponding to an unmanned aircraft service, the content shown in S805 is performed.

[0250] S805: The UE sends a 12th message to SMF1, and correspondingly, SMF1 receives a 12th message from the UE.

[0251] In S805, the second session belongs to a session corresponding to the unmanned aerial vehicle service, and the UE may trigger modification or establishment of the second session, i.e., trigger modification or establishment of the session corresponding to the unmanned aerial vehicle service. For example, the UE may send a 12th message to SMF1.

[0252] S806: The UE does not send or suspends the transmission of the 12th message to the SMF1.

[0253] In S806, the second session belongs to a session corresponding to a non-unmanned aerial vehicle service, and the UE does not trigger modification or establishment of the second session, i.e., the UE does not trigger modification or establishment of the session corresponding to the non-unmanned aerial vehicle service. For example, the UE does not send or suspends transmission of the 12th message to SMF1. Optionally, when the UE suspends transmission of the 12th message to SMF1, the UE may start a second timer. Furthermore, if the first condition is met during the execution of the second timer (or when the execution ends), the UE does not send the 12th message to SMF1; or, if the second condition is met during the execution of the second timer, the UE sends the 12th message to SMF1. For an explanation of the second condition, please refer to the relevant content of FIG. 4. Details will not be repeated here.

[0254] In the procedure shown in Figure 8, after receiving the 11th message from the AF, which is used to request establishing or modifying the second session by using the SMS-SC, the UE may determine that the first condition is met, and when it determines that the second session belongs to a session corresponding to a non-unmanned aircraft service, the UE does not send or postpones sending the 12th message to the SMF1, thereby avoiding the initiation of the establishment or modification of the session corresponding to the non-unmanned aircraft service, thereby reducing attacks that an attacker may launch against the UE by using the non-unmanned aircraft service, and preventing the non-unmanned aircraft service from occupying the resources of the unmanned aircraft service.

[0255] 9 is another schematic flowchart of a communication method according to an embodiment of the present application. In this embodiment, the first device is an SMS-SC, and the SMS-SC does not send or refrains from sending a request to the UE to establish or modify a session corresponding to a non-unmanned aerial vehicle service. As shown in FIG. 9, the method may include the following steps:

[0256] S901: The AF sends a tenth message to the SMS-SC. In response, the SMS-SC receives a tenth message from the AF.

[0257] For the specific implementation process of S901, please refer to S801, and the details will not be repeated here.

[0258] S902: The SMS-SC determines that the first condition is met.

[0259] The first condition may include one or more of the following conditions: the UE is authorized for the unmanned aircraft service, the UE initiates establishment of a first session corresponding to the unmanned aircraft service, or the UE is in a flight state. For example, the SMS-SC may subscribe to a service from the AMF (or SMF or UAS NF) related to the unmanned aircraft authorization status or flight status of the UE. For example, when the UE is authorized for the unmanned aircraft service, the AMF (or SMF or UAS NF) may notify the SMS-SC that the UE is authorized for the unmanned aircraft service; or the SMS-SC may send a request message to the AMF (or SMF or UAS NF) to obtain the unmanned aircraft authorization status or flight status of the UE. In another example, the SMS-SC may subscribe to a service related to the session status from the AMF (or SMF, UDR, or UDM). For example, when the number of sessions corresponding to the UE's unmanned aircraft service changes, the AMF (or SMF, UDR, or UDM) may notify the SMS-SC of the number of existing sessions corresponding to the UE's unmanned aircraft service, so that the SMS-SC can determine whether the second session is the first session corresponding to the unmanned aircraft service initiated by the UE; or the SMS-SC may send a request message to the AMF (or SMF, UDR, or UDM) to obtain the number of sessions corresponding to the UE's unmanned aircraft service and determine whether the session initiated by the UE (i.e., the second session) is the first session corresponding to the unmanned aircraft service. In another example, the SMS-SC may locally store UE context information, where the UE context information includes the UE's unmanned aircraft authorization status and flight status. In this way, the SMS-SC may determine the UE's unmanned aircraft authorization status or flight status based on the locally stored UE context information. For a specific implementation process of S902, please refer to the relevant content of S401. The details will not be explained again here.

[0260] S903: The SMS-SC determines whether the second session belongs to a session corresponding to a non-unmanned aerial vehicle service.

[0261] S903 is an optional step. For example, after determining that the first condition is met, the SMS-SC may not send or suspend sending the eleventh message to the UE. The eleventh message is used to trigger the UE to request the establishment or modification of the second session. In another example, the SMS-SC may determine whether the second session belongs to a session corresponding to a non-unmanned aerial vehicle service based on the tenth message. The tenth message may include one or more of the following information: UE type indication information, a UAV ID, a DNN, USS address information, a USS ID, an S-NSSAI identifier, an AF ID, a session service type, or the like. For an implementation in which the SMS-SC determines whether the second session belongs to a session corresponding to a non-unmanned aerial vehicle service based on the tenth message, please refer to the related description in S401. Details will not be described again here.

[0262] Optionally, when the tenth message is used to modify the second session, the SMS-SC may send a message to another device (e.g., SMF, UDM, or UDR) used to request whether the second session belongs to a session corresponding to a non-unmanned aerial vehicle service (i.e., to recognize from the other device whether the second session belongs to a session corresponding to a non-unmanned aerial vehicle service).

[0263] Optionally, the tenth message may include a UE identifier (e.g., a generic public subscription identifier (GPSI), a SUPI, or a UAV ID) and / or an AF identifier. The SMS-SC may determine a service type of the second session based on the UE identifier and / or the AF identifier. For example, if the UE identifier is a common terminal identifier rather than an unmanned aerial vehicle identifier (e.g., a UAV ID), the UE may determine that the second session belongs to a session corresponding to a non-unmanned aerial vehicle service. In another example, if the AF indicated by the AF identifier is an AF for a non-unmanned aerial vehicle service, or if the AF is not an AF for a unmanned aerial vehicle service (does not belong to a USS), the UE may determine that the second session belongs to a session corresponding to a non-unmanned aerial vehicle service.

[0264] If the SMS-SC determines that the second session belongs to a session corresponding to an unmanned aircraft service, the SMS-SC performs steps S904 and S905; or if the SMS-SC determines that the second session belongs to a session corresponding to a non-unmanned aircraft service, the SMS-SC performs step S906. In another optional implementation, if the SMS-SC determines that the second session belongs to a session corresponding to an unmanned aircraft service and triggers modification of the session to a session corresponding to a non-unmanned aircraft service, the SMS-SC performs steps S906; or if the SMS-SC determines that the second session belongs to a session corresponding to a non-unmanned aircraft service and triggers modification of the session to a session corresponding to an unmanned aircraft service, the SMS-SC performs steps S904 and S905.

[0265] S904: The SMS-SC sends an eleventh message to the UE, and correspondingly, the UE receives the eleventh message from the SMS-SC.

[0266] At S904, the second session may belong to or be modified to a session corresponding to an unmanned aerial vehicle service, and the SMS-SC may send an eleventh message to the UE.

[0267] S905: The UE sends a 12th message to SMF1, and correspondingly, SMF1 receives a 12th message from the UE.

[0268] After receiving the 11th message, the UE triggers modification or establishment of a session corresponding to the unmanned aerial vehicle service and sends a 12th message to the SMF1. The 12th message is used to request establishment or modification of a second session.

[0269] S906: The SMS-SC does not send or suspends the sending of the 11th message to the UE.

[0270] In S906, the second session belongs to a session corresponding to a non-unmanned aerial vehicle service, and the SMS-SC does not send or suspends the transmission of the eleventh message to the UE. Optionally, when the SMS-SC suspends the transmission of the eleventh message to the UE, the SMS-SC may start a second timer. Furthermore, if the first condition is met while the second timer is running (or when the execution ends), the SMS-SC does not send the eleventh message to the UE; or, if the second condition is met while the second timer is running, the SMS-SC sends the eleventh message to the UE. For an explanation of the second condition, please refer to the relevant content of FIG. 4. Details will not be repeated here.

[0271] In the procedure shown in Figure 9, after receiving the tenth message from the AF, which is used to request the establishment or modification of the second session, the SMS-SC may determine that the first condition is met, and when it determines that the second session belongs to a session corresponding to a non-unmanned aircraft service, the SMS-SC does not send or postpones sending the eleventh message to the UE, thereby preventing the establishment or modification of the session corresponding to the non-unmanned aircraft service, thereby reducing attacks that an attacker may launch against the UE by using the non-unmanned aircraft service, and preventing the non-unmanned aircraft service from occupying the resources of the unmanned aircraft service.

[0272] FIG. 10 is another schematic flowchart of a communication method according to an embodiment of the present application. In this embodiment, the first control plane procedure is a primary authentication procedure. The primary authentication procedure may be initiated by the SEAF, AMF, or UDM. In addition, in this embodiment, the first device may be the SEAF or AMF, or the first device may be the UDM, AUSF, or ARPF. In addition, when the first device is the UDM, AUSF, or ARPF, the third device may be the SEAF or AMF. As shown in FIG. 10, the method includes two implementations. One implementation includes the contents shown in steps S1002 to S1004, and the other implementation includes the contents shown in steps S1005 to S1009.

[0273] S1001: The SEAF determines to start the primary authentication procedure.

[0274] S1001 is an optional step. The SEAF may initiate a primary authentication procedure for the UE. For example, when the UE registers with the network for the first time or when the SEAF does not store the security context of the UE, the SEAF may initiate the primary authentication procedure for the UE. In another example, the SEAF may periodically or aperiodically initiate the primary authentication procedure for the UE based on the network configuration. It should be understood that the reason and time for initiating the primary authentication procedure by the SEAF are not limited to this embodiment of the present application.

[0275] It should be noted that in this embodiment, the steps performed by the SEAF may alternatively be performed by the AMF.

[0276] Before the SEAF starts the primary authentication procedure, the SEAF may execute the contents shown in S1002 to S1004, or may execute the contents shown in S1005.

[0277] S1002: The SEAF determines that the UE is in flight.

[0278] The SEAF may determine the status of the UE by using the AMF. In some implementations, the SEAF and the AMF are combined in the same network function, and the AMF stores the status of the UE. In this way, the SEAF may retrieve the status of the UE. In another implementation, the SEAF and the AMF are independent network functions, and the SEAF may obtain the status of the UE from the AMF. For example, the SEAF may send a message to the AMF to request the status of the UE. After receiving the message, the AMF sends indication information to the SEAF indicating whether the UE is in an airborne state or a non-airborne state. In another example, the SEAF may subscribe to the status of the UE from the AMF. When the status of the UE is updated (e.g., when the UE switches from an airborne state to a non-airborne state, or when the UE switches from a non-airborne state to an airborne state), the AMF may push the status of the UE to the SEAF. For information about obtaining the status of the UE by the AMF, please refer to the related content in Figure 5. Details will not be described again here. If the SEAF determines that the UE is in a flight state, the SEAF performs the content shown in S1003. If the SEAF determines that the UE is in a non-flight state, the SEAF performs a primary authentication procedure, for example, sends a message to the UDM (or AUSF or ARPF) that is used to request (or notify) that the primary authentication procedure be performed. In Figure 10, an example is used in which the SEAF determines that the UE is in a flight state.

[0279] It should be understood that in Figure 10, the SEAF is determined to be in flight state is used as an example. In another possible implementation, S1002 can be replaced with the SEAF being determined to be in flight state when the first condition is met. For a specific implementation process, please refer to S401. The details will not be described again here.

[0280] S1003: The SEAF suspends or terminates the primary authentication procedure.

[0281] The SEAF may suspend or terminate the primary authentication procedure when it determines that the UE is in flight.

[0282] S1004: If the UE is in flight while the first timer is running (or when the execution ends), the SEAF terminates the primary authentication procedure.

[0283] S1004 is an optional step. For example, the SEAF may suspend the primary authentication procedure, start a first timer, and determine the status of the UE while the first timer is running. For example, the SEAF obtains the status of the UE from the AMF while the timer is running. For specific implementation, refer to the content in S1002. Details will not be described again here. If the SEAF recognizes from the AMF that the UE is in a non-flight state while the first timer is running, the SEAF may terminate the first timer and prepare to start the primary authentication procedure, for example, send a message to the UDM (or AUSF or ARPF) used to request (or notify) the primary authentication procedure. If the UE is in a flight state while the first timer is running (or when the execution ends) (for example, the SEAF does not receive information indicating that the UE is in a non-flight state from the AMF while the first timer is running), the SEAF may terminate the primary authentication procedure, for example, when the execution of the first timer ends. FIG. 10 shows an example in which the UE is in flight while the first timer is running.

[0284] S1005: The SEAF sends a fourth message to the UDM, and correspondingly, the UDM receives a fourth message from the SEAF.

[0285] In this embodiment, the fourth message may be, for example, an authentication request message. However, the name of the fourth message is not limited in this embodiment of the present application. The fourth message may be used to request (or notify) that a primary authentication procedure is to be performed.

[0286] It should be noted that in this embodiment, the steps performed by the UDM may alternatively be performed by the AUSF or the ARPF.

[0287] S1006: The UDM determines that the UE is in flight.

[0288] The UDM may determine the status of the UE. For example, the UDM may obtain the status of the UE from the AMF. For specific implementation, please refer to the description of the SEAF obtaining the status of the UE from the AMF. Details will not be described again here. If the UDM determines that the UE is in a flight state, the content shown in S1007 is executed. If the UDM determines that the UE is in a non-flight state, a primary authentication procedure is executed, for example, an authentication vector of the UE is generated based on the fourth message, and step S1009 is executed. In Figure 10, an example is used in which the UDM determines that the UE is in a flight state.

[0289] It should be understood that in Figure 10, the UDM is determined to be in flight as an example. In another possible implementation, S1006 can be replaced with the UDM being determined to be in flight as a first condition is met. For a specific implementation process, please refer to S401. The details will not be described again here.

[0290] S1007: The UDM suspends or terminates the primary authentication procedure.

[0291] When determining that the UE is in flight, the UDM may suspend or terminate the primary authentication procedure.

[0292] S1008: If the UE is in a flight state while the first timer is running, the UDM terminates the primary authentication procedure.

[0293] S1008 is an optional step. For example, the UDM may suspend the primary authentication procedure, start a first timer, and determine the status of the UE while the first timer is running. For a specific implementation process, please refer to the relevant content in S1004. Details will not be described again here. If the UDM recognizes from the AMF that the UE is in a non-flight state while the first timer is running (or when it ends), the UDM may terminate the first timer and perform the primary authentication procedure. If the UE is in a flight state while the first timer is running (or when it ends), for example, the UDM does not receive information from the AMF indicating that the UE is in a non-flight state while the first timer is running), the UDM may terminate the primary authentication procedure, for example, when the first timer ends. Figure 10 shows an example in which the UE is in a flight state while the first timer is running.

[0294] It should be noted that the timer started by the SEAF in S1004 may be the same as or different from the timer started by the UDM in S1008, which is not limited in this embodiment of the present application.

[0295] S1009: The UDM sends a fifth message to the SEAF, and correspondingly, the SEAF receives a fifth message from the UDM.

[0296] In this embodiment, the fifth message may be, for example, an authentication response message. However, the name of the fifth message is not limited in this embodiment of the present application. When a primary authentication procedure is performed, the fifth message may include the authentication vector in step S1006. When a primary authentication procedure is not performed, the fifth message may indicate that the primary authentication procedure is not performed. Optionally, the fifth message may include a reason for not performing the primary authentication procedure. For example, the reason for not performing the primary authentication procedure may be a timeout and / or the UE being in a flight state.

[0297] In the procedure shown in Figure 10, before performing (or starting) the primary authentication procedure for the UE, the first device may determine the status of the UE, and when determining that the UE is in a flight state, may suspend or terminate the primary authentication procedure for the UE. This may avoid a problem in which performing the primary authentication procedure for the UE while the UE is in flight increases the UE's power consumption, thereby consuming the UE's power in advance and preventing it from completing flight tasks. In addition, suspending or terminating the primary authentication procedure may free up resources required to perform the primary authentication procedure, thereby providing the UE in flight with more available resources to perform unmanned aerial vehicle services.

[0298] FIG. 11 is another schematic flowchart of a communication method according to an embodiment of the present application. In this embodiment, the first control plane procedure is a deregistration procedure, and the deregistration procedure may be initiated by a UDM or may be initiated by an AMF. In addition, in this embodiment, the first device may be a UDM, or the first device may be an AMF. In addition, when the first device is an AMF, the third device may be a UDM. As shown in FIG. 11, the method includes two implementations. One implementation includes the contents shown in steps S1102 to S1104, and the other implementation includes the contents shown in steps S1105 to S1109. When the deregistration procedure is initiated by an AMF, steps S1101 to S1105 are not executed.

[0299] S1101: The UDM determines to start the deregistration procedure.

[0300] S1101 is an optional step. The UDM may initiate a deregistration procedure for the UE. For example, the UDM may determine to initiate a deregistration procedure for the UE based on an operational requirement (e.g., the UE's subscription information changes, or the UE's subscription does not support the current usage status or usage domain). It should be understood that the reason and time for initiating the deregistration procedure by the UDM are not limited to this embodiment of the present application.

[0301] Before the UDM starts the deregistration procedure, the UDM may execute the contents shown in S1102 to S1104, or may execute the contents shown in S1105.

[0302] S1102: The UDM determines that the UE is in flight.

[0303] The UDM may determine the status of the UE. For example, the UDM may obtain the status of the UE from the AMF or the UDR. For a specific implementation process, please refer to the relevant content of Figure 10, in which the SEAF obtains the status of the UE from the AMF. Details will not be described again here. If the UDM determines that the UE is in a flight state, the UDM performs the content shown in S1103. If the UDM determines that the UE is in a non-flight state, the UDM performs a deregistration procedure, for example, sends a message to the AMF used to request (or notify) the AMF to perform the deregistration procedure. In Figure 11, an example is used in which the UDM determines that the UE is in a flight state.

[0304] It should be understood that in Figure 11, the UDM is determined to be in flight as an example. In another possible implementation, S1102 can be replaced with the UDM being determined to be in flight as a first condition is met. For a specific implementation process, please refer to S401. The details will not be described again here.

[0305] S1103: The UDM suspends or terminates the deregistration procedure.

[0306] When determining that the UE is in flight, the UDM may suspend or terminate the deregistration procedure.

[0307] S1104: If the UE is in a flight state while the first timer is running, the UDM terminates the deregistration procedure.

[0308] S1104 is an optional step. For example, the UDM may suspend the deregistration procedure, start a first timer, and determine the status of the UE while the first timer is running. For a specific implementation process, please refer to the relevant content in S1004. Details will not be described again here. If the UDM recognizes from the AMF that the UE is in a non-flight state while the first timer is running, the UDM may terminate the execution of the first timer and prepare to start the deregistration procedure, for example, send a message to the AMF used to request (or notify) the AMF to perform the deregistration procedure. If the UE is in a flight state while the first timer is running (for example, the UDM does not receive information indicating that the UE is in a non-flight state while the first timer is running), the UDM may terminate the deregistration procedure, for example, when the execution of the first timer ends. Figure 11 shows an example in which the UE is in a flight state while the first timer is running.

[0309] S1105: The UDM sends a fourth message to the AMF, and correspondingly, the AMF receives a fourth message from the UDM.

[0310] In this embodiment, the fourth message may be, for example, a deregistration notification message. However, the name of the fourth message is not limited in this embodiment of the present application. The fourth message may be used to request (or notify) the execution of a deregistration procedure.

[0311] S1106: The AMF determines that the UE is in flight.

[0312] The AMF may determine the status of the UE. For a specific implementation process, please refer to the content of Figure 5. The details will not be described again here. If the AMF determines that the UE is in a flight state, the AMF executes the content shown in S1107. If the AMF determines that the UE is in a non-flight state, the AMF executes a deregistration procedure, for example, initiates a procedure to release all sessions of the UE. Optionally, the AMF may send a request message for deregistration to the UE. Figure 11 uses an example in which the AMF determines that the UE is in a flight state.

[0313] It should be understood that in Figure 11, the AMF is determined when the UE is in a flight state as an example. In another possible implementation, S1106 can be replaced with the AMF being determined when the first condition is met. For a specific implementation process, please refer to S401. The details will not be described again here.

[0314] It should be noted that in a deregistration procedure initiated by the AMF, steps S1101 to S1105 are not executed, and only step S1106 is executed. For example, according to the operation or management requirements for the AMF, the AMF cannot support the expiration of the permitted or predetermined UE deregistration time. It should be understood that the reason and time for initiating the deregistration procedure by the AMF are not limited to this embodiment of the present application.

[0315] S1107: AMF suspends or terminates the deregistration procedure.

[0316] When determining that the UE is in flight, the AMF may suspend or terminate the deregistration procedure.

[0317] S1108: If the UE is in a flight state while the first timer is running, the AMF terminates the deregistration procedure.

[0318] S1108 is an optional step. For example, the AMF may suspend the deregistration procedure, start a first timer, and determine the status of the UE while the first timer is running. For a specific implementation process, please refer to the relevant content in S1104. Details will not be described again here. If the UE is in a non-flight state while the first timer is running, the AMF may terminate the execution of the first timer and perform the deregistration procedure. If the UE is in a flight state while the first timer is running, the AMF may terminate the deregistration procedure, for example, when the execution of the first timer ends. Figure 11 shows an example in which the UE is in a flight state while the first timer is running.

[0319] It should be noted that the timer started by the UDM in S1104 may be the same as or different from the timer started by the AMF in S1108, which is not limited in this embodiment of the present application.

[0320] S1109: The AMF sends a fifth message to the UDM, and correspondingly, the UDM receives a fifth message from the AMF.

[0321] In this embodiment, the fifth message may be, for example, a deregistration notification response message. However, the name of the fifth message is not limited in this embodiment of the present application. If the deregistration procedure is not performed, the fifth message may indicate that the deregistration procedure is not performed. If the deregistration procedure is performed in S1106 (the UE is not in a flight state or the first condition is not met), the fifth message may be used to acknowledge that the fourth message is received. Optionally, the fifth message may include a reason for not performing the deregistration procedure. For example, the reason for not performing the deregistration procedure may be a timeout and / or the UE is in a flight state.

[0322] 11 , before performing (or starting) the UE deregistration procedure, the first device may determine the status of the UE, and when determining that the UE is in flight, may suspend or terminate the UE deregistration procedure. This may avoid a problem in which the UE is unable to communicate with the mobile communication network due to the connection between the UE and the mobile communication network being cut off due to completion of the UE deregistration procedure while the UE is in flight, and therefore the UE is unable to respond to control commands from a remote control and perform unmanned aerial vehicle services. In addition, suspending or terminating the deregistration procedure may free up resources required to perform the deregistration procedure, thereby providing the UE in flight with more available resources for performing unmanned aerial vehicle services.

[0323] FIG. 12 is another schematic flowchart of a communication method according to an embodiment of the present application. In this embodiment, the first control plane procedure is a slice authentication procedure. The slice authentication procedure may be initiated by the AAA-S, or may be initiated by the DN, or may be initiated by the AMF. In addition, in this embodiment, the first device may be the NSSAAF, or the first device may be the AMF. In addition, when the first device is the NSSAAF, the third device may be the AAA-S or the DN; or when the first device is the AMF, the third device may be the NSSAAF. As shown in FIG. 12, when the slice authentication procedure is initiated by the AAA-S (or the DN), the method includes two implementations. One implementation includes the contents shown in steps S1203 to S1206, and the other implementation includes the contents shown in steps S1207 to S1212. When the slice authentication procedure is initiated by the AMF, the implementation includes the contents shown in steps S1208 to S1212.

[0324] S1201: The AAA-S determines to start a slice authentication procedure or a slice re-authentication procedure.

[0325] In Figure 12, an example is used in which the AAA-S determines to initiate the slice authentication procedure.

[0326] S1201 is an optional step. The AAA-S may initiate a slice authentication procedure for the UE. For example, the AAA-S may determine to initiate the slice authentication procedure for the UE based on the AAA-S detecting that the slice usage status of the UE is abnormal. In another example, the AAA-S may periodically or aperiodically initiate the slice authentication procedure for the UE. It should be understood that the reason and time for the AAA-S to initiate the slice authentication procedure are not limited to this embodiment of the present application.

[0327] It should be noted that in this embodiment, the steps performed by the AAA-S may alternatively be performed by the DN.

[0328] S1202: The AAA-S sends a fourth message to the NSSAAF, and in response, the NSSAAF receives a fourth message from the AAA-S.

[0329] In this embodiment, the fourth message may be, for example, an authentication request message or a re-authenticate request message. However, the name of the fourth message is not limited in this embodiment of the present application. The fourth message may be used to request (or notify) that a slice authentication procedure be performed.

[0330] After the NSSAAF receives the fourth message, the NSSAAF may execute the contents shown in S1203 to S1206, or may execute the contents shown in S1207.

[0331] S1203: The NSSAAF determines that the UE is in flight.

[0332] The NSSAAF may determine the status of the UE. For example, the NSSAAF may obtain the status of the UE from the AMF. For a specific implementation process, please refer to the relevant content of Figure 10, in which the SEAF obtains the status of the UE from the AMF. Details will not be described again here. If the NSSAAF determines that the UE is in a flight state, the content shown in S1204 is executed. If the NSSAAF determines that the UE is in a non-flight state, a slice authentication procedure is executed, for example, a message used to request (or notify) the AMF to execute the slice authentication procedure is sent. In Figure 12, an example is used in which the NSSAAF determines that the UE is in a flight state.

[0333] It should be understood that in Figure 12, the NSSAAF is used as an example to determine that the UE is in a flight state. In another possible implementation, S1202 can be replaced with the NSSAAF being determined when the first condition is met. For a specific implementation process, please refer to S401. The details will not be described again here.

[0334] S1204: The NSSAAF suspends or terminates the slice authentication procedure.

[0335] The NSSAAF may suspend or terminate the slice authentication procedure when it determines that the UE is in flight.

[0336] S1205: If the UE is in a flight state while the first timer is running, the NSSAAF terminates the slice authentication procedure.

[0337] S1205 is an optional step. For example, the NSSAAF may suspend the slice authentication procedure, start a first timer, and determine the status of the UE while the first timer is running. For a specific implementation process, please refer to the relevant content in S1004. Details will not be described again here. If the NSSAAF recognizes from the AMF that the UE is in a non-flight state while the first timer is running, the NSSAAF may terminate the execution of the first timer and perform the slice authentication procedure, for example, send a message to the AMF used to request (or notify) the execution of the slice authentication procedure. If the UE is in a flight state while the first timer is running (for example, the NSSAAF does not receive information indicating that the UE is in a non-flight state while the first timer is running), the NSSAAF may terminate the slice authentication procedure, for example, when the execution of the first timer ends. Figure 12 shows an example in which the UE is in a flight state while the first timer is running.

[0338] S1206: The NSSAAF sends a fifth message to the AAA-S, and in response, the AAA-S receives a fifth message from the NSSAAF.

[0339] In this embodiment, the fifth message may be, for example, an authentication response or a re-authenticate response message. However, the name of the fifth message is not limited in this embodiment of the present application. The fifth message may indicate that the slice authentication procedure will not be performed. Optionally, the fifth message may include a reason for not performing the slice authentication procedure. For example, the reason for not performing the slice authentication procedure may be a timeout and / or the UE being in a flight state.

[0340] S1207: The NSSAAF sends a fourth message to the AMF, and correspondingly, the AMF receives a fourth message from the NSSAAF.

[0341] For an explanation of the fourth message, please refer to the contents of S1202. The details will not be explained again here.

[0342] S1208: The AMF determines that the UE is in flight.

[0343] It should be noted that in a slice authentication procedure initiated by the AMF, steps S1201 to S1207 are not performed, and step S1208 is directly performed. For example, the AMF may determine that slice authentication needs to be performed on the UE based on a received UE registration request message, and prepare to start slice authentication. In another example, the AMF may determine that slice authentication needs to be started after the UE performs primary authentication again or the UE moves to a new PLMN (e.g., roams). It should be understood that the reason and time for starting the slice authentication procedure by the AMF are not limited to this embodiment of the present application.

[0344] The AMF may determine the status of the UE. For a specific implementation process, please refer to the content of Figure 5. The details will not be described again here.

[0345] If the AMF determines that the UE is in flight, the AMF executes the contents shown in S1209.

[0346] If the AMF determines that the UE is in a non-flight state, steps S1209 to S1212 are not performed, and the slice authentication procedure is performed. If the slice authentication is initiated by the AAA-S, the AMF may send a response message for the fourth message to the NSSAAF. Optionally, before sending the response message for the fourth message, the AMF may send a slice authentication message to the UE. Furthermore, if the AMF initiates the slice authentication procedure, the AMF may further send a slice authentication request message to the AAA-S (through the NSSAAF). Figure 12 does not show steps for performing slice authentication. In addition, in Figure 12, an example is used in which the AMF determines that the UE is in a flight state.

[0347] It should be understood that in Figure 12, the AMF is determined when the UE is in a flight state as an example. In another possible implementation, S1208 can be replaced with the AMF being determined when the first condition is met. For a specific implementation process, please refer to S401. The details will not be described again here.

[0348] S1209: AMF suspends or terminates the slice authentication procedure.

[0349] The AMF may suspend or terminate the slice authentication procedure when it determines that the UE is in flight.

[0350] S1210: If the UE is in a flight state while the first timer is running, the AMF terminates the slice authentication procedure.

[0351] S1210 is an optional step. For example, the AMF may suspend the slice authentication procedure, start a first timer, and determine the status of the UE while the first timer is running. For a specific implementation process, please refer to the relevant content in S1205. Details will not be described again here. If the UE is in a non-flight state while the first timer is running, the AMF may terminate the execution of the first timer and perform the slice authentication procedure. If the UE is in a flight state while the first timer is running, the AMF may terminate the slice authentication procedure, for example, when the execution of the first timer ends. Figure 12 shows an example in which the UE is in a flight state while the first timer is running.

[0352] It should be noted that the timer started by the NSSAAF in S1205 may be the same as or different from the timer started by the AMF in S1210, which is not limited in this embodiment of the present application.

[0353] S1211: The AMF sends a fifth message to the NSSAAF, and correspondingly, the NSSAAF receives a fifth message from the AMF.

[0354] For an explanation of the fifth message, please refer to the contents of S1206. The details will not be explained again here.

[0355] S1212: The NSSAAF sends a fifth message to the AAA-S, and in response, the AAA-S receives a fifth message from the NSSAAF.

[0356] After receiving the fifth message, the NSSAAF may forward the fifth message to the AAA-S. For details, please refer to the relevant description of S1206. The details will not be repeated here.

[0357] In the procedure shown in FIG. 12, before performing the slice authentication procedure for the UE, the first device may determine the status of the UE, and when determining that the UE is in a flight state, may suspend or terminate the slice authentication procedure for the UE. This may avoid the problem of increasing the power consumption of the UE by performing the slice authentication procedure for the UE while the UE is in flight, thereby pre-consuming the UE's power and preventing it from completing the flight task. In addition, suspending or terminating the slice authentication procedure may free up resources required to perform the slice authentication procedure, thereby providing the flying UE with more available resources to perform unmanned aerial vehicle services.

[0358] 13 is another schematic flowchart of a communication method according to an embodiment of the present application. In this embodiment, the first control plane procedure is a secondary authentication procedure. The secondary authentication procedure may be initiated by the AAA-S, or may be initiated by the DN, or may be initiated by the SMF. In addition, in this embodiment, the first device is the SMF, and the third device is the AAA-S or the DN. As shown in FIG. 13, the method includes the following steps:

[0359] S1301: The AAA-S determines to start a secondary authentication procedure or a re-authentication procedure of the secondary authentication.

[0360] In FIG. 13, an example is used in which the AAA-S determines to initiate a secondary authentication procedure.

[0361] S1301 is an optional step. The AAA-S may initiate a secondary authentication procedure for the UE. For example, the AAA-S may determine to initiate a secondary authentication procedure for the UE based on the AAA-S detecting that the UE's session is abnormal. In another example, the AAA-S may initiate the secondary authentication procedure for the UE periodically or aperiodically. It should be understood that the reason and time for the AAA-S to initiate the secondary authentication procedure are not limited to this embodiment of the present application.

[0362] It should be noted that in this embodiment, the steps performed by the AAA-S may alternatively be performed by the DN.

[0363] S1302: The AAA-S sends a fourth message to the SMF, and in response, the SMF receives a fourth message from the AAA-S.

[0364] In this embodiment, the fourth message may be, for example, a re-authenticate request or an authentication request message. However, the name of the fourth message is not limited in this embodiment of the present application. The fourth message may be used to request (or notify) that a secondary authentication procedure be performed.

[0365] S1303: The SMF determines that the UE is in flight.

[0366] It should be noted that in the secondary authentication procedure initiated by the SMF, the SMF does not perform S1301 and S1302, but directly initiates S1303. For example, the SMF may determine that the UE requires secondary authentication based on the received UE session establishment request message. It should be understood that the reason and time for initiating the secondary authentication procedure by the SMF are not limited to this embodiment of the present application.

[0367] The SMF may determine the status of the UE. For example, the SMF may obtain the status of the UE from the AMF. For a specific implementation process, please refer to the relevant content of Figure 10, in which the SEAF obtains the status of the UE from the AMF. Details will not be repeated here. If the SMF determines that the UE is in a flight state, the SMF executes the content shown in S1304. If the SMF determines that the UE is in a non-flight state, the SMF executes a secondary authentication procedure (secondary authentication procedure initiated by the AAA-S) or initiates a secondary authentication procedure (secondary authentication procedure initiated by the AMF). The secondary authentication procedure is not shown in Figure 13. In Figure 13, an example is used in which the SMF determines that the UE is in a flight state.

[0368] It should be understood that in Figure 13, the SMF is determined when the UE is in flight state is used as an example. In another possible implementation, S1302 can be replaced with the SMF being determined when the first condition is met. For a specific implementation process, please refer to S401. The details will not be described again here.

[0369] S1304: The SMF suspends or terminates the secondary authentication procedure.

[0370] The SMF may suspend or terminate the secondary authentication procedure when it determines that the UE is in flight.

[0371] S1305: If the UE is in a flight state while the first timer is running, the SMF terminates the secondary authentication procedure.

[0372] S1305 is an optional step. For example, the SMF may suspend the secondary authentication procedure, start a first timer, and determine the status of the UE while the first timer is running. For a specific implementation process, please refer to the relevant content in S1004. Details will not be described again here. If the SMF recognizes from the AMF that the UE is in a non-flight state while the first timer is running, the SMF may terminate the execution of the first timer and prepare to start the secondary authentication procedure, for example, send a message to the AMF used to request (or notify) the execution of the secondary authentication procedure. If the UE is in a flight state while the first timer is running (for example, the SMF does not receive information indicating that the UE is in a non-flight state from the AMF while the first timer is running), the SMF may terminate the secondary authentication procedure, for example, when the execution of the first timer ends. Figure 13 shows an example in which the UE is in a flight state while the first timer is running.

[0373] S1306: The SMF sends a fifth message to the AAA-S, and correspondingly, the AAA-S receives a fifth message from the SMF.

[0374] In this embodiment, the fifth message may be, for example, a re-authenticate response message. However, the name of the fifth message is not limited in this embodiment of the present application. The fifth message may indicate that the secondary authentication procedure is not performed. Optionally, the fifth message may include a reason for not performing the secondary authentication procedure. For example, the reason for not performing the secondary authentication procedure may be a timeout and / or the UE being in a flight state.

[0375] In the procedure shown in Figure 13, before performing the secondary authentication procedure of the UE, the first device may determine the status of the UE, and when determining that the UE is in a flight state, may suspend or terminate the secondary authentication procedure of the UE. This may avoid the problem of increasing the power consumption of the UE by performing the secondary authentication procedure of the UE while the UE is in flight, thereby pre-consuming the UE's power and preventing it from completing flight tasks. In addition, suspending or terminating the secondary authentication procedure may free up resources required to perform the secondary authentication procedure, thereby providing the UE in flight with more available resources to perform unmanned aerial vehicle services.

[0376] In the above embodiments provided in the present application, the methods provided in the embodiments of the present application are described separately from the perspective of the interaction between the first device and the second device. To implement the functions in the above methods provided in the embodiments of the present application, the first device or the second device may include a hardware structure and / or a software module, and may implement the functions in the form of a hardware structure, a software module, or a combination of a hardware structure and a software module.

[0377] The following describes a communication device for implementing the above method in the embodiments of the present application with reference to the accompanying drawings. Therefore, all of the above content can be used in the following embodiments. The repeated content will not be described again.

[0378] FIG. 14 is a diagram of the structure of a communication device 1400. The communication device 1400 may correspondingly implement functions or steps implemented by the first device or the second device in the above-mentioned method embodiments. The communication device may include a processing unit 1401 and a transceiver unit 1402. Optionally, the communication device 1400 may further include a storage unit (not shown in FIG. 14). The storage unit may be configured to store instructions (codes or programs) and / or data. The processing unit 1401 and the transceiver unit 1402 may be coupled to the storage unit. For example, the processing unit 1401 may read the instructions (codes or programs) and / or data in the storage unit and implement the corresponding method. The above units may be independently located or partially or fully integrated. For example, the transceiver unit 1402 may include a transmitting unit and a receiving unit.

[0379] In examples, the communications apparatus 1400 may implement the functions or steps implemented by the first device in the method embodiments described above.

[0380] The processing unit 1401 is configured to determine that a first condition is met, where the first condition includes one or more of the following conditions: the terminal device is authorized for unmanned aircraft services, the terminal device initiates establishment of a first session corresponding to the unmanned aircraft services, or the terminal device is in an airborne state; and to restrict non-unmanned aircraft services of the terminal device and / or restrict a first control plane procedure of the terminal device, where the first control plane procedure is not a procedure specific to the unmanned aircraft services.

[0381] In a possible implementation, when restricting a non-unmanned aerial vehicle service of a terminal device, the processing unit 1401 may be specifically configured to: when the first device is a first session management function device, release all or part of a session corresponding to the non-unmanned aerial vehicle service managed by the first device, and / or prohibit the establishment or modification of a session corresponding to the non-unmanned aerial vehicle service; or when the first device is a short message service service center, skip or suspend sending a first message to the terminal device, where the first message is used to request the establishment or modification of a session corresponding to the non-unmanned aerial vehicle service; or when the first device is a terminal device, skip or suspend sending a first message to the first session management function device, where the first message is used to request the establishment or modification of a session corresponding to the non-unmanned aerial vehicle service.

[0382] In a possible implementation, when the first device determines that the terminal device is authorized for unmanned aircraft services and / or that the terminal device is in an airborne state, before the first device restricts the non-unmanned aircraft services of the terminal device and / or restricts the first control plane procedure, the transceiver unit 1402 is configured to receive a second message from the terminal device, where the second message is used to request establishing a first session; and the processing unit 1401 is further configured to determine, based on the second message, that the first session belongs to a session corresponding to the unmanned aircraft service.

[0383] In a possible implementation, the transceiver unit 1402 is further configured to send a third message to the second device, where the third message is used to request restricting non-unmanned aerial vehicle services of the terminal device.

[0384] In one possible implementation, the transceiver unit 1402 is further configured to receive first instruction information from the second device, where the first instruction information instructs the second device to release one or more sessions corresponding to the non-unmanned aerial vehicle services. When the non-unmanned aerial vehicle services of the terminal device are restricted, the processing unit 1401 is specifically configured to release one or more sessions corresponding to the non-unmanned aerial vehicle services based on the first instruction information.

[0385] In another possible implementation, the first device restricting the non-unmanned aerial vehicle services of the terminal device includes the first device releasing all or a portion of the sessions corresponding to the non-unmanned aerial vehicle services managed by the first device, and the processing unit 1401 is further configured to determine N is greater than M, where N is the number of sessions corresponding to the non-unmanned aerial vehicle services managed by the first device, and M is the number of sessions corresponding to the non-unmanned aerial vehicle services that are allowed to be established on the first device when the terminal device performs the unmanned aerial vehicle service; and determining to release H sessions corresponding to the non-unmanned aerial vehicle services, where H is a positive integer greater than or equal to (NM).

[0386] In a possible implementation, when the non-unmanned aerial vehicle service of the terminal device is restricted, the transceiver unit 1402 is configured to send second instruction information to the terminal device, where the second instruction information indicates that establishment of a session corresponding to the non-unmanned aerial vehicle service is prohibited.

[0387] In a possible implementation, the first control plane procedure includes one or more of a primary authentication procedure, a deregistration procedure, a slice authentication procedure, or a secondary authentication procedure.

[0388] In a possible implementation, when the first control plane procedure of the terminal device is restricted, the processing unit 1401 is configured to suspend or terminate the first control plane procedure.

[0389] In a possible implementation, after the first device suspends the first control plane procedure, the processing unit 1401 is further configured to start a first timer; determine that the terminal device satisfies a first condition while the first timer is running; and terminate the first control plane procedure when the execution of the first timer ends.

[0390] In a possible implementation, the transceiver unit 1402 is further configured to receive a fourth message from the third device, where the fourth message is used to request performing the first control plane procedure; and send a fifth message to the third device, where the fifth message includes a reason for not performing the first control plane procedure.

[0391] In a possible implementation, when it is determined that the terminal device is in a flight state, the transceiver unit 1402 is configured to receive third instruction information from the access and mobility management function device, where the third instruction information indicates that the terminal device is in a flight state.

[0392] Optionally, the transceiver unit 1402 is further configured to send a sixth message to the access and mobility management function network element, where the sixth message is used to obtain a status of the terminal device, and the status of the terminal device includes a flying state and / or a non-flying state.

[0393] In a possible implementation, the first device is an access and mobility management function device; when determining that the terminal device is in a flight state, the transceiver unit 1402 is configured to receive fourth instruction information from the fourth device, where the fourth instruction information indicates that the terminal device is in a flight state; or the processing unit 1401 is configured to determine that the terminal device is in a flight state based on the mobility information of the terminal device and / or the flight information of the terminal device.

[0394] In a possible implementation, the first device is a terminal device; when determining that the terminal device is in a flight state, the processing unit 1401 is configured to determine that the terminal device is in a flight state based on mobility information and / or fifth instruction information from the application layer, where the fifth instruction information instructs the terminal device to enter a flight mode.

[0395] In a possible implementation, the processing unit 1401 is further configured to: determine that a second condition is met, where the second condition includes one or more of the following conditions: authorization for the unmanned aircraft service is revoked from the terminal device, the terminal device is not authorized for the unmanned aircraft service, the unmanned aircraft service of the terminal device is deregistered, or the terminal device releases the last session corresponding to the unmanned aircraft service.

[0396] The first device is a first session management function device, the transceiver unit 1402 is further configured to receive a seventh message from the terminal device, and the processing unit 1401 is further configured to establish or modify a session corresponding to a non-unmanned aerial vehicle service based on the seventh message, where the seventh message is used to request the establishment or modification of a session corresponding to a non-unmanned aerial vehicle service.

[0397] Alternatively, the first device is a short message service service center, and the transceiver unit 1402 is further configured to send an eighth message to the terminal device, where the eighth message is used to request establishing or modifying a session corresponding to a non-unmanned aerial vehicle service.

[0398] Alternatively, the first device is a terminal device, and the transceiver unit 1402 is further configured to send an eighth message to the first session management function device, where the eighth message is used to request establishing or modifying a session corresponding to a non-unmanned aerial vehicle service.

[0399] In a possible implementation, the processing unit 1401 is further configured to: determine that a second condition is met, where the second condition includes one or more of the following conditions: approval for the unmanned aircraft service is revoked from the terminal device, the terminal device is not approved for the unmanned aircraft service, the unmanned aircraft service of the terminal device is deregistered, or the terminal device releases the last session corresponding to the unmanned aircraft service; the transceiver unit 1402 is further configured to: receive a fourth message from the third device, where the fourth message is used to request performing a first control plane procedure; and the processing unit 1401 is further configured to perform the first control plane procedure.

[0400] In another example, the communications apparatus 1400 may implement the functions or steps implemented by the second device in the method embodiments described above.

[0401] The transceiver unit 1402 is configured to receive a message from a first session management function device, used to request restricting a non-unmanned aerial vehicle service of a terminal device.

[0402] The processing unit 1401 is configured to determine, based on the message, that a second session management function device manages a session corresponding to the non-unmanned aerial vehicle service of the terminal device.

[0403] The transceiver unit 1402 is further configured to send instruction information to the second session management function device, where the instruction information instructs the second session management function device to release all or part of the session corresponding to the non-unmanned aerial vehicle service managed by the second session management function device, and / or to prohibit the establishment or modification of the session corresponding to the non-unmanned aerial vehicle service.

[0404] In a possible implementation, the transceiver unit 1402 is further configured to send first instruction information to the first session management function device, where the first instruction information instructs the release of one or more sessions corresponding to the non-unmanned aerial vehicle service.

[0405] In a possible implementation, the transceiver unit 1402 is further configured to: receive N from the first session management function device, where N is the number of sessions corresponding to non-unmanned aerial vehicle services managed by the first session management function device; and the processing unit 1401 is further configured to: determine that the first session management function device needs to release one or more sessions corresponding to the non-unmanned aerial vehicle services based on the number of sessions corresponding to non-unmanned aerial vehicle services established by the terminal device, N and M, where M is the number of sessions corresponding to non-unmanned aerial vehicle services that are allowed to be established on the first session management function device when the terminal device executes the unmanned aerial vehicle service.

[0406] For a more detailed description of the processing unit 1401 and the transceiver unit 1402, please directly refer to the relevant description in the method embodiments shown in any one of Figures 4 to 13. The details will not be described again here.

[0407] 15 illustrates a communication device 1500 according to an embodiment of the present application. The communication device 1500 may be a first device and may implement the functions of the first device in the method provided in the embodiment of the present application. Alternatively, the communication device 1500 may be a second device and may implement the functions of the second device in the method provided in the embodiment of the present application. Alternatively, the communication device 1500 may be a device that supports the first device in implementing the corresponding functions of the method provided in the embodiment of the present application, or a device that supports the second device in implementing the corresponding functions of the method provided in the embodiment of the present application. The communication device 1500 may be a chip system. In this embodiment of the present application, the chip system may include a chip, or may include a chip and other discrete components.

[0408] The communication device 1500 includes at least one processor 1520 configured to implement or support the communication device 1500 in implementing the functions of the first device or the second device in the method provided in the embodiment of the present application. For details, please refer to the detailed description in the exemplary method. Details will not be described again here.

[0409] Optionally, the communication device 1500 may further include at least one memory 1530 configured to store program instructions and / or data. The memory 1530 is coupled to the processor 1520. A coupling in this embodiment of the present application refers to an indirect coupling or communication connection between devices, units, or modules, which may be electrical, mechanical, or another form and is used to exchange information between the devices, units, or modules. The processor 1520 may cooperate with the memory 1530. The processor 1520 may execute the program instructions and / or data stored in the memory 1530, enabling the communication device 1500 to implement a corresponding method. At least one of the at least one memory may be included in the processor. The memory 1530 may exist independently, for example, as an off-chip memory, and be connected to the processor 1520 through a communication bus (represented by the thick line 1540 in FIG. 15 ). Alternatively, the memory 1530 may be integrated into the processor 1520.

[0410] Optionally, communication apparatus 1500 may further include a communication interface 1510 configured to communicate with another device by using a transmission medium, such that a device used in communication apparatus 1500 may communicate with another device. For example, when the communication apparatus is a first device, the other device is a second device or a third device. Processor 1520 may transmit and receive data through communication interface 1510. Communication interface 1510 may specifically be a transceiver.

[0411] In a hardware implementation, the transceiver unit 1402 may be a transceiver, which is integrated into the communication device 1500 to form a communication interface 1510 .

[0412] The specific connection medium between the communication interface 1510, the processor 1520, and the memory 1530 is not limited in this embodiment of the present application. In this embodiment of the present application, in FIG. 15, the memory 1530, the processor 1520, and the communication interface 1510 are connected through a communication bus 1540. The manner of connection between other components is merely an example for explanation and is not limited thereto. The communication bus 1540 may be classified as an address bus, a data bus, a control bus, or the like. For ease of representation, only one thick line is used for representation in FIG. 15, but this does not mean that there is only one communication bus or only one type of communication bus.

[0413] In the embodiments of the present application, the processor 1520 may be a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, which may implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of the present application. The general-purpose processor may be a microprocessor, or any conventional processor or the like. The steps of the methods disclosed with reference to the embodiments of the present application may be performed directly by a hardware processor, or may be performed by a combination of hardware and software modules in the processor.

[0414] In embodiments of the present application, memory 1530 may be a non-volatile memory, such as a hard disk drive (HDD) or a solid-state drive (SSD), or a volatile memory, such as a random access memory (RAM). Memory is any medium that can carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited to such. Memory in embodiments of the present application may alternatively be a circuit or any other device capable of implementing a memory function and configured to store program instructions and / or data.

[0415] An embodiment of the present application further provides a communication system, specifically, the communication system includes a first device and / or a second device.

[0416] An embodiment of the present application further provides a computer-readable storage medium containing instructions, which, when executed on a computer, enable the computer to perform the method in the above embodiment.

[0417] An embodiment of the present application further provides a computer program product including instructions, which, when executed on a computer, enable the computer to perform the method in the above embodiment.

[0418] An embodiment of the present application provides a chip system, which includes a processor and may further include memory, and is configured to implement the functions of the first device or the second device in the above-described method. The chip system may include a chip, or may include a chip and other discrete components.

[0419] It should be understood that in the embodiments of the present application, the sequence numbers of the processes do not mean the order of execution, and the order of execution of the processes should be determined according to the functions and internal logic of the processes, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0420] Those skilled in the art may recognize that, in combination with the examples described in the embodiments disclosed herein, the units and algorithm steps may be implemented by electronic hardware or a combination of computer software and electronic hardware. Whether a function is implemented by hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art may use different methods to implement the described functions for each specific application, but such implementations should not be considered to go beyond the scope of the present application.

[0421] Those skilled in the art can clearly understand that for convenience and conciseness of description, the specific operation processes of the above-described systems, devices and units may refer to the corresponding processes in the above-described method embodiments, and the details will not be described again in this specification.

[0422] In some embodiments provided herein, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the described device embodiments are merely examples. For example, the division into units is merely a logical division of functionality. In actual implementation, other division schemes may exist. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not implemented. In addition, the shown or described mutual couplings or direct couplings or communication connections may be implemented through some interfaces, and indirect couplings or communication connections between devices or units may be implemented in electrical, mechanical, or other forms.

[0423] Units described as separate parts may or may not be physically separate, and parts presented as units may or may not be physical units, and may be located in one place or distributed over multiple network units. Some or all of the units may be selected according to actual requirements to achieve the objectives of the solutions in the embodiments.

[0424] In addition, the functional units in the embodiments of the present application may be integrated into one processing unit, or each of the units may exist physically alone, or two or more units may be integrated into one unit.

[0425] When a function is implemented in the form of a software functional unit and sold or used as an independent product, the function may be stored in a computer-readable storage medium. Based on this understanding, the technical solutions of the present application may be essentially implemented in the form of a software product, or a portion contributing to the prior art may be implemented in the form of a software product. A computer software product is stored in a storage medium and includes a plurality of instructions for instructing a computer device (which may be a personal computer, a server, or a network device) to perform all or some of the steps of the method described in the embodiments of the present application. The storage medium includes any medium capable of storing program code, such as a USB flash drive, a removable hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0426] The above description is merely a specific implementation of the present application. However, the scope of protection of the embodiments of the present application is not limited thereto. Any modifications or substitutions that are easily understood by those skilled in the art within the technical scope disclosed in the embodiments of the present application shall fall within the scope of protection of the embodiments of the present application. Therefore, the scope of protection of the embodiments of the present application shall be subject to the scope of protection of the claims.

Claims

1. determining, by a first device, that a first condition is satisfied, wherein the first condition includes one or more of the following conditions: the terminal device is approved for unmanned aerial vehicle service, the terminal device initiates establishment of a first session corresponding to the unmanned aerial vehicle service, or the terminal device is in an airborne state; and restricting, by the first device, non-unmanned aerial vehicle services of the terminal device and / or restricting a first control plane procedure of the terminal device, wherein the first control plane procedure is not a procedure specific to the unmanned aerial vehicle service; A communication method comprising:

2. The step of restricting non-unmanned aerial vehicle services of the terminal device by the first device comprises: the first device is a first session management function device, and releasing, by the first device, all or a portion of a session corresponding to the non-unmanned aerial vehicle service managed by the first device and / or prohibiting establishment or modification of a session corresponding to the non-unmanned aerial vehicle service; or the first device is a short message service service center, and skipping or suspending, by the first device, sending a first message to the terminal device, where the first message is used to request establishing or modifying a session corresponding to the non-unmanned aerial vehicle service; or the first device is the terminal device, skipping or suspending, by the first device, sending a first message to a first session management function device, wherein the first message is used to request establishing or modifying a session corresponding to the non-unmanned aerial vehicle service; The method of claim 1 , comprising:

3. If the first device determines that the terminal device is approved for the unmanned aerial vehicle service and / or that the terminal device is in a flight state, Prior to the step of restricting non-unmanned aerial vehicle services of the terminal device by the first device and / or the step of restricting first control plane procedures, the method may further include: receiving, by the first device, a second message from the terminal device, wherein the second message is used to request establishing a first session; and determining, by the first device, based on the second message, that the first session belongs to a session corresponding to the unmanned aerial vehicle service. The method of claim 1 or 2, comprising:

4. The method further comprises: transmitting, by the first device, a third message to a second device, wherein the third message is used to request restricting the non-unmanned aerial vehicle services of the terminal device; The method of any one of claims 1 to 3, comprising:

5. The method further comprises: receiving, by the first device, first instruction information from the second device, wherein the first instruction information instructs the release of one or more sessions corresponding to the non-unmanned aerial vehicle service. Provided with: The step of restricting non-unmanned aerial vehicle services of the terminal device by the first device comprises: releasing, by the first device, the one or more sessions corresponding to the non-unmanned aerial vehicle service based on the first instruction. The method of claim 4, comprising:

6. The step of restricting, by the first device, the non-unmanned aerial vehicle service of the terminal device includes the step of releasing, by the first device, all or a portion of a session corresponding to the non-unmanned aerial vehicle service managed by the first device, and the method further includes: determining, by the first device, that N is greater than M, where N is the number of sessions corresponding to the non-unmanned aerial vehicle service managed by the first device, and M is the number of sessions corresponding to the non-unmanned aerial vehicle service that are permitted to be established on the first device when the terminal device executes the unmanned aerial vehicle service; and determining, by the first device, to release H sessions corresponding to the non-unmanned aerial vehicle services, where H is a positive integer greater than or equal to (N-M); 5. The method of claim 1, comprising:

7. The step of restricting non-unmanned aerial vehicle services of the terminal device by the first device includes: transmitting, by the first device, second instruction information to the terminal device, wherein the second instruction information indicates that establishment of the session corresponding to the non-unmanned aerial vehicle service is prohibited; 7. The method of claim 1, comprising:

8. The method of claim 1 , wherein the first control plane procedure comprises one or more of a primary authentication procedure, a de-registration procedure, a slice authentication procedure, or a secondary authentication procedure.

9. The step of restricting a first control plane procedure of the terminal device by the first device comprises: suspending or terminating the first control plane procedure by the first device. The method of claim 8, comprising:

10. After the step of suspending the first control plane procedure by the first device, the method further comprises: starting a first timer by the first device; determining, by the first device, that the terminal device satisfies the first condition during execution of the first timer; and Terminating the first control plane procedure by the first device when the execution of the first timer expires. The method of claim 9 comprising:

11. The method further comprises: receiving, by the first device, a fourth message from a third device, wherein the fourth message is used to request that the first control plane procedure be performed; and sending, by the first device, a fifth message to the third device, wherein the fifth message includes a reason for not performing the first control plane procedure; 11. The method of claim 9 or 10, comprising:

12. The step of determining, by the first device, that the terminal device is in a flight state includes: receiving, by the first device, third indication information from an access and mobility management function device, wherein the third indication information indicates that the terminal device is in a flight state.

12. The method of any one of claims 1 to 11, comprising:

13. The method further comprises: sending, by the first device, a sixth message to the access and mobility management function device, wherein the sixth message is used to obtain a status of the terminal device, the status of the terminal device including the flight status and / or non-flight status; The method of claim 12, comprising:

14. the first device is an access and mobility management function device; The step of determining, by the first device, that the terminal device is in a flight state includes: receiving, by the first device, fourth indication information from a fourth device, wherein the fourth indication information indicates that the terminal device is in a flight state; or determining, by the first device, that the terminal device is in a flight state based on mobility information of the terminal device and / or flight information of the terminal device; 12. The method of any one of claims 1 to 11, comprising:

15. the first device is the terminal device; The step of determining, by the first device, that the terminal device is in a flight state includes: determining, by the first device, that the terminal device is in a flight state based on mobility information and / or fifth instruction information from an application layer, wherein the fifth instruction information instructs the terminal device to enter a flight mode; 12. The method of any one of claims 1 to 11, comprising:

16. The method further comprises: determining, by the first device, that a second condition is satisfied, wherein the second condition includes one or more of the following conditions: authorization for the unmanned aerial vehicle service is revoked from the terminal device, the terminal device is not authorized for the unmanned aerial vehicle service, the terminal device is deregistered for the unmanned aerial vehicle service, or the terminal device releases its last session corresponding to the unmanned aerial vehicle service; and the first device is the first session management function device, receiving, by the first device, a seventh message from the terminal device and establishing or modifying a session corresponding to the non-unmanned aerial vehicle service based on the seventh message, wherein the seventh message is used to request establishing or modifying the session corresponding to the non-unmanned aerial vehicle service; or the first device is the short message service service center, and sending, by the first device, an eighth message to the terminal device, wherein the eighth message is used to request establishing or modifying a session corresponding to the non-unmanned aerial vehicle service; or the first device is a terminal device, and sending, by the first device, an eighth message to the first session management function device, wherein the eighth message is used to request establishing or modifying a session corresponding to the non-unmanned aerial vehicle service.

16. The method of any one of claims 1 to 15, comprising:

17. The method further comprises: determining, by the first device, that the second condition is satisfied, wherein the second condition includes one or more of the following conditions: authorization for the unmanned aerial vehicle service is revoked from the terminal device, the terminal device is not authorized for the unmanned aerial vehicle service, the terminal device is deregistered for the unmanned aerial vehicle service, or the terminal device releases the last session corresponding to the unmanned aerial vehicle service; receiving, by the first device, the fourth message from the third device, wherein the fourth message is used to request that the first control plane procedure be performed; and executing, by the first device, the first control plane procedure.

17. The method of any one of claims 1 to 16, comprising:

18. receiving, by a second device, a message from a first device used to request restricting non-unmanned aerial vehicle services of the terminal device, wherein the first device is a first session management function device; determining, by the second device, based on the message, that a second session management function device manages a session corresponding to the non-unmanned aerial vehicle service of the terminal device; and sending, by the second device, instruction information to the second session management function device, wherein the instruction information instructs the second device to release all or part of the session corresponding to the non-unmanned aerial vehicle service managed by the second session management function device and / or instructs the second device to prohibit establishment or modification of the session corresponding to the non-unmanned aerial vehicle service; A communication method comprising:

19. The method further comprises: sending, by the second device, first instruction information to the first session management function device, wherein the first instruction information instructs the release of one or more sessions corresponding to the non-unmanned aerial vehicle service; 20. The method of claim 18, comprising:

20. The method further comprises: receiving, by the second device, N from the first session management function device, where N is the number of sessions corresponding to the non-unmanned aerial vehicle service managed by the first session management function device; and determining, by the second device, that the first session management function device needs to release one or more sessions corresponding to the non-unmanned aerial vehicle service based on the number of sessions corresponding to the non-unmanned aerial vehicle service established by the terminal device, N and M, where M is the number of sessions corresponding to the non-unmanned aerial vehicle service that are allowed to be established on the first session management function device when the terminal device executes the unmanned aerial vehicle service; 20. The method of claim 19, comprising:

21. A communications device comprising a processing unit and a transceiver unit, wherein the processing unit is configured to determine that a first condition is met, wherein the first condition includes one or more of the following conditions: a terminal device is authorized for unmanned aerial vehicle service, the terminal device initiates establishment of a first session corresponding to the unmanned aerial vehicle service, or the terminal device is in an airborne state; and restrict non-unmanned aerial vehicle services of the terminal device and / or restrict a first control plane procedure of the terminal device, wherein the first control plane procedure is not a procedure specific to the unmanned aerial vehicle service; and The transceiver unit is configured to perform reception and transmission of the communication device. Communication equipment.

22. When the non-unmanned aerial vehicle service of the terminal device is restricted: the communications device is a first session management function device, and the processing unit is specifically configured to release all or a portion of a session corresponding to the non-unmanned aerial vehicle service managed by the communications device and / or prohibit establishment or modification of a session corresponding to the non-unmanned aerial vehicle service; or The communication device is a short message service service center, and the transceiver unit is specifically configured to skip or postpone sending a first message to the terminal device, where the first message is used to request establishing or modifying a session corresponding to the non-unmanned aerial vehicle service; or the communication device is the terminal device, and the transceiver unit is specifically configured to skip or postpone sending a first message to a first session management function device, where the first message is used to request establishing or modifying a session corresponding to the non-unmanned aerial vehicle service; 22. The apparatus of claim 21.

23. If it is determined that the terminal device is approved for the unmanned aerial vehicle service and / or that the terminal device is in a flight state, Before the non-unmanned aerial vehicle service of the terminal device is restricted and / or a first control plane procedure is restricted, the transceiver unit is further configured to receive a second message from the terminal device, where the second message is used to request establishing a first session; and The processing unit is further configured to determine, based on the second message, that the first session belongs to a session corresponding to the unmanned aerial vehicle service.

23. Apparatus according to claim 21 or 22.

24. The transceiver unit further comprises: and transmitting a third message to a second device, wherein the third message is used to request restricting the non-unmanned aerial vehicle services of the terminal device.

24. Apparatus according to claims 21 to 23.

25. The transceiver unit further comprises: configured to receive first instruction information from the second device, where the first instruction information instructs releasing one or more sessions corresponding to the non-unmanned aerial vehicle service; When restricting the non-unmanned aerial vehicle service of the terminal device, the processing unit specifically: and configured to release the one or more sessions corresponding to the non-unmanned aerial vehicle service based on the first instruction information.

25. The apparatus of claim 24.

26. Restricting the non-unmanned aerial vehicle service of the terminal device includes releasing all or a portion of a session corresponding to the non-unmanned aerial vehicle service managed by the communication device, and the processing unit further: determining that N is greater than M, where N is the number of sessions corresponding to the non-unmanned aerial vehicle service managed by the communication device, and M is the number of sessions corresponding to the non-unmanned aerial vehicle service that are permitted to be established on the communication device when the terminal device executes the unmanned aerial vehicle service; and Determine to release H sessions corresponding to the non-unmanned aerial vehicle services, where H is a positive integer greater than or equal to (N-M); 25. The apparatus of any one of claims 21 to 24, configured to:

27. When the non-unmanned aerial vehicle service of the terminal device is restricted, the transceiver unit: sending second instruction information to the terminal device, where the second instruction information indicates that establishment of the session corresponding to the non-unmanned aerial vehicle service is prohibited; 27. The apparatus of any one of claims 21 to 26, configured to:

28. 28. The apparatus of claim 21, wherein the first control plane procedure comprises one or more of a primary authentication procedure, a de-registration procedure, a slice authentication procedure, or a secondary authentication procedure.

29. 29. The apparatus of claim 28, wherein when the first control plane procedure of the terminal device is restricted, the processing unit is specifically configured to suspend or terminate the first control plane procedure.

30. After suspending the first control plane procedure, the processing unit further: Start a first timer; determining that the terminal device satisfies the first condition while the first timer is running; and Terminating the first control plane procedure when the execution of the first timer expires.

30. The apparatus of claim 29, configured to:

31. The transceiver unit further comprises: receiving a fourth message from a third device, wherein the fourth message is used to request that the first control plane procedure be performed; and sending a fifth message to the third device, wherein the fifth message includes a reason for not performing the first control plane procedure; 31. The apparatus of claim 29 or 30, configured to:

32. When determining that the terminal device is in a flight state, the transceiver unit further: receiving third indication information from the access and mobility management function device, where the third indication information indicates that the terminal device is in a flight state; 32. The apparatus of any one of claims 21 to 31, configured to:

33. The transceiver unit further comprises: Sending a sixth message to the access and mobility management function network element, wherein the sixth message is used to obtain a status of the terminal device, and the status of the terminal device includes the flight status and / or non-flight status; 33. The apparatus of claim 32, configured to:

34. the communication device is an access and mobility management function device; When determining that the terminal device is in a flight state: The transceiver unit is configured to receive fourth indication information from a fourth device, where the fourth indication information indicates that the terminal device is in a flight state; or The processing unit is configured to determine that the terminal device is in a flight state based on mobility information of the terminal device and / or flight information of the terminal device.

32. Apparatus according to any one of claims 21 to 31.

35. the communication device is the terminal device; When determining that the terminal device is in a flight state, the processing unit is specifically configured to determine that the terminal device is in a flight state based on mobility information and / or fifth instruction information from an application layer, where the fifth instruction information instructs the terminal device to enter a flight mode.

32. Apparatus according to any one of claims 21 to 31.

36. The processing unit further comprises: determine that a second condition is satisfied, where the second condition is configured to include one or more of the following conditions: authorization for the unmanned aerial vehicle service is revoked from the terminal device, the terminal device is not authorized for the unmanned aerial vehicle service, the terminal device is deregistered for the unmanned aerial vehicle service, or the terminal device releases a last session corresponding to the unmanned aerial vehicle service; and the communication device is the first session management function device, and the transceiver unit is further configured to receive a seventh message from the terminal device and establish or modify a session corresponding to the non-unmanned aerial vehicle service based on the seventh message, where the seventh message is used to request the establishment or modification of the session corresponding to the non-unmanned aerial vehicle service; or The communication device is the short message service service center, and the transceiver unit is further configured to send an eighth message to the terminal device, where the eighth message is used to request establishing or modifying a session corresponding to the non-unmanned aerial vehicle service; or the communication device is the terminal device, and the transceiver unit is further configured to send an eighth message to the first session management function device, where the eighth message is used to request establishing or modifying a session corresponding to the non-unmanned aerial vehicle service.

36. Apparatus according to any one of claims 21 to 35.

37. The processing unit further comprises: determine that the second condition is satisfied, where the second condition is configured to include one or more of the following conditions: authorization for the unmanned aerial vehicle service is revoked from the terminal device, the terminal device is not authorized for the unmanned aerial vehicle service, the terminal device is deregistered for the unmanned aerial vehicle service, or the terminal device releases the last session corresponding to the unmanned aerial vehicle service; The transceiver unit is further configured to: receive the fourth message from the third device, where the fourth message is used to request performing the first control plane procedure; and the processing unit is further configured to execute the first control plane procedure.

37. Apparatus according to any one of claims 21 to 36.

38. A communication device comprising a processing unit and a transceiver unit, The transceiver unit is configured to receive a message from a first session management function device, the message being used to request restricting non-unmanned aerial vehicle services of the terminal device; The processing unit is configured to determine, based on the message, that a second session management function device manages a session corresponding to the non-unmanned aerial vehicle service of the terminal device; and The transceiver unit is further configured to send instruction information to the second session management function device, where the instruction information instructs the second session management function device to release all or part of the session corresponding to the non-unmanned aerial vehicle service managed by the second session management function device, and / or instructs the second session management function device to prohibit establishment or modification of the session corresponding to the non-unmanned aerial vehicle service. Communication equipment.

39. The transceiver unit further comprises:

39. The apparatus of claim 38, configured to send first instruction information to the first session management function device, wherein the first instruction information instructs releasing one or more sessions corresponding to the non-unmanned aerial vehicle service.

40. The transceiver unit further comprises: configured to receive N from the first session management function device, where N is the number of sessions corresponding to the non-unmanned aerial vehicle service managed by the first session management function device; and 40. The apparatus of claim 39, wherein the processing unit is further configured to: determine that the first session management function device needs to release one or more sessions corresponding to the non-unmanned aerial vehicle service based on N and M, the number of sessions corresponding to the non-unmanned aerial vehicle service established by the terminal device, where M is the number of sessions corresponding to the non-unmanned aerial vehicle service that are allowed to be established on the first session management function device when the terminal device executes the unmanned aerial vehicle service.

41. A communications device comprising one or more processors and a memory, the one or more processors coupled to the memory; the memory configured to store a computer program; The one or more processors are configured to execute the computer program stored in the memory, such that the communication device executes the method of any one of claims 1 to 17 or executes the method of any one of claims 18 to 20. Communication equipment.

42. A chip coupled to a memory and configured to read and execute program instructions stored in said memory to perform the method of any one of claims 1 to 17 or to perform the method of any one of claims 18 to 20.

43. 21. A computer-readable storage medium comprising a program or instructions, wherein when said program or said instructions are run on a computer, the method of any one of claims 1 to 17 is performed, or the method of any one of claims 18 to 20 is performed.

44. A communication system comprising a first device configured to perform the method of any one of claims 1 to 17 and / or a second device configured to perform the method of any one of claims 18 to 20.

45. A computer program product comprising a program or instructions, wherein when said program or instructions are run on a computer, the method of any one of claims 1 to 17 is performed or the method of any one of claims 18 to 20 is performed.

46. determining, by a first device, that a first condition is met, restricting a non-unmanned aerial vehicle service of a terminal device and / or restricting a first control plane procedure of the terminal device, and sending a third message to a second device, where the first control plane procedure is not specific to the unmanned aerial vehicle service, and the third message is used to request restricting the non-unmanned aerial vehicle service of the terminal device, and the first condition includes one or more of the following conditions: the terminal device is authorized for the unmanned aerial vehicle service, the terminal device initiates establishment of a first session corresponding to the unmanned aerial vehicle service, or the terminal device is in an airborne state; and receiving, by the second device, the third message and sending instructional information to a second session management function device, wherein the second session management function device is a device determined based on the third message to be configured to manage a session corresponding to the non-unmanned aerial vehicle service of the terminal device; A communication method comprising:

47. The method further comprises: receiving, by the second session management function device, the instruction information and, based on the instruction information, releasing all or a portion of the session corresponding to the non-unmanned aerial vehicle service managed by the second session management function device and / or prohibiting establishment or modification of the session corresponding to the non-unmanned aerial vehicle service.

47. The method of claim 46, comprising:

48. receiving, by a second device, a third message from the first device, wherein the third message is used to request restricting the non-unmanned aerial vehicle services of the terminal device; determining, by the second device, based on the third message, that a second session management function device will manage a session corresponding to the non-unmanned aerial vehicle service of the terminal device, and sending indication information to the second session management function device; and receiving, by the second session management function device, the instruction information and, based on the instruction information, releasing all or a portion of the session corresponding to the non-unmanned aerial vehicle service managed by the second session management function device and / or prohibiting establishment or modification of the session corresponding to the non-unmanned aerial vehicle service. A communication method comprising:

49. A communication system comprising a first device and a second device, The first device: determine that a first condition is met, restrict a non-unmanned aerial vehicle service of a terminal device and / or restrict a first control plane procedure of the terminal device, and send a third message to a second device, where the first control plane procedure is not specific to the unmanned aerial vehicle service, and the third message is used to request restricting the non-unmanned aerial vehicle service of the terminal device, and the first condition is configured to include one or more of the following conditions: the terminal device is authorized for the unmanned aerial vehicle service, the terminal device initiates establishment of a first session corresponding to the unmanned aerial vehicle service, or the terminal device is in an airborne state; and The second device: receive the third message and send instruction information to a second session management function device, where the second session management function device is configured to manage a session corresponding to the non-unmanned aerial vehicle service of the terminal device, the second session management function device being a device determined based on the third message. Communication system.

50. 50. The system of claim 49, further comprising: the second session management function device configured to receive the instruction information and, based on the instruction information, release all or a portion of the session corresponding to the non-unmanned aerial vehicle service managed by the second session management function device and / or prohibit establishment or modification of the session corresponding to the non-unmanned aerial vehicle service.

51. A communication system comprising a second device and a second session management function device, The second device: receiving a third message from the first device, wherein the third message is used to request restricting the non-unmanned aerial vehicle services of the terminal device; Determine, based on the third message, that the second session management function device manages a session corresponding to the non-unmanned aerial vehicle service of the terminal device; and Sending instruction information to the second session management function device configured to: The second session management function device: receiving the instruction information; and Based on the instruction information, release all or part of the session corresponding to the non-unmanned aerial vehicle service managed by the second session management function device, and / or prohibit establishment or modification of the session corresponding to the non-unmanned aerial vehicle service. It is configured as follows: Communication system.

Images