Method and apparatus for mobile IAB-mt barring management in a wireless communication system

Abstract

A method of a terminal, wherein the terminal is capable of acting as a mobile integrated access and backhaul mobile terminal (mIAB-MT), the method comprising determining to access a cell that is not broadcasting information indicating that the cell supports mobile IAB and in response to determining to access the cell that is not broadcasting information indicating that the cell supports mobile IAB, accessing the cell as a user equipment (UE) or accessing the cell as an IAB-MT.

Description

METHOD AND APPARATUS FOR MOBILE IAB-MT BARRING MANAGEMENT IN A WIRELESS COMMUNICATION SYSTEM

[0001] The present disclosure relates to a communication system, and more particularly, and more particularly, to a method and device for efficiently performing a wireless network function. Furthermore, the disclosure provides one or more techniques for mobile IAB-MT barring management, for example in a 3rd Generation Partnership Project (3GPP) 5th Generation (5G) New Radio (NR) network.

[0002] Considering the development of wireless communication from generation to generation, the technologies have been developed mainly for services targeting humans, such as voice calls, multimedia services, and data services. Following the commercialization of 5G (5th-generation) communication systems, it is expected that the number of connected devices will exponentially grow. Increasingly, these will be connected to communication networks.

[0003] Examples of connected things may include vehicles, robots, drones, home appliances, displays, smart sensors connected to various infrastructures, construction machines, and factory equipment. Mobile devices are expected to evolve in various form-factors, such as augmented reality glasses, virtual reality headsets, and hologram devices. In order to provide various services by connecting hundreds of billions of devices and things in the 6G (6th-generation) era, there have been ongoing efforts to develop improved 6G communication systems. For these reasons, 6G communication systems are referred to as beyond-5G systems.

[0004] 6G communication systems, which are expected to be commercialized around 2030, will have a peak data rate of tera (1,000 giga)-level bps and a radio latency less than 100μsec, and thus will be 50 times as fast as 5G communication systems and have the 1 / 10 radio latency thereof.

[0005] In order to accomplish such a high data rate and an ultra-low latency, it has been considered to implement 6G communication systems in a terahertz band (for example, 95GHz to 3THz bands). It is expected that, due to severer path loss and atmospheric absorption in the terahertz bands than those in mmWave bands introduced in 5G, technologies capable of securing the signal transmission distance (that is, coverage) will become more crucial. It is necessary to develop, as major technologies for securing the coverage, radio frequency (RF) elements, antennas, novel waveforms having a better coverage than orthogonal frequency division multiplexing (OFDM), beamforming and massive multiple input multiple output (MIMO), full dimensional MIMO (FD-MIMO), array antennas, and multiantenna transmission technologies such as large-scale antennas. In addition, there has been ongoing discussion on new technologies for improving the coverage of terahertz-band signals, such as metamaterial-based lenses and antennas, orbital angular momentum (OAM), and reconfigurable intelligent surface (RIS).

[0006] Moreover, in order to improve the spectral efficiency and the overall network performances, the following technologies have been developed for 6G communication systems: a full-duplex technology for enabling an uplink transmission and a downlink transmission to simultaneously use the same frequency resource at the same time; a network technology for utilizing satellites, high-altitude platform stations (HAPS), and the like in an integrated manner; an improved network structure for supporting mobile base stations and the like and enabling network operation optimization and automation and the like; a dynamic spectrum sharing technology via collison avoidance based on a prediction of spectrum usage; an use of artificial intelligence (AI) in wireless communication for improvement of overall network operation by utilizing AI from a designing phase for developing 6G and internalizing end-to-end AI support functions; and a next-generation distributed computing technology for overcoming the limit of UE computing ability through reachable super-high-performance communication and computing resources (such as mobile edge computing (MEC), clouds, and the like) over the network. In addition, through designing new protocols to be used in 6G communication systems, developing mecahnisms for implementing a hardware-based security environment and safe use of data, and developing technologies for maintaining privacy, attempts to strengthen the connectivity between devices, optimize the network, promote softwarization of network entities, and increase the openness of wireless communications are continuing.

[0007] It is expected that research and development of 6G communication systems in hyper-connectivity, including person to machine (P2M) as well as machine to machine (M2M), will allow the next hyper-connected experience. Particularly, it is expected that services such as truly immersive extended reality (XR), high-fidelity mobile hologram, and digital replica could be provided through 6G communication systems. In addition, services such as remote surgery for security and reliability enhancement, industrial automation, and emergency response will be provided through the 6G communication system such that the technologies could be applied in various fields such as industry, medical care, automobiles, and home appliances.

[0008] According to an embodiment of the disclosure, a method of a terminal is provided. The terminal may be capable of acting as a mobile integrated access and backhaul mobile terminal (mIAB-MT). The method may comprise determining to access a cell that is not broadcasting information indicating that the cell supports mobile IAB; in response to determining to access the cell that is not broadcasting information indicating that the cell supports mobile IAB, accessing the cell as a user equipment (UE) or accessing the cell as an IAB-MT.

[0009] According to an embodiment of the disclosure, a terminal capable of acting as a mobile integrated access and backhaul mobile terminal (mIAB-MT) is provided. The terminal may comprise a transceiver and at least one processor coupled to the transceiver. The terminal may be configured to determine to access a cell that is not broadcasting information indicating that the cell supports mobile IAB; in response to determining to access the cell that is not broadcasting information indicating that the cell supports mobile IAB, access the cell as a user equipment (UE) or accessing the cell as an IAB-MT

[0010] According to an embodiment of the disclosure, a computer program comprising instructions which, when the program is executed by a computer or processor, cause the computer or processor to carry out the method.

[0011] According to an embodiment of the disclosure, a computer or processor-readable data carrier having stored thereon a computer program is provided.

[0012] Figure 1 illustrates an two-hop IAB network, according to an embodiment of the disclosure;

[0013] Figure 2 illustrates an mIAB node entering an area where cells do not support mIAB, according to an embodiment of the disclosure;

[0014] Figure 3 illustrates a flowchart of method for allowing an mIAB-MT device to access a network not broadcasting mobileIAB-Support, according to an embodiment of the disclosure;

[0015] Figure 4 illustrates a call flow of an method in which an mIAB node is redirected to another network supporting mIAB, according to an embodiment of the disclosure;

[0016] Figure 5 illustrates a flowchart of an method of a terminal, according to an embodiment of the disclosure; and

[0017] Figure 6 illustrates a block diagram of an network entity, according to an embodiment of the disclosure.

[0018] Throughout the disclosure, the expression "at least one of a, b or c" indicates only a, only b, only c, both a and b, both a and c, both b and c, all of a, b, and c, or variations thereof.

