WO2021168632A1 - 中继方法、路由表的生成方法、装置、设备及存储介质 - Google Patents

中继方法、路由表的生成方法、装置、设备及存储介质 Download PDF

Info

Publication number
WO2021168632A1
WO2021168632A1 PCT/CN2020/076487 CN2020076487W WO2021168632A1 WO 2021168632 A1 WO2021168632 A1 WO 2021168632A1 CN 2020076487 W CN2020076487 W CN 2020076487W WO 2021168632 A1 WO2021168632 A1 WO 2021168632A1
Authority
WO
WIPO (PCT)
Prior art keywords
relay
pdu
identifier
terminal
network device
Prior art date
Application number
PCT/CN2020/076487
Other languages
English (en)
French (fr)
Inventor
卢前溪
Original Assignee
Oppo广东移动通信有限公司
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 Oppo广东移动通信有限公司 filed Critical Oppo广东移动通信有限公司
Priority to CN202080096827.0A priority Critical patent/CN115088387A/zh
Priority to PCT/CN2020/076487 priority patent/WO2021168632A1/zh
Priority to EP20922133.2A priority patent/EP4114137A4/en
Priority to CN202310184554.0A priority patent/CN116232408A/zh
Publication of WO2021168632A1 publication Critical patent/WO2021168632A1/zh
Priority to US17/894,678 priority patent/US20220408342A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/02—Communication route or path selection, e.g. power-based or shortest path routing
    • H04W40/22—Communication route or path selection, e.g. power-based or shortest path routing using selective relaying for reaching a BTS [Base Transceiver Station] or an access point
    • 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/246—Connectivity information discovery
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/14—Relay systems
    • H04B7/15—Active relay systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H04W88/04—Terminal devices adapted for relaying to or from another terminal or user

