Relay method, routing table generation method, device, equipment and storage medium
By introducing a relay protocol stack in the 5G communication system, remote terminals and network devices can independently determine the routing of relay PDUs, solving the problem of low flexibility in the relay solution in the prior art and achieving more flexible and efficient communication process.
Patent Information
- Application Number
- CN202310184554.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2020-02-24
- Publication Date
- 2024-11-29
- Estimated Expiration
- 2040-02-24
AI Technical Summary
In 5G mobile communication technology, the relay solution between the remote terminal and the network device is low in flexibility, and the mapping relationship between the remote terminal and the wireless bearer is limited by configuring the base station.
The relay protocol stack is introduced, located between the packet data aggregation protocol PDCP layer and the layer 2 protocol stack or the media access control MAC layer, including the relay receiving entity and the relay sending entity. The remote terminal and network equipment can independently determine the relay PDU. The routing does not require network equipment to configure the mapping relationship between wireless bearer and terminal identity.
It improves communication flexibility between remote terminals and network devices, makes the routing process of relay PDUs more flexible, reduces dependence on network device configuration, and improves communication flexibility and efficiency.
Smart Images

Figure CN116232408B_ABST
Abstract
Description
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS
[0002] This application is a divisional application of the Chinese patent application submitted to the China Patent Office on February 24, 2020, with application number 202080096827.0, and invention name “Relay method, routing table generation method, device, equipment and storage medium”. Technical Field
[0003] The present application relates to the field of communication technology, and in particular to a relay method, a method for generating a routing table, an apparatus, a device and a storage medium. Background Art
[0004] In the fifth generation wireless systems (5G), in order to expand the coverage range and coverage effect of the network, a relay terminal can be set between the remote terminal and the network device, and data packets or signaling are transmitted between the remote terminal and the network device through the relay terminal.
[0005] In the related art, 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. In implementation, the network device can configure the mapping relationship between the local index and the wireless bearer identifier, and send the configuration relationship to the relay terminal, wherein the local index is used to identify the remote terminal, and the wireless bearer identifier is used to identify the wireless bearer. In this way, 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, and determines the corresponding wireless bearer based on the local index and the above-mentioned mapping relationship, and sends the relay PDU to the network device through the wireless bearer.
[0006] However, the mapping relationship between the remote terminal and the wireless bearer is completely configured by the base station to achieve communication between the remote terminal and the network device, and the relay solution has low flexibility. Summary of the invention
[0007] The embodiment of the present application provides a relay method, a method, an apparatus, a device and a storage medium for generating a routing table, which can flexibly realize the communication problem between a remote terminal and a network device. The technical solution is as follows:
[0008] In a first aspect, a relay method is provided, which is applied to a relay terminal, wherein the relay terminal includes a relay protocol stack, the relay protocol stack is located between a packet data convergence protocol PDCP layer and a layer 2 protocol stack, or 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, and the method includes:
[0009] 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;
[0010] The relay sending entity is used to send the relay PDU to a next hop node.
[0011] In a second aspect, a relay method is provided, which is applied to a remote terminal, wherein the remote terminal includes a relay protocol stack, wherein the relay protocol stack is located between a packet data convergence protocol PDCP layer and a layer 2 protocol stack of a PC5 interface, or the relay protocol stack is a MAC layer protocol stack, wherein the relay protocol stack includes a relay sending entity, and the method includes:
[0012] 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 a next hop node;
[0013] The first relay PDU is a relay PDU sent by the remote terminal to the network device.
[0014] In a third aspect, a relay method is provided, which is applied to a network device, wherein the network device includes a relay protocol stack, the relay protocol stack is located between a packet data convergence protocol PDCP layer and a layer 2 protocol stack of a Uu interface, or the relay protocol stack is a MAC layer protocol stack, the relay protocol stack includes a relay receiving entity, and the method includes:
[0015] The relay receiving entity is used to receive a first relay PDU from a previous hop node, where the first relay PDU is sent from the remote terminal to the network device.
[0016] In a fourth aspect, a method for generating a routing table is provided, the method comprising:
[0017] receiving a first relay protocol data unit (PDU) from a remote terminal, wherein the first relay PDU includes a terminal identifier of the remote terminal, and the first relay PDU is sent by the remote terminal to the network device;
[0018] A first routing relationship is established based on the terminal identifier of the remote terminal and the node identifier of the previous hop node, where the first routing relationship is a routing relationship when the terminal identifier is used as the destination identifier.
[0019] In a fifth aspect, a relay device is provided, configured in a relay terminal, the relay terminal comprising a relay protocol stack, the relay protocol stack being located between a packet data convergence protocol PDCP layer and a layer 2 protocol stack, or the relay protocol stack being a media access control MAC layer protocol stack, the relay protocol stack comprising a relay receiving module and a relay sending module:
[0020] The relay receiving module 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;
[0021] The relay sending module is used to send the relay PDU to the next hop node.
[0022] In a sixth aspect, a relay device is provided, configured at a remote terminal, the remote terminal comprising a relay protocol stack, the relay protocol stack being located between a packet data convergence protocol PDCP layer and a layer 2 protocol stack of a PC5 interface, or the relay protocol stack being a MAC layer protocol stack, the relay protocol stack comprising a relay sending module, the relay sending module being used to receive a PDCP PDU sent by the PDCP layer, generate a first relay PDU according to the PDCP PDU, and send the first relay PDU to a next hop node;
[0023] The first relay PDU is a relay PDU sent by the remote terminal to the network device.
[0024] In the seventh aspect, a relay device is provided, which is configured in a network device, wherein the network device includes a relay protocol stack, and the relay protocol stack is located between the packet data convergence protocol PDCP layer and the layer 2 protocol stack of the Uu interface, or the relay protocol stack is a MAC layer protocol stack, and the relay protocol stack includes a relay receiving module, and the relay receiving module is used to receive a first relay PDU from a previous hop node, and the first relay PDU is sent from the remote terminal to the network device.
[0025] In an eighth aspect, a device for generating a routing table is provided, the device comprising:
[0026] A receiving module, configured to receive a first relay protocol data unit (PDU) from a remote terminal, wherein the first relay PDU includes a terminal identifier of the remote terminal, and the first relay PDU is sent by the remote terminal to the network device;
[0027] The routing establishment module is used to establish a first routing relationship based on the terminal identifier of the remote terminal and the node identifier of the previous hop node, wherein the first routing relationship is a routing relationship when the terminal identifier is used as the destination identifier.
[0028] In a ninth aspect, a relay terminal is provided, the device comprising a processor and a memory, the memory storing at least one instruction, the at least one instruction being used to be executed by the processor to implement any of the methods described above executed by the relay terminal in the first and fourth aspects.
[0029] In a tenth aspect, a remote terminal is provided, the device comprising a processor and a memory, the memory storing at least one instruction, the at least one instruction being used to be executed by the processor to implement any of the methods described in the second aspect above.
[0030] In the eleventh aspect, a network device is provided, the device comprising a processor and a memory, the memory storing at least one instruction, the at least one instruction being used to be executed by the processor to implement any of the methods described above for execution by the network device in the third and fourth aspects.
[0031] In a twelfth aspect, a computer-readable storage medium is provided, on which instructions are stored, and when the instructions are executed by a processor, the method of the above aspect performed by the relay terminal is implemented.
[0032] In a thirteenth aspect, a computer-readable storage medium is provided, on which instructions are stored, and when the instructions are executed by a processor, the method of implementing the above aspect by a remote terminal is implemented.
[0033] In a fourteenth aspect, a computer-readable storage medium is provided, on which instructions are stored, and when the instructions are executed by a processor, the method of implementing the above aspects by a network device is implemented.
[0034] In a fifteenth aspect, a computer program product comprising instructions is provided, which, when executed on a computer, enables the computer to execute the method described in the above aspects and executed by a relay terminal, a remote terminal or a network device.
[0035] The beneficial effects brought by the technical solution provided by the embodiment of the present application include at least:
[0036] The relay terminal of the present application includes a relay protocol stack, which is located between the packet data convergence protocol PDCP layer and the layer 2 protocol stack, or the relay protocol stack is a media access control MAC layer protocol stack, and 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. In this way, between the remote device and the network device, the relay terminal including the relay protocol stack can autonomously determine the next hop node of the relay PDU to successfully relay the relay PDU from one end to the other end, without the need for the network device to configure the mapping relationship between the wireless bearer and the remote terminal identifier, so that the routing process of the relay PDU is more flexible. BRIEF DESCRIPTION OF THE DRAWINGS
[0037] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.
[0038] Figure 1 is a schematic diagram of a communication system provided by an exemplary embodiment of the present application;
[0039] Figure 2 is a system block diagram including a relay protocol stack provided by an exemplary embodiment of the present application;
[0040] Figure 3 is a schematic diagram of a relay PDU format shown in an exemplary embodiment of the present application;
[0041] Figure 4 is a schematic diagram of another relay PDU format shown in an exemplary embodiment of the present application;
[0042] Figure 5 is a flow chart of a relay method provided by an exemplary embodiment of the present application;
[0043] Figure 6 is a schematic diagram of a transmission process of a relay PDU shown in an exemplary embodiment of the present application;
[0044] Figure 7 is a flow chart of a relay method provided by another exemplary embodiment of the present application;
[0045] Figure 8 is a flow chart of a relay method provided by another exemplary embodiment of the present application;
[0046] Fig. 9is a flow chart of a relay method provided by another exemplary embodiment of the present application;
[0047] Fig.10 is a system block diagram of a protocol stack provided by an exemplary embodiment of the present application;
[0048] Fig.11 is a flow chart of a method for generating a routing table provided by an exemplary embodiment of the present application;
[0049] Fig.12 is a schematic diagram of a relay process provided by an exemplary embodiment of the present application;
[0050] Fig.13 is a schematic diagram of a relay process provided by another exemplary embodiment of the present application;
[0051] Fig.14 is a schematic diagram of a relay process provided by another exemplary embodiment of the present application;
[0052] Fig.15 is a schematic diagram of a relay process provided by another exemplary embodiment of the present application;
[0053] Fig.16 is a flow chart of a method for generating a routing table provided by another exemplary embodiment of the present application;
[0054] Fig.17 is a schematic structural diagram of a relay device provided by an exemplary embodiment of the present application;
[0055] Fig.18 is a structural schematic diagram of a relay device provided by another exemplary embodiment of the present application;
[0056] Fig.19 is a schematic structural diagram of a relay device provided by another exemplary embodiment of the present application;
[0057] Fig. 20 It is a structural schematic diagram of a routing table generation device shown in an exemplary embodiment of the present application;
[0058] Fig.21 is a structural schematic diagram of a routing table generation device shown in another exemplary embodiment of the present application;
[0059] Fig. 22 It is a structural diagram of a communication device provided by an exemplary embodiment of the present application. DETAILED DESCRIPTION
[0060] In order to make the objectives, technical solutions and advantages of the present application clearer, the implementation methods of the present application will be further described in detail below with reference to the accompanying drawings.
[0061] Before introducing in detail the relay method and the method for generating a routing table provided in the embodiments of the present application, a brief introduction to the professional terms and implementation environment involved in the embodiments of the present application is first given.
[0062] First, a brief introduction is given to the professional terms involved in the embodiments of the present application.
[0063] Radio bearer: is a collection of wireless logical resources, which is divided into signaling radio bearer (SRB) and data radio bearer (DRB). DRB is further divided into default bearer and dedicated bearer.
[0064] A communication link between communication devices, such as between a terminal and a network device, between two terminals, or between two network devices, may be facilitated using one or more radio bearers. For example, a network device may use a radio bearer to generate one or more signals and / or send one or more signals to a terminal.
[0065] Uu interface: The air interface between the network device and the terminal (or user equipment (UE)) is called the Uu interface.
[0066] PC5 interface: It is an interface introduced between communication devices. In the embodiment of the present application, the remote terminal and the relay terminal can establish communication through the PC5 interface, or the relay terminal and the relay terminal can also establish communication through the PC5 interface.
[0067] Direct communication (Sidelink): It is an important branch of cellular Internet of Things technology, namely, object-to-object communication technology. It can meet 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 be addressed through the source ID (Source ID) and destination ID (Destination ID) of the media access control layer (Media Access Control, MAC). Before transmission, there is no need for pre-connection between UEs. The Sidelink communication method is used to meet the faster and more efficient connection between UEs.
[0068] Different protocol entities in the protocol stack of the wireless access network:
[0069] 1) Service Data Adaptation Protocol (SDAP): Responsible for mapping QoS bearers to radio bearers according to the Quality-of-Service (QoS) requirements. This protocol layer does not exist in the long term evolution (LTE) system, but in the new radio (NR) when connected to the 5G core network, the new QoS processing requires this protocol entity.
[0070] 2) Packet Data Convergence Protocol (PDCP): implements IP header compression, encryption and integrity protection. It also handles retransmission, in-order delivery and deduplication during switching. For dual connections with separate bearers, PDCP can provide routing and replication, that is, configure a PDCP entity for each radio bearer of the terminal.
[0071] 3) Radio Link Control (RLC): Responsible for data segmentation and retransmission. RLC provides services to PDCP in the form of RLC signaling. Each RLC channel (corresponding to each radio bearer) is configured with an RLC entity for each terminal. In order to reduce latency, compared with LTE, RLC in NR does not support in-sequence delivery of data to higher protocol layers.
[0072] 4) Medium Access Control (MAC): Responsible for logical channel multiplexing, Hybrid Automatic Repeat-reQuest (HARQ), and scheduling and scheduling-related functions. The scheduling functions for uplink and downlink are located in the network equipment. MAC provides services to RLC in the form of logical channels. NR changes the header structure of MAC, so that it can support low-latency processing more effectively than LTE.
[0073] 5) Physical Layer (PHY): Responsible for encoding and decoding, modulation, demodulation, multi-antenna mapping and other typical physical layer functions. The physical layer provides services to the MAC layer in the form of transmission channels.
[0074] As an example, when three IP packets are given: packet 1, packet 2, and packet 3, where packet 1 and packet 2 are on one radio bearer a, and packet 3 is on another radio bearer b. The SDAP protocol maps IP packets to different bearers, packet 1 and packet 2 are mapped to radio bearer a, and packet 3 is mapped to radio bearer b. Generally, data entities from or to higher protocol layers are called service data units (SDUs), while data entities from or to lower protocol layers are called protocol data units (PDUs). Therefore, the output of SDAP is SDAP PDU, which is equivalent to PDCP SDU.
[0075] The PDCP protocol performs (optional) IP header compression for each radio bearer and then encrypts it. Depending on the configuration, it is decided whether to add a PDCP header, which contains the information required by the terminal for decryption and a sequence number for retransmission and in-order delivery. The output of PDCP is forwarded to RLC.
[0076] If necessary, the RLC protocol segments the PDCP PDU and adds an RLC header containing a sequence number for retransmission handling. Unlike LTE, the RLC in NR does not provide data order delivery services to higher protocol layers. Because the reordering mechanism will cause additional latency, this latency may cause damage to services that require very low latency. If it is really necessary, the PDCP layer can provide in-sequence delivery.
[0077] The RLC PDU is sent to the MAC layer, which multiplexes multiple RLC PDUs and adds a MAC header to form a new transport block. The physical layer provides services to the MAC layer in the form of transport channels. The transport channel is defined by the way and characteristics of information transmission over the radio interface. The data on the transport channel is organized into transport blocks. In each transmission time interval (TTI), at most one transport block of dynamically variable size is sent to or from the terminal over the radio interface.
[0078] To support priority processing, the MAC layer can multiplex multiple logical channels onto a transport channel, where each logical channel has its own RLC entity. At the receiving end, the MAC layer is responsible for the corresponding demultiplexing and forwarding of the RLC PDU to their respective RLC entities. In order to support demultiplexing at the receiving end, the MAC header is required, and the subheader of each MAC SDU is placed before the SDU, so that the PDU can be pre-processed before receiving the scheduling decision. Among them, the subheader contains 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 contain reserved bits for demand or future use.
[0079] Dual connectivity: For a terminal to communicate, at least one connection needs to be established between the terminal and the network. The terminal must be connected to at least one cell that handles all its uplink and downlink transmissions, and all data streams, including user data and Radio Resource Control (RRC) signaling, are processed by this cell. However, in some cases, dual connectivity (DC) needs to be established between the terminal and the network. Dual connectivity is to connect a terminal to two cells, that is, the terminal is connected to the network through multiple cells, such as in the case of user plane aggregation, where data streams from multiple cells are aggregated together to increase the data rate, and in another example, in the scenario where the control plane and the user plane are separated, the communication and signaling of the control plane are processed by one node, and the data of the user plane is processed by another node, thereby increasing the data rate.
[0080] Next, the implementation environment involved in the embodiments of the present application is briefly introduced.
[0081] Figure 1 A schematic diagram of a communication system provided by an exemplary embodiment of the present application is shown, and 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 via a Uu interface, and the remote terminal 130 and the relay terminal 120 may be connected via a PC5 interface. The number of the relay terminals 120 may be one or more, and when the number of the relay terminals 120 is more than one, the relay terminals 120 may also be connected via a PC5 interface.
[0082] Among them, the network device 110 can be a device that communicates with the relay terminal 120 (or referred to as a communication terminal, terminal). The network device 110 can provide communication coverage for a specific geographical area and can communicate with a relay terminal located in the coverage area. Optionally, the network device 110 can be an evolved network device (eNB or eNodeB) in an LTE system, or a wireless controller in a cloud radio access network (CRAN), or the network device can 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.
[0083] The relay terminal 120 is a terminal deployed in a communication system for providing relay services for communications between remote terminals and network devices. 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. Alternatively, 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 relay PDU to the remote terminal 130. In this case, the transmission of the relay PDU is a downlink transmission.
[0084] 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 a wireless modem, as well as various forms of user equipment, mobile stations (MS), terminals (terminal devices), etc.
[0085] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: Global System of Mobile Communication (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, LTE Frequency Division Duplex (FDD) system, LTE Time Division Duplex (TDD) system, Advanced Long Term Evolution (LTE-A) system, New Radio (NR) system, NR system evolution system, LTE on unlicensed spectrum (LTE-based access to Unlicensed spectrum, LTE-U) system, NR-U system, Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) communication system, Wireless Local Area Network (WLAN) system. Networks, WLAN), Wireless Fidelity (WiFi), next generation communication systems or other communication systems, etc.
[0086] Generally speaking, the number of connections supported by traditional communication systems is limited and easy to implement. However, with the development of communication technology, mobile communication systems will not only support traditional communications, but also support, for example, device to device (Device to Device, D2D) communication, machine to machine (Machine to Machine, M2M) communication, machine type communication (Machine Type Communication, MTC), vehicle to vehicle (V2V) communication and vehicle to everything (V2X) system, etc. The embodiments of the present application can also be applied to these communication systems.
[0087] Optionally, the relay terminals 120 may perform device to device (D2D) communication in a direct communication manner.
[0088] Optionally, the remote terminal 130 and the relay terminal 120 may perform device-to-device (D2D) communication in a direct communication manner.
[0089] Optionally, the 5G communication system or 5G network may also be referred to as a New Radio (NR) system or NR network.
[0090] Figure 1 A network device, two relay terminals and four remote terminals are shown by way of example. Optionally, the communication system 100 may include multiple network devices and each network device may include another number of terminals within its coverage area, which is not limited in the embodiments of the present application.
[0091] Optionally, the communication system 100 may also include other network entities such as a network controller and a mobility management entity, which is not limited in the embodiments of the present application.
[0092] It should be understood that the device with communication function in the network / system in the embodiment of the present application can be referred to as a communication device. Figure 1 Taking the communication system 100 shown as an example, the communication equipment may include a network device 110, a relay terminal 120 and a remote terminal 130 with communication functions. The network device 110, the relay terminal 120 and the remote terminal 130 may be the specific devices described above and will not be repeated here; the communication equipment may also include other devices in the communication system 100, such as a network controller, a mobile management entity and other network entities, which is not limited in the embodiments of the present application.
[0093] Based on the above communication system, in the method provided in 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 device is connected and communicated through the Uu interface of the 3GPP system. The remote terminal, the relay terminal and the network device all include a relay protocol stack, through which the relay PDU between the remote terminal and the network device can be relayed.
[0094] As an example, the relay protocol stack may be a newly added protocol stack. For example, for a remote terminal, 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 between the PDCP layer and the layer 2 protocol stack of the Uu interface; for a relay terminal, the relay protocol stack included in the relay terminal is located between the PDCP layer and the layer 2 protocol stack, and, in the case where the relay terminal interacts with the network device, the layer 2 protocol stack includes the layer 2 protocol stack of the Uu interface, and in the case where the relay terminal interacts with another relay terminal, or in the case where the relay terminal interacts with a remote terminal, 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, and if the communication device adjacent to the relay terminal is a network device, 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. In addition, as an example, the layer 2 protocol stack includes but is not limited to the RLC layer protocol stack and the MAC layer protocol stack.
[0095] See also Figure 2 , Figure 2 A system block diagram including a relay protocol stack provided by an exemplary embodiment of the present application is shown. The protocol stack from the remote terminal to the network device is the PDCP protocol layer of the 3GPP Uu interface, and other protocol layers above the PDCP protocol layer, including other user plane protocol layers, such as the SDAP protocol layer and the IP protocol layer, and other control plane protocol layers, such as the RRC and the Non-Access Stratum (NAS) protocol layer. 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 the present application.
[0096] As another example, for any communication device among the remote terminal, the relay terminal and the network device, the relay protocol stack may be a MAC layer protocol stack of the communication device.
[0097] The relay protocol stack includes a relay receiving entity and a relay sending entity, which can be collectively referred to as a relay protocol entity. The functions of the relay protocol entity include: generating a routing table, forwarding data packets whose destination identifier is not this node, and processing data packets whose destination identifier is this node or a broadcast identifier. If the relay protocol entity receives an SDU that the PDCP layer of the 3GPP Uu interface requires to be sent, a relay protocol PDU will also be generated. Among them, for the relay sending entity of the relay terminal, whether it is a relay PDU generated by the PDCP layer or a relay PDU received from an adjacent node, the relay sending entity of the relay terminal forwards this relay PDU to the next hop node.
[0098] It should be noted that when there are multiple relay terminals between the remote terminal and the network device, the relay terminal can also be a remote terminal at the same time. Figure 2 As shown, relay terminal 1 can communicate with network equipment through relay terminal 2. At this time, for relay terminal 2, relay terminal 1 is a remote terminal.
[0099] As an example, Figure 2 Two relay terminals are used as an example for explanation, which does not constitute a limitation on the present application. The relay method of the present application is applicable to a communication system including one or more relay terminals.
[0100] It should be noted that in the communication system, the relay terminal can be called the parent node of the remote terminal, and the remote terminal is the child node of the relay terminal. When a remote terminal itself is transformed into a relay terminal, this parent-child relationship remains unchanged. For example, if the communication system includes a remote terminal, a relay terminal 1, a relay terminal 2, and a network device, and these communication devices are sequentially connected, then the remote terminal is the child node of the relay terminal 1, the relay terminal 1 is the child node of the relay terminal 2, and the relay terminal 2 is the child node of the 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, and during the communication process, the parent-child relationship remains unchanged. All parent and child nodes can know their respective identities when establishing a parent-child relationship. When the identity of one of the nodes changes, this node can notify all adjacent nodes to update, so that each node can autonomously update the established routing table.
[0101] Among them, each remote terminal and relay terminal has a unique identifier. In the uplink direction (the direction from the remote terminal to the network device), the protocol header of the relay PDU contains at least a source identifier, that is, it can be understood that the source identifier in the protocol header of the relay PDU is not empty. At this time, the content of the source identifier is the terminal identifier of the remote terminal. In the downlink direction (the direction from the network device to the remote terminal or relay terminal), the protocol header of the relay PDU contains at least a destination identifier, that is, it can be understood that the destination identifier in the protocol header of the relay PDU is not empty. At this time, the content of the destination identifier is the network device identifier of the network device. In addition, the protocol header of the relay PDU can also include a wireless bearer identifier or a logical channel identifier. Exemplarily, the wireless bearer identifier can be an SRB ID or a DRB ID. Usually, more than one wireless bearer is often established on the above-mentioned PC5 interface or Uu interface.
[0102] In addition, in the uplink direction, the relay PDU may include signaling or data packets related to a remote terminal. In the downlink direction, the relay PDU may include broadcast signaling or broadcast data, such as system messages, in addition to signaling or data packets related to a remote terminal.
[0103] In addition, in the process of a remote terminal sending a relay PDU to a network device through a relay terminal, or a network device sending a relay PDU to a remote terminal through a relay terminal, there may be multiple relay PDU formats. The relay PDU formats in this application include but are not limited to the following two. This application only uses the following two relay PDU formats as examples for explanation.
[0104] In a possible implementation, the relay PDU format may be the following format 1:
[0105] The relay PDU may include at least: a terminal identifier, a radio bearer identifier or a logical channel identifier.
[0106] The terminal identifier can be interpreted as different meanings depending on the source of the relay PDU. For example, if the relay PDU comes from a child node, the terminal identifier included in the relay PDU is interpreted as a source identifier, that is, the content of the source identifier of the relay PDU protocol header is the terminal identifier. Furthermore, the destination identifier of the relay PDU protocol header can be empty. If the relay PDU comes from a parent node, the terminal identifier included in the relay PDU is interpreted as a destination identifier, that is, the content of the destination identifier of the relay PDU protocol header is the terminal identifier.
[0107] In other words, if the relay PDU is generated at this node, then before sending this relay PDU to the parent node, the source identifier is filled in with the node identifier of this node. For example, for a remote terminal, in the process of generating the relay PDU, the source identifier of the protocol header of the relay PDU is filled in with the terminal identifier of the remote terminal. If the relay PDU is sent to a child node, the destination identifier is filled in with the terminal identifier of the target child node. For example, the target child node is a remote terminal, that is, when the network device generates a relay PDU, the destination identifier in the protocol header of the relay PDU is filled in with the terminal identifier of the remote terminal.
[0108] In addition, when the relay PDU is sent from the network device to the remote terminal, a certain number of bits can be reserved to indicate the broadcast identifier. In this case, it means that the relay PDU includes broadcast data or broadcast signaling. At this time, it means that the transmitted relay PDU is for all connected relay terminals and remote terminals. Among them, the bit corresponding to the broadcast identifier cannot be occupied by the node identifier of the remote terminal, relay terminal and network device. Figure 3 As shown, Figure 3 It is a schematic diagram of a relay PDU format according to an exemplary embodiment of the present application, wherein the R bit is a reserved bit.
[0109] In addition, in the case where a relay terminal directly connected to a network node is connected to a network device via a dual connection, the relay PDU may also include an indication information, which is used to indicate the cell group where the PDCP entity of the wireless bearer between the relay terminal and the network device is located. That is, according to the indication information, it can be distinguished whether the destination of the relay PDU is a master cell group (Master Cell Group, MCG) or a secondary cell group (Secondary Cell Group, SCG).
[0110] In another possible implementation, the relay PDU format may be the following format 2:
[0111] The relay PDU may include: a terminal identifier, a network device identifier, a radio bearer identifier or a logical channel identifier.
[0112] In this case, the source identifier and the destination identifier of the protocol header of the relay PDU are not empty. For example, if the relay PDU is sent from a remote terminal to a network device, the source identifier in the protocol header of the relay PDU is the terminal identifier, and the destination identifier is the network device identifier; if the relay PDU is sent from a network device to a remote terminal, the source identifier in the protocol header of the relay PDU is the network device identifier, and the destination identifier is the terminal identifier.
[0113] After the relay protocol layer receives the relay PDU, it can determine the source of the relay PDU based on the source identifier contained in the relay PDU, that is, whether the relay PDU is sent by the network device or the remote terminal. According to the destination identifier contained in the relay PDU, it can determine where the relay PDU needs to be sent, that is, whether the relay PDU needs to be sent to the network device or the remote terminal.
[0114] Similarly, if the relay PDU is sent from the network device to the remote terminal, a certain bit can be reserved to identify the broadcast identifier. In this case, it means that the relay PDU includes broadcast data or broadcast signaling. At this time, it means that the relay PDU transmitted is to all connected relay terminals and remote terminals. The bit corresponding to this broadcast identifier cannot be occupied by the node identifier of the remote terminal, relay terminal and network device.
[0115] like Figure 4 As shown, Figure 4 1 is a schematic diagram of another relay PDU format according to an exemplary embodiment of the present application, wherein the R bit identifies a reserved bit. The source identifier and the destination identifier are unique node identifiers of a remote terminal or a network device. In addition, the network device identifier may be a separately reserved identifier, or an identifier generated based on all or part of the bit information of a global base station identifier or a global cell identifier.
[0116] It should be noted that when transmitting the relay PDU, the relay PDU can be generated using the above-mentioned format 1 or format 2.
[0117] Based on the generation method of the above PDU format, the working principles of the relay receiving entity and the relay sending entity included in the relay protocol layer are briefly introduced below.
[0118] The working principle of the relay receiving entity is as follows:
[0119] For each relay PDU received from a remote terminal, taking the generation of a relay PDU in accordance with relay PDU format 1 as an example, the relay receiving entity can obtain a terminal identifier, a radio bearer identifier or a logical channel identifier, indication information and a PDCP PDU according to relay PDU format 1. Except for the PDCP PDU, all other parts are located in the protocol header of the relay PDU.
[0120] Processing of terminal identification:
[0121] If the terminal identifier is not in the downstream routing table established by the relay terminal, the 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 node identifier of the previous hop node. The first routing relationship is the routing relationship when the terminal identifier is used as the destination identifier. If the previous hop node is a remote terminal, the first routing relationship includes the corresponding relationship between the terminal identifier and the terminal identifier. For example, if the terminal identifier is RMUE and the previous hop node is a remote terminal, a routing record is added to the downstream routing table: (RMUE, RMUE).
[0122] It should be noted that if the relay PDU is generated in accordance with the relay PDU format 1, the relay receiving entity can obtain the destination identifier in addition to the above information, for example, the destination identifier is a network device identifier.
[0123] For each relay PDU received from the network device, the relay receiving entity can at least obtain the destination identifier, the radio bearer identifier or the logical channel identifier and the PDCP PDU according to the relay PDU format 1 or the relay PDU format 2. Except for the PDCP PDU, the other parts are all located in the protocol header of the relay PDU.
[0124] Processing of purpose identification:
[0125] If the destination identifier is the same as the node identifier of this node, or this destination identifier is reserved for broadcast data or broadcast signaling, it means that this node needs to process the relay PDU, so the wireless bearer identifier 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.
[0126] If the destination identifier is different from the node identifier of this node, it means that it needs to be forwarded to the relay PDU. Therefore, according to the destination identifier, the relay PDU is forwarded to the next hop node. Alternatively, if the destination identifier is reserved for broadcast data or broadcast signaling, it means that not only does it need to receive the relay PDU itself, but it also needs to be delivered to the relay sending entity of the relay protocol stack, and the relay sending entity sends the relay PDU to all child nodes connected to the relay terminal.
[0127] The working principle of the relay sending entity is as follows:
[0128] If the node needs to generate a relay PDU, the upper layer protocol will pass the information required to generate the relay PDU to the relay protocol layer, including the PDCP PDU, source identifier, destination identifier, radio bearer identifier and cell group identifier, which are all passed to the relay sending entity of the relay protocol stack. The relay sending entity generates the relay PDU according to the relay PDU format 1 or format 2.
[0129] Processing of relay PDU: Whether it is a relay PDU generated by the relay sending entity or a relay PDU obtained from the relay receiving entity, the relay sending entity will query the existing routing table (including the uplink routing table or the downlink routing table) to obtain the destination identifier of the next hop node. If the destination identifier is empty, the relay PDU is forwarded to the default next hop node. If the destination identifier is not empty, the node corresponding to the destination identifier is determined to be the next hop node, and the relay PDU is forwarded to the next hop node.
[0130] Furthermore, if the protocol header of the relay PDU contains indication information for indicating the cell group, then only the relay terminal that directly establishes a communication connection with the network device needs to decide whether to deliver the relay PDU to the MCG or SCG based on 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.
[0131] So far, the above is based on the above Figure 2 The protocol system including the relay protocol stack shown in the figure respectively describes the relay protocol stacks on the remote terminal, the relay terminal and the network device, and the process of receiving and sending the relay PDU based on the relay protocol stack. Next, the relay method and the method for establishing the routing table involved in the embodiment of the present application will be described in detail in conjunction with the accompanying drawings.
[0132] See also Figure 5 ,Should Figure 5 is a flowchart of a relay method according to an exemplary embodiment of the present application, which can be applied to the above Figure 1 In the communication system shown, the relay method is mainly performed by the relay terminal 130, and may include at least part of the following contents:
[0133] Step 510: The relay receiving entity is used to receive the relay PDU sent by the previous hop node, and transfer the relay PDU to the relay sending entity.
[0134] The relay PDU includes a first relay PDU and / or a second relay PDU, wherein the first relay PDU is sent from a remote terminal to a network device, and the second relay PDU is sent from the network device to the remote terminal, or the second relay PDU is broadcast by the network device.
[0135] Step 520: The relay sending entity is used to send the relay PDU to the next hop node.
[0136] The next hop node may be a network device, another relay terminal or a remote terminal.
[0137] It should be noted that after the connection is established, a parent-child node relationship is also established between the network device, the relay terminal and the remote terminal, and the parent-child node relationship will not change. According to the parent-child node relationship existing in the communication system, the next hop node can be the parent node of the relay terminal, such as a network device or a relay terminal, or can be the child node of the relay terminal, such as a remote terminal or a relay terminal.
[0138] According to the above, there are two possible formats of the transmitted relay PDU. Figure 3 In the case of format 1 shown:
[0139] If the direction of transmitting the relay PDU is: from the remote terminal to the network device, then the relay PDU is the first relay PDU, and the protocol header of the first relay PDU includes: the terminal identifier of the remote terminal, and the terminal identifier is the source identifier (Source ID) of the first relay PDU.
[0140] If the direction of transmitting the relay PDU is: from the network device to the remote terminal, then the relay PDU is the second relay PDU, and the protocol header of the second relay PDU includes: the terminal identifier of the remote terminal, and the terminal identifier is the destination identifier (Destination ID) of the second relay PDU.
[0141] Optionally, the protocol header of the second relay PDU further includes: a broadcast identifier, which is a destination identifier of the second relay PDU.
[0142] In this case, it means that the second relay PDU includes broadcast data or broadcast signaling. At this time, all connected relay terminals and / or remote terminals need to receive and process the second relay PDU.
[0143] Optionally, 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. Thus, according to the source identifier, it can be determined that the second PDU comes from the network device.
[0144] When the relay PDU is the above Figure 4 In the case of format 2 shown:
[0145] If the direction of the transmission relay PDU is: sent from the remote terminal to the network device, then the relay PDU is the first relay PDU, and 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. In addition, 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.
[0146] Similarly, if the direction of the transmission relay PDU is: from the network device to the remote terminal, then the relay PDU is the second relay PDU, and the protocol header of the second relay PDU includes: the network device identifier of the network device, and the network device identifier is the source identifier of the second relay PDU. In addition, 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.
[0147] When format 2 is used to design the relay PDU, since the protocol header of the relay PDU includes not only the source identifier but also the destination identifier, when the relay terminal receives the relay PDU, it does not need to determine the transmission direction of the relay PDU by itself, but only needs to send the relay PDU to the node indicated by the destination identifier in the protocol header.
[0148] As an example, when the relay protocol stack is located between the PDCP layer and the layer 2 protocol stack, the protocol header of the first relay PDU further includes: a radio bearer identifier, which is an identifier of a radio bearer between the remote terminal and the network device.
[0149] As an example, when the relay protocol stack is a MAC layer protocol stack, the first relay PDU further includes: a logical channel identifier.
[0150] In order to expand the coverage of the wireless network, it is common for multiple remote terminals to communicate with the network device through a relay terminal, that is, one network device accesses multiple remote terminals through the relay terminal. At this time, for the network device, when receiving the relay PDU from the remote terminal, the network device needs to determine which remote terminal the relay PDU specifically comes from. However, when the remote terminal communicates indirectly with the network device, it will establish multiple wireless bearers according to different data packets or transmission efficiency requirements, and each wireless bearer has its corresponding wireless bearer identifier. Therefore, the protocol header of the first relay PDU can also include a wireless bearer identifier. The network device can determine which remote terminal the relay PDU comes from based on the wireless bearer identifier, thereby improving the effectiveness of communication.
[0151] Among them, the wireless bearer can be SRB or DRB. Because the first remote terminal is in Sidelink communication mode, SRB is a direct communication signaling wireless bearer SL SRB, and DRB is a direct communication data wireless bearer SL DRB. The corresponding wireless bearer identifiers are SL SRB ID and SL DRB ID respectively. When 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 (i.e., the network device) can distinguish the wireless bearers corresponding to different remote terminals through the above-mentioned wireless bearer identifier.
[0152] In addition, the radio bearer identifier can also be LCID, which is used to distinguish the logical channel identifier between the MAC layer and the RLC layer. When the relay protocol stack is implemented at the MAC layer, the logical channel identifier LCID is associated with the PDCP PDU multiplexed in the MAC layer. The destination end (i.e., network equipment) of the relay PDU can distinguish the radio bearers corresponding to different remote terminals through the above logical channels.
[0153] Optionally, since there is a possibility of dual connectivity (DC) between the relay terminal and the network device, as an example, the first relay PDU also includes indication information, which is used to indicate the cell group where the PDCP entity of the wireless bearer between the relay terminal and the network device is located.
[0154] In another possible implementation, the cell group identifier may be included in the network device identifier. That is, if the protocol header of the first relay PDU also includes the network device identifier, the network device identifier may also include the cell group identifier, which is used to indicate the cell group where the PDCP entity of the wireless bearer between the relay terminal and the network device is located.
[0155] Among them, the cell group can be a main cell group MCG or a secondary cell group SCG.
[0156] It should be noted that before the RRC reconfiguration process, uplink messages are routed to the MCG by default. After the RRC reconfiguration process, some PDCP entities of wireless bearers are configured on the MCG, and some are configured on the SCG. When generating a relay PDU, if the remote terminal determines that it is a wireless bearer routed to the MCG based on the configuration information on the RRC reconfiguration message, the identifier used to indicate the MCG is marked in the protocol header or network device identifier of the relay PDU; if it is a wireless bearer routed to the SCG, the identifier used to indicate the SCG is marked in the protocol header or network device identifier of the relay PDU.
[0157] Next, the transmission process of the relay PDU is introduced. Figure 5 In an optional embodiment of the present invention, the previous hop node may be a remote terminal, or the previous hop node may be another relay terminal between the relay terminal and the remote terminal.
[0158] In this case, the relay PDU is the first relay PDU. For the relay receiving entity of the relay terminal, the relay receiving entity is also used to: when 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 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.
[0159] If the routing relationship corresponding to the terminal identifier is not included in the downlink routing table, in order to ensure that the relay terminal can determine how to transmit the second relay PDU when receiving the second relay PDU whose source identifier is the terminal identifier, the relay receiving entity establishes a first routing relationship in the downlink routing table. For example, please refer to Figure 6 ,exist Figure 6 During the transmission of the relay PDU shown, 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 220, the destination identifier in the first routing relationship is the terminal identifier of the remote terminal 10, and the previous hop node is the relay terminal 210.
[0160] As an example, the format of the downlink routing table is shown in Table 1 below. The relay terminal can determine the table of the next hop identifier according to the destination identifier.
[0161] Table 1
[0162] Purpose Identification Next hop node ID
[0163] As an example, in Figure 6 In the transmission process of the relay PDU shown, 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. When the PC5 connection is established between the remote terminal 10 and the relay terminal 210, and the identifier RLUE_1 of the relay terminal 210 is known, when the remote terminal 10 wants to send the first 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.
[0164] After receiving the first relay PDU, the relay terminal 210 finds that the routing relationship corresponding to the source identifier is not included in the downstream routing table, and it is considered that the first relay PDU is a relay PDU sent by a new remote terminal. In other words, 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 downstream routing table. Therefore, when it is determined that the terminal identifier included in the protocol header of the received first relay PDU is not included in the downstream routing table, the relay terminal 210 uses the source identifier included in the protocol header of the first relay PDU as the destination identifier in the reverse direction, and adds a routing record in the downstream routing table, that is, establishes the first routing relationship, as shown in Table 2.
[0165] Table 2
[0166] Purpose Identification Next hop node ID RMUE_1 RMUE_1
[0167] In this way, when a second relay PDU is received in the downlink direction, if the destination identifier in the second relay PDU is RMUE_1, the next hop node can be determined according to the first routing relationship in Table 2.
[0168] For another example, for the relay terminal 220, the relay terminal 220 adds a routing record in its downlink routing table according to the same method, that is, establishes a first routing relationship, as shown in Table 3 below.
[0169] Table 3
[0170] Purpose Identification Next hop node ID RMUE_1 RLUE_1
[0171] Furthermore, a specific implementation of the relay sending entity being used to send the first relay PDU to the next hop node may include: the relay sending entity being used to send the first relay PDU to a default next hop node.
[0172] In a possible implementation manner, the destination identifier in the first relay PDU is empty. In this case, the relay terminal may transmit the first relay PDU according to a default path.
[0173] As an example, the default next hop node may include multiple ones. In this case, the default next hop node can be determined according to a 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 a target value, the relay terminal is determined as the next hop node. The target value can be set according to actual needs.
[0174] For example, please refer to Figure 6 , the next hop node of the relay terminal 210 includes the relay terminal 220 and the relay terminal 230. In this case, the relay terminal 210 can determine the default next hop node according to the selection strategy.
[0175] It should be noted that the above selection strategy can also be determined based on the communication status between the relay terminal and the network device, and a relay terminal with the best communication status is determined as the next hop node. This embodiment of the present application does not limit this.
[0176] In another possible implementation manner, the target identifier in the first relay PDU is not empty. In this case, the relay terminal can determine the next hop node according to the target identifier.
[0177] In addition, when the target identifier in the first relay PDU is not empty, that is, the protocol header of the first relay PDU includes the network device identifier, the relay sending entity is also 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 identifier of the next hop node. The second routing relationship is the routing relationship when the network device identifier is used as the destination identifier.
[0178] As an example, when the destination identifier included in the protocol header of the first relay PDU is the network device identifier of the network device, the relay sending entity queries the uplink routing table based on the network device identifier whether there is a routing relationship with the network device identifier as the destination identifier.
[0179] If a corresponding routing relationship exists, the first relay PDU is sent to the next hop node indicated by the next hop node identifier in the routing relationship.
[0180] If the network device identifier is used as the destination identifier and there is no corresponding routing relationship, the relay sending entity of the relay terminal may transmit the first relay PDU according to a default path.
[0181] The default next hop node may include multiple ones. In this case, the default next hop node can be determined according to a 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 a target value, the relay terminal is determined as the next hop node. The target value can be set according to actual needs.
[0182] For example, please refer to Figure 6 , the next hop nodes of the relay terminal 210 include the relay terminal 220 and the relay terminal 230. In this case, the relay terminal 210 can determine that the default next hop node is 220 according to the selection strategy.
[0183] Afterwards, the relay terminal not only sends the first relay PDU to the next hop, but also establishes a second routing relationship. For example, when the next hop node is determined to be the relay terminal 220, a second routing relationship as shown in Table 4 below is established.
[0184] Based on the above Figure 6 In the transmission process of the relay PDU shown, the network device identifier of the network device 30 is BS_ID, and the second routing relationship is the routing relationship in the uplink routing table. As an example, when the destination identifier is the network device identifier, the relay terminal 210 establishes a second routing relationship in the uplink routing table, as shown in Table 4 below.
[0185] Table 4
[0186] Purpose Identification Next hop node ID BS_ID RLUE_2
[0187] Based on Figure 5 In an optional embodiment, the previous hop node is a network device, or the previous hop node of the relay terminal is another relay terminal between the network device and the relay terminal;
[0188] The relay receiving entity is also used to: determine the first routing relationship corresponding to the terminal identifier from the downlink routing table according to the terminal identifier in the protocol header of the second relay PDU, and determine the node indicated by the node identifier corresponding to the terminal identifier in the first routing relationship as the next hop node.
[0189] Based on the above Figure 6 In the transmission process of the relay PDU shown, the identifier of the network device 30 is BS_ID, and the first routing relationship is the routing relationship in the downlink routing table. As an example, 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. According to the first routing relationship shown in Table 5, it is determined that the node identifier corresponding to the RMUE_1 identifier is RLUE_2, and the next hop node is the relay terminal 220 indicated by RLUE_2.
[0190] Table 5
[0191] Purpose Identification Next hop node ID RMUE_1 RLUE_2
[0192] Optionally, the second relay PDU includes a reference identifier and a PDCP PDU, the reference identifier includes a wireless bearer identifier or a logical channel identifier, and when the protocol header of the second relay PDU also includes a broadcast identifier, the relay receiving entity is also used to submit the reference identifier and PDCP PDU in the second relay PDU to the upper layer.
[0193] The second relay PDU is sent from the network device to the remote terminal. When the protocol header of the second relay PDU also includes a broadcast identifier, it indicates that the second relay PDU needs to be sent to each terminal that communicates directly or indirectly 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 submit the PDCP PDU and reference identifier in the second relay PDU to the upper layer, so that the upper layer can obtain the system's broadcast data or broadcast signaling from the network device.
[0194] The relay method provided in this embodiment is applied to a relay terminal, and the relay terminal includes a relay protocol stack, and the relay protocol stack is located between the packet data convergence protocol PDCP layer and the layer 2 protocol stack, or the relay protocol stack is a media access control MAC layer protocol stack, and 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. In this way, between the remote device and the network device, the relay terminal including the relay protocol stack can autonomously determine the next hop node of the relay PDU to successfully relay the relay PDU from one end to the other end, without the need for the network device to configure the mapping relationship between the wireless bearer and the remote terminal identifier, so that the routing process of the relay PDU is more flexible.
[0195] Figure 7 is a flowchart of a relay method according to another exemplary embodiment of the present application, which can be applied to the above Figure 1 In the communication system shown, the relay method is mainly performed by the remote terminal 120, and may include at least part of the following contents:
[0196] Step 710: 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.
[0197] The first relay PDU is a relay PDU sent by the remote terminal to the network device.
[0198] Optionally, the relay protocol stack further includes a relay receiving entity, based on Figure 7 In an optional embodiment, the above method also includes: the relay receiving entity is used to receive a second relay PDU from the previous 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.
[0199] As an example, 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.
[0200] Optionally, the method further includes: the relay receiving entity is further used to submit 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.
[0201] It should be noted that 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, after the relay receiving entity receives the second relay PDU, it will hand over the reference identifier and PDCP PDU included in the second relay PDU to the upper layer for processing. For the second relay PDU not sent to itself, the remote terminal can directly discard the second relay PDU without passing it to the upper layer for processing.
[0202] Optionally, the above method also includes: the second relay PDU includes a reference identifier and a PDCP PDU, and the above method also includes: the relay receiving entity is also used to submit the reference identifier and 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 a broadcast identifier.
[0203] By predicting in advance whether the destination identifier of the second relay PDU is the same as its own node identifier, the data transmission efficiency can be improved. In addition, the accuracy of data transmission is ensured and unnecessary data packet processing is reduced.
[0204] Optionally, when the relay PDU format 1 is adopted to generate the 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.
[0205] Optionally, when the relay PDU format 2 is used to generate the relay PDU, the protocol header of the first relay PDU includes: the terminal identifier of the remote terminal, which is the source identifier of the first relay PDU. In addition, 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.
[0206] 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 packet data convergence protocol PDCP layer 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. Among them, the first relay PDU is the relay PDU sent by the remote terminal to the network device. That is, the remote terminal can autonomously determine the next hop node of the first relay PDU to send the first relay PDU to the network device end. In this process, there is no need for the network device to configure the mapping relationship between the wireless bearer and the remote terminal identifier, so that the routing process of transmitting the first relay PDU is more flexible.
[0207] Since the relay method provided in this application introduces a relay protocol layer into the protocol stacks of the remote terminal, the relay terminal and the network device, the steps of applying the method to each node are generally the same. For specific implementation details, see Figure 5 The relay method embodiment applied to the relay terminal is not described in detail here.
[0208] Figure 8 is a flowchart of a relay method according to another exemplary embodiment of the present application, which can be applied to the above Figure 1 In the communication system shown, the relay method is mainly performed by the network device 110, and may include at least part of the following contents:
[0209] Step 810: The relay receiving entity is used to receive a first relay PDU from a previous hop node, where the first relay PDU is sent from a remote terminal to a network device.
[0210] Optionally, in the case where the relay protocol stack is located between the PDCP layer and the layer 2 protocol stack, the protocol header of the first relay PDU further includes: a radio bearer identifier, where the radio bearer identifier is an identifier of a radio bearer between the remote terminal and the network device;
[0211] In the case where the relay protocol stack is a MAC layer protocol stack, the first relay PDU further includes: a logical channel identifier.
[0212] Optionally, if the destination identifier of the first relay PDU is not empty, the relay receiving entity is further used to submit the PDCP PDU and the radio bearer identifier included in the first relay PDU to the upper layer when the destination identifier of the first relay PDU is the same as the local identifier.
[0213] Optionally, if the destination identifier of the first relay PDU is empty, the relay receiving entity is also used to submit the PDCP PDU and the radio bearer identifier included in the first relay PDU to the upper layer, or to submit the PDCP PDU and the logical channel identifier included in the first relay PDU to the upper layer.
[0214] Optionally, the relay protocol stack also includes a relay sending entity, and the above method also includes: the relay sending entity is used to receive a 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.
[0215] 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.
[0216] Optionally, the protocol header of the second relay PDU further includes: a terminal identifier of the remote terminal, where the terminal identifier is a destination identifier of the second relay PDU.
[0217] Optionally, 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.
[0218] The relay method provided in the embodiment of the present application is applied to a network device, the network device includes a relay protocol stack, the relay protocol stack is located between the packet data convergence protocol PDCP layer and the layer 2 protocol stack of the Uu interface, or the relay protocol stack is a media access control MAC layer protocol stack, 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 first relay PDU is sent by the remote terminal 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 autonomously 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 mapping relationship between the wireless bearer and the remote terminal identifier, so that the routing process of transmitting the second relay PDU is more flexible.
[0219] Since the relay method provided in this application introduces a relay protocol layer into the protocol stacks of the remote terminal, the relay terminal and the network device, the steps of applying the method to each node are generally the same. For specific implementation details, see Figure 5 The relay method embodiment applied to the relay terminal is not described in detail here.
[0220] Next, the process of the remote terminal communicating with the network device through the relay terminal in the present application is explained.
[0221] like Fig. 9 As shown, Fig. 9 A relay method according to another exemplary embodiment of the present application is shown, and the method is applied to the above Figure 1 The communication system shown includes a remote terminal, a relay terminal and a network device. The relay method may include at least part of the following contents:
[0222] 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.
[0223] The first relay PDU is a relay PDU sent by the remote terminal to the network device.
[0224] Step 920: The relay receiving entity of the relay terminal receives the first relay PDU sent by the previous hop node, and transmits the first relay PDU to the relay sending entity.
[0225] Wherein, when the protocol header of the first relay PDU includes a network device identifier, the relay sending entity is used 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 a routing relationship when the network device identifier is used as the destination identifier. The previous hop node may be a remote terminal, or the previous hop node may be another relay terminal between the relay terminal and the remote terminal.
[0226] Optionally, the first relay PDU further includes indication information, where the indication information is used to indicate a cell group where a PDCP entity of a radio bearer between the relay terminal and the network device is located, wherein the cell group includes a primary cell group MCG or a secondary cell group SCG.
[0227] Optionally, the relay receiving entity is also used to: when the downlink routing table does not include a 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 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.
[0228] Step 930: The relay sending entity of the relay terminal sends the first relay PDU to the next hop node.
[0229] Step 940: The relay receiving entity of the network device receives the first relay PDU from the previous hop node.
[0230] It should be noted that when the relay receiving entity of the network device receives the first relay PDU, it determines whether the destination identifier of the first relay PDU is empty. If the destination identifier of the first relay PDU is not empty, and the destination identifier of the first relay PDU is the same as the identifier of the local end, the relay receiving entity submits the PDCP PDU and the wireless bearer identifier included in the first relay PDU to the upper layer.
[0231] In addition, after receiving the first relay PDU, the network device may send at least one of a response message, broadcast data or broadcast signaling including the first relay PDU to the remote terminal. See the downlink routing process of steps 950 to 980 below.
[0232] 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.
[0233] 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.
[0234] Step 960: The relay receiving entity of the relay terminal receives the second relay PDU sent by the previous hop node, and transmits the second relay PDU to the relay sending entity.
[0235] The previous hop node is a network device, or the previous hop node is another relay terminal between the relay terminal and the network device.
[0236] It should be noted that, when the relay receiving entity determines that the protocol header of the second relay PDU also includes a broadcast identifier, the second relay PDU is delivered to the upper layer.
[0237] Step 970: The relay sending entity of the relay terminal sends the second relay PDU to the next hop node.
[0238] 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.
[0239] Step 980: The relay receiving entity of the remote terminal receives the second relay PDU from the previous hop node.
[0240] It should be noted that, when 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.
[0241] Optionally, when the relay receiving entity determines that the protocol header of the second relay PDU also includes a broadcast identifier, the second relay PDU is delivered to an upper layer.
[0242] In the above-mentioned process of transmitting relay PDU, it should be noted that the first relay PDU is transmitted in the uplink direction, and the second relay PDU is transmitted in the downlink direction. 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 the 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 the uplink transmission.
[0243] In the relay method embodiment of the present application, since a new relay protocol layer is introduced into the protocol stack of the remote terminal, the relay terminal and the network device, the relay protocol stack is located between the packet data convergence protocol PDCP layer and the layer 2 protocol stack of the PC5 interface, or the relay protocol stack is the 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; wherein the relay PDU includes a first relay PDU and / or a second relay PDU, the first relay PDU is sent from the remote terminal to the network device, the second relay PDU is sent from the network device to the remote terminal, or the second relay PDU is broadcast by the network device. In this way, between the remote terminal and the network device, the relay terminal including the relay protocol stack can autonomously determine the next hop node of the relay PDU to successfully relay the relay PDU from one end to the other end. There is no need for the network device to configure the mapping relationship between the wireless bearer and the remote terminal identifier, making the routing process of the relay PDU more flexible.
[0244] In addition, the relay method in the present application can not only be implemented by introducing a new relay protocol stack between the packet data convergence protocol PDCP layer and the layer 2 protocol stack, but also can implement the function of the relay protocol at the MAC layer. Fig.10 The protocol stack shown in the system block diagram a of the protocol stack in, or the protocol stack shown in the system block diagram b of the protocol stack, Fig.10 It is a system block diagram of a protocol stack provided by an exemplary embodiment of the present application.
[0245] The MAC CE used to identify the terminal is introduced at the MAC layer of the Uu interface. There are two possible contents of this MAC CE. One is the network-assigned identifier saved by the terminal before connecting to the network. This identifier can be the STMSI, I-RNTI or a random number of the NAS layer, or part of the UE identifier, such as the lowest 16 bits. The other is the C-RNTI newly assigned to the terminal by the network after the UE is connected to the network. The above-mentioned terminals are remote terminals and relay terminals.
[0246] In addition to using the content of MAC CE as the terminal identifier, the function of the relay protocol is implemented at the MAC layer. In addition, a MAC PDU of a Uu interface can simultaneously contain multiple PDCP PDUs. Multiple PDCP PDUs may belong to different logical channels, and there is no need to introduce a new protocol layer. The function of the above-mentioned relay protocol layer is implemented at the MAC layer.
[0247] Through the LCID in the MAC PDU and the correspondence between the LCID and the radio bearer, no additional DRB ID is required in the MAC PDU. The mapping relationship between the LCID and the DRB ID is specified in the RRC configuration message.
[0248] It should be noted that the implementation of the relay protocol function at the MAC layer is basically the same as the solution of introducing a new relay protocol layer between the PDCP layer and the layer 2 protocol stack of the PC5 interface in terms of route establishment and maintenance. The difference is that the terminal identifier uses the terminal identifier MAC CE in the MAC PDU. When the MAC PDU is sent from the child node to the parent node, this terminal identifier MAC CE is interpreted as the source identifier, otherwise it is interpreted as the destination identifier.
[0249] The function of implementing the relay protocol at the MAC layer is to establish and maintain the route. Refer to the solution of introducing a new relay protocol layer between the PDCP layer and the layer 2 protocol stack of the PC5 interface mentioned above. Figure 5-Figure 9 The step flow chart and detailed explanation shown are not repeated here.
[0250] Fig.11 is a flowchart of a method for generating a routing table according to an exemplary embodiment of the present application. The method for generating a routing table can be applied to the above Figure 1 In the relay terminal 120 of the communication system shown, the method for generating the routing table may include at least part of the following contents:
[0251] Step 1110: Receive a first relay PDU from a remote terminal, where the first relay PDU includes a terminal identifier of the remote terminal, and the first relay PDU is sent by the remote terminal to the network device.
[0252] 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.
[0253] The previous hop node refers to the previous hop node of the relay terminal, and the previous hop node may be a remote terminal, or the previous hop node may be another relay terminal between the relay terminal and the remote terminal.
[0254] Step 1130: Send the first relay PDU to the next hop node.
[0255] 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 routing relationship when the terminal identifier is used as the destination identifier.
[0256] It should be noted that, in the uplink direction, after the first relay PDU is generated using relay PDU format 1, during the transmission process, 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. When the first relay PDU is generated using relay PDU format 2, during the transmission process, the protocol header of the first relay PDU includes a terminal identifier and a network device identifier, the terminal identifier is the source identifier 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.
[0257] Similarly, in the downlink direction, based on Fig.11 In an optional embodiment, the method further includes: receiving 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 broadcast by the network device; according to the destination identifier in the protocol header of the second relay PDU and the first routing relationship, sending the second relay PDU to the next hop node. The destination identifier includes a terminal identifier, or the destination identifier includes a broadcast identifier.
[0258] As an example, see Fig.12 , Fig.12 It is a schematic diagram of a relay process provided by an exemplary embodiment of the present application, which is applied to the method for generating a routing table provided by the present application to request and forward system messages of a network device, etc., wherein the system messages include broadcast data or broadcast signaling.
[0259] In the relay process diagram shown in FIG12 , the terminal identifier of the remote terminal is RMUE, the terminal identifier of the relay terminal is RLUE, and the network device identifier of the network device is BS_ID.
[0260] The remote terminal detects the existence of the relay terminal and wants to receive the broadcast message of the service cell where the relay terminal is located to determine whether it can obtain service in the service 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 the reception of system messages.
[0261] The protocol header of the first relay PDU may include: RMUE.
[0262] Alternatively, the protocol header of the first relay PDU may include RMUE and BS_ID, wherein the RMUE is a source identifier of the first relay PDU, and the BS_ID is a destination identifier of the first relay PDU.
[0263] The relay terminal establishes a 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. For the relay terminal, the network device is the only node in the uplink, so the network device is the default next hop node, and the relay terminal sends the first relay PDU to the network device.
[0264] After receiving the 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. The third routing relationship indicates that the second relay PDU sent to the remote terminal RMUE is forwarded through the relay terminal RLUE.
[0265] In addition, when the destination identifier included in the first relay PDU is not empty, the network device determines whether the first relay PDU is sent to itself based on the destination identifier. If so, the network device delivers the first relay PDU to the upper layer protocol, such as to the RRC layer.
[0266] In the downlink process, the network device can send messages based on the third routing relationship established in the uplink. The uplink routing and the downlink routing are symmetrical.
[0267] As an example, the RRC layer of the network device decides to transmit the system message to the remote terminal on a dedicated channel after processing, and then sends the second relay PDU of the system message to the relay terminal according to the established third routing relationship, namely (RMUE, RLUE).
[0268] The protocol header of the second relay PDU may include: a terminal identifier, and the terminal identifier is a destination identifier of the second relay PDU.
[0269] Alternatively, the protocol header of the second relay PDU may include a terminal identifier and a network device identifier, wherein the terminal identifier is a destination identifier of the second relay PDU, and the network device identifier is a source identifier of the second relay PDU.
[0270] Furthermore, the second relay PDU may also include a broadcast identifier. For example, the broadcast identifier may be DESTINATION_BC, which is used to indicate that the second relay PDU includes broadcast data or broadcast signaling.
[0271] After receiving the second relay PDU, the relay terminal determines 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 its own RRC layer for processing. At the same time, the relay terminal forwards the second relay PDU to the remote terminal. After receiving the second relay PDU, the remote terminal also determines 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 its own RRC layer for processing.
[0272] Optionally, the first relay PDU further includes a radio bearer identifier or a logical channel identifier, where the radio bearer identifier is an identifier of a radio bearer between the remote terminal and the network device.
[0273] Optionally, when the function of the relay protocol is implemented through the MAC layer, the first relay PDU is relayed through the self-media access control MAC layer.
[0274] Since there is a parent-child node relationship in the communication system, and all parent-child nodes can know each other's identity when establishing the parent-child relationship. When the connection is interrupted or the link is changed, the parent-child relationship will change, and the original routing table needs to be updated. Therefore, when the node identity of a node changes, this node can notify all adjacent nodes to update, so that each node can autonomously update the established routing table.
[0275] Therefore, based on Fig.11 In an optional embodiment, if the next hop node is a network device, the method further includes:
[0276] When the first relay PDU includes a CCCH (Common Control Channel) message, obtain the first cell radio network temporary identifier C-RNTI (Cell Radio-Network Temporary Identifier) information allocated by the network device to itself, and send the first C-RNTI information to the previous hop node.
[0277] Among them, since a network device is connected to multiple relay terminals, in order to distinguish different relay terminals, after the relay terminal and the network device establish a connection, the network device can allocate a new terminal identifier for the connected relay terminal.
[0278] It should be noted that when the relay terminal uses a new terminal identifier assigned by the network device, it is necessary to inform other connected previous hop nodes of the updated terminal identifier, wherein the previous hop node may be a remote terminal or a relay terminal located between the relay terminal and the remote terminal.
[0279] Optionally, the method further includes: receiving second C-RNTI information from the remote terminal, where the second C-RNTI information is allocated by the network device to the remote terminal, and updating the terminal identifier in the first routing relationship to the second C-RNTI information.
[0280] Similarly, when the terminal identification of the remote terminal is updated, the relay terminal and the network device communicating with the remote terminal need to be informed so that the relay terminal and the network device can update the routing table.
[0281] As an example, Fig.13 As shown, Fig.13 It is a schematic diagram of a relay process provided by another exemplary embodiment of the present application.
[0282] The remote terminal sends a CCCH message to the network to start establishing or restoring the above Fig.12 In the RRC connection shown, the relay terminal is in an idle state or an inactive state.
[0283] Fig.13 The relay process shown is used to explain how to establish a routing table during the process of establishing, restoring or reestablishing an RRC connection, and how to forward the first relay PDU from the remote terminal to the network device.
[0284] In the relay process diagram shown in 13, the original identifier of the remote terminal is: RMUE. After establishing the RRC connection, the new terminal identifier assigned to it by the network device is: C-RNTI_M. The original identifier of the relay terminal is: RLUE. After establishing the Uu connection with the network device, the new terminal identifier assigned to it by the network device is: C-RNTI_L. Assume that the network device identifier of the network device is: BS_ID.
[0285] In the process of establishing the second routing relationship in the uplink, the remote terminal and the relay terminal establish a PC5 connection. After the PC5 connection is established, the remote terminal can obtain the terminal identification RLUE of the relay terminal. At this time, the remote terminal records a routing relationship (BS_ID, RLUE). The meaning of this routing relationship is: all relay PDUs sent to the network device need to be sent to the relay terminal with the terminal identification RLUE.
[0286] The remote terminal sends a first relay PDU including a CCCH message to the relay terminal, wherein the protocol header of the first relay PDU may include: RMUE.
[0287] Alternatively, the protocol header of the first relay PDU may include RMUE and BS_ID, wherein the RMUE is a source identifier of the first relay PDU, and the BS_ID is a destination identifier of the first relay PDU.
[0288] After receiving the first relay PDU, the relay terminal establishes a first routing relationship (RMUE, RMUE). An RRC connection and a wireless bearer for forwarding the first relay PDU are established with the network device. For the relay terminal, the network device is the only node in the uplink, so the network device is the default next hop node. The relay terminal sends the first relay PDU to the network device and establishes a second routing relationship (BS_ID, BS_ID). In addition, after the network device establishes a connection with the relay terminal, it reallocates a terminal identifier to the relay terminal.
[0289] As an example, the network device may allocate first C-RNTI information to the relay terminal, such as the first C-RNTI information is C-RNTI_L. Fig.13 In the relay process diagram shown, the relay terminal updates its own terminal identifier to C-RNTI_L and informs the remote terminal of the updated terminal identifier. The relay terminal forwards the first relay PDU containing the CCCH message to the network device.
[0290] For the remote terminal, after receiving the C-RNTI_L sent by the relay terminal, the recorded routing relationship (BS_ID, RLUE) is changed to (BS_ID, C-RNTI_L).
[0291] For the network device, since the network device receives the relay PDU with the source identifier of RMUE for the first time, a routing record (RMUE, C-RNTI_L) is established. As an example, the network device delivers the CCCH message to the upper RRC protocol layer.
[0292] During downlink communication, after processing the CCCH message, the network device sends a second relay PDU containing an RRC connection establishment message to the relay terminal. The protocol header of the second relay terminal may include the terminal identifier 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, and the RMUE is the destination identifier of the second relay PDU.
[0293] Optionally, according to different CCCH messages, the network device may also send other RRC messages, such as RRC connection reestablishment or RRC recovery message to the relay terminal.
[0294] After receiving the second relay PDU, the relay terminal forwards the second relay PDU to the remote terminal by querying the routing record (RMUE, RMUE).
[0295] 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 delivers the PDCU and radio bearer identifier (or logical channel identifier) in the second relay PDU to the RRC layer protocol.
[0296] In addition, in the received RRC connection establishment message, the network device reallocates a new terminal identifier to the remote terminal, that is, the second relay PDU includes second C-RNTI information. As an example, the new terminal identifier is C-RNTI_M.
[0297] After processing this RRC message, the RRC layer of the remote terminal notifies the relay terminal of the previous hop node of the second C-RNTI information through PC5 signaling. After receiving the second C-RNTI information, the relay terminal updates the first routing relationship (RMUE, RMUE) to (C-RNTI_M, C-RNTI_M).
[0298] In addition, after the network device assigns a new terminal identifier to the remote terminal, its own routing 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 updated by RMUE to C-RNTI_M. In other words, the remote terminal sends the first relay PDU containing the RRC connection completion 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.
[0299] When the network device receives the first relay PDU, it 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 routing between the network device and the remote terminal has been established.
[0300] As an example, after the routing relationship is updated, in the protocol header of the second relay PDU transmitted in the downlink, the source identifier is BS_ID and the destination identifier is C-RNTI_M. In the protocol header of the first relay PDU transmitted in the uplink, the source identifier is C-RNTI_M and the destination identifier is BS_ID.
[0301] It should be noted that Fig.13In the relay process shown, all relay PDUs are described in accordance with the relay PDU format 2. When the relay PDU format 1 is used, it is sufficient to omit the BS_ID in the protocol header of the relay PDU. Whether the destination identifier contained in the protocol header of the relay PDU is a remote terminal or a network device is determined according to the direction in which the relay PDU is sent.
[0302] To sum up, the method for establishing a routing table provided in the present application can not only realize the autonomous establishment of routing relationships, but also can modify the terminal identifiers of the relay terminal and the remote terminal connected to the network device according to the RRC connection status, thereby improving the flexibility of the relay solution.
[0303] Therefore, based on Fig.11 In an optional embodiment, the first relay PDU also includes indication information, where 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.
[0304] Optionally, the network device identifier further includes a cell group identifier, and the cell group identifier is used to indicate a cell group where a PDCP entity of a radio bearer between the relay terminal and the network device is located.
[0305] Optionally, the cell group includes a main cell group MCG or a secondary cell group SCG.
[0306] That is, since there may be a dual connection between the relay terminal and the network device, the relay terminal needs to determine to which cell group the first relay PDU is to be sent when communicating with the network device.
[0307] As an example, before the RRC reconfiguration process, 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. When the remote terminal generates the first relay PDU based on the configuration information on the RRC reconfiguration message, if it is routed to the MCG, then the identifier used to indicate the MCG is marked in the protocol header of the first relay PDU. For example, the identifier may be the primary cell group identifier. If it is routed to the SCG, then the identifier used to indicate the SCG is marked in the protocol header of the first relay PDU. For example, the identifier may be the secondary cell group identifier.
[0308] See also Fig.14 , Fig.14 It is a schematic diagram of a relay process provided by another exemplary embodiment of the present application.
[0309] Compared with Example 13, the difference of this example is that 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 relay PDU format 1. This example is also applicable to relay PDU format 2. It is only necessary to add a network device identifier in the protocol header of each relay PDU. For example, in the first relay PDU of uplink transmission, the network device identifier is the destination identifier, and in the second relay PDU of downlink transmission, the network device identifier is the source identifier.
[0310] In this example, in order to enable relay terminal 2 to determine how the first relay PDU from the remote terminal is routed, indication information is included in the protocol header of the first relay PDU, which is used to indicate whether the first relay PDU is sent to MCG or SCG.
[0311] It should be noted that if this indication information does not exist, the relay terminal 2 will forward the first relay PDU to the MCG. If the PDCP entity of the wireless bearer between the remote terminal and the network device is configured on the MCG (SCG), the uplink and downlink relay PDUs are transmitted between the remote terminal and the MCG (SCG). Among them, the routing of the wireless bearer is fixed, such as the PDCP entities of SRB0, SRB1 and SRB2 are configured on the MCG, and the PDCP entity of SRB3 is configured on the SCG.
[0312] The specific relay process of this example is as follows Fig.13 The remote terminal's routing establishment process and Fig.13 The process shown is similar and will not be described in detail.
[0313] In addition, if the format of the relay PDU adopts format 2, the MCG (SCG) identifier can be directly used for indication. For example, the cell group identifier of MCG is MCG_ID, and the cell group identifier of SCG is SCG_ID, which can be included in the network device identifier. In this way, before RRC reconfiguration, all signaling and data are defaulted between the remote terminal and MCG. In the RRC reconfiguration message, the remote terminal sets the destination identifier in the protocol header of the uplink relay PDU to MCG_ID or SCG_ID according to the location of the PDCP entity. Relay terminal 2 needs to determine the correct route based on different destination identifiers.
[0314] Furthermore, the first relay PDU includes a switching message, and the switching message is used to trigger the relay terminal to establish a connection with a target cell, and the target cell is a cell after switching.
[0315] That is, if the remote terminal has established a wireless link of the Uu interface with the source network device. As the remote terminal gradually moves out of the coverage of the source network device, the remote terminal finds through measurement that there is another available relay terminal, so it sends a measurement report to the source network device, and the remote terminal requests to switch from the Uu interface to a relay link.
[0316] See also Fig.15 , Fig.15 This is a schematic diagram of a relay process provided by another exemplary embodiment of the present application. In this example, the terminal identifier of the remote terminal is C-RNTI_M, the terminal identifier of the relay terminal is C_RNTI_L, and the network device identifier of the network device is BS_ID. As an example, when the remote terminal needs to switch from the Uu interface to a relay link, before sending the measurement report, the remote terminal already knows the target service cell where the relay terminal is located, and reports the target service cell as part of the measurement result to the source network device.
[0317] The source network device and the target network device where the target serving cell is located exchange switching messages according to the conventional cell switching process, and send the switching command to the remote terminal.
[0318] Optionally, in order to reduce the delay of the switching, the remote terminal can establish a PC5 connection with the relay terminal before receiving the switching command. After receiving the switching command, the remote terminal sends the first relay PDU containing the switching completion message to the relay terminal. Assume that the first relay PDU is generated in the above format 1.
[0319] The arrival of this first relay PDU triggers the process of establishing an RRC connection and relay radio bearer between the relay terminal and the target network device, and the relay terminal adds routing records in its uplink routing table and downlink routing table, 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, it only needs to add a radio bearer for transmitting the relay PDU, and no routing relationship needs to be established.
[0320] The relay terminal sends the first relay PDU containing the handover completion message to 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).
[0321] Optionally, in order to further reduce the switching delay, the connection between the remote terminal and the target network device may also be established in advance.
[0322] Optionally, the measurement report may also include prompt information, such as telling the source network device that it needs 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 switching command based on such prompt information, such as omitting the configuration parameters of the RLC layer and the protocols below the RLC layer, and appropriately extending the time for the switching execution protection to ensure the smooth completion of the protection switching.
[0323] It should be noted that this example is described based on relay PDU format 1, but is also applicable to relay PDU format 2. When relay PDU format 2 is used, the network device identifier BS_ID of the target network device needs to be added as the destination identifier in the relay PDU protocol header of the uplink transmission, and the network device identifier BS_ID of the target network device needs to be added as the source identifier in the relay PDU protocol header of the downlink transmission.
[0324] In summary, the routing table generation method provided by the present application, when receiving or sending a relay PDU, the relay terminal determines the next hop node of the relay PDU according to the protocol header of the relay PDU and the routing relationship in the routing table, and the process of transmitting the relay PDU is more flexible. The transmission route of the relay PDU can be defined according to the routing table, which also alleviates the congestion and packet loss when transmitting data packets over the wireless bearer to a certain extent, and the relay solution is more flexible and efficient. In addition, the above-mentioned routing table generation process is not only applicable to relay terminals, but also to remote terminals and network devices.
[0325] Fig.16 is a flowchart of a method for generating a routing table according to another exemplary embodiment of the present application, and the method for generating a routing table can be applied to the above Figure 1 In the network device 110 of the communication system shown, the method for establishing the routing table may include at least part of the following contents:
[0326] Step 1610: Receive a first relay PDU from a remote terminal, the protocol header of the first relay PDU includes a terminal identifier of the remote terminal, and the first relay PDU is a relay PDU sent by the remote terminal to the network device.
[0327] It should be noted that the first relay PDU includes a PDCP PDU and a wireless bearer identifier, the wireless bearer indicated by the wireless bearer identifier is a wireless bearer between a remote terminal and a network device, and the first relay PDU includes a data packet of the wireless bearer; or, the first relay PDU includes a PDCP PDU and a logical channel identifier.
[0328] In addition, for the received first relay PDU, if the first relay PDU adopts relay PDU format 1, then when the destination identifier of the first relay PDU is empty, 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.
[0329] For the first relay PDU received, if the first relay PDU adopts relay PDU format 2, then when the purpose identifier of the first relay PDU is not empty, if the purpose identifier of the first relay PDU is the same as the local identifier, the PDCP PDU and the wireless bearer identifier are submitted to the upper layer, or the PDCP PDU and the logical channel identifier are submitted to the upper layer.
[0330] Step 1620: Establish a third routing relationship, the third routing relationship includes the terminal identifier and the node identifier of the previous hop node of the network device, and the third routing relationship is a routing relationship when the terminal identifier is used as the destination identifier.
[0331] It should be noted that, since 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 as the third routing relationship.
[0332] The establishment of the third routing relationship is similar to the establishment process of the first routing relationship and the second routing relationship. Fig.11 The flow chart of the method for generating the routing table and the detailed step implementation example shown are not repeated here.
[0333] In summary, the routing table establishment method provided in the present application receives a first relay PDU from a remote terminal, the protocol header of the first relay PDU includes a terminal identifier of the remote terminal, and the first relay PDU is a relay PDU sent by the remote terminal to a network device. A third routing relationship is established, the third routing relationship includes a terminal identifier and a node identifier of a previous hop node of the network device, and the third routing relationship is a routing relationship when the terminal identifier is used as a destination identifier. In this way, in subsequent communication processes, the network device can determine which relay terminal the second relay PDU sent to the remote terminal should be transmitted through based on the establishment of the third routing relationship. In this process, the network device does not need to pre-configure the mapping relationship between the wireless bearer and the remote terminal identifier, so that the routing process of transmitting the first relay PDU is more flexible.
[0334] Fig.17It is a structural schematic diagram of a relay device according to an exemplary embodiment. The device 1700 can be configured in a relay terminal. The relay device includes a relay protocol stack. The relay protocol stack is located between the packet data convergence protocol PDCP layer and the protocol stack of the PC5 interface. Alternatively, 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. The device 1700 includes:
[0335] The relay receiving module 1710 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 module;
[0336] The relay sending module 1720 is used to send the relay PDU to the next hop node;
[0337] Optionally, the relay PDU includes a first relay PDU, and a protocol header of the first relay PDU includes: a terminal identifier of a remote terminal, and the terminal identifier is a source identifier of the first relay PDU.
[0338] Optionally, the protocol header of the first relay PDU further includes: a network device identifier of the network device, where the network device identifier is a destination identifier of the first relay PDU.
[0339] Optionally, the relay PDU includes a second relay PDU, and 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.
[0340] Optionally, the protocol header of the second relay PDU includes: a broadcast identifier, where the broadcast identifier is a destination identifier of the second relay PDU.
[0341] Optionally, the protocol header of the second relay PDU further includes: a source identifier, where the source identifier is a network device identifier of the network device.
[0342] Optionally, in the case where the relay protocol stack is located between the PDCP layer and the layer 2 protocol stack, the protocol header of the first relay PDU further includes: a radio bearer identifier, where the radio bearer identifier is an identifier of a radio bearer between the remote terminal and the network device;
[0343] In the case where the relay protocol stack is a MAC layer protocol stack, the first relay PDU further includes: a logical channel identifier.
[0344] Optionally, the first relay PDU further includes indication information, where the indication information is used to indicate a cell group where a Packet Data Convergence Protocol PDCP entity of a radio bearer between the relay terminal and the network device is located.
[0345] Optionally, the network device identifier further includes a cell group identifier, and the cell group identifier is used to indicate a cell group where a PDCP entity of a radio bearer between the relay terminal and the network device is located.
[0346] Optionally, the cell group includes a main cell group MCG or a secondary cell group SCG.
[0347] Optionally, the previous hop node is a remote terminal, or the previous hop node is another relay terminal between the relay terminal and the remote terminal;
[0348] The relay receiving module 1710 is also used to: when 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, the first 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.
[0349] Optionally, the relay PDU includes a first relay PDU, and the relay sending module 1720 is configured to send the first relay PDU to a next hop node, including:
[0350] The relay sending module 1720 is used to send the first relay PDU to the default next hop node.
[0351] Optionally, the relay PDU includes a first relay PDU. When the protocol header of the first relay PDU includes a network device identifier, the relay sending module 1720 is used to establish a second routing relationship in the uplink routing table. The second routing relationship includes the network device identifier and a node identifier of the next hop node. The second routing relationship is a routing relationship when the network device identifier is used as the destination identifier.
[0352] Optionally, the relay PDU includes a second relay PDU, the previous hop node is a network device, or the previous hop node of the relay terminal is another relay terminal between the network device and the relay terminal;
[0353] The relay receiving module 1710 is further used to: determine a first routing relationship corresponding to the terminal identifier from a downlink routing table according to the terminal identifier in the protocol header of the second relay PDU;
[0354] 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.
[0355] Optionally, 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;
[0356] In the case that the protocol header of the second relay PDU further includes a broadcast identifier, the relay receiving module is further configured to deliver the reference identifier and the PDCP PDU in the second relay PDU to an upper layer.
[0357] Optionally, in the case where the relay terminal interacts with the network device, the layer 2 protocol stack includes a layer 2 protocol stack of the Uu interface;
[0358] In the case where a relay terminal interacts with another relay terminal, or in the case where a relay terminal interacts with a remote terminal, the layer 2 protocol stack includes a layer 2 protocol stack of a PC5 interface.
[0359] Optionally, the layer 2 protocol stack includes a radio link control RLC layer protocol stack and a media access control MAC layer protocol stack.
[0360] The relay method provided in this embodiment is applied to a relay terminal, and the relay terminal includes a relay protocol stack, and the relay protocol stack is located between the packet data convergence protocol PDCP layer and the layer 2 protocol stack, or the relay protocol stack is a media access control MAC layer protocol stack, and 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. In this way, between the remote device and the network device, the relay terminal including the relay protocol stack can autonomously determine the next hop node of the relay PDU to successfully relay the relay PDU from one end to the other end, without the need for the network device to configure the mapping relationship between the wireless bearer and the remote terminal identifier, so that the routing process of the relay PDU is more flexible.
[0361] Fig.18 1800 is a schematic diagram of a structure of a relay device according to an exemplary embodiment. The device 1800 can be configured in a remote terminal. The relay device includes a relay protocol stack. The relay protocol stack is located between the packet data convergence protocol PDCP layer and the protocol stack of the PC5 interface. Alternatively, the relay protocol stack is a MAC layer protocol stack. The relay protocol stack includes a relay sending module 1810. The device 1800 may include:
[0362] The relay sending module 1810 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;
[0363] The first relay PDU is a relay PDU sent by the remote terminal to the network device.
[0364] Optionally, the relay protocol stack also includes a relay receiving module 1820, which is used to receive a second relay PDU from the previous hop node, where 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.
[0365] Optionally, 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;
[0366] The relay receiving module 1820 is further configured to deliver the second relay PDU including the reference identifier and the PDCP PDU to an 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.
[0367] Optionally, 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;
[0368] The relay receiving module 1820 is further configured to, when it is determined that the protocol header of the second relay PDU also includes a broadcast identifier, submit the reference identifier and the PDCP PDU included in the second relay PDU to an upper layer.
[0369] Optionally, the protocol header of the first relay PDU includes: a terminal identifier of the remote terminal, where the terminal identifier is a source identifier of the first relay PDU.
[0370] Optionally, the protocol header of the first relay PDU further includes: a network device identifier of the network device;
[0371] The network device identifier is the destination identifier of the first relay PDU.
[0372] 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 packet data convergence protocol PDCP layer 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. Among them, the first relay PDU is the relay PDU sent by the remote terminal to the network device. That is, the remote terminal can autonomously determine the next hop node of the first relay PDU to send the first relay PDU to the network device end. In this process, there is no need for the network device to configure the mapping relationship between the wireless bearer and the remote terminal identifier, so that the routing process of transmitting the first relay PDU is more flexible.
[0373] Fig.1919 is a schematic diagram of a structure of a relay device according to an exemplary embodiment. The device 1900 can be configured in a network device. The relay device includes a relay protocol stack. The relay protocol stack is located between the packet data convergence protocol PDCP layer and the protocol stack of the PC5 interface. Alternatively, the relay protocol stack is a MAC layer protocol stack. The relay protocol stack includes a relay receiving module 1910 and a relay sending module 1920. The device 1900 may include:
[0374] The relay receiving module 1910 is used to receive a first relay PDU from a previous hop node, where the first relay PDU is sent from a remote terminal to a network device.
[0375] Optionally, in the case where the relay protocol stack is located between the PDCP layer and the layer 2 protocol stack, the protocol header of the first relay PDU further includes: a radio bearer identifier, where the radio bearer identifier is an identifier of a radio bearer between the remote terminal and the network device;
[0376] In the case where the relay protocol stack is a MAC layer protocol stack, the first relay PDU further includes: a logical channel identifier.
[0377] Optionally, if the destination identifier of the first relay PDU is not empty, the relay receiving module 1910 is further configured to submit the PDCP PDU and the radio bearer identifier included in the first relay PDU to the upper layer when the destination identifier of the first relay PDU is the same as the local identifier.
[0378] Optionally, if the destination identifier of the first relay PDU is empty, the relay receiving module 1910 is also used to submit the PDCP PDU and wireless bearer identifier included in the first relay PDU to the upper layer, or submit the PDCP PDU and logical channel identifier included in the first relay PDU to the upper layer.
[0379] Optionally, the relay protocol stack further includes a relay sending module 1920, and the device 1900 further includes:
[0380] The relay sending module 1920 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;
[0381] 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.
[0382] Optionally, the protocol header of the second relay PDU further includes: a terminal identifier of the remote terminal, where the terminal identifier is a destination identifier of the second relay PDU.
[0383] Optionally, 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.
[0384] The relay method provided in the embodiment of the present application is applied to a network device, the network device includes a relay protocol stack, the relay protocol stack is located between the packet data convergence protocol PDCP layer and the layer 2 protocol stack of the Uu interface, or the relay protocol stack is a media access control MAC layer protocol stack, 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 first relay PDU is sent by the remote terminal 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 autonomously 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 mapping relationship between the wireless bearer and the remote terminal identifier, so that the routing process of transmitting the second relay PDU is more flexible.
[0385] Fig. 20 2000 is a schematic diagram of a structure of a device for generating a routing table according to an exemplary embodiment. The device 2000 may be configured in a relay terminal. The device 2000 may include:
[0386] The receiving module 2010 is used to receive a first relay protocol data unit PDU from a remote terminal, where the first relay PDU includes a terminal identifier of the remote terminal, and the first relay PDU is sent by the remote terminal to the network device;
[0387] The routing establishment module 220 is used to establish a first routing relationship based on the terminal identifier of the remote terminal and the node identifier of the previous hop node. The first routing relationship is a routing relationship when the terminal identifier is used as the destination identifier.
[0388] Optionally, the first relay PDU further includes a network device identifier, which is a destination identifier of the first relay PDU and is used to indicate a network device to which the first relay PDU needs to be transmitted.
[0389] Optionally, the first relay PDU further includes a radio bearer identifier or a logical channel identifier, where the radio bearer identifier is an identifier of a radio bearer between the remote terminal and the network device.
[0390] Optionally, the first relay PDU further includes indication information, where the indication information is used to indicate a cell group where a Packet Data Convergence Protocol PDCP entity of a radio bearer between the relay terminal and the network device is located.
[0391] Optionally, the network device identifier further includes a cell group identifier, and the cell group identifier is used to indicate a cell group where a PDCP entity of a radio bearer between the relay terminal and the network device is located.
[0392] Optionally, the cell group includes a main cell group MCG or a secondary cell group SCG.
[0393] Optionally, the next hop node is a network device, and the apparatus further includes a sending module 2030, and the sending module 2030 is used to:
[0394] When the first relay PDU includes a common control channel CCCH message, obtaining first cell radio network temporary identifier C-RNTI information allocated by the network device to itself;
[0395] The first C-RNTI information is sent to the previous hop node.
[0396] Optionally, the receiving module 2010 is further used for:
[0397] receiving second C-RNTI information from a remote terminal, where the second C-RNTI information is allocated to the remote terminal by a network device;
[0398] The terminal identifier in the first routing relationship is updated to the second C-RNTI information.
[0399] Optionally, the first relay PDU includes a switching message, and the switching message is used to trigger the relay terminal to establish a connection with a target cell, and the target cell is a cell after switching.
[0400] Optionally,
[0401] The receiving module 2010 is further configured to receive a second relay PDU from the network device, where 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;
[0402] The sending module 2030 is used 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.
[0403] Optionally, the destination identifier includes a terminal identifier; or, the destination identifier includes a broadcast identifier.
[0404] In summary, the routing table generation method provided by the present application, when receiving or sending a relay PDU, the relay terminal determines the next hop node of the relay PDU according to the protocol header of the relay PDU and the routing relationship in the routing table, and the process of transmitting the relay PDU is more flexible. The transmission route of the relay PDU can be defined according to the routing table, which also alleviates the congestion and packet loss when transmitting data packets over the wireless bearer to a certain extent, and the relay solution is more flexible and efficient. In addition, the above-mentioned routing table generation process is not only applicable to relay terminals, but also to remote terminals and network devices.
[0405] Fig.21 21 is a schematic diagram of a structure of a device for generating a routing table according to another exemplary embodiment. The device 2100 may be configured in a network device. The device 2100 may include:
[0406] The receiving module 2110 is configured to receive a first relay PDU from a remote terminal, wherein the protocol header of the first relay PDU includes a terminal identifier of the remote terminal, and the first relay PDU is a relay PDU sent by the remote terminal to the network device;
[0407] The routing establishment module 2120 is used to establish a third routing relationship, which includes a terminal identifier and a node identifier of a previous hop node of the network device. The third routing relationship is a routing relationship when the terminal identifier is used as a destination identifier.
[0408] Optionally, 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, and the first relay PDU includes a data packet of the radio bearer; or,
[0409] The first relay PDU includes a PDCP PDU and a logical channel identifier.
[0410] Optionally, the apparatus 2100 further includes:
[0411] The delivery module 2130 is configured to deliver the PDCP PDU and the radio bearer identifier to the upper layer, or deliver the PDCP PDU and the logical channel identifier to the upper layer when the destination identifier of the first relay PDU is empty.
[0412] Optionally, the apparatus 2100 further includes:
[0413] The delivery module 2130 is configured to deliver the PDCP PDU and the radio bearer identifier to an upper layer if the destination identifier of the first relay PDU is not empty and if the destination identifier of the first relay PDU is the same as the local identifier.
[0414] In summary, the routing table establishment method provided in the present application receives a first relay PDU from a remote terminal, the protocol header of the first relay PDU includes a terminal identifier of the remote terminal, and the first relay PDU is a relay PDU sent by the remote terminal to a network device. A third routing relationship is established, the third routing relationship includes a terminal identifier and a node identifier of a previous hop node of the network device, and the third routing relationship is a routing relationship when the terminal identifier is used as a destination identifier. In this way, in subsequent communication processes, the network device can determine which relay terminal the second relay PDU sent to the remote terminal should be transmitted through based on the establishment of the third routing relationship. In this process, the network device does not need to pre-configure the mapping relationship between the wireless bearer and the remote terminal identifier, so that the routing process of transmitting the first relay PDU is more flexible.
[0415] Please refer to Fig. 22 , which shows a schematic diagram of the structure of a communication device (terminal or access network device) provided by an exemplary embodiment of the present application, wherein the communication device includes: a processor 1201, a receiver 1202, a transmitter 1203, a memory 1204 and a bus 1205.
[0416] The processor 1201 includes one or more processing cores. The processor 1201 executes various functional applications and information processing by running software programs and modules.
[0417] The receiver 1202 and the transmitter 1203 may be implemented as a communication component, which may be a communication chip.
[0418] The memory 1204 is connected to the processor 1201 via a bus 1205 .
[0419] The memory 1204 may be used to store at least one instruction, and the processor 1201 may be used to execute the at least one instruction to implement the various steps performed by the terminal and the network device in the above-mentioned various method embodiments.
[0420] In addition, memory 1204 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, and volatile or non-volatile storage devices include but are not limited to: magnetic disks or optical disks, electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), static random access memory (SRAM), read-only memory (ROM), magnetic memory, flash memory, and programmable read-only memory (PROM).
[0421] The present application provides a computer-readable storage medium, in which at least one instruction is stored. The at least one instruction is loaded and executed by the processor to implement the relay method and routing table generation method provided by the above-mentioned various method embodiments.
[0422] The present application also provides a computer program product. When the computer program product runs on a computer, the computer executes the relay method and routing table generation method provided by the above-mentioned various method embodiments.
[0423] Those skilled in the art should be aware that in one or more of the above examples, the functions described in the embodiments of the present application can be implemented with hardware, software, firmware, or any combination thereof. When implemented using software, these functions can be stored in a computer-readable medium or transmitted as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media and communication media, wherein the communication media include any media that facilitates the transmission of a computer program from one place to another. The storage medium can be any available medium that a general or special-purpose computer can access.
[0424] The above description is only an optional embodiment of the present application and is not intended to limit the present application. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application shall be included in the protection scope of the present application.
Claims
1. A relay method, characterized in that: Applied to a relay terminal, the relay terminal includes a relay protocol stack, the relay protocol stack is located between a packet data convergence protocol PDCP layer and a layer 2 protocol stack, the relay protocol stack includes a relay receiving entity and a relay sending entity, and the method includes: 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 PDU includes a second relay PDU, and the protocol header of the second relay PDU includes: a terminal identifier of a remote terminal, the terminal identifier being a destination identifier of the second relay PDU; and A radio bearer identifier, where the radio bearer identifier is an identifier of a radio bearer between the remote terminal and the network device.
2. The method according to claim 1, characterized in that The relay PDU also includes a first relay PDU, and 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.
3. The method according to claim 1, characterized in that When the relay receiving entity determines that the destination identifier of the second relay PDU is the same as the local identifier, the second relay PDU is transmitted.
4. The method according to claim 2, characterized in that In the case where the relay protocol stack is located between the PDCP layer and the layer 2 protocol stack, the protocol header of the first relay PDU further includes: a radio bearer identifier, where the radio bearer identifier is an identifier of a radio bearer between the remote terminal and the network device.
5. The method according to claim 1, characterized in that In the case where the relay terminal interacts with the network device, the layer 2 protocol stack includes a layer 2 protocol stack of a Uu interface; In the case where the relay terminal interacts with another relay terminal, or in the case where the relay terminal interacts with a remote terminal, the layer 2 protocol stack includes a layer 2 protocol stack of a 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.
6. A relay method, characterized in that: Applied to a remote terminal, the remote terminal includes a relay protocol stack, the relay protocol stack is located between a packet data convergence protocol PDCP layer and a layer 2 protocol stack of a PC5 interface, the relay protocol stack includes a relay receiving entity, and the method includes: The relay receiving entity is used to receive a second relay PDU from a previous hop node, wherein 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 includes: a terminal identifier of the remote terminal, the terminal identifier is a destination identifier of the second relay PDU; and a radio bearer identifier, the radio bearer identifier is an identifier of a radio bearer between the remote terminal and the network device; The relay receiving entity is further configured to deliver the radio bearer identifier and the PDCP PDU in the second relay PDU to an 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.
7. The method according to claim 6, characterized in that The relay protocol stack also includes a relay sending entity, and the method further includes: 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 sent by the PDCP layer, and send the first relay PDU to a next hop node; The first relay PDU is a relay PDU sent by the remote terminal to the network device.
8. The method according to claim 7, characterized in that 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.
9. The method according to claim 8, characterized in that The protocol header of the first relay PDU also includes: a network device identifier of the network device; The network device identifier is a destination identifier of the first relay PDU.
10. A relay method, characterized in that: Applied to a network device, the network device includes a relay protocol stack, the relay protocol stack is located between a packet data convergence protocol PDCP layer and a layer 2 protocol stack of a Uu interface, the relay protocol stack includes a relay sending entity, and the method 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 send the second relay PDU to a next hop node; wherein the second relay PDU is a relay PDU sent by the network device to a remote terminal, or the second relay PDU is broadcast by the network device; the protocol header of the second relay PDU includes: a terminal identifier of the remote terminal, the terminal identifier is a destination identifier of the second relay PDU; and a wireless bearer identifier, the wireless bearer identifier is an identifier of a wireless bearer between the remote terminal and the network device.
11. The method according to claim 10, characterized in that The relay protocol stack further includes a relay receiving entity, and the method further includes: The relay receiving entity is used to receive a first relay PDU from a previous hop node, where the first relay PDU is sent from the remote terminal to the network device; The protocol header of the first relay PDU also includes: a radio bearer identifier, where the radio bearer identifier is an identifier of a radio bearer between the remote terminal and the network device.
12. The method according to claim 11, characterized in that If the destination identifier of the first relay PDU is not empty, the relay receiving entity is further used to submit the PDCP PDU and the radio bearer identifier included in the first relay PDU to an upper layer when the destination identifier of the first relay PDU is the same as the local identifier.
13. The method according to claim 10, characterized in that The second relay PDU also includes a broadcast identifier, and the broadcast identifier is used to indicate that the second relay PDU includes broadcast data or broadcast signaling.
14. A relay terminal, characterized in that: The device comprises a processor and a memory, wherein the memory stores at least one instruction, and the at least one instruction is used to be executed by the processor to implement the steps of any one of the methods of claims 1-5.
15. A remote terminal, characterized in that: The device comprises a processor and a memory, wherein the memory stores at least one instruction, and the at least one instruction is used to be executed by the processor to implement the steps of any one of the methods of claims 6-9.
16. A network device, characterized in that: The device comprises a processor and a memory, wherein the memory stores at least one instruction, and the at least one instruction is used to be executed by the processor to implement the steps of any one of the methods of claims 10-13.
Citation Information
Patent Citations
Layer 2 relay protocols and mobility relay method
CN108029148A
