KR20200110690A - Control plane signaling for unified access and backhaul nodes - Google Patents

Abstract

As network signaling improves, various communication systems will benefit. For example, some embodiments may benefit from improved connectivity between a relay node and a network entity. The method may include receiving a user equipment portion of aggregated access and backhaul node downlink information from a donor node. The downlink information may include F1 application protocol information. The method may also include transmitting downlink information comprising F1 application protocol information from the user equipment portion of the aggregated access and backhaul node to the radio access network portion of the aggregated access and backhaul node.

Description

Control plane signaling for unified access and backhaul nodes

Cross-references to related applications:

This application claims priority to U.S. Provisional Patent Application No. 62/619,479, filed on January 19, 2018. The entire contents of this application are incorporated herein by reference.

Field:

As network signaling improves, various communication systems will benefit. For example, some embodiments may benefit from improved connectivity between a relay node and a network entity.

3GPP (Third Generation Partnership Project) NR (New Radio) or 5G (5th Generation) technology includes a function that allows minimal manual work to be performed when a network is constructed using NR or 5G technology. For example, automated self-configuration is provided as a function. When using the high-frequency band, NR or 5G technology can easily extend coverage in a fast and cost-effective manner by minimizing or requiring no network planning or re-planning. To facilitate this, a wireless backhaul is used to connect relay nodes, also referred to as Integrated Access and Backhaul (IAB) nodes, to each other and also to a base station having a fixed connection.

As described above, a relay node (RN) or an IAB node is included as part of a communication system using NR or 5G technology. One or more RN or IAB nodes are connected to each other. The RN or IAB node has a wireless backhaul connection instead of a wired connection, which connects the RN or IAB node to a donor 5G or NR NodeB (DgNB) or other IAB node. DgNB is a base station fixedly connected to the network backhaul. The serving DgNB controls the use of radio resources in the communication system, and considers both access and backhaul links as part of radio resource allocation.

One embodiment may include receiving downlink information including at least F1 application protocol information from a donor node, in the user equipment portion of an integrated access and backhaul node. It's about how. The method also includes transmitting downlink information comprising at least the F1 application protocol information from the user equipment portion of the aggregated access and backhaul node to the radio access network portion of the aggregated access and backhaul node.

Another embodiment relates to an apparatus that may include at least one processor and at least one memory including computer program code. The at least one memory and the computer program code cause the device to receive, by at least one processor, downlink information including at least F1 application protocol information from a donor node, at least in the user equipment portion of the integrated access and backhaul node. Is configured to do. The apparatus is further configured to transmit downlink information including at least the F1 application protocol information from the user equipment portion of the aggregated access and backhaul node to the radio access network portion of the aggregated access and backhaul node.

In one embodiment, the donor node may comprise a donor node central unit for downlink information. In another embodiment, the downlink information may be aggregated with other data on the backhaul link. According to another embodiment, a signaling radio bearer may be carried over a backhaul link, and downlink information in the user equipment portion of the unified access and backhaul node may be received through the signaling radio bearer.

In another embodiment, the downlink information may be received as a radio resource control message or signal at the user equipment portion of the aggregated access and backhaul node. According to an embodiment, the signaling radio bearer may include an identifier, and the identifier may be a logical channel identifier. In one embodiment, the method indicates that the received downlink information should be transmitted to the radio access network portion of the aggregated access and backhaul node based on the identifier in the radio resource control message or the logical channel identifier used for the signaling radio bearer. It may include the step of identifying.

According to one embodiment, the downlink information conveyed from the user equipment portion of the aggregated access and backhaul node to the wireless network portion of the aggregated access and backhaul node updates the configuration of the radio access network portion of the aggregated access and backhaul node. In one embodiment, the backhaul link may be used when the aggregated access and backhaul node is in a radio link control grant mode. According to an embodiment, the backhaul link may include at least one of a radio link control layer, a medium access control layer, and an adaptation layer.

In yet another embodiment, the donor node central unit may include an internal user plane function. In another embodiment, a signal of at least one service of a non-access layer service or a protocol data unit service may be transmitted through the integrated access and backhaul node. According to one embodiment, the signaling radio bearer may be terminated in the user equipment portion of the aggregated access and backhaul node.

Another embodiment relates to an apparatus that may include receiving means for receiving downlink information including at least F1 application protocol information from a donor node, in the user equipment portion of an integrated access and backhaul node. The apparatus may also comprise a delivery means for transmitting downlink information comprising at least F1 application protocol information from the user equipment portion of the aggregated access and backhaul node to the radio access network portion of the aggregated access and backhaul node.

Another embodiment may relate to a method that may include, at a donor node, generating downlink information for the aggregated access and backhaul node, the downlink information including at least F1 application protocol information. The method may also include transmitting downlink information comprising at least F1 application protocol information from the donor node to the user equipment portion of the aggregated access and backhaul node.

Another embodiment may relate to a device that may include at least one processor and at least one memory including computer program code. The at least one memory and the computer program code are configured to cause the device to generate, by at least one processor, downlink information for at least, at the donor node, for unified access and backhaul nodes, the downlink information being at least an F1 application. Contains protocol information. The apparatus may also be configured to transmit downlink information including at least F1 application protocol information from the donor node to the user equipment portion of the aggregate access and backhaul node.

In some embodiments, the donor node may comprise a donor node central unit for generating the downlink information. In yet another embodiment, the downlink information may be aggregated with other data on the backhaul link. In one embodiment, downlink information generated in the donor node central unit for the radio access network portion of the unified access and backhaul node may be at least F1 application protocol information encapsulated with radio resource control protocol information.

In another embodiment, the signaling radio bearer may be carried over the backhaul link, and the downlink information transmitted to the user equipment portion of the aggregated access and backhaul node may be transmitted over the signaling radio bearer. According to another embodiment, the downlink information is transmitted as a radio resource control message or signal from the donor node central unit to the user equipment portion of the integrated access and backhaul node. In another embodiment, the signaling radio bearer may be identified by an identifier, and the identifier may be a logical channel identifier.

According to one embodiment, the downlink information generated in the donor node central unit for the radio access network portion of the aggregated access and backhaul node may be configured to update the configuration of the radio access network portion of the aggregated access and backhaul node. In another embodiment, a backhaul link may be used when the aggregated access and backhaul node is in a radio link control grant mode.

