IAB node handover during CU migration

Abstract

A method is performed by the target CU during the handover of a migration node from a source central unit (CU) and a source distributed unit (DU) to a target CU and a target DU. The method includes sending a first handover command to the target DU for handing over at least one child node of the migration node from the source CU and source DU to the target CU and target DU.

Description

Technical Field

[0001] This disclosure generally relates to wireless communications, and more specifically, to systems and methods for integrated access and wireless backhaul (IAB) handover in central unit (CU) migration. Background Technology

[0002] The 3GPP (3rd Generation Partnership Project) wireless network specifications include the IAB (Independent Access Block) for 5G (5G) New Radio (NR) networks. The use of short-range millimeter-wave spectrum in NR creates a need for dense deployments with multi-hop backhaul. However, fiber-to-every-base station is too expensive and sometimes impossible (e.g., historical sites). The main IAB principle is to use wireless links (instead of fiber) for backhaul to enable flexible and dense cell deployments without densifying the transport network. Use case scenarios for the IAB can include coverage extension, deployment of large numbers of small cells, and fixed wireless access (FWA) for example, in residential / office buildings. The large bandwidth available for NR in millimeter-wave spectrum provides opportunities for self-backhaul without limiting the spectrum available for access links. Furthermore, the inherent multi-beam and multiple-input multiple-output (MIMO) support in NR reduces cross-link interference between backhaul and access links, thus facilitating higher density.

[0003] The IAB architecture discussed in 3GPP TR 38.874 can utilize the Central Unit (CU) / Distributed Unit (DU) split architecture of NR, where IAB nodes host the DU portion controlled by the CU. IAB nodes also have a Mobile Termination (MT) portion for communicating with their parent nodes.

[0004] The IAB specification can reuse other existing functions and interfaces defined in NR. Specifically, MT, gNodeB-Distributed Unit (gNB-DU), gNodeB-Central Unit (gNB-CU), User Plane Function (UPF), Access and Mobility Management Function (AMF), and Session Management Function (SMF), along with their corresponding interfaces NR Uu (between MT and gNB), F1, NG, X2, and N4, serve as the baseline for the IAB architecture. Modifications or enhancements to these functions and interfaces to support IAB will be explained in the context of the architecture discussion. Additional features such as multi-hop forwarding are included in the architecture discussion because they aid in understanding IAB operations.

[0005] MT functionality is an integral part of an IAB node. As used herein, MT refers to a function residing on an IAB-node that terminates the radio interface layer of the backhaul Uu interface toward the IAB-donor or other IAB-nodes.

[0006] Figure 1A high-level architectural view of a sample IAB network is shown. Specifically, Figure 1 This is a reference diagram for the IAB in standalone mode, where the IAB comprises one IAB donor and multiple IAB nodes. The IAB donor is considered a single logical node, which includes a set of functions (e.g., gNB-DU, gNodeB-Central Unit-Control Plane (gNB-CU-CP), gNodeB-Central Unit-User Plane (gNB-CU-UP)) and other possible functions. In deployment, the IAB donor can be split based on these functions, as allowed by the 3GPP Next Generation Radio Access Network (NG-RAN) architecture; these functions may all be located in the same location or not. When such splitting occurs, IAB-related aspects may arise. Furthermore, if it is obvious that some of the functions currently associated with the IAB donor do not perform IAB-specific tasks, these functions can be moved outside the donor.

[0007] Figure 2 The baseline user plane protocol stack for IAB is shown. Figure 3 The baseline control plane protocol stack for IAB is shown. For example... Figure 2 and Figure 3 As shown, the selected protocol stack reuses the current CU-DU split specification, where the complete user plane F1-U (General Packet Radio Service Tunneling Protocol-User Plane (GTP-U) / User Datagram Protocol (UDP)) / Internet Protocol (IP)) terminates at the IAB node (as in a regular DU), and the complete control plane F1-C (F1-Application Protocol (F1-AP) / Flow Control Transport Protocol (SCTP) / IP) also terminates at the IAB node (as in a regular DU). In the above case, Network Domain Security (NDS) is used to protect both UP and CP services (Internet Protocol Security (IPsec) in the case of UP, and Datagram Transport Layer Security (DTLS) in the case of CP). IPsec can also be used for CP protection instead of DTLS, and in this case, the DTLS layer will not be used.

[0008] IAB nodes and IAB donors include a Backhaul Adaptation Protocol (BAP), which routes packets to appropriate downstream / upstream nodes and maps user equipment (UE) bearer data to appropriate backhaul radio link control (RLC) channels (as well as between ingress and egress backhaul RLC channels in intermediate IAB nodes) to meet the end-to-end quality of service (QoS) requirements of the bearer.

[0009] On an IAB-node, the BAP sublayer contains one BAP entity at the MT function and a separate BAP entity located at the same location at the DU function. On an IAB-donor-DU, the BAP sublayer contains only one BAP entity. Each BAP entity has a transmit part and a receive part. The transmit part of the BAP entity has a corresponding receive part at the IAB-node or IAB-donor-DU across the backhaul link.

[0010] Figure 4 An example functional view of the BAP sublayer is shown. Although Figure 4 This example architecture is based on the radio interface protocol architecture defined in 3GPP TS 38.300, but it should not limit the implementation. Figure 4 In this implementation, the receiving part on a BAP entity transmits BAP Protocol Data Units (PDUs) to the sending part on a BAP entity located in the same location. Alternatively, the receiving part can transmit BAP Service Data Units (SDUs) to the sending part located in the same location. When transmitting a BAP SDU, the receiving part removes the BAP header, while the sending part adds a BAP header, wherein the BAP Routing Identifier (ID) is the same as the BAP Routing Identifier carried in the BAP PDU header before removal. Therefore, in the implementation, transmitting a BAP SDU in this manner is functionally equivalent to transmitting a BAP PDU.

[0011] The BAP sublayer provides data transmission services to the upper layers. The BAP sublayer expects each RLC entity to receive the following services from the lower layers: acknowledged data transmission services and unacknowledged data transmission services. A detailed description is provided in 3GPP TS 38.322.

[0012] The BAP sublayer supports the following functions: data transmission; determining the BAP destination and path of packets from the upper layer; determining the egress backhaul RLC channel for packets routed to the next hop; routing packets to the next hop; distinguishing between traffic to be transmitted to the upper layer and traffic to be transmitted to the egress link; and flow control feedback and polling signaling.

[0013] Figure 5 Examples of some possible IAB-node migration scenarios are shown, listed in order of complexity.

[0014] For example, in case (A) within the CU, the IAB-node (e) and the UE it serves are moved together to a new parent node (IAB-node (b)) under the same donor-DU (1). A successful migration within the donor-DU requires establishing a UE context for the IAB-node (e) MT in the DU of the new parent node (IAB-node (b)), updating the routing tables of the IAB nodes along the path to the IAB-node (e), and allocating resources on the new path. The IP address of the IAB-node (e) will remain unchanged, while the F1-U tunnel / connection between the donor-CU (1) and the IAB-node (e) DU will be redirected through the IAB-node (b).

[0015] As another example, in case (B) within the CU, the process requirements / complexity are the same as in case (A). Furthermore, since the new IAB-donor DU (i.e., DU2) is connected to the same L2 network, the IAB-node (e) can use the same IP address under the new donor DU. However, the new donor DU (i.e., DU2) will need to notify the network using the IAB-node (e)'s L2 address in order to acquire / maintain the same IP address for the IAB-node (e) through some mechanism such as Address Resolution Protocol (ARP).

[0016] The situation within the CU (C) is more complex than that within the CU (A) because it also requires the allocation of a new IP address for the IAB-node (e). In the case where IPsec is used to protect the F1-U tunnel / connection between the donor-CU (1) and the IAB-node (e) DU, it is possible to use the existing IP address along the path segment between the donor-CU (1) and the security gateway (SeGW), as well as the new IP address of the IPsec tunnel between the SeGW and the IAB-node (e) DU.

[0017] As another example, the CU-intersection case (D) is the most complex in terms of process requirements and may require new specification processes that go beyond the scope of 3GPP Release 16.

[0018] Note that 3GPP Release 16 has a standardized process for migrations within a CU only. Specifically, during CU topology adaptation, both the source and target parent nodes are served by the same IAB-donor-CU. The target parent node can use a different IAB-donor-DU than the source parent node. The source path can also share nodes with the target path.

[0019] Figure 6 The example of an IAB CU-based topology adaptation process is shown, where the target parent node uses a different IAB-donor-DU than the source parent node. Specifically, the illustrated CU-based topology adaptation process includes:

[0020] 1. The migrated IAB-MT sends a measurement report message to the source parent node gNB-DU. This report is based on the measurement configuration received from the IAB-donor-CU during the previous IAB-MT migration.

[0021] 2. The source parent node gNB-DU sends a UL RRC MESSAGE TRANSFER message to the IAB-donor-CU to convey the received measurement report.

[0022] 3. The IAB-donor-CU sends a UE CONTEXT SETUP REQUEST message to the target parent node gNB-DU to create a UE context and establish one or more bearers for the migrated IAB-MT. These bearers are used by the migrated IAB-MT for its own data and signaling services.

[0023] 4. The target parent node gNB-DU responds to the IAB-donor-CU with the UE CONTEXT SETUP RESPONSE message.

[0024] 5. The IAB-donor-CU sends a UE CONTEXT MODIFICATION REQUEST message to the source parent node gNB-DU, which includes the generated RRCReconfiguration message. The Transmission ActionIndicator in the UECONTEXT MODIFICATION REQUEST message indicates that data transmission to the migrating IAB-node should be stopped.

[0025] 6. The source parent node gNB-DU forwards the received RRCReconfiguration message to the migrating IAB-MT.

[0026] 7. The source parent node gNB-DU responds to the IAB-donor-CU with the UE CONTEXT MODIFICATION RESPONSE message.

[0027] 8. Perform the random access (RA) procedure at the target parent node gNB-DU.

[0028] 9. Migrate IAB-MT and respond to the target parent node gNB-DU with the RRCReconfigurationComplete message.

[0029] 10. The target parent node gNB-DU sends a UL RRC MESSAGE TRANSFER message to the IAB-donor-CU to convey the received RRCReconfigurationComplete message. Additionally, uplink packets can be sent from the migrating IAB-MT, and these uplink packets are forwarded to the IAB-donor-CU via the target parent node gNB-DU. These downlink (DL) and uplink (UL) packets belong to the MT's own signaling and data services.

[0030] 11. The IAB-donor-CU configures BAP-layer routing entries and BH RLC channels on the target path between the migrating IAB-node and the target IAB-donor-DU. This step also includes assigning a Transport Network Layer (TNL) address that can be routed via the target IAB-donor-DU. These configurations can be performed at an earlier stage (e.g., immediately after step 3). The new TNL address is included in the RRCReconfiguration message at step 5.

[0031] 12. All F1-U tunnels and F1-C tunnels were switched to use the new TNL address of the migrated IAB node.

[0032] 13. The IAB-donor-CU sends a UE CONTEXT RELEASE COMMAND message to the source parent node gNB-DU.

[0033] 14. The source parent node gNB-DU releases the context of the migration IAB-MT and responds to the IAB-donor-CU with the UE CONTEXT RELEASECOMPLETE message.

[0034] 15. The IAB-donor-CU releases BAP routing entries and BH RLC channels on the source path. Migrating an IAB-node can also release the TNL address it used on the source path.

[0035] If the source and destination routes share a common node, it may not be necessary to release the BHRLC channels and BAP route entries for these nodes in step 15.

[0036] Steps 11, 12, and 15 are also executed for the descendant nodes of the migrated IAB-node, as follows:

[0037] - Descendant nodes switch to the new TNL address anchored in the target IAB-donor-DU. The IAB-donor-CU can send these addresses to the descendant nodes and release the old addresses via the appropriate Radio Resource Control (RRC) signaling.

[0038] - If necessary, the IAB-donor-CU configures the BH RLC channels, BAP-layer routing entries on the target path of the descendant node, and BHRLC channel mappings on the descendant node in the same manner as described in step 11 for migrating the IAB-node.

[0039] - The descendant node switches its F1-U and F1-C tunnels to the new TNL address anchored at the new IAB-donor-DU in the same manner as described in step 12 for migrating the IAB node.

[0040] Depending on the implementation, these steps can be performed after the IAB-node migration switchover or in parallel with the IAB-node migration switchover. In version 16, packets traveling along the UL direction that are lost during the migration process may be unrecoverable.

[0041] Upstream, packets traveling between the source parent node and the IAB-donor-CU can be transmitted even after the destination path has been established. Downlink data traveling in the source path can be discarded. This depends on the implementation. The IAB-donor-CU can determine downlink data that was not successfully transmitted on the return link based on the implementation.

[0042] Specific procedures for CU / DU split architectures are described in 3GPP TS 38.401. These procedures occur between the CU and DU (or between CU-CP and CU-UP if the CU is split into UP and CP functions). Specifically, as disclosed in Figure 8.9.2-1 of 3GPP TS 38.401, the procedures for establishing a bearer context on the F1-U in gNB-CU-UP may include:

[0043] 0. Bearer context establishment (e.g., after an SGNB ADDITION REQUEST message from the MeNB) is triggered in gNB-CU-CP.

[0044] 1. The gNB-CU-CP sends a BEARER CONTEXT SETUP REQUEST message to establish a bearer context in the gNB-CU-UP. This message contains uplink (UL) TNL address information for S1-U or NG-U, and downlink (DL) TNL address information for X2-U or Xn-U if necessary. For NG-RAN, the gNB-CU-CP determines the flow-to-DRB mapping and sends the generated SDAP and PDCP configurations to the gNB-CU-UP.

[0045] 2. gNB-CU-UP responds with a BEARER CONTEXT SETUP RESPONSE message, which contains UL TNL address information for F1-U and DL TNL address information for S1-U or NG-U, and, if necessary, UL TNL address information for X2-U or Xn-U.

[0046] Indirect data transmission via gNB-CU-UP for split bearer cannot be ruled out.

[0047] 3. Perform the F1 UE context establishment procedure to establish one or more bearers in the gNB-DU.

[0048] 4. gNB-CU-CP sends a BEARER CONTEXT MODIFICATION REQUEST message, which contains DL TNL address information for F1-U and PDCP states.

[0049] 5. gNB-CU-UP responds with a BEARER CONTEXT MODIFICATION RESPONSE message.

[0050] Furthermore, as disclosed in Figure 8.9.3.1-1 of 3GPP TS 38.401, the procedure initiated by gNB-CU-CP for releasing the bearer context on F1-U in gNB-CU-UP includes:

[0051] 0. Bearer context release (e.g., after an SGNB RELEASE REQUEST message from the MeNB) is triggered in gNB-CU-CP.

[0052] 1. gNB-CU-CP sends a BEARER CONTEXT MODIFICATION REQUEST message to gNB-CU-UP.

[0053] 2. gNB-CU-UP responds with a BEARER CONTEXT MODIFICATIONRESPONSE carrying the PDCP UL / DL state.

[0054] 3. Perform the F1 UE context modification procedure to stop data transmission for the UE. When to stop UE scheduling depends on the gNB-DU implementation.

[0055] Steps 1 through 3 are performed only when it is necessary to preserve the PDCP state of the bearer (e.g., for bearer type changes).

[0056] 4. gNB-CU-CP can receive UE CONTEXT RELEASE messages from MeNB during EN-DC operations, as described in Section 8.4.2.1.

[0057] 5 and 7. Perform the bearer context release procedure.

[0058] 6. Perform the F1 UE context release procedure to release the UE context in the gNB-DU.

[0059] As disclosed in Figure 8.9.3.2-1 of 3GPP TS 38.401, the process initiated by gNB-CU-UP to release the bearer context in gNB-CU-UP includes:

[0060] 0. For example, due to a local failure, the bearer context is released in gNB-CU-UP.

[0061] 1. The gNB-CU-UP sends a BEARER CONTEXT RELEASE REQUEST message to request the release of the bearer context in the gNB-CU-UP. This message may contain PDCP status.

[0062] 2.-5. If it is necessary to retain the PDCP state, the E1 bearer context modification and F1 UE context modification procedures are performed. The E1 bearer context modification procedure is used to convey data forwarding information to gNB-CU-UP. gNB-CU-CP can receive UE context release from MeNB.

[0063] 6. gNB-CU-CP sends a BEARER CONTEXT RELEASE COMMAND message to release the bearer context in gNB-CU-UP.

[0064] 7. gNB-CU-UP responds with BEARER CONTEXT RELEASE COMPLETE to acknowledge the release of the bearer context, which also includes data forwarding information.

[0065] 8. The F1 UE context release procedure can be executed to release the UE context in the gNB-DU.

[0066] As disclosed in 3GPP TS 37.340, Figure 8.9.4-1 of 3GPP TS 37.340 shows and discloses a procedure for inter-gNB handover involving gNB-CU-UP changes. This procedure includes:

[0067] 1. The source gNB-CU-CP sends a HANDOVER REQUEST message to the target gNB-CU-CP.

[0068] 2-4. Perform the bearer context establishment procedure as described in Section 8.9.2.

[0069] 5. The target gNB-CU-CP responds to the source gNB-CU-CP with a HANDOVER REQUEST ACKNOWLEDGE message.

[0070] 6. Perform the F1 UE context modification procedure to stop UL data transmission at gNB-DU and send a handover command to the UE.

[0071] 7-8. Perform a bearer context modification procedure (initiated by gNB-CU-CP) to enable gNB-CU-CP to retrieve the PDCPUL / DL state and exchange data forwarding information for the bearer.

[0072] 9. The source gNB-CU-CP sends an SN STATUS TRANSFER message to the target gNB-CU-CP.

[0073] 10-11. Perform the bearer context modification procedure as described in Section 8.9.2.

[0074] 12. Data forwarding from the source gNB-CU-UP to the destination gNB-CU-UP can be performed.

[0075] 13-15. Perform a path switching procedure to update the DL TNL address information used to navigate to the NG-U to the core network.

[0076] 16. The target gNB-CU-CP sends a UE CONTEXT RELEASE message to the source gNB-CU-CP.

[0077] 17. and 19. Perform the bearer context release procedure.

[0078] 18. Perform the F1 UE context release procedure to release the UE context in the source gNB-DU.

[0079] Figure 8.9.5-1 in 3GPP TS 37.340 discusses and illustrates the procedure for modifying the gNB-CU-UP within the gNB. This procedure includes:

[0080] 1. For example, based on a measurement report from the UE, a change to gNB-CU-UP is triggered in gNB-CU-CP.

[0081] 2-3. Perform the bearer context establishment procedure as described in Section 8.9.2.

[0082] 4. Perform the F1 UE context modification procedure to change the UL TNL address information used for F1-U for one or more bearers in gNB-DU.

[0083] 5-6. Perform the bearer context modification procedure (initiated by gNB-CU-CP) to enable gNB-CU-CP to retrieve the PDCP UL / DL status and exchange data forwarding information for the bearer.

[0084] 7-8. Perform the bearer context modification procedure as described in Section 8.9.2.

[0085] 9. It can perform data forwarding from the source gNB-CU-UP to the target gNB-CU-UP.

[0086] 10-12. Perform a path switching procedure to update the DL TNL address information used to navigate to the NG-U to the core network.

[0087] 13-14. Perform the bearer context release procedure (initiated by gNB-CU-CP) as described in Section 8.9.3.

[0088] The Xn procedures for mobility are described in 3GPP TS 38.423. The core messages / procedures and information elements for UE mobility are summarized below (these messages are referenced in the signaling diagram above).

[0089] A HANDOVER REQUEST message is sent from a source Next Generation Radio Access Network (NG-RAN) node to a target NG-RAN node to request resources to be prepared for handover. Therefore, the direction is from the source NG-RAN node to the target NG-RAN node. Table 1 discloses the elements of the HANDOVER REQUEST message.

[0090]

[0091]

[0092]

[0093]

[0094]

[0095]

[0096] Table 1

[0097] In Table 1, CGI refers to Cell Global Identifier, and E-UTRA refers to Evolved Universal Terrestrial Radio Access. GUAMI refers to Globally Unique AMF ID.

[0098] The HANDOVER REQUEST ACKNOWLEDGE message is sent by the target NG-RAN node to notify the source NG-RAN node of the resources prepared at the target. Therefore, the direction is from the target NG-RAN node to the source NG-RAN node. Table 2 discloses the elements of the HANDOVER REQUEST ACKNOWLEDGE message.

[0099]

[0100]

[0101]

[0102] Table 2

[0103] The HandoverCommand (from 3GPP TS 38.331) is used to transmit handover commands generated by the target gNB. Therefore, the direction is from the target gNB to the source gNB / source RAN. The HandoverCommand is as follows:

[0104] HandoverCommand message

[0105] -- ASN1START

[0106] -- TAG-HANDOVER-COMMAND-START

[0107] HandoverCommand ::= SEQUENCE {

[0108] criticalExtensions CHOICE {

[0109] c1 CHOICE{

[0110] handoverCommand HandoverCommand-IEs,

[0111] spare3 NULL, spare2 NULL, spare1 NULL

[0112] },

[0113] criticalExtensionsFuture SEQUENCE {}

[0114] }

[0115] }

[0116] HandoverCommand-IEs ::= SEQUENCE {

[0117] handoverCommandMessage OCTET STRING (CONTAININGRRCReconfiguration),

[0118] nonCriticalExtension SEQUENCE {}OPTIONAL

[0119] }

[0120] -- TAG-HANDOVER-COMMAND-STOP

[0121] -- ASN1STOP

[0122] HandoverCommand (Toggle Command) Field Description The HandoverCommand message contains an RRCReconfiguration message generated by the target gNB (full) for performing a switch within the NR or switching to the NR.

[0123] The HANDOVER PREPARATION FAILURE message is sent by the target NG-RAN node to notify the source NG-RAN node that the handover preparation has failed. Therefore, the direction is from the target NG-RAN node to the source NG-RAN node. Table 4 discloses the elements of the HANDOVER PREPARATION FAILURE message.

[0124]

[0125]

[0126] Table 4

[0127] The HANDOVER CANCEL message is sent from the source NG-RAN node to the target NG-RAN node to cancel the ongoing handover. Therefore, the direction is from the source NG-RAN node to the target NG-RAN node. Table 5 discloses the elements of the HANDOVER CANCEL message.

[0128]

[0129] Table 5

[0130] The PDU Session Resources To Be Setup List (IE) contains information related to the PDU session resources used in UE context transmissions between NG-RAN nodes, as disclosed in Table 6.

[0131]

[0132]

[0133]

[0134]

[0135] Table 6

[0136] The PDU Session Resources Admitted List (IE) contains information related to PDU session resources to report the success of PDU session resource establishment, as disclosed in Table 7.

[0137]

[0138]

[0139]

[0140]

[0141] Table 7

[0142] The PDU Session Resources Not Admitted List contains a list of PDU session resources that are not permitted to be added to or modified, as disclosed in Table 8.

[0143]

[0144]

[0145] Table 8

[0146] The QoS Flow Identifier (IE) identifies QoS flows within a PDU session. It is specified in 3GPP TS23.501 and its definition and usage are shown in Table 9.

[0147]

[0148] Table 9

[0149] F1 signaling and procedures are described in 3GPP TS 38.473 and are summarized below.

[0150] The INITIAL UL RRC MESSAGE TRANSFER message is sent by the gNB-DU to transmit the initial Layer 3 message to the gNB-CU via the F1 interface. Therefore, the direction is from the gNB-DU to the gNB-CU. Table 10 discloses the elements of the INITIAL UL RRC MESSAGE TRANSFER message.

[0151]

[0152]

[0153]

[0154] Table 10

[0155] In Table 10, C-RNTI refers to the cell-specific radio network temporary identifier.

[0156] The DL RRC MESSAGE TRANSFER message is sent by the gNB-CU to transmit Layer 3 messages to the gNB-DU via the F1 interface. Therefore, the direction is from the gNB-CU to the gNB-DU. Table 11 discloses the elements of the DL RRC MESSAGE TRANSFER message.

[0157]

[0158]

[0159]

[0160]

[0161] Table 11

[0162] As used in this article, PLMN refers to Public Land Mobile Network, and PLMNID refers to PLMN identifier. RRM refers to Radio Resource Management.

[0163] The UL RRC MESSAGE TRANSFER is sent by the gNB-DU to transmit Layer 3 messages to the gNB-CU via the F1 interface. Therefore, the direction is from the gNB-DU to the gNB-CU. Table 12 discloses the elements of the UL RRC MESSAGE TRANSFER message.

[0164]

[0165]

[0166] Table 12

[0167] The RRC DELIVERY REPORT message is sent by the gNB-DU to notify the gNB-CU of the transmission status of the DLRRC message. Therefore, the direction is from the gNB-DU to the gNB-CU. Table 13 discloses the elements of the RRC DELIVERY REPORT message.

[0168]

[0169]

[0170] Table 13

[0171] Several challenges exist. For example, as mentioned above, 3GPP only standardized the migration process within the IAB CU. Given that inter-CU migration is a key feature of IAB, existing UE handover and IAB CU migration processes need to be enhanced to reduce service interruptions (due to IAB-node migration) and signaling load.

[0172] The technology has been used to transmit information / context regarding the migration of IAB nodes and all UEs and IAB nodes directly or indirectly served by the IAB nodes to the target CU. The target CU uses this information to perform appropriate licensing control. The target CU-CP responds to the HANDOVER REQUEST with a HANDOVER REQUEST ACK, which indicates a list of licensed and unlicensed PDU session resources (for each relevant UE / IAB node included in the handover request), which is essentially a list of QoS flows associated with each UE / IAB-MT.

[0173] Figure 7 The example IAB network scenario is shown where IAB 3 is migrating from donor CU1 to CU2 (and from parent node IAB1 to IAB2). Even though only the IAB-3 MT is actually changing its receive / transmit radio connection to the new parent node (IAB-2 DU), all UEs and IAB nodes directly or indirectly served by IAB-3 must receive a handover command (i.e., an RRC reconfiguration message containing reconfigurationWithSync) to change the security key when relocating their context, even if they are still connected to the same IAB node as before (3GPP security specifications mandate that the security key be changed whenever the PDCP termination point changes).

[0174] Currently, there is no designated group handover procedure, so it is unclear how and when handover commands are sent to each IAB-MT and UE. This is particularly problematic when the migrating IAB node is not a leaf node (i.e., when it serves other IAB nodes under it). Summary of the Invention

[0175] Certain aspects of this disclosure and its embodiments may provide solutions to these or other challenges. For example, a particular embodiment processes the sending of handover commands to the MTs and UEs of IAB nodes via signals, where the MTs and UEs of these IAB nodes are affected by the integrated access and wireless backhaul (IAB) handover of the parent IAB node during inter-Center Unit (CU) migration.

[0176] According to some embodiments, a method is performed by the target CU during a handover of a migration node from a source central unit (CU) and a source distributed unit (DU) to a target CU and a target DU. The method includes sending a first handover command via the target DU to the migration node for handing over at least one child node of the migration node from the source CU and source DU to the target CU and target DU.

[0177] According to some embodiments, a method is performed by a migration node during a handover from source CUs and source DUs to target CUs and target DUs. The method includes: receiving a first handover command from the target CU via the source CU. The first handover command is used to switch at least one child node of the migration node from the source CUs and source DUs to the target CUs and target DUs. The migration node sends the message to at least one child node.

[0178] According to some embodiments, a method is performed by a migration node during a handover from source CUs and source DUs to target CUs and target DUs. The migration node is a child node of a parent migration node and is the parent node of at least one additional child node. The method includes: receiving a first handover command from the target CU via the parent migration node. The first handover command is for a handover being performed together with the migration node from source CUs and source DUs to at least one additional child node of the target CU and target DU. The migration node sends the message to at least one additional child node of the migration node.

[0179] According to some embodiments, the target CU includes processing circuitry configured to send a first handover command via the target DU to the migration node during a handover from the source CU and source DU to the target CU and target DU.

[0180] According to some embodiments, the migration node includes processing circuitry configured to receive a first handover command from the target CU via the source CU during a handover from the source CU and source DU to the target CU and target DU. The first handover command is used to switch at least one child node of the migration node from the source CU and source DU to the target CU and target DU. The processing circuitry is configured to send the message to at least one child node.

[0181] According to some embodiments, a migration node includes processing circuitry configured to operate during a handover from source CUs and source DUs to target CUs and target DUs. The migration node is a child node of a parent migration node and is the parent node of at least one additional child node. The processing circuitry is configured to receive a first handover command from the target CU via the parent migration node. This first handover command is for use with the migration node in the handover from source CUs and source DUs to at least one additional child node of the target CU and target DU. The processing circuitry is configured to send this message to at least one additional child node of the migration node.

[0182] Certain embodiments may provide one or more of the following technical advantages. For example, a particular embodiment includes signaling enhancements to facilitate handover between the IAB node and its associated UE and IAB node (specifically, regarding the transmission of handover commands to the IAB-MT and UE). This particular embodiment does so in such an optimal manner that it eliminates the need to send handover commands to each UE and IAB node individually, thereby reducing the total handover / relocation latency of the IAB node and its associated UE, and potentially preventing performance degradation of active services for the associated UE.