Definitions

  • This application relates to the field of communication technology, and in particular to a relay method, a routing table generation method, device, equipment, and storage medium.
  • a relay terminal in order to expand the coverage and coverage of the network, a relay terminal can be set up between the remote terminal and the network device, and between the remote terminal and the network device Through the relay terminal to transmit data packets or signaling.
  • the remote terminal and the relay terminal can be connected through the PC5 interface, and the relay terminal and the network device can be connected through the Uu interface.
  • the network device can configure the mapping relationship between the local index and the radio bearer identity, and send the configuration relationship to the relay terminal, where the local index is used to identify the remote terminal, and the radio bearer identity is used to identify the radio bearer.
  • the remote terminal sends a Protocol Data Unit (PDU) to the relay terminal, and the relay PDU carries the local index of the remote terminal.
  • the relay terminal receives the relay PDU, determines the corresponding radio bearer according to the local index and the foregoing mapping relationship, and sends the relay PDU to the network device through the radio bearer.
  • PDU Protocol Data Unit
  • mapping relationship between the remote terminal and the radio bearer is completely configured by the base station, so that the communication between the remote terminal and the network device can be realized, and the flexibility of the relay scheme is low.
  • the embodiments of the present application provide a relay method, a routing table generation method, device, equipment, and storage medium, which can flexibly realize the communication problem between a remote terminal and a network device.
  • the technical solution is as follows:
  • a relay method which is applied to a relay terminal, the relay terminal includes a relay protocol stack, and the relay protocol stack is located between the PDCP layer and the layer 2 protocol stack of the Packet Data Convergence Protocol,
  • the relay protocol stack is a media access control MAC layer protocol stack
  • the relay protocol stack includes a relay receiving entity and a relay sending entity
  • the method includes:
  • the relay receiving entity is configured to receive the relay protocol data unit PDU sent by the previous hop node, and deliver the relay PDU to the relay sending entity;
  • the relay sending entity is used to send the relay PDU to the next hop node.
  • a relay method which is applied to a remote terminal, the remote terminal includes a relay protocol stack, and the relay protocol stack is located in the layer 2 protocol stack of the PDCP layer of the packet data convergence protocol and the PC5 interface
  • the relay protocol stack is a MAC layer protocol stack
  • the relay protocol stack includes a relay sending entity, and the method includes:
  • the relay sending entity is configured to receive the PDCP PDU sent by the PDCP layer, generate a first relay PDU according to the PDCP PDU, and send the first relay PDU to the next hop node;
  • the first relay PDU is a relay PDU sent by the remote terminal to the network device.
  • a relay method which is applied to a network device, the network device includes a relay protocol stack, and the relay protocol stack is located between the PDCP layer of the packet data convergence protocol and the layer 2 protocol stack of the Uu interface
  • the relay protocol stack is a MAC layer protocol stack
  • the relay protocol stack includes a relay receiving entity, and the method includes:
  • the relay receiving entity is configured to receive a first relay PDU from a previous hop node, and the first relay PDU is sent by the remote terminal to the network device.
  • a method for generating a routing table includes:
  • a first routing relationship is established, where the first routing relationship is a routing relationship when the terminal identifier is used as a destination identifier.
  • a relay device configured in a relay terminal, the relay terminal includes a relay protocol stack, and the relay protocol stack is located between the PDCP layer and the layer 2 protocol stack of the Packet Data Convergence Protocol,
  • the relay protocol stack is a media access control MAC layer protocol stack, and the relay protocol stack includes a relay receiving module and a relay sending module:
  • the relay receiving module is configured to receive the relay protocol data unit PDU sent by the previous hop node, and deliver the relay PDU to the relay sending entity;
  • the relay sending module is used to send the relay PDU to the next hop node.
  • a relay device configured in a remote terminal, the remote terminal includes a relay protocol stack, and the relay protocol stack is located at the layer 2 protocol stack of the PDCP layer of the packet data convergence protocol and the PC5 interface
  • the relay protocol stack is a MAC layer protocol stack
  • the relay protocol stack includes a relay transmission module
  • the relay transmission module is configured to receive the PDCP PDU sent by the PDCP layer, according to the The PDCP PDU generates a first relay PDU, and sends the first relay PDU to the next hop node;
  • the first relay PDU is a relay PDU sent by the remote terminal to the network device.
  • a relay device configured in a network device, the network device includes a relay protocol stack, and the relay protocol stack is located between the PDCP layer of the packet data convergence protocol and the layer 2 protocol stack of the Uu interface , Or, the relay protocol stack is a MAC layer protocol stack, the relay protocol stack includes a relay receiving module, and the relay receiving module is configured to receive the first relay PDU from the previous hop node, the The first relay PDU is sent by the remote terminal to the network device.
  • a device for generating a routing table includes:
  • the receiving module is configured to receive a first relay protocol data unit PDU from a remote terminal, the first relay PDU includes the terminal identifier of the remote terminal, and the first relay PDU is the remote terminal Sent to the network device;
  • the route establishment module is configured to establish a first routing relationship based on the terminal identification of the remote terminal and the node identification of the previous hop node, where the first routing relationship is the routing relationship when the terminal identification is used as the destination identification.
  • a relay terminal in a ninth aspect, includes a processor and a memory, the memory stores at least one instruction, and the at least one instruction is used to be executed by the processor to implement the above-mentioned first aspect and Any one of the methods executed by the relay terminal in the fourth aspect.
  • a remote terminal in a tenth aspect, includes a processor and a memory, the memory stores at least one instruction, and the at least one instruction is used to be executed by the processor to implement the above-mentioned second aspect Any of the methods described.
  • a network device in an eleventh aspect, includes a processor and a memory, the memory stores at least one instruction, and the at least one instruction is used to be executed by the processor to implement the third aspect and Any one of the methods executed by the network device in the fourth aspect.
  • a computer-readable storage medium is provided, and instructions are stored on the computer-readable storage medium, and when the instructions are executed by a processor, the method executed by the relay terminal in the above aspects is realized.
  • a computer-readable storage medium is provided, and instructions are stored on the computer-readable storage medium, and when the instructions are executed by a processor, the above-mentioned method is implemented by a remote terminal.
  • a computer-readable storage medium is provided, and instructions are stored on the computer-readable storage medium, and when the instructions are executed by a processor, the method executed by a network device in the above aspect is realized.
  • a computer program product containing instructions which when running on a computer, causes the computer to execute the method executed by the relay terminal, remote terminal or network device described in the above aspect.
  • the relay terminal of the present application includes a relay protocol stack, which is located between the PDCP layer of the packet data convergence protocol and the layer 2 protocol stack, or the relay protocol stack is a media access control MAC layer protocol stack, and the relay protocol
  • the stack includes a relay receiving entity and a relay sending entity.
  • the relay receiving entity is used to receive the relay protocol data unit PDU sent by the previous hop node, and pass the relay PDU to the relay sending entity; the relay sending entity is used to send the relay PDU to the next hop node.
  • the relay terminal containing the relay protocol stack can autonomously determine the next hop node of the relay PDU, so as to successfully relay the relay PDU from one end to the other end without the need for a network
  • the device configuration relates to the mapping relationship between the radio bearer and the remote terminal identifier, which makes the routing process of the relay PDU more flexible.
  • Fig. 1 is a schematic diagram of a communication system provided by an exemplary embodiment of the present application
  • Fig. 2 is a block diagram of a system including a relay protocol stack provided by an exemplary embodiment of the present application
  • Fig. 3 is a schematic diagram of a relay PDU format shown in an exemplary embodiment of the present application.
  • Fig. 4 is a schematic diagram of another relay PDU format shown in an exemplary embodiment of the present application.
  • Fig. 5 is a flowchart of a relay method provided by an exemplary embodiment of the present application.
  • Fig. 6 is a schematic diagram of a relay PDU transmission process shown in an exemplary embodiment of the present application.
  • FIG. 7 is a flowchart of a relay method provided by another exemplary embodiment of the present application.
  • FIG. 8 is a flowchart of a relay method provided by another exemplary embodiment of the present application.
  • FIG. 9 is a flowchart of a relay method provided by another exemplary embodiment of the present application.
  • Fig. 10 is a system block diagram of a protocol stack provided by an exemplary embodiment of the present application.
  • FIG. 11 is a flowchart of a method for generating a routing table provided by an exemplary embodiment of the present application.
  • FIG. 12 is a schematic diagram of a relay process provided by an exemplary embodiment of the present application.
  • FIG. 13 is a schematic diagram of a relay process provided by another exemplary embodiment of the present application.
  • FIG. 14 is a schematic diagram of a relay process provided by another exemplary embodiment of the present application.
  • FIG. 15 is a schematic diagram of a relay process provided by another exemplary embodiment of the present application.
  • FIG. 16 is a flowchart of a method for generating a routing table provided by another exemplary embodiment of the present application.
  • FIG. 17 is a schematic structural diagram of a relay device provided by an exemplary embodiment of the present application.
  • FIG. 18 is a schematic structural diagram of a relay device provided by another exemplary embodiment of the present application.
  • FIG. 19 is a schematic structural diagram of a relay device provided by another exemplary embodiment of the present application.
  • Fig. 20 is a schematic structural diagram of an apparatus for generating a routing table according to an exemplary embodiment of the present application.
  • FIG. 21 is a schematic structural diagram of an apparatus for generating a routing table according to another exemplary embodiment of the present application.
  • Fig. 22 is a schematic structural diagram of a communication device provided by an exemplary embodiment of the present application.
  • Radio bearer It is a collection of wireless logical resources, divided into Signal Radio Bearer (SRB) and Data Radio Bearer (DRB), and DRB is divided into default bearer and dedicated bearer.
  • SRB Signal Radio Bearer
  • DRB Data Radio Bearer
  • Communication links between communication devices can all use one or more radio bearers to assist.
  • the network device may use the radio bearer to generate one or more signals, and/or send one or more signals to the terminal.
  • Uu interface The air interface between the network equipment and the terminal (or User Equipment (UE)) is called the Uu interface.
  • UE User Equipment
  • PC5 interface It is an interface introduced between the communication device and the communication device.
  • the remote terminal and the relay terminal can establish communication through the PC5 interface, or the relay terminal and the relay terminal can also communicate through the PC5 interface.
  • the interface establishes communication.
  • Direct link communication (Sidelink): It is an important branch of cellular Internet of Things technology, that is, things communication technology. It can satisfy the direct communication between two terminals, such as the communication between the remote terminal and the relay terminal in this application, or the communication between the relay terminal and the relay terminal.
  • the sidelink communication method can realize addressing through the source identification (Source ID) and destination identification (Destination ID) of the media access control layer (Media Access Control, MAC). Before transmission, UEs do not need to be connected in advance, and the Sidelink communication mode is used to satisfy a faster and more efficient connection mode between UEs.
  • SDAP Service Data Adaptation Protocol: responsible for mapping QoS bearers to radio bearers according to Quality-of-Service (QoS) requirements.
  • This protocol layer does not exist in the long term evolution (LTE) system, but when connected to the 5G core network in the New Radio (NR), the new QoS processing requires this protocol entity.
  • Packet Data Convergence Protocol realizes IP header compression, encryption, and integrity protection. When switching, it also handles retransmission, sequential delivery, and deduplication. For dual connectivity with separate bearers, PDCP can provide routing and replication, that is, configure a PDCP entity for each radio bearer of the terminal.
  • Radio-Link Control responsible for data segmentation and retransmission.
  • RLC provides services to PDCP in the form of RLC signaling, and each RLC channel (corresponding to each radio bearer) configures one RLC entity for one terminal.
  • RLC in NR does not support the orderly delivery of data to a higher protocol layer.
  • MAC Medium-Access Control
  • HARQ Hybrid Automatic Repeat-reQuest
  • the scheduling function for uplink and downlink resides in the network equipment.
  • MAC provides services to RLC in the form of logical channels.
  • NR changes the MAC header structure, so that compared to LTE, it can more effectively support low-latency processing.
  • PHY Physical Layer
  • SDAP protocol maps IP data packets to different bearers. Data packet 1 and data packet 2 are mapped to radio bearer a, and data packet 3 is mapped to radio bearer b.
  • SDU Service Data Unit
  • PDU Protocol Data Unit
  • the PDCP protocol performs (optional) IP header compression on each radio bearer, and then performs encryption. According to the configuration, it will decide whether to add a PDCP header.
  • the header information contains the information required for terminal decryption and the serial number used for retransmission and in-order delivery.
  • the output of PDCP is forwarded to RLC.
  • the RLC protocol segments the PDCP PDU and adds the RLC header, which contains the sequence number used for retransmission processing.
  • RLC in NR does not provide a data case delivery service to higher protocol layers. Because the reordering mechanism will cause additional delay, this delay may cause damage to services that require very low delay. If really needed, it can be delivered in order by the PDCP layer.
  • the RLC PDU is sent to the MAC layer, and the MAC layer multiplexes multiple RLC PDUs and adds a MAC header to form a new transmission block.
  • the physical layer provides services for the MAC layer in the form of transport channels.
  • the transmission channel is defined by the way and characteristics of information transmission through the wireless interface.
  • the data on the transmission channel is organized into transmission blocks. In each transmission time interval (Transmission Time Interval, TTI), at most one transmission block with a dynamically variable size is sent to the terminal or sent by the terminal through the wireless interface.
  • TTI Transmission Time Interval
  • the MAC layer can multiplex multiple logical channels onto one transmission channel, where each logical channel has its own RLC entity.
  • the MAC layer is responsible for corresponding demultiplexing and forwarding RLC PDUs to their respective RLC entities.
  • the sub-header includes the logical channel identifier (Logical Channel Index, LCID) of the logical channel receiving the RLC PDU and the length of the PDU (in bytes), and may also include reserved bits for demand or future use.
  • LCID Logical Channel Index
  • Dual connection For the terminal to communicate, at least one connection must be established between the terminal and the network.
  • the terminal must be connected to at least one cell that processes all its uplink and downlink transmissions, and all data streams, including user data and radio resource control (Radio Resource Control, RRC) signaling, are processed by this cell.
  • RRC Radio Resource Control
  • dual connectivity DC
  • Dual connectivity is to connect a terminal to two cells, that is, the terminal is connected to the network through multiple cells, such as the case of user plane aggregation, in which data streams from multiple cells are aggregated to increase the data rate. For example, in a scenario where the control plane is separated from the user plane, the communication and signaling of the control plane are processed by one node, and the data on the user plane is processed by another node, thereby increasing the data rate.
  • FIG. 1 shows a schematic diagram of a communication system provided by an exemplary embodiment of the present application.
  • the communication system may include: a remote terminal 130, a relay terminal 120, and a network device 110.
  • the network device 110 and the relay terminal 120 may be connected through a Uu interface, and the remote terminal 130 and the relay terminal 120 may be connected through a PC5 interface.
  • the number of the relay terminal 120 may be one or more. When the number of the relay terminal 120 is more than one, the relay terminal 120 and the relay terminal 120 may also be connected through a PC5 interface.
  • the network device 110 may be a device that communicates with the relay terminal 120 (or called a communication terminal or terminal).
  • the network device 110 may provide communication coverage for a specific geographic area, and may communicate with relay terminals located in the coverage area.
  • the network device 110 may be an evolved network device (Evolutional Node B, eNB or eNodeB) in an LTE system, or a radio controller in a cloud radio access network (Cloud Radio Access Network, CRAN), or
  • the network device may be a mobile switching center, a relay station, an access point, a vehicle-mounted device, a wearable device, a hub, a switch, a bridge, a router, a network device in a 5G network, or a network device in a future communication system, etc.
  • the relay terminal 120 is a terminal deployed in a communication system to provide a relay service for communication between a remote terminal and a network device.
  • the communication process between the remote terminal 130 and the relay terminal 120 may be: the remote terminal 130 sends a relay PDU to the relay terminal, the relay terminal receives the relay PDU, and forwards the relay PDU to the network device 110, In this case, the transmission of the relay PDU is an uplink transmission.
  • the communication process between the remote terminal 130 and the relay terminal 120 may also be: the network device 110 sends a relay PDU to the relay terminal, the relay terminal receives the relay PDU, and forwards the middle to the remote terminal 130 Following the PDU, in this case, the transmission of the relay PDU is a downlink transmission.
  • the remote terminal 130 and the relay terminal 120 may include various handheld devices with wireless communication functions, vehicle-mounted devices, wearable devices, computing devices or other processing devices connected to wireless modems, as well as various forms of user equipment, mobile stations (Mobile Station, MS), terminal (terminal device), etc.
  • GSM Global System of Mobile Communication
  • CDMA Code Division Multiple Access
  • WCDMA broadband code division multiple access
  • GSM Global System of Mobile Communication
  • GPRS General Packet Radio Service
  • LTE Long Term Evolution
  • FDD Frequency Division Duplex
  • TDD Time Division Duplex
  • LTE-A Advanced Long Term Evolution
  • NR New Radio
  • UMTS Universal Mobile Telecommunication System
  • WiMAX Worldwide Interoperability for Microwave Access
  • WiMAX Wireless Local Area Networks
  • WLAN Wireless Fidelity
  • D2D Device to Device
  • M2M Machine to Machine
  • MTC machine type communication
  • V2V vehicle to vehicle
  • V2X vehicle networking
  • the relay terminals 120 may use a direct connection communication method to perform device to device (D2D) communication.
  • D2D device to device
  • the remote terminal 130 and the relay terminal 120 may adopt a direct connection communication manner for direct terminal connection (Device to Device, D2D) communication.
  • D2D Direct terminal connection
  • the 5G communication system or 5G network may also be referred to as a New Radio (NR) system or NR network.
  • NR New Radio
  • Figure 1 exemplarily shows one network device, two relay terminals and four remote terminals.
  • the communication system 100 may include multiple network devices and the coverage of each network device may include other The number of terminals is not limited in this embodiment of the application.
  • the communication system 100 may also include other network entities such as a network controller and a mobility management entity, which are not limited in the embodiment of the present application.
  • network entities such as a network controller and a mobility management entity, which are not limited in the embodiment of the present application.
  • the devices with communication functions in the network/system in the embodiments of the present application may be referred to as communication devices.
  • the communication device may include a network device 110 with a communication function, a relay terminal 120, and a remote terminal 130.
  • the network device 110, the relay terminal 120, and the remote terminal 130 may be upper
  • the specific devices described in the text will not be repeated here; the communication devices may also include other devices in the communication system 100, such as network controllers, mobility management entities, and other network entities, which are not limited in the embodiment of the present application.
  • the remote terminal is connected to the network device through one or more relay terminals.
  • the remote terminal and the relay terminal, or the relay terminal and the relay terminal are connected through the PC5 interface of the 3GPP (Third Generation Partnership Project) system, and the relay terminal directly connected to the network equipment Connect and communicate through the Uu interface of the 3GPP system.
  • the remote terminal, the relay terminal, and the network device all include a relay protocol stack, and the relay protocol stack can be used to relay the relay PDU between the remote terminal and the network device.
  • the relay protocol stack may be a newly-added protocol stack.
  • the relay protocol stack included in the remote terminal is located between the PDCP layer and the layer 2 protocol stack of the PC5 interface; for a network device, the relay protocol stack included in the network device is located in PDCP Layer and the layer 2 protocol stack of the Uu interface; for the relay terminal, the relay protocol stack included in the relay terminal is located between the PDCP layer and the layer 2 protocol stack, and between the relay terminal and the network
  • the layer 2 protocol stack includes the layer 2 protocol stack of the Uu interface.
  • the layer 2 protocol stack includes the layer 2 protocol stack of the PC5 interface. That is, if the communication device adjacent to the relay terminal is a remote terminal, the relay protocol stack included in the relay terminal is located between the PDCP layer and the layer 2 protocol stack of the PC5 interface. The communication device adjacent to the terminal is a network device, and the relay protocol stack included in the relay terminal is located between the PDCP layer and the layer 2 protocol stack of the Uu interface.
  • the layer 2 protocol stack includes but is not limited to an RLC layer protocol stack and a MAC layer protocol stack.
  • Figure 2 shows a system block diagram including a relay protocol stack provided by an exemplary embodiment of the present application.
  • the protocol stack from the remote terminal to the network device is the PDCP protocol layer of the 3GPP Uu interface, and one of the PDCP protocol layers Other protocol layers above include other user plane protocol layers, such as SDAP protocol layer and IP protocol layer, and other control plane protocol layers, such as RRC and Non-Access Stratum (NAS) protocol layers.
  • the protocol stack from the remote terminal to the relay terminal and from the relay terminal to the relay terminal is the protocol stack of layer L2/L1 of the 3GPP PC5 interface. Between the PDCP protocol layer and the PC5 layer 2 protocol layer is the relay protocol layer described in this application.
  • the relay protocol stack may be the MAC layer protocol stack of the communication device.
  • the relay protocol stack includes a relay receiving entity and a relay sending entity.
  • the relay receiving entity and the receiving sending entity may be collectively referred to as a relay protocol entity.
  • the functions of the relay protocol entity include: generating a routing table, forwarding a data packet whose destination identifier is not the current node, and processing a data packet whose destination identifier is the current node or a broadcast identifier. If the relay protocol entity receives the SDU requested by the PDCP layer of the 3GPP Uu interface, it will also generate the PDU of the relay protocol.
  • the relay sending entity of the relay terminal determines whether it is a relay PDU generated according to the PDCP layer or a relay PDU received from a neighboring node.
  • the relay sending entity of the relay terminal sends this relay PDU Forward to the next hop node.
  • the relay terminal may also be a remote terminal at the same time.
  • the relay terminal 1 can communicate with the network device through the relay terminal 2.
  • the relay terminal 1 is a remote terminal.
  • Fig. 2 uses two relay terminals as an example for explanation, which does not constitute a limitation to the present application.
  • the relay method of the present application is applicable to a communication system including one or more relay terminals.
  • the relay terminal can be referred to as the parent node of the remote terminal, and the remote terminal is the child node of the relay terminal.
  • the parent-child relationship remains unchanged.
  • the communication system includes remote terminals, relay terminals 1, relay terminals 2, network equipment, and these If the communication device has a communication connection in turn, the remote terminal is a child node of the relay terminal 1, the relay terminal 1 is a child node of the relay terminal 2, and the relay terminal is a child node of a 2-bit network device, It is not difficult to understand that the network device is the parent node of the relay terminal 2, the relay terminal 2 is the parent node of the relay terminal 1, and the relay terminal 1 is the parent node of the remote terminal.
  • the father-son relationship remains the same. All parent-child nodes can learn their respective identifiers when establishing a parent-child relationship. When the identity of one of the nodes changes, this node can notify all neighboring nodes to update, so that each node can independently update the established routing table.
  • each remote terminal and relay terminal has a unique identifier.
  • the protocol header of the relay PDU contains at least the source identifier, which means that the source identifier in the protocol header of the relay PDU is not empty.
  • the source The content of the identification is the terminal identification of the remote terminal.
  • the protocol header of the relay PDU contains at least the destination identifier, that is, it can be understood that the destination identifier in the protocol header of the relay PDU is not empty.
  • the content of the destination identifier is the network device identifier of the network device.
  • the protocol header of the relay PDU may also include a radio bearer identifier or a logical channel identifier.
  • the radio bearer identifier may be an SRB ID or a DRB ID. Under normal circumstances, more than one radio bearer is often established on the aforementioned PC5 interface or Uu interface.
  • the relay PDU may contain signaling or data packets related to a certain remote terminal.
  • the relay PDU may include not only signaling or data packets related to a certain remote terminal, but also broadcast signaling or broadcast data, such as system messages.
  • relay PDU format includes but is not limited to the following two. This application only uses the following two relay PDU formats as examples for explanation.
  • the relay PDU format can be the following format 1:
  • the relay PDU may include at least: terminal identification, radio bearer identification, or logical channel identification.
  • the terminal identifier can be interpreted as having different meanings. For example, if the relay PDU comes from a child node, the terminal identifier included in the relay PDU is interpreted as the source identifier, that is, the content of the source identifier in the protocol header of the relay PDU is the terminal identifier. Further, the The purpose identifier of the relay PDU protocol header may be empty. If the relay PDU comes from the parent node, the terminal identifier included in the relay PDU is interpreted as the destination identifier, that is, the content of the destination identifier in the protocol header of the relay PDU at this time is the terminal identifier.
  • the source ID fills in the node ID of the node, for example, for the remote terminal
  • the source identifier of the protocol header of the relay PDU is filled in with the terminal identifier of the remote terminal.
  • the destination identifier is filled in with the terminal identifier of the target child node.
  • the target child node is a remote terminal, that is, when the network device generates a relay PDU, the relay PDU
  • the destination identifier in the protocol header is the terminal identifier of the remote terminal.
  • FIG. 3 is a schematic diagram showing a relay PDU format according to an exemplary embodiment of the present application, where the R bit is a reserved bit.
  • the relay PDU may also include an indication information, which is used to indicate the PDCP of the radio bearer between the relay terminal and the network device
  • the cell group where the entity is located that is, according to the indication information, it can be distinguished whether the destination of the relay PDU is a primary cell group (Master Cell Group, MCG) or a secondary cell group (Secondary Cell Group, SCG).
  • the relay PDU format can be the following format 2:
  • the relay PDU may include: terminal identification, network device identification, radio bearer identification, or logical channel identification.
  • the source identifier and the destination identifier of the protocol header of the relay PDU are not empty.
  • the protocol header of the relay PDU is the terminal ID
  • the destination ID is the network device ID
  • the source ID in the protocol header of the relay PDU is the network device ID
  • the destination ID Is the terminal identifier.
  • the relay protocol layer After the relay protocol layer receives the relay PDU, it can determine the source of the relay PDU according to the source identifier contained in the relay PDU, that is, whether the relay PDU is sent by a network device or a remote terminal. According to the destination identifier contained in the relay PDU, it can be determined where the relay PDU needs to be sent, that is, whether the relay PDU needs to be sent to a network device or a remote terminal.
  • the relay PDU is sent from the network device to the remote terminal, a certain bit can be reserved to identify the broadcast identifier.
  • the relay PDU includes broadcast data or broadcast signaling.
  • the relay PDU delivered is for all connected relay terminals and remote terminals.
  • the bit corresponding to this broadcast identifier cannot be occupied by the node identifiers of remote terminals, relay terminals and network equipment.
  • FIG. 4 is a schematic diagram showing another relay PDU format according to an exemplary embodiment of the present application, in which the R bit identifies the reserved bit.
  • the source identifier and the destination identifier are the unique node identifiers of the remote terminal or network device.
  • the network device identifier may be a separately reserved identifier, or an identifier generated based on all or part of the global base station identifier or global cell identifier.
  • the relay PDU when the relay PDU is transmitted, the relay PDU can be generated in the above-mentioned format 1 or format 2.
  • the working principle of the relay receiving entity is as follows:
  • the relay receiving entity can obtain the terminal ID and the radio bearer ID Or logical channel identification, indication information and PDCP PDU. Except for PDCP PDU, the other parts are located in the protocol header of the relay PDU.
  • the terminal identifier is not in the downstream routing table established by the relay terminal, then this terminal identifier is used as the destination identifier in the reverse direction, and a first routing relationship is established in the downstream routing table.
  • the first routing relationship includes the terminal identifier and the upstream The node identifier of the one-hop node, and the first routing relationship is the routing relationship when the terminal identifier is used as the destination identifier.
  • the last hop node is a remote terminal
  • the first routing relationship includes the corresponding relationship between the terminal identifier and the terminal identifier. Add a routing record in the routing table: (RMUE, RMUE).
  • the relay receiving entity can also obtain a destination identifier, for example, the destination identifier is a network device identifier.
  • the relay receiving entity can at least obtain the destination identifier, the radio bearer identifier or the logical channel identifier and the PDCP PDU. Except for PDCP PDU, the other parts are all located in the protocol header of the relay PDU.
  • the destination ID is the same as the node ID of this node, or this destination ID is reserved for broadcast data or broadcast signaling, it means that this node needs to process the relay PDU, so the radio bearer ID and PDCP PDU are delivered to The upper layer protocol, or, the logical channel identifier and PDCP PDU are delivered to the upper layer protocol.
  • the relay PDU is forwarded to the next hop node.
  • this purpose identifier is reserved for broadcast data or broadcast signaling, it means that it is not only necessary to receive the relay PDU by itself, but also needs to be delivered to the relay sending entity of the relay protocol stack. The PDU is then sent to all child nodes connected to the relay terminal.
  • the working principle of the relay sending entity is as follows:
  • the upper layer protocol will pass the information needed to generate the relay PDU to the relay protocol layer, including PDCP PDU, source identification, destination identification, radio bearer identification, and cell group identification.
  • the relay sending entity of the protocol stack The relay sending entity generates the relay PDU according to the relay PDU format 1 or format 2.
  • relay PDU Processing of relay PDU: Whether it is the relay PDU generated by the relay sending entity or the relay PDU obtained from the relay receiving entity, the relay sending entity will follow the existing routing table (including the uplink routing table or the downlink routing table). ) Query to obtain the destination identifier of the next hop node. If the destination identifier is empty, then the relay PDU is forwarded to the default next hop node, if the destination identifier is not empty, then the node corresponding to the destination identifier is determined to be the next hop node, and the relay PDU is forwarded Give the next hop node.
  • the protocol header of the relay PDU contains indication information for indicating the cell group
  • the relay terminal that directly establishes a communication connection with the network device needs to decide to deliver the relay PDU to the MCG or SCG according to this indication information. , That is, other relay terminals between the remote terminal and the network device do not need to pay attention to the indication information.
  • the above is based on the protocol system including the relay protocol stack shown in Figure 2 above, respectively for the remote terminal, the relay terminal and the relay protocol stack on the network device, and the relay PDU is realized based on the relay protocol stack.
  • the process of receiving and sending is explained.
  • the relay method and the method for establishing a routing table involved in the embodiments of the present application will be introduced in detail with reference to the accompanying drawings.
  • FIG. 5 is a flowchart of a relay method according to an exemplary embodiment of the present application.
  • the relay method can be applied to the communication system shown in FIG. 130, the relay method may include at least part of the following content:
  • Step 510 The relay receiving entity is used to receive the relay PDU sent by the previous hop node, and pass the relay PDU to the relay sending entity.
  • the relay PDU includes a first relay PDU and/or a second relay PDU.
  • the first relay PDU is sent by the remote terminal to the network device
  • the second relay PDU is sent by the network device to the remote The end terminal, or the second relay PDU is broadcast by the network device.
  • Step 520 The relay sending entity is used to send the relay PDU to the next hop node.
  • the next hop node can be a network device, another relay terminal or a remote terminal.
  • the next hop node can be the parent node of the relay terminal, for example, a network device or a relay terminal, or a child node of the relay terminal, for example, a remote End terminal or relay terminal.
  • the relay PDU is the first relay PDU
  • the protocol header of the first relay PDU includes: the terminal identifier of the remote terminal, and the terminal identifier Is the Source ID of the first relay PDU.
  • the relay PDU is the second relay PDU
  • the protocol header of the second relay PDU includes: the terminal identifier of the remote terminal, and the terminal identifier It is the destination ID of the second relay PDU.
  • the protocol header of the second relay PDU further includes: a broadcast identifier, and the broadcast identifier is a destination identifier of the second relay PDU.
  • the second relay PDU includes broadcast data or broadcast signaling.
  • all connected relay terminals and/or remote terminals need to receive and process the second relay PDU.
  • the protocol header of the second relay PDU further includes: a source identifier, and the source identifier is a network device identifier of the network device.
  • the source identifier is a network device identifier of the network device.
  • the relay PDU is the first relay PDU
  • the protocol header of the first relay PDU includes: the terminal identifier of the remote terminal, and the terminal identifier Is the source identifier of the first relay PDU.
  • the protocol header of the first relay PDU also includes: the network device identifier of the network device, and the network device identifier is the destination identifier of the first relay PDU.
  • the relay PDU is the second relay PDU
  • the protocol header of the second relay PDU includes: the network device identifier of the network device , The network device identifier is the source identifier of the second relay PDU.
  • the protocol header of the second relay PDU also includes: the terminal identifier of the remote terminal, and the terminal identifier is the destination identifier of the second relay PDU.
  • the relay terminal When using format 2 to design the relay PDU, since the protocol header of the relay PDU includes not only the source identifier but also the destination identifier, the relay terminal does not need to judge the transmission direction of the relay PDU by itself when receiving the relay PDU Just send the relay PDU to the node indicated by the destination identifier in the protocol header.
  • the protocol header of the first relay PDU further includes: a radio bearer identifier, which is a remote terminal and a network device The identity of the radio bearer between.
  • the first relay PDU when the relay protocol stack is a MAC layer protocol stack, the first relay PDU further includes: a logical channel identifier.
  • the network device In order to expand the coverage of a wireless network, multiple remote terminals often communicate with a network device through a relay terminal, that is, a network device accesses multiple remote terminals through a relay terminal. At this time, for the network device, when receiving a relay PDU from a remote terminal, the network device needs to determine which remote terminal the relay PDU comes from. However, when the remote terminal communicates indirectly with the network device, it will establish multiple radio bearers according to different data packets or transmission efficiency requirements, and each radio bearer has its corresponding radio bearer identifier. Therefore, the protocol header of the first relay PDU may also include a radio bearer identifier. The network device can determine which remote terminal the relay PDU comes from according to the radio bearer identifier, which improves the effectiveness of communication.
  • the radio bearer can be SRB or DRB. Because the first remote terminal is in the Sidelink communication mode, the SRB is the direct communication signaling radio bearer SL SRB, and the DRB is the direct communication data radio bearer SL DRB, and the corresponding radio bearer identifiers are SL SRB ID and SL DRB ID, respectively.
  • the relay protocol stack is located between the PDCP layer and the layer 2 protocol stack of the PC5 interface, the destination end of the relay PDU (ie, the network device) can distinguish the radio bearers corresponding to different remote terminals through the above-mentioned radio bearer identifier.
  • the radio bearer identifier may also be an LCID, and the LCID is an identifier used to distinguish the logical channel between the MAC layer and the RLC layer.
  • the PDCP PDU multiplexed in the MAC layer is associated with the logical channel identifier LCID, and the destination of the relay PDU (ie, network equipment) can distinguish between different remote locations through the above logical channels.
  • the radio bearer corresponding to the end terminal.
  • the first relay PDU further includes indication information, and the indication information is used in the indication The cell group where the PDCP entity of the radio bearer of the terminal and the network device is located.
  • the cell group identity can be included in the network device identity. That is, if the protocol header of the first relay PDU also includes a network device identifier, the network device identifier may also include a cell group identifier, and the cell group identifier is used to indicate the PDCP entity of the radio bearer between the relay terminal and the network device The cell group you are in.
  • the cell group can be a primary cell group MCG or a secondary cell group SCG.
  • uplink messages are routed to the MCG by default.
  • some radio bearer PDCP entities are configured on the MCG, and some are configured on the SCG.
  • the remote terminal determines that it is routed to the radio bearer on the MCG according to the configuration information on the RRC reconfiguration message, it will mark the identifier for indicating the MCG in the protocol header of the relay PDU or the network device identifier ; If it is a radio bearer routed to the SCG, mark the identifier used to indicate the SCG in the protocol header of the relay PDU or the network device identifier.
  • the last hop node may be a remote terminal, or the last hop node may be another relay terminal between the relay terminal and the remote terminal.
  • the relay PDU is the first relay PDU.
  • the relay receiving entity is also used to establish a first routing relationship in the downlink routing table when the downlink routing table does not include the routing relationship corresponding to the terminal identifier.
  • a routing relationship includes the terminal identifier and the node identifier of the previous hop node, and the first routing relationship is the routing relationship when the terminal identifier is used as the destination identifier.
  • the relay receiving entity establishes the first routing relationship in the downlink routing table.
  • the first routing relationship is the routing relationship when the terminal identifier is used as the destination identifier, that is, in the downlink routing table, for the relay terminal
  • the destination identifier in the first routing relationship is the terminal identifier of the remote terminal 10
  • the last hop node is the relay terminal 210.
  • the format of the downlink routing table is shown in Table 1 below, and the relay terminal can determine the next hop identifier table according to the destination identifier.
  • the identifier of the remote terminal 10 is RMUE_1, the identifier of the relay terminal 210 is RLUE_1, and the identifier of the relay terminal 220 is RLUE_2.
  • the remote terminal 10 wants to send the first piece of signaling through the relay terminal 210, it writes its own identifier (RMUE_1) as the source identifier in the protocol header of the first relay PDU.
  • the relay terminal 210 After the relay terminal 210 receives the first relay PDU, and finds that the routing relationship corresponding to the source identifier is not included in the downlink routing table, it considers that the first relay PDU is a relay PDU sent by a new remote terminal. . That is, the remote terminal has not established a connection with the relay terminal before, so there is no routing relationship with the terminal identifier of the remote terminal as the destination identifier in the downlink routing table. Therefore, when it is determined that the downlink routing table does not include the terminal identifier included in the protocol header of the received first relay PDU, the relay terminal 210 uses the source identifier contained in the protocol header of the first relay PDU as the destination identifier in the reverse direction. , And add a routing record in the downlink routing table, that is, establish the first routing relationship, as shown in Table 2.
  • the next hop node can be determined according to the first routing relationship in Table 2.
  • the relay terminal 220 adds a routing record to its downlink routing table according to the same method, that is, establishes the first routing relationship, as shown in Table 3 below.
  • the specific implementation of the relay sending entity for sending the first relay PDU to the next hop node may include: the relay sending entity is used for sending the first relay PDU to the default next hop node.
  • the target identifier in the first relay PDU is empty.
  • the relay terminal may transmit the first relay PDU according to a default path.
  • the default next hop node may include multiple, in this case, the default next hop node can be determined according to the selection strategy.
  • the selection strategy can be set according to actual needs. For example, when the remote terminal connected to the default next-hop node is less than the target value, the relay terminal is determined as the next-hop node. Among them, the target value can be set according to actual needs.
  • the next hop node of the relay terminal 210 includes the relay terminal 220 and the relay terminal 230.
  • the relay terminal 210 can determine the default next hop node according to the selection strategy. .
  • the above selection strategy can also be determined according to the communication status between the relay terminal and the network device, and the relay terminal with the best communication status is determined to be the next hop node, which is not limited in this embodiment of the application. .
  • the target identifier in the first relay PDU is not empty.
  • the relay terminal may determine the next hop node according to the target identifier.
  • the relay sending entity is also used to establish the second relay in the uplink routing table.
  • the routing relationship, the second routing relationship includes the network device identifier and the node identifier of the next hop node, and the second routing relationship is the routing relationship when the network device identifier is used as the destination identifier.
  • the relay sending entity queries whether the network device identifier exists in the uplink routing table as the destination according to the network device identifier. Identified routing relationship.
  • the first relay PDU is sent to the next hop node indicated by the next hop node identifier in the routing relationship.
  • the relay sending entity of the relay terminal can transmit the first relay PDU according to the default path.
  • the default next hop node may include multiple, in this case, the default next hop node can be determined according to the selection strategy.
  • the selection strategy can be set according to actual needs. For example, when the remote terminal connected to the default next-hop node is less than the target value, the relay terminal is determined as the next-hop node.
  • the target value can be set according to actual needs.
  • the next hop node of the relay terminal 210 includes the relay terminal 220 and the relay terminal 230.
  • the relay terminal 210 can determine the default next hop node according to the selection strategy. Is 220.
  • the relay terminal not only sends the first relay PDU to the next hop, but also establishes a second routing relationship. For example, when determining that the next hop node is the relay terminal 220, establish the second as shown in Table 4 below. Routing relationship.
  • the network device identifier of the network device 30 is BS_ID
  • the second routing relationship is the routing relationship in the uplink routing table.
  • the relay terminal 210 establishes a second routing relationship in the uplink routing table, as shown in Table 4 below.
  • the last hop node is a network device, or the last hop node of the relay terminal is another relay terminal between the network device and the relay terminal;
  • the relay receiving entity is further configured to: according to the terminal identifier in the protocol header of the second relay PDU, determine the first routing relationship corresponding to the terminal identifier from the downlink routing table, and combine the node corresponding to the terminal identifier in the first routing relationship The node indicated by the identifier is determined as the next hop node.
  • the identifier of the network device 30 is BS_ID, and the first routing relationship is the routing relationship in the downlink routing table.
  • the first routing relationship is shown in Table 5 below:
  • the terminal identifier in the protocol header of the second relay PDU is RMUE_1.
  • RLUE_2 the node identifier corresponding to the RMUE_1 identifier
  • the next hop node is the relay terminal 220 indicated by RLUE_2 .
  • the second relay PDU includes a reference identifier and a PDCP PDU
  • the reference identifier includes a radio bearer identifier or a logical channel identifier
  • the relay receiving entity also uses In the second relay PDU, the reference identifier and the PDCP PDU are delivered to the upper layer.
  • the second relay PDU is sent from the network device to the remote terminal.
  • the protocol header of the second relay PDU also includes the broadcast identifier, it means that the second relay PDU needs to be sent to each device that directly or indirectly communicates with the network device. Therefore, for the relay terminal, after the relay receiving entity receives the second relay PDU, in addition to forwarding it to the second relay PDU, it also needs to transfer the PDCP PDU in the second relay PDU and the reference
  • the identification is submitted to the upper layer so that the upper layer can obtain the broadcast data or broadcast signaling of the system from the network equipment.
  • the relay method provided in this embodiment is applied to a relay terminal.
  • the relay terminal includes a relay protocol stack, and the relay protocol stack is located between the PDCP layer of the packet data convergence protocol and the layer 2 protocol stack, or the relay protocol stack is Media access control MAC layer protocol stack.
  • the relay protocol stack includes a relay receiving entity and a relay sending entity. The relay receiving entity is used to receive the relay protocol data unit PDU sent by the previous hop node, and pass the relay PDU to the relay sending entity; the relay sending entity is used to send the relay PDU to the next hop node.
  • the relay terminal containing the relay protocol stack can autonomously determine the next hop node of the relay PDU, so as to successfully relay the relay PDU from one end to the other end without the need for a network
  • the device configuration relates to the mapping relationship between the radio bearer and the remote terminal identifier, which makes the routing process of the relay PDU more flexible.
  • FIG. 7 is a flowchart showing a relay method according to another exemplary embodiment of the present application.
  • the relay method can be applied to the communication system shown in FIG. 1 and is mainly executed by the remote terminal 120.
  • the relay method may include at least part of the following content:
  • Step 710 The relay sending entity is configured to receive the PDCP PDU sent by the PDCP layer, generate a first relay PDU according to the PDCP PDU, and send the first relay PDU to the next hop node.
  • the first relay PDU is a relay PDU sent by the remote terminal to the network device.
  • the relay protocol stack further includes a relay receiving entity.
  • the relay receiving entity is configured to receive the second relay from the previous hop node.
  • PDU the second relay PDU is a relay PDU sent by the network device to the remote terminal, or the second relay PDU is broadcast by the network device.
  • the second relay PDU includes a reference identifier and a PDCP PDU
  • the reference identifier includes a radio bearer identifier or a logical channel identifier
  • the above method further includes: the relay receiving entity is further configured to include the reference identifier and the PDCP in the second relay PDU when it is determined that the destination identifier in the protocol header of the second relay PDU is the same as the local identifier.
  • the PDU is delivered to the upper layer.
  • the remote terminal when the remote terminal receives the second relay PDU, the remote terminal will pre-determine whether the received second relay PDU is sent to itself. For the second relay PDU sent to itself, the After receiving the second relay PDU, the receiving entity hands the reference identifier and the PDCP PDU included in the second relay PDU to the upper layer for processing. For the second relay PDU that is not sent to itself, the remote terminal can directly discard the second relay PDU without passing it to the upper layer for processing.
  • the above method further includes: the second relay PDU includes a reference identifier and a PDCP PDU, and the above method further includes: the relay receiving entity is further configured to determine that the protocol header of the second relay PDU also includes a broadcast identifier.
  • the reference identifier and PDCP PDU included in the second relay PDU are delivered to the upper layer.
  • the efficiency of data transmission can be improved, in addition, the accuracy of data transmission is ensured, and unnecessary data packet processing is reduced.
  • the protocol header of the first relay PDU includes: the terminal identifier of the remote terminal, and the terminal identifier is the source identifier of the first relay PDU.
  • the protocol header of the first relay PDU includes: the terminal identifier of the remote terminal, and the terminal identifier is the source identifier of the first relay PDU.
  • the protocol header of the first relay PDU also includes: the network device identifier of the network device; the network device identifier is the destination identifier of the first relay PDU.
  • the relay method provided in the embodiment of the present application is applied to a remote terminal, and the remote terminal includes a relay protocol stack, and the relay protocol stack is located between the PDCP layer of the packet data convergence protocol and the layer 2 protocol stack of the PC5 interface, or,
  • the relay protocol stack is a media access control MAC layer protocol stack, and the relay protocol stack includes a relay sending entity.
  • the relay sending entity is used to receive the PDCP PDU sent by the PDCP layer, generate a first relay PDU according to the PDCP PDU, and send the first relay PDU to the next hop node.
  • the first relay PDU is a relay PDU sent by the remote terminal to the network device.
  • the remote terminal can independently determine the next hop node of the first relay PDU to send the first relay PDU to the network device.
  • the network device does not need to configure the radio bearer and the remote
  • the mapping relationship between the terminal identities makes the routing process of transmitting the first relay PDU more flexible.
  • the relay protocol layer is introduced into the protocol stacks of the remote terminal, the relay terminal and the network equipment.
  • the steps of the method applied to each node are roughly the same.
  • the specific implementation details are shown in Figure 5.
  • the embodiment of the relay method applied to the relay terminal is shown, and will not be repeated here.
  • FIG. 8 is a flowchart showing a relay method according to another exemplary embodiment of the present application.
  • the relay method may be applied to the communication system shown in FIG. 1 and is mainly executed by the network device 110.
  • the following method may include at least part of the following content:
  • Step 810 The relay receiving entity is used to receive the first relay PDU from the previous hop node, and the first relay PDU is sent by the remote terminal to the network device.
  • the protocol header of the first relay PDU further includes: a radio bearer identifier, which is between the remote terminal and the network device The identity of the radio bearer;
  • the first relay PDU further includes: a logical channel identifier.
  • the relay receiving entity is also used to send the first relay PDU to the local end when the destination identifier of the first relay PDU is the same as the local identifier.
  • the included PDCP PDU and radio bearer identification are delivered to the upper layer.
  • the relay receiving entity is further used to deliver the PDCP PDU and the radio bearer identifier included in the first relay PDU to the upper layer, or send the first relay PDU to the upper layer.
  • the PDCP PDU and the logical channel identifier included in the relay PDU are delivered to the upper layer.
  • the relay protocol stack further includes a relay sending entity
  • the above method further includes: the relay sending entity is used to receive the PDCP PDU sent by the PDCP layer, generate a second relay PDU according to the PDCP PDU, and transfer the second relay PDU Sent to the next hop node.
  • the second relay PDU is a relay PDU sent by the network device to the remote terminal, or the second relay PDU is broadcast by the network device.
  • the protocol header of the second relay PDU further includes: a terminal identifier of the remote terminal, and the terminal identifier is a destination identifier of the second relay PDU.
  • the second relay PDU further includes a broadcast identifier, and the broadcast identifier is used to indicate that the second relay PDU includes broadcast data or broadcast signaling.
  • the relay method provided in the embodiments of the present application is applied to a network device, and the network device includes a relay protocol stack, and the relay protocol stack is located between the PDCP layer of the packet data convergence protocol and the layer 2 protocol stack of the Uu interface, or the relay
  • the protocol stack is the MAC layer protocol stack for media access control.
  • the relay protocol stack includes a relay receiving entity.
  • the relay receiving entity is used to receive the first relay PDU from the previous hop node.
  • the terminal is sent to the network device.
  • the relay sending entity is used to receive the PDCP PDU sent by the PDCP layer, generate a second relay PDU according to the PDCP PDU, and send the second relay PDU to the next hop node.
  • the network device can independently determine the next hop node of the second relay PDU to send the second relay PDU to the remote terminal. In this process, the network device does not need to pre-configure the relationship between the radio bearer and the remote terminal identification.
  • the mapping relationship makes the routing process of transmitting the second relay PDU more flexible.
  • the relay protocol layer is introduced into the protocol stacks of the remote terminal, the relay terminal and the network equipment.
  • the steps of the method applied to each node are roughly the same.
  • the specific implementation details are shown in Figure 5.
  • the embodiment of the relay method applied to the relay terminal is shown, and will not be repeated here.
  • FIG. 9 shows a relay method according to another exemplary embodiment of the present application.
  • the method is applied to the communication system shown in FIG. 1, including a remote terminal, a relay terminal, and a network. equipment.
  • the relay method may include at least part of the following content:
  • Step 910 The relay sending entity of the remote terminal receives the PDCP PDU sent by the PDCP layer, generates a first relay PDU according to the PDCP PDU, and sends the first relay PDU to the next hop node.
  • the first relay PDU is a relay PDU sent by the remote terminal to the network device.
  • Step 920 The relay receiving entity of the relay terminal receives the first relay PDU sent by the previous hop node, and delivers the first relay PDU to the relay sending entity.
  • the relay sending entity is used to establish a second routing relationship in the uplink routing table, and the second routing relationship includes the network device identifier and the node of the next hop node Identification
  • the second routing relationship is the routing relationship when the network device identification is used as the destination identification.
  • the last hop node may be a remote terminal, or the last hop node may be another relay terminal between the relay terminal and the remote terminal.
  • the first relay PDU further includes indication information, and the indication information is used to indicate the cell group where the PDCP entity of the radio bearer between the relay terminal and the network device is located.
  • the cell group includes a primary cell group MCG or a secondary cell group SCG.
  • the relay receiving entity is further configured to: in the case that the downlink routing table does not include the routing relationship corresponding to the terminal identifier, establish a first routing relationship in the downlink routing table, the first routing relationship including the terminal identifier and the previous hop The node identifier of the node, and the first routing relationship is the routing relationship when the terminal identifier is used as the destination identifier.
  • Step 930 The relay sending entity of the relay terminal sends the first relay PDU to the next hop node.
  • Step 940 The relay receiving entity of the network device receives the first relay PDU from the previous hop node.
  • the relay receiving entity of the network device determines whether the destination identifier of the first relay PDU is empty. If the destination ID of the first relay PDU is not empty, and the destination ID of the first relay PDU is the same as the local ID, the relay receiving entity delivers the PDCP PDU and the radio bearer ID included in the first relay PDU To the upper level.
  • the network device may send at least one of a response message including the first relay PDU, broadcast data, or broadcast signaling to the remote terminal. See the downstream routing process of step 950 to step 980 below.
  • Step 950 The relay sending entity of the network device receives the PDCP PDU sent by the PDCP layer, generates a second relay PDU according to the PDCP PDU, and sends the second relay PDU to the next hop node
  • the second relay PDU is a relay PDU sent by the network device to the remote terminal, or the second relay PDU is broadcast by the network device.
  • the next hop node is a relay terminal directly connected to the network device.
  • Step 960 The relay receiving entity of the relay terminal receives the second relay PDU sent by the previous hop node, and delivers the second relay PDU to the relay sending entity.
  • the last hop node is a network device, or the last hop node is another relay terminal between the relay terminal and the network device.
  • the relay receiving entity determines that the protocol header of the second relay PDU also includes the broadcast identifier, it delivers the second relay PDU to the upper layer.
  • Step 970 The relay sending entity of the relay terminal sends the second relay PDU to the next hop node.
  • the next hop node is a remote terminal, or the next hop node is another relay terminal between the relay terminal and the remote terminal.
  • Step 980 The relay receiving entity of the remote terminal receives the second relay PDU from the previous hop node.
  • the relay receiving entity determines that the destination identifier in the protocol header of the second relay PDU is the same as the local identifier, the second relay PDU is delivered to the upper layer.
  • the relay receiving entity determines that the protocol header of the second relay PDU also includes a broadcast identifier, it delivers the second relay PDU to the upper layer.
  • the first routing relationship is the routing relationship when the terminal identifier is used as the destination identifier, that is, the first routing relationship is the routing relationship in downlink transmission.
  • the second routing relationship is the routing relationship when the network device identifier is used as the destination identifier, that is, the second routing relationship is the routing relationship in uplink transmission.
  • the relay protocol stack is located at the PDCP layer and the PDCP layer of the packet data convergence protocol.
  • the relay protocol stack is a media access control MAC layer protocol stack, and the relay protocol stack includes a relay sending entity and a relay receiving entity.
  • the relay receiving entity is used to receive the relay protocol data unit PDU sent by the previous hop node and pass the relay PDU to the relay sending entity; the relay sending entity is used to send the relay PDU to the next hop node; among them,
  • the relay PDU includes a first relay PDU and/or a second relay PDU, the first relay PDU is sent by the remote terminal to the network device, and the second relay PDU is sent by the network device to the remote terminal, Or, the second relay PDU is broadcast by the network device.
  • the relay terminal including the relay protocol stack can autonomously determine the next hop node of the relay PDU, so as to successfully relay the relay PDU from one end to the other end without the need for a network
  • the device configuration relates to the mapping relationship between the radio bearer and the remote terminal identifier, which makes the routing process of the relay PDU more flexible.
  • the relay method in this application can not only be implemented by introducing a new relay protocol stack between the PDCP layer of the packet data convergence protocol and the layer 2 protocol stack, but also can implement the function of the relay protocol at the MAC layer.
  • FIG. 10 is a system block diagram of a protocol stack provided by an exemplary embodiment of the present application .
  • the MAC CE used to identify the terminal in the MAC layer of the Uu interface There are two possibilities for the content of this MAC CE.
  • One is the network-assigned identifier saved by the terminal before connecting to the network.
  • This identifier can be STMSI, I-RNTI or a random number at the NAS layer, or a part of the UE identifier. , Such as the lowest 16 bits.
  • the other is the C-RNTI newly allocated by the network to the terminal after the UE is connected to the network.
  • the above-mentioned terminals are remote terminals and relay terminals.
  • the relay protocol function is implemented at the MAC layer. It is also possible that the MAC PDU of a Uu interface can contain multiple PDCP PDUs at the same time, and multiple PDCP PDUs may belong to different logics. Channel, and there is no need to introduce a new protocol layer, the above-mentioned relay protocol layer function is realized in the MAC layer.
  • the implementation and maintenance of the relay protocol function at the MAC layer is basically consistent with the introduction of a new relay protocol layer between the PDCP layer and the layer 2 protocol stack of the PC5 interface.
  • the difference is that the terminal identifier uses the terminal identifier MAC CE in the MAC PDU.
  • the terminal identification MAC CE is interpreted as the source identification, and vice versa, it is interpreted as the destination identification.
  • FIG. 11 is a flowchart showing a method for generating a routing table according to an exemplary embodiment of the present application.
  • the method for generating a routing table may be applied to the relay terminal 120 in the communication system shown in FIG.
  • the method of generating can include at least part of the following content:
  • Step 1110 Receive a first relay PDU from the remote terminal, the first relay PDU includes the terminal identifier of the remote terminal, and the first relay PDU is sent by the remote terminal to the network device.
  • Step 1120 Establish a first routing relationship based on the terminal identifier of the remote terminal and the node identifier of the previous hop node.
  • the last hop node refers to the last hop node of the relay terminal, and the last hop node may be a remote terminal, or the last hop node may be another relay between the relay terminal and the remote terminal terminal.
  • Step 1130 Send the first relay PDU to the next hop node.
  • the next hop node refers to the next hop node of the relay terminal, and the next hop node is a network device or the next hop node is between the relay terminal and the network device, and the first routing relationship is the terminal identifier as the destination identifier The routing relationship at the time.
  • the protocol header of the first relay PDU includes the terminal identifier of the remote terminal, and the terminal The identifier is the source identifier of the first relay PDU.
  • the protocol header of the first relay PDU includes a terminal identification and a network device identification, and the terminal identification is the source identification of the first relay PDU,
  • the network device identifier is the destination identifier of the first relay PDU, and the network device identifier is used to indicate the network device to which the first relay PDU needs to be transmitted.
  • the above method further includes: receiving a second relay PDU from the network device, and the second relay PDU is sent by the network device to the remote terminal. Following the PDU, or, the second relay PDU is broadcast by the network device; according to the destination identifier in the protocol header of the second relay PDU and the first routing relationship, the second relay PDU is sent to the next hop node.
  • the target identifier includes a terminal identifier, or the target identifier includes a broadcast identifier.
  • FIG. 12 is a schematic diagram of a relay process provided by an exemplary embodiment of the present application, which is applied to the routing table generation method provided in the present application to request and forward system messages of network devices, etc.
  • the system message includes broadcast data or broadcast signaling.
  • the terminal identifier of the remote terminal is: RMUE
  • the terminal identifier of the relay terminal is: RLUE
  • the network device identifier of the network device is: BS_ID.
  • the remote terminal detects the existence of the relay terminal and wants to receive the broadcast message of the serving cell where the relay terminal is located, to determine whether it can obtain service in the serving cell, so it first establishes a PC5 connection with the relay terminal.
  • the remote terminal sends a first relay PDU to the relay terminal, and the first relay PDU is an RRC message.
  • the RRC message is used to request to receive system messages.
  • the protocol header of the first relay PDU may include: RMUE.
  • the protocol header of the first relay PDU may include RMUE and BS_ID, where the RMUE is the source identifier of the first relay PDU, and the BS_ID is the destination identifier of the first relay PDU.
  • the relay terminal establishes the first routing relationship (RMUE, RMUE) according to the source identifier, and completes the establishment or reconfiguration process of the radio bearer for carrying the first relay PDU between the Uu interface and the network device.
  • the network device is the only uplink node, so the network device is the default next hop node, and the relay terminal sends the first relay PDU to the network device.
  • the network device After receiving this first relay PDU, the network device establishes a third routing relationship (RMUE, RLUE) according to the source identifier in the protocol header of the first relay PDU, and the third routing relationship indicates that it is sent to the remote terminal
  • the second relay PDU of the RMUE is forwarded by the relay terminal RLUE.
  • the network device determines whether the first relay PDU is sent to itself according to the destination identifier. Then the PDU is delivered to the upper layer protocol, such as to the RRC layer.
  • the network device may perform the process of sending a message based on the third routing relationship established in the uplink.
  • Upstream routing and downstream routing are symmetrical.
  • the RRC layer of the network device decides to deliver the system message to the remote terminal on the dedicated channel, and then transfers the system message to the second relay PDU according to the established third routing relationship, namely (RMUE, RLUE) Sent to the relay terminal.
  • the protocol header of this second relay PDU may include: a terminal identifier, and the terminal identifier is a destination identifier of the second relay PDU.
  • the protocol header of the second relay PDU may include a terminal identifier and a network device identifier, where the terminal identifier is the destination identifier of the second relay PDU.
  • the network device identifier is the source identifier of the second relay PDU.
  • the second relay PDU may also include a broadcast identifier.
  • the broadcast identifier may be DESTINATION_BC, which is used to indicate that the second relay PDU includes broadcast data or broadcast signaling.
  • the relay terminal After receiving this second relay PDU, the relay terminal judges that it is a broadcast message according to the destination identifier, and then delivers the PDCP PDU and radio bearer identifier (or logical channel identifier) included in the second relay PDU to its own
  • the RRC layer performs processing, and the relay terminal forwards this second relay PDU to the remote terminal at the same time.
  • the remote terminal After receiving this second relay PDU, the remote terminal also judges that this is a broadcast message based on the destination identifier, and then delivers the PDCP PDU and radio bearer identifier (or logical channel identifier) included in the second relay PDU to itself
  • the RRC layer is processed.
  • the first relay PDU further includes a radio bearer identifier or a logical channel identifier, and the radio bearer identifier is an identifier of a radio bearer between the remote terminal and the network device.
  • the first relay PDU is relayed through the self-media access control MAC layer.
  • the node can notify all neighboring nodes to update, so that each node can update the established routing table autonomously.
  • the above method further includes:
  • the first relay PDU includes CCCH (Common Control Channel, Common Control Channel) message
  • the first cell radio network temporary identifier C-RNTI Cell Radio-Network Temporary Identifier allocated by the network device for itself is acquired. Network Temporary Identifier) information, and send the first C-RNTI information to the previous hop node.
  • the network device can allocate a new one for the connected relay terminal Terminal ID.
  • the relay terminal adopts the new terminal identifier assigned by the network device, the updated terminal identifier needs to be notified to other connected previous hop nodes.
  • the last hop node may be a remote terminal, or a relay terminal located between the relay terminal and the remote terminal.
  • the above method further includes: receiving second C-RNTI information from the remote terminal, where the second C-RNTI information is allocated by the network device for the remote terminal, and updating the terminal identifier in the first routing relationship to The second C-RNTI information.
  • the relay terminal and the network device communicating with it need to be notified, so that the relay terminal and the network device can update the routing table.
  • FIG. 13 is a schematic diagram of a relay process provided by another exemplary embodiment of the present application.
  • the remote terminal sends a CCCH message to the network to start establishing or resuming the RRC connection as shown in FIG. 12, and the relay terminal is in an idle state or an inactive state.
  • the relay process shown in FIG. 13 is used to explain how to establish a routing table during the process of RRC connection establishment, restoration or re-establishment, and how to forward the first relay PDU from the remote terminal to the network device.
  • the original identifier of the remote terminal is: RMUE.
  • the new terminal identifier assigned to it by the network device is: C-RNTI_M.
  • the original identifier of the relay terminal is: RLUE, and the Uu connection is established with the network equipment, and the new terminal identifier assigned to it by the network equipment is: C-RNTI_L.
  • the network device identifier of the network device is: BS_ID.
  • the remote terminal and the relay terminal establish a PC5 connection.
  • the remote terminal can obtain the terminal identifier RLUE of the relay terminal.
  • the remote terminal records a routing relationship (BS_ID, RLUE), the meaning of the routing relationship is: all relay PDUs sent to the network device need to be sent to the relay terminal whose terminal identification is RLUE.
  • the remote terminal sends the first relay PDU containing the CCCH message to the relay terminal.
  • the protocol header of the first relay PDU may include: RMUE.
  • the protocol header of the first relay PDU may include RMUE and BS_ID, where the RMUE is the source identifier of the first relay PDU, and the BS_ID is the destination identifier of the first relay PDU.
  • the relay terminal After receiving the first relay PDU, the relay terminal establishes a first routing relationship (RMUE, RMUE). And establish an RRC connection with the network device and a radio bearer for forwarding the first relay PDU.
  • RMUE first routing relationship
  • the network device is the only uplink node, so the network device is the default next hop node.
  • the relay terminal sends the first relay PDU to the network device to establish a second routing relationship (BS_ID, BS_ID).
  • the network device reassigns a terminal identifier to the relay terminal.
  • the network device may allocate the first C-RNTI information to the relay terminal.
  • the first C-RNTI information is C-RNTI_L.
  • the logo is updated to C-RNTI_L.
  • the relay terminal will forward the first relay PDU containing the CCCH message to the network device.
  • the recorded routing relationship (BS_ID, RLUE) is changed to (BS_ID, C-RNTI_L).
  • a routing record (RMUE, C-RNTI_L) is established.
  • the network device delivers the CCCH message to the upper RRC protocol layer.
  • the network device After processing the CCCH message, the network device sends the second relay PDU containing the RRC connection establishment message to the relay terminal.
  • the protocol header of the second relay terminal may include the terminal identification RMUE of the remote terminal, or the protocol header of the second relay PDU may include BS_ID and RMUE.
  • the BS_ID is the source identifier of the second relay PDU
  • the RMUE is the destination identifier of the second relay PDU.
  • the network device may also send other RRC messages, such as: RRC connection re-establishment or RRC recovery message to the relay terminal.
  • RRC messages such as: RRC connection re-establishment or RRC recovery message
  • the relay terminal After receiving the above-mentioned second relay PDU, the relay terminal forwards the second relay PDU to the remote terminal by querying the routing record (RMUE, RMUE).
  • the remote terminal After receiving the second relay PDU, the remote terminal determines that the second relay PDU is sent to itself according to the destination identifier (ie, RMUE), and then the PDCU and radio bearer identifier in the second relay PDU (Or logical channel identifier) is delivered to the RRC layer protocol.
  • the destination identifier ie, RMUE
  • the PDCU and radio bearer identifier in the second relay PDU Or logical channel identifier
  • the network device reassigns a new terminal identifier to the remote terminal, that is, the second relay PDU includes the second C-RNTI information.
  • the new terminal identifier is C-RNTI_M.
  • the RRC layer of the remote terminal informs the relay terminal of the previous hop node of the second C-RNTI information through PC5 signaling. After the relay terminal receives the second C-RNTI information, it will The first routing relationship (RMUE, RMUE) is updated to (C-RNTI_M, C-RNTI_M).
  • the network device assigns a new terminal identifier to the remote terminal, its own route also needs to be updated, that is, when the network device needs to transmit the second relay PDU to the remote terminal next time, the corresponding destination identifier should be Update to C-RNTI_M by RMUE. That is, the remote terminal sends the first relay PDU containing the RRC connection complete message to the relay terminal, and the source identifier contained in the first relay PDU is C-RNTI_M and the destination identifier is BS_ID. The relay terminal sends the first relay PDU to the network device.
  • the network device When receiving this first relay PDU, the network device establishes a third routing relationship according to the destination identifier, for example, the third routing relationship is (C-RNTI_M, C-RNTI_L). So far, the route between the network device and the remote terminal has been established.
  • the source identifier is BS_ID
  • the destination identifier is C-RNTI_M
  • the source identifier is C-RNTI_M
  • the destination identifier is BS_ID.
  • the method for establishing a routing table provided in this application can not only realize the autonomous establishment of routing relationships, but also modify the terminal identifiers of the relay terminals and remote terminals connected to the network equipment according to the RRC connection status.
  • the flexibility of the relay scheme has been improved.
  • the first relay PDU further includes indication information, which is used to indicate the cell group where the PDCP entity of the radio bearer between the relay terminal and the network device is located.
  • the network device identity further includes a cell group identity, and the cell group identity is used to indicate the cell group where the PDCP entity of the radio bearer between the relay terminal and the network device is located.
  • the cell group includes a primary cell group MCG or a secondary cell group SCG.
  • the relay terminal needs to determine which cell group to send the first relay PDU to when communicating with the network device.
  • the remote terminal Before the RRC reconfiguration process, all uplink messages are routed to the MCG by default. After the RRC reconfiguration process, some DRB PDCP entities are configured on the MCG, and some are configured on the SCG.
  • the configuration information on the RRC reconfiguration message when the remote terminal generates the first relay PDU, if it is routed to the MCG, it will mark the identifier for indicating the MCG in the protocol header of the first relay PDU.
  • the identifier may be the primary cell group identifier. If it is routed to the SCG, then the identifier for indicating the SCG is marked in the protocol header of the first relay PDU.
  • the identifier may be the secondary cell group identifier.
  • FIG. 14 is a schematic diagram of a relay process provided by another exemplary embodiment of the present application.
  • the remote terminal is connected to the network device through two relay terminals, and the format of the relay PDU can be format 1 and format 2.
  • This example is explained based on the relay PDU format 1.
  • This example is also applicable to relay PDU format 2.
  • the protocol header of the first relay PDU contains indication information, which is used to indicate the first relay PDU.
  • a relay PDU is sent to the MCG or to the SCG.
  • the relay terminal 2 will forward the first relay PDU to the MCG.
  • the PDCP entity of the radio bearer between the remote terminal and the network device is configured on the MCG (SCG)
  • the uplink and downlink relay PDUs are transferred between the remote terminal and the MCG (SCG).
  • the routing of the radio bearer is fixed.
  • the PDCP entities of SRB0, SRB1, and SRB2 are configured on the MCG
  • the PDCP entity of SRB3 is configured on the SCG.
  • the specific relay process of this example is shown in Figure 13.
  • the route establishment process of the remote terminal is similar to the process shown in FIG. 13, and will not be repeated here.
  • the MCG (SCG) identifier can be directly used to indicate.
  • the cell group identification of MCG is MCG_ID
  • the cell group identification of SCG is SCG_ID
  • the identification may be included in the network device identification.
  • the remote terminal separately configures the uplink relay PDU protocol according to the location of the PDCP entity.
  • the destination identifier in the header is set to MCG_ID or SCG_ID. The relay terminal 2 needs to determine the correct route according to different destination identifiers.
  • the first relay PDU includes a handover message, and the handover message is used to trigger the relay terminal to establish a connection with the target cell, and the target cell is a cell after the handover.
  • the remote terminal if the remote terminal has established a Uu interface wireless link with the source network device. As the remote terminal gradually moves out of the coverage of the source network device, the remote terminal finds that there is another available relay terminal through measurement, so it sends a measurement report to the source network device, and the remote terminal requests to switch from the Uu interface to one Relay link.
  • the terminal identifier of the remote terminal is C-RNTI_M
  • the terminal identifier of the relay terminal is C_RNTI_L
  • the network device identifier of the network device is BS_ID.
  • the source network device and the target network device where the target serving cell is located perform handover message interaction according to the usual cell handover procedure, and send the handover command to the remote terminal.
  • the remote terminal may establish a PC5 connection with the relay terminal in advance before receiving the handover command. After receiving the handover command, the remote terminal sends the first relay PDU containing the handover complete message to the relay terminal. It is assumed that the first relay PDU is generated in the above-mentioned format 1.
  • This first relay PDU triggers the process of establishing an RRC connection and relaying radio bearer between the relay terminal and the target network device, and the relay terminal adds routing records to its own uplink routing table and downlink routing table, respectively. Namely (BS_ID, BS_ID) and (C-RNTI_M, C-RNTI_M). If the relay terminal has established a Uu interface connection with the target network device, then only the radio bearer for transmitting the relay PDU needs to be added, and no routing relationship is established.
  • the relay terminal sends the first relay PDU containing the handover complete message to the target network device.
  • the target network device After receiving the first relay PDU, the target network device establishes a third routing relationship (C_RNTI_M, C_RNTI_L).
  • the connection between the remote terminal and the target network device may also be established in advance.
  • the measurement report may also include prompt information, such as telling the source network device to indirectly connect to the target network device through a relay terminal when switching to the target network device.
  • the target network device can optimize the content of the handover command based on such prompt information, such as omitting the configuration parameters of the RLC layer and protocols below the RLC layer, and appropriately extending the time for handover to perform protection to protect the smooth completion of the handover.
  • relay PDU format 1 the network device identifier BS_ID of the target network device needs to be added as the target identifier in the relay PDU protocol header of the uplink transmission, and the network device of the target network device needs to be added to the relay PDU protocol header of the downlink transmission.
  • the device identification BS_ID is used as the source identification.
  • the relay terminal determines the next relay PDU based on the protocol header of the relay PDU and the routing relationship in the routing table. Hopping nodes, the process of transmitting the relay PDU is more flexible, and the transmission route of the relay PDU can be defined according to the routing table. To a certain extent, it also alleviates the occurrence of congestion and packet loss when the wireless bearer transmits data packets.
  • the relay scheme is more flexible and efficient.
  • the foregoing routing table generation process is not only applicable to relay terminals, but also to remote terminals and network equipment.
  • FIG. 16 is a flowchart showing a method for generating a routing table according to another exemplary embodiment of the present application.
  • the method for generating a routing table may be applied to the network device 110 in the communication system shown in FIG.
  • the method of establishing can include at least part of the following content:
  • Step 1610 Receive a first relay PDU from the remote terminal.
  • the protocol header of the first relay PDU includes the terminal identifier of the remote terminal.
  • the first relay PDU is a relay PDU sent by the remote terminal to the network device.
  • the first relay PDU includes a PDCP PDU and a radio bearer identifier
  • the radio bearer indicated by the radio bearer identifier is a radio bearer between a remote terminal and a network device
  • the first relay PDU includes a data packet of the radio bearer
  • the first relay PDU includes a PDCP PDU and a logical channel identifier.
  • the PDCP PDU and the radio bearer identifier are delivered to the upper layer , Or, deliver PDCP PDU and logical channel identification to the upper layer.
  • the first relay PDU For the received first relay PDU, if the first relay PDU adopts relay PDU format 2, then if the destination identifier of the first relay PDU is not empty, if the destination identifier of the first relay PDU is the same as the original If the end identifier is the same, the PDCP PDU and the radio bearer identifier are delivered to the upper layer, or the PDCP PDU and the logical channel identifier are delivered to the upper layer.
  • Step 1620 Establish a third routing relationship, the third routing relationship includes the terminal identification and the node identification of the last hop node of the network device, and the third routing relationship is the routing relationship when the terminal identification is used as the destination identification.
  • the third routing relationship is established by the network device, in order to distinguish it from the second routing relationship established by the relay terminal, it can be renamed here as the third routing relationship.
  • the establishment of the third routing relationship is similar to the establishment of the first routing relationship and the second routing relationship described above.
  • For the routing relationship process please refer to the flowchart of the routing table generation method shown in FIG. 11 and the detailed step embodiment. This will not be repeated here.
  • the routing table establishment method receives a first relay PDU from a remote terminal.
  • the protocol header of the first relay PDU includes the terminal identifier of the remote terminal, and the first relay PDU is the remote terminal.
  • a third routing relationship is established.
  • the third routing relationship includes the terminal identifier and the node identifier of the last hop node of the network device.
  • the third routing relationship is the routing relationship when the terminal identifier is used as the destination identifier.
  • the network device can determine which relay terminal should transmit the second relay PDU sent to the remote terminal according to the establishment of the third routing relationship. In this process, there is no need for the network device to pre-configure Regarding the mapping relationship between the radio bearer and the remote terminal identifier, the routing process for transmitting the first relay PDU is more flexible.
  • FIG. 17 is a schematic structural diagram of a relay device according to an exemplary embodiment.
  • the device 1700 may be configured in a relay terminal, the relay device includes a relay protocol stack, and the relay protocol stack is located in a packet data convergence protocol. Between the PDCP layer and the protocol stack of the PC5 interface or, the relay protocol stack is a media access control MAC layer protocol stack, the relay protocol stack includes a relay receiving module 1710 and a relay sending module 1720, and the device 1700 includes:
  • the relay receiving module 1710 is configured to receive the relay protocol data unit PDU sent by the previous hop node, and pass the relay PDU to the relay sending module;
  • the relay sending module 1720 is used to send the relay PDU to the next hop node
  • the relay PDU includes a first relay PDU
  • the protocol header of the first relay PDU includes: a terminal identifier of the remote terminal, and the terminal identifier is a source identifier of the first relay PDU.
  • the protocol header of the first relay PDU further includes: a network device identifier of the network device, and the network device identifier is a destination identifier of the first relay PDU.
  • the relay PDU includes a second relay PDU
  • the protocol header of the second relay PDU includes: a terminal identifier of the remote terminal, and the terminal identifier is a destination identifier of the second relay PDU.
  • the protocol header of the second relay PDU includes: a broadcast identifier, and the broadcast identifier is a destination identifier of the second relay PDU.
  • the protocol header of the second relay PDU further includes: a source identifier, and the source identifier is a network device identifier of the network device.
  • the protocol header of the first relay PDU further includes: a radio bearer identifier, which is between the remote terminal and the network device The identity of the radio bearer;
  • the first relay PDU further includes: a logical channel identifier.
  • the first relay PDU further includes indication information, and the indication information is used to indicate the cell group where the packet data convergence protocol PDCP entity of the radio bearer of the relay terminal and the network device is located.
  • the network device identity further includes a cell group identity, and the cell group identity is used to indicate the cell group where the PDCP entity of the radio bearer between the relay terminal and the network device is located.
  • the cell group includes a primary cell group MCG or a secondary cell group SCG.
  • the last hop node is a remote terminal, or the last hop node is another relay terminal between the relay terminal and the remote terminal;
  • the relay receiving module 1710 is further configured to: in the case that the downlink routing table does not include the routing relationship corresponding to the terminal identifier of the remote terminal, establish a first routing relationship in the downlink routing table, and the first routing relationship includes the terminal identifier and the uplink The node identifier of the one-hop node, and the first routing relationship is the routing relationship when the terminal identifier is used as the destination identifier.
  • the relay PDU includes a first relay PDU
  • the relay sending module 1720 is configured to send the first relay PDU to the next hop node, including:
  • the relay sending module 1720 is configured to send the first relay PDU to the default next hop node.
  • the relay PDU includes a first relay PDU
  • the relay sending module 1720 is configured to establish a second routing relationship in the uplink routing table,
  • the second routing relationship includes the network device identifier and the node identifier of the next hop node, and the second routing relationship is the routing relationship when the network device identifier is used as the destination identifier.
  • the relay PDU includes a second relay PDU, and the last hop node is a network device, or the last hop node of the relay terminal is another relay terminal between the network device and the relay terminal;
  • the relay receiving module 1710 is further configured to: according to the terminal identifier in the protocol header of the second relay PDU, determine the first routing relationship corresponding to the terminal identifier from the downlink routing table;
  • the relay receiving module 1710 is further configured to determine the node indicated by the node identifier corresponding to the terminal identifier in the first routing relationship as the next hop node.
  • the second relay PDU includes a reference identifier and a PDCP PDU, and the reference identifier includes a radio bearer identifier or a logical channel identifier;
  • the relay receiving module is further configured to deliver the reference identifier and the PDCP PDU in the second relay PDU to the upper layer.
  • the layer 2 protocol stack includes the layer 2 protocol stack of the Uu interface
  • the layer 2 protocol stack includes the layer 2 protocol stack of the PC5 interface.
  • the layer 2 protocol stack includes a radio link control RLC layer protocol stack and a media access control MAC layer protocol stack.
  • the relay method provided in this embodiment is applied to a relay terminal.
  • the relay terminal includes a relay protocol stack, and the relay protocol stack is located between the PDCP layer of the packet data convergence protocol and the layer 2 protocol stack, or the relay protocol stack is Media access control MAC layer protocol stack.
  • the relay protocol stack includes a relay receiving entity and a relay sending entity. The relay receiving entity is used to receive the relay protocol data unit PDU sent by the previous hop node, and pass the relay PDU to the relay sending entity; the relay sending entity is used to send the relay PDU to the next hop node.
  • the relay terminal containing the relay protocol stack can autonomously determine the next hop node of the relay PDU, so as to successfully relay the relay PDU from one end to the other end without the need for a network
  • the device configuration relates to the mapping relationship between the radio bearer and the remote terminal identifier, which makes the routing process of the relay PDU more flexible.
  • FIG. 18 is a schematic structural diagram of a relay device according to an exemplary embodiment.
  • the device 1800 may be configured in a remote terminal.
  • the relay device includes a relay protocol stack, and the relay protocol stack is located in the packet data convergence protocol. Between the PDCP layer and the protocol stack of the PC5 interface or the relay protocol stack is the MAC layer protocol stack, the relay protocol stack includes a relay sending module 1810, and the device 1800 may include:
  • the relay sending module 1810 is configured to receive the PDCP PDU sent by the PDCP layer, generate a first relay PDU according to the PDCP PDU, and send the first relay PDU to the next hop node;
  • the first relay PDU is a relay PDU sent by the remote terminal to the network device.
  • the relay protocol stack further includes a relay receiving module 1820.
  • the relay receiving module 1820 is configured to receive a second relay PDU from the previous hop node, and the second relay PDU is sent by the network device to the remote terminal
  • the relay PDU, or the second relay PDU, is broadcast by the network device.
  • the second relay PDU includes a reference identifier and a PDCP PDU, and the reference identifier includes a radio bearer identifier or a logical channel identifier;
  • the relay receiving module 1820 is further configured to deliver the second relay PDU including the reference identifier and the PDCP PDU to the upper layer when it is determined that the destination identifier in the protocol header of the second relay PDU is the same as the local identifier.
  • the second relay PDU includes a reference identifier and a PDCP PDU, and the reference identifier includes a radio bearer identifier or a logical channel identifier;
  • the relay receiving module 1820 is further configured to deliver the reference identifier and the PDCP PDU included in the second relay PDU to the upper layer when it is determined that the protocol header of the second relay PDU also includes the broadcast identifier.
  • the protocol header of the first relay PDU includes: the terminal identifier of the remote terminal, and the terminal identifier is the source identifier of the first relay PDU.
  • the protocol header of the first relay PDU further includes: a network device identifier of the network device;
  • the network device identifier is the destination identifier of the first relay PDU.
  • the relay method provided in the embodiment of the present application is applied to a remote terminal, and the remote terminal includes a relay protocol stack, and the relay protocol stack is located between the PDCP layer of the packet data convergence protocol and the layer 2 protocol stack of the PC5 interface, or,
  • the relay protocol stack is a media access control MAC layer protocol stack, and the relay protocol stack includes a relay sending entity.
  • the relay sending entity is used to receive the PDCP PDU sent by the PDCP layer, generate a first relay PDU according to the PDCP PDU, and send the first relay PDU to the next hop node.
  • the first relay PDU is a relay PDU sent by the remote terminal to the network device.
  • the remote terminal can independently determine the next hop node of the first relay PDU to send the first relay PDU to the network device.
  • the network device does not need to configure the radio bearer and the remote
  • the mapping relationship between the terminal identities makes the routing process of transmitting the first relay PDU more flexible.
  • FIG. 19 is a schematic structural diagram of a relay device according to an exemplary embodiment.
  • the device 1900 may be configured in a network device.
  • the relay device includes a relay protocol stack, and the relay protocol stack is located in the packet data convergence protocol PDCP. Between the layer and the protocol stack of the PC5 interface, or, the relay protocol stack is the MAC layer protocol stack, and the relay protocol stack includes a relay receiving module 1910 and a relay sending module 1920.
  • the device 1900 may include:
  • the relay receiving module 1910 is configured to receive the first relay PDU from the previous hop node, and the first relay PDU is sent by the remote terminal to the network device.
  • the protocol header of the first relay PDU further includes: a radio bearer identifier, which is between the remote terminal and the network device The identity of the radio bearer;
  • the first relay PDU further includes: a logical channel identifier.
  • the relay receiving module 1910 is further configured to include the first relay PDU if the destination identifier of the first relay PDU is the same as the local identifier
  • the PDCP PDU and the radio bearer identification are delivered to the upper layer.
  • the relay receiving module 1910 is further configured to deliver the PDCP PDU and the radio bearer identifier included in the first relay PDU to the upper layer, or include the first relay PDU
  • the PDCP PDU and logical channel identification are delivered to the upper layer.
  • the relay protocol stack further includes a relay sending module 1920
  • the device 1900 further includes:
  • the relay sending module 1920 is configured to receive the PDCP PDU sent by the PDCP layer, generate a second relay PDU according to the PDCP PDU, and send the second relay PDU to the next hop node;
  • the second relay PDU is a relay PDU sent by the network device to the remote terminal, or the second relay PDU is broadcast by the network device.
  • the protocol header of the second relay PDU further includes: a terminal identifier of the remote terminal, and the terminal identifier is a destination identifier of the second relay PDU.
  • the second relay PDU further includes a broadcast identifier, and the broadcast identifier is used to indicate that the second relay PDU includes broadcast data or broadcast signaling.
  • the relay method provided in the embodiments of the present application is applied to a network device, and the network device includes a relay protocol stack, and the relay protocol stack is located between the PDCP layer of the packet data convergence protocol and the layer 2 protocol stack of the Uu interface, or the relay
  • the protocol stack is the MAC layer protocol stack for media access control.
  • the relay protocol stack includes a relay receiving entity.
  • the relay receiving entity is used to receive the first relay PDU from the previous hop node.
  • the terminal is sent to the network device.
  • the relay sending entity is used to receive the PDCP PDU sent by the PDCP layer, generate a second relay PDU according to the PDCP PDU, and send the second relay PDU to the next hop node.
  • the network device can independently determine the next hop node of the second relay PDU to send the second relay PDU to the remote terminal. In this process, the network device does not need to pre-configure the relationship between the radio bearer and the remote terminal identification.
  • the mapping relationship makes the routing process of transmitting the second relay PDU more flexible.
  • Fig. 20 is a schematic diagram showing the structure of an apparatus for generating a routing table according to an exemplary embodiment.
  • the apparatus 2000 may be configured in a relay terminal, and the apparatus 2000 may include:
  • the receiving module 2010 is configured to receive a first relay protocol data unit PDU from a remote terminal, the first relay PDU includes the terminal identifier of the remote terminal, and the first relay PDU is sent by the remote terminal to the network device;
  • the routing establishment module 2020 is configured to establish a first routing relationship based on the terminal identification of the remote terminal and the node identification of the previous hop node.
  • the first routing relationship is the routing relationship when the terminal identification is used as the destination identification.
  • the first relay PDU further includes a network device identifier, the network device identifier is a destination identifier of the first relay PDU, and the network device identifier is used to indicate the network device to which the first relay PDU needs to be transmitted.
  • the first relay PDU further includes a radio bearer identifier or a logical channel identifier, and the radio bearer identifier is an identifier of a radio bearer between the remote terminal and the network device.
  • the first relay PDU further includes indication information, and the indication information is used to indicate the cell group where the packet data convergence protocol PDCP entity of the radio bearer of the relay terminal and the network device is located.
  • the network device identity further includes a cell group identity, and the cell group identity is used to indicate the cell group where the PDCP entity of the radio bearer between the relay terminal and the network device is located.
  • the cell group includes a primary cell group MCG or a secondary cell group SCG.
  • next hop node is a network device, and the device further includes a sending module 2030, and the sending module 2030 is configured to:
  • the first relay PDU includes the common control channel CCCH message, acquiring the first cell radio network temporary identifier C-RNTI information allocated by the network device for itself;
  • the receiving module 2010 is further configured to:
  • the terminal identifier in the first routing relationship is updated to the second C-RNTI information.
  • the first relay PDU includes a handover message, and the handover message is used to trigger the relay terminal to establish a connection with the target cell, and the target cell is a cell after the handover.
  • the receiving module 2010 is also configured to receive a second relay PDU from a network device, the second relay PDU is a relay PDU sent by the network device to a remote terminal, or the second relay PDU is a network device broadcast of;
  • the sending module 2030 is configured to send the second relay PDU to the next hop node according to the destination identifier in the protocol header of the second relay PDU and the first routing relationship.
  • the target identifier includes a terminal identifier; or, the target identifier includes a broadcast identifier.
  • the relay terminal determines the next relay PDU based on the protocol header of the relay PDU and the routing relationship in the routing table. Hopping nodes, the process of transmitting the relay PDU is more flexible, and the transmission route of the relay PDU can be defined according to the routing table. To a certain extent, it also alleviates the occurrence of congestion and packet loss when the wireless bearer transmits data packets.
  • the relay scheme is more flexible and efficient.
  • the foregoing routing table generation process is not only applicable to relay terminals, but also to remote terminals and network equipment.
  • Fig. 21 is a schematic structural diagram showing an apparatus for generating a routing table according to another exemplary embodiment.
  • the apparatus 2100 may be configured in a network device, and the apparatus 2100 may include:
  • the receiving module 2110 is used to receive a first relay PDU from a remote terminal.
  • the protocol header of the first relay PDU includes the terminal identifier of the remote terminal.
  • the first relay PDU is a relay sent by the remote terminal to the network device. PDU;
  • the routing establishment module 2120 is configured to establish a third routing relationship.
  • the third routing relationship includes the terminal identification and the node identification of the last hop node of the network device.
  • the third routing relationship is the routing relationship when the terminal identification is used as the destination identification.
  • the first relay PDU includes a PDCP PDU and a radio bearer identifier
  • the radio bearer indicated by the radio bearer identifier is a radio bearer between the remote terminal and the network device
  • the first relay PDU includes a data packet of the radio bearer
  • the first relay PDU includes a PDCP PDU and a logical channel identifier.
  • the apparatus 2100 further includes:
  • the delivery module 2130 is configured to deliver the PDCP PDU and the radio bearer identifier to the upper layer when the destination identifier of the first relay PDU is empty, or deliver the PDCP PDU and the logical channel identifier to the upper layer.
  • the apparatus 2100 further includes:
  • the delivery module 2130 is configured to deliver the PDCP PDU and the radio bearer identification to the upper layer if the destination identification of the first relay PDU is not empty and the destination identification of the first relay PDU is the same as the local identification.
  • the routing table establishment method receives a first relay PDU from a remote terminal.
  • the protocol header of the first relay PDU includes the terminal identifier of the remote terminal, and the first relay PDU is the remote terminal.
  • a third routing relationship is established.
  • the third routing relationship includes the terminal identifier and the node identifier of the last hop node of the network device.
  • the third routing relationship is the routing relationship when the terminal identifier is used as the destination identifier.
  • the network device can determine which relay terminal should transmit the second relay PDU sent to the remote terminal according to the establishment of the third routing relationship. In this process, there is no need for the network device to pre-configure Regarding the mapping relationship between the radio bearer and the remote terminal identifier, the routing process for transmitting the first relay PDU is more flexible.
  • FIG. 22 shows a schematic structural diagram of a communication device (terminal or access network device) provided by an exemplary embodiment of the present application.
  • the communication device includes: a processor 1201, a receiver 1202, a transmitter 1203, and a memory 1204 and bus 1205.
  • the processor 1201 includes one or more processing cores, and the processor 1201 executes various functional applications and information processing by running software programs and modules.
  • the receiver 1202 and the transmitter 1203 may be implemented as a communication component, and the communication component may be a communication chip.
  • the memory 1204 is connected to the processor 1201 through a bus 1205.
  • the memory 1204 may be used to store at least one instruction, and the processor 1201 is used to execute the at least one instruction, so as to implement each step performed by the terminal and the network device in the foregoing method embodiments.
  • the memory 1204 can be implemented by any type of volatile or non-volatile storage device or a combination thereof.
  • the volatile or non-volatile storage device includes, but is not limited to: magnetic disks or optical disks, electrically erasable and programmable Read-only memory (EEPROM), erasable programmable read-only memory (EPROM), static anytime access memory (SRAM), read-only memory (ROM), magnetic memory, flash memory, programmable read-only memory (PROM) .
  • the present application provides a computer-readable storage medium in which at least one instruction is stored, and the at least one instruction is loaded and executed by the processor to implement the relay method and routing provided by the foregoing various method embodiments The method of table generation.
  • the present application also provides a computer program product, which when the computer program product runs on a computer, causes the computer to execute the relay method and the routing table generation method provided by the foregoing method embodiments.
  • the functions described in the embodiments of the present application may be implemented by hardware, software, firmware, or any combination thereof. When implemented by software, these functions can be stored in a computer-readable medium or transmitted as one or more instructions or codes on the computer-readable medium.
  • the computer-readable medium includes a computer storage medium and a communication medium, where the communication medium includes any medium that facilitates the transfer of a computer program from one place to another.
  • the storage medium may be any available medium that can be accessed by a general-purpose or special-purpose computer.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本申请提供了一种中继方法、路由表的生成方法、装置、设备及存储介质，涉及通信技术领域。所述方法包括：中继终端包括中继协议栈，中继协议栈位于分组数据汇聚协议PDCP层与层2协议栈之间，或者，中继协议栈是媒体接入控制MAC层协议栈，中继接收实体用于接收上一跳节点发送的中继协议数据单元PDU，将中继PDU传递给所述中继发送实体；中继发送实体用于将中继PDU发送给下一跳节点。如此，在远端终端与网络设备之间，通过包含中继协议栈的中继终端可以自主确定中继PDU的下一跳节点，以将中继PDU从一端成功中继至另一端，无需网络设备配置关于无线承载和远端终端标识之间的映射关系，使得中继PDU的路由过程较为灵活。