According to another embodiment, the backhaul link may include at least one of a radio link control layer, a medium access control layer, and an adaptation layer. According to another embodiment, the donor node central unit may include an internal user plane function. In another embodiment, the signaling radio bearer may be terminated in the user equipment portion of the aggregated access and backhaul node.

Another embodiment may relate to a device that may include, in a donor node, a generating means for generating downlink information for an aggregated access and backhaul node, the downlink information including at least F1 application protocol information. . The apparatus may also include transmission means for transmitting downlink information comprising at least F1 application protocol information from the donor node to the user equipment portion of the aggregated access and backhaul node.

In order to properly understand the present invention, reference should be made to the accompanying drawings.
1 shows an example of a diagram according to some embodiments.
2 shows an example of a diagram according to some embodiments.
3 shows an example of a diagram according to some embodiments.
3A shows an example of a diagram in accordance with some embodiments.
4 shows an example of a diagram according to some embodiments.
5 shows an example of a diagram according to some embodiments.
5A shows an example of a flowchart in accordance with some embodiments.
6 shows an example of a flowchart in accordance with some embodiments.
7 shows an example of a flowchart in accordance with some embodiments.
8 shows an example of a system according to some embodiments.

In 5G or NR technology, the IAB node may have a UE portion, which is also known as a User Equipment (UE) function or a Mobile Termination (MT) function, and in an embodiment including a multi-hop relay, a DgNB or other IAB node Is connected with The IAB node may also include a portion of a radio access network (RAN) serving the UE or the access UE as well as child IAB nodes connected to the IAB node, also known as the next hop IAB node. The RAN portion may be composed of a full gNB or a distributed unit (gNB-DU) portion of gNB. In some embodiments, the UE portion may be controlled by radio resource control (RRC) signaling. That is, the UE portion of the IAB node may use an RRC similar to that of any general UE, which means that the donor gNB may configure the IAB node UE portion by sending an RRC reconfiguration message to the IAB node.

Some embodiments may help support self-backhauling in which the same carrier may be used for backhaul connections and access links. That is, some embodiments help to support in-band backhaul operation. 1 and 2 relate to transmission of control signaling to an IAB node RAN part. In particular, embodiments may extend the RRC information transmission to transmit an F1 Application Protocol (F1AP) message from the DgNB central unit (CU) to the RAN/DU portion of the IAB node. In addition to this or in another embodiment, a specific type of signaling radio bearer (SRB), referred to as SRBx, may be used to help transmit the F1 application protocol message from the DgNB CU to the RAN part of the IAB node. By using the SRBx, the UE and/or the IAB node can recognize a signal transmitted according to LCID (Logical Channel IDs). That is, in one embodiment, the RRC information transmission may be extended to transmit the F1AP, whereas in another embodiment, the SRBx may be used to transmit the F1AP.

In some embodiments, Stream Control Transport Protocol (SCTP) or Internet Protocol (IP) may be used to transmit or deliver the F1 Application Protocol (F1AP) from a CU to a Distributed Unit (DU). Using its own backhauling, the F1AP is signaled or transmitted through a user plane function (UPF) for the IAB node using a protocol data unit (PDU) session terminated at the UE portion of the IAB node. Can be. That is, the UPF, which may be located in the IAB node CU outside the donor node, may transmit the F1AP to the UE portion of the IAB node. However, this backhaul signaling using UPF is not suitable for layer 2 (L2) relay-based self backhauling, because by definition SCTP is used over the L2 protocol, and as such, a specific header identifying the protocol must be added. Self-backhauling can be utilized as part of an automated autonomous configuration provided by NR or 5G.

1 shows an example of a diagram according to some embodiments. Specifically, FIG. 1 shows an example of an F1AP for controlling an IAB node RAN portion, which can encapsulate a message in control plane traffic. For example, the message may be contained in a transparent container or SRB of control plane traffic. As shown in FIG. 1, some embodiments may include transmitting an F1AP message (also referred to as F1AP information) from the DgNB CU to the RAN portion of the IAB node by extending RRC information transmission. An SRB such as SRBx is used to transmit F1AP information from the DgNB CU to the IAB node, so that signaling can be recognized according to an identifier such as an LCID or information included in an RRC layer transmitting F1AP information. That is, the LCID may be associated with an SRB or DRB such as SRBx, through which data or downlink information may be received.

1 shows a donor node 110 such as a DgNB including a central unit portion 120 and a distributed unit portion 130. 1 also shows the SRBx that may be established between the DgNB CU and RRC entities in the UE portion of the second IAB node. The same SRBx passes through the first hop 140 located between the DgNB 110 and the first IAB node 150, and the second between the UE portion of the first IAB node 150 and the second IAB node 170 It can pass through the hop 160. The first hop 140 and the second hop 160 may be wireless backhaul links. A message or signaling transmitted over the wireless backhaul link shown as SRBx over the first hop 140 and/or the second hop 160 may be recognized using an identifier such as information contained within the LCID or RRC protocol. . For example, in SRBx, x may be 2 or x may be 4. The same value of x may be applied to both hops indicated in FIG. 1.

The cardinality of the SRB may be related to the priority of the SRB. For example, each SRB may be recognized as having a different priority according to the number x. For example, SRB2 may be defined as having a lower priority than SRB1 and, for example, it may be used for NAS message transmission, whereas SRB4 has a higher priority than SRB2 but a lower priority than SRB1. May be, and is indicated to be used for at least F1AP message transmission or delivery between the DgNB and the IAB node. In some other embodiments, a higher SRB x number may mean a lower priority.

In some embodiments, downlink information may be transmitted from the DgNB CU 120 to the RAN portion of the IAB node via SRBx over the first hop 140 and/or SRBx over the second hop 160. That is, the DgNB CU 120 is for transmission to both the DgNB DU 130 and the RAN portion of the second IAB node 170 (which may also be referred to as the IAB node DU portion). The downlink information may include F1AP information. In some embodiments, the downlink information may be transmitted using RRC signaling, and may be transmitted in the form of RRC information, which is information included in the RRC message. A signaling radio bearer such as SRBx may be used only when transmitting F1AP information in some embodiments. If only a signaling radio bearer such as SRBx is used to transmit the F1AP information, the F1AP information can be additionally differentiated or prioritized through any other traffic. As shown in FIG. 1, the DgNB may configure the RAN portion of the second IAB node using F1AP, which may be transmitted through SRBx. Receiving the F1AP information may change the configuration of the RAN part of the IAB node.

