EP4226732A1

EP4226732A1 - Methods, apparatuses, and computer readable media for peer-to-peer communication via integrated access and backhaul network

Info

Publication number: EP4226732A1
Application number: EP20956500.1A
Authority: EP
Inventors: Ilkka Keskitalo; Matti Laitila; Jens Gebert; Xiang Xu; Henri Koskinen
Original assignee: Nokia Solutions and Networks Oy
Current assignee: Nokia Solutions and Networks Oy
Priority date: 2020-10-09
Filing date: 2020-10-09
Publication date: 2023-08-16
Also published as: CN116349384A; CN116349384B; EP4226732A4; WO2022073185A1

Abstract

Disclosed are methods for. An example method may include: receiving, at a first apparatus, configuration information from a donor apparatus in an integrated access and backhaul network for a peer-to-peer connection between the first apparatus and a second apparatus via the integrated access and backhaul network; and transmit, at the first apparatus via an access link and to a third apparatus serving the first apparatus in the integrated access and backhaul network, a data unit of the peer-to-peer connection based on the configuration information. Related apparatuses and computer readable media are also disclosed.

Description

METHODS, APPARATUSES, AND COMPUTER READABLE MEDIA FOR PEER-TO-PEER COMMUNICATION VIA INTEGRATED ACCESS AND BACKHAUL NETWORK

TECHNICAL FIELD

Various embodiments relate to methods, apparatuses, and computer readable media for peer-to-peer communication via an integrated access and backhaul network.

BACKGROUND

Integrated access and backhaul (IAB) network, where a part of radio resources is also used for wireless backhauling, has been introduced in a telecommunication system such as a new radio (NR or 5G) system, so that, for example, flexible and dense deployments of NR cells may be enabled without densifying the transport network proportionately and the site acquisition costs and fiber deployment costs may be reduced.
SUMMARY
In a first aspect, disclosed is an apparatus comprising at least one processor and at least one memory including computer program code, the at least one memory and the computer program code being configured to, with the at least one processor, cause the apparatus as a first apparatus to: receive configuration information from a donor apparatus in an integrated access and backhaul network for a peer-to-peer connection between the first apparatus and a second apparatus via the integrated access and backhaul network; and transmit, via an access link and to a third apparatus serving the first apparatus in the integrated access and backhaul network, a data unit of the peer-to-peer connection based on the configuration information.
In some embodiments, the at least one memory and the computer program code are configured to, with the at least one processor, further cause the apparatus to transmit a request for establishing the peer-to-peer connection with the second apparatus, the request comprising information on at least one of an identifier of the first apparatus, an identifier of the second apparatus, and an identifier of a data flow associated with the data unit.
In some embodiments, the configuration information comprises information on at least one of a radio bearer used over the access link for the peer-to-peer connection, and an identifier of the peer-to-peer connection.
In some embodiments, the at least one memory and the computer program code are configured to, with the at least one processor, further cause the apparatus to determine a radio bearer used for transmitting the data unit over the access link based on the configuration information.
In some embodiments, the first apparatus is a user equipment or a mobile termination part of an integrated access and backhaul network node apparatus in the integrated access and backhaul network.
In some embodiments, the peer-to-peer connection emulates a sidelink connection between the first apparatus and the second apparatus, and comprises a sidelink packet data convergence protocol communication layer and a sidelink service data adaptation protocol communication layer terminated at the first apparatus and at the second apparatus and transparently relayed through the integrated access and backhaul network.
In a second aspect, disclosed is an apparatus comprising at least one processor and at least one memory including computer program code, the at least one memory and the computer program code being configured to, with the at least one processor, cause the apparatus as a first apparatus in an integrated access and backhaul network to: receive routing and bearer mapping configuration information from a donor apparatus in the integrated access and backhaul network for a peer-to-peer connection between a second apparatus served by the first apparatus and a third apparatus via the integrated access and backhaul network; receive a data unit of the peer-to-peer connection from the second apparatus via an access link; and transmit a backhaul adaptation protocol packet including a backhaul adaptation protocol header and the data unit based on the routing and bearer mapping configuration information, the backhaul adaptation protocol header comprising information associated with the peer-to-peer connection.
In some embodiments, the routing and bearer mapping configuration information comprises information on at least one of a routing identifier used for routing the data unit to a next-hop apparatus, an identifier of the next-hop apparatus, an identifier of the peer-to-peer connection, an identifier of a radio bearer used over the access link for the peer-to-peer connection, an identifier of a logical channel used over the access link for the peer-to-peer connection, and an identifier of a logical channel used for transmitting the backhaul adaptation protocol packet to the next-hop apparatus.
In some embodiments, the information associated with the peer-to-peer connection comprises at least one of a routing identifier used for routing the data unit to a next-hop apparatus in the integrated access and backhaul network, an identifier of the peer-to-peer connection, an identifier of a radio bearer used over the access link for the peer-to-peer connection, and an identifier of the second apparatus.
In some embodiments, the peer-to-peer connection emulates a sidelink connection between the second apparatus and the third apparatus, and comprises a sidelink packet data convergence protocol communication layer and a sidelink service data adaptation protocol communication layer terminated at the second apparatus and at the third apparatus and transparently relayed through the integrated access and backhaul network.
In a third aspect, disclosed is an apparatus comprising at least one processor and at least one memory including computer program code, the at least one memory and the computer program code being configured to, with the at least one processor, cause the apparatus as a first apparatus to: receive configuration information from a donor apparatus in an integrated access and backhaul network for a peer-to-peer connection between the first apparatus and a second apparatus via the integrated access and backhaul network; and receive, via an access link and from a third apparatus serving the first apparatus in the integrated access and backhaul network, a data unit of the peer-to-peer connection based on the configuration information.
In some embodiments, the configuration information comprises information on at least one of a radio bearer used over the access link for the peer-to-peer connection, and an identifier of the peer-to-peer connection.
In some embodiments, the at least one memory and the computer program code are configured to, with the at least one processor, further cause the apparatus to determine a radio bearer used for carrying the data unit over the access link based on the configuration information.
In some embodiments, the first apparatus is a user equipment or a mobile termination part of an integrated access and backhaul network node apparatus in the integrated access and backhaul network.
In some embodiments, the peer-to-peer connection emulates a sidelink connection between the first apparatus and the second apparatus, and comprises a sidelink packet data convergence protocol communication layer and a sidelink service data adaptation protocol communication layer terminated at the first apparatus and at the second apparatus and transparently relayed through the integrated access and backhaul network.
In a fourth aspect, disclosed is an apparatus comprising at least one processor and at least one memory including computer program code, the at least one memory and the computer program code being configured to, with the at least one processor, cause the apparatus as a first apparatus in an integrated access and backhaul network to receive bearer mapping configuration information from a donor apparatus in the integrated access and backhaul network for a peer-to-peer connection between a second apparatus and a third apparatus served by the first apparatus via the integrated access and backhaul network; receive a backhaul adaptation protocol packet including a backhaul adaptation protocol header and a data unit of the peer-to-peer connection, the backhaul adaptation protocol packet comprising information associated with the peer-to-peer connection; and transmit the data unit to the third apparatus via a first access link based on the bearer mapping configuration information and the backhaul adaptation protocol header.
In some embodiments, the bearer mapping configuration information comprises information on at least one of an identifier of the third apparatus, an identifier of the peer-to-peer connection, an identifier of a radio bearer used over the first access link for the peer-to-peer connection, an identifier of a logical channel used over the first access link for the peer-to-peer connection, and an identifier of the first access link.
In some embodiments, the information associated with the peer-to-peer connection comprises at least one of an identifier of the peer-to-peer connection, an identifier of a radio bearer used over a second access link between the second apparatus and a fourth apparatus serving the second apparatus in the integrated access and backhaul network for the peer-to-peer connection, an identifier of the second access link, and an identifier of the second apparatus.
In some embodiments, the peer-to-peer connection emulates a sidelink connection between the second apparatus and the third apparatus, and comprises a sidelink packet data convergence protocol communication layer and a sidelink service data adaptation protocol communication layer terminated at the second apparatus and at the third apparatus and transparently relayed through the integrated access and backhaul network.
In a fifth aspect, disclosed is an apparatus comprising at least one processor and at least one memory including computer program code, the at least one memory and the computer program code being configured to, with the at least one processor, cause the apparatus as a donor apparatus in an integrated access and backhaul network to: transmit, to a first apparatus, first configuration information for a peer-to-peer connection between the first apparatus and a second apparatus via the integrated access and backhaul network, to enable the first apparatus to transmit a data unit of the peer-to-peer connection via a first access link to a third apparatus serving the first apparatus in the integrated access and backhaul network; transmit, to the second apparatus, second configuration information for the peer-to-peer connection, to enable the second apparatus to receive the data unit via a second access link from a fourth apparatus serving the second apparatus in the integrated access and backhaul network; transmit, to the third apparatus, first routing and bearer mapping configuration information for the peer-to-peer connection; and transmit, to the fourth apparatus, second bearer mapping configuration information for the peer-to-peer connection.
In some embodiments, the at least one memory and the computer program code is configured to, with the at least one processor, further cause the apparatus to receive a request from the first apparatus for establishing the peer-to-peer connection with the second apparatus, the request comprising information on at least one of an identifier of the first apparatus, an identifier of the second apparatus, and an identifier of a data flow associated with the data unit.
In some embodiments, the first configuration information comprises information on at least one of a radio bearer used over the first access link for the peer-to-peer connection, and an identifier of the peer-to-peer connection.
In some embodiments, the second configuration information comprises at least one of information on at least one of a radio bearer used over the second access link for the peer-to-peer connection, and an identifier of the peer-to-peer connection.
In some embodiments, the first routing and bearer mapping configuration information comprises information on at least one of a routing identifier for routing the data unit to a next-hop apparatus in the integrated access and backhaul network, an identifier of the next-hop apparatus, an identifier of the peer-to-peer connection, an identifier of a radio bearer used over the first access link for the peer-to-peer connection, an identifier of a logical channel used over the first access link for the peer-to-peer connection, and an identifier of a logical channel used for transmitting a backhaul adaptation protocol packet carrying the data unit to the next-hop apparatus.
In some embodiments, the second bearer mapping configuration information comprises information on at least one of an identifier of the second apparatus, an identifier of the peer-to-peer connection, an identifier of a radio bearer used over the second access link for the peer-to-peer connection, an identifier of a logical channel used over the second access link for the peer-to-peer connection, and an identifier of the second access link.
In some embodiments, the at least one memory and the computer program code are configured to, with the at least one processor, further cause the apparatus to determine at least one apparatus in the integrated access and backhaul network, the at least one apparatus comprising the third apparatus and the fourth apparatus, and forming a routing path for the peer to peer connection from the first apparatus to the second apparatus bypassing the donor apparatus.
In some embodiments, the peer-to-peer connection emulates a sidelink connection between the first apparatus and the second apparatus, and comprises a sidelink packet data convergence protocol communication layer and a sidelink service data adaptation protocol communication layer terminated at the first apparatus and at the second apparatus and transparently relayed through the integrated access and backhaul network.
In a sixth aspect, disclosed is a method comprising: receiving, at a first apparatus, configuration information from a donor apparatus in an integrated access and backhaul network for a peer-to-peer connection between the first apparatus and a second apparatus via the integrated access and backhaul network; and transmitting, at the first apparatus via an access link and to a third apparatus serving the first apparatus in the integrated access and backhaul network, a data unit of the peer-to-peer connection based on the configuration information.
In some embodiments, the method further comprises transmitting a request for establishing the peer-to-peer connection with the second apparatus, the request comprising information on at least one of an identifier of the first apparatus, an identifier of the second apparatus, and an identifier of a data flow associated with the data unit.
In some embodiments, the configuration information comprises information on at least one of a radio bearer used over the access link for the peer-to-peer connection, and an identifier of the peer-to-peer connection.
In some embodiments, the method further comprises determining a radio bearer used for transmitting the data unit over the access link based on the configuration information.
In some embodiments, the first apparatus is a user equipment or a mobile termination part of an integrated access and backhaul network node apparatus in the integrated access and backhaul network.
In some embodiments, the peer-to-peer connection emulates a sidelink connection between the first apparatus and the second apparatus, and comprises a sidelink packet data convergence protocol communication layer and a sidelink service data adaptation protocol communication layer terminated at the first apparatus and at the second apparatus and transparently relayed through the integrated access and backhaul network.
In a seventh aspect, disclosed is a method comprising: receiving, at a first apparatus in an integrated access and backhaul network, routing and bearer mapping configuration information from a donor apparatus in the integrated access and backhaul network for a peer-to-peer connection between a second apparatus served by the first apparatus and a third apparatus via the integrated access and backhaul network; receiving, at the first apparatus, a data unit of the peer-to-peer connection from the second apparatus via an access link; and transmitting, at the first apparatus, a backhaul adaptation protocol packet including a backhaul adaptation protocol header and the data unit based on the routing and bearer mapping configuration information, the backhaul adaptation protocol header comprising information associated with the peer-to-peer connection.
In some embodiments, the routing and bearer mapping configuration information comprises information on at least one of a routing identifier used for routing the data unit to a next-hop apparatus, an identifier of the next-hop apparatus, an identifier of the peer-to-peer connection, an identifier of a radio bearer used over the access link for the peer-to-peer connection, an identifier of a logical channel used over the access link for the peer-to-peer connection, and an identifier of a logical channel used for transmitting the backhaul adaptation protocol packet to the next-hop apparatus.
In some embodiments, the information associated with the peer-to-peer connection comprises at least one of a routing identifier used for routing the data unit to a next-hop apparatus in the integrated access and backhaul network, an identifier of the peer-to-peer connection, an identifier of a radio bearer used over the access link for the peer-to-peer connection, and an identifier of the second apparatus.
In some embodiments, the peer-to-peer connection emulates a sidelink connection between the second apparatus and the third apparatus, and comprises a sidelink packet data convergence protocol communication layer and a sidelink service data adaptation protocol communication layer terminated at the second apparatus and at the third apparatus and transparently relayed through the integrated access and backhaul network.
In an eighth aspect, disclosed is a method comprising: receiving, at a first apparatus, configuration information from a donor apparatus in an integrated access and backhaul network for a peer-to-peer connection between the first apparatus and a second apparatus via the integrated access and backhaul network; and receiving, at the first apparatus via an access link and from a third apparatus serving the first apparatus in the integrated access and backhaul network, a data unit of the peer-to-peer connection based on the configuration information.
In some embodiments, the configuration information comprises information on at least one of a radio bearer used over the access link for the peer-to-peer connection, and an identifier of the peer-to-peer connection.
In some embodiments, the method further comprises determining, at the first apparatus, a radio bearer used for carrying the data unit over the access link based on the configuration information.
In some embodiments, the first apparatus is a user equipment or a mobile termination part of an integrated access and backhaul network node apparatus in the integrated access and backhaul network.
In some embodiments, the peer-to-peer connection emulates a sidelink connection between the first apparatus and the second apparatus, and comprises a sidelink packet data convergence protocol communication layer and a sidelink service data adaptation protocol communication layer terminated at the first apparatus and at the second apparatus and transparently relayed through the integrated access and backhaul network.
In a ninth aspect, disclosed is a method comprising: receiving, at a first apparatus in an integrated access and backhaul network, bearer mapping configuration information from a donor apparatus in the integrated access and backhaul network for a peer-to-peer connection between a second apparatus and a third apparatus served by the first apparatus via the integrated access and backhaul network; receiving, at the first apparatus, a backhaul adaptation protocol packet including a backhaul adaptation protocol header and a data unit of the peer-to-peer connection, the backhaul adaptation protocol packet comprising information associated with the peer-to-peer connection; and transmitting, at the first apparatus, the data unit to the third apparatus via a first access link based on the bearer mapping configuration information and the backhaul adaptation protocol header.
In some embodiments, the bearer mapping configuration information comprises information on at least one of an identifier of the third apparatus, an identifier of the peer-to-peer connection, an identifier of a radio bearer used over the first access link for the peer-to-peer connection, an identifier of a logical channel used over the first access link for the peer-to-peer connection, and an identifier of the first access link.
In some embodiments, the information associated with the peer-to-peer connection comprises at least one of an identifier of the peer-to-peer connection, an identifier of a radio bearer used over a second access link between the second apparatus and a fourth apparatus serving the second apparatus in the integrated access and backhaul network for the peer-to-peer connection, an identifier of the second access link, and an identifier of the second apparatus.
In some embodiments, the peer-to-peer connection emulates a sidelink connection between the second apparatus and the third apparatus, and comprises a sidelink packet data convergence protocol communication layer and a sidelink service data adaptation protocol communication layer terminated at the second apparatus and at the third apparatus and transparently relayed through the integrated access and backhaul network.
In a tenth aspect, disclosed is a method comprising: transmitting, at a donor apparatus in an integrated access and backhaul network and to a first apparatus, first configuration information for a peer-to-peer connection between the first apparatus and a second apparatus via the integrated access and backhaul network, to enable the first apparatus to transmit a data unit of the peer-to-peer connection via a first access link to a third apparatus serving the first apparatus in the integrated access and backhaul network; transmitting, at the donor apparatus to the second apparatus, second configuration information for the peer-to-peer connection, to enable the second apparatus to receive the data unit via a second access link from a fourth apparatus serving the second apparatus in the integrated access and backhaul network; transmitting, at the donor apparatus to the third apparatus, first routing and bearer mapping configuration information for the peer-to-peer connection; and transmitting, at the donor apparatus to the fourth apparatus, second bearer mapping configuration information for the peer-to-peer connection.
In some embodiments, the method further comprises receiving, at the donor apparatus, a request from the first apparatus for establishing the peer-to-peer connection with the second apparatus, the request comprising information on at least one of an identifier of the first apparatus, an identifier of the second apparatus, and an identifier of a data flow associated with the data unit.
In some embodiments, the first configuration information comprises information on at least one of a radio bearer used over the first access link for the peer-to-peer connection, and an identifier of the peer-to-peer connection.
In some embodiments, the second configuration information comprises at least one of information on at least one of a radio bearer used over the second access link for the peer-to-peer connection, and an identifier of the peer-to-peer connection.
In some embodiments, the first routing and bearer mapping configuration information comprises information on at least one of a routing identifier for routing the data unit to a next-hop apparatus in the integrated access and backhaul network, an identifier of the next-hop apparatus, an identifier of the peer-to-peer connection, an identifier of a radio bearer used over the first access link for the peer-to-peer connection, an identifier of a logical channel used over the first access link for the peer-to-peer connection, and an identifier of a logical channel used for transmitting a backhaul adaptation protocol packet carrying the data unit to the next-hop apparatus.
In some embodiments, the second bearer mapping configuration information comprises information on at least one of an identifier of the second apparatus, an identifier of the peer-to-peer connection, an identifier of a radio bearer used over the second access link for the peer-to-peer connection, an identifier of a logical channel used over the second access link for the peer-to-peer connection, and an identifier of the second access link.
In some embodiments, the method further comprises determining, at the donor apparatus, at least one apparatus in the integrated access and backhaul network, the at least one apparatus comprising the third apparatus and the fourth apparatus, and forming a routing path for the peer to peer connection from the first apparatus to the second apparatus bypassing the donor apparatus.
In some embodiments, the peer-to-peer connection emulates a sidelink connection between the first apparatus and the second apparatus, and comprises a sidelink packet data convergence protocol communication layer and a sidelink service data adaptation protocol communication layer terminated at the first apparatus and at the second apparatus and transparently relayed through the integrated access and backhaul network.
In a eleventh aspect, disclosed is an apparatus as a first apparatus comprising: means for receiving configuration information from a donor apparatus in an integrated access and backhaul network for a peer-to-peer connection between the first apparatus and a second apparatus via the integrated access and backhaul network, and means for transmitting, via an access link and to a third apparatus serving the first apparatus in the integrated access and backhaul network, a data unit of the peer-to-peer connection based on the configuration information.
In some embodiments, the apparatus further comprises means for transmitting a request for establishing the peer-to-peer connection with the second apparatus, the request comprising information on at least one of an identifier of the first apparatus, an identifier of the second apparatus, and an identifier of a data flow associated with the data unit.
In some embodiments, the configuration information comprises information on at least one of a radio bearer used over the access link for the peer-to-peer connection, and an identifier of the peer-to-peer connection.
In some embodiments, the apparatus further comprises means for determining a radio bearer used for transmitting the data unit over the access link based on the configuration information.
In some embodiments, the first apparatus is a user equipment or a mobile termination part of an integrated access and backhaul network node apparatus in the integrated access and backhaul network.
In some embodiments, the peer-to-peer connection emulates a sidelink connection between the first apparatus and the second apparatus, and comprises a sidelink packet data convergence protocol communication layer and a sidelink service data adaptation protocol communication layer terminated at the first apparatus and at the second apparatus and transparently relayed through the integrated access and backhaul network.
In a twelfth aspect, disclosed is an apparatus as a first apparatus in an integrated access and backhaul network comprising: means for receiving routing and bearer mapping configuration information from a donor apparatus in the integrated access and backhaul network for a peer-to-peer connection between a second apparatus served by the first apparatus and a third apparatus via the integrated access and backhaul network, means for receiving a data unit of the peer-to-peer connection from the second apparatus via an access link, and means for transmitting a backhaul adaptation protocol packet including a backhaul adaptation protocol header and the data unit based on the routing and bearer mapping configuration information, the backhaul adaptation protocol header comprising information associated with the peer-to-peer connection.
In some embodiments, the routing and bearer mapping configuration information comprises information on at least one of a routing identifier used for routing the data unit to a next-hop apparatus, an identifier of the next-hop apparatus, an identifier of the peer-to-peer connection, an identifier of a radio bearer used over the access link for the peer-to-peer connection, an identifier of a logical channel used over the access link for the peer-to-peer connection, and an identifier of a logical channel used for transmitting the backhaul adaptation protocol packet to the next-hop apparatus.
In some embodiments, the information associated with the peer-to-peer connection comprises at least one of a routing identifier used for routing the data unit to a next-hop apparatus in the integrated access and backhaul network, an identifier of the peer-to-peer connection, an identifier of a radio bearer used over the access link for the peer-to-peer connection, and an identifier of the second apparatus.
In some embodiments, the peer-to-peer connection emulates a sidelink connection between the second apparatus and the third apparatus, and comprises a sidelink packet data convergence protocol communication layer and a sidelink service data adaptation protocol communication layer terminated at the second apparatus and at the third apparatus and transparently relayed through the integrated access and backhaul network.
In a thirteenth aspect, disclosed is an apparatus as a first apparatus comprising: means for receiving configuration information from a donor apparatus in an integrated access and backhaul network for a peer-to-peer connection between the first apparatus and a second apparatus via the integrated access and backhaul network, and means for receiving, via an access link and from a third apparatus serving the first apparatus in the integrated access and backhaul network, a data unit of the peer-to-peer connection based on the configuration information.
In some embodiments, the configuration information comprises information on at least one of a radio bearer used over the access link for the peer-to-peer connection, and an identifier of the peer-to-peer connection.
In some embodiments, the apparatus further comprises means for determining, at the first apparatus, a radio bearer used for carrying the data unit over the access link based on the configuration information.
In some embodiments, the first apparatus is a user equipment or a mobile termination part of an integrated access and backhaul network node apparatus in the integrated access and backhaul network.
In some embodiments, the peer-to-peer connection emulates a sidelink connection between the first apparatus and the second apparatus, and comprises a sidelink packet data convergence protocol communication layer and a sidelink service data adaptation protocol communication layer terminated at the first apparatus and at the second apparatus and transparently relayed through the integrated access and backhaul network.
In a fourteenth aspect, disclosed is an apparatus as a first apparatus in an integrated access and backhaul network comprising: means for receiving bearer mapping configuration information from a donor apparatus in the integrated access and backhaul network for a peer-to-peer connection between a second apparatus and a third apparatus served by the first apparatus via the integrated access and backhaul network, means for receiving a backhaul adaptation protocol packet including a backhaul adaptation protocol header and a data unit of the peer-to-peer connection, the backhaul adaptation protocol packet comprising information associated with the peer-to-peer connection, and means for transmitting the data unit to the third apparatus via a first access link based on the bearer mapping configuration information and the backhaul adaptation protocol header.
In some embodiments, the bearer mapping configuration information comprises information on at least one of an identifier of the third apparatus, an identifier of the peer-to-peer connection, an identifier of a radio bearer used over the first access link for the peer-to-peer connection, an identifier of a logical channel used over the first access link for the peer-to-peer connection, and an identifier of the first access link.
In some embodiments, the information associated with the peer-to-peer connection comprises at least one of an identifier of the peer-to-peer connection, an identifier of a radio bearer used over a second access link between the second apparatus and a fourth apparatus serving the second apparatus in the integrated access and backhaul network for the peer-to-peer connection, an identifier of the second access link, and an identifier of the second apparatus.
In some embodiments, the peer-to-peer connection emulates a sidelink connection between the second apparatus and the third apparatus, and comprises a sidelink packet data convergence protocol communication layer and a sidelink service data adaptation protocol communication layer terminated at the second apparatus and at the third apparatus and transparently relayed through the integrated access and backhaul network.
In a fifteenth aspect, disclosed is an apparatus as a donor apparatus in an integrated access and backhaul network comprising: means for transmitting, to a first apparatus, first configuration information for a peer-to-peer connection between the first apparatus and a second apparatus via the integrated access and backhaul network, to enable the first apparatus to transmit a data unit of the peer-to-peer connection via a first access link to a third apparatus serving the first apparatus in the integrated access and backhaul network, means for transmitting, to the second apparatus, second configuration information for the peer-to-peer connection, to enable the second apparatus to receive the data unit via a second access link from a fourth apparatus serving the second apparatus in the integrated access and backhaul network, means for transmitting, to the third apparatus, first routing and bearer mapping configuration information for the peer-to-peer connection, and means for transmitting, to the fourth apparatus, second bearer mapping configuration information for the peer-to-peer connection.
In some embodiments, the apparatus further comprises means for receiving a request from the first apparatus for establishing the peer-to-peer connection with the second apparatus, the request comprising information on at least one of an identifier of the first apparatus, an identifier of the second apparatus, and an identifier of a data flow associated with the data unit.
In some embodiments, the first configuration information comprises information on at least one of a radio bearer used over the first access link for the peer-to-peer connection, and an identifier of the peer-to-peer connection.
In some embodiments, the second configuration information comprises at least one of information on at least one of a radio bearer used over the second access link for the peer-to-peer connection, and an identifier of the peer-to-peer connection.
In some embodiments, the first routing and bearer mapping configuration information comprises information on at least one of a routing identifier for routing the data unit to a next-hop apparatus in the integrated access and backhaul network, an identifier of the next-hop apparatus, an identifier of the peer-to-peer connection, an identifier of a radio bearer used over the first access link for the peer-to-peer connection, an identifier of a logical channel used over the first access link for the peer-to-peer connection, and an identifier of a logical channel used for transmitting a backhaul adaptation protocol packet carrying the data unit to the next-hop apparatus.
In some embodiments, the second bearer mapping configuration information comprises information on at least one of an identifier of the second apparatus, an identifier of the peer-to-peer connection, an identifier of a radio bearer used over the second access link for the peer-to-peer connection, an identifier of a logical channel used over the second access link for the peer-to-peer connection, and an identifier of the second access link.
In some embodiments, the apparatus further comprises means for determining at least one apparatus in the integrated access and backhaul network, the at least one apparatus comprising the third apparatus and the fourth apparatus, and forming a routing path for the peer to peer connection from the first apparatus to the second apparatus bypassing the donor apparatus.
In some embodiments, the peer-to-peer connection emulates a sidelink connection between the first apparatus and the second apparatus, and comprises a sidelink packet data convergence protocol communication layer and a sidelink service data adaptation protocol communication layer terminated at the first apparatus and at the second apparatus and transparently relayed through the integrated access and backhaul network.
In a sixteenth aspect, disclosed is a computer readable medium comprising instructions stored thereon for causing an apparatus as a first apparatus to: receive configuration information from a donor apparatus in an integrated access and backhaul network for a peer-to-peer connection between the first apparatus and a second apparatus via the integrated access and backhaul network; and transmit, via an access link and to a third apparatus serving the first apparatus in the integrated access and backhaul network, a data unit of the peer-to-peer connection based on the configuration information.
In some embodiments, the instructions further cause the apparatus to transmit a request for establishing the peer-to-peer connection with the second apparatus, the request comprising information on at least one of an identifier of the first apparatus, an identifier of the second apparatus, and an identifier of a data flow associated with the data unit.
In some embodiments, the configuration information comprises information on at least one of a radio bearer used over the access link for the peer-to-peer connection, and an identifier of the peer-to-peer connection.
In some embodiments, the instructions further cause the apparatus to determine a radio bearer used for transmitting the data unit over the access link based on the configuration information.
In some embodiments, the first apparatus is a user equipment or a mobile termination part of an integrated access and backhaul network node apparatus in the integrated access and backhaul network.
In some embodiments, the peer-to-peer connection emulates a sidelink connection between the first apparatus and the second apparatus, and comprises a sidelink packet data convergence protocol communication layer and a sidelink service data adaptation protocol communication layer terminated at the first apparatus and at the second apparatus and transparently relayed through the integrated access and backhaul network.
In a seventeenth aspect, disclosed is a computer readable medium comprising instructions stored thereon for causing an apparatus as a first apparatus in an integrated access and backhaul network to: receive routing and bearer mapping configuration information from a donor apparatus in the integrated access and backhaul network for a peer-to-peer connection between a second apparatus served by the first apparatus and a third apparatus via the integrated access and backhaul network; receive a data unit of the peer-to-peer connection from the second apparatus via an access link; and transmit a backhaul adaptation protocol packet including a backhaul adaptation protocol header and the data unit based on the routing and bearer mapping configuration information, the backhaul adaptation protocol header comprising information associated with the peer-to-peer connection.
In some embodiments, the routing and bearer mapping configuration information comprises information on at least one of a routing identifier used for routing the data unit to a next-hop apparatus, an identifier of the next-hop apparatus, an identifier of the peer-to-peer connection, an identifier of a radio bearer used over the access link for the peer-to-peer connection, an identifier of a logical channel used over the access link for the peer-to-peer connection, and an identifier of a logical channel used for transmitting the backhaul adaptation protocol packet to the next-hop apparatus.
In some embodiments, the information associated with the peer-to-peer connection comprises at least one of a routing identifier used for routing the data unit to a next-hop apparatus in the integrated access and backhaul network, an identifier of the peer-to-peer connection, an identifier of a radio bearer used over the access link for the peer-to-peer connection, and an identifier of the second apparatus.
In some embodiments, the peer-to-peer connection emulates a sidelink connection between the second apparatus and the third apparatus, and comprises a sidelink packet data convergence protocol communication layer and a sidelink service data adaptation protocol communication layer terminated at the second apparatus and at the third apparatus and transparently relayed through the integrated access and backhaul network.
In an eighteenth aspect, disclosed is a computer readable medium comprising instructions stored thereon for causing an apparatus as a first apparatus to: receive configuration information from a donor apparatus in an integrated access and backhaul network for a peer-to-peer connection between the first apparatus and a second apparatus via the integrated access and backhaul network; and receive, via an access link and from a third apparatus serving the first apparatus in the integrated access and backhaul network, a data unit of the peer-to-peer connection based on the configuration information.
In some embodiments, the configuration information comprises information on at least one of a radio bearer used over the access link for the peer-to-peer connection, and an identifier of the peer-to-peer connection.
In some embodiments, the instructions further cause the apparatus to determine a radio bearer used for carrying the data unit over the access link based on the configuration information.
In some embodiments, the first apparatus is a user equipment or a mobile termination part of an integrated access and backhaul network node apparatus in the integrated access and backhaul network.
In some embodiments, the peer-to-peer connection emulates a sidelink connection between the first apparatus and the second apparatus, and comprises a sidelink packet data convergence protocol communication layer and a sidelink service data adaptation protocol communication layer terminated at the first apparatus and at the second apparatus and transparently relayed through the integrated access and backhaul network.
In a nineteenth aspect, disclosed is a computer readable medium comprising instructions stored thereon for causing an apparatus as a first apparatus in an integrated access and backhaul network to: receive bearer mapping configuration information from a donor apparatus in the integrated access and backhaul network for a peer-to-peer connection between a second apparatus and a third apparatus served by the first apparatus via the integrated access and backhaul network; receive a backhaul adaptation protocol packet including a backhaul adaptation protocol header and a data unit of the peer-to-peer connection, the backhaul adaptation protocol packet comprising information associated with the peer-to-peer connection; and transmit the data unit to the third apparatus via a first access link based on the bearer mapping configuration information and the backhaul adaptation protocol header.
In some embodiments, the bearer mapping configuration information comprises information on at least one of an identifier of the third apparatus, an identifier of the peer-to-peer connection, an identifier of a radio bearer used over the first access link for the peer-to-peer connection, an identifier of a logical channel used over the first access link for the peer-to-peer connection, and an identifier of the first access link.
In some embodiments, the information associated with the peer-to-peer connection comprises at least one of an identifier of the peer-to-peer connection, an identifier of a radio bearer used over a second access link between the second apparatus and a fourth apparatus serving the second apparatus in the integrated access and backhaul network for the peer-to-peer connection, an identifier of the second access link, and an identifier of the second apparatus.
In some embodiments, the peer-to-peer connection emulates a sidelink connection between the second apparatus and the third apparatus, and comprises a sidelink packet data convergence protocol communication layer and a sidelink service data adaptation protocol communication layer terminated at the second apparatus and at the third apparatus and transparently relayed through the integrated access and backhaul network.
In a twentieth aspect, disclosed is a computer readable medium comprising instructions stored thereon for causing an apparatus as a donor apparatus in an integrated access and backhaul network to: transmit, to a first apparatus, first configuration information for a peer-to-peer connection between the first apparatus and a second apparatus via the integrated access and backhaul network, to enable the first apparatus to transmit a data unit of the peer-to-peer connection via a first access link to a third apparatus serving the first apparatus in the integrated access and backhaul network; transmit, to the second apparatus, second configuration information for the peer-to-peer connection, to enable the second apparatus to receive the data unit via a second access link from a fourth apparatus serving the second apparatus in the integrated access and backhaul network; transmit, to the third apparatus, first routing and bearer mapping configuration information for the peer-to-peer connection; and transmit, to the fourth apparatus, second bearer mapping configuration information for the peer-to-peer connection.
In some embodiments, the at least one memory and the computer program code is configured to, with the at least one processor, further cause the apparatus to receive a request from the first apparatus for establishing the peer-to-peer connection with the second apparatus, the request comprising information on at least one of an identifier of the first apparatus, an identifier of the second apparatus, and an identifier of a data flow associated with the data unit.
In some embodiments, the first configuration information comprises information on at least one of a radio bearer used over the first access link for the peer-to-peer connection, and an identifier of the peer-to-peer connection.
In some embodiments, the second configuration information comprises at least one of information on at least one of a radio bearer used over the second access link for the peer-to-peer connection, and an identifier of the peer-to-peer connection.
In some embodiments, the first routing and bearer mapping configuration information comprises information on at least one of a routing identifier for routing the data unit to a next-hop apparatus in the integrated access and backhaul network, an identifier of the next-hop apparatus, an identifier of the peer-to-peer connection, an identifier of a radio bearer used over the first access link for the peer-to-peer connection, an identifier of a logical channel used over the first access link for the peer-to-peer connection, and an identifier of a logical channel used for transmitting a backhaul adaptation protocol packet carrying the data unit to the next-hop apparatus.
In some embodiments, the second bearer mapping configuration information comprises information on at least one of an identifier of the second apparatus, an identifier of the peer-to-peer connection, an identifier of a radio bearer used over the second access link for the peer-to-peer connection, an identifier of a logical channel used over the second access link for the peer-to-peer connection, and an identifier of the second access link.
In some embodiments, the instructions further cause the apparatus to determine at least one apparatus in the integrated access and backhaul network, the at least one apparatus comprising the third apparatus and the fourth apparatus, and forming a routing path for the peer to peer connection from the first apparatus to the second apparatus bypassing the donor apparatus.
In some embodiments, the peer-to-peer connection emulates a sidelink connection between the first apparatus and the second apparatus, and comprises a sidelink packet data convergence protocol communication layer and a sidelink service data adaptation protocol communication layer terminated at the first apparatus and at the second apparatus and transparently relayed through the integrated access and backhaul network.

