Cell selection for IAB nodes

Abstract

This disclosure describes methods, systems, and apparatus for wireless communication based on cell selection criteria for integrated access and backhaul (IAB) nodes.

Description

Technical Field

[0001] This application relates generally to wireless communication systems, and particularly to integrated access and backhaul (IAB). Background Technology

[0002] Wireless mobile communication technologies use various standards and protocols to transmit data between base stations and wireless mobile devices. Wireless communication system standards and protocols may include 3GPP Long Term Evolution (LTE) (e.g., 4G) or New Radio (NR) (e.g., 5G); the Institute of Electrical and Electronics Engineers (IEEE) 802.16 standard, commonly referred to by the industry organization as WiMAX; and the IEEE 802.11 standard for Wireless Local Area Networks (WLANs), commonly referred to by the industry organization as Wi-Fi. In the 3GPP Radio Access Network (RAN) of an LTE system, a base station may include RAN nodes such as an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node B (also commonly referred to as Evolved Node B, Enhanced Node B, eNodeB, or eNB) and / or a Radio Network Controller (RNC) in the E-UTRAN, which communicates with wireless communication equipment called User Equipment (UE). In the fifth generation (5G) wireless RAN, RAN nodes may include 5G nodes and NR nodes (also known as next-generation node B or g NodeB (gNB)).

[0003] The RAN uses Radio Access Technology (RAT) to communicate between RAN nodes and UEs. The RAN can include Global System for Mobile Communications (GSM), Enhanced Data Rate GSM Evolution (EDGE) RAN (GERAN), Universal Terrestrial Radio Access Network (UTRAN), and / or E-UTRAN, which provides access to communication services through the core network. Each RAN operates according to a specific 3GPP RAT. For example, GERAN implements the GSM and / or EDGE RAT, UTRAN implements the Universal System for Mobile Communications (UMTS) RAT or other 3GPP RATs, E-UTRAN implements the LTE RAT, and NG-RAN implements the 5G RAT. In some deployments, E-UTRAN may also implement the 5G RAT.

[0004] 5G NR frequency bands can be divided into two distinct frequency ranges. Frequency range 1 (FR1) includes bands below 6 GHz, some of which may be used by previous standards but could potentially be extended to cover new spectrum offerings from 410 MHz to 7125 MHz. Frequency range 2 (FR2) includes bands from 24.25 GHz to 52.6 GHz. The millimeter wave (mmWave) bands in FR2 have a shorter range but higher available bandwidth than those in FR1. Those skilled in the art will recognize that these frequency ranges, presented by way of example, may vary over time or in different regions. Attached Figure Description

[0005] To facilitate identification of any particular element or action being discussed, one or more of the most significant digits in the reference numerals refer to the drawing number in which the element was first introduced.

[0006] Figure 1 An IAB architecture based on one implementation scheme is shown.

[0007] Figure 2 An exemplary IAB network according to one implementation is shown.

[0008] Figure 3 This is a flowchart illustrating a method for an IAB node to select a cell in a wireless network, according to one implementation scheme.

[0009] Figure 4 This is a flowchart illustrating a method for an IAB node in a wireless network according to one implementation scheme.

[0010] Figure 5 This is a flowchart illustrating a method for using IAB donor node metrics according to one implementation scheme.

[0011] Figure 6 This is a flowchart illustrating a method in a wireless network comprising multiple IAB nodes according to one implementation scheme.

[0012] Figure 7 An example of a service-based architecture according to certain implementation schemes is shown.

[0013] Figure 8 A UE according to one implementation is shown.

[0014] Figure 9 A network node according to one implementation scheme is shown.

[0015] Figure 10 An exemplary IAB network according to one implementation is illustrated schematically.

[0016] Figure 11An exemplary protocol architecture for IAB is shown according to one implementation scheme.

[0017] Figure 12 An IAB architecture based on one implementation scheme is shown.

[0018] Figure 13 An NG-RAN architecture according to one implementation is shown. Detailed Implementation

[0019] This disclosure relates to Integrated Access and Backhaul (IAB), a feature designed in 3GPP to implement multi-hop routing. An IAB node acts as both an access node connecting to a UE and provides backhaul links to other IAB nodes.

[0020] Efforts are underway to identify and evaluate potential solutions for efficient operation of integrated access and radio backhaul for NR. In some architectures used in cellular networks, the NR link itself can be used as a backhaul alternative to fiber optics, which typically have long delivery cycles (e.g., long lead times for installation, inaccessibility of certain areas, etc., resulting in significant costs) due to economic and logistical constraints. The high bandwidth of the NR link, combined with efficient segmentation of the control and data units of the gNB, allows for the deployment of such architectures. Combined with mmWave technology, IAB technology may be able to provide better coverage and higher throughput for UEs that previously lacked line-of-sight coverage. However, the new architecture now leads to the introduction of multi-hop networks with new challenges.

[0021] Figure 1 An exemplary IAB architecture 100 is illustrated. The IAB architecture 100 includes an IAB donor 102 having fiber optic connectivity (e.g., via an NG interface) to a 5G core 104, IAB node 106, and IAB node 108. The IAB donor 102, which may also be referred to as a back-end node or parent IAB node, includes a data unit (DU) (shown as DU 120) and a control unit (CU) (shown as CU 124). IAB nodes 106 and 108 may be referred to as intermediate nodes and each includes two sub-components: a DU (shown as DU 116 and DU 118) and a mobile terminal (MT) (shown as MT 126 and MT 122).

[0022] The MT includes components that configure the gNB to behave similarly to a regular UE. For example, in an MT with additional enhancements discussed in 3GPP Releases 16 and 17, the protocols typically used by a UE to connect to the network are supported. For instance, MT 126 allows IAB node 106 to establish a Signaling Radio Bearer (SRB) and / or a Data Radio Bearer (DRB) with its parent node (IAB node 102). The MT performs cell selection to identify which parent to join, establishes and utilizes Radio Link Control (RLC) through the Backhaul Adaptation Protocol (BAP) layer, which provides functionality for carrying routing data for different UEs on different routes across the network.

[0023] In current wireless systems, System Information Block 1 (SIB1) includes information relevant to assessing whether a UE is allowed to access the cell, and defines the scheduling of other system information. SIB1 also includes radio resource configuration information shared by all UEs, as well as prohibition information applied to unified access control. In some such systems, the only way for a particular IAB node to access another IAB node or donor / parent is by using the standards defined in SIB1. However, because IAB nodes are higher-power gNBs (compared to the power of the UE), standards (e.g., Reference Signal Received Power (RSRP) and Reference Signal Received Quality (RSRQ) thresholds) can result in finding multiple parents. This can lead to problems for both the IAB nodes (i.e., IAB donor 102, IAB node 106, IAB node 108) and the corresponding UEs connected to them (i.e., UE 110, UE 112, UE 114).

[0024] Figure 2 An exemplary IAB network 200 is shown, which includes a 5G core 202 connected via optical fiber to a first IAB donor 204 (IA donor 1) having a coverage area 206 and a second IAB donor 208 (IAB donor 2) having a coverage area 210. Figure 2 Also shown are a first IAB node 212 (IAB node 1) with coverage area 214, a second IAB node 216 (IAB node 2) with coverage area 218, a third IAB node 220 (IAB node 3) with coverage area 222, a first UE 224 (UE1), a second UE 226 (UE2), a third UE 228 (UE3), and a fourth UE 230 (UE4). Figure 2 In the example shown, each of the UE and the IAB node is in different radio frequency (RF) conditions of the next-hop IAB node and the donor, which leads to a variety of possibilities in which the cell selection criteria of both the IAB node and the UE within the coverage of those nodes can be modified.