Transmission or delivery of F1AP information using a dedicated signaling radio bearer, such as SRB4 over the wireless backhaul link, and/or RRC information transmission using, for example, SRB2, over-the-air, reduces protocol overhead in wireless transmission. Can be reduced. For example, an IP or SCTP header may not be required in some embodiments. Thus, an IP header with at least 20 bytes may not be required and/or an SCTP header with at least 16 bytes may not be required. When using a dedicated signaling radio bearer over the radio backhaul link, overhead from the RRC message transmitted to the RAN portion of the IAB node can also be minimized. In addition, the embodiment shown in FIG. 1 may not use a user plane function (UPF) to transmit F1AP information, which makes it possible to use the same DgNB CU for both the DgNB DU and the RAN portion of the IAB node. In FIG. 1, a message can be stably transmitted using an SRB. For example, at least one of the SRBs may use Radio Link Control (RLC) approval mode (AM), which may help to more stably transmit F1AP information transmitted through the SRB.

2 shows an example of a diagram according to some embodiments. Specifically, FIG. 2 shows a user plane with UPF 210 used for UE traffic to and from the UE via the L2-based IAB node. As can be seen from FIG. 2, the DgNB 211 may have a CU-DU split. A radio bearer may be provided between the DgNB CU Packet Data Convergence Protocol (PDCP) 212 and the UE PDCP 218. The IAB node shown in FIG. 2 may include a function similar to the DgNB DU 213. In some embodiments, the IAB node may only host at least one lower L2 protocol layer, such as an RLC layer, a medium access control (MAC) layer and/or a physical (PHY) layer.

In some embodiments, HARQ retransmissions may be transmitted individually for each hop, such as the Uu interface between the IAB node and the UE and the first hop 214 and the second hop 216. DRB may be delivered through the Uu interface with the first hop 214 and/or the second hop 216. The example shown in FIG. 2 shows only the RLC-L (low or light) of the first IAB node 215 and the second IAB node 217, which means that the RLC in the IAB node is divided/ This may mean that re-partitioning can be performed and, if necessary, RLC PDU buffering can be performed. RLC retransmission may be end-to-end between the DgNB DU 213 and the UE 218. In another embodiment, the IAB nodes 215 and 217 may host the entire RLC, which means that RLC retransmission may be performed on each hop. When RLC retransmission is performed in each hop 214 and 216, a DgNB having a split CU-DU similar to the split shown in FIG. 2 may be used.

As shown in FIG. 2, a UE tunnel may exist between the UPF 210 and the DgNB CU 212 and an F1 tunnel may exist between the DgNB CU 212 and the DgNB DU 213. L2 MAC aggregation may be performed in the first hop 214 and the second hop 216. The first hop 214 and the second hop 216 may be similar to the first hop 140 and the second hop 160 shown in FIG. 1 and may allow user plane transmission to the IAB node. . In some embodiments, the user plane function may be included in the DgNB DU portion 213, the first IAB node 215 and/or the second IAB node 217. A user specific user tunnel may be provided between the DgNB DU portion 213 and the UE 218.

3 shows an example of a diagram according to some embodiments. Specifically, FIG. 3 shows an example of a MAC PDU structure. In some embodiments, the MAC PDU structure may be the same as the NR MAC PDU structure specified in TS 38.321 except for the UE ID(s) added for the MAC service data unit (SDU). When the UE ID can be added by a separate adaptation layer to be part of the MAC SDU, the MAC PDU may be the same as the MAC PDU specified in TS 38.321. 3GPP TS 38.321 is incorporated herein by reference in its entirety.

The MAC PDU 310 may include an LCID, a MAC control element (MAC CE), a user equipment identifier (ID) and/or a sub-header including a MAC SDU. In addition to RLC and MAC, the backhaul link may include an adaptation layer. The adaptation layer may be a separate layer, or, in some embodiments, may be part of a MAC or RLC. UE traffic of a plurality of UEs served by one or more IAB nodes such as the first IAB node 150 and the second IAB node 170 of FIG. 1 and the IAB node 215 and IAB node 217 of FIG. 2 Wireless backhaul links can be used to aggregate on a single backhaul transmission channel. The backhaul transmission channel may mean a transmission channel used through a backhaul link.

In some embodiments, UE traffic aggregation by one or more IAB nodes may be referred to as MAC or adaptation layer aggregation. In some embodiments, the adaptation layer, or MAC or RLC layer, may add a UE ID for each MAC PDU or MAC SDU. The UE ID can be used for routing in its own backhaul tree under the DgNB. Its own backhaul tree may contain one or more IAB nodes connected to each other.

3A shows an example of a diagram in accordance with some embodiments. Specifically, FIG. 3A shows a combination of diagrams shown in FIGS. 1 and 2, wherein F1AP information is from the UE portion of the second IAB node 170/217 to the RAN portion of the second IAB node 170/217. It can be transmitted or delivered. The upper part of FIG. 3A shows the control plane of the second IAB node, and the lower part shows the user plane from the viewpoint of the access UE. The communication system shown in FIG. 3A includes a DgNB (110/211), a first hop (140/214), a first IAB node (150/215), a second hop (160/216), and a second IAB node 170/ 217), UPF 210 and UE 218. The RAN portion of the second IAB node 170/217 that may be located in the user plane may receive downlink information such as F1AP information from the UE portion of the second IAB node 170 that may be located in the control plane. . IAB node 2 170 and IAB node 2 217 are the same IAB node, 170 denotes a control plane operation, and 217 denotes a user plane operation. The above applies equally to other network elements in the same diagram as DgNB and IAB node 1.