[0183] Other advantages may be apparent to those skilled in the art. Some embodiments may lack the advantages described, or may have some or all of the advantages described. Attached Figure Description

[0184] To gain a more complete understanding of the disclosed embodiments, their features, and advantages, the following description is now taken in conjunction with the accompanying drawings, in which:

[0185] Figure 1 A high-level architecture diagram of an example IAB network is shown;

[0186] Figure 2 The baseline user plane protocol stack for IAB is shown;

[0187] Figure 3 The baseline control plane protocol stack for IAB is shown;

[0188] Figure 4 An example functional diagram of the BAP sublayer is shown;

[0189] Figure 5 Examples of some possible IAB-node migration scenarios are shown, listed in order of complexity.

[0190] Figure 6 The example topology adaptation process within the IAB CU is shown;

[0191] Figure 7 An example IAB network scenario is shown;

[0192] Figure 8A and Figure 8B An example diagram of signaling used for switching commands according to certain embodiments is shown;

[0193] Figure 9 An example wireless network according to certain embodiments is shown;

[0194] Figure 10 An example network node according to some embodiments is shown;

[0195] Figure 11 An example wireless device according to certain embodiments is shown;

[0196] Figure 12 An example user device according to certain embodiments is shown;

[0197] Figure 13 A virtualized environment is shown that, according to certain embodiments, functionality implemented by some embodiments can be virtualized;

[0198] Figure 14 A telecommunications network connected to a host computer via an intermediate network, according to certain embodiments, is shown;

[0199] Figure 15 A general block diagram of a host computer communicating with a user equipment via a base station through a partially wireless connection, according to some embodiments, is shown.

[0200] Figure 16 A method implemented in a communication system according to one embodiment is shown;

[0201] Figure 17 Another method implemented in a communication system according to one embodiment is shown;

[0202] Figure 18 Another method implemented in a communication system according to one embodiment is shown;

[0203] Figure 19 Another method implemented in a communication system according to one embodiment is shown;

[0204] Figure 20 A method performed by the target CU during a handover from the source CU and source DU to the target CU and target DU, according to certain embodiments, is illustrated.

[0205] Figure 21 An example virtual device according to certain embodiments is shown;

[0206] Figure 22 The method performed by the migration node during a handover from source CU and source DU to target CU and target DU, according to certain embodiments, is illustrated.

[0207] Figure 23 Another example virtual device according to certain embodiments is shown;

[0208] Figure 24 The following methods, according to certain embodiments, are illustrated, performed by a migration node during a handover from source CU and source DU to target CU and target DU; and

[0209] Figure 25 Another example virtual device according to certain embodiments is shown. Detailed Implementation

[0210] Some embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. However, other embodiments are included within the scope of the subject matter disclosed herein, and the disclosed subject matter should not be construed as being limited to the embodiments set forth herein; rather, these embodiments are provided by way of example only to convey the scope of the subject matter to those skilled in the art.

[0211] Generally, unless explicitly stated and / or implied from the context, all terms used herein shall be interpreted according to their common meaning in the relevant art. Unless otherwise expressly stated, all references to “an element, device, component, apparatus, step, etc.” shall be openly interpreted as referring to at least one instance of an element, device, component, apparatus, step, etc. The steps of any method disclosed herein need not be performed in the exact order disclosed, unless a step is explicitly described as occurring after or before another step and / or it is implied that a step must occur after or before another step. Where appropriate, any feature of any embodiment disclosed herein may be applied to any other embodiment. Similarly, any advantage of any embodiment may be applied to any other embodiment, and vice versa. Further objects, features, and advantages of the appended embodiments will become apparent from the following description.

[0212] As described herein, inter-CU IAB node migration can be caused by, for example, radio link failure (RLF), load balancing, and IAB node mobility. These are non-limiting examples. The terms migration, handover, and mobility are used interchangeably, as are the terms “gNB-CU” and “donor-CU”, “CU-CP” and “CU”. All considerations for split donors (i.e., donor CUs) also apply to non-split donors (i.e., donor gNBs).

[0213] The term "gNB" applies to all its variations, such as "gNB", "en-gNB", etc. The term "UE / IAB node directly served by the migrated IAB node" refers to a UE / IAB node directly connected to the migrated IAB node. The term "UE / IAB node indirectly served by the migrated IAB node" means that the migrated IAB node is the ancestor node of the IAB node currently serving the UE or IAB node. The term "related UE / IAB node" refers to a UE / IAB node that is being directly / indirectly served by the migrated IAB node.

[0214] Although this document describes certain embodiments from the perspective of IAB networks, all embodiments (including those such as sending handover commands and reconfiguration completion messages via group signals (transmitted via messages similar to DL and UL RRC messages, respectively) are also applicable to non-IAB scenarios, such as in the case of CU / DU splitting, where the UE is directly connected to the DU.

[0215] Some embodiments disclosed herein involve signaling handover commands to the MTs and UEs of IAB nodes that are affected by the Integrated Access and Radio Backhaul (IAB) handover of the parent IAB node during inter-CU migration. Specifically, certain embodiments include a hierarchical or step-by-step approach, whereby the target CU prepares handover commands (i.e., RRC reconfiguration including reconfigurationWithSync) for each relevant UE and IAB-MT, but includes only the handover command for the IAB-MT in the handover request confirmation message. After the handover of the IAB-MT is completed, the target CU then sends an F1-AP message, which includes all handover commands for the UEs under the IAB node that have just been handed over, as well as the handover command for the child IAB-MT. The same process is applied when the child IAB-MT has been handed over, until all hops have been addressed and all UEs and IAB-MTs have been handed over.

[0216] Figure 8A and Figure 8B Example signaling diagrams of handover commands according to certain embodiments disclosed herein are shown. For example, according to certain embodiments, a target CU or target donor-CU 60 in the IAB network (which serves as a candidate donor node for IAB node 70 (migrating IAB node) and provides connectivity for UEs 80a, 80b, 80c, 80d) performs one or more of the following steps:

[0217] 1. Receive a HANDOVER REQUEST-like message (an enhanced version of the traditional Xn message or a new message for IAB handover) from the source CU or source donor CU 90, which includes the context of the first migration IAB node and UEs 80a to 80d directly or indirectly served by the first migration IAB node and IAB node 95.

[0218] 2. Perform license control on the UE and IAB nodes included in the handover request.

[0219] 3. Prepare handover commands (i.e., synchronized RRC reconfiguration) for each UE and IAB node affected by the migration. For Figure 7 Example scenarios include MT for IAB3 and IAB4, as well as UEs a, b, c, and e.

[0220] 4. Prepare and send a message similar to HANDOVER REQUEST ACKNOWLEDGE (an enhanced version of the traditional Xn message or a new message for IAB handover) to the source CU. The HANDOVER REQUEST ACKNOWLEDGE message includes a list of permitted and unpermitted PDU session resources associated with the relevant UE and IAB node, and contains a HandoverCommand for the MT of the first migrating IAB node, which directly or indirectly serves all UEs and other IAB nodes included in the HANDOVER REQUEST. Figure 7 In the example scenario, the message only includes the HandoverCommand for IAB3-MT.

[0221] Applying traditional handover principles directly to this scenario will result in the target CU including all handover commands of all UEs / IAB nodes that are being served directly or indirectly by the IAB node in a separate message (i.e., one HandoverCommand for each relevant UE / MT, each sent in a separate HANDOVER REQUEST ACKNOWLEDGE message).

[0222] 5. Receive the RRC reconfiguration complete message from the MT (IAB-3 MT) of the migrated IAB node.

[0223] 6. Establish / relocate the F1 connection between the IAB node and the first network node.

[0224] 7. Use messages similar to F1-AP DL RRC transmission for UE / IAB nodes directly under the migrated IAB node (e.g., Figure 7 In the scenario, UEs (a, b, c, and IAB4-MT) send prepared handover commands.

[0225] In some embodiments, traditional messages are used. This allows a single message to be sent for each UE and sub-IAB node serving the service.

[0226] In some embodiments, the F1-AP DL RRC transmission message is enhanced or new messages are introduced (e.g., F1-AP IABDL RRC transmission message, F1-AP group DL RRC transmission message) to include several RRC messages going to several UEs / IAB-MTs (i.e., including the F1-AP UE / IAB-MT identifier and the corresponding handover command, i.e., including the RRC reconfiguration with reconfigurationWithSync).

[0227] • Additionally, a group RRC transmission status request can be indicated in the group DL transmission message.

[0228] According to some embodiments, when the DU has successfully sent a message to the UE (from the perspective of the lower layer, i.e., PHY-MAC-RLC), in the CU / DU separation architecture, the DU sends the transmission status to the CU, and the reconfiguration completion message from the UE indicates that the UE has successfully decoded / compiled / applied the RRC message.

[0229] 8. In the hierarchical approach, each sub-IAB node to which the switching command was sent in step 7 is considered a migrating IAB node.

[0230] 9. Repeat steps 5 through 8 for each IAB node considered a migrated IAB node in step 8. For each hop / layer of the IAB network, and until all UEs and IAB nodes directly or indirectly served by the first migrated IAB node have been correctly switched over (i.e., each ready-to-send command is sent to each UE / IAB-MT, the F1 connection of each directly / indirectly served IAB node is relocated to the target CU, and a reconfiguration completion message corresponding to each switch command is received). For the step corresponding to step 5 (i.e., receiving the completion message):

[0231] In some embodiments, each UE / IAB-MT under the migrated IAB node receives the RRC reconfiguration complete message in a separate UL RRC transport message, just as in the traditional CU / DU split architecture.

[0232] In some embodiments, a modified or newly defined similar UL RRC transport message is received, which includes an RRC reconfiguration completion message for more than one UE or IAB-MT (up to all UEs / IAB-MTs under the migrated IAB node).

[0233] In some embodiments, instead of waiting for a completion message from the IAB-MT before sending a handover command corresponding to the UE / sub-IAB node under the IAB node, receiving the RRC transmission status corresponding to the handover command of the MT is regarded as a trigger for preparing to send a group DL transmission message to the IAB node.

[0234] Some other embodiments include steps for migrating an IAB node from a source CU or a source donor CU to a target CU or a target donor CU. For example, according to some embodiments, these steps may include one or more of the following:

[0235] 1. Receive F1-AP messages from the target CU via the source CU. These messages contain handover commands for a large number of UEs and sub-IAB nodes served by the migrated IAB nodes (i.e., UE / IAB-MT identifiers and handover commands, including RRC reconfiguration with reconfigurationWithSync). The F1-AP message is:

[0236] An enhanced version of the oF1-AP DL RRC transmission message, or

[0237] o New messages introduced for this group of signaling (e.g., F1-AP IAB DL RRC transmission message, F1-AP group DL RRC transmission message, etc.).

[0238] 2. Forward the handover command to the corresponding UE / sub-IAB-MT.

[0239] 3. Receive the RRC reconfiguration complete message from each UE / sub-IAB-MT.

[0240] 4. Transmit an RRC reconfiguration complete message to the target CU.

[0241] In some embodiments, each message is transmitted using a separate conventional F1-AP UL RRC transmission message.

[0242] In certain embodiments, for example, the traditional F1-AP UL RRC transport message is enhanced or new F1-AP messages are defined (e.g., F1-AP IAB UL RRC transport message, F1-AP group UL RRC transport message) for RRC reconfiguration completion messages that include a large number of UEs / sub-IAB-MTs (up to all UEs / sub-IAB-MTs directly served by the migrated IAB node).

[0243] • Migrating IAB nodes can wait to receive a completion message from each of their UEs / sub-IAB-MTs before generating group UL RRC transmission messages.

[0244] • The migration IAB node waits for a certain duration based on a configured timer value (e.g., based on the network implementation specified in the standard, via OAM configuration, etc.) and includes all completion messages that the migration IAB node has received during that time in the group UL RRC transmission message (completion messages received after that time may be sent one by one, or the IAB node may wait for another duration equivalent to the configured timer or another timer value and compile another group of messages, etc.).

[0245] In some embodiments, group RRC transmission status messages are sent in a manner similar to step 4 described above. For example, if the received group DL RRC transmission message includes a request for a group RRC transmission status indication, the IAB node will send a group RRC transmission status message aggregating the transmission status of each relevant UE / IAB-MT. The same considerations can be made for group UL RRC transmission messages (i.e., waiting for all RRC messages of all UEs / IAB-MTs to be correctly sent before compiling the group transmission status message, waiting for a certain period of time, etc.).

[0246] The group signaling enhancements mentioned in the above embodiments that carry information to / from multiple UEs and IAB-MT (e.g., messages similar to modified or new F1AP DL / UL RRC transmissions) can be generalized to carry any other messages (e.g., non-handover RRC messages, i.e., messages that do not contain reconfigurationWithSync, or even non-RRC messages similar to NAS messages). Furthermore, although the examples described herein are for IAB scenarios, this concept can be reused even in non-IAB scenarios (e.g., CU / DU split architecture where the UE is directly under the DU) to achieve effective group signaling via non-UE associated messages, instead of sending messages to / from each UE individually.

[0247] for Figure 7 The handover scenario illustrated below is given by example in the signaling diagram. In the illustrated signaling diagram, the "+HO command to IAB3-MT" refers to the content (as an octet string) within the "Target NG-RAN node To Source NG-RAN node Transparent Container" IE of the message. The DL RRC transmission message sent from CU1 to IAB1 is also a conventional DL RRC transmission message. The "+HO command to IAB3-MT" refers to the content (as an octet string) within the "RRC-Container" IE of the message.

[0248] The following are example messages used in some embodiments. One example message is a new, non-UE-associated F1APIAB DL RRC MESSAGE TRANSFER message carrying HandoverCommands for multiple UEs / IAB-MTs. In certain embodiments, DL RRC messages for the associated UE and IAB-MT are carried as items in the same unified list within the F1APIAB DL RRC MESSAGE TRANSFER message (the examples below refer to this embodiment). In some embodiments, separate lists exist within the F1APIAB DL RRC MESSAGE TRANSFER message for the associated UE and associated IAB-MT.

[0249] Another example is a new, non-UE-associated F1AP IAB UL RRC MESSAGE TRANSFER message, which carries RRCReconfigurationComplete messages from multiple UEs / IAB-MTs. In a particular embodiment, the UL RRC messages for the relevant UE and IAB-MT are carried as items in the same unified list within the F1AP IAB UL RRC MESSAGE TRANSFER message (the example below refers to this embodiment). In a particular embodiment, a separate list exists within the F1AP IAB UL RRC MESSAGE TRANSFER message for the relevant UE and the relevant IAB-MT.

[0250] Another example is the new F1AP IAB RRC Delivery Report, which carries the RRC DL message delivery status for one or more IAB-MTs and / or UEs. This message can carry a delivery status indication for each relevant IAB-MT and / or UE individually, or it can carry a single IE indicating that all DL RRC messages have been successfully delivered.

[0251] The information carried in this message may only pertain to the UE and IAB-MT directly served by the IAB node that receives the F1AP message.

[0252] The IAB DL RRC MESSAGE TRANSFER is a non-UE-related message sent by the IAB-donor-CU to transmit Layer 3 messages involving one or more IAB-MTs and / or UEs directly served by the IAB-DU. The message direction is from the IAB-donor-CU to the IAB-DU. However, as mentioned above, in non-IAB cases, this message can be generalized to be from any CU to any DU. This also applies to all the example messages described above.

[0253] Table 14 summarizes the elements of the example IAB DL RRC MESSAGE TRANSFER.

[0254]

[0255]

[0256]

[0257]

[0258] Table 14

[0259] The Group RRC Delivery Status Request Required IE informs the DU whether a group RRC delivery status indication is preferred. This IE can serve as an alternative to the RRC Delivery Status Request IE (which is per UE / MT). For example, if all deliveries are OK, a group confirmation can be used instead of a single confirmation.

[0260] Some IEs (e.g., Additional Radio Resource Management (RRM) Policy Index) can be signaled at the top level (i.e., the same value for all UEs / IAB-MT).

[0261] The IAB UL RRC MESSAGE TRANSFER (non-UE associated message) is sent by the IAB-DU to transmit Layer 3 messages involving one or more IAB-MTs and / or UEs directly served by the IAB-DU to the IAB-donor-CU. The message direction is from the IAB-DU to the IAB-donor-CU. Table 15 summarizes the elements of an example IAB UL RRC MESSAGE TRANSFER (non-UE associated message).

[0262]

[0263]

[0264]

[0265] Table 15

[0266] The IAB RRC DELIVERY REPORT message is sent by the IAB-DU to inform the IAB-donor-CU about the delivery status of DL RRC messages for one or more IAB-MTs and / or UEs directly served by the IAB-DU. The message is sent from the IAB-DU to the IAB-donor-CU. Table 16 summarizes the elements of a sample IAB RRC DELIVERY REPORT message.

[0267]

[0268]

[0269] Table 16

[0270] Figure 9 Wireless networks according to some embodiments are illustrated. While the subject matter described herein can be implemented using any suitable components in any suitable type of system, the embodiments disclosed herein pertain to wireless networks (e.g., Figure 9 The example wireless network shown is described below. For simplicity, Figure 9The wireless network depicted only includes network 106, network nodes 160 and 160b, and WD 110. In practice, the wireless network may also include any additional elements suitable for supporting communication between wireless devices or between a wireless device and another communication device (e.g., a landline telephone, a service provider, or any other network node or terminal device). Among the components shown, network node 160 and wireless device (WD) 110 are depicted in additional detail. The wireless network can provide communication and other types of services to one or more wireless devices to facilitate access to and / or use of services provided by or via the wireless network.

[0271] Wireless networks can include any type of communications, telecommunications, data, cellular and / or radio networks or other similar systems, and / or interface with any type of communications, telecommunications, data, cellular and / or radio networks or other similar systems. In some embodiments, a wireless network can be configured to operate according to a specific standard or other type of predefined rules or procedures. Thus, specific embodiments of a wireless network can implement communication standards such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, or 5G standards; Wireless Local Area Network (WLAN) standards, such as the IEEE 802.11 standard; and / or any other suitable wireless communication standards, such as Global Microwave Access Interoperability (WiMax), Bluetooth, Z-Wave, and / or ZigBee standards.

[0272] Network 106 may include one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTN), packet data networks, optical networks, wide area networks (WAN), local area networks (LAN), wireless local area networks (WLAN), wired networks, wireless networks, metropolitan area networks, and other networks to enable communication between devices.

[0273] Network node 160 and WD 110 include various components described in more detail below. These components work together to provide network node and / or wireless device functionality, such as providing wireless connectivity in a wireless network. In different embodiments, the wireless network may include any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and / or any other components that can facilitate or participate in the communication of data and / or signals (whether via wired or wireless connections).

[0274] Figure 10Example network nodes according to certain embodiments are shown. As used herein, a network node refers to a device capable of, configured, arranged, and / or operable to communicate directly or indirectly with wireless devices and / or with other network nodes or devices in a wireless network to enable and / or provide wireless access to the wireless devices and / or perform other functions (e.g., management) in the wireless network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points) and base stations (BSs) (e.g., radio base stations, NodeBs, evolved NodeBs (eNBs), and NR NodeBs (gNBs)). Base stations can be classified based on the coverage they provide (or in other words, based on their transmit power levels), and thus they can also be referred to as femtocells, picocells, microcells, or macrocells. A base station can be a relay node or a relay donor node controlling a relay. A network node can also include one or more (or all) portions of a distributed radio base station, such as a centralized digital unit and / or a remote radio unit (RRU), sometimes referred to as a remote radio headend (RRH). Such a remote radio unit may or may not be integrated with an antenna as an antenna-integrated radio. A portion of a distributed radio base station can also be referred to as a node in a distributed antenna system (DAS). Other examples of network equipment include multi-standard radio (MSR) equipment (e.g., an MSR BS), network controllers (e.g., a radio network controller (RNC) or base station controller (BSC)), base transceiver stations (BTS), transport points, transport nodes, multi-cell / multicast coordination entities (MCEs), core network nodes (e.g., mobile switching centers (MSCs), mobility management entities (MMEs)), operations and maintenance (O&M) nodes, operations support system (OSS) nodes, self-optimizing network (SON) nodes, location nodes (e.g., evolved servicing mobile location centers (E-SMLCs)), and / or minimized-driven testing (MDTs)). As another example, a network node can be a virtual network node, as described in more detail below. However, more generally, a network node can represent any suitable device (or group of devices) that is capable of, configured, deployed, and / or operable to enable and / or provide access to a wireless communication network for wireless devices, or to provide some service to wireless devices already connected to the wireless network.