[0019] Hereinafter, embodiments of the disclosure will be described in detail with reference to the accompanying drawings. As the present description allows for various changes and numerous embodiments of the disclosure, certain embodiments of the disclosure will be illustrated in the drawings and described in detail in the written description. However, this is not intended to limit the embodiments of the disclosure, and it will be understood that the disclosure includes all modifications, equivalents, and substitutes falling within the spirit and scope of various embodiments of the disclosure. In this disclosure, "examples" and "embodiments" may be used interchangeably.

[0020] In describing embodiments of the disclosure, when the detailed description of the relevant known functions or configurations is determined to unnecessarily obscure the gist of the disclosure, the detailed description thereof may be omitted herein. Furthermore, numbers (e.g., first, second, etc.) used in the description of the specification are merely identification symbols for distinguishing one element from another.

[0021] As for the terms as used in embodiments of the disclosure, common terms that are currently widely used are selected as much as possible while taking into account the functions of the disclosure. However, the terms may vary depending on the intention of those of ordinary skill in the art, precedents, the emergence of new technology, and the like. Also, in a specific case, there are also terms arbitrarily selected by the applicant. In this case, the meaning of the terms will be described in detail in the description of embodiments of the disclosure. Therefore, the terms as used herein should be defined based on the meaning of the terms and the description throughout the disclosure rather than simply the names of the terms.

[0022] The scope of the disclosure may be defined by the appended claims rather than the detailed description. Various features stated in one claim category (e.g., a method claim) of the disclosure may also be claimed in other claim categories (e.g., a system claim). In addition, an embodiment of the disclosure may include various combinations of individual features within the claims as well as combinations of features specified in the appended claims. All changes or modifications derived from the meaning and scope of the claims and equivalent concepts thereof should be construed as falling within the scope of the disclosure.

[0023] Also, when one element is referred to as being "connected" or "coupled" to another element, the one element may be directly connected or coupled to the other element, but it will be understood that the elements may be connected or coupled to each other via an intervening element therebetween unless otherwise stated. Also, when one element is referred to as being "directly connected" or "physically connected" to another element, it will be understood that the one element may be "electrically connected to" the other element with an intervening element there between. Throughout the disclosure, the terms "transmit," "receive," and "communicate" may include both direct communication and indirect communication. Throughout the disclosure, the expression "a portion includes a certain element" means that a portion further includes other elements rather than excludes other elements unless otherwise stated.

[0024] Also, an element represented by "unit," "module," etc. in the disclosure may be one element in which two or more elements are combined, or may be divided into two or more element for each more subdivided function. These functions may be implemented as hardware or software, or may be implemented as a combination of hardware and software. Also, each of the elements to be described below may additionally perform, in addition to the main function thereof, some or all of the functions that other elements are responsible for, and some of the main functions that the respective elements are responsible for may be dedicated by other elements.

[0025] The singular forms as used herein are intended to include the plural forms as well unless the context clearly indicates otherwise. All terms including technical or scientific terms as used herein have the same meaning as commonly understood by those of ordinary skill in the art.

[0026] Throughout the disclosure, the term "or" is inclusive and not exclusive unless otherwise stated. Therefore, the expression "A or B" may indicate "A," "B," or "both A and B" unless the context clearly indicates otherwise. Throughout the disclosure, the expression "at least one of" or "one or more of" refer to a case where different combinations of one or more of the listed items may be used, or only one of the listed items is required. For example, the expression "at least one of A, B, and C" may include only A, only B, only C, A and B, A and C, B and C, or all of A, B, and C.

[0027] It will be understood that the respective blocks of flowcharts and combinations of the flowcharts may be performed by computer program instructions. Because these computer program instructions may be embedded in a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatuses, the instructions to be executed through the processor of the computer or other programmable data processing apparatus generate modules for performing the functions described in the flowchart block(s). Because these computer program instructions may also be stored in a computer-executable or computer-readable memory that may direct the computer or other programmable data processing apparatus so as to implement functions in a particular manner, the instructions stored in the computer-executable or computer-readable memory are also capable of producing an article of manufacture containing instruction modules for performing the functions described in the flowchart block(s). Because the computer program instructions may also be embedded in the computer or other programmable data processing apparatus, the instructions for executing the computer or other programmable data processing apparatuses by generating a computer-implemented process by performing a series of operations on the computer or other programmable data processing apparatuses may provide operations for executing the functions described in the flowchart block(s).

[0028] Also, each block may represent part of a module, segment, or code that includes one or more executable instructions for executing a specified logical function(s). It should also be noted that, in some alternative implementations, the functions described in the blocks may occur out of the order noted in the drawings. For example, two blocks illustrated in succession may in fact be executed substantially concurrently, or the blocks may sometimes be executed in a reverse order, depending on the functions involved therein.

[0029] Hereinafter, embodiments of the disclosure will be described with reference to the accompanying drawings, so that those of ordinary skill in the art may easily carry out the disclosure. However, the disclosure may be implemented in various different forms and is not limited to the embodiments described herein. In order to clearly explain the disclosure, parts irrelevant to the description are omitted in the drawings, and similar reference numerals are assigned to similar parts throughout the specification.

[0030] Also, although a long-term evolution (LTE), LTE-A, LTE Pro, or 5th generation (5G) system is described below as an example, the embodiments of the disclosure may also be applied to other communication systems having technical backgrounds or channel forms similar thereto. For example, 5G-Advance or 6th generation (6G) (beyond 5G), which has been developed after 5G mobile communication technology (NR), may be included, and the 5G may be a concept including the existing LTE, LTE-A, and other similar services. Also, the disclosure may also be applied to other communication systems through some modifications without departing from the scope of the disclosure.

[0031] Terms as used herein are briefly described, and an embodiment of the disclosure are described in detail.

[0032] Terms as used herein are those defined by taking into account the functions in the disclosure, but the terms may vary depending on the intention of users or those of ordinary skill in the art, precedents, or the like. Therefore, the definitions should be made based on the contents throughout the specification.

[0033] In the disclosure, a base station is configured to perform resource allocation of a user equipment (UE), and may be at least one of a gNode B, an eNode B, a Node B (or xNode B (x is an alphabet including g and e)), a base station (BS), a radio access unit, a base station controller, a satellite, an airborn, RAN node, access point, wireless point, transmission / reception point, central unit, distributed unit, radio unit, remote radio head or a node on a network, but the disclosure is not limited thereto. The base station in the disclosure may refer to a base station itself, a cell, or a radio unit (RU) according to interpretation, and a target for exchanging messages with the UE may be a distributed unit (DU) or a central unit (CU) according to a structure.

[0034] Also, in the disclosure, the UE may include a mobile station (MS), a cellular phone, a smartphone, a computer, a vehicle, a satellite, IAB-MT, mIAB-MT, NCR-MT, electronic device, user device, mobile station, subscriber station, customer premises equipment, terminal, remote terminal, wireless terminal, vehicle terminal or a multimedia system capable of performing a communication function.

[0035] Also, in the disclosure, the cell may represent an area covered by one base station in wireless communication. Cells may be classified into mega cells, macro cells, micro cells, and pico cells according to sizes thereof, but this is only an example, and the types of cells are not limited thereto.