Description

中继方法、路由表的生成方法、装置、设备及存储介质 技术领域
本申请涉及通信技术领域，特别涉及一种中继方法、路由表的生成方法、装置、设备及存储介质。
背景技术
在第五代移动通信技术(5th generation wireless systems，5G)中，为了扩大网络的覆盖范围和覆盖效果，可以在远端终端和网络设备之间设置中继终端，在远端终端和网络设备之间通过中继终端来传送数据包或者信令。
相关技术中，远端终端与中继终端可以通过PC5接口连接，中继终端与网络设备可以通过Uu接口连接。在实施中，可以由网络设备来配置本地索引与无线承载标识的映射关系，并将该配置关系发给中继终端，其中，本地索引用于标识远端终端，无线承载标识用于标识无线承载。如此，远端终端向中继终端发送协议数据单元(Protocal Data Unit，PDU)，中继PDU携带有远端终端的本地索引。中继终端接收该中继PDU，并根据本地索引和上述映射关系，确定对应的无线承载，并通过该无线承载向网络设备发送中继PDU。
然而，远端终端以及无线承载之间的映射关系完全是由基站进行配置，才可以实现远端终端与网络设备之间的通信，中继方案灵活性低。
发明内容
本申请实施例提供了一种中继方法、路由表的生成方法、装置、设备及存储介质，能够灵活地实现远端终端与网络设备之间的通信问题。所述技术方案如下：
第一方面，提供了一种中继方法，应用于中继终端，所述中继终端包括中继协议栈，所述中继协议栈位于分组数据汇聚协议PDCP层与层2协议栈之间，或者，所述中继协议栈是媒体接入控制MAC层协议栈，所述中继协议栈包括中继接收实体和中继发送实体，所述方法包括：
所述中继接收实体用于接收上一跳节点发送的中继协议数据单元PDU，将所述中继PDU传递给所述中继发送实体；
所述中继发送实体用于将所述中继PDU发送给下一跳节点。
第二方面，提供了一种中继方法，应用于远端终端，所述远端终端包括中继协议栈，所述中继协议栈位于分组数据汇聚协议PDCP层与PC5接口的层2协议栈之间，或者，所述中继协议栈是MAC层协议栈，所述中继协议栈包括中继发送实体，所述方法包括：
所述中继发送实体用于接收所述PDCP层发送的PDCP PDU，根据所述PDCP PDU生成第一中继PDU，将所述第一中继PDU发送给下一跳节点；
其中，所述第一中继PDU是所述远端终端向网络设备发送的中继PDU。
第三方面，提供了一种中继方法，应用于网络设备，所述网络设备包括中继协议栈，所述中继协议栈位于分组数据汇聚协议PDCP层与Uu接口的层2协议栈之间，或者，所述中继协议栈是MAC层协议栈，所述中继协议栈包括中继接收实体，所述方法包括：
所述中继接收实体用于接收来自上一跳节点的第一中继PDU，所述第一中继PDU是由所述远端终端发给所述网络设备的。
第四方面，提供了一种路由表的生成方法，所述方法包括：
接收来自远端终端的第一中继协议数据单元PDU，所述第一中继PDU包括所述远端终端的终端标识，所述第一中继PDU是所述远端终端发给所述网络设备的；
基于所述远端终端的终端标识和上一跳节点的节点标识，建立第一路由关系，所述第一路由关系是所述终端标识作为目的标识时的路由关系。
第五方面，提供了一种中继装置，配置于中继终端，所述中继终端包括中继协议栈，所述中继协议栈位于分组数据汇聚协议PDCP层与层2协议栈之间，或者，所述中继协议栈是媒体接入控制MAC层协议栈，所述中继协议栈包括中继接收模块和中继发送模块：
所述中继接收模块用于接收上一跳节点发送的中继协议数据单元PDU，将所述中继PDU传递给所述中继发送实体；
所述中继发送模块用于将所述中继PDU发送给下一跳节点。
第六方面，提供了一种中继装置，配置于远端终端，所述远端终端包括中继协议栈，所述中继协议栈位于分组数据汇聚协议PDCP层与PC5接口的层2协议栈之间，或者，所述中继协议栈是MAC层协议栈，所述中继协议栈包括中继发送模块，所述中继发送模块用于接收所述PDCP层发送的PDCP PDU，根据所述PDCP PDU生成第一中继PDU，将所述第一中继PDU发送给下一跳节点；
其中，所述第一中继PDU是所述远端终端向网络设备发送的中继PDU。
第七方面，提供了一种中继装置，配置于网络设备，所述网络设备包括中继协议栈，所述中继协议栈位于分组数据汇聚协议PDCP层与Uu接口的层2协议栈之间，或者，所述中继协议栈是MAC层协议栈，所述中继协议栈包括中继接收模块，所述中继接收模块用于接收来自上一跳节点的第一中继PDU，所述第一中继PDU是由所述远端终端发给所述网络设备的。
第八方面，提供了一种路由表的生成装置，所述装置包括：
接收模块，用于接收来自远端终端的第一中继协议数据单元PDU，所述第一中继PDU包括所述远端终端的终端标识，所述第一中继PDU是所述远端终端发给所述网络设备的；
路由建立模块，用于基于所述远端终端的终端标识和上一跳节点的节点标识，建立第一路由关系，所述第一路由关系是所述终端标识作为目的标识时的路由关系。
第九方面，提供了一种中继终端，所述设备包括处理器和存储器，所述存储器存储有至少一条指令，所述至少一条指令用于被所述处理器执行以实现上述第一方面和第四方面中的中继终端执行的任一所述的方法。
第十方面，提供了一种远端终端，所述设备包括处理器和存储器，所述存储器存储有至少一条指令，所述至少一条指令用于被所述处理器执行以实现上述第二方面中任一所述的方法。
第十一方面，提供了一种网络设备，所述设备包括处理器和存储器，所述存储器存储有至少一条指令，所述至少一条指令用于被所述处理器执行以实现上述第三方面和第四方面中的网络设备执行的任一所述的方法。
第十二方面，提供了一种计算机可读存储介质，所述计算机可读存储介质上存储有指令，所述指令被处理器执行时实现上述方面由中继终端执行的方法。
第十三方面，提供了一种计算机可读存储介质，所述计算机可读存储介质上存储有指令，所述指令被处理器执行时实现上述方面由远端终端执行的方法。
第十四方面，提供了一种计算机可读存储介质，所述计算机可读存储介质上存储有指令，所述指令被处理器执行时实现上述方面由网络设备执行的方法。
第十五方面，提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述方面所述的由中继终端、远端终端或网络设备执行的方法。
本申请实施例提供的技术方案带来的有益效果至少包括：
本申请的中继终端包括中继协议栈，中继协议栈位于分组数据汇聚协议PDCP层与层2协议栈之间，或者，中继协议栈是媒体接入控制MAC层协议栈，中继协议栈包括中继接收实体和中继发送实体。中继接收实体用于接收上一跳节点发送的中继协议数据单元PDU，将中继PDU传递给中继发送实体；中继发送实体用于将中继PDU发送给下一跳节点。如此，在远端设备与网络设备之间，通过包含中继协议栈的中继终端可以自主确定中继PDU的下一跳节点，以将中继PDU从一端成功中继至另一端，无需网络设备配置关于无线承载和远端终端标识之间的映射关系，使得中继PDU的路由过程较为灵活。
附图说明
为了更清楚地说明本申请实施例中的技术方案，下面将对实施例描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1是本申请一个示例性实施例提供的通信系统的示意图；
图2是本申请一个示例性实施例提供的包含中继协议栈的系统框图；
图3是本申请一示例性实施例示出的一种中继PDU格式的示意图；
图4是本申请一示例性实施例示出的另一种中继PDU格式的示意图；
图5是本申请一个示例性实施例提供的中继方法的流程图；
图6是本申请一示例性实施例示出的一种中继PDU的传输过程示意图；
图7是本申请另一个示例性实施例提供的中继方法的流程图；
图8是本申请另一个示例性实施例提供的中继方法的流程图；
图9是本申请另一个示例性实施例提供的中继方法的流程图；
图10是本申请一个示例性实施例提供的一种协议栈的系统框图；
图11是本申请一个示例性实施例提供的一种路由表的生成方法的流程图；
图12是本申请一个示例性实施例提供的一种中继过程示意图；
图13是本申请另一个示例性实施例提供的一种中继过程示意图；
图14是本申请另一个示例性实施例提供的一种中继过程示意图；
图15是本申请另一个示例性实施例提供的一种中继过程示意图；
图16是本申请另一个示例性实施例提供的一种路由表的生成方法的流程图；
图17是本申请一个示例性实施例提供的中继装置的结构示意图；
图18是本申请另一个示例性实施例提供的中继装置的结构示意图；
图19是本申请另一个示例性实施例提供的中继装置的结构示意图；
图20是本申请一示例性实施例示出的一种路由表的生成装置的结构示意图；
图21是本申请另一示例性实施例示出的一种路由表的生成装置的结构示意图；
图22是本申请一个示例性实施例提供的通信设备的结构示意图。
具体实施方式
为使本申请的目的、技术方案和优点更加清楚，下面将结合附图对本申请实施方式作进一步地详细描述。
在对本申请实施例提供的中继方法、路由表的生成方法进行详细介绍之前，先对本申请实施例涉及的专业术语和实施环境进行简单介绍。
首先，对本申请实施例涉及的专业术语进行简单介绍。
无线承载：是一种无线逻辑资源集合体，分为信令无线承载(Signal Radio Bearer，SRB)和数据无线承载(Data Radio Bearer，DRB)，而DRB又分为默认承载和专用承载。
通信设备之间的通信链路，诸如终端与网络设备之间，两个终端之间，两个网络设备之间，均可以使用一个或多个无线承载来协助。例如，网络设备可以使用无线承载来生成一个或多个信号，和/或，向终端发送一个或多个信号。
Uu接口：网络设备和终端(或称用户设备(User Equipment，UE))之间的空中接口称为Uu接口。
PC5接口：是在通信设备与通信设备之间引入的接口，在本申请实施例中，远端终端与中继终端可以通过PC5接口建立通信，或者，中继终端与中继终端也可以通过PC5接口建立通信。
直连通信(Sidelink)：是蜂窝物联网技术中的一个重要分支，即物物通信技术。其可以满足两个终端之间的直接通信，比如本申请中的远端终端和中继终端之间通信，或者中继终端和中继终端之间通信。Sidelink通信方式可以通过媒体接入控制层(Media Access Control，MAC)的源标识(Source ID)和目的标识(Destination ID)来实现寻址。在传输之前，UE之间不需要预先连接，Sidelink通信方式以此来满足UE之间更加快捷且高效的连接方式。
无线接入网络的协议栈中的不同协议实体：
1)服务数据调整协议(Service Data Adaptation Protocol，SDAP)：负责根据服务质量(Quality-of-Service，QoS)要求将QoS承载映射到无线承载。长期演进(long term evolution，LTE)系统中不存在该协议层，但在新无线(New Radio，NR)中当连接到5G核心网时，新的QoS处理需要这一协议实体。
2)分组数据汇聚协议(Packet Data Convergence Protocol，PDCP)：实现IP报头压缩、加密和完整性保护。在切换时，它还处理重传、按序递交和重复数据删除。对于承载分离的双连接，PDCP可以提供路由和复制，即为终端的每个无线承载配置一个PDCP实体。
3)无线链路控制(Radio-Link Control，RLC)：负责数据分段和重传。RLC以RLC信令的形式向PDCP提供服务，每个RLC信道(对应每个无线承载)针对一个终端配置一个RLC实体。为了减少时延，与LTE相比，NR中的RLC不支持数据按序递交给更高的协议层。
4)媒体接入控制(Medium-Access Control，MAC)：负责逻辑信道的复用、混合自动重传请求(Hybrid Automatic Repeat-reQuest，HARQ)以及调度和调度相关的功能。用于上行和下行链路的调度功能居于网络设备中。MAC以逻辑信道的形式向RLC提供服务。NR改变了MAC的报头结构，从而相对LTE来说，可以更有效的支持低时延处理。
5)物理层(Physical Layer，PHY)：负责编解码、调制、解调、多天线映射以及其他典型的物理层功能。物理层以传输信道的形式向MAC层提供服务。
作为一个示例，当给定三个IP数据包：数据包1、数据包2和数据包3，其中，数据包1和数据包2在一个无线承载a上，数据包3在另一个无线承载b上。SDAP协议将IP数据包映射到不同的承载上，数据包1和数据包2被映射到无线承载a上，数据包3被映射到无线承载b上。通常，来自或者去往更高协议层的数据实体被称为服务数据单元(Service Data Unit，SDU)，而来自或者去往较低协议层的数据实体被称为协议数据单元(Protocol Data Unit，PDU)。因此，SDAP的输出是SDAP PDU，等价于PDCP SDU。
PDCP协议对每个无线承载执行(可选的)IP报头压缩，然后进行加密。根据配置，会决定是否添加PDCP报头，报头信息包含终端解密所需的信息以及用于重传和按序递交的序列号。PDCP的输出被转发给RLC。
如果需要，RLC协议对PDCP PDU进行分段，并添加RLC报头，其中包含用于重传处理的序列号。与LTE不同，NR中的RLC不向更高协议层提供数据案序递交服务。因为重排序的机制会引起额外的时延，这种时延可能对需要非常低时延的服务造成损害。如果确实需要，可以由PDCP层提供按序递交。
RLC PDU被发送到MAC层，MAC层对多个RLC PDU进行复用并添加MAC报头以形成新的传输块。 物理层以传输信道的形式为MAC层提供服务。传输信道是由信息通过无线接口传输的方式和特性来定义的。传输信道上的数据被组织成传输块。在每个传输时间间隔(Transmission Time Interval，TTI)中，最多一个大小动态可变的传输块通过无线接口发送到终端或者由终端发出。
为了支持优先级处理，MAC层可以将多个逻辑信道复用到一个传输信道上，其中每个逻辑信道拥有自己的RLC实体。在接收端，MAC层负责相应的解复用并将RLC PDU转发至他们各自的RLC实体。为了支持接收端的解复用，需要使用MAC报头，将每个MAC SDU的子报头放在SDU之前，可以在接收到调度决策之前对PDU进行预处理。其中，子报头包含接收RLC PDU的逻辑信道的逻辑信道标识(Logical Channel Index，LCID)和PDU的长度(以字节为单位)，还可以包含供需求或将来使用的预留比特。
双连接：对于要进行通信的终端，至少需要在终端和网络之间建立一个连接。终端至少要连接到一个处理其所有上下行传输的小区，所有的数据流，包括用户数据和无线资源控制(Radio Resource Control，RRC)信令，都由该小区处理。但是在某些情况下，终端和网络之间需要建立双连接(Dual Connectivity，DC)。双连接就是把一个终端连接到两个小区，也即是，终端通过多个小区连接到网络，比如用户面聚合的情况，其中来自多个小区的数据流被聚合在一起以提高数据速率，又比如，控制面和用户面分离的场景，控制面的通信和信令由一个节点处理，用户面的数据由另一个节点处理，从而提高数据速率。
接下来，对本申请实施例涉及的实施环境进行简单介绍。
图1示出了本申请一个示例性实施例提供的通信系统示意图，该通信系统可以包括：远端终端130、中继终端120和网络设备110。网络设备110和中继终端120之间可以通过Uu接口连接，远端终端130与中继终端120之间可以通过PC5接口连接。该中继终端120的数量可以为一个或者多个，当该中继终端120的数量为多个时，中继终端120和中继终端120之间也可以通过PC5接口连接。
其中，网络设备110可以是与中继终端120(或称为通信终端、终端)通信的设备。网络设备110可以为特定的地理区域提供通信覆盖，可以与位于该覆盖区域内的中继终端进行通信。可选地，该网络设备110可以是LTE系统中的演进型网络设备(Evolutional Node B，eNB或eNodeB)，或者是云无线接入网络(Cloud Radio Access Network，CRAN)中的无线控制器，或者该网络设备可以为移动交换中心、中继站、接入点、车载设备、可穿戴设备、集线器、交换机、网桥、路由器、5G网络中的网络设备或者未来通信系统中的网络设备等。
中继终端120是一种部署在通信系统中，用于为远程终端和网络设备之间的通信提供中继服务的终端。远端终端130与中继终端120之间的通信过程可以为：远端终端130向中继终端发送中继PDU，中继终端接收该中继PDU，并向网络设备110转发该中继PDU，在该种情况下，中继PDU的传输为上行传输。或者，远端终端130与中继终端120之间的通信过程也可以为：网络设备110向中继终端发送中继PDU，中继终端接收该中继PDU，并向远端终端130转发该中继PDU，在该种情况下，中继PDU的传输为下行传输。
远端终端130和中继终端120可以包括各种具有无线通信功能的手持设备、车载设备、可穿戴设备、计算设备或连接到无线调制解调器的其他处理设备，以及各种形式的用户设备，移动台(Mobile Station，MS)，终端(terminal device)等等。
本申请实施例的技术方案可以应用于各种通信系统，例如：全球移动通讯(Global System of Mobile Communication，GSM)系统、码分多址(Code Division Multiple Access，CDMA)系统、宽带码分多址(Wideband Code Division Multiple Access，WCDMA)系统、通用分组无线业务(General Packet Radio Service，GPRS)、长期演进(Long Term Evolution，LTE)系统、LTE频分双工(Frequency Division Duplex，FDD)系统、LTE时分双工(Time Division Duplex，TDD)系统、先进的长期演进(Advanced long Term Evolution，LTE-A)系统、新无线(New Radio，NR)系统、NR系统的演进系统、非授权频段上的LTE(LTE-based access to Unlicensed spectrum，LTE-U)系统、NR-U系统、通用移动通信系统(Universal Mobile Telecommunication System，UMTS)、全球互联微波接入(Worldwide Interoperability for Microwave Access，WiMAX)通信系统、无线局域网(Wireless Local Area Networks，WLAN)、无线保真(Wireless Fidelity，WiFi)、下一代通信系统或其他通信系统等。
通常来说，传统的通信系统支持的连接数有限，也易于实现，然而，随着通信技术的发展，移动通信系统将不仅支持传统的通信，还将支持例如，设备到设备(Device to Device，D2D)通信，机器到机器(Machine to Machine，M2M)通信，机器类型通信(Machine Type Communication，MTC)，车辆间(Vehicle to Vehicle，V2V)通信以及车联网(Vehicle to Everything，V2X)系统等。本申请实施例也可以应用于这些通信系统。
可选地，中继终端120之间可以采用直连通信的方式进行终端直连(Device to Device，D2D)通信。
可选地，远端终端130和中继终端120之间可以采用直连通信的方式进行终端直连(Device to Device，D2D)通信。
可选地，5G通信系统或5G网络还可以称为新无线(New Radio，NR)系统或NR网络。
图1示例性地示出了一个网络设备、两个中继终端和四个远端终端，可选地，该通信系统100可以包 括多个网络设备并且每个网络设备的覆盖范围内可以包括其它数量的终端，本申请实施例对此不做限定。
可选地，该通信系统100还可以包括网络控制器、移动管理实体等其他网络实体，本申请实施例对此不作限定。
应理解，本申请实施例中网络/系统中具有通信功能的设备可称为通信设备。以图1示出的通信系统100为例，通信设备可包括具有通信功能的网络设备110、中继终端120和远端终端130，网络设备110、中继终端120和远端终端130可以为上文所述的具体设备，此处不再赘述；通信设备还可包括通信系统100中的其他设备，例如网络控制器、移动管理实体等其他网络实体，本申请实施例中对此不做限定。
基于上述通信系统，在本申请提供的方法中，对于远端终端通过一个或者多个中继终端连接到网络设备。其中远端终端和中继终端，或者中继终端和中继终端之间通过3GPP(Third Generation Partnership Project，第三代合作伙伴项目)系统的PC5接口进行连接，和网络设备直接连接的中继终端通过3GPP系统的Uu接口进行连接和通讯。其中，远端终端、中继终端和网络设备都包括中继协议栈，通过该中继协议栈，可以实现对远端终端和网络设备之间的中继PDU进行中继。
作为一种示例，该中继协议栈可以是新增的协议栈。譬如，对于远端终端来说，该远端终端包括的中继协议栈位于PDCP层和PC5接口的层2协议栈之间；对于网络设备来说，该网络设备包括的中继协议栈位于PDCP层与Uu接口的层2协议栈之间；对于中继终端来说，该中继终端包括的中继协议栈位于PDCP层与层2协议栈之间，并且，在该中继终端与该网络设备交互的情况下，该层2协议栈包括Uu接口的层2协议栈，在该中继终端与另一中继终端交互的情况下，或者，在该中继终端与远端终端交互的情况下，该层2协议栈包括PC5接口的层2协议栈。也即是，若与该中继终端相邻的通信设备为远端终端，则该中继终端包括的中继协议栈位于PDCP层与PC5接口的层2协议栈之间，若与该中继终端相邻的通信设备为网络设备，则该中继终端包括的中继协议栈位于PDCP层与Uu接口的层2协议栈之间。另外，作为一种示例，该层2协议栈包括但不限于RLC层协议栈和MAC层协议栈。
参见图2，图2示出了本申请一个示例性实施例提供的包含中继协议栈的系统框图，远端终端到网络设备的协议栈是3GPP Uu接口的PDCP协议层，以及PDCP协议层之上的其他协议层，包括其他的用户面协议层，比如SDAP协议层和IP协议层，以及其他的控制面协议层，比如RRC和非接入层(Non-Access Stratum，NAS)协议层。远端终端到中继终端，以及中继终端到中继终端的协议栈是3GPP PC5接口的层L2/L1的协议栈。在PDCP协议层和PC5层2协议层之间是本申请中所述的中继协议层。
作为另一种示例，对于该远端终端、中继终端和网络设备中任一通信设备，该中继协议栈可以是该通信设备的MAC层协议栈。
中继协议栈包括中继接收实体和中继发送实体，这里可以将该中继接收实体和接收发送实体统称为中继协议实体。中继协议实体的功能包括：生成路由表、前转目的标识不是本节点的数据包、处理目的标识是本节点或者为广播标识的数据包。如果中继协议实体收到3GPP Uu接口的PDCP层要求发送的SDU,那么还会生成中继协议的PDU。其中，对于中继终端的中继发送实体来说，无论是根据PDCP层生成的中继PDU，还是从相邻节点收到的中继PDU，中继终端的中继发送实体将这个中继PDU转发给下一跳节点。
需要说明的是，当远端终端和网络设备之间存在多个中继终端时，中继终端也可以同时是一个远端终端。作为一个示例，如图2所示，中继终端1可以通过中继终端2和网络设备进行通信，此时对中继终端2而言，中继终端1是远端终端。
作为一个示例，图2以2个中继终端作为例子进行解释说明，并不构成对本申请的限定。本申请的中继方法适用于包括一个或者多个中继终端的通信系统。
需要说明的是，在该通信系统中，可以将中继终端称为远端终端的父节点，而远端终端则是该中继终端的子节点。当某个远端终端本身转变成中继终端时，这种父子关系保持不变，譬如，若该通信系统中包括远端终端、中继终端1、中继终端2、网络设备，并且，这些通信设备依次建有通信连接，则，该远端终端为该中继终端1的子节点，该中继终端1为中继终端2的子节点，该中继终端2位网络设备的子节点，不难理解，该网络设备为中继终端2的父节点，该中继终端2为中继终端1的父节点，该中继终端1为远端终端的父节点，且在通信过程中，该父子关系保持不变。所有的父子节点之间在建立父子关系时可以获知各自的标识。当其中一个节点的标识发生改变时，这个节点可以通知所有相邻节点进行更新，以便于各个节点对已建立的路由表进行自主更新。
其中，每个远端终端和中继终端都有唯一的标识。在上行方向上(从远端终端到网络设备的方向)，中继PDU的协议头中至少包含源标识，即可以理解为中继PDU的协议头中的源标识不为空，此时，源标识的内容为远端终端的终端标识。在下行方向上(从网络设备到远端终端或者中继终端的方向)，中继PDU的协议头中至少包含目的标识，即可以理解为中继PDU的协议头中的目的标识不为空，此时，目的标识的内容为网络设备的网络设备标识。另外，中继PDU的协议头中还可以包括无线承载标识或逻辑信道标识，示例性的，该无线承载标识可以为SRB ID或DRB ID。通常情况下，在上述的PC5接口或者Uu接口上往往会建立超过1个的无线承载。
另外，在上行方向上，中继PDU可以包含和某个远端终端相关的信令或者数据包。在下行方向上，中继PDU除了可以包含和某个远端终端相关的信令或者数据包之外，还可以包括广播信令或者广播数据，比如系统消息等。
此外，在远端终端通过中继终端向网络设备发送中继PDU，或者网络设备通过中继终端向远端终端发送中继PDU的过程中，中继PDU格式的可以有多种，本申请中的中继PDU格式包括但不限于以下两种，本申请仅以以下两种中继PDU格式作为示例解释说明。
在一种可能的实现方式中，中继PDU格式可以为下述格式1：
中继PDU可以至少包括：终端标识、无线承载标识或逻辑信道标识。
根据该中继PDU的来源不同，该终端标识可以被解释为不同含义。譬如，如果该中继PDU是来自子节点，则该中继PDU包括的终端标识被解释为源标识，即此时该中继PDU协议头的源标识的内容为该终端标识，进一步地，该中继PDU协议头的目的标识可以为空。如果中继PDU是来自父节点，则该中继PDU包括的终端标识被解释为目的标识，即此时该中继PDU协议头的目的标识的内容为该终端标识。
换句话来说，如果该中继PDU是在本节点生成的，那么，在将这个中继PDU向父节点发送之前，源标识就填写本节点的节点标识，譬如，对于远端终端来说，在生成中继PDU的过程中，该中继PDU的协议头的源标识填写的是该远端终端的终端标识。如果这个中继PDU是向某个子节点发送，则目的标识填写的是目标子节点的终端标识，譬如，该目标子节点为远端终端，即当网络设备生成中继PDU时，该中继PDU的协议头中的目的标识填写的是远端终端的终端标识。
另外，当中继PDU是从网络设备发送给远端终端时，可以预留一定的比特来表示广播标识，在该种情况下，意味着该中继PDU包括广播数据或广播信令，此时，意味着所传递的中继PDU是给所有相连的中继终端和远端终端。其中，这个广播标识对应的比特位不可以为远端终端、中继终端和网络设备的节点标识所占用。如图3所示，图3是根据本申请一示例性实施例示出的一种中继PDU格式的示意图，其中R比特为预留的比特。
此外，在与网络节点直接相连的中继终端通过双连接连接到网络设备的情况下，中继PDU还可以包括一个指示信息，该指示信息用于指示中继终端与网络设备的无线承载的PDCP实体所在的小区组，也即是，根据该指示信息可以区分这个中继PDU的目的地是主小区组(Master Cell Group，MCG)还是辅小区组(Secondary Cell Group，SCG)。
在另一种可能的实现方式中，中继PDU格式可以为下述格式2：
中继PDU可以包括：终端标识、网络设备标识、无线承载标识或逻辑信道标识。
在该种情况下，该中继PDU的协议头的源标识和目的标识均不为空，譬如，若该中继PDU是由远端终端发给网络设备的，则该中继PDU的协议头中的源标识为终端标识，目的标识为网络设备标识；若该中继PDU是由网络设备发给远端终端的，则该中继PDU的协议头中的源标识为网络设备标识，目的标识为终端标识。
中继协议层收到该中继PDU后，根据该中继PDU包含的源标识可以判断该中继PDU的来源，也即是，该中继PDU是网络设备发送的还是远端终端发送的。根据该中继PDU包含的目的标识可以确定该中继PDU需要发往何处，也即是，该中继PDU是需要发送给网络设备还是需要发送给远端终端。
同理，若中继PDU是从网络设备发送到远端终端，可以预留一定比特来标识广播标识。在该种情况下，意味着该中继PDU包括广播数据或广播信令，此时，意味着所传递的中继PDU是给所有相连的中继终端和远端终端。这个广播标识所对应的比特位不可以为远端终端、中继终端和网络设备的节点标识所占用。
如图4所示，图4是根据本申请一示例性实施例示出的另一种中继PDU格式的示意图，其中R比特标识预留的比特。其中，源标识和目的标识是远端终端或者网络设备的唯一节点标识。另外，网络设备标识可以是一个单独预留的标识，或者是根据全球基站标识、或者全球小区标识的全部或者部分比特信息生成的一个标识。
需要说明的是，在传输中继PDU时，中继PDU可以采用上述格式1或者格式2的方式来生成。
基于上述PDU格式的生成方式，接下来，对中继协议层包括的中继接收实体和中继发送实体的工作原理进行简单介绍。
其中，中继接收实体的工作原理如下：
对于每个接收到的来自远端终端的中继PDU，以按照中继PDU格式1的方式生成中继PDU为例，根据中继PDU格式1，中继接收实体可以得到终端标识，无线承载标识或逻辑信道标识，指示信息和PDCP PDU。其中除了PDCP PDU之外，其他部分均位于中继PDU的协议头中。
针对终端标识的处理：
如果终端标识不在中继终端已建立的下行路由表中，则把这个终端标识作为反方向的目的标识，在该下行路由表中建立第一路由关系，该第一路由关系包括该终端标识和上一跳节点的节点标识，该第一路由 关系为该终端标识作为目的标识时的路由关系。其中，如果该上一跳节点为远端终端，那么该第一路由关系包括终端标识和终端标识的对应关系，如，若终端标识为RMUE，上一跳节点为远端终端，则在该下行路由表中增加一条路由记录：(RMUE，RMUE)。
需要说明的是，若按照中继PDU格式1的方式生成中继PDU，则中继接收实体除了能够得到上述信息外，还可以得到目的标识，譬如，该目的标识为网络设备标识。
对于每个接收到的来自网络设备的中继PDU，根据中继PDU格式1或中继PDU格式2，中继接收实体至少可以得到目的标识，无线承载标识或逻辑信道标识和PDCP PDU。其中除了PDCP PDU之外，其他部分是均位于中继PDU的协议头中。
针对目的标识的处理：
如果目的标识和本节点的节点标识是相同的，或者这个目的标识是预留给广播数据或者广播信令的，说明本节点需要处理该中继PDU，所以，将无线承载标识和PDCP PDU投递给上层协议，或者，将逻辑信道标识和PDCP PDU投递给上层协议。
如果目的标识和本节点的节点标识不相同，说明需要转发给中继PDU，因此，根据该目的标识，将该中继PDU转发给下一跳节点。或者，如果这个目的标识是预留给广播数据或者广播信令的，说明不仅需要自己接收该中继PDU，还需要投递给中继协议栈的中继发送实体，由中继发送实体将该中继PDU发送给与该中继终端相连接的所有子节点。
中继发送实体的工作原理如下：
若本节点需要生成中继PDU，则上层协议将产生中继PDU所需要的信息传递给中继协议层，包括PDCP PDU、源标识、目的标识、无线承载标识和小区组标识都传递给中继协议栈的中继发送实体。中继发送实体按照中继PDU格式1或者格式2产生中继PDU。
针对中继PDU的处理：无论是中继发送实体生成的中继PDU，还是从中继接收实体得到的中继PDU，中继发送实体都会根据已存在的路由表(包括上行路由表或下行路由表)查询获得下一跳节点的目的标识。如果目的标识为空，那么就将该中继PDU转发给缺省的下一跳节点，如果目的标识不为空，那么确定该目的标识对应的节点为下一跳节点，并转发该中继PDU给该下一跳节点。
进一步地，如果中继PDU的协议头包含用于指示小区组的指示信息，那么，只有与网络设备直接建立通信连接的中继终端才需要根据这个指示信息决定把中继PDU投递给MCG或SCG，即远端终端与网络设备之间的其他中继终端不需要关注该指示信息。
至此，上述是基于上述图2所示的包含中继协议栈的协议系统，分别对远端终端、中继终端和网络设备上的中继协议栈，以及基于该中继协议栈实现中继PDU接收和发送的过程进行了说明。接下来，将结合附图，对本申请实施例涉及的中继方法、路由表的建立方法进行详细介绍。
请参见图5，该图5是根据本申请一示例性实施例示出的一种中继方法的流程图，该中继方法可以应用于上述图1所示的通信系统中，主要由中继终端130来执行，该中继方法可以包括如下内容中的至少部分内容：
步骤510：中继接收实体用于接收上一跳节点发送的中继PDU，将中继PDU传递给中继发送实体。
其中，中继PDU包括第一中继PDU和/或第二中继PDU，所述第一中继PDU是由远端终端发给网络设备的，第二中继PDU是由网络设备发给远端终端的，或者，第二中继PDU是由网络设备广播的。
步骤520：中继发送实体用于将中继PDU发送给下一跳节点。
其中，下一跳节点可以是网络设备、另一中继终端或者远端终端。
需要说明的是，在建立连接后，网络设备、中继终端和远端终端之间也建立了父子节点关系，且该父子节点关系不会改变。根据通信系统中存在的父子节点关系，该下一跳节点可以为该中继终端的父节点，譬如，为网络设备或中继终端，也可以为该中继终端的子节点，譬如，为远端终端或者中继终端。
根据前文所述，传输的中继PDU存在两种可能的格式，当中继PDU为上述图3所示的格式1的情况下：
若传输中继PDU的方向为：由远端终端发给网络设备，则该中继PDU为第一中继PDU，该第一中继PDU的协议头包括：远端终端的终端标识，终端标识为第一中继PDU的源标识(Source ID)。
若传输中继PDU的方向为：从网络设备发给远端终端，则该中继PDU为第二中继PDU，该第二中继PDU的协议头包括：远端终端的终端标识，终端标识为第二中继PDU的目的标识(Destination ID)。
可选地，第二中继PDU的协议头还包括：广播标识，该广播标识为第二中继PDU的目的标识。
在该种情况下，意味着该第二中继PDU包括广播数据或广播信令，此时，所有相连的中继终端和/或远端终端均需要接收并处理该第二中继PDU。
可选地，第二中继PDU的协议头还包括：源标识，该源标识为网络设备的网络设备标识。如此，根据该源标识，可以确定该第二PDU是来自网络设备的。
当中继PDU为上述图4所示的格式2的情况下：
若传输中继PDU的方向为：由远端终端发给网络设备，则该中继PDU为第一中继PDU，该第一中继PDU的协议头包括：远端终端的终端标识，终端标识为第一中继PDU的源标识。此外，第一中继PDU的协议头还包括：网络设备的网络设备标识，网络设备标识为第一中继PDU的目的标识。
同理，若传输中继PDU的方向为：从网络设备发给远端终端，则该中继PDU为第二中继PDU，该第二中继PDU的协议头包括：网络设备的网络设备标识，网络设备标识为第二中继PDU的源标识。此外，第二中继PDU的协议头中还包括：远端终端的终端标识，终端标识为第二中继PDU的目的标识。
采用格式2设计中继PDU时，由于中继PDU的协议头中不但包括源标识，还包括目的标识，所以中继终端在接收到该中继PDU时，无需自己判断该中继PDU的传输方向，将该中继PDU发往该协议头中的目的标识指示的节点即可。
作为一种示例，在中继协议栈位于PDCP层与层2协议栈之间的情况下，第一中继PDU的协议头还包括：无线承载标识，该无线承载标识为远端终端与网络设备之间的无线承载的标识。
作为一种示例，在中继协议栈是MAC层协议栈的情况下，第一中继PDU还包括：逻辑信道标识。
为了扩大无线网络的覆盖范围，常出现多个远端终端通过一个中继终端和网络设备通信的情况，也即是，一个网络设备通过中继终端接入多个远端终端。此时，对于网络设备而言，在接收到来自远端终端的中继PDU时，网络设备需要确定该中继PDU具体来自哪一个远端终端。然而，远端终端在和网络设备间接通信时，会根据不同的数据包或者传输效率等需求，建立多个无线承载，每个无线承载都有其对应的无线承载标识。因此，第一中继PDU的协议头中还可以包括无线承载标识。网络设备可以根据该无线承载标识确定该中继PDU来自哪一个远端终端，提高了通信的有效性。
其中，无线承载可以是SRB，也可以是DRB。因为第一远端终端处于Sidelink通信方式，所以SRB是直连通信信令无线承载SL SRB，DRB是直连通信数据无线承载SL DRB，对应的无线承载标识分别为SL SRB ID和SL DRB ID。在中继协议栈位于PDCP层与PC5接口的层2协议栈之间的情况下，中继PDU的目的端(即网络设备)可以通过上述无线承载标识区分不同远端终端对应的无线承载。
此外，无线承载标识还可以是LCID，LCID是用来区别MAC层和RLC层之间的逻辑信道的标识。在中继协议栈在MAC层实现的情况下，复用在MAC层里的PDCP PDU前面关联的是逻辑信道标识LCID，中继PDU的目的端(即网络设备)可以通过上述逻辑信道区分不同远端终端对应的无线承载。
可选地，由于中继终端和网络设备之间存在双连接(Dual Connectivity，DC)的可能性，所以，作为一种示例，第一中继PDU还包括指示信息，该指示信息用于指示中继终端与网络设备的无线承载的PDCP实体所在的小区组。
在另一种可能的实现方式中，可以将小区组标识包含于网络设备标识中。也即是，若第一中继PDU的协议头中还包括网络设备标识，则该网络设备标识还可以包括小区组标识，小区组标识用于指示中继终端与网络设备的无线承载的PDCP实体所在的小区组。
其中，该小区组可以为主小区组MCG或辅小区组SCG。
需要说明的是，在RRC重配置过程之前，上行的消息都缺省路由到MCG上。RRC重配过程之后，有的无线承载的PDCP实体配置在MCG上，有的配置在SCG上。在生成中继PDU时，如果远端终端根据RRC重配置消息上的配置信息确定是路由到MCG上的无线承载，则在中继PDU的协议头或者网络设备标识中标注用于指示MCG的标识；如果是路由到SCG上的无线承载，则在中继PDU的协议头或者网络设备标识中标注用于指示SCG的标识。
接下来，对中继PDU的传输过程进行介绍。在基于图5的可选实施例中，上一跳节点可以为远端终端，或者，上一跳节点可以是处于中继终端与远端终端之间的另一中继终端。
在该种情况下，该中继PDU为第一中继PDU。对于中继终端的中继接收实体来说，该中继接收实体，还用于：在下行路由表不包括终端标识对应的路由关系的情况下，在下行路由表中建立第一路由关系，第一路由关系包括终端标识和上一跳节点的节点标识，第一路由关系是终端标识作为目的标识时的路由关系。
如果在下行路由表中不包括该终端标识对应的路由关系，则为了能够保证该中继终端在接收到源标识为该终端标识的第二中继PDU时可以确定如何对该第二中继PDU进行传输，所以，该中继接收实体在下行路由表中建立第一路由关系。譬如，请参考图6，在图6所示的中继PDU的传输过程中，第一路由关系是终端标识作为目的标识时的路由关系，也即是，在下行路由表中，对于中继终端220而言，第一路由关系中的目的标识为远端终端10的终端标识，上一跳节点是中继终端210。
作为一个示例，下行路由表的格式如下表1所示，中继终端可以根据目的标识来确定下一跳标识的表格。
表1
目的标识 下一跳节点标识
作为一个示例，在图6所示中继PDU的传输过程中，远端终端10的标识是RMUE_1，中继终端210 的标识是RLUE_1,中继终端220的标识是RLUE_2。当远端终端10和中继终端210之间建立PC5连接，并且获知中继终端210的标识RLUE_1。远端终端10想要通过中继终端210发送第一条信令时，将自己的标识(RMUE_1)作为源标识写在第一中继PDU的协议头里。
中继终端210在收到这个第一中继PDU后，发现下行路由表中不包括这个源标识对应的路由关系，则认为该第一中继PDU是一个新的远端终端发送的中继PDU。也即是，该远端终端之前并没有和中继终端建立连接，因此下行路由表中没有该远端终端的终端标识作为目的标识的路由关系。因此，当确定下行路由表中不包括接收的第一中继PDU的协议头包括的终端标识时，中继终端210把第一中继PDU的协议头中包含的源标识作为反方向的目的标识，并且在下行路由表中增加一条路由记录，即建立第一路由关系，如表2所示。
表2
目的标识 下一跳节点标识
RMUE_1 RMUE_1
如此，当在下行方向上收到一个第二中继PDU,如果该第二中继PDU中的目的标识是RMUE_1的话，就可以根据该表2中的第一路由关系，确定下一跳节点。
再如，对于中继终端220来说，则中继终端220根据相同的方法在它的下行路由表中增加一条路由记录，即建立第一路由关系，如下表3所示。
表3
目的标识 下一跳节点标识
RMUE_1 RLUE_1
进一步地，中继发送实体用于将第一中继PDU发送给下一跳节点的具体实现可以包括：中继发送实体用于将第一中继PDU发送给缺省的下一跳节点。
在一种可能的实现方式中，该第一中继PDU中的目标标识为空的，在该种情况下，该中继终端可以按照缺省的路径来传输该第一中继PDU。
作为一种示例，缺省的下一跳节点可能包括多个，在该种情况下，可以根据选取策略确定缺省的下一跳节点。该选取策略可以根据实际需求进行设置，譬如，当缺省的下一跳节点连接的远端终端小于目标值时，将该中继终端确定为下一跳节点。其中，该目标值可以根据实际需求进行设置。
譬如，请参考图6，中继终端210的下一跳节点包括中继终端220和中继终端230，在该种情况下，该中继终端210可以根据选取策略确定缺省的下一跳节点。
需要说明的是，上述选取策略还可以是根据中继终端和网络设备之间的通信状况确定，确定通信状况最好的一个中继终端为下一跳节点，本申请实施例对此不做限定。
在另一种可能的实现方式中，该第一中继PDU中的目标标识不为空，在该种情况下，该中继终端可以根据该目标标识来确定下一跳节点。
另外，在该第一中继PDU中的目标标识不为空的情况下，即第一中继PDU的协议头包括网络设备标识，该中继发送实体还用于在上行路由表中建立第二路由关系，第二路由关系包括网络设备标识和下一跳节点的节点标识，第二路由关系是网络设备标识作为目的标识时的路由关系。
作为一个示例，当第一中继PDU的协议头中包括的目的标识为网络设备的网络设备标识时，中继发送实体根据该网络设备标识，查询上行路由表中是否存在该网络设备标识作为目的标识的路由关系。
若存在相应的路由关系，则将该第一中继PDU发送至该路由关系中下一跳节点标识指示的下一跳节点。
若该网络设备标识作为目的标识时，不存在相应的路由关系，则中继终端的中继发送实体可以按照缺省的路径来传输该第一中继PDU。
其中，缺省的下一跳节点可能包括多个，在该种情况下，可以根据选取策略确定缺省的下一跳节点。该选取策略可以根据实际需求进行设置，譬如，当缺省的下一跳节点连接的远端终端小于目标值时，将该中继终端确定为下一跳节点。其中，该目标值可以根据实际需求进行设置。
譬如，请参考图6，中继终端210的下一跳节点包括中继终端220和中继终端230，在该种情况下，该中继终端210可以根据选取策略确定缺省的下一跳节点为220。
之后，中继终端不仅将该第一中继PDU发送给下一跳，还建立第二路由关系，譬如，在确定下一跳节点为中继终端220时，建立如下表4所示的第二路由关系。
基于上述图6所示的中继PDU的传输过程，网络设备30的网络设备标识为BS_ID，且第二路由关系为上行路由表中的路由关系，作为一个示例，当目的标识为网络设备标识时，中继终端210在上行路由表中建立第二路由关系，如下表4所示。
表4
目的标识 下一跳节点标识
BS_ID RLUE_2
在基于图5的可选实施例中，上一跳节点为网络设备，或者，中继终端的上一跳节点为处于网络设备与中继终端之间的另一中继终端；
中继接收实体，还用于：根据第二中继PDU的协议头中的终端标识，从下行路由表中确定终端标识对应的第一路由关系，将第一路由关系中，终端标识对应的节点标识指示的节点确定为下一跳节点。
基于上述图6所示的中继PDU的传输过程，网络设备30的标识为BS_ID，且第一路由关系为下行路由表中的路由关系，作为一个示例，第一路由关系如下表5所示，第二中继PDU的协议头中的终端标识为RMUE_1，根据如表5所示的第一路由关系，确定RMUE_1标识对应的节点标识为RLUE_2，则下一跳节点为RLUE_2指示的中继终端220。
表5
目的标识 下一跳节点标识
RMUE_1 RLUE_2
可选地，第二中继PDU包括参考标识和PDCP PDU，参考标识包括无线承载标识或逻辑信道标识，在第二中继PDU的协议头还包括广播标识的情况下，中继接收实体还用于将第二中继PDU中的参考标识和PDCP PDU递交给上层。
第二中继PDU是从网络设备发送到远端终端的，当第二中继PDU的协议头还包括广播标识，表示该第二中继PDU需要发送到每个与网路设备直接或间接通信的终端，所以，对于中继终端来说，其中继接收实体接收到第二中继PDU后，除了转发给第二中继PDU之外，还需要将第二中继PDU中的PDCP PDU和参考标识递交给上层，以便于上层从中获取系统来自网络设备的广播数据或广播信令。
本实施例提供的中继方法应用于中继终端中，中继终端包括中继协议栈，中继协议栈位于分组数据汇聚协议PDCP层与层2协议栈之间，或者，中继协议栈是媒体接入控制MAC层协议栈，中继协议栈包括中继接收实体和中继发送实体。中继接收实体用于接收上一跳节点发送的中继协议数据单元PDU，将中继PDU传递给中继发送实体；中继发送实体用于将中继PDU发送给下一跳节点。如此，在远端设备与网络设备之间，通过包含中继协议栈的中继终端可以自主确定中继PDU的下一跳节点，以将中继PDU从一端成功中继至另一端，无需网络设备配置关于无线承载和远端终端标识之间的映射关系，使得中继PDU的路由过程较为灵活。
图7是根据本申请另一示例性实施例示出的一种中继方法的流程图，该中继方法可以应用于上述图1所示的通信系统中，主要由远端终端120来执行，该中继方法可以包括如下内容中的至少部分内容：
步骤710：中继发送实体用于接收PDCP层发送的PDCP PDU，根据PDCP PDU生成第一中继PDU，将第一中继PDU发送给下一跳节点。
其中，第一中继PDU是远端终端向网络设备发送的中继PDU。
可选地，所述中继协议栈还包括中继接收实体，在基于图7的可选实施例中，上述方法还包括：中继接收实体用于接收来自上一跳节点的第二中继PDU，第二中继PDU是网络设备向远端终端发送的中继PDU，或者，第二中继PDU是由网络设备广播的。
作为一种示例，第二中继PDU包括参考标识和PDCP PDU，参考标识包括无线承载标识或逻辑信道标识。
可选地，上述方法还包括：中继接收实体还用于在确定第二中继PDU的协议头中的目的标识与本端标识相同的情况下，将第二中继PDU包括参考标识和PDCP PDU递交给上层。
需要说明的是，当远端终端接收到第二中继PDU时，远端终端会预先判断接收的第二中继PDU是否是发送给自己的，对于发送给自己的第二中继PDU，中继接收实体接收该第二中继PDU后，将该第二中继PDU中包括的参考标识和PDCP PDU交给上层处理。对于不是发送给自己的第二中继PDU，远端终端可以直接丢掉该第二中继PDU，不用传递给上层处理。
可选地，上述方法还包括：第二中继PDU包括参考标识和PDCP PDU，上述方法还包括：中继接收实体还用于在确定第二中继PDU的协议头中还包括广播标识的情况下，将第二中继PDU包括的参考标识和PDCP PDU递交给上层。
通过提前预判第二中继PDU的目的标识是否与自身的节点标识相同，可以提高数据传递效率，此外还确保了数据传输的准确性，减少不必要的数据包处理。
可选地，采用中继PDU格式1生成中继PDU时，第一中继PDU的协议头包括：远端终端的终端标识，终端标识为第一中继PDU的源标识。
可选地，采用中继PDU格式2生成中继PDU时，第一中继PDU的协议头包括：远端终端的终端标识，终端标识为第一中继PDU的源标识。此外，第一中继PDU的协议头还包括：网络设备的网络设备标 识；网络设备标识为第一中继PDU的目的标识。
在本申请实施例提供的中继方法应用于远端终端中，远端终端包括中继协议栈，中继协议栈位于分组数据汇聚协议PDCP层与PC5接口的层2协议栈之间，或者，中继协议栈是媒体接入控制MAC层协议栈，中继协议栈包括中继发送实体。中继发送实体用于接收PDCP层发送的PDCP PDU，根据PDCP PDU生成第一中继PDU，将第一中继PDU发送给下一跳节点。其中，第一中继PDU是远端终端向网络设备发送的中继PDU。也即是，在远端终端可以自主确定第一中继PDU的下一跳节点，以将第一中继PDU发往网络设备端，在此过程中，无需网络设备配置关于无线承载和远端终端标识之间的映射关系，使得传输第一中继PDU的路由过程较为灵活。
由于本申请提供的中继方法，在远端终端、中继终端和网络设备的协议栈中均引入了中继协议层，该方法应用于各个节点的步骤大体相同，具体实施细节参见图5所示应用于中继终端的中继方法实施例，在此不做赘述。
图8是根据本申请另一示例性实施例示出的一种中继方法的流程图，该中继方法可以应用于上述图1所示的通信系统中，主要由网络设备110来执行，该中继方法可以包括如下内容中的至少部分内容：
步骤810：中继接收实体用于接收来自上一跳节点的第一中继PDU，第一中继PDU是由远端终端发给网络设备的。
可选地，在中继协议栈位于PDCP层与层2协议栈之间的情况下，第一中继PDU的协议头还包括：无线承载标识，无线承载标识为远端终端与网络设备之间的无线承载的标识；
在中继协议栈是MAC层协议栈的情况下，第一中继PDU还包括：逻辑信道标识。
可选地，若所述第一中继PDU的目的标识不为空，中继接收实体还用于在第一中继PDU的目的标识与本端标识相同的情况下，将第一中继PDU包括的PDCP PDU和无线承载标识递交给上层。
可选地，若所述第一中继PDU的目的标识为空，中继接收实体还用于将第一中继PDU包括的PDCP PDU和无线承载标识递交给上层，或者，将所述第一中继PDU包括的PDCP PDU和所述逻辑信道标识递交给上层。
可选地，中继协议栈还包括中继发送实体，上述方法还包括：中继发送实体用于接收PDCP层发送的PDCP PDU，根据PDCP PDU生成第二中继PDU，将第二中继PDU发送给下一跳节点。
其中，第二中继PDU为网络设备向远端终端发送的中继PDU，或者，第二中继PDU为网络设备广播的。
可选地，第二中继PDU的协议头还包括：远端终端的终端标识，终端标识为第二中继PDU的目的标识。
可选地，第二中继PDU还包括广播标识，广播标识用于指示第二中继PDU包括广播数据或广播信令。
在本申请实施例提供的中继方法应用于网络设备中，网络设备包括中继协议栈，中继协议栈位于分组数据汇聚协议PDCP层与Uu接口的层2协议栈之间，或者，中继协议栈是媒体接入控制MAC层协议栈，中继协议栈包括中继接收实体，中继接收实体用于接收来自上一跳节点的第一中继PDU，第一中继PDU是由远端终端发给网络设备的。中继发送实体用于接收PDCP层发送的PDCP PDU，根据PDCP PDU生成第二中继PDU，将第二中继PDU发送给下一跳节点。网络设备可以自主确定第二中继PDU的下一跳节点，以将第二中继PDU发往远端终端，在此过程中，无需网络设备预先配置关于无线承载和远端终端标识之间的映射关系，使得传输第二中继PDU的路由过程较为灵活。
由于本申请提供的中继方法，在远端终端、中继终端和网络设备的协议栈中均引入了中继协议层，该方法应用于各个节点的步骤大体相同，具体实施细节参见图5所示应用于中继终端的中继方法实施例，在此不做赘述。
接下来，对于本申请中远端终端通过中继终端和网络设备进行通信的过程进行解释说明。
如图9所示，图9是根据本申请另一示例性实施例示出的一种中继方法，该方法应用于上述图1所示的通信系统中，包括远端终端、中继终端和网络设备。该中继方法可以包括如下内容中的至少部分内容：
步骤910：远端终端的中继发送实体接收PDCP层发送的PDCP PDU，根据PDCP PDU生成第一中继PDU，将第一中继PDU发送给下一跳节点。
其中，第一中继PDU是远端终端向网络设备发送的中继PDU。
步骤920：中继终端的中继接收实体接收上一跳节点发送的第一中继PDU，将第一中继PDU传递给中继发送实体。
其中，第一中继PDU的协议头包括网络设备标识的情况下，中继发送实体用于在上行路由表中建立第二路由关系，第二路由关系包括网络设备标识和下一跳节点的节点标识，第二路由关系是网络设备标识作为目的标识时的路由关系。上一跳节点可以为远端终端，或者，上一跳节点可以是处于中继终端与远端终端之间的另一中继终端。
可选地，第一中继PDU还包括指示信息，指示信息用于指示中继终端与网络设备的无线承载的PDCP 实体所在的小区组。其中，小区组包括主小区组MCG或辅小区组SCG。
可选地，中继接收实体还用于：在下行路由表不包括终端标识对应的路由关系的情况下，在下行路由表中建立第一路由关系，第一路由关系包括终端标识和上一跳节点的节点标识，第一路由关系是终端标识作为目的标识时的路由关系。
步骤930：中继终端的中继发送实体将第一中继PDU发送给下一跳节点。
步骤940：网络设备的中继接收实体接收来自上一跳节点的第一中继PDU。
需要说明的是，网络设备的中继接收实体在接收地第一中继PDU时，判断第一中继PDU的目的标识是否为空。若第一中继PDU的目的标识不为空，且第一中继PDU的目的标识与本端标识相同的情况下，中继接收实体将第一中继PDU包括的PDCP PDU和无线承载标识递交给上层。
此外，网络设备在接收第一中继PDU后，可以向远端终端发送包括第一中继PDU的响应消息、广播数据或广播信令中的至少一种。参见下述步骤950-步骤980的下行路由过程。
步骤950：网络设备的中继发送实体接收PDCP层发送的PDCP PDU，根据PDCP PDU生成第二中继PDU，将第二中继PDU发送给下一跳节点
其中，第二中继PDU为网络设备向远端终端发送的中继PDU，或者，第二中继PDU为网络设备广播的。下一跳节点是和网络设备直接相连接的中继终端。
步骤960：中继终端的中继接收实体接收上一跳节点发送的第二中继PDU，将第二中继PDU传递给中继发送实体。
其中，上一跳节点为网络设备，或者，上一跳节点是处于中继终端与网络设备之间的另一中继终端。
需要说明的是，中继接收实体确定第二中继PDU的协议头中还包括广播标识的情况下，将第二中继PDU递交给上层。
步骤970：中继终端的中继发送实体将第二中继PDU发送给下一跳节点。
其中，下一跳节点为远端终端，或者，下一跳节点是处于中继终端与远端终端之间的另一中继终端。
步骤980：远端终端的中继接收实体接收来自上一跳节点的第二中继PDU。
需要说明的是，中继接收实体确定第二中继PDU的协议头中的目的标识与本端标识相同的情况下，将第二中继PDU递交给上层。
可选地，中继接收实体确定第二中继PDU的协议头中还包括广播标识的情况下，将第二中继PDU递交给上层。
上述传输中继PDU的个过程中，需要说明的是，在上行方向上传输的是第一中继PDU，在下行方向上传输的是第二中继PDU。第一路由关系是是终端标识作为目的标识时的路由关系，也即是，第一路由关系是下行传输中的路由关系。第二路由关系是网络设备标识作为目的标识时的路由关系，也即是，第二路由关系是上行传输中的路由关系。
在本申请的中继方法实施例中，由于在远端终端、中继终端和网络设备的的协议栈中引入了新的中继协议层，该中继协议栈位于分组数据汇聚协议PDCP层与PC5接口的层2协议栈之间，或者，中继协议栈是媒体接入控制MAC层协议栈，中继协议栈包括中继发送实体和中继接收实体。中继接收实体用于接收上一跳节点发送的中继协议数据单元PDU，将中继PDU传递给中继发送实体；中继发送实体用于将中继PDU发送给下一跳节点；其中，中继PDU包括第一中继PDU和/或第二中继PDU，第一中继PDU是由远端终端发给网络设备的，第二中继PDU是由网络设备发给远端终端的，或者，第二中继PDU是由网络设备广播的。如此，在远端终端与网络设备之间，通过包含中继协议栈的中继终端可以自主确定中继PDU的下一跳节点，以将中继PDU从一端成功中继至另一端，无需网络设备配置关于无线承载和远端终端标识之间的映射关系，使得中继PDU的路由过程较为灵活。
此外，本申请中的中继方法不仅可以在分组数据汇聚协议PDCP层与层2协议栈之间引入新的中继协议栈来实现，也可以在MAC层实现中继协议的功能。参见图10中的协议栈的系统框图a所示的协议栈，或者,协议栈的系统框图b所示的协议栈，图10是本申请一个示例性实施例提供的一种协议栈的系统框图。
在Uu接口的MAC层引入用于标识终端的MAC CE。这个MAC CE的内容有两种可能，一种是终端在连接网络之前保存的网络分配的标识，这个标识可以是NAS层的STMSI,I-RNTI或者一个随机数，或者是这个UE标识的一部分内容，比如最低16比特位。另外一种是UE在连接到网络之后，网络新分配给终端的C-RNTI，上述终端为远端终端和中继终端。
除了采用MAC CE的内容作为终端标识之外，在MAC层实现中继协议的功能，还可以在于一个Uu接口的MAC PDU中可以同时包含多个的PDCP PDU，多个PDCP PDU可能属于不同的逻辑信道，并且不需要引入新的协议层，上述的中继协议层的功能在MAC层就实现了。
通过MAC PDU中的LCID，以及LCID和无线承载的对应关系，所以在MAC PDU中不需要额外的DRB ID。LCID和DRB ID之间的映射关系在RRC配置消息中进行规定。
需要说明的是，在MAC层实现中继协议的功能在路由建立和维护上，和PDCP层与PC5接口的层2 协议栈之间引入新的中继协议层的方案基本一致。区别在于终端的标识采用了MAC PDU中的终端标识MAC CE。当MAC PDU从子节点发送给父节点的时候，这个终端标识MAC CE被解释为源标识，相反则解释为目的标识。
在MAC层实现中继协议的功能在路由建立和维护上，参考上述PDCP层与PC5接口的层2协议栈之间引入新的中继协议层的方案，详见图5-图9所示的步骤流程图及详细解释，在此不再赘述。
图11是根据本申请一示例性实施例示出的一种路由表的生成方法的流程图，该路由表的生成方法可以应用于上述图1所示的通信系统中中继终端120，该路由表的生成方法可以包括如下内容中的至少部分内容：
步骤1110：接收来自远端终端的第一中继PDU，第一中继PDU包括远端终端的终端标识，第一中继PDU是远端终端发给网络设备的。
步骤1120：基于远端终端的终端标识和上一跳节点的节点标识，建立第一路由关系。
其中，上一跳节点是指中继终端的上一跳节点，且上一跳节点可以为远端终端，或者，上一跳节点可以为中继终端与远端终端之间的另一中继终端。
步骤1130：将第一中继PDU发送给下一跳节点。
其中，下一跳节点是指中继终端的下一跳节点，且下一跳节点为网络设备或者下一跳节点处于中继终端与网络设备之间，第一路由关系是终端标识作为目的标识时的路由关系。
需要说明的是，在上行方向上，在采用中继PDU格式1生成第一中继PDU后，在传输过程中，该第一中继PDU的协议头包括远端终端的终端标识，且该终端标识为第一中继PDU的源标识。当采用中继PDU格式2生成第一中继PDU后，在传输过程中，该第一中继PDU的协议头包括终端标识和网络设备标识，该终端标识为第一中继PDU的源标识，该网络设备标识为该第一中继PDU的目的标识，网络设备标识用于指示第一中继PDU需要传输到的网络设备。
同理，在下行方向上，在基于图11的可选实施例中，上述方法还包括：接收来自网络设备的第二中继PDU，第二中继PDU是由网络设备向远端终端发送的中继PDU，或者，第二中继PDU为网络设备广播的；根据第二中继PDU的协议头中的目的标识和所述第一路由关系，将所述第二中继PDU发给下一跳节点。其中，目的标识包括终端标识，或者，目的标识包括广播标识。
作为一个示例，参见图12，图12是本申请一个示例性实施例提供的一种中继过程示意图，应用于本申请提供的路由表的生成方法来请求和前转网络设备的系统消息等，该系统消息包括广播数据或广播信令。
在12所示的中继过程示意图中，远端终端的终端标识为：RMUE，中继终端的终端标识为：RLUE，网络设备的网络设备标识为：BS_ID。
远端终端检测发现中继终端的存在，想要接收中继终端所在服务小区的广播消息，用以判断是否可以在该服务小区获得服务，于是先和中继终端之间建立了PC5连接。远端终端发送第一中继PDU给中继终端，该第一中继PDU为RRC消息。该RRC消息用于请求接收系统消息。
第一中继PDU的协议头中可以包括：RMUE。
或者，第一中继PDU的协议头中可以包括RMUE和BS_ID，其中，该RMUE为该第一中继PDU的源标识，该BS_ID为该第一中继PDU的目的标识。
中继终端根据源标识，建立第一路由关系(RMUE,RMUE)，并在Uu接口和网络设备之间完成用于承载第一中继PDU的无线承载的建立或者重配过程。对中继终端而言，网络设备是上行唯一的节点，因此网络设备是缺省的下一跳节点，中继终端将该第一中继PDU发送给网络设备。
网络设备在收到这个第一中继PDU后，根据该第一中继PDU的协议头中的源标识，建立第三路由关系(RMUE，RLUE)，该第三路由关系表示发往远端终端RMUE的第二中继PDU通过中继终端RLUE来转发。
此外，在该第一中继PDU包括的目的标识不为空的情况下，网络设备根据目的标识，判断这个第一中继PDU是否是发送给自己的，若是，则网络设备把这个第一中继PDU投递给上层协议，如发给RRC层。
在下行过程中，网络设备可以基于上行建立的第三路由关系，进行发送消息的过程。上行路由和下行路由具有对称性。
作为一个示例，网络设备的RRC层经过处理以后决定在专用信道传递系统消息给远端终端，于是将系统消息根据已建立的第三路由关系，即(RMUE，RLUE)，把第二中继PDU发送给中继终端。
这个第二中继PDU的协议头中可以包括：终端标识，该终端标识为该第二中继PDU的目的标识。
或者，该第二中继PDU的协议头可以包括终端标识和网络设备标识，其中，该终端标识为该第二中继PDU的目的标识。该网络设备标识为该第二中继PDU的源标识。
进一步地，该第二中继PDU还可以包括广播标识，譬如，该广播标识可以为DESTINATION_BC，用 于指示该第二中继PDU包括广播数据或者广播信令等。
中继终端在收到这个第二中继PDU以后，根据目的标识判断这是一个广播消息，于是将该第二中继PDU包括的PDCP PDU和无线承载标识(或逻辑信道标识)投递给自己的RRC层进行处理，同时中继终端把这个第二中继PDU前转给远端终端。远端终端在收到这个第二中继PDU以后，同样根据目的标识判断这是一个广播消息，于是将该第二中继PDU包括的PDCP PDU和无线承载标识(或逻辑信道标识)投递给自己的RRC层进行处理。
可选地，第一中继PDU还包括无线承载标识或逻辑信道标识，无线承载标识为远端终端与网络设备之间的无线承载的标识。
可选地，当通过MAC层实现中继协议的功能时，第一中继PDU通过自媒体接入控制MAC层进行中继。
由于通信系统中存在父子节点关系，且所有的父子节点之间在建立父子关系时可以获知各自的标识。当连接中断或者更换链路时，父子关系都会发生变化，需要进行原本路由表的更新。因此，当一个节点的节点标识发生改变时，这个节点可以通知所有相邻节点进行更新，以便于各个节点对已建立的路由表进行自主更新。
因此，在基于图11的可选实施例中，若下一跳节点为网络设备，上述方法还包括：
在第一中继PDU包括CCCH(Common Control Channel，公共控制信道)消息的情况下，获取网络设备为自身分配的第一小区无线网络临时标识符C-RNTI(Cell Radio-Network Temporary Identifier，小区无线网络临时标识符)信息，将第一C-RNTI信息发送给上一跳节点。
其中，由于一个网络设备连接有多个中继终端，为了对不同的中继终端进行区分，在中继终端和网络设备将建立连接后，网络设备可以为接入的中继终端分配一个新的终端标识。
需要说明的是，当中继终端采用网络设备分配的新的终端标识时，需要将更新后的终端标识告知给其他相连的上一跳节点。其中，上一跳节点可以为远端终端，或者位于该中继终端和远端终端之间的中继终端。
可选地，上述方法还包括：接收来自远端终端的第二C-RNTI信息，第二C-RNTI信息是由网络设备为远端终端分配的，将第一路由关系中的终端标识更新为第二C-RNTI信息。
同理，当远端终端的终端标识更新时，需要告知与其进行通信的中继终端和网络设备，以便于中继终端和网络设备进行路由表的更新。
作为一个示例，如图13所示，图13是本申请另一个示例性实施例提供的一种中继过程示意图。
远端终端发送CCCH消息给网络开始建立或者恢复如上述图12所示的RRC连接，中继终端处于空闲态或者非激活状态。
图13所示的中继过程，用于解释如何在RRC连接建立、恢复或者重建的过程中建立路由表，以及如何前转来自远端终端的第一中继PDU给网络设备。
在13所示的中继过程示意图中，远端终端的原始标识是：RMUE，在建立RRC连接以后，网络设备为其分配的新的终端标识为：C-RNTI_M。中继终端的原始标识是：RLUE，在和网络设备建立Uu连接，网络设备为其分配的新的终端标识为：C-RNTI_L。假设网络设备的网络设备标识为：BS_ID。
在上行建立第二路由关系的过程中，远端终端和中继终端建立PC5连接，在PC5连接建立以后，远端终端可以获得中继终端的终端标识RLUE，此时远端终端记录一条路由关系(BS_ID，RLUE)，该路由关系的含义是：所有发送给网络设备的中继PDU都需要发送给终端标识为RLUE的中继终端。
远端终端发送包含CCCH消息的第一中继PDU给中继终端。其中，该第一中继PDU的协议头中可以包括：RMUE。
或者，第一中继PDU的协议头中可以包括RMUE和BS_ID，其中，该RMUE为该第一中继PDU的源标识，该BS_ID为该第一中继PDU的目的标识。
中继终端收到第一中继PDU以后，建立第一路由关系(RMUE，RMUE)。并和网络设备之间建立RRC连接和用于前转第一中继PDU的无线承载。对中继终端而言，网络设备是上行唯一的节点，因此网络设备是缺省的下一跳节点，中继终端将该第一中继PDU发送给网络设备，建立第二路由关系(BS_ID，BS_ID)。此外，网络设备在和中继终端建立连接后，网络设备会重新分配一个终端标识给中继终端。
作为一个示例，网络设备可以给中继终端分配第一C-RNTI信息，如该第一C-RNTI信息为C-RNTI_L，在图13所示中继过程示意图中，中继终端将自身的终端标识更新成C-RNTI_L。并将更新的终端标识告知给远端终端。中继终端将把包含CCCH消息的第一中继PDU前转给网络设备。
对于远端终端来说，在接收到该中继终端发送的C-RNTI_L后，将所记录的路由关系(BS_ID，RLUE)更改为(BS_ID，C-RNTI_L)。
对于网络设备来说，由于网络设备第一次收到源标识为RMUE的中继PDU，所以建立路由记录(RMUE，C-RNTI_L)。作为一示例，网络设备将CCCH消息投递给上层RRC协议层。
在下行通信的过程中，网络设备在处理了CCCH消息以后，发送包含RRC连接建立消息的第二中继PDU给中继终端。第二中继终端的协议头中可以包括远端终端的终端标识RMUE，或者，第二中继PDU的协议头中可以包括BS_ID和RMUE。其中，该BS_ID为该第二中继PDU的源标识，该RMUE为该第二中继PDU的目的标识。
可选地，根据CCCH消息的不同，网络设备也可以发送其他RRC消息，比如：RRC连接重建，或者RRC恢复消息给该中继终端。
中继终端在收到上述第二中继PDU以后，通过查询路由记录(RMUE，RMUE)，将第二中继PDU前转给远端终端。
远端终端在收到这个第二中继PDU以后，根据目的标识(即RMUE)，确定该第二中继PDU是发送给自己的，则将该第二中继PDU中的PDCU和无线承载标识(或逻辑信道标识)投递给RRC层协议。
此外，在收到的RRC连接建立消息中，网络设备给远端终端重新分配了一个新的终端标识，即第二中继PDU包括第二C-RNTI信息，作为一个示例，新的终端标识为C-RNTI_M。
远端终端的RRC层在处理了这个RRC消息以后，通过PC5信令将第二C-RNTI信息通知给上一跳节点的中继终端，中继终端接收该第二C-RNTI信息后，将第一路由关系(RMUE，RMUE)更新为(C-RNTI_M，C-RNTI_M)。
另外，当网络设备给远端终端分配了新的终端标识后，自身的路由也需要更新，也即是，当下次网络设备需要向远端终端传送第二中继PDU时，对应的目的标识应该由RMUE更新为C-RNTI_M。也即是，在远端终端把包含RRC连接完成消息的第一中继PDU发送给中继终端，该第一中继PDU包含的源标识为C-RNTI_M，目的标识为BS_ID。中继终端将该第一中继PDU发送给网络设备。
网络设备在收到这个第一中继PDU时，根据目的标识建立第三路由关系，譬如，该第三路由关系为(C-RNTI_M，C-RNTI_L)。到此为止，网络设备与远端终端之间的路由已完成建立。
作为一种示例，在路由关系更新之后，在下行传输的第二中继PDU的协议头中，源标识为BS_ID，目的标识为C-RNTI_M。而在上行传输的第一中继PDU的协议头中，源标识为C-RNTI_M，目的标识为BS_ID。
需要说明的是，图13所示的中继过程中所有中继PDU都是按照中继PDU的格式2来进行描述的。当采用格式1的中继PDU时，只需将上述中继PDU的协议头中的BS_ID省略就即可。而中继PDU的协议头中包含的目的标识是远端终端还是网络设备是根据中继PDU发送的方向来判决的。
综上所述，本申请提供的路由表的建立方法，不仅可以实现路由关系的自主建立，此外，还可以根据RRC连接状态连接到网络设备的中继终端和远端终端的终端标识进行修改，中继方案的灵活性有所提高。
因此，在基于图11的可选实施例中，第一中继PDU还包括指示信息，该指示信息用于指示中继终端与网络设备的无线承载的PDCP实体所在的小区组。
可选地，网络设备标识还包括小区组标识，小区组标识用于指示中继终端与网络设备的无线承载的PDCP实体所在的小区组。
可选地，小区组包括主小区组MCG或辅小区组SCG。
也即是，由于中继终端和网络设备之间可能存在双连接的情况，也即是，中继终端在和网络设备通信时需要确定将第一中继PDU发送至哪个小区组。
作为一种示例，在RRC重配置过程之前，上行的消息都缺省路由到MCG上。RRC重配过程之后，有的DRB的PDCP实体配置在MCG上，有的配置在SCG上。远端终端根据RRC重配置消息上的配置信息，在生成第一中继PDU的时候，如果是路由到MCG上的，那么在第一中继PDU的协议头中标注用于指示MCG的标识，譬如，该标识可以是主小区组标识，如果是路由到SCG上的，那么在第一中继PDU的协议头中标注用于指示SCG的标识，譬如，该标识可以是辅小区组标识。
参见图14，图14是本申请另一个示例性实施例提供的一种中继过程示意图。
和示例13比较，本示例的不同之处在于，远端终端通过2个中继终端连接到网络设备，中继PDU的格式可以采用格式1和格式2。本示例基于中继PDU格式1进行解释说明。本示例同样适用于中继PDU格式2，仅需在每个中继PDU的协议头中添加一个网络设备标识即可，譬如，在上行传输的第一中继PDU中，该网络设备标识为目的标识，在下行传输的第二中继PDU中，该网络设备标识为源标识。
本示例中，为了让中继终端2能够判断从远端终端来的第一中继PDU是如何路由的，在第一中继PDU的协议头中包含指示信息，该指示信息用于指示该第一中继PDU是发送给MCG的还是发送给SCG的。
需要说明的是，如果不存在这个指示信息，那么中继终端2会把第一中继PDU前转给MCG。远端终端和网络设备之间的无线承载的PDCP实体如果配置在MCG(SCG)上，则上下行的中继PDU就在远端终端和MCG(SCG)之间进行传递。其中，无线承载的路由是固定的，如SRB0、SRB1和SRB2的PDCP实体配置在MCG上，而SRB3的PDCP实体配置在SCG上。
本示例的具体中继过程如图13所示。远端终端的路由建立过程和图13所示过程类似，就不再赘述。
此外，若中继PDU的格式采用格式2，则，可以直接采用MCG(SCG)的标识来进行指示。比如，MCG的小区组标识为MCG_ID，SCG的小区组标识为SCG_ID，该标识可以包括在网络设备标识中。如此，在RRC重配置之前，所有的信令和数据都缺省在远端终端和MCG之间，在RRC重配置消息中，远端终端根据PDCP实体所在，分别把上行的中继PDU的协议头中的目的标识设置为MCG_ID或者SCG_ID。中继终端2需要根据不同的目的标识来确定正确的路由。
进一步地，第一中继PDU包括切换消息，切换消息用于触发中继终端与目标小区建立连接，目标小区为切换后的小区。
也即是，若远端终端已经和源网络设备建立Uu接口的无线链路。随着远端终端逐渐移动出源网络设备的覆盖范围，远端终端通过测量发现存在另一个可用的中继终端，于是向源网络设备发送了测量报告，远端终端请求从Uu接口切换到一个中继链路。
参见图15，图15是本申请另一个示例性实施例提供的一种中继过程示意图。在本示例中，远端终端的终端标识C-RNTI_M，中继终端的终端标识为C_RNTI_L，网络设备的网络设备标识为BS_ID。作为一个示例，当远端终端需要从Uu接口切换到一个中继链路时，在发送测量报告之前，远端终端已经知道中继终端所在的目标服务小区，并且把目标服务小区作为测量结果的一部分报告给源网络设备。
源网络设备和目标服务小区所在的目标网络设备按照惯常的小区切换流程进行切换消息的交互，并且把切换命令发送给了远端终端。
可选地，为了减少切换的时延，远端终端在接收到切换命令之前，可以预先和中继终端之间建立PC5连接。在收到切换命令之后，远端终端把包含切换完成消息的第一中继PDU发送给中继终端。假设该第一中继PDU是采用上述格式1的方式生成的。
这个第一中继PDU的到达触发了中继终端和目标网络设备之间建立RRC连接和中继无线承载的过程，并且中继终端在自身的上行路由表和下行路由表中分别增加路由记录，即(BS_ID，BS_ID)和(C-RNTI_M，C-RNTI_M)。如果中继终端已经和目标网络设备建立Uu接口的连接，那么只需要增加传递中继PDU的无线承载即可，不用再建立路由关系。
中继终端将包含切换完成消息的第一中继PDU发送给了目标网络设备。目标网络设备在收到该第一中继PDU以后，建立第三路由关系(C_RNTI_M，C_RNTI_L)。
可选地，为了进一步降低切换时延，远端终端和目标网络设备之间的连接也可以提前建立。
可选地，测量报告中也可以包括提示信息，比如告诉源网络设备切换到目标网络设备的时候需要通过一个中继终端间接连接到目标网络设备。目标网络设备可以根据这样的提示信息来优化切换命令的内容，比如省略RLC层和以及RLC层以下协议的配置参数，并且把切换执行保护的时间进行适当的延长，以保护切换的顺利完成。
需要说明的是，本示例是以中继PDU格式1进行描述的，但同样适用于中继PDU格式2。当采用中继PDU格式2时，在上行传输的中继PDU协议头中需要增加目标网络设备的网络设备标识BS_ID作为目的标识，在下行传输的中继PDU协议头中需要增加目标网络设备的网络设备标识BS_ID作为源标识。
综上所述，本申请提供的路由表生成方法，当接收或发送一个中继PDU时，中继终端根据该中继PDU的协议头和路由表中的路由关系确定该中继PDU的下一跳节点，传输中继PDU的过程更为灵活，且根据路由表可以定义中继PDU的传输路由，在一定程度上也缓解了无线承载传输数据包时拥堵情况的发生，以及丢包等情况，中继方案更灵活高效。此外，上述路由表的生成过程不仅适用于中继终端，也适用于远端终端和网络设备。
图16是根据本申请另一示例性实施例示出的一种路由表的生成方法的流程图，该路由表的生成方法可以应用于上述图1所示的通信系统中网络设备110，该路由表的建立方法可以包括如下内容中的至少部分内容：
步骤1610：接收来自远端终端的第一中继PDU，第一中继PDU的协议头包括远端终端的终端标识，第一中继PDU是远端终端向网络设备发送的中继PDU。
需要说明的是，第一中继PDU包括PDCP PDU和无线承载标识，无线承载标识指示的无线承载为远端终端与网络设备之间的无线承载，第一中继PDU包括无线承载的数据包；或者，第一中继PDU包括PDCP PDU和逻辑信道标识。
此外，对于接收的第一中继PDU，若第一中继PDU采用中继PDU格式1，则在第一中继PDU的目的标识为空的情况下，将PDCP PDU和无线承载标识递交给上层，或者，将PDCP PDU和逻辑信道标识递交给上层。
对于接收的第一中继PDU，若第一中继PDU采用中继PDU格式2，则在第一中继PDU的目的标识不为空的情况下，若第一中继PDU的目的标识与本端标识相同，将PDCP PDU和无线承载标识递交给上层，或者，将PDCP PDU和逻辑信道标识递交给上层。
步骤1620：建立第三路由关系，第三路由关系包括终端标识和网络设备的上一跳节点的节点标识，第 三路由关系是终端标识作为目的标识时的路由关系。
需要说明的是，由于该第三路由关系是网络设备建立的，所以，为了与中继终端建立的第二路由关系进行区分，这里可以重新命名为第三路由关系。
其中，第三路由关系的建立，与上述第一路由关系和第二路由关系的建立过程类似，路由关系的过程参见上述图11所示的路由表的生成方法流程图和详细步骤实施例，在此不再赘述。
综上所述，本申请提供的路由表建立方法，接收来自远端终端的第一中继PDU，第一中继PDU的协议头包括远端终端的终端标识，第一中继PDU是远端终端向网络设备发送的中继PDU。建立第三路由关系，第三路由关系包括终端标识和网络设备的上一跳节点的节点标识，第三路由关系是终端标识作为目的标识时的路由关系。如此，在后续通信过程中，网络设备可以根据建立第三的路由关系确定发送给远端终端的第二中继PDU应该通过哪一个中继终端去传输，在此过程中，无需网络设备预先配置关于无线承载和远端终端标识之间的映射关系，使得传输第一中继PDU的路由过程较为灵活。
图17是根据一示例性实施例示出的一种中继装置的结构示意图，该装置1700可以配置于中继终端中，该中继装置包括中继协议栈，中继协议栈位于分组数据汇聚协议PDCP层与PC5接口的协议栈之间或者，中继协议栈是媒体接入控制MAC层协议栈，中继协议栈包括中继接收模块1710和中继发送模块1720，装置1700包括：
中继接收模块1710用于接收上一跳节点发送的中继协议数据单元PDU，将中继PDU传递给中继发送模块；
中继发送模块1720用于将中继PDU发送给下一跳节点；
可选地，该中继PDU包括第一中继PDU，第一中继PDU的协议头包括：远端终端的终端标识，终端标识为第一中继PDU的源标识。
可选地，第一中继PDU的协议头还包括：网络设备的网络设备标识，网络设备标识为第一中继PDU的目的标识。
可选地，该中继PDU包括第二中继PDU，第二中继PDU的协议头包括：远端终端的终端标识，终端标识为第二中继PDU的目的标识。
可选地，第二中继PDU的协议头包括：广播标识，广播标识为第二中继PDU的目的标识。
可选地，第二中继PDU的协议头还包括：源标识，源标识为网络设备的网络设备标识。
可选地，在中继协议栈位于PDCP层与层2协议栈之间的情况下，第一中继PDU的协议头还包括：无线承载标识，无线承载标识为远端终端与网络设备之间的无线承载的标识；
在中继协议栈是MAC层协议栈的情况下，第一中继PDU还包括：逻辑信道标识。
可选地，第一中继PDU还包括指示信息，指示信息用于指示中继终端与网络设备的无线承载的分组数据汇聚协议PDCP实体所在的小区组。
可选地，网络设备标识还包括小区组标识，小区组标识用于指示中继终端与网络设备的无线承载的PDCP实体所在的小区组。
可选地，小区组包括主小区组MCG或辅小区组SCG。
可选地，上一跳节点为远端终端，或者，上一跳节点是处于中继终端与远端终端之间的另一中继终端；
中继接收模块1710，还用于：在下行路由表不包括远端终端的终端标识对应的路由关系的情况下，在下行路由表中建立第一路由关系，第一路由关系包括终端标识和上一跳节点的节点标识，第一路由关系是终端标识作为目的标识时的路由关系。
可选地，该中继PDU包括第一中继PDU，中继发送模块1720用于将第一中继PDU发送给下一跳节点，包括：
中继发送模块1720用于将第一中继PDU发送给缺省的下一跳节点。
可选地，该中继PDU包括第一中继PDU，在第一中继PDU的协议头包括网络设备标识的情况下，中继发送模块1720用于在上行路由表中建立第二路由关系，第二路由关系包括网络设备标识和下一跳节点的节点标识，第二路由关系是网络设备标识作为目的标识时的路由关系。
可选地，该中继PDU包括第二中继PDU，上一跳节点为网络设备，或者，中继终端的上一跳节点为处于网络设备与中继终端之间的另一中继终端；
中继接收模块1710，还用于：根据第二中继PDU的协议头中的终端标识，从下行路由表中确定终端标识对应的第一路由关系；
中继接收模块1710，还用于：将第一路由关系中，终端标识对应的节点标识指示的节点确定为下一跳节点。
可选地，第二中继PDU包括参考标识和PDCP PDU，参考标识包括无线承载标识或逻辑信道标识；
在第二中继PDU的协议头还包括广播标识的情况下，中继接收模块还用于将第二中继PDU中的参考标识和PDCP PDU递交给上层。
可选地，在中继终端与网络设备交互的情况下，层2协议栈包括Uu接口的层2协议栈；
在中继终端与另一中继终端交互的情况下，或者，在中继终端与远端终端交互的情况下，层2协议栈包括PC5接口的层2协议栈。
可选地，层2协议栈包括无线链路控制RLC层协议栈和媒体接入控制MAC层协议栈。
本实施例提供的中继方法应用于中继终端中，中继终端包括中继协议栈，中继协议栈位于分组数据汇聚协议PDCP层与层2协议栈之间，或者，中继协议栈是媒体接入控制MAC层协议栈，中继协议栈包括中继接收实体和中继发送实体。中继接收实体用于接收上一跳节点发送的中继协议数据单元PDU，将中继PDU传递给中继发送实体；中继发送实体用于将中继PDU发送给下一跳节点。如此，在远端设备与网络设备之间，通过包含中继协议栈的中继终端可以自主确定中继PDU的下一跳节点，以将中继PDU从一端成功中继至另一端，无需网络设备配置关于无线承载和远端终端标识之间的映射关系，使得中继PDU的路由过程较为灵活。
图18是根据一示例性实施例示出的一种中继装置的结构示意图，该装置1800可以配置于远端终端中，该中继装置包括中继协议栈，中继协议栈位于分组数据汇聚协议PDCP层与PC5接口的协议栈之间或者，中继协议栈是MAC层协议栈，中继协议栈包括中继发送模块1810，该装置1800可以包括：
中继发送模块1810用于接收PDCP层发送的PDCP PDU，根据PDCP PDU生成第一中继PDU，将第一中继PDU发送给下一跳节点；
其中，第一中继PDU是远端终端向网络设备发送的中继PDU。
可选地，中继协议栈还包括中继接收模块1820，中继接收模块1820用于接收来自上一跳节点的第二中继PDU，第二中继PDU是网络设备向远端终端发送的中继PDU，或者，第二中继PDU是由网络设备广播的。
可选地，第二中继PDU包括参考标识和PDCP PDU，参考标识包括无线承载标识或逻辑信道标识；
中继接收模块1820还用于在确定第二中继PDU的协议头中的目的标识与本端标识相同的情况下，将第二中继PDU包括参考标识和PDCP PDU递交给上层。
可选地，第二中继PDU包括参考标识和PDCP PDU，参考标识包括无线承载标识或逻辑信道标识；
中继接收模块1820还用于在确定第二中继PDU的协议头中还包括广播标识的情况下，将第二中继PDU包括的参考标识和PDCP PDU递交给上层。
可选地，第一中继PDU的协议头包括：远端终端的终端标识，终端标识为第一中继PDU的源标识。
可选地，第一中继PDU的协议头还包括：网络设备的网络设备标识；
网络设备标识为第一中继PDU的目的标识。
在本申请实施例提供的中继方法应用于远端终端中，远端终端包括中继协议栈，中继协议栈位于分组数据汇聚协议PDCP层与PC5接口的层2协议栈之间，或者，中继协议栈是媒体接入控制MAC层协议栈，中继协议栈包括中继发送实体。中继发送实体用于接收PDCP层发送的PDCP PDU，根据PDCP PDU生成第一中继PDU，将第一中继PDU发送给下一跳节点。其中，第一中继PDU是远端终端向网络设备发送的中继PDU。也即是，在远端终端可以自主确定第一中继PDU的下一跳节点，以将第一中继PDU发往网络设备端，在此过程中，无需网络设备配置关于无线承载和远端终端标识之间的映射关系，使得传输第一中继PDU的路由过程较为灵活。
图19是根据一示例性实施例示出的一种中继装置的结构示意图，该装置1900可以配置于网络设备中，该中继装置包括中继协议栈，中继协议栈位于分组数据汇聚协议PDCP层与PC5接口的协议栈之间，或者，中继协议栈是MAC层协议栈，中继协议栈包括中继接收模块1910和中继发送模块1920，该装置1900可以包括：
中继接收模块1910用于接收来自上一跳节点的第一中继PDU，第一中继PDU是由远端终端发给网络设备的。
可选地，在中继协议栈位于PDCP层与层2协议栈之间的情况下，第一中继PDU的协议头还包括：无线承载标识，无线承载标识为远端终端与网络设备之间的无线承载的标识；
在中继协议栈是MAC层协议栈的情况下，第一中继PDU还包括：逻辑信道标识。
可选地，若第一中继PDU的目的标识不为空，中继接收模块1910还用于在第一中继PDU的目的标识与本端标识相同的情况下，将第一中继PDU包括的PDCP PDU和无线承载标识递交给上层。
可选地，若第一中继PDU的目的标识为空，中继接收模块1910还用于将第一中继PDU包括的PDCPPDU和无线承载标识递交给上层，或者，将第一中继PDU包括的PDCP PDU和逻辑信道标识递交给上层。
可选地，中继协议栈还包括中继发送模块1920，装置1900还包括：
中继发送模块1920用于接收PDCP层发送的PDCP PDU，根据PDCP PDU生成第二中继PDU，将第二中继PDU发送给下一跳节点；
其中，第二中继PDU为网络设备向远端终端发送的中继PDU，或者，第二中继PDU为网络设备广播 的。
可选地，第二中继PDU的协议头还包括：远端终端的终端标识，终端标识为第二中继PDU的目的标识。
可选地，第二中继PDU还包括广播标识，广播标识用于指示第二中继PDU包括广播数据或广播信令。
在本申请实施例提供的中继方法应用于网络设备中，网络设备包括中继协议栈，中继协议栈位于分组数据汇聚协议PDCP层与Uu接口的层2协议栈之间，或者，中继协议栈是媒体接入控制MAC层协议栈，中继协议栈包括中继接收实体，中继接收实体用于接收来自上一跳节点的第一中继PDU，第一中继PDU是由远端终端发给网络设备的。中继发送实体用于接收PDCP层发送的PDCP PDU，根据PDCP PDU生成第二中继PDU，将第二中继PDU发送给下一跳节点。网络设备可以自主确定第二中继PDU的下一跳节点，以将第二中继PDU发往远端终端，在此过程中，无需网络设备预先配置关于无线承载和远端终端标识之间的映射关系，使得传输第二中继PDU的路由过程较为灵活。
图20是根据一示例性实施例示出的一种路由表的生成装置的结构示意图，该装置2000可以配置于中继终端中，该装置2000可以包括：
接收模块2010，用于接收来自远端终端的第一中继协议数据单元PDU，第一中继PDU包括远端终端的终端标识，第一中继PDU是远端终端发给网络设备的；
路由建立模块2020，用于基于远端终端的终端标识和上一跳节点的节点标识，建立第一路由关系，第一路由关系是终端标识作为目的标识时的路由关系。
可选地，第一中继PDU还包括网络设备标识，网络设备标识为第一中继PDU的目的标识，网络设备标识用于指示第一中继PDU需要传输到的网络设备。
可选地，第一中继PDU还包括无线承载标识或逻辑信道标识，无线承载标识为远端终端与网络设备之间的无线承载的标识。
可选地，第一中继PDU还包括指示信息，指示信息用于指示中继终端与网络设备的无线承载的分组数据汇聚协议PDCP实体所在的小区组。
可选地，网络设备标识还包括小区组标识，小区组标识用于指示中继终端与网络设备的无线承载的PDCP实体所在的小区组。
可选地，小区组包括主小区组MCG或辅小区组SCG。
可选地，下一跳节点为网络设备，该装置还包括发送模块2030，发送模块2030用于：
在第一中继PDU包括公共控制信道CCCH消息的情况下，获取网络设备为自身分配的第一小区无线网络临时标识符C-RNTI信息；
将第一C-RNTI信息发送给上一跳节点。
可选地，所述接收模块2010，还用于：
接收来自远端终端的第二C-RNTI信息，第二C-RNTI信息是由网络设备为远端终端分配的；
将第一路由关系中的终端标识更新为第二C-RNTI信息。
可选地，第一中继PDU包括切换消息，切换消息用于触发中继终端与目标小区建立连接，目标小区为切换后的小区。
可选地，
所述接收模块2010，还用于接收来自网络设备的第二中继PDU，第二中继PDU是由网络设备向远端终端发送的中继PDU，或者，第二中继PDU为网络设备广播的；
所述发送模块2030，用于根据第二中继PDU的协议头中的目的标识和第一路由关系，将第二中继PDU发给下一跳节点。
可选地，目的标识包括终端标识；或者，目的标识包括广播标识。
综上所述，本申请提供的路由表生成方法，当接收或发送一个中继PDU时，中继终端根据该中继PDU的协议头和路由表中的路由关系确定该中继PDU的下一跳节点，传输中继PDU的过程更为灵活，且根据路由表可以定义中继PDU的传输路由，在一定程度上也缓解了无线承载传输数据包时拥堵情况的发生，以及丢包等情况，中继方案更灵活高效。此外，上述路由表的生成过程不仅适用于中继终端，也适用于远端终端和网络设备。
图21是根据另一示例性实施例示出的一种路由表的生成装置的结构示意图，该装置2100可以配置于网络设备中，该装置2100可以包括：
接收模块2110，用于接收来自远端终端的第一中继PDU，第一中继PDU的协议头包括远端终端的终端标识，第一中继PDU是远端终端向网络设备发送的中继PDU；
路由建立模块2120，用于建立第三路由关系，第三路由关系包括终端标识和网络设备的上一跳节点的节点标识，第三路由关系是终端标识作为目的标识时的路由关系。
可选地，第一中继PDU包括PDCP PDU和无线承载标识，无线承载标识指示的无线承载为远端终端 与网络设备之间的无线承载，第一中继PDU包括无线承载的数据包；或者，
第一中继PDU包括PDCP PDU和逻辑信道标识。
可选地，装置2100还包括：
递交模块2130，用于在第一中继PDU的目的标识为空的情况下，将PDCP PDU和无线承载标识递交给上层，或者，将PDCP PDU和逻辑信道标识递交给上层。
可选地，装置2100还包括：
所述递交模块2130，用于在第一中继PDU的目的标识不为空的情况下，若第一中继PDU的目的标识与本端标识相同，将PDCP PDU和无线承载标识递交给上层。
综上所述，本申请提供的路由表建立方法，接收来自远端终端的第一中继PDU，第一中继PDU的协议头包括远端终端的终端标识，第一中继PDU是远端终端向网络设备发送的中继PDU。建立第三路由关系，第三路由关系包括终端标识和网络设备的上一跳节点的节点标识，第三路由关系是终端标识作为目的标识时的路由关系。如此，在后续通信过程中，网络设备可以根据建立第三的路由关系确定发送给远端终端的第二中继PDU应该通过哪一个中继终端去传输，在此过程中，无需网络设备预先配置关于无线承载和远端终端标识之间的映射关系，使得传输第一中继PDU的路由过程较为灵活。
请参考图22，其示出了本申请一个示例性实施例提供的通信设备(终端或接入网设备)的结构示意图，该通信设备包括：处理器1201、接收器1202、发射器1203、存储器1204和总线1205。
处理器1201包括一个或者一个以上处理核心，处理器1201通过运行软件程序以及模块，从而执行各种功能应用以及信息处理。
接收器1202和发射器1203可以实现为一个通信组件，该通信组件可以是一块通信芯片。
存储器1204通过总线1205与处理器1201相连。
存储器1204可用于存储至少一个指令，处理器1201用于执行该至少一个指令，以实现上述各个方法实施例中的终端和网络设备执行的各个步骤。
此外，存储器1204可以由任何类型的易失性或非易失性存储设备或者它们的组合实现，易失性或非易失性存储设备包括但不限于：磁盘或光盘，电可擦除可编程只读存储器(EEPROM)，可擦除可编程只读存储器(EPROM)，静态随时存取存储器(SRAM)，只读存储器(ROM)，磁存储器，快闪存储器，可编程只读存储器(PROM)。
本申请提供了一种计算机可读存储介质，所述存储介质中存储有至少一条指令，所述至少一条指令由所述处理器加载并执行以实现上述各个方法实施例提供的中继方法和路由表的生成方法。
本申请还提供了一种计算机程序产品，当计算机程序产品在计算机上运行时，使得计算机执行上述各个方法实施例提供的中继方法和路由表的生成方法。
本领域技术人员应该可以意识到，在上述一个或多个示例中，本申请实施例所描述的功能可以用硬件、软件、固件或它们的任意组合来实现。当使用软件实现时，可以将这些功能存储在计算机可读介质中或者作为计算机可读介质上的一个或多个指令或代码进行传输。计算机可读介质包括计算机存储介质和通信介质，其中通信介质包括便于从一个地方向另一个地方传送计算机程序的任何介质。存储介质可以是通用或专用计算机能够存取的任何可用介质。
以上所述仅为本申请的可选实施例，并不用以限制本申请，凡在本申请的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本申请的保护范围之内。