BRIEF DESCRIPTION OF THE DRAWINGS

Some embodiments will now be described, by way of non-limiting examples, with reference to the accompanying drawings, where like reference numerals indicate similar or corresponding elements or parts in various accompanying drawings.
FIG. 1 illustrates an example of a peer-to-peer connection between peer IAB nodes in an embodiment.
FIG. 2 illustrates an example of configuration procedure for an expected peer-to-peer connection in an embodiment.
FIG. 3 illustrates an example of protocol stacks at respective nodes involved in an expected peer-to-peer connection.
FIG. 4 illustrates another example of a peer-to-peer connection between peer IAB nodes in an embodiment.
FIG. 5 illustrates another example of configuration procedure for an expected peer-to-peer connection in an embodiment.
FIG. 6 illustrates another example of protocol stacks at respective nodes involved in an expected peer-to-peer connection.
FIG. 7 illustrates an example method for a peer-to-peer communication via an IAB network in an embodiment.
FIG. 8 illustrates an example apparatus for a peer-to-peer communication via an IAB network in an embodiment.
FIG. 9 illustrates an example apparatus for a peer-to-peer communication via an IAB network in an embodiment.
FIG. 10 illustrates an example method for a peer-to-peer communication via an IAB network in an embodiment.
FIG. 11 illustrates an example apparatus for a peer-to-peer communication via an IAB network in an embodiment.
FIG. 12 illustrates an example apparatus for a peer-to-peer communication via an IAB network in an embodiment.
FIG. 13 illustrates an example method for a peer-to-peer communication via an IAB network in an embodiment.
FIG. 14 illustrates an example apparatus for a peer-to-peer communication via an IAB network in an embodiment.
FIG. 15 illustrates an example apparatus for a peer-to-peer communication via an IAB network in an embodiment.
FIG. 16 illustrates an example method for a peer-to-peer communication via an IAB network in an embodiment.
FIG. 17 illustrates an example apparatus for a peer-to-peer communication via an IAB network in an embodiment.
FIG. 18 illustrates an example apparatus for a peer-to-peer communication via an IAB network in an embodiment.
FIG. 19 illustrates an example method for a peer-to-peer communication via an IAB network in an embodiment.
FIG. 20 illustrates an example apparatus for a peer-to-peer communication via an IAB network in an embodiment.
FIG. 21 illustrates an example apparatus for a peer-to-peer communication via an IAB network in an embodiment.

DETAILED DESCRIPTION