[0036] Also, in the disclosure, the DU may be connected to the RU and the CU and execute some of radio link control (RLC), medium access control (MAC), and physical (PHY) layers. In an embodiment of the disclosure, a virtualized DU may be included.

[0037] Also, in the disclosure, the CU may include radio resource control (RRC), service data adaptation protocol (SDAP), and packet data convergence protocol (PDCP) layers. One CU may manage one or more DUs, and may be connected to the one or more DUs through an F1 interface. In an embodiment of the disclosure, a virtualized CU may be included.

[0038] Also, in the disclosure, the RU may convert a radio signal into a digital signal for the purpose of transmission through a packet network.

[0039] In addition, in the disclosure, a downlink (DL) is a radio transmission path through which the base station transmits data or a control signal to the UE. For example, in the LTE system, the DL may employ an orthogonal frequency division multiplexing (OFDM) scheme.

[0040] In addition, in the disclosure, an uplink (UL) refers to a radio transmission path through which the UE transmits data or a control signal to the base station. For example, in the LTE system, the UL may employ a single carrier frequency division multiplexing access (SC-FDMA) scheme.

[0041] For convenience of description, the terms and names defined in the 3rd generation partnership project long term evolution (3GPP) standard or the terms and names modified based thereon are used herein.

[0042] However, the disclosure is not limited by the terms and names and may be equally applied to wireless communication systems conforming to other standards. Although an embodiment of the disclosure will be described below with reference to a 5G wireless communication technology as an example, an embodiment of the disclosure may also be applied to other wireless communication systems having technical backgrounds or channel forms similar thereto. As another example, the embodiments of the disclosure may be applied to LTE or LTE-A, which is a wireless communication system prior to NR, and may also be applied to a wireless communication system developed after NR. Furthermore, it will be understood by those of ordinary skill in the art that the embodiments of the disclosure may also be applied to other wireless communication systems through partial modifications without departing from the scope of the disclosure.

[0043] The embodiments of the disclosure may also be applied to other wireless communication systems through modifications.

[0044] The present disclosure may address, solve and / or mitigate, at least partly, at least one of the problems and / or disadvantages associated with the related art, for example at least one of the problems and / or disadvantages described herein. The present disclosure may provide at least one advantage over the related art, for example at least one of the advantages described herein.

[0045] Other aspects, advantages and salient features of the invention will become apparent to those skilled in the art from the following detailed description taken in conjunction with the accompanying drawings.

[0046] The following description of examples of the present disclosure, with reference to the accompanying drawings, is provided to assist in a comprehensive understanding of the present disclosure, as defined by the claims. The description includes various specific details to assist in that understanding but these are to be regarded as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the examples described herein can be made without departing from the scope of the disclosure.

[0047] The same or similar components may be designated by the same or similar reference numerals, although they may be illustrated in different drawings.

[0048] Detailed descriptions of techniques, structures, functions, operations or processes known in the art may be omitted for clarity and conciseness, and to avoid obscuring the subject matter of the present disclosure.

[0049] The terms and words used herein are not limited to the bibliographical or standard meanings, but, are merely used to enable a clear and consistent understanding of the disclosure.

[0050] Throughout the description and claims of this specification, the words "comprise", "include" and "contain" and variations of the words, for example "comprising" and "comprises", means "including but not limited to", and is not intended to (and does not) exclude other features, elements, components, integers, steps, processes, operations, functions, characteristics, properties and / or groups thereof.

[0051] Throughout the description and claims of this specification, the singular form, for example "a", "an" and "the", encompasses the plural unless the context otherwise requires. For example, reference to "an object" includes reference to one or more of such objects.

[0052] Throughout the description and claims of this specification, language in the general form of "X for Y" (where Y is some action, process, operation, function, activity or step and X is some means for carrying out that action, process, operation, function, activity or step) encompasses means X adapted, configured or arranged specifically, but not necessarily exclusively, to do Y.

[0053] Features, elements, components, integers, steps, processes, operations, functions, characteristics, properties and / or groups thereof described or disclosed in conjunction with a particular aspect, embodiment, example or claim are to be understood to be applicable to any other aspect, embodiment, example or claim described herein unless incompatible therewith.

[0054] The skilled person will appreciate that the techniques described herein may be used in any suitable combination.

[0055] Certain examples of the present disclosure provide one or more techniques for mobile IAB-MT barring management, for example in a 3GPP 5G NR network. However, the skilled person will appreciate that the present disclosure is not limited to these examples, and may be applied in any suitable system or standard, for example one or more existing and / or future generation wireless communication systems or standards, including any existing or future releases of the same standards specification, for example 3GPP 5G, 5G-advanced or 6th Generation (6G).

[0056] The functionality of the various network entities and other features disclosed herein may be applied to corresponding or equivalent entities or features in the same or any other suitable communication systems or standards. Corresponding or equivalent entities or features may be regarded as entities or features that perform the same or similar role, function or purpose within the network.

[0057] For example, the functionality of a base station or the like (e.g. eNB, gNB, NB, RAN node, access point, wireless point, transmission / reception point, central unit, distributed unit, radio unit, remote radio head, etc.) in the examples below may be applied to any other suitable type of entity performing RAN functions, and the functionality of a UE or other terminal device (e.g. IAB-MT, mIAB-MT, NCR-MT, electronic device, user device, mobile station, subscriber station, customer premises equipment, terminal, remote terminal, wireless terminal, vehicle terminal, etc.) in the examples below may be applied to any other suitable type of device.

[0058] A particular network entity may be implemented as a network element on a dedicated hardware, as a software instance running on a dedicated hardware, and / or as a virtualised function instantiated on an appropriate platform, e.g. on a cloud infrastructure.

[0059] The skilled person will appreciate that the present disclosure is not limited to the specific examples disclosed herein. For example:

[0060] The techniques disclosed herein are not limited to 3GPP 5G.

[0061] One or more entities in the examples disclosed herein may be replaced with one or more alternative entities performing equivalent or corresponding functions, processes or operations.

[0062] One or more of the messages in the examples disclosed herein may be replaced with one or more alternative messages, signals or other type of information carriers that communicate equivalent or corresponding information.

[0063] One or more further elements or entities may be added to the examples disclosed herein.

[0064] One or more non-essential elements or entities may be omitted in certain examples.

[0065] The functions, processes or operations of a particular entity in one example may be divided between two or more separate entities in an alternative example.

[0066] The functions, processes or operations of two or more separate entities in one example may be performed by a single entity in an alternative example.

[0067] Information carried by a particular message in one example may be carried by two or more separate messages in an alternative example.

[0068] Information carried by two or more separate messages in one example may be carried by a single message in an alternative example.

[0069] The order in which operations are performed and / or the order in which messages are transmitted may be modified, if possible, in alternative examples.

[0070] Various acronyms, abbreviations and definitions used in the present disclosure are defined as following.