[0275] exist Figure 10 In this network node 160, processing circuitry 170, device-readable medium 180, interface 190, auxiliary equipment 184, power supply 186, power supply circuitry 187, and antenna 162 are included. Although Figure 10The network node 160 shown in the example wireless network can represent a device including a combination of the hardware components shown, but other embodiments may include network nodes with different combinations of components. It should be understood that a network node includes any suitable combination of hardware and / or software required to perform the tasks, features, functions, and methods disclosed herein. Furthermore, although the components of network node 160 are depicted as a single box within a larger box or nested within multiple boxes, in practice, a network node may include multiple different physical components constituting a single illustrated component (e.g., device-readable medium 180 may include multiple separate hard disk drives and multiple RAM modules).

[0276] Similarly, network node 160 may consist of multiple physically separate components (e.g., Node B components and RNC components, BTS components and BSC components, etc.), each with its own respective components. In some scenarios where network node 160 includes multiple separate components (e.g., BTS and BSC components), one or more of these separate components may be shared among multiple network nodes. For example, a single RNC may control multiple NodeBs. In such scenarios, each unique NodeB and RNC pair may be considered a single, separate network node in some cases. In some embodiments, network node 160 may be configured to support multiple Radio Access Technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate device-readable media 180 for different RATs), and some components may be reused (e.g., the same antenna 162 may be shared by the RATs). Network node 160 may also include multiple sets of various illustrated components for integrating different wireless technologies (e.g., GSM, Wideband Code Division Multiple Access (WCDMA), LTE, NR, WiFi, or Bluetooth wireless technologies) into network node 160. These wireless technologies can be integrated into the same or different chips or chipsets and other components within network node 160.

[0277] Processing circuitry 170 is configured to perform any determination, calculation, or similar operation (e.g., certain acquisition operations) described herein as being provided by a network node. These operations performed by processing circuitry 170 may include information acquired by processing circuitry 170 through processes such as: converting the acquired information into other information, comparing the acquired or converted information with information stored in the network node, and / or performing one or more operations based on the acquired or converted information, and making a determination based on the result of said processing.

[0278] Processing circuitry 170 may include a combination of one or more of the following: a microprocessor, controller, central processing unit, digital signal processor, application-specific integrated circuit, field-programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and / or coding logic, operable to provide network node 160 functionality, either alone or in combination with other network node 160 components (e.g., device-readable medium 180). For example, processing circuitry 170 may execute instructions stored in device-readable medium 180 or in memory within processing circuitry 170. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein. In some embodiments, processing circuitry 170 may include a system-on-a-chip (SoC).

[0279] In some embodiments, processing circuitry 170 may include one or more of radio frequency (RF) transceiver circuitry 172 and baseband processing circuitry 174. In some embodiments, RF transceiver circuitry 172 and baseband processing circuitry 174 may be on separate chips (or chipsets), boards, or units (e.g., radio units and digital units). In alternative embodiments, some or all of RF transceiver circuitry 172 and baseband processing circuitry 174 may be on the same chip or chipset, board, or unit group.

[0280] In some embodiments, some or all of the functions described herein as being provided by a network node, base station, eNB, or other such network device may be performed by processing circuitry 170, which executes instructions stored on device-readable medium 180 or memory within processing circuitry 170. In alternative embodiments, some or all of the functions may be provided by processing circuitry 170, for example, in a hard-wired manner, without executing instructions stored on separate or discrete device-readable media. In any of these embodiments, processing circuitry 170 may be configured to perform the described functions regardless of whether instructions stored on device-readable storage media are executed. The benefits provided by such functions are not limited to processing circuitry 170 or other components of network node 160, but are enjoyed as a whole by network node 160 and / or generally by end users and wireless networks.

[0281] Device-readable medium 180 may include any form of volatile or non-volatile computer-readable memory, including but not limited to permanent storage devices, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (e.g., hard disk), removable storage media (e.g., flash drives, compact discs (CDs), or digital video discs (DVDs)) and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory device that stores information, data, and / or instructions usable by processing circuitry 170. Device-readable medium 180 may store any suitable instructions, data, or information, including computer programs, software, applications including one or more of logic, rules, code, tables, etc., and / or other instructions executable by processing circuitry 170 and usable by network node 160. Device-readable medium 180 may be used to store any calculations performed by processing circuitry 170 and / or any data received via interface 190. In some embodiments, processing circuitry 170 and device-readable medium 180 may be considered integrated.

[0282] Interface 190 is used for wired or wireless communication of signaling and / or data between network node 160, network 106, and / or WD 110. As shown, interface 190 includes a port / terminal 194 for sending and receiving data to and from network 106, for example, via a wired connection. Interface 190 also includes radio front-end circuitry 192, which may be coupled to antenna 162, or in some embodiments, is part of antenna 162. Radio front-end circuitry 192 includes a filter 198 and an amplifier 196. Radio front-end circuitry 192 may be connected to antenna 162 and processing circuitry 170. Radio front-end circuitry 192 may be configured to modulate the signal communicating between antenna 162 and processing circuitry 170. Radio front-end circuitry 192 may receive digital data that will be transmitted wirelessly to other network nodes or WDs. Radio front-end circuitry 192 may use a combination of filter 198 and / or amplifier 196 to convert the digital data into a radio signal with suitable channel and bandwidth parameters. The radio signal can then be transmitted via antenna 162. Similarly, when receiving data, antenna 162 can collect radio signals, which are then converted into digital data by radio front-end circuitry 192. The digital data can then be passed to processing circuitry 170. In other embodiments, the interface may include different components and / or different combinations of components.

[0283] In some alternative embodiments, network node 160 may not include a separate radio front-end circuitry 192. Instead, processing circuitry 170 may include radio front-end circuitry and may be connected to antenna 162 without requiring a separate radio front-end circuitry 192. Similarly, in some embodiments, all or some of the RF transceiver circuitry 172 may be considered part of interface 190. In other embodiments, interface 190 may include one or more ports or terminals 194, radio front-end circuitry 192, and RF transceiver circuitry 172 (as part of a radio unit (not shown),) and interface 190 may communicate with baseband processing circuitry 174 (which is part of a digital unit (not shown)).

[0284] Antenna 162 may include one or more antennas or antenna arrays configured to transmit and / or receive wireless signals. Antenna 162 may be coupled to radio front-end circuitry 190 and may be any type of antenna capable of wirelessly transmitting and receiving data and / or signals. In some embodiments, antenna 162 may include one or more omnidirectional, sector, or planar antennas operable to transmit / receive radio signals between, for example, 2 GHz and 66 GHz. Omnidirectional antennas can be used to transmit / receive radio signals in any direction, sector antennas can be used to transmit / receive radio signals to / from devices within a specific area, and planar antennas can be line-of-sight antennas used to transmit / receive radio signals in a relatively straight line. In some cases, the use of more than one antenna may be referred to as MIMO. In some embodiments, antenna 162 may be separate from network node 160 and may be connected to network node 160 via an interface or port.

[0285] Antenna 162, interface 190, and / or processing circuitry 170 can be configured to perform any receive operation and / or certain acquire operation described herein as being performed by a network node. Any information, data, and / or signals can be received from a wireless device, another network node, and / or any other network device. Similarly, antenna 162, interface 190, and / or processing circuitry 170 can be configured to perform any transmit operation described herein as being performed by a network node. Any information, data, and / or signals can be transmitted to a wireless device, another network node, and / or any other network device.

[0286] Power supply circuit 187 may include or be coupled to power management circuitry and is configured to provide power to the components of network node 160 to perform the functions described herein. Power supply circuit 187 may receive power from power source 186. Power source 186 and / or power supply circuit 187 may be configured to provide power to various components of network node 160 in a manner suitable for the individual components (e.g., at the voltage and current levels required by each respective component). Power source 186 may be included in or outside power supply circuit 187 and / or network node 160. For example, network node 160 may be connected to an external power source (e.g., a power outlet) via input circuitry or an interface such as a cable, thereby supplying power to power supply circuit 187. As another example, power source 186 may include a power source in the form of a battery or battery pack, which is connected to or integrated into power supply circuit 187. The battery can provide backup power if the external power source fails. Other types of power sources, such as photovoltaic devices, may also be used.

[0287] Alternative embodiments of network node 160 may include more than Figure 10 Additional components of the components shown may be responsible for providing certain aspects of the functionality of the network node, including any of the functions described herein and / or any functionality required to support the subject matter described herein. For example, network node 160 may include a user interface device to allow information to be input into and output from network node 160. This can allow users to perform diagnostic, maintenance, repair, and other management functions on network node 160.