[0025] For example, the third IAB node 220 may choose to join either the first IAB node 212 or the second IAB node 216 based on the cellular network load of those specific intermediate nodes (e.g., the number of idle and connected UEs on a specific IAB node, the amount of signaling and data bearers already activated on a specific IAB node, or the ability to maintain the QoS of a specific application service). Similarly, the second IAB node 216 and the first IAB node 212 may join either the first IAB donor 204 or the second IAB donor 208 not only based on the S-Cell standard but also based on control. The CUs in the first IAB donor 204 and the second IAB donor 208 can control this selection / connection process and help set the end as the end link.

[0026] In the example shown, the first UE 224, the second UE 226, and the third UE 228 also have several options. For example, the third UE 228 can connect to a donor (i.e., the first IAB donor 204 or the second IAB donor 208) instead of the second IAB node 216 for latency purposes. The second UE 226 can choose to connect to the second IAB node 216 instead of the first IAB node 212 for load reasons between the IAB donor and the IAB node. The first UE 224 can select the third IAB node 220 instead of the second IAB node 216 based on network load. Furthermore, the fourth UE 230 can select the first IAB donor 204 or the second IAB donor 208 based on any device via its S-standard or reselect to the cell based on its configured measurement reports. However, none of these variations are available for the current UE or IAB node.

[0027] Because gNBs have better hardware and power capacity than UEs, the strongest cell standards currently in use can typically be easily met by multiple parent IAB nodes in a typical deployment scenario.

[0028] Therefore, in one embodiment disclosed herein, two different sets of cell selection criteria are transmitted in the IAB node and the UE's SIB1. For example, the selection criteria may include the UE's Qrxlevmin value and the IAB node's rxlevmin_iab_Node value, the UE's Qrxlevminoffset value and the IAB node's Qrxlevminoffset_iab_Node value, the UE's PMax value and the IAB node's PMax_iab_Node value, the UE's Qqualmin value and the IAB node's Qqualmin_iab_Node value, and the UE's Qqualminoffset value and the IAB node's Qqualminoffset_iab_Node value. The IAB node should be able to calculate its Qqualmeas to identify nodes that are not heavily loaded and can be selected / reselected.

[0029] When Srxlev > 0 and Squal > 0, the cell selection criterion S in the normal coverage area is satisfied, where for the UE:

[0030] Srxlev=Qrxlevmeas–(Qrxlevmin+Qrxlevminoffset)–Pcompensation–Qoffsettemp; and

[0031] Squal=Qqualmeas–(Qqualmin+Qqualminoffset)–Qoffsettemp.

[0032] Srxlev is the cell selected receive (RX) level value (in dB). Squal is the selected quality value (in dB). Qoffsettemp is the offset temporarily applied to the cell. Qrxlevmeas is the measured cell RX level value (RSRP). Qqualmeas is the measured cell quality value (RSRQ). Qrxlevmin is the minimum required RX level in the cell (in dBm). Qqualmin is the minimum required quality level in the cell (in dB). Qrxlevminoffset is the offset of Qrxlevmin for signaling consideration in the Srxlev evaluation, as a result of periodically searching for higher priority PLMNs while normally camped in the VPLMN. Qqualminoffset is the offset of Qqualmin for signaling consideration in the Squal evaluation, as a result of periodically searching for higher priority PLMNs while normally camped in the VPLMN. Pcompensation is a compensation parameter based on various power parameters, including PMax associated with the maximum transmit (TX) power.

[0033] When performing cell selection for IAB, the equations with the corresponding set of cell selection criteria are:

[0034] Srxlev=Qrxlevmeas–(Qrxlevmin_iab_Node+Qrxlevminoffset_iab_Node)–Pcompensation–Qoffsettemp; and

[0035] Squal=Qqualmeas–(Qqualmin_iab_Node+Qqualminoffset_iab_Node)–Qoffsettemp.

[0036] Figure 3 This is a flowchart illustrating a method 300 for an IAB node to select a cell in a wireless network according to one embodiment. In block 302, method 300 includes processing system information including a first set of cell selection criteria corresponding to a non-IAB UE and a second set of cell selection criteria corresponding to an IAB MT / UE. In block 304, method 300 includes measuring the cell to obtain cell measurement results. In block 306, method 300 includes determining whether cell selection conditions are met based on the cell measurement results and the second set of cell selection criteria corresponding to the IAB MT / UE. In block 308, based at least in part on the determination that the cell selection conditions are met, method 300 includes selecting the cell for wireless backhaul communication.

[0037] In another implementation, the IAB node is configured to broadcast its "depth" in the tree (i.e., the number of hops from the node to the initial donor node). This parameter can be used as a selection criterion when attached to a cell. When this parameter is considered independently of channel conditions, fewer hops may be better for an end-to-end (E2E) system. Additionally, depth can be indicated as a 3D matrix of hops, idle load, and connected load.

[0038] For example, Figure 4 This is a flowchart illustrating a method 400 for a first IAB node in a wireless network according to one embodiment. In block 402, method 400 includes processing a first message from a second IAB node at the first IAB node. The first message includes an indication of the hop count from the second IAB node to the IAB donor node. In block 404, method 400 includes using the hop count indication in a decision regarding a cell attached to the cell corresponding to the second IAB node.

[0039] In another implementation, a separate IAB donor node priority metric is used to help identify and / or prioritize IAB donor nodes during node selection or reselection. Priorities can be broadcast, for example, using dedicated signaling or overridden by individual priorities. For the broadcast priority option, a new Information Element (IE) can be created in the SIB. The IAB donor node priority metric can be based on the current load of the respective IAB donor node.

[0040] For example, Figure 5 This is a flowchart illustrating a method 500 for using IAB donor node metrics according to one embodiment. In block 502, method 500 includes determining IAB donor node metrics. In block 504, method 500 includes using IAB donor node metrics to identify and prioritize the selection or reselection of a specific IAB donor node among a plurality of IAB donor nodes.

[0041] In another implementation, for faster reselection of the IAB node, the IAB node is configured to remain inactive on the RRC connection rather than enter an RRC idle state. For example, the IAB node can be configured to always redirect instead of reselect.

[0042] For example, Figure 6 This is a flowchart illustrating method 600 in a wireless network comprising multiple IAB nodes according to one embodiment. In block 602, method 600 includes establishing connections between multiple IAB nodes in a tree including parent and child nodes in RRC connection mode. In block 604, upon individually exiting RRC connection mode, method 600 includes keeping the multiple IAB nodes in an inactive state of the RRC connection instead of an RRC idle state.

[0043] Exemplary System Architecture

[0044] In some implementations, the 5G system architecture supports data connectivity and services, enabling deployment using technologies such as network function virtualization and software-defined networking. The 5G system architecture can leverage service-based interactions between control plane network functions. Separating user plane functions from control plane functions allows for independent scalability, evolution, and flexible deployment (e.g., centralized or distributed (remote) locations). Modular function design allows for function reuse and enables flexible and efficient network slicing. Network functions and their network function services can interact directly or indirectly with another NF and its network function services via a service communication broker. Another intermediate function helps route control plane messages. This architecture minimizes dependencies between the AN and CN. The architecture may include an aggregated core network with a common AN-CN interface integrating different access types (e.g., 3GPP access and non-3GPP access). The architecture also supports a unified authentication framework, stateless NFs that decouple compute and storage resources, capability exposure, concurrent access to local and centralized services (to support low-latency services and access to local data networks, with user plane functions deployed near the AN), and / or roaming in the visited PLMN using both home-routed traffic and local breakout traffic.

[0045] A 5G architecture can be defined as service-based, and interactions between network functions can include service-based representations, where a network function within the control plane (e.g., an AMF) enables other authorized network functions to access its services. Service-based representations can also include point-to-point reference points. Reference point representations can also be used to illustrate interactions between NF services within network functions described by point-to-point reference points (e.g., N11) between any two network functions (e.g., AMF and SMF).

