WO2023065778A1 - 中继通信的方法和装置 - Google Patents

中继通信的方法和装置 Download PDF

Info

Publication number
WO2023065778A1
WO2023065778A1 PCT/CN2022/110802 CN2022110802W WO2023065778A1 WO 2023065778 A1 WO2023065778 A1 WO 2023065778A1 CN 2022110802 W CN2022110802 W CN 2022110802W WO 2023065778 A1 WO2023065778 A1 WO 2023065778A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal device
request message
uav
service provider
relay
Prior art date
Application number
PCT/CN2022/110802
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 WO2023065778A1 publication Critical patent/WO2023065778A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/24—Reselection being triggered by specific parameters
    • H04W36/30—Reselection being triggered by specific parameters by measured or perceived connection quality data

Definitions

  • the present application relates to the field of communications, and more particularly, to a method and device for relaying communications.
  • UAV uncrewed aerial vehicle
  • the current agreement stipulates the authentication and authorization of a UAV and the authorization process of C2 communication, but in some scenarios, multiple drones may work together, and one or some of them are more capable. Data from other drones can be transmitted to a controller or server, i.e. drone relay communication becomes a possible scenario.
  • This application provides a method and device for relay communication, in order to realize the authentication and authorization of Remote UAV in the relay communication scenario.
  • a method for relaying communication is provided.
  • the method for relaying communication may be executed by the first terminal device, or may also be executed by a chip or circuit provided in the first terminal device. Not limited.
  • the execution of the first terminal device is used as an example for description below.
  • the method of relaying communication includes:
  • the first terminal device receives a first request message from the second terminal device, the first request message includes a first identifier, and the first identifier is the identifier of the second terminal device assigned by the service provider; the first terminal device sending a second request message to a network element of the first core network, where the second request message includes the first identifier, where the second request message is used to request to establish the connection between the second terminal device and the service provider and/or control communication between devices and through the first terminal device.
  • the first terminal device requests to establish an Communication between the second terminal device and the service provider and/or controller.
  • the first core network element receiving the second request message can determine whether to authenticate the second terminal device, so as to realize the authentication and authorization of the remote terminal device in the relay scenario, and realize Remote UE under the premise of ensuring security.
  • Relay networking
  • the second request message may be a request message for requesting modification or establishment of a session, and the session is used between the second terminal device and the service provider communication.
  • the above-mentioned second request message can reuse the request message used to request modification or session establishment in the current process, reducing signaling overhead.
  • the method further includes: the first terminal device receiving a second response message from the first core network element in response to the second request message, the The second response message includes the authentication and authorization result of the second terminal device, wherein the authentication and authorization result of the second terminal device includes whether the second terminal device is legal, and/or whether the first terminal device is allowed to relay the Data of the second terminal device.
  • the first terminal device can obtain the authentication and authorization result of the second terminal device, so that it can determine whether the second terminal device is legal or not, according to the authentication and authorization result of the second terminal device.
  • the data of the second terminal device is relayed to ensure safety.
  • the authentication and authorization result of the second terminal device further includes: whether the second terminal device matches the controller.
  • the first terminal device can simultaneously obtain the legality authentication result of the second terminal device and the authentication authorization of the communication between the second terminal device and the controller, thereby simplifying the authentication process.
  • the second request message further includes an identifier of the controller, and the controller requests for the second terminal device to control the second terminal device.
  • controller the authentication and authorization result of the second terminal device also includes: whether the controller is allowed to control the second terminal device; and/or, the second request message also includes the identity of the first terminal device, and the second terminal device
  • the authentication and authorization result of the device also includes: whether the controller controlling the first terminal device is allowed to control the second terminal device.
  • different information elements carried in the second request message can determine the authentication result of the second terminal device in different ways, thereby improving the flexibility of the solution.
  • the method further includes: the first terminal device receiving first indication information from the second terminal device, where the first indication information is used to indicate that the second The terminal device requests to establish communication with the controller; the first terminal device sends the first indication information to the first core network element.
  • the first terminal device can authenticate the C2 communication of the second terminal device through the first indication information, so that the authentication authorization of the communication between the second terminal device and the controller can be independently authenticated, and there is conducive to regulation.
  • the first terminal device receives at least one of the following information from the second terminal device: flight information, controller identification, service provider identification , the identifier of the second terminal device.
  • the method further includes: the first terminal device receiving second indication information from the first core network element, where the second indication information is used to indicate that the first Whether the second terminal device is allowed to communicate with the controller; the first terminal device sends the second indication information to the second terminal device.
  • the method further includes: the first terminal device sends a first response message in response to the first request message to the second terminal device, and the first response The message includes the authentication and authorization result of the second terminal device.
  • the first terminal device obtains the authentication and authorization result of the second terminal device and forwards it to the second terminal device, so that the second terminal device can know its own authentication and authorization result.
  • the method before the first terminal device sends the second request message to the first core network element, the method further includes: the first terminal device determines to serve the second request message.
  • the service provider of the second terminal device is the same as the service provider serving the first terminal device, and/or the first terminal device determines that the controller controlling the first terminal device is the same as the controller controlling the second terminal device .
  • the first terminal device can determine the need to request the first core network element to trigger the process of authenticating the second terminal device in different ways, and can judge in advance whether authentication is required to avoid unnecessary Signaling overhead.
  • the first terminal device determines that the provider serving the second terminal device is the same as the provider serving the first terminal device, including: the first terminal device According to the first identification, it is determined that the service provider serving the second terminal device is the same as the service provider serving the first terminal device; and/or, the first request message further includes address information of the service provider, the The first terminal device determines according to the address information that the service provider serving the second terminal device is the same as the service provider serving the first terminal device.
  • the first terminal device can determine that the provider serving the second terminal device is the same as the provider serving the first terminal device in different ways, which improves the flexibility of the solution.
  • the first request message further includes an identifier of the controller, and the controller requests for the second terminal device to control the second terminal device.
  • the first terminal device determines that the controller that controls the first terminal device is the same as the controller that controls the second terminal device, including: the first terminal device determines the controller that controls the first terminal device according to the identifier of the controller The controller is the same as the controller controlling the second terminal device.
  • the first core network element is a session management function element SMF
  • the second request message is a session establishment request message or a session modification request message.
  • the second request message when the second request message is a session establishment request message, the second request message is used to establish a connection between the first terminal device and the service provider and/or the A second session between controllers, where the second session is used to transmit data between the second terminal device and the service provider and/or the controller; or when the second request message is a session modification request message, The second request message is used to request to modify the first session as a session for further transmitting data between the second terminal device and the service provider and/or the controller, before sending the session modification request message , the first session is a session established by the first terminal device for transmitting data between the first terminal device and the service provider and/or the controller.
  • the controller is used to control the second terminal device;
  • the service provider is a third-party entity, and is used to provide services for the first terminal device and the The second terminal device provides the service.
  • a method for relaying communication is provided.
  • the method for relaying communication can be executed by the second terminal device, or can also be executed by a chip or circuit provided in the second terminal device. Not limited.
  • the execution of the second terminal device is used as an example for description below.
  • the method of relaying communication includes:
  • the second terminal device acquires a first identifier, which is the identifier of the second terminal device assigned by the service provider; the second terminal device sends a first request message to the first terminal device, and the first request message includes In the first identification, the second terminal device is a terminal device connected to the Internet through a relay.
  • the first terminal device can learn the first identifier of the second terminal device, and the first identifier triggers an authentication process of the second terminal device.
  • the authentication and authorization of remote terminal equipment in the relay scenario is realized, and the Remote UE relay networking is realized under the premise of ensuring security.
  • the method further includes: the second terminal device receiving a first response message from the first terminal device in response to the first request message, the first The response message includes the authentication and authorization result of the second terminal device, wherein the authentication and authorization result of the second terminal device includes whether the second terminal device is legal, and/or whether the first terminal device is allowed to relay the second terminal device. data from the terminal device.
  • the second terminal device acquires the authentication and authorization result of the second terminal device from the first terminal device, so that the second terminal device can know its own authentication and authorization result.
  • the authentication and authorization result of the second terminal device further includes: whether the second terminal device matches the controller.
  • the second terminal device can simultaneously obtain the legality authentication result of the second terminal device and the authentication authorization of the communication between the second terminal device and the controller, thereby simplifying the authentication process.
  • the method further includes: the second terminal device sending first indication information to the first terminal device, where the first indication information is used to indicate that the second terminal The device requests to establish communication with the controller.
  • the second terminal device can request the C2 communication authentication of the second terminal device through the first indication information, so that the authentication authorization of the communication between the second terminal device and the controller can be independently authenticated, conducive to regulation.
  • the method further includes: the second terminal device receiving second indication information from the first terminal device, where the second indication information is used to indicate that the second terminal Whether the device is allowed to communicate with this controller.
  • the first request message further includes an identifier of the controller, and/or an identifier of the service provider, where the controller is the second terminal A device requests a controller for controlling the end device.
  • a method for relaying communication is provided, and the method for relaying communication may be performed by a network element of the first core network, or may also be performed by a chip or a circuit provided in the network element of the first core network, This application is not limited to this.
  • the execution of the network element of the first core network is taken as an example for description below.
  • the method of relaying communication includes:
  • the first core network element receives a second request message from the first terminal device, the second request message includes a first identifier, and the first identifier is the identifier of the second terminal device assigned by the service provider; the first The network element of the core network sends a third request message to the service provider, the third request message includes the first identifier and the identifier of the first terminal device, and the third request message is used to request the service provider to The second terminal device performs authentication and authorization, wherein the second request message is used to request establishment of communication between the second terminal device and the service provider and/or controller through the first terminal device.
  • the first terminal device requests the first core network element to trigger the authentication process of the second terminal device according to the first identifier of the second terminal device.
  • the authentication and authorization of remote terminal equipment in the relay scenario is realized, and the Remote UE relay networking is realized under the premise of ensuring security.
  • the method further includes: the first core network element receiving a third response message from the service provider in response to the third request message, the first The third response message includes the authentication and authorization result of the second terminal device, wherein the authentication and authorization result of the second terminal device includes whether the second terminal device is legal, and/or whether the first terminal device is allowed to relay the first terminal device The data of the second terminal equipment.
  • the network element of the first core network can obtain the authentication and authorization result of the second terminal device, so as to determine whether the second terminal device is legal according to the authentication and authorization result of the second terminal device, or, Whether to relay the data of the second terminal device to ensure security.
  • the authentication and authorization result of the second terminal device further includes: whether the second terminal device matches the controller.
  • the network element of the first core network can simultaneously obtain the legality authentication result of the second terminal device and the authentication authorization of the communication between the second terminal device and the controller, thereby simplifying the authentication process.
  • the method further includes: the first core network element receiving first indication information from the first terminal device, where the first indication information is used to indicate that the first The second terminal device requests to establish communication with the controller; the network element of the first core network determines whether the second terminal device is allowed to communicate with the controller.
  • the network element of the first core network can determine the C2 communication authentication for the second terminal device based on the first indication information, so that the authentication of the communication between the second terminal device and the controller can be independently authenticated Authorization is conducive to supervision.
  • the first core network element determining whether the second terminal device is allowed to communicate with the controller includes: the first core network element according to the second The terminal device authentication and authorization result determines whether the second terminal device is allowed to communicate with the controller; and/or, the first core network element obtains from the service provider whether the second terminal device is allowed to communicate with the controller.
  • the network element of the first core network can determine the C2 communication authentication result for the second terminal device in different ways, which improves the flexibility of the solution.
  • the first core network element obtains from the service provider whether the second terminal device is allowed to communicate with the controller, including: the first core network The element sends a fourth request message to the service provider, and the fourth request message is used to request the service provider to determine whether the second terminal device is allowed to communicate with the controller; the first core network element receives a request from the service provider A fourth response message of the provider in response to the fourth request message, where the fourth response message includes second indication information, where the second indication information is used to indicate whether the second terminal device is allowed to communicate with the controller.
  • the method further includes: the first core network element sending the second indication information to the first terminal device.
  • the method further includes: the first core network element sending a second response message in response to the second request message to the first terminal device, the first The second response message includes the authentication and authorization result of the second terminal device.
  • the network element of the first core network obtains the authentication authorization result of the second terminal device and forwards it to the first terminal device, so that the first terminal device can know the authentication authorization result of the second terminal device result.
  • the first core network element is a session management function element SMF
  • the second request message is a session establishment request message or a session modification request message.
  • the second request message when the second request message is a session establishment request message, the second request message is used to establish a connection between the first terminal device and the service provider and/or the A second session between controllers, where the second session is used to transmit data between the second terminal device and the service provider and/or the controller; or when the second request message is a session modification request message, The second request message is used to request to modify the first session as a session for further transmitting data between the second terminal device and the service provider and/or the controller, before sending the session modification request message , the first session is a session established by the first terminal device for transmitting data between the first terminal device and the service provider and/or the controller.
  • the controller is used to control the second terminal device;
  • the service provider is a third-party entity, and is used to provide services for the first terminal device and the The second terminal device provides the service.
  • a method for relaying communication is provided.
  • the method for relaying communication can be performed by a service provider, or can also be performed by a chip or circuit provided in the service provider, which is not limited in this application .
  • the implementation of the service provider is taken as an example below.
  • the method of relaying communication includes:
  • the service provider receives a third request message from a network element of the first core network, the third request message includes a first identifier, and the first identifier is the identifier of the second terminal device allocated by the service provider; the service provider The provider authenticates and authorizes the second terminal device according to the first identifier, where the second terminal device is a terminal device connected to the Internet through a relay.
  • the service provider can obtain the first identifier of the second terminal device, and perform authentication of the second terminal device according to the first identifier. In this way, the authentication and authorization of remote terminal equipment in the relay scenario is realized, and the Remote UE relay networking is realized under the premise of ensuring security.
  • the method further includes: the service provider sends a third response message in response to the third request message to the first core network element, and the third The response message includes the authentication and authorization result of the second terminal device, wherein the authentication and authorization result of the second terminal device includes whether the second terminal device is legal, and/or whether the first terminal device is allowed to relay the second terminal device. data from the terminal device.
  • the authentication and authorization result of the second terminal device further includes: whether the second terminal device matches the controller.
  • the network element of the first core network can simultaneously obtain the legality authentication result of the second terminal device and the authentication authorization of the communication between the second terminal device and the controller, thereby simplifying the authentication process.
  • the method further includes: the service provider receives a fourth request message from the network element of the first core network; the service provider receives the fourth request message according to the fourth request message determining whether the second terminal device is allowed to communicate with the controller; the service provider sends a fourth response message corresponding to the fourth request message to the first core network element, and the fourth response message includes second indication information , the second indication information is used to indicate whether the second terminal device is allowed to communicate with the controller.
  • the service provider can independently authenticate the authentication authorization of the communication between the second terminal device and the controller, which is beneficial to supervision.
  • a method for relaying communication is provided.
  • the method for relaying communication may be executed by the first terminal device, or may also be executed by a chip or circuit provided in the first terminal device. Not limited.
  • the execution of the first terminal device is used as an example for description below.
  • the first terminal device sends capability information to the service provider, and the capability information is used to indicate the capability of the first terminal device to relay data of other terminal devices; the first terminal device receives the relay service code from the service provider, the The relay service code is used to indicate that the first terminal device is allowed to relay data of other terminal devices.
  • the first terminal device acquires a relay service code based on capability information. After the first terminal device obtains the relay service code, the second terminal device can connect to the network through the relay, and realize the relay networking of the second terminal device under the premise of simplifying the process.
  • the method further includes: the first terminal device sends the identifier of the second terminal device, and/or the identifier of the terminal device system to the supplier of the terminal device , wherein the second terminal device is a terminal device connected to the Internet through a relay.
  • a method for relaying communication is provided.
  • the method for relaying communication can be executed by the second terminal device, or can also be executed by a chip or circuit provided in the second terminal device. Not limited.
  • the execution of the second terminal device is used as an example for description below.
  • the method of relaying communication includes:
  • the second terminal device obtains a relay service code, where the relay service code is used to indicate that the first terminal device is allowed to relay data of other terminal devices; the second terminal device discovers the first terminal device according to the relay service code.
  • the second terminal device relays networking according to the relay service code, and realizes the relay networking of the second terminal device under the premise of simplifying the process.
  • the method further includes: the second terminal device transmits the data of the second terminal device through a session, where the session is established by the first terminal device to transmit the second A session of end-device data.
  • a method for relaying communication is provided, and the method for relaying communication may be performed by a service provider, or may also be performed by a chip or a circuit provided in the service provider, which is not limited in this application .
  • the implementation of the service provider is taken as an example below.
  • the method of relaying communication includes:
  • the service provider receives capability information from the first terminal device, where the capability information is used to indicate the capability of the first terminal device to relay data from other terminal devices; the service provider sends a relay service code to the first terminal device, the The relay service code is used to indicate that the first terminal device is allowed to relay data of other terminal devices.
  • the first terminal device acquires a relay service code based on capability information. After the first terminal device obtains the relay service code, the second terminal device can connect to the network through the relay, and realize the relay networking of the second terminal device under the premise of simplifying the process.
  • the method further includes: the service provider receives an identifier of the second terminal device from the first terminal device, and/or an identifier of the terminal device system, wherein , the second terminal device is a terminal device connected to the Internet through a relay.
  • an apparatus for relaying communication includes a processor configured to implement the functions of the first terminal device in the methods described in the first aspect and the fifth aspect.
  • the apparatus for relaying communication may further include a memory, the memory is coupled to the processor, and the processor is configured to realize the functions of the first terminal device in the methods described in the first aspect and the fifth aspect.
  • the memory is used to store program instructions and data.
  • the memory is coupled to the processor, and the processor can call and execute program instructions stored in the memory, so as to realize the functions of the first terminal device in the methods described in the first aspect and the fifth aspect.
  • the device for relaying communication may also include a communication interface, which is used for the device for relaying communication to communicate with other devices.
  • the communication interface may be a transceiver, an input/output interface, or a circuit.
  • the device for relaying communication includes: a processor and a communication interface
  • the processor is configured to run a computer program, so that the device for relaying communication implements any one of the methods described in the first aspect and the fifth aspect above;
  • the processor communicates with the outside through the communication interface.
  • the external may be an object other than the processor, or an object other than the device.
  • the device for relaying communication is a chip or a chip system.
  • the communication interface may be an input/output interface, an interface circuit, an output circuit, an input circuit, pins or related circuits on the chip or the chip system.
  • the processor may also be embodied as a processing circuit or logic circuit.
  • an apparatus for relaying communication includes a processor configured to implement the functions of the second terminal device in the methods described in the second aspect and the sixth aspect.
  • the apparatus for relaying communication may further include a memory, the memory is coupled to the processor, and the processor is configured to realize the functions of the second terminal device in the methods described in the second aspect and the sixth aspect.
  • the memory is used to store program instructions and data.
  • the memory is coupled with the processor, and the processor can call and execute program instructions stored in the memory, so as to realize the functions of the second terminal device in the methods described in the second aspect and the sixth aspect.
  • the device for relaying communication may further include a communication interface, which is used for the device for relaying communication to communicate with other devices.
  • the communication interface may be a transceiver, an input/output interface, or a circuit.
  • the device for relaying communication includes: a processor and a communication interface
  • the processor communicates with the outside through the communication interface
  • the processor is configured to run a computer program, so that the device for relaying communication implements any one of the methods described in the second aspect and the sixth aspect.
  • the external may be an object other than the processor, or an object other than the device.
  • the device for relaying communication is a chip or a chip system.
  • the communication interface may be an input/output interface, interface circuit, output circuit, input circuit, pin or related circuit on the chip or chip system.
  • the processor may also be embodied as a processing circuit or logic circuit.
  • an apparatus for relaying communication includes a processor configured to implement the function of the first core network element in the method described in the third aspect above.
  • the device for relaying communication may further include a memory, the memory is coupled to the processor, and the processor is configured to realize the function of the first core network element in the method described in the third aspect above.
  • the memory is used to store program instructions and data.
  • the memory is coupled to the processor, and the processor can call and execute program instructions stored in the memory, so as to realize the functions of the first core network element in the method described in the third aspect above.
  • the device for relaying communication may further include a communication interface, which is used for the device for relaying communication to communicate with other devices.
  • the communication interface may be a transceiver, an input/output interface, or a circuit.
  • the device for relaying communication includes: a processor and a communication interface
  • the processor communicates with the outside through the communication interface
  • the processor is configured to run a computer program, so that the device for relaying communication implements any method described in the third aspect above.
  • the external may be an object other than the processor, or an object other than the device.
  • the device for relaying communication is a chip or a chip system.
  • the communication interface may be an input/output interface, interface circuit, output circuit, input circuit, pin or related circuit on the chip or chip system.
  • the processor may also be embodied as a processing circuit or logic circuit.
  • an apparatus for relaying communication includes a processor configured to implement the function of the service provider in the methods described in the fourth aspect and the seventh aspect.
  • the device for relaying communication may further include a memory, the memory is coupled to the processor, and the processor is configured to realize the function of the service provider in the methods described in the fourth aspect and the seventh aspect.
  • the memory is used to store program instructions and data.
  • the memory is coupled with the processor, and the processor can call and execute the program instructions stored in the memory, so as to implement the service provider function in the methods described in the fourth aspect and the seventh aspect.
  • the device for relaying communication may further include a communication interface, which is used for the device for relaying communication to communicate with other devices.
  • the communication interface may be a transceiver, an input/output interface, or a circuit.
  • the device for relaying communication includes: a processor and a communication interface
  • the processor communicates with the outside through the communication interface
  • the processor is configured to run a computer program, so that the device for relaying communication implements any one of the methods described in the fourth aspect and the seventh aspect.
  • the external may be an object other than the processor, or an object other than the device.
  • the device for relaying communication is a chip or a chip system.
  • the communication interface may be an input/output interface, interface circuit, output circuit, input circuit, pin or related circuit on the chip or chip system.
  • the processor may also be embodied as a processing circuit or logic circuit.
  • the present application provides a computer-readable storage medium, where instructions are stored in the computer-readable storage medium, and when the computer-readable storage medium is run on a computer, it causes the computer to execute the methods described in the above aspects.
  • the present application provides a computer program product containing instructions, which, when run on a computer, cause the computer to execute the methods described in the above aspects.
  • a communication system including the device for relaying communication shown in the eighth aspect to the eleventh aspect.
  • a fifteenth aspect provides a chip device, including a processing circuit, the processing circuit is used to call and run a program from a memory, so that a communication device installed with the chip device executes the methods described in the above aspects.
  • FIG. 1 are schematic structural diagrams of a communication system applicable to an embodiment of the present application.
  • FIG. 2 is a schematic diagram of a relay architecture provided by an embodiment of the present application.
  • Fig. 3 is a schematic flowchart of a method for relaying communication provided by the present application.
  • Fig. 4 is a schematic flowchart of another method for relaying communication provided by the present application.
  • Fig. 5 is a schematic flowchart of another method for relaying communication provided by the present application.
  • Fig. 6 is a schematic block diagram of a communication device provided according to an embodiment of the present application.
  • Fig. 7 is another schematic block diagram of a communication device provided according to an embodiment of the present application.
  • the technical solutions of the embodiments of the present application can be applied to various communication systems, such as: the fifth generation (5th generation, 5G) system or new radio (new radio, NR), long term evolution (long term evolution, LTE) system, LTE frequency Division duplex (frequency division duplex, FDD) system, LTE time division duplex (time division duplex, TDD), etc.
  • 5G fifth generation
  • NR new radio
  • long term evolution long term evolution
  • LTE frequency Division duplex frequency division duplex
  • FDD frequency division duplex
  • TDD time division duplex
  • the technical solution provided by this application can also be applied to future communication systems, such as the sixth generation mobile communication system.
  • the technical solution of the embodiment of the present application can also be applied to device to device (device to device, D2D) communication, vehicle-to-everything (V2X) communication, machine to machine (machine to machine, M2M) communication, machine Type communication (machine type communication, MTC), and Internet of things (internet of things, IoT) communication system or other communication systems.
  • D2D device to device
  • V2X vehicle-to-everything
  • M2M machine to machine
  • MTC machine Type communication
  • IoT Internet of things
  • FIG. 1 shows a schematic structural diagram of a communication system to which this embodiment of the present application applies.
  • the communication system shown in (a) in FIG. 1 includes a 5G network architecture based on a service interface.
  • the network architecture may include but not limited to the following network elements (or called functional network elements, functional entities, nodes, devices, etc.):
  • User equipment user equipment, UE
  • 5G radio access network equipment radio access network, NG-RAN
  • access and mobility management function access and mobility management function, AMF
  • session management function session management function, SMF
  • user plane function user plane function, UPF
  • unified data management unified data management, UDM
  • data network data network, DN
  • authentication server function authentication server function, AUSF
  • network data analysis function network data analytics function, NWDAF
  • capability exposure function network exposure function
  • NEF network exposure function
  • NEF network exposure function
  • NRF policy control function device
  • application function application function, AF
  • UE A terminal communicating with (R)AN, also called terminal equipment, access terminal, subscriber unit, subscriber station, mobile station, mobile station (MS), mobile terminal (mobile terminal, MT), remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device.
  • R A terminal communicating with (R)AN, also called terminal equipment, access terminal, subscriber unit, subscriber station, mobile station, mobile station (MS), mobile terminal (mobile terminal, MT), remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device.
  • R communicating with
  • R also called terminal equipment, access terminal, subscriber unit, subscriber station, mobile station, mobile station (MS), mobile terminal (mobile terminal, MT), remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device.
  • a terminal device may be a device that provides voice/data connectivity to users, for example, a handheld device with a wireless connection function, a vehicle-mounted device, and the like.
  • examples of some terminals can be: mobile phone (mobile phone), tablet computer (pad), computer with wireless transceiver function (such as notebook computer, palmtop computer, etc.), mobile internet device (mobile internet device, MID), virtual reality (virtual reality, VR) equipment, augmented reality (augmented reality, AR) equipment, wireless terminals in industrial control (industrial control), wireless terminals in self driving (self driving), wireless in remote medical (remote medical) Terminals, wireless terminals in smart grid, wireless terminals in transportation safety, wireless terminals in smart city, wireless terminals in smart home, cellular phones, cordless Telephones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication capabilities, computing devices, or connected Other processing devices to wireless modems, vehicle-mounted devices, wearable devices, terminal devices in the 5G network or terminal devices in the future evolution of the public land mobile network (PLMN), etc.
  • PLMN public land mobile network
  • the terminal device may also be a terminal device in an Internet of Things (Internet of things, IoT) system.
  • IoT Internet of things
  • Its main technical feature is to connect objects to the network through communication technology, so as to realize the intelligent network of human-machine interconnection and object interconnection.
  • IoT technology can achieve massive connections, deep coverage, and terminal power saving through, for example, narrow band (NB) technology.
  • NB narrow band
  • the terminal device may be any device that can access the network.
  • a certain air interface technology may be used to communicate with each other between the terminal device and the access network device.
  • the user equipment can be used as a base station.
  • a user equipment may act as a scheduling entity, which provides sidelink signals between user equipments in V2X or D2D, etc.
  • a cell phone and an automobile communicate with each other using sidelink signals. Communication between cellular phones and smart home devices without relaying communication signals through base stations.
  • NG-RAN It is used to provide network access functions for authorized user equipment in a specific area, and can use transmission tunnels with different service qualities according to the level of user equipment and business requirements.
  • NG-RAN can manage wireless resources, provide access services for user equipment, and then complete the forwarding of control signals and user equipment data between user equipment and the core network.
  • NG-RAN can also be understood as a base station in a traditional network.
  • the access network device in the embodiment of the present application may be any communication device with a wireless transceiver function for communicating with the user equipment.
  • the access network equipment includes but not limited to: evolved Node B (evolved Node B, eNB), radio network controller (radio network controller, RNC), Node B (Node B, NB), base station controller (base station controller) , BSC), base transceiver station (base transceiver station, BTS), home base station (home evolved Node B, HeNB, or home Node B, HNB), baseband unit (baseBand unit, BBU), wireless fidelity (wireless fidelity, WIFI ) system in the access point (access point, AP), wireless relay node, wireless backhaul node, transmission point (transmission point, TP) or transmission and reception point (transmission and reception point, TRP), etc., can also be 5G , such as, NR, gNB in the system, or, transmission point (TRP or TP), one or a group (including multiple antenna panels
  • a gNB may include a centralized unit (CU) and a DU.
  • the gNB may also include an active antenna unit (AAU).
  • the CU implements some functions of the gNB, and the DU implements some functions of the gNB.
  • the CU is responsible for processing non-real-time protocols and services, and realizing the functions of radio resource control (radio resource control, RRC) and packet data convergence protocol (packet data convergence protocol, PDCP) layer.
  • the DU is responsible for processing physical layer protocols and real-time services, realizing the functions of the radio link control (radio link control, RLC) layer, media access control (media access control, MAC) layer and physical (physical, PHY) layer.
  • the AAU implements some physical layer processing functions, radio frequency processing and related functions of active antennas. Since the information of the RRC layer will eventually become the information of the PHY layer, or be transformed from the information of the PHY layer, under this architecture, high-level signaling, such as RRC layer signaling, can also be considered to be sent by the DU , or, sent by DU+AAU.
  • the access network device may be a device including one or more of a CU node, a DU node, and an AAU node.
  • the CU can be divided into access network devices in the access network (radio access network, RAN), and the CU can also be divided into access network devices in the core network (core network, CN). Do limited.
  • UPF network element mainly responsible for processing user packets, such as forwarding, billing, legal interception, etc.
  • the user plane network element may also be called a protocol data unit (protocol data unit, PDU) session anchor (PDU session anchor, PSA).
  • PDU protocol data unit
  • PSA session anchor
  • the user plane network element may be a UPF network element.
  • the user plane network element may still be a UPF network element, or may have other names, which are not limited in this application.
  • DN It is used to provide the network for transmitting data.
  • the data network may be a DN.
  • the data network may still be a DN, or may have other names, which are not limited in this application.
  • AUSF It mainly includes the following functions: the authentication server function, interacts with the unified data management network element to obtain user information, and performs authentication-related functions, such as generating intermediate keys.
  • the authentication server function network element may be an AUSF network element.
  • the authentication server functional network element may still be an AMF network element, or may have other names, which are not limited in this application.
  • AMF network element mainly used for terminal attachment, mobility management, and tracking area update process in the mobile network.
  • the access management network element terminates the non-access stratum (NAS) message, completes registration management, Connection management and reachability management, allocation of tracking area list (track area list, TA list) and mobility management, etc., and transparent routing of session management (session management, SM) messages to session management network elements.
  • NAS non-access stratum
  • the access management network element may be an AMF network element.
  • the access management network element may still be an AMF network element, or may have other names, which are not limited in this application.
  • SMF mainly used for session management, Internet Protocol (IP) address allocation and management of terminal equipment, selection of manageable user plane functions, endpoints for policy control and charging function interfaces, and downlink data notification.
  • IP Internet Protocol
  • the session management network element may be an SMF network element.
  • the session management network element may still be an SMF network element, or may have other names, which are not limited in this application.
  • PCF including user subscription data management function, policy control function, charging policy control function, quality of service (quality of service, QoS) control, etc.
  • the policy control network element may be a PCF network element.
  • the policy control network element may still be a PCF network element, or may have other names, which are not limited in this application.
  • UDM It can be understood as the naming of unified data management network elements in the 5G architecture.
  • the unified data management network element mainly includes the following functions: unified data management, support for authentication credential processing in the 3GPP authentication and key agreement mechanism, user identity processing, access authorization, registration and mobility management, subscription management, short message management etc.
  • NEF mainly includes the following functions: the services and capabilities provided by the secure and open 3GPP network functions are internally open, or open to third parties, etc.; transform or translate information interacting with AF and information interacting with internal network functions, such as AF Service identification and internal 5G core network information such as data network name (data network name, DNN), single network slice selection assistance information (single network slice selection assistance information, S-NSSAI), etc.
  • NRF mainly includes the following functions: service discovery function, maintaining the NF text of available network function (network function, NF) instances and the services they support.
  • NWDAF from each network function (network function, NF), such as policy control network element, session management network element, user plane network element, access management network element, application function network element (through network capability opening function network element) ) to collect data, analyze and forecast.
  • network function such as policy control network element, session management network element, user plane network element, access management network element, application function network element (through network capability opening function network element)
  • the data analysis network element may be a NWDAF network element.
  • the data analysis network element may still be the NWDAF network element, or may have other names, which are not limited in this application.
  • AF mainly includes the following functions: connection management, mobility management, registration management, access authentication and authorization, reachability management, security context management and other functions related to access and mobility.
  • interfaces between network elements of the control plane in (a) in FIG. 1 are service-oriented interfaces.
  • Nnef, Nnrf, Nnwdaf, Namf, Npcf, Nsmf, and Nudm in (a) in Figure 1 are the service interfaces provided by the above-mentioned NEF, NRF, NWDAF, AMF, PCF, SMF, and UDM, respectively, and are used to call the corresponding Servicing operations.
  • N1, N2, N3, N4, and N6 are interface serial numbers. The meanings of these interface serial numbers may refer to the meanings defined in the third generation partnership project (3rd generation partnership project, 3GPP) standard agreement, and no limitation is made here.
  • the control plane network functional entities of the same network slice can discover each other through the NRF network element, obtain the access address information of the other party, and then They can directly communicate with each other through the control plane signaling bus.
  • interfaces between the control plane network elements in (a) in FIG. 1 may also be point-to-point interfaces, which will not be repeated here.
  • the above-mentioned network element or function may be a network element in a hardware device, or a software function running on dedicated hardware, or a virtualization function instantiated on a platform (for example, a cloud platform).
  • the network element with the session management function is the SMF network element
  • the data analysis network element is the NWDAF network element as an example for description.
  • the SMF network element is referred to as SMF for short
  • the NWDAF network element is referred to as NWDAF for short. That is, the SMF described later in this application can be replaced by a session management function network element, and the NWDAF can be replaced by a data analysis function network element.
  • this application takes the devices as SMF entities and NWDAF entities as examples to describe the relay communication.
  • devices For the implementation methods of devices as chips in SMF entities and chips in NWDAF entities, you can refer to the devices as SMF The specific description of entities and NWDAF entities will not be repeated.
  • network function network element entities such as AMF network elements, SMF network elements, PCF network elements, AF network elements, and UDM network elements are called network function network elements (network function network elements).
  • network function network elements network function network elements
  • NF network function network elements
  • a collection of network elements such as AMF network elements, SMF network elements, PCF network elements, AF network elements, and UDM network elements can be called control plane functional network elements.
  • (a) in FIG. 1 is a communication system applicable to the embodiment of the present application.
  • UAV uncrewed aerial vehicles
  • drones may also provide temporary communication services, that is, wireless access nodes are carried on drones, which are often used in major events such as live football matches, or emergency events such as earthquakes and tsunamis.
  • wireless access nodes are carried on drones, which are often used in major events such as live football matches, or emergency events such as earthquakes and tsunamis.
  • 3GPP is discussing issues related to UAV networking, which can solve the problems of identification, authorization and tracking when remotely controlling UAVs.
  • UAS service supplier provides services for UAVs to use the airspace safely and effectively, and is responsible for UAV authentication authorization, command and control (command and control, C2) communication authentication authorization, UAV Identification and tracking, etc.
  • a UAV is a type of UE, and may also be called a UE.
  • UAS is an uncrewed aerial system (UAS).
  • FIG. 1 shows a schematic structural diagram of a communication system to which this embodiment of the present application applies.
  • the network architecture may include but not limited to the following network elements (or called functional network elements, functional entities, nodes, devices, etc.):
  • UE 4G access network ((R)AN), NG-RAN, 5G core network (5G core, 5GC), 4G core network (evolved packet core, EPC), UAS, USS, DN and third-party authorized entities (third party authorized entity, TPAE).
  • R access network
  • NG-RAN 5G core network
  • 5G core 5G core
  • 5GC 4G core network
  • EPC evolved packet core
  • UAS UAS
  • USS DN
  • third-party authorized entities third party authorized entity, TPAE
  • the description of network elements such as UE, NG-RAN, 5GC can be Refer to the description in (a) in FIG. 1; the description of network elements such as (R)AN, EPC, and TPAE can refer to the description in the current 4G network related technologies, and will not be repeated in this application.
  • This application mainly introduces USS and UAS.
  • UAS includes UAV and UAV controller, for example, UAS includes a UAV and a UAV controller.
  • USS A third-party entity or network element that provides services for the safe and effective use of airspace by UAVs. It is responsible for UAV authentication and authorization, C2 communication authentication and authorization, and UAV identification and tracking. Wherein, the UAV is a kind of UE, and may also be referred to as UE.
  • the USS can be set up together with the DN (for example, the USS can be regarded as a function in the DN), and it can also be set up together with the AF (for example, the USS can be regarded as a function in the AF), or the USS can also be set up independently.
  • the DN for example, the USS can be regarded as a function in the DN
  • the AF for example, the USS can be regarded as a function in the AF
  • the USS can also be set up independently.
  • the USS may also be called a UAS traffic management (UAS traffic management, UTM) entity or network element, or other names.
  • UAS traffic management UTM
  • UTM UAS traffic management
  • the UAV expects to communicate with the UAV controller (uncrewed aerial vehicle controller, UAVc) on the Internet, it first needs to perform authentication and authorization of the UAV, that is, to judge whether the UAV itself is legal, and then to authorize the C2 communication, that is, to judge whether Allow UAV and UAVc communication and other possible authorization, such as whether the flight path is legal.
  • UAV controller uncrewed aerial vehicle controller
  • UAV authentication and authorization can be performed in the registration process, and can also be performed in the session establishment process; C2 communication authorization is performed in the session establishment or modification process.
  • the UAV needs to establish a session to the USS for position identification and position reporting, and the UAV needs to establish a session to the UAVc for control and command. If the authentication and authorization of the UAV is performed in the session establishment process, it can be performed in the session establishment process from the UAV to the USS. Authorization of C2 communication may be performed during UAV to UAVc session establishment or modification.
  • the session from the UAV to the USS and the session from the UAV to the UAVc may be the same session or different sessions. If the UAV-to-USS session and the UAV-to-UAVc session are the same session, and UAV authentication and authorization are performed during the session establishment process, UAV authentication and authorization and C2 communication authorization may be performed at the same time.
  • multiple drones may work together, such as: drone cruise, disaster relief, performances, etc.
  • one or some of the drones has strong capabilities and can transmit the data of other drones to the controller or server, that is, drone relay is a possible scenario.
  • the system architecture shown in Figure 2 can be understood as a relay architecture.
  • the UAV relay scenario it includes the following two types of UAVs:
  • Remote UE is a UE with short-distance communication capabilities, and can be understood as a UE connected to the Internet through a relay.
  • Remote UAV refers to a UAV connected to the Internet through relay.
  • the other is a relay terminal device (UE-to-Network Relay UE) that is connected to the network through the terminal device.
  • the UE-to-Network Relay UE is also a UE with short-distance communication capabilities and supports Remote UE networking, that is, the Remote UE passes through UE-to-Network Relay UE networking, that is, relay.
  • it is also called UE-to-Network Relay UAV, or simply Relay UAV, which refers to relay UAV.
  • the user plane connection used to transmit control and command messages may be understood as a link in which the controller controls the UAV in the embodiment of the present application.
  • the authorization of C2 communication refers to judging whether to allow UAV and UAVc communication.
  • the authorization of the C2 communication involved in the embodiment of the present application is performed during the establishment or modification of the session from the UAV to the UAVc.
  • the authorization of C2 communication stipulated in the current agreement (for example, 3GPP TS 23.502) mainly refers to the authorization process of C2 communication corresponding to a certain UAV, and does not involve how to realize the authorization through the Relay UAV in the relay scenario shown in Figure 2.
  • This application does not specifically describe the authorization process of the C2 communication corresponding to a certain UAV, and can refer to the description in the current agreement.
  • the authorization of the C2 communication for a certain UAV is performed during the session establishment or modification from the UAV corresponding to the UAV to the UAVc.
  • the UAV identifier assigned by the USS uniquely identifies the UAV within the scope of USS management.
  • the USS management scope includes 3 UAVs (such as UAV#1, UAV#2 and UAV#3), and the USS assigns 3 CAA-Level UAV IDs to the 3 UAVs respectively (such as, CAA-Level UAV ID# 1. CAA-Level UAV ID#2 and CAA-Level UAV ID#3), where CAA-Level UAV ID#1 is used to identify UAV#1, CAA-Level UAV ID#2 is used to identify UAV#2, CAA -Level UAV ID#3 is used to identify UAV#3.
  • the Relay UE needs to be authorized to relay the data of the Remote UE, and it is determined in the PCF or UDM or DN that the Relay UE transmits the data of the specified Remote UE.
  • the authentication of the Remote UE is authorized whether the Relay UE can relay the data of the Remote UE.
  • the Remote UE is regarded as a normal UE, and no third party (such as USS) is required for further authentication and authorization, and no further authentication and authorization is required for the Remote UE and the Remote UE.
  • the communication services of other UEs are authorized (for example, the authorization of C2 communication).
  • UAV authentication and authorization USS UAV authorization/authentication, UUAA.
  • UUAA refers to judging whether the UAV itself is legal.
  • UUAA can be performed during the registration process, and can also be performed during the session establishment process.
  • the embodiment of the present application mainly involves the execution of UUAA in the session establishment process, and does not describe the process of executing UUAA in the registration process.
  • the UUAA stipulated in the current agreement mainly refers to the UUAA process corresponding to a certain UAV, and does not involve how to implement UUAA to the Remote UAV through the Relay UAV in the relay scenario shown in Figure 2.
  • the UUAA for a UAV is executed during the establishment of a PDU session corresponding to the UAV.
  • for indication may include both direct indication and indirect indication.
  • indication information for indicating A it may include that the indication information directly indicates A or indirectly indicates A, but it does not mean that A must be included in the indication information.
  • the "storage" mentioned in the embodiment of the present application may refer to storage in one or more memories.
  • the one or more memories may be provided independently, or may be integrated in an encoder or decoder, a processor, or a communication device.
  • a part of the one or more memories may also be provided separately, and a part may be integrated in a decoder, a processor, or a communication device.
  • the type of the storage may be any form of storage medium, which is not limited in this application.
  • the "protocol” involved in the embodiment of the present application may refer to a standard protocol in the communication field, for example, may include LTE protocol, NR protocol and related protocols applied in future communication systems, which is not limited in this application.
  • the current protocol does not specify how to implement remote UAV (Remote UAV) UAV authentication authorization and C2 communication authorization in the relay scenario.
  • the present application provides a relay communication method, which can realize authentication and authorization of terminal equipment and authorization of C2 communication in a relay scenario.
  • the embodiments shown below do not specifically limit the specific structure of the execution subject of the method provided in the embodiment of the application, as long as the program that records the code of the method provided in the embodiment of the application can be executed according to the application
  • the method provided in the embodiment is sufficient for communication.
  • the execution subject of the method provided in the embodiment of the present application may be a terminal device or a core network device, or a functional module in a terminal device or a core network device that can call a program and execute the program .
  • Fig. 3 is a schematic flowchart of a method for relaying communication provided by the present application. Include the following steps:
  • the second terminal device sends a first request message to the first terminal device, or the first terminal device receives the first request message from the second terminal device.
  • the first request message includes a first identifier, where the first identifier is an identifier allocated by a service provider for identifying the second terminal device.
  • the first terminal device can be understood as a Relay UE, which is used to support the networking of the second terminal device (such as Remote UE), for example, the Relay UE is used to relay the Remote UE to the service provider and/or controller
  • the data of the Relay UE relaying the data of the Remote UE shown in the following can be understood as the data of the Relay UE relaying the Remote UE to the service provider and/or controller.
  • the terminal device is UAV as an example for illustration. Above-mentioned first terminal equipment is Relay UAV, and second terminal equipment is Remote UAV.
  • the method of relay communication is described by taking "Remote UE” as Remote UAV and “Relay UE” as Relay UAV as an example, which is just an example, and does not constitute any limitation on the protection scope of this application.
  • the UAV can also be replaced by other terminal devices (such as smart phones, smart wearable devices, etc.), which is not limited in this application.
  • the first identifier included in the first request message is an identifier assigned by the service provider to uniquely identify the second terminal device within the management scope of the service provider.
  • the second terminal device is Remote UAV
  • the service provider is USS.
  • the above-mentioned first identification is the CAA-Level UAV ID allocated by the USS for the Remote UAV.
  • the specific form of the CAA-Level UAV ID is not limited, and it can be used to identify the Remote UAV within the scope of USS management.
  • the CAA-Level UAV ID can be the serial number of the Remote UAV, the registration identifier issued by the CAA, or the universally unique identifier (UUID) issued by the USS.
  • the terminal device can also be other devices except drones, then the above-mentioned service provider can be a provider other than USS that provides services for the terminal device. This is not limited.
  • the first request message may be a direct communication request (direct communication request) message sent by the Remote UAV to the Relay UAV, and the direct communication request message carries the CAA-Level UAV ID allocated by the USS for the Remote UAV.
  • direct communication request direct communication request
  • the first request message can also be other messages sent by the Remote UAV to the Relay UAV.
  • whether the first request message is an existing message or a new message between the Remote UAV and the Relay UAV is not limited.
  • the first request message may further include address information of the service provider (for example, address information of the USS), and/or an identifier of the controller (for example, an identifier of the UAVc).
  • address information of the service provider for example, address information of the USS
  • an identifier of the controller for example, an identifier of the UAVc.
  • the USS is the USS serving the Remote UAV
  • the UAVc is the UAVc that the Remote UAV expects to match, that is, the UAVc is used to control the Remote UAV.
  • the address information of the USS may be IP address information of the USS, or other information that can be used to address the USS, which is not limited in this application.
  • the identification of UAVc can be the identification that is used for 3GPP system identification UAVc such as general public subscription identity (generic public subscription identity, GPSI), or the identification such as CAA-Level UAVc ID that is used for USS identification UAVc, or IP address information , or other information that can be used to identify the UAVc, which is not limited in this application.
  • 3GPP system identification UAVc such as general public subscription identity (generic public subscription identity, GPSI)
  • CAA-Level UAVc ID that is used for USS identification UAVc
  • IP address information IP address information
  • the method shown in FIG. 3 may further include:
  • the second terminal device establishes a connection with the first terminal device.
  • the Remote UAV discovers a Relay UAV that can provide relay services for the Remote UAV according to certain characteristics (for example, the Remote UAV and the Relay UAV are in the same communication group, or use the same application or service).
  • a Relay UAV broadcasts a first relay service code (relay service code, RSC), and if a Remote UAV can recognize the first RSC, it can try to establish a connection with the Relay UAV.
  • RSC relay service code
  • the Remote UAV broadcasts the second RSC.
  • the Relay UAV broadcasts a reply message or sends a reply message to the Remote UAV.
  • the reply message can carry the second RSC that it can support, and the Remote UAV receives the Reply to the message to determine whether to establish a connection with the Relay UAV.
  • the above-mentioned method of judging whether to establish a connection with the Relay UAV by identifying the RSC is just an example to illustrate how the Remote UAV establishes a connection with the Relay UAV, and does not constitute any limitation to the protection scope of the application.
  • the UAV establishes a connection with the Relay UAV.
  • the Remote UAV can also establish a connection with the Relay UAV in other ways, for example, according to the historical transmission path or according to the instructions of the manager, etc., which will not be described here.
  • the first terminal device needs to send a second request message to the network element of the first core network, so that the second terminal device can communicate with the service provider and/or the controller, as shown in FIG.
  • the method shown in 3 may also include:
  • the first terminal device sends a second request message to the first core network element, or the first core network element receives the second request message from the first terminal device.
  • the second request message includes the above-mentioned first identifier.
  • the second request message is used to request to establish communication between the second terminal device and the controller controlling the second terminal device and/or the service provider.
  • the controller is used to control the second terminal device, and the service provider may be understood as a third party entity, which is used to provide services for the first terminal device and the second terminal device.
  • the second request message requests to establish a session for an uncrewed aerial system (uncrewed aerial system, UAS) service.
  • UAS uncrewed aerial system
  • the UAS service refers to the service provided for UAV to communicate with USS, communicate with UAVc, and so on. That is, sessions for UAS services include UAV-to-USS sessions and/or UAV-to-UAVc sessions.
  • the second request message is used to request the first core network element to initiate an authentication process for the second terminal device
  • the second request message is used to request the first core network element to initiate a session establishment process for communication with the second terminal device.
  • the first core network element involved in this embodiment of the present application may be a session management function network element.
  • the network element with the session management function may be an SMF, or other network elements capable of implementing the session management function, and the name of the network element is not limited in this embodiment of the application.
  • the second request message may be a request message for requesting modification or establishing a session, and the session is used for communication between the second terminal device and the service provider and/or for communication between the second terminal device and the controller.
  • the network element of the first core network can establish a connection between the first terminal device and the service provider and/or the controller according to the second request message.
  • a second session is used for transmitting data between the second terminal device and the service provider and/or the controller.
  • the network element of the first core network can modify the first session according to the second request message to be used to transmit the first terminal device and the A data session between the service provider and/or the controller and a data session between the second terminal device and the service provider and/or the controller, wherein the first session is sending the The session for transmitting data between the first terminal device and the service provider and/or the controller established by the first terminal device before the session modification request message.
  • the second request message requests to modify or establish a PDU session for communication between the Remote UAV and the USS, and information such as remote identification, UAV positioning and tracking can be transmitted between the two through the session; or the second The PDU session requested by the request message to modify or establish is used for both the communication between the Remote UAV and the USS and the communication between the Remote UAV and the UAVc.
  • the second request message includes the above-mentioned first identifier.
  • CAA-Level UAV ID of Remote UE For example, CAA-Level UAV ID of Remote UE.
  • the first request message carries the address information of the USS
  • the second request message also carries the address information of the USS.
  • the above-mentioned first request message carries the identifier of the UAVc
  • the second request message also carries the identifier of the UAVc.
  • the above-mentioned first request message carries the address information of the USS and the identifier of the UAVc
  • the second request message also carries the address information of the USS and the identifier of the UAVc.
  • the Remote UAV is authenticated and authorized, and at the same time, it is determined whether to allow the Relay UAV to relay the data of the Remote UAV, that is, to determine whether to allow the Relay UAV to relay the Remote UAV to Data from USS and/or UAVc.
  • the first terminal device may have established a PDU session for the first terminal device to communicate with the service provider and/or the controller, and the method shown in FIG. 3 may further include:
  • the first terminal device establishes a first session.
  • This first session is used for the first terminal to communicate with the service provider and/or the controller.
  • the above second request message is a PDU session modification request message.
  • the Relay UAV reuses the first session of the communication between the Relay UAV and the USS and/or UAVc, that is, the session used for the communication between the Remote UAV and the USS and/or UAVc and the session for the communication between the Relay UAV and the USS and/or UAVc Same for the first session.
  • the second request message contains indication information, and the indication information indicates that the session is used for communication between the Remote UAV and the USS and/or UAVc, and indicates the communication between the Relay UAV and the USS and/or UAVc.
  • Communication that is, the session simultaneously transmits the data sent by the Relay UAV to the USS and/or UAVc and the data sent by the Remote UAV to the USS and/or UAVc.
  • the above-mentioned second request message is a PDU session establishment request message.
  • the Relay UAV does not reuse the first session of communication between the Relay UAV and the USS and/or UAVc.
  • the second request message contains indication information, and the indication information indicates that the session is used for communication between the Remote UAV and the USS and/or UAVc, that is, the session transmission Remote UAV is sent to the USS and/or UAVc The data.
  • the Relay UAV executes the above-mentioned step S320, it is necessary to judge whether it is necessary to initiate session establishment or modification for the authentication and authorization of the Remote UAV, that is, to judge whether it is necessary to send the second request message, which mainly involves determining to send the second request message in the embodiment of the present application.
  • the situation of the request message because if it is determined that the second request message is not sent, it proves that the Relay UAV cannot be realized as the function of the Remote UAV relay communication, and this application mainly considers the authentication of the Remote UAV under the relay scenario, then as shown in Figure 3
  • the method flow also includes:
  • the first terminal device determines to send the second request message.
  • the Relay UAV may determine whether it is necessary to initiate a session establishment or modification request message for the authentication and authorization of the Remote UAV in the following manner:
  • the Relay UAV determines whether the USS serving the Remote UAV is the same as the USS serving the Relay UAV according to the CAA-Level UAV ID provided by the Remote UAV. If they are the same, the second request message needs to be sent; if they are different, the second request message does not need to be sent.
  • the USS serving the Remote UAV is mainly considered to be the same as the USS serving the Relay UAV.
  • the Relay UAV can obtain the USS information by analyzing the CAA-Level UAV ID, and the first request message does not need to carry the address information of the USS.
  • CAA-Level UAV ID provided by the Remote UAV contains USS information during the construction process, and the Relay UAV can know the construction method of the CAA-Level UAV ID. This application explains how the Relay UAV parses the CAA-Level UAV ID Not limited.
  • the Relay UAV determines whether the USS serving the Remote UAV is the same as the USS serving the Relay UAV according to the address information of the USS provided by the Remote UAV. If they are the same, they need to send a second request message; if they are different, they do not need to send a second request message.
  • the USS serving the Remote UAV is mainly considered to be the same as the USS serving the Relay UAV.
  • the address information of the USS needs to be carried in the first request message.
  • the Relay UAV determines whether the UAVc controlling the Remote UAV is the same as the UAVc controlling the Relay UAV according to the UAVc identifier provided by the Remote UAV, and if they are the same, they need to send the second request message; if they are different, they do not need to send the second request message.
  • the UAVc controlling the Remote UAV is mainly considered to be the same as the UAVc controlling the Relay UAV.
  • the first request message needs to carry the identifier of the UAVc.
  • the method flow shown in FIG. 3 also includes:
  • the network element of the first core network queries subscription information and/or acquires policy information.
  • the SMF queries subscription information or acquires policy information from the UDM or PCF.
  • the UDM or PCF is the UDM or PCF that serves the Relay UAV
  • the subscription information and/or policy information also includes indication information indicating whether the Relay UAV is allowed to relay the data of other UAVs, that is, indicating whether to allow Following the data information from other UAVs to the USS and/or UAVc
  • the UDM or PCF serving the Relay UAV is the same as the UDM or PCF serving the Remote UAV in this implementation.
  • UDM or PCF is the UDM/PCF serving Remote UAV
  • the subscription information and/or policy information also includes indication information indicating whether the Remote UAV is allowed to be relayed by other UAVs, that is, indicating whether to allow
  • the UDM or PCF serving the Relay UAV is different from the UDM or PCF serving the Remote UAV for the data information relayed by other UAVs to the USS and/or UAVc.
  • SMF may communicate with UDM or PCF serving Remote UAV in various ways to query subscription information and/or policy information. This application does not limit how SMF communicates with UDM or PCF serving Remote UAV, which may be direct or indirect.
  • the method flow shown in Figure 3 also includes:
  • the first core network element sends a third request message to the service provider, or the service provider receives the third request message from the first core network element.
  • the third request message is used to request the USS to authenticate and authorize the validity of the Remote UAV, that is, the Remote UAV can realize relay networking only after the authentication and authorization succeeds.
  • the third request message is also used to request the USS to determine whether to allow the Relay UAV to relay the data of the Remote UAV, that is, whether to allow the Relay UAV to relay the data from the Remote UAV to the USS and/or UAVc.
  • the third request message is also used to request the USS to authorize the Remote UAV to match the UAVc, that is, to allow the UAVc to control the Remote UAV.
  • the third request message may be called a certificate authorization request message, or may also be called an authentication request message, etc., and the type and name of the message are not limited in this embodiment of the present application.
  • the CAA-Level UAV ID of the Remote UAV is included in the authentication authorization request message.
  • the authentication authorization request message also includes the identifier of the Relay UAV and/or the address information of the Remote UAV.
  • the identification of Relay UAV refers to the identification used by 3GPP system to identify Relay UAV, such as GPSI, or the identification used by USS to identify Relay UAV, such as CAA-Level UAV ID, or IP address information, or other information that can be used to identify Relay UAV
  • the address information of the Remote UAV refers to the IP address information of the Remote UAV, or other information that can be used to address the Remote UAV, which is not limited by this application.
  • the authentication authorization request message may also include the UAVc identifier.
  • the method flow shown in Figure 3 also includes:
  • the service provider determines an authentication and authorization result of the second terminal device.
  • the authentication and authorization result of the Remote UAV includes whether the Remaote UAV is legal, and/or, whether the Relay UAV can relay the data of the Remote UAV, that is, whether the data of the Remote UAV can be relayed to the USS and/or UAVc.
  • the authentication and authorization result of the second terminal device also includes: whether the Remote UAV matches the UAVc.
  • the USS determines whether to allow the Remote UAV to match the UAVc.
  • the USS determines whether to allow the Remote UAV to match the UAVc controlling the Relay UAV.
  • the USS determines whether to allow the Relay UAV to relay the data of the Remote UAV.
  • the USS needs to send the authentication and authorization result of the Remote UAV to the SMF, and the method flow shown in Figure 3 also includes:
  • the service provider sends a third response message to the first core network element, or the first core network element receives the third response message from the service provider.
  • the third response message is in response to the above-mentioned third request message, and includes the authentication and authorization result of the Remote UAV.
  • the third response message includes address information of the UAVc.
  • the third response message may explicitly or implicitly indicate whether the Remote UAV is allowed to match the UAVc.
  • the explicit indication means that there is a separate indication, for example, the third response message contains indication information, and the indication information is used to indicate whether the Remote UAV is allowed to match UAVc;
  • the implicit indication means that there is no individual indication, for example, the first If the response message does not include an independent instruction, it means that the Remote UAV is allowed to match UAVc, or if the address information of UAVc is included in the message, it means that the Remote UAV is allowed to match UAVc.
  • the third response message may explicitly or implicitly indicate whether the Remote UAV is allowed to match the UAVc controlling the Relay UAV.
  • the explicit indication means that there is a separate indication
  • the third response message contains indication information, and the indication information is used to indicate whether the Remote UAV is allowed to match the UAVc controlling the Relay UAV;
  • the implicit indication means that there is no separate indication . For example, if no independent indication is included in the third response message, it means that the Remote UAV is allowed to match the UAVc controlling the Relay UAV.
  • the third response message may explicitly or implicitly indicate whether the Relay UAV is allowed to relay the data of the Remote UAV.
  • the explicit indication means that there is a separate indication, for example, the third response message contains indication information, and the indication information is used to indicate whether the Relay UAV is allowed to relay the data of the Remote UAV;
  • the implicit indication means that there is no separate indication For example, if no independent indication is included in the third response message, it means that the Relay UAV is allowed to relay the data of the Remote UAV.
  • the third response message may contain both the authentication and authorization result of the Remote UAV and one or more indication information.
  • multiple results are fused into an independent indication information, that is, indicating whether the Relay UAV is allowed to relay the data of the Remote UAV, which implicitly includes information such as whether the authentication and authorization of the Remote UAV is successful.
  • authentication and authorization results and indication information are collectively referred to as authentication and authorization results, and no distinction is made.
  • the USS provides the address information of the Remote UAV to the UAVc or the core network element on the UAVc side.
  • the SMF obtains the authentication and authorization result of the above-mentioned Remote UAV, it can notify the Relay UAV through the second response message, and the method flow shown in Figure 3 also includes:
  • the first core network element sends a second response message to the first terminal device, or the first terminal device receives the second response message from the first core network element.
  • the second response message is used to respond to the second request message.
  • the second response message includes the authentication and authorization result of the Remote UAV.
  • the SMF sends a session establishment or modification rejection message to the Relay UAV, and the message contains a rejection reason value.
  • the reason value may be that the Remote UAV authentication and authorization failed, or the Relay UAV is not allowed to relay the data of the Remote UAV, etc. .
  • the SMF configures the address information of UAVc in the UPF.
  • the session can be used for communication from the Remote UAV to the USS , also used for communication from Remote UAV to UAVc.
  • the SMF if the Remote UAV authentication and authorization result is successful, the SMF establishes a rule in the UPF, and the rule is used for the Remote UAV and USS and/or UAVc The communication between them, that is, the detection and forwarding rules of uplink and downlink data;
  • the SMF updates the rules in the UPF, and the rules are used for communication between the Relay UAV and the USS and/or UAVc and Communication between Remote UAV and USS and/or UAVc, that is, rules such as detection and forwarding of uplink and downlink data.
  • step S321 SMF establishes rules in UPF, and described rules are used for the communication between Relay UAV and USS and/or UAVc
  • step S342 SMF adds rules in UPF, and described rules are used for Remote Communication between UAV and USS and/or UAVc.
  • the method flow shown in Figure 3 also includes:
  • the first terminal device sends a first response message to the second terminal device.
  • the first response message is used to respond to the first request message.
  • the first response message includes the authentication and authorization result of the Remote UAV.
  • the Relay UAV can relay the data from the Remote UAV to the UAVc or the data from the USS through the PDU session.
  • the authentication and authorization result of the second terminal device in the method flow shown in Figure 3 may include whether the second terminal device is matched to the controller, or may not include whether the second terminal device is matched to the controller, that is, the C2 authentication authorization may be one-time Authorization may not be a one-time authorization.
  • this application also provides another method of relay communication, as shown in Figure 4, which is another method provided by this application.
  • the second terminal device sends the first indication information to the first terminal device, or the first terminal device receives the first indication information from the second terminal device.
  • the first indication information is used to indicate that the Remote UAV requests to establish communication with the controller.
  • the communication requested by the second terminal device to establish with the controller is C2 communication as an example.
  • the terminal device is a device other than the UAV
  • the second terminal device may request to establish communication with the controller by another name, which is not limited in this application. That is to say, the first indication information is used to indicate that the C2 communication is requested.
  • the Remote UAV has completed the authentication and authorization of whether the Remote UAV is legal through the registration process or the process shown in Figure 3, but the C2 communication authentication authorization is not a one-time authorization, and C2 communication authentication authorization is required for each flight.
  • the first indication information may be carried in a direct communication request (direct communication request) message between the Remote UAV and the Relay UAV, and the first indication information indicates that the Remote UAV expects to establish C2 communication.
  • the second terminal device may also send at least one of the following information to the first terminal device:
  • the identification of Remote UAV may be the identification such as GPSI that is used for 3GPP system identification Remote UAV, or the identification such as CAA-Level UAV ID that is used for USS identification Remote UAV, or other information that can be used for identification Remote UAV, in this embodiment
  • the USS is the USS serving the Remote UAV.
  • the UAVc is the UAVc that the Remote UAV expects to match, that is, the UAVc is used to control the Remote UAV.
  • the address information of the USS may be IP address information of the USS, or other information that can be used to address the USS, which is not limited in this application.
  • the identification of UAVc can be the identification that is used for 3GPP system identification UAVc such as general public subscription identity (generic public subscription identity, GPSI), or the identification such as CAA-Level UAVc ID that is used for USS identification UAVc, or IP address information , or other information that can be used to identify the UAVc, which is not limited in this application.
  • 3GPP system identification UAVc such as general public subscription identity (generic public subscription identity, GPSI)
  • CAA-Level UAVc ID that is used for USS identification UAVc
  • IP address information IP address information
  • the method shown in Figure 4 may also include:
  • the first terminal device sends the first indication information to the first core network element, or the first core network element receives the first indication information from the first terminal device.
  • the first indication information may be carried in a request message for requesting establishment or modification of a PDU session, and the PDU session requested for modification or establishment is used for C2 communication of the Remote UAV.
  • the first terminal device may have established a first session for the first terminal device to communicate with the service provider and/or the controller, as shown in step S321 in FIG. 3 , which will not be repeated here.
  • the first indication information may be carried in a PDU session modification request message in which the Relay UAV initiates a session modification process.
  • the Relay UAV reuses the first session of the communication between the Relay UAV and the USS and/or UAVc, that is, the session used for the communication between the Remote UAV and the USS and/or UAVc and the session for the communication between the Relay UAV and the USS and/or UAVc Same for the first session.
  • the first indication information may be carried in the PDU session establishment request message of the Relay UAV initiating the session establishment process.
  • the Relay UAV does not reuse the first session of communication between the Relay UAV and the USS and/or UAVc.
  • the first terminal device may also send at least one of the following information to the network element of the first core network:
  • C2 communication indication information flight plan information, Remote UAV identification, UAVc identification and USS address information.
  • DNN and/or S-NSSAI can be used to identify the C2 communication session, and the specific form of the above-mentioned first indication information can be DNN and/or S-NSSAI.
  • a separate information element is added to the request message for establishing or modifying a PDU session to indicate C2 communication.
  • the first terminal device may send the flight plan information to a network element of the first core network after receiving the flight plan information.
  • a new session is established for C2 communication, and the first terminal device sends the identifier of the Remote UAV to the network element of the first core network.
  • the first terminal device may send the UAVc identifier to a network element of the first core network after receiving the UAVc identifier.
  • the first terminal device may send the address information of the USS to a network element of the first core network.
  • the method flow shown in FIG. 4 also includes:
  • the first core network element determines whether the second terminal device is allowed to communicate with the controller.
  • whether the second terminal device is allowed to communicate with the controller may be referred to as the C2 authentication and authorization result of the Remote UAV.
  • the SMF may determine the C2 authentication and authorization results of the Remote UAV in the following ways:
  • the SMF It is determined that the C2 authentication and authorization of the Remote UAV failed.
  • the SMF determines that the C2 authentication and authorization of the Remote UAV is successful.
  • the SMF cannot determine the C2 authorization result of the Remote UAV, and needs to further request authorization from the USS.
  • the SMF needs to further determine the C2 authorization result of the Remote UAV based on whether the Remote UAV is successfully authenticated and authorized and whether the Relay UAV is allowed to relay the data of the Remote UAV.
  • the method flow shown in Figure 4 also includes:
  • the network element of the first core network confirms the authentication and authorization result of the second terminal device.
  • the authentication and authorization result of the second terminal device includes: whether the Remote UAV is successfully authenticated and authorized and whether the Relay UAV is allowed to relay the data of the Remote UAV.
  • the SMF may query the above information from other network elements, such as AMF, UDM or NEF, and may also determine the authentication and authorization result of the second terminal device according to the information stored by itself, which is not limited in this application.
  • other network elements such as AMF, UDM or NEF
  • the first core network element sends a fourth request message to the service provider, or the service provider receives the fourth request message from the first core network element.
  • the fourth request message is used to request the service provider to determine whether the Remote UAV is allowed to communicate with the controller, which may be called a C2 authentication authorization request message.
  • the fourth request message includes the aviation information of the Remote UAV and/or the identification of the UAVc provided by the Remote.
  • the fourth request message includes the identifier of the Relay UAV.
  • the service provider needs to determine whether to allow C2 communication, and the method flow shown in FIG. 4 also includes:
  • the service provider determines whether the second terminal device is allowed to communicate with the controller.
  • the USS performs authorization related to the flight path according to the aviation information
  • the USS performs matching-related authorization according to the UAVc identifier; the USS performs relay-related authorization according to the Relay UAV identifier.
  • the method flow shown in FIG. 4 also includes:
  • the service provider sends a fourth response message to the first core network element, or the first core network element receives the fourth response message from the service provider.
  • the fourth response message includes second indication information, where the second indication information is used to indicate whether the second terminal device is allowed to communicate with the controller.
  • the first core network element can determine the C2 authentication and authorization result of the Remote UAV, and/or, the first core network element receives the C2 authentication and authorization result from the service provider, perform the following steps:
  • the network element of the first core network sends the second indication information to the first terminal device.
  • the second indication information is used to indicate whether the second terminal device is allowed to communicate with the controller.
  • Whether the second terminal device is allowed to communicate with the controller may be indicated in an explicit or implicit manner.
  • the message contains indication information, and the indication information is used to indicate whether C2 communication is allowed. Implicit way, that is, there is no obvious indication information.
  • SMF indicates that C2 communication is allowed by sending a session establishment/modification acceptance message, and rejects C2 communication by sending a session establishment/modification rejection message. In the rejection scenario, it can provide a rejection cause value. This application does not limit the method of providing the C2 authorization result.
  • the first terminal device sends second indication information to the second terminal device.
  • the second indication information may be sent explicitly or in an explicit manner.
  • FIG. 5 is a schematic diagram of another method for relay communication provided by the embodiment of the present application Flowchart, including the following steps:
  • the first terminal device sends capability information to the service provider, or the service provider receives capability information from the first terminal device.
  • the capability information is used to indicate the capability of the Relay UAV to relay the data of the Remote UAV.
  • the Relay UAV may also send the identifier of the Remote UAV expected to be relayed, and/or the identifier of the UAS, to the service provider.
  • the Relay UE or UAVc can also send the identification of the UAVc to the service provider.
  • the USS can generate an RSC for the UAVc to control other Remote UAVs and Relay UAVs.
  • the Relay UAV can obtain the above identification through local configuration or Remote UAV reporting.
  • the capability information means that the Relay UAV can relay the data of another UAV.
  • the capability information means that the Relay UAV can relay data of one or more data types from another UAV, where the data types include at least one of the following:
  • C2 communication data for example, data from Remote UAV to UAVc
  • data from Remote UAV to USS data from Remote UAV to USS
  • data related to non-UAV services of Remote UAV or other possible data types, which are not limited in this application.
  • the identification of above-mentioned Remote UAV can be one or more information (as, the CAA-Level UAV ID that USS distributes for Remote UAV for Remote UAV, 3GPP system recognizes the identification of Remote UAV etc.) for identifying Remote UAV, in this embodiment
  • the form of the identification of the UAV is not limited, and will not be repeated here.
  • the identification of the UAS refers to the identification of the UAS where the Relay UAV is located (for example, the 3GPP system recognizes the identification of the UAS), and the form of the identification of the UAS is not limited in this embodiment.
  • Relay UAV provides information to the USS is not limited, for example, it can be any of the following ways:
  • the Relay UAV sends directly to the USS through a message, or the Relay UAV sends to the AMF during the registration process, and then the AMF sends it to the USS indirectly or directly through the NEF, or the Relay UAV sends to the SMF during the session management process, and then the SMF indirectly or through the NEF Send directly to USS, or other possible transmission methods, which are not limited in this application.
  • the identification of UAVc refers to the identification of the UAV controller that can control Relay UAV and Remote UAV simultaneously (as, 3GPP system recognizes the identification of UAVc), the form of the identification of UAVc is not limited in this embodiment.
  • the service provider receives the capability information from the first terminal device, it can determine whether to allow the Relay UAV to relay the data of other UAVs based on the capability information.
  • the situation of permission is mainly considered.
  • the method flow shown in FIG. 5 also includes include:
  • the service provider sends the relay service code to the first terminal device, or the first terminal device receives the relay service code from the service provider.
  • the USS determines whether to allow the Relay UAV to relay the data of other UAVs, and if allowed, provides a relay service code (relay service code, RSC) to the Relay UAV.
  • relay service code relay service code
  • the Relay UAV provides the identifier of the Remote UE in step S510, and the USS determines whether to allow the Relay UAV to relay the data of the Remote UAV.
  • step S510 the Relay UAV provides the identification of the UAS, and the USS determines whether to allow the Relay UAV to relay data of other UAVs in the UAS.
  • the capability information of the relay UAV provided by the Relay UAV in step S510 indicates that the Relay UAV can relay one or more types of data from another UAV, and the USS determines whether to allow the Relay UAV to relay the Relay UAV One or more supported types of data.
  • the USS makes a judgment in combination with the foregoing information.
  • the RSC generated by the USS may be associated with the UAVc (for example, one RSC is bound to one UAVc identifier).
  • the second terminal device can discover the first terminal device according to the relay service code, and the method flow shown in FIG. 5 also includes:
  • the second terminal device discovers the first terminal device according to the relay service code.
  • the RSC is associated with the UAVc identifier
  • the Relay UAV is connected to the Remote UAV, it is necessary to confirm whether the Remote UAV is connected to the UAVc corresponding to the RSC; or,
  • the Remote UAV and the Relay UAV establish a connection through the RSC corresponding to a certain UAVc, the Remote UAV can only connect to the corresponding UAVc through the Relay UAV.
  • the second terminal device may relay data through the first terminal device, specifically:
  • Relay UAV establishes or modifies a session for transmitting Remote UAV data, and Relay UAV transmits Remote UAV data through this session.
  • the Remote UAV can be connected to the Internet through the relay, which simplifies the relay communication process.
  • a PDU session in this application is an example of a PDU session.
  • a PDU session may also be replaced by another session, which is not limited in this application.
  • sequence numbers of the above processes do not mean the order of execution, and the execution order of each process should be determined by its functions and internal logic, and should not constitute any limitation on the implementation process of the embodiment of the present application.
  • the equipment in the existing network architecture is used as an example for illustration (such as network equipment, terminal equipment, etc.). Examples are not limited. For example, devices that can implement the same function in the future are applicable to this embodiment of the application.
  • the methods and operations implemented by the device may also be implemented by the device's A component (such as a chip or a circuit) implements.
  • each network element includes a corresponding hardware structure and/or software module for performing each function.
  • the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed by hardware or computer software drives hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art may use different methods to implement the described functions for each specific application, but such implementation should not be regarded as exceeding the scope of the present application.
  • the device for relaying communication provided by the embodiment of the present application will be described in detail with reference to FIG. 6 and FIG. 7 . It should be understood that the descriptions of the device embodiments correspond to the descriptions of the method embodiments. Therefore, for content that is not described in detail, reference may be made to the method embodiments above. For brevity, some content will not be repeated here.
  • the embodiment of the present application can divide the functional modules of the transmitting end device or the receiving end device according to the above method example, for example, each functional module can be divided corresponding to each function, or two or more functions can be integrated into one processing module middle.
  • the above-mentioned integrated modules can be implemented in the form of hardware or in the form of software function modules. It should be noted that the division of modules in the embodiment of the present application is schematic, and is only a logical function division, and there may be other division methods in actual implementation. In the following, description will be made by taking the division of each functional module corresponding to each function as an example.
  • FIG. 6 is a schematic block diagram of an apparatus 600 provided by an embodiment of the present application.
  • the device 600 includes a transceiver unit 610 and a processing unit 620 .
  • the transceiver unit 610 can implement a corresponding communication function, and the processing unit 620 is used for data processing.
  • the transceiver unit 610 may also be called a communication interface or a communication unit, and when the transceiver unit 610 realizes the function of acquiring information, it may also be called an acquisition unit.
  • the device 600 may further include a storage unit, which may be used to store instructions and/or data, and the processing unit 620 may read the instructions and/or data in the storage unit, so that the device implements the aforementioned method embodiments .
  • a storage unit which may be used to store instructions and/or data
  • the processing unit 620 may read the instructions and/or data in the storage unit, so that the device implements the aforementioned method embodiments .
  • the apparatus 600 can be used to execute the actions performed by the devices (such as the above-mentioned first terminal device, second terminal device, first core network element, service provider, etc.) in the above method embodiments.
  • the apparatus 600 It can be a device or a component that can be configured in the device.
  • the transceiver unit 610 is used to perform operations related to sending and receiving of the device in the method embodiments above
  • the processing unit 620 is used to perform operations related to processing of the device in the method embodiments above.
  • the apparatus 600 is configured to perform the actions performed by the first terminal device in the above method embodiments.
  • the transceiver unit 610 receives a first request message from the second terminal device, where the first request message includes a first identifier, and the first identifier is the ID of the second terminal device assigned by the service provider. logo;
  • the transceiver unit 610 is further configured to send a second request message to the network element of the first core network, the second request message includes the first identifier, wherein the second request message is used to request to establish the second terminal device and control communication between the controller of the second terminal device and/or the service provider and via the first terminal device.
  • the transceiver unit 610 is further configured to receive a second response message from the first core network element in response to the second request message, where the second response message includes the authentication and authorization result of the second terminal device , wherein the authentication and authorization result of the second terminal device includes whether the second terminal device is legal, and/or whether the apparatus 600 allows relaying the data of the second terminal device.
  • the transceiving unit 610 is further configured to receive first indication information from the second terminal device, where the first indication information is used to indicate that the second terminal device requests to establish communication with the controller; the transceiving unit 610 is also configured to It is used for sending the first indication information to the first core network element.
  • the transceiver unit 610 is further configured to receive second indication information from the network element of the first core network, where the second indication information is used to indicate whether the second terminal device is allowed to communicate with the controller; the transceiver unit 610, It is also used to send the second indication information to the second terminal device.
  • the transceiving unit 610 is further configured to send a first response message in response to the first request message to the second terminal device, where the first response message includes an authentication and authorization result of the second terminal device.
  • the processing unit 620 is configured to determine that the service provider serving the second terminal device is the same as the service provider serving the first terminal device, and/or the first terminal device determines to control the first terminal device
  • the controller of the device is the same as the controller controlling the second terminal device.
  • the processing unit 620 determining that the supplier serving the second terminal device is the same as the supplier serving the first terminal device, includes: the processing unit 620 determines the service provider serving the second terminal device according to the first identification The provider is the same as the service provider that serves the apparatus 600; and/or, the first request message further includes address information of the service provider, and the processing unit 620 determines the service that serves the second terminal device according to the address information The provider is the same as the service provider servicing the device 600 .
  • the processing unit 620 determines that the controller controlling the first terminal device is the same as the controller controlling the second terminal device includes: the processing unit 620 determines the controller controlling the apparatus 600 according to the identifier of the controller Same as the controller controlling the second terminal device.
  • the transceiver unit 610 is configured to send capability information to a service provider, where the capability information is used to indicate the capability of the first terminal device to relay data of other terminal devices;
  • the transceiving unit 610 is further configured to receive a relay service code from the service provider, where the relay service code is used to indicate that the first terminal device is allowed to relay data of other terminal devices.
  • the transceiver unit 610 is configured to send the identifier of the second terminal device and/or the identifier of the terminal device system to the supplier of the terminal device, where the second terminal device is a terminal connected to the network through a relay equipment.
  • the apparatus 600 can implement the steps or processes corresponding to the execution of the first terminal device in the method embodiment according to the embodiment of the present application, and the apparatus 600 can include a unit for executing the method executed by the first terminal device in the method embodiment .
  • each unit in the apparatus 600 and other operations and/or functions described above are respectively for realizing the corresponding process of the method embodiment in the first terminal device in the method embodiment.
  • the transceiver unit 610 can be used to execute the transceiver steps in the method, such as steps S311, S310, S321, S320, S342 and S343; the processing unit 620 can be used to execute the method in The processing steps, such as step S322.
  • the transceiver unit 610 can be used to execute the transceiver steps in the method, such as steps S410 , S420 , S440 and S450 .
  • the transceiver unit 610 can be used to execute the transceiver steps in the method, such as steps S510 , S520 and S530 .
  • the apparatus 600 is configured to perform the actions performed by the second terminal device in the above method embodiments.
  • the transceiver unit 610 is configured to acquire a first identifier, where the first identifier is an identifier of the second terminal device assigned by a service provider;
  • the transceiving unit 610 is configured to send a first request message to the first terminal device, where the first request message includes the first identifier, wherein the second terminal device is a terminal device networked through a relay.
  • the transceiver unit 610 is configured to receive a first response message from the first terminal device in response to the first request message, where the first response message includes an authentication and authorization result of the second terminal device, wherein, The authentication and authorization result of the second terminal device includes whether the second terminal device is legal, and/or whether the first terminal device is allowed to relay the data of the second terminal device.
  • the transceiving unit 610 is configured to send first indication information to the first terminal device, where the first indication information is used to indicate that the second terminal device requests to establish communication with the controller.
  • the transceiving unit 610 is configured to receive second indication information from the first terminal device, where the second indication information is used to indicate whether the second terminal device is allowed to communicate with the controller.
  • the transceiver unit 610 is configured to acquire a relay service code, where the relay service code is used to indicate that the first terminal device is allowed to relay data of other terminal devices;
  • the transceiving unit 610 is configured to discover the first terminal device according to the relay service code.
  • the apparatus 600 can implement the steps or processes corresponding to the execution of the second terminal device in the method embodiment according to the embodiment of the present application, and the apparatus 600 can include a unit for executing the method executed by the second terminal device in the method embodiment . Moreover, each unit in the apparatus 600 and other operations and/or functions mentioned above are respectively for realizing the corresponding process of the method embodiment in the second terminal device in the method embodiment.
  • the transceiver unit 610 can be used to execute the transceiver steps in the method, such as steps S311 , S310 and S343 .
  • the transceiver unit 610 can be used to execute the transceiver steps in the method, such as steps S410 and S450.
  • the transceiving unit 610 can be used to execute the transceiving steps in the method, such as step S530.
  • the apparatus 600 is configured to perform the actions performed by the first core network element in the above method embodiments.
  • the transceiver unit 610 is configured to receive a second request message from the first terminal device, where the second request message includes a first identifier, and the first identifier is the second terminal assigned by the service provider. identification of the device;
  • the transceiver unit 610 is configured to send a third request message to the service provider, where the third request message includes the first identifier and the identifier of the first terminal device, and the third request message is used to request the service provider to
  • the second terminal device performs authentication and authorization, where the second terminal device is a terminal device connected to the Internet through a relay.
  • the transceiving unit 610 is configured to receive a third response message from the service provider in response to the third request message, where the third response message includes an authentication and authorization result of the second terminal device, wherein the The authentication and authorization result of the second terminal device includes whether the second terminal device is legal, and/or whether the first terminal device is allowed to relay the data of the second terminal device.
  • the transceiving unit 610 is configured to receive first indication information from the first terminal device, where the first indication information is used to indicate that the second terminal device requests to establish communication with the controller;
  • a processing unit 620 configured to determine whether the second terminal device is allowed to communicate with the controller.
  • the processing unit 620 determining whether the second terminal device is allowed to communicate with the controller includes: the processing unit 620 determining whether the second terminal device is allowed to communicate with the controller according to the authentication authorization result of the second terminal device; And/or, the processing unit 620 acquires from the service provider whether the second terminal device is allowed to communicate with the controller.
  • the transceiver unit 610 is configured to send a fourth request message to the service provider, where the fourth request message is used to request the service provider to determine whether the second terminal device is allowed to communicate with the controller;
  • a transceiver unit 610 configured to receive a fourth response message from the service provider in response to the fourth request message, where the fourth response message includes second indication information, where the second indication information is used to indicate whether the second terminal device Allows communication with this controller.
  • the transceiving unit 610 is configured to send a second response message in response to the second request message to the first terminal device, where the second response message includes an authentication and authorization result of the second terminal device.
  • the apparatus 600 can implement the steps or processes corresponding to the execution of the first core network element in the method embodiment according to the embodiment of the present application.
  • the unit of the method Moreover, each unit in the apparatus 600 and other operations and/or functions mentioned above are respectively for realizing the corresponding process of the method embodiment in the network element of the first core network in the method embodiment.
  • the transceiver unit 610 can be used to execute the transceiver steps in the method, such as steps S321, S320, S330, S341 and S342; the processing unit 620 can be used to execute the processing in the method Step, such as step S323.
  • the transceiver unit 610 can be used to execute the transceiver steps in the method, such as steps S420, S432, S434 and S440; the processing unit 620 can be used to execute the processing steps in the method, such as the steps S431 and S430.
  • the apparatus 600 is configured to perform the actions performed by the service provider in the above method embodiments.
  • the transceiver unit 610 is configured to receive a third request message from a network element of the first core network, where the third request message includes a first identifier, and the first identifier is the An identifier of the second terminal device; a processing unit 620 configured to perform authentication and authorization on the second terminal device according to the first identifier, where the second terminal device is a terminal device networked through a relay.
  • the transceiver unit 610 is configured to send a third response message in response to the third request message to the first core network element, where the third response message includes an authentication and authorization result of the second terminal device, wherein , the authentication and authorization result of the second terminal device includes whether the second terminal device is legal, and/or, whether the first terminal device is allowed to relay the data of the second terminal device.
  • the transceiver unit 610 is configured to receive a fourth request message from the first core network element
  • a processing unit 620 configured to determine whether the second terminal device is allowed to communicate with the controller according to the fourth request message
  • the transceiver unit 610 is configured to send a fourth response message corresponding to the fourth request message to the first core network element, where the fourth response message includes second indication information, and the second indication information is used to indicate the second terminal Whether the device is allowed to communicate with this controller.
  • the transceiver unit 610 is configured to receive capability information from the first terminal device, where the capability information is used to indicate the capability of the first terminal device to relay data of other terminal devices;
  • the transceiving unit 610 is configured to send a relay service code to the first terminal device, where the relay service code is used to indicate that the first terminal device is allowed to relay data of other terminal devices.
  • the apparatus 600 may implement the steps or processes corresponding to the method executed by the service provider in the method embodiment according to the embodiment of the present application, and the apparatus 600 may include a unit for executing the method executed by the service provider in the method embodiment. Moreover, each unit in the apparatus 600 and other operations and/or functions mentioned above are respectively for realizing the corresponding process of the method embodiment in the service provider in the method embodiment.
  • the transceiving unit 610 can be used to execute the transceiving steps in the method, such as steps S330 and S341; the processing unit 620 can be used to execute the processing steps in the method, such as step S340.
  • the transceiving unit 610 can be used to execute the transceiving steps in the method, such as steps S432 and S434; the processing unit 620 can be used to execute the processing steps in the method, such as step S433.
  • the transceiver unit 610 can be used to execute the transceiver steps in the method, such as steps S510 and S520.
  • the processing unit 620 in the above embodiments may be implemented by at least one processor or processor-related circuits.
  • the transceiver unit 610 may be implemented by a transceiver or transceiver-related circuits.
  • the storage unit can be realized by at least one memory.
  • the embodiment of the present application further provides an apparatus 700 .
  • the apparatus 700 includes a processor 710 and may further include one or more memories 720 .
  • the processor 710 is coupled with the memory 720, and the memory 720 is used to store computer programs or instructions and/or data, and the processor 710 is used to execute the computer programs or instructions and/or data stored in the memory 720, so that the methods in the above method embodiments be executed.
  • the apparatus 700 includes one or more processors 710 .
  • the memory 720 may be integrated with the processor 710, or set separately.
  • the apparatus 700 may further include a transceiver 730, and the transceiver 730 is used for receiving and/or sending signals.
  • the processor 710 is configured to control the transceiver 730 to receive and/or send signals.
  • the apparatus 700 is used to implement operations performed by devices (such as the above-mentioned first terminal device, second terminal device, first core network element, service provider, etc.) in the above method embodiments.
  • devices such as the above-mentioned first terminal device, second terminal device, first core network element, service provider, etc.
  • FIG. 7 is only an example rather than a limitation, and the above-mentioned device including a transceiver unit and a processing unit may not depend on the structure shown in FIG. 7 .
  • the chip When the device 700 is a chip, the chip includes a transceiver unit and a processing unit.
  • the transceiver unit may be an input-output circuit or a communication interface;
  • the processing unit is a processor or a microprocessor or an integrated circuit integrated on the chip.
  • the apparatus 700 may also be a system-on-a-chip or a processing system, so that a device installed with the apparatus 700 can implement the methods and functions of the embodiments of the present application.
  • the processing unit can be a processing circuit in a chip system or a processing system, which realizes the control of the device installed with the chip system or processing system, and can also couple and link the storage unit to call the instructions in the storage unit, so that the device can realize this
  • the transceiver unit can be an input and output circuit in a chip system or a processing system, outputting information processed by the chip system, or inputting data or signaling information to be processed into the chip system for processing.
  • the embodiment of the present application also provides a computer-readable storage medium, on which is stored the device (such as the first terminal device, the second terminal device, the first core network element, the service provider etc.) computer instructions for performing the method.
  • the device such as the first terminal device, the second terminal device, the first core network element, the service provider etc.
  • the computer program when executed by a computer, the computer can implement the method performed by the network device in the foregoing method embodiments.
  • the embodiment of the present application also provides a computer program product containing instructions.
  • the computer implements the device (such as the first terminal device, the second terminal device, the first core network network) in the above method embodiment. element, service provider, etc.).
  • the embodiment of the present application also provides a communication system, which includes the devices in the above embodiments (such as the above-mentioned first terminal device, second terminal device, first core network element, service provider, etc.), such as including Relay UE, Remote UE, and SMF.
  • the devices in the above embodiments such as the above-mentioned first terminal device, second terminal device, first core network element, service provider, etc.
  • Relay UE Remote UE
  • SMF SMF
  • processors mentioned in the embodiment of the present application may be a central processing unit (central processing unit, CPU), and may also be other general processors, digital signal processors (digital signal processor, DSP), application specific integrated circuits ( 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.
  • a general-purpose processor may be a microprocessor, or the processor may be any conventional processor, or the like.
  • the memory mentioned in the embodiments of the present application may be a volatile memory and/or a nonvolatile memory.
  • the non-volatile memory can be read-only memory (read-only memory, ROM), programmable read-only memory (programmable ROM, PROM), erasable programmable read-only memory (erasable PROM, EPROM), electrically programmable Erases programmable read-only memory (electrically EPROM, EEPROM) or flash memory.
  • the volatile memory may be random access memory (RAM).
  • RAM random access memory
  • RAM can be used as an external cache.
  • RAM may include the following forms: static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous dynamic random access memory (synchronous DRAM, SDRAM) , double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection dynamic random access memory (synchlink DRAM, SLDRAM) and Direct memory bus random access memory (direct rambus RAM, DR RAM).
  • static random access memory static random access memory
  • dynamic RAM dynamic random access memory
  • DRAM synchronous dynamic random access memory
  • SDRAM synchronous DRAM
  • double data rate SDRAM double data rate SDRAM
  • DDR SDRAM double data rate SDRAM
  • ESDRAM enhanced synchronous dynamic random access memory
  • SLDRAM synchronous connection dynamic random access memory
  • Direct memory bus random access memory direct rambus RAM, DR RAM
  • the processor is a general-purpose processor, DSP, ASIC, FPGA or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components
  • the memory storage module may be integrated in the processor.
  • memories described herein are intended to include, but are not limited to, these and any other suitable types of memories.
  • the disclosed devices and methods may be implemented in other ways.
  • the device embodiments described above are only illustrative.
  • the division of the units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components can be combined or May be integrated into another system, or some features may be ignored, or not implemented.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection of devices or units may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place, or may be distributed to multiple network units. Part or all of the units can be selected according to actual needs to implement the solutions provided in this application.
  • each functional unit in each embodiment of the present application may be integrated into one unit, each unit may exist separately physically, or two or more units may be integrated into one unit.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable devices.
  • the computer may be a personal computer, a server, or a network 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 transmitted from a website, computer, server or data center Transmission to another website site, computer, server, or data center by wired (eg, coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (eg, infrared, wireless, microwave, etc.).
  • the computer-readable storage medium may be any available medium that can be accessed by a computer, or a data storage device such as a server or a data center integrated with one or more available media.
  • the available medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, DVD), or a semiconductor medium (for example, a solid state disk (solid state disk, SSD) etc.
  • the aforementioned available medium may include But not limited to: U disk, mobile hard disk, read-only memory (read-only memory, ROM), random access memory (random access memory, RAM), magnetic disk or optical disk and other media that can store program codes.

Landscapes

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

Abstract

本申请提供了一种中继通信的方法和装置，该中继通信的方法包括：第一终端设备接收来自通过中继方式联网的第二终端设备的第一请求消息，该第一请求消息中包括服务供应商分配的该第二终端设备的标识；该第一终端设备向第一核心网网元发送第二请求消息，该第二请求消息中包括该第一标识，其中，该第二请求消息用于请求建立该第二终端设备与控制该第二终端设备的控制器和/或该服务供应商之间的通信。通过携带第二终端设备的第一标识触发第二终端设备与该服务供应商和/或控制器之间的通信建立流程，从而实现中继的场景中远程终端设备的认证授权。

Description

中继通信的方法和装置
本申请要求于2021年10月20日提交中国专利局、申请号为202111224378.6、申请名称为“中继通信的方法和装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域，并且更具体地，涉及一种中继通信的方法和装置。
背景技术
近年来，在第五代(5th generation，5G)通信系统中，无人机(uncrewed aerial vehicle，UAV)的应用越来越普及，如果UAV期望联网与无人机控制器(uncrewed aerial vehicle controller，UAVc)通信，则需要进行UAV的认证授权和命令和控制(command and control，C2)通信的授权。
目前协议中规定了针对某个UAV的认证授权和C2通信的授权流程，但是在某些场景下，多个无人机可能会配合工作，其中的某个或某些无人机能力较强，可以将其他无人机的数据传输给控制器或服务器，即无人机中继通信成为一个可能的场景。
在无人机中继通信的场景中如何实现远程UAV(Remote UAV)的UAV的认证授权和C2通信的授权成为亟待解决的问题。
发明内容
本申请提供一种中继通信的方法和装置，以期实现在中继通信场景中Remote UAV的认证授权。
第一方面，提供了一种中继通信的方法，该中继通信的方法可以由第一终端设备执行，或者，也可以由设置于第一终端设备中的芯片或电路执行，本申请对此不作限定。为了便于描述，下文中以第一终端设备执行为例进行说明。
该中继通信的方法包括：
第一终端设备接收来自第二终端设备的第一请求消息，该第一请求消息中包括第一标识，该第一标识为服务供应商分配的该第二终端设备的标识；该第一终端设备向第一核心网网元发送第二请求消息，该第二请求消息中包括该第一标识，其中，该第二请求消息用于请求建立该第二终端设备与该服务供应商和/或控制器之间且通过该第一终端设备进行的通信。
本申请实施例提供的中继通信的方法，第一终端设备(如，中继终端设备(Relay UE))根据第二终端设备(如，远程终端设备(Remote UE))的第一标识请求建立该第二终端设备与该服务供应商和/或控制器之间的通信。具体地，接收第二请求消息的第一核心网网元能够确定是否需要对第二终端设备进行认证，从而实现中继的场景中远程终端设备的 认证授权，在保证安全的前提下实现Remote UE中继联网。
结合第一方面，在第一方面的某些实现方式中，该第二请求消息可以是用于请求修改或者建立会话的请求消息，该会话用于该第二终端设备与该服务供应商之间通信。
上述的第二请求消息可以复用目前流程中的用于请求修改或者建立会话的请求消息，降低信令的开销。
结合第一方面，在第一方面的某些实现方式中，该方法还包括：该第一终端设备接收来自该第一核心网网元的响应于该第二请求消息的第二响应消息，该第二响应消息中包括该第二终端设备的认证授权结果，其中，该第二终端设备的认证授权结果包括该第二终端设备是否合法，和/或，该第一终端设备是否允许中继该第二终端设备的数据。
本申请实施例提供的中继通信的方法，第一终端设备能够获取第二终端设备的认证授权结果，从而可以根据第二终端设备的认证授权结果确定第二终端设备是否合法，或者，是否对第二终端设备的数据进行中继，以保障安全。
结合第一方面，在第一方面的某些实现方式中，该第二终端设备的认证授权结果还包括：该第二终端设备是否匹配到该控制器。
本申请实施例提供的中继通信的方法，第一终端设备可以同时获取第二终端设备的合法性认证结果和第二终端设备与控制器的通信的认证授权，从而简化认证过程。
结合第一方面，在第一方面的某些实现方式中，该第二请求消息中还包括该控制器的标识，该控制器为该第二终端设备请求用于控制该第二终端设备的控制器，该第二终端设备的认证授权结果还包括：是否允许该控制器控制该第二终端设备；和/或，该第二请求消息中还包括该第一终端设备的标识，该第二终端设备的认证授权结果还包括：是否允许控制该第一终端设备的控制器控制该第二终端设备。
本申请实施例提供的中继通信的方法，第二请求消息中携带不同的信元能够通过不同的方式确定第二终端设备的认证结果，提高方案的灵活性。
结合第一方面，在第一方面的某些实现方式中，该方法还包括：该第一终端设备接收来自该第二终端设备的第一指示信息，该第一指示信息用于指示该第二终端设备请求与该控制器建立通信；该第一终端设备向该第一核心网网元发送该第一指示信息。
本申请实施例提供的中继通信的方法，第一终端设备可以通过第一指示信息针对第二终端设备的C2通信认证，从而可以单独认证第二终端设备和控制器的通信的认证授权，有利于监管。
结合第一方面，在第一方面的某些实现方式中，该第一终端设备接收来自该第二终端设备的以下信息中的至少一种：飞行信息、控制器的标识、服务供应商的标识、该第二终端设备的标识。
结合第一方面，在第一方面的某些实现方式中，该方法还包括：该第一终端设备接收来自该第一核心网网元的第二指示信息，该第二指示信息用于指示第二终端设备是否允许与该控制器通信；该第一终端设备向该第二终端设备发送该第二指示信息。
结合第一方面，在第一方面的某些实现方式中，该方法还包括：该第一终端设备向该第二终端设备发送响应于该第一请求消息的第一响应消息，该第一响应消息中包括该第二终端设备的认证授权结果。
本申请实施例提供的中继通信的方法，第一终端设备获取第二终端设备的认证授权结 果，并转发给第二终端设备，使得第二终端设备能够获知自身认证授权结果。
结合第一方面，在第一方面的某些实现方式中，在该第一终端设备向第一核心网网元发送第二请求消息之前，该方法还包括：该第一终端设备确定服务该第二终端设备的服务供应商和服务该第一终端设备的服务供应商相同，和/或，该第一终端设备确定控制该第一终端设备的控制器和控制该第二终端设备的控制器相同。
本申请实施例提供的中继通信的方法，第一终端设备可以通过不同的方式确定需要请求第一核心网网元触发认证第二终端设备的流程，可以提前判断是否需要认证，避免不必要的信令开销。
结合第一方面，在第一方面的某些实现方式中，该第一终端设备确定服务该第二终端设备的供应商和服务该第一终端设备的供应商相同，包括：该第一终端设备根据该第一标识确定服务该第二终端设备的服务供应商和服务该第一终端设备的服务供应商相同；和/或，该第一请求消息中还包括该服务供应商的地址信息，该第一终端设备根据该地址信息确定服务该第二终端设备的服务供应商和服务该第一终端设备的服务供应商相同。
本申请实施例提供的中继通信的方法，第一终端设备可以通过不同的方式确定服务该第二终端设备的供应商和服务该第一终端设备的供应商相同，提高方案的灵活性。
结合第一方面，在第一方面的某些实现方式中，该第一请求消息中还包括该控制器的标识，该控制器为该第二终端设备请求用于控制该第二终端设备的控制器，该第一终端设备确定控制该第一终端设备的控制器和控制该第二终端设备的控制器相同，包括：该第一终端设备根据该控制器的标识确定控制该第一终端设备的控制器和控制该第二终端设备的控制器相同。
结合第一方面，在第一方面的某些实现方式中，该第一核心网网元为会话管理功能网元SMF，该第二请求消息为会话建立请求消息或会话修改请求消息。
结合第一方面，在第一方面的某些实现方式中，该第二请求消息为会话建立请求消息时，该第二请求消息用于建立该第一终端设备与该服务供应商和/或该控制器之间的第二会话，该第二会话用于传输该第二终端设备与该服务供应商和/或该控制器之间的数据；或该第二请求消息为会话修改请求消息时，该第二请求消息用于请求将该第一会话修改为用于进一步传输该第二终端设备与该服务供应商和/或该控制器之间的数据的会话，在发送该会话修改请求消息前，该第一会话为该第一终端设备建立的用于传输该第一终端设备与该服务供应商和/或该控制器之间的数据的会话。
结合第一方面，在第一方面的某些实现方式中，其特征在于，该控制器用于控制该第二终端设备；该服务供应商是第三方实体，用于为该第一终端设备和该第二终端设备提供服务。
第二方面，提供了一种中继通信的方法，该中继通信的方法可以由第二终端设备执行，或者，也可以由设置于第二终端设备中的芯片或电路执行，本申请对此不作限定。为了便于描述，下文中以第二终端设备执行为例进行说明。
该中继通信的方法包括：
第二终端设备获取第一标识，该第一标识为服务供应商分配的该第二终端设备的标识；该第二终端设备向第一终端设备发送第一请求消息，该第一请求消息中包括该第一标识，其中，该第二终端设备为通过中继方式联网的终端设备。
本申请实施例提供的中继通信的方法，第一终端设备能够获知第二终端设备的第一标识，该第一标识触发第二终端设备的认证流程。从而实现中继的场景中远程终端设备的认证授权，在保证安全的前提下实现Remote UE中继联网。
结合第二方面，在第二方面的某些实现方式中，该方法还包括：该第二终端设备接收来自该第一终端设备的响应于该第一请求消息的第一响应消息，该第一响应消息中包括该第二终端设备的认证授权结果，其中，该第二终端设备的认证授权结果包括该第二终端设备是否合法，和/或，该第一终端设备是否允许中继该第二终端设备的数据。
本申请实施例提供的中继通信的方法，第二终端设备从第一终端设备获取第二终端设备的认证授权结果，使得第二终端设备能够获知自身认证授权结果。
结合第二方面，在第二方面的某些实现方式中，该第二终端设备的认证授权结果还包括：该第二终端设备是否匹配到该控制器。
本申请实施例提供的中继通信的方法，第二终端设备可以同时获取第二终端设备的合法性认证结果和第二终端设备与控制器的通信的认证授权，从而简化认证过程。
结合第二方面，在第二方面的某些实现方式中，该方法还包括：该第二终端设备向该第一终端设备发送第一指示信息，该第一指示信息用于指示该第二终端设备请求与控制器建立通信。
本申请实施例提供的中继通信的方法，第二终端设备可以通过第一指示信息请针对第二终端设备的C2通信认证，从而可以单独认证第二终端设备和控制器的通信的认证授权，有利于监管。
结合第二方面，在第二方面的某些实现方式中，该方法还包括：该第二终端设备接收来自该第一终端设备的第二指示信息，该第二指示信息用于指示第二终端设备是否允许与该控制器通信。
结合第二方面，在第二方面的某些实现方式中，该第一请求消息中还包括控制器的标识，和/或，该服务供应商的标识，其中，该控制器为该第二终端设备请求用于控制该终端设备的控制器。
第三方面，提供了一种中继通信的方法，该中继通信的方法可以由第一核心网网元执行，或者，也可以由设置于第一核心网网元中的芯片或电路执行，本申请对此不作限定。为了便于描述，下文中以第一核心网网元执行为例进行说明。
该中继通信的方法包括：
第一核心网网元接收来自第一终端设备的第二请求消息，该第二请求消息中包括第一标识，该第一标识为服务供应商分配的该第二终端设备的标识；该第一核心网网元向该服务供应商发送第三请求消息，该第三请求消息中包括该第一标识和该第一终端设备的标识，该第三请求消息用于请求该服务供应商对该第二终端设备进行认证授权，其中，该第二请求消息用于请求建立该第二终端设备与该服务供应商和/或控制器之间且通过所述第一终端设备进行的通信。
本申请实施例提供的中继通信的方法，第一终端设备根据第二终端设备的第一标识请求第一核心网网元触发第二终端设备的认证流程。从而实现中继的场景中远程终端设备的认证授权，在保证安全的前提下实现Remote UE中继联网。
结合第三方面，在第三方面的某些实现方式中，该方法还包括：该第一核心网网元接 收来自该服务供应商的响应于该第三请求消息的第三响应消息，该第三响应消息中包括该第二终端设备的认证授权结果，其中，该第二终端设备的认证授权结果包括该第二终端设备是否合法，和/或，该第一终端设备是否允许中继该第二终端设备的数据。
本申请实施例提供的中继通信的方法，第一核心网网元能够获取第二终端设备的认证授权结果，从而可以根据第二终端设备的认证授权结果确定第二终端设备是否合法，或者，是否对第二终端设备的数据进行中继，以保障安全。
结合第三方面，在第三方面的某些实现方式中，该第二终端设备的认证授权结果还包括：该第二终端设备是否匹配到该控制器。
本申请实施例提供的中继通信的方法，第一核心网网元可以同时获取第二终端设备的合法性认证结果和第二终端设备与控制器的通信的认证授权，从而简化认证过程。
结合第三方面，在第三方面的某些实现方式中，该方法还包括：该第一核心网网元接收来自第一终端设备的第一指示信息，该第一指示信息用于指示该第二终端设备请求与该控制器建立通信；该第一核心网网元确定该第二终端设备是否允许与该控制器通信。
本申请实施例提供的中继通信的方法，第一核心网网元可以基于第一指示信息确定针对第二终端设备的C2通信认证，从而可以单独认证第二终端设备和控制器的通信的认证授权，有利于监管。
结合第三方面，在第三方面的某些实现方式中，该第一核心网网元确定该第二终端设备是否允许与该控制器通信，包括：该第一核心网网元根据该第二终端设备认证授权结果确定该第二终端设备是否允许与该控制器通信；和/或，该第一核心网网元从该服务供应商获取该第二终端设备是否允许与该控制器通信。
本申请实施例提供的中继通信的方法，第一核心网网元可以通过不同的方式确定针对第二终端设备的C2通信认证结果，提高了方案的灵活性。
结合第三方面，在第三方面的某些实现方式中，该第一核心网网元从该服务供应商获取该第二终端设备是否允许与该控制器通信，包括：该第一核心网网元向该服务供应商发送第四请求消息，该第四请求消息用于请求该服务供应商确定该第二终端设备是否允许与该控制器通信；该第一核心网网元接收来自该服务供应商的响应于该第四请求消息的第四响应消息，该第四响应消息包括第二指示信息，该第二指示信息用于指示第二终端设备是否允许与该控制器通信。
结合第三方面，在第三方面的某些实现方式中，该方法还包括：该第一核心网网元向该第一终端设备发送该第二指示信息。
结合第三方面，在第三方面的某些实现方式中，该方法还包括：该第一核心网网元向该第一终端设备发送响应于该第二请求消息的第二响应消息，该第二响应消息中包括该第二终端设备的认证授权结果。
本申请实施例提供的中继通信的方法，第一核心网网元获取第二终端设备的认证授权结果，并转发给第一终端设备，使得第一终端设备能够获知第二终端设备的认证授权结果。
结合第三方面，在第三方面的某些实现方式中，该第一核心网网元为会话管理功能网元SMF，该第二请求消息为会话建立请求消息或会话修改请求消息。
结合第三方面，在第三方面的某些实现方式中，该第二请求消息为会话建立请求消息时，该第二请求消息用于建立该第一终端设备与该服务供应商和/或该控制器之间的第二 会话，该第二会话用于传输该第二终端设备与该服务供应商和/或该控制器之间的数据；或该第二请求消息为会话修改请求消息时，该第二请求消息用于请求将该第一会话修改为用于进一步传输该第二终端设备与该服务供应商和/或该控制器之间的数据的会话，在发送该会话修改请求消息前，该第一会话为该第一终端设备建立的用于传输该第一终端设备与该服务供应商和/或该控制器之间的数据的会话。
结合第三方面，在第三方面的某些实现方式中，其特征在于，该控制器用于控制该第二终端设备；该服务供应商是第三方实体，用于为该第一终端设备和该第二终端设备提供服务。
第四方面，提供了一种中继通信的方法，该中继通信的方法可以由服务供应商执行，或者，也可以由设置于服务供应商中的芯片或电路执行，本申请对此不作限定。为了便于描述，下文中以服务供应商执行为例进行说明。
该中继通信的方法包括：
服务供应商接收来自第一核心网网元的第三请求消息，该第三请求消息中包括第一标识，该第一标识为该服务供应商分配的该第二终端设备的标识；该服务供应商根据该第一标识对该第二终端设备进行认证授权，其中，该第二终端设备为通过中继方式联网的终端设备。
本申请实施例提供的中继通信的方法，服务供应商能够获知第二终端设备的第一标识，根据该第一标识进行第二终端设备的认证。从而实现中继的场景中远程终端设备的认证授权，在保证安全的前提下实现Remote UE中继联网。
结合第四方面，在第四方面的某些实现方式中，该方法还包括：该服务供应商向该第一核心网网元发送响应于该第三请求消息的第三响应消息，该第三响应消息中包括该第二终端设备的认证授权结果，其中，该第二终端设备的认证授权结果包括该第二终端设备是否合法，和/或，该第一终端设备是否允许中继该第二终端设备的数据。
结合第四方面，在第四方面的某些实现方式中，该第二终端设备的认证授权结果还包括：该第二终端设备是否匹配到该控制器。
本申请实施例提供的中继通信的方法，第一核心网网元可以同时获取第二终端设备的合法性认证结果和第二终端设备与控制器的通信的认证授权，从而简化认证过程。
结合第四方面，在第四方面的某些实现方式中，该方法还包括：该服务供应商接收来自该第一核心网网元的第四请求消息；该服务供应商根据该第四请求消息确定该第二终端设备是否允许与该控制器通信；该服务供应商向该第一核心网网元发送应于该第四请求消息的第四响应消息，该第四响应消息包括第二指示信息，该第二指示信息用于指示第二终端设备是否允许与该控制器通信。
本申请实施例提供的中继通信的方法，服务供应商可以单独认证第二终端设备和控制器的通信的认证授权，有利于监管。
第五方面，提供了一种中继通信的方法，该中继通信的方法可以由第一终端设备执行，或者，也可以由设置于第一终端设备中的芯片或电路执行，本申请对此不作限定。为了便于描述，下文中以第一终端设备执行为例进行说明。
第一终端设备向服务供应商发送能力信息，该能力信息用于指示该第一终端设备中继其他终端设备数据的能力；该第一终端设备接收来自该服务供应商的中继服务码，该中继 服务码用于指示该第一终端设备允许中继其他终端设备数据。
本申请实施例提供的中继通信的方法，第一终端设备基于能力信息获取中继服务码。第一终端设备获得中继服务码后，第二终端设备可通过中继联网，在简化流程的前提下实现第二终端设备中继联网。
结合第五方面，在第五方面的某些实现方式中，该方法还包括：该第一终端设备向该终端设备的供应商发送第二终端设备的标识，和/或，终端设备系统的标识，其中，该第二终端设备为通过中继方式联网的终端设备。
第六方面，提供了一种中继通信的方法，该中继通信的方法可以由第二终端设备执行，或者，也可以由设置于第二终端设备中的芯片或电路执行，本申请对此不作限定。为了便于描述，下文中以第二终端设备执行为例进行说明。
该中继通信的方法包括：
第二终端设备获取中继服务码，该中继服务码用于指示该第一终端设备允许中继其他终端设备数据；该第二终端设备根据该中继服务码发现该第一终端设备。
本申请实施例提供的中继通信的方法，第二终端设备根据中继服务码中继联网，在简化流程的前提下实现第二终端设备中继联网。
结合第六方面，在第六方面的某些实现方式中，该方法还包括：该第二终端设备通过会话传输该第二终端设备的数据，该会话为该第一终端设备建立的传输第二终端设备的数据的会话。
第七方面，提供了一种中继通信的方法，该中继通信的方法可以由服务供应商执行，或者，也可以由设置于服务供应商中的芯片或电路执行，本申请对此不作限定。为了便于描述，下文中以服务供应商执行为例进行说明。
该中继通信的方法包括：
服务供应商接收来自第一终端设备的能力信息，该能力信息用于指示该第一终端设备中继其他终端设备数据的能力；该服务供应商向该第一终端设备发送中继服务码，该中继服务码用于指示该第一终端设备允许中继其他终端设备数据。
本申请实施例提供的中继通信的方法，第一终端设备基于能力信息获取中继服务码。第一终端设备获得中继服务码后，第二终端设备可通过中继联网，在简化流程的前提下实现第二终端设备中继联网。
结合第七方面，在第七方面的某些实现方式中，该方法还包括：该服务供应商接收来自第一终端设备的第二终端设备的标识，和/或，终端设备系统的标识，其中，该第二终端设备为通过中继方式联网的终端设备。
第八方面，提供一种中继通信的装置，该中继通信的装置包括处理器，用于实现上述第一方面和第五方面描述的方法中第一终端设备的功能。
可选地，该中继通信的装置还可以包括存储器，该存储器与该处理器耦合，该处理器用于实现上述第一方面和第五方面描述的方法中第一终端设备的功能。
在一种可能的实现中，该存储器用于存储程序指令和数据。该存储器与该处理器耦合，该处理器可以调用并执行该存储器中存储的程序指令，用于实现上述第一方面和第五方面描述的方法中第一终端设备的功能。
可选地，该中继通信的装置还可以包括通信接口，该通信接口用于该中继通信的装置 与其它设备进行通信。该通信接口可以为收发器、输入/输出接口、或电路等。
在一种可能的设计中，该中继通信的装置包括：处理器和通信接口，
该处理器用于运行计算机程序，以使得该中继通信的装置实现上述第一方面和第五方面描述的任一种方法；
该处理器利用该通信接口与外部通信。
可以理解，该外部可以是处理器以外的对象，或者是该装置以外的对象。
在另一种可能的设计中，该中继通信的装置为芯片或芯片系统。该通信接口可以是该芯片或芯片系统上输入/输出接口、接口电路、输出电路、输入电路、管脚或相关电路等。该处理器也可以体现为处理电路或逻辑电路。
第九方面，提供一种中继通信的装置，该中继通信的装置包括处理器，用于实现上述第二方面和第六方面描述的方法中第二终端设备的功能。
可选地，该中继通信的装置还可以包括存储器，该存储器与该处理器耦合，该处理器用于实现上述第二方面和第六方面描述的方法中第二终端设备的功能。
在一种可能的实现中，该存储器用于存储程序指令和数据。该存储器与该处理器耦合，该处理器可以调用并执行该存储器中存储的程序指令，用于实现上述第二方面和第六方面描述的方法中第二终端设备的功能。
可选地，该中继通信的装置还可以包括通信接口，该通信接口用于该中继通信的装置与其它设备进行通信。该通信接口可以为收发器、输入/输出接口、或电路等。
在一种可能的设计中，该中继通信的装置包括：处理器和通信接口，
该处理器利用该通信接口与外部通信；
该处理器用于运行计算机程序，以使得该中继通信的装置实现上述第二方面和第六方面描述的任一种方法。
可以理解，该外部可以是处理器以外的对象，或者是该装置以外的对象。
在另一种可能的设计中，该中继通信的装置为芯片或芯片系统。该通信接口可以是该芯片或芯片系统上的输入/输出接口、接口电路、输出电路、输入电路、管脚或相关电路等。该处理器也可以体现为处理电路或逻辑电路。
第十方面，提供一种中继通信的装置，该中继通信的装置包括处理器，用于实现上述第三方面描述的方法中第一核心网网元的功能。
可选地，该中继通信的装置还可以包括存储器，该存储器与该处理器耦合，该处理器用于实现上述第三方面描述的方法中第一核心网网元的功能。
在一种可能的实现中，该存储器用于存储程序指令和数据。该存储器与该处理器耦合，该处理器可以调用并执行该存储器中存储的程序指令，用于实现上述第三方面描述的方法中第一核心网网元的功能。
可选地，该中继通信的装置还可以包括通信接口，该通信接口用于该中继通信的装置与其它设备进行通信。该通信接口可以为收发器、输入/输出接口、或电路等。
在一种可能的设计中，该中继通信的装置包括：处理器和通信接口，
该处理器利用该通信接口与外部通信；
该处理器用于运行计算机程序，以使得该中继通信的装置实现上述第三方面描述的任一种方法。
可以理解，该外部可以是处理器以外的对象，或者是该装置以外的对象。
在另一种可能的设计中，该中继通信的装置为芯片或芯片系统。该通信接口可以是该芯片或芯片系统上的输入/输出接口、接口电路、输出电路、输入电路、管脚或相关电路等。该处理器也可以体现为处理电路或逻辑电路。
第十一方面，提供一种中继通信的装置，该中继通信的装置包括处理器，用于实现上述第四方面和第七方面描述的方法中服务供应商的功能。
可选地，该中继通信的装置还可以包括存储器，该存储器与该处理器耦合，该处理器用于实现上述第四方面和第七方面描述的方法中服务供应商的功能。
在一种可能的实现中，该存储器用于存储程序指令和数据。该存储器与该处理器耦合，该处理器可以调用并执行该存储器中存储的程序指令，用于实现上述第四方面和第七方面描述的方法中服务供应商的功能。
可选地，该中继通信的装置还可以包括通信接口，该通信接口用于该中继通信的装置与其它设备进行通信。该通信接口可以为收发器、输入/输出接口、或电路等。
在一种可能的设计中，该中继通信的装置包括：处理器和通信接口，
该处理器利用该通信接口与外部通信；
该处理器用于运行计算机程序，以使得该中继通信的装置实现上述第四方面和第七方面描述的任一种方法。
可以理解，该外部可以是处理器以外的对象，或者是该装置以外的对象。
在另一种可能的设计中，该中继通信的装置为芯片或芯片系统。该通信接口可以是该芯片或芯片系统上的输入/输出接口、接口电路、输出电路、输入电路、管脚或相关电路等。该处理器也可以体现为处理电路或逻辑电路。
第十二方面，本申请提供一种计算机可读存储介质，该计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机执行上述各方面所述的方法。
第十三方面，本申请提供一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述各方面所述的方法。
第十四方面，提供了一种通信系统，包括第八方面至第十一方面所示的中继通信的装置。
第十五方面，提供了一种芯片装置，包括处理电路，该处理电路用于从存储器中调用并运行程序，使得安装有该芯片装置的通信设备执行上述各方面所述的方法。
附图说明
图1中的(a)和(b)是本申请实施例适用的通信系统的架构示意图。
图2是本申请实施例提供的中继架构示意图。
图3是本申请提供的一种中继通信的方法的示意性流程图。
图4是本申请提供的另一种中继通信的方法的示意性流程图。
图5是本申请提供的又一种中继通信的方法的示意性流程图。
图6是根据本申请实施例提供的通信装置的示意性框图。
图7是根据本申请实施例提供的通信装置的另一示意性框图。
具体实施方式
下面将结合附图，对本申请中的技术方案进行描述。
本申请实施例的技术方案可以应用于各种通信系统，例如：第五代(5th generation，5G)系统或新无线(new radio，NR)、长期演进(long term evolution，LTE)系统、LTE频分双工(frequency division duplex，FDD)系统、LTE时分双工(time division duplex，TDD)等。本申请提供的技术方案还可以应用于未来的通信系统，如第六代移动通信系统。本申请实施例的技术方案还可以应用于设备到设备(device to device，D2D)通信，车辆外联(vehicle-to-everything，V2X)通信，机器到机器(machine to machine，M2M)通信，机器类型通信(machine type communication，MTC)，以及物联网(internet of things，IoT)通信系统或者其他通信系统。
为便于理解本申请实施例，首先结合图1中的(a)和(b)简单介绍本申请实施例适用的通信系统。
作为示例性说明，图1中的(a)示出了本申请实施例适用的通信系统的架构示意图。图1中的(a)所示的通信系统中包括基于服务化接口的5G网络架构。如图1中的(a)所示，该网络架构可以包括但不限于以下网元(或者称为功能网元、功能实体、节点、设备等)：
用户设备(user equipment，UE)、5G无线接入网设备(radio access network，NG-RAN)、接入和移动性管理功能(access and mobility management function，AMF)网元、会话管理功能(session management function，SMF)网元、用户面功能(user plane function，UPF)网元、统一数据管理(unified data management，UDM)网元、数据网络(data network，DN)、认证服务器功能(authentication server function，AUSF)、网络数据分析功能(network data analytics function，NWDAF)网元、能力开放功能(network exposure function，NEF)、网络存储功能(NF repository function，NRF)、策略控制功能设备(policy control function，PCF)、应用功能(application function，AF)、等。
下面对图1中的(a)中示出的各网元进行简单介绍：
1、UE：与(R)AN通信的终端，也可以称为终端设备(terminal equipment)、接入终端、用户单元、用户站、移动站、移动台(mobile station，MS)、移动终端(mobile terminal，MT)、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。终端设备可以是一种向用户提供语音/数据连通性的设备，例如，具有无线连接功能的手持式设备、车载设备等。目前，一些终端的举例可以为：手机(mobile phone)、平板电脑(pad)、带无线收发功能的电脑(如笔记本电脑、掌上电脑等)、移动互联网设备(mobile internet device，MID)、虚拟现实(virtual reality，VR)设备、增强现实(augmented reality，AR)设备、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程医疗(remote medical)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端、蜂窝电话、无绳电话、会话启动协议(session initiation protocol，SIP)电话、无线本地环路(wireless local loop，WLL)站、个人数字助理(personal digital assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备，5G网络中的终端设备或者 未来演进的公用陆地移动通信网络(public land mobile network，PLMN)中的终端设备等。
此外，终端设备还可以是物联网(Internet of things，IoT)系统中的终端设备。IoT是未来信息技术发展的重要组成部分，其主要技术特点是将物品通过通信技术与网络连接，从而实现人机互连，物物互连的智能化网络。IoT技术可以通过例如窄带(narrow band，NB)技术，做到海量连接，深度覆盖，终端省电。
应理解，终端设备可以是任何可以接入网络的设备。终端设备与接入网设备之间可以采用某种空口技术相互通信。
可选地，用户设备可以用于充当基站。例如，用户设备可以充当调度实体，其在V2X或D2D等中的用户设备之间提供侧行链路信号。比如，蜂窝电话和汽车利用侧行链路信号彼此通信。蜂窝电话和智能家居设备之间通信，而无需通过基站中继通信信号。
2、NG-RAN：用于为特定区域的授权用户设备提供入网功能，并能够根据用户设备的级别，业务的需求等使用不同服务质量的传输隧道。
NG-RAN能够管理无线资源，为用户设备提供接入服务，进而完成控制信号和用户设备数据在用户设备和核心网之间的转发，NG-RAN也可以理解为传统网络中的基站。
示例性地，本申请实施例中的接入网设备可以是用于与用户设备通信的任意一种具有无线收发功能的通信设备。该接入网设备包括但不限于：演进型节点B(evolved Node B，eNB)、无线网络控制器(radio network controller，RNC)、节点B(Node B，NB)、基站控制器(base station controller，BSC)、基站收发台(base transceiver station，BTS)、家庭基站(home evolved Node B，HeNB，或home Node B，HNB)、基带单元(baseBand unit，BBU)，无线保真(wireless fidelity，WIFI)系统中的接入点(access point，AP)、无线中继节点、无线回传节点、传输点(transmission point，TP)或者发送接收点(transmission and reception point，TRP)等，还可以为5G，如，NR，系统中的gNB，或，传输点(TRP或TP)，5G系统中的基站的一个或一组(包括多个天线面板)天线面板，或者，还可以为构成gNB或传输点的网络节点，如基带单元(BBU)，或，分布式单元(distributed unit，DU)等。
在一些部署中，gNB可以包括集中式单元(centralized unit，CU)和DU。gNB还可以包括有源天线单元(active antenna unit，AAU)。CU实现gNB的部分功能，DU实现gNB的部分功能。比如，CU负责处理非实时协议和服务，实现无线资源控制(radio resource control，RRC)，分组数据汇聚层协议(packet data convergence protocol，PDCP)层的功能。DU负责处理物理层协议和实时服务，实现无线链路控制(radio link control，RLC)层、媒体接入控制(media access control，MAC)层和物理(physical，PHY)层的功能。AAU实现部分物理层处理功能、射频处理及有源天线的相关功能。由于RRC层的信息最终会变成PHY层的信息，或者，由PHY层的信息转变而来，因而，在这种架构下，高层信令，如RRC层信令，也可以认为是由DU发送的，或者，由DU+AAU发送的。可以理解的是，接入网设备可以为包括CU节点、DU节点、AAU节点中一项或多项的设备。此外，可以将CU划分为接入网(radio access network，RAN)中的接入网设备，也可以将CU划分为核心网(core network，CN)中的接入网设备，本申请对此不做限定。
3、UPF网元：主要负责对用户报文进行处理，如转发、计费、合法监听等。用户面网元也可以称为协议数据单元(protocol data unit，PDU)会话锚点(PDU session anchor， PSA)。
在5G通信系统中，用户面网元可以是UPF网元。在未来通信系统中，用户面网元仍可以是UPF网元，或者，还可以有其它的名称，本申请不做限定。
4、DN：用于提供传输数据的网络。
在5G通信系统中，数据网络可以是DN。在未来通信系统中，数据网络仍可以是DN，或者，还可以有其它的名称，本申请不做限定。
5、AUSF：主要包括以下功能：认证服务器功能，与统一数据管理网元交互获取用户信息，并执行认证相关的功能，如生成中间密钥等。
在5G通信系统中，认证服务器功能网元可以是AUSF网元。在未来通信系统中，认证服务器功能网元仍可以是AMF网元，或者，还可以有其它的名称，本申请不做限定。
6、AMF网元：主要用于移动网络中的终端的附着、移动性管理、跟踪区更新流程，接入管理网元终结了非接入层(non access stratum，NAS)消息、完成注册管理、连接管理以及可达性管理、分配跟踪区域列表(track area list，TA list)以及移动性管理等，并且透明路由会话管理(session management，SM)消息到会话管理网元。
在5G通信系统中，接入管理网元可以是AMF网元。在未来通信系统中，接入管理网元仍可以是AMF网元，或者，还可以有其它的名称，本申请不做限定。
7、SMF：主要用于会话管理、终端设备的网络互连协议(internet protocol，IP)地址分配和管理、选择可管理用户平面功能、策略控制和收费功能接口的终结点以及下行数据通知等。
在5G通信系统中，会话管理网元可以是SMF网元。在未来通信系统中，会话管理网元仍可以是SMF网元，或者，还可以有其它的名称，本申请不做限定。
8、PCF：包含用户签约数据管理功能、策略控制功能、计费策略控制功能、服务质量(quality of service，QoS)控制等。
在5G通信系统中，该策略控制网元可以是PCF网元。在未来通信系统中，策略控制网元仍可以是PCF网元，或者，还可以有其它的名称，本申请不做限定。
9、UDM：可以理解为统一数据管理网元在5G架构中的命名。其中，统一数据管理网元主要包括以下功能：统一数据管理，支持3GPP认证和密钥协商机制中的认证信任状处理，用户身份处理，接入授权，注册和移动性管理，签约管理，短消息管理等。
10、NEF：主要包括以下功能：安全的开放3GPP网络功能提供的业务和能力，有内部开放，或者开放给第三方等；转化或翻译与AF交互的信息和内部网络功能交互的信息，如AF服务标识和内部5G核心网信息如数据网络名(data network name，DNN)，单网络切片选择辅助信息(single network slice selection assistance information，S-NSSAI)等。
11、NRF：主要包括以下功能：服务发现功能，维护可用的网络功能(network function，NF)实例的NF文本以及他们支持的服务。
12、NWDAF：可以从各个网络功能(network function，NF)，例如策略控制网元、会话管理网元、用户面网元、接入管理网元、应用功能网元(通过网络能力开放功能网元)收集数据，并进行分析和预测。
在5G通信系统中，数据分析网元可以是NWDAF网元。在未来通信系统中数据分析网元仍可以是NWDAF网元，或者，还可以有其它的名称，本申请不做限定。
13、AF：主要包括以下功能：连接管理、移动性管理、注册管理、接入认证和授权、可达性管理、安全上下文管理等接入和移动性相关的功能。
从图1中的(a)可以看出，图1中的(a)中的各个控制面网元之间的接口是服务化的接口。
例如，图1中的(a)中Nnef、Nnrf、Nnwdaf、Namf、Npcf、Nsmf、Nudm分别为上述NEF、NRF、NWDAF、AMF、PCF、SMF和UDM提供的服务化接口，用于调用相应的服务化操作。N1、N2、N3、N4，以及N6为接口序列号。这些接口序列号的含义可参见第三代合作伙伴计划(3rd generation partnership project，3GPP)标准协议中定义的含义，在此不做限制。
服务化使得5G核心网形成一个扁平化的架构，通过控制面的信令总线，同一个网络切片的控制面网络功能实体之间可以通过NRF网元相互发现对方，获得对方的访问地址信息，然后可以通过控制面信令总线直接相互通信。
需要说明的是，图1中的(a)中的各个控制面网元之间的接口还可以是点对点接口，这里不再赘述。
可以理解的是，上述网元或者功能既可以是硬件设备中的网络元件，也可以是在专用硬件上运行软件功能，或者是平台(例如，云平台)上实例化的虚拟化功能。
为方便说明，本申请后续，以会话管理功能网元为SMF网元，数据分析网元为NWDAF网元为例进行说明。进一步地，将SMF网元简称为SMF，NWDAF网元简称为NWDAF。即本申请后续所描述的SMF均可替换为会话管理功能网元，NWDAF均可替换为数据分析功能网元。
为方便说明，本申请，以装置为SMF实体、NWDAF实体为例，对中继通信的进行说明，对于装置为SMF实体内的芯片、NWDAF实体内的芯片的实现方法，可参考装置分别为SMF实体、NWDAF实体的具体说明，不再重复介绍。
需要说明的是，图1中的(a)中所涉及的各个网元以及网元之间的通信接口的名称是以目前协议中规定的为例进行简单说明的，但并不限定本申请实施例只能够应用于目前已知的通信系统。因此，以目前协议为例描述时出现的标准名称，都是功能性描述，本申请对于网元、接口或信令等的具体名称并不限定，仅表示网元、接口或者信令的功能，可以对应的扩展到其它系统，比如5G或未来通信系统中。
另外，还需要说明的是，在某些网络架构中，AMF网元、SMF网元、PCF网元、AF网元以及UDM网元等网络功能网元实体都称为网络功能网元(network function，NF)网元；或者，在另一些网络架构中，AMF网元，SMF网元，PCF网元，AF网元，UDM网元等网元的集合都可以称为控制面功能网元。
图1中的(a)为本申请实施例适用的通信系统。近年来，在图1中的(a)所示的通信系统的基础上，无人机(uncrewed aerial vehicle，UAV)的应用越来越普及，例如，在民用领域，从个人娱乐的小型无人机，到各种各样的带来经济价值的无人机(如，植保无人机、救灾无人机、消防无人机、快递无人机)等等，种类繁多。
除此之外，无人机还可能提供临时的通信服务，即无人机上载有无线接入节点，这常应用于重大事件如足球比赛直播，或紧急事件如地震海啸等场景。当前3GPP正在讨论UAV联网相关课题，可以解决远程控制UAV时的识别、授权以及追踪等问题。
具体地，无人机系统服务供应商(UAS service supplier，USS)为UAV安全和有效使用空域提供服务，负责UAV的认证授权、命令和控制(command and control，C2)通信的认证授权、UAV的识别追踪等。UAV是UE的一种，也可以称为UE。其中，UAS为无人机航空系统(uncrewed aerial system,UAS)。
为了便于理解，下面结合图1中的(b)简单介绍USS、UAS。
作为示例性说明，图1中的(b)示出了本申请实施例适用的通信系统的架构示意图。该网络架构可以包括但不限于以下网元(或者称为功能网元、功能实体、节点、设备等)：
UE、4G接入网((R)AN)、NG-RAN、5G核心网(5G core，5GC)、4G核心网(evolved packet core，EPC)、UAS、USS、DN和第三方授权实体(third party authorized entity，TPAE)。
其中，UE、NG-RAN、5GC(包括但不限于图1中的(a)所示的通过服务化接口连接的网元，如，AMF、SMF、PCF等)、DN等网元的描述可以参考图1中的(a)中的描述；(R)AN、EPC和TPAE等网元的描述可以参考目前4G网络相关技术中的描述，本申请中不再进行赘述。本申请主要介绍USS和UAS。
UAS：包括UAV和UAV控制器，例如，UAS包括一个UAV和一个UAV控制器。
USS：第三方实体或网元，为无人机UAV安全和有效使用空域提供服务，负责UAV的认证授权、C2通信的认证授权、UAV的识别追踪等。其中，UAV是UE的一种，也可以称为UE。
USS可以和DN合设(如，USS可以看做DN中的功能)，也可以和AF合设(如，USS可以看做AF中的功能)，或者还可以是单独设立USS。
本申请对该网元的名称不限定，例如，USS还可以称为无人机流量管理(UAS traffic management，UTM)实体或网元，或其他的名称。
进一步地，如果UAV期望联网与无人机控制器(uncrewed aerial vehicle controller，UAVc)通信，则首先需要进行UAV的认证授权，即判断UAV自身是否合法，然后需要进行C2通信的授权，即判断是否允许UAV和UAVc通信以及其他可能的授权，如飞行路径是否合法。
上述的UAV的认证授权和C2通信的授权的决策者都是USS。其中，UAV的认证授权可以在注册流程中执行，也可以在会话建立流程中执行；C2通信的授权在会话建立或修改流程中执行。
具体地，UAV需要建立到USS的会话用于识别位置、位置上报等，UAV需要建立到UAVc的会话用于控制和命令等。如果UAV的认证授权在会话建立流程中执行，则可以在UAV到USS的会话建立流程中执行。C2通信的授权可以在UAV到UAVc的会话建立或修改中执行。
可选地，UAV到USS的会话和UAV到UAVc的会话可以是同一个会话，也可以是不同的会话。如果UAV到USS的会话和UAV到UAVc的会话是同一个会话，且UAV的认证授权在会话建立流程中执行，则UAV的认证授权和C2通信的授权可能同时执行。
在某些场景下，多个无人机可能会配合工作，如：无人机巡航、救灾、表演等。在这种场景下，其中的某个或某些无人机能力较强，可以将其他无人机的数据传输给控制器或服务器，即无人机中继是一个可能的场景。
具体地，图2所示的系统架构可以理解为中继架构，在无人机中继的场景下，包括以 下两种类型的无人机：
一种是远程终端设备(Remote UE)，该Remote UE是具有近距离通信能力的UE，可以理解为一个通过中继方式联网的UE。在本申请中，也称为Remote UAV，指通过中继方式联网的UAV。
另一种是通过终端设备联网的中继终端设备(UE-to-Network Relay UE)，该UE-to-Network Relay UE同样是具有近距离通信能力的UE，支持Remote UE联网，即Remote UE通过UE-to-Network Relay UE联网，也即中继。在本申请中，也称为UE-to-Network Relay UAV，或简称为Relay UAV，指中继UAV。
由上述可知，如果UAV需要联网，则需要进行UAV的认证授权和C2通信的授权，但是目前未针对无人机中继的场景说明如何进行UAV的认证授权和C2通信的授权，本申请提供一种中继通信方法，能够实现在中继场景下终端设备的认证授权和C2通信的授权。
为了便于理解本申请实施例的技术方案，在以5G架构为基础介绍本申请实施例的方案之前，首先对本申请实施例可能涉及到的5G中的一些术语或概念进行简单描述。
1、C2通信。
用于传输控制和命令的消息的用户面连接，本申请实施例中可以理解为控制器控制UAV的链路。
2、C2通信的授权。
C2通信的授权指的是判断是否允许UAV和UAVc通信。本申请实施例中涉及的C2通信的授权是在UAV到UAVc的会话建立或修改中执行的。
目前协议中(如，3GPP TS 23.502)规定的C2通信的授权主要指的是某个UAV对应的C2通信的授权流程，并未涉及图2所示的中继场景下，如何通过Relay UAV实现对Remote UAV的C2通信的授权。
本申请中对于针对某个UAV对应的C2通信的授权流程不做具体描述，可以参考目前协议中的描述。
例如，在某个UAV对应的UAV到UAVc的会话建立或修改中执行针对该UAV的C2通信的授权。
3、民航局级别的无人机标识(Civil Aviation Administration level UAV identify，CAA-Level UAV ID)。
USS分配的UAV标识，在USS管理范围内唯一标识UAV。
例如，USS管理范围内包括3个UAV(如，UAV#1、UAV#2和UAV#3)，USS为该3个UAV分别分配3个CAA-Level UAV ID(如，CAA-Level UAV ID#1、CAA-Level UAV ID#2和CAA-Level UAV ID#3)，其中，CAA-Level UAV ID#1用于标识UAV#1，CAA-Level UAV ID#2用于标识UAV#2，CAA-Level UAV ID#3用于标识UAV#3。
4、Remote UE的认证。
Relay UE中继Remote UE的数据需要进行授权，在PCF或UDM或DN中确定Relay UE传输指定Remote UE的数据。该Remote UE的认证，授权的是Relay UE是否可以中继Remote UE的数据，将Remote UE看作普通UE，不需要第三方(如，USS)进行进一步的认证授权，也不需要对Remote UE和其他UE的通信业务进行授权(如，C2通信的 授权)。
5、UAV的认证授权(USS UAV authorization/authentication，UUAA)。
UUAA指的是判断UAV自身是否合法。UUAA可以在注册流程中执行，也可以在会话建立流程中执行。本申请实施例中主要涉及在会话建立流程中执行UUAA，对于在注册流程中执行UUAA的流程不做描述。
目前协议中(如，3GPP TS 23.502)规定的UUAA主要指的是某个UAV对应的UUAA流程，并未涉及图2所示的中继场景下，如何通过Relay UAV实现对Remote UAV的UUAA。
本申请中对于针对某个UAV对应的UUAA流程不做具体描述，可以参考目前协议中的描述。
例如，在某个UAV对应的PDU会话建立过程中执行针对该UAV的UUAA。
此外，为了便于理解本申请实施例，做出以下几点说明。
第一，在本申请中，“用于指示”可以包括用于直接指示和用于间接指示。当描述某一指示信息用于指示A时，可以包括该指示信息直接指示A或间接指示A，而并不代表该指示信息中一定包括有A。
第二，在本申请中第一、第二以及各种数字编号(例如，“#1”、“#2”)仅为描述方便进行的区分，并不用来限制本申请实施例的范围。例如，区分不同的信息等。
第三，本申请实施例中涉及的“保存”，可以是指的保存在一个或者多个存储器中。所述一个或者多个存储器，可以是单独的设置，也可以是集成在编码器或者译码器，处理器、或通信装置中。所述一个或者多个存储器，也可以是一部分单独设置，一部分集成在译码器、处理器、或通信装置中。存储器的类型可以是任意形式的存储介质，本申请并不对此限定。
第四，本申请实施例中涉及的“协议”可以是指通信领域的标准协议，例如可以包括LTE协议、NR协议以及应用于未来的通信系统中的相关协议，本申请对此不做限定。
上文结合图1简单介绍了本申请实施例提供的中继通信的方法能够应用的场景，以及介绍了本申请实施例中可能涉及到的基本概念，下面将结合附图详细说明本申请实施例提供的中继通信的方法。
由上述可知，目前协议中没有规定中继的场景中如何实现远程UAV(Remote UAV)的UAV的认证授权和C2通信的授权。本申请提供一种中继通信方法，能够实现在中继场景下终端设备的认证授权和C2通信的授权。
应理解，下文示出的实施例并未对本申请实施例提供的方法的执行主体的具体结构特别限定，只要能够通过运行记录有本申请实施例的提供的方法的代码的程序，以根据本申请实施例提供的方法进行通信即可，例如，本申请实施例提供的方法的执行主体可以是终端设备或核心网设备，或者，是终端设备或核心网设备中能够调用程序并执行程序的功能模块。
以下，不失一般性，以设备之间的交互为例详细说明本申请实施例提供的中继通信的方法。
图3是本申请提供的一种中继通信的方法的示意性流程图。包括以下步骤：
S310，第二终端设备向第一终端设备发送第一请求消息，或者第一终端设备接收来自第二终端设备的第一请求消息。
该第一请求消息中包括第一标识，该第一标识为服务供应商分配的用于标识该第二终端设备的标识。
本申请实施例中，第一终端设备可以理解为Relay UE，用于支持第二终端设备(如，Remote UE)联网，例如，Relay UE用于中继Remote UE到服务供应商和/或控制器的数据，下文中所示的Relay UE中继Remote UE的数据可以理解为Relay UE中继Remote UE的到服务供应商和/或控制器的数据。为了便于描述，本申请实施例中以终端设备为UAV为例进行说明。上述第一终端设备为Relay UAV，第二终端设备为Remote UAV。
需要说明的是，本申请实施例中以“Remote UE”为Remote UAV，“Relay UE”为Relay UAV为例对中继通信的方法进行说明只是举例，对本申请的保护范围不构成任何的限定。在实际应用中，UAV也可以被替换为其他的终端设备(如，智能手机、智能穿戴设备等)，本申请对此不做限定。
该第一请求消息中包括的第一标识为服务供应商分配的在该服务供应商管理范围内唯一标识该第二终端设备的标识。
例如，第二终端设备为Remote UAV，服务供应商为USS。上述的第一标识为USS为Remote UAV分配的CAA-Level UAV ID，本申请实施例中对于CAA-Level UAV ID的具体形式不做限定，能够用于标识USS管理范围内的Remote UAV即可，如，CAA-Level UAV ID可以是Remote UAV的序列号、CAA发布的(issued)的注册标识符或USS发布的(issued)通用唯一识别码(universally unique identifier，UUID)等。
需要说明的是，本申请实施例中终端设备还可以是除无人机之外的其他设备，则上述的服务供应商可以是除USS之外的为终端设备提供服务的供应商，本申请对此不做限定。
示例性地，第一请求消息可以是Remote UAV向Relay UAV发送的直接通信请求(direct communication request)消息，该直接通信请求消息中携带USS为Remote UAV分配的CAA-Level UAV ID。
示例性地，第一请求消息还可以是Remote UAV向Relay UAV发送的其他消息，本申请中对于第一请求消息是Remote UAV和Relay UAV之间已有的消息还是新增的消息不做限定。
可选的，第一请求消息中还可以包括服务供应商的地址信息(如，USS的地址信息)，和/或，控制器的标识(如，UAVc的标识)。其中，所述USS为服务Remote UAV的USS，所述UAVc为Remote UAV期望匹配的UAVc，即UAVc用于控制Remote UAV。
示例性地，USS的地址信息可以是USS的IP地址信息，或其他可用于寻址USS的信息，本申请不做限定。
示例性地，UAVc的标识可以是用于3GPP系统识别UAVc的标识如通用公开用户标识(generic public subscription identity，GPSI)，或用于USS识别UAVc的标识如CAA-Level UAVc ID，或IP地址信息，或其他可用于标识UAVc的信息，本申请不做限定。
应理解，第二终端设备向第一终端设备发送第一请求消息之前，第二终端设备和第一终端设备之间已经建立连接，图3所示的方法还可以包括：
S311，第二终端设备与第一终端设备建立连接。
具体地，Remote UAV根据某些特征(如，Remote UAV和Relay UAV是同一个通信组，或使用同一个应用或服务)发现能够为Remote UAV提供中继服务的Relay UAV。
作为一种可能的实现方式，某个Relay UAV广播第一中继服务编码(relay service code，RSC)，如果有Remote UAV可以识别出该第一RSC，则可以尝试与该Relay UAV建立连接。
作为另一种可能的实现方式，某个Remote UAV需要寻求Relay UAV为其提供中继服务，则该Remote UAV广播第二RSC。当有Relay UAV可以支持该第二RSC对应的中继服务，则Relay UAV广播回复消息或向该Remote UAV发送回复消息，回复消息中可以携带其可以支持的第二RSC，Remote UAV根据接收到的回复消息，判断是否与Relay UAV建立连接。
需要说明的是，上述的通过识别RSC判断是否与Relay UAV建立连接的方式，只是举例说明Remote UAV如何与Relay UAV建立连接，对本申请的保护范围不构成任何的限定，本申请实施例中对于Remote UAV如何与Relay UAV建立连接不做限定，Remote UAV还可以通过其他方式与Relay UAV建立连接，例如，根据历史传输路径或者根据管理器的指示等，这里不再赘述。
进一步地，第一终端设备接收到上述的第一请求消息之后，需要向第一核心网网元发送第二请求消息，以使得第二终端设备能够与服务供应商和/或控制器通信，图3所示的方法还可以包括：
S320，第一终端设备向第一核心网网元发送第二请求消息，或者第一核心网网元接收来自第一终端设备的第二请求消息。
该第二请求消息中包括上述的第一标识。
示例性地，该第二请求消息用于请求建立该第二终端设备与控制该第二终端设备的控制器和/或该服务供应商之间的通信。该控制器用于控制该第二终端设备，该服务供应商可以理解为第三方实体，用于为该第一终端设备和第二终端设备提供服务。
或者说，该第二请求消息请求建立用于无人机航空系统(uncrewed aerial system,UAS)服务的会话。
其中，所述UAS服务，指用于UAV与USS通信、与UAVc通信等连接所提供的服务。也就是说，用于UAS服务的会话包括UAV到USS的会话和/或UAV到UAVc的会话。
或者说，该第二请求消息用于请求第一核心网网元发起针对该第二终端设备的认证流程；
或者说，该第二请求消息用于请求第一核心网网元发起用于该第二终端设备通信的会话建立流程。
示例性地，本申请实施例中涉及的第一核心网网元可以是会话管理功能网元。会话管理功能网元可以是SMF，或者能够实现会话管理功能的其他网元，本申请实施例中对于网元的名称不做任何的限定。
具体地，该第二请求消息可以是用于请求修改或者建立会话的请求消息，该会话用于第二终端设备与服务供应商之间通信和/或第二终端与控制器之间的通信。
作为一种可能的实现方式，在第二请求消息为会话建立请求消息的情况下，第一核心网网元能够根据第二请求消息建立第一终端设备与服务供应商和/或控制器之间的第二会话，该第二会话用于传输第二终端设备与服务供应商和/或所述控制器之间的数据。
作为另一种可能的实现方式，在第二请求消息为会话修改请求消息的情况下，第一核心网网元能够根据第二请求消息修改第一会话为用于传输第一终端设备与所述服务供应商和/或所述控制器之间的数据以及所述第二终端设备与所述服务供应商和/或所述控制器之间的数据的会话，其中，第一会话为在发送所述会话修改请求消息前所述第一终端设备建立的用于传输所述第一终端设备与所述服务供应商和/或所述控制器之间的数据的会话。
需要说明的是，本申请中对于会话建立流程或修改流程中第一核心网网元具体实现不做限制(如，获取建立会话所需的信息等)，可以参考目前会话建立流程或修改流程相关技术中的描述。
示例性地，第二请求消息请求修改或建立的PDU会话用于Remote UAV与USS之间的通信，两者之间可以通过该会话传输远程识别、无人机定位和追踪等信息；或者第二请求消息请求修改或建立的PDU会话同时用于Remote UAV与USS之间的通信和Remote UAV与UAVc之间的通信。
具体地，该第二请求消息中包含上述的第一标识。如，Remote UE的CAA-Level UAV ID。
作为一种可能的实现方式，上述第一请求消息中携带有USS的地址信息，该第二请求消息中也携带该USS的地址信息。
作为另一种可能的实现方式，上述第一请求消息中携带有UAVc的标识，该第二请求消息中也携带该UAVc的标识。
作为又一种可能的实现方式，上述第一请求消息中携带有USS的地址信息和UAVc的标识，该第二请求消息中也携带该USS的地址信息和UAVc的标识。
具体地，在第二请求消息请求PDU会话建立或修改过程中，对Remote UAV进行认证授权，同时确定是否允许该Relay UAV中继Remote UAV的数据，即确定是否允许该Relay UAV中继Remote UAV到USS和/或UAVc的数据。
需要说明的是，第一终端设备可以已经建立用于第一终端设备与服务供应商和/或控制器通信的PDU会话，图3所示的方法还可以包括：
S321，第一终端设备建立第一会话。
该第一会话用于第一终端设备与服务供应商和/或控制器通信。
作为一种可能的实现方式，上述的第二请求消息为PDU会话修改请求消息。例如，Relay UAV重用Relay UAV与USS和/或UAVc之间通信的第一会话，即用于Remote UAV与USS和/或UAVc之间通信的会话和Relay UAV与USS和/或UAVc之间通信的第一会话相同。
可选的，在该实现方式下第二请求消息中包含指示信息，指示信息指示会话用于Remote UAV与USS和/或UAVc之间的通信，以及指示Relay UAV与USS和/或UAVc之间的通信，即该会话同时传输Relay UAV发送到USS和/或UAVc的数据和Remote UAV发送到USS和/或UAVc的数据。
作为另一种可能的实现方式，上述的第二请求消息为PDU会话建立请求消息。例如，Relay UAV不重用Relay UAV与USS和/或UAVc之间通信的第一会话。
可选的，在该实现方式下第二请求消息中包含指示信息，指示信息指示会话用于Remote UAV与USS和/或UAVc之间的通信，即该会话传输Remote UAV发送到USS和 /或UAVc的数据。
示例性地，Relay UAV执行上述的步骤S320之前，需要判断是否需要为Remote UAV的认证授权发起会话建立或修改，即判断是否需要发送第二请求消息，本申请实施例中主要涉及确定发送第二请求消息的情况，因为如果确定不发送第二请求消息证明Relay UAV无法实现为Remote UAV中继通信的功能，而本申请主要考虑的是中继场景下Remote UAV的认证，则图3所示的方法流程还包括：
本申请对步骤S311和S321的先后顺序不作限定。
S322，第一终端设备确定发送第二请求消息。
可选地，Relay UAV可能通过下述方式确定是否需要为Remote UAV的认证授权发起会话建立或修改请求消息：
方式一：
Relay UAV根据Remote UAV提供的CAA-Level UAV ID确定服务Remote UAV的USS与服务Relay UAV的USS是否相同。如果相同，需要发送第二请求消息；如果不同，则不需要发送第二请求消息。
本申请实施例中主要考虑服务Remote UAV的USS与服务Relay UAV的USS相同的情况。
在方式一中，Relay UAV解析CAA-Level UAV ID可以获得USS信息，第一请求消息中可以不携带USS的地址信息。
需要说明的是，Remote UAV提供的CAA-Level UAV ID在构造的过程中包含了USS信息，而Relay UAV能够获知CAA-Level UAV ID的构造方式，本申请对Relay UAV如何解析CAA-Level UAV ID不限定。
方式二：
Relay UAV根据Remote UAV提供的USS的地址信息确定服务Remote UAV的USS与服务Relay UAV的USS是否相同，如果相同，需要发送第二请求消息；如果不同，则不需要发送第二请求消息。
本申请实施例中主要考虑服务Remote UAV的USS与服务Relay UAV的USS相同的情况。
在方式二中，第一请求消息中需要携带USS的地址信息。
方式三：
Relay UAV根据Remote UAV提供的UAVc的标识确定控制Remote UAV的UAVc与控制Relay UAV的UAVc是否相同，如果相同，需要发送第二请求消息；如果不同，则不需要发送第二请求消息。
本申请实施例中主要考虑控制Remote UAV的UAVc与控制Relay UAV的UAVc相同的情况。
在方式三中，第一请求消息中需要携带UAVc的标识。
具体地，SMF接收到上述的第二请求消息之后，需要进行签约信息的查询和/或策略信息的获取，图3所示的方法流程还包括：
S323，第一核心网网元查询签约信息和/或获取策略信息。
具体地，SMF从UDM或PCF查询签约信息或获取策略信息。
作为一种可能的实现方式，UDM或PCF是服务Relay UAV的UDM或PCF，签约信息和/或策略信息中还包括指示Relay UAV是否允许中继其他UAV的数据的指示信息，即指示是否允许中继其他UAV的到USS和/或UAVc的数据的信息，在该实现方式下服务Relay UAV的UDM或PCF和服务Remote UAV的UDM或PCF相同。
作为另一种可能的实现方式，UDM或PCF是服务Remote UAV的UDM/PCF，签约信息和/或策略信息中还包括指示Remote UAV是否允许被其他UAV中继数据的指示信息，即指示是否允许被其他UAV中继到USS和/或UAVc的数据的信息，在该实现方式下服务Relay UAV的UDM或PCF和服务Remote UAV的UDM或PCF不同。
SMF可能通过多种方式与服务Remote UAV的UDM或PCF通信查询签约信息和/或策略信息，本申请对SMF如何与服务Remote UAV的UDM或PCF通信不做限制，可能是直接的或间接的。
进一步地，为了实现Remote UAV的认证授权，图3所示的方法流程还包括：
S330，第一核心网网元向服务供应商发送第三请求消息，或者服务供应商接收来自第一核心网网元的第三请求消息。
具体地，该第三请求消息用于请求USS认证授权Remote UAV的合法性，即Remote UAV在认证授权成功后才能实现中继联网。
作为一种可能的实现方式，该第三请求消息还用于请求USS确定是否允许Relay UAV中继Remote UAV的数据，即是否允许Relay UAV中继Remote UAV到USS和/或UAVc的数据。
作为另一种可能的实现方式，该第三请求消息还用于请求USS授权Remote UAV匹配UAVc，即允许UAVc控制Remote UAV。
示例性地，第三请求消息可以称为证授权请求消息，或者还可以称为认证请求消息等，本申请实施例中对于消息的类型和名称等不做限定。
具体地，该认证授权请求消息中包括Remote UAV的CAA-Level UAV ID。
可选的，该认证授权请求消息中还包括Relay UAV的标识和/或Remote UAV的地址信息。
其中，Relay UAV的标识指的是用于3GPP系统识别Relay UAV的标识如GPSI，或用于USS识别Relay UAV的标识如CAA-Level UAV ID，或IP地址信息，或其他可用于标识Relay UAV的信息，本申请不做限定；Remote UAV的地址信息指Remote UAV的IP地址信息，或其他可用于寻址Remote UAV的信息，本申请不做限定。
在上述的第二请求消息中包含了UAVc的标识(或者说UAVc的标识信息)的情况下，该认证授权请求消息中也可以包含UAVc的标识。
具体地，USS接收到上述的第三请求消息之后，需要进行Remote UAV的合法性的认证，确定Remote UAV的认证授权结果，图3所示的方法流程还包括：
S340，服务供应商确定第二终端设备的认证授权结果。
具体地，该Remote UAV的认证授权结果包括Remaote UAV是否合法，和/或，Relay UAV是否可以中继Remote UAV的数据，即是否可以中继Remote UAV到USS和/或UAVc的数据。
作为一种可能的实现方式，第二终端设备的认证授权结果还包括：Remote UAV是否 匹配到UAVc。
例如，在上述的第三请求消息中包括UAVc的标识的情况下，USS确定是否允许Remote UAV匹配UAVc。
还例如，在上述的第三请求消息中包括Relay UAV的标识的情况下，USS确定是否允许Remote UAV匹配控制Relay UAV的UAVc。
又例如，在上述的第三请求消息中包括Relay UAV的标识的情况下，USS确定是否允许Relay UAV中继Remote UAV的数据。
进一步地，USS需要将Remote UAV的认证授权结果发送给SMF，图3所示的方法流程还包括：
S341，服务供应商向第一核心网网元发送第三响应消息，或者第一核心网网元接收来自服务供应商的第三响应消息。
具体地，该第三响应消息响应于上述的第三请求消息，包含Remote UAV的认证授权结果。
可选的，该第三响应消息中包含UAVc的地址信息。
示例性地，第三响应消息可以显式或隐式的指示是否允许Remote UAV匹配UAVc。
其中，显式指示指的是有单独的指示，例如，第三响应消息中包含指示信息，指示信息用于指示是否允许Remote UAV匹配UAVc；隐式指示指的是没有单独的指示，例如，第三响应消息中没有包含独立的指示，则表示允许Remote UAV匹配UAVc，或者消息中包含UAVc的地址信息，则表示允许Remote UAV匹配UAVc。
示例性地，第三响应消息可以显式或隐式的指示是否允许Remote UAV匹配控制Relay UAV的UAVc。
其中，显式指示指的是有单独的指示，例如，第三响应消息中包含指示信息，指示信息用于指示是否允许Remote UAV匹配控制Relay UAV的UAVc；隐式指示指的是没有单独的指示。例如，第三响应消息中没有包含独立的指示，则表示允许Remote UAV匹配控制Relay UAV的UAVc。
示例性地，第三响应消息可以显式或隐式的指示是否允许Relay UAV中继Remote UAV的数据。
其中，显式指示指的是有单独的指示，例如，第三响应消息中包含指示信息，指示信息用于指示是否允许Relay UAV中继Remote UAV的数据；隐式指示指的是没有单独的指示，例如，第三响应消息中没有包含独立的指示，则表示允许Relay UAV中继Remote UAV的数据。
需要说明的是，若使用显式指示的方式指示结果，则可能出现第三响应消息中既包含Remote UAV的认证授权结果又包含一种或多种指示信息的情况。
在一种可能的实现方式中，将多种结果融合成一个独立的指示信息，即指示是否允许Relay UAV中继该Remote UAV的数据，隐式的包含了Remote UAV是否认证授权成功等信息。
为了便于描述，统一将认证授权结果和指示信息等称为认证授权结果，不再区分。
在一种可能的实现方式中，在第三请求消息中包含了Remote UAV的地址信息的情况下，则USS向UAVc或UAVc侧的核心网网元提供Remote UAV的地址信息。
进一步地，SMF获得上述的Remote UAV的认证授权结果之后，可以通过第二响应消息通知到Relay UAV，图3所示的方法流程还包括：
S342，第一核心网网元向第一终端设备发送第二响应消息，或者第一终端设备接收来自第一核心网网元的第二响应消息。
该第二响应消息用于响应第二请求消息。
该第二响应消息中包含Remote UAV的认证授权结果。
在一种可能的实现方式中，SMF向Relay UAV发送会话建立或修改拒绝消息，消息中包含拒绝原因值，原因值可能是Remote UAV认证授权失败，或不允许Relay UAV中继Remote UAV的数据等。
在一种可能的实现方式中，若第三响应消息中包含了UAVc的地址信息，则SMF在UPF中配置UAVc的地址信息，这种情况下，该会话既可以用于Remote UAV到USS的通信，也用于Remote UAV到UAVc的通信。
需要说明的是，在第二请求消息为PDU会话建立请求消息的场景下，若Remote UAV认证授权结果为成功，则SMF在UPF中建立规则，所述规则用于Remote UAV与USS和/或UAVc之间的通信，即上下行数据的检测转发等规则；
在第二请求消息为PDU会话修改请求消息的场景下，若Remote UAV认证授权结果为成功，则SMF在UPF中更新规则，所述规则用于Relay UAV与USS和/或UAVc之间的通信以及Remote UAV与USS和/或UAVc之间的通信，即上下行数据的检测转发等规则。
例如，在步骤S321中，SMF在UPF中建立规则，所述规则用于Relay UAV与USS和/或UAVc之间的通信，在步骤S342中，SMF在UPF中增加规则，所述规则用于Remote UAV与USS和/或UAVc之间的通信。
进一步地，Relay UAV需要将Remote UAV的认证授权结果发送给Remote UAV，通过第一响应消息通知到Relay UAV，图3所示的方法流程还包括：
S343，第一终端设备向第二终端设备发送第一响应消息。
该第一响应消息用于响应第一请求消息。
该第一响应消息中包含Remote UAV的认证授权结果。
若授权结果指示成功(对于多个结果的情况，指没有失败的结果)，则Relay UAV可以通过该PDU会话中继来自Remote UAV的目的地为UAVc的数据或目的地为USS的数据。
图3所示的方法流程中第二终端设备的认证授权结果可以包括第二终端设备是否匹配到控制器，也可以不包括第二终端设备是否匹配到控制器，即C2认证授权可以是一次性授权的也可以不是一次性授权的。在C2认证授权不是一次性授权，每次飞行都需要进行C2认证授权的情况下，本申请还提供另一种中继通信的方法，如图4所示，图4是本申请提供的另一种中继通信的方法的示意性流程图，包括以下步骤：
S410，第二终端设备向第一终端设备发送第一指示信息，或者第一终端设备接收来自第二终端设备的第一指示信息。
该第一指示信息用于指示Remote UAV请求与控制器建立通信。本申请中以第二终端设备请求与控制器建立的通信为C2通信为例进行说。针对终端设备为除UAV之外的设 备的情况下第二终端设备请求与控制器建立的通信可以为其他名称，本申请对此不做限定。也就是说第一指示信息用于指示请求进行C2通信。
例如，Remote UAV已经通过注册流程或图3所示的流程完成Remote UAV是否合法的认证授权了，但C2通信认证授权不是一次性授权，每次飞行都需要进行C2通信认证授权。
示例性地，第一指示信息可以携带在Remote UAV和Relay UAV之间的直接通信请求(direct communication request)消息中，该第一指示信息指示Remote UAV期望建立C2通信。
可选的，第二终端设备还可以向第一终端设备发送以下信息中的至少一个：
飞行计划信息、Remote UAV的标识、UAVc的标识和USS的地址信息中的一个或多个。
其中，Remote UAV的标识可能是用于3GPP系统识别Remote UAV的标识如GPSI，或用于USS识别Remote UAV的标识如CAA-Level UAV ID，或其他可用于标识Remote UAV的信息，该实施例中对此不做限定。所述USS为服务Remote UAV的USS。所述UAVc为Remote UAV期望匹配的UAVc，即UAVc用于控制Remote UAV。
示例性地，USS的地址信息可以是USS的IP地址信息，或其他可用于寻址USS的信息，本申请不做限定。
示例性地，UAVc的标识可以是用于3GPP系统识别UAVc的标识如通用公开用户标识(generic public subscription identity，GPSI)，或用于USS识别UAVc的标识如CAA-Level UAVc ID，或IP地址信息，或其他可用于标识UAVc的信息，本申请不做限定。
应理解，第二终端设备向第一终端设备发送第一指示信息之前，第二终端设备和第一终端设备之间已经建立连接，具体链接建立方式可以参考上述图3中的步骤S311的描述，这里不再赘述。
进一步地，第一终端设备接收到上述的第一指示信息之后，需要向第一核心网网元发送第一指示信息，以使得第一核心网网元触发认证授权第二终端设备的C2通信认证授权，图4所示的方法还可以包括：
S420，第一终端设备向第一核心网网元发送第一指示信息，或者第一核心网网元接收来自第一终端设备的第一指示信息。
该第一指示信息可以携带在用于请求建立或修改PDU会话的请求消息中，该请求修改或建立的PDU会话用于Remote UAV的C2通信。
示例性地，第一终端设备可以已经建立用于第一终端设备与服务供应商和/或控制器通信的第一会话，如图3中步骤S321所示，这里不再赘述。
作为一种可能的实现方式，第一指示信息可以携带在Relay UAV发起会话修改流程的PDU会话修改请求消息中。例如，Relay UAV重用Relay UAV与USS和/或UAVc之间通信的第一会话，即用于Remote UAV与USS和/或UAVc之间通信的会话和Relay UAV与USS和/或UAVc之间通信的第一会话相同。
作为另一种可能的实现方式，第一指示信息可以携带在Relay UAV发起会话建立流程的PDU会话建立请求消息中。例如，Relay UAV不重用Relay UAV与USS和/或UAVc之间通信的第一会话。
可选的，第一终端设备还可以向第一核心网网元发送以下信息中的至少一个：
C2通信指示信息、飞行计划信息、Remote UAV的标识、UAVc的标识和USS的地址信息中的一个或多个。
在一种可能的实现方式中，用DNN和/或S-NSSAI可以用于标识C2通信会话，上述的第一指示信息的具体体现形式可以是DNN和/或S-NSSAI，无需在用于请求建立或修改PDU会话的请求消息单独增加信元用于指示C2通信。
作为一种可能的实现方式，第一终端设备接收到飞行计划信息，可以向第一核心网网元发送该飞行计划信息。
作为另一种可能的实现方式，建立一个新的会话用于C2通信，第一终端设备向第一核心网网元发送Remote UAV的标识。
作为又一种可能的实现方式，第一终端设备接收到UAVc的标识，可以向第一核心网网元发送UAVc的标识。
作为又一种可能的实现方式，第一终端设备接收到USS的地址信息，可以向第一核心网网元发送USS的地址信息。
具体地，SMF接收到上述的第一指示信息之后，需要确定第二终端设备是否允许与所述控制器通信，图4所示的方法流程还包括：
S430，第一核心网网元确定第二终端设备是否允许与所述控制器通信。
其中，第二终端设备是否允许与所述控制器可以称为Remote UAV的C2认证授权结果。
具体地，SMF可能通过下述方式确定Remote UAV的C2认证授权结果：
在一种可能的实现方式中，若Remote UAV没有进行过Remote UAV的合法认证授权结果，或之前的Remote UAV的合法认证授权结果指示失败，或不允许Relay UAV中继Remote UAV的数据，则SMF确定Remote UAV的C2认证授权失败。
在另一种可能的实现方式中，若Remote UAV有成功的Remote UAV的合法认证授权结果，且允许Relay UAV中继Remote UAV的数据，且Relay UAV未携带Remote UAV的航空信息和/或UAVc的标识，则SMF确定Remote UAV的C2认证授权成功。
在又一种可能的实现方式中，若Remote UAV有成功的Remote UAV的合法认证授权结果，且允许Relay UAV中继Remote UAV的数据，且Relay UAV携带Remote UAV的航空信息和/或UAVc的标识，则SMF无法确定Remote UAV的C2授权结果，需要进一步向USS请求授权。
由上述可知，SMF需要基于Remote UAV是否成功认证授权以及是否允许Relay UAV中继Remote UAV的数据，进一步确定Remote UAV的C2授权结果，图4所示的方法流程还包括：
S431，第一核心网网元确认第二终端设备的认证授权结果。
该第二终端设备的认证授权结果包括：Remote UAV是否成功认证授权以及是否允许Relay UAV中继Remote UAV的数据。
示例性地，SMF可能从其他网元查询到上述信息，如AMF、UDM或NEF等，也可以根据自身存储的信息确定第二终端设备的认证授权结果，本申请对此不做限定。
还可以通过执行以下步骤确定Remote UAV的C2认证授权结果：
S432，第一核心网网元向服务供应商发送第四请求消息，或者服务供应商接收来自第一核心网网元的第四请求消息。
第四请求消息用于请求所述服务供应商确定Remote UAV是否允许与控制器通信，可以称为C2认证授权请求消息。
可选地，第四请求消息中包含Remote UAV的航空信息和/或Remote提供的UAVc的标识。
可选的，第四请求消息中包含Relay UAV的标识。
进一步地，服务供应商接收到第四请求消息之后，需要确定是否允许C2通信，图4所示的方法流程还包括：
S433，服务供应商确定第二终端设备是否允许与所述控制器通信。
在第四请求消息中包含Remote UAV的航空信息的情况下，USS根据航空信息进行飞行路径相关的授权；
在第四请求消息中包含UAVc的标识的情况下，USS根据UAVc的标识进行匹配相关的授权；USS根据Relay UAV的标识进行中继相关的授权。
服务供应商确定是否允许C2通信之后，将C2认证授权结果发送给第一核心网网元，图4所示的方法流程还包括：
S434，服务供应商向第一核心网网元发送第四响应消息，或者第一核心网网元接收来自服务供应商的第四响应消息。
第四响应消息包括第二指示信息，第二指示信息用于指示第二终端设备是否允许与所述控制器通信。
在第一核心网网元可以确定Remote UAV的C2认证授权结果，和/或，第一核心网网元接收来自服务供应商的C2认证授权结果的情况下，执行以下步骤：
S440，第一核心网网元向第一终端设备发送第二指示信息。
第二指示信息用于指示第二终端设备是否允许与所述控制器通信。
可以通过显式或隐式的方式指示第二终端设备是否允许与所述控制器通信。显式的方式，即在消息中包含指示信息，指示信息用于指示是否允许C2通信。隐式的方式，即没有明显的指示信息，如SMF通过发送会话建立/修改接受消息表示允许C2通信，而通过发送会话建立/修改拒绝消息表示拒绝C2通信，在拒绝的场景，可以提供拒绝的原因值。本申请对C2授权结果的提供方式不做限定。
S450、第一终端设备向第二终端设备发送第二指示信息。
类似的，可以通过显式或显式的方式发送第二指示信息。
图3所示的流程和图4所示的流程的区别在于，图3所示的流程中USS认证授权了Remote UAV的合法性，并且可以授权了Remote UAV和UAVc的匹配，后续飞行时也不需要再次进行授权。而图4所示的流程中假设USS仅认证授权了Remote UAV的合法性，但是Remote UAV和UAVc的匹配以及飞行信息等需要在每次飞行时进行认证授权。也就是说，图3所示的流程可以一次性授权Remote UAV的合法性和C2认证授权，流程更加简化；图4所示的流程需要多次C2认证授权，更有利于监管。
本申请还提供一种中继通信的方法，能够更加简化Remote UAV的中继联网流程，下面结合图5进行说明，图5是本申请实施例提供的又一种中继通信的方法的示意性流程图， 包括以下步骤：
S510、第一终端设备向服务供应商发送能力信息，或者服务供应商接收来自第一终端设备的能力信息。
该能力信息用于指示Relay UAV中继Remote UAV的数据的能力。
可选的，Relay UAV还可以向服务供应商发送期望中继的Remote UAV的标识，和/或，UAS的标识。
可选的，Relay UE或UAVc还可以向服务供应商发送UAVc的标识，对于同一个UAVc，USS可以生成一个RSC用于该UAVc控制其他Remote UAV和Relay UAV。
Relay UAV可以通过本地配置或Remote UAV上报等方式获取上述标识。
所述能力信息指Relay UAV可以中继另一个UAV的数据。
在一种可能的实现方式中，能力信息指Relay UAV可以中继另一个UAV一种或多种数据类型的数据，其中，数据类型包括以下至少一种：
C2通信数据(如，Remote UAV到UAVc的数据)、Remote UAV到USS的数据、Remote UAV的非UAV业务相关的数据，或者其他可能数据类型，本申请对此不做限定。
上述的Remote UAV的标识可以是一个或多个用于标识Remote UAV的信息(如，USS为Remote UAV分配的CAA-Level UAV ID，3GPP系统识别Remote UAV的标识等)，该实施例中对Remote UAV的标识的形式不做限定，这里不再赘述。
UAS的标识指的是Relay UAV所在的UAS的标识(如，3GPP系统识别UAS的标识)，该实施例中UAS的标识的形式不做限定。
需要说明的是，Relay UAV向USS提供的信息的方式是不限定的，例如可以是以下方式中的任意种：
Relay UAV通过一个消息直接发送给USS，或Relay UAV在注册流程中向AMF发送，然后AMF通过NEF间接或直接发送给USS，或Relay UAV在会话管理流程中向SMF发送，然后SMF通过NEF间接或直接发送给USS，或其他可能的传输方式，本申请不做限定。
UAVc的标识指的是可以同时控制Relay UAV和Remote UAV的UAV控制器的标识(如，3GPP系统识别UAVc的标识)，该实施例中对UAVc的标识的形式不做限定。
进一步地，服务供应商接收来自第一终端设备的能力信息之后，可以基于能力信息确定是否允许Relay UAV中继其他UAV的数据，该实施中主要考虑允许的情况，图5所示的方法流程还包括：
S520，服务供应商向第一终端设备发送中继服务码，或者第一终端设备接收来自服务供应商的中继服务码。
具体地，USS确定是否允许Relay UAV中继其他UAV的数据，若允许，则向Relay UAV提供中继服务码(relay service code，RSC)。
在一种可能的实现方式中，步骤S510中Relay UAV提供了Remote UE的标识，USS确定是否允许Relay UAV中继Remote UAV的数据。
在一种可能的实现方式中，步骤S510中Relay UAV提供了UAS的标识，USS确定是否允许Relay UAV中继UAS中其他UAV的数据。
在一种可能的实现方式中，步骤S510中Relay UAV提供的中继UAV的能力信息指 示Relay UAV可以中继另一个UAV一种或多种类型的数据，USS确定是否允许Relay UAV中继Relay UAV支持的一种或多种类型的数据。
在一种可能的实现方式中，USS结合上述多种信息进行判断。
如果步骤S510中携带了UAVc的标识，则USS所生成的RSC可以与UAVc关联(如，一个RSC与一个UAVc的标识绑定)。
在第一终端设备获得上述的中继服务码之后，第二终端设备可以根据中继服务码发现第一终端设备，图5所示的方法流程还包括：
S530，第二终端设备根据中继服务码发现第一终端设备。
如果RSC与UAVc的标识有关联关系，则Relay UAV与Remote UAV进行连接时，需要确认Remote UAV是否连接到RSC所对应的UAVc；或者，
如果Remote UAV与Relay UAV通过某个UAVc所对应的RSC建立了连接，则Remote UAV仅能通过Relay UAV连接到相应的UAVc上。
进一步地，第二终端设备可以通过第一终端设备中继数据，具体地：
Relay UAV为传输Remote UAV的数据建立或修改会话，Relay UAV通过该会话传输Remote UAV的数据。
图5所示的流程中Relay UAV获得Relay Service Code后，Remote UAV可通过中继联网，简化中继通信流程。
需要说明的是，本申请中的“会话”为PDU会话为例，在实际应用中，PDU会话也可以被替换为其他的会话，本申请对此不做限定。
应理解，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
还应理解，在本申请的各个实施例中，如果没有特殊说明以及逻辑冲突，不同的实施例之间的术语和/或描述具有一致性、且可以相互引用，不同的实施例中的技术特征根据其内在的逻辑关系可以组合形成新的实施例。
还应理解，在上述一些实施例中，主要以现有的网络架构中的设备为例进行了示例性说明(如网络设备、终端设备等等)，应理解，对于设备的具体形式本申请实施例不作限定。例如，在未来可以实现同样功能的设备都适用于本申请实施例。
可以理解的是，上述各个方法实施例中，由设备(如上述第一终端设备、第二终端设备、第一核心网网元、服务供应商等)实现的方法和操作，也可以由设备的部件(例如芯片或者电路)实现。
以上，结合图3至图5详细说明了本申请实施例提供的中继通信的方法。上述中继通信的方法主要从各个网元之间交互的角度进行了介绍。可以理解的是，各个网元，为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。
本领域技术人员应该可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
以下，结合图6和图7详细说明本申请实施例提供的中继通信的装置。应理解，装 置实施例的描述与方法实施例的描述相互对应，因此，未详细描述的内容可以参见上文方法实施例，为了简洁，部分内容不再赘述。
本申请实施例可以根据上述方法示例对发射端设备或者接收端设备进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。下面以采用对应各个功能划分各个功能模块为例进行说明。
图6是本申请实施例提供的装置600的示意性框图。该装置600包括收发单元610和处理单元620。收发单元610可以实现相应的通信功能，处理单元620用于进行数据处理。收发单元610还可以称为通信接口或通信单元，收发单元610实现获取信息功能的情况下，还可以称为获取单元。
可选地，该装置600还可以包括存储单元，该存储单元可以用于存储指令和/或数据，处理单元620可以读取存储单元中的指令和/或数据，以使得装置实现前述方法实施例。
该装置600可以用于执行上文方法实施例中设备(如上述第一终端设备、第二终端设备、第一核心网网元、服务供应商等)所执行的动作，这时，该装置600可以为设备或者可配置于设备中的部件，收发单元610用于执行上文方法实施例中设备的收发相关的操作，处理单元620用于执行上文方法实施例中设备的处理相关的操作。
作为一种设计，该装置600用于执行上文方法实施例中第一终端设备所执行的动作。
一种可能的实现方式，收发单元610，接收来自第二终端设备的第一请求消息，该第一请求消息中包括第一标识，该第一标识为服务供应商分配的该第二终端设备的标识；
收发单元610，还用于向第一核心网网元发送第二请求消息，该第二请求消息中包括该第一标识，其中，该第二请求消息用于请求建立该第二终端设备与控制该第二终端设备的控制器和/或该服务供应商之间且通过所述第一终端设备进行的通信。
可选地，收发单元610，还用于接收来自该第一核心网网元的响应于该第二请求消息的第二响应消息，该第二响应消息中包括该第二终端设备的认证授权结果，其中，该第二终端设备的认证授权结果包括该第二终端设备是否合法，和/或，该装置600是否允许中继该第二终端设备的数据。
可选地，收发单元610，还用于接收来自该第二终端设备的第一指示信息，该第一指示信息用于指示该第二终端设备请求与该控制器建立通信；收发单元610，还用于向该第一核心网网元发送该第一指示信息。
可选地，收发单元610，还用于接收来自该第一核心网网元的第二指示信息，该第二指示信息用于指示第二终端设备是否允许与该控制器通信；收发单元610，还用于向该第二终端设备发送该第二指示信息。
可选地，收发单元610，还用于向该第二终端设备发送响应于该第一请求消息的第一响应消息，该第一响应消息中包括该第二终端设备的认证授权结果。
可选地，处理单元620，用于确定服务该第二终端设备的服务供应商和服务该第一终端设备的服务供应商相同，和/或，该第一终端设备确定控制该第一终端设备的控制器和控制该第二终端设备的控制器相同。
可选地，处理单元620，确定服务该第二终端设备的供应商和服务该第一终端设备的供应商相同，包括：该处理单元620根据该第一标识确定服务该第二终端设备的服务供应商和服务该装置600的服务供应商相同；和/或，该第一请求消息中还包括该服务供应商的地址信息，该处理单元620根据该地址信息确定服务该第二终端设备的服务供应商和服务该装置600的服务供应商相同。
可选地，处理单元620，确定控制该第一终端设备的控制器和控制该第二终端设备的控制器相同，包括：该处理单元620根据该控制器的标识确定控制该装置600的控制器和控制该第二终端设备的控制器相同。
另一种可能的实现方式，收发单元610，用于向服务供应商发送能力信息，该能力信息用于指示该第一终端设备中继其他终端设备数据的能力；
收发单元610，还用于接收来自该服务供应商的中继服务码，该中继服务码用于指示该第一终端设备允许中继其他终端设备数据。
可选地，收发单元610，用于向该终端设备的供应商发送第二终端设备的标识，和/或，终端设备系统的标识，其中，该第二终端设备为通过中继方式联网的终端设备。
该装置600可实现对应于根据本申请实施例的方法实施例中的第一终端设备执行的步骤或者流程，该装置600可以包括用于执行方法实施例中的第一终端设备执行的方法的单元。并且，该装置600中的各单元和上述其他操作和/或功能分别为了实现方法实施例中的第一终端设备中的方法实施例的相应流程。
其中，当该装置600用于执行图3中的方法时，收发单元610可用于执行方法中的收发步骤，如步骤S311、S310、S321、S320、S342和S343；处理单元620可用于执行方法中的处理步骤，如步骤S322。
当该装置600用于执行图4中的方法时，收发单元610可用于执行方法中的收发步骤，如步骤S410、S420、S440和S450。
当该装置600用于执行图5中的方法时，收发单元610可用于执行方法中的收发步骤，如步骤S510、S520和S530。
应理解，各单元执行上述相应步骤的具体过程在上述方法实施例中已经详细说明，为了简洁，在此不再赘述。
作为另一种设计，该装置600用于执行上文方法实施例中第二终端设备所执行的动作。
一种可能的实现方式，收发单元610，用于获取第一标识，该第一标识为服务供应商分配的该第二终端设备的标识；
收发单元610，用于向第一终端设备发送第一请求消息，该第一请求消息中包括该第一标识，其中，该第二终端设备为通过中继方式联网的终端设备。
可选地，收发单元610，用于接收来自该第一终端设备的响应于该第一请求消息的第一响应消息，该第一响应消息中包括该第二终端设备的认证授权结果，其中，该第二终端设备的认证授权结果包括该第二终端设备是否合法，和/或，该第一终端设备是否允许中继该第二终端设备的数据。
可选地，收发单元610，用于向该第一终端设备发送第一指示信息，该第一指示信息用于指示该第二终端设备请求与控制器建立通信。
可选地，收发单元610，用于接收来自该第一终端设备的第二指示信息，该第二指示 信息用于指示第二终端设备是否允许与该控制器通信。
另一种可能的实现方式，收发单元610，用于获取中继服务码，该中继服务码用于指示该第一终端设备允许中继其他终端设备数据；
收发单元610，用于根据该中继服务码发现该第一终端设备。
该装置600可实现对应于根据本申请实施例的方法实施例中的第二终端设备执行的步骤或者流程，该装置600可以包括用于执行方法实施例中的第二终端设备执行的方法的单元。并且，该装置600中的各单元和上述其他操作和/或功能分别为了实现方法实施例中的第二终端设备中的方法实施例的相应流程。
其中，当该装置600用于执行图3中的方法时，收发单元610可用于执行方法中的收发步骤，如步骤S311、S310和S343。
当该装置600用于执行图4中的方法时，收发单元610可用于执行方法中的收发步骤，如步骤S410和S450。
当该装置600用于执行图5中的方法时，收发单元610可用于执行方法中的收发步骤，如步骤S530。
应理解，各单元执行上述相应步骤的具体过程在上述方法实施例中已经详细说明，为了简洁，在此不再赘述。
作为又一种设计，该装置600用于执行上文方法实施例中第一核心网网元所执行的动作。
一种可能的实现方式，收发单元610，用于接收来自第一终端设备的第二请求消息，该第二请求消息中包括第一标识，该第一标识为服务供应商分配的该第二终端设备的标识；
收发单元610，用于向该服务供应商发送第三请求消息，该第三请求消息中包括该第一标识和该第一终端设备的标识，该第三请求消息用于请求该服务供应商对该第二终端设备进行认证授权，其中，该第二终端设备为通过中继方式联网的终端设备。
可选地，收发单元610，用于接收来自该服务供应商的响应于该第三请求消息的第三响应消息，该第三响应消息中包括该第二终端设备的认证授权结果，其中，该第二终端设备的认证授权结果包括该第二终端设备是否合法，和/或，该第一终端设备是否允许中继该第二终端设备的数据。
可选地，收发单元610，用于接收来自第一终端设备的第一指示信息，该第一指示信息用于指示该第二终端设备请求与该控制器建立通信；
处理单元620，用于确定该第二终端设备是否允许与该控制器通信。
可选地，处理单元620确定该第二终端设备是否允许与该控制器通信，包括：该处理单元620根据该第二终端设备认证授权结果确定该第二终端设备是否允许与该控制器通信；和/或，该处理单元620从该服务供应商获取该第二终端设备是否允许与该控制器通信。
可选地，收发单元610，用于向该服务供应商发送第四请求消息，该第四请求消息用于请求该服务供应商确定该第二终端设备是否允许与该控制器通信；
收发单元610，用于接收来自该服务供应商的响应于该第四请求消息的第四响应消息，该第四响应消息包括第二指示信息，该第二指示信息用于指示第二终端设备是否允许与该控制器通信。
收发单元610，用于向该第一终端设备发送响应于该第二请求消息的第二响应消息，该第二响应消息中包括该第二终端设备的认证授权结果。
该装置600可实现对应于根据本申请实施例的方法实施例中的第一核心网网元执行的步骤或者流程，该装置600可以包括用于执行方法实施例中的第一核心网网元执行的方法的单元。并且，该装置600中的各单元和上述其他操作和/或功能分别为了实现方法实施例中的第一核心网网元中的方法实施例的相应流程。
其中，当该装置600用于执行图3中的方法时，收发单元610可用于执行方法中的收发步骤，如步骤S321、S320、S330、S341和S342；处理单元620可用于执行方法中的处理步骤，如步骤S323。
当该装置600用于执行图4中的方法时，收发单元610可用于执行方法中的收发步骤，如步骤S420、S432、S434和S440；处理单元620可用于执行方法中的处理步骤，如步骤S431和S430。
应理解，各单元执行上述相应步骤的具体过程在上述方法实施例中已经详细说明，为了简洁，在此不再赘述。
作为又一种设计，该装置600用于执行上文方法实施例中服务供应商所执行的动作。
一种可能的实现方式，收发单元610，用于接收来自第一核心网网元的第三请求消息，该第三请求消息中包括第一标识，该第一标识为该服务供应商分配的该第二终端设备的标识；处理单元620，用于根据该第一标识对该第二终端设备进行认证授权，其中，该第二终端设备为通过中继方式联网的终端设备。
可选地，收发单元610，用于向该第一核心网网元发送响应于该第三请求消息的第三响应消息，该第三响应消息中包括该第二终端设备的认证授权结果，其中，该第二终端设备的认证授权结果包括该第二终端设备是否合法，和/或，该第一终端设备是否允许中继该第二终端设备的数据。
可选地，收发单元610，用于接收来自该第一核心网网元的第四请求消息；
处理单元620，用于根据该第四请求消息确定该第二终端设备是否允许与该控制器通信；
收发单元610，用于向该第一核心网网元发送应于该第四请求消息的第四响应消息，该第四响应消息包括第二指示信息，该第二指示信息用于指示第二终端设备是否允许与该控制器通信。
另一种可能的实现方式，收发单元610，用于接收来自第一终端设备的能力信息，该能力信息用于指示该第一终端设备中继其他终端设备数据的能力；
收发单元610，用于向该第一终端设备发送中继服务码，该中继服务码用于指示该第一终端设备允许中继其他终端设备数据。
该装置600可实现对应于根据本申请实施例的方法实施例中的服务供应商执行的步骤或者流程，该装置600可以包括用于执行方法实施例中的服务供应商执行的方法的单元。并且，该装置600中的各单元和上述其他操作和/或功能分别为了实现方法实施例中的服务供应商中的方法实施例的相应流程。
其中，当该装置600用于执行图3中的方法时，收发单元610可用于执行方法中的收发步骤，如步骤S330和S341；处理单元620可用于执行方法中的处理步骤，如步骤S340。
当该装置600用于执行图4中的方法时，收发单元610可用于执行方法中的收发步骤，如步骤S432和S434；处理单元620可用于执行方法中的处理步骤，如步骤S433。
当该装置600用于执行图5中的方法时，收发单元610可用于执行方法中的收发步骤，如步骤S510和S520。
应理解，各单元执行上述相应步骤的具体过程在上述方法实施例中已经详细说明，为了简洁，在此不再赘述。
上文实施例中的处理单元620可以由至少一个处理器或处理器相关电路实现。收发单元610可以由收发器或收发器相关电路实现。存储单元可以通过至少一个存储器实现。
如图7所示，本申请实施例还提供一种装置700。该装置700包括处理器710，还可以包括一个或多个存储器720。处理器710与存储器720耦合，存储器720用于存储计算机程序或指令和/或数据，处理器710用于执行存储器720存储的计算机程序或指令和/或数据，使得上文方法实施例中的方法被执行。可选地，该装置700包括的处理器710为一个或多个。
可选地，该存储器720可以与该处理器710集成在一起，或者分离设置。
可选地，如图7所示，该装置700还可以包括收发器730，收发器730用于信号的接收和/或发送。例如，处理器710用于控制收发器730进行信号的接收和/或发送。
作为一种方案，该装置700用于实现上文方法实施例中由设备(如上述第一终端设备、第二终端设备、第一核心网网元、服务供应商等)执行的操作。
应理解，图7仅为示例而非限定，上述包括收发单元和处理单元的设备可以不依赖于图7所示的结构。
当该装置700为芯片时，该芯片包括收发单元和处理单元。其中，收发单元可以是输入输出电路、通信接口；处理单元为该芯片上集成的处理器或者微处理器或者集成电路。当然装置700还可以为一个芯片系统或处理系统，使得安装该装置700的设备可以实现本申请实施例的方法和功能。例如，处理单元可以为芯片系统或处理系统中的处理电路，实现对安装了该芯片系统或处理系统的设备的控制，还可以耦合链接存储单元，调用存储单元中的指令，使得设备可以实现本申请实施例的方法和功能，收发单元，可以为芯片系统或处理系统中的输入输出电路，将芯片系统处理好的信息输出，或将待处理的数据或信令信息输入芯片系统进行处理。
本申请实施例还提供一种计算机可读存储介质，其上存储有用于实现上述方法实施例中由设备(如上述第一终端设备、第二终端设备、第一核心网网元、服务供应商等)执行的方法的计算机指令。
例如，该计算机程序被计算机执行时，使得该计算机可以实现上述方法实施例中由网络设备执行的方法。
本申请实施例还提供一种包含指令的计算机程序产品，该指令被计算机执行时使得该计算机实现上述方法实施例中由设备(如上述第一终端设备、第二终端设备、第一核心网网元、服务供应商等)执行的方法。
本申请实施例还提供一种通信系统，该通信系统包括上文实施例中的设备(如上述第一终端设备、第二终端设备、第一核心网网元、服务供应商等)，如包括Relay UE、Remote UE和SMF。
上述提供的任一种装置中相关内容的解释及有益效果均可参考上文提供的对应的方法实施例，此处不再赘述。
应理解，本申请实施例中提及的处理器可以是中央处理单元(central processing unit，CPU)，还可以是其他通用处理器、数字信号处理器(digital signal processor，DSP)、专用集成电路(application specific integrated circuit，ASIC)、现成可编程门阵列(field programmable gate array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
还应理解，本申请实施例中提及的存储器可以是易失性存储器和/或非易失性存储器。其中，非易失性存储器可以是只读存储器(read-only memory，ROM)、可编程只读存储器(programmable ROM，PROM)、可擦除可编程只读存储器(erasable PROM，EPROM)、电可擦除可编程只读存储器(electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(random access memory，RAM)。例如，RAM可以用作外部高速缓存。作为示例而非限定，RAM可以包括如下多种形式：静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(dynamic RAM，DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(direct rambus RAM，DR RAM)。
需要说明的是，当处理器为通用处理器、DSP、ASIC、FPGA或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件时，存储器(存储模块)可以集成在处理器中。
还需要说明的是，本文描述的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的保护范围。
在本申请所提供的几个实施例中，应该理解到，所揭露的装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。此外，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元实现本申请提供的方案。
另外，在本申请各个实施例中的各功能单元可以集成在一个单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。例如，所述计算机可以是个人计算机，服务器，或者网络设备等。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘(solid state disk，SSD)等。例如，前述的可用介质可以包括但不限于：U盘、移动硬盘、只读存储器(read-only memory，ROM)、随机存取存储器(random access memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (27)

  1. 一种中继通信的方法，其特征在于，包括：
    第一终端设备接收来自第二终端设备的第一请求消息，所述第一请求消息中包括第一标识，所述第一标识为服务供应商分配的所述第二终端设备的标识；
    所述第一终端设备向第一核心网网元发送第二请求消息，所述第二请求消息中包括所述第一标识，
    其中，所述第二请求消息用于请求建立所述第二终端设备与所述服务供应商和/或控制器之间且通过所述第一终端设备进行的通信。
  2. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    所述第一终端设备接收来自所述第一核心网网元的响应于所述第二请求消息的第二响应消息，所述第二响应消息中包括所述第二终端设备的认证授权结果，
    其中，所述第二终端设备的认证授权结果包括所述第二终端设备是否合法，和/或，所述第一终端设备是否允许中继所述第二终端设备的数据。
  3. 根据权利要求2所述的方法，其特征在于，所述第二终端设备的认证授权结果还包括：
    所述第二终端设备是否匹配到所述控制器。
  4. 根据权利要求2或3所述的方法，其特征在于，所述方法还包括：
    所述第一终端设备接收来自所述第二终端设备的第一指示信息，所述第一指示信息用于指示所述第二终端设备请求与所述控制器建立通信；
    所述第一终端设备向所述第一核心网网元发送所述第一指示信息。
  5. 根据权利要求4所述的方法，其特征在于，所述方法还包括：
    所述第一终端设备接收来自所述第一核心网网元的第二指示信息，所述第二指示信息用于指示第二终端设备是否允许与所述控制器通信；
    所述第一终端设备向所述第二终端设备发送所述第二指示信息。
  6. 根据权利要求2至5中任一项所述的方法，其特征在于，所述方法还包括：
    所述第一终端设备向所述第二终端设备发送响应于所述第一请求消息的第一响应消息，所述第一响应消息中包括所述第二终端设备的认证授权结果。
  7. 根据权利要求1至6中任一项所述的方法，其特征在于，在所述第一终端设备向第一核心网网元发送第二请求消息之前，所述方法还包括：
    所述第一终端设备确定服务所述第二终端设备的服务供应商和服务所述第一终端设备的服务供应商相同，和/或，
    所述第一终端设备确定控制所述第一终端设备的控制器和所述控制器相同。
  8. 根据权利要求7所述的方法，其特征在于，所述第一终端设备确定服务所述第二终端设备的供应商和服务所述第一终端设备的供应商相同，包括：
    所述第一终端设备根据所述第一标识确定服务所述第二终端设备的服务供应商和服务所述第一终端设备的服务供应商相同；和/或，
    所述第一请求消息中还包括所述服务供应商的地址信息，所述第一终端设备根据所述 地址信息确定服务所述第二终端设备的服务供应商和服务所述第一终端设备的服务供应商相同。
  9. 根据权利要求7或8所述的方法，其特征在于，所述第一请求消息中还包括所述控制器的标识，
    所述第一终端设备确定控制所述第一终端设备的控制器和所述控制器相同，包括：
    所述第一终端设备根据所述控制器的标识确定控制所述第一终端设备的控制器和所述控制器相同。
  10. 根据权利要求1至9中任一项所述的方法，其特征在于，所述第一核心网网元为会话管理功能网元SMF，所述第二请求消息为会话建立请求消息或会话修改请求消息。
  11. 根据权利要求10所述的方法，其特征在于，所述第二请求消息为会话建立请求消息时，所述第二请求消息用于建立所述第一终端设备与所述服务供应商和/或所述控制器之间的第二会话，所述第二会话用于传输所述第二终端设备与所述服务供应商和/或所述控制器之间的数据；或
    所述第二请求消息为会话修改请求消息时，所述第二请求消息用于请求将所述第一会话修改为进一步传输所述第二终端设备与所述服务供应商和/或所述控制器之间的数据的会话；在发送所述会话修改请求消息前，所述第一会话为所述第一终端设备建立的用于传输所述第一终端设备与所述服务供应商和/或所述控制器之间的数据的会话。
  12. 根据权利要求1至11中任一项所述的方法，其特征在于，所述控制器用于控制所述第二终端设备；所述服务供应商是第三方实体，用于为所述第一终端设备和所述第二终端设备提供服务。
  13. 一种中继通信的方法，其特征在于，包括：
    第一核心网网元接收来自第一终端设备的第二请求消息，所述第二请求消息中包括第一标识，所述第一标识为服务供应商分配的第二终端设备的标识；
    所述第一核心网网元向所述服务供应商发送第三请求消息，所述第三请求消息中包括所述第一标识和所述第一终端设备的标识，所述第三请求消息用于请求所述服务供应商对所述第二终端设备进行认证授权，
    其中，所述第二请求消息用于请求建立所述第二终端设备与所述服务供应商和/或控制器之间且通过所述第一终端设备进行的通信。
  14. 根据权利要求13所述的方法，其特征在于，所述方法还包括：
    所述第一核心网网元接收来自所述服务供应商的响应于所述第三请求消息的第三响应消息，所述第三响应消息中包括所述第二终端设备的认证授权结果，
    其中，所述第二终端设备的认证授权结果包括所述第二终端设备是否合法，和/或，所述第一终端设备是否允许中继所述第二终端设备的数据。
  15. 根据权利要求14所述的方法，其特征在于，所述第二终端设备的认证授权结果还包括：所述第二终端设备是否匹配到所述控制器。
  16. 根据权利要求13或14所述的方法，其特征在于，所述方法还包括：
    所述第一核心网网元接收来自第一终端设备的第一指示信息，所述第一指示信息用于指示所述第二终端设备请求与所述控制器建立通信；
    所述第一核心网网元确定所述第二终端设备是否允许与所述控制器通信。
  17. 根据权利要求16所述的方法，其特征在于，所述第一核心网网元确定所述第二终端设备是否允许与所述控制器通信，包括：
    所述第一核心网网元根据所述第二终端设备认证授权结果确定所述第二终端设备是否允许与所述控制器通信；和/或，
    所述第一核心网网元从所述服务供应商获取所述第二终端设备是否允许与所述控制器通信。
  18. 根据权利要求17所述的方法，其特征在于，所述第一核心网网元从所述服务供应商获取所述第二终端设备是否允许与所述控制器通信，包括：
    所述第一核心网网元向所述服务供应商发送第四请求消息，所述第四请求消息用于请求所述服务供应商确定所述第二终端设备是否允许与所述控制器通信；
    所述第一核心网网元接收来自所述服务供应商的响应于所述第四请求消息的第四响应消息，所述第四响应消息包括第二指示信息，所述第二指示信息用于指示第二终端设备是否允许与所述控制器通信。
  19. 根据权利要求18所述的方法，其特征在于，所述方法还包括：
    所述第一核心网网元向所述第一终端设备发送所述第二指示信息。
  20. 根据权利要求14至19中任一项所述的方法，其特征在于，所述方法还包括：
    所述第一核心网网元向所述第一终端设备发送响应于所述第二请求消息的第二响应消息，所述第二响应消息中包括所述第二终端设备的认证授权结果。
  21. 根据权利要求13至20中任一项所述的方法，其特征在于，所述第一核心网网元为会话管理功能网元SMF，所述第二请求消息为会话建立请求消息或会话修改请求消息。
  22. 根据权利要求21所述的方法，其特征在于，所述第二请求消息为会话建立请求消息时，所述第二请求消息用于建立所述第一终端设备与所述服务供应商和/或所述控制器之间的第二会话，所述第二会话用于传输所述第二终端设备与所述服务供应商和/或所述控制器之间的数据；或
    所述第二请求消息为会话修改请求消息时，所述第二请求消息用于请求将所述第一会话修改为用于进一步传输所述第二终端设备与所述服务供应商和/或所述控制器之间的数据的会话，在发送所述会话修改请求消息前，所述第一会话为所述第一终端设备建立的用于传输所述第一终端设备与所述服务供应商和/或所述控制器之间的数据的会话。
  23. 根据权利要求13至22中任一项所述的方法，其特征在于，所述控制器用于控制所述第二终端设备；所述服务供应商是第三方实体，用于为所述第一终端设备和所述第二终端设备提供服务。
  24. 一种中继通信的装置，其特征在于，包括用于执行权利要求1至12中任一项所述的方法的单元。
  25. 一种中继通信的装置，其特征在于，包括用于执行权利要求13至23中任一项所述的方法的单元。
  26. 一种计算机可读存储介质，其特征在于，包括计算机指令，当所述计算机指令在被处理器运行时，使得所述计算机执行如权利要求1至12中任一项所述的方法，或者使得所述计算机执行如权利要求13至23中任一项所述的方法。
  27. 一种芯片装置，其特征在于，包括处理电路，所述处理电路用于从存储器中调用 并运行程序，使得安装有该芯片装置的通信设备执行如权利要求1至12中任一项所述的方法，或者使得所述安装有该芯片装置的通信设备执行如权利要求13至23中任一项所述的方法。
PCT/CN2022/110802 2021-10-20 2022-08-08 中继通信的方法和装置 WO2023065778A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202111224378.6A CN115996437A (zh) 2021-10-20 2021-10-20 中继通信的方法和装置
CN202111224378.6 2021-10-20

Publications (1)

Publication Number Publication Date
WO2023065778A1 true WO2023065778A1 (zh) 2023-04-27

Family

ID=85989284

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/110802 WO2023065778A1 (zh) 2021-10-20 2022-08-08 中继通信的方法和装置

Country Status (2)

Country Link
CN (1) CN115996437A (zh)
WO (1) WO2023065778A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104469695A (zh) * 2013-09-12 2015-03-25 华为技术有限公司 网络接入方法、近距离通信服务器、中继终端及终端
CN106470382A (zh) * 2015-08-14 2017-03-01 中兴通讯股份有限公司 授权验证方法、配置信息接收方法、装置、基站及终端
CN109951827A (zh) * 2017-12-21 2019-06-28 上海诺基亚贝尔股份有限公司 用于设备到设备通信的方法、设备和计算机可读存储介质
CN109716810B (zh) * 2017-01-06 2020-08-25 华为技术有限公司 授权验证方法和装置
CN113132334A (zh) * 2019-12-31 2021-07-16 华为技术有限公司 授权结果的确定方法及装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104469695A (zh) * 2013-09-12 2015-03-25 华为技术有限公司 网络接入方法、近距离通信服务器、中继终端及终端
CN106470382A (zh) * 2015-08-14 2017-03-01 中兴通讯股份有限公司 授权验证方法、配置信息接收方法、装置、基站及终端
CN109716810B (zh) * 2017-01-06 2020-08-25 华为技术有限公司 授权验证方法和装置
CN109951827A (zh) * 2017-12-21 2019-06-28 上海诺基亚贝尔股份有限公司 用于设备到设备通信的方法、设备和计算机可读存储介质
CN113132334A (zh) * 2019-12-31 2021-07-16 华为技术有限公司 授权结果的确定方法及装置

Also Published As

Publication number Publication date
CN115996437A (zh) 2023-04-21

Similar Documents

Publication Publication Date Title
US20210400489A1 (en) 3gpp private lans
WO2021136211A1 (zh) 授权结果的确定方法及装置
EP4007326A1 (en) Method and device for activating 5g user
US20230087407A1 (en) Authentication and authorization method and apparatus
US20230371111A1 (en) Communication method, apparatus, and system
WO2021132093A1 (ja) Ａｍｆノード及びその方法
US20230284119A1 (en) Access to snpn by using credential owned by entity separated from snpn, and support for f1 interface therefor
WO2021132096A1 (ja) Ａｍｆノード及びその方法
WO2022199451A1 (zh) 会话切换的方法和装置
CN116723507B (zh) 针对边缘网络的终端安全方法及装置
WO2023065778A1 (zh) 中继通信的方法和装置
WO2022126329A1 (zh) 目标信息获取方法、发送方法、装置、设备及存储介质
CN114600487B (zh) 身份认证方法及通信装置
KR20210040776A (ko) 5g 사용자 활성화 방법 및 장치
WO2023054568A1 (ja) Ａｍｆノード、ｕａｖ、ｓｍｆノード、方法、及び非一時的なコンピュータ可読媒体
WO2023054198A1 (ja) 第１のノード、第２のノード、第１のノードによる方法、第２のノードよる方法、ｕｅ、及びｕｅによる方法
JP7131721B2 (ja) Ａｍｆノード及びその方法
WO2023160199A1 (zh) 一种接入通信网络的方法和装置
JP7428265B2 (ja) 通信端末及びその方法
WO2023065826A1 (zh) 一种通信方法及通信装置
WO2022027529A1 (zh) 一种切片认证的方法及装置
WO2022170798A1 (zh) 确定策略的方法和通信装置
WO2023072271A1 (zh) 管理安全上下文的方法和装置
WO2023202337A1 (zh) 通信方法和装置
WO2023213184A1 (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: 22882400

Country of ref document: EP

Kind code of ref document: A1