WO2022193903A1 - 发现服务实体的方法和通信装置 - Google Patents

发现服务实体的方法和通信装置 Download PDF

Info

Publication number
WO2022193903A1
WO2022193903A1 PCT/CN2022/076788 CN2022076788W WO2022193903A1 WO 2022193903 A1 WO2022193903 A1 WO 2022193903A1 CN 2022076788 W CN2022076788 W CN 2022076788W WO 2022193903 A1 WO2022193903 A1 WO 2022193903A1
Authority
WO
WIPO (PCT)
Prior art keywords
network device
information
network
discovered
discover
Prior art date
Application number
PCT/CN2022/076788
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 华为技术有限公司
Publication of WO2022193903A1 publication Critical patent/WO2022193903A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/005—Discovery of network devices, e.g. terminals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/06—Authentication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management

Definitions

  • the present application relates to the field of communication, and more particularly, to a method and a communication device for discovering a service entity.
  • the drone In order to access the network, the drone needs to go through a series of authentication and authorization, and the premise of the authentication and authorization of the drone is that the 3rd generation partnership project (3GPP) system can successfully discover that the drone can be used for the drone.
  • 3GPP 3rd generation partnership project
  • a third-party entity for the service which usually does not belong to the 3GPP system to which the drone is connected.
  • the 3GPP system fails to successfully discover the third-party entity and thus cannot perform authentication and authorization.
  • the present application provides a method and a communication device for discovering a service entity, which reduces the problem that a legitimate terminal device cannot perform authentication and authorization because the core network fails to successfully discover a third-party entity serving the terminal device.
  • a method for discovering a service entity including: a first network device receiving first information, where the first information includes related information of a second network device, the second network device providing the terminal device with the pending information The discovered network device, and the second network device does not belong to the mobile network system where the first network device is located; the first network device performs discovery processing for the second network device according to the first information; When the discovery process of the network device fails, the first network device sends second information, the second information is used to request to re-provide the network device to be discovered; the first network device receives third information, the third information includes the fifth Relevant information of the network device, the fifth network device is the updated network device to be discovered provided by the terminal device, and the fifth network device does not belong to the mobile network system where the first network device is located; the first network device A discovery process for the fifth network device is performed according to the third information.
  • the mobile network system mentioned in this application can also be understood as a network system of a mobile network operator, such as PLMN, or can also be called a 3GPP system, and the name of the mobile network system is not limited in this application.
  • the second network device does not belong to the mobile network system where the terminal device is located. It can be understood that the second network device does not belong to any operator. In some scenarios, it can also be called a third-party entity. Referred to as a service entity, in a scenario where the terminal device is a networked drone, the second network device may be USS, UTM or USS/UTM, and this application does not limit the name of the second network device.
  • the first network device may send the second information to the access and mobility management function network element or the session management network element, or may send the second information to other network devices, which is not limited in this application .
  • the first network device may receive the updated first information from the access and mobility management function network element or the session management network element, or may receive the updated first information from other network devices information, or the updated first information may also be received from the terminal device, which is not limited in this application.
  • the network devices to be discovered in this application include but are not limited to third-party entities, second network devices, fifth network devices, USS/UTM, and the network devices to be discovered have “service terminal equipment” or “service UE” capabilities, and/or the ability to manage terminal equipment or manage the behavior of the UE.
  • the core network side device instructs the terminal device to update the network device to be discovered. This reduces the problem that legitimate terminal devices cannot perform authentication and authorization due to the failure of the core network to discover third-party entities.
  • the second information includes first indication information, where the first indication information requests to re-provide the network device to be discovered.
  • the second information includes at least one of second indication information and a first cause value, wherein the second indication information indicates that the first network device according to the The first information cannot discover the second network device, and the first reason value indicates the reason why the first network device cannot discover the second network device according to the first information.
  • a method for discovering a service entity comprising: a terminal device sending fourth information, where the fourth information includes related information of a second network device, the second network device providing the terminal device with the to-be-discovered network equipment, and the second network equipment does not belong to the mobile network system where the terminal equipment is located; the terminal equipment receives fifth information, and the fifth information is used to request the terminal equipment to re-provide the network equipment to be discovered; the terminal equipment sends Sixth information, the sixth information includes relevant information of a fifth network device, the fifth network device is an updated network device to be discovered, and the fifth network device does not belong to the mobile network system where the terminal device is located.
  • the terminal device in the authentication and authorization process, after the terminal device sends to the core network the relevant information of the second network device that serves the terminal device and is not in the same mobile network system as the terminal device, it receives a request sent by the core network to provide the After the indication of the relevant information of the network device to be discovered, the relevant information of the fifth network device is sent to the core network, and the terminal device updates the relevant information of the network device to be discovered to the core network in a timely manner after the authentication and authorization fails, thereby reducing the number of problems caused by the core network.
  • the network fails to discover the third-party entity, which leads to the problem that the legitimate terminal device cannot perform authentication and authorization.
  • the fourth information includes third indication information, where the third indication information requests to re-provide the network device to be discovered.
  • the fourth information includes at least one of fourth indication information and a second cause value, wherein the fourth indication information indicates that the first network device according to the The third information cannot discover the second network device, and the second reason value indicates the reason why the first network device cannot discover the second network device according to the third information.
  • a method for discovering a service entity comprising: a third network device receiving second information, where the second information is used to request to re-provide a network device to be discovered, where the network device to be discovered provides a terminal device the network device serving the terminal device, and the network device to be discovered does not belong to the mobile network system where the third network device is located; the third network device sends fifth information according to the second information, and the fifth information is used for Request to re-provide the to-be-discovered network device; the third network device receives sixth information, where the sixth information includes relevant information of the fifth network device, and the fifth network device is the updated to-be-discovered device provided by the terminal device and the fifth network device does not belong to the mobile network system where the third network device is located; the third network device sends third information, and the third information includes relevant information of the fifth network device
  • the core network side device instructs the terminal device to update the network device to be discovered. This reduces the problem that legitimate terminal devices cannot perform authentication and authorization due to the failure of the core network to discover third-party entities.
  • the second information includes first indication information, where the first indication information requests to re-provide the network device to be discovered.
  • the second information includes at least one of second indication information and a first cause value, wherein the second indication information indicates that the first network device according to the The first information cannot discover the second network device, and the first reason value indicates the reason why the first network device cannot discover the second network device according to the first information.
  • the fourth information includes third indication information, and the third indication information instructs the terminal device to update the third information.
  • the fourth information includes at least one of fourth indication information and a second cause value, wherein the fourth indication information indicates that the first network device cannot discover For the second network device, the second reason value indicates the reason why the first network device cannot discover the second network device according to the third information.
  • a method for discovering a service entity comprising: a first network device receiving seventh information from a terminal device, where the seventh information includes related information of a second network device, the second network device serving the The network device of the terminal device, and the second network device does not belong to the mobile network system where the first network device is located; the first network device cannot discover the second network device according to the seventh information; the first network device reports to the first network device
  • the fourth network device sends eighth information, the eighth information requests the relevant information of the second network device; the first network device receives ninth information from the fourth network device, the ninth information includes the information of the second network device Related Information.
  • the core network when the core network fails to discover the second network device serving the terminal device and not in the same mobile network system as the terminal device, the core network requests the fourth network device for a new second network related information of the device, thereby reducing the problem that the legitimate terminal device cannot perform authentication and authorization due to the failure of the core network to discover the second network device.
  • the eighth information includes at least one of fifth indication information and a third cause value, wherein the fifth indication information indicates that the first network device according to the The first information cannot discover the second network device, and the third reason value indicates the reason why the first network device cannot discover the second network device according to the first information.
  • the eighth information includes part or all of the information included in the seventh information.
  • a method for discovering a service entity comprising: a fourth network device receiving eighth information from the first network device, the eighth information requesting related information of a second network device, the second network device is a network device serving the terminal device, and the second network device does not belong to the mobile communication system where the first network device is located; the fourth network device queries the relevant information of the second network device for the first network device; the The fourth network device sends ninth information to the first network device, where the ninth information includes related information of the second network device.
  • the core network when the core network fails to discover the second network device serving the terminal device and not in the same mobile network system as the terminal device, the core network requests the fourth network device for a new second network related information of the device, thereby reducing the problem that the legitimate terminal device cannot perform authentication and authorization due to the failure of the core network to discover the second network device.
  • the eighth information includes at least one of fifth indication information and a third cause value, wherein the fifth indication information indicates that the first network device according to the The first information cannot discover the second network device, and the third reason value indicates the reason why the first network device cannot discover the second network device according to the first information.
  • the eighth information includes part or all of the seventh information.
  • a method for discovering a service entity comprising: a first network device receiving tenth information from a terminal device, the tenth information including a first list, and the first list including at least one second network device's information Relevant information, the relevant information of each second network device is used to discover a second network device, the second network device is a network device serving the terminal device, and the second network device does not belong to the first network device
  • the mobile network system where it is located the first network device cannot discover the second network device according to the relevant information of one of the second network devices in the tenth information; the first network device is based on the other information in the tenth information.
  • the relevant information of the second network device discovers the second network device.
  • the terminal device in the authentication and authorization process, is used to provide the first network device with a list of second network devices that serve the terminal device and are not in the same mobile network system as the terminal device, so that the first network device is based on the list.
  • the relevant information of one of the second network devices cannot discover the second network device
  • the second network device can be continuously discovered according to the relevant information of other second network devices in the list, thereby reducing the failure of the core network to discover the second network device. , which leads to the problem that legitimate terminal devices cannot perform authentication and authorization.
  • the tenth information further includes priority information of related information of the plurality of second network devices, and the first network device discovers the first network device in the order of priority. 2. Network equipment.
  • a method for discovering a service entity including: a terminal device sending tenth information, where the tenth information includes a first list, the first list including related information of at least one second network device, each of which The relevant information of the second network device is used to discover a second network device, the second network device is a network device serving the terminal device, and the second network device does not belong to the mobile network system accessed by the terminal device.
  • the terminal device in the authentication and authorization process, is used to provide the first network device with a list of second network devices that serve the terminal device and are not in the same mobile network system as the terminal device, so that the first network device is based on the list.
  • the relevant information of one of the second network devices cannot discover the second network device
  • the second network device can be continuously discovered according to the relevant information of other second network devices in the list, thereby reducing the failure of the core network to discover the second network device. , which leads to the problem that legitimate terminal devices cannot perform authentication and authorization.
  • the tenth information further includes priority information of related information of the plurality of second network devices, and the first network device discovers the first network device in the order of priority. 2. Network equipment.
  • an apparatus for discovering a service entity comprising: a transceiver module, configured to receive first information, where the first information includes relevant information of a second network device, the second network device provides information for the terminal device The network device to be discovered, and the second network device does not belong to the mobile network system where the first network device is located; the processing module is configured to perform discovery processing for the second network device according to the first information; When the discovery process of the second network device fails, the transceiver module is further configured to send second information, where the second information is used to request to re-provide the network device to be discovered; the transceiver module is further configured to receive third information, the The third information includes relevant information of the fifth network device, the fifth network device is the updated network device to be discovered provided by the terminal device, and the fifth network device does not belong to the mobile network system where the first network device is located; The processing module is further configured to perform discovery processing for the fifth network device according to the third information.
  • the core network side device instructs the terminal device to update the network device to be discovered. This reduces the problem that legitimate terminal devices cannot perform authentication and authorization due to the failure of the core network to discover third-party entities.
  • the second information includes first indication information, and the first indication information indicates to update the first information.
  • the second information includes at least one of second indication information and a first cause value, wherein the second indication information indicates that the first network device according to the The first information cannot discover the second network device, and the first reason value indicates the reason why the first network device cannot discover the second network device according to the first information.
  • an apparatus for discovering a service entity comprising: a transceiver module configured to send fourth information, where the fourth information includes relevant information of a second network device provided by the terminal device. The network device to be discovered, and the second network device does not belong to the mobile network system where the terminal device is located; the transceiver module is further configured to receive fifth information, and the fifth information is used to request the terminal device to re-provide the to-be-discovered network device network equipment; the transceiver module is further configured to send sixth information, where the sixth information includes relevant information of the fifth network equipment, the fifth network equipment is the updated network equipment to be discovered, and the fifth network equipment does not It belongs to the mobile network system where the terminal device is located.
  • the terminal device in the authentication and authorization process, after the terminal device sends to the core network the relevant information of the second network device that serves the terminal device and is not in the same mobile network system as the terminal device, it receives a request sent by the core network to provide the After the indication of the relevant information of the network device to be discovered, the relevant information of the fifth network device is sent to the core network, and the terminal device updates the relevant information of the network device to be discovered to the core network in a timely manner after the authentication and authorization fails, thereby reducing the number of problems caused by the core network.
  • the network fails to discover the third-party entity, which leads to the problem that the legitimate terminal device cannot perform authentication and authorization.
  • the apparatus further includes a processing module configured to determine the updated first information according to the fourth information.
  • the fourth information includes third indication information, and the third indication information instructs the terminal device to update the third information.
  • the fourth information includes at least one of fourth indication information and a second cause value, wherein the fourth indication information indicates that the first network device according to the The third information cannot discover the second network device, and the second reason value indicates the reason why the first network device cannot discover the second network device according to the third information.
  • an apparatus for discovering a service entity comprising: a transceiver module for receiving second information, where the second information is used to request to re-provide a network device to be discovered, where the network device to be discovered is a terminal device The provided network equipment serving the terminal equipment, and the network equipment to be discovered does not belong to the mobile network system where the third network equipment is located; the processing module is used for sending fifth information according to the second information, and the fifth information is used in response to requesting to re-provide the to-be-discovered network device; the transceiver module is further configured to receive sixth information, where the sixth information includes relevant information of the fifth network device, and the fifth network device is the updated information provided by the terminal device. the network device to be discovered, and the fifth network device does not belong to the mobile network system where the third network device is located; the transceiver module is also used for third information, and the third information includes relevant information of the fifth network device .
  • the core network side device instructs the terminal device to update the network device to be discovered. This reduces the problem that legitimate terminal devices cannot perform authentication and authorization due to the failure of the core network to discover third-party entities.
  • the second information includes first indication information, and the first indication information indicates to update the first information.
  • the second information includes at least one of second indication information and a first cause value, wherein the second indication information indicates that the first network device according to the The first information cannot discover the second network device, and the first reason value indicates the reason why the first network device cannot discover the second network device according to the first information.
  • the fourth information includes third indication information, and the third indication information instructs the terminal device to update the third information.
  • the fourth information includes at least one of fourth indication information and a second cause value, wherein the fourth indication information indicates that the first network device according to the The first information cannot discover the second network device, and the second reason value indicates the reason why the first network device cannot discover the second network device according to the first information.
  • an apparatus for discovering a service entity comprising: a transceiver module configured to receive seventh information from a terminal device, where the fifth information includes relevant information of a second network device, and the second network device is a network device serving the terminal device, and the second network device does not belong to the mobile network system where the first network device is located; the processing module is configured to be unable to discover the second network device according to the seventh information; the transceiver module further is used to send eighth information to the fourth network device, the eighth information requests relevant information of the second network device; the transceiver module is also used to receive ninth information from the fourth network device, the ninth information includes relevant information of the second network device.
  • the core network when the core network fails to discover the second network device serving the terminal device and not in the same mobile network system as the terminal device, the core network requests the fourth network device for a new second network related information of the device, thereby reducing the problem that the legitimate terminal device cannot perform authentication and authorization due to the failure of the core network to discover the second network device.
  • the eighth information includes at least one of fifth indication information and a third cause value, wherein the fifth indication information indicates the first network device The second network device cannot be discovered according to the first information, and the third reason value indicates the reason why the first network device cannot discover the second network device according to the first information.
  • the eighth information includes the seventh information.
  • a twelfth aspect provides an apparatus for discovering a service entity, comprising: a transceiver module for receiving eighth information from the first network device, where the eighth information requests related information of the second network device, the second The network device is a network device serving the terminal device, and the second network device does not belong to the mobile communication system where the first network device is located; a processing module is configured to query the relevant information of the second network device for the first network device ; The transceiver module is further configured to send ninth information to the first network device, where the ninth information includes relevant information of the second network device.
  • the core network when the core network fails to discover the second network device serving the terminal device and not in the same mobile network system as the terminal device, the core network requests the fourth network device for a new second network related information of the device, thereby reducing the problem that the legitimate terminal device cannot perform authentication and authorization due to the failure of the core network to discover the second network device.
  • the eighth information includes at least one of fifth indication information and a third cause value, wherein the fifth indication information indicates that the first network device according to The first information cannot discover the second network device, and the third reason value indicates the reason why the first network device cannot discover the second network device according to the first information.
  • the eighth information includes the seventh information.
  • a thirteenth aspect provides an apparatus for discovering a service entity, comprising: a transceiver module for receiving tenth information from a terminal device, where the tenth information includes a first list, and the first list includes at least one second network Relevant information of the device, the relevant information of each second network device is used to discover one of the second network devices, the second network device is a network device serving the terminal device, and the second network device does not belong to the first network device.
  • the mobile network system where the network device is located; the processing module is configured to fail to discover the second network device according to the related information of the second network device in the tenth information; the processing module is further configured to and other related information of the second network device to discover the second network device.
  • the terminal device in the authentication and authorization process, is used to provide the first network device with a list of second network devices that serve the terminal device and are not in the same mobile network system as the terminal device, so that the first network device is based on the list.
  • the relevant information of one of the second network devices cannot discover the second network device
  • the second network device can be continuously discovered according to the relevant information of other second network devices in the list, thereby reducing the failure of the core network to discover the second network device. , which leads to the problem that legitimate terminal devices cannot perform authentication and authorization.
  • the tenth information further includes priority information of related information of the plurality of second network devices, and the first network device discovers in the order of priority the second network device.
  • a fourteenth aspect provides an apparatus for discovering a service entity, comprising: a transceiver module configured to send tenth information, where the tenth information includes a first list, and the first list includes related information of at least one second network device , the relevant information of each second network device is used to discover one second network device, the second network device is a network device serving the terminal device, and the second network device does not belong to the mobile device accessed by the terminal device. network system.
  • the terminal device in the authentication and authorization process, is used to provide the first network device with a list of second network devices that serve the terminal device and are not in the same mobile network system as the terminal device, so that the first network device is based on the list.
  • the relevant information of one of the second network devices cannot discover the second network device
  • the second network device can be continuously discovered according to the relevant information of other second network devices in the list, thereby reducing the failure of the core network to discover the second network device. , which leads to the problem that legitimate terminal devices cannot perform authentication and authorization.
  • the tenth information further includes priority information of related information of the plurality of second network devices, and the first network device discovers in the order of priority the second network device.
  • a fifteenth aspect provides a communication device, comprising: a processor and a memory; the memory for storing a computer program; the processor for executing the computer program stored in the memory, so that the communication device executes the first The methods and embodiments of any one of the one to seventh aspects.
  • a sixteenth aspect provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program runs on a computer, the computer causes the computer to execute any of the first to seventh aspects.
  • a seventeenth aspect provides a chip system, comprising: a processor for calling and running a computer program from a memory, so that a communication device installed with the chip system executes any one of the first to seventh aspects described methods and examples.
  • An eighteenth aspect provides a communication system, the communication system includes a first network device and a terminal device, wherein the first network device is configured to perform the method and implementation of any one of the first aspect and the second aspect example.
  • a nineteenth aspect provides a communication system, where the communication system includes a first network device, a terminal device, and a third network device, wherein the first network device is configured to perform any one of the first to third aspects. methods and examples described.
  • FIG. 1 shows a network architecture suitable for this embodiment of the present application.
  • FIG. 2 shows another network architecture suitable for this embodiment of the present application.
  • FIG. 3 shows a schematic diagram of an example of an application scenario to which the embodiments of the present application are applied.
  • FIG. 4 shows a schematic interaction diagram of an example of the method for discovering a service entity of the present application.
  • FIG. 5 shows a schematic interaction diagram of yet another example of the method for discovering a service entity of the present application.
  • FIG. 6 shows a schematic interaction diagram of still another example of the method for discovering a service entity of the present application.
  • FIG. 7 shows a schematic interaction diagram of yet another example of the method for discovering a service entity of the present application.
  • FIG. 8 shows a schematic interaction diagram of still another example of the method for discovering a service entity of the present application.
  • FIG. 9 shows a schematic interaction diagram of still another example of the method for discovering a service entity of the present application.
  • FIG. 10 shows a schematic interaction diagram of yet another example of the method for discovering a service entity of the present application.
  • FIG. 11 shows a schematic block diagram of an example of a communication device for authentication and authorization of the present application.
  • FIG. 12 shows a schematic block diagram of yet another example of the communication device for authentication and authorization of the present application.
  • GSM global system for mobile communications
  • CDMA code division multiple access
  • CDMA wideband code division multiple access
  • WCDMA wideband code division multiple access
  • general packet radio service general packet radio service, GPRS
  • long term evolution long term evolution
  • LTE long term evolution
  • LTE frequency division duplex frequency division duplex
  • TDD time division duplex
  • UMTS universal mobile telecommunication system
  • WiMAX worldwide interoperability for microwave access
  • 5G 5th generation
  • NR new radio
  • V2V Vehicle-to-vehicle
  • V2I vehicle-to-infrastructure
  • V2P Vehicle to pedestrian
  • V2N vehicle to network communication
  • FIG. 1 provides a network architecture, and each network element that may be involved in the network architecture will be described below with reference to FIG. 1 .
  • User equipment can be called terminal equipment, terminal, access terminal, subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile equipment, user terminal, wireless communication equipment, User Agent or User Device.
  • the UE may also be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a wireless communication capability handheld devices, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, terminal devices in 5G networks or future evolution of public land mobile networks (PLMN) or non-terrestrial
  • the terminal equipment of the network can also be terminal equipment, logical entities, intelligent equipment, such as mobile phones, intelligent terminals and other terminal equipment, or communication equipment such as servers, gateways, base stations, controllers, or objects.
  • Internet-connected devices such as sensors, electricity meters, water meters and other Internet of Things (IoT) devices. It can also be an unmanned aerial vehicle (unmanned aerial vehicle or uncrewed aerial vehicle, UAV) with communication capabilities. This embodiment of the present application does not limit this.
  • Universal mobile telecommunications system (UMTS) terrestrial radio access network such as the third generation (3rd generation, 3G)/second generation (2nd generation, 2G) connection access the network.
  • GSM Global system for mobile communication
  • EDGE enhanced data rate for GSM evolution
  • GERAN Global system for mobile communication
  • 3G /2G access network 3G /2G access network.
  • Evolved universal terrestrial radio access network such as the fourth generation (4th generation, 4G) access network.
  • S-GW Serving gateway
  • PDN gateway Public data network gateway (PDN gateway, P-GW) entity: the user plane data link anchor between 3GPP and non-3GPP networks, which can be responsible for managing data routing between 3GPP and non-3GPP networks.
  • Mobility Management Entity It is mainly responsible for functions such as mobility management, bearer management, user authentication and authentication, and selection of S-GW and P-GW.
  • Operator's IP services can be an IP multimedia subsystem (IP multimedia subsystem, IMS), and IMS is a general network architecture that provides multimedia services based on IP networks; It can be a packet switching service (packet switching service, PSS) and so on.
  • IP multimedia subsystem IP multimedia subsystem
  • IMS IP multimedia subsystem
  • PSS packet switching service
  • PCRF Policy and charging rules function
  • HSS Home subscriber server
  • the HSS can include user profiles, perform user authentication and authorization, and provide information about Information about the user's physical location.
  • Serving general packet radio service (GPRS) support node can complete routing and forwarding of packet data packets, mobility management, session management, logical link management, authentication and encryption, CDR generation and output functions.
  • GPRS general packet radio service
  • the LTE-Uu interface is the reference point between the terminal and the E-UTRAN;
  • the S1-U interface is the reference point between the E-UTRAN and the S-GW entity;
  • the N5 interface is the S-GW entity and the P-GW entity.
  • Control plane interface S1-MME connects MME with E-UTRAN, similar to the control part of the wireless network layer in UMTS network, etc.;
  • S11 interface is the reference point between MME and S-GW entity;
  • S12 interface is UTRAN/GERAN The reference point with the S-GW entity;
  • the S4 interface is the reference point between the SGSN and the S-GW entity;
  • the S6a interface is the reference point between the MME and the HSS;
  • the S3 interface is the reference point between the MME and the SGSN.
  • FIG. 2 provides another network architecture, and each network element that may be involved in the network architecture will be described below with reference to FIG. 2 .
  • UE It has been introduced above with reference to FIG. 1 , and it is not repeated here for brevity.
  • Access network It provides network access functions for authorized users in a specific area, and can use different quality transmission tunnels according to user levels and business needs.
  • the access network may be an access network using different access technologies.
  • 3GPP access technologies such as those employed in 3G, 4G or 5G systems
  • non-3GPP non-3rd Generation Partnership Project
  • 3GPP access technology refers to an access technology that conforms to 3GPP standard specifications.
  • An access network using 3GPP access technology is called a radio access network (RAN).
  • RAN radio access network
  • RAN radio access network
  • RAN radio access network
  • a non-3GPP access technology refers to an access technology that does not conform to 3GPP standard specifications, for example, an air interface technology represented by an access point (AP) in wifi.
  • AP access point
  • An access network that implements access network functions based on wireless communication technology can be called a radio access network (RAN).
  • the radio access network can manage radio resources, provide access services for terminals, and then complete the forwarding of control signals and user data between the terminal and the core network.
  • the radio access network can be, for example, a base station (NodeB), an evolved NodeB (evolved NodeB, eNB or eNodeB), a base station (gNB) in a 5G mobile communication system, a base station in a future mobile communication system, or an AP in a WiFi system, etc., It can also be a wireless controller in a cloud radio access network (CRAN) scenario, or the access network device can be a relay station, an access point, an in-vehicle device, a wearable device, and a network in the future 5G network equipment or network equipment in a future evolved PLMN network, etc.
  • CRAN cloud radio access network
  • the embodiments of the present application do not limit the specific technology and specific device form adopted by the wireless access network device.
  • Access and mobility management function (AMF) entity mainly used for mobility management and access management, etc., and can be used to implement mobility management entity (mobility management entity, MME) functions in addition to sessions Other functions other than management, such as lawful interception, or access authorization (or authentication) functions.
  • MME mobility management entity
  • Session management function (SMF) entity mainly used for session management, UE IP address allocation and management, selection of manageable user plane functions, policy control, or termination point of charging function interface and downlink data notification, etc. .
  • User plane function (UPF) entity that is, a data plane gateway. It can be used for packet routing and forwarding, or quality of service (QoS) processing of user plane data. User data can be accessed to a data network (DN) through this network element. In this embodiment of the present application, it can be used to implement the function of the user plane gateway.
  • DN data network
  • Data Network A network for providing data transmission.
  • DN A network for providing data transmission.
  • an operator's service network an Internet (Internet) network, a third-party service network, and the like.
  • AUSF Authentication server function
  • Network exposure function (NEF) entity used to securely open services and capabilities provided by the 3GPP network function to the outside.
  • NRF entity used to store the network function entity and the description information of the services it provides, as well as support service discovery, network element entity discovery, etc.
  • PCF Policy control function
  • Unified data management (UDM) entity used to handle user identification, access authentication, registration, or mobility management, etc.
  • Application function (AF) entity used to perform data routing affected by applications, access network open function network elements, or interact with the policy framework to perform policy control, etc.
  • AF application function
  • it may be a V2X application server, a V2X application enabling server, or a drone server (which may include a drone monitoring server, or a drone application service server).
  • the N1 interface is the reference point between the terminal and the AMF entity; the N2 interface is the reference point between the AN and the AMF entity, and is used for non-access stratum (NAS) messages.
  • Sending, etc. N3 interface is the reference point between (R)AN and UPF entity, used to transmit user plane data, etc.
  • N4 interface is the reference point between SMF entity and UPF entity, used to transmit tunnels such as N3 connections Identification information, data buffer indication information, and downlink data notification messages and other information;
  • the N6 interface is the reference point between the UPF entity and the DN, and is used to transmit data on the user plane.
  • FIG. 1 and FIG. 2 can be applied to the embodiments of the present application.
  • the network architecture applicable to the embodiments of the present application is not limited to this, and any network architecture that can implement the functions of the above network elements All are applicable to the embodiments of the present application.
  • the AMF entity, the SMF entity, the UPF entity, the NEF entity, the AUSF entity, the NRF entity, the PCF entity, and the UDM entity shown in FIG. 1 or FIG. 2 can be understood as network elements in the core network for implementing different functions. , for example, can be combined into network slices on demand. These core network elements may be independent devices, or may be integrated into the same device to implement different functions, which is not limited in this application. It should be noted that the above-mentioned "network element" may also be referred to as an entity, a device, an apparatus, or a module, etc., which is not particularly limited in this application.
  • FIG. 3 shows a schematic diagram of an application scenario of an embodiment of the present application.
  • the UAS 300 can perform information exchange and wireless communication with the network system with the UTM traffic management entity UTM303.
  • the UAV controller 301 or the UAV 302 can exchange information with an access network (radio access network, RAN) 304 and a core network (core network, CN) 305, and can also exchange information through the access network 304 or the core network 305 conducts information interaction with UTM303;
  • UAV controller 301 can also conduct information exchange with UAV 302 through access network 304 or core network 305, and can also conduct information interaction with UAV 302 through UTM303.
  • the UAV controller 301 and the UAV 302 may be in the same access network or core network, or may be in different access networks or core networks, which is not limited in this embodiment of the present application.
  • Unmanned aerial vehicle controller (UAVC) 301 used to control the drone 302, such as controlling the flight state or flight action of the drone.
  • the drone controller can be a smartphone, tablet, laptop, smart watch or smart remote control, traditional remote control, dedicated remote control, etc. It can also be a bracelet, ring, gloves, armband, watch, etc. Can be used for gestures
  • the device for controlling the drone can also be a headgear such as a headgear that can be used to control the drone with a mind, or a device such as a smart jacket or jacket that can be used to control the drone by the user's body movements.
  • the present application does not limit the specific type of the UAV controller.
  • the name and form of the device with the function of the drone controller may be different.
  • the above-mentioned devices capable of having the function of a drone controller or capable of controlling the drone are collectively referred to as a drone controller.
  • the drone controller 301 can control the flight state of the drone 302.
  • the drone controller can control the direction, aileron, lift, tilt, speed, throttle, flaps, etc. of the drone, and can also control Actions such as turning, climbing, diving, rolling, hovering, taking off, and landing of the UAV are not limited in this embodiment of the present application.
  • Unmanned aerial vehicle (UAV) 302 Or, it can also be (uncrewed aerial vehicle, UAV), also known as unmanned aerial vehicle, aerial robot, which is controlled by radio remote control equipment and self-provided program
  • UAV uncrewed aerial vehicle
  • the unmanned aircraft of the device can complete aerial flight tasks and various load tasks under unmanned conditions.
  • the UAVs in the embodiments of the present application may be unmanned helicopters, fixed-wing aircraft, multi-rotor aircraft, unmanned airships, and unmanned paragliders; and may also include near-space vehicles, such as stratospheric airships, high-altitude balloons, solar-powered drones Human-machine, etc.; it can also be four-axis, six-axis, single-axis, vector control and other forms of drones.
  • the drones in the embodiments of the present application can be used in the fields of military, industry, civil use, agriculture, construction, film and television, environmental protection, etc., as well as special industries that use drones for operations, such as using drones for military reconnaissance, patrol, Aerial photography, environmental monitoring, border monitoring, express delivery, power inspection, confirmation of rights, flood control and drought relief, post-disaster rescue, etc.
  • the embodiments of the present application do not limit the name and form of the drone.
  • unmanned aerial vehicles the specific type of the drone is not limited herein.
  • the names of devices with unmanned aircraft functions may be different in order to be applied to different scenarios or to complete different aerial missions.
  • unmanned aerial vehicles the above-mentioned devices capable of unmanned aircraft functions are collectively referred to as unmanned aerial vehicles.
  • the UAV 302 may be equipped with various sensors or functional modules, such as gyroscopes (flight attitude perception), accelerometers, geomagnetic induction, barometric pressure sensors (rough control of hovering height), ultrasonic sensors (precise control of low altitudes or obstacle avoidance) , optical flow sensor (hovering horizontal position is accurately determined), global positioning system (global positioning system, GPS) module (horizontal position height rough positioning), control circuit, compass, etc., by collecting the angular rate, attitude, position of the UAV , acceleration, altitude and airspeed, etc., can automatically maintain the normal flight attitude of the drone.
  • sensors or functional modules such as gyroscopes (flight attitude perception), accelerometers, geomagnetic induction, barometric pressure sensors (rough control of hovering height), ultrasonic sensors (precise control of low altitudes or obstacle avoidance) , optical flow sensor (hovering horizontal position is accurately determined), global positioning system (global positioning system, GPS) module (horizontal position
  • each functional module may also have other names, which are not limited in the embodiments of the present application.
  • the unmanned aerial vehicle in the embodiment of the present application may also have more or less functional modules, and may also implement more or less functions, etc., and the embodiment of the present application does not limit this in any way.
  • an unmanned aerial system (UAS) 300 may include one or more drone controllers 301 and one or more drones 302 .
  • a drone controller can control one or more drones, a drone can also be controlled by one or more drone controllers, and multiple drone controllers can cooperate to control multiple drones.
  • Human-machine which is not limited in this embodiment of the present application.
  • the drone 302 in the drone system 300 can be any one or more types mentioned above, and the drone controller 301 can also be any one or more types mentioned above.
  • the embodiment does not make any limitation on this.
  • this application also includes:
  • UAS service provider An entity that supports the safe and efficient use of airspace by providing services to the operator or pilot of the drone to meet the operational requirements of the drone. USS can provide any subset of functionality to meet the provider's business objectives. It should be noted that this name is only for convenience to express its function, and should not constitute any limitation to this application, and this application does not exclude the possibility of adopting other names in subsequent standards.
  • Unmanned aerial system traffic management A set of functions and services for managing a range of automated device operations (e.g., drone certification, drone business authorization, drone policy management, unmanned airspace machine flow control). It should be noted that this name is only for convenience to express its function, and should not constitute any limitation to this application, and this application does not exclude the possibility of adopting other names in subsequent standards.
  • the entities of the USS and the UTM may be one entity, may be in an inclusive relationship, or may be in a parallel relationship, which is not limited in this application.
  • USS, UTM, and USS/UTM refer to the same entity, and its name may be a service entity or the like.
  • TPAE Third-party authorized entity
  • UAS application function network element UAS application function, UAS AF
  • UAV flight enablement subsystem UAV flight enablement subsystem
  • UFES UAS application function network element
  • UAS AF or UFES provides a separate interface for USS or UTM to access 3GPP system services, executes commands issued by USS or UTM, and is responsible for information transmission inside and outside the 3GPP system. It should be noted that this name is only for convenience to express its function, and should not constitute any limitation to this application, and this application does not exclude the possibility of adopting other names in subsequent standards.
  • UAS AF or UFES may be an existing network element, such as NEF/SCEF, or a new network element, or may be deployed together with NEF or service capability exposure function (SCEF).
  • SCEF service capability exposure function
  • the entities of UAS AF and UFES may be one entity, may be in an inclusive relationship, or may be in a parallel relationship, which is not limited in this application.
  • drones In recent years, the application of drones has gradually become popular. Especially in the civilian field, from small drones for personal entertainment to a variety of drones that bring economic value, such as plant protection drones, disaster relief drones, firefighting drones, express delivery Drones and more. However, while drones bring various economic benefits and entertainment to people, they also bring about the problem of how to manage drones.
  • UAVs suitable for remote control scenarios have more and more demands for networking.
  • 3GPP system in order to better manage UAVs, the application of 3GPP system in the entire UAV field is also getting more and more attention.
  • 5G system Take the 5G system as an example.
  • 3GPP is studying connected drones, and the system improves the management of drones through the network.
  • the UAV and the UAV controller are respectively connected to the 3GPP network, and the two communicate through the 3GPP network. Specifically, after the drone is connected to the Internet, UAS services can be obtained.
  • the drone controller can remotely control the flight of the drone through the network, the drone can send data information to the cloud through the network, and the drone can also Get timely obstacle avoidance assistance and more through the network.
  • the drone in order to control the flight of the drone through networking, the drone will request to establish a session to connect with its controller, which is called a command and control (command and control, C2) communication-related session.
  • UAV networking requires authentication and authorization of the UAV itself. If a session related to C2 communication needs to be established, C2 communication authentication and authorization are also required. These authentication authorizations need to be carried out in a third-party entity, namely USS or UTM. Currently, UAV authentication and authorization can be performed in the registration process, or in the process of establishing/modifying a protocol data unit (PDU) session.
  • PDU protocol data unit
  • the UAV certification authorization in this application includes the certification authorization related to UAV, such as whether the UAV itself is legal (UAV certification authorization), whether the UAV flight plan is legal (the flight path certification authorization), whether the UAV can It communicates with a specific UAVC (paired authentication authorization), etc., or may also include other UAV-related authentication authorizations, which are not limited in this application.
  • the 3GPP system In order to send the authorization and authentication request of the drone to the USS/UTM, the 3GPP system needs to perform the discovery of the USS/UTM. At present, there is no corresponding solution for the scenario in which the 3GPP system fails to successfully discover the USS/UTM and thus cannot perform authentication and authorization. Therefore, the present application wishes to provide a solution to the above-mentioned problems.
  • FIG. 4 is a schematic interaction diagram of the method 400 of the present application.
  • a terminal device sends fourth information to a third network device, where the fourth information includes relevant information of a second network device, the second network device is a network device to be discovered provided by the terminal device, and the second network device Does not belong to the mobile network system where the terminal device is located.
  • the terminal device sending the fourth information to the third network device can also be understood as that the terminal device sends the fourth information to the third network device through other network devices. It should be noted that the information sent by the terminal device to other network devices may or may not be of the same type as the information sent by other network devices to the third network device, but all the above information includes the fourth information.
  • the mobile network system here may also be understood as a network system of a mobile network operator, such as a PLMN, or may also be called a 3GPP system, and this application does not limit the name of the mobile network system.
  • the second network device here does not belong to the mobile network system where the terminal device is located, and it can also be understood that the second network device does not belong to any operator. It should be noted that, in some scenarios, the second network device may be referred to as a third-party entity, and may also be referred to as a service entity.
  • the device may be USS, UTM or USS/UTM, and this application does not limit the name of the second network device.
  • the third network device here may be SMF or AMF.
  • the third network device sends first information to the first network device, where the first information includes related information of the second network device, the second network device is the network device to be discovered provided by the terminal device, and the second network device The network device does not belong to the mobile network system where the first network device is located.
  • the third network device sends the first information to the first network device, which can also be understood as the third network device sending the first information to the first network device through other devices. It should be noted that the information discovered by the third network device to other devices may be of a different type or the same information type as the information sent by other network devices to the first network device, which is not limited in this application.
  • S401 and S402 are to send the relevant information of the second network device from the terminal device to the first network device.
  • the terminal device may directly send the relevant information to the first network device.
  • a network device or it may also be sent by the terminal device to the first network device through the third network device and other network devices, which is not limited in this application.
  • the third information and the first information may be the same information, which is not limited in this application.
  • the first network device performs discovery processing for the second network device according to the first information.
  • the “discovery” mentioned in this application refers to determining the second network device serving the terminal device according to the relevant information of the second network device.
  • the relevant information of the second network device may be an identifier assigned to it by the second network device, and the address of the second network device may be obtained by parsing the identifier, thereby determining the second network device.
  • it may also be called “determination” or “analysis”, etc., which is not limited in this application.
  • the first network device sends second information, where the second information is used to request to re-provide the network device to be discovered.
  • the discovery process of the second network device failed may also be understood as failure to successfully discover the second network device, or failure to discover the second network device. There may be various reasons for "the discovery process of the second network device fails", for details, please refer to step S703 in the method 700 .
  • the third network device sends fifth information to the terminal device, where the fifth information is used to request to re-provide the network device to be discovered.
  • S404 and S405 are to send the information from the first network device instructing the terminal device to update the network device to be discovered to the terminal device.
  • the information is sent to the terminal device, or may also be sent to the terminal device by the first network device through the third network device and/or other network devices, which is not limited in this application.
  • the second information and the fifth information may be the same information, which is not limited in this application.
  • the terminal device sends sixth information to the third network device, where the sixth information includes relevant information of the fifth network device, the fifth network device is the updated network device to be discovered provided by the terminal device, and the The fifth network device does not belong to the mobile network system where the third network device is located.
  • the third network device sends third information to the first network device, where the third information includes relevant information of the fifth network device.
  • the third network device sends the third information to the first network device according to the foregoing sixth information.
  • S406 and S407 are to send the relevant information of the fifth network device from the terminal device to the first network device.
  • the terminal device directly sends the relevant information of the fifth network device
  • the information is sent to the first network device, or may also be sent by the terminal device to the first network device through a third network device and/or other network devices, which is not limited in this application.
  • the core network side device instructs the terminal device to update the network to be discovered.
  • Device-related information thereby reducing the problem that legitimate terminal devices cannot perform authentication and authorization due to the failure of the core network to discover third-party entities.
  • FIG. 5 is a schematic interaction diagram of the method 500 of the present application.
  • a terminal device sends fifth information to a first network device, where the fifth information includes relevant information of a second network device, the second network device is a network device serving the terminal device, and the second network device does not belong to the The mobile network system where the first network device is located.
  • the first network device cannot discover the second network device according to the seventh information.
  • the second network device cannot be discovered may also be understood as failing to discover the second network device successfully, or failing to discover the second network device. There may be various reasons for "the second network device cannot be found", for details, please refer to step S703 in the method 700 .
  • the first network device sends eighth information to the fourth network device, where the eighth information requests relevant information of the second network device.
  • the first network device cannot discover the second network device according to the related information of the second network device provided by the terminal device, and therefore requests the fourth network device for other related information of the second network device.
  • the fourth network device queries the related information of the second network device.
  • the function possessed by the fourth network device may only be capable of querying relevant information of the second network device, or the function possessed by the fourth network device may also include the function of the second network device.
  • the fourth network device has different functions, refer to the description of the "fourth network device" in the method 900 .
  • the fourth network device sends ninth information to the first network device, where the ninth information includes relevant information of the second network device.
  • the fourth network device inquires about the relevant information of the second network device, it sends the relevant information to the first network device.
  • the relevant information of the second network device For the specific implementation, refer to possible situation 1 of S905 in the method 900; if the fourth network device does not inquire about the relevant information
  • the relevant information of the second network device for a specific processing method, refer to the second possible situation of S905 in the method 900 .
  • the core network in the authentication and authorization process, when the core network fails to discover a second network device serving the terminal device and not in the same mobile network system as the terminal device, the core network requests a new second network device from the fourth network device through the core network. related information of the network device, thereby reducing the problem that the legitimate terminal device cannot perform authentication and authorization due to the failure of the core network to discover the second network device.
  • FIG. 6 is a schematic interaction diagram of the method 600 of the present application.
  • a terminal device sends eighth information to a first network device, where the eighth information includes a first list, where the first list includes relevant information of at least one second network device, and the relevant information of each second network device is used for A second network device is found, the second network device is a network device serving the terminal device, and the second network device does not belong to the mobile network system where the first network device is located.
  • the terminal device sends the eighth information to the first network device, it can also be understood that the terminal device sends the eighth information to the first network device through other devices, which is not limited in this application.
  • the first network device cannot discover the second network device according to one piece of related information of the second network device in the tenth information.
  • the first network device discovers the second network device according to the related information of other second network devices in the tenth information.
  • the terminal device in the authentication and authorization process, is used to provide the first network device with a list of second network devices that serve the terminal device and are not in the same mobile network system as the terminal device, so that the first network device is in accordance with the
  • the relevant information of one second network device in the list cannot discover the second network device
  • the second network device can be continuously discovered according to the relevant information of other second network devices in the list, thereby reducing the need for the core network to discover the second network device. Failure, and the legitimate terminal device cannot perform authentication and authorization.
  • FIG. 7 is a schematic interaction diagram of the method 700 of the present application.
  • the embodiments in this application are all described by taking a 5G communication system as an example, and the embodiments of this application may also be applied to 4G or future communication systems, such as the 5G communication system in the embodiments of this application.
  • the registration process may also be a 4G attach process, and the 5G PDU session establishment/modification process may also be a 4G PDN connection establishment/modification process, which is not limited in this application.
  • the UE performs a registration process.
  • the AMF checks whether the UE has an aviation subscription (aerial subscriptions). If the UE has an aviation subscription, the AMF will further request the USS/UTM for UAV authentication authorization for the UE. Before successful UAV authentication and authorization, the UE is not allowed to establish a session related to command and control (C2) communication.
  • C2 command and control
  • the UE will send a registration request message to the AMF during the registration process.
  • the UE includes the relevant information of the USS/UTM serving the UE in the registration request message.
  • the relevant information of the USS/UTM serving the UE may include the UAV identifier (CAA-Level UAV ID), the USS/UTM address or the fully qualified domain name (FQDN) assigned by the aviation management department.
  • UAV identifier CAA-Level UAV ID
  • USS/UTM address or the fully qualified domain name (FQDN) assigned by the aviation management department.
  • FQDN fully qualified domain name assigned by the aviation management department.
  • flight authorization id flight authorization identifier
  • the CAA-Level UAV ID here is the information used to uniquely identify the UAV, which may be allocated independently by USS/UTM, or may be allocated by 3GPP system assisted by USS/UTM, or may be allocated by other means.
  • the CAA-Level UAV ID is used to discover the USS/UTM, that is, the USS/UTM information of the serving UAV can be determined by parsing the CAA-Level UAV ID.
  • the present application does not limit the distribution method and specific composition method of the identifier.
  • the AMF sends a UAV authentication authorization request message to the UFES, where the message includes the above information for discovering the USS/UTM.
  • the network element UFES in this application refers to the network element that opens an interface to the USS/UTM in the 3GPP system. It may be an existing network element, such as NEF, or it may be a new network element. , which is not limited in this application.
  • the UFES determines the USS/UTM serving the UE according to the relevant information of the USS/UTM of the serving UE provided by the UE, and the UFES determines that the discovery of the USS/UTM fails according to the relevant information.
  • UFES determines the USS/UTM serving the UE according to the UAV identification assigned by the aviation management department. Unable to connect, UFES determines that the USS/UTM has failed to be discovered.
  • the second possible reason is that UFES determines the USS/UTM serving the UE according to the USS/UTM address or FQDN provided by the UE. If the determined USS/UTM cannot be connected, the UFES determines that the USS/UTM has failed to be found.
  • Possible reason 3 There is a list of USS/UTM that is allowed or not allowed to be stored in UFES. If the USS/UTM determined by UFES (determined by parsing CAA Level UAV ID or USS/UTM address, etc.) is not an allowed USS/UTM In the list, UFES determines that the USS/UTM has failed to be discovered.
  • the USS/UTM service UE has location and/or time restrictions. If the UFES communicates with the USS/UTM and learns that the location and/or time of the service UE is invalid, that is, the USS/UTM provided by the UAV will no longer serve the UAV. , UFES determines that the USS/UTM has failed to be discovered. As an example, the USS/UTM has signed an agreement with the UE before, and the agreement stipulates that the UE is only served within a certain area and/or a certain time range. Once the area and/or time where the current UE is located is not within the above range, It means that the service has expired.
  • each USS/UTM has limited service capabilities, it must be planned in advance to serve certain UAVs in a certain area at a certain point in time, if it is authorized at the wrong time and/or place, the USS/UTM will No service will be provided.
  • the USS/UTM may be found to fail due to other reasons, such as failure to connect because there is no trust relationship between the UFES and the USS/UTM, which is not limited in this application.
  • the UFES replies to the AMF a UAV authentication authorization response message, where the message includes a USS/UTM discovery failure indication and/or a specific USS/UTM discovery failure reason.
  • the message contains the specific USS/UTM discovery failure reasons, which can be the above-mentioned failure reasons, namely, UAV identification resolution failure, USS/UTM cannot be connected, and USS/UTM is not in the allowed USS/UTM list. Or USS/UTM no longer serves the UE, etc.
  • USS/UTM discovery failure reasons which can be the above-mentioned failure reasons, namely, UAV identification resolution failure, USS/UTM cannot be connected, and USS/UTM is not in the allowed USS/UTM list. Or USS/UTM no longer serves the UE, etc.
  • the AMF sends a USS/UTM information update request message to the UE, where the message is used to request the UE to provide new information for discovering the USS/UTM.
  • the message includes a USS/UTM discovery failure indication, and/or the above-mentioned reason for the USS/UTM discovery failure.
  • the UE sends a USS/UTM information update response message to the AMF.
  • the UE will include the new information about the USS/UTM serving the UE in the response message.
  • the relevant information of the USS/UTM of the serving UE here may be the relevant information of the USS/UTM of one serving UE, or the relevant information of the USS/UTM of multiple serving UEs, that is, the relevant information of the USS/UTM of an alternative serving UE.
  • USS/UTM can be one or more.
  • the AMF indicates in the configuration update command message that it fails to discover the USS/UTM.
  • the configuration update message includes a specific reason for the failure to discover the USS/UTM.
  • the UE performs a mobile registration update process, and includes the new USS/UTM related information of the serving UE in the registration request message.
  • the UE may immediately return new information for discovering the USS/UTM to the network side, or may not immediately return the information to the network side.
  • S705b and S706b may be applicable to scenarios such as the UE needs to obtain new information for discovering USS/UTM through offline or application plane.
  • steps S705b and S706b may be separated by a long time, and other processes may be included in the middle. .
  • the AMF after receiving the USS/UTM discovery failure indication, the AMF sends a deregistration request message to the UE.
  • the registration request message includes a deregistration cause value, that is, USS/UTM discovery failure.
  • the AMF includes the USS/UTM discovery failure indication in the configuration update command message, and the UE sends a de-registration request to the AMF after determining that there is no new information for discovering the USS/UTM.
  • the registration request message It contains the de-registration reason value, that is, there is no available new information about the USS/UTM of the UE serving the UE.
  • the AMF sends a UAV authentication authorization request message to the UFES again, which contains the relevant information of the new USS/UTM serving the UE.
  • the UFES discovers the USS/UTM according to the related information of the USS/UTM of the new serving UE.
  • step S708 If the UFES determines in step S708 that the discovery of the USS/UTM fails, steps S704 to S708 may need to be performed repeatedly until the USS/UTM is successfully discovered. If the USS/UTM is successfully discovered in step S708, step S709 is not performed.
  • the UFES sends a UAV authentication authorization request message to the USS/UTM.
  • the USS/UTM responds to the UFES with a UAV authentication authorization response, which includes the authorization result.
  • the UFES forwards the UAV authentication and authorization response to the AMF.
  • the AMF sends a configuration update command message to the UE, which indicates the authorization result of the UAV.
  • the core network side device instructs the UE to update the relevant information of the USS/UTM serving the UE, specifically, the AMF requests The UE provides new information about the USS/UTM of the UE serving the UE, or the AMF indicates to the UE that the discovery of the USS/UTM fails, thereby reducing the problem that the legitimate UE cannot perform UAV authentication and authorization due to the failure of the core network to discover the USS/UTM. .
  • FIG. 8 is a schematic interaction diagram of the method 800 of the present application.
  • the UE performs a registration process.
  • the UE may perform the UAV authentication and authorization process, that is, steps S702 to S713 in the method 700 .
  • step S802 may or may not be performed, and when step S802 is not performed, the method 800 is applicable to various scenarios.
  • step S802 is executed:
  • the UAV authentication and authorization process is performed during the registration process.
  • step S802 is not executed:
  • the UAV authentication and authorization process is executed in the PDU session establishment process, or the UAV authentication and authorization process is executed in the PDU session modification process.
  • the corresponding PDU session establishment request is a PDU session modification request
  • the corresponding PDU session establishment acceptance is a PDU session modification.
  • the PDU session modification process is used as an example here, which is not limited in this application.
  • the UAV authentication and authorization is performed in the registration process or in the PDU session establishment process, and the session communicated between UAV and USS/UTM and the session communicated between UAV and UAVC are the same session, or UAV
  • the session communicated with the USS/UTM and the session communicated between the UAV and the UAVC are different sessions, which are not limited in this application.
  • the UE initiates a PDU session establishment request to the SMF.
  • the SMF determines that C2 communication authentication and authorization is required, and sends a C2 communication authentication authorization request message to the UFES, which includes information for discovering the USS/UTM.
  • the UFES replies to the SMF a C2 communication authentication authorization response message, wherein the content included in the C2 communication authentication authorization response message is consistent with that in S704 in the method 700.
  • S807a to S810a After the SMF receives the USS/UTM discovery failure indication, there are multiple ways to process, such as the following S807a to S810a, or, S807b and S808b.
  • the SMF after receiving the USS/UTM discovery failure indication, the SMF sends the USS/UTM discovery failure indication to the AMF.
  • S808a to S809a are the same as S705a to S706a in the method 700 .
  • the AMF after receiving the USS/UTM information update response, the AMF sends a USS/UTM discovery failure indication to the SMF, and sends the received information about the new USS/UTM serving the UE to the SMF.
  • the SMF sends a PDU session establishment accept message to the UE, where the PDU session establishment accept message includes a USS/UTM discovery failure indication.
  • the UE initiates a PDU session establishment/modification request, and the message includes the relevant information of the new USS/UTM serving the UE.
  • S807b and S808b may immediately return the new information about the USS/UTM serving the UE to the network side, or may not immediately return the information to the network side.
  • S807b and S808b may be applicable to scenarios such as the UE needs to obtain new information for discovering USS/UTM through offline or application plane.
  • steps S807b and S808b may be separated by a long time, and other processes may be included in the middle. .
  • the SMF after receiving the indication of USS/UTM discovery failure, the SMF sends a PDU session establishment reject message to the UE.
  • the PDU session establishment rejection message may include a rejection cause value.
  • the rejection cause value may be a USS/UTM discovery failure.
  • the SMF includes the USS discovery failure indication in the PDU Session Accept message. After determining that there is no new information for discovering the USS/UTM, the UE sends a session release request to the SMF, optionally including the deregistration reason value. , ie there is no new discovery USS/UTM information available.
  • the SMF sends a C2 communication authentication authorization request message to the UFES again, which contains new information for discovering the USS/UTM.
  • the UFES discovers the USS/UTM according to the new information for discovering the USS/UTM.
  • step S813 if the UFES determines in step S812 that the USS/UTM discovery fails, steps S806 to S812 may need to be repeatedly performed. If the USS/UTM is successfully discovered in step S812, step S813 is not performed.
  • the UFES after determining the USS/UTM for serving the UE, the UFES sends a C2 communication authentication authorization request message to the USS/UTM.
  • the USS/UTM responds to the UFES with a C2 communication authentication authorization response, which includes the authorization result.
  • the UFES forwards it to the SMF.
  • the SMF sends a PDU session establishment/modification response message to the UE, which indicates the authorization result of the UAV.
  • the core network side device instructs the UE to update the USS/UTM serving the UE Specifically, the SMF triggers the AMF to initiate a USS/UTM information update request to the UE, or the SMF initiates a PDU session establishment request to the UE, and indicates the failure to discover the UDD/UTM, thereby reducing the need for the core network to discover the USS/UTM.
  • UTM fails, and the legitimate UE cannot perform UAV authentication and authorization.
  • FIG. 9 is a schematic interaction diagram of the method 900 of the present application.
  • the UE performs a registration process.
  • the UAV authentication and authorization process the UAV authentication and authorization process.
  • the UFES receives the authorization and authentication request message, which contains the information for discovering the USS/UTM.
  • step S902 may be step S702 in method 700 or steps S803-S804 in method 800, or may be other implementation manners, which are not limited in this embodiment.
  • step S903 which is consistent with step S703 in the method 700.
  • the UFES sends a USS/UTM discovery request message to a fourth network device, where the request message is used to request the fourth network device to provide information about the USS/UTM serving the UE.
  • the UFES stores information of a fourth network device, and the fourth network device can be used to discover the USS/UTM.
  • Step S904 is executed when the UFES determines that the USS/UTM serving the UE cannot be discovered according to the relevant information about the USS/UTM of the serving UE provided by the UE.
  • the request message may include at least one of the information of the UE and the related information of the USS/UTM of the service UE provided by the UE.
  • the request message may include first indication information, where the indication information indicates that the USS/UTM discovery fails.
  • the fourth network device provides the UFES with a USS/UTM discovery response message, where the message includes USS/UTM information.
  • the fourth network device has inquired about the USS/UTM that can serve the UE for the UE, and then sends the queried information about the USS/UTM serving the UE to the UFES through a USS/UTM discovery response message.
  • the related information of the USS/UTM of the serving UE may be the related information of the USS/UTM of one or more serving UEs.
  • the fourth network device When the fourth network device only has the function of querying the USS/UTM of the serving UE, it can provide a USS/UTM discovery failure indication in the message; or, when the fourth network device also has the function of USS/UTM, it can It serves the UE by itself, and sends its own information to the UFES through the USS/UTM discovery response message.
  • the method 900 may further include a step, the fourth network device queries the USS/UTM serving the UE according to the received USS/UTM discovery request message.
  • step S906 if in S905, the response message sent by the fourth network device includes a USS/UTM discovery failure indication, then in step S906, steps S704 to S708 in the method 700, or steps S806 to S812 in the method 800 can be combined. , so that the UE provides the information for discovering the USS/UTM again.
  • the UFES sends a UAV and/or C2 communication authentication authorization request message to the USS/UTM.
  • the USS/UTM provides a UAV and/or C2 communication authentication authorization response message to the UFES.
  • the UFES forwards the authentication and authorization result to the core network element, which is consistent with steps S712 and S713 in the method 700 .
  • the core network when the core network fails to discover the USS/UTM, the core network requests the fourth network device for new information about the USS/UTM serving the UE, and according to the USS/UTM serving the UE provided by the fourth network device The relevant information of the UE determines the USS/UTM of the serving UE, thereby reducing the problem that the legitimate UE cannot perform UAV authentication and authorization due to the failure of the core network to discover the USS/UTM.
  • FIG. 10 is a schematic interaction diagram of the method 1000 of the present application.
  • the UE performs a registration process.
  • the UFES receives an authorization authentication request message, and the message includes a list of USS/UTM serving the UE, in other words, multiple alternative USS/UTM serving the UE provided by the UE to the UFES.
  • the message includes a plurality of indication information, each indication information includes relevant information of a USS/UTM of a serving UE, and the USS/UTM corresponding to each indication information is different.
  • the UFES can indicate the priority of each candidate USS/UTM in the list, so that when the UFES determines that the USS/UTM fails to be discovered according to the information related to one of the USS/UTMs, the priority indicated in the list can be used. USS/UTM is discovered in turn according to other USS/UTM related information.
  • the UFES determines that the USS/UTM fails to discover the USS/UTM according to the USS/UTM related information of the serving UE, and the reason for the failure to discover the USS/UTM is consistent with step S703 in the method 700.
  • this step further includes:
  • the UFES determines whether the USS/UTM is successfully discovered according to the priority or order of the alternative USS/UTM-related information, and once the USS/UTM is successfully discovered, the USS/UTM is used.
  • the UFES determines that the USS/UTM fails to be found according to the relevant information of the USS/UTM with the highest priority or the first in the order, it will go to the USS/UTM with the second highest priority or in the second order according to the relevant information Discover USS/UTM. If USS/UTM is successfully discovered, use it. If discovery fails, continue to discover USS/UTM based on USS/UTM related information in a similar way.
  • step S1004 If the UFES finds that the USS/UTM fails according to the USS/UTM list provided by the UAV, in step S1004, steps S704 to S708 in the method 700, or steps S806 to S812 in the method 800 can be combined to make the UE re-provide for Discover USS/UTM information.
  • the USS/UTM provides a UAV and/or C2 communication authentication authorization response message to the UFES.
  • the UFES forwards the authentication and authorization result to the core network element, which is consistent with steps S712 and S713 in the method 700.
  • the UE provides the core network with a list of candidate USS/UTMs including relevant information of multiple USS/UTMs serving the UE, so that the core network finds that the USS/UTM fails according to the relevant information of one of the USS/UTMs. It is possible to continue to discover the USS/UTM according to the relevant information of other USS/UTMs in the list, thereby reducing the problem that the legitimate UE cannot perform UAV authentication and authorization due to the failure of the core network to discover the USS/UTM.
  • FIG. 11 is a schematic block diagram of a communication apparatus for discovering a service entity provided by an embodiment of the present application.
  • the communication device 10 may include a transceiver module 11 and a processing module 12 .
  • the transceiver module 11 may be used to receive information sent by other devices, and may also be used to send information to other devices. For example, receiving the first information or sending the second information.
  • the processing module 12 may be configured to perform content processing of the apparatus, for example, the second network device cannot be found according to the first information.
  • the communication apparatus 10 may correspond to the first network device or the UFES or the NEF in the above method embodiment.
  • the communication apparatus 10 may correspond to the first network device or UFES or NEF in any one of the methods 400 to 1000 according to the embodiments of the present application, and the communication apparatus 10 may include a method for executing A module of operations performed by a network device or UFES or NEF, and each unit in the communication apparatus 10 is respectively in order to implement the operations performed by the first network device or UFES or NEF in the corresponding method.
  • the transceiver module 11 is configured to execute steps S402, S404, and S407, and the processing module 12 is configured to instruct step S403.
  • the transceiver module 11 is configured to execute steps S501, S503, and S505, and the processing module 12 is configured to instruct step S502.
  • the transceiver module 11 is configured to execute step S601
  • the processing module 12 is configured to instruct steps S602 and S603.
  • the transceiver module 11 is configured to execute steps S702, S704, S707, S710, S711 and S712, and the processing module 12 is configured to instruct steps S703 and S708.
  • the transceiver module 11 is configured to execute steps S804, S806, S811, S814, S815, and S816, and the processing module 12 is configured to instruct steps S802, S805, S812.
  • the transceiver module 11 is configured to execute steps S904, S905, S907, and S908, and the processing module 12 is configured to instruct steps S901, S902, S903, S906, S909.
  • the transceiver module 11 is configured to execute steps S1005 and S1006, and the processing module 12 is configured to instruct steps S1001, S1002, S1003, S1004, and S1007.
  • the transceiver module 11 is configured to receive first information, where the first information includes related information of a second network device, the second network device is the to-be-discovered information provided by the terminal device network device, and the second network device does not belong to the mobile network system where the first network device is located; the processing module 12 is configured to perform discovery processing for the second network device according to the first information; When the device discovery process fails, the transceiver module 11 is further configured to send second information, where the second information is used to request to re-provide the network device to be discovered; the transceiver module 11 is also configured to receive third information, the first The third information includes relevant information of the fifth network device, the fifth network device is the updated network device to be discovered provided by the terminal device, and the fifth network device does not belong to the mobile network system where the first network device is located; The processing module 12 is further configured to perform discovery processing for the fifth network device according to the third information.
  • the second information includes first indication information, and the first indication information requests to re-provide the network device to be discovered.
  • the second information includes at least one of second indication information and a first cause value, wherein the second indication information indicates that the first network device cannot discover the second network device according to the first information, and the first The reason value indicates the reason why the first network device cannot discover the second network device according to the first information.
  • the transceiver module 11 is configured to receive seventh information from a terminal device, where the fifth information includes relevant information of a second network device that serves the terminal The network device of the device, and the second network device does not belong to the mobile network system where the first network device is located; the processing module 12 is configured to fail to discover the second network device according to the seventh information; the transceiver module 11 also uses to send eighth information to the fourth network device, the eighth information requests the relevant information of the second network device; the transceiver module 11 is also used to receive ninth information from the fourth network device, the ninth information includes relevant information of the second network device.
  • the eighth information includes at least one of fifth indication information and a third reason value, wherein the fifth indication information indicates that the first network device cannot discover the second network device according to the first information, and the third The reason value indicates the reason why the first network device cannot discover the second network device according to the first information.
  • the eighth information includes the seventh information.
  • the transceiver module 11 is configured to receive tenth information from the terminal device, where the tenth information includes a first list, and the first list includes related information of at least one second network device information, the relevant information of each second network device is used to discover a second network device, the second network device is a network device serving the terminal device, and the second network device does not belong to the location of the first network device
  • the mobile network system the processing module 12 is configured to be unable to discover the second network device according to the relevant information of the second network device in the eighth information; the processing module 12 is also configured to use the information in the tenth information Other relevant information of the second network device discovers the second network device.
  • the tenth information further includes priority information of related information of the plurality of second network devices, and the first network device discovers the second network devices according to the priority order.
  • the communication apparatus 10 may correspond to the terminal device in the above method embodiment.
  • the communication apparatus 10 may correspond to a terminal device in any one of the methods 400 to 1000 according to the embodiments of the present application, and the communication apparatus 10 may include a device for performing operations performed by the terminal device in the corresponding method. modules, and each unit in the communication apparatus 10 is respectively to implement the operations performed by the terminal device in the corresponding method.
  • the transceiver module 11 is configured to perform steps S401, S405, and S406.
  • the transceiver module 11 is configured to perform step S501.
  • the transceiver module 11 is configured to execute step S601.
  • the transceiver module 11 is configured to perform steps S701, S705a-S706a or SS705b-S706b, S709, S713.
  • the transceiver module 11 is configured to perform steps S801, S802, S803, S802, S808a-S809a or S807b-S808b, S813, and S817.
  • the transceiver module 11 is configured to perform steps S901, S902, S906, and S909.
  • the transceiver module 11 is configured to perform steps S1001, S1002, S1004, and S1007.
  • the transceiver module 11 is configured to send fourth information, where the fourth information includes relevant information of a second network device, and the second network device is the to-be-discovered information provided by the terminal device. network equipment, and the second network equipment does not belong to the mobile network system where the terminal equipment is located; the transceiver module 11 is further configured to receive fifth information, and the fifth information is used to request the terminal equipment to re-provide the network equipment to be discovered ; The transceiver module 11 is also used to send the sixth information, the sixth information includes the relevant information of the fifth network device, the fifth network device is the updated network device to be discovered, and the fifth network device does not belong to The mobile network system where the terminal device is located.
  • the fourth information includes third indication information
  • the third indication information requests the terminal device to re-provide the network device to be discovered.
  • the fourth information includes at least one of fourth indication information and a second cause value, wherein the fourth indication information indicates that the first network device cannot discover the second network device according to the third information, and the second The reason value indicates the reason why the first network device cannot discover the second network device according to the third information.
  • the transceiver module 11 is configured to send tenth information, where the tenth information includes a first list, and the first list includes related information of at least one second network device, each The relevant information of the second network device is used to discover a second network device, the second network device is a network device serving the terminal device, and the second network device does not belong to the mobile network system accessed by the terminal device.
  • the tenth information further includes priority information of the related information of the plurality of second network devices, and the first network device discovers the second network devices in order of priority.
  • the communication apparatus 10 may correspond to the third network device or AMF or SMF in the above method embodiment.
  • the communication apparatus 10 may correspond to the third network device or AMF or SMF in any of the methods 400, 700 to 1000 according to the embodiments of the present application, and the communication apparatus 10 may include a method for executing the corresponding method.
  • the modules in the operation performed by the third network device or AMF or SMF, and each unit in the communication apparatus 10 is respectively in order to realize the operations performed by the third network device or AMF or SMF in the corresponding method.
  • the transceiver module 11 is configured to perform steps S401, S402, S405, and S406.
  • the transceiver module 11 is configured to perform steps 701, S72, S704, S705a-S706a or S705b-S706b, S707, S709, S7012, and S713.
  • the transceiver module 11 is configured to perform steps S801, S802, S803, S804, S806, S807a and S810a, or, S807b and S808b, S811, S813, and S816 , S817.
  • the transceiver module 11 is configured to execute steps S807a-S810a or S807b-S808b, S813.
  • the transceiver module 11 is configured to perform steps S901, S902, S906, and S909.
  • the transceiver module 11 is configured to perform steps S1001, S1002, S1004, and S1007.
  • the transceiver module 11 is configured to receive second information, where the second information is used to request to re-provide a network device to be discovered, the network device to be discovered is a network device provided by a terminal device to serve the terminal device, and the The network device to be discovered does not belong to the mobile network system where the third network device is located; the processing module 12 is configured to send fifth information according to the second information, and the fifth information is used to request to re-provide the network device to be discovered; The transceiver module 11 is further configured to receive sixth information, where the sixth information includes relevant information of the fifth network device, the fifth network device is the updated network device to be discovered provided by the terminal device, and the sixth information is The fifth network device does not belong to the mobile network system where the third network device is located; the transceiver module 11 is also used for third information, where the third information includes relevant information of the fifth network device.
  • the second information includes first indication information, and the first indication information requests to provide the to-be-discovered network device again.
  • the second information includes at least one of second indication information and a first cause value, wherein the second indication information indicates that the first network device cannot discover the second network device according to the first information, and the first cause value Indicates the reason why the first network device cannot discover the second network device according to the first information.
  • the fourth information includes third indication information, and the third indication information instructs the terminal device to update the third information.
  • the second information includes at least one of fourth indication information and a second cause value, wherein the fourth indication information indicates that the first network device cannot discover the second network device, and the second reason value indicates that the first network device The reason why the device cannot find the second network device according to the third information.
  • the communication apparatus 10 may correspond to the fourth network device in the above method embodiment.
  • the communication apparatus 10 may correspond to the fourth network device in any one of the method 500 and the method 900 according to the embodiment of the present application, and the communication apparatus 10 may include a method for executing the method specified by the fourth network device in the corresponding method. Modules for performing operations, and each unit in the communication apparatus 10 is respectively in order to implement the operations performed by the fourth network device in the corresponding method.
  • the transceiver module 11 is configured to execute steps S503 and S505, and the processing module 12 is configured to instruct step S504.
  • the transceiver module 11 is configured to perform steps S904 and S905.
  • the transceiver module 11 is configured to receive eighth information from the first network device, the eighth information requests related information of a second network device, the second network device is a network device serving the terminal device, and the The second network device does not belong to the mobile communication system where the first network device is located; the processing module 12 is used to query the relevant information of the second network device for the first network device; the transceiver module 11 is also used to send the first network device to the first network device.
  • a network device sends ninth information, where the ninth information includes related information of the second network device.
  • the eighth information includes at least one of fifth indication information and a third reason value, wherein the fifth indication information indicates that the first network device cannot discover the second network device according to the first information, and the third The reason value indicates the reason why the first network device cannot discover the second network device according to the first information.
  • the eighth information includes the seventh information.
  • FIG. 12 is a schematic diagram of an apparatus 20 for information transmission provided by an embodiment of the present application.
  • the device 20 may be a UFES or NEF, or a chip or a chip system or the like located on the UFES or NEF.
  • the apparatus 20 may be a terminal device, including various handheld devices with wireless communication functions, vehicle-mounted devices, wearable devices, computing devices, or other processing devices connected to a wireless modem, as well as various forms of
  • the terminal, mobile station, terminal, user equipment, soft terminal, etc. can also be a chip or a chip system located on the terminal equipment.
  • the apparatus 20 may be AMF, SMF or MME, including various devices for mobility management and access management and/or for session management functions, etc. Chip or system on chip on SMF or MME etc.
  • the device 20 may be a USS or a UTM, or a chip or a chip system or the like located on the USS or UTM.
  • the apparatus 20 may include a processor 21 (ie, an example of a processing module) and a memory 22 .
  • the memory 22 is used for storing instructions
  • the processor 21 is used for executing the instructions stored in the memory 22, so that the apparatus 20 implements the execution of the devices in the various possible designs described above in the methods corresponding to FIG. 4 to FIG. 9 . step.
  • the device 20 may further include an input port 23 (ie, an example of a transceiver module) and an output port 24 (ie, another example of a transceiver module).
  • the processor 21, the memory 22, the input port 23 and the output port 24 can communicate with each other through an internal connection path to transmit control and/or data signals.
  • the memory 22 is used to store a computer program, and the processor 21 can be used to call and run the computer program from the memory 22 to control the input port 23 to receive signals, control the output port 24 to send signals, and complete the process of the terminal device in the above method. step.
  • the memory 22 may be integrated in the processor 21 or may be provided separately from the processor 21 .
  • the input port 23 is a receiver
  • the output port 24 is a transmitter.
  • the receiver and the transmitter may be the same or different physical entities. When they are the same physical entity, they can be collectively referred to as transceivers.
  • the input port 23 is an input interface
  • the output port 24 is an output interface
  • the functions of the input port 23 and the output port 34 can be considered to be implemented by a transceiver circuit or a dedicated chip for transceiver.
  • the processor 21 can be considered to be implemented by a dedicated processing chip, a processing circuit, a processor or a general-purpose chip.
  • a general-purpose computer may be used to implement the device provided by the embodiments of the present application.
  • the program codes that will implement the functions of the processor 21 , the input port 23 and the output port 24 are stored in the memory 22 , and the general-purpose processor implements the functions of the processor 21 , the input port 23 and the output port 24 by executing the codes in the memory 22 .
  • each module or unit in the apparatus 20 may be used to perform each action or process performed by the device (eg, terminal device) performing random access in the above method, and detailed description thereof is omitted here to avoid redundant description.
  • the processor may be a central processing unit (CPU, central processing unit), and the processor may also be other general-purpose processors, digital signal processors (DSP, digital signal processors), dedicated integrated Circuit (application specific integrated circuit, ASIC), off-the-shelf programmable gate array (field programmable gate array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.
  • DSP digital signal processors
  • ASIC application specific integrated circuit
  • FPGA off-the-shelf programmable gate array
  • a general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
  • Embodiments of the present application further provide a computer-readable storage medium, on which computer instructions for implementing the method executed by the terminal device in the foregoing method embodiments are stored.
  • the computer program when executed by a computer, the computer can implement the method executed by the terminal device in the above method embodiments.
  • Embodiments of the present application further provide a computer-readable storage medium, on which computer instructions for implementing the method performed by the first network device or the UFES or the NEF in the foregoing method embodiments are stored.
  • the computer program when executed by a computer, the computer can implement the method executed by the first network device or the UFES or the NEF in the above method embodiments.
  • Embodiments of the present application further provide a computer-readable storage medium, on which computer instructions for implementing the method executed by the third network device or the AMF or the SMF in the foregoing method embodiments are stored.
  • the computer when the computer program is executed by a computer, the computer can implement the method executed by the third network device or the AMF or the SMF in the above method embodiments.
  • Embodiments of the present application further provide a computer-readable storage medium, on which computer instructions for implementing the method executed by the fourth network device in the foregoing method embodiments are stored.
  • the computer when the computer program is executed by a computer, the computer can implement the method executed by the fourth network device in the above method embodiments.
  • Embodiments of the present application further provide a computer program product including instructions, which, when executed by a computer, cause the computer to implement the method executed by the terminal device in the above method embodiments, or the method executed by the first network device or the UFES or the NEF , or a method performed by a third network device or AMF or SMF, or a method performed by a fourth network device.
  • An embodiment of the present application further provides a communication system, where the communication system includes the terminal device, the first network device or UFES or NEF, and the third network device or AMF or SMF in the above embodiments.
  • An embodiment of the present application further provides a communication system, where the communication system includes the terminal device in the above embodiment, the first network device or UFES or NEF, and the fourth network device.
  • the memory in the embodiments of the present application may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically programmable Erase programmable read-only memory (electrically EPROM, EEPROM) or flash memory.
  • Volatile memory may be random access memory (RAM), which acts as an external cache.
  • RAM random access memory
  • SRAM static random access memory
  • DRAM dynamic random access memory
  • SDRAM synchronous dynamic random access memory
  • DDR SDRAM Double data rate synchronous dynamic random access memory
  • ESDRAM enhanced synchronous dynamic random access memory
  • SLDRAM synchronous link dynamic random access memory
  • direct rambus RAM direct rambus RAM
  • the above embodiments may be implemented in whole or in part by software, hardware, firmware or any other combination.
  • the above-described embodiments may be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions or computer programs. When the computer instructions or computer programs are loaded or executed on a computer, all or part of the processes or functions described in the embodiments of the present application are generated.
  • the computer may be a general purpose computer, special purpose computer, computer network, or other programmable device.
  • the computer instructions may be stored in or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions may be downloaded from a website site, computer, server or data center Transmission to another website site, computer, server or data center by wire (eg, infrared, wireless, microwave, etc.).
  • the computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server, a data center, or the like that contains one or more sets of available media.
  • the usable media may be magnetic media (eg, floppy disks, hard disks, magnetic tapes), optical media (eg, DVDs), or semiconductor media.
  • the semiconductor medium may be a solid state drive.
  • the size of the sequence numbers of the above-mentioned processes does not mean the sequence of execution, and the execution sequence of each process should be determined by its functions and internal logic, and should not be dealt with in the embodiments of the present application. implementation constitutes any limitation.
  • the apparatus 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 shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit.
  • the functions, if implemented in the form of software functional units and sold or used as independent products, may be stored in a computer-readable storage medium.
  • the computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application.
  • a computer device which may be a personal computer, a server, or a network device, etc.
  • the aforementioned storage medium includes: a U disk, a removable hard disk, a ROM, a RAM, a magnetic disk, or an optical disk and other mediums that can store program codes.

Landscapes

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

Abstract

本申请提供了一种发现服务实体的方法和装置，在核心网根据终端设备提供的服务终端设备的第三方实体的相关信息不能发现该第三方实体时，通过核心网向终端设备再次请求该第三方实体的相关信息，或者，核心网向其他设备请求该第三方实体的相关信息，或者，核心网根据终端设备提供的包括多个该第三方实体的相关信息的列表中的其他该第三方实体的相关信息发现该第三方实体。本申请提供的发现服务实体的方法和装置，能够减少由于核心网发现该第三方实体失败，而导致合法的终端设备无法进行认证授权的问题。

Description

发现服务实体的方法和通信装置
本申请要求于2021年3月15日提交中国国家知识产权局、申请号为202110277238.9、发明名称为“发现服务实体的方法和通信装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域，并且更具体地，涉及一种发现服务实体的方法和通信装置。
背景技术
近年来，无人机应用的逐渐普及在给大众带来各种经济利益和娱乐消遣的同时，也使得无人机的管理更加复杂。而无人机接入网络后，可以获得无人机系统服务，有利于更好地管理无人机。
为了接入网络，无人机需要进行一系列的认证授权，而无人机进行认证授权的前提是第三代合作伙伴计划(3rd generation partnership project，3GPP)系统能够成功地发现能够为无人机服务的第三方实体，该第三方实体通常不属于无人机接入的3GPP系统。目前，对于3GPP系统未能成功发现该第三方实体而导致无法进行认证授权的场景，尚没有对应的解决方案。
发明内容
本申请提供一种发现服务实体的方法和通信装置，减少由于核心网未能成功发现为终端设备服务的第三方实体，而导致合法的终端设备无法进行认证授权的问题。
第一方面，提供了一种发现服务实体的方法，包括：第一网络设备接收第一信息，该第一信息包括第二网络设备的相关信息，该第二网络设备为该终端设备提供的待发现的网络设备，且该第二网络设备不属于该第一网络设备所在的移动网络系统；该第一网络设备根据该第一信息进行针对该第二网络设备的发现处理；当针对该第二网络设备的发现处理失败时，该第一网络设备发送第二信息，该第二信息用于请求重新提供待发现的网络设备；该第一网络设备接收第三信息，该第三信息包括第五网络设备的相关信息，该第五网络设备是该终端设备提供的更新后的待发现的网络设备，且该第五网络设备不属于该第一网络设备所在的移动网络系统；该第一网络设备根据该第三信息进行针对该第五网络设备的发现处理。
应理解，本申请中提及的移动网络系统也可以理解为移动网络运营商的网络系统，例如PLMN，或者也可以称为3GPP系统，本申请对于该移动网络系统的名称不做限定。本申请中的该第二网络设备不属于该终端设备所在的移动网络系统可以理解为第二网络设备不属于任何一个运营商，在某些场景下，也可以称之为第三方实体，还可以称之为服务实体，在终端设备是联网无人机的场景下，该第二网络设备可以是USS、UTM或USS/UTM， 本申请对于该第二网络设备的名称不做限定。
应理解，本申请中，该第一网络设备可以向接入和移动管理功能网元或会话管理网元发送第二信息，也可以向其他网络设备发送第二信息，本申请对此不做限定。
应理解，本申请中，该第一网络设备可以接收来自接入和移动管理功能网元或会话管理网元的更新后的该第一信息，也可以从其他网络设备接收更新后的该第一信息，或者也可以从终端设备接收更新后的该第一信息，本申请对此不做限定。
需要说明的是，本申请中待发现的网络设备包括但不限于第三方实体、第二网络设备、第五网络设备、USS/UTM，该待发现的网络设备具备“服务终端设备”或者“服务UE”的能力，和/或管理终端设备或者管理UE的行为的能力。
上述技术方案，在认证授权流程中，当核心网发现服务终端设备的、与终端设备不在同一个移动网络系统的第二网络设备失败时，通过核心网侧设备指示终端设备更新待发现的网络设备的相关信息，从而减少由于核心网发现第三方实体失败，而导致合法的终端设备无法进行认证授权的问题。
结合第一方面，在第一方面的某些实现方式中，该第二信息包括第一指示信息，该第一指示信息请求重新提供待发现的网络设备。
结合第一方面，在第一方面的某些实现方式中，该第二信息包括第二指示信息和第一原因值中的至少一个，其中，该第二指示信息指示该第一网络设备根据该第一信息不能发现该第二网络设备，该第一原因值指示该第一网络设备根据该第一信息不能发现该第二网络设备的原因。
第二方面，提供了一种发现服务实体的方法，包括：终端设备发送第四信息，该第四信息包括第二网络设备的相关信息，该第二网络设备为该终端设备提供的待发现的网络设备，且该第二网络设备不属于该终端设备所在的移动网络系统；该终端设备接收第五信息，该第五信息用于请求该终端设备重新提供待发现的网络设备；该终端设备发送第六信息，该第六信息包括第五网络设备的相关信息，该第五网络设备是更新后的待发现的网络设备，且该第五网络设备不属于该终端设备所在的移动网络系统。
上述技术方案，在认证授权流程中，在终端设备向核心网发送服务终端设备的、与终端设备不在同一个移动网络系统的第二网络设备的相关信息之后，收到核心网发送的请求重新提供待发现的网络设备的相关信息的指示之后，向核心网发送第五网络设备的相关信息，通过终端设备在认证授权失败后及时向核心网更新待发现的网络设备的相关信息，从而减少由于核心网发现第三方实体失败，而导致合法的终端设备无法进行认证授权的问题。
结合第二方面，在第二方面的某些实现方式中，该第四信息包括第三指示信息，该第三指示信息请求重新提供待发现的网络设备。
结合第二方面，在第二方面的某些实现方式中，该第四信息包括第四指示信息和第二原因值中的至少一个，其中，该第四指示信息指示该第一网络设备根据该第三信息不能发现该第二网络设备，该第二原因值指示该第一网络设备根据该第三信息不能发现该第二网络设备的原因。
第三方面，提供了一种发现服务实体的方法，包括：第三网络设备接收第二信息，该第二信息用于请求重新提供待发现的网络设备，该待发现的网络设备为终端设备提供的服务该终端设备的网络设备，且该待发现的网络设备不属于该第三网络设备所在的移动网络 系统；该第三网络设备根据该第二信息发送第五信息，该第五信息用于请求重新提供该待发现的网络设备；该第三网络设备接收第六信息，该第六信息包括该第五网络设备的相关信息，该第五网络设备是该终端设备提供的更新后的待发现的网络设备，且该第五网络设备不属于该第三网络设备所在的移动网络系统；该第三网络设备发送第三信息，该第三信息包括该第五网络设备的相关信息
上述技术方案，在认证授权流程中，当核心网发现服务终端设备的、与终端设备不在同一个移动网络系统的第二网络设备失败时，通过核心网侧设备指示终端设备更新待发现的网络设备的相关信息，从而减少由于核心网发现第三方实体失败，而导致合法的终端设备无法进行认证授权的问题。
结合第三方面，在第三方面的某些实现方式中，该第二信息包括第一指示信息，该第一指示信息请求重新提供待发现的网络设备。
结合第三方面，在第三方面的某些实现方式中，该第二信息包括第二指示信息和第一原因值中的至少一个，其中，该第二指示信息指示该第一网络设备根据该第一信息不能发现该第二网络设备，该第一原因值指示该第一网络设备根据该第一信息不能发现该第二网络设备的原因。
结合第三方面，在第三方面的某些实现方式中，该第四信息包括第三指示信息，该第三指示信息指示该终端设备更新该第三信息。
结合第三方面，在第三方面的某些实现方式中，该第四信息包括第四指示信息和第二原因值中的至少一个，其中，该第四指示信息指示该第一网络设备不能发现该第二网络设备，该第二原因值指示该第一网络设备根据该第三信息不能发现该第二网络设备的原因。
第四方面，提供了一种发现服务实体的方法，包括：第一网络设备接收来自终端设备的第七信息，该第七信息包括第二网络设备的相关信息，该第二网络设备为服务该终端设备的网络设备，且该第二网络设备不属于该第一网络设备所在的移动网络系统；该第一网络设备根据该第七信息不能发现该第二网络设备；该第一网络设备向第四网络设备发送第八信息，该第八信息请求该第二网络设备的相关信息；该第一网络设备接收来自该第四网络设备的第九信息，该第九信息包括该第二网络设备的相关信息。
上述技术方案，在认证授权流程中，当核心网发现服务终端设备的、与终端设备不在同一个移动网络系统的第二网络设备失败时，通过核心网向第四网络设备请求新的第二网络设备的相关信息，从而减少由于核心网发现第二网络设备失败，而导致合法的终端设备无法进行认证授权的问题。
结合第四方面，在第四方面的某些实现方式中，该第八信息包括第五指示信息和第三原因值中的至少一个，其中，该第五指示信息指示该第一网络设备根据该第一信息不能发现该第二网络设备，该第三原因值指示该第一网络设备根据该第一信息不能发现该第二网络设备的原因。
结合第四方面，在第四方面的某些实现方式中，该第八信息包括该第七信息中包含的部分或全部信息。
第五方面，提供了一种发现服务实体的方法，包括：第四网络设备接收来自该第一网络设备的第八信息，该第八信息请求第二网络设备的相关信息，该第二网络设备为服务该终端设备的网络设备，且该第二网络设备不属于该第一网络设备所在的移动通信系统；该 第四网络设备为该第一网络设备查询该第二网络设备的相关信息；该第四网络设备向该第一网络设备发送第九信息，该第九信息包括该第二网络设备的相关信息。
上述技术方案，在认证授权流程中，当核心网发现服务终端设备的、与终端设备不在同一个移动网络系统的第二网络设备失败时，通过核心网向第四网络设备请求新的第二网络设备的相关信息，从而减少由于核心网发现第二网络设备失败，而导致合法的终端设备无法进行认证授权的问题。
结合第五方面，在第五方面的某些实现方式中，该第八信息包括第五指示信息和第三原因值中的至少一个，其中，该第五指示信息指示该第一网络设备根据该第一信息不能发现该第二网络设备，该第三原因值指示该第一网络设备根据该第一信息不能发现该第二网络设备的原因。
结合第五方面，在第五方面的某些实现方式中，或者该第八信息包括该第七信息中的部分或全部信息。
第六方面，提供了一种发现服务实体的方法，包括：第一网络设备接收来自终端设备的第十信息，该第十信息包括第一列表，该第一列表包括至少一个第二网络设备的相关信息，每个该第二网络设备的相关信息用于发现一个该第二网络设备，该第二网络设备为服务该终端设备的网络设备，且该第二网络设备不属于该第一网络设备所在的移动网络系统；该第一网络设备根据该第十信息中的一个该第二网络设备的相关信息不能发现该第二网络设备；该第一网络设备根据该第十信息中的其他该第二网络设备的相关信息发现该第二网络设备。
上述技术方案，在认证授权流程中，通过终端设备向第一网络设备提供服务终端设备的、与终端设备不在同一个移动网络系统的第二网络设备的列表，使得第一网络设备在根据该列表中的一个第二网络设备的相关信息不能发现第二网络设备时，可以根据该列表中的其他第二网络设备的相关信息继续发现第二网络设备，从而减少由于核心网发现第二网络设备失败，而导致合法的终端设备无法进行认证授权的问题。
结合第六方面，在第六方面的某些实现方式中，该第十信息还包括该多个第二网络设备的相关信息的优先级信息，该第一网络设备按照优先级的顺序发现该第二网络设备。
第七方面，提供了一种发现服务实体的方法，包括：终端设备发送第十信息，该第十信息包括第一列表，该第一列表包括至少一个第二网络设备的相关信息，每个该第二网络设备的相关信息用于发现一个该第二网络设备，该第二网络设备为服务该终端设备的网络设备，且该第二网络设备不属于该终端设备接入的移动网络系统。
上述技术方案，在认证授权流程中，通过终端设备向第一网络设备提供服务终端设备的、与终端设备不在同一个移动网络系统的第二网络设备的列表，使得第一网络设备在根据该列表中的一个第二网络设备的相关信息不能发现第二网络设备时，可以根据该列表中的其他第二网络设备的相关信息继续发现第二网络设备，从而减少由于核心网发现第二网络设备失败，而导致合法的终端设备无法进行认证授权的问题。
结合第七方面，在第七方面的某些实现方式中，该第十信息还包括该多个第二网络设备的相关信息的优先级信息，该第一网络设备按照优先级的顺序发现该第二网络设备。
第八方面，提供了一种发现服务实体的装置，包括：收发模块，用于接收第一信息，该第一信息包括第二网络设备的相关信息，该第二网络设备为该终端设备提供的待发现的 网络设备，且该第二网络设备不属于该第一网络设备所在的移动网络系统；处理模块，用于根据该第一信息进行针对该第二网络设备的发现处理；当针对该第二网络设备的发现处理失败时，该收发模块，还用于发送第二信息，该第二信息用于请求重新提供待发现的网络设备；该收发模块，还用于接收第三信息，该第三信息包括第五网络设备的相关信息，该第五网络设备是该终端设备提供的更新后的待发现的网络设备，且该第五网络设备不属于该第一网络设备所在的移动网络系统；该处理模块，还用于根据该第三信息进行针对该第五网络设备的发现处理。
上述技术方案，在认证授权流程中，当核心网发现服务终端设备的、与终端设备不在同一个移动网络系统的第二网络设备失败时，通过核心网侧设备指示终端设备更新待发现的网络设备的相关信息，从而减少由于核心网发现第三方实体失败，而导致合法的终端设备无法进行认证授权的问题。
结合第八方面，在第八方面的某些实现方式中，该第二信息包括第一指示信息，该第一指示信息指示更新该第一信息。
结合第八方面，在第八方面的某些实现方式中，该第二信息包括第二指示信息和第一原因值中的至少一个，其中，该第二指示信息指示该第一网络设备根据该第一信息不能发现该第二网络设备，该第一原因值指示该第一网络设备根据该第一信息不能发现该第二网络设备的原因。
第九方面，提供了一种发现服务实体的装置，包括：收发模块，用于发送第四信息，该第四信息包括第二网络设备的相关信息，该第二网络设备为该终端设备提供的待发现的网络设备，且该第二网络设备不属于该终端设备所在的移动网络系统；该收发模块，还用于接收第五信息，该第五信息用于请求该终端设备重新提供待发现的网络设备；该收发模块，还用于发送第六信息，该第六信息包括第五网络设备的相关信息，该第五网络设备是更新后的待发现的网络设备，且该第五网络设备不属于该终端设备所在的移动网络系统。
上述技术方案，在认证授权流程中，在终端设备向核心网发送服务终端设备的、与终端设备不在同一个移动网络系统的第二网络设备的相关信息之后，收到核心网发送的请求重新提供待发现的网络设备的相关信息的指示之后，向核心网发送第五网络设备的相关信息，通过终端设备在认证授权失败后及时向核心网更新待发现的网络设备的相关信息，从而减少由于核心网发现第三方实体失败，而导致合法的终端设备无法进行认证授权的问题。
结合第九方面，在第九方面的某些实现方式中，该装置还包括，处理模块，用于根据该第四信息确定该更新后的该第一信息。
结合第九方面，在第九方面的某些实现方式中，该第四信息包括第三指示信息，该第三指示信息指示该终端设备更新该第三信息。
结合第九方面，在第九方面的某些实现方式中，该第四信息包括第四指示信息和第二原因值中的至少一个，其中，该第四指示信息指示该第一网络设备根据该第三信息不能发现该第二网络设备，该第二原因值指示该第一网络设备根据该第三信息不能发现该第二网络设备的原因。
第十方面，提供了一种发现服务实体的装置，包括：收发模块，用于接收第二信息，该第二信息用于请求重新提供待发现的网络设备，该待发现的网络设备为终端设备提供的服务该终端设备的网络设备，且该待发现的网络设备不属于该第三网络设备所在的移动网 络系统；处理模块，用于根据该第二信息发送第五信息，该第五信息用于请求重新提供该待发现的网络设备；该收发模块，还用于接收第六信息，该第六信息包括该第五网络设备的相关信息，该第五网络设备是该终端设备提供的更新后的待发现的网络设备，且该第五网络设备不属于该第三网络设备所在的移动网络系统；该收发模块，还用于第三信息，该第三信息包括该第五网络设备的相关信息。
上述技术方案，在认证授权流程中，当核心网发现服务终端设备的、与终端设备不在同一个移动网络系统的第二网络设备失败时，通过核心网侧设备指示终端设备更新待发现的网络设备的相关信息，从而减少由于核心网发现第三方实体失败，而导致合法的终端设备无法进行认证授权的问题。
结合第十方面，在第十方面的某些实现方式中，该第二信息包括第一指示信息，该第一指示信息指示更新该第一信息。
结合第十方面，在第十方面的某些实现方式中，该第二信息包括第二指示信息和第一原因值中的至少一个，其中，该第二指示信息指示该第一网络设备根据该第一信息不能发现该第二网络设备，该第一原因值指示该第一网络设备根据该第一信息不能发现该第二网络设备的原因。
结合第十方面，在第十方面的某些实现方式中，该第四信息包括第三指示信息，该第三指示信息指示该终端设备更新该第三信息。
结合第十方面，在第十方面的某些实现方式中，该第四信息包括第四指示信息和第二原因值中的至少一个，其中，该第四指示信息指示该第一网络设备根据该第一信息不能发现该第二网络设备，该第二原因值指示该第一网络设备根据该第一信息不能发现该第二网络设备的原因。
第十一方面，提供了一种发现服务实体的装置，包括：收发模块，用于接收来自终端设备的第七信息，该第五信息包括第二网络设备的相关信息，该第二网络设备为服务该终端设备的网络设备，且该第二网络设备不属于该第一网络设备所在的移动网络系统；处理模块，用于根据该第七信息不能发现该第二网络设备；该收发模块，还用于向第四网络设备发送第八信息，该第八信息请求该第二网络设备的相关信息；该收发模块，还用于接收来自该第四网络设备的第九信息，该第九信息包括该第二网络设备的相关信息。
上述技术方案，在认证授权流程中，当核心网发现服务终端设备的、与终端设备不在同一个移动网络系统的第二网络设备失败时，通过核心网向第四网络设备请求新的第二网络设备的相关信息，从而减少由于核心网发现第二网络设备失败，而导致合法的终端设备无法进行认证授权的问题。
结合第十一方面，在第十一方面的某些实现方式中，该第八信息包括第五指示信息和第三原因值中的至少一个，其中，该第五指示信息指示该第一网络设备根据该第一信息不能发现该第二网络设备，该第三原因值指示该第一网络设备根据该第一信息不能发现该第二网络设备的原因。
结合第十一方面，在第十一方面的某些实现方式中，该第八信息包括该第七信息。
第十二方面，提供了一种发现服务实体的装置，包括：收发模块，用于接收来自该第一网络设备的第八信息，该第八信息请求第二网络设备的相关信息，该第二网络设备为服务该终端设备的网络设备，且该第二网络设备不属于该第一网络设备所在的移动通信系统； 处理模块，用于为该第一网络设备查询该第二网络设备的相关信息；该收发模块，还用于向该第一网络设备发送第九信息，该第九信息包括该第二网络设备的相关信息。
上述技术方案，在认证授权流程中，当核心网发现服务终端设备的、与终端设备不在同一个移动网络系统的第二网络设备失败时，通过核心网向第四网络设备请求新的第二网络设备的相关信息，从而减少由于核心网发现第二网络设备失败，而导致合法的终端设备无法进行认证授权的问题。
结合第十二方面，在第五方面的某些实现方式中，该第八信息包括第五指示信息和第三原因值中的至少一个，其中，该第五指示信息指示该第一网络设备根据该第一信息不能发现该第二网络设备，该第三原因值指示该第一网络设备根据该第一信息不能发现该第二网络设备的原因。
结合第十二方面，在第十二方面的某些实现方式中，或者该第八信息包括该第七信息。
第十三方面，提供了一种发现服务实体的装置，包括：收发模块，用于接收来自终端设备的第十信息，该第十信息包括第一列表，该第一列表包括至少一个第二网络设备的相关信息，每个该第二网络设备的相关信息用于发现一个该第二网络设备，该第二网络设备为服务该终端设备的网络设备，且该第二网络设备不属于该第一网络设备所在的移动网络系统；处理模块，用于根据该第十信息中的一个该第二网络设备的相关信息不能发现该第二网络设备；该处理模块，还用于根据该第十信息中的其他该第二网络设备的相关信息发现该第二网络设备。
上述技术方案，在认证授权流程中，通过终端设备向第一网络设备提供服务终端设备的、与终端设备不在同一个移动网络系统的第二网络设备的列表，使得第一网络设备在根据该列表中的一个第二网络设备的相关信息不能发现第二网络设备时，可以根据该列表中的其他第二网络设备的相关信息继续发现第二网络设备，从而减少由于核心网发现第二网络设备失败，而导致合法的终端设备无法进行认证授权的问题。
结合第十三方面，在第十三方面的某些实现方式中，该第十信息还包括该多个第二网络设备的相关信息的优先级信息，该第一网络设备按照优先级的顺序发现该第二网络设备。
第十四方面，提供了一种发现服务实体的装置，包括：收发模块，用于发送第十信息，该第十信息包括第一列表，该第一列表包括至少一个第二网络设备的相关信息，每个该第二网络设备的相关信息用于发现一个该第二网络设备，该第二网络设备为服务该终端设备的网络设备，且该第二网络设备不属于该终端设备接入的移动网络系统。
上述技术方案，在认证授权流程中，通过终端设备向第一网络设备提供服务终端设备的、与终端设备不在同一个移动网络系统的第二网络设备的列表，使得第一网络设备在根据该列表中的一个第二网络设备的相关信息不能发现第二网络设备时，可以根据该列表中的其他第二网络设备的相关信息继续发现第二网络设备，从而减少由于核心网发现第二网络设备失败，而导致合法的终端设备无法进行认证授权的问题。
结合第十四方面，在第十四方面的某些实现方式中，该第十信息还包括该多个第二网络设备的相关信息的优先级信息，该第一网络设备按照优先级的顺序发现该第二网络设备。
第十五方面，提供了一种通信装置，包括：处理器和存储器；该存储器，用于存储计算机程序；该处理器，用于执行该存储器中存储的计算机程序，以使得该通信装置执行第一方面至第七方面中任一方面该的方法和实施例。
第十六方面，提供了一种计算机可读存储介质，该计算机可读存储介质上存储有计算机程序，当该计算机程序在计算机上运行时，使得该计算机执行第一方面至第七方面中任一方面所述的方法和实施例。
第十七方面，提供了一种芯片系统，包括：处理器，用于从存储器中调用并运行计算机程序，使得安装有所述芯片系统地通信设备执行第一方面至第七方面中任一方面所述的方法和实施例。
第十八方面，提供了一种通信系统，该通信系统包括第一网络设备和终端设备，其中该第一网络设备用于执行第一方面和第二方面中任一方面所述的方法和实施例。
第十九方面，提供了一种通信系统，该通信系统包括第一网络设备、终端设备和第三网络设备，其中该第一网络设备用于执行第一方面至第三方面中任一方面所述的方法和实施例。
附图说明
图1示出了一种适用于本申请实施例的网络架构。
图2示出了另一种适用于本申请实施例的网络架构。
图3示出了本申请实施例适用的应用场景的一例的示意图。
图4示出了本申请的发现服务实体的方法的一例的示意性交互图。
图5示出了本申请的发现服务实体的方法的又一例的示意性交互图。
图6示出了本申请的发现服务实体的方法的又一例的示意性交互图。
图7示出了本申请的发现服务实体的方法的又一例的示意性交互图。
图8示出了本申请的发现服务实体的方法的又一例的示意性交互图。
图9示出了本申请的发现服务实体的方法的又一例的示意性交互图。
图10示出了本申请的发现服务实体的方法的又一例的示意性交互图。
图11示出了本申请的用于认证授权的通信装置的一例的示意性框图。
图12示出了本申请的用于认证授权的通信装置的又一例的示意性框图。
具体实施方式
下面将结合附图，对本申请中的技术方案进行描述。
本申请实施例提供的技术方案可以应用于各种通信系统，例如：全球移动通信(global system for mobile communications，GSM)系统、码分多址(code division multiple access，CDMA)系统、宽带码分多址(wideband code division multiple access，WCDMA)系统、通用分组无线业务(general packet radio service，GPRS)、长期演进(long term evolution，LTE)系统、LTE频分双工(frequency division duplex，FDD)系统、LTE时分双工(time division duplex，TDD)、通用移动通信系统(universal mobile telecommunication system，UMTS)、全球互联微波接入(worldwide interoperability for microwave access，WiMAX)通信系统、第五代(5th generation，5G)系统或新无线(new radio，NR)或者未来的3GPP系统等。
通常来说，传统的通信系统支持的连接数有限，也易于实现，然而，随着通信技术的发展，移动通信系统将不仅支持传统的通信，还将支持例如，设备到设备(device to device， D2D)通信，机器到机器(machine to machine，M2M)通信，机器类型通信(machine type communication，MTC)，车辆与万物(vehicle to everything，V2X)通信(也可以称为车辆网通信)，例如，车辆与车辆(vehicle to vehicle，V2V)通信(也可以称为车到车通信)、车辆与基础设施(vehicle to infrastructure，V2I)通信(也可以称为车到基础设施通信)，车辆与行人(vehicle to pedestrian，V2P)通信(也可以称为车到人通信)，车辆与网络(vehicle to network，V2N)通信(也可以称为车到网络通信)。
图1提供了一种网络架构，下面结合图1对该网络架构中可能涉及的各个网元分别进行说明。
1、用户设备(user equipment，UE)：可以称终端设备、终端、接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、无线通信设备、用户代理或用户装置。UE还可以是蜂窝电话、无绳电话、会话启动协议(session initiation protocol，SIP)电话、无线本地环路(wireless local loop，WLL)站、个人数字助理(personal digital assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备，5G网络中的终端设备或者未来演进的公用陆地移动通信网络(public land mobile network，PLMN)中或者非陆地网络(non-terrestrial networks，NTN)的终端设备等，还可以是端设备，逻辑实体，智能设备，如手机，智能终端等终端设备，或者服务器，网关，基站，控制器等通信设备，或者物联网设备，如传感器，电表，水表等物联网(internet of things，IoT)设备。还可以是具有通信功能的无人机(unmanned aerial vehicle或uncrewed aerial vehicle，UAV)。本申请实施例对此并不限定。
2、通用移动通信系统(universal mobile telecommunications system，UMTS)陆地无线接入网(UMTS terrestrial radio access network，UTRAN)：如第三代(3rd generation，3G)/第二代(2nd generation，2G)接入网。
3、全球移动通信系统(global system for mobile communication，GSM)/改进数据率GSM服务(enhanced data rate for GSM evolution，EDGE)陆地无线接入网(GSM/EDGE terrestrial radio access network，GERAN)：如3G/2G接入网。
4、演进的通用移动通信系统(evolved universal terrestrial radio access network，E-UTRAN)：如第四代(4th generation，4G)接入网。
5、服务网关(serving gateway，S-GW)实体：可以负责用户面处理，数据包的理由和转发等功能。
6、公共数据网(public data network，PDN)网关(PDN gateway，P-GW)实体：3GPP和非3GPP网络间的用户面数据链路锚点，可以负责管理3GPP和非3GPP间的数据路由。
7、移动性管理实体(mobility management entity，MME)：主要负责移动性管理、承载管理、用户的鉴权认证、S-GW和P-GW的选择等功能。
8、运营商的互联网协议(internet protocol，IP)服务(operator’s IP services)：例如可以为IP多媒体子系统(IP multimedia subsystem，IMS)，IMS为基于IP网络提供多媒体业务的通用网络架构；又如可以为分组交换服务(packet switching service，PSS)等。
9、策略与计费规则功能单元(policy and charging rules function，PCRF)：是业务数据流和IP承载资源的策略与计费控制策略决策点，它可以为策略与计费执行功能单元选 择及提供可用的策略和计费控制决策。
10、归属签约用户服务器(home subscriber server，HSS)：可以支持用于处理调用/会话的IMS网络实体的主要用户数据库，HSS可包括用户配置文件，执行用户的身份验证和授权，并可提供有关用户物理位置的信息。
11、服务通用分组无线服务技术(general packet radio service，GPRS)支持节点(serving GPRS support node，SGSN)：可以完成分组数据包的路由转发、移动性管理、会话管理、逻辑链路管理、鉴权和加密、话单产生和输出等功能。
在该网络架构中，LTE-Uu接口为终端与E-UTRAN之间的参考点；S1-U接口为E-UTRAN和S-GW实体之间的参考点；N5接口为S-GW实体和P-GW实体之间的参考点；SGi接口为P-GW实体和IMS之间的参考点；Rx接口为IMS和PCRF之间的参考点；Gx接口为P-GW实体和PCRF之间的参考点；控制平面接口S1-MME将MME与E-UTRAN相连，类似于UMTS网络中的无线网络层的控制部分等；S11接口为MME与S-GW实体之间的参考点；S12接口为UTRAN/GERAN与S-GW实体之间的参考点；S4接口为SGSN与S-GW实体之间的参考点；S6a接口为MME与HSS之间的参考点；S3接口为MME与SGSN之间的参考点。
图2提供了又一种网络架构，下面结合图2对该网络架构中可能涉及的各个网元分别进行说明。
1、UE：在上文中结合图1已介绍，此处为简洁，不再赘述。
2、接入网(access network，AN)：为特定区域的授权用户提供入网功能，并能够根据用户的级别，业务的需求等使用不同质量的传输隧道。接入网络可以为采用不同接入技术的接入网络。目前的无线接入技术有两种类型：3GPP接入技术(例如3G、4G或5G系统中采用的无线接入技术)和非第三代合作伙伴计划(non-3GPP)接入技术。3GPP接入技术是指符合3GPP标准规范的接入技术，采用3GPP接入技术的接入网络称为无线接入网络(radio access network，RAN)，其中，5G系统中的接入网设备称为下一代基站节点(next generation Node Base station，gNB)。非3GPP接入技术是指不符合3GPP标准规范的接入技术，例如，以wifi中的接入点(access point，AP)为代表的空口技术。
基于无线通信技术实现接入网络功能的接入网可以称为无线接入网(radio access network，RAN)。无线接入网能够管理无线资源，为终端提供接入服务，进而完成控制信号和用户数据在终端和核心网之间的转发。
无线接入网例如可以是基站(NodeB)、演进型基站(evolved NodeB，eNB或eNodeB)、5G移动通信系统中的基站(gNB)、未来移动通信系统中的基站或WiFi系统中的AP等，还可以是云无线接入网络(cloud radio access network，CRAN)场景下的无线控制器，或者该接入网设备可以为中继站、接入点、车载设备、可穿戴设备以及未来5G网络中的网络设备或者未来演进的PLMN网络中的网络设备等。本申请的实施例对无线接入网设备所采用的具体技术和具体设备形态不做限定。
3、接入和移动管理功能(access and mobility management function，AMF)实体：主要用于移动性管理和接入管理等，可以用于实现移动性管理实体(mobility management entity，MME)功能中除会话管理之外的其它功能，例如，合法监听、或接入授权(或鉴权)等功能。
4、会话管理功能(session management function，SMF)实体：主要用于会话管理、UE的IP地址分配和管理、选择可管理用户平面功能、策略控制、或收费功能接口的终结点以及下行数据通知等。
5、用户平面功能(user plane function，UPF)实体：即，数据面网关。可用于分组路由和转发、或用户面数据的服务质量(quality of service，QoS)处理等。用户数据可通过该网元接入到数据网络(data network，DN)。在本申请实施例中，可用于实现用户面网关的功能。
6、数据网络(DN)：用于提供传输数据的网络。例如，运营商业务的网络、因特(Internet)网、第三方的业务网络等。
7、认证服务功能(authentication server function，AUSF)实体：主要用于用户鉴权等。
8、网络开放功能(network exposure function，NEF)实体：用于安全地向外部开放由3GPP网络功能提供的业务和能力等。
9、网络存储功能(network function(NF)repository function，NRF)实体：用于保存网络功能实体以及其提供服务的描述信息，以及支持服务发现，网元实体发现等。
10、策略控制功能(policy control function，PCF)实体：用于指导网络行为的统一策略框架，为控制平面功能网元(例如AMF，SMF网元等)提供策略规则信息等。
11、统一数据管理(unified data management，UDM)实体：用于处理用户标识、接入鉴权、注册、或移动性管理等。
12、应用功能(application function，AF)实体：用于进行应用影响的数据路由，接入网络开放功能网元，或，与策略框架交互进行策略控制等。例如可以是V2X应用服务器，V2X应用使能服务器，还可以是无人机服务器(可以包括无人机监管服务器，或无人机应用业务服务器)。
在图2所示的网络架构中，N1接口为终端与AMF实体之间的参考点；N2接口为AN和AMF实体的参考点，用于非接入层(non-access stratum，NAS)消息的发送等；N3接口为(R)AN和UPF实体之间的参考点，用于传输用户面的数据等；N4接口为SMF实体和UPF实体之间的参考点，用于传输例如N3连接的隧道标识信息，数据缓存指示信息，以及下行数据通知消息等信息；N6接口为UPF实体和DN之间的参考点，用于传输用户面的数据等。
应理解，上述图1、图2所示的网络架构可以应用于本申请实施例，此外，适用本申请实施例的网络架构并不局限于此，任何能够实现上述各个网元的功能的网络架构都适用于本申请实施例。
还应理解，图1或图2中所示的AMF实体、SMF实体、UPF实体、NEF实体、AUSF实体、NRF实体、PCF实体、UDM实体可以理解为核心网中用于实现不同功能的网元，例如可以按需组合成网络切片。这些核心网网元可以各自独立的设备，也可以集成于同一设备中实现不同的功能，本申请对此不做限定。需要说明的是，上述“网元”也可以称为实体、设备、装置或模块等，本申请并未特别限定。
还应理解，上述命名仅为用于区分不同的功能，并不代表这些网元分别为独立的物理设备，本申请对于上述网元的具体形态不作限定，例如，可以集成在同一个物理设备中，也可以分别是不同的物理设备。此外，上述命名仅为便于区分不同的功能，而不应对本申 请构成任何限定，本申请并不排除在5G网络以及未来其它的网络中采用其他命名的可能。例如，在6G网络中，上述各个网元中的部分或全部可以沿用5G中的术语，也可能采用其他名称等。在此进行统一说明，以下不再赘述。
还应理解，图1或图2中的各个网元之间的接口名称只是一个示例，具体实现中接口的名称可能为其他的名称，本申请对此不作具体限定。此外，上述各个网元之间的所传输的消息(或信令)的名称也仅仅是一个示例，对消息本身的功能不构成任何限定。
图3示出了本申请实施例的应用场景示意图。如图3所示，无人机系统300可以与带有无人机系统流量管理实体UTM303的网络系统进行信息交互和无线通信。例如，无人机控制器301或无人机302可以与接入网(radio access network，RAN)304、核心网(core network，CN)305进行信息交互，还可以通过接入网304或核心网305与UTM303进行信息交互；无人机控制器301还可以通过接入网304或核心网305与无人机302进行信息交互，还可以通过UTM303与无人机302进行信息交互。
应理解，无人机控制器301与无人机302可以处于同一接入网或核心网中，也可以处于不同的接入网或核心网中，本申请实施例对此并不限定。
1、无人机控制器(unmanned aerial vehicle controller，UAVC)301：用于对无人机302进行控制，例如控制无人机的飞行状态或飞行动作等。无人机控制器可以是智能手机、平板、手提电脑、智能手表或智能遥控器、传统遥控器、专用远程控制器等，还可以是手环、指环、手套、臂带、手表等可用于手势控制无人机的装置，还可以是头套等可用于意念控制无人机的头戴设备，还可以是智能夹克、外套等可用于用户身体动作控制无人机的装置等。
应理解，本申请对无人机控制器的具体类型不作限定。随着智能化的发展，具备无人机控制器功能的设备的名称和形式可能会有所不同。为方便描述，本申请所有实施例中，上述能够具备无人机控制器功能或能够控制无人机的装置统称为无人机控制器。
无人机控制器301可以对无人机302的飞行状态进行控制，例如无人机控制器可以控制无人机的方向、副翼、升降、倾斜、速度、油门、襟翼等，还可以控制无人机的转弯、爬升、俯冲、横滚、悬停、起飞、落地等动作，本申请实施例对此不做任何限定。
2、无人机(unmanned aerial vehicle，UAV)302：或者，也可以是(uncrewed aerial vehicle，UAV)，还可以称为无人驾驶飞机、空中机器人，是利用无线电遥控设备和自备的程序控制装置的不载人飞机，可以在无人驾驶的条件下完成空中飞行任务和各种负载任务。本申请实施例中的无人机可以是无人直升机、固定翼机、多旋翼飞行器、无人飞艇、无人伞翼机；还可以包括临近空间飞行器，例如平流层飞艇、高空气球、太阳能无人机等；还可以是四轴、六轴、单轴、矢量控制等多种形式的无人机。本申请实施例中的无人机可以用于军事、工业、民用、农业、建筑、影视、环保等领域以及用到无人机作业的特种行业，例如用无人机来进行军事侦察、巡视、航拍、环境监测、边防监控、送快递、电力巡检、确权、防汛抗旱、灾后救援等等。本申请实施例对无人机的名称和形式并不限定。
应理解，本文对无人机的具体类型不作限定。随着智能化的发展，为应用于不同的场景或完成不同的空中飞行任务，具备无人驾驶飞机功能的设备的名称可能会有所不同。为方便描述，本申请所有实施例中，上述能够具备无人驾驶飞机功能的装置统称为无人机。
无人机302可以配备有多种传感器或功能模块，例如陀螺仪(飞行姿态感知)、加速 计、地磁感应、气压传感器(悬停高度粗略控制)、超声波传感器(低空高度精确控制或避障)、光流传感器(悬停水平位置精确确定)、全球定位系统(global positioning system，GPS)模块(水平位置高度粗略定位)、控制电路、指南针等，通过采集无人机的角速率、姿态、位置、加速度、高度和空速等，能够实现自动保持无人机的正常飞行姿态。应理解，上述无人机配置的模块或硬件名称仅仅是一个示例，在具体实现中，各个功能模块还可以有其他的名称，本申请实施例对此并不限定。本申请实施例中的无人机还可以具有更多或更少的功能模块，也可以实现更多或更少的功能等，本申请实施例对此也不做任何限定。
还应理解，无人机系统(unmanned aerial system，UAS)300可以包括一个或多个无人机控制器301和一个或多个无人机302。例如，一个无人机控制器可以控制一个或多个无人机，一个无人机也可以被一个或多个无人机控制器控制，多个无人机控制器也可以协同控制多个无人机，本申请实施例对此不做限定。
无人机系统300中的无人机302可以是上文提到的任意一种或多种类型，无人机控制器301也可以是上文提到的任意一种或多种类型，本申请实施例对此不做任何限定。除了上述介绍的网元之外，本申请中还包括：
无人机系统服务提供商(UAS service supplier，USS)：通过向无人机的运营者或飞行员提供服务，以满足无人机运营要求，为安全、高效地使用空域提供支持的实体。USS可以提供任何功能子集以满足提供商的业务目标。需要说明的是，该命名仅为便于表示其功能，而不应对本申请构成任何限定，本申请并不排除在以后的标准中采用其他命名的可能。
无人机流量管理(unmanned aerial system traffic management，UTM)：一套用于管理一系列自动设备操作的功能和服务(例如无人机认证、无人机业务授权、无人机策略管理、空域无人机流量控制)。需要说明的是，该命名仅为便于表示其功能，而不应对本申请构成任何限定，本申请并不排除在以后的标准中采用其他命名的可能。
此外，USS和UTM的实体可以是一个实体，可以是包含关系，也可以是并列关系，本申请对此不做限定。在本申请实施例中，USS、UTM、USS/UTM指的是同一个实体，其名称可能是服务实体等。
第三方授权实体(third party authorized entity，TPAE)：可以识别和/或跟踪UAV，在一定范围内检查是否有非法的UAV。
无人机应用功能网元(UAS application function，UAS AF)、无人机飞行使能子系统(UAV flight enablement subsystem，UFES)。UAS AF或UFES为USS或UTM提供一个接入3GPP系统服务的单独的接口，执行USS或UTM下发的命令，负责3GPP系统内部与外部的信息传输。需要说明的是，该命名仅为便于表示其功能，而不应对本申请构成任何限定，本申请并不排除在以后的标准中采用其他命名的可能。此外，UAS AF或UFES可以是现有的网元，如就是NEF/SCEF，或新的网元，也可能与NEF或业务能力开放功能(service capability exposure function，SCEF)共同部署。此外，UAS AF和UFES的实体可以是一个实体，可以是包含关系，也可以是并列关系，本申请对此不做限定。
近年来，无人机应用逐渐普及。特别是在民用领域，从个人娱乐的小型无人机，到各种各样的带来经济价值的无人机，种类繁多，如植保无人机、救灾无人机、消防无人机、快递无人机等等。然而无人机在给人们带来各种经济利益和娱乐消遣的同时，也带来了如 何管理无人机的问题。
适用于远程控制场景的无人机，对于联网的需求越来越多。目前，为了更好地管理无人机，3GPP系统在整个无人机领域的应用也越来越受到重视。以5G系统为例，在近期的标准会议中，3GPP正在研究联网无人机，系统通过网络改善对于无人机的管理。在3GPP的无人机系统架构中，无人机和无人机控制器分别接入3GPP网络，两者通过3GPP网络进行通信。具体地，无人机在联网后，可以获得UAS服务，如无人机控制器可以通过网络远程控制无人机的飞行，无人机可以通过网络将数据信息发送给云端，无人机还可以通过网络获得及时的避障辅助等等。其中，为了联网进行控制无人机的飞行，无人机会请求建立会话与其控制器连接，该会话被称为命令和控制(command and control，C2)通信相关的会话。
无人机联网需要进行无人机自身的认证授权，如果需要建立C2通信相关的会话，还需要进行C2通信的认证授权，这些认证授权需要在一个第三方实体中进行，即USS或UTM。目前，UAV认证授权可以在注册流程中执行，也可以在协议数据单元(protocol data unit，PDU)会话建立/修改过程中执行。
需要说明的是，本申请中的UAV认证授权，包括跟UAV相关的认证授权，例如UAV自身是否合法(UAV的认证授权)、UAV的飞行计划是否合法(飞行路径的认证授权)、UAV是否可以和特定的UAVC通信(配对的认证授权)等等，或者，还有可能包括其他与UAV相关的认证授权，本申请对此不做限定。
为了将无人机的授权认证请求发送给USS/UTM，3GPP系统需要进行USS/UTM的发现。目前，对于3GPP系统未能成功发现USS/UTM而导致无法进行认证授权的场景，尚没有对应的解决方案。因此，本申请希望提供针对上述问题的解决方案。
下面将结合附图详细说明本申请实施例。
下面结合图4，对本申请实施例的发现服务实体的方法400进行详细说明。图4是本申请的方法400的示意性交互图。
S401，终端设备向第三网络设备发送第四信息，该第四信息包括第二网络设备的相关信息，该第二网络设备为该终端设备提供的待发现的网络设备，且该第二网络设备不属于该终端设备所在的移动网络系统。
这里的终端设备向第三网络设备发送第四信息也可以理解为，终端设备通过其他网络设备向第三网络设备发送第四信息。需要说明的是，终端设备向其他网络设备发送的信息可能与其他网络设备向第三网络设备发送的信息的信息类型不一样，也可能一样，但上述所有信息都包含第四信息。
这里的移动网络系统也可以理解为移动网络运营商的网络系统，例如PLMN，或者也可以称为3GPP系统，本申请对于该移动网络系统的名称不做限定。这里的该第二网络设备不属于该终端设备所在的移动网络系统，也可以理解为第二网络设备不属于任何一个运营商。需要说明的是，在某些场景下，该第二网络设备可以称为第三方实体，还可以称为服务实体，示例性地，在终端设备是联网无人机的场景下，该第二网络设备可以是USS、UTM或USS/UTM，本申请对于该第二网络设备的名称不做限定。
作为一个示例，这里的第三网络设备可以SMF或AMF。
S402，第三网络设备向第一网络设备发送第一信息，该第一信息包括第二网络设备的 相关信息，该第二网络设备为该终端设备提供的待发现的网络设备，且该第二网络设备不属于该第一网络设备所在的移动网络系统。
这里的第三网络设备向第一网络设备发送第一信息，也可以理解为第三网络设备通过其他设备向第一网络设备发送第一信息。需要说明的是，第三网络设备向其他设备发现的信息可能与其他网络设备向第一网络设备发送的信息的信息类型不一样，也可能一样，本申请对此不做限定。
需要说明的是，S401和S402的目的是为了将来自终端设备的第二网络设备的相关信息发送给第一网络设备，在具体实现中，还有可能直接由终端设备将该相关信息发送给第一网络设备，或者也有可能由终端设备通过第三网络设备和其他网络设备发送给第一网络设备，本申请对此不做限定。在具体实现中，第三信息和第一信息可能为同一信息，本申请对此不做限定。
S403，第一网络设备根据该第一信息进行针对该第二网络设备的发现处理。
需要说明的是，本申请中提到的“发现”指的是根据第二网络设备的相关信息确定服务终端设备的第二网络设备。示例的，第二网络设备的相关信息可以是第二网络设备为其分配的标识符，可以通过解析该标识符可以得到第二网络设备的地址，从而确定第二网络设备。除了“发现”，还可以称为“确定”或“解析”等，本申请对此不做限定。
S404，当针对该第二网络设备的发现处理失败时，该第一网络设备发送第二信息，该第二信息用于请求重新提供待发现的网络设备。
或者，“对该第二网络设备的发现处理失败”也可以理解为未能成功发现第二网络设备，或者，发现第二网络设备失败。导致“对该第二网络设备的发现处理失败”的原因可能有多种，具体可参见方法700中步骤S703。
S405、第三网络设备向终端设备发送第五信息，该第五信息用于请求重新提供该待发现的网络设备。
需要说明的是，S404和S405的目的是为了将来自第一网络设备指示终端设备更新待发现的网络设备的信息发送给终端设备，在具体实现中，还有可能直接由第一网络设备将该信息发给终端设备，或者也可以可能由第一网络设备通过第三网络设备和/或其他网络设备发送给终端设备，本申请对此不做限定。在具体实现中，第二信息和第五信息可能为同一信息，本申请对此不做限定。
S406，终端设备向第三网络设备发送第六信息，该第六信息包括该第五网络设备的相关信息，该第五网络设备是该终端设备提供的更新后的待发现的网络设备，且该第五网络设备不属于该第三网络设备所在的移动网络系统。
S407，第三网络设备向第一网络设备发送第三信息，该第三信息包括该第五网络设备的相关信息。
具体地，第三网络设备根据上述第六信息向第一网络设备发送第三信息。
需要说明的是，S406和S407的目的是为了将来自终端设备的第五网络设备的相关信息发送给第一网络设备，在具体实现中，还有可能直接由终端设备将第五网络设备的相关信息发给第一网络设备，或者也可以可能由终端设备通过第三网络设备和/或其他网络设备发送给第一网络设备，本申请对此不做限定。
本申请实施例，在认证授权流程中，当核心网发现服务终端设备的、与终端设备不在 同一个移动网络系统的第二网络设备失败时，通过核心网侧设备指示终端设备更新待发现的网络设备的相关信息，从而减少由于核心网发现第三方实体失败，而导致合法的终端设备无法进行认证授权的问题。
下面结合图5，对本申请实施例的发现服务实体的方法500进行详细说明。图5是本申请的方法500的示意性交互图。
S501，终端设备向第一网络设备发送第五信息，该第五信息包括第二网络设备的相关信息，该第二网络设备为服务该终端设备的网络设备，且该第二网络设备不属于该第一网络设备所在的移动网络系统。
S502，第一网络设备根据第七信息不能发现第二网络设备。
或者，“不能发现第二网络设备”也可以理解为未能成功发现第二网络设备，或者，发现第二网络设备失败。导致“不能发现第二网络设备”的原因可能有多种，具体可参见方法700中步骤S703。
S503，第一网络设备向第四网络设备发送第八信息，该第八信息请求该第二网络设备的相关信息。
应理解，第一网络设备根据终端设备提供的第二网络设备的相关信息不能发现第二网络设备，因此向第四网络设备请求其他的第二网络设备的相关信息。
S504，第四网络设备接收到第八信息后，查询第二网络设备的相关信息。
应理解，该第四网络设备具备的功能可以仅仅是能够查询第二网络设备的相关信息，或者该第四网络设备具备的功能也可以包括第二网络设备的功能。第四网络设备具备不同功能的具体实现方式参见方法900中对于“第四网络设备”的描述。
S505，第四网络设备向第一网络设备发送第九信息，该第九信息包括该第二网络设备的相关信息。
如果第四网络设备查询到第二网络设备的相关信息，则将该相关信息发送给第一网络设备，具体实施方式参见方法900中的S905的可能的情况一；如果第四网络设备没有查询到第二网络设备的相关信息，具体处理方式参见方法900中的S905的可能的情况二。
本申请实施例，在认证授权流程中，当核心网发现服务终端设备的、与终端设备不在同一个移动网络系统的第二网络设备失败时，通过核心网向第四网络设备请求新的第二网络设备的相关信息，从而减少由于核心网发现第二网络设备失败，而导致合法的终端设备无法进行认证授权的问题。
下面结合图6，对本申请实施例的发现服务实体的方法600进行详细说明。图6是本申请的方法600的示意性交互图。
S601，终端设备向第一网络设备发送第八信息，该第八信息包括第一列表，该第一列表包括至少一个第二网络设备的相关信息，每个该第二网络设备的相关信息用于发现一个该第二网络设备，该第二网络设备为服务该终端设备的网络设备，且该第二网络设备不属于该第一网络设备所在的移动网络系统。
需要说明的是，对于终端设备向第一网络设备发送第八信息，还可以理解为终端设备通过其他设备将第八信息发送给第一网络设备，本申请对此不做限定。
S602，该第一网络设备根据该第十信息中的一个该第二网络设备的相关信息不能发现该第二网络设备。
S603，该第一网络设备根据该第十信息中的其他该第二网络设备的相关信息发现该第二网络设备。
本申请实施例，在认证授权流程中，通过终端设备向第一网络设备提供服务终端设备的、与终端设备不在同一个移动网络系统的第二网络设备的列表，使得第一网络设备在根据该列表中的一个第二网络设备的相关信息不能发现第二网络设备时，可以根据该列表中的其他第二网络设备的相关信息继续发现第二网络设备，从而减少由于核心网发现第二网络设备失败，而导致合法的终端设备无法进行认证授权的问题。
需要说明的是，上述方法400、500、600中的方法可以单独实施，也可以将其中的两个或三个方法组合实施，本申请对此并不做限定。
下面结合图7，对本申请实施例的发现服务实体的方法700进行详细说明。图7是本申请的方法700的示意性交互图。
需要说明的是，为了方便，本申请中的实施例均以5G通信系统为例进行说明，而本申请的实施例还可以应用于4G或者未来的通信系统，例如本申请实施例中的5G的注册流程还可以是4G的附着流程，5G的PDU会话建立/修改流程还可以是4G的PDN连接建立/修改流程，本申请对此不做限定。
S701，UE执行注册流程。
应理解，AMF检查UE是否具有航空签约(aerial subscriptions)，若UE具有航空签约，则AMF会为UE进一步向USS/UTM请求UAV认证授权。在成功进行UAV认证授权之前，UE不允许建立用于命令和控制(command and control,C2)通信相关的会话。
UE在注册流程中会向AMF发送注册请求消息。为了发现服务UE的USS/UTM，UE在注册请求消息中包含服务UE的USS/UTM的相关信息。
需要说明的是，服务UE的USS/UTM的相关信息，可以包含航空管理部门分配的UAV标识(CAA-Level UAV ID)、USS/UTM地址或全限定域名(fully qualified domain name，FQDN)中的一种或多种，还可以是其他信息，如飞行授权标识符(flight authorization id)，本申请对此不做限定。
这里的CAA-Level UAV ID是用于唯一标识UAV的信息，可以是USS/UTM独立分配的，或者，可以是3GPP系统辅助USS/UTM分配的，或者，也可以是通过其他方式分配的。在本申请中，CAA-Level UAV ID是用来发现USS/UTM的，即通过解析CAA-Level UAV ID可以确定服务UAV的USS/UTM信息。但本申请对该标识的分配方式和具体组成方式不做限定。
S702，AMF向UFES发送UAV认证授权请求消息，消息中包含上述用于发现USS/UTM的信息。
需要说明的是，本申请中的网元UFES代指3GPP系统中向USS/UTM开放接口的网元，它可能是现有的网元，如NEF，或者，也可能是一种新的网元，本申请对此不做限定。
S703，UFES根据UE提供的服务UE的USS/UTM的相关信息确定服务UE的USS/UTM，UFES根据该相关信息确定发现USS/UTM失败。
需要说明的是，发现USS/UTM失败的原因可能有很多，包括但不限于如下几种可能的原因：
可能的原因一，UFES根据航空管理部门分配的UAV标识解析确定服务UE的 USS/UTM，若根据该UAV标识无法解析出格式有效的USS/UTM信息或解析出的USS/UTM信息的格式有效但无法连接，则UFES确定发现USS/UTM失败。
可能的原因二，UFES根据UE提供的USS/UTM地址或FQDN确定服务UE的USS/UTM，若确定的USS/UTM无法连接，则UFES确定发现USS/UTM失败。
可能的原因三，UFES中存储有允许使用的或不允许使用的USS/UTM列表，若UFES确定的USS/UTM(解析CAA Level UAV ID或USS/UTM地址等方式确定)不在允许的USS/UTM列表中，则UFES确定发现USS/UTM失败。
可能的原因四，USS/UTM服务UE有地点和/或时间的限制，若UFES与USS/UTM通信后获知服务UE的地点和/或时间失效，即UAV提供的USS/UTM不再服务该UAV，则UFES确定发现USS/UTM失败。作为一个示例，USS/UTM与UE之前签订了协议，协议约定仅在某个区域范围和/或某个时间范围内服务该UE，一旦当前UE所处的区域和/或时间不在上述范围内，即表示该服务已失效。换句话说，每个USS/UTM的服务能力有限，它必须事先规划好在某个时间点服务某个区域的某些UAV，如果在错误的时间和/或地点找它授权，USS/UTM则不会提供服务。
需要注意的是，上述场景并不意味着授权失败，在上述场景中UAV可能是合法的。
除此之外，还可能因为其他原因发现USS/UTM失败，如因UFES和USS/UTM之间因没有信任关系而无法连接，本申请对此不做限定。
S704，UFES向AMF回复UAV认证授权响应消息，消息中包含USS/UTM发现失败指示和/或具体的USS/UTM发现失败原因。
作为一个示例，消息中包含的是具体的USS/UTM发现失败原因，可以是上述的几种失败原因，即UAV标识解析失败、USS/UTM无法连接、USS/UTM不在允许的USS/UTM列表中或USS/UTM不再服务该UE等。
AMF在收到USS/UTM发现失败的指示后，有多种方式进行处理，如下文的S705a和S706a，或者，S705b和S706b。
S705a，AMF向UE发送USS/UTM信息更新请求消息，消息用于请求UE提供新的用于发现USS/UTM的信息。可选的，消息中包含USS/UTM发现失败指示，和/或上述USS/UTM发现失败的原因。
S706a，UE向AMF发送USS/UTM信息更新响应消息。
可能的情况一，若UE中有新的服务UE的USS/UTM的相关信息，则在收到更新请求消息后，将新的服务UE的USS/UTM的相关信息包含在响应消息中。
作为一个示例，这里的服务UE的USS/UTM的相关信息可以是一个服务UE的USS/UTM的相关信息，也可以是多个服务UE的USS/UTM的相关信息，即备选的服务UE的USS/UTM可以是一个或多个。
可能的情况二，若UE中没有服务UE的USS/UTM的相关信息，则在收到更新请求消息后，在响应消息中指示无可用的新的服务UE的USS/UTM的相关信息，在这种场景下，后续步骤不再执行。
S705b，AMF在配置更新命令消息中指示发现USS/UTM失败。
作为一种示例，该配置更新消息中包含具体的发现USS/UTM失败的原因。
S706b，UE执行移动注册更新流程，并在注册请求消息中包含新的服务UE的 USS/UTM的相关信息。
应理解，在执行S705b和S706b时，UE可以立即向网络侧返回新的用于发现USS/UTM的信息，也可以不立即向网络侧返回该信息。示例性地，S705b和S706b可适用于UE需要通过线下或应用面获取新的用于发现USS/UTM的信息等场景，具体地，步骤S705b和S706b可以相隔较长时间，中间可能包含其他流程。
除了S705a和S706a，或者，S705b和S706b之外，还可以有其他的处理方式。
作为一个示例，AMF在收到USS/UTM发现失败的指示后，向UE发送去注册请求消息，可选的，该注册请求消息中包含去注册原因值，即USS/UTM发现失败。
作为一个示例，AMF在配置更新命令消息中包含USS/UTM发现失败指示，UE在确定没有新的用于发现USS/UTM的信息后，向AMF发送去注册请求，可选的，该注册请求消息中包含去注册原因值，即无可用的新的服务UE的USS/UTM的相关信息。
S707、AMF再次向UFES发送UAV认证授权请求消息，其中包含新的服务UE的USS/UTM的相关信息。
S708、UFES根据新的服务UE的USS/UTM的相关信息发现USS/UTM。
S709、如果在步骤S708中UFES确定发现USS/UTM失败，则可能需要重复执行步骤S704至S708，直到成功发现USS/UTM。如果在步骤S708中成功发现USS/UTM，则不执行步骤S709。
S710，UFES向USS/UTM发送UAV认证授权请求消息。
S711，USS/UTM向UFES回应UAV认证授权响应，其中包含授权结果。
S712，UFES将UAV认证授权响应转发给AMF。
S713，AMF向UE发送配置更新命令消息，其中指示UAV的授权结果。
本申请实施例，在注册流程后的UAV认证授权流程中，当核心网发现USS/UTM失败时，通过核心网侧设备指示UE更新服务UE的USS/UTM的相关信息，具体地，由AMF请求UE提供新的服务UE的USS/UTM的相关信息，或者由AMF向UE指示发现USS/UTM失败，从而减少由于核心网发现USS/UTM失败，而导致的合法的UE无法进行UAV认证授权的问题。
下面结合图8，对本申请实施例的发现服务实体的方法800进行详细说明。图8是本申请的方法800的示意性交互图。
S801，UE执行注册流程。
S802，UE可能执行UAV认证授权流程，即方法700中的步骤S702至S713。
需要说明的是，步骤S802可能执行，可能不执行，而不执行步骤S802时该方法800又适用于多种场景。
情况一，执行步骤S802：
UAV认证授权流程在注册流程中执行。
情况二，不执行步骤S802：
UAV认证授权流程在PDU会话建立流程中执行，或者，UAV认证授权流程在PDU会话修改流程中执行，对应的PDU会话建立请求则为PDU会话修改请求，对应的PDU会话建立接受则为PDU会话修改命令，这里以PDU会话修改流程为例，本申请对此不做限定。
可能的场景一，若UAV与USS/UTM之间通信的会话和UAV与UAVC之间C2通信的会话是相同的会话，则在PDU会话建立流程中，同时进行UAV认证授权和C2通信认证授权，下述所有流程中提到的C2通信认证授权可以替换为UAV认证授权和/或C2通信认证授权。
可能的场景二，若UAV与USS/UTM之间通信的会话和UAV与UAVC之间C2通信的会话是不同的会话，则在两个PDU会话建立流程中，独立进行UAV认证授权和C2通信认证授权。下述所有流程相当于需要执行两遍，一遍是用于UAV与USS/UTM之间建立的会话，此时下述所有流程中提到的C2通信认证授权需要替换为UAV认证授权；一遍是用于UAV与UAVC之间建立的会话。
还可能有其他的场景，若UAV与USS/UTM之间通信的会话和UAV与UAVC之间C2通信的会话是不同的会话，在UAV与USS/UTM建立通信会话时同时进行UAV认证授权和C2通信认证授权，本申请对此不做限定。
需要说明的是，UAV认证授权在注册流程中执行，还是在PDU会话建立流程中执行，以及UAV与USS/UTM之间通信的会话和UAV与UAVC之间通信的会话是相同的会话，或者UAV与USS/UTM之间通信的会话和UAV与UAVC之间通信的会话是不同的会话，本申请对此不做限定。
S803、UE向SMF发起PDU会话建立请求。
S804、SMF确定需要进行C2通信认证授权，则向UFES发起C2通信认证授权请求消息，其中包含用于发现USS/UTM的信息。
S805，与方法700中的步骤S703一致。
S806，UFES向SMF回复C2通信认证授权响应消息，其中，该C2通信认证授权响应消息中包含的内容与方法700中的S704中一致。
SMF在收到USS/UTM发现失败的指示后，有多种方式进行处理，如下文的S807a至S810a，或者，S807b和S808b。
S807a，SMF在收到USS/UTM发现失败指示后，向AMF发送USS/UTM发现失败指示。
S808a至S809a与方法700中的S705a至S706a一致。
S810a，AMF在收到USS/UTM信息更新响应后，向SMF发送USS/UTM发现失败指示，将收到的新的服务UE的USS/UTM的相关信息发送给SMF。
S807b，SMF向UE发送PDU会话建立接受消息，该PDU会话建立接受消息中包含USS/UTM发现失败指示。
S808b，UE发起PDU会话建立/修改请求，并在消息中包含新的服务UE的USS/UTM的相关信息。
应理解，在执行S807b和S808b时，UE可以立即向网络侧返回新的服务UE的USS/UTM的相关信息，也可以不立即向网络侧返回该信息。示例性地，S807b和S808b可适用于UE需要通过线下或应用面获取新的用于发现USS/UTM的信息等场景，具体地，步骤S807b和S808b可以相隔较长时间，中间可能包含其他流程。
除了上述S807a至S810a，或者，S807b和S808b之外，还可以有其他的处理方式。
作为一个示例，SMF在收到USS/UTM发现失败的指示后，向UE发送PDU会话建 立拒绝消息。可选的，该PDU会话建立拒绝消息可以包括拒绝原因值，示例性的，该拒绝原因值可以是USS/UTM发现失败。
作为一个示例，SMF在PDU会话接受消息中包含USS发现失败指示，UE在确定没有新的用于发现USS/UTM的信息后，向SMF发送会话释放请求，可选的，其中包含去注册原因值，即无可用的新的发现USS/UTM的信息。
S811，SMF再次向UFES发送C2通信认证授权请求消息，其中包含新的用于发现USS/UTM的信息。
S812，UFES根据新的用于发现USS/UTM的信息发现USS/UTM。
S813，若在步骤S812中UFES确定USS/UTM发现失败，则可能需要重复执行步骤S806至S812。如果在步骤S812中成功发现USS/UTM，则不执行步骤S813。
S814，UFES在确定用于服务UE的USS/UTM后，向USS/UTM发送C2通信认证授权请求消息。
S815，USS/UTM向UFES回应C2通信认证授权响应，其中包含授权结果。
S816，UFES在收到C2通信认证授权响应后，将其转发给SMF。
S817，SMF向UE发送PDU会话建立/修改响应消息，其中指示UAV的授权结果。
本申请实施例，在PDU会话建立或修改过程中的UAV和/或C2通信认证授权请求过程中，当核心网发现USS/UTM失败时，通过核心网侧设备指示UE更新服务UE的USS/UTM的相关信息，具体地，由SMF触发AMF向UE发起USS/UTM的信息更新请求，或者SMF向UE发起PDU会话建立请求，并在其中指示发现UDD/UTM失败，从而减少由于核心网发现USS/UTM失败，而导致的合法的UE无法进行UAV认证授权的问题。
下面结合图9，对本申请实施例的发现服务实体的方法900进行详细说明。图9是本申请的方法900的示意性交互图。
S901，UE执行注册流程。
S902，UAV认证授权流程。在该流程中，UFES收到了授权认证请求消息，消息中包含了用于发现USS/UTM的信息。
需要说明的是，步骤S902中的认证授权流程可以是方法700中步骤S702或者方法800中步骤S803-S804，也可以是其他的实现方式，本实施例对此不做限定。
S903，与方法700中的步骤S703一致。
S904，UFES向一个第四网络设备发送USS/UTM发现请求消息，请求消息用于请求第四网络设备提供服务UE的USS/UTM的相关信息。
应理解，UFES存储了一个第四网络设备的信息，该第四网络设备可以用于发现USS/UTM。在UFES根据UE提供的服务UE的USS/UTM的相关信息确定不能发现服务UE的USS/UTM时，会执行步骤S904。
示例性地，该请求消息中可以包括UE的信息、UE提供的服务UE的USS/UTM的相关信息中的至少一个。
或者，示例性地，该请求消息中可以包括第一指示信息，该指示信息指示USS/UTM发现失败。
S905，第四网络设备向UFES提供USS/UTM发现响应消息，消息中包含USS/UTM 的信息。
关于消息中包含的USS/UTM的信息，包括多种不同的情况。
可能的情况一，该第四网络设备为UE查询到了可以服务UE的USS/UTM，则将查询到的服务UE的USS/UTM的相关信息通过USS/UTM发现响应消息发送给UFES。
需要说明的是，这里的服务UE的USS/UTM的相关信息可以是一个或多个服务UE的USS/UTM的相关信息。
可能的情况二，该第四网络设备无法查询到服务UE的USS/UTM时，鉴于该第四网络设备具备的功能不同，还可能包括不同的情况。
当该第四网络设备仅具备查询服务UE的USS/UTM的功能，则可以在消息中提供USS/UTM发现失败指示；或者，当该第四网络设备还具备USS/UTM的功能时，则可以自行为UE服务，并将自身的信息通过USS/UTM发现响应消息发送给UFES。
可选地，在步骤S905之前，该方法900还可以包括一个步骤，第四网络设备根据接收到的USS/UTM发现请求消息查询服务UE的USS/UTM。
S906，如果在S905中，该第四网络设备发送的响应消息中包含USS/UTM发现失败指示，则在步骤S906中可以结合方法700中的步骤S704至S708，或者方法800中的步骤S806至S812，使得UE重新提供用于发现USS/UTM的信息。
S907，UFES向USS/UTM发送UAV和/或C2通信认证授权请求消息。
S908，USS/UTM向UFES提供UAV和/或C2通信认证授权响应消息。
S909，UFES在获得认证授权响应消息后，将认证授权结果转发至核心网网元，与方法700中的步骤S712和S713一致。
本申请实施例，在核心网发现USS/UTM失败时，通过核心网向第四网络设备请求新的服务UE的USS/UTM的相关信息，并根据第四网络设备提供的服务UE的USS/UTM的相关信息确定服务UE的USS/UTM，从而减少由于核心网发现USS/UTM失败，而导致的合法的UE无法进行UAV认证授权的问题。
下面结合图10，对本申请实施例的发现服务实体的方法1000进行详细说明。图10是本申请的方法1000的示意性交互图。
S1001，UE执行注册流程。
S1002，UFES收到了授权认证请求消息，该消息中包含服务UE的USS/UTM列表，换句话说，UE向UFES提供的多个备选的服务UE的USS/UTM。
作为一个示例，该消息中包括多个指示信息，每个指示信息都包括一个服务UE的USS/UTM的相关信息，且每个指示信息对应的USS/UTM都不同。
可选地，UFES可以在列表中指示各个备选的USS/UTM的优先级，以便于UFES在根据其中一个USS/UTM相关的信息确定发现USS/UTM失败时，可以根据列表中指示的优先级依次根据其他的USS/UTM相关的信息来发现USS/UTM。
S1003、UFES根据服务UE的USS/UTM相关信息确定发现USS/UTM失败，以及发现USS/UTM失败的原因与方法700中的步骤S703一致，另外，该步骤还包括：
UFES按照备选的USS/UTM相关信息的优先级或排列顺序确定是否发现USS/UTM成功，一旦成功发现USS/UTM，则使用该USS/UTM。
作为一个示例，当UFES根据优先级最高或排列顺序为第一的USS/UTM的相关信息 确定发现USS/UTM失败，则根据优先级次高或者排列顺序为第二的USS/UTM的相关信息去发现USS/UTM，如果成功发现USS/UTM，则使用，如果发现失败，则用类似的方式继续根据USS/UTM相关信息发现USS/UTM。
S1004、若UFES根据UAV提供的USS/UTM列表发现USS/UTM失败，则在步骤S1004中可以结合方法700中的步骤S704至S708，或者方法800中的步骤S806至S812，使得UE重新提供用于发现USS/UTM的信息。
S1005、在确定服务UE的USS/UTM的信息后，向该USS/UTM发送UAV和/或C2通信认证授权请求消息。
S1006、该USS/UTM向UFES提供UAV和/或C2通信认证授权响应消息。
S1007、UFES在获得认证授权响应消息后，将认证授权结果转发至核心网网元，与方法700中的步骤S712和S713一致。
本申请实施例，通过UE向核心网提供包括多个服务UE的USS/UTM的相关信息的备选USS/UTM列表，使得核心网根据其中一个USS/UTM的相关信息发现USS/UTM失败后，可以继续根据列表中的其他USS/UTM的相关信息继续发现USS/UTM，从而减少由于核心网发现USS/UTM失败，而导致的合法的UE无法进行UAV认证授权的问题。
以上，结合图4至图10详细说明了本申请实施例提供的方法。以下，结合图11至图12详细说明本申请实施例提供的装置。
图11是本申请实施例提供的用于发现服务实体的通信装置的示意性框图。如图11所示，该通信装置10可以包括收发模块11和处理模块12。
其中，收发模块11可以用于接收其他装置发送的信息，还可以用于向其他装置发送信息。比如，接收第一信息或发送第二信息。处理模块12可以用于进行装置的内容处理，比如，根据该第一信息不能发现该第二网络设备。
在一种可能的设计中，该通信装置10可对应于上述方法实施例中的第一网络设备或UFES或NEF。
具体地，该通信装置10可对应于根据本申请实施例的方法400至方法1000中任一方法中的第一网络设备或UFES或NEF，该通信装置10可以包括用于执行相应方法中由第一网络设备或UFES或NEF所执行的操作的模块，并且，该通信装置10中的各单元分别为了实现相应方法中由第一网络设备或UFES或NEF所执行的操作。
示例性的，在该通信装置10对应于方法400中的第一网络设备时，收发模块11用于执行步骤S402、S404、S407，处理模块12用于指示步骤S403。
示例性的，在该通信装置10对应于方法500中的第一网络设备时，收发模块11用于执行步骤S501、S503、S505，处理模块12用于指示步骤S502。
示例性的，在该通信装置10对应于方法600中的第一网络设备时，收发模块11用于执行步骤S601，处理模块12用于指示步骤S602、S603。
示例性的，在该通信装置10对应于方法700中的UFES或NEF时，收发模块11用于执行步骤S702、S704、S707、S710、S711、S712，处理模块12用于指示步骤S703、S708。
示例性的，在该通信装置10对应于方法800中的UFES或NEF时，收发模块11用于执行步骤S804、S806、S811、S814、S815、S816，处理模块12用于指示步骤S802、 S805、S812。
示例性的，在该通信装置10对应于方法900中的UFES或NEF时，收发模块11用于执行步骤S904、S905、S907、S908，处理模块12用于指示步骤S901、S902、S903、S906、S909。
示例性的，在该通信装置10对应于方法1000中的UFES或NEF时，收发模块11用于执行步骤S1005、S1006，处理模块12用于指示步骤S1001、S1002、S1003、S1004、S1007。
具体地，在一种可能的实施例中，收发模块11，用于接收第一信息，该第一信息包括第二网络设备的相关信息，该第二网络设备为该终端设备提供的待发现的网络设备，且该第二网络设备不属于该第一网络设备所在的移动网络系统；处理模块12，用于根据该第一信息进行针对该第二网络设备的发现处理；当针对该第二网络设备的发现处理失败时，该收发模块11，还用于发送第二信息，该第二信息用于请求重新提供待发现的网络设备；该收发模块11，还用于接收第三信息，该第三信息包括第五网络设备的相关信息，该第五网络设备是该终端设备提供的更新后的待发现的网络设备，且该第五网络设备不属于该第一网络设备所在的移动网络系统；该处理模块12，还用于根据该第三信息进行针对该第五网络设备的发现处理。
其中，该第二信息包括第一指示信息，该第一指示信息请求重新提供待发现的网络设备。
其中，该第二信息包括第二指示信息和第一原因值中的至少一个，其中，该第二指示信息指示该第一网络设备根据该第一信息不能发现该第二网络设备，该第一原因值指示该第一网络设备根据该第一信息不能发现该第二网络设备的原因。
具体地，在另一种可能的实施例中，收发模块11，用于接收来自终端设备的第七信息，该第五信息包括第二网络设备的相关信息，该第二网络设备为服务该终端设备的网络设备，且该第二网络设备不属于该第一网络设备所在的移动网络系统；处理模块12，用于根据该第七信息不能发现该第二网络设备；该收发模块11，还用于向第四网络设备发送第八信息，该第八信息请求该第二网络设备的相关信息；该收发模块11，还用于接收来自该第四网络设备的第九信息，该第九信息包括该第二网络设备的相关信息。
其中，该第八信息包括第五指示信息和第三原因值中的至少一个，其中，该第五指示信息指示该第一网络设备根据该第一信息不能发现该第二网络设备，该第三原因值指示该第一网络设备根据该第一信息不能发现该第二网络设备的原因。
其中，该第八信息包括该第七信息。
具体地，在另一种可能的实施例中，收发模块11，用于接收来自终端设备的第十信息，该第十信息包括第一列表，该第一列表包括至少一个第二网络设备的相关信息，每个该第二网络设备的相关信息用于发现一个该第二网络设备，该第二网络设备为服务该终端设备的网络设备，且该第二网络设备不属于该第一网络设备所在的移动网络系统；处理模块12，用于根据该第八信息中的一个该第二网络设备的相关信息不能发现该第二网络设备；该处理模块12，还用于根据该第十信息中的其他该第二网络设备的相关信息发现该第二网络设备。
其中，该第十信息还包括该多个第二网络设备的相关信息的优先级信息，该第一网络 设备按照优先级的顺序发现该第二网络设备。
在一种可能的设计中，该通信装置10可对应于上述方法实施例中的终端设备。
具体地，该通信装置10可对应于根据本申请实施例的方法400至方法1000中任一方法中的终端设备，该通信装置10可以包括用于执行相应方法中由终端设备所执行的操作的模块，并且，该通信装置10中的各单元分别为了实现相应方法中由终端设备所执行的操作。
示例性的，在该通信装置10对应于方法400中的终端设备时，收发模块11用于执行步骤S401、S405、S406。
示例性的，在该通信装置10对应于方法500中的终端设备时，收发模块11用于执行步骤S501。
示例性的，在该通信装置10对应于方法600中的终端设备时，收发模块11用于执行步骤S601。
示例性的，在该通信装置10对应于方法700中的UE时，收发模块11用于执行步骤S701、S705a-S706a或SS705b-S706b、S709、S713。
示例性的，在该通信装置10对应于方法800中的UE时，收发模块11用于执行步骤S801、S802、S803、S802、S808a-S809a或S807b-S808b、S813、S817。
示例性的，在该通信装置10对应于方法900中的UE时，收发模块11用于执行步骤S901、S902、S906、S909。
示例性的，在该通信装置10对应于方法1000中的UE时，收发模块11用于执行步骤S1001、S1002、S1004、S1007。
具体地，在一种可能的实施例中，收发模块11，用于发送第四信息，该第四信息包括第二网络设备的相关信息，该第二网络设备为该终端设备提供的待发现的网络设备，且该第二网络设备不属于该终端设备所在的移动网络系统；该收发模块11，还用于接收第五信息，该第五信息用于请求该终端设备重新提供待发现的网络设备；该收发模块11，还用于发送第六信息，该第六信息包括第五网络设备的相关信息，该第五网络设备是更新后的待发现的网络设备，且该第五网络设备不属于该终端设备所在的移动网络系统。
其中，该第四信息包括第三指示信息，该第三指示信息请求该终端设备重新提供待发现的网络设备。
其中，该第四信息包括第四指示信息和第二原因值中的至少一个，其中，该第四指示信息指示该第一网络设备根据该第三信息不能发现该第二网络设备，该第二原因值指示该第一网络设备根据该第三信息不能发现该第二网络设备的原因。
具体地，在另一种可能的实施例中，收发模块11，用于发送第十信息，该第十信息包括第一列表，该第一列表包括至少一个第二网络设备的相关信息，每个该第二网络设备的相关信息用于发现一个该第二网络设备，该第二网络设备为服务该终端设备的网络设备，且该第二网络设备不属于该终端设备接入的移动网络系统。
该第十信息还包括该多个第二网络设备的相关信息的优先级信息，该第一网络设备按照优先级的顺序发现该第二网络设备。
在一种可能的设计中，该通信装置10可对应于上述方法实施例中的第三网络设备或AMF或SMF。
具体地，该通信装置10可对应于根据本申请实施例的方法400、方法700至方法1000中任一方法中的第三网络设备或AMF或SMF，该通信装置10可以包括用于执行相应方法中由第三网络设备或AMF或SMF所执行的操作的模块，并且，该通信装置10中的各单元分别为了实现相应方法中由第三网络设备或AMF或SMF所执行的操作。
示例性的，在该通信装置10对应于方法400中的第三网络设备时，收发模块11用于执行步骤S401、S402、S405、S406。
示例性的，在该通信装置10对应于方法700中的AMF时，收发模块11用于执行步骤701、S72、S704、S705a-S706a或S705b-S706b、S707、S709、S7012、S713。
示例性的，在该通信装置10对应于方法800中的SMF时，收发模块11用于执行步骤S801、S802、S803、S804、S806、S807a和S810a，或，S807b和S808b、S811、S813、S816、S817。
示例性的，在该通信装置10对应于方法800中的AMF时，收发模块11用于执行步骤S807a-S810a或S807b-S808b、S813。
示例性的，在该通信装置10对应于方法900中的AMF或SMF时，收发模块11用于执行步骤S901、S902、S906、S909。
示例性的，在该通信装置10对应于方法1000中的SMF或SMF时，收发模块11用于执行步骤S1001、S1002、S1004、S1007。
具体地，收发模块11，用于接收第二信息，该第二信息用于请求重新提供待发现的网络设备，该待发现的网络设备为终端设备提供的服务该终端设备的网络设备，且该待发现的网络设备不属于该第三网络设备所在的移动网络系统；处理模块12，用于根据该第二信息发送第五信息，该第五信息用于请求重新提供该待发现的网络设备；该收发模块11，还用于接收第六信息，该第六信息包括该第五网络设备的相关信息，该第五网络设备是该终端设备提供的更新后的待发现的网络设备，且该第五网络设备不属于该第三网络设备所在的移动网络系统；该收发模块11，还用于第三信息，该第三信息包括该第五网络设备的相关信息。
其中，该第二信息包括第一指示信息，该第一指示信息请求重新提供该待发现的网络设备。
该第二信息包括第二指示信息和第一原因值中的至少一个，其中，该第二指示信息指示该第一网络设备根据该第一信息不能发现该第二网络设备，该第一原因值指示该第一网络设备根据该第一信息不能发现该第二网络设备的原因。
其中，该第四信息包括第三指示信息，该第三指示信息指示该终端设备更新该第三信息。
该第二信息包括第四指示信息和第二原因值中的至少一个，其中，该第四指示信息指示该第一网络设备不能发现该第二网络设备，该第二原因值指示该第一网络设备根据该第三信息不能发现该第二网络设备的原因。
在一种可能的设计中，该通信装置10可对应于上述方法实施例中的第四网络设备。
具体地，该通信装置10可对应于根据本申请实施例的方法500、方法900中任一方法中的第四网络设备，该通信装置10可以包括用于执行相应方法中由第四网络设备所执行的操作的模块，并且，该通信装置10中的各单元分别为了实现相应方法中由第四网络 设备所执行的操作。
示例性的，在该通信装置10对应于方法500中的第四网络设备时，收发模块11用于执行步骤S503、S505，处理模块12用于指示步骤S504。
示例性的，在该通信装置10对应于方法900中的第四网络设备时，收发模块11用于执行步骤S904、S905。
具体地，收发模块11，用于接收来自该第一网络设备的第八信息，该第八信息请求第二网络设备的相关信息，该第二网络设备为服务该终端设备的网络设备，且该第二网络设备不属于该第一网络设备所在的移动通信系统；处理模块12，用于为该第一网络设备查询该第二网络设备的相关信息；该收发模块11，还用于向该第一网络设备发送第九信息，该第九信息包括该第二网络设备的相关信息。
其中，该第八信息包括第五指示信息和第三原因值中的至少一个，其中，该第五指示信息指示该第一网络设备根据该第一信息不能发现该第二网络设备，该第三原因值指示该第一网络设备根据该第一信息不能发现该第二网络设备的原因。
其中，或者该第八信息包括该第七信息。
图12为本申请实施例提供的信息传输的装置20的示意图。
在一种可能的设计中，该装置20可以为UFES或NEF，也可以为位于UFES或NEF上的芯片或芯片系统等。
在一种可能的设计中，该装置20可以为终端设备，包括各种具有无线通信功能的手持设备、车载设备、可穿戴设备、计算设备或连接到无线调制解调器的其它处理设备，以及各种形式的终端，移动台，终端，用户设备，软终端等等，也可以为位于终端设备上的芯片或芯片系统等。
在一种可能的设计中，该装置20可以为AMF或SMF或MME，包括各种用于移动性管理和接入管理和/或用于会话管理功能的设备等等，也可以为位于AMF或SMF或MME上的芯片或芯片系统等。
在一种可能的设计中，该装置20可以为USS或UTM，也可以为位于USS或UTM上的芯片或芯片系统等。
该装置20可以包括处理器21(即，处理模块的一例)和存储器22。该存储器22用于存储指令，该处理器21用于执行该存储器22存储的指令，以使该装置20实现如图4至图9中对应的方法中上述各种可能的设计中的设备执行的步骤。
进一步地，该装置20还可以包括输入口23(即，收发模块的一例)和输出口24(即，收发模块的另一例)。进一步地，该处理器21、存储器22、输入口23和输出口24可以通过内部连接通路互相通信，传递控制和/或数据信号。该存储器22用于存储计算机程序，该处理器21可以用于从该存储器22中调用并运行该计算机程序，以控制输入口23接收信号，控制输出口24发送信号，完成上述方法中终端设备的步骤。该存储器22可以集成在处理器21中，也可以与处理器21分开设置。
可选地，若该信息传输的装置20为通信设备，该输入口23为接收器，该输出口24为发送器。其中，接收器和发送器可以为相同或者不同的物理实体。为相同的物理实体时，可以统称为收发器。
可选地，若该装置20为芯片或电路，该输入口23为输入接口，该输出口24为输出 接口。
作为一种实现方式，输入口23和输出口34的功能可以考虑通过收发电路或者收发的专用芯片实现。处理器21可以考虑通过专用处理芯片、处理电路、处理器或者通用芯片实现。
作为另一种实现方式，可以考虑使用通用计算机的方式来实现本申请实施例提供的设备。即将实现处理器21、输入口23和输出口24功能的程序代码存储在存储器22中，通用处理器通过执行存储器22中的代码来实现处理器21、输入口23和输出口24的功能。
其中，装置20中各模块或单元可以用于执行上述方法中进行随机接入的设备(例如，终端设备)所执行的各动作或处理过程，这里，为了避免赘述，省略其详细说明。
该装置20所涉及的与本申请实施例提供的技术方案相关的概念，解释和详细说明及其他步骤请参见前述方法或其他实施例中关于这些内容的描述，此处不做赘述。
应理解，本申请实施例中，该处理器可以为中央处理单元(CPU，central processing unit)，该处理器还可以是其他通用处理器、数字信号处理器(DSP，digital signal processor)、专用集成电路(application specific integrated circuit，ASIC)、现成可编程门阵列(field programmable gate array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
本申请实施例还提供一种计算机可读存储介质，其上存储有用于实现上述方法实施例中由终端设备执行的方法的计算机指令。
例如，该计算机程序被计算机执行时，使得该计算机可以实现上述方法实施例中由终端设备执行的方法。
本申请实施例还提供一种计算机可读存储介质，其上存储有用于实现上述方法实施例中由第一网络设备或UFES或NEF执行的方法的计算机指令。
例如，该计算机程序被计算机执行时，使得该计算机可以实现上述方法实施例中由第一网络设备或UFES或NEF执行的方法。
本申请实施例还提供一种计算机可读存储介质，其上存储有用于实现上述方法实施例中由第三网络设备或AMF或SMF执行的方法的计算机指令。
例如，该计算机程序被计算机执行时，使得该计算机可以实现上述方法实施例中由第三网络设备或AMF或SMF执行的方法。
本申请实施例还提供一种计算机可读存储介质，其上存储有用于实现上述方法实施例中由第四网络设备执行的方法的计算机指令。
例如，该计算机程序被计算机执行时，使得该计算机可以实现上述方法实施例中由第四网络设备执行的方法。
本申请实施例还提供一种包含指令的计算机程序产品，该指令被计算机执行时使得该计算机实现上述方法实施例中由终端设备执行的方法，或由第一网络设备或UFES或NEF执行的方法，或由第三网络设备或AMF或SMF执行的方法，或由第四网络设备执行的方法。
本申请实施例还提供一种通信系统，该通信系统包括上文实施例中的终端设备、第一网络设备或UFES或NEF、第三网络设备或AMF或SMF。
本申请实施例还提供一种通信系统，该通信系统包括上文实施例中的终端设备、第一 网络设备或UFES或NEF、第四网络设备。
还应理解，本申请实施例中的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(read-only memory，ROM)、可编程只读存储器(programmable ROM，PROM)、可擦除可编程只读存储器(erasable PROM，EPROM)、电可擦除可编程只读存储器(electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(random access memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(direct rambus RAM，DR RAM)。
上述实施例，可以全部或部分地通过软件、硬件、固件或其他任意组合来实现。当使用软件实现时，上述实施例可以全部或部分地以计算机程序产品的形式实现。该计算机程序产品包括一个或多个计算机指令或计算机程序。在计算机上加载或执行所述计算机指令或计算机程序时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以为通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集合的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质。半导体介质可以是固态硬盘。
应理解，本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
应理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组 件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、ROM、RAM、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应所述以权利要求的保护范围为准。

Claims (19)

  1. 一种发现服务实体的方法，其特征在于，包括：
    第一网络设备接收第一信息，所述第一信息包括第二网络设备的相关信息，所述第二网络设备为所述终端设备提供的待发现的网络设备，且所述第二网络设备不属于所述第一网络设备所在的移动网络系统；
    所述第一网络设备根据所述第一信息进行针对所述第二网络设备的发现处理；
    当针对所述第二网络设备的发现处理失败时，所述第一网络设备发送第二信息，所述第二信息用于请求重新提供待发现的网络设备；
    所述第一网络设备接收第三信息，所述第三信息包括第五网络设备的相关信息，所述第五网络设备是所述终端设备提供的更新后的待发现的网络设备，且所述第五网络设备不属于所述第一网络设备所在的移动网络系统；
    所述第一网络设备根据所述第三信息进行针对所述第五网络设备的发现处理。
  2. 根据权利要求1所述的方法，其特征在于，所述第二信息包括第二指示信息和第一原因值中的至少一个，其中，所述第二指示信息指示所述第一网络设备根据所述第一信息不能发现所述第二网络设备，所述第一原因值指示所述第一网络设备根据所述第一信息不能发现所述第二网络设备的原因。
  3. 一种发现服务实体的方法，其特征在于，包括：
    终端设备发送第四信息，所述第四信息包括第二网络设备的相关信息，所述第二网络设备为所述终端设备提供的待发现的网络设备，且所述第二网络设备不属于所述终端设备所在的移动网络系统；
    所述终端设备接收第五信息，所述第五信息用于请求所述终端设备重新提供待发现的网络设备；
    所述终端设备发送第六信息，所述第六信息包括第五网络设备的相关信息，所述第五网络设备是更新后的待发现的网络设备，且所述第五网络设备不属于所述终端设备所在的移动网络系统。
  4. 根据权利要求3所述的方法，其特征在于，所述第四信息包括第四指示信息和第二原因值中的至少一个，其中，所述第四指示信息指示所述第一网络设备不能发现所述第二网络设备，所述第二原因值指示所述第一网络设备不能发现所述第二网络设备的原因。
  5. 一种发现服务实体的方法，其特征在于，包括：
    第三网络设备接收第二信息，所述第二信息用于请求重新提供待发现的网络设备，所述待发现的网络设备为终端设备提供的服务所述终端设备的网络设备，且所述待发现的网络设备不属于所述第三网络设备所在的移动网络系统；
    所述第三网络设备根据所述第二信息发送第五信息，所述第五信息用于请求重新提供所述待发现的网络设备；
    所述第三网络设备接收第六信息，所述第六信息包括所述第五网络设备的相关信息，所述第五网络设备是所述终端设备提供的更新后的待发现的网络设备，且所述第五网络设备不属于所述第三网络设备所在的移动网络系统；
    所述第三网络设备发送第三信息，所述第三信息包括所述第五网络设备的相关信息。
  6. 根据权利要求5所述的方法，其特征在于，所述第二信息包括第二指示信息和第一原因值中的至少一个，其中，所述第二指示信息指示所述第一网络设备根据所述第一信息不能发现所述第二网络设备，所述第一原因值指示所述第一网络设备根据所述第一信息不能发现所述第二网络设备的原因。
  7. 根据权利要求5所述的方法，其特征在于，所述第二信息包括第四指示信息和第二原因值中的至少一个，其中，所述第四指示信息指示所述第一网络设备不能发现所述第二网络设备，所述第二原因值指示所述第一网络设备根据所述第三信息不能发现所述第二网络设备的原因。
  8. 一种发现服务实体的装置，其特征在于，包括：
    收发模块，用于接收第一信息，所述第一信息包括第二网络设备的相关信息，所述第二网络设备为所述终端设备提供的待发现的网络设备，且所述第二网络设备不属于所述第一网络设备所在的移动网络系统；
    处理模块，用于根据所述第一信息进行针对所述第二网络设备的发现处理；
    当针对所述第二网络设备的发现处理失败时，所述收发模块，还用于发送第二信息，所述第二信息用于请求重新提供待发现的网络设备；
    所述收发模块，还用于接收第三信息，所述第三信息包括第五网络设备的相关信息，所述第五网络设备是所述终端设备提供的更新后的待发现的网络设备，且所述第五网络设备不属于所述第一网络设备所在的移动网络系统；
    所述处理模块，还用于根据所述第三信息进行针对所述第五网络设备的发现处理。
  9. 根据权利要求8所述的装置，其特征在于，所述第二信息包括第二指示信息和第一原因值中的至少一个，其中，所述第二指示信息指示所述第一网络设备根据所述第一信息不能发现所述第二网络设备，所述第一原因值指示所述第一网络设备根据所述第一信息不能发现所述第二网络设备的原因。
  10. 一种发现服务实体的装置，其特征在于，包括：
    收发模块，用于发送第四信息，所述第四信息包括第二网络设备的相关信息，所述第二网络设备为所述终端设备提供的待发现的网络设备，且所述第二网络设备不属于所述终端设备所在的移动网络系统；
    所述收发模块，还用于接收第五信息，所述第五信息用于请求所述终端设备重新提供待发现的网络设备；
    所述收发模块，还用于发送第六信息，所述第六信息包括第五网络设备的相关信息，所述第五网络设备是更新后的待发现的网络设备，且所述第五网络设备不属于所述终端设备所在的移动网络系统。
  11. 根据权利要求10所述的装置，其特征在于，所述第四信息包括第二指示信息和第一原因值中的至少一个，其中，所述第二指示信息指示所述第一网络设备根据所述第一信息不能发现所述第二网络设备，所述第一原因值指示所述第一网络设备根据所述第一信息不能发现所述第二网络设备的原因。
  12. 一种发现服务实体的装置，其特征在于，包括：
    收发模块，用于接收第二信息，所述第二信息用于请求重新提供待发现的网络设备， 所述待发现的网络设备为终端设备提供的服务所述终端设备的网络设备，且所述待发现的网络设备不属于所述第三网络设备所在的移动网络系统；
    处理模块，用于根据所述第二信息发送第五信息，所述第五信息用于请求重新提供所述待发现的网络设备；
    所述收发模块，还用于接收第六信息，所述第六信息包括所述第五网络设备的相关信息，所述第五网络设备是所述终端设备提供的更新后的待发现的网络设备，且所述第五网络设备不属于所述第三网络设备所在的移动网络系统；
    所述收发模块，还用于第三信息，所述第三信息包括所述第五网络设备的相关信息。
  13. 根据权利要求12所述的装置，其特征在于，所述第二信息包括第二指示信息和第一原因值中的至少一个，其中，所述第二指示信息指示所述第一网络设备根据所述第一信息不能发现所述第二网络设备，所述第一原因值指示所述第一网络设备根据所述第一信息不能发现所述第二网络设备的原因。
  14. 根据权利要求12所述的装置，其特征在于，所述第二信息包括第四指示信息和第二原因值中的至少一个，其中，所述第四指示信息指示所述第一网络设备根据所述第三信息不能发现所述第二网络设备，所述第二原因值指示所述第一网络设备根据所述第三信息不能发现所述第二网络设备的原因。
  15. 一种通信装置，其特征在于，包括：
    处理器和存储器；
    所述存储器，用于存储计算机程序；
    所述处理器，用于执行所述存储器中存储的计算机程序，以使得所述通信装置执行权利要求1或2所述的通信方法，或执行权利要求3或4所述的通信方法，或执行权利要求5至7中任一项所述的通信方法。
  16. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质上存储有计算机程序，当所述计算机程序在计算机上运行时，使得所述计算机执行如权利要求1或2所述的通信方法，或执行权利要求3或4所述的通信方法，或执行权利要求5至7中任一项所述的通信方法。
  17. 一种芯片系统，其特征在于，包括：处理器，用于从存储器中调用并运行计算机程序，使得安装有所述芯片系统地通信设备执行如权利要求1或2所述的通信方法，或执行权利要求3或4所述的通信方法，或执行权利要求5至7中任一项所述的通信方法。
  18. 一种通信系统，其特征在于，所述通信系统包括第一网络设备和终端设备，其中所述第一网络设备用于执行如权利要求1或2所述的方法，所述终端设备用于执行如权利要求3或4所述的方法。
  19. 一种通信系统，其特征在于，所述通信系统包括第一网络设备、终端设备和第三网络设备，其中所述第一网络设备用于执行如权利要求1或2所述的方法，所述终端设备用于执行如权利要求3或4所述的方法，所述第三网络设备用于执行如权利要求5至7中任一项所述的方法。
PCT/CN2022/076788 2021-03-15 2022-02-18 发现服务实体的方法和通信装置 WO2022193903A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110277238.9 2021-03-15
CN202110277238.9A CN115150803B (zh) 2021-03-15 2021-03-15 发现服务实体的方法和通信装置

Publications (1)

Publication Number Publication Date
WO2022193903A1 true WO2022193903A1 (zh) 2022-09-22

Family

ID=83321532

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/076788 WO2022193903A1 (zh) 2021-03-15 2022-02-18 发现服务实体的方法和通信装置

Country Status (2)

Country Link
CN (1) CN115150803B (zh)
WO (1) WO2022193903A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190098537A1 (en) * 2017-09-28 2019-03-28 Weihua QIAO SMF, AMF and UPF Relocation During UE Registration
US20190387458A1 (en) * 2015-08-03 2019-12-19 Convida Wireless, Llc Mechanisms for ad hoc service discovery
WO2020113520A1 (zh) * 2018-12-06 2020-06-11 Oppo广东移动通信有限公司 用于建立连接的方法、网络设备和终端设备
CN112055309A (zh) * 2019-06-05 2020-12-08 上海华为技术有限公司 一种通信方法以及相关设备
CN112205020A (zh) * 2019-10-30 2021-01-08 深圳市大疆创新科技有限公司 视频传输方法、设备及计算机可读存储介质

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3313106B1 (en) * 2015-06-18 2021-04-28 Sony Corporation System and method to manage terminal devices
CN109525678B (zh) * 2018-12-25 2022-09-27 众安信息技术服务有限公司 区块链网络系统以及相应的节点设备发现方法

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190387458A1 (en) * 2015-08-03 2019-12-19 Convida Wireless, Llc Mechanisms for ad hoc service discovery
US20190098537A1 (en) * 2017-09-28 2019-03-28 Weihua QIAO SMF, AMF and UPF Relocation During UE Registration
WO2020113520A1 (zh) * 2018-12-06 2020-06-11 Oppo广东移动通信有限公司 用于建立连接的方法、网络设备和终端设备
CN112055309A (zh) * 2019-06-05 2020-12-08 上海华为技术有限公司 一种通信方法以及相关设备
CN112205020A (zh) * 2019-10-30 2021-01-08 深圳市大疆创新科技有限公司 视频传输方法、设备及计算机可读存储介质

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
INTERDIGITAL: "C2 communication switching for change of UAV-C", 3GPP DRAFT; S2-2004169, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. e-meeting; 20200601 - 20200612, 22 May 2020 (2020-05-22), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051890174 *

Also Published As

Publication number Publication date
CN115150803A (zh) 2022-10-04
CN115150803B (zh) 2024-06-14

Similar Documents

Publication Publication Date Title
WO2020143569A1 (zh) 无线网络通信方法、网络设备和终端
US20220116814A1 (en) Meeting strict qos requirements through network control of device route and location
US20220078857A1 (en) Method for transmitting/receiving pdb-related signal in wireless communication system and device therefor
US11917451B2 (en) Method by which NWDAF transmits and receives signal in wireless communication system, and device therefor
EP3949339B1 (en) Requesting data connection for uav operation
WO2020156127A1 (zh) 无线通信的方法和通信设备
US20220167260A1 (en) Method for terminal to connect to network in wireless communication system
US20220295337A1 (en) Operation method of ue related to pfi in wireless communication system, and apparatus therefor
EP3952599A1 (en) Method for establishing communication bearer, device and system
WO2022170911A1 (zh) 认证授权的方法与通信装置
JP2023545686A (ja) 航空システムのセッション管理
US20220312509A1 (en) Qos-related operation method in wireless communication system and apparatus therefor
US20230007721A1 (en) Method and device for controlling configuration related to sidelink communication in wireless communication system
US11670177B2 (en) Unmanned aerial vehicle remote identification, command and control
CN116438823A (zh) 航空系统的认证和授权
US20220361039A1 (en) Operation method related to sidelink transmission and reception of ue in wireless communication system, and device therefor
WO2022156627A1 (zh) 一种无人机通信管理方法及装置
WO2022193903A1 (zh) 发现服务实体的方法和通信装置
US20220312205A1 (en) Communication method and device for supporting authentication of unmanned aerial vehicle in wireless communication system
JP2024527505A (ja) 第１のＡｃｃｅｓｓ ａｎｄ Ｍｏｂｉｌｉｔｙ Ｍａｎａｇｅｍｅｎｔ Ｆｕｎｃｔｉｏｎ（ＡＭＦ）装置の方法、ユーザ装置（ＵＥ）の方法、第１のＡｃｃｅｓｓ ａｎｄ Ｍｏｂｉｌｉｔｙ Ｍａｎａｇｅｍｅｎｔ Ｆｕｎｃｔｉｏｎ（ＡＭＦ）装置、およびユーザ装置（ＵＥ）
WO2022206532A1 (zh) 一种服务质量QoS更新的方法、装置和系统
US20240171968A1 (en) Reduced capacity ues and 5th generation core network interactions
EP4451648A1 (en) Authorization method and apparatus
WO2023165425A1 (zh) 一种通信方法、装置及设备
WO2024098268A1 (zh) 信息传输方法及装置、通信设备及存储介质

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: 22770258

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 22770258

Country of ref document: EP

Kind code of ref document: A1