Claims (98)

  1. 一种中继方法，其特征在于，应用于中继终端，所述中继终端包括中继协议栈，所述中继协议栈位于分组数据汇聚协议PDCP层与层2协议栈之间，或者，所述中继协议栈是媒体接入控制MAC层协议栈，所述中继协议栈包括中继接收实体和中继发送实体，所述方法包括：
    所述中继接收实体用于接收上一跳节点发送的中继协议数据单元PDU，将所述中继PDU传递给所述中继发送实体；
    所述中继发送实体用于将所述中继PDU发送给下一跳节点。
  2. 如权利要求1所述的方法，其特征在于，所述中继PDU包括第一中继PDU，所述第一中继PDU的协议头包括：所述远端终端的终端标识，所述终端标识为所述第一中继PDU的源标识。
  3. 如权利要求2所述的方法，其特征在于，所述第一中继PDU的协议头还包括：所述网络设备的网络设备标识，所述网络设备标识为所述第一中继PDU的目的标识。
  4. 如权利要求1所述的方法，其特征在于，所述中继PDU包括第二中继PDU，所述第二中继PDU的协议头包括：所述远端终端的终端标识，所述终端标识为所述第二中继PDU的目的标识。
  5. 如权利要求4所述的方法，其特征在于，所述第二中继PDU的协议头包括：广播标识，所述广播标识为所述第二中继PDU的目的标识。
  6. 如权利要求4或5所述的方法，其特征在于，所述第二中继PDU的协议头还包括：源标识，所述源标识为所述网络设备的网络设备标识。
  7. 如权利要求2或3所述的方法，其特征在于，
    在所述中继协议栈位于PDCP层与层2协议栈之间的情况下，所述第一中继PDU的协议头还包括：无线承载标识，所述无线承载标识为所述远端终端与所述网络设备之间的无线承载的标识；
    在所述中继协议栈是MAC层协议栈的情况下，所述第一中继PDU还包括：逻辑信道标识。
  8. 如权利要求2、3或7所述的方法，其特征在于，所述第一中继PDU还包括指示信息，所述指示信息用于指示所述中继终端与网络设备的无线承载的分组数据汇聚协议PDCP实体所在的小区组。
  9. 如权利要求3所述的方法，其特征在于，所述网络设备标识还包括小区组标识，所述小区组标识用于指示所述中继终端与所述网络设备的无线承载的PDCP实体所在的小区组。
  10. 如权利要求8或9所述的方法，其特征在于，所述小区组包括主小区组MCG或辅小区组SCG。
  11. 如权利要求1-10中任一项所述的方法，其特征在于，所述上一跳节点为所述远端终端，或者，所述上一跳节点是处于所述中继终端与所述远端终端之间的另一中继终端；
    所述中继接收实体，还用于：在下行路由表不包括所述远端终端的终端标识对应的路由关系的情况下，在所述下行路由表中建立第一路由关系，所述第一路由关系包括所述终端标识和所述上一跳节点的节点标识，所述第一路由关系是所述终端标识作为目的标识时的路由关系。
  12. 如权利要求11所述的方法，其特征在于，所述中继PDU包括第一中继PDU，所述中继发送实体用于将所述第一中继PDU发送给下一跳节点，包括：
    所述中继发送实体用于将所述第一中继PDU发送给缺省的下一跳节点。
  13. 如权利要求11所述的方法，其特征在于，所述中继PDU包括第一中继PDU，在所述第一中继PDU的协议头包括网络设备标识的情况下，所述方法还包括：
    所述中继发送实体用于在上行路由表中建立第二路由关系，所述第二路由关系包括所述网络设备标识和所述下一跳节点的节点标识，所述第二路由关系是所述网络设备标识作为目的标识时的路由关系。
  14. 如权利要求1-11所述的方法，其特征在于，所述中继PDU包括第二中继PDU，所述上一跳节点为网络设备，或者，所述中继终端的上一跳节点为处于所述网络设备与所述中继终端之间的另一中继终端；
    所述中继接收实体，还用于：根据所述第二中继PDU的协议头中的终端标识，从所述下行路由表中确定所述终端标识对应的第一路由关系；
    所述中继接收实体，还用于：将所述第一路由关系中，所述终端标识对应的节点标识指示的节点确定为所述下一跳节点。
  15. 如权利要求14所述的方法，其特征在于，所述第二中继PDU包括参考标识和PDCP PDU，所述参考标识包括无线承载标识或逻辑信道标识；
    在所述第二中继PDU的协议头还包括广播标识的情况下，所述中继接收实体还用于将所述第二中继PDU中的参考标识和PDCP PDU递交给上层。
  16. 如权利要求1-15中任一项所述的方法，其特征在于，
    在所述中继终端与所述网络设备交互的情况下，所述层2协议栈包括Uu接口的层2协议栈；
    在所述中继终端与另一中继终端交互的情况下，或者，在所述中继终端与远端终端交互的情况下，所 述层2协议栈包括PC5接口的层2协议栈。
  17. 如权利要求1或16所述的方法，其特征在于，所述层2协议栈包括无线链路控制RLC层协议栈和媒体接入控制MAC层协议栈。
  18. 一种中继方法，其特征在于，应用于远端终端，所述远端终端包括中继协议栈，所述中继协议栈位于分组数据汇聚协议PDCP层与PC5接口的层2协议栈之间，或者，所述中继协议栈是MAC层协议栈，所述中继协议栈包括中继发送实体，所述方法包括：
    所述中继发送实体用于接收所述PDCP层发送的PDCP PDU，根据所述PDCP PDU生成第一中继PDU，将所述第一中继PDU发送给下一跳节点；
    其中，所述第一中继PDU是所述远端终端向网络设备发送的中继PDU。
  19. 如权利要求18所述的方法，其特征在于，所述中继协议栈还包括中继接收实体，所述方法还包括：
    所述中继接收实体用于接收来自上一跳节点的第二中继PDU，所述第二中继PDU是所述网络设备向所述远端终端发送的中继PDU，或者，所述第二中继PDU是由所述网络设备广播的。
  20. 如权利要求19所述的方法，其特征在于，所述第二中继PDU包括参考标识和PDCP PDU，所述参考标识包括无线承载标识或逻辑信道标识，所述方法还包括：
    所述中继接收实体还用于在确定所述第二中继PDU的协议头中的目的标识与本端标识相同的情况下，将所述第二中继PDU包括参考标识和PDCP PDU递交给上层。
  21. 如权利要求19所述的方法，其特征在于，所述第二中继PDU包括参考标识和PDCP PDU，所述参考标识包括无线承载标识或逻辑信道标识，所述方法还包括：
    所述中继接收实体还用于在确定所述第二中继PDU的协议头中还包括广播标识的情况下，将所述第二中继PDU包括的参考标识和PDCP PDU递交给上层。
  22. 如权利要求18所述的方法，其特征在于，所述第一中继PDU的协议头包括：所述远端终端的终端标识，所述终端标识为所述第一中继PDU的源标识。
  23. 如权利要求22所述的方法，其特征在于，所述第一中继PDU的协议头还包括：所述网络设备的网络设备标识；
    所述网络设备标识为所述第一中继PDU的目的标识。
  24. 一种中继方法，其特征在于，应用于网络设备，所述网络设备包括中继协议栈，所述中继协议栈位于分组数据汇聚协议PDCP层与Uu接口的层2协议栈之间，或者，所述中继协议栈是MAC层协议栈，所述中继协议栈包括中继接收实体，所述方法包括：
    所述中继接收实体用于接收来自上一跳节点的第一中继PDU，所述第一中继PDU是由所述远端终端发给所述网络设备的。
  25. 如权利要求24所述的方法，其特征在于，
    在所述中继协议栈位于PDCP层与层2协议栈之间的情况下，所述第一中继PDU的协议头还包括：无线承载标识，所述无线承载标识为所述远端终端与所述网络设备之间的无线承载的标识；
    在所述中继协议栈是MAC层协议栈的情况下，所述第一中继PDU还包括：逻辑信道标识。
  26. 如权利要求25所述的方法，其特征在于，若所述第一中继PDU的目的标识不为空，所述中继接收实体还用于在所述第一中继PDU的目的标识与本端标识相同的情况下，将所述第一中继PDU包括的PDCP PDU和所述无线承载标识递交给上层。
  27. 如权利要求25所述的方法，其特征在于，若所述第一中继PDU的目的标识为空，所述中继接收实体还用于将所述第一中继PDU包括的PDCP PDU和所述无线承载标识递交给上层，或者，将所述第一中继PDU包括的PDCP PDU和所述逻辑信道标识递交给上层。
  28. 如权利要求24所述的方法，其特征在于，所述中继协议栈还包括中继发送实体，所述方法还包括：
    所述中继发送实体用于接收所述PDCP层发送的PDCP PDU，根据所述PDCP PDU生成第二中继PDU，将所述第二中继PDU发送给下一跳节点；
    其中，所述第二中继PDU为所述网络设备向所述远端终端发送的中继PDU，或者，所述第二中继PDU为所述网络设备广播的。
  29. 如权利要求28所述的方法，其特征在于，所述第二中继PDU的协议头还包括：所述远端终端的终端标识，所述终端标识为所述第二中继PDU的目的标识。
  30. 如权利要求28所述的方法，其特征在于，所述第二中继PDU还包括广播标识，所述广播标识用于指示所述第二中继PDU包括广播数据或广播信令。
  31. 一种路由表的生成方法，其特征在于，所述方法包括：
    接收来自远端终端的第一中继协议数据单元PDU，所述第一中继PDU包括所述远端终端的终端标识，所述第一中继PDU是所述远端终端发给所述网络设备的；
    基于所述远端终端的终端标识和上一跳节点的节点标识，建立第一路由关系，所述第一路由关系是所述终端标识作为目的标识时的路由关系。
  32. 如权利要求31所述的方法，其特征在于，在所述路由表的生成方法应用于中继终端的情况下，所述方法还包括：
    将所述第一中继PDU发送给下一跳节点。
  33. 如权利要求32所述的方法，其特征在于，所述第一中继PDU还包括网络设备标识，所述网络设备标识为所述第一中继PDU的目的标识，所述网络设备标识用于指示所述第一中继PDU需要传输到的网络设备。
  34. 如权利要求32或33所述的方法，其特征在于，所述第一中继PDU还包括无线承载标识或逻辑信道标识，所述无线承载标识为所述远端终端与网络设备之间的无线承载的标识。
  35. 如权利要求32-34中任一项所述的方法，其特征在于，所述第一中继PDU还包括指示信息，所述指示信息用于指示所述中继终端与网络设备的无线承载的分组数据汇聚协议PDCP实体所在的小区组。
  36. 如权利要求33所述的方法，其特征在于，所述网络设备标识还包括小区组标识，所述小区组标识用于指示所述中继终端与网络设备的无线承载的PDCP实体所在的小区组。
  37. 如权利要求35或36所述的方法，其特征在于，所述小区组包括主小区组MCG或辅小区组SCG。
  38. 如权利要求32所述的方法，其特征在于，所述下一跳节点为所述网络设备，所述方法还包括：
    在所述第一中继PDU包括公共控制信道CCCH消息的情况下，获取所述网络设备为自身分配的第一小区无线网络临时标识符C-RNTI信息；
    将所述第一C-RNTI信息发送给所述上一跳节点。
  39. 如权利要求38所述的方法，其特征在于，所述方法还包括：
    接收来自所述远端终端的第二C-RNTI信息，所述第二C-RNTI信息是由所述网络设备为所述远端终端分配的；
    将所述第一路由关系中的终端标识更新为所述第二C-RNTI信息。
  40. 如权利要求32所述的方法，其特征在于，所述第一中继PDU包括切换消息，所述切换消息用于触发所述中继终端与目标小区建立连接，所述目标小区为切换后的小区。
  41. 如权利要求32所述的方法，其特征在于，所述方法还包括：
    接收来自网络设备的第二中继PDU，所述第二中继PDU是由网络设备向所述远端终端发送的中继PDU，或者，所述第二中继PDU为所述网络设备广播的；
    根据所述第二中继PDU的协议头中的目的标识和所述第一路由关系，将所述第二中继PDU发给下一跳节点。
  42. 如权利要求41所述的方法，其特征在于，
    所述目的标识包括所述终端标识；或者，
    所述目的标识包括广播标识。
  43. 如权利要求31所述的方法，其特征在于，所述路由表的建立方法应用于网络设备中。
  44. 如权利要求43所述的方法，其特征在于，所述第一中继PDU包括PDCP PDU和无线承载标识，所述无线承载标识指示的无线承载为所述远端终端与网络设备之间的无线承载，所述第一中继PDU包括所述无线承载的数据包；或者，
    所述第一中继PDU包括PDCP PDU和逻辑信道标识。
  45. 如权利要求44所述的方法，其特征在于，所述方法还包括：
    在所述第一中继PDU的目的标识为空的情况下，将所述PDCP PDU和所述无线承载标识递交给上层，或者，将所述PDCP PDU和所述逻辑信道标识递交给上层。
  46. 如权利要求44所述的方法，其特征在于，所述方法还包括：
    在所述第一中继PDU的目的标识不为空的情况下，若所述第一中继PDU的目的标识与本端标识相同，将所述PDCP PDU和所述无线承载标识递交给上层。
  47. 一种中继装置，其特征在于，配置于中继终端，所述中继终端包括中继协议栈，所述中继协议栈位于分组数据汇聚协议PDCP层与层2协议栈之间，或者，所述中继协议栈是媒体接入控制MAC层协议栈，所述中继协议栈包括中继接收模块和中继发送模块：
    所述中继接收模块用于接收上一跳节点发送的中继协议数据单元PDU，将所述中继PDU传递给所述中继发送模块；
    所述中继发送模块将所述中继PDU发送给下一跳节点。
  48. 如权利要求47所述的装置，其特征在于，所述中继PDU包括第一中继PDU，所述第一中继PDU的协议头包括：所述远端终端的终端标识，所述终端标识为所述第一中继PDU的源标识。
  49. 如权利要求48所述的装置，其特征在于，所述第一中继PDU的协议头还包括：所述网络设备的网络设备标识，所述网络设备标识为所述第一中继PDU的目的标识。
  50. 如权利要求47所述的装置，其特征在于，所述中继PDU包括第二中继PDU，所述第二中继PDU的协议头包括：所述远端终端的终端标识，所述终端标识为所述第二中继PDU的目的标识。
  51. 如权利要求50所述的装置，其特征在于，所述第二中继PDU的协议头包括：广播标识，所述广播标识为所述第二中继PDU的目的标识。
  52. 如权利要求50或51所述的装置，其特征在于，所述第二中继PDU的协议头还包括：源标识，所述源标识为所述网络设备的网络设备标识。
  53. 如权利要求48或49所述的装置，其特征在于，
    在所述中继协议栈位于PDCP层与层2协议栈之间的情况下，所述第一中继PDU的协议头还包括：无线承载标识，所述无线承载标识为所述远端终端与所述网络设备之间的无线承载的标识；
    在所述中继协议栈是MAC层协议栈的情况下，所述第一中继PDU还包括：逻辑信道标识。
  54. 如权利要求48、49或53中任一项所述的装置，其特征在于，所述第一中继PDU还包括指示信息，所述指示信息用于指示所述中继终端与网络设备的无线承载的分组数据汇聚协议PDCP实体所在的小区组。
  55. 如权利要求49所述的装置，其特征在于，所述网络设备标识还包括小区组标识，所述小区组标识用于指示所述中继终端与所述网络设备的无线承载的PDCP实体所在的小区组。
  56. 如权利要求54或55所述的装置，其特征在于，所述小区组包括主小区组MCG或辅小区组SCG。
  57. 如权利要求47-56中任一项所述的装置，其特征在于，所述上一跳节点为所述远端终端，或者，所述上一跳节点是处于所述中继终端与所述远端终端之间的另一中继终端；
    所述中继接收模块，还用于：在下行路由表不包括所述远端终端的终端标识对应的路由关系的情况下，在所述下行路由表中建立第一路由关系，所述第一路由关系包括所述终端标识和所述上一跳节点的节点标识，所述第一路由关系是所述终端标识作为目的标识时的路由关系。
  58. 如权利要求57所述的装置，其特征在于，所述中继PDU包括第一中继PDU，所述中继发送模块用于将所述第一中继PDU发送给下一跳节点，包括：
    所述中继发送模块还用于将所述第一中继PDU发送给缺省的下一跳节点。
  59. 如权利要求57所述的装置，其特征在于，所述中继PDU包括第一中继PDU，在所述第一中继PDU的协议头包括网络设备标识的情况下，所述中继发送模块还用于在上行路由表中建立第二路由关系，所述第二路由关系包括所述网络设备标识和所述下一跳节点的节点标识，所述第二路由关系是所述网络设备标识作为目的标识时的路由关系。
  60. 如权利要求47-57所述的装置，其特征在于，所述中继PDU包括第二中继PDU，所述上一跳节点为网络设备，或者，所述中继终端的上一跳节点为处于所述网络设备与所述中继终端之间的另一中继终端；
    所述中继接收模块，还用于：根据所述第二中继PDU的协议头中的终端标识，从所述下行路由表中确定所述终端标识对应的第一路由关系；
    所述中继接收模块，还用于：将所述第一路由关系中，所述终端标识对应的节点标识指示的节点确定为所述下一跳节点。
  61. 如权利要求60所述的装置，其特征在于，所述第二中继PDU包括参考标识和PDCP PDU，所述参考标识包括无线承载标识或逻辑信道标识；
    在所述第二中继PDU的协议头还包括广播标识的情况下，所述中继接收模块还用于将所述第二中继PDU中的参考标识和PDCP PDU递交给上层。
  62. 如权利要求47-61中任一项所述的装置，其特征在于，
    在所述中继终端与所述网络设备交互的情况下，所述层2协议栈包括Uu接口的层2协议栈；
    在所述中继终端与另一中继终端交互的情况下，或者，在所述中继终端与远端终端交互的情况下，所述层2协议栈包括PC5接口的层2协议栈。
  63. 如权利要求47或62所述的装置，其特征在于，所述层2协议栈包括无线链路控制RLC层协议栈和媒体接入控制MAC层协议栈。
  64. 一种中继装置，其特征在于，配置于远端终端，所述远端终端包括中继协议栈，所述中继协议栈位于分组数据汇聚协议PDCP层与PC5接口的层2协议栈之间，或者，所述中继协议栈是MAC层协议栈，所述中继协议栈包括中继发送模块：
    所述中继发送模块用于接收所述PDCP层发送的PDCP PDU，根据所述PDCP PDU生成第一中继PDU，将所述第一中继PDU发送给下一跳节点；
    其中，所述第一中继PDU是所述远端终端向网络设备发送的中继PDU。
  65. 如权利要求64所述的在装置，其特征在于，所述中继协议栈还包括中继接收模块，所述中继接收模块用于接收来自上一跳节点的第二中继PDU，所述第二中继PDU是所述网络设备向所述远端终端发送的中继PDU，或者，所述第二中继PDU是由所述网络设备广播的。
  66. 如权利要求65所述的装置，其特征在于，所述第二中继PDU包括参考标识和PDCP PDU，所述参考标识包括无线承载标识或逻辑信道标识；
    所述中继接收模块还用于在确定所述第二中继PDU的协议头中的目的标识与本端标识相同的情况下，将所述第二中继PDU包括参考标识和PDCP PDU递交给上层。
  67. 如权利要求65所述的装置，其特征在于，所述第二中继PDU包括参考标识和PDCP PDU，所述参考标识包括无线承载标识或逻辑信道标识；
    所述中继接收模块还用于在确定所述第二中继PDU的协议头中还包括广播标识的情况下，将所述第二中继PDU包括的参考标识和PDCP PDU递交给上层。
  68. 如权利要求64所述的装置，其特征在于，所述第一中继PDU的协议头包括：所述远端终端的终端标识，所述终端标识为所述第一中继PDU的源标识。
  69. 如权利要求68所述的装置，其特征在于，所述第一中继PDU的协议头还包括：所述网络设备的网络设备标识；
    所述网络设备标识为所述第一中继PDU的目的标识。
  70. 一种中继装置，其特征在于，配置于网络设备，所述网络设备包括中继协议栈，所述中继协议栈位于分组数据汇聚协议PDCP层与Uu接口的层2协议栈之间，或者，所述中继协议栈是MAC层协议栈，所述中继协议栈包括中继接收模块：
    所述中继接收模块接收来自上一跳节点的第一中继PDU，所述第一中继PDU是由所述远端终端发给所述网络设备的。
  71. 如权利要求70所述的装置，其特征在于，
    在所述中继协议栈位于PDCP层与层2协议栈之间的情况下，所述第一中继PDU的协议头还包括：无线承载标识，所述无线承载标识为所述远端终端与所述网络设备之间的无线承载的标识；
    在所述中继协议栈是MAC层协议栈的情况下，所述第一中继PDU还包括：逻辑信道标识。
  72. 如权利要求71所述的装置，其特征在于，若所述第一中继PDU的目的标识不为空，所述中继接收模块还用于在所述第一中继PDU的目的标识与本端标识相同的情况下，将所述第一中继PDU包括的PDCP PDU和所述无线承载标识递交给上层。
  73. 如权利要求71所述的装置，其特征在于，若所述第一中继PDU的目的标识为空，所述中继接收模块还用于将所述第一中继PDU包括的PDCP PDU和所述无线承载标识递交给上层，或者，将所述第一中继PDU包括的PDCP PDU和所述逻辑信道标识递交给上层。
  74. 如权利要求70所述的装置，其特征在于，所述中继协议栈还包括中继发送模块，所述中继发送模块用于接收所述PDCP层发送的PDCP PDU，根据所述PDCP PDU生成第二中继PDU，将所述第二中继PDU发送给下一跳节点；
    其中，所述第二中继PDU为所述网络设备向所述远端终端发送的中继PDU，或者，所述第二中继PDU为所述网络设备广播的。
  75. 如权利要求74所述的装置，其特征在于，所述第二中继PDU的协议头还包括：所述远端终端的终端标识，所述终端标识为所述第二中继PDU的目的标识。
  76. 如权利要求74所述的装置，其特征在于，所述第二中继PDU还包括广播标识，所述广播标识用于指示所述第二中继PDU包括广播数据或广播信令。
  77. 一种路由表的生成装置，其特征在于，所述装置包括：
    接收模块，用于接收来自远端终端的第一中继协议数据单元PDU，所述第一中继PDU包括所述远端终端的终端标识，所述第一中继PDU是所述远端终端发给所述网络设备的；
    路由建立模块，用于基于所述远端终端的终端标识和上一跳节点的节点标识，建立第一路由关系，所述第一路由关系是所述终端标识作为目的标识时的路由关系。
  78. 如权利要求77所述的装置，其特征在于，在所述路由表的生成方法应用于中继终端的情况下，所述装置还包括：
    发送模块，用于将所述第一中继PDU发送给下一跳节点。
  79. 如权利要求78所述的装置，其特征在于，所述第一中继PDU还包括网络设备标识，所述网络设 备标识为所述第一中继PDU的目的标识，所述网络设备标识用于指示所述第一中继PDU需要传输到的网络设备。
  80. 如权利要求78或79所述的装置，其特征在于，所述第一中继PDU还包括无线承载标识或逻辑信道标识，所述无线承载标识为所述远端终端与网络设备之间的无线承载的标识。
  81. 如权利要求78-80中任一项所述的装置，其特征在于，所述第一中继PDU还包括指示信息，所述指示信息用于指示所述中继终端与网络设备的无线承载的分组数据汇聚协议PDCP实体所在的小区组。
  82. 如权利要求79所述的装置，其特征在于，所述网络设备标识还包括小区组标识，所述小区组标识用于指示所述中继终端与网络设备的无线承载的PDCP实体所在的小区组。
  83. 如权利要求81或82所述的装置，其特征在于，所述小区组包括主小区组MCG或辅小区组SCG。
  84. 如权利要求78所述的装置，其特征在于，所述下一跳节点为所述网络设备，所述发送模块还用于：
    在所述第一中继PDU包括公共控制信道CCCH消息的情况下，获取所述网络设备为自身分配的第一小区无线网络临时标识符C-RNTI信息；
    将所述第一C-RNTI信息发送给所述上一跳节点。
  85. 如权利要求84所述的装置，其特征在于，所述接收模块还用于：
    接收来自所述远端终端的第二C-RNTI信息，所述第二C-RNTI信息是由所述网络设备为所述远端终端分配的；
    将所述第一路由关系中的终端标识更新为所述第二C-RNTI信息。
  86. 如权利要求78所述的装置，其特征在于，所述第一中继PDU包括切换消息，所述切换消息用于触发所述中继终端与目标小区建立连接，所述目标小区为切换后的小区。
  87. 如权利要求78所述的装置，其特征在于，
    所述接收模块，还用于接收来自网络设备的第二中继PDU，所述第二中继PDU是由网络设备向所述远端终端发送的中继PDU，或者，所述第二中继PDU为所述网络设备广播的；
    所述发送模块，还用于根据所述第二中继PDU的协议头中的目的标识和所述第一路由关系，将所述第二中继PDU发给下一跳节点。
  88. 如权利要求87所述的装置，其特征在于，
    所述目的标识包括所述终端标识；或者，
    所述目的标识包括广播标识。
  89. 如权利要求77所述的装置，其特征在于，所述路由表的建立装置配置于网络设备中。
  90. 如权利要求89所述的装置，其特征在于，所述第一中继PDU包括PDCP PDU和无线承载标识，所述无线承载标识指示的无线承载为所述远端终端与网络设备之间的无线承载，所述第一中继PDU包括所述无线承载的数据包；或者，
    所述第一中继PDU包括PDCP PDU和逻辑信道标识。
  91. 如权利要求90所述的装置，其特征在于，所述装置还包括：
    递交模块，用于在所述第一中继PDU的目的标识为空的情况下，将所述PDCP PDU和所述无线承载标识递交给上层，或者，将所述PDCP PDU和所述逻辑信道标识递交给上层。
  92. 如权利要求90所述的装置，其特征在于，所述递交模块，还用于在所述第一中继PDU的目的标识不为空的情况下，若所述第一中继PDU的目的标识与本端标识相同，将所述PDCP PDU和所述无线承载标识递交给上层。
  93. 一种中继终端，其特征在于，所述设备包括处理器和存储器，所述存储器存储有至少一条指令，所述至少一条指令用于被所述处理器执行以实现权利要求1-17任一项方法的步骤，或者，用于实现权利要求31-42任一项方法的步骤。
  94. 一种远端终端，其特征在于，所述设备包括处理器和存储器，所述存储器存储有至少一条指令，所述至少一条指令用于被所述处理器执行以实现权利要求18-23任一项方法的步骤。
  95. 一种网络设备，其特征在于，所述设备包括处理器和存储器，所述存储器存储有至少一条指令，所述至少一条指令用于被所述处理器执行以实现权利要求24-30任一项方法的步骤，或者，用于实现权利要求31、43-46任一项方法的步骤。
  96. 一种计算机可读存储介质，所述计算机可读存储介质上存储有指令，其特征在于，所述指令被处理器执行时实现权利要求1-17任一项方法的步骤，或者，用于实现权利要求31-42任一项方法的步骤。
  97. 一种计算机可读存储介质，所述计算机可读存储介质上存储有指令，其特征在于，所述指令被处理器执行时实现权利要求18-23任一项方法的步骤。
  98. 一种计算机可读存储介质，所述计算机可读存储介质上存储有指令，其特征在于，所述指令被处 理器执行时实现实现权利要求24-30任一项方法的步骤，或者，用于实现权利要求31、43-46任一项方法的步骤。