[0046] Figure 7 A service-based architecture 700 in 5GS according to one implementation is shown. As described in 3GPP TS 23.501, the service-based architecture 700 includes NFs such as NSSF 702, NEF 704, NRF 706, PCF 708, UDM 710, AUSF 712, AMF 714, and SMF 716 for communicating with UE 720, (R)AN 722, UPF 724, and DN 726. NFs and NF services can communicate directly (referred to as direct communication) or indirectly via SCP 718 (referred to as indirect communication). Figure 7 It also shows the corresponding service-based interfaces including Nutm, Naf, Nudm, Npcf, Nsmf, Nnrf, Namf, Nnef, Nnssf, and Nausf, as well as reference points N1, N2, N3, N4, and N6. The following describes the... Figure 7 The example functions provided by NF are shown below.

[0047] NSSF 702 supports functions such as: selecting the set of network slice instances serving the UE; determining the allowed NSSAIs and, if necessary, the mapping to subscribed S-NSSAIs; determining the configured NSSAIs and, if necessary, the mapping to subscribed S-NSSAIs; and / or determining the set of AMFs to be used to serve the UE, or, based on the configuration, possibly by querying the NRF to determine a list of candidate AMFs.

[0048] The NEF 704 supports the exposure of capabilities and events. NF capabilities and events can be securely exposed by the NEF 704 (e.g., for third-party, application functions, and / or edge computing). The NEF 704 can use a standardized interface (Nudr) to the UDR to store / retrieve information as structured data. The NEF 704 can also securely provide information from external applications to the 3GPP network and can provide application functions to securely provide information to the 3GPP network (e.g., anticipated UE behavior, 5GLAN group information, and service-specific information), where the NEF 704 can authenticate and authorize and help restrict application functions. The NEF 704 can provide internal-external information translation by translating information exchanged with the AF and information exchanged with internal network functions. For example, the NEF 704 translates between the AF service identifier and internal 5G core information (such as DNN and S-NSSAI). The NEF 704 can handle the masking of network and user-sensitive information to external AFs according to network policies. The NEF 704 can receive information from other network functions (based on their exposure capabilities) and store the received information as structured data using a standardized interface to the UDR. The stored information can then be accessed by the NEF 704 and re-exposed to other network and application functions for purposes such as analysis. For external exposure of services related to a specific UE, the NEF 704 can reside in the HPLMN. Depending on the operator agreement, the NEF 704 in the HPLMN can have an interface with the NF in the VPLMN. When the UE is able to switch between EPC and 5GC, SCEF+NEF can be used for service exposure.

[0049] NRF 706 supports service discovery by receiving NF discovery requests from NF instances or SCPs and providing information about the discovered NF instances to the NF instances or SCPs. NRF 706 also supports P-CSCF discovery (a special case of SMF discovery AF), maintaining NF profiles of available NF instances and their supported services, and / or notifying subscribed NF service consumers or SCPs of newly registered / updated / deregistered NF instances along with their NF services. In the context of network slicing, multiple NRFs can be deployed at different levels depending on the network implementation, such as PLMN level (NRFs configured with information about the entire PLMN), shared slice level (NRFs configured with information about the network slice set), and / or slice-specific level (NRFs configured with information about the S-NSSAI). In the context of roaming, multiple NRFs can be deployed in different networks, where the NRF in the visited PLMN (referred to as vNRF) is configured with information about the visited PLMN, and the NRF in the home PLMN (referred to as hNRF) is configured with information about the home PLMN, referenced by the vNRF via the N27 interface.

[0050] PCF 708 supports a unified policy framework for managing network behavior. PCF 708 provides policy rules for control plane functions to enforce them. PCF 708 accesses subscription information related to policy decisions in the Unified Data Repository (UDR). PCF 708 can access the UDR located in the same PLMN as PCF.

[0051] The UDM 710 supports the generation of 3GPP AKA authentication credentials, user identification processing (e.g., storage and management of SUPI for each subscriber in a 5G system), de-hiding of privacy-preserving subscription identifiers (SUCI), access authorization based on subscription data (e.g., roaming restrictions), UE service NF registration management (e.g., storing AMF for UE storage services, storing SMF for UE PDU sessions), service / session continuity (e.g., maintaining SMF / DNN allocation for ongoing sessions), MT-SMS delivery, lawful interception functionality (especially in outbound roaming scenarios where the UDM is the only contact point of the LI), subscription management, SMS management, 5GLAN group management processing, and / or external parameter configuration (expected UE behavior parameters or network configuration parameters). To provide these functions, the UDM 710 uses subscription data (including authentication data) that can be stored in the UDR. In this case, the UDM implements application logic and may not require internal user data storage, and several different UDMs can provide services to the same user in different transactions. The UDM 710 can reside in the HPLMN of its subscriber and can access information from the UDR located in the same PLMN.

[0052] AF 728 interacts with the core network to provide services such as: application-driven traffic routing; access to NEF 704; interaction with policy frameworks used for policy control; and / or interaction between IMS and 5GC. Based on operator deployment, application functions trusted by the operator may be allowed to interact directly with relevant network functions. Application functions that the operator does not allow direct access to network functions may interact with relevant network functions via an external exposure framework through NEF 704.

[0053] The AUSF 712 supports authentication for 3GPP access and untrusted non-3GPP access. The AUSF 712 also provides support for network slicing-specific authentication and authorization.

[0054] AMF 714 supports the termination of the RAN CP interface (N2), the termination of the NAS (N1) for NAS encryption and integrity protection, registration management, connection management, reachability management, mobility management, lawful interception (for AMF events and interfaces to the LI system), transmission of SM messages between the UE and SMF, transparent proxy for routing SM messages, access authentication, access authorization, transmission of SMS messages between the UE and SMSF, SEAF, location service management for regulated services, transmission of location service messages between the UE and LMF and between the RAN and LMF, EPS bearer ID allocation for interoperability with EPS, UE mobility event notification, control plane CIoT 5GS optimization, user plane CIoT 5GS optimization, configuration of external parameters (expected UE behavior parameters or network configuration parameters) and / or network slice-specific authentication and authorization. Some or all of the AMF functions can be supported in a single instance of AMF 714. Regardless of the number of network functions, in some implementations, only one NAS interface instance per access network between the UE and the CN terminates with one of the network functions that implements at least NAS security and mobility management. AMF 714 may also include policy-related functions.

[0055] In addition to the functions described above, AMF 714 may also include the following functions supporting non-3GPP access networks: support for an N2 interface with N3IWF / TNGF, on which some information (e.g., 3GPP cell identifier) ​​and procedures (e.g., handover-related) defined on 3GPP access may not be applicable, and non-3GPP access-specific information not applicable to 3GPP access may be applied; support for NAS signaling by UE via N3IWF / TNGF, where some procedures supported by NAS signaling on 3GPP access may not be applicable to untrusted non-3GPP (e.g., paging) access; support for authentication of UEs connected via N3IWF / TNGF; management of mobility, authentication, and separate security context states for UEs connected via non-3GPP access or simultaneously via 3GPP access or non-3GPP access; support for effective coordination of RM management contexts on both 3GPP and non-3GPP access; and / or support for dedicated CM management contexts for UEs connecting via non-3GPP access. Support for all of the above functions may not be required in network slicing instances.

