WO2019137505A1 - 一种数据传输方法及装置 - Google Patents

一种数据传输方法及装置 Download PDF

Info

Publication number
WO2019137505A1
WO2019137505A1 PCT/CN2019/071481 CN2019071481W WO2019137505A1 WO 2019137505 A1 WO2019137505 A1 WO 2019137505A1 CN 2019071481 W CN2019071481 W CN 2019071481W WO 2019137505 A1 WO2019137505 A1 WO 2019137505A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
message
communication device
terminal
indication information
Prior art date
Application number
PCT/CN2019/071481
Other languages
English (en)
French (fr)
Inventor
王瑞
戴明增
李铕
曾清海
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP19738167.6A priority Critical patent/EP3731484B1/en
Publication of WO2019137505A1 publication Critical patent/WO2019137505A1/zh
Priority to US16/925,614 priority patent/US11463937B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/02—Communication route or path selection, e.g. power-based or shortest path routing
    • H04W40/22—Communication route or path selection, e.g. power-based or shortest path routing using selective relaying for reaching a BTS [Base Transceiver Station] or an access point
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/06—Notations for structuring of protocol data, e.g. abstract syntax notation one [ASN.1]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
    • H04L69/321—Interlayer communication protocols or service data unit [SDU] definitions; Interfaces between layers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
    • H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
    • H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
    • H04L69/324—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the data link layer [OSI layer 2], e.g. HDLC
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
    • H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
    • H04L69/326—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the transport layer [OSI layer 4]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/10—Scheduling measurement reports ; Arrangements for measurement reports

Definitions

  • the embodiments of the present invention relate to the field of communications technologies, and in particular, to a data transmission method and apparatus.
  • the relay node has the characteristics of wireless self-return and flexible placement.
  • a User Equipment (UE) peer-to-peer Packet Data Convergence Protocol (PDCP) layer can be placed in the host base station system, and the UE peer-to-peer wireless link control
  • the Layer Link Protocol (RLC) layer is placed in the RN.
  • PHY physical layer
  • MAC media access control
  • RLC Layer 2
  • L2 Layer 2
  • the embodiment of the present application provides a data transmission method and apparatus, which enable an RN to quickly identify and process data received by the RN.
  • a data transmission method is provided, which is applied to a chip in a first communication device or a first communication device, the first communication device being an intermediate forwarding node, a serving node of the terminal, a donor base station or a donor base station Distributed unit DU in the system.
  • the data transmission method provided by the embodiment of the present application is: the first communication device acquires the first data, and sends a first message including the first data and the type identifier to the second communication device, where the type identifier is used to indicate the first The type of data.
  • the type of the first data includes at least one of user plane data, a status report, a control plane message, and a radio resource control RRC message of the terminal.
  • the second communication device When the first communication device is an intermediate forwarding node, the second communication device is a previous hop device or a next hop device of the intermediate forwarding node.
  • the second communication device When the first communication device is the service node of the terminal, the second communication device is the last hop device of the service node of the terminal.
  • the first communication device is a donor base station or a DU, the second communication device is a next hop device of the first communication device.
  • the first message includes the first indication information and the global number SN of the user plane data; the first indication information is used to indicate the data radio bearer DRB of the terminal to which the user plane data belongs.
  • the first data is a status report, the first data includes a global SN of the user plane data carried by the DRB of the terminal, the first data is used to indicate the transmission status of the DRB data packet of the third communication device, and the third communication device is the terminal and the middle. Forward the node or the service node of the terminal.
  • the first message includes at least one of the transport layer protocol layer information of the first interface, the second indication information, the identifier of the terminal at the first interface, and the third indication information; a logical communication interface between the communication device and the second communication device, the transport layer protocol layer information of the first interface includes a protocol IP address interconnected between the networks of the first communication device, an IP address of the second communication device, and a host base station Or the IP address of the DU, the port number of the first communication device, the port number of the second communication device, the port number of the host base station or the DU, the flow identifier of the flow control transport protocol SCTP, and at least one of the load protocol identifier PPI of the SCTP,
  • the second indication information is used to indicate the first communication device
  • the third indication information is used to indicate the first interface
  • the first message includes the fourth indication information and the identifier of the serving node of the terminal, where the fourth indication information is used to indicate the terminal.
  • the data transmission method provided by the embodiment of the present application is transmitted in a unified message format, so that the time of each node in the multi-hop relay network processing the message having the format can be effectively reduced.
  • the first message sent by the first communications device to the second communications device includes the type identifier. Therefore, after acquiring the first message, the second communications device in the embodiment of the present application may directly determine the first identifier according to the type identifier.
  • the type of the data, and the first message is processed by the method corresponding to the type of the first data, further improving the processing efficiency of each node in the multi-hop relay network.
  • the first indication information is a Tunnel Endpoint Identifier (TEID), an Internet Protocol (IP) address, a destination IP address, a source port number, a destination port number, and a terminal identifier.
  • TEID Tunnel Endpoint Identifier
  • IP Internet Protocol
  • DRB Data Radio Bearer
  • the second indication information is used to indicate the first communication device.
  • the second indication information may be a UE identifier (for example, C-RNTI, S-TMSI, GUTI, etc.) when the RN is used as the UE, or when the RN is used as the UE.
  • the F1-like interface identifier (for example, the UE F1AP ID, or the UE F1AP-like ID) assigned by the previous hop may also be the RN ID after the RN is used as the UE, and then converted from the UE mode to the RN mode.
  • the second indication information may have the same format as the DU identifier.
  • the second indication information may be a global identifier, which is composed of an RN local identifier and an RN hop count.
  • the RN local identifier may be allocated to a previous hop node of the RN (for example, a RN or a DU in a host base station system).
  • the third indication information is used to indicate an F1-like interface to distinguish logical F1-like connections of different RNs.
  • the fourth indication information is used to indicate the terminal.
  • the fourth indication information may be any one of the following information or a combination of any one of the following: a F1-like interface UE ID (UE F1AP-like ID), a C-RNTI, a cell ID, and a context identifier (Context) ID) and so on.
  • the fourth indication information is a combination of the terminal identifier and the RN identifier.
  • the first data when the first data is a status report, the first data further includes fifth indication information, where the fifth indication information is used to indicate a DRB of the terminal.
  • the fifth indication information is a TEID, a source IP address, a destination IP address, a source port number, a destination port number, a terminal identifier, and a DRB identifier.
  • the foregoing first indication information may be the same as the foregoing fifth indication information, or may be different, and is not specifically limited in this embodiment of the present application.
  • the first data specifically includes each DRB of the at least one DRB of the third communications device.
  • the fifth indication information carried.
  • the first message further includes at least one of a target identifier and a sixth indication information, where the target identifier is used to indicate a serving node of the terminal, and the sixth indication information is used. Indicate the terminal.
  • the second communication device may determine the destination device of the first message to perform corresponding processing/forwarding.
  • the target identifier may be an identifier of a service node of the terminal or an IP address of a service node of the terminal.
  • the sixth indication information may be any one of the following information or a combination of any one of the following: a F1-like interface UE ID (UE F1AP-like ID), a C-RNTI, a cell ID, and a context identifier (Context ID) )Wait.
  • UE F1AP-like ID UE F1AP-like ID
  • C-RNTI C-RNTI
  • Cell ID cell ID
  • Context ID context identifier
  • the first communications device obtains The method of the first data is: the first communication device receives a second message including the second data, where the second data includes seventh indication information, where the seventh indication information is used to indicate the DRB of the terminal or the terminal; The second data is obtained in the second message, and the seventh indication information is replaced with the identifier of the terminal at the first interface or the fourth indication information, and the first data is generated.
  • the seventh indication information may be any one of the following information or a combination of any one of the following: a F1-like interface UE ID (UE F1AP-like ID), a C-RNTI, a cell ID, and a context identifier (Context ID) )Wait.
  • UE F1AP-like ID UE F1AP-like ID
  • C-RNTI C-RNTI
  • Cell ID cell ID
  • Context ID context identifier
  • the seventh indication information in the embodiment of the present application is the same as the identifier of the terminal on the first interface, and the seventh indication information and the fourth indication information are identifiers of the terminal on different interfaces.
  • the first communications device After acquiring the second data, the first communications device generates the first data by replacing the identifier used to represent the terminal, and then sends the first data to the second communications device.
  • the second message is sent by the next hop device of the first communication device. If the second communication device is the next hop device of the first communication device, the second message is sent by the last hop device of the first communication device.
  • the first communications device after acquiring the first data, further compresses the sub information in the first data according to the first preset compression algorithm.
  • the sub-information includes at least one of an IP header, an SCTP common header, and information other than the target information in the SCTP data block, where the target information is at least one of user data, a flow identifier, and a PPI; or the sub-information includes an IP header.
  • the first communication device sends the first message including the compressed first data to the second communication device.
  • the first communications device After acquiring the first data, the first communications device compresses the first data or the partial information in the first data, effectively reducing the resources occupied by the first message, and reducing the transmission overhead of the air interface resource.
  • the method for the first communications device to obtain the first data is: the first communications device receives the fourth communications device The third message is sent, the third message includes the second data; the first communications device obtains the second data from the third message, and decompresses the second data according to the second preset compression algorithm to obtain the first data.
  • the fourth communication device is the next hop device of the first communication device; if the second communication device is the next hop device of the first communication device, The fourth communication device is the last hop device of the first communication device.
  • the first communication device further receives a fourth message that is sent by the second communication device and includes the third data; the first communication device is first solved according to the third preset compression algorithm. The third data is compressed, and the decompressed third data is sent to the terminal.
  • the first communication device further receives a fifth message that is sent by the second communication device and includes the fourth data.
  • the first communication device decompresses the fourth data according to the fourth preset compression algorithm. And transmitting the decompressed fourth data to the centralized unit CU in the host base station system.
  • the method for the first communication device to acquire the first data is: the first communication device receives a sixth message that is sent by the CU and includes the fifth data; the first communication device is configured from the sixth message. Obtaining the fifth data, and decompressing the fifth data according to the fifth preset compression algorithm to obtain the first data.
  • the first communication device when the first communication device is a different device, in the corresponding data transmission process (uplink data transmission/downlink data transmission), the first communication device also performs decompression processing.
  • the first communications device after acquiring the first data, further processes the first data according to the first preset key and the first preset target algorithm.
  • the first preset target algorithm includes at least one of a preset encryption algorithm and a first preset integrity protection algorithm.
  • the first communication device sends the first message including the processed first data to the second communication device.
  • the first preset target algorithm includes at least one of a preset encryption algorithm and a first preset integrity protection algorithm, and the first communication device processes the first data according to the first preset key and the first preset target algorithm.
  • the first communication device is substantially configured to perform security protection processing on the first data. In this way, the security and integrity of the first data can be effectively guaranteed.
  • the method for the first communications device to obtain the first data is: the first communications device receives the fifth communications And sending, by the device, a seventh message that includes the sixth data; the first communications device acquires the sixth data from the seventh message, and processes the sixth data according to the second preset key and the second preset target algorithm, to obtain the first One data.
  • the second preset target algorithm includes at least one of a first preset decryption algorithm and a second preset integrity protection algorithm.
  • the fifth communication device is the next hop device of the first communication device; if the second communication device is the next hop device of the first communication device, The fifth communication device is the last hop device of the first communication device.
  • the first communication device further receives an eighth message that is sent by the second communication device and includes the seventh data; the first communication device obtains the seventh data from the eighth message, and And processing the seventh data according to the third preset key and the third preset target algorithm, and further sending the processed seventh data to the terminal.
  • the third preset target algorithm includes at least one of a second preset decryption algorithm and a third preset integrity protection algorithm.
  • the first communication device further receives a ninth message including the eighth data sent by the second communication device; the first communication device acquires the eighth data from the ninth message, and according to the fourth pre
  • the secret key and the fourth preset target algorithm are processed to process the eighth data, and then the processed eighth data is sent to the centralized unit CU of the host base station system.
  • the fourth preset target algorithm includes at least one of a third preset decryption algorithm and a fourth preset integrity protection algorithm.
  • the first communication device when the first communication device is a different device, in the corresponding data transmission process (uplink data transmission/downlink data transmission), the first communication device also performs decryption and/or integrity protection processing.
  • a data transmission apparatus is provided, where the data transmission apparatus is a chip in a first communication device or a first communication device, and the first communication device is an intermediate forwarding node, a service node of the terminal, a host base station, or a host base station system.
  • Distributed unit DU Specifically, the data transmission device includes an acquisition unit and a transmission unit.
  • the obtaining unit is configured to acquire the first data.
  • the sending unit is configured to send a first message to the second communications device, where the first message includes the first data and the type identifier that are obtained by the acquiring unit, and the type identifier is used to indicate the type of the first data, where the type of the first data includes At least one of user plane data, status report, control plane message, and radio resource control RRC message of the terminal.
  • the first communication device is an intermediate forwarding node
  • the second communication device is a previous hop device or a next hop device of the intermediate forwarding node.
  • the second communication device is the last hop device of the service node of the terminal; when the first communication device is the host base station or the DU, the second communication device is under the first communication device One hop device.
  • the first data is the user plane data
  • the first message includes the first indication information and the global number SN of the user plane data; the first indication information is used to indicate the data radio bearer DRB of the terminal to which the user plane data belongs.
  • the first data is a status report, the first data includes a global SN of the user plane data carried by the DRB of the terminal, the first data is used to indicate the transmission status of the DRB data packet of the third communication device, and the third communication device is the terminal and the middle.
  • the first message includes at least one of the transport layer protocol layer information of the first interface, the second indication information, the identifier of the terminal at the first interface, and the third indication information; a logical communication interface between the communication device and the second communication device, the transport layer protocol layer information of the first interface includes a protocol IP address interconnected between the networks of the first communication device, an IP address of the second communication device, and a host base station Or the IP address of the DU, the port number of the first communication device, the port number of the second communication device, the port number of the host base station or the DU, the flow identifier of the flow control transport protocol SCTP, and at least one of the load protocol identifier PPI of the SCTP,
  • the second indication information is used to indicate the first communication device
  • the third indication information is used to indicate the first interface
  • the first message includes the fourth indication information and the identifier of the serving node of the terminal, where the fourth indication information is used to indicate the
  • the first data when the first data is a status report, the first data further includes fifth indication information, where the fifth indication information is used to indicate a DRB of the terminal.
  • the foregoing first data specifically includes each of the at least one DRB of the third communications device.
  • the fifth indication information carried by the DRB is not limited to the third communications device.
  • the first message further includes at least one of a target identifier and a sixth indication information; the target identifier is used to indicate a serving node of the terminal, and the sixth indication information is used by Instruct the terminal.
  • the data transmission apparatus when the first data is a control plane message, and the first message includes the identifier of the first interface or the fourth indication information, the data transmission apparatus further includes Receiving unit.
  • the receiving unit is configured to receive a second message that includes the second data, where the second data includes seventh indication information, where the seventh indication information is used to indicate the DRB of the terminal or the terminal.
  • the acquiring unit is further configured to acquire the second data from the second message received by the receiving unit.
  • the data transmission device in the embodiment of the present application further includes a replacement unit.
  • the replacing unit is configured to replace the seventh indication information with the identifier of the terminal at the first interface or the fourth indication information to generate the first data.
  • the data transmission apparatus further includes a compression unit.
  • the compression unit is configured to compress the sub-information in the first data according to the first preset compression algorithm after the obtaining unit acquires the first data, where the sub-information includes an IP header, an SCTP common header, and an SCTP data block.
  • the target information is at least one of user data, a flow identifier, and a PPI; or, the sub-information includes an IP header, a User Datagram Protocol UDP header, and a GTP header of the General Packet Radio Service Tunneling Protocol.
  • the sending unit is specifically configured to send, to the second communications device, the first message that includes the compressed first data.
  • the data transmission apparatus further includes a receiving unit and a decompression unit.
  • the receiving unit is configured to receive a third message sent by the fourth communications device, where the third message includes the second data.
  • the acquiring unit is further configured to acquire the second data from the third message received by the receiving unit.
  • the decompression unit is configured to decompress the second data according to the second preset compression algorithm to obtain the first data.
  • the fourth communication device is the next hop device of the first communication device; if the second communication device is the next hop device of the first communication device, The fourth communication device is the last hop device of the first communication device.
  • the receiving unit is configured to receive a fourth message sent by the second communications device, where the fourth message includes the third data.
  • the decompression unit is configured to decompress the third data according to the third preset compression algorithm.
  • the sending unit is specifically configured to send, by the terminal, the decompressed third data.
  • the receiving unit is configured to receive a fifth message sent by the second communications device, where the fifth message includes fourth data.
  • the decompression unit is configured to decompress the fourth data according to the fourth preset compression algorithm.
  • the sending unit is specifically configured to send the decompressed fourth data to the centralized unit CU in the host base station system;
  • the receiving unit is configured to receive a sixth message sent by the CU, and the sixth message includes the fifth data.
  • the obtaining unit is further configured to acquire the fifth data from the sixth message.
  • the decompression unit is configured to decompress the fifth data according to the fifth preset compression algorithm to obtain the first data.
  • the data transmission apparatus in the embodiment of the present application further includes a security protection unit.
  • the security protection unit is configured to process the first data according to the first preset key and the first preset target algorithm after the acquiring unit acquires the first data, where the first preset target algorithm includes a preset encryption algorithm and a first At least one of a preset integrity protection algorithm.
  • the sending unit is specifically configured to send, to the second communications device, the first message that includes the processed first data.
  • the data transmission apparatus in the embodiment of the present application further includes a receiving unit and a security processing unit.
  • the receiving unit is configured to receive a seventh message sent by the fifth communications device, where the seventh message includes the sixth data.
  • the acquiring unit is further configured to acquire the sixth data from the seventh message received by the receiving unit.
  • the security processing unit is configured to process the sixth data acquired by the acquiring unit according to the second preset key and the second preset target algorithm to obtain the first data.
  • the second preset target algorithm includes at least one of a first preset decryption algorithm and a second preset integrity protection algorithm.
  • the fifth communication device is the next hop device of the first communication device; if the second communication device is the next hop device of the first communication device, The fifth communication device is the last hop device of the first communication device.
  • the receiving unit is configured to receive an eighth message sent by the second communications device, where the eighth message includes the seventh data.
  • the obtaining unit is further configured to acquire the seventh data from the eighth message received by the receiving unit.
  • the security processing unit is configured to process the seventh data acquired by the acquiring unit according to the third preset key and the third preset target algorithm.
  • the sending unit is specifically configured to send the processed seventh data to the terminal, where the third preset target algorithm includes at least one of a second preset decryption algorithm and a third preset integrity protection algorithm.
  • the receiving unit is configured to receive a ninth message sent by the second communications device, where the ninth message includes the eighth data.
  • the obtaining unit is further configured to acquire the eighth data from the ninth message.
  • the security processing unit is configured to process the eighth data according to the fourth preset key and the fourth preset target algorithm.
  • the sending unit is specifically configured to send the processed eighth data to the centralized unit CU of the host base station system.
  • the fourth preset target algorithm includes at least one of a third preset decryption algorithm and a fourth preset integrity protection algorithm.
  • a data transmission apparatus comprising: one or more processors, a memory, and a communication interface. Wherein the memory and communication interface are coupled to one or more processors; the data transmission device is in communication with other devices via a communication interface, the memory is for storing computer program code, and the computer program code includes instructions when one or more processors execute the instructions.
  • the data transmission apparatus performs the data transmission method as described in the first aspect above and its various possible implementations.
  • a computer readable storage medium having stored therein instructions; when executed on a data transmission device, causing the data transmission device to perform the first aspect as described above and various possibilities thereof The data transmission method described in the implementation manner.
  • a computer program product comprising instructions which, when run on a data transmission device, cause the data transmission device to perform the data transmission method as described in the first aspect above and its various possible implementations.
  • the names of the above data transmission devices are not limited to the devices or the functional modules themselves. In actual implementation, these devices or functional modules may appear under other names. As long as the functions of the respective devices or functional modules are similar to the present application, they are within the scope of the claims and their equivalents.
  • a data transmission method is provided, which is applied to a chip in a host base station or a host base station.
  • the data transmission method is: after receiving the first message including the first data and the type identifier sent by the first communication device, determining the type of the first data according to the type identifier, and processing the first data according to the type of the first data.
  • the above type identification is used to indicate the type of the first data.
  • the type of the first data includes at least one of user plane data, a status report, a control plane message, and a radio resource control RRC message of the terminal.
  • the first message includes the first indication information and the global number SN of the user plane data; the first indication information is used to indicate the data radio bearer DRB of the terminal to which the user plane data belongs.
  • the first data is a status report, the first data includes a global SN of the user plane data carried by the DRB of the terminal, the first data is used to indicate the transmission status of the DRB data packet of the third communication device, and the third communication device is the terminal and the middle. Forward the node or the service node of the terminal.
  • the first message includes at least one of the transport layer protocol layer information of the first interface, the second indication information, the identifier of the terminal at the first interface, and the third indication information; a logical communication interface between the communication device and the second communication device, the transport layer protocol layer information of the first interface includes a protocol IP address interconnected between the networks of the first communication device, an IP address of the second communication device, and a host base station Or the IP address of the DU, the port number of the first communication device, the port number of the second communication device, the port number of the host base station or the DU, the flow identifier of the flow control transport protocol SCTP, and at least one of the load protocol identifier PPI of the SCTP,
  • the second indication information is used to indicate the first communication device
  • the third indication information is used to indicate the first interface
  • the first message includes the fourth indication information and the identifier of the serving node of the terminal, where the fourth indication information is used to indicate the terminal.
  • the data transmission method provided by the embodiment of the present application is transmitted in a unified message format, so that the time for the host base station to process the message with the format can be effectively reduced.
  • the first message sent by the first communication device to the host base station includes the type identifier. Therefore, after obtaining the first message, the host base station in the embodiment of the present application may directly determine the type of the first data according to the type identifier. Further processing the first message by using a method corresponding to the type of the first data further improves the processing efficiency of the host base station.
  • the first indication information is a TEID, a source IP address, a destination IP address, a source port number, a target port number, a terminal identifier, and a DRB identifier.
  • the second indication information is used to indicate the first communication device.
  • the second indication information may be a UE identifier (for example, C-RNTI, S-TMSI, GUTI, etc.) when the RN is used as the UE, or when the RN is used as the UE.
  • the F1-like interface identifier (for example, the UE F1AP ID, or the UE F1AP-like ID) assigned by the previous hop may also be the RN ID after the RN is used as the UE, and then converted from the UE mode to the RN mode.
  • the second indication information may have the same format as the DU identifier.
  • the second indication information may be a global identifier, which is composed of an RN local identifier and an RN hop count.
  • the RN local identifier may be allocated to a previous hop node of the RN (for example, a RN or a DU in a host base station system).
  • the third indication information is used to indicate an F1-like interface to distinguish logical F1-like connections of different RNs.
  • the fourth indication information is used to indicate the terminal.
  • the fourth indication information may be any one of the following information or a combination of any one of the following: a F1-like interface UE ID (UE F1AP-like ID), a C-RNTI, a cell ID, and a context identifier (Context) ID) and so on.
  • the fourth indication information is a combination of the terminal identifier and the RN identifier.
  • the first data when the first data is a status report, the first data further includes fifth indication information, where the fifth indication information is used to indicate a DRB of the terminal.
  • the fifth indication information is a TEID, a source IP address, a destination IP address, a source port number, a destination port number, a terminal identifier, and a DRB identifier.
  • the foregoing first indication information may be the same as the foregoing fifth indication information, or may be different, and is not specifically limited in this embodiment of the present application.
  • the first data specifically includes each DRB of the at least one DRB of the second communications device.
  • the fifth indication information carried.
  • the method for processing the first data by the host base station according to the type of the first data is: the host base station according to the first data, The DRB data packet of the second communication device that is not successfully received indicated by the first data is transmitted to the second communication device.
  • the host base station before processing the first data according to the type of the first data, the host base station further receives the sixth indication information sent by the first communications device or the third communications device. And the sixth indication information is used to indicate that the DRB data packet of the second communication device that is not successfully received by the first data indication is sent by the third communications device to the second communications device.
  • a data transmission apparatus being a chip in a host base station or a host base station.
  • the data transmission device includes a receiving unit and a processing unit.
  • the receiving unit is configured to receive the first message sent by the first communications device, where the first message includes the first data and the type identifier, the type identifier is used to indicate the type of the first data, and the type of the first data includes the user plane data and the status. At least one of a report, a control plane message, and a radio resource control RRC message of the terminal.
  • the processing unit is configured to determine a type of the first data according to the type identifier in the first message received by the receiving unit, and process the first data according to the type of the first data.
  • the first message includes the first indication information and the global number SN of the user plane data; the first indication information is used to indicate the data radio bearer DRB of the terminal to which the user plane data belongs.
  • the first data is a status report, the first data includes a global SN of the user plane data carried by the DRB of the terminal, the first data is used to indicate the transmission status of the DRB data packet of the second communication device, and the second communication device is the terminal, the middle Forward the node or the service node of the terminal.
  • the first data is a control plane message
  • the first message includes at least one of the transport layer protocol layer information of the first interface, the second indication information, the identifier of the terminal at the first interface, and the third indication information
  • the first interface is a host a logical communication interface between the base station and the first communication device
  • the transport layer protocol layer information of the first interface includes a protocol IP address interconnected between the networks of the first communication device, an IP address of the host base station, and a port of the first communication device At least one of a port number of the host base station, a flow identifier of the flow control transmission protocol SCTP, and a load protocol identifier PPI of the SCTP
  • the second indication information is used to indicate the first communication device
  • the third indication information is used to indicate the first interface.
  • the first message includes at least one of the fourth indication information and the identifier of the cell to which the terminal belongs, where the fourth indication information is used to indicate the terminal.
  • the foregoing first data further includes fifth indication information, where the fifth indication information is used to indicate the DRB of the terminal.
  • the foregoing first data specifically includes each of the at least one DRB of the second communications device.
  • the fifth indication information carried by the DRB is not limited to the DRB.
  • the processing unit is configured to: send, according to the first data, the first data indication to the second communications device The DRB packet of the second communication device that was successfully received.
  • the receiving unit is further configured to: before the processing unit processes the first data according to the type of the first data, receive the first communications device or the third communications.
  • the sixth indication information sent by the device is used to indicate that the DRB data packet of the second communication device that is not successfully received by the first data indication is sent by the third communication device to the second communication device.
  • a data transmission apparatus comprising: one or more processors, a memory, and a communication interface. Wherein the memory and communication interface are coupled to one or more processors; the data transmission device is in communication with other devices via a communication interface, the memory is for storing computer program code, and the computer program code includes instructions when one or more processors execute the instructions.
  • the data transmission apparatus performs the data transmission method as described in the sixth aspect above and its various possible implementations.
  • a ninth aspect further provides a computer readable storage medium having stored therein instructions; when operating on the data transmission device, causing the data transmission device to perform the sixth aspect as described above and various possibilities thereof The data transmission method described in the implementation manner.
  • a computer program product comprising instructions which, when run on a data transmission device, cause the data transmission device to perform the data transmission method as described in the sixth aspect above and its various possible implementations.
  • the names of the above data transmission devices are not limited to the devices or the functional modules themselves. In actual implementation, these devices or functional modules may appear under other names. As long as the functions of the respective devices or functional modules are similar to the present application, they are within the scope of the claims and their equivalents.
  • FIG. 1 is a schematic structural diagram of a base station system composed of a CU and a DU in a 5G system;
  • FIG. 2 is a schematic structural diagram of a multi-hop relay network according to an embodiment of the present application.
  • FIG. 3 is a schematic structural diagram of a protocol stack of an LTE R10 Relay according to an embodiment of the present disclosure
  • FIG. 4 is a schematic diagram 1 of a protocol stack structure of each node in a hop-by-hop architecture according to an embodiment of the present application
  • FIG. 5 is a schematic diagram 1 of a protocol stack structure of each node in an end-to-end architecture of an RN and a DU according to an embodiment of the present disclosure
  • FIG. 6 is a schematic structural diagram of a protocol stack of each node in an end-to-end architecture of an RN and a CU according to an embodiment of the present disclosure
  • FIG. 7 is a schematic structural diagram of a communication system according to an embodiment of the present application.
  • FIG. 8 is a schematic structural diagram of hardware of a mobile phone according to an embodiment of the present disclosure.
  • FIG. 9 is a schematic structural diagram of hardware of an RN according to an embodiment of the present disclosure.
  • FIG. 10 is a schematic structural diagram of hardware of a host base station according to an embodiment of the present application.
  • FIG. 11 is a schematic structural diagram of a protocol layer of each node in a communication system according to an embodiment of the present disclosure
  • FIG. 12 is a schematic diagram 2 of a protocol stack structure of each node in a hop-by-hop architecture according to an embodiment of the present disclosure
  • FIG. 13 is a schematic diagram 2 of a protocol stack structure of each node in an end-to-end architecture of an RN and a DU according to an embodiment of the present disclosure
  • FIG. 14 is a schematic diagram 3 of a protocol stack structure of each node in a hop-by-hop architecture according to an embodiment of the present disclosure
  • FIG. 15 is a schematic diagram 4 of a protocol stack structure of each node in a hop-by-hop architecture according to an embodiment of the present disclosure
  • 16 is a schematic diagram of a format of an uncompressed SCTP data packet in an embodiment of the present application.
  • 17 is a schematic diagram 1 of a format of a first message in an embodiment of the present application.
  • FIG. 18 is a second schematic diagram of a format of a first message according to an embodiment of the present application.
  • FIG. 19 is a schematic diagram of a format of an uncompressed GTP-U data packet in an embodiment of the present application.
  • 21 is a format of a first message in the protocol stack shown in FIG. 15 in the embodiment of the present application.
  • 22 is a schematic flowchart 1 of a configuration process of an IAB function protocol layer of each node in the embodiment of the present application;
  • FIG. 23 is a second schematic diagram of a configuration process of an IAB function protocol layer of each node in the embodiment of the present application.
  • FIG. 24 is a schematic flowchart 3 of a configuration process of an IAB function protocol layer of each node in the embodiment of the present application.
  • FIG. 25 is a schematic flowchart 1 of a data transmission method according to an embodiment of the present application.
  • FIG. 26 is a second schematic flowchart of a data transmission method according to an embodiment of the present disclosure.
  • FIG. 27 is a schematic structural diagram 1 of a data transmission apparatus according to an embodiment of the present disclosure.
  • FIG. 28 is a schematic structural diagram 2 of a data transmission apparatus according to an embodiment of the present application.
  • Host base station system A base station system that provides wireless access to a relay node, and is connected to the relay node via a wireless Un interface.
  • the host base station system may be a Domin evolved Node Base Station (DeNB), or may be composed of a Centralized Unit (CU) and a Distributed Unit (DU).
  • DeNB Domin evolved Node Base Station
  • CU Centralized Unit
  • DU Distributed Unit
  • the CU is mainly used for centralized radio resource and connection management control, and has a wireless high-level protocol stack function, such as a Radio Resource Control (RRC) layer and a PDCP layer.
  • the CU can also support some core network functions to sink to the access network, called the edge computing network, which can meet the higher requirements of network delays for emerging services (such as video, online shopping, virtual/augmented reality, etc.) in future communication networks.
  • the DU has distributed user plane processing functions, and mainly has layer 2 functions with high physical layer functions and high real-time requirements.
  • the CU has an RRC layer and a PDCP layer
  • the DU has an RLC layer, a MAC layer, and a PHY layer.
  • the CU can be deployed in a centralized manner, and the deployment of the DU depends on the actual network environment.
  • DU can be distributed centrally; for traffic is sparse, station spacing is more Large areas, such as suburban counties, mountainous areas, etc., can be deployed in a distributed manner.
  • FIG. 1 is a schematic structural diagram of a base station system composed of a CU and a DU in a 5 Generation Mobile Communication Technology (5G) system.
  • 5G 5 Generation Mobile Communication Technology
  • the CU and the DU communicate through a CU-DU interface, and the interface can be used to transmit a control plane message between the CU and the DU, or an RRC message of the UE served by the base station system, or the base station system.
  • the CU-DU interface is referred to as an F1 interface, and its control plane is called F1-C, and its user plane is called F1-U.
  • the control plane message between the CU and the DU carried by the F1-C is called the F1 Application Protocol (F1AP) message.
  • F1AP F1 Application Protocol
  • the F1AP message can be divided into two parts: a common message (or Common Message, or Non UE Associated) and a UE related message (UE Associated).
  • Common messages can be used for F1 interface management, CU/DU configuration updates, and cell management.
  • the UE related message may be used to establish/manage/update/delete the UE context, quality of service (QoS) parameters of the interactive UE, protocol stack configuration, and the like.
  • the UE related message may also be used to transmit the RRC message of the UE, that is, the PDCP protocol data in the RRC message transmitted by the Signaling Radio Bearers (SRB) 1/SRB 2/SRB1S/SRB2S/SRB 3 of the UE.
  • SRB Signaling Radio Bearers
  • the Protocol Data Unit (PDU), and the RRC PDU in the RRC message transmitted by the SRB 0 are included in the F1AP message for transmission as an RRC container (Container).
  • the F1-U transmits the data of the UE.
  • the PDCP PDU of the UE is encapsulated in a General Packet Radio Service Tunneling Protocol-User Plane (GTP-U) data packet for transmission.
  • GTP-U General Packet Radio Service Tunneling Protocol-User Plane
  • the DRB of the UE can be identified by using the GTP TEID.
  • Un port The NR backhaul link is called Un port.
  • the Un port includes a wireless transmission interface in which the RN communicates with the host base station system, and a wireless transmission interface in which the RN communicates with the RN.
  • Uu interface The access link that the RN or the host base station system serves for the UE is called a Uu interface.
  • Multi-hop relay network consists of a terminal, multiple RNs, and a host base station system. Data or signaling is forwarded by multiple RNs between a source (such as a terminal or a base station system) to a sink (such as a donor base station system or terminal).
  • a source such as a terminal or a base station system
  • a sink such as a donor base station system or terminal.
  • Service node A node in the network that is directly connected to the terminal through an air interface and provides control plane messages and user plane data transmission for the terminal.
  • Intermediate forwarding node A node that provides relay transmission for other RNs and a node that provides relay transmission for terminals served by other RNs.
  • the hop count level can be used to describe the location of a certain RN in the network.
  • the RN of the RN directly communicating with the host base station system has a hop count of 1
  • the RN of the RN communicating with the host base station system via another RN has a hop count of 2, and so on.
  • the multi-hop relay network includes a host base station, a relay node 1 to a relay node 4, and terminal 1 to terminal 6.
  • the host base station directly communicates with the relay node 1 and the relay node 4.
  • the interface between the host base station and the relay node 1 is an Un1 interface
  • the interface between the host base station and the relay node 4 is an Un4 interface
  • the interface between the relay node 1 and the relay node 2 is an Un2 interface
  • the interface between the relay node 2 and the relay node 3 is an Un3 interface.
  • the terminal 1 communicates with the relay node 1 through the Uu1 interface
  • the terminal 2 communicates with the relay node 2 through the Uu2 interface
  • the terminal 3 communicates with the relay node 3 through the Uu3 interface
  • the terminal 4 communicates with the relay node 4 through the Uu4 interface
  • the terminal 5 The terminal 6 communicates with the relay node 1 through the Uu5 interface
  • the terminal 6 communicates with the relay node 4 through the Uu6 interface.
  • the hop count level of the relay node 1 and the relay node 4 is 1; the relay node 2 communicates with the host base station through the relay node 1, so The hop count level is 2; similarly, the hop count level of the relay node 5 is also 2; the relay node 3 communicates with the host node through the relay node 2 and the relay node 1, so that the hop count level is 3.
  • the relay node 1 is an intermediate forwarding node of the relay node 2
  • the relay node 1 and the relay node 2 are intermediate forwarding nodes of the relay node 3
  • the relay node 1 and the relay node 2 are terminals 3.
  • the relay node 1 is a service node of the terminal 1
  • the relay node 2 is a service node of the terminal 2
  • the relay node 3 is a service node of the terminal 3 and the terminal 5
  • the relay node 4 is a service node of the terminal 4 and the terminal 6.
  • the previous hop node is the host base station or the DU in the host base station system.
  • the intermediate forwarding node may be referred to as a next hop node of the DU in the host base station or the donor base station system.
  • each node has a complete protocol stack.
  • Figure 3 illustrates a protocol stack architecture for various nodes in a network including RNs.
  • the protocol stack architecture is divided into a protocol stack architecture of the control plane and a protocol stack architecture of the user plane.
  • a in FIG. 3 shows a control plane protocol stack of a UE, an RN, a donor base station, and a Mobility Management Entity (MME) (hereinafter referred to as MME-UE) serving the UE.
  • the control plane protocol stack of the UE includes a non-access stratum (NAS), a radio resource control (RRC) layer, a PDCP layer, an RLC layer, a MAC layer, and a PHY layer from top to bottom.
  • the control plane protocol stack that the RN communicates with the UE includes an RRC layer, a PDCP layer, an RLC layer, a MAC layer, and a PHY layer from top to bottom.
  • the control plane protocol stack that communicates with the host base station includes an S1 application protocol from top to bottom (S1 Application Protocol). , S1-AP) layer, Stream Control Transmission Protocol (SCTP) layer, Internet Protocol (IP) layer, PDCP layer, RLC layer, MAC layer, and PHY layer.
  • S1-AP S1 application protocol from top to bottom
  • SCTP Stream Control Transmission Protocol
  • IP Internet Protocol
  • PDCP layer PDCP layer
  • RLC layer Internet Protocol
  • MAC layer MAC layer
  • PHY layer PHY layer.
  • the control plane protocol stack of the host base station communicating with the RN includes an S1-AP layer, an SCTP layer, an IP layer, a PDCP layer, an RLC layer, a MAC layer, and a PHY layer from top to bottom; the protocol stack for communicating with the MME-UE is from top to bottom.
  • the S1-AP layer, the SCTP layer, the IP layer, the data link layer (which may also be referred to as an L2 layer), and the physical layer (which may also be referred to as an L1 layer) are included.
  • the protocol stack of the MME-UE includes a NAS, an S1-AP layer, an SCTP layer, an IP layer, an L2 layer, and an L1 layer from top to bottom.
  • the R10Relay control plane has a complete protocol stack.
  • the RRC message of the UE is terminated in the RN, and the RN provides the proxy (Proxy) of the S1/X2 message for the UE.
  • the S1 interface is the host base station and the core network (Core Net, CN) control plane.
  • the interface between the entities, the X2 interface can be the interface between the host base station and the RN (or RN and RN).
  • FIG. 3 shows a UE, an RN, a donor base station, and a Serving Gateway (SGW)/Public Data Network Gateway (PGW) serving the UE (referred to as SGW-UE/ in the figure).
  • SGW Serving Gateway
  • PGW Public Data Network Gateway
  • User plane protocol stack of PGW-UE includes an IP layer, a PDCP layer, an RLC layer, a MAC layer, and a PHY layer from top to bottom.
  • the user plane protocol stack that the RN communicates with the UE includes a PDCP layer, an RLC layer, a MAC layer, and a PHY layer from top to bottom.
  • the user plane protocol stack that communicates with the host base station includes a general packet radio service tunneling protocol user plane from top to bottom (General Packet Radio Service Tunneling Protocol-User Plane (GTP-U) layer, User Datagram Protocol (UDP) layer, IP layer, PDCP layer, RLC layer, MAC layer, and PHY layer.
  • GTP-U General Packet Radio Service Tunneling Protocol-User Plane
  • UDP User Datagram Protocol
  • the user protocol stack of the host base station communicating with the RN includes a GTP-U layer, a UDP layer, an IP layer, a PDCP layer, an RLC layer, a MAC layer, and a PHY layer from top to bottom, and a user plane protocol for communicating with the SGW-UE/PGW-UE
  • the stack includes a GTP-U layer, a UDP layer, an IP layer, an L2 layer, and an L1 layer from top to bottom.
  • the SGW-UE/PGW-UE includes an IP layer, a GTP-U layer, a UDP layer, an IP layer, an L2 layer, and an L1 layer from top to bottom.
  • the R10 Relay user plane also has a complete protocol stack, which can provide the data radio bearer (DRB) transmission service for the UE, and can aggregate the data of multiple UEs and forward them to the host base station through the backhaul link. .
  • DRB data radio bearer
  • the RN on the control plane, the RN generates a UE-related S1 message for the UE.
  • the RN encapsulates the GTP format data packet of the S1 interface.
  • the host base station provides a proxy service for the message or data of the above S1 interface, and sends the above message or data to the corresponding core network node.
  • the GTP tunnel can be distinguished, for example, TEID. If the control plane S1AP message of multiple UEs is carried in the DRB of the same Un interface, the UE S1AP ID in the S1AP message can be distinguished. If a DRB carries both user plane data and S1AP messages, it can be distinguished by an IP address, that is, a different IP address is assigned to the GTP-U tunnel of the user plane and the SCTP connection of the control plane.
  • the host base station After receiving the S1AP message sent by the RN, the host base station replaces the IP address with the IP address of the MME-UE, and replaces the UE S1AP ID of the Un interface in the message with the host base station/MME allocated for the UE by the S1-MME. ID.
  • the host base station After receiving the GTP-U data packet sent by the RN, the host base station replaces the IP address thereof with the IP address of the SGW-UE, and replaces the uplink/downlink TEID with the corresponding SGW/homing base station as the evolved group of the UE.
  • EPS-bearer Evolved Packet System bearer
  • the RN Because the RN has the characteristics of wireless self-backhaul and flexible deployment, it can save the cost of trenching and embedding when the traditional base station is placed on the wired backhaul link. It is suitable for the initial deployment of the 5G network and the network of the evolved communication system. However, the R10 RN can only support relatively simple placement in the scenario, such as single-hop single-homing, does not support multi-hop relay networks, and cannot meet the needs of future network diversification.
  • the Uu interface and the Un interface have complete control planes and user plane protocol stacks.
  • the uplink and downlink data packets of the UE need to be processed by the PDCP layer of the RN, which increases the processing delay.
  • the PDCP layer of the UE peer can be placed in the host base station system, and the RLC layer of the UE peer is placed in the RN.
  • the RN can only complete the processing of the PHY, MAC, and RLC layers.
  • the protocol architecture of the RN is referred to as an L2 architecture.
  • the above-mentioned configuration of placing the peer RLC layer of the UE in the RN, the PDCP layer of the UE peering in the host base station system is similar to the above CU-DU architecture (refer to FIG. 1 above), and the host base station system can be regarded as a CU, RN. Can be regarded as DU. Different from the above CU-DU architecture, the host base station system communicates with the RN through a wireless interface, and in the multi-hop relay network, the host base station system directly communicates with the one-hop RN, and the host base station system and the hop count are greater than one.
  • the RN cannot communicate directly, and needs to transit through the RN located between the two (it should be noted that the location relationship here refers to the location relationship in the communication connection, not the geographical relationship). Therefore, the design of the protocol stack of the multi-hop L2 Relay network can be designed by referring to the interface protocol of the CU-DU. For example, the signaling interaction between the RN and the host base station system based on the F1AP procedure and the cell, and the G1-U based GTP-U The protocol stack architecture encapsulates and sends user data.
  • the RN may perform signaling interaction with the host base station system through the RRC message of the RN, and may be used for managing the context of the UE, transmitting configuration information to the UE, etc., but the functions and procedures of the existing RRC do not support the foregoing RN.
  • the interaction between the UE and the host base station is performed. Therefore, a new RRC procedure and a cell need to be defined, and standardization of the multi-hop relay network is added.
  • the design of the air interface between the RN-homing base station system based on the F1 interface can be Minimize the introduction of new signaling procedures and cells.
  • the end-to-end architecture includes an end-to-end architecture of RNs and DUs, and an end-to-end architecture of RNs and CUs.
  • the embodiment of the present application is described by taking the multi-hop relay network 1 as an example.
  • the multi-hop relay network 1 includes a CU, a DU, an RN 1, an RN 2, and a UE.
  • the interface between the RN 1 and the DU is Un1
  • the interface between the RN 1 and the RN 2 is Un2
  • the interface between the RN 2 and the UE is Un2
  • multi-hop relay network 1 is merely an example of a multi-hop relay network, and is not a limitation on a multi-hop relay network.
  • the multi-hop relay network in this embodiment of the present application may include multiple RNs.
  • a in FIG. 4 shows the control plane protocol stack of each node in the multi-hop relay network 1 in the architecture
  • B in FIG. 4 shows each of the multi-hop relay networks 1 in the architecture.
  • Adapt. in FIG. 4 represents an adaptation layer.
  • the F1AP layer of the RN in FIG. 4 is similar to the S1-AP layer of the RN in FIG. 3.
  • the F1AP layer of the DU and the CU in FIG. 4 is similar to the S1-AP layer of the base station in FIG.
  • the peer RRC layer and PDCP layer of the UE are placed on the CU, and the peer RLC layer of the UE is placed on the RN 2.
  • the RN 2 During the uplink transmission, the RN 2 generates a UE-related F1AP message, and transmits its generated F1AP message to the RN 1 through the Un2 interface. Specifically, for the uplink RRC message of the UE, after receiving the RRC message of the UE through the Uu interface, the RN2 processes the RRC message to the RLC layer, and carries the RLC SDU or the PDCP PDU in the F1AP message and sends the message to the RN 1. After receiving the F1AP message, the RN 1 processes the F1AP message received by the Un2 interface.
  • the UE F1AP ID and/or TEID related to the UE in the F1AP message body are replaced with the identifier corresponding to the UE on the Un1 interface.
  • the other content remains unchanged.
  • the processed F1AP message is sent to the DU on the Un 1 interface.
  • the DU processes the received F1AP message (for example, replacing the UE F1AP ID and/or TEID related to the UE in the F1AP message body with the identifier corresponding to the UE on the F1 interface, and the other content remains unchanged), and
  • the processed F1AP message is further carried on the F1 interface and sent to the CU.
  • the CU processes the received F1AP message (for example, extracts the RRC message therein and performs RRC layer processing.
  • the CU performs PDCP processing before performing RRC layer processing).
  • the CU During the downlink transmission, the CU generates a UE-related F1AP message and sends it to the DU through the F1 interface.
  • the DU processes the received F1AP message (for example, the UE F1AP ID and/or TEID on the F1 interface related to the UE in the F1AP message body is replaced with the identifier corresponding to the UE on the Un1 interface, and the other content remains unchanged. ), and the processed F1AP message is sent to the RN 1 on the Un1 interface.
  • the CU is carried in the F1AP message and sent to the DU.
  • the RN 1 processes the received F1AP message (for example, replacing the UE F1AP ID and/or TEID on the Un1 related to the UE in the F1AP message body with the UE on the Un2 interface.
  • the corresponding identifier remains unchanged.
  • the processed F1AP message is sent to the RN2 on the Un2 port.
  • the RN2 processes the received F1AP message, for example, extracts the downlink RRC message, and processes the extracted downlink RRC message through the RLC layer that is peered with the UE, and then sends the message to the UE through the Uu interface.
  • the peer PDCP layer of the UE is placed on the CU and the peer RLC layer of the UE is placed on the RN2.
  • the RN 2 receives the data of the UE through the Uu interface, for example, the data carried by the UE DRB, processes the received data to the RLC layer, and encapsulates the RLC SDU/PDCP PDCU into GTP-U data.
  • the Un2 interface is sent to RN 1.
  • the RN 1 processes the received GTP-U data (for example, the TEID corresponding to the UE on the Un2 interface is replaced with the TEID corresponding to the UE on the Un1 interface, and the content of the UE data remains unchanged), and the processed content is processed.
  • the GTP-U data bearer is sent to the DU on the Un1 interface.
  • the DU processes the received GTP-U data (for example, replacing the GTP TEID with the corresponding TEID on the F1 interface, the content of the UE data remains unchanged), and further carries the processed GTP-U data in the Sent to the CU on the F1 interface.
  • the CU processes the received GTP-U data (for example, extracts data of the UE, and the data of the UE may be a PDCP PDU/RLC SDU), and performs PDCP layer processing.
  • the CU encapsulates the UE's data (eg, DRB PDCP PDU) into GTP-U data, and sends the GTP-U data to the DU through the F1 interface.
  • the DU processes the received GTP-U data (for example, the TEID corresponding to the UE on the F1 interface is replaced with the TEID corresponding to the UE on the Un1 interface, the content of the UE data remains unchanged), and the processed GTP is changed.
  • the -U data bearer is sent to the RN 1 on the Un1 interface.
  • the RN 1 processes the received GTP-U data (for example, the TEID corresponding to the UE on the Un1 interface is replaced with the TEID corresponding to the UE on the Un2 interface, and the content of the UE data remains unchanged), and the processed data is processed.
  • the GTP-U data bearer is sent to the RN 2 on the Un2 interface.
  • the RN 2 processes the received GTP-U data, for example, extracts the PDCP PDU/RLC SDU, and processes it through the RLC layer that is peered with the UE, and sends it to the UE through the Uu interface.
  • each node in the data transmission path can perceive the information of each UE, maintain the context of the UE, and manage the UE. And data statistics to guarantee the QoS of the UE.
  • the UE identifier (for example, the UE F1AP ID/TEID) is maintained for each of the transmission channels, for example, the UE identifier of the Un2 interface is allocated to the RN 2 or the RN 1, and the UE identifier of the Un1 interface is allocated by the RN 1 or the DU.
  • the UE identity on the F1 interface is assigned to the DU or CU.
  • the intermediate forwarding node of the two-stage transmission channel needs to replace the two-stage UE identifier (optional, which determines/maintains the mapping relationship between the two-stage UE identifiers).
  • each node on the transmission path needs to parse and encapsulate the F1AP message/GTP-U data, which reduces the forwarding speed of the UE signaling/data.
  • a in FIG. 5 shows the control plane protocol stack of each node in the multi-hop relay network 1 in the architecture
  • B in FIG. 5 shows the multi-hop in the architecture. Following the user plane protocol stack of each node in network 1.
  • a in FIG. 6 shows the control plane protocol stack of each node in the multi-hop relay network 1 in the architecture
  • B in FIG. 6 shows the multi-hop in the architecture. Following the user plane protocol stack of each node in network 1.
  • the F1AP message transmitted on each segment of the air interface is not encrypted by the air interface, and the security of the data cannot be effectively guaranteed.
  • the embodiment of the present application provides a data transmission method.
  • the first communication device (or the chip in the first communication device) sends the first data and the second communication device to the second communication device.
  • the first data may be at least one of user plane data (such as a PDCP PDU of a terminal), a status report, a control plane message, and an RRC message of the terminal.
  • the first message sent by the first communications device to the second communications device includes the type identifier. Therefore, after acquiring the first message, the second communications device in the embodiment of the present application may directly determine the first identifier according to the type identifier.
  • the type of the data, and the first message is processed by the method corresponding to the type of the first data, further improving the processing efficiency of each node in the multi-hop relay network.
  • the first communication device in the embodiment of the present application may be an intermediate forwarding node, a serving node of the terminal, a host base station, or a DU in the host base station system.
  • the second communication device is a previous hop device or a next hop device of the intermediate forwarding node.
  • the second communication device is the last hop device of the service node of the terminal.
  • the second communication device is the next hop device of the first communication device.
  • the data transmission method provided by the embodiment of the present application is applicable to a communication system.
  • the communication system may be a 5G system, or may be an LTE system, or may be another communication system including at least one RN, which is not specifically limited in this embodiment of the present application.
  • the host base station and any of the relay nodes in FIG. 2 may be the first communication device.
  • the communication system includes two RNs as an example for description.
  • the communication system includes a terminal 70, an RN 71, an RN 72, and a donor base station system 73.
  • the terminal 70 communicates with the RN 72 via the Uu interface
  • the RN 72 communicates with the RN 71 via the Un2 interface
  • the RN 71 communicates with the donor base station system 73 via the Un1 interface.
  • FIG. 7 is only an example of the communication system provided by the embodiment of the present application, and is not specifically limited to the communication system.
  • both the RN 71 and the RN 72 may serve multiple terminals, or the communication system may have at least one RN between the RN 71 and the RN 72.
  • the terminal 70 in the embodiment of the present application may refer to a mobile phone (such as the mobile phone 800 shown in FIG. 8), a tablet computer, a personal computer (PC), and an individual capable of realizing data transmission with the RN 72 on the control plane and the user plane.
  • a mobile phone such as the mobile phone 800 shown in FIG. 8
  • a tablet computer such as the mobile phone 800 shown in FIG. 8
  • PC personal computer
  • an individual capable of realizing data transmission with the RN 72 on the control plane and the user plane.
  • the mobile phone 800 is used as an example of the terminal.
  • the mobile phone 800 may specifically include: a processor 801, a radio frequency (RF) circuit 802, a memory 803, a touch screen 804, a Bluetooth device 805, and one or more sensors 806.
  • a component such as a Wireless Fidelity (Wi-Fi) device 807, a positioning device 808, an audio circuit 809, a peripheral interface 810, and a power supply device 811.
  • Wi-Fi Wireless Fidelity
  • a positioning device 808 an audio circuit 809
  • peripheral interface 810 a peripheral interface 810
  • a power supply device 811 can communicate over one or more communication buses or signal lines (not shown in Figure 8).
  • the hardware structure shown in FIG. 8 does not constitute a limitation to a mobile phone, and the mobile phone 800 may include more or less components than those illustrated, or some components may be combined, or different component arrangements.
  • the processor 801 is a control center of the mobile phone 800.
  • the various parts of the mobile phone 800 are connected by various interfaces and lines, and the mobile phone 800 is executed by running or executing an application stored in the memory 803 and calling data stored in the memory 803.
  • processor 801 can include one or more processing units.
  • the processor 801 may further include a fingerprint verification chip, configured to verify the collected fingerprint.
  • the radio frequency circuit 802 can be used to receive and transmit wireless signals during transmission or reception of information or calls.
  • the radio frequency circuit 802 can process the downlink data of the base station and then process it to the processor 801; in addition, transmit data related to the uplink to the base station.
  • radio frequency circuits include, but are not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like.
  • the radio frequency circuit 802 can also communicate with other devices through wireless communication.
  • the wireless communication can use any communication standard or protocol, including but not limited to global mobile communication systems, general packet radio services, code division multiple access, wideband code division multiple access, long term evolution, email, short message service, and the like.
  • the memory 803 is used to store applications and data, and the processor 801 executes various functions and data processing of the mobile phone 800 by running applications and data stored in the memory 803.
  • the memory 803 mainly includes a storage program area and a storage data area, wherein the storage program area can store an operating system, an application required for at least one function (such as a sound playing function, an image processing function, etc.); the storage data area can be stored according to the use of the mobile phone. Data created at 800 o'clock (such as audio data, phone book, etc.).
  • the memory 803 may include high speed random access memory (RAM), and may also include nonvolatile memory such as a magnetic disk storage device, a flash memory device, or other volatile solid state storage device.
  • the memory 803 can store various operating systems such as an iOS operating system, an Android operating system, and the like.
  • the above memory 803 may be independent and connected to the processor 801 through the above communication bus; the memory 803 may also be integrated with the processor 801.
  • the touch screen 804 may specifically include a touch panel 804-1 and a display 804-2.
  • the touchpad 804-1 can collect touch events on or near the user of the mobile phone 800 (for example, the user uses a finger, a stylus, or the like on the touchpad 804-1 or the touchpad 804. The operation near -1), and the collected touch information is sent to other devices (for example, processor 801).
  • the touch event of the user in the vicinity of the touchpad 804-1 may be referred to as a hovering touch; the hovering touch may mean that the user does not need to directly touch the touchpad in order to select, move or drag a target (eg, an icon, etc.) , and only the user is located near the device to perform the desired function.
  • the touch panel 804-1 can be implemented in various types such as resistive, capacitive, infrared, and surface acoustic waves.
  • a display 804-2 can be used to display information entered by the user or information provided to the user as well as various menus of the handset 800.
  • the display 804-2 can be configured in the form of a liquid crystal display, an organic light emitting diode, or the like.
  • the touchpad 804-1 can be overlaid on the display 804-2. When the touchpad 804-1 detects a touch event on or near it, the touchpad 804-1 transmits to the processor 801 to determine the type of touch event, followed by the processor. 801 can provide a corresponding visual output on display 804-2 depending on the type of touch event.
  • touchpad 804-1 and display 804-2 are implemented as two separate components to implement the input and output functions of handset 800, in some embodiments, touchpad 804- 1 is integrated with the display 804-2 to implement the input and output functions of the mobile phone 800. It is to be understood that the touch screen 804 is formed by stacking a plurality of layers of materials. In the embodiment of the present application, only the touch panel (layer) and the display screen (layer) are shown, and other layers are in the embodiment of the present application. Not recorded in the middle.
  • the touch panel 804-1 may be disposed on the front surface of the mobile phone 800 in the form of a full-board
  • the display screen 804-2 may also be disposed on the front surface of the mobile phone 800 in the form of a full-board, so that the front side of the mobile phone can be borderless. Structure.
  • the mobile phone 800 can also have a fingerprint recognition function.
  • the fingerprint reader 812 can be configured on the back of the handset 800 (eg, below the rear camera) or on the front side of the handset 800 (eg, below the touch screen 804).
  • the fingerprint collection device 812 can be configured in the touch screen 804 to implement the fingerprint recognition function, that is, the fingerprint collection device 812 can be integrated with the touch screen 804 to implement the fingerprint recognition function of the mobile phone 800.
  • the fingerprint capture device 812 is disposed in the touch screen 804 and may be part of the touch screen 804 or may be otherwise disposed in the touch screen 804.
  • the main component of the fingerprint collection device 812 in the embodiment of the present application is a fingerprint sensor, which can adopt any type of sensing technology, including but not limited to optical, capacitive, piezoelectric or ultrasonic sensing technologies. .
  • the mobile phone 800 can also include a Bluetooth device 805 for enabling data exchange between the handset 800 and other short-range devices (eg, mobile phones, smart watches, etc.).
  • the Bluetooth device in the embodiment of the present application may be an integrated circuit or a Bluetooth chip or the like.
  • the handset 800 can also include at least one type of sensor 806, such as a light sensor, motion sensor, and other sensors.
  • the light sensor may include an ambient light sensor and a proximity sensor, wherein the ambient light sensor may adjust the brightness of the display of the touch screen 804 according to the brightness of the ambient light, and the proximity sensor may turn off the power of the display when the mobile phone 800 moves to the ear.
  • the accelerometer sensor can detect the magnitude of acceleration in all directions (usually three axes). When it is stationary, it can detect the magnitude and direction of gravity. It can be used to identify the gesture of the mobile phone (such as horizontal and vertical screen switching, related Game, magnetometer attitude calibration), vibration recognition related functions (such as pedometer, tapping), etc.
  • the mobile phone 800 can also be configured with gyroscopes, barometers, hygrometers, thermometers, infrared sensors and other sensors, here Let me repeat.
  • the Wi-Fi device 807 is configured to provide the mobile phone 800 with network access complying with the Wi-Fi related standard protocol, and the mobile phone 800 can access the Wi-Fi access point through the Wi-Fi device 807, thereby helping the user to send and receive emails, Browsing web pages and accessing streaming media, etc., it provides users with wireless broadband Internet access.
  • the Wi-Fi device 807 can also function as a Wi-Fi wireless access point, and can provide Wi-Fi network access to other devices.
  • the positioning device 808 is configured to provide a geographic location for the mobile phone 800. It can be understood that the positioning device 808 can be specifically a receiver of a positioning system such as a Global Positioning System (GPS) or a Beidou satellite navigation system or a Russian GLONASS. After receiving the geographical location transmitted by the positioning system, the positioning device 808 sends the information to the processor 801 for processing, or sends it to the memory 803 for storage. In some other embodiments, the positioning device 808 can also be a receiver of an Assisted Global Positioning System (AGPS), which assists the positioning device 808 in performing ranging and positioning services by acting as a secondary server.
  • AGPS Assisted Global Positioning System
  • the secondary location server provides location assistance over a wireless communication network in communication with a location device 808 (i.e., a GPS receiver) of a device, such as handset 800.
  • the positioning device 808 can also be a Wi-Fi access point based positioning technology. Since each Wi-Fi access point has a globally unique MAC address, the device can scan and collect broadcast signals from surrounding Wi-Fi access points when Wi-Fi is turned on, so Wi- can be obtained. The MAC address broadcasted by the Fi access point; the device sends the data (such as the MAC address) capable of indicating the Wi-Fi access point to the location server through the wireless communication network, and each Wi-Fi access point is retrieved by the location server. The geographic location, combined with the strength of the Wi-Fi broadcast signal, calculates the geographic location of the device and sends it to the location device 808 of the device.
  • Audio circuitry 809, speaker 813, microphone 814 can provide an audio interface between the user and handset 800.
  • the audio circuit 809 can transmit the converted electrical data of the received audio data to the speaker 813 for conversion to the sound signal output by the speaker 813; on the other hand, the microphone 814 converts the collected sound signal into an electrical signal by the audio circuit 809. After receiving, it is converted into audio data, and then the audio data is output to the RF circuit 802 for transmission to, for example, another mobile phone, or the audio data is output to the memory 803 for further processing.
  • the peripheral interface 810 is used to provide various interfaces for external input/output devices (such as a keyboard, a mouse, an external display, an external memory, a subscriber identity module card, etc.). For example, it is connected to the mouse through a Universal Serial Bus (USB) interface, and is connected to a Subscriber Identification Module (SIM) card provided by the service provider through a metal contact on the card slot of the subscriber identity module. . Peripheral interface 810 can be used to couple the external input/output peripherals described above to processor 801 and memory 803.
  • USB Universal Serial Bus
  • SIM Subscriber Identification Module
  • the mobile phone 800 can communicate with other devices in the device group through the peripheral interface 810.
  • the peripheral interface 810 can receive display data sent by other devices for display, etc. No restrictions are imposed.
  • the mobile phone 800 can also include a power supply device 811 (such as a battery and a power management chip) that supplies power to various components.
  • the battery can be logically connected to the processor 801 through the power management chip to manage charging, discharging, and power management through the power supply device 811. And other functions.
  • the mobile phone 800 may further include a camera (front camera and/or rear camera), a flash, a pico projector, a near field communication (NFC) device, and the like, and details are not described herein.
  • a camera front camera and/or rear camera
  • flash flash
  • pico projector pico projector
  • NFC near field communication
  • FIG. 9 is a schematic diagram of a composition of an RN according to an embodiment of the present disclosure.
  • the RN may include at least one processor 91, a memory 92, a transceiver 93, and a bus 94.
  • the processor 91 is a control center of the RN, and may be a processor or a collective name of a plurality of processing elements.
  • the processor 91 is a CPU, and may be an Application Specific Integrated Circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of the present application, for example, one or more microprocessors. (Digital Signal Processor, DSP), or one or more Field Programmable Gate Arrays (FPGAs).
  • ASIC Application Specific Integrated Circuit
  • the processor 91 can perform various functions of the RN by running or executing a software program stored in the memory 92 and calling data stored in the memory 92.
  • processor 91 may include one or more CPUs, such as CPU 0 and CPU 1 shown in the figures.
  • the RN may include multiple processors, such as processor 91 and processor 95 shown in FIG.
  • processors can be a single core processor (CPU) or a multi-core processor (multi-CPU).
  • a processor herein may refer to one or more devices, circuits, and/or processing cores for processing data, such as computer program instructions.
  • the memory 92 can be a Read-Only Memory (ROM) or other type of static storage device that can store static information and instructions, a Random Access Memory (RAM) or other type that can store information and instructions.
  • the dynamic storage device can also be an Electrically Erasable Programmable Read-Only Memory (EEPROM), a Compact Disc Read-Only Memory (CD-ROM) or other optical disc storage, and a disc storage device. (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or can be used to carry or store desired program code in the form of instructions or data structures and can be Any other media accessed, but not limited to this.
  • Memory 92 may be present independently and coupled to processor 91 via bus 94. The memory 92 can also be integrated with the processor 91.
  • the memory 92 is used to store a software program that executes the solution of the present application, and is controlled by the processor 91 for execution.
  • the transceiver 93 is configured to communicate with other devices or communication networks. For example, it is used for communication with a communication network such as an Ethernet, a radio access network (RAN), or a wireless local area network (WLAN).
  • Transceiver 93 may include all or part of a baseband processor, and may also optionally include an RF processor.
  • the RF processor is used to transmit and receive RF signals
  • the baseband processor is used to implement processing of a baseband signal converted by an RF signal or a baseband signal to be converted into an RF signal.
  • the bus 94 may be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus.
  • ISA Industry Standard Architecture
  • PCI Peripheral Component Interconnect
  • EISA Extended Industry Standard Architecture
  • the bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 9, but it does not mean that there is only one bus or one type of bus.
  • the device structure shown in FIG. 9 does not constitute a limitation to the RN, and may include more or less components than those illustrated, or some components may be combined, or different component arrangements.
  • the host base station system 73 in the embodiment of the present application may be an independent host base station, which may be a base station (BS) or a base station controller for wireless communication, or may be composed of a DU 730 and a CU 731. Since the donor base station system 73 may be composed of the DU 730 and the CU 731, the DU 730 and the CU 731 are indicated by dashed boxes in FIG. 7 described above.
  • BS base station
  • a base station controller for wireless communication or may be composed of a DU 730 and a CU 731. Since the donor base station system 73 may be composed of the DU 730 and the CU 731, the DU 730 and the CU 731 are indicated by dashed boxes in FIG. 7 described above.
  • the main functions of the host base station system 73 include one or more of the following functions: performing radio resource management, IP header compression, and user data stream encryption, performing MME selection when the terminal is attached, and routing user plane data to the SGW, The organization and transmission of paging messages, the organization and transmission of broadcast messages, the configuration of measurement and measurement reports for mobility or scheduling, and the like.
  • the name of the donor base station may vary in systems employing different wireless access technologies.
  • the name of the donor base station is an evolved base station (evolved NodeB, eNB or eNodeB); in the 3rd generation mobile communication
  • the name of the host base station is a base station (Node B); in the next generation wireless communication system (such as a 5G system), the name of the host base station is gNB.
  • This name may change as communication technologies evolve.
  • the donor base station may be other means of providing wireless communication functionality to the terminal device.
  • FIG. 10 shows the hardware structure of the donor base station.
  • the donor base station may include at least one processor 101, a memory 102, a transceiver 103, and a bus 104.
  • processor 101 may include one or more CPUs, such as CPU0 and CPU1 in FIG.
  • the host base station may include multiple processors, such as the processor 101 and the processor 105 in FIG.
  • the device structure illustrated in FIG. 10 does not constitute a definition of a host base station, and may include more or fewer components than those illustrated, or some components may be combined, or different component arrangements.
  • the data transmission method provided by the embodiment of the present application is transmitted in a unified message format for the different types of data, which can effectively reduce the time for each node in the multi-hop relay network to process messages having the format. Therefore, each RN and the host base station system in the embodiment of the present application have a function of supporting generation/resolving of messages having the same format.
  • the embodiment of the present application adds a corresponding protocol layer in the protocol stack of the RN and the host base station system, or adds a corresponding function in an existing protocol layer (such as the RLC layer or the PDCP layer).
  • an existing protocol layer such as the RLC layer or the PDCP layer.
  • the above-described function of generating/resolving messages having the same format is supported. If the host base station system is composed of the DU and the CU, add a separate protocol layer with corresponding functions in the protocol stack of the DU or add a corresponding function in an existing protocol layer (such as the RLC layer).
  • the added protocol layer may be referred to as an Integrated Access Link and Backhaul Link (IAB) functional protocol layer, and may be other names.
  • IAB Integrated Access Link and Backhaul Link
  • FIG. 11 shows a control plane protocol stack and a user plane protocol stack of each node in the embodiment of the present application.
  • FIG. 12 shows the control plane protocol stack and the user plane protocol stack of each node in the hop-by-hop architecture in the embodiment of the present application
  • FIG. 13 shows the RN 72 to The control plane protocol stack and the user plane protocol stack of each node in the embodiment of the present application are in the end-to-end architecture of the DU 730.
  • FIG. 14 shows a control plane protocol stack and a user plane protocol stack of each node in the embodiment of the present application.
  • FIG. 15 shows a control plane protocol stack and a user plane protocol stack of each node in the embodiment of the present application.
  • the F1 interface provides a method for the CU to interact with the DU in the base station system, and the F1AP defines a signaling flow for supporting the function of the F1 interface.
  • the embodiment of the present application can establish a similar interface between the RN and the host base station system/upper hop RN for the interaction between the RN and the host base station system/upper hop RN, which can be an F1 interface.
  • the name of a similar interface having similar functions for transmitting UE related information for UE context management, UE configuration, etc. is not limited.
  • the embodiment of the present application refers to this as an F1-like interface.
  • a unified message format can be used to transmit different types of data.
  • the unified message format includes the type identifier and the first data, and the unified message format may refer to the subsequent description.
  • the type identifier is used to indicate the type of the first data.
  • the type of the first data includes at least one of user plane data, a status report, a control plane message, and an RRC message of the terminal.
  • the first data in the embodiment of the present application is user plane data.
  • the user plane data includes a PDCP PDU/RLC PDU/H-RLC PDU of the DRB belonging to the terminal, and the data of the user plane of the terminal may be a data packet similar to the GTP-U format.
  • the H-RLC refers to dividing the existing RLC protocol layer into multiple parts according to functions (which may be called a sub-protocol layer), and the H-RLC is one part, and is responsible for performing functions such as ARQ.
  • the IAB function protocol layer can transmit the user plane data in one of two ways:
  • Method 1 User plane data (PDCP PDU RLC PDU/H-RLC PDU belonging to the DRB of the terminal) is carried in the user plane of the F1-like interface.
  • the user plane protocol stack of the F1-like interface may include any one or any combination of the following: a GTP-U layer, a UDP layer, and an IP layer.
  • the user plane data (the PDCP PDU RLC PDU/H-RLC PDU of the DRB belonging to the terminal) is directly carried in the IAB function protocol layer for transmission. For example, it is directly carried in the PDU of the IAB function protocol layer.
  • the first message in the embodiment of the present application further includes first indication information, where the first indication information is used to indicate the DRB of the terminal to which the user plane data belongs.
  • the first indication information may be user plane transport layer information, where the user plane transport layer information may include any one of the following information or a combination of any one of the following: TEID, source IP address, destination IP address, source Port number, destination port number.
  • the first message sent by the IAB function protocol layer needs to include an additional terminal identifier and DRB identifier information.
  • the first indication information may include any one of the following information or a combination of any of the following: TEID, source IP address, destination IP address, source port number, destination port number, terminal identifier, DRB identifier.
  • the first message further includes a sequence number (SN) of the user plane data.
  • the global SN of the user plane data is divided into the SN of the user plane data in the DRB of the terminal and the SN of the user plane data in the DRB of the RN.
  • the SN of the user plane data in the DRB of the terminal is generated by the host base station system and the terminal/the service node of the terminal, and the host base station, the intermediate forwarding node, and the service node of the terminal perform maintenance, and the intermediate forwarding node does not change the SN, so it is called Global SN.
  • the SN of the user plane data in the DRB of the terminal may be the PDCP SN and/or HFN of the terminal, or may be the RLC SN of the terminal, where the two SNs are supported by the host base station system (corresponding to downlink data) and the terminal (corresponding to The uplink data is generated; it can also be a GTP-U SN, or a newly defined SN, for example, an SN inside the IAB functional protocol layer, which is simply referred to as an IAB SN of the terminal, and the above two SNs are supported by the host base station system (corresponding to the downlink) Data) is generated with the service node (corresponding to the uplink data) of the terminal.
  • the SN of the user plane data in the DRB of the RN is between the RN and the host base station system directly connected through the air interface, or the SN maintained between the RN and the RN, which is simply referred to as the RN DRB SN.
  • the RN DRB SN may be an RN PDCP SN (if the protocol stack of the Un interface has an RN PDCP protocol layer, and the IAB function protocol layer is below the RN PDCP protocol layer, or the IAB function protocol layer and the RN PDCP protocol layer Co-located, at this time, the RN PDCP SN can be identified in the IAB function protocol layer, or a newly defined SN, for example, the SN inside the IAB function protocol layer, referred to as RN IAB SN.
  • the data of the terminal for example: PDU Session, QoS flow (whose identifier is called QoS flow identifier, QFI)
  • QoS parameter requirements For example: GBR (Guranteed Bit Rate), latency/end-to-end delay, jitter, packet loss rate, forwarding priority, and voice MOS value.
  • GBR Guard Bit Rate
  • the host base station system sends the foregoing QoS parameters to the RN and the intermediate node serving the terminal.
  • each RAN node may limit the rate of the Non-GBR service of the terminal to an AMBR (Aggregate Maximum Bit Rate) value.
  • the RAN node when the data of the terminal is via the host base station system on the RAN side and one or more RNs, the RAN node not only needs to know the corresponding QoS parameter requirements; but also needs to monitor the data of the terminal to ensure that the corresponding QoS requirements can be met.
  • Each RN needs to be able to identify data from different terminals (and identify different DRBs and/or QFIs belonging to one terminal).
  • the host base station system directly informs each RN, and each RN can guarantee itself. Similarly, for AMBR, each RN can guarantee it by itself. For the delay, the host base station system needs to negotiate with each RN, or the host base station system decides to notify each RN, so that each RN guarantees the delay requirement of the Un/Uu interface associated with itself.
  • the first data in the embodiment of the present application is a status report.
  • the status report is used to indicate the transmission status of the DRB data packet of the terminal, the intermediate forwarding node, and the service node of the terminal.
  • the transmission status of the DRB data packet refers to the transmission status and/or packet loss status of the DRB data packet.
  • the RLC layer that is peered with the terminal 70 is placed on the RN 72, and the PDCP layer that is peered with the terminal 70 is placed on the host base station system 73. Therefore, the embodiment of the present application
  • the RLC status report and PDCP status report in the middle are different from the existing status report.
  • the data of the terminal (for example, the granularity of the terminal DRB in the L2 architecture) is first transmitted on the Un interface (for example, the DRB of the RN) to the RN serving the terminal, and the RN connects the terminal through the Uu interface.
  • the data bearer is sent to the terminal on the DRB of the terminal.
  • the RLC SN of the terminal of the Uu interface and the RLC SN of the RN of the Un interface are independently numbered. Therefore, the status report for feedback of the RLC SN can only feed back the RLC transmission status of a Uu interface or a Un interface.
  • the RN may not be able to obtain the PDCP SN of the terminal. Therefore, the PDCP status report cannot be fed back based on the PDCP SN of the terminal. For example, in the foregoing FIG. 4, FIG. 5 and FIG.
  • the bearer is transmitted in the Un port, and if the GTP-U data packet is encrypted by the IP layer, If the RN 1 is not aware of the encryption mode, the RN 1 cannot know the PDCP SN of the terminal. Even if the PDCP SN can be learned, the GTP-U data packet needs to be parsed, and additional processing overhead is introduced.
  • the PDCP PDU of the terminal is transmitted on the Un interface, it is also processed by the PDCP entity of the RN DRB. The PDCP entity needs to encrypt the user plane data.
  • an end-to-end SN between the host base station system and the RN serving the terminal may be defined, and the intermediate forwarding node and the RN serving the terminal may perform feedback of the status report based on the SN.
  • the end-to-end SN between the host base station system and the RN serving the terminal in the embodiment of the present application is referred to as a global SN of the terminal, such as an IAB SN.
  • the global SN may be a PDCP SN (the intermediate forwarding node may be aware of the PDCP SN of the terminal), or may be an RLC SN.
  • the PDCP SN refers to the SN corresponding to the PDCP SDU/PDU
  • the RLC SN refers to the SN corresponding to the RLC SDU (or RLC SDU segment).
  • the status report when the first data is a status report, the status report includes a global SN of user plane data carried by the DRB of the terminal.
  • the first data further includes fifth indication information used to indicate the DRB of the terminal.
  • the status report may be a status report of the DRB of the terminal, and is used to provide information about whether the user plane data carried by the DRB of the terminal is successfully transmitted/received.
  • the status report may be a status report of the DRB of the terminal that serves the RN, or may be a status report of the DRB of the terminal that the other RN provides the service (in this case, the RN is not directly connected to the terminal through the air interface, But forward the data for the terminal). That is to say, the transmission granularity of the status report is the DRB of the terminal.
  • the fifth indication information may be at least one of a TEID, a source IP address, a destination IP address, a source port number, a target port number, a terminal identifier, and a DRB identifier.
  • the status report of the DRB of the terminal may be directed to one DRB of the terminal.
  • the status report includes fifth indication information corresponding to the terminal; or the status report transmitted by the IAB function protocol layer may be used for multiple terminals.
  • the DRB at this time, the status report includes a plurality of fifth indication information related to the terminal; or the status report transmitted by the IAB function protocol layer may be directed to all DRBs of the terminal, and the status report includes a terminal for indicating the terminal.
  • the sixth indication information is provided.
  • the sixth indication information may be any one of the following information or a combination of any one of the following: a cell radio network temporary identifier C-RNTI, a cell identifier, a terminal context identifier, an F1 interface identifier of the terminal, and a terminal F1 -like interface identifier, TEID, terminal identifier in other formats.
  • the status report transmitted by the IAB function protocol layer can be directed to all DRBs of the terminal
  • the status report further includes all fifth indication information related to the terminal. If the status report does not include all the fifth indication information related to the terminal, the status report may be composed of a plurality of status reports of the DRBs of the terminals arranged in a certain order. The order may be specified by a protocol preset, or may be arranged in descending order of DRB logos or small to large.
  • the status report of the DRB of the terminal may be an RLC status report/PDCP status report of the terminal.
  • the DRB status report of the terminal may be a combination of RLC status report/PDCP status report of one or more terminals generated by the IAB function protocol layer.
  • the status report of the DRB of the terminal further includes the global SN of the terminal.
  • the host base station system/intermediate forwarding node can determine the transmission status of the data packet of the terminal according to the global SN.
  • the status report of the DRB of the terminal includes the status of the downlink and/or uplink data packets.
  • the status of the data packet may include any one of the following or a combination of any one of the following: a maximum successful transmitted/received global SN (Highest Successfully Delivered Sequence Number), and a transmission hole (referring to one or more consecutive SNs) Maximum global SN and minimum global SN of unsuccessfully transmitted/received data packets, transmission hole sequence number, global SN for maximum consecutive successful transmission/reception, maximum global SN and minimum global SN for one successful transmission data block, successful transmission Data block sequence number, global SN successfully transmitted, lost global SN, maximum transmitted/received global SN, terminal identity, DRB identity, TEID.
  • the specific information included in the status report of the DRB of the terminal is not limited to the foregoing SN, and may also include, for example, a global SN of the first lost packet and a global SN of the next packet to be transmitted.
  • the global SN of the first lost packet is the smallest global SN in the transmission hole, and the next packet to be transmitted is downlinked.
  • the global SN is the global SN+1 of the largest downlink transmission. Therefore, the possible cases are not listed here.
  • the status report of the DRB of the terminal may also be in the form of a bitmap, where each bit corresponds to a state in which a data packet corresponding to one SN is lost.
  • the global SN of the largest successfully transmitted is When the data of a certain DRB of the terminal is transmitted between the node that generates the status report and the terminal that is serving the next hop node/the terminal that is serving the same, the next hop node/the terminal that it serves successfully receives the DRB of the terminal. In the data packet, the SN corresponding to the largest packet of the SN.
  • the global SN of the maximum consecutively successfully transmitted is the next hop node/the terminal of the service succeeded when the data of the DRB of the terminal is transmitted between the node generating the status report and the terminal of the next hop node/the service thereof.
  • the SN consecutive data packets of this DRB belonging to the terminal the SN corresponding to the largest packet of the SN.
  • the transmission hole sequence number in the embodiment of the present application refers to a sequence number corresponding to each transmission hole when it is necessary to indicate different transmission holes when there may be more than one transmission hole.
  • the successful sending means that the sending end receives the acknowledgement (Acknowledge, ACK) feedback of the receiving end.
  • the lost data packet is received by the opposite party (Non Acknowledge (NACK) feedback, or the ACK feedback of the opposite end is not received.
  • successful receiving means that the receiving end successfully receives the data sent by the sending end.
  • the transmission success data block refers to one or more SN consecutive data packets that are successfully received in the data packet of the global SN that is larger than the above-mentioned maximum consecutive successful transmission.
  • the transmission success data block sequence number refers to the sequence number corresponding to each transmission success data block when it is necessary to indicate different transmission success data blocks when there may be more than one transmission success data block.
  • the status report may be a status report of the DRB of the RN, and used to provide information about whether the user plane data carried by the DRB of the RN is correctly sent/received.
  • the status report may be a status report of the DRB of its own Un interface, or may be a status report generated by the RN/DU for the DRB of the Un interface of the next hop RN. That is to say, the transmission granularity of the status report is the DRB of the RN.
  • the status report of the DRB of the RN may be reported for a status of the DRB of the at least one terminal carried by each DRB in the at least one DRB of the RN.
  • the status report of the DRB of the RN further includes a terminal identifier and/or a DRB identifier, or an identifier (eg, TEID, UE context context identifier, or other format identifier) for identifying the DRB of the terminal.
  • the status report of the DRB of the RN does not include the DRB identifier
  • the status report of the DRB of the RN may be composed of a status report of the DRBs of the plurality of terminals arranged in a certain order. The order of the arrangement here may be pre-defined by the protocol, or may be arranged in order of DRB identification from large to small or from small to large.
  • the DRB of each RN corresponds to an IAB function protocol layer entity.
  • the status report of the DRB of the RN does not distinguish the DRB of the terminal it carries, and feeds back the DRB transmission status of the RN by the SN in the DRB carrying the RN.
  • the status report of the DRB of the RN includes any one of the following or a combination of any one of the following: a maximum successful transmission/reception RN DRB SN, and one transmission hole (referring to one or SN consecutive multiple unsuccessfully sent) /received data packet) maximum RN DRB SN and minimum RN DRB SN, transmission hole sequence number, maximum consecutive successfully transmitted/received RN DRB SN, maximum RN DRB SN and minimum RN DRB SN for transmission success data block, transmission Success data block sequence number, maximum transmitted/received RN DRB SN, successfully transmitted RN DRB SN, lost RN DRB SN, RN identity, DRB identity, RN DRB identity.
  • the status report of the DRB of the RN may include a status report of all DRBs of the Un interface of the RN, or may be a status report of all DRBs including the next hop of the RN.
  • the DRB status report of the RN further includes an RN identifier and/or a DRB identifier, or includes information for identifying the RN DRB. If the DRB identifier is not carried, the DRB status report of the RN may be composed of a plurality of status reports of DRBs of the RNs arranged in a certain order. The order here may be pre-specified by the protocol, or may be arranged in order of DRB identification from large to small or from small to large.
  • the RN may also generate an RLC status report of the Un port of the DRB.
  • the status report in this application is referred to as an RN RLC status report.
  • the RN RLC status report includes any one of the following or a combination of any of the following: the largest successfully transmitted RN RLC SN, the successfully transmitted RN RLC SN, the lost RN RLC SN, the largest RN RLC SN of a transport hole, and Minimum RN RLC SN, transmission hole sequence number, RN identity, DRB identity.
  • the RN generates a status report of the RN at the IAB function protocol layer based on the RN RLC status report described above.
  • the status report of the RN is composed of some or all of the RN RLC status reports of the RN.
  • an IA has an IAB function protocol layer entity, and all DRBs of the RN correspond to the IAB function protocol layer entity.
  • the status report of the RN further includes an RN identifier and/or a DRB identifier, or includes information for identifying the RN DRB. If the status report of the RN does not include the DRB identifier, the status report may be composed of multiple RN RLC status reports arranged in a certain order.
  • the status report of the RN includes only one RN RLC status report corresponding to the RN DRB.
  • the IAB function protocol layer entity may be a per RN DRB, that is, one RN DRB corresponds to one IAB function protocol layer entity.
  • the status report in the embodiment of the present application may be periodically reported, or may be triggered by an event, which is not specifically limited in this embodiment of the present application.
  • the periodic report can be used by the data anchor (for example, the host base station system) to delete the data packet that has been successfully sent according to the foregoing status report.
  • the data anchor for example, the host base station system
  • the data anchor deletes the data packet that has been successfully sent according to the foregoing status report.
  • the PDCP entity of the terminal deletes the PDCP PDU, and the IAB function protocol is used.
  • the layer buffers the PDCP PDU of the downlink terminal, and deletes the PDCP PDU after the received status report feedback terminal has correctly received the PDCP PDU.
  • periodic reporting can also be used inside the data anchor.
  • the PDCP entity of the terminal continues to buffer the PDCP PDU, and the data anchor receiving status report is that the terminal has correctly received the PDCP PDU.
  • the PDCP entity that notifies the terminal deletes the PDCP PDU.
  • the event may be: terminal handover, radio link failure (RLF), RN handover, RN RLF or polling indication (exemplary, the polling indication) Instructions generated for the IAB functional protocol layer).
  • RLF radio link failure
  • RN handover RN handover
  • RN RLF polling indication
  • the terminal switches from the source node to the target node, data forwarding from the source node to the target node is required.
  • the source node of the terminal may feed back the status report of the terminal to the data anchor, or the status report of the DRB of one or several terminals, for the data anchor point. Data that is not successfully transmitted to the terminal is forwarded to the target node.
  • the data anchor point may be a common last hop or an upper n (n>1) hop RN of the source node and the target node, or may be a host base station common to the source node and the target node (for example: PDCP peering with the terminal) Placed at the donor base station, the PDCP PDU that the terminal did not successfully receive may also be cached on the donor base station). That is to say, before and after the terminal is switched, the data of the terminal needs to be relayed through the data anchor point.
  • the source node may feed back the RLC status report of the terminal to the data anchor point.
  • the source node may be an RN, and the target node may be an RN or a donor base station.
  • the target node is the same node as the data anchor. Since the data anchor needs to send the data that the terminal does not successfully receive to the target node, so that the target node sends the data to the terminal, the data anchor needs to know the information of the target node, which can be based on the following manner: mode 1, the source node informs the data anchor Point, for example, by switching the preparation process, the source node negotiates with the target node in advance, and informs the data anchor point of the information of the target node; and second, the target node notifies the data anchor point, for example, when the terminal is accessed by the target node, The target node notifies the data anchor so that the data anchor switches the data path of the terminal from the source node to the target node.
  • mode 1 the source node informs the data anchor Point, for example, by switching the preparation process, the source node negotiates with the target node in advance,
  • the status report for the DRB transmission status may be sent, for explicitly notifying the target node/data anchor that the data packet is not successfully received.
  • the terminal By sending the status report to the data anchor by the terminal itself, it is possible to prevent the data anchor from transmitting the data packet that the terminal has successfully received but still has the acknowledgment (ACK) feedback to the target node; or, if the data anchor points the above terminal already
  • the data packet that is successfully received but still has the acknowledgment (ACK) feedback in the future is sent to the target node, and the terminal sends the status report to the target node by itself, which can prevent the target node from successfully receiving the terminal but still send an acknowledgment (ACK) in the future.
  • the feedback packet is sent to the terminal.
  • the terminal performs RRC connection re-establishment in the cell provided by the target node, and the target node notifies the original serving node that the terminal generates RLF, and the original serving node may forward the data of the terminal to the target node.
  • the data anchor caches the data that needs to be forwarded
  • the original serving node of the terminal may feed back the status report of the terminal to the data anchor, or the status report of the DRB of several terminals, for the data anchor point.
  • the target node forwards data that has not been successfully sent to the terminal.
  • the data anchor point may be a common last hop or an upper n (n>1) hop RN of the original serving node and the target node, or may be a host base station common to the original serving node and the target node (eg, peering with the terminal)
  • the PDCP is placed at the donor base station, and the PDCP PDU that the terminal did not successfully receive may also be cached on the donor base station). That is to say, before and after the RRC connection of the terminal is re-established, the data of the terminal needs to be transmitted through the relay of the data anchor point.
  • the original serving node may feed back the RLC status report of the terminal to the data anchor point.
  • the original serving node may be an RN
  • the target node may be an RN or a donor base station.
  • the target node is the same node as the data anchor.
  • the data anchor Since the data anchor needs to send the data that the terminal does not successfully receive to the target node, so that the target node sends the data to the terminal, the data anchor needs to know the information of the target node, which can be based on the following manner: mode 1, the original service node informs the data
  • the anchor point for example, the original service node configures the target node to the terminal in advance, and informs the data anchor point of the information of the target node in advance;
  • the target node notifies the data anchor point, for example, when the terminal is accessed by the target node, the target node
  • the data anchor is notified so that the data anchor switches the data path of the terminal from the original serving node to the target node.
  • the terminal may send a status report for the DRB transmission status, which is used to explicitly notify the target node/data anchor that the data packet is not successfully received.
  • the RN when the RN switches from the source node to the target node, data forwarding from the source node to the target node needs to be completed.
  • the source node of the RN may feed back the status report of the RN to the data anchor, or the DRB status report of one or several RNs (where the RN service is carried)
  • the data of the terminal is used by the data anchor to forward data that is not successfully sent to the RN to the target node.
  • the data anchor point is a common last hop or an upper n (n>1) hop RN of the source node and the target node, or a host base station common to the source node and the target node (eg, the PDCP peering with the terminal is placed in the The host base station, the PDCP PDU that the terminal did not successfully receive may also be cached on the donor base station).
  • the data of the RN (for example, the data including the terminal of the RN service and the data of the next hop of the RN service) need to be relayed by the data anchor.
  • the data anchor is the previous hop RN/homing base station directly connected to the source node and the target node through the air interface
  • the source node may feed back the RLC status report of the RN to the data anchor.
  • the source node may be an RN
  • the target node may be an RN or a host base station.
  • the target node is the same node as the data anchor.
  • the data anchor Since the data anchor needs to send the data that the terminal does not successfully receive to the target node, so that the target node sends the data to the RN, the data anchor needs to know the information of the target node, which can be based on the following manner: mode 1, the source node informs the data anchor Point, for example, by switching the preparation process, the source node negotiates with the target node in advance, and informs the data anchor point of the information of the target node; and second, the target node notifies the data anchor point, for example, when the RN is accessed by the target node, The target node notifies the data anchor so that the data anchor switches the RN's data path from the source node to the target node.
  • mode 1 the source node informs the data anchor Point, for example, by switching the preparation process, the source node negotiates with the target node in advance, and informs the data anchor point of the information of the target node; and second, the target node notifies the data anchor point, for example, when the RN
  • a status report for the data transmission status of the RN may be sent, for explicitly notifying the target node/data anchor that the data packet is not successfully received.
  • the RN By sending the status report to the data anchor by the RN itself, it is possible to prevent the data anchor from transmitting the data packet that the RN has successfully received but still has the acknowledgment (ACK) feedback to the target node; or, if the data anchor points the RN already A data packet that is successfully received but also has an acknowledgment (ACK) feedback in the future is sent to the target node, and the RN itself sends a status report to the target node, which can prevent the target node from successfully receiving the RN but still send an acknowledgment (ACK) in the future.
  • the feedback packet is sent to the RN.
  • the RN performs RRC connection re-establishment in the cell provided by the target node, and the original serving node learns that the RN has an RLF (for example, the target node notifies the original serving node that the RN has an RLF), and the original service
  • the node can forward the data of the RN to the target node.
  • the data anchor caches the data that needs to be forwarded
  • the original serving node of the RN may feed back the status report of the RN to the data anchor or the DRB status report of several RNs for the data anchor point to the target.
  • the node forwards data that has not been successfully sent to the RN.
  • the data anchor point is a common last hop or an upper n (n>1) hop RN of the original serving node and the target node, or a host base station common to the original serving node and the target node (for example, a PDCP peered with the terminal)
  • the PDCP PDU that the terminal did not successfully receive may also be cached on the donor base station).
  • the original serving node may feed back the RLC status report of the RN to the data anchor.
  • the original serving node may be an RN
  • the target node may be an RN or a donor base station.
  • the target node is the same node as the data anchor.
  • the data anchor Since the data anchor needs to send the data that the RN has not successfully received to the target node, so that the target node sends the data to the RN, the data anchor needs to know the information of the target node, which can be based on the following manner: mode 1, the original service node informs the data
  • the anchor point for example, the original service node configures the target node to the RN in advance, and informs the data anchor point of the information of the target node in advance;
  • the target node notifies the data anchor point, for example, when the RN is accessed by the target node, the target node
  • the data anchor is notified so that the data anchor switches the data path of the RN from the original serving node to the target node.
  • the RN may send a status report for the data transmission status of the RN, to explicitly notify the target node/data anchor that the data packet is not successfully received.
  • the hop upper hop node needs to route the received status report as the data of the node that sends the status report to the data. Anchor point.
  • UE3 accesses RN3, and performs data transmission with the base station through RN2 and RN1, and RN2 generates a status report of DRB of RN3 of the Un3 port.
  • the IAB function protocol layer entity of the RN2 peering with the RN3 generates the status report, and sends the status report to the IAB function layer entity of the RN2 peering with the RN1, so that the RN2 passes the Un2.
  • the port sends the status report to the RN1.
  • Another possible way is that the IAB function layer entity of the RN2 peering with the RN1 generates the status report.
  • the IAB function protocol layer entity of the RN2 peering with the RN3 will The transmission/reception status of the packet of the Un3 port informs the IA2 functional layer entity of the RN2 that is equivalent to the RN1.
  • the routing manner of the foregoing status report may be implemented in multiple manners.
  • the IAB function protocol layer entity is the per RN DRB, for example, the DRB1 and the DRB2 of one terminal are carried on the DRB1 of the RN3 of the Un3 port, but in the Un2 port, the DRB1 of the terminal is carried in the DRB1 of the RN2, and the DRB2 of the terminal is carried in the RN2.
  • the status report of DRB2 and RN2 transmitted on the Un2 port should be the feedback state of the DRB1 of the feedback terminal in the DRB1 of the RN2, and the DRB2 transmission state of the terminal is fed back in the DRB2 of the RN2.
  • the RN1 should transmit the transmission status of the terminal DRB carried in the RN1 DRB on its own DRB. That is, when the intermediate forwarding node forwards the status report, the status report needs to be reorganized, and the terminal DRB status report included in the status report is aggregated according to its own RN DRB, and the terminal DRB status carried in one RN DRB is aggregated into one. The status is reported and transmitted in the RN DRB.
  • the first data in the embodiment of the present application is a control plane message.
  • the F1-like interface can transmit an interface control plane message, similar to the F1AP, and is called an F1AP-like signaling procedure/message.
  • An optional way is that the F1AP-like signaling procedure and message are consistent with the F1AP or extended based on the F1AP. This enables direct reuse of existing interface processes and reduces standardization efforts.
  • F1AP-like messages can be classified into two categories: Common Message (or Non-UE-associated) and UE-related (UE associated) messages.
  • the logical F1-like connection may be identified using a combination of any one or more of the following: control plane transport layer information (if any), second indication information, and identification of the terminal on the F1-like interface ( UE F1-like ID), third indication information.
  • the control plane transport layer information is information carried by the transport layer protocol of the F1-like interface.
  • the control plane transport layer information includes: an IP address of the host base station system and/or an IP address of the RN.
  • the control plane transport layer information includes: the port number of the host base station system and/or the port number of the RN, the stream identifier of the SCTP (Stream Identifier), and the SCTP. Payload Protocol Identifier, etc.
  • control plane transport layer information may include any one of the following information or a combination of any of the following: the IP address of the host base station system, the IP address of the RN, the port number of the host base station system, the port number of the RN, SCTP Flow identification, as well as the PPI of SCTP.
  • the second indication information is used to indicate the RN that establishes the F1-like interface with the donor base station system.
  • the second indication information may be a UE identifier (for example, C-RNTI, S-TMSI, GUTI, etc.) when the RN is used as the UE, or when the RN is used as the UE, the last hop is
  • the assigned F1-like interface identifier (for example, the UE F1AP ID, or the UE F1AP-like ID) may also be an RN ID after the RN is accessed as the UE, and then converted from the UE mode to the RN mode (optional,
  • the RN ID can be configured for OAM, or assigned by the host base station system, or pre-configured).
  • the second indication information may have the same format as the DU identifier.
  • the second indication information may be a global identifier, which is composed of an RN local identifier and an RN hop count.
  • the RN local identifier may be allocated to a previous hop node of the RN (for example, a RN or a DU in a host base station system).
  • the third indication information is used to indicate an F1-like interface to distinguish logical F1-like connections of different RNs.
  • a terminal-related logical F1-like connection may be established between the RN and the host base station system for the terminal served by the RN.
  • the terminal related logic F1-like connection may use any one of the following information or a combination of any multiple to distinguish different terminals: fourth indication information for indicating the terminal, and identifier of the service node of the terminal.
  • the fourth indication information may be any one of the following information or a combination of any one of the following: a F1-like interface UE ID (UE F1AP-like ID), a C-RNTI, a cell ID, a context identifier (Context ID), and the like. Further optionally, the fourth indication information is a combination of the terminal identifier and the RN identifier.
  • the embodiment of the present application The RN is referred to as an RN serving the terminal, and the terminal is referred to as a terminal served by the RN.
  • the first data in the embodiment of the present application is an RRC message of the terminal.
  • the IAB function protocol layer After acquiring the RRC message of the terminal, the IAB function protocol layer sends a first message including an RRC message of the terminal and a type identifier corresponding to the RRC message.
  • the RRC message of the UE may be carried in the F1AP-like message, or may be directly transmitted through the IAB function protocol layer, for example, directly carried in the PDU of the IAB function protocol layer.
  • the foregoing first message may include a target identifier, where the target identifier is used to indicate a service node of the terminal.
  • the first communication device determines the target device of the control plane message or the user plane data according to the target identifier, thereby performing processing and/or forwarding.
  • the target identifier may be an identifier of a service node of the terminal or an IP address of a service node of the terminal.
  • the first message further includes sixth indication information, where the sixth indication information is used to indicate that the first data belongs to the terminal or the first data is related to the terminal.
  • the type identifier is used to indicate the type of the first data, such that the device receiving the first message described above can perform different processing based on the data type.
  • the IAB function protocol layer can be used to transmit any one or any combination of the following data types: F1AP-like control plane message (optional, further divided into public F1AP- Like control plane and UE related F1AP-like control plane message), terminal RRC message, user plane data, Uu interface status report, Un interface status report.
  • F1AP-like control plane message (optional, further divided into public F1AP- Like control plane and UE related F1AP-like control plane message)
  • terminal RRC message terminal RRC message
  • user plane data Uu interface status report
  • Un interface status report Un interface status report.
  • the user plane data, the control plane data, the RRC message, and the status report are all referred to as the first data.
  • the IBA function protocol layer compresses the first data or the first data according to the first preset compression algorithm.
  • Sub-information includes at least one of an IP header, an SCTP common header, and information other than the target information in the SCTP data block, where the target information is at least one of user data, a flow identifier, and a PPI; or includes an IP header, At least one of the UDP header and the information other than the TEID in the GTP header.
  • the host base station system/RN When the control plane protocol stack of the F1-like interface between the host base station system and the RN includes the transport layer protocol layer, the host base station system/RN generates the F1AP-like control plane message including the transport protocol layer information field, and transmits the same.
  • the protocol layer information field is compressed; when the host base station system/RN receives the F1AP-like control plane message, the transmission protocol layer information field is decompressed.
  • the above compression/decompression is performed by the DU.
  • Figure 16 shows the format of an existing SCTP/IP packet and the format of each field in the SCTP packet.
  • the fields carrying useful information include: source IP address, destination IP address, for IP addressing, source port number, destination port number, and flow identifier, which are used to distinguish public messages.
  • the UE related message the PPI is used to indicate the corresponding AP type (for example, S1AP is 18, NGAP is 60, and F1AP is 62).
  • the F1AP-like message body should be carried in the User Data field in Figure 16.
  • the information is static. If the intermediate forwarding node does not need to obtain the information it includes, it can be compressed.
  • compressing it specifically includes compressing it to zero, or deleting/stripping the compressed information; alternatively, the compressed information can be notified to the opposite end by other means, such as a control plane message.
  • decompressing includes restoring the compressed information; in another optional manner, the compressed information is not used by the peer end, and correspondingly, the peer end does not need to perform decompression processing.
  • the first sub-information of the first data is compressed.
  • the first sub-information may be an IP header (such as the IPv6 Header part in FIG. 16), or an IP header and an SCTP common header, or a part other than User Data in the IP header, the SCTP common header, and the SCTP data block; or The part of the IP header, the SCTP common header, and the SCTP data block except the User Data and the flow identifier; or the part other than the User Data, the flow identifier, and the PPI in the IP header, the SCTP common header, and the SCTP data block.
  • IP header such as the IPv6 Header part in FIG. 16
  • IP header and an SCTP common header or a part other than User Data in the IP header, the SCTP common header, and the SCTP data block
  • the part of the IP header, the SCTP common header, and the SCTP data block except the User Data and the flow identifier
  • the foregoing compression and decompression are performed by the two nodes of the F1-like interface (for example, the host base station and the RN that establish the interface), and the intermediate forwarding node (for example, the RN that relays the F1AP-like control plane message) ) No need to proceed.
  • the two nodes of the F1-like interface for example, the host base station and the RN that establish the interface
  • the intermediate forwarding node for example, the RN that relays the F1AP-like control plane message
  • the foregoing first preset compression algorithm is pre-configured (for example, protocol specification), or configured by a host base station system/Operation and Management (OAM).
  • the RN may be configured by the eNB to the RN through the RRC message of the RN, or may be configured to the RN during the establishment of the F1-like interface, or may be configured to the RN after the F1-like interface is established.
  • the host base station system sends a compression activation/deactivation indication to the RN, to indicate that the RN starts to use/stop using the compression function.
  • the compressed indication is carried in the data packet, and is used to indicate that the F1AP-like control plane message is compressed.
  • the above compression indication is 1 bit information, "1" is compressed, and "0" is uncompressed.
  • the foregoing compression indication is carried in the header of the IAB function protocol layer.
  • the IAB function protocol layer data packet of the F1AP-like control plane message carries a message identifier, which is used to distinguish the common message or the UE.
  • the IAB function protocol layer data packet carrying the F1AP-like control plane message carries an AP type, and is used to indicate that the corresponding AP type is F1AP-like. For example, if the F1AP-like protocol layer is the same as the F1AP protocol layer, when the eNB is composed of the CU-DU, the DU strips the transport protocol layer of the F1AP message received by the F1 interface, and only retains the F1AP message body.
  • the Un port is transmitted to the RN.
  • the DU receives the F1AP-like control plane message sent by the RN from the Un interface, it uses the F1AP message body transmitted on the F1 interface to add a transmission domain for transmission on the F1 interface. .
  • the user plane data bearer is transmitted in the user plane of the F1-like interface.
  • the F1-like interface user plane protocol stack includes a transport layer protocol layer (for example, GTP-U/UDP/IP)
  • the PDCP PDU of the terminal is carried in the GTP-U data packet.
  • the host base station system/RN When the host base station system/RN generates the user plane data including the information layer of the transport protocol layer, the transport protocol layer information field is compressed; when the host base station system/RN receives the user plane data, the transport protocol layer information field is performed. unzip.
  • the host base station system when it is composed of a CU and a DU, the above compression/decompression is performed by the DU.
  • Figure 19 shows the format of an existing GTP-U packet and the format of each field in the GTP-U datagram.
  • the fields of useful information carried by the GTP-U datagram include: source IP address, destination IP address, used for IP addressing, source port number, target port number, and TEID is used to identify a DRB of a UE.
  • the information is static. If the intermediate forwarding node does not need to obtain the information it includes, it can be compressed. In particular, compressing it specifically includes compressing it to zero, or deleting/stripping the compressed information; alternatively, the compressed information can be notified to the opposite end by other means, such as a control plane message.
  • decompressing includes restoring the compressed information; in another optional manner, the compressed information is not used by the peer end, and correspondingly, the peer end does not need to perform decompression processing.
  • the first sub-information of the first data is compressed.
  • the first sub-information may be an IP header, or an IP header and a UDP header, or a part other than the TEID in the IP header, the UDP header, and the GTP header; or a UDP header and a GTP header.
  • the F1AP-like user plane data includes the TEID or the first indication information.
  • the TEID carried by the F1-like user plane data packet corresponds to the TEID on the F1 interface, that is, for the DRB of the same UE, the same TEID is used when transmitting on the F1-like interface and transmitting on the F1 interface.
  • the host base station system is composed of the CU-DU
  • the DU strips the transport protocol layer domain of the GTP-U data packet received by the F1 interface, and only reserves the TEID and the PDCP PDU of the UE, and is used to transmit to the Un port.
  • RN similarly, when the DU receives the F1AP-like user plane data packet sent by the RN from the Un port, it uses the F1-U data packet transmitted on the F1 interface to add a transmission domain for transmission on the F1 interface.
  • the IAB functional protocol layer provides integrity protection and/or encryption for the transmitted first data (eg, for control plane messages, user plane data, status reports).
  • the downlink is securely protected by the PDCP layer peered with the terminal in the host base station system, and uplinked and protected by the PDCP layer of the terminal, so no further need is needed. safety protection.
  • the F1AP-like control plane message since it carries configuration information (such as cell configuration information, etc.) of the RN and the base station system, and configuration information related to the terminal (such as QoS information of the terminal, etc.), in order to prevent theft or Tampering requires security. Therefore, the F1AP-like control plane message can be secured by the IAB function protocol layer. Optionally, other data types can also be secured.
  • the specific implementation manner of the security protection may be encryption and/or integrity protection, that is, the IAB function protocol layer of the sending end encrypts and/or integrity protects data that needs to be secured, and the IAB function protocol layer of the receiving end is The data is decrypted and or integrity checked.
  • the sender and the receiver need to use the same encryption/integrity protection key and algorithm, and the encryption and integrity protection keys and algorithms may be the same or different.
  • the above security protection function may use the security protection function of the RN PDCP, that is, the encryption key and algorithm using the RN PDCP, and the integrity protection key. And algorithms to secure data that requires security protection.
  • Figure 17 shows the format of its first message.
  • Figure 18 shows the format of its first message.
  • the IAB functional protocol layer and the PDCP layer are independent protocol layers.
  • the IAB functional protocol layer is part of the RN RLC layer, for example as a sublayer of the RN RLC layer.
  • the data of the IAB function protocol layer is carried in the RN RLC PDU, for example, as the content part of the RLC PDU.
  • an IAB function protocol layer data indication to the RN RLC PDU (for example)
  • a bit indicator bit is used to indicate that the RN RLC PDU includes IAB function protocol layer data.
  • the IAB function protocol layer data indication may be included in the RLC header.
  • a in FIG. 20 shows the format of a data packet of the existing RLC layer
  • B shows the format of a data packet of the RLC layer in which the IAB function is integrated in the embodiment of the present application.
  • Oct in Fig. 20 represents a byte.
  • the IAB functional protocol layer can be placed in the PDCP layer. If the IAB function protocol layer is part of the RN PDCP layer, for example, it is a sublayer of the RN PDCP layer. At this time, the data of the IAB function protocol layer is carried in the RN PDCP PDU, for example, as a content part of the PDCP PDU. In order to enable the RN to read the PDCP PDU to identify the RN PDCP PDU carrying the IAB function protocol layer data, and further parse according to the data format of the IAB function protocol layer, the IAB function protocol layer data indication is added to the RN PDCP PDU.
  • the IAB function protocol layer data indication may be included in the PDCP header.
  • a in FIG. 21 shows the format of a data packet of the existing PDCP layer, and B shows the format of a data packet of the PDCP layer in which the IAB function is integrated in the embodiment of the present application.
  • MAC-1 in Figure 21 is the integrity protection check digit.
  • the embodiment of the present application adds an IAB function protocol layer to the protocol stack of the RN and the host base station system, and the IAB function protocol layer can implement the functions of the above 1-8.
  • the initial configuration of the IA and the IAB functional protocol layer of the host base station system is required.
  • FIG. 22 shows a flow of configuring an IAB function protocol layer in a scenario in which the RN 1 accesses the network.
  • the host base station system in the following process may be an independent host base station, or may be composed of a CU and a DU. If the host base station system is an independent host base station, the interaction between the CU and the DU in FIG. 22 is the internal interaction of the host base station system. It should be noted that whether the host base station system performs the CU-DU segmentation has no effect on the processing of the RN 1. Specifically, when the RN 1 sends a message to the host base station system, if the host base station system is composed of the CU and the DU, the DU receives the message sent by the RN 1 through an air interface (for example, the Un1 port), and further, the message may need to be sent. To the CU.
  • an air interface for example, the Un1 port
  • the RN 1 When the RN 1 receives a certain message sent by the host base station system, if the host base station system is composed of the CU and the DU, the message received by the RN 1 may be generated by the DU and sent to the RN 1 through the air interface, or generated by the CU, and It is sent to the DU through the F1 interface, and then processed by the DU and then sent to the RN 1 through the air interface.
  • the configuration method includes:
  • the host base station system is composed of a CU and a DU, an F1 interface is established between the DU and the CU, and the F1 interface is used to indicate whether each has the function of supporting the IAB function protocol layer.
  • This step exists if the host base station system consists of a CU and a DU.
  • the DU indicates to the CU through the F1AP message that it has the function of supporting the IAB function protocol layer.
  • the F1AP message includes information used to indicate that the DU has an IAB function protocol layer.
  • the CU is similar to the DU and will not be described in detail here.
  • the host base station system generates first configuration information related to the RN access network, and sends the first configuration information.
  • both the CU and the DU can provide services for the RN, for example, the DU supports the function of the IAB function protocol layer, and the host base station system composed of the CU and the DU can control the control plane of the RN.
  • the user plane data is routed to the core network node serving the RN, determining that the host base station system can provide services for the RN, and the host base station system generates the first configuration information.
  • the first configuration information may include an access control parameter used to indicate the RN, and may also include information related to the RN-specific radio resource configuration (eg, a random access resource, a PUCCH, and a signal for measurement). Configuration, measurement reporting configuration, etc.).
  • an access control parameter used to indicate the RN may also include information related to the RN-specific radio resource configuration (eg, a random access resource, a PUCCH, and a signal for measurement). Configuration, measurement reporting configuration, etc.).
  • the host base station system (for example, the DU) broadcasts the first configuration information through the air interface.
  • the first configuration information is a system message.
  • S2202 The RN 1 sends a message 1 to the host base station system to request access to the network.
  • the RN 1 may initiate a random access procedure and send a message 1 to request to establish an RRC connection (including a scenario of newly created, restored, and reconstructed).
  • the message 1 may include an RRC Connection Request message, an RRC Connection Resume Request message, or an RRC Connection Reestablishment Request message.
  • the RN 1 may further send an RN indication, so that the host base station system recognizes that it is not an ordinary terminal that requests to establish an RRC connection, but an RN.
  • the RN indication may be included in the MAC data packet for DU interpretation; or the RN 1 accesses using the RN-dedicated random access resource, so that the DU can identify that the random access is not an ordinary terminal, but an RN .
  • the DU sends an RRC message included in the message 1 to the CU through the F1 interface.
  • the device in the random access process identifies the device that initiates the access as an RN, instead of the normal terminal, it determines whether the RN is allowed to access. If the DU determines that the RN 1 is not allowed to access, the CU sends a notification message to the CU to notify the CU to reject the access of the RN 1, so that the CU sends an RRC message indicating that the access is denied to the RN 1. Optionally, the DU notifies the CU to reject the access of the RN 1 by using a display indication, or may implicitly indicate.
  • the DU does not determine whether to allow the access of the RN 1, after receiving the message 1, the RRC message of the RN 1 in the message 1 is forwarded to the CU through the F1 interface.
  • S2204 The host base station system sends a message 2 to the RN 1.
  • the message 2 is used to indicate whether the RN 1 is allowed to access.
  • the message 2 may include an RRC Connection Setup message, an RRC Connection Resume message, an RRC Connection Reestablishment message, an RRC Connection Reject message, and an RRC connection recovery.
  • RRC Connection Resume Reject message or RRC Connection Reestablishment Reject message may include an RRC Connection Resume message.
  • the CU receives the RRC message in the message 1 sent by the DU, and determines that the requesting access device is the RN, and then determines whether the RN 1 is allowed to access, thereby generating an indication of permission or rejection.
  • the RN 1 accesses the message 2 and sends the message 2 to the RN 1 through the DU.
  • the message 2 generated by the CU is used to indicate that the RN 1 is allowed to access.
  • the message 2 may include an RRC Connection Setup message, an RRC Connection Resume message, or an RRC Connection Reestablishment message.
  • the CU determines to deny access to the RN 1, the CU generates a message 2 indicating that the RN 1 access is denied.
  • the message 2 may include an RRC Connection Reject message, an RRC Connection Resume Reject message, or an RRC Connection Reestablishment Reject message.
  • the notification message sent by the DU may also be received, to indicate that the CU rejects the access of the RN 1, and the CU generates the message 2 for indicating that the RN 1 access is denied.
  • RN 1 sends message 3 to the donor base station system.
  • Message 3 is used to indicate that the RRC setup is complete.
  • the message 3 may include an RRC Connection Setup Complete message, an RRC Connection Resume Complete message, or an RRC Connection Reestablishment Complete message.
  • the message 3 further includes an identifier of the RN 1.
  • the message 3 here is only used to describe a certain message, which is different from the message 3 in the existing random access procedure.
  • the DU forwards the RRC message in the message 3 to the CU through the F1 interface.
  • the host base station system sends a message 4 including the second configuration information to the RN 1 to instruct the RN 1 to configure an IAB function protocol layer that is equivalent to the host base station system according to the second configuration information.
  • the second configuration information includes security configuration information and compression configuration information.
  • the message 4 further includes any one of the following information or a combination of any one of the following: a relay mode activation indication, an RB list, an RB PHY/MAC/RLC configuration, and a cell group configuration (cellgroupconfig) PDCP configuration of RB, QoS information of DRB.
  • a relay mode activation indication an RB list
  • an RB PHY/MAC/RLC configuration an RB PHY/MAC/RLC configuration
  • cell groupconfig cell group configuration
  • the PHY/MAC/RLC configuration of the RB is included in the cellgroupconfig, which also includes the common configuration of the access cell.
  • the message 4 may be an RRC Connection Reconfiguration (RRC Connection Reconfiguration) message or an RRC Reconfiguration (RRC Reconfiguration) message.
  • RRC Connection Reconfiguration RRC Connection Reconfiguration
  • RRC Reconfiguration RRC Reconfiguration
  • the CU sends a message 5 including the third configuration information to the DU through the F1 interface after receiving the RRC message in the message 3, and the third configuration information is used to indicate the completion of the DU.
  • the foregoing third configuration information includes any one of the following information or a combination of any one of the following: an anchor key, a control plane key, a user plane key, an encryption algorithm, an integrity protection algorithm, Key derived information (eg, hop count, counter), compression activation indication, compression zero indication, compressed domain indication, compression algorithm.
  • the message 5 may be an F1AP message, such as a UE context setup request message or a UE context modification request message.
  • the message 5 further includes: an RB list of the RN1 and QoS information corresponding to the DRB.
  • the RB list includes an RB identifier.
  • the QoS information corresponding to the DRB includes at least one of the following information: a DRB identifier, a QoS parameter of the DRB, and a QoS parameter of the QoS flow carried in the DRB.
  • the DU sends a message 6 including the fourth configuration information to the CU by using the F1 interface, where the message 6 is used to indicate the configuration parameter of the IAB function protocol layer of the RN 1 to the CU, so that the CU generates a corresponding configuration message (for example, an RRC message). ), the configuration message is used to send to RN 1.
  • the message 6 is used to indicate the configuration parameter of the IAB function protocol layer of the RN 1 to the CU, so that the CU generates a corresponding configuration message (for example, an RRC message).
  • the configuration message is used to send to RN 1.
  • the fourth configuration information includes any one of the following information or a combination of any one of the following: an anchor key, a control plane key, a user plane key, an encryption algorithm, an integrity protection algorithm, and a key derivation Information (eg, hop count, counter), compression activation indication, compression zero indication, compressed domain indication, compression algorithm.
  • the message 6 further includes at least one of the following information: an RB list of the RN1, a PHY/MAC/RLC configuration of the RB, and a cell group configuration (cellgroupconfig).
  • the following three ways of configuring the configuration parameters of the IAB function protocol layer in the RN 1 can be implemented by sending the message 5 and/or the message 6 between the CU and the DU:
  • the CU determines the configuration information of the IAB function protocol layer in the DU, and sends the configuration information to the DU through the message 5.
  • the second configuration information is the third configuration information.
  • the DU determines the configuration information of the IAB function protocol layer in the DU, and sends the configuration information to the CU through the message 6, so that the CU generates a corresponding RRC message, which is used to instruct the RN 1 to perform corresponding configuration.
  • the second configuration information is the foregoing fourth configuration information;
  • Manner 3 The CU determines the first sub-configuration information of the IAB function protocol layer in the DU (ie, the third configuration information), and sends the first sub-configuration information to the DU through the message 5; and/or the DU determines the second sub-configuration information.
  • the fourth configuration information is sent to the CU through the message 6; the host base station system (which may be a CU or a DU) obtains the second according to the first sub-configuration information and the second sub-configuration information. Configuration information.
  • the first sub-configuration information may be at least one of an anchor key, a secret key-derived information, and whether the compression is performed
  • the second sub-configuration information may be at least one of an encryption algorithm, an integrity protection algorithm, and a compression algorithm.
  • the CU For mode one and mode three, the CU needs to obtain the capability information of the RN 1 (for example, whether the supported encryption algorithm/integrity protection algorithm/compression algorithm). For mode 2 and mode 3, the DU needs to obtain the capability information of the RN 1.
  • the foregoing capability information may be sent by the RN 1 to the CU through an RRC message, or may be sent by the core network to the CU through an interface between the core network and the base station, such as an NG interface.
  • the CU After acquiring the capability information of the RN 1, the CU sends the capability information of the RN 1 to the DU through the F1 interface.
  • the RN 1 configures an IAB function protocol layer of the RN 1 according to the second configuration information.
  • the RN 1 sends a message 7 to the host base station system for requesting to establish an F1-like interface.
  • the method for the RN 1 to configure the IAB function protocol layer of the RN 1 according to the second configuration information is:
  • message 7 is an RRC message.
  • the DU does not parse the message 7, but sends the message 7 to the CU over the F1 interface.
  • the CU After receiving the message 7, the CU establishes a corresponding F1 interface for the F1-like interface of the RN 1, and notifies the DU to establish a transmission channel of the Uu interface with the RN 1 for the F1-like interface.
  • message 7 is an IAB functional protocol layer/MAC layer/RLC layer/PHY layer message.
  • the DU parses the message 7 to establish a transmission channel for the Uu port with the RN 1 for the F1-like interface.
  • the DU establishes a transmission channel of the Uu interface between the F1-like interface and the RN 1 to allocate a radio resource, such as SRB, DRB, RLC-bearer, etc., for transmitting the F1-like interface message.
  • a radio resource such as SRB, DRB, RLC-bearer, etc.
  • the DU requests the CU to establish a corresponding F1 interface for the F1-like interface.
  • the CU establishes a corresponding F1 interface for the F1-like interface, and the CU considers the RN 1 as a DU, and establishes an F1 interface between the CU and the DU for the RN 1, and the DU is responsible for the F1 interface.
  • the message is forwarded to the CU or RN 1.
  • the RN 1 starts the base station mode, so that the RN 1 can send a system message or receive a random access request (Random Access Preamble) message of other nodes.
  • a random access request Random Access Preamble
  • the RRC message related to the embodiment of the present application is an RRC message defined by the LTE.
  • the application is also applicable to messages defined in other systems that are different from the RRC message name but have the same function or similar functions.
  • the steps in this embodiment can also be used separately.
  • the S2200-S2201 is optional, and the implementation of the solution does not depend on the foregoing two steps; the S2202-S2206 is used to perform the admission determination of the RN by the host base station system, especially when the host base station system is composed of the CU-DU.
  • the CU and the DU may be required to jointly perform an admission decision on the RN; the S2207-S2208 is used by the host base station to perform the IAB function configuration on the RN1, especially when the host base station system is composed of the CU and the DU, the foregoing configuration needs to be performed by the CU and the DU.
  • the S2202-S2206 and S2207-S2208 can be applied as two separate processes.
  • FIG. 23 shows a flow of configuring an IAB function protocol layer in a scenario where a node 2 (terminal or RN 2) accesses a network through the RN 1.
  • the configuration method includes:
  • RN 1 sends an RRC message in message 1 to the donor base station system.
  • the RN 1 sends the RRC message in the message 1 to the host base station system in an IAB function protocol layer message.
  • the RN 1 determines, in the random access process, that the device that initiates the access is an RN, instead of the normal terminal, determines whether the node 2 is allowed to access, and if the RN 1 determines that the node 2 is not allowed to access, the RN 1 passes The F1-like interface sends a notification message to the host base station system for notifying the access of the deny node 2, so that the host base station system sends an RRC message indicating the denial of access to the node 2.
  • the RN 1 notifies the host base station system that the access of the node 2 is denied by using a display indication or an implicit indication.
  • the host base station system is composed of a CU and a DU
  • the DU sends the RRC message that it receives to the CU through the F1 interface.
  • S2302 can refer to the description of S2203 above, and details are not described herein again.
  • the host base station system sends a message 8 to the node 2.
  • the message 8 is used to indicate whether the node 2 is allowed to access.
  • the message 8 may include an RRC Connection Setup message, an RRC Connection Resume message, an RRC Connection Reestablishment message, an RRC Connection Reject message, and an RRC connection recovery.
  • RRC Connection Resume Reject message or RRC Connection Reestablishment Reject message may include an RRC Connection Resume message.
  • the CU determines whether the requesting access device is the RN, and then determines whether the node 2 is allowed to access, thereby generating an indication to allow or deny the node 2 to access.
  • Message 8 send message 8 to node 2 via DU and RN 2.
  • the CU sends the RRC message in the message 8 to the DU through the F1 interface, and the DU forwards the RRC message in the message 8 to the RN 1, and the RN1 sends the RRC message in the message 8 to the node 2.
  • the message 8 generated by the CU is used to indicate that the node 2 is allowed to access.
  • the message 8 may include an RRC Connection Setup message, an RRC Connection Resume message, or an RRC Connection Reestablishment message.
  • the CU determines to deny access to node 2
  • the CU If the CU determines to deny access to node 2, the CU generates a message 8 indicating that access to node 2 is denied.
  • the message 8 may include an RRC Connection Reject message, an RRC Connection Resume Reject message, or an RRC Connection Reestablishment Reject message.
  • the node 2 sends a message 9 to the RN 1/host base station system.
  • Message 9 is used to indicate that the RRC setup is complete.
  • the message 9 may include an RRC Connection Setup Complete message, an RRC Connection Resume Complete message, or an RRC Connection Reestablishment Complete message.
  • the message 9 further includes an identifier of the RN, where the device that sends the message is an RN, which is not an ordinary terminal.
  • RN 1 sends an RRC message in message 9 to the donor base station system.
  • RRC message 9 For the process of the RN 1 transmitting the RRC message in the message 9 to the host base station system, reference may be made to the foregoing S2205, and details are not described herein again.
  • the DU forwards the RRC message in the message 9 to the CU through the F1 interface.
  • the host base station system sends a message 10 including the fifth configuration information and/or the sixth configuration information to the RN 1 to instruct the RN 1 to perform configuration according to the fifth configuration information and/or the sixth configuration information.
  • the host base station system is composed of the CU and the DU
  • the node 2 is the RN 2
  • the CU after receiving the RRC message in the message 9, the CU sends the seventh configuration information to the DU through the F1 interface.
  • the seven configuration information is used to instruct the DU to perform the configuration of the IAB function protocol layer corresponding to the node 2.
  • the seventh configuration information includes any one of the following information related to the node 2 or a combination of any one of the following: security configuration information, compression configuration information, and capability information.
  • security configuration information any one of the following information related to the node 2 or a combination of any one of the following: security configuration information, compression configuration information, and capability information.
  • capability information any one of the following: security configuration information, compression configuration information, and capability information.
  • the host base station system is composed of the CU and the DU
  • the CU after receiving the RRC message in the message 9, the CU sends the fifth configuration information to the DU through the F1 interface, where the CU sends the fifth configuration information to the DU.
  • the fifth configuration information is used to instruct the RN 1 to perform configuration of the IAB function protocol layer corresponding to the node 2.
  • the fifth configuration information includes any one of the following information related to the node 2 or a combination of any one of the following: security configuration information, compression configuration information, and capability information.
  • the foregoing fifth configuration information and the seventh configuration information may be included in different messages, for example, the fifth configuration information is included in the message 11, and the seventh configuration information is included in the message 12.
  • the above message 11 may be included in the message 12.
  • the fifth configuration information is the same as the seventh configuration information, or the fifth configuration information is a subset of the seventh configuration information.
  • the message 12 may only contain the seventh configuration information.
  • the CU may further send the eighth configuration information to the DU, where the eighth configuration information is used to indicate the QoS information of the node 2 to the DU, so that the DU is based on the bearer in the RN.
  • the QoS requirement of the data of the node 2 in the DRB of 1 is adjusted and updated for the PHY/MAC/RLC configuration of the DRB of the RN 1, thereby triggering the CU to send an RRC reconfiguration message to the RN 1 for reconfiguration.
  • the CU determines how the data of the node 2 is mapped into the DRB of the RN 1, and sends the QoS requirement of the data of the node 2 (for example, the QoS parameter of the DRB or the QoS parameter of the QoS flow).
  • the DU it is convenient for the DU to decide whether it is necessary to update the PHY/MAC/RLC configuration of the DRB of the RN1 carrying the data of the node 2.
  • the eighth configuration information includes any one of the following information or a combination of any one of the following: an RB list of the node 2, QoS information corresponding to the DRB of the node 2, a correspondence between the DRB of the node 2 and the DRB of the RN 1, and the node 2
  • the QoS flow list includes a QoS flow identifier (QFI for short) and/or a DRB identifier for node 2.
  • the CU may further send sixth configuration information to the DU, where used to indicate the QoS information of the node 2 to the RN 1.
  • the sixth configuration information includes any one of the following information or a combination of any one of: an RB list of the node 2 and QoS information corresponding to the DRB of the node 2.
  • the sixth configuration information may be included in the message 11/message 12 described above.
  • the sixth configuration information is a subset of the eighth configuration information.
  • the CU sends the eighth configuration information to the DU, and the DU generates the sixth configuration information based on the eighth configuration information.
  • the above message 11/message 12 may be an F1AP message, or may be a UE context setup request or a UE context modification request message.
  • the UE/RN F1AP ID included in the message 12 is used to determine the RN 1 And can be used to indicate that the DU performs the configuration of the air interface with the RN 1; the UE/RN F1AP ID included in the message 11 is used to determine the node 2, and can be used to instruct the DU to perform the configuration of the air interface corresponding to the node 2, and/or
  • the configuration information is forwarded to the RN 1, and the RN 1 performs the configuration of the air interface with the node 2.
  • the sixth configuration information and the eighth configuration information both contain QoS information of the data of the node 2, and the two may not be identical.
  • the base station system for example, CU and/or DU
  • the delay requirement B and the bearer in the UE DRB are required to meet the delay requirement C, and the delay requirement B is included in the seventh configuration information, and the delay requirement C is included in the eighth configuration information.
  • the CU does not need to send the fifth configuration information and the seventh configuration information to the DU.
  • the node 2 is an RN and the IAB function protocol layer is hop-by-hop, the DU does not need to perform the configuration of the IAB function protocol layer corresponding to the node 2, and the RN 1 needs to perform the configuration of the IAB function protocol layer corresponding to the node 2, that is, the CU. There is no need to send the seventh configuration information, but the fifth configuration information needs to be sent.
  • the RN 1 does not need to process the above message (for example, security protection/encryption), therefore, the CU does not need to send the fifth configuration information.
  • the RN 1 does not need to process the above message (for example, security protection/encryption), therefore, the CU does not need to send the fifth configuration information.
  • the DU acquires the foregoing fifth configuration information and/or the sixth configuration information based on the message 11 to generate the message 10; or the DU receives the message 12 and processes the message 12 (for example, replacing the UE/RN F1AP ID of the F1 interface. Instructing the identity of the node 2 on the F1-like interface, compressing all or part of the information in the message 12, and protecting all or part of the information in the message 12, that is, the message according to the encryption algorithm and/or the integrity protection algorithm. All or part of the information in 12).
  • the RN 1 performs the configuration of the IAB functional protocol layer peered with the node 2 according to the message 10, and sends the configuration to the host base station system.
  • the message 13 of the configuration information is used to indicate the configuration parameters related to the node 2 of the host base station system, so that the host base station system generates a corresponding configuration message (for example, an RRC message) and sends it to the RN 1.
  • the ninth configuration information includes any one of the following information or a combination of any of the following: security configuration information, compression configuration information, RB list of the node 2, and PHY/MAC/RLC configuration corresponding to the RB.
  • the message 13 may be an F1AP-like message, or may be a message similar to a UE context setup response or a UE context modification response.
  • the DU sends a message 14 including the tenth configuration information to the CU, and indicates a configuration parameter related to the CU and is used by the CU to generate a corresponding configuration message (for example, an RRC message). ) and sent to node 2.
  • the tenth configuration information includes any one of the following information or a combination of any one of the following: security configuration information, compression configuration information, RB list of node 2, and PHY/MAC/RLC configuration corresponding to the RB.
  • the DU sends the eleventh configuration information to the CU, where the eleventh configuration information includes any one of the following information or a combination of any one of the following: the RB list of the RN1 and the PHY/MAC/RLC configuration corresponding to the RB And indicating that the CU generates a reconfiguration to message sent to the RN 1, and changes the configuration of the RB of the RN1.
  • the eleventh configuration information may be included in the message 13 or the message 14.
  • the message 13/message 14 may be an F1AP message, or may be a UE context setup response message or a UE context modification response message.
  • the UE/RN F1AP ID in the message 13 is used to determine the node 2 for indicating the configuration information related to the CU
  • the UE/RN F1AP ID in the message 14 is used to determine the RN 1 for indicating the CU and Configuration information related to RN 1.
  • the node 2 When the node 2 is an RN, the node 2 needs to be configured with an IAB function protocol layer, for which the security configuration and/or compression configuration can be determined by the CU (the end-to-end architecture is applied, and the CU is a centralized decision anchor point), or the DU determines (Applicable end-to-end architecture), or the CU negotiates with the DU, or is determined by the RN 1 (applicable to the hop-by-hop architecture), or the CU negotiates with the RN 1, or the DU negotiates with the RN 1, or the CU, DU, and RN 1 negotiates the decision together.
  • the CU the end-to-end architecture is applied, and the CU is a centralized decision anchor point
  • the DU determines (Applicable end-to-end architecture)
  • the CU negotiates with the DU, or is determined by the RN 1 (applicable to the hop-by-hop architecture)
  • the CU negotiates with the RN 1
  • the key can be determined by the CU or DU, and the algorithm can be determined by RN 1.
  • the foregoing security configuration and/or compression configuration manner can be implemented by sending the message 10, the message 11, the message 12, the message 13, and the message 14 between the CU, the DU, and the RN 1.
  • the sequence of sending specific configuration information may be performed in multiple manners, for example, according to the sequence described in the foregoing steps, or the DU first sends the tenth.
  • the configuration information is sent to the CU
  • the fifth configuration information/the sixth configuration information is sent to the RN 1.
  • the embodiment of the present application does not specifically limit this.
  • the host base station system sends a message 15 to the RN 1.
  • the message 15 includes a combination of one or more of the following: configuration of an IAB functional protocol layer corresponding to node 2 (eg, security configuration information, compression configuration information), RB list of RN 1, PHY/MAC/ of RB RLC configuration, PDCP configuration of RB, QoS information of DRB.
  • configuration of an IAB functional protocol layer corresponding to node 2 eg, security configuration information, compression configuration information
  • RB list of RN 1 e.g, PHY/MAC/ of RB RLC configuration
  • PDCP configuration of RB e.g., QoS information of DRB.
  • the message 15 may include an RRC Connection Reconfiguration or RRC Reconfiguration message.
  • the RN 1 after receiving the foregoing message, applies the new configuration and replies to the response message of the configuration completion.
  • the host base station system sends a message 16 to the node 2.
  • the message 16 contains a combination of one or more of the following: the configuration of the IAB functional protocol layer (if the node 2 is the RN, the cell appears, otherwise it does not appear), the RN mode activation indication (if the node 2 is the RN) Then, the cell appears, otherwise it does not appear), the RB list of the node 2, the PHY/MAC/RLC configuration of the RB, the PDCP configuration of the RB, and the QoS information of the DRB.
  • the message 16 may be an RRC Connection Reconfiguration or RRC Reconfiguration message.
  • the node 2 after receiving the foregoing message, applies the new configuration and replies to the response message of the configuration completion.
  • S2309 may be executed first, and then S2310 may be executed.
  • S2310 may be executed first, and then S2309 is executed. This embodiment of the present application does not specifically limit this.
  • the node 2 if the node 2 is the RN 2, the node 2 sends a message 17 to the RN 1 for requesting to establish an F1-like interface.
  • the RN 1 does not parse the message 17, but sends the message 17 to the host base station system via the F1-like interface.
  • the host base station system is similar to the processing of the message 7 in the embodiment shown in FIG. 22, that is, the DU is sent to the CU through the F1 interface, and after receiving the message 17, the CU establishes a corresponding F1 interface for the F1-like interface, and Let the DU establish a transmission channel with the Uu port between the RN 1 and the F1-like interface.
  • the RN 1 parses the message 17, thereby establishing a transmission channel for the Uu port with the node 2 for the F1-like interface, optionally, the DU request.
  • the CU establishes a corresponding F1 interface for the F1-like interface.
  • the DU establishes a transmission channel of the Uu interface between the F1-like interface and the RN 1 , and allocates a radio resource, such as SRB, DRB, RLC-bearer, etc., for transmitting the F1-like interface message.
  • the CU establishes a corresponding F1 interface for the F1-like interface, where the CU considers the RN1 as a DU, and establishes an F1 interface between the CU and the DU for the RN1, and the DU is responsible for forwarding the message on the F1 interface.
  • CU or RN 1 the CU considers the RN1 as a DU, and establishes an F1 interface between the CU and the DU for the RN1, and the DU is responsible for forwarding the message on the F1 interface.
  • the node 2 turns on the base station mode, so that the node 2 can send a system message or receive a random access request (Random Access Preamble) message of other nodes.
  • a random access request Random Access Preamble
  • the steps in this embodiment can also be used separately.
  • the S2300-S2305 is used for performing admission control of the access of the RN by the host base station system/RN1, especially when the host base station system is composed of CU-DUs, and the CU and the DU may be required to jointly perform the admission determination on the node 2.
  • S2306-S2311 is used by the host base station to configure the node 2, especially when the host base station system is composed of the CU and the DU and the node 2 is the RN, the foregoing configuration needs to be jointly performed by the CU and the DU, and further, the DU is required to be / or configuration of the IAB functional layer peering with node 2 at RN1. Therefore, the S2300-S2305 and S2306-S2311 can be applied as two separate processes.
  • FIG. 24 shows a flow of configuring the IAB function protocol layer in the scenario where the node 2 is the RN 2 and the terminal accesses the network through the RN 2 and the RN 1.
  • the configuration method includes:
  • S2400 The terminal establishes an RRC connection with the host base station system through the RN 2 and the RN 1.
  • the terminal sends a message 3 to the RN 2, and the RN 2 sends the RRC message included in the message 3 to the RN 1, and the RN 1 sends the RRC message to the host base station system.
  • the CU sends the first configuration information to the DU, and is used to notify the DU of the QoS information related to the UE, so that the DU can update the RN according to the QoS requirement of the terminal.
  • PHY/MAC/RLC configuration of the DRB PHY/MAC/RLC configuration of the DRB.
  • the DU adjusts and updates the PHY/MAC/RLC configuration of the DRB of the RN 1 according to the QoS requirements of the data of the terminal carried in the DRB of the RN 1, thereby triggering the CU to send an RRC reconfiguration to the message to the RN 1 for reconfiguration.
  • the CU determines how the data of the terminal is mapped into the DRB of the RN 1, and sends the QoS requirement of the data of the terminal (for example, the QoS parameter of the DRB or the QoS parameter of the QoS flow).
  • the DU it is convenient for the DU to determine whether it is necessary to update the PHY/MAC/RLC configuration of the DRB of the RN 1 carrying the data of the above terminal.
  • the first configuration information includes any one of the following information or a combination of any one of the following: an RB list of the terminal, QoS information corresponding to the DRB of the terminal, a correspondence between the DRB of the terminal and the DRB of the RN 1, and a QoS flow list of the terminal, The QoS information corresponding to the QoS flow of the terminal, the correspondence between the QoS flow of the terminal and the DRB of the RN 1.
  • the CU sends the second configuration information to the DU through the F1 interface, and is used to indicate the QoS information of the RN 1 terminal, so that the RN 1 can update the PHY/MAC/RLC configuration of the RN 2 DRB according to the QoS requirement of the terminal.
  • the RN 1 adjusts and updates the PHY/MAC/RLC configuration of the DRB of the RN 2 according to the QoS requirement of the data of the terminal carried in the DRB of the RN 2, thereby triggering the CU to issue an RRC reconfiguration to the message to the RN 2 for reconfiguration.
  • the CU determines how the data of the terminal is mapped into the DRB of the RN 2, and sends the QoS requirement of the data of the terminal (for example, the QoS parameter of the DRB or the QoS parameter of the QoS flow) to DU, the DU is forwarded to the RN 1, and the RN 1 determines whether it is necessary to update the PHY/MAC/RLC configuration of the DRB of the RN 2 carrying the data of the above terminal.
  • the second configuration information includes any one of the following information or a combination of any one of the following: an RB list of the terminal, QoS information corresponding to the DRB of the terminal, a correspondence between the DRB of the terminal and the DRB of the RN 2, and a QoS flow list of the terminal, The QoS information corresponding to the QoS flow of the terminal, the correspondence between the QoS flow of the terminal and the DRB of the RN 2.
  • the CU sends the third configuration information to the DU through the F1 interface, and is used to indicate the QoS information of the RN 2 terminal, so that the RN 2 provides the PHY/MAC/RLC configuration parameter of the UE DRB according to the QoS requirement of the terminal, so that the CU can
  • the configuration parameters are sent to the UE through RRC reconfiguration to the message.
  • the CU determines how the data of the terminal is mapped to the DRB of the terminal, and sends the QoS requirement of the data of the terminal (for example, the QoS parameter of the DRB or the QoS parameter of the QoS flow) to the DU.
  • the DU is forwarded to the RN 1, and further forwarded by the RN 1 to the RN 2, and the RN 2 determines whether it is necessary to update the PHY/MAC/RLC configuration of the DRB of the RN 2 carrying the data of the terminal.
  • the third configuration information includes any one of the following information or a combination of any one of the following: an RB list of the terminal, QoS information corresponding to the DRB of the terminal, a QoS flow list of the terminal, and QoS information corresponding to the QoS flow of the terminal.
  • the first configuration information, the second configuration information, and the third configuration information may be included in the first message, the second message, and the third message, respectively.
  • the first message, the second message, and the third message in this embodiment may be an F1AP message, where the UE/RN F1AP ID may be used to determine the RN 1, the RN 2, and the terminal, respectively, for determining, by the DU, that the first message is parsed. And updating the RN 1 DRB configuration based on the first configuration information therein.
  • the DU forwards it to the RN 1 for processing.
  • the DU forwards it to the RN 1, so that the RN 1 forwards the packet to the RN 2 for processing.
  • the first configuration information, the second configuration information, and the third configuration information may be located in the first message, and after receiving the first message, the DU applies the first configuration information, and sends the second configuration information and the third configuration information.
  • the DU applies the first configuration information, and sends the second configuration information and the third configuration information.
  • the second configuration information and/or the third configuration information may be a subset of the first configuration information, and the DU obtains the second configuration information and/or the third configuration information based on the first configuration information.
  • the first message/second message/third message may be a UE context setup request message or a UE context modification request message.
  • the first configuration information, the second configuration information, and the third configuration information all include QoS requirements of the data of the terminal, and the three may not be identical.
  • the host base station system for example, CU and/or DU
  • the host base station system may further decompose it into a bearer in the RN 1 DRB for transmission.
  • the delay requirement B is required, the delay required to be transmitted in the RN 2 DRB is required to be satisfied, and the delay requirement D to be transmitted in the UE DRB is required, and the delay requirement B is included in the first configuration.
  • the delay requirement C is included in the second configuration information, and the delay requirement D is included in the third configuration message.
  • the host base station system sends the second configuration information and the third configuration information to the RN1, so that the RN1 parses the second configuration information to determine whether to change the configuration of the RN2 DRB. If the configuration of the RN 2 DRB needs to be changed, the RN 1 communicates with the host base station system to facilitate the host base station system to send the new configuration to the RN 2 through the RN 1.
  • the second configuration information and the third configuration information may be included in the fourth message and the fifth message, respectively.
  • the fourth message and the fifth message may be F1AP-like messages, where the carried UE/RN ID is used to identify the RN 2 and the UE, respectively, and the RN 1 may be informed that the second configuration information is related to the RN 2 The configuration is analyzed and processed, so that the RN 1 knows that the third configuration information is related to the UE and needs to be forwarded to the RN 2 for processing.
  • the foregoing second configuration information and the third configuration information may be included in the fourth message, and the RN 1 obtains the third configuration information from the fourth message, and sends the configuration information to the RN 2.
  • the third configuration information is included in the second configuration information, and the RN 1 obtains the third configuration information by using the second configuration information.
  • the RN 1 sends the third configuration information to the RN 2, and the RN 2 determines the PHY/MAC/RLC configuration parameter of the DRB of the terminal based on the third configuration information.
  • the third configuration information is included in an F1AP-like message, where the carried UE ID is used to identify the UE, and the RN 2 can learn that the third configuration information is related to the UE it serves, and parses and processes the UE. .
  • the RN 2 sends the fourth configuration information to the RN 1, where the RB list of the terminal and the PHY/MAC/RLC configuration corresponding to the RB are included.
  • the fourth configuration information may be included in an F1AP-like message similar to a UE Context setup response or a UE context modification response message.
  • the RN 1 sends the fourth configuration information sent by the RN 2 to the host base station system.
  • the RN 1 further sends a fifth configuration information to the host base station system, where the RB list carrying the RN 2 and the PHY/MAC/RLC configuration corresponding to the RB are used to enable the host base station system to configure the updated RB by using the RN 1 Send to RN 2.
  • the foregoing fourth configuration information and the fifth configuration information may include different messages, for example, a sixth message and a seventh message.
  • the sixth message and the seventh message may be F1AP-like messages, where the carried UE/RN ID is used to determine the UE and the RN 2, and the host base station system learns that the two types of configuration information are respectively sent to the terminal and RN 2.
  • the fourth configuration information and the fifth configuration information may also be included in the same message, such as the sixth message.
  • the sixth message/seventh message may be an F1AP-like message, and further, may be an F1AP- similar to a UE context setup response or a UE context modification response message. Like message.
  • the DU sends the fourth configuration information and/or the fifth configuration information to the CU.
  • the DU sends the sixth configuration information to the CU, where the RB list of the RN 1 and the PHY/MAC/RLC configuration corresponding to the RB are used to enable the CU to send the updated RB configuration to the RN 1.
  • the foregoing fourth configuration information, the fifth configuration information, and the sixth configuration information may be included in different messages, such as an eighth message, a ninth message, and a tenth message.
  • the eighth message, the ninth message, and the tenth message may be an F1AP message, where the carried UE/RN F1AP ID is used to determine the UE, the RN 2, and the RN 1, and the host base station system learns that the foregoing configuration information is respectively Sent to the UE, RN 2 and RN 1.
  • the fourth configuration information, the fifth configuration information, and the sixth configuration information may also be included in the same message, for example, the eighth message.
  • the eighth message, the ninth message, and the tenth message may be F1AP-like messages similar to a UE context setup response or a UE context modification response message.
  • the host base station system sends the eleventh message to the terminal based on the fourth configuration information.
  • the eleventh message includes any one or a combination of any of the following: an RB list of the terminal, a PHY/MAC/RLC configuration of the RB, a PDCP configuration of the RB, and QoS information of the DRB.
  • the eleventh message is an RRC message, and further may be an RRC Connection Reconfiguration or an RRC Reconfiguration (RRC Reconfiguration) message.
  • the terminal after receiving the foregoing message, applies the new configuration, and responds to the response message of the configuration completion.
  • the foregoing eleventh message needs to be sent by the host base station system to the RN 1, and is sent by the RN 1 to the RN 2, and then sent by the RN 2 to the terminal.
  • the process is the same as the RRC message sent by the host base station system to the terminal, and details are not described herein.
  • the response message replied by the terminal needs to be received by the RN 2 and then sent to the RN 1, and sent by the RN 1 to the host base station system, and details are not described herein again.
  • the host base station system sends the twelfth message to the RN 2 based on the fifth configuration information.
  • the twelfth message includes any one or a combination of any of the following: an RB list of the RN 2, a PHY/MAC/RLC configuration of the RB, a PDCP configuration of the RB, and QoS information of the DRB.
  • the twelfth message is an RRC message, and further may be an RRC Connection Reconfiguration or an RRC Reconfiguration (RRC Reconfiguration) message.
  • the RN 2 After receiving the foregoing message, the RN 2 applies the new configuration and replies to the response message of the configuration completion.
  • the twelfth message needs to be sent by the eNB to the RN 1 and sent by the RN 1 to the RN 2.
  • the process is the same as the RRC message sent by the eNB to the RN 2, and details are not described herein.
  • the response message replied by the RN 2 needs to be sent by the RN 1 to the host base station system, and details are not described herein.
  • the host base station system sends the thirteenth message to the RN 1 based on the seventh configuration information.
  • the thirteenth message includes any one or a combination of any of the following: an RB list of RN 1, a PHY/MAC/RLC configuration of the RB, a PDCP configuration of the RB, and QoS information of the DRB.
  • the thirteenth message is an RRC message, and may further be an RRC Connection Reconfiguration or an RRC Reconfiguration (RRC Reconfiguration) message.
  • the RN 1 after receiving the foregoing message, applies the new configuration and replies to the response message of the configuration completion.
  • the thirteenth message needs to be sent by the CU of the host base station system to the DU, and the DU is sent to the RN 1, and the process is the same as the RRC message sent by the host base station system to the RN1. This will not be repeated here.
  • the response message replied by the RN 1 needs to be sent by the DU to the CU, and is not described here.
  • the order of execution of S2407, S2408, and S2409 is not limited in the embodiment of the present application.
  • the present application does not limit the order in which the specific configuration information is sent in the S2400-S2406 step. For example, it can be performed in the order described in the above steps.
  • the DU first sends the sixth configuration information to the CU, and then sends the second configuration information/third configuration information to the RN1; the RN1 first sends the fifth configuration information to the DU, and then sends the third configuration information to the RN2.
  • the above RN 1 is equivalent to the RN 71 in FIG. 7, and the RN 2 is equivalent to the RN 72 in FIG.
  • each node in the communication system can transmit data based on the respective IAB function protocol layer.
  • the data transmission method provided by the embodiment of the present application includes:
  • the first communications device acquires the first data.
  • the first communications device sends a first message including the type identifier and the first data to the second communications device.
  • the first communication device is an intermediate forwarding node, a serving node of the terminal, a donor base station, or a DU in the host base station system.
  • the second communication device is a previous hop device or a next hop device of the intermediate forwarding node.
  • the first communication device is the RN 71 and the second communication device is the RN 72 or the DU 730.
  • the second communication device is the last hop device of the service node of the terminal.
  • the first communication device is the RN 72 and the second communication device is the RN 71.
  • the second communication device is a next hop device of the first communication device.
  • the types of the first data are user plane data, status reports, control plane messages, and RRC messages of the terminal.
  • the first message includes the first indication information and the global SN of the user plane data.
  • the first data is a status report
  • the first data includes a global SN of the user plane data carried by the DRB of the terminal
  • the first data is used to indicate the transmission status of the DRB data packet of the third communication device
  • the third communication device is the terminal and the middle. Forward the node or the service node of the terminal.
  • the first data is a control plane message
  • the first message includes at least one of the transport layer protocol layer information of the first interface, the second indication information, the identifier of the terminal at the first interface, and the third indication information.
  • the first interface is a logical communication interface between the first communication device and the second communication device, that is, the F1-like interface described above.
  • a logical communication interface is the opposite of a physical interface.
  • a physical interface can refer to an air interface, such as an Un interface.
  • the transport layer protocol layer information of the first interface includes an IP address of the first communication device, an IP address of the second communication device, an IP address of the host base station or the DU, a port number of the first communication device, a port number of the second communication device, At least one of a port number of the host base station or the DU, a flow identifier of the SCTP, and a PPI of the SCTP, where the second indication information is used to indicate the first communication device, and the third indication information is used to indicate the first interface; or the first message includes And at least one of the fourth indication information and the identifier of the service node of the terminal, where the fourth indication information is used to indicate the terminal.
  • the first data when the first data is a status report, the first data is further included in the fifth indication information indicating the DRB of the terminal. If the third communication device is an intermediate forwarding node or a serving node of the terminal, the first data specifically includes fifth indication information carried by each DRB in the at least one DRB of the third communication device.
  • the first message in the embodiment of the present application further includes at least one of a target identifier and sixth indication information for indicating the terminal, regardless of whether the first data is similar to the foregoing.
  • the target identifier is used to indicate the service node of the terminal.
  • the first indication information the second indication information, the third indication information, the fourth indication information, the fifth indication information, and the sixth indication information, refer to the foregoing description, and details are not described herein again.
  • the method for the first communications device to obtain the first data is: the first communications device receives the first a second message of the second data, the second data includes seventh indication information, where the seventh indication information is used to indicate the DRB of the terminal or the terminal; the first communication device acquires the second data, and replaces the seventh indication information with the terminal
  • the identifier of the interface or the fourth indication information generates the first data.
  • the first communications device After generating the first data, the first communications device generates a first message and sends a first message to the second communications device. It can be seen that, in this process, the first communication device essentially replaces the seventh indication information with the identifier of the first interface or the fourth indication information.
  • the method for the first communication device to acquire the first data is applicable to the uplink transmission process.
  • the method for the first communication device to acquire the first data is applicable to the downlink transmission process.
  • the method for the first communication device to acquire the first data is applicable to both the uplink transmission process and the downlink transmission process.
  • the first communications device after acquiring the first data, further compresses the first data or the sub information in the first data according to the first preset compression algorithm. In this way, the first communication device transmits a first message including the compressed first data to the second communication device.
  • the sub-information includes at least one of an IP header, an SCTP common header, and information other than the target information in the SCTP data block, where the target information is at least one of data, a flow identifier, and a PPI; or the sub-information includes an IP header, At least one of the UDP header and the information other than the TEID in the GTP header.
  • the foregoing compression method is applicable to the uplink transmission process.
  • the above compression method is applicable to a downlink transmission process.
  • the above compression method is applicable to both the uplink transmission process and the downlink transmission process.
  • the first communication device acquires the first data by: the first communication device receives the third message sent by the fourth communication device, and the third message includes the second data; the first communication The device obtains the second data from the third message, and decompresses the second data according to the second preset compression algorithm to obtain the first data.
  • the fourth communication device is the next hop device of the first communication device. If the second communication device is the next hop device of the first communication device, the fourth communication device is the last hop device of the first communication device.
  • the first communication device further receives the fourth message sent by the second communication device, where the fourth message includes the third data; the first communication device is configured according to the third preset compression algorithm. The third data is compressed, and the decompressed third data is sent to the terminal.
  • the first communication device further receives a fifth message sent by the second communication device, where the fifth message includes fourth data; the first communication device decompresses according to the fourth preset compression algorithm
  • the fourth data is sent to the CU in the host base station system to send the decompressed fourth data.
  • the method for the first communication device to acquire the first data is: the first communication device receives a sixth message that is sent by the CU and includes the fifth data; the first communication device is configured from the sixth message. Obtaining the fifth data, and decompressing the fifth data according to the fifth preset compression algorithm to obtain the first data.
  • the first communications device further processes the first data according to the first preset key and the first preset target algorithm, and sends the first data to the second communications device, including the processed first The first message of the data.
  • the first preset target algorithm includes at least one of a preset encryption algorithm and a first preset integrity protection algorithm. Therefore, the first communication device processes the first data according to the first preset key and the first preset target algorithm, and substantially protects the first data.
  • the foregoing security protection method is applicable to the uplink transmission process.
  • the first communication device is a DU in a host base station or a host base station system
  • the above security protection method is applicable to a downlink transmission process.
  • the first communication device is an intermediate forwarding node
  • the foregoing security protection method is applicable to both the uplink transmission process and the downlink transmission process.
  • the method for acquiring the first data by the first communications device is: receiving a seventh message sent by the fifth communications device, where the seventh message includes the sixth data; acquiring the sixth data, and And processing the sixth data according to the second preset key and the second preset target algorithm to obtain the first data.
  • the second preset target algorithm includes at least one of a first preset decryption algorithm and a second preset integrity protection algorithm.
  • the fifth communication device is the next hop device of the first communication device. If the second communication device is the next hop device of the first communication device, the fifth communication device is the last hop device of the first communication device.
  • the first communication device further receives an eighth message sent by the second communication device, where the eighth message includes the seventh data; the first communication device acquires the seventh data, and according to the The third preset key and the third preset target algorithm process the seventh data; the first communication device sends the processed seventh data to the terminal.
  • the third preset target algorithm includes at least one of a second preset decryption algorithm and a third preset integrity protection algorithm.
  • the first communication device further receives a ninth message sent by the second communication device, where the ninth message includes eighth data; the first communication device acquires the eighth data, and according to the fourth preset The secret key and the fourth preset target algorithm process the eighth data; the first communication device sends the processed eighth data to the CU of the host base station system.
  • the fourth preset target algorithm includes at least one of a third preset decryption algorithm and a fourth preset integrity protection algorithm.
  • the embodiment described in FIG. 25 describes a method in which an intermediate forwarding point transmits data in an uplink/downlink data transmission process, and also describes that a service node of the terminal transmits in an uplink/downlink data transmission process.
  • the method of data also describes a method for the host base station system to transmit data during downlink data transmission.
  • the data transmission method includes:
  • the host base station receives the first message that is sent by the first communications device and includes the first data and the type identifier.
  • the type identifier is used to indicate the type of the first data, and the type of the first data includes at least one of user plane data, a status report, a control plane message, and an RRC message of the terminal.
  • the host base station determines, according to the type identifier, a type of the first data.
  • the host base station processes the first data according to the type of the first data.
  • the first message in this embodiment is the same as the first message, and details are not described herein again.
  • the method for the host base station to process the first data is: the host base station sends, according to the first data, the DRB data packet of the second communication device that is not successfully received by the first data to the second communication device. .
  • the host base station further receives, by the first communications device or the third communications device, sixth indication information, where the sixth indication information is used to indicate that the first communications data is sent to the second communications device by using the third communications device.
  • the method for processing the first data by the host base station is: the host base station sends, according to the first data, the DRB data packet of the second communication device that is not successfully received by the first data to the second communication device by using the third communication device.
  • the data transmission method provided by the embodiment of the present application is transmitted in a unified message format, so that the time for each node in the multi-hop relay network to process messages having the format can be effectively reduced. .
  • the embodiment of the present application provides a data transmission device 300, which is a chip in a first communication device or a first communication device.
  • the first communication device is an intermediate forwarding node, a serving node of the terminal, a donor base station, or a DU in the host base station system.
  • the data transmission device 300 is configured to perform the steps performed by the first communication device in the above data transmission method.
  • the data transmission device 300 provided by the embodiment of the present application may include a module corresponding to the corresponding step.
  • the embodiment of the present application may divide the function module of the data transmission device 300 according to the foregoing method example.
  • each function module may be divided according to each function, or two or more functions may be integrated into one processing module.
  • the above integrated modules can be implemented in the form of hardware or in the form of software functional modules.
  • the division of modules in the embodiments of the present application is schematic, and is only a logical function division, and may be further divided in actual implementation.
  • FIG. 27 shows a possible structural diagram of the data transmission device 300 in the case where the respective functional modules are divided by corresponding functions.
  • the data transmission device 300 includes an acquisition unit 30, a transmission unit 31, a reception unit 32, a replacement unit 33, a compression unit 34, a decompression unit 35, a security protection unit 36, and a security processing unit 37.
  • the obtaining unit 30 is configured to support the data transmission device 300 to perform S250 in the above embodiment, and/or other processes for the techniques described herein; the transmitting unit 31 is configured to support the data transmission device 300 to perform the above embodiments.
  • receiving unit 32 for supporting the data transmission device 300 to perform "receiving a second message comprising the second data", and/or for the techniques described herein Other processes
  • the replacement unit 33 is configured to support the data transmission device 300 to perform "replace the seventh indication information with the identity of the terminal at the first interface or the fourth indication information", and/or other techniques for the techniques described herein
  • a compression unit 34 for supporting the data transmission device 300 to perform "compressing sub-information in the first data according to a first preset compression algorithm", and/or other processes for the techniques described herein
  • decompression unit 35 for supporting the data transmission device 300 to perform "for decompressing the second data according to the second predetermined compression algorithm", and/or other techniques for the techniques described herein
  • the security protection unit 36 is configured to support the data transmission device 300 to perform "processing the first data according to the first preset key and the first preset target algorithm", and/or other processes for the techniques described herein
  • the security processing unit 37 is configured to support the data transmission device 300
  • the data transmission device 300 provided by the embodiment of the present application includes but is not limited to the foregoing modules.
  • the data transmission device 300 may further include a storage unit.
  • the storage unit can be used to store the program code of the data transmission device 300. All the related content of the steps involved in the foregoing method embodiments may be referred to the functional descriptions of the corresponding functional modules, and details are not described herein again.
  • the above-mentioned obtaining unit 30, replacement unit 33, compression unit 34, decompression unit 35, security protection unit 36, and security processing unit 37 may be the processing in FIG.
  • the transmitter 91, the transmitting unit 31 and the receiving unit 32 may be the transceiver 93 in FIG. 9, and the storage unit may be the memory 92 in FIG.
  • the foregoing obtaining unit 30, the replacing unit 33, the compressing unit 34, the decompressing unit 35, the security protecting unit 36, and the security processing unit 37 may be the processor 101 in FIG. 10, and the transmitting unit 31
  • the and receiving unit 32 may be the transceiver 103 of FIG. 10, and the storage unit may be the memory 102 of FIG.
  • the data transmission device 300 When the data transmission device 300 operates, the data transmission device 300 performs the steps of the first communication device in the data transmission method of the embodiment shown in FIG.
  • Another embodiment of the present application further provides a computer readable storage medium having instructions stored therein.
  • the data transmission device 300 When the instructions are run on the data transmission device 300, the data transmission device 300 performs the operation as shown in FIG. The step of the first communication device in the data transmission method of the embodiment.
  • a computer program product comprising computer executed instructions stored in a computer readable storage medium; at least one processor of the data transmission device 300 can The computer-executable instructions are read from a computer readable storage medium, and the at least one processor executes the computer-executed instructions such that the data transfer device 300 implements the steps of executing the first one of the data transfer methods illustrated in FIG.
  • the embodiment of the present application provides a data transmission device 400, which may be a host base station or a chip in the host base station.
  • the data transmission device 400 is configured to perform the steps performed by the donor base station in the above data transmission method.
  • the data transmission device 400 provided by the embodiment of the present application may include a module corresponding to the corresponding step.
  • the embodiment of the present application may divide the function module by the data transmission device 400 according to the above method example.
  • each function module may be divided according to each function, or two or more functions may be integrated into one processing module.
  • the above integrated modules can be implemented in the form of hardware or in the form of software functional modules.
  • the division of modules in the embodiments of the present application is schematic, and is only a logical function division, and may be further divided in actual implementation.
  • FIG. 28 shows a possible structural diagram of the data transmission device 400 in the present embodiment.
  • the data transmission device 400 includes a receiving unit 40 and a processing unit 41.
  • the receiving unit 40 is configured to instruct the data transmission device 400 to perform S260 in the above embodiment, and/or other processes for the techniques described herein;
  • the processing unit 41 is configured to support the data transmission device 400 to perform S261 in the above embodiment.
  • S262, and/or other processes for the techniques described herein All the related content of the steps involved in the foregoing method embodiments may be referred to the functional descriptions of the corresponding functional modules, and details are not described herein again.
  • the data transmission device 400 provided by the embodiment of the present application includes but is not limited to the above modules.
  • the data transmission device 400 may further include a storage unit.
  • the storage unit can be used to store program codes and data of the data transmission device 400.
  • the above processing unit 41 may be the processor 101 in FIG. 10, the receiving unit 40 may be the transceiver 103 in FIG. 10, and the storage unit may be the memory 102 in FIG.
  • Another embodiment of the present application also provides a computer readable storage medium including one or more program codes, the one or more programs including instructions when a processor in the data transfer device 400 is executing At the time of the program code, the data transmission device 400 executes the data transmission method as shown in FIG.
  • a computer program product comprising computer executed instructions stored in a computer readable storage medium; at least one processor of the data transfer device 400 can The computer-executable instructions are read from a computer readable storage medium, and the at least one processor executes the computer-executed instructions such that the data transfer device 400 implements the steps of executing the host base station in the data transfer method illustrated in FIG.
  • a computer program product includes one or more computer instructions.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • the computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, computer instructions can be wired from a website site, computer, server or data center (eg, Coaxial cable, fiber optic, digital subscriber line (DSL), or wireless (eg, infrared, wireless, microwave, etc.) is transmitted to another website site, computer, server, or data center.
  • the computer readable storage medium can be any available media that can be accessed by a computer or a data terminal device, such as a server, data center, or the like, including one or more available media.
  • the usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (such as a solid state disk (SSD)).
  • the disclosed apparatus and method may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the modules or units is only a logical function division.
  • there may be another division manner for example, multiple units or components may be used.
  • the combination may be integrated into another device, or some features may be ignored or not performed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may be one physical unit or multiple physical units, that is, may be located in one place, or may be distributed to multiple different places. . Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.
  • the integrated unit if implemented in the form of a software functional unit and sold or used as a standalone product, may be stored in a readable storage medium.
  • the technical solution of the embodiments of the present application may be embodied in the form of a software product in the form of a software product in essence or in the form of a contribution to the prior art, and the software product is stored in a storage medium.
  • a number of instructions are included to cause a device (which may be a microcontroller, chip, etc.) or a processor to perform all or part of the steps of the methods described in various embodiments of the present application.
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like, which can store program codes. .

Landscapes

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

Abstract

本申请实施例公开一种数据传输方法及装置，涉及通信技术领域，能够使得中继节点RN快速识别并处理其接收到的数据。该方法应用于第一通信设备或第一通信设备中的芯片，第一通信设备为中间转发节点、终端的服务节点、宿主基站或者宿主基站系统中的分布式单元DU。方法包括：获取第一数据；向第二通信设备发送包括第一数据以及类型标识的第一消息，类型标识用于表示第一数据的类型，第一数据的类型包括用户面数据、状态报告、控制面消息以及终端的无线资源控制RRC消息中的至少一个。

Description

一种数据传输方法及装置
本申请要求于2018年01月12日提交中国专利局、申请号为201810032655.5、发明名称为“一种数据传输方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请实施例涉及通信技术领域，尤其涉及一种数据传输方法及装置。
背景技术
中继节点(Relay Node，RN)具备无线自回传、置于灵活等特点。在多跳中继的场景中，可以将用户设备(User Equipment，UE)对等的分组数据汇聚协议(Packet Data Convergence Protocol，PDCP)层置于宿主基站系统中，UE对等的无线链路控制层协议(Radio Link Control，RLC)层置于RN中。这样，对于UE的数据，RN仅完成物理层(Physical Layer，PHY)、媒体接入控制(Media Access Control，MAC)层、RLC层的处理即可。此时，将该RN的协议架构称为层2(Layer2，L2)架构。
但是，在包括L2架构的RN的多跳中继网络中，目前还不存在RN如何识别或处理其接收到的数据的方法。
发明内容
本申请实施例提供一种数据传输方法及装置，能够使得RN快速识别并处理其接收到的数据。
为达到上述目的，本申请实施例采用如下技术方案：
第一方面，提供一种数据传输方法，该数据传输方法应用于第一通信设备或第一通信设备中的芯片，该第一通信设备为中间转发节点、终端的服务节点、宿主基站或者宿主基站系统中的分布式单元DU。具体的，本申请实施例提供的数据传输方法为：第一通信设备获取第一数据，并向第二通信设备发送包括第一数据以及类型标识的第一消息，上述类型标识用于表示第一数据的类型。第一数据的类型包括用户面数据、状态报告、控制面消息以及终端的无线资源控制RRC消息中的至少一个。当第一通信设备为中间转发节点时，第二通信设备为中间转发节点的上一跳设备或下一跳设备。当第一通信设备为终端的服务节点时，第二通信设备为终端的服务节点的上一跳设备。当第一通信设备为宿主基站或者DU时，第二通信设备为第一通信设备的下一跳设备。
具体的，若第一数据为用户面数据，第一消息包括第一指示信息以及用户面数据的全局编号SN；第一指示信息用于指示用户面数据归属的终端的数据无线承载DRB。若第一数据为状态报告，第一数据包括终端的DRB承载的用户面数据的全局SN，第一数据用于指示第三通信设备的DRB数据包的传输情况，第三通信设备为终端、中间转发节点或者终端的服务节点。若第一数据为控制面消息，第一消息包括第一接口的传输层协议层信息、第二指示信息、终端在第一接口的标识以及第三指示信息中的至少一个；第一接口为第一通信设备与第二通信设备之间的逻辑通信接口，第一接口的传输层协议层信息包括第一通信设备的网络之间互连的协议IP地址、第二通信设备的 IP地址、宿主基站或DU的IP地址，第一通信设备的端口号、第二通信设备的端口号、宿主基站或DU的端口号，流控制传输协议SCTP的流标识以及SCTP的负载协议标识PPI中的至少一个，第二指示信息用于指示第一通信设备，第三指示信息用于指示第一接口；或者，第一消息包括第四指示信息和终端的服务节点的标识，第四指示信息用于指示终端。
可以看出，对于不同类型的数据，本申请实施例提供的数据传输方法采用统一的消息格式传输，这样，可有效的降低多跳中继网络中的各个节点处理具有该格式的消息的时间。
此外，由于第一通信设备向第二通信设备发送的第一消息包括类型标识，因此，本申请实施例中的第二通信设备在获取到第一消息后，可根据类型标识直接确定出第一数据的类型，进而采用与第一数据的类型对应的方法处理第一消息，进一步提升了多跳中继网络中各个节点的处理效率。
可选的，上述第一指示信息为隧道端点标识(Tunnel Endpoint Identifier，TEID)，源网络之间互联协议(Internet Protocol，IP)地址，目的IP地址，源端口号，目标端口号，终端标识，数据无线承载(Data Radio Bearer，DRB)标识。
上述第二指示信息用于指示第一通信设备。若第一通信设备为RN，则第二指示信息可以为当RN作为UE接入时的UE标识(例如C-RNTI，S-TMSI，GUTI等)，也可以为当RN作为UE接入时，上一跳RN为其分配的F1-like接口标识(例如UE F1AP ID，或者UE F1AP-like ID)，还可以为当RN作为UE接入后，从UE模式转换为RN模式后的RN ID。可选的，若将RN视为一个DU，则第二指示信息可能与DU标识具有相同的格式。可选的，该第二指示信息可以为一个全局标识，其由RN局部标识和RN跳数组成。可选的，RN局部标识可以为该RN的上一跳节点(例如RN或者宿主基站系统中的DU)分配的。
第三指示信息用于指示F1-like接口，以区分不同RN的逻辑F1-like连接。
第四指示信息用于指示终端。可选的，该第四指示信息可以为以下信息中的任一种或任意多种的组合：F1-like接口UE ID(UE F1AP-like ID)、C-RNTI、cell ID、上下文标识(Context ID)等。进一步可选的，第四指示信息为终端标识与RN标识的组合。
可选的，在本申请的一种可能的实现方式中，当第一数据为状态报告时，上述第一数据还包括第五指示信息，第五指示信息用于指示终端的DRB。
上述第五指示信息为TEID，源IP地址，目的IP地址，源端口号，目标端口号，终端标识，DRB标识。可选的，上述第一指示信息与上述第五指示信息可以相同，也可以不同，本申请实施例对此不作具体限定。
可选的，在本申请的另一种可能的实现方式中，若第三通信设备为中间转发节点或终端的服务节点，第一数据具体包括第三通信设备的至少一个DRB中的每个DRB承载的第五指示信息。
可选的，在本申请的另一种可能的实现方式中，第一消息还包括目标标识和第六指示信息中的至少一个；目标标识用于指示终端的服务节点，第六指示信息用于指示终端。
在第一消息还包括目标标识和第六指示信息中的至少一个的情况下，第二通信设备可确定第一消息的目的设备，从而进行相应的处理/转发。
可选的，目标标识可以为终端的服务节点的标识或终端的服务节点的IP地址。
可选的，第六指示信息可以为以下信息中的任一种或任意多种的组合：F1-like接口UE ID(UE F1AP-like ID)、C-RNTI、cell ID、上下文标识(Context ID)等。
可选的，在本申请的另一种可能的实现方式中，当第一数据为控制面消息、且第一消息包括终端在第一接口的标识或第四指示信息时，第一通信设备获取第一数据的方法为：第一通信设备接收包括第二数据的第二消息，该第二数据包括第七指示信息，第七指示信息用于指示终端或终端的DRB；第一通信设备从第二消息中获取第二数据，并将第七指示信息替换为终端在第一接口的标识或第四指示信息，生成第一数据。
可选的，第七指示信息可以为以下信息中的任一种或任意多种的组合：F1-like接口UE ID(UE F1AP-like ID)、C-RNTI、cell ID、上下文标识(Context ID)等。
本申请实施例中的第七指示信息与终端在第一接口的标识为终端在不同接口的标识，同理，第七指示信息与第四指示信息为终端在不同接口的标识。第一通信设备在获取到第二数据后，通过替换用于表示终端的标识生成第一数据，进而向第二通信设备发送第一数据。
可以理解的是，若第二通信设备为第一通信设备的上一跳设备，则第二消息为第一通信设备的下一跳设备发送的。若第二通信设备为第一通信设备的下一跳设备，则第二消息为第一通信设备的上一跳设备发送的。
可选的，在本申请的另一种可能的实现方式中，第一通信设备在获取第一数据之后，还根据第一预设压缩算法，压缩第一数据中的子信息。该子信息包括IP头、SCTP公共头以及SCTP数据块中除目标信息之外的信息中的至少一个，该目标信息为用户数据、流标识以及PPI中的至少一个；或者，子信息包括IP头、用户数据报协议UDP头以及通用分组无线服务隧道协议GTP头中除TEID之外的信息中的至少一个。相应的，第一通信设备向第二通信设备发送包括压缩后的第一数据的第一消息。
第一通信设备在获取第一数据之后，将第一数据或第一数据中的部分信息压缩，有效的降低了第一消息占用的资源，减少了空口资源的传输开销。
可选的，在本申请的另一种可能的实现方式中，若第一通信设备为中间转发节点，则该第一通信设备获取第一数据的方法为：第一通信设备接收第四通信设备发送的第三消息，该第三消息包括第二数据；该第一通信设备从第三消息中获取第二数据，并根据第二预设压缩算法，解压缩第二数据，得到第一数据。其中，若第二通信设备为第一通信设备的上一跳设备，第四通信设备为第一通信设备的下一跳设备；若第二通信设备为第一通信设备的下一跳设备，第四通信设备为第一通信设备的上一跳设备。
若第一通信设备为终端的服务节点，则该第一通信设备还接收第二通信设备发送的包括第三数据的第四消息；该第一通信设备第一根据第三预设压缩算法，解压缩第三数据，并向终端发送解压后的第三数据。
若第一通信设备为DU，则该第一通信设备还接收第二通信设备发送的包括第四数据的第五消息；该第一通信设备根据第四预设压缩算法，解压缩第四数据，并向宿主基站系统中的集中式单元CU发送解压后的第四数据。
若第一通信设备为DU，则该第一通信设备获取第一数据的方法为：该第一通信设备接收CU发送的包括第五数据的第六消息；该第一通信设备从第六消息中获取第五数据，并根据第五预设压缩算法，解压缩第五数据，得到第一数据。
可以看出，当第一通信设备为不同的设备时，在相应的数据传输过程(上行数据传输/下行数据传输)中，第一通信设备还会进行解压缩处理。
可选的，在本申请的另一种可能的实现方式中，第一通信设备在获取第一数据之后，还根据第一预设秘钥和第一预设目标算法，处理第一数据。该第一预设目标算法包括预设加密算法和第一预设完整性保护算法中的至少一种。相应的，第一通信设备向第二通信设备发送包括处理后的第一数据的第一消息。
第一预设目标算法包括预设加密算法和第一预设完整性保护算法中的至少一种，第一通信设备根据第一预设秘钥和第一预设目标算法处理第一数据的过程实质上为第一通信设备对第一数据进行安全保护处理。这样，能够有效的保证了第一数据的安全性，以及完整性。
可选的，在本申请的另一种可能的实现方式中，若第一通信设备为中间转发节点，则该第一通信设备获取第一数据的方法为：该第一通信设备接收第五通信设备发送的包括第六数据的第七消息；该第一通信设备从第七消息中获取第六数据，并根据第二预设秘钥和第二预设目标算法，处理第六数据，得到第一数据。第二预设目标算法包括第一预设解密算法和第二预设完整性保护算法中的至少一种。其中，若第二通信设备为第一通信设备的上一跳设备，第五通信设备为第一通信设备的下一跳设备；若第二通信设备为第一通信设备的下一跳设备，第五通信设备为第一通信设备的上一跳设备。
若第一通信设备为终端的服务节点，则该第一通信设备还接收第二通信设备发送的包括第七数据的第八消息；该第一通信设备从第八消息中获取第七数据，并根据第三预设秘钥和第三预设目标算法，处理第七数据，进而向终端发送处理后的第七数据。第三预设目标算法包括第二预设解密算法和第三预设完整性保护算法中的至少一种。
若第一通信设备为DU，该第一通信设备还接收第二通信设备发送的包括第八数据的第九消息；该第一通信设备从第九消息中获取第八数据，并根据第四预设秘钥和第四预设目标算法，处理第八数据，进而向宿主基站系统的集中式单元CU发送处理后的第八数据。第四预设目标算法包括第三预设解密算法和第四预设完整性保护算法中的至少一种。
可以看出，当第一通信设备为不同的设备时，在相应的数据传输过程(上行数据传输/下行数据传输)中，第一通信设备还会进行解密和/或完整性保护处理。
第二方面，提供一种数据传输装置，该数据传输装置为第一通信设备或第一通信设备中的芯片，第一通信设备为中间转发节点、终端的服务节点、宿主基站或者宿主基站系统中的分布式单元DU。具体的，数据传输装置包括获取单元和发送单元。
本申请提供的各个单元模块所实现的功能具体如下：
上述获取单元，用于获取第一数据。上述发送单元，用于向第二通信设备发送第一消息，第一消息包括上述获取单元获取到的第一数据以及类型标识，类型标识用于表示第一数据的类型，第一数据的类型包括用户面数据、状态报告、控制面消息以及 终端的无线资源控制RRC消息中的至少一个。当第一通信设备为中间转发节点时，第二通信设备为中间转发节点的上一跳设备或下一跳设备。当第一通信设备为终端的服务节点时，第二通信设备为终端的服务节点的上一跳设备；当第一通信设备为宿主基站或者DU时，第二通信设备为第一通信设备的下一跳设备。若第一数据为用户面数据，第一消息包括第一指示信息以及用户面数据的全局编号SN；第一指示信息用于指示用户面数据归属的终端的数据无线承载DRB。若第一数据为状态报告，第一数据包括终端的DRB承载的用户面数据的全局SN，第一数据用于指示第三通信设备的DRB数据包的传输情况，第三通信设备为终端、中间转发节点或者终端的服务节点。若第一数据为控制面消息，第一消息包括第一接口的传输层协议层信息、第二指示信息、终端在第一接口的标识以及第三指示信息中的至少一个；第一接口为第一通信设备与第二通信设备之间的逻辑通信接口，第一接口的传输层协议层信息包括第一通信设备的网络之间互连的协议IP地址、第二通信设备的IP地址、宿主基站或DU的IP地址，第一通信设备的端口号、第二通信设备的端口号、宿主基站或DU的端口号，流控制传输协议SCTP的流标识以及SCTP的负载协议标识PPI中的至少一个，第二指示信息用于指示第一通信设备，第三指示信息用于指示第一接口；或者，第一消息包括第四指示信息和终端的服务节点的标识，第四指示信息用于指示终端。
可选的，在本申请的一种可能的实现方式中，当第一数据为状态报告时，上述第一数据还包括第五指示信息，第五指示信息用于指示终端的DRB。
可选的，在本申请的另一种可能的实现方式中，若上述第三通信设备为中间转发节点或终端的服务节点，上述第一数据具体包括第三通信设备的至少一个DRB中的每个DRB承载的第五指示信息。
可选的，在本申请的另一种可能的实现方式中，第一消息还包括目标标识和第六指示信息中的至少一个；该目标标识用于指示终端的服务节点，第六指示信息用于指示终端。
可选的，在本申请的另一种可能的实现方式中，当第一数据为控制面消息、且第一消息包括终端在第一接口的标识或第四指示信息时，数据传输装置还包括接收单元。该接收单元，用于接收包括第二数据的第二消息，第二数据包括第七指示信息，第七指示信息用于指示终端或终端的DRB。上述获取单元，还用于从上述接收单元接收到的第二消息中获取第二数据。此外，本申请实施例中的数据传输装置还包括替换单元。该替换单元用于将第七指示信息替换为终端在第一接口的标识或第四指示信息，生成第一数据。
可选的，在本申请的另一种可能的实现方式中，本申请实施例提供的数据传输装置还包括压缩单元。该压缩单元，用于在上述获取单元获取第一数据之后，根据第一预设压缩算法，压缩第一数据中的子信息，该子信息包括IP头、SCTP公共头以及SCTP数据块中除目标信息之外的信息中的至少一个，目标信息为用户数据、流标识以及PPI中的至少一个；或者，子信息包括IP头、用户数据报协议UDP头以及通用分组无线服务隧道协议GTP头中除TEID之外的信息中的至少一个。上述发送单元，具体用于向第二通信设备发送包括压缩后的第一数据的第一消息。
可选的，在本申请的另一种可能的实现方式中，本申请实施例提供的数据传输装 置还包括接收单元和解压缩单元。若第一通信设备为中间转发节点，上述接收单元用于接收第四通信设备发送的第三消息，第三消息包括第二数据。上述获取单元还用于从上述接收单元接收到的第三消息中获取第二数据。上述解压缩单元用于根据第二预设压缩算法，解压缩第二数据，得到第一数据。其中，若第二通信设备为第一通信设备的上一跳设备，第四通信设备为第一通信设备的下一跳设备；若第二通信设备为第一通信设备的下一跳设备，第四通信设备为第一通信设备的上一跳设备。
若第一通信设备为终端的服务节点，上述接收单元用于接收第二通信设备发送的第四消息，第四消息包括第三数据。上述解压缩单元，用于根据第三预设压缩算法，解压缩第三数据。上述发送单元具体用于终端发送解压后的第三数据。
若第一通信设备为DU，上述接收单元用于接收第二通信设备发送的第五消息，第五消息包括第四数据。上述解压缩单元用于根据第四预设压缩算法，解压缩第四数据。上述发送单元，具体用于向宿主基站系统中的集中式单元CU发送解压后的第四数据；
若第一通信设备为DU，上述接收单元用于接收CU发送的第六消息，第六消息包括第五数据。上述获取单元还用于从第六消息中获取第五数据。上述解压缩单元用于根据第五预设压缩算法，解压缩第五数据，得到第一数据。
可选的，在本申请的另一种可能的实现方式中，本申请实施例中的数据传输装置还包括安全保护单元。该安全保护单元，用于在上述获取单元获取第一数据之后，根据第一预设秘钥和第一预设目标算法，处理第一数据，第一预设目标算法包括预设加密算法和第一预设完整性保护算法中的至少一种。上述发送单元，具体用于向第二通信设备发送包括处理后的第一数据的第一消息。
可选的，在本申请的另一种可能的实现方式中，本申请实施例中的数据传输装置还包括接收单元和安全处理单元。若第一通信设备为中间转发节点，上述接收单元用于接收第五通信设备发送的第七消息，第七消息包括第六数据。上述获取单元还用于从上述接收单元接收到第七消息中获取第六数据。上述安全处理单元用于根据第二预设秘钥和第二预设目标算法，处理上述获取单元获取到的第六数据，得到第一数据。第二预设目标算法包括第一预设解密算法和第二预设完整性保护算法中的至少一种。其中，若第二通信设备为第一通信设备的上一跳设备，第五通信设备为第一通信设备的下一跳设备；若第二通信设备为第一通信设备的下一跳设备，第五通信设备为第一通信设备的上一跳设备。
若第一通信设备为终端的服务节点，上述接收单元用于接收第二通信设备发送的第八消息，第八消息包括第七数据。上述获取单元还用于从上述接收单元接收到的第八消息中获取第七数据。上述安全处理单元用于根据第三预设秘钥和第三预设目标算法，处理上述获取单元获取到的第七数据。上述发送单元具体用于向终端发送处理后的第七数据；第三预设目标算法包括第二预设解密算法和第三预设完整性保护算法中的至少一种。
若第一通信设备为DU，上述接收单元用于接收第二通信设备发送的第九消息，第九消息包括第八数据。上述获取单元还用于从第九消息中获取第八数据。上述安全处理单元用于根据第四预设秘钥和第四预设目标算法，处理第八数据。上述发送单元 具体用于向宿主基站系统的集中式单元CU发送处理后的第八数据。第四预设目标算法包括第三预设解密算法和第四预设完整性保护算法中的至少一种。
第三方面，提供一种数据传输装置，该数据传输装置包括：一个或多个处理器、存储器、通信接口。其中，存储器、通信接口与一个或多个处理器耦合；数据传输装置通过通信接口与其他设备通信，存储器用于存储计算机程序代码，计算机程序代码包括指令，当一个或多个处理器执行指令时，数据传输装置执行如上述第一方面及其各种可能的实现方式所述的数据传输方法。
第四方面，还提供一种计算机可读存储介质，该计算机可读存储介质中存储有指令；当其在数据传输装置上运行时，使得数据传输装置执行如上述第一方面及其各种可能的实现方式所述的数据传输方法。
第五方面，还提供一种包括指令的计算机程序产品，当其在数据传输装置上运行时，使得数据传输装置执行如上述第一方面及其各种可能的实现方式所述的数据传输方法。
在本申请中，上述数据传输装置的名字对设备或功能模块本身不构成限定，在实际实现中，这些设备或功能模块可以以其他名称出现。只要各个设备或功能模块的功能和本申请类似，属于本申请权利要求及其等同技术的范围之内。
本申请中第二方面、第三方面、第四方面、第五方面及其各种实现方式的具体描述，可以参考第一方面及其各种实现方式中的详细描述；并且，第二方面、第三方面、第四方面、第五方面及其各种实现方式的有益效果，可以参考第一方面及其各种实现方式中的有益效果分析，此处不再赘述。
第六方面，提供一种数据传输方法，该数据传输方法应用于宿主基站或宿主基站中的芯片。该数据传输方法为：接收第一通信设备发送的包括第一数据以及类型标识的第一消息之后，根据类型标识确定第一数据的类型，并根据第一数据的类型处理第一数据。上述类型标识用于表示第一数据的类型。第一数据的类型包括用户面数据、状态报告、控制面消息以及终端的无线资源控制RRC消息中的至少一个。
具体的，若第一数据为用户面数据，第一消息包括第一指示信息以及用户面数据的全局编号SN；第一指示信息用于指示用户面数据归属的终端的数据无线承载DRB。若第一数据为状态报告，第一数据包括终端的DRB承载的用户面数据的全局SN，第一数据用于指示第三通信设备的DRB数据包的传输情况，第三通信设备为终端、中间转发节点或者终端的服务节点。若第一数据为控制面消息，第一消息包括第一接口的传输层协议层信息、第二指示信息、终端在第一接口的标识以及第三指示信息中的至少一个；第一接口为第一通信设备与第二通信设备之间的逻辑通信接口，第一接口的传输层协议层信息包括第一通信设备的网络之间互连的协议IP地址、第二通信设备的IP地址、宿主基站或DU的IP地址，第一通信设备的端口号、第二通信设备的端口号、宿主基站或DU的端口号，流控制传输协议SCTP的流标识以及SCTP的负载协议标识PPI中的至少一个，第二指示信息用于指示第一通信设备，第三指示信息用于指示第一接口；或者，第一消息包括第四指示信息和终端的服务节点的标识，第四指示信息用于指示终端。
可以看出，对于不同类型的数据，本申请实施例提供的数据传输方法采用统一的 消息格式传输，这样，可有效的降低宿主基站处理具有该格式的消息的时间。
此外，由于第一通信设备向宿主基站发送的第一消息包括类型标识，因此，本申请实施例中的宿主基站在获取到第一消息后，可根据类型标识直接确定出第一数据的类型，进而采用与第一数据的类型对应的方法处理第一消息，进一步提升了宿主基站的处理效率。
可选的，上述第一指示信息为TEID，源IP地址，目的IP地址，源端口号，目标端口号，终端标识，DRB标识。
上述第二指示信息用于指示第一通信设备。若第一通信设备为RN，则第二指示信息可以为当RN作为UE接入时的UE标识(例如C-RNTI，S-TMSI，GUTI等)，也可以为当RN作为UE接入时，上一跳RN为其分配的F1-like接口标识(例如UE F1AP ID，或者UE F1AP-like ID)，还可以为当RN作为UE接入后，从UE模式转换为RN模式后的RN ID。可选的，若将RN视为一个DU，则第二指示信息可能与DU标识具有相同的格式。可选的，该第二指示信息可以为一个全局标识，其由RN局部标识和RN跳数组成。可选的，RN局部标识可以为该RN的上一跳节点(例如RN或者宿主基站系统中的DU)分配的。
第三指示信息用于指示F1-like接口，以区分不同RN的逻辑F1-like连接。
第四指示信息用于指示终端。可选的，该第四指示信息可以为以下信息中的任一种或任意多种的组合：F1-like接口UE ID(UE F1AP-like ID)、C-RNTI、cell ID、上下文标识(Context ID)等。进一步可选的，第四指示信息为终端标识与RN标识的组合。
可选的，在本申请的一种可能的实现方式中，当第一数据为状态报告时，上述第一数据还包括第五指示信息，第五指示信息用于指示终端的DRB。
上述第五指示信息为TEID，源IP地址，目的IP地址，源端口号，目标端口号，终端标识，DRB标识。可选的，上述第一指示信息与上述第五指示信息可以相同，也可以不同，本申请实施例对此不作具体限定。
可选的，在本申请的另一种可能的实现方式中，若第二通信设备为中间转发节点或终端的服务节点，第一数据具体包括第二通信设备的至少一个DRB中的每个DRB承载的第五指示信息。
可选的，在本申请的另一种可能的实现方式中，若第一数据为状态报告时，宿主基站根据第一数据的类型，处理第一数据的方法为：宿主基站根据第一数据，向第二通信设备发送第一数据指示的未被成功接收的第二通信设备的DRB数据包。
可选的，在本申请的另一种可能的实现方式中，在根据第一数据的类型，处理第一数据之前，宿主基站还接收第一通信设备或第三通信设备发送的第六指示信息，第六指示信息用于指示通过第三通信设备向第二通信设备发送第一数据指示的未被成功接收的第二通信设备的DRB数据包。
第七方面，提供一种数据传输装置，该数据传输装置为宿主基站或宿主基站中的芯片。具体的，该数据传输装置包括接收单元和处理单元。
本申请提供的各个单元模块所实现的功能具体如下：
上述接收单元，用于接收第一通信设备发送的第一消息，第一消息包括第一数据 以及类型标识，类型标识用于表示第一数据的类型，第一数据的类型包括用户面数据、状态报告、控制面消息以及终端的无线资源控制RRC消息中的至少一个。上述处理单元，用于根据上述接收单元接收到的第一消息中的类型标识，确定第一数据的类型，并根据第一数据的类型，处理第一数据。
具体的，若第一数据为用户面数据，第一消息包括第一指示信息以及用户面数据的全局编号SN；第一指示信息用于指示用户面数据归属的终端的数据无线承载DRB。若第一数据为状态报告，第一数据包括终端的DRB承载的用户面数据的全局SN，第一数据用于指示第二通信设备的DRB数据包的传输情况，第二通信设备为终端、中间转发节点或终端的服务节点。若第一数据为控制面消息，第一消息包括第一接口的传输层协议层信息、第二指示信息、终端在第一接口的标识以及第三指示信息中的至少一个；第一接口为宿主基站与第一通信设备之间的逻辑通信接口，第一接口的传输层协议层信息包括第一通信设备的网络之间互连的协议IP地址、宿主基站的IP地址、第一通信设备的端口号、宿主基站的端口号、流控制传输协议SCTP的流标识以及SCTP的负载协议标识PPI中的至少一个，第二指示信息用于指示第一通信设备，第三指示信息用于指示第一接口；或者，第一消息包括第四指示信息和终端归属的小区的标识中的至少一个，第四指示信息用于指示终端。
可选的，在本申请的一种可能的实现方式中，上述第一数据还包括第五指示信息，第五指示信息用于指示终端的DRB。
可选的，在本申请的另一种可能的实现方式中，若第二通信设备为中间转发节点或终端的服务节点，上述第一数据具体包括第二通信设备的至少一个DRB中的每个DRB承载的第五指示信息。
可选的，在本申请的另一种可能的实现方式中，若第一数据为状态报告时，上述处理单元具体用于：根据第一数据，向第二通信设备发送第一数据指示的未被成功接收的第二通信设备的DRB数据包。
可选的，在本申请的另一种可能的实现方式中，上述接收单元，还用于在上述处理单元根据第一数据的类型，处理第一数据之前，接收第一通信设备或第三通信设备发送的第六指示信息，该第六指示信息用于指示通过第三通信设备向第二通信设备发送第一数据指示的未被成功接收的第二通信设备的DRB数据包。
第八方面，提供一种数据传输装置，该数据传输装置包括：一个或多个处理器、存储器、通信接口。其中，存储器、通信接口与一个或多个处理器耦合；数据传输装置通过通信接口与其他设备通信，存储器用于存储计算机程序代码，计算机程序代码包括指令，当一个或多个处理器执行指令时，数据传输装置执行如上述第六方面及其各种可能的实现方式所述的数据传输方法。
第九方面，还提供一种计算机可读存储介质，该计算机可读存储介质中存储有指令；当其在数据传输装置上运行时，使得数据传输装置执行如上述第六方面及其各种可能的实现方式所述的数据传输方法。
第十方面，还提供一种包括指令的计算机程序产品，当其在数据传输装置上运行时，使得数据传输装置执行如上述第六方面及其各种可能的实现方式所述的数据传输方法。
在本申请中，上述数据传输装置的名字对设备或功能模块本身不构成限定，在实际实现中，这些设备或功能模块可以以其他名称出现。只要各个设备或功能模块的功能和本申请类似，属于本申请权利要求及其等同技术的范围之内。
本申请中第七方面、第八方面、第九方面、第十方面及其各种实现方式的具体描述，可以参考第六方面及其各种实现方式中的详细描述；并且，第七方面、第八方面、第九方面、第十方面及其各种实现方式的有益效果，可以参考第六方面及其各种实现方式中的有益效果分析，此处不再赘述。
本申请的这些方面或其他方面在以下的描述中会更加简明易懂。
附图说明
图1为5G系统中由CU和DU组成的基站系统的结构示意图；
图2为本申请实施例提供的一种多跳中继网络的结构示意图；
图3为本申请实施例提供的LTE R10 Relay的协议栈架构示意图；
图4为本申请实施例提供的在逐跳架构中各个节点的协议栈架构示意图一；
图5为本申请实施例提供的在RN与DU的端到端架构中各个节点的协议栈架构示意图一；
图6为本申请实施例提供的在RN与CU的端到端架构中各个节点的协议栈架构示意图；
图7为本申请实施例提供的通信系统的结构示意图；
图8为本申请实施例提供的手机的硬件结构示意图；
图9为本申请实施例提供的RN的硬件结构示意图；
图10为本申请实施例提供的宿主基站的硬件结构示意图；
图11为本申请实施例提供的通信系统中各个节点的协议层架构示意图；
图12为本申请实施例提供的在逐跳架构中各个节点的协议栈架构示意图二；
图13为本申请实施例提供的在RN与DU的端到端架构中各个节点的协议栈架构示意图二；
图14为本申请实施例提供的在逐跳架构中各个节点的协议栈架构示意图三；
图15为本申请实施例提供的在逐跳架构中各个节点的协议栈架构示意图四；
图16为本申请实施例中未被压缩的SCTP数据包的格式示意图；
图17为本申请实施例中第一消息的格式示意图一；
图18为本申请实施例中第一消息的格式示意图二；
图19为本申请时候实施例中未被压缩的GTP-U数据包的格式示意图；
图20为本申请实施例中在图14示出的协议栈中第一消息的格式；
图21为本申请实施例中在图15示出的协议栈中第一消息的格式；
图22为本申请实施例中各个节点的IAB功能协议层的配置流程示意图一；
图23为本申请实施例中各个节点的IAB功能协议层的配置流程示意图二；
图24为本申请实施例中各个节点的IAB功能协议层的配置流程示意图三；
图25为本申请实施例提供的数据传输方法流程示意图一；
图26为本申请实施例提供的数据传输方法流程示意图二；
图27为本申请实施例提供的数据传输装置的结构示意图一；
图28为本申请实施例提供的数据传输装置的结构示意图二。
具体实施方式
为了便于理解本申请，现对本申请实施例涉及到的相关概念进行描述。
宿主基站系统：为中继节点提供无线接入的基站系统，与中继节点之间通过无线的Un接口连接。宿主基站系统可以为一个独立的宿主基站(Donor evolved Node Base Station，DeNB)，也可以由集中式单元(Centralized Unit，CU)和分布式单元(Distributed Unit，DU)组成。
CU主要用于负责集中式无线资源和连接管理控制，具备无线高层协议栈功能，例如：无线资源控制(Radio Resource Control，RRC)层和PDCP层等。CU也能够支持部分核心网功能下沉至接入网，称作边缘计算网络，能够满足未来通信网络中新兴业务(如视频、网购、虚拟/增强现实等)对于网络时延的更高要求。DU具备分布式用户面处理功能，主要具备物理层功能和实时性需求较高的层2功能。相应的，CU具有RRC层和PDCP层，DU具有RLC层、MAC层和PHY层。
CU可以集中式的布放，DU的布放取决于实际网络环境。示例性的，对于核心城区、话务密度较高、站间距较小或机房资源受限的区域，例如：高校和大型演出场馆，可以集中式布放DU；对于话务较稀疏、站间距较大等区域，例如：郊县，山区等区域，可以采取分布式的方式布放DU。
图1为第五代通信技术(the 5 Generation Mobile Communication Technology，5G)系统中由CU和DU组成的基站系统的结构示意图。
如图1所示，CU与DU之间通过CU-DU接口进行通信，该接口可以用于传输CU与DU之间的控制面消息，或者该基站系统服务的UE的RRC消息，或者该基站系统服务的UE的数据等。为了简化描述，将该CU-DU接口称为F1接口，其控制面称为F1-C，其用户面称为F1-U。F1-C承载的CU与DU之间的控制面消息称为F1应用协议(F1 Application Protocol，F1AP)消息。F1AP消息可以分为公共消息(Common Message，或者，Non UE Associated)和UE相关消息(UE Associated)两部分。公共消息可以用于F1接口管理、CU/DU配置更新以及小区管理等。UE相关消息可以用于建立/管理/更新/删除UE上下文、交互UE的服务质量(Quality of Service，QoS)参数以及协议栈配置等。此外，UE相关消息还可以用于传输UE的RRC消息，即将UE的信令无线承载(Signaling Radio Bearers，SRB)1/SRB 2/SRB1S/SRB2S/SRB 3所传输的RRC消息中的PDCP协议数据单元(Protocol Data Unit，PDU)，以及SRB 0所传输的RRC消息中的RRC PDU作为RRC容器(Container)包括于F1AP消息中进行传输。F1-U传输UE的数据。具体的，将UE的PDCP PDU封装在通用分组无线服务隧道协议用户面(General Packet Radio Service Tunneling Protocol-User Plane，GTP-U)数据包中进行传输。这里，可以利用GTP TEID识别UE的DRB
Un口：RN的回传链路称为Un口。Un口包括RN与宿主基站系统通信的无线传输接口，以及RN与RN通信的无线传输接口。
Uu接口：RN或宿主基站系统为UE服务的接入链路称为Uu口。
多跳中继网络：由终端、多个RN以及宿主基站系统组成。数据或信令从信源(如终端或宿主基站系统)到信宿(如宿主基站系统或终端)之间经过多个RN的转发。
服务节点：网络中，与终端直接通过空口相连，并为该终端提供控制面消息和用户面数据传输的节点。
中间转发节点：为其他RN提供中继传输的节点和为其他RN所提供服务的终端提供中继传输的节点。
一般的，可采用跳数等级描述某一RN在网络中的位置。与宿主基站系统直接通信的RN的跳数等级为1，经由另一RN与宿主基站系统通信的RN的跳数等级为2，以此类推。
示例性的，如图2所示，多跳中继网络包括宿主基站、中继节点1～中继节点4，终端1～终端6。宿主基站与中继节点1和中继节点4直接通信，宿主基站与中继节点1之间的接口为Un1接口，宿主基站与中继节点4之间的接口为Un4接口。中继节点1与中继节点2之间的接口为Un2接口，中继节点2与中继节点3之间的接口为Un3接口。终端1通过Uu1接口与中继节点1通信，终端2通过Uu2接口与中继节点2通信，终端3通过Uu3接口与中继节点3通信，终端4通过Uu4接口与中继节点4通信，终端5通过Uu5接口与中继节点1通信，终端6通过Uu6接口与中继节点4通信。
由于宿主基站与中继节点1和中继节点4直接通信，因此，中继节点1和中继节点4的跳数等级为1；中继节点2通过中继节点1与宿主基站通信，因此其跳数等级为2；类似的，中继节点5的跳数等级也为2；中继节点3通过中继节点2和中继节点1与宿主节点通信，因此其跳数等级为3。结合上述描述可知，中继节点1为中继节点2的中间转发节点，中继节点1和中继节点2为中继节点3的中间转发节点，中继节点1和中继节点2为终端3和终端5的中间转发节点等。中继节点1为终端1的服务节点，中继节点2为终端2的服务节点，中继节点3为终端3和终端5的服务节点，中继节点4为终端4和终端6的服务节点。
对于跳数为1的中间转发节点，由于其直接与宿主基站或宿主基站系统内的DU通信，因此其上一跳节点为宿主基站或宿主基站系统内的DU。对应的，可以将该中间转发节点称为宿主基站或宿主基站系统内的DU的下一跳节点。
第10版长期演进计划(Long Term Evolution Release 10，LTE R10)引入了中继技术。在包括RN的网络中，各个节点均具备完整的协议栈。参见图3，图3示出了包括RN的网络中各个节点的协议栈架构。该协议栈架构分为控制面的协议栈架构和用户面的协议栈架构。
图3中的A示出了UE、RN、宿主基站和为UE提供服务的移动管理模块(Mobility Management Entity，MME)(图中记为MME-UE)的控制面协议栈。UE的控制面协议栈从上至下包括非接入层(non-Access Stratum，NAS)、无线资源控制(Radio Resource Control，RRC)层、PDCP层、RLC层、MAC层和PHY层。RN与UE通信的控制面协议栈从上至下包括RRC层、PDCP层、RLC层、MAC层和PHY层，与宿主基站通信的控制面协议栈从上至下包括S1应用协议(S1 Application Protocol，S1-AP)层、流控制传输协议(Stream Control Transmission Protocol，SCTP)层、网络互连协议(Internet Protocol，IP)层、PDCP层、RLC层、MAC层和PHY层。宿主基站与RN通信的控制面协议栈从上至下包括S1-AP层、SCTP层、IP层、PDCP层、RLC层、 MAC层和PHY层；与MME-UE通信的协议栈从上至下包括S1-AP层、SCTP层、IP层、数据链路层(也可以称为L2层)和物理层(也可以称为L1层)。MME-UE的协议栈从上至下包括NAS、S1-AP层、SCTP层、IP层、L2层和L1层。R10Relay控制面有完整的协议栈，UE的RRC消息终结在RN，同时RN为UE提供S1/X2消息的proxy(代理)，其中，S1接口为宿主基站和核心网(Core Net，CN)控制面实体之间的接口，X2接口可以为宿主基站和RN(或者RN和RN)之间的接口。
图3中的B示出了UE、RN、宿主基站和为UE提供服务的服务网关(Serving Gateway，SGW)/公用数据网网关(Public Data Network Gateway，PGW)(图中记为SGW-UE/PGW-UE)的用户面协议栈。UE的用户面协议栈从上至下包括IP层、PDCP层、RLC层、MAC层和PHY层。RN与UE通信的用户面协议栈从上至下包括PDCP层、RLC层、MAC层和PHY层，与宿主基站通信的用户面协议栈从上至下包括通用分组无线服务隧道协议用户面(General Packet Radio Service Tunneling Protocol-User Plane，GTP-U)层、用户数据报协议(User Datagram Protocol，UDP)层、IP层、PDCP层、RLC层、MAC层和PHY层。宿主基站与RN通信的用户协议栈从上至下包括GTP-U层、UDP层、IP层、PDCP层、RLC层、MAC层和PHY层，与SGW-UE/PGW-UE通信的用户面协议栈从上至下包括GTP-U层、UDP层、IP层、L2层和L1层。SGW-UE/PGW-UE中从上至下包括IP层、GTP-U层、UDP层、IP层、L2层和L1层。R10 Relay用户面也有完整的协议栈，能够为UE提供空口数据无线承载(Data Radio Bearer，DRB)传输服务，并且可以将多个UE的数据进行汇聚，通过回传链路一并转发给宿主基站。
结合上述图3，在控制面，RN为UE生成UE相关的(UE associated)S1消息；在用户面，RN为UE封装S1接口的GTP格式的数据包。宿主基站为上述S1接口的消息或数据提供代理(proxy)服务，将上述消息或数据发送至对应的核心网节点。
若同一个Un接口的DRB中承载有多个UE的用户面数据，可通过GTP隧道进行区分，例如：TEID。若同一个Un接口的DRB中承载有多个UE的控制面S1AP消息，可通过S1AP消息中的UE S1AP ID进行区分。若一个DRB中既承载有用户面数据又承载有S1AP消息，可以通过IP地址区分，即为用户面的GTP-U隧道和控制面的SCTP连接分配不同的IP地址。宿主基站收到RN发来的S1AP消息后，将其中IP地址替换为MME-UE的IP地址，将该消息中Un接口的UE S1AP ID替换为宿主基站/MME在S1-MME为该UE分配的ID。宿主基站收到RN发来的GTP-U数据包后，将其中的IP地址替换为SGW-UE的IP地址，将其中的上行/下行TEID替换为相应的SGW/宿主基站为该UE的演进分组系统承载(Evolved Packet System bearer，EPS-bearer)分配的上行/下行TEID。
由于RN具备无线自回传、部署灵活等特点，能够节省传统基站置于有线回传链路时的挖沟埋线成本，其适用于5G网络及演进的通信系统的网络初期铺展。但是，R10 RN仅能支持比较简单的置于场景，如单跳单宿主，不支持多跳中继网络，无法满足未来网络多样化的需求。
为了能支持多跳中继网络，提供更好的性能，满足未来网络更加多样化的需求，需要研究支持多跳中继网络的RN。
R10 Relay网络中Uu口和Un口有完整的控制面和用户面协议栈，在用户面，对于UE的上下行数据包，都需要经过RN的PDCP层的处理，增加了处理时延。5G网络中可以将UE对等的PDCP层置于宿主基站系统中，UE对等的RLC层置于RN中。这样，对于UE的数据，RN仅完成PHY、MAC、RLC层的处理即可。此时，将该RN的协议架构称为L2架构。
上述将UE的对等RLC层置于RN，UE对等的PDCP层置于宿主基站系统的架构与上述CU-DU架构(可以参考上述如图1)类似，宿主基站系统可以视为CU，RN可以视为DU。与上述CU-DU架构不同的是，宿主基站系统与RN之间通过无线接口通信，并且在多跳中继网络中，宿主基站系统与一跳RN直接通信，宿主基站系统与跳数大于1的RN不能直接通信，需要通过位于二者之间的RN进行中转(需要说明的是，这里的位置关系是指在通信连接的位置关系，而不是指地理位置关系)。因此，多跳L2 Relay网络的协议栈的设计可以借鉴CU-DU的接口协议设计，例如：基于F1AP流程和信元进行RN与宿主基站系统之间的信令交互，基于F1-U的GTP-U协议栈架构进行用户数据的封装和发送。需要说明的是，RN也可以通过RN的RRC消息与宿主基站系统进行信令交互，用于管理UE的上下文、传递对UE的配置信息等，但是现有的RRC的功能和流程不支持上述RN与宿主基站之间进行UE相关信息的交互，因此需要定义新的RRC流程和信元，增加了实现多跳中继网络的标准化工作，而基于F1接口进行RN-宿主基站系统之间空口的设计可以尽量少引入新的信令流程和信元。
对于L2架构的RN，在基于F1接口进行RN与宿主基站系统之间空口的设计的情况下，可以基于逐跳架构(Hop by Hop)或端到端架构完成数据的传输。其中，端到端架构包括RN与DU的端到端架构、RN与CU的端到端架构。
本申请实施例以多跳中继网络1为例进行说明。多跳中继网络1包括CU、DU、RN 1、RN 2以及UE，RN 1与DU之间的接口为Un1，RN 1与RN 2之间的接口为Un2，RN 2与UE之间的接口为Uu。
需要说明的是，上述多跳中继网络1仅仅是对多跳中继网络的一种举例说明，并不是对多跳中继网络的限定。本申请实施例中的多跳中继网络可以包括多个RN。
对于逐跳架构，图4中的A示出了该架构中多跳中继网络1中各个节点的控制面协议栈，图4中的B示出了该架构中多跳中继网络1中各个节点的用户面协议栈。其中，图4中的Adap.表示适配层。结合上述图3可知，图4中RN的F1AP层与图3中RN的S1-AP层类似，图4中DU和CU的F1AP层与图3中基站的S1-AP层类似。
在图4的A中，UE的对等RRC层和PDCP层置于CU上，UE的对等RLC层置于RN 2上。
在上行传输过程中，RN 2生成UE相关的F1AP消息，并通过Un2接口将其生成的F1AP消息发送至RN 1。特殊的，对于UE的上行RRC消息而言，RN2在通过Uu接口接收到UE的RRC消息后，将其处理到RLC层，并将RLC SDU或PDCP PDU携带在F1AP消息中发送至RN 1。RN 1通过Un2接口接收到F1AP消息后，对其接收到的F1AP消息进行处理(例如：将F1AP消息体中与UE相关的UE F1AP ID和/或TEID等替换为Un1接口上与UE对应的标识，其他内容保持不变)，并将处理后的F1AP消息承载在Un 1接口上发送至DU。DU对其接收到的F1AP消息进行处理(例 如：将F1AP消息体中与UE相关的UE F1AP ID和/或TEID等替换为F1接口上与UE对应的标识，其他内容保持不变)，并将处理后的F1AP消息进一步承载在F1接口上发送至CU。CU对其接收到的F1AP消息进行处理(例如：提取其中的RRC消息，并进行RRC层处理。可选的，CU在进行RRC层处理之前，先进行PDCP处理)。
在下行传输过程中，CU生成UE相关的F1AP消息，通过F1接口发送至DU。DU对其接收到的F1AP消息进行处理(例如：将F1AP消息体中与UE相关的F1接口上的UE F1AP ID和/或TEID等替换为Un1接口上与UE对应的标识，其他内容保持不变)，并将处理后的F1AP消息承载在Un1接口上发送至RN 1。特殊的，对于UE的下行RRC消息而言，CU生成RRC消息后(即RRC PDU)(可选的，RRC消息还经过PDCP层处理)，将其携带在F1AP消息中发送至DU。RN 1通过Un1接口接收到F1AP消息后，对其接收到的F1AP消息进行处理(例如：将F1AP消息体中与UE相关的Un1上的UE F1AP ID和/或TEID等替换为Un2接口上与UE对应的标识，其他内容保持不变)，并将处理后的F1AP消息承载在Un2口上发送至RN2。RN2对其接收到的F1AP消息进行处理，例如：提取其中的下行RRC消息，并将提取出的下行RRC消息经过与UE对等的RLC层处理后，通过Uu口发送至UE。
在图4的B中，UE的对等PDCP层置于CU上，UE的对等RLC层置于RN2上。
在上行传输过程中，RN 2通过Uu接口接收到UE的数据，例如：UE DRB承载的数据，将接收到的数据处理到RLC层，并将RLC SDU/PDCP PDCU封装成GTP-U数据，通过Un2接口发送至RN 1。RN 1对其接收到的GTP-U数据进行处理(例如：将Un2接口上UE对应的TEID替换为在Un1接口上UE对应的TEID，UE的数据的内容保持不变)，并将处理后的GTP-U数据承载在Un1接口上发送至DU。DU对其接收到的GTP-U数据进行处理(例如：将GTP TEID替换为在F1接口上对应的TEID，UE的数据的内容保持不变)，并将处理后的GTP-U数据进一步承载在F1接口上发送至CU。CU对其接收到的GTP-U数据进行处理(例如：提取UE的数据，UE的数据可以为PDCP PDU/RLC SDU)，并进行PDCP层处理。
在下行传输过程中，CU将UE的数据(例如：DRB PDCP PDU)封装为GTP-U数据，并通过F1接口将GTP-U数据发送至DU。DU对其接收到的GTP-U数据进行处理(例如：将F1接口上UE对应的TEID替换为在Un1接口上UE对应的TEID，UE的数据的内容保持不变)，并将处理后的GTP-U数据承载在Un1接口上发送至RN 1。RN 1对其接收到的GTP-U数据进行处理(例如：将Un1接口上UE对应的TEID替换为在Un2接口上UE对应的TEID，UE的数据的内容保持不变)，并将处理后的GTP-U数据承载在Un2接口上发送至RN 2。RN 2对其接收到的GTP-U数据进行处理，例如：提取出其中的PDCP PDU/RLC SDU，并经过与UE对等的RLC层处理，通过Uu接口发送至UE。
可以看出，图4示出的协议栈(控制面协议栈和用户面协议栈)中，数据传输路径中的每个节点均可以感知每个UE的信息，维护UE的上下文，对UE进行管理和数据统计，以保障UE的QoS。UE标识(例如UE F1AP ID/TEID)为每段传输通道各自维护的，例如：在Un2接口的UE标识为RN 2或RN 1分配的，在Un1接口的UE标识为RN 1或DU分配的，在F1接口的UE标识为DU或CU分配的。因此，两段传 输通道的中间转发节点需要做两段UE标识的替换(可选的，其决定/维护两段UE标识的映射关系)。但是，传输路径上的每个节点均需要做F1AP消息/GTP-U数据的解析和封装，降低了UE信令/数据的转发速度。
对于RN与DU的端到端架构，图5中的A示出了该架构中多跳中继网络1中各个节点的控制面协议栈，图5中的B示出了该架构中多跳中继网络1中各个节点的用户面协议栈。
与上述图4示出的协议栈不同的是，图5示出的协议栈中，数据传输路径中除RN 2、DU和CU之外的其他节点在接收到其上一节点/下一节点发送的数据后，无需进行F1AP协议层/GTP-U协议层的数据处理/解析，直接转发即可。
对于RN与CU的端到端架构，图6中的A示出了该架构中多跳中继网络1中各个节点的控制面协议栈，图6中的B示出了该架构中多跳中继网络1中各个节点的用户面协议栈。
与上述图4和图5示出的协议栈不同的是，图6示出的协议栈中，数据传输路径中除RN 2和CU之外的其他节点在接收到其上一节点/下一节点发送的数据后，无需进行F1AP协议层/GTP-U协议层的数据处理/解析，直接转发即可。
可以看出，与图4示出的协议栈相比，图5和图6示出的协议栈(控制面协议栈和用户面协议栈)中，部分/所有中间转发节点无需处理/解析其接收到的数据，提高了转发效率。但是，图5和图6示出的协议栈中，部分/所有中间转发节点无法感知其他RN服务的UE的信息，也无法对其他RN服务的UE进行数据统计。
此外，上述图4、图5以及图6示出的协议栈中，各段空口上传输的F1AP消息没有进行空口加密，数据的安全性不能得到有效的保障。
除了上述转发速度低、无法统计UE的数据的问题之外，目前还未明确上述RN 1以及上述RN2如何识别或处理其接收到的数据的方法。
针对上述问题，本申请实施例提供一种数据传输方法，第一通信设备(或第一通信设备中的芯片)在获取到第一数据后，向第二通信设备发送包括第一数据以及用于表示该第一数据的类型的类型标识的第一消息。这里，第一数据可以为用户面数据(如终端的PDCP PDU)、状态报告、控制面消息以及终端的RRC消息中的至少一个。可以看出，对于不同类型的数据，本申请实施例提供的数据传输方法采用统一的消息格式传输，这样，可有效的降低多跳中继网络中的各个节点处理具有该格式的消息的时间。
此外，由于第一通信设备向第二通信设备发送的第一消息包括类型标识，因此，本申请实施例中的第二通信设备在获取到第一消息后，可根据类型标识直接确定出第一数据的类型，进而采用与第一数据的类型对应的方法处理第一消息，进一步提升了多跳中继网络中各个节点的处理效率。
本申请实施例中的第一通信设备可以为中间转发节点、终端的服务节点、宿主基站或或宿主基站系统中的DU。当第一通信设备为中间转发节点时，第二通信设备为中间转发节点的上一跳设备或下一跳设备。当第一通信设备为终端的服务节点时，第二通信设备为终端的服务节点的上一跳设备。当第一通信设备为宿主基站或者宿主基站系统中的DU时，第二通信设备为第一通信设备的下一跳设备。
本申请实施例提供的数据传输方法适用于通信系统。该通信系统可以是5G系统，也可以是LTE系统，还可以是其他包括至少一个RN的通信系统，本申请实施例对此不作具体限定。
本申请实施例提供的通信系统的结构示意图可以参考上述图2。图2中的宿主基站以及任一中继节点均可以为上述第一通信设备。
为了便于理解，这里以通信系统包括2个RN为例进行说明。参见图7，该通信系统包括终端70、RN 71、RN 72以及宿主基站系统73。终端70通过Uu接口与RN 72通信，RN 72通过Un2接口与RN 71通信，RN 71通过Un1接口与宿主基站系统73通信。
需要说明的是，图7仅仅是对本申请实施例提供的通信系统的举例说明，并不是对该通信系统的具体限定。在实际应用中，RN 71和RN 72均可为多个终端提供服务，或者，该通信系统可以在RN 71与RN 72之间还存在至少一个RN。
本申请实施例中的终端70可以是指能够与RN 72在控制面和用户面实现数据传输的手机(如图8所示的手机800)、平板电脑、个人计算机(Personal Computer，PC)、个人数字助理(Personal Digital Assistant，PDA)、智能手表、上网本、可穿戴电子设备等，本申请实施例对该设备的具体形式不做特殊限制。
如图8所示，以手机800作为上述终端举例，手机800具体可以包括：处理器801、射频(Radio Frequency，RF)电路802、存储器803、触摸屏804、蓝牙装置805、一个或多个传感器806、无线保真(Wireless Fidelity，Wi-Fi)装置807、定位装置808、音频电路809、外设接口810以及电源装置811等部件。这些部件可通过一根或多根通信总线或信号线(图8中未示出)进行通信。本领域技术人员可以理解，图8中示出的硬件结构并不构成对手机的限定，手机800可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置。
下面结合图8对手机800的各个部件进行具体的介绍：
处理器801是手机800的控制中心，利用各种接口和线路连接手机800的各个部分，通过运行或执行存储在存储器803内的应用程序，以及调用存储在存储器803内的数据，执行手机800的各种功能和处理数据。在一些实施例中，处理器801可包括一个或多个处理单元。在本申请实施例一些实施例中，上述处理器801还可以包括指纹验证芯片，用于对采集到的指纹进行验证。
射频电路802可用于在收发信息或通话过程中，无线信号的接收和发送。特别地，射频电路802可以将基站的下行数据接收后，给处理器801处理；另外，将涉及上行的数据发送至基站。通常，射频电路包括但不限于天线、至少一个放大器、收发信机、耦合器、低噪声放大器、双工器等。此外，射频电路802还可以通过无线通信和其他设备通信。所述无线通信可以使用任一通信标准或协议，包括但不限于全球移动通讯系统、通用分组无线服务、码分多址、宽带码分多址、长期演进、电子邮件、短消息服务等。
存储器803用于存储应用程序以及数据，处理器801通过运行存储在存储器803的应用程序以及数据，执行手机800的各种功能以及数据处理。存储器803主要包括存储程序区以及存储数据区，其中，存储程序区可存储操作系统、至少一个功能所需 的应用程序(比如声音播放功能、图像处理功能等)；存储数据区可以存储根据使用手机800时所创建的数据(比如音频数据、电话本等)。此外，存储器803可以包括高速随机存取存储器(RAM)，还可以包括非易失存储器，例如磁盘存储器件、闪存器件或其他易失性固态存储器件等。存储器803可以存储各种操作系统，例如，iOS操作系统，Android操作系统等。上述存储器803可以是独立的，通过上述通信总线与处理器801相连接；存储器803也可以和处理器801集成在一起。
触摸屏804具体可以包括触控板804-1和显示器804-2。
其中，触控板804-1可采集手机800的用户在其上或附近的触摸事件(比如用户使用手指、触控笔等任何适合的物体在触控板804-1上或在触控板804-1附近的操作)，并将采集到的触摸信息发送至其他器件(例如处理器801)。其中，用户在触控板804-1附近的触摸事件可以称之为悬浮触控；悬浮触控可以是指，用户无需为了选择、移动或拖动目标(例如图标等)而直接接触触控板，而只需用户位于设备附近以便执行所想要的功能。此外，可以采用电阻式、电容式、红外线以及表面声波等多种类型来实现触控板804-1。
显示器(也称为显示屏)804-2可用于显示由用户输入的信息或提供给用户的信息以及手机800的各种菜单。可以采用液晶显示器、有机发光二极管等形式来配置显示器804-2。触控板804-1可以覆盖在显示器804-2之上，当触控板804-1检测到在其上或附近的触摸事件后，传送给处理器801以确定触摸事件的类型，随后处理器801可以根据触摸事件的类型在显示器804-2上提供相应的视觉输出。虽然在图2中，触控板804-1与显示屏804-2是作为两个独立的部件来实现手机800的输入和输出功能，但是在某些实施例中，可以将触控板804-1与显示屏804-2集成而实现手机800的输入和输出功能。可以理解的是，触摸屏804是由多层的材料堆叠而成，本申请实施例实施例中只展示出了触控板(层)和显示屏(层)，其他层在本申请实施例实施例中不予记载。另外，触控板804-1可以以全面板的形式配置在手机800的正面，显示屏804-2也可以以全面板的形式配置在手机800的正面，这样在手机的正面就能够实现无边框的结构。
另外，手机800还可以具有指纹识别功能。例如，可以在手机800的背面(例如后置摄像头的下方)配置指纹识别器812，或者在手机800的正面(例如触摸屏804的下方)配置指纹识别器812。又例如，可以在触摸屏804中配置指纹采集器件812来实现指纹识别功能，即指纹采集器件812可以与触摸屏804集成在一起来实现手机800的指纹识别功能。在这种情况下，该指纹采集器件812配置在触摸屏804中，可以是触摸屏804的一部分，也可以以其他方式配置在触摸屏804中。本申请实施例实施例中的指纹采集器件812的主要部件是指纹传感器，该指纹传感器可以采用任何类型的感测技术，包括但不限于光学式、电容式、压电式或超声波传感技术等。
手机800还可以包括蓝牙装置805，用于实现手机800与其他短距离的设备(例如手机、智能手表等)之间的数据交换。本申请实施例实施例中的蓝牙装置可以是集成电路或者蓝牙芯片等。
手机800还可以包括至少一种传感器806，比如光传感器、运动传感器以及其他传感器。具体的，光传感器可包括环境光传感器及接近传感器，其中，环境光传感器 可根据环境光线的明暗来调节触摸屏804的显示器的亮度，接近传感器可在手机800移动到耳边时，关闭显示器的电源。作为运动传感器的一种，加速计传感器可检测各个方向上(一般为三轴)加速度的大小，静止时可检测出重力的大小及方向，可用于识别手机姿态的应用(比如横竖屏切换、相关游戏、磁力计姿态校准)、振动识别相关功能(比如计步器、敲击)等；至于手机800还可配置的陀螺仪、气压计、湿度计、温度计、红外线传感器等其他传感器，在此不再赘述。
Wi-Fi装置807，用于为手机800提供遵循Wi-Fi相关标准协议的网络接入，手机800可以通过Wi-Fi装置807接入到Wi-Fi接入点，进而帮助用户收发电子邮件、浏览网页和访问流媒体等，它为用户提供了无线的宽带互联网访问。在其他一些实施例中，该Wi-Fi装置807也可以作为Wi-Fi无线接入点，可以为其他设备提供Wi-Fi网络接入。
定位装置808，用于为手机800提供地理位置。可以理解的是，该定位装置808具体可以是全球定位系统(Global Positioning System，GPS)或北斗卫星导航系统、俄罗斯GLONASS等定位系统的接收器。定位装置808在接收到上述定位系统发送的地理位置后，将该信息发送至处理器801进行处理，或者发送至存储器803进行保存。在另外的一些实施例中，该定位装置808还可以是辅助全球卫星定位系统(Assisted Global Positioning System，AGPS)的接收器，AGPS系统通过作为辅助服务器来协助定位装置808完成测距和定位服务，在这种情况下，辅助定位服务器通过无线通信网络与设备例如手机800的定位装置808(即GPS接收器)通信而提供定位协助。在另外的一些实施例中，该定位装置808也可以是基于Wi-Fi接入点的定位技术。由于每一个Wi-Fi接入点都有一个全球唯一的MAC地址，设备在开启Wi-Fi的情况下即可扫描并收集周围的Wi-Fi接入点的广播信号，因此可以获取到Wi-Fi接入点广播出来的MAC地址；设备将这些能够标示Wi-Fi接入点的数据(例如MAC地址)通过无线通信网络发送至位置服务器，由位置服务器检索出每一个Wi-Fi接入点的地理位置，并结合Wi-Fi广播信号的强弱程度，计算出该设备的地理位置并发送到该设备的定位装置808中。
音频电路809、扬声器813、麦克风814可提供用户与手机800之间的音频接口。音频电路809可将接收到的音频数据转换后的电信号，传输到扬声器813，由扬声器813转换为声音信号输出；另一方面，麦克风814将收集的声音信号转换为电信号，由音频电路809接收后转换为音频数据，再将音频数据输出至RF电路802以发送至比如另一手机，或者将音频数据输出至存储器803以便进一步处理。
外设接口810，用于为外部的输入/输出设备(例如键盘、鼠标、外接显示器、外部存储器、用户识别模块卡等)提供各种接口。例如通过通用串行总线(Universal Serial Bus，USB)接口与鼠标连接，通过用户识别模块卡卡槽上的金属触点与电信运营商提供的用户识别模块卡(Subscriber Identification Module，SIM)卡进行连接。外设接口810可以被用来将上述外部的输入/输出外围设备耦接到处理器801和存储器803。
在本申请实施例中，手机800可通过外设接口810与设备组内的其他设备进行通信，例如，通过外设接口810可接收其他设备发送的显示数据进行显示等，本申请实施例对此不作任何限制。
手机800还可以包括给各个部件供电的电源装置811(比如电池和电源管理芯片)，电池可以通过电源管理芯片与处理器801逻辑相连，从而通过电源装置811实现管理充电、放电、以及功耗管理等功能。
尽管图8未示出，手机800还可以包括摄像头(前置摄像头和/或后置摄像头)、闪光灯、微型投影装置、近场通信(Near Field Communication，NFC)装置等，在此不再赘述。
图9为本申请实施例提供的一种RN的组成示意图，如图9所示，RN可以包括至少一个处理器91，存储器92、收发器93、总线94。
下面结合图9对RN的各个构成部件进行具体的介绍：
处理器91是RN的控制中心，可以是一个处理器，也可以是多个处理元件的统称。例如，处理器91是一个CPU，也可以是特定集成电路(Application Specific Integrated Circuit，ASIC)，或者是被配置成实施本申请实施例的一个或多个集成电路，例如：一个或多个微处理器(Digital Signal Processor，DSP)，或，一个或者多个现场可编程门阵列(Field Programmable Gate Array，FPGA)。
其中，处理器91可以通过运行或执行存储在存储器92内的软件程序，以及调用存储在存储器92内的数据，执行RN的各种功能。
在具体的实现中，作为一种实施例，处理器91可以包括一个或多个CPU，例如图中所示的CPU 0和CPU 1。
在具体实现中，作为一种实施例，RN可以包括多个处理器，例如图9中所示的处理器91和处理器95。这些处理器中的每一个可以是一个单核处理器(single-CPU)，也可以是一个多核处理器(multi-CPU)。这里的处理器可以指一个或多个设备、电路、和/或用于处理数据(例如计算机程序指令)的处理核。
存储器92可以是只读存储器(Read-Only Memory，ROM)或可存储静态信息和指令的其他类型的静态存储设备，随机存取存储器(Random Access Memory，RAM)或者可存储信息和指令的其他类型的动态存储设备，也可以是电可擦可编程只读存储器(Electrically Erasable Programmable Read-Only Memory，EEPROM)、只读光盘(Compact Disc Read-Only Memory，CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器92可以是独立存在，通过总线94与处理器91相连接。存储器92也可以和处理器91集成在一起。
其中，存储器92用于存储执行本申请方案的软件程序，并由处理器91来控制执行。
收发器93，用于与其他设备或通信网络通信。如用于与以太网，无线接入网(radio access network，RAN)，无线局域网(Wireless Local Area Networks，WLAN)等通信网络通信。收发器93可以包括基带处理器的全部或部分，以及还可选择性地包括RF处理器。RF处理器用于收发RF信号，基带处理器则用于实现由RF信号转换的基带信号或即将转换为RF信号的基带信号的处理。
总线94，可以是工业标准体系结构(Industry Standard Architecture，ISA)总线、 外部设备互连(Peripheral Component Interconnect，PCI)总线或扩展工业标准体系结构(Extended Industry Standard Architecture，EISA)总线等。该总线可以分为地址总线、数据总线、控制总线等。为便于表示，图9中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
图9中示出的设备结构并不构成对RN的限定，可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置。
本申请实施例中的宿主基站系统73可以是独立的宿主基站，该宿主基站可以是无线通信的基站(Base Station，BS)或基站控制器等；也可以是由DU 730和CU 731组成。由于宿主基站系统73可能是由DU 730和CU 731组成，因此，上述图7中用虚线框表示DU 730和CU 731。
具体的，宿主基站系统73的主要功能包括如下一个或多个功能：进行无线资源的管理、IP头的压缩及用户数据流的加密、终端附着时进行MME的选择、路由用户面数据至SGW、寻呼消息的组织和发送、广播消息的组织和发送、以移动性或调度为目的的测量及测量报告的配置等等。
当宿主基站系统73为独立的宿主基站时，在采用不同的无线接入技术的系统中，宿主基站的名称可能会有所不同。例如：在LTE网络(或称为第4代移动通信技术(the fourth Generation Telecommunication，4G)系统)中，宿主基站的名称为演进的基站(evolved NodeB，eNB或eNodeB)；在第3代移动通信技术(the third Generation Telecommunication，3G)系统中，宿主基站的名称为基站(Node B)；在下一代无线通信系统(如5G系统)中，宿主基站的名称为gNB。随着通信技术的演进，这一名称可能会变化。此外，在其它可能的情况下，宿主基站可以是其它为终端设备提供无线通信功能的装置。
当宿主基站系统73为独立的宿主基站时，图10示出了该宿主基站的硬件结构。如图10所示，宿主基站可以包括至少一个处理器101，存储器102、收发器103、总线104。
在具体实现中，作为一种实施例，处理器101可以包括一个或多个CPU，例如图10中的CPU0和CPU1。
在具体实现中，作为一种实施例，该该宿主基站可以包括多个处理器，例如图10中的处理器101和处理器105。
图10中所示的各个器件的作用以及其他说明可以示例性的参见上文。
此外，图10中示出的设备结构并不构成对宿主基站的限定，可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置。
由于针对不同类型的数据，本申请实施例提供的数据传输方法采用统一的消息格式传输，可有效的降低多跳中继网络中的各个节点处理具有该格式的消息的时间。因此，本申请实施例中的各个RN和宿主基站系统均具备支持生成/解析具有该同一格式的消息的功能。
为此，本申请实施例通过在RN和宿主基站系统的协议栈中添加独立的、具有相应功能的协议层或者在现有的某一协议层(如RLC层或PDCP层)中添加相应功能，支持上述生成/解析具有该同一格式的消息的功能。其中，若宿主基站系统由DU和 CU组成，则在DU的协议栈中添加独立的、具有相应功能的协议层或者在现有的某一协议层(如RLC层)中添加相应功能。
为了便于说明，本申请实施例以在RN和宿主基站系统的协议栈中添加独立的、具有相应功能的协议层为例进行说明。其中，添加的协议层可以称为接入回传一体化(Integrated Access link and Backhaul link，IAB)功能协议层，也可以用其他名称，本申请实施例对此不作具体限定。
为了便于描述，本申请实施例均以IAB功能协议层为例进行说明。
结合上述图7，若宿主基站系统73为独立的宿主基站，图11示出了本申请实施例中各个节点的控制面协议栈和用户面协议栈。若宿主基站系统73由DU 730和CU 731组成，图12示出了在逐跳架构中本申请实施例中各个节点的控制面协议栈和用户面协议栈，图13示出了在RN 72到DU 730的端到端架构中本申请实施例中各个节点的控制面协议栈和用户面协议栈。
进一步地，若将本申请实施例中RN的PDCP层置于CU 731上，即Un接口传输不执行RN PDCP功能，则IAB功能协议层与PDCP层为两个独立的协议层。在这种场景中，图14示出了本申请实施例中各个节点的控制面协议栈和用户面协议栈。
若将本申请实施例中RN的PDCP层置于DU 730上，即Un接口传输执行RN PDCP功能，此时，IAB功能协议层可能置于PDCP层中。在这种场景中，图15示出了本申请实施例中各个节点的控制面协议栈和用户面协议栈。
结合上述描述可知，F1接口提供一个基站系统中的CU与DU交互的方法，而F1AP中定义了信令流程，用于支持F1接口的功能。相应的，本申请实施例在RN与宿主基站系统/上一跳RN之间可以建立类似的接口，用于RN与宿主基站系统/上一跳RN之间的交互，该接口(可以为F1接口，或者具备类似的用于传递UE相关信息以进行UE上下文管理、UE配置等功能的其他接口)的名称不限。为了便于描述，本申请实施例将其称为F1-like接口。
对于上述图11～图15示出的协议栈中的IAB功能协议层而言，可采用统一的消息格式传输不同类型的数据。这里，统一的消息格式是指包括类型标识和第一数据，该统一的消息格式具体可以参考后续描述。类型标识用于表示第一数据的类型。第一数据的类型包括用户面数据、状态报告、控制面消息以及终端的RRC消息中的至少一个。
现对IAB功能协议层的功能进行详细解释。
1、传输用户面数据
对应的，本申请实施例中的第一数据为用户面数据。
可选的，用户面数据包括属于终端的DRB的PDCP PDU/RLC PDU/H-RLC PDU，该终端的用户面的数据可以为类似GTP-U格式的数据包。其中，H-RLC是指将现有RLC协议层按照功能划分为多个部分(可以称为子协议层)，H-RLC为其中一个部分，负责完成ARQ等功能。
IAB功能协议层在获取到用户面数据后，可以采用以下两种方式中的其中一种传输用户面的数据：
方式一、用户面数据(属于终端的DRB的PDCP PDU RLC PDU/H-RLC PDU) 承载在F1-like接口的用户面中传输。
可选的，F1-like接口的用户面协议栈可以包括以下任一种或任意多种的组合：GTP-U层、UDP层和IP层。
方式二、用户面数据(属于终端的DRB的PDCP PDU RLC PDU/H-RLC PDU)直接承载在该IAB功能协议层中传输。例如：直接承载在该IAB功能协议层的PDU中。
当第一数据为用户面数据时，本申请实施例中的第一消息还包括第一指示信息，该第一指示信息用于指示用户面数据归属的终端的DRB。对于上述方式一，第一指示信息可以为用户面传输层信息，该用户面传输层信息可以包括以下信息中的任一种或任意多种的组合：TEID，源IP地址，目的IP地址，源端口号，目标端口号。对于上述方式二，IAB功能协议层发送的第一消息则需要包括额外的终端标识和DRB标识信息等。简单的说，第一指示信息可以包括以下信息中的任一种或任意多种的组合：TEID，源IP地址，目的IP地址，源端口号，目标端口号，终端标识，DRB标识。
可选的，第一消息还包括用户面数据的全局编号(Sequence Number，SN)。用户面数据的全局SN分为用户面数据在终端的DRB内的SN和用户面数据在RN的DRB内的SN。
用户面数据在终端的DRB内的SN由宿主基站系统和终端/该终端的服务节点生成，宿主基站、中间转发节点以及该终端的服务节点进行维护，中间转发节点不更改该SN，因此称为全局SN。
示例性的，用户面数据在终端的DRB内的SN可以为终端的PDCP SN和/或HFN，也可以为终端的RLC SN，上述两种SN由宿主基站系统(对应下行数据)和终端(对应上行数据)生成；也可以为GTP-U SN，还可以为一个新定义的SN，例如：IAB功能协议层内部的SN，简称为终端的IAB SN，上述两种SN由宿主基站系统(对应下行数据)和该终端的服务节点(对应上行数据)生成。
用户面数据在RN的DRB内的SN为直接通过空口相连的RN和宿主基站系统之间，或者RN与RN之间维护的SN，简称为RN DRB SN。示例性的，RN DRB SN可以为RN PDCP SN(如果Un口的协议栈有RN PDCP协议层，且该IAB功能协议层在RN PDCP协议层之下，或者该IAB功能协议层与RN PDCP协议层共置于，此时在IAB功能协议层中可以识别RN PDCP SN)，也可以为一个新定义的SN，例如：IAB功能协议层内部的SN，简称为RN IAB SN。
对于终端的数据(例如：PDU Session、QoS流(其标识称为QoS flow identifier，QFI))，一般具有QoS参数要求。例如：GBR(Guranteed Bit Rate，保证比特率)、时延(latency)/端到端时延、抖动、丢包率、转发优先级和语音MOS值等。当终端的数据承载在无线接入网(Radio Access Network，RAN)侧时，宿主基站系统将上述QoS参数发送至为终端服务的RN和中间节点。另外，每个RAN节点可能会对该终端的Non-GBR的业务进行限速，使其不超过AMBR(Aggregate Maximum Bit Rate，总计最大比特速率)值。因此，当终端的数据经由RAN侧的宿主基站系统以及一个或多个RN时，RAN节点不仅需要获知对应的QoS参数要求；还需要监测终端的数据，以确保能够满足对应的QoS要求，此时各个RN需要能够识别不同终端的数据(以及 识别属于一个终端的不同的DRB和/或QFI)。
对于GBR，宿主基站系统直接知会各个RN，各个RN自行保障即可。类似的，对于AMBR而言，各个RN可以自行保证。对于时延，则需要宿主基站系统和各个RN进行协商，或者宿主基站系统决定后告知各个RN，从而令各个RN保证与自身相关的Un/Uu接口的时延要求。
2、传输状态报告
对应的，本申请实施例中的第一数据为状态报告。该状态报告用于指示终端、中间转发节点、终端的服务节点的DRB数据包的传输情况，这里，DRB数据包的传输情况指DRB数据包的传输状态和/或丢包情况。
在上述图11～图15示出的协议栈中，与终端70对等的RLC层置于RN 72上，与终端70对等的PDCP层置于宿主基站系统73上，因此，本申请实施例中的RLC状态报告和PDCP状态报告与现有的状态报告不同。以下行为例，终端的数据(例如，在L2架构中以终端DRB为粒度)会先承载在Un接口(例如RN的DRB)上传输给为该终端服务的RN，该RN通过Uu接口将终端的数据承载在终端的DRB上发送至终端。因此，Uu接口的终端的RLC SN与Un接口的RN的RLC SN是独立编号的，因此，针对RLC SN进行反馈的状态报告仅能反馈一段Uu接口或者Un接口的RLC传输状态。终端的PDCP PDU承载在Un接口上传输时，RN可能无法获取终端的PDCP SN，因此，无法基于终端的PDCP SN反馈PDCP状态报告。例如，在上述图4、图5以及图6中，终端的PDCP PDU经过GTP-U/UDP/IP协议栈处理后，承载在Un口中传输，若该GTP-U数据包经过了IP层加密，加密方式RN 1不感知，则RN 1无法获知终端的PDCP SN，即便可以获知PDCP SN，也需要解析GTP-U数据包，引入额外的处理开销。此外，终端的PDCP PDU承载在Un口上传输时，还经过RN DRB的PDCP实体进行处理。而PDCP实体对用户面数据需要进行加密，若该加密方式是宿主基站系统与为该终端服务的RN之间协商的，中间转发节点不感知该加密方式，则中间转发节点无法解析出终端的PDCP SN。此时，可以定义一个宿主基站系统到为该终端服务的RN之间的端到端的SN，中间转发节点和为该终端服务的RN均可以基于该SN进行状态报告的反馈。为了便于描述，本申请实施例中将宿主基站系统到为该终端服务的RN之间的端到端的SN称为终端的全局SN，例如IAB SN。
需要说明的是，上述全局SN可能为PDCP SN(中间转发节点可以感知终端的PDCP SN)，也可以为RLC SN。例如：在终端的部分RLC的功能为与宿主基站系统对等的情况下，宿主基站系统与终端之间维护对应的SN，中间转发节点不改变该SN。若该RLC功能为ARQ功能，则该全局SN为用于ARQ的RLC SN。需要说明的是，PDCP SN是指PDCP SDU/PDU对应的SN；RLC SN是指RLC SDU(或RLC SDU segment)对应的SN。
综上，第一数据为状态报告时，该状态报告包括终端的DRB承载的用户面数据的全局SN。
可选的，第一数据还包括用于指示终端的DRB的第五指示信息。也就是说，状态报告可以为终端的DRB的状态报告，用于提供该终端的DRB所承载的用户面数据是否被成功发送/接收的信息。对于RN而言，该状态报告可以为该RN提供服务的终 端的DRB的状态报告，也可以为其它RN提供服务的终端的DRB的状态报告(此时，RN不直接与该终端通过空口相连，但为该终端的数据进行转发)。也就是说，状态报告的传输粒度为终端的DRB。
可选的，第五指示信息可以为TEID、源IP地址、目的IP地址、源端口号、目标端口号、终端标识以及DRB标识中的至少一个。
可选的，终端的DRB的状态报告可以针对终端的一个DRB，此时，该状态报告包括与该终端对应的第五指示信息；或者，IAB功能协议层传输的状态报告可以针对终端的多个DRB，此时，该状态报告包括与该终端相关的多个第五指示信息；或者，IAB功能协议层传输的状态报告可以针对终端的所有DRB，此时，该状态报告包括用于指示终端的第六指示信息。示例性的，该第六指示信息可以为以下信息中的任一种或任意多种的组合：小区无线网络临时标识C-RNTI，小区标识，终端上下文标识，终端的F1接口标识，终端的F1-like接口标识，TEID，其他格式的终端标识。可选的，在IAB功能协议层传输的状态报告可以针对终端的所有DRB的情况下，状态报告还包括与该终端相关的所有第五指示信息。若状态报告不包括与该终端相关的所有第五指示信息，则该状态报告可以由多个按照一定的顺序排列的终端的DRB的状态报告组成。该顺序可以为协议预设规定，也可以按照DRB标识由大到小或者由小到大的顺序排列。
可选的，RN生成针对其服务的终端的DRB的状态报告时，终端的DRB的状态报告可以为终端的RLC状态报告/PDCP状态报告。终端的DRB状态报告可以为IAB功能协议层生成的一个或多个终端的RLC状态报告/PDCP状态报告的组合。
可选的，RN生成针对其服务的终端的DRB的状态报告时，或者生成针对其他RN提供服务的终端的DRB的状态报告时，终端的DRB的状态报告还包括该终端的全局SN。这样，宿主基站系统/中间转发节点可根据该全局SN确定终端的数据包的传输情况。
具体的，终端的DRB的状态报告包括下行和/或上行数据包的状态。其中，数据包的状态可以包括以下内容中的任一种或任意多种的组合：最大的成功发送/接收的全局SN(Highest Successfully Delivered Sequence Number)、一个传输空洞(指一个或SN连续的多个未成功发送/接收的数据包)的最大全局SN和最小全局SN、传输空洞序号、最大的连续成功发送/接收的全局SN、一个传输成功数据块的最大全局SN和最小全局SN、传输成功数据块序号、成功发送的全局SN、丢失的全局SN、最大的发送/接收的全局SN、终端标识、DRB标识、TEID。需要说明的是，终端的DRB的状态报告包括的具体信息不限于上述SN，例如还可以包括第一个丢失的包的全局SN以及下行下一个即将被发送的包的全局SN。但是由于它们均可通过上述终端的DRB状态报告所包括的信息推断得出，例如：第一个丢失的包的全局SN即为传输空洞中的最小全局SN，下行下一个即将被发送的包的全局SN即为下行最大的发送的全局SN+1，因此，在此不再一一罗列可能的情况。
此外，终端的DRB的状态报告也可以是位图(bitmap)的形式，其中，每个bit对应一个SN对应的数据包是否丢失的状态。
当中间转发节点生成其与为下一跳节点之间的链路的状态报告时，或终端的服务 节点针对该终端的Uu口的传输情况生成状态报告时，上述最大的成功发送的全局SN是指生成该状态报告的节点与其下一跳节点/其服务的终端之间传输该终端的某一DRB的数据时，下一跳节点/其服务的终端成功接收的属于该终端的这一DRB的数据包中，SN最大的包对应的SN。上述最大的连续成功发送的全局SN是指生成该状态报告的节点与其下一跳节点/其服务的终端之间传输该终端的某一DRB的数据时，下一跳节点/其服务的终端成功接收的属于该终端的这一DRB的SN连续的数据包中，SN最大的包对应的SN。
其中，本申请实施例中的传输空洞序号是指当可能有多于一个传输空洞时，需要指示不同的传输空洞时，每个传输空洞对应的序号。可选的，成功发送是指发送端收到接收端的确认(Acknowledge,ACK)反馈。可选的，丢失的数据包是指收到对端的否认(Non Acknowledge，NACK)反馈，或者没有收到对端的ACK反馈。可选的，成功接收是指接收端成功收到了发送端发送的数据。
传输成功数据块是指大于上述最大的连续成功发送的全局SN的数据包中，成功被接收的一个或SN连续的多个数据包。
传输成功数据块序号是指当可能有多于一个传输成功数据块时，需要指示不同的传输成功数据块时，每个传输成功数据块对应的序号。
可选的，状态报告可以为RN的DRB的状态报告，用于提供该RN的DRB所承载的用户面数据是否正确发送/接收的信息。对于RN而言，该状态报告可以为自身的Un接口的DRB的状态报告，也可以是RN/DU针对其下一跳RN的Un接口的DRB生成的状态报告。也就是说，状态报告的传输粒度为RN的DRB。
可选的，RN的DRB的状态报告可以针对该RN的至少一个DRB中的每个DRB所承载的至少一个终端的DRB的状态报告。此时，该RN的DRB的状态报告还包括终端标识和/或DRB标识，或者包括用于识别终端的DRB的标识(例如TEID、UE上下文context标识、或者其他格式的标识)。若该RN的DRB的状态报告不包括DRB标识，则RN的DRB的状态报告可以由按照一定顺序排列的多个终端的DRB的状态报告组成。这里的排列顺序可以为协议预先规定的，也可以为按照DRB标识由大到小或者由小到大的顺序排列。
需要说明的是，在这种情况下，每个RN的DRB均对应一个IAB功能协议层实体(entity)。或者，RN的DRB的状态报告不区分其承载的终端的DRB，通过携带RN的DRB内的SN，反馈RN的DRB的传输情况。具体的，RN的DRB的状态报告包括以下内容中的任一种或任意多种的组合：最大的成功发送/接收的RN DRB SN，一个传输空洞(指一个或SN连续的多个未成功发送/接收的数据包)的最大RN DRB SN和最小RN DRB SN、传输空洞序号、最大的连续成功发送/接收的RN DRB SN、一个传输成功数据块的最大RN DRB SN和最小RN DRB SN、传输成功数据块序号、最大的发送/接收的RN DRB SN、成功发送的RN DRB SN，丢失的RN DRB SN，RN标识，DRB标识，RN DRB标识。
可选的，RN的DRB的状态报告可以包括该RN的Un接口的所有DRB的状态报告，也可以为包括其下一跳RN的所有DRB的状态报告。此时，RN的DRB状态报告还包括RN标识和/或DRB标识，或者包括用于识别RN DRB的信息。若不携带DRB 标识，则RN的DRB状态报告可以由多个按照一定的顺序排列的RN的DRB的状态报告组成。这里的顺序可以为协议预先规定的，也可以为按照DRB标识由大到小或者由小到大的顺序排列。
可选的，若将RN视为终端，则RN也可以生成自身DRB的Un口的RLC状态报告，本申请实施例将该状态报告称为RN RLC状态报告。
RN RLC状态报告包括以下内容中的任一种或任意多种的组合：最大的成功发送的RN RLC SN、成功发送的RN RLC SN、丢失的RN RLC SN、一个传输空洞的最大RN RLC SN和最小RN RLC SN、传输空洞序号、RN标识，DRB标识。
RN基于上述RN RLC状态报告在IAB功能协议层生成RN的状态报告。具体的，RN的状态报告由该RN的部分或全部RN RLC状态报告组成。需要说明的是，在这种情况下，一个RN上有一个IAB功能协议层实体，该RN的所有DRB均对应这个IAB功能协议层实体。可选的，RN的状态报告还包括RN标识和/或DRB标识，或者包括用于识别RN DRB的信息。若RN的状态报告未包括DRB标识，则上述状态报告可以为多个按照一定的顺序排列的RN RLC状态报告组成。或者，RN的状态报告仅包含一个RN DRB对应的RN RLC状态报告，此时IAB功能协议层实体可以为per RN DRB的，即一个RN DRB对应一个IAB功能协议层实体。
本申请实施例中的状态报告可以是周期上报的，也可以是事件触发上报的，本申请实施例对此不做具体限定。
其中，周期上报可以用于数据锚点(例如宿主基站系统)根据上述状态报告删除已经被成功发送的数据包。示例性的，在数据锚点内部，当与终端对等的PDCP实体(简称为终端的PDCP实体)将PDCP PDU发送给IAB功能协议层后，终端的PDCP实体将上述PDCP PDU删除，IAB功能协议层缓存下行终端的PDCP PDU，当收到的状态报告反馈终端已经正确收到该PDCP PDU后删除该PDCP PDU。此外，周期上报还可以用于数据锚点内部。示例性的，在数据锚点内部，当终端的PDCP实体将PDCP PDU通过下层发送后，终端的PDCP实体继续缓存上述PDCP PDU，数据锚点接收状态报告得知终端已经正确收到该PDCP PDU后会通知终端的PDCP实体删除该PDCP PDU。
事件触发上报状态报告的场景中，该事件可以为：终端切换、终端发生无线链路失败(Radio Link Failure，RLF)、RN切换、RN发生RLF或收到polling指示(示例性的，该polling指示为IAB功能协议层生成的指示信息)。
示例性的，终端从源节点切换到目标节点时，需要进行源节点到目标节点的数据转发。此时，若数据锚点缓存了上述需要转发的数据，则该终端的源节点可以向数据锚点反馈该终端的状态报告，或者一个或若干个终端的DRB的状态报告，用于数据锚点向目标节点转发未向该终端发送成功的数据。其中，数据锚点可以为源节点与目标节点的共同的上一跳或上n(n>1)跳RN，也可以为源节点与目标节点共同的宿主基站(例如：与终端对等的PDCP置于在宿主基站，终端没有成功收到的PDCP PDU可能还缓存在宿主基站上)。也就是说，终端切换前后，终端的数据均需要经过该数据锚点的中继传输。可选的，若数据锚点为与源节点与目标节点直接通过空口相连的上一跳RN/宿主基站，则源节点可以向数据锚点反馈该终端的RLC状态报告。其中，源 节点可以为RN，目标节点可以为RN或者宿主基站。特殊的，目标节点与数据锚点是同一个节点。由于数据锚点需要将终端未成功接收的数据发送到目标节点，以便目标节点发送给该终端，因此，数据锚点需要获知目标节点的信息，可以基于以下方式：方式一、源节点告知数据锚点，例如通过切换准备过程，源节点提前与目标节点进行协商，并将目标节点的信息告知数据锚点；方式二、目标节点告知数据锚点，例如当该终端由该目标节点接入后，目标节点通知数据锚点，从而令数据锚点将终端的数据路径由源节点切换到目标节点。
可选的，当终端从目标节点接入后，可以发送针对自身DRB传输情况的状态报告，用于明确告知目标节点/数据锚点其未成功接收的数据包。这种做法的好处是，终端的服务节点或中间转发节点针对该终端的DRB反馈状态报告时，其中指示的终端未成功收到的数据包可能终端已经成功收到，但是还未来得及发送确认(ACK)反馈，因此，终端可以在接入目标节点后提供更加精确的状态报告，避免发送重复数据造成的空口资源浪费。通过终端自己发送状态报告给数据锚点，可以避免数据锚点将终端已经成功收到但是还未来得及发送确认(ACK)反馈的数据包发送给目标节点；或者，若数据锚点将上述终端已经成功收到但是还未来得及发送确认(ACK)反馈的数据包发送给目标节点，通过终端自己发送状态报告给目标节点，可以避免目标节点将终端已经成功收到但是还未来得及发送确认(ACK)反馈的数据包发送给终端。
示例性的，当终端发生RLF后，该终端在目标节点提供的小区内进行RRC连接重建立立，目标节点通知原服务节点该终端发生RLF，原服务节点可以将该终端的数据转发给目标节点。此时，若数据锚点缓存了上述需要转发的数据，则该终端的原服务节点可以向数据锚点反馈该终端的状态报告，或者若干个终端的DRB的状态报告，用于数据锚点向目标节点转发未向该终端发送成功的数据。其中，数据锚点可以为原服务节点与目标节点的共同的上一跳或上n(n>1)跳RN，也可以为原服务节点与目标节点共同的宿主基站(例如：与终端对等的PDCP置于在宿主基站，终端没有成功收到的PDCP PDU可能还缓存在宿主基站上)。也就是说，终端的RRC连接重建立前后，终端的数据均需要经过该数据锚点的中继传输。可选的，若数据锚点为与原服务节点与目标节点直接通过空口相连的上一跳RN，则原服务节点可以向数据锚点反馈该终端的RLC状态报告。其中，原服务节点可以为RN，目标节点可以为RN或者宿主基站。特殊的，目标节点与数据锚点是同一个节点。由于数据锚点需要将终端未成功接收的数据发送到目标节点，以便目标节点发送给该终端，因此，数据锚点需要获知目标节点的信息，可以基于以下方式：方式一、原服务节点告知数据锚点，例如原服务节点提前配置目标节点给终端，并提前将目标节点的信息告知数据锚点；方式二、目标节点告知数据锚点，例如当该终端由该目标节点接入后，目标节点通知数据锚点，从而令数据锚点将终端的数据路径由原服务节点切换到目标节点。
可选的，与终端发生切换的场景类似，当终端从目标节点接入后，可以发送针对自身DRB传输情况的状态报告，用于明确告知目标节点/数据锚点其未成功接收的数据包。
示例性的，RN从源节点切换到目标节点时，需要完成源节点到目标节点的数据转发。此时若数据锚点缓存了上述需要转发的数据，则该RN的源节点可以向数据锚 点反馈该RN的状态报告，或者一个或若干个RN的DRB状态报告(其中承载了该RN服务的终端的数据)，用于数据锚点向目标节点转发未向该RN发送成功的数据。或者，RN切换之后，部分终端的数据(所有DRB或部分DRB)不会继续通过该RN中继传输，或者部分终端不再由该RN服务，则源节点需要向数据锚点反馈这些终端的终端DRB的状态报告。其中数据锚点为源节点与目标节点的共同的上一跳或上n(n>1)跳RN，或者为源节点与目标节点共同的宿主基站(例如：与终端对等的PDCP置于在宿主基站，终端没有成功收到的PDCP PDU可能还缓存在宿主基站上)。即该RN切换前后，RN的数据(例如：包括该RN服务的终端的数据以及该RN服务的下一跳RN的数据)均需要经过该数据锚点的中继传输。若数据锚点为与源节点与目标节点直接通过空口相连的上一跳RN/宿主基站，则源节点可以向数据锚点反馈该RN的RLC状态报告。其中，源节点可以为RN，目标节点可以为RN或者宿主基站。特殊的，目标节点与数据锚点是同一个节点。由于数据锚点需要将终端未成功接收的数据发送到目标节点，以便目标节点发送给该RN，因此，数据锚点需要获知目标节点的信息，可以基于以下方式：方式一、源节点告知数据锚点，例如通过切换准备过程，源节点提前与目标节点进行协商，并将目标节点的信息告知数据锚点；方式二、目标节点告知数据锚点，例如当该RN由该目标节点接入后，目标节点通知数据锚点，从而令数据锚点将RN的数据路径由源节点切换到目标节点。
可选的，当RN从目标节点接入后，可以发送针对自身的数据传输情况的状态报告，用于明确告知目标节点/数据锚点其未成功接收的数据包。这种做法的好处是，RN的服务节点或中间转发节点针对该RN的数据反馈状态报告时，其中指示的RN未成功收到的数据包可能RN已经成功收到，但是还未来得及发送确认(ACK)反馈，因此，RN可以在接入目标节点后提供更加精确的状态报告，避免发送重复数据造成的空口资源浪费。通过RN自己发送状态报告给数据锚点，可以避免数据锚点将RN已经成功收到但是还未来得及发送确认(ACK)反馈的数据包发送给目标节点；或者，若数据锚点将上述RN已经成功收到但是还未来得及发送确认(ACK)反馈的数据包发送给目标节点，通过RN自己发送状态报告给目标节点，可以避免目标节点将RN已经成功收到但是还未来得及发送确认(ACK)反馈的数据包发送给RN。
示例性的，当RN发生RLF后，该RN在目标节点提供的小区内进行RRC连接重建立，原服务节点获知该RN发生RLF(例如：目标节点通知原服务节点该RN发生RLF)，原服务节点可以将该RN的数据转发给目标节点。此时，若数据锚点缓存了上述需要转发的数据，则该RN的原服务节点可以向数据锚点反馈该RN的状态报告，或者若干个RN的DRB状态报告，用于数据锚点向目标节点转发未向该RN发送成功的数据。或者，RN RRC连接重建之后，部分终端的数据(所有DRB或部分DRB)不会继续通过该RN中继传输，或者部分终端不再由该RN服务，则源节点需要向数据锚点反馈这些终端的终端DRB的状态报告。其中数据锚点为原服务节点与目标节点的共同的上一跳或上n(n>1)跳RN，或者为原服务节点与目标节点共同的宿主基站(例如与终端对等的PDCP置于在宿主基站，终端没有成功收到的PDCP PDU可能还缓存在宿主基站上)。即该RN RRC连接重建立前后，RN的数据均需要经过该数据锚点的中继传输。若数据锚点为与原服务节点与目标节点直接通过空口相连的上一 跳RN，则原服务节点可以向数据锚点反馈该RN的RLC状态报告。其中，原服务节点可以为RN，目标节点可以为RN或者宿主基站。特殊的，目标节点与数据锚点是同一个节点。由于数据锚点需要将RN未成功接收的数据发送到目标节点，以便目标节点发送给该RN，因此，数据锚点需要获知目标节点的信息，可以基于以下方式：方式一、原服务节点告知数据锚点，例如原服务节点提前配置目标节点给RN，并提前将目标节点的信息告知数据锚点；方式二、目标节点告知数据锚点，例如当该RN由该目标节点接入后，目标节点通知数据锚点，从而令数据锚点将RN的数据路径由原服务节点切换到目标节点。
可选的，与RN发生切换的场景类似，当RN从目标节点接入后，可以发送针对自身数据传输情况的状态报告，用于明确告知目标节点/数据锚点其未成功接收的数据包。
需要说明的是，对于上述几种情况，若数据锚点不是RN上一跳节点，则RN上一跳节点需要将收到的状态报告作为发送该状态报告的节点的数据向上路由，发送至数据锚点。
以图11所示的协议栈和图2所示的连接关系为例，UE3接入RN3，并通过RN2和RN1与宿主基站进行数据传输，RN2生成Un3口的RN3的DRB的状态报告。具体的，一种可能的方式为，RN2的与RN3对等的IAB功能协议层实体生成该状态报告，并将该状态报告发送给RN2的与RN1对等的IAB功能层实体，以便RN2通过Un2口将该状态报告发送给RN1；另一种可能的方式为，RN2的与RN1对等的IAB功能层实体生成该状态报告，可选的，RN2的与RN3对等的IAB功能协议层实体将Un3口的数据包的发送/接收状态告知RN2的与RN1对等的IAB功能层实体。由于对于某一个终端的多个DRB在不同的Un口上可能有不同的映射方式，因此上述状态报告的路由方式可能有多种实现方式。对于IAB功能协议层实体是per RN DRB的情况，例如一个终端的DRB1和DRB2承载在Un3口的RN3的DRB1上，但是在Un2口，终端的DRB1承载在RN2的DRB1，终端的DRB2承载在RN2的DRB2，RN2在Un2口发送的状态报告应该为在RN2的DRB1中反馈终端的DRB1的传输状态，在RN2的DRB2中反馈终端的DRB2的传输状态。类似的，RN1收到上述反馈终端DRB传输情况的DRB时，应该在自身的DRB上传输承载在该RN1 DRB中的终端DRB的传输状态。即，中间转发节点对状态报告进行转发时，需要对状态报告进行重组，将状态报告中包含的终端DRB状态报告按照自身RN DRB进行聚合，将承载在一个RN DRB中的终端DRB状态聚合成一个状态报告，并在该RN DRB中传输。
3、传输控制面消息
对应的，本申请实施例中的第一数据为控制面消息。
上述F1-like接口可以传输接口控制面消息，与F1AP类似的，称为F1AP-like信令流程/消息。一种可选的方式是，F1AP-like信令流程和消息与F1AP一致，或者基于F1AP基础上进行扩展。这样能够直接复用现有接口流程，减少标准化工作。
与F1AP类似的，F1AP-like消息可以分为两类：公共消息(Common message，或者Non UE-associated)和UE相关(UE associated)消息。
可选的，RN与宿主基站系统之间建立F1-like接口后，二者之间存在一个逻辑 F1-like连接(logical F1-like connection)，不同的RN与宿主基站系统之间的逻辑F1-like连接不同，不同RN的F1AP-like消息可以通过承载的逻辑F1-like连接来区分。可选的，逻辑F1-like连接可以使用以下信息中的任一种或多种的组合来识别：控制面传输层信息(如果有)、第二指示信息、终端在F1-like接口的标识(UE F1-like ID)、第三指示信息。其中，控制面传输层信息即为F1-like接口的传输层协议携带的信息。示例性的，若F1-like接口的传输层协议层包括IP层，则控制面传输层信息包括：宿主基站系统的IP地址和/或RN的IP地址。示例性的，若F1-like接口的传输层协议层包括SCTP层，则控制面传输层信息包括：宿主基站系统的端口号和/或RN的端口号，SCTP的流标识(Stream Identifier)，SCTP的负载协议标识(Payload Protocol Identifier)等。简单的说，控制面传输层信息可以包括以下信息中的任一种或任意多种的组合：宿主基站系统的IP地址，RN的IP地址，宿主基站系统的端口号，RN的端口号，SCTP的流标识，以及SCTP的PPI等。第二指示信息用于指示与宿主基站系统建立该F1-like接口的RN。示例性的，第二指示信息可以为当RN作为UE接入时的UE标识(例如C-RNTI，S-TMSI，GUTI等)，也可以为当RN作为UE接入时，上一跳RN为其分配的F1-like接口标识(例如UE F1AP ID，或者UE F1AP-like ID)，还可以为当RN作为UE接入后，从UE模式转换为RN模式后的RN ID(可选的，该RN ID可以为OAM配置，或者宿主基站系统分配，或者为预配置的)。可选的，若将RN视为一个DU，则第二指示信息可能与DU标识具有相同的格式。可选的，该第二指示信息可以为一个全局标识，其由RN局部标识和RN跳数组成。可选的，RN局部标识可以为该RN的上一跳节点(例如RN或者宿主基站系统中的DU)分配的。第三指示信息用于指示F1-like接口，以区分不同RN的逻辑F1-like连接。
可选的，在一个RN与宿主基站系统之间，可以为该RN服务的终端建立一个终端相关逻辑F1-like连接。可选的，该终端相关逻辑F1-like连接可以采用以下信息中的任一种或任意多种的组合来区分不同终端：用于指示终端的第四指示信息，终端的服务节点的标识。
其中，第四指示信息可以为以下信息中的任一种或任意多种的组合：F1-like接口UE ID(UE F1AP-like ID)、C-RNTI、cell ID、上下文标识(Context ID)等。进一步可选的，第四指示信息为终端标识与RN标识的组合。
需要说明的是，若终端接入某RN提供的小区，或者终端直接与某RN通过空口相连，或者某RN为终端提供Uu口，或者某RN为终端提供空口传输的无线资源，本申请实施例将该RN称为为该终端服务的RN，该终端称为该RN服务的终端。
4、传输终端的RRC消息
对应的，本申请实施例中的第一数据为终端的RRC消息。
IAB功能协议层在获取到终端的RRC消息后，发送包括该终端的RRC消息和与该RRC消息对应的类型标识的第一消息。
可选的，UE的RRC消息可以承载于F1AP-like消息中传输，也可以直接通过IAB功能协议层传输，例如，直接承载在IAB功能协议层的PDU中。
5、携带路由信息
上述第一消息可以包括目标标识，该目标标识用于指示终端的服务节点。第一通 信设备根据该目标标识确定控制面消息或用户面数据的目标设备，从而进行处理和/或转发。
可选的，目标标识可以为终端的服务节点的标识或终端的服务节点的IP地址。
进一步地，上述第一消息还包括第六指示信息，该第六指示信息用于指示第一数据属于该终端或第一数据与该终端相关。
6、携带类型标识
类型标识用于表示第一数据的类型，这样，接收到上述第一消息的设备可基于数据类型进行不同的处理。
由上述几个功能的描述可知，IAB功能协议层可以用于传输以下数据类型中的任一种或任意多种的组合：F1AP-like控制面消息(可选的，进一步可以分为公共F1AP-like控制面和UE相关的F1AP-like控制面消息)，终端的RRC消息，用户面数据，Uu接口的状态报告，Un接口的状态报告。在通过IAB功能协议层传输上述数据时，可以进一步携带其对应的数据类型，用于接收端识别上述数据类型后，依据对应的功能的处理流程处理。
7、具备压缩功能
上述用户面数据、控制面数据、RRC消息以及状态报告均称为第一数据，IBA功能协议层在获取到第一数据后，根据第一预设压缩算法，压缩第一数据或第一数据中的子信息。其中，子信息包括IP头、SCTP公共头以及SCTP数据块中除目标信息之外的信息中的至少一个，所述目标信息为用户数据、流标识以及PPI中的至少一个；或者包括IP头、UDP头以及GTP头中除TEID之外的信息中的至少一个。
当宿主基站系统与RN之间的F1-like接口的控制面协议栈包括传输层协议层时，宿主基站系统/RN生成上述包括传输协议层信息域的F1AP-like控制面消息时，对其传输协议层信息域进行压缩；当宿主基站系统/RN接收上述F1AP-like控制面消息时，对其传输协议层信息域进行解压缩。可选的，对于宿主基站系统，当其由CU和DU组成时，上述压缩/解压缩由DU进行。
图16示出了现有的SCTP/IP包的格式，以及SCTP包中各个域的格式。对于S1、NG、F1等现有接口，其中携带了有用信息的域包括：源IP地址，目标IP地址，用于IP寻址；源端口号，目标端口号；流标识，用于区分公共消息或UE相关消息；PPI，用于指示对应的AP类型(例如：S1AP为18，NGAP为60，F1AP为62)。其中，F1AP-like消息体应该承载在图16中的User Data域中。对于除F1AP-like消息体以外的其他域，其信息均为静态的，若中间转发节点不需要获取其包括的信息，则可以将其进行压缩。特殊的，将其压缩具体包括将其压缩为零，或者称为删除/剥离上述被压缩的信息；一种可选方式为，被压缩的信息可以通过其他方式(例如控制面消息)告知对端，相应的，解压缩包括恢复被压缩的信息；另一种可选的方式为，被压缩的信息不被对端使用，则相应的，对端无需进行解压缩处理。
可选的，对第一数据的第一子信息进行压缩。第一子信息可以为IP头(例如图16中的IPv6 Header部分)，或者为IP头和SCTP公共头，或者为IP头、SCTP公共头和SCTP数据块中除User Data以外的部分；或者为IP头、SCTP公共头和SCTP数据块中除User Data和流标识以外的部分；或者为IP头、SCTP公共头和SCTP数据块 中除User Data、流标识和PPI以外的部分。
可选的，上述压缩和解压缩由F1-like接口的两端节点(例如:建立该接口的宿主基站和RN)进行，中间转发节点(例如为上述F1AP-like控制面消息进行中继传输的RN)无需进行。
可选的，上述第一预设压缩算法为预配置(例如协议规定)，或由宿主基站系统/运营和管理实体(Operation and management，OAM)配置。具体的，可以由宿主基站系统通过RN的RRC消息配置给RN，也可以是在F1-like接口建立过程中配置给RN，也可以是在F1-like接口建立完成后配置给RN。
可选的，宿主基站系统向RN发送压缩激活/去激活指示，用于指示RN开始使用/停止使用上述压缩功能。
可选的，在传输上述被压缩过的F1AP-like控制面消息时，在数据包中携带压缩指示，用于表示该F1AP-like控制面消息经过了压缩。示例性的，上述压缩指示为1bit信息，“1”为被压缩，“0”为未压缩。
可选的，上述压缩指示携带在IAB功能协议层包头中。
当宿主基站系统与RN之间的F1-like接口的控制面协议栈不包括传输层协议层时，F1AP-like控制面消息的IAB功能协议层数据包携带消息标识，用于区分公共消息或UE相关消息。可选的，携带F1AP-like控制面消息的IAB功能协议层数据包携带AP类型，用于指示对应的AP类型为F1AP-like。示例性的，若F1AP-like协议层与F1AP协议层相同，当宿主基站CU-DU组成时，DU将F1接口收到的F1AP消息的传输协议层域剥离，仅保留F1AP消息体，用于在Un口传输给RN；类似的，当DU从Un口接收到RN发送的F1AP-like控制面消息时，将其作为F1接口上传输的F1AP消息体，增加传输域，用于在F1接口上传输。
类似的，采用上述方式一传输用户面数据时，用户面数据承载在F1-like接口的用户面中传输。
当F1-like接口用户面协议栈包括传输层协议层(例如GTP-U/UDP/IP)时，终端的PDCP PDU承载在GTP-U数据包中。宿主基站系统/RN生成上述包括传输协议层信息域的用户面数据时，对其传输协议层信息域进行压缩；当宿主基站系统/RN接收上述用户面数据时，对其传输协议层信息域进行解压缩。可选的，对于宿主基站系统，当其由CU和DU组成时，上述压缩/解压缩由DU进行。
图19示出了现有的GTP-U数据包的格式，以及GTP-U数据报中各个域的格式。GTP-U数据报携带的有用信息的域包括：源IP地址，目标IP地址，用于IP寻址；源端口号，目标端口号；TEID用于识别一个UE的DRB。对于除UE PDCP PDU以外的其他域，其信息均为静态的，若中间转发节点不需要获取其包括的信息，则可以将其进行压缩。特殊的，将其压缩具体包括将其压缩为零，或者称为删除/剥离上述被压缩的信息；一种可选方式为，被压缩的信息可以通过其他方式(例如控制面消息)告知对端，相应的，解压缩包括恢复被压缩的信息；另一种可选的方式为，被压缩的信息不被对端使用，则相应的，对端无需进行解压缩处理。
可选的，对第一数据的第一子信息进行压缩。第一子信息可以为IP头，或者为IP头和UDP头，或者为IP头、UDP头和GTP头中TEID以外的部分；或者为UDP 头和GTP头。
当F1-like接口用户面协议栈不包括传输层协议层时，F1AP-like用户面数据包括TEID，或者第一指示信息。示例性的，若F1-like用户面数据包携带的TEID与F1接口上的TEID相对应，即对于同一个UE的DRB，其在F1-like接口传输和在F1接口传输时，使用相同的TEID。可选的，当宿主基站系统由CU-DU组成时，DU将F1接口收到的GTP-U数据包的传输协议层域剥离，仅保留TEID和UE的PDCP PDU，用于在Un口传输给RN；类似的，当DU从Un口接收到RN发送的F1AP-like用户面数据包时，将其作为F1接口上传输的F1-U数据包，增加传输域，用于在F1接口上传输。
8、提供空口安全保护
IAB功能协议层为传输的第一数据(例如可以为控制面消息、用户面数据、状态报告)提供完整性保护和/或加密。
对于IAB功能协议层传输的终端的RRC消息和用户面的数据而言，下行经由宿主基站系统内与终端对等的PDCP层进行安全保护，上行，经过终端的PDCP层进行安全保护，因此无需进一步安全保护。但是，对于F1AP-like控制面消息，由于其携带了RN和宿主基站系统的配置信息(例如小区配置信息等)，以及终端相关的配置信息(例如终端的QoS信息等)，为了防止被窃取或篡改，需要进行安全保护。因此，可以由IAB功能协议层对F1AP-like控制面消息进行安全保护。可选的，也可以对其他数据类型进行安全保护。
具体的，安全保护的具体实现方式可以为加密和/或完整性保护，即发送端的IAB功能协议层对需要进行安全保护的数据进行加密和/或完整性保护，接收端的IAB功能协议层对上述数据进行解密和或完整性校验。其中，发送端和接收端需要使用一样的加密/完整性保护的秘钥和算法，加密和完整性保护的秘钥和算法可以相同或者不同。
需要说明的是，当IAB功能协议层置于在RN PDCP协议层中，则上述安全保护功能可以使用RN PDCP的安全保护功能，即使用RN PDCP的加密秘钥和算法，以及完整性保护秘钥和算法，对需要进行安全保护的数据进行安全保护。
结合上述描述，对于上述图12、图14以及图15示出的协议栈而言，图17示出了其第一消息的格式。对于上述图13示出的协议栈而言，图18示出了其第一消息的格式。
对于图14示出的协议栈而言，IAB功能协议层与PDCP层是独立的协议层。特殊的，该IAB功能协议层作为RN RLC层的一部分，例如：作为RN RLC层的子层。此时，IAB功能协议层的数据承载在RN RLC PDU中，例如：作为RLC PDU的内容部分。为了使得RN在读取RLC PDU时能够识别出承载了IAB功能协议层数据的RN RLC PDU，进而按照IAB功能协议层的数据格式解析，在上述RN RLC PDU中添加IAB功能协议层数据指示(例如1比特(bit)指示位)，用于指示该RN RLC PDU中包含IAB功能协议层数据。可选的，该IAB功能协议层数据指示可以包含于RLC头中。图20中的A示出了现有的RLC层的数据包的格式，B示出了本申请实施例中融合了IAB功能的RLC层的数据包的格式。图20中的Oct表示字节。
类似的，对于图15示出的协议栈而言，IAB功能协议层可以置于PDCP层中。 若IAB功能协议层为RN PDCP层的一部分，例如：作为RN PDCP层的子层。此时，IAB功能协议层的数据承载在RN PDCP PDU中，例如：作为PDCP PDU的内容部分。为了使得RN在读取PDCP PDU是能够识别出承载了IAB功能协议层数据的RN PDCP PDU，进而按照IAB功能协议层的数据格式解析，因此，在上述RN PDCP PDU中添加IAB功能协议层数据指示(例如：1bit指示位)，用于指示该RN PDCP PDU中包含IAB功能协议层数据。可选的，该IAB功能协议层数据指示可以包含于PDCP头中。图21中的A示出了现有的PDCP层的数据包的格式，B示出了本申请实施例中融合了IAB功能的PDCP层的数据包的格式。图21中的MAC-1为完整性保护校验位。
从上面描述可知，本申请实施例在RN和宿主基站系统的协议栈中添加了IAB功能协议层，IAB功能协议层能够实现上述1～8的功能。为了使得RN和宿主基站系统能够实现上述1～8的功能，需对RN和宿主基站系统的IAB功能协议层进行初始配置。
现对RN和宿主基站系统的IAB功能协议层的初始配置进行描述。
图22示出了RN 1接入网络的场景中，配置IAB功能协议层的流程。
下述流程中的宿主基站系统可以为独立的宿主基站，也可以由CU和DU组成。若宿主基站系统为独立的宿主基站，则图22中CU与DU之间的交互均为宿主基站系统的内部交互。需要说明的是，宿主基站系统是否进行了CU-DU的切分对RN 1的处理没有影响。具体的，在RN 1向宿主基站系统发送某一消息时，若宿主基站系统由CU和DU组成，则DU通过空口(例如Un1口)接收RN 1发送的消息，进一步，可能需要将该消息发送给CU。在RN 1接收宿主基站系统发送的某一消息时，若宿主基站系统由CU和DU组成，则RN 1接收到的消息可能是DU生成并通过空口发送给RN 1的，或者是CU生成，并通过F1接口发送给DU，再由DU处理后通过空口发送给RN 1的。
如图22所示，该配置方法包括：
S2200(可选的)、若宿主基站系统由CU和DU组成的情况下，DU与CU之间建立F1接口，并通过该F1接口指示各自是否具备支持IAB功能协议层的功能。
若宿主基站系统由CU和DU组成，则会存在该步骤。
具体的，对于DU而言，该DU通过F1AP消息向CU指示其具备支持IAB功能协议层的功能。可选的，该F1AP消息包括用于指示DU具有IAB功能协议层的信息。
CU与DU类似，这里不再详细描述。
S2201(可选的)、宿主基站系统生成与RN接入网络相关的第一配置信息，并发送该第一配置信息。
具体的，若宿主基站系统由CU和DU组成，CU和DU均能为RN提供服务，例如DU支持IAB功能协议层的功能，且CU和DU组成的宿主基站系统能将RN的控制面信令和用户面数据路由到为RN服务的核心网节点，则确定该宿主基站系统能够为RN提供服务，宿主基站系统生成第一配置信息。
可选的，该第一配置信息可以包括用于指示RN的接入控制参数，也可以包括与RN专用的无线资源配置相关的信息(例如：随机接入资源，PUCCH，用于测量的信号的配置，测量上报配置等)。
在生成第一配置信息后，宿主基站系统(例如DU)通过空口广播上述第一配置 信息。
示例性的，第一配置信息为系统消息。
S2202、RN 1向宿主基站系统发送消息1，以请求接入网络。
具体的，RN 1可以发起随机接入过程，并发送消息1以请求建立RRC连接(具体包含新建、恢复和重建的场景)。
消息1可以包括RRC建立请求(RRC Connection Request)消息、RRC连接恢复请求(RRC Connection Resume Request)消息或RRC连接重建立请求(RRC Connection Reestablishment Request)消息。
可选的，在上述随机接入过程，RN 1还可以发送RN指示，以便于宿主基站系统识别出请求建立RRC连接的不是普通的终端，而是一个RN。该RN指示可以包含在MAC数据包中，用于DU解读；或者，RN 1使用RN专用的随机接入资源接入，从而DU可以识别出发起随机接入的不是普通的终端，而是一个RN。
S2203(可选的)、在宿主基站系统由CU和DU组成的情况下，DU通过F1接口，向CU发送消息1包括的RRC消息。
可选的，若DU在随机接入过程识别发起接入的设备为RN，而非普通终端，则判断是否允许该RN接入。若DU确定不允许RN 1接入，则通过F1接口向CU发送通知消息，用于通知CU拒绝RN 1的接入，从而使得CU向RN 1发送用于指示拒绝接入的RRC消息。可选的，DU通知CU拒绝RN 1的接入可采用显示指示，也可隐式指示。
若DU未判断是否允许RN 1的接入，在接收到消息1后将该消息1中RN 1的RRC消息通过F1接口转发给CU。
S2204、宿主基站系统向RN 1发送消息2。
其中，消息2用于指示是否允许RN 1接入。
可选的，消息2可以包括RRC连接建立(RRC Connection Setup)消息、RRC连接恢复(RRC Connection Resume)消息、RRC重建(RRC Connection Reestablishment)消息、RRC连接拒绝(RRC Connection Reject)消息、RRC连接恢复拒绝(RRC Connection Resume Reject)消息或RRC重建拒绝(RRC Connection Reestablishment Reject)消息。
若宿主基站系统由CU和DU组成，则CU接收到DU发送的消息1中的RRC消息后，确定请求接入设备的为RN，进而判断是否允许该RN 1接入，从而生成指示允许或拒绝该RN 1接入的消息2，并通过DU向RN 1发送消息2。
若CU确定允许RN 1接入，则CU生成的消息2用于指示允许RN 1接入。此时，消息2可以包括RRC连接建立(RRC Connection Setup)消息、RRC连接恢复(RRC Connection Resume)消息或RRC重建(RRC Connection Reestablishment)消息。
若CU确定拒绝RN 1的接入，则CU生成用于指示拒绝RN 1接入的消息2。此时，该消息2可以包括RRC连接拒绝(RRC Connection Reject)消息、RRC连接恢复拒绝(RRC Connection Resume Reject)消息或RRC重建拒绝(RRC Connection Reestablishment Reject)消息。
可选的，在CU生成消息2之前，还可以接收DU发送的通知消息，用于指示CU 拒绝该RN 1的接入，从而CU生成用于指示拒绝RN 1接入的消息2。
S2205、若消息2用于指示允许RN 1接入，则RN 1向宿主基站系统发送消息3。
消息3用于指示RRC建立完成。
消息3可以包括RRC连接建立完成(RRC Connection Setup Complete)消息、RRC连接恢复完成(RRC Connection Resume Complete)消息或RRC重建完成(RRC Connection Reestablishment Complete)消息。
可选的，消息3还包括RN 1的标识。
需要说明的是，这里的消息3仅仅是用于说明某一消息，与现有的随机接入过程中的message 3不同。
S2206(可选的)、在宿主基站系统由CU和DU组成的情况下，DU通过F1接口向CU转发消息3中的RRC消息。
S2207、宿主基站系统向RN 1发送包括第二配置信息的消息4，用于指示RN 1根据第二配置信息配置与宿主基站系统对等的IAB功能协议层。
第二配置信息包括安全配置信息和压缩配置信息。
可选的，消息4还包含以下信息中的任一种或任意多种的组合：中继模式(relay mode)激活指示，RB列表，RB的PHY/MAC/RLC配置，小区组配置(cellgroupconfig)RB的PDCP配置，DRB的QoS信息。示例性的，一种可能的情况是，RB的PHY/MAC/RLC配置包含于cellgroupconfig中，cellgroupconfig还包括接入小区的公共配置。
可选的，消息4可以为RRC连接重配置(RRC Connection Reconfiguration)消息，也可以为RRC重配置(RRC Reconfiguration)消息。
在宿主基站系统由CU和DU组成的情况下，CU在接收到上述消息3中的RRC消息之后，通过F1接口向DU发送包括第三配置信息的消息5，第三配置信息用于指示DU完成与RN 1之间对等的IAB功能协议层的配置。
示例性的，上述第三配置信息包括以下信息中的任一种或任意多种的组合：锚秘钥(anchor key)、控制面秘钥、用户面秘钥、加密算法、完整性保护算法、秘钥衍生信息(例如跳数、counter)、压缩激活指示、压缩为零指示、压缩域指示、压缩算法。
可选的，消息5可以为F1AP消息，例如：终端的上下文建立请求(UE context setup request)消息，或者终端的上下文修改请求(UE context modification request)消息。
消息5还包括：RN1的RB列表以及DRB对应的QoS信息。
其中，RB列表包括RB标识。可选的，DRB对应的QoS信息包括以下信息中的至少一种：DRB标识、该DRB的QoS参数以及承载在该DRB的QoS flow的QoS参数。
可选的，DU通过F1接口向CU发送包括第四配置信息的消息6，该消息6用于向CU指示RN 1的IAB功能协议层的配置参数，使得CU生成对应的配置消息(例如RRC消息)，该配置消息用于向RN 1发送。
其中，第四配置信息包括以下信息中的任一种或任意多种的组合：锚秘钥(anchor key)、控制面秘钥、用户面秘钥、加密算法、完整性保护算法、秘钥衍生信息(例如跳数、counter)、压缩激活指示、压缩为零指示、压缩域指示、压缩算法。
可选的，消息6还包含以下信息中的至少一种：RN1的RB列表、RB的PHY/MAC/RLC配置，以及小区组配置(cellgroupconfig)。
通过上述CU与DU之间发送消息5和/或消息6可以实现以下三种配置RN 1中IAB功能协议层的配置参数的方式：
方式一、CU确定DU中IAB功能协议层的配置信息，并通过消息5向DU发送该配置信息，此时，上述的第二配置信息即为上述第三配置信息；
方式二、DU确定该DU中IAB功能协议层的配置信息，并通过消息6向CU发送该配置信息，以便于CU生成对应的RRC消息，用于指示RN 1进行相应配置，此时，上述第二配置信息即为上述第四配置信息；
方式三、CU确定DU中IAB功能协议层的第一子配置信息(即上述第三配置信息)，并通过消息5向DU发送该第一子配置信息；和/或DU确定第二子配置信息(即上述第四配置信息)，并通过消息6向CU发送第二子配置信息；宿主基站系统(可以为CU，或者为DU)基于第一子配置信息和第二子配置信息获得上述第二配置信息。
可选的，第一子配置信息可以为锚秘钥、秘钥衍生信息以及是否进行压缩中的至少一个，第二子配置信息可以为加密算法、完整性保护算法以及压缩算法中的至少一个。
对于方式一和方式三，CU需要获取RN 1的能力信息(例如：是否支持的加密算法/完整性保护算法/压缩算法)。对于方式二和方式三，DU需要获取RN 1的能力信息。
可选的，上述能力信息可以由RN 1通过RRC消息发送至CU，也可以由核心网通过核心网与基站之间的接口(例如NG接口)发送至CU。CU在获取到RN 1的能力信息后，通过F1接口向DU发送RN 1的能力信息。
S2208、RN 1根据第二配置信息配置RN 1的IAB功能协议层。
可选的，RN 1向宿主基站系统发送消息7，用于请求建立F1-like接口。
在宿主基站系统由CU和DU组成的情况下，RN 1根据第二配置信息配置RN 1的IAB功能协议层的方法为：
在一种实现方式中，消息7为RRC消息。在这种情况下，DU并不解析该消息7，而是将该消息7通过F1接口发送至CU。CU在接收到消息7后，为RN 1的F1-like接口建立对应的F1接口，以及通知DU为该F1-like接口建立与RN 1之间Uu口的传输通道。
在另一种实现方式中，消息7为IAB功能协议层/MAC层/RLC层/PHY层消息。在这种情况下，DU解析该消息7，从而为该F1-like接口建立与RN 1之间Uu口的传输通道。
可选的，DU为该F1-like接口建立与RN 1之间Uu口的传输通道包括分配用于传输F1-like接口消息的无线资源，例如SRB，DRB，RLC-bearer等。
可选的，DU请求CU为该F1-like接口建立对应的F1接口。这种情况下，CU为该F1-like接口建立对应的F1接口包括CU将该RN 1视为一个DU，在CU与DU之间为RN 1建立一个F1接口，DU负责将该F1接口上的消息转发给CU或RN 1。
可选的，F1-like接口建立完成后，RN 1开启基站模式，这样，RN 1即可发送系 统消息或接收其他节点的随机接入请求(Random Access Preamble)消息。
此时该网络中各个节点的IAB功能协议层的配置结束。
需要说明的是，本申请实施例所涉及到的RRC消息为LTE定义的RRC消息，本申请也适用于其他系统中定义的与上述RRC消息名称不同但功能相同或类似的消息。另外，本实施例中的步骤也可以分别使用。具体的，S2200-S2201为可选的，本方案的实施不依赖于上述两个步骤；S2202-S2206用于进行宿主基站系统对RN的准入判决，尤其是当宿主基站系统由CU-DU组成时，可能需要CU和DU联合对RN进行准入判决；S2207-S2208用于宿主基站对RN1进行IAB功能的配置，尤其是当宿主基站系统由CU和DU组成时，上述配置需要由CU和DU联合进行，此外，还需要进行DU处与RN1对等的IAB功能层的配置。因此，S2202-S2206与S2207-S2208可以作为两个独立的过程进行应用。
结合上述图22，图23示出了在节点2(终端或RN 2)通过RN 1接入网络的场景中，配置IAB功能协议层的流程。
如图23所示，该配置方法包括：
S2300、在接收到RN 1发送的系统消息后，节点2向RN 1发送消息1。
S2300可以参考上述S2202，此处不再进行详细赘述。
S2301、RN 1向宿主基站系统发送消息1中的RRC消息。
可选的，RN 1将消息1中的RRC消息承载在IAB功能协议层消息中发送至宿主基站系统。
可选的，RN 1在随机接入过程中确定出发起接入的设备为RN，而非普通终端，则判断是否允许该节点2接入，若RN 1确定不允许节点2接入，则通过F1-like接口向宿主基站系统发送通知消息，用于通知拒绝节点2的接入，进而使得宿主基站系统向节点2发送用于指示拒绝接入的RRC消息。
可选的，RN 1通知宿主基站系统拒绝节点2的接入可以采用显示指示或隐式指示。
S2302(可选的)、在宿主基站系统由CU和DU组成的情况下，DU通过F1接口向CU发送其接收到的RRC消息。
S2302可以参考上述S2203的描述，此处不再进行详细赘述。
S2303、宿主基站系统向节点2发送消息8。
其中，消息8用于指示是否允许节点2接入。
可选的，消息8可以包括RRC连接建立(RRC Connection Setup)消息、RRC连接恢复(RRC Connection Resume)消息、RRC重建(RRC Connection Reestablishment)消息、RRC连接拒绝(RRC Connection Reject)消息、RRC连接恢复拒绝(RRC Connection Resume Reject)消息或RRC重建拒绝(RRC Connection Reestablishment Reject)消息。
若宿主基站系统由CU和DU组成，则CU接收到DU发送的RRC消息后，确定请求接入设备是否为RN，进而判断是否允许节点2接入，从而生成指示允许或拒绝该节点2接入的消息8，并通过DU和RN 2向节点2发送消息8。
具体的，CU通过F1接口向DU发送消息8中的RRC消息，DU向RN 1转发消息8中的RRC消息，RN 1向节点2发送消息8中的RRC消息。
若CU确定允许节点2接入，则CU生成的消息8用于指示允许节点2接入。此时，消息8可以包括RRC连接建立(RRC Connection Setup)消息、RRC连接恢复(RRC Connection Resume)消息或RRC重建(RRC Connection Reestablishment)消息。
若CU确定拒绝节点2的接入，则CU生成用于指示拒绝节点2接入的消息8。此时，该消息8可以包括RRC连接拒绝(RRC Connection Reject)消息、RRC连接恢复拒绝(RRC Connection Resume Reject)消息或RRC重建拒绝(RRC Connection Reestablishment Reject)消息。
S2304、若消息8用于指示允许节点2接入，则节点2向RN 1/宿主基站系统发送消息9。
消息9用于指示RRC建立完成。
消息9可以包括RRC连接建立完成(RRC Connection Setup Complete)消息、RRC连接恢复完成(RRC Connection Resume Complete)消息或RRC重建完成(RRC Connection Reestablishment Complete)消息。
可选的，若节点2为RN 2则消息9还包括RN的标识，用于指示发送该消息的设备为RN，并非普通终端。
若节点2向RN 1发送消息9，则RN 1向宿主基站系统发送消息9中的RRC消息。RN 1向宿主基站系统发送消息9中的RRC消息的过程可以参考上述S2205，此处不再进行详细赘述。
S2305(可选的)、在宿主基站系统由CU和DU组成的情况下，DU通过F1接口向CU转发消息9中的RRC消息。
S2306、宿主基站系统向RN 1发送包括第五配置信息和/或第六配置信息的消息10，用于指示RN 1根据第五配置信息和/或第六配置信息进行配置。
可选的，在宿主基站系统由CU和DU组成的情况下，若节点2为RN 2，CU在接收到上述消息9中的RRC消息之后，通过F1接口向DU发送第七配置信息，该第七配置信息用于指示DU进行与节点2对应的IAB功能协议层的配置。
示例性的，上述第七配置信息包含与节点2相关的以下信息中的任一种或任意多种的组合：安全配置信息、压缩配置信息，能力信息。其中，CU获取节点2的能力信息的方式与获取RN 1的能力信息的方式类似，在此不再赘述。
可选的，在宿主基站系统由CU和DU组成的情况下，若节点2为RN 2，CU在接收到上述消息9中的RRC消息之后，CU通过F1接口向DU发送第五配置信息，该第五配置信息用于指示RN 1进行与节点2对应的IAB功能协议层的配置。
示例性的，上述第五配置信息包含与节点2相关的以下信息中的任一种或任意多种的组合：安全配置信息、压缩配置信息，能力信息。
上述第五配置信息和第七配置信息可以包含在不同的消息中，例如第五配置信息包含在消息11中，第七配置信息包含在消息12中。
可选的，上述消息11可能包含于消息12中。这样，第五配置信息与第七配置信息相同，或者第五配置信息为第七配置信息的子集。此时，消息12可以仅包含第七配置信息。
可选的，在宿主基站系统由CU和DU组成的情况下，CU还可以向DU发送第八 配置信息，该第八配置信息用于向DU指示节点2的QoS信息，便于DU根据承载在RN 1的DRB中的节点2的数据的QoS要求，对RN 1的DRB的PHY/MAC/RLC配置进行调整和更新，从而触发CU发RRC重配置消息给RN 1进行重配。
需要说明的是，在这种方式下，CU确定节点2的数据如何映射到RN 1的DRB中，并将节点2的数据的QoS要求(例如：DRB的QoS参数或者QoS flow的QoS参数)发送至DU，便于DU决定是否需要更新承载节点2的数据的RN1的DRB的PHY/MAC/RLC配置。
第八配置信息包括以下信息中的任一种或任意多种的组合：节点2的RB列表、节点2的DRB对应的QoS信息、节点2的DRB与RN 1的DRB的对应关系、节点2的QoS flow列表、节点2的QoS flow对应的QoS信息、节点2的QoS flow与RN 1的DRB的对应关系。其中，QoS flow列表包含QoS flow标识(简称QFI)和/或节点2的DRB标识。
可选的，CU还可以向DU发送第六配置信息，用于向RN 1指示节点2的QoS信息。
第六配置信息包括以下信息中的任一种或任意多种的组合：节点2的RB列表、节点2的DRB对应的QoS信息。
可选的，第六配置信息可以包含在上述消息11/消息12中。
特殊的，第六配置信息是第八配置信息的子集，此时，CU发送第八配置信息给DU，DU基于该第八配置信息生成第六配置信息。上述消息11/消息12可以为F1AP消息，也可以为UE上下文设置请求(UE context setuprequest)或UE上下文修改请求(UE context modification request)消息。
可选的，若消息12包含第七配置信息和/或第八配置信息，消息11包含第五配置信息和/或第六配置信息，则消息12包含的UE/RN F1AP ID用于确定RN 1，能够用于指示DU进行与RN 1之间的空口的配置；消息11包含的UE/RN F1AP ID用于确定节点2，能够用于指示DU进行与节点2对应的空口的配置，和/或将配置信息转发给RN 1，用于RN 1进行与节点2之间的空口的配置。
需要说明的是，第六配置信息和第八配置信息均包含节点2的数据的QoS信息，二者可能不完全相同。示例性的，对于时延相关的参数，若节点2的RAN侧的时延要求为A，则基站系统(例如CU和/或DU)可以进一步将其分解为承载在RN 1 DRB中传输时需要满足的时延要求B和承载在UE DRB中传输是需要满足的时延要求C，并将上述时延要求B包含在第七配置信息中，将时延要求C包含在第八配置信息中。
需要说明的是，如果节点2是终端，则CU无需发送第五配置信息和第七配置信息给DU。若节点2是RN，且IAB功能协议层是逐跳的，则DU无需进行与节点2对应的IAB功能协议层的配置，RN 1需要进行与节点2对应的IAB功能协议层的配置，即CU无需发送第七配置信息，但是需要发送第五配置信息。如果IAB功能协议层是端到端的，即CU发送至节点2的IAB功能协议层消息时，RN 1无需对上述消息进行处理(例如，安全保护/加密)，因此，CU无需发送第五配置信息给RN 1。
可选的，DU基于消息11获取上述第五配置信息和/或第六配置信息，生成消息10；或者，DU接收消息12，并处理消息12(例如：将F1接口的UE/RN F1AP ID更 换为F1-like接口上指示节点2的标识，对消息12中的全部或部分信息进行压缩，对消息12中的全部或部分信息进行安全保护，即根据加密算法和/或完整性保护算法对消息12中的全部或部分信息)。
S2307(可选的)、若网络架构为逐跳架构，且节点2为RN 2，则RN 1根据消息10进行与节点2对等的IAB功能协议层的配置，并向宿主基站系统发送包括第九配置信息的消息13，用于指示宿主基站系统与节点2相关的配置参数，便于宿主基站系统生成对应的配置消息(例如RRC消息)并发送至RN 1。
第九配置信息包含以下信息中的任一种或任意多种的组合：安全配置信息、压缩配置信息，节点2的RB列表以及RB对应的PHY/MAC/RLC配置。
消息13可以为F1AP-like消息，也可以为与UE上下文建立响应(UE context setup response)或UE上下文修改响应(UE context modification response)类似功能的消息。
S2308、在宿主基站系统由CU和DU组成的情况下，DU向CU发送包括第十配置信息的消息14，指示CU与节点2相关的配置参数，用于CU生成对应的配置消息(例如RRC消息)并发送至节点2。
第十配置信息包含以下信息中的任一种或任意多种的组合：安全配置信息、压缩配置信息，节点2的RB列表以及RB对应的PHY/MAC/RLC配置。
可选的，DU发送第十一配置信息给CU，其中，第十一配置信息包含以下信息中的任一种或任意多种的组合：RN1的RB列表以及RB对应的PHY/MAC/RLC配置，用于指示CU生成发送至RN 1的重配至消息，更改RN1的RB的配置。
可选的，第十一配置信息可以包含于消息13或消息14中。
消息13/消息14可以为F1AP消息，也可以为UE上下文建立响应(UE context setup response)消息或UE上下文修改响应(UE context modification response)消息。此时，消息13中的UE/RN F1AP ID用于确定节点2，用于指示CU与节点2相关的配置信息，消息14中的UE/RN F1AP ID用于确定RN 1，用于指示CU与RN 1相关的配置信息。
当节点2为RN时，需要为节点2配置IAB功能协议层，对于其中的安全配置和/或压缩配置可以由CU确定(适用端到端架构，且CU为集中决策锚点)，或者DU决定(适用端到端架构)，或者CU与DU协商决定，或者由RN 1确定(适用于逐跳架构)，或者由CU与RN 1协商决定，或者DU与RN 1协商决定，或者CU、DU与RN 1共同协商决定。
在协商决定的几种方式中，秘钥可以由CU或DU决定，算法可以由RN 1决定。通过上述CU、DU与RN 1之间发送消息10、消息11、消息12、消息13、消息14可以实现上述安全配置和/或压缩配置方式。
需要说明的是，本申请实施例中可先执行S2306-S2308的过程中，发送具体配置信息的先后顺序可以有多种方式，例如按照上述步骤中描述的先后顺序执行，或者DU先发送第十一配置信息给CU后在发送第五配置信息/第六配置信息给RN 1，本申请实施例对此不作具体限定。
S2309、宿主基站系统向RN 1发送消息15。
该消息15包含以下信息中的一种或多种的组合：与节点2对应的IAB功能协议层的配置(例如安全配置信息，压缩配置信息)，RN 1的RB列表，RB的PHY/MAC/RLC 配置，RB的PDCP配置，DRB的QoS信息。
该消息15可以包括RRC连接重配置(RRC Connection Reconfiguration)或RRC重配置(RRC Reconfiguration)消息。
可选的，RN 1收到上述消息后，应用新配置，并回复配置完成的响应消息。
S2310、宿主基站系统向节点2发送消息16。
该消息16包含以下信息中的一种或多种的组合：IAB功能协议层的配置(如果节点2为RN，则该信元出现，否则不出现)、RN mode激活指示(如果节点2为RN，则该信元出现，否则不出现)、节点2的RB列表、RB的PHY/MAC/RLC配置、RB的PDCP配置、DRB的QoS信息。
该消息16可以为RRC连接重配置(RRC Connection Reconfiguration)或RRC重配置(RRC Reconfiguration)消息。
可选的，节点2收到上述消息后，应用新配置，并回复配置完成的响应消息。
需要说明的是，本申请实施例中可先执行S2309，后执行S2310，也可以先执行S2310，后执行S2309，本申请实施例对此不作具体限定。
S2311(可选的)、若节点2为RN 2，则节点2向RN 1发送消息17，用于请求建立F1-like接口。
若消息17为RRC消息，RN 1并不解析该消息17，而是将该消息17通过F1-like接口发送至宿主基站系统。宿主基站系统收到后与图22所示实施例中对消息7的处理类似，即DU通过F1接口发送至CU，CU收到消息17后，为该F1-like接口建立对应的F1接口，以及令DU为该F1-like接口建立与RN 1之间Uu口的传输通道。
若消息17为IAB功能协议层/MAC层/RLC层/PHY消息，RN 1解析该消息17，从而为该F1-like接口建立与节点2之间Uu口的传输通道，可选的，DU请求CU为该F1-like接口建立对应的F1接口。可选的，DU为该F1-like接口建立与RN 1之间Uu口的传输通道包括，分配用于传输F1-like接口消息的无线资源，例如SRB，DRB，RLC-bearer等。可选的，CU为该F1-like接口建立对应的F1接口包括CU将该RN1视为一个DU，在CU与DU之间为RN1建立一个F1接口，DU负责将该F1接口上的消息转发给CU或RN 1。
进一步地，在F1-like接口建立完成后，节点2开启基站模式，这样，节点2即可发送系统消息或接收其他节点的随机接入请求(Random Access Preamble)消息。
此时，该网络中各个节点的IAB功能协议层的配置结束。
另外，本实施例中的步骤也可以分别使用。具体的，S2300-S2305用于进行宿主基站系统/RN1对RN的接入进行准入控制，尤其是当宿主基站系统由CU-DU组成时，可能需要CU和DU联合对节点2进行准入判决；S2306-S2311用于宿主基站对节点2进行配置，尤其是当宿主基站系统由CU和DU组成且节点2为RN时，上述配置需要由CU和DU联合进行，此外，还需要进行DU处和/或RN1处的与节点2对等的IAB功能层的配置。因此，S2300-S2305与S2306-S2311可以作为两个独立的过程进行应用。
进一步地，结合上述图23，图24示出了上述节点2为RN 2，终端通过RN 2、RN 1接入网络的场景中，配置IAB功能协议层的流程。
如图24所示，该配置方法包括：
S2400、终端通过RN 2和RN 1与宿主基站系统建立RRC连接。
具体的，终端向RN 2发送消息3，RN 2将消息3中包含的RRC消息发送给RN 1，RN 1将上述RRC消息发给宿主基站系统。
S2401(可选的)、在宿主基站系统由CU和DU组成的情况下，CU向DU发送第一配置信息，用于向DU通知UE相关的QoS信息，便于DU根据终端的QoS要求更新RN 1 DRB的PHY/MAC/RLC配置。
DU根据承载在RN 1的DRB中的终端的数据的QoS要求，对RN 1的DRB的PHY/MAC/RLC配置进行调整和更新，从而触发CU发RRC重配至消息给RN 1进行重配。
需要说明的是，在该种方式下，由CU确定终端的数据如何映射入RN 1的DRB中，并将终端的数据的QoS要求(例如，DRB的QoS参数，或者QoS flow的QoS参数)发送至DU，便于DU确定是否需要更新承载上述终端的数据的RN 1的DRB的PHY/MAC/RLC配置。
第一配置信息包含以下信息中的任一种或任意多种的组合：终端的RB列表、终端的DRB对应的QoS信息、终端的DRB与RN 1的DRB的对应关系、终端的QoS flow列表、终端的QoS flow对应的QoS信息、终端的QoS flow与RN 1的DRB的对应关系。
可选的，CU通过F1接口向DU发送第二配置信息，用于指示RN 1终端的QoS信息，便于RN 1根据终端的QoS要求更新RN 2 DRB的PHY/MAC/RLC配置。RN 1根据承载在RN 2的DRB中的终端的数据的QoS要求，对RN 2的DRB的PHY/MAC/RLC配置进行调整和更新，从而触发CU发RRC重配至消息给RN 2进行重配。
需要说明的是，在该种方式下，由CU确定终端的数据如何映射入RN 2的DRB中，并将终端的数据的QoS要求(例如DRB的QoS参数，或者QoS flow的QoS参数)发送至DU，令DU转发给RN 1，由RN 1确定是否需要更新承载上述终端的数据的RN 2的DRB的PHY/MAC/RLC配置。
第二配置信息包含以下信息中的任一种或任意多种的组合：终端的RB列表、终端的DRB对应的QoS信息、终端的DRB与RN 2的DRB的对应关系、终端的QoS flow列表、终端的QoS flow对应的QoS信息、终端的QoS flow与RN 2的DRB的对应关系。
可选的，CU通过F1接口向DU发送第三配置信息，用于指示RN 2终端的QoS信息，便于RN 2根据终端的QoS要求提供UE DRB的PHY/MAC/RLC配置参数，便于CU将上述配置参数通过RRC重配至消息发送至UE。
需要说明的是，在该种方式下，由CU确定终端的数据如何映射至终端的DRB中，并将终端的数据的QoS要求(例如DRB的QoS参数，或者QoS flow的QoS参数)发送至DU，令DU转发给RN 1，进一步由RN 1转发给RN 2，由RN 2确定是否需要更新承载上述终端的数据的RN 2的DRB的PHY/MAC/RLC配置。
第三配置信息包含以下信息中的任一种或任意多种的组合：终端的RB列表，终 端的DRB对应的QoS信息、终端的QoS flow列表、终端的QoS flow对应的QoS信息。
这里，第一配置信息、第二配置信息和第三配置信息可以分别包含与第一消息、第二消息和第三消息中。
本实施例中的第一消息、第二消息和第三消息可以为F1AP消息，其中的UE/RN F1AP ID可以分别用于确定RN 1，RN 2和终端，用于DU确定解析第一消息，并基于其中的第一配置信息进行RN 1 DRB配置的更新。DU在确定出第二消息的内容为RN 2相关，则将其转发给RN 1处理。同理，DU在确定出第三消息的内容为UE相关，则将其转发给RN 1，便于RN 1转发给RN 2进行处理。
可选的，第一配置信息、第二配置信息和第三配置信息可以位于第一消息中，DU收到第一消息后，应用第一配置信息，将第二配置信息和第三配置信息发送至RN 1。
特殊的，第二配置信息和/或第三配置信息可以为第一配置信息的子集，DU基于第一配置信息获得第二配置信息和/或第三配置信息。示例性的，第一消息/第二消息/第三消息可以为UE上下文建立请求(UE Context setup request)消息或UE上下文修改请求(UE context modification request)消息。
需要说明的是，第一配置信息、第二配置信息和第三配置信息中均包含终端的数据的QoS要求，三者可能不完全相同。示例性的，对于时延相关的参数，若终端的RAN侧的时延要求为A，则宿主基站系统(例如CU和/或DU)可以进一步将其分解为承载在RN 1 DRB中传输时需要满足的时延要求B、承载在RN 2 DRB中传输是需要满足的时延要求C和承载在UE DRB中传输是需要满足的时延要求D，并将上述时延要求B包含在第一配置信息中，将时延要求C包含在第二配置信息中，将时延要求D包含在第三配置消息中。
S2402、宿主基站系统向RN 1发送第二配置信息和第三配置信息，以便于RN 1解析第二配置信息，确定是否更改RN 2 DRB的配置。若需要更改RN 2 DRB的配置，则RN 1与宿主基站系统通信，便于宿主基站系统通过RN 1将新配置发送至RN 2。
可选的，第二配置信息和第三配置信息可以分别包含于第四消息和第五消息中。示例性的，第四消息和第五消息可以为F1AP-like消息，其中携带的UE/RN ID分别用于识别RN 2、UE，可以令RN 1得知第二配置信息为与RN 2相关的配置，从而进行解析和处理，令RN 1得知第三配置信息是与UE相关的，需要转发给RN 2处理。
可选的，上述第二配置信息和第三配置信息可以包含于第四消息中，RN 1从第四消息中获取第三配置信息，并发送至RN 2。特殊的，第三配置信息包含于第二配置信息中，RN 1通过第二配置信息获取第三配置信息。
S2403、RN 1将第三配置信息发送至RN 2，RN 2基于第三配置信息确定终端的DRB的PHY/MAC/RLC配置参数。
可选的，第三配置信息包含于一个F1AP-like消息中，其中携带的UE ID用于识别UE，可以领RN 2得知第三配置信息为与自己服务的UE相关的，进行解析和处理。
S2404、RN 2发送第四配置信息至RN 1，其中包含终端的RB列表以及RB对应的PHY/MAC/RLC配置。
示例性的，第四配置信息可以包含在类似于UE上下文建立响应(UE Context setup  response)或UE上下文修改响应(UE context modification response)消息的F1AP-like消息中。
S2405、RN 1将RN 2发送的第四配置信息发送至宿主基站系统。
可选的，RN 1还向宿主基站系统发送第五配置信息，其中携带RN 2的RB列表以及RB对应的PHY/MAC/RLC配置，用于令宿主基站系统通过RN 1将更新后的RB配置发送至RN 2。
可选的，上述第四配置信息和第五配置信息可以包含与不同的消息中，例如：第六消息和第七消息。示例性的，第六消息和第七消息可以为F1AP-like消息，其中携带的UE/RN ID用于确定UE和RN 2，用于宿主基站系统得知上述两种配置信息分别发送至终端和RN 2。
上述第四配置信息和第五配置信息也可以包含在相同的消息中，例如第六消息。示例性的，第六消息/第七消息可以为F1AP-like消息，进一步的，可以为与UE上下文建立响应(UE Context setup response)或UE上下文修改响应(UE context modification response)消息类似的F1AP-like消息。
S2406(可选的)、在宿主基站系统由CU和DU组成的情况下，DU将第四配置信息和/或第五配置信息发送至CU。
可选的，DU向CU发送第六配置信息，其中携带RN 1的RB列表以及RB对应的PHY/MAC/RLC配置，用于令CU将更新后的RB配置发送至RN 1。
可选的，上述第四配置信息、第五配置信息以及第六配置信息可以包含与不同的消息中，例如第八消息、第九消息和第十消息中。示例性的，第八消息、第九消息和第十消息可以为F1AP消息，其中携带的UE/RN F1AP ID用于确定UE、RN 2和RN 1，用于宿主基站系统得知上述配置信息分别发送至UE、RN 2和RN 1。
上述第四配置信息、第五配置信息以及第六配置信息也可以包含在相同的消息中，例如第八消息。示例性的，第八消息、第九消息和第十消息可以为与UE上下文建立响应(UE Context setup response)或UE上下文修改响应(UE context modification response)消息类似的F1AP-like消息。
S2407、宿主基站系统基于第四配置信息，向终端发送第十一消息。
第十一消息包含以下信息中的任一种或任意多种的组合：终端的RB列表、RB的PHY/MAC/RLC配置、RB的PDCP配置、DRB的QoS信息。示例性的，该第十一消息为RRC消息，进一步的可以为RRC连接重配置(RRC Connection Reconfiguration)或RRC重配置(RRC Reconfiguration)消息。
可选的，终端收到上述消息后，应用新配置，并回复配置完成的响应消息。
上述第十一消息需要宿主基站系统发送至RN 1，由RN 1发送至RN 2，再由RN 2发送至终端，该过程与宿主基站系统向终端发送RRC消息相同，在此不再赘述。
类似的，终端回复的响应消息也需要由RN 2接收后发送至RN 1，由RN 1发送至宿主基站系统，在此不再赘述。
S2408(可选的)、当RN 2的RB的配置需要更新的时，宿主基站系统基于第五配置信息，向RN 2发送第十二消息。
第十二消息包含以下信息中的任一种或任意多种的组合：RN 2的RB列表、RB 的PHY/MAC/RLC配置、RB的PDCP配置、DRB的QoS信息。
示例性的，该第十二消息为RRC消息，进一步的可以为RRC连接重配置(RRC Connection Reconfiguration)或RRC重配置(RRC Reconfiguration)消息。
可选的，RN 2收到上述消息后，应用新配置，并回复配置完成的响应消息。上述第十二消息需要宿主基站系统发送至RN 1，由RN 1发送至RN 2，该过程与宿主基站系统向RN 2发送RRC消息相同，在此不再赘述。
类似的，RN 2回复的响应消息也需要由RN 1接收到后发送至宿主基站系统，在此不再赘述。
S2409(可选的)、当RN 1的RB的配置需要更新时，宿主基站系统基于第七配置信息，向RN 1发送第十三消息。
第十三消息包含以下信息中的任一种或任意多种的组合：RN 1的RB列表、RB的PHY/MAC/RLC配置、RB的PDCP配置、DRB的QoS信息。示例性的，该第十三消息为RRC消息，进一步的可以为RRC连接重配置(RRC Connection Reconfiguration)或RRC重配置(RRC Reconfiguration)消息。
可选的，RN 1收到上述消息后，应用新配置，并回复配置完成的响应消息。
在宿主基站系统由CU和DU组成的情况下，上述第十三消息需要宿主基站系统的CU发送至DU，由DU发送至RN 1，该过程与宿主基站系统向RN 1发送RRC消息相同，在此不再赘述。
类似的，RN 1回复的响应消息也需要由DU接收到后发送至CU，在此不再赘述。
需要说明的是，本申请实施例对S2407、S2408以及S2409的执行顺序不作限定。另外，对于S2400-S2406步骤中具体配置信息的发送顺序，本申请也不做限定。例如，可以按照上述步骤中描写的顺序执行。或者，DU先发送第六配置信息给CU，再发送第二配置信息/第三配置信息给RN1；RN1先发送第五配置信息给DU，再发送第三配置信息给RN2。
上述RN 1与图7中的RN 71等效，RN 2与图7中的RN 72等效。
在各个节点的IAB功能协议层配置好之后，通信系统中的各个节点即可基于各自的IAB功能协议层传输数据。
现对本申请实施例中的数据传输方法进行描述。
具体的，结合图7示出的通信系统，如图25所示，本申请实施例提供的数据传输方法包括：
S250、第一通信设备获取第一数据。
S251、第一通信设备向第二通信设备发送包括类型标识与第一数据的第一消息。
这里，第一通信设备为中间转发节点、终端的服务节点、宿主基站或者宿主基站系统中的DU。
当第一通信设备为中间转发节点时，第二通信设备为中间转发节点的上一跳设备或下一跳设备。例如，第一通信设备为RN 71，则第二通信设备为RN 72或DU 730。
当第一通信设备为终端的服务节点时，第二通信设备为终端的服务节点的上一跳设备。例如：第一通信设备为RN 72，第二通信设备为RN 71。
当第一通信设备为宿主基站或者DU时，第二通信设备为第一通信设备的下一跳 设备。
第一数据的类型为用户面数据、状态报告、控制面消息以及终端的RRC消息。
结合上述描述可知，若第一数据为用户面数据，第一消息包括第一指示信息以及用户面数据的全局SN。
若第一数据为状态报告，第一数据包括终端的DRB承载的用户面数据的全局SN，第一数据用于指示第三通信设备的DRB数据包的传输情况，第三通信设备为终端、中间转发节点或终端的服务节点。
若第一数据为控制面消息，第一消息包括第一接口的传输层协议层信息、第二指示信息、终端在第一接口的标识以及第三指示信息中的至少一个。这里，第一接口为第一通信设备与第二通信设备之间的逻辑通信接口，即上述F1-like接口。逻辑通信接口与物理接口相反，物理接口可以指空口，如Un接口。第一接口的传输层协议层信息包括第一通信设备的IP地址、第二通信设备的IP地址、宿主基站或DU的IP地址、第一通信设备的端口号、第二通信设备的端口号、宿主基站或DU的端口号、SCTP的流标识以及SCTP的PPI中的至少一个，第二指示信息用于指示第一通信设备，第三指示信息用于指示第一接口；或者，第一消息包括第四指示信息和终端的服务节点的标识中的至少一个，第四指示信息用于指示终端。
结合上述IAB功能协议层的功能描述可知，当第一数据为状态报告时，第一数据还包括于指示终端的DRB的第五指示信息。若上述第三通信设备为中间转发节点或终端的服务节点，则第一数据具体包括第三通信设备的至少一个DRB中的每个DRB承载的第五指示信息。
不论第一数据的类似是上述哪一种，本申请实施例中的第一消息还包括目标标识和用于指示终端的第六指示信息中的至少一个。目标标识用于指示终端的服务节点。
第一指示信息、第二指示信息、第三指示信息、第四指示信息、第五指示信息以及第六指示信息可参考上述描述，这里不再进行详细赘述。
具体的，当第一数据为控制面消息、且第一消息包括终端在第一接口的标识或第四指示信息时，第一通信设备获取第一数据的方法为：第一通信设备接收包括第二数据的第二消息，该第二数据包括第七指示信息，第七指示信息用于指示终端或终端的DRB；第一通信设备获取第二数据，并将第七指示信息替换为终端在第一接口的标识或第四指示信息，生成第一数据。第一通信设备在生成第一数据后，生成第一消息，并向第二通信设备发送第一消息。可以看出，这一过程，第一通信设备实质上是将第七指示信息替换为第一接口的标识或第四指示信息。
需要说明的是，当第一通信设备为终端的服务节点时，上述第一通信设备获取第一数据的方法适用于上行传输过程。当第一通信设备为宿主基站或宿主基站系统中的DU时，上述第一通信设备获取第一数据的方法适用于下行传输过程。当第一通信设备为中间转发节点时，上述第一通信设备获取第一数据的方法既适用于上行传输过程，也适用于下行传输过程。
可选的，第一通信设备在获取到第一数据之后，还根据第一预设压缩算法，压缩第一数据或第一数据中的子信息。这样，第一通信设备向第二通信设备发送包括压缩后的第一数据的第一消息。
其中，子信息包括IP头、SCTP公共头以及SCTP数据块中除目标信息之外的信息中的至少一个，目标信息为数据、流标识以及PPI中的至少一个；或者，子信息包括IP头、UDP头以及GTP头中除TEID之外的信息中的至少一个。
需要说明的是，当第一通信设备为终端的服务节点时，上述压缩方法适用于上行传输过程。当第一通信设备为宿主基站或宿主基站系统中的DU时，上述压缩方法适用于下行传输过程。当第一通信设备为中间转发节点时，上述压缩方法既适用于上行传输过程，也适用于下行传输过程。
若第一通信设备为中间转发节点，则该第一通信设备获取第一数据的方法为：第一通信设备接收第四通信设备发送的第三消息，第三消息包括第二数据；第一通信设备从第三消息中获取第二数据，并根据第二预设压缩算法，解压缩第二数据，得到第一数据。其中，若第二通信设备为第一通信设备的上一跳设备，第四通信设备为第一通信设备的下一跳设备。若第二通信设备为第一通信设备的下一跳设备，第四通信设备为第一通信设备的上一跳设备。
若第一通信设备为终端的服务节点，则该第一通信设备还接收第二通信设备发送的第四消息，第四消息包括第三数据；第一通信设备根据第三预设压缩算法，解压缩第三数据，并向终端发送解压后的第三数据。
若第一通信设备为DU，则该第一通信设备还接收第二通信设备发送的第五消息，该第五消息包括第四数据；该第一通信设备根据第四预设压缩算法，解压缩第四数据，并向宿主基站系统中的CU发送解压后的第四数据。
若第一通信设备为DU，则该第一通信设备获取第一数据的方法为：该第一通信设备接收CU发送的包括第五数据的第六消息；该第一通信设备从第六消息中获取第五数据，并根据第五预设压缩算法，解压缩第五数据，得到第一数据。
可选的，第一通信设备在获取到第一数据之后，还根据第一预设秘钥和第一预设目标算法，处理第一数据，并向第二通信设备发送包括处理后的第一数据的第一消息。
第一预设目标算法包括预设加密算法和第一预设完整性保护算法中的至少一种。因此，上述第一通信设备根据根据第一预设秘钥和第一预设目标算法，处理第一数据的过程实质上为对第一数据进行安全保护。
需要说明的是，当第一通信设备为终端的服务节点时，上述安全保护的方法适用于上行传输过程。当第一通信设备为宿主基站或宿主基站系统中的DU时，上述安全保护方法适用于下行传输过程。当第一通信设备为中间转发节点时，上述安全保护方法既适用于上行传输过程，也适用于下行传输过程。
当第一通信设备为中间转发节点时，该第一通信设备获取第一数据的方法为：接收第五通信设备发送的第七消息，该第七消息包括第六数据；获取第六数据，并根据第二预设秘钥和第二预设目标算法，处理第六数据，得到第一数据。
第二预设目标算法包括第一预设解密算法和第二预设完整性保护算法中的至少一种。
可以理解的是，若第二通信设备为第一通信设备的上一跳设备，第五通信设备为第一通信设备的下一跳设备。若第二通信设备为第一通信设备的下一跳设备，第五通信设备为第一通信设备的上一跳设备。
若第一通信设备为终端的服务节点，则该第一通信设备还接收第二通信设备发送的第八消息，第八消息包括第七数据；该第一通信设备获取第七数据，并根据第三预设秘钥和第三预设目标算法，处理第七数据；该第一通信设备向终端发送处理后的第七数据。
第三预设目标算法包括第二预设解密算法和第三预设完整性保护算法中的至少一种。
若第一通信设备为DU，则该第一通信设备还接收第二通信设备发送的第九消息，第九消息包括第八数据；该第一通信设备获取第八数据，并根据第四预设秘钥和第四预设目标算法，处理第八数据；该第一通信设备向宿主基站系统的CU发送处理后的第八数据。
其中，第四预设目标算法包括第三预设解密算法和第四预设完整性保护算法中的至少一种。
对于图7示出的通信系统，图25所描述的实施例描述了中间转发点在上行/下行数据传输过程中传输数据的方法，也描述了终端的服务节点在上行/下行数据传输过程中传输数据的方法，还描述了宿主基站系统在下行数据传输过程中传输数据的方法。
现在对宿主基站在上行数据传输过程中传输数据的方法进行说明。
具体的，结合图7示出的通信系统，如图26所示，本申请实施例提供的数据传输方法包括：
S260、宿主基站接收第一通信设备发送的包括第一数据以及类型标识的第一消息。
类型标识用于表示第一数据的类型，第一数据的类型包括用户面数据、状态报告、控制面消息以及终端的RRC消息中的至少一个。
S261、宿主基站根据类型标识，确定第一数据的类型。
S262、宿主基站根据第一数据的类型，处理第一数据。
本实施例中的第一消息与上述第一消息相同，此处不再进行详细赘述。
若第一数据为状态报告，宿主基站处理第一数据的方法为：该宿主基站根据第一数据，向第二通信设备发送第一数据指示的未被成功接收的第二通信设备的DRB数据包。
可选的，在S262之前，宿主基站还接收第一通信设备或第三通信设备发送的第六指示信息，该第六指示信息用于指示通过第三通信设备向第二通信设备发送第一数据指示的未被成功接收的第二通信设备的DRB数据包。这样，宿主基站处理第一数据的方法为：该宿主基站根据第一数据，通过第三通信设备向第二通信设备发送第一数据指示的未被成功接收的第二通信设备的DRB数据包。
综上所述，对于不同类型的数据，本申请实施例提供的数据传输方法采用统一的消息格式传输，这样，可有效的降低多跳中继网络中的各个节点处理具有该格式的消息的时间。
本申请实施例提供一种数据传输装置300，该数据传输装置300为第一通信设备或第一通信设备中的芯片。第一通信设备为中间转发节点、终端的服务节点、宿主基站或者宿主基站系统中的DU。该数据传输装置300用于执行以上数据传输方法中的第一通信设备所执行的步骤。本申请实施例提供的数据传输装置300可以包括相应步 骤所对应的模块。
本申请实施例可以根据上述方法示例对数据传输装置300进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
在采用对应各个功能划分各个功能模块的情况下，图27示出数据传输装置300的一种可能的结构示意图。如图27所示，数据传输装置300包括获取单元30、发送单元31、接收单元32、替换单元33、压缩单元34、解压缩单元35、安全保护单元36、安全处理单元37。获取单元30用于支持该数据传输装置300执行上述实施例中的S250，和/或用于本文所描述的技术的其它过程；发送单元31用于支持该数据传输装置300执行上述实施例中的S251，和/或用于本文所描述的技术的其它过程；接收单元32用于支持该数据传输装置300执行“接收包括第二数据的第二消息”，和/或用于本文所描述的技术的其它过程；替换单元33用于支持该数据传输装置300执行“将第七指示信息替换为终端在第一接口的标识或第四指示信息”，和/或用于本文所描述的技术的其它过程；压缩单元34用于支持该数据传输装置300执行“根据第一预设压缩算法，压缩第一数据中的子信息”，和/或用于本文所描述的技术的其它过程；解压缩单元35用于支持该数据传输装置300执行“用于根据第二预设压缩算法，解压缩第二数据”，和/或用于本文所描述的技术的其它过程；安全保护单元36用于支持该数据传输装置300执行“根据第一预设秘钥和第一预设目标算法，处理第一数据”，和/或用于本文所描述的技术的其它过程；安全处理单元37用于支持该数据传输装置300执行“根据第三预设秘钥和第三预设目标算法，处理获取到的第七数据”，和/或用于本文所描述的技术的其它过程。当然，本申请实施例提供的数据传输装置300包括但不限于上述模块，例如数据传输装置300还可以包括存储单元。存储单元可以用于存储该数据传输装置300的程序代码。其中，上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
当数据传输装置300为终端的服务节点或中间转发节点时，上述获取单元30、替换单元33、压缩单元34、解压缩单元35、安全保护单元36以及安全处理单元37可以是图9中的处理器91，发送单元31和接收单元32可以是图9中的收发器93，存储单元可以是图9中的存储器92。
当数据传输装置300为宿主基站时，上述获取单元30、替换单元33、压缩单元34、解压缩单元35、安全保护单元36以及安全处理单元37可以是图10中的处理器101，发送单元31和接收单元32可以是图10中的收发器103，存储单元可以是图10中的存储器102。
当数据传输装置300运行时，该数据传输装置300执行如图25所示的实施例的数据传输方法中第一通信设备的步骤。
本申请另一实施例还提供一种计算机可读存储介质，该计算机可读存储介质中存储有指令，当指令在数据传输装置300上运行时，该数据传输装置300执行如图25所示的实施例的数据传输方法中第一通信设备的步骤。
在本申请的另一实施例中，还提供一种计算机程序产品，该计算机程序产品包括计算机执行指令，该计算机执行指令存储在计算机可读存储介质中；数据传输装置300的至少一个处理器可以从计算机可读存储介质读取该计算机执行指令，至少一个处理器执行该计算机执行指令使得数据传输装置300实施执行图25所示的数据传输方法中的第一通信设备的步骤。
本申请实施例提供一种数据传输装置400，该数据传输装置400可以为宿主基站或所述宿主基站中的芯片。该数据传输装置400用于执行以上数据传输方法中的宿主基站所执行的步骤。本申请实施例提供的数据传输装置400可以包括相应步骤所对应的模块。
本申请实施例可以根据上述方法示例对数据传输装置400进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
在采用对应各个功能划分各个功能模块的情况下，图28示出了本实施例中数据传输装置400的一种可能的结构示意图。如图28所示，数据传输装置400包括接收单元40和处理单元41。接收单元40用于指示数据传输装置400执行上述实施例中的S260，和/或用于本文所描述的技术的其它过程；处理单元41用于支持该数据传输装置400执行上述实施例中的S261和S262，和/或用于本文所描述的技术的其它过程。其中，上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。当然，本申请实施例提供的数据传输装置400包括但不限于上述模块，例如数据传输装置400还可以包括存储单元。存储单元可以用于存储该数据传输装置400的程序代码和数据。
上述处理单元41可以是图10中的处理器101，接收单元40可以是图10中的收发器103，存储单元可以是图10中的存储器102。
本申请另一实施例还提供一种计算机可读存储介质，该计算机可读存储介质包括一个或多个程序代码，该一个或多个程序包括指令，当数据传输装置400中的处理器在执行该程序代码时，该数据传输装置400执行如图26所示的数据传输方法。
在本申请的另一实施例中，还提供一种计算机程序产品，该计算机程序产品包括计算机执行指令，该计算机执行指令存储在计算机可读存储介质中；数据传输装置400的至少一个处理器可以从计算机可读存储介质读取该计算机执行指令，至少一个处理器执行该计算机执行指令使得数据传输装置400实施执行图26所示的数据传输方法中的宿主基站的步骤。
在上述实施例中，可以全部或部分的通过软件，硬件，固件或者其任意组合来实现。当使用软件程序实现时，可以全部或部分地以计算机程序产品的形式出现。计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行计算机程序指令时，全部或部分地产生按照本申请实施例的流程或功能。计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如， 计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心传输。计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包括一个或多个可用介质集成的服务器、数据中心等数据终端设备。该可用介质可以是磁性介质，(例如，软盘，硬盘、磁带)、光介质(例如，DVD)或者半导体介质(例如固态硬盘Solid State Disk(SSD))等。
通过以上的实施方式的描述，所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，仅以上述各功能模块的划分进行举例说明，实际应用中，可以根据需要而将上述功能分配由不同的功能模块完成，即将装置的内部结构划分成不同的功能模块，以完成以上描述的全部或者部分功能。
在本申请所提供的几个实施例中，应该理解到，所揭露的装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述模块或单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个装置，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是一个物理单元或多个物理单元，即可以位于一个地方，或者也可以分布到多个不同地方。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个可读取存储介质中。基于这样的理解，本申请实施例的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该软件产品存储在一个存储介质中，包括若干指令用以使得一个设备(可以是单片机，芯片等)或处理器(processor)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何在本申请揭露的技术范围内的变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (28)

  1. 一种数据传输方法，其特征在于，应用于第一通信设备或所述第一通信设备中的芯片，所述第一通信设备为中间转发节点、终端的服务节点、宿主基站或者宿主基站系统中的分布式单元DU，所述数据传输方法包括：
    获取第一数据；
    向第二通信设备发送第一消息，所述第一消息包括所述第一数据以及类型标识，所述类型标识用于表示所述第一数据的类型，所述第一数据的类型包括用户面数据、状态报告、控制面消息以及所述终端的无线资源控制RRC消息中的至少一个；当所述第一通信设备为所述中间转发节点时，所述第二通信设备为所述中间转发节点的上一跳设备或下一跳设备；当所述第一通信设备为所述终端的服务节点时，所述第二通信设备为所述终端的服务节点的上一跳设备；当所述第一通信设备为所述宿主基站或者所述DU时，所述第二通信设备为所述第一通信设备的下一跳设备；其中，
    若所述第一数据为所述用户面数据，所述第一消息包括第一指示信息以及所述用户面数据的全局编号SN；第一指示信息用于指示所述用户面数据归属的所述终端的数据无线承载DRB；
    若所述第一数据为所述状态报告，所述第一数据包括所述终端的DRB承载的所述用户面数据的所述全局SN，所述第一数据用于指示第三通信设备的DRB数据包的传输情况，所述第三通信设备为所述终端、所述中间转发节点或者所述终端的服务节点；
    若所述第一数据为所述控制面消息，所述第一消息包括第一接口的传输层协议层信息、第二指示信息、所述终端在所述第一接口的标识以及第三指示信息中的至少一个；所述第一接口为所述第一通信设备与所述第二通信设备之间的逻辑通信接口，所述第一接口的传输层协议层信息包括所述第一通信设备的网络之间互连的协议IP地址、所述第二通信设备的IP地址、所述宿主基站或所述DU的IP地址、所述第一通信设备的端口号、所述第二通信设备的端口号、所述宿主基站或所述DU的端口号、流控制传输协议SCTP的流标识以及SCTP的负载协议标识PPI中的至少一个，所述第二指示信息用于指示所述第一通信设备，所述第三指示信息用于指示所述第一接口；或者，所述第一消息包括第四指示信息和所述终端的服务节点的标识，所述第四指示信息用于指示所述终端。
  2. 根据权利要求1所述的数据传输方法，其特征在于，当所述第一数据为所述状态报告时，
    所述第一数据还包括第五指示信息，所述第五指示信息用于指示所述终端的DRB。
  3. 根据权利要求2所述的数据传输方法，其特征在于，
    若所述第三通信设备为所述中间转发节点或所述终端的服务节点，所述第一数据具体包括所述第三通信设备的至少一个DRB中的每个DRB承载的所述第五指示信息。
  4. 根据权利要求1-3中任意一项所述的数据传输方法，其特征在于，
    所述第一消息还包括目标标识和第六指示信息中的至少一个；所述目标标识用于指示所述终端的服务节点，所述第六指示信息用于指示所述终端。
  5. 根据权利要求1或4所述的数据传输方法，其特征在于，当所述第一数据为所述控制面消息、且所述第一消息包括所述终端在所述第一接口的标识或所述第四指示 信息时，所述获取第一数据，具体包括：
    接收包括第二数据的第二消息，所述第二数据包括第七指示信息，所述第七指示信息用于指示所述终端或所述终端的DRB；
    获取所述第二数据；
    将所述第七指示信息替换为所述终端在所述第一接口的标识或所述第四指示信息，生成所述第一数据。
  6. 根据权利要求1-5中任意一项所述的数据传输方法，其特征在于，
    所述获取第一数据之后，所述数据传输方法还包括：
    根据第一预设压缩算法，压缩所述第一数据中的子信息；所述子信息包括IP头、SCTP公共头以及SCTP数据块中除目标信息之外的信息中的至少一个，所述目标信息为用户数据、流标识以及PPI中的至少一个；或者，所述子信息包括IP头、用户数据报协议UDP头以及通用分组无线服务隧道协议GTP头中除TEID之外的信息中的至少一个；
    所述向第二通信设备发送第一消息，具体包括：
    向所述第二通信设备发送包括压缩后的第一数据的第一消息。
  7. 根据权利要求6所述的数据传输方法，其特征在于，
    若所述第一通信设备为所述中间转发节点，所述获取第一数据，具体包括：
    接收第四通信设备发送的第三消息，所述第三消息包括第二数据；从所述第三消息中获取所述第二数据；根据第二预设压缩算法，解压缩所述第二数据，得到所述第一数据；其中，若所述第二通信设备为所述第一通信设备的上一跳设备，所述第四通信设备为所述第一通信设备的下一跳设备；若所述第二通信设备为所述第一通信设备的下一跳设备，所述第四通信设备为所述第一通信设备的上一跳设备；
    若所述第一通信设备为所述终端的服务节点，所述数据传输方法还包括：
    接收所述第二通信设备发送的第四消息，所述第四消息包括第三数据；根据第三预设压缩算法，解压缩所述第三数据，并向所述终端发送解压后的第三数据；
    若所述第一通信设备为所述DU，所述数据传输方法还包括：
    接收所述第二通信设备发送的第五消息，所述第五消息包括第四数据；根据第四预设压缩算法，解压缩所述第四数据，并向所述宿主基站系统中的集中式单元CU发送解压后的第四数据；
    若所述第一通信设备为所述DU，所述获取第一数据，具体包括：
    接收所述CU发送的第六消息，所述第六消息包括第五数据；从所述第六消息中获取所述第五数据；根据第五预设压缩算法，解压缩所述第五数据，得到所述第一数据。
  8. 根据权利要求1-7中任意一项所述的数据传输方法，其特征在于，
    在所述获取第一数据之后，所述数据传输方法还包括：
    根据第一预设秘钥和第一预设目标算法，处理所述第一数据，所述第一预设目标算法包括预设加密算法和第一预设完整性保护算法中的至少一种；
    所述向第二通信设备发送第一消息，具体包括：
    向所述第二通信设备发送包括处理后的第一数据的第一消息。
  9. 根据权利要求8所述的数据传输方法，其特征在于，
    若所述第一通信设备为中间转发节点，所述获取第一数据，具体包括：
    接收第五通信设备发送的第七消息，所述第七消息包括第六数据；获取所述第六数据，并根据第二预设秘钥和第二预设目标算法，处理所述第六数据，得到所述第一数据，所述第二预设目标算法包括第一预设解密算法和第二预设完整性保护算法中的至少一种；其中，若所述第二通信设备为所述第一通信设备的上一跳设备，所述第五通信设备为所述第一通信设备的下一跳设备；若所述第二通信设备为所述第一通信设备的下一跳设备，所述第五通信设备为所述第一通信设备的上一跳设备；
    若所述第一通信设备为所述终端的服务节点，所述数据传输方法还包括：
    接收所述第二通信设备发送的第八消息，所述第八消息包括第七数据；获取所述第七数据，并根据第三预设秘钥和第三预设目标算法，处理所述第七数据；向所述终端发送处理后的第七数据；所述第三预设目标算法包括第二预设解密算法和第三预设完整性保护算法中的至少一种；
    若所述第一通信设备为所述DU，所述数据传输方法还包括：
    接收所述第二通信设备发送的第九消息，所述第九消息包括第八数据；获取所述第八数据，并根据第四预设秘钥和第四预设目标算法，处理所述第八数据；向所述宿主基站系统的集中式单元CU发送处理后的第八数据；所述第四预设目标算法包括第三预设解密算法和第四预设完整性保护算法中的至少一种。
  10. 一种数据传输方法，其特征在于，应用于宿主基站或所述宿主基站中的芯片，所述数据传输方法包括：
    接收第一通信设备发送的第一消息，所述第一消息包括第一数据以及类型标识，所述类型标识用于表示所述第一数据的类型，所述第一数据的类型包括用户面数据、状态报告、控制面消息以及终端的无线资源控制RRC消息中的至少一个；
    根据所述类型标识，确定所述第一数据的类型；
    根据所述第一数据的类型，处理所述第一数据；
    其中，
    若所述第一数据为所述用户面数据，所述第一消息包括第一指示信息以及所述用户面数据的全局编号SN；第一指示信息用于指示所述用户面数据归属的所述终端的数据无线承载DRB；
    若所述第一数据为所述状态报告，所述第一数据包括所述终端的DRB承载的用户面数据的全局SN，所述第一数据用于指示第二通信设备的DRB数据包的传输情况，所述第二通信设备为所述终端、中间转发节点或所述终端的服务节点；
    若所述第一数据为所述控制面消息，所述第一消息包括第一接口的传输层协议层信息、第二指示信息、所述终端在所述第一接口的标识以及第三指示信息中的至少一个；所述第一接口为所述宿主基站与所述第一通信设备之间的逻辑通信接口，所述第一接口的传输层协议层信息包括所述第一通信设备的网络之间互连的协议IP地址、所述宿主基站的IP地址、所述第一通信设备的端口号、所述宿主基站的端口号、流控制传输协议SCTP的流标识以及SCTP的负载协议标识PPI中的至少一个，所述第二指示信息用于指示所述第一通信设备，所述第三指示信息用于指示所述第一接口；或者， 所述第一消息包括第四指示信息和所述终端归属的小区的标识中的至少一个，所述第四指示信息用于指示所述终端。
  11. 根据权利要求10所述的数据传输方法，其特征在于，当所述第一数据为所述状态报告时，
    所述第一数据还包括第五指示信息，所述第五指示信息用于指示所述终端的DRB。
  12. 根据权利要求11所述的数据传输方法，其特征在于，
    若所述第二通信设备为所述中间转发节点或所述终端的服务节点，所述第一数据具体包括所述第二通信设备的至少一个DRB中的每个DRB承载的所述第五指示信息。
  13. 根据权利要求10-12中任意一项所述的数据传输方法，其特征在于，若所述第一数据为所述状态报告时，所述根据所述第一数据的类型，处理所述第一数据，具体包括：
    根据所述第一数据，向所述第二通信设备发送所述第一数据指示的未被成功接收的所述第二通信设备的DRB数据包。
  14. 根据权利要求13所述的数据传输方法，其特征在于，所述根据所述第一数据的类型，处理所述第一数据之前，所述数据传输方法还包括：
    接收所述第一通信设备或第三通信设备发送的第六指示信息，所述第六指示信息用于指示通过所述第三通信设备向所述第二通信设备发送所述第一数据指示的未被成功接收的所述第二通信设备的DRB数据包。
  15. 一种数据传输装置，其特征在于，所述数据传输装置为第一通信设备或所述第一通信设备中的芯片，所述第一通信设备为中间转发节点、终端的服务节点、宿主基站或者宿主基站系统中的分布式单元DU，包括：
    获取单元，用于获取第一数据；
    发送单元，用于向第二通信设备发送第一消息，所述第一消息包括所述获取单元获取到的所述第一数据以及类型标识，所述类型标识用于表示所述第一数据的类型，所述第一数据的类型包括用户面数据、状态报告、控制面消息以及所述终端的无线资源控制RRC消息中的至少一个；当所述第一通信设备为所述中间转发节点时，所述第二通信设备为所述中间转发节点的上一跳设备或下一跳设备；当所述第一通信设备为所述终端的服务节点时，所述第二通信设备为所述终端的服务节点的上一跳设备；当所述第一通信设备为所述宿主基站或者所述DU时，所述第二通信设备为所述第一通信设备的下一跳设备；其中，
    若所述第一数据为所述用户面数据，所述第一消息包括第一指示信息以及所述用户面数据的全局编号SN；第一指示信息用于指示所述用户面数据归属的所述终端的数据无线承载DRB；
    若所述第一数据为所述状态报告，所述第一数据包括所述终端的DRB承载的所述用户面数据的所述全局SN，所述第一数据用于指示第三通信设备的DRB数据包的传输情况，所述第三通信设备为所述终端、所述中间转发节点或者所述终端的服务节点；
    若所述第一数据为所述控制面消息，所述第一消息包括第一接口的传输层协议层信息、第二指示信息、所述终端在所述第一接口的标识以及第三指示信息中的至少一个；所述第一接口为所述第一通信设备与所述第二通信设备之间的逻辑通信接口，所 述第一接口的传输层协议层信息包括所述第一通信设备的网络之间互连的协议IP地址、所述第二通信设备的IP地址、所述宿主基站或所述DU的IP地址，所述第一通信设备的端口号、所述第二通信设备的端口号、所述宿主基站或所述DU的端口号，流控制传输协议SCTP的流标识以及SCTP的负载协议标识PPI中的至少一个，所述第二指示信息用于指示所述第一通信设备，所述第三指示信息用于指示所述第一接口；或者，所述第一消息包括第四指示信息和所述终端的服务节点的标识，所述第四指示信息用于指示所述终端。
  16. 根据权利要求15所述的数据传输装置，其特征在于，当所述第一数据为所述状态报告时，
    所述第一数据还包括第五指示信息，所述第五指示信息用于指示所述终端的DRB。
  17. 根据权利要求16所述的数据传输装置，其特征在于，
    若所述第三通信设备为所述中间转发节点或所述终端的服务节点，所述第一数据具体包括所述第三通信设备的至少一个DRB中的每个DRB承载的所述第五指示信息。
  18. 根据权利要求15-17中任意一项所述的数据传输装置，其特征在于，
    所述第一消息还包括目标标识和第六指示信息中的至少一个；所述目标标识用于指示所述终端的服务节点，所述第六指示信息用于指示所述终端。
  19. 根据权利要求15或18所述的数据传输装置，其特征在于，当所述第一数据为所述控制面消息、且所述第一消息包括所述终端在所述第一接口的标识或所述第四指示信息时，所述数据传输装置还包括接收单元；
    所述接收单元，用于接收包括第二数据的第二消息，所述第二数据包括第七指示信息，所述第七指示信息用于指示所述终端或所述终端的DRB；
    所述获取单元，还用于从所述接收单元接收到的所述第二消息中获取所述第二数据；
    所述数据传输装置还包括替换单元；
    所述替换单元，用于将所述第七指示信息替换为所述终端在所述第一接口的标识或所述第四指示信息，生成所述第一数据。
  20. 根据权利要求15-19中任意一项所述的数据传输装置，其特征在于，所述数据传输装置还包括压缩单元；
    所述压缩单元，用于在所述获取单元所述获取第一数据之后，根据第一预设压缩算法，压缩所述第一数据中的子信息；所述子信息包括IP头、SCTP公共头以及SCTP数据块中除目标信息之外的信息中的至少一个，所述目标信息为用户数据、流标识以及PPI中的至少一个；或者，所述子信息包括IP头、用户数据报协议UDP头以及通用分组无线服务隧道协议GTP头中除TEID之外的信息中的至少一个；
    所述发送单元，具体用于向所述第二通信设备发送包括压缩后的第一数据的第一消息。
  21. 根据权利要求20所述的数据传输装置，其特征在于，所述数据传输装置还包括接收单元和解压缩单元；
    若所述第一通信设备为所述中间转发节点，所述接收单元用于接收第四通信设备发送的第三消息，所述第三消息包括第二数据；所述获取单元还用于从所述接收单元 接收到的所述第三消息中获取所述第二数据；所述解压缩单元用于根据第二预设压缩算法，解压缩所述第二数据，得到所述第一数据；其中，若所述第二通信设备为所述第一通信设备的上一跳设备，所述第四通信设备为所述第一通信设备的下一跳设备；若所述第二通信设备为所述第一通信设备的下一跳设备，所述第四通信设备为所述第一通信设备的上一跳设备；
    若所述第一通信设备为所述终端的服务节点，所述接收单元用于接收所述第二通信设备发送的第四消息，所述第四消息包括第三数据；所述解压缩单元，用于根据第三预设压缩算法，解压缩所述第三数据；所述发送单元具体用于所述终端发送解压后的第三数据；
    若所述第一通信设备为所述DU，所述接收单元用于接收所述第二通信设备发送的第五消息，所述第五消息包括第四数据；所述解压缩单元用于根据第四预设压缩算法，解压缩所述第四数据；所述发送单元，具体用于向所述宿主基站系统中的集中式单元CU发送解压后的第四数据；
    若所述第一通信设备为所述DU，所述接收单元用于接收所述CU发送的第六消息，所述第六消息包括第五数据；所述获取单元还用于从所述第六消息中获取所述第五数据；所述解压缩单元用于根据第五预设压缩算法，解压缩所述第五数据，得到所述第一数据。
  22. 根据权利要求15-21中任意一项所述的数据传输装置，其特征在于，所述数据传输装置还包括安全保护单元；
    所述安全保护单元，用于在所述获取单元所述获取第一数据之后，根据第一预设秘钥和第一预设目标算法，处理所述第一数据，所述第一预设目标算法包括预设加密算法和第一预设完整性保护算法中的至少一种；
    所述发送单元，具体用于向所述第二通信设备发送包括处理后的第一数据的第一消息。
  23. 根据权利要求22所述的数据传输装置，其特征在于，所述数据传输装置还包括接收单元和安全处理单元；
    若所述第一通信设备为中间转发节点，所述接收单元用于接收第五通信设备发送的第七消息，所述第七消息包括第六数据；所述获取单元还用于从所述接收单元接收到所述第七消息中获取所述第六数据；所述安全处理单元用于根据第二预设秘钥和第二预设目标算法，处理所述获取单元获取到的所述第六数据，得到所述第一数据，所述第二预设目标算法包括第一预设解密算法和第二预设完整性保护算法中的至少一种；其中，若所述第二通信设备为所述第一通信设备的上一跳设备，所述第五通信设备为所述第一通信设备的下一跳设备；若所述第二通信设备为所述第一通信设备的下一跳设备，所述第五通信设备为所述第一通信设备的上一跳设备；
    若所述第一通信设备为所述终端的服务节点，所述接收单元用于接收所述第二通信设备发送的第八消息，所述第八消息包括第七数据；所述获取单元还用于从所述接收单元接收到的所述第八消息中获取所述第七数据；所述安全处理单元用于根据第三预设秘钥和第三预设目标算法，处理所述获取单元获取到的所述第七数据；所述发送单元具体用于向所述终端发送处理后的第七数据；所述第三预设目标算法包括第二预 设解密算法和第三预设完整性保护算法中的至少一种；
    若所述第一通信设备为所述DU，所述接收单元用于接收所述第二通信设备发送的第九消息，所述第九消息包括第八数据；所述获取单元还用于从所述第九消息中获取所述第八数据；所述安全处理单元用于根据第四预设秘钥和第四预设目标算法，处理所述第八数据；所述发送单元具体用于向所述宿主基站系统的集中式单元CU发送处理后的第八数据；所述第四预设目标算法包括第三预设解密算法和第四预设完整性保护算法中的至少一种。
  24. 一种数据传输装置，其特征在于，所述数据传输装置为宿主基站或所述宿主基站中的芯片，包括：
    接收单元，用于接收第一通信设备发送的第一消息，所述第一消息包括第一数据以及类型标识，所述类型标识用于表示所述第一数据的类型，所述第一数据的类型包括用户面数据、状态报告、控制面消息以及终端的无线资源控制RRC消息中的至少一个；
    处理单元，用于根据所述接收单元接收到的所述第一消息中的所述类型标识，确定所述第一数据的类型，并根据所述第一数据的类型，处理所述第一数据；
    其中，
    若所述第一数据为所述用户面数据，所述第一消息包括第一指示信息以及所述用户面数据的全局编号SN；第一指示信息用于指示所述用户面数据归属的所述终端的数据无线承载DRB；
    若所述第一数据为所述状态报告，所述第一数据包括所述终端的DRB承载的用户面数据的全局SN，所述第一数据用于指示第二通信设备的DRB数据包的传输情况，所述第二通信设备为所述终端、中间转发节点或所述终端的服务节点；
    若所述第一数据为所述控制面消息，所述第一消息包括第一接口的传输层协议层信息、第二指示信息、所述终端在所述第一接口的标识以及第三指示信息中的至少一个；所述第一接口为所述宿主基站与所述第一通信设备之间的逻辑通信接口，所述第一接口的传输层协议层信息包括所述第一通信设备的网络之间互连的协议IP地址、所述宿主基站的IP地址、所述第一通信设备的端口号、所述宿主基站的端口号、流控制传输协议SCTP的流标识以及SCTP的负载协议标识PPI中的至少一个，所述第二指示信息用于指示所述第一通信设备，所述第三指示信息用于指示所述第一接口；或者，所述第一消息包括第四指示信息和所述终端归属的小区的标识中的至少一个，所述第四指示信息用于指示所述终端。
  25. 根据权利要求24所述的数据传输装置，其特征在于，当所述第一数据为所述状态报告时，
    所述第一数据还包括第五指示信息，所述第五指示信息用于指示所述终端的DRB。
  26. 根据权利要求25所述的数据传输装置，其特征在于，
    若所述第二通信设备为所述中间转发节点或所述终端的服务节点，所述第一数据具体包括所述第二通信设备的至少一个DRB中的每个DRB承载的所述第五指示信息。
  27. 根据权利要求24-26中任意一项所述的数据传输装置，其特征在于，若所述第一数据为所述状态报告时，所述处理单元具体用于：
    根据所述第一数据，向所述第二通信设备发送所述第一数据指示的未被成功接收的所述第二通信设备的DRB数据包。
  28. 根据权利要求27所述的数据传输装置，其特征在于，
    所述接收单元，还用于在所述处理单元根据所述第一数据的类型，处理所述第一数据之前，接收所述第一通信设备或第三通信设备发送的第六指示信息，所述第六指示信息用于指示通过所述第三通信设备向所述第二通信设备发送所述第一数据指示的未被成功接收的所述第二通信设备的DRB数据包。
PCT/CN2019/071481 2018-01-12 2019-01-11 一种数据传输方法及装置 WO2019137505A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP19738167.6A EP3731484B1 (en) 2018-01-12 2019-01-11 Data transmission method and device
US16/925,614 US11463937B2 (en) 2018-01-12 2020-07-10 Data transmission method and apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810032655.5 2018-01-12
CN201810032655.5A CN110035042B (zh) 2018-01-12 2018-01-12 一种数据传输方法及装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/925,614 Continuation US11463937B2 (en) 2018-01-12 2020-07-10 Data transmission method and apparatus

Publications (1)

Publication Number Publication Date
WO2019137505A1 true WO2019137505A1 (zh) 2019-07-18

Family

ID=67218865

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/071481 WO2019137505A1 (zh) 2018-01-12 2019-01-11 一种数据传输方法及装置

Country Status (4)

Country Link
US (1) US11463937B2 (zh)
EP (1) EP3731484B1 (zh)
CN (2) CN112039944A (zh)
WO (1) WO2019137505A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021026704A1 (zh) * 2019-08-09 2021-02-18 华为技术有限公司 一种无线通信的方法和装置
WO2021068257A1 (en) * 2019-10-12 2021-04-15 Nokia Shanghai Bell Co., Ltd. Signaling reduction at handover of an iab node
US11805464B2 (en) * 2018-02-11 2023-10-31 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Mobile communication system, method and device

Families Citing this family (24)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110366206A (zh) * 2018-03-26 2019-10-22 华为技术有限公司 一种信息传输方法和装置
HUE063433T2 (hu) * 2018-04-04 2024-01-28 Zte Corp Eljárás és rendszerek üzenetek cseréjére vezeték nélküli hálózatban
CN110636643A (zh) * 2018-06-21 2019-12-31 中兴通讯股份有限公司 数据包的发送、接收方法及装置和数据包的传输系统
CN110636570B (zh) * 2018-06-25 2022-08-02 中兴通讯股份有限公司 Iab网络中iab节点信息的处理方法及装置
WO2020022849A1 (en) * 2018-07-27 2020-01-30 Samsung Electronics Co., Ltd. Method and apparatus for wireless communication of wireless node in wireless communication system
WO2021026707A1 (zh) * 2019-08-09 2021-02-18 华为技术有限公司 一种去激活iab节点的方法及装置
CN116233950A (zh) * 2019-08-15 2023-06-06 华为技术有限公司 一种路由方法及装置
CN112398959B (zh) * 2019-08-15 2022-02-25 华为技术有限公司 Rlc信道确定方法和装置
BR112022005876A2 (pt) * 2019-09-30 2022-06-21 Huawei Tech Co Ltd Método de transmissão de pacote de dados e aparelho
US11770875B2 (en) * 2019-10-03 2023-09-26 Qualcomm Incorporated Integrated access and backhaul (IAB) timing handling for positioning
CN112911641A (zh) * 2019-12-03 2021-06-04 华为技术有限公司 通信处理方法和通信处理装置
US11844076B2 (en) * 2019-12-31 2023-12-12 Qualcomm Incorporated Techniques for multiplexing remote UE RRC messages in a wireless communication system
CN115004634B (zh) * 2020-04-03 2023-12-19 Oppo广东移动通信有限公司 信息处理方法、装置、设备及存储介质
CN113766461A (zh) * 2020-06-01 2021-12-07 中国电信股份有限公司 用户面数据处理方法和基站
CN113810215A (zh) * 2020-06-12 2021-12-17 华为技术有限公司 一种中继通信方法及相关设备
US11429279B2 (en) * 2020-09-16 2022-08-30 Samsung Electronics Co., Ltd. Automatic data separation and placement for compressed data in a storage device
US20240056939A1 (en) * 2020-12-31 2024-02-15 Lenovo (Beijing) Limited Relaying information using one or more relays
WO2022151233A1 (en) * 2021-01-14 2022-07-21 Nokia Shanghai Bell Co., Ltd. Method, apparatus and computer program
EP4054282A1 (en) * 2021-03-02 2022-09-07 Nokia Solutions and Networks Oy Preventing data outage for user equipment during e-utran new radio dual connectivity procedure
US11902260B2 (en) * 2021-08-02 2024-02-13 Cisco Technology, Inc. Securing control/user plane traffic
WO2023010367A1 (zh) * 2021-08-04 2023-02-09 富士通株式会社 终端设备的转移方法、装置和系统
WO2023156138A1 (en) * 2022-02-21 2023-08-24 Sony Group Corporation Method, node and system for implementing an interworking layer
CN115549027A (zh) * 2022-11-24 2022-12-30 中国电力科学研究院有限公司 一种压板状态在线监测系统及方法
CN117857670A (zh) * 2024-03-05 2024-04-09 深圳国人无线通信有限公司 一种基于5gnr系统的简化rrc消息处理方法和基站

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2011002244A2 (en) * 2009-07-02 2011-01-06 Lg Electronics Inc. A method to facilitate user equipment (ue) handoff within a packet data communication system
CN102160300A (zh) * 2008-09-19 2011-08-17 诺基亚西门子通信公司 网络元件以及操作网络元件的方法
WO2014007494A1 (en) * 2012-07-02 2014-01-09 Lg Electronics Inc. Method and apparatus for switching connection in wireless communication system
CN104219144A (zh) * 2014-09-09 2014-12-17 华为技术有限公司 确定业务流的转发路径的方法、系统和网络管理系统
KR20170132080A (ko) * 2016-05-23 2017-12-01 한국전자통신연구원 핸드오버 방법

Family Cites Families (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101626607B (zh) * 2008-07-11 2012-06-27 普天信息技术研究院有限公司 无线通信系统中中继场景下终端切换的方法和系统
CN101877915B (zh) * 2009-04-28 2014-07-02 中兴通讯股份有限公司 一种长期演进系统中继站的数据传输方法和系统
CN103188681B (zh) * 2009-09-28 2016-08-10 华为技术有限公司 数据传输方法、装置及系统
KR101831448B1 (ko) * 2010-02-02 2018-02-26 엘지전자 주식회사 이동 통신 시스템에서 ｐｄｃｐ 기능을 선택적으로 적용하는 방법
WO2012055114A1 (en) * 2010-10-29 2012-05-03 Nokia Siemens Networks Oy Security of user plane traffic between relay node and radio access network
CN103582161B (zh) * 2012-07-26 2016-12-21 普天信息技术研究院有限公司 一种基于lte系统中继节点的数据传输方法
EP2924940B1 (en) * 2012-12-27 2019-12-04 Huawei Technologies Co., Ltd. User plane data transmission methods, mobility management network element and evolved node b
EP2835925B1 (en) * 2013-08-09 2018-08-08 Panasonic Intellectual Property Corporation of America Efficient Status Reporting for UEs in dual connectivity during mobility
CN105580329B (zh) * 2014-08-21 2018-11-20 华为技术有限公司 一种空口数据传输的方法、装置及系统
CN104468312B (zh) * 2014-11-20 2019-03-15 中兴通讯股份有限公司 一种无线中继站及其接入核心网的方法和系统
US9992806B2 (en) * 2015-01-15 2018-06-05 Intel IP Corporation Public safety discovery and communication using a UE-to-UE relay
CN106162694B (zh) * 2015-04-09 2020-06-19 上海诺基亚贝尔股份有限公司 用于支持覆盖范围扩展和业务连续性的方法以及装置
US10516605B2 (en) * 2015-06-03 2019-12-24 Vid Scale, Inc. Enhancing performance of multi-path communications

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102160300A (zh) * 2008-09-19 2011-08-17 诺基亚西门子通信公司 网络元件以及操作网络元件的方法
WO2011002244A2 (en) * 2009-07-02 2011-01-06 Lg Electronics Inc. A method to facilitate user equipment (ue) handoff within a packet data communication system
WO2014007494A1 (en) * 2012-07-02 2014-01-09 Lg Electronics Inc. Method and apparatus for switching connection in wireless communication system
CN104219144A (zh) * 2014-09-09 2014-12-17 华为技术有限公司 确定业务流的转发路径的方法、系统和网络管理系统
KR20170132080A (ko) * 2016-05-23 2017-12-01 한국전자통신연구원 핸드오버 방법

Non-Patent Citations (1)

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

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11805464B2 (en) * 2018-02-11 2023-10-31 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Mobile communication system, method and device
WO2021026704A1 (zh) * 2019-08-09 2021-02-18 华为技术有限公司 一种无线通信的方法和装置
WO2021068257A1 (en) * 2019-10-12 2021-04-15 Nokia Shanghai Bell Co., Ltd. Signaling reduction at handover of an iab node

Also Published As

Publication number Publication date
US11463937B2 (en) 2022-10-04
CN112039944A (zh) 2020-12-04
CN110035042B (zh) 2020-08-07
EP3731484A1 (en) 2020-10-28
US20200344666A1 (en) 2020-10-29
CN110035042A (zh) 2019-07-19
EP3731484B1 (en) 2023-01-04
EP3731484A4 (en) 2020-12-30

Similar Documents

Publication Publication Date Title
WO2019137505A1 (zh) 一种数据传输方法及装置
WO2019214709A1 (zh) 信息传输方法及装置
JP6884879B2 (ja) 中継通信方法ならびに中継通信装置およびシステム
US20190166526A1 (en) Method for establishing a fronthaul interface, method for performing access for a ue, method and apparatus for performing a handover for a ue, data forwarding method, user equipment and base station
US10863513B2 (en) Method for reconfiguring data radio bearer and user equipment
WO2021204003A1 (zh) 一种临近服务的业务处理方法、设备及系统
WO2017166138A1 (zh) 中继传输的方法和装置
US20220232651A1 (en) Method for transmitting control signaling in relay network, configuration method and device
CN110381608B (zh) 一种中继网络的数据传输方法及装置
JP6885427B2 (ja) 基地局、無線通信システムおよび通信方法
CN110999355B (zh) 用于分离用户面的服务质量实现
US9344922B2 (en) Radio communication system and base station
CN108432311A (zh) 一种资源请求方法、设备、网络侧节点及系统
WO2021197269A1 (zh) 一种临近服务的数据传输方法、设备及系统
WO2019105483A1 (zh) 一种传输方法和中继节点
WO2021097858A1 (zh) 一种通信方法及装置
JP2014014019A (ja) 無線通信システム
WO2020001256A1 (zh) 一种数据传输方法及装置
JP2014096662A (ja) 無線通信システムおよび通信制御方法
WO2017132954A1 (zh) 一种数据传输方法、装置及相关设备
WO2018141241A1 (zh) 设备切换方法及设备、承载配置方法及设备、通信系统
WO2021189496A1 (zh) 用于网络切片的数据传输方法及设备
CN111510929B (zh) Iab网络中进行lcid扩展的方法及装置
US20150257048A1 (en) Mobile communication method
KR20210073599A (ko) 릴레이 네트워크에서 제어 시그널링을 송신하는 방법, 구성 방법 및 장치

Legal Events

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

Ref document number: 19738167

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2019738167

Country of ref document: EP

Effective date: 20200720