[0071] Abbreviations / Definitions

[0072] In the present disclosure, the following acronyms / definitions may be used.

[0073] 3GPP 3rdGeneration Partnership Project

[0074] 4G 4thGeneration

[0075] 5G 5thGeneration

[0076] 5GC 5G Core

[0077] 6G 6thGeneration

[0078] AMF Access and Mobility management Function

[0079] ATG Air-to-Ground

[0080] DU Distributed Unit

[0081] eNB Base Station

[0082] EN-DC E-UTRA NR Dual Connectivity

[0083] EPC Evolved Packet Core

[0084] E-UTRA Evolved Universal Terrestrial Radio Access

[0085] E-UTRAN Evolved Universal Terrestrial Radio Access Network

[0086] gNB 5G NR Base Station

[0087] IAB Integrated Access and Backhaul

[0088] ID Identity / Identification

[0089] IE Information Element

[0090] LTE Long Term Evolution

[0091] MBSR Mobile Base Station Relay

[0092] mIAB Mobile IAB

[0093] MIB Master Information Block

[0094] MSG Message

[0095] MT Mobile Termination

[0096] NAS Non Access Stratum

[0097] NB Base Station

[0098] NCR Network Controlled Repeater

[0099] NF Network Function

[0100] NG Next Generation

[0101] NR New Radio

[0102] NR-DC NR Dual Connectivity

[0103] NTN Non-Terrestrial Network

[0104] PCI Physical Cell ID

[0105] PLMN Public Land Mobile Network

[0106] RAN Radio Access Network

[0107] RACH Random Access Channel

[0108] RANAC RAN Area Code

[0109] Rel Release

[0110] RRC Radio Resource Control

[0111] Rx Receive

[0112] SIB System Information Block

[0113] SMF Session Management Function

[0114] SNPN Standalone Non-Public Network

[0115] TAC Tracking Area Code

[0116] TAG Timing Advance Group

[0117] TR Technical Report

[0118] TS Technical Specification

[0119] UE User Equipment

[0120] In 3GPP 5G NR, Integrated Access and Backhaul (IAB) is a technique for providing wireless backhaul as an alternative to a fibre backhaul network. An IAB network comprises IAB nodes, at which wireless resources are shared between wireless backhaul and access links. By means of such a configuration, it is possible to install nodes without the necessity of providing a fibre data connection, thereby allowing speedy and simple roll out of network coverage to locations where no such data connection is available or possible. Due to the limited coverage area of an IAB node, the backhaul network is typically implemented as a multi-hop network with backhaul traffic traversing multiple IAB nodes.

[0121] Figure 1 illustrates an two-hop IAB network, according to an embodiment of the disclosure.

[0122] Referring to Figure 1, a two-hop IAB network may correspond to a two-hop IAB network as described in 3GPP NR Rel-16 and further enhanced in Rel-17, Rel. 18 or etc.

[0123] A UE, or any other terminal device (such as IAB-MT, mIAB-MT or NCR-MT) may be barred from a cell. Being barred from a cell means that the UE shall not camp on a cell that is barred, and may in some cases not consider the cell in the cell selection or cell reselection algorithm. This may also sometimes be referred to as Cell status and cell reservations.

[0124] A UE may be barred from a cell due to a range of reasons including one or more of the following:

[0125] > cellBarredis signalled with value true in MIB. This means that no UE can access the cell, unless there is nothing else signalled. This is useful as it allows as it allows for the UE to determine whether it is barred without having to acquire SIB1, thus saving power during for instance cell reselection.

[0126] > cellBarredXdue to any cell-wide feature is signalled in SIB1, for instance:

[0127] >> cellBarredNTN- indicates whether an NTN UE is barred from accessing the cell. In this case the cell will utilize the cellBarred in MIB to barr all legacy, non-NTN UEs from accessing the cell and then the cellBarredNTN in SIB1 is used to barr NTN UEs.

[0128] >> cellBarredATG,cellBarredRedCap1Rx,cellBarredNESall operate in the same manner. This is useful when the cell is enhanced and requires all UE to have implemented some feature in order to access the cell, such as an NTN UE, where without having implemented NTN features, the UE cannot access the cell.

[0129] > X-Supportin SIB1- Which is barring operation for specific types of UEs, for instance:

[0130] >> iab-Support- indicates whether IAB nodes are barred or not to connect to the cell. An IAB-node will ignore the cellBarred in MIB and only consider this bit whether it is barred from entering a UE.

[0131] >> ncr-Supportoperate in a similar manner. This is type of barring useful when there are multiple types of UEs in a network, and a network may not support certain types of UEs to access the cell.

[0132] > cellReservedForOtherUse- Allows the network to be reserved for a specific future use. If it is true then legacy UEs will be barred.

[0133] According to an embodiment of the disclosure, enhance IAB may be enhanced to enable mobile IABs. The deploymentof the mobile IAB may allow for IAB-DUs to provide connectivity on trains, buses etc. Mobile IAB does not support Dual Connectivity options (i.e. EN-DC or NR-DC). According to an embodiment of the disclosure,good mobility support may be provided.

[0134] The Work Item Description mentions the following enhancements:

[0135] > Define Procedures for migration / topology adaptation to enable IAB-node mobility, including inter-donor migration of the entire mobile IAB-node (full migration) [RAN3, RAN2]

[0136] >> The mobile IAB-node can connect to a stationary (intermediate) IAB-node. Optimizations specific to the scenarios, where the mobile IAB-node connects to a stationary (intermediate) IAB-node, or where it directly connects to an IAB-donor-DU are de-prioritized.

[0137] >> The mobility of dual-connected IAB-nodes is down-prioritized.

[0138] > Enhancements for mobility of an IAB-node together with its served UEs, including aspects related to group mobility. No optimizations for the targeting of surrounding UEs. [RAN3, RAN2]

[0139] Note: Solutions should avoid touching upon topics where Rel-17 discussions already occurred and where the topic was excluded from Rel-17, except for enhancements that are specific to IAB-node mobility.

[0140] > Mitigation of interference due to IAB-node mobility, including the avoidance of potential reference and control signal collisions (e.g. PCI, RACH). [RAN3, RAN2]

[0141] For the purpose of the enhancements related to mobility two main enhancements were introduced:

[0142] > RACH-less handover, which allows UEs to perform very fast handovers when the mIAB-MT perform DU migration.

[0143] >> This takes advantage of the fact that the handovers are performed to same physical mIAB cell.

[0144] > Enhanced UE cell reselection prioritizing an mIAB cell if the UE detects that it is onboard a vehicle.

[0145] >> If the UE detects that it is onboard a vehicle, the UE will prioritize any cell that indicates that it is an mIAB cell. The indication of the mIAB being an mIAB cell is sent in SIB1.

[0146] >> The non-mIAB cells may also broadcast cell reselection assistance information that indicates that there are mIAB cells to prioritize if the UE is onboard a vehicle.

