Method, apparatus, and computer-readable medium for peer-to-peer communications via an integrated access and backhaul network

Abstract

An example method is disclosed that may include: receiving, at a first device, configuration information from a donor device in an integrated access and backhaul network for a peer-to-peer connection between the first device and a second device via the integrated access and backhaul network; and sending, at the first device, data units of the peer-to-peer connection to a third device serving the first device in the integrated access and backhaul network via an access link based on the configuration information. Related devices and computer-readable media are also disclosed.

Description

Technical Field

[0001] Various embodiments are directed to methods, apparatus, and computer-readable media for peer-to-peer communications via an integrated access and backhaul network. Background Art

[0002] An integrated access and backhaul (IAB) network in which a portion of radio resources is also used for wireless backhaul has been introduced in telecommunication systems such as new radio (NR or 5G) systems, making it possible, for example, to achieve flexible and dense deployment of NR cells without proportionally encrypting the transmission network, and to reduce site acquisition costs and fiber deployment costs. Summary of the invention

[0003] In a first aspect, an apparatus is disclosed, comprising at least one processor and at least one memory comprising computer program code, wherein the at least one memory and the computer program code are configured to utilize the at least one processor to enable the apparatus as a first device to: receive configuration information for a peer connection between the first device and a second device from a donor device in an integrated access and backhaul network via an integrated access and backhaul network; and based on the configuration information, send data units of the peer connection to a third device in the integrated access and backhaul network serving the first device via an access link.

[0004] 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 send a request for establishing a peer connection with the second device, the request comprising information about at least one of an identifier of the first device, an identifier of the second device, and an identifier of a data stream associated with the data unit.

[0005] In some embodiments, the configuration information comprises information about at least one of a radio bearer used on an access link for the peer connection and an identifier of the peer connection.

[0006] In some embodiments, the at least one memory and the computer program code are configured to, with at least one processor, further cause the apparatus to determine, based on the configuration information, a radio bearer for sending the data unit on the access link.

[0007] In some embodiments, the first device is a user equipment or a mobile terminal portion of an integrated access and backhaul network node device in an integrated access and backhaul network.

[0008] In some embodiments, the peer connection simulates a sidelink connection between a first device and a second device and includes a sidelink packet data convergence protocol communication layer and a sidelink service data adaptation protocol communication layer, which are terminated at the first device and the second device and transparently relayed through an integrated access and backhaul network.

[0009] In a second aspect, an apparatus is disclosed, comprising at least one processor and at least one memory comprising computer program code, wherein the at least one memory and the computer program code are configured to use the at least one processor to enable the apparatus as a first device in an integrated access and backhaul network to: receive routing and bearer mapping configuration information for a peer connection between a second device and a third device served by the first device from a donor device in the integrated access and backhaul network via the integrated access and backhaul network; receive a data unit of the peer connection from the second device via an access link; and send a backhaul adaptive protocol packet including a backhaul adaptive protocol header and the data unit based on the routing and bearer mapping configuration information, wherein the backhaul adaptive protocol header includes information associated with the peer connection.

[0010] In some embodiments, the routing and bearer mapping configuration information includes information about at least one of: a routing identifier for routing data units to a next hop device, an identifier of the next hop device, an identifier of a peer connection, an identifier of a radio bearer used on an access link for the peer connection, an identifier of a logical channel used on an access link for the peer connection, and a logical channel identifier for sending a backhaul adaptation protocol packet to the next hop device.

[0011] In some embodiments, the information associated with the peer connection includes at least one of: a routing identifier for routing data units to a next hop device in the integrated access and backhaul network, an identifier of the peer connection, an identifier of a radio bearer used on an access link for the peer connection, and an identifier of the second device.

[0012] In some embodiments, the peer connection simulates a sidelink connection between a second device and a third device and includes a sidelink packet data convergence protocol communication layer and a sidelink service data adaptation protocol communication layer, which are terminated at the second device and the third device and transparently relayed through an integrated access and backhaul network.

[0013] In a third aspect, an apparatus is disclosed, comprising at least one processor and at least one memory comprising computer program code, wherein the at least one memory and the computer program code are configured to utilize the at least one processor to enable the apparatus as a first device to: receive configuration information for a peer connection between the first device and a second device from a donor device in the integrated access and backhaul network via the integrated access and backhaul network; and based on the configuration information, receive data units of the peer connection from a third device in the integrated access and backhaul network serving the first device via an access link.

[0014] In some embodiments, the configuration information comprises information about at least one of a radio bearer used on an access link for the peer connection and an identifier of the peer connection.

[0015] 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, based on the configuration information, a radio bearer for carrying the data unit on the access link.

[0016] In some embodiments, the first device is a user equipment or a mobile terminal portion of an integrated access and backhaul network node device in an integrated access and backhaul network.

[0017] In some embodiments, the peer connection simulates a sidelink connection between a first device and a second device and includes a sidelink packet data convergence protocol communication layer and a sidelink service data adaptation protocol communication layer, which are terminated at the first device and the second device and transparently relayed through an integrated access and backhaul network.

[0018] In a fourth aspect, a device is disclosed comprising at least one processor and at least one memory comprising computer program code, wherein the at least one memory and the computer program code are configured to utilize the at least one processor so that the device, as a first device in an integrated access and backhaul network, receives bearer mapping configuration information for a peer connection between a second device and a third device served by the first device from a donor device in the integrated access and backhaul network via the integrated access and backhaul network service; receives a backhaul adaptation data packet comprising a backhaul adaptation protocol header and a data unit of the peer connection, the backhaul adaptation information packet comprising information associated with the peer link; and based on the bearer mapping configuration information and the backhaul adaptation protocol header, sends the data unit to the third device via the first access link.

[0019] In some embodiments, the bearer mapping configuration information includes information about at least one of: an identifier of a third device, an identifier of a peer connection, an identifier of a radio bearer used on a first access link for the peer connection, an identifier of a logical channel used on the first access link for the peer connection, and an identifier of the first access link.

[0020] In some embodiments, the information associated with the peer connection includes at least one of: an identifier of the peer connection, an identifier of a radio bearer used on a second access link between a second device and a fourth device serving the second device in an integrated access and backhaul network for the peer connection, and an identifier of the second access link and an identifier of the second device.

[0021] In some embodiments, the peer connection simulates a sidelink connection between a second device and a third device and includes a sidelink packet data convergence protocol communication layer and a sidelink service data adaptation protocol communication layer, which are terminated at the second device and the third device and transparently relayed through an integrated access and backhaul network.

[0022] In a fifth aspect, a device is disclosed, comprising at least one processor and at least one memory comprising computer program code, wherein the at least one memory and the computer program code are configured to utilize the at least one processor to enable the device to act as a donor device in an integrated access and backhaul network to: send first configuration information for a peer connection between the first device and a second device to a first device via the integrated access and backhaul network, so that the first device can send data units of the peer connection to a third device serving the third device in the integrated access and backhaul network via a first access link; send second configuration information for the peer connection to the second device, so that the second device can receive the data units from a fourth device serving the second device in the integrated access and backhaul network via a second access link; send first routing and bearer mapping configuration information for the peer connection to the third device; and send second bearer mapping configuration information for the peer connection to the fourth device.

[0023] 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 receive, from the first device, a request to establish a peer connection with the second device, the request comprising information about at least one of: an identifier of the first device, an identifier of the second device, and an identifier of a data stream associated with the data unit.

[0024] In some embodiments, the first configuration information comprises information about at least one of a radio bearer used on the first access link for the peer connection and an identifier of the peer connection.

[0025] In some embodiments, the second configuration information comprises information about at least one of a radio bearer used on the second access link for the peer connection and an identifier of the peer connection.

[0026] In some embodiments, the first routing and bearer mapping configuration information includes information about at least one of: a routing identifier for routing a data unit to a next-hop device in an integrated access and backhaul network, an identifier of the next-hop device, an identifier of a peer connection, an identifier of a radio bearer used on the first access link for the peer connection, an identifier of a logical channel used on the first access link for the peer connection, and a logical channel identifier for sending a backhaul adaptation protocol packet carrying the data unit to the next-hop device.

[0027] In some embodiments, the second bearer mapping configuration information includes information about at least one of: an identifier of the second device, an identifier of the peer connection, an identifier of a radio bearer used on a second access link for the peer connection, an identifier of a logical channel used on the second access link for the peer connection, and an identifier of the second access link.

[0028] 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 device in the integrated access and backhaul network, the at least one device comprising the third device and the fourth device, and to form a routing path for a peer connection from the first device to the second device bypassing the donor device.

[0029] In some embodiments, the peer connection simulates a sidelink connection between a first device and a second device, and includes a sidelink packet data convergence protocol communication layer and a sidelink service data adaptation protocol communication layer, which are terminated at the first device and the second device and transparently relayed through an integrated access and backhaul network.

[0030] In a sixth aspect, a method is disclosed, comprising: at a first device, receiving configuration information for a peer connection between a first device and a second device from a donor device in an integrated access and backhaul network via an integrated access and backhaul network; and based on the configuration information, at the first device, sending data units of the peer connection to a third device serving the first device in the integrated access and backhaul network via an access link.

[0031] In some embodiments, the method further comprises sending a request for establishing a peer connection with a second device, the request comprising information about at least one of an identifier of the first device, an identifier of the second device, and an identifier of a data stream associated with the data unit.

[0032] In some embodiments, the configuration information comprises information about at least one of a radio bearer used on an access link for the peer connection and an identifier of the peer connection.

[0033] In some embodiments, the method further comprises determining a radio bearer for sending the data unit on the access link based on the configuration information.

[0034] In some embodiments, the first device is a user equipment or a mobile terminal portion of an integrated access and backhaul network node device in an integrated access and backhaul network.

[0035] In some embodiments, the peer connection simulates a sidelink connection between a first device and a second device, and includes a sidelink packet data convergence protocol communication layer and a sidelink service data adaptation protocol communication layer, which are terminated at the first device and the second device and transparently relayed through an integrated access and backhaul network.

[0036] In a seventh aspect, a method is disclosed, comprising: receiving, at a first device in the integrated access and backhaul network, routing and bearer mapping configuration information for a peer connection between a second device and a third device served by the first device from a donor device in the integrated access and backhaul network via an integrated access and backhaul network; receiving, at the first device, a data unit of the peer connection from the second device via an access link; and sending, at the first device, a backhaul adaptive protocol packet including a backhaul adaptive protocol header and the data unit based on the routing and bearer mapping configuration information, the backhaul adaptive protocol header including information associated with the peer connection.

[0037] In some embodiments, the routing and bearer mapping configuration information includes information about at least one of: a routing identifier for routing a data unit to a next hop device, an identifier of the next hop device, an identifier of a peer connection, an identifier of a radio bearer used on an access link for the peer connection, an identifier of a logical channel used on an access link for the peer connection, and an identifier of a logical channel for sending the backhaul adaptation protocol packet to the next hop device.

[0038] In some embodiments, the information associated with the peer connection includes information of at least one of: a routing identifier for routing a data unit to a next hop device in an integrated access and backhaul network, an identifier of the peer connection, an identifier of a radio bearer used on an access link for the peer connection, and an identifier of a radio bearer used in the peer connection, and an identifier of a second device.

[0039] In some embodiments, the peer connection simulates a side link connection between a second device and a third device, and includes a side link packet data convergence protocol communication layer and a side link service data adaptation protocol communication layer, which are terminated at the second device and the third device and transparently relayed through an integrated access and backhaul network.

[0040] In an eighth aspect, a method is disclosed, comprising: receiving, at a first device via an integrated access and backhaul network, configuration information for a peer connection between a first device and a second device from a donor device in the integrated access and backhaul network; and receiving, at the first device via an access link, data units of the peer connection from a third device serving the first device in the integrated access and backhaul network based on the configuration information.

[0041] In some embodiments, the configuration information comprises information about at least one of a radio bearer used on an access link for the peer connection and an identifier of the peer connection.

[0042] In some embodiments, the method further comprises determining, at the first device, a radio bearer for carrying the data unit on the access link based on the configuration information.

[0043] In some embodiments, the first device is a user equipment or a mobile terminal portion of an integrated access and backhaul network node device in an integrated access and backhaul network.

[0044] In some embodiments, the peer connection simulates a sidelink connection between a first device and a second device, and includes a sidelink packet data convergence protocol communication layer and a sidelink service data adaptation protocol communication layer, which are terminated at the first device and the second device and transparently relayed through an integrated access and backhaul network.

[0045] In a ninth aspect, a method is disclosed, comprising: receiving, at a first device in an integrated access and backhaul network via an integrated access and backhaul network service, bearer mapping configuration information for a peer connection between a second device and a third device served by the first device from a donor device in the integrated access and backhaul network; receiving, at the first device, a backhaul adaptation protocol packet, the backhaul adaptation protocol packet including a backhaul adaptation packet header and a data unit of the peer connection, the backhaul adaptation protocol packet including information associated with the peer link; and sending, at the first device, the data unit to the third device via a first access link based on the bearer mapping configuration information and the backhaul adaptation protocol header.

[0046] In some embodiments, the bearer mapping configuration information includes information about at least one of: an identifier of the third device, an identifier of the peer connection, an identifier of a radio bearer used on the first access link for the peer connection, an identifier of a logical channel used on the first access link for the peer connection, and an identifier of the first access link.

[0047] In some embodiments, the information associated with the peer connection includes at least one of: an identifier of the peer connection, an identifier of a radio bearer used on a second access link between a second device in an integrated access and backhaul network for the peer connection and a fourth device serving the second device, an identifier of the second access link, and an identifier of the second device.

[0048] In some embodiments, the peer connection simulates a side link connection between a second device and a third device, and includes a side link packet data convergence protocol communication layer and a side link service data adaptation protocol communication layer, which are terminated at the second device and the third device and transparently relayed through the integrated access and backhaul network.

[0049] In a tenth aspect, a method is disclosed, comprising: at a donor device in an integrated access and backhaul network, sending first configuration information for a peer connection between a first device and a second device to a first device via the integrated access and backhaul network, so that the first device can send data units of the peer connection to a third device serving the first device in the integrated access and backhaul network via a first access link; sending second configuration information for the peer connection to the second device at the donor device, so that the second device can receive the data units from a fourth device serving the second device in the integrated access and backhaul network via a second access link; sending first routing and bearer mapping configuration information for the peer connection to the third device at the donor device; and sending second bearer mapping configuration information for the peer connection to the fourth device at the donor device.

[0050] In some embodiments, the method further includes receiving, at the donor device, a request from the first device to establish a peer connection with the second device, the request including information about at least one of an identifier of the first device, an identifier of the second device, and an identifier of a data stream associated with the data unit.

[0051] In some embodiments, the first configuration information comprises information about at least one of a radio bearer used on the first access link for the peer connection and an identifier of the peer connection.

[0052] In some embodiments, the second configuration information comprises information about at least one of a radio bearer used on the second access link for the peer connection and an identifier of the peer connection.

[0053] In some embodiments, the first routing and bearer mapping configuration information includes information about at least one of: a routing identifier for routing a data unit to a next-hop device in an integrated access and backhaul network, an identifier of the next-hop device, an identifier of a peer connection, an identifier of a radio bearer used on the first access link for the peer connection, an identifier of a logical channel used on the first access link for the peer connection, and a logical channel identifier for sending a backhaul adaptation protocol packet carrying the data unit to the next-hop device.

[0054] In some embodiments, the second bearer mapping configuration information includes information about at least one of: an identifier of the second device, an identifier of the peer connection, an identifier of a radio bearer used on a second access link for the peer connection, an identifier of a radio bearer used for the peer connection on the second access link, an identifier of a logical channel used on the second access link for the peer connection, and an identifier of the second access link.

[0055] In some embodiments, the method further includes determining, at the donor device, at least one device in the integrated access and backhaul network, the at least one device comprising a third device and a fourth device, and forming a routing path for the peer connection from the first device to the second device that bypasses the donor device.

[0056] In some embodiments, the peer connection simulates a sidelink connection between a first device and a second device, and includes a sidelink packet data convergence protocol communication layer and a sidelink service data adaptation protocol communication layer, which are terminated at the first device and the second device and transparently relayed through an integrated access and backhaul network.

[0057] In an eleventh aspect, a device as a first device is disclosed, comprising: a device for receiving configuration information for a peer connection between a first device and a second device from a donor device in an integrated access and backhaul network via an integrated access and backhaul network; and a device for sending data units of the peer connection to a third device serving the first device in the integrated access and backhaul network via an access link based on the configuration information.

[0058] In some embodiments, the device further comprises means for sending a request for establishing a peer connection with a second device, the request comprising information about at least one of an identifier of the first device, an identifier of the second device, and an identifier of a data flow associated with the data unit.

