WO2020221360A1 - 一种通信方法及装置 - Google Patents
一种通信方法及装置 Download PDFInfo
- Publication number
- WO2020221360A1 WO2020221360A1 PCT/CN2020/088499 CN2020088499W WO2020221360A1 WO 2020221360 A1 WO2020221360 A1 WO 2020221360A1 CN 2020088499 W CN2020088499 W CN 2020088499W WO 2020221360 A1 WO2020221360 A1 WO 2020221360A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- data packet
- iab node
- host
- node
- information
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/74—Address processing for routing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/02—Standardisation; Integration
- H04L41/0246—Exchanging or transporting network management information using the Internet; Embedding network management web servers in network elements; Web-services-based protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/38—Flow based routing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
-
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/50—Address allocation
- H04L61/5007—Internet protocol [IP] addresses
- H04L61/5014—Internet protocol [IP] addresses using dynamic host configuration protocol [DHCP] or bootstrap protocol [BOOTP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/26—Network addressing or numbering for mobility support
Definitions
- This application relates to the field of communication technology, and in particular to a communication method and device.
- the fifth-generation (5th-generation, 5G) mobile communication system puts forward more stringent requirements in all aspects of network performance indicators. For example, the capacity index is increased by 1000 times, wider coverage requirements, ultra-high reliability and ultra-low latency, etc.
- the capacity index is increased by 1000 times, wider coverage requirements, ultra-high reliability and ultra-low latency, etc.
- the use of high-frequency small stations to network is becoming more and more popular.
- the high-frequency carrier has poor propagation characteristics, severe attenuation due to obstruction, and limited coverage. Therefore, a large number of densely deployed small stations are required. Accordingly, providing optical fiber backhaul for these densely deployed small stations is expensive and difficult to construct. Therefore, an economical and convenient backhaul solution is needed; on the other hand, from the perspective of wide coverage requirements, to provide network coverage in some remote areas, the deployment of optical fibers is difficult and costly, and flexible and convenient access and backhaul solutions are also required. .
- the 5G system introduces integrated access and backhaul (IAB) network technology.
- the access link (AL) and backhaul link (BL) in the IAB network are all wireless
- the transmission scheme avoids optical fiber deployment, thereby reducing deployment costs and increasing deployment flexibility.
- a wireless backhaul node can provide wireless access services for terminal devices, and the wireless backhaul node can also be called an IAB node (IAB node) or a relay node (RN).
- the service data of the terminal device can be transmitted by a wireless backhaul node connected to a host node through a wireless backhaul link, and the host node can be an IAB donor (IAB donor) or a donor base station (donor gNodeB, DgNB).
- this application provides a communication method and device to implement communication between an IAB node and an OAM server.
- an embodiment of the present application provides a communication method, the method includes: a host DU receives a first access from the host CU and returns the Internet Protocol IP address of an integrated IAB node and first routing information, the first routing information It is used to route the first data packet to the first IAB node, where the destination IP address of the first data packet is the IP address of the first IAB node; further, the host DU receives the first data packet and transfers the first data packet And the first routing information is sent to the next hop node of the host DU.
- the first data packet may be an OAM service data packet or a DHCP service data packet. Accordingly, the first data packet may be received from an OAM server or may also be received from a DHCP server. In the embodiment of the present application, the first data packet is an OAM service data packet as an example for description.
- the first data packet is an OAM service data packet
- the above method can also be described as follows:
- the host DU receives from the host CU the Internet Protocol IP address of the first access backhaul integrated IAB node and first routing information.
- the first routing information is used to route the first data packet to the first IAB node, where the first data
- the packet is an OAM service data packet, and the destination IP address of the first data packet is the IP address of the first IAB node; further, the host DU receives the first data packet from the OAM server, and sends the first data packet and the first routing information The next hop node for the host DU.
- the host DU sends the first data packet to the next hop node of the host DU, and then the next hop node of the host DU can subsequently send the first data packet to the first IAB node.
- the first routing information includes: the identifier of the first path, the sending node on the first path is the host DU, and the receiving node on the first path is the first IAB node; or, the first IAB node The first logo.
- the first identifier of the first IAB node is the adaptation layer identifier allocated by the hosting centralized unit CU for the first IAB node.
- the first routing information includes: the identifier of the second path and the second identifier of the first IAB node, the sending node on the second path is the host DU, and the receiving node on the second path is the first The parent node of the IAB node; or, the identity of the parent node of the first IAB node and the second identity of the first IAB node.
- the second identity of the first IAB node is the cell radio network temporary identity C-RNTI assigned by the parent node of the first IAB node to the first IAB node, or the second identity of the first IAB node
- the first F1AP identifier assigned to the first IAB node for the parent node of the first IAB node; or, the second identifier of the first IAB node includes the first F1AP identifier and the second F1AP identifier assigned by the host CU to the first IAB node.
- the host DU sends the first routing information to the next hop node of the host DU, including: the host DU carries the first routing information in the adaptation layer of the host DU and sends it to the next hop of the host DU. Jump node.
- the host DU sends the first data packet to the next hop node of the host DU, including: the host DU receives the first information and the first bearer information from the host CU, and the first bearer information is used to indicate transmission
- the return radio link control BH RLC channel of the first data packet includes the first information, and the first information includes at least one of the following: Differentiated Services Code Point DSCP value, flow label, OAM server IP address, port Number; the host DU maps the first data packet to the BH RLC channel and sends it to the next hop node of the host DU.
- an embodiment of the present application provides a communication method, the method includes: the host CU obtains the IP address of the first IAB node and first routing information, the first routing information is used to route the first data packet to the first IAB node, where the first data packet is an OAM service data packet, and the destination IP address of the first data packet is the IP address of the first IAB node; further, the host CU sends the IP address of the first IAB node and the first IAB node to the host DU One routing information.
- the first routing information includes: the identifier of the first path, the sending node on the first path is the host DU, and the receiving node on the first path is the first IAB node; or, the first IAB node The first logo.
- the first identifier of the first IAB node is the adaptation layer identifier allocated by the hosting centralized unit CU for the first IAB node.
- the first routing information includes: the identifier of the second path and the second identifier of the first IAB node, the sending node on the second path is the host DU, and the receiving node on the second path is the first The parent node of the IAB node; or, the identity of the parent node of the first IAB node and the second identity of the first IAB node.
- the second identifier of the first IAB node is the C-RNTI allocated by the parent node of the first IAB node to the first IAB node, or the second identifier of the first IAB node is the first IAB node
- the parent node of is the first F1AP identifier assigned by the first IAB node; or, the second identifier of the first IAB node includes the first F1AP identifier and the second F1AP identifier assigned by the host CU for the first IAB node.
- the donor CU sends first information and first bearer information to the host DU.
- the first bearer information is used to indicate the BH RLC channel for transmitting the first data packet.
- the first data packet includes the first information.
- One piece of information includes at least one of the following: DSCP value, flow label, IP address of the OAM server, and port number.
- an embodiment of the present application provides a communication method, the method includes: a donor DU receives first information and first bearer information from the host CU, the first bearer information is used to indicate the BH RLC channel for transmitting the first data packet ,
- the first data packet includes first information, and the first information includes at least one of the following: DSCP value, flow label, IP address of the OAM server, and port number; further, the host DU receives the first data packet from the OAM server, and The first data packet is mapped to the next hop node sent to the host DU in the BH RLC channel.
- an embodiment of the present application provides a communication method.
- the method includes: a donor CU obtains first information and first bearer information, where the first bearer information is used to indicate a BH RLC channel for transmitting the first data packet, and the first
- the data packet includes first information, and the first information includes at least one of the following: DSCP value, flow label, IP address of the OAM server, and port number; further, the host CU sends the first information and first bearer information to the host DU.
- an embodiment of the present application provides a communication method.
- the method includes: a first IAB node receives an OAM server's IP address and second routing information from a host CU, and the second routing information is used to route the second data packet To the host DU, the destination IP address of the second data packet is the IP address of the OAM server; further, the first IAB node generates the second data packet, and sends the second data packet and the second routing information to the upstream of the first IAB node One-hop node.
- the second routing information includes: the identifier of the third path, the sending node on the third path is the first IAB node, and the receiving node on the third path is the host DU; or Identification, the sending node on the fourth path is the last hop node of the first IAB node, and the receiving node on the fourth path is the host DU.
- the first IAB node sends the second routing information to the previous hop node of the first IAB node, including: the first IAB node carries the second routing information in the adaptation layer of the first IAB node Sent to the previous hop node of the first IAB node.
- the first IAB node sending the second data packet to the previous hop node of the first IAB node includes: the first IAB node receives the second information and the second bearer information from the host CU, and the second The bearer information is used to indicate the BH RLC channel for transmitting the second data packet, the second data packet includes second information, and the second information includes at least one of the following: DSCP value, flow label, IP address of the OAM server, and port number; further , The first IAB node maps the second data packet to the BH RLC channel and sends it to the previous hop node of the first IAB node.
- an embodiment of the present application provides a communication method.
- the method includes: the host CU obtains the IP address of the OAM server and second routing information, the second routing information is used to route the second data packet to the host DU, and the first Second, the destination IP address of the data packet is the IP address of the OAM server; further, the host CU sends the IP address of the OAM server and the second routing information to the first IAB node.
- the second routing information includes: the identifier of the third path, the sending node on the third path is the first IAB node, and the receiving node on the third path is the host DU; or Identification, the sending node on the fourth path is the last hop node of the first IAB node, and the receiving node on the fourth path is the host DU.
- an embodiment of the present application provides a communication method.
- the method includes: a first IAB node receives second information and second bearer information from a host CU, and the second bearer information is used to indicate the BH that transmits the second data packet.
- RLC channel the second data packet includes second information, the second information includes at least one of the following: DSCP value, flow label, OAM server IP address, port number; further, the first IAB node generates the second data packet, The second data packet is mapped to the previous hop node sent to the first IAB node in the BH RLC channel.
- an embodiment of the present application provides a communication method, the method includes: a donor CU obtains second information and second bearer information, the second bearer information is used to indicate a BH RLC channel for transmitting the second data packet, and the second The data packet includes second information, and the second information includes at least one of the following: DSCP value, flow label, IP address and port number of the OAM server; further, the host CU sends the second information and the second bearer information to the first IAB node .
- an embodiment of the present application provides a communication method.
- the method includes: a host DU receives a first data packet and first routing information from the host CU, and the first routing information is used to route the first data packet to the first data packet.
- IAB node where the first data packet is an OAM service data packet, and the destination IP address of the first data packet is the IP address of the first IAB node; further, the host DU combines the first data packet with the first data packet according to the first routing information A routing information is sent to the next hop node of the host DU.
- the first routing information includes: the identifier of the first path, the sending node on the first path is the host DU, and the receiving node on the first path is the first IAB node; or, the first IAB node The first logo.
- the first identifier of the first IAB node is the adaptation layer identifier allocated by the hosting centralized unit CU for the first IAB node.
- the first routing information includes: the identifier of the second path and the second identifier of the first IAB node, the sending node on the second path is the host DU, and the receiving node on the second path is the first The parent node of the IAB node; or, the identity of the parent node of the first IAB node and the second identity of the first IAB node.
- the second identifier of the first IAB node is the C-RNTI allocated by the parent node of the first IAB node to the first IAB node, or the second identifier of the first IAB node is the first IAB node
- the parent node of is the first F1AP identifier assigned by the first IAB node; or, the second identifier of the first IAB node includes the first F1AP identifier and the second F1AP identifier assigned by the host CU for the first IAB node.
- the host DU sends the first routing information to the next hop node of the host DU, including: the host DU carries the first routing information in the adaptation layer of the host DU and sends it to the next hop of the host DU. Jump node.
- the host DU sends the first data packet to the next hop node of the host DU, including: the host DU receives the first information and the first bearer information from the host CU, and the first bearer information is used to indicate transmission The return radio link control BH RLC channel of the first data packet; the first data packet includes the first information, and the first information includes at least one of the following: Differentiated Services Code Point DSCP value, flow label, OAM server IP address, port Further, the host DU maps the first data packet to the BH RLC channel and sends it to the next hop node of the host DU.
- an embodiment of the present application provides a communication method, the method includes: a host CU receives a first data packet from an OAM server, the first data packet is an OAM service data packet; further, the host CU sends a first data packet to the host DU A data packet and first routing information, the first routing information is used to route the first data packet to the first IAB node, and the destination IP address of the first data packet is the IP address of the first IAB node.
- the first routing information includes: the identifier of the first path, the sending node on the first path is the host DU, and the receiving node on the first path is the first IAB node; or, the first IAB node The first logo.
- the first identifier of the first IAB node is the adaptation layer identifier allocated by the hosting centralized unit CU for the first IAB node.
- the first routing information includes: the identifier of the second path and the second identifier of the first IAB node, the sending node on the second path is the host DU, and the receiving node on the second path is the first The parent node of the IAB node; or, the identity of the parent node of the first IAB node and the second identity of the first IAB node.
- the second identifier of the first IAB node is the C-RNTI allocated by the parent node of the first IAB node to the first IAB node, or the second identifier of the first IAB node is the first IAB node
- the parent node of is the first F1AP identifier assigned by the first IAB node; or, the second identifier of the first IAB node includes the first F1AP identifier and the second F1AP identifier assigned by the host CU for the first IAB node.
- the method further includes: the host CU sends first information and first bearer information to the host DU, the first bearer information is used to indicate a BH RLC channel for transmitting the first data packet, and the first data packet includes The first information, the first information includes at least one of the following: DSCP value, flow label, IP address of the OAM server, and port number.
- an embodiment of the application provides a communication method, the method includes: an access management function entity obtains subscription information of a first IAB node, and the subscription information includes the quality of service QoS of the OAM service data of the first IAB node Information; Further, the access management function entity sends the QoS information of the OAM service data of the first IAB node to the host CU.
- an embodiment of the present application provides a communication method.
- the method includes: a host CU receives OAM service QoS information from an access management function entity, and sends the OAM service QoS information to the host DU; further, The donor CU receives the BH RLC channel information allocated for the QoS information of the OAM service returned by the donor DU.
- the BH RLC channel information includes the identity of the BH RLC channel between the donor DU and the next hop node of the donor DU or the logic corresponding to the BH RLC channel Channel ID.
- an embodiment of the present application provides a communication device.
- the communication device includes a processor, which is coupled with a memory, and the memory is used to store a computer program or instruction, and the processor runs the computer program or instruction to enable the method of any one of the first aspect to the twelfth aspect described above When executed, the communication device may also include the memory.
- an embodiment of the present application provides a communication device that includes one or more modules for implementing the method of any one of the first aspect to the twelfth aspect, the one or more Each module may correspond to the steps of the method in any one of the first aspect to the twelfth aspect described above.
- an embodiment of the present application provides a chip, the chip includes a processor and an interface circuit, the interface circuit is coupled to the processor, and the processor is used to run a computer program or instruction to implement aspects such as the first aspect to In the method of any one of the twelfth aspect, the interface circuit is used to communicate with modules other than the chip.
- an embodiment of the present application provides a computer storage medium that stores a program for implementing the method in any one of the first to eighth aspects.
- the wireless communication device is caused to execute the method of any one of the first aspect to the twelfth aspect.
- the embodiments of the present application provide a computer program product, the program product includes a program, and when the program is executed, the method in any one of the first aspect to the twelfth aspect is executed.
- Figure 1 is a schematic diagram of a network architecture to which an embodiment of the application is applicable;
- FIG. 2A is an example of a network architecture including an application scenario of multiple IAB nodes
- FIG. 2B is another example of a network architecture including an application scenario of multiple IAB nodes
- FIG. 3A is a schematic diagram of the communication between the IAB node and the OAM server through the host DU;
- 3B is a schematic diagram of the IAB node 121 that can communicate with the OAM server through the host CU;
- 3C, 3D, 3E, and 3F are schematic diagrams of protocol stacks provided by embodiments of the present application.
- FIG. 4 is a schematic flowchart corresponding to a communication method provided in Embodiment 1 of this application;
- FIG. 5A is a schematic flowchart corresponding to yet another communication method provided in Embodiment 1 of this application.
- Figure 5B is a schematic diagram of establishing a BH RLC channel
- FIG. 6 is a schematic flowchart corresponding to yet another communication method provided in Embodiment 1 of this application.
- FIG. 7 is a schematic flowchart corresponding to another communication method provided in Embodiment 2 of this application.
- FIG. 8 is a schematic flowchart corresponding to yet another communication method provided in Embodiment 2 of this application.
- FIG. 9 is a schematic flowchart corresponding to yet another communication method provided in Embodiment 2 of this application.
- FIG. 10 is a possible exemplary block diagram of a device involved in an embodiment of this application.
- FIG. 11 is a schematic structural diagram of a device involved in an embodiment of this application.
- a terminal device is a device that provides users with voice and/or data connectivity.
- the terminal equipment may be referred to as user equipment (UE), mobile station (mobile station, MS), mobile terminal (mobile terminal, MT), etc., and may include, for example, a wireless connection function Handheld device, or processing device connected to a wireless modem.
- the terminal may communicate with the core network via a radio access network (RAN), and exchange voice and/or data with the RAN.
- RAN radio access network
- terminal equipment are: personal communication service (PCS) phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (personal digital assistant, PDA), barcode, radio frequency identification (RFID), sensors, global positioning system (GPS), laser scanners and other information sensing equipment.
- PCS personal communication service
- SIP session initiation protocol
- WLL wireless local loop
- PDA personal digital assistant
- RFID radio frequency identification
- sensors sensors
- GPS global positioning system
- laser scanners and other information sensing equipment.
- the terminal device can also be a wearable device.
- Wearable devices can also be called wearable smart devices. It is a general term for the application of wearable technology to intelligently design daily wear and develop wearable devices, such as glasses, gloves, watches, clothing and shoes.
- a wearable device is a portable device that is directly worn on the body or integrated into the user's clothes or accessories. Wearable devices are not only a hardware device, but also realize powerful functions through software support, data interaction, and cloud interaction. In a broad sense, wearable smart devices include full-featured, large-sized, complete or partial functions that can be achieved without relying on smart phones, such as smart watches or smart glasses, and only focus on a certain type of application function, and need to cooperate with other devices such as smart phones.
- the terminal can also be virtual reality (VR) equipment, augmented reality (AR) equipment, wireless terminals in industrial control, wireless terminals in self-driving (self-driving), remote surgery Wireless terminal in (remote medical surgery), wireless terminal in smart grid, wireless terminal in transportation safety, wireless terminal in smart city, and smart home Wireless terminals, etc.
- VR virtual reality
- AR augmented reality
- wireless terminals in industrial control wireless terminals in self-driving (self-driving)
- remote surgery Wireless terminal in remote surgery
- wireless terminal in smart grid wireless terminal in transportation safety
- wireless terminal in smart city and smart home Wireless terminals, etc.
- the function of the terminal device may be realized by a hardware component inside the terminal device, and the hardware component may be a processor and/or a programmable chip inside the terminal device.
- the chip may be implemented by an application-specific integrated circuit (ASIC) or a programmable logic device (PLD).
- ASIC application-specific integrated circuit
- PLD programmable logic device
- the above-mentioned PLD can be a complex programmable logical device (CPLD), a field-programmable gate array (FPGA), a generic array logic (generic array logic, GAL), a system on a chip , SOC) or any combination thereof.
- CPLD complex programmable logical device
- FPGA field-programmable gate array
- GAL generic array logic
- SOC system on a chip
- the donor base station can be an IAB donor (IAB donor), which is a device that connects terminal equipment to the wireless network in the communication system.
- IAB donor is a device that connects terminal equipment to the wireless network in the communication system.
- the donor base station is connected to the core network through a wired link.
- the donor base station may include radio network controller (RNC), node B (Node B, NB), base station controller (BSC), base transceiver station (base transceiver station, BTS).
- RNC radio network controller
- Node B, NB node B
- BSC base station controller
- base transceiver station base transceiver station
- home base station for example, home evolved NodeB, or home Node B, HNB), baseband unit (BBU), etc.
- BBU baseband unit
- LTE-A advanced long term evolution
- NodeB or eNB or e-NodeB, evolutional Node B can also include the evolution in the advanced long term evolution (LTE-A) Type base station (NodeB or eNB or e-NodeB, evolutional Node B), or may also include the next generation node B (gNB) in the 5G system (also called the new radio (NR) system) )Wait.
- the donor base station may include a centralized unit (CU) and a distributed unit (DU).
- This structure separates the protocol layer of the eNB in the long term evolution (LTE) system or the gNB in the NR system, and some protocol layers (such as the packet data convergence protocol (PDCP) layer and wireless
- PDCP packet data convergence protocol
- RRC radio resource control
- the functions of the resource control (radio resource control, RRC) layer are placed under the centralized control of the CU, and some or all of the protocol layers (such as the physical (PHY) layer, the media access control (MAC) layer, and the wireless link
- the functions of the radio link control (RLC) layer) are distributed in the DU, and the CU controls the DU.
- the CU of the donor base station may be referred to as the donor CU
- the DU of the donor base station may be referred to as the donor DU.
- the function of the donor base station may be implemented by hardware components inside the donor base station, such as a processor and/or a programmable chip inside the donor base station.
- the chip can be implemented by ASIC, or PLD.
- the aforementioned PLD may be any one of CPLD, FPGA, GAL, SOC or any combination thereof.
- the wireless backhaul equipment can provide wireless access services for the terminal equipment through the access link.
- the wireless backhaul equipment is connected to the host base station through a one-hop or multi-hop backhaul link to transmit the service data of the terminal equipment. Re-sending or forwarding of data to expand the coverage of the mobile communication system.
- the wireless backhaul device may be an IAB node, a relay station, a reception point (transmission reception point, TRP), or a transmission point (transmission point, TP), etc.
- the wireless backhaul device may include a mobile-termination (MT) unit and a DU. Communicate with the parent node (that is, the previous hop of the wireless backhaul device) through the MT unit, and communicate with the child node (that is, the next hop of the wireless backhaul device) through the DU.
- the wireless backhaul device may include at least one MT unit.
- the wireless backhaul device may include only one MT unit.
- the MT unit is an MT unit with multiple connections. The wireless backhaul device may pass through the MT unit.
- the wireless backhaul node may include multiple MT units, and each MT unit of the multiple MT units is connected to the wireless backhaul device.
- a parent node establishes a connection as an independent backhaul link of the wireless backhaul device.
- the function of the wireless backhaul device may be implemented by hardware components inside the wireless backhaul device, for example, a processor and/or a programmable chip inside the wireless backhaul device.
- the chip can be implemented by ASIC, or PLD.
- the aforementioned PLD may be any one of CPLD, FPGA, GAL, SOC or any combination thereof.
- the wireless backhaul device may have different names in different communication systems.
- the wireless backhaul device may be called a relay node (RN).
- the wireless backhaul device can be called an IAB node (IAB node).
- IAB node IAB node
- wireless backhaul devices can also have different names, which are not limited here.
- Link Refers to the path between two adjacent nodes in a path.
- Access link the link between the terminal device and the base station, or between the terminal device and the IAB node, or between the terminal device and the host node, or between the terminal device and the host DU.
- the access link includes a wireless link used when a certain IAB node is in the role of a common terminal device to communicate with its parent node. When the IAB node acts as an ordinary terminal device, it does not provide backhaul services for any child nodes.
- the access link includes an uplink access link and a downlink access link. In the embodiments of the present application, since the access link of the terminal device is a wireless link, the access link may also be called a wireless access link.
- Backhaul link the link between the IAB node and the parent node when it is used as a wireless backhaul node.
- the backhaul link includes an uplink backhaul link and a downlink backhaul link.
- the backhaul link since the backhaul link between the IAB node and the parent node is a wireless link, the backhaul link may also be called a wireless backhaul link.
- Each IAB node regards the neighboring node that provides wireless access service and/or wireless backhaul service for it as a parent node.
- each IAB node can be regarded as a child node of its parent node.
- the child node may also be called a lower-level node, and the parent node may also be called an upper-level node.
- the last hop node of a node refers to the last node in the path containing the node that received the data packet before the node. It can be understood that the previous hop node of a node may include the previous hop node of the node in uplink transmission and the previous hop node of the node in downlink transmission.
- the next hop node of a node refers to the first node in the path containing the node that receives the data packet after the node. It can be understood that the next hop node of a node may include the next hop node of the node in uplink transmission and the next hop node of the node in downlink transmission.
- the previous hop node refers to the parent node, and the next hop node refers to the child node.
- the next hop node refers to the child node, and the previous hop node refers to the parent node.
- multiple refers to two or more than two. In view of this, “multiple” can also be understood as “at least two” in the embodiments of the present application. "At least one" can be understood as one or more, for example, one, two or more. For example, including at least one refers to including one, two or more, and does not limit which ones are included. For example, including at least one of A, B, and C, then the included can be A, B, C, A and B, A and C, B and C, or A and B and C.
- the communication systems applicable to the embodiments of this application include, but are not limited to: narrowband-internet of things (NB-IoT) systems, wireless local access network (WLAN) systems, LTE systems, 5G systems, or after 5G Communication system, such as NR, device to device (device to device, D2D) communication system.
- NB-IoT narrowband-internet of things
- WLAN wireless local access network
- 5G 5G
- 5G Communication system such as NR
- D2D device to device
- the wireless backhaul device is an IAB node and the donor base station is an IAB donor as an example for description, where the IAB node is a specific name for the relay node in the IAB network, and does not limit the solution of the embodiment of the application.
- the use of IAB nodes in the embodiments of this application is only for the purpose of description, and does not mean that the solutions in the embodiments of this application are only used in NR scenarios.
- IAB nodes can generally refer to any node with a relay function.
- the IAB node may be any of the aforementioned base stations or terminal devices with a forwarding function, or may be an independent device form, which is not limited in the embodiment of the present application.
- FIG. 1 is a schematic diagram of a network architecture to which an embodiment of this application is applicable.
- the network architecture includes a terminal device 110, an IAB node 120, and a donor base station 130.
- the terminal device 110 is connected to the IAB node 120 in a wireless manner
- the IAB node 120 is connected to the donor base station 130 in a wireless manner.
- the terminal device 110 and the IAB node 120 and between the IAB node 120 and the donor base station 130 can communicate through a licensed spectrum, or communicate through an unlicensed spectrum, or at the same time through a licensed spectrum Communicate with unlicensed spectrum.
- the licensed spectrum can be a spectrum below 6 GHz, which is not restricted here.
- the IAB node regards the node providing the backhaul service as the only parent node.
- the IAB node 120 regards the donor base station 130 as the parent node.
- DRB data radio bearer
- the IAB node 120 receives the uplink data of the terminal device 110 on a certain data radio bearer (DRB)
- DRB data radio bearer
- the donor base station transmits the The uplink data is sent to the mobile gateway device (for example, the user port function (UPF) entity in the 5G system).
- the mobile gateway device sends the downlink data to the donor base station, and then sends it to the terminal device 110 via the IAB node 120 in turn.
- UPF user port function
- the network architecture may not be limited to include terminal devices, IAB nodes, and donor base stations. For example, it may also include core network equipment or equipment for carrying virtualized network functions, etc., which are obvious to a person of ordinary skill in the art, and will not be detailed here.
- the network architecture diagram shown in Figure 1 although one terminal device, one IAB node, and one donor base station are shown, the network architecture does not limit the number of terminal devices, IAB nodes, and donor base stations, for example, also It may include multiple terminal devices, multiple IAB nodes, multiple donor base stations, and so on.
- only one IAB node is included. In this embodiment of the application, the number and deployment locations of IAB nodes are not limited.
- Figure 2A and Figure 2B show two application scenarios examples.
- FIG. 2A is an example of a network architecture including an application scenario of multiple IAB nodes.
- the network architecture shown in Figure 2A can be understood as a multi-hop wireless backhaul scenario.
- the network architecture includes two IAB nodes and two terminal devices, the two IAB nodes are the IAB node 120 and the IAB node 121, respectively, and the two terminal devices are the terminal device 110 and the terminal device 111, respectively.
- the terminal device 110 and the terminal device 111 are respectively connected to the IAB node 121 in a wireless manner, the IAB node 121 is connected to the IAB node 120 in a wireless manner, and the IAB node 120 is connected to the donor base station 130 in a wireless manner.
- the IAB node 121 regards the IAB node 120 providing the backhaul service as the parent node, and the IAB node 120 regards the donor base station 130 as the parent node.
- the IAB node 121 After the IAB node 121 receives the uplink data of the terminal device 110 and the terminal device 111, it will sequentially pass through the IAB node 121 and the IAB node 120, and then transmit to the donor base station, which then sends the uplink data to the mobile gateway device.
- the mobile gateway device sends the downlink data of the terminal device to the donor base station, and then sends it to the terminal device 110 and the terminal device 111 via the IAB node 120 and the IAB node 121 in sequence.
- FIG. 2B is another example of a network architecture including an application scenario of multiple IAB nodes.
- the difference from FIG. 2A is that the network architecture shown in FIG. 2B includes three IAB nodes and one terminal device.
- the three IAB nodes are respectively IAB node 120 to IAB node 122, IAB node 120 to IAB node 122 and the host base station
- Two routing paths are formed between 130, one routing path is composed of IAB node 121, IAB node 122, and donor base station 130, and the other routing path is composed of IAB node 121, IAB node 120, and donor base station 130.
- the terminal device can communicate with the donor base station 130 through these two routing paths.
- the network architecture shown in Figure 2B can be understood as a multi-hop + multi-connection wireless backhaul scenario.
- the network architecture illustrated in FIG. 1, FIG. 2A, and FIG. 2B may further include an OAM server 140.
- the donor base station 130 may communicate with the OAM server 140, for example, in a wired manner.
- the IAB node After introducing the IAB node, the IAB node also needs to communicate with the OAM server.
- the IAB node obtains the accessible cell list information from the OAM server for the initial access of the IAB node; for example, the IAB node obtains it from the OAM server
- the DU-related configuration information of the IAB node such as the DU identifier, the DU cell identifier, etc., is used to start the DU module; another example, after the IAB node starts the DU module, the IAB node can send some information to the OAM server, such as service count information (traffic counters) and alarm information (alarms), or the IAB node can also obtain some information from the OAM server, such as software upgrade configuration.
- the embodiment of this application will mainly study the communication between the IAB node and the OAM server.
- the IAB node involved in the embodiment of the present application can be understood as an IAB node that has completed the initial access, and the specific implementation of the initial access is not limited in the embodiment of the present application.
- the communication between the IAB node and the OAM server involved in the embodiments of the present application is to transmit operation and maintenance (operation and maintenance, OM) configuration data, alarm data, traffic data, log data, or tracking data, etc.
- operation and maintenance operation and maintenance
- OM operation and maintenance
- the IAB node may send service counting information and alarm information to the OAM service, or the IAB node may receive the software upgrade configuration sent by the OAM service.
- the IAB node still obtains the accessible cell list information from the OAM server after completing the initial access.
- the IAB node in the embodiment of the present application may also obtain the accessible cell list from the OAM server. Information to verify whether the cell it is currently accessing is legal.
- the OAM service data packet is routed through the donor DU.
- the host DU can directly receive OAM service data packets from the OAM server (or through one or more routers to receive the OAM service
- the host DU can directly receive OAM service data packets from the OAM server (or through one or more routers to receive the OAM service
- the received OAM service data packet can be directly routed to the OAM server (or through 1 or Multiple routers are forwarded and routed to the OAM server, where there may be one or more routers on the path between the host DU and the OAM server).
- the IAB node 121 can communicate with the OAM server through the host DU, where the
- the OAM service data packet that the host DU interacts with the OAM server may be routed by the host CU. This means that the transmission of OAM service data packets does not need to pass through the core network of the IAB node.
- the OAM server can only learn the IP address of the host CU, and the host DU can only learn the IP address of the host CU, and the host CU can learn the IP address of the OAM server.
- the host CU After the host CU receives the OAM service data packet 1 sent by the IAB node from the host DU, it can forward the OAM service data packet 1 to the OAM server, or, after the host CU receives the OAM service data packet 2 from the OAM server, it analyzes the OAM service
- the data packet 2 knows whether the data packet is sent to itself or the IAB node DU. If it is sent to the IAB node DU, it can be further forwarded to the corresponding IAB node DU through the host DU.
- the host CU and the host DU can be connected to a unified OAM server (where the host DU can be connected to the OAM server through the host CU), that is, the same OAM server manages the host CU and the host DU.
- the IAB node 121 may communicate with the OAM server through the host CU, where the host CU and the OAM server are directly connected by wire.
- the IAB node communicating with the OAM server may include: the IAB node communicating with the OAM server through the host DU, or the IAB node communicating with the OAM server through the host CU.
- the two situations will be described in detail below in conjunction with specific embodiments.
- the IAB node is the IAB node 120 shown in FIG. 2A
- the host DU can directly communicate with the IAB node.
- the embodiments described below are mainly based on the case where one or more other IAB nodes exist between the IAB node and the host DU as an example.
- the description will be mainly directed to the implementation of the communication between the first IAB node and the OAM server through the host DU (such as the situation shown in FIG. 3A).
- the first IAB node is the IAB node 121 in FIG. 3A.
- the protocol stack for communication between the first IAB node and the OAM server may be as shown in FIG. 3C.
- TCP refers to transmission control protocol
- UDP refers to user datagram protocol
- Adapt is Refers to the adaptation layer.
- the IP address of the first IAB node can be understood as being allocated by the host DU.
- the IP address of the first IAB node can be assigned by the DHCP server and forwarded to the host DU.
- the host DU can be understood as a DHCP proxy (proxy).
- the communication between the first IAB node and the OAM server through the host DU may include downlink communication (for example: the first IAB node ⁇ -> ⁇ host DU ⁇ OAM server) and uplink communication (for example: the first IAB node ⁇ -> ⁇ host DU ⁇ OAM server).
- the host DU For downlink communication, an example is described by taking the host DU directly wired to the OAM server.
- the host DU can directly receive the first data packet from the OAM server (the first data packet is a data packet of the DU of the first IAB node).
- the first data packet is a data packet of the DU of the first IAB node.
- This part of the content will mainly study how the host DU sends the first data packet to the DU of the first IAB node.
- two possible solutions will be provided, namely, Solution 1 and Solution 2.
- FIG. 4 is a schematic diagram of a process corresponding to a communication method provided in Embodiment 1 of this application. As shown in FIG. 4, the method includes:
- Step 401 The host CU obtains the IP address of the first IAB node.
- the IP address of the first IAB node described here can be understood as the IP address of the DU of the first IAB node.
- the IP address of the DU of the first IAB node may be assigned by the host DU, or may be sent to the DU of the first IAB node through the host DU after being assigned by the DHCP server.
- the host CU may obtain the IP address of the DU of the first IAB node in various ways. In a possible implementation manner, the host CU can obtain the IP address of the DU of the first IAB node from the host DU.
- the host CU can assign The IP address and the information of the first IAB node are sent to the host CU, where the information of the first IAB node can be identified by the cell identification of the first IAB node and the cell wireless network temporary identification assigned by the access cell to the first IAB node (cell radio network temporary identifier, C-RNTI); accordingly, the host CU can obtain the IP address of the DU of the first IAB node.
- the information of the first IAB node can be identified by the cell identification of the first IAB node and the cell wireless network temporary identification assigned by the access cell to the first IAB node (cell radio network temporary identifier, C-RNTI); accordingly, the host CU can obtain the IP address of the DU of the first IAB node.
- the host CU may obtain the IP address of the DU of the first IAB node from the MT of the first IAB node. For example, after the DU of the first IAB node obtains the assigned IP address from the host DU, The MT of the first IAB node sends the IP address of the DU of the first IAB node to the host CU through an RRC message; accordingly, the host CU can obtain the IP address of the DU of the first IAB node.
- Step 402 The host CU determines the first routing information corresponding to the IP address of the DU of the first IAB node, and sends the first routing information corresponding to the IP address of the DU of the first IAB node to the host DU.
- the first routing information is used to route the first data packet to the first IAB node, and the destination IP address of the first data packet is the IP address of the DU of the first IAB node.
- the first data packet may be a data packet sent by the OAM server to the first IAB node, and the first data packet does not have a limiting effect.
- the host CU may send the IP address of the DU of the first IAB node and the first routing information corresponding to the IP address to the host DU.
- Step 403 The host DU receives the first routing information corresponding to the IP address of the DU of the first IAB node from the host CU.
- the host DU may receive the IP address of the DU of the first IAB node and the first routing information corresponding to the IP address from the host CU.
- the first routing information may include the identification of the first path or the first identification of the first IAB node.
- the first path is used to indicate the path from the host DU to the first IAB node, that is, the sending node on the first path is the host DU, and the receiving node on the first path is the first IAB node.
- the first identifier of the first IAB node may be an identifier assigned by the host CU to the first IAB node to identify the first IAB node, such as an adaptation layer identifier assigned by the host CU to the first IAB node, such as a backhaul adaptation layer Protocol (backhaul adaptation protocol) identification (ID).
- backhaul adaptation protocol backhaul adaptation protocol
- the host CU selects the path for the data packet; for example, the first IAB node is the IAB node 121 in FIG.
- the first routing information It may include the identification of path 1a (composed of IAB node 121, IAB node 122, and donor base station 130) or path 1b (composed of IAB node 121, IAB node 120, and donor base station 130); when the first routing information can include path 1a , It indicates that the path selected by the host CU for the data packet is path 1a, and when the first routing information may include path 1b, it indicates that the path selected by the host CU for the data packet is path 1b.
- the host DU checks the routing table information maintained by the host DU according to the first identifier of the first IAB node to learn the next hop node that sends the data packet. information.
- the first routing information may include the identifier of the second path and the second identifier of the first IAB node, or the identifier of the parent node of the first IAB node and the second identifier of the first IAB node.
- the second path is used to indicate the path from the host DU to the parent node of the first IAB node, that is, the sending node on the second path is the host DU, and the receiving node on the second path is the parent of the first IAB node. node.
- the identity of the parent node of the first IAB node may be the cell identity of the parent node of the first IAB node or the DU identity of the parent node of the first IAB node.
- the second identifier of the first IAB node may be at least one of the following: the C-RNTI allocated by the parent node of the first IAB node to the first IAB node; the first F1 allocated by the parent node of the first IAB node to the first IAB node Application protocol (F1application protocol, F1AP) identifier; the second F1AP identifier allocated by the host CU for the first IAB node.
- F1application protocol, F1AP Application protocol
- the host CU can establish a mapping relationship (or a correspondence relationship) between the IP address of the DU of the first IAB node and the first routing information.
- the mapping relationship may also include the IP address of the OAM server.
- the IP address of the OAM server may be obtained in advance by the host CU, or may be notified to the host CU by the host DU.
- mapping relationship between the IP address of the DU of the first IAB node and the first routing information See Table 1 for several possible examples of the mapping relationship between the IP address of the DU of the first IAB node and the first routing information.
- the mapping relationship between the IP address of the DU of the first IAB node and the first routing information may be one of multiple possible scenarios shown in Table 1.
- each row represents a possible situation of the mapping relationship.
- the meaning of the first row in Table 1 is: if the destination IP address of the data packet to be transmitted is the IP address of the DU of the first IAB node, the corresponding routing information includes the identification of the first path; for another example, in Table 1
- the meaning of the fifth line is: if the destination IP address of the data packet to be transmitted is the IP address of the DU of the first IAB node, and the source IP address is the IP address of the OAM server, the corresponding routing information includes the identifier of the first path.
- the target node in Table 1 may also be referred to as a target node, which is not specifically limited.
- the host CU may send the first routing information corresponding to the IP address of the DU of the first IAB node to the host DU (for example, it can be understood that the host CU notifies the host DU of the determined mapping relationship).
- the host CU may send F1AP signaling to the host DU.
- the F1AP signaling includes a parameter list, and the parameter list may include one or more items. Item information, each item of information includes two parameters; taking the two parameters included in one item of information as parameter 1 and parameter 2, for example, parameter 1 in this item of information may include the IP of the DU of the first IAB node Address, parameter 2 may include first routing information.
- parameter 1 and parameter 2 may be located in different information elements (information element, IE), for example, parameter 1 is located in IE1, and parameter 2 is located in IE2, which is not specifically limited.
- IE information element
- the host CU sends a mapping relationship to the host DU; in other possible embodiments, the host CU may send multiple mapping relationships to the host DU (the DU of multiple IAB nodes) Multiple routing information corresponding to the IP address), for example, the host CU sends F1AP signaling to the host DU.
- the F1AP signaling includes the IP addresses of the DUs of multiple IAB nodes and multiple routing information, and the IP addresses of the DUs of multiple IAB nodes One-to-one correspondence with multiple routing information.
- Step 404 The OAM server generates a first data packet, and sends the first data packet to the host DU.
- the OAM server After the OAM server obtains the IP address of the DU of the first IAB node, if it determines that it needs to send OAM data to the DU of the first IAB node, it can generate the first data packet, and the destination IP address of the first data packet is the first data packet.
- the IP address of the DU of an IAB node, and the source IP address is the IP address of the OAM server.
- the OAM server can obtain the IP address of the DU of the first IAB node in many ways. In a possible implementation, after the DU of the first IAB node obtains the IP address assigned by the host DU, it can The OAM server sends uplink information.
- the OAM server can obtain the IP address of the DU of the first IAB node.
- the DHCP server is directly deployed on the OAM server. Therefore, the OAM server directly allocates an IP address to the DU of the first IAB node.
- Step 405 The host DU receives the first data packet from the OAM server, and sends the first data packet and the first routing information to the next hop node of the host DU.
- the host DU may carry the first routing information in the adaptation layer of the host DU and send it to the next hop node of the host DU.
- the host DU can parse the IP layer of the first data packet to obtain the destination IP address of the first data packet (optionally, the source IP address can also be obtained); and the host DU can then From the mapping relationship received in step 403, the first routing information corresponding to the destination IP address is obtained.
- the first IAB node is the IAB node 121 shown in FIG. 2A
- the first routing information corresponding to the IP address of the DU of the IAB node 121 includes the identifier of the first path
- the first path is: host DU ⁇ IAB node 120 ⁇ IAB node 121.
- the host DU knows that the next hop node is the IAB node 120, and then the host DU can send the first data packet and the first routing information to the IAB node 120.
- the first IAB node is the IAB node 121 shown in FIG. 2A
- the first routing information corresponding to the IP address of the DU of the IAB node 121 includes the adaptation layer identifier of the IAB node 121 (such as the dynamic bandwidth allocation protocol ( bandwidth allocation protocol, BAP)ID).
- the host DU can learn that the next hop node that sends the first data packet is the IAB node 120 by looking up the routing table (in other examples, it is also possible to determine that the next hop node is the IAB node 122. The application embodiment does not limit this), and the host DU may send the first data packet and the first routing information to the IAB node 120.
- the host DU After obtaining the first routing information corresponding to the destination IP address, the host DU can learn the next hop node of the first data packet, and send the first data packet to the next hop node.
- the next hop node of the host DU may send the first data packet to the IAB node 121, thereby realizing the communication between the IAB node 121 and the OAM server.
- the above steps 401 to 405 mainly describe the implementation process of the host DU sending the first data packet to the next hop node of the host DU, and for the node between the first IAB node and the host DU, it can be directly based on
- the first routing information is used to transmit the first data packet.
- between the first IAB node and the host DU includes IAB node a and IAB node b, where IAB node b is the next hop node of the host DU.
- IAB node b is from the host DU After receiving the first data packet and the first routing information, the next hop node can be determined as the IAB node a according to the first routing information, and the first data packet and the first routing information are sent to the IAB node a; the IAB node a After the IAB node b receives the first data packet and the first routing information, it determines according to the first routing information that the next hop node is the first IAB node and the first IAB node is the destination node of the first data packet, and then the first The data packet is sent to the first IAB node.
- the description in FIG. 4 above is mainly based on an example in which the host CU determines the first routing information and sends it to the host DU.
- the host DU may also determine the first routing information, so that steps 401 to 403 may not be performed; accordingly, in step 405, after the host DU receives the first data packet, it may According to the destination IP address of the first data packet, determine the first routing information (for example, the corresponding IAB node can be determined as the first IAB node according to the destination IP address, and then query the pre-stored routing table according to the first identifier of the first IAB node To determine the first routing information), and send the first data packet and the first routing information to the next hop node of the host DU.
- the first routing information for example, the corresponding IAB node can be determined as the first IAB node according to the destination IP address, and then query the pre-stored routing table according to the first identifier of the first IAB node To determine the first routing information
- the first IAB node sends a DHCPdiscover message to the host DU through the parent node. If the host DU If a DHCP server is deployed on the host DU, the host DU directly processes the DHCP discover message; otherwise, the host DU further forwards the received DHCP discover message to the DHCP server. In the process of sending the DHCP discover message by the first IAB node, there can be two ways:
- the first IAB node MT When the first IAB node MT sends a DHCP discover message to the parent node, the first IAB node MT carries the identification of the first IAB node in its adaptation layer (for example, the host CU allocates the appropriate information for the first IAB node). Configuration layer identification) or the identification of the first IAB node (such as the C-RNTI assigned by the parent node DU cell) and the identification of the parent node of the first IAB node (such as the cell identification of the first IAB node accessing the parent node) ). The parent node further carries the information received from the adaptation layer of its DU in the adaptation layer of its MT and sends it to the host DU.
- the adaptation layer for example, the host CU allocates the appropriate information for the first IAB node.
- Configuration layer identification or the identification of the first IAB node (such as the C-RNTI assigned by the parent node DU cell) and the identification of the parent node of the first IAB
- Method 2 When the first IAB node MT sends a DHCP discover message to the parent node, and then the parent node forwards the DHCP discover message to the host DU, the MT of the parent node carries the identity of the first IAB node in its adaptation layer (e.g., parent The C-RNTI allocated by the node DU for the first IAB node and the identity of the parent node (for example, the cell identity of the parent node for the first IAB node to access) are sent to the host DU.
- the identity of the first IAB node in its adaptation layer e.g., parent
- the C-RNTI allocated by the node DU for the first IAB node and the identity of the parent node for example, the cell identity of the parent node for the first IAB node to access
- the host DU binds the IP address of the first IAB node DU with the information received from its adaptation layer, that is, the IP address of the first IAB node DU and the identity of the first IAB node (for example, the host CU is the The adaptation layer identifier assigned by the first IAB node has a corresponding relationship, or the IP address of the first IAB node DU and the identifier of the first IAB node (such as the C-RNTI assigned by the parent node DU cell) and the first The identifier of the parent node of the IAB node (for example, the cell identifier of the first IAB node accessing the parent node) has a corresponding relationship.
- the host DU After that, after the host DU receives the first data packet, it extracts the target IP address carried in the IP packet. If the target IP address is the IP address of the DU of the first IAB node, the host DU will use the previously bound correspondence relationship. To determine the route of the first data packet, the identification of the corresponding first IAB node (such as the adaptation layer identification assigned by the host CU for the first IAB node) or the identification of the first IAB node (such as the parent node DU cell is The assigned C-RNTI) and the identity of the parent node of the first IAB node (such as the cell identity of the first IAB node accessing the parent node) are carried in its adaptation layer and sent to the host DU together with the first data packet. Next hop node.
- the identification of the corresponding first IAB node such as the adaptation layer identification assigned by the host CU for the first IAB node
- the identification of the first IAB node such as the parent node DU cell is The assigned C-RNTI
- the host CU does not make routing decisions, so there is no need to know the IP address assigned by the first IAB node DU, and there is no need to send the corresponding relationship between the IP address of the first IAB node DU and the first routing information to the host DU.
- the host DU directly performs routing according to the corresponding relationship bound in the previous DHCP process.
- step 404 and step 405 are optional.
- the routing scheme in scheme one is also applicable to the transmission of DHCP discover/off/request/Ack messages, that is, the first data packet can be a DHCP discover/off/request/Ack message.
- FIG. 5A is a schematic flowchart corresponding to another communication method provided in Embodiment 1 of this application. As shown in FIG. 5A, the method includes:
- Step 501 The host CU obtains first information.
- Step 502 The host CU sends first bearer information corresponding to the first information to the host DU.
- the first bearer information is used to indicate a BH RLC channel that bears the first data packet, and the first data packet includes the first information.
- the first bearer information may be the identifier of the BH RLC channel or the identifier (logical channel ID, LCID) of the logical channel corresponding to the BH RLC channel.
- Step 503 The host DU receives first bearer information corresponding to the first information from the host CU.
- the BH RLC channel for transmitting OAM services can be a unique BH RLC channel predefined by the protocol.
- the BH RLC channel corresponding to the protocol predefined logical channel 1 is used to transmit OAM service data packets.
- the BH RLC channel for transmitting the OAM service may be the default BH RLC channel.
- the default BH RLC channel established when the first IAB node initially accesses.
- the BH RLC channel for transmitting OAM services may be established by the donor CU.
- the host CU may obtain the QoS information of the OAM service of the first IAB node, and then trigger the DU of the host DU and the related IAB node to establish transmission OAM.
- Business BH RLC channel may obtain the QoS information of the OAM service of the first IAB node in various ways. The embodiment of the present application provides a possible way as shown in FIG. 5B, including:
- Step a the first IAB node performs initial access.
- Step b During the initial access process of the first IAB node, the access management function entity obtains the subscription information of the first IAB node, and the subscription information includes the QoS information of the OAM service.
- the access management function entity may obtain the subscription information of the first IAB node from a home subscriber server (home subscriber server, HSS) or unified data management (unified data management, UDM).
- the access management function entity may be an access and mobility management function (AMF) entity.
- AMF access and mobility management function
- Step c The access management function entity sends the QoS information of the OAM service to the host CU.
- the access management function entity may send the QoS information of the OAM service to the host CU through an initial context setup request (initial context setup request).
- Step d The host CU receives the QoS information of the OAM service, and sends the QoS information of the OAM service to the host DU.
- the host CU may send the QoS information of the OAM service to the host DU through a context setup request (context setup request).
- Step e The donor DU receives the QoS information of the OAM service, allocates the corresponding BH RLC channel for the OAM service, and returns the assigned BH RLC channel identifier to the donor CU.
- the identifier of BH RLC channel 2 where BH RLC channel 2 is the RLC channel used to transmit OAM service data packets between the donor DU and the next hop node of the donor DU.
- the host DU may return the identity of the BH RLC channel 2 to the host CU through a context setup response (context setup response).
- the donor CU can also trigger the DU of the relevant IAB node to establish the corresponding BH RLC channel, which is similar to the process of triggering the donor DU to establish the BH RLC channel, and will not be repeated.
- the first information may be used to indicate that the data packet including the first information is an OAM service data packet.
- the first information may include at least one of the following: a differentiated services code point (DSCP) value; a flow label; an IP address of the OAM server; and a port number.
- DSCP differentiated services code point
- the DSCP value or flow identifier can be predefined through the protocol, or the DSCP value or flow identifier corresponding to the OAM service can also be determined by the host CU and the OAM server after negotiation.
- the DSCP value carried in the IP header field of the data packet can be used to identify the data packet as an OAM service data packet; for IPv6, the DSCP value or flow identifier carried in the IP header field of the data packet can be used To identify the data packet as an OAM service data packet.
- the IP address of the OAM server if the source IP address of the data packet is the IP address of the OAM server, it means that the data packet is an OAM service data packet.
- the port number the port number corresponding to the OAM service can be predefined through the protocol, or the port number corresponding to the OAM service can be determined by the host CU and the OAM server after negotiation. In this way, the port number of the data packet (source port Number and/or destination port number) to identify the data packet as an OAM service data packet.
- the first information may include.
- the first information may also include other possible information, as long as it is carried in a data packet and can identify the data packet as
- the information in the OAM service data packet can be any, and the specific information is not limited.
- the host CU sends the first bearer information corresponding to the OAM service data packet to the host DU.
- the host DU recognizes that the received data packet is an OAM service data packet, there is no limitation, which is left to implementation.
- the host CU may establish a mapping relationship between the first information and the first bearer information.
- BH RLC channel identification Flow identification BH RLC channel identification IP address of the OAM server BH RLC channel identification The port number BH RLC channel identification DSCP value The identifier of the logical channel corresponding to the BH RLC channel Flow identification The identifier of the logical channel corresponding to the BH RLC channel IP address of the OAM server The identifier of the logical channel corresponding to the BH RLC channel The port number The identifier of the logical channel corresponding to the BH RLC channel
- each row represents a possible mapping relationship.
- the meaning of the first row in Table 2 is: if the data packet to be transmitted includes the DSCP value, the corresponding bearer information is the identifier of the BH RLC channel; for example, the meaning of the third row in Table 2 is: if the data to be transmitted
- the source IP address of the packet is the IP address of the OAM server, and the corresponding bearer information is the identifier of the BH RLC channel.
- the identity of the BH RLC channel can be a newly defined identity.
- the meaning of other lines please refer to the first and third lines, and the details are not repeated here.
- the host CU may send multiple pieces of first information and multiple pieces of first bearer information to the host DU.
- the information may correspond to multiple pieces of first bearer information one to one.
- the donor CU can establish a mapping relationship between the first information and the identity of BH RLC channel 1 (or the identity of the logical channel corresponding to BH RLC channel 1), and the first information and the identity of BH RLC channel 1a ( Or the mapping relationship of the logical channel identifier corresponding to the BH RLC channel 1a).
- the host CU may determine (or establish) the mapping relationship between the first information and the first bearer information in multiple ways.
- the BH RLC channel is established in the manner shown in FIG. 5B, since the BH RLC channel is established based on the QoS information of the OAM service, and the information included in the first information is all information that can reflect the OAM service, Therefore, the donor CU can establish a mapping relationship between the first information and the BH RLC channel.
- the host CU can send the first bearer information corresponding to the first information to the host DU, which can be understood as notifying the host DU of the established mapping relationship.
- the DU sends the first routing information corresponding to the IP address of the DU of the first IAB node.
- the host CU may send F1AP signaling to the host DU.
- the F1AP signaling includes a parameter list, and the parameter list may include one item Or multiple pieces of information, each piece of information includes two parameters; taking the two parameters included in one item of information as parameter 1 and parameter 2, for example, parameter 1 in this item of information may include the first information, parameter 2
- the first bearer information may be included.
- the donor DU can learn that the first information corresponds to the first bearer information, and store the mapping relationship.
- parameter 1 and parameter 2 may be located in different IEs.
- parameter 1 is located in IE1 and parameter 2 is located in IE2, which is not specifically limited.
- Step 504 The OAM server generates a first data packet, and sends the first data packet to the host DU.
- the OAM server obtains the IP address of the DU of the first IAB node, if it determines that it needs to send data to the IP address of the DU of the IAB node, it can generate the first data packet, and the destination IP address of the first data packet is the first data packet.
- the IP address of the DU of an IAB node, and the source IP address is the IP address of the OAM server.
- the OAM server may also mark the corresponding DSCP value or flow label in the IP layer header field of the first data packet, that is, the IP layer header field of the first data packet includes the DSCP value or flow label.
- Step 505 The host DU receives the first data packet from the OAM server, and sends the first data packet to the next hop node of the host DU.
- the host DU may map the first data packet in the corresponding BH RLC channel and send it to the next hop node of the host DU.
- the host DU can parse the IP layer of the first data packet to obtain the first information (such as DSCP value or flow label); in turn, the host DU can, according to the information received in step 503, Obtain the BH RLC channel corresponding to the DSCP value or flow label, such as BH RLC channel 1.
- the donor DU receives the mapping relationship between the first information and the identifier of the BH RLC channel 1 from the donor CU, and the first information and the BH RLC channel 1a
- the host DU can obtain the next hop node (such as IAB node 120) of the host DU in the path of transmitting the first data packet based on the routing information of the first data packet, and then can determine the DSCP value or flow label
- the corresponding BH RLC channel is BH RLC channel 1.
- the next hop node of the host DU may send the first data packet to the IAB node 121 (that is, the first IAB node), thereby realizing the communication between the IAB node 121 and the OAM server.
- the above steps 501 to 505 mainly describe the implementation process of the host DU mapping the first data packet to the corresponding BH RLC channel and send it to the next hop node of the host DU, and for the communication between the first IAB node and the host DU
- it can map the first data packet to the corresponding BH RLC channel and send it to the next hop according to the mapping relationship between the import BH RLC channel (ingress BH RLC channel) and the export BH RLC channel (egress BH RLC channel) node.
- the mapping relationship between the ingress BH RLC channel and the egress BH RLC channel can be determined by the host CU and sent to the corresponding IAB node.
- the first IAB node and the host DU includes IAB node a and IAB node b, where IAB node b is the next hop node of the host DU.
- IAB node b is from the host DU
- it can map the first data packet to the corresponding BH RLC channel (such as BH RLC channel 1b) according to the first bearer information and send it to IAB node a;
- IAB node a receives it through BH RLC channel 1b
- the first data packet is mapped to the corresponding BH RLC channel (for example, the BH RLC channel 1c) and sent to the first IAB node.
- FIG. 5A is described with an example in which the host CU determines the first bearer information and sends it to the host DU.
- the host CU may also determine a downlink filter (DL filter) and send it to the host DU.
- the downlink filter is used to map the downlink data packet to be transmitted to the corresponding BH RLC channel for transmission.
- DL filter can filter the downlink data packet according to the source address and/or destination address of the downlink data packet, and/or the source port number and/or destination port number, and directly map the downlink data packet to the corresponding BH RLC Channel.
- the host DU receives the first data packet from the OAM server, and can map the first data packet to the corresponding BH RLC channel through the downlink filter and send it to the next hop node; other content except this difference can refer to the above Description in Figure 5A.
- the host CU may not configure the mapping relationship for the host DU, and the host DU directly performs the mapping. That is, the host DU determines that the first bearer information corresponding to the first information has not been received from the host CU. That is: if there is only one BH RLC channel between the host DU and the next hop node after the route is determined, the host DU directly maps the data packet to the BH RLC channel for transmission after receiving the first data packet.
- the host DU recognizes that the first data packet is an OAM service data packet (e.g., by source IP address or port number, Or pre-configured DSCP/flow label), the host DU maps the packet to the first established BH RLC channel or to the default BH RLC channel or the standard BH RLC channel reserved for OAM service transmission .
- This mapping method is also applicable to the transmission of F1setup request/response messages and DHCP discover/off/request/Ack messages.
- the host CU may also determine the mapping relationship (referred to as the mapping relationship 1) between the IP address of the DU of the first IAB node and the DSCP (or flow identifier) and the DSCP (or flow identifier) and the first A mapping relationship of bearer information (called mapping relationship 2).
- the OAM server does not need to mark the corresponding DSCP value or flow label in the IP layer header field of the first data packet. Accordingly, the host DU receives After the first data packet, the corresponding DSCP (or flow identifier) can be obtained according to the destination IP address of the first data packet and the mapping relationship 1, and then the first bearer information can be obtained according to the mapping relationship 2.
- mapping relationship 1 the mapping relationship between the IP address of the DU of the first IAB node and the DSCP (or flow identifier) and the DSCP (or flow identifier) and the first A mapping relationship of bearer information (called mapping relationship 2).
- the OAM server does not need to mark the corresponding DSCP value or flow label in
- scheme 1 focuses on describing routing information
- scheme 2 focuses on describing bearer information, and other content besides this difference
- scheme 1 and scheme Two can be cross-referenced.
- the methods described in Scheme 1 and Scheme 2 can be implemented separately, or can also be implemented in combination, which is not specifically limited.
- step 504 and step 505 are optional.
- the host DU is directly connected to the OAM server by wire as an example.
- the host DU can directly send the second data packet to the OAM server (the destination IP address of the second data packet may be the IP address of the OAM server).
- This part of the content will mainly study how the first IAB node (for example, the DU of the first IAB node here) sends the second data packet to the host DU.
- two possible solutions will be provided, namely, solution one and Option II.
- FIG. 6 is a schematic flow diagram corresponding to another communication method provided in Embodiment 1 of this application. As shown in FIG. 6, the method includes:
- Step 601 The host CU obtains the IP address of the OAM server.
- the host CU can obtain the IP address of the OAM server in a variety of ways, which are not specifically limited.
- Step 602 The host CU determines the second routing information corresponding to the IP address of the OAM server, and sends the second routing information corresponding to the IP address of the OAM server to the first IAB node.
- the second routing information is used to route the second data packet to the host DU, and the destination IP address of the second data packet is the IP address of the OAM server.
- the second routing information may include the identifier of the third path or the identifier of the fourth path, the sending node on the third path is the first IAB node, and the receiving node on the third path is the host DU; the sending node on the fourth path is the last hop node of the first IAB node, and the receiving node on the fourth path is the host DU.
- Step 603 The first IAB node receives the second routing information corresponding to the IP address of the OAM server from the host CU.
- the DU of the first IAB node receives the second routing information corresponding to the IP address of the OAM server from the host CU.
- Step 604 The first IAB node generates a second data packet.
- the DU of the first IAB node generates the second data packet.
- the DU of the first IAB node obtains the IP address of the OAM server, if it is determined that data needs to be sent to the IP address of the OAM server, a second data packet can be generated, and the source IP address of the second data packet is the first IAB
- the IP address of the DU of the node, and the destination IP address is the IP address of the OAM server.
- the DU of the first IAB node may obtain the IP address of the OAM server in multiple ways, which are not limited in the embodiment of the present application.
- Step 605 The first IAB node sends the second data packet and the second routing information to the previous hop node of the first IAB node.
- the host CU may not need for the host CU to send the determined first routing information to the first IAB node, so steps 601 to 603 may not be performed; accordingly, in step 605, the first IAB After the node generates the second data packet, it determines the first routing information (such as the identifier of the host DU, or the IP address of the host DU), and carries the second routing information in its adaptation layer and sends the second data packet together The last hop node for the first IAB node.
- the first routing information such as the identifier of the host DU, or the IP address of the host DU
- the idea of the method described in scheme 1 of uplink communication is similar to the idea of the method described in scheme 1 of downlink communication.
- the differences include: for example, in downlink communication, the host DU will A data packet and the first routing information are sent to the next hop node of the host DU, and in the uplink communication, the first IAB node (for example, the MT of the first IAB node) connects the second data packet and the second route The information is sent to the previous hop node of the first IAB node. All content except differences can be cross-referenced.
- FIG. 7 is a schematic flow diagram corresponding to another communication method provided in Embodiment 2 of this application. As shown in FIG. 7, the method includes:
- Step 701 The host CU obtains second information.
- Step 702 The host CU determines the second bearer information corresponding to the second information, and sends the second bearer information corresponding to the second information to the first IAB node.
- the second bearer information is used to indicate the BH RLC channel for transmitting the second data packet, and the second data packet includes the second information.
- the second bearer information may be the identifier of the BH RLC channel or the identifier of the logical channel corresponding to the BH RLC channel.
- Step 703 The first IAB node receives second bearer information corresponding to the second information from the host CU.
- the MT of the first IAB node receives the second bearer information corresponding to the second information from the host CU.
- Step 704 the first IAB node generates a second data packet.
- the DU of the first IAB node generates the second data packet.
- the DU of the first IAB node may add the corresponding DSCP value or flow label in the IP layer header field of the second data packet, that is, the IP layer header field of the second data packet includes the DSCP value or flow Label; further, the DU of the first IAB node is sent to the MT of the first IAB node through the internal interface.
- Step 705 The first IAB node maps the second data packet to the corresponding BH RLC channel according to the second bearer information and sends it to the previous hop node of the first IAB node.
- the MT of the second IAB node may map the second data packet to the corresponding BH RLC channel and send it to the previous hop node of the first IAB node according to the mapping relationship obtained from the host CU.
- the idea of the method described in the second uplink communication scheme is similar to the idea of the method described in the second downlink communication scheme.
- the differences include: for example, in downlink communication, the host DU transfers the first A data packet is mapped to the corresponding BH RLC channel and sent to the next hop node of the host DU, while in uplink communication, the MT of the first IAB node maps the second data packet to the corresponding BH RLC channel and sends it to the first The previous hop node of the IAB node.
- the BH RLC channel for transmitting OAM services can be a unique BH RLC channel predefined by the protocol.
- the BH RLC channel corresponding to the protocol predefined logical channel 1 is used to transmit OAM service data packets.
- the BH RLC channel for transmitting the OAM service may be the default BH RLC channel.
- the BH RLC channel that transmits OAM services can be triggered by the donor CU.
- the host CU can obtain the QoS information of the OAM service of the first IAB node, and then trigger the host DU and the DU of the related IAB node to establish the BH for OAM service transmission. RLC channel.
- the host CU may not configure the mapping relationship for the MT of the first IAB node, and the MT of the first IAB node directly performs the mapping. That is: if there is only one BH RLC channel between the MT of the first IAB node and the last hop node (parent node) after the route is determined, the MT of the first IAB node directly sends the data packet after receiving the first data packet. Mapping to the BH RLC channel for transmission.
- the MT of the first IAB node learns that the first data packet is an OAM service data packet ( For example: by source IP address, or port number, or pre-configured DSCP/flow label), the MT of the first IAB node maps the data packet to the first established BH RLC channel or maps to the default BH RLC channel On the channel or the BH RLC channel reserved by the standard for OAM service transmission.
- This mapping method is also applicable to the transmission of F1setup request/response messages and DHCP discover/off/request/Ack messages.
- scheme 1 focuses on describing routing information
- scheme 2 focuses on describing bearer information, and other content besides this difference
- scheme 1 and scheme Two can be cross-referenced.
- the methods described in Scheme 1 and Scheme 2 can be implemented separately, or can also be implemented in combination, which is not specifically limited.
- one or more other IAB nodes exist between the first IAB node and the host DU as an example for description. If there are no other IAB nodes between the first IAB node and the host DU, For example, the first IAB node is the IAB node 120 shown in FIG. 2A. In this case, from the perspective of routing, the host DU can directly communicate with the first IAB node.
- the first data packet can be directly sent to the first IAB node; from the perspective of the bearer, it can also use the method described in the second solution above to determine the BH RLC channel between the host DU and the first IAB node , And map the first data packet to the BH RLC channel and send it to the first IAB node.
- the description will mainly focus on the implementation of the communication between the first IAB node and the OAM server through the host CU (such as the situation shown in FIG. 3B).
- the IP address of the first IAB node may be assigned by the host CU, or may be assigned by the DHCP server, and the host CU serves as a DHCP proxy.
- the communication between the first IAB node and the OAM server through the host CU may include downlink communication (for example: the first IAB node ⁇ -> ⁇ host CU ⁇ OAM server) and uplink communication (for example: the first IAB node ⁇ -> ⁇ host CU ⁇ OAM server).
- downlink communication for example: the first IAB node ⁇ -> ⁇ host CU ⁇ OAM server
- uplink communication for example: the first IAB node ⁇ -> ⁇ host CU ⁇ OAM server.
- the uplink communication can refer to the description in the first embodiment. Only the downlink communication is introduced below.
- the host CU may forward the data packet received from the OAM server to the host DU, and then the host DU sends the first data packet to the first IAB node.
- the host CU may forward the data packet received from the OAM server to the host DU, and then the host DU sends the first data packet to the first IAB node.
- two possible schemes will be provided, namely scheme one and scheme two.
- the protocol stack for the communication between the first IAB node and the OAM server is shown in FIG. 3D Shown.
- Fig. 8 is a schematic flow diagram corresponding to another communication method provided in the second embodiment of the application. As shown in Fig. 8, the method includes:
- Step 801 The OAM server generates a first data packet, and sends the first data packet to the host CU.
- the OAM layer of the first data packet includes the identifier of the DU of the first IAB node.
- Step 802 The host CU receives the first data packet from the OAM server.
- the host CU parses the OAM layer of the first data packet to obtain the identifier of the DU of the first IAB node, and can learn that the first data packet is a data packet that needs to be sent to the first IAB node, and can further combine the first data packet with The first routing information is sent to the host DU.
- Step 804 After receiving the first data packet and the first routing information, the host DU determines the next hop node of the host DU according to the first routing information, and sends the first data and the first routing information to the next hop of the host DU node.
- the difference between the method described in the downlink communication scheme 1 of the second embodiment and the method described in the downlink communication scheme 1 of the embodiment includes: For example, in the downlink communication scheme 1 of the embodiment 1, the host The CU determines the first routing information and sends it to the host DU.
- the subsequent host DU After the subsequent host DU receives the first data packet from the OAM server, it can obtain the corresponding first routing information according to the destination IP address of the first data packet, and transfer the first data
- the packet and the first routing information are sent to the next hop node of the host DU; in the first downlink communication scheme in the second embodiment, after the host CU receives the first data packet from the OAM server, the first data packet and the first route
- the information is sent to the host DU together; for example, in the first downlink communication scheme in the first embodiment, the host CU determines the corresponding first routing information based on the IP address of the DU of the first IAB node, while in the second embodiment, the downlink communication In the first solution, the host CU determines the corresponding first routing information based on the identifier of the DU of the first IAB node. Except for differences, the two can refer to each other.
- the protocol stack for the communication between the first IAB node and the OAM server is shown in FIG. 3E And shown in Figure 3F.
- the difference between the protocol stacks of Figure 3E and Figure 3F is that the ip-in-ip method is adopted in Figure 3F, that is, the OAM service data packet (IP packet) is encapsulated in the IP packet between the host CU and the host DU for transmission .
- the host DU is similar to a router, and forwards data packets according to the IP address of the OAM service.
- FIG. 9 is a schematic flow diagram corresponding to another communication method provided in Embodiment 2 of this application. As shown in FIG. 9, the method includes:
- Step 901 The OAM server generates a first data packet, and sends the first data packet to the host CU.
- the OAM server obtains the IP address of the DU of the first IAB node, if it determines that it needs to send data to the first IAB node, it can generate a first data packet, and the destination IP address of the first data packet is the first IAB node
- the IP address of the DU, the source IP address is the IP address of the OAM server.
- Step 902 The host CU receives the first data packet from the OAM server.
- Step 903 The host CU parses the IP layer of the first data packet to obtain the destination IP address, and then sends the first data packet and the first routing information to the host DU.
- Step 904 After receiving the first data packet and the first routing information, the host DU determines the next hop node of the host DU according to the first routing information, and sends the first data and the first routing information to the next hop of the host DU node.
- the difference between the method described in the second downlink communication scheme 2 in the second embodiment and the method described in the downlink communication scheme 1 of the second embodiment includes: for example, in the downlink communication scheme 1 of the second embodiment, the host After the CU receives the first data packet from the OAM server, it determines the first routing information based on the identifier of the DU of the first IAB node included in the first data packet. In the second embodiment of downlink communication, the host CU receives After the OAM server receives the first data packet, it determines the first routing information based on the destination IP address of the first data packet. Except for differences, the two can refer to each other.
- first and second embodiments it should be noted that the first or second solutions in the second embodiment can be implemented separately, or they can be implemented in combination with the second downlink communication solution in the first embodiment. limited.
- step numbers involved in the foregoing embodiments of the present application are only a possible example of the execution process, and do not constitute a restriction on the order of execution of the respective steps.
- the steps shown in the above drawings are not mandatory.
- additions and deletions can be made based on the above drawings, which are not specifically limited.
- the host CU and the host DU may include corresponding hardware structures and/or software modules for performing various functions.
- the embodiments of the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed by hardware or computer software-driven hardware depends on the specific application and design constraint conditions of the technical solution. Professionals and technicians can use different methods for each specific application to implement the described functions, but such implementation should not be considered beyond the scope of this application.
- FIG. 10 shows a possible exemplary block diagram of the device involved in the embodiment of the present application.
- the apparatus 1000 may include: a processing unit 1002 and a communication unit 1003.
- the processing unit 1002, the communication unit 1003, and the storage unit 1001 are connected by a communication bus.
- the communication unit 1003 may be a device with a transceiving function and used to communicate with other devices.
- the storage unit 1001 may include one or more memories.
- the storage unit 1001 can exist independently and is connected to the processing unit 1002 through a communication bus.
- the storage unit 1001 may also be integrated with the processing unit 1201.
- the processing unit 1002 is used to control and manage the actions of the device 1000.
- the communication unit 1003 is used to support communication between the device 1000 and other network entities.
- the communication unit 1003 is also referred to as a transceiver unit, and may include a receiving unit and/or a sending unit, which are used to perform receiving and sending operations, respectively.
- the device 1000 may further include a storage unit 1001 for storing program codes and/or data of the device 1000.
- the processing unit 1002 may be a processor or a controller, which may implement or execute various exemplary logical blocks, modules, and circuits described in conjunction with the disclosure of the embodiments of the present application.
- the communication unit 1003 may be a communication interface, a transceiver, or a transceiver circuit, etc., where the communication interface is a general term. In a specific implementation, the communication interface may include multiple interfaces.
- the storage unit 1001 may be a memory.
- the device 1000 may be the host DU in any of the above embodiments, or may also be a chip set in the host DU.
- the processing unit 1002 may support the device 1000 to perform the actions of the host DU in the foregoing method examples.
- the processing unit 1002 mainly executes the internal actions of the host DU in the method example, and the communication unit 1003 can support communication between the apparatus 1000 and other devices.
- the communication unit 1003 is used to perform step 403 and step 404 in FIG. 4.
- the communication unit is configured to receive from the host centralized unit CU the Internet Protocol IP address of the first access backhaul integrated IAB node and first routing information, and the first routing information is used for Routing the first data packet to the first IAB node, where the first data packet is an OAM service data packet, and the destination IP address of the first data packet is the IP address of the first IAB node;
- the OAM server receives the first data packet; and sends the first data packet and the first routing information to the next hop node of the host DU.
- the first routing information includes: the identifier of the first path, the sending node on the first path is the host DU, and the receiving node on the first path is the first path.
- the first identifier of the first IAB node is an adaptation layer identifier allocated by the hosting centralized unit CU to the first IAB node.
- the first routing information includes: the identifier of the second path and the second identifier of the first IAB node, the sending node on the second path is the host DU, and The receiving node on the second path is the parent node of the first IAB node; or, the identifier of the parent node of the first IAB node and the second identifier of the first IAB node.
- the second identity of the first IAB node is the cell radio network temporary identity C-RNTI allocated by the parent node of the first IAB node to the first IAB node, or the The second identifier of the first IAB node is the first F1AP identifier assigned to the first IAB node by the parent node of the first IAB node; or, the second identifier of the first IAB node includes the first F1AP An identifier and a second F1AP identifier allocated by the host CU to the first IAB node.
- the communication unit is specifically configured to: the host DU carries the first routing information in the adaptation layer of the host DU and sends it to the next hop node of the host DU.
- the communication unit is further configured to receive first information and first bearer information from the donor CU, where the first bearer information is used to indicate the backhaul radio link control BH RLC for transmitting the first data packet Channel;
- the first data packet includes the first information, the first information includes at least one of the following: differentiated services code point DSCP value, flow label, the IP address of the OAM server, port number;
- the first data packet is mapped to the next hop node sent to the donor DU in the BH RLC channel.
- the communication unit is configured to receive first information and first bearer information from the donor CU, where the first bearer information is used to indicate a BH RLC channel for transmitting the first data packet, and the first data packet
- the first information is included, and the first information includes at least one of the following: DSCP value, flow label, IP address and port number of the OAM server; receiving the first data packet from the OAM server; and The first data packet is mapped to the next hop node sent to the donor DU in the BH RLC channel.
- the device 1000 may be the host CU in any of the foregoing embodiments, or may also be a chip provided in the host CU.
- the processing unit 1002 may support the apparatus 1000 to perform the actions of the host CU in the foregoing method examples.
- the processing unit 1002 mainly executes the internal actions of the host CU in the method example, and the communication unit 1003 can support communication between the apparatus 1000 and other devices.
- the communication unit 1003 is used to perform step 401 in FIG. 4, and the processing unit may be used to perform step 404 in FIG.
- the communication unit is configured to obtain the IP address of the first IAB node and first routing information, where the first routing information is used to route the first data packet to the first IAB node, wherein, the first data packet is an OAM service data packet, and the destination IP address of the first data packet is the IP address of the first IAB node; and sending the IP address of the first IAB node to the host DU And the first routing information.
- the first routing information includes: the identifier of the first path, the sending node on the first path is the host DU, and the receiving node on the first path is the first path.
- the first identifier of the first IAB node is an adaptation layer identifier allocated by the hosting centralized unit CU to the first IAB node.
- the first routing information includes: the identifier of the second path and the second identifier of the first IAB node, the sending node on the second path is the host DU, and The receiving node on the second path is the parent node of the first IAB node; or, the identifier of the parent node of the first IAB node and the second identifier of the first IAB node.
- the second identifier of the first IAB node is the C-RNTI allocated to the first IAB node by the parent node of the first IAB node, or the C-RNTI of the first IAB node
- the second identifier is the first F1AP identifier assigned to the first IAB node by the parent node of the first IAB node; or, the second identifier of the first IAB node includes the first F1AP identifier and the host The second F1AP identifier allocated by the CU to the first IAB node.
- the communication unit is further configured to send first information and first bearer information to the donor DU, where the first bearer information is used to indicate a BH RLC channel for transmitting the first data packet, and
- the first data packet includes the first information, and the first information includes at least one of the following: a DSCP value, a flow label, an IP address of the OAM server, and a port number.
- the communication unit is configured to obtain first information and first bearer information, where the first bearer information is used to indicate a BH RLC channel for transmitting a first data packet, and the first data packet includes the First information, the first information includes at least one of the following: DSCP value, flow label, IP address and port number of the OAM server; and sending the first information and the first bearer information to the host DU .
- FIG. 11 is a schematic structural diagram of an apparatus involved in an embodiment of the application.
- it may be a schematic structural diagram of a base station, or exemplarily may be a structural schematic diagram of a donor base station.
- the DUs included therein may be Refers to the host DU, and the included CU may be the host CU.
- the base station can be applied to the system shown in FIG. 1 or FIG. 2A or FIG. 2B to perform the functions of the donor base station in the foregoing method embodiment.
- the base station 110 may include one or more DU 1101 and one or more CU 1102.
- the DU 1101 may include at least one antenna 11011, at least one radio frequency unit 11012, at least one processor 11013, and at least one memory 11014.
- the DU 1101 part is mainly used for the transmission and reception of radio frequency signals, the conversion of radio frequency signals and baseband signals, and part of baseband processing.
- the CU1102 may include at least one processor 11022 and at least one memory 11021.
- CU1102 and DU1101 can communicate through interfaces, where the control plan interface can be Fs-C, such as F1-C, and the user plane (User Plan) interface can be Fs-U, such as F1-U.
- the CU 1102 part is mainly used to perform baseband processing, control the base station, and so on.
- the DU 1101 and CU1102 may be physically set together, or may be physically separated, that is, a distributed base station.
- the CU 1102 is the control center of the base station, which may also be called a processing unit, and is mainly used to complete the baseband processing function.
- the CU 1102 may be used to control the base station to execute the operation procedure of the network device in the foregoing method embodiment.
- the baseband processing on the CU and DU can be divided according to the protocol layer of the wireless network.
- the functions of the PDCP layer and above are set in the CU, and the protocol layers below the PDCP, such as the RLC layer and MAC layer, are set in the DU.
- the CU implements the functions of the RRC layer and the PDCP layer
- the DU implements the functions of the RLC layer, the MAC layer, and the physical layer.
- the donor base station 110 may include one or more radio frequency units (RU), one or more DUs, and one or more CUs.
- the DU may include at least one processor 11013 and at least one memory 11014
- the RU may include at least one antenna 11011 and at least one radio frequency unit 11012
- the CU may include at least one processor 11022 and at least one memory 11021.
- the CU1102 may be composed of one or more single boards, and multiple single boards may jointly support a single access indication wireless access network (such as a 5G network), or may respectively support different access standards Wireless access network (such as LTE network, 5G network or other networks).
- the memory 11021 and the processor 11022 may serve one or more boards. In other words, the memory and the processor can be set separately on each board. It can also be that multiple boards share the same memory and processor. In addition, necessary circuits can be provided on each board.
- the DU1101 can be composed of one or more single boards.
- Multiple single boards can jointly support a wireless access network with a single access indication (such as a 5G network), and can also support wireless access networks with different access standards (such as LTE network, 5G network or other network).
- the memory 11014 and the processor 11013 may serve one or more boards. In other words, the memory and the processor can be set separately on each board. It can also be that multiple boards share the same memory and processor. In addition, necessary circuits can be provided on each board.
- the DU in the donor base station 110 may send the data packet to the MT in the next hop node of the donor DU through the antenna, and then the MT in the next hop node of the donor DU sends the data packet to the host through the internal interface.
- the DU in the next hop node of the DU may send the data packet to the MT in the next hop node of the donor DU through the antenna, and then the MT in the next hop node of the donor DU sends the data packet to the host through the internal interface.
- the DU in the next hop node of the DU may send the data packet to the MT in the next hop node of the donor DU through the antenna, and then the MT in the next hop node of the donor DU sends the data packet to the host through the internal interface.
- the DU in the next hop node of the DU may send the data packet to the MT in the next hop node of the donor DU through the antenna, and then the MT in the next hop node of the donor DU send
- each step in the method provided in this embodiment can be completed by an integrated logic circuit of hardware in the processor or instructions in the form of software.
- the steps of the method disclosed in the embodiments of the present application may be directly embodied as being executed and completed by a hardware processor, or executed and completed by a combination of hardware and software modules in the processor.
- the processor in the embodiment of the present application may be an integrated circuit chip with signal processing capability.
- the steps of the foregoing method embodiments can be completed by hardware integrated logic circuits in the processor or instructions in the form of software.
- the aforementioned processor may be a general-purpose central processing unit (central processing unit, CPU), general-purpose processor, digital signal processing (digital signal processing, DSP), application specific integrated circuits (ASIC), field programmable gate array Field programmable gate array (FPGA) or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof; it can also be a combination that implements computing functions, such as a combination of one or more microprocessors, DSP and micro-processing The combination of the device and so on.
- the general-purpose processor may be a microprocessor or the processor may also be any conventional processor or the like.
- the memory or storage unit in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory.
- the non-volatile memory can be read-only memory (ROM), programmable read-only memory (programmable ROM, PROM), erasable programmable read-only memory (erasable PROM, EPROM), and electronic Erase programmable read-only memory (electrically EPROM, EEPROM) or flash memory.
- the volatile memory may be random access memory (RAM), which is used as an external cache.
- RAM random access memory
- static random access memory static random access memory
- dynamic RAM dynamic random access memory
- DRAM dynamic random access memory
- SDRAM synchronous dynamic random access memory
- double data rate synchronous dynamic random access memory double data rate SDRAM, DDR SDRAM
- enhanced synchronous dynamic random access memory enhanced SDRAM, ESDRAM
- serial link DRAM SLDRAM
- direct rambus RAM direct rambus RAM
- the above embodiments it may be implemented in whole or in part by software, hardware, firmware or any combination thereof.
- software it can be implemented in the form of a computer program product in whole or in part.
- the computer program product includes one or more computer programs or instructions.
- the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices.
- the computer program or instruction may be stored in a computer-readable storage medium, or transmitted through the computer-readable storage medium.
- the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server integrating one or more available media.
- the usable medium may be a magnetic medium, such as a floppy disk, a hard disk, and a magnetic tape; it may also be an optical medium, such as a DVD; it may also be a semiconductor medium, such as a solid state disk (SSD).
- the various illustrative logic units and circuits described in the embodiments of this application can be implemented by general-purpose processors, digital signal processors, application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, Discrete gates or transistor logic, discrete hardware components, or any combination of the above are designed to implement or operate the described functions.
- the general-purpose processor may be a microprocessor, and optionally, the general-purpose processor may also be any traditional processor, controller, microcontroller, or state machine.
- the processor can also be implemented by a combination of computing devices, such as a digital signal processor and a microprocessor, multiple microprocessors, one or more microprocessors combined with a digital signal processor core, or any other similar configuration achieve.
- the steps of the method or algorithm described in the embodiments of the present application can be directly embedded in hardware, a software unit executed by a processor, or a combination of the two.
- the software unit can be stored in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM or any other storage medium in the field.
- the storage medium may be connected to the processor, so that the processor can read information from the storage medium, and can store and write information to the storage medium.
- the storage medium may also be integrated into the processor.
- the processor and the storage medium can be arranged in an ASIC, and the ASIC can be arranged in a terminal device.
- the processor and the storage medium may also be arranged in different components in the terminal device.
- These computer program instructions can also be loaded on a computer or other programmable data processing equipment, so that a series of operation steps are executed on the computer or other programmable equipment to produce computer-implemented processing, so as to execute on the computer or other programmable equipment.
- the instructions provide steps for implementing functions specified in a flow or multiple flows in the flowchart and/or a block or multiple blocks in the block diagram.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Databases & Information Systems (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
一种通信方法及装置,该方法包括:宿主CU建立第一IAB节点的IP地址和第一路由信息的映射关系,并将该映射关系发送给宿主DU;相应地,宿主DU从宿主CU接收第一IAB节点的IP地址和其对应的第一路由信息后,若接收到第一数据包,第一数据包的目的IP为第一IAB节点的IP地址,则可以根据映射关系,将第一数据包和第一路由信息发送给宿主DU的下一跳节点。进一步地,宿主DU还可以从宿主CU接收第一信息和BH RLC信道的映射关系,进而在发送第一数据包(第一数据包包括第一信息)时,可以将第一数据包映射到相应的BH RLC信道中来发送。
Description
相关申请的交叉引用
本申请要求在2019年04月30日提交中国专利局、申请号为201910365512.0、申请名称为“一种通信方法及装置”的中国专利申请的优先权,其全部内容通过引用结合在本申请中。
本申请涉及通信技术领域,尤其涉及一种通信方法及装置。
相较于第四代移动通信系统,第五代(5th-generation,5G)移动通信系统针对网络各项性能指标,全方位得都提出了更严苛的要求。例如,容量指标提升1000倍,更广的覆盖需求、超高可靠超低时延等。一方面,考虑到高频载波频率资源丰富,在热点区域,为满足5G超高容量需求,利用高频小站组网愈发流行。高频载波传播特性较差,受遮挡衰减严重,覆盖范围不广,故而需要大量密集部署小站,相应地,为这些大量密集部署的小站提供光纤回传的代价很高,施工难度大,因此需要经济便捷的回传方案;另一方面,从广覆盖需求的角度出发,在一些偏远地区提供网络覆盖,光纤的部署难度大,成本高,也需要设计灵活便利的接入和回传方案。
5G系统中引入了接入回传一体化(integrated access and backhaul,IAB)网络技术,IAB网络中的接入链路(access link,AL)和回传链路(backhaul link,BL)皆采用无线传输方案,避免光纤部署,从而降低部署成本,提高部署灵活性。在IAB网络中,无线回传节点可以为终端设备提供无线接入服务,该无线回传节点又可以称为IAB节点(IAB node)或中继节点(relay node,RN)。终端设备的业务数据可以由无线回传节点通过无线回传链路连接到宿主节点传输,宿主节点可以是IAB宿主(IAB donor)或者宿主基站(donor gNodeB,DgNB)。
然而,当引入IAB节点后,IAB节点如何与操作管理维护(operation administration maintenance,OAM)服务器通信仍需进一步的研究。
发明内容
有鉴于此,本申请提供了一种通信方法及装置,用以实现IAB节点与OAM服务器之间的通信。
第一方面,本申请实施例提供了一种通信方法,该方法包括:宿主DU从宿主CU接收第一接入回传一体化IAB节点的互联网协议IP地址和第一路由信息,第一路由信息用于将第一数据包路由到第一IAB节点,其中,第一数据包的目的IP地址为第一IAB节点的IP地址;进一步地,宿主DU接收第一数据包,并将第一数据包和第一路由信息发送给宿主DU的下一跳节点。
其中,第一数据包可以为OAM业务数据包或者也可以为DHCP业务数据包,相应地, 第一数据包可以是从OAM服务器接收的或者也可能是从DHCP服务器接收的。本申请实施例中将以第一数据包为OAM业务数据包为例进行描述。
针对于第一数据包为OAM业务数据包的情形,上述方法也可以描述为如下内容:
宿主DU从宿主CU接收第一接入回传一体化IAB节点的互联网协议IP地址和第一路由信息,第一路由信息用于将第一数据包路由到第一IAB节点,其中,第一数据包为OAM业务数据包,第一数据包的目的IP地址为第一IAB节点的IP地址;进一步地,宿主DU从OAM服务器接收第一数据包,并将第一数据包和第一路由信息发送给宿主DU的下一跳节点。
采用该种方式,实现了宿主DU将第一数据包发送给宿主DU的下一跳节点,进而后续可由宿主DU的下一跳节点将第一数据包发送给第一IAB节点。
在一种可能的设计中,第一路由信息包括:第一路径的标识,第一路径上的发送节点为宿主DU,第一路径上的接收节点为第一IAB节点;或者,第一IAB节点的第一标识。
在一种可能的设计中,第一IAB节点的第一标识为宿主集中式单元CU为第一IAB节点分配的适配层标识。
在一种可能的设计中,第一路由信息包括:第二路径的标识和第一IAB节点的第二标识,第二路径上的发送节点为宿主DU,第二路径上的接收节点为第一IAB节点的父节点;或者,第一IAB节点的父节点的标识和第一IAB节点的第二标识。
在一种可能的设计中,第一IAB节点的第二标识为第一IAB节点的父节点为第一IAB节点分配的小区无线网络临时标识C-RNTI,或者,第一IAB节点的第二标识为第一IAB节点的父节点为第一IAB节点分配的第一F1AP标识;或者,第一IAB节点的第二标识包括第一F1AP标识和宿主CU为第一IAB节点分配的第二F1AP标识。
在一种可能的设计中,宿主DU将第一路由信息发送给宿主DU的下一跳节点,包括:宿主DU将第一路由信息携带在宿主DU的适配层中发送给宿主DU的下一跳节点。
在一种可能的设计中,宿主DU将第一数据包发送给宿主DU的下一跳节点,包括:宿主DU从宿主CU接收第一信息和第一承载信息,第一承载信息用于指示传输第一数据包的回传无线链路控制BH RLC信道;第一数据包包括第一信息,第一信息包括以下至少一项:差分服务代码点DSCP值、流标签、OAM服务器的IP地址、端口号;宿主DU将第一数据包映射到BH RLC信道中发送给宿主DU的下一跳节点。
第二方面,本申请实施例提供了一种通信方法,该方法包括:宿主CU获取第一IAB节点的IP地址和第一路由信息,第一路由信息用于将第一数据包路由到第一IAB节点,其中,第一数据包为OAM业务数据包,第一数据包的目的IP地址为第一IAB节点的IP地址;进一步地,宿主CU向宿主DU发送第一IAB节点的IP地址和第一路由信息。
在一种可能的设计中,第一路由信息包括:第一路径的标识,第一路径上的发送节点为宿主DU,第一路径上的接收节点为第一IAB节点;或者,第一IAB节点的第一标识。
在一种可能的设计中,第一IAB节点的第一标识为宿主集中式单元CU为第一IAB节点分配的适配层标识。
在一种可能的设计中,第一路由信息包括:第二路径的标识和第一IAB节点的第二标识,第二路径上的发送节点为宿主DU,第二路径上的接收节点为第一IAB节点的父节点;或者,第一IAB节点的父节点的标识和第一IAB节点的第二标识。
在一种可能的设计中,第一IAB节点的第二标识为第一IAB节点的父节点为第一IAB节点分配的C-RNTI,或者,第一IAB节点的第二标识为第一IAB节点的父节点为第一IAB节 点分配的第一F1AP标识;或者,第一IAB节点的第二标识包括第一F1AP标识和宿主CU为第一IAB节点分配的第二F1AP标识。
在一种可能的设计中,宿主CU向宿主DU发送第一信息和第一承载信息,第一承载信息用于指示传输第一数据包的BH RLC信道,第一数据包包括第一信息,第一信息包括以下至少一项:DSCP值、流标签、OAM服务器的IP地址、端口号。
第三方面,本申请实施例提供了一种通信方法,该方法包括:宿主DU从宿主CU接收第一信息和第一承载信息,第一承载信息用于指示传输第一数据包的BH RLC信道,第一数据包包括第一信息,第一信息包括以下至少一项:DSCP值、流标签、OAM服务器的IP地址、端口号;进一步地,宿主DU从OAM服务器接收第一数据包,并将第一数据包映射到BH RLC信道中发送给宿主DU的下一跳节点。
第四方面,本申请实施例提供了一种通信方法,该方法包括:宿主CU获取第一信息和第一承载信息,第一承载信息用于指示传输第一数据包的BH RLC信道,第一数据包包括第一信息,第一信息包括以下至少一项:DSCP值、流标签、OAM服务器的IP地址、端口号;进一步地,宿主CU向宿主DU发送第一信息和第一承载信息。
第五方面,本申请实施例提供了一种通信方法,该方法包括:第一IAB节点从宿主CU接收OAM服务器的IP地址和第二路由信息,第二路由信息用于将第二数据包路由到宿主DU,第二数据包的目的IP地址为OAM服务器的IP地址;进一步地,第一IAB节点生成第二数据包,将第二数据包和第二路由信息发送给第一IAB节点的上一跳节点。
在一种可能的设计中,第二路由信息包括:第三路径的标识,第三路径上的发送节点为第一IAB节点,第三路径上的接收节点为宿主DU;或者,第四路径的标识,第四路径上的发送节点为第一IAB节点的上一跳节点,第四路径上的接收节点为宿主DU。
在一种可能的设计中,第一IAB节点将第二路由信息发送给第一IAB节点的上一跳节点,包括:第一IAB节点将第二路由信息携带在第一IAB节点的适配层中发送给第一IAB节点的上一跳节点。
在一种可能的设计中,第一IAB节点将第二数据包发送给第一IAB节点的上一跳节点,包括:第一IAB节点从宿主CU接收第二信息和第二承载信息,第二承载信息用于指示传输第二数据包的BH RLC信道,第二数据包包括第二信息,第二信息包括以下至少一项:DSCP值、流标签、OAM服务器的IP地址、端口号;进一步地,第一IAB节点将第二数据包映射到BH RLC信道中发送给第一IAB节点的上一跳节点。
第六方面,本申请实施例提供了一种通信方法,该方法包括:宿主CU获取OAM服务器的IP地址和第二路由信息,第二路由信息用于将第二数据包路由到宿主DU,第二数据包的目的IP地址为OAM服务器的IP地址;进一步地,宿主CU向第一IAB节点发送OAM服务器的IP地址和第二路由信息。
在一种可能的设计中,第二路由信息包括:第三路径的标识,第三路径上的发送节点为第一IAB节点,第三路径上的接收节点为宿主DU;或者,第四路径的标识,第四路径上的发送节点为第一IAB节点的上一跳节点,第四路径上的接收节点为宿主DU。
第七方面,本申请实施例提供了一种通信方法,该方法包括:第一IAB节点从宿主CU接收第二信息和第二承载信息,第二承载信息用于指示传输第二数据包的BH RLC信道,第二数据包包括第二信息,第二信息包括以下至少一项:DSCP值、流标签、OAM服务器的IP地址、端口号;进一步地,第一IAB节点生成第二数据包,将第二数据包映射到BH RLC 信道中发送给第一IAB节点的上一跳节点。
第八方面,本申请实施例提供了一种通信方法,该方法包括:宿主CU获取第二信息和第二承载信息,第二承载信息用于指示传输第二数据包的BH RLC信道,第二数据包包括第二信息,第二信息包括以下至少一项:DSCP值、流标签、OAM服务器的IP地址、端口号;进一步地,宿主CU向第一IAB节点发送第二信息和第二承载信息。
第九方面,本申请实施例提供了一种通信方法,该方法包括:宿主DU从宿主CU接收第一数据包和第一路由信息,第一路由信息用于将第一数据包路由到第一IAB节点,其中,第一数据包为OAM业务数据包,第一数据包的目的IP地址为第一IAB节点的IP地址;进一步地,宿主DU根据第一路由信息,将第一数据包和第一路由信息发送给宿主DU的下一跳节点。
在一种可能的设计中,第一路由信息包括:第一路径的标识,第一路径上的发送节点为宿主DU,第一路径上的接收节点为第一IAB节点;或者,第一IAB节点的第一标识。
在一种可能的设计中,第一IAB节点的第一标识为宿主集中式单元CU为第一IAB节点分配的适配层标识。
在一种可能的设计中,第一路由信息包括:第二路径的标识和第一IAB节点的第二标识,第二路径上的发送节点为宿主DU,第二路径上的接收节点为第一IAB节点的父节点;或者,第一IAB节点的父节点的标识和第一IAB节点的第二标识。
在一种可能的设计中,第一IAB节点的第二标识为第一IAB节点的父节点为第一IAB节点分配的C-RNTI,或者,第一IAB节点的第二标识为第一IAB节点的父节点为第一IAB节点分配的第一F1AP标识;或者,第一IAB节点的第二标识包括第一F1AP标识和宿主CU为第一IAB节点分配的第二F1AP标识。
在一种可能的设计中,宿主DU将第一路由信息发送给宿主DU的下一跳节点,包括:宿主DU将第一路由信息携带在宿主DU的适配层中发送给宿主DU的下一跳节点。
在一种可能的设计中,宿主DU将第一数据包发送给宿主DU的下一跳节点,包括:宿主DU从宿主CU接收第一信息和第一承载信息,第一承载信息用于指示传输第一数据包的回传无线链路控制BH RLC信道;第一数据包包括第一信息,第一信息包括以下至少一项:差分服务代码点DSCP值、流标签、OAM服务器的IP地址、端口号;进一步地,宿主DU将第一数据包映射到BH RLC信道中发送给宿主DU的下一跳节点。
第十方面,本申请实施例提供了一种通信方法,该方法包括:宿主CU从OAM服务器接收第一数据包,第一数据包为OAM业务数据包;进一步地,宿主CU向宿主DU发送第一数据包和第一路由信息,第一路由信息用于将第一数据包路由到第一IAB节点,第一数据包的目的IP地址为第一IAB节点的IP地址。
在一种可能的设计中,第一路由信息包括:第一路径的标识,第一路径上的发送节点为宿主DU,第一路径上的接收节点为第一IAB节点;或者,第一IAB节点的第一标识。
在一种可能的设计中,第一IAB节点的第一标识为宿主集中式单元CU为第一IAB节点分配的适配层标识。
在一种可能的设计中,第一路由信息包括:第二路径的标识和第一IAB节点的第二标识,第二路径上的发送节点为宿主DU,第二路径上的接收节点为第一IAB节点的父节点;或者,第一IAB节点的父节点的标识和第一IAB节点的第二标识。
在一种可能的设计中,第一IAB节点的第二标识为第一IAB节点的父节点为第一IAB节 点分配的C-RNTI,或者,第一IAB节点的第二标识为第一IAB节点的父节点为第一IAB节点分配的第一F1AP标识;或者,第一IAB节点的第二标识包括第一F1AP标识和宿主CU为第一IAB节点分配的第二F1AP标识。
在一种可能的设计中,该方法还包括:宿主CU向宿主DU发送第一信息和第一承载信息,第一承载信息用于指示传输第一数据包的BH RLC信道,第一数据包包括第一信息,第一信息包括以下至少一项:DSCP值、流标签、OAM服务器的IP地址、端口号。
第十一方面,本申请实施例提供了一种通信方法,该方法包括:接入管理功能实体获取第一IAB节点的签约信息,签约信息中包括第一IAB节点的OAM业务数据的服务质量QoS信息;进一步地,接入管理功能实体将第一IAB节点的OAM业务数据的QoS信息发送给宿主CU。
第十二方面,本申请实施例提供了一种通信方法,该方法包括:宿主CU从接入管理功能实体接收OAM业务的QoS信息,并将OAM业务的QoS信息发送给宿主DU;进一步地,宿主CU接收宿主DU返回的为OAM业务的QoS信息分配的BH RLC信道信息,BH RLC信道信息包括宿主DU和宿主DU的下一跳节点之间的BH RLC信道的标识或BH RLC信道对应的逻辑信道标识。
第十三方面,本申请实施例提供了一种通信装置。该通信装置包括处理器,处理器与存储器耦合,该存储器用于存储计算机程序或指令,该处理器运行该计算机程序或者指令,使得上述第一方面至第十二方面中的任一方面的方法被执行,该通信装置还可以包括该存储器。
第十四方面,本申请实施例提供了一种通信装置,该通信装置包括一个或者多个模块,用于实现上述第一方面至第十二方面中的任一方面的方法,该一个或者多个模块可以与上述第一方面至第十二方面中的任一方面的方法的步骤相对应。
第十五方面,本申请实施例提供了一种芯片,该芯片包括处理器和接口电路,该接口电路和该处理器耦合,该处理器用于运行计算机程序或指令,以实现如第一方面至第十二方面中任一方面的方法,该接口电路用于与该芯片之外的其它模块进行通信。
第十六方面,本申请实施例提供了一种计算机存储介质,存储有用于实现上述第一方面至第八方面中任一方面的方法的程序。当该程序在无线通信装置中运行时,使得该无线通信装置执行第一方面至第十二方面中任一方面的方法。
第十七方面,本申请实施例提供了一种计算机程序产品,该程序产品包括程序,当该程序被运行时,使得上述第一方面至第十二方面中任一方面的方法被执行。
图1为本申请实施例适用的网络架构的示意图;
图2A为包括多个IAB节点的应用场景的网络架构的一种示例;
图2B为包括多个IAB节点的应用场景的网络架构的又一种示例;
图3A为IAB节点通过宿主DU和OAM服务器进行通信示意图;
图3B为IAB节点121可以通过宿主CU和OAM服务器进行通信示意图;
图3C、图3D、图3E、图3F位本申请实施例提供的协议栈示意图;
图4为本申请实施例一提供的一种通信方法所对应的流程示意图;
图5A为本申请实施例一提供的又一种通信方法所对应的流程示意图;
图5B为建立BH RLC信道的示意图;
图6为本申请实施例一提供的又一种通信方法所对应的流程示意图;
图7为本申请实施例二提供的又一种通信方法所对应的流程示意图;
图8为本申请实施例二提供的又一种通信方法所对应的流程示意图;
图9为本申请实施例二提供的又一种通信方法所对应的流程示意图;
图10为本申请实施例中所涉及的装置的可能的示例性框图;
图11为本申请实施例中所涉及的装置的结构示意图。
下面将结合本申请实施例中的附图,对本申请实施例中的技术方案进行清楚、完整地描述。
以下,对本申请实施例中的部分用语进行解释说明,以便于本领域技术人员理解。
1)终端设备,是一种向用户提供语音和/或数据连通性的设备。在本申请实施例中,所述终端设备可以称为用户设备(user equipment,UE)、移动台(mobile station,MS)、移动终端(mobile terminal,MT)等,例如可以包括具有无线连接功能的手持式设备、或连接到无线调制解调器的处理设备。该终端可以经无线接入网(radio access network,RAN)与核心网进行通信,与RAN交换语音和/或数据。一些终端设备的举例为:个人通信业务(personal communication service,PCS)电话、无绳电话、会话发起协议(session initiation protocol,SIP)话机、无线本地环路(wireless local loop,WLL)站、个人数字助理(personal digital assistant,PDA)、条码、射频识别(radio frequency identification,RFID)、传感器、全球定位系统(global positioning system,GPS)、激光扫描器等信息传感设备等设备。
终端设备还可以可穿戴设备。可穿戴设备也可以称为穿戴式智能设备,是应用穿戴式技术对日常穿戴进行智能化设计、开发出可以穿戴的设备的总称,如眼镜、手套、手表、服饰及鞋等。可穿戴设备即直接穿在身上,或是整合到用户的衣服或配件的一种便携式设备。可穿戴设备不仅仅是一种硬件设备,更是通过软件支持以及数据交互、云端交互来实现强大的功能。广义穿戴式智能设备包括功能全、尺寸大、可不依赖智能手机实现完整或者部分的功能,例如:智能手表或智能眼镜等,以及只专注于某一类应用功能,需要和其它设备如智能手机配合使用,如各类进行体征监测的智能手环、智能头盔、智能首饰等。该终端还可以是虚拟现实(virtual reality,VR)设备、增强现实(augmented reality,AR)设备、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程手术(remote medical surgery)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端等。
所述终端设备的功能可以通过终端设备内部的硬件部件来实现,所述硬件部件可以为所述终端设备内部的处理器和/或可编程的芯片。可选的,该芯片可以通过专用集成电路(application-specific integrated circuit,ASIC)实现,或可编程逻辑器件(programmable logic device,PLD)实现。上述PLD可以是复杂程序逻辑器件(complex programmable logical device,CPLD),现场可编程门阵列(field-programmable gate array,FPGA),通用阵列逻辑(generic array logic,GAL),片上系统(system on a chip,SOC)中的任一项或其任意组合。
2)宿主基站(Donor next generation node B,DgNB)可以是IAB宿主(IAB donor),是通信系统中将终端设备接入到无线网络的设备,宿主基站通过有线链路连接到核心网。作为一种示例,宿主基站可以包括无线网络控制器(radio network controller,RNC)、节点B(Node B,NB)、基站控制器(base station controller,BSC)、基站收发台(base transceiver station,BTS)、家庭基站(例如,home evolved NodeB,或home Node B,HNB)、基带单元(base band unit,BBU)等,也可以包括演进的长期演进(advanced long term evolution,LTE-A)中的演进型基站(NodeB或eNB或e-NodeB,evolutional Node B),或者也可以包括5G系统(也可以称为新无线(new radio,NR)系统)中的下一代节点B(next generation node B,gNB)等。作为另一种示例,宿主基站可以包括集中单元(centralized unit,CU)和分布单元(distributed unit,DU)。这种结构将长期演进(long term evolution,LTE)系统中eNB或NR系统中的gNB的协议层拆分开,部分协议层(例如分组数据汇聚层协议(packet data convergence protocol,PDCP)层和无线资源控制(radio resource control,RRC)层)的功能放在CU集中控制,剩下部分或全部协议层(例如物理(physical,PHY)层,媒体访问控制(media access control,MAC)层,无线链路控制(radio link control,RLC)层)的功能分布在DU中,由CU控制DU。本申请实施例中,为便于描述,可以将宿主基站的CU称为宿主CU,将宿主基站的DU称为宿主DU。
该宿主基站的功能可以是由宿主基站内部的硬件部件实现,例如宿主基站内部的处理器和/或可编程的芯片。例如,该芯片可以通过ASIC实现,或PLD实现。上述PLD可以是CPLD、FPGA、GAL、SOC中任一项或其任意组合。
3)无线回传设备,可以通过接入链路为终端设备提供无线接入服务,无线回传设备通过一跳或者多跳回传链路连接到宿主基站传输终端设备的业务数据,通过对业务数据的重新发送或者转发,来扩大移动通信系统的覆盖范围。作为一种示例,无线回传设备可以IAB节点、中继站、接收点(transmission reception point,TRP)或传输点(transmission point,TP)等。
作为一种示例,无线回传设备可以包括移动终端(mobile-termination,MT)单元和DU。通过MT单元与父节点(也就是无线回传设备的上一跳)进行通信,通过DU与子节点(也就是无线回传设备的下一跳)进行通信。示例性地,无线回传设备可以包括至少一个MT单元,例如,无线回传设备可以仅包括一个MT单元,该MT单元是具有多连接能力的MT单元,该无线回传设备可以通过该MT单元与该无线回传设备的多个父节点之间建立回传连接;又例如,无线回传节点可以包括多个MT单元,该多个MT单元中的每个MT单元与该无线回传设备的一个父节点建立连接,作为该无线回传设备的一条独立回传链路。
该无线回传设备的功能可以是由无线回传设备内部的硬件部件实现,例如,所述无线回传设备内部的处理器和/或可编程的芯片。例如,该芯片可以通过ASIC实现,或PLD实现。上述PLD可以是CPLD、FPGA、GAL、SOC中任一项或其任意组合。
需要说明的是,无线回传设备在不同的通信系统中可以有不同的名称,例如,在LTE系统、LTE-A系统中,该无线回传设备可以称为中继节点(relay node,RN);在5G系统中,该无线回传设备可以称为IAB节点(IAB node)。当然,在其他通信系统中,无线回传设备还可以有不同的名称,在此不作限制。
4)链路:是指一条路径中的两个相邻节点之间的路径。
5)接入链路:终端设备与基站之间,或者终端设备与IAB节点之间,或者终端设备与宿主节点之间,或者终端设备与宿主DU之间的链路。或者,接入链路包括某个IAB节点作为普通终端设备角色时和它的父节点进行通信时所使用的无线链路。IAB节点作为普通终端设备角色时,不为任何子节点提供回传服务。接入链路包括上行接入链路和下行接入链路。本申请实施例中,由于终端设备的接入链路为无线链路,故接入链路也可被称为无线接入链路。
6)回传链路:IAB节点作为无线回传节点时与父节点之间的链路。IAB节点作为无线回传节点时,为子节点提供无线回传服务。回传链路包括上行回传链路,以及下行回传链路。本申请实施例中,由于IAB节点与父节点之间的回传链路为无线链路,故回传链路也可被称为无线回传链路。
7)父节点与子节点:每个IAB节点将为其提供无线接入服务和/或无线回传服务的相邻节点视为父节点(parent node)。相应地,每个IAB节点可视为其父节点的子节点(child node)。可替换地,子节点也可以称为下级节点,父节点也可以称为上级节点。
8)节点的上一跳节点:是指在包含该节点的路径中的、在该节点之前最后一个接收到数据包的节点。可以理解为,节点的上一跳节点可以包括上行传输中该节点的上一跳节点,和下行传输中该节点的上一跳节点。
9)节点的下一跳节点:是指在包含该节点的路径中的、在该节点之后第一个接收到数据包的节点。可以理解为,节点的下一跳节点可以包括上行传输中该节点的下一跳节点,和下行传输中该节点的下一跳节点。
需要说明的是:本申请实施例中,对于上行方向,上一跳节点指的是父节点,下一跳节点指的是子节点。对下行方向,下一跳节点指的是子节点,上一跳节点是的是父节点。
10)本申请实施例中“多个”是指两个或两个以上,鉴于此,本申请实施例中也可以将“多个”理解为“至少两个”。“至少一个”,可理解为一个或多个,例如理解为一个、两个或更多个。例如,包括至少一个,是指包括一个、两个或更多个,而且不限制包括的是哪几个,例如,包括A、B和C中的至少一个,那么包括的可以是A、B、C、A和B、A和C、B和C、或A和B和C。“和/或”,描述关联对象的关联关系,表示可以存在三种关系,例如,A和/或B,可以表示:单独存在A,同时存在A和B,单独存在B这三种情况。另外,字符“/”,如无特殊说明,一般表示前后关联对象是一种“或”的关系。本申请实施例中的术语“系统”和“网络”可被互换使用。除非有相反的说明,本申请实施例提及“第一”、“第二”等序数词用于对多个对象进行区分,不用于限定多个对象的顺序、时序、优先级或者重要程度。
本申请实施例适用的通信系统包括但不限于:窄带物联网(narrow band-internet of things,NB-IoT)系统、无线局域网(wireless local access network,WLAN)系统、LTE系统、5G系统或者5G之后的通信系统,如NR、设备到设备(device to device,D2D)通信系统。
下文中将以无线回传设备为IAB节点,宿主基站为IAB donor为例进行描述,其中,IAB节点是在IAB网络中对中继节点的特定称呼,不对本申请实施例的方案构成限定。本申请实施例中用IAB节点仅仅出于描述的需要,并不表示本申请实施例的方案仅用于NR的场景,在本申请实施例中,IAB节点可以泛指任何具有中继功能的节点或设备,示例性 地,IAB节点可以是一种具有转发功能的上述基站或者终端设备中的任意一种,也可以是一种独立的设备形态,本申请实施例对此不作限定。
图1为本申请实施例适用的网络架构的示意图。如图1所示,该网络架构中包括终端设备110、IAB节点120以及宿主基站130。在图1所示的网络架构中,终端设备110通过无线的方式与IAB节点120相连,IAB节点120通过无线的方式与宿主基站130相连。终端设备110与IAB节点120之间以及IAB节点120与宿主基站130之间均可以通过授权频谱(licensed spectrum)进行通信,也可以通过非授权频谱(unlicensed spectrum)进行通信,也可以同时通过授权频谱和非授权频谱进行通信,例如,该授权频谱可以为6GHz以下的频谱,在此不作限制。在图1所示的网络架构中,IAB节点将为其提供回传服务的节点视为唯一的父节点,例如,IAB节点120将宿主基站130视为父节点。当IAB节点120在某个数据无线承载(data radio bearer,DRB)上接收终端设备110的上行数据,将该上行数据映射到对应的BH RLC channel上传输至宿主基站后,再由宿主基站将该上行数据发送至移动网关设备(例如5G系统中的用户面功能(user port function,UPF)实体)。类似的,下行方向上,移动网关设备将下行数据发送至宿主基站,然后依次经由IAB节点120发送至终端设备110。
需要说明的是,在如图1所示的网络架构图中,尽管示出了终端设备、IAB节点及宿主基站,但该网络架构可以并不限于包括终端设备、IAB节点及宿主基站。例如,还可以包括核心网设备或用于承载虚拟化网络功能的设备等,这些对于本领域普通技术人员而言是显而易见的,在此不一一详述。另外,如图1所示的网络架构图中,尽管示出了一个终端设备、一个IAB节点及一个宿主基站,但该网络架构并不限制终端设备、IAB节点及宿主基站的数量,例如,也可以包括多个终端设备、多个IAB节点及多个宿主基站等。另外,需要说明的是,在如图1所示的应用场景中,仅包括一个IAB节点。在本申请实施例中不对IAB节点的数量及部署位置进行限制。
基于图1所示意的网络架构,图2A和图2B给出了两种应用场景示例。
参见图2A,为包括多个IAB节点的应用场景的网络架构的一种示例。图2A所示的网络架构可以理解为多跳无线回传场景。在图2A中,该网络架构中包括两个IAB节点以及两个终端设备,两个IAB节点分别为IAB节点120和IAB节点121,两个终端设备分别为终端设备110和终端设备111。终端设备110和终端设备111分别通过无线的方式与IAB节点121相连,IAB节点121通过无线的方式与IAB节点120相连,IAB节点120通过无线的方式与宿主基站130相连。在图2A所示的网络架构中,IAB节点121将为其提供回传服务的IAB节点120视为父节点,IAB节点120将宿主基站130视为父节点。当IAB节点121接收终端设备110和终端设备111的上行数据后,将依次经由IAB节点121和IAB节点120,然后传输至宿主基站后,再由宿主基站将该上行数据发送至移动网关设备。类似的,下行方向上,移动网关设备将终端设备的下行数据发送至宿主基站,然后依次经由IAB节点120和IAB节点121,发送至终端设备110和终端设备111。
参见图2B,为包括多个IAB节点的应用场景的网络架构的又一种示例。与图2A不同的是,在图2B所示的网络架构中包括三个IAB节点和一个终端设备,三个IAB节点分别为IAB节点120~IAB节点122,IAB节点120~IAB节点122与宿主基站130之间形成两条路由路径,一条路由路径由IAB节点121、IAB节点122和宿主基站130组成,另一条路由路径由IAB节点121、IAB节点120和宿主基站130组成。终端设备可以通过这两条路 由路径与宿主基站130进行通信。图2B所示的网络架构可以理解为多跳+多连接无线回传场景。
本申请实施例中,图1、图2A和图2B所示意的网络架构中还可以包括OAM服务器140。作为一种示例,宿主基站130可以和OAM服务器140进行通信,比如通过有线的方式进行通信。在引入IAB节点后,IAB节点也需要与OAM服务器进行通信,比如,IAB节点从OAM服务器获取可接入的小区列表信息,用于IAB节点的初始接入;又比如,IAB节点从OAM服务器获取IAB节点的DU相关的配置信息,例如DU的标识、DU小区的标识等,用于启动DU模块;又比如,IAB节点启动DU模块后,IAB节点可以向OAM服务器发送一些信息,例如业务计数信息(traffic counters)和警报信息(alarms),或者,IAB节点也可以从OAM服务器获取一些信息,例如软件升级配置等。本申请实施例将主要研究IAB节点与OAM服务器之间的通信。
示例性地,本申请实施例中所涉及的IAB节点可以理解为已经完成初始接入的IAB节点,而具体如何完成初始接入,本申请实施例不做限定。基于此,本申请实施例中所涉及的IAB节点与OAM服务器之间的通信,以传输操作维护(operation and maintenance,OM)的配置数据、告警数据、话统数据、日志数据或者跟踪数据等等,例如可以是为了获取DU相关的配置信息,或者IAB节点向OAM服务发送业务计数信息和警报信息,或者,IAB节点接收OAM服务发送的软件升级配置等。当然,也不排除IAB节点完成初始接入后,仍从OAM服务器获取可接入的小区列表信息的可能性,比如本申请实施例中的IAB节点也可以从OAM服务器获取可接入的小区列表信息,以验证其当前接入的小区是否合法。
针对于宿主基站和OAM服务器之间的通信,当宿主基站包括CU和DU时,在一个示例中,OAM业务数据包通过宿主DU进行路由。这意味着,OAM业务数据包的传输不需要通过宿主CU以及IAB节点的核心网,即:宿主DU可以直接从OAM服务器接收OAM业务数据包(也可以通过1个或多个路由器接收从OAM服务发送的OAM业务数据包,其中,宿主DU和OAM服务器之间的路径上可以存在1个或者多个路由器),或者将收到的OAM业务数据包直接路由到OAM服务器(也可以通过1个或多个路由器转发后路由到OAM服务器,其中,宿主DU和OAM服务器之间的路径上可以存在1个或者多个路由器)。此种情形下,以图2A所示意的应用场景为例,参见图3A,IAB节点121可以通过宿主DU和OAM服务器进行通信,其中,宿主DU和OAM服务器之间直接有线相连。
在又一个示例中,宿主DU和OAM服务器交互的OAM业务数据包可以由宿主CU进行路由。这意味着,OAM业务数据包的传输不需要经过IAB节点的核心网。作为一种可能方案,OAM服务器仅能获知宿主CU的IP地址,而宿主DU仅能获知宿主CU的IP地址,宿主CU可以获知OAM服务器的IP地址。宿主CU从宿主DU接收到IAB节点发送的OAM业务数据包1后,可以将OAM业务数据包1转发给OAM服务器,或者,宿主CU从OAM服务器收到OAM业务数据包2后,通过解析OAM业务数据包2获知该数据包是发送给自己的还是IAB节点DU的,如果是发送给IAB节点DU的,则可以进一步通过宿主DU转发给对应的IAB节点DU。在该示例中,宿主CU和宿主DU可以连接到统一的OAM服务器(其中,宿主DU可以是通过宿主CU连接到OAM服务器),即由同一个OAM服务器来管理宿主CU和宿主DU。此种情形下,仍以图2A所示意的应用场景 为例,参见图3B,IAB节点121可以通过宿主CU和OAM服务器进行通信,其中,宿主CU和OAM服务器之间直接有线相连。当然,宿主CU和OAM服务器之间的路径上也可以存在一个或多个路由器,本申请实施例对此不做限制。
也就是说,本申请实施例中,IAB节点与OAM服务器进行通信可以包括:IAB节点通过宿主DU和OAM服务器进行通信,或者,IAB节点通过宿主CU和OAM服务器进行通信。下面结合具体实施例分别对这两种情形进行详细描述。
需要说明的是,若IAB节点与宿主DU之间不存在其它IAB节点,比如IAB节点为图2A中所示意的IAB节点120,此种情形下,宿主DU可以直接和IAB节点进行通信。下文所描述的实施例中主要是以IAB节点与宿主DU之间存在一个或多个其它IAB节点的情形下为例。
实施例一
在实施例一中,将主要针对第一IAB节点通过宿主DU和OAM服务器进行通信(比如图3A所示意的情形)的实现进行描述。以图3A中所示意的情形为例,假设第一IAB节点为图3A中的IAB节点121,此种情形下,第一IAB节点和OAM服务器进行通信的协议栈可以如图3C所示。需要说明的是,图3C(或者后文中的图3D、图3E、图3F)中的TCP是指传输控制协议(transmission control protocol),UDP是指用户数据报协议(user datagram protocol),Adapt是指适配层。
在该实施例中,若宿主DU上部署有动态主机设置协议(dynamic host configuration protocol,DHCP)服务器,则第一IAB节点的IP地址可以理解为是由宿主DU分配的。在又一个示例中,若宿主DU上未部署DHCP服务器(此种情形下,DHCP服务器可以部署在OAM服务器上),则第一IAB节点的IP地址可以由DHCP服务器分配,并通过宿主DU转发给第一IAB节点,此时,宿主DU可以理解为DHCP代理(proxy)。
第一IAB节点通过宿主DU和OAM服务器进行通信可以包括下行通信(比如:第一IAB节点←……←宿主DU←OAM服务器)和上行通信(比如:第一IAB节点→……→宿主DU→OAM服务器)。
(1)下行通信
针对于下行通信,以宿主DU直接有线连接到OAM服务器为例进行说明,宿主DU可以直接从OAM服务器接收第一数据包(第一数据包为第一IAB节点的DU的数据包)。该部分内容将主要研究宿主DU如何将第一数据包发送给第一IAB节点的DU,示例性,将提供两种可能的方案,分别为方案一和方案二。
方案一
图4为本申请实施例一提供的一种通信方法所对应的流程示意图,如图4所示,该方法包括:
步骤401,宿主CU获取第一IAB节点的IP地址,示例性地,此处所描述的第一IAB节点的IP地址可以理解为第一IAB节点的DU的IP地址。第一IAB节点的DU的IP地址可以由宿主DU分配的,或者,由DHCP服务器分配后通过宿主DU发送给第一IAB节点的DU。
本申请实施例中,宿主CU可以通过多种方式获取第一IAB节点的DU的IP地址。在一种可能的实现方式中,宿主CU可以从宿主DU获取第一IAB节点的DU的IP地址,比 如宿主DU为第一IAB节点的DU分配IP地址后,可以将第一IAB节点的DU的IP地址和第一IAB节点的信息发送给宿主CU,其中,第一IAB节点的信息可以由第一IAB节点接入的小区标识以及该接入小区为第一IAB节点分配的小区无线网络临时标识(cell radio network temporary identifier,C-RNTI)组成;相应地,宿主CU可以得到第一IAB节点的DU的IP地址。
在另一种可能的实现方式中,宿主CU可以从第一IAB节点的MT获取第一IAB节点的DU的IP地址,比如第一IAB节点的DU从宿主DU获取分配的IP地址后,可以由第一IAB节点的MT通过RRC消息将第一IAB节点的DU的IP地址发送给宿主CU;相应地,宿主CU可以得到第一IAB节点的DU的IP地址。
步骤402,宿主CU确定第一IAB节点的DU的IP地址对应的第一路由信息,并向宿主DU发送第一IAB节点的DU的IP地址对应的第一路由信息。其中,第一路由信息用于将第一数据包路由到第一IAB节点,第一数据包的目的IP地址为第一IAB节点的DU的IP地址。
可选的,第一数据包可以是OAM服务器发送给第一IAB节点的数据包,第一不起限定作用。
可选的,宿主CU可以向宿主DU发送第一IAB节点的DU的IP地址和该IP地址对应的第一路由信息。
步骤403,宿主DU从宿主CU接收第一IAB节点的DU的IP地址对应的第一路由信息。
可选的,宿主DU可以从宿主CU接收第一IAB节点的DU的IP地址和该IP地址对应的第一路由信息。
在一个示例中,第一路由信息可以包括第一路径的标识或者第一IAB节点的第一标识。其中,第一路径用于指示宿主DU到第一IAB节点的路径,也就是说,第一路径上的发送节点为宿主DU,第一路径上的接收节点为第一IAB节点。第一IAB节点的第一标识可以为宿主CU为第一IAB节点分配的用于识别第一IAB节点的标识,比如宿主CU为第一IAB节点分配的适配层标识,比如回传适配层协议(backhaul adaptation protocol)标识(identification,ID)。
在该示例中,若宿主DU到第一IAB节点的路径有多条(比如参见图2B所示,若第一IAB节点为IAB节点121,则宿主DU到IAB节点121有两条路径),则当第一路由信息中包括第一路径的标识时,可以理解为是由宿主CU为数据包选择路径;举个例子,第一IAB节点为图2B中的IAB节点121,此时第一路由信息可以包括路径1a(由IAB节点121、IAB节点122和宿主基站130组成)的标识或者路径1b(由IAB节点121、IAB节点120和宿主基站130组成);当第一路由信息可以包括路径1a时,说明宿主CU为数据包选择的路径为路径1a,当第一路由信息可以包括路径1b时,说明宿主CU为数据包选择的路径为路径1b。当第一路由信息中包括第一IAB节点的第一标识时,可以理解为宿主DU根据第一IAB节点的第一标识,查自己维护的路由表信息来获知发送数据包的下一跳节点的信息。
在又一个示例中,第一路由信息可以包括第二路径的标识和第一IAB节点的第二标识,或者,第一IAB节点的父节点的标识和第一IAB节点的第二标识。其中,第二路径用于指示宿主DU到第一IAB节点的父节点的路径,也就是说,第二路径上的发送节点为宿主DU,第二路径上的接收节点为第一IAB节点的父节点。第一IAB节点的父节点的标识可以第一 IAB节点的父节点的小区标识或者第一IAB节点的父节点的DU的标识。第一IAB节点的第二标识可以为以下至少一项:第一IAB节点的父节点为第一IAB节点分配的C-RNTI;第一IAB节点的父节点为第一IAB节点分配的第一F1应用协议(F1application protocol,F1AP)标识;宿主CU为第一IAB节点分配的第二F1AP标识。
本申请实施例中,宿主CU获取到第一IAB节点的DU的IP地址后,可以建立第一IAB节点的DU的IP地址和第一路由信息之间的映射关系(或者称为对应关系),可选地,该映射关系中还可以包括OAM服务器的IP地址,OAM服务器的IP地址可以为宿主CU预先获取的,也可以为宿主DU通知宿主CU的。
参见表1所示,为第一IAB节点的DU的IP地址和第一路由信息之间的映射关系的几种可能的情形示例。具体实施中,第一IAB节点的DU的IP地址和第一路由信息之间的映射关系可以为表1所示意的多种可能的情形中的一种。
表1:映射关系示例1
表1中,每一行代表映射关系的一种可能的情形。比如,表1中第一行的含义为:若待传输数据包的目的IP地址为第一IAB节点的DU的IP地址,则对应的路由信息包括第一路径的标识;又比如,表1中第五行的含义为:若待传输数据包的目的IP地址为第一IAB节点的DU的IP地址,源IP地址为OAM服务器的IP地址,则对应的路由信息包括第一路径的标识。其它行的含义可参照第一行和第五行,具体不再赘述。此外,表1中的目标节点也可以称为目的节点,具体不做限定。
进一步地,宿主CU可以向宿主DU发送第一IAB节点的DU的IP地址对应的第一路由信息(比如可以理解为宿主CU将确定的映射关系通知给宿主DU),具体的实现方式可以有多种。在一种可能的实现方式中,以映射关系为表1中的第一行为例,宿主CU可以向宿主DU发送F1AP信令,F1AP信令中包括参数列表,参数列表中可以包括一项或多项信息,每一项信息中包括两个参数;以其中的一项信息包括的两个参数为参数1和参数2为例,该项信息中的参数1可以包括第一IAB节点的DU的IP地址,参数2可以包括第一路由信息。相应地,宿主DU接收到F1AP信令后,可以获知第一IAB节点的DU的IP地址对应第一路由信息,并存储该映射关系。本申请实施例中,参数1和参数2可以位于不 同的信息元素(information element,IE)中,比如,参数1位于IE1中,参数2位于IE2中,具体不做限定。
需要说明的是,上述仅是宿主CU向宿主DU发送一条映射关系为例进行描述的;在其它可能的实施例中,宿主CU可以向宿主DU发送多条映射关系(多个IAB节点的DU的IP地址对应的多个路由信息),比如宿主CU向宿主DU发送F1AP信令,F1AP信令中包括多个IAB节点的DU的IP地址和多个路由信息,多个IAB节点的DU的IP地址和多个路由信息一一对应。
步骤404,OAM服务器生成第一数据包,并向宿主DU发送第一数据包。
此处,OAM服务器获取到第一IAB节点的DU的IP地址后,若确定需要向第一IAB节点的DU发送OAM数据,则可以生成第一数据包,第一数据包的目的IP地址为第一IAB节点的DU的IP地址,源IP地址为OAM服务器的IP地址。其中,OAM服务器获取第一IAB节点的DU的IP地址的方式可以有多种,在一种可能的实现方式中,第一IAB节点的DU获取到宿主DU为其分配的IP地址后,可以向OAM服务器发送上行信息,如此,OAM服务器可以获取到第一IAB节点的DU的IP地址。在另一种可能的实现方式中,OAM服务器上直接部署DHCP服务器,因此,OAM服务器直接为第一IAB节点的DU分配IP地址。
步骤405,宿主DU从OAM服务器接收第一数据包,并将第一数据包和第一路由信息发送给宿主DU的下一跳节点。
示例性地,宿主DU可以将第一路由信息携带在宿主DU的适配层中发送给宿主DU的下一跳节点。
此处,宿主DU接收到第一数据包后,可以解析第一数据包的IP层,得到第一数据包的目的IP地址(可选地,还可以得到源IP地址);进而宿主DU可以根据步骤403中接收到的映射关系,得到目的IP地址对应的第一路由信息。
举个例子,第一IAB节点为图2A中所示意的IAB节点121,IAB节点121的DU的IP地址对应的第一路由信息包括第一路径的标识,第一路径为:宿主DU→IAB节点120→IAB节点121。宿主DU根据第一路径可知下一跳节点为IAB节点120,进而宿主DU可以将第一数据包和第一路由信息发送给IAB节点120。
再举个例子,第一IAB节点为图2A中所示意的IAB节点121,IAB节点121的DU的IP地址对应的第一路由信息包括IAB节点121的适配层标识(比如动态带宽分配协议(bandwidth allocation protocol,BAP)ID)。宿主DU根据IAB节点121的适配层标识,查路由表可获知发送第一数据包的下一跳节点为IAB节点120(在其它示例中,也有可能确定下一跳节点为IAB节点122,本申请实施例对此不做限定),进而宿主DU可以将第一数据包和第一路由信息发送给IAB节点120。
宿主DU在得到目的IP地址对应的第一路由信息后,可以获知第一数据包的下一跳节点,将第一数据包发送给该下一跳节点。
后续,可由宿主DU的下一跳节点(比如IAB节点120)将第一数据包发送给IAB节点121,从而实现了IAB节点121和OAM服务器之间的通信。
上述步骤401至步骤405主要描述了宿主DU将第一数据包发送给宿主DU的下一跳节点的实现过程,而针对于第一IAB节点和宿主DU之间的节点来说,其可以直接根据第一路由信息来传输第一数据包。比如第一IAB节点和宿主DU之间包括IAB节点a和IAB 节点b,其中IAB节点b为宿主DU的下一跳节点,针对于IAB节点a和IAB节点b来说,IAB节点b从宿主DU接收到第一数据包和第一路由信息后,可以根据第一路由信息确定下一跳节点为IAB节点a,并将第一数据包和第一路由信息发送给IAB节点a;IAB节点a从IAB节点b接收到第一数据包和第一路由信息后,根据第一路由信息确定下一跳节点为第一IAB节点且第一IAB节点为第一数据包的目的节点,进而可将第一数据包发送给第一IAB节点。
需要说明的是,上述图4中主要是以宿主CU确定第一路由信息并发送给宿主DU为例进行描述的。在其它可能的实施例中,也可以由宿主DU确定第一路由信息,如此则可以不再执行步骤401至步骤403;相应地,在步骤405中,宿主DU接收到第一数据包后,可以根据第一数据包的目的IP地址,确定第一路由信息(比如可以根据目的IP地址确定对应的IAB节点为第一IAB节点,然后再根据第一IAB节点的第一标识查询预先存储的路由表来确定第一路由信息),并将第一数据包和第一路由信息发送给宿主DU的下一跳节点,具体的,第一IAB节点通过父节点向宿主DU发送DHCP discover消息,如果宿主DU上部署了DHCP服务器,则宿主DU直接处理DHCP discover消息,否则,宿主DU将收到的DHCP discover消息进一步转发给DHCP服务器。第一IAB节点发送DHCP discover消息的过程中,又可以存在两种方式:
方式1:第一IAB节点MT向父节点发送DHCP discover消息时,由第一IAB节点MT在其适配层中携带第一IAB节点的标识(如:宿主CU为该第一IAB节点分配的适配层标识)或者第一IAB节点的标识(如:父节点DU小区为其分配的C-RNTI)和第一IAB节点的父节点的标识(如:第一IAB节点接入父节点的小区标识)。父节点将从其DU的适配层中收到的该信息进一步携带在其MT的适配层中发送给宿主DU。
方式2:第一IAB节点MT向父节点发送DHCP discover消息,然后父节点向宿主DU转发DHCP discover消息时,由父节点的MT在其适配层中携带第一IAB节点的标识(如:父节点DU为第一IAB节点分配的C-RNTI)和该父节点的标识(如:第一IAB节点接入父节点的小区标识)发送给宿主DU。
宿主DU将第一IAB节点DU的IP地址和从其适配层中收到的信息进行绑定,即:第一IAB节点DU的IP地址与第一IAB节点的标识(如:宿主CU为该第一IAB节点分配的适配层标识)具有对应关系,或者,第一IAB节点DU的IP地址与第一IAB节点的标识(如:父节点DU小区为其分配的C-RNTI)和第一IAB节点的父节点的标识(如:第一IAB节点接入父节点的小区标识)具有对应关系。
之后,宿主DU收到第一数据包后,提取出IP包中携带的目标IP地址,如果该目标IP地址是第一IAB节点的DU的IP地址,则宿主DU根据之前绑定的对应关系,确定第一数据包的路由,将对应的第一IAB节点的标识(如:宿主CU为该第一IAB节点分配的适配层标识)或者第一IAB节点的标识(如:父节点DU小区为其分配的C-RNTI)和第一IAB节点的父节点的标识(如:第一IAB节点接入父节点的小区标识)携带在其适配层中和第一数据包一起发送给宿主DU的下一跳节点。
该方式下,宿主CU不进行路由决策,所以无需获知第一IAB节点DU分配的IP地址,也无需给宿主DU发送第一IAB节点DU的IP地址和第一路由信息的对应关系。而由宿主DU根据之前DHCP流程中绑定的对应关系直接进行路由。
另外,需要说明的是,步骤404和步骤405是可选的。
方案一中的路由方案,同样适用于DHCP discover/off/request/Ack消息的传输,即第一数据包可以为DHCP discover/off/request/Ack消息。
方案二
图5A为本申请实施例一提供的又一种通信方法所对应的流程示意图,如图5A所示,该方法包括:
步骤501,宿主CU获取第一信息。
步骤502,宿主CU向宿主DU发送第一信息对应的第一承载信息。
所述第一承载信息用于指示承载第一数据包的BH RLC信道,第一数据包包括第一信息。示例性地,第一承载信息可以为BH RLC信道的标识或者BH RLC信道对应的逻辑信道的标识(logical channel ID,LCID)。
步骤503,宿主DU从宿主CU接收第一信息对应的第一承载信息。
下面对传输OAM业务的BH RLC信道进行介绍:在一个示例中,传输OAM业务的BH RLC信道可以为协议预定义的一个特有的BH RLC信道。比如,协议预定义逻辑信道1对应的BH RLC信道用于传输OAM业务数据包。又或者,传输OAM业务的BH RLC信道可以是默认的BH RLC信道。比如,第一IAB节点初始接入时建立的默认BH RLC信道。
在又一个示例中,传输OAM业务的BH RLC信道可以为宿主CU触发建立的,比如宿主CU可以获取第一IAB节点的OAM业务的QoS信息,进而触发宿主DU以及相关IAB节点的DU建立传输OAM业务的BH RLC信道。其中,宿主CU获取第一IAB节点的OAM业务的QoS信息的实现方式可以有多种,本申请实施例提供一种可能的方式参见图5B所示,包括:
步骤a,第一IAB节点进行初始接入。
步骤b,在第一IAB节点在初始接入过程中,接入管理功能实体获取第一IAB节点的签约信息,签约信息中包括OAM业务的QoS信息。比如,接入管理功能实体可以从归属签约用户服务器(home subscriber server,HSS)或统一数据管理(unified data management,UDM)获取第一IAB节点的签约信息。其中,接入管理功能实体可以为接入和移动管理功能(access and mobility management function,AMF)实体。
步骤c,接入管理功能实体向宿主CU发送OAM业务的QoS信息。
比如,接入管理功能实体可以通过初始上下文建立请求(initial context setup request)向宿主CU发送OAM业务的QoS信息。
步骤d,宿主CU接收OAM业务的QoS信息,并向宿主DU发送OAM业务的QoS信息。
比如,宿主CU可以通过上下文建立请求(context setup request)向宿主DU发送OAM业务的QoS信息。
步骤e,宿主DU接收到OAM业务的QoS信息,为OAM业务分配对应的BH RLC信道,并向宿主CU返回分配的BH RLC信道的标识。例如:BH RLC信道2的标识,其中,BH RLC信道2为宿主DU和宿主DU的下一跳节点之间用于传输OAM业务数据包的RLC信道。比如,宿主DU可以通过上下文建立响应(context setup response)向宿主CU返回BH RLC信道2的标识。
此外,宿主CU还可以触发相关IAB节点的DU建立对应的BH RLC信道,类似于触 发宿主DU建立BH RLC信道的流程,不再赘述。
需要说明的是,图5B中所涉及的这些步骤或操作仅是示例,本申请实施例还可以执行其它操作或者各种操作的变形,具体实施中,可以执行这些步骤中的部分或全部,本申请实施例对此不做限定。图5B所描述的触发建立BH RLC信道的方法可以单独实施,或者也可以结合到方案二中来实施,具体不做限定。
本申请实施例中,第一信息可以用于指示包括该第一信息的数据包为OAM业务数据包。比如,第一信息可以包括以下至少一项:差分服务代码点(differentiated services code point,DSCP)值;流标识(flow label);OAM服务器的IP地址;端口号。其中,对于DSCP值或流标识来说,可以通过协议预先定义OAM业务对应的DSCP值或流标识,或者,也可以由宿主CU和OAM服务器协商后确定OAM业务对应的DSCP值或流标识。示例性地,对于IPv4,可以使用数据包的IP头字段中携带的DSCP值来标识该数据包为OAM业务数据包;对于IPv6,可以使用数据包的IP头字段中携带的DSCP值或者流标识来标识该数据包为OAM业务数据包。对于OAM服务器的IP地址来说,若数据包的源IP地址为OAM服务器的IP地址,则说明该数据包为OAM业务数据包。对于端口号来说,可以通过协议预先定义OAM业务对应的端口号,或者,也可以由宿主CU和OAM服务器协商后确定OAM业务对应的端口号,如此,可以使用数据包的端口号(源端口号和/或目的端口号)来标识该数据包为OAM业务数据包。
需要说明的是,上述仅示例性列出了第一信息可能包括的信息,在其它实施例中,第一信息还可以包括其它可能的信息,只要是携带在数据包中并能够标识数据包为OAM业务数据包的信息均可,具体不做限定。作为另一种可能,宿主CU给宿主DU发送OAM业务数据包对应的第一承载信息,至于宿主DU如何识别收到的数据包是OAM业务数据包可以不限定,留给实现。
在该示例中,宿主CU获取第一信息后,可以建立第一信息和第一承载信息之间的映射关系。
参见表2所示,为第一信息和第一承载信息之间的映射关系的几种可能的情形示例。
表2:映射关系示例2
DSCP值 | BH RLC信道的标识 |
流标识 | BH RLC信道的标识 |
OAM服务器的IP地址 | BH RLC信道的标识 |
端口号 | BH RLC信道的标识 |
DSCP值 | BH RLC信道对应的逻辑信道的标识 |
流标识 | BH RLC信道对应的逻辑信道的标识 |
OAM服务器的IP地址 | BH RLC信道对应的逻辑信道的标识 |
端口号 | BH RLC信道对应的逻辑信道的标识 |
表2中,每一行代表一种可能的映射关系。比如,表2中第一行的含义为:若待传输数据包包括DSCP值,则对应的承载信息为BH RLC信道的标识;又比如,表2中第三行的含义为:若待传输数据包的源IP地址为OAM服务器的IP地址,则对应的承载信息为BH RLC信道的标识。其中,BH RLC信道的标识可以新定义的一个标识。其它行的含义可参照第一行和第三行,具体不再赘述。
需要说明的是,上述以一条映射关系为例进行描述的,在上述步骤502和步骤503中,宿主CU可以向宿主DU发送多个第一信息和多个第一承载信息,其中多个第一信息和多个第一承载信息可以一一对应。参见图2B所示意的情形,若宿主DU和IAB节点120之间用于传输OAM业务数据的BH RLC信道为BH RLC信道1,宿主DU和IAB节点122之间用于传输OAM业务数据的BH RLC信道为BH RLC信道1a,则宿主CU可以建立第一信息和BH RLC信道1的标识(或BH RLC信道1对应的逻辑信道的标识)的映射关系以及第一信息和BH RLC信道1a的标识(或BH RLC信道1a对应的逻辑信道的标识)的映射关系。
本申请实施例中,宿主CU确定(或者说建立)第一信息和第一承载信息之间的映射关系的方式可以有多种。示例性地,当采用图5B所示意的方式建立BH RLC信道后,由于BH RLC信道是基于OAM业务的QoS信息建立的,而第一信息中包括的信息均为能够反映出OAM业务的信息,因此,宿主CU可以建立第一信息和BH RLC信道之间的映射关系。
进一步地,宿主CU可以向宿主DU发送第一信息对应的第一承载信息,可以理解为将建立的映射关系通知给宿主DU,具体的实现方式可以有多种,比如可以参照上述宿主CU向宿主DU发送第一IAB节点的DU的IP地址对应的第一路由信息的方式,示例性地,宿主CU可以向宿主DU发送F1AP信令,F1AP信令中包括参数列表,参数列表中可以包括一项或多项信息,每一项信息中包括两个参数;以其中的一项信息包括的两个参数为参数1和参数2为例,该项信息中的参数1可以包括第一信息,参数2可以包括第一承载信息。相应地,宿主DU接收到F1AP信令后,可以获知第一信息对应第一承载信息,并存储该映射关系。本申请实施例中,参数1和参数2可以位于不同的IE中,比如,参数1位于IE1中,参数2位于IE2中,具体不做限定。
步骤504,OAM服务器生成第一数据包,并向宿主DU发送第一数据包。
此处,OAM服务器获取到第一IAB节点的DU的IP地址后,若确定需要向IAB节点的DU的IP地址发送数据,则可以生成第一数据包,第一数据包的目的IP地址为第一IAB节点的DU的IP地址,源IP地址为OAM服务器的IP地址。
示例性地,OAM服务器还可以在第一数据包的IP层头字段中打上对应的DSCP值或流标签,也就是说,第一数据包的IP层头字段中包括DSCP值或流标签。
步骤505,宿主DU从OAM服务器接收第一数据包,并将第一数据包发送给宿主DU的下一跳节点。
示例性地,宿主DU可以将第一数据包映射在对应的BH RLC信道中发送给宿主DU的下一跳节点。
此处,宿主DU接收到第一数据包后,可以解析第一数据包的IP层,可得到第一信息(比如DSCP值或流标签);进而宿主DU可以根据步骤503中接收到的信息,得到DSCP值或流标签对应的BH RLC信道,比如BH RLC信道1。
示例性地,参见上文中的描述,在图2B所示意的情形中,若宿主DU从宿主CU接收到第一信息和BH RLC信道1的标识的映射关系,以及第一信息和BH RLC信道1a的标识的映射关系,则宿主DU可以基于第一数据包的路由信息得到传输第一数据包的路径中宿主DU的下一跳节点(比如IAB节点120),进而可确定出DSCP值或流标签对应的BH RLC信道为BH RLC信道1。
后续,可由宿主DU的下一跳节点(比如IAB节点120)将第一数据包发送给IAB节点121(即第一IAB节点),从而实现了IAB节点121和OAM服务器之间的通信。
上述步骤501至步骤505主要描述了宿主DU将第一数据包映射到相应的BH RLC信道中发送给宿主DU的下一跳节点的实现过程,而针对于第一IAB节点和宿主DU之间的节点来说,其可以根据进口BH RLC信道(ingress BH RLC channel)和出口BH RLC信道(egress BH RLC channel)的映射关系,将第一数据包映射到相应的BH RLC信道中发送给下一跳节点。其中,ingress BH RLC channel和egress BH RLC channel的映射关系可以为宿主CU确定并发送给相应的IAB节点。比如第一IAB节点和宿主DU之间包括IAB节点a和IAB节点b,其中IAB节点b为宿主DU的下一跳节点,针对于IAB节点a和IAB节点b来说,IAB节点b从宿主DU接收到第一数据包后,可以根据第一承载信息将第一数据包映射到对应的BH RLC信道(比如BH RLC信道1b)中发送给IAB节点a;IAB节点a通过BH RLC信道1b接收到第一数据包后,根据ingress BH RLC channel和egress BH RLC channel的映射关系,将第一数据包映射到对应的BH RLC信道(比如BH RLC信道1c)中发送给第一IAB节点。
需要说明的是,上述图5A是以宿主CU确定第一承载信息并发送给宿主DU为例进行描述的。在又一种可能的实施例中,宿主CU也可以确定下行过滤器(DL filter)并发送给宿主DU,下行过滤器用于将待传输的下行数据包映射到相应的BH RLC信道上传输,具体的,DL filter可以根据下行数据包的源地址和/或目标地址,和/或,源端口号和/或目标端口号来进行下行数据包的过滤,将下行数据包直接映射到对应的BH RLC信道上。如此,宿主DU从OAM服务器接收到第一数据包,可以通过下行过滤器将第一数据包映射到对应的BH RLC信道上发送给下一跳节点;除此差异之外的其它内容可以参照上述图5A中的描述。
此外,还有一种可能的实现方式,为了实现简单,宿主CU可以不给宿主DU配置映射关系,由宿主DU直接进行映射。也就是说,宿主DU确定未从所述宿主CU接收到第一信息对应的第一承载信息。即:如果宿主DU与确定路由后的下一跳节点之间只存在一个BH RLC信道,则宿主DU收到第一数据包后直接将该数据包映射到该BH RLC信道上传输。否则,如果宿主DU与确定路由后的下一跳节点之间存在多个BH RLC信道,则宿主DU识别出该第一数据包是OAM业务数据包(如:通过源IP地址,或者端口号,或者预配置的DSCP/flow label),则宿主DU将该数据包映射到第一个建立的BH RLC信道上或者映射到默认的BH RLC信道上或者标准为OAM业务传输预留的BH RLC信道上。该映射方式同样适用F1setup request/response消息以及DHCP discover/off/request/Ack消息的传输。
在又一种可能的实施例中,宿主CU也可以确定第一IAB节点的DU的IP地址和DSCP(或流标识)的映射关系(称为映射关系1)以及DSCP(或流标识)和第一承载信息的映射关系(称为映射关系2),此种情形下,OAM服务器可以无需在第一数据包的IP层头字段中打上对应的DSCP值或流标签,相应地,宿主DU接收到第一数据包后,可以根据第一数据包的目的IP地址和映射关系1得到对应的DSCP(或流标识),进而根据映射关系2得到第一承载信息。除此差异之外的其它内容可以参照上述图5A中的描述。
在下行通信中,针对于上述方案一和方案二,需要说明的是:方案一中侧重于描述路由信息,方案二中侧重于描述承载信息,除此差异之外的其它内容,方案一和方案二可以 相互参照。本申请实施例中,方案一和方案二所描述的方法可以分别单独实施,或者也可以结合实施,具体不做限定。
另外,需要说明的是,步骤504和步骤505是可选的。
(2)上行通信
针对于上行通信,以宿主DU直接有线连接到OAM服务器为例进行说明,宿主DU可以直接向OAM服务器发送第二数据包(第二数据包的目的IP地址可以为OAM服务器的IP地址)。该部分内容将主要研究第一IAB节点(比如此处可以为第一IAB节点的DU)如何将第二数据包发送给宿主DU,示例性,将提供两种可能的方案,分别为方案一和方案二。
方案一
图6为本申请实施例一提供的又一种通信方法所对应的流程示意图,如图6所示,该方法包括:
步骤601,宿主CU获取OAM服务器的IP地址。
此处,宿主CU可以通过多种方式获取OAM服务器的IP地址,具体不做限定。
步骤602,宿主CU确定OAM服务器的IP地址对应的第二路由信息,并向第一IAB节点发送OAM服务器的IP地址对应的第二路由信息。其中,第二路由信息用于将第二数据包路由到宿主DU,第二数据包的目的IP地址为OAM服务器的IP地址。
其中,第二路由信息可以包括第三路径的标识或者第四路径的标识,所述第三路径上的发送节点为所述第一IAB节点,所述第三路径上的接收节点为所述宿主DU;所述第四路径上的发送节点为所述第一IAB节点的上一跳节点,所述第四路径上的接收节点为宿主DU。
步骤603,第一IAB节点从宿主CU接收OAM服务器的IP地址对应的第二路由信息。示例性地,第一IAB节点的DU从宿主CU接收OAM服务器的IP地址对应的第二路由信息。
步骤604,第一IAB节点生成第二数据包,示例性地,第一IAB节点的DU生成第二数据包。
此处,第一IAB节点的DU获取到OAM服务器的IP地址后,若确定需要向OAM服务器的IP地址发送数据,则可以生成第二数据包,第二数据包的源IP地址为第一IAB节点的DU的IP地址,目的IP地址为OAM服务器的IP地址。其中,第一IAB节点的DU获取OAM服务器的IP地址的方式可以有多种,本申请实施例对此不做限定。
步骤605,第一IAB节点将第二数据包和第二路由信息发送给第一IAB节点的上一跳节点。
需要说明的是,上述图6中主要是以宿主CU确定第一路由信息并发送给第一IAB节点为例进行描述的。
在其它可能的实施例中,也可以不需要宿主CU发送确定的第一路由信息给第一IAB节点,如此则可以不再执行步骤601至步骤603;相应地,在步骤605中,第一IAB节点生成第二数据包后,确定第一路由信息(如:宿主DU的标识,或者,宿主DU的IP地址),并将第二路由信息携带在其适配层中与第二数据包一起发送给第一IAB节点的上一跳节点。
需要说明的是,在上行通信的方案一中所描述的方法的思路与下行通信的方案一中所描述的方法的思路类似,其差异之处包括:比如,下行通信中是由宿主DU将第一数据包和第一路由信息发送给宿主DU的下一跳节点,而上行通信中是由第一IAB节点(比如此 处可以为第一IAB节点的MT)将第二数据包和第二路由信息发送给第一IAB节点的上一跳节点。除差异之外的其它内容均可相互参照。
方案二
图7为本申请实施例二提供的又一种通信方法所对应的流程示意图,如图7所示,该方法包括:
步骤701,宿主CU获取第二信息。
步骤702,宿主CU确定第二信息对应的第二承载信息,并向第一IAB节点发送第二信息对应的第二承载信息。所述第二承载信息用于指示传输第二数据包的BH RLC信道,第二数据包包括第二信息。示例性地,第二承载信息可以为BH RLC信道的标识或者BH RLC信道对应的逻辑信道的标识。
步骤703,第一IAB节点从宿主CU接收第二信息对应的第二承载信息。
示例性地,第一IAB节点的MT从宿主CU接收第二信息对应的第二承载信息。
步骤704,第一IAB节点生成第二数据包,示例性地,第一IAB节点的DU生成第二数据包。
示例性地,第一IAB节点的DU可以在第二数据包的IP层头字段中打上对应的DSCP值或流标签,也就是说,第二数据包的IP层头字段中包括DSCP值或流标签;进而,第一IAB节点的DU通过内部接口发送给第一IAB节点的MT。
步骤705,第一IAB节点根据第二承载信息,将第二数据包映射到对应的BH RLC信道中发送给第一IAB节点的上一跳节点。
示例性地,第二IAB节点的MT可以根据从宿主CU获取的映射关系,将第二数据包映射到相应的BH RLC信道中发送给第一IAB节点的上一跳节点。
需要说明的是,在上行通信的方案二中所描述的方法的思路与下行通信的方案二中所描述的方法的思路类似,其差异之处包括:比如,下行通信中是由宿主DU将第一数据包映射到相应的BH RLC信道中发送给宿主DU的下一跳节点,而上行通信中是由第一IAB节点的MT将第二数据包映射到相应的BH RLC信道中发送给第一IAB节点的上一跳节点。除差异之外的其它内容均可相互参照,比如,上行通信的方案二中,传输OAM业务的BH RLC信道可以为协议预定义的一个特有的BH RLC信道。比如,协议预定义逻辑信道1对应的BH RLC信道用于传输OAM业务数据包。又或者,传输OAM业务的BH RLC信道可以是默认的BH RLC信道。比如,第一IAB节点初始接入时建立的默认BH RLC信道。又或者,传输OAM业务的BH RLC信道可以为宿主CU触发建立的,比如宿主CU可以获取第一IAB节点的OAM业务的QoS信息,进而触发宿主DU以及相关IAB节点的DU建立传输OAM业务的BH RLC信道。
为了实现简单,类似于下行通信,宿主CU可以不给第一IAB节点的MT配置映射关系,由第一IAB节点的MT直接进行映射。即:如果第一IAB节点的MT与确定路由后的上一跳节点(父节点)之间只存在一个BH RLC信道,则第一IAB节点的MT收到第一数据包后直接将该数据包映射到该BH RLC信道上传输。否则,如果第一IAB节点的MT与确定路由后的上一跳节点(父节点)之间存在多个BH RLC信道,则第一IAB节点的MT获知该第一数据包是OAM业务数据包(如:通过源IP地址,或者端口号,或者预配置的DSCP/flow label),则第一IAB节点的MT将该数据包映射到第一个建立的BH RLC信道上或者映射到默认的BH RLC信道上或者标准为OAM业务传输预留的BH RLC信道上。 该映射方式同样适用F1setup request/response消息以及DHCP discover/off/request/Ack消息的传输。
在上行通信中,针对于上述方案一和方案二,需要说明的是:方案一中侧重于描述路由信息,方案二中侧重于描述承载信息,除此差异之外的其它内容,方案一和方案二可以相互参照。本申请实施例中,方案一和方案二所描述的方法可以分别单独实施,或者也可以结合实施,具体不做限定。
需要说明的是,实施例一中主要以第一IAB节点与宿主DU之间存在一个或多个其它IAB节点为例进行描述的,若第一IAB节点与宿主DU之间不存在其它IAB节点,比如第一IAB节点为图2A中所示意的IAB节点120,此种情形下,从路由的角度来看,宿主DU可以直接和第一IAB节点进行通信,比如宿主DU接收到第一数据包后,可以直接将第一数据包发送给第一IAB节点;从承载的角度来看,其同样可以采用上述方案二中所描述的方法,以确定宿主DU和第一IAB节点之间的BH RLC信道,并将第一数据包映射到该BH RLC信道中发送给第一IAB节点。
实施例二
在实施例二中,将主要针对第一IAB节点通过宿主CU和OAM服务器进行通信(比如图3B所示意的情形))的实现进行描述。该实施例中,示例性地,第一IAB节点的IP地址可以是由宿主CU分配的,也可以是由DHCP服务器分配的,宿主CU作为DHCP proxy。
第一IAB节点通过宿主CU和OAM服务器进行通信可以包括下行通信(比如:第一IAB节点←……←宿主CU←OAM服务器)和上行通信(比如:第一IAB节点→……→宿主CU→OAM服务器)。其中,在该实施例中,上行通信可以参见实施例一中的描述。下面仅对下行通信进行介绍。
针对于下行通信,宿主CU可以将从OAM服务器接收到的数据包转发给宿主DU,进而由宿主DU将第一数据包发送给第一IAB节点。示例性地,将提供两种可能的方案,分别为方案一和方案二。
方案一
在方案一中,以图3B中所示意的情形为例,假设第一IAB节点为图3B中的IAB节点121,此种情形下,第一IAB节点和OAM服务器进行通信的协议栈如图3D所示。
基于图3D所示意的协议栈,图8为本申请实施例二提供的又一种通信方法所对应的流程示意图,如图8所示,该方法包括:
步骤801,OAM服务器生成第一数据包,并向宿主CU发送第一数据包。
示例性,第一数据包的OAM层中包括第一IAB节点的DU的标识。
步骤802,宿主CU从OAM服务器接收第一数据包。
步骤803,宿主CU解析第一数据包的OAM层获取到第一IAB节点的DU的标识,可获知第一数据包为需要发送给第一IAB节点的数据包,进而可将第一数据包和第一路由信息发送给宿主DU。
步骤804,宿主DU接收到第一数据包和第一路由信息后,根据第一路由信息确定宿主DU的下一跳节点,并将第一数据和第一路由信息发送给宿主DU的下一跳节点。
需要说明的是,实施例二中下行通信的方案一描述的方法与实施例一中下行通信的方案一描述的方法的差异之处包括:比如,实施例一中下行通信的方案一中,宿主CU确定 第一路由信息并发送给宿主DU,进而后续宿主DU从OAM服务器接收到第一数据包后,可以根据第一数据包的目的IP地址得到对应的第一路由信息,并将第一数据包和第一路由信息发送给宿主DU的下一跳节点;实施例二中下行通信的方案一中,宿主CU从OAM服务器接收到第一数据包后,可以将第一数据包和第一路由信息一并发送给宿主DU;又比如,实施例一中下行通信的方案一中,宿主CU是基于第一IAB节点的DU的IP地址确定对应的第一路由信息,而实施例二中下行通信的方案一中,宿主CU是基于第一IAB节点的DU的标识确定对应的第一路由信息。除差异之外的其它内容二者可以相互参照。
方案二
在方案二中,以图3B中所示意的情形为例,假设第一IAB节点为图3B中的IAB节点121,此种情形下,第一IAB节点和OAM服务器进行通信的协议栈如图3E和图3F所示。其中,图3E和图3F的协议栈区别在于,图3F中采用ip-in-ip的方式,即OAM业务的数据包(IP包)封装在宿主CU和宿主DU之间的IP包中进行传输。图3E中,宿主DU类似于路由器,根据OAM业务的数据包的IP地址进行转发。
图9为本申请实施例二提供的又一种通信方法所对应的流程示意图,如图9所示,该方法包括:
步骤901,OAM服务器生成第一数据包,并向宿主CU发送第一数据包。
此处,OAM服务器获取到第一IAB节点的DU的IP地址后,若确定需要向第一IAB节点发送数据,则可以生成第一数据包,第一数据包的目的IP地址为第一IAB节点的DU的IP地址,源IP地址为OAM服务器的IP地址。
步骤902,宿主CU从OAM服务器接收第一数据包。
步骤903,宿主CU解析第一数据包的IP层获取到目的IP地址,进而将第一数据包和第一路由信息发送给宿主DU。
步骤904,宿主DU接收到第一数据包和第一路由信息后,根据第一路由信息确定宿主DU的下一跳节点,并将第一数据和第一路由信息发送给宿主DU的下一跳节点。
需要说明的是,实施例二中下行通信的方案二描述的方法与实施例二中下行通信的方案一描述的方法的差异之处包括:比如,实施例二中下行通信的方案一中,宿主CU从OAM服务器接收到第一数据包后,是基于第一数据包包括的第一IAB节点的DU的标识来确定第一路由信息,而实施例二中下行通信的方案二中,宿主CU从OAM服务器接收到第一数据包后,是基于第一数据包的目的IP地址来确定第一路由信息。除差异之外的其它内容二者可以相互参照。
针对于实施例一和实施例二,需要说明的是,实施例二中的方案一或方案二可以分别单独实施,或者,也可以与实施例一中下行通信的方案二结合实施,具体不做限定。
本申请的上述各个实施例中所涉及的步骤编号仅为执行流程的一种可能的示例,并不构成对各个步骤的执行先后顺序的限制。本申请实施例中,相互之间没有时序依赖关系的步骤之间没有严格的执行顺序。上述各个附图中所示意的步骤并非必选步骤,具体实施中,可以基于上述各附图进行增删,具体不做限定。
上述主要从宿主CU、宿主DU之间交互的角度对本申请实施例提供的方案进行了介绍。可以理解的是,为了实现上述功能,宿主CU、宿主DU可以包括执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到,结合本文中所公开的实施 例描述的各示例的单元及算法步骤,本申请的实施例能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行,取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能,但是这种实现不应认为超出本申请的范围。
在采用集成的单元(模块)的情况下,图10示出了本申请实施例中所涉及的装置的可能的示例性框图。如图10所示,装置1000可以包括:处理单元1002和通信单元1003。处理单元1002、通信单元1003和存储单元1001通过通信总线相连。通信单元1003可以是具有收发功能的装置,用于与其他设备进行通信。存储单元1001可以包括一个或者多个存储器。存储单元1001可以独立存在,通过通信总线与处理单元1002相连。存储单元1001也可以与处理单元1201集成在一起。
处理单元1002用于对装置1000的动作进行控制管理。通信单元1003用于支持装置1000与其他网络实体的通信。可选地,通信单元1003也称为收发单元,可以包括接收单元和/或发送单元,分别用于执行接收和发送操作。装置1000还可以包括存储单元1001,用于存储装置1000的程序代码和/或数据。
其中,处理单元1002可以是处理器或控制器,其可以实现或执行结合本申请的实施例公开内容所描述的各种示例性的逻辑方框,模块和电路。通信单元1003可以是通信接口、收发器或收发电路等,其中,该通信接口是统称,在具体实现中,该通信接口可以包括多个接口。存储单元1001可以是存储器。
该装置1000可以为上述任一实施例中的宿主DU、或者还可以为设置在宿主DU中的芯片。处理单元1002可以支持装置1000执行上文中各方法示例中宿主DU的动作。或者,处理单元1002主要执行方法示例中的宿主DU内部动作,通信单元1003可以支持装置1000与其它设备之间的通信。例如,通信单元1003用于执行图4中的步骤403和步骤404。
具体地,在一个实施例中,通信单元用于,从宿主集中式单元CU接收第一接入回传一体化IAB节点的互联网协议IP地址和第一路由信息,所述第一路由信息用于将第一数据包路由到所述第一IAB节点,其中,所述第一数据包为OAM业务数据包,所述第一数据包的目的IP地址为所述第一IAB节点的IP地址;从OAM服务器接收所述第一数据包;以及,将所述第一数据包和所述第一路由信息发送给所述宿主DU的下一跳节点。
在一种可能的设计中,所述第一路由信息包括:第一路径的标识,所述第一路径上的发送节点为所述宿主DU,所述第一路径上的接收节点为所述第一IAB节点;或者,所述第一IAB节点的第一标识。
在一种可能的设计中,所述第一IAB节点的第一标识为宿主集中式单元CU为所述第一IAB节点分配的适配层标识。
在一种可能的设计中,所述第一路由信息包括:第二路径的标识和所述第一IAB节点的第二标识,所述第二路径上的发送节点为所述宿主DU,所述第二路径上的接收节点为所述第一IAB节点的父节点;或者,所述第一IAB节点的父节点的标识和所述第一IAB节点的第二标识。
在一种可能的设计中,所述第一IAB节点的第二标识为所述第一IAB节点的父节点为所述第一IAB节点分配的小区无线网络临时标识C-RNTI,或者,所述第一IAB节点的第二标识为所述第一IAB节点的父节点为所述第一IAB节点分配的第一F1AP标识;或者,所述第一IAB节点的第二标识包括所述第一F1AP标识和所述宿主CU为所述第一IAB节点分配的 第二F1AP标识。
在一种可能的设计中,通信单元具体用于:所述宿主DU将所述第一路由信息携带在所述宿主DU的适配层中发送给所述宿主DU的下一跳节点。
在一种可能的设计中,通信单元还用于,从宿主CU接收第一信息和第一承载信息,所述第一承载信息用于指示传输第一数据包的回传无线链路控制BH RLC信道;所述第一数据包包括所述第一信息,所述第一信息包括以下至少一项:差分服务代码点DSCP值、流标签、所述OAM服务器的IP地址、端口号;将所述第一数据包映射到所述BH RLC信道中发送给所述宿主DU的下一跳节点。
在又一个实施例中,通信单元用于,从宿主CU接收第一信息和第一承载信息,所述第一承载信息用于指示传输第一数据包的BH RLC信道,所述第一数据包包括所述第一信息,所述第一信息包括以下至少一项:DSCP值、流标签、所述OAM服务器的IP地址、端口号;从OAM服务器接收所述第一数据包;以及,将所述第一数据包映射到所述BH RLC信道中发送给所述宿主DU的下一跳节点。
该装置1000可以为上述任一实施例中的宿主CU、或者还可以为设置在宿主CU中的芯片。处理单元1002可以支持装置1000执行上文中各方法示例中宿主CU的动作。或者,处理单元1002主要执行方法示例中的宿主CU内部动作,通信单元1003可以支持装置1000与其它设备之间的通信。例如,通信单元1003用于执行图4中的步骤401,处理单元可以用于执行图4中的步骤404。
具体地,在一个实施例中,通信单元用于,获取第一IAB节点的IP地址和第一路由信息,所述第一路由信息用于将第一数据包路由到所述第一IAB节点,其中,所述第一数据包为OAM业务数据包,所述第一数据包的目的IP地址为所述第一IAB节点的IP地址;以及,向宿主DU发送所述第一IAB节点的IP地址和所述第一路由信息。
在一种可能的设计中,所述第一路由信息包括:第一路径的标识,所述第一路径上的发送节点为所述宿主DU,所述第一路径上的接收节点为所述第一IAB节点;或者,所述第一IAB节点的第一标识。
在一种可能的设计中,所述第一IAB节点的第一标识为宿主集中式单元CU为所述第一IAB节点分配的适配层标识。
在一种可能的设计中,所述第一路由信息包括:第二路径的标识和所述第一IAB节点的第二标识,所述第二路径上的发送节点为所述宿主DU,所述第二路径上的接收节点为所述第一IAB节点的父节点;或者,所述第一IAB节点的父节点的标识和所述第一IAB节点的第二标识。
在一种可能的设计中,所述第一IAB节点的第二标识为所述第一IAB节点的父节点为所述第一IAB节点分配的C-RNTI,或者,所述第一IAB节点的第二标识为所述第一IAB节点的父节点为所述第一IAB节点分配的第一F1AP标识;或者,所述第一IAB节点的第二标识包括所述第一F1AP标识和所述宿主CU为所述第一IAB节点分配的第二F1AP标识。
在一种可能的设计中,通信单元还用于,向所述宿主DU发送第一信息和第一承载信息,所述第一承载信息用于指示传输第一数据包的BH RLC信道,所述第一数据包包括所述第一信息,所述第一信息包括以下至少一项:DSCP值、流标签、所述OAM服务器的IP地址、端口号。
在又一个实施例中,通信单元用于,获取第一信息和第一承载信息,所述第一承载信 息用于指示传输第一数据包的BH RLC信道,所述第一数据包包括所述第一信息,所述第一信息包括以下至少一项:DSCP值、流标签、所述OAM服务器的IP地址、端口号;以及,向宿主DU发送所述第一信息和所述第一承载信息。
图11为本申请实施例中所涉及的装置的结构示意图,如可以为基站的结构示意图,示例性地可以为宿主基站的结构示意图,当基站110为宿主基站时,其所包括的DU可以是指宿主DU,其所包括的CU可以是指宿主CU。如图11所示,该基站可应用于如图1或图2A或图2B所示的系统中,执行上述方法实施例中宿主基站的功能。基站110可包括一个或多个DU 1101和一个或多个CU 1102。所述DU 1101可以包括至少一个天线11011,至少一个射频单元11012,至少一个处理器11013和至少一个存储器11014。所述DU 1101部分主要用于射频信号的收发以及射频信号与基带信号的转换,以及部分基带处理。CU1102可以包括至少一个处理器11022和至少一个存储器11021。CU1102和DU1101之间可以通过接口进行通信,其中,控制面(Control plan)接口可以为Fs-C,比如F1-C,用户面(User Plan)接口可以为Fs-U,比如F1-U。
所述CU 1102部分主要用于进行基带处理,对基站进行控制等。所述DU 1101与CU1102可以是物理上设置在一起,也可以物理上分离设置的,即分布式基站。所述CU 1102为基站的控制中心,也可以称为处理单元,主要用于完成基带处理功能。例如所述CU 1102可以用于控制基站执行上述方法实施例中关于网络设备的操作流程。
具体的,CU和DU上的基带处理可以根据无线网络的协议层划分,例如PDCP层及以上协议层的功能设置在CU,PDCP以下的协议层,例如RLC层和MAC层等的功能设置在DU。又例如,CU实现RRC层、PDCP层的功能,DU实现RLC层、MAC层和物理层的功能。
此外,可选的,宿主基站110可以包括一个或多个射频单元(RU),一个或多个DU和一个或多个CU。其中,DU可以包括至少一个处理器11013和至少一个存储器11014,RU可以包括至少一个天线11011和至少一个射频单元11012,CU可以包括至少一个处理器11022和至少一个存储器11021。
在一个实施例中,所述CU1102可以由一个或多个单板构成,多个单板可以共同支持单一接入指示的无线接入网(如5G网),也可以分别支持不同接入制式的无线接入网(如LTE网,5G网或其他网)。所述存储器11021和处理器11022可以服务于一个或多个单板。也就是说,可以每个单板上单独设置存储器和处理器。也可以是多个单板共用相同的存储器和处理器。此外每个单板上还可以设置有必要的电路。所述DU1101可以由一个或多个单板构成,多个单板可以共同支持单一接入指示的无线接入网(如5G网),也可以分别支持不同接入制式的无线接入网(如LTE网,5G网或其他网)。所述存储器11014和处理器11013可以服务于一个或多个单板。也就是说,可以每个单板上单独设置存储器和处理器。也可以是多个单板共用相同的存储器和处理器。此外每个单板上还可以设置有必要的电路。
可选地,宿主基站110中的DU可以通过天线将数据包发送宿主DU的下一跳节点中的MT,进而由宿主DU的下一跳节点中的MT通过内部接口将该数据包发送给宿主DU的下一跳节点中的DU。
在实现过程中,本实施例提供的方法中的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。结合本申请实施例所公开的方法的步骤可以直接体现为硬件处理器执行完成,或者用处理器中的硬件及软件模块组合执行完成。
应注意,本申请实施例中的处理器可以是一种集成电路芯片,具有信号的处理能力。在实现过程中,上述方法实施例的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器可以是通用中央处理器(central processing unit,CPU),通用处理器,数字信号处理(digital signal processing,DSP),专用集成电路(application specific integrated circuits,ASIC),现场可编程门阵列(field programmable gate array,FPGA)或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合;也可以是实现计算功能的组合,例如包括一个或多个微处理器组合,DSP和微处理器的组合等等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
可以理解,本申请实施例中的存储器或存储单元可以是易失性存储器或非易失性存储器,或可包括易失性和非易失性存储器两者。其中,非易失性存储器可以是只读存储器(read-only memory,ROM)、可编程只读存储器(programmable ROM,PROM)、可擦除可编程只读存储器(erasable PROM,EPROM)、电可擦除可编程只读存储器(electrically EPROM,EEPROM)或闪存。易失性存储器可以是随机存取存储器(random access memory,RAM),其用作外部高速缓存。通过示例性但不是限制性说明,许多形式的RAM可用,例如静态随机存取存储器(static RAM,SRAM)、动态随机存取存储器(dynamic RAM,DRAM)、同步动态随机存取存储器(synchronous DRAM,SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM,DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM,ESDRAM)、同步连接动态随机存取存储器(synchlink DRAM,SLDRAM)和直接内存总线随机存取存储器(direct rambus RAM,DR RAM)。应注意,本文描述的系统和方法的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
在上述实施例中,可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时,可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机程序或指令。在计算机上加载和执行所述计算机程序或指令时,全部或部分地执行本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机程序或指令可以存储在计算机可读存储介质中,或者通过所述计算机可读存储介质进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是集成一个或多个可用介质的服务器等数据存储设备。所述可用介质可以是磁性介质,例如,软盘、硬盘、磁带;也可以是光介质,例如,DVD;还可以是半导体介质,例如,固态硬盘(solid state disk,SSD)。
本申请实施例中所描述的各种说明性的逻辑单元和电路可以通过通用处理器,数字信号处理器,专用集成电路(ASIC),现场可编程门阵列(FPGA)或其它可编程逻辑装置,离散门或晶体管逻辑,离散硬件部件,或上述任何组合的设计来实现或操作所描述的功能。通用处理器可以为微处理器,可选地,该通用处理器也可以为任何传统的处理器、控制器、微控制器或状态机。处理器也可以通过计算装置的组合来实现,例如数字信号处理器和微处理器,多个微处理器,一个或多个微处理器联合一个数字信号处理器核,或任何其它类似的配置来实现。
本申请实施例中所描述的方法或算法的步骤可以直接嵌入硬件、处理器执行的软件单元、或者这两者的结合。软件单元可以存储于RAM存储器、闪存、ROM存储器、EPROM存储器、EEPROM存储器、寄存器、硬盘、可移动磁盘、CD-ROM或本领域中其它任意形式的存储媒介中。示例性地,存储媒介可以与处理器连接,以使得处理器可以从存储媒 介中读取信息,并可以向存储媒介存写信息。可选地,存储媒介还可以集成到处理器中。处理器和存储媒介可以设置于ASIC中,ASIC可以设置于终端设备中。可选地,处理器和存储媒介也可以设置于终端设备中的不同的部件中。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上,使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理,从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
尽管结合具体特征对本申请实施例进行了描述,显而易见的,在不脱离本申请实施例的精神和范围的情况下,可对其进行各种修改和组合。相应地,本说明书和附图仅仅是所附权利要求所界定的本申请实施例的示例性说明,且视为已覆盖本申请实施例范围内的任意和所有修改、变化、组合或等同物。
Claims (52)
- 一种通信方法,其特征在于,所述方法包括:宿主分布式单元DU从宿主集中式单元CU接收第一接入回传一体化IAB节点的互联网协议IP地址和第一路由信息,所述第一路由信息用于将第一数据包路由到所述第一IAB节点,其中,所述第一数据包的目的IP地址为所述第一IAB节点的IP地址;所述宿主DU接收所述第一数据包;所述宿主DU将所述第一数据包和所述第一路由信息发送给所述宿主DU的下一跳节点。
- 根据权利要求1所述的方法,其特征在于,所述第一数据包为操作管理维护OAM业务数据包;或者,所述第一数据包为动态主机设置协议DHCP业务数据包。
- 根据权利要求1或2所述的方法,其特征在于,所述第一路由信息包括:第一路径的标识,所述第一路径上的发送节点为所述宿主DU,所述第一路径上的接收节点为所述第一IAB节点;或者,所述第一IAB节点的第一标识。
- 根据权利要求3所述的方法,其特征在于:所述第一IAB节点的第一标识为宿主集中式单元CU为所述第一IAB节点分配的适配层标识。
- 根据权利要求1或2所述的方法,其特征在于,所述第一路由信息包括:第二路径的标识和所述第一IAB节点的第二标识,所述第二路径上的发送节点为所述宿主DU,所述第二路径上的接收节点为所述第一IAB节点的父节点;或者,所述第一IAB节点的父节点的标识和所述第一IAB节点的第二标识。
- 根据权利要求5所述的方法,其特征在于:所述第一IAB节点的第二标识为所述第一IAB节点的父节点为所述第一IAB节点分配的小区无线网络临时标识C-RNTI,或者,所述第一IAB节点的第二标识为所述第一IAB节点的父节点为所述第一IAB节点分配的第一F1AP标识;或者,所述第一IAB节点的第二标识包括所述第一F1AP标识和所述宿主CU为所述第一IAB节点分配的第二F1AP标识。
- 根据权利要求1至6中任一项所述的方法,其特征在于,所述宿主DU将所述第一路由信息发送给所述宿主DU的下一跳节点,包括:所述宿主DU将所述第一路由信息携带在所述宿主DU的适配层中发送给所述宿主DU的下一跳节点。
- 根据权利要求1至7中任一项所述的方法,其特征在于,所述宿主DU将所述第一数据包发送给所述宿主DU的下一跳节点,包括:所述宿主DU从宿主CU接收第一信息对应的第一承载信息,所述第一承载信息用于指示传输第一数据包的回传无线链路控制BH RLC信道;所述第一数据包包括所述第一信息,所述第一信息包括以下至少一项:差分服务代码点DSCP值、流标签、所述OAM服务器的IP地址、端口号;所述宿主DU将所述第一数据包映射到所述BH RLC信道中发送给所述宿主DU的下一跳节点。
- 根据权利要求1至7中任一项所述的方法,其特征在于,所述宿主DU将所述第一数据包发送给所述宿主DU的下一跳节点,包括:所述宿主DU将所述第一数据包映射到预定义的BH RLC信道中发送给所述宿主DU的下一跳节点;或者,所述宿主DU将所述第一数据包映射到默认BH RLC信道中发送给所述宿主DU的下一跳节点;或者,所述宿主DU将所述第一数据包映射到第一个建立的BH RLC信道中发送给所述宿主DU的下一跳节点。
- 根据权利要求9所述的方法,其特征在于,所述宿主DU未从所述宿主CU接收到第一信息对应的第一承载信息,所述第一承载信息用于指示传输所述第一数据包的BH RLC信道,所述第一数据包包括所述第一信息,所述第一信息包括以下一项或者多项:DSCP值、流标签、所述OAM服务器的IP地址和端口号。
- 一种通信方法,其特征在于,所述方法包括:宿主CU获取第一IAB节点的IP地址和第一路由信息,所述第一路由信息用于将第一数据包路由到所述第一IAB节点,其中,所述第一数据包的目的IP地址为所述第一IAB节点的IP地址;所述宿主CU向宿主DU发送所述第一IAB节点的IP地址和所述第一路由信息。
- 根据权利要求11所述的方法,其特征在于,所述第一数据包为操作管理维护OAM业务数据包;或者,所述第一数据包为DHCP业务数据包。
- 根据权利要求11或12所述的方法,其特征在于,所述第一路由信息包括:第一路径的标识,所述第一路径上的发送节点为所述宿主DU,所述第一路径上的接收节点为所述第一IAB节点;或者,所述第一IAB节点的第一标识。
- 根据权利要求13所述的方法,其特征在于:所述第一IAB节点的第一标识为宿主集中式单元CU为所述第一IAB节点分配的适配层标识。
- 根据权利要求11或12所述的方法,其特征在于,所述第一路由信息包括:第二路径的标识和所述第一IAB节点的第二标识,所述第二路径上的发送节点为所述宿主DU,所述第二路径上的接收节点为所述第一IAB节点的父节点;或者,所述第一IAB节点的父节点的标识和所述第一IAB节点的第二标识。
- 根据权利要求15所述的方法,其特征在于:所述第一IAB节点的第二标识为所述第一IAB节点的父节点为所述第一IAB节点分配的C-RNTI,或者,所述第一IAB节点的第二标识为所述第一IAB节点的父节点为所述第一IAB节点分配的第一F1AP标识;或者,所述第一IAB节点的第二标识包括所述第一F1AP标识和所述宿主CU为所述第一IAB节点分配的第二F1AP标识。
- 根据权利要求11至16中任一项所述的方法,其特征在于,所述方法还包括:所述宿主CU向所述宿主DU发送第一信息对应的第一承载信息,所述第一承载信息用于指示传输第一数据包的BH RLC信道,所述第一数据包包括所述第一信息,所述第一信息包括以下至少一项:DSCP值、流标签、所述OAM服务器的IP地址、端口号。
- 一种通信方法,其特征在于,所述方法包括:宿主DU从宿主CU接收第一信息对应的第一承载信息,所述第一承载信息用于指示传输第一数据包的BH RLC信道,所述第一数据包包括所述第一信息,所述第一信息包括以 下至少一项:DSCP值、流标签、所述OAM服务器的IP地址、端口号;所述宿主DU接收所述第一数据包;所述宿主DU将所述第一数据包映射到所述BH RLC信道中发送给所述宿主DU的下一跳节点。
- 根据权利要求18所述的方法,其特征在于,所述第一数据包为OAM业务数据包;所述宿主DU接收所述第一数据包,包括:所述宿主DU从OAM服务器接收所述第一数据包。
- 根据权利要求18所述的方法,其特征在于,所述第一数据包为F1建立请求消息或者F1建立响应消息。
- 一种通信方法,其特征在于,所述方法包括:宿主DU接收第一数据包;所述宿主DU将所述第一数据包映射到预定义的BH RLC信道中发送给所述宿主DU的下一跳节点;或者,所述宿主DU将所述第一数据包映射到默认BH RLC信道中发送给所述宿主DU的下一跳节点;或者,所述宿主DU将所述第一数据包映射到第一个建立的BH RLC信道中发送给所述宿主DU的下一跳节点。
- 根据权利要求21所述的方法,其特征在于,所述宿主DU未从所述宿主CU接收到第一信息对应的第一承载信息,所述第一承载信息用于指示传输第一数据包的BH RLC信道,所述第一数据包包括所述第一信息,所述第一信息包括以下至少一项:DSCP值、流标签、所述OAM服务器的IP地址、端口号。
- 根据权利要求21或22所述的方法,其特征在于,所述第一数据包为OAM业务数据包;所述宿主DU接收第一数据包,包括:所述宿主DU从OAM服务器接收所述第一数据包。
- 根据权利要求21或22所述的方法,其特征在于,所述第一数据包为F1建立请求消息或者F1建立响应消息。
- 一种通信方法,其特征在于,所述方法包括:宿主CU获取第一信息对应的第一承载信息,所述第一承载信息用于指示传输第一数据包的BH RLC信道,所述第一数据包包括所述第一信息,所述第一信息包括以下至少一项:DSCP值、流标签、所述OAM服务器的IP地址、端口号;所述宿主CU向宿主DU发送所述第一信息对应的所述第一承载信息。
- 根据权利要求25所述的方法,其特征在于,所述第一数据包为OAM业务数据包。
- 根据权利要求25所述的方法,其特征在于,所述第一数据包为F1建立请求消息或者F1建立响应消息。
- 一种通信方法,其特征在于,所述方法包括:第一IAB节点从宿主CU接收第二信息对应的第二承载信息,所述第二承载信息用于指示传输第二数据包的BH RLC信道,所述第二数据包包括第二信息;第一IAB节点生成所述第二数据包;第一IAB节点根据所述第二承载信息将所述第二数据包映射到BH RLC信道中发送给第一IAB节点的上一跳节点。
- 根据权利要求28所述的方法,其特征在于,所述第二信息包括以下一项或者多项:DSCP值、流标签、OAM服务器的IP地址和端口号。
- 根据权利要求28或29所述的方法,其特征在于,所述第二数据包为OAM业务数据包。
- 根据权利要求28或29所述的方法,其特征在于,所述第二数据包为F1建立请求消息或者F1建立响应消息。
- 一种通信方法,其特征在于,所述方法包括:所述第一IAB节点的DU生成第二数据包;所述第一IAB节点的MT将所述第二数据包映射到预定义的BH RLC信道中发送给所述第一IAB节点的上一跳节点;或者,所述第一IAB节点将所述第二数据包映射到默认BH RLC信道中发送给所述第一IAB节点的上一跳节点;或者,所述第一IAB节点将所述第二数据包映射到第一个建立的BH RLC信道中发送给所述第一IAB节点的上一跳节点。
- 根据权利要求32所述的方法,其特征在于,所述第一IAB节点未从所述宿主CU接收到第二信息对应的第二承载信息,所述第二承载信息用于指示传输所述第二数据包的BH RLC信道,所述第二数据包包括所述第二信息,所述第二信息包括以下至少一项:DSCP值、流标签、所述OAM服务器的IP地址、端口号。
- 根据权利要求32或33所述的方法,其特征在于,所述第二数据包为OAM业务数据包。
- 根据权利要求32或33所述的方法,其特征在于,所述第二数据包为F1建立请求消息或者F1建立响应消息。
- 一种通信方法,其特征在于,所述方法包括:IAB节点从宿主CU接收进口BH RLC信道和出口BH RLC信道的映射关系;所述IAB节点通过所述进口BH RLC信道接收到数据包后,将所述数据包映射到对应的出口BH RLC信道中发送给所述IAB节点的下一跳节点,所述数据包为OAM业务数据包。
- 一种通信装置,其特征在于,所述装置包括用于执行如权利要求1至36中任一项所述的方法的单元。
- 一种通信装置,其特征在于,所述装置执行如权利要求1至36中任一项所述的方法。
- 一种通信装置,其特征在于,包括:通信接口和至少一个处理器,所述通信接口和所述至少一个处理器通过线路互联,所述通信接口用于执行权利要求1到10中任一项,或者权利要求18至20中任一项,或者权利要求21至24中任一项所述的方法中,在所述装置侧进行消息接收和发送的操作;所述至少一个处理器调用指令,执行权利要求1到10任一项,或者权利要求18至20中任一项,或者权利要求21至24中任一项所述的方法中,在所述装置进行的消息处理或控制操作。
- 根据权利要求39所述的装置,其特征在于,所述装置为宿主DU。
- 一种通信装置,其特征在于,包括:通信接口和至少一个处理器,所述通信接口和所述至少一个处理器通过线路互联,所述通信接口用于执行权利要求11到17中任一项,或者权利要求25至27中任一项所述的方法中,在所述装置侧进行消息接收和发送的操作;所述至少一个处理器调用指令,执行权利要求11到17中任一项,或者权利要求25 至27中任一项所述的方法中,在所述装置进行的消息处理或控制操作。
- 根据权利要求41所述的装置,其特征在于,所述装置为宿主CU。
- 一种通信装置,其特征在于,包括:通信接口和至少一个处理器,所述通信接口和所述至少一个处理器通过线路互联,所述通信接口用于执行权利要求28到31中任一项,或者权利要求32至35中任一项所述的方法中,在所述装置侧进行消息接收和发送的操作;所述至少一个处理器调用指令,执行权利要求28到31中任一项,或者权利要求32至35中任一项所述的方法中,在所述装置进行的消息处理或控制操作。
- 根据权利要求43所述的装置,其特征在于,所述装置为第一IAB节点。
- 一种通信装置,其特征在于,包括:通信接口和至少一个处理器,所述通信接口和所述至少一个处理器通过线路互联,所述通信接口用于执行权利要求36所述的方法中,在所述装置侧进行消息接收和发送的操作;所述至少一个处理器调用指令,执行权利要求36所述的方法中,在所述装置进行的消息处理或控制操作。
- 根据权利要求45所述的装置,其特征在于,所述装置为IAB节点。
- 一种通信系统,其特征在于,所述通信系统包括如权利要求39或40所述的装置和如权利要求41或42所述的装置。
- 根据权利要求47所述的通信系统,其特征在于,所述通信系统还包括如权利要求43或44所述的装置。
- 根据权利要求47或48所述的通信系统,其特征在于,所述通信系统还包括如权利要求45或46所述的装置。
- 一种通信装置,其特征在于,包括处理器,所述处理器与存储器耦合,所述存储器用于存储计算机程序或指令,所述处理器用于执行所述计算机程序或指令,使得权利要求1至10中任一所述的方法,或者权利要求11至17中任一所述的方法,或者权利要求18至20中任一项所述的方法,或者权利要求21至24中任一项所述的方法,或者权利要求25至27中任一项所述的方法,或者权利要求28至31中任一项所述的方法,或者权利要求32至35中任一项所述的方法,或者权利要求36所述的方法被执行。
- 一种包含指令的计算机程序产品,其特征在于,当其在计算机上运行时,使得计算机执行上述1到36中任一项所述的方法。
- 一种计算机可读存储介质,其特征在于,包括指令,当其在计算机上运行时,使得执行如权利要求1至36中任一项所述的方法。
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201910365512.0 | 2019-04-30 | ||
CN201910365512.0A CN111865802B (zh) | 2019-04-30 | 2019-04-30 | 一种通信方法及装置 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2020221360A1 true WO2020221360A1 (zh) | 2020-11-05 |
Family
ID=72966737
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2020/088499 WO2020221360A1 (zh) | 2019-04-30 | 2020-04-30 | 一种通信方法及装置 |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN111865802B (zh) |
WO (1) | WO2020221360A1 (zh) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN115250508A (zh) * | 2021-04-25 | 2022-10-28 | 大唐移动通信设备有限公司 | Iab网络中数据传输的方法、iab节点及存储介质 |
US12149981B2 (en) | 2019-08-15 | 2024-11-19 | Samsung Electronics Co., Ltd. | Method and apparatus for mapping backhaul channels in a wireless system |
Families Citing this family (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
GB2583521B (en) * | 2019-05-02 | 2022-01-12 | Samsung Electronics Co Ltd | Relay network routing |
US20240015530A1 (en) * | 2020-11-04 | 2024-01-11 | Nokia Technologies Oy | Routing in Integrated Access and Backhaul Communication |
CN114650569A (zh) * | 2020-12-18 | 2022-06-21 | 维沃移动通信有限公司 | 自回传iab网络中数据分流的方法及装置、网络侧设备 |
CN114765830A (zh) * | 2021-01-15 | 2022-07-19 | 华为技术有限公司 | 一种通信方法及相关设备 |
CN115051949B (zh) * | 2021-03-09 | 2024-08-16 | 维沃移动通信有限公司 | 数据路由方法及装置 |
WO2022205326A1 (en) * | 2021-04-01 | 2022-10-06 | Zte Corporation | Integrated access and backhaul donor migration methods and systems |
CN115190536A (zh) * | 2021-04-01 | 2022-10-14 | 华为技术有限公司 | 用于信息传输的方法和装置 |
CN117280850A (zh) * | 2021-04-01 | 2023-12-22 | 中兴通讯股份有限公司 | 无线通信中的流量传输方案 |
CN118510077A (zh) * | 2023-02-16 | 2024-08-16 | 华为技术有限公司 | 通信方法及通信装置 |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2018175817A1 (en) * | 2017-03-23 | 2018-09-27 | Intel Corporation | Advanced radio resource management in next-gen multi-hop relaying cellular network |
WO2019042228A1 (zh) * | 2017-08-26 | 2019-03-07 | 华为技术有限公司 | 一种通过中继的通信处理方法和装置 |
Family Cites Families (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10631346B2 (en) * | 2017-08-08 | 2020-04-21 | Qualcomm Incorporated | Communicating remote and local data in a wireless fronthaul |
EP3516818B1 (en) * | 2017-08-10 | 2020-06-24 | Ofinno, LLC | Radio resource configuration synchronization |
CN109257212B (zh) * | 2018-09-10 | 2021-09-03 | 中信科移动通信技术股份有限公司 | 一种iab基站接入的方法 |
-
2019
- 2019-04-30 CN CN201910365512.0A patent/CN111865802B/zh active Active
-
2020
- 2020-04-30 WO PCT/CN2020/088499 patent/WO2020221360A1/zh active Application Filing
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2018175817A1 (en) * | 2017-03-23 | 2018-09-27 | Intel Corporation | Advanced radio resource management in next-gen multi-hop relaying cellular network |
WO2019042228A1 (zh) * | 2017-08-26 | 2019-03-07 | 华为技术有限公司 | 一种通过中继的通信处理方法和装置 |
Non-Patent Citations (3)
Title |
---|
KDDI CORPORATION: "Consideration on Routing Management Procedure", 3GPP DRAFT; R3-190490_KDDI_IAB_ROUTING_MANAGEMENT,, 15 February 2019 (2019-02-15), XP051604430 * |
KDDI CORPORATION: "Consideration on Routing Management", R3-191410, 3GPP TSG-WG3 MEETING #103-BIS, 29 March 2019 (2019-03-29), XP051694868 * |
NOKIA ET AL.: "IAB OAM Connectivity", R3-192058, 3GPP TSG-WG3 MEETING #103BIS, 15 April 2019 (2019-04-15), XP051712337 * |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US12149981B2 (en) | 2019-08-15 | 2024-11-19 | Samsung Electronics Co., Ltd. | Method and apparatus for mapping backhaul channels in a wireless system |
CN115250508A (zh) * | 2021-04-25 | 2022-10-28 | 大唐移动通信设备有限公司 | Iab网络中数据传输的方法、iab节点及存储介质 |
Also Published As
Publication number | Publication date |
---|---|
CN111865802A (zh) | 2020-10-30 |
CN111865802B (zh) | 2022-03-11 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2020221360A1 (zh) | 一种通信方法及装置 | |
US11510131B2 (en) | Configuration method, data transmission method, and apparatus | |
US11909652B2 (en) | Method, device and storage medium for quality of service (QoS) flow management of time sensitive data for transmission of ethernet packet filter sets | |
US10841789B2 (en) | Method and device for relay transmission | |
US20210378035A1 (en) | Identifier management method and apparatus | |
JP7516578B2 (ja) | Iabネットワーク通信方法及び関連デバイス | |
WO2020164615A1 (zh) | 一种通信方法及相关设备 | |
WO2022082679A1 (zh) | 一种通信方法及相关设备 | |
WO2020192654A1 (zh) | 配置无线链路控制rlc承载的方法和装置 | |
WO2020098747A1 (zh) | 传输路径的配置方法及装置 | |
US20230156833A1 (en) | Packet Forwarding Method, Apparatus, and System | |
CN114071510A (zh) | 一种通信方法及装置 | |
WO2021218938A1 (zh) | 一种资源协调方法及装置 | |
WO2021062803A1 (zh) | 一种数据包传输方法及装置 | |
CN106455086B (zh) | 一种进行数据传输的方法和设备 | |
CN112398959A (zh) | Rlc信道确定方法和装置 | |
CN114365540B (zh) | 通信方法、设备及系统 | |
WO2021026902A1 (zh) | 一种配置方法、通信装置和通信系统 | |
WO2022022639A1 (zh) | 一种通信方法及装置 | |
WO2021204277A1 (zh) | 通信方法、装置及系统 | |
WO2023130989A1 (zh) | 一种通信方法及装置 | |
WO2022156785A1 (zh) | 一种通信方法及通信装置 | |
WO2020216083A1 (zh) | 一种通信方法、通信装置及终端设备 | |
WO2021062717A1 (zh) | 一种缓冲区状态报告传输方法及装置 | |
TWI827186B (zh) | 路由方法和通信裝置 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 20799515 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 20799515 Country of ref document: EP Kind code of ref document: A1 |