[0147] The enhancements relating migration / topology enhancements include that there is the possibility for a donor gNB to indicate whether it supports mobile IABs connecting to it. This may be similar to the indication introduced in Release 16 IAB whereby a donor gNB may indicate whether it supports IAB. For a release 16 IAB, the donor gNB indicates that it is IAB-capable, otherwise the IAB-MT may not connect to the cell. Both the Rel-16 IAB indicator and the Rel-18 mIAB indicator may be sent as part of PLMN-IdentityInfoList in SIB1 as shown in [Table 1]:

[0148] ------------------------- 3GPP TS 38.331 V18.0.0 --------------------------PLMN-IdentityInfoListThe IEPLMN-IdentityInfoListincludes a list of PLMN identity information.PLMN-IdentityInfoListinformation element-- ASN1START-- TAG-PLMN-IDENTITYINFOLIST-STARTPLMN-IdentityInfoList ::= SEQUENCE (SIZE (1..maxPLMN)) OF PLMN-IdentityInfoPLMN-IdentityInfo ::= SEQUENCE {plmn-IdentityList SEQUENCE (SIZE (1..maxPLMN)) OF PLMN-Identity,trackingAreaCode TrackingAreaCode OPTIONAL, -- Need Rranac RAN-AreaCode OPTIONAL, -- Need RcellIdentity CellIdentity,cellReservedForOperatorUse ENUMERATED {reserved, notReserved},...,[[iab-Support-r16 ENUMERATED {true} OPTIONAL -- Need S]],[[trackingAreaList-r17 SEQUENCE (SIZE (1..maxTAC-r17)) OF TrackingAreaCode OPTIONAL, -- Need RgNB-ID-Length-r17 INTEGER (22..32) OPTIONAL -- Cond eventID-TSS]],[[mobileIAB-Support-r18 ENUMERATED {true} OPTIONAL -- Need S]]}-- TAG-PLMN-IDENTITYINFOLIST-STOP-- ASN1STOP------------------------- 3GPP TS 38.331 V18.0.0 -------------------------

[0149] According to embodiments of the disclosure, the following may be agreed or assumed on the issue of Rel-18 mIAB node's capabilities and its 'place' in the Rel-16 / 17 IAB node evolution:

[0150] - It may not be supported that Rel-18 mobile IAB-node concurrently operate as a Rel-16 / 17 IAB-node, as e.g. mobile-IAB doesn't support child IAB nodes.

[0151] - For example, there are restrictions for the network in configuring concurrent use of R-18 mIAB feature(s) and rel-16 / 17 IAB features.

[0152] - if an IAB-node may send both MSG5 indications to the network, and the network decides (or if the IAB-node should decide).

[0153] - RAN2 assumes that the mobileIAB-NodeIndication-r18 in Msg5 implies a preference / intention, with the purpose to help gNB select core network node at initial registration.

[0154] - RAN2 assumes that the MT Idle mode behaviours is reflected by a Cap wo signalling in TS 38.306.

[0155] - A separate mobile-IAB capability (signalled) may be introduced .

[0156] The above information is presented as background information only to assist with an understanding of the present disclosure. No determination has been made, and no assertion is made, as to whether any of the above might be applicable as related art with regard to the present disclosure.

[0157] Certain examples or embodiments of the present disclosure may be provided in the form of an apparatus / device / network entity configured to perform one or more defined network functions and / or a method therefor. Certain examples or embodiments of the present disclosure may be provided in the form of a system (e.g. network or wireless communication system) comprising one or more such apparatuses / devices / network entities, and / or a method therefor.

[0158] Certain examples or embodiments of the present disclosure provide a UE (e.g. IAB-MT, mIAB-MT, NCR-MT) / network entity (e.g. AMF, SMF, NF) / base station (e.g. eNB, gNB) configured to perform a method according to any example, aspect, embodiment and / or claim disclosed herein.

[0159] Certain examples or embodiments of the present disclosure provide a network (or wireless communication system) comprising a UE (e.g. IAB-MT, mIAB-MT, NCR-MT), network entity (e.g. AMF, SMF, NF), base station (e.g. eNB, gNB) according to any examples, aspects, embodiments and / or claims disclosed herein. The network transmits some configuration (i.e. SIB 1, SIB X, RRC message ) to a UE for configuring.

[0160] Certain examples or embodiments of the present disclosure provide a computer program comprising instructions which, when the program is executed by a computer or processor, cause the computer or processor to carry out a method according to any example, aspect, embodiment and / or claim disclosed herein.

[0161] Certain examples or embodiments of the present disclosure provide a computer or processor-readable data carrier having stored thereon a computer program according to any example, aspect, embodiment and / or claim disclosed herein.

[0162] According to embodiments of the disclosure, , the following maybe agreed or assumed on the issue of mIAB vs. IAB operation, and:

[0163] - A parent node indicates support of mobile IAB but not Rel-16 / 17 IAB by broadcasting the "mobile IABsupported" indicator but not the "IABsupported" indicator in SIB1.

[0164] - A parent node indicates support of both, mobile IAB and Rel-16 / 17 IAB, by broadcasting "mobile IABsupported" and "IABsupported" in SIB1.

[0165] - From AS / R2 point of view, an IAB-node indicates capabilities to the network and the use of these are configured by the network.

[0166] - R2 assumes that the device can know whether it is intended to operate as R18 mIAB or R16 / 17-IAB node, (how the device knows may be up to implementation or may be outside R2 scope, e.g. subscription, device internal param etc), the MSG5 indication is an indication of this intended mode of operation. This agreement is not intended to mandate that a mIAB node must support R16 / 17 operation.

[0167] - R2 assumes that the IAB-node only indicates either mobile IAB or Rel-16 / 17 IAB for MSG5, not both.

[0168] Figure 2 illustrates an mIAB node entering an area where cells do not support mIAB, according to an embodiment of the disclosure.

[0169] Additionally, according to embodiments of the disclosure, the following may be agreed or assumed:

[0170] As defined in TS 38.331, when a MBSR includes the mobile IAB-indication when establishing the RRC connection, it shall not include the IAB-indication as described in clause 5.35.2.

[0171] The table 2 below (which may be given as an illustration of one possible interpretation of the current situation, with additional comments in italics part of the present disclosure) summarises certain access barring options for an mIAB / MBSR device:

