WO2019192605A1 - 拓扑信息的管理方法及装置、***、存储介质、电子装置 - Google Patents

拓扑信息的管理方法及装置、***、存储介质、电子装置 Download PDF

Info

Publication number
WO2019192605A1
WO2019192605A1 PCT/CN2019/081542 CN2019081542W WO2019192605A1 WO 2019192605 A1 WO2019192605 A1 WO 2019192605A1 CN 2019081542 W CN2019081542 W CN 2019081542W WO 2019192605 A1 WO2019192605 A1 WO 2019192605A1
Authority
WO
WIPO (PCT)
Prior art keywords
iab node
information
topology management
topology
base station
Prior art date
Application number
PCT/CN2019/081542
Other languages
English (en)
French (fr)
Inventor
邹伟
陈琳
黄莹
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2019192605A1 publication Critical patent/WO2019192605A1/zh

Links

Images

Classifications

    • 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/12—Discovery or management of network topologies

Definitions

  • the present application relates to the field of communications, and in particular, to a method, device, system, storage medium, and electronic device for managing topology information.
  • the fifth-generation mobile communication technology (5G, 5th Generation) under study at the 3rd Generation Partnership Project (3GPP) will achieve greater throughput, more user connections, lower latency, and more High reliability, and lower power consumption (including network side devices and user terminals).
  • 3GPP 3rd Generation Partnership Project
  • IAB Integrated Access and Backhaul
  • the state, and the use of content prediction and caching technology will also increase the fluctuation range of the return link resource demand, which will result in low efficiency of the use of wired backhaul and waste investment costs.
  • For microwave backhaul there is also an increase in hardware cost and an additional spectrum cost (if the unlicensed spectrum is used, the transmission quality is not guaranteed), the antenna height of the transmitting node is relatively low, and the microwave is more easily blocked, resulting in a return chain. Defects such as violent fluctuations in road quality.
  • the use of wireless self-return technology is one of the important technical choices to avoid the above problems and reduce capital expenditure (CAPEX, Capital Expenditure).
  • the self-backhaul technology means that the backhaul link and the access link use the same wireless transmission technology, share the same frequency band, and reuse resources by time division or frequency division.
  • the use of self-backhaul technology in ultra-dense networks has the following advantages:
  • the system can adaptively adjust the resource allocation ratio according to the network load condition and improve the resource use efficiency
  • the joint quality of the wireless self-backhaul can be effectively guaranteed by joint optimization with the access link, which greatly improves the transmission reliability.
  • UDN Ultra-Dense Network
  • the main enhancements are the increase of link capacity and flexible resource allocation and path selection. Therefore, the main research directions include link enhancement of backhaul links and Joint optimization of access links and backhaul links.
  • wireless self-backhaul technology can also be used in scenarios where wired connection deployment costs are high.
  • the 1a) architecture considers that the service flow is relayed by adding a DU with a self-backhaul function based on the separation of a CU (Centralized Unit)/DU (Distributed Unit).
  • 1 is a schematic diagram of a 3GPP reference relay architecture 1a in the related art of the present application.
  • an IAB node serves as a DU to provide access services for local UEs, and each IAB node passes a local user terminal ( MT, Mobile Terminal) is connected to the parent node of the upper level.
  • MT Mobile Terminal
  • the MT shares access bandwidth as an access user of the parent node and other users (UEs) of the parent node. Since the DU and the CU are connected through the F1 interface, a one-hop or multi-hop data bearer needs to be established between the DU of the IAB node and the CU of the IAB Donor to transmit the F1 message. At each hop, the data bearer carries data transmission through the wireless air interface (NR Uu, New Radio Uu) between the MT and the DU. Therefore, for a multi-hop F1 bearer, the intermediate IAB node needs to forward the received F1 message. This forwarding process can be implemented at the intermediate node by the IP layer or the Adapt layer.
  • the Internet Protocol (IP) layer or the Adapt layer may forward the data packet to the next connection according to the target address of the received data packet (such as the target IAB Node ID (ID) or other information).
  • IP Internet Protocol
  • ID target IAB Node ID
  • the IAB Donor is a node with a wired connection, which can contain one DU and one CU, and the Donor base station is also called a parent base station.
  • SDAP Service Data Adaptation Protocol
  • Adapt layer an adaptation layer (Adapt layer) needs to be added to implement the transmission, reception and forwarding of F1 interface data.
  • an IAB node is a node in an IAB network that utilizes a self-backhaul connection to provide remote access.
  • the IAB Donor base station refers to a node in the IAB network that has a wired core network connection, and other IAB nodes access the core network through the Donor base station.
  • the topology of the IAB network may change at any time due to changes in the radio link. How to effectively maintain the topology is a problem that wireless IAB networks must solve.
  • the embodiment of the invention provides a method, a device, a storage medium and an electronic device for managing topology information.
  • a method for managing topology information including: receiving a topology management message; and adjusting a wireless connection of a local first integrated access backhaul node according to the topology management message.
  • a topology information management apparatus including: a receiving module, configured to receive a topology management message; and an adjustment module, configured to adjust a local first integrated access back according to the topology management message Pass the wireless connection of the node.
  • a topology information management system including: a first IAB node, a second IAB node, a donor base station, and a core network, where the first IAB node includes: a receiving module, configured to: Receiving a topology management message; and an adjustment module, configured to adjust a wireless connection of the local first integrated access return node according to the topology management message.
  • a storage medium having stored therein a computer program, wherein the computer program is configured to execute the steps of any one of the method embodiments described above.
  • an electronic device comprising a memory and a processor, wherein the memory stores a computer program, the processor being arranged to run the computer program to perform any of the above The steps in the method embodiments.
  • the IAB node adjusts the local wireless connection according to the topology management message, and solves the technical problem that the IAB node in the related art cannot effectively maintain the topology of the IAB network.
  • FIG. 1 is a schematic diagram of a 3GPP reference relay architecture 1a in the related art of the present application;
  • FIG. 2 is a schematic diagram of an example of a specific protocol stack architecture implemented by an Adapt layer of an intermediate node in the architecture of the related art
  • FIG. 3 is a flowchart of a method for managing topology information according to an embodiment of the present invention.
  • FIG. 4 is a structural block diagram of a topology information management apparatus according to an embodiment of the present invention.
  • FIG. 5 is a structural block diagram of a topology information management system according to an embodiment of the present invention.
  • FIG. 6 is a relay architecture embodiment of a topology management entity provided by the present application in an IAB node and a core network;
  • FIG. 7 is a relay architecture embodiment of an OAM entity in which an topology management entity provided in the present application is located in an IAB node and a core network;
  • FIG. 8 is a relay architecture embodiment of a topology management entity provided by the present application at an IAB node and a Donor base station;
  • FIG. 9 is a functional block diagram embodiment of an IAB node with a topology management entity provided above the adaptation layer provided by the present application;
  • FIG. 10 is a functional block diagram embodiment of an IAB node in which the topology management entity provided in the present application is located in an adaptation layer;
  • FIG. 11 is a functional block diagram embodiment of an IAB donor base station in which the topology management entity provided in the present application is located in an adaptation layer;
  • FIG. 12 is a functional block diagram embodiment of an IAB donor base station with a topology management entity provided above the adaptation layer provided by the present application;
  • FIG. 13 is a functional block diagram embodiment of an IAB Donor base station of a topology management entity provided by the present application in an upper layer of a CU function;
  • FIG. 14 is a functional block diagram embodiment of an IAB Donor base station of a topological management entity provided by the present application in an upper layer of an RRC function in a CU;
  • FIG. 15 is a functional block diagram embodiment of an IAB Donor base station within a RRC function of a topology management entity provided by the present application;
  • topology management message exchanged between topology management entities provided by the present application
  • FIG. 17 is a schematic diagram of a centralized topology management provided by the present application.
  • FIG. 18 is a schematic diagram of a schematic diagram of distributed topology management provided by the present application.
  • the network architecture includes: an IAB node, an IAB donor, and a core network (NGC).
  • the IAB node provides an access service for the local UE as a DU, and each IAB node is connected to the parent node of the upper level through a local user terminal (MT).
  • the MT shares access bandwidth as an access user of the parent node and other users (UEs) of the parent node. Since the DU and the CU are connected through the F1 interface, a one-hop or multi-hop data bearer needs to be established between the DU of the IAB node and the CU of the IAB Donor to transmit the F1 message.
  • the intermediate IAB node needs to forward the received F1 message.
  • This forwarding process can be implemented at the intermediate node by the IP layer or the Adapt layer. Specifically, the IP layer or the Adapt layer may forward the data packet to the next connection according to the destination address of the received data packet (such as the target IAB Node ID) or other information.
  • the IAB Donor is a node with a wired connection that can contain one DU and one CU.
  • FIG. 3 is a flowchart of a method for managing topology information according to an embodiment of the present invention. As shown in FIG. 3, the process includes the following steps. :
  • Step S302 receiving a topology management message.
  • Step S304 adjusting a wireless connection of the local first integrated access backhaul node according to the topology management message.
  • the IAB node adjusts the local wireless connection according to the topology management message, and solves the technical problem that the IAB node in the related art cannot effectively maintain the topology structure of the IAB network.
  • monitoring the first integrated access backhaul IAB node accesses the network through the self-backhaul link, where the network includes: a first IAB node, a donor base station, a core network; and is a first IAB node
  • a radio bearer is configured, wherein the radio bearer is used to deliver a topology management message for the first IAB node.
  • the radio bearer is configured for the IAB node, so that the IAB node can exchange topology management messages with other network elements, perform topology update of the IAB network, and solve related technologies.
  • the technical problem of the IAB node cannot effectively maintain the topology of the IAB network.
  • the topology management message is from at least one of the following: a second IAB node, a Donor base station, a DU of a Donor base station, a CU of a Donor base station, a core network, and an AMF (Access and Mobility Management Function) of the core network.
  • the method further includes: establishing, by the first IAB node, a connection for transmitting the topology management message, where the connection includes at least one of: the first IAB node to the core network Data connection, the first IAB node to the operation and maintenance management OAM functional entity data connection, the first IAB node to the donor base station's radio resource control (RRC, Radio Resoruce Control) signaling connection, the first IAB node to the donor base station wireless a data connection, a wireless data connection established between the first IAB node and the second IAB node, an F1AP (F1 Application Protocol) connection established between the first IAB node and the CU of the Donor base station, and the first IAB node and the core network AMF are established.
  • RRC Radio Resoruce Control
  • F1AP F1 Application Protocol
  • the data connection of the IAB node to the core network includes at least one of the following: an IP connection, a GTP-U (GPRS Tunneling Protocol-User Plance) connection.
  • an IP connection a GTP-U (GPRS Tunneling Protocol-User Plance) connection.
  • GTP-U GPRS Tunneling Protocol-User Plance
  • the wireless data connection established between the first IAB node and the second IAB node includes one of the following: a logical link connection processed by the RLC layer of the radio link control, and a logic of the PDCP layer processing of the RLC layer and the packet data centralized protocol.
  • Link connection a logical link connection processed by the RLC layer of the radio link control, and a logic of the PDCP layer processing of the RLC layer and the packet data centralized protocol.
  • the first IAB node and the second IAB node are adjacent IAB nodes.
  • the solution of the embodiment further includes: the first IAB node and the other network element exchange topology management messages, perform topology control and management, and include one of the following: the first functional entity located at the first IAB node and the donor base station The second functional entity manages the message using the radio bearer interaction topology;
  • the first functional entity located at the first IAB node and the third functional entity located at the core network use the radio bearer to exchange topology management messages;
  • the first functional entity located at the first IAB node and the fourth functional entity located at the second IAB node use the radio bearer to exchange topology management messages.
  • the first functional entity is located at the adaptation layer of the first IAB node, and/or the second functional entity is located at the RRC layer of the donor base station, and/or the second functional entity is located at the DU of the donor base station, and/or The second functional entity is located at the CU of the donor base station, and/or the third functional entity is located in the core network in the OAM or AMF functional entity, and/or the fourth functional entity is located in the adaptation layer of the second IAB node.
  • the second functional entity is located in an adaptation layer of the distribution unit DU of the donor base station.
  • the topology management message carries at least one of the following information: target node address information, source node address information, message length information, channel quality information of one or more wireless links, and establishment information of one or more wireless links.
  • Demolition information of one or more wireless links enabling information of one or more wireless links, setting one or more wireless links as information of the standby wireless link, subsequent transmission indication information of the message, wireless link Subsequent transmission indication information of the information, geographical location information of the local IAB node, neighboring area information of one or more local IAB nodes (neighborhood identity and congestion, and measurement results of neighboring areas (such as carrier frequency, bandwidth, TAI) (Tracking Area Identity), CP (Cyclic Prefix) length, TDD (Time-division Duplex) cell uplink and downlink subframe configuration, AMF list), neighboring area PLMN (Public Land Mobile Network, public land mobile network), next step Information about topology control actions (such as establishing or tearing down a connection, enabling a connection or setting a connection to stand
  • the topology management message includes one or more of the following information fields: source IAB node address, target IAB node address, subsequent transmission indication of the current message, message length, radio link identity, radio link status, wireless chain Subsequent transmission indication of the road status, cell identification of the neighboring area, neighboring area measurement result, PLMN supported by the neighboring area, information of the next topology control action (such as establishing or tearing down a connection, enabling a connection or connecting a connection) Set to standby, etc.; wherein the wireless link status includes at least one of: channel quality of the wireless link, establishment of the wireless link, removal of the wireless link, activation of the wireless link, setting the wireless link to standby The subsequent transmission indication of the radio link status is used to indicate whether the current radio link status needs to be used for subsequent transmission and subsequent transmission; wherein the neighboring area measurement result includes: carrier frequency, bandwidth, tracking area identifier TAI, cyclic prefix CP length, uplink and downlink subframe configuration of the time division duplex TDD cell, AMF
  • the method according to the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course, by hardware, but in many cases, the former is A better implementation.
  • the technical solution of the present application which is essential or contributes to the prior art, may be embodied in the form of a software product stored in a storage medium (such as ROM/RAM, disk,
  • the optical disc includes a number of instructions for causing a terminal device (which may be a cell phone, a computer, a server, or a network device, etc.) to perform the methods of various embodiments of the present application.
  • a device for managing topology information is provided, which is used to implement the foregoing embodiments and preferred embodiments, and details are not described herein.
  • the term "module” may implement a combination of software and/or hardware of a predetermined function.
  • the apparatus described in the following embodiments is preferably implemented in software, hardware, or a combination of software and hardware, is also possible and contemplated.
  • FIG. 4 is a structural block diagram of a topology information management apparatus according to an embodiment of the present invention. As shown in FIG. 4, the apparatus includes:
  • the receiving module 40 is configured to receive a topology management message.
  • the adjusting module 42 is configured to adjust a wireless connection of the local first integrated access backhaul node according to the topology management message.
  • FIG. 5 is a structural block diagram of a topology information management system according to an embodiment of the present invention. As shown in FIG. 5, the method includes: a first IAB node 50, a donor base station 52, a core network 54, a second IAB node 56, and a first IAB node. 50 includes:
  • the receiving module 500 is configured to receive a topology management message.
  • the adjusting module 502 is configured to adjust a wireless connection of the local first integrated access backhaul node according to the topology management message.
  • the donor base station 52 includes: a monitoring module 520, configured to monitor the first integrated access backhaul IAB node to access the network through a self-backhaul link, where the network includes: a first IAB node, a donor base station, and a core network.
  • the configuration module 522 is configured to configure a radio bearer for the first IAB node, where the radio bearer is used to deliver a topology management message to the first IAB node.
  • the first functional entity located at the first IAB node and the second functional entity located at the donor base station use the radio bearer interaction topology management message; or, in the first IAB node
  • the first functional entity located at the first IAB node and the third functional entity located at the core network use the radio bearer to exchange topology management messages; or the first functional entity located at the first IAB node and the second IAB node
  • the fourth functional entity manages the message using the radio bearer interaction topology.
  • each of the above modules may be implemented by software or hardware.
  • the foregoing may be implemented by, but not limited to, the foregoing modules are all located in the same processor; or, the above modules are in any combination.
  • the forms are located in different processors.
  • the topology of the IAB network may change at any time due to changes in the radio link. How to effectively maintain the topology is the program aim of this embodiment.
  • the Donor base station When the IAB node accesses the network through the self-backhaul link, the Donor base station should configure a corresponding one-hop or multi-hop radio bearer to transmit the topology management related message.
  • the functional entity responsible for managing the topology uses the above bearer to perform topology management message interaction, and updates the local topology information and/or routing information according to the information in the message.
  • the foregoing topology management message may be a control PDU (Protocol Data Unit) of the adaptation layer or a newly extended Control PDU of the RLC radio link control layer.
  • the foregoing bearer may be a type of bearer of the following: a data connection from the IAB node to the core network, which may be an IP connection or a GTP-U connection; a data connection of the IAB node to the OAM functional entity; and an RRC of the IAB node to the donor base station Signaling connection; wireless data connection from the IAB node to the donor base station; wireless data connection established between the two IAB nodes.
  • the two wireless data connections established between the two IAB nodes may be logical link connections that are only processed by the RLC, or may be extended by the corresponding PDCP layer.
  • the above IAB node can implement the above data bearer through its connected user equipment MT.
  • the two IAB nodes at the two ends of the bearer may be two adjacent IAB nodes.
  • the functional entity of the IAB node may collect information related to the local topology, and send the information to the peer management entity of the peer end by using the foregoing bearer.
  • the local topology related information may be one or more of the following: geographic location information of the local node, detected neighbor information (specifically including cell identifier, measurement result, PLMN, etc.), the wireless chain of the node
  • the road status update information includes the channel quality of each link, the newly established link, the failed link, the enabled link, and the standby link.
  • the topology management function entity of the IAB node may also receive information about topology control from the peer topology management entity, and perform corresponding topology control actions.
  • the topology control action may be connection establishment or teardown, enable or set to standby, and the like.
  • the topology management function entity may also update the local topology according to the received information.
  • the foregoing topology may be a global topology that reflects the IAB network, or a topology that reflects only a part of the IAB network connection.
  • the topology management function entity may also send topology management information to command the topology management of the peer end. The entity performs a topology control action.
  • the two ends of the bearer are functional entities responsible for topology management, and are respectively located at the IAB node and the donor base station or the IAB node and the core network.
  • the functional entity responsible for topology management of the foregoing IAB node may be located at an adaptation layer of the IAB node.
  • the functional entity responsible for topology management of the Donor base station may be located in an RRC functional entity of the Donor base station; optionally, the functional entity responsible for topology management of the Donor base station may be located in the DU of the Donor base station; optionally, the Donor base station
  • the functional entity responsible for topology management may be the adaptation layer of the DU at the Donor base station.
  • the functional entity responsible for topology management of the core network may be located in an OAM functional entity.
  • the foregoing topology management related message may include one or more of the following information: target node address information, source node address information, message length information, channel quality information of one or more wireless links, one or more Information about the establishment of a wireless link, the removal information of one or more wireless links, the activation information of one or more wireless links, and one or more wireless links as alternate information, messages or wireless link information Subsequent transmission indication information, neighboring area information (specifically including cell identification, measurement result, PLMN, etc.), topology control action information, such as connection establishment or teardown, enabling or setting to standby.
  • the format of the foregoing topology management related message may include one or more of the following information domains: a source IAB node address, a target IAB node address, a subsequent transmission indication of the message, a length, a wireless link identifier, and a wireless The link status, the subsequent transmission indication of the radio link status, the neighboring area information list, the specific cell identifier including one or more neighboring cells, the cell measurement result, the PLMN supported by the cell, and the like.
  • the IAB node address is used to identify different nodes in the IAB network, and the identifier may be uniformly allocated by the network, or may be the ID of the IAB node, or the ID of the DU in the IAB node, or the ID of the Donor base station.
  • the wireless link identifier is used to identify different wireless links in the IAB network, and the identifier may be uniformly allocated by the network, or may be generated in some manner according to the user equipment ID and its logical link ID connected to the IAB node.
  • the wireless link status may include one or more of the channel quality of the wireless link, the establishment, teardown, activation, and provisioning of the wireless link.
  • the wireless link state subsequent transmission indication may indicate information such as whether the wireless link state requires subsequent transmission and the range of subsequent transmissions in the distributed topology management.
  • the above information fields related to the radio link may constitute a radio link information unit.
  • One or more wireless link information elements may be included in a single topology management message.
  • the length information field is used to indicate the length of the topology management message.
  • the length information field may indicate the number of subsequent radio link information units.
  • a unified subsequent transmission indication may be provided for all the wireless links in a topology management message; in this case, a subsequent transmission indication field of the message may be indicated in each message.
  • topology management entity 6 is a relay architecture embodiment of a topology management entity provided by the present application in an IAB node and a core network.
  • the bearer is a data connection from the IAB node to the OAM management entity, and may be an IP connection or a GTP-U connection.
  • the topology management entity performs topology management message interaction through the foregoing bearer, and updates local topology information and/or routing information according to the information in the message.
  • topology management entity 7 is a relay architecture embodiment of an OAM entity in which the topology management entity provided by the present application is located in an IAB node and a core network.
  • the bearer is a data connection from the IAB node to the Donor base station, and may be an IP connection or a GTP-U connection.
  • the topology management entity performs topology management message interaction through the foregoing bearer, and updates local topology information and/or routing information according to the information in the message.
  • the topology management entity 8 is a relay architecture embodiment of a topology management entity provided by the present application at an IAB node and a Donor base station.
  • the bearer is a data connection from the IAB node to the Donor base station, and may be a dedicated data connection, an RRC signaling connection, an IP connection, a GTP-U connection, or a connection established between the DU of the IAB node and the DU of the Donor base station.
  • the topology management entity performs topology management message interaction through the foregoing bearer, and updates local topology information and/or routing information according to the information in the message.
  • FIG. 9 is a functional block diagram embodiment of an IAB node with a topology management entity provided above the adaptation layer provided by the present application.
  • the topology management entity is located on the adaptation layer (Adapt layer) functional entity, and the adaptation layer reports the topology management message to the topology management entity after receiving the topology management message.
  • the topology management message may come from a local DU or from a user terminal (MT, Mobile Terminal) for implementing self-backhaul.
  • FIG. 10 is a functional block diagram embodiment of an IAB node in which the topology management entity provided by the present application is located in an adaptation layer.
  • the topology management entity is located in the adaptation layer (Adapt layer) functional entity, and directly processes the received topology management message as part of the adaptation layer.
  • the topology management message can come from a local DU or from a user terminal for implementing self-backhaul.
  • FIG. 11 is a functional block diagram embodiment of an IAB donor base station in which the topology management entity provided by the present application is located in an adaptation layer.
  • the topology management entity is located in the adaptation layer (Adapt layer) functional entity, and directly processes the received topology management message as part of the adaptation layer.
  • Topology management messages can come from local DUs.
  • FIG. 12 is a functional block diagram embodiment of an IAB donor base station with a topology management entity provided above the adaptation layer provided by the present application.
  • the topology management entity is located on the adaptation layer (Adapt layer) functional entity, and the adaptation layer reports the topology management message to the topology management entity after receiving the topology management message.
  • Topology management messages can come from local DUs.
  • FIG. 13 is a functional block diagram embodiment of an IAB Donor base station of a topology management entity provided by the present application in an upper layer of a CU function.
  • the topology management entity is located on the CU function entity.
  • the adaptation layer After receiving the topology management message, the adaptation layer forwards the topology management message to the CU, and then reports the CU to the topology management entity.
  • Topology management messages can come from local DUs.
  • FIG. 14 is a functional block diagram embodiment of an IAB Donor base station of an upper layer RRC function provided by the topology management entity provided in the present application.
  • the topology management entity is located in the CU function entity and is above the RRC function entity.
  • the adaptation layer forwards the topology management message to the CU, and then the RRC entity in the CU identifies the RRC entity and forwards it to the topology management entity.
  • Topology management messages can come from local DUs.
  • the RRC entity of the Donor base station needs to be able to identify the topology management message on the bearer re-RRC connection and forward it to the topology management entity.
  • the topology management entity is located in the RRC function entity of the CU function entity. After receiving the topology management message, the adaptation layer forwards the topology management message to the CU, and then the RRC entity in the CU identifies and receives the RRC entity. The topology management entity directly processes the topology management messages as part of the RRC. Topology management messages can come from local DUs. Here, the RRC entity of the Donor base station needs to be able to identify the topology management message carried over the RRC connection.
  • topology management message 16 is an embodiment of a topology management message exchanged between topology management entities provided by the present application.
  • the above topology management related message may include one or more of the following information: target node address information, source node address information, message length information, channel quality information of one or more wireless links, and one or more wireless links. Establishment information, removal information of one or more wireless links, activation information of one or more wireless links, setting one or more wireless links as alternate information, subsequent transmission indication of messages or wireless link information information.
  • the format of the foregoing topology management related message may include one or more of the following information domains: a source IAB node address, a target IAB node address, a subsequent transmission indication of the message, a length, a wireless link identifier, and a wireless Link status, subsequent transmission indication of the status of the radio link.
  • the IAB node address is used to identify different nodes in the IAB network, and the identifier may be uniformly allocated by the network, or may be the ID of the IAB node, or the ID of the DU in the IAB node, or the ID of the Donor base station.
  • the wireless link identifier is used to identify different wireless links in the IAB network, and the identifier may be uniformly allocated by the network, or may be generated in some manner according to the user equipment ID and its logical link ID connected to the IAB node.
  • the wireless link status may include one or more of the channel quality of the wireless link, the establishment, teardown, activation, and provisioning of the wireless link.
  • the wireless link state subsequent transmission indication may indicate information such as whether the wireless link state requires subsequent transmission and the range of subsequent transmissions in the distributed topology management.
  • the above information fields related to the radio link may constitute a radio link information unit.
  • One or more wireless link information elements may be included in a single topology management message.
  • the length information field is used to indicate the length of the topology management message.
  • the length information field may indicate the number of subsequent radio link information units.
  • a unified subsequent transmission indication may be provided for all the wireless links in a topology management message; in this case, a subsequent transmission indication field of the message may be indicated in each message.
  • FIG. 17 is a schematic diagram of a centralized topology management diagram provided by the present application.
  • the entity may be located in the IAB Donor base station, the DU of the Donor base station, the CU of the Donor base station, the core network, or the AMF of the core network.
  • the specific centralized topology management may include the following steps:
  • Step 1 The IAB node measures the other IAB nodes/donors in the vicinity, and then sends the topology management message to the centralized topology management entity to report the topology management information, which may include: the geographic location of the IAB node, the currently accessed cell identifier, and Congestion, neighbor identification and congestion, measurement results of neighbors (such as carrier frequency, bandwidth, TAI, CP length, uplink and downlink subframe configuration of TDD cell, AMF list), PLMN of neighboring cell, etc.
  • the IAB node When the IAB node is initially started, after the IAB node is selected as the UE to access the network, the node can report its own IAB node identity and interact with the centralized topology management entity under the control of the parent node or the core network AMF. Report the above information.
  • Step 2 The centralized topology management entity feeds back the topology management indication to the IAB node through the topology management message according to the topology of the current network that it maintains. Specifically, you can select one or more parent IAB nodes/donors for the IAB node, or instruct them to establish a new connection.
  • Step 3 The IAB node performs corresponding topology update according to the topology management indication of the centralized topology management entity. It should be noted that the parent IAB node/donor configured by the centralized topology management entity may be different from the current access zone of the IAB node. If not, the IAB node releases the connection with the previous cell and in turn establishes an RRC connection with the configured parent IAB node/donor.
  • FIG. 18 is a schematic diagram of a schematic diagram of distributed topology management provided by the present application.
  • the specific distributed topology management may include the following steps:
  • Step 1 The IAB node measures the other IAB nodes/donors in the vicinity, and then sends the topology management message to the topology management entity of the neighboring node to report the local topology management information, which may include: the geographic location of the IAB node, and the current access. Cell identification and congestion, neighbor identification and congestion, measurement results for neighbors (such as carrier frequency, bandwidth, TAI, CP length, uplink and downlink subframe configuration of TDD cell, AMF list), PLMN of neighboring cell, etc. .
  • the IAB node When the IAB node is initially started, after selecting an IAB node to access the network as the UE, the node can report its own IAB node identity and manage distributed topology management of other nodes under the control of the parent node or core network AMF. Entities interact to report the above information.
  • Step 2 The distribution topology management entity of each node maintains its local network topology according to the received topology management information of the neighboring nodes, and feeds back the topology management indication to other IAB nodes through the topology management message. Specifically, you can select one or more parent IAB nodes/donors for other IAB nodes, or instruct them to establish a new connection.
  • Step 3 The IAB node performs corresponding topology update according to the topology management indication of the centralized topology management entity. It should be noted that the parent IAB node/donor configured by the topology management entity may be different from the cell currently accessed by the IAB node. If not, the IAB node releases the connection with the previous cell and in turn establishes an RRC connection with the configured parent IAB node/donor.
  • the topology update of the IAB network can be effectively performed.
  • Embodiments of the present invention also provide a storage medium having stored therein a computer program, wherein the computer program is configured to execute the steps of any one of the method embodiments described above.
  • the above storage medium may be configured to store a computer program for performing the following steps:
  • the foregoing storage medium may include, but is not limited to, a USB flash drive, a Read-Only Memory (ROM), and a Random Access Memory (RAM).
  • ROM Read-Only Memory
  • RAM Random Access Memory
  • Embodiments of the present invention also provide an electronic device comprising a memory and a processor having a computer program stored therein, the processor being arranged to execute a computer program to perform the steps of any of the method embodiments described above.
  • the electronic device may further include a transmission device and an input and output device, wherein the transmission device is connected to the processor, and the input and output device is connected to the processor.
  • the foregoing processor may be configured to perform the following steps by using a computer program:
  • modules or steps of the present application can be implemented by a general computing device, which can be concentrated on a single computing device or distributed in a network composed of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein.
  • the steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated as a single integrated circuit module.
  • the application is not limited to any particular combination of hardware and software.

Landscapes

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

Abstract

本申请提供了一种拓扑信息的管理方法及装置、***、存储介质、电子装置，其中，该方法包括：接收拓扑管理消息；根据所述拓扑管理消息调整本地第一综合接入回传节点的无线连接。通过本申请，解决了相关技术中的IAB节点不能有效维护IAB网络的拓扑结构的技术问题。

Description

拓扑信息的管理方法及装置、***、存储介质、电子装置
本申请要求在2018年04月04日提交中国专利局、申请号为201810301935.1的中国专利申请的优先权，该申请的全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域，具体而言，涉及一种拓扑信息的管理方法及装置、***、存储介质、电子装置。
背景技术
本申请发明人在实现本申请所实施技术方案的过程中，至少发现相关技术中存在如下技术问题：
在第三代合作伙伴计划(3GPP，3rd Generation Partnership Project)正在研究的第五代移动通信技术(5G，5th Generation)将实现更大的吞吐量，更多的用户连接，更低时延，更高可靠性，和更低功耗(包括网络侧设备和用户终端)。在3GPP的讨论中，综合接入回传(IAB，Integrated Access and Backhaul)技术作为一个新的研究项目已经立项，其目标是：使一个或多个IAB节点可以作为母节点的用户设备(UE，User Equipment)通过其本地接入资源连接到母节点，并在此基础上形成多跳的无线自回传网络为IAB节点的本地接入UE提供回传连接。
5G超密集组网(UDN，Ultra-Dense Network)部署场景中，需要考虑不同回传技术的适用性。对于有线回传，在大量发送节点(TP，Transmission Point)密集部署的场景下(如密集街区)，考虑到电缆或光纤的部署或租赁成本，站址的选择及维护成本等，可能使有线回传的成本高得难以接受。即便铺设了有线回传，由于密集部署场景下，每个节点服务的用户数少，负载波动大，或由于节能/干扰控制，一些节点会被动态打开或关闭，很多时候回传链路处于空闲状态，而使用内容预测及缓存技术也会增加回传链路资源需求的波动范围，因此会导致有线回传的使用效率低，浪费投资成本。对于微波回传，也存在增加硬件成本，增加额外的频谱成本(如果使用非授权频谱，传输质量得不到保证)，传输节点的天线高度相对较低，微波更容易被遮挡，导致回传链路质量的剧烈 波动等缺陷。
采用无线自回传技术，是避免上述问题、减少资本支出(CAPEX，Capital Expenditure)的重要技术选择之一。自回传技术是指回传链路和接入链路使用相同的无线传输技术，共用同一频带，通过时分或频分方式复用资源。在超密集网络中使用自回传技术具有如下优势：
不需要有线连接，支持无规划或半规划的灵活的传输节点部署，有效降低部署成本；
与接入链路共享频谱和无线传输技术，减少频谱及硬件成本；
通过接入链路与回传链路的联合优化，***可以根据网络负载情况，自适应地调整资源分配比例，提高资源使用效率；
由于使用授权频谱，通过与接入链路的联合优化，无线自回传的链路质量可以得到有效保证，大大提高了传输可靠性。
UDN(Ultra-Dense Network)网络中采用自回传技术，面临的主要增强需求在于链路容量的提升以及灵活的资源分配和路径选择，因此主要的研究方向包括回传链路的链路增强以及接入链路和回传链路的联合优化。
除此之外，无线自回传技术还可以用于有线连接部署成本较大的场景。
RAN3#99会议的WA for IAB Architecture for L2/3 relaying(R3-181502)中提及了五种relay架构。其中1a)架构是考虑在CU(Centralized Unit，集中单元)/DU(Distributed Unit，分布单元)分离的基础上通过增加具有自回传功能的DU来中继业务流。图1是本申请相关技术中3GPP参考中继架构1a的示意图，如图1所示，IAB节点(IAB Node)作为一个DU为本地UE提供接入服务，各个IAB节点通过本地的一个用户终端(MT，Mobile Terminal)和上一级的母节点相连。该MT作为母节点的接入用户和母节点的其他用户(UE)共享接入带宽。由于DU和CU之间是通过F1接口进行联系，所以IAB节点的DU和IAB Donor的CU之间需要建立一个一跳或多跳的数据承载来传输F1消息。在每一跳，该数据承载又是通过MT和DU之间的无线空口(NR Uu，New Radio Uu)承载进行数据传输。所以，对于多跳的F1承载，中间的IAB节点需要对收到的F1消息进行转发。这个转发过程在中间节点可以由IP层或Adapt层实现。具体的，互联网协议(IP，Internet Protocol)层或Adapt层可以根据收到的数据包的目标地址(如目标IAB Node标识(ID，Identity))或其他信息将数据包转发到 下一条的连接中。IAB Donor是具有有线连接的节点，其可以包含一个DU和一个CU，Donor基站也叫母基站。
图2是本申请相关技术的架构中由中间节点的Adapt层实现转发的一个具体的协议栈架构实例示意图。SDAP(业务数据适配协议)是5G中新增加的协议层，在每个IAB节点中，需要增加一个适配层(Adapt层)实现F1接口数据的发送，接收和转发。
综上所述，IAB节点就是IAB网络中利用自回传连接提供远端接入的节点。IAB Donor基站是指IAB网络中具有有线的核心网连接的节点，其他IAB节点通过Donor基站接入核心网。
在多跳IAB网络中，由于无线链路的变化，IAB网络的拓扑结构随时可能发生改变。如何有效的维护的拓扑结构是无线IAB网络必须解决的一个问题。
针对相关技术中存在的上述问题，目前尚未发现有效的解决方案。
发明内容
本发明实施例提供了一种拓扑信息的管理方法及装置、***、存储介质、电子装置。
根据本发明的一个实施例，提供了一种拓扑信息的管理方法，包括：接收拓扑管理消息；根据所述拓扑管理消息调整本地第一综合接入回传节点的无线连接。
根据本发明的另一个实施例，提供了一种拓扑信息的管理装置，包括：接收模块，用于接收拓扑管理消息；调整模块，用于根据所述拓扑管理消息调整本地第一综合接入回传节点的无线连接。
根据本发明的另一个实施例，提供了一种拓扑信息的管理***，包括：第一IAB节点，第二IAB节点，donor基站，核心网，所述第一IAB节点包括：接收模块，用于接收拓扑管理消息；调整模块，用于根据所述拓扑管理消息调整本地第一综合接入回传节点的无线连接。
根据本发明的又一个实施例，还提供了一种存储介质，所述存储介质中存储有计算机程序，其中，所述计算机程序被设置为运行时执行上述任一项方法实施例中的步骤。
根据本发明的又一个实施例，还提供了一种电子装置，包括存储器和处理 器，所述存储器中存储有计算机程序，所述处理器被设置为运行所述计算机程序以执行上述任一项方法实施例中的步骤。
通过本申请，IAB节点根据拓扑管理消息调整本地的无线连接，解决了相关技术中的IAB节点不能有效维护IAB网络的拓扑结构的技术问题。
附图说明
此处所说明的附图用来提供对本申请的进一步理解，构成本申请的一部分，本申请的示意性实施例及其说明用于解释本申请，并不构成对本申请的不当限定。在附图中：
图1是本申请相关技术中3GPP参考中继架构1a的示意图；
图2是本申请相关技术的架构中由中间节点的Adapt层实现转发的一个具体的协议栈架构实例示意图；
图3是根据本发明实施例的拓扑信息的管理方法的流程图；
图4是根据本发明实施例的拓扑信息的管理装置的结构框图；
图5是根据本发明实施例的拓扑信息的管理***的结构框图；
图6是本申请提供的拓扑管理实***于IAB节点和核心网的中继架构实施例；
图7是本申请提供的拓扑管理实***于IAB节点和核心网中的OAM实体的中继架构实施例；
图8是本申请提供的拓扑管理实***于IAB节点和Donor基站的中继架构实施例；
图9是本申请提供的拓扑管理实***于适配层之上的IAB节点的功能框图实施例；
图10是本申请提供的拓扑管理实***于适配层中的IAB节点的功能框图实施例；
图11是本申请提供的拓扑管理实***于适配层中的IAB donor基站的功能框图实施例；
图12是本申请提供的拓扑管理实***于适配层之上的IAB donor基站的功能框图实施例；
图13是本申请提供的拓扑管理实***于CU功能上层的IAB Donor基站的 功能框图实施例；
图14是本申请提供的拓扑管理实***于CU内RRC功能上层的IAB Donor基站的功能框图实施例；
图15是本申请提供的拓扑管理实***于CU内RRC功能内部的IAB Donor基站的功能框图实施例；
图16是本申请提供的拓扑管理实体之间交换的拓扑管理消息的实施例；
图17是本申请提供的集中式拓扑管理示意图实施例；
图18是本申请提供的分布式拓扑管理示意图实施例。
具体实施方式
下文中将参考附图并结合实施例来详细说明本申请。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互组合。
需要说明的是，本申请的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。
实施例1
本申请实施例可以运行于图1所示的网络架构上，如图1所示，该网络架构包括：IAB节点(IAB Node)、donor基站(IAB donor)、核心网(NGC)。IAB节点(IAB Node)作为一个DU为本地UE提供接入服务，各个IAB节点通过本地的一个用户终端(MT)和上一级的母节点相连。该MT作为母节点的接入用户和母节点的其他用户(UE)共享接入带宽。由于DU和CU之间是通过F1接口进行联系，所以IAB节点的DU和IAB Donor的CU之间需要建立一个一跳或多跳的数据承载来传输F1消息。在每一跳，该数据承载又是通过MT和DU之间的无线NR Uu承载进行数据传输。所以，对于多跳的F1承载，中间的IAB节点需要对收到的F1消息进行转发。这个转发过程在中间节点可以由IP层或Adapt层实现。具体的，IP层或Adapt层可以根据收到的数据包的目标地址(如目标IAB Node ID)或其他信息将数据包转发到下一条的连接中。IAB Donor是具有有线连接的节点，其可以包含一个DU和一个CU。
在本实施例中提供了一种运行于上述网络架构的拓扑信息的管理方法，图3是根据本发明实施例的拓扑信息的管理方法的流程图，如图3所示，该流程包括如下步骤：
步骤S302，接收拓扑管理消息；
步骤S304，根据拓扑管理消息调整本地第一综合接入回传节点的无线连接。
通过上述步骤，IAB节点根据拓扑管理消息调整本地的无线连接，解决了相关技术中的IAB节点不能有效维护IAB网络的拓扑结构的技术问题。
在donor基站侧，执行以下步骤：监测第一综合接入回传IAB节点通过自回传链路接入网络，其中，网络包括：第一IAB节点，donor基站，核心网；为第一IAB节点配置无线承载，其中，无线承载用于为第一IAB节点传递拓扑管理消息。
通过上述步骤，在IAB节点通过自回传链路接入到网络时，为其配置无线承载，从而该IAB节点可以与其他网元交互拓扑管理消息，进行IAB网络的拓扑更新，解决了相关技术中的IAB节点不能有效维护IAB网络的拓扑结构的技术问题。
可选地，拓扑管理消息来自于以下至少之一：第二IAB节点，Donor基站，Donor基站的DU，Donor基站的CU，核心网，核心网的AMF(Access and Mobility Management Function)。
可选地，在第一IAB节点接收拓扑管理消息之前，方法还包括：为第一IAB节点建立用于传递拓扑管理消息的连接，其中，连接包括以下至少之一：第一IAB节点到核心网的数据连接，第一IAB节点到操作维护管理OAM功能实体的数据连接，第一IAB节点到donor基站的无线资源控制(RRC，Radio Resoruce Control)信令连接，第一IAB节点到donor基站的无线数据连接，第一IAB节点与第二IAB节点之间建立的无线数据连接，第一IAB节点与Donor基站的CU之间建立的F1AP(F1Application Protocol)连接，第一IAB节点与核心网AMF建立的NG-C(NG-Control Plane)连接，第一IAB节点与第二IAB节点之间建立的Xn连接，第一IAB节点到donor基站的Xn连接。
可选地，IAB节点到核心网的数据连接包括以下至少之一：IP连接，GTP-U(用户层面的GPRS隧道协议，GPRS Tunnelling Protocol-User Plance)连接。
可选地，第一IAB节点与第二IAB节点之间建立的无线数据连接包括以下之一：无线链路控制RLC层处理的逻辑链路连接，RLC层和分组数据集中协议PDCP层处理的逻辑链路连接。
可选地，第一IAB节点与第二IAB节点是相邻的IAB节点。
可选地，本实施例的方案还包括：第一IAB节点与其他网元交互拓扑管理消息，进行拓扑控制和管理，包括以下之一：位于第一IAB节点的第一功能实体与位于donor基站的第二功能实体使用无线承载交互拓扑管理消息；
位于第一IAB节点的第一功能实体与位于核心网的第三功能实体使用无线承载交互拓扑管理消息；
位于第一IAB节点的第一功能实体与位于第二IAB节点的第四功能实体使用无线承载交互拓扑管理消息。
可选地，第一功能实***于第一IAB节点的适配层，和/或，第二功能实***于donor基站的RRC层，和/或，第二功能实***于donor基站的DU，和/或，第二功能实***于donor基站的CU，和/或，第三功能实***于核心网位于OAM或AMF功能实体中，和/或，第四功能实***于第二IAB节点的适配层。可选的，第二功能实***于donor基站的分布单元DU的适配层。
可选地，拓扑管理消息携带以下信息至少之一：目标节点地址信息，源节点地址信息，消息长度信息，一条或多条无线链路的信道质量信息，一条或多条无线链路的建立信息，一条或多条无线链路的拆除信息，一条或多条无线链路的启用信息，把一条或多条无线链路设置为备用无线链路的信息，消息的后续传输指示信息，无线链路信息的后续传输指示信息，本端IAB节点的地理位置信息，一个或多个本端IAB节点的邻区信息(邻区标识和拥塞情况，对邻区的测量结果(如载频，带宽，TAI(Tracking Area Identity)，CP(Cyclic Prefix)长度，TDD(Time-division Duplex)小区的上下行子帧配置，AMF列表)，邻区的PLMN(Public Land Mobile Network，公共陆地移动网络)，下一步拓扑控制动作的信息(如建立或拆除某个连接，启用某个连接或将某个连接设为备用等)。
可选地，拓扑管理消息包含下列信息域的一项或多项：源IAB节点地址，目标IAB节点地址，当前消息的后续传输指示，消息长度，无线链路标识，无线链路状态，无线链路状态的后续传输指示，邻区的小区标识，邻区测量结果，邻区所支持的PLMN，下一步拓扑控制动作的信息(如建立或拆除某个连接，启用某个连接或将某个连接设为备用等)；其中，无线链路状态包含以下至少之一：无线链路的信道质量，无线链路的建立，无线链路的拆除，无线链路的启用，将无线链路设置为备用；无线链路状态的后续传输指示用于指示当前无 线链路状态是否需要进行后续传输以及后续传输的范围；其中，所述邻区测量结果包含：载频，带宽，跟踪区标识TAI，循环前缀CP长度，时分双工TDD小区的上下行子帧配置，AMF列表。。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到根据上述实施例的方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端设备(可以是手机，计算机，服务器，或者网络设备等)执行本申请各个实施例的方法。
实施例2
在本实施例中还提供了一种拓扑信息的管理装置，***，用于实现上述实施例及优选实施方式，已经进行过说明的不再赘述。如以下所使用的，术语“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的装置较佳地以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。
图4是根据本发明实施例的拓扑信息的管理装置的结构框图，如图4所示，该装置包括：
接收模块40，用于接收拓扑管理消息；
调整模块42，用于根据拓扑管理消息调整本地第一综合接入回传节点的无线连接。
图5是根据本发明实施例的拓扑信息的管理***的结构框图，如图5所示，包括：第一IAB节点50，donor基站52，核心网54，第二IAB节点56，第一IAB节点50包括：
接收模块500，用于接收拓扑管理消息；
调整模块502，用于根据拓扑管理消息调整本地第一综合接入回传节点的无线连接。
可选的，donor基站52包括：监测模块520，用于监测第一综合接入回传IAB节点通过自回传链路接入网络，其中，网络包括：第一IAB节点，donor基站，核心网；配置模块522，用于为第一IAB节点配置无线承载，其中，无线承载 用于为第一IAB节点传递拓扑管理消息。
可选的，在为第一IAB节点配置无线承载之后，位于第一IAB节点的第一功能实体与位于donor基站的第二功能实体使用无线承载交互拓扑管理消息；或，在为第一IAB节点配置无线承载之后，位于第一IAB节点的第一功能实体与位于核心网的第三功能实体使用无线承载交互拓扑管理消息；或，位于第一IAB节点的第一功能实体与位于第二IAB节点的第四功能实体使用无线承载交互拓扑管理消息。
需要说明的是，上述各个模块是可以通过软件或硬件来实现的，对于后者，可以通过以下方式实现，但不限于此：上述模块均位于同一处理器中；或者，上述各个模块以任意组合的形式分别位于不同的处理器中。
实施例3
本实施例用于结合具体的实施方式对本申请的方案进行详细说明：
在多跳IAB网络中，由于无线链路的变化，IAB网络的拓扑结构随时可能发生改变。如何有效的维护的拓扑结构是本实施例的方案宗旨。
当IAB节点通过自回传链路接入网络时，Donor基站应该为其配置相应的一跳或多跳的无线承载来传递拓扑管理相关的消息。负责管理拓扑的功能实体使用上述承载进行拓扑管理消息的交互，并根据消息内的信息更新本地的拓扑信息和/或路由信息。可选的，上述拓扑管理消息可以是适配层的控制PDU(协议数据单元)或RLC无线链路控制)层新扩展的控制PDU。
可选的，上述承载可以是以下的某类承载：IAB节点到核心网的数据连接，可以是IP连接或GTP-U连接；IAB节点到OAM功能实体的数据连接；IAB节点到donor基站的RRC信令连接；IAB节点到donor基站的无线数据连接；在两个IAB节点之间建立的无线数据连接。
其中，两个在两个IAB节点之间建立的无线数据连接可以是只经过RLC处理的逻辑链路连接，也可以为其扩展相应的PDCP层处理。上述IAB节点可以通过其相连的用户设备MT实现上述数据承载。可选的，上述承载两端的两个IAB节点可以是相邻的两个IAB节点。
可选的，IAB节点的功能实体可以收集本地拓扑相关的信息，并通过上述承载发送给对端的拓扑管理实体。可选的，本地拓扑相关信息可以是以下的一项或多项：本节点的地理位置信息，检测到的邻区信息(具体的包含小区标识， 测量结果，PLMN等)，本节点的无线链路状况更新信息，包括各链路的信道质量，新建立的链路，故障的链路，启用的链路，设为备用的链路等。
可选的，IAB节点的拓扑管理功能实体也可以接收来自对端拓扑管理实体的拓扑控制的信息，并进行相应的拓扑控制动作。可选的，拓扑控制动作可以是连接建立或拆除，启用或设为备用等。
可选的，拓扑管理功能实体还可以根据收到的信息更新本地的拓扑结构。可选的，上述拓扑结构可以是反映IAB网络全局的拓扑结构，也可以是只反映部分IAB网络连接的拓扑结构；可选的，上述拓扑管理功能实体还可以发送拓扑管理信息命令对端的拓扑管理实体进行某个拓扑控制动作。
可选的，上述承载两端是负责拓扑管理的功能实体，分别位于IAB节点和donor基站或IAB节点和核心网。可选的，上述IAB节点的负责拓扑管理的功能实体可以位于该IAB节点的适配层。可选的，Donor基站的负责拓扑管理的功能实体可以位于Donor基站的RRC功能实体；可选的，Donor基站的负责拓扑管理的功能实体可以位于Donor基站的DU中；可选的，Donor基站的负责拓扑管理的功能实体可以是在Donor基站的DU的适配层。可选的，核心网的负责拓扑管理的功能实体可以位于OAM功能实体中。
可选的，上述拓扑管理相关的消息可以包含下列信息的一项或多项：目标节点地址信息，源节点地址信息，消息长度信息，一条或多条无线链路的信道质量信息，一条或多条无线链路的建立信息，一条或多条无线链路的拆除信息，一条或多条无线链路的启用信息，把一条或多条无线链路设为备用的信息，消息或无线链路信息的后续传输指示信息，邻区信息(具体的包含小区标识，测量结果，PLMN等)，拓扑控制动作信息，如连接建立或拆除，启用或设为备用等。
可选的，上述拓扑管理相关的消息的格式中可以包含下列信息域的一项或多项：源IAB节点地址，目标IAB节点地址，本消息的后续传输指示，长度，无线链路标识，无线链路状态，无线链路状态的后续传输指示，邻区信息列表，具体的包含一个或多个邻区的小区标识，小区测量结果，小区所支持的PLMN等。
其中，IAB节点地址用于标识IAB网络中的不同节点，其标识可以由网络统一分配，也可以是IAB节点的ID，或IAB节点中DU的ID，或者Donor基 站的ID。无线链路标识用于标识IAB网络中不同的无线链路，其标识可以由网络统一分配，也可以根据IAB节点相连的用户设备ID和其逻辑链路ID以某种方式生成。无线链路状态可以包含无线链路的信道质量，无线链路的建立，拆除，启用和设为备用等信息中的一项或多项。无线链路状态后续传输指示可以在分布式拓扑管理中指示该无线链路状态是否需要进行后续传输以及后续传输的范围等信息。上述无线链路相关的信息域可以组成一个无线链路信息单元。单个拓扑管理消息中可以包含一个或多个无线链路信息单元。长度信息域用于指示拓扑管理消息的长度；可选的，上述长度信息域可以指示后续无线链路信息单元的数量。可选的，可以为某个拓扑管理消息中的所有无线链路提供统一的后续传输指示；这时，每个消息中可以有一个本消息的后续传输指示域对其进行指示。
图6是本申请提供的拓扑管理实***于IAB节点和核心网的中继架构实施例。在每个IAB节点和核心网中都有一个拓扑管理(Topology Mgmt)实体，他们通过一跳或多跳的承载相连。该承载为IAB节点到OAM管理实体的数据连接，可以是IP连接或GTP-U连接。拓扑管理实体通过上述承载进行拓扑管理消息的交互，并根据消息内的信息更新本地的拓扑信息和/或路由信息。
图7是本申请提供的拓扑管理实***于IAB节点和核心网中的OAM实体的中继架构实施例。在每个IAB节点和核心网的OAM实体中都有一个拓扑管理实体，他们通过一跳或多跳的承载相连。该承载为IAB节点到Donor基站的数据连接，可以是IP连接或GTP-U连接。拓扑管理实体通过上述承载进行拓扑管理消息的交互，并根据消息内的信息更新本地的拓扑信息和/或路由信息。
图8是本申请提供的拓扑管理实***于IAB节点和Donor基站的中继架构实施例。在每个IAB节点和Donor基站中都有一个拓扑管理实体，他们通过一跳或多跳的承载相连。该承载为IAB节点到Donor基站的数据连接，可以是专用数据连接，RRC信令连接，IP连接，GTP-U连接，或者IAB节点的DU和Donor基站的DU之间建立的连接。拓扑管理实体通过上述承载进行拓扑管理消息的交互，并根据消息内的信息更新本地的拓扑信息和/或路由信息。
图9是本申请提供的拓扑管理实***于适配层之上的IAB节点的功能框图实施例。拓扑管理实***于适配层(Adapt层)功能实体之上，适配层在收到拓扑管理消息后将其上报给拓扑管理实体。拓扑管理消息可以来自本地的DU，或 者来自于用于实现自回传的用户终端(MT，Mobile Terminal)。
图10是本申请提供的拓扑管理实***于适配层中的IAB节点的功能框图实施例。拓扑管理实***于适配层(Adapt层)功能实体之中，作为适配层的一部分直接处理收到的拓扑管理消息。拓扑管理消息可以来自本地的DU，或者来自于用于实现自回传的用户终端。
图11是本申请提供的拓扑管理实***于适配层中的IAB donor基站的功能框图实施例。拓扑管理实***于适配层(Adapt层)功能实体之中，作为适配层的一部分直接处理收到的拓扑管理消息。拓扑管理消息可以来自本地的DU。
图12是本申请提供的拓扑管理实***于适配层之上的IAB donor基站的功能框图实施例。拓扑管理实***于适配层(Adapt层)功能实体之上，适配层在收到拓扑管理消息后将其上报给拓扑管理实体。拓扑管理消息可以来自本地的DU。
图13是本申请提供的拓扑管理实***于CU功能上层的IAB Donor基站的功能框图实施例。拓扑管理实***于CU功能实体之上，适配层在收到拓扑管理消息后将其转发给CU，再由CU上报给拓扑管理实体。拓扑管理消息可以来自本地的DU。
图14是本申请提供的拓扑管理实***于CU内RRC功能上层的IAB Donor基站的功能框图实施例。拓扑管理实***于CU功能实体之中，RRC功能实体之上，适配层在收到拓扑管理消息后将其转发给CU，再由CU中的RRC实体进行识别后转发给拓扑管理实体。拓扑管理消息可以来自本地的DU。这里，Donor基站的RRC实体需要能够识别出承载再RRC连接之上的拓扑管理消息，并转发给拓扑管理实体。
图15是本申请提供的拓扑管理实***于CU内RRC功能内部的IAB Donor基站的功能框图实施例。拓扑管理实***于CU功能实体的RRC功能实体中，适配层在收到拓扑管理消息后将其转发给CU，再由CU中的RRC实体进行识别和接收。拓扑管理实体作为RRC的一部分直接对拓扑管理消息进行处理。拓扑管理消息可以来自本地的DU。这里，Donor基站的RRC实体需要能够识别出承载在RRC连接之上的拓扑管理消息。
图16是本申请提供的拓扑管理实体之间交换的拓扑管理消息的实施例。上述拓扑管理相关的消息可以包含下列信息的一项或多项：目标节点地址信息， 源节点地址信息，消息长度信息，一条或多条无线链路的信道质量信息，一条或多条无线链路的建立信息，一条或多条无线链路的拆除信息，一条或多条无线链路的启用信息，把一条或多条无线链路设为备用的信息，消息或无线链路信息的后续传输指示信息。
可选的，上述拓扑管理相关的消息的格式中可以包含下列信息域的一项或多项：源IAB节点地址，目标IAB节点地址，本消息的后续传输指示，长度，无线链路标识，无线链路状态，无线链路状态的后续传输指示。
其中，IAB节点地址用于标识IAB网络中的不同节点，其标识可以由网络统一分配，也可以是IAB节点的ID，或IAB节点中DU的ID，或者Donor基站的ID。无线链路标识用于标识IAB网络中不同的无线链路，其标识可以由网络统一分配，也可以根据IAB节点相连的用户设备ID和其逻辑链路ID以某种方式生成。无线链路状态可以包含无线链路的信道质量，无线链路的建立，拆除，启用和设为备用等信息中的一项或多项。无线链路状态后续传输指示可以在分布式拓扑管理中指示该无线链路状态是否需要进行后续传输以及后续传输的范围等信息。上述无线链路相关的信息域可以组成一个无线链路信息单元。单个拓扑管理消息中可以包含一个或多个无线链路信息单元。长度信息域用于指示拓扑管理消息的长度；可选的，上述长度信息域可以指示后续无线链路信息单元的数量。可选的，可以为某个拓扑管理消息中的所有无线链路提供统一的后续传输指示；这时，每个消息中可以有一个本消息的后续传输指示域对其进行指示。
图17是本申请提供的集中式拓扑管理示意图实施例。存在一个集中拓扑管理实体对IAB网络的拓扑进行维护，该实体可以位于IAB Donor基站，Donor基站的DU，Donor基站的CU，核心网，或核心网的AMF中。具体的集中式拓扑管理可以包括如下步骤：
步骤1：IAB node对周围的其他IAB node/donor进行测量，然后向集中拓扑管理实体发送拓扑管理消息报告各项拓扑管理信息，具体的可以包含：IAB node地理位置，当前接入的小区标识和拥塞情况，邻区标识和拥塞情况，对邻区的测量结果(如载频，带宽，TAI，CP长度，TDD小区的上下行子帧配置，AMF列表)，邻区的PLMN，等。当IAB节点初始启动时，以UE的身份选择一个IAB node接入到网络后，该节点可以报告自己的IAB节点身份，并在母节 点或核心网AMF的控制下和集中拓扑管理实体进行交互，报告上述信息。
步骤2：集中拓扑管理实体根据其维护的当前网络的拓扑情况，通过拓扑管理消息反馈拓扑管理指示给IAB节点。具体的，可以为IAB node选择合适的一个或多个parent IAB node/donor，或者指示其建立新的连接。
步骤3：IAB节点根据集中拓扑管理实体的拓扑管理指示进行相应的拓扑更新。需要注意的是，集中拓扑管理实体配置的parent IAB node/donor可能与IAB node当前接入的小区不同。如果不同，则IAB node释放与先前小区的连接，转而与所配置的parent IAB node/donor建立RRC连接。
图18是本申请提供的分布式拓扑管理示意图实施例。IAB网络的每个节点，包括IAB节点和IAB Donor基站都存在一个分布式的拓扑管理实体。具体的分布式拓扑管理可以包括如下步骤：
步骤1：IAB node对周围的其他IAB node/donor进行测量，然后向相邻节点的拓扑管理实体发送拓扑管理消息报告本地的拓扑管理信息，具体的可以包含：IAB node地理位置，当前接入的小区标识和拥塞情况，邻区标识和拥塞情况，对邻区的测量结果(如载频，带宽，TAI，CP长度，TDD小区的上下行子帧配置，AMF列表)，邻区的PLMN，等。当IAB节点初始启动时，以UE的身份选择一个IAB node接入到网络后，该节点可以报告自己的IAB节点身份，并在母节点或核心网AMF的控制下和其他节点的分布式拓扑管理实体进行交互，报告上述信息。
步骤2：各节点的分布拓扑管理实体根据收到的相邻节点的拓扑管理信息维护其本地的网络拓扑，并通过拓扑管理消息反馈拓扑管理指示给其他IAB节点。具体的，可以为其他IAB node选择合适的一个或多个parent IAB node/donor，或者指示其建立新的连接。
步骤3：IAB节点根据集中拓扑管理实体的拓扑管理指示进行相应的拓扑更新。需要注意的是，拓扑管理实体配置的parent IAB node/donor可能与IAB node当前接入的小区不同。如果不同，则IAB node释放与先前小区的连接，转而与所配置的parent IAB node/donor建立RRC连接。
采用本实施例的方案，能够有效的进行IAB网络的拓扑更新。
实施例4
本发明的实施例还提供了一种存储介质，该存储介质中存储有计算机程序， 其中，该计算机程序被设置为运行时执行上述任一项方法实施例中的步骤。
可选地，在本实施例中，上述存储介质可以被设置为存储用于执行以下步骤的计算机程序：
S1，接收拓扑管理消息；
S2，根据所述拓扑管理消息调整本地第一综合接入回传节点的无线连接。
可选地，在本实施例中，上述存储介质可以包括但不限于：U盘、只读存储器(Read-Only Memory，简称为ROM)、随机存取存储器(Random Access Memory，简称为RAM)、移动硬盘、磁碟或者光盘等各种可以存储计算机程序的介质。
本发明的实施例还提供了一种电子装置，包括存储器和处理器，该存储器中存储有计算机程序，该处理器被设置为运行计算机程序以执行上述任一项方法实施例中的步骤。
可选地，上述电子装置还可以包括传输设备以及输入输出设备，其中，该传输设备和上述处理器连接，该输入输出设备和上述处理器连接。
可选地，在本实施例中，上述处理器可以被设置为通过计算机程序执行以下步骤：
S1，接收拓扑管理消息；
S2，根据所述拓扑管理消息调整本地第一综合接入回传节点的无线连接。
可选地，本实施例中的具体示例可以参考上述实施例及可选实施方式中所描述的示例，本实施例在此不再赘述。
显然，本领域的技术人员应该明白，上述的本申请的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，可选地，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本申请不限制于任何特定的硬件和软件结合。
以上所述仅为本申请的优选实施例而已，并不用于限制本申请，对于本领域的技术人员来说，本申请可以有各种更改和变化。凡在本申请的原则之内，所作的任何修改、等同替换、改进等，均应包含在本申请的保护范围之内。

Claims (16)

  1. 一种拓扑信息的管理方法，包括：
    接收拓扑管理消息；
    根据所述拓扑管理消息调整本地第一综合接入回传IAB节点的无线连接。
  2. 根据权利要求1所述的方法，其中，所述拓扑管理消息来自于以下至少之一：第二IAB节点，母Donor基站，所述Donor基站的分布单元DU，所述Donor基站的集中单元CU，核心网，所述核心网的接入和移动管理功能AMF。
  3. 根据权利要求1或2所述的方法，在第一IAB节点接收所述拓扑管理消息之前，所述方法还包括：
    为所述第一IAB节点建立用于传递所述拓扑管理消息的连接，其中，所述连接包括以下至少之一：
    所述第一IAB节点到核心网的数据连接，所述第一IAB节点到操作维护管理OAM功能实体的数据连接，所述第一IAB节点到donor基站的无线资源控制RRC信令连接，所述第一IAB节点到donor基站的无线数据连接，所述第一IAB节点与第二IAB节点之间建立的无线数据连接，所述第一IAB节点与Donor基站的CU之间建立的F1AP连接，所述第一IAB节点与核心网AMF建立的NG-C连接，所述第一IAB节点与第二IAB节点之间建立的Xn连接，所述第一IAB节点到donor基站的的Xn连接。
  4. 根据权利要求3所述的方法，其中，所述IAB节点到核心网的数据连接包括以下至少之一：IP连接，GTP-U连接。
  5. 根据权利要求3所述的方法，其中，所述第一IAB节点与第二IAB节点之间建立的无线数据连接包括以下之一：无线链路控制RLC层处理的逻辑链路连接，RLC层和分组数据集中协议PDCP层处理的逻辑链路连接。
  6. 根据权利要求3所述的方法，其中，所述第一IAB节点与所述第二IAB节点是相邻的IAB节点。
  7. 根据权利要求1所述的方法，所述方法还包括以下之一：
    位于所述第一IAB节点的第一功能实体与位于donor基站的第二功能实体使用无线承载交互所述拓扑管理消息；
    位于所述第一IAB节点的第一功能实体与位于核心网的第三功能实体使用无线承载交互所述拓扑管理消息；
    位于所述第一IAB节点的第一功能实体与位于第二IAB节点的第四功能实 体使用无线承载交互所述拓扑管理消息。
  8. 根据权利要求7所述的方法，其中，所述第一功能实***于所述第一IAB节点的适配层，和/或，所述第二功能实***于所述donor基站的RRC层，和/或，所述第二功能实***于所述donor基站的DU，和/或，所述第二功能实***于所述donor基站的CU，和/或，所述第三功能实***于所述核心网位于OAM或AFM功能实体中，和/或，所述第四功能实***于所述第二IAB节点的适配层。
  9. 根据权利要求8所述的方法，其中，所述第二功能实***于所述donor基站的分布单元DU的适配层。
  10. 根据权利要求1所述的方法，其中，所述拓扑管理消息携带以下信息至少之一：
    目标节点地址信息，源节点地址信息，消息长度信息，一条或多条无线链路的信道质量信息，一条或多条无线链路的建立信息，一条或多条无线链路的拆除信息，一条或多条无线链路的启用信息，把一条或多条无线链路设置为备用无线链路的信息，消息的后续传输指示信息，无线链路信息的后续传输指示信息，本端IAB节点的地理位置信息，一个或多个本端IAB节点的邻区信息，下一步拓扑控制动作的信息。
  11. 根据权利要求1所述的方法，其中，所述拓扑管理消息包含下列信息域的一项或多项：
    源IAB节点地址，目标IAB节点地址，当前消息的后续传输指示，消息长度，无线链路标识，无线链路状态，无线链路状态的后续传输指示，邻区的小区标识，邻区测量结果，邻区所支持的PLMN，下一步拓扑控制动作的信息；
    其中，所述无线链路状态包含以下至少之一：无线链路的信道质量，无线链路的建立，无线链路的拆除，无线链路的启用，将无线链路设置为备用；所述无线链路状态的后续传输指示用于指示当前无线链路状态是否需要进行后续传输以及后续传输的范围；
    其中，所述邻区测量结果包含：载频，带宽，跟踪区标识TAI，循环前缀CP长度，时分双工TDD小区的上下行子帧配置，AMF列表。
  12. 一种拓扑信息的管理装置，包括：
    接收模块，用于接收拓扑管理消息；
    调整模块，用于根据所述拓扑管理消息调整本地综合接入回传节点的无线连接。
  13. 一种拓扑信息的管理***，包括：第一IAB节点，第二IAB节点，donor基站，核心网，所述第一IAB节点包括：
    接收模块，用于接收拓扑管理消息；
    调整模块，用于根据所述拓扑管理消息调整本地第一综合接入回传节点的无线连接。
  14. 根据权利要求13所述的***，
    在为所述第一IAB节点配置无线承载之后，位于所述第一IAB节点的第一功能实体与位于所述donor基站的第二功能实体使用所述无线承载交互所述拓扑管理消息；或，
    在为所述第一IAB节点配置无线承载之后，位于所述第一IAB节点的第一功能实体与位于所述核心网的第三功能实体使用所述无线承载交互所述拓扑管理消息；或，
    位于所述第一IAB节点的第一功能实体与位于第二IAB节点的第四功能实体使用所述无线承载交互所述拓扑管理消息。
  15. 一种存储介质，所述存储介质中存储有计算机程序，其中，所述计算机程序被设置为运行时执行所述权利要求1至11任一项中所述的方法。
  16. 一种电子装置，包括存储器和处理器，所述存储器中存储有计算机程序，所述处理器被设置为运行所述计算机程序以执行所述权利要求1至11任一项中所述的方法。
PCT/CN2019/081542 2018-04-04 2019-04-04 拓扑信息的管理方法及装置、***、存储介质、电子装置 WO2019192605A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810301935.1A CN110351109B (zh) 2018-04-04 2018-04-04 拓扑信息的管理方法及装置、***、存储介质、电子装置
CN201810301935.1 2018-04-04

Publications (1)

Publication Number Publication Date
WO2019192605A1 true WO2019192605A1 (zh) 2019-10-10

Family

ID=68100032

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/081542 WO2019192605A1 (zh) 2018-04-04 2019-04-04 拓扑信息的管理方法及装置、***、存储介质、电子装置

Country Status (2)

Country Link
CN (1) CN110351109B (zh)
WO (1) WO2019192605A1 (zh)

Cited By (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113133040A (zh) * 2021-05-12 2021-07-16 江苏亨鑫众联通信技术有限公司 一种问题物理网口定位方法、装置及可读存储介质
US20210274425A1 (en) * 2018-07-31 2021-09-02 Asustek Computer Inc. Method and apparatus of updating routing table of an iab (integrated access backhaul) node in a wireless communication system
US20210378044A1 (en) * 2019-02-15 2021-12-02 Huawei Technologies Co., Ltd. Method for controlling wireless backhaul link and apparatus
CN114071617A (zh) * 2020-08-07 2022-02-18 大唐移动通信设备有限公司 Iab节点组切换中的信息传输方法、装置、网络设备及***
WO2022047805A1 (en) * 2020-09-07 2022-03-10 Nokia Shanghai Bell Co., Ltd. Methods, apparatuses and computer readable media for integrated access and backhaul communication
CN114365540A (zh) * 2019-12-31 2022-04-15 华为技术有限公司 通信方法、设备及***
CN114586425A (zh) * 2019-10-18 2022-06-03 高通股份有限公司 集成接入回程(iab)节点定位
CN114762372A (zh) * 2019-12-13 2022-07-15 华为技术有限公司 通信方法、装置及***
CN115022932A (zh) * 2022-06-02 2022-09-06 成都中科微信息技术研究院有限公司 一种提高nr***小区节能关闭时终端业务可靠性的方法及nr***
CN115150965A (zh) * 2021-03-31 2022-10-04 维沃移动通信有限公司 数据调度方法、装置及设备

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112954805B (zh) * 2019-12-11 2023-09-08 ***通信有限公司研究院 一种资源配置方法、上报方法及设备
EP4099762A4 (en) * 2020-02-28 2023-01-18 Huawei Technologies Co., Ltd. COMMUNICATION METHOD AND COMMUNICATION DEVICE
CN111400640B (zh) * 2020-04-10 2023-09-22 中国铁塔股份有限公司 一种站址全息信息管理***、构建方法及构建装置
CN114095948A (zh) * 2020-07-30 2022-02-25 华为技术有限公司 信息传输的方法、装置和***
CN116456352A (zh) * 2022-01-05 2023-07-18 华为技术有限公司 通信方法及通信装置
CN116996436A (zh) * 2022-04-25 2023-11-03 华为技术有限公司 通信方法及装置、存储介质、程序产品
CN115996404B (zh) * 2023-03-24 2023-05-30 广州世炬网络科技有限公司 节点链路动态调整方法及装置

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101500270A (zh) * 2008-02-02 2009-08-05 华为技术有限公司 一种负荷均衡的方法和装置
CN101820355A (zh) * 2010-01-20 2010-09-01 瑞斯康达科技发展股份有限公司 一种获取网络拓扑的方法和网元

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106031219B (zh) * 2014-02-17 2020-01-14 瑞典爱立信有限公司 无线回程链路的处理
US10136359B2 (en) * 2015-06-30 2018-11-20 Qualcomm Incorporated Traffic flow migration in backhaul networks
CN106572480B (zh) * 2015-10-10 2019-08-30 电信科学技术研究院 回传网络的管理方法、接入网管理实体、设备及无线小站

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101500270A (zh) * 2008-02-02 2009-08-05 华为技术有限公司 一种负荷均衡的方法和装置
CN101820355A (zh) * 2010-01-20 2010-09-01 瑞斯康达科技发展股份有限公司 一种获取网络拓扑的方法和网元

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
AT &T: "Discussion on NSA/SA support for IAB architectures", 3GPP TSG-RAN WG3 #99 R3-181346, 2 March 2018 (2018-03-02), XP051401784 *
QUALCOMM INC.: "IAB - Control-plane Aspects", 3GPP TSG-RAN WG2 NR AD HOC 1801 R2-1800414, 26 January 2018 (2018-01-26), XP051385719 *
QUALCOMM INC.: "IAB Topology and Route Management", 3GPP TSG-RAN WG3 MEETING #99 R3-181080, 2 March 2018 (2018-03-02), XP051401414 *

Cited By (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210274425A1 (en) * 2018-07-31 2021-09-02 Asustek Computer Inc. Method and apparatus of updating routing table of an iab (integrated access backhaul) node in a wireless communication system
US20210378044A1 (en) * 2019-02-15 2021-12-02 Huawei Technologies Co., Ltd. Method for controlling wireless backhaul link and apparatus
CN114586425A (zh) * 2019-10-18 2022-06-03 高通股份有限公司 集成接入回程(iab)节点定位
CN114762372A (zh) * 2019-12-13 2022-07-15 华为技术有限公司 通信方法、装置及***
CN114365540B (zh) * 2019-12-31 2023-11-17 华为技术有限公司 通信方法、设备及***
CN114365540A (zh) * 2019-12-31 2022-04-15 华为技术有限公司 通信方法、设备及***
CN114071617A (zh) * 2020-08-07 2022-02-18 大唐移动通信设备有限公司 Iab节点组切换中的信息传输方法、装置、网络设备及***
WO2022047805A1 (en) * 2020-09-07 2022-03-10 Nokia Shanghai Bell Co., Ltd. Methods, apparatuses and computer readable media for integrated access and backhaul communication
CN115150965A (zh) * 2021-03-31 2022-10-04 维沃移动通信有限公司 数据调度方法、装置及设备
CN115150965B (zh) * 2021-03-31 2023-06-23 维沃移动通信有限公司 数据调度方法、装置及设备
CN113133040B (zh) * 2021-05-12 2022-08-19 江苏亨鑫众联通信技术有限公司 一种问题物理网口定位方法、装置及可读存储介质
CN113133040A (zh) * 2021-05-12 2021-07-16 江苏亨鑫众联通信技术有限公司 一种问题物理网口定位方法、装置及可读存储介质
CN115022932A (zh) * 2022-06-02 2022-09-06 成都中科微信息技术研究院有限公司 一种提高nr***小区节能关闭时终端业务可靠性的方法及nr***

Also Published As

Publication number Publication date
CN110351109B (zh) 2022-04-29
CN110351109A (zh) 2019-10-18

Similar Documents

Publication Publication Date Title
WO2019192605A1 (zh) 拓扑信息的管理方法及装置、***、存储介质、电子装置
US11647426B2 (en) Method and apparatus for processing IAB node information in IAB network
US10390348B2 (en) System and method for an agile wireless access network
CN112042259B (zh) 用于在无线通信***中执行通信的方法和装置
US10075895B2 (en) Various routing architectures for dynamic multi-hop backhauling cellular network and various methods useful in conjunction therewith
US7623863B2 (en) System and method for adjusting connection parameters in a wireless network
KR102350433B1 (ko) 연합 x2 게이트웨이
US9801215B2 (en) Apparatus and methods for cellular network communication based on plural mobile cores
WO2021027860A1 (zh) 路由方法、bsr的生成方法、装置和存储介质
WO2019080800A1 (zh) 一种信息传输方法和设备
WO2019100882A1 (zh) 一种会话处理的方法、装置及***
KR20130064746A (ko) 애드 혹 네트워크가 가능한 방법 및 장치
WO2016161900A1 (zh) 一种进行数据传输的方法和设备
KR101229163B1 (ko) 중계 데이터 경로 아키텍처를 형성하는 방법, 사용자 평면 데이터 경로 시스템 및 중계 데이터 경로 아키텍처를 형성하는 시스템
US9668244B2 (en) Radio resource management method, macro base station, and low-power node
CN109076639A (zh) 信息传输装置、方法以及通信***
JP7099556B2 (ja) 無線バックホールを確保する方法、子基地局、親基地局、並びに子基地局及び親基地局における方法
WO2019245547A1 (en) A method to support topology discovery for integrated access and backhaul topology management and routing
WO2010105410A1 (zh) 一种建立无线承载的方法、装置及***
CN115699877A (zh) 无线通信***中向终端提供本地数据网络信息的方法及装置
WO2019163645A1 (ja) 中継通信が行われるセルラ通信ネットワークのための制御装置、基地局装置、端末装置、それらの制御方法、及びプログラム
WO2022082690A1 (zh) 群组切换的方法、装置和***
US20180213465A1 (en) Sdn controlled overlay network
WO2019212546A1 (en) Self-backhaul with enhanced signaling
WO2023016634A1 (en) Relay extension in cellular network

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: 19781315

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 04/02/2021)

122 Ep: pct application non-entry in european phase

Ref document number: 19781315

Country of ref document: EP

Kind code of ref document: A1