[0059] In some embodiments, the configuration information comprises information about at least one of a radio bearer used on an access link for the peer connection and an identifier of the peer connection.

[0060] In some embodiments, the apparatus further comprises means for determining a radio bearer for sending the data unit on the access link based on the configuration information.

[0061] In some embodiments, the first device is a user equipment or a mobile terminal portion of an integrated access and backhaul network node device in an integrated access and backhaul network.

[0062] In some embodiments, the peer connection simulates a sidelink connection between a first device and a second device, and includes a sidelink packet data convergence protocol communication layer and a sidelink service data adaptation protocol communication layer, which are terminated at the first device and the second device and transparently relayed through an integrated access and backhaul network.

[0063] In a twelfth aspect, a device is disclosed as a first device in an integrated access and backhaul network, comprising: a device for receiving routing and bearer mapping configuration information for a peer connection between a second device and a third device served by the first device from a donor device in the integrated access and backhaul network via the integrated access and backhaul network; a module for receiving a data unit of the peer connection from the second device via an access link; and a device for sending a backhaul adaptation protocol packet including a backhaul adaptation protocol header and the data unit based on the routing and bearer mapping configuration information, wherein the backhaul adaptation protocol header includes information associated with the peer connection.

[0064] In some embodiments, the routing and bearer mapping configuration information includes information about at least one of the following: a routing identifier for routing a data unit to a next hop device, an identifier of the next hop device, an identifier of a peer connection, an identifier of a logical channel used on an access link for the peer connection, and a logical channel identifier for sending the backhaul adaptation protocol packet to the next hop device.

[0065] In some embodiments, the information associated with the peer connection includes at least one of: a routing identifier for routing a data unit to a next hop device in the integrated access and backhaul network, an identifier of the peer connection, an identifier of a radio bearer used on an access link for the peer connection, and an identifier of a second device.

[0066] In some embodiments, the peer connection simulates a sidelink connection between a second device and a third device, and includes a sidelink packet data convergence protocol communication layer and a sidelink service data adaptation protocol communication layer, which are terminated at the second device and the third device and are transparently relayed through an integrated access and backhaul network.

[0067] In the thirteenth aspect, a device as a first device is disclosed, comprising: a device for receiving configuration information from a donor device in an integrated access and backhaul network via the integrated access and backhaul network, the configuration information being used for a peer connection between the first device and a second device; and a device for receiving data units of the peer connection from a third device in the integrated access and backhaul network serving the first device via an access link based on the configuration information.

[0068] In some embodiments, the configuration information comprises information about at least one of a radio bearer used on an access link for the peer connection and an identifier of the peer connection.

[0069] In some embodiments, the apparatus further comprises means for determining, at the first device, a radio bearer for carrying the data unit on the access link based on the configuration information.

[0070] In some embodiments, the first device is a user equipment or a mobile terminal portion of an integrated access and backhaul network node device in an integrated access and backhaul network.

[0071] In some embodiments, the peer connection simulates a sidelink connection between a first device and a second device, and includes a sidelink packet data convergence protocol communication layer and a sidelink service data adaptation protocol communication layer, which are terminated at the first device and the second device and are transparently relayed through an integrated access and backhaul network.

[0072] In a fourteenth aspect, a device is disclosed as a first device in an integrated access and backhaul network, comprising: a device for receiving bearer mapping configuration information for a peer connection between a second device and a third device served by the first device from a donor device in the integrated access and backhaul network via the integrated access and backhaul network; a device for receiving a backhaul adaptation protocol packet including a backhaul adaptation protocol header and a data unit of the peer connection, the backhaul adaptation protocol packet including information associated with the peer connection; and a device for sending the data unit to the third device via a first access link based on the bearer mapping configuration information and the backhaul adaptation protocol header.

[0073] In some embodiments, the bearer mapping configuration information includes information about at least one of: an identifier of a third device, an identifier of a peer connection, an identifier of a radio bearer used on a first access link for the peer connection, an identifier of a logical channel used in the first access link for the peer connection, and an identifier of the first access link.

[0074] In some embodiments, the information associated with the peer connection includes at least one of: an identifier of the peer connection, an identifier of a radio bearer used on a second access link between a second device and a fourth device serving the second device in an integrated access and backhaul network for the peer connection, and an identifier of the second access link and an identifier of the second device.

[0075] In some embodiments, the peer connection simulates a side link connection between a second device and a third device, and includes a side link packet data convergence protocol communication layer and a side link service data adaptation protocol communication layer, which are terminated at the second device and the third device and transparently relayed through an integrated access and backhaul network.

[0076] In a fifteenth aspect, a device serving as a donor device in an integrated access and backhaul network is disclosed, comprising: a device for sending first configuration information for a peer connection between a first device and a second device to a first device via the integrated access and backhaul network, so that the first device can send a data unit of the peer connection to a third device serving the first device in the integrated access and backhaul network via a first access link; a device for sending second configuration information for the peer connection to the second device so that the second device can receive the data unit from a fourth device serving the second device in the integrated access and backhaul network via a second access link; a device for sending first routing and bearer mapping configuration information for the peer connection to the third device; and a device for sending a second bearer mapping configuration for the peer connection to the fourth device.

[0077] In some embodiments, the apparatus further comprises means for receiving, from the first device, a request to establish a peer connection with the second device, the request comprising information about at least one of an identifier of the first device, an identifier of the second device, and an identifier of a data stream associated with the data unit.

[0078] In some embodiments, the first configuration information comprises information about at least one of a radio bearer used on the first access link for the peer connection and an identifier of the peer connection.

[0079] In some embodiments, the second configuration information comprises at least one of information about at least one of a radio bearer used on the second access link for the peer connection and an identifier of the peer connection.

[0080] In some embodiments, the first routing and bearer mapping configuration information includes information about at least one of: a routing identifier for routing a data unit to a next-hop device in an integrated access and backhaul network, an identifier of the next-hop device, an identifier of a peer connection, an identifier of a radio bearer used on a first access link for the peer connection, an identifier of a logical channel used on the first access link for the peer connection, and an identifier of a logical channel for sending a backhaul adaptation protocol packet carrying the data unit to the next-hop device.

[0081] In some embodiments, the second bearer mapping configuration information includes information about at least one of: an identifier of the second device, an identifier of the peer connection, an identifier of a radio bearer used on a second access link for the peer connection, an identifier of a logical channel used on the second access link for the peer connection, and an identifier of the second access link.

[0082] In some embodiments, the device also includes means for determining at least one device in the integrated access and backhaul network, the at least one device including the third device and the fourth device, and forming a routing path for a peer connection from the first device to the second device bypassing the donor device.

[0083] In some embodiments, the peer connection simulates a sidelink connection between a first device and a second device, and includes a sidelink packet data convergence protocol communication layer and a sidelink service data adaptation protocol communication layer, which are terminated at the first device and the second device and transparently relayed through an integrated access and backhaul network.

[0084] In the sixteenth aspect, a computer-readable medium is disclosed, comprising instructions stored thereon, the instructions being used to enable an apparatus as a first device to: receive peer connection configuration information for a first device and a second device from a donor device in an integrated access and backhaul network via an integrated access and backhaul network; and based on the configuration information, send data units of the peer connection to a third device in the integrated access and backhaul network serving the first device via an access link.

[0085] In some embodiments, the instructions further cause the apparatus to send a request for establishing a peer connection with the second device, the request comprising information about at least one of an identifier of the first device, an identifier of the second device, and an identifier of a data stream associated with the data unit.

[0086] In some embodiments, the configuration information comprises information about at least one of a radio bearer used on an access link for the peer connection and an identifier of the peer connection.

[0087] In some embodiments, the instructions further cause the apparatus to determine a radio bearer for sending the data unit over the access link based on the configuration information.

[0088] In some embodiments, the first device is a user equipment or a mobile terminal portion of an integrated access and backhaul network node device in an integrated access and backhaul network.

[0089] In some embodiments, the peer connection simulates a sidelink connection between a first device and a second device, and includes a sidelink packet data convergence protocol communication layer and a sidelink service data adaptation protocol communication layer, which are terminated at the first device and the second device and transparently relayed through an integrated access and backhaul network.

[0090] In a seventeenth aspect, a computer-readable medium is disclosed comprising instructions stored thereon, the instructions being used to cause an apparatus serving as a first device in an integrated access and backhaul network to: receive routing and bearer mapping configuration information for a peer connection between a second device and a third device served by the first device from a donor device in the integrated access and backhaul network via the integrated access and backhaul network; receive a data unit of the peer connection from the second device via an access link; and send a backhaul adaptive protocol packet comprising a backhaul adaptive protocol header and a data unit based on the routing and bearer mapping configuration information, the backhaul adaptive protocol header comprising information associated with the peer connection.

[0091] In some embodiments, the routing and bearer mapping configuration information includes information about at least one of: a routing identifier for routing a data unit to a next hop device, an identifier of the next hop device, an identifier of a peer connection, an identifier of a radio bearer used on an access link for the peer connection, and an identifier of a logical channel used on the access link for the peer connection, and an identifier of a logical channel for sending the backhaul adaptation protocol packet to the next hop device.

[0092] In some embodiments, the information associated with the peer connection includes at least one of: a routing identifier for routing data units to a next hop device in the integrated access and backhaul network, an identifier of the peer connection, an identifier of a radio bearer used on an access link for the peer connection, and an identifier of the second device.

[0093] In some embodiments, the peer connection simulates a sidelink connection between a second device and a third device, and includes a sidelink packet data convergence protocol communication layer and a sidelink service data adaptation protocol communication layer, which are terminated at the second device and the third device and transparently relayed through an integrated access and backhaul network.

[0094] In an eighteenth aspect, a computer-readable medium is disclosed, comprising instructions stored thereon, the instructions being used to enable an apparatus as a first device to: receive configuration information for a peer connection between a first device and a second device from a donor device in an integrated access and backhaul network via an integrated access and backhaul network; and based on the configuration information, receive data units of the peer connection from a third device serving the first device in the integrated access and backhaul network via an access link.

[0095] In some embodiments, the configuration information comprises information about at least one of a radio bearer used on an access link for the peer connection and an identifier of the peer connection.

[0096] In some embodiments, the instructions further cause the apparatus to determine a radio bearer for carrying the data unit on the access link based on the configuration information.

[0097] In some embodiments, the first device is a user equipment or a mobile terminal portion of an integrated access and backhaul network node device in an integrated access and backhaul network.

[0098] In some embodiments, the peer connection simulates a sidelink connection between a first device and a second device, and includes a sidelink packet data convergence protocol communication layer and a sidelink service data adaptation protocol communication layer, which are terminated at the first device and the second device and transparently relayed through an integrated access and backhaul network.

[0099] In a nineteenth aspect, a computer-readable medium is disclosed comprising instructions stored thereon, the instructions being used to cause an apparatus as a first device in an integrated access and backhaul network: to receive, from a donor device in the integrated access and backhaul network via the integrated access and backhaul network, bearer mapping configuration information for a peer connection between a second device and a third device connected by the first device; to receive a backhaul adaptation data packet comprising a backhaul adaptation protocol header and a data unit of the peer connection, the backhaul adaptation information packet comprising information associated with the peer link; and to send the data unit to the third device via the first access link based on the bearer mapping configuration information and the backhaul adaptation protocol header.

[0100] In some embodiments, the bearer mapping configuration information includes information about at least one of: an identifier of a third device, an identifier of a peer connection, an identifier of a radio bearer used on a first access link for the peer connection, an identifier of a logical channel used in the first access link for the peer connection, and an identifier of the first access link.

[0101] In some embodiments, the information associated with the peer connection includes at least one of: an identifier of the peer connection, an identifier of a radio bearer used on a second access link between a second device and a fourth device serving the second device in an integrated access and backhaul network for the peer connection, an identifier of the second access link, and a second device identifier.

[0102] In some embodiments, the peer connection simulates a sidelink connection between a second device and a third device, and includes a sidelink packet data convergence protocol communication layer and a sidelink service data adaptation protocol communication layer, which are terminated at the second device and the third device and transparently relayed through an integrated access and backhaul network.

[0103] In the twentieth aspect, a computer-readable medium is disclosed, comprising instructions stored thereon, the instructions being used to enable an apparatus serving as a donor device in an integrated access and backhaul network to: send first configuration information for a peer connection between a first device and a second device to a first device via the integrated access and backhaul network, so that the first device can send data units of the peer connection to a third device serving the first device in the integrated access and backhaul network via a first access link; send second configuration information for the peer connection to the second device, so that the second device can receive the data units from a fourth device serving the second device in the integrated access and backhaul network via a second access link; send first routing and bearer mapping configuration information for the peer connection to the third device; and send second bearer mapping configuration information for the peer connection to the fourth apparatus.

[0104] 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 receive, from the first device, a request to establish a peer connection with the second device, the request comprising information about at least one of an identifier of the first device, an identifier of the second device, and an identifier of a data stream associated with the data unit.

[0105] In some embodiments, the first configuration information comprises information about at least one of a radio bearer used on the first access link for the peer connection and an identifier of the peer connection.

[0106] In some embodiments, the second configuration information comprises at least one of information about at least one of a radio bearer used on the second access link for the peer connection and an identifier of the peer connection.

[0107] In some embodiments, the first routing and bearer mapping configuration information includes information about at least one of: a routing identifier for routing a data unit to a next-hop device in an integrated access and backhaul network, an identifier of the next-hop device, an identifier of a peer connection, and an identifier of a radio bearer used on the first access link for the peer connection, an identifier of a logical channel used on the first access link for the peer connection, and a logical channel identifier for sending a backhaul adaptation protocol packet carrying the data unit to the next-hop device.

[0108] In some embodiments, the second bearer mapping configuration information includes information about at least one of: an identifier of the second device, an identifier of the peer connection, an identifier of a radio bearer used on a second access link for the peer connection, an identifier of a logical channel used on the second access link for the peer connection, and an identifier of the second access link.

[0109] In some embodiments, the instructions further cause the apparatus to determine at least one device in the integrated access and backhaul network, the at least one device comprising the third device and the fourth device, and to form a routing path for a peer connection from the first device to the second device bypassing the donor device.

[0110] In some embodiments, the peer connection simulates a sidelink connection between a first device and a second device, and includes a sidelink packet data convergence protocol communication layer and a sidelink service data adaptation protocol communication layer, which are terminated at the first device and the second device and transparently relayed through an integrated access and backhaul network. BRIEF DESCRIPTION OF THE DRAWINGS

[0111] Some embodiments will now be described, by way of non-limiting examples, with reference to the accompanying drawings, in which like reference numerals designate similar or corresponding elements or parts in the various figures.

[0112] Figure 1 An example of a peer-to-peer connection between peer IAB nodes in an embodiment is shown.

[0113] Figure 2 An example of a configuration process for a desired peer connection in an embodiment is shown.

[0114] Figure 3 An example of a protocol stack at each node involved in a desired peer-to-peer connection is shown.

[0115] Figure 4 Another example of a peer-to-peer connection between peer IAB nodes in an embodiment is shown.

[0116] Figure 5 Another example of a configuration process for a desired peer connection in an embodiment is shown.

[0117] Figure 6 Another example of a protocol stack at each node involved in a desired peer-to-peer connection is shown.

[0118] Figure 7 An example method for peer-to-peer communication via an IAB network in an embodiment is shown.

[0119] Figure 8An example apparatus for peer-to-peer communication via an IAB network in an embodiment is shown.

[0120] Fig. 9 An example device for peer-to-peer communication via an IAB network in an embodiment is shown.

[0121] Fig.10 An example method for peer-to-peer communication via an IAB network in an embodiment is shown.

[0122] Fig.11 An example apparatus for peer-to-peer communication via an IAB network in an embodiment is shown.

[0123] Fig.12 An example device for peer-to-peer communication via an IAB network in an embodiment is shown.

[0124] Fig.13 An example method for peer-to-peer communication via an IAB network in an embodiment is shown.

[0125] Fig.14 An example apparatus for peer-to-peer communication via an IAB network in an embodiment is shown.

[0126] Fig.15 An example device for peer-to-peer communication via an IAB network in an embodiment is shown.

[0127] Fig.16 An example method for peer-to-peer communication via an IAB network in an embodiment is shown.

[0128] Fig.17 An example apparatus for peer-to-peer communication via an IAB network in an embodiment is shown.

[0129] Fig.18 An example device for peer-to-peer communication via an IAB network in an embodiment is shown.

[0130] Fig.19 An example method for peer-to-peer communication via an IAB network in an embodiment is shown.

[0131] Fig. 20 An example apparatus for peer-to-peer communication via an IAB network in an embodiment is shown.

[0132] Fig.21 An example device for peer-to-peer communication via an IAB network in an embodiment is shown. DETAILED DESCRIPTION