[0172] Rel-16 / Rel-17 IABRel-18 mobile IABcell broadcasting "iab-Support""iab-NodeIndication" in MSG5This is legacy IAB behaviour."iab-NodeIndication" in MSG5 and function as Rel-16 / Rel-17 IABIn line with agreement made in Chicago, although should be noted that an mIAB device need not be mandated to be able to operate as an IAB device.cell broadcasting "mobileIAB-Support"BarredThis is legacy behaviour (legacy node cannot understand mIAB indication)."mobileIAB-NodeIndication" in MSG5Rules out the possibility of mIAB device operating as an IAB node, but in this case the network is not broadcasting iab-support and therefore the behaviour is as expected.cell broadcasting "mobileIAB-Support" and "iab-Support""iab-NodeIndication" in MSG5This is legacy IAB behaviour.1) "iab-NodeIndication" and function as Rel-16 / Rel-17 IAB2) "mobileIAB-NodeIndication" in MSG5Both indications cannot be sent as per SA2 agreement, and as per RAN2 agreement device can know whether it is intended to operate as R18 mIAB or R16 / 17-IAB node. Therefore this is expected behaviour.cell broadcasting neither "mobileIAB-Support" nor "iab-Support"barredThis is legacy IAB behaviour.barredPossible open issue

[0173] One open issue identified above may include whether an mIAB-MT should be barred from accessing the network as a UE, when cell is broadcasting neither "mobileIAB-Support" nor "iab-Support". For an IAB-MT there was little use for this (to allow access as regular UE) due to static deployments. But given the fact that an mIAB-MT is moving from areas where network supports mIAB into areas where there is no mIAB support, and back - it may make sense to allow connectivity as a UE for e.g. configuration purposes. This scenario where an mIAB is located on a train can be seen in Figure 2. According to certain examples of the present disclosure, connectivity as a UE (i.e. configuration purposes) is allowed.As per the agreements referenced above, an mIAB would 'know' whether it should connect as mIAB or IAB (we assume any mIAB could do both, although this is not mandated, but does appear to be a reasonable assumption, although simultaneous operation as mIAB and IAB is not allowed or at least not supported by standards).

[0174] First row of the Table 2 above refers to an mIAB-MT detecting a cell broadcasting iab-Support. An mIAB which (at that point in time) views (or considers) itself as an IAB node would then access this cell as an IAB node. While this is not a key scenario in certain examples of the present disclosure - certain examples relate to a node that is configured to act as an mIAB node, in the case where the detected cell does not broadcast mIAB support (i.e. last row of the Table 2) - in some examples access as a regular UE of an mIAB node configured to operate as an mIAB node is predicated on IAB support broadcast, and therefore the first-row scenario is also impacted.

[0175] In certain examples of the present disclosure, an mIAB-MT device is allowed to access a network not broadcasting mobileIAB-Support. This brings certain benefits as disclosed herein but requires changes to the features of the current mobile networks, which are described in the examples below.

[0176] As an mIAB node moves through a network, there will be cases when mIAB will move through a network where there is no support for mIABs, i.e. there is no broadcasting of the mIAB-Support. Similarly, there can also be cases where the broadcasting of the mobileIAB-Support has stopped.

[0177] Figure 3 is a flowchart of method for allowing an mIAB-MT device to access a network not broadcasting mobileIAB-Support, according to an embodiment of the disclosure

[0178] The actions in certain examples can be seen in Figure 3. The step of deciding to access non-mIAB supporting cell is described below under the heading "mIAB decides to access non-mIAB supporting cell" and the (optional) step of re-configuring mIAB-MT is described below under heading "Actions after accessing non-mIAB cell".

[0179] In certain examples of the present disclosure, being barred from a cell is equivalent to not being allowed to access a cell, and not being barred from a cell is equivalent to being allowed to access a cell. In certain examples, barring may be regarded as meaning temporarily not being allowed access (for example, where barring may be regarded as meaning delayed access). "mIAB decides to access non-mIAB supporting cell"

[0180] In these cases, in certain examples, the mIAB-MT will be allowed to access the network, i.e. a cell or a gNB. An equivalent statement, would be that a mIAB-MT would not be barred from accessing a cell not broadcasting the mobileIAB-Support.

[0181] However, while the above may be useful for a mIAB-MT in an area where there is no support for mobile IAB, it may also cause issues in areas where there are support for mIAB, i.e. the mIAB-MT may connect to cells that do not support mIAB, while there in fact are mIAB-capable cells. Thus there may need to be some refinements to the conditions. In a refinement, an mIAB-MT which is allowed to access the network as a regular UE even when a cell is not broadcasting mobileIAB-Support, enters an area where there is a mix of cells broadcasting mobileIAB-Support and not broadcasting mobileIAB-Support. In one scenario, the mIAB-MT is only allowed to select cells which do broadcast mobileIAB-Support. In another scenario, the network can override this by configuring the priority of various cells i.e. selection of cells which do not broadcast mobileIAB-Support may be allowed even in presence of cells which do broadcast mobileIAB-Support.

[0182] Some further refined conditions on when a mIAB-MT may access a cell:

[0183] > The mIAB-MT is allowed to access the network as a UE if there are no other cells broadcasting mobileIAB-Support, or alternatively the mIAB-MT is not barred to access a cell that does not broadcast mobileIAB-Support if there are no cells detected by the mIAB-MT that are broadcasting the mobileIAB-Support.

[0184] >> The condition can be further refined that there are no other cells broadcasting mobileIAB-Support on the frequency, no other cells broadcasting mobileIAB-Support on the PLMN, no other cells broadcasting mobileIAB-Support in a Tracking area

[0185] >> The condition can be that there are no cells broadcasting the mobileIAB-Support detected by the mIAB-MT within a time-limit. This time-limit can be hardcoded or configured. A suitable hardcoded, could be 300 seconds.

[0186] >>> As refinement the mIAB-MT may be allowed to access a cell, i.e. is not barred to access a cell, if the mIAB-MT has been barred from accessing the cell for more than 300 seconds

[0187] >>>Has been barred from accessing any cell for more than 300 seconds

[0188] >>>>This can be useful if the mIAB-MT is barred for other reasons from accessing other cells, other than not broadcasting mobileIAB-Support

[0189] >> This makes it so that the UE will always select a cell with mobileIAB-Support before selecting a cell that does not broadcast mobileIAB-Support

[0190] > Any cell broadcasting mobileIAB-Support on any frequency will always have highest priority, i.e. the condition remains that the mIAB-MT is allowed to access a cell not broadcasting mobileIAB-Support, but that the mIAB-MT will always select a cell that broadcasts the mobileIAB-Support, if the cell is detected.

[0191] >> This priority may be configured by the network, for instance via dedicated signalling

[0192] > Allowing an mIAB-MT to access the network as a regular UE even when a cell is not broadcasting mobileIAB-Support is predicated on said cell broadcasting iab-Support. It could be assumed that a cell that broadcasts iab-Support belongs to a part of the network which supports IAB operation and therefore may also support some aspects (features) of mIAB operation.

[0193] > A further condition that can be combined with other conditions is that an mIAB-MT may access a non-mIAB cell if the mIAB-node has previously operated as an mIAB cell. The condition may for instance be that the mIAB-node has detected cells supporting mIAB, or that mIAB-MT has registered, authenticated or been authorized to operate as an IAB-node or an mIAB-node.

[0194] >> Further refine is that it must have done so within 24 hours.