An IAB network may be configured with spanning tree (ST) and directed acyclic graph (DAG) topologies, where a donor base station (also referred to as a donor node in the IAB network or an IAB-donor) hosting central unit (CU) functionality and one or more IAB nodes may be included. Centralized mechanisms at the CU of the IAB-donor, which may have an overview of the whole network/path, may be employed for handover decisions, topology change, routing, bearer mapping, and so on. An IAB node may include a mobile termination (MT) part used to communicate with a parent node (e.g. another IAB node serving this IAB node or the IAB-donor) in the IAB network via an uplink (UL) , and a distributed unit (DU) part used to communicate with a child node (e.g. another IAB node served by this IAB node) in the IAB network or a user equipment (UE) served by this IAB node via a downlink (DL) .
Efficient multi-hop forwarding may be enabled via the IAB-specific backhaul adaptation protocol (BAP) , where each IAB node hosting distributed unit (DU) functionality may be assigned, by the IAB-donor, a unique layer 2 (L2) address (BAP address) which is routable from/to the IAB-donor. The BAP of the origin node (IAB-donor DU for the DL traffic, and the access IAB node for the UL traffic) may add a BAP header to its transmitted data packet or data unit. The BAP header may include information for example on a BAP routing identifier (e.g. BAP address of the destination/source IAB node and an optional path identifier) . Each IAB node may have a routing table which may be configured by the IAB-donor CU and may include information on for example the next-hop identifier for each BAP routing identifier. For example, separate routing tables may be kept for the DL and UL directions in an IAB node, where the DL table may be used by the DU part of the IAB node, and the UL table may be used by the MT part of the IAB node. One or more intermediate IAB nodes between an access IAB node for the expected data traffic and the IAB-donor may forward data packets (e.g. service data units or SDUs) based on routing identifiers or destination addresses. Backhaul (BH) radio link control (RLC) channels may be used for transporting data packets between a child IAB node and a parent IAB node or between an IAB node MT and the IAB-donor DU, and a mapping between UE radio bearers and BH RLC channels (e.g. N: 1 mapping and 1: 1 mapping) may be performed based on specific parameters, such as an quality of service (QoS) profile of the bearers.
There are some use cases where an ability of peer IAB nodes (e.g. a branch from the IAB-donor to one of the peer IAB nodes is different from a branch from the IAB-donor to the other of the peer IAB nodes) to directly communicate with each other (e.g. bypassing the IAB-donor) in a mesh topology, which is also called as a peer-to-peer (P2P) communication/connection between the peer IAB nodes, is expected, for example in a form of control plane (CP) signaling to enable more responsive inter-node coordination and/or in a form of user plane (UP) data to reduce UP latency and the path length traversed by the data packets (e.g. when data is to be transmitted locally from a UE served by one IAB node to another UE served by a nearby IAB node) . For example, a PC5 interface (an interface for proximity service direct communication) may be used to implement the P2P connection between peer IAB nodes (e.g. peer IAB MTs of two IAB nodes) or peer UEs accessing the IAB network, for example by using PC5-based sidelink functionality. However, the PC5-based implementation for the P2P connection via the IAB network may involve complex radio resource allocations including allocations both for BH/access links and between sidelink (SL) resources.
In various embodiments of this disclosure, the P2P connection via the IAB network may be implemented via Uu (an interface between the UE and network) interfaces or access links, without using the PC5 interfaces.
FIG. 1 illustrates an example of a P2P connection between peer IAB nodes in an embodiment. In this example, an IAB network may include an IAB-donor 105 and IAB nodes 101, 102, 103, 104 and so on, where the IAB node 102 is a parent node of the IAB node 101 and is a child node of the IAB node 103, the IAB node 104 is another child node of the IAB node 103, and a P2P connection 108 between the MT part 106 of the IAB node 101 and the MT part 107 of the IAB node 104 is expected.
In an embodiment, the IAB-donor 105 may be notified by a request for example from the MT part 106 of the IAB node 101 or the MT part 107 of the IAB node 104 that the P2P connection 108 is expected. For example, such request may include information on one or more of an identifier of the MT part 106 of the IAB node 101 or the IAB node 101 (e.g. the BAP address of the IAB node 101) , an identifier of the MT part 107 of the IAB node 104 or the IAB node 104 (e.g. the BAP address of the IAB node 104) , an identifier of a data flow (e.g. packet flow identifier for a PC5 QoS flow identifying the flow or stream of data packets or SDUs of the P2P connection 108) , and so on. In another embodiment, the IAB-donor 105 may determine the P2P connection 108 for example autonomously and/or in response to a requirement from an application layer, without receiving a request from the MT part 106 of the IAB node 101 or the MT part 107 of the IAB node 104.
As illustrated in FIG. 1, for the expected P2P connection 108, the IAB-donor 105 may determine a path 110 (e.g. the shortest path) between the MT part 106 of the IAB node 101 and the MT part 107 of the IAB node 104 via the IAB nodes 102 and 103, where an access link 111 via a Uu interface/access link (rather than a PC5 interface or a BH link) is used between the MT part 106 of the IAB node 101 and the DU part of the IAB node 102, a BH link 112 is still used between the IAB node 102 and the IAB node 103, and an access link 113 via a Uu interface/access link (rather than a PC5 interface or a BH link) is used between the MT part 107 of the IAB node 104 and the DU part of the IAB node 103.
Further, as illustrated in FIG. 1, the DU part 109 of the IAB node 103 may be configured by the IAB-donor 105 to route the data packets of the P2P connection 108 from the IAB node 102 to the IAB node 104 or from the IAB node 104 to the IAB node 102 based on the routing and mapping configuration information provided by the IAB-donor 105, rather than routing the data packets of the P2P connection 108 to a parent IAB node of the IAB node 103 in the IAB network, and the MT part of the IAB node 103 may be not involved for the P2P connection 108, so that, for example, the path 110 determined for the expected P2P connection 108 may bypass the IAB-donor 105 and/or one or more IAB nodes between the IAB node 103 and the IAB donor 105, and more efficient data communication may be achieved.
It is appreciated that this disclosure is not limited to the example as illustrated in FIG. 1. In different embodiments, depending on the topology of the IAB network and the peer nodes/apparatuses terminating the expected P2P connection, the IAB-donor 105 and/or one or more IAB nodes in the IAB networks may be included in the determined path 110, and one or more IAB nodes, such as the IAB node 103 where the MT part is not involved in the P2P connection and the DU part is configured so that the P2P data from a child IAB node or a served UE is routed to another child IAB node or another served UE rather than a parent IAB node or the IAB donor, may be included in the determined path 110. In another embodiment, an IAB node included in the path determined for a P2P connection may also be configured to route the P2P data from a parent IAB node of the IAB node to another parent IAB node of the IAB node rather than a child IAB node of the IAB node.
FIG. 2 illustrates an example of configuration procedure for the expected P2P connection 108 in an embodiment, where the IAB-donor 105 may determine configuration information for respective IAB nodes included in the path 110, and may transmit configuration information 201, 202, 203, and 204 associated with the P2P connection 108 to the associated IAB nodes 101, 102, 103, and 104, respectively, for example via one or more downlinks in the IAB network, so that the associated IAB nodes 101, 102, 103, and 104 may operate accordingly to implement the P2P connection 108.
For example, the configuration information 201 from the IAB-donor 105 to the MT part 106 of the IAB node 101 may include information for configuring packet data convergence protocol (PDCP) and/or service data adaptation protocol (SDAP) in the IAB node 101, information for configuring RLC, and so on. For example, the information for configuring PDCP and/or SDAP may be used for defining a radio bearer used by the MT part 106 of the IAB node 101 for the P2P connection 108. Also, for example in a case where the radio bearer defined by the PDCP/SDAP configuration for mapping the data packets or SDUs to be transmitted or received by the MT part 106 of the IAB node 101 will be mapped to a separate BH RLC channel in the IAB network (1: 1 mapping) and the BH RLC channel is a part of a BH chain dedicated for the P2P connection via the IAB network, the P2P connection 108 may be indicated or identified implicitly for example based on the PDCP/SDAP configurations.
In another embodiment, the configuration 201 may also include information on an identifier or indication of the P2P connection 108 for identifying or indicating the P2P connection 108 uniquely within the IAB network. For example, the identifier or indication of the P2P connection 108 may be determined/assigned by the IAB-donor 105, or may be determined/assigned by the IAB node 101 (or the MT part 106 of the IAB node 101) for example when requesting the P2P connection 108. In different embodiments, the identifier or indication of the P2P connection 108 may be in any suitable form capable of identifying or indicating the P2P connection 108 uniquely within the IAB network. For example, the identifier or indication of the P2P connection 108 may be a single identifier, a combination of several information items (e.g. a combination of two or more of the BAP address of the IAB node 102 serving the MT part 106 of the IAB node 101, an identifier of the radio bearer mapping the data packets or SDUs to be transmitted or received by the MT part 106 of the IAB node 101, and the BAP address of the IAB node 101) , and so on.
In different embodiments, the configuration information 201 may be transmitted in any suitable form at any suitable timing. For example, in a case where the IAB-donor 105 receives a request from the MT part 106 of the IAB node 101 or the MT part 107 of the IAB node 104 that the P2P connection 108 is expected, the configuration information 201 may be included in a response to the request.
Based on the configuration information 201, for example, the MT part 106 of the IAB node 101 may determine the radio bearer used for transmitting or carrying the data unit over the access link, so as to transmit the data unit of the P2P connection 108 to the IAB node 102 or receive the data unit of the P2P connection 108 from the IAB node 102, corresponding to the P2P data reception or P2P data transmission at the MT part 107 of the IAB node 104.
The configuration information 204 from the IAB-node 105 to the MT part 107 of the IAB node 104 may include one or more information items similar to those in the configuration information 201, and may be in a form similar to that of the configuration information 201. For example, similar to the configuration information 201, the configuration information 204 may also include one or more of information for configuring PDCP and/or SDAP for defining a radio bearer used by the MT part 107 of the IAB node 104 for the P2P connection 108, information for configuring RLC, information on an identifier or indication of the P2P connection 108, and so on. Also, similar to the configuration information 201, for example in a case where the IAB-donor 105 receives a request from the MT part 106 of the IAB node 101 or the MT part 107 of the IAB node 104 that the P2P connection 108 is expected, the configuration information 204 may be included in a response to the request.
Based on the configuration information 204, for example, the MT part 107 of the IAB node 104 may determine the radio bearer used for transmitting or carrying the data unit over the access link, so as to transmit the data unit of the P2P connection 108 to the IAB node 103 or receive the data unit of the P2P connection 108 from the IAB node 103, corresponding to the P2P data reception or P2P data transmission at the MT part 106 of the IAB node 101.
As illustrated in FIG. 2, the IAB-donor 105 may also determine and transmit configuration information 202 to the IAB node 102 which serves the MT part 106 of the IAB node 101 and is included in the determined path 110. For example, the configuration information 202 may provide routing and mapping configuration information to the IAB node 102.
For example, the configuration information 202 may include configuration information for the IAB node 102 in a case where the MT part 106 of the IAB node 101 served by the IAB node 102 transmits data packets via the P2P connection 108 or the path 110 to the MT part 107 of the IAB node 104. In such case, the MT part 106 of IAB node 101 may be at least a part of a transmitting peer apparatus, the MT part 107 of IAB node 104 may be at least a part of a receiving peer apparatus.
For example, the configuration information for the IAB node 102 as a transmitting access IAB node may include, but is not limited to, one or more of: information for configuring RLC channel; at least one routing table for determining a next-hop for the transmitted data packet/unit; an identifier or an indication of the P2P connection 108; an identifier of a radio bearer for the P2P connection 108; information on a mapping of the P2P connection 108 or a radio bearer of the P2P connection 108 to a routing identifier, or an association of an identifier of the P2P connection 108 or the radio bearer of the P2P connection 108 with a RLC channel; at least one mapping table for determining mappings of ingress (P2P) RLC channel to egress RLC channel on the next-hop link for example selected based on the routing table; an association of the identifier of the P2P connection 108 with an identifier of a logical channel such as the RLC channel; an association of the identifier of radio bearer for the P2P connection 108 with the identifier of the logical channel; and so on.
It is appreciated that the information items in the configuration information 202 may be not limited to the above examples. For example, in case of 1: 1 mapping, the P2P connection 108 may be implicit and may be associated with the RLC channel, and thus, the information on the identifier of the P2P connection 108 may be omitted from the configuration information 202. It is appreciated that the configuration information 202 may be in any suitable form or format. For example, the information on association of the identifier of the P2P connection 108 with the identifier of the RLC channel may include or may be expressed by information on the identifier of the P2P connection 108 and the identifier of the RLC channel, or may be an indication/flag configured in a specified field in the configuration information 202.
In addition, the configuration information 202 may also include configuration information for the IAB node 102 in a case where the MT part 106 of the IAB node 101 served by the IAB node 102 receives data packets via the P2P connection 108 or the path 110 from the MT part 107 of the IAB node 104. In such case, the MT part 106 of IAB node 101 may be at least a part of the receiving peer apparatus, the MT part 107 of IAB node 104 may be at least a part of the transmitting peer apparatus. The configuration information for the IAB node 102 in such case may be similar to that for the IAB node 102 acting as a transmitting access IAB node. In an embodiment, for the IAB node 102 acting as a receiving access IAB node, the information on the routing table may be omitted from the configuration information 202. Further, for example in case of 1: 1 mapping, the information on the identifier of the P2P connection 108 may also be omitted from the configuration information 202.
The configuration information 202 may be used by the IAB node 102 for example for mapping and routing data units, generating BAP header (which will be described later) , and so on.
As illustrated in FIG. 2, the IAB-donor 105 may also transmit configuration information 203 to the IAB node 103 serving the MT part 107 of the IAB node 104. Similar to the configuration information 202 for the IAB node 102, the configuration information 203 may include configuration information for the IAB node 103 acting as a transmitting access IAB node and/or configuration information for the IAB node 103 acting as a receiving access IAB node, which may be similar to configuration information for the IAB node 102 acting as a transmitting access IAB node and configuration information for the IAB node 102 acting as a receiving access IAB node, respectively, and will not be repeated here.
Further, as a “special” intermediate IAB node, the IAB node 103 may be configured based on the configuration information 203 from the IAB-donor so that the MT part of the IAB node 103 is not involved for the P2P connection 108 and the routing table for the P2P connection 108 in the DU part 109 of the IAB node 103 includes information on routing from the IAB node 102 (a child IAB node of the IAB node 103) to the IAB node 104 (another child IAB node of the IAB node 103) and/or information on routing from the IAB node 104 to the IAB node 102, rather than a parent IAB node of the IAB node 103, in a case where the data unit is associated with the P2P connection 108.
In addition, as illustrated in FIG. 2, in an embodiment, before the IAB-donor 105 determines and provide configuration information 201 to 204, an operation 205 for service authorization and provisioning may be performed which may also involve a core network (CN) 206. Through the operation 205, for example, any suitable information associated with the P2P service authorization and provisioning, such as PC5 QoS profile and PC5 QoS rule for each PC5 QoS flow (e.g. each being associated with a packet flow identifier or PFI) , may be provided to the MT part 106 of the IAB node 101 and the MT part 107 of the IAB node 104, and also possibly to the IAB-donor 105. Thus, for example, for the data packets of the P2P connection 108, the MT part 106 of the IAB node 101 or the MT part 107 of the IAB node 104, as the transmitting peer apparatus, may map the data packets to a PC5 QoS flow based on the QoS rules received in the operation 205, which may be further mapped to a radio bearer. In an embodiment, the request from the MT part 106 of the IAB node 101 or the MT part 107 of the IAB node 104 to the IAB-donor 105 on the P2P connection 108 may include information on the PC5 QoS flow (e.g. PFI of the flows) .
It is appreciated that the configuration procedure of the P2P connection 108 is not limited to the sequence as illustrated in FIG. 2. In another embodiment, the respective configuration information 201, 202, 203, and 204 may be transmitted from the IAB-donor 105 to respective IAB nodes 101, 102, 103, and 104 in any suitable orders, and any suitable manners may be adopted to ensure that P2P communication via the P2P connection 108 may be performed after respective associated IAB nodes 101, 102, 103, and 104 have been suitably configured. In another embodiment, the respective IAB node 101, 102, 103, or 104 may transmit a response for example to the reception of the respective configuration information 201, 202, 203, or 204.
FIG. 3 illustrates an example of protocol stacks at respective nodes involved in the P2P connection 108, where for the MT part 106 of the IAB node 101 and the MT part 107 of the IAB node 104 involved in the P2P connection 108, the protocol layers may be controlled and configured by the IAB-donor 105 during the configuration phase as illustrated by FIG. 2 for example based on corresponding configuration information from the IAB-donor 105.
As illustrated in FIG. 3, higher P2P protocol layers such as the SDAP layer and PDCP layer may use P2P protocols (e.g. sidelink protocols) for the P2P connection 108, whereas the lower protocol layers (e.g. the RLC layer and the MAC layer) use radio links. On the access links 111 and 113, there are the RLC layer and the media access control (MAC) layer (also a physical layer or PHY layer not illustrated in FIG. 3) , while on the BH links 112, there is also a BAP layer for routing and bearer mapping on RLC channels.
For example in a case where the MT part 106 of the IAB node 101 transmits P2P data to the MT part 107 of the IAB node 104, the MT part 106 of the IAB node 101 may determine a radio bearer used for transmitting the data unit of the P2P connection 108 over the access link 111, for example based on the configuration information 201 as illustrated in FIG. 2, and then may transmit the data unit of the P2P connection 108 to the DU part of the IAB node 102 via the access link 111.
For the data unit received via the access link 111 by the DU part of the IAB node 102, the IAB node 102 (acting as the transmitting access IAB node) may determine, for example based on the radio bearer used for carrying the data unit and the configuration information 202, that this received data unit is associated with the P2P connection 108. Then, the IAB node 102 may generate a BAP packet including an appropriate BAP header and the received data unit in an operation 301.
For example, the BAP header added in the operation 301 may include a routing identifier used for routing the data unit to a next-hop along the peer-to-peer path. In another embodiment, the BAP header added in the operation 301 may also include information for identifying the P2P connection 108 and/or the radio bearer used over the access link 111 for the P2P connection 108. For example, the BAP header added in the operation 301 may include the identifier of the P2P connection 108 which may be a global unique identifier assigned by the IAB-donor 105 and is included in the configuration information 202. In another example, the identifier of the P2P connection 108 may be a combination of two or more information items such as the BAP address of the IAB node 102, an identifier of the radio bearer over the access link 111, the BAP address of the IAB node 101 or an identifier of the MT part 106 of the IAB node 101, and so on. In another embodiment, the BAP header added in the operation 301 may also include information for identifying the radio bearer over the access link 111.
Then, the IAB node 102 may transmit the generated BAP packet to its next-hop (the IAB node 103) via the BH link 112, for example based on the routing table and the mapping table included in the configuration information 202.
In the DU part 109 of the IAB node 103, in response to receiving the BAP packet from the IAB node 102, the IAB node 103 may determine whether the received BAP packet is associated with a P2P connection, for example based on the BAP header of the BAP packet. For example, the DU part 109 of the IAB node 103 may parse the BAP packet in an operation 302 to check an identifier or an indication of a P2P connection.
In a case of determining that the received BAP packet is associated with the P2P connection 108 (e.g. when checking the existence of the identifier or the indication of the P2P connection 108) , the DU part 109 of the IAB node 103, as the access IAB node serving the MT part 107 of the IAB node 104 as the target peer apparatus, may remove the BAP header in the operation 302. Then, for example based on at least one of the BAP header and the configuration information 203, the DU part 109 of the IAB node 103 may determine the identifier of the RLC channel over the access link 113 for the P2P connection 108, and may transmit the data unit obtained from the BAP packet via the determined RLC channel over the access link 113 to the destination of the P2P connection 108 (the MT part 107 of the IAB node 104) .
In a case of determining that the received BAP packet is not associated with the P2P connection 108, for example, the IAB node 103 may forward the received BAP packet to its parent IAB node in the IAB network where the MT part of the IAB node 103 may be involved.
Similarly, in a case where the MT part 107 of the IAB node 104 transmits P2P data to the MT part 106 of the IAB node 101, the MT part 107 of the IAB node 104 may determine a radio bearer used for transmitting the data unit of the P2P connection 108 over the access link 113, for example based on the configuration information 204 as illustrated in FIG. 2, and then may transmit the data unit of the P2P connection 108 to the DU part of the IAB node 103 via the access link 113. It is appreciated that the access link 113 involved in the case where the MT part 107 of the IAB node 104 transmits P2P data to the MT part 106 of the IAB node 101 and the access link 113 involved in the case where the MT part 106 of the IAB node 101 transmits P2P data to the MT part 107 of the IAB node 104 may be either the same or different.
Then, similar to the case where the MT part 106 of the IAB node 101 transmits P2P data to the MT part 107 of the IAB node 104, in the case where the MT part 107 of the IAB node 104 transmits P2P data to the MT part 106 of the IAB node 101, the IAB node 103 (acting as the transmitting access IAB node) may determine, for example based on the radio bearer used for carrying the data unit and the configuration information 203, that this received data unit is associated with the P2P connection 108. Then, the IAB node 103 may generate a BAP packet including a BAP header and the received data unit in an operation 302.
For example, the BAP header added in the operation 302 may include a routing identifier used for routing the data unit to the next-hop. In another embodiment, the BAP header added in the operation 302 may also include information for identifying the P2P connection 108 and/or the radio bearer used over the access link 113 for the P2P connection 108. For example, the BAP header added in the operation 302 may include the identifier of the P2P connection 108 which may be a global unique identifier assigned by the IAB-donor 105 and is included in the configuration information 203. In another example, the identifier of the P2P connection 108 may be a combination of two or more information items such as the BAP address of the IAB node 103, an identifier of the radio bearer over the access link 113, the BAP address of the IAB node 104 or an identifier of the MT part 107 of the IAB node 104, and so on. In another embodiment, the BAP header added in the operation 302 may also include information for identifying the radio bearer over the access link 113.
Then, the IAB node 103 may transmit the generated BAP packet to its next-hop (the IAB node 102) via the BH link 112, for example based on the routing table and the mapping table included in the configuration information 203.
In the DU part of the IAB node 102, in response to receive the BAP packet from the IAB node 103, the IAB node 102 may determine whether the received BAP packet is associated with a P2P connection, for example based on the BAP header of the BAP packet. For example, the DU part of the IAB node 102 may parse the BAP packet in an operation 301 to check an identifier or an indication of a P2P connection.
In a case of determining that the received BAP packet is associated with the P2P connection 108 (e.g. when checking the existence of the identifier or the indication of the P2P connection 108 in the BAP header) , the DU part of the IAB node 102, as the access IAB node serving the MT part 106 of the IAB node 101 as the target peer apparatus, may remove the BAP header in the operation 301. Then, based on at least one of the BAP header and the configuration information 202, for example, the DU part of the IAB node 102 may determine the identifier of the RLC channel over the access link 111 for the P2P connection 108, and may transmit the data unit obtained from the BAP packet via the determined RLC channel over the access link 111 to the destination of the P2P connection 108 (the MT part 106 of the IAB node 101) .
It is appreciated that the access link 111 involved in the case where the MT part 107 of the IAB node 104 transmits P2P data to the MT part 106 of the IAB node 101 and the access link 111 involved in the case where the MT part 106 of the IAB node 101 transmits P2P data to the MT part 107 of the IAB node 104 may be either the same or different. Also, it is appreciated that the BH link 112 involved in the case where the MT part 107 of the IAB node 104 transmits P2P data to the MT part 106 of the IAB node 101 and the BH link 112 involved in the case where the MT part 106 of the IAB node 101 transmits P2P data to the MT part 107 of the IAB node 104 may be either the same or different.
Thus, a P2P connection 108 between the peer apparatuses (the MT part 106 of the IAB node 101 and the MT part 107 of the IAB node 104) in the IAB network may be implemented via access links/Uu interfaces, rather than via the PC5 interfaces.
FIG. 4 illustrates an example of a P2P connection between peer UEs via the IAB network in an embodiment. In this example, an IAB network may include an IAB-donor 405 and IAB nodes 401, 402, 403, 404 and so on, where the IAB node 402 is a parent node of the IAB node 401 and is a child node of the IAB node 403, the IAB node 404 is another child node of the IAB node 403, and a P2P connection 408 between the UE 406 served by the IAB node 401 and the UE 407 served by the IAB node 404 is expected.
In an embodiment, the IAB-donor 405 may be notified by a request for example from the UE 406 or the UE 407 that the P2P connection 408 is expected. For example, such request may include information on one or more of an identifier of the UE 406 or the IAB node 401 (e.g. the BAP address of the IAB node 401) , an identifier of the UE 407 or the IAB node 404 (e.g. the BAP address of the IAB node 404) , an identifier of a data flow (e.g. packet flow identifier for a PC5 QoS flow mapping the data packet or SDU of the P2P connection 408) , and so on. In another embodiment, the IAB-donor 405 may determine the P2P connection 408 for example autonomously and/or in response to a requirement from an application layer, without receiving a request from the UE 406 or the UE 407.
As illustrated in FIG. 4, for the expected P2P connection 408, the IAB-donor 405 may determine a path 410 (e.g. the shortest path) between the UE 406 and the UE 407 via the IAB nodes 401, 402, 403 and 404, where an access link 411 via a Uu interface/access link (rather than a PC interface or a BH link) is used between the UE 406 and the DU part of the IAB node 401, a BH link 412 is used between the IAB node 401 and the IAB node 402, a BH link 413 is used between the IAB node 402 and the IAB node 403, a BH link 413 is used between the IAB node 403 and the IAB node 404, and an access link 415 via a Uu interface/access link (rather than a PC interface) is used between the UE 407 and the DU part of the IAB node 404.
Further, as illustrated in FIG. 4, the DU part 409 of the IAB node 403 may be configured by the IAB-donor 405 to route the data packets of the P2P connection 408 from the UE 406 to the UE 407 or from the UE 407 to the UE 406 based on the routing and mapping configuration information provided by the IAB-donor 405, rather than routing the data packets of the P2P connection 408 to a parent IAB node of the IAB node 403 in the IAB network, and the MT part of the IAB node 403 may be not involved for the P2P connection 408, so that, for example, the path 410 determined for the expected P2P connection 408 may bypass the IAB-donor 405 and/or one or more IAB nodes between the IAB node 403 and the IAB donor 405, and more efficient data communication may be achieved.
It is appreciated that this disclosure is not limited to the example as illustrated in FIG. 4. In different embodiments, depending on the topology of the IAB network and the peer nodes/apparatuses terminating the expected P2P connection, the IAB-donor 405 and/or one or more IAB nodes in the IAB networks may be included in the determined path 410, and one or more IAB nodes, such as the IAB node 403 where the MT part is not involved in the P2P connection and the DU part is configured so that the P2P data from a child IAB node or a served UE is routed to another child IAB node or another served UE rather than a parent IAB node or the IAB donor, may be included in the determined path 410. In another embodiment, an IAB node included in the path determined for a P2P connection may also be configured to route the P2P data from a parent IAB node of the IAB node to another parent IAB node of the IAB node rather than a child IAB node of the IAB node.
FIG. 5 illustrates an example of configuration procedure for the expected P2P connection 408 in an embodiment, where the IAB-node 405 may determine configuration information for the UE 406, the UE 407, and respective IAB nodes included in the path 410, and may transmit configuration information 501, 502, 503, 504, 505, and 506 associated with the P2P connection 408 to the UE 406, the IAB node 401, the IAB node 402, the IAB node 403, the IAB node 404, and the UE 407, respectively, for example via one or more downlinks in the IAB network, so that the UE 406, the IAB node 401, the IAB node 402, the IAB node 403, the IAB node 404, and the UE 407 may operate accordingly to implement the P2P connection 408.
Similar to the configuration information 201, the configuration information 501 from the IAB-donor 405 to the UE 406 may include information for configuring PDCP and/or SDAP in the UE 406, information for configuring RLC, and so on. For example, the information for configuring PDCP and/or SDAP may be used for defining a radio bearer used by the UE 406 for the P2P connection 408. Also, for example in a case where the radio bearer defined by the PDCP/SDAP configuration for mapping the data packets or SDUs to be transmitted or received by the UE 406 will be mapped to a separate BH RLC channel in the IAB network (1: 1 mapping) and the BH RLC channel is a part of a BH chain dedicated for the P2P connection via the IAB network, the P2P connection 408 may be indicated or identified implicitly for example based on the PDCP/SDAP configurations.
In another embodiment, the configuration 501 may also include information on an identifier or indication of the P2P connection 408 for identifying or indicating the P2P connection 408 uniquely within the IAB network. For example, the identifier or indication of the P2P connection 408 may be determined/assigned by the IAB-donor 405, or may be determined/assigned by the UE 406 for example when requesting the P2P connection 408. In different embodiments, the identifier or indication of the P2P connection 408 may be in any suitable form capable of identify or indicate P2P connection 408 uniquely within the IAB network. For example, the identifier or indication of the P2P connection 408 may be a single identifier, a combination of several information items (e.g. a combination of two or more of the BAP address of the IAB node 401 serving the UE 406, an identifier of the radio bearer mapping the data packets or SDUs to be transmitted or received by the UE 406, and the identifier of the UE 406) , and so on.
In different embodiments, the configuration information 501 may be transmitted in any suitable form at any suitable timing. For example, in a case where the IAB-donor 405 receives a request from the UE 406 or the UE 407 that the P2P connection 408 is expected, the configuration information 501 may be included in a response to the request.
Based on the configuration information 501, for example, the UE 406 may determine the radio bearer used for transmitting or carrying the data unit over the access link, so as to transmit the data unit of the P2P connection 408 to the IAB node 401 or receive the data unit of the P2P connection 408 from the IAB node 401, corresponding to the P2P data reception or P2P data transmission at the UE 406.
The configuration information 506 from the IAB-node 405 to the UE 407 may include one or more information items similar to those in the configuration information 501, and may be in a form similar to that of the configuration information 501. For example, similar to the configuration information 501, the configuration information 506 may also include one or more of information for configuring PDCP and/or SDAP for defining a radio bearer used by the UE 407 for the P2P connection 408, information for configuring RLC, information on an identifier or indication of the P2P connection 408, and so on. Also, similar to the configuration information 501, for example in a case where the IAB-donor 405 receives a request from the UE 406 or the UE 407 that the P2P connection 408 is expected, the configuration information 506 may be included in a response to the request.
Based on the configuration information 506, for example, the UE 407 may determine the radio bearer used for transmitting or carrying the data unit over the access link, so as to transmit the data unit of the P2P connection 408 to the IAB node 404 or receive the data unit of the P2P connection 408 from the IAB node 404, corresponding to the P2P data reception or P2P data transmission at the UE 407.
As illustrated in FIG. 5, the IAB-donor 405 may also determine and transmit configuration information 502 to the IAB node 401 which serves the UE 406 and is included in the determined path 410. For example, the configuration information 502 may provide routing and mapping configuration information to the IAB node 401.
For example, the configuration information 502 may include configuration information for the IAB node 401 in a case where the UE 406 transmits data packets via the P2P connection 408 or the path 410 to the UE 407. In such case, the UE 406 may be at least a part of a transmitting peer apparatus, the UE 407 may be at least a part of a receiving peer apparatus.
For example, the configuration information for the IAB node 401 as a transmitting access IAB node may include, but is not limited to, one or more of: information for configuring RLC channel; at least one routing table for determining a next-hop for the transmitted data packet/unit; an identifier or an indication of the P2P connection 408; an identifier of a radio bearer for the P2P connection 408; information on a mapping of the P2P connection 408 or a radio bearer of the P2P connection 408 to a routing identifier, or an association of an identifier of the P2P connection 408 or the radio bearer of the P2P connection 408 with a RLC channel; at least one mapping table for determining mappings of ingress (P2P) RLC channel to egress RLC channel on the next-hop link for example selected based on the routing table; an association of the identifier of the P2P connection 408 with an identifier of a logical channel such as the RLC channel; an association of the identifier of radio bearer for the P2P connection 408 with the identifier of the logical channel; and so on.
It is appreciated that the information items in the configuration information 502 may be not limited to the above examples. For example, in case of 1: 1 mapping, the P2P connection 408 may be implicit and may be associated with the RLC channel, and thus, the information on the identifier of the P2P connection 408 may be omitted from the configuration information 502. It is appreciated that the configuration information 502 may be in any suitable form or format. For example, the information on association of the identifier of the P2P connection 408 with the identifier of the RLC channel may include or may be expressed by information on the identifier of the P2P connection 408 and the identifier of the RLC channel, or may be an indication/flag configured in a specified field in the configuration information 502.
In addition, the configuration information 502 may also include configuration information for the IAB node 401 in a case where the UE 406 receives data packets via the P2P connection 408 or the path 410 from the UE 407. In such case, the UE 406 may be at least a part of the receiving peer apparatus, the UE 407 may be at least a part of the transmitting peer apparatus. The configuration information for the IAB node 401 in such case may be similar to that for the IAB node 401 acting as a transmitting access IAB node. In an embodiment, for the IAB node 401 acting as a receiving access IAB node, the information on the routing table may be omitted from the configuration information 502. Further, for example in case of 1: 1 mapping, the information on the identifier of the P2P connection 408 may also be omitted from the configuration information 502.
The configuration information 502 may used by the IAB node 401 for example for mapping and routing data units, generating BAP header (which will be described later) , and so on.
As illustrated in FIG. 5, the IAB-donor 405 may also transmit configuration information 505 to the IAB node 404 serving the UE 407. Similar to the configuration information 502 for the IAB node 401, the configuration information 505 may include configuration information for the IAB node 404 acting as a transmitting access IAB node and/or configuration information for the IAB node 404 acting as a receiving access IAB node, which may be similar to configuration information for the IAB node 401 acting as a transmitting access IAB node and configuration information for the IAB node 401 acting as a receiving access IAB node, respectively, and will not be repeated here.
Further, as illustrated in FIG. 5, the IAB-donor 406 may also transmit configuration information 503 and 505 to the intermediate IAB nodes 402 and 403, respectively. For example, the configuration information 503 and 505 may include routing and bearer mapping configuration which is used by the IAB nodes 402 and 403, respectively, to forward the BAP packets to the next-hop. As a “special” intermediate IAB node, the IAB node 403 may be configured based on the configuration information 504 from the IAB-donor so that the MT part of the IAB node 403 is not involved for the P2P connection 408 and the routing table for the P2P connection 408 in the DU part 409 of the IAB node 403 includes information on routing from the IAB node 402 (a child IAB node of the IAB node 403) to the IAB node 404 (another child IAB node of the IAB node 403) and/or information on routing from the IAB node 404 to the IAB node 402, rather than a parent IAB node of the IAB node 403, in a case where the data unit is associated with the P2P connection 408.
In addition, as illustrated in FIG. 5, in an embodiment, before the IAB-donor 405 determines and provide configuration information 501 to 506, an operation 507 for service authorization and provisioning may be performed which may also involve a core network (CN) 508. Through the operation 508, for example, any suitable information associated with the P2P service authorization and provisioning, such as PC5 QoS profile and PC5 QoS rule for each PC5 QoS flow (e.g. each being associated with a packet flow identifier or PFI) , may be provided to the UE 406 and the UE 407, and also possibly to the IAB-donor 405. Thus, for example, for the data packets of the P2P connection 408, the UE 406 or the UE 407, as the transmitting peer apparatus, may map the data packets to a PC5 QoS flow based on the QoS rules received in the operation 507, which may be further mapped to a radio bearer. In an embodiment, the request from the UE 406 or the UE 407 to the IAB-donor 405 on the P2P connection 408 may include information on the PC5 QoS flow (e.g. PFI of the flows) .
It is appreciated that the configuration procedure of the P2P connection 408 is not limited to the sequence as illustrated in FIG. 5. In another embodiment, the respective configuration information 501 to 506 may be transmitted from the IAB-donor 405 in any suitable orders, and any suitable manners may be adopted to ensure that P2P communication via the P2P connection 408 may be performed after respective UEs and IAB nodes have been suitably configured.
FIG. 6 illustrates an example of protocol stacks at respective nodes involved in the P2P connection 408, where for the UE 406 and the UE 407, the protocol layers may be controlled and configured by the IAB nodes 401 and 404, respectively, during the configuration phase as illustrated by FIG. 5 for example based on corresponding configuration information from the IAB-donor 405.
As illustrated in FIG. 6, higher P2P protocol layers such as the SDAP layer and PDCP layer may use P2P protocols (e.g. sidelink protocols) for the P2P connection 408, whereas the lower protocol layers (e.g. the RLC layer and the MAC layer) use radio links. On the access links 411 and 415, there are the RLC layer and the media access control (MAC) layer (also a physical layer or PHY layer not illustrated in FIG. 6) , while on the BH links 412, 413, and 414, there is also BAP layers for routing bearer mapping on RLC channels.
For example in a case where the UE 406 transmits P2P data to the UE 407, the UE 406 may determine a radio bearer used for transmitting the data unit of the P2P connection 408 over the access link 411, for example based on the configuration information 501 as illustrated in FIG. 5, and then may transmit the data unit of the P2P connection 408 to the DU part of the IAB node 401 via the access link 411.
For the data unit received via the access link 411 by the DU part of the IAB node 401, the IAB node 401 (acting as the transmitting access IAB node) may determine, for example based on the radio bearer used for carrying the data unit and the configuration information 502, that this received data unit is associated with the P2P connection 408. Then, the IAB node 401 may generate a BAP packet including a BAP header and the received data unit in an operation 601.
For example, the BAP header added in the operation 601 may include a routing identifier used for routing the data unit to the next-hop (e.g. the IAB node 402) . In another embodiment, the BAP header added in the operation 601 may also include information for identifying the P2P connection 408 and/or the radio bearer used over the access link 411 for the P2P connection 408. For example, the BAP header added in the operation 601 may include the identifier of the P2P connection 408 which may be a global unique identifier assigned by the IAB-donor 405 and is included in the configuration information 502. In another example, the identifier of the P2P connection 408 may be a combination of two or more information items such as the BAP address of the IAB node 401, an identifier of the radio bearer over the access link 411, an identifier of the UE 406, and so on. In another embodiment, the BAP header added in the operation 601 may also include information for identifying the radio bearer over the access link 411.
Then, the IAB node 401 may transmit the generated BAP packet to its next-hop (the IAB node 402) via the BH link 412, for example based on the routing table and the mapping table included in the configuration information 503.
The intermediate IAB node 402 may forward the received BAP packet for the P2P connection 408 to its next-hop (the IAB node 403) via the BH link 413, for example based on the routing table and the mapping table included in the configuration information 504.
In the DU part 409 of the IAB node 403, in response to receive the BAP packet from the IAB node 402, the IAB node 403 may determine whether the received BAP packet is associated with a P2P connection, for example based on the BAP header of the BAP packet. For example, the DU part 409 of the IAB node 403 may parse the BAP packet to check an identifier or an indication of a P2P connection. For example, in a case of determining that the received BAP packet is associated with the P2P connection 408 (e.g. when checking the existence of the identifier or the indication of the P2P connection 408) , the DU part 409 of the IAB node 403 may forward the received BAP packet to its next-hop (the IAB node 404) for example based on the routing table and the mapping table included in the configuration information 504, where, as illustrated in FIG. 6, the MT part of the “special” intermediate IAB node 403 is not involved in the P2P connection 408, and thus the BAP packet for the P2P connection 408 is routed by the IAB node 403 from its child IAB node 402 to its another child IAB node 404 so that the IAB-donor 405 is bypassed.
Then, the MT part of the IAB node 404 receives the BAP packet from the IAB node 403. As the access IAB node serving the UE 407 as the target peer apparatus, the IAB node 404 may remove the BAP header in the operation 602. Then, for example based on at least one of the BAP header and the configuration information 505, the DU part of the IAB node 404 may determine the identifier of the RLC channel over the access link 415 for the P2P connection 408, and may transmit the data unit obtained from the BAP packet via the determined RLC channel over the access link 415 to the destination of the P2P connection 408 (the UE 407) .
Similarly, in a case where the UE 407 transmits P2P data to the UE 406, the UE 407 may determine a radio bearer used for transmitting the data unit of the P2P connection 408 over the access link 415, for example based on the configuration information 506 as illustrated in FIG. 5, and then may transmit the data unit of the P2P connection 408 to the DU part of the IAB node 404 via the access link 415. It is appreciated that the access link 415 involved in the case where the UE 407 transmits P2P data to the UE 406 and the access link 415 involved in the case where the UE 406 transmits P2P data to the UE 407 may be either the same or different.
Then, the IAB node 404 (acting as the transmitting access IAB node) may determine, for example based on the radio bearer used for carrying the data unit and the configuration information 505, that this received data unit is associated with the P2P connection 408. Then, the IAB node 404 may generate a BAP packet including a BAP header and the received data unit in an operation 602.
For example, the BAP header added in the operation 602 may include a routing identifier used for routing the data unit to the next-hop. In another embodiment, the BAP header added in the operation 602 may also include information for identifying the P2P connection 408 and/or the radio bearer used over the access link 415 for the P2P connection 408. For example, the BAP header added in the operation 602 may include the identifier of the P2P connection 408 which may be a global unique identifier assigned by the IAB-donor 405 and is included in the configuration information 505. In another example, the identifier of the P2P connection 408 may be a combination of two or more information items such as the BAP address of the IAB node 404, an identifier of the radio bearer over the access link 415, an identifier of the UE 407, and so on. In another embodiment, the BAP header added in the operation 602 may also include information for identifying the radio bearer over the access link 415.
Then, the IAB node 404 may transmit the generated BAP packet to its next-hop IAB node 403 via the BH link 414 for example based on the routing table and the mapping table included in the configuration information 505. The IAB node 403 may transmit the received BAP packet to its child IAB node 402 via the BH link 413 for example based on the routing table and the mapping table included in the configuration information 504 in a case of determining the BAP packet from its another child IAB node 404 as P2P data. The IAB node 402 may further forward the BAP packet from the IAB node 403 to its next-hop, the IAB node 402, for example based on the routing table and the mapping table included in the configuration information 503.
In the DU part of the IAB node 401, in response to receive the BAP packet from the IAB node 402, the IAB node 401 may determine whether the received BAP packet is associated with a P2P connection, for example based on the BAP header of the BAP packet. For example, the DU part of the IAB node 401 may parse the BAP packet in an operation 601 to check an identifier or an indication of a P2P connection.
In a case of determining that the received BAP packet is associated with the P2P connection 408 (e.g. when checking the existence of the identifier or the indication of the P2P connection 408 in the BAP header) , the DU part of the IAB node 401, as the access IAB node serving the target apparatus UE 406, may remove the BAP header in the operation 601. Then, based on at least one of the BAP header and the configuration information 502, for example, the DU part of the IAB node 401 may determine the identifier of the RLC channel over the access link 411 for the P2P connection 408, and may transmit the data unit obtained from the BAP packet via the determined RLC channel over the access link 411 to the destination of the P2P connection 408 (the UE 406) .
It is appreciated that the access link 411 involved in the case where the UE 407 transmits P2P data to the UE 406 and the access link 411 involved in the case where the UE 406 transmits P2P data to the UE 407 may be either the same or different. Also, it is appreciated that the BH links 412, 413, and 414 involved in the case where the UE 407 transmits P2P data to the UE 406 and the BH links 412, 413, and 414 involved in the case where the UE 406 transmits P2P data to the UE 407 may be either the same or different, respectively.
Thus, a P2P connection 408 between the peer apparatuses (the UE 406 and the UE 407) via the IAB network may be implemented via access links/Uu interfaces, rather than via the PC5 interfaces.
As illustrated in the above examples, direct communication between peer IAB nodes or peer UEs may enabled, where P2P is on higher protocol layers with no changes, and Uu/access links are used at lower layers rather than the PC5 radio connections which may result in complex processing.
It is appreciated that this disclosure is not limited to the above examples. For example, in an embodiment, P2P automatic repeat request (ARQ) in RLC may also be used between the peer apparatuses, for example between the MT part 106 of the IAB node 101 and the MT part 107 of the IAB node 104 or between the UE 406 and the UE 407, in addition to the “hop-by-hop” ARQ on the intermediate links.
Throughout this disclosure, modifiers such as “first” , “second” , “third” , and “fourth” are used to distinguish different entities/apparatuses/parts/operations/elements in an embodiment, rather than intending to refer to a specific entity/apparatus/part/operation/element throughout various embodiments. For example, a “first apparatus” and a “second apparatus” may refer to a transmitting peer apparatus and a receiving peer apparatus in an embodiment, a transmitting peer apparatus and a transmitting access apparatus in another embodiment, a transmitting peer apparatus and a receiving access apparatus in yet another embodiment, or the like. For example, a “first apparatus” may refer to a transmitting peer apparatus in an embodiment, a receiving peer apparatus in another embodiment, a transmitting access apparatus in yet another embodiment, or the like. Similarly, for example, a “second apparatus” may refer to a transmitting peer apparatus in an embodiment, a receiving peer apparatus in another embodiment, a transmitting access apparatus in yet another embodiment, or the like. For example, a transmitting peer apparatus as a first apparatus in an embodiment may be referred to as a second apparatus in another embodiment. Similarly, a receiving access apparatus as a third apparatus in an embodiment may be referred to as a first apparatus in another embodiment.
FIG. 7 illustrates an example method 700 for P2P communication via an IAB network in an embodiment, which may be performed in a donor apparatus as at least a part of an IAB-donor such as the IAB donor 105 or 405 in the above examples. As illustrated in FIG. 7, the example method 700 may include an operation 701, an operation 702, an operation 703, and an operation 704.
In the operation 701, donor apparatus may transmit, to a first apparatus (for example, the MT part 106 of the IAB node 101 as a transmitting peer apparatus, the MT part 107 of the IAB node 104 as a transmitting peer apparatus, the UE 406 as a transmitting peer apparatus, and the UE 407 as a transmitting peer apparatus in the above examples) , first configuration information (for example, the configuration information 201 when the MT part 106 of the IAB node 101 is a transmitting peer apparatus, the configuration information 204 when the MT part 107 of the IAB node 104 is a transmitting peer apparatus, the configuration information 501 when the UE 406 is a transmitting peer apparatus, and the configuration information 506 when the UE 407 is a transmitting peer apparatus in the above examples) for a P2P connection (for example the P2P connection 108 or 408 in the above examples) between the first apparatus and a second apparatus (for example, the MT part 106 of the IAB node 101 as a receiving peer apparatus, the MT part 107 of the IAB node 104 as a receiving peer apparatus, the UE 406 as a receiving peer apparatus, and the UE 407 as a receiving peer apparatus in the above examples) via the IAB network, to enable the first apparatus to transmit a data unit of the P2P connection via a first access link (for example, the access link 111 when the MT part 106 of the IAB node 101 is a transmitting peer apparatus, the access link 113 when the MT part 107 of the IAB node 104 is a transmitting peer apparatus, the access link 411 when the UE 406 is a transmitting peer apparatus, and the access link 415 when the UE 407 is a transmitting peer apparatus in the above examples) to a third apparatus (for example, at least a part of IAB node 102 when the MT part 106 of the IAB node 101 is a transmitting peer apparatus, at least a part of IAB node 103 when the MT part 107 of the IAB node 104 is a transmitting peer apparatus, at least a part of IAB node 401 when the UE 406 is a transmitting peer apparatus, and at least a part of IAB node 404 when the UE 407 is a transmitting peer apparatus in the above examples) serving the first apparatus in the IAB network.
In the operation 702, the donor apparatus may transmit, to the second apparatus, second configuration information (for example, the configuration information 204 when the MT part 107 of the IAB node 104 is a receiving peer apparatus, the configuration information 201 when the MT part 106 of the IAB node 101 is a receiving peer apparatus, the configuration information 501 when the UE 406 is a receiving peer apparatus, and the configuration information 506 when the UE 407 is a receiving peer apparatus in the above examples) for the P2P connection, to enable the second apparatus to receive the data unit via a second access link (for example, the access link 113 when the MT part 107 of the IAB node 104 is a receiving peer apparatus, the access link 111 when the MT part 106 of the IAB node 101 is a receiving peer apparatus, the access link 411 when the UE 406 is a receiving peer apparatus, and the access link 415 when the UE 407 is a receiving peer apparatus in the above examples) from a fourth apparatus (for example, at least a part of IAB node 103 when the MT part 107 of the IAB node 104 is a receiving peer apparatus, at least a part of IAB node 102 when the MT part 106 of the IAB node 101 is a receiving peer apparatus, at least a part of IAB node 401 when the UE 406 is a receiving peer apparatus, and at least a part of IAB node 404 when the UE 407 is a receiving peer apparatus in the above examples) serving the second apparatus in the IAB network.
Further, in the operation 703, the donor apparatus may transmit, to the third apparatus, first routing and bearer mapping configuration information (for example, the configuration information 202 when the MT part 106 of the IAB node 101 is a transmitting peer apparatus, the configuration information 203 when the MT part 107 of the IAB node 104 is a transmitting peer apparatus, the configuration information 502 when the UE 406 is a transmitting peer apparatus, and the configuration information 505 when the UE 407 is a transmitting peer apparatus in the above examples) for the P2P connection.
In addition, in the operation 704, the donor apparatus may transmit, to the fourth apparatus, second bearer mapping configuration information (for example, the configuration information 203 when the MT part 107 of the IAB node 104 is a receiving peer apparatus, the configuration information 202 when the MT part 106 of the IAB node 101 is a receiving peer apparatus, the configuration information 502 when the UE 406 is a receiving peer apparatus, and the configuration information 505 when the UE 407 is a receiving peer apparatus in the above examples) for the P2P connection.
In some embodiments, the example method 700 may further include an operation of receiving a request from the first apparatus for establishing the P2P connection with the second apparatus. For example, the request may include information on at least one of an identifier of the first apparatus, an identifier of the second apparatus, and an identifier of a data flow associated with the data unit.
In some embodiments, the first configuration information may include information on at least one of a radio bearer used over the first access link for the P2P connection, and an identifier of the P2P connection.
In some embodiments, the second configuration information may include at least one of information on at least one of a radio bearer used over the second access link for the P2P connection, and an identifier of the P2P connection.
In some embodiments, the first routing and bearer mapping configuration information may include information on at least one of a routing identifier for routing the data unit to a next-hop apparatus in the IAB network, an identifier of the next-hop apparatus, an identifier of the P2P connection, an identifier of a radio bearer used over the first access link for the P2P connection, an identifier of a logical channel used over the first access link for the P2P connection, an identifier of a logical channel used for transmitting a BAP packet carrying the data unit to the next-hop apparatus.
In some embodiments, the second bearer mapping configuration information may include information on at least one of an identifier of the second apparatus, an identifier of the P2P connection, an identifier of a radio bearer used over the second access link for the P2P connection, an identifier of a logical channel used over the second access link for the P2P connection, an identifier of the second access link.
In some embodiments, the example method 700 may further include an operation of determining at least one apparatus in the IAB network where the at least one apparatus may include the third apparatus and the fourth apparatus, and may form a routing path (e.g. the paths 110 and 410 in the above examples) for the P2P connection from the first apparatus to the second apparatus bypassing the donor apparatus.
In some embodiments, the P2P connection may emulate a sidelink connection between the first apparatus and the second apparatus, and may include a sidelink PDCP communication layer and a sidelink SDAP communication layer terminated at the first apparatus and at the second apparatus and transparently relayed through the IAB network as shown in FIG. 3 and 6.
FIG. 8 illustrates an example apparatus 800 for P2P communication via an IAB network in an embodiment, which may be at least a part of an IAB-donor such as the IAB donor 105 or 405 in the above examples.
As shown in FIG. 8, the example apparatus 800 may include at least one processor 801 and at least one memory 802 that may include computer program code 803. The at least one memory 802 and the computer program code 803 may be configured to, with the at least one processor 801, cause the apparatus 800 at least to perform at least the operations of the example method 700 described above.
In various embodiments, the at least one processor 801 in the example apparatus 800 may include, but not limited to, at least one hardware processor, including at least one microprocessor such as a central processing unit (CPU) , a portion of at least one hardware processor, and any other suitable dedicated processor such as those developed based on for example Field Programmable Gate Array (FPGA) and Application Specific Integrated Circuit (ASIC) . Further, the at least one processor 801 may also include at least one other circuitry or element not shown in FIG. 8.
In various embodiments, the at least one memory 802 in the example apparatus 800 may include at least one storage medium in various forms, such as a volatile memory and/or a non-volatile memory. The volatile memory may include, but not limited to, for example, a random-access memory (RAM) , a cache, and so on. The non-volatile memory may include, but not limited to, for example, a read only memory (ROM) , a hard disk, a flash memory, and so on. Further, the at least memory 802 may include, but are not limited to, an electric, a magnetic, an optical, an electromagnetic, an infrared, or a semiconductor system, apparatus, or device or any combination of the above.
Further, in various embodiments, the example apparatus 800 may also include at least one other circuitry, element, and interface, for example at least one I/O interface, at least one antenna element, and the like.
In various embodiments, the circuitries, parts, elements, and interfaces in the example apparatus 800, including the at least one processor 801 and the at least one memory 802, may be coupled together via any suitable connections including, but not limited to, buses, crossbars, wiring and/or wireless lines, in any suitable ways, for example electrically, magnetically, optically, electromagnetically, and the like.
FIG. 9 illustrates an example apparatus 900 for P2P communication via an IAB network in an embodiment, which may be at least a part of an IAB-donor such as the IAB donor 105 or 405 in the above examples.
As shown in FIG. 9, the example apparatus 900 may include means for performing operations of the example method 700 described above in various embodiments. For example, the apparatus 900 may include means 901 for performing the operation 701 of the example method 700, means 902 for performing the operation 702 of the example method 700, means 903 for performing the operation 703 of the example method 700, and means 904 for performing the operation 704 of the example method 700. In one or more another embodiment, at least one I/O interface, at least one antenna element, and the like may also be included in the example apparatus 900. In some embodiments, examples of means in the apparatus 900 may include circuitries. In some embodiments, examples of means may also include software modules and any other suitable function entities. In some embodiments, one or more additional means may be included in the apparatus 900 for performing one or more additional operations of the example method 700.
The term “circuitry” throughout this disclosure may refer to one or more or all of the following: (a) hardware-only circuit implementations (such as implementations in only analog and/or digital circuitry) ; (b) combinations of hardware circuits and software, such as (as applicable) (i) a combination of analog and/or digital hardware circuit (s) with software/firmware and (ii) any portions of hardware processor (s) with software (including digital signal processor (s) ) , software, and memory (ies) that work together to cause an apparatus, such as a mobile phone or server, to perforvarious functions) ; and (c) hardware circuit (s) and or processor (s) , such as a microprocessor (s) or a portion of a microprocessor (s) , that requires software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation. This definition of circuitry applies to one or all uses of this terin this disclosure, including in any claims. As a further example, as used in this disclosure, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and/or firmware. The term circuitry also covers, for example and if applicable to the claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device.
FIG. 10 illustrates an example method 1000 for P2P communication via an IAB network in an embodiment, which may be performed in a first apparatus as at least a part of a transmitting peer apparatus such as the MT part 106 of the IAB node 101 when acting as a transmitting peer apparatus, at least a part of the MT part 107 of the IAB node 104 when acting as a transmitting peer apparatus, at least a part of the UE 406 when acting as a transmitting peer apparatus, and at least a part of the UE 407 when acting as a transmitting peer apparatus. As illustrated in FIG. 10, the example method 1000 may include an operation 1001 and an operation 1002.
In the operation 1001, the first apparatus may receive configuration information (e.g. the configuration information 201 when the MT part 106 of the IAB node 101 is the transmitting peer apparatus, the configuration information 204 when the MT part 107 of the IAB node 104 is the transmitting peer apparatus, the configuration information 501 when the UE 406 is the transmitting peer apparatus, and the configuration 506 when the UE 407 is the transmitting peer apparatus) from a donor apparatus (e.g. the example apparatus 800 and 900 performing the example method 700) in the IAB network for a P2P connection (e.g. the P2P connection 108 or 408) between the first apparatus and a second apparatus (e.g. at least a part of the MT part 106 of the IAB node 101 when acting as a receiving peer apparatus, at least a part of the MT part 107 of the IAB node 104 when acting as a receiving peer apparatus, at least a part of the UE 406 when acting as a receiving peer apparatus, and at least a part of the UE 407 when acting as a receiving peer apparatus) via the IAB network.
Then, in the operation 1002, the first apparatus may transmit, via an access link (e.g. the access link 111 when the MT part 106 of the IAB node 101 is the transmitting peer apparatus, the access link 113 when the MT part 107 of the IAB node 104 is the transmitting peer apparatus, the access link 411 when the UE 406 is the transmitting peer apparatus, and the access link 415 when the UE 407 is the transmitting peer apparatus) and to a third apparatus (e.g. at least a part of the IAB node 102 when the MT part 106 of the IAB node 101 is the transmitting peer apparatus, at least a part of the IAB node 103 when the MT part 107 of the IAB node 104 is the transmitting peer apparatus, at least a part of the IAB node 401 when the UE 406 is the transmitting peer apparatus, and at least a part of the IAB node 404 when the UE 407 is the transmitting peer apparatus) serving the first apparatus in the IAB network, a data unit of the P2P connection based on the configuration information received in the operation 1001.
In some embodiments, the example method 1000 may further include an operation of transmitting a request for establishing the P2P connection with the second apparatus. For example, the request may include information on at least one of an identifier of the first apparatus, an identifier of the second apparatus, and an identifier of a data flow associated with the data unit.
In some embodiments, the configuration information received in the operation 1001 may include information on at least one of a radio bearer used over the access link for the P2P connection, and an identifier of the P2P connection.
In some embodiments, the example method 1000 may further include an operation of determining a radio bearer used for transmitting the data unit over the access link based on the configuration information received in the operation 1001.
In some embodiments, the P2P connection may emulate a sidelink connection between the first apparatus and the second apparatus, and may include a sidelink PDCP communication layer and a sidelink SDAP communication layer terminated at the first apparatus and at the second apparatus and transparently relayed through the IAB network.
FIG. 11 illustrates an example apparatus 1100 for P2P communication via an IAB network in an embodiment, which may be a first apparatus as at least a part of a transmitting peer apparatus such as the MT part 106 of the IAB node 101 when acting as a transmitting peer apparatus, at least a part of the MT part 107 of the IAB node 104 when acting as a transmitting peer apparatus, at least a part of the UE 406 when acting as a transmitting peer apparatus, and at least a part of the UE 407 when acting as a transmitting peer apparatus.
As shown in FIG. 1100, the example apparatus 1100 may include at least one processor 1101 and at least one memory 1102 that may include computer program code 1103. The at least one memory 1102 and the computer program code 1103 may be configured to, with the at least one processor 1101, cause the apparatus 1100 at least to perform at least the operations of the example method 1000 described above.
In various embodiments, the at least one processor 1101 in the example apparatus 1100 may include, but not limited to, at least one hardware processor, including at least one microprocessor such as a CPU, a portion of at least one hardware processor, and any other suitable dedicated processor such as those developed based on for example FPGA and ASIC. Further, the at least one processor 1101 may also include at least one other circuitry or element not shown in FIG. 11.
In various embodiments, the at least one memory 1102 in the example apparatus 1100 may include at least one storage medium in various forms, such as a volatile memory and/or a non-volatile memory. The volatile memory may include, but not limited to, for example, a RAM, a cache, and so on. The non-volatile memory may include, but not limited to, for example, a ROM, a hard disk, a flash memory, and so on. Further, the at least memory 1102 may include, but are not limited to, an electric, a magnetic, an optical, an electromagnetic, an infrared, or a semiconductor system, apparatus, or device or any combination of the above.
Further, in various embodiments, the example apparatus 1100 may also include at least one other circuitry, element, and interface, for example at least one I/O interface, at least one antenna element, and the like.
In various embodiments, the circuitries, parts, elements, and interfaces in the example apparatus 1100, including the at least one processor 1101 and the at least one memory 1102, may be coupled together via any suitable connections including, but not limited to, buses, crossbars, wiring and/or wireless lines, in any suitable ways, for example electrically, magnetically, optically, electromagnetically, and the like.
FIG. 12 illustrates an example apparatus 1200 for P2P communication via an IAB network in an embodiment, which may be a first apparatus as at least a part of a transmitting peer apparatus such as the MT part 106 of the IAB node 101 when acting as a transmitting peer apparatus, at least a part of the MT part 107 of the IAB node 104 when acting as a transmitting peer apparatus, at least a part of the UE 406 when acting as a transmitting peer apparatus, and at least a part of the UE 407 when acting as a transmitting peer apparatus.
As shown in FIG. 12, the example apparatus 1200 may include means for performing operations of the example method 1000 described above in various embodiments. For example, the apparatus 1200 may include means 1201 for performing the operation 1001 of the example method 1000 and means 1202 for performing the operation 1002 of the example method 1000. In one or more another embodiment, at least one I/O interface, at least one antenna element, and the like may also be included in the example apparatus 1200. In some embodiments, examples of means in the apparatus 1200 may include circuitries. In some embodiments, examples of means may also include software modules and any other suitable function entities. In some embodiments, one or more additional means may be included in the apparatus 1200 for performing one or more additional operations of the example method 1000.
FIG. 13 illustrates an example method 1300 for P2P communication via an IAB network in an embodiment, which may be performed in a first apparatus as at least a part of a receiving peer apparatus such as the MT part 106 of the IAB node 101 when acting as a receiving peer apparatus, at least a part of the MT part 107 of the IAB node 104 when acting as a receiving peer apparatus, at least a part of the UE 406 when acting as a receiving peer apparatus, and at least a part of the UE 407 when acting as a receiving peer apparatus. As illustrated in FIG. 13, the example method 1300 may include an operation 1301 and an operation 1302.
In the operation 1301, the first apparatus may receive configuration information (e.g. the configuration information 201 when the MT part 106 of the IAB node 101 is the receiving peer apparatus, the configuration information 204 when the MT part 107 of the IAB node 104 is the receiving peer apparatus, the configuration information 501 when the UE 406 is the receiving peer apparatus, and the configuration 506 when the UE 407 is the receiving peer apparatus) from a donor apparatus (e.g. the example apparatus 800 and 900 performing the example method 700) in the IAB network for a P2P connection (e.g. the P2P connection 108 or 408) between the first apparatus and a second apparatus (e.g. at least a part of the MT part 106 of the IAB node 101 when acting as a transmitting peer apparatus, at least a part of the MT part 107 of the IAB node 104 when acting as a transmitting peer apparatus, at least a part of the UE 406 when acting as a transmitting peer apparatus, and at least a part of the UE 407 when acting as a transmitting peer apparatus) via the IAB network.
Then, in the operation 1302, the first apparatus may receive, via an access link (e.g. the access link 111 when the MT part 106 of the IAB node 101 is the receiving peer apparatus, the access link 113 when the MT part 107 of the IAB node 104 is the receiving peer apparatus, the access link 411 when the UE 406 is the receiving peer apparatus, and the access link 415 when the UE 407 is the receiving peer apparatus) and from a third apparatus (e.g. at least a part of the IAB node 102 when the MT part 106 of the IAB node 101 is the receiving peer apparatus, at least a part of the IAB node 103 when the MT part 107 of the IAB node 104 is the receiving peer apparatus, at least a part of the IAB node 401 when the UE 406 is the receiving peer apparatus, and at least a part of the IAB node 404 when the UE 407 is the receiving peer apparatus) serving the first apparatus in the IAB network, a data unit of the P2P connection based on the configuration information received in the operation 1301.
In some embodiments, the configuration information received in the operation 1301 may include information on at least one of a radio bearer used over the access link for the P2P connection, and an identifier of the P2P connection.
In some embodiments, the example method 1300 may further include an operation of determining a radio bearer used for carrying the data unit over the access link based on the configuration information received in the operation 1301.
In some embodiments, the P2P connection may emulate a sidelink connection between the first apparatus and the second apparatus, and may include a sidelink PDCP communication layer and a sidelink SDAP communication layer terminated at the first apparatus and at the second apparatus and transparently relayed through the IAB network.
FIG. 14 illustrates an example apparatus 1400 for P2P communication via an IAB network in an embodiment, which may be a first apparatus as at least a part of a receiving peer apparatus such as the MT part 106 of the IAB node 101 when acting as a receiving peer apparatus, at least a part of the MT part 107 of the IAB node 104 when acting as a receiving peer apparatus, at least a part of the UE 406 when acting as a receiving peer apparatus, and at least a part of the UE 407 when acting as a receiving peer apparatus.
As shown in FIG. 14, the example apparatus 1400 may include at least one processor 1401 and at least one memory 1402 that may include computer program code 1403. The at least one memory 1402 and the computer program code 1403 may be configured to, with the at least one processor 1401, cause the apparatus 1400 at least to perform at least the operations of the example method 1300 described above.
In various embodiments, the at least one processor 1401 in the example apparatus 1400 may include, but not limited to, at least one hardware processor, including at least one microprocessor such as a CPU, a portion of at least one hardware processor, and any other suitable dedicated processor such as those developed based on for example FPGA and ASIC. Further, the at least one processor 1401 may also include at least one other circuitry or element not shown in FIG. 14.
In various embodiments, the at least one memory 1402 in the example apparatus 1400 may include at least one storage medium in various forms, such as a volatile memory and/or a non-volatile memory. The volatile memory may include, but not limited to, for example, a RAM, a cache, and so on. The non-volatile memory may include, but not limited to, for example, a ROM, a hard disk, a flash memory, and so on. Further, the at least memory 1402 may include, but are not limited to, an electric, a magnetic, an optical, an electromagnetic, an infrared, or a semiconductor system, apparatus, or device or any combination of the above.
Further, in various embodiments, the example apparatus 1400 may also include at least one other circuitry, element, and interface, for example at least one I/O interface, at least one antenna element, and the like.
In various embodiments, the circuitries, parts, elements, and interfaces in the example apparatus 1400, including the at least one processor 1401 and the at least one memory 1402, may be coupled together via any suitable connections including, but not limited to, buses, crossbars, wiring and/or wireless lines, in any suitable ways, for example electrically, magnetically, optically, electromagnetically, and the like.
FIG. 15 illustrates an example apparatus 1500 for P2P communication via an IAB network in an embodiment, which may be a first apparatus as at least a part of a receiving peer apparatus such as the MT part 106 of the IAB node 101 when acting as a receiving peer apparatus, at least a part of the MT part 107 of the IAB node 104 when acting as a receiving peer apparatus, at least a part of the UE 406 when acting as a receiving peer apparatus, and at least a part of the UE 407 when acting as a receiving peer apparatus.
As shown in FIG. 15, the example apparatus 1500 may include means for performing operations of the example method 1300 described above in various embodiments. For example, the apparatus 1500 may include means 1501 for performing the operation 1301 of the example method 1300 and means 1502 for performing the operation 1302 of the example method 1300. In one or more another embodiment, at least one I/O interface, at least one antenna element, and the like may also be included in the example apparatus 1500. In some embodiments, examples of means in the apparatus 1500 may include circuitries. In some embodiments, examples of means may also include software modules and any other suitable function entities. In some embodiments, one or more additional means may be included in the apparatus 1500 for performing one or more additional operations of the example method 1300.
In some embodiments, the example methods 1000 and 1300 may be implemented in the same apparatus. For example, the at least one memory 1102 and the computer program code 1103 in the example apparatus 1100 may also be configured to, with the at least one processor 1101, cause the apparatus 1100 at least to perform at least the operations of the example method 1300 described above. For example, the at least one memory 1402 and the computer program code 1403 in the example apparatus 1400 may also be configured to, with the at least one processor 1401, cause the apparatus 1400 at least to perform at least the operations of the example method 1000 described above. For example, the means 1201 and 1202 in the example apparatus 1200 and the means 1501 and 1502 in the example apparatus 1500 may be configured in the same apparatus which is further configured to perform both the example method 1000 and the example method 1300.
FIG. 16 illustrates an example method 1600 for P2P communication via an IAB network in an embodiment, which may be performed in a first apparatus as at least a part of a transmitting access IAB node such as the IAB node 102 when the MT part 106 of the IAB node 101 acts as a transmitting peer apparatus, the IAB node 103 when the MT part 107 of the IAB node 104 acts as a transmitting peer apparatus, the IAB node 401 when the UE 406 acts as a transmitting peer apparatus, and the IAB node 404 when the UE 407 acts as a transmitting peer apparatus in the above examples. As illustrated in FIG. 16, the example method 1600 may include an operation 1601, an operation 1602, and an operation 1603.
In the operation 1601, the first apparatus may receive configuration information (for example, the configuration information 202 when the IAB node 102 is a transmitting access IAB node, the configuration information 203 when the IAB node 103 is a transmitting access IAB node, the configuration information 502 when the IAB node 401 is a transmitting access IAB node, and the configuration information 505 when the IAB node 404 is a transmitting access IAB node, which may include routing and bearer mapping configuration information for the corresponding IAB node, respectively) from a donor apparatus (for example the IAB-donor 105 and the IAB-donor 405) in the IAB network for a P2P connection (for example, the P2P connection 108 or the P2P connection 408) between a second apparatus (for example, the MT part 106 of the IAB node 101 as a transmitting peer apparatus, the MT part 107 of the IAB node 104 as a transmitting peer apparatus, the UE 406 as a transmitting peer apparatus, and the UE 407 as a transmitting peer apparatus) served by the first apparatus and a third apparatus (for example, the MT part 106 of the IAB node 101 as a receiving peer apparatus, the MT part 107 of the IAB node 104 as a receiving peer apparatus, the UE 406 as a receiving peer apparatus, and the UE 407 as a receiving peer apparatus) via the IAB network.
Then, in the operation 1602, the first apparatus may receive a data unit of the P2P connection from the second apparatus via an access link (for example, the access link 111 when the MT part 106 of the IAB node 101 is the transmitting peer apparatus, the access link 113 when the MT part 107 of the IAB node 104 is the transmitting peer apparatus, the access link 411 when the UE 406 is the transmitting peer apparatus, and the access link 415 when the UE 407 is the transmitting peer apparatus) .
Then, in the operation 1603, the first apparatus may transmit a BAP packet including a BAP header and the data unit based on the configuration information received in the operation 1601, where the BAP header may include information associated with the P2P connection.
In some embodiments, the configuration information received in the operation 1601 may include information on at least one of a routing identifier used for routing the data unit to a next-hop apparatus, an identifier of the next-hop apparatus, an identifier of the P2P connection, an identifier of a radio bearer used over the access link for the P2P connection, an identifier of a logical channel used over the access link for the P2P connection, and an identifier of a logical channel used for transmitting the BAP packet to the next-hop apparatus.
In some embodiments, the information on the P2P connection included in the BAP header may include at least one of a routing identifier used for routing the data unit to a next-hop apparatus in the IAB network, an identifier of the P2P connection, an identifier of a radio bearer used over the access link for the P2P connection, and an identifier of the second apparatus. For example, in a case where the two peer apparatuses (the second apparatus as the transmitting peer apparatus, and the third apparatus as the receiving peer apparatus) have P2P connection via the same access IAB nodes, the identifier of the second apparatus may be used to separate the connections of the two peer apparatuses.
In some embodiments, the P2P connection may emulate a sidelink connection between the second apparatus and the third apparatus, and may include a sidelink PDCP communication layer and a sidelink SDAP communication layer terminated at the second apparatus and at the third apparatus and transparently relayed through the IAB network as shown in FIG. 3 and 6.
FIG. 17 illustrates an example apparatus 1700 for P2P communication via an IAB network in an embodiment, which may be a first apparatus as at least a part of a transmitting access IAB node such as the IAB node 102 when the MT part 106 of the IAB node 101 acts as a transmitting peer apparatus, the IAB node 103 when the MT part 107 of the IAB node 104 acts as a transmitting peer apparatus, the IAB node 401 when the UE 406 acts as a transmitting peer apparatus, and the IAB node 404 when the UE 407 acts as a transmitting peer apparatus in the above examples.
As shown in FIG. 17, the example apparatus 1700 may include at least one processor 1701 and at least one memory 1702 that may include computer program code 1703. The at least one memory 1702 and the computer program code 1703 may be configured to, with the at least one processor 1701, cause the apparatus 1700 at least to perform at least the operations of the example method 1600 described above.
In various embodiments, the at least one processor 1701 in the example apparatus 1700 may include, but not limited to, at least one hardware processor, including at least one microprocessor such as a CPU, a portion of at least one hardware processor, and any other suitable dedicated processor such as those developed based on for example FPGA and ASIC. Further, the at least one processor 1701 may also include at least one other circuitry or element not shown in FIG. 17.
In various embodiments, the at least one memory 1702 in the example apparatus 1700 may include at least one storage medium in various forms, such as a volatile memory and/or a non-volatile memory. The volatile memory may include, but not limited to, for example, a RAM, a cache, and so on. The non-volatile memory may include, but not limited to, for example, a ROM, a hard disk, a flash memory, and so on. Further, the at least memory 1702 may include, but are not limited to, an electric, a magnetic, an optical, an electromagnetic, an infrared, or a semiconductor system, apparatus, or device or any combination of the above.
Further, in various embodiments, the example apparatus 1700 may also include at least one other circuitry, element, and interface, for example at least one I/O interface, at least one antenna element, and the like.
In various embodiments, the circuitries, parts, elements, and interfaces in the example apparatus 1700, including the at least one processor 1701 and the at least one memory 1702, may be coupled together via any suitable connections including, but not limited to, buses, crossbars, wiring and/or wireless lines, in any suitable ways, for example electrically, magnetically, optically, electromagnetically, and the like.
FIG. 18 illustrates an example apparatus 1800 for P2P communication via an IAB network in an embodiment, which may be a first apparatus as at least a part of a transmitting access IAB node such as the IAB node 102 when the MT part 106 of the IAB node 101 acts as a transmitting peer apparatus, the IAB node 103 when the MT part 107 of the IAB node 104 acts as a transmitting peer apparatus, the IAB node 401 when the UE 406 acts as a transmitting peer apparatus, and the IAB node 404 when the UE 407 acts as a transmitting peer apparatus in the above examples.
As shown in FIG. 18, the example apparatus 1800 may include means for performing operations of the example method 1600 described above in various embodiments. For example, the apparatus 1800 may include means 1801 for performing the operation 1601 of the example method 1600, means 1802 for performing the operation 1602 of the example method 1600, and means 1803 for performing the operation 1603 of the example method 1600. In one or more another embodiment, at least one I/O interface, at least one antenna element, and the like may also be included in the example apparatus 1800. In some embodiments, examples of means in the apparatus 1800 may include circuitries. In some embodiments, examples of means may also include software modules and any other suitable function entities. In some embodiments, one or more additional means may be included in the apparatus 1800 for performing one or more additional operations of the example method 1600.
FIG. 19 illustrates an example method 1900 for P2P communication via an IAB network in an embodiment, which may be performed in a first apparatus as at least a part of a receiving access IAB node such as the IAB node 102 when the MT part 106 of the IAB node 101 acts as a receiving peer apparatus, the IAB node 103 when the MT part 107 of the IAB node 104 acts as a receiving peer apparatus, the IAB node 401 when the UE 406 acts as a receiving peer apparatus, and the IAB node 404 when the UE 407 acts as a receiving peer apparatus in the above examples. As illustrated in FIG. 19, the example method 1900 may include an operation 1901, an operation 1902, and an operation 1903.
In the operation 1901, the first apparatus may receive configuration information (for example, the configuration information 202 when the IAB node 102 is a receiving access IAB node, the configuration information 203 when the IAB node 103 is a receiving access IAB node, the configuration information 502 when the IAB node 401 is a receiving access IAB node, and the configuration information 505 when the IAB node 404 is a receiving access IAB node, which may include bearer mapping configuration information for the corresponding IAB node, respectively) from a donor apparatus (for example the IAB-donor 105 and the IAB-donor 405) in the IAB network for a P2P connection (for example, the P2P connection 108 or the P2P connection 408) between a second apparatus (for example, the MT part 106 of the IAB node 101 as a transmitting peer apparatus, the MT part 107 of the IAB node 104 as a transmitting peer apparatus, the UE 406 as a transmitting peer apparatus, and the UE 407 as a transmitting peer apparatus) and a third apparatus (for example, the MT part 106 of the IAB node 101 as a receiving peer apparatus, the MT part 107 of the IAB node 104 as a receiving peer apparatus, the UE 406 as a receiving peer apparatus, and the UE 407 as a receiving peer apparatus) served by the first apparatus via the IAB network.
Then, in the operation 1902, the first apparatus may receive a BAP packet including a BAP header and a data unit of the P2P connection, where the BAP packet may include information associated with the P2P connection.
Then, in the operation 1903, the first apparatus may transmit the data unit to the third apparatus via a first access link (for example, the access link 111 when the MT part 106 of the IAB node 101 is the receiving peer apparatus, the access link 113 when the MT part 107 of the IAB node 104 is the receiving peer apparatus, the access link 411 when the UE 406 is the receiving peer apparatus, and the access link 415 when the UE 407 is the receiving peer apparatus) based on the configuration information received in the operation 1901 and the BAP header.
In some embodiments, the configuration information received in the operation 1901 may include information on at least one of an identifier of the third apparatus, an identifier of the P2P connection, an identifier of a radio bearer used over the first access link for the P2P connection, an identifier of a logical channel used over the first access link for the P2P connection, and an identifier of the first access link.
In some embodiments, the information on the P2P connection included in the BAP header may include at least one of an identifier of the P2P connection, an identifier of a radio bearer used over a second access link (for example, the access link 111 when the MT part 106 of the IAB node 101 is a transmitting peer apparatus, the access link 113 when the MT part 107 of the IAB node 104 is a transmitting peer apparatus, the access link 411 when the UE 406 is a transmitting peer apparatus, and the access link 415 when the UE 407 is a transmitting peer apparatus) between the second apparatus and a fourth apparatus (for example, the IAB node 102 when the MT part 106 of the IAB node 101 acts as a transmitting peer apparatus, the IAB node 103 when the MT part 107 of the IAB node 104 acts as a transmitting peer apparatus, the IAB node 401 when the UE 406 acts as a transmitting peer apparatus, and the IAB node 404 when the UE 407 acts as a transmitting peer apparatus) serving the second apparatus in the integrated access and backhaul network for the P2P connection, an identifier of the second access link, and an identifier of the second apparatus. For example, in a case where the two peer apparatuses (the second apparatus as the transmitting peer apparatus and the third apparatus as the receiving peer apparatus in the embodiment of FIG. 19) have P2P connection via the same access IAB nodes, the identifier of the second apparatus may be used to separate the connections of the two peer apparatuses.
In some embodiments, the P2P connection may emulate a sidelink connection between the second apparatus and the third apparatus, and may include a sidelink PDCP communication layer and a sidelink SDAP communication layer terminated at the second apparatus and at the third apparatus and transparently relayed through the IAB network.
FIG. 20 illustrates an example apparatus 2000 for P2P communication via an IAB network in an embodiment, which may be performed in a first apparatus as at least a part of a receiving access IAB node such as the IAB node 102 when the MT part 106 of the IAB node 101 acts as a receiving peer apparatus, the IAB node 103 when the MT part 107 of the IAB node 104 acts as a receiving peer apparatus, the IAB node 401 when the UE 406 acts as a receiving peer apparatus, and the IAB node 404 when the UE 407 acts as a receiving peer apparatus in the above examples.
As shown in FIG. 20, the example apparatus 2000 may include at least one processor 2001 and at least one memory 2002 that may include computer program code 2003. The at least one memory 2002 and the computer program code 2003 may be configured to, with the at least one processor 2001, cause the apparatus 2000 at least to perform at least the operations of the example method 1900 described above.
In various embodiments, the at least one processor 2001 in the example apparatus 2000 may include, but not limited to, at least one hardware processor, including at least one microprocessor such as a CPU, a portion of at least one hardware processor, and any other suitable dedicated processor such as those developed based on for example FPGA and ASIC. Further, the at least one processor 2001 may also include at least one other circuitry or element not shown in FIG. 19.
In various embodiments, the at least one memory 2002 in the example apparatus 2000 may include at least one storage medium in various forms, such as a volatile memory and/or a non-volatile memory. The volatile memory may include, but not limited to, for example, a RAM, a cache, and so on. The non-volatile memory may include, but not limited to, for example, a ROM, a hard disk, a flash memory, and so on. Further, the at least memory 2002 may include, but are not limited to, an electric, a magnetic, an optical, an electromagnetic, an infrared, or a semiconductor system, apparatus, or device or any combination of the above.
Further, in various embodiments, the example apparatus 2000 may also include at least one other circuitry, element, and interface, for example at least one I/O interface, at least one antenna element, and the like.
In various embodiments, the circuitries, parts, elements, and interfaces in the example apparatus 2000, including the at least one processor 2001 and the at least one memory 2002, may be coupled together via any suitable connections including, but not limited to, buses, crossbars, wiring and/or wireless lines, in any suitable ways, for example electrically, magnetically, optically, electromagnetically, and the like.
FIG. 21 illustrates an example apparatus 2100 for P2P communication via an IAB network in an embodiment, which may be performed in a first apparatus as at least a part of a receiving access IAB node such as the IAB node 102 when the MT part 106 of the IAB node 101 acts as a receiving peer apparatus, the IAB node 103 when the MT part 107 of the IAB node 104 acts as a receiving peer apparatus, the IAB node 401 when the UE 406 acts as a receiving peer apparatus, and the IAB node 404 when the UE 407 acts as a receiving peer apparatus in the above examples.
As shown in FIG. 21, the example apparatus 2100 may include means for performing operations of the example method 1900 described above in various embodiments. For example, the apparatus 2100 may include means 2101 for performing the operation 1901 of the example method 1900, means 2102 for performing the operation 1902 of the example method 1900, and means 2103 for performing the operation 1903 of the example method 1900. In one or more another embodiment, at least one I/O interface, at least one antenna element, and the like may also be included in the example apparatus 2100. In some embodiments, examples of means in the apparatus 2100 may include circuitries. In some embodiments, examples of means may also include software modules and any other suitable function entities. In some embodiments, one or more additional means may be included in the apparatus 2100 for performing one or more additional operations of the example method 1900.
In some embodiments, the example methods 1600 and 1900 may be implemented in the same apparatus. For example, the at least one memory 1702 and the computer program code 1703 in the example apparatus 1700 may also be configured to, with the at least one processor 1701, cause the apparatus 1700 at least to perform at least the operations of the example method 1900 described above. For example, the at least one memory 2002 and the computer program code 2003 in the example apparatus 2000 may also be configured to, with the at least one processor 2001, cause the apparatus 2000 at least to perform at least the operations of the example method 1600 described above. For example, the means in the example apparatus 1800 and the means in the example apparatus 2100 may be configured in the same apparatus which is further configured to perform both the example method 1600 and the example method 1900.
Another example embodiment may relate to computer program codes or instructions which may cause an apparatus to perform at least respective methods described above. Another example embodiment may be related to a computer readable medium having such computer program codes or instructions stored thereon. In some embodiments, such a computer readable medium may include at least one storage medium in various forms such as a volatile memory and/or a non-volatile memory. The volatile memory may include, but not limited to, for example, a RAM, a cache, and so on. The non-volatile memory may include, but not limited to, a ROM, a hard disk, a flash memory, and so on. The non-volatile memory may also include, but are not limited to, an electric, a magnetic, an optical, an electromagnetic, an infrared, or a semiconductor system, apparatus, or device or any combination of the above.
Unless the context clearly requires otherwise, throughout the description and the claims, the words “comprise, ” “comprising, ” and the like are to be construed in an inclusive sense, as opposed to an exclusive or exhaustive sense; that is to say, in the sense of “including, but not limited to. ” The word “coupled” , as generally used herein, refers to two or more elements that may be either directly connected, or connected by way of one or more intermediate elements. Likewise, the word “connected” , as generally used herein, refers to two or more elements that may be either directly connected, or connected by way of one or more intermediate elements. Additionally, the words “herein, ” “above, ” “below, ” and words of similar import, when used in this application, shall refer to this application as a whole and not to any particular portions of this application. Where the context permits, words in the description using the singular or plural number may also include the plural or singular number respectively. The word “or” in reference to a list of two or more items, that word covers all of the following interpretations of the word: any of the items in the list, all of the items in the list, and any combination of the items in the list.
Moreover, conditional language used herein, such as, among others, “can, ” “could, ” “might, ” “may, ” “e.g., ” “for example, ” “such as” and the like, unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain embodiments include, while other embodiments do not include, certain features, elements and/or states. Thus, such conditional language is not generally intended to imply that features, elements and/or states are in any way required for one or more embodiments or that one or more embodiments necessarily include logic for deciding, with or without author input or prompting, whether these features, elements and/or states are included or are to be performed in any particular embodiment.
While some embodiments have been described, these embodiments have been presented by way of example, and are not intended to limit the scope of the disclosure. Indeed, the apparatus, methods, and systems described herein may be embodied in a variety of other forms; furthermore, various omissions, substitutions and changes in the form of the methods and systems described herein may be made without departing from the spirit of the disclosure. For example, while blocks are presented in a given arrangement, alternative embodiments may perform similar functionalities with different components and/or circuit topologies, and some blocks may be deleted, moved, added, subdivided, combined, and/or modified. At least one of these blocks may be implemented in a variety of different ways. The order of these blocks may also be changed. Any suitable combination of the elements and acts of the some embodiments described above can be combined to provide further embodiments. The accompanying claims and their equivalents are intended to cover such forms or modifications as would fall within the scope and spirit of the disclosure.