[0288] Figure 11An example wireless device 110 according to certain embodiments is illustrated. As used herein, a wireless device (WD) refers to a device capable of, configured to, arranged to, and / or operable to communicate wirelessly with network nodes and / or other wireless devices. Unless otherwise stated, the term WD may be used interchangeably with User Equipment (UE) herein. Wireless transmission may include sending and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for transmitting information over the air. In some embodiments, a WD may be configured to send and / or receive information without direct human interaction. For example, a WD may be designed to send information to the network in a predetermined schedule when triggered by an internal or external event or in response to a request from the network. Examples of WDs include, but are not limited to, smartphones, mobile phones, cellular phones, Voice over IP (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, game consoles or devices, music storage devices, playback devices, wearable terminal devices, wireless endpoints, mobile stations, tablet computers, portable computers, portable embedded devices (LEEs), portable-installed devices (LMEs), smart devices, wireless client devices (CPEs), and in-vehicle wireless terminal devices. A WD can, for example, support device-to-device (D2D) communication, vehicle-to-vehicle (V2V) communication, vehicle-to-infrastructure (V2I) communication, and vehicle-to-everything (V2X) communication by implementing 3GPP standards for sidelink communication, and in this case, can be referred to as a D2D communication device. As another specific example, in the Internet of Things (IoT) scenario, a WD can represent a machine or other device that performs monitoring and / or measurement and sends the results of such monitoring and / or measurement to another WD and / or network node. In this case, the WD can be a machine-to-machine (M2M) device, which in the 3GPP context can be referred to as an MTC device. As a concrete example, a WD can be a UE implementing the 3GPP Narrowband Internet of Things (NB-IoT) standard. Specific examples of such machines or devices are sensors, metering devices (e.g., power meters), industrial machines, or household or personal appliances (e.g., refrigerators, televisions, etc.), personal wearable devices (e.g., watches, fitness trackers, etc.). In other scenarios, a WD can refer to a vehicle or other device capable of monitoring and / or reporting its operational status or other functions associated with its operation. As described above, a WD can represent a wirelessly connected endpoint, in which case the device can be referred to as a wireless terminal. Furthermore, as described above, a WD can be mobile, in which case it can also be referred to as a mobile device or mobile terminal.

[0289] As shown in the figure, wireless device 110 includes an antenna 111, an interface 114, processing circuitry 120, a device-readable medium 130, a user interface device 132, auxiliary devices 134, a power supply 136, and a power circuit 137. WD 110 may include one or more of the components shown for various wireless technologies supported by WD 110 (e.g., GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, to name just a few). These wireless technologies may be integrated into a chip or chipset that is the same as or different from other components within WD 110.

[0290] Antenna 111 may include one or more antennas or antenna arrays configured to transmit and / or receive wireless signals and connected to interface 114. In some alternative embodiments, antenna 111 may be separate from WD 110 and may be connected to WD 110 via an interface or port. Antenna 111, interface 114, and / or processing circuitry 120 may be configured to perform any receive or transmit operations described herein as performed by a WD. Any information, data, and / or signals may be received from a network node and / or another WD. In some embodiments, radio front-end circuitry and / or antenna 111 may be considered as an interface.

[0291] As shown, interface 114 includes radio front-end circuitry 112 and antenna 111. Radio front-end circuitry 112 includes one or more filters 118 and amplifiers 116. Radio front-end circuitry 114 is connected to antenna 111 and processing circuitry 120 and is configured to modulate the signal transmitted between antenna 111 and processing circuitry 120. Radio front-end circuitry 112 may be coupled to antenna 111 or be a portion of antenna 111. In some embodiments, WD 110 may not include a separate radio front-end circuitry 112; instead, processing circuitry 120 may include radio front-end circuitry and may be connected to antenna 111. Similarly, in some embodiments, some or all of RF transceiver circuitry 122 may be considered part of interface 114. Radio front-end circuitry 112 can receive digital data that will be transmitted wirelessly to other network nodes or WD. Radio front-end circuitry 112 can use a combination of filters 118 and / or amplifiers 116 to convert the digital data into radio signals with suitable channel and bandwidth parameters. The radio signals can then be transmitted via antenna 111. Similarly, when receiving data, antenna 111 can collect radio signals, which are then converted into digital data by radio front-end circuitry 112. The digital data can then be passed to processing circuitry 120. In other embodiments, the interface may include different components and / or different combinations of components.

[0292] Processing circuitry 120 may include a combination of one or more of the following: a microprocessor, controller, central processing unit, digital signal processor, application-specific integrated circuit, field-programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and / or coding logic, operable to provide WD 110 functionality, either alone or in combination with other WD 110 components (e.g., device-readable medium 130). Such functionality may include providing any of the various wireless features or benefits discussed herein. For example, processing circuitry 120 may execute instructions stored in device-readable medium 130 or in memory within processing circuitry 120 to provide the functionality disclosed herein.

[0293] As shown in the figure, the processing circuit 120 includes one or more of an RF transceiver circuit 122, a baseband processing circuit 124, and an application processing circuit 126. In other embodiments, the processing circuit may include different components and / or different combinations of components. In some embodiments, the processing circuit 120 of the WD 110 may include a System-on-a-Chip (SOC). In some embodiments, the RF transceiver circuit 122, the baseband processing circuit 124, and the application processing circuit 126 may be on a separate chip or chipset. In alternative embodiments, a portion or all of the baseband processing circuit 124 and the application processing circuit 126 may be combined into a single chip or chipset, and the RF transceiver circuit 122 may be on a separate chip or chipset. In further alternative embodiments, a portion or all of the RF transceiver circuit 122 and the baseband processing circuit 124 may be on the same chip or chipset, and the application processing circuit 126 may be on a separate chip or chipset. In other alternative embodiments, a portion or all of the RF transceiver circuit 122, the baseband processing circuit 124, and the application processing circuit 126 may be combined in the same chip or chipset. In some embodiments, the RF transceiver circuit 122 may be part of the interface 114. The RF transceiver circuit 122 may modulate the RF signal for use by the processing circuit 120.

[0294] In some embodiments, some or all of the functions described herein as being performed by WD may be provided by processing circuitry 120, which executes instructions stored on device-readable medium 130, which in some embodiments may be computer-readable storage medium. In alternative embodiments, some or all of the functions may be provided by processing circuitry 120, for example, in a hard-wired manner, without executing instructions stored on separate or discrete device-readable storage media. In any of those particular embodiments, processing circuitry 120 may be configured to perform the described functions regardless of whether instructions stored on device-readable storage media are executed. The benefits provided by such functions are not limited to processing circuitry 120 or other components of WD 110, but are enjoyed as a whole by WD 110 and / or generally by end users and wireless networks.

[0295] Processing circuitry 120 may be configured to perform any determination, calculation, or similar operation (e.g., certain acquisition operations) described herein as being performed by WD. These operations performed by processing circuitry 120 may include processing information acquired by processing circuitry 120 by, for example, converting the acquired information into other information, comparing the acquired or converted information with information stored by WD 110, and / or performing one or more operations based on the acquired or converted information, and making a determination based on the result of said processing.

[0296] Device-readable medium 130 is operable to store computer programs, software, applications including one or more of logic, rules, code, tables, etc., and / or other instructions executable by processing circuitry 120. Device-readable medium 130 may include computer memory (e.g., random access memory (RAM) or read-only memory (ROM)), mass storage media (e.g., hard disk), removable storage media (e.g., CD or DVD), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory device storing information, data, and / or instructions usable by processing circuitry 120. In some embodiments, processing circuitry 120 and device-readable medium 130 may be considered integrated.

[0297] User interface device 132 can provide components that allow a human user to interact with WD 110. This interaction can take many forms, such as visual, auditory, tactile, etc. User interface device 132 is operable to produce outputs to the user and allow the user to provide inputs to WD 110. The type of interaction can vary depending on the type of user interface device 132 installed in WD 110. For example, if WD 110 is a smartphone, the interaction can be via a touchscreen; if WD 110 is a smart meter, the interaction can be via a screen providing a purpose (e.g., the number of gallons used) or a speaker providing an audible alarm (e.g., if smoke is detected). User interface device 132 can include input interfaces, devices, and circuitry, as well as output interfaces, devices, and circuitry. User interface device 132 is configured to allow information to be input into WD 110 and is connected to processing circuitry 120 to allow processing circuitry 120 to process the input information. User interface device 132 can include, for example, a microphone, proximity or other sensors, buttons / buttons, a touch display, one or more cameras, a USB port, or other input circuitry. User interface device 132 is also configured to allow information output from WD 110 and to allow processing circuitry 120 to output information from WD 110. User interface device 132 may include, for example, a speaker, display, vibration circuitry, USB port, headphone jack, or other output circuitry. By using one or more input and output interfaces, devices, and circuitry of user interface device 132, WD 110 can communicate with end users and / or wireless networks and allow them to benefit from the functionality described herein.

[0298] The auxiliary device 134 is operable to provide more specific functions that may not typically be performed by the WD. This may include dedicated sensors for measuring for various purposes, interfaces for additional types of communication such as wired communication, etc. The contents and types of components of the auxiliary device 134 may vary depending on the embodiment and / or scenario.

[0299] In some embodiments, power source 136 may be in the form of a battery or battery pack. Other types of power sources may also be used, such as an external power source (e.g., a power outlet), a photovoltaic device, or a battery cell. WD 110 may also include power circuitry 137 for supplying power from power source 136 to various parts of WD 110 that require power from power source 136 to perform any function described or indicated herein. In some embodiments, power circuitry 137 may include power management circuitry. Power circuitry 137 may additionally or alternatively be operable to receive power from an external power source; in this case, WD 110 may be connected to an external power source (e.g., a power outlet) via input circuitry or an interface such as a power cable. In some embodiments, power circuitry 137 may also be operable to supply power from an external power source to power source 136. For example, this may be used for charging power source 136. Power circuitry 137 may perform any formatting, conversion, or other modifications on the power from power source 136 to suit the power supply for the various components of WD 110 being powered.

[0300] Figure 12 An embodiment of a UE according to the various aspects described herein is illustrated. As used herein, "User Equipment" or "UE" may not necessarily have the meaning of a "user" in the sense of a human user who owns and / or operates the relevant equipment. Alternatively, a UE may refer to a device intended to be sold to or operated by a human user but may not or initially be associated with a particular human user (e.g., a smart sprinkler controller). Alternatively, a UE may refer to a device not intended to be sold to or operated by an end user but may be associated with or operated for the benefit of a user (e.g., a smart power meter). UE 200 can be any UE identified by the 3rd Generation Partnership Project (3GPP), including NB-IoT UEs, Machine Type Communication (MTC) UEs, and / or Enhanced MTC (eMTC) UEs. Figure 12 As shown, UE 200 is an example of a WD configured for communication according to one or more communication standards (such as 3GPP's GSM, UMTS, LTE, and / or 5G standards). As previously stated, the terms WD and UE are used interchangeably. Therefore, although... Figure 12 This is for UE, but the components discussed in this article also apply to WD, and vice versa.

[0301] exist Figure 12In this embodiment, UE 200 includes processing circuitry 201 operatively coupled to an input / output interface 205, a radio frequency (RF) interface 209, a network connectivity interface 211, a memory 215 including random access memory (RAM) 217, read-only memory (ROM) 219, and a storage medium 221, a communication subsystem 231, a power supply 233, and / or any other component, or any combination thereof. The storage medium 221 includes an operating system 223, application programs 225, and data 227. In other embodiments, the storage medium 221 may include other similar types of information. Some UEs may use... Figure 12 This refers to all components shown, or only a subset of those components. The level of integration between components can vary from one UE to another. Furthermore, some UEs may contain multiple instances of components, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0302] exist Figure 12 In this embodiment, processing circuitry 201 can be configured to process computer instructions and data. Processor 201 can be configured to execute any sequential state machine containing machine instructions stored in memory as a machine-readable computer program, such as one or more hardware-implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logic and suitable firmware; one or more stored programs, a general-purpose processor (e.g., a microprocessor or digital signal processor (DSP)) and suitable software; or any combination thereof. For example, processing circuitry 201 may include two central processing units (CPUs). Data may be information in a form suitable for use by a computer.

[0303] In the depicted embodiments, the input / output interface 205 can be configured to provide a communication interface to an input device, an output device, or both input and output devices. The UE 200 can be configured to use an output device via the input / output interface 205. The output device can use an interface port of the same type as the input device. For example, a USB port can be used to provide input to and output from the UE 200. The output device can be a speaker, sound card, video card, display, monitor, printer, actuator, transmitter, smart card, another output device, or any combination thereof. The UE 200 can be configured to use an input device via the input / output interface 205 to allow a user to capture information into the UE 200. The input device can include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, digital camcorder, webcam, etc.), a microphone, a sensor, a mouse, a trackball, a directional keyboard, a touchpad, a scroll wheel, a smart card, etc. A presence-sensitive display can include a capacitive or resistive touch sensor to sense input from the user. Sensors can be, for example, accelerometers, gyroscopes, tilt sensors, force sensors, magnetometers, optical sensors, proximity sensors, another type of sensor, or any combination thereof. For example, input devices can be accelerometers, magnetometers, digital cameras, microphones, and optical sensors.

[0304] exist Figure 12 In this configuration, RF interface 209 can be configured to provide a communication interface to RF components such as transmitters, receivers, and antennas. Network connectivity interface 211 can be configured to provide a communication interface to network 243a. Network 243a may include wired and / or wireless networks, such as local area networks (LANs), wide area networks (WANs), computer networks, wireless networks, telecommunications networks, another similar network, or any combination thereof. For example, network 243a may include a Wi-Fi network. Network connectivity interface 211 can be configured to include receiver and transmitter interfaces for communicating with one or more other devices over the communication network according to one or more communication protocols (e.g., Ethernet, TCP / IP, SONET, ATM, etc.). Network connectivity interface 211 can implement receiver and transmitter functions suitable for the communication network link (e.g., optical, electrical, etc.). The transmitter and receiver functions may share circuit components or software, or alternatively, may be implemented separately.

[0305] RAM 217 can be configured to interface with processing circuitry 201 via bus 202 to provide storage or cache of data or computer instructions during the execution of software programs such as operating systems, applications, and device drivers. ROM 219 can be configured to provide computer instructions or data to processing circuitry 201. For example, ROM 219 can be configured to store invariant low-level system code or data for basic system functions such as basic input and output (I / O), startup, or reception of keystrokes from a keyboard, stored in non-volatile memory. Storage medium 221 can be configured to include memory such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), disk, optical disk, floppy disk, hard disk, removable magnetic tape, or flash drive. In one example, storage medium 221 can be configured to include operating system 223, application 225 such as a web browser application, widget or gadget engine or another application, and data file 227. Storage medium 221 can store any one or a combination of various operating systems for use by UE 200.