[0195] > Further condition that can be combined with the other conditions is that mIAB can only access a non-mIAB supporting cell on network, PLMN or tracking area with which the mobile IAB has already registered.

[0196] > Further condition that can be combined with the other conditions is that mIAB can only access a non-mIAB supporting cell on network, PLMN or tracking area with which the mobile IAB hasnotalready registered.

[0197] > Further condition that can be combined is that the mIAB-MT has not been released by a network

[0198] >> For instance if the UE has been released by a network, i.e. via RRC release message, the UE may not access a cell that does not support mIAB.

[0199] >> This can have a time-limit, configured or hardcoded, for instance 300 seconds

[0200] > In certain examples, accessing a non-mIAB supporting cell can only be done during specific states of the mIAB:

[0201] >> During RRC re-establishment, i.e. if the mobile IAB-MT selects a cell that does not indicate mobileIAB-Support during the cell selection during RRC Re-establishment procedure

[0202] >> When the UE is in idle or inactive mode

[0203] The cell not supporting mIAB may for instance be an 4G LTE cell, i.e. an E-UTRAN cell. This would mean that the mIAB node performs access to the E-UTRAN cell as a UE. The E-UTRAN cell may be a cell that supports IAB EN-DC, which means that the cell is broadcastingiab-Support, or the cell may be a cell that does not support IAB, i.e. the cell does not broadcastiab-Support.There may also be limitations on whether an mIAB node connecting as a UE is allowed to connected to an E-UTRAN cell that is connected via 5GC or EPC. For instance, the mIAB-node may only be allowed to connect as a UE to an E-UTRAN cell connected via 5GC, which is an NG-eNB. The conditions for connecting may be similar, i.e. that there are no cells which support mIAB detected, but there may also be further conditions such as no NR cells detected before the mIAB node can connect via E-UTRAN, or via EPC.

[0204] "Actions after accessing non-mIAB cell"

[0205] In certain examples, when the mIAB-MT accesses a cell that does not indicate mobileIAB-Support, the mIAB-MT (or IAB-MT, or "UE") does not indicate the mobileIAB-NodeIndication or iab-NodeIndication.

[0206] Figure 4 is a call flow of an method in which an mIAB node is redirected to another network supporting mIAB, according to an embodiment of the disclosure

[0207] An mIAB-MT may be allowed to access the network as a regular UE to the network the mIAB-MT is attached to, which is not supporting mIAB-MT, leading to said mIAB-MT and UEs attaching to it being configured to access another operator's network in the area which does support mIAB. In other words, the mIAB node may connect to the network it is already attached to as a UE, and then be redirected to another operators network to operate as an mIAB node. The call flow can be seen in Figure 4.

[0208] Note that "Network" is intentionally broad, which can be different or same operator, different or same PLMNs, different AMFs etc. Network 1 does not broadcast mobile IAB support and according to prior art the mIAB-MT may not be allowed to access it at all and mIAB would not provide service to any UEs. If we allow it to access the network as a regular UE, the network can be made aware of its potential to operate as mIAB and could hand over to another network (which supports mobile IAB), based on a local roaming agreement.

[0209] The mIAB node may be configured with new cells, new tracking areas or PLMNs that the mIAB-MT is allowed to access to. For instance the allowed tracking areas and allowed PLMNs may be reconfigured via NAS.

[0210] The mIAB node may be authorized or configured or reconfigured to function as an IAB node (including declaring itself to the network as an IAB node) instead of functioning as a mIAB node. i.e. the mIAB may be re-configured to an IAB node. If a mIAB node is authorized to act as an mIAB node, and then receives an authorization to act as an IAB node, the actions may be one of the following:

[0211] > The mIAB node is now authorized as an IAB node, and no longer authorized as an mIAB node.

[0212] > The mIAB node is now authorized both to act as an mIAB node and an IAB node.

[0213] The mIAB node may be set up to allow for UE emergency calls. For instance if the mIAB register to a cell, PLMN, or tracking area of another operator, the mIAB-node may continue to provide service for the new operator. This may allow some of the UEs to camp on the mIAB-node to provide emergency camping, i.e. the UE camps on the cell provided by the mIAB for emergency cells. The mIAB itself may alternatively be allowed to access their own operator network for purposes of making or forwarding emergency calls.

[0214] Related art mainly assumes an IAB / mIAB node is tied to a specific network. Certain examples of the present disclosure build on this to cover access to other networks in cases where access to own network as an mIAB would not be possible - we allow access as a UE, which then gets handed over to another network to operate using its mIAB features, as covered above.

[0215] Reverting to original configuration is an additional feature of certain examples of the present disclosure. How to revert to an original configuration is important if the mIAB node is PLMN specific, and the result of the original network (network 1) pushing the mIAB node to a different network (network 2) meaning that the customers of network 1 may lose all service apart from emergency calling. The commercial model would be complex, but also the technical reconfiguration of the mIAB node would be quite disruptive, so there should definitely be triggers defined to revert back to original configuration. It also means the mIAB node needs to store its original configuration, or at least, continue to seek a network 1 node advertising 'mobileIAB-Support', even when attached to network 2, and re-attach to network 1 as soon as a network 1 node becomes available. This could trigger either the reconfiguration of the mIAB node from storage, or the mIAB node to be reconfigured back to network 1 configuration by the network itself.

[0216] An example of how the existing specification may be modified to incorporate one or more of the above techniques will now be described. According to an embodiment, the specification may be modified as shown in Table 3.

[0217] -------------------------- 3GPP TS 38.331 V18.0.05.2.2.4.2　　　　　　　　　　　　　 Actions upon reception of theSIB1Upon receiving theSIB1the UE shall:. . .1>　 if in RRC_CONNECTED while T311 is not running:. . .1>　 else:. . .3>　 else if UE is a mobile IAB-MT and ifmobileIAB-Supportis not provided for the selected PLMN nor the registered PLMN nor PLMN of the equivalent PLMN list nor the selected SNPN nor the registered SNPN nor SNPN of the equivalent SNPN list;and if,3> the UE is a mobile IAB-MT which has detected other cell(s) broadcastingmobileIAB-Supportfor the selected PLMN or the registered PLMN or PLMN of the equivalent PLMN list or the selected SNPN or the registered SNPN or SNPN of the equivalent SNPN list:4>　 consider the cell as barred in accordance with TS 38.304

[0020] ;NOTE 1:　 If the mobile IAB-MT detects no other cell broadcasting mobileIAB-Support, and performs RRC establishment, the mobile IAB-MT does not consider itself to be connecting as a mobile IAB-node, see 5.3.3.4.

[0218] Figure 5 illustrates a flowchart of an method of a terminal, according to an embodiment of the disclosure The terminal is capable of acting as a m-IAB-MT.

[0219] In step 501 the method comprises determining to access a cell that is not broadcasting information indicating that the cell supports mobile IAB.