PCT/CN2020/076487 2020-02-24 2020-02-24 中继方法、路由表的生成方法、装置、设备及存储介质 WO2021168632A1 (zh)

Priority Applications (5)

Application Number Priority Date Filing Date Title
CN202080096827.0A CN115088387A (zh) 2020-02-24 2020-02-24 中继方法、路由表的生成方法、装置、设备及存储介质
PCT/CN2020/076487 WO2021168632A1 (zh) 2020-02-24 2020-02-24 中继方法、路由表的生成方法、装置、设备及存储介质
EP20922133.2A EP4114137A4 (en) 2020-02-24 2020-02-24 RELAY METHOD, METHOD FOR CREATING A ROUTING TABLE, DEVICE AND DEVICE, AND STORAGE MEDIA
CN202310184554.0A CN116232408A (zh) 2020-02-24 2020-02-24 中继方法、路由表的生成方法、装置、设备及存储介质
US17/894,678 US20220408342A1 (en) 2020-02-24 2022-08-24 Relay Method, Method for Generating Routing Table, and Device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/076487 WO2021168632A1 (zh) 2020-02-24 2020-02-24 中继方法、路由表的生成方法、装置、设备及存储介质

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/894,678 Continuation US20220408342A1 (en) 2020-02-24 2022-08-24 Relay Method, Method for Generating Routing Table, and Device