[0306] Storage medium 221 can be configured to include multiple physical drive units, such as redundant array of independent disks (RAID), floppy disk drives, flash memory, USB flash drives, external hard disk drives, thumb drives, pen drives, key drives, high-density digital versatile optical disc (HD-DVD) drives, internal hard disk drives, Blu-ray disc drives, holographic digital data storage (HDDS) disc drives, external mini dual in-line memory modules (DIMMs), synchronous dynamic random access memory (SDRAM), external micro DIMM SDRAM, smart card memory such as a user identification module or removable user identity (SIM / RUIM) module, other memory, or any combination thereof. Storage medium 221 can allow UE 200 to access computer-executable instructions, applications, etc., stored on transient or non-transient storage media to unload or upload data. Articles such as those utilizing communication systems can be tangibly embodied in storage medium 221, which may include device-readable media.

[0307] exist Figure 12In this configuration, processing circuitry 201 can be configured to communicate with network 243b using communication subsystem 231. Networks 243a and 243b can be one or more of the same networks or one or more different networks. Communication subsystem 231 can be configured to include one or more transceivers for communicating with network 243b. For example, communication subsystem 231 can be configured to include one or more remote transceivers for communicating with another device (e.g., another WD, UE) or a base station of a radio access network (RAN) capable of wireless communication according to one or more communication protocols (e.g., IEEE 802.2, CDMA, WCDMA, GSM, LTE, Universal Terrestrial Radio Access Network (UTRAN), WiMax, etc.). Each transceiver can include transmitter 233 and / or receiver 235 to implement transmitter or receiver functions suitable for the RAN link (e.g., frequency allocation, etc.). Furthermore, the transmitter 233 and receiver 235 of each transceiver can share circuit components, software, or firmware, or alternatively, can be implemented separately.

[0308] In the illustrated embodiment, the communication functions of the communication subsystem 231 may include data communication, voice communication, multimedia communication, short-range communication such as Bluetooth, near-field communication, location-based communication (such as the use of a Global Positioning System (GPS) for determining location), another similar communication function, or any combination thereof. For example, the communication subsystem 231 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. The network 243b may include wired and / or wireless networks, such as a local area network (LAN), a wide area network (WAN), a computer network, a wireless network, a telecommunications network, another similar network, or any combination thereof. For example, the network 243b may be a cellular network, a Wi-Fi network, and / or a near-field network. The power supply 213 may be configured to provide alternating current (AC) or direct current (DC) power to the components of the UE 200.

[0309] The features, benefits, and / or functions described herein may be implemented in one of the components of UE 200 or partitioned among multiple components of UE 200. Furthermore, the features, benefits, and / or functions described herein may be implemented in any combination of hardware, software, or firmware. In one example, communication subsystem 231 may be configured to include any of the components described herein. Additionally, processing circuitry 201 may be configured to communicate with any such component via bus 202. In another example, any such component may be represented by program instructions stored in memory, which, when executed by processing circuitry 201, perform the corresponding functions described herein. In another example, the functionality of any such component may be partitioned between processing circuitry 201 and communication subsystem 231. In yet another example, the non-computationally intensive functions of any such component may be implemented in software or firmware, and the computationally intensive functions may be implemented in hardware.

[0310] Figure 13 This is a schematic block diagram illustrating a virtualized environment 300, in which functionality implemented by some embodiments can be virtualized. In this context, virtualization means creating a virtual version of an apparatus or device that may include a virtualized hardware platform, storage devices, and network resources. As used herein, virtualization can be applied to nodes (e.g., virtualized base stations or virtualized radio access nodes) or devices (e.g., UEs, wireless devices, or any other type of communication device) or components thereof, and relates to an implementation in which at least a portion of functionality is implemented as one or more virtual components (e.g., through one or more applications, components, functions, virtual machines, or containers executing on one or more physical processing nodes in one or more networks).

[0311] In some embodiments, some or all of the functionality described herein may be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments 300 hosted on one or more hardware nodes 330. Furthermore, in embodiments where the virtual node is not a radio access node or does not require radio connectivity (e.g., a core network node), the network node may then be fully virtualized.

[0312] These functionalities can be implemented by one or more applications 320 (which may alternatively be referred to as software instances, virtual devices, network functions, virtual nodes, virtual network functions, etc.), one or more applications 320 being operable to implement some of the features, functions, and / or benefits of some embodiments disclosed herein. Applications 320 run in a virtualization environment 300, which provides hardware 330 including processing circuitry 360 and memory 390. Memory 390 contains instructions 395 executable by the processing circuitry 360, thereby enabling application 320 to provide one or more of the features, benefits, and / or functions disclosed herein.

[0313] The virtualization environment 300 includes general-purpose or special-purpose network hardware devices 330, which include one or more processors or processing circuitry 360, which may be commercial off-the-shelf (COTS) processors, application-specific integrated circuits (ASICs), or any other type of processing circuitry including digital or analog hardware components or special-purpose processors. Each hardware device may include memory 390-1, which may be non-permanent memory for temporarily storing instructions 395 or software executed by the processing circuitry 360. Each hardware device may include one or more network interface controllers (NICs) 370, also referred to as network interface cards, which include physical network interfaces 380. Each hardware device may also include non-transitory, permanent machine-readable storage media 390-2 in which the software 395 and / or instructions executable by the processing circuitry 360 are stored. The software 395 may include any type of software, including software for instantiating one or more virtualization layers 350 (also referred to as hypervisors), software for executing virtual machines 340, and software that allows them to perform the functions, features, and / or benefits described in relation to some embodiments described herein.

[0314] Virtual machine 340 includes virtual processing, virtual memory, virtual networking or interfaces, and virtual storage, and can be run by a corresponding virtualization layer 350 or hypervisor. Different embodiments of instances of virtual device 320 may be implemented on one or more of virtual machines 340, and these implementations may be made in different ways.

[0315] During operation, the processing circuitry 360 executes software 395 to instantiate a hypervisor or virtualization layer 350, which may sometimes be referred to as a virtual machine monitor (VMM). The virtualization layer 350 can present a virtual operating platform that appears as networked hardware of the virtual machine 340.

[0316] like Figure 13 As shown, hardware 330 can be a standalone network node with general or specific components. Hardware 330 may include antenna 3225 and may implement some functions through virtualization. Alternatively, hardware 330 may be part of a larger hardware cluster (e.g., in a data center or customer premises equipment (CPE)) where many hardware nodes work together and are managed by management and coordination (MANO) 3100, which in particular oversees the lifecycle management of application 320.

[0317] In some contexts, hardware virtualization is referred to as Network Functions Virtualization (NFV). NFV can be used to unify numerous network device types onto industry-standard high-capacity server hardware, physical switches, and physical storage that can reside in data centers and customer premises equipment (CPE).

[0318] In the context of NFV, virtual machine 340 can be a software implementation of a physical machine, and its running programs are executed as if they were running on a physical, non-virtualized machine. Each virtual machine 340, along with the portion of hardware 330 that executes that virtual machine (whether it is hardware dedicated to that virtual machine and / or hardware shared by that virtual machine and other virtual machines in virtual machine 340), forms a separate virtual network element (VNE).

[0319] Still within the context of NFV, a Virtual Network Function (VNF) is responsible for handling specific network functions running in one or more virtual machines 340 on top of the hardware network infrastructure 330, and corresponds to... Figure 13 Application 320.

[0320] In some embodiments, each of the one or more radio units 3200, including one or more transmitters 3220 and one or more receivers 3210, may be coupled to one or more antennas 3225. The radio unit 3200 may communicate directly with the hardware node 330 via one or more suitable network interfaces and may be used in conjunction with virtual components to provide radio capabilities to the virtual node, such as a radio access node or base station.

[0321] In some embodiments, the control system 3230 may be used to implement some signaling, and the control system 3230 may alternatively be used for communication between the hardware node 330 and the radio unit 3200.

[0322] Figure 14 A telecommunications network connected to a host computer via an intermediate network, according to some embodiments, is illustrated. (Refer to...) Figure 14 According to an embodiment, the communication system includes a telecommunications network 410 (e.g., a 3GPP-type cellular network), which includes an access network 411 (e.g., a radio access network) and a core network 414. The access network 411 includes multiple base stations 412a, 412b, and 412c (e.g., NB, eNB, gNB, or other types of wireless access points), each defining a corresponding coverage area 413a, 413b, or 413c. Each base station 412a, 412b, or 412c can be connected to the core network 414 via a wired or wireless connection 415. A first UE 491 located in coverage area 413c is configured to wirelessly connect to or be paged by the corresponding base station 412c. A second UE 492 located in coverage area 413a can wirelessly connect to the corresponding base station 412a. Although multiple UEs 491, 492 are shown in this example, the disclosed embodiments are equally applicable to situations where a single UE is in the coverage area or a single UE is connected to the corresponding base station 412.

[0323] Telecommunications network 410 is connected to host computer 430, which may be implemented as a standalone server, a cloud-based server, a distributed server, or as a processing resource within a server cluster. Host computer 430 may be owned or controlled by a service provider, or may be operated by or on behalf of the service provider. Connections 421 and 422 between telecommunications network 410 and host computer 430 may extend directly from core network 414 to host computer 430, or may pass through an optional intermediate network 420. Intermediate network 420 may be one or more of a public, private, or hosted network; intermediate network 420 (if any) may be a backbone network or the Internet; specifically, intermediate network 420 may include two or more subnetworks (not shown).

[0324] Figure 14 The communication system as a whole establishes a connection between the connected UEs 491 and 492 and the host computer 430. This connection can be described as an over-the-top (OTT) connection 450. The host computer 430 and the connected UEs 491 and 492 are configured to transmit data and / or signaling via the OTT connection 450 using access network 411, core network 414, any intermediate network 420, and possibly other infrastructure (not shown) as intermediaries. The participating communication devices through which the OTT connection 450 passes are unaware of the routes of uplink and downlink communications; in this sense, the OTT connection 450 can be transparent. For example, it may not notify or need to notify base station 412 of past routes of input downlink communications with data originating from host computer 430 to be forwarded (e.g., handed over) to the connected UE 491. Similarly, base station 412 does not need to know the future routes of uplink communications originating from UE 491 and heading towards the host computer 430.

[0325] Figure 15 A host computer is illustrated that communicates with a user equipment via a base station through a partially wireless connection, according to some embodiments. Reference will now be made to... Figure 15This section describes example implementations of the UE, base station, and host computer discussed in the preceding paragraphs according to embodiments. In communication system 500, host computer 510 includes hardware 515, which includes a communication interface 516 configured to establish and maintain wired or wireless connections with interfaces of different communication devices of communication system 500. Host computer 510 also includes processing circuitry 518, which may have storage and / or processing capabilities. In particular, processing circuitry 518 may include one or more programmable processors, application-specific integrated circuits, field-programmable gate arrays, or combinations of such devices (not shown) adapted to execute instructions. Host computer 510 also includes software 511, which is stored in or accessible by host computer 510 and executable by processing circuitry 518. Software 511 includes host application 512. Host application 512 is operable to provide services to a remote user (e.g., UE 530), which is connected via an OTT connection 550 terminated at UE 530 and host computer 510. When providing services to remote users, host application 512 can provide user data sent using OTT connection 550.

[0326] The communication system 500 also includes a base station 520 provided in the telecommunications system. The base station 520 includes hardware 525 enabling it to communicate with a host computer 510 and a UE 530. Hardware 525 may include: a communication interface 526 for establishing and maintaining wired or wireless connections with different communication devices of the communication system 500; and a radio interface 527 for establishing and maintaining connections with at least the coverage area served by the base station 520. Figure 15 The UE 530 (not shown in the image) has a wireless connection 570. The communication interface 526 can be configured to facilitate connection 560 to the host computer 510. Connection 560 can be direct, or it can be via the core network of the telecommunications system (…). Figure 15 (Not shown) and / or via one or more intermediate networks outside the telecommunications system. In the illustrated embodiment, the hardware 525 of base station 520 also includes processing circuitry 528, which may include one or more programmable processors, application-specific integrated circuits, field-programmable gate arrays, or combinations thereof (not shown) suitable for executing instructions. Base station 520 also has software 521 stored internally or accessible via an external connection.

[0327] The communication system 500 also includes the previously mentioned UE 530. Its hardware 535 may include a radio interface 537 configured to establish and maintain a wireless connection 570 with a base station serving the coverage area currently occupied by the UE 530. The hardware 535 of the UE 530 also includes processing circuitry 538, which may include one or more programmable processors, application-specific integrated circuits, field-programmable gate arrays, or combinations thereof (not shown) suitable for executing instructions. The UE 530 also includes software 531, which is stored in or accessible by the UE 530 and executable by the processing circuitry 538. The software 531 includes a client application 532. The client application 532 can be operated to provide services to human or non-human users via the UE 530 with the support of the host computer 510. In the host computer 510, a host application 512 executing can communicate with the executing client application 532 via an OTT connection 550, which terminates between the UE 530 and the host computer 510. When providing services to a user, client application 532 can receive request data from host application 512 and provide user data in response to the request data. OTT connection 550 can transmit both request data and user data. Client application 532 can interact with the user to generate the user data it provides.

[0328] Notice, Figure 15 The host computer 510, base station 520, and UE 530 shown can be respectively connected to Figure 14 The host computer 430, base stations 412a, 412b, and 412c are similar to or identical to one of the UEs 491 and 492. That is, the internal workings of these entities can be as follows: Figure 15 As shown, and independently, the surrounding network topology can be Figure 14 The network topology.

[0329] exist Figure 15 The OTT connection 550 has been abstractly depicted to illustrate communication between the host computer 510 and the UE 530 via base station 520, without explicitly mentioning any intermediate devices or the precise routing of messages via these devices. The network infrastructure can determine the routing, which can be configured to be hidden from the UE 530 or the service provider operating the host computer 510, or both. During OTT connection 550 activity, the network infrastructure can also make decisions to dynamically change the routing (e.g., based on load balancing considerations or network reconfiguration).

[0330] The wireless connection 570 between UE 530 and base station 520 is based on the teachings of the embodiments described throughout this disclosure. One or more embodiments in various embodiments improve the performance of OTT services provided to UE 530 using OTT connection 550, wherein wireless connection 570 forms the final segment of OTT connection 550.