[0220] In response to determining to access the cell that is not broadcasting information indicating that the cell supports mobile IAB, in step 502 the method comprises accessing the cell as a user equipment (UE) or accessing the cell as an IAB-MT.

[0221] Figure 6 illustrates a block diagram of an network entity , according to an embodiment of the disclosure

[0222] Figure 6 is a block diagram of an exemplary network entity that may be used in examples of the present disclosure. For example, a UE (e.g. IAB-MT, mIAB-MT, NCR-MT) / network entity (e.g. AMF, SMF, NF) / base station (e.g. eNB, gNB) in the examples of Figures 1-5 may comprise an entity of Figure 6. The skilled person will appreciate that a network entity may be implemented, for example, as a network element on a dedicated hardware, as a software instance running on a dedicated hardware, and / or as a virtualised function instantiated on an appropriate platform, e.g. on a cloud infrastructure.

[0223] The entity 600 comprises a processor (or controller) 601, a transmitter 603 and a receiver 605. The receiver 605 is configured for receiving one or more messages from one or more other network entities, for example as described above. The transmitter 603 is configured for transmitting one or more messages to one or more other network entities, for example as described above. The processor 601 is configured for performing one or more operations, for example according to the operations as described above.

[0224] The techniques described herein may be implemented using any suitably configured apparatus and / or system. Such an apparatus and / or system may be configured to perform a method according to any aspect, embodiment, example or claim disclosed herein. Such an apparatus may comprise one or more elements, for example one or more of receivers, transmitters, transceivers, processors, controllers, modules, units, and the like, each element configured to perform one or more corresponding processes, operations and / or method steps for implementing the techniques described herein. For example, an operation / function of X may be performed by a module configured to perform X (or an X-module). The one or more elements may be implemented in the form of hardware, software, or any combination of hardware and software.

[0225] It will be appreciated that examples of the present disclosure may be implemented in the form of hardware, software or any combination of hardware and software. Any such software may be stored in the form of volatile or non-volatile storage, for example a storage device like a ROM, whether erasable or rewritable or not, or in the form of memory such as, for example, RAM, memory chips, device or integrated circuits or on an optically or magnetically readable medium such as, for example, a CD, DVD, magnetic disk or magnetic tape or the like.

[0226] It will be appreciated that the storage devices and storage media are embodiments of machine-readable storage that are suitable for storing a program or programs comprising instructions that, when executed, implement certain examples of the present disclosure. Accordingly, certain examples provide a program comprising code for implementing a method, apparatus or system according to any example, embodiment, aspect and / or claim disclosed herein, and / or a machine-readable storage storing such a program. Still further, such programs may be conveyed electronically via any medium, for example a communication signal carried over a wired or wireless connection.

[0227] In a first example, there is provided a method of a terminal, wherein the terminal is capable of acting as a mobile integrated access and backhaul mobile terminal (mIAB-MT), the method comprising: determining to access a cell that is not broadcasting information indicating that the cell supports mobile IAB; in response to determining to access the cell that is not broadcasting information indicating that the cell supports mobile IAB, accessing the cell as a user equipment (UE) or accessing the cell as an IAB-MT.

[0228] In a second example, there is provided the method of the first example, wherein accessing the cell as a UE comprises accessing the cell without providing backhaul services via the cell.

[0229] In a third example, there is provided the method of the first or second example, wherein accessing the cell as a UE comprises accessing the cell for configuration purposes.

[0230] In a fourth example, there is provided the method of any of the first to third examples, wherein accessing the cell as a UE comprises accessing the cell for operation, administration, and maintenance (OAM) access.

[0231] In a fifth example, there is provided the method of any of the first to fourth examples, wherein accessing the cell as a UE or accessing the cell as an IAB-MT comprises accessing the cell without indicating that the terminal is a mobile IAB node.

[0232] In a sixth example, there is provided the method of the fifth example, wherein accessing the cell as an IAB-MT comprises: determining whether the cell is broadcasting information indicating that the cell supports IAB; and in response to determining that the cell is broadcasting information indicating that the cell supports IAB, accessing the cell as an IAB-MT without indicating that the terminal is a mobile IAB node.

[0233] In a seventh example, there is provided the method of the fifth example, wherein accessing the cell as a UE further comprises accessing the cell without indicating that the terminal is an IAB node

[0234] In an eighth example, there is provided the method of any of the first to fourth examples, wherein the information indicating that the cell supports mobile IAB comprises mobileIAB-Support broadcast in SIB1.

[0235] In a ninth example, there is provided a terminal capable of acting as a mobile integrated access and backhaul mobile terminal (mIAB-MT), wherein the terminal is configured to operate according to a method of any of the first to eighth examples.

[0236] In a tenth example, there is provided a computer program comprising instructions which, when the program is executed by a computer or processor, cause the computer or processor to carry out a method according to any of the first to eighth examples.

[0237] In an eleventh example, there is provided a computer or processor-readable data carrier having stored thereon a computer program according to the tenth example.

[0238] While the invention has been shown and described with reference to certain examples, it will be understood by those skilled in the art that various changes in form and detail may be made therein without departing from the scope of the invention, as defined by the appended claims.

Claims

1.A method of a terminal, wherein the terminal is capable of acting as a mobile integrated access and backhaul mobile terminal (mIAB-MT), the method comprising:determining to access a cell that is not broadcasting information indicating that the cell supports mobile IAB;in response to determining to access the cell that is not broadcasting information indicating that the cell supports mobile IAB, accessing the cell as a user equipment (UE) or accessing the cell as an IAB-MT.2.The method of claim 1, wherein accessing the cell as a UE comprises accessing the cell without providing backhaul services via the cell.3.The method of claim 1 or claim 2, wherein accessing the cell as a UE comprises accessing the cell for configuration purposes.4.The method of any preceding claim, wherein accessing the cell as a UE comprises accessing the cell for operation, administration, and maintenance (OAM) access.5.The method of any preceding claim, wherein accessing the cell as a UE or accessing the cell as an IAB-MT comprises accessing the cell without indicating that the terminal is a mobile IAB node.6.The method of claim 5, wherein accessing the cell as an IAB-MT comprises:determining whether the cell is broadcasting information indicating that the cell supports IAB; andin response to determining that the cell is broadcasting information indicating that the cell supports IAB, accessing the cell as an IAB-MT without indicating that the terminal is a mobile IAB node.7.The method of claim 5, wherein accessing the cell as a UE further comprisesaccessing the cell without indicating that the terminal is an IAB node8.The method of any preceding claim, wherein the information indicating that the cell supports mobile IAB comprisesmobileIAB-Supportbroadcast in SIB1.9.A terminal capable of acting as a mobile integrated access and backhaul mobile terminal (mIAB-MT), wherein the terminal is configured to operate according to a method of any preceding claim.10.A computer program comprising instructions which, when the program is executed by a computer or processor, cause the computer or processor to carry out a method according to any of claims 1 to 8.11.A computer or processor-readable data carrier having stored thereon a computer program according to claim 10.

Images