Publications (1)

Publication Number Publication Date
WO2021168632A1 true WO2021168632A1 (zh) 2021-09-02

Family

ID=77491720

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/076487 WO2021168632A1 (zh) 2020-02-24 2020-02-24 中继方法、路由表的生成方法、装置、设备及存储介质

Country Status (4)

Country Link
US (1) US20220408342A1 (zh)
EP (1) EP4114137A4 (zh)
CN (2) CN115088387A (zh)
WO (1) WO2021168632A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024060242A1 (en) * 2022-09-23 2024-03-28 Nec Corporation Method, device and computer storage medium of communication

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116249077B (zh) * 2023-02-27 2023-10-20 北京云智软通信息技术有限公司 获取工作组成员通信路由状态的方法及装置

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101668324A (zh) * 2008-09-04 2010-03-10 华为技术有限公司 中继网络的路由方法、装置及系统
CN108029148A (zh) * 2015-07-23 2018-05-11 英特尔Ip公司 层2中继协议和移动性中继方法
WO2018176416A1 (zh) * 2017-03-31 2018-10-04 华为技术有限公司 中继通信方法、装置和系统
US20180287689A1 (en) * 2017-03-30 2018-10-04 Lg Electronics Inc. Method for performing management of local id identifying a remote ue in a relay ue in wireless communication system and a device therefor
CN108809897A (zh) * 2017-04-28 2018-11-13 中兴通讯股份有限公司 一种中继发现及中继转发方法、设备和存储介质
US20190349834A1 (en) * 2018-05-10 2019-11-14 Telefonaktiebolaget Lm Ericsson (Publ) QoS and Hop-Aware Adaptation Layer for Mutli-Hop Integrated Access Backhaul System

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101668324A (zh) * 2008-09-04 2010-03-10 华为技术有限公司 中继网络的路由方法、装置及系统
CN108029148A (zh) * 2015-07-23 2018-05-11 英特尔Ip公司 层2中继协议和移动性中继方法
US20180287689A1 (en) * 2017-03-30 2018-10-04 Lg Electronics Inc. Method for performing management of local id identifying a remote ue in a relay ue in wireless communication system and a device therefor
WO2018176416A1 (zh) * 2017-03-31 2018-10-04 华为技术有限公司 中继通信方法、装置和系统
CN108809897A (zh) * 2017-04-28 2018-11-13 中兴通讯股份有限公司 一种中继发现及中继转发方法、设备和存储介质
US20190349834A1 (en) * 2018-05-10 2019-11-14 Telefonaktiebolaget Lm Ericsson (Publ) QoS and Hop-Aware Adaptation Layer for Mutli-Hop Integrated Access Backhaul System

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
ZTE: "Consideration on Routing in IAB Architecture 1a and 1b", 3GPP DRAFT; R2-1812469 CONSIDERATION ON ROUTING IN IAB ARCHITECTURE 1A AND 1B, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Gothenburg, Sweden; 20180820 - 20180824, 10 August 2018 (2018-08-10), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051522067 *
ZTE: "Discussion on layer 2 ProSe UE-to-network relay for feD2D", 3GPP DRAFT; R2-166815 DISCUSSION ON LAYER 2 PROSE UE-TO-NETWORK RELAY FOR FED2D, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Kaohsiung; 20161010 - 20161014, 30 September 2016 (2016-09-30), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051161848 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024060242A1 (en) * 2022-09-23 2024-03-28 Nec Corporation Method, device and computer storage medium of communication