[0056] The SMF 716 supports session management (e.g., session establishment, modification, and release, including tunnel maintenance between UPF and AN nodes), UE IP address allocation and management (including optional authorization) (where UE IP addresses can be received from the UPF or from an external data network), DHCPv4 (server and client) and DHCPv6 (server and client) functions, the ability to respond to Address Resolution Protocol (ARP) requests and / or IPv6 neighbor request requests with local cached information based on Ethernet PDUs (e.g., the SMF responds to ARP and / or IPv6 neighbor request requests by providing the MAC address corresponding to the IP address sent in the request), selection and control of user plane functions (including controlling the UPF to proxy ARP or IPv6 neighbor discovery or forwarding all ARP / IPv6 neighbor request traffic to the SMF for Ethernet PDU sessions), traffic-directing configuration at the UPF to route traffic to the appropriate destination, and 5G VN group management (e.g., maintaining the topology of the involved PSA UPF, in the PSA...). Establishing and releasing N19 tunnels between UPFs, configuring traffic forwarding at the UPF to apply local handover, and / or N6-based or N19-based forwarding, terminating the interface for policy control functions, lawful interception (for SM events and interfaces to the LI system), charging data collection and support for charging interfaces, controlling and coordinating charging data collection at the UPF, terminating the SM portion of NAS messages, downlink data notification, initiator of AN-specific SM information sent to the AN via the AMF through N2, determination of the SSC mode of the session, control plane CIoT 5GS optimization, header compression, acting as an I-SMF in the deployment of insertable / removable / repositionable I-SMFs, configuring external parameters (expected UE behavior parameters or network configuration parameters), P-CSCF discovery for IMS services, roaming functions (e.g., handling local implementation to apply QoS). SLA (VPLMN), charging data collection and charging interface (VPLMN) and / or lawful interception (in the VPLMN for SM events and interfaces to LI systems), interaction with external DNs to transmit signaling for PDU session authentication / authorization for external DNs and / or instructing UPF and NG-RAN to perform redundant transmissions on N3 / N9 interfaces. Some or all of the SMF functions may be supported in a single instance of SMF. However, in some implementations, not all functions need to be supported in instances of network slices. In addition to functionality, SMF 716 may include policy-related functions.

[0057] SCP 718 includes one or more of the following functions: indirect communication; delegated discovery; message forwarding and routing to the destination NF / NF service; communication security (e.g., authorization for NF service consumers to access NF service manufacturer APIs), load balancing, monitoring, overload control, etc.; and / or optionally, interaction with a UDR to resolve UDM group ID / UDR group ID / AUSF group ID / PCF group ID / CHF group ID / HSS group ID based on UE identity (e.g., SUPI or IMPI / IMPU). Some or all of the SCP functions may be supported in a single instance of the SCP. In some implementations, SCP 718 may be deployed in a distributed manner and / or more than one SCP may exist in the communication path between NF services. SCPs may be deployed at the PLMN level, shared slice level, and slice-specific level. Carrier deployments may be left to ensure that the SCP can communicate with the relevant NRF.

[0058] UE 720 may include devices with radio communication capabilities. For example, UE 720 may include a smartphone (e.g., a handheld touchscreen mobile computing device that can connect to one or more cellular networks). UE 720 may also include any mobile or non-mobile computing device, such as a personal data assistant (PDA), pager, laptop computer, desktop computer, wireless phone, or any computing device that includes a wireless communication interface. UE is also referred to as a client, mobile phone, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, or reconfigurable mobile device. UE 720 may include an IoT UE, which may include a network access layer designed to utilize low-power IoT applications with short-lived UE connections. The IoT UE may exchange data with an MTC server or device via a PLMN, other UEs using ProSe or D2D communication, sensor networks, or IoT networks using technologies such as M2M, MTC, or mMTC. M2M or MTC data exchange may be machine-initiated data exchange. An IoT network describes interconnected IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure). IoT UEs may execute background applications (e.g., keeping track of activity messages, status updates, etc.) to facilitate connectivity within the IoT network.

[0059] UE 720 can be configured to connect or communicatively couple with (R)AN 722 via radio interface 730, which can be a physical communication interface or layer configured to operate using cellular communication protocols such as GSM, CDMA network protocols, push-to-talk (PTT), cellular PTT (POC), UMTS, 3GPP LTE, 5G, NR, etc. For example, UE 720 and (R)AN 722 can use a Uu interface (e.g., an LTE-Uu interface) to exchange control plane data via a protocol stack including PHY, MAC, RLC, PDCP, and RRC layers. DL transmissions can be made from (R)AN 722 to UE 720, and UL transmissions can be made from UE 720 to (R)AN 722. UE 720 can also use a sidelink to communicate directly with another UE (not shown) for D2D, P2P, and / or ProSe communication. For example, the ProSe interface may include one or more logical channels, including but not limited to the Physical Side Link Control Channel (PSCCH), Physical Side Link Shared Channel (PSSCH), Physical Side Link Discovery Channel (PSDCH), and Physical Side Link Broadcast Channel (PSBCH).

[0060] (R)AN 722 may include one or more access nodes, which may be referred to as a base station (BS), Node B, evolved Node B (eNB), next-generation Node B (gNB), RAN node, controller, Transmitter Receiving Point (TRP), etc., and may include ground stations (e.g., terrestrial access points) or satellite stations that provide coverage within a geographic area (e.g., a cellular base station). (R)AN 722 may include one or more RAN nodes for providing coverage for macrocell base stations, picocell base stations, femtocell base stations, or other types of cellular base stations. Macrocells may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow UEs to have unrestricted access with a service subscription. Picocells may cover a relatively small geographic area and may allow UEs to have unrestricted access with a service subscription. Femtocells may cover a relatively small geographic area (e.g., a home) and may allow restricted access for UEs associated with a femtocell (e.g., a UE in a Closed Subscriber Group (CSG), a UE of a user in a home, etc.).

[0061] Although not shown, multiple RAN nodes (such as (R)AN 722) may be used, with Xn interfaces defined between two or more nodes. In some specific implementations, the Xn interface may include an Xn user plane (Xn-U) interface and an Xn control plane (Xn-C) interface. Xn-U provides non-guaranteed delivery of user plane PDUs and supports / provides data forwarding and flow control functions. Xn-C provides management and error handling functions for managing the functionality of the Xn-C interface; mobility support for UE 720 in connected modes (e.g., CM-connected) includes functions for managing UE mobility in connected modes between one or more (R)AN nodes. This mobility support may include context transfer from the old (source) serving (R)AN node to the new (destination) serving (R)AN node; and control of user plane tunnels between the old (source) serving (R)AN node and the new (destination) serving (R)AN node.

[0062] The UPF 724 can serve as an anchor point for mobility within and between RATs, an external PDU session point interconnected with the DN 726, and a branch point supporting multihomed PDU sessions. The UPF 724 can also perform packet routing and forwarding, packet inspection, user plane portion enforcement of policy rules, lawful packet interception (UP collection), traffic usage reporting, QoS processing on the user plane (e.g., packet filtering, gating, UL / DL rate enforcement), uplink traffic authentication (e.g., SDF-to-QoS flow mapping), transport-level packet marking in uplink and downlink, and downlink packet buffering and downlink data notification triggering. The UPF 724 may include an uplink classifier to support routing traffic flows to the data network. The DN 726 may represent various network operator services, Internet access, or third-party services. The DN 726 may include, for example, an application server.

[0063] Figure 8 This is a block diagram of a configurable example UE 800 according to various embodiments of the present disclosure, including instructions that correspond to any of the example methods and / or processes described herein, which are executed on a computer-readable medium. The UE 800 includes one or more processors 802, transceivers 804, memory 806, a user interface 808, and a control interface 810.

[0064] The one or more processors 802 may include, for example, an application processor, an audio digital signal processor, a central processing unit, and / or one or more baseband processors. Each of the one or more processors 802 may include internal memory and / or may include an interface for communicating with external memory (including memory 806). The internal or external memory may store software code, programs, and / or instructions executable by the one or more processors 802 to configure and / or facilitate the UE 800 to perform various operations, including those described herein. For example, the execution of instructions may configure the UE 800 to communicate using one or more wired or wireless communication protocols (including one or more wireless communication protocols standardized by 3GPP, such as those commonly referred to as 5G / NR, LTE, LTE-A, UMTS, HSPA, GSM, GPRS, EDGE, etc.) or any other current or future protocols that can be used in conjunction with the one or more transceivers 804, user interface 808, and / or control interface 810. For example, the one or more processors 802 may execute program code stored in memory 806 or other memory corresponding to the MAC, RLC, PDCP, and RRC layer protocols standardized by 3GPP (e.g., for NR and / or LTE). Alternatively, the processor 802 may execute program code stored in memory 806 or other memory that, together with the one or more transceivers 804, implements the corresponding PHY layer protocol, such as Orthogonal Frequency Division Multiplexing (OFDM), Orthogonal Frequency Division Multiple Access (OFDMA), and Single Carrier Frequency Division Multiple Access (SC-FDMA).