[0133] The IAB network may be configured with a spanning tree (ST) and directed acyclic graph (DAG) topology, which may include a donor base station (also referred to as a donor node or IAB donor in an IAB network) hosting a central unit (CU) function and one or more IAB nodes. The centralized mechanism at the IAB donor CU may have an overview of the entire network / path, which may be used for handover decisions, topology changes, routing, bearer mapping, etc. The IAB node may include: a mobile terminal (MT) part for communicating with a parent node in the IAB network (e.g., another IAB node or an IAB donor serving the IAB node) via an uplink (UL); and a distributed unit (DU) part for communicating with a child node in the IAB network (e.g., another IAB node served by the IAB node) or a user equipment (UE) served by the IAB node via a downlink (DL).

[0134] Efficient multi-hop forwarding can be achieved via an IAB-specific backhaul adaptation protocol (BAP), wherein each IAB node hosting a distributed unit (DU) function can be assigned a unique Layer 2 (L2) address (BAP address) by the IAB donor, which can be routed from and / or to the IAB donor. The BAP of the source node (IAB donor DU for DL ​​services, and access IAB node for UL services) can add a BAP header to the data packet or data unit it sends. The BAP header may include, for example, information about a BAP routing identifier (e.g., the BAP address and optional path identifier of the target / source IAB node). Each IAB node may have a routing table, which may be configured by the IAB donor CU and may include information such as a next hop identifier for each BAP routing identifier. For example, separate routing tables may be reserved for DL ​​and UL directions in the IAB node, wherein the DL table may be used by the DU portion of the IAB node, and the UL table may be used by the MT portion of the IAB node. One or more intermediate IAB nodes between the access IAB node and the IAB donor for the intended data traffic may forward data packets (e.g., service data units or SDUs) based on a routing identifier or a destination address. A backhaul (BH) radio link control (RLC) channel may be used to send data packets between a child IAB node and a parent IAB node or between an IAB node MT and an IAB donor DU, and mapping (e.g., N:1 mapping and 1:1 mapping) between UE radio bearers and BH RLC channels may be performed based on specific parameters such as a quality of service (QoS) profile of the bearer.

[0135] There are some use cases where it is desirable for peer IAB nodes (e.g., the branch from the IAB donor to one of the peer IAB nodes is different from the branch from the IAB donor to another peer IAB) to communicate directly with each other in a mesh topology (e.g., bypassing the IAB donor), which is also referred to as peer-to-peer (P2P) communication / connection between peer IAB nodes, such as in the form of control plane (CP) signaling to achieve more responsive inter-node coordination and / or such as in the form of user plane (UP) data to reduce UP latency and the path length traversed by data packets (e.g., when data is to be sent locally from a UE served by one IAB node to another UE served by a nearby IAB node). For example, a PC5 interface (interface for proximity services direct communication) can be used to achieve P2P connections between peer IAB nodes (e.g., peer IAB MTs of two IAB nodes) or peer UEs accessing an IAB network, for example, by using a PC5-based sidelink function. However, implementation of P2P connections based on PC5 via an IAB network may involve complex radio resource allocation including allocation between BH / access link and side link (SL) resources.

[0136] In various embodiments of the present disclosure, P2P connection via the IAB network may be achieved through a Uu (interface between UE and network) interface or access link without using a PC5 interface.

[0137] Figure 1 An example of a P2P connection between peer IAB nodes in an embodiment is shown. In this example, an IAB network may include an IAB donor 105 and IAB nodes 101, 102, 103, 104, etc., wherein IAB node 102 is a parent node of IAB node 101 and a child node of IAB network node 103, IAB node 104 is another child node of IAB node 103, and a P2P connection 108 between an MT portion 106 of IAB node 101 and an MT portion 107 of IAB node 104 is expected.

[0138] In one embodiment, the IAB donor 105 may be notified of the expected P2P connection 108 by, for example, a request from the MT portion 106 of the IAB node 101 or the MT portion 107 of the IAB node 104. For example, such a request may include information about one or more of: an identifier of the MT portion 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 portion 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., a packet flow identifier identifying a flow of data packets or SDUs of the P2P connection 108 or a PC5 QoS flow of a flow), etc. In another embodiment, the IAB donor 105 may determine the P2P connection 108, for example, autonomously and / or in response to a request from an application layer, without receiving a request from the MT portion 106 of the IAB node 101 or the MT portion 107 of the IAB node 104.

[0139] like Figure 1 As shown in , for an expected P2P connection 108, the IAB donor 105 can determine a path 110 (e.g., the shortest path) between the MT portion 106 of the IAB node 101 and the MT portion 107 of the IAB node 104 via the IAB nodes 102 and 103, wherein an access link 111 via a Uu interface / access link (instead of a PC5 interface or a BH link) is used between the MT portion 106 of the IAB node 101 and the DU portion of the IAB node 102, the 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 (instead of a PC5 interface or a BH link) is used between the MT portion 107 of the IAB node 104 and the DU portion of the IAB node 103.

[0140] In addition, if Figure 1 As shown in , the IAB donor 105 may configure the DU portion 109 of the IAB node 103 to route 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, instead of routing the data packets of the P2P connection to the parent IAB node of the IAB node 103 in the IAB network, and the MT portion of the IAB node 103 may not involve the P2P connection 108, so that, for example, the path 110 determined for the intended 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.

[0141] It should be understood that the present disclosure is not limited to Figure 1 . In different embodiments, depending on the topology of the IAB network and the peer nodes / devices terminated at the desired P2P connection, the IAB donor 105 and / or one or more IAB nodes in the IAB network may be included in the determined path 110, and one or more IAB nodes, such as the IAB node 103, may be included in the determined path 110, wherein the MT portion is not involved in the P2P connection, and the DU portion is configured such that P2P data from a child IAB node or a served UE is routed to another child IAB node or another served UE, rather than to a parent IAB node or an IAB donor. In another embodiment, the IAB nodes included in the path determined for the P2P connection may also be configured to route P2P data from one parent IAB node of the IAB node to another parent IAB node of the IAB node, rather than to a child IAB node of the IAB node.

[0142] Figure 2 An example of a configuration process of a desired P2P connection 108 in one embodiment is shown, wherein the IAB donor 105 can determine configuration information of each IAB node included in the path 110, and can send 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 can operate accordingly to implement the P2P connection 108.

[0143] 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 the Packet Data Convergence Protocol (PDCP) and / or the Service Data Adaptation Protocol (SDAP) in the IAB node, information for configuring the RLC, etc. For example, the information for configuring the PDCP and / or SDAP may be used to define the radio bearers used by the MT part 106 of the IAB node 101 for the P2P connection 108. And the P2P connection 108 may be implicitly indicated or identified, for example, based on the PDCP / SDAP configuration, for example, in the case where the radio bearers defined by the PDCP / SDAP configuration for mapping data packets or SDUs to be sent or received by the MT part 106 of the IAB node 101 are to be mapped to separate BH RLC channels in the IAB network (1:1 mapping) and the BH RLC channel is part of a BH chain dedicated to the P2P connection via the IAB network.

[0144] In another embodiment, the configuration 201 may also include information about the P2P connection 108, an identifier or indication for uniquely identifying or indicating the P2P connection 108 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 portion 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 that can uniquely identify or indicate the P2P connection 108 within the IAB network. For example, the identifier or indication of the P2P connection 108 may be a single identifier, a combination of multiple information items (e.g., a combination of two or more of a BAP address of the IAB node 102 serving the MT portion 106 of the IAB node 101, an identifier of a radio bearer mapping a data packet or SDU to be sent or received by the MT portion 106 of the IAB node 101, and a BAP address of the IAB node 101), etc.

[0145] In different embodiments, configuration information 201 may be sent in any suitable form at any suitable time. For example, when IAB donor 105 receives a request for desired P2P connection 108 from MT portion 106 of IAB node 101 or MT portion 107 of IAB node 104, configuration information 201 may be included in a response to the request.

[0146] Based on the configuration information 201, for example, the MT part 106 of the IAB node 101 can determine a radio bearer for sending or carrying data units on the access link so as to send data units of the P2P connection 108 to the IAB node 102 or receive data units 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.

[0147] 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 the information items in the configuration information 201, and may be in a similar form to the configuration information 202. 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 to define radio bearers used by the MT part 107 of the IAB node 104 for the P2P connection 108, information for configuring RLC, information about an identifier or indication of the P2P connection 108, etc. In addition, similar to the configuration information 201, for example, in the case where the IAB donor 105 receives a request for a desired P2P connection 108 from the MT part 106 of the IAB node 101 or the MT part 107 of the IAB node 104, the configuration information 204 may be included in a response to the request.

[0148] Based on the configuration information 204, for example, the MT part 107 of the IAB node 104 can determine a radio bearer for sending or carrying data units on the access link so as to send data units of the P2P connection 108 to the IAB node 103 or receive data units 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.

[0149] like Figure 2 As shown in , IAB donor 105 may also determine and send configuration information 202 to IAB node 102, which serves MT portion 106 of IAB node 101 and is included in determined path 110. For example, configuration information 202 may provide IAB node 102 with routing and mapping configuration information.

[0150] For example, in the case where the MT portion 106 of the IAB node 101 served by the IAB node 102 sends a data packet to the MT portion 107 of the IAB node 104 via the P2P connection 108 or the path 110, the configuration information 202 may include configuration information of the IAB node 102. In this case, the MT portion 106 of the IAB node 101 may be at least a portion of the sending peer device, and the MT portion 107 of the IAB node 104 may be a portion of the receiving peer device.

[0151] For example, the configuration information of the IAB node 102 as a sending access IAB node may include, but is not limited to, one or more of the following: information for configuring an RLC channel; at least one routing table for determining a next hop for a sent data packet / unit; an identifier or indication of a P2P connection 108; an identifier of a radio bearer for the P2P connection 108; information about a mapping of a 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 a radio bearer of the P2P connection with an RLC channel; at least one mapping table for determining a mapping of an ingress (P2P) RLC channel to an egress RLC channel on a next hop link selected, for example, based on a routing table; an association of an identifier of the P2P connection 108 with an identifier of a logical channel such as an RLC channel; an association of an identifier of a radio bearer of the P2P connection 108 with an identifier of a logical channel; and the like.

[0152] It is understood that the information items in the configuration information 202 are not limited to the above examples. For example, in the case of 1:1 mapping, the P2P connection 108 may be implicit and may be associated with the RLC channel, and therefore, the information about the identifier of the P2P connection 108 may be omitted from the configuration information 202. It is understood that the configuration information 202 may be in any suitable form or format. For example, the information about the association of the identifier of the P2P connection 108 with the identifier of the RLC channel may include or may be represented by information about the identifier of the P2P connection and the RLC channel identifier, or may be an indication / flag configured in a designated field in the configuration information 202.

[0153] In addition, in the case where the MT portion 106 of the IAB node 101 served by the IAB node 102 receives data packets from the MT portion 107 of the IAB node 104 via the P2P connection 108 or the path 110, the configuration information 202 may also include the configuration information of the IAB node 102. In this case, the MT portion 106 of the IAB node 101 may be at least a part of the receiving peer device, and the MT portion 107 of the IAB device 104 may be a part of the sending peer device. In this case, the configuration information of the IAB node 102 may be similar to the configuration information of the IAB node 102 acting as a sending access IAB node. In one embodiment, for the IAB node 102 acting as a receiving access IAB node, information about the routing table may be omitted from the configuration information 202. In addition, for example, in the case of 1:1 mapping, information about the identifier of the P2P connection 108 may also be omitted from the configuration information 202.

[0154] IAB node 102 may use configuration information 202, for example, to map and route data units, generate BAP headers (described later), and so on.

[0155] like Figure 2 As shown in , the IAB donor 105 may also send configuration information 203 to the IAB node 103 serving the MT portion 107 of the IAB node 104. Similar to the configuration information 202 for the IAB node 102, the configuration information 203 includes configuration information for the IAB node 103 acting as a sending access IAB node and / or configuration information for the IAB node 103 acting as a receiving access IAB node, which may be similar to the configuration information of the IAB node 102 acting as a sending access IAB node and the configuration information of the IAB node 102 acting as a receiving access IAB, respectively, and will not be repeated here.

[0156] In addition, as a "special" intermediate IAB node, the IAB node 103 can be configured based on the configuration information 203 from the IAB donor, so that when the data unit is associated with the P2P connection 108, the MT part of the IAB node 103 does not involve the P2P connection 108, and the routing table of the P2P connection 108 in the DU part 109 of the IAB node 103 includes information about the route 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 about the route from the IAB node 104 to the IAB node 102 instead of the parent IAB node of the IAB node 103.

[0157] In addition, if Figure 2 As shown, in one embodiment, before the IAB donor 105 determines and provides the configuration information 201 to 204, an operation 205 of service authorization and provisioning, which may also involve a core network (CN) 206, may be performed. For example, through operation 205, any suitable information associated with P2P service authorization and provisioning, such as a PC5 QoS profile and PC5 QoS rules (e.g., each associated with a packet flow identifier or PFI) for each PC5 QoS flow, may be provided to the MT portion 106 of the IAB node 101, the MT portion 107 of the IAB node 104, and possibly the IAB donor 105. Thus, for example, for a data packet of the P2P connection 108, the MT portion 106 of the IAB node 101 or the MT portion 107 of the IAB node 104 as a sending peer device may map the data packet to a PC5 QoS flow based on the QoS rules received in operation 205, which may be further mapped to a radio bearer. In one embodiment, the request from the MT portion 106 of the IAB node 101 or the MT portion 107 of the IAB node 104 to the IAB donor 105 on the P2P connection 108 may include information about the PC5 QoS flow (eg, the PFI of the flow).

[0158] It is understood that the configuration process of the P2P connection 108 is not limited to the following. Figure 2 In another embodiment, the respective configuration information 201, 202, 203, and 204 may be sent from the IAB donor 105 to the respective IAB nodes 101, 102, 103, and 104 in any suitable order, and any suitable manner may be employed to ensure that P2P communication via the P2P connection 108 may be performed after the respective associated IAB nodes 102, 103, 104 have been appropriately configured. In another embodiment, the respective IAB node 101, 102, 103, or 104 may send, for example, a response to the receipt of the respective configuration information 201, 202, 203, or 204.

[0159] Figure 3 1 shows an example of a protocol stack at each node involved in the P2P connection 108, wherein 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 layer may be configured based on the corresponding configuration information from the IAB donor 105, for example. Figure 2 The configuration phase is shown during which control and configuration by the IAB donor 105 is performed.

[0160] like Figure 3 As shown in FIG. 1 , higher P2P protocol layers such as the SDAP layer and the PDCP layer may use a P2P protocol (e.g., a sidelink protocol) for the P2P connection 108, while lower protocol layers (e.g., an RLC layer and a MAC layer) use a wireless link. On access links 111 and 113, there is an RLC layer and a media access control (MAC) layer (also Figure 3 ), and on the BH link 112, there is also a BAP layer for routing and bearer mapping on the RLC channel.

[0161] For example, in the case where the MT part 106 of the IAB node 101 sends P2P data to the MT part 107 of the IAB node 104, the MT part 106 of the IAB node 101 may, for example, based on Figure 2 The configuration information 201 shown in FIG. 1 determines a radio bearer for sending data units of the P2P connection 108 on the access link 111 , and the data units in the P2P connection 108 may then be sent to the DU part of the IAB node 102 via the access link 111 .

[0162] For a data unit received by the DU portion of the IAB node 102 via the access link 111, the IAB node (acting as a sending access IAB node) may determine, for example, based on the radio bearer used to carry the data unit and the configuration information 202, that the received data unit is associated with the P2P connection 108. Then, in operation 301, the IAB node 102 may generate a BAP packet including an appropriate BAP header and the received data unit.

[0163] For example, the BAP header added in operation 301 may include a routing identifier for routing the data unit to the next hop along the peer path. In another embodiment, the BAP header added in operation 301 may also include information for identifying the P2P connection 108 and / or the radio bearer used on the access link 111 for the P2P connection 108. For example, the BAP header added in operation 301 may include an identifier of the P2P connection 108, which may be a globally unique identifier assigned by the IAB donor 105 and 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 a BAP address of the IAB node 102, an identifier of the radio bearer on the access link 111, a BAP address of the IAB node 101, or an identifier of the MT part 106 of the IAB node. In another embodiment, the BAP header added in operation 301 may also include information for identifying the radio bearer on the access link 111.

[0164] Then, the IAB node 102 may send the generated BAP packet to its next hop (IAB node 103 ) via the BH link 112 , for example, based on the routing table and mapping table included in the configuration information 202 .

[0165] In the DU portion 109 of the IAB node 103, in response to receiving the BAP packet from the IAB node 102, the IAB node 104 may determine whether the received BAP packet is associated with a P2P connection, for example, based on a BAP header of the BAP packet. For example, the DU portion 109 of the IAB node 103 may parse the BAP packet in operation 302 to check for an identifier or indication of a P2P connection.

[0166] Upon determining that the received BAP packet is associated with the P2P connection 108 (e.g., when checking for the presence of an identifier or indication of the P2P connection 108), the DU portion 109 of the IAB node 103, as an access IAB node serving the MT portion 107 of the IAB node 104 as a target peer device, may remove the BAP header in operation 302. Then, for example, based on at least one of the BAP header and the configuration information 203, the DU portion 109 of the IAB node 103 may determine an identifier of an RLC channel on the access link 113 for the P2P connection 108, and may send a data unit obtained from the BAP packet to the target of the P2P connection 108 (the MT portion 107 of the IAB node 104) via the determined RLC channel on the access link 113.

[0167] In case it is determined 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, which may involve the MT portion of the IAB node.

[0168] Similarly, in the case where the MT portion 107 of the IAB node 104 sends P2P data to the MT portion 106 of the IAB node 101, the MT portion 107 of the IAB node 104 may, for example, send P2P data based on the following information: Figure 2 The configuration information 204 shown in FIG. 1 determines a radio bearer for sending data units of the P2P connection 108 on the access link 113, and the data units of the P2P connection 108 can then be sent to the DU part of the IAB node 103 via the access link 113. It should be understood that the access link 113 involved in the case where the MT part 107 of the IAB node 104 sends P2P data to the MT part 106 of the IAB node 101 and the access link 113 involved when the MT part 106 of the IAB node 101 sends P2P data to the MT part 107 of the IAB node 104 may be the same or different.

[0169] Then, similar to the case where the MT part 106 of the IAB node 101 sends 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 sends P2P data to the MT part 106 of the IAB node 101, the IAB node 103 (acting as a sending access IAB node) may determine, for example, based on the radio bearer used to carry the data unit and the configuration information 203 that the received data unit is associated with the P2P connection 108. Then, in operation 302, the IAB node 103 may generate a BAP packet including a BAP header and the received data unit.

[0170] For example, the BAP header added in operation 302 may include a routing identifier for routing the data unit to the next hop. In another embodiment, the BAP header added in operation 302 may also include information for identifying the P2P connection 108 and / or a radio bearer for the P2P connection 108 on the access link 113. For example, the BAP header added in operation 302 may include an identifier of the P2P connection 108, which may be a globally unique identifier assigned by the IAB donor 105 and 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 a BAP address of the IAB node 103, an identifier of a radio bearer on the access link 113, a BAP address of the IAB node 104, or an identifier of the MT part 107 of the IAB node 104. In another embodiment, the BAP header added in operation 302 may also include information for identifying a radio bearer on the access link 113.

[0171] Then, the IAB node 103 may send the generated BAP packet to its next hop (IAB node 102 ) via the BH link 112 , for example, based on the routing table and mapping table included in the configuration information 203 .

[0172] In the DU portion of the IAB node 102, in response to receiving a BAP packet from the IAB node 103, the IAB node 104 may determine whether the received BAP packet is associated with a P2P connection, for example, based on a BAP header of the BAP packet. For example, the DU portion of the IAB node 102 may parse the BAP packet in operation 301 to check for an identifier or indication of a P2P connection.

[0173] Upon determining that the received BAP packet is associated with the P2P connection 108 (e.g., when checking the presence of an identifier in the BAP header or an indication of the P2P connection 108), the DU portion of the IAB node 102, as an access IAB node serving the MT portion 106 of the IAB node 101 as a target peer device, may remove the BAP header in operation 301. Then, for example, based on at least one of the BAP header and the configuration information 202, the DU portion of the IAB node 102 may determine an identifier of an RLC channel on the access link 111 of the P2P connection 108, and may send a data unit obtained from the BAP packet to the target of the P2P connection 108 (the MT portion 106 of the IAB node 101) via the determined RLC channel on the access link 111.

[0174] It is to be understood that the access link 111 involved in the case where the MT portion 107 of the IAB node 104 sends P2P data to the MT portion 106 of the IAB node 101 and the access link 111 involved in the case where the MT portion 106 of the IAB node 101 sends P2P data to the MT portion 107 of the IAB node 104 may be the same or different. In addition, it is to be understood that the BH link 112 involved in the case where the MT portion 107 of the IAB node 104 sends P2P data to the MT portion 106 of the IAB node 101 and the BH link 112 involved in the case where the MT portion 106 of the IAB node 101 sends P2P data to the MT portion 107 of the IAB node 104 may be the same or different.

[0175] Therefore, the P2P connection 108 between peer devices (MT portion 106 of IAB node 101 and MT portion 107 of IAB node 104) in the IAB network may be implemented via the access link / Uu interface instead of the PC5 interface.

[0176] Figure 4 An example of a P2P connection between peer UEs via an IAB network in an embodiment is shown. In this example, the IAB network may include an IAB donor 405 and IAB nodes 401, 402, 403, 404, etc., wherein the IAB node 402 is a parent node of the IAB node 401 and a child node of the IAB network node 403, the IAB node 404 is another child node of the IAB node 403, and a P2P connection 408 is desired between a UE 406 served by the IAB 401 and a UE 407 served by the IAB network 404.

[0177] In one embodiment, IAB donor 405 may be notified of the expected P2P connection 408 by, for example, a request from UE 406 or UE 407. For example, such a request may include information about one or more of the following: an identifier of UE 406 or IAB node 401 (e.g., a BAP address of IAB node 404), an identifier of UE 407 or IAB node 404 (e.g., a BAP address of IAB node 406), an identifier of a data flow (e.g., a packet flow identifier of a PC5 QoS flow that maps data packets or SDUs of P2P connection 408), etc. In another embodiment, IAB donor 405 may determine P2P connection 408, for example, autonomously and / or in response to a request from an application layer, without receiving a request from UE 406 or UE 407.

[0178] like Figure 4As shown in , for an expected P2P connection 408, the IAB donor 405 can 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, wherein 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 portion 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 DU portion of the UE 407 and the IAB node 404.

[0179] In addition, if Figure 4 As shown in , the IAB donor 405 may configure the DU portion 409 of the IAB node 403 to route 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, instead of routing the data packets of the P2P connection 408 to the parent IAB node of the IAB node 403 in the IAB network, and the MT portion of the IAB node 403 may not involve the P2P connection 408, so that, for example, the path 410 determined for the intended 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.

[0180] It should be understood that the present disclosure is not limited to Figure 4 . In different embodiments, depending on the topology of the IAB network and the peer nodes / devices terminated at the expected P2P connection, the IAB donor 405 and / or one or more IAB nodes in the IAB network may be included in the determined path 410, and one or more IAB nodes, such as the IAB node 403, may be included in the determined path 410, wherein the MT portion is not involved in the P2P connection, and the DU portion is configured such that P2P data from a child IAB node or a served UE is routed to another child IAB node or another served UE, rather than the parent IAB node and the IAB donor. In another embodiment, the IAB nodes included in the path determined for the P2P connection may also be configured to route P2P data from one parent IAB node of the IAB node to another parent IAB node in the IAB node, rather than a child IAB node on the IAB node.

[0181] Figure 5An example of a configuration process for an expected P2P connection 408 in one embodiment is shown, wherein an IAB node 405 may determine configuration information for UE 406, UE 407, and corresponding IAB nodes included in a path 410, and may send configuration information 501, 502, 503, 504, 505, and 506 associated with the P2P connection 408 to UE 406, IAB node 401, IAB node 402, IAB node 403, IAB node 404, and UE 407, respectively, for example via one or more downlinks in the IAB network, so that UE 406, IAB node 401, IAB node 402, IAB node 403, IAB node 404, and UE 407 may operate accordingly to implement the P2P connection 408.

[0182] 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, etc. For example, the information for configuring PDCP or SDAP may be used to define a radio bearer used by the UE 406 for the P2P connection 408. And for example, in the case where the radio bearer defined by the PDCP / SDAP configuration for mapping data packets or SDUs to be sent or received by the UE 406 is to be mapped to a separate BH RLC channel in the IAB network (1:1 mapping) and the BH RLC channel is part of a BH chain dedicated to the P2P connection via the IAB network, the P2P connection 408 may be implicitly indicated or identified, for example, based on the PDCP / SDAP configuration.

[0183] In another embodiment, the configuration 501 may also include information about the P2P connection 408, an identifier or indication for uniquely identifying or indicating the P2P connection 408 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 uniquely identifying or indicating the P2P connection 408 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 an identifier of a radio bearer to which a data packet or SDU to be sent or received by the UE 406 is mapped, and an identifier of the UE 406), and the like.

[0184] In different embodiments, configuration information 501 may be sent in any suitable form at any suitable timing. For example, in the case where IAB donor 405 receives a request for desired P2P connection 408 from UE 406 or UE 407, configuration information 501 may be included in a response to the request.

[0185] Based on the configuration information 501, for example, the UE 406 may determine a radio bearer for sending or carrying a data unit on an access link so as to send a data unit of the P2P connection 408 to the IAB node 401 or receive a data unit in the P2P connection 408 from the IAB node 402 corresponding to a P2P data reception or a P2P data transmission at the UE 406.

[0186] Configuration information 506 from IAB node 405 to UE 407 may include one or more information items similar to those in configuration information 501, and may be in a similar form to configuration information 502. For example, similar to configuration information 501, configuration information 506 may also include one or more of the following: information for configuring PDCP and / or SDAP to define radio bearers used by UE 407 for P2P connection 408, information for configuring RLC, information about P2P connection 408 identifiers or indications, etc. In addition, similar to configuration information 501, for example, in the case where IAB donor 405 receives a request from UE 406 or UE 407 that P2P connection 408 is desired, configuration information 506 may be included in a response to the request.

[0187] Based on the configuration information 506, for example, corresponding to P2P data reception or P2P data transmission at the UE 407, the UE 407 may determine a radio bearer for sending or carrying data units on the access link in order to send data units of the P2P connection 408 to the IAB node 404, or to receive data units of the P2P connection 408 from the IAB node 404.

[0188] like Figure 5 As shown in , the IAB donor 405 may also determine and send configuration information 502 to the IAB node 401 that serves the UE 406 and is included in the determined path 410. For example, the configuration information 502 may provide the IAB node 401 with routing and mapping configuration information.

[0189] For example, where UE 406 sends data packets to UE 407 via P2P connection 408 or path 410, configuration information 502 may include configuration information for IAB node 401. In this case, UE 406 may be at least part of a sending peer device and UE 407 may be part of a receiving peer device.

[0190] For example, the configuration information of the IAB node 401 as a sending access IAB node may include, but is not limited to, one or more of the following: information for configuring an RLC channel; at least one routing table for determining a next hop of a sent data packet / unit; an identifier or indication of a P2P connection 408; an identifier of a radio bearer of the P2P connection 408; information about a mapping of the P2P connection 408 or the P2P connection 408 to a routing identifier, or information about an association between an identifier of the P2P connection 408 or the radio bearer of the P2P connection 408 and an RLC channel; at least one mapping table for determining a mapping of an ingress (P2P) RLC channel to an egress RLC channel on a next hop link selected, for example, based on a routing table; an association between an identifier of the P2P connection 408 and an identifier of a logical channel such as an RLC channel; an association between an identifier of the radio bearer of the P2P connection 408 and an identifier of a logical channel; and the like.

[0191] It is understood that the information items in the configuration information 502 are not limited to the above examples. For example, in the case of 1:1 mapping, the P2P connection 408 may be implicit and may be associated with the RLC channel, and therefore, the information about the identifier of the P2P connection 408 may be omitted from the configuration information 502. It is understood that the configuration information 502 may be in any suitable form or format. For example, the information about the association of the identifier of the P2P connection 408 with the identifier of the RLC channel may include or may be represented by information about the identifier 408 of the P2P connection and the RLC channel identifier, or may be an indication / flag configured in a designated field in the configuration information 502.

[0192] In addition, in the case where UE 406 receives a data packet from UE 407 via P2P connection 408 or path 410, configuration information 502 may also include configuration information of IAB node 401. In this case, UE 406 may be at least a part of a receiving peer device, and UE 407 may be at least a part of a sending peer device. In this case, the configuration information of IAB node 401 may be similar to the configuration information of IAB node 401 acting as a sending access IAB node. In one embodiment, for IAB node 401 acting as a receiving access IAB node, information about a routing table may be omitted from configuration information 502. In addition, for example, in the case of 1:1 mapping, information about an identifier of P2P connection 408 may also be omitted from configuration information 502.

[0193] IAB node 401 may use configuration information 502, for example, for mapping and routing data units, generating a BAP header (to be described later), and the like.

[0194] like Figure 5As shown in , the IAB donor 405 may also send configuration information 505 to the IAB node 404 serving the UE 407. Similar to the configuration information 502 of the IAB node 401, the configuration information 505 may include configuration information for the IAB node 404 acting as a sending access IAB node and / or configuration information for the IAB node 404 acting as a receiving access IAB, which may be similar to the configuration information of the IAB node 401 acting as a sending access IAB node and the configuration information of the IAB node 401 acting as a receiving access IAB, respectively, and will not be repeated here.

[0195] In addition, if Figure 5 As shown in , the IAB donor 406 may also send 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 configurations, which the IAB nodes 402 and 403 use to forward the BAP packet to the next hop, respectively. 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 does not involve the P2P connection 408, and in the case where the data unit is associated with the P2P connection 408, the routing table of the P2P connection 408 in the DU part 409 of the IAB node 403 includes information about the route 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 about the route from the IAB node 404 to the IAB node 402 instead of the parent IAB node of the IAB node 403.

[0196] In addition, if Figure 5 As shown in , in one embodiment, before the IAB donor 405 determines and provides the configuration information 501 to 506, an operation 507 of service authorization and provisioning may be performed, which may also involve the core network (CN) 508. For example, through operation 508, any suitable information associated with P2P service authorization and provisioning, such as a PC5 QoS profile and PC5 QoS rules for each PC5 QoS flow (e.g., each associated with a packet flow identifier or PFI) may be provided to the UE 406 and UE 407, and may also be provided to the IAB donor 405. Thus, for example, for data packets of the P2P connection 408, the UE 406 or UE 407 as a sending peer device may map the data packets to a PC5 QoS flow based on the QoS rules received in operation 507, which may be further mapped to a radio bearer. In one embodiment, the request from the UE 406 or UE 407 to the IAB donor 405 on the P2P connection 408 may include information about the PC5 QoS flow (e.g., the PFI of the flow).

[0197] It is understood that the configuration process of P2P connection 408 is not limited to the following. Figure 5 In another embodiment, the various configuration information 501 to 506 may be sent from the IAB donor 405 in any suitable order, and any suitable manner may be adopted to ensure that P2P communication can be performed via the P2P connection 408 after the various UEs and IAB nodes have been properly configured.

[0198] Figure 6 An example of a protocol stack at each node involved in a P2P connection 408 is shown, where for UE 406 and UE 407, the protocol layer may be as follows: Figure 5 During the configuration phase shown, IAB nodes 401 and 404 are controlled and configured, respectively, based on corresponding configuration information from IAB donor 405, for example.

[0199] like Figure 6 As shown in FIG. 4 , higher P2P protocol layers such as the SDAP layer and the PDCP layer may use a P2P protocol (e.g., a sidelink protocol) for the P2P connection 408, while lower protocol layers (e.g., an RLC layer and a MAC layer) use a radio link. On access links 411 and 415, there is an RLC layer and a media access control (MAC) layer (also Figure 6 ), and on BH links 412, 413 and 414, there is also a BAP layer for routing bearer mapping on the RLC channel.

[0200] For example, in the case where UE 406 sends P2P data to UE 407, UE 406 may, for example, Figure 5 The configuration information 501 shown determines a radio bearer for sending data units of the P2P connection 408 over the access link 411 , and the data units of the P2P connection 408 may then be sent to the DU portion of the IAB node 401 via the access link 411 .

[0201] For a data unit received by the DU portion of the IAB node 401 via the access link 411, the IAB node 401 (acting as a transmitting access IAB node) may determine, for example, based on a radio bearer for carrying the data unit and the configuration information 502, that the received data unit is associated with the P2P connection 408. Then, in operation 601, the IAB node 401 may generate a BAP packet including a BAP header and the received data unit.

[0202] For example, the BAP header added in operation 601 may include a routing identifier for routing the data unit to the next hop (e.g., the IAB node 402). In another embodiment, the BAP header added in operation 601 may also include information for identifying the P2P connection 408 and / or a radio bearer used on the access link 411 for the P2P connection 408. For example, the BAP header added in operation 601 may include an identifier of the P2P connection 408, which may be a globally unique identifier assigned by the IAB donor 405 and 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 a BAP address of the IAB node 401, an identifier of a radio bearer on the access link 411, an identifier of the UE 406, and the like. The BAP header added in operation 601 may also include information for identifying a radio bearer on the access link 411.

[0203] Then, the IAB node 401 may send the generated BAP packet to its next hop (IAB node 402 ) via the BH link 412 , for example, based on the routing table and mapping table included in the configuration information 503 .

[0204] For example, the intermediate IAB node 402 may forward the received BAP packet for the P2P connection 408 to its next hop (IAB node 403 ) via the BH link 413 based on the routing table and the mapping table included in the configuration information 504 .

[0205] In the DU portion 409 of the IAB node 403, in response to receiving a 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 a BAP header of the BAP packet. For example, the DU portion 409 of the IAB node 403 may parse the BAP packet to check for an identifier or indication of a P2P connection. For example, in the event that it is determined that the received BAP packet is associated with the P2P connection 408 (e.g., when checking for the presence of an identifier or indication of the P2P connection 408), the DU portion 409 of the IAB node 403 may forward the received BAP packet to its next hop (IAB node 404), for example, based on a routing table and a mapping table included in the configuration information 504, wherein, as shown in FIG. Figure 6 As shown in , the MT portion of the "special" intermediate IAB node 402 is not involved in the P2P connection 408, and therefore the BAP packets for the P2P connection 408 are routed by the IAB node 403 from its child IAB node 402 to its other child IAB node 404, such that the IAB donor 405 is bypassed.

[0206] Then, the MT part of the IAB node 404 receives the BAP packet from the IAB node 403. As an access IAB node serving the UE 407 as a target peer device, the IAB node 404 may remove the BAP header in 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 an identifier of an RLC channel on the access link 415 used for the P2P connection 408, and may send a data unit obtained from the BAP packet via the RLC channel on the determined access link 415 to the target (UE 407) of the P2P connection 408.

[0207] Similarly, in the case where UE 407 sends P2P data to UE 406, UE 407 may, for example, Figure 5 The configuration information 506 shown in FIG. 5 determines a radio bearer for sending data units of the P2P connection 408 through the access link 415, and the data units of the P2P connection 408 can then be sent to the DU part of the IAB node 404 via the access link 415. It should be understood that the access link 415 involved in the case where the UE 407 sends P2P data to the UE 406 and the access link 415 involved when the UE 406 sends P2P data to the UE 407 can be the same or different.

[0208] Then, the IAB node 404 (acting as a sending access IAB node) may determine, for example based on the radio bearer used to carry the data unit and the configuration information 505, that the received data unit is associated with the P2P connection 408. Then, in operation 602, the IAB node 404 may generate a BAP packet including a BAP header and the received data unit.

[0209] For example, the BAP header added in operation 602 may include a routing identifier for routing the data unit to the next hop. In another embodiment, the BAP header added in operation 602 may also include information for identifying the P2P connection 408 and / or a radio bearer used on the access link 415 for the P2P connection 408. For example, the BAP header added in operation 602 may include an identifier of the P2P connection 408, which may be a globally unique identifier assigned by the IAB donor 405 and 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 a BAP address of the IAB node 404, an identifier of a radio bearer on the access link 415, an identifier of the UE 407, and the like. In another embodiment, the BAP header added in operation 602 may also include information for identifying a radio bearer on the access link 415.

[0210] Then, the IAB node 404 may send the generated BAP packet to its next-hop IAB node 403 via the BH link 414, for example, based on the routing table and mapping table included in the configuration information 505. In the case where the BAP packet from another child IAB node 404 of the IAB node 403 is determined as P2P data, the IAB node 403 may send the received BAP packet to its child IAB node 402 via the BH link 413, for example, based on the routing table and mapping table included in the configuration information 504. The IAB node 402 may further forward the BAP packet from the IAB node 403 to its next-hop IAB node 402, for example, based on the routing table and mapping table included in the configuration information 503.

[0211] In the DU portion of the IAB node 401, in response to receiving a BAP packet from the IAB node 402, the IAB node 400 may determine whether the received BAP packet is associated with a P2P connection, for example, based on a BAP header of the BAP packet. For example, the DU portion of the IAB node 401 may parse the BAP packet in operation 601 to check for an identifier or indication of a P2P connection.

[0212] In the event that it is determined that the received BAP packet is associated with the P2P connection 408 (e.g., when checking for the presence of an identifier or indication of the P2P connection 408 in the BAP header), the DU portion of the IAB node 401, as an access IAB node serving the target device UE 406, may remove the BAP header in operation 601. Then, for example, based on at least one of the BAP header and the configuration information 502, the DU portion of the IAB node 401 may determine an identifier of an RLC channel on the access link 411 for the P2P connection 408, and may send a data unit obtained from the BAP packet via the determined RLC channel to the target (UE 406) of the P2P connection 408 via the access link 411.

[0213] It is understood that the access link 411 involved in the case where UE 407 sends P2P data to UE 406 and the access link 411 involved in the case where UE 406 sends P2P data to UE 407 may be the same or different. In addition, it is understood that the BH links 412, 413 and 414 involved in the case where UE 407 sends P2P data to UE 406 and the BH links 412, 413 and 414 involved in the case where UE 406 sends P2P data to UE 407 may be the same or different, respectively.

[0214] Therefore, the P2P connection 408 between peer devices (UE 406 and UE 407) via the IAB network may be implemented via the access link / Uu interface instead of through the PC5 interface.

[0215] As shown in the above examples, direct communication between peer IAB nodes or peer UEs is enabled, where P2P is located on higher protocol layers without changes, and Uu / access links are used for lower layers instead of PC5 radio connections that may cause complex processing.

[0216] It should be understood that the present disclosure is not limited to the above examples. For example, in one embodiment, in addition to the "hop-by-hop" ARQ on the intermediate link, the P2P automatic repeat request (ARQ) in the RLC can also be used between peer devices, such as 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.

[0217] Throughout this disclosure, modifiers such as "first", "second", "third", and "fourth" are used to distinguish different entities / devices / components / operations / elements in the embodiments, and are not intended to refer to specific entities / devices / components / operations / elements in various embodiments. For example, in one embodiment, "first device" and "second device" may refer to a sending peer device and a receiving peer device, in another embodiment, may refer to a sending peer device and a sending access device, or in another embodiment, may refer to a sending peer device and a sending access device, etc. For example, in one embodiment, "first device" may refer to a sending peer device, in another embodiment, may refer to a receiving peer device, in yet another embodiment, may refer to a sending access device, etc. Similarly, for example, in one embodiment, "second device" may refer to a sending peer device, in another embodiment, may refer to a receiving peer device, in yet another embodiment, may refer to a sending access device, etc. For example, a sending peer device that is a first device in one embodiment may be referred to as a second device in another embodiment. Similarly, a receiving access device that is a third device in one embodiment may be referred to as a first device in another embodiment.

[0218] Figure 7 An example method 700 for P2P communication via an IAB network in one embodiment is shown, which in the above example may be performed in a donor device that is at least part of an IAB donor such as IAB donor 105 or 405. Figure 7 As shown, example method 700 may include operation 701 , operation 702 , operation 703 , and operation 704 .

[0219] In operation 701, the donor device may send first configuration information (e.g., in the above example, configuration information 201 when the MT part 106 of the IAB node 101 is a sending peer device, configuration information 204 when the MT part 107 of the IAB node 104 is a sending peer device, configuration information 501 when the UE 406 is a sending peer device, and information 506 when the UE 407 is a sending peer device) to the first device (e.g., in the above example, the MT part 106 of the IAB node 101 as a sending peer device, the MT part 107 of the IAB device 104 as a sending peer device, the UE 406 as a sending peer device, and the UE 407 as a sending peer device) for the first device and the second device (e.g., in the above example, the MT part 106 of the IAB node 101 as a receiving peer device, the MT part 107 of the IAB node 104 as a receiving peer device, the UE 406 as a receiving peer device 406 and UE 407 as a receiving peer device) via a P2P connection (e.g., P2P connection 108 or 408 in the above example) of the IAB network, so that the first device can send a message to a third device (e.g., in the above example, at least a part of the IAB node 102 when the MT part 106 of the IAB node 101 is a sending peer device, at least a part of the IAB node 103 when the MT part 107 of the IAB node 104 is a sending peer device, and access link 415 when the UE 407 is a sending peer device) in the IAB network serving the first device via a first access link (e.g., in the above example, the access link 111 when the MT part 106 of the IAB node 101 is a sending peer device; the access link 113 when the MT part 107 of the IAB node 104 is a sending peer device; the access link 411 when the UE 406 is a sending peer device; and the access link 415 when the UE 407 is a sending peer device). 406 is a sending peer device, at least a portion of the IAB node 401, and when the UE 407 is a sending peer device, at least a portion of the IAB node 404) sends the data unit of the P2P connection (.

[0220] In operation 702, the donor device may send second configuration information for a second connection to the second device (e.g., in the above example, configuration information 204 when the MT part 107 of the IAB node 104 is a receiving peer device, configuration message 201 when the MT part 106 of the IAB node 101 is a receiving peer device, configuration information 501 when the UE 406 is a receiving peer device, and configuration command 506 when the UE 407 is a receiving peer device) to enable the second device to connect to the second device via a second access link (e.g., in the above example, access link 113 when the MT part 107 of the IAB node 104 is a receiving peer device, access link 111 when the MT part 106 of the IAB node 101 is a receiving peer device, access link 411 when the UE 406 is a receiving peer device, and access command 506 when the UE 407 is a receiving peer device). 407 is the receiving peer device, access link 415) receives the data unit from a fourth device serving a second device in the IAB network (e.g., in the above example, at least a portion of IAB node 103 when MT portion 107 of IAB node 104 is the receiving peer device, at least a portion of IAB node 102 when MT portion 106 of IAB device 101 is the receiving peer device, at least a portion of IAB node 401 when UE 406 is the receiving peer device, and at least a portion of IAB node 404 when UE 407 is the receiving peer device).

[0221] In addition, in operation 703, the donor device may send first routing and bearer mapping configuration information for the P2P connection to the third device (for example, in the above example, when the MT part 106 of the IAB node 101 is a sending peer device, it is configuration information 202, when the MT part 107 of the IAB node 104 is a sending peer device, it is configuration information 203, when the UE 406 is a sending peer device, it is configuration information 502, and when the UE 407 is a sending peer device, it is configuration information 505).

[0222] In addition, in operation 704, the donor device may send second bearer mapping configuration information for the peer connection to the fourth device (for example, in the above example, when the MT part 107 of the IAB node 104 is a receiving peer device, it is configuration information 203, when the MT part 106 of the IAB node 101 is a receiving peer device, it is configuration message 202, when the UE 406 is a receiving peer device, it is configuration information 502, and when the UE 407 is a receiving peer device, it is configuration information 505).

[0223] In some embodiments, the example method 700 may also include an operation of receiving a request from the first device to establish a P2P connection with the second device. For example, the request may include information about at least one of an identifier of the first device, an identifier of the second device, and an identifier of a data stream associated with the data unit.

[0224] In some embodiments, the first configuration information may include information about at least one of a radio bearer used on the first access link for the P2P connection and an identifier of the P2P connection.

[0225] In some embodiments, the second configuration information may include at least one of information regarding at least one of: a radio bearer used on the second access link for the P2P connection and an identifier of the P2P connection.

[0226] In some embodiments, the first routing and bearer mapping configuration information may include information about at least one of the following: a routing identifier for routing the data unit to a next hop device in the IAB network, an identifier of the next hop device, an identifier of the P2P connection, an identifier of a radio bearer used on the first access link for the P2P connection, an identifier of a logical channel used on the first access link for the P2P connection, and a logical channel identifier for sending a BAP packet carrying the data unit to the next hop device.

[0227] In some embodiments, the second bearer mapping configuration information may include information about at least one of: an identifier of the second device, an identifier of the P2P connection, an identifier of a radio bearer used on the second access link for the P2P connection, an identifier of a logical channel used on the second access link for the P2P connection, and an identifier of the second access link.

[0228] In some embodiments, example method 700 may further include determining operation of at least one device in the IAB network, wherein the at least one device may include a third device and a fourth device, and may form a routing path for a P2P connection from the first device to the second device bypassing a donor device (e.g., paths 110 and 410 in the above example).

[0229] In some embodiments, the P2P connection may simulate a sidelink connection between the first device and the second device, and may include a sidelink PDCP communication layer and a sidelink SDAP communication layer, which are terminated at the first device and at the second device and transparently relayed through the IAB network, such as Figure 3 and 6 as shown in .

[0230] Figure 8An example apparatus 800 for P2P communication via an IAB network in one embodiment is shown, which may be at least a portion of an IAB donor such as the IAB donor 105 or 405 in the above examples.

[0231] like Figure 8 As shown in , the example apparatus 800 may include at least one processor 801 and at least one memory 802 which may include computer program code 803. The at least one memory 802 and the computer program code 803 may be configured to use the at least one processor 801 to cause the apparatus 800 to at least perform the operations of the example method 700 described above.

[0232] In various embodiments, at least one processor 801 in the example device 800 may include, but is 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, a field programmable gate array (FPGA) and an application specific integrated circuit (ASIC). In addition, at least one processor 801 may also include Figure 8 At least one other circuit or element not shown.

[0233] In various embodiments, at least one memory 802 in the example apparatus 800 may include at least one storage medium in various forms, such as volatile memory and / or non-volatile storage medium. Volatile memory may include, but is not limited to, for example, random access memory (RAM), cache, etc. Non-volatile memory may include, but is not limited to, for example, read-only memory (ROM), hard disk, flash memory, etc. In addition, at least the memory 802 may include, but is not limited to, electrical, magnetic, optical, electromagnetic, infrared or semiconductor systems, devices or equipment, or any combination of the above.

[0234] Additionally, in various embodiments, the example device 800 may further include at least one other circuit, element, and interface, such as at least one I / O interface, at least one antenna element, and the like.

[0235] In various embodiments, the circuits, components, elements, and interfaces in the example device 800 including at least one processor 801 and at least one memory 802 may be coupled together in any suitable manner, such as electrically, magnetically, optically, electromagnetically, etc., via any suitable connection including, but not limited to, buses, crossbar switches, wiring, and / or wireless lines.

[0236] Fig. 9 An example device 900 is shown for P2P communication via an IAB network in one embodiment, which may be at least a portion of an IAB donor such as IAB donor 105 or 405 in the above examples.

[0237] like Fig. 9 As shown in , the example device 900 may include means for performing the operations of the above-described example method 700 in various embodiments. For example, the device 900 may include: means 901 for performing operation 701 of the example method 700, means 902 for performing operation 702 of the example method 700, means 903 for performing operation 703 of the example method 700, and means 904 for performing operation 704 of the example method 700. In one or more other embodiments, the example device 900 may also include at least one I / O interface, at least one antenna element, etc. In some embodiments, examples of means in the device 900 may include circuits. In some embodiments, examples of means may also include software modules and any other suitable functional entities. In some embodiments, the device 900 may include one or more additional means for performing one or more additional operations of the example method 700.

[0238] The term "circuitry" in this disclosure may refer to one or more or all of the following: (a) hardware circuit implementations only (such as implementations only in analog and / or digital circuits); (b) combinations of hardware circuitry and software, such as (i) analog and / or digital hardware circuitry and software / firmware, if applicable, and (ii) hardware processors and software (including digital signal processors), any portion of software and memory, which work together to enable a device such as a mobile phone or server to perform various functions; and (c) hardware circuitry and / or processors, such as microprocessors or portions of microprocessors, which require software (e.g., firmware) to operate, but when software is not required to operate, the software may not be present. This definition of circuitry applies to one or all uses of the term in this disclosure, including in any claims. As a further example, as used in this disclosure, the term circuitry also covers implementations of hardware circuitry or processor (or multiple processors) or portions of hardware circuitry or processors and their (or their) accompanying software and / or firmware. The term circuitry also includes, for example and if applicable to a claim element, a baseband integrated circuit or processor integrated circuit for a mobile device, or a similar integrated circuit in a server, cellular network device, or other computing or network device.

[0239] Fig.10An example method 1000 for P2P communication via an IAB network in one embodiment is shown, which may be performed in a first device that acts as at least a portion of a sending peer device, such as the MT portion 106 of the IAB node 101 when acting as a sending peer device, at least a portion of the MT portion 107 of the IAB node 104 when acting as a sending peer device, at least a portion of the UE 406 when acting as a sending peer device, and at least a portion of the UE 407 when acting as a sending peer device. Fig.10 As shown in , example method 1000 may include operation 1001 and operation 1002 .

[0240] In operation 1001, a first device may receive configuration information (e.g., configuration information 201 when MT portion 106 of IAB node 101 is a sending peer device, configuration information 204 when MT portion 107 of IAB node 104 is a sending peer device, configuration information 501 when UE 406 is a sending peer device, and configuration information 506 when UE 407 is a sending peer device) from a donor device (e.g., P2P connection 108 or 08) in an IAB network for a P2P connection (e.g., P2P connection 108 or 08) between the first device and a second device (e.g., at least a portion of MT portion 106 of IAB node 101 when acting as a receiving peer device, at least a portion of MT portion 107 of IAB node 104 when acting as a receiving peer device, at least a portion of UE 406 when acting as a sending peer device, and at least a portion of UE 407 when acting as a receiving peer device) via the IAB network.

[0241] Then, in operation 1002, based on the configuration information received in operation 1001, the first device sends a message to a third device (e.g., at least a part of the IAB node 102 when the MT part 106 of the IAB node 101 is a sending peer device, at least a part of the IAB node 103 when the MT part 107 of the IAB node 104 is a sending peer device, at least a part of the IAB node 401 when the UE 406 is a sending peer device, and at least a part of the IAB node 407 when the UE 407 is a sending peer device) in the IAB network via an access link (e.g., access link 111 when the MT part 106 of the IAB node 101 is a sending peer device, access link 113 when the MT part 107 of the IAB node 104 is a sending peer device, access link 411 when the UE 406 is a sending peer device, and access link 415 when the UE 407 is a sending peer device). 407 is a data unit for sending a P2P connection when a peer device (at least a part of the IAB node 404 device) sends the data unit.

[0242] In some embodiments, the example method 1000 may also include an operation of sending a request to establish a P2P connection with a second device. For example, the request may include information about at least one of an identifier of the first device, an identifier of the second device, and an identifier of a data stream associated with the data unit.

[0243] In some embodiments, the configuration information received in operation 1001 may include information on at least one of a radio bearer used on an access link for the P2P connection and an identifier of the P2P connection.

[0244] In some embodiments, example method 1000 may further include an operation of determining a radio bearer for sending a data unit over the access link based on the configuration information received in operation 1001 .

[0245] In some embodiments, the P2P connection may simulate a sidelink connection between the first device and the second device, and may include a sidelink PDCP communication layer and a sidelink SDAP communication layer, which are terminated at the first device and at the second device and transparently relayed through the IAB network.

[0246] Fig.11 An example apparatus 1100 for P2P communication via an IAB network in an embodiment is shown, which may be a first device that is at least a portion of a sending peer device, such as the MT portion 106 of the IAB node 101 when acting as a sending peer device, at least a portion of the MT portion 107 of the IAB node 104 when acting as a sending peer device, at least a portion of the UE 406 when acting as a sending peer device, and at least a portion of the UE 407 when acting as a sending peer device.

[0247] As shown in diagram 1100, the example apparatus 1100 may include at least one processor 1101 and at least one memory 1102 which may include computer program code 1103. The at least one memory 1102 and the computer program code 1103 may be configured to utilize the at least one processor 1101 to cause the apparatus 1100 to at least perform the operations of the example method 1000 described above.

[0248] In various embodiments, at least one processor 1101 in the example device 1100 may include, but is not limited to, at least one hardware processor including at least one microprocessor such as a CPU, a portion of at least one software processor, and any other suitable dedicated processor such as a processor developed based on FPGA and ASIC. In addition, at least one processor 1101 may also include Fig.11 At least one other circuit or element not shown.

[0249] In various embodiments, at least one memory 1102 in the example device 1100 may include at least one storage medium in various forms, such as volatile memory and / or non-volatile memory. Volatile memory may include, but is not limited to, for example, RAM, cache, etc. Non-volatile storage may include, but is not limited to, ROM, hard disk, flash memory, etc. In addition, at least the memory 1102 may include, but is not limited to, electrical, magnetic, optical, electromagnetic, infrared or semiconductor systems, devices, or means or any combination of the above.

[0250] Furthermore, in various embodiments, the example device 1100 may further include at least one other circuit, element, and interface, such as at least one I / O interface, at least one antenna element, and the like.

[0251] In various embodiments, the circuits, components, elements, and interfaces in the example device 1100 including at least one processor 1101 and at least one memory 1102 may be coupled together in any suitable manner, such as electrically, magnetically, optically, electromagnetically, etc., via any suitable connection including but not limited to buses, cross switches, wiring, and / or wireless lines.

[0252] Fig.12 An example device 1200 is shown for P2P communication via an IAB network in one embodiment, which can be a first device that is at least a portion of a sending peer device, such as the MT portion 106 of the IAB node 101 when acting as a sending peer device, at least a portion of the MT portion 107 of the IAB node 104 when acting as a sending peer device, at least a portion of the UE 406 when acting as a sending peer device, and at least a portion of the UE 407 when acting as a sending peer device.

[0253] like Fig.12 As shown in , the example device 1200 may include means for performing the operations of the above-described example method 1000 in various embodiments. For example, the device 1200 may include means 1201 for performing the operation 1001 of the example method 1000 and means 1202 for performing the step 1002 of the example method 1000. In one or more other embodiments, the example device 1200 may also include at least one I / O interface, at least one antenna element, etc. In some embodiments, examples of means in the device 1200 may include circuits. In some embodiments, examples of means may also include software modules and any other suitable functional entities. In some embodiments, the device 1200 may include one or more additional means for performing one or more additional operations of the example method 1000.

[0254] Fig.13An example method 1300 for P2P communication via an IAB network in one embodiment is shown, which may be performed in a first device as at least a portion of a receiving peer device, such as the MT portion 106 of the IAB node 101 when charging a receiving peer device, at least a portion of the MT portion 107 of the IAB node 104 when acting as a receiving peer device, at least a portion of the UE 406 when acting as a receiving peer device, and at least a portion of the UE 407 when acting as a receiving peer device. Fig.13 As shown in , example method 1300 may include operation 1301 and operation 1302 .

[0255] In operation 1301, the first device may receive configuration information (e.g., configuration information 201 when the MT part 106 of the IAB node 101 is a receiving peer device, configuration message 204 when the MT part 107 of the IAB node 104 is a receiving peer device, configuration data 501 when the UE 406 is a receiving peer device, and configuration 506 when the UE 407 is a receiving peer device) for a P2P connection (e.g., P2P connection 108 or 408) between the first device and a second device (e.g., at least a portion of the MT part 106 of the IAB node 101 when acting as a sending peer device, at least a portion of the MT part 107 of the IAB node 104 when acting as a sending peer device, at least a portion of the UE 406 when acting as a sending peer device, and at least a portion of the UE 407 when acting as a sending peer device) from a donor device in the IAB network (e.g., example devices 800 and 900 performing example method 700).

[0256] Then, in operation 1302, the first device receives data units of the P2P connection from a third device (e.g., at least a part of the IAB node 102 when the MT part 106 of the IAB node 101 is a receiving peer device, at least a part of the IAB node 103 when the MT part 107 of the IAB node 104 is a receiving peer device, at least a part of the IAB node 401 when the UE 406 is a receiving peer device, and at least a part of the IAB node 404 when the UE 407 is a receiving peer device) serving the first device in the IAB network via an access link (e.g., access link 111 when the MT part 106 of the IAB node 101 is a receiving peer device, access link 113 when the MT part 107 of the IAB node 104 is a receiving peer device, access link 411 when the UE 406 is a receiving peer device, and access link 415 when the UE 407 is a receiving peer device) based on the configuration information received in operation 1301.

[0257] In some embodiments, the configuration information received in operation 1301 may include information on at least one of a radio bearer used on an access link for the P2P connection and an identifier of the P2P connection.

[0258] In some embodiments, example method 1300 may further include an operation of determining a radio bearer for carrying the data unit on the access link based on the configuration information received in operation 1301 .

[0259] In some embodiments, the P2P connection may simulate a sidelink connection between the first device and the second device, and may include a sidelink PDCP communication layer and a sidelink SDAP communication layer, which are terminated at the first device and the second device and transparently relayed through the IAB network.

[0260] Fig.14 An example apparatus 1400 is shown for P2P communication via an IAB network in one embodiment, which can be a first device that is at least a portion of a receiving peer device, such as the MT portion 106 of the IAB node 101 when acting as a receiving peer device; at least a portion of the MT portion 107 of the IAB node 104 when acting as a receiving peer device; at least a portion of the UE 406 when acting as a receiving peer device; and at least a portion of the UE 407 when acting as a receiving peer device.

[0261] like Fig.14 As shown in , the example apparatus 1400 may include at least one processor 1401 and at least one memory 1402 which may include computer program code 1403. The at least one memory 1402 and the computer program code 1403 may be configured to use the at least one processor 1401 to cause the apparatus 1400 to at least perform the operations of the example method 1300 described above.

[0262] In various embodiments, at least one processor 1401 in the example device 1400 may include, but is not limited to, at least one hardware processor, including at least one microprocessor such as a CPU, a portion of at least one software processor, and any other suitable dedicated processor such as a processor developed based on, for example, FPGA and ASIC. In addition, at least one processor 1401 may also include Fig.14 At least one other circuit or element not shown.

[0263] In various embodiments, at least one memory 1402 in the example device 1400 may include at least one storage medium in various forms, such as volatile memory and / or non-volatile memory. Volatile memory may include, but is not limited to, for example, RAM, cache, etc. Non-volatile storage may include, but is not limited to, ROM, hard disk, flash memory, etc. In addition, at least the memory 1402 may include, but is not limited to, an electrical, magnetic, optical, electromagnetic, infrared or semiconductor system, device, or apparatus, or any combination of the above.

[0264] Additionally, in various embodiments, the example device 1400 may further include at least one other circuit, element, and interface, such as at least one I / O interface, at least one antenna element, and the like.

[0265] In various embodiments, the circuits, components, elements, and interfaces in the example device 1400 including at least one processor 1401 and at least one memory 1402 may be coupled together in any suitable manner, such as electrically, magnetically, optically, electromagnetically, etc., via any suitable connection including, but not limited to, buses, crossbar switches, wiring, and / or wireless lines.

[0266] Fig.15 An example device 1500 is shown for P2P communication via an IAB network in one embodiment, which can be a first device that is at least a portion of a receiving peer device, such as the MT portion 106 of the IAB node 101 when acting as a receiving peer device; the MT portion 107 of the IAB node 104 when acting as a receiving peer device; at least a portion of the UE 406 when acting as a receiving peer device; and at least a portion of the UE 407 when acting as a receiving peer device.

[0267] like Fig.15 As shown in , the example device 1500 may include means for performing the operations of the above-described example method 1300 in various embodiments. For example, the device 1500 may include means 1501 for performing the operations 1301 of the example method 1300 and means 1502 for performing the operations 1302 of the example method 1300. In one or more other embodiments, the example device 1500 may also include at least one I / O interface, at least one antenna element, etc. In some embodiments, examples of means in the device 1500 may include circuits. In some embodiments, examples of means may also include software modules and any other suitable functional entities. In some embodiments, the device 1500 may include one or more additional means for performing one or more additional operations of the example method 1300.

[0268] In some embodiments, example methods 1000 and 1300 may be implemented in the same device. For example, at least one memory 1102 and computer program code 1103 in example device 1100 may also be configured to use at least one processor 1101 to cause device 1100 to at least perform the operations of example method 1300 described above. For example, at least one memory 1402 and computer program code 1403 in example device 1400 may also be configured to use at least one processor 1401 to cause device 1400 to at least perform the operations of example method 1000 described above. For example, means 1201 and 1202 in example device 1200 and means 1501 and 1502 in example device 1500 may be configured in the same device that is further configured to perform both example method 1000 and example method 1300.

[0269] Fig.16 An example method 1600 for P2P communication via an IAB network in one embodiment is shown, which may be performed in a first device that is at least part of a sending access IAB node, such as IAB node 102 when MT portion 106 of IAB node 101 acts as a sending peer device; IAB node 103 when MT portion 107 of IAB node 104 acts as a sending peer device; IAB node 401 when UE 406 acts as a sending peer device; and IAB node 404 when UE 407 acts as a sending peer device. Fig.16 As shown in , example method 1600 may include operation 1601 , operation 1602 , and operation 1603 .

[0270] In operation 1601, the first device may receive, from a donor device in the IAB network (e.g., the IAB donor 105 in the IAB donor 405) via the IAB network, a second device (e.g., the MT part 106 of the IAB node 101 as a sending peer device, the MT part 107 of the IAB node 104 as a sending peer device, the UE 406 as a sending peer device, and the UE 407 as a sending peer device) and a third device (e.g., the MT part 106 of the IAB node 101 as a receiving peer device, the MT part 107 of the IAB device 104 as a receiving peer device, the UE 406 as a receiving peer device, and the UE 407 as a receiving peer device) served by the first device. 407) between the P2P connection (e.g., P2P connection 108 or P2P connection 408) (e.g., configuration information 202 when the IAB node 102 is a sending access IAB node, configuration information 203 when the IAB node 103 is a sending access IAB node, configuration information 502 when the IAB node 401 is a sending access IAB node, and configuration information 505 when the IAB node 404 is a sending access IAC node, which may respectively include routing and bearer mapping configuration information for the corresponding IAB nodes).

[0271] Then in operation 1602, the first device may receive data units of the P2P connection from the second device via an access link (e.g., access link 111 when the MT portion 106 of the IAB node 101 is a sending peer device, access link 113 when the MT portion 107 of the IAB node 104 is a sending peer device, access link 411 when the UE 406 is a sending peer device, and access link 415 when the UE 407 is a sending peer device).

[0272] Then, in operation 1603 , the first device may transmit a BAP packet including a BAP header and a data unit based on the configuration information received in operation 1601 , wherein the BAP header may include information associated with the P2P connection.

[0273] In some embodiments, the configuration information received in operation 1601 may include information about at least one of: a routing identifier for routing a data unit to a next-hop device, an identifier of the next-hop device, an identifier of the P2P connection, an identifier of a radio bearer used on an access link for the P2P connection, and an identifier of a logical channel used on the access link for the P2P connection and a logical channel identifier for sending a BAP packet to the next-hop device.

[0274] In some embodiments, the information about the P2P connection included in the BAP header may include at least one of a routing identifier for routing the data unit to a next hop device in the IAB network, an identifier of the P2P connection, an identifier of a radio bearer used on an access link for the P2P connection, and an identifier of the second device. For example, in the case where two peer devices (a second device being a sending peer device, and a third device being a receiving peer device) have a P2P connection via the same access IAB node, the identifier of the second device may be used to separate the connections of the two peer devices.

[0275] In some embodiments, the P2P connection may simulate a side link connection between the second device and the third device, and may include a side link PDCP communication layer and a side link SDAP communication layer, which are terminated at the second device and the third device and transparently relayed through the IAB network, such as Figure 3 and 6 as shown in .

[0276] Fig.17 An example apparatus 1700 for P2P communication via an IAB network in one embodiment is shown, which may be executed in a first device that is at least part of a sending access IAB node, such as, in the above examples, IAB node 102 when MT portion 106 of IAB node 101 acts as a sending peer device, IAB node 401 when UE 406 acts as a sending peer device, and IAB node 404 when UE 407 acts as a sending peer device.

[0277] like Fig.17 As shown in , the example apparatus 1700 may include at least one processor 1701 and at least one memory 1702, and the memory 1702 may include computer program code 1703. The at least one memory 1702 and the computer program code 1703 may be configured to use the at least one processor 1701 to cause the device 1700 to at least perform the operations of the above-mentioned example method 1600.

[0278] In various embodiments, at least one processor 1701 in the example device 1700 may include, but is 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, FPGAs and ASICs. In addition, at least one processor 1701 may also include Fig.17 At least one other circuit or element not shown.

[0279] In various embodiments, at least one memory 1702 in the example device 1700 may include various forms of at least one storage medium, such as volatile memory and / or non-volatile memory. Volatile memory may include, but is not limited to, for example, RAM, cache, etc. Non-volatile storage may include, but is not limited to, ROM, hard disk, flash memory, etc. In addition, at least memory 1702 may include, but is not limited to, electrical, magnetic, optical, electromagnetic, infrared or semiconductor systems, devices, or means, or any combination of the above.

[0280] Additionally, in various embodiments, the example device 1700 may further include at least one other circuit, element, and interface, such as at least one I / O interface, at least one antenna element, and the like.

[0281] In various embodiments, the circuits, components, elements, and interfaces in the example device 1700 including at least one processor 1701 and at least one memory 1702 may be coupled together in any suitable manner, such as electrically, magnetically, optically, electromagnetically, etc., via any suitable connection including but not limited to buses, cross switches, wiring, and / or wireless lines.

[0282] Fig.18 An example device 1800 for P2P communication via an IAB network in one embodiment is shown, which can be a first device that is at least part of a sending access IAB node, such as IAB node 102 in the above examples when MT part 106 of IAB node 101 acts as a sending peer device; IAB node 103 when MT part 107 of IAB node 104 acts as a sending peer device; IAB node 401 when UE 406 acts as a sending peer device; and IAB node 404 when UE 407 acts as a sending peer device.

[0283] like Fig.18 As shown, the example device 1800 may include means for performing the operations of the above-described example method 1600 in various embodiments. For example, the device 1800 may include means 1801 for performing operation 1601 of the example method 1600, means 1802 for performing step 1602 of the example method 1600, and means 1803 for performing step 1803 of the example method 1600. In one or more other embodiments, the example device 1800 may also include at least one I / O interface, at least one antenna element, etc. In some embodiments, examples of means in the device 1800 may include circuits. In some embodiments, examples of means may also include software modules and any other suitable functional entities. In some embodiments, the device 1800 may include one or more additional means for performing one or more additional operations of the example method 1600.

[0284] Fig.19 An example method 1900 for P2P communication via an IAB network in one embodiment is shown, which may be performed in a first device as at least part of a receiving access IAB node, such as, in the above example, IAB node 102 when MT portion 106 of IAB node 101 acts as a receiving peer device, IAB node 103 when MT portion 107 of IAB node 104 acts as a receiving peer device, IAB node 401 when UE 406 acts as a receiving peer device, and IAB node 404 when UE 407 acts as a receiving peer device. Fig.19 As shown in , example method 1900 may include operation 1901 , operation 1902 , and operation 1903 .

[0285] In operation 1901, the first device may receive, from a donor device of the IAB network (e.g., the IAB donor 105 and the IAB donor 405) via the IAB network, a message for a second device (e.g., the MT part 106 of the IAB node 101 as a sending peer device, the MT part 107 of the IAB device 104 as a sending peer device, the UE 406 as a sending peer device, and the UE 407 as a sending peer device) and a third device served by the first device (e.g., the MT part 106 of the IAB node 101 as a receiving peer device, the MT part 107 of the IAB device 104 as a receiving peer device, the UE 406 as a receiving peer device, and the UE 407 as a receiving peer device). 407) (for example, configuration information of a P2P connection (for example, P2P connection 108 or P2P connection 408) between IAB node 102 and IAB node 103 (for example, configuration information 202 when IAB node 102 is a receiving access IAB node, configuration information 203 when IAB node 103 is a receiving access IAB node, configuration information 502 when IAB node 401 is a receiving access IAB node, and configuration information 505 when IAB node 404 is a receiving access access IAB node, which may respectively include bearer mapping configuration information of the corresponding IAB node).

[0286] Then, in operation 1902, the first device may receive a BAP packet including a BAP header and a data unit of the P2P connection, wherein the BAP packet may include information associated with the P2P connection.

[0287] Then in operation 1903, the first device may send a data unit to a third device via a first access link (e.g., access link 111 when the MT part 106 of the IAB node 101 is a receiving peer device, access link 113 when the MT part 107 of the IAB node 104 is a receiving peer device, access link 411 when the UE 406 is a receiving peer device, and access link 415 when the UE 407 is a receiving peer device) based on the configuration information and the BAP header received in operation 1901.

[0288] In some embodiments, the configuration information received in operation 1901 may include information about at least one of an identifier of a third device, an identifier of a P2P connection, an identifier of a radio bearer used on a first access link for the P2P connection, an identifier of a logical channel used on the first access link for the P2P connection, and an identifier of the first access link.

[0289] In some embodiments, the information about the P2P connection included in the BAP header may include at least one of the following: an identifier of the P2P connection; a second access link (e.g., access link 111 when the MT part 106 of the IAB node 101 is a sending peer device, access link 113 when the MT part 107 of the IAB node 104 is a sending peer device, access link 411 when the UE 406 is a sending peer device, and access link 412 when the UE 407 is a sending peer device) between the second device and a fourth device serving the second device in the integrated access and backhaul network for the P2P connection (e.g., IAB node 102 when the MT part 106 of the IAB node 101 acts as a sending peer device, IAB node 103 when the MT part 107 of the IAB node 104 acts as a sending peer device, IAB node 401 when the UE 406 acts as a sending peer device, and IAB node 404 when the UE 407 acts as a sending peer device); 407 is the identifier of the radio bearer used when sending the access link 415 of the peer device; the identifier of the second access link; and the identifier of the second device. Fig.19 In an embodiment, in which the second device acts as a sending peer device and the third device acts as a receiving peer device) have a P2P connection via the same access IAB node, the identifier of the second device may be used to separate the connections of the two peer devices.

[0290] In some embodiments, the P2P connection may simulate a sidelink connection between the second device and the third device, and may include a sidelink PDCP communication layer and a sidelink SDAP communication layer, which are terminated at the second device and the third device and transparently relayed through the IAB network.

[0291] Fig. 20An example apparatus 2000 is shown for P2P communication via an IAB network in one embodiment, which may be executed in a first device that is at least part of a receiving access IAB node, such as IAB node 102 when MT portion 106 of IAB node 101 acts as a receiving peer device, IAB node 103 when MT portion 107 of IAB node 104 acts as a receiving peer device, IAB node 401 when UE 406 acts as a receiving peer device, and IAB node 404 when UE 407 acts as a receiving peer device in the above examples.

[0292] like Fig. 20 As shown in , the example apparatus 2000 may include at least one processor 2001 and at least one memory 2002 which may include computer program code 2003. The at least one memory 2002 and the computer program code 2003 may be configured to use the at least one processor 2001 to cause the device 2000 to at least perform the operations of the example method 1900 described above.

[0293] In various embodiments, at least one processor 2001 in the example device 2000 may include, but is not limited to, at least one hardware processor including at least one microprocessor such as a CPU, a portion of at least one software processor, and any other suitable dedicated processor such as a processor developed based on, for example, FPGA and ASIC. In addition, at least one processor 2001 may also include Fig.19 At least one other circuit or element not shown.

[0294] In various embodiments, at least one memory 2002 in the example apparatus 2000 may include at least one storage medium in various forms, such as volatile memory and / or non-volatile memory. Volatile memory may include, but is not limited to, for example, RAM, cache, etc. Non-volatile storage may include, but is not limited to, ROM, hard disk, flash memory, etc. In addition, at least the memory 2002 may include, but is not limited to, electrical, magnetic, optical, electromagnetic, infrared or semiconductor systems, devices, or means or any combination of the above.

[0295] Furthermore, in various embodiments, the example apparatus 2000 may further include at least one other circuit, element, and interface, such as at least one I / O interface, at least one antenna element, and the like.

[0296] In various embodiments, circuits, components, elements, and interfaces in an example device 2000 including at least one processor 2001 and at least one memory 2002 are coupled together in any suitable manner, such as electrically, magnetically, optically, electromagnetically, etc., via any suitable connection including but not limited to buses, crossbars, wiring, and / or wireless lines.

[0297] Fig.21 An example device 2100 for P2P communication via an IAB network in one embodiment is shown, and the method can be performed in a first device that is at least part of a receiving access IAB node, such as the MT part 106 of the IAB node 101 acting as the IAB node 102 when the receiving peer device, the MT part 107 of the IAB node 104 acting as the IAB node 103 when the receiving peer device, the UE 406 acting as the IAB node 401 when the receiving peer device, and the UE 407 acting as the IAB node 404 when the receiving peer device.

[0298] like Fig.21 As shown in , the example device 2100 may include means for performing the operations of the above-described example method 1900 in various embodiments. For example, the device 2100 may include means 2101 for performing operation 1901 of the example method 1900, means 2102 for performing step 1902 of the example method 1900, and means 2103 for performing step 1903 of the example method 1900. In one or more other embodiments, the example device 2100 may also include at least one I / O interface, at least one antenna element, etc. In some embodiments, examples of means in the device 2100 may include circuits. In some embodiments, examples of means may also include software modules and any other suitable functional entities. In some embodiments, the device 2100 may include one or more additional means for performing one or more additional operations of the example method 1900.

[0299] In some embodiments, example methods 1600 and 1900 may be implemented in the same apparatus. For example, at least one memory 1702 and computer program code 1703 in example apparatus 1700 may also be configured to use at least one processor 1701 to cause apparatus 1700 to at least perform the operations of example method 1900 described above. For example, at least one memory 2002 and computer program code 2003 in example apparatus 2000 may also be configured to use at least one processor 2001 to cause apparatus 2000 to at least perform the operations of example method 1600 described above. For example, the apparatus in example device 1800 and the apparatus in example device 2100 may be configured in the same apparatus that is further configured to perform both example method 1600 and example method 1900.

[0300] Another example embodiment may involve computer program code or instructions that cause a device to perform at least each of the above methods. Another example embodiment may involve a computer readable medium having such computer program code or instructions stored thereon. In some embodiments, such a computer readable medium may include at least one storage medium in various forms, such as volatile memory and / or non-volatile memory. Volatile memory may include, but is not limited to, for example, RAM, cache, etc. Non-volatile storage may include, but is not limited to, electrical, magnetic, optical, electromagnetic, infrared or semiconductor systems, devices or apparatuses, or any combination of the above.

[0301] Unless the context clearly requires otherwise, throughout the specification and claims, the words "include", "including", etc. should be interpreted as inclusive, not exclusive or exhaustive; that is, in the sense of "including but not limited to", as generally used herein, the word "coupled" refers to two or more elements that can be directly connected, or can be connected through one or more intermediate elements. Similarly, as generally used herein, the word "connected" refers to two or more elements that can be directly connected, or can be connected through one or more intermediate elements. In addition, the words "herein", "above", "below" and words of similar meaning used in this application shall refer to the entirety of this application, not to any particular part of this application. Where the context permits, words used in the singular or plural in the specification may also include the plural or singular, respectively. The word "or" refers to a list of two or more items, and the word covers all of the following interpretations of the word: any item in the list, all items in the list, and any combination of items in the list.

[0302] Furthermore, conditional language used herein, such as "may," "might," "could," "for example," "such as," and the like, unless otherwise specifically stated or understood otherwise in the context of use, is generally intended to convey that some embodiments include, while other embodiments do not include, certain features, elements, and / or states. Thus, such conditional language is generally not intended to imply that one or more embodiments require features, elements, and / or states in any way, or that one or more embodiments must include logic for deciding, with or without author input or prompting, whether such features, elements, or states are included or will be performed in any particular embodiment.

[0303] Although some embodiments have been described, these embodiments are presented by way of example and are not intended to limit the scope of the present disclosure. In fact, the devices, methods, and systems described herein may be embodied in various other forms; in addition, various omissions, substitutions, and changes may be made to the forms of the methods and systems described herein without departing from the spirit of the present disclosure. For example, when blocks are presented in a given arrangement, alternative embodiments may use different components and / or circuit topologies to perform similar functions, and may delete, move, add, subdivide, combine, and / or modify some blocks. At least one of these blocks may be implemented in various different ways. The order of these blocks may also be changed. Any suitable combination of the elements and actions of some of the above-described embodiments may be combined to provide further embodiments. The attached claims and their equivalents are intended to cover forms or modifications that fall within the scope and spirit of the present disclosure.

Claims

1. A device for communication, comprising: at least one processor; as well as at least one memory comprising 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 device to: receiving, via an integrated access and backhaul network, configuration information for a peer-to-peer connection between the first device and a second device from a donor device in the integrated access and backhaul network, and Based on the configuration information, sending data units of the peer connection to a third device serving the first device in the integrated access and backhaul network via an access link; Wherein, the peer connection simulates a side link connection between the first device and the second device, and includes a side link packet data convergence protocol communication layer and a side link service data adaptation protocol communication layer, which are terminated at the first device and the second device and transparently relayed through the integrated access and backhaul network.

2. The device according to 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: A request for establishing the peer-to-peer connection with the second device is sent, the request comprising information about at least one of an identifier of the first device, an identifier of the second device, and an identifier of a data flow associated with the data unit.

3. The device according to claim 1 or 2, wherein: The configuration information comprises information about at least one of a radio bearer used on the access link for the peer connection and an identifier of the peer connection.

4. The device as claimed in claim 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: A radio bearer for sending the data unit on the access link is determined based on the configuration information.

5. The device according to any one of claims 1, 2, or 4, wherein: The first device is a user equipment or a mobile terminal part of an integrated access and backhaul network node device in the integrated access and backhaul network.

6. A device for communication, comprising: at least one processor; as well as 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 device in an integrated access and backhaul network to: receiving, via an integrated access and backhaul network, routing and bearer mapping configuration information for a peer-to-peer connection between a second device served by the first device and a third device from a donor device in the integrated access and backhaul network, receiving data units of the peer-to-peer connection from the second device via an access link, and sending 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 including information associated with the peer connection; Wherein, the peer connection simulates a side link connection between the second device and the third device, and includes a side link packet data convergence protocol communication layer and a side link service data adaptation protocol communication layer, which are terminated at the second device and the third device and transparently relayed through the integrated access and backhaul network.

7. The device according to claim 6, wherein: The routing and bearer mapping configuration information includes information about at least one of: a routing identifier for routing the data unit to a next hop device, an identifier of the next hop device, an identifier of the peer connection, an identifier of a radio bearer used on the access link for the peer connection, an identifier of a logical channel used on the access link for the peer connection, and an identifier of a logical channel for sending a backhaul adaptation protocol packet to the next hop device.

8. The device according to claim 6 or 7, wherein: The information associated with the peer connection includes at least one of a routing identifier for routing the data unit to a next hop device in the integrated access and backhaul network, an identifier of the peer connection, an identifier of a radio bearer used on the access link for the peer connection, and an identifier of the second device.

9. An apparatus for communication, comprising: at least one processor; as well as at least one memory comprising 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 device to: receiving, via an integrated access and backhaul network, configuration information for a peer-to-peer connection between the first device and a second device from a donor device in the integrated access and backhaul network, and receiving, based on the configuration information, data units of the peer connection from a third device serving the first device in the integrated access and backhaul network via an access link; Wherein, the peer connection simulates a side link connection between the first device and the second device, and includes a side link packet data convergence protocol communication layer and a side link service data adaptation protocol communication layer, which are terminated at the first device and the second device and transparently relayed through the integrated access and backhaul network.

10. The device of claim 9, wherein: The configuration information comprises information about at least one of a radio bearer used on the access link for the peer connection and an identifier of the peer connection.

11. The device according to claim 9 or 10, 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: A radio bearer for carrying the data unit on the access link is determined based on the configuration information.

12. The device according to any one of claims 9 to 10, wherein: The first device is a user equipment or a mobile terminal part of an integrated access and backhaul network node device in the integrated access and backhaul network.

13. An apparatus for communication, comprising: at least one processor; as well as 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 device in an integrated access and backhaul network to: receiving, via an integrated access and backhaul network, from a donor device in the integrated access and backhaul network, bearer mapping configuration information for a peer connection between a second device and a third device served by the first device, receiving a backhaul adaptation protocol packet including a backhaul adaptation protocol header and a data unit of the peer connection, the backhaul adaptation protocol packet including information associated with the peer connection, and Sending the data unit to the third device via the first access link based on the bearer mapping configuration information and the backhaul adaptation protocol header; Wherein, the peer connection simulates a side link connection between the second device and the third device, and includes a side link packet data convergence protocol communication layer and a side link service data adaptation protocol communication layer, which are terminated at the second device and the third device and transparently relayed through the integrated access and backhaul network.

14. The device of claim 13, wherein: The bearer mapping configuration information includes information about at least one of: an identifier of the third device, an identifier of the peer connection, an identifier of a radio bearer used on the first access link for the peer connection, an identifier of a logical channel on the first access link for the peer connection, and an identifier of the first access link.

15. The device according to claim 13 or 14, wherein: The information associated with the peer connection includes at least one of: an identifier of the peer connection, an identifier of a radio bearer used on a second access link between a second device in the integrated access and backhaul network used for the peer connection and a fourth device serving the second device, an identifier of the second access link, and an identifier of the second device.

16. An apparatus for communication, comprising: at least one processor; as well as 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 device in an integrated access and backhaul network to: sending first configuration information for a peer-to-peer connection between the first device and a second device to a first device via the integrated access and backhaul network, so that the first device can send data units of the peer-to-peer connection to a third device serving the first device in the integrated access and backhaul network via a first access link, sending second configuration information for the peer connection to the second device so that the second device can receive the data unit from a fourth device serving the second device in the integrated access and backhaul network via a second access link, sending first routing and bearer mapping configuration information for the peer connection to the third device, and Sending second bearer mapping configuration information for the peer connection to the fourth device; Wherein, the peer connection simulates a side link connection between the first device and the second device, and includes a side link packet data convergence protocol communication layer and a side link service data adaptation protocol communication layer, which are terminated at the first device and the second device and transparently relayed through the integrated access and backhaul network.

17. The device of claim 16, 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: A request is received from the first device to establish a peer connection with the second device, the request comprising information about at least one of an identifier of the first device, an identifier of the second device, and an identifier of a data flow associated with the data unit.

18. The device according to claim 16 or 17, wherein: The first configuration information includes information about at least one of a radio bearer used on the first access link for the peer connection and an identifier of the peer connection.

19. The device of claim 18, wherein: The second configuration information includes information about at least one of a radio bearer used on the second access link for the peer connection and an identifier of the peer connection.

20. The device of any one of claims 16, 17, or 19, wherein: The first routing and bearer mapping configuration information includes information about at least one of the following: a routing identifier for routing the data unit to a next-hop device in the integrated access and backhaul network, an identifier of the next-hop device, an identifier of a peer connection, an identifier of a radio bearer used on the first access link for the peer connection, an identifier of a logical channel used on the first access link for the peer connection, and a logical channel identifier for sending a backhaul adaptation protocol packet carrying the data unit to the next-hop device.

21. The device of any one of claims 16, 17, or 19, wherein: The second bearer mapping configuration information includes information about at least one of: an identifier of the second device, an identifier of the peer connection, an identifier of a radio bearer used on the second access link for the peer connection, an identifier used on a logical channel for the peer connection, and an identifier of the second access link.

22. The device of any one of claims 16, 17, or 19, 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: At least one device in the integrated access and backhaul network is determined, the at least one device comprising the third device and the fourth device, and a routing path for the peer-to-peer connection from the first device to the second device is formed bypassing the donor device.

23. A method for communication, comprising: receiving, at a first device, configuration information for a peer-to-peer connection between the first device and a second device from a donor device in the integrated access and backhaul network, via the integrated access and backhaul network, and Based on the configuration information, sending, at the first device, via an access link, a data unit of the peer connection to a third device serving the first device in the integrated access and backhaul network; Wherein, the peer connection simulates a side link connection between the first device and the second device and includes a side link packet data convergence protocol communication layer and a side link service data adaptation protocol communication layer, which are terminated at the first device and the second device and transparently relayed through the integrated access and backhaul network.

24. The method of claim 23, further comprising: A request for establishing a peer-to-peer connection with the second device is sent, the request comprising information about at least one of an identifier of the first device, an identifier of the second device, and an identifier of a data flow associated with the data unit.

25. The method of claim 23 or 24, wherein: The configuration information comprises information about at least one of a radio bearer used on the access link for the peer connection and an identifier of the peer connection.

26. The method of claim 25, further comprising: A radio bearer for sending the data unit on the access link is determined based on the configuration information.

27. The method of any one of claims 23, 24, or 26, wherein: The first device is a user equipment or a mobile terminal part of an integrated access and backhaul network node device in the integrated access and backhaul network.

28. A method for communication, comprising: receiving, at a first device in the integrated access and backhaul network, routing and bearer mapping configuration information for a peer-to-peer connection between a second device served by the first device and a third device from a donor device in the integrated access and backhaul network via an integrated access and backhaul network, receiving, at the first device, a data unit of the peer-to-peer connection from the second device via an access link, and At the first device, sending 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 including information associated with the peer connection; Wherein, the peer connection simulates a side link connection between the second device and the third device and includes a side link packet data convergence protocol communication layer and a side link service data adaptation protocol communication layer, which are terminated at the second device and the third device and transparently relayed through the integrated access and backhaul network.

29. The method of claim 28, wherein: The routing and bearer mapping configuration information includes information about at least one of: a routing identifier for routing the data unit to a next hop device, an identifier of the next hop device, an identifier of the peer connection, an identifier of a radio bearer used on the access link for the peer connection, an identifier of a logical channel used on the access link for the peer connection, and a logical channel identifier for sending the backhaul adaptation protocol packet to the next hop device.

30. The method of claim 28 or 29, wherein: The information associated with the peer connection includes at least one of: a routing identifier for routing the data unit to a next hop device in the integrated access and backhaul network, an identifier of the peer connection, an identifier of a radio bearer used on the access link for the peer connection, and an identifier of the second device.

31. A method for communication, comprising: receiving, at a first device via an integrated access and backhaul network, configuration information for a peer-to-peer connection between the first device and a second device from a donor device in the integrated access and backhaul network, and receiving, at the first device, via an access link, a data unit of the peer-to-peer connection from a third device serving the first device in the integrated access and backhaul network based on the configuration information; Wherein, the peer connection simulates a side link connection between the first device and the second device, and includes a side link packet data convergence protocol communication layer and a side link service data adaptation protocol communication layer, which are terminated at the first device and the second device and transparently relayed through the integrated access and backhaul network.

32. The method of claim 31, wherein: The configuration information comprises information about at least one of a radio bearer used on the access link for the peer connection and an identifier of the peer connection.

33. The method of claim 31 or 32, further comprising: At the first device, a radio bearer for carrying the data unit on the access link is determined based on the configuration information.

34. The method of claim 31 or 32, wherein: The first device is a user equipment or a mobile terminal part of an integrated access and backhaul network node device in the integrated access and backhaul network.

35. A method for communication, comprising: receiving, via an integrated access and backhaul network, bearer mapping configuration information for a peer-to-peer connection between a second device and a third device served by the first device from a donor device in the integrated access and backhaul network, receiving, at the first device, a backhaul adaptation protocol packet including a backhaul adaptation protocol header and a data unit of the peer connection, the backhaul adaptation protocol packet including information associated with the peer connection, and At the first device, based on the bearer mapping configuration information and the backhaul adaptation protocol header, sending the data unit to the third device via a first access link; Wherein, the peer connection simulates a side link connection between the second device and the third device, and includes a side link packet data convergence protocol communication layer and a side link service data adaptation protocol communication layer, which are terminated at the second device and the second device, and are transparently relayed through the integrated access and backhaul network.

36. The method of claim 35, wherein: The bearer mapping configuration information includes information about at least one of: an identifier of the third device, an identifier of the peer connection, an identifier of a radio bearer used on the first access link for the peer connection, an identifier of a logical channel used on the first access link for the peer connection, and an identifier of the first access link.

37. The method of claim 35 or 36, wherein: The information associated with the peer connection includes at least one of: an identifier of the peer connection, an identifier of a radio bearer used on a second access link between the second device and a fourth device serving the second device in the integrated access and backhaul network used for the peer connection, an identifier of the second access link, and an identifier of the second device.

38. A method for communication, comprising: sending, at a donor device in an integrated access and backhaul network, first configuration information for a peer-to-peer connection between the first device and a second device to a first device via the integrated access and backhaul network, so that the first device can send data units of the peer-to-peer connection to a third device serving the first device in the integrated access and backhaul network via a first access link, sending, at the donor device, second configuration information for the peer connection to the second device to enable the second device to receive the data unit from a fourth device serving the second device in the integrated access and backhaul network via a second access link, sending, at the donor device, first routing and bearer mapping configuration information for the peer connection to the third device, and Sending, at the donor device, second bearer mapping configuration information for the peer connection to the fourth device; Wherein, the peer connection simulates a side link connection between the first device and the second device and includes a side link packet data convergence protocol communication layer and a side link service data adaptation protocol communication layer, which are terminated at the first device and the second device and are transparently relayed through the integrated access and backhaul network.

39. The method of claim 38, further comprising: At the donor device, a request is received from the first device to establish the peer connection with the second device, the request comprising information about at least one of an identifier of the first device, an identifier of the second device, and an identifier of a data stream associated with the data unit.

40. The method of claim 38 or 39, wherein: The first configuration information includes information about at least one of a radio bearer used on the first access link for the peer connection and an identifier of the peer connection.

41. The method of claim 40, wherein: The second configuration information comprises at least one of information on at least one of: a radio bearer used on the second access link for the peer connection and an identifier of the peer connection.

42. The method of any one of claims 38, 39, or 41, wherein: The first routing and bearer mapping configuration information includes information about at least one of: a routing identifier for routing the data unit to a next-hop device in the integrated access and backhaul network, an identifier of the next-hop device, an identifier of the peer connection, an identifier of a radio bearer used on the first access link for the peer connection, an identifier of a logical channel used on the first access link for the peer connection, and a logical channel identifier for sending a backhaul adaptation protocol packet carrying the data unit to the next-hop device.

43. The method of any one of claims 38, 39, or 41, wherein: The second bearer mapping configuration information includes information about at least one of: an identifier of the second device, an identifier of the peer connection, an identifier of a radio bearer used on the second access link for the peer connection, an identifier of a logical channel used on the second access link for the peer connection, and an identifier of the second access link.

44. The method of any one of claims 38, 39, or 41, further comprising: At the donor device, at least one device in the integrated access and backhaul network is determined, the at least one device comprising the third device and the fourth device, and a routing path for the peer connection from the first device to the second device bypassing the donor device is formed.

45. A computer-readable medium comprising instructions stored thereon, the instructions being configured to cause a device as a first device to: receiving, via the integrated access and backhaul network, configuration information for a peer-to-peer connection between the first device and the second device from a donor device in the integrated access and backhaul network, and Based on the configuration information, sending the data unit of the peer connection to a third device serving the first device in the integrated access and backhaul network via an access link; in, The peer connection simulates a sidelink connection between the first device and the second device, and includes a sidelink packet data convergence protocol communication layer and a sidelink service data adaptation protocol communication layer, which are terminated at the first device and the second device and transparently relayed through the integrated access and backhaul network.

46. ​​The computer readable medium of claim 45, wherein: The instructions further cause the device to: A request for establishing the peer-to-peer connection with the second device is sent, the request comprising information about at least one of an identifier of the first device, an identifier of the third device, and an identifier of a data flow associated with the data unit.

47. The computer readable medium of claim 45 or 46, wherein: The configuration information comprises information about at least one of a radio bearer used on the access link for the peer connection and an identifier of the peer connection.

48. The computer readable medium of any one of claims 45 to 46, wherein the instructions further cause the device to: A radio bearer for sending the data unit on the access link is determined based on the configuration information.

49. The computer readable medium of any one of claims 45 to 46, wherein: The first device is a user equipment or a mobile terminal part of an integrated access and backhaul network node device in the integrated access and backhaul network.

50. A computer-readable medium comprising instructions stored thereon for causing a device as a first device in an integrated access and backhaul network to: receiving, via the integrated access and backhaul network, routing and bearer mapping configuration information for a peer-to-peer connection between a second device served by the first device and a third device from a donor device in the integrated access and backhaul network, receiving data units of the peer-to-peer connection from the second device via an access link, and sending 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 including information associated with the peer connection; in, The peer connection simulates a side link connection between the second device and the third device, and includes a side link packet data convergence protocol communication layer and a side link service data adaptation protocol communication layer, which are terminated at the second device and the second device and are transparently relayed through the integrated access and backhaul network.

51. The computer readable medium of claim 50, wherein: The routing and bearer mapping configuration information includes information about at least one of: a routing identifier for routing the data unit to a next hop device, an identifier of the next hop device, an identifier of the peer connection, an identifier of a radio bearer used on the access link for the peer connection, an identifier of a logical channel used on the access link for the peer connection, and an identifier of a logical channel for sending the backhaul adaptation protocol packet to the next hop device.

52. The computer readable medium of claim 50 or 51, wherein: The information associated with the peer connection includes at least one of: a routing identifier for routing the data unit to a next hop device in the integrated access and backhaul network, an identifier of the peer connection, an identifier of a radio bearer used on the access link for the peer connection, and an identifier of the second device.

53. A computer-readable medium comprising instructions stored thereon, the instructions for causing a device as a first device to: receiving, via an integrated access and backhaul network, configuration information for a peer-to-peer connection between the first device and a second device from a donor device in the integrated access and backhaul network, and receiving, based on the configuration information, data units of the peer connection via an access link and from a third device serving the first device in the integrated access and backhaul network; in, The peer connection simulates a sidelink connection between the first device and the second device and includes a sidelink packet data convergence protocol communication layer and a sidelink service data adaptation protocol communication layer, which are terminated at the first device and the second device and transparently relayed through the integrated access and backhaul network.

54. The computer readable medium of claim 53, wherein: The configuration information comprises information about at least one of a radio bearer used on the access link for the peer connection and an identifier of the peer connection.

55. The computer readable medium of claim 53 or 54, wherein: The instructions further cause the device to: A radio bearer for carrying the data unit on the access link is determined based on the configuration information.

56. The computer readable medium of claim 53 or 54, wherein: The first device is a user equipment or a mobile terminal part of an integrated access and backhaul network node device in an integrated access and backhaul network.

57. A computer readable medium comprising instructions stored thereon for causing a device as a first device in an integrated access and backhaul network to: receiving, via an integrated access and backhaul network, bearer mapping configuration information for a peer-to-peer connection between a second device and a third device served by the first device from a donor device in the integrated access and backhaul network, receiving a backhaul adaptation protocol packet including a backhaul adaptation protocol header and a data unit of the peer connection, the backhaul adaptation protocol packet including information associated with the peer connection, and Sending the data unit to the third device via the first access link based on the bearer mapping configuration information and the backhaul adaptation protocol header; in, The peer connection simulates a side link connection between the second device and the third device, and includes a side link packet data convergence protocol communication layer and a side link service data adaptation protocol communication layer, which are terminated at the second device and the second device and are transparently relayed through the integrated access and backhaul network.

58. The computer readable medium of claim 57, wherein: The bearer mapping configuration information includes information about at least one of: an identifier of the third device, an identifier of the peer connection, an identifier of a radio bearer used on the first access link for the peer connection, an identifier of a logical channel used on the first access link for the peer connection, and an identifier of the first access link.

59. The computer readable medium of claim 57 or 58, wherein: The information associated with the peer connection includes at least one of: an identifier of the peer connection, an identifier of a radio bearer for the peer connection used on a second access link between the second device and a fourth device serving the second device in the integrated access and backhaul network, an identifier of the second access link, and an identifier of the second device.

60. A computer readable medium comprising instructions stored thereon for causing an apparatus as a donor device in an integrated access and backhaul network to: sending first configuration information for a peer-to-peer connection between the first device and a second device to a first device via an integrated access and backhaul network, so that the first device can send data units of the peer-to-peer connection to a third device serving the first device in the integrated access and backhaul network via a first access link, sending second configuration information for the peer connection to the second device so that the second device can receive the data unit from a fourth device serving the second device in the integrated access and backhaul network via a second access link, sending first routing and bearer mapping configuration information for the peer connection to the third device, and Sending second bearer mapping configuration information for the peer connection to the fourth device; in, The peer connection simulates a sidelink connection between the first device and the second device and includes a sidelink packet data convergence protocol communication layer and a sidelink service data adaptation protocol communication layer, which are terminated at the first device and the second device and are transparently relayed through the integrated access and backhaul network.

61. The computer readable medium of claim 60, wherein: The instructions further cause the device to: A request is received from the first device to establish a peer connection with the second device, the request comprising information about at least one of an identifier of the first device, an identifier of the second device, and an identifier of a data flow associated with the data unit.

62. The computer readable medium of claim 60 or 61, wherein: The first configuration information includes information about at least one of a radio bearer used on the first access link for the peer connection and an identifier of the peer connection.

63. The computer readable medium of claim 62, wherein: The second configuration information comprises at least one of information on at least one of: a radio bearer used on the second access link for a peer connection and an identifier of the peer connection.

64. The computer readable medium of any one of claims 60, 61, or 63, wherein: The first routing and bearer mapping configuration information includes information about at least one of: a routing identifier for routing the data unit to a next-hop device in the integrated access and backhaul network, an identifier of the next-hop device, an identifier of the peer connection, an identifier of a radio bearer used on the first access link for the peer connection, an identifier of a logical channel used on the first access link for the peer connection, and a logical channel identifier for sending a backhaul adaptation protocol packet carrying the data unit to the next-hop device.

65. The computer readable medium of any one of claims 60, 61, or 63, wherein: The second bearer mapping configuration information includes information about at least one of: an identifier of the second device, an identifier of the peer connection, an identifier of a radio bearer used on the second access link for the peer connection, an identifier of a logical channel used on the second access link for the peer connection, and an identifier of the second access link.

66. The computer readable medium of any one of claims 60, 61, or 63, wherein: The instructions further cause the device to: At least one device in the integrated access and backhaul network is determined, the at least one device comprising the third device and the fourth device, and a routing path for a peer connection from the first device to the second device is formed that bypasses the donor device.

Images