Claims

An apparatus comprising:

at least one processor; and

at least one memory including computer program code, the at least one memory and the computer program code being configured to, with the at least one processor, cause the apparatus as a first apparatus to:

receive configuration information from a donor apparatus in an integrated access and backhaul network for a peer-to-peer connection between the first apparatus and a second apparatus via the integrated access and backhaul network, and

transmit, via an access link and to a third apparatus serving the first apparatus in the integrated access and backhaul network, a data unit of the peer-to-peer connection based on the configuration information.
The apparatus of claim 1 wherein the at least one memory and the computer program code are configured to, with the at least one processor, further cause the apparatus to:

transmit a request for establishing the peer-to-peer connection with the second apparatus, the request comprising information on at least one of an identifier of the first apparatus, an identifier of the second apparatus, and an identifier of a data flow associated with the data unit.
The apparatus of claim 1 or 2 wherein the configuration information comprises information on at least one of a radio bearer used over the access link for the peer-to-peer connection, and an identifier of the peer-to-peer connection.
The apparatus of any of claims 1 to 3 wherein the at least one memory and the computer program code are configured to, with the at least one processor, further cause the apparatus to:

determine a radio bearer used for transmitting the data unit over the access link based on the configuration information.
The apparatus of any of claims 1 to 4 wherein the first apparatus is a user equipment or a mobile termination part of an integrated access and backhaul network node apparatus in the integrated access and backhaul network.
The apparatus of any of claims 1 to 5 wherein the peer-to-peer connection emulates a sidelink connection between the first apparatus and the second apparatus, and comprises a sidelink packet data convergence protocol communication layer and a sidelink service data adaptation protocol communication layer terminated at the first apparatus and at the second apparatus and transparently relayed through the integrated access and backhaul network.
An apparatus comprising:

at least one processor; and

at least one memory including computer program code, the at least one memory and the computer program code being configured to, with the at least one processor, cause the apparatus as a first apparatus in an integrated access and backhaul network to:

receive routing and bearer mapping configuration information from a donor apparatus in the integrated access and backhaul network for a peer-to-peer connection between a second apparatus served by the first apparatus and a third apparatus via the integrated access and backhaul network,

receive a data unit of the peer-to-peer connection from the second apparatus via an access link, and

transmit a backhaul adaptation protocol packet including a backhaul adaptation protocol header and the data unit based on the routing and bearer mapping configuration information, the backhaul adaptation protocol header comprising information associated with the peer-to-peer connection.
The apparatus of claim 7 wherein the routing and bearer mapping configuration information comprises information on at least one of a routing identifier used for routing the data unit to a next-hop apparatus, an identifier of the next-hop apparatus, an identifier of the peer-to-peer connection, an identifier of a radio bearer used over the access link for the peer-to-peer connection, an identifier of a logical channel used over the access link for the peer-to-peer connection, and an identifier of a logical channel used for transmitting the backhaul adaptation protocol packet to the next-hop apparatus.
The apparatus of claim 7 or 8 wherein the information associated with the peer-to-peer connection comprises at least one of a routing identifier used for routing the data unit to a next-hop apparatus in the integrated access and backhaul network, an identifier of the peer-to-peer connection, an identifier of a radio bearer used over the access link for the peer-to-peer connection, and an identifier of the second apparatus.
The apparatus of any of claims 7 to 9 wherein the peer-to-peer connection emulates a sidelink connection between the second apparatus and the third apparatus, and comprises a sidelink packet data convergence protocol communication layer and a sidelink service data adaptation protocol communication layer terminated at the second apparatus and at the third apparatus and transparently relayed through the integrated access and backhaul network.
An apparatus comprising:

at least one processor; and

at least one memory including computer program code, the at least one memory and the computer program code being configured to, with the at least one processor, cause the apparatus as a first apparatus to:

receive configuration information from a donor apparatus in an integrated access and backhaul network for a peer-to-peer connection between the first apparatus and a second apparatus via the integrated access and backhaul network, and

receive, via an access link and from a third apparatus serving the first apparatus in the integrated access and backhaul network, a data unit of the peer-to-peer connection based on the configuration information.
The apparatus of claim 11 wherein the configuration information comprises information on at least one of a radio bearer used over the access link for the peer-to-peer connection, and an identifier of the peer-to-peer connection.
The apparatus of claim 11 or 12 wherein the at least one memory and the computer program code are configured to, with the at least one processor, further cause the apparatus to:

determine a radio bearer used for carrying the data unit over the access link based on the configuration information.
The apparatus of any of claims 11 to 13 wherein the first apparatus is a user equipment or a mobile termination part of an integrated access and backhaul network node apparatus in the integrated access and backhaul network.
The apparatus of any of claims 11 to 14 wherein the peer-to-peer connection emulates a sidelink connection between the first apparatus and the second apparatus, and comprises a sidelink packet data convergence protocol communication layer and a sidelink service data adaptation protocol communication layer terminated at the first apparatus and at the second apparatus and transparently relayed through the integrated access and backhaul network.
An apparatus comprising:

at least one processor; and

at least one memory including computer program code, the at least one memory and the computer program code being configured to, with the at least one processor, cause the apparatus as a first apparatus in an integrated access and backhaul network to:

receive bearer mapping configuration information from a donor apparatus in the integrated access and backhaul network for a peer-to-peer connection between a second apparatus and a third apparatus served by the first apparatus via the integrated access and backhaul network,

receive a backhaul adaptation protocol packet including a backhaul adaptation protocol header and a data unit of the peer-to-peer connection, the backhaul adaptation protocol packet comprising information associated with the peer-to-peer connection, and

transmit the data unit to the third apparatus via a first access link based on the bearer mapping configuration information and the backhaul adaptation protocol header.
The apparatus of claim 16 wherein the bearer mapping configuration information comprises information on at least one of an identifier of the third apparatus, an identifier of the peer-to-peer connection, an identifier of a radio bearer used over the first access link for the peer-to-peer connection, an identifier of a logical channel used over the first access link for the peer-to-peer connection, and an identifier of the first access link.
The apparatus of claim 16 or 17 wherein the information associated with the peer-to-peer connection comprises at least one of an identifier of the peer-to-peer connection, an identifier of a radio bearer used over a second access link between the second apparatus and a fourth apparatus serving the second apparatus in the integrated access and backhaul network for the peer-to-peer connection, an identifier of the second access link, and an identifier of the second apparatus.
The apparatus of any of claims 16 to 18 wherein the peer-to-peer connection emulates a sidelink connection between the second apparatus and the third apparatus, and comprises a sidelink packet data convergence protocol communication layer and a sidelink service data adaptation protocol communication layer terminated at the second apparatus and at the third apparatus and transparently relayed through the integrated access and backhaul network.
An apparatus comprising:

at least one processor; and

at least one memory including computer program code, the at least one memory and the computer program code being configured to, with the at least one processor, cause the apparatus as a donor apparatus in an integrated access and backhaul network to:

transmit, to a first apparatus, first configuration information for a peer-to-peer connection between the first apparatus and a second apparatus via the integrated access and backhaul network, to enable the first apparatus to transmit a data unit of the peer-to-peer connection via a first access link to a third apparatus serving the first apparatus in the integrated access and backhaul network,

transmit, to the second apparatus, second configuration information for the peer-to-peer connection, to enable the second apparatus to receive the data unit via a second access link from a fourth apparatus serving the second apparatus in the integrated access and backhaul network,

transmit, to the third apparatus, first routing and bearer mapping configuration information for the peer-to-peer connection, and

transmit, to the fourth apparatus, second bearer mapping configuration information for the peer-to-peer connection.
The apparatus of claim 20 wherein the at least one memory and the computer program code is configured to, with the at least one processor, further cause the apparatus to:

receive a request from the first apparatus for establishing the peer-to-peer connection with the second apparatus, the request comprising information on at least one of an identifier of the first apparatus, an identifier of the second apparatus, and an identifier of a data flow associated with the data unit.
The apparatus of claim 20 or 21 wherein the first configuration information comprises information on at least one of a radio bearer used over the first access link for the peer-to-peer connection, and an identifier of the peer-to-peer connection.
The apparatus of any of claims 20 to 22 wherein the second configuration information comprises at least one of information on at least one of a radio bearer used over the second access link for the peer-to-peer connection, and an identifier of the peer-to-peer connection.
The apparatus of any of claims 20 to 23 wherein the first routing and bearer mapping configuration information comprises information on at least one of a routing identifier for routing the data unit to a next-hop apparatus in the integrated access and backhaul network, an identifier of the next-hop apparatus, an identifier of the peer-to-peer connection, an identifier of a radio bearer used over the first access link for the peer-to-peer connection, an identifier of a logical channel used over the first access link for the peer-to-peer connection, and an identifier of a logical channel used for transmitting a backhaul adaptation protocol packet carrying the data unit to the next-hop apparatus.
The apparatus of any of claims 20 to 24 wherein the second bearer mapping configuration information comprises information on at least one of an identifier of the second apparatus, an identifier of the peer-to-peer connection, an identifier of a radio bearer used over the second access link for the peer-to-peer connection, an identifier of a logical channel used over the second access link for the peer-to-peer connection, and an identifier of the second access link.
The apparatus of any of claims 20 to 25 wherein the at least one memory and the computer program code are configured to, with the at least one processor, further cause the apparatus to:

determine at least one apparatus in the integrated access and backhaul network, the at least one apparatus comprising the third apparatus and the fourth apparatus, and forming a routing path for the peer to peer connection from the first apparatus to the second apparatus bypassing the donor apparatus.
The apparatus of any of claims 20 to 26 wherein the peer-to-peer connection emulates a sidelink connection between the first apparatus and the second apparatus, and comprises a sidelink packet data convergence protocol communication layer and a sidelink service data adaptation protocol communication layer terminated at the first apparatus and at the second apparatus and transparently relayed through the integrated access and backhaul network.
A method comprising:

receiving, at a first apparatus, configuration information from a donor apparatus in an integrated access and backhaul network for a peer-to-peer connection between the first apparatus and a second apparatus via the integrated access and backhaul network, and

transmitting, at the first apparatus via an access link and to a third apparatus serving the first apparatus in the integrated access and backhaul network, a data unit of the peer-to-peer connection based on the configuration information.
The method of claim 28 further comprising:

transmitting a request for establishing the peer-to-peer connection with the second apparatus, the request comprising information on at least one of an identifier of the first apparatus, an identifier of the second apparatus, and an identifier of a data flow associated with the data unit.
The method of claim 28 or 29 wherein the configuration information comprises information on at least one of a radio bearer used over the access link for the peer-to-peer connection, and an identifier of the peer-to-peer connection.
The method of any of claims 28 to 30 further comprising:

determining a radio bearer used for transmitting the data unit over the access link based on the configuration information.
The method of any of claims 28 to 31 wherein the first apparatus is a user equipment or a mobile termination part of an integrated access and backhaul network node apparatus in the integrated access and backhaul network.
The method of any of claims 28 to 32 wherein the peer-to-peer connection emulates a sidelink connection between the first apparatus and the second apparatus, and comprises a sidelink packet data convergence protocol communication layer and a sidelink service data adaptation protocol communication layer terminated at the first apparatus and at the second apparatus and transparently relayed through the integrated access and backhaul network.
A method comprising:

receiving, at a first apparatus in an integrated access and backhaul network, routing and bearer mapping configuration information from a donor apparatus in the integrated access and backhaul network for a peer-to-peer connection between a second apparatus served by the first apparatus and a third apparatus via the integrated access and backhaul network,

receiving, at the first apparatus, a data unit of the peer-to-peer connection from the second apparatus via an access link, and

transmitting, at the first apparatus, a backhaul adaptation protocol packet including a backhaul adaptation protocol header and the data unit based on the routing and bearer mapping configuration information, the backhaul adaptation protocol header comprising information associated with the peer-to-peer connection.
The method of claim 34 wherein the routing and bearer mapping configuration information comprises information on at least one of a routing identifier used for routing the data unit to a next-hop apparatus, an identifier of the next-hop apparatus, an identifier of the peer-to-peer connection, an identifier of a radio bearer used over the access link for the peer-to-peer connection, an identifier of a logical channel used over the access link for the peer-to-peer connection, and an identifier of a logical channel used for transmitting the backhaul adaptation protocol packet to the next-hop apparatus.
The method of claim 34 or 35 wherein the information associated with the peer-to-peer connection comprises at least one of a routing identifier used for routing the data unit to a next-hop apparatus in the integrated access and backhaul network, an identifier of the peer-to-peer connection, an identifier of a radio bearer used over the access link for the peer-to-peer connection, and an identifier of the second apparatus.
The method of any of claims 34 to 36 wherein the peer-to-peer connection emulates a sidelink connection between the second apparatus and the third apparatus, and comprises a sidelink packet data convergence protocol communication layer and a sidelink service data adaptation protocol communication layer terminated at the second apparatus and at the third apparatus and transparently relayed through the integrated access and backhaul network.
A method comprising:

receiving, at a first apparatus, configuration information from a donor apparatus in an integrated access and backhaul network for a peer-to-peer connection between the first apparatus and a second apparatus via the integrated access and backhaul network, and

receiving, at the first apparatus via an access link and from a third apparatus serving the first apparatus in the integrated access and backhaul network, a data unit of the peer-to-peer connection based on the configuration information.
The method of claim 38 wherein the configuration information comprises information on at least one of a radio bearer used over the access link for the peer-to-peer connection, and an identifier of the peer-to-peer connection.
The method of claim 38 or 39 further comprising:

determining, at the first apparatus, a radio bearer used for carrying the data unit over the access link based on the configuration information.
The method of any of claims 38 to 40 wherein the first apparatus is a user equipment or a mobile termination part of an integrated access and backhaul network node apparatus in the integrated access and backhaul network.
The method of any of claims 38 to 41 wherein the peer-to-peer connection emulates a sidelink connection between the first apparatus and the second apparatus, and comprises a sidelink packet data convergence protocol communication layer and a sidelink service data adaptation protocol communication layer terminated at the first apparatus and at the second apparatus and transparently relayed through the integrated access and backhaul network.
A method comprising:

receiving, at a first apparatus in an integrated access and backhaul network, bearer mapping configuration information from a donor apparatus in the integrated access and backhaul network for a peer-to-peer connection between a second apparatus and a third apparatus served by the first apparatus via the integrated access and backhaul network,

receiving, at the first apparatus, a backhaul adaptation protocol packet including a backhaul adaptation protocol header and a data unit of the peer-to-peer connection, the backhaul adaptation protocol packet comprising information associated with the peer-to-peer connection, and

transmitting, at the first apparatus, the data unit to the third apparatus via a first access link based on the bearer mapping configuration information and the backhaul adaptation protocol header.
The method of claim 43 wherein the bearer mapping configuration information comprises information on at least one of an identifier of the third apparatus, an identifier of the peer-to-peer connection, an identifier of a radio bearer used over the first access link for the peer-to-peer connection, an identifier of a logical channel used over the first access link for the peer-to-peer connection, and an identifier of the first access link.
The method of claim 43 or 44 wherein the information associated with the peer-to-peer connection comprises at least one of an identifier of the peer-to-peer connection, an identifier of a radio bearer used over a second access link between the second apparatus and a fourth apparatus serving the second apparatus in the integrated access and backhaul network for the peer-to-peer connection, and an identifier of the second access link, and an identifier of the second apparatus.
The method of any of claims 43 to 45 wherein the peer-to-peer connection emulates a sidelink connection between the second apparatus and the third apparatus, and comprises a sidelink packet data convergence protocol communication layer and a sidelink service data adaptation protocol communication layer terminated at the second apparatus and at the third apparatus and transparently relayed through the integrated access and backhaul network.
A method comprising:

transmitting, at a donor apparatus in an integrated access and backhaul network and to a first apparatus, first configuration information for a peer-to-peer connection between the first apparatus and a second apparatus via the integrated access and backhaul network, to enable the first apparatus to transmit a data unit of the peer-to-peer connection via a first access link to a third apparatus serving the first apparatus in the integrated access and backhaul network,

transmitting, at the donor apparatus to the second apparatus, second configuration information for the peer-to-peer connection, to enable the second apparatus to receive the data unit via a second access link from a fourth apparatus serving the second apparatus in the integrated access and backhaul network,

transmitting, at the donor apparatus to the third apparatus, first routing and bearer mapping configuration information for the peer-to-peer connection, and