[0065] Memory 806 may include memory regions for the one or more processors 802 to store variables used in the protocols, configurations, controls, and other functions of the UE 800 (including operations corresponding to or including any of the example methods and / or processes described herein). Furthermore, memory 806 may include non-volatile memory (e.g., flash memory), volatile memory (e.g., static or dynamic RAM), or combinations thereof. Additionally, memory 806 may interact with memory time slots through which one or more removable memory cards of various formats (e.g., SD cards, Memory Sticks, Compact Flash, etc.) can be inserted and removed.

[0066] The one or more transceivers 804 may include radio frequency transmitter and / or receiver circuitry that facilitates communication between the UE 800 and other devices supporting similar wireless communication standards and / or protocols. For example, the one or more transceivers 804 may include switches, mixer circuitry, amplifier circuitry, filter circuitry, and synthesizer circuitry. Such RF circuitry systems may include a receive signal path having circuitry for down-converting RF signals received from a front-end module (FEM) and providing baseband signals to the one or more processors 802. The RF circuitry may also include a transmit signal path that may include circuitry for up-converting the baseband signals provided by the baseband processor and providing an RF output signal for transmission to the FEM. The FEM may include a receive signal path that may include circuitry configured to operate on RF signals received from one or more antennas, amplify the received signals, and provide an amplified version of the received signals to the RF circuitry for further processing. The FEM may also include a transmit signal path that may include circuitry configured to amplify transmit signals provided by the RF circuitry for transmission by one or more antennas. In various implementations, amplification along the transmit or receive signal path can be performed only in the RF circuitry, only in the FEM, or in both the RF and FEM circuitries. In some implementations, the FEM circuitry may include a TX / RX switch to switch between transmit and receive mode operation.

[0067] In some exemplary embodiments, the one or more transceivers 804 include transmitters and receivers that enable the device 1200 to communicate with various 5G / NR networks according to various protocols and / or methods proposed for standardization by 3GPP and / or other standards bodies. For example, such functionality may operate cooperatively with the one or more processors 802 to implement a PHY layer based on OFDM, OFDMA, and / or SC-FDMA technologies, as described herein with reference to other figures.

[0068] User interface 808 may take various forms depending on the specific implementation, or may not be present in UE 800. In some implementations, user interface 808 includes a microphone, speaker, slide button, pressable button, display, touchscreen display, mechanical or virtual keypad, mechanical or virtual keyboard, and / or any other user interface features typically present on mobile phones. In other implementations, UE 800 may include a tablet computing device with a large touchscreen display. In such implementations, one or more mechanical features of user interface 808 may be replaced by equivalent or functionally equivalent virtual user interface features (e.g., virtual keypad, virtual buttons, etc.) implemented using a touchscreen display, as is well known to those skilled in the art. In other implementations, UE 800 may be a digital computing device, such as a laptop computer, desktop computer, workstation, etc., which includes a mechanical keyboard that can be integrated, detached, or removable according to a particular exemplary implementation. Such digital computing devices may also include a touchscreen display. Many example implementations of UE 800 with a touchscreen display are capable of receiving user input, such as input related to exemplary methods and / or processes described herein or known to those skilled in the art.

[0069] In some exemplary embodiments of this disclosure, the UE 800 may include an orientation sensor, which may be used in various ways by the features and functions of the UE 800. For example, the UE 800 may use the output of the orientation sensor to determine when a user has changed the physical orientation of the touchscreen display of the UE 800. An indication signal from the orientation sensor can be used by any application executing on the UE 800 to automatically change the orientation of the screen display (e.g., from portrait to landscape) when the indication signal indicates a change of approximately 90 degrees in the physical orientation of the device. In this way, the application is able to maintain the screen display in a user-readable manner regardless of the physical orientation of the device. Additionally, the output of the orientation sensor may be used in conjunction with various exemplary embodiments of this disclosure.

[0070] The control interface 810 may take various forms depending on the specific implementation. For example, the control interface 810 may include an RS-232 interface, an RS-485 interface, a USB interface, an HDMI interface, a Bluetooth interface, an IEEE (“FireWire”) interface, and an I / O interface. 2 Interfaces include C-type interfaces and PCMCIA interfaces. In some exemplary embodiments of this disclosure, control interface 1260 may include an IEEE 802.3 Ethernet interface, as described above. In some embodiments of this disclosure, control interface 810 may include analog interface circuitry, including, for example, one or more digital-to-analog (D / A) converters and / or analog-to-digital (A / D) converters.

[0071] Those skilled in the art will recognize that the list of features, interfaces, and radio frequency communication standards above is merely exemplary and not limited to the scope of this disclosure. In other words, UE 800 may include more than Figure 8 Further functionalities are shown, including, for example, a video and / or still image camera, microphone, media player, and / or recorder. Additionally, the one or more transceivers 804 may include circuitry for communicating using additional radio frequency communication standards, including Bluetooth, GPS, and / or others. Furthermore, the one or more processors 802 may execute software code stored in memory 806 to control such additional functionalities. For example, directional velocity and / or position estimates output from a GPS receiver can be used by any application executing on the UE 800, including various exemplary methods and / or computer-readable media according to various exemplary embodiments of this disclosure.

[0072] Figure 9 This is a block diagram of a configurable example network node 900 according to various embodiments of the present disclosure, including instructions executed on a computer-readable medium corresponding to any of the example methods and / or processes described herein.

[0073] Network node 900 includes one or more processors 902, a radio network interface 904, a memory 906, a core network interface 908, and other interfaces 910. Network node 900 may include, for example, a base station, eNB, gNB, access node, or components thereof.

[0074] The one or more processors 902 may include any type of processor or processing circuitry and may be configured to perform one of the methods or processes disclosed herein. Memory 906 may store software code, programs, and / or instructions executable by the one or more processors 902 to configure network node 900 to perform various operations, including those described herein. For example, execution of such stored instructions may configure network node 900 to communicate with one or more other devices using protocols (including one or more methods and / or processes described above) according to various embodiments of this disclosure. Furthermore, execution of such stored instructions may configure and / or facilitate network node 900 to communicate with one or more other devices using other protocols or protocol layers (such as one or more of the PHY, MAC, RLC, PDCP, and RRC layer protocols standardized by 3GPP for LTE, LTE-A, and / or NR, or any other higher-level protocols used in conjunction with radio network interface 904 and core network interface 908). By way of example, and not limitation, core network interface 908 includes an S1 interface, and radio network interface 904 may include a Uu interface, as standardized by 3GPP. The memory 906 may also store variables used in the protocols, configurations, control, and other functions of the network node 900. Therefore, the memory 906 may include non-volatile memory (e.g., flash memory, hard disk, etc.), volatile memory (e.g., static or dynamic RAM), network-based (e.g., "cloud") storage devices, or combinations thereof.

[0075] The radio network interface 904 may include a transmitter, receiver, signal processor, ASIC, antenna, beamforming unit, and other circuitry enabling the network node 900 to communicate with other equipment (such as multiple compatible user equipment (UEs) in some embodiments). In some embodiments, the network node 900 may include various protocols or protocol layers, such as the PHY, MAC, RLC, PDCP, and RRC layer protocols standardized by 3GPP for LTE, LTE-A, and / or 5G / NR. According to further embodiments of this disclosure, the radio network interface 904 may include a PHY layer based on OFDM, OFDMA, and / or SC-FDMA technologies. In some embodiments, the functionality of such a PHY layer may be provided cooperatively by the radio network interface 904 and the one or more processors 902.