Also Published As

Publication number Publication date
EP4114137A1 (en) 2023-01-04
CN115088387A (zh) 2022-09-20
EP4114137A4 (en) 2023-04-19
US20220408342A1 (en) 2022-12-22
CN116232408A (zh) 2023-06-06

Similar Documents

Publication Publication Date Title
US20230073469A1 (en) Sidelink relay communication method and apparatus, device and medium
US10972935B2 (en) Method for performing reflective quality of service (QoS) in wireless communication system and a device therefor
US11115855B2 (en) Method for transmitting UL packet based on quality of service (QoS) flow in wireless communication system and a device therefor
US11438941B2 (en) Communication method and communications apparatus
KR102060806B1 (ko) 무선 통신 시스템에서 데이터를 송수신하기 위한 방법 및 이를 지원하는 장치
CN108353310B (zh) 在无线通信系统中发送和接收数据的方法和支持该方法的装置
CN108377567B (zh) 一种在5g架构下建立双连接传输数据的方法、装置和系统
KR102103343B1 (ko) 이종 네트워크 무선 통신 시스템에서 데이터 전송 장치 및 방법
US11317401B2 (en) Method and apparatus for selecting carrier
US20160037510A1 (en) Method for performing a logical channel prioritization and communication device thereof
JP7270766B2 (ja) 無線ベアラ構成方法、装置及びシステム
CN110366140B (zh) 一种数据传输方法和装置
US20190200259A1 (en) Method for transmitting and receiving data in wireless communication system, and device for supporting same
US20210212122A1 (en) Method for transmitting and receiving data in wireless communication system and device for supporting same
US20220408342A1 (en) Relay Method, Method for Generating Routing Table, and Device
CN112514522A (zh) 用于恢复时挂起不活动和挂起时恢复不活动的方法
EP2863701B1 (en) Communication network, user equipment and signalling transmission method
WO2016136493A1 (ja) 基地局及び無線端末
US20220408344A1 (en) Relay method, routing table generation method and apparatus, terminal, and storage medium
US20190289496A1 (en) Method for transmitting/receiving data in wireless communication system and device for supporting same
WO2018054336A1 (zh) 消息的发送方法和装置
JP7478749B2 (ja) 無線ベアラ確立方法及び装置
CN112738911A (zh) 一种在5g架构下建立双连接传输数据的方法、装置和系统
WO2023015454A1 (zh) 路径建立方法、选择方法、装置、终端设备及存储介质
WO2022253817A1 (en) Hybrid quality of service flow

Legal Events

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

Ref document number: 20922133

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2020922133

Country of ref document: EP

Effective date: 20220926