transmitting, at the donor apparatus to the fourth apparatus, second bearer mapping configuration information for the peer-to-peer connection.
The method of claim 47 further comprising:

receiving, at the donor apparatus, a request from the first apparatus for establishing the peer-to-peer connection with the second apparatus, the request comprising information on at least one of an identifier of the first apparatus, an identifier of the second apparatus, and an identifier of a data flow associated with the data unit.
The method of claim 47 or 48 wherein the first configuration information comprises information on at least one of a radio bearer used over the first access link for the peer-to-peer connection, and an identifier of the peer-to-peer connection.
The method of any of claims 47 to 49 wherein the second configuration information comprises at least one of information on at least one of a radio bearer used over the second access link for the peer-to-peer connection, and an identifier of the peer-to-peer connection.
The method of any of claims 47 to 50 wherein the first routing and bearer mapping configuration information comprises information on at least one of a routing identifier for routing the data unit to a next-hop apparatus in the integrated access and backhaul network, an identifier of the next-hop apparatus, an identifier of the peer-to-peer connection, an identifier of a radio bearer used over the first access link for the peer-to-peer connection, an identifier of a logical channel used over the first access link for the peer-to-peer connection, and an identifier of a logical channel used for transmitting a backhaul adaptation protocol packet carrying the data unit to the next-hop apparatus.
The method of any of claims 47 to 51 wherein the second bearer mapping configuration information comprises information on at least one of an identifier of the second apparatus, an identifier of the peer-to-peer connection, an identifier of a radio bearer used over the second access link for the peer-to-peer connection, an identifier of a logical channel used over the second access link for the peer-to-peer connection, and an identifier of the second access link.
The method of any of claims 47 to 52 further comprising:

determining, at the donor apparatus, at least one apparatus in the integrated access and backhaul network, the at least one apparatus comprising the third apparatus and the fourth apparatus, and forming a routing path for the peer to peer connection from the first apparatus to the second apparatus bypassing the donor apparatus.
The method of any of claims 47 to 53 wherein the peer-to-peer connection emulates a sidelink connection between the first apparatus and the second apparatus, and comprises a sidelink packet data convergence protocol communication layer and a sidelink service data adaptation protocol communication layer terminated at the first apparatus and at the second apparatus and transparently relayed through the integrated access and backhaul network.
An apparatus as a first apparatus comprising:

means for receiving configuration information from a donor apparatus in an integrated access and backhaul network for a peer-to-peer connection between the first apparatus and a second apparatus via the integrated access and backhaul network, and

means for transmitting, via an access link and to a third apparatus serving the first apparatus in the integrated access and backhaul network, a data unit of the peer-to-peer connection based on the configuration information.
The apparatus of claim 55 further comprising:

means for transmitting a request for establishing the peer-to-peer connection with the second apparatus, the request comprising information on at least one of an identifier of the first apparatus, an identifier of the second apparatus, and an identifier of a data flow associated with the data unit.
The apparatus of claim 55 or 56 wherein the configuration information comprises information on at least one of a radio bearer used over the access link for the peer-to-peer connection, and an identifier of the peer-to-peer connection.
The apparatus of any of claims 55 to 57 further comprising:

means for determining a radio bearer used for transmitting the data unit over the access link based on the configuration information.
The apparatus of any of claims 55 to 58 wherein the first apparatus is a user equipment or a mobile termination part of an integrated access and backhaul network node apparatus in the integrated access and backhaul network.
The apparatus of any of claims 55 to 59 wherein the peer-to-peer connection emulates a sidelink connection between the first apparatus and the second apparatus, and comprises a sidelink packet data convergence protocol communication layer and a sidelink service data adaptation protocol communication layer terminated at the first apparatus and at the second apparatus and transparently relayed through the integrated access and backhaul network.
An apparatus as a first apparatus in an integrated access and backhaul network comprising:

means for receiving routing and bearer mapping configuration information from a donor apparatus in the integrated access and backhaul network for a peer-to-peer connection between a second apparatus served by the first apparatus and a third apparatus via the integrated access and backhaul network,

means for receiving a data unit of the peer-to-peer connection from the second apparatus via an access link, and

means for transmitting a backhaul adaptation protocol packet including a backhaul adaptation protocol header and the data unit based on the routing and bearer mapping configuration information, the backhaul adaptation protocol header comprising information associated with the peer-to-peer connection.
The apparatus of claim 61 wherein the routing and bearer mapping configuration information comprises information on at least one of a routing identifier used for routing the data unit to a next-hop apparatus, an identifier of the next-hop apparatus, an identifier of the peer-to-peer connection, an identifier of a radio bearer used over the access link for the peer-to-peer connection, an identifier of a logical channel used over the access link for the peer-to-peer connection, and an identifier of a logical channel used for transmitting the backhaul adaptation protocol packet to the next-hop apparatus.
The apparatus of claim 61 or 62 wherein the information associated with the peer-to-peer connection comprises at least one of a routing identifier used for routing the data unit to a next-hop apparatus in the integrated access and backhaul network, an identifier of the peer-to-peer connection, an identifier of a radio bearer used over the access link for the peer-to-peer connection, and an identifier of the second apparatus.
The apparatus of any of claims 61 to 63 wherein the peer-to-peer connection emulates a sidelink connection between the second apparatus and the third apparatus, and comprises a sidelink packet data convergence protocol communication layer and a sidelink service data adaptation protocol communication layer terminated at the second apparatus and at the third apparatus and transparently relayed through the integrated access and backhaul network.
An apparatus as a first apparatus comprising:

means for receiving configuration information from a donor apparatus in an integrated access and backhaul network for a peer-to-peer connection between the first apparatus and a second apparatus via the integrated access and backhaul network, and

means for receiving, via an access link and from a third apparatus serving the first apparatus in the integrated access and backhaul network, a data unit of the peer-to-peer connection based on the configuration information.
The apparatus of claim 65 wherein the configuration information comprises information on at least one of a radio bearer used over the access link for the peer-to-peer connection, and an identifier of the peer-to-peer connection.
The apparatus of claim 65 or 66 further comprising:

means for determining, at the first apparatus, a radio bearer used for carrying the data unit over the access link based on the configuration information.
The apparatus of any of claims 65 to 67 wherein the first apparatus is a user equipment or a mobile termination part of an integrated access and backhaul network node apparatus in the integrated access and backhaul network.
The apparatus of any of claims 65 to 68 wherein the peer-to-peer connection emulates a sidelink connection between the first apparatus and the second apparatus, and comprises a sidelink packet data convergence protocol communication layer and a sidelink service data adaptation protocol communication layer terminated at the first apparatus and at the second apparatus and transparently relayed through the integrated access and backhaul network.
An apparatus as a first apparatus in an integrated access and backhaul network comprising:

means for receiving bearer mapping configuration information from a donor apparatus in the integrated access and backhaul network for a peer-to-peer connection between a second apparatus and a third apparatus served by the first apparatus via the integrated access and backhaul network,

means for receiving a backhaul adaptation protocol packet including a backhaul adaptation protocol header and a data unit of the peer-to-peer connection, the backhaul adaptation protocol packet comprising information associated with the peer-to-peer connection, and

means for transmitting the data unit to the third apparatus via a first access link based on the bearer mapping configuration information and the backhaul adaptation protocol header.
The apparatus of claim 70 wherein the bearer mapping configuration information comprises information on at least one of an identifier of the third apparatus, an identifier of the peer-to-peer connection, an identifier of a radio bearer used over the first access link for the peer-to-peer connection, an identifier of a logical channel used over the first access link for the peer-to-peer connection, and an identifier of the first access link.
The apparatus of claim 70 or 71 wherein the information associated with the peer-to-peer connection comprises at least one of an identifier of the peer-to-peer connection, an identifier of a radio bearer used over a second access link between the second apparatus and a fourth apparatus serving the second apparatus in the integrated access and backhaul network for the peer-to-peer connection, an identifier of the second access link, and an identifier of the second apparatus.
The apparatus of any of claims 70 to 72 wherein the peer-to-peer connection emulates a sidelink connection between the second apparatus and the third apparatus, and comprises a sidelink packet data convergence protocol communication layer and a sidelink service data adaptation protocol communication layer terminated at the second apparatus and at the third apparatus and transparently relayed through the integrated access and backhaul network.
An apparatus as a donor apparatus in an integrated access and backhaul network comprising:

means for transmitting, to a first apparatus, first configuration information for a peer-to-peer connection between the first apparatus and a second apparatus via the integrated access and backhaul network, to enable the first apparatus to transmit a data unit of the peer-to-peer connection via a first access link to a third apparatus serving the first apparatus in the integrated access and backhaul network,

means for transmitting, to the second apparatus, second configuration information for the peer-to-peer connection, to enable the second apparatus to receive the data unit via a second access link from a fourth apparatus serving the second apparatus in the integrated access and backhaul network,

means for transmitting, to the third apparatus, first routing and bearer mapping configuration information for the peer-to-peer connection, and

means for transmitting, to the fourth apparatus, second bearer mapping configuration information for the peer-to-peer connection.
The apparatus of claim 74 further comprising:

means for receiving a request from the first apparatus for establishing the peer-to-peer connection with the second apparatus, the request comprising information on at least one of an identifier of the first apparatus, an identifier of the second apparatus, and an identifier of a data flow associated with the data unit.
The apparatus of claim 74 or 75 wherein the first configuration information comprises information on at least one of a radio bearer used over the first access link for the peer-to-peer connection, and an identifier of the peer-to-peer connection.
The apparatus of any of claims 74 to 76 wherein the second configuration information comprises at least one of information on at least one of a radio bearer used over the second access link for the peer-to-peer connection, and an identifier of the peer-to-peer connection.
The apparatus of any of claims 74 to 77 wherein the first routing and bearer mapping configuration information comprises information on at least one of a routing identifier for routing the data unit to a next-hop apparatus in the integrated access and backhaul network, an identifier of the next-hop apparatus, an identifier of the peer-to-peer connection, an identifier of a radio bearer used over the first access link for the peer-to-peer connection, an identifier of a logical channel used over the first access link for the peer-to-peer connection, and an identifier of a logical channel used for transmitting a backhaul adaptation protocol packet carrying the data unit to the next-hop apparatus.
The apparatus of any of claims 74 to 78 wherein the second bearer mapping configuration information comprises information on at least one of an identifier of the second apparatus, an identifier of the peer-to-peer connection, an identifier of a radio bearer used over the second access link for the peer-to-peer connection, an identifier of a logical channel used over the second access link for the peer-to-peer connection, and an identifier of the second access link.
The apparatus of any of claims 74 to 79 further comprising:

means for determining at least one apparatus in the integrated access and backhaul network, the at least one apparatus comprising the third apparatus and the fourth apparatus, and forming a routing path for the peer to peer connection from the first apparatus to the second apparatus bypassing the donor apparatus.
The apparatus of any of claims 74 to 80 wherein the peer-to-peer connection emulates a sidelink connection between the first apparatus and the second apparatus, and comprises a sidelink packet data convergence protocol communication layer and a sidelink service data adaptation protocol communication layer terminated at the first apparatus and at the second apparatus and transparently relayed through the integrated access and backhaul network.
A computer readable medium comprising instructions stored thereon for causing an apparatus as a first apparatus to:

receive configuration information from a donor apparatus in an integrated access and backhaul network for a peer-to-peer connection between the first apparatus and a second apparatus via the integrated access and backhaul network, and

transmit, via an access link and to a third apparatus serving the first apparatus in the integrated access and backhaul network, a data unit of the peer-to-peer connection based on the configuration information.
The computer readable medium of claim 82 wherein the instructions further cause the apparatus to:

transmit a request for establishing the peer-to-peer connection with the second apparatus, the request comprising information on at least one of an identifier of the first apparatus, an identifier of the second apparatus, and an identifier of a data flow associated with the data unit.
The computer readable medium of claim 82 or 83 wherein the configuration information comprises information on at least one of a radio bearer used over the access link for the peer-to-peer connection, and an identifier of the peer-to-peer connection.
The computer readable medium of any of claims 82 to 83 wherein the instructions further cause the apparatus to:

determine a radio bearer used for transmitting the data unit over the access link based on the configuration information.
The computer readable medium of any of claims 82 to 85 wherein the first apparatus is a user equipment or a mobile termination part of an integrated access and backhaul network node apparatus in the integrated access and backhaul network.
The computer readable medium of any of claims 82 to 86 wherein the peer-to-peer connection emulates a sidelink connection between the first apparatus and the second apparatus, and comprises a sidelink packet data convergence protocol communication layer and a sidelink service data adaptation protocol communication layer terminated at the first apparatus and at the second apparatus and transparently relayed through the integrated access and backhaul network.
A computer readable medium comprising instructions stored thereon for causing an apparatus as a first apparatus in an integrated access and backhaul network to:

receive routing and bearer mapping configuration information from a donor apparatus in the integrated access and backhaul network for a peer-to-peer connection between a second apparatus served by the first apparatus and a third apparatus via the integrated access and backhaul network,

receive a data unit of the peer-to-peer connection from the second apparatus via an access link, and

transmit a backhaul adaptation protocol packet including a backhaul adaptation protocol header and the data unit based on the routing and bearer mapping configuration information, the backhaul adaptation protocol header comprising information associated with the peer-to-peer connection.
The computer readable medium of claim 88 wherein the routing and bearer mapping configuration information comprises information on at least one of a routing identifier used for routing the data unit to a next-hop apparatus, an identifier of the next-hop apparatus, an identifier of the peer-to-peer connection, an identifier of a radio bearer used over the access link for the peer-to-peer connection, an identifier of a logical channel used over the access link for the peer-to-peer connection, and an identifier of a logical channel used for transmitting the backhaul adaptation protocol packet to the next-hop apparatus.
The computer readable medium of claim 88 or 89 wherein the information associated with the peer-to-peer connection comprises at least one of a routing identifier used for routing the data unit to a next-hop apparatus in the integrated access and backhaul network, an identifier of the peer-to-peer connection, an identifier of a radio bearer used over the access link for the peer-to-peer connection, and an identifier of the second apparatus.
The computer readable medium of any of claims 88 to 90 wherein the peer-to-peer connection emulates a sidelink connection between the second apparatus and the third apparatus, and comprises a sidelink packet data convergence protocol communication layer and a sidelink service data adaptation protocol communication layer terminated at the second apparatus and at the third apparatus and transparently relayed through the integrated access and backhaul network.
A computer readable medium comprising instructions stored thereon for causing an apparatus as a first apparatus to:

receive configuration information from a donor apparatus in an integrated access and backhaul network for a peer-to-peer connection between the first apparatus and a second apparatus via the integrated access and backhaul network, and

receive, via an access link and from a third apparatus serving the first apparatus in the integrated access and backhaul network, a data unit of the peer-to-peer connection based on the configuration information.
The computer readable medium of claim 92 wherein the configuration information comprises information on at least one of a radio bearer used over the access link for the peer-to-peer connection, and an identifier of the peer-to-peer connection.
The computer readable medium of claim 92 or 93 wherein the instructions further cause the apparatus to:

determine a radio bearer used for carrying the data unit over the access link based on the configuration information.
The computer readable medium of any of claims 92 to 94 wherein the first apparatus is a user equipment or a mobile termination part of an integrated access and backhaul network node apparatus in the integrated access and backhaul network.
The computer readable medium of any of claims 92 to 95 wherein the peer-to-peer connection emulates a sidelink connection between the first apparatus and the second apparatus, and comprises a sidelink packet data convergence protocol communication layer and a sidelink service data adaptation protocol communication layer terminated at the first apparatus and at the second apparatus and transparently relayed through the integrated access and backhaul network.
A computer readable medium comprising instructions stored thereon for causing an apparatus as a first apparatus in an integrated access and backhaul network to:

receive bearer mapping configuration information from a donor apparatus in the integrated access and backhaul network for a peer-to-peer connection between a second apparatus and a third apparatus served by the first apparatus via the integrated access and backhaul network,

receive a backhaul adaptation protocol packet including a backhaul adaptation protocol header and a data unit of the peer-to-peer connection, the backhaul adaptation protocol packet comprising information associated with the peer-to-peer connection, and

transmit the data unit to the third apparatus via a first access link based on the bearer mapping configuration information and the backhaul adaptation protocol header.
The computer readable medium of claim 97 wherein the bearer mapping configuration information comprises information on at least one of an identifier of the third apparatus, an identifier of the peer-to-peer connection, an identifier of a radio bearer used over the first access link for the peer-to-peer connection, an identifier of a logical channel used over the first access link for the peer-to-peer connection, and an identifier of the first access link.
The computer readable medium of claim 97 or 98 wherein the information associated with the peer-to-peer connection comprises at least one of an identifier of the peer-to-peer connection, an identifier of a radio bearer used over a second access link between the second apparatus and a fourth apparatus serving the second apparatus in the integrated access and backhaul network for the peer-to-peer connection, an identifier of the second access link, and an identifier of the second apparatus.
The computer readable medium of any of claims 97 to 99 wherein the peer-to-peer connection emulates a sidelink connection between the second apparatus and the third apparatus, and comprises a sidelink packet data convergence protocol communication layer and a sidelink service data adaptation protocol communication layer terminated at the second apparatus and at the third apparatus and transparently relayed through the integrated access and backhaul network.
A computer readable medium comprising instructions stored thereon for causing an apparatus as a donor apparatus in an integrated access and backhaul network to:

transmit, to a first apparatus, first configuration information for a peer-to-peer connection between the first apparatus and a second apparatus via the integrated access and backhaul network, to enable the first apparatus to transmit a data unit of the peer-to-peer connection via a first access link to a third apparatus serving the first apparatus in the integrated access and backhaul network,

transmit, to the second apparatus, second configuration information for the peer-to-peer connection, to enable the second apparatus to receive the data unit via a second access link from a fourth apparatus serving the second apparatus in the integrated access and backhaul network,

transmit, to the third apparatus, first routing and bearer mapping configuration information for the peer-to-peer connection, and

transmit, to the fourth apparatus, second bearer mapping configuration information for the peer-to-peer connection.
The computer readable medium of claim 101 wherein the at least one memory and the computer program code is configured to, with the at least one processor, further cause the apparatus to:

receive a request from the first apparatus for establishing the peer-to-peer connection with the second apparatus, the request comprising information on at least one of an identifier of the first apparatus, an identifier of the second apparatus, and an identifier of a data flow associated with the data unit.
The computer readable medium of claim 101 or 102 wherein the first configuration information comprises information on at least one of a radio bearer used over the first access link for the peer-to-peer connection, and an identifier of the peer-to-peer connection.
The computer readable medium of any of claims 101 to 103 wherein the second configuration information comprises at least one of information on at least one of a radio bearer used over the second access link for the peer-to-peer connection, and an identifier of the peer-to-peer connection.
The computer readable medium of any of claims 101 to 104 wherein the first routing and bearer mapping configuration information comprises information on at least one of a routing identifier for routing the data unit to a next-hop apparatus in the integrated access and backhaul network, an identifier of the next-hop apparatus, an identifier of the peer-to-peer connection, an identifier of a radio bearer used over the first access link for the peer-to-peer connection, an identifier of a logical channel used over the first access link for the peer-to-peer connection, and an identifier of a logical channel used for transmitting a backhaul adaptation protocol packet carrying the data unit to the next-hop apparatus.
The computer readable medium of any of claims 101 to 105 wherein the second bearer mapping configuration information comprises information on at least one of an identifier of the second apparatus, an identifier of the peer-to-peer connection, an identifier of a radio bearer used over the second access link for the peer-to-peer connection, an identifier of a logical channel used over the second access link for the peer-to-peer connection, and an identifier of the second access link.
The computer readable medium of any of claims 101 to 106 wherein the instructions further cause the apparatus to:

determine at least one apparatus in the integrated access and backhaul network, the at least one apparatus comprising the third apparatus and the fourth apparatus, and forming a routing path for the peer to peer connection from the first apparatus to the second apparatus bypassing the donor apparatus.
The computer readable medium of any of claims 101 to 107 wherein the peer-to-peer connection emulates a sidelink connection between the first apparatus and the second apparatus, and comprises a sidelink packet data convergence protocol communication layer and a sidelink service data adaptation protocol communication layer terminated at the first apparatus and at the second apparatus and transparently relayed through the integrated access and backhaul network.