WO2021027501A1 - 连接建立方法及装置、链路状态的通知方法及装置、接口建立方法及装置、信息传输方法及装置、集合接入回传节点、集中单元、系统、存储介质 - Google Patents
连接建立方法及装置、链路状态的通知方法及装置、接口建立方法及装置、信息传输方法及装置、集合接入回传节点、集中单元、系统、存储介质 Download PDFInfo
- Publication number
- WO2021027501A1 WO2021027501A1 PCT/CN2020/103176 CN2020103176W WO2021027501A1 WO 2021027501 A1 WO2021027501 A1 WO 2021027501A1 CN 2020103176 W CN2020103176 W CN 2020103176W WO 2021027501 A1 WO2021027501 A1 WO 2021027501A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- information
- node
- iab
- iab node
- link
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 116
- 230000005540 biological transmission Effects 0.000 title claims abstract description 25
- 238000003860 storage Methods 0.000 title claims abstract description 10
- 238000004891 communication Methods 0.000 claims description 88
- 230000004044 response Effects 0.000 claims description 49
- 230000008859 change Effects 0.000 claims description 18
- 238000013507 mapping Methods 0.000 claims description 14
- 238000013508 migration Methods 0.000 claims description 14
- 230000005012 migration Effects 0.000 claims description 14
- 238000004590 computer program Methods 0.000 claims description 13
- 238000009826 distribution Methods 0.000 claims description 7
- 230000006978 adaptation Effects 0.000 claims description 6
- 238000010586 diagram Methods 0.000 description 34
- 230000008569 process Effects 0.000 description 26
- 230000006870 function Effects 0.000 description 6
- 238000012545 processing Methods 0.000 description 5
- 238000005516 engineering process Methods 0.000 description 4
- 230000000694 effects Effects 0.000 description 2
- 238000012423 maintenance Methods 0.000 description 2
- 239000013256 coordination polymer Substances 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000002360 preparation method Methods 0.000 description 1
- 230000011664 signaling Effects 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/11—Allocation or use of connection identifiers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/0005—Control or signalling for completing the hand-off
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/0005—Control or signalling for completing the hand-off
- H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
- H04W36/0019—Control or signalling for completing the hand-off for data sessions of end-to-end connection adapted for mobile IP [MIP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/0005—Control or signalling for completing the hand-off
- H04W36/0055—Transmission or use of information for re-establishing the radio link
- H04W36/0064—Transmission or use of information for re-establishing the radio link of control information between different access points
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/18—Management of setup rejection or failure
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/19—Connection re-establishment
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W84/00—Network topologies
- H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
- H04W84/04—Large scale networks; Deep hierarchical networks
- H04W84/042—Public Land Mobile systems, e.g. cellular systems
- H04W84/047—Public Land Mobile systems, e.g. cellular systems using dedicated repeater stations
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
- H04W88/08—Access point devices
- H04W88/085—Access point devices with remote components
Definitions
- This application relates to the field of communications, such as a connection establishment method and device, link state notification method and device, interface establishment method and device, information transmission method and device, collective access backhaul node, centralized unit, system, storage medium.
- IAB Integrated Access and Backhaul
- 5G fifth generation of mobile communication technology
- the goal is to make one or more IAB nodes use the local mobile terminal (MT, Mobile Terminal) function part to connect to the parent node through the New Radio (NR), and form a multi-hop wireless self-return on this basis.
- MT local mobile terminal
- NR New Radio
- Each IAB node includes a distributed unit (DU, Distributed Unit) functional part and an MT functional part.
- DU Distributed Unit
- the DU is used to serve the user equipment (UE, User Equipment) of the node and the MT of the next hop node, and establish a radio link layer control (RLC, Radio Link Control) connection with it;
- RLC Radio Link Control
- the function of the MT is equivalent to a UE , Used to access the parent node of the previous hop through the Un interface of NR and establish an RLC connection with it. Therefore, different IAB nodes can use the wireless access capability of the local MT to access the parent node of the previous hop, and the parent node can then be connected to the previous hop node, until finally connected to the donor next generation NodeB, donor gNB).
- the donor gNB includes a host CU (donor Centralized Unit, donor CU) and multiple host DU (donor DU), and each donor DU is connected to the donor CU in a wired manner.
- the donor CU and the donor DU, as well as the donor CU and the DU of each IAB node are connected through an enhanced F1 interface.
- connection establishment method including:
- the embodiment of the present application also provides a method for notifying the link status, including:
- the first communication node sends link state information to a second communication node, where the second communication node is a child node of the first communication node;
- the link state information includes at least one of the following: identification information of the CU connected by the first communication node, change information of the CU connected by the first communication node, and IP address of the CU connected by the first communication node, The first communication node link relocation indication, and the first communication node link re-establishment indication.
- the embodiment of the present application also provides an interface establishment method, including:
- the interface establishment response message includes the re-allocated DU identifier.
- the embodiments of the present application also provide an information transmission method, including:
- the handover response message carries at least one of the address information of the first CU and the identifier of the IAB DU.
- the embodiment of the present application also provides another information transmission method, including:
- the embodiment of the present application also provides another interface establishment method, including:
- an interface establishment failure message is sent to the IAB node, and the cause value in the interface establishment failure message is unknown or the DU identifier is assigned Or, sending an interface setup response message to the IAB node, where the interface setup response message contains the DU identifier that is reassigned.
- connection establishment device including:
- the obtaining module is used to obtain the address information of the first CU
- the connection establishment module is configured to establish a connection with the first CU according to the address information of the first CU.
- the embodiment of the present application also provides a link state notification device, which is applied to the first communication node, and includes:
- a link state information sending module configured to send link state information to a second communication node; wherein, the second communication node is a child node of the first communication node;
- the link state information includes at least one of the following: identification information of the CU connected by the first communication node, change information of the CU connected by the first communication node, and IP address of the CU connected by the first communication node, The first communication node link relocation indication, and the first communication node link re-establishment indication.
- the embodiment of the present application also provides an interface establishment device, including:
- the request sending module is used to send an interface establishment request message to the first CU;
- the response receiving module is configured to receive an interface establishment failure message sent by the first CU, where the cause value in the interface establishment failure message is unknown or the DU identifier has been assigned; or to receive an interface establishment response message sent by the first CU ,
- the interface establishment response message includes the re-allocated DU identifier.
- the embodiment of the present application also provides an information transmission device, including:
- a handover request sending module configured to send a handover request message to the first CU, where the handover request message carries information of the IAB node;
- the handover response receiving module is configured to receive a handover response message sent by the first CU, where the handover response message carries at least one of the address information of the first CU and the identifier of the IAB DU.
- the embodiment of the present application also provides another information transmission device, including:
- the identification or address sending module is used to send the identification information or address information of the first CU to the IAB node.
- the embodiment of the present application also provides another interface establishment device, including:
- a connection establishment receiving module configured to receive an interface establishment request message from the IAB node
- the connection establishment feedback module is configured to send an interface establishment failure message to the IAB node when the DU identifier of the IAB node conflicts with other DU identifiers that have a connection relationship, and the cause value in the interface establishment failure message It is unknown or the DU identifier has been allocated; or, an interface establishment response message is sent to the IAB node, and the interface establishment response message contains the re-allocated DU identifier.
- the embodiment of the present application also provides an IAB node, the IAB node includes: a processor and a memory;
- the memory is used to store instructions
- the processor is configured to read the instruction to execute any one of the connection establishment method, the link state notification method, or the first interface establishment method described above.
- An embodiment of the present application also provides a CU, where the CU includes a processor and a memory;
- the memory is used to store instructions
- the processor is configured to read the instruction to execute the method described in any one of the foregoing information transmission method or the second interface establishment method.
- the embodiment of the present application also provides a communication system, including the above-mentioned IAB node and the above-mentioned CU.
- the embodiments of the present application also provide a storage medium, where the storage medium stores a computer program, and when the computer program is executed by a processor, any one of the methods in the embodiments of the present application is implemented.
- connection establishment method provided by the embodiment of the application can be used to solve the problem of connecting to the new donor CU when an IAB node switches to a new donor CU by obtaining the address information of the first CU and establishing a connection with the first CU according to the address information The service continuity of the child IAB node under the IAB node.
- FIG. 1 is a schematic diagram 1 of the implementation process of a connection establishment method according to an embodiment of the application
- FIG. 2 is a schematic diagram 2 of the implementation process of a connection establishment method according to an embodiment of the application
- FIG. 3 is a schematic diagram 1 of the implementation process of an interface establishment method according to an embodiment of the application.
- FIG. 4 is a schematic diagram of an implementation process of an information transmission method according to an embodiment of the application.
- FIG. 5 is a second schematic diagram of the implementation process of an interface establishment method according to an embodiment of the application.
- FIG. 6 is a schematic diagram of the implementation process of Embodiment 1 of this application.
- FIG. 7 is a schematic structural diagram of a connection establishment apparatus according to an embodiment of the application.
- FIG. 8 is a first structural diagram of an interface establishment device according to an embodiment of the application.
- FIG. 9 is a schematic structural diagram of an information transmission device according to an embodiment of the application.
- FIG. 10 is a second structural diagram of an interface establishment apparatus according to an embodiment of the application.
- FIG. 11 is a schematic diagram of the structure of an IAB node for connection establishment or interface establishment according to an embodiment of the application;
- FIG. 12 is a schematic diagram of a CU structure for information transmission or interface establishment according to an embodiment of the application.
- FIG. 13 is a first structural diagram of a communication system according to an embodiment of this application.
- FIG. 14 is a second structural diagram of a communication system according to an embodiment of this application.
- FIG. 1 is a schematic diagram 1 of the implementation process of a method for establishing a connection according to an embodiment of the application, including:
- Step S11 Obtain the address information of the first CU.
- Step S12 Establish a connection with the first CU according to the address information of the first CU.
- the foregoing first CU may be a target donor CU, and after establishing a connection with the first CU, an F1 interface setup request (F1 Setup Request) may be sent to the first CU.
- the execution subject of a connection establishment method in the embodiment of the present application may be an IAB node, especially a migrating IAB node (migrating IAB node) and a downstream IAB node to which it is connected, or an IAB node performing RRC reconstruction And the connected downstream IAB node (downstream IAB node).
- downstream (downstream) can refer to the direction away from the IAB-donor in the multi-hop backhaul.
- the step S11 includes: receiving the identification information of the first CU; searching the mapping table of the CU identification information and the CU address information according to the identification information of the first CU to obtain the address information of the first CU.
- the mapping relationship table between the CU identification information and the CU address information may be pre-stored, or obtained through the network, or configured through operation and maintenance management (OAM, Operation Administration and Maintenance).
- OAM operation and maintenance management
- the identification information of the first CU may be carried in an adaptation layer (adapter layer) message, and the adaptation layer message comes from an upper IAB node.
- adaptation layer adapter layer
- the upper IAB node includes: the parent IAB node that directly provides the service or all IAB nodes that participate in forwarding data to the first CU.
- the identification information of the first CU may be carried in a radio resource control (RRC, Radio Resource Control) reconfiguration (Reconfiguration) message, and the RRC reconfiguration message comes from the first CU.
- RRC Radio Resource Control
- Reconfiguration Radio Resource Control
- the foregoing RRC reconfiguration message may include a cell identity (CellIdentity) and a physical cell identity (PhysCellId), and the cell identity (CellIdentity) may include identification information of the first CU.
- the step S11 includes: receiving the address information of the first CU from the second CU.
- the address information of the first CU may be carried in the F1 message or the RRC reconfiguration message.
- the above-mentioned second CU may be the source donor CU.
- FIG. 2 is a schematic diagram 2 of the implementation process of a connection establishment method according to an embodiment of the application. As shown in FIG. 2, in an implementation manner, before establishing a connection with the first CU in step S12, it may further include:
- Step S21 Receive link connection success indication information from the upper-layer IAB node; where the link connection success indication information includes at least one of the following: identification information of the first CU, cell identification, CU change identification, and The Internet Protocol (IP) address of the CU, the link migration success indication, the link reestablishment success indication, the identifier of the IAB node for link migration, and the identifier of the IAB node for link reconstruction.
- the link connection success indication information includes at least one of the following: identification information of the first CU, cell identification, CU change identification, and The Internet Protocol (IP) address of the CU, the link migration success indication, the link reestablishment success indication, the identifier of the IAB node for link migration, and the identifier of the IAB node for link reconstruction.
- IP Internet Protocol
- the step S11 includes: receiving the address information of the first CU from the first CU.
- the address information of the first CU may be carried in the RRC reconfiguration message.
- An embodiment of the present application also proposes a link state notification method, including: a first communication node sends link state information to a second communication node, where the second communication node is a child node of the first communication node .
- the link state information includes at least one of the following: identification information of the CU connected by the first communication node, change information of the CU connected by the first communication node, and IP address of the CU connected by the first communication node, The first communication node link relocation indication, and the first communication node link re-establishment indication.
- the foregoing first communication node and second communication node are IAB nodes.
- the first communication node may send link state information to the second communication node when performing link migration; or, the first communication node may send link state information to the second communication node when performing RRC reconstruction.
- the link relocation indication of the first communication node includes at least one of the following: a link relocation start indication, a link relocation success indication, and a link relocation failure indication.
- FIG. 3 is a schematic diagram 1 of the implementation process of an interface establishment method according to an embodiment of the application, including:
- Step S31 Send an interface establishment request message to the first CU.
- Step S32 Receive an interface establishment failure message sent by the first CU, where the cause value in the interface establishment failure message is unknown or the DU identifier has been assigned; or, receive an interface establishment response message sent by the first CU, so The interface establishment response message contains the re-allocated DU identifier.
- Fig. 4 is a schematic diagram of the implementation process of an information transmission method according to an embodiment of the application, including:
- Step S41 Send a handover request message to the first CU, where the handover request message carries the information of the IAB node.
- Step S42 Receive a handover response message sent by the first CU, where the handover response message carries at least one of the address information of the first CU and the identifier of the IAB DU.
- the information transmission method proposed in this embodiment can be applied to the source donor CU.
- the information of the IAB node includes: the identifier of the IAB node, the context information of the backhaul channel of the IAB node, the context information of the UE served by the IAB node, and At least one item of context information of the downlink IAB node of the IAB node.
- an information transmission method proposed in an embodiment of the present application may further include:
- Step S43 Send at least one of the address information of the first CU and the identifier of the IAB DU to the IAB node.
- At least one of the address information of the first CU and the identifier of the IAB DU is carried in an RRC reconfiguration message or an F1 message.
- the embodiment of the present application also proposes another information transmission method, including: sending the identification information or address information of the first CU to the IAB node.
- the information transmission method proposed in this embodiment can be applied to the target donor CU.
- the identification information or address information of the first CU may be carried in the RRC reconfiguration message.
- the RRC reconfiguration message includes a cell identifier and a physical cell identifier (PhysCellId), and the cell identifier carries identification information of the first CU.
- CellId physical cell identifier
- FIG. 5 is a schematic diagram of the second implementation process of an interface establishment method according to an embodiment of the application, including:
- S51 Receive an interface establishment request message from the IAB node.
- IAB-node3 is a child node of IAB-node1.
- the source donor CU needs to send the context information of IAB-node1 to the target donor CU.
- FIG. 6 is a schematic diagram of the implementation process of Embodiment 1 of this application, including:
- Step S61 The source donor CU sends a handover request message to the target donor CU, where the handover request message carries the information of the migrated IAB-node1.
- the information of IAB-node1 may include: identification information of IAB-node1, context information of the backhaul channel of IAB-node1, context information of UEs served by IAB-node1, and IAB-node1 At least one item of context information of the downstream IAB node (for example, IAB-node 3).
- Step S62 The target donor CU sends a handover response message to the source donor CU, where the handover response message carries at least one of the address information of the target donor CU and the identifier of the IAB DU.
- the identifier of the IAB DU includes at least one of the following: the DU identifier of the migration node (for example, IAB-node1), and the DU identifier of the downstream node of the migration node (for example, IAB-node3).
- this embodiment solves the problem of how IAB-node1 obtains the IP address of the target donor CU, and if the migrated IAB node continues to serve the downstream IAB node, then its downstream IAB-node (downstream IAB-node) ) How to get the IP address of the target donor CU.
- IAB-node3 is a child node of IAB-node1.
- IAB-node 3 For the downstream IAB node (ie, IAB-node 3), although its parent IAB node (parent IAB-node), ie IAB-node 1, has not changed, the donor CU has changed. Therefore, it is necessary to notify IAB-node that the donor CU has changed.
- IAB-node3 needs to obtain the IP address of the target donor CU.
- This embodiment proposes the following ways for the downlink IAB node to obtain the IP address of the target donor CU:
- Each IAB node (including the migrated IAB node and its downstream IAB node) can pre-configure a mapping table from CU Id to CU IP address, or download a mapping table from CU Id to CU IP address through the network side, or through OAM Configure a mapping table from CU Id to CU IP address.
- the IAB node only needs to obtain the gNB Id of the target donor CU (ie, the CU Id of the target donor CU) to look up the above mapping table to obtain the IP address of the target donor CU.
- the IP address can be a transport layer address (Transport Layer Address).
- the IAB node can obtain the new air interface cell global identifier (NCGI, NR Cell Global Identifier) of the target donor CU, and obtain the CU Id of the target donor CU according to the NCGI.
- NCGI new air interface cell global identifier
- the CUId of the target donor CU can be obtained during the handover process of the MT.
- the migrated IAB node directly passes the adapter layer after the handover is completed.
- the message informs the lower-layer IAB node, and the lower-layer IAB node continues to inform its lower-layer IAB node.
- the adapter layer message includes at least one of the following: identification information of the target, cell identification, CU change identification, IP address of the first CU, link migration success indication, etc.
- the target donor CU informs IAB-node3 through RRC signaling (for example, an RRC reconfiguration message) that the migration of the DU without changing the CU has occurred.
- RRC reconfiguration message carries a cell identity (CellIdentity) and a physical cell identity (PhysCellId), and the CellIdentity is used to indicate the CUId of the target donor CU (for example, the target cell gNBid). Because the donor CU changes, the CellIdentity will also change; but because the DU has not changed, the PhysCellId may not change.
- the RRC reconfiguration message may also contain other information.
- the IAB MT or the UE can determine that the CU changes but the DU does not change. There is no need to re-execute the cell access process, but it needs to receive configuration information updates later. Then, the downlink IAB node (such as IAB-node3 in this embodiment) can look up the above mapping table, learn the IP address of the target donor CU, establish a TNL connection with the target donor CU, and then initiate an F1 connection establishment process to the target donor CU.
- the downlink IAB node such as IAB-node3 in this embodiment
- Method 2 The source donor CU sends the IP address of the target donor CU to the downstream IAB node. This step should be performed before the source donor CU sends a handover command to the migrated IAB node.
- Method 2 can have the following two forms:
- Method 2a The source donor CU sends the IP address of the target donor CU to the DU part of the downstream IAB node through the F1 interface.
- Manner 2b The source donor CU sends the IP address of the target donor CU to the MT part of the downstream IAB node through an RRC message.
- the source donor CU needs to obtain the IP address of the target donor CU, and the IP address of the target donor CU can be obtained by the following methods: obtain the IP address of the target donor CU during the handover preparation process; or pre-configure a CUId to CU IP address mapping table; or download a CU Id to CU IP address mapping table through the network side; or configure a CU Id to CU IP address mapping table through OAM.
- the source donor CU sends an RRC reconfiguration message to the MT of the IAB node (such as IAB-node1 in this embodiment).
- the RRC reconfiguration message may contain the IP address of the target donor CU and other information , Such as CellIdentity and PhysCellId.
- the source donor CU sends an F1 message to the DU of the IAB node (such as IAB-node1 in this embodiment).
- the F1 message may contain the IP address of the target donor CU, which is used to indicate the release of the DU of the downstream IAB node and the source donor The F1 connection of the CU and the establishment of the F1 connection with the target donor CU.
- the source donor CU decides which downstream IAB nodes need to switch to the target donor CU.
- the source donor CU sends an RRC reconfiguration message to the MT of the downstream IAB node (such as IAB-node3 in this embodiment).
- the RRC reconfiguration message may include the IP address of the target donor CU and other information, such as CellIdentity and PhysCellId .
- the source donor CU sends an F1 message to the DU of the downstream IAB node (such as IAB-node3 in this embodiment).
- the F1 message may contain the IP address of the target donor CU, which is used to indicate the release and source of the DU of the downstream IAB node.
- the F1 connection of the donor CU and the F1 connection of the target donor CU are established.
- the downstream IAB node that receives the above information cannot immediately initiate a new F1 connection establishment process.
- the downstream IAB node (such as IAB-node3 in this embodiment) receives the above information, it does not immediately initiate the F1 connection establishment process, but waits for the parent IAB node (such as IAB-node1 in this embodiment) to switch successfully Then release the F1 connection with the source donor CU, and establish the F1 connection with the target donor CU.
- the migrated IAB node After the migrated IAB node completes the handover, it needs to send an instruction message to IAB-node3. After receiving the instruction message, IAB-node3 will start to perform the handover process of not changing the DU but changing the CU, and establish a new F1 connection.
- the migrated IAB node For the migrated IAB node, it is a relatively simple way to directly carry the IP address of the target donor CU in the RRC reconfiguration message.
- the above F1 connection may refer to an F1 access protocol (AP, Application Protocol) connection.
- AP Application Protocol
- Manner 3 The target donor CU sends its own IP address to the MT part of the downlink IAB node through an RRC message.
- the target donor CU For the migrated IAB, after the MT part of the IAB establishes an RRC connection with the target donor CU, the target donor CU sends the IP address to the MT of the IAB through the RRC reconfiguration message, and then the MT of the IAB informs the DU part to obtain the target donor The IP address of the CU.
- the target donor CU can determine that the donor CU has changed, and therefore initiates the F1 connection establishment process with the target donor CU.
- the F1 connection here can be an F1-C connection.
- the donor CU can send an RRC reconfiguration message to notify updated information, for example, carrying the target cell id.
- the CellIdentity can be changed after the DU changes the CU, but the physical cell identifier (PCI, Physical Cell Identifier, PhysCellId) of the cell is not changed.
- the access is still the same DU, there is no need to perform a random access process to find a new cell, and the resources of the physical layer and the media access control (MAC, Media Access Control) layer will not change.
- the configuration information related to the Packet Data Convergence Protocol (PDCP) and the configuration information related to the Service Data Adaptation Protocol (SDAP) will also change.
- the donor CU can pass The RRC reconfiguration message informs the UE of updated cell configuration information (new CellIdentity and unchanged PCI) and bearer configuration information, where the bearer configuration information may include the above-mentioned PDCP-related configuration information and SDAP-related configuration information.
- the updated cell configuration information may also include Public Land Mobile Network (PLMN) information, Tracking Area Code (TAC), and uplink and downlink time slots (slot) configuration information.
- PLMN Public Land Mobile Network
- TAC Tracking Area Code
- slot uplink and downlink time slots
- the gNB-DU ID is unique within a gNB-CU, but if the CU is replaced, there is a possibility of conflict. Therefore, when the DU changes the CU, when the CU receives the DU initiates a connection establishment request with the CU, if it finds that the current gNB-DU ID conflicts with the gNB-DU ID of other connections, it can send an F1 connection establishment failure message (F1 SETUP FAILURE), and set the value of the cause (Cause) to unknown (Unknown) or DU identification (already allocated gNB-DU ID). Alternatively, an F1 connection establishment response message (F1 SETUP RESPONSE) may be sent, and the F1 SETUP RESPONSE may carry the new DU identifier allocated by the CU for the gNB-DU.
- F1 connection establishment failure message F1 SETUP FAILURE
- F1 SETUP RESPONSE F1 connection establishment response message
- gNB-CU UE F1AP ID gNB-CU-CP UE E1AP ID
- gNB-CU-UP UE E1AP ID are also handled in the same way.
- the gNB-DU ID is unique within a gNB-CU, but if the CU is replaced, if the previously allocated DU ID continues to be used, there is a possibility of conflict. Therefore, after the DU changes to the CU, in order to avoid the possibility of conflict, the target CU can allocate a new DU identifier to the DU in advance.
- the embodiments of this application can adopt at least the following two solutions:
- Step 1 The source CU sends a handover request message to the target CU, where the handover request message carries the information of the IAB node.
- Step 2 The source CU receives the handover response message sent by the target CU, where the handover response message carries the identification information of the IAB DU.
- the source CU sends the identification information of the IAB DU to the IAB node, and then the IAB node can use the identification information to establish an F1 connection with the target CU.
- the source CU can also use a similar method to transfer the identification information of the downstream IAB DU. Sent to the downstream IAB node, and then the downstream IAB node can use the identification information to establish an F1 connection with the target CU.
- the target donor CU sends the IAB DU identification information to the MT of the IAB node through the RRC reconfiguration message, and then the MT of the IAB node informs the DU part Then, the IAB node can use the identification information to establish an F1 connection with the target CU.
- the above method can also be used for the downstream IAB of the migrated IAB (such as IAB-node3 in this embodiment).
- the target donor CU sends the identification information of the downlink IAB DU to the MT of the downlink IAB node through the RRC reconfiguration message; then the MT of the downlink IAB node informs the DU part, and then downlink
- the IAB node can use the identification information to establish an F1 connection with the target CU.
- Embodiment 6 is a diagrammatic representation of Embodiment 6
- the IAB node When the IAB node needs to perform RRC re-establishment due to link failure or other reasons, if the re-established cell is selected to connect to a new target donor CU, then the IP address of the target CU needs to be obtained again. For example, the target donor CU sends its own IP address information to the MT of the IAB node through the RRC reconfiguration message, and then the MT of the IAB node informs the DU part, and then the DU part of the IAB node can use the IP address to establish a TNL connection with the target CU. Then establish an F1 connection.
- the downstream IAB node also needs to re-establish an F1 connection with the new target donor CU, and also needs to obtain the IP address of the target donor CU.
- the target donor CU sends its own IP address information to the MT of the downlink IAB node through the RRC reconfiguration message, and then the MT of the downlink IAB node informs the DU part, and then the DU part of the downlink IAB node can use the IP address and
- the target CU establishes a TNL connection, and then establishes an F1 connection.
- the IAB node After the IAB node performs RRC reconstruction, it sends the indication information of the completion of the reconstruction to the downlink IAB node through an adaptation layer message (adapter layer).
- the adapter layer message includes at least one of the following: Identification information, cell identification, CU change identification, IP address of the first CU, and link reestablishment success indication.
- the target CU can allocate a new DU identifier to the DU in advance.
- the target donor CU sends the identification information of the IAB DU to the MT of the IAB node through the RRC reconfiguration message, and then the MT of the IAB node informs the DU part, and then the DU part of the IAB node can use the identification information to establish an F1 connection with the target CU.
- the implementation manner is similar to some of the manners in the foregoing embodiment, and will not be repeated here.
- Embodiment 8 is a diagrammatic representation of Embodiment 8
- the first communication node may send link state information to the second communication node (for example, the child IAB node of the first communication node) when performing link migration or RRC reconstruction.
- the link state information may include at least one of the following: identification information of the CU connected to the first communication node, change information of the CU connected to the first communication node, and IP address of the CU connected to the first communication node, The first communication node link relocation indication, and the first communication node link re-establishment indication.
- the link relocation indication of the first communication node may include at least one of the following: a link relocation start indication, a link relocation success indication, and a link relocation failure indication.
- FIG. 7 is a schematic structural diagram of a connection establishment device of an embodiment of the application, including:
- the obtaining module 701 is used to obtain the address information of the first CU.
- the connection establishment module 702 is configured to establish a connection with the first CU according to the address information of the first CU.
- the acquiring module 701 is configured to: receive the identification information of the first CU; find the mapping relationship between the CU identification information and the CU address information according to the identification information of the first CU to obtain the address of the first CU information.
- the mapping relationship table between the CU identification information and the CU address information may be pre-stored, may be obtained through the network, or configured through OAM.
- the acquiring module 701 is configured to receive address information of the first CU from the second CU or the first CU.
- the above-mentioned device may further include:
- the link connection success indication information receiving module 703 is configured to receive link connection success indication information from an upper-layer IAB node; the link connection success indication information includes at least one of the following: identification information of the first CU, cell identification , The CU change identifier, the IP address of the first CU, the link migration success indication, the link reestablishment success indication, the identifier of the IAB node for link migration, and the identifier of the IAB node for link reconstruction.
- the embodiment of the present application also proposes a link state notification device, which can be applied to a first communication node, and the device includes:
- the link state information sending module is configured to send link state information to a second communication node; wherein the second communication node is a child node of the first communication node.
- the link state information includes at least one of the following: identification information of the CU connected by the first communication node, change information of the CU connected by the first communication node, and IP address of the CU connected by the first communication node, The first communication node link relocation indication, and the first communication node link re-establishment indication.
- the aforementioned first communication node and second communication node may be IAB nodes.
- FIG. 8 is a schematic structural diagram 1 of an interface establishment device according to an embodiment of the application, including:
- the request sending module 801 is configured to send an interface establishment request message to the first CU.
- the response receiving module 802 is configured to receive an interface establishment failure message sent by the first CU, where the cause value in the interface establishment failure message is unknown or the DU identifier has been assigned; or to receive an interface establishment response sent by the first CU Message, the interface establishment response message contains the re-allocated DU identifier.
- FIG. 9 is a schematic structural diagram of an information transmission device according to an embodiment of the application, including:
- the handover request sending module 901 is configured to send a handover request message to the first CU, where the handover request message carries information of the IAB node.
- the handover response receiving module 902 is configured to receive a handover response message sent by the first CU, where the handover response message carries at least one of the address information of the first CU and the identifier of the IAB DU.
- the above-mentioned device may further include:
- the sending module 903 is configured to send at least one of the address information of the first CU and the identifier of the IAB DU to the IAB node.
- the embodiment of the present application also proposes another information transmission device, including: an identification or address sending module, configured to send identification information or address information of the first CU to the IAB node.
- FIG. 10 is a schematic diagram of the second structure of the device for establishing an interface according to an embodiment of this application, including:
- the connection establishment receiving module 1001 is configured to receive an interface establishment request message from the IAB node;
- the connection establishment feedback module 1002 is configured to send an interface establishment failure message to the IAB node when the DU identity of the IAB node conflicts with the DU identity of other connected IAB nodes, the interface establishment failure message
- the reason value in is unknown or the DU identifier has been allocated; or, an interface establishment response message is sent to the IAB node, and the interface establishment response message contains the DU identifier that is re-allocated.
- FIG. 11 is a schematic diagram of the structure of an IAB node according to an embodiment of the present application.
- the IAB node 110 provided in an embodiment of the present application includes a memory 1103 and a processor 1104.
- the IAB node 110 may further include an interface 1101 and a bus 1102.
- the interface 1101, the memory 1103 and the processor 1104 are connected through a bus 1102.
- the memory 1103 is used to store instructions.
- the processor 1104 is configured to read the instructions to execute the technical solutions of the foregoing method embodiments applied to the IAB node.
- the implementation principles and technical effects are similar, and details are not described herein again.
- FIG. 12 is a schematic structural diagram of a CU according to an embodiment of the application.
- the CU 120 provided in the embodiment of the application includes a memory 1203 and a processor 1204.
- the CU 120 may also include an interface 1201 and a bus 1202.
- the interface 1201, the memory 1203 and the processor 1204 are connected through a bus 1202.
- the memory 1203 is used to store instructions.
- the processor 1204 is configured to read the instructions to execute the technical solutions of the foregoing method embodiments applied to the CU.
- the implementation principles and technical effects are similar, and details are not described herein again.
- FIG. 13 is a schematic diagram 1 of the structure of a communication system according to an embodiment of the application. As shown in FIG. 13, the system includes: an IAB node 110 as in the foregoing embodiment and a CU 120 in the foregoing embodiment.
- FIG. 14 is a schematic diagram of the second structure of a communication system according to an embodiment of the application.
- the system includes: an IAB node 110 as in the foregoing embodiment and a CU 120 in the foregoing embodiment.
- each IAB node is divided into an MT part and a DU part.
- the MT part of each IAB node is connected to the DU by Uu
- the DU part of each IAB node is connected to the CU by F1.
- the present application provides a storage medium that stores a computer program, and when the computer program is executed by a processor, the method in the foregoing embodiment is implemented.
- the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, this application may adopt the form of hardware embodiments, software embodiments, or embodiments combining software and hardware. Moreover, this application may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, optical storage, etc.) containing computer-usable program codes.
- These computer program instructions can also be stored in a computer-readable memory that can guide a computer or other programmable data processing equipment to work in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture including the instruction device.
- the device implements the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.
- 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)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
Claims (37)
- 一种连接建立方法,包括:获取第一集中单元CU的地址信息;根据所述第一CU的地址信息,与所述第一CU建立连接。
- 根据权利要求1所述的方法,其中,所述获取第一CU的地址信息,包括:接收所述第一CU的标识信息;根据所述第一CU的标识信息查找CU标识信息与CU地址信息的映射关系,得到所述第一CU的地址信息。
- 根据权利要求2所述的方法,其中,所述第一CU的标识信息携带在适配层消息中,所述适配层消息来自上层集合接入回传IAB节点;其中,所述上层IAB节点包括:直接提供服务的父IAB节点或者参与转发数据到所述第一CU的IAB节点。
- 根据权利要求2所述的方法,其中,所述第一CU的标识信息携带在无线资源控制RRC重配消息中,所述RRC重配消息来自所述第一CU。
- 根据权利要求4所述的方法,其中,所述RRC重配消息包含小区标识和物理小区标识,所述小区标识包含所述第一CU的标识信息。
- 根据权利要求1所述的方法,其中,所述获取第一CU的地址信息,包括:接收来自第二CU的所述第一CU的地址信息。
- 根据权利要求6所述的方法,其中,所述第一CU的地址信息携带在F1消息或RRC重配消息中。
- 根据权利要求1或2所述的方法,在所述与所述第一CU建立连接之前,还包括:接收来自上层IAB节点的链路连接成功指示信息;所述链路连接成功指示信息包括以下至少一项:所述第一CU的标识信息,小区标识,CU变更标识,所述第一CU的互联网协议IP地址,链路迁移成功指示,链路重建成功指示,链路迁移的IAB节点的标识,链路重建的IAB节点的标识。
- 根据权利要求1所述的方法,其中,所述获取第一CU的地址信息,包括:接收来自所述第一CU的所述第一CU的地址信息。
- 根据权利要求9所述的方法,其中,所述第一CU的地址信息携带在RRC重配消息中。
- 一种链路状态的通知方法,包括:第一通信节点向第二通信节点发送链路状态信息,其中,所述第二通信节点为所述第一通信节点的子节点;所述链路状态信息包括以下至少一项:所述第一通信节点连接的集中单元CU的标识信息,所述第一通信节点连接的CU变更信息,所述第一通信节点连接的CU的互联网协议IP地址,所述第一通信节点链路迁移指示,所述第一通信节点链路重建指示。
- 根据权利要求11所述的方法,其中,所述第一通信节点向第二通信节点发送链路状态信息,包括:在所述第一通信节点执行链路迁移的情况下,向所述第二通信节点发送链路状态信息。
- 根据权利要求11所述的方法,其中,所述第一通信节点向第二通信节点发送链路状态信息,包括:在所述第一通信节点执行无线资源控制RRC重建的情况下,向所述第二通信节点发送链路状态信息。
- 根据权利要求11至13中任一项所述的方法,其中,所述第一通信节点链路迁移指示包括以下至少一项:链路迁移启动指示,链路迁移成功指示,链路迁移失败指示。
- 一种接口建立方法,包括:向第一集中单元CU发送接口建立请求消息;接收所述第一CU发送的接口建立失败消息,所述接口建立失败消息中的原因值为未知或分布单元DU标识已分配;或者,接收所述第一CU发送的接口建立响应消息,所述接口建立响应消息中包含重新分配的DU标识。
- 一种信息传输方法,包括:向第一集中单元CU发送切换请求消息,所述切换请求消息携带集合接入回传IAB节点的信息;接收所述第一CU发送的切换响应消息,所述切换响应消息携带所述第一CU的地址信息及IAB分布单元DU的标识中的至少一项。
- 根据权利要求16所述的方法,其中,所述IAB节点的信息包括:所述IAB节点的标识信息、IAB节点的回传信道的上下文信息、所述IAB节点服务的用户设备UE的上下文信息、以及所述IAB节点的下行IAB节点的 上下文信息中的至少一项。
- 根据权利要求16或17所述的方法,还包括:向所述IAB节点发送所述第一CU的地址信息及所述IAB DU的标识中的至少一项。
- 根据权利要求18所述的方法,其中,所述第一CU的地址信息及所述IAB DU的标识中的至少一项携带在无线资源控制RRC重配消息或F1消息中。
- 一种信息传输方法,包括:向集合接入回传IAB节点发送第一集中单元CU的标识信息或者地址信息。
- 根据权利要求20所述的方法,其中,所述第一CU的标识信息或者地址信息携带在无线资源控制RRC重配消息中。
- 根据权利要求21所述的方法,其中,所述RRC重配消息包含小区标识和物理小区标识,所述小区标识携带所述第一CU的标识信息。
- 一种接口建立方法,包括:接收来自集合接入回传IAB节点的接口建立请求消息;在所述IAB节点的分布单元DU标识与其他存在连接关系的DU标识存在冲突的情况下,向所述IAB节点发送接口建立失败消息,所述接口建立失败消息中的原因值为未知或DU标识已分配;或者,向所述IAB节点发送接口建立响应消息,所述接口建立响应消息中包含重新分配的DU标识。
- 一种连接建立装置,包括:获取模块,设置为获取第一CU的地址信息;连接建立模块,设置为根据所述第一CU的地址信息,与所述第一CU建立连接。
- 根据权利要求24所述的装置,其中,所述获取模块是设置为,接收所述第一CU的标识信息;根据所述第一CU的标识信息查找CU标识信息与CU地址信息的映射关系,得到所述第一CU的地址信息。
- 根据权利要求24所述的装置,其中,所述获取模块是设置为,接收来自第二CU或所述第一CU的所述第一CU的地址信息。
- 根据权利要求24或者25所述的装置,还包括:链路连接成功指示信息接收模块,设置为接收来自上层集合接入回传IAB 节点的链路连接成功指示信息;所述链路连接成功指示信息包括以下至少一项:所述第一CU的标识信息,小区标识,CU变更标识,所述第一CU的互联网协议IP地址,链路迁移成功指示,链路重建成功指示,链路迁移的IAB节点的标识,链路重建的IAB节点的标识。
- 一种链路状态的通知装置,应用于第一通信节点,包括:链路状态信息发送模块,设置为向第二通信节点发送链路状态信息;其中,所述第二通信节点为所述第一通信节点的子节点;所述链路状态信息包括以下至少一项:所述第一通信节点连接的集中单元CU的标识信息,所述第一通信节点连接的CU变更信息,所述第一通信节点连接的CU的互联网协议IP地址,所述第一通信节点链路迁移指示,所述第一通信节点链路重建指示。
- 一种接口建立装置,包括:请求发送模块,设置为向第一集中单元CU发送接口建立请求消息;响应接收模块,设置为接收所述第一CU发送的接口建立失败消息,所述接口建立失败消息中的原因值为未知或分布单元DU标识已分配;或者接收所述第一CU发送的接口建立响应消息,所述接口建立响应消息中包含重新分配的DU标识。
- 一种信息传输装置,包括:切换请求发送模块,设置为向第一集中单元CU发送切换请求消息,所述切换请求消息携带集合接入回传IAB节点的信息;切换响应接收模块,设置为接收所述第一CU发送的切换响应消息,所述切换响应消息携带所述第一CU的地址信息及IAB分布单元DU的标识中的至少一项。
- 根据权利要求30所述的装置,还包括:发送模块,设置为向所述IAB节点发送所述第一CU的地址信息及所述IAB DU的标识中的至少一项。
- 一种信息传输装置,包括:标识或地址发送模块,设置为向集合接入回传IAB节点发送第一集中单元CU的标识信息或者地址信息。
- 一种接口建立装置,包括:连接建立接收模块,设置为接收来自集合接入回传IAB节点的接口建立请 求消息;连接建立反馈模块,设置为在所述IAB节点的分布单元DU标识与其他存在连接关系的DU标识存在冲突的情况下,向所述IAB节点发送接口建立失败消息,所述接口建立失败消息中的原因值为未知或DU标识已分配;或者,向所述IAB节点发送接口建立响应消息,所述接口建立响应消息中包含重新分配的DU标识。
- 一种集合接入回传IAB节点,包括:处理器及存储器;所述存储器设置为存储指令;所述处理器设置为读取所述指令以执行如权利要求1至15中任一所述的方法。
- 一种集中单元CU,包括:处理器及存储器;所述存储器设置为存储指令;所述处理器设置为读取所述指令以执行如权利要求16至23中任一所述的方法。
- 一种通信系统,包括如权利要求34所述的集合接入回传IAB节点及如权利要求35所述的集中单元CU。
- 一种存储介质,存储有计算机程序,所述计算机程序被处理器执行时实现权利要求1至23中任一项所述的方法。
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US17/635,570 US20220322464A1 (en) | 2019-08-15 | 2020-07-21 | Connection establishment method and device, link state notification method and device, interface establishment method and device, information transmission method and device, integrated access backhaul node, centralized unit, system and storage medium |
EP20853348.9A EP4017206A4 (en) | 2019-08-15 | 2020-07-21 | CONNECTION ESTABLISHMENT METHOD AND DEVICE, CONNECTION STATE REPORTING METHOD AND DEVICE, INTERFACE ESTABLISHMENT METHOD AND DEVICE, INFORMATION TRANSMISSION METHOD AND DEVICE, INTEGRATED ACCESS BACKHAUL NODE, CENTRALIZED UNIT, SYSTEM AND STORAGE MEDIA |
CA3148150A CA3148150A1 (en) | 2019-08-15 | 2020-07-21 | Connection establishment method,device,integrated access backhaul node and storage medium |
KR1020227008620A KR20220049553A (ko) | 2019-08-15 | 2020-07-21 | 연결 설정 방법 및 장치, 링크 상태 통보 방법 및 장치, 인터페이스 설정 방법 및 장치, 정보 전송 방법 및 장치, 통합 액세스 백홀 노드, 중앙집중형 유닛, 시스템, 저장매체 |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201910768209.5 | 2019-08-15 | ||
CN201910768209.5A CN111093286A (zh) | 2019-08-15 | 2019-08-15 | 连接建立方法、装置、集合接入回传节点及存储介质 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2021027501A1 true WO2021027501A1 (zh) | 2021-02-18 |
Family
ID=70393409
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2020/103176 WO2021027501A1 (zh) | 2019-08-15 | 2020-07-21 | 连接建立方法及装置、链路状态的通知方法及装置、接口建立方法及装置、信息传输方法及装置、集合接入回传节点、集中单元、系统、存储介质 |
Country Status (6)
Country | Link |
---|---|
US (1) | US20220322464A1 (zh) |
EP (1) | EP4017206A4 (zh) |
KR (1) | KR20220049553A (zh) |
CN (1) | CN111093286A (zh) |
CA (1) | CA3148150A1 (zh) |
WO (1) | WO2021027501A1 (zh) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP4319304A4 (en) * | 2021-03-31 | 2024-04-24 | Fujitsu Limited | SIGNAL SENDING AND RECEIVING METHOD AND APPARATUS AND COMMUNICATION SYSTEM |
Families Citing this family (39)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN112788542B (zh) * | 2019-11-07 | 2022-06-24 | 华为技术有限公司 | 通信方法、设备及系统 |
DE112020006494T5 (de) * | 2020-01-10 | 2022-11-17 | Sony Group Corporation | Infrastrukturausrüstung, zentraleinheitsknoten und verfahren |
US11832140B2 (en) * | 2020-04-30 | 2023-11-28 | Qualcomm Incorporated | Inter-donor cell management in wireless communication network |
US12101647B2 (en) * | 2020-05-12 | 2024-09-24 | Qualcomm Incorporated | Delayed delivery of reconfiguration message in integrated access and backhaul (IAB) network |
CN113747521B (zh) * | 2020-05-29 | 2023-02-17 | 维沃移动通信有限公司 | 网络切换方法、装置、通信设备及系统 |
CN113766578B (zh) * | 2020-06-01 | 2023-02-17 | 维沃移动通信有限公司 | 自回传网络切换的方法、装置和网络设备 |
CN113766582B (zh) * | 2020-06-03 | 2023-03-14 | 维沃移动通信有限公司 | 网络切换方法、装置、通信设备及系统 |
CN113852999A (zh) * | 2020-06-28 | 2021-12-28 | 中兴通讯股份有限公司 | 资源管理方法及网络设备 |
CN113873587B (zh) * | 2020-06-30 | 2023-09-22 | 华为技术有限公司 | 一种用于iab网络通信的方法及相关设备 |
CN113891407B (zh) * | 2020-07-03 | 2022-09-02 | 大唐移动通信设备有限公司 | 一种切换方法和设备 |
CN113938877B (zh) * | 2020-07-13 | 2022-11-22 | 大唐移动通信设备有限公司 | 一种小区全局标识的配置方法、装置及存储介质 |
CN114071602B (zh) * | 2020-08-04 | 2023-05-26 | 大唐移动通信设备有限公司 | 一种节点切换配置方法及装置 |
US20230292191A1 (en) * | 2020-08-05 | 2023-09-14 | Nokia Solutions And Networks Oy | Mechanism for cell identity management |
CN114071610B (zh) * | 2020-08-06 | 2023-04-25 | 维沃移动通信有限公司 | 切换方法、装置及相关设备 |
CN114071608A (zh) * | 2020-08-06 | 2022-02-18 | 大唐移动通信设备有限公司 | 一种信息传输方法及装置 |
CN114071617B (zh) * | 2020-08-07 | 2024-07-02 | 大唐移动通信设备有限公司 | Iab节点组切换中的信息传输方法、装置、设备及系统 |
EP4192101A4 (en) * | 2020-08-31 | 2023-08-30 | Huawei Technologies Co., Ltd. | NODE SWITCHING METHOD AND RELATED DEVICE |
CN116250280A (zh) * | 2020-09-25 | 2023-06-09 | 上海诺基亚贝尔股份有限公司 | 用于集成接入和回程通信的方法、装置和计算机可读介质 |
CN114390602B (zh) * | 2020-10-16 | 2023-09-19 | 大唐移动通信设备有限公司 | 连接建立方法、装置、设备及存储介质 |
JP2023545801A (ja) * | 2020-10-21 | 2023-10-31 | 富士通株式会社 | 信号の送受信方法、装置及び通信システム |
JP2023545809A (ja) * | 2020-10-22 | 2023-10-31 | 富士通株式会社 | グループ移行方法、装置及びシステム |
CN114667757A (zh) | 2020-10-22 | 2022-06-24 | 上海诺基亚贝尔股份有限公司 | 在集成接入和回程通信中传递业务 |
US20220312529A1 (en) * | 2020-10-22 | 2022-09-29 | Apple Inc. | Systems and methods for multi-hop configurations in iab networks for reduced latency |
WO2022082683A1 (zh) * | 2020-10-22 | 2022-04-28 | 华为技术有限公司 | 一种用于接入回传一体化iab系统中的通信方法及相关设备 |
CN114390727B (zh) * | 2020-10-22 | 2024-04-26 | 大唐移动通信设备有限公司 | 目标对象切换方法及装置、电子设备、网络设备 |
WO2022088112A1 (zh) * | 2020-10-30 | 2022-05-05 | 华为技术有限公司 | 一种释放f1连接的方法、装置及系统 |
US11743757B2 (en) * | 2021-01-05 | 2023-08-29 | Qualcomm Incorporated | Gradual migration in an Integrated Access and Backhaul (IAB) network |
CN114765823B (zh) * | 2021-01-15 | 2024-01-26 | 大唐移动通信设备有限公司 | 一种节点切换方法及设备 |
WO2022160249A1 (en) * | 2021-01-29 | 2022-08-04 | Nec Corporation | Methods, devices, and computer readable medium for communication |
EP4298750A1 (en) * | 2021-04-01 | 2024-01-03 | ZTE Corporation | Integrated access and backhaul donor migration methods and systems |
CN115190536A (zh) * | 2021-04-01 | 2022-10-14 | 华为技术有限公司 | 用于信息传输的方法和装置 |
CN115314956A (zh) * | 2021-05-07 | 2022-11-08 | 华为技术有限公司 | 一种iab节点连接更新方法及装置 |
WO2023010367A1 (zh) * | 2021-08-04 | 2023-02-09 | 富士通株式会社 | 终端设备的转移方法、装置和系统 |
WO2023028831A1 (en) * | 2021-08-31 | 2023-03-09 | Nec Corporation | Methods, devices, and computer readable medium for communication |
WO2024007286A1 (en) * | 2022-07-08 | 2024-01-11 | Lenovo (Beijing) Limited | Method and apparatus for ue handover in iab network |
CN117545025A (zh) * | 2022-08-01 | 2024-02-09 | 华为技术有限公司 | 一种基于接入回传一体化iab的通信方法及装置 |
CN117560732A (zh) * | 2022-08-05 | 2024-02-13 | 北京三星通信技术研究有限公司 | 节点执行的方法及网络节点 |
WO2024065289A1 (en) * | 2022-09-28 | 2024-04-04 | Lenovo (Beijing) Limited | Method and apparatus for iab node integration |
CN118510077A (zh) * | 2023-02-16 | 2024-08-16 | 华为技术有限公司 | 通信方法及通信装置 |
Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20190053183A1 (en) * | 2017-08-10 | 2019-02-14 | Kyungmin Park | Timing Advance Group Configuration |
Family Cites Families (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN110365470B (zh) * | 2018-03-26 | 2023-10-10 | 华为技术有限公司 | 一种密钥生成方法和相关装置 |
CN112740758B (zh) * | 2018-10-09 | 2022-11-15 | 联想(北京)有限公司 | 具有网络信息的切换请求 |
CN115442010A (zh) * | 2019-02-15 | 2022-12-06 | 华为技术有限公司 | 标识管理的方法和装置 |
KR102627400B1 (ko) * | 2019-03-28 | 2024-01-18 | 지티이 코포레이션 | Iab 핸드오버들을 위한 시스템 및 방법 |
-
2019
- 2019-08-15 CN CN201910768209.5A patent/CN111093286A/zh active Pending
-
2020
- 2020-07-21 WO PCT/CN2020/103176 patent/WO2021027501A1/zh unknown
- 2020-07-21 US US17/635,570 patent/US20220322464A1/en active Pending
- 2020-07-21 KR KR1020227008620A patent/KR20220049553A/ko not_active Application Discontinuation
- 2020-07-21 EP EP20853348.9A patent/EP4017206A4/en active Pending
- 2020-07-21 CA CA3148150A patent/CA3148150A1/en active Pending
Patent Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20190053183A1 (en) * | 2017-08-10 | 2019-02-14 | Kyungmin Park | Timing Advance Group Configuration |
Non-Patent Citations (4)
Title |
---|
ANONYMOUS: "3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Study on Integrated Access and Backhaul; (Release 16)", 3GPP STANDARD; TECHNICAL REPORT; 3GPP TR 38.874, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, no. V16.0.0, 31 December 2018 (2018-12-31), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, pages 1 - 111, XP051591643 * |
QUALCOMM INC.: "IAB topological redundancy for architecture 1a", 3GPP TSG-RAN WG3 MEETING #101, R3-184694, 24 August 2018 (2018-08-24), XP051528041 * |
QUALCOMM INCORPORATED ET AL.: "IAB inter-CU Topology Adaptation for Arch 1a", 3GPP TSG-RAN WG3 MEETING #102, R3-186456, 16 November 2018 (2018-11-16), XP051482600 * |
See also references of EP4017206A4 |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP4319304A4 (en) * | 2021-03-31 | 2024-04-24 | Fujitsu Limited | SIGNAL SENDING AND RECEIVING METHOD AND APPARATUS AND COMMUNICATION SYSTEM |
Also Published As
Publication number | Publication date |
---|---|
CN111093286A (zh) | 2020-05-01 |
US20220322464A1 (en) | 2022-10-06 |
CA3148150A1 (en) | 2021-02-18 |
EP4017206A4 (en) | 2023-08-16 |
KR20220049553A (ko) | 2022-04-21 |
EP4017206A1 (en) | 2022-06-22 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2021027501A1 (zh) | 连接建立方法及装置、链路状态的通知方法及装置、接口建立方法及装置、信息传输方法及装置、集合接入回传节点、集中单元、系统、存储介质 | |
CN110167051B (zh) | 集中式单元-分布式单元架构下的通信方法、通信设备 | |
US20220174759A1 (en) | Method and apparatus for operating wireless communication system having separated mobility management and session management | |
KR102407078B1 (ko) | 사용자 정보 관리를 위한 방법 및 시스템 | |
KR102469973B1 (ko) | 통신 방법 및 장치 | |
JP7483898B2 (ja) | 通信方法及び装置 | |
WO2019157985A1 (zh) | 一种无线回传通信处理方法和相关设备 | |
KR20170133793A (ko) | 이동통신 코어 망에서의 시그널링 방법 및 그 시스템 | |
CN109548174B (zh) | 一种偶联管理的方法和网络节点 | |
US20230239940A1 (en) | Data transmission method and apparatus | |
US11483759B2 (en) | Address sending method and device and storage medium | |
WO2018014154A1 (zh) | 一种rrc连接重建方法和装置 | |
CN109688631B (zh) | 一种连接处理方法和设备 | |
WO2021129018A1 (zh) | 网络连接的重建立方法及装置、存储介质、电子装置 | |
WO2014127699A1 (zh) | 一种建立直接通信路径的方法、设备及系统 | |
WO2018145526A1 (zh) | Gtp传输通道的配置方法及装置、存储介质 | |
US20230262827A1 (en) | Communication method applied to integrated access and backhaul iab system and related device | |
JP7149328B2 (ja) | カップリングリダイレクト方法および装置 | |
US20230308971A1 (en) | Methods and apparatus for supporting switching of traffic corresponding to a communication session between two non-3gpp access paths | |
CN109587709A (zh) | 本地数据网的发现、配置方法、终端、核心网设备及基站 | |
WO2021042381A1 (zh) | 一种通信方法、装置及系统 | |
WO2020066056A1 (ja) | 制御プレーン機器、プログラム、システム及び情報処理装置 | |
WO2023030945A2 (en) | Data synchronization between active and standby nodes for service continuity | |
JP6645677B2 (ja) | リンク確立方法およびデバイス | |
JP2024530096A (ja) | 通信接続の再確立のための通信ネットワークコンポーネント及び方法 |
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: 20853348 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 3148150 Country of ref document: CA |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
ENP | Entry into the national phase |
Ref document number: 20227008620 Country of ref document: KR Kind code of ref document: A |
|
ENP | Entry into the national phase |
Ref document number: 2020853348 Country of ref document: EP Effective date: 20220315 |