WO2022068336A1 - 路由信息更新方法、通信装置及存储介质 - Google Patents

路由信息更新方法、通信装置及存储介质 Download PDF

Info

Publication number
WO2022068336A1
WO2022068336A1 PCT/CN2021/108264 CN2021108264W WO2022068336A1 WO 2022068336 A1 WO2022068336 A1 WO 2022068336A1 CN 2021108264 W CN2021108264 W CN 2021108264W WO 2022068336 A1 WO2022068336 A1 WO 2022068336A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal
routing information
message
updated
relay
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2021/108264
Other languages
English (en)
French (fr)
Inventor
张博
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
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 Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to EP21873998.5A priority Critical patent/EP4207686A4/en
Publication of WO2022068336A1 publication Critical patent/WO2022068336A1/zh
Priority to US18/192,866 priority patent/US20230262579A1/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/24—Connectivity information management, e.g. connectivity discovery or connectivity update
    • H04W40/248—Connectivity information update
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/66—Layer 2 routing, e.g. in Ethernet based MAN's

Definitions

  • the embodiments of the present application relate to the field of communications, and in particular, to a routing information update method, a communication device, and a storage medium.
  • a terminal device eg, a mobile phone
  • a network network
  • another terminal device eg, a mobile phone
  • user equipment (user equipment, UE) 1 can communicate with the network through UE2, wherein UE2 plays the role of a relay (UE-to-network relay) from UE1 to the network, which can improve the coverage capability of the network to UE1.
  • UE1 can communicate with UE3 through UE2, wherein UE2 plays the role of a relay (UE-to-UE relay) from UE1 to UE3, which can increase the communication distance between UE1 and UE3.
  • the above-mentioned near-field service communication scenario may also be referred to as a relay scenario.
  • the relay scenario data transmission is performed between different UEs based on the IP address of the UE, but currently, it is not possible to implement the IP update of the UE for the relay scenario.
  • Embodiments of the present application provide a routing information updating method, a communication device, and a storage medium, which can implement updating of routing information of a terminal for a relay scenario.
  • an embodiment of the present application provides a method for updating routing information, the method includes: a second terminal generates routing information of the first terminal, and a relay function of the second terminal is based on the routing information of the first terminal for the first terminal.
  • Provide communication services with the first device where the first device includes a third terminal and/or a network device; the second terminal updates the routing information of the first terminal, and generates updated routing information of the first terminal;
  • a terminal sends a second message, where the second message includes updated routing information of the first terminal; when the first device includes a third terminal, the second terminal sends the updated routing information of the first terminal to the third terminal.
  • the second terminal may replace the stored routing information of the first terminal before updating with the updated routing information of the first terminal.
  • the first terminal may replace the routing information before the update of the first terminal with the updated routing information of the first terminal.
  • the first terminal may use the relay function of the second terminal to communicate with the first device based on the updated routing information of the first terminal.
  • the method can be applied to update the routing information of the UE in the relay scenario.
  • the second terminal plays the role of a relay and is used to provide communication services for the first terminal and the first device.
  • the second terminal may distribute the routing information of the first terminal to the first terminal, and update the routing information of the first terminal.
  • the first terminal may send a third message to the second terminal to notify the second terminal that it The replacement of routing information has been completed. That is, the third message may be used to indicate that the first terminal has replaced the routing information before the update of the first terminal with the updated routing information of the first terminal. Replacing the stored routing information of the first terminal before the update with the updated routing information of the first terminal by the second terminal may be performed after receiving the third message.
  • the second terminal updates the routing information of the first terminal, and after generating the updated routing information of the first terminal, the stored routing information of the first terminal before the update can be replaced with the first terminal.
  • the updated routing information of the terminal does not necessarily need to be performed after receiving the third message, and the present application does not limit the sequence of the second terminal performing the replacement process.
  • the method before the second terminal updates the routing information of the first terminal, the method further includes: the second terminal receives a first message from the first terminal, where the first message is used to indicate the first terminal The second terminal updates the routing information of the first terminal; and the second terminal updates the routing information of the first terminal, including: the second terminal updates the routing information of the first terminal according to the first message.
  • the above update process may be initiated by the first terminal.
  • the first terminal may send a first message to the second terminal to instruct the second terminal to update the routing information of the first terminal.
  • the routing information updating method may be implemented based on a process of updating the connection identifier of the first terminal.
  • the first message is a connection identification update request message
  • the second message is a connection identification update response message.
  • the first message includes the updated layer 2 identifier of the first terminal; the method further includes: the second terminal updates the layer 2 identifier of the second terminal to generate the updated layer 2 identifier of the second terminal; the second message Also includes the updated layer 2 identification of the second terminal.
  • the above-mentioned third message may be a connection identification update confirmation message.
  • the second message sent by the second terminal to the first terminal may further include the updated layer 2 identifier of the first terminal.
  • the first terminal may also determine that Whether the included updated layer 2 identifier of the first terminal is the same as the updated layer 2 identifier of the first terminal sent by itself in the first message, so as to realize verification to ensure the update accuracy. If the first terminal checks that the two are different, the first terminal may send a rejection message to the second terminal, and the subsequent steps are not performed. If it is the same, continue execution.
  • the first message may further include the routing information before the update of the first terminal, which can be used by the second terminal to determine the routing information before the first terminal, that is, the routing information before the update of the first terminal. routing information.
  • the routing information of the first terminal includes: first routing information and second routing information; the first routing information is routing information used when the first terminal communicates directly with the second terminal, and the second routing information is the routing information used when the first terminal communicates directly with the second terminal.
  • the information is the routing information used by the first terminal when using the relay function of the second terminal; the first message includes an update instruction, and the update instruction is used to instruct the second terminal to update the second routing information; the updated information of the first terminal
  • the routing information is the updated second routing information.
  • the first terminal may also send the first routing information generated by itself to the second terminal for direct communication between the first terminal and the second terminal.
  • the first message may further include the pre-update layer 2 identifier of the first terminal and the pre-update layer 2 identifier of the second terminal, which can be used by the second terminal to determine the identity of the first message. sender identity.
  • the second terminal determines which one of the aforementioned one or more first terminals sends the first message.
  • the method further includes: the second terminal generates updated routing information of the second terminal according to the first message; the second message further includes the updated routing information of the second terminal.
  • the method further includes: the second terminal sends the updated routing information of the first terminal to the network device.
  • the first message further includes identification information of the fourth terminal, and the fourth terminal includes the third terminal; the method further includes: the second terminal sends, according to the identification information of the fourth terminal, to the fourth terminal The updated routing information of the first terminal.
  • the first terminal can send the identification information of the fourth terminal to the first terminal by sending the first terminal to the first terminal. to instruct.
  • the first terminal may send the identification information of the fourth terminal to the second terminal through the foregoing first message.
  • on-demand updates are considered. Only the third terminal that needs to communicate with the first terminal can obtain the updated routing information of the first terminal, and the operation of additionally notifying each third terminal can be avoided.
  • the method further includes: the second terminal updates the routing information of the third terminal to generate updated routing information of the third terminal; the second terminal sends the third terminal and the first terminal to the third terminal The updated routing information of the third terminal.
  • updating the routing information of the third terminal by the second terminal includes: after the second terminal receives the first message from the first terminal, updating the routing information of the third terminal.
  • the routing information of the first terminal and the third terminal can be updated at the same time, which can prevent an attacker from determining the routing information before and after the update of the first terminal according to the same routing information of the third terminal.
  • the information belongs to the same first terminal.
  • the method further includes: the second terminal sends a first radio resource control RRC message to the network device, where the first RRC message includes a message that provides data transmission for the first terminal Identification information of the air interface, the first RRC message is used to instruct the network device to update the identification information; the second terminal receives the second RRC message from the network device, and the second RRC message includes the updated identification information.
  • This design can be applied to a scenario where there is an end-to-end protection mechanism between the first terminal and the network device.
  • the end-to-end parameters between the first terminal and the network device that can be used to identify the first terminal need to be updated.
  • an embodiment of the present application provides a communication device.
  • the device has the function of implementing the method described in the first aspect above.
  • the functions can be implemented by hardware, or by executing corresponding software by hardware.
  • the hardware or software includes one or more units or modules corresponding to the functions of the method described in the first aspect above, for example, a processing unit, a transceiver unit, and the like.
  • an embodiment of the present application further provides a communication apparatus, including: a processor configured to execute computer instructions stored in a memory, and when the computer instructions are executed, cause the apparatus to execute the first aspect or the first A method as described in any possible design of the aspect.
  • an embodiment of the present application further provides a communication device, including: a processor and an interface circuit, where the processor is configured to communicate with other devices through the interface circuit, and execute the first aspect or any possible design of the first aspect. method described.
  • the communication devices described in the second to fourth aspects above can be applied to a second terminal having a relay function.
  • the embodiments of the present application further provide a computer-readable storage medium, including: computer software instructions; when the computer software instructions are stored in an electronic device, such as a second terminal with a relay function, or built in the electronic device When running in the chip, the electronic device is caused to perform the method described in the first aspect or any possible design of the first aspect.
  • an embodiment of the present application provides a routing information update method, the method includes: a first terminal generates a first message, the first message is used to instruct the second terminal to update routing information of the first terminal; the first The terminal uses the routing information of the first terminal to communicate with the first device through the relay function of the second terminal, where the first device includes a third terminal and/or a network device; the first terminal sends a first message to the second terminal; the first terminal A second message from the second terminal is received, where the second message includes updated routing information of the first terminal; the first terminal replaces the routing information before the update of the first terminal with the updated routing information of the first terminal.
  • the first message is a connection identifier update request message
  • the second message is a connection identifier update response message
  • the method further includes: The layer 2 identifier of a terminal is updated to generate the updated layer 2 identifier of the first terminal; the first message includes the updated layer 2 identifier of the first terminal; the second message also includes the updated layer 2 identifier of the second terminal logo.
  • the routing information of the first terminal includes: first routing information and second routing information; the first routing information is routing information used when the first terminal communicates directly with the second terminal, and the first routing information is the routing information used when the first terminal communicates directly with the second terminal.
  • the second routing information is the routing information used by the first terminal when using the relay function of the second terminal; the first message includes an update instruction, and the update instruction is used to instruct the second terminal to update the second routing information; the update of the first terminal
  • the updated routing information is the updated second routing information.
  • the second message further includes updated routing information of the second terminal.
  • the first message further includes identification information of the fourth terminal, and the fourth terminal includes the third terminal.
  • the method further includes: the first terminal sends the updated routing information of the first terminal to the fourth terminal through the second terminal; the fourth terminal includes the third terminal.
  • the first terminal can transparently transmit the updated routing information of the first terminal to the third terminal through the second terminal.
  • the third terminal may actively initiate an update of the routing information of the third terminal to the second terminal.
  • the method further includes: the first terminal receiving the updated routing information of the third terminal from the second terminal.
  • the method described in the sixth aspect above corresponds to some steps in the method described in the first aspect, and is a step performed by the first terminal. Therefore, the same beneficial effects as those described in the first aspect are not described here. Repeat.
  • an embodiment of the present application provides a communication device.
  • the device has the function of implementing the method described in the sixth aspect.
  • the functions can be implemented by hardware, or by executing corresponding software by hardware.
  • the hardware or software includes one or more units or modules corresponding to the functions of the method described in the sixth aspect, for example, a processing unit, a transceiver unit, and the like.
  • an embodiment of the present application further provides a communication device, comprising: a processor configured to execute computer instructions stored in a memory, and when the computer instructions are executed, cause the device to execute the sixth aspect or the sixth aspect A method as described in any possible design of the aspect.
  • an embodiment of the present application further provides a communication device, including: a processor and an interface circuit, where the processor is configured to communicate with other devices through the interface circuit, and execute the sixth aspect or any possible design of the sixth aspect. method described.
  • the communication apparatus described in the seventh to ninth aspects above can be applied to having a first terminal, and the first terminal uses the routing information of the first terminal to communicate with the first device through the relay function of the second terminal.
  • the embodiments of the present application further provide a computer-readable storage medium, including: computer software instructions; when the computer software instructions run in an electronic device, such as the first terminal, or a chip built into the electronic device When , the electronic device is caused to perform the method described in the sixth aspect or any possible design of the sixth aspect.
  • an embodiment of the present application provides a method for updating routing information.
  • the method includes: a third terminal uses routing information of the third terminal to communicate with a first device through a relay function of the second terminal, and the first device includes: The first terminal and/or the network device; the third terminal receives the updated routing information of the first terminal from the second terminal; the third terminal sends to the second terminal a route for indicating the second terminal to the third terminal A message for updating information; the third terminal receives the updated routing information of the third terminal from the second terminal.
  • the updated routing information of the first terminal is transparently transmitted by the first terminal to the third terminal through the second terminal.
  • the third terminal may actively initiate an update of the routing information of the third terminal to the second terminal.
  • an embodiment of the present application provides a communication device.
  • the device has the function of implementing the method described in the eleventh aspect above.
  • the functions can be implemented by hardware, or by executing corresponding software by hardware.
  • the hardware or software includes one or more units or modules corresponding to the functions of the method described in the eleventh aspect above, for example, a processing unit, a transceiver unit, and the like.
  • an embodiment of the present application further provides a communication apparatus, including: a processor configured to execute computer instructions stored in a memory, and when the computer instructions are executed, cause the apparatus to perform the eleventh aspect or The method described in any possible design of the eleventh aspect.
  • an embodiment of the present application further provides a communication device, including: a processor and an interface circuit, where the processor is configured to communicate with other devices through the interface circuit, and executes the eleventh aspect or any possible possibility of the eleventh aspect. method described in the design.
  • the communication apparatus described in the twelfth aspect to the fourteenth aspect above may be applied to a third terminal.
  • the embodiments of the present application further provide a computer-readable storage medium, including: computer software instructions; when the computer software instructions run in an electronic device, such as a third terminal, or a chip built into the electronic device When , the electronic device is caused to execute the method described in the eleventh aspect or any possible design of the eleventh aspect.
  • an embodiment of the present application provides a method for updating routing information, the method includes: a network device communicates with a first terminal through a second terminal; the network device receives a first RRC message from the second terminal, the first RRC message The message includes identification information of the air interface that provides data transmission for the first terminal, and the first RRC message is used to instruct the network device to update the identification information; the network device, according to the first RRC message, updates the air interface that provides data transmission for the first terminal.
  • the identification information is updated to generate updated identification information; the network device sends a second RRC message to the second terminal, where the second RRC message includes the updated identification information.
  • This method can be applied to the scenario where there is an end-to-end protection mechanism between the first terminal using the relay function of the second terminal and the network device.
  • the end-to-end available protection mechanism between the first terminal and the network device needs to be updated. to identify the parameters of the first terminal. For example, the above-mentioned identification information of the air interface for data transmission is provided for the first terminal.
  • the network device receiving the first RRC message from the second terminal includes: the network device receiving the first RRC message sent by the second terminal after updating the routing information of the first terminal.
  • an embodiment of the present application provides a communication device.
  • the device has the function of implementing the method described in the sixteenth aspect.
  • the functions can be implemented by hardware, or by executing corresponding software by hardware.
  • the hardware or software includes one or more units or modules corresponding to the functions of the method described in the sixteenth aspect, for example, a processing unit, a transceiver unit, and the like.
  • an embodiment of the present application further provides a communication device, including: a processor configured to execute computer instructions stored in a memory, and when the computer instructions are executed, cause the device to execute the sixteenth aspect or The method described in any possible design of the sixteenth aspect.
  • an embodiment of the present application further provides a communication device, including: a processor and an interface circuit, where the processor is configured to communicate with other devices through the interface circuit, and executes the sixteenth aspect or any possible possibility of the sixteenth aspect. method described in the design.
  • the communication apparatuses described in the seventeenth to nineteenth aspects above can be applied to network equipment.
  • embodiments of the present application further provide a computer-readable storage medium, including: computer software instructions; when the computer software instructions are run in an electronic device, such as a network device, or a chip built into the electronic device , so that the electronic device performs the method described in the sixteenth aspect or any possible design of the sixteenth aspect.
  • an embodiment of the present application further provides a communication device, including: a transceiver unit and a processing unit.
  • the transceiver unit can be used to send and receive information, or to communicate with other network elements.
  • the processing unit may be used to process the data.
  • the apparatus may implement the method described in any one of the first aspect, the sixth aspect, the eleventh aspect, and the sixteenth aspect through the transceiver unit and the processing unit.
  • an embodiment of the present application further provides a computer program product, which, when executed, can implement any one of the first aspect, the sixth aspect, the eleventh aspect, and the sixteenth aspect the method described in the aspect.
  • an embodiment of the present application further provides a chip system, where the chip system is applied to an electronic device (eg, the above-mentioned first terminal, second terminal, third terminal, or network device).
  • the chip system includes one or more interface circuits and one or more processors; the interface circuit and the processor are interconnected by lines; the processor receives and executes computer instructions from the memory of the electronic device through the interface circuit, so as to realize the first aspect and the sixth aspect Aspects, and the method of any of the sixteenth aspects.
  • an embodiment of the present application further provides a communication system, where the communication system includes at least a first terminal, a second terminal, and a third terminal.
  • the first terminal is used to implement the method according to the sixth aspect
  • the second terminal is used to implement the method according to the first aspect.
  • the third terminal is configured to implement the method according to the eleventh aspect.
  • an embodiment of the present application further provides a communication system, where the communication system includes at least a first terminal, a second terminal, and a network device.
  • the first terminal is used to implement the method according to the sixth aspect
  • the second terminal is used to implement the method according to the first aspect.
  • a network device is used to implement the method as described in the sixteenth aspect.
  • Fig. 1 shows a kind of scene schematic diagram of short-range service communication
  • Fig. 2 shows the scene schematic diagram of another short-range service communication
  • FIG. 3 shows a schematic diagram of the composition of an electronic device provided by an embodiment of the present application
  • FIG. 4 shows a schematic flowchart of a method for updating routing information provided by an embodiment of the present application
  • Fig. 5 shows the schematic diagram of the connection identification when UE1 communicates with UE3 through relay
  • Fig. 6 shows the schematic diagram of the connection identification when UE1 communicates with gNB through relay
  • FIG. 7 shows another schematic flowchart of the routing information updating method provided by the embodiment of the present application.
  • FIG. 8 shows another schematic flowchart of the routing information updating method provided by the embodiment of the present application.
  • FIG. 9 shows another schematic flowchart of the routing information update method provided by the embodiment of the present application.
  • Figure 10 shows a schematic diagram of a dedicated connection
  • Figure 11 shows a schematic diagram of a shared connection
  • FIG. 12 shows another schematic flowchart of the routing information updating method provided by the embodiment of the present application.
  • FIG. 13 shows another schematic flowchart of the routing information update method provided by the embodiment of the present application.
  • FIG. 14 shows another schematic flowchart of the routing information updating method provided by the embodiment of the present application.
  • FIG. 15 shows a schematic structural diagram of a communication apparatus provided by an embodiment of the present application.
  • FIG. 16 shows another schematic structural diagram of a communication device provided by an embodiment of the present application.
  • FIG. 17 shows another schematic structural diagram of a communication apparatus provided by an embodiment of the present application.
  • the embodiments of the present application may be applicable to the scenario of short-range service communication.
  • Near Field Service Communication is also called Proximity Service Communication.
  • FIG. 1 shows a schematic diagram of a scenario of short-range service communication.
  • a near-field service communication scenario may include: user equipment (user equipment, UE) 1, UE2, and a network (network).
  • UE1 can be connected to UE2, and UE2 can be connected to a network (for example, UE2 can be connected to a network device used to access the network), so that UE1 can communicate with the network through UE2 to realize the communication between UE1 and the network. data transmission.
  • UE2 plays the role of a relay (UE-to-network relay) from UE1 to the network, which can improve the coverage capability of the network to UE1.
  • the interface between UE1 and UE2 is a PC5 interface, and the interface between UE2 and the network is a Uu interface.
  • FIG. 2 shows a schematic diagram of another short-range service communication scenario.
  • another scenario of short-range service communication may include: UE1, UE2, and UE3.
  • the UE1 can be connected with the UE2, and the UE2 can be connected with the UE3, so that the UE1 can communicate with the UE3 through the UE2, so as to realize the data transmission between the UE1 and the UE3.
  • UE2 plays the role of a relay (UE-to-UE relay) from UE1 to UE3, which can increase the communication distance between UE1 and UE3.
  • the interface between UE1 and UE2 is a PC5 interface, and the interface between UE2 and UE3 is also a PC5 interface.
  • the above-mentioned scenarios of short-range service communication shown in FIG. 1 and FIG. 2 may also be referred to as relay scenarios.
  • the relay scenario data transmission is performed between different UEs (eg, UE1 and UE2, or UE2 and UE3) based on the IP addresses of the UEs.
  • UEs eg, UE1 and UE2, or UE2 and UE3
  • IP addresses of the UEs eg.g, UE1 and UE2, or UE2 and UE3
  • an embodiment of the present application provides a routing information update method, which can be applied to update routing information of a UE in the above relay scenario.
  • the second terminal can generate routing information of the first terminal
  • the relay function of the second terminal can provide communication services for the first terminal and the first device based on the routing information of the first terminal
  • the first device includes the third terminal and/or network equipment.
  • the second terminal may update the routing information of the first terminal to generate an update of the first terminal After the routing information. Then, the second terminal may send the updated routing information of the first terminal to the first terminal through a message, which may be referred to as a second message.
  • the first terminal After receiving the updated routing information of the first terminal, the first terminal will replace the routing information before the update of the first terminal with the updated routing information of the first terminal.
  • the routing information implements communication with the first device through the relay function of the second terminal.
  • the second terminal when the first device includes the third terminal, the second terminal will also send the updated routing information of the first terminal to the third terminal, and the third terminal may replace the stored routing information of the first terminal before the update with The updated routing information of the first terminal is received, so that subsequent data transmission will be performed with the first terminal through the relay function of the second terminal according to the updated routing information of the first terminal.
  • the second terminal plays the role of a relay and is used to provide communication services for the first terminal and the first device.
  • the second terminal may distribute the routing information of the first terminal to the first terminal, and update the routing information of the first terminal.
  • the first terminal refers to UE1
  • the second terminal refers to UE2
  • the first device refers to a network device for accessing the network.
  • the first terminal refers to UE1
  • the second terminal refers to UE2
  • the first device refers to UE3.
  • the first terminal and the second terminal can directly establish a secure connection.
  • the first terminal is configured to be able to use the relay function of the second terminal.
  • the second terminal is configured to perform a relay function to send data of the first terminal to the first device.
  • the configuration information of the first terminal may be obtained from a network device or network element during the registration process, for example, a network device or network element.
  • Elements can include: policy control function (PCF), unified data management function (UDM), user data records (UDR), ProSe function entity (ProSe function), etc., which are not described here. limit.
  • PCF policy control function
  • UDM unified data management function
  • UDR user data records
  • ProSe function entity ProSe function
  • the specific configuration path can be as follows: PCF sends configuration information to access and mobility management function (AMF), and then AMF implements non-access stratum (NAS) message through AMF. sent to the first terminal.
  • AMF access and mobility management function
  • NAS non-access stratum
  • the configuration process of the second terminal or the third terminal included in the first device may be the same as the configuration process of the first terminal, which will not be repeated here.
  • the routing information may be IP routing, or layer-2 ID routing, or other non-IP routing, for example, MAC information, private network address, etc., here
  • IP routing or layer-2 ID routing, or other non-IP routing, for example, MAC information, private network address, etc.
  • the specific type of routing information is not limited, and the following description takes IP as an example.
  • the above-mentioned terminals such as the first terminal, the second terminal, and the third terminal may also be referred to as user equipment (User Equipment, UE), mobile station (mobile station, MS), mobile terminal (mobile terminal, MT), etc. .
  • the third terminal may also be referred to as a remote UE.
  • the terminal in the embodiments of this application, the terminal refers to any one of the first terminal, the second terminal, and the third terminal
  • the terminal may be a device that provides voice and/or data connectivity to the user, for example, it may be are mobile phones ("cellular" phones), cell phones, computers, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants, PDA), laptop computers, handheld communication devices, handheld computing devices, satellite wireless devices, wireless modem cards, TV set top boxes (STBs), customer premise equipment (CPEs), wearable devices (such as smart watches, smart bracelets, pedometers, etc.), in-vehicle devices (such as cars, bicycles, electric vehicles, airplanes, ships, trains, high-speed trains, etc.), virtual reality (VR) devices, augmented reality (augmented reality (AR) devices, wireless terminals in industrial control, smart home devices (eg, refrigerators, TVs, air conditioners, electricity meters, etc.), smart robots, workshop equipment, wireless devices in
  • the above-mentioned network device may also be referred to as an access network (access network, AN) device, for example, may be a radio access network (radio access network, RAN) device or a next-generation radio access network device.
  • the terminal can communicate with the AN device.
  • AN equipment can provide functional services such as wireless resource management, service quality management, data encryption and compression for terminals.
  • the AN device may be a next generation node B (gNB), an evolved node B (evolved Node B, eNB), a next generation evolved node B (ng-eNB), etc. Base stations that do not support security policies.
  • the AN device may also be a base station that supports a security policy, such as a 5G base station.
  • the AN device may also be a transmission reception point (TRP), a radio network controller (RNC), a base station controller (BSC), a base station Base transceiver station (BTS), home base station (eg, home evolved NodeB, or home Node B, HNB), base band unit (BBU), or wireless fidelity (Wifi) access point (access point, AP), centralized unit (central unit, CU), distributed unit (distributed unit, DU), centralized unit-control plane (central unit-control plane, CU-CP), centralized unit-user plane (central unit-user plane, CU-UP), etc.
  • TRP transmission reception point
  • RNC radio network controller
  • BSC base station controller
  • BTS base station Base transceiver station
  • home base station eg, home evolved NodeB, or home Node B, HNB
  • BBU base band unit
  • Wi wireless fidelity
  • FIG. 3 shows a schematic diagram of the composition of an electronic device provided by an embodiment of the present application.
  • the electronic device may be a first terminal, a second terminal, and a first device (a network device or a third terminal) in this embodiment of the present application.
  • the electronic device may include: at least one processor 31 , a memory 32 , a communication interface 33 , and a bus 34 .
  • the processor 31 is the control center of the terminal, and may be a processor or a general term for multiple processing elements.
  • the processor 31 may be a central processing unit (CPU), a specific integrated circuit (application specific integrated circuit, ASIC), or may be configured to implement one or more embodiments of the present application
  • An integrated circuit such as: one or more microprocessors (digital signal processor, DSP), or, one or more field programmable gate array (field programmable gate array, FPGA), etc.
  • the processor 31 can execute various functions of the electronic device by running or executing software programs stored in the memory 32 and calling data stored in the memory 32 .
  • the processor 31 may include one or more CPUs, such as CPU0 and CPU1 shown in FIG. 3 .
  • the electronic device may include multiple processors, such as the processor 31 and the processor 35 shown in FIG. 3 .
  • processors can be a single-core processor (single-CPU) or a multi-core processor (multi-CPU).
  • a processor herein may refer to one or more devices, circuits, and/or processing cores for processing data (eg, computer program instructions).
  • the memory 32 is used for storing software programs for executing the method steps performed by the terminal in the solution of the present application, and the execution is controlled by the processor 31 .
  • the memory 32 may be read-only memory (ROM) or other type of static storage device that can store static information and instructions, random access memory (RAM) or other type of static storage device that can store information and instructions It can also be an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disk storage, CD-ROM storage (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or capable of carrying or storing desired program code in the form of instructions or data structures and capable of being executed by a computer Access any other medium without limitation.
  • ROM read-only memory
  • RAM random access memory
  • EEPROM electrically erasable programmable read-only memory
  • CD-ROM compact disc read-only memory
  • CD-ROM storage including
  • the memory 32 may exist independently and is connected to the processor 31 through a bus 34 .
  • the memory 32 can also be integrated with the processor 31, which is not limited here.
  • Communication interface 33 using any transceiver-like device, is used to communicate with other devices or a communication network.
  • the communication interface 33 may be an Ethernet interface, a radio access network (RAN) interface, a wireless local area network (WLAN) interface, and the like.
  • the communication interface 33 may include a receiving unit to implement a receiving function, and a transmitting unit to implement a transmitting function.
  • the bus 34 may be an industry standard architecture (ISA) bus, a peripheral component interconnect (PCI) bus, or an extended industry standard architecture (EISA) bus or the like.
  • ISA industry standard architecture
  • PCI peripheral component interconnect
  • EISA extended industry standard architecture
  • the bus can be divided into address bus, data bus, control bus and so on. For ease of presentation, only one thick line is used in FIG. 3, but it does not mean that there is only one bus or one type of bus.
  • bus 34 is used in FIG. 3, it can be understood that the bus 34 can also be replaced by other forms of connection relationship, not limited to the bus itself
  • FIG. 4 shows a schematic flowchart of a method for updating routing information provided by an embodiment of the present application.
  • the routing information updating method may include S401-S406.
  • the first terminal sends a first message to the second terminal, where the first message is used to instruct the second terminal to update the routing information of the first terminal.
  • the above updating process may be initiated by the first terminal.
  • the first terminal may send a first message to the second terminal to instruct the second terminal to update the routing information of the first terminal.
  • the second terminal receives the first message from the first terminal.
  • the second terminal updates the routing information of the first terminal to generate updated routing information of the first terminal.
  • the second terminal may update the routing information of the first terminal according to the indication of the first message, and generate updated routing information of the first terminal.
  • the second terminal sends a second message to the first terminal, where the second message includes updated routing information of the first terminal.
  • the first terminal receives the second message from the second terminal.
  • the first terminal replaces the stored routing information of the first terminal before updating with the updated routing information of the first terminal.
  • the first terminal can subsequently use the relay function of the second terminal to communicate with the first device according to the updated routing information of the first terminal.
  • S405 The first terminal sends a third message to the second terminal, where the third message is used to indicate that the first terminal has replaced the routing information before the update of the first terminal with the updated routing information of the first terminal.
  • the third message may also indicate that the first terminal has received the updated routing information.
  • the second terminal receives the third message from the first terminal.
  • the first terminal may send a third message to the second terminal to notify the second terminal that it has completed the replacement of routing information .
  • the second terminal After receiving the third message, the second terminal also replaces the stored routing information of the first terminal before updating with the updated routing information of the first terminal. For example, S406 can be executed.
  • the second terminal replaces the stored routing information of the first terminal before the update with the updated routing information of the first terminal.
  • the relay function of the second terminal can subsequently provide a communication service for the first terminal and the first device according to the updated routing information of the first terminal.
  • S406 may also be completed after S402. That is, after the second terminal updates the routing information of the first terminal and generates the updated routing information of the first terminal, the stored routing information of the first terminal before the update can be replaced with the updated routing information of the first terminal. routing information. It is not necessary to perform the replacement process after receiving the third message, and the embodiment of the present application does not limit the sequence of the second terminal performing the replacement process.
  • the update process of the routing information shown in FIG. 4 may be implemented based on the process of updating the link identifier of the first terminal, and the first terminal may obtain the first terminal in the process of updating the link identifier.
  • FIG. 5 shows a schematic diagram of a connection identifier when UE1 communicates with UE3 through relay.
  • the identification related to the connection of the PC5 interface between UE1 and the relay may include: layer 2 identification (layer 2 ID), Key ID1, Key-session ID1.
  • the layer 2 identifier includes: UE1 layer 2 ID, relay layer 2 ID1, which are used to identify the layer 2 connection between UE1 and the relay.
  • Key ID1 used to identify the shared key Key between UE1 and relay.
  • Key-session ID1 used to identify the session key between UE1 and relay.
  • the IP of UE1 corresponding to UE1 layer 2 ID and relay layer 2 ID1 is UE1 IP
  • the IP of relay is relay IP1.
  • the identification related to the connection of the PC5 interface between the relay and the UE3 may include: layer 2 identification (layer 2 ID), Key ID2, Key-session ID2.
  • the layer 2 identifier includes: relay layer 2 ID2 and UE3 layer 2 ID, which are used to identify the layer 2 connection between the relay and UE3.
  • Key ID2 used to identify the shared key Key between relay and UE3.
  • Key-session ID2 used to identify the session key between relay and UE3.
  • the IP of UE3 corresponding to relay layer 2 ID2 and UE3 layer 2 ID is UE3 IP
  • the IP of relay is relay IP2.
  • relay layer 2 ID1 and relay layer 2 ID2 may be the same or different, and relay IP1 and relay IP2 may also be the same or different, which are not limited here.
  • FIG. 6 shows a schematic diagram of a connection identifier when UE1 communicates with gNB through relay.
  • the identification related to the connection of the PC5 interface between UE1 and the relay may include: layer 2 ID (layer 2 ID), Key ID1, Key- session ID1.
  • the layer 2 identifier includes: UE1 layer 2 ID, relay layer 2 ID1, which are used to identify the layer 2 connection between UE1 and the relay.
  • Key ID1 used to identify the shared key Key between UE1 and relay.
  • Key-session ID1 used to identify the session key between UE1 and relay.
  • the IP of UE1 corresponding to UE1 layer 2 ID and relay layer 2 ID1 is UE1 IP
  • the IP of relay is relay IP1.
  • the identifier related to the connection of the Uu interface between the relay and the gNB may be an identifier shared between the relay and the gNB, which is used to identify the wireless or wired connection between them.
  • it may include: C-RNTI, SRN, bearer identification (or called air interface identification), spectrum identification, session ID serving UE1, PDCP SQN, etc.
  • the bearer identification refers to identification information of a radio bearer (also called an air interface) that provides data transmission for the UE1.
  • the above-mentioned first message may be a link identifier update request (link identifier update request) message
  • the above-mentioned second message may be a link identifier update response (link identifier update response) message
  • the above-mentioned third message may be a link identifier update acknowledgement (link identifier update acknowledgement/ACK) message.
  • the first terminal is UE1
  • the second terminal is UE2 (hereinafter referred to as relay)
  • the third terminal is UE3
  • the routing information is IP.
  • the updated method is exemplified.
  • a secure connection is established between UE1 and relay, and between relay and UE3.
  • FIG. 7 shows another schematic flowchart of the routing information updating method provided by the embodiment of the present application.
  • the routing information updating method may include S701-S707.
  • connection identifier update request message includes: the updated layer 2 identifier (UE1 new layer-2 ID) of UE1.
  • the layer 2 identifier can be reselected to obtain the updated UE1. and then generates a connection identity update request message carrying the updated layer 2 identity of UE1.
  • connection identifier update request message may also include the MSB of Key-sess ID, the updated application identifier of UE1, and the like.
  • S702 UE1 sends a connection identifier update request message to the relay.
  • connection identifier update request message is used to instruct the relay to update the IP of the UE1.
  • the relay receives the connection identification update request message.
  • the relay generates an updated layer 2 identifier (relay new layer-2 ID) of the relay, and updates the IP of UE1 to generate an updated IP (new UE1 IP) of UE1.
  • the relay After the relay generates the updated layer 2 identifier of the relay, it will replace the pre-update layer 2 identifier of the relay with it.
  • connection identifier update response message includes: the updated layer 2 identifier of the relay and the updated IP of the UE1.
  • UE1 receives the connection identity update response message.
  • the connection identifier update response message sent by the relay to UE1 may further include the updated layer 2 identifier of UE1.
  • UE1 may also determine the connection identifier update response message. Whether the updated layer 2 identifier of UE1 is the same as the updated layer 2 identifier of UE1 sent by itself in the connection identifier update request message is verified, so as to ensure the update accuracy. If the UE1 checks that the two are different, the UE1 can send a reject message to the relay, and the following steps are not performed. If it is the same, continue execution.
  • connection identifier update response message may also include the LSB of Key-sess ID, the updated application identifier of UE2, and the like.
  • UE1 replaces the locally stored relay's pre-update layer-2 identifier (relay old layer-2 ID) with the relay's post-update layer-2 identifier, and replaces the pre-update IP (old UE1 IP) of UE1 with the update of UE1 after the IP.
  • S706 UE1 sends a connection identifier update confirmation message to the relay.
  • connection identifier update confirmation message is used to indicate that the UE1 has replaced the locally stored pre-update IP of the UE1 with the updated IP of the UE1, or that the UE1 has received the updated IP of the UE1.
  • connection identifier update confirmation message sent by the UE1 to the relay may further include the updated IP of the UE1.
  • the relay After the relay receives the connection identity update confirmation message, it can also determine whether the updated IP of UE1 included in the connection identity update confirmation message is the same as the updated IP of UE1 sent by itself in the connection identity update response message, so as to realize further Check to ensure the update accuracy. If the relay checks that the two are different, the relay may send a reject message to UE1, and the following steps are not performed. If it is the same, continue execution.
  • connection identifier update confirmation message sent by the UE1 to the relay may further include the updated layer 2 identifier of the relay.
  • the relay After the relay receives the connection identifier update confirmation message, it can also determine whether the updated layer 2 identifier of the relay included in the connection identifier update confirmation message is the same as the updated layer 2 identifier of the relay sent by itself in the connection identifier update response message , so as to achieve further verification to ensure the accuracy of the update. If the relay checks that the two are different, the relay may send a reject message to UE1, and the following steps are not performed. If it is the same, continue execution.
  • the relay replaces the locally stored layer 2 identifier (UE1 old layer-2 ID) of the UE1 before the update with the updated layer 2 identifier of the UE1, and replaces the IP before the update of the UE1 with the updated IP of the UE1.
  • UE1 old layer-2 ID the locally stored layer 2 identifier
  • the above process shown in FIG. 7 completes the sharing of the updated layer 2 identity between the UE1 and the UE2, and the updating of the IP of the UE1. Subsequently, the relay will save the correspondence between the updated layer 2 identifier of the UE1 and the updated IP of the UE1, and provide communication services for the UE1 and other devices (eg, UE3) according to the correspondence.
  • the relay will save the correspondence between the updated layer 2 identifier of the UE1 and the updated IP of the UE1, and provide communication services for the UE1 and other devices (eg, UE3) according to the correspondence.
  • the relay replaces the locally stored UE1's pre-update layer-2 ID (UE1 old layer-2 ID) with the UE1's updated layer-2 ID, which may occur when the relay generates the updated layer-2 ID of UE1.
  • Any subsequent steps are not limited. For example, it is executed in S707, or executed after S703.
  • the action of the relay replacing the locally stored pre-update IP of the UE1 with the updated IP of the UE1 may occur at any step after the relay generates the updated IP of the UE1, without limitation. For example, it is executed in S707, or executed after S703.
  • the above Key-session ID can be replaced with a Key ID, that is, the update of the Key ID is performed.
  • the relay may also replace the IP before the update of the UE1 in the context of the UE1 with the IP after the update of the UE1.
  • the connection identifier update request message sent by UE1 to the relay may further include the IP of UE1 before updating, which may be used by the relay to determine the previous IP address of UE1.
  • the IP of the UE1 includes: a first IP and a second IP; the first IP is the IP used when the UE1 communicates directly with the relay, and the second IP is the IP used when the UE1 uses the relay function of the relay.
  • the second IP is an IP issued by the relay for the UE1
  • the first IP is an IP generated by the UE itself.
  • the connection identifier update request message sent by the UE1 to the relay may further include an update indication, which may be used to instruct the relay to update the second IP.
  • the relay may update the second IP according to the update instruction.
  • the updated IP of the UE1 included in the connection identity update response message sent by the relay to the UE1 refers to the updated second IP.
  • the UE1 may also send the first IP generated by itself to the relay for direct communication between the UE1 and the relay.
  • the connection identifier update request message sent by UE1 to the relay may further include the layer 2 identifier before the update of UE1 and the layer 2 identifier before the update of the relay, which can be used by the relay to determine the connection identifier update request The sender identity of the message. For example, when one or more UE1 uses the relay function of the relay, the relay can determine the above-mentioned layer 2 identifier of the UE1 before the update and the layer 2 identifier before the update of the relay included in the connection identifier update request message. Which of the one or more UE1 sent the connection identity update request message.
  • the relay may further update the IP of the relay after receiving the first message, and send the updated IP of the relay to the UE1.
  • the above-mentioned connection identifier update response message may further include the updated IP (new relay IP) of the relay.
  • UE1 may replace the locally stored pre-update IP (old relay IP) of the relay with the received updated IP of the relay.
  • UE1 sends the updated IP of the relay to the relay through S706, so that the relay checks whether the updated IP of the relay sent in step S704 is the same as the updated IP of the relay in step S706, thereby realizing further calibration. to ensure the accuracy of the update. If the relay checks that the two are different, the relay may send a reject message to UE1, and the following steps are not performed. If it is the same, continue execution.
  • FIG. 7 mainly illustrates how the UE1 triggers to update the connection between the UE1 and the relay.
  • the connection update between UE1 and the relay may also be actively triggered by the relay.
  • the step of S701 may be omitted, and the update is directly triggered by the relay (for the specific trigger reason, please refer to the description of the triggering by UE1 above), the updated IP of UE1 is generated, and sent to UE1 .
  • the specific principle is similar to that in FIG. 7 and will not be repeated here.
  • FIG. 7 may be applicable to the foregoing scenario shown in FIG. 1 , and may also be applicable to the foregoing scenario shown in FIG. 2 .
  • the routing information method further includes the step of notifying UE3 of the updated IP of UE1 on the basis of FIG. 7 .
  • FIG. 8 shows another schematic flowchart of the routing information updating method provided by the embodiment of the present application. As shown in FIG. 8 , the routing information updating method may further include S801-S802 on the basis of the aforementioned FIG. 7 .
  • the relay sends the updated IP of the UE1 to the UE3.
  • S801 shown in FIG. 8 is after S707, in fact, S801 can be executed at any time after S703, such as: it can be executed after S704, or at the same time as S704, etc. limit.
  • Executing after S706 can ensure that UE1 has correctly received the updated IP of UE1 before triggering execution of S801. It can be further explained that the relay can ensure that the UE1 will use the updated IP of the UE1 in the future, and then notify other terminals, such as the UE3.
  • the relay will send the IP before the update of the UE1, which is used by the UE3 to determine the IP information of which terminal needs to be updated.
  • UE3 replaces the locally stored IP of UE1 before updating with the updated IP of UE1.
  • the UE3 after the UE3 replaces the locally stored IP of UE1 before updating with the updated IP of UE1, it can also send an acknowledgement message to the relay to notify the relay that it has completed the replacement, or has received the updated IP of UE1. IP.
  • UE3 determines UE1 information according to the IP before updating of UE1, and then performs replacement.
  • UE3 sends the updated IP of UE1 to the relay.
  • the relay can also determine whether the updated IP of UE1 in S801 is the same as the updated IP of UE1 sent in S802, so as to realize further verification to ensure the update accuracy. If the relay checks that the two are different, the relay may send a reject message to UE1, and the following steps are not performed. If it is the same, continue execution.
  • UE3 will send data to UE1 according to the updated IP of UE1.
  • the relay may send the updated IP of UE1 to target UE3 according to the identification information of target UE3.
  • the target UE3 refers to the UE3 among the multiple UE3s that communicate with the UE1 through relay.
  • the UE1 may indicate by sending the identification information of the target UE3 to the relay.
  • the UE1 may send the identification information of the target UE3 to the relay through the aforementioned connection identification update request message.
  • the identification information of the target UE3 may include: the IP of the target UE3, the application identification of the target UE3, the layer 2 identification of the target UE3, etc., which are not limited herein.
  • the target UE3 may be UE3 with which UE1 wishes to communicate.
  • the relay may also send the updated IP of UE1 to the target UE3 according to the identification information of the target UE3 stored locally according to the identification information of the target UE3 that has historical communication with the UE1.
  • the relay can determine the connection between UE1 and the relay according to the identifier (such as the UE1 layer-2 ID, old UE1 IP, etc.) that identifies the connection in the connection identifier update request message sent by UE1, and then determine the connection between the corresponding relay and UE3 and the identification information of the target UE3, so as to determine to send the updated IP of the UE1 to the corresponding UE3.
  • the identifier such as the UE1 layer-2 ID, old UE1 IP, etc.
  • the routing information method is shown in FIG. 7 above.
  • the step of notifying the updated IP of the UE1 to the network device may also be included, which is similar to FIG. 8 and will not be repeated.
  • the routing information method does not include the step of notifying the network device of the updated IP of the UE1.
  • FIG. 9 shows another schematic flowchart of the routing information updating method provided by the embodiment of the present application. As shown in FIG. 9 , the routing information update method may further include S901-S902 on the basis of the aforementioned FIG. 7 .
  • UE1 sends the updated IP of UE1 to UE3 through relay.
  • the UE1 may transparently transmit the updated IP of the UE1 to the target UE3 that wishes to communicate with the UE1 through a relay.
  • the updated IP of UE1 may be transparently transmitted to all UE3 in historical communication.
  • UE1 sends a message to UE3 through relay, and UE1 and UE3 communicate directly with each other logically.
  • the relay is the proxy, which directly routes the data sent by UE1 to UE3. It can also be understood that the relay will not modify the content.
  • S901 shown in FIG. 9 is after S707, in fact, S901 can be executed at any time after UE1 receives the connection identification update response message, such as: can be executed simultaneously with S705, which is not performed here. limit. That is, it can be understood that after the UE1 determines to receive the updated IP of the UE1 distributed by the relay, it triggers the execution of S901 to send the updated IP of the UE1 to the UE3.
  • S901 carries the pre-update IP information of UE1. Used to identify the identity of the sender UE1.
  • UE3 replaces the locally stored IP of UE1 before updating with the updated IP of UE1.
  • the UE3 after the UE3 replaces the locally stored IP before the update of UE1 with the updated IP of UE1, it can also send a confirmation message to the relay and/or UE1 to notify the relay and/or UE1 that it has completed the replacement. , or the updated IP of UE1 has been received.
  • the UE3 determines to replace the locally stored IP before the update of the UE1 with the updated IP of the UE1 carried in S901 according to the IP information before the UE1 carried in the step S901.
  • the S901 message supports the use of an integrity protection mechanism. It can be an end-to-end integrity protection mechanism based on a shared key between UE1 and UE3. Currently, the replacement action is performed only when the UE3 uses the shared secret key between it and the UE1 to verify that the integrity protection of S901 is passed.
  • the S901 message supports the use of an integrity protection mechanism. It can be a fragmented integrity protection mechanism based on the shared key between UE1 and the relay, and the shared key between the relay and UE3. Currently, the replacement action is performed only after the UE3 uses the shared secret key between it and the relay to verify that the received S901 integrity protection is passed.
  • on-demand updates are also considered. Only the UE3 that needs to communicate with the UE1 can obtain the updated IP of the UE1, which can avoid the operation of additionally notifying each UE3.
  • the above embodiment mainly describes the method for updating the IP and connection identifier of the UE1.
  • the connection ID between UE1 and relay is updated, but the ID between relay and UE3 is not changed, then it is assumed that the connection between relay and UE3 is designed for UE1 to transmit data to UE3. Then, through the unchanged connection identifier between the relay and the UE3, the old and new identifiers between the UE1 and the relay are associated, such as the updated layer 2 identifier of the UE1.
  • the old data packet of UE1 is: the old identifier of UE1
  • the routing information updating method provided by the embodiment of the present application may further include a step of updating the routing information of the UE3 and the connection identifier between the UE3 and the relay on the basis of the foregoing embodiments. It can be applied to the scenario where the connection between the relay and UE3 is designed for UE1 to transmit data to UE3 (that is, the connection between the relay and UE3 is a dedicated connection), and it can also be applied to the scenario where the connection between the relay and UE3 is a shared connection , the specific applicable scenarios are not limited.
  • Figure 10 shows a schematic diagram of a dedicated connection.
  • the connection between UE1 and the relay is 1, the connection between UE4 and the relay is 3, and the connection between the relay and UE3 is 2 and 4.
  • 1 is bound to 2
  • 3 is bound to 4. That is, 2 is dedicated to 1 and 4 is dedicated to 3.
  • 2 must also be updated.
  • Figure 11 shows a schematic diagram of a shared connection.
  • the connection between UE1 and the relay is 1, the connection between UE4 and the relay is 3, and the connection between the relay and UE3 is 2.
  • 2 may serve 1 or serve 3, that is, the connection 2 between relay and UE3 is shared. Then when the connection 1 between UE1 and the relay is updated, 2 can be updated or not.
  • FIG. 12 shows another schematic flowchart of the routing information updating method provided by the embodiment of the present application.
  • the routing information updating method may further include S1201-S1206 on the basis of any one of the aforementioned FIG. 7-FIG. 9 (taking FIG. 7 as an example).
  • the update process of the IP of the UE3 may also be implemented in the update process of the connection identifier between the UE3 and the relay.
  • the relay triggers and executes the update of the connection between the relay and the UE3, generates the updated layer 2 identifier (relay new layer-2 ID) of the relay, and updates the IP of the UE3 to generate the updated IP of the UE3 (new UE3 IP).
  • the updated layer 2 identifier of the relay described in S1201 and the updated layer 2 identifier of the relay described in the embodiment shown in FIG. 7 may be the same or different, which is not limited.
  • the relay triggers the execution of the update of the connection between the relay and the UE3, and the relay may execute the relay after determining that the UE1 has completed the update according to the first message or the update indication in the first message, or according to the ACK message sent by the UE1.
  • the relay may determine whether to perform an update according to whether the connection between the relay and the UE3 is a dedicated connection or a public connection. If it is a dedicated connection, the update process of S1201 is triggered to be executed. If it is a public connection, there is no need to trigger and execute the update process of S1201.
  • connection identifier update request message includes: the updated layer 2 identifier of the relay and the updated IP of the UE3.
  • connection identity update request message receives the connection identity update request message.
  • connection identifier update request message here is different from the connection identifier update request message sent by the UE1 to the relay described in the foregoing embodiment.
  • UE3 generates an updated layer 2 identifier of UE3.
  • connection identifier update response message includes: the updated layer 2 identifier of UE3.
  • the relay receives the connection identification update response message.
  • the connection identifier update request message here is different from the connection identifier update request message sent by the relay to the UE1 described in the foregoing embodiment.
  • the relay replaces the locally stored pre-update layer 2 identifier of UE3 with the updated layer 2 identifier of UE3.
  • the connection identifier update response message sent by the UE3 to the relay may further include the updated layer 2 identifier of the relay and/or the updated IP of the UE3.
  • the relay After the relay receives the connection identifier update response message, it can also Determine the updated layer 2 identity of the relay and/or the updated IP of UE3 included in the connection identity update response message and the updated layer 2 identity of the relay sent by itself in the connection identity update request message and/or the updated layer 2 identity of UE3. Check whether the updated IP is the same, so as to realize the verification to ensure the update accuracy. If the relay checks that the two are different, the relay may send a rejection message to UE3, and the following steps are not performed. If it is the same, continue execution.
  • the relay sends a connection identifier update confirmation message to UE3.
  • connection identity update confirmation message here is different from the connection identity update confirmation message sent by the UE1 to the relay described in the foregoing embodiment.
  • connection identity update confirmation message sent by the relay to UE3 may further include the updated layer 2 identity of UE3, and after receiving the connection identity update confirmation message, UE3 may also determine the connection identity update confirmation message. Whether the updated layer 2 identifier of UE3 is the same as the updated layer 2 identifier of UE3 sent by itself in the connection identifier update response message is verified, so as to ensure the update accuracy. If UE3 checks and finds that the two are different, UE3 may send a reject message to the relay, and the following steps are not performed. If it is the same, continue execution.
  • UE3 replaces the locally stored layer 2 identifier of the relay before updating with the updated layer 2 identifier of the relay, and replaces the pre-update IP of UE3 with the updated IP of UE3.
  • S1206 may also be executed at any other time after S1202, and is not limited to after S1205.
  • the relay may further include a step of notifying UE1 of the updated IP of UE3, so as to notify UE1 of the latest IP address of UE3.
  • the step of sending the updated IP to UE1 may be triggered after S1204.
  • the relay checks S1204 that the integrity protection is successful, it is sent to UE1.
  • UE1 may replace the pre-update IP of UE3 with the updated IP of UE3. This step is similar to the step of relay notifying UE1 of the updated IP of UE1 to UE3 shown in the above-mentioned FIG. 8 or FIG. 9 , or the manner in which UE1 transparently transmits the updated IP of UE1 to UE3 through the relay, which is not repeated here. Repeat.
  • the process of updating the IP of UE3 and the connection identifier between UE3 and the relay is triggered by updating the IP of UE1 and the connection identifier between UE1 and the relay.
  • the steps described in the above Figure 12 are executed after the relay receives the connection identity update request message from UE1, and it does not specifically limit which step to start executing after, and the foregoing illustrations are only examples. Sexual description.
  • UE1 may notify the relay The identification information of the target UE3 is sent, and the relay may send a connection identification update request message to the target UE3 according to the identification information of the target UE3.
  • the target UE3 refers to the UE3 among the multiple UE3s that communicate with the UE1 through relay.
  • the UE1 may indicate by sending the identification information of the target UE3 to the relay.
  • the UE1 may send the identification information of the target UE3 to the relay through the aforementioned connection identification update request message.
  • specific identification information of the target UE3 reference may be made to the foregoing embodiments.
  • on-demand updates are also considered. Only the UE3 that needs to communicate with the UE1 can obtain the updated IP of the UE1, which can avoid the operation of additionally notifying each UE3.
  • the relay may also send a connection identifier update request message to the target UE3 according to the locally stored target UE3 that has historical communication with the UE1.
  • the connection between the relay and the UE3 and the connection between the UE1 and the relay are mapped.
  • the relay can determine the connection between UE1 and the relay according to the identifier (such as the UE1 layer-2 ID, old UE1 IP, etc.) that identifies the connection in the connection identifier update request message sent by UE1, and then determine the connection between the corresponding relay and UE3 connection, so as to determine to send a connection identification update request message to the corresponding UE3.
  • the identifier such as the UE1 layer-2 ID, old UE1 IP, etc.
  • the relay may determine whether to execute it according to the protection mode of the PC5 interface between it and the UE1. For example, if encryption protection is not enabled for data protection between the relay and UE1, the subsequent update operation may need to be triggered according to the embodiment shown in FIG. 12 . If encryption protection is enabled, the attacker cannot see the parameters (for example, IP) of the end-to-end data between UE1 and UE3 through the PC5 port. The association between old and new identifiers between relays. At this time, the relay does not need to trigger subsequent update operations. Of course, if encryption protection is enabled, the relay can also determine whether to trigger subsequent updates according to other local policies, which is not limited here.
  • FIG. 12 mainly illustrates how the relay triggers the connection update between the relay and the UE3 in the case of the connection update between the UE1 and the relay.
  • the connection update between the relay and UE3 may also be initiated by UE3.
  • UE3 can actively send a trigger request message for connection update to the relay for subsequent update.
  • FIG. 13 shows another schematic flowchart of the routing information updating method provided by the embodiment of the present application.
  • the routing information update method may further include S1301-S1307 on the basis of the aforementioned FIG. 9 .
  • UE3 sends a fourth message to the relay, where the fourth message is used to instruct the relay to update the IP of UE3.
  • the relay receives the fourth message.
  • connection between the UE3 and the relay is triggered to perform the update, and the process of triggering the update here can refer to the action triggered by the relay above.
  • the relay generates an updated layer 2 identifier of the relay, and updates the IP of the UE3 to generate the updated IP of the UE3.
  • connection identifier update request message includes: the updated layer 2 identifier of the relay and the updated IP of the UE3.
  • UE3 generates an updated layer 2 identifier of UE3.
  • connection identifier update response message includes: the updated layer 2 identifier of UE3.
  • the relay will replace the locally stored pre-update layer 2 identifier of UE3 with the updated layer 2 identifier of UE3.
  • the relay sends a connection identifier update confirmation message to UE3.
  • the UE3 replaces the locally stored layer 2 identifier of the relay before the update with the updated layer 2 identifier of the relay, and replaces the pre-update IP of the UE3 with the updated IP of the UE3.
  • the UE3 may directly generate the updated layer 2 identifier of the UE3, and in S1301, the updated layer 2 identifier of the UE3 may be sent to the relay to trigger the execution of the update.
  • the steps are similar to S701-706, and the UE3 directly triggers the execution of the update at this time.
  • the step of notifying UE1 of the updated IP of UE3 is also included, so as to notify UE1 of the latest IP address of UE3.
  • UE1 may be notified for UE3, or UE1 may be notified by relay; there is no limitation.
  • UE1 may replace the pre-update IP of UE3 with the updated IP of UE3.
  • This step is also similar to the above-mentioned step of relay notifying UE1 of the updated IP of UE1 to UE3 shown in FIG. 8 or FIG. 9 , or the method of UE1 transparently transmitting the updated IP of UE1 to UE3 through the relay. No longer.
  • the routing information method on the basis of the above-mentioned FIG. Provide the step of updating the identification information of the air interface for data transmission.
  • the end-to-end protection mechanism between the UE1 and the gNB
  • the end-to-end parameters between the UE1 and the gNB that can be used to identify the UE1 need to be updated.
  • FIG. 14 shows another schematic flowchart of the routing information updating method provided by the embodiment of the present application.
  • the routing information update method may further include S1401-S1403 on the basis of the aforementioned FIG. 7 .
  • the relay sends a first radio resource control (radio resource control, RRC) message to the gNB, where the first RRC message includes identification information of an air interface that provides data transmission for UE1, and the first RRC message is used to instruct the gNB to update the identification information.
  • RRC radio resource control
  • the gNB receives the first RRC message.
  • the relay may determine an air interface (also called a radio bearer) that provides data transmission for UE1 according to the UE1 IP or UE1 layer-2 ID sent by UE1, to generate the first RRC message.
  • an air interface also called a radio bearer
  • the first RRC message is a message sent by the relay after updating the IP of the UE1.
  • the steps shown in FIG. 14 are performed after the steps shown in FIG. 7 .
  • the relay triggers the execution of the update of S1401 after determining that the UE1 completes the IP update of the UE1 successfully.
  • the first RRC message may also carry an update indication, which is used to instruct the gNB to update the identification information of the air interface that provides data transmission for the first terminal.
  • the first RRC message may also be another special message type that can be used to instruct the gNB to update the identification information of the air interface providing data transmission for the first terminal, which is not limited herein.
  • the gNB updates the identification information of the air interface that provides data transmission for the first terminal according to the first RRC message, and generates updated identification information.
  • the gNB may determine, according to the update indication or the message type carried in the first RRC message, to perform the update of the identity information of the air interface.
  • the updated identification information may include: a new cell access radio network temporary identifier (C-RNTI), a new RRC Counter, a new air interface (or bearer) identification, a new spectrum identification, The new packet data convergence protocol (PDCP) sequence number (sequence number, SQN) or counter (can start from 0, or randomly selected), new other IDs that identify this air interface, etc., are not made here. limit.
  • C-RNTI new cell access radio network temporary identifier
  • RRC Counter a new air interface (or bearer) identification
  • SQN packet data convergence protocol
  • counter can start from 0, or randomly selected
  • the gNB sends a second RRC message to the relay, where the second RRC message includes the updated identification information.
  • the relay receives the second RRC message.
  • the second RRC message may also be referred to as an RRC reconfiguration message.
  • the relay may select a corresponding air interface providing data transmission for the first terminal according to the updated identification information, and transmit the data of the UE1 to the gNB.
  • the relay will replace the locally stored identification information before the update of the air interface providing data transmission for the first terminal with the updated identification information, which will not be repeated.
  • the relay can also return a response message or a confirmation message to the gNB to notify the gNB that it has completed the replacement.
  • the relay may also send the updated identification information included in the second RRC message to the UE1, and the UE1 may refresh the parameters between the UE1 and the gNB according to the updated identification information. For example, use a new PDCP SQN or counter to replace the existing PDCP SQN or counter, or use a new bearer identifier to replace the old bearer identifier, etc. Other replacement operations will not be described in detail.
  • the bearer identifier may be a parameter used to perform PDCP layer protection.
  • the embodiment shown in FIG. 14 can trigger the update of the air interface Uu radio identity, so as to prevent an attacker from associating the old and new identity between the UE and the relay according to the existing radio bearer identity between the relay and the network device.
  • the relay may also determine whether to execute it according to the protection mode of the PC5 interface between it and the UE1. For example, if encryption protection is not enabled for data protection between relay and UE1, follow-up update operations can be triggered according to the embodiment shown in Figure 14; if encryption protection is enabled, attackers cannot see the connection between UE1 and gNB through PC5 port. parameters (for example, PDCP SQN or counter, air interface identifier, etc.), then the association between the old and new identifiers between UE1 and the relay cannot be completed according to the exposed parameters between UE1 and gNB. At this time, the relay can There is no need to trigger subsequent update operations. Of course, if encryption protection is enabled, the relay can also determine whether to trigger subsequent updates according to other local policies, which is not limited here.
  • the protection performed is an end-to-end protection mechanism between the UE and the gNB (taking PDCP protection as an example for description). Then, at this time, the updated parameters used for end-to-end protection need to be notified to UE1 (taking PDCP as an example, it can be a bearer identifier here).
  • the relay side triggers the update process, that is, steps S701-S707 are not included.
  • the update of the air interface is directly triggered by the relay. You can refer to the content of S1401.
  • the relay triggers and executes the update of the air interface identification according to local policies, etc., sends the bearer identification before the update to the gNB, and obtains the updated bearer identification from the gNB (optional, can be used RRC reconfiguration message).
  • the relay needs to determine the corresponding UE1 according to the bearer identification before the update, and send the updated bearer identification to the UE1.
  • the relay when UE1 uses the relay function, after sending data to the relay, the relay will use the air interface bearer corresponding to the bearer identification to transmit the data of UE1 to the base station. Therefore, the relay needs to send the updated bearer identity to UE1. At this time, the updated bearer identity can be shared between the UE1 and the gNB. Then UE1 and gNB use the updated bearer identity to perform end-to-end PDCP layer protection between UE1 and gNB.
  • the gNB side triggers the update process, that is, steps S701-S707 and S1401 are not included.
  • the update of the air interface is directly triggered by the gNB, and the gNB triggers the update of the air interface identity according to local policies, etc., and sends the updated bearer identity to the relay (optionally, an RRC reconfiguration message can be used; bearer ID).
  • the relay receives the updated bearer identifier (optionally, there is also the bearer identifier before the update).
  • the Relay can determine the bearer identifier before the update according to the bearer identifier after the update (for example, when there is only one bearer, or determine the bearer identifier before the update according to other parameters (such as session identifier, etc. without limitation)), or the Relay can determine the bearer identifier before the update according to the received bearer identifier.
  • the bearer identity before the update determines the corresponding UE1, and sends the updated bearer identity to the UE1.
  • the updated bearer identity can be shared between the UE1 and the gNB.
  • UE1 and gNB use the updated bearer identity to perform end-to-end PDCP layer protection between UE1 and gNB.
  • the process of triggering the update of the bearer identity when the gNB is handed over does not include steps S701-S707 and S1401.
  • the source gNB triggers a handover between gNBs according to the local policy, the source gNB switches to the target gNB, and receives the updated bearer identity from the target gNB.
  • the source gNB sends the updated bearer identification to the relay (optionally, an RRC reconfiguration message may be used; optionally, the pre-updated bearer identification may also be sent).
  • the relay receives the updated bearer identifier (optionally, there is also the bearer identifier before the update).
  • the Relay can determine the bearer identifier before the update according to the bearer identifier after the update (for example, when there is only one bearer, or determine the bearer identifier before the update according to other parameters (such as session identifier, etc. without limitation)), or the Relay can determine the bearer identifier before the update according to the received bearer identifier.
  • the bearer identity before the update determines the corresponding UE1, and sends the updated bearer identity to the UE1.
  • the updated bearer identity can be shared between the UE1 and the gNB.
  • UE1 and gNB use the updated bearer identity to perform end-to-end PDCP layer protection between UE1 and gNB.
  • the content related to the layer 2 identifier in the foregoing embodiments of the present application may be optional content, that is, the above-mentioned processes of generating, sending and verifying may only include processing of routing information.
  • optional integrity protection is performed on each message in the foregoing embodiments of the present application.
  • the sender such as UE1
  • the receiver such as relay
  • the sender will use the key shared with the receiver (such as relay) to perform integrity protection; after the receiver receives the message, it will use the key shared with the sender to perform integrity protection. check. After the verification is passed, subsequent operations will be performed. If the verification fails, a rejection message is sent to the sender.
  • the sender such as UE1
  • the content of S901 is directly sent to UE3, so logically the sender and receiver are UE1 and UE3.
  • the protection key of S901 is shared between UE1 and UE3.
  • the update of IP is only an exemplary description, and the routing information update method provided by the embodiments of the present application is also applicable to the update of other identifiers that can be used for routing, such as: layer 2 identification (layer-2 ID) routing, or other non-IP routing, such as MAC information, private network address, etc.
  • layer-2 ID layer 2 identification
  • non-IP routing such as MAC information, private network address, etc.
  • new identities of other UEs that may be leaked will also be updated, for example, application identities of UEs and the like. This part of the description is embodied in an optional manner in the foregoing embodiment, and will not be repeated here.
  • the first terminal eg: UE1
  • the second terminal eg: UE2
  • the third terminal eg: UE3
  • network equipment eg: gNB
  • the embodiment of the present application may further provide a communication apparatus that can be applied to the first terminal.
  • FIG. 15 shows a schematic structural diagram of a communication apparatus provided by an embodiment of the present application.
  • the communication device includes: a processing unit 1501 and a transceiver unit 1502 .
  • the processing unit 1501 and the transceiver unit 1502 are used to implement the steps performed by the first terminal described in the foregoing embodiments.
  • the transceiver unit 1502 is used to implement the sending functions of the first terminal such as S401, S405, S702, S706, and S901, as well as the receiving functions embodied in other unused steps.
  • the processing unit 1501 is configured to implement data processing functions of the first terminal such as S404, S701, and S705.
  • the sending and receiving functions of the first terminal described in the foregoing embodiments can be implemented by the transceiver unit 1502 .
  • the data processing functions of the first terminal such as: generating an updated layer 2 identifier of the first terminal, performing an IP replacement operation, etc., can be implemented by the processing unit 1501, which will not be described in detail here.
  • FIG. 16 shows another schematic structural diagram of a communication apparatus provided by an embodiment of the present application.
  • the communication device includes: a processing unit 1601 and a transceiver unit 1602 .
  • the processing unit 1601 and the transceiver unit 1602 are configured to implement the steps performed by the second terminal described in the foregoing embodiments.
  • the transceiver unit 1602 is used to implement the sending functions of the second terminal such as S403, S405, S704, S801, S1202, S1205, S1303, S1306, and S1401, and other receiving functions not embodied in steps.
  • the processing unit 1601 is configured to implement data processing functions of the second terminal such as S402, S406, S703, S707, S1201, and S1302.
  • the sending and receiving functions of the second terminal described in the foregoing embodiments can be implemented by the transceiver unit 1602 .
  • the data processing functions of the second terminal such as: generating an updated layer 2 identifier of the second terminal, performing an IP replacement operation, etc., can be implemented by the processing unit 1601, which will not be described in detail here.
  • FIG. 17 shows another schematic structural diagram of a communication apparatus provided by an embodiment of the present application.
  • the communication device includes: a processing unit 1701 and a transceiver unit 1702 .
  • the processing unit 1701 and the transceiver unit 1702 are configured to implement the steps performed by the third terminal described in the foregoing embodiments.
  • the transceiver unit 1702 is used to implement the sending functions of the third terminal such as S1204, S1301, and S1305, as well as the receiving functions embodied in other unused steps.
  • the processing unit 1701 is configured to implement data processing functions of the third terminal such as S902, S1203, S1206, S1304, and S1307.
  • the processing unit 1701 and the transceiver unit 1702 are configured to implement the steps performed by the network device described in the foregoing embodiments.
  • the transceiver unit 1702 is used to implement the sending functions of the network device such as S1403, and the receiving functions embodied in other unused steps.
  • the processing unit 1701 is used to implement data processing functions such as S1402 of the network device.
  • the sending and receiving functions of the first device described in the foregoing embodiments can be implemented by the transceiver unit 1702 .
  • the data processing functions of the first device can all be implemented by the processing unit 1701, which will not be described in detail here.
  • the division of units in the above apparatus is only a division of logical functions, and in actual implementation, it may be fully or partially integrated into one physical entity, or may be physically separated. And all the units in the device can be realized in the form of software calling through the processing element; also can all be realized in the form of hardware; some units can also be realized in the form of software calling through the processing element, and some units can be realized in the form of hardware.
  • each unit can be a separately established processing element, or can be integrated in a certain chip of the device to be implemented, and can also be stored in the memory in the form of a program, which can be called by a certain processing element of the device and execute the unit's processing.
  • All or part of these units can be integrated together, and can also be implemented independently.
  • the processing element described here may also be called a processor, which may be an integrated circuit with signal processing capability.
  • each step of the above method or each of the above units may be implemented by an integrated logic circuit of hardware in the processor element or implemented in the form of software being invoked by the processing element.
  • a unit in any of the above apparatuses may be one or more integrated circuits configured to implement the above methods, such as: one or more ASICs, or, one or more DSPs, or, one or more FPGA, or a combination of at least two of these integrated circuit forms.
  • the processing element can be a general-purpose processor, such as a CPU or other processors that can invoke programs.
  • these units can be integrated together and implemented in the form of a system-on-a-chip (SOC).
  • the above unit for receiving is an interface circuit or input circuit of the device for receiving signals from other devices.
  • the receiving unit is an interface circuit or an input circuit used by the chip to receive signals from other chips or devices.
  • the means for transmitting is an interface circuit or output circuit of the device for transmitting signals to other devices.
  • the sending unit is an interface circuit or an output circuit used by the chip to send signals to other chips or devices.
  • an embodiment of the present application may further provide a communication apparatus, which may be applied to any one of the first terminal, the second terminal, and the first device.
  • the communication apparatus may include: a processor and an interface circuit.
  • the processor may include one or more.
  • the processor When the communication device is applied to the first terminal, the second terminal, or the first device, the processor is configured to communicate with other devices through the interface circuit, and execute the corresponding execution of the first terminal, the second terminal, or the first device in the above method. of the various steps.
  • the first terminal, the second terminal, or the first device respectively implements the units of each corresponding step in the above method, which may be implemented in the form of a processing element scheduler.
  • an apparatus for a first terminal, a second terminal, or a first device may include a processing element and a storage element, and the processing element invokes a program stored in the storage element to execute the corresponding first terminal and second terminal in the above method embodiments. , or a method performed by the first device.
  • the storage element may be a storage element on the same chip as the processing element, ie, an on-chip storage element.
  • the program for executing the method performed by the first terminal, the second terminal, or the first device in the above method may be in a storage element on a different chip from the processing element, ie, an off-chip storage element.
  • the processing element calls or loads the program from the off-chip storage element to the on-chip storage element, so as to call and execute the method performed by the first terminal, the second terminal, or the first device in the above method embodiments.
  • an embodiment of the present application may further provide a communication apparatus, and the communication apparatus may include a processor, configured to execute computer instructions stored in a memory, and when the computer instructions are executed, cause the apparatus to execute the above first terminal , the second terminal, or the method executed by the first device.
  • the memory may be located within the communication device or external to the communication device.
  • the processor includes one or more.
  • the units of the first terminal, the second terminal, or the first device implementing each step in the above method may be configured as one or more processing elements, and these processing elements may be provided in the corresponding first terminal,
  • the processing elements here may be integrated circuits, such as: one or more ASICs, or, one or more DSPs, or, one or more FPGAs, or a combination of these types of integrated circuits . These integrated circuits can be integrated together to form chips.
  • the units of the first terminal, the second terminal, or the first device that implement each step in the above method may be integrated together and implemented in the form of an SOC, and the SOC chip is used to implement the corresponding method.
  • At least one processing element and a storage element may be integrated in the chip, and the corresponding method may be implemented in the form of a program stored in the storage element being invoked by the processing element; or, at least one integrated circuit may be integrated in the chip for implementing the corresponding method; or , can be combined with the above implementations, the functions of some units are realized in the form of calling programs by processing elements, and the functions of some units are realized in the form of integrated circuits.
  • the processing elements here are the same as those described above, and may be a general-purpose processor, such as a CPU, or one or more integrated circuits configured to implement the above method, such as: one or more ASICs, or one or more microprocessors DSP, or, one or more FPGAs, etc., or a combination of at least two of these integrated circuit forms.
  • a general-purpose processor such as a CPU
  • one or more integrated circuits configured to implement the above method, such as: one or more ASICs, or one or more microprocessors DSP, or, one or more FPGAs, etc., or a combination of at least two of these integrated circuit forms.
  • the storage element may be one memory or a collective term for multiple storage elements.
  • an embodiment of the present application further provides a chip system, and the chip system can be applied to any one of the above-mentioned first terminal, second terminal, or first device.
  • the chip system includes one or more interface circuits and one or more processors; the interface circuit and the processor are interconnected by lines; the processor receives and executes computer instructions from the memory of the electronic device through the interface circuit, so as to realize the corresponding methods in the above method embodiments. A method performed by the first terminal, the second terminal, or the first device.
  • the disclosed apparatus and method may be implemented in other manners.
  • the device embodiments described above are only illustrative.
  • the division of the modules or units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components may be Incorporation may either be integrated into another device, or some features may be omitted, or not implemented.
  • the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components shown as units may be one physical unit or multiple physical units, that is, they may be located in one place, or may be distributed to multiple different places . Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit.
  • the above-mentioned integrated units may be implemented in the form of hardware, or may be implemented in the form of software functional units.
  • the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it may be stored in a readable storage medium.
  • the software product is stored in a program product, such as a computer-readable storage medium, and includes several instructions to cause a device (which may be a single-chip microcomputer, a chip, etc.) or a processor (processor) to execute all of the methods described in the various embodiments of the present application. or part of the steps.
  • the aforementioned storage medium includes: a U disk, a removable hard disk, a ROM, a RAM, a magnetic disk, or an optical disk and other mediums that can store program codes.
  • the embodiments of the present application may further provide a computer-readable storage medium, including: computer software instructions; when the computer software instructions are executed in the electronic device or in a chip built in the electronic device, the electronic device can be made to perform the foregoing implementation. For example, the method performed by the first terminal, the second terminal, or the first device.

Landscapes

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

Abstract

本申请公开了一种路由信息更新方法、通信装置及存储介质。该方法包括：第二终端生成第一终端的路由信息，第二终端的中继功能基于第一终端的路由信息为第一终端与第一设备提供通信服务，第一设备包括第三终端和/或网络设备。第二终端对第一终端的路由信息进行更新，生成第一终端的更新后的路由信息。第二终端向第一终端发送第二消息，第二消息包括第一终端的更新后的路由信息。第一设备包括第三终端时，第二终端向第三终端发送第一终端的更新后的路由信息。该方法中，第二终端可以为第一终端分发第一终端的路由信息，并更新第一终端的路由信息。

Description

路由信息更新方法、通信装置及存储介质
本申请要求于2020年09月30日提交国家知识产权局、申请号为202011066067.7、申请名称为“路由信息更新方法、通信装置及存储介质”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请实施例涉及通信领域，尤其涉及一种路由信息更新方法、通信装置及存储介质。
背景技术
近距离业务通信，也称为邻近服务(proximity service)通信。一种近距离业务通信的场景中，某个终端设备(如：手机)可以通过另外一个终端设备(如：也可以是手机)与网络(network)进行通信。例如，用户设备(user equipment，UE)1可以通过UE2与网络进行通信，其中，UE2扮演了UE1至网络的中继(UE-to-network relay)的角色，能够提高网络对UE1的覆盖能力。另一种近距离业务通信的场景中，某个终端设备也可以通过另外一个终端设备，与又一个终端设备进行通信。例如，UE1可以通过UE2与UE3进行通信，其中，UE2扮演了UE1至UE3的中继(UE-to-UE relay)的角色，能够增大UE1和UE3之间的通信距离。
上述近距离业务通信的场景也可称为relay场景。在relay场景中，不同UE之间是基于UE的IP地址进行数据传输的，但是，目前还无法实现针对relay场景进行UE的IP更新。
发明内容
本申请实施例提供一种路由信息更新方法、通信装置及存储介质，可以实现针对relay场景进行终端的路由信息的更新。
第一方面，本申请实施例提供一种路由信息更新方法，所述方法包括：第二终端生成第一终端的路由信息，第二终端的中继功能基于第一终端的路由信息为第一终端与第一设备提供通信服务，第一设备包括第三终端和/或网络设备；第二终端对第一终端的路由信息进行更新，生成第一终端的更新后的路由信息；第二终端向第一终端发送第二消息，第二消息包括第一终端的更新后的路由信息；第一设备包括第三终端时，第二终端向第三终端发送第一终端的更新后的路由信息。
该方法中，第二终端可以将存储的第一终端的更新前的路由信息替换为第一终端的更新后的路由信息。第一终端接收到第二消息后，可以将第一终端的更新前的路由信息替换为第一终端的更新后的路由信息。后续，第一终端可以基于第一终端的更新后的路由信息，使用第二终端的中继功能，与第一设备通信。
该方法可以适用于relay场景下对UE的路由信息进行更新。该方法中，第二终端扮演了relay的角色，用于为第一终端与第一设备提供通信服务。第二终端可以为第一终端分发第一终端的路由信息，并更新第一终端的路由信息。
在一种可能的设计中，第一终端将存储的第一终端的更新前的路由信息替换为第一终端的更新后的路由信息后，可以向第二终端发送第三消息通知第二终端其已完成路由信息的替换。也即，第三消息可以用于指示第一终端已将第一终端的更新前的路由信息替换为第一终端的更新后的路由信息。第二终端将存储的第一终端的更新前的路由信息替换为第一终端的更新后的路由信息可以是在接收到第三消息后执行。
在其他可能的设计中，第二终端对第一终端的路由信息进行更新，生成第一终端的更新后的路由信息后，即可将存储的第一终端的更新前的路由信息替换为第一终端的更新后的路由信息。并不一定要在接收到第三消息后，才执行该替换过程，本申请对第二终端执行替换过程的时序并不作限制。
在一种可能的设计中，所述第二终端对第一终端的路由信息进行更新之前，所述方法还包括：第二终端接收来自第一终端的第一消息，第一消息用于指示第二终端对第一终端的路由信息进行更新；所述第二终端对第一终端的路由信息进行更新，包括：第二终端根据第一消息，对第一终端的路由信息进行更新。
本设计中，上述更新过程可以由第一终端发起。例如，当第一终端确定需要更新路由信息时，如：为保证数据传输的安全性或隐私性，第一终端确定需要对路由信息进行定期更新，或者，当第一终端的的应用标识和/或位置发生变化导致需要对第一终端的路由信息进行更新时，第一终端可以向第二终端发送第一消息，以指示第二终端对第一终端的路由信息进行更新。
在一种可能的设计中，该路由信息更新方法可以基于第一终端的连接标识更新的过程而实现。第一消息是连接标识更新请求消息，第二消息是连接标识更新响应消息。第一消息包括第一终端的更新后的层2标识；所述方法还包括：第二终端对第二终端的层2标识进行更新，生成第二终端的更新后的层2标识；第二消息还包括第二终端的更新后的层2标识。
本设计中，上述第三消息可以是连接标识更新确认消息。
可选地，第二终端向第一终端发送的第二消息中还可以包括第一终端的更新后的层2标识，第一终端接收到连接标识更新响应消息后，还可以确定第二消息中包括的第一终端的更新后的层2标识与自己在第一消息中发送的第一终端的更新后的层2标识是否相同，从而实现校验，以保证更新准确性。如果第一终端校验得到二者不同，则第一终端可以向第二终端发送拒绝消息，不执行后续的步骤。如果相同，则继续执行。
可选地，上述路由信息更新方法中，第一消息中还可以包括第一终端的更新前的路由信息，可以用于第二终端确定第一终端之前的路由信息，即第一终端的更新前的路由信息。
在一种可能的设计中，第一终端的路由信息包括：第一路由信息和第二路由信息；第一路由信息是第一终端与第二终端直接通信时所使用的路由信息，第二路由信息是第一终端使用第二终端的中继功能时所使用的路由信息；第一消息包括更新指示，更新指示用于指示第二终端对第二路由信息进行更新；第一终端的更新后的路由信息是更新后的第二路由信息。
可选地，第一终端也可以将自己生成的第一路由信息发送给第二终端，用于第一终端和第二终端之间直接进行通信。
在一种可能的设计中，第一消息中还可以包括第一终端的更新前的层2标识、以及第二终端的更新前的层2标识，可以用于的第二终端确定第一消息的发送者身份。
例如，当有一个或多个第一终端使用第二终端的中继功能时，第二终端可以根据第一消息中包括的第一终端的更新前的层2标识、以及第二终端的更新前的层2标识，确定是前述一个或多个第一终端中的哪一个发送的第一消息。
在一种可能的设计中，所述方法还包括：第二终端根据第一消息，生成第二终端的更新后的路由信息；第二消息还包括第二终端的更新后的路由信息。
在一种可能的设计中，第一设备包括网络设备时，所述方法还包括：第二终端向网络设备发送第一终端的更新后的路由信息。
在一种可能的设计中，第一消息还包括第四终端的标识信息，第四终端包括第三终端；所述方法还包括：第二终端根据第四终端的标识信息，向第四终端发送第一终端的更新后的路由信息。
本设计中，第二终端向哪个第三终端发送第一终端的更新后的路由信息，是根据来自第一终端的指示确定的，第一终端可以通过向第一终端发送第四终端的标识信息进行指示。例如，第一终端可以通过前述第一消息向第二终端发送第四终端的标识信息。从而，考虑了按需的更新。只有需要与第一终端通信的第三终端才能够获得第一终端的更新后的路由信息，能够避免额外通知每一个第三终端的操作。
在一种可能的设计中，所述方法还包括：第二终端对第三终端的路由信息进行更新，生成第三终端的更新后的路由信息；第二终端向第三终端以及第一终端发送第三终端的更新后的路由信息。
例如，所述第二终端对第三终端的路由信息进行更新，包括：第二终端接收来自第一终端的第一消息后，对第三终端的路由信息进行更新。
本设计中，可以实现同时对第一终端和第三终端的路由信息进行更新，能够避免攻击者根据相同的第三终端的路由信息，确定第一终端的更新前的路由信息和更新后的路由信息是属于同一个第一终端的。从而，可以避免关联攻击。
在一种可能的设计中，第一设备包括网络设备时，所述方法还包括：第二终端向网络设备发送第一无线资源控制RRC消息，第一RRC消息包括为第一终端提供数据传输的空口的标识信息，第一RRC消息用于指示网络设备对所述标识信息进行更新；第二终端接收来自网络设备的第二RRC消息，第二RRC消息包括更新后的标识信息。
本设计可以应用于第一终端与网络设备之间有端到端的保护机制的场景，此时，需要更新第一终端与网络设备之间端到端的可以用来标识第一终端的参数。
第二方面，本申请实施例提供一种通信装置。该装置具有实现上述第一方面所述方法的功能。功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。硬件或软件包括一个或多个与上述第一方面所述方法的功能相对应的单元或模块，例如，处理单元、收发单元等。
第三方面，本申请实施例还提供一种通信装置，包括：处理器，用于执行存储器中存储的计算机指令，当所述计算机指令被执行时，使得所述装置执行第一方面或第一方面任一可能的设计中所述的方法。
第四方面，本申请实施例还提供一种通信装置，包括：处理器和接口电路，处理器用于通过接口电路与其它装置通信，并执行第一方面或第一方面任一可能的设计中所述的方法。
以上第二方面至第四方面所述的通信装置，可以应用于具有中继功能的第二终端。
第五方面，本申请实施例还提供一种计算机可读存储介质，包括：计算机软件指令； 当所述计算机软件指令在电子设备，如：具有中继功能的第二终端，或内置在电子设备的芯片中运行时，使得电子设备执行第一方面或第一方面任一可能的设计中所述的方法。
可以理解地，上述提供的第二方面至第五方面所能达到的有益效果，可参考第一方面及其任一种可能的设计方式中的有益效果，此处不再赘述。
第六方面，本申请实施例提供一种路由信息更新方法，所述方法包括：第一终端生成第一消息，第一消息用于指示第二终端对第一终端的路由信息进行更新；第一终端使用第一终端的路由信息通过第二终端的中继功能与第一设备通信，第一设备包括第三终端和/或网络设备；第一终端向第二终端发送第一消息；第一终端接收来自第二终端的第二消息，第二消息包括第一终端的更新后的路由信息；第一终端将第一终端的更新前的路由信息替换为第一终端的更新后的路由信息。
在一种可能的设计中，第一消息是连接标识更新请求消息，第二消息是连接标识更新响应消息；所述第一终端生成第一消息之前，所述方法还包括：第一终端对第一终端的层2标识进行更新，生成第一终端的更新后的层2标识；第一消息包括第一终端的更新后的层2标识；第二消息还包括第二终端的更新后的层2标识。
在一种可能的设计中，第一终端的路由信息包括：第一路由信息和第二路由信息；第一路由信息是第一终端与所述第二终端直接通信时所使用的路由信息，第二路由信息是第一终端使用第二终端的中继功能时所使用的路由信息；第一消息包括更新指示，更新指示用于指示第二终端对第二路由信息进行更新；第一终端的更新后的路由信息是更新后的第二路由信息。
在一种可能的设计中，第二消息还包括第二终端的更新后的路由信息。
在一种可能的设计中，第一消息还包括第四终端的标识信息，第四终端包括第三终端。
在一种可能的设计中，所述方法还包括：第一终端通过第二终端向第四终端发送第一终端的更新后的路由信息；第四终端包括第三终端。
本设计中，第一终端可以通过第二终端向第三终端透传第一终端的更新后的路由信息。可选地，第三终端可以在接收到第一终端的更新后的路由信息后，主动向第二终端发起对第三终端的路由信息的更新。
在一种可能的设计中，所述方法还包括：第一终端接收来自第二终端的第三终端的更新后的路由信息。
上述第六方面所述的方法与上述第一方面所述的方法中的部分步骤相对应，为第一终端执行的步骤，因此，与上述第一方面中所述的相同的有益效果在此未再赘述。
第七方面，本申请实施例提供一种通信装置。该装置具有实现上述第六方面所述方法的功能。功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。硬件或软件包括一个或多个与上述第六方面所述方法的功能相对应的单元或模块，例如，处理单元、收发单元等。
第八方面，本申请实施例还提供一种通信装置，包括：处理器，用于执行存储器中存储的计算机指令，当所述计算机指令被执行时，使得所述装置执行第六方面或第六方面任一可能的设计中所述的方法。
第九方面，本申请实施例还提供一种通信装置，包括：处理器和接口电路，处理器用于通过接口电路与其它装置通信，并执行第六方面或第六方面任一可能的设计中所述的方法。
以上第七方面至第九方面所述的通信装置，可以应用于具有第一终端，第一终端使用第一终端的路由信息通过第二终端的中继功能与第一设备通信。
第十方面，本申请实施例还提供一种计算机可读存储介质，包括：计算机软件指令；当所述计算机软件指令在电子设备，如：上述第一终端，或内置在电子设备的芯片中运行时，使得电子设备执行第六方面或第六方面任一可能的设计中所述的方法。
可以理解地，上述提供的第七方面至第十方面所能达到的有益效果，可参考第六方面及其任一种可能的设计方式中的有益效果，此处不再赘述。
第十一方面，本申请实施例提供一种路由信息更新方法，所述方法包括：第三终端使用第三终端的路由信息通过第二终端的中继功能与第一设备通信，第一设备包括第一终端和/或网络设备；第三终端接收来自第二终端的第一终端的更新后的路由信息；第三终端向第二终端发送用于指示第二终端对所述第三终端的路由信息进行更新的消息；第三终端接收来自第二终端的第三终端的更新后的路由信息。
该方法中，第一终端的更新后的路由信息是第一终端通过第二终端透传给第三终端的。第三终端可以在接收到第一终端的更新后的路由信息后，主动向第二终端发起对第三终端的路由信息的更新。
第十二方面，本申请实施例提供一种通信装置。该装置具有实现上述第十一方面所述方法的功能。功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。硬件或软件包括一个或多个与上述第十一方面所述方法的功能相对应的单元或模块，例如，处理单元、收发单元等。
第十三方面，本申请实施例还提供一种通信装置，包括：处理器，用于执行存储器中存储的计算机指令，当所述计算机指令被执行时，使得所述装置执行第十一方面或第十一方面任一可能的设计中所述的方法。
第十四方面，本申请实施例还提供一种通信装置，包括：处理器和接口电路，处理器用于通过接口电路与其它装置通信，并执行第十一方面或第十一方面任一可能的设计中所述的方法。
以上第十二方面至第十四方面所述的通信装置，可以应用于第三终端。
第十五方面，本申请实施例还提供一种计算机可读存储介质，包括：计算机软件指令；当所述计算机软件指令在电子设备，如：第三终端，或内置在电子设备的芯片中运行时，使得电子设备执行第十一方面或第十一方面任一可能的设计中所述的方法。
可以理解地，上述提供的第十二方面至第十五方面所能达到的有益效果，可参考第十一方面及其任一种可能的设计方式中的有益效果，此处不再赘述。
第十六方面，本申请实施例提供一种路由信息更新方法，所述方法包括：网络设备通过第二终端与第一终端通信；网络设备接收来自第二终端的第一RRC消息，第一RRC消息包括为第一终端提供数据传输的空口的标识信息，第一RRC消息用于指示网络设备对所述标识信息进行更新；网络设备根据第一RRC消息，对为第一终端提供数据传输的空口的标识信息进行更新，生成更新后的标识信息；网络设备向第二终端发送第二RRC消息，第二RRC消息包括所述更新后的标识信息。
该方法中可以适用于使用第二终端的中继功能的第一终端与网络设备之间有端到端的保护机制的场景，此时，需要更新第一终端与网络设备之间端到端的可以用来标识第一终端的参数。例如，上述为第一终端提供数据传输的空口的标识信息。
在一种可能的设计中，所述网络设备接收来自第二终端的第一RRC消息，包括：网 络设备接收第二终端对第一终端的路由信息进行更新后发送的所述第一RRC消息。
第十七方面，本申请实施例提供一种通信装置。该装置具有实现上述第十六方面所述方法的功能。功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。硬件或软件包括一个或多个与上述第十六方面所述方法的功能相对应的单元或模块，例如，处理单元、收发单元等。
第十八方面，本申请实施例还提供一种通信装置，包括：处理器，用于执行存储器中存储的计算机指令，当所述计算机指令被执行时，使得所述装置执行第十六方面或第十六方面任一可能的设计中所述的方法。
第十九方面，本申请实施例还提供一种通信装置，包括：处理器和接口电路，处理器用于通过接口电路与其它装置通信，并执行第十六方面或第十六方面任一可能的设计中所述的方法。
以上第十七方面至第十九方面所述的通信装置，可以应用于网络设备。
第二十方面，本申请实施例还提供一种计算机可读存储介质，包括：计算机软件指令；当所述计算机软件指令在电子设备，如：网络设备，或内置在电子设备的芯片中运行时，使得电子设备执行第十六方面或第十六方面任一可能的设计中所述的方法。
可以理解地，上述提供的第十七方面至第二十方面所能达到的有益效果，可参考第十六方面及其任一种可能的设计方式中的有益效果，此处不再赘述。
第二十一方面，本申请实施例还提供一种通信装置，包括：收发单元和处理单元。收发单元可以用于收发信息，或者用于与其他网元通信。处理单元可以用于对数据进行处理。如：该装置可以通过收发单元和处理单元实现如第一方面、第六方面、第十一方面、以及第十六方面中的任一方面所述的方法。
第二十二方面，本申请实施例还提供一种计算机程序产品，该计算机程序产品被执行时可以实现如第一方面、第六方面、第十一方面、以及第十六方面中的任一方面所述的方法。
第二十三方面，本申请实施例还提供一种芯片系统，该芯片系统应用于电子设备(如：上述第一终端、第二终端、第三终端或网络设备)。芯片系统包括一个或多个接口电路和一个或多个处理器；接口电路和处理器通过线路互联；处理器通过接口电路从电子设备的存储器接收并执行计算机指令，以实现第一方面、第六方面、以及第十六方面中的任一方面所述的方法。
第二十四方面，本申请实施例还提供一种通信系统，该通信系统至少包括第一终端、第二终端、以及第三终端。第一终端用于实现如第六方面所述的方法，第二终端用于实现如第一方面所述的方法。第三终端用于实现如第十一方面所述的方法。
第二十五方面，本申请实施例还提供一种通信系统，该通信系统至少包括第一终端、第二终端、以及网络设备。第一终端用于实现如第六方面所述的方法，第二终端用于实现如第一方面所述的方法。网络设备用于实现如第十六方面所述的方法。
可以理解地，上述提供的第二十一方面至第二十五方面所能达到的有益效果，可参考第一方面、第六方面、第十一方面、以及第十六方面等所述的有益效果，此处不再赘述。
附图说明
图1示出了一种近距离业务通信的场景示意图；
图2示出了另一种近距离业务通信的场景示意图；
图3示出了本申请实施例提供的一种电子设备的组成示意图；
图4示出了本申请实施例提供的路由信息更新方法的流程示意图；
图5示出了UE1通过relay与UE3通信时的连接标识的示意图；
图6示出了UE1通过relay与gNB通信时的连接标识的示意图；
图7示出了本申请实施例提供的路由信息更新方法的另一流程示意图；
图8示出了本申请实施例提供的路由信息更新方法的又一流程示意图；
图9示出了本申请实施例提供的路由信息更新方法的又一流程示意图；
图10示出了专用连接的示意图；
图11示出了共用连接的示意图；
图12示出了本申请实施例提供的路由信息更新方法的又一流程示意图；
图13示出了本申请实施例提供的路由信息更新方法的又一流程示意图；
图14示出了本申请实施例提供的路由信息更新方法的又一流程示意图；
图15示出了本申请实施例提供的通信装置的结构示意图；
图16示出了本申请实施例提供的通信装置的另一结构示意图；
图17示出了本申请实施例提供的通信装置的又一结构示意图。
具体实施方式
本申请实施例可以适用于近距离业务通信的场景。近距离业务通信也称为邻近服务(proximity service)通信。首先结合图1和图2，对本申请实施例的应用场景进行介绍。
图1示出了一种近距离业务通信的场景示意图。如图1所示，一种近距离业务通信的场景可以包括：用户设备(user equipment，UE)1、UE2和网络(network)。其中，UE1可以与UE2连接，UE2可以与网络(network)连接(如：UE2可以与用于接入网络的网络设备连接)，从而UE1可以通过UE2与网络进行通信，实现UE1与网络之间的数据传输。
在图1所示的近距离业务通信场景中，UE2扮演了UE1至网络的中继(UE-to-network relay)的角色，能够提高网络对UE1的覆盖能力。其中，UE1与UE2之间的接口为PC5接口，UE2与网络之间的接口为Uu接口。
图2示出了另一种近距离业务通信的场景示意图。如图2所示，另一种近距离业务通信的场景可以包括：UE1、UE2和UE3。其中，UE1可以与UE2连接，UE2可以与UE3连接，从而UE1可以通过UE2与UE3进行通信，实现UE1与UE3之间的数据传输。
在图2所示的近距离业务通信场景中，UE2扮演了UE1至UE3的中继(UE-to-UE relay)的角色，能够增大UE1和UE3之间的通信距离。其中，UE1与UE2之间的接口为PC5接口，UE2与UE3之间的接口也为PC5接口。
上述图1和图2所示的近距离业务通信的场景也可称为relay场景。在relay场景中，不同UE之间(如：UE1和UE2，或者UE2和UE3)是基于UE的IP地址进行数据传输的。为保证数据传输的安全性，常常需要对UE的IP地址进行定期地更新，或者，当UE的应用标识和/或位置发生变化时，需要对UE的IP地址进行更新。但是，目前还无法实 现针对relay场景进行UE的IP更新。
对此，本申请实施例提供了一种路由信息更新方法，该方法可以适用于上述relay场景下对UE的路由信息进行更新。该方法中，第二终端可以生成第一终端的路由信息，第二终端的中继功能能够基于第一终端的路由信息为第一终端与第一设备提供通信服务，第一设备包括第三终端和/或网络设备。在第二终端的中继功能基于第一终端的路由信息为第一终端与第一设备提供通信服务的过程中，第二终端可以对第一终端的路由信息进行更新，生成第一终端的更新后的路由信息。然后，第二终端可以通过消息向第一终端发送第一终端的更新后的路由信息，该消息可称为第二消息。第一终端在接收到第一终端的更新后的路由信息后，会用第一终端的更新后的路由信息替换第一终端的更新前的路由信息，从而后续会根据第一终端的更新后的路由信息，通过第二终端的中继功能实现与第一设备的通信。其中，当第一设备包括第三终端时，第二终端还会向第三终端发送第一终端的更新后的路由信息，第三终端可以将存储的第一终端的更新前的路由信息替换为接收到的第一终端的更新后的路由信息，从而后续会根据第一终端的更新后的路由信息，通过第二终端的中继功能与第一终端进行数据传输。
该方法中，第二终端扮演了relay的角色，用于为第一终端与第一设备提供通信服务。第二终端可以为第一终端分发第一终端的路由信息，并更新第一终端的路由信息。例如，在图1所示的应用场景中，第一终端是指UE1，第二终端是指UE2，第一设备是指用于接入网络的网络设备。在图2所示的应用场景中，第一终端是指UE1，第二终端是指UE2，第一设备是指UE3。
可以理解的，本申请实施例中，第一终端和第二终端直接可以建立安全连接。第一终端被配置为可以使用第二终端的中继功能。第二终端被配置为可以执行中继功能，将第一终端的数据发送给第一设备。
一些实施例中，第一终端的配置信息(即是指配置第一终端可以使用第二终端的中继功能)可以在注册流程中，从网络设备或网元中得到，例如，网络设备或网元可以包括：策略控制功能(policy control function，PCF)、统一数据管理功能(unified data management，UDM)、用户数据记录(user data records，UDR)、ProSe功能实体(ProSe function)等，在此不作限制。以PCF为例，具体配置路径可以为：PCF发送配置信息至接入和移动管理功能(access and mobility management function，AMF)，再由AMF通过实现非接入层(non-access stratum，NAS)消息发送给第一终端。
类似地，第二终端或第一设备包括的第三终端的配置过程，可以与第一终端的配置过程相同，在此不再赘述。
可选地，本申请实施例中，路由信息可以是IP路由、或者，层2标识(layer-2 ID)路由、又或者其他non-IP路由，例如，MAC信息，私网地址等，在此对路由信息的具体类型不作限制，下文以IP为例进行描述。
可选地，上述第一终端、第二终端、第三终端等终端也可以称之为用户设备(User Equipment，UE)、移动台(mobile station，MS)、移动终端(mobile terminal，MT)等。或者，其中，第三终端还可以称为远端(remote)UE。
一些实施例中，终端(本申请实施例中，终端指第一终端、第二终端、以及第三终端中的任意一个)可以是指向用户提供语音和/或数据连通性的设备，例如，可以是移动电话(“蜂窝”电话)、手机、电脑，无绳电话、会话发起协议(session initiation protocol，SIP)电话、无线本地环路(wireless local loop，WLL)站、个人数字助理(personal digital  assistant，PDA)、膝上型计算机、手持式通信设备、手持式计算设备、卫星无线设备、无线调制解调器卡、电视机顶盒(set top box，STB)、用户驻地设备(customer premise equipment，CPE)、可穿戴设备(例如智能手表、智能手环、计步器等)，车载设备(例如，汽车、自行车、电动车、飞机、船舶、火车、高铁等)、虚拟现实(virtual reality，VR)设备、增强现实(augmented reality，AR)设备、工业控制(industrial control)中的无线终端、智能家居设备(例如，冰箱、电视、空调、电表等)、智能机器人、车间设备、无人驾驶(self driving)中的无线终端、远程手术(remote medical surgery)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端，或智慧家庭(smart home)中的无线终端、飞行设备(例如，智能机器人、热气球、无人机、飞机)以及用于在无线系统上进行通信的其它设备等，本申请对终端的具体表现形式不作限制。
可选地，上述网络设备也可以称为接入网(access network，AN)设备，如：可以是无线接入网设备(radio access network，RAN)设备或下一代无线接入网设备。终端可以与AN设备进行通信。AN设备可以为终端提供无线资源管理、服务质量管理、数据加密和压缩等功能服务。
一些实施例中，AN设备可以是下一代节点(next generation node B，gNB)、演进型节点B(evolved Node B，eNB)、下一代演进型节点(next generation evolved node B，ng-eNB)等不支持安全策略的基站。或者，另外一些实施例中，AN设备也可以是支持安全策略的基站，如：5G基站。又或者，还有一些实施例中，AN设备还可以是传输接收点(transmission reception point，TRP)、无线网络控制器(radio network controller，RNC)、基站控制器(base station controller，BSC)、基站收发台(base transceiver station，BTS)、家庭基站(例如，home evolved NodeB，或home Node B，HNB)、基带单元(base band unit，BBU)，或无线保真(wireless fidelity，Wifi)接入点(access point，AP)、集中单元(central unit，CU)、分布式单元(distributed unit，DU)、集中单元-控制平面(central unit-control plane，CU-CP)、集中单元-用户平面(central unit-user plane，CU-UP)等。
以下结合附图对本申请实施例提供的路由信息更新方法进行示例性说明。
需要说明的是，在本申请的描述中，“第一”、“第二”等字样仅仅是为了区分描述，并不用于对某个特征的特别限定。本申请实施例的描述中，“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。字符“/”一般表示前后关联对象是一种“或”的关系。本申请中所涉及的至少一个是指一个或多个；多个，是指两个或两个以上。
另外，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
图3示出了本申请实施例提供的一种电子设备的组成示意图。该电子设备可以是本申请实施例中的第一终端、第二终端、以及第一设备(网络设备或第三终端)。如图3所示，该电子设备可以包括：至少一个处理器31，存储器32、通信接口33、总线34。
下面结合图3对终端的各个构成部件进行具体的介绍。
处理器31是终端的控制中心，可以是一个处理器，也可以是多个处理元件的统称。例如，处理器31可以是一个中央处理器(central processing unit，CPU)，也可以是特定集成电路(application specific integrated circuit，ASIC)，或者还可以是被配置成实施本 申请实施例的一个或多个集成电路，例如：一个或多个微处理器(digital signal processor，DSP)，或，一个或者多个现场可编程门阵列(field programmable gate array，FPGA)等。
其中，处理器31可以通过运行或执行存储在存储器32内的软件程序，以及调用存储在存储器32内的数据，执行电子设备的各种功能。
在具体的实现中，作为一种实施例，处理器31可以包括一个或多个CPU，例如图3中所示的CPU0和CPU1。
在具体的实现中，作为一种实施例，电子设备可以包括多个处理器，例如图3中所示的处理器31和处理器35。这些处理器中的每一个可以是一个单核处理器(single-CPU)，也可以是一个多核处理器(multi-CPU)。这里的处理器可以指一个或多个设备、电路、和/或用于处理数据(例如计算机程序指令)的处理核。
存储器32用于存储执行本申请方案终端执行的方法步骤的软件程序，并由处理器31来控制执行。存储器32可以是只读存储器(read-only memory，ROM)或可存储静态信息和指令的其他类型的静态存储设备，随机存取存储器(random access memory，RAM)或者可存储信息和指令的其他类型的动态存储设备，也可以是电可擦可编程只读存储器(electrically erasable programmable read-only memory，EEPROM)、只读光盘(compact disc read-only memory，CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。
存储器32可以是独立存在，通过总线34与处理器31相连接。或者，存储器32也可以和处理器31集成在一起，在此不作限制。
通信接口33，使用任何收发器一类的装置，用于与其他设备或通信网络通信。通信接口33可以是以太网接口，无线接入网(radio access network，RAN)接口，无线局域网(wireless local area networks，WLAN)接口等。通信接口33可以包括接收单元实现接收功能，以及发送单元实现发送功能。
总线34，可以是工业标准体系结构(industry standard architecture，ISA)总线、外部设备互连(peripheral component interconnect，PCI)总线或扩展工业标准体系结构(extended industry standard architecture，EISA)总线等。该总线可以分为地址总线、数据总线、控制总线等。为便于表示，图3中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
虽然附图3中使用了总线34，但是可以理解的，总线34也可以被替换为其他形式的连接关系，而不局限于总线本身
图4示出了本申请实施例提供的路由信息更新方法的流程示意图。如图4所示，该路由信息更新方法可以包括S401-S406。
S401、第一终端向第二终端发送第一消息，第一消息用于指示第二终端对第一终端的路由信息进行更新。
也即，上述更新过程可以由第一终端发起。例如，当第一终端确定需要更新路由信息时，如：为保证数据传输的安全性或隐私性，第一终端确定需要对路由信息进行定期更新，或者，当第一终端的的应用标识和/或位置发生变化导致需要对第一终端的路由信息进行更新时，第一终端可以向第二终端发送第一消息，以指示第二终端对第一终端的路由信息进行更新。
相应地，第二终端接收来自第一终端的第一消息。
S402、第二终端对第一终端的路由信息进行更新，生成第一终端的更新后的路由信息。
第二终端接收到第一消息后，可以根据第一消息的指示，对第一终端的路由信息进行更新，生成第一终端的更新后的路由信息。
S403、第二终端向第一终端发送第二消息，第二消息包括第一终端的更新后的路由信息。
相应地，第一终端接收来自第二终端的第二消息。
S404、第一终端将存储的第一终端的更新前的路由信息替换为第一终端的更新后的路由信息。
完成替换后，第一终端后续即可根据第一终端的更新后的路由信息，使用第二终端的中继功能与第一设备进行通信时。
S405、第一终端向第二终端发送第三消息，第三消息用于指示第一终端已将第一终端的更新前的路由信息替换为第一终端的更新后的路由信息。
或者，第三消息也可以指示第一终端已接收更新后的路由信息。
相应地，第二终端接收来自第一终端的第三消息。
例如，第一终端将存储的第一终端的更新前的路由信息替换为第一终端的更新后的路由信息后，可以向第二终端发送第三消息通知第二终端其已完成路由信息的替换。第二终端接收到第三消息后，也会将存储的第一终端的更新前的路由信息替换为第一终端的更新后的路由信息。如：可以执行S406。
S406、第二终端将存储的第一终端的更新前的路由信息替换为第一终端的更新后的路由信息。
完成替换后，第二终端的中继功能后续即可根据第一终端的更新后的路由信息，为第一终端与第一设备提供通信服务。
可选地，上述图4所示的路由信息的更新过程中，S406也可以是在S402之后完成。也即，第二终端对第一终端的路由信息进行更新，生成第一终端的更新后的路由信息后，即可将存储的第一终端的更新前的路由信息替换为第一终端的更新后的路由信息。并不一定要在接收到第三消息后，才执行该替换过程，本申请实施例对第二终端执行替换过程的时序并不作限制。
在一种可能的设计中，上述图4所示的路由信息的更新过程可以基于第一终端的连接标识(link identifier)更新的过程而实现，第一终端可以在连接标识的更新过程中获得第二终端颁发的第一终端的更新后的路由信息。
以第一终端为UE1，第二终端为UE2(下面称为relay)，第三终端为UE3，路由信息为IP为例，图5示出了UE1通过relay与UE3通信时的连接标识的示意图。如图5所示，UE1与relay之间的PC5接口的连接相关的标识可以包括：层2标识(layer 2 ID)、Key ID1、Key-session ID1。其中，层2标识包括：UE1 layer 2 ID、relay layer 2 ID1，用于标识UE1和relay之间的层2连接。Key ID1，用于标识UE1和relay之间的共享密钥Key。Key-session ID1，用于标识UE1和relay之间的会话密钥。UE1 layer 2 ID和relay layer 2 ID1对应的UE1的IP为UE1 IP，relay的IP为relay IP1。
请继续参考图5所示，relay与UE3之间的PC5接口的连接相关的标识可以包括：层2标识(layer 2 ID)、Key ID2、Key-session ID2。其中，层2标识包括：relay layer 2 ID2、UE3 layer 2 ID，用于标识relay和UE3之间之间的层2连接。Key ID2，用于标识relay和UE3之间的共享密钥Key。Key-session ID2，用于标识relay和UE3之间的会话密钥。relay layer 2 ID2和UE3 layer 2 ID对应的UE3的IP为UE3 IP，relay的IP为relay IP2。
其中，relay layer 2 ID1和relay layer 2 ID2可以相同或不同，relay IP1和relay IP2也可以相同或不同，在此不作限制。
以第一终端为UE1，第二终端为UE2(下面称为relay)，网络设备为gNB，路由信息为IP为例，图6示出了UE1通过relay与gNB通信时的连接标识的示意图。如图6所示，与前述图5中UE1与relay之间的连接相同，UE1与relay之间的PC5接口的连接相关的标识可以包括：层2标识(layer 2 ID)、Key ID1、Key-session ID1。其中，层2标识包括：UE1 layer 2 ID、relay layer 2 ID1，用于标识UE1和relay之间的层2连接。Key ID1，用于标识UE1和relay之间的共享密钥Key。Key-session ID1，用于标识UE1和relay之间的会话密钥。UE1 layer 2 ID和relay layer 2 ID1对应的UE1的IP为UE1 IP，relay的IP为relay IP1。
请继续参考图6所示，relay与gNB之间的Uu接口的连接相关的标识，可以为relay与gNB之间共享的标识，用来标识他们之间的无线或者有线的连接。例如，可以包括：C-RNTI、SRN、承载标识(或称为空口标识)、频谱标识、为UE1服务的会话ID、PDCP SQN等。其中，承载标识是指为UE1提供数据传输的无线承载(也称空口)的标识信息。
当基于第一终端的连接标识更新的过程实现时，上述第一消息可以是连接标识更新请求(link identifier update request)消息，上述第二消息可以是连接标识更新响应(link identifier update response)消息，上述第三消息可以是连接标识更新确认(link identifier update acknowledgement/ACK)消息。
下面以图7为例，假设第一终端为UE1，第二终端为UE2(下面称为relay)，第三终端为UE3，路由信息为IP，对UE1在连接标识更新的过程中实现路由信息的更新的方式进行示例性说明。其中，UE1与relay之间、以及relay与UE3之间建立安全连接。
图7示出了本申请实施例提供的路由信息更新方法的另一流程示意图。如图7所示，该路由信息更新方法可以包括S701-S707。
S701、UE1生成连接标识更新请求消息，连接标识更新请求消息包括：UE1的更新后的层2标识(UE1new layer-2 ID)。
例如，当UE1确定要执行连接标识的更新时(确定执行更新的条件可以参考前述实施例中所述的第一终端确定更新路由信息的条件)，可以重新选择层2标识，得到UE1的更新后的层2标识，然后生成携带含UE1的更新后的层2标识的连接标识更新请求消息。
可选地，连接标识更新请求消息中还可以包括MSB of Key-sess ID、UE1的更新后的应用标识等。
S702、UE1向relay发送连接标识更新请求消息。
其中，连接标识更新请求消息用于指示relay对UE1的IP进行更新。
相应地，relay接收连接标识更新请求消息。
S703、relay生成relay的更新后的层2标识(relay new layer-2 ID)，以及对UE1的IP进行更新，生成UE1的更新后的IP(new UE1 IP)。
relay生成relay的更新后的层2标识后，会用其替换relay的更新前的层2标识。
S704、relay向UE1发送连接标识更新响应消息，连接标识更新响应消息包括：relay的更新后的层2标识、UE1的更新后的IP。
相应地，UE1接收连接标识更新响应消息。
这里，可选地，relay向UE1发送的连接标识更新响应消息中还可以包括UE1的更新后的层2标识，UE1接收到连接标识更新响应消息后，还可以确定连接标识更新响应消息中包括的UE1的更新后的层2标识与自己在连接标识更新请求消息中发送的UE1的更新后的层2标识是否相同，从而实现校验，以保证更新准确性。如果UE1校验得到二者不同，则UE1可以向relay发送拒绝消息，不执行下面的步骤。如果相同，则继续执行。
可选地，连接标识更新响应消息中还可以包括LSB of Key-sess ID、UE2的更新后的应用标识等。
S705、UE1将本地存储的relay的更新前的层2标识(relay old layer-2 ID)替换为relay的更新后的层2标识，UE1的更新前的IP(old UE1 IP)替换为UE1的更新后的IP。
S706、UE1向relay发送连接标识更新确认消息。
其中，连接标识更新确认消息用于指示UE1已将本地存储的UE1的更新前的IP替换为UE1的更新后的IP，或者UE1已接收UE1的更新后的IP。
可选的，UE1向relay发送的连接标识更新确认消息中还可以包括UE1的更新后的IP。relay接收到连接标识更新确认消息后，还可以确定连接标识更新确认消息中包括的UE1的更新后的IP与自己在连接标识更新响应消息中发送的UE1的更新后的IP是否相同，从而实现进一步校验，以保证更新准确性。如果relay校验得到二者不同，则relay可以向UE1发送拒绝消息，不执行下面的步骤。如果相同，则继续执行。
类似地，UE1向relay发送的连接标识更新确认消息中还可以包括relay的更新后的层2标识。relay接收到连接标识更新确认消息后，还可以确定连接标识更新确认消息中包括的relay的更新后的层2标识与自己在连接标识更新响应消息中发送的relay的更新后的层2标识是否相同，从而实现进一步校验，以保证更新准确性。如果relay校验得到二者不同，则relay可以向UE1发送拒绝消息，不执行下面的步骤。如果相同，则继续执行。
S707、relay将本地存储的UE1的更新前的层2标识(UE1 old layer-2 ID)替换为UE1的更新后的层2标识，UE1的更新前的IP替换为UE1的更新后的IP。
上述图7所示的过程完成了UE1与UE2之间更新后的层2标识的共享，以及UE1的IP的更新。后续，relay将保存UE1的更新后的层2标识与UE1的更新后的IP之间的对应关系，根据该对应关系为UE1和其他设备(如：UE3)提供通信服务。
可选的，relay将本地存储的UE1的更新前的层2标识(UE1 old layer-2 ID)替换为UE1的更新后的层2标识的动作可以发生在relay生成UE1的更新后的层2标识之后的任意步骤，不做限制。例如在S707执行，或者在S703后执行。
可选的，relay将本地存储的UE1的更新前的IP替换为UE1的更新后的IP的动作可以发生在relay生成UE1的更新后的IP之后的任意步骤，不做限制。例如在S707执行，或者在S703后执行。
可选的，上述Key-session ID可替换为Key ID，即执行Key ID的更新。
可选地，relay还可以将UE1的上下文中UE1的更新前的IP替换为UE1的更新后的IP。
可选地，上述图7所示的路由信息更新方法中，UE1向relay发送的连接标识更新请求消息中还可以包括UE1的更新前的IP，可以用于relay确定UE1之前的IP地址。
一些实施例中，UE1的IP包括：第一IP和第二IP；第一IP是UE1与relay直接通信时所使用的IP，第二IP是UE1使用relay的中继功能时所使用的IP。这里，第二IP是relay为UE1颁发的IP，第一IP是由UE自己生成的IP。UE1向relay发送的连接标识更新请求消息中还可以包括更新指示，可以用于指示relay对第二IP进行更新。relay可以根据更新指示，执行第二IP的更新。此时，relay向UE1发送的连接标识更新响应消息中包括的UE1的更新后的IP即是指更新后的第二IP。
当然可以理解的是，本申请实施例中，UE1也可以将自己生成的第一IP发送给relay，用于UE1和relay之间直接进行通信。
在一种可能的设计中，UE1向relay发送的连接标识更新请求消息中还可以包括UE1的更新前的层2标识、以及relay的更新前的层2标识，可以用于relay确定连接标识更新请求消息的发送者身份。例如，当有一个或多个UE1使用relay的中继功能时，relay可以根据连接标识更新请求消息中包括的UE1的更新前的层2标识、以及relay的更新前的层2标识，确定是前述一个或多个UE1中的哪一个发送的连接标识更新请求消息。
可选地，对于上述图7所示的实施例而言，relay还可以在接收到第一消息后，对relay的IP进行更新，并将relay的更新后的IP发送给UE1。例如，上述连接标识更新响应消息中还可以包括relay的更新后的IP(new relay IP)。UE1可以将本地存储的relay的更新前的IP(old relay IP)替换为接收到的relay的更新后的IP。可选的，UE1通过S706发送relay的更新后的IP给relay，以使relay校验步骤S704中发送的relay的更新后的IP与步骤S706中relay的更新后的IP是否相同，从而实现进一步校验，以保证更新准确性。如果relay校验得到二者不同，则relay可以向UE1发送拒绝消息，不执行下面的步骤。如果相同，则继续执行。
可选地，上述图7主要说明了UE1如何触发实现对UE1与relay之间的连接进行更新。也有一些实施例中，UE1与relay之间的连接更新也可以是由relay主动触发。例如，在上述图7所示的实施例中，可以没有S701的步骤，直接由relay主动触发更新(具体触发原因可以参考上述UE1触发的描述)，生成UE1的更新后的IP，并发送给UE1。具体原理与图7类似，不再赘述。
上述图7所示的实施例可以适用于前述图1所示的场景，也可以适用于前述图2所示的场景。
对于上述图2所示的场景，即UE1通过relay与UE3进行通信的场景而言，该路由信息方法在上述图7所示的基础上还包括将UE1的更新后的IP通知给UE3的步骤。例如，图8示出了本申请实施例提供的路由信息更新方法的又一流程示意图。如图8所示，该路由信息更新方法在前述图7所示的基础上，还可以包括S801-S802。
S801、relay向UE3发送UE1的更新后的IP。
可选地，虽然图8中示出的S801是在S707之后，但实际上，S801可以是在S703之后的任意时刻执行，如：可以是在S704之后，或者与S704同时执行等，在此不作限制。在S706之后执行，可以确保UE1已经正确接收了UE1的更新后的IP之后，再触发执行S801。可以进一步解释为，relay可以确保UE1未来会使用UE1的更新后的IP的情况下，再通知其他终端，如UE3。
可选的，relay会发送UE1的更新前的IP，用于UE3确定需要更新哪一个终端的IP 信息。
S802、UE3将本地存储的UE1的更新前的IP替换为UE1的更新后的IP。
可选地，UE3将本地存储的UE1的更新前的IP替换为UE1的更新后的IP后，也可以向relay发送一个确认消息，用于通知relay其已完成替换，或者已接收UE1的更新后的IP。
可选的，UE3根据UE1的更新前的IP确定UE1信息，再执行替换。
可选的，UE3向relay发送的UE1的更新后的IP。relay接收到确认消息后，还可以确定S801中UE1的更新后的IP与S802中发送的UE1的更新后的IP是否相同，从而实现进一步校验，以保证更新准确性。如果relay校验得到二者不同，则relay可以向UE1发送拒绝消息，不执行下面的步骤。如果相同，则继续执行。
后续，UE3将会根据UE1的更新后的IP，向UE1发送数据。
在一种可能的设计中，当UE1通过relay与多个UE3进行通信时，UE1可以向relay发送目标UE3的更多的标识信息(如：称为第四终端的标识信息，第四终端包括与UE1通信的UE3)，relay可以根据目标UE3的标识信息，向目标UE3发送UE1的更新后的IP。目标UE3即是指与UE1通过relay进行通信多个UE3中的UE3。换言之，S801中，relay向哪个UE3发送UE1的更新后的IP，是根据来自UE1的指示确定的，UE1可以通过向relay发送目标UE3的标识信息进行指示。例如，UE1可以通过前述连接标识更新请求消息向relay发送目标UE3的标识信息。
其中，目标UE3的标识信息可以包括：目标UE3的IP、目标UE3的应用标识、目标UE3的层2标识等，在此不作限制。目标UE3可以是UE1希望与之通信的UE3。
本设计中，考虑了按需的更新。只有需要与UE1通信的UE3才能够获得UE1的更新后的IP，能够避免额外通知每一个UE3的操作。
或者，在另外一种可能的设计中，relay也可以根据本地保存的与UE1有历史通信的目标UE3的标识信息，根据此UE3的标识信息向目标UE3发送UE1的更新后的IP。
又或者，在又一种可能的设计中，可能由一个专有的或者公共的relay，relay与UE3之间的连接和UE1与relay之间的连接有映射。此时relay可以根据UE1发送的连接标识更新请求消息中标识这个连接的标识(如上述UE1 layer-2 ID、old UE1 IP等)确定UE1与relay之间的连接，进而确定对应relay和UE3之间的连接，以及目标UE3的标识信息，从而确定向对应的UE3发送UE1的更新后的IP。
类似地，对于上述图1所示的场景，即UE1通过relay与网络设备，如：gNB，进行通信的场景而言，当网络设备需要知道UE1的IP时，该路由信息方法在上述图7所示的基础上，也可以包括将UE1的更新后的IP通知给网络设备的步骤，与图8类似，不再赘述。或者，当网络设备不需要知道UE1的IP时，该路由信息方法不包括将UE1的更新后的IP通知给网络设备的步骤。
上述图8所示的实施例中，是由relay将UE1的更新后的IP通知给UE3。在另外一些实施例中，也可以是由UE1将UE1的更新后的IP通过relay透传给UE3。例如，图9示出了本申请实施例提供的路由信息更新方法的又一流程示意图。如图9所示，该路由信息更新方法在前述图7所示的基础上，还可以包括S901-S902。
S901、UE1通过relay向UE3发送UE1的更新后的IP。
可选地，S901中，UE1可以通过relay向希望与之通信的目标UE3透传UE1的更新后的IP。或者，也可以向全部的历史通信的UE3透传UE1的更新后的IP。
还可以理解为，UE1通过relay发送消息至UE3，在逻辑上UE1与UE3是直接互通的。这里relay就是代理，直接路由UE1发送的数据给UE3。还可以理解为relay不会修改其中的内容。
可选地，虽然图9中示出的S901是在S707之后，但实际上，S901可以是UE1接收到连接标识更新响应消息之后的任意时刻执行，如：可以是与S705同时执行，在此不作限制。即可以理解为UE1确定接收relay分发的UE1更新后的IP之后，再触发执行S901向UE3发送UE1更新后的IP。
可选的，S901携带UE1的更新前的IP信息。用于标识发送者UE1的身份。
S902、UE3将本地存储的UE1的更新前的IP替换为UE1的更新后的IP。
可选地，UE3将本地存储的UE1的更新前的IP替换为UE1的更新后的IP后，也可以向relay和/或UE1发送一个确认消息，用于通知relay和/或UE1其已完成替换，或者已接收UE1的更新后的IP。
这里UE3根据步骤S901携带的UE1前的IP信息，确定将本地存储的UE1的更新前的IP替换为S901中携带的UE1的更新后的IP。
可选的，S901消息支持采用完整性保护机制。可以为基于UE1与UE3之间共享密钥执行的端到端的完整性保护机制。当前仅当，UE3采用其与UE1之间共享秘钥校验S901完整性保护通过之后，才执行替换动作。
可选的，S901消息支持采用完整性保护机制。可以为基于UE1与relay之间共享密钥，和relay与UE3之间共享密钥执行的分段的完整性保护机制。当前仅当，UE3采用其与relay之间共享秘钥校验接收到的S901完整性保护通过之后，才执行替换动作。
图9所示的实施例中，也考虑了按需的更新。只有需要与UE1通信的UE3才能够获得UE1的更新后的IP，能够避免额外通知每一个UE3的操作。
上述实施例主要说明了对UE1的IP和连接标识进行更新的方法。但是，在某些场景下，如果UE1与relay之间的连接标识更新了，而relay与UE3之间的标识没有变，那么假设relay与UE3之间的连接是专为UE1传递数据给UE3的，则通过relay与UE3之间没有变的连接标识，关联到UE1与relay之间的新旧标识，如：UE1的更新后的层2标识。例如，一些消息格式中，UE1旧的数据包为：UE1旧标识||UE3的标识；更新后，UE1新的数据包为：UE1新标识||UE3的标识。那么攻击者可以根据相同的UE3的标识，确定UE1旧标识和UE1新标识是属于同一个UE1的。这意味着，即使UE1与relay之间连接更新了，攻击者仍旧可以执行关联攻击。
对此，本申请实施例提供的该路由信息更新方法在前述实施例的基础上，还可以包括对UE3的路由信息、以及UE3与relay之间的连接标识进行更新的步骤。可以适用于relay与UE3之间的连接是专为UE1传递数据给UE3(即relay与UE3之间的连接是专用连接)的场景，也可以适用于relay与UE3之间的连接是共用连接的场景，具体适用的场景并不作限制。
举例说明，图10示出了专用连接的示意图。如图10所示，UE1与relay之间的连接为1，UE4与relay之间的连接为3，relay与UE3之间的连接为2和4。其中，1与2绑定，3与4绑定。也即，2是专为1服务的，4是专为3服务的。那么当UE1与relay之间的连接1更新时，2也必须更新。
图11示出了共用连接的示意图。如图11所示，UE1与relay之间的连接为1，UE4与relay之间的连接为3，relay与UE3之间的连接为2。其中，2可以为1服务，也可以 为3服务，即，relay与UE3之间的连接2是共用的。那么当UE1与relay之间的连接1更新时，2可以更新，也可以不更新。
下面结合图12对UE3的路由信息、以及UE3与relay之间的连接标识进行更新的步骤进行示例性说明。图12示出了本申请实施例提供的路由信息更新方法的又一流程示意图。如图12所示，该路由信息更新方法在前述图7-图9任一所示(以图7为例)的基础上，还可以包括S1201-S1206。该方法中，UE3的IP的更新过程也可以是在UE3与relay之间的连接标识的更新过程中实现的。
S1201、relay触发执行relay与UE3之间连接的更新，生成relay的更新后的层2标识(relay new layer-2 ID)，以及对UE3的IP进行更新，生成UE3的更新后的IP(new UE3 IP)。
其中，S1201中所述的relay的更新后的层2标识与前述图7所示的实施例中所述的relay的更新后的层2标识可以相同，也可以不同，不作限制。
可选地，relay触发执行relay与UE3之间连接的更新可以是relay根据第一消息或者第一消息中的更新指示，又或者根据UE1发送的ACK消息，确定UE1已经完成了更新之后，执行relay与UE3之间连接的更新。
可选的，relay可以根据其与UE3之间连接是专用连接，还是公用连接确定是否要执行更新。如果是专用连接，就触发执行S1201的更新流程。如果是公用连接，就不需要触发执行S1201的更新流程。
S1202、relay向UE3发送连接标识更新请求消息，连接标识更新请求消息包括：relay的更新后的层2标识、UE3的更新后的IP。
相应地，UE3接收连接标识更新请求消息。需注意的是，此处的连接标识更新请求消息与前述实施例中所述的UE1发送给relay的连接标识更新请求消息不同。
S1203、UE3生成UE3的更新后的层2标识。
S1204、UE3向relay发送连接标识更新响应消息，连接标识更新响应消息包括：UE3的更新后的层2标识。
相应地，relay接收连接标识更新响应消息。需注意的是，此处的连接标识更新请求消息与前述实施例中所述的relay发送给UE1的连接标识更新请求消息不同。
可选地，relay将本地存储的UE3的更新前的层2标识替换为UE3的更新后的层2标识。
这里，可选地，UE3向relay发送的连接标识更新响应消息中还可以包括relay的更新后的层2标识和/或UE3的更新后的IP，relay接收到连接标识更新响应消息后，还可以确定连接标识更新响应消息中包括的relay的更新后的层2标识和/或UE3的更新后的IP与自己在连接标识更新请求消息中发送的relay的更新后的层2标识和/或UE3的更新后的IP是否相同，从而实现校验，以保证更新准确性。如果relay校验得到二者不同，则relay可以向UE3发送拒绝消息，不执行下面的步骤。如果相同，则继续执行。
S1205、relay向UE3发送连接标识更新确认消息。
需注意的是，此处的连接标识更新确认消息与前述实施例中所述的UE1发送给relay的连接标识更新确认消息不同。
这里，可选地，relay向UE3发送的连接标识更新确认消息中还可以包括UE3的更新后的层2标识，UE3接收到连接标识更新确认消息后，还可以确定连接标识更新确认消息中包括的UE3的更新后的层2标识与自己在连接标识更新响应消息中发送的UE3 的更新后的层2标识是否相同，从而实现校验，以保证更新准确性。如果UE3校验得到二者不同，则UE3可以向relay发送拒绝消息，不执行下面的步骤。如果相同，则继续执行。
S1206、UE3将本地存储的relay的更新前的层2标识替换为relay的更新后的层2标识，UE3的更新前的IP替换为UE3的更新后的IP。
可选地，S1206也可以是在S1202之后的其他任意时刻执行，并不限定于S1205之后。
上述图12所示的实施例中，还可以包括relay向UE1通知UE3的更新后的IP的步骤，用于向UE1通知UE3最新的IP地址。这里可以为S1204后触发向UE1发送更新后的IP的步骤。可选的，relay校验S1204完整性保护成功之后，向UE1发送。UE1可以将UE3的更新前的IP替换为UE3的更新后的IP。该步骤与上述图8或图9中所示的relay将UE1的更新后的IP通知给UE3的步骤，或者UE1将UE1的更新后的IP通过relay透传给UE3的方式类似，在此不再赘述。
另外，上述图12所示的实施例中，对UE3的IP、以及UE3与relay之间的连接标识进行更新过程，是由对UE1的IP、以及UE1与relay之间的连接标识的更新所触发的，基于这样的理解，上述图12所述的步骤是在relay接收到来自UE1的连接标识更新请求消息后执行的，具体并不限定再之后的哪一步开始执行，前述图示均仅为示例性说明。
与前述实施例中向UE3通知UE1的更新后的IP的方式类似，对于图12所示的场景，在一种可能的设计中，当UE1通过relay与多个UE3进行通信时，UE1可以向relay发送目标UE3的标识信息，relay可以根据目标UE3的标识信息，向目标UE3发送连接标识更新请求消息。目标UE3即是指与UE1通过relay进行通信多个UE3中的UE3。换言之，S1202中，relay向哪个UE3发送UE1的更新后的IP，是根据来自UE1的指示确定的，UE1可以通过向relay发送目标UE3的标识信息进行指示。例如，UE1可以通过前述连接标识更新请求消息向relay发送目标UE3的标识信息。目标UE3的标识信息具体可以参考前述实施例所述。
本设计中，同样考虑了按需的更新。只有需要与UE1通信的UE3才能够获得UE1的更新后的IP，能够避免额外通知每一个UE3的操作。
或者，在另外一种可能的设计中，relay也可以根据本地保存的与UE1有历史通信的目标UE3，向目标UE3发送连接标识更新请求消息。又或者，在又一种可能的设计中，对于上述图10所示的专用连接而言，relay与UE3之间的连接和UE1与relay之间的连接有映射。此时relay可以根据UE1发送的连接标识更新请求消息中标识这个连接的标识(如上述UE1 layer-2 ID、old UE1 IP等)确定UE1与relay之间的连接，进而确定对应relay和UE3之间的连接，从而确定向对应的UE3发送连接标识更新请求消息。
可选地，对于上述图12所示的过程，可以由relay根据其与UE1之间PC5接口的保护方式来确定是否执行。例如，relay与UE1之间数据保护没有开启加密保护，那么可以按照图12所示的实施例需要触发后续更新操作。如果开了加密保护，那么攻击者通过PC5口是看不到UE1与UE3之间端到端数据的参数(例如，IP)，那么就不能根据暴露出来的UE1与UE3之间的参数完成UE1与relay之间新旧标识的关联，此时，relay可以不需要触发后续的更新操作，当然，如果开了加密保护，relay也可以根据其他本地策略，确定是否触发后续更新，在此并不作限制。
上述图12主要说明了在UE1与relay之间的连接更新的情况下，relay如何触发实现 relay与UE3之间的连接更新。也有一些实施例中，relay与UE3之间的连接更新也可以是由UE3发起的。例如，在上述图9所示的实施例中，由UE1将UE1的更新后的IP通过relay透传给UE3的场景下，UE3可以主动向relay发起连接更新的触发请求消息，进行后续的更新。
下面结合图13对UE3可以主动向relay发起连接更新的触发请求消息，如：称为第四消息，进行后续的更新的过程进行示例性说明。图13示出了本申请实施例提供的路由信息更新方法的又一流程示意图。如图13所示，该路由信息更新方法在前述图9所示的基础上，还可以包括S1301-S1307。
S1301、UE3向relay发送第四消息，第四消息用于指示relay对UE3的IP进行更新。
相应地，relay接收第四消息。
此时，UE3与relay的连接被触发执行更新，这里触发更新的过程可以参考上面relay触发的动作。
S1302、relay生成relay的更新后的层2标识，以及对UE3的IP进行更新，生成UE3的更新后的IP。
S1303、relay向UE3发送连接标识更新请求消息，连接标识更新请求消息包括：relay的更新后的层2标识、UE3的更新后的IP。
S1304、UE3生成UE3的更新后的层2标识。
S1305、UE3向relay发送连接标识更新响应消息，连接标识更新响应消息包括：UE3的更新后的层2标识。
relay会用UE3的更新后的层2标识替换掉本地存储的UE3的更新前的层2标识。
S1306、relay向UE3发送连接标识更新确认消息。
S1307、UE3将本地存储的relay的更新前的层2标识替换为relay的更新后的层2标识，UE3的更新前的IP替换为UE3的更新后的IP。
上述S1302-S1307与前述S1201-S1206相同，在此不再赘述。
上述也可以UE3直接生成UE3的更新后的层2标识，在S1301中发送UE3的更新后的层2标识给relay触发执行更新。步骤类似于S701-706，此时UE3直接触发执行更新。
上述图13所示的实施例中，同样还会包括向UE1通知UE3的更新后的IP的步骤，用于向UE1通知UE3最新的IP地址。这里可以为UE3通知UE1，或者relay通知UE1；不做限制。UE1可以将UE3的更新前的IP替换为UE3的更新后的IP。该步骤同样与上述图8或图9中所示的relay将UE1的更新后的IP通知给UE3的步骤，或者UE1将UE1的更新后的IP通过relay透传给UE3的方式类似，在此亦不再赘述。
可选地，对于上述图1所示的场景，即UE1通过relay与网络设备，如：gNB，进行通信的场景而言，该路由信息方法在上述图7所示的基础上还包括对为UE1提供数据传输的空口的标识信息进行更新的步骤。例如，UE1与gNB之间有端到端的保护机制时，需要更新UE1与gNB之间端到端的可以用来标识UE1的参数。
以图14为例，图14示出了本申请实施例提供的路由信息更新方法的又一流程示意图。如图14所示，该路由信息更新方法在前述图7所示的基础上，还可以包括S1401-S1403。
S1401、relay向gNB发送第一无线资源控制(radio resource control，RRC)消息，第一RRC消息包括为UE1提供数据传输的空口的标识信息，第一RRC消息用于指示gNB对标识信息进行更新。
相应地，gNB接收第一RRC消息。
可选地，relay可以根据UE1发送的UE1 IP或者UE1 layer-2 ID，来确定为UE1提供数据传输的空口(也称无线承载)，以生成第一RRC消息。
这里，第一RRC消息是relay对UE1的IP进行更新后发送的消息。换言之，图14所示的步骤是在图7中所示的步骤之后执行的。可以理解为，relay在确定UE1完成UE1的IP更新成功之后，触发执行S1401的更新。
可选地，第一RRC消息中也可以携带更新指示，用于指示gNB对为第一终端提供数据传输的空口的标识信息进行更新。或者，第一RRC消息也可以是其他特殊的能够用于指示gNB对为第一终端提供数据传输的空口的标识信息进行更新的消息类型，在此不作限制。
S1402、gNB根据第一RRC消息，对为第一终端提供数据传输的空口的标识信息进行更新，生成更新后的标识信息。
可选的，gNB可以根据第一RRC消息中携带的更新指示或者消息类型确定要执行空口的标识信息更新。
可选地，更新后的标识信息可以包括：新的小区无线网络标示(cell access radio network temporary identifier，C-RNTI)、新的RRC Counter、新的空口(或承载)标识、新的频谱标识、新的分组数据汇聚层协议(packet data convergence protocol，PDCP)序列号(sequence number，SQN)或者counter(可以从0开始，或者随机选择)、新的其他标识此空口标识的ID等，在此不作限制。
S1403、gNB向relay发送第二RRC消息，第二RRC消息包括更新后的标识信息。
相应的，relay接收第二RRC消息。
可选的，第二RRC消息也可以称为RRC重配置消息。
后续，relay可以根据更新后的标识信息，选择对应的为第一终端提供数据传输的空口，向gNB传输UE1的数据。
当然，在此之前，relay会将本地存储的为第一终端提供数据传输的空口的更新前的标识信息替换为更新后的标识信息，不再赘述。之后，relay还可以向gNB返回响应消息或确认消息，用于通知gNB其已完成替换。
一些实施例中，relay还可以将第二RRC消息包括的更新后的标识信息发送给UE1，UE1可以根据更新后的标识信息刷新UE1与gNB之间的参数。例如，采用新的PDCP SQN或者counter替换已有的PDCP SQN或者counter，或者采用新的承载标识来替换旧的承载标识等，其他替换操作不在赘述。这里承载标识可以为用来执行PDCP层保护时采用的参数。
图14所示的实施例能够触发执行空口Uu无线标识的更新，避免攻击者可以根据relay与网络设备之间已有的无线承载标识来关联UE与relay之间新旧的标识。
可选地，对于上述图14所示的过程，也可以由relay根据其与UE1之间PC5接口的保护方式来确定是否执行。例如，relay与UE1之间数据保护没有开启加密保护，那么可以按照图14所示的实施例需要触发后续更新操作；如果开了加密保护，那么攻击者通过PC5口是看不到UE1与gNB之间端到端数据的参数(例如,PDCP SQN或counter，空口标识等)，那么就不能根据暴露出来的UE1与gNB之间的参数完成UE1与relay之间新旧标识的关联，此时，relay可以不需要触发后续的更新操作，当然，如果开了加密保护，relay也可以根据其他本地策略，确定是否触发后续更新，在此并不作限制。
还一种可能性为，如果执行的保护为UE与gNB之间的端到端的保护机制(以PDCP保护为例进行描述)。那么此时需要将更新后的用于端到端保护的参数通知给UE1(以PDCP为例，这里可以为承载标识)。
因此，那么还一种可能性为relay侧触发更新的流程，即不包括步骤S701-S707。由relay直接触发空口的更新，可以参考S1401内容，relay根据本地策略等触发执行空口标识的更新，发送更新前的承载标识至gNB，并从gNB得到更新后的承载标识(可选的，可以采用RRC重配置消息)。此时relay需要根据更新前的承载标识确定对应的UE1，并且向UE1发送更新后的承载标识。可以理解UE1在使用relay功能的时候，发送给relay数据后，relay会采用此承载标识对应的空口承载传递UE1的数据给基站。因此，relay需要向UE1发送更新后的承载标识。此时UE1与gNB之间才能共享更新后的承载标识。之后UE1与gNB使用更新后的承载标识进行UE1与gNB之间端到端的PDCP层保护。
还一种可能性为，gNB侧触发更新的流程，即不包括步骤S701-S707，以及S1401。由gNB直接触发空口的更新，gNB根据本地策略等触发执行空口标识的更新，发送更新后的承载标识给relay(可选的，可以采用RRC重配置消息；可选的，还可以发送更新前的承载标识)。此时relay接收更新后的承载标识(可选的，还有更新前的承载标识)。Relay可以根据更新后承载标识自己确定更新前的承载标识(例如当只有一个承载的时候，或者根据其他参数(例如会话标识等不做限制)确定更新前的承载标识)，或者Relay根据接收到的更新前的承载标识确定对应的UE1，并且向UE1发送更新后的承载标识。此时UE1与gNB之间才能共享更新后的承载标识。之后UE1与gNB使用更新后的承载标识进行UE1与gNB之间端到端的PDCP层保护。
还一种可能性为，gNB切换时触发承载标识更新的流程，即不包括步骤S701-S707，以及S1401。源gNB根据本地策略触发执行gNB之间的切换，由源gNB切换至目标gNB，并从目标gNB接收到更新后的承载标识。源gNB发送更新后的承载标识给relay(可选的，可以采用RRC重配置消息；可选的还可以发送更新前的承载标识)。此时relay接收更新后的承载标识(可选的，还有更新前的承载标识)。Relay可以根据更新后承载标识自己确定更新前的承载标识(例如当只有一个承载的时候，或者根据其他参数(例如会话标识等不做限制)确定更新前的承载标识)，或者Relay根据接收到的更新前的承载标识确定对应的UE1，并且向UE1发送更新后的承载标识。此时UE1与gNB之间才能共享更新后的承载标识。之后UE1与gNB使用更新后的承载标识进行UE1与gNB之间端到端的PDCP层保护。
还需要进一步说明的是，本申请前述实施例中层2标识相关的内容可以为可选的内容，即上述提到的生成，发送和校验的过程可以仅包括路由信息的处理。
另外，可选的本申请前述实施例中每个消息都是执行了完整性保护。发送者(例如UE1)在发送消息之前，会采用与接收方(例如relay)共享的密钥执行完整性保护；接受者接收到消息之后，会采用与发送方共享的密钥进行完整性保护的校验。当校验通过之后，才会执行后续的操作。如果校验不通过，则发送拒绝消息至发送方。其中一个例外为，图13中，UE1通过relay发送S901消息给UE3的场景时，此时S901的内容是直接发送给UE3，因此逻辑上发送方和接收方为UE1和UE3。此时S901的保护密钥是UE1与UE3之间共享的。
还需要说明的是，本申请前述实施例中，关于IP的更新仅为示例性说明，本申请实施例提供的该路由信息更新方法同样适用于其他可以用于路由的标识的更新，如：层2 标识(layer-2 ID)路由、又或者其他non-IP路由，例如，MAC信息，私网地址等。另外，除了前述路由信息外，本申请实施例中对其他可能会泄露的UE的新的标识也会进行更新，例如，UE的应用标识等。此部分描述均以在前述实施例中可选地方式中进行体现，不再进行赘述。
上述主要从各个网元之间交互的角度对本申请实施例提供的方案进行了介绍。可以理解的是，第一终端(如：UE1)、第二终端(如：UE2)、第三终端(如：UE3)、网络设备(如：gNB)等，为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。
如：本申请实施例还可以提供一种可以应用于第一终端的通信装置。图15示出了本申请实施例提供的通信装置的结构示意图。如图15所示，该通信装置包括：处理单元1501和收发单元1502。处理单元1501和收发单元1502用于实现前述实施例中所述的第一终端执行的步骤。例如：收发单元1502用于实现第一终端的S401、S405、S702、S706、S901等发送功能、以及其他未用步骤体现的接收功能。处理单元1501用于实现第一终端的S404、S701、S705等数据处理功能。
需要说明的是，此处并未一一列举前述实施例中第一终端的全部功能，但应当理解，前述实施例中所述的第一终端的发送和接收功能，均可以通过收发单元1502实现。第一终端的数据处理功能，如：生成第一终端的更新后的层2标识、执行IP的替换操作等，均可以通过处理单元1501实现，此处不再详细描述。
类似地，本申请实施例还可以提供一种应用于第二终端的通信装置。图16示出了本申请实施例提供的通信装置的另一结构示意图。如图16所示，该通信装置包括：处理单元1601和收发单元1602。处理单元1601和收发单元1602用于实现前述实施例中所述的第二终端执行的步骤。例如：收发单元1602用于实现第二终端的S403、S405、S704、S801、S1202、S1205、S1303、S1306、S1401等发送功能、以及其他未用步骤体现的接收功能。处理单元1601用于实现第二终端的S402、S406、S703、S707、S1201、S1302等数据处理功能。
这里同样并未一一列举前述实施例中第二终端的全部功能，应当理解，前述实施例中所述的第二终端的发送和接收功能，均可以通过收发单元1602实现。第二终端的数据处理功能，如：生成第二终端的更新后的层2标识、执行IP的替换操作等，均可以通过处理单元1601实现，此处不再详细描述。
类似地，本申请实施例还可以提供一种应用于第一设备的通信装置。图17示出了本申请实施例提供的通信装置的又一结构示意图。如图17所示，该通信装置包括：处理单元1701和收发单元1702。
当第一设备是上述第三终端(如UE3)时，处理单元1701和收发单元1702用于实现前述实施例中所述的第三终端执行的步骤。例如：收发单元1702用于实现第三终端的S1204、S1301、S1305等发送功能、以及其他未用步骤体现的接收功能。处理单元1701用于实现第三终端的S902、S1203、S1206、S1304、S1307等数据处理功能。
当第一设备是上述网络设备(如gNB)时，处理单元1701和收发单元1702用于实现前述实施例中所述的网络设备执行的步骤。例如：收发单元1702用于实现网络设备的S1403等发送功能、以及其他未用步骤体现的接收功能。处理单元1701用于实现网络设备的S1402等数据处理功能。
需要说明的是，此处也未一一列举前述实施例中第一设备的全部功能，但应当理解， 前述实施例中所述的第一设备的发送和接收功能，均可以通过收发单元1702实现。第一设备的数据处理功能均可以通过处理单元1701实现，此处不再详细描述。
应理解以上装置中单元的划分仅仅是一种逻辑功能的划分，实际实现时可以全部或部分集成到一个物理实体上，也可以物理上分开。且装置中的单元可以全部以软件通过处理元件调用的形式实现；也可以全部以硬件的形式实现；还可以部分单元以软件通过处理元件调用的形式实现，部分单元以硬件的形式实现。
例如，各个单元可以为单独设立的处理元件，也可以集成在装置的某一个芯片中实现，此外，也可以以程序的形式存储于存储器中，由装置的某一个处理元件调用并执行该单元的功能。此外这些单元全部或部分可以集成在一起，也可以独立实现。这里所述的处理元件又可以称为处理器，可以是一种具有信号的处理能力的集成电路。在实现过程中，上述方法的各步骤或以上各个单元可以通过处理器元件中的硬件的集成逻辑电路实现或者以软件通过处理元件调用的形式实现。
在一个例子中，以上任一装置中的单元可以是被配置成实施以上方法的一个或多个集成电路，例如：一个或多个ASIC，或，一个或多个DSP，或，一个或者多个FPGA，或这些集成电路形式中至少两种的组合。
再如，当装置中的单元可以通过处理元件调度程序的形式实现时，该处理元件可以是通用处理器，例如CPU或其它可以调用程序的处理器。再如，这些单元可以集成在一起，以片上系统(system-on-a-chip，SOC)的形式实现。
以上用于接收的单元是一种该装置的接口电路或者输入电路，用于从其它装置接收信号。例如，当该装置以芯片的方式实现时，该接收单元是该芯片用于从其它芯片或装置接收信号的接口电路或者输入电路。当通信装置包括用于发送的单元时，该用于发送的单元是一种该装置的接口电路或者输出电路，用于向其它装置发送信号。例如，当该装置以芯片的方式实现时，该发送单元是该芯片用于向其它芯片或装置发送信号的接口电路或者输出电路。
例如，本申请实施例还可以提供一种通信装置，可以应用于第一终端、第二终端、以及第一设备中的任意一种。该通信装置可以包括：处理器和接口电路。该处理器可以包括一个或多个。
当该通信装置应用于第一终端、第二终端、或者第一设备时，处理器用于通过接口电路与其它装置通信，并执行以上方法中第一终端、第二终端、或者第一设备对应执行的各个步骤。
在一种实现中，第一终端、第二终端、或者第一设备分别实现以上方法中各个对应步骤的单元可以通过处理元件调度程序的形式实现。例如，用于第一终端、第二终端、或者第一设备的装置可以包括处理元件和存储元件，处理元件调用存储元件存储的程序，以执行以上方法实施例中对应第一终端、第二终端、或者第一设备执行的方法。存储元件可以为与处理元件处于同一芯片上的存储元件，即片内存储元件。
在另一种实现中，用于执行以上方法中第一终端、第二终端、或者第一设备所执行的方法的程序可以在与处理元件处于不同芯片上的存储元件，即片外存储元件。此时，处理元件从片外存储元件调用或加载程序于片内存储元件上，以调用并执行以上方法实施例中对应第一终端、第二终端、或者第一设备执行的方法。
例如，本申请实施例还可以提供一种通信装置，该通信装置可以包括处理器，用于执行存储器中存储的计算机指令，当所述计算机指令被执行时，使得所述装置执行以上 第一终端、第二终端、或者第一设备所执行的方法。该存储器可以位于该通信装置之内，也可以位于该通信装置之外。且该处理器包括一个或多个。
在又一种实现中，第一终端、第二终端、或者第一设备实现以上方法中各个步骤的单元可以是被配置成一个或多个处理元件，这些处理元件可以设置于对应第一终端、第二终端、或者第一设备上，这里的处理元件可以为集成电路，例如：一个或多个ASIC，或，一个或多个DSP，或，一个或者多个FPGA，或者这些类集成电路的组合。这些集成电路可以集成在一起，构成芯片。
第一终端、第二终端、或者第一设备实现以上方法中各个步骤的单元可以集成在一起，以SOC的形式实现，该SOC芯片，用于实现对应的方法。该芯片内可以集成至少一个处理元件和存储元件，由处理元件调用存储元件的存储的程序的形式实现对应的方法；或者，该芯片内可以集成至少一个集成电路，用于实现对应的方法；或者，可以结合以上实现方式，部分单元的功能通过处理元件调用程序的形式实现，部分单元的功能通过集成电路的形式实现。
这里的处理元件同以上描述，可以是通用处理器，例如CPU，还可以是被配置成实施以上方法的一个或多个集成电路，例如：一个或多个ASIC，或，一个或多个微处理器DSP，或，一个或者多个FPGA等，或这些集成电路形式中至少两种的组合。
存储元件可以是一个存储器，也可以是多个存储元件的统称。
例如，本申请实施例还提供一种芯片系统，该芯片系统可以应用于上述第一终端、第二终端、或者第一设备中的任意一种。芯片系统包括一个或多个接口电路和一个或多个处理器；接口电路和处理器通过线路互联；处理器通过接口电路从电子设备的存储器接收并执行计算机指令，以实现以上方法实施例中对应第一终端、第二终端、或者第一设备所执行的方法。
通过以上的实施方式的描述，所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，仅以上述各功能模块的划分进行举例说明，实际应用中，可以根据需要而将上述功能分配由不同的功能模块完成，即将装置的内部结构划分成不同的功能模块，以完成以上描述的全部或者部分功能。
在本申请所提供的几个实施例中，应该理解到，所揭露的装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述模块或单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个装置，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是一个物理单元或多个物理单元，即可以位于一个地方，或者也可以分布到多个不同地方。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个可读取存储介质中。基于这样的理解，本申请实施例的技术方案本质上 或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，如：程序。该软件产品存储在一个程序产品，如计算机可读存储介质中，包括若干指令用以使得一个设备(可以是单片机，芯片等)或处理器(processor)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、ROM、RAM、磁碟或者光盘等各种可以存储程序代码的介质。
例如，本申请实施例还可以提供一种计算机可读存储介质，包括：计算机软件指令；当计算机软件指令在电子设备，或者内置在电子设备的芯片中运行时，可以使得电子设备执行如前述实施例所述的第一终端、第二终端、或者第一设备执行的方法。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何在本申请揭露的技术范围内的变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (24)

  1. 一种路由信息更新方法，其特征在于，所述方法包括：
    第二终端生成第一终端的路由信息，所述第二终端的中继功能基于所述第一终端的路由信息为所述第一终端与第一设备提供通信服务，所述第一设备包括第三终端和/或网络设备；
    所述第二终端对所述第一终端的路由信息进行更新，生成所述第一终端的更新后的路由信息；
    所述第二终端向所述第一终端发送第二消息，所述第二消息包括所述第一终端的更新后的路由信息；
    所述第一设备包括所述第三终端时，所述第二终端向所述第三终端发送所述第一终端的更新后的路由信息。
  2. 根据权利要求1所述的方法，其特征在于，所述第二终端对所述第一终端的路由信息进行更新之前，所述方法还包括：
    所述第二终端接收来自所述第一终端的第一消息，所述第一消息用于指示所述第二终端对所述第一终端的路由信息进行更新；
    所述第二终端对所述第一终端的路由信息进行更新，包括：
    所述第二终端根据所述第一消息，对所述第一终端的路由信息进行更新。
  3. 根据权利要求2所述的方法，其特征在于，所述第一消息是连接标识更新请求消息，所述第二消息是连接标识更新响应消息；
    所述第一消息包括所述第一终端的更新后的层2标识；
    所述方法还包括：
    所述第二终端对所述第二终端的层2标识进行更新，生成所述第二终端的更新后的层2标识；
    所述第二消息还包括所述第二终端的更新后的层2标识。
  4. 根据权利要求2或3所述的方法，其特征在于，所述第一终端的路由信息包括：第一路由信息和第二路由信息；所述第一路由信息是所述第一终端与所述第二终端直接通信时所使用的路由信息，所述第二路由信息是所述第一终端使用所述第二终端的中继功能时所使用的路由信息；
    所述第一消息包括更新指示，所述更新指示用于指示所述第二终端对所述第二路由信息进行更新；所述第一终端的更新后的路由信息是更新后的第二路由信息。
  5. 根据权利要求2-4任一项所述的方法，其特征在于，所述方法还包括：
    所述第二终端根据所述第一消息，生成第二终端的更新后的路由信息；
    所述第二消息还包括所述第二终端的更新后的路由信息。
  6. 根据权利要求2-5任一项所述的方法，其特征在于，所述第一设备包括所述网络设备时，所述方法还包括：
    所述第二终端向所述网络设备发送所述第一终端的更新后的路由信息。
  7. 根据权利要求2-6任一项所述的方法，其特征在于，所述第一消息还包括第四终端的标识信息，所述第四终端包括所述第三终端；所述方法还包括：
    所述第二终端根据所述第四终端的标识信息，向所述第四终端发送所述第一终端的更新后的路由信息。
  8. 根据权利要求2-7任一项所述的方法，其特征在于，所述方法还包括：
    所述第二终端对所述第三终端的路由信息进行更新，生成所述第三终端的更新后的路由信息；
    所述第二终端向所述第三终端以及所述第一终端发送所述第三终端的更新后的路由信息。
  9. 根据权利要求8所述的方法，其特征在于，所述第二终端对所述第三终端的路由信息进行更新，包括：
    所述第二终端接收来自所述第一终端的第一消息后，对所述第三终端的路由信息进行更新。
  10. 根据权利要求1-6任一项所述的方法，其特征在于，所述第一设备包括所述网络设备时，所述方法还包括：
    所述第二终端向所述网络设备发送第一无线资源控制RRC消息，所述第一RRC消息包括为所述第一终端提供数据传输的空口的标识信息，所述第一RRC消息用于指示所述网络设备对所述标识信息进行更新；
    所述第二终端接收来自所述网络设备的第二RRC消息，所述第二RRC消息包括更新后的标识信息。
  11. 一种路由信息更新方法，其特征在于，所述方法包括：
    第一终端生成第一消息，所述第一消息用于指示第二终端对所述第一终端的路由信息进行更新；所述第一终端使用所述第一终端的路由信息通过所述第二终端的中继功能与第一设备通信，所述第一设备包括第三终端和/或网络设备；
    所述第一终端向所述第二终端发送所述第一消息；
    所述第一终端接收来自所述第二终端的第二消息，所述第二消息包括所述第一终端的更新后的路由信息；
    所述第一终端将所述第一终端的更新前的路由信息替换为所述第一终端的更新后的路由信息。
  12. 根据权利要求11所述的方法，其特征在于，所述第一消息是连接标识更新请求消息，所述第二消息是连接标识更新响应消息；所述第一终端生成第一消息之前，所述方法还包括：
    所述第一终端对所述第一终端的层2标识进行更新，生成所述第一终端的更新后的层2标识；
    所述第一消息包括所述第一终端的更新后的层2标识；
    所述第二消息还包括所述第二终端的更新后的层2标识。
  13. 根据权利要求11或12所述的方法，其特征在于，所述第一终端的路由信息包括：第一路由信息和第二路由信息；所述第一路由信息是所述第一终端与所述第二终端直接通信时所使用的路由信息，所述第二路由信息是所述第一终端使用所述第二终端的中继功能时所使用的路由信息；
    所述第一消息包括更新指示，所述更新指示用于指示所述第二终端对所述第二路由信息进行更新；所述第一终端的更新后的路由信息是更新后的第二路由信息。
  14. 根据权利要求11-13任一项所述的方法，其特征在于，所述第二消息还包括所述第二终端的更新后的路由信息。
  15. 根据权利要求11-14任一项所述的方法，其特征在于，所述第一消息还包括第 四终端的标识信息，所述第四终端包括所述第三终端。
  16. 根据权利要求11-14任一项所述的方法，其特征在于，所述方法还包括：
    所述第一终端通过所述第二终端向第四终端发送所述第一终端的更新后的路由信息；所述第四终端包括所述第三终端。
  17. 根据权利要求11-16任一项所述的方法，其特征在于，所述方法还包括：
    所述第一终端接收来自所述第二终端的所述第三终端的更新后的路由信息。
  18. 一种路由信息更新方法，其特征在于，所述方法包括：
    第三终端使用所述第三终端的路由信息通过第二终端的中继功能与第一设备通信，所述第一设备包括第一终端和/或网络设备；
    所述第三终端接收来自所述第二终端的所述第一终端的更新后的路由信息；
    所述第三终端向所述第二终端发送用于指示所述第二终端对所述第三终端的路由信息进行更新的消息；
    所述第三终端接收来自所述第二终端的所述第三终端的更新后的路由信息。
  19. 一种路由信息更新方法，其特征在于，所述方法包括：
    网络设备通过第二终端与第一终端通信；
    所述网络设备接收来自所述第二终端的第一RRC消息，所述第一RRC消息包括为所述第一终端提供数据传输的空口的标识信息，所述第一RRC消息用于指示所述网络设备对所述标识信息进行更新；
    所述网络设备根据所述第一RRC消息，对为所述第一终端提供数据传输的空口的标识信息进行更新，生成更新后的标识信息；
    所述网络设备向所述第二终端发送第二RRC消息，所述第二RRC消息包括所述更新后的标识信息。
  20. 根据权利要求19所述的方法，其特征在于，所述网络设备接收来自所述第二终端的第一RRC消息，包括：
    所述网络设备接收所述第二终端对所述第一终端的路由信息进行更新后发送的所述第一RRC消息。
  21. 一种通信装置，其特征在于，包括：处理单元和收发单元，所述处理单元和所述收发单元共同用于实现如权利要求1-20任一项所述的方法。
  22. 一种通信装置，其特征在于，包括：处理器和接口电路，所述处理器用于通过所述接口电路与其它装置通信，并执行权利要求1-20任一项所述的方法。
  23. 一种通信装置，其特征在于，包括：处理器，用于执行存储器中存储的计算机指令，当所述计算机指令被执行时，使得所述装置执行权利要求1-20任一项所述的方法。
  24. 一种计算机可读存储介质，其特征在于，包括：计算机软件指令；
    当所述计算机软件指令在电子设备或内置在所述电子设备的芯片中运行时，使得所述电子设备执行权利要求1-20任一项所述的方法。
PCT/CN2021/108264 2020-09-30 2021-07-23 路由信息更新方法、通信装置及存储介质 Ceased WO2022068336A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP21873998.5A EP4207686A4 (en) 2020-09-30 2021-07-23 METHOD FOR UPDATING ROUTING INFORMATION, COMMUNICATION DEVICE AND STORAGE MEDIUM
US18/192,866 US20230262579A1 (en) 2020-09-30 2023-03-30 Route information update method, communication apparatus, and storage medium

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202011066067.7A CN114339942B (zh) 2020-09-30 2020-09-30 路由信息更新方法、通信装置及存储介质
CN202011066067.7 2020-09-30

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/192,866 Continuation US20230262579A1 (en) 2020-09-30 2023-03-30 Route information update method, communication apparatus, and storage medium

Publications (1)

Publication Number Publication Date
WO2022068336A1 true WO2022068336A1 (zh) 2022-04-07

Family

ID=80949620

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/108264 Ceased WO2022068336A1 (zh) 2020-09-30 2021-07-23 路由信息更新方法、通信装置及存储介质

Country Status (4)

Country Link
US (1) US20230262579A1 (zh)
EP (1) EP4207686A4 (zh)
CN (2) CN114339942B (zh)
WO (1) WO2022068336A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US12526862B1 (en) * 2024-07-10 2026-01-13 Asus Technology Licensing Inc. Method and apparatus for supporting link identifier update for UE-to-UE relay communication in a wireless communication system

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017106705A2 (en) * 2015-12-17 2017-06-22 Security Innovation, Inc Secure vehicle communication system
CN107547335A (zh) * 2016-06-27 2018-01-05 丛林网络公司 在evpn中信号通知ip地址移动的方法和网络设备
CN109150713A (zh) * 2018-08-22 2019-01-04 赛尔网络有限公司 基于bgp+源终端和目的终端之间的路由方法及路由监测方法
WO2019231818A1 (en) * 2018-05-28 2019-12-05 Qualcomm Incorporated Roll-over of identifiers and keys for unicast vehicle to vehicle communication links

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104717714A (zh) * 2013-12-17 2015-06-17 中兴通讯股份有限公司 路由信息发送、接收的方法、装置及路由信息处理系统
US9936530B2 (en) * 2015-03-10 2018-04-03 Intel IP Corporation Systems, methods, and devices for device-to-device relay communication
CN106255227A (zh) * 2015-06-11 2016-12-21 阿尔卡特朗讯 一种用于d2d中继的方法、设备与系统
CN110149674A (zh) * 2018-02-13 2019-08-20 华为技术有限公司 一种路由更新方法及设备
CN111586765B (zh) * 2019-02-15 2023-01-13 华为技术有限公司 中继通信的方法和装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017106705A2 (en) * 2015-12-17 2017-06-22 Security Innovation, Inc Secure vehicle communication system
CN107547335A (zh) * 2016-06-27 2018-01-05 丛林网络公司 在evpn中信号通知ip地址移动的方法和网络设备
WO2019231818A1 (en) * 2018-05-28 2019-12-05 Qualcomm Incorporated Roll-over of identifiers and keys for unicast vehicle to vehicle communication links
CN109150713A (zh) * 2018-08-22 2019-01-04 赛尔网络有限公司 基于bgp+源终端和目的终端之间的路由方法及路由监测方法

Non-Patent Citations (1)

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

Also Published As

Publication number Publication date
CN118301702A (zh) 2024-07-05
CN114339942B (zh) 2024-04-23
EP4207686A1 (en) 2023-07-05
US20230262579A1 (en) 2023-08-17
CN114339942A (zh) 2022-04-12
EP4207686A4 (en) 2024-01-24

Similar Documents

Publication Publication Date Title
CN109996306B (zh) 通信方法和通信设备
JP7270766B2 (ja) 無線ベアラ構成方法、装置及びシステム
US12563616B2 (en) Packet forwarding method, apparatus, and system
JP2024535136A (ja) ５ｇシステムにおける時間同期サービスの帯域幅効率的構成のための方法及び装置
US12040979B2 (en) Communications method, apparatus, and system
EP4192185A1 (en) Computing bearer application method and apparatus
CN114071510A (zh) 一种通信方法及装置
CN113841366B (zh) 通信方法及装置
US20240155418A1 (en) Method and apparatus for connecting qos flow based terminal in wireless communication system
CN112019489B (zh) 验证方法及装置
WO2022022639A1 (zh) 一种通信方法及装置
CN113518475B (zh) 通信方法、装置及系统
CN115915196A (zh) 一种链路状态检测方法、通信装置及通信系统
WO2023098209A1 (zh) 一种数据传输保护方法、设备及系统
US20230262579A1 (en) Route information update method, communication apparatus, and storage medium
WO2022233011A1 (zh) 建立连接的方法和终端设备
EP4561004A1 (en) Message routing method and device
CN118524438A (zh) 通信方法及装置
CN116783873A (zh) 下一代系统的数据管理和后台数据传送策略控制的性能测量
WO2023272670A1 (zh) 一种网络连接的方法、装置及系统
EP4391629A1 (en) Communication method and related device
EP4188030A1 (en) Communication method and apparatus based on data edge protocol
WO2023246746A1 (zh) 一种通信方法及相关设备
CN118679810A (zh) 集成接入和回传网络中的服务请求
CN119835639A (zh) 通信方法及通信装置

Legal Events

Date Code Title Description
ENP Entry into the national phase

Ref document number: 2021873998

Country of ref document: EP

Effective date: 20230331

NENP Non-entry into the national phase

Ref country code: DE