4 shows an example of a diagram according to some embodiments. Specifically, FIG. 4 shows a UE control plane for L2 relay using an IAB node. As can be seen from FIG. 4, a UE Non-Access Stratum (NAS) service is provided in a communication system. The communication system includes an Access and Mobility Function (AMF) 410, a DgNB 411 including a CU part 412 and a DU part 413, a first hop 414, a first IAB node 415, and a second It includes a hop 416, a second IAB node 417 and a UE 418. The embodiment shown in FIG. 4 is shown in FIG. 2 except that FIG. 2 relates to a PDU service in a user plane for UE traffic, and FIG. 4 relates to a NAS service in a control plane for UE traffic. It may be similar to the embodiment described.

The network side (RRC) may be in the DgNB CU 412 and one or more user specific user tunnels or SRBs may be provided between the DgNB CU 412 and the UE 418. Data traffic between the DgNB 411 and the UE 418 may be transmitted using an IAB transport channel that may include L2 MAC layer aggregation or L2 adaptation layer aggregation. In some embodiments, NAS signaling may be between AMF 410 and UE 418 and may be transmitted using RRC signaling, eg, RRC information transmission. As can be seen in FIG. 4, F1AP information may be transmitted from the DgNB CU 412 to the DgNB DU 413.

5 shows an example of a diagram according to some embodiments. Specifically, FIG. 5 shows a control plane for the UE portion of the IAB node. 5, the IAB node NAS service includes the AMF 510, the CU part 512, and the DU part 513 including the DgNB 511, the first hop 514, and the first IAB node 515. ), a second hop 516, and a second IAB node 517. A new radio application protocol (NGAP) over SCTP can be used to connect the AMF 510 and the DgNB CU 512, and the F1 control plane can be used to connect the DgNB CU 512 and the DgNB DU 513, , L2 MAC aggregation may be used to connect the DgNB DU portion 513 and the first IAB node 515 and connect the first IAB node 515 and the second IAB node 517.

As shown in FIG. 5, IAB nodes 515 and 517 may have a UE portion that receives and/or transmits downlink or uplink information over a backhaul link. IAB nodes 515 and 517 may also have a RAN portion (also referred to as an IAB node DU portion) capable of receiving and/or transmitting uplink or downlink information in the access direction. The RAN portion of the IAB node may communicate with the UE itself or with the UE portion of the next hop IAB node. The UE portion of the IAB node may function similarly to the UE, but the UE portion of the IAB node may support any enhancements specified for the backhaul link in addition to the UE functionality. The enhancements specified for the backhaul link may be located in the MAC layer and/or the adaptation layer, for example.

In some embodiments, control of the UE portion of the IAB node, such as PHY, MAC, RLC or reconfiguration of the adaptation layer, may be performed using RRC signaling. For example, the UE portion of the IAB node may terminate the SRB carrying RRC and NAS signaling. RRC may be located in DgNB CU, and NAS may be located in AMF. The SRB terminated in the UE portion of the IAB node may be transmitted over a backhaul link with or separately from normal UE traffic. In some embodiments, the aggregation shown in FIG. 5 may be aggregated on the same transport channel of UE traffic and SRB. To facilitate routing and multiplexing, the UE portion of the IAB node may have a similar identifier (which may be a UE ID) as other 3GPP access UEs. The UE ID may be included in downlink information transmitted from the DgNB, or downlink information transmitted from the UE portion of the IAB node to help the IAB node identify the access UE or the UE portion of the IAB node. In other embodiments, the RAN portion of the IAB node may identify the downlink link used to update the configuration of the RAN portion.

The DgNB CU 512 may control the DgNB DU 513 using F1AP when the DgNB 511 includes a CU-DU split. Thus, in some embodiments, the DgNB CU 512 may be used to transmit F1AP information to the DgNB DU 513 and the RAN portion of the IAB node. According to the above embodiments, the F1AP information may be transmitted from the DgNB CU 512 to the IAB nodes 515 and 517 through one or more backhaul links or hops 514 and 516. The F1AP may be transmitted in a CU-DU split through SCTP and/or IP. When using SCTP and/or IP for transmission between the DgNB CU and the IAB node, the IP packet may be located in the DgNB CU or routed through an internal UPF disposed therewith. The internal UPF located within the DgNB CU can be used to handle IP routing to the IAB node and/or UE. Some embodiments may use a PDU session and/or a data radio bearer (DRB) that may be terminated at the IAB node.

1-5, in some embodiments including a multi-hop self backhauling link or one or more individual self-backhauling links, the RAN protocol and/or SRB may be used to wirelessly transmit F1AP information. . That is, the RAN protocol and/or SRB may be used to transmit F1AP information through a radio backhaul link. In the embodiment shown in FIGS. 1-5, SRB content may not be tunneled from the CU. In addition, between the DgNB CU and the DgNB DU, SRB may be used instead of DRB to have a lossless fixed F1AP interface similar to F1AP over SCTP. For example, user plane traffic between the DgNB CU and the DgNB DU may use GPRS tunneling protocol user data tunneling (GTP-U).

In some embodiments, RRC information transmission may be used. The downlink information may be transmitted to the RAN or DU portion of the IAB node through the UE portion of the IAB node. The downlink information may support or include F1AP information. The UE portion that has received the downlink information may be in the RRC connected mode. In some embodiments, the uplink information transmission procedure from the IAB node may also support F1AP protocol signaling. For example, this embodiment may be similar to a NAS signaling transmission in which the recipient can infer the intended destination of the message from the structure of the message. Both the RRC procedure and ASN.1 can be improved to support sending F1AP information to the IAB node.

As shown in FIG. 1, SRBx may be used for transmission of F1AP. One type of SRB, such as SRB4, may be designated for F1AP information transmission between the DgNB CU and the RAN portion or DU portion of the IAB node. Since the SRB can use the fixed LCID, information transmitted from the DgNB CU can be identified when the SRBx is used for F1AP transmission. Thus, in some embodiments, the F1AP information or message may be transmitted directly from the F1AP layer to the PDCP layer of SRB4, and the receiver may route this message to the F1AP layer.