[0076] The core network interface 908 may include transmitters, receivers, and other circuitry enabling the network node 900 to communicate with other equipment in the core network (in some embodiments, such as circuit-switched (CS) and / or packet-switched (PS) networks). In some embodiments, the core network interface 908 may include an S1 interface standardized by 3GPP. In some embodiments, the core network interface 908 may include one or more interfaces to one or more SGW, MME, SGSN, GGSN, and other physical devices, including functions known to those skilled in the art in GERAN, UTRAN, E-UTRAN, and CDMA2000 core networks. In some embodiments, these one or more interfaces may be multiplexed together on a single physical interface. In some embodiments, the lower layers of the core network interface 908 may include one or more of Asynchronous Transfer Mode (ATM), Internet Protocol over Ethernet (IP), SDH over fiber, T1 / E1 / PDH over copper, microwave radio, or other wired or wireless transmission technologies known to those skilled in the art.

[0077] Other interfaces 910 may include transmitters, receivers, and other circuitry that enables network node 900 to communicate with external networks, computers, databases, etc., for the operation, management, and maintenance of network node 900 or other network equipment operatively connected thereto.

[0078] Figure 10 An exemplary IAB network 1000 is schematically illustrated, comprising an IAB donor 1002 and five IAB nodes: a first node 1004 (node ​​1), a second node 1006 (node ​​2), a third node 1008 (node ​​3), a fourth node 1010 (node ​​4), and a fifth node 1012 (node ​​5). As used herein, IAB nodes may also be referred to as relay nodes. Relay nodes may receive uplink traffic (indicated by arrows) from downlink or sub-relay nodes (or from UEs) and provide uplink traffic to a parent relay node. Uplink traffic from UEs associated with three users (user A 1014, user B 1016, and user C 1018) is routed through the exemplary IAB network 1000. Users A and B are attached to the fifth node 1012, and user C is attached to the fourth node 1010. User A's uplink traffic is routed through the fourth node 1010, the second node 1006, and the first node 1004. User B's uplink traffic is routed through the fourth node 1010, the third node 1008, and the first node 1004. User C's uplink traffic is routed through the second node 1006 and the first node 1004. Although Figure 10The arrows shown represent uplink traffic, but those skilled in the art will recognize from the disclosure herein that IAB nodes can also be used for downlink traffic. See, for example... Figure 12 Description of the exemplary IAB architecture 1200.

[0079] Figure 11 An exemplary protocol architecture for IAB 1100 according to one embodiment is illustrated. The exemplary protocol architecture of IAB 1100 shows various protocol layers for UE 1102, first IAB node 1104 (IAB node 1), second IAB node 1106 (IAB node 2), and IAB donor 1108. These layers may correspond to mobile terminal (MT), distributed unit (DU), or centralized unit (CU)-user plane (UP) entities. The DU and CU-UP of IAB donor 1108 can communicate via the donor's in-feed F1-U interface. In this example, UE 1102 wirelessly communicates with second IAB node 1106 via the UE's dedicated radio bearer (DRB), and second IAB node 1106 wirelessly relays uplink traffic to first IAB node 1104 via a backhaul (BH) radio link control (RLC) channel. Protocol layers include, for example, Media Access Control (MAC), RLC, Packet Data Convergence Protocol (PDCP), Service Data Adaptation Protocol (SDAP), Internet Protocol (IP), User Datagram Protocol (UDP), and General Packet Radio Service (GPRS) Tunneling Protocol User Plane (GTP-U).

[0080] The exemplary protocol architecture used for IAB 1100 also includes a Backhaul Adaptation Protocol (BAP) layer, which provides functionality for routing data for different UEs across different routes over the network. This is accomplished via an adaptation layer header that includes some information for identifying the bearer. The routing involves mapping incoming data to outgoing links based on the bearer identifier.

[0081] Given that different UE bearers can be carried on different routes via the network, in some implementations, the buffer occupancy state generated by the node is only related to the bearers routed through that node and the IAB nodes on those routes.

[0082] Figure 12An exemplary IAB architecture 1200 according to one embodiment is illustrated. The exemplary IAB architecture 1200 includes a 5GC 1202, a donor node 1204, multiple IAB nodes (six IAB nodes, shown as IAB relay nodes 1206), and multiple UEs (six UEs, shown as UE 1208). The donor node 1204 may include a centralized unit (CU, shown as CU 1210) and a distributed unit (DU, shown as DU 1212). CU 1210 may be divided into, for example, a control plane CU and a user plane CU. Furthermore, although only one DU 1212 is shown, DU 1212 may include multiple distributed units. As shown, solid lines between CU 1210 and 5GC 1202 and DU 1212 may represent wired links (e.g., fiber optic links), while dashed lines may represent wireless links.

[0083] Each IAB relay node 1206 (also referred to herein as an IAB RN or “relay transmit / receive point” or “rTRP”) is a network node in an IAB deployment that has UE functionality and (at least a portion thereof) gNB functionality. As shown, some IAB RNs access other IAB RNs, and some IAB RNs access donor node 1204. An IAB DN (or IAB donor, also referred to as an “anchor node”, etc.) is a network node in an IAB deployment that terminates its NG interface via a wired connection. An IAB DN is a RAN node that provides the UE interface to the core network (shown as 5GC 1202) and provides radio backhaul functionality to the IAB nodes. IAB nodes are relay nodes and / or RAN nodes that support radio access UE and radio backhaul access traffic.

[0084] In the implementation, the IAB system architecture supports multi-hop backhaul. IAB multi-hop backhaul provides a greater range of scalability than single-hop systems. Multi-hop backhaul also enables backhaul around obstacles (e.g., buildings haphazardly deployed in an urban environment). The maximum number of hops expected in a deployment depends on many factors, such as frequency, cell density, propagation environment, traffic load, various key performance indicators (KPIs), and / or other similar factors. From an architectural perspective, hop count flexibility is desirable, therefore the IAB system does not impose limitations on the number of backhaul hops.