[0331] Measurement procedures may be provided for the purpose of monitoring data rates, latency, and other factors improved in one or more embodiments. Optional network functions may also be available for reconfiguring the OTT connection 550 between host computer 510 and UE 530 in response to changes in measurement results. The measurement procedures and / or network functions for reconfiguring the OTT connection 550 may be implemented in software 511 and hardware 515 of host computer 510, or in software 531 and hardware 535 of UE 530, or both. In embodiments, sensors (not shown) may be deployed in or associated with communication devices traversed by the OTT connection 550; the sensors may participate in the measurement procedures by providing values ​​of the monitored quantities illustrated above, or by providing values ​​of other physical quantities from which software 511, 531 can calculate or estimate the monitored quantities. Reconfiguration of the OTT connection 550 may include message formatting, retransmission settings, preferred routing, etc.; reconfiguration does not need to affect base station 520 and may be unknown or imperceptible to base station 520. Such procedures and functions may be known and practiced in the art. In some embodiments, the measurement may involve proprietary UE signaling, which facilitates the host computer 510 in measuring throughput, propagation time, latency, etc. The measurement can be achieved by software 511 and 531 using OTT connection 550 to send messages (particularly empty or "virtual" messages) while simultaneously monitoring propagation time, errors, etc.

[0332] Figure 16 This is a flowchart illustrating a method according to one embodiment implemented in a communication system. The communication system includes a host computer, a base station, and a UE, which may be a reference... Figure 14 and Figure 15 The host computer, base station, and UE are described. For the sake of brevity, this section will only include descriptions of... Figure 16The diagram is referenced. In step 610, the host computer provides user data. In sub-step 611 of step 610 (which may be optional), the host computer provides user data by executing a host application. In step 620, the host computer initiates a transmission carrying user data to the UE. In step 630 (which may be optional), in accordance with the teachings of the embodiments described throughout this disclosure, the base station sends the user data carried in the transmission initiated by the host computer to the UE. In step 640 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

[0333] Figure 17 This is a flowchart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be a reference... Figure 14 and Figure 15 The host computer, base station, and UE are described. For the sake of brevity, this section will only include descriptions of... Figure 17 The diagram is referenced. In step 710 of the method, the host computer provides user data. In an optional sub-step (not shown), the host computer provides user data by executing a host application. In step 720, the host computer initiates a transmission carrying user data to the UE. According to the teachings of the embodiments described throughout this disclosure, this transmission may be via a base station. In step 730 (which may be optional), the UE receives the user data carried in the transmission.

[0334] Figure 18 This is a flowchart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be a reference... Figure 14 and Figure 15 The host computer, base station, and UE are described. For the sake of brevity, this section will only include descriptions of... Figure 18 The diagram is referenced. In step 810 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step 820, the UE provides user data. In sub-step 821 of step 820 (which may be optional), the UE provides user data by executing a client application. In sub-step 811 of step 810 (which may be optional), the UE executes a client application that provides user data in response to the received input data provided by the host computer. When providing user data, the executed client application may also consider user input received from the user. Regardless of the specific manner in which user data is provided, the UE initiates the transmission of user data to the host computer in sub-step 830 (which may be optional). In step 840 of the method, the host computer receives user data sent from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.

[0335] Figure 19 This is a flowchart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be a reference... Figure 14 and Figure 15 The host computer, base station, and UE are described. For the sake of brevity, this section will only include descriptions of... Figure 19 The diagram is referenced. In step 910 (which may be optional), the base station receives user data from the UE in accordance with the teachings of the embodiments described throughout this disclosure. In step 920 (which may be optional), the base station initiates a transmission of the received user data to the host computer. In step 930 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

[0336] The term unit may have the conventional meaning in the field of electronic, electrical and / or electronic equipment, and may include, for example, electrical and / or electronic circuits, devices, modules, processors, memories, logic solid-state and / or discrete devices, computer programs or instructions for performing various tasks, processes, calculations, outputs and / or display functions (e.g., those functions described herein).

[0337] Figure 20 A method 1000, according to certain embodiments, is illustrated, performed by a target CU during a handover of a migration node from source CU and source DU to target CU and target DU. At step 1002, the target CU sends a first handover command to the target DU for handing over at least one child node of the migration node from source CU and source DU to the target CU and target DU.

[0338] In a specific embodiment, the migration node is an integrated access and backhaul node (IAB) node; the switching of the migration node is an inter-CU IAB migration; the first CU is the first donor CU during the inter-CU IAB migration; the second CU is the second donor CU during the inter-CU IAB migration; and the target DU is the target donor DU.

[0339] In a particular embodiment, the target CU receives a handover request from the source CU, the handover request indicating a migration node and at least one child node for switching from the source CU to the target CU.

[0340] In a particular embodiment, the target CU sends a handover request confirmation message to the migration node via the source CU. This handover request confirmation message includes a second handover command used only by the migration node, and is sent to the migration node before the first handover command is sent to at least one child node.

[0341] In a particular embodiment, before sending the first handover command, the target CU receives an RRC reconfiguration complete message from the MT of the migration node and establishes an F1 connection between the migration node and the target CU.

[0342] In a particular embodiment, the first switching command includes an F1-AP DL RRC transmission message.

[0343] In a particular embodiment, the first switching command includes multiple messages, and each of the multiple messages is used to migrate a node from the source CU and source DU to a specific child node among the multiple child nodes of the target CU and target DU.

[0344] In a particular embodiment, the first switching command includes a request for the group RRC transmission status.

[0345] In a particular embodiment, the target CU receives at least one reconfiguration complete message from at least one child node, and at least one response message indicates that at least one child node has received a first handover command.

[0346] In a particular embodiment, a first switching command sent to the migration node initiates a unique switching command for at least one child node of the migration node.

[0347] In a particular embodiment, at least one child node of the migration node includes a child IAB node, which is a parent node relative to at least one additional child node, and the target CU sends a third handover command for switching from the first CU to at least one additional child node of the second CU together with the child IAB node.

[0348] In a particular embodiment, before sending the third handover command, the target CU receives the RRC reconfiguration complete message from the MT of the sub-IAB node and establishes an F1 connection between the sub-IAB node and the first network node.

[0349] Figure 21 A wireless network (e.g.) is shown. Figure 9 A schematic block diagram of a virtual device 1100 in a wireless network (as shown in the diagram). This device can be used in wireless devices or network nodes (e.g., Figure 9 This is implemented in the wireless device 110 or network node 160 shown. The device 1100 is operable to perform the reference... Figure 20 The example methods described herein, as well as any other possible processes or methods disclosed herein. It should also be understood that... Figure 20 The method need not be performed solely by device 1100. At least some operations of the method may be performed by one or more other entities.

[0350] The virtual device 1100 may include processing circuitry (which may include one or more microprocessors or microcontrollers) and other digital hardware (which may include digital signal processors (DSPs), dedicated digital logic, etc.). The processing circuitry may be configured to execute program code stored in memory, which may include one or more types of memory, such as read-only memory (ROM), random access memory, cache memory, flash memory, optical storage devices, etc. The program code stored in the memory includes program instructions for executing one or more telecommunications and / or data communication protocols and instructions for executing one or more techniques described herein in several embodiments. In some embodiments, the processing circuitry may be used to cause the transmitting module 1110 and any other suitable unit of the device 1100 to perform corresponding functions according to one or more embodiments of this disclosure.

[0351] According to some embodiments, the sending module 1110 may perform certain sending functions of the apparatus 1100. For example, the sending module 1110 may send a first switching command to the target DU for switching at least one child node of the migration node from the source CU and source DU to the target CU and target DU.

[0352] As used herein, the term module or unit may have the conventional meaning in the field of electronic, electrical and / or electronic equipment, and may include, for example, electrical and / or electronic circuits, devices, modules, processors, memories, logic solid-state and / or discrete devices, computer programs or instructions for performing various tasks, processes, calculations, outputs and / or display functions (e.g., those functions described herein).

[0353] Figure 22 A method 1200, performed by a migration node during a handover from source CU and source DU to target CU and target DU according to certain embodiments, is described. At step 1202, the migration node receives a first handover command from the target CU via the source CU. This first handover command is used to switch at least one child node of the migration node from the source CU and source DU to the target CU and target DU. At step 1204, the migration node sends this message to at least one child node.

[0354] In a particular embodiment, the migration node is an IAB node; the switching from the source CU and source DU to the target CU and target DU is an inter-CU IAB migration; the CU is the source donor CU during the inter-CU IAB migration; and the target CU is the source donor CU during the inter-CU IAB migration.

[0355] In a particular embodiment, the migration node receives a handover request confirmation message via the source CU before receiving the first handover command. The handover request confirmation message includes a second handover command intended only for use by the migration node.

[0356] In a particular embodiment, before receiving the second handover command, the migration node sends an RRC reconfiguration complete message to the target CU via the source CU, and establishes an F1 connection between the migration node and the target CU based on the RRC reconfiguration complete message.

[0357] In a particular embodiment, the first switching command includes an F1-AP DL RRC transmission message.

[0358] In a particular embodiment, the first switching command includes multiple messages, and each of the multiple messages is for a specific child node among multiple child nodes of the migration node. The multiple child nodes are switching from source CU and source DU to target CU and target DU together with the migration node.

[0359] In a particular embodiment, the first switching command includes a request for the group RRC transmission status.

[0360] In a particular embodiment, the first switching command initiates a unique switching command for at least one child node of the migrated node.

[0361] In a particular embodiment, the migration node receives at least one reconfiguration complete message from at least one child node, and the at least one reconfiguration complete message indicates that at least one child node has received a first handover command. The migration node sends at least one reconfiguration complete message from at least one child node to the target CU.

[0362] In a particular embodiment, at least one reconfiguration complete message includes a plurality of reconfiguration complete messages, and each of the plurality of reconfiguration complete messages comes from a specific child node among a plurality of child nodes of the migration node.

[0363] In a particular embodiment, each of the multiple reconfiguration complete messages is sent to the target CU in a separate F1-AP UL RRC transport message.

[0364] In a particular embodiment, multiple reconfiguration complete messages are sent to the target CU in a single F1-AP UL RRC transport message.

[0365] In a particular embodiment, a single F1-AP UL RRC transmission message is sent after a duration associated with the timer.

[0366] In a particular embodiment, the migration node receives a request from the target CU for group delivery of multiple reconfiguration complete messages.

[0367] In a particular embodiment, at least one child node of the migration node includes a child IAB node, which is a parent node relative to at least one additional child node, and the migration node receives a third handover command for switching from the source CU and source DU to the target CU and target DU together with the child IAB node. The migration node sends the third handover command to the at least one additional child IAB node.

[0368] In a particular embodiment, before receiving the third handover command, the migration node receives an RRC reconfiguration complete message from the MT of at least one additional sub-IAB node and sends an RRC reconfiguration complete message to the target CU to trigger the establishment of an F1 connection between the at least one additional sub-IAB node and the target CU.

[0369] Figure 23 A wireless network (e.g.) is shown. Figure 9 The diagram shows a schematic block diagram of a virtual device 1300 in a wireless network. This device can be used in wireless devices or network nodes (e.g., Figure 9 This is implemented in the wireless device 110 or network node 160 shown. The device 1300 is operable to perform the reference... Figure 23 The example methods described herein, as well as any other possible processes or methods disclosed herein. It should also be understood that... Figure 23 The method need not be performed solely by device 1300. At least some operations of the method may be performed by one or more other entities.

[0370] The virtual device 1300 may include processing circuitry (which may include one or more microprocessors or microcontrollers) and other digital hardware (which may include digital signal processors (DSPs), dedicated digital logic, etc.). The processing circuitry may be configured to execute program code stored in memory, which may include one or more types of memory, such as read-only memory (ROM), random access memory, cache memory, flash memory, optical storage devices, etc. The program code stored in the memory includes program instructions for executing one or more telecommunications and / or data communication protocols and instructions for executing one or more techniques described herein in several embodiments. In some embodiments, the processing circuitry may be used to cause the receiving module 1310, the transmitting module 1320, and any other suitable unit of the device 1300 to perform corresponding functions according to one or more embodiments of this disclosure.

[0371] According to some embodiments, the receiving module 1310 may perform certain receiving functions of the apparatus 1300. For example, the receiving module 1310 may receive a first handover command from the target CU via the source CU. The first handover command is used to hand over at least one child node of the migration node from the source CU and source DU to the target CU and target DU.

[0372] According to some embodiments, the sending module 1320 may perform certain sending functions of the device 1300. For example, the sending module 1320 may send a message to at least one child node.

[0373] Figure 24 A method 1400, performed by a migration node during a handover from source CU and source DU to target CU and target DU according to certain embodiments, is described. The migration node is a child node of a parent migration node and is the parent node of at least one additional child node. At step 1402, the migration node receives a first handover command from the target CU via the parent migration node. This first handover command is for at least one additional child node of the migration node, which is also handing over from source CU and source DU to target CU and target DU along with the migration node. At step 1404, the migration node sends this message to at least one additional child node of the migration node.

[0374] In a specific embodiment, the migration node and the parent migration node are IAB nodes; the handover is an inter-CU IAB migration; the source CU is the source donor CU during the inter-CU IAB migration; and the target CU is the target donor CU during the inter-CU IAB migration.

[0375] In a particular embodiment, the migration node receives a handover request confirmation message via its parent migration node before receiving the first handover command. The handover request confirmation message includes a second handover command intended for use by the migration node.

[0376] In a specific embodiment, before receiving the second handover command, the migration node sends an RRC reconfiguration complete message to the target CU via the parent migration node. Based on the RRC reconfiguration complete message, an F1 connection is established between the migration node and the target CU.

[0377] In a particular embodiment, the first switching command includes an F1-AP DL RRC transmission message.

[0378] In a particular embodiment, the migration node is a parent node relative to a plurality of child nodes that switch from the source CU and source DU to the target CU and target DU together with the migration node; the first switching command includes a plurality of messages; and each of the plurality of messages is for a specific child node among the plurality of child nodes.

[0379] In a particular embodiment, the migration node sends at least one reconfiguration complete message to the target CU via the parent migration node. This at least one reconfiguration complete message indicates that the migration node has received a first handover command.

[0380] In a particular embodiment, the migration node is a parent node relative to a plurality of child nodes that switch from the source CU and source DU to the target CU and target DU together with the migration node. The at least one reconfiguration complete message includes a plurality of reconfiguration complete messages, each of which originates from a specific child node among the plurality of child nodes.

[0381] In a particular embodiment, each of the multiple reconfiguration complete messages is sent to the parent migration node in a separate Radio Resource Control (RRC) message.

[0382] In a particular embodiment, multiple reconfiguration complete messages are sent to the parent migration node in a single RRC message.

[0383] In a particular embodiment, a single RRC message is sent after a duration associated with the timer.

[0384] In a particular embodiment, the migration node receives a request from the parent migration node for a group delivery of multiple reconfiguration complete messages.

[0385] Figure 25 A wireless network (e.g.) is shown. Figure 9 The diagram shows a schematic block diagram of a virtual device 1500 in a wireless network. This device can be used in wireless devices or network nodes (e.g., Figure 9 This is implemented in the wireless device 110 or network node 160 shown. The device 1500 is operable to perform the reference... Figure 24 The example methods described herein, as well as any other possible processes or methods disclosed herein. It should also be understood that... Figure 24 The method need not be performed solely by device 1500. At least some operations of the method may be performed by one or more other entities.

[0386] The virtual device 1500 may include processing circuitry (which may include one or more microprocessors or microcontrollers) and other digital hardware (which may include digital signal processors (DSPs), dedicated digital logic, etc.). The processing circuitry may be configured to execute program code stored in memory, which may include one or more types of memory, such as read-only memory (ROM), random access memory, cache memory, flash memory, optical storage devices, etc. The program code stored in the memory includes program instructions for executing one or more telecommunications and / or data communication protocols and instructions for executing one or more techniques described herein in several embodiments. In some embodiments, the processing circuitry may be used to cause the receiving module 1510, the transmitting module 1520, and any other suitable unit of the device 1500 to perform corresponding functions according to one or more embodiments of this disclosure.

[0387] According to some embodiments, the receiving module 1510 may perform certain receiving functions of the apparatus 1500. For example, the receiving module 1510 may receive a first handover command from the target CU via a parent migration node. The first handover command is for at least one additional child node of the migration node, which is also switching from the source CU and source DU to the target CU and target DU together with the migration node.

[0388] According to some embodiments, the sending module 1520 may perform certain sending functions of the device 1500. For example, the sending module 1520 may send the message to at least one additional child node of the migration node.

[0389] Example Implementation

[0390] Group A Example Implementation

[0391] Example 1. A method performed by a wireless device, the method comprising: any of the wireless device steps, features, or functions described above, alone or in combination with the other steps, features, or functions described above.

[0392] Example 2. The method according to the foregoing embodiments further includes one or more of the above-described additional wireless device steps, features, or functions.

[0393] Example 3. The method according to any of the foregoing embodiments further includes: providing user data; and forwarding the user data to a host computer via transmission to a base station.

[0394] Group B Implementation Examples

[0395] Example 4. A method performed by a base station for switching an IAB node from a first donor CU to a second donor CU during an inter-CU IAB migration, the method comprising: any of the steps, features, or functions described above with respect to the Group A embodiments, alone or in combination with the other steps, features, or functions described above.

[0396] Example 5. A method performed by a base station for switching an IAB node from a first donor CU to a second donor CU during an inter-CU IAB migration, the method comprising: any of the steps, features, or functions described above with respect to the Group B embodiments, alone or in combination with the other steps, features, or functions described above.

[0397] Example 6. The method according to any of the foregoing embodiments further includes: obtaining user data; and forwarding the user data to a host computer or a wireless device.

[0398] Group C Implementation Examples

[0399] Example 7. A wireless device includes: processing circuitry configured to perform any step of any of the embodiments in Group A; and power supply circuitry configured to supply power to the wireless device.

[0400] Example 8. A base station includes: a processing circuit configured to perform any step of any of the embodiments in Group B; and a power supply circuit configured to supply power to a wireless device.

[0401] Example 9. A user equipment (UE) includes: an antenna configured to transmit and receive wireless signals; a radio front-end circuit connected to the antenna and a processing circuit and configured to modulate signals transmitted between the antenna and the processing circuit; a processing circuit configured to perform any step of any of the Group A embodiments; an input interface connected to the processing circuit and configured to allow information to be input into the UE for processing by the processing circuit; an output interface connected to the processing circuit and configured to output information processed by the processing circuit from the UE; and a battery connected to the processing circuit and configured to power the UE.

[0402] Example 10. A communication system including a host computer, comprising: processing circuitry configured to provide user data; and a communication interface configured to forward the user data to a cellular network for transmission to a user equipment (UE), wherein the cellular network includes a base station having a radio interface and processing circuitry, the processing circuitry of the base station being configured to perform any step of any of the embodiments in Group B.

[0403] Example 11. The communication system according to the foregoing embodiments also includes a base station.

[0404] Example 12. The communication system according to the foregoing two embodiments further includes a UE, wherein the UE is configured to communicate with a base station.

[0405] Example 13. A communication system according to the foregoing three embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application to provide user data; and the UE includes processing circuitry configured to execute a client application associated with the host application.

[0406] Exemplary Example 14. A method implemented in a communication system including a host computer, a base station, and a user equipment (UE), the method comprising: providing user data at the host computer; and initiating a transmission carrying the user data to the UE via a cellular network including the base station at the host computer, wherein the base station performs any step of any of the group B embodiments.

[0407] Example 15. The method according to the foregoing embodiments further includes: transmitting user data at the base station.

[0408] Example 16. The method according to the foregoing two embodiments, wherein user data is provided at the host computer by executing a host application, the method further includes: executing a client application associated with the host application at the UE.

[0409] Example 17. A user equipment (UE) configured to communicate with a base station, the UE including a radio interface and processing circuitry configured to perform any of the three embodiments described above.

[0410] Example 18. A communication system including a host computer, comprising: processing circuitry configured to provide user data; and a communication interface configured to forward the user data to a cellular network for transmission to a user equipment (UE), wherein the UE includes a radio interface and processing circuitry, and components of the UE are configured to perform any step of any of the Group A embodiments.

[0411] Example 19. The communication system according to the foregoing embodiments, wherein the cellular network further includes a base station configured to communicate with the UE.

[0412] Example 20. A communication system according to the foregoing two embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application to provide user data; and the processing circuitry of the UE is configured to execute a client application associated with the host application.

[0413] Exemplary Example 21. A method implemented in a communication system including a host computer, a base station, and a user equipment (UE), the method comprising: providing user data at the host computer; and initiating a transmission carrying the user data to the UE via a cellular network including the base station at the host computer, wherein the UE performs any step of any of the embodiments in Group A.

[0414] Example 22. The method according to the foregoing embodiments further includes: receiving user data from the base station at the UE.

[0415] Example 23. A communication system including a host computer, comprising: a communication interface configured to receive user data originating from transmissions from a user equipment (UE) to a base station, wherein the UE includes a radio interface and processing circuitry, the processing circuitry of the UE being configured to perform any step of any of the embodiments in Group A.

[0416] Example 24. The communication system according to the foregoing embodiments further includes a UE.

[0417] Example 25. The communication system according to the foregoing two embodiments further includes a base station, wherein the base station includes: a radio interface configured to communicate with a UE; and a communication interface configured to forward user data carried in transmissions from the UE to the base station to a host computer.

[0418] Example 26. A communication system according to the foregoing three embodiments, wherein: the processing circuit of the host computer is configured to execute a host application; and the processing circuit of the UE is configured to execute a client application associated with the host application, thereby providing user data.

[0419] Example 27. A communication system according to the foregoing four embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application to provide requested data; and the processing circuitry of the UE is configured to execute a client application associated with the host application to provide user data in response to the requested data.

[0420] Exemplary Example 28. A method implemented in a communication system including a host computer, a base station, and a user equipment (UE), the method comprising: at the host computer, receiving user data transmitted from the UE to the base station, wherein the UE performs any step of any of the embodiments in Group A.

[0421] Example 29. The method according to the foregoing embodiments further includes: providing user data to the base station at the UE.

[0422] Example 30. The method according to the foregoing two embodiments further includes: at the UE, executing a client application to provide user data to be sent; and at the host computer, executing a host application associated with the client application.

[0423] Example 31. The method according to the foregoing three embodiments further includes: executing a client application at the UE; and receiving input data to the client application at the UE, the input data being provided at a host computer by executing a host application associated with the client application, wherein the client application provides user data to be sent in response to the input data.

[0424] Example 32. A communication system including a host computer, the host computer including a communication interface configured to receive user data originating from transmissions from a user equipment (UE) to a base station, wherein the base station includes a radio interface and processing circuitry configured to perform any step of any of the Group B embodiments.

[0425] Example 33. The communication system according to the foregoing embodiments further includes a base station.

[0426] Example 34. The communication system according to the foregoing two embodiments further includes a UE, wherein the UE is configured to communicate with the base station.

[0427] Example 35. A communication system according to the foregoing three embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application; the UE is configured to execute a client application associated with the host application, thereby providing the user data to be received by the host computer.

[0428] Exemplary Example 36. A method implemented in a communication system including a host computer, a base station, and a user equipment (UE), the method comprising: at the host computer, receiving from the base station user data transmitted from the base station that has already been received from the UE, wherein the UE is configured to perform any step of any of the embodiments in Group A.

[0429] Example 37. The method according to the foregoing embodiments further includes: receiving user data from the UE at the base station.

[0430] Example 38. The method according to the foregoing two embodiments further includes: at the base station, initiating the transmission of received user data to the host computer.

Claims

1. A method performed by the target CU during a handover of a migration node from a source central unit (CU) and a source distributed unit (DU) to a target CU and a target DU, the method comprising: A first handover command is sent to the migration node via the target DU to switch at least one child node of the migration node from the source CU and source DU to the target CU and target DU. The method further includes the following steps before the first switching command is sent to the at least one child node: A handover request confirmation message is sent to the migration node via the source CU, wherein the handover request confirmation message includes a second handover command used only by the migration node. Receive an RRC reconfiguration complete message from the migration node's move termination MT, and Based on the RRC reconfiguration completion message, an F1 connection is established between the migration node and the target CU.

2. The method according to claim 1, wherein: The migration node is an Integrated Access and Backhaul (IAB) node. The switching of the migration node is an IAB migration between CUs; The first CU is the first donor CU during the IAB migration between CUs; The second CU is the second donor CU during the IAB migration between CUs; ​​and The target DU is the target donor DU.

3. The method according to claim 1 or 2, further comprising: A handover request is received from the source CU, the handover request indicating the migration node and the at least one child node for switching from the source CU to the target CU.

4. The method according to claim 1 or 2, further comprising: Receive at least one reconfiguration complete message from the at least one child node, and at least one response message indicating that the at least one child node has received the first switching command.

5. A method performed by a migration node during a handover from a source central unit (CU) and a source distributed unit (DU) to a target CU and a target DU, the method comprising: The first handover command is received from the target CU via the source CU, the first handover command being used to switch at least one child node of the migration node from the source CU and source DU to the target CU and target DU; as well as Send the first switching command to the at least one child node. Prior to receiving the first switching command, the method further includes: The handover request confirmation message is received via the source CU, wherein the handover request confirmation message includes a second handover command used only by the migration node. Sending an RRC reconfiguration complete message to the target CU via the source CU, and Specifically, an F1 connection is established between the migration node and the target CU based on the RRC reconfiguration completion message.

6. The method according to claim 5, further comprising: Receive at least one reconfiguration complete message from the at least one child node, the at least one reconfiguration complete message indicating that the at least one child node has received the first switching command; as well as Send the at least one reconfiguration completion message from the at least one child node to the target CU.

7. The method according to claim 5 or 6, wherein, At least one child node of the migration node includes a child IAB node, the child IAB node being a parent node relative to at least one additional child node, and wherein the method further includes: Receive a third handover command for switching the at least one additional child node, together with the child IAB node, from the source CU and source DU to the target CU and target DU; and Send the third switching command to the at least one additional sub-IAB node.

8. A method performed by a migration node during a handover from a source central unit (CU) and a source distributed unit (DU) to a target CU and a target DU, the migration node being a child node of a parent migration node and a parent node of at least one additional child node, the method comprising: The first switching command is received from the target CU via the parent migration node. The first switching command is used to switch from the source CU and source DU to the target CU and target DU together with the migration node. as well as Send the first switching command to at least one of the additional child nodes of the migration node. Prior to receiving the first switching command, the method further includes: The handover request confirmation message is received via the parent migration node, wherein the handover request confirmation message includes a second handover command used only by the migration node. Send an RRC reconfiguration complete message to the target CU via the parent migration node, and Specifically, an F1 connection is established between the migration node and the target CU based on the RRC reconfiguration completion message.

9. The method according to claim 8, further comprising: At least one reconfiguration complete message is sent to the target CU via the parent migration node, the at least one reconfiguration complete message indicating that the migration node has received the first switch command.

10. A target central unit (CU), comprising: The processing circuitry is configured to: during the handover of the migration node from the source CU and source distributed unit DU to the target CU and target DU, Send a first handover command to the target DU to switch at least one child node of the migration node from the source CU and source DU to the target CU and target DU. Specifically, before the first switching command is sent to the at least one child node, the processing circuit is further configured to: A handover request confirmation message is sent to the migration node via the source CU, wherein the handover request confirmation message includes a second handover command used only by the migration node. Receive the RRC reconfiguration complete message from the MT of the migration node, and Based on the RRC reconfiguration completion message, an F1 connection is established between the migration node and the target CU.

11. The target CU according to claim 10, wherein, The processing circuit is configured to receive a handover request from the source CU, the handover request indicating the migration node and the at least one child node for switching from the source CU to the target CU.

12. A migration node, comprising: The processing circuit is configured as follows: During the handover from the source central unit (CU) and source distributed unit (DU) to the target CU and target DU, a first handover command is received from the target CU via the source CU. The first handover command is used to switch at least one child node of the migration node from the source CU and source DU to the target CU and target DU. as well as Send the first switching command to the at least one child node. Prior to receiving the first switching command, the processing circuit is further configured to: The handover request confirmation message is received via the source CU, wherein the handover request confirmation message includes a second handover command used only by the migration node. Sending an RRC reconfiguration complete message to the target CU via the source CU, and Specifically, an F1 connection is established between the migration node and the target CU based on the RRC reconfiguration completion message.

13. A migration node, wherein the migration node is a child node of a parent migration node and a parent node of at least one additional child node, the migration node comprising: The processing circuit is configured as follows: During the handover from the source central unit (CU) and source distributed unit (DU) to the target CU and target DU, a first handover command is received from the target CU via the parent migration node. The first handover command is used to switch from the source CU and source DU to the at least one additional child node of the target CU and target DU together with the migration node. as well as Send the first switching command to at least one of the additional child nodes of the migration node. Prior to receiving the first switching command, the processing circuit is further configured to: The handover request confirmation message is received via the parent migration node, wherein the handover request confirmation message includes a second handover command used only by the migration node. Send an RRC reconfiguration complete message to the target CU via the parent migration node, and Specifically, an F1 connection is established between the migration node and the target CU based on the RRC reconfiguration completion message.

Images