WO2024001782A1 - 一种通信方法及装置 - Google Patents

一种通信方法及装置 Download PDF

Info

Publication number
WO2024001782A1
WO2024001782A1 PCT/CN2023/100183 CN2023100183W WO2024001782A1 WO 2024001782 A1 WO2024001782 A1 WO 2024001782A1 CN 2023100183 W CN2023100183 W CN 2023100183W WO 2024001782 A1 WO2024001782 A1 WO 2024001782A1
Authority
WO
WIPO (PCT)
Prior art keywords
uav
message
terminal device
session
service
Prior art date
Application number
PCT/CN2023/100183
Other languages
English (en)
French (fr)
Inventor
雷中定
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP23829964.8A priority Critical patent/EP4539525A4/en
Publication of WO2024001782A1 publication Critical patent/WO2024001782A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/02—Access restriction performed under specific conditions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/12—Detection or prevention of fraud
    • H04W12/121—Wireless intrusion detection systems [WIDS]; Wireless intrusion prevention systems [WIPS]
    • H04W12/122—Counter-measures against attacks; Protection against rogue devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/12—Detection or prevention of fraud
    • H04W12/126—Anti-theft arrangements, e.g. protection against subscriber identity module [SIM] cloning

Definitions

  • the present application relates to the field of communication technology, and in particular, to a communication method and device.
  • the unmanned/uncrewed aerial system includes an unmanned/uncrewed aerial vehicle (UAV) and a UAV remote controller (UAV controller, UAVC).
  • UAV unmanned/uncrewed aerial vehicle
  • UAV controller UAV controller
  • UAVC UAV remote controller
  • the remote control of the drone may be referred to as a remote control or remote control device, etc.
  • the drone can fly autonomously or according to the control instructions of the remote controller. That is, communication can be carried out between the drone and the remote controller.
  • the remote controller can send control instructions to the drone, so that the drone sends the captured photos or videos to the remote controller after taking aerial photography.
  • UAV systems can be combined with mobile communication networks to make full use of the advantages of mobile communication networks, such as wide-area coverage, high reliability, and support for high-speed mobile services, and expand UAV systems to achieve beyond-line-of-sight (long-range) high-speed Reliable flight, thus enabling UAV systems to gain wider applications and markets. That is, the drone has two roles at the same time: one is a terminal in the mobile communication network, and the other is a drone that can fly in the drone system.
  • mobile communication networks can not only provide UAVs with services enjoyed by ordinary terminals (such as multimedia communications, data services, etc.), but also provide UAVs with UAV-specific services (such as remote positioning, no-fly fence, etc.).
  • drones face the following problems:
  • DoS denial of service
  • the drone sends a large amount of non-drone business data, maliciously occupying the drone's resources (such as network resources, computing resources, battery resources, etc.), affecting the normal operation of the drone, causing the drone to deviate from the route and fail to reach its intended destination. address, even causing problems such as the drone crashing. Therefore, how to reduce attackers’ use of non-drone services to attack drones is an issue that needs to be solved urgently.
  • Embodiments of the present application provide a communication method and device to reduce attacks on drones by attackers using non-drone services and improve the security of drones.
  • the present application provides a communication method, which may be executed by a first device or by a component (such as a chip) of the first device.
  • the first device determines that the first condition is met, and the first condition includes one or more of the following conditions: the terminal device is authorized to operate the drone service, and the terminal device initiates the establishment of the first described A session corresponding to the drone service, or the terminal device is in a flight state; the first device restricts the non-drone business of the terminal device and/or restricts the first control plane process of the terminal device, wherein, The first control plane process is not a process exclusive to the UAV business.
  • the first device conditionally restricts the non-drone services of the terminal device to reduce the number of attackers. Use non-UAV services to attack terminal equipment to improve the security of terminal equipment.
  • the first device conditionally limits the first control plane process of the terminal device, releasing resources required to execute the first control plane process, thereby providing more usable resources for the UAV business.
  • the terminal device is authorized to perform drone services, it means that the terminal device supports the simultaneous execution of drone services and non-drone services.
  • the first device limits the non-drone services of the terminal device and can Reduce attackers' use of non-UAV services to attack terminal devices and prevent non-UAV services from invading UAV business resources.
  • the terminal device is authorized for the drone service, the first device can restrict the first control plane process and release the resources required to execute the first control plane process, thereby reserving more authorized drones for the terminal device. Resources available for machine business.
  • the terminal device initiates the establishment of a session corresponding to the first drone service, which means that the terminal device will perform the drone service.
  • the first device restricts the non-drone business of the terminal device, which can reduce attacks.
  • the attacker uses non-UAV services to attack the terminal equipment while the terminal equipment is performing UAV services, and prevents non-UAV services from encroaching on the UAV business while the terminal equipment is performing UAV services. resource.
  • the terminal device initiates the establishment of a session corresponding to the first drone service, and the first device restricts the first control plane process, which can release the resources required to execute the first control plane process and increase the usability of the drone service.
  • the first device when the terminal device is in flight, the first device restricts non-UAV services of the terminal device, which can reduce attacks by attackers using non-UAV services to attack the terminal device in flight, and avoid occupying the terminal equipment due to non-UAV services.
  • the large amount of resources of the terminal equipment causes problems such as the terminal equipment deviating from the route and being unable to reach the expected destination address, etc., which improves the security of the terminal equipment.
  • the first device restricts the first control plane process, which can reserve more resources that can be used by the UAV business for the terminal device in flight, thus preventing the terminal device in flight from causing a terminal failure due to insufficient resources. Problems such as equipment not working properly or even crashing.
  • the first device limits the non-UAV services of the terminal device, which may 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 the sessions corresponding to the non-UAV services managed by the first device, and/or prohibits the establishment or modification of all Describe the sessions corresponding to non-drone services.
  • the first device is a short message service center, and the first device does not send or suspends sending the first message to the terminal device, and the first message is used to request the establishment or modification of the non-UAV.
  • the first device is the terminal device, and the first device does not send or suspends sending a first message to the first session management function device, and the first message is used to request the establishment or modification of the non-unmanned device.
  • the session corresponding to the machine service.
  • the first device can release the session corresponding to the non-UAV service, prohibit the establishment or modification of the session corresponding to the non-UAV service, or not send a request for establishment to the terminal device or the session management function device. Or modifying the session messages corresponding to non-UAV services and other measures to limit the non-UAV services of terminal devices, and the implementation method is flexible.
  • the method may further include: the first device receiving a second message from the terminal device, the second message being used to request Establishing a first session; and, based on the second message, the first device determines that the first session belongs to a session corresponding to the drone service.
  • the first device can determine whether the received session establishment request message is used to establish a session corresponding to the drone service. For example, the first session For a session corresponding to the drone service, the first device restricts the drone service and/or restricts the first control plane process. For another example, the first session belongs to the session corresponding to the non-UAV service, which means that the first device has released the session corresponding to the non-UAV service and/or the terminal device has not established the first session corresponding to the UAV service.
  • the resource Sufficient, in this case, the first device may not restrict non-UAV services and/or, thereby improving resource utilization while reducing the impact on UAV services.
  • the method may further include: the first device sending a third message to the second device, the third message being used to request restriction of the non-UAV business of the terminal device. .
  • the first device may send a third message to the second device, so that the second device limits the non-UAV services of the terminal device.
  • the method may further include: the first device receiving first indication information from the second device, the first indication information being used to indicate releasing one or more of the non- Session corresponding to drone business.
  • the first device may limit the non-UAV services of the terminal device by: the first device releases one or more sessions corresponding to the non-UAV services according to the first instruction information.
  • the first device restricting the non-UAV services of the terminal device includes the first device releasing all or part of the non-UAV services managed by the first device.
  • sessions corresponding to the service the method may further include: the first device determines that N is greater than M, where the N is the number of sessions corresponding to the non-UAV service managed by the first device, and the M is the number of sessions corresponding to the non-UAV services that the terminal device allows to establish at the first device when executing the UAV service; the first device determines to release H of the non-UAV services.
  • the H is a positive integer greater than or equal to (N-M).
  • the first device can release one or more sessions corresponding to non-UAV services according to the instruction information of the second device, or can also release one or more sessions corresponding to non-UAV services according to N and M.
  • Flexible implementation
  • the first device restricts the non-UAV business of the terminal device, which may be: the first device sends second instruction information to the terminal device, and the second instruction The information indicates that establishment of a session corresponding to the non-UAV service is prohibited.
  • the first device instructs the terminal device to prohibit the establishment of sessions corresponding to non-UAV services. This prevents the terminal device from initiating sessions corresponding to non-UAV services, thereby limiting the non-UAV services of the terminal device. the goal of.
  • the first control plane process includes one or more of a first authentication process, a de-registration process, a slice authentication process or a secondary authentication process.
  • the first device restricts the first control plane process of the terminal device, which may be: the first device suspends or terminates the first control plane process.
  • the first device can suspend or terminate the first control plane process.
  • the first control plane process is not a proprietary process of the drone business, so the suspension or termination of the first control plane process will not be detrimental to the drone. execution of the business, and can release the resources required to execute the first control plane process, thereby providing more available resources for the drone business, which is beneficial to the execution of the drone business.
  • the method further includes: the first device starts a first timer; the first device determines that the The terminal device satisfies the first condition during the running of the first timer; the first device terminates the first control plane process when the first timer ends.
  • the first device can first suspend the first control plane process. If the terminal device meets the first condition during the timer running period, the first device can terminate the first control plane process. If the terminal device does not meet the first condition during the period, the first device can execute the first control plane process.
  • the method may further include: the first device receiving a fourth message from a third device, the fourth message being used to request execution of the first control plane process; A device sends a fifth message to the third device, where the fifth message includes the reason for not performing the first control process.
  • the first device when the first device suspends or terminates the first control plane process, the first device can feed back to the third device the reason why the first control plane process is not executed.
  • the reason for not executing the first control plane process may be, for example, that the terminal device satisfies the first condition.
  • the first device determines that the terminal device is in a flight state, which may be: the first device receives third indication information from the access and mobility management function device, and the third indication The information indicates that the terminal device is in a flight state.
  • the first device sends a sixth message to the access and mobility management function network element, where the sixth message is used to obtain the status of the terminal device, and the status of the terminal device includes Flight status or/and non-flight status.
  • 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 may be actively pushed by the access and mobility management functional device, or may be obtained by the first device by subscribing to the status of the terminal device from the access and mobility management functional device.
  • the implementation method is flexible.
  • the first device is an access and mobility management function device; the first device determines that the terminal device is in a flight state, specifically: the first device receives a message from a fourth device.
  • the fourth indication information is used to indicate that the terminal device is in a flight state; or, the first device determines according to the movement information of the terminal device and/or the flight information of the terminal device.
  • the terminal device is in flight state.
  • the access and mobility management function device can obtain from the fourth device that the terminal device is in the flight state, and can also determine that the terminal device is in the flight state based on the movement information and/or flight information of the terminal device.
  • the implementation method is flexible.
  • the first device is the terminal device; the first device determines that the terminal device is in a flight state, which may be: the first device determines that the terminal device is in a flight state based on movement information and/or information from the application layer.
  • the fifth indication information determines that the terminal device is in a flight state, wherein the fifth indication information instructs the terminal device to enter the flight mode.
  • the terminal device can determine whether it is in a flight state.
  • 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: the terminal device is revoked Authorization of the drone service, the terminal device is not authorized to the drone service, the drone service of the terminal device is de-registered, or the terminal device releases the last drone The session corresponding to the machine service;
  • the first device is a first session management function device, the first device receives the seventh message from the terminal device, and establishes or modifies the session corresponding to the non-UAV service according to the seventh message, Wherein, the seventh message is used to request the establishment or modification of a session corresponding to the non-UAV service;
  • the first device is a short message service center, and the first device sends an eighth message to the terminal device, where the eighth message is used to request the establishment or modification of a session corresponding to the non-UAV service. ;
  • the first device is the 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 the establishment or modification of the non-UAV service corresponding to the session.
  • the first device when the first device determines that the second condition is met, the first device cancels the configuration of the terminal.
  • the restrictions on non-UAV services of the equipment enable the first device to perform non-UAV services and improve compatibility.
  • 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: the terminal device is revoked Authorization of the drone service, the terminal device is not authorized to the drone service, the drone service of the terminal device is de-registered, or the terminal device releases the last drone session corresponding to the machine service; the first device receives a fourth message from the third device, the fourth message is used to request execution of the first control plane process; the first device executes the first control plane process process.
  • the first device when the first device determines that the second condition is met, the first device cancels the restriction on the first control plane process, so that the first device can execute the first control plane process, which can improve compatibility.
  • the present application provides a communication method, which can be executed by a second device or by a component (such as a chip) of the second device.
  • the second device receives a message from the first session management function device requesting to limit the non-drone services of the terminal device; the second device determines the second session management function based on the message
  • the device manages a session corresponding to the non-UAV service of the terminal device; the second device sends indication information to the second session management function device, wherein the indication information is used to instruct release of the second session
  • the management function device manages all or part of the sessions corresponding to the non-UAV services, and/or instructs that establishment or modification of the sessions corresponding to the non-UAV services is prohibited.
  • the second device responds to a message restricting the non-UAV service of the terminal device, determines the session management function device that manages the session corresponding to the non-UAV service of the terminal device, and provides the session management function to the session management device.
  • the functional device sends instruction information to instruct the session management functional device to restrict the non-UAV business of the terminal device, thereby reducing attackers' use of non-UAV services to attack UAVs and preventing non-UAV services from encroaching on UAVs. Machine business resources.
  • the method may further include: the second device sending first indication information to the first session management function device, the first indication information being used to indicate releasing one or more non- Session corresponding to drone business.
  • the method may further include: the second device receiving N from the first session management function device, where the N is managed by the first session management function device.
  • the number of sessions corresponding to the non-UAV service ; the second device determines the first value based on the number of sessions corresponding to the non-UAV service established by the terminal device, the N and M
  • the session management function device needs to release one or more sessions corresponding to the non-UAV service, where M is the number of sessions allowed by the terminal device when executing the UAV service.
  • the second device can maintain the number of sessions corresponding to the non-drone services that have been established by the terminal device, and determine each session in one or more session management function devices corresponding to the terminal device in combination with N and M. The number of sessions corresponding to non-UAV services that need to be released by the management function device.
  • the present application provides a communication device.
  • the communication device is configured to perform the method described in the above first aspect and any possible implementation manner of the first aspect.
  • the communication device is, for example, a first device, or a functional module in the first device, such as a baseband device or a chip system.
  • the communication device includes a baseband device and a radio frequency device.
  • the communication device includes a processing unit (sometimes also called a processing module) and a transceiver unit (sometimes also called a transceiver module).
  • the transceiver unit can realize the sending function and the receiving function.
  • a sending unit sometimes also called a sending module
  • a receiving unit sometimes also called a sending module
  • receiving module The sending unit and the receiving unit can be the same functional unit, which is called the sending and receiving unit. This functional unit can realize the sending function and the receiving function; or, the sending unit and the receiving unit can be different functional units, and the sending and receiving unit is a general term for these functional units.
  • the present application provides a communication device.
  • the communication device is configured to perform the method described in the above second aspect and any possible implementation manner of the second aspect.
  • the communication device is, for example, a second device, or a functional module in the second device, such as a baseband device or a chip system.
  • the communication device includes a baseband device and a radio frequency device.
  • the communication device includes a processing unit (sometimes also called a processing module) and a transceiver unit (sometimes also called a transceiver module).
  • the transceiver unit can realize the sending function and the receiving function.
  • a sending unit sometimes also called a sending module
  • a receiving unit sometimes also called a sending module
  • receiving module sometimes also called a sending module
  • the sending unit and the receiving unit can be the same functional unit, which is called the sending and receiving unit, and the functional unit can realize the sending function and the receiving function; or the sending unit and the receiving unit can be different functional units, and the sending and receiving unit is responsible for these functions.
  • the present application provides a communication device.
  • the communications device may include one or more processors.
  • the communication device may also include a memory.
  • the memory is used 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, so that the communication device executes the first aspect and any of the possible implementations of the first aspect. method described.
  • the present application provides a communication device.
  • the communications device may include one or more processors.
  • the communication device may also include a memory.
  • the memory is used 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, so that the communication device executes the second aspect and any of the possible implementations of the second aspect. method described.
  • the present application provides a communication system.
  • the communication system includes the communication device described in the fifth aspect, and/or the communication device described in the sixth aspect.
  • the present application provides a computer-readable storage medium, which is used to store computer programs or instructions that, when executed, make any one of the above-mentioned aspects possible.
  • the method described in the implementation manner is implemented, or the method described in the above second aspect and any possible implementation manner of the second aspect is implemented.
  • the present application provides a computer program product containing instructions, which, when run on a computer, enables the method described in the above first aspect and any possible implementation of the first aspect to be implemented, or causes The method described in the above second aspect and any possible implementation manner of the second aspect is implemented.
  • the present application also provides a chip, which is coupled to a memory and used to read and execute program instructions in the memory, so that the device where the chip is located implements the above first aspect and any of the first aspects.
  • a chip which is coupled to a memory and used to read and execute program instructions in the memory, so that the device where the chip is located implements the above first aspect and any of the first aspects.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • Figure 1 is a schematic diagram of the network architecture
  • Figure 2 is another schematic diagram of the network architecture
  • Figure 3 is a schematic diagram of drone business and non-drone business
  • Figure 4 is a schematic flow chart of a communication method provided by an embodiment of the present application.
  • Figure 5 is another schematic flow diagram of a communication method provided by an embodiment of the present application.
  • Figure 6 is another schematic flowchart of a communication method provided by an embodiment of the present application.
  • Figure 7 is another schematic flow diagram of a communication method provided by an embodiment of the present application.
  • Figure 8 is another schematic flow diagram of a communication method provided by an embodiment of the present application.
  • Figure 9 is another schematic flow diagram of a communication method provided by an embodiment of the present application.
  • Figure 10 is a schematic flowchart of yet another communication method provided by an embodiment of the present application.
  • FIG 11 is a schematic flowchart of yet another communication method provided by an embodiment of the present application.
  • Figure 12 is a schematic flowchart of yet another communication method provided by an embodiment of the present application.
  • Figure 13 is a schematic flowchart of yet another communication method provided by an embodiment of the present application.
  • Figure 14 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • Figure 15 is another structural schematic diagram of a communication device provided by an embodiment of the present application.
  • Terminal equipment also known as user equipment (UE), access terminal, terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile equipment, user terminal, user Agent or user device, etc.
  • the terminal device may be, for example, a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a smart phone, a mobile phone, a wireless local loop (WLL) ) website, personal digital assistant (PDA), etc.
  • SIP session initiation protocol
  • WLL wireless local loop
  • PDA personal digital assistant
  • the terminal device can also be a handheld device with wireless communication capabilities, a computing device or other device connected to a wireless modem, a vehicle-mounted device, a wearable device, a drone or the Internet of Things, a terminal in the Internet of Vehicles, a 5G network and in the future Any form of terminal in the network, relay user equipment or terminals in the future evolved 6G network, etc.
  • the embodiments of the present application do not limit the type or type of terminal equipment.
  • the functions of the terminal device may be implemented by hardware components inside the terminal device, and the hardware components may be processors and/or programmable chips inside the terminal device.
  • the chip can be implemented by an application-specific integrated circuit (ASIC) or a programmable logic device (PLD).
  • ASIC application-specific integrated circuit
  • PLD programmable logic device
  • the above-mentioned PLD can be a complex programmable logical device (CPLD), a field-programmable gate array (FPGA), a general array logic (GAL), a system on a chip (system on a chip) , SOC) or any combination thereof.
  • CPLD complex programmable logical device
  • FPGA field-programmable gate array
  • GAL general array logic
  • SOC system on a chip
  • the following introduction takes the terminal device as a drone as an example.
  • Drone business refers to the business or services exclusively for drones enjoyed by drones.
  • the UAV service may be a communication service provided by the network for UAVs on the control plane and/or the user plane. or services.
  • the drone business can be a drone-specific or control plane process specifically used for drones (such as drone certification, authorization, or flight route authorization, etc.), command and control (C2) Communication, remote identification of drones, remote positioning, no-fly fences, or flight map download services, etc.
  • C2 command and control
  • the types of drone services in the embodiments of the present application are not limited to this.
  • Non-drone services refer to services other than drone services, which can be understood as services enjoyed by ordinary terminal equipment.
  • the non-UAV service may be, for example, a multimedia communication service, a data service or an Internet service, etc., but the embodiment of the present application is not limited to this type of non-UAV service.
  • the network cannot identify the type of drone (for example, when identifying the drone as an ordinary terminal) or when there is no drone business authorized for the drone, the drone can be regarded as an ordinary terminal device.
  • the services provided by the network to the drone are non-drone services.
  • “plurality” means two or more.
  • “plurality” in the embodiments of this application can also be understood as “at least two”.
  • “At least one” can be understood as one or more, for example, one, two or more.
  • including at least one means including one, two or more, and it does not limit which ones are included.
  • it includes at least one of A, B and C, then it can include A, B, C, A and B, A and C, B and C, or A and B and C.
  • “And/or” describes the relationship between related objects, indicating that there can be three relationships.
  • a and/or B can mean: A exists alone, A and B exist simultaneously, and B exists alone.
  • the character "/" unless otherwise specified, generally indicates that the related objects are in an "or” relationship.
  • the terms “system” and “network” in the embodiments of this application may be used interchangeably.
  • ordinal numbers such as “first" and "second” mentioned in the embodiments of this application are used to distinguish multiple objects and are not used to limit the order, timing, priority or importance of multiple objects.
  • first device, the second device, the third device and the fourth device involved in the embodiments of the present application are used to distinguish multiple devices and do not limit the priority or importance of the multiple devices.
  • first message, second message, third message, fourth message, etc. involved in the embodiment of the present application are used to distinguish multiple messages and do not limit the order, timing, priority or importance of the multiple messages. degree.
  • the word "exemplary” is used to mean an example, illustration or explanation. Any embodiment or design described herein as “exemplary” is not intended to be construed as preferred or advantageous over other embodiments or designs. Rather, the use of the word “exemplary” is intended to present the concept in a concrete manner.
  • PLMN public land mobile network
  • MNO mobile network operators
  • 3GPP 3rd generation partnership project
  • 3GPP networks usually include but are not limited to fifth-generation mobile communications (5th-generation, 5G) networks (referred to as 5G networks), fourth-generation mobile communications (4th-generation, 4G) networks (referred to as 4G networks), and other future communication systems Such as 6G network, etc.
  • 5G networks fifth-generation mobile communications
  • 4th-generation, 4G networks fourth-generation mobile communications
  • 6G networks 6th-generation networks
  • 6G networks 6th-generation network
  • Figure 1 is a schematic diagram of a network architecture according to an embodiment of the present application. It takes the 5G network architecture based on service-based architecture in the non-roaming scenario defined in the 3GPP standardization process as an example.
  • the network architecture can include three parts, namely the terminal equipment part, the data network (DN) part and the PLMN part.
  • the terminal device part may include the terminal device 110, which can establish a connection with the operator network through an interface (such as N1, etc.) provided by the operator network, and use data and/or voice services provided by the operator network.
  • the terminal device 110 can also access the data network 120 through the operator network, and use the operator services deployed on the data network 120, and/or services provided by third parties.
  • the above-mentioned third party may be a service provider other than the operator's network and the terminal device 110, and may provide other data and/or voice services for the terminal device 110.
  • the specific manifestations of the above-mentioned third parties can be determined according to the actual application scenarios and are not limited here.
  • For an introduction to the terminal device 110 please refer to the introduction of the terminal device in the foregoing explanation of terminology section, and will not be described again here.
  • the data network 120 which may also be called a packet data network (PDN), is usually a network located outside the operator's network, such as a third-party network.
  • the operator's network can access multiple data networks 120, and a variety of services can be deployed on the data networks 120 to provide data and/or voice services to the terminal device 110.
  • the data network 120 can be a private network of a smart factory.
  • the sensors installed in the workshop of the smart factory can be the terminal devices 110.
  • the data network 120 is deployed with a control server of the sensor, and the control server can provide services for the sensor.
  • the sensor can communicate with the control server, obtain instructions from the control server, and transmit the collected sensor data to the control server according to the instructions.
  • the data network 120 may be an internal office network of a certain company, and the mobile phones or computers of the company's employees may be the terminal devices 110. The employees' mobile phones or computers may access information, data resources, etc. on the company's internal office network.
  • PLMN can include but is not limited to: network exposure function (NEF)131, network function repository function (NRF)132, policy control function (PCF)133, unified data management (unified data management (UDM) 134. Unmanned/uncrewed aerial system (UAS) 135. Authentication server function (AUSF) 136. Access and mobility management function (AMF) 137. Session management function (SMF) 138. User plane function (UPF) 139. (Radio) access network ((R)AN) 140. Application function function, AF) 141, network slice authentication and authorization function (network slice specific authentication and authorization function, NSSAAF) 142, etc.
  • the part other than the (wireless) access network 140 part may be called the core network (core network, CN) part.
  • AN 140 also called wireless (Radio) AN
  • the terminal device 110 To access the operator's network, the terminal device 110 first passes through the (R)AN 140, and then can connect to the service node of the operator's network through the (R)AN 140.
  • the access network device (RAN device) in the embodiment of this application is a device that provides wireless communication functions for the terminal device 110, and may also be called a network.
  • Equipment, RAN equipment includes but is not limited to: next generation node base station (gNB) in the 5G system, evolved node B (evolved node B, eNB) in the long term evolution (long term evolution, LTE), Radio network controller (RNC), Node B (NB), Base Station Controller (BSC), Base Transceiver Station (BTS), Home Base Station (e.g., home evolved nodeB, or home node B, HNB), base band unit (BBU), transmission point (transmitting and receiving point, TRP), transmitting point (transmitting point, TP), small base station equipment (pico), mobile switching center , or network equipment in future networks, etc.
  • gNB next generation node base station
  • eNB evolved node B
  • eNB long term evolution
  • RNC Radio network controller
  • NB Node B
  • BSC Base Station Controller
  • BTS Base Transceiver Station
  • HNB home evolved nodeB
  • BBU base band unit
  • TRP transmitting and receiving point
  • TP
  • access network equipment For convenience of description, in all embodiments of this application, the above-mentioned devices that provide wireless communication functions for the terminal equipment 110 are collectively called access network equipment or simply RAN or AN. It should be understood that this article does not limit the specific type of access network equipment.
  • the network opening function 131 is a control plane function provided by the operator to enable third parties to use services provided by the network.
  • the network opening function 131 can be NEF, as shown in Figure 1; in future communication systems, such as the 6G communication system, the network opening function 131 can still be NEF, or may have other names.
  • the application examples are not limiting.
  • the network storage function 132 is a control plane function provided by the operator and can be used to maintain real-time information of all network function services in the network.
  • the network storage function 132 may be an NRF, as shown in Figure 1; in a future communication system, such as a 6G communication system, the network storage function 132 may still be an NRF, or may have other names.
  • the application examples are not limiting.
  • the policy control function 133 is a control plane function provided by the operator. It supports a unified policy framework to govern network behavior, and provides policy rules and contract information related to policy decisions to other control functions.
  • the policy control function 133 may be a PCF, as shown in Figure 1; in a future communication system, such as a 6G communication system, the policy control function 133 may still be a PCF, or may have other names.
  • the application examples are not limiting.
  • Unified data management 134 is a control plane function provided by the operator. It is responsible for storing the user permanent identifier (subscriber permanent identifier, SUPI) and the publicly used subscription identifier (generic public subscription identifier) of the subscribed users in the operator's network. GPSI), credential and other information. SUPI is first encrypted during transmission, and the encrypted SUPI is called a hidden user subscription 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's network.
  • the contract users of the above-mentioned operator network can specifically be users who use services provided by the operator network, such as users who use China Telecom's mobile phone chip cards, or users who use China Mobile's mobile phone chip cards, etc.
  • the trust certificate of the above-mentioned contract user can be a long-term key stored in the mobile phone chip card or a small file stored in information related to the encryption of the mobile phone chip card, which can be used for authentication and/or authorization.
  • permanent identifiers, credentials, security contexts, authentication data (cookies), and information related to token verification/authentication and authorization are not distinguished or limited for the convenience of description. .
  • the unified data management 134 can be UDM, as shown in Figure 1; in future communication systems, such as the 6G communication system, the unified data management 134 can still be UDM, or may have other names.
  • the application examples are not limiting.
  • UAV system function 135 is a control plane function provided by the operator to serve the UAV system. It is responsible for opening the network's UAV business capabilities to external networks. For example, it can open UAV authentication/authorization services, UAV flight authorization service, pairing authorization of UAV and remote controller, UAV re-authentication/authorization/revocation, UAV location information report, UAV quality of service (QoS) control, As well as traffic filtering for command and control (C2) communications, etc.
  • UAV authentication/authorization services UAV flight authorization service
  • pairing authorization of UAV and remote controller For example, it can open UAV authentication/authorization services, UAV flight authorization service, pairing authorization of UAV and remote controller, UAV re-authentication/authorization/revocation, UAV location information report, UAV quality of service (QoS) control, As well as traffic filtering for command and control (C2) communications, etc.
  • QoS quality of service
  • C2 traffic filtering for command and control
  • Unmanned aerial vehicle system functions 135 may be generated by network open functions 131 An instance (instance), or a sub-function of the common network opening function 131, or it can be an independent function specifically used to provide UAV services, so it is usually marked as UAS NF/NEF, but the embodiment of this application does not It is not limited to this.
  • the authentication server function 136 is a control plane function provided by the operator, and is usually used for first-level authentication, that is, network authentication between the terminal device 110 (subscriber) and the PLMN. After receiving the authentication request initiated by the contracted user, the authentication server function 136 can authenticate and/or authorize the contracted user through the authentication information and/or authorization information stored in the unified data management 134, or generate the contracted user's profile through the unified data management 134. Authentication and/or authorization information. The authentication server function 136 may feed back authentication information and/or authorization information to the subscriber.
  • the authentication server function 136 may be AUSF, as shown in Figure 1; in future communication systems, such as a 6G communication system, the authentication server function 136 may still be AUSF, or may have other names.
  • the application examples are not limiting.
  • the access and mobility management function 137 is a control plane network function provided by the PLMN. It is responsible for the access control and mobility management of the terminal device 110 accessing the PLMN, including, for example, mobility status management, allocation of user temporary identities, authentication and authorization. User functions.
  • the access and mobility management function 137 can be an AMF, as shown in Figure 1; in a future communication system, such as a 6G communication system, the access and mobility management function 137 can still be an AMF. Or it may have other names, which are not limited by the embodiments of this application.
  • the session management function 138 is a control plane network function provided by the PLMN and is responsible for managing the protocol data unit (PDU) of the terminal device 110.
  • PDU session is a channel used to transmit PDU. Terminal devices need to transmit data to and from DN 120 through PDU session.
  • PDU sessions may be established, maintained, deleted, etc., by the session management function 138.
  • Session management function 138 includes session management (such as session establishment, modification and release, including tunnel maintenance between user plane function 139 and AN 140, etc.), selection and control of user plane function 139, service and session continuity (service and session continuity, SSC) mode selection, roaming and other session-related functions.
  • the session management function 138 may be SMF, as shown in Figure 1; in future communication systems, such as a 6G communication system, the session management function 138 may still be an SMF, or may have other names.
  • SMF Session Management Function
  • future communication systems such as a 6G communication system
  • the session management function 138 may still be an SMF, or may have other names.
  • the application examples are not limiting.
  • the user plane function 139 is a gateway provided by the PLMN to communicate with the data network DN 120.
  • User plane functions 139 include data packet routing and transmission, data packet detection, business usage reporting, quality of service (QoS) processing, legal interception, uplink data packet detection, downlink data packet storage and other user plane related functions.
  • QoS quality of service
  • the user plane function 139 can be UPF, as shown in Figure 1; in future communication systems, such as the 6G communication system, the user plane function 139 can still be UPF, or may have other names.
  • the application examples are not limiting.
  • Application function 141 is a control plane function that can be deployed by the operator or an external third party.
  • the application function 141 supports services such as traffic routing control, policy control function 133 interaction, and access network function opening by interacting with other network functions of the core network.
  • the application function 141 may be AF, as shown in Figure 1; in future communication systems, such as a 6G communication system, the application function 141 may still be AF, or may have other names.
  • This application implements Examples are not limited.
  • the network slice authentication and authorization function 142 is a control plane network function provided by the PLMN and is used to support slice authentication between the terminal device 110 and the data network 120 .
  • the network slice authentication and authorization function 142 can be NSSAAF, as shown in Figure 1; in future communication systems, such as the 6G communication system, the network slice authentication and authorization function NSSAAF can still be SMF, or there may be other
  • NSSAAF NSSAAF
  • SMF SMF
  • each network function in PLMN can be either a network element implemented on dedicated hardware, a software instance running on dedicated hardware, or an instance of a virtualized function on an appropriate platform, for example, the above-mentioned virtualization
  • the platform can be a cloud platform.
  • each network function in the PLMN can also be called a network element, functional entity or device.
  • the access and mobility management function can also be called the access and mobility management function network element, access and mobility management Functional entities or access and mobility management functional equipment, etc.
  • the session management function can also be called session management functional network elements, session management functional entities or session management functional equipment, etc., which will not be listed here.
  • the network functions in the PLMN shown in Figure 1 may also include other network functions.
  • the PLMN also includes unified data repository (UDR), etc. (not shown in Figure 1).
  • the PLMN includes Other network functions are not limited.
  • the names of the network functions shown in Figure 1 are only used as examples here, and are not used as a limitation on the network functions included in the network architecture to which the methods of the embodiments of the present application are applicable.
  • the names of devices that implement network functions in systems with different access technologies may be different, and the embodiments of this application do not limit this.
  • Nnef, Nnrf, Npcf, Nudm, Nausf, Namf, Nsmf, Nnssaaf, Naf, N1, N2, N3, N4, and N6 are interface serial numbers.
  • the meaning of the above interface serial number may refer to the meaning defined in the 3GPP standard protocol. This application does not limit the meaning of the above interface serial number.
  • the interface names between various network functions in Figure 1 are only examples. In specific implementations, the interface names of the system architecture may also be other names, and this application does not limit this.
  • the network architecture shown in Figure 1 does not constitute a limitation of the communication systems to which the embodiments of the present application can be applied.
  • the network architecture shown in Figure 1 is a 5G system architecture.
  • the technical solution provided by the embodiment of the present application can be applied not only to the 5G system, but also to the fourth generation mobile communication technology (the 4th generation, 4G) system. , such as LTE systems, or may also be applied to next-generation mobile communication systems or other similar communication systems, without specific limitations.
  • Figure 2 provides a schematic diagram of the combination of 5G mobile network and UAV system.
  • the network entity of UAS service suppliers (USS) 121 is added in Figure 2. It usually does not belong to the operator network, but is deployed in the third-party data network 120, but this application The embodiment is not limited to this.
  • the UAS service 121 communicates with the UAS function 135 of the 3GPP network via the N33 interface.
  • the UAV system service 121 can store UAS-related information, such as UAS authentication information. Based on this information, the UAV system service 121 can perform identity authentication, flight authorization, etc. on the UAS.
  • the UAS regulatory department can also supervise the operation of UAS through UAS system service 121 to ensure the safety of UAS flight control and public safety.
  • the UAV system service 121 can also establish channels with other regulatory or safety flight departments to obtain flight-related information.
  • the UAV system service 121 can not only communicate with the UAV/remote controller through the operator's network, but also have the function of remote control of the UAV flight, which is not limited here.
  • the UAS service 121 may also represent an UAS traffic management entity (UAS traffic management, UTM) or an entity that integrates USS and UTM, which is not limited by this application.
  • the UAV can play two roles at the same time: one is a terminal in the operator network (ie PLMN, or mobile communication network), and the other is A drone that can be flown in UAS.
  • the operator network can not only provide UAVs with the services enjoyed by ordinary terminals (such as multimedia communications, data services, Internet, etc.), but also provide UAVs with UAV-specific services.
  • Some services include drone type certification and authorization (including drone-specific certification, authorization, flight route authorization, etc.), C2 communications, remote identification of drones, remote positioning, no-fly fences, flight map downloads, etc.
  • services exclusive to drones are called drone services, and services that are not exclusive to drones are called non-drone services.
  • non-drone services are examples, please refer to the aforementioned terminology explanation section and will not be repeated here.
  • drones can play two roles at the same time, they are vulnerable to potential security risks of denial of service (DoS) attacks.
  • DoS denial of service
  • the attacker can use the drone's non-drone business to send a large amount of videos, Internet data, etc. unrelated to the drone business, to maliciously consume the drone's resources ( Network resources, computing resources, battery resources, etc.), occupying the resources required by the drone to perform drone services, thereby affecting the normal operation of the drone (such as delaying the drone's response to C2 communication instructions, rapid battery depletion, etc.), Safety accidents causing the drone to deviate from its course, fail to arrive as expected, or even crash.
  • Network resources, computing resources, battery resources, etc. occupying the resources required by the drone to perform drone services, thereby affecting the normal operation of the drone (such as delaying the drone's response to C2 communication instructions, rapid battery depletion, etc.)
  • Figure 3 shows a schematic diagram of the relationship between PDU session and DN.
  • DN 1 is a DN specifically used for drone services and only supports sessions for drone services (PDU session 1).
  • DN 2 is a DN used for drone services and non-drone services. It supports both PDU sessions for drone services (PDU session 2) and PDU sessions for non-drone services (PDU session 3).
  • DN 3 is a DN exclusively used for non-UAV services and only supports PDU sessions for non-UAV services (PDU Session 4).
  • embodiments of the present application provide a communication method and device.
  • the first device determines that the conditions are met, the non-UAV business of the terminal device is restricted and/or the first control plane process of the terminal device is restricted.
  • the first control plane process is not a process exclusive to the UAV service.
  • the first condition includes that the terminal device is authorized for the UAV service, the terminal device initiates the establishment of a session corresponding to the first UAV service, or the terminal device is in At least one of the flight status.
  • the first device's conditional restriction of non-drone services of the terminal device can reduce attackers' use of non-drone services to attack the terminal device and prevent non-drone services from occupying the resources of the drone service.
  • the first device conditionally limits the first control plane process, releasing the resources required to execute the first control plane process, thereby reserving more usable resources for the UAV business, thereby preventing the terminal device from Insufficient resources cause terminal equipment to fail to work properly or even crash.
  • the embodiment of the present application takes the drone service and non-drone business of the terminal device as an example, and prevents the non-drone business from encroaching on the drone service by restricting the non-drone business and/or the first control plane process. resources for the human-machine business, and reserve more available resources for the drone business. It should be understood that the replacement of the UAV service with the first type of service of the terminal device and the replacement of the non-UAV service with the second type of service of the terminal device are also applicable to the embodiments of the present application. That is, the embodiment of the present application is not limited to the first type of business being drone business and the second type of business being non-drone business.
  • the first type of business is a business with high reliability and low latency requirements
  • the second type of business is a business with non-high reliability and non-low latency requirements.
  • the first type of service is a high-priority service
  • the second type of service is a low-priority service.
  • the first device may be a session management function device, a short message service-service center (SMS-SC), a terminal device, or a security anchor function (SEAF) device.
  • SMS-SC short message service-service center
  • SEAF security anchor function
  • equipment access and mobility management function equipment, unified data management equipment, authentication server function equipment, authentication credential repository and processing function (ARPF) equipment; or other devices that include the functions of one of the aforementioned devices device; or a component (such as a chip or functional module) in one of the aforementioned devices.
  • ARPF authentication credential repository and processing function
  • the specific implementation form of the first device in the embodiments of the present application is not limited to this.
  • the second device may be a unified data management device, a unified data storage device, or a policy control function device; or other devices that include the functions of one of the aforementioned devices; or a component (such as a chip or functional module) within one of the aforementioned devices,
  • the specific implementation form of the second device in the embodiment of the present application is not limited thereto.
  • the third device can be a security anchoring function device, an access and mobility management function device, a unified data management device, a network slicing authentication and authorization function device, an authentication, authorization and accounting server (authentication authorization and accounting-server, AAA-S) ), a data network; or other equipment that has the function of one of the foregoing devices; or a component (such as a chip or functional module) within one of the foregoing devices.
  • the specific implementation form of the third device in the embodiment of the present application is not limited to this.
  • the fourth device may be a terminal device, an access network device, an unmanned aerial vehicle system service, or an unmanned aerial vehicle system functional device; or other equipment that has the function of one of the foregoing devices; or a component (such as a chip) within one of the foregoing devices. or functional module), the specific implementation form of the fourth device in the embodiment of the present application is not limited to this.
  • the session management function device is replaced by SMF
  • the short message service center is replaced by SMS-SC
  • the terminal device is replaced by UE
  • the security anchoring function device is replaced by SEAF.
  • replace the access and mobility management functional equipment with AMF replace the unified data management equipment with UDM
  • replace the authentication server functional equipment with AUSF replace the authentication credential storage and processing functional equipment with ARPF
  • replace the policy control function device with PCF replace the network slice authentication and authorization function device with NSSAAF
  • replace the authentication, authorization and accounting server with AAA-S replace the data network with DN
  • replace the access network Replace equipment with RAN UAS services with USS, UAS functional equipment with UAS NF/NEF or UAS NF, and application functional equipment with AF.
  • the embodiment of the present application can support multiple session management function devices to manage the session of the UE at the same time.
  • the embodiment of this application takes as an example that the first session management function device and the second session management function device can manage the session of the UE at the same time.
  • the first session management function device is replaced by SMF 1
  • the second session management function device is replaced by SMF 2.
  • the session involved in the embodiment of the present application may be a PDU session or other sessions.
  • the embodiment of the present application does not limit the specific implementation form of the session.
  • Figure 4 is a schematic flow chart of a communication method provided by an embodiment of the present application. As shown in Figure 4, the method may include the following content.
  • S401 The first device determines that the first condition is met.
  • the first condition includes one or more of the following conditions: the UE is authorized for the drone service, the UE initiates the establishment of a session corresponding to the first drone service, or the UE is in a flight state.
  • the first device may determine that the UE is authorized for the drone service.
  • the drone service authorized by the UE can be understood as one or more of the registration authorization of the UE as a drone, the session authorization corresponding to the drone business, the pairing authorization or the flight authorization, but the embodiment of the present application is not limited to this.
  • the registration authorization of the UE as a drone can be understood as the UE obtaining authorization from the USS during the registration process as a drone.
  • the session authorization corresponding to the drone service can be understood as that the UE has obtained authorization from the USS during its session establishment or modification process as a drone.
  • Pairing authorization can be understood as the pairing relationship between the USS and the UE and the corresponding remote control.
  • Authorization is performed to allow the UE and the remote controller in a pairing relationship to communicate, for example, C2 information is transmitted between the UE and the remote controller. It should be understood that pairing authorization can be performed in the session establishment or modification process, or in other processes, and is not limited by this application.
  • Flight authorization refers to the USS authorizing flight-related information such as the UE's flight route, flight plan, etc. The flight authorization can be performed during the session establishment or modification process, or in other processes, and is not limited by this application.
  • the USS can notify the network of the authorization result indicating that the UE is authorized to the drone service, so the device in the network, such as the first device, can obtain the above authorization result.
  • the AMF initiates the authentication and authorization between the drone and the USS to the USS (via UAS NF) process.
  • the USS completes the authentication and authorization of the UE (that is, it completes the registration and authorization of the drone), and can send the authorization result indicating that the UE has been successfully registered and authorized as a drone to the UAS NF and/or AMF in the network.
  • the AMF or UAS NF can send the authorization result to the SMF. Therefore, the first device in the network (such as SMF, or AMF, etc.) can determine that the UE has obtained registration authorization from the USS based on the authorization result, and store the authorization result.
  • the SMF initiates to the USS (via UAS NF) the communication between the drone and the USS. Session authorization process for drone business.
  • the USS completes the session authorization for the UE and can send the authorization result to the UAS NF and/or SMF.
  • the SMF or UAS NF may send an authorization result indicating that the session corresponding to the UAV service is authorized to the AMF. Therefore, the first device (such as SMF, or AMF, etc.) can determine that the UE has obtained the drone session authorization of the USS based on the authorization result, and store the authorization result.
  • the SMF initiates to the USS (via UAS NF) the drone business between the drone and the USS. Session authorization process.
  • the USS determines whether to authorize the UE to pair with the corresponding remote control based on the pairing information in the message sent by the SMF or the pairing information stored by the USS, and sends the pairing authorization result to the UAS NF and/or SMF.
  • the SMF or UAS NF can send the results of the pairing authorization to the AMF. Therefore, the first device (such as SMF, or AMF, etc.) can determine that the UE has obtained the USS pairing authorization for the UE and its corresponding remote controller based on the result of the pairing authorization, and store the result of the pairing authorization.
  • the SMF initiates to the USS (via UAS NF) the drone business between the drone and the USS. Session authorization process.
  • the USS determines whether to authorize the UE's flight route (and/or flight plan) based on the UE's flight route information (and/or flight plan and other information), and sends the flight authorization result to the UAS NF and/or SMF.
  • the flight route and/or flight plan information may be information from the UE, or may be information stored in the USS, which is not limited in the embodiments of this application.
  • the SMF or UAS NF can send the results of the flight authorization to the AMF. Therefore, the first device (such as SMF, or AMF, etc.) can determine that the UE has obtained flight authorization for the UAV from the USS based on the result of the flight authorization, and store the result of the flight authorization.
  • the authorization process involved above may be a process initiated by the network side (such as AMF, or SMF, etc.); or it may also be a process initiated by the USS, which is not limited in this application.
  • the above-mentioned pairing authorization and flight authorization are performed during the session establishment or modification process as an example, but the embodiments of the present application are not limited thereto.
  • the pairing authorization and flight authorization can also be performed during the registration process.
  • the above description serves as an example to illustrate the specific implementation process of the first device determining that the UE is authorized to have drone services.
  • the embodiment of the present application is not applicable to the first device to determine that the UE is authorized to have drone services.
  • the specific methods and procedures for authorized drone business are not limited to Set on this.
  • the first device may determine that the UE initiates the establishment of a session corresponding to the first drone service.
  • the first device is SMF 1
  • SMF 1 can determine whether the UE initiates the establishment of a session corresponding to the first drone service based on the stored information of the UE (such as the context information of the UE, etc.).
  • the context information of the UE may include sessions corresponding to different services that the UE has established.
  • SMF 1 receives a message from the UE for requesting the establishment of a session (for example, recorded as a second message, the second message is used to request the establishment of the first session); SMF 1 can determine whether the first session is based on the context information of the UE.
  • the session corresponding to the first drone service of this UE may determine whether the first session belongs to the session corresponding to the UAV service, and if it is determined that the first session belongs to the session corresponding to the UAV service, then determine whether the first session belongs to the session corresponding to the UAV service according to the context information of the UE. It is the session corresponding to the first drone service of the UE. For example, the first session belongs to a session not corresponding to the drone service, or the first session belongs to a session corresponding to the drone service but the context information of the UE includes other sessions corresponding to the drone service, SMF 1 can determine the second message It is not a message used to establish the session corresponding to the first drone service.
  • the first session belongs to the session corresponding to the drone service, and the context information of the UE does not include the session corresponding to the drone service.
  • SMF 1 can determine that the second message is used to request the establishment of the first drone of the UE.
  • the session corresponding to the service means that it is determined that the UE initiates the establishment of the session corresponding to the first drone service.
  • SMF 1 may determine whether the first session belongs to a session corresponding to the drone service. For example, SMF 1 can determine whether the first session belongs to the session corresponding to the drone service according to the second message.
  • the second message may include one or more of the following information: UE type indication information, UAV identification (identity, ID), data network name (DN name, DNN), USS address information, USS ID, single network slice selection Auxiliary information (single network slice selection assistance information, S-NSSAI) identification, AF ID, or session service type, etc. It should be understood that this information may be included in the second message and sent to SMF 1, or may be included in other messages and sent to SMF 1, which is not limited in the embodiment of this application. This information is introduced below.
  • UE type indication information which can indicate whether the UE is a drone or an ordinary UE.
  • the second message includes the type indication information of the UE, and the type indication information of the UE indicates that the UE is a drone.
  • SMF 1 can determine that the first session belongs to the session corresponding to the drone service.
  • the second message includes the type indication information of the UE, and the type indication information of the UE indicates that the UE is an ordinary UE. Based on the second message, SMF 1 can determine that the first session belongs to a session corresponding to the non-UAV service.
  • UAV ID which can be the ID of the drone registered for the UE, or the ID assigned by the USS to the UE as the drone. If the second message includes the UAV ID, SMF 1 can determine based on the second message that the first session belongs to the session corresponding to the UAV service.
  • the DN can be a DN related to the drone service or a DN related to the non-drone service. This is not limited in the embodiment of the present application.
  • the second message includes a DNN, and the DN indicated by the DNN is a DN related to the drone service. Based on the second message, SMF 1 can determine that the first session belongs to the session corresponding to the drone service.
  • the second message includes a DNN, and the DN indicated by the DNN is a DN related to non-UAV services. SMF 1 can determine based on the second message that the first session belongs to a session corresponding to the non-UAV service.
  • USS address information or USS ID which can be used to indicate the USS serving the first session. If the second message includes USS address information and/or USS ID, SMF 1 can determine based on the second message that the first session belongs to the session corresponding to the UAV service.
  • the S-NSSAI identifier can be used to indicate the slice service type corresponding to the first session.
  • the slice service type can Whether it is a slicing service corresponding to a UAV service or a slicing service corresponding to a non-UAV service, the embodiment of the present application does not limit this.
  • the second message includes S-NSSAI, and the S-NSSAI indicates the slice service corresponding to the drone service. Based on the second message, SMF 1 can determine that the first session belongs to the session corresponding to the drone service.
  • the second message includes S-NSSAI, and the S-NSSAI indicates the slice service corresponding to the non-UAV service. Based on the second message, SMF 1 can determine that the first session belongs to the session corresponding to the non-UAV service.
  • AF ID can be used to indicate the AF corresponding to the establishment of the first session.
  • the AF can be an AF related to the drone service or an AF related to the non-drone service. This is not limited in the embodiment of the present application.
  • the second message includes an AF ID, and the AF indicated by the AF ID is an AF related to the drone service.
  • SMF 1 can determine that the first session belongs to the session corresponding to the drone service.
  • the second message includes an AF ID, and the AF indicated by the AF ID is an AF related to non-UAV services. SMF 1 can determine based on the second message that the first session belongs to a session corresponding to the non-UAV service.
  • the service type of the session can be used to indicate the service type corresponding to the first session.
  • the service type can be, for example, drone service, non-drone service, etc., which is not limited in the embodiment of this application.
  • the second message includes the service type of the session, and the service type of the session is used to indicate the drone service. Based on the second message, SMF 1 can determine that the first session belongs to the session corresponding to the drone service.
  • the second message includes the service type of the session, and the service type of the session is used to indicate the non-UAV service. Based on the second message, SMF 1 can determine that the first session belongs to the session corresponding to the non-UAV service.
  • SMF 1 can also determine whether the first session belongs to the session corresponding to the drone service based on the combination of the above information.
  • the second message includes DNN and S-NSSAI, and the combination of DNN and S-NSSAI indicates the drone service. Based on the second message, SMF 1 can determine that the first session belongs to the session corresponding to the drone service.
  • the second message includes DNN and S-NSSAI, and the combination of DNN and S-NSSAI indicates a non-UAV service. Based on the second message, SMF 1 can determine that the first session belongs to a session corresponding to the non-UAV service. .
  • SMF 1 can also determine whether the first session belongs to a session corresponding to the drone service based on the other two or more combinations of the above information. The embodiments of this application will not be listed one by one here.
  • the first device is SMF 1.
  • SMF 1 can determine whether the UE initiates the establishment of a session corresponding to the first drone service based on the UE information stored in SMF 1 (such as the context information of the UE, etc.).
  • the first device can also be SMF 2, or other SMF.
  • the relevant content of the first device being SMF 1, which will not be described again here.
  • the first device is not the SMF, and the first device can determine from the SMF whether the UE initiates the establishment of a session corresponding to the first drone service.
  • the first device may subscribe to the SMF for the session information of the UE, or send a message to the SMF for requesting the session information of the UE; after the SMF determines that the UE initiates the establishment of a session corresponding to the first UAV service, the SMF may The first device sends instruction information for instructing the UE to initiate the establishment of a session corresponding to the first UAV service; the first device receives the instruction information, and determines based on the instruction information that the UE initiates the establishment of a session corresponding to the first UAV service. session.
  • the first device determines that the UE is authorized for the drone service, and determines that the UE initiates the establishment of the first session corresponding to the drone service. Next, the first device determines that the UE is in the flight state.
  • the first device is a UE, and the first device may determine that the UE is in the flight state according to the mobility information, or according to the fifth indication information from the application layer, or according to the mobility information and the fifth indication information from the application layer.
  • the movement information may include height and/or movement speed.
  • the UE can measure its own horizontal height. If the measured horizontal height is greater than or equal to the height threshold, the UE can determine that it is in a flight state.
  • the height threshold may be preset, which is not limited in the embodiments of this application.
  • the UE can measure its own movement speed, If the measured movement speed is greater than or equal to the speed threshold, the UE can determine that it is in a flight state.
  • the speed threshold may be preset, which is not limited in the embodiments of the present application.
  • the fifth indication information may instruct the UE to enter flight mode.
  • the first device is an AMF, and the first device can maintain the status of the UE.
  • the state of the UE includes a flight state and/or a non-flight state.
  • the first device may acquire the status of the UE periodically or aperiodically.
  • the first device may receive fourth indication information from the fourth device, where the fourth indication information is used to indicate that the UE is in the flight state. Further, the first device may determine that the UE is in the flight state according to 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 for requesting the status of the UE. According to the embodiment of the present application There is no limit to this.
  • the first device may determine that the UE is in a flight state based on the UE's movement information, or based on the UE's flight information, or based on the UE's movement information and the UE's flight information.
  • the first device can obtain the mobility information of the UE from a base station, a gateway mobile location center (GMLC) or a location management function (LMF) device.
  • GMLC gateway mobile location center
  • LMF location management function
  • the first device determines that the UE is in a flying state; otherwise, the first device determines that the UE is in a non-flying state.
  • the first device may obtain the flight information of the UE from the USS.
  • the flight information may include flight paths, flight schedules, etc.
  • the first device may determine whether the current time and the UE's current location match the flight path and flight schedule. If the current time and the current position of the UE match the flight path and flight schedule, the first device determines that the UE is in the flight state; otherwise, the first device determines that the UE is in the non-flight state.
  • the first device may obtain the status of the UE from the AMF.
  • the first device may receive third indication information from the AMF, the third indication information indicating that the UE is in the flight state. Further, the first device may determine that the UE is in the flight state according to the third indication information.
  • the AMF may actively push the status of the UE to the first device, or the AMF may also send a message (such as the sixth message) sent by the first device for subscribing (or requesting) the status of the UE to the first device.
  • the status of the UE is sent, which is not limited in the embodiment of this application.
  • the first device restricts the non-UAV services of the UE and/or restricts the first control plane process of the UE.
  • the first device limits the non-UAV services of the UE, or limits the first control plane process of the UE, or limits the non-UAV services of the UE and limits the first control plane process of the UE.
  • the first device may limit the non-UAV services of the UE in one or more of the following ways.
  • the first device is SMF 1.
  • the first device releases the session corresponding to the non-UAV business of the UE managed by SMF 1, or prohibits (or refuses) the establishment or modification of the session corresponding to the non-UAV business of the UE. , or release the session corresponding to the non-UAV service of the UE managed by SMF1 and prohibit the establishment or modification of the session corresponding to the non-UAV service of the UE.
  • the first device may release sessions corresponding to all non-UAV services of the UE managed by SMF 1, or the first device may release sessions corresponding to part of the non-UAV services of the UE managed by SMF 1.
  • SMF 1 can actively trigger the release process of sessions corresponding to non-UAV services. For example, SMF 1 releases the IP address allocated to the session corresponding to the non-UAV service, or sends a session release message for releasing the session corresponding to the non-UAV service to the UPF so that the UPF releases the IP address corresponding to the non-UAV service. Session-related resources (such as discarding the remaining data packets corresponding to the session corresponding to the non-UAV business and releasing the corresponding tunnel resources and stored context, etc.).
  • SMF 1 notifies the corresponding AMF, so that the AMF releases the session-related resources (such as session ID, SMF ID, etc.) corresponding to the non-UAV business, and notifies AN to release the session-related resources corresponding to the non-UAV business.
  • session-related resources such as session ID, SMF ID, etc.
  • AN resources, etc. should be understood It should be noted that the specific implementation solution of SMF releasing sessions corresponding to non-UAV services in the embodiment of the present application is not limited to this.
  • the first device determines that N is greater than M, and determines to release all or part of the sessions corresponding to the non-UAV services of the UE managed by SMF 1.
  • N may be the number of sessions corresponding to the non-UAV services of the UE managed by SMF 1.
  • the first device may determine the N based on the context information of the UE stored in the first device, or obtain the N from UDM, UDR, or AMF. The method of obtaining N in the embodiment of the present application is not limited to this.
  • M may be the number of sessions corresponding to non-UAV services that the UE is allowed to establish at SMF 1 when performing UAV services.
  • the M may be preset, or configured in PCF, or obtained from UDM, UDR, or AMF.
  • the first device may determine to release H sessions corresponding to non-UAV services, where H may be a positive integer greater than or equal to (N-M).
  • the first device may prohibit the establishment of some or all of the sessions corresponding to non-UAV services of the UE (including prohibiting the modification of some of the sessions corresponding to the UAV services of the UE into sessions corresponding to non-UAV services) or It is prohibited to modify some or all of the sessions corresponding to non-UAV services of the UE.
  • the first device prohibits the establishment or modification of the session corresponding to the non-UAV service of the UE, which can be understood as the first device rejects the message from the UE requesting the establishment or modification of the session corresponding to the non-UAV service; or It is understood that the first device rejects the message from the UE for requesting to modify the session corresponding to the drone service to a session corresponding to the non-drone service; or it is understood that the first device does not respond or rejects the message from the AF for requesting establishment.
  • the first device does not respond or rejects the message from the AF requesting to modify the session corresponding to the UAV service to a session corresponding to the non-UAV service; or It is understood that the first device deletes or discards a message from the UE or AF for requesting to establish or modify a session corresponding to the non-UAV service; or it is understood that the first device deletes or discards a message from the UE or AF for requesting the establishment or modification of a session corresponding to the unmanned aerial vehicle service.
  • the session corresponding to the drone service is modified into a message corresponding to the session not corresponding to the drone service, etc.
  • the first device receives a message from the UE or AF requesting to establish or modify a session, and determines whether the session used in the message to request the establishment or modification belongs to a session corresponding to the UAV service. If the session used by this message to request establishment or modification belongs to the session corresponding to the UAV business (it should be noted that, according to the above understanding, modifying the session corresponding to the UAV business in this application also includes changing the session corresponding to the non-UAV business). The session is modified to a session corresponding to the drone service (which will not be repeated later), and the first device continues to perform the process of establishing or modifying the session according to the message.
  • modifying a session corresponding to a non-UAV service in this application also includes changing the session corresponding to the UAV service
  • the session is modified to a session corresponding to the non-UAV service (which will not be repeated later), and the first device rejects the request or does not respond to the message.
  • the first device For the first device to determine whether the session belongs to the session corresponding to the drone service, reference may be made to the relevant content of S401, which will not be described again here.
  • the first device is AMF, or other devices (such as UDM, PCF, etc.).
  • the first device triggers or notifies the SMF to release the sessions corresponding to all or part of the non-UAV services of the UE managed by the SMF, or prohibit (or refuse) the establishment or modification of the sessions corresponding to all or part of the non-UAV services of the UE.
  • the first device determines to limit the non-drone services of the UE, determines the SMF that manages the session of the UE (such as SMF 1 and/or SMF 2), and sends to the SMF all the information for releasing the UE managed by the SMF. Or some notification messages for sessions corresponding to non-UAV services.
  • the first device determines the SMF that manages the session corresponding to the non-UAV service of the UE, and sends the notification message to the SMF.
  • the specific implementation method of releasing the session corresponding to the non-UAV service of the UE please refer to the relevant description of the aforementioned method 1, and the steps will be repeated here.
  • Method 3 The first device is SMS-SC, and the first device does not send or suspends sending to the UE a session corresponding to the request to establish or modify the non-UAV service (for example, recorded as the first message).
  • the first message may be a short message, for example, but the embodiment of the present application does not limit the specific implementation form of the first message.
  • the first message may come from AF.
  • the AF can determine the need to establish or modify a session corresponding to the UE's non-UAV business based on the application requirements (such as actively pushing video, data, etc.
  • SMS- SC sends the first message (so that after SMS-SC receives the first message, it notifies the UE, and the UE sends a request message to establish or modify the session corresponding to the UE's non-UAV service); SMS-SC receives the first message Finally, it is determined that the first condition is met, and the first message is not sent to or is suspended from being sent to the UE.
  • Method 4 The first device is the UE, and the first device does not or suspends sending the first message to SMF 1.
  • the first message is used to request the establishment or modification of a session corresponding to the non-UAV service.
  • the AF can determine the need to establish or modify a session corresponding to the UE's non-UAV business based on application requirements (such as actively pushing video data, image data, etc. to the UE) or the UE's application requirements, and generate a session to trigger the UE to request the establishment Or modify the request message of the session corresponding to the UE's non-UAV service, and send the request message to SMS-SC; after receiving the request message, SMS-SC forwards the request message to the UE; the UE receives the request message Finally, it is determined that the first condition is met, and the first message is not or suspended from being sent to SMF 1. In this method, the first message is used to request the establishment or modification of a session corresponding to the non-UAV service.
  • application requirements such as actively pushing video data, image data, etc. to the UE
  • the UE's application requirements such as actively pushing video data, image data, etc. to the UE
  • the first device may send the second indication information to the UE.
  • the second indication information may indicate that establishing a session corresponding to non-UAV services is prohibited. In this way, the UE may not initiate the establishment or modification of the session corresponding to the non-UAV service according to the second indication information.
  • the first device restricts the non-UAV services of the UE.
  • the first control plane process of the first device restricting the UE is introduced.
  • the first control plane process is not unique to the drone business.
  • the first control plane process is not a process exclusive to the UAV business. It can be understood that the non-execution of the first control plane process will not have a negative impact on the UE's UAV business; or it can be understood as the non-execution of the first control plane process. It will not affect the normal execution of the UE's drone business; or it is understood that the first control plane process is not a necessary process for the normal execution of the UE's drone business; or it is understood that executing the first control plane process is not only detrimental to the UE's drone business.
  • executing the first control plane process is not only a necessary process for the normal execution of the UE's UAV business, but also a necessary process for the normal execution of the UE's non-UAV business.
  • the process, etc. are not limited by the embodiments of this application.
  • the first control plane process may include one or more of the following processes: a primary authentication process, a de-registration process, a slice authentication process, or a secondary authentication process, etc. This embodiment of the present application does not Limited to this.
  • the first device may limit the first control plane process by suspending or terminating the first control plane process.
  • the first device receives a fourth message from the third device, the fourth message is used to request execution of the first control plane process; the first device determines that the first condition is met, and may suspend or terminate the first control plane process.
  • the first device may send a fifth message to the third device, the fifth message including the reason for not performing (or not executing) the first control plane process.
  • the reason for not executing the first control plane process may be, for example, that the first condition is met or a timeout occurs, which is not limited in the embodiments of this application.
  • the first device can start the first timer and determine whether the UE satisfies the first condition during the running of the first timer (or at the end of the running). If the first device determines that the UE meets the first condition during the running of the first timer (or at the end of the running), the first device may terminate the first control plane process at the end of the first timer. If the first device determines that the UE does not meet the first condition during the running of the first timer, the first device may execute the first control plane process.
  • the first condition determined by the first device includes that the UE is authorized for the drone service and/or the UE is in a flight state. Further, the first device may also receive a third condition from the UE. Two messages, and It is determined whether the first session requested to be established by the second message belongs to the session corresponding to the drone service. Wherein, if the first device determines that the first session belongs to a session corresponding to the drone service, the first device can perform the content shown in S402; or, if the first device determines that the first session belongs to a session corresponding to the non-drone service, then The first device may not execute the content shown in S402. The first device determines whether the first session is a session corresponding to the drone service.
  • the first session requested to be established by the second message belongs to the session corresponding to the drone service, which means that the UE is about to perform the drone service.
  • the first device restricts the non-drone services of the UE and/or restricts the first control plane process of the UE, which can prevent non-drone services from occupying the resources of the drone business and prepare for the drone business. Leave more usable resources; or, the first session requested by the second message belongs to a session corresponding to a non-UAV service, which means that the UE has not yet executed the UAV service.
  • the first device allows Executing non-UAV services and allowing the execution of first control plane processes can improve resource utilization and improve compatibility.
  • the first condition determined by the first device includes that the UE is authorized for the drone service and/or the UE is in a flight state. Further, the first device may also receive a message from the UE. second message, and determine whether the first session requested by the second message belongs to a session corresponding to the UAV service. Wherein, the first device determines that the first session belongs to a session corresponding to the drone service, and the first device may not execute the content shown in S402. For another example, the first device determines that the first session belongs to a session corresponding to a non-UAV service, and the first device may reject the request to establish the first session. The first device determines whether the first session is a session corresponding to the drone service.
  • the first session requested to be established by the second message belongs to the session corresponding to the drone service.
  • the first device does not perform S402 , but when the first session belongs to a session corresponding to a non-UAV service, the first device will refuse to establish a session corresponding to the non-UAV service, so that it can execute the existing (or ongoing) session while executing the UAV service. Executing) non-UAV services and executing the first control plane process can improve resource utilization, while rejecting new sessions corresponding to non-UAV services can prevent attackers from using newly created non-UAV services to attack the UE.
  • the first condition determined by the first device includes that the UE is authorized for the drone service and/or the UE is in a flight state. Further, the first device may also receive a message from the UE. second message, and determine whether the first session requested to be established by the second message is a session corresponding to the first drone service initiated by the UE. For example, the first device may determine whether the first session is a session corresponding to the first drone service initiated by the UE according to the context information of the UE stored in the first device.
  • the first device may send a request to SMF, UDR or UDM to obtain information about whether the UE has established a session corresponding to the drone service. If yes, it can be determined that the first session is not the session corresponding to the first drone service initiated by the UE, otherwise it can be determined that the first session is the session corresponding to the first drone service initiated by the UE.
  • the first session is not the session corresponding to the first drone service initiated by the UE, which means that before the first device receives the first session establishment request (that is, when the first session corresponding to the drone service is established) , the session corresponding to the UE's non-UAV service has been released.
  • the first device does not need to repeatedly request to limit the non-UAV service and/or limit the first control plane process, thereby eliminating unnecessary message interaction. , improve resource utilization. That is, if the first device determines that the first session is not a session corresponding to the first drone service initiated by the UE, the first device may not perform the content shown in S402; or, the first device determines that the first session is initiated by the UE.
  • the first device can execute the content shown in S402.
  • the first device may send a request (or notification) to the second device to restrict the UE.
  • the non-UAV business message (for example, recorded as the third message) is to execute the content shown in S403.
  • S403 The first device sends the third message to the second device. Accordingly, the second device receives the third message.
  • the third message may be used to request (or notify) to limit the UE's non-UAV services.
  • S404 The second device determines that SMF 2 manages a session corresponding to the UE's non-UAV service.
  • the second device may determine the SMF that manages the session of the UE.
  • the second device determines the SMF that manages the session corresponding to the non-UAV service of the UE.
  • the second device may determine the SMF that manages the session of the UE or manages the non-UAV service of the UE based on the stored context information of the UE and/or based on the context information of the UE obtained from the UDM or UDR or PCF.
  • the SMF of the corresponding session may be determined.
  • the PCF may send a message for requesting the session information of the UE or the association information with the SMF to the UDM (or UDR); and receive the session information of the UE (including the association information with the SMF) from the UDM (or UDR) or the association information with the SMF. associated information.
  • the context information of the UE may include association information between the UE and the SMF.
  • the association information between the UE and the SMF may include the identity of the SMF that manages the session corresponding to the non-UAV service of the UE or the identity of the SMF that manages the session of the UE.
  • the association information between the UE and the SMF may also include the identification of the SMF that manages the session corresponding to the UE's drone service.
  • SMF 1 and SMF 2 simultaneously manage sessions with UE's non-UAV services as an example. Then in S404, the second device can determine that SMF 2 manages a session corresponding to the non-UAV service of the UE.
  • S405 The second device sends the sixth instruction information to SMF 2.
  • SMF 2 receives the sixth indication information.
  • the sixth instruction information is used to instruct to release the session corresponding to the non-UAV business of the UE managed by SMF 2, or to prohibit the establishment or modification of the session corresponding to the non-UAV business of the UE, or to instruct the release of SMF 2 management.
  • the sixth indication information may be used to instruct to release the sessions corresponding to all or part of the non-UAV services of the UE managed by SMF 2.
  • the first device determines to release all or part of the sessions corresponding to the non-UAV services of the UE managed by SMF 1.
  • the first device receives the first indication information from the second device, and releases the data corresponding to one or more non-UAV services of the UE managed by SMF 1 according to the first indication information. session.
  • the first indication information may indicate releasing one or more sessions corresponding to non-UAV services.
  • the second device determines the SMF that manages sessions corresponding to the UE's non-UAV services, and determines the number of sessions corresponding to the UE's non-UAV services released by the SMF.
  • the second device receives N from SMF 1, and determines that SMF 1 needs to release one or more non-drone services based on the number of sessions corresponding to the non-drone business established by the UE, N and M. Sessions corresponding to the service, or determine the number of sessions corresponding to the non-UAV service of the UE that SMF 1 needs to release (or to be released).
  • the first device can revoke restrictions on non-UAV services and/or revoke restrictions on the first control plane process. For example, if the first device determines that the second condition is met, the first device may revoke restrictions on non-UAV services and/or revoke restrictions on the first control plane process.
  • the first device is SMF 1.
  • the first device determines that the second condition is met, receives the seventh message from the UE, and establishes or modifies a session corresponding to the non-UAV service based on the seventh message.
  • the seventh message is used to Request to establish or modify a session corresponding to non-UAV services.
  • the first device is 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.
  • the eighth message is used to request the establishment or modification of a non-unmanned network.
  • the session corresponding to the machine service.
  • the first device is a UE, the first device determines that the second condition is met, receives an eighth message from the SMS-SC, and sends the eighth message to SMF 1.
  • the eighth message is used to request the establishment or modification of a non-None. Conversations corresponding to human-machine services.
  • the first device determines that it is full If the second condition is met, a message (for example, recorded as a fourth message) for requesting execution of the first control plane process is received from the third device, and the first control plane process is executed.
  • the second condition includes one or more of the following conditions: the UE is revoked from the drone business authorization, the UE is not authorized to the drone business, the UE's drone business is de-registered, or the UE releases the last Sessions corresponding to drone business, etc.
  • the USS when the USS is ready to revoke the authorization for the drone service of the UE, it can send the revocation request (through the UAS NF) to the AMF (or SMF), and the AMF (or SMF) will continue to execute the drone service for the UE.
  • Authorization revocation process the revocation result will be sent to the UE through AMF (or SMF).
  • the AMF and SMF can subscribe to the authorization information from each other, that is, they can receive the authorization revocation results from each other. Therefore, the first device (such as UE, SMF, or AMF) can determine that the UE is revoked from the drone service authorization, but the embodiment of the present application is not limited thereto. For example, when the UE needs to be de-registered, the AMF will receive the de-registration request and execute the de-registration process with the UE, so the AMF and the UE can obtain information about the completion of the de-registration process.
  • the SMF can obtain the deregistration information of the UE through the AMF (the SMF subscribes to the notification service of related information), but the embodiment of the present application is not limited to this.
  • the first device is an SMF
  • the first device can determine whether the UE releases the session corresponding to the last drone service according to the stored context information of the UE. For another example, if the first device is not the SMF, the first device may obtain from the SMF whether the UE releases the session corresponding to the last drone service.
  • the AMF can maintain the status of the UE.
  • Figure 5 is a schematic flowchart of a communication method provided by an embodiment of the present application.
  • the first device is AMF
  • the fourth device is RAN, or UE, or USS, or UAS NF/NEF.
  • the AMF can obtain the status of the UE according to one or more of the four methods shown in Figure 5.
  • Method 1 includes steps S501 to S503, method 2 includes steps S504 and S505, method 3 includes steps S506 to S508, and method 4 includes steps S509 to S511.
  • the method may also include the following processes.
  • AMF sends the ninth message to RAN; accordingly, RAN receives the ninth message from AMF.
  • the AMF may send the 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 in the embodiments of this application.
  • the RAN determines the status of the UE according to the mobility information of the UE.
  • the movement information includes one or more of height, movement speed, position or movement trajectory.
  • the RAN can measure the UE and obtain the mobility information of the UE.
  • the RAN may receive mobility information from the UE. It should be understood that the embodiments of the present application do not limit the specific implementation manner in which the RAN obtains mobility information.
  • the RAN may determine whether the UE is in a flight state or a non-flight state according to the UE's mobility information. For example, if the altitude is greater than or equal to the altitude threshold, the RAN may determine that the UE is in a flight state.
  • the height threshold may be preset, which is not limited in the embodiments of this application.
  • the RAN may determine that it is in a flight state.
  • the speed threshold may be preset, which is not limited in the embodiments of the present application.
  • the RAN sends the fourth indication information to the AMF; accordingly, the AMF receives the fourth indication information from the RAN.
  • the fourth indication information may be used to indicate that the UE is in a flight state, or to indicate that the UE is in a non-flight state.
  • the RAN may send fourth indication information to the AMF to indicate the status of the UE.
  • FIG. 5 takes the fourth indication information indicating that the UE is in the flight state as an example.
  • S504 The UE determines the status of the UE according to the mobility information and/or the fifth indication information.
  • the UE can measure one or more of its own height, movement speed, position, or movement trajectory, or can calculate the movement information of the UE by measuring the received wireless signal of the RAN.
  • the fifth indication information may come from the application layer of the UE.
  • the application layer triggers the UE to enter the flight mode.
  • the application layer may generate the fifth indication information.
  • the fifth indication information is used to instruct the UE to enter the flight mode. Further, the UE enters the flight mode according to The fifth indication information determines that the UE is in a flight state.
  • the UE sends the fourth indication information to the AMF; accordingly, the AMF receives the fourth indication information from the UE.
  • S506 AMF obtains the mobility information of the UE.
  • the AMF may obtain the UE's mobility information from the RAN and/or GMLC (or LMF).
  • the RAN may proactively report the UE's mobility information to the AMF; or, after receiving a message from the AMF requesting to obtain the UE's mobility information, the RAN may send the UE's mobility information to the AMF.
  • the GMLC (or LMF) can actively push the UE's mobility information to the AMF; or, after receiving a message from the AMF requesting to obtain the UE's mobility information, the GMLC (or LMF) can send the UE's mobility information to the AMF.
  • Mobile information It should be understood that the embodiment of the present application does not limit the specific implementation manner in which the AMF obtains the mobility information of the UE.
  • S507 AMF obtains the flight information of the UE.
  • the flight information may include, for example, flight route and/or flight time.
  • the AMF can obtain the UE's flight information from the UAS NF/NEF (or USS).
  • the UAS NF/NEF or USS
  • the UAS NF/NEF can actively push the UE's flight information to the AMF; or, the UAS NF/NEF (or the USS) can receive a message from the AMF requesting the UE's flight information and send it to the AMF.
  • the flight information of the UE; the embodiment of this application does not limit the specific implementation method for the AMF to obtain the flight information of the UE.
  • the AMF determines the status of the UE based on the mobility information and flight information.
  • the AMF may determine whether the current time and the UE's current location match the flight path and flight schedule. If the current time and the current position of the UE match the flight path and flight schedule, the AMF determines that the UE is in the flight state; otherwise, the AMF determines that the UE is in the non-flight state. For another example, the AMF may determine the status of the UE based on mobility information. For example, if the altitude is greater than or equal to the altitude threshold, the AMF may determine that the UE is in the flight state; or if the movement speed is greater than or equal to the speed threshold, the AMF may determine that it is in the flight state.
  • the AMF can send a status request message for obtaining the UE to other devices (such as network data analytics function (NWDAF) device); NWDAF can collect UE-related information (such as mobility information and/or flight information, etc.), determine the status of the UE, and send the status of the UE to the AMF.
  • NWDAF may send the mobility information and/or flight information obtained 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.
  • Figure 5 takes the AMF as an example to determine the status of the UE based on mobility information and flight information.
  • AMF has completed obtaining the status of the UE through method 3.
  • the AMF obtains the status of the UE through method 4.
  • AMF sends the ninth message to UAS NF/NEF; accordingly, UAS NF/NEF receives the ninth message from AMF.
  • the AMF can send the ninth message to the UAS NF/NEF (or USS) to obtain the status of the UE; or, the UAS NF/NEF (or the USS) can also actively push the status of the UE to the AMF; the embodiment of this application is Not limited.
  • UAS NF/NEF determines the status of the UE.
  • UAS NF/NEF can obtain the status of the UE based on the locally stored status of the UE, or the UAS NF/NEF can also obtain the status of the UE from the USS, such as sending a request message to the USS to obtain the status of the UE.
  • the USS can obtain the status of the UE based on the communication content between itself and the UE, or the USS can also determine the status of the UE based on the UE's flight authorization information and/or flight schedule.
  • there is a dedicated communication channel (such as C2 communication) between the USS and the UE as a drone and the USS can obtain the status of the UE based on the communication content of the communication channel.
  • the USS may determine the status of the UE based on the stored flight authorization information and/or flight schedule of the UE.
  • UAS NF/NEF sends the fourth indication information to AMF; accordingly, AMF receives the fourth indication information from UAS NF/NEF.
  • the AMF has completed obtaining the status of the UE through method 4.
  • AMF can determine the status of the UE based on mobility information and flight information, and can also obtain the status of the UE from the RAN or UE or UAS NF/NEF or USS.
  • the implementation method is flexible and adaptable.
  • the AMF can maintain (or save) the status of the UE and send the status of the UE to other devices (such as SMF, SMS-SC, UDM, AUSF, ARPF or NSSAAF, etc.) so that the other devices can determine whether the UE is in flight. state.
  • FIG. 5 introduces how AMF obtains the status of the UE in various ways. Next, the process shown in Figure 4 will be introduced with reference to Figures 6 to 13.
  • Figure 6 is another schematic flowchart of a communication method provided by an embodiment of the present application.
  • the first device is SMF 1
  • SMF 1 releases sessions corresponding to all non-UAV services of the UE managed by SMF 1.
  • the second device is PCF, UDM, UDR, or AMF.
  • the method may include the following processes.
  • S601 The UE sends the second message to SMF 1; accordingly, SMF 1 receives the second message from the UE.
  • S601 is an optional step, that is, SMF 1 can determine whether the first condition is met in response to the second message, or SMF 1 can also determine whether the first condition is met periodically or aperiodically. This is not limited in the embodiment of the present application.
  • the second message is used to request the establishment of the first session.
  • the second message may be, for example, a PDU session establishment request (PDU session establishment request) message.
  • the second message may be used to request modification of the first session.
  • the second message may be, for example, a PDU session modification request (PDU session modification request) message. This embodiment of the present application does not limit the name of the second message.
  • S602 SMF 1 determines that the first condition is met.
  • the first condition includes one or more of the following conditions: the UE is authorized for the drone service, the UE initiates the establishment of a session corresponding to the first drone service, or the UE is in a flight state.
  • SMF 1 may determine whether the first condition is satisfied. For example, SMF 1 may determine whether the UE is authorized for the drone service according to the stored context information of the UE. For example, SMF 1 can obtain from AMF whether the UE is authorized for the drone service (subscribe to AMF's service about the UE's drone authorization status, and when the drone is authorized, AMF will notify SMF 1; or SMF 1 will notify AMF Send a request message to obtain the UE's drone service authorization status).
  • SMF 1 may Determine whether the first session is a session corresponding to the first drone service initiated by the UE.
  • SMF 1 may obtain the status of the UE from the AMF, and determine whether the UE is in the flight status according to the status of the UE.
  • SMF 1 satisfies the first condition as an example.
  • S603 SMF 1 determines that the first session belongs to the session corresponding to the drone service, and determines that the first session is the session corresponding to the first drone service of the UE.
  • S603 is an optional step.
  • the first condition determined by SMF 1 in S602 includes that the UE is authorized for the drone service and/or the UE is in a flight state. After executing S602, SMF 1 may execute S603 or not execute S603.
  • the first condition determined by SMF 1 includes the UE initiating the establishment of the first session corresponding to the drone service, then S603 and S602 can be understood as one step, and SMF 1 does not need to execute S603.
  • the second message is used to request the creation of a first session.
  • SMF 1 determines that the first session belongs to a session corresponding to the drone service, and determines whether the first session is a session corresponding to the first drone service. If the first session is a session corresponding to the first drone service, SMF 1 can execute the contents shown in S604-S609; otherwise, the contents shown in S604-S609 will not be executed.
  • the second message is used to request modification of the first session.
  • SMF 1 can determine that the first session belongs to a session corresponding to the non-UAV service, and determine whether the modified first session is the first UAV. The session corresponding to the business. If the modified first session is the session corresponding to the first drone service, SMF 1 executes the content shown in S604-S609, otherwise, the content shown in S604-S609 is not executed.
  • the second message is used to request modification of the first session.
  • SMF 1 determines that the first session belongs to the session corresponding to the drone service. Further, SMF 1 can also determine whether the second message requests to modify the drone service. The session is modified to a session corresponding to the non-UAV business. If the second message requests to modify the session corresponding to the drone service to a session corresponding to the non-drone service, SMF 1 executes the content shown in S604-S609; otherwise, the content shown in S604-S609 is not executed.
  • S604 SMF 1 releases the session corresponding to the non-UAV service of the UE managed by SMF 1, and/or prohibits the establishment or modification of the session corresponding to the non-UAV service.
  • SMF 1 can release all sessions corresponding to non-UAV services of the UE managed by SMF 1, or prohibit the establishment or modification of sessions corresponding to non-UAV services, or release the UE managed by SMF 1 All sessions corresponding to non-UAV services and prohibit the creation or modification of sessions corresponding to non-UAV services.
  • SMF 1 can initiate the session release process and notify relevant NFs, network elements (such as UPF, AMF, RAN, etc.), UE, etc. to release resources related to the session.
  • SMF 1 can be configured as a policy that prohibits the establishment or modification of sessions corresponding to non-UAV services. If SMF 1 receives a request message from the UE for establishing or modifying a session, SMF 1 can determine whether the session corresponds to non-UAV services. If the session is a session corresponding to the UAV business, SMF 1 establishes or modifies the session; or, if the session is a session corresponding to a non-UAV business, SMF 1 can suspend or terminate the establishment or modification of the session. Optionally, after SMF 1 suspends establishing or modifying the session, if SMF 1 determines that the second condition is met, SMF 1 continues to establish or modify the session.
  • step S603 determines that the first session belongs to a session corresponding to a non-UAV service
  • SMF 1 may reject the establishment request of the first session or reject the modification request of the first session.
  • the second message is a request to modify the first session to a session corresponding to the drone service
  • SMF 1 may not reject the request.
  • SMF 1 determines that the first session is No is the session corresponding to the first drone service. If the first session is a session corresponding to the first drone service, the contents shown in S605-S609 can be executed; otherwise, the contents shown in S605-S609 will not be executed.
  • step S603 determines that the first session belongs to the session corresponding to the UAV service and the second message is used to request the creation of the first session
  • SMF 1 determines whether the first session is a session corresponding to the first UAV service. If the first session is a session corresponding to the first drone service, the contents shown in S605-S609 can be executed; otherwise, the contents shown in S605-S609 will not be executed.
  • step S603 determines that the first session belongs to the session corresponding to the UAV service and the second message is used to request to modify the first session
  • SMF 1 determines whether the request modifies the session corresponding to the UAV service to a session corresponding to the non-UAV service. session. If so, SMF 1 rejects the request; otherwise, the contents shown in S605-S609 can be executed.
  • SMF 1 sends the second indication information to the UE; accordingly, the UE receives the second indication information from SMF 1.
  • SMF 1 may send second indication information to the UE.
  • the second indication information may be used to indicate that the establishment of a session corresponding to the non-UAV service of the UE is prohibited, or may indicate that the establishment of the non-UAV service of the UE at SMF 1 is prohibited. corresponding session.
  • the UE can first determine whether the session belongs to a session corresponding to the UAV service before initiating session establishment. If the session is a session corresponding to the UAV service, the UE initiates the process of establishing the session; or, if the session is a session corresponding to a non-UAV service, the UE may suspend the process of establishing the session.
  • the UE may initiate a process for establishing the session.
  • the UE may initiate a process for establishing the session.
  • the UE to determine whether the session belongs to the session corresponding to the drone service please refer to the relevant content of SMF 1 to determine whether the first session belongs to the session corresponding to the drone service, which will not be described again here.
  • the second instruction information sent by SMF 1 can also be used to indicate that it is prohibited to modify the session corresponding to the drone service to a session corresponding to the non-drone service.
  • the UE can first determine whether the session modification request belongs to modifying the session corresponding to the drone service to a session corresponding to the non-drone service before initiating the session modification process. If the session modification request does not belong to modifying the session corresponding to the drone service to a session corresponding to the non-drone service, the UE initiates the session modification process; or, if the session modification request belongs to modifying the session corresponding to the drone service For a session corresponding to non-UAV services, the UE may suspend the process of initiating modification of the session.
  • the UE may initiate the session modification process.
  • the UE may initiate the session modification process.
  • the UE to determine whether the session belongs to the session corresponding to the drone service please refer to the relevant content of SMF 1 to determine whether the first session belongs to the session corresponding to the drone service, which will not be described again here.
  • SMF 1 has completed the restrictions on non-drone services.
  • SMF 1 can also perform the content shown in S606.
  • S606 SMF 1 sends the third message to PCF; accordingly, PCF receives the third message from SMF 1.
  • the third message may be used to request or notify to limit the session corresponding to the non-UAV service of the UE. It should be noted that the steps performed by PCF in this embodiment can also be performed by UDM, UDR, or AMF.
  • S607 The PCF determines that SMF 2 manages a session corresponding to the UE's non-UAV service.
  • the PCF can determine the SMF that manages the session corresponding to the non-UAV service of the UE or the PCF determines the SMF that manages the session of the UE (in Figure 6, the PCF determines that SMF 2 manages the non-UAV session of the UE. Taking the session corresponding to the human-machine business as an example). For example, the PCF may determine the SMF that manages the session corresponding to the non-UAV service of the UE based on the context information of the UE and/or the association information between the UE and the SMF obtained from the UDM or UDR.
  • the PCF can be based on the context information of the UE and/or the association information between the UE and the SMF obtained from the UDM or UDR, Determine the SMF that manages the session with the UE. It should be noted that if the PCF determines that SMF 2 manages the session of the UE and does not determine whether SMF 2 manages the session corresponding to the UE's non-UAV service, SMF 2 can determine whether it manages the UE's non-UAV session in step S609. The session corresponding to the human-machine business and perform the corresponding operations.
  • PCF sends the sixth indication information to SMF 2; accordingly, SMF 2 receives the sixth indication information from PCF.
  • the sixth instruction information may be used to instruct (or notify) to release all sessions corresponding to non-UAV services of the UE managed by SMF 2, or to indicate that the establishment or modification of sessions corresponding to non-UAV services is prohibited. session, or release all sessions corresponding to non-UAV services of the UE managed by SMF 2 and prohibit the establishment or modification of sessions corresponding to non-UAV services.
  • S609 SMF 2 releases the session corresponding to the non-UAV business of the UE managed by SMF 2, and/or prohibits the establishment or modification of the session corresponding to the non-UAV business.
  • SMF 2 can release all sessions corresponding to non-UAV services of the UE managed by SMF 2 according to the sixth instruction information and/or prohibit the establishment or modification of sessions corresponding to non-UAV services.
  • SMF 2 may send indication information to the UE indicating that it is prohibited to establish (or to prohibit establishing at SMF 2) a session corresponding to a non-UAV service.
  • Figure 7 is another schematic flowchart of a communication method provided by an embodiment of the present application.
  • the first device is SMF 1
  • SMF 1 releases sessions corresponding to some non-UAV services of the UE managed by SMF 1.
  • the second device is PCF, UDM, UDR, or AMF.
  • the method may include the following processes.
  • S701 to S703, S706, S707, and S711 in Figure 7 are the same as S601 to S603, S606, S607, and S605 in Figure 6. The difference is:
  • S704 SMF 1 determines that N is greater than M.
  • S704 is an optional step.
  • SMF 1 can determine the number of sessions corresponding to the non-UAV service of the UE to be released based on N and M, that is, perform the content shown in S704 and S705; or, SMF 1 can also determine the release based on the first instruction information from the PCF.
  • the number of sessions corresponding to the UE's non-UAV services is to perform the contents shown in S706, S708 and S709.
  • N may be the number of sessions corresponding to the non-UAV services of the UE managed by SMF 1.
  • the first device may determine the N according to the context information of the UE, or obtain the N from the UDM or UDR.
  • the method of obtaining N in the embodiment of the present application is not limited to this.
  • M may be the number of sessions corresponding to non-UAV services that the UE is allowed to establish at SMF 1 when performing UAV services.
  • the M may be preset, or configured in PCF, or obtained from UDM or UDR.
  • the embodiment of this application does not limit the implementation of M.
  • SMF 1 can determine whether N is greater than M. If N is less than or equal to M and step S701 is executed, the process of establishing or modifying the first session is executed; if N is less than or equal to M and step S701 is not executed, the process End; if N is greater than M, SMF 1 executes the content shown in S705.
  • SMF 1 determines to release H sessions corresponding to non-UAV services.
  • H is a positive integer greater than or equal to (NM).
  • SMF 1 may determine to release H sessions corresponding to non-UAV services among N sessions corresponding to non-UAV services.
  • SMF 1 can arbitrarily select H sessions corresponding to non-UAV services from the N sessions corresponding to non-UAV services.
  • SMF 1 can select H sessions corresponding to the N non-UAV services based on the priorities of the sessions corresponding to the N non-UAV services. For example, the N non-UAV services Sessions corresponding to the H non-UAV services with lower priorities in the corresponding sessions.
  • SMF 1 may select H sessions corresponding to non-UAV services from the N sessions corresponding to non-UAV services based on the session establishment duration and/or resources consumed by the sessions, such as those with a longer establishment time. H sessions corresponding to (or shorter) non-UAV services, or H sessions corresponding to H non-UAV services that consume more resources (or less), etc. It should be understood that the embodiment of the present application does not limit the selection of H sessions corresponding to non-UAV services.
  • S708 PCF determines that SMF 1 releases H sessions corresponding to non-UAV services and SMF 2 releases Q sessions corresponding to non-UAV services.
  • SMF 1 can send N to PCF, such as carrying N in the third message and sending it to PCF; PCF can determine that N is greater than M based on N and M and determine that SMF 1 releases the H non-digital data of the UE. Drone business.
  • the PCF maintains the number of sessions corresponding to the non-UAV services that the UE has established. For example, the PCF receives N from SMF 1 and receives the non-UAV from SMF 2 for the UE it manages.
  • PCF can be based on the number of sessions corresponding to non-UAV services that the UE has established (for example, recorded as (For example, recorded as Y, Y is a positive integer) Determine whether the SMF releases the session corresponding to the UE's non-UAV business. Y may be predefined, which is not limited in the embodiments of this application. If session.
  • the PCF may determine that SMF 1 releases one or more (e.g., recorded as H) sessions corresponding to non-UAV services of the UE managed by it, and determines that SMF 2 releases Q (Q is Positive number) Sessions corresponding to non-UAV services. For example, the PCF can determine based on X, Y, N and M that SMF 1 releases the sessions corresponding to the H non-UAV services of the UE that it manages.
  • PCF determines that SMF 2 releases Q sessions corresponding to non-UAV services please refer to the implementation process of PCF determining that SMF 1 releases H sessions corresponding to non-UAV services, which will not be described again here.
  • the number of sessions corresponding to the non-drone services to be released determined by SMF 1 based on N and M is different from the non-drone services to be released determined by PCF based on N and M, or based on X, Y, N and M.
  • the number of corresponding sessions may be the same or different, which is not limited in the embodiment of this application.
  • PCF can also be performed by UDM, UDR or AMF.
  • PCF sends the first indication information to SMF 1; accordingly, SMF 1 receives the first indication information from PCF.
  • the first indication information is used to instruct to release sessions corresponding to the H non-UAV services of the UE.
  • SMF 1 releases sessions corresponding to the H non-UAV services of the UE managed by SMF 1.
  • SMF 1 releases the H sessions corresponding to the non-UAV services of the UE managed by the SMF 1, and/or prohibits the establishment or modification of the sessions corresponding to the non-UAV services.
  • SMF 1 For the specific implementation process, please refer to S604. Description will not be repeated here.
  • Figure 7 takes SMF 1 as an example to release sessions corresponding to H non-UAV services of UE managed by SMF 1.
  • PCF sends the sixth indication information to SMF 2; accordingly, SMF 2 receives the sixth indication information from PCF.
  • the sixth instruction information may be used to instruct to release Q sessions corresponding to non-UAV services of the UE managed by SMF 2, and/or to instruct that establishment or modification of sessions corresponding to non-UAV services is prohibited.
  • FIG. 7 takes the sixth instruction information as an example to indicate releasing sessions corresponding to Q non-UAV services of the UE managed by SMF 2.
  • S713 SMF 2 releases Q sessions corresponding to non-UAV services of the UE managed by SMF 2 and/or prohibits the establishment or modification of sessions corresponding to non-UAV services.
  • SMF 2 releases Q sessions corresponding to non-UAV services of the UE managed by SMF 2, and/or prohibits the establishment or modification of sessions corresponding to non-UAV services.
  • SMF 2 For the specific implementation process, please refer to S604. Description will not be repeated here.
  • Figure 7 takes SMF 2 as an example to release sessions corresponding to Q non-UAV services of UE managed by SMF 2.
  • Figure 8 is another schematic flowchart of a communication method provided by an embodiment of the present application.
  • the first device is a UE, and the UE does not send or suspends sending to SMF 1 a request to establish or modify a session corresponding to the non-UAV service.
  • the method may include the following processes.
  • S801 AF sends the tenth message to SMS-SC. Accordingly, the SMS-SC receives the tenth message from the AF.
  • the tenth message is used to trigger the UE to request to establish or modify the second session.
  • the tenth message may be an SMS message, for example, but the embodiment of the present application does not limit the specific implementation form of the tenth message.
  • the AF may determine to trigger the UE to initiate establishment or modification of the second session, generate a tenth message, and send the tenth message to the SMS-SC.
  • the AF may determine to trigger the UE to initiate a second session establishment or modification process based on application requirements (such as actively pushing video data to the UE, etc.) or the UE's application requirements.
  • the AF sends a tenth message to the SMS-SC, and the tenth message can reach the SMS-SC via NEF and UDM.
  • NEF and UDM can verify the AF and determine that the receiving end device of the tenth message is SMS-SC. It should be understood that the embodiment of the present application does not limit the transmission path of the tenth message.
  • SMS-SC sends the eleventh message to the UE.
  • the UE receives the eleventh message from the SMS-SC.
  • the SMS-SC After receiving the tenth message, the SMS-SC sends an eleventh message to the UE.
  • the eleventh message is used to notify the UE to trigger the establishment or modification process of the second session.
  • the SMS-SC may send a response message to the AF indicating that the eleventh message has been sent to the UE.
  • S803 The UE determines that the first condition is met.
  • the first condition may include one or more of the following conditions: the UE is authorized for the drone service, the UE initiates the establishment of a session corresponding to the first drone service, or the UE is in a flight state.
  • the UE can determine whether it is authorized for the drone service based on the stored context information or drone authorization status.
  • the UE may determine based on the stored context information or session state that the session establishment to be initiated is a session corresponding to the first drone service.
  • the UE may determine that it is in the flight state according to the mobility information and/or the fifth indication information.
  • S803 please refer to the relevant content of S401 and will not be repeated here.
  • S804 The UE determines whether the second session belongs to a session corresponding to non-UAV services.
  • S804 is an optional step. For example, after the UE determines that the first condition is met, it may not send or suspend sending the twelfth message to SMF 1.
  • the twelfth message is used to request the establishment or modification of the second session.
  • the UE may determine whether the second session belongs to a session corresponding to non-UAV services according to the eleventh message.
  • the eleventh message may include one or more of the following information: UE type indication information, UAV ID, DNN, USS address information, USS ID, S-NSSAI identification, AF ID, or session service type, etc.
  • the eleventh message may include a UE identity (such as a general public subscription identifier (GPSI), SUPI, UAV ID, etc.) and/or an AF identity.
  • the UE can identify the and/or the AF identifier determines the service type of the second session. For example, if the UE identity is a common terminal identity rather than a UAV identity (such as a UAV ID), the UE may determine that the second session belongs to a session corresponding to a non-UAV service.
  • the UE may determine that the second session belongs to the session corresponding to the non-UAV service.
  • the content shown in S805 is executed; or, if the UE determines that the second session belongs to a session corresponding to a non-UAV service, the content shown in S806 is executed.
  • the UE determines that the second session belongs to a session corresponding to the drone service and is ready to trigger the modification of the session to a session not corresponding to the drone service then perform the content shown in S806; Alternatively, if the UE determines that the second session belongs to a session corresponding to a non-UAV service and is ready to trigger modification of the session to a session corresponding to the UAV service, then the content shown in S805 is executed.
  • S805 The UE sends the twelfth message to SMF 1; accordingly, SMF 1 receives the twelfth message from the UE.
  • the second session belongs to the session corresponding to the drone service, and the UE can trigger the modification or establishment of the second session, that is, trigger the modification or establishment of the session corresponding to the drone service.
  • the UE sends the twelfth message to SMF 1.
  • S806 The UE does not or suspends sending the twelfth message to SMF 1.
  • the second session belongs to the session corresponding to the non-UAV service, and the UE does not trigger the modification or establishment of the second session, that is, the UE does not trigger the modification or establishment of the session corresponding to the non-UAV service.
  • the UE does not or suspends sending the twelfth message to SMF1.
  • the UE can start the second timer.
  • the UE does not send the twelfth message to SMF 1; or if the second condition is met during the running of the second timer, the UE sends the twelfth message to SMF 1 Send the twelfth message.
  • the second condition please refer to the relevant content in Figure 4 and will not be repeated here.
  • the UE after receiving the eleventh message from the AF for requesting to establish or modify the second session through SMS-SC, the UE can determine that the first condition is met, and determine that the second session is not In the case of a session corresponding to the drone business, the twelfth message is not sent or suspended to SMF 1, which avoids initiating the establishment or modification of a session corresponding to the non-drone business, thereby reducing the attacker's use of non-drone services. Attacks on UE by human-machine services and avoid non-UAV services from encroaching on the resources of UAV services.
  • Figure 9 is another schematic flowchart of a communication method provided by an embodiment of the present application.
  • the first device is the SMS-SC, and the SMS-SC does not or suspends sending to the UE a request to establish or modify a session corresponding to the non-UAV service.
  • the method may include the following processes.
  • S901 AF sends the tenth message to SMS-SC. Accordingly, the SMS-SC receives the tenth message from the AF.
  • SMS-SC determines that the first condition is met.
  • the first condition may include one or more of the following conditions: the UE is authorized for the drone service, the UE initiates the establishment of a session corresponding to the first drone service, or the UE is in a flight state.
  • the SMS-SC may subscribe to services of the AMF (or SMF or UAS NF) regarding the UE's drone authorization status or flight status.
  • the AMF or SMF or UAS NF
  • the SMS-SC can also send a message to the AMF (or SMF or UAS NF). Request message to obtain the UE's drone authorization status or flight status.
  • SMS-SC can subscribe to AMF (or SMF or UDR or UDM) for services related to session status. For example, when the number of sessions corresponding to the UE's drone service changes, the AMF (or SMF or UDR or UDM) can notify SMS-SC of the number of sessions corresponding to the existing drone service of the UE, so that SMS-SC can determine whether the second session is a session corresponding to the first drone service initiated and established by the UE; Alternatively, the SMS-SC may also send a request message to the AMF (or SMF or UDR or UDM) to obtain the number of sessions corresponding to the UE's drone service, thereby determining whether the session initiated by the UE (i.e., the second session) is the first session to be established.
  • AMF or SMF or UDR or UDM
  • the SMS-SC can locally store the context information of the UE, which includes the drone authorization status and flight status of the UE. In this way, the SMS-SC can determine the drone status of the UE based on the locally stored context information of the UE. aircraft authorization status or flight status.
  • the specific implementation process of S902 please refer to the relevant content of S401 and will not be repeated here.
  • SMS-SC determines whether the second session belongs to a session corresponding to non-UAV services.
  • S903 is an optional step.
  • 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 to establish or modify the second session.
  • the SMS-SC may determine whether the second session belongs to a session corresponding to non-UAV services according to the tenth message.
  • the tenth message may include one or more of the following information: UE type indication information, UAV ID, DNN, USS address information, USS ID, S-NSSAI identification, AF ID, or session service type, etc.
  • SMS-SC can send a message to other devices (such as SMF or UDM or UDR) to request whether the second session belongs to a session corresponding to non-UAV services. (That is, obtaining from other devices whether the second session belongs to a session corresponding to non-UAV services).
  • devices such as SMF or UDM or UDR
  • the tenth message may include a UE identity (such as a general public subscription identifier (GPSI) or SUPI, UAV ID, etc.) and/or an AF identity.
  • SMS-SC may determine the service type of the second session according to the UE identity and/or AF identity. For example, if the UE identity is a common terminal identity rather than a UAV identity (such as a UAV ID), the UE can determine that the second session belongs to a session corresponding to a non-UAV service.
  • the UE may determine that the second session belongs to the session corresponding to the non-UAV service.
  • the SMS-SC determines that the second session belongs to a session corresponding to the drone service, it executes the contents shown in S904 and S905; or, if the SMS-SC determines that the second session belongs to a session corresponding to the non-drone service, it executes the contents shown in S906. displayed content.
  • the SMS-SC determines that the second session belongs to the session corresponding to the drone service and is ready to trigger the modification of the session to a session not corresponding to the drone service, then perform S906 content; or, if the SMS-SC determines that the second session belongs to a session corresponding to a non-UAV service, and is ready to trigger the modification of the session to a session corresponding to the UAV service, then execute the contents shown in S904 and S905.
  • SMS-SC sends the eleventh message to the UE; accordingly, the UE receives the eleventh message from the SMS-SC.
  • the second session belongs to a session corresponding to the drone service or is to be modified to a session corresponding to the drone service, and the SMS-SC may send an eleventh message to the UE.
  • S905 The UE sends the twelfth message to SMF 1; accordingly, SMF 1 receives the twelfth message from the UE.
  • the UE After receiving the eleventh message, the UE triggers the modification or establishment of the session corresponding to the drone service, and sends the twelfth message to SMF 1.
  • the twelfth message is used to request the establishment or modification of the second session.
  • SMS-SC does not or suspends sending the eleventh message to the UE.
  • the second session belongs to a session corresponding to non-UAV services, and the SMS-SC does not or suspends sending the eleventh message to the UE.
  • the SMS-SC can start the second timer.
  • the SMS-SC does not send a message to The UE sends the eleventh message; or if the second condition is met during the running of the second timer, the SMS-SC sends the eleventh message to the UE.
  • the second condition please refer to the relevant content in Figure 4 and will not be repeated here.
  • the SMS-SC can determine that the first condition is met, and determine that the second session belongs to a non-UAV.
  • the eleventh message is not sent or suspended to the UE, which avoids establishing or modifying a session corresponding to the non-UAV service, thereby reducing attackers' attacks on the UE using non-UAV services. , and to prevent non-drone businesses from encroaching on the resources of the drone business.
  • Figure 10 is another schematic flowchart of a communication method provided by an embodiment of the present application.
  • the first control plane process is the first authentication process.
  • the first authentication process may be initiated by SEAF or AMF or UDM.
  • the first device may be SEAF or AMF; or the first device may also be UDM, AUSF or ARPF.
  • the third device may be SEAF or AMF.
  • the method includes two implementation methods, one of which includes the content shown in steps S1002 to S1004, and the other implementation method includes the content shown in steps S1005 to S1009.
  • S1001 SEAF determines to initiate the first authentication process.
  • SEAF can initiate the first authentication process of the UE. For example, when the UE registers with the network for the first time or when SEAF does not store the UE's security context, SEAF can initiate the UE's first authentication process. For another example, SEAF can initiate the first authentication process of the UE periodically or aperiodically according to the network configuration. It should be understood that the embodiment of the present application does not limit the reason and time for SEAF to initiate the first authentication process.
  • the steps performed by SEAF can also be performed by AMF.
  • SEAF Before SEAF initiates the first authentication process, SEAF may perform the content shown in S1002 to S1004, or perform the content shown in S1005.
  • S1002 SEAF determines that the UE is in flight state.
  • SEAF can determine the status of the UE through AMF.
  • One implementation method is that SEAF and AMF are merged and implemented in the same network function. AMF stores the status of the UE, so that SEAF can read the status of the UE.
  • SEAF and AMF are independent network functions, and SEAF can obtain the status of the UE from 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 to indicate that the UE is in the flight state or in the non-flight state.
  • SEAF can subscribe to the AMF for the UE's status; when the UE's status is updated (such as the UE switching from flying state to non-flying state, or the UE switching from non-flying state to flying state), AMF can push the UE's status to SEAF. .
  • the AMF can obtain the status of the UE, please refer to the relevant content in Figure 5, which will not be described again here.
  • SEAF determines that the UE is in the flight state, it executes the content shown in S1003; if SEAF determines that the UE is in the non-flight state, it executes the first authentication process, such as sending a request (or notification) to UDM (or AUSF, or ARPF) for execution News about the first-time certification process.
  • Figure 10 takes SEAF's determination that the UE is in the flight state as an example.
  • Figure 10 takes SEAF determining that the UE is in the flight state as an example.
  • S1002 can be replaced by SEAF determining that the first condition is met.
  • S401 which will not be repeated here. Repeat.
  • S1003 SEAF suspends or terminates the first certification process.
  • SEAF may suspend or terminate the first authentication process.
  • S1004 is an optional step.
  • the SEAF may start a first timer and determine the status of the UE during the running of the first timer. For example, during the running of the timer, SEAF obtains the status of the UE from the AMF. For the specific implementation method, please refer to the content of S1002, which will not be described again here. If SEAF obtains from the AMF that the UE is in a non-flight state during the running of the first timer, SEAF can end the running of the first timer and prepare to initiate the first authentication process, such as sending a request to UDM (or AUSF, or ARPF) for ( or notification) message to perform the first authentication process.
  • UDM or AUSF, or ARPF
  • SEAF may terminate the first Authentication process, such as terminating the first authentication process when the first timer runs out.
  • Figure 10 shows an example when the UE is in the flight state during the running of the first timer.
  • SEAF sends the fourth message to UDM; accordingly, UDM receives the fourth message from SEAF.
  • the fourth message may be, for example, an authenticate request message, but the name of the fourth message in this embodiment is not limited to this.
  • the fourth message may be used to request (or notify) to perform the first authentication process.
  • the steps performed by UDM can also be performed by AUSF or ARPF.
  • UDM determines that the UE is in flight state.
  • UDM can determine the status of the UE. For example, UDM can obtain the status of the UE from the AMF. For specific implementation methods, please refer to the description of SEAF obtaining the status of the UE from the AMF, which will not be described again here. If the UDM determines that the UE is in the flight state, the content shown in S1007 is executed; if the UDM determines that the UE is in the non-flight state, the first authentication process is executed, such as generating the authentication vector of the UE according to the fourth message, and executing step S1009.
  • Figure 10 takes UDM as an example to determine that the UE is in the flight state.
  • Figure 10 takes UDM determining that the UE is in the flight state as an example.
  • S1006 can be replaced by UDM determining that the first condition is met.
  • S401 please refer to S401, which will not be repeated here. Repeat.
  • the UDM may suspend or terminate the first authentication process.
  • S1008 is an optional step.
  • the UDM can start the first timer and determine the status of the UE during the running of the first timer. Please refer to the relevant content of S1004 for the specific implementation process, which will not be described again here. If the UDM obtains from the AMF that the UE is in the non-flight state during the running of the first timer (or at the end of the running), the UDM can end the running of the first timer and perform the first authentication process.
  • the UDM may terminate the first Authentication process, such as terminating the first authentication process when the first timer runs out.
  • Figure 10 shows an example when the UE is in the flight state during the running of the first timer.
  • timer started by SEAF in S1004 and the timer started by UDM in S1008 may be the same or different, and this is not limited in the embodiment of the present application.
  • UDM sends the fifth message to SEAF; accordingly, SEAF receives the fifth message from UDM.
  • the fifth message may be, for example, an authenticate response message, but the name of the fifth message in this embodiment is not limited to this.
  • the fifth message may include the authentication vector described in step S1006.
  • the fifth message may be used to indicate that the first authentication process is not performed.
  • the fifth message may include the reason for not performing the first authentication process.
  • the reason for not executing the first authentication process may be, for example, timeout, and/or the UE is in a flight state, etc.
  • the first device before executing (or initiating) the first authentication process of the UE, can determine the status of the UE, and when determining that the UE is in the flight state, suspend or terminate the first authentication process of the UE, so that It can avoid problems such as an increase in the UE's power consumption due to the execution of the UE's first authentication process during the UE's flight, causing the UE's power to be exhausted in advance and unable to complete the flight mission. Furthermore, suspending or terminating the execution of the first authentication process can release the resources required to execute the first authentication process, thereby providing the flying UE with more usable resources for executing drone services.
  • Figure 11 is another schematic flowchart of a communication method provided by an embodiment of the present application.
  • the first control plane process is a de-registration process, which may be initiated by UDM or AMF.
  • the first device may be a UDM; or the first device may also be an AMF.
  • the third device may be a UDM.
  • the method includes two implementation methods, one of which includes the content shown in steps S1102 to S1104, and the other implementation method includes the content shown in steps S1105 to S1109.
  • steps S1101-S1105 are not executed.
  • UDM determines to initiate the de-registration process.
  • the UDM can initiate the de-registration process of the UE.
  • UDM may determine to initiate the de-registration process of the UE based on operational requirements (such as changes in the UE's subscription information, the UE's subscription not supporting the current usage conditions, usage regions, etc.). It should be understood that the embodiment of the present application does not limit the reason and time for the UDM to initiate the de-registration process.
  • the UDM may execute the content shown in S1102 to S1104, or execute the content shown in S1105.
  • UDM determines that the UE is in flight state.
  • UDM can determine the status of the UE. For example, UDM can obtain the status of the UE from the AMF or UDR. For the specific implementation process, please refer to the relevant content of SEAF obtaining the status of the UE from the AMF in Figure 10, which will not be described again here. If the UDM determines that the UE is in the flight state, the content shown in S1103 is executed; if the UDM determines that the UE is in the non-flight state, the de-registration process is executed, such as sending a message requesting (or notifying) the de-registration process to the AMF.
  • Figure 11 uses UDM to determine that the UE is in the flight state as an example.
  • Figure 11 takes UDM determining that the UE is in the flight state as an example.
  • S1102 can be replaced by UDM determining that the first condition is met.
  • S401 please refer to S401, which will not be repeated here. Repeat.
  • S1103 UDM suspends or terminates the de-registration process.
  • the UDM may suspend or terminate the de-registration process.
  • S1104 During the running of the first timer, the UE is in the flight state, and the UDM terminates the de-registration process.
  • S1104 is an optional step.
  • the UDM can start the first timer and determine the status of the UE during the running of the first timer. Please refer to the relevant content of S1004 for the specific implementation process, which will not be described again here.
  • the UDM obtains from the AMF that the UE is in the non-flight state during the running of the first timer, the UDM can end the running of the first timer and prepare to initiate the de-registration process, such as sending a request (or notification) to the AMF to execute the de-registration process. news.
  • the UDM may terminate the de-registration process, as in the first timer running period.
  • the de-registration process is terminated when a timer runs out.
  • Figure 11 is an example when the UE is in the flight state during the running of the first timer.
  • UDM sends the fourth message to AMF; accordingly, AMF receives the fourth message from UDM.
  • the fourth message may be, for example, a deregistration notification message, but the name of the fourth message in this embodiment is not limited to this.
  • the fourth message can be used to request (or notify) to perform the de-registration process.
  • S1106 The AMF determines that the UE is in flight state.
  • AMF can determine the status of the UE. Please refer to Figure 5 for the specific implementation process, which will not be described again here. If the AMF determines that the UE is in the flight state, it executes the content shown in S1107; if the AMF determines that the UE is in the non-flight state, it executes the de-registration process, for example, initiates the process of releasing all sessions of the UE. Optionally, the AMF may send a request message for deregistration to the UE. Figure 11 takes the AMF determining that the UE is in the flight state as an example.
  • Figure 11 takes the AMF determining that the UE is in the flight state as an example.
  • S1106 can be replaced by the AMF determining that the first condition is met.
  • S401 please refer to S401, which will not be repeated here. Repeat.
  • S1101-S1105 are not executed, but S1106 is executed.
  • the AMF may be allowed based on operational or management requirements, the AMF is unable to support the UE, or the scheduled de-registration time has expired. It should be understood that the embodiment of the present application does not limit the reason and time for the AMF to initiate the de-registration process.
  • S1107 AMF suspends or terminates the de-registration process.
  • the AMF may suspend or terminate the de-registration process.
  • S1108 is an optional step.
  • the AMF can start the first timer and determine the status of the UE during the running of the first timer. Please refer to the relevant content of S1104 for the specific implementation process, which will not be described again here.
  • the AMF may end running the first timer and execute the de-registration process.
  • the AMF may terminate the de-registration process, such as terminating the de-registration process when the first timer runs.
  • Figure 11 is an example when the UE is in the flight state during the running of the first timer.
  • timer started by UDM in S1104 and the timer started by AMF in S1108 may be the same or different, and this is not limited in the embodiment of the present application.
  • AMF sends the fifth message to UDM; accordingly, UDM receives the fifth message from AMF.
  • the fifth message may be, for example, a deregistration notification response message, but the name of the fifth message in this embodiment is not limited to this. If the de-registration process is not executed, the fifth message may be used to indicate that the de-registration process is not executed. If the de-registration process is performed in S1106 (the UE is not in the flight state or does not meet the first condition), the fifth message may be used to confirm receipt of the fourth message.
  • the fifth message may include the reason for not performing the de-registration process. The reason for not executing the de-registration process may be, for example, timeout and/or the UE is in a flight state, etc.
  • the first device before executing (or initiating) the de-registration process of the UE, can determine the status of the UE, and when determining that the UE is in the flight state, suspend or terminate the de-registration process of the UE, so that It can be avoided that the connection between the UE and the mobile communication network is disconnected due to the completion of the UE's de-registration process while the UE is flying, causing the UE to be unable to communicate with the mobile communication network, making the UE unable to respond to the control instructions of the remote controller and unable to execute the drone.
  • the suspension or termination of the de-registration process can release the resources required to execute the de-registration process, thereby providing the flying UE with more usable resources for executing drone services.
  • FIG 12 is a schematic flowchart of yet another communication method provided by an embodiment of the present application.
  • the first control The noodle making process is a slice authentication process.
  • the slice authentication process can be initiated by AAA-S, or it can be initiated by DN, or it can be initiated by AMF.
  • the first device may be NSSAAF; or the first device may also be AMF.
  • the third device is AAA-S or DN; or, when the first device is AMF, the third device may be NSSAAF.
  • the method when the slice authentication process is initiated by AAA-S (or DN), the method includes two implementations, one of which includes the content shown in steps S1203 to S1206, and the other implementation Including the contents shown in steps S1207 to S1212.
  • the implementation When the slice authentication process is initiated by the AMF, the implementation includes the contents shown in steps S1208 to S1212.
  • AAA-S determines to initiate the slice authentication process or the slice re-authentication process.
  • Figure 12 takes the AAA-S determination and sending slice authentication process as an example.
  • AAA-S can initiate the UE's slice authentication process.
  • AAA-S may determine to initiate the UE's slice authentication process based on the AAA-S detecting an abnormality in the UE's slice usage.
  • AAA-S may initiate the UE's slice authentication process periodically or aperiodically. It should be understood that the embodiment of the present application does not limit the reason and time for AAA-S to initiate the slice authentication process.
  • AAA-S can also be performed by DN.
  • AAA-S sends the fourth message to NSSAAF; accordingly, NSSAAF receives the fourth message from AAA-S.
  • the fourth message may be, for example, an authentication request message or a re-authenticate request message, but the name of the fourth message in this embodiment is not limited to this.
  • the fourth message may be used to request (or notify) to perform the slice authentication process.
  • NSSAAF may execute the content shown in S1203 to S1206, or execute the content shown in S1207.
  • NSSAAF determines that the UE is in flight state.
  • NSSAAF can determine the status of the UE.
  • NSSAAF can obtain the status of the UE from the AMF.
  • the content shown in S1204 is executed; if the NSSAAF determines that the UE is in the non-flight state, the slice authentication process is executed, such as sending a message to the AMF for requesting (or notifying) the execution of the slice authentication process.
  • Figure 12 takes NSSAAF’s determination that the UE is in flight status as an example.
  • Figure 12 takes NSSAAF determining that the UE is in the flight state as an example.
  • S1202 can be replaced by NSSAAF determining that the first condition is met.
  • S401 please refer to S401, which will not be repeated here. Repeat.
  • S1204 NSSAAF suspends or terminates the slice authentication process.
  • NSSAAF may suspend or terminate the slice authentication process.
  • S1205 During the running of the first timer, the UE is in the flight state, and NSSAAF terminates the slice authentication process.
  • S1205 is an optional step.
  • the NSSAAF can start the first timer and determine the status of the UE during the running of the first timer. Please refer to the relevant content of S1004 for the specific implementation process, which will not be described again here.
  • the NSSAAF obtains from the AMF that the UE is in a non-flight state during the running of the first timer, the NSSAAF can end the running of the first timer and perform the slice authentication process, such as sending a request (or notification) to the AMF to perform the slice authentication process. information.
  • NSSAAF may terminate the slice authentication process, as in the first timer running.
  • the slice authentication process is terminated when a timer runs out.
  • Figure 12 is an example when the UE is in the flight state during the running of the first timer.
  • NSSAAF sends the fifth message to AAA-S; accordingly, AAA-S receives the fifth message from NSSAAF.
  • the fifth message may be, for example, an authentication response or a re-authenticate response message, but the name of the fifth message in this embodiment of the application is not limited thereto.
  • This fifth message may be used to indicate that the slice authentication process is not performed.
  • the fifth message may include the reason for not performing the slice authentication process.
  • the reason for not executing the slice authentication process may be, for example, timeout, and/or the UE is in a flight state, etc.
  • NSSAAF sends the fourth message to AMF; accordingly, AMF receives the fourth message from NSSAAF.
  • S1208 The AMF determines that the UE is in flight state.
  • S1201-S1207 are not executed, but S1208 is executed directly.
  • the AMF may determine that the UE needs to perform slice authentication based on the received registration request message of the UE, and thereby prepare to initiate slice authentication.
  • the AMF determines that slice authentication needs to be initiated. It should be understood that the embodiment of the present application does not limit the reason and time for the AMF to initiate the slice authentication process.
  • AMF can determine the status of the UE. Please refer to Figure 5 for the specific implementation process, which will not be described again here.
  • the AMF determines that the UE is in the flight state, the content shown in S1209 is executed.
  • AMF may send a response message of the fourth message to NSSAAF.
  • the AMF may send a slice authentication message to the UE before sending the response message of the fourth message.
  • the AMF can also send a slice authentication request message to AAA-S (via NSSAAF).
  • Figure 12 does not show steps regarding performing slice authentication. And, Figure 12 takes the AMF determining that the UE is in the flight state as an example.
  • Figure 12 takes the AMF determining that the UE is in the flight state as an example.
  • S1208 can be replaced by the AMF determining that the first condition is met.
  • S401 please refer to S401, which will not be repeated here. Repeat.
  • S1209 AMF suspends or terminates the slice authentication process.
  • the AMF may suspend or terminate the slice authentication process.
  • S1210 is an optional step.
  • the AMF can start the first timer and determine the status of the UE during the running of the first timer. Please refer to the relevant content of S1205 for the specific implementation process, which will not be described again here.
  • the AMF may end running the first timer and perform the slice authentication process.
  • the AMF may terminate the slice authentication process, such as terminating the slice authentication process when the first timer runs.
  • Figure 12 is an example when the UE is in the flight state during the running of the first timer.
  • timer started by NSSAAF in S1205 and the timer started by AMF in S1210 may be the same or different, and this is not limited in the embodiment of the present application.
  • AMF sends the fifth message to NSSAAF; accordingly, NSSAAF receives the fifth message from AMF.
  • NSSAAF sends the fifth message to AAA-S; accordingly, AAA-S receives the fifth message from NSSAAF.
  • NSSAAF After receiving the fifth message, NSSAAF can forward the fifth message to AAA-S.
  • AAA-S For details, please refer to the relevant description of S1206, which will not be described again here.
  • the first device before executing the slice authentication process of the UE, can determine the status of the UE, and when it is determined that the UE is in the flight state, suspend or terminate the slice authentication process of the UE. This can avoid During flight, the UE's power consumption increases due to the execution of the UE's slice authentication process, causing the UE's power to be exhausted in advance and unable to complete the flight mission. In addition, the suspension or termination of the slice authentication process can release the resources required to execute the slice authentication process, thereby providing the flying UE with more usable resources for executing drone services.
  • Figure 13 is another schematic flowchart of a communication method provided by an embodiment of the present application.
  • the first control plane process is a secondary authentication process.
  • the secondary authentication process may be initiated by AAA-S, or may be initiated by DN, or may be initiated by SMF.
  • the first device is SMF, and the third device is AAA-S or DN.
  • the method includes the following steps.
  • AAA-S determines to initiate the secondary authentication process or the re-authentication process of the secondary authentication.
  • AAA-S determines to initiate the secondary authentication process as an example.
  • AAA-S can initiate the secondary authentication process of the UE.
  • AAA-S may determine to initiate the secondary authentication process of the UE based on the AAA-S detecting an abnormality in the UE's session.
  • AAA-S may initiate the secondary authentication process of the UE periodically or aperiodically. It should be understood that the embodiment of the present application does not limit the reason and time for AAA-S to initiate the secondary authentication process.
  • AAA-S can also be performed by DN.
  • AAA-S sends the fourth message to SMF; accordingly, SMF receives the fourth message from AAA-S.
  • the fourth message may be, for example, a re-authenticate request (re-authenticate request) or an authentication request message, but the name of the fourth message in this embodiment is not limited to this.
  • the fourth message may be used to request (or notify) to perform the secondary authentication process.
  • the SMF determines that the UE is in flight state.
  • SMF does not execute S1301-S1302, but directly initiates S1303.
  • the SMF may determine that the UE needs to perform secondary authentication based on the received session establishment request message of the UE. It should be understood that the embodiment of the present application does not limit the reason and time for the SMF to initiate the secondary authentication process.
  • SMF can determine the status of the UE.
  • SMF can obtain the status of the UE from the AMF.
  • the SMF determines that the UE is in the flight state, it executes the content shown in S1304; if the SMF determines that the UE is in the non-flight state, it executes the secondary authentication process (the secondary authentication process initiated by AAA-S) or initiates the secondary authentication process (AMF The secondary authentication process initiated), the secondary authentication process is not shown in Figure 13.
  • Figure 13 takes SMF to determine that the UE is in the flight state as an example.
  • Figure 13 takes the SMF to determine that the UE is in the flight state as an example.
  • S1302 can be replaced by the SMF to determine that the first condition is met.
  • S401 please refer to S401, which will not be repeated here. Repeat.
  • S1304 SMF suspends or terminates the secondary authentication process.
  • the SMF may suspend or terminate the secondary authentication process.
  • S1305 is an optional step.
  • the SMF can start the first timer. And determine the status of the UE during the running of the first timer. Please refer to the relevant content of S1004 for the specific implementation process, which will not be described again here.
  • the SMF can end the running of the first timer and prepare to initiate the secondary authentication process, such as sending a request (or notification) to the AMF to perform the secondary authentication process. Information about the authentication process.
  • the SMF may terminate the secondary authentication process, such as The secondary authentication process is terminated when the first timer runs out.
  • Figure 13 is an example when the UE is in the flight state during the running of the first timer.
  • S1306 SMF sends the fifth message to AAA-S; accordingly, AAA-S receives the fifth message from SMF.
  • the fifth message may be, for example, a re-authenticate response message, but the name of the fifth message in this embodiment is not limited to this.
  • the fifth message may be used to indicate that the secondary authentication process is not performed.
  • the fifth message may include the reason for not performing the secondary authentication process.
  • the reason for not performing the secondary authentication process may be, for example, timeout, and/or the UE is in a flight state, etc.
  • the first device before executing the secondary authentication process of the UE, can determine the status of the UE, and when determining that the UE is in the flight state, suspend or terminate the secondary authentication process of the UE, which can avoid During the UE's flight, the power consumption of the UE increases due to the secondary authentication process of the UE, causing the UE's power to be exhausted in advance and unable to complete the flight mission.
  • the suspension or termination of the secondary authentication process can release the resources required to execute the secondary authentication process, thereby providing the flying UE with more usable resources for executing drone services.
  • the methods provided by the embodiments of the present application are introduced from the perspective of interaction between the first device and the second device.
  • the first device or the second device may include a hardware structure and/or a software module to implement the above-mentioned functions in the form of a hardware structure, a software module, or a hardware structure plus a software module. Each function.
  • FIG. 14 shows a schematic structural diagram of a communication device 1400.
  • the communication device 1400 can correspondingly implement the functions or steps implemented by the first device or the second device in each of the above method embodiments.
  • the communication device may include a processing unit 1401 and a transceiver unit 1402.
  • the communication device 1400 may also include a storage unit (not shown in FIG. 14), which may be used to store instructions (code or programs) and/or data.
  • the processing unit 1401 and the transceiver unit 1402 can be coupled with the storage unit.
  • the processing unit 1401 can read the instructions (code or program) and/or data in the storage unit to implement the corresponding method.
  • Each of the above units can be set up independently or partially or fully integrated.
  • the transceiver unit 1402 may include a sending unit and a receiving unit.
  • the communication device 1400 can implement the functions or steps implemented by the first device in each of the above method embodiments.
  • the processing unit 1401 is used to determine that the first condition is met, and the first condition includes one or more of the following conditions: the terminal device is authorized for the drone service, and the terminal device initiates the establishment of the first A session corresponding to the drone service, or the terminal device is in a flight state; and, restricting the non-drone business of the terminal device and/or restricting the first control plane process of the terminal device, wherein the third A control plane process is not a process exclusive to the drone business.
  • the processing unit 1401 when restricting non-UAV services of the terminal device, the processing unit 1401 may be used to:
  • the first device is a first session management function device that releases all or part of the sessions corresponding to the non-UAV services managed by the first device, and/or prohibits the establishment or modification of the non-UAV services.
  • the session corresponding to the business is a first session management function device that releases all or part of the sessions corresponding to the non-UAV services managed by the first device, and/or prohibits the establishment or modification of the non-UAV services.
  • the first device is a short message service center and does not send or suspends sending the 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-UAV service.
  • the first device is the terminal device and does not send or suspends sending the first message to the first session management function device.
  • the first message is used to request the establishment or modification of the session corresponding to the non-UAV service. .
  • the transceiver unit 1402 is configured to receive a second message from the terminal device, where the second message is used to request the establishment of a first session; And, the processing unit 1401 is further configured to determine, according to the second message, that the first session belongs to the session corresponding to the drone service.
  • the transceiver unit 1402 is further configured to: send a third message to the second device, where the third message is used to request restriction of the non-UAV service of the terminal device.
  • the transceiver unit 1402 is further configured to receive first instruction information from the second device, where the first instruction information is used to instruct the release of one or more of the non-UAVs.
  • the processing unit 1401 is specifically configured to: release one or more sessions corresponding to the non-UAV services according to the first instruction information.
  • the first device restricting the non-UAV services of the terminal device includes the first device releasing all or part of the non-UAV services managed by the first device.
  • Sessions corresponding to the service the processing unit 1401 is further configured to: determine that N is greater than M, where N is the number of sessions corresponding to the non-UAV service managed by the first device, and M is the number of sessions corresponding to the non-UAV service managed by the first device.
  • the H is a positive integer greater than or equal to (N-M).
  • the transceiver unit 1402 when restricting non-UAV services of the terminal device, is configured to send second instruction information to the terminal device, the second instruction information indicating that the establishment of all Describe the sessions corresponding to non-drone services.
  • the first control plane process includes one or more of a first authentication process, a de-registration process, a slice authentication process or a secondary authentication process.
  • the processing unit 1401 when restricting the first control plane process of the terminal device, is configured to suspend or terminate the first control plane process.
  • the processing unit 1401 is further configured to: start a first timer; determine that during the running of the first timer The terminal device satisfies the first condition; and the first control plane process is terminated when the first timer ends.
  • the transceiving unit 1402 is further configured to receive a fourth message from a third device, where the fourth message is used to request execution of the first control plane process; and, to the third device The device sends a fifth message, where the fifth message includes the reason for not performing the first control process.
  • the transceiver unit 1402 when it is determined that the terminal device is in the flight state, is configured to receive third indication information from the access and mobility management function device, where the third indication information indicates that the terminal The device is in flight mode.
  • the transceiver unit 1402 is further configured to send a sixth message to the access and mobility management function network element, wherein, the sixth message is used to obtain the status of the terminal device, and the status of the terminal device includes a flight state or/and a non-flight state.
  • the first device is an access and mobility management function device; when it is determined that the terminal device is in the flight state, the transceiver unit 1402 is configured to receive fourth indication information from the fourth device, The fourth indication information is used to indicate 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 movement information of the terminal device and/or the flight information of the terminal device. Flight status.
  • the first device is the terminal device; when it is determined that the terminal device is in the flight state, the processing unit 1401 is configured to determine based on the movement information and/or the fifth indication information from the application layer In the flight state, the fifth indication information instructs the terminal device to enter the flight mode.
  • the processing unit 1401 is further configured to determine that a second condition is met, wherein the second condition includes one or more of the following conditions: the terminal device is revoked and the unmanned The drone service is authorized, the terminal device is not authorized for the drone service, the drone service of the terminal device is deregistered, or the terminal device releases the last drone service corresponding to Conversation;
  • the first device is a first session management function device.
  • the transceiver unit 1402 is further configured to receive the seventh message from the terminal device, and the processing unit 1401 is further configured to establish or modify the seventh message according to the seventh message.
  • a session corresponding to non-UAV services wherein the seventh message is used to request the establishment or modification of a session corresponding to non-UAV services;
  • the first device is a short message service center
  • the transceiver unit 1402 is further configured to send an eighth message to the terminal device, where the eighth message is used to request the establishment or modification of the non-UAV service correspondence. conversation;
  • the first device is the 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 the establishment or modification of the non-UAV service. corresponding session.
  • the processing unit 1401 is further configured to determine that a second condition is met, wherein the second condition includes one or more of the following conditions: the terminal device is revoked and the unmanned The drone service is authorized, the terminal device is not authorized for the drone service, the drone service of the terminal device is deregistered, or the terminal device releases the last drone service corresponding to Session; transceiver unit 1402, further configured to receive a fourth message from a third device, the fourth message being used to request execution of the first control plane process; processing unit 1401, further configured to execute the first control plane process process.
  • the communication device 1400 can implement the functions or steps implemented by the second device in each of the above method embodiments.
  • the transceiver unit 1402 is configured to receive a message from the first session management function device requesting restriction of non-UAV services of the terminal device.
  • the processing unit 1401 is configured to determine, according to the message, that the second session management function device manages a session corresponding to the non-UAV service of the terminal device.
  • the transceiver unit 1402 is further configured to send instruction information to the second session management function device, where the instruction information is used to instruct the release of all or part of the non-UAV services managed by the second session management function device.
  • the corresponding session and/or indicates that establishment or modification of the session corresponding to the non-UAV business is prohibited.
  • the transceiver unit 1402 is further configured to send first instruction information to the first session management function device, where the first instruction information is used to instruct the release of one or more non-UAV services. corresponding session.
  • the transceiving unit 1402 is further configured to receive information from the first session management function.
  • N is the number of sessions corresponding to the non-UAV business managed by the first session management function device;
  • the processing unit 1401 is further configured to be configured according to the The number of sessions corresponding to the non-UAV service, the N and M, determine that the first session management function device needs to release one or more sessions corresponding to the non-UAV service, wherein the M is the number of sessions corresponding to the non-UAV service that the terminal device allows to be established at the first session management function device when executing the UAV service.
  • FIG. 15 shows a communication device 1500 provided by an embodiment of the present application.
  • the communication device 1500 may be a first device capable of realizing the functions of the first device in the method provided by an embodiment of the present application.
  • the communication device 1500 may be The second device can realize the functions of the second device in the method provided by the embodiments of this application; or, the communication device 1500 can also be a device that can support the first device to realize the corresponding functions in the method provided by the embodiments of this application, or can A device that supports the second device to implement the corresponding function in the method provided by the embodiment of the present application.
  • the communication device 1500 may be a chip system. In the embodiments of this application, the chip system may be composed of chips, or may include chips and other discrete devices.
  • the communication device 1500 includes at least one processor 1520, which is used to implement or support the communication device 1500 to implement the functions of the first device or the second device in the method provided by the embodiment of the present application. For details, please refer to the detailed description in the method example and will not be repeated here.
  • the communication device 1500 may also include at least one memory 1530 for storing program instructions and/or data.
  • Memory 1530 and processor 1520 are coupled.
  • the coupling in the embodiment of this application is an indirect coupling or communication connection between devices, units or modules, which may be in electrical, mechanical or other forms, and is used for information interaction between devices, units or modules.
  • the processor 1520 may cooperate with the memory 1530.
  • the processor 1520 may execute program instructions and/or data stored in the memory 1530, so that the communication device 1500 implements the corresponding method.
  • At least one of the at least one memory may be included in the processor.
  • the memory 1530 may exist independently, such as an off-chip memory, and is connected to the processor 1520 through a communication bus (indicated by a thick line 1540 in Figure 15).
  • the memory 1530 may also be integrated with the processor 1520.
  • the communication device 1500 may also include a communication interface 1510 for communicating with other devices through a transmission medium, so that the devices used in the communication device 1500 can communicate with other devices.
  • a communication interface 1510 for communicating with other devices through a transmission medium, so that the devices used in the communication device 1500 can communicate with other devices.
  • Processor 1520 may utilize communication interface 1510 to send and receive data.
  • the communication interface 1510 may specifically be a transceiver.
  • the above-mentioned transceiver unit 1402 may be a transceiver, and the transceiver is integrated in the communication device 1500 to form the communication interface 1510.
  • connection medium between the communication interface 1510, the processor 1520 and the memory 1530 is not limited in the embodiment of the present application.
  • the memory 1530, the processor 1520 and the communication interface 1510 are connected through the communication bus 1540.
  • the connection methods between other components are only schematically illustrated and are not limiting.
  • the communication bus 1540 can be divided into an address bus, a data bus, a control bus, etc. For ease of presentation, only one thick line is used in Figure 15, but it does not mean that there is only one communication bus or one type of communication bus.
  • the processor 1520 may be a general 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 can be implemented Or execute the disclosed methods, steps and logical block diagrams in the embodiments of this application.
  • general purpose processor It can be a microprocessor or any conventional processor, etc.
  • the steps of the methods disclosed in conjunction with the embodiments of the present application can be directly implemented by a hardware processor, or executed by a combination of hardware and software modules in the processor.
  • the memory 1530 can be a non-volatile memory, such as a hard disk drive (HDD) or a solid-state drive (SSD), etc., or it can also be a volatile memory (volatile memory), For example, random-access memory (RAM).
  • Memory is, but is not limited to, any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer.
  • the memory in the embodiment of the present application can also be a circuit or any other device capable of realizing a storage function, used to store program instructions and/or data.
  • An embodiment of the present application also provides a communication system.
  • the communication system includes a first device and/or a second device.
  • An embodiment of the present application also provides a computer-readable storage medium, which includes instructions that, when run on a computer, cause the computer to execute the methods in each of the above embodiments.
  • An embodiment of the present application also provides a computer program product, which includes instructions that, when run on a computer, cause the computer to execute the methods in each of the above embodiments.
  • Embodiments of the present application provide a chip system, which includes a processor and may also include a memory for implementing the functions of the first device or the second device in the foregoing method.
  • the chip system can be composed of chips or include chips and other discrete devices.
  • the size of the sequence numbers of the above-mentioned processes does not mean the order of execution.
  • the execution order of each process should be determined by its functions and internal logic, and should not be used in the embodiments of the present application.
  • the implementation process constitutes any limitation.
  • the disclosed systems, devices and methods can be implemented in other ways.
  • the device embodiments described above are only illustrative.
  • the division of the units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components may be combined or can be integrated into another system, or some features can be ignored, or not implemented.
  • the coupling or direct coupling or communication connection between each other shown or discussed may be through some interfaces, and the indirect coupling or communication connection of the devices or units may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place, or they may be distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.
  • each functional unit in each embodiment of the present application can be integrated into one processing unit, each unit can exist physically alone, or two or more units can be integrated into one unit.
  • the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium.
  • the technical solution of this application is essentially The part that has made technical contributions or the part of the technical solution can be embodied in the form of a software product.
  • the computer software product is stored in a storage medium and includes a number of instructions to enable a computer device (which can be a personal computer, server , or network equipment, etc.) perform all or part of the steps of the methods described in various embodiments of this application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk or optical disk and other media that can store program code. .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请提供一种通信方法及装置，在该方法中，第一设备确定满足第一条件，以及限制终端设备的非无人机业务和/或限制终端设备的第一控制面流程。其中，第一条件包括如下条件中的一种或多种：终端设备被授权无人机业务，终端设备发起建立第一个无人机业务对应的会话，或者终端设备处于飞行状态，第一控制面流程不是无人机业务专有的流程。通过本申请，第一设备有条件地限制终端设备的非无人机业务可以减少攻击者利用非无人机业务对终端设备的攻击，提高终端设备的安全性。第一设备有条件地限制终端设备的第一控制面流程，释放了执行第一控制面流程所需的资源，从而能够为无人机业务提供更多的可使用资源。

Description

一种通信方法及装置
相关申请的交叉引用
本申请要求在2022年06月28日提交中国国家知识产权局、申请号为202210752034.0、申请名称为“一种通信方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种通信方法及装置。
背景技术
无人机系统(unmanned/uncrewed aerial system，UAS)包括无人机(unmanned/uncrewed aerial vehicle，UAV)和无人机的遥控器(UAV controller，UAVC)。该无人机的遥控器可简称为遥控器或遥控设备等。无人机可以自主飞行，也可以根据遥控器的控制指令进行飞行。即无人机和遥控器之间可以进行通信，例如，遥控器可以向无人机发送控制指令，以使得无人机在航拍后将拍摄的照片或视频发送给遥控器。
无人机系统可以与移动通信网络相结合以便充分利用移动通信网络的优势，如广域覆盖、高可靠性以及支持高速移动业务等，将无人机系统拓展到实现超视距(远程)高可靠的飞行，从而使能无人机系统获得更广泛的应用、市场。即，无人机同时兼具两个角色：一个是移动通信网络中的终端，另一个是无人机系统中可以飞行的无人机。对于移动通信网络而言，移动通信网络不仅可以为无人机提供普通终端所享有的业务(如多媒体通信、数据业务等)，还可以为无人机提供无人机专有的业务(如远程定位、禁飞围栏等)。
无人机兼顾的两个角色使得无人机面临如下问题：在无人机飞行中，攻击者利用移动通信网络实施针对无人机的拒绝服务(denial of service，DoS)攻击，如向无人机发送大量非无人机业务的数据，恶意挤占无人机的资源(如网络资源、计算资源、电池资源等)，影响无人机的正常工作，造成无人机偏离航线，无法预期到达目的地址，甚至导致无人机坠落等问题。因此，如何减少攻击者利用非无人机业务对无人机的攻击是亟需解决的问题。
发明内容
本申请实施例提供一种通信方法及装置，用以减少攻击者利用非无人机业务对无人机的攻击，提高无人机的安全性。
第一方面，本申请提供一种通信方法，该方法可以由第一设备执行，或者由第一设备的部件(如芯片)执行。在该方法中，第一设备确定满足第一条件，所述第一条件包括如下条件中的一种或多种：终端设备被授权无人机业务，所述终端设备发起建立第一个所述无人机业务对应的会话，或者所述终端设备处于飞行状态；所述第一设备限制所述终端设备的非无人机业务和/或限制所述终端设备的第一控制面流程，其中，所述第一控制面流程不是所述无人机业务专有的流程。
在本申请实施例中，第一设备有条件地限制终端设备的非无人机业务可以减少攻击者 利用非无人机业务对终端设备的攻击，提高终端设备的安全性。第一设备有条件地限制终端设备的第一控制面流程，释放了执行第一控制面流程所需的资源，从而能够为无人机业务提供更多的可使用资源。
例如，终端设备被授权无人机业务，意味着该终端设备支持同时执行无人机业务和非无人机业务，在此情况下，第一设备限制该终端设备的非无人机业务，能够减少攻击者利用非无人机业务对终端设备的攻击，避免非无人机业务侵占无人机业务的资源。或者，终端设备被授权无人机业务，第一设备可以限制第一控制面流程，可以释放执行该第一控制面流程所需的资源，从而能够为终端设备预留更多该授权的无人机业务可使用的资源。
又例如，终端设备发起建立第一个无人机业务对应的会话，意味着终端设备将要执行无人机业务，在此情况下，第一设备限制终端设备的非无人机业务，能够减少攻击者在终端设备执行无人机业务的过程中利用非无人机业务对该终端设备的攻击，以及避免非无人机业务在终端设备执行无人机业务的过程中侵占该无人机业务的资源。或者，终端设备发起建立第一个无人机业务对应的会话，第一设备限制第一控制面流程，可以释放执行该第一控制面流程所需的资源，增加了该无人机业务可使用的资源。
再例如，终端设备处于飞行状态，第一设备限制终端设备非无人机业务，能够减少攻击者利用非无人机业务对飞行中的终端设备的攻击，可以避免因非无人机业务占用该终端设备的大量资源导致该终端设备偏离航线、无法到达预期目的地址等问题，提高了终端设备的安全性。或者，终端设备处于飞行状态，第一设备限制第一控制面流程，可以为飞行中的终端设备预留更多无人机业务可使用的资源，避免了飞行中的终端设备因资源不足导致终端设备无法正常工作，甚至坠毁等问题。
在一种可能的实现方式中，所述第一设备限制所述终端设备的非无人机业务，具体可以为如下中的任一项一种：
所述第一设备是第一会话管理功能设备，所述第一设备释放所述第一设备管理的全部或部分的所述非无人机业务对应的会话，和/或禁止建立或禁止修改所述非无人机业务对应的会话。
或者，所述第一设备是短消息业务服务中心，所述第一设备不向或暂停向所述终端设备发送第一消息，所述第一消息用于请求建立或修改所述非无人机业务对应的会话。
或者，所述第一设备是所述终端设备，所述第一设备不向或暂停向第一会话管理功能设备发送第一消息，所述第一消息用于请求建立或修改所述非无人机业务对应的会话。
通过上述实现方式中，第一设备可以通过释放非无人机业务对应的会话、禁止建立或禁止修改非无人机业务对应的会话、或者不向终端设备或会话管理功能设备发送用于请求建立或修改非无人机业务对应的会话的消息等多种措施实现对终端设备的非无人机业务的限制，实现方式灵活。
在一种可能的实现方式中，若所述第一设备确定所述终端设备被授权所述无人机业务，和/或所述终端设备处于飞行状态，在所述第一设备限制所述终端设备的非无人机业务和/或限制所述第一控制面流程之前，该方法还可以包括：所述第一设备接收来自所述终端设备的第二消息，所述第二消息用于请求建立第一会话；以及，所述第一设备根据所述第二消息，确定所述第一会话属于所述无人机业务对应的会话。
通过上述实现方式中，若终端设备被授权无人机业务和/或处于飞行状态，第一设备可以确定接收到的会话建立请求消息是否用于建立无人机业务对应的会话。例如，第一会话 属于无人机业务对应的会话，第一设备限制无人机业务和/或限制第一控制面流程。又例如，第一会话属于非无人机业务对应的会话，意味着第一设备已释放非无人机业务的会话和/或终端设备还未建立第一个无人机业务对应的会话，资源充足，在此情况下，第一设备可以不限制非无人机业务和/或，从而能够在减少对无人机业务的影响的情况下提高资源的利用率。
在一种可能的实现方式中，该方法还可以包括：所述第一设备向第二设备发送第三消息，所述第三消息用于请求限制所述终端设备的所述非无人机业务。
通过上述实现方式中，第一设备在确定限制终端设备的非无人机业务后，可以向第二设备发送第三消息，以便第二设备限制终端设备的非无人机业务。
在一种可能的实现方式中，该方法还可以包括：所述第一设备接收来自所述第二设备的第一指示信息，所述第一指示信息用于指示释放一个或多个所述非无人机业务对应的会话。相应的，第一设备限制所述终端设备的非无人机业务可以为：该第一设备根据第一指示信息释放一个或多个所述非无人机业务对应的会话。
在另一种可能的实现方式中，所述第一设备限制所述终端设备的非无人机业务包括所述第一设备释放所述第一设备管理的全部或部分的所述非无人机业务对应的会话，该方法还可以包括：所述第一设备确定N大于M，其中，所述N是所述第一设备所管理的所述非无人机业务对应的会话的数量，所述M是所述终端设备在执行所述无人机业务时允许在所述第一设备处建立的所述非无人机业务对应的会话的数量；所述第一设备确定释放H个所述非无人机业务对应的会话，所述H为大于或等于(N-M)的正整数。
通过上述实现方式，第一设备可以根据第二设备的指示信息释放一个或多个非无人机业务对应的会话，也可以根据N和M释放一个或多个非无人机业务对应的会话，实现方式灵活。
在一种可能的实现方式中，所述第一设备限制所述终端设备的非无人机业务，可以为：所述第一设备向所述终端设备发送第二指示信息，所述第二指示信息指示禁止建立所述非无人机业务对应的会话。
通过上述实现方式，第一设备指示终端设备禁止建立非无人机业务对应的会话，这样可以使得终端设备不发起非无人机业务对应的会话，从而达到限制该终端设备的非无人机业务的目的。
在一种可能的实现方式中，所述第一控制面流程包括首次认证流程、去注册流程、切片认证流程或二次认证流程中的一项或多项。
在一种可能的实现方式中，所述第一设备限制所述终端设备的第一控制面流程，可以为：所述第一设备暂停或终止所述第一控制面流程。
通过上述实现方式，第一设备可以暂停或终止第一控制面流程，第一控制面流程不是无人机业务的专有流程，这样第一控制面流程的暂停或终止不会不利于无人机业务的执行，并且可以释放执行第一控制面流程所需的资源，从而能够为无人机业务提供更多可用的资源，有利于无人机业务的执行。
在一种可能的实现方式中，在所述第一设备暂停所述第一控制面流程之后，所述方法还包括：所述第一设备启动第一计时器；所述第一设备确定在所述第一计时器的运行期间所述终端设备满足所述第一条件；所述第一设备在所述第一计时器运行结束时终止所述第一控制面流程。
通过上述实现方式，第一设备可以先暂停第一控制面流程，若在计时器运行期间内终端设备满足第一条件，则第一设备可以终止该第一控制面流程，而若在计时器运行期间内终端设备不满足第一条件，则第一设备可以执行第一控制面流程。
在一种可能的实现方式中，该方法还可以包括：所述第一设备接收来自第三设备的第四消息，所述第四消息用于请求执行所述第一控制面流程；所述第一设备向所述第三设备发送第五消息，所述第五消息包括不进行所述第一控制流程的原因。
通过上述实现方式，在第一设备暂停或终止第一控制面流程的情况下，第一设备可以向第三设备反馈不执行第一控制面流程的原因。该不执行第一控制面流程的原因例如可以是终端设备满足第一条件。
在一种可能的实现方式中，所述第一设备确定终端设备处于飞行状态，可以为：所述第一设备接收来自接入与移动性管理功能设备的第三指示信息，所述第三指示信息指示所述终端设备处于飞行状态。可选地，所述第一设备向所述接入与移动性管理功能网元发送第六消息，其中，所述第六消息用于获取所述终端设备的状态，所述终端设备的状态包括飞行状态或/和非飞行状态。
通过上述实现方式，第一设备可以从接入与移动性管理功能设备处获取终端设备的状态。该终端设备的状态可以是接入与移动性管理功能设备主动推送的，或者可以是第一设备通过向接入与移动性管理功能设备订阅终端设备的状态得到的，实现方式灵活。
在一种可能的实现方式中，所述第一设备为接入与移动性管理功能设备；所述第一设备确定终端设备处于飞行状态，具体可以为：所述第一设备接收来自第四设备的第四指示信息，所述第四指示信息用于指示所述终端设备处于飞行状态；或者，所述第一设备根据所述终端设备的移动信息和/或所述终端设备的飞行信息，确定所述终端设备处于飞行状态。
通过上述实现方式，接入与移动性管理功能设备可以从第四设备处获取终端设备处于飞行状态，也可以根据终端设备的移动信息和/或飞行信息确定终端设备处于飞行状态，实现方式灵活。
在一种可能的实现方式中，所述第一设备为所述终端设备；所述第一设备确定终端设备处于飞行状态，可以为：所述第一设备根据移动信息和/或来自应用层的第五指示信息确定处于飞行状态，其中，所述第五指示信息指示所述终端设备进入飞行模式。
通过上述实现方式，终端设备可以确定自身是否处于飞行状态。
在一种可能的实现方式中，该方法还可以包括：所述第一设备确定满足第二条件，其中，所述第二条件包括如下条件中的一种或多种：所述终端设备被撤销所述无人机业务的授权，所述终端设备不被授权所述无人机业务，所述终端设备的所述无人机业务被去注册，或者所述终端设备释放最后一个所述无人机业务对应的会话；
所述第一设备是第一会话管理功能设备，所述第一设备接收来自所述终端设备的第七消息，并根据所述第七消息建立或修改所述非无人机业务对应的会话，其中，所述第七消息用于请求建立或修改所述非无人机业务对应的会话；
或者，所述第一设备是短消息业务服务中心，所述第一设备向所述终端设备发送第八消息，所述第八消息用于请求建立或修改所述非无人机业务对应的会话；
或者，所述第一设备是所述终端设备，所述第一设备向第一会话管理功能设备发送第八消息，所述第八消息用于请求建立或修改所述非无人机业务对应的会话。
通过上述实现方式，在第一设备确定满足第二条件的情况下，第一设备取消对终端设 备的非无人机业务的限制，使得第一设备能够执行非无人机业务，能够提高兼容性。
在一种可能的实现方式中，该方法还可以包括：所述第一设备确定满足第二条件，其中，所述第二条件包括如下条件中的一种或多种：所述终端设备被撤销所述无人机业务的授权，所述终端设备不被授权所述无人机业务，所述终端设备的所述无人机业务被去注册，或者所述终端设备释放最后一个所述无人机业务对应的会话；所述第一设备接收来自第三设备的第四消息，所述第四消息用于请求执行所述第一控制面流程；所述第一设备执行所述第一控制面流程。
通过上述实现方法，在第一设备确定满足第二条件的情况下，第一设备取消对第一控制面流程的限制，使得第一设备能够执行第一控制面流程，能够提高兼容性。
第二方面，本申请提供一种通信方法，该方法可以由第二设备执行，或者由第二设备的部件(如芯片)执行。在该方法中：第二设备接收来自第一会话管理功能设备的用于请求限制所述终端设备的非无人机业务的消息；所述第二设备根据所述消息，确定第二会话管理功能设备管理有所述终端设备的非无人机业务对应的会话；所述第二设备向所述第二会话管理功能设备发送指示信息，其中，所述指示信息用于指示释放所述第二会话管理功能设备管理的全部或部分所述非无人机业务对应的会话，和/或指示禁止建立或禁止修改所述非无人机业务对应的会话。
在本申请实施例中，第二设备响应于限制终端设备的非无人机业务的消息，确定管理有该终端设备的非无人机业务对应的会话的会话管理功能设备，并向该会话管理功能设备发送指示信息，以指示该会话管理功能设备限制该终端设备非无人机业务，从而能够减少攻击者利用非无人机业务对无人机的攻击，避免非无人机业务侵占无人机业务的资源。
在一种可能的实现方式中，该方法还可以包括：所述第二设备向所述第一会话管理功能设备发送第一指示信息，所述第一指示信息用于指示释放一个或多个非无人机业务对应的会话。
在一种可能的实现方式中，该方法还可以包括：所述第二设备接收来自所述第一会话管理功能设备的N，其中，所述N是所述第一会话管理功能设备所管理的所述非无人机业务对应的会话的数量；所述第二设备根据所述终端设备已建立的所述非无人机业务对应的会话的数量，所述N和M，确定所述第一会话管理功能设备需要释放一个或多个所述非无人机业务对应的会话，其中，所述M是所述终端设备在执行所述无人机业务时允许在所述第一会话管理功能设备处建立的所述非无人机业务对应的会话的数量。
通过上述实现方法，第二设备可以维护终端设备已建立的非无人机业务对应的会话的数量，并结合N和M确定终端设备所对应的一个或多个会话管理功能设备中的每个会话管理功能设备所需要释放的非无人机业务对应的会话的数量。
第三方面，本申请提供一种通信装置。所述通信装置用于执行为上述第一方面及第一方面任一项可能的实现方式中所述的方法。该通信装置例如为第一设备，或为第一设备中的功能模块，例如基带装置或芯片系统等。
一种可能的实现方式中，所述通信装置包括基带装置和射频装置。另一种可能的实现方式中，所述通信装置包括处理单元(有时也称为处理模块)和收发单元(有时也称为收发模块)。收发单元能够实现发送功能和接收功能，在收发单元实现发送功能时，可称为发送单元(有时也称为发送模块)，在收发单元实现接收功能时，可称为接收单元(有时也称为接收模块)。发送单元和接收单元可以是同一个功能单元，该功能单元称为收发单 元，该功能单元能实现发送功能和接收功能；或者，发送单元和接收单元可以是不同的功能单元，收发单元是对这些功能单元的统称。
第四方面，本申请提供一种通信装置。所述通信装置用于执行为上述第二方面及第二方面任一项可能的实现方式中所述的方法。该通信装置例如为第二设备，或为第二设备中的功能模块，例如基带装置或芯片系统等。
一种可能的实现方式中，所述通信装置包括基带装置和射频装置。另一种可能的实现方式中，所述通信装置包括处理单元(有时也称为处理模块)和收发单元(有时也称为收发模块)。收发单元能够实现发送功能和接收功能，在收发单元实现发送功能时，可称为发送单元(有时也称为发送模块)，在收发单元实现接收功能时，可称为接收单元(有时也称为接收模块)。发送单元和接收单元可以是同一个功能单元，该功能单元称为收发单元，该功能单元能实现发送功能和接收功能；或者，发送单元和接收单元可以是不同的功能单元，收发单元是对这些功能单元的统称。
第五方面，本申请提供一种通信装置。所述通信装置可以包括一个或多个处理器。可选地，该通信装置还可以包括存储器。其中，所述存储器用于存储一个或多个计算机程序或指令。所述一个或多个处理器用于执行所述存储器存储的所述一个或多个计算机程序或指令，以使得所述通信装置执行上述第一方面及第一方面任一项可能的实现方式中所述的方法。
第六方面，本申请提供一种通信装置。所述通信装置可以包括一个或多个处理器。可选地，该通信装置还可以包括存储器。其中，所述存储器用于存储一个或多个计算机程序或指令。所述一个或多个处理器用于执行所述存储器存储的所述一个或多个计算机程序或指令，以使得所述通信装置执行上述第二方面及第二方面任一项可能的实现方式中所述的方法。
第七方面，本申请提供一种通信系统。所述通信系统包括上述第五方面所述的通信装置，和/或，上述第六方面所述的通信装置。
第八方面，本申请提供一种计算机可读存储介质，所述计算机可读存储介质用于存储计算机程序或指令，当其被运行时，使得上述第一方面及第一方面任一项可能的实现方式中所述的方法被实现，或者使得上述第二方面及第二方面任一项可能的实现方式中所述的方法被实现。
第九方面，本申请提供一种包含指令的计算机程序产品，当其在计算机上运行时，使得上述第一方面及第一方面任一项可能的实现方式中所述的方法被实现，或者使得上述第二方面及第二方面任一项可能的实现方式中所述的方法被实现。
第十方面，本申请还提供一种芯片，所述芯片与存储器耦合，用于读取并执行所述存储器中的程序指令，以使得所述芯片所在装置实现上述第一方面及第一方面任一项可能的实现方式中所述的方法，或实现上述第二方面及第二方面任一项可能的实现方式中所述的方法。可选地，该芯片系统可以由芯片构成，也可以包含芯片和其他分立器件。
上述第三方面至第十方面及其任一项可能的实现方式所能达到的技术效果请相应参照上述第一方面至第二方面及其任一项可能的实现方式所能达到的技术效果，这里不再重复赘述。
附图说明
图1为网络架构的一种示意图；
图2为网络架构的又一种示意图；
图3为无人机业务与非无人机业务的一种示意图；
图4为本申请实施例提供的通信方法的一种流程示意图；
图5为本申请实施例提供的通信方法的又一种流程示意图；
图6为本申请实施例提供的通信方法的又一种流程示意图；
图7为本申请实施例提供的通信方法的又一种流程示意图；
图8为本申请实施例提供的通信方法的又一种流程示意图；
图9为本申请实施例提供的通信方法的又一种流程示意图；
图10为本申请实施例提供的通信方法的再一种流程示意图；
图11为本申请实施例提供的通信方法的再一种流程示意图；
图12为本申请实施例提供的通信方法的再一种流程示意图；
图13为本申请实施例提供的通信方法的再一种流程示意图；
图14为本申请实施例提供的通信装置的一种结构示意图；
图15为本申请实施例提供的通信装置的又一种结构示意图。
具体实施方式
为了使本申请实施例的目的、技术方案和优点更加清楚，下面先介绍本申请实施例涉及的部分术语。
(1)终端设备，也可以称为用户设备(user equipment，UE)、接入终端、终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、用户代理或用户装置等。终端设备例如可以是蜂窝电话(cellular phone)、无绳电话、会话启动协议(session initiation protocol，SIP)电话、智能电话(smart phone)、手机(mobile phone)、无线本地环路(wireless local loop，WLL)站、个人数字处理(personal digital assistant，PDA)等。或者，终端设备还可以是具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它设备、车载设备、可穿戴设备、无人机或物联网、车联网中的终端、5G网络以及未来网络中的任意形态的终端、中继用户设备或者未来演进的6G网络中的终端等。本申请实施例对终端设备的类型或种类等并不限定。
终端设备的功能可以通过终端设备内部的硬件部件来实现，所述硬件部件可以为所述终端设备内部的处理器和/或可编程的芯片。可选地，该芯片可以通过专用集成电路(application-specific integrated circuit，ASIC)实现，或可编程逻辑器件(programmable logic device，PLD)实现。上述PLD可以是复杂程序逻辑器件(complex programmable logical device，CPLD)，现场可编程门阵列(field-programmable gate array，FPGA)，通用阵列逻辑(generic array logic，GAL)，片上系统(system on a chip，SOC)中的任一项或其任意组合。
另外，为了便于理解本申请实施例，下文以终端设备为无人机为例进行介绍。
(2)无人机业务，是指无人机享有的专门用于无人机的业务或服务。该无人机业务可以是网络在控制面(control plane)和/或用户面(user plane)为无人机提供的通信业务 或服务。例如，无人机业务可以是无人机专有或者专门用于无人机的控制面流程(如无人机认证、授权、或飞行路线授权等)，命令与控制(command and control，C2)通信，远程识别无人机，远程定位，禁飞围栏，或者飞行地图下载服务等，但本申请实施例对无人机业务的类型并不限定于此。
(3)非无人机业务，是指除了无人机业务之外的业务，可理解为普通终端设备所享有的业务。该非无人机业务例如可以为多媒体通信业务，数据业务或互联网业务等，但本申请实施例对非无人机业务的类型并不限定于此。
需要说明的是，当网络无法识别无人机的类型时(如，识别无人机成普通终端时)或者没有授权无人机的无人机业务时，无人机可以被当成是普通终端设备，此时网络提供给该无人机的业务属于非无人机业务。
(4)本申请实施例中“多个”是指两个或两个以上，鉴于此，本申请实施例中也可以将“多个”理解为“至少两个”。“至少一个”，可理解为一个或多个，例如理解为一个、两个或更多个。例如，包括至少一个，是指包括一个、两个或更多个，而且不限制包括的是哪几个，例如，包括A、B和C中的至少一个，那么包括的可以是A、B、C、A和B、A和C、B和C、或A和B和C。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，字符“/”，如无特殊说明，一般表示前后关联对象是一种“或”的关系。本申请实施例中的术语“系统”和“网络”可被互换使用。
除非有相反的说明，本申请实施例提及“第一”、“第二”等序数词用于对多个对象进行区分，不用于限定多个对象的顺序、时序、优先级或者重要程度。例如，本申请实施例涉及的第一设备、第二设备、第三设备以及第四设备用于对多个设备进行区分，并不限定该多个设备的优先级或重要程度。又例如，本申请实施例涉及的第一消息、第二消息、第三消息以及第四消息等用于对多个消息进行区别，并不限定该多个消息的顺序、时序、优先级或重要程度。
另外，在本申请实施例中，“示例性的”一词用于表示作例子、例证或说明。本申请中被描述为“示例性的”的任何实施例或设计方案不应被解释为比其他实施例或设计方案更优选或更具优势。确切而言，使用“示例性的”一词旨在以具体方式呈现概念。
本申请将围绕可包括多个设备、组件、模块等的系统来呈现各个方面、实施例或特征。应当理解和明白的是，各个系统可以包括另外的设备、组件、模块等，并且/或者可以并不包括结合附图讨论的所有设备、组件、模块等。此外，还可以使用这些方案的组合。
前面介绍了本申请实施例涉及的部分术语，接下来介绍本申请实施例适用的通信系统。
需要说明的是，本申请实施例描述的网络架构以及业务场景是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
本申请实施例的技术方案可以应用于各种通信系统。一个通信系统中，由运营者运营的部分可称为公共陆地移动网络(public land mobile network，PLMN)(也可以称为运营商网络、移动通信网络等)。PLMN是由政府或其所批准的经营者，为公众提供陆地移动通信业务目的而建立和经营的网络，主要是移动网络运营商(mobile network operator，MNO) 为用户提供移动宽带接入服务的公共网络。本申请中所描述的PLMN，具体可以为符合第三代合作伙伴项目(3rd generation partnership project，3GPP)标准要求的网络，简称3GPP网络。3GPP网络通常包括但不限于第五代移动通信(5th-generation，5G)网络(简称5G网络)、第四代移动通信(4th-generation，4G)网络(简称4G网络)以及未来的其他通信系统如6G网络等。为了方便描述，本申请实施例中将以PLMN或5G网络为例进行说明。
图1是本申请实施例的一种网络架构示意图，它以3GPP标准化过程中定义的非漫游场景下基于服务化架构的5G网络架构为例。该网络架构可以包括三部分，分别是终端设备部分、数据网络(data network，DN)部分和PLMN部分。
终端设备部分可以包括终端设备110，可通过运营商网络提供的接口(例如N1等)与运营商网络建立连接，使用运营商网络提供的数据和/或语音等服务。终端设备110还可通过运营商网络访问数据网络120，使用数据网络120上部署的运营商业务，和/或第三方提供的业务。其中，上述第三方可为运营商网络和终端设备110之外的服务方，可为终端设备110提供其他数据和/或语音等服务。其中，上述第三方的具体表现形式，具体可根据实际应用场景确定，在此不做限制。有关终端设备110的介绍请参考前述术语解释部分对终端设备的介绍，此处不再赘述。
数据网络120，也可以称为分组数据网络(packet data network，PDN)，通常是位于运营商网络之外的网络，例如第三方网络。运营商网络可以接入多个数据网络120，数据网络120上可部署多种业务，可为终端设备110提供数据和/或语音等服务。例如，数据网络120可以是某智能工厂的私有网络，智能工厂安装在车间的传感器可以是终端设备110，数据网络120中部署了传感器的控制服务器，控制服务器可为传感器提供服务。传感器可与控制服务器通信，获取控制服务器的指令，根据指令将采集的传感器数据传送给控制服务器等。又例如，数据网络120可以是某公司的内部办公网络，该公司员工的手机或者电脑可为终端设备110，员工的手机或者电脑可以访问公司内部办公网络上的信息、数据资源等。
PLMN可以包括但不限于：网络开放功能(network exposure function，NEF)131、网络存储功能(network function repository function，NRF)132、策略控制功能(policy control function，PCF)133、统一数据管理(unified data management，UDM)134、无人机系统功能(unmanned/uncrewed aerial system，UAS)135、认证服务器功能(authentication server function，AUSF)136、接入与移动性管理功能(access and mobility management function，AMF)137、会话管理功能(session management function，SMF)138、用户面功能(user plane function，UPF)139、(无线)接入网((radio)access network，(R)AN)140、应用功能(application function，AF)141、网络切片认证授权功能(network slice specific authentication and authorization function，NSSAAF)142等。上述PLMN中，除(无线)接入网140部分之外的部分可以称为核心网(core network，CN)部分。
示例性的，下面对本申请的各个实施例可能涉及的网络功能进行简要介绍，另外图1还涉及其他网元，在此不做过多介绍。
AN 140，也称无线(Radio)AN，可以看作是运营商网络的子网络，是运营商网络中业务节点与终端设备110之间的实施系统。终端设备110要接入运营商网络，首先是经过(R)AN 140，进而可通过(R)AN 140与运营商网络的业务节点连接。本申请实施例中的接入网设备(RAN设备)，是一种为终端设备110提供无线通信功能的设备，也可以称为网络 设备，RAN设备包括但不限于：5G系统中的下一代基站节点(next generation node base station，gNB)、长期演进(long term evolution，LTE)中的演进型节点B(evolved node B，eNB)、无线网络控制器(radio network controller，RNC)、节点B(node B，NB)、基站控制器(base station controller，BSC)、基站收发台(base transceiver station，BTS)、家庭基站(例如，home evolved nodeB，或home node B，HNB)、基带单元(base band unit，BBU)、传输点(transmitting and receiving point，TRP)、发射点(transmitting point，TP)、小基站设备(pico)、移动交换中心，或者未来网络中的网络设备等。采用不同无线接入技术的系统中，具备接入网设备功能的设备的名称可能会有所不同。为方便描述，本申请所有实施例中，上述为终端设备110提供无线通信功能的装置统称为接入网设备或简称为RAN或AN。应理解，本文对接入网设备的具体类型不作限定。
网络开放功能131，是由运营商提供的控制面功能，用于使能第三方使用网络提供的服务。例如，在5G通信系统中，网络开放功能131可以是NEF，如图1所示；在未来通信系统，如6G通信系统中，网络开放功能131仍可以是NEF，或可能有其它的名称，本申请实施例不做限定。
网络存储功能132，是由运营商提供的控制面功能，可用于维护网络中所有网络功能服务的实时信息。例如，在5G通信系统中，网络存储功能132可以是NRF，如图1所示；在未来通信系统，如6G通信系统中，网络存储功能132仍可以是NRF，或可能有其它的名称，本申请实施例不做限定。
策略控制功能133，是由运营商提供的控制面功能，它支持统一的策略框架来治理网络行为、向其他控制功能提供策略规则、策略决策相关的签约信息等。例如，在5G通信系统中，策略控制功能133可以是PCF，如图1所示；在未来通信系统，如6G通信系统中，策略控制功能133仍可以是PCF，或可能有其它的名称，本申请实施例不做限定。
统一数据管理134，是由运营商提供的控制面功能，负责存储运营商网络中签约用户的用户永久标识符(subscriber permanent identifier，SUPI)、签约用户的公开使用的签约标识(generic public subscription identifier，GPSI)，信任状(credential)等信息。其中SUPI在传输过程中会先进行加密，加密后的SUPI被称为隐藏的用户签约标识符(subscription concealed identifier，SUCI)。统一数据管理134所存储的这些信息可用于终端设备110接入运营商网络的认证和授权。其中，上述运营商网络的签约用户具体可为使用运营商网络提供的业务的用户，例如使用中国电信的手机芯卡的用户，或者使用中国移动的手机芯卡的用户等。上述签约用户的信任状可为该手机芯卡存储的长期密钥或者跟该手机芯卡加密相关的信息等存储的小文件，用于认证和/或授权。需要说明的是，永久标识符、信任状、安全上下文、认证数据(cookie)、以及令牌等同验证/认证、授权相关的信息，在本申请实施例中，为了描述方便起见不做区分、限制。例如，在5G通信系统中，统一数据管理134可以是UDM，如图1所示；在未来通信系统，如6G通信系统中，统一数据管理134仍可以是UDM，或可能有其它的名称，本申请实施例不做限定。
无人机系统功能135，是由运营商提供的服务于无人机系统的控制面功能，负责将网络支持无人机业务能力开放给外部网络，例如它可以开放无人机认证/授权服务、无人机飞行授权服务、无人机和遥控器的配对授权、无人机的重认证/授权/吊销、无人机的位置信息报告、无人机服务质量(quality of service，QoS)控制、以及用于命令与控制(command and control，C2)通信的流量过滤等。无人机系统功能135可以是由网络开放功能131生 成的一个实例(instance)，或普通网络开放功能131的一个子功能，也可以是独立的专门用于提供无人机服务的功能，因此通常标注为UAS NF/NEF，但本申请实施例并不限定于此。
认证服务器功能136，是由运营商提供的控制面功能，通常用于一级认证，即终端设备110(签约用户)与PLMN之间的网络认证。认证服务器功能136接收到签约用户发起的认证请求之后，可通过统一数据管理134中存储的认证信息和/或授权信息对签约用户进行认证和/或授权，或者通过统一数据管理134生成签约用户的认证和/或授权信息。认证服务器功能136可向签约用户反馈认证信息和/或授权信息。例如，在5G通信系统中，认证服务器功能136可以是AUSF，如图1所示；在未来通信系统，如6G通信系统中，认证服务器功能136仍可以是AUSF，或可能有其它的名称，本申请实施例不做限定。
接入与移动性管理功能137，是由PLMN提供的控制面网络功能，负责终端设备110接入PLMN的接入控制和移动性管理，例如包括移动状态管理，分配用户临时身份标识，认证和授权用户等功能。例如，在5G通信系统中，接入与移动性管理功能137可以是AMF，如图1所示；在未来通信系统，如6G通信系统中，接入与移动性管理功能137仍可以是AMF，或可能有其它的名称，本申请实施例不做限定。
会话管理功能138，是由PLMN提供的控制面网络功能，负责管理终端设备110的协议数据单元(protocol data unit，PDU)。PDU会话是一个用于传输PDU的通道，终端设备需要通过PDU会话与DN 120互相传输数据。PDU会话可以由会话管理功能138负责建立、维护和删除等。会话管理功能138包括会话管理(如会话建立、修改和释放，包含用户面功能139和AN 140之间的隧道维护等)、用户面功能139的选择和控制、业务和会话连续性(service and session continuity，SSC)模式选择、漫游等会话相关的功能。例如，在5G通信系统中，会话管理功能138可以是SMF，如图1所示；在未来通信系统，如6G通信系统中，会话管理功能138仍可以是SMF，或可能有其它的名称，本申请实施例不做限定。
用户面功能139，是由PLMN提供的与数据网络DN 120进行通信的网关。用户面功能139包括数据包路由和传输、数据包检测、业务用量上报、服务质量(quality of service，QoS)处理、合法监听、上行数据包检测、下行数据包存储等用户面相关的功能。例如，在5G通信系统中，用户面功能139可以是UPF，如图1所示；在未来通信系统，如6G通信系统中，用户面功能139仍可以是UPF，或可能有其它的名称，本申请实施例不做限定。
应用功能141，是一个控制面功能，可以由运营商部署也可以是外部第三方部署。应用功能141通过与核心网的其他网络功能的交互，来支持流量路由控制、策略控制功能133交互、接入网功能开放等服务。例如，在5G通信系统中，应用功能141可以是AF，如图1所示；在未来通信系统，如6G通信系统中，应用功能141仍可以是AF，或可能有其它的名称，本申请实施例不做限定。
网络切片认证授权功能142，是由PLMN提供的控制面网络功能，用于支持终端设备110与数据网络120进行的切片认证。例如，在5G通信系统中，网络切片认证授权功能142可以是NSSAAF，如图1所示；在未来通信系统，如6G通信系统中，网络切片认证授权功能NSSAAF仍可以是SMF，或可能有其它的名称，本申请实施例不做限定。
其中，PLMN中的各个网络功能既可以是在专用硬件上实现的网络元件，也可以是在专用硬件上运行的软件实例，或者是在适当平台上虚拟化功能的实例，例如，上述虚拟化 平台可以为云平台。以及，该PLMN中的各个网络功能也可以称为网元、功能实体或者设备，例如，接入与移动性管理功能也可以称为接入与移动性管理功能网元、接入与移动性管理功能实体或接入与移动性管理功能设备等，会话管理功能也可以称为会话管理功能网元、会话管理功能实体或会话管理功能设备等，这里不再一一列举。
图1所示的PLMN中的网络功能还可以包括其他网络功能，例如，PLMN还包括统一数据存储(unified data repository，UDR)等(图1中未示出)，本申请实施例对于PLMN中包括的其他网络功能不作限定。另外，图1中所示的网络功能的名称在这里仅作为一种示例说明，并不作为对本申请实施例的方法适用的网络架构中包括的网络功能的限定。不同接入技术的系统中实现网络功能的设备名称可以不同，本申请实施例并不对此进行限定。
图1中Nnef、Nnrf、Npcf、Nudm、Nausf、Namf、Nsmf、Nnssaaf、Naf、N1、N2、N3、N4，以及N6为接口序列号。示例性的，上述接口序列号的含义可参见3GPP标准协议中定义的含义，本申请对于上述接口序列号的含义不做限制。需要说明的是，图1中的各个网络功能之间的接口名称也仅仅是一个示例，在具体实现中，该系统架构的接口名称还可能为其他名称，本申请对此不作限定。
需要说明的是，图1所示的网络架构并不构成本申请实施例能够适用的通信系统的限定。图1所示的网络架构为5G系统架构，可选地，本申请实施例提供的技术方案除了可应用于5G系统外，还可以应用于第四代移动通信技术(the 4th generation，4G)系统中，例如LTE系统，或者还可以应用于下一代移动通信系统或其他类似的通信系统，具体的不做限制。
基于图1所示的网络架构，图2提供一种5G移动网络与无人机系统相结合的示意图。如图2所示，图2中增加了无人机系统服务(UAS service suppliers，USS)121的网络实体，它通常不属于运营商网络，而是在第三方数据网络120中部署，但本申请实施例并不限定于此。无人机系统服务121通过N33接口与3GPP网络的无人机系统功能135进行通信。
无人机系统服务121可以存储UAS的相关信息，比如UAS的认证信息，基于此信息，无人机系统服务121可以对无人机进行身份认证、飞行授权等。UAS的监管部门也可以通过无人机系统服务121对UAS的运营进行监管，确保无人机飞行控制的安全以及公共安全。无人机系统服务121也可以与其他监管或安全飞行部门建立通道，获取飞行相关信息。在一些应用场景中，无人机系统服务121除了可以和无人机/遥控器通过运营商网络通信外，还可以具有遥控无人机飞行的功能，这里不作限定。需要说明的是，无人机系统服务121还可以代表无人机系统流量管理实体(UAS traffic management，UTM)或代表集成了USS和UTM的实体，本申请不作限定。
在图2所示的基于移动通信网络的远程控制UAS中，无人机可以同时兼具两个角色：一个是运营商网络(即PLMN，或称为移动通信网络)中的终端，另一个是UAS中可以飞行的无人机。从运营商网络所提供的业务而言，运营商网络不仅可以为无人机提供普通终端所享有的业务(如多媒体通信、数据业务、互联网等)，而且可以为无人机提供无人机专有的业务，如无人机类型的认证授权(包括无人机专有认证、授权、飞行路线授权等)、C2通信、远程识别无人机、远程定位、禁飞围栏、飞行地图下载等。为了便于描述，下文中将无人机专有的业务称为无人机业务，将不属于无人机专有的业务称为非无人机业务， 具体请参考前述的术语解释部分，此处不再赘述。
正是由于无人机可同时兼顾两个角色，使其具有容易遭受拒绝服务(denial of service，DoS)攻击的潜在安全风险。具体地，在无人机飞行中，攻击者可以利用无人机的非无人机业务，向无人机发送大量无关无人机业务的视频、互联网数据等，恶意消耗无人机的资源(网络资源、计算资源、电池资源等)，挤占无人机执行无人机业务所需资源，从而影响无人机的正常工作(如延迟无人机响应C2通信指令、电池快速耗尽等)，造成无人机偏离航向、无法按照预期到达、甚至坠毁的安全事故。
以图3为例，图3示出了PDU会话和DN的一种关系示意图。如图3所示，DN 1是专门用于无人机业务的DN，只支持无人机业务的会话(PDU会话1)。DN 2是用于无人机业务和非无人机业务的DN，既支持无人机业务的PDU会话(PDU会话2)，又支持非无人机业务的PDU会话(PDU会话3)。DN 3是专有用于非无人机业务的DN，仅支持非无人机业务的PDU会话(PDU会话4)。如图3所示，在无人机的飞行过程中，无人机的大量资源消耗在非无人机业务上，会使得无人机电池资源大量消耗，无法保证无人机有足够电池飞到目的地。并且，该非无人机业务会占用无人机的大量计算资源，造成无人机业务的计算结果有了延迟，无法正常快速地响应遥控器的指令，会出现实际飞行路线错误、无人机延迟抵达、飞行事故等潜在的风险。
鉴于此，本申请实施例提供一种通信方法及装置，在该方法中，第一设备确定满足条件，则限制终端设备的非无人机业务和/或限制终端设备的第一控制面流程，该第一控制面流程不是无人机业务专有的流程，其中的第一条件包括终端设备被授权无人机业务，终端设备发起建立第一个无人机业务对应的会话，或终端设备处于飞行状态中的至少一项。这样，第一设备有条件地限制终端设备非无人机业务能够减少攻击者利用非无人机业务对终端设备的攻击，避免非无人机业务侵占无人机业务的资源。以及，第一设备有条件地限制第一控制面流程，释放了执行该第一控制面流程所需的资源，从而能够为无人机业务预留更多可使用的资源，从而避免终端设备因资源不足导致终端设备无法正常工作，甚至坠毁等问题。
为了更好地介绍本申请实施例，下面结合附图介绍本申请实施例所提供的方法。在本申请的各个实施例对应的附图中，凡是可选的步骤均用虚线表示。本申请的各个实施例所提供的方法均可应用于图1或图2所示的通信系统。
需要说明的是，本申请实施例以终端设备的无人机业务和非无人机业务为例，通过限制非无人机业务和/或第一控制面流程，避免非无人机业务侵占无人机业务的资源，以及为无人机业务预留更多可使用的资源。应理解的是，无人机业务替换为终端设备的第一类业务，非无人机业务替换为终端设备的第二类业务，也同样适用于本申请实施例。即，本申请实施例并不限定于第一类业务是无人机业务，第二类业务是非无人机业务。例如，第一类业务是高可靠、低时延需求的业务，第二类业务是非高可靠、非低时延需求的业务，通过限制第二类业务和/或不是第一类业务专有的流程，以避免第二类业务侵占第一类业务的资源，以及为第一类业务预留更多可使用的资源，从而确保第一类业务的正常执行。又例如，第一类业务是高优先级业务，第二类业务是低优先级业务。
需要说明的是，本申请实施例涉及第一设备、第二设备、第三设备以及第四设备。其中的第一设备可以是会话管理功能设备，短消息业务服务中心(short message service-service center，SMS-SC)，终端设备，安全锚定功能(security anchor function，SEAF)设 备，接入与移动性管理功能设备，统一数据管理设备，认证服务器功能设备，认证凭证存储库和处理(authentication credential repository and processing function，ARPF)设备；或者是包括前述某个设备的功能的其它设备；或者是前述某个设备内的部件(如芯片或功能模块)，本申请实施例对第一设备的具体实现形式并不限定于此。
第二设备可以是统一数据管理设备，统一数据存储设备，策略控制功能设备；或者是包括前述某个设备的功能的其它设备；或者是前述某个设备内的部件(如芯片或功能模块)，本申请实施例对第二设备的具体实现形式并不限定于此。
第三设备可以是安全锚定功能设备，接入与移动性管理功能设备，统一数据管理设备，网络切片认证授权功能设备，认证、授权以及计费服务器(authentication authorization and accounting-server，AAA-S)，数据网络；或者是前述某个设备的功能的其它设备；或者是前述某个设备内的部件(如芯片或功能模块)，本申请实施例对第三设备的具体实现形式并不限定于此。
第四设备可以是终端设备，接入网设备，无人机系统服务，无人机系统功能设备；或者是前述某个设备的功能的其它设备；或者是前述某个设备内的部件(如芯片或功能模块)，本申请实施例对第四设备的具体实现形式并不限定于此。
为了方便说明，在后文的各个实施例中，将会话管理功能设备用SMF代替，将短消息业务服务中心用SMS-SC代替，将终端设备用UE代替，将安全锚定功能设备用SEAF代替，将接入与移动性管理功能设备用AMF代替，将统一数据管理设备用UDM代替，将认证服务器功能设备用AUSF代替，将认证凭证存储库和处理功能设备用ARPF代替，将统一数据存储设备用于UDR代替，将策略控制功能设备用PCF代替，将网络切片认证授权功能设备用NSSAAF代替，将认证、授权以及计费服务器用AAA-S代替，将数据网络用DN代替，将接入网设备用RAN代替，将无人机系统服务用USS代替，将无人机系统功能设备用UAS NF/NEF或UAS NF代替，以及将应用功能设备用AF代替。
需要说明的是，本申请实施例可以支持多个会话管理功能设备同时管理UE的会话。为了便于理解，本申请实施例以第一会话管理功能设备和第二会话管理功能设备可同时管理UE的会话为例。那么为了方便说明，在后文的各个实施例中将第一会话管理功能设备用SMF 1代替，将第二会话管理功能设备用SMF 2代替。另外，本申请实施例涉及的会话可以是PDU会话，也可以是其它会话，本申请实施例对会话的具体实现形式不作限定。
图4为本申请实施例提供的通信方法的一种流程示意图。如图4所示，该方法可以包括如下内容。
S401：第一设备确定满足第一条件。
其中，第一条件包括如下条件中的一种或多种：UE被授权无人机业务，UE发起建立第一个无人机业务对应的会话，或者UE处于飞行状态。
作为一个示例，第一设备可以确定UE被授权无人机业务。UE被授权无人机业务可以理解为UE作为无人机的注册授权、无人机业务对应的会话授权、配对授权或飞行授权中的一种或多种，但本申请实施例并不限定于此。
其中，UE作为无人机的注册授权可理解为UE作为无人机在注册流程中获得了USS的授权。无人机业务对应的会话授权可理解为UE在其作为无人机的会话建立或修改流程中，获得了USS的授权。配对授权可理解为USS对UE与相应的遥控器之间的配对关系 进行授权，从而允许有配对关系的UE和遥控器进行通信，例如UE与遥控器之间传输C2信息。应理解的是，配对授权可以在会话建立或修改流程中进行，也可以在其他流程中进行，本申请不作限制。飞行授权是指USS对UE的飞行路线、飞行计划等飞行相关的信息进行授权，该飞行授权可以在会话建立或修改流程中进行，也可以在其他流程中进行，本申请不作限制。
当UE被授权无人机业务后，USS可以将用于指示UE被授权无人机业务的授权结果通知网络，因此网络中的设备，如第一设备，可以获取到上述授权结果。
以UE被授权无人机业务为UE作为无人机的注册授权为例，在UE作为无人机的注册流程中，AMF向USS发起(经过UAS NF)无人机与USS之间的认证授权流程。USS完成对UE的认证与授权(即完成了无人机的注册授权)，可以将用于指示UE作为无人机被注册授权成功的授权结果发送给网络中的UAS NF和/或AMF。可选地，AMF或UAS NF可以将该授权结果发送给SMF。从而，网络中的第一设备(如SMF、或AMF等)根据该授权结果可以确定该UE已经获得了USS的注册授权，并存储该授权结果。
以UE被授权无人机业务为无人机业务对应的会话授权为例，在UE作为无人机的会话建立或修改流程中，SMF向USS发起(经过UAS NF)无人机与USS之间的无人机业务的会话授权流程。USS完成对UE的会话授权，可以将授权结果发送给UAS NF和/或SMF。可选地，SMF或UAS NF可以将用于指示无人机业务对应的会话被授权的授权结果发送给AMF。从而，第一设备(如SMF、或AMF等)根据该授权结果可以确定该UE已经获得了USS的无人机会话授权，并存储该授权结果。
以UE被授权无人机业务为配对授权为例，在UE作为无人机的会话建立或修改流程中，SMF向USS发起(经过UAS NF)无人机与USS之间的无人机业务的会话授权流程。USS根据SMF发送的消息中的配对信息或者USS存储的配对信息确定是否授权该UE与相应的遥控器进行配对，并将配对授权的结果发送给UAS NF和/或SMF。可选地，SMF或UAS NF可以将配对授权的结果发送给AMF。从而，第一设备(如SMF、或AMF等)根据该配对授权的结果可以确定该UE已经获得了USS对UE和其相对应的遥控器的配对授权，并存储该配对授权的结果。
以UE被授权无人机业务为飞行授权为例，在UE作为无人机的会话建立或修改流程中，SMF向USS发起(经过UAS NF)无人机与USS之间的无人机业务的会话授权流程。USS根据UE的飞行路线信息(和/或飞行计划等信息)确定是否授权该UE的飞行路线(和/或飞行计划)，并将飞行授权的结果发送给UAS NF和/或SMF。该飞行路线和/或飞行计划等信息可以是来自UE的信息，或者也可以是USS存储的信息，本申请实施例不作限定。可选地，SMF或UAS NF可以将飞行授权的结果发送给AMF。从而，第一设备(如SMF、或AMF等)根据该飞行授权的结果可以确定该UE已经获得了USS对无人机的飞行授权，并存储该飞行授权的结果。
需要说明的是，上述涉及的授权流程可以是由网络侧(如AMF、或SMF等)发起的流程；或者也可以由USS发起的流程，本申请对此不作限定。以及，上述涉及的配对授权、飞行授权是以在会话建立或修改的流程中进行为例，但本申请实施例并不限定于此。例如，该配对授权、飞行授权也可以在注册流程中进行。另外，以上描述作为一种示例说明了第一设备确定UE被授权无人机业务的具体实现过程，但应理解的是，本申请实施例对UE被授权无人机业务以及第一设备确定UE被授权无人机业务的具体方法和具体流程并不限 定于此。
作为又一个示例，第一设备可以确定UE发起建立第一个无人机业务对应的会话。例如，第一设备是SMF 1，SMF 1可以根据存储的UE的信息(如UE的上下文信息等)确定UE是否发起建立第一个无人机业务对应的会话。其中，UE的上下文信息可以包括UE已建立的不同业务对应的会话。例如，SMF 1接收来自UE的用于请求建立会话的消息(如记为第二消息，该第二消息用于请求建立第一会话)；SMF 1可以根据UE的上下文信息确定第一会话是否是该UE的第一个无人机业务对应的会话。例如，SMF 1可以确定第一会话是否属于无人机业务对应的会话，并在确定该第一会话属于无人机业务对应的会话的情况下，再根据UE的上下文信息确定该第一会话是否是该UE的第一个无人机业务对应的会话。例如，第一会话属于非无人机业务对应的会话，或者第一会话属于无人机业务对应的会话但UE的上下文信息包括无人机业务对应的其他会话，SMF 1可以确定该第二消息不是用于建立第一个无人机业务对应的会话的消息。又例如，第一会话属于无人机业务对应的会话，且UE的上下文信息不包括无人机业务对应的会话，SMF 1可以确定该第二消息用于请求建立UE的第一个无人机业务对应的会话，即确定UE发起建立第一个无人机业务对应的会话。
可选地，SMF 1可以确定第一会话是否属于无人机业务对应的会话。例如，SMF 1可以根据第二消息确定第一会话是否属于无人机业务对应的会话。该第二消息可以包括如下信息中一种或多种：UE的类型指示信息、UAV标识(identity，ID)、数据网络名称(DN name，DNN)、USS地址信息、USS ID、单一网络切片选择辅助信息(single network slice selection assistance information，S-NSSAI)标识、AF ID、或会话的业务类型等。应理解的是，这些信息可以包含在第二消息中发送给SMF 1，也可以包含在其它消息中发送给SMF 1，本申请实施例不作限定。下面对这些信息进行介绍。
(1)UE的类型指示信息，可指示该UE是无人机或者是普通UE。例如，第二消息包括UE的类型指示信息，该UE的类型指示信息指示该UE是无人机，SMF 1根据该第二消息可以确定第一会话属于无人机业务对应的会话。又例如，第二消息包括UE的类型指示信息，该UE的类型指示信息指示该UE是普通UE，SMF 1根据该第二消息可以确定第一会话属于非无人机业务对应的会话。
(2)UAV ID，可以为UE注册无人机的ID，或者为USS为UE分配的作为无人机的ID。若第二消息包括UAV ID，SMF 1根据该第二消息可以确定第一会话属于无人机业务对应的会话。
(3)DNN，可用于指示第一会话对应的DN，该DN可以是无人机业务相关的DN，也可以是非无人机业务相关的DN，本申请实施例对此不作限定。例如，第二消息包括DNN，且该DNN所指示的DN是无人机业务相关的DN，SMF 1根据该第二消息可以确定第一会话属于无人机业务对应的会话。又例如，第二消息包括DNN，且该DNN所指示的DN是非无人机业务相关的DN，SMF 1根据该第二消息可以确定第一会话属于非无人机业务对应的会话。
(4)USS地址信息或USS ID，可用于指示为第一会话提供服务的USS。若第二消息包括USS地址信息和/或USS ID，SMF 1根据该第二消息可以确定第一会话属于无人机业务对应的会话。
(5)S-NSSAI标识，可用于指示第一会话对应的切片业务类型，该切片业务类型可 以是无人机业务对应的切片业务，或者是非无人机业务对应的切片业务，本申请实施例对此不作限定。例如，第二消息包括S-NSSAI，且该S-NSSAI指示无人机业务对应的切片业务，SMF 1根据该第二消息可以确定第一会话属于无人机业务对应的会话。又例如，第二消息包括S-NSSAI，且该S-NSSAI指示非无人机业务对应的切片业务，SMF 1根据该第二消息可以确定第一会话属于非无人机业务对应的会话。
(6)AF ID，可用于指示发起建立第一会话对应的AF，该AF可以是无人机业务相关的AF，或者是非无人机业务相关的AF，本申请实施例对此不作限定。例如，第二消息包括AF ID，且该AF ID所指示的AF是无人机业务相关的AF，SMF 1根据该第二消息可以确定第一会话属于无人机业务对应的会话。又例如，第二消息包括AF ID，且该AF ID所指示的AF是非无人机业务相关的AF，SMF 1根据该第二消息可以确定第一会话属于非无人机业务对应的会话。
(7)会话的业务类型，可用于指示第一会话对应的业务类型，该业务类型例如可以是无人机业务、非无人机业务等，本申请实施例不作限制。例如，第二消息包括会话的业务类型，且该会话的业务类型用于指示无人机业务，SMF 1根据该第二消息可以确定第一会话属于无人机业务对应的会话。又例如，第二消息包括会话的业务类型，且该会话的业务类型用于指示非无人机业务，SMF 1根据该第二消息可以确定第一会话属于非无人机业务对应的会话。
需要说明的是，SMF 1也可以根据上述信息的组合，确定第一会话是否属于无人机业务对应的会话。例如，第二消息包括DNN和S-NSSAI，且该DNN和S-NSSAI的组合指示无人机业务，SMF 1根据该第二消息可以确定第一会话属于无人机业务对应的会话。又例如，第二消息包括DNN和S-NSSAI，且该DNN和S-NSSAI的组合指示非无人机业务，SMF 1根据该第二消息可以确定第一会话属于非无人机业务对应的会话。另外，SMF 1还可以根据上述信息中的其他两种或者两种以上的信息的组合，确定第一会话是否属于无人机业务对应的会话，本申请实施例在此不再一一列举。
在上述示例中，第一设备是SMF 1，SMF 1可以根据SMF 1存储的UE的信息(如UE的上下文信息等)确定UE是否发起建立第一个无人机业务对应的会话。当然，第一设备也可以是SMF 2，或者其它SMF，其实现方式请参考第一设备是SMF 1的相关内容，此处不再赘述。在另一种可能实现的方式中，第一设备不是SMF，第一设备可以从SMF处确定UE是否发起建立第一个无人机业务对应的会话。例如，第一设备可以向SMF订阅UE的会话信息，或者向SMF发送用于请求获取UE的会话信息的消息；在SMF确定UE发起建立第一个无人机业务对应的会话后，SMF可以向第一设备发送用于指示UE发起建立第一个无人机业务对应的会话的指示信息；第一设备接收该指示信息，并根据该指示信息确定UE发起建立第一个无人机业务对应的会话。
前面介绍了第一设备确定UE被授权无人机业务，以及确定UE发起建立第一个无人机业务对应的会话。接下来介绍第一设备确定UE处于飞行状态。
作为一个示例，第一设备是UE，第一设备可以根据移动信息，或根据来自应用层的第五指示信息，或根据移动信息和来自应用层的第五指示信息，确定UE处于飞行状态。其中，移动信息可以包括高度和/或运动速度。例如，UE可以测量自身的水平高度，若测量得到的水平高度大于或等于高度阈值，UE可以确定自身处于飞行状态。该高度阈值可以是预先设定的，本申请实施例对此不作限定。又例如，UE可以测量自身的运动速度， 若测量得到的运动速度大于或等于速度阈值，UE可以确定自身处于飞行状态。该速度阈值可以是预先设定的，本申请实施例对此不作限定。第五指示信息可指示UE进入飞行模式。
作为另一个示例，第一设备是AMF，第一设备可以维护UE的状态。其中，UE的状态包括飞行状态和/或非飞行状态。例如，第一设备可以周期性地或非周期性地获取UE的状态。例如，第一设备可以接收来自第四设备的第四指示信息，该第四指示信息用于指示UE处于飞行状态。进一步，第一设备可以根据该第四指示信息确定UE处于飞行状态。其中，第四设备可以主动向第一设备发送第四指示信息，也可以在接收到第一设备的用于请求UE的状态的消息后向第一设备发送该第四指示信息，本申请实施例对此不作限定。又例如，第一设备可以根据UE的移动信息，或根据UE的飞行信息，或根据UE的移动信息和UE的飞行信息，确定UE处于飞行状态。例如，第一设备可以从基站、网关移动定位中心(gateway mobile location center，GMLC)或定位管理功能(location management function，LMF)设备等设备处获取UE的移动信息。例如，若UE的移动信息中的运动速度(或高度)大于或等于设备阈值，第一设备确定UE处于飞行状态；反之，第一设备确定UE处于非飞行状态。例如，第一设备可以从USS处获取UE的飞行信息。该飞行信息可以包括飞行路径、飞行时间表等。例如，第一设备可以确定当前时间以及UE当前的位置是否与飞行路径和飞行时间表相匹配。若当前时间以及UE当前的位置与飞行路径和飞行时间表相匹配，第一设备确定UE处于飞行状态；否则，第一设备确定UE处于非飞行状态。
作为再一个示例，第一设备可以从AMF处获取UE的状态。例如，第一设备可以接收来自AMF的第三指示信息，该第三指示信息指示UE处于飞行状态。进一步，第一设备根据该第三指示信息可以确定UE处于飞行状态。例如，AMF可以主动向第一设备推送UE的状态，或者AMF也可以在接收到第一设备发送的用于订阅(或请求)UE的状态的消息(如记为第六消息)向第一设备发送UE的状态，本申请实施例对此不作限定。
S402：第一设备限制UE的非无人机业务和/或限制UE的第一控制面流程。
在S402中，第一设备限制UE的非无人机业务，或者限制UE的第一控制面流程，或者限制UE的非无人机业务以及限制UE的第一控制面流程。示例性的，第一设备可以通过如下方式中的一种或多种限制UE的非无人机业务。
方式一：第一设备是SMF 1，第一设备释放SMF 1管理的该UE的非无人机业务对应的会话，或者禁止(或拒绝)建立或修改该UE的非无人机业务对应的会话，或者释放SMF1管理的该UE的非无人机业务对应的会话以及禁止建立或禁止修改该UE的非无人机业务对应的会话。
例如，第一设备可以释放SMF 1管理的该UE的全部非无人机业务对应的会话，或者第一设备可以释放SMF 1管理的该UE的部分非无人机业务对应的会话。其中，SMF 1可以主动触发非无人机业务对应的会话的释放流程。例如，SMF 1释放分配给非无人机业务对应的会话的IP地址，或向UPF发送用于释放非无人机业务对应的会话的会话释放消息以便UPF释放与该非无人机业务对应的会话相关的资源(如丢掉该非无人机业务对应的会话对应的剩余数据包并释放相应的隧道(tunnel)资源和存储的上下文等)。进一步，SMF 1通知相应的AMF，以便AMF释放与该非无人机业务对应的会话相关的资源(如会话ID、SMF ID等)、以及通知AN释放与该非无人机业务对应的会话相关的AN资源等。应理解 的是，本申请实施例对SMF释放非无人机业务对应的会话的具体实现方案并不限定于此。
例如，第一设备确定N大于M，并确定释放SMF 1管理的该UE的全部或部分非无人机业务对应的会话。其中，N可以是SMF 1所管理的该UE的非无人机业务对应的会话的数量。例如，第一设备可以根据第一设备存储的UE的上下文信息确定该N，或者从UDM或UDR或AMF处获取该N，本申请实施例对N的获取方式并不限定于此。M可以是UE在执行无人机业务时允许在SMF 1处建立的非无人机业务对应的会话的数量。该M可以是预先设置的，或者是PCF配置，或者是从UDM或UDR或AMF处获取的，本申请实施例对M的实现方式不作限定。可选地，第一设备可以确定释放H个非无人机业务对应的会话，该H可以是大于或等于(N-M)的正整数。
又例如，第一设备可以禁止建立该UE的部分或全部非无人机业对应的会话(包括禁止将该UE的部分无人机业务对应的会话修改成非无人机业务对应的会话)或禁止修改该UE的部分或全部非无人机业务对应的会话。
其中，第一设备禁止建立或禁止修改该UE的非无人机业务对应的会话，可以理解为第一设备拒绝来自UE的用于请求建立或修改非无人机业务对应的会话的消息；或者理解为第一设备拒绝来自UE的用于请求将无人机业务对应的会话修改为非无人机业务对应的会话的消息；或者理解为第一设备不响应或拒绝来自AF的用于请求建立或修改非无人机业务对应的会话的消息；或者理解为第一设备不响应或拒绝来自AF的用于请求将无人机业务对应的会话修改为非无人机对应的会话的消息；或者理解为第一设备删除或丢弃来自UE或AF的用于请求建立或修改非无人机业务对应的会话的消息；或者理解为第一设备删除或丢弃来自UE或AF的用于请求将无人机业务对应的会话修改为非无人机业务对应的会话的消息等，本申请实施例并不限定于此。例如，第一设备接收来自UE或AF的用于请求建立或修改会话的消息，确定该消息用于请求建立或修改的会话是否属于无人机业务对应的会话。若该消息用于请求建立或修改的会话属于无人机业务对应的会话(需要说明的是，根据上述理解，本申请中修改无人机业务对应的会话还包括将非无人机业务对应的会话修改为无人机业务对应的会话，后面不再重复赘述)，第一设备根据该消息继续执行建立或修改会话的流程。若该消息用于请求建立或修改的会话属于非无人机业务对应的会话(需要说明的是，根据上述理解，本申请中修改非无人机业务对应的会话还包括将无人机业务对应的会话修改为非无人机业务对应的会话，后面不再重复赘述)，第一设备拒绝该请求或不响应该消息。其中，第一设备确定会话是否属于无人机业务对应的会话可参考S401的相关内容，此处不再赘述。
方式二：第一设备是AMF、或其他设备(如UDM，PCF等)。第一设备触发或者通知SMF释放SMF管理的该UE的全部或部分非无人机业务对应的会话，或者禁止(或拒绝)建立或修改该UE的全部或部分非无人机业务对应的会话。
例如，第一设备确定限制UE的非无人机业务，确定管理该UE的会话的SMF(如SMF 1和/或SMF 2)，并向该SMF发送用于释放该SMF管理的该UE的全部或者部分非无人机业务对应的会话的通知消息。可选地，第一设备确定管理该UE的非无人机业务对应的会话的SMF，并向该SMF发送该通知消息。其中，释放UE的非无人机业务对应的会话的具体实现方式请参考前述方式一的相关描述，此处步骤赘述。
方式三：第一设备是SMS-SC，第一设备不向或暂停向UE发送用于请求建立或修改非无人机业务对应的会话(如记为第一消息)。
该第一消息例如可以是短消息，但本申请实施例对第一消息的具体实现形式不作限定。该第一消息可以来自于AF。例如，AF可根据应用需求(如主动向UE推送视频、数据等)或UE的应用需求等确定需要建立或修改UE的非无人机业务对应的会话，并生成第一消息，以及向SMS-SC发送该第一消息(以便SMS-SC收到第一消息后，通知UE，由UE发出建立或修改UE的非无人机业务对应的会话的请求消息)；SMS-SC接收到第一消息后，确定满足第一条件，以及不向或暂停向UE发送该第一消息。
方式四：第一设备是UE，第一设备不向或暂停向SMF 1发送第一消息。该第一消息用于请求建立或修改非无人机业务对应的会话。
例如，AF可根据应用需求(如主动向UE推送视频数据、图像数据等)或UE的应用需求等确定需要建立或修改UE的非无人机业务对应的会话，并生成用于触发UE请求建立或修改UE的非无人机业务对应的会话的请求消息，以及向SMS-SC发送该请求消息；SMS-SC接收到该请求消息后，将该请求消息转发给UE；UE接收到该请求消息后，确定满足第一条件，以及不向或暂停向SMF 1发送第一消息。在本方式中，该第一消息用于请求建立或修改非无人机业务对应的会话。
方式五：第一设备可以向UE发送第二指示信息。该第二指示信息可指示禁止建立非无人机业务对应的会话。这样，UE根据该第二指示信息，可以不发起非无人机业务对应的会话的建立或修改。
前面介绍了第一设备限制UE的非无人机业务，接下来介绍第一设备限制UE的第一控制面流程。
第一控制面流程不是无人机业务专有的流程。第一控制面流程不是无人机业务专有的流程，可以理解为第一控制面流程的不执行不会对UE的无人机业务造成负面影响；或者理解为第一控制面流程的不执行不会影响UE的无人机业务的正常执行；或者理解为第一控制面流程不是UE的无人机业务正常执行的必要流程；或者理解为执行第一控制面流程不仅对UE的无人机业务造成影响，而且对UE的非无人机业务造成影响；或者理解为执行第一控制面流程不仅是UE的无人机业务正常执行的必要流程也是UE的非无人机业务正常执行的必要流程等，本申请实施例不作限定。
示例性的，该第一控制面流程可以包括如下流程中的一项或多项：首次(primary)认证流程，去注册流程，切片认证流程，或二次认证流程等，本申请实施例并不限定于此。
示例性的，第一设备可以通过暂停或终止第一控制面流程实现对该第一控制面流程的限制。例如，第一设备接收来自第三设备的第四消息，该第四消息用于请求执行第一控制面流程；第一设备确定满足第一条件，以及可以暂停或终止该第一控制面流程。可选地，第一设备可以向第三设备发送第五消息，该第五消息包括不进行(或不执行)第一控制面流程的原因。该不执行第一控制面流程的原因例如可以是满足第一条件，或者是超时等，本申请实施例不作限定。可选地，第一设备在暂停第一控制面流程之后，可以启动第一计时器，并确定在第一计时器的运行期间(或运行结束时)UE是否满足第一条件。若第一设备确定在第一计时器的运行期间(或运行结束时)UE满足第一条件，第一设备可以在第一计时器运行结束时终止该第一控制面流程。若第一设备确定在第一计时器的运行期间UE不满足第一条件，第一设备可以执行该第一控制面流程。
在一种可能的实现方式中，在S401中，第一设备确定的第一条件包括UE被授权无人机业务和/或UE处于飞行状态，进一步，该第一设备还可以接收来自UE的第二消息，并 确定该第二消息所请求建立的第一会话是否属于无人机业务对应的会话。其中，第一设备确定第一会话属于无人机业务对应的会话，则第一设备可以执行S402所示的内容；或者，第一设备确定第一会话属于非无人机业务对应的会话，则第一设备可以不执行S402所示的内容。其中第一设备确定第一会话是否属于无人机业务对应的会话，请参考S401的相关内容，此处不再赘述。通过该实现方式，在UE被授权无人机业务和/或UE处于飞行状态的情况下，第二消息所请求建立的第一会话属于无人机业务对应的会话，意味着UE即将执行无人机业务，第一设备限制该UE的非无人机业务和/或限制该UE的第一控制面流程，可以避免非无人机业务侵占无人机业务的资源，为该无人机业务预留更多可使用的资源；或者，第二消息所请求建立的第一会话属于非无人机业务对应的会话，则意味着UE尚未执行无人机业务，在此情况下，第一设备允许执行非无人机业务和允许执行第一控制面流程，能够提高资源利用率以及提高兼容性。
在又一种可能的实现方式中，在S401中，第一设备确定的第一条件包括UE被授权无人机业务和/或UE处于飞行状态，进一步，该第一设备还可以接收来自UE的第二消息，并确定该第二消息所请求建立的第一会话是否属于无人机业务对应的会话。其中，第一设备确定第一会话属于无人机业务对应的会话，第一设备可以不执行S402所示的内容。又例如，第一设备确定第一会话属于非无人机业务对应的会话，第一设备可以拒绝建立第一会话的请求。其中第一设备确定第一会话是否属于无人机业务对应的会话，请参考S401的相关内容，此处不再赘述。通过该实现方式，在UE被授权无人机业务和/或UE处于飞行状态的情况下，第二消息所请求建立的第一会话属于无人机业务对应的会话，第一设备虽然不执行S402，但在该第一会话属于非无人机业务对应的会话时，第一设备会拒绝建立非无人机业务对应的会话，这样能够在执行无人机业务的情况下执行已有(或正在执行)的非无人机业务以及执行第一控制面流程，可以提高资源利用率，而拒绝新建非无人机业务对应的会话，能够避免攻击者利用新建的非无人机业务攻击UE。
在另一种可能的实现方式中，在S401中，第一设备确定的第一条件包括UE被授权无人机业务和/或UE处于飞行状态，进一步，该第一设备还可以接收来自UE的第二消息，并确定该第二消息所请求建立的第一会话是否是UE发起的第一个无人机业务对应的会话。例如，第一设备可以根据自身存储的UE的上下文信息确定第一会话是否为UE发起的第一个无人机业务对应的会话。例如，如果第一设备已经存储了无人机业务对应的会话信息，则可以确定第一会话不是UE发起的第一个无人机业务对应的会话，否则可以确定第一会话是UE发起的第一个无人机业务对应的会话。可选地，第一设备可以向SMF、UDR或UDM发送请求，获取UE是否已经建立了无人机业务对应的会话的信息。如果有，则可以确定第一会话不是UE发起的第一个无人机业务对应的会话，否则可以确定第一会话是UE发起的第一个无人机业务对应的会话。其中，第一会话不是UE发起的第一个无人机业务对应的会话，意味着第一设备在收到第一会话建立请求之前(即在无人机业务对应的第一个会话建立时)，UE的非无人机业务对应的会话已经被释放，在此情况下，第一设备不必重复请求限制非无人机业务和/或限制第一控制面流程，从而免去不必要的消息交互，提高资源的利用率。即，第一设备确定第一会话不是UE发起的第一个无人机业务对应的会话，则第一设备可以不执行S402所示的内容；或者，第一设备确定第一会话是UE发起的第一个无人机业务对应的会话，则第一设备可以执行S402所示的内容。
在一种可能的实现方式中，第一设备可以向第二设备发送用于请求(或通知)限制UE 的非无人机业务的消息(如记为第三消息)，即执行S403所示的内容。
S403：第一设备向第二设备发送第三消息。相应地，第二设备接收第三消息。
S403为可选步骤。第三消息可用于请求(或通知)限制UE的非无人机业务。
S404：第二设备确定SMF 2管理有UE的非无人机业务对应的会话。
S404为可选步骤。示例性的，第二设备接收到第三消息后，可以确定管理有UE的会话的SMF。可选地，第二设备确定管理有UE的非无人机业务对应的会话的SMF。例如，第二设备可以根据存储的UE的上下文信息，和/或根据从UDM或UDR或PCF处获取的UE的上下文信息，确定管理有UE的会话的SMF或者管理有UE的非无人机业务对应的会话的SMF。例如，PCF可以向UDM(或UDR)发送用于请求UE的会话信息或与SMF的关联信息的消息；以及接收来自UDM(或UDR)的UE的会话信息(包括SMF的关联信息)或与SMF的关联信息。其中，UE的上下文信息可包括UE与SMF的关联信息。UE与SMF的关联信息可以包括管理有UE的非无人机业务对应的会话的SMF的标识或管理有UE会话的SMF标识。可选地，该UE与SMF的关联信息还可以包括管理有UE的无人机业务对应的会话的SMF的标识。在本申请实施例中，以SMF 1和SMF 2同时管理有UE的非无人机业务的会话为例。那么在S404中，第二设备可以确定SMF 2管理有UE的非无人机业务对应的会话。
S405：第二设备向SMF 2发送第六指示信息。相应地，SMF 2接收第六指示信息。
S405为可选步骤。该第六指示信息用于指示释放SMF 2管理的该UE的非无人机业务对应的会话，或指示禁止建立或禁止修改该UE的非无人机业务对应的会话，或指示释放SMF 2管理的该UE的非无人机业务对应的会话以及禁止建立或禁止修改该UE的非无人机业务对应的会话。可选地，该第六指示信息可用于指示释放SMF 2管理的该UE的全部或部分非无人机业务对应的会话。
在S402中，第一设备确定释放SMF 1管理的该UE的全部或部分非无人机业务对应的会话。在另一种可能的实现方式中，第一设备接收来自第二设备的第一指示信息，并根据该第一指示信息释放SMF 1管理的该UE的一个或多个非无人机业务对应的会话。该第一指示信息可指示释放一个或多个非无人机业务对应的会话。例如，第二设备接收到第三消息后，确定管理有UE的非无人机业务对应的会话的SMF，并确定SMF释放的该UE非无人机业务对应的会话的数量。以SMF 1为例，第二设备接收来自SMF 1的N，并根据UE已建立的非无人机业务对应的会话的数量，N以及M，确定SMF 1需要释放一个或多个非无人机业务对应的会话，或者确定SMF 1需要释放(或待释放)的该UE的非无人机业务对应的会话的数量。
在一种可能的实现方式中，第一设备可以撤销对非无人机业务的限制和/或撤销对第一控制面流程的限制。例如，第一设备确定满足第二条件，第一设备可以撤销对非无人机业务的限制和/或撤消对第一控制面流程的限制。例如，第一设备是SMF 1，第一设备确定满足第二条件，接收来自UE的第七消息，并根据该第七消息建立或修改非无人机业务对应的会话，该第七消息用于请求建立或修改非无人机业务对应的会话。又例如，第一设备是SMS-SC，第一设备确定满足第二条件，接收来自AF的第八消息，以及向UE发送该第八消息，该第八消息用于请求建立或修改非无人机业务对应的会话。再例如，第一设备是UE，第一设备确定满足第二条件，接收来自SMS-SC的第八消息，以及向SMF 1发送该第八消息，该第八消息用于请求建立或修改非无人机业务对应的会话。再例如，第一设备确定满 足第二条件，接收来自第三设备的用于请求执行第一控制面流程的消息(如记为第四消息)，以及执行该第一控制面流程。
其中，第二条件包括如下条件中的一种或多种：UE被撤消无人机业务的授权，UE不被授权无人机业务，UE的无人机业务被去注册，或UE释放最后一个无人机业务对应的会话等。例如，当USS准备撤销对UE的无人机业务的授权时，可以将撤销请求(通过UAS NF)发送给AMF(或SMF)，并由AMF(或SMF)继续执行针对UE的无人机业务的授权撤销流程，撤销的结果会经过AMF(或SMF)发送给UE。AMF与SMF可以互相订阅该授权信息，即可以从对方收到授权撤销的结果。因此，第一设备(如UE、SMF、或AMF)可以确定UE被撤消无人机业务的授权，但本申请实施例并不限定于此。例如，当UE需要被去注册时，AMF会收到去注册请求，并执行与UE的去注册流程，因此AMF与UE可以获取到去注册流程完成的信息。另外，SMF可以通过AMF获取UE的去注册信息(SMF订阅了相关信息的通知服务)，但本申请实施例并不限定于此。例如，第一设备是SMF，第一设备可以根据存储的UE的上下文信息确定UE是否释放最后一个无人机业务对应的会话。再例如，第一设备不是SMF，第一设备可以从SMF处获取UE是否释放最后一个无人机业务对应的会话。
在S401中，AMF可以维护UE的状态。下面结合图5介绍AMF获取UE的状态的实现方式。
图5为本申请实施例提供的通信方法的一种流程示意图。在本实施例中，第一设备是AMF，第四设备是RAN、或UE、或USS、或UAS NF/NEF。AMF可以根据图5所示的四种方式中的一种或多种获取UE的状态。其中的方式1包括步骤S501至S503，方式2包括S504和S505，方式3包括步骤S506至S508，以及方式4包括步骤S509至S511。如图5所示，该方法还可以包括如下流程。
S501：AMF向RAN发送第九消息；相应地，RAN接收来自AMF的第九消息。
S501为可选步骤。例如，AMF可以向RAN发送第九消息，以获取UE的状态；或者，RAN也可以主动向AMF上报UE的状态；本申请实施例对此不作限定。
S502：RAN根据UE的移动信息确定UE的状态。
该移动信息包括高度、运动速度、位置或运动轨迹中的一项或多项。例如，RAN可以对UE进行测量，得到该UE的移动信息。又例如，RAN可以接收来自UE的移动信息。应理解的是，本申请实施例对RAN获取移动信息的具体实现方式不作限定。进一步，RAN可以根据UE的移动信息确定UE处于飞行状态或处于非飞行状态。例如，高度大于或等于高度阈值，RAN可以确定UE处于飞行状态。该高度阈值可以是预先设定的，本申请实施例对此不作限定。又例如，运动速度大于或等于速度阈值，RAN可以确定自身处于飞行状态。该速度阈值可以是预先设定的，本申请实施例对此不作限定。
S503：RAN向AMF发送第四指示信息；相应地，AMF接收来自RAN的第四指示信息。
该第四指示信息可用于指示UE处于飞行状态，或指示UE处于非飞行状态。RAN可以向AMF发送第四指示信息，以指示UE的状态。为了便于理解，图5以第四指示信息指示UE处于飞行状态为例。
至此，AMF通过方式1完成对UE的状态的获取。接下来介绍AMF通过方式2获取UE的状态。
S504：UE根据移动信息和/或第五指示信息确定UE的状态。
例如，UE可以对自身的高度、运动速度、位置或运动轨迹中的一项或多项进行测量，也可以通过对收到的RAN的无线信号进行测量，从而计算出UE的移动信息。关于移动信息的描述以及UE根据移动信息确定UE的状态可参考S502的描述，此处不再赘述。第五指示信息可以是来自于UE的应用层的，例如应用层触发UE进入飞行模式，该应用层可以生成第五指示信息，该第五指示信息用于指示UE进入飞行模式，进一步，UE根据该第五指示信息确定UE处于飞行状态。
S505：UE向AMF发送第四指示信息；相应地，AMF接收来自UE的第四指示信息。
S505的具体实现过程请参考S503，此处不再赘述。
至此，AMF通过方式2完成对UE的状态的获取。接下来介绍AMF通过方式3获取UE的状态。
S506：AMF获取UE的移动信息。
例如，AMF可以从RAN和/或GMLC(或LMF)处获取UE的移动信息。例如，RAN可以主动向AMF上报UE的移动信息；或者，RAN可以在接收到来自AMF的用于请求获取UE的移动信息的消息后，向AMF发送该UE的移动信息。又例如，GMLC(或LMF)可以主动向AMF推送UE的移动信息；或者，GMLC(或LMF)可以在接收到来自AMF的用于请求获取UE的移动信息的消息后，向AMF发送该UE的移动信息。应理解的是，本申请实施例对AMF获取UE的移动信息的具体实现方式不作限定。
S507：AMF获取UE的飞行信息。
该飞行信息例如可以包括飞行路线和/或飞行时间。例如，AMF可以从UAS NF/NEF(或USS)处获取UE的飞行信息。例如，UAS NF/NEF(或USS)可以主动向AMF推送UE的飞行信息；或者，UAS NF/NEF(或USS)可以接收到来自AMF的用于请求UE的飞行信息的消息后，向AMF发送该UE的飞行信息；本申请实施例对AMF获取UE的飞行信息的具体实现方式不作限定。
S508：AMF根据移动信息和飞行信息确定UE的状态。
例如，AMF可以确定当前时间以及UE当前的位置是否与飞行路径和飞行时间表相匹配。若当前时间以及UE当前的位置与飞行路径和飞行时间表相匹配，AMF确定UE处于飞行状态；否则，AMF确定UE处于非飞行状态。又例如，AMF可以根据移动信息确定UE的状态。例如，若高度大于或等于高度阈值，AMF可以确定UE处于飞行状态；或者，若运动速度大于或等于速度阈值，AMF可以确定自身处于飞行状态。再例如，AMF可以向其它设备(例如网络数据分析功能(network data analytics function，NWDAF)设备)发送用于获取UE的状态请求消息；NWDAF可以根据收集到的UE相关信息(如移动信息和/或飞行信息等)，确定UE的状态，以及向AMF发送UE的状态。可选地，AMF可以向NWDAF发送AMF获取的移动信息和/或飞行信息；NWDAF根据接收到的移动信息和/或飞行信息，确定UE的状态，以及向AMF发送UE的状态。图5以AMF根据移动信息和飞行信息确定UE的状态为例。
至此，AMF通过方式3完成对UE的状态的获取。接下来介绍AMF通过方式4获取UE的状态。
S509：AMF向UAS NF/NEF发送第九消息；相应地，UAS NF/NEF接收来自AMF的第九消息。
S509为可选步骤。例如，AMF可以向UAS NF/NEF(或USS)发送第九消息，以获取UE的状态；或者，UAS NF/NEF(或USS)也可以主动向AMF推送UE的状态；本申请实施例对此不作限定。
需要说明的是，由UAS NF/NEF执行的部分同样也可以由USS执行。
S510：UAS NF/NEF确定UE的状态。
例如，UAS NF/NEF可以根据本地存储的UE的状态，或者UAS NF/NEF也可以从USS处获取UE的状态，如向USS发送用于获取UE的状态的请求消息。其中，USS可以根据自身与UE之间的通信内容获取UE的状态，或者，USS也可以根据UE的飞行授权信息和/或飞行时间表等确定UE的状态。例如，USS与作为无人机的UE之间有专门的通信通道(如C2通信)，USS可以根据该通信通道的通信内容获取UE的状态。又例如，USS可以根据存储的UE的飞行授权信息和/或飞行时间表等信息，确定UE的状态。
S511：UAS NF/NEF向AMF发送第四指示信息；相应地，AMF接收来自UAS NF/NEF的第四指示信息。
S511的具体实现过程请参考S503，此处不再赘述。
至此，AMF通过方式4完成对UE的状态的获取。
在图5所示的流程中，AMF可以根据移动信息和飞行信息确定UE的状态，也可以从RAN或UE或UAS NF/NEF或USS处获取UE的状态，实现方式灵活，适应性强。进一步，该AMF可以维护(或保存)UE的状态，以及向其它设备(如SMF、SMS-SC、UDM、AUSF、ARPF或NSSAAF等)发送该UE的状态，以便该其它设备确定UE是否处于飞行状态。
图5介绍了AMF通过多种方式获取UE的状态。接下来结合图6至图13介绍图4所示的流程。
图6为本申请实施例提供的通信方法的又一种流程示意图。在本实施例中，第一设备是SMF 1，以及SMF 1释放该SMF 1管理的UE的全部非无人机业务对应的会话。第二设备是PCF，或是UDM，或是UDR，或是AMF。如图6所示，该方法可以包括如下流程。
S601：UE向SMF 1发送第二消息；相应地，SMF 1接收来自UE的第二消息。
S601为可选步骤，即SMF 1可以响应于第二消息确定是否满足第一条件，或者SMF 1也可以周期性地或非周期性地确定是否满足第一条件，本申请实施例对此不作限定。该第二消息用于请求建立第一会话，该第二消息例如可以是PDU会话建立请求(PDU session establishment request)消息。或者，该第二消息可以用于请求修改第一会话，该第二消息例如可以是PDU会话修改请求(PDU session modification request)消息。本申请实施例对第二消息的名称不作限定。
S602：SMF 1确定满足第一条件。
第一条件包括如下条件中的一种或多种：UE被授权无人机业务，UE发起建立第一个无人机业务对应的会话，或者UE处于飞行状态。在S602中，SMF 1可以确定是否满足第一条件。例如，SMF 1可以根据存储的UE的上下文信息确定UE是否被授权无人机业务。例如，SMF 1可以从AMF处获取UE是否被授权无人机业务(订阅AMF关于UE的无人机授权状态的服务，当无人机被授权时，由AMF通知SMF 1；或者SMF 1向AMF发送请求消息，获取UE的无人机业务授权状态)。又例如，SMF 1可以根据UE的上下文信息 确定该第一会话是否是UE发起建立第一个无人机业务对应的会话。再例如，SMF 1可以从AMF处获取UE的状态，并根据UE的状态确定UE是否处于飞行状态。S602的具体实现过程请参考S401的相关内容，此处不再赘述。图6中以SMF 1满足第一条件为例。
S603：SMF 1确定第一会话属于无人机业务对应的会话，且确定第一会话是UE的第一个无人机业务对应的会话。
S603为可选步骤。例如，在S602中SMF 1确定的第一条件包括UE被授权无人机业务和/或UE处于飞行状态，SMF 1在执行S602之后可以执行S603，也可以不执行S603。又例如，在S602中SMF 1确定的第一条件包括UE发起建立第一个无人机业务对应的会话，那么S603与S602可理解为一个步骤，SMF 1无需执行S603。
作为一个示例，第二消息用于请求创建第一会话，SMF 1确定该第一会话属于无人机业务对应的会话，并确定该第一会话是否为第一个无人机业务对应的会话。如果该第一会话是第一个无人机业务对应的会话，SMF 1可以执行S604-S609所示的内容；否则不执行S604-S609所示的内容。
作为又一个示例，第二消息用于请求修改第一会话，SMF 1可以确定该第一会话属于非无人机业务对应的会话，并确定修改后的第一会话是否为第一个无人机业务对应的会话。如果修改后的第一会话是第一个无人机业务对应的会话，SMF 1执行S604-S609所示的内容，否则，则不执行S604-S609所示的内容。
作为再一个示例，第二消息用于请求修改第一会话，SMF 1确定该第一会话属于无人机业务对应的会话，进一步，SMF 1还可以确定第二消息是否请求将无人机业务对应的会话修改为非无人机业务对应的会话。若第二消息请求将无人机业务对应的会话修改为非无人机业务对应的会话，SMF 1执行S604-S609所示的内容；否则不执行S604-S609所示的内容。
S603的具体实现过程请参考S401的相关内容，此处不再赘述。另外，图6中以第一会话属于无人机业务对应的会话，且第一会话是第一个无人机业务对应的会话为例。
S604：SMF 1释放SMF 1管理的UE的非无人机业务对应的会话，和/或禁止建立或禁止修改非无人机业务对应的会话。
在本实施例中，SMF 1可以释放SMF 1管理的该UE的全部非无人机业务对应的会话，或禁止建立或禁止修改非无人机业务对应的会话，或释放SMF 1管理的该UE的全部非无人机业务对应的会话以及禁止建立或禁止修改非无人机业务对应的会话。例如，SMF 1可以发起会话释放流程，并通知相关NF、网元(如UPF、AMF、RAN等)、UE等释放相关该会话的资源。
可选地，SMF 1可以配置为禁止建立或禁止修改非无人机业务对应的会话的策略。如果SMF 1接收来自UE的用于建立或修改会话的请求消息，SMF 1可以确定该会话是否属于非无人机业务对应的话。若该会话属于无人机业务对应的会话，SMF 1建立或修改该会话；或者，若该会话属于非无人机业务对应的会话，SMF 1可以暂停或终止建立或修改该会话。可选地，SMF 1暂停建立或修改该会话之后，若SMF 1确定满足第二条件，则SMF 1继续建立或修改该会话。
如果步骤S603确定第一会话属于非无人机业务对应的会话，SMF 1可以拒绝该第一会话的建立请求或拒绝对该第一会话的修改请求。可选地，如果该第二消息是请求将第一会话修改为无人机业务对应的会话，SMF 1也可以不拒绝该请求。SMF 1确定第一会话是 否为第一个无人机业务对应的会话。如果第一会话是第一个无人机业务对应的会话，可以执行S605-S609所示的内容；否则不执行S605-S609所示的内容。
如果步骤S603确定第一会话属于无人机业务对应的会话且第二消息用于请求创建第一会话，SMF 1确定第一会话是否为第一个无人机业务对应的会话。如果第一会话是第一个无人机业务对应的会话，可以执行S605-S609所示的内容；否则不执行S605-S609所示的内容。
如果步骤S603确定第一会话属于无人机业务对应的会话且第二消息用于请求修改第一会话，SMF 1确定该请求是否将无人机业务对应的会话修改为非无人机业务对应的会话。如果是，SMF 1拒绝该请求；否则可以执行S605-S609所示的内容。
S605：SMF 1向UE发送第二指示信息；相应地，UE接收来自SMF 1的第二指示信息。
S605为可选步骤。SMF 1可以向UE发送第二指示信息，该第二指示信息可用于指示禁止建立该UE的非无人机业务对应的会话，或可指示禁止在SMF 1处建立该UE的非无人机业务对应的会话。这样，UE接收到第二指示信息后，在发起建立会话之前，可以先确定该会话是否属于无人机业务对应的会话。若该会话属于无人机业务对应的会话，UE发起建立该会话的流程；或者，若该会话属于非无人机业务对应的会话，UE可以暂停发起建立该会话的流程。例如，若UE接收到来自SMF 1的用于指示允许建立非无人机业务对应的会话的指示信息，UE可以发起建立该会话的流程。其中，UE确定会话是否属于无人机业务对应的会话请参考SMF 1确定第一会话是否属于无人机业务对应的会话的相关内容，此处不再赘述。
SMF 1发送的第二指示信息，还可用于指示禁止将无人机业务对应的会话修改为非无人机业务对应的会话。这样，UE接收到第二指示信息后，在发起会话修改流程之前，可以先确定该会话修改请求是否属于将无人机业务对应的会话修改为非无人机业务对应的会话。若该会话修改请求不属于将无人机业务对应的会话修改为非无人机业务对应的会话，UE发起该会话修改流程；或者，若该会话修改请求属于将无人机业务对应的会话修改为非无人机业务对应的会话，UE可以暂停发起该会话修改的流程。例如，若UE接收到来自SMF 1的用于指示允许建立非无人机业务对应的会话的指示信息，UE可以发起该会话修改流程。其中，UE确定会话是否属于无人机业务对应的会话请参考SMF 1确定第一会话是否属于无人机业务对应的会话的相关内容，此处不再赘述。
至此，SMF 1完成了对非无人机业务的限制。可选地，SMF 1还可以执行S606所示的内容。
S606：SMF 1向PCF发送第三消息；相应地，PCF接收来自SMF 1的第三消息。
该第三消息可用于请求或通知限制UE的非无人机业务对应的会话。需要说明的是，本实施例中由PCF执行的步骤同样也可以由UDM或UDR，或AMF执行。
S607：PCF确定SMF 2管理有UE的非无人机业务对应的会话。
PCF接收到第三消息后，可以确定管理有该UE的非无人机业务对应的会话的SMF或PCF确定管理有UE的会话的SMF(图6中以PCF确定SMF 2管理有UE的非无人机业务对应的会话为例)。例如，PCF可以根据UE的上下文信息，和/或从UDM或UDR处获取的UE与SMF的关联信息，确定管理有UE的非无人机业务对应的会话的SMF。可选地，PCF可以根据UE的上下文信息，和/或从UDM或UDR处获取的UE与SMF的关联信息， 确定管理有UE的会话的SMF。需要说明的是，如果PCF确定SMF 2管理有UE的会话，且没有确定SMF 2是否管理了UE的非无人机业务对应的会话，则SMF 2可以在步骤S609确定是否管理了UE的非无人机业务对应的会话，并执行相应操作。
S607的具体实现过程请参考S404，此处不再赘述。
S608：PCF向SMF 2发送第六指示信息；相应地，SMF 2接收来自PCF的第六指示信息。
在本实施例中，该第六指示信息可用于指示(或通知)释放SMF 2管理的该UE的全部非无人机业务对应的会话，或者指示禁止建立或禁止修改非无人机业务对应的会话，或者释放SMF 2管理的该UE的全部非无人机业务对应的会话以及禁止建立或禁止修改非无人机业务对应的会话。
S609：SMF 2释放SMF 2管理的UE的非无人机业务对应的会话，和/或禁止建立或禁止修改非无人机业务对应的会话。
SMF 2可以根据第六指示信息释放SMF 2管理的UE的全部非无人机业务对应的会话和/或禁止建立或禁止修改非无人机业务对应的会话，具体实现过程可参考S604，此处不再赘述。可选地，SMF 2可以向UE发送用于指示禁止建立(或禁止在SMF 2处建立)非无人机业务对应的会话的指示信息。
图7本申请实施例提供的通信方法的又一种流程示意图。在本实施例中，第一设备是SMF 1，以及SMF 1释放该SMF 1管理的UE的部分非无人机业务对应的会话。第二设备是PCF，或是UDM，或是UDR，或是AMF。如图6所示，该方法可以包括如下流程。
其中，图7中的S701至S703、S706、S707、S711与图6中的S601至S603、S606、S607、S605分别对应相同，不同之处在于：
S704：SMF 1确定N大于M。
S704为可选步骤。例如，SMF 1可以根据N和M确定释放UE的非无人机业务对应的会话的数量，即执行S704和S705所示的内容；或者，SMF 1也可以根据来自PCF的第一指示信息确定释放UE的非无人机业务对应的会话的数量，即执行S706、S708和S709所示的内容。
其中，N可以是SMF 1管理的该UE的非无人机业务对应的会话的数量。例如，第一设备可以根据UE的上下文信息确定该N，或者从UDM或UDR处获取该N，本申请实施例对N的获取方式并不限定于此。M可以是UE在执行无人机业务时允许在SMF 1处建立的非无人机业务对应的会话的数量。该M可以是预先设置的，或者是PCF配置，或者是从UDM或UDR处获取的，本申请实施例对M的实现方式不作限定。
在S704中，SMF 1可以确定N是否大于M，如果N小于或等于M且执行了步骤S701，则执行建立或修改第一会话的流程；如果N小于或等于M且没有执行步骤S701，则流程结束；如果N大于M，则SMF 1执行S705所示的内容。
S705：SMF 1确定释放H个非无人机业务对应的会话。
H为大于或等于(N-M)的正整数。例如，SMF 1可以确定释放N个非无人机业务对应的会话中的H个非无人机业务对应的会话。例如，SMF 1可以从该N个非无人机业务对应的会话中任意选取H个非无人机业务对应的会话。又例如，SMF 1可以根据该N个非无人机业务对应的会话的优先级选择H个非无人机业务对应的会话，如该N个非无人机业务 对应的会话中优先级较低的H个非无人机业务对应的会话。再例如，SMF 1可以根据会话建立时长和/或会话所消耗的资源等从该N个非无人机业务对应的会话中选取H个非无人机业务对应的会话，如建立时长较长的(或较短的)H个非无人机业务对应的会话，或资源消耗较多的(或较少的)H个非无人机业务对应的会话等。应理解的是，本申请实施例对H个非无人机业务对应的会话的选取不作限定。
S708：PCF确定SMF 1释放H个非无人机业务对应的会话以及SMF 2释放Q个非无人机业务对应的会话。
在一种可能的实现方式中，SMF 1可以向PCF发送N，如将N携带在第三消息发送给PCF；PCF可以根据N和M，确定N大于M以及确定SMF 1释放UE的H个非无人机业务。
在另一种可能的实现方式中，PCF维护有UE已建立的非无人机业务对应的会话的数量，如PCF接收来自SMF 1的N以及接收来自SMF 2的其管理的该UE的非无人机业务对应的会话的数量。PCF可以根据UE已建立的非无人机业务对应的会话的数量(如记为X，X为正整数)以及UE在执行无人机业务时允许建立的非无人机业务对应的会话的数量(如记为Y，Y为正整数)判断SMF是否释放UE的非无人机业务对应会话。其中的Y可以是预先定义的，本申请实施例对此不作限定。若X小于或等于Y，PCF确定SMF不释放UE的非无人机业务对应会话；或者，若X大于Y，PCF可以确定SMF释放该UE的大于或等于(X-Y)个非无人机业务对应会话。进一步，PCF可以确定SMF 1释放其管理的该UE的一个或多个(如记为H个)非无人机业务对应的会话，以及确定SMF 2释放其管理的该UE的Q个(Q为正数)非无人机业务对应的会话。例如，PCF可以根据X、Y、N以及M确定SMF 1释放其管理的该UE的H个非无人机业务对应的会话。
需要说明的是，PCF确定SMF 2释放Q个非无人机业务对应的会话可参考PCF确定SMF 1释放H个非无人机业务对应的会话的实现过程，此处不再赘述。另外，SMF 1根据N和M确定的待释放的非无人机业务对应的会话的数量，与PCF根据N和M，或根据X、Y、N以及M确定的待释放的非无人机业务对应的会话的数量可以相同，也可以不同，本申请实施例不作限定。
需要说明的是，由PCF执行的步骤同样也可以由UDM或UDR或AMF执行。
S709：PCF向SMF 1发送第一指示信息；相应地，SMF 1接收来自PCF的第一指示信息。
在本实施例中，第一指示信息用于指示释放UE的H个非无人机业务对应的会话。
S710：SMF 1释放SMF 1管理的UE的H个非无人机业务对应的会话。
在S710中，SMF 1释放该SMF 1管理的UE的H个非无人机业务对应的会话，和/或禁止建立或禁止修改非无人机业务对应的会话，具体实现过程请参考S604的相关描述，此处不再赘述。为了便于描述，图7以SMF 1释放SMF 1管理的UE的H个非无人机业务对应的会话为例。
S712：PCF向SMF 2发送第六指示信息；相应地，SMF 2接收来自PCF的第六指示信息。
第六指示信息可用于指示释放SMF 2管理的UE的Q个非无人机业务对应的会话，和/或指示禁止建立或禁止修改非无人机业务对应的会话。为了便于描述，图7以第六指示信息指示释放SMF 2管理的UE的Q个非无人机业务对应的会话为例。
S713：SMF 2释放SMF 2管理的UE的Q个非无人机业务对应的会话和/或禁止建立或禁止修改非无人机业务对应的会话。
在S713中，SMF 2释放该SMF 2管理的UE的Q个非无人机业务对应的会话，和/或禁止建立或禁止修改非无人机业务对应的会话，具体实现过程请参考S604的相关描述，此处不再赘述。为了便于描述，图7以SMF 2释放SMF 2管理的UE的Q个非无人机业务对应的会话为例。
图8为本申请实施例提供的通信方法的又一种流程示意图。在本实施例中，第一设备是UE，以及UE不向或暂停向SMF 1发送用于请求建立或修改非无人机业务对应的会话。如图8所示，该方法可以包括如下流程。
S801：AF向SMS-SC发送第十消息。相应地，SMS-SC接收来自AF的第十消息。
第十消息用于触发UE请求建立或修改第二会话，该第十消息例如可以是SMS消息，但本申请实施例对第十消息的具体实现形式不作限定。例如，AF可以确定触发UE发起第二会话的建立或修改，并生成第十消息，以及向SMS-SC发送第十消息。例如，AF可以根据应用需求(如主动向UE推送视频数据等)或UE的应用需求等确定触发UE发起第二会话的建立或修改流程。
可选地，AF向SMS-SC发送第十消息，该第十消息可以经过NEF和UDM到达SMS-SC。其中，NEF和UDM可以对AF进行验证，确定该第十消息的接收端设备是SMS-SC。应理解的是，本申请实施例对第十消息的传输路径不作限定。
S802：SMS-SC向UE发送第十一消息。相应地，UE接收来自SMS-SC的第十一消息。
SMS-SC接收到第十消息后，向UE发送第十一消息，该第十一消息用于通知UE触发第二会话的建立或修改流程。
可选地，SMS-SC可以向AF发送响应消息，该响应消息指示已将第十一消息发送给UE。
S803：UE确定满足第一条件。
第一条件可以包括如下条件中的一种或多种：UE被授权无人机业务，UE发起建立第一个无人机业务对应的会话，或者UE处于飞行状态。例如，UE可以根据存储的上下文信息或无人机授权状态确定自身是否被授权无人机业务。又例如，UE可以根据存储的上下文信息或会话状态确定将要发起的会话建立是第一个无人机业务对应的会话。再例如，UE可以根据移动信息和/或第五指示信息确定处于飞行状态。S803的具体实现过程请参考S401的相关内容，此处不再赘述。
S804：UE确定第二会话是否属于非无人机业务对应的会话。
S804为可选步骤。例如，UE确定满足第一条件后可以不向或暂停向SMF 1发送第十二消息，该第十二消息用于请求建立或修改第二会话。又例如，UE可以根据第十一消息确定第二会话是否属于非无人机业务对应的会话。该第十一消息可以包括如下信息中一种或多种：UE的类型指示信息、UAV ID、DNN、USS地址信息、USS ID、S-NSSAI标识、AF ID、或会话的业务类型等。其中UE根据第十一消息确定第二会话是否属于非无人机业务对应的会话的实现方式请参考S401的相关描述，此处不再赘述。
可选地，该第十一消息可以包括UE标识(如通用公共用户标识(generic public subscription identifier，GPSI)或SUPI、UAV ID等)和/或AF标识。UE可以根据UE标识 和/或AF标识确定第二会话的业务类型。例如，UE标识为普通终端标识，而不是无人机标识(如UAV ID)，UE可以确定第二会话属于非无人机业务对应的会话。又例如，AF标识所指示的AF属于非无人机业务的AF或该AF不属于无人机业务的AF(不属于USS)，UE可以确定第二会话属于非无人机业务对应的会话。
如果UE确定第二会话属于无人机业务对应的会话，则执行S805所示内容；或者，如果UE确定第二会话属于非无人机业务对应的会话，则执行S806所示的内容。在另一种可选实现方式中，如果UE确定第二会话属于无人机业务对应的会话，且准备触发将该会话修改为非无人机业务对应的会话，则执行S806所示的内容；或者，如果UE确定第二会话属于非无人机业务对应的会话，且准备触发将该会话修改为无人机业务对应的会话，则执行S805所示的内容。
S805：UE向SMF 1发送第十二消息；相应地，SMF 1接收来自UE的第十二消息。
在S805中，第二会话属于无人机业务对应的会话，UE可以触发对第二会话的修改或建立，即触发对无人机业务对应的会话的修改或建立。例如，UE向SMF 1发送第十二消息。
S806：UE不向或暂停向SMF 1发送第十二消息。
在S806中，第二会话属于非无人机业务对应的会话，UE不触发对第二会话的修改或建立，即UE不触发对非无人机业务对应的会话的修改或建立。例如，UE不向或暂停向SMF1发送第十二消息。可选地，若UE暂停向SMF 1发送第十二消息，UE可以启动第二计时器。进一步，若在第二计时器运行期间(或运行结束时)满足第一条件，UE不向SMF 1发送第十二消息；或者若在第二计时器运行期间满足第二条件，UE向SMF 1发送第十二消息。其中有关第二条件的描述请参考图4的相关内容，此处不再赘述。
在图8所示的流程中，UE通过SMS-SC接收到来自AF的用于请求建立或修改第二会话的第十一消息之后可以确定满足第一条件，并在确定该第二会话属于非无人机业务对应的会话的情况下，不向或暂停向SMF 1发送该第十二消息，避免了发起对非无人机业务对应的会话的建立或修改，从而能够减少攻击者利用非无人机业务对UE的攻击，以及避免非无人机业务侵占无人机业务的资源。
图9为本申请实施例提供的通信方法的又一种流程示意图。在本实施例中，第一设备是SMS-SC，以及SMS-SC不向或暂停向UE发送用于请求建立或修改非无人机业务对应的会话。如图9所示，该方法可以包括如下流程。
S901：AF向SMS-SC发送第十消息。相应地，SMS-SC接收来自AF的第十消息。
其中S901的具体实现过程请参考S801，此处不再赘述。
S902：SMS-SC确定满足第一条件。
第一条件可以包括如下条件中的一种或多种：UE被授权无人机业务，UE发起建立第一个无人机业务对应的会话，或者UE处于飞行状态。例如，SMS-SC可以订阅AMF(或SMF或UAS NF)的有关UE的无人机授权状态或飞行状态的服务。例如，当UE被授权无人机业务时，AMF(或SMF或UAS NF)可以通知SMS-SC该UE被授权无人机业务；或者SMS-SC也可以向AMF(或SMF或UAS NF)发送请求消息，获取UE的无人机授权状态或飞行状态。又例如，SMS-SC可以向AMF(或SMF或UDR或UDM)订阅与会话状态相关的服务。例如，当UE的无人机业务对应的会话数量发生改变时，AMF(或SMF 或UDR或UDM)可以通知SMS-SC该UE已有的无人机业务对应的会话数量，从而SMS-SC可以确定第二会话是否为UE发起建立的第一个无人机业务对应的会话；或者，SMS-SC也可以向AMF(或SMF或UDR或UDM)发送请求消息，获取UE的无人机业务对应的会话数量，从而确定UE发起建立的会话(即第二会话)是否为建立第一个无人机业务对应的会话。再例如，SMS-SC可以本地存储UE的上下文信息，该UE的上下文信息包括UE的无人机授权状态和飞行状态，这样，SMS-SC可以根据本地存储的UE的上下文信息确定UE的无人机授权状态或飞行状态。S902的具体实现过程请参考S401的相关内容，此处不再赘述。
S903：SMS-SC确定第二会话是否属于非无人机业务对应的会话。
S903为可选步骤。例如，SMS-SC确定满足第一条件后可以不向或暂停向UE发送第十一消息。该第十一消息用于触发UE请求建立或修改第二会话。又例如，SMS-SC可以根据第十消息确定第二会话是否属于非无人机业务对应的会话。该第十消息可以包括如下信息中的一种或多种：UE的类型指示信息、UAV ID、DNN、USS地址信息、USS ID、S-NSSAI标识、AF ID、或会话的业务类型等。其中SMS-SC根据第十消息确定第二会话是否属于非无人机业务对应的会话的实现方式请参考S401的相关描述，此处不再赘述。
可选地，若第十消息用于修改第二会话，SMS-SC可以向其它设备(如SMF或UDM或UDR)发送用于请求该第二会话是否属于非无人机业务对应的会话的消息(即从其他设备获取第二会话是否属于非无人机业务对应的会话)。
可选地，该第十消息可以包括UE标识(如通用公共用户标识(generic public subscription identifier，GPSI)或SUPI、UAV ID等)和/或AF标识。SMS-SC可以根据UE标识和/或AF标识确定第二会话的业务类型。例如，UE标识为普通终端标识，而不是无人机标识(如UAV ID)，UE可以确定第二会话属于非无人机业务对应的会话。又例如，AF标识所指示的AF属于非无人机业务的AF或该AF不属于无人机业务的AF(不属于USS)，UE可以确定第二会话属于非无人机业务对应的会话。
如果SMS-SC确定第二会话属于无人机业务对应的会话，则执行S904和S905所示内容；或者，如果SMS-SC确定第二会话属于非无人机业务对应的会话，则执行S906所示的内容。在另一种可选实现方式中，如果SMS-SC确定第二会话属于无人机业务对应的会话，且准备触发将该会话修改为非无人机业务对应的会话，则执行S906所示的内容；或者，如果SMS-SC确定第二会话属于非无人机业务对应的会话，且准备触发将该会话修改为无人机业务对应的会话，则执行S904和S905所示的内容。
S904：SMS-SC向UE发送第十一消息；相应地，UE接收来自SMS-SC的第十一消息。
在S904中，第二会话属于无人机业务对应的会话或将要修改为无人机业务对应的会话，SMS-SC可以向UE发送第十一消息。
S905：UE向SMF 1发送第十二消息；相应地，SMF 1接收来自UE的第十二消息。
UE接收到第十一消息后，触发对无人机业务对应的会话的修改或建立，以及向SMF 1发送第十二消息。该第十二消息用于请求建立或修改第二会话。
S906：SMS-SC不向或暂停向UE发送第十一消息。
在S906中，第二会话属于非无人机业务对应的会话，SMS-SC不向或暂停向UE发送第十一消息。可选地，若SMS-SC暂停向UE发送第十一消息，SMS-SC可以启动第二计时器。进一步，若在第二计时器运行期间(或运行结束时)满足第一条件，SMS-SC不向 UE发送第十一消息；或者若在第二计时器运行期间满足第二条件，SMS-SC向UE发送第十一消息。其中有关第二条件的描述请参考图4的相关内容，此处不再赘述。
在图9所示的流程中，SMS-SC接收到来自AF的用于请求建立或修改第二会话的第十消息之后可以确定满足第一条件，并在确定该第二会话属于非无人机业务对应的会话的情况下，不向或暂停向UE发送该第十一消息，避免了建立或修改非无人机业务对应的会话，从而能够减少攻击者利用非无人机业务对UE的攻击，以及避免非无人机业务侵占无人机业务的资源。
图10为本申请实施例提供的通信方法的再一种流程示意图。在本实施例中，第一控制面流程是首次认证流程。该首次认证流程可以是由SEAF或AMF或UDM发起的。以及，在本实施例中，第一设备可以是SEAF或AMF；或者第一设备也可以是UDM或AUSF或ARPF。另外，在第一设备是UDM或AUSF或ARPF时，第三设备可以是SEAF或AMF。如图10所示，该方法包括两种实现方式，其中的一种实现方式包括步骤S1002至S1004所示的内容，另一种实现方式包括步骤S1005至S1009所示的内容。
S1001：SEAF确定发起首次认证流程。
S1001为可选步骤。SEAF可以发起UE的首次认证流程。例如，当UE第一次注册到网络时或者SEAF没有存储UE的安全上下文时，SEAF可以发起UE的首次认证流程。又例如，SEAF可以根据网络的配置周期性地或非周期性地发起UE的首次认证流程。应理解的是，本申请实施例对SEAF发起首次认证流程的原因和时间不作限定。
需要说明的是，在本实施例中，由SEAF执行的步骤同样可以由AMF执行。
在SEAF发起首次认证流程之前，SEAF可以执行S1002至S1004所示的内容，或者执行S1005所示的内容。
S1002：SEAF确定UE处于飞行状态。
SEAF可以通过AMF确定UE的状态。一种实现方式，SEAF与AMF合并实现在同一网络功能中，AMF存储有UE的状态，这样SEAF可以读取UE的状态。另一种实现方式，SEAF与AMF为互相独立的网络功能，SEAF可以从AMF处获取UE的状态。例如，SEAF可以向AMF发送用于请求UE的状态的消息；AMF接收到该消息后，向SEAF发送用于指示UE处于飞行状态或处于非飞行状态的指示信息。又例如，SEAF可以向AMF订阅UE的状态；在UE的状态更新(如UE从飞行状态切换至非飞行状态，或者UE从非飞行状态切换至飞行状态)时，AMF可以向SEAF推送UE的状态。其中，AMF获取UE的状态请参考图5的相关内容，此处不再赘述。若SEAF确定UE处于飞行状态，则执行S1003所示内容；若SEAF确定UE处于非飞行状态，则执行该首次认证流程，如向UDM(或AUSF、或ARPF)发送用于请求(或通知)执行首次认证流程的消息。图10以SEAF确定UE处于飞行状态为例。
应理解的是，图10以SEAF确定UE处于飞行状态为例，在另一种可能实现的方式中，该S1002可替换为SEAF确定满足第一条件，具体实现过程请参考S401，此处不再赘述。
S1003：SEAF暂停或终止首次认证流程。
在确定UE处于飞行状态时，SEAF可以暂停或终止首次认证流程。
S1004：在第一计时器运行期间(或运行结束时)UE处于飞行状态，SEAF终止首次认证流程。
S1004为可选步骤。例如，SEAF暂停首次认证流程，该SEAF可以启动第一计时器，并确定在该第一计时器运行期间UE的状态。例如，在计时器运行期间SEAF从AMF处获取UE的状态，具体实现方式请参考S1002的内容，此处不再赘述。若在第一计时器运行期间SEAF从AMF处获取UE处于非飞行状态，SEAF可以结束运行第一计时器，并准备发起首次认证流程，如向UDM(或AUSF、或ARPF)发送用于请求(或通知)执行首次认证流程的消息。若在第一计时器运行期间(或运行结束时)UE处于飞行状态(如SEAF在第一计时器运行期间未接收到来自AMF的用于指示UE处于非飞行状态的信息)，SEAF可以终止首次认证流程，如在第一计时器运行结束时终止首次认证流程。图10在第一计时器运行期间UE处于飞行状态为例。
S1005：SEAF向UDM发送第四消息；相应地，UDM接收来自SEAF的第四消息。
在本实施例中，该第四消息例如可以是认证请求(authenticate request)消息，但本申请实施例对第四消息的名称并不限定于此。该第四消息可用于请求(或通知)执行首次认证流程。
需要说明的是，在本实施例中，由UDM执行的步骤同样可以由AUSF或ARPF执行。
S1006：UDM确定UE处于飞行状态。
UDM可以确定UE的状态。例如，UDM可以从AMF处获取UE的状态，具体实现方式请参考SEAF从AMF处获取UE的状态的描述，此处不再赘述。若UDM确定UE处于飞行状态，则执行S1007所示内容；若UDM确定UE处于非飞行状态，则执行该首次认证流程，如根据第四消息，生成UE的认证向量等，并执行步骤S1009。图10以UDM确定UE处于飞行状态为例。
应理解的是，图10以UDM确定UE处于飞行状态为例，在另一种可能实现的方式中，该S1006可替换为UDM确定满足第一条件，具体实现过程请参考S401，此处不再赘述。
S1007：UDM暂停或终止首次认证流程。
在确定UE处于飞行状态时，UDM可以暂停或终止首次认证流程。
S1008：在第一计时器运行期间UE处于飞行状态，UDM终止首次认证流程。
S1008为可选步骤。例如，UDM暂停首次认证流程，该UDM可以启动第一计时器，并确定在该第一计时器运行期间UE的状态，具体实现过程请参考S1004的相关内容，此处不再赘述。若在第一计时器运行期间(或运行结束时)UDM从AMF处获取UE处于非飞行状态，UDM可以结束运行第一计时器，并执行首次认证流程。若在第一计时器运行期间(或运行结束时)UE处于飞行状态(如UDM在第一计时器运行期间未接收到来自AMF的用于指示UE处于非飞行状态的信息)，UDM可以终止首次认证流程，如在第一计时器运行结束时终止首次认证流程。图10在第一计时器运行期间UE处于飞行状态为例。
需要说明的是，SEAF在S1004中启动的计时器与UDM在S1008启动的计时器可以相同，也可以不同，本申请实施例对此不作限定。
S1009：UDM向SEAF发送第五消息；相应地，SEAF接收来自UDM的第五消息。
在本实施例中，该第五消息例如可以是认证响应(authenticate response)消息，但本申请实施例对第五消息的名称并不限定于此。当执行首次认证流程时，该第五消息可以包括步骤S1006所述的认证向量。当未执行首次认证流程时，该第五消息可用于指示未执行首次认证流程。可选地，该第五消息可包括不执行首次认证流程的原因。该不执行首次认证流程的原因例如可以是超时，和/或UE处于飞行状态等。
在图10所示的流程中，在执行(或发起)UE的首次认证流程之前，第一设备可以确定UE的状态，并在确定UE处于飞行状态时，暂停或终止UE的首次认证流程，这样可以避免在UE飞行中因执行UE的首次认证流程导致UE功耗增加，使得UE的电量提前耗尽，不能完成飞行任务等问题。并且，首次认证流程的暂停或终止执行能够释放执行该首次认证流程所需的资源，从而能够为飞行中的UE提供更多的可使用资源用于执行无人机业务。
图11为本申请实施例提供的通信方法的再一种流程示意图。在本实施例中，第一控制面流程是去注册流程，该去注册流程可以是UDM发起的，也可以时AMF发起的。以及，在本实施例中，第一设备可以是UDM；或者第一设备也可以是AMF。另外，在第一设备是AMF时，第三设备可以是UDM。如图11所示，该方法包括两种实现方式，其中的一种实现方式包括步骤S1102至S1104所示的内容，另一种实现方式包括步骤S1105至S1109所示的内容。当去注册流程为AMF发起时，不执行步骤S1101-S1105。
S1101：UDM确定发起去注册流程。
S1101为可选步骤。UDM可以发起UE的去注册流程。例如，UDM可以根据运营需求(如UE的签约信息改变、UE的签约不支持当前的使用状况、使用地域等)确定发起UE的去注册流程。应理解的是，本申请实施例对UDM发起去注册流程的原因和时间不作限定。
在UDM发起去注册流程之前，UDM可以执行S1102至S1104所示的内容，或者执行S1105所示的内容。
S1102：UDM确定UE处于飞行状态。
UDM可以确定UE的状态。例如，UDM可以从AMF或UDR处获取UE的状态，具体实现过程请参考图10中SEAF从AMF处获取UE的状态的相关内容，此处不再赘述。若UDM确定UE处于飞行状态，则执行S1103所示内容；若UDM确定UE处于非飞行状态，则执行该去注册流程，如向AMF发送用于请求(或通知)执行去注册流程的消息。图11以UDM确定UE处于飞行状态为例。
应理解的是，图11以UDM确定UE处于飞行状态为例，在另一种可能实现的方式中，该S1102可替换为UDM确定满足第一条件，具体实现过程请参考S401，此处不再赘述。
S1103：UDM暂停或终止去注册流程。
在确定UE处于飞行状态时，UDM可以暂停或终止去注册流程。
S1104：在第一计时器运行期间UE处于飞行状态，UDM终止去注册流程。
S1104为可选步骤。例如，UDM暂停去注册流程，该UDM可以启动第一计时器，并确定在该第一计时器运行期间UE的状态，具体实现过程请参考S1004的相关内容，此处不再赘述。若在第一计时器运行期间UDM从AMF处获取UE处于非飞行状态，UDM可以结束运行第一计时器，并准备发起去注册流程，如向AMF发送用于请求(或通知)执行去注册流程的消息。若在第一计时器运行期间UE处于飞行状态(如UDM在第一计时器运行期间未接收到来自AMF的用于指示UE处于非飞行状态的信息)，UDM可以终止去注册流程，如在第一计时器运行结束时终止去注册流程。图11在第一计时器运行期间UE处于飞行状态为例。
S1105：UDM向AMF发送第四消息；相应地，AMF接收来自UDM的第四消息。
在本实施例中，该第四消息例如可以是去注册通知(deregistration notification)消息，但本申请实施例对第四消息的名称并不限定于此。该第四消息可用于请求(或通知)执行去注册流程。
S1106：AMF确定UE处于飞行状态。
AMF可以确定UE的状态，具体实现过程请参考图5的内容，此处不再赘述。若AMF确定UE处于飞行状态，则执行S1107所示内容；若AMF确定UE处于非飞行状态，则执行该去注册流程，如，发起释放UE所有会话的流程。可选地，AMF可以向UE发送用于去注册的请求消息。图11以AMF确定UE处于飞行状态为例。
应理解的是，图11以AMF确定UE处于飞行状态为例，在另一种可能实现的方式中，该S1106可替换为AMF确定满足第一条件，具体实现过程请参考S401，此处不再赘述。
需要说明的是，在AMF发起的去注册流程中，不执行S1101-S1105，而是执行S1106。例如，AMF可以根据运营或管理的要求、AMF无法支持UE被允许的、或者预定的去注册时间到期。应理解的是，本申请实施例对AMF发起去注册流程的原因和时间不作限定。
S1107：AMF暂停或终止去注册流程。
在确定UE处于飞行状态时，AMF可以暂停或终止去注册流程。
S1108：在第一计时器运行期间UE处于飞行状态，AMF终止去注册流程。
S1108为可选步骤。例如，AMF暂停去注册流程，该AMF可以启动第一计时器，并确定在该第一计时器运行期间UE的状态，具体实现过程请参考S1104的相关内容，此处不再赘述。若在第一计时器运行期间UE处于非飞行状态，AMF可以结束运行第一计时器，并执行去注册流程。若在第一计时器运行期间UE处于飞行状态，AMF可以终止去注册流程，如在第一计时器运行结束时终止去注册流程。图11在第一计时器运行期间UE处于飞行状态为例。
需要说明的是，UDM在S1104中启动的计时器与AMF在S1108启动的计时器可以相同，也可以不同，本申请实施例对此不作限定。
S1109：AMF向UDM发送第五消息；相应地，UDM接收来自AMF的第五消息。
在本实施例中，该第五消息例如可以是去注册通知响应(deregistration notification response)消息，但本申请实施例对第五消息的名称并不限定于此。如果去注册流程没有执行，该第五消息可用于指示未执行去注册流程。如果在S1106执行了去注册流程(UE不处于飞行状态或不满足第一条件)，该第五消息可用于确认收到了第四消息。可选地，该第五消息可包括不执行去注册流程的原因。该不执行去注册流程的原因例如可以是超时，和/或UE处于飞行状态等。
在图11所示的流程中，在执行(或发起)UE的去注册流程之前，第一设备可以确定UE的状态，并在确定UE处于飞行状态时，暂停或终止UE的去注册流程，这样可以避免在UE飞行中因完成UE的去注册流程断开了UE与移动通信网络之间的连接导致UE无法与移动通信网络进行通信，使得UE不能响应遥控器的控制指令，不能执行无人机业务等问题。并且，去注册流程的暂停或终止执行能够释放执行该去注册流程所需的资源，从而能够为飞行中的UE提供更多的可使用资源用于执行无人机业务。
图12为本申请实施例提供的通信方法的再一种流程示意图。在本实施例中，第一控 制面流程是切片认证流程，该切片认证流程可以是AAA-S发起的，或者也可以是由DN发起的，也可以是AMF发起的。以及，在本实施例中，第一设备可以是NSSAAF；或者第一设备也可以是AMF。另外，在第一设备是NSSAAF时，第三设备是AAA-S或DN；或者，在第一设备是AMF时，第三设备可以是NSSAAF。如图12所示，当切片认证流程为AAA-S(或DN)发起时，该方法包括两种实现方式，其中的一种实现方式包括步骤S1203至S1206所示的内容，另一种实现方式包括步骤S1207至S1212所示的内容。当切片认证流程为AMF发起时，实现方式包括步骤S1208至S1212所示的内容。
S1201：AAA-S确定发起切片认证流程或者切片重认证流程。
图12中以AAA-S确定发送切片认证流程为例。
S1201为可选步骤。AAA-S可以发起UE的切片认证流程。例如，AAA-S可以根据AAA-S检测到UE的切片使用状况出现异常等确定发起UE的切片认证流程。又例如，AAA-S可以周期性地或非周期性地发起UE的切片认证流程。应理解的是，本申请实施例对AAA-S发起切片认证流程的原因和时间不作限定。
需要说明的是，在本实施例中，由AAA-S执行的步骤同样也可以由DN执行。
S1202：AAA-S向NSSAAF发送第四消息；相应地，NSSAAF接收来自AAA-S的第四消息。
在本实施例中，该第四消息例如可以是认证请求消息或者重认证请求(re-authenticate request)消息，但本申请实施例对第四消息的名称并不限定于此。该第四消息可用于请求(或通知)执行切片认证流程。
在NSSAAF接收到第四消息后，NSSAAF可以执行S1203至S1206所示的内容，或者执行S1207所示的内容。
S1203：NSSAAF确定UE处于飞行状态。
NSSAAF可以确定UE的状态。例如，NSSAAF可以从AMF处获取UE的状态，具体实现过程请参考图10中SEAF从AMF处获取UE的状态的相关内容，此处不再赘述。若NSSAAF确定UE处于飞行状态，则执行S1204所示内容；若NSSAAF确定UE处于非飞行状态，则执行该切片认证流程，如向AMF发送用于请求(或通知)执行切片认证流程的消息。图12以NSSAAF确定UE处于飞行状态为例。
应理解的是，图12以NSSAAF确定UE处于飞行状态为例，在另一种可能实现的方式中，该S1202可替换为NSSAAF确定满足第一条件，具体实现过程请参考S401，此处不再赘述。
S1204：NSSAAF暂停或终止切片认证流程。
在确定UE处于飞行状态时，NSSAAF可以暂停或终止切片认证流程。
S1205：在第一计时器运行期间UE处于飞行状态，NSSAAF终止切片认证流程。
S1205为可选步骤。例如，NSSAAF暂停切片认证流程，该NSSAAF可以启动第一计时器，并确定在该第一计时器运行期间UE的状态，具体实现过程请参考S1004的相关内容，此处不再赘述。若在第一计时器运行期间NSSAAF从AMF处获取UE处于非飞行状态，NSSAAF可以结束运行第一计时器，并执行切片认证流程，如向AMF发送用于请求(或通知)执行切片认证流程的消息。若在第一计时器运行期间UE处于飞行状态(如NSSAAF在第一计时器运行期间未接收到来自AMF的用于指示UE处于非飞行状态的信息)，NSSAAF可以终止切片认证流程，如在第一计时器运行结束时终止切片认证流程。 图12在第一计时器运行期间UE处于飞行状态为例。
S1206：NSSAAF向AAA-S发送第五消息；相应地，AAA-S接收来自NSSAAF的第五消息。
在本实施例中，该第五消息例如可以是认证响应或重认证响应(re-authenticate response)消息，但本申请实施例对第五消息的名称并不限定于此。该第五消息可用于指示未执行切片认证流程。可选地，该第五消息可包括不执行切片认证流程的原因。该不执行切片认证流程的原因例如可以是超时，和/或UE处于飞行状态等。
S1207：NSSAAF向AMF发送第四消息；相应地，AMF接收来自NSSAAF的第四消息。
其中有关第四消息的描述请参考S1202的内容，此处不再赘述。
S1208：AMF确定UE处于飞行状态。
需要说明的是，在AMF发起的切片认证流程中，不执行S1201-S1207，而是直接执行S1208。例如，AMF可以根据收到的UE的注册请求消息确定UE需要进行切片认证，从而准备发起切片认证。又例如，当UE重新执行了主认证之后或UE移动到新的PLMN(如漫游)，AMF确定需要发起切片认证。应理解的是，本申请实施例对AMF发起切片认证流程的原因和时间不作限定。
AMF可以确定UE的状态，具体实现过程请参考图5的内容，此处不再赘述。
若AMF确定UE处于飞行状态，则执行S1209所示内容。
若AMF确定UE处于非飞行状态，则不执行步骤S1209-S1212，而是执行切片认证流程。如果是AAA-S发起的切片认证，AMF可以向NSSAAF发送第四消息的响应消息。可选的，AMF在发送该第四消息的响应消息之前，可以向UE发送切片认证消息。进一步，若AMF发起的切片认证流程，AMF还可以向AAA-S(经过NSSAAF)发送切片认证请求消息。图12没有示出关于进行切片认证的步骤。以及，图12以AMF确定UE处于飞行状态为例。
应理解的是，图12以AMF确定UE处于飞行状态为例，在另一种可能实现的方式中，该S1208可替换为AMF确定满足第一条件，具体实现过程请参考S401，此处不再赘述。
S1209：AMF暂停或终止切片认证流程。
在确定UE处于飞行状态时，AMF可以暂停或终止切片认证流程。
S1210：在第一计时器运行期间UE处于飞行状态，AMF终止切片认证流程。
S1210为可选步骤。例如，AMF暂停切片认证流程，该AMF可以启动第一计时器，并确定在该第一计时器运行期间UE的状态，具体实现过程请参考S1205的相关内容，此处不再赘述。若在第一计时器运行期间UE处于非飞行状态，AMF可以结束运行第一计时器，并执行切片认证流程。若在第一计时器运行期间UE处于飞行状态，AMF可以终止切片认证流程，如在第一计时器运行结束时终止切片认证流程。图12在第一计时器运行期间UE处于飞行状态为例。
需要说明的是，NSSAAF在S1205中启动的计时器与AMF在S1210启动的计时器可以相同，也可以不同，本申请实施例对此不作限定。
S1211：AMF向NSSAAF发送第五消息；相应地，NSSAAF接收来自AMF的第五消息。
其中有关第五消息的描述请参考S1206的内容，此处不再赘述。
S1212：NSSAAF向AAA-S发送第五消息；相应地，AAA-S接收来自NSSAAF的第五消息。
NSSAAF接收到第五消息后，可以将该第五消息转发给AAA-S，具体请参考S1206的相关描述，此处不再赘述。
在图12所示的流程中，在执行UE的切片认证流程之前，第一设备可以确定UE的状态，并在确定UE处于飞行状态时，暂停或终止UE的切片认证流程，这样可以避免在UE飞行中因执行UE的切片认证流程导致UE功耗增加，使得UE的电量提前耗尽，不能完成飞行任务等问题。并且，切片认证流程的暂停或终止执行能够释放执行该切片认证流程所需的资源，从而能够为飞行中的UE提供更多的可使用资源用于执行无人机业务。
图13为本申请实施例提供的通信方法的又一种流程示意图。在本实施例中，第一控制面流程是二次认证流程，该二次认证流程可以是AAA-S发起的，或者也可以是由DN发起的，也可以是SMF发起的。以及，在本实施例中，第一设备是SMF，第三设备是AAA-S或DN。如图13所示，该方法包括如下步骤。
S1301：AAA-S确定发起二次认证流程或者二次认证的重认证流程。
图13中以AAA-S确定发起二次认证流程为例。
S1301为可选步骤。AAA-S可以发起UE的二次认证流程。例如，AAA-S可以根据AAA-S检测到UE的会话出现异常等确定发起UE的二次认证流程。又例如，AAA-S可以周期性地或非周期性地发起UE的二次认证流程。应理解的是，本申请实施例对AAA-S发起二次认证流程的原因和时间不作限定。
需要说明的是，在本实施例中，由AAA-S执行的步骤同样也可以由DN执行。
S1302：AAA-S向SMF发送第四消息；相应地，SMF接收来自AAA-S的第四消息。
在本实施例中，该第四消息例如可以是重认证请求(re-authenticate request)或认证请求消息，但本申请实施例对第四消息的名称并不限定于此。该第四消息可用于请求(或通知)执行二次认证流程。
S1303：SMF确定UE处于飞行状态。
需要说明的是，在SMF发起的二次认证流程中，SMF不执行S1301-S1302，而是直接发起S1303。例如，SMF可以根据收到的UE的会话建立请求消息确定UE需要进行二次认证。应理解的是，本申请实施例对SMF发起二次认证流程的原因和时间不作限定。
SMF可以确定UE的状态。例如，SMF可以从AMF处获取UE的状态，具体实现过程请参考图10中SEAF从AMF处获取UE的状态的相关内容，此处不再赘述。若SMF确定UE处于飞行状态，则执行S1304所示内容；若SMF确定UE处于非飞行状态，则执行该二次认证流程(AAA-S发起的二次认证流程)或发起二次认证流程(AMF发起的二次认证流程)，二次认证流程在图13中未示出。图13以SMF确定UE处于飞行状态为例。
应理解的是，图13以SMF确定UE处于飞行状态为例，在另一种可能实现的方式中，该S1302可替换为SMF确定满足第一条件，具体实现过程请参考S401，此处不再赘述。
S1304：SMF暂停或终止二次认证流程。
在确定UE处于飞行状态时，SMF可以暂停或终止二次认证流程。
S1305：在第一计时器运行期间UE处于飞行状态，SMF终止二次认证流程。
S1305为可选步骤。例如，SMF暂停二次认证流程，该SMF可以启动第一计时器， 并确定在该第一计时器运行期间UE的状态，具体实现过程请参考S1004的相关内容，此处不再赘述。若在第一计时器运行期间SMF从AMF处获取UE处于非飞行状态，SMF可以结束运行第一计时器，并准备发起二次认证流程，如向AMF发送用于请求(或通知)执行二次认证流程的消息。若在第一计时器运行期间UE处于飞行状态(如SMF在第一计时器运行期间未接收到来自AMF的用于指示UE处于非飞行状态的信息)，SMF可以终止二次认证流程，如在第一计时器运行结束时终止二次认证流程。图13在第一计时器运行期间UE处于飞行状态为例。
S1306：SMF向AAA-S发送第五消息；相应地，AAA-S接收来自SMF的第五消息。
在本实施例中，该第五消息例如可以是重认证响应(re-authenticate response)消息，但本申请实施例对第五消息的名称并不限定于此。该第五消息可用于指示未执行二次认证流程。可选地，该第五消息可包括不执行二次认证流程的原因。该不执行二次认证流程的原因例如可以是超时，和/或UE处于飞行状态等。
在图13所示的流程中，在执行UE的二次认证流程之前，第一设备可以确定UE的状态，并在确定UE处于飞行状态时，暂停或终止UE的二次认证流程，这样可以避免在UE飞行中因执行UE的二次认证流程导致UE功耗增加，使得UE的电量提前耗尽，不能完成飞行任务等问题。并且，二次认证流程的暂停或终止执行能够释放执行该二次认证流程所需的资源，从而能够为飞行中的UE提供更多的可使用资源用于执行无人机业务。
上述本申请提供的实施例中，分别从第一设备与第二设备之间交互的角度对本申请实施例提供的方法进行了介绍。为了实现上述本申请实施例提供的方法中的各功能，第一设备或第二设备可以包括硬件结构和/或软件模块，以硬件结构、软件模块、或硬件结构加软件模块的形式来实现上述各功能。
下面结合附图介绍本申请实施例中用来实现上述方法的通信装置。因此，上文中的内容均可以用于后续实施例中，重复的内容不再赘述。
图14示出了一种通信装置1400的结构示意图。该通信装置1400可以对应实现上述各个方法实施例中由第一设备或第二设备实现的功能或者步骤。该通信装置可以包括处理单元1401和收发单元1402。可选地，通信装置1400还可以包括存储单元(图14中未示出)，该存储单元可以用于存储指令(代码或者程序)和/或数据。处理单元1401和收发单元1402可以与该存储单元耦合，例如，处理单元1401可以读取存储单元中的指令(代码或者程序)和/或数据，以实现相应的方法。上述各个单元可以独立设置，也可以部分或者全部集成。例如收发单元1402可包括发送单元和接收单元。
作为一个示例，通信装置1400可实现上述各个方法实施例中由第一设备实现的功能或步骤。
其中，处理单元1401，用于确定满足第一条件，所述第一条件包括如下条件中的一种或多种：终端设备被授权无人机业务，所述终端设备发起建立第一个所述无人机业务对应的会话，或者所述终端设备处于飞行状态；以及，限制所述终端设备的非无人机业务和/或限制所述终端设备的第一控制面流程，其中，所述第一控制面流程不是所述无人机业务专有的流程。
在一种可能的实现方式中，在限制所述终端设备的非无人机业务时，处理单元1401具体可以用于：
所述第一设备是第一会话管理功能设备，释放所述第一设备管理的全部或部分的所述非无人机业务对应的会话，和/或禁止建立或禁止修改所述非无人机业务对应的会话。
或者，所述第一设备是短消息业务服务中心，不向或暂停向所述终端设备发送第一消息，所述第一消息用于请求建立或修改所述非无人机业务对应的会话。
或者，所述第一设备是所述终端设备，不向或暂停向第一会话管理功能设备发送第一消息，所述第一消息用于请求建立或修改所述非无人机业务对应的会话。
在一种可能的实现方式中，若所述第一设备确定所述终端设备被授权所述无人机业务，和/或所述终端设备处于飞行状态，在所述第一设备限制所述终端设备的非无人机业务和/或限制所述第一控制面流程之前，收发单元1402，用于接收来自所述终端设备的第二消息，所述第二消息用于请求建立第一会话；以及，处理单元1401，进一步用于根据所述第二消息，确定所述第一会话属于所述无人机业务对应的会话。
在一种可能的实现方式中，收发单元1402，进一步用于：向第二设备发送第三消息，所述第三消息用于请求限制所述终端设备的所述非无人机业务。
在一种可能的实现方式中，收发单元1402，进一步用于：接收来自所述第二设备的第一指示信息，所述第一指示信息用于指示释放一个或多个所述非无人机业务对应的会话。在限制终端设备非无人机业务时，处理单元1401，具体用于：根据所述第一指示信息释放一个或多个所述非无人机业务对应的会话。
在另一种可能的实现方式中，所述第一设备限制所述终端设备的非无人机业务包括所述第一设备释放所述第一设备管理的全部或部分的所述非无人机业务对应的会话，处理单元1401，进一步用于：确定N大于M，其中，所述N是所述第一设备所管理的所述非无人机业务对应的会话的数量，所述M是所述终端设备在执行所述无人机业务时允许在所述第一设备处建立的所述非无人机业务对应的会话的数量；以及确定释放H个所述非无人机业务对应的会话，所述H为大于或等于(N-M)的正整数。
在一种可能的实现方式中，在限制所述终端设备的非无人机业务时，收发单元1402，用于向所述终端设备发送第二指示信息，所述第二指示信息指示禁止建立所述非无人机业务对应的会话。
在一种可能的实现方式中，所述第一控制面流程包括首次认证流程、去注册流程、切片认证流程或二次认证流程中的一项或多项。
在一种可能的实现方式中，在限制所述终端设备的第一控制面流程时，处理单元1401，用于暂停或终止所述第一控制面流程。
在一种可能的实现方式中，在所述第一设备暂停所述第一控制面流程之后，处理单元1401，进一步用于：启动第一计时器；确定在所述第一计时器的运行期间所述终端设备满足所述第一条件；以及，在所述第一计时器运行结束时终止所述第一控制面流程。
在一种可能的实现方式中，收发单元1402，进一步用于接收来自第三设备的第四消息，所述第四消息用于请求执行所述第一控制面流程；以及，向所述第三设备发送第五消息，所述第五消息包括不进行所述第一控制流程的原因。
在一种可能的实现方式中，在确定终端设备处于飞行状态时，收发单元1402，用于接收来自接入与移动性管理功能设备的第三指示信息，所述第三指示信息指示所述终端设备处于飞行状态。
可选地，收发单元1402，进一步用于向所述接入与移动性管理功能网元发送第六消息， 其中，所述第六消息用于获取所述终端设备的状态，所述终端设备的状态包括飞行状态或/和非飞行状态。
在一种可能的实现方式中，所述第一设备为接入与移动性管理功能设备；在确定终端设备处于飞行状态时，收发单元1402，用于接收来自第四设备的第四指示信息，所述第四指示信息用于指示所述终端设备处于飞行状态；或者，处理单元1401，用于根据所述终端设备的移动信息和/或所述终端设备的飞行信息，确定所述终端设备处于飞行状态。
在一种可能的实现方式中，所述第一设备为所述终端设备；在确定终端设备处于飞行状态时，处理单元1401，用于根据移动信息和/或来自应用层的第五指示信息确定处于飞行状态，其中，所述第五指示信息指示所述终端设备进入飞行模式。
在一种可能的实现方式中，处理单元1401，进一步用于确定满足第二条件，其中，所述第二条件包括如下条件中的一种或多种：所述终端设备被撤销所述无人机业务的授权，所述终端设备不被授权所述无人机业务，所述终端设备的所述无人机业务被去注册，或者所述终端设备释放最后一个所述无人机业务对应的会话；
所述第一设备是第一会话管理功能设备，收发单元1402，进一步用于接收来自所述终端设备的第七消息，以及处理单元1401，进一步用于根据所述第七消息建立或修改所述非无人机业务对应的会话，其中，所述第七消息用于请求建立或修改所述非无人机业务对应的会话；
或者，所述第一设备是短消息业务服务中心，收发单元1402，进一步用于向所述终端设备发送第八消息，所述第八消息用于请求建立或修改所述非无人机业务对应的会话；
或者，所述第一设备是所述终端设备，收发单元1402，进一步用于向第一会话管理功能设备发送第八消息，所述第八消息用于请求建立或修改所述非无人机业务对应的会话。
在一种可能的实现方式中，处理单元1401，进一步用于确定满足第二条件，其中，所述第二条件包括如下条件中的一种或多种：所述终端设备被撤销所述无人机业务的授权，所述终端设备不被授权所述无人机业务，所述终端设备的所述无人机业务被去注册，或者所述终端设备释放最后一个所述无人机业务对应的会话；收发单元1402，进一步用于接收来自第三设备的第四消息，所述第四消息用于请求执行所述第一控制面流程；处理单元1401，进一步用于执行所述第一控制面流程。
作为又一个示例，通信装置1400可实现上述各个方法实施例中由第二设备实现的功能或步骤。
其中，收发单元1402，用于接收来自第一会话管理功能设备的用于请求限制所述终端设备的非无人机业务的消息。
处理单元1401，用于根据所述消息，确定第二会话管理功能设备管理有所述终端设备的非无人机业务对应的会话。
收发单元1402，还用于向所述第二会话管理功能设备发送指示信息，其中，所述指示信息用于指示释放所述第二会话管理功能设备管理的全部或部分所述非无人机业务对应的会话，和/或指示禁止建立或禁止修改所述非无人机业务对应的会话。
在一种可能的实现方式中，收发单元1402，进一步用于向所述第一会话管理功能设备发送第一指示信息，所述第一指示信息用于指示释放一个或多个非无人机业务对应的会话。
在一种可能的实现方式中，收发单元1402，进一步用于接收来自所述第一会话管理功 能设备的N，其中，所述N是所述第一会话管理功能设备所管理的所述非无人机业务对应的会话的数量；处理单元1401，进一步用于根据所述终端设备已建立的所述非无人机业务对应的会话的数量，所述N和M，确定所述第一会话管理功能设备需要释放一个或多个所述非无人机业务对应的会话，其中，所述M是所述终端设备在执行所述无人机业务时允许在所述第一会话管理功能设备处建立的所述非无人机业务对应的会话的数量。
有关上述处理单元1401和收发单元1402更详细的描述可以直接参考图4至图13中任一项所示的方法实施例中相关描述直接得到，这里不加赘述。
如图15所示为本申请实施例提供的通信装置1500，其中，通信装置1500可以是第一设备，能够实现本申请实施例提供的方法中第一设备的功能，或者，通信装置1500可以是第二设备，能够实现本申请实施例提供的方法中第二设备的功能；或者，通信装置1500也可以是能够支持第一设备实现本申请实施例提供的方法中对应的功能的装置，或者能够支持第二设备实现本申请实施例提供的方法中对应的功能的装置。其中，该通信装置1500可以为芯片系统。本申请实施例中，芯片系统可以由芯片构成，也可以包含芯片和其他分立器件。
通信装置1500包括至少一个处理器1520，用于实现或用于支持通信装置1500实现本申请实施例提供的方法中第一设备或第二设备的功能。具体参见方法示例中的详细描述，此处不做赘述。
可选地，通信装置1500还可以包括至少一个存储器1530，用于存储程序指令和/或数据。存储器1530和处理器1520耦合。本申请实施例中的耦合是装置、单元或模块之间的间接耦合或通信连接，可以是电性，机械或其它的形式，用于装置、单元或模块之间的信息交互。处理器1520可能和存储器1530协同操作。处理器1520可能执行存储器1530中存储的程序指令和/或数据，以使得通信装置1500实现相应的方法。所述至少一个存储器中的至少一个可以包括于处理器中。该存储器1530可以是独立存在，例如片外存储器，通过通信总线(图15中以粗线1540表示)与处理器1520相连接。该存储器1530也可以和处理器1520集成在一起。
可选地，通信装置1500还可以包括通信接口1510，用于通过传输介质和其它设备进行通信，从而用于通信装置1500中的装置可以和其它设备进行通信。示例性的，当该通信装置为第一设备时，该其它设备为第二设备或第三设备等。处理器1520可以利用通信接口1510收发数据。通信接口1510具体可以是收发器。
在硬件实现上，上述收发单元1402可以为收发器，收发器集成在通信装置1500中构成通信接口1510。
本申请实施例中不限定上述通信接口1510、处理器1520以及存储器1530之间的具体连接介质。本申请实施例在图15中以存储器1530、处理器1520以及通信接口1510之间通过通信总线1540连接，其它部件之间的连接方式，仅是进行示意性说明，并不引以为限。所述通信总线1540可以分为地址总线、数据总线、控制总线等。为便于表示，图15中仅用一条粗线表示，但并不表示仅有一根通信总线或一种类型的通信总线。
在本申请实施例中，处理器1520可以是通用处理器、数字信号处理器、专用集成电路、现场可编程门阵列或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件，可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器 可以是微处理器或者任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。
在本申请实施例中，存储器1530可以是非易失性存储器，比如硬盘(hard disk drive，HDD)或固态硬盘(solid-state drive，SSD)等，还可以是易失性存储器(volatile memory)，例如随机存取存储器(random-access memory，RAM)。存储器是能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。本申请实施例中的存储器还可以是电路或者其它任意能够实现存储功能的装置，用于存储程序指令和/或数据。
本申请实施例还提供一种通信系统，具体的，通信系统包括第一设备，和/或第二设备。
本申请实施例中还提供一种计算机可读存储介质，包括指令，当其在计算机上运行时，使得计算机执行上述各个实施例中的方法。
本申请实施例中还提供一种计算机程序产品，包括指令，当其在计算机上运行时，使得计算机执行上述各个实施例中的方法。
本申请实施例提供了一种芯片系统，该芯片系统包括处理器，还可以包括存储器，用于实现前述方法中第一设备或第二设备的功能。该芯片系统可以由芯片构成，也可以包含芯片和其他分立器件。
应理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现 有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(read-only memory，ROM)、随机存取存储器(random access memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请实施例的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请实施例揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请实施例的保护范围之内。因此，本申请实施例的保护范围应所述以权利要求的保护范围为准。

Claims (51)

  1. 一种通信方法，其特征在于，所述方法包括：
    第一设备确定满足第一条件，所述第一条件包括如下条件中的一种或多种：终端设备被授权无人机业务，所述终端设备发起建立第一个所述无人机业务对应的会话，或者所述终端设备处于飞行状态；
    所述第一设备限制所述终端设备的非无人机业务和/或限制所述终端设备的第一控制面流程，其中，所述第一控制面流程不是所述无人机业务专有的流程。
  2. 根据权利要求1所述的方法，其特征在于，所述第一设备限制所述终端设备的非无人机业务，包括：
    所述第一设备是第一会话管理功能设备，所述第一设备释放所述第一设备管理的全部或部分的所述非无人机业务对应的会话，和/或禁止建立或禁止修改所述非无人机业务对应的会话；或者，
    所述第一设备是短消息业务服务中心，所述第一设备不向或暂停向所述终端设备发送第一消息，所述第一消息用于请求建立或修改所述非无人机业务对应的会话；或者，
    所述第一设备是所述终端设备，所述第一设备不向或暂停向第一会话管理功能设备发送第一消息，所述第一消息用于请求建立或修改所述非无人机业务对应的会话。
  3. 根据权利要求1或2所述的方法，其特征在于，若所述第一设备确定所述终端设备被授权所述无人机业务，和/或所述终端设备处于飞行状态；
    在所述第一设备限制所述终端设备的非无人机业务和/或限制所述第一控制面流程之前，所述方法还包括：
    所述第一设备接收来自所述终端设备的第二消息，所述第二消息用于请求建立第一会话；
    所述第一设备根据所述第二消息，确定所述第一会话属于所述无人机业务对应的会话。
  4. 根据权利要求1至3中所述的方法，其特征在于，所述方法还包括：
    所述第一设备向第二设备发送第三消息，所述第三消息用于请求限制所述终端设备的所述非无人机业务。
  5. 根据权利要求4所述的方法，其特征在于，所述方法还包括：
    所述第一设备接收来自所述第二设备的第一指示信息，所述第一指示信息用于指示释放一个或多个所述非无人机业务对应的会话；
    所述第一设备限制所述终端设备的非无人机业务，包括：
    所述第一设备根据所述第一指示信息释放一个或多个所述非无人机业务对应的会话。
  6. 根据权利要求1至4中任一项所述的方法，其特征在于，所述第一设备限制所述终端设备的非无人机业务包括所述第一设备释放所述第一设备管理的全部或部分的所述非无人机业务对应的会话，所述方法还包括：
    所述第一设备确定N大于M，其中，所述N是所述第一设备所管理的所述非无人机业务对应的会话的数量，所述M是所述终端设备在执行所述无人机业务时允许在所述第一设备处建立的所述非无人机业务对应的会话的数量；
    所述第一设备确定释放H个所述非无人机业务对应的会话，所述H为大于或等于(N-M)的正整数。
  7. 根据权利要求1至6中任一项所述的方法，其特征在于，所述第一设备限制所述终端设备的非无人机业务，包括：
    所述第一设备向所述终端设备发送第二指示信息，所述第二指示信息指示禁止建立所述非无人机业务对应的会话。
  8. 根据权利要求1至7中任一项所述的方法，其特征在于，所述第一控制面流程包括首次认证流程、去注册流程、切片认证流程或二次认证流程中的一项或多项。
  9. 根据权利要求8所述的方法，其特征在于，所述第一设备限制所述终端设备的第一控制面流程，包括：
    所述第一设备暂停或终止所述第一控制面流程。
  10. 根据权利要求9所述的方法，其特征在于，在所述第一设备暂停所述第一控制面流程之后，所述方法还包括：
    所述第一设备启动第一计时器；
    所述第一设备确定在所述第一计时器的运行期间所述终端设备满足所述第一条件；
    所述第一设备在所述第一计时器运行结束时终止所述第一控制面流程。
  11. 根据权利要求9或10所述的方法，其特征在于，所述方法还包括：
    所述第一设备接收来自第三设备的第四消息，所述第四消息用于请求执行所述第一控制面流程；
    所述第一设备向所述第三设备发送第五消息，所述第五消息包括不进行所述第一控制流程的原因。
  12. 根据权利要求1至11中任一项所述的方法，其特征在于，所述第一设备确定终端设备处于飞行状态，包括：
    所述第一设备接收来自接入与移动性管理功能设备的第三指示信息，所述第三指示信息指示所述终端设备处于飞行状态。
  13. 根据权利要求12所述的方法，其特征在于，所述方法还包括：
    所述第一设备向所述接入与移动性管理功能网元发送第六消息，其中，所述第六消息用于获取所述终端设备的状态，所述终端设备的状态包括飞行状态或/和非飞行状态。
  14. 根据权利要求1至11中任一项所述的方法，其特征在于，所述第一设备为接入与移动性管理功能设备；
    所述第一设备确定终端设备处于飞行状态，包括：
    所述第一设备接收来自第四设备的第四指示信息，所述第四指示信息用于指示所述终端设备处于飞行状态；或者，
    所述第一设备根据所述终端设备的移动信息和/或所述终端设备的飞行信息，确定所述终端设备处于飞行状态。
  15. 根据权利要求1至11中任一项所述的方法，其特征在于，所述第一设备为所述终端设备；
    所述第一设备确定终端设备处于飞行状态，包括：
    所述第一设备根据移动信息和/或来自应用层的第五指示信息确定处于飞行状态，其中，所述第五指示信息指示所述终端设备进入飞行模式。
  16. 根据权利要求1至15中任一项所述的方法，其特征在于，所述方法还包括：
    所述第一设备确定满足第二条件，其中，所述第二条件包括如下条件中的一种或多种： 所述终端设备被撤销所述无人机业务的授权，所述终端设备不被授权所述无人机业务，所述终端设备的所述无人机业务被去注册，或者所述终端设备释放最后一个所述无人机业务对应的会话；
    所述第一设备是第一会话管理功能设备，所述第一设备接收来自所述终端设备的第七消息，并根据所述第七消息建立或修改所述非无人机业务对应的会话，其中，所述第七消息用于请求建立或修改所述非无人机业务对应的会话；或者，
    所述第一设备是短消息业务服务中心，所述第一设备向所述终端设备发送第八消息，所述第八消息用于请求建立或修改所述非无人机业务对应的会话；或者，
    所述第一设备是所述终端设备，所述第一设备向第一会话管理功能设备发送第八消息，所述第八消息用于请求建立或修改所述非无人机业务对应的会话。
  17. 根据权利要求1至16中任一项所述的方法，其特征在于，所述方法还包括：
    所述第一设备确定满足第二条件，其中，所述第二条件包括如下条件中的一种或多种：所述终端设备被撤销所述无人机业务的授权，所述终端设备不被授权所述无人机业务，所述终端设备的所述无人机业务被去注册，或者所述终端设备释放最后一个所述无人机业务对应的会话；
    所述第一设备接收来自第三设备的第四消息，所述第四消息用于请求执行所述第一控制面流程；
    所述第一设备执行所述第一控制面流程。
  18. 一种通信方法，其特征在于，包括：
    第二设备接收来自第一设备的用于请求限制所述终端设备的非无人机业务的消息，所述第一设备为第一会话管理功能设备；
    所述第二设备根据所述消息，确定第二会话管理功能设备管理有所述终端设备的非无人机业务对应的会话；
    所述第二设备向所述第二会话管理功能设备发送指示信息，其中，所述指示信息用于指示释放所述第二会话管理功能设备管理的全部或部分所述非无人机业务对应的会话，和/或指示禁止建立或禁止修改所述非无人机业务对应的会话。
  19. 根据权利要求18所述的方法，其特征在于，所述方法还包括：
    所述第二设备向所述第一会话管理功能设备发送第一指示信息，所述第一指示信息用于指示释放一个或多个非无人机业务对应的会话。
  20. 根据权利要求19所述的方法，其特征在于，所述方法还包括：
    所述第二设备接收来自所述第一会话管理功能设备的N，其中，所述N是所述第一会话管理功能设备所管理的所述非无人机业务对应的会话的数量；
    所述第二设备根据所述终端设备已建立的所述非无人机业务对应的会话的数量，所述N和M，确定所述第一会话管理功能设备需要释放一个或多个所述非无人机业务对应的会话，其中，所述M是所述终端设备在执行所述无人机业务时允许在所述第一会话管理功能设备处建立的所述非无人机业务对应的会话的数量。
  21. 一种通信装置，其特征在于，包括处理单元和收发单元；
    其中，所述处理单元，用于确定满足第一条件，所述第一条件包括如下条件中的一种或多种：终端设备被授权无人机业务，所述终端设备发起建立第一个所述无人机业务对应的会话，或者所述终端设备处于飞行状态；以及，限制所述终端设备的非无人机业务和/ 或限制所述终端设备的第一控制面流程，其中，所述第一控制面流程不是所述无人机业务专有的流程；
    所述收发单元，用于执行所述通信装置的接收和发送。
  22. 根据权利要求21所述的装置，其特征在于，在限制所述终端设备的非无人机业务时：
    所述通信装置是第一会话管理功能设备，所述处理单元具体用于：释放所述通信装置管理的全部或部分的所述非无人机业务对应的会话，和/或禁止建立或禁止修改所述非无人机业务对应的会话；或者，
    所述通信装置是短消息业务服务中心，所述收发单元具体用于：不向或暂停向所述终端设备发送第一消息，所述第一消息用于请求建立或修改所述非无人机业务对应的会话；或者，
    所述通信装置是所述终端设备，所述收发单元具体用于：不向或暂停向第一会话管理功能设备发送第一消息，所述第一消息用于请求建立或修改所述非无人机业务对应的会话。
  23. 根据权利要求21或22所述的装置，其特征在于，若确定所述终端设备被授权所述无人机业务，和/或所述终端设备处于飞行状态；
    在限制所述终端设备的非无人机业务和/或限制所述第一控制面流程之前，所述收发单元还用于：接收来自所述终端设备的第二消息，所述第二消息用于请求建立第一会话；
    所述处理单元还用于：根据所述第二消息，确定所述第一会话属于所述无人机业务对应的会话。
  24. 根据权利要求21至23中所述的装置，其特征在于，所述收发单元还用于：
    向第二设备发送第三消息，所述第三消息用于请求限制所述终端设备的所述非无人机业务。
  25. 根据权利要求24所述的装置，其特征在于，所述收发单元还用于：
    接收来自所述第二设备的第一指示信息，所述第一指示信息用于指示释放一个或多个所述非无人机业务对应的会话；
    在限制所述终端设备的非无人机业务时，所述处理单元具体用于：
    根据所述第一指示信息释放一个或多个所述非无人机业务对应的会话。
  26. 根据权利要求21至24中任一项所述的装置，其特征在于，所述限制所述终端设备的非无人机业务包括释放所述通信装置管理的全部或部分的所述非无人机业务对应的会话，所述处理单元还用于：
    确定N大于M，其中，所述N是所述通信装置所管理的所述非无人机业务对应的会话的数量，所述M是所述终端设备在执行所述无人机业务时允许在所述通信装置处建立的所述非无人机业务对应的会话的数量；
    确定释放H个所述非无人机业务对应的会话，所述H为大于或等于(N-M)的正整数。
  27. 根据权利要求21至26中任一项所述的装置，其特征在于，在限制所述终端设备的非无人机业务时，所述收发单元用于：
    向所述终端设备发送第二指示信息，所述第二指示信息指示禁止建立所述非无人机业务对应的会话。
  28. 根据权利要求21至27中任一项所述的装置，其特征在于，所述第一控制面流程包括首次认证流程、去注册流程、切片认证流程或二次认证流程中的一项或多项。
  29. 根据权利要求28所述的装置，其特征在于，在限制所述终端设备的第一控制面流程时，所述处理单元具体用于：
    暂停或终止所述第一控制面流程。
  30. 根据权利要求29所述的装置，其特征在于，在暂停所述第一控制面流程之后，所述处理单元还用于：
    启动第一计时器；
    确定在所述第一计时器的运行期间所述终端设备满足所述第一条件；
    在所述第一计时器运行结束时终止所述第一控制面流程。
  31. 根据权利要求29或30所述的装置，其特征在于，所述收发单元还用于：
    接收来自第三设备的第四消息，所述第四消息用于请求执行所述第一控制面流程；
    向所述第三设备发送第五消息，所述第五消息包括不进行所述第一控制流程的原因。
  32. 根据权利要求21至31中任一项所述的装置，其特征在于，在确定终端设备处于飞行状态时，所述收发单还元用于：
    接收来自接入与移动性管理功能设备的第三指示信息，所述第三指示信息指示所述终端设备处于飞行状态。
  33. 根据权利要求32所述的装置，其特征在于，所述收发单元还用于：
    向所述接入与移动性管理功能网元发送第六消息，其中，所述第六消息用于获取所述终端设备的状态，所述终端设备的状态包括飞行状态或/和非飞行状态。
  34. 根据权利要求21至31中任一项所述的装置，其特征在于，所述通信装置为接入与移动性管理功能设备；
    在确定终端设备处于飞行状态时：
    所述收发单元用于接收来自第四设备的第四指示信息，所述第四指示信息用于指示所述终端设备处于飞行状态；或者，
    所述处理单元用于根据所述终端设备的移动信息和/或所述终端设备的飞行信息，确定所述终端设备处于飞行状态。
  35. 根据权利要求21至31中任一项所述的装置，其特征在于，所述通信装置为所述终端设备；
    在确定终端设备处于飞行状态时，所述处理单元具体用于：
    根据移动信息和/或来自应用层的第五指示信息确定处于飞行状态，其中，所述第五指示信息指示所述终端设备进入飞行模式。
  36. 根据权利要求21至35中任一项所述的装置，其特征在于，所述处理单元还用于：
    确定满足第二条件，其中，所述第二条件包括如下条件中的一种或多种：所述终端设备被撤销所述无人机业务的授权，所述终端设备不被授权所述无人机业务，所述终端设备的所述无人机业务被去注册，或者所述终端设备释放最后一个所述无人机业务对应的会话；
    所述通信装置是第一会话管理功能设备，所述收发单元还用于接收来自所述终端设备的第七消息，并根据所述第七消息建立或修改所述非无人机业务对应的会话，其中，所述第七消息用于请求建立或修改所述非无人机业务对应的会话；或者，
    所述通信装置是短消息业务服务中心，所述收发单元还用于向所述终端设备发送第八消息，所述第八消息用于请求建立或修改所述非无人机业务对应的会话；或者，
    所述通信装置是所述终端设备，所述收发单元还用于向第一会话管理功能设备发送第 八消息，所述第八消息用于请求建立或修改所述非无人机业务对应的会话。
  37. 根据权利要求21至36中任一项所述的装置，其特征在于，所述处理单元还用于：
    确定满足第二条件，其中，所述第二条件包括如下条件中的一种或多种：所述终端设备被撤销所述无人机业务的授权，所述终端设备不被授权所述无人机业务，所述终端设备的所述无人机业务被去注册，或者所述终端设备释放最后一个所述无人机业务对应的会话；
    所述收发单元还用于接收来自第三设备的第四消息，所述第四消息用于请求执行所述第一控制面流程；
    所述处理单元还用于执行所述第一控制面流程。
  38. 一种通信装置，其特征在于，包括处理单元和收发单元；
    其中，所述收发单元，用于接收来自第一会话管理功能设备的用于请求限制所述终端设备的非无人机业务的消息；
    所述处理单元，用于根据所述消息，确定第二会话管理功能设备管理有所述终端设备的非无人机业务对应的会话；
    所述收发单元，还用于向所述第二会话管理功能设备发送指示信息，其中，所述指示信息用于指示释放所述第二会话管理功能设备管理的全部或部分所述非无人机业务对应的会话，和/或指示禁止建立或禁止修改所述非无人机业务对应的会话。
  39. 根据权利要求38所述的装置，其特征在于，所述收发单元还用于：
    向所述第一会话管理功能设备发送第一指示信息，所述第一指示信息用于指示释放一个或多个非无人机业务对应的会话。
  40. 根据权利要求39所述的装置，其特征在于，所述收发单元还用于：
    接收来自所述第一会话管理功能设备的N，其中，所述N是所述第一会话管理功能设备所管理的所述非无人机业务对应的会话的数量；
    所述处理单元，还用于根据所述终端设备已建立的所述非无人机业务对应的会话的数量，所述N和M，确定所述第一会话管理功能设备需要释放一个或多个所述非无人机业务对应的会话，其中，所述M是所述终端设备在执行所述无人机业务时允许在所述第一会话管理功能设备处建立的所述非无人机业务对应的会话的数量。
  41. 一种通信装置，其特征在于，包括一个或多个处理器和存储器，所述一个或多个处理器与所述存储器耦合；
    所述存储器，用于存储计算机程序；
    所述一个或多个处理器，用于执行所述存储器中存储的计算机程序，以使得所述通信装置执行如权利要求1至17中任一项所述的方法，或执行如权利要求18至20中任一项所述的方法。
  42. 一种芯片，其特征在于，所述芯片与存储器耦合，用于读取并执行所述存储器中存储的程序指令，以执行如权利要求1至17中任一项所述的方法，或者执行如权利要求18至20中任一项所述的方法。
  43. 一种计算机可读存储介质，其特征在于，包括程序或指令，当所述程序或指令在计算机上运行时，执行如权利要求1至17中任一项所述的方法，或者执行如权利要求18至20中任一项所述的方法。
  44. 一种通信系统，其特征在于，包括用于执行如权利要求1至17中任一项所述方法的第一设备，和/或，包括用于执行如权利要求18至20中任一项所述方法的第二设备。
  45. 一种计算机程序产品，其特征在于，包括程序或指令，当所述程序或指令在计算机上运行时，如权利要求1至17中任一项所述的方法被执行，或者如权利要求18至20中任一项所述的方法被执行。
  46. 一种通信方法，其特征在于，所述方法包括：
    第一设备确定满足第一条件，限制终端设备的非无人机业务和/或限制终端设备的第一控制面流程，以及向第二设备发送第三消息，其中，所述第一控制面流程不是所述无人机业务专有的流程，所述第三消息用于请求限制所述终端设备的所述非无人机业务，所述第一条件包括如下条件中的一种或多种：所述终端设备被授权无人机业务，所述终端设备发起建立第一个所述无人机业务对应的会话，或者所述终端设备处于飞行状态；
    所述第二设备接收所述第三消息，向第二会话管理功能设备发送指示信息；其中，所述第二会话管理功能设备是根据所述第三消息确定的用于管理所述终端设备的非无人机业务对应的会话的设备。
  47. 根据权利要求46所述的方法，其特征在于，所述方法还包括：
    所述第二会话管理功能设备接收所述指示信息，根据所述指示信息释放所述第二会话管理功能设备管理的全部或部分所述非无人机业务对应的会话，和/或禁止建立或禁止修改所述非无人机业务对应的会话。
  48. 一种通信方法，其特征在于，所述方法包括：
    第二设备接收来自第一设备的第三消息，所述第三消息用于请求限制所述终端设备的所述非无人机业务；
    所述第二设备根据所述第三消息，确定第二会话管理功能设备管理有所述终端设备的非无人机业务对应的会话，以及向所述第二会话管理功能设备发送指示信息；
    所述第二会话管理功能设备接收所述指示信息，根据所述指示信息释放所述第二会话管理功能设备管理的全部或部分所述非无人机业务对应的会话，和/或禁止建立或禁止修改所述非无人机业务对应的会话。
  49. 一种通信系统，其特征在于，所述系统包括第一设备和第二设备，其中，
    所述第一设备用于：
    确定满足第一条件，限制终端设备的非无人机业务和/或限制终端设备的第一控制面流程，以及向第二设备发送第三消息，其中，所述第一控制面流程不是所述无人机业务专有的流程，所述第三消息用于请求限制所述终端设备的所述非无人机业务，所述第一条件包括如下条件中的一种或多种：所述终端设备被授权无人机业务，所述终端设备发起建立第一个所述无人机业务对应的会话，或者所述终端设备处于飞行状态；
    所述第二设备用于：
    接收所述第三消息，向第二会话管理功能设备发送指示信息；其中，所述第二会话管理功能设备是根据所述第三消息确定的用于管理所述终端设备的非无人机业务对应的会话的设备。
  50. 根据权利要求49所述的系统，其特征在于，所述系统还包括：
    所述第二会话管理功能设备，用于：接收所述指示信息，根据所述指示信息释放所述第二会话管理功能设备管理的全部或部分所述非无人机业务对应的会话，和/或禁止建立或禁止修改所述非无人机业务对应的会话。
  51. 一种通信系统，其特征在于，所述系统包括第二设备和第二会话管理功能设备，其 中，
    所述第二设备用于：
    接收来自第一设备的第三消息，所述第三消息用于请求限制所述终端设备的所述非无人机业务；
    根据所述第三消息，确定所述第二会话管理功能设备管理有所述终端设备的非无人机业务对应的会话，以及
    向所述第二会话管理功能设备发送指示信息；
    所述第二会话管理功能设备用于：
    接收所述指示信息；
    根据所述指示信息释放所述第二会话管理功能设备管理的全部或部分所述非无人机业务对应的会话，和/或禁止建立或禁止修改所述非无人机业务对应的会话。
PCT/CN2023/100183 2022-06-28 2023-06-14 一种通信方法及装置 WO2024001782A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP23829964.8A EP4539525A4 (en) 2022-06-28 2023-06-14 COMMUNICATION METHOD AND DEVICE

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210752034.0 2022-06-28
CN202210752034.0A CN117354804A (zh) 2022-06-28 2022-06-28 一种通信方法及装置

Publications (1)

Publication Number Publication Date
WO2024001782A1 true WO2024001782A1 (zh) 2024-01-04

Family

ID=89361929

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/100183 WO2024001782A1 (zh) 2022-06-28 2023-06-14 一种通信方法及装置

Country Status (3)

Country Link
EP (1) EP4539525A4 (zh)
CN (1) CN117354804A (zh)
WO (1) WO2024001782A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104281154A (zh) * 2014-10-17 2015-01-14 中国电子科技集团公司第二十七研究所 一种可控功耗的无人机飞行控制系统及方法
CN108614577A (zh) * 2018-05-30 2018-10-02 中国联合网络通信集团有限公司 无人机的信息传输方法与装置
KR20190131337A (ko) * 2018-05-16 2019-11-26 한양대학교 산학협력단 인지 무선 통신 기반의 중계 장치 및 이를 포함하는 무인 항공기와, 상기 무인 항공기를 이용한 인지 무선 통신 기반의 중계 방법
CN110673640A (zh) * 2019-10-21 2020-01-10 深圳市道通智能航空技术有限公司 一种无人机控制方法、装置、设备和存储介质
CN113676936A (zh) * 2020-05-15 2021-11-19 华为技术有限公司 一种异常行为无人机的处理方法、网元、系统及存储介质

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110602735B (zh) * 2018-06-13 2021-06-29 华为技术有限公司 一种受限服务的提供方法及通信设备
WO2021196185A1 (zh) * 2020-04-03 2021-10-07 Oppo广东移动通信有限公司 无线通信方法、终端设备和网络设备
EP4136777A1 (en) * 2020-04-17 2023-02-22 Telefonaktiebolaget LM ERICSSON (PUBL) A method of and an unmanned aerial vehicle for acting upon a restriction in services for the uav, a uav control server and a base station

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104281154A (zh) * 2014-10-17 2015-01-14 中国电子科技集团公司第二十七研究所 一种可控功耗的无人机飞行控制系统及方法
KR20190131337A (ko) * 2018-05-16 2019-11-26 한양대학교 산학협력단 인지 무선 통신 기반의 중계 장치 및 이를 포함하는 무인 항공기와, 상기 무인 항공기를 이용한 인지 무선 통신 기반의 중계 방법
CN108614577A (zh) * 2018-05-30 2018-10-02 中国联合网络通信集团有限公司 无人机的信息传输方法与装置
CN110673640A (zh) * 2019-10-21 2020-01-10 深圳市道通智能航空技术有限公司 一种无人机控制方法、装置、设备和存储介质
CN113676936A (zh) * 2020-05-15 2021-11-19 华为技术有限公司 一种异常行为无人机的处理方法、网元、系统及存储介质

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP4539525A4 *

Also Published As

Publication number Publication date
EP4539525A4 (en) 2025-05-07
CN117354804A (zh) 2024-01-05
EP4539525A1 (en) 2025-04-16

Similar Documents

Publication Publication Date Title
EP4305877B1 (en) Mobility in non-public networks
US20240073848A1 (en) Network Slice in a Wireless Network
EP4082291B1 (en) Uplink data indication
US20240015630A1 (en) Routing Between Networks Based on Identifiers
US20230328821A1 (en) Modifying PDU Sessions In Underlay Networks
US20230319685A1 (en) Access Restriction of Wireless Device
US20240298253A1 (en) Network Slice for Access of Wireless Device to a Network
US20230354463A1 (en) State Transition of Wireless Device
US20240129794A1 (en) Network Congestion Control
US20240022952A1 (en) Resource Allocation in Non-Public Network
US12335833B2 (en) Emergency service
US20240381081A1 (en) Alternative Slice Authentication
US20240129793A1 (en) Network Overload Control
US20250184279A1 (en) Data Unit Discard Report
US20240298229A1 (en) Change of Serving Node
WO2024001782A1 (zh) 一种通信方法及装置
EP4535846A1 (en) Communication method and apparatus
US20250220431A1 (en) Security Negotiation
WO2022206296A1 (zh) 一种会话控制的方法、装置和系统
WO2024060894A1 (zh) 一种通信方法及装置
WO2024102238A1 (en) Media data delivery
WO2024097090A1 (en) Media data reporting
WO2024254163A1 (en) Admission control of wireless device

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23829964

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2024575161

Country of ref document: JP

WWE Wipo information: entry into national phase

Ref document number: 202517000526

Country of ref document: IN

WWE Wipo information: entry into national phase

Ref document number: 2023829964

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2023829964

Country of ref document: EP

Effective date: 20250107

NENP Non-entry into the national phase

Ref country code: DE

WWP Wipo information: published in national office

Ref document number: 202517000526

Country of ref document: IN

WWP Wipo information: published in national office

Ref document number: 2023829964

Country of ref document: EP