Downlink information such as F1AP may be transmitted from the DgNB CU to the RAN portion of the IAB node (also referred to as the IAB node gNB DU) through the UE portion of the IAB node in the RRC connected mode. That is, the exclusive information of the F1 application protocol may be used to transmit RAN part/DU IAB node specific F1AP information between the network and the IAB node. In some embodiments, both the UE and RAN portions of the IAB node may be in RRC connected mode, while in some other embodiments, the UE and RAN portions of the IAB node may be in different modes. For example, the UE portion of the IAB node may be in connected mode, while the RAN portion of the IAB node may be in inactive mode. In some embodiments, the RAN may initiate transmission of downlink information when it needs to transmit F1AP-only information. The RAN may initiate downlink information transmission by, for example, sending a downlink information transmission message from the DgNB to the IAB node. Upon receiving the downlink information, the IAB node or the UE portion of the IAB node may identify the F1AP and transmit the received information to the upper layer of the F1AP, for example, an entity that processes the F1AP.

In some embodiments, the IAB control message may be used for transmission of downlink information. The downlink information may include F1AP information. The downlink information may be transmitted via a wireless backhaul, for example via SRB4. In some embodiments, the downlink information may also be transmitted over the downlink control channel, and the RLC service access point may be in grant mode. In the grant mode, the RLC entity may be configured to transmit or receive PDUs on the downlink or uplink control channel.

5A shows an example of a flowchart in accordance with some embodiments. In step 520, the donor node central unit, for example the DgNB CU, may transmit or deliver the F1 application information to the RAN portion of the IAB node. In some embodiments, the F1 application information may be transmitted over an SRB such as SRBx. In step 530, the UE portion of the IAB node may receive a message containing downlink F1 application protocol information transmitted from the donor node central unit in step 520, for example via SRBx. In step 540, the RAN portion of the IAB node may receive the F1 application protocol information from the donor node central unit through the UE portion of the IAB node. That is, the UE portion of the IAB node may transmit the F1 application information, and the RAN portion of the IAB node may receive the F1 application information transmitted from the UE portion of the IAB node.

6 shows an example of a flowchart in accordance with some embodiments. Specifically, FIG. 6 shows a method or process performed by the UE portion of the IAB node. In step 610, the UE portion of the IAB node may receive downlink information from a donor node, such as a DgNB. The downlink information may include F1 application protocol information. In one embodiment, the donor node may comprise a donor node central unit for generating downlink information. In some embodiments, the donor node central unit may include an internal UPF. The downlink information may be aggregated, for example, with other data on the backhaul link located between the DgNB CU and the UE portion of the IAB node, or between the DgNB CU and the RAN portion of the IAB node. In some embodiments, the SRB may be carried over a backhaul link. In some embodiments, the backhaul link may be used when the IAB node is in the RLC AM. The backhaul link may include at least one of an RLC layer, a MAC layer, or an adaptation layer. Downlink information received in the UE portion of the IAB node may be received through the SRB. In some embodiments, the downlink information may be received as an RRC message or signal at the UE portion of the IAB node.

SRB may include an identifier such as an LCID. SRB may be terminated in the UE portion of the IAB node. In step 620, the UE portion of the IAB node may identify that the received downlink information should be delivered to the RAN portion of the IAB node, based on the identifier in the RRC message or the LCID used for the SRB. In step 630, the UE portion of the IAB node may deliver downlink information, which may include F1 application protocol information, to the RAN portion of the IAB node.

The downlink information delivered from the UE portion of the IAB node to the RAN portion of the IAB node may update the configuration of the RAN portion of the IAB node. That is, the RAN portion of the IAB node may update the configuration of the RAN portion of the IAB node based on the identified configuration received from the donor node central unit through the UE portion of the IAB node. The RAN portion of the IAB node may identify the updated configuration of the RAN portion of the IAB node based on downlink information or F1 application information. In some embodiments, at least one signal of a NAS service or a PDU service may be transmitted through the IAB node.

7 shows an example of a flowchart in accordance with some embodiments. Specifically, Fig. 7 shows a method or process performed by a donor node central unit, such as a DgNB. In step 710, the donor node may generate or configure downlink information for the IAB node. In some embodiments where the donor node may be divided into CU-DUs, the donor node central unit may generate or configure downlink information for the IAB node. In some embodiments, the donor node central unit may include an internal user plane function. The downlink information may include F1 application protocol information. Downlink information generated in the donor node central unit may be configured for the RAN portion of the IAB node. In some embodiments, downlink information may be transmitted from the donor node central unit to the UE portion of the IAB node to reconfigure or configure the UE portion of the IAB node. The downlink information generated by the donor node central unit for the RAN of the IAB node may be RRC protocol information including F1 application protocol information. The downlink information generated in the donor node central unit for the RAN portion of the IAB node may be configured to update the configuration of the RAN portion of the IAB node.

In step 720, the method may include transmitting downlink information including F1 application protocol information from the donor node central unit to the UE portion of the IAB node via a backhaul link. The downlink information can be aggregated with other data on the backhaul link. The backhaul link may be used when the aggregate access and backhaul node is in a radio link control grant mode. The backhaul link may include at least one of an RLC layer, a MAC layer, or an adaptation layer. In some embodiments, the SRB may be carried over the backhaul link, and the downlink information transmitted to the UE portion of the IAB node may be transmitted over the SRB. The SRB may include an identifier, and the identifier may be an LCID. In some embodiments, the SRB may be terminated in the UE portion of the IAB node. In one embodiment, the F1AP information may be transmitted by extending the RRC information transmission to transmit the F1AP. In this embodiment, the F1AP information may be encapsulated within an RRC message, and this message may be transmitted to the UE portion of the IAB node using an existing SRB, eg SRB2. In another embodiment, another SRB, for example SRB4, may be specified to transmit the F1AP information. In the latter embodiment, the F1AP information is not encapsulated in an RRC message, but instead the F1AP message itself is transmitted through another SRB. In general, the SRB transmits an RRC message, but here in the latter embodiment, the RRC may not be involved in the transmission of F1AP information.

As described above, in some embodiments, the donor node central unit, eg, the DgNB CU, may configure or generate F1 application protocol information for the RAN portion of the IAB. In addition, the donor central unit may configure or generate RRC protocol information including F1 application protocol information for the UE portion of the IAB node. The donor node central unit may then transmit the F1 application protocol information to the RAN portion of the IAB node through an SRB such as SRBx. The F1 application protocol information may be transmitted from the donor node central unit to the RAN portion of the IAB node through the UE portion of the IAB node.