[0085] The IAB system architecture also supports topology adaptation. Topology adaptation refers to the process of autonomously reconfiguring the backhaul network without interrupting service to the UE and / or mitigating service interruptions in situations such as congestion or local congestion. For example, wireless backhaul links may be susceptible to congestion due to moving objects such as vehicles, weather-related events (e.g., seasonal changes (leafingers), infrastructure changes (e.g., new buildings), etc. These vulnerabilities can exist in physically stationary IAB nodes and / or mobile IAB nodes. In addition, traffic variations can create uneven load distribution on the wireless backhaul links, leading to local link or node congestion.

[0086] In implementations supporting multi-hop and topology adaptation, IAB nodes include topology management mechanisms and routing selection and optimization (RSO) mechanisms. Topology management mechanisms include protocol stacks, interfaces between rTRPs or IAB nodes, controls and user plane procedures for identifying one or more hops in the IAB network, traffic forwarding via one or more radio backhaul links in the IAB network, QoS handling, etc. RSO mechanisms include mechanisms for discovering and managing backhaul links of TRPs with integrated backhaul and access capabilities; RAN-based mechanisms for supporting dynamic routing (potentially without core network involvement) to accommodate short-term blocking and transmission of latency-sensitive traffic across the entire backhaul link; and mechanisms for evaluating end-to-end RSO across different resource allocations / routing across multiple nodes.

[0087] Operation of different links can be performed at the same frequency (“in-band”) or different frequencies (“out-of-band”). In-band backhaul includes scenarios where the access link and backhaul link overlap at least partially in frequency, resulting in half-duplex or interference constraints, which may mean that the IAB node may not be transmitting and receiving simultaneously on both links. In contrast, out-of-band scenarios may not have such constraints. In the implementation, one or more of the IAB nodes include mechanisms for dynamically allocating resources between the backhaul link and the access link, including mechanisms for efficiently multiplexing the access link and the backhaul link (for both DL and UL directions) in time, frequency, or space under per-link half-duplex constraints on one or more backhaul link hops in both TDD and FDD operations; and crosslink interference (CLI) measurement, coordination, and suppression between the rTRP and the UE.

[0088] Figure 13An NG-RAN architecture 1300 according to one embodiment is shown, which includes 5GC 1302 and NG-RAN 1304. NG-RAN 1304 includes multiple gNBs (two gNBs shown as gNB 1306 and gNB 1308) connected to 5GC 1302 via NG interfaces. gNB 1306 and gNB 1308 can support FDD mode, TDD mode, or dual-mode operation and are connected to each other via Xn-C interfaces. As shown, gNB 1308 includes a gNB-CU 1310 connected to gNB-DU 1312 and gNB-DU 1314 via an F1 interface. gNB 1308 may include only a single gNB-DU or more than the two shown. The NG interface, Xn-C interface, and F1 interface are logical interfaces.

[0089] For one or more embodiments, at least one of the components shown in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes, and / or methods described in the Embodiments section below. For example, the baseband circuitry described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples below. As another example, circuitry associated with the UE, base station, network element, etc., described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples shown in the Examples section below.

[0090] Example Section

[0091] The following examples relate to other implementation schemes.

[0092] Example 1 is a method for selecting a parent cell in a wireless network for an Integrated Access and Backhaul (IAB) node. The method includes: processing system information, the system information including a first set of cell selection criteria corresponding to a non-IAB User Equipment (UE) and a second set of cell selection criteria corresponding to an IAB Mobile Terminal (MT) UE; measuring a cell to obtain cell measurement results; determining whether cell selection conditions are met based on the cell measurement results and the second set of cell selection criteria corresponding to the IAB MT UE; and selecting the cell for wireless backhaul communication, at least in part based on the determination that the cell selection conditions are met.

[0093] Example 2 includes the method of Example 1, wherein determining whether the cell selection condition is satisfied includes: calculating a value Srxlev based on a measured cell reception (RX) level value from the cell measurement results; and calculating a value Squal based on a measured cell quality value from the cell measurement results; wherein the cell selection condition is satisfied when the value Srxlev and the value Squal exceed 0, wherein the value Srxlev...

[0094] Example 3 includes the method of Example 2, wherein the value Srxlev is at least partially determined as Qrxlevmeas – (Qrxlevmin_iab_Node + Qrxlevminoffset_iab_Node), wherein: Qrxlevmeas includes the measured cell RX level value; Qrxlevmin_iab_Node includes a threshold from the second set of cell selection criteria of the IAB node indicating the minimum RX level in the cell; and Qrxlevminoffset_iab_Node includes an offset value from the second set of cell selection criteria of the IAB node indicating the offset of Qrxlevmin_iab_Node.

[0095] Example 4 includes the method of Example 3, wherein the value Srxlev further depends on the parameter PMax_iab_Node associated with the maximum transmit (TX) power of the IAB node from the second set of cell selection criteria of the IAB node.

[0096] Example 5 includes the method of Example 3, wherein the measured cell RX level value includes the reference signal received power (RSRP).

[0097] Example 6 includes the method of Example 2, wherein the value Squal is at least partially determined as Qqualmeas – (Qqualmin_iab_Node + Qqualminoffset_iab_Node), wherein: Qqualmeas includes a measured cell quality value from cell measurement results; Qqualmin_iab_Node includes a threshold from the second set of cell selection criteria of the IAB node indicating the minimum quality level in the cell; and Qqualminoffset_iab_Node includes an offset value from the second set of cell selection criteria of the IAB node indicating an offset from Qqualmin_iab_Node.

[0098] Example 7 includes the method of Example 6, wherein the measured cell quality value includes Reference Signal Received Quality (RSRQ).

[0099] Example 8 includes the method of Example 1, further comprising: processing a first message from a second IAB node at the IAB node, the first message including an indication of the number of hops from the second IAB node to the IAB donor node; and using the indication of the number of hops in a decision to select the cell corresponding to the second IAB node for wireless backhaul communication.

[0100] Example 9 includes the method of Example 8, further comprising: after connecting to the second IAB, broadcasting a second message from the IAB node to indicate a new hop count from the IAB node through the second IAB node to the IAB donor node.

[0101] Example 10 includes the method of Example 1, and further includes selecting the cell for measurement based on the IAB donor node priority metric to obtain the cell measurement result.

[0102] Example 11 includes the method of Example 1, and further includes selecting the cell for wireless backhaul communication on a second cell based at least in part on the IAB donor node priority metric.

[0103] Example 12 includes the method of Example 10 or Example 11, wherein the IAB donor node is broadcast using dedicated signaling or is overridden by individual priorities.

[0104] Example 13 includes the method of Example 1, wherein the IAB node is configured to enter an inactive state of the RRC connection, rather than entering an RRC idle state.

[0105] Example 14 is an apparatus for a first Integrated Access and Backhaul (IAB) node in a wireless network. The apparatus includes a processor and a memory storing instructions, which, when executed by the processor, configure the apparatus to: process at the first IAB node a first message from a second IAB node, the first message including an indication of the number of hops from the second IAB node to an IAB donor node; and to use the indication of the number of hops in a decision regarding a cell attached to the cell corresponding to the second IAB node.

[0106] Example 15 includes the apparatus of Example 14, wherein the instructions further configure the apparatus to: after connecting to the second IAB, broadcast a second message from the first IAB node to indicate a new hop count from the first IAB node through the second IAB node to the IAB donor node.

[0107] Example 16 is a method comprising: determining an Integrated Access and Backhaul (IAB) donor node metric; and using the IAB donor node metric to identify and prioritize the selection or reselection of a specific IAB donor node among a plurality of IAB donor nodes.

[0108] Example 17 includes the method of Example 16, wherein the IAB donor node metric is broadcast from the plurality of IAB donor nodes.

[0109] Example 18 includes the method of Example 17, wherein the IAB donor node metric is broadcast in the information element (IE) of a System Information Block (SIB) message.

[0110] Example 19 includes the method of Example 17, wherein the IAB donor node metric is based on the current load of the plurality of IAB donor nodes.

[0111] Example 20 includes the method of Example 16, wherein determining the IAB donor node metric includes receiving the IAB donor node metric in a dedicated signaling message.

[0112] Example 21 is a computer-readable storage medium comprising instructions that, when executed by a computer in a wireless network including multiple Integrated Access and Backhaul (IAB) nodes, cause the computer to: establish a connection among multiple IAB nodes in a tree including parent and child nodes in Radio Resource Control (RRC) connection mode; and, upon individually exiting the RRC connection mode, keep the multiple IAB nodes in an inactive state of the RRC connection, rather than an RRC idle state.

[0113] Example 22 may include an apparatus comprising means for performing one or more elements of the method or any other method or process described herein, as described in any of the above examples or related to them.

[0114] Example 23 may include one or more non-transitory computer-readable media, which include instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of the method or any other method or process described herein, as described in any of the above embodiments or related to them.

[0115] Example 24 may include an apparatus comprising one or more elements of a logic component, module, or circuit for performing one or more of the methods or processes described in or associated with any of the above examples or any other methods or processes described herein.

[0116] Example 25 may include any method, technique, or process, or part or component thereof, that is described in or related to any of the above examples.

[0117] Example 26 may include an apparatus comprising one or more processors and one or more computer-readable media, the one or more computer-readable media including instructions that, when executed by the one or more processors, cause the one or more processors to perform any of the methods, techniques, or processes or portions thereof described or associated with any of the above embodiments.

[0118] Example 27 may include any signal or part or component thereof that is described or associated with any of the above examples.

[0119] Embodiment 28 may include datagrams, packets, frames, segments, protocol data units (PDUs) or messages or parts or components thereof as described in or related to any of the above embodiments, or otherwise described in this disclosure.

[0120] Example 29 may include a data-encoded signal or part or component thereof that is in or related to any of the above examples, or otherwise described in this disclosure.

[0121] Embodiment 30 may include a signal or part or component thereof encoded as a datagram, packet, frame, segment, PDU or message as described in any of the above embodiments or in connection with them, or otherwise described in this disclosure.

[0122] Example 31 may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors will cause the one or more processors to perform any of the methods, techniques or processes or portions thereof described in or related to any of the above examples.

[0123] Example 32 may include a computer program comprising instructions, wherein execution of the program by a processing element will cause the processing element to perform any of the methods, techniques, or processes or portions thereof described in or associated with any of the above embodiments.

[0124] Example 33 may include signals in a wireless network as shown and described herein.

[0125] Example 34 may include methods for communicating in a wireless network as shown and described herein.

[0126] Example 35 may include a system for providing wireless communication as shown and described herein.

[0127] Example 36 may include a device for providing wireless communication as shown and described herein.

[0128] Unless otherwise expressly stated, any of the above embodiments may be combined with any other embodiment (or combination of embodiments). The foregoing description of one or more specific embodiments provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise forms disclosed. In view of the teachings above, modifications and variations are possible, or modifications and variations may be obtained from the practice of various embodiments.

[0129] Implementations and specific embodiments of the systems and methods described herein may include various operations embodied in machine-executable instructions to be executed by a computer system. The computer system may include one or more general-purpose or special-purpose computers (or other electronic devices). The computer system may include hardware components, including specific logical components for performing the operations, or may include a combination of hardware, software, and / or firmware.

[0130] It should be recognized that the systems described herein include descriptions of specific implementations. These implementations may be combined into a single system, partially integrated into other systems, divided into multiple systems, or otherwise partitioned or combined. Furthermore, it is conceivable to use parameters, attributes, aspects, etc., of one implementation in another implementation. For clarity, these parameters, attributes, aspects, etc., are described only in one or more implementations, and it should be recognized that unless specifically stated herein, these parameters, attributes, aspects, etc., may be combined with or substituted for parameters, attributes, aspects, etc., of another implementation.

[0131] As is widely recognized, the use of personally identifiable information should comply with privacy policies and practices that are generally accepted to meet or exceed industry or governmental requirements for protecting user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly explained to users.

[0132] Although the foregoing has been described in considerable detail for clarity, it will be apparent that certain changes and modifications can be made without departing from the principles of the invention. It should be noted that many alternative ways exist to implement both the processes and apparatus described herein. Therefore, embodiments of the invention should be considered illustrative rather than restrictive, and this specification is not limited to the details given herein, but can be modified within the scope of the appended claims and their equivalents.

Claims

1. A method for selecting a parent cell in a wireless network for integrated access and backhaul (IAB) nodes, the method comprising: The system information is processed, including a first set of cell selection criteria corresponding to a non-IAB user equipment UE and a second set of cell selection criteria corresponding to an IAB mobile terminal MT UE. Measure the cell to obtain cell measurement results; The cell selection criteria are determined based on the cell measurement results and the second set of cell selection criteria corresponding to the IAB MT UE to determine whether the cell selection conditions are met. as well as The cell is selected for wireless backhaul communication, at least in part, based on the determination that the cell selection criteria are met.

2. The method of claim 1, wherein determining whether the cell selection condition is met includes: The value Srxlev is calculated based on the measured cell received RX level value from the cell measurement results. as well as The value Squal is calculated based on the measured cell quality value from the cell measurement results. The cell selection condition is satisfied when the values ​​Srxlev and Squal exceed 0, wherein the value Srxlev is...

3. The method of claim 2, wherein the value Srxlev is at least partially determined as Qrxlevmeas – (Qrxlevmin_iab_Node + Qrxlevminoffset_iab_Node), where: Qrxlevmeas includes the measured cell RX level value; Qrxlevmin_iab_Node includes a threshold from the second set of cell selection criteria of the IAB node indicating the minimum RX level in the cell; and Qrxlevminoffset_iab_Node includes the offset value of the second set of cell selection criteria from the IAB node relative to the offset of Qrxlevmin_iab_Node.

4. The method of claim 3, wherein the value Srxlev further depends on the parameter PMax_iab_Node associated with the maximum transmit TX power of the IAB node from the second set of cell selection criteria of the IAB node.

5. The method of claim 3, wherein the measured cell RX level value includes the reference signal received power RSRP.

6. The method of claim 2, wherein the value Squal is at least partially determined as Qqualmeas – (Qqualmin_iab_Node + Qqualminoffset_iab_Node), where: Qqualmeas includes the measured cell quality value derived from the cell measurement results; Qqualmin_iab_Node includes a threshold from the second set of cell selection criteria of the IAB node indicating the minimum quality level in the cell; and Qqualminoffset_iab_Node) includes the offset value of the second set of cell selection criteria from the IAB node relative to the offset of Qqualmin_iab_Node.

7. The method of claim 6, wherein the measured cell quality value includes Reference Signal Received Quality (RSRQ).

8. The method according to claim 1, further comprising: At the IAB node, a first message from the second IAB node is processed, the first message including an indication of the number of hops from the second IAB node to the IAB donor node; as well as The indication of the hop count is used in the decision to select the cell corresponding to the second IAB node for wireless backhaul communication.

9. The method of claim 8, further comprising, after connecting to the second IAB, broadcasting a second message from the IAB node to indicate a new hop count from the IAB node through the second IAB node to the IAB donor node.

10. The method of claim 1, further comprising selecting the cell for measurement based on the IAB donor node priority metric to obtain the cell measurement result.

11. The method of claim 1, further comprising selecting the cell for wireless backhaul communication on the second cell based at least in part on an IAB donor node priority metric.

12. The method of claim 10 or claim 11, wherein the IAB donor node is broadcast using dedicated signaling or is overridden by individual priorities.

13. The method of claim 1, wherein the IAB node is configured to enter an inactive state of the RRC connection, rather than an RRC idle state.

14. An apparatus for a first integrated access and backhaul (IAB) node in a wireless network, the apparatus comprising: processor; as well as The memory stores instructions that, when executed by the processor, configure the device to: At the first IAB node, a first message from the second IAB node is processed. This first message includes an indication of the depth in a tree containing multiple nodes, where the depth is indicated as a 3D matrix of hops, idle load, and connection load. The indication of the depth will be used in the decision-making process for the cell attached to the corresponding second IAB node.

15. The apparatus of claim 14, wherein the instructions further configure the apparatus to: after connecting to the second IAB, broadcast a second message from the first IAB node to indicate a new hop count from the first IAB node through the second IAB node to the IAB donor node.

16. A method for communication, the method comprising: Determine the metrics for integrated access and backhaul IAB donor nodes; as well as The IAB donor node metric is used to identify and prioritize the selection or reselection of a specific IAB donor node among a plurality of IAB donor nodes, wherein the IAB donor node metric is based on the current load of the plurality of IAB donor nodes.

17. The method of claim 16, wherein the IAB donor node metric is broadcast from the plurality of IAB donor nodes.

18. The method of claim 17, wherein the IAB donor node metric is broadcast in the information element IE of the System Information Block (SIB) message.

19. The method of claim 16, wherein determining the IAB donor node metric includes receiving the IAB donor node metric in a dedicated signaling message.

20. A computer-readable storage medium comprising instructions that, when executed by a computer in a wireless network including a plurality of Integrated Access and Backhaul (IAB) nodes, cause the computer to: Establish connections between multiple IAB nodes in a tree, including parent and child nodes in Radio Resource Control (RRC) connection mode; and When exiting the RRC connection mode individually, the plurality of IAB nodes, including the parent node and the child node, are kept in an inactive state of the RRC connection, rather than an RRC idle state.

Images