8 shows a system in accordance with some embodiments. It is to be understood that each block of FIGS. 1 to 7 may be implemented by various means, such as hardware, software, firmware, one or more processors and/or circuits, or a combination thereof. In one embodiment, the system may include several devices such as, for example, network entity 820 or UE 810. Although only one network entity is shown for illustration, the system may include one or more UEs 810 and one or more network entities 820. The network entity may be a network node, an access node, a base station, an evolved NodeB (eNB), a 5G or NR NodeB (gNB), a donor gNB, a host, a server, or any other access or network node discussed herein.

In some embodiments, the IAB node 830 has a UE portion similar to the UE 810 and access UEs or next hop IAB node UE portion for communicating with the RAN portion of the donor node or parent IAB node in a multi-hop embodiment. It may include a RAN portion that may be similar to the network entity 820 for communication of. Thus, in some embodiments, a single IAB node includes at least two or more processors 811 and 821, at least two or more transceivers 813 and 823, at least two or more memories 812 and 822, and at least two or more antennas ( 814, 824). In another embodiment, the processor, transceiver, memory and/or antenna may be shared between the UE portion and the RAN portion of the IAB node.

Each of these devices may include at least one processor or control unit or module denoted 811 and 821. At least one memory may be provided for each device, and these may be denoted 812 and 822, respectively. The memory may contain computer program instructions or computer code. One or more transceivers 813 and 823 may be provided, and each device may also include antennas shown at 814 and 824, respectively. Although only one antenna each is shown, multiple antennas and multiple antenna elements may be provided in each device. A higher category UE generally includes a plurality of antenna panels. For example, other configurations of these devices may be provided. For example, the network entity 820 and the UE 810 may be additionally configured for wired communication in addition to wireless communication, and in this case, the antennas 814 and 824 are not limited to just antennas, and any form of communication May represent hardware.

Transceivers 813 and 823 may each independently be a transmitter, a receiver, or a unit or device that may be configured for both transmitter and receiver, or for both transmission and reception. In other embodiments, the network entity may have at least one individual receiver or transmitter. The transmitter and/or receiver (as far as the radio component is concerned) can also be implemented, for example, as a remote radio head on the mast and not on the device itself. Operations and functions can be performed on other entities such as nodes, hosts or servers in a flexible manner. In other words, the division of work may vary depending on the situation. One possible use is to allow network nodes to serve local content. One or more functions may be implemented as virtual application(s) in software that may run on a server.

The user device or user equipment includes a mobile phone or a mobile station (MS) such as a smart phone or multimedia device, a tablet with wireless communication function, a personal data or digital assistant (PDA) with wireless communication function, a portable media player, a digital camera, and a pocket. It may be a video camera, a navigation unit with wireless communication capability, or any combination thereof. In other embodiments, the UE may be a machine type communication (MTC) device or an Internet of Things device, which may not require human interaction such as sensors, meters, and actuators.

In some embodiments, a device such as user equipment 810 or network entity 820 may include means for performing the embodiments described above with respect to FIGS. 1-7. In some embodiments, the device may include computer program code and at least one memory including at least one processor. At least one memory containing computer program code may be configured, by at least one processor, to cause an apparatus to perform at least one of the processes described herein. The device may be, for example, user equipment 810 or network entity 820.

The processors 811 and 821 include a central processing unit (CPU), a digital signal processor (DSP), an application specific integrated circuit (ASIC), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), and digitally enhanced circuits. Or any computing or data processing device, such as a similar device or a combination thereof. The processor may be implemented as a single controller or a plurality of controllers or processors.

In the case of firmware or software, the implementation may include modules or units of at least one chipset (eg, procedure, function, etc.). Memory 812 and 822 may be any suitable storage device, such as a non-transitory computer-readable medium. A hard disk drive (HDD), random access memory (RAM), flash memory or other suitable memory may be used. The memory may be combined with the processor on a single integrated circuit, or may be separate from it. In addition, computer program instructions may be stored in memory and processed by a processor, and may be computer program code in any suitable form, such as a compiled or interpreted computer program written in any suitable programming language. The memory or data storage entity is typically internal, but may be external or a combination thereof, such as when additional memory capacity is obtained from a service provider. The memory can be fixed or removable.

The memory and computer program instructions, along with a processor for a particular device, may be configured to cause a hardware device, such as the network entity 820 or the UE 810, to perform any of the processes described above (e.g., FIG. 1-7). Thus, in some embodiments, a non-transitory computer-readable medium is a computer instruction or one or more computer programs (e.g., additional or non-transitory) capable of performing a process such as one of the processes described herein when executed in hardware. Updated software routines, applets or macros). In another embodiment, the computer program product may encode instructions for performing any of the processes described above, or may be embodied in a non-transitory computer-readable medium, and the above-described process when executed on a computer program product and hardware. It is possible to encode an instruction that performs any of the processes. The computer program may be coded in a programming language, which may be a high-level programming language such as objective-C, C, C++, C#, Java, or the like, or a low-level programming language such as machine language or assembler. Alternatively, some embodiments may be performed entirely in hardware.

In some embodiments, an apparatus may include circuitry configured to perform any of the processes or functions shown in FIGS. 1-6. In one example, the circuit may be implemented as a hardware-only circuit such as an analog and/or digital circuit. In another example, the circuit is a combination of analog and/or digital hardware circuit(s) and software or firmware, and/or any portion of the hardware processor(s) and software (including digital signal processor(s)). , Software, and at least one memory working together to cause the device to perform various processes or functions. In another example, the circuit may be a hardware circuit and/or processor(s) such as a microprocessor(s) or part of a microprocessor(s) comprising software such as firmware for manipulation. The software of the circuit may not exist if it is not necessary for the operation of the hardware.

A specific example of the circuit may be a content coding circuit, a content decoding circuit, a processing circuit, an image generating circuit, a data analysis circuit, or a discrete circuit. The term circuit can also be a baseband integrated circuit or processor integrated circuit, for example for a mobile device, a network entity, or a similar integrated circuit in a server, cellular network device or other computing or network device.

In addition, although FIG. 8 illustrates a system including a network entity 820 and a UE 810, some embodiments may be applied to configurations including other configurations and additional elements, as illustrated and discussed herein. have. For example, there may be multiple user equipment and multiple network entities, and there may be other nodes that provide similar functions, such as nodes that combine the functions of the user equipment and network entities such as relay nodes. Similarly, the UE 810 may have various configurations for communication other than the communication network entity 820. For example, the UE 810 may be configured for device-to-device, machine-to-machine and/or vehicle-to-vehicle transmission.

The above embodiments can significantly improve the functionality of the network and/or of the user equipment and network entities included in the network. Specifically, the above embodiments are canonical, such as using "empty SEQUENCE", e.g., using a non-critical extension through ASN.1 SEQUENCE, where the content remains open at the time of definition and is only defined later. It makes it possible to efficiently extend 5G or NR signaling using the ASN.1 extension mechanism. In other embodiments, the ASN.1 extension mechanism may be an extension addition group, e.g., a "omitted sign" marker is defined in the ASN.1 code to later define a predefined syntax or open OCTET STRING (e.g. ASN.1 field) Defined OCTET STRING, but no content and content will be defined later) can be an ASN.1 extension mechanism to indicate where a new field can be created after an ellipsis marker. Embodiments may also help reduce protocol overhead in wireless transmission by using SRBx and/or RRC transmission information. The DgNB CU can also be used for both the DgNB DU and/or the RAN portion of the IAB node, which helps to reduce the resources required for F1AP transmission.

Features, structures, or characteristics of some embodiments described throughout this specification may be combined in any suitable manner in one or more embodiments. For example, “specific embodiments,” “some embodiments,” “other embodiments,” or other similar phrases used throughout this specification indicate that a particular feature, structure, or characteristic described in connection with the embodiment It means that it can be included in at least one embodiment. Thus, throughout this specification, “in a specific embodiment,” “in some embodiments,” “in other embodiments,” or other similar phrases do not necessarily mean the same group of embodiments, and the features, structures described, Or the features may be combined in any suitable manner in one or more embodiments.

Those skilled in the art will readily understand that the invention described above may be practiced with different sequences of steps and/or hardware elements of different configurations than those disclosed. Therefore, although the present invention has been described based on these preferred embodiments, it will be apparent to those skilled in the art that some modifications, variations and alternative configurations may be made within the spirit and scope of the present invention.

Abbreviation

AMF Access and Mobility Function

BH Backhaul

CU Central Unit

DRB Data Radio Bearer

DU Distributed Unit

F1AP F1 Application Protocol

F1-C F1 Control plane

F1-U F1 User plane

GTP-U GPRS Tunneling Protocol User data tunneling

IAB Integrated Access and Backhaul

MAC Medium Access Control

NAS Non-Access Stratum

PDCP Packet Data Convergence Protocol

PDU Protocol Data Unit

RAN Radio Access Network

RLC Radio Link Control

RN Relay Node

RRC Radio Resource Control

SCTP Stream Control Transmission Protocol

SRB Signaling Radio Bearer

UE User Equipment

UPF User Plane Function

Claims (53)

As a method,
In the user equipment part of the integrated access and backhaul node, receiving downlink information including at least F1 application protocol information from a donor node, and
Transmitting the downlink information comprising at least the F1 application protocol information from the user equipment portion of the aggregated access and backhaul node to a radio access network portion of the aggregated access and backhaul node,
Way.
The method of claim 1,
The donor node comprises a donor node central unit for generating the downlink information,
Way.
The method according to claim 1 or 2,
The downlink information is aggregated with other data on the backhaul link,
Way.
The method according to any one of claims 1 to 3,
A signaling radio bearer is delivered through the backhaul link,
The downlink information received at the user equipment portion of the aggregated access and backhaul node is received through the signaling radio bearer,
Way.
The method according to any one of claims 1 to 4,
The downlink information is received as a radio resource control message or signal at the user equipment portion of the integrated access and backhaul node,
Way.
The method according to any one of claims 1 to 5,
The signaling radio bearer is identified by an identifier, and the identifier is a logical channel identifier,
Way.
The method according to any one of claims 1 to 6,
Based on an identifier in the radio resource control message or a logical channel identifier used for the signaling radio bearer, identifying that the received downlink information should be transmitted to the radio access network portion of the aggregated access and backhaul node. More included,
Way.
The method according to any one of claims 1 to 7,
The downlink information transmitted from the user equipment portion of the aggregated access and backhaul node to the radio access network portion of the aggregated access and backhaul node updates the configuration of the radio access network portion of the aggregated access and backhaul node,
Way.
The method according to any one of claims 1 to 8,
The backhaul link of the aggregated access and backhaul node is configured to use a radio link control grant mode,
Way.
The method according to any one of claims 1 to 9,
The backhaul link includes at least one of a radio link control layer, a medium access control layer, and an adaptation layer,
Way.
The method according to any one of claims 1 to 10,
The donor node central unit includes an internal user plane function,
Way.
The method according to any one of claims 1 to 11,
The signal of at least one service of a non-access layer service or a protocol data unit service is transmitted through the integrated access and backhaul node,
Way.
The method according to any one of claims 1 to 12,
The signaling radio bearer is terminated at the user equipment portion of the aggregated access and backhaul node,
Way.
As a device,
At least one processor,
At least one memory containing computer program code,
The at least one memory and the computer program code cause the device by the at least one processor to at least,
In the user equipment portion of the integrated access and backhaul node, to receive downlink information including at least F1 application protocol information from the donor node,
Configured to transmit the downlink information comprising at least the F1 application protocol information from the user equipment portion of the aggregated access and backhaul node to a radio access network portion of the aggregated access and backhaul node,
Device.
The method of claim 14,
The donor node comprises a donor node central unit for generating the downlink information,
Device.
The method of claim 14 or 15,
The downlink information is aggregated with other data on the backhaul link,
Device.
The method according to any one of claims 14 to 16,
A signaling radio bearer is delivered through the backhaul link,
The downlink information received at the user equipment portion of the aggregated access and backhaul node is received through the signaling radio bearer,
Device.
The method according to any one of claims 14 to 17,
The downlink information is received as a radio resource control message or signal at the user equipment portion of the integrated access and backhaul node,
Device.
The method according to any one of claims 14 to 18,
The signaling radio bearer is identified by an identifier, and the identifier is a logical channel identifier,
Device.
The method according to any one of claims 14 to 19,
The at least one memory and the computer program code may also cause the device to, by the at least one processor, the received down message, based on an identifier in the radio resource control message or a logical channel identifier used for the signaling radio bearer. Configured to identify that link information should be transmitted to the radio access network portion of the aggregated access and backhaul node,
Device.
The method according to any one of claims 14 to 20,
The downlink information transmitted from the user equipment portion of the aggregated access and backhaul node to the radio access network portion of the aggregated access and backhaul node updates the configuration of the radio access network portion of the aggregated access and backhaul node,
Device.
The method according to any one of claims 14 to 21,
The backhaul link of the aggregated access and backhaul node is configured to use a radio link control grant mode,
Device.
The method according to any one of claims 14 to 22,
The backhaul link includes at least one of a radio link control layer, a medium access control layer, and an adaptation layer,
Device.
The method according to any one of claims 14 to 23,
The donor node central unit includes an internal user plane function,
Device.
The method according to any one of claims 14 to 24,
The signal of at least one service of a non-access layer service or a protocol data unit service is transmitted through the integrated access and backhaul node,
Device.
The method according to any one of claims 14 to 25,
The signaling radio bearer is terminated at the user equipment portion of the aggregated access and backhaul node,
Device.
As a device,
Receiving means for receiving downlink information including at least F1 application protocol information from the donor node, in the user equipment portion of the integrated access and backhaul node,
Transmitting means for transmitting the downlink information including at least the F1 application protocol information from the user equipment portion of the aggregated access and backhaul node to a radio access network portion of the aggregated access and backhaul node,
Device.
As a method,
In the donor node, generating downlink information for the aggregated access and backhaul node, the downlink information including at least F1 application protocol information; and,
Transmitting the downlink information including the at least F1 application protocol information from the donor node to a user equipment portion of the aggregated access and backhaul node,
Way.
The method of claim 28,
The donor node is a donor node central unit for generating the downlink information
Containing,
Way.
The method of claim 28 or 29,
The downlink information is aggregated with other data on the backhaul link,
Way.
The method according to any one of claims 28 to 30,
The downlink information generated in the donor node central unit for the radio access network portion of the integrated access and backhaul node is at least F1 application protocol information encapsulated with radio resource control protocol information,
Way.
The method according to any one of claims 28 to 31,
The signaling radio bearer is carried over the backhaul link,
Downlink information transmitted to the user equipment portion of the aggregated access and backhaul node is transmitted through the signaling radio bearer,
Way.
The method according to any one of claims 28 to 32,
The downlink information is transmitted as a radio resource control message or signal from the donor node central unit to the user equipment portion of the integrated access and backhaul node,
Way.
The method according to any one of claims 28 to 33,
The signaling radio bearer includes an identifier,
The identifier is a logical channel identifier,
Way.
The method according to any one of claims 28 to 34,
The downlink information generated in the donor node central unit for the radio access network portion of the aggregated access and backhaul node is configured to update the configuration of the radio access network portion of the aggregated access and backhaul node,
Way.
The method according to any one of claims 28 to 35,
The backhaul link is used when the aggregated access and backhaul node is in a radio link control grant mode,
Way.
The method according to any one of claims 28 to 36,
The backhaul link includes at least one of a radio link control layer, a medium access control layer, and an adaptation layer,
Way.
The method according to any one of claims 28 to 37,
The donor node central unit includes an internal user plane function,
Way.
The method according to any one of claims 28 to 38,
The signaling radio bearer is terminated at the user equipment portion of the aggregated access and backhaul node,
Way.
As a device,
At least one processor,
At least one memory containing computer program code,
The at least one memory and the computer program code cause the device by the at least one processor to at least,
At the donor node, generate downlink information for the aggregated access and backhaul node, the downlink information including at least F1 application protocol information; and,
Configured to transmit the downlink information including the at least F1 application protocol information from the donor node to the user equipment portion of the aggregated access and backhaul node,
Device.
The method of claim 40,
The donor node comprises a donor node central unit for generating the downlink information,
Device.
The method of claim 40 or 41,
The at least one memory and the computer program code are further configured by the at least one processor to cause the apparatus to synthesize the downlink information with other data on a backhaul link,
Device.
The method according to any one of claims 40 to 42,
The downlink information generated in the donor node central unit for the radio access network portion of the integrated access and backhaul node is at least F1 application protocol information encapsulated with radio resource control protocol information,
Device.
The method according to any one of claims 40 to 43,
A signaling radio bearer is delivered through the backhaul link,
Downlink information transmitted to the user equipment portion of the aggregated access and backhaul node is transmitted through the signaling radio bearer,
Device.
The method according to any one of claims 40 to 44,
The downlink information is transmitted as a radio resource control message or signal from the donor node central unit to the user equipment portion of the integrated access and backhaul node,
Device.
The method according to any one of claims 40 to 45,
The signaling radio bearer includes an identifier,
The identifier is a logical channel identifier,
Device.
The method according to any one of claims 40 to 46,
The downlink information generated in the donor node central unit for the radio access network portion of the aggregated access and backhaul node is configured to update the configuration of the radio access network portion of the aggregated access and backhaul node,
Device.
The method according to any one of claims 40 to 47,
The backhaul link is used when the aggregated access and backhaul node is in a radio link control grant mode,
Device.
The method according to any one of claims 40 to 48,
The backhaul link includes at least one of a radio link control layer, a medium access control layer, and an adaptation layer,
Device.
The method according to any one of claims 40 to 49,
The donor node central unit includes an internal user plane function,
Device.
The method according to any one of claims 40 to 50,
The signaling radio bearer is terminated at the user equipment portion of the aggregated access and backhaul node,
Device.
As a device,
In the donor node, generating means for generating downlink information for the aggregated access and backhaul node, the downlink information including at least F1 application protocol information; and,
A transmission means for transmitting the downlink information including the at least F1 application protocol information from the donor node to the user equipment portion of the aggregated access and backhaul node,
Device.
As a computer readable medium,
A program instruction for performing the method according to any one of claims 1 to 13 and 28 to 39 is stored,
Computer readable medium.

Images