Method, apparatus, and computer-readable medium for integrated access and backhaul communications

Abstract

Embodiments of the present disclosure relate to methods, devices, and computer-readable storage media for integrated access and backhaul (IAB) communications. According to an embodiment of the present disclosure, an IAB node sends a registration request including information about the IAB node to an access and mobility management function (AMF). The AMF sends a message to the IAB node indicating a registration area and at least one allowed network slice for access by the IAB node. The registration area and at least one allowed network slice are determined based on the information about the IAB node. The solution implements slice support information exchange and registration management for mobile IAB.

Description

Technical Field

[0001] Embodiments of the present disclosure relate generally to the field of telecommunications, and in particular to methods, apparatus, and computer-readable media for integrated access and backhaul (IAB) communications. Background Art

[0002] IAB has been introduced in Release 16 (Rel-16) of the 3GPP specification as a key enabler for rapid and cost-effective deployment. IAB nodes use the same spectrum and air interface for access and backhaul, creating a hierarchical wireless multi-hop network between sites. Each hop ultimately terminates at an IAB donor node that is connected to the core network by means of conventional fixed backhaul. The IAB node includes a mobile termination (MT) part and a distributed unit (DU) part, the MT part acting as a user equipment (UE) toward its parent IAB node or donor IAB node, and the DU part acting as a base station toward the next hop IAB node and UE. IAB nodes can have different implementation options or operating modes. For example, an IAB node can be installed on a fixed infrastructure (e.g., a lamp post or street furniture). Such an IAB node can be called a fixed IAB node. Depending on the channel conditions on the wireless backhaul, a fixed IAB node can migrate from one donor IAB node to a neighboring donor IAB. Another IAB node implementation may be a case where the IAB node is installed on a vehicle and the IAB node is active (i.e., serving a UE), in which case the IAB is static or slowly moving, and in particular serves a UE outside the vehicle. For example, when the vehicle is parked, the IAB node may serve a UE outside the vehicle. When a nomadic IAB is inactive (i.e., inoperable), it may enter an idle mode, for example, similar to RRC idle or RRC inactive. Such an IAB node may be referred to as a nomadic IAB node. A nomadic IAB node may be integrated into a vehicle, for example, into a vehicle of a car-sharing fleet or a taxi fleet. A nomadic IAB node may be used to provide coverage and / or capacity enhancement. Another concept of IAB (i.e., mobile IAB) has recently been proposed. A mobile IAB node is located on a mobile object (e.g., a vehicle or a balloon or a drone) and provides wireless access to (multiple) UEs inside or outside the mobile object. Taking into account mobility and / or wireless backhaul channel conditions, the mobile IAB node may migrate from one IAB donor or parent IAB node to another IAB donor or parent IAB node. This migration may be in the form of a handover.

[0003] Network slicing is a key 5G feature that can be used to support different services using the same underlying mobile network infrastructure. Current network slicing mechanisms are developed for UE or for network devices / elements. Summary of the invention

[0004] In general, example embodiments of the present disclosure provide methods, apparatus, and computer-readable media for IAB communications.

[0005] In a first aspect, a method is provided. The method includes sending a registration request including information about the IAB node from an IAB node to an access and mobility management function; and receiving a message from the access and mobility management function indicating a registration area and at least one allowed network slice for access by the IAB node, the registration area and the at least one allowed network slice being determined based on the information about the IAB node.

[0006] In a second aspect, a method is provided. The method receives, at an access and mobility management function, a registration request including information about the IAB node from an IAB node; and sends a message to the IAB node indicating a registration area and at least one allowed network slice for access by the IAB node, the registration area and the at least one allowed network slice being determined based on the information about the IAB node.

[0007] In a third aspect, an apparatus is provided. The apparatus includes at least one processor and at least one memory including computer program code. The at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to: send a registration request including information about the apparatus to an access and mobility management function; and receive a message from the access and mobility management function indicating a registration area and at least one allowed network slice for access by the apparatus, the registration area and the at least one allowed network slice being determined based on information about an IAB node.

[0008] In a fourth aspect, an apparatus is provided. The apparatus includes at least one processor and at least one memory including computer program code. The at least one memory and the computer program code are configured to, together with the at least one processor, cause the apparatus to: receive a registration request including information about the IAB node from an IAB node; and send a message to the IAB node indicating a registration area and at least one allowed network slice for access by the IAB node, the registration area and the at least one allowed network slice being determined based on the information about the IAB node.

[0009] In a fifth aspect, an apparatus is provided. The apparatus comprises means for sending a registration request including information about the apparatus to an access and mobility management function; and means for receiving a message from the access and mobility management function indicating a registration area and at least one allowed network slice for access by the apparatus, the registration area and the at least one allowed network slice being determined based on the information about the apparatus.

[0010] In a sixth aspect, an apparatus is provided. The apparatus includes a component for receiving a registration request including information about the IAB node from an IAB node; and a component for sending a message to the IAB node indicating a registration area and at least one allowed network slice for access by the IAB node, the registration area and the at least one allowed network slice being determined based on the information about the IAB node.

[0011] In a seventh aspect, a computer program product is provided, the computer program product being stored on a computer readable medium and comprising machine executable instructions, wherein when the machine executable instructions are executed, the machine executes the method according to the first aspect or the second aspect.

[0012] In an eighth aspect, a computer-readable storage medium is provided, the computer-readable storage medium comprising program instructions stored thereon, wherein when the instructions are executed by a device, the device executes the method according to the first aspect or the second aspect.

[0013] It should be understood that the invention summary is not intended to determine the key or essential features of the embodiments of the present disclosure, nor is it intended to limit the scope of the present disclosure. Other features of the present disclosure will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] The above and other objects, features and advantages of the present disclosure will become more apparent through a more detailed description of some example embodiments of the present disclosure in the accompanying drawings, in which:

[0015] Figure 1 A block diagram illustrating an example environment in which embodiments of the present disclosure may be implemented;

[0016] Figure 2 A schematic diagram showing interactions between devices according to some example embodiments of the present disclosure;

[0017] Figure 3 A schematic diagram showing interactions between devices according to some example embodiments of the present disclosure;

[0018] Figure 4 A schematic diagram showing interactions between devices according to some example embodiments of the present disclosure;

[0019] Figure 5 A flowchart illustrating an example method for IAB communications according to some example embodiments of the present disclosure is shown;

[0020] Figure 6 A flowchart illustrating an example method for IAB communications according to some example embodiments of the present disclosure is shown;

[0021] Figure 7shows a simplified block diagram of an apparatus suitable for implementing an embodiment of the present disclosure; and

[0022] Figure 8 A block diagram of an example computer-readable medium is shown according to some example embodiments of the present disclosure.

[0023] Throughout the drawings, the same or similar reference numerals refer to the same or similar elements. DETAILED DESCRIPTION

[0024] The principle of the present disclosure will now be described with reference to some example embodiments. It should be understood that these embodiments are described only to illustrate and help those skilled in the art to understand and implement the present disclosure, and do not represent any limitation on the scope of the present disclosure. The disclosure described herein can be implemented in various other ways except the way described below.

[0025] In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs.

[0026] In this disclosure, references to "one embodiment," "an embodiment," and "an example embodiment" indicate that the described embodiment may include a particular feature, structure, or characteristic, but not every embodiment must include the particular feature, structure, or characteristic. In addition, such phrases do not necessarily refer to the same embodiment. In addition, when a particular feature, structure, or characteristic is described in conjunction with an embodiment, those skilled in the art believe that it is within the knowledge of those skilled in the art to affect such feature, structure, or characteristic in conjunction with other embodiments, whether or not explicitly described.

[0027] It should be understood that although the terms "first" and "second" etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another element. For example, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element without departing from the scope of the exemplary embodiments. As used herein, the term "and / or" includes any and all combinations of one or more of the listed terms.

[0028] The terms used herein are only used to describe specific embodiments and are not intended to limit the example embodiments. As used herein, the singular forms "a", "an", and "the" also include the plural forms, unless the context clearly indicates otherwise. It is further understood that the terms "comprises", "comprising", "has", "having", "includes", and / or "including" when used herein specify the presence of the features, elements, and / or components, etc., but do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof.

[0029] As used in this application, the term "circuitry" may refer to one, more, or all of the following:

[0030] (a) a pure hardware circuit implementation (such as an implementation using only analog and / or digital circuitry), and

[0031] (b) a combination of hardware circuitry and software such as (where applicable):

[0032] (i) a combination of analog and / or digital hardware circuits and software / firmware, and

[0033] (ii) any portion of a hardware processor(s) with software, including digital signal processor(s), software and memory(s), which work together to cause a device (such as a mobile phone or server) to perform various functions, and

[0034] (c) Hardware circuit(s) and / or processor(s), such as microprocessor(s) or portion(s) of microprocessor(s), which requires software (e.g., firmware)

[0035] The software can be saved when no operation is needed.

[0036] This definition of circuitry applies to all uses of the term in this application, including in any claims. As another example, as used in this application, the term circuitry also covers an implementation of only a hardware circuit or processor (or multiple processors) or a portion of a hardware circuit or processor and its accompanying software and / or firmware. For example, if applicable to a particular claim element, the term circuitry also covers a baseband integrated circuit or processor integrated circuit for a mobile device, or a similar integrated circuit in a server, cellular network device, or other computing or network device.

[0037] As used herein, the term "communication network" refers to a network that complies with any suitable communication standard, such as Long Term Evolution (LTE), Advanced LTE (LTE-a), Wideband Code Division Multiple Access (WCDMA), High Speed ​​Packet Access (HSPA), Narrowband Internet of Things (NB-IoT), New Radio (NR), etc. In addition, the communication between the terminal device and the network device in the communication network can be performed according to any suitable generation of communication protocol, including but not limited to the first generation (1G), second generation (2G), 2.5G, 2.75G, third generation (3G), fourth generation (4G), 4.5G, future fifth generation (5G) communication protocol, and / or any other protocol currently known or to be developed in the future. The embodiments of the present disclosure can be applied to various communication systems. In view of the rapid development of communication, there will certainly be future types of communication technologies and systems that can embody the present disclosure. The scope of the present disclosure should not be limited to the above-mentioned systems.

[0038] As used herein, the term "network device" refers to a node in a communication network through which a terminal device accesses the network and receives services from the network. A network device may refer to a base station (BS) or an access point (AP), for example, a NodeB (NodeB or NB), an evolved NodeB (eNodeB or eNB), a NR NB (also referred to as a gNB), a remote radio unit (RRU), a radio head (RH), a remote radio head (RRH), a relay, a low-power node (such as a femto, a micro, etc.), depending on the terminology and technology applied. In the following description, the terms "network device", "BS" and "node" may be used interchangeably.

[0039] The term "terminal device" refers to any terminal device capable of wireless communication. As an example and not limitation, a terminal device may also be referred to as a communication device, a user equipment (UE), a subscriber station (SS), a portable subscriber station, a mobile station (MS), or an access terminal (AT). The terminal device may include, but is not limited to, a mobile phone, a cellular phone, a smart phone, a voice over IP (VoIP) phone, a wireless local loop phone, a tablet computer, a wearable terminal device, a personal digital assistant (PDA), a portable computer, a desktop computer, an image capture terminal device (such as a digital camera), a game terminal device, a music storage and playback device, a vehicle-mounted wireless terminal device, a wireless endpoint, a mobile station, a laptop embedded device (LEE), a laptop vehicle-mounted device (LME), a USB dongle, a smart device, a wireless customer premises equipment (CPE), an Internet of Things (IoT) device, a watch or other wearable device, a head-mounted display (HMD), a vehicle, a drone, medical equipment and applications (e.g., remote surgery), industrial equipment and applications (e.g., robots and / or other wireless devices operating in the context of an industrial and / or automated processing chain), consumer electronic devices, devices operating on commercial and / or industrial wireless networks, etc. In the following description, the terms "terminal device", "communication device", "terminal", "user equipment" and "UE" may be used interchangeably.

[0040] Although the functions described herein may be performed in fixed and / or wireless network nodes in various example embodiments, in other example embodiments, the functions may be implemented in a user equipment device (such as a mobile phone or tablet or laptop or desktop or mobile IOT device or fixed IOT device). For example, the user equipment device may be appropriately equipped with corresponding capabilities as described in conjunction with (multiple) fixed and / or wireless network nodes. The user equipment device may be a user device and / or a control device, such as a chipset or a processor, which is configured to control the user device when installed in the user device. Examples of such functions include boot server functions and / or home subscriber servers, which may be implemented in the user equipment device by providing the user equipment device with software configured to cause the user equipment device to execute from the perspective of these functions / nodes.

[0041] Integrated Access and Backhaul (IAB) has been introduced in Rel-16 as a key enabler for fast and cost-effective deployment, for example, targeting outdoor dense mmWave deployments. IAB nodes can use the same spectrum and air interface for access and backhaul, creating a hierarchical wireless multi-hop network between sites. Each hop ultimately terminates at a donor node (also called "IAB donor") that can be connected to the 5G core network (5GC) with the help of conventional fixed backhaul.

[0042] Figure 11 shows a block diagram of an example environment 100 in which embodiments of the present disclosure may be implemented. Figure 1 As shown, environment 100 includes core network 110, IAB donor node 120, IAB nodes 130-1 and 130-2 (collectively referred to as "IAB node 130" or individually referred to as "IAB node 130"), network device 140 (such as gNB), and UE 150-1, 150-2 and 150-3 (collectively referred to as "UE 150" or individually referred to as "UE 150"). In this document, the terms "IAB node" and "IAB device" may be used interchangeably. The terms "IAB donor node", "IAB donor" and "IAB donor device" may be used interchangeably.

[0043] The core network 110 may include many network entities that provide different network functions, for example, a network slice selection function (NSSF) 111, a unified data repository (UDM) 112, an access and mobility management function (AMF) 113, an operation administration and maintenance (OAM) 114, a network function (NF) repository function (NRF), a session management function (SMF), a policy control function (PCF), a network exposure function (NEF), etc.

[0044] The IAB donor node 120 may include a centralized unit (CU) 121 (also referred to as an "IAB donor CU 121") and a distributed unit (DU) 122 (also referred to as an "IAB donor DU 122"). The IAB node 130-1 may include an MT portion 131-1 and a DU 132-1. The IAB node 130-2 may include an MT portion 131-2 and a DU 132-2. The MTs 131-1 and 131-2 may also be collectively referred to as "IAB MTs 131" or individually as "IAB MTs 131". The DUs 132-1 and 132-2 may also be collectively referred to as "IAB DUs 132" or individually as "IAB DUs 132".

[0045] The IAB donor DU 122 or each IAB DU 132 may provide one or more cells to serve the UE. For example, the cells provided by the DU may broadcast normal control signals, such as synchronization signal blocks (SSBs) for downlink synchronization and system information. Therefore, from the perspective of the UE, the cells provided by the DU may be regarded as normal cells. For example, Figure 1 As shown, IAB donor DU 122 serves UE 150-1, IAB DU 132-1 serves UE 150-2, and IAB DU 132-2 serves UE 150-3.

[0046] The IAB MT 131 of the IAB node 130 may act as a UE toward its parent node. For example, the IAB MT 131-1 may act as a UE toward the IAB donor node 120 (i.e., the IAB donor DU 122), and the IAB MT 131-2 may act as a UE toward the IAB node 130-1 (i.e., the IAB DU 132-1). On the sublink, the IAB DU 132 of the IAB node 130 may act as a network device (such as a gNB) toward its next-hop IAB node. For example, the IAB donor DU 122 may act as a gNB toward the IAB node 130-1, and the IAB DU 132-1 may act as a gNB toward the IAB node 130-2. On the access link, as described above, the IAB donor node 120 and the IAB node 130 may act as normal gNBs to provide a wireless interface for the UE 150 in its coverage area.

[0047] In the environment 100, each IAB MT 132 may have a radio resource control (RRC) connection with the IAB donor CU 121 and a non-access stratum (NAS) connection with the AMF 113. Each IAB node 130 (i.e., IAB DU 132) maintains an F1 interface to the IAB donor node 120 (i.e., IAB donor CU 121). Therefore, it can be inferred that the IAB node 130 has both an access node function (by means of the IAB DU 132 having an F1 interface to the IAB donor CU 121) and a UE function (by means of the IAB MT 131 having an RRC connection to the IAB donor CU 121 and a NAS connection to the AMF 113).

[0048] Communications in environment 100 may be implemented according to any (multiple) appropriate communications protocols, including but not limited to cellular communications protocols such as first generation (1G), second generation (2G), third generation (3G), fourth generation (4G), and fifth generation (5G), wireless local network communications protocols such as Institute of Electrical and Electronics Engineers (IEEE) 802.11, and / or any other protocols currently known or to be developed in the future. In addition, communications may utilize any appropriate wireless communications technology, including but not limited to: code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), frequency division duplex (FDD), time division duplex (TDD), multiple input multiple output (MIMO), orthogonal frequency division multiple access (OFDMA), and / or any other technology currently known or to be developed in the future.

[0049] As mentioned above, network slicing is a key 5G feature that can be used to support different services using the same underlying mobile network infrastructure. Network slices may differ in their service requirements (such as URLLC and eMBB) or the tenants that provide these services. Network slices are uniquely identified via single network slice selection assistance information (S-NSSAI). In the current 3GPP specification, a UE is allowed to connect to and be served by up to eight network slices simultaneously. On the other hand, each cell can support a large number of network slices. The S-NSSAI may include a slice service type (SST) field with a length of 8 bits and a slice differentiator (SD) field with a length of 24 bits, or only the SST field, in which case the total length of the S-NSSAI is 8 bits.

[0050] A registration area is a list of tracking areas (TAs) that support the same slice from the perspective of the UE, i.e., slices allowed for the UE. Here, slices and network slices can be used interchangeably. When a UE registers with the core network, the UE can indicate the network slice (e.g., S-NSSAI) to which it requests access. The core network analyzes the UE profile and subscription data to verify that the network slice that the UE can indeed access. Therefore, the core network sends a list of allowed network slices to the UE. The list of allowed network slices may be different, or only a subset of the requested network slices from the registration request. If the allowed network slices contain at least one network slice, the core network also configures a registration area for the UE. The registration area includes a list of TAs in which all allowed network slices are supported. The core network knows the current TA of the UE from the registration request, and knows the slice support information of the neighboring TAs (which indicates the network slices supported in the neighboring TAs). Based on this information, the core network can configure the UE with a list of TAs in which the slice support is homogeneous for the UE. Once the UE leaves a TA in the registration area, it needs to perform a registration area update, and the core network re-evaluates the network slice requested by the UE and configures a new registration area for the UE.

[0051] Slice support information for neighboring TAs may be exchanged during Xn establishment and NG-RAN node configuration update. Slice support information for IAB DUs may be exchanged during F1 establishment and gNB DU configuration update. For example, slice support information may be provided per TA in the form of a set of slice identity identifiers (i.e., S-NSSAI).

[0052] exist Figure 1In the illustrated environment 100, each IAB node 130 may be connected to the core network 110 via multiple parent IAB nodes. Each IAB node 130 may serve a group of UEs, where the UEs may be associated with different network slices. For example, for a UE 150-2 to be served by a given network slice, both the IAB node 130-1 and the IAB donor node 120 should support the network slice.

[0053] As described above, different IAB implementations or operation modes are possible, for example, fixed IAB, nomadic IAB or mobile IAB. For example, a mobile IAB node is located on a mobile object and provides wireless access to UEs inside or outside the mobile object. As described above, in different implementations of the IAB node, the IAB node can change (such as migrate or switch) from one donor IAB node or parent IAB node to another donor IAB node or parent IAB node. For IAB communications, factors such as inherent mobility or migration need to be taken into account to enable slicing support. In the current 3GPP specifications, network slicing mechanisms are mainly developed for UEs or for network devices. Considering that the IAB node contains both the MT part and the DU part, and neither UE-specific signaling nor access node / network device-specific signaling can be used to provide slicing support for the IAB node, slicing support for the IAB node should be provided.

[0054] Embodiments of the present disclosure provide a solution for IAB communication to solve the above-mentioned problems and one or more other potential problems. The solution provides a mechanism for slice support information exchange and registration management for IAB operation. These mechanisms can be handled by jointly considering that the IAB node has UE and access node functions. These mechanisms can be applied to different implementations or operating modes of one or more IAB nodes (such as (multiple) fixed IAB nodes, (multiple) mobile IAB nodes and / or (multiple) mobile IAB nodes). It can be inferred that such a mechanism can be applied to a network including an IAB node or a network element, which can function similarly to an IAB node (e.g., a wireless relay).

[0055] Figure 2 A schematic diagram of an interaction 200 between devices according to some example embodiments of the present disclosure is shown. For example, the interaction 200 involves an IAB node 130 (such as IAB node 130-1 and / or 130-2), an IAB donor node 120, and an AMF 113.

[0056] like Figure 2 As shown, the IAB MT 131 sends a 201 registration request to the AMF 113 via a NAS connection.

[0057] In some example embodiments, the registration request may include an indication of an operating mode of the IAB node 130, and information about the network slices that the IAB node 130 requests to access. For example, the information about the network slices may be the S-NSSAI of these network slices, also referred to as the "requested S-NSSAI". The requested S-NSSAI may be pre-configured at the IAB node 130, or configured online to the IAB node 130. For example, the IAB donor CU 121 may select the AMF 113 based on the requested S-NSSAI. For example, taking into account the indication of the operating mode of the IAB node 130, the number of requested S-NSSAIs may exceed 8.

[0058] In some example embodiments, the indication of the operating mode of the IAB node 130 may have different forms. For example, the indication of the operating mode may be an IAB indicator indicating that the IAB node 130 is fixed, mobile or nomadic. That is, such an indication may also imply an IAB implementation option or operating mode, such as a fixed IAB, a nomadic IAB or a mobile IAB. For another example, the indication of the operating mode may be a mobile IAB indicator indicating whether the IAB node 130 is a mobile IAB node. In some cases, different IAB nodes may be assigned different identifiers (IDs), wherein a predetermined ID range may indicate a mobile IAB node, while other IDs may indicate a fixed IAB node or a nomadic IAB node. For example, in this case, the indication of the operating mode may be an ID of the IAB node 130, which may be used to identify that the IAB node 130 is a mobile IAB node, a fixed IAB node or a nomadic IAB node.

[0059] like Figure 2As shown, AMF 113 determines 202 the network slices that are allowed to be accessed by IAB node 130, and the registration areas corresponding to the allowed network slices. In some example embodiments, AMF 113 may obtain subscription data from UDM 112. For example, the subscription data may indicate the network slices subscribed by IAB node 130. In some example embodiments, AMF 113 may determine the allowed network slices based on the requested network slices indicated in the registration request, the subscribed network slices obtained from UDM 112, and the network slices supported by IAB donor node 120 (e.g., the network slices supported by IAB donor 120 in the tracking area where IAB node 130 is located). In some example embodiments, AMF 113 may query a network slice selection function (NSSF) for slice selection. NSSF may return a set of network slice instance (NSI) identifiers. In some example embodiments, AMF 113 may also determine the network slices for the IAB backhaul link, and include the network slices for the IAB backhaul link in the allowed network slices.

[0060] In some example embodiments, for example, the registration request may not include information about the requested network slice. In this case, AMF 113 may obtain subscription data indicating the subscribed network slice from UDM 112. If the subscribed network slice obtained from UDM 112 is supported in the TA where IAB node 130 is located, AMF 113 may determine the allowed network slice as the subscribed network slice obtained from UDM 112. That is, AMF 113 may determine the allowed network slice based only on the subscription data.

[0061] like Figure 2 As shown, AMF 113 sends 203b a registration accept message to IAB MT 131 via a NAS connection, the registration accept message indicating the registration area and the allowed network slices (such as the S-NSSAI of these network slices, also referred to as "allowed S-NSSAI"). In some example embodiments, the number of allowed S-NSSAIs may exceed 8. AMF 113 may also send 203a a registration accept message to IAB donor CU 121. IAB MT 131 forwards 204 information about the registration area and allowed network slices to IAB DU 132.

[0062] Subsequently, the IAB DU 132 provides 205 information about the allowed network slices (such as allowed S-NSSAI) and TA to the IAB donor CU 121 in the F1-AP procedure. The allowed S-NSSAI may be the same as or different from the requested or configured S-NSSAI. The IAB donor CU 121 reports 206 information about at least one of the allowed network slices to the AMF 113 in the NG configuration update procedure, wherein at least one of the allowed network slices is supported in a tracking area corresponding to a tracking area identity (TAI) of the IAB node 130.

[0063] exist Figure 2 In the example shown, UE-specific signaling is used to provide information about the access node so that the requested NSSAI does correspond to the slice support information of the mobile IAB. Since the IAB can support different UEs with different slice support capabilities, the network slices supported by the IAB node can be far more than eight. In contrast to conventional UEs, the AMF also considers the slice support information of the IAB donor CU while allocating an allowed S-NSSAI for the mobile IAB node. The slice support information in the F1-AP process matches the allowed NSSAI provided by the AMF, which is also different from conventional DU operation.

[0064] Figure 3 A schematic diagram of an interaction 300 between devices according to some example embodiments of the present disclosure is shown. For example, the interaction 300 involves an IAB node 130 (such as IAB node 130-1 and / or 130-2), an IAB donor node 120, an AMF 113, and an OAM 114.

[0065] like Figure 3 As shown, the IAB MT 131 sends a 301 registration request to the AMF 113 via a NAS connection.

[0066] The registration request may not include the S-NSSAI of the network slice to which the IAB node 130 requests access. In some example embodiments, the registration request may include user location information (ULI) of the IAB MT 131, and an indication of the operating mode of the IAB node 130. The indication of the operating mode of the IAB node 130 may have different forms. For example, the indication of the operating mode may be an IAB indicator indicating that the IAB node 130 is fixed, mobile, or nomadic. That is, such an indication may also imply an IAB implementation option or operating mode, such as a fixed IAB, a nomadic IAB, or a mobile IAB. For another example, the indication of the operating mode may be a mobile IAB indicator indicating whether the IAB node 130 is a mobile IAB node. In some cases, different IAB nodes may be assigned different identifiers (IDs), where a predetermined ID range may indicate a mobile IAB node, while other IDs may indicate a fixed IAB node or a nomadic IAB node. For example, in this case, the indication of the operating mode may be an ID of IAB node 130, which may be used to identify whether the IAB 130 node is a mobile IAB node, a fixed IAB node, or a nomadic IAB node. Alternatively, in some example embodiments, the registration request may include an indication of a mobile IAB slice (e.g., a network slice for an IAB backhaul link), which may implicitly indicate that the IAB node 130 is a mobile IAB node.

[0067] like Figure 3 As shown, AMF 113 determines 302 a registration area based on the ULI of IAB MT 131 and an indication that IAB node 130 is a mobile IAB node. AMF 113 sends 303 a registration accept message indicating the registration area and the network slice (such as the S-NSSAI of the network slice) for the IAB backhaul link to IAB MT 131 via a NAS connection.

[0068] In some example embodiments, IAB MT 131 may establish a PDU session with OAM 114 such that OAM 114 obtains 304b ULI from IAB MT 131 via the PDU session. Alternatively, OAM 114 may obtain 304a ULI of IAB MT 131 from AMF 113. OAM 114 provides 305 configuration to IAB MT 131 based on the ULI of IAB MT 131. For example, the configuration may indicate network slices to be supported in the registration area (such as S-NSSAI of the network slice), tracking area identities (TAIs) to be announced, etc. IAB MT 131 forwards 306 information about the supported network slices and TAs to IAB DU 132.

[0069] Subsequently, the IAB DU 132 provides 307 information about the allowed network slices (such as allowed S-NSSAI) and TA to the IAB donor CU 121 in the F1-AP procedure. The allowed S-NSSAI may be the same as or different from the requested or configured S-NSSAI. The IAB donor CU 121 reports 308 information about the allowed network slices to the AMF 113 in the NG Configuration Update procedure. To this end, the NG-RAN may provide a mapping between the physical cell identity (PCI) / tracking area identity (TAI) / cell global identity (CGI) and an identifier of the mobile IAB MT in the NG Configuration Update message.

[0070] exist Figure 3 In the example shown, the S-NSSAI is allowed to be configured to the mobile IAB node at runtime based on the location of the mobile IAB node. The registration area is determined based on the best support of the IAB node. For example, the registration area can only include the TA indicated by the ULI of the mobile IAB node.

[0071] Figure 4 A schematic diagram of an interaction 400 between devices according to some example embodiments of the present disclosure is shown. For example, the interaction 400 involves an IAB node 130 (such as IAB node 130-1 or 130-2), an IAB donor node 120, and an AMF 113.

[0072] like Figure 4 As shown, the IAB MT 131 sends a 401 Registration Request to the AMF 113 via a NAS connection.

[0073] In some example embodiments, the registration request may include identification information of IAB node 130. For example, the identification information of IAB node 130 may be an access node identification of IAB node 130, such as at least one of TAI, PCI, and CGI of IAB node 130. In some example embodiments, the identification information of IAB node 130 may include an indication of an operation mode of IAB node 130. For example, such an indication may also imply an IAB implementation option or an operation mode, such as a fixed IAB, a nomadic IAB, or a mobile IAB.

[0074] In some example embodiments, the indication of the operating mode of the IAB node 130 may have different forms. For example, the indication of the operating mode may be an IAB indicator, which indicates that the IAB node 130 is fixed, mobile or nomadic. That is, such an indication may also imply an IAB implementation option or operating mode, such as a fixed IAB, a nomadic IAB or a mobile IAB. For another example, the indication of the operating mode may be a mobile IAB indicator, which indicates whether the IAB node 130 is a mobile IAB node. In some cases, different IAB nodes may be assigned different identifiers (IDs), wherein a predetermined ID range may indicate a mobile IAB node, and other IDs may indicate a fixed IAB node or a nomadic IAB node. For example, in this case, the indication of the operating mode may be an ID of the IAB node 130, which may be used to identify that the IAB node is a mobile IAB node, a fixed IAB node or a nomadic IAB node.

[0075] like Figure 4 As shown, AMF 113 obtains 402 subscription data from UDM 112. For example, the subscription data may indicate the network slice subscribed by IAB node 130. AMF 113 sends 403 a registration accept message to IAB MT 131 via a NAS connection. For example, the registration accept message may not indicate the registration area or the allowed network slices of IAB node 130. IAB MT 131 forwards 404 the registration accept message to IABDU 132 to indicate that there is no registration area and allowed network slices. In some example embodiments, AMF 113 may also send a registration accept message ( Figure 4 not shown).

[0076] like Figure 4 As shown, in the F1-AP process, the IAB DU 132 provides 405 information about supported network slices (such as S-NSSAI of these network slices) to the IAB donor CU 121. The IAB donor CU 121 provides 406 the slice support information to the AMF 113 for each TA in the NG configuration update process. The AMF 113 determines 407 the network slices allowed to be accessed by the IAB node 130, and the registration areas corresponding to the allowed network slices. In some example embodiments, the AMF 113 may determine the allowed network slices based on the supported network slices provided in the F1-AP process, the subscribed network slices obtained from the UDM 112, and the network slices supported by the IAB donor node 120 and / or the identification information of the IAB node 130 (such as TAI / PCI / CGI).

[0077] AMF 113 sends 408 a message to IAB MT 131 indicating the registration area and allowed network slices in the UE configuration update procedure. In some example embodiments, any deviation from the supported S-NSSAI provided in the F1-AP procedure shall be transmitted via the gNB DU configuration update procedure ( Figure 4 ) is transmitted to the IAB donor CU 121.

[0078] exist Figure 4 In the example shown, non-UE associated signaling is used to provide slice support information for the mobile IAB node. For the UE associated signaling part, the IAB MT also provides access node identification information, such as TAI, PCI or CGI. However, the requested S-NSSAI is not included. Unlike conventional UEs, the AMF waits to receive slice support information for the mobile IAB node from the IAB donor CU. The slice support information is provided to the AMF by the IAB donor CU via the NG application protocol. Considering the access node identification information of the mobile IAB node, the AMF can determine the slice support information of the mobile IAB node (such as allowing S-NSSAI), and can determine the registration of the mobile IAB node.

[0079] In some example embodiments, the IAB node may change TA association, for example, when the IAB node moves to a new TA or the IAB node migrates to a new donor IAB node or parent IAB node in a different TA that is not included in its registration area. In this case, the same Figure 2 , Figure 3 or Figure 4 A process similar to the above example shown. For example, the AMF 113 may provide the mobile IAB node 130 with an allowed S-NSSAI based on the intersection of the network slices subscribed by the mobile IAB node 130 and the network slices supported by the IAB donor node 120 (as advertised). The IAB donor node 120 may then detect which network slices may be considered supported in the TAI of the IAB node 130. Once the IAB node 130 is up and running for use by the UE, and after interacting with the IAB node 130 via the F1-AP process, the IAB donor node 120 may use the NG application protocol to confirm this information to the AMF.

[0080] Figure 5 A flowchart of an example method 500 for IAB communication according to some example embodiments of the present disclosure is shown. The method 500 may be performed in Figure 1 The method 500 is implemented at the IAB node 130 shown. It should be understood that the method 500 may include additional blocks not shown and / or may omit some of the blocks shown, and the scope of the present disclosure is not limited in this regard.

[0081] In block 510, the IAB node 130 sends a registration request to an AMF (eg, AMF 113), the registration request including information about the IAB node.

[0082] In box 520, the IAB node 130 receives a message from the AMF indicating a registration area and at least one allowed network slice for access by the IAB node, the registration area and the at least one allowed network slice being determined based on the information about the IAB node.

[0083] In some example embodiments, the information about the IAB node may include information about at least one network slice requested by the IAB node. The IAB node 130 may receive a registration accept message from the AMF indicating a registration area and at least one allowed network slice, the registration area and the at least one allowed network slice being determined based on the at least one network slice requested by the IAB node.

[0084] In some example embodiments, IAB node 130 may provide information about at least one allowed network slice to an IAB donor node (e.g., IAB donor node 120), such that the IAB donor node sends information about one or more allowed network slices of the at least one allowed network slice to the AMF.

[0085] In some example embodiments, the information about the IAB node may include user location information of the IAB node. The IAB node 130 may receive a registration acceptance message from the AMF, the registration acceptance message indicating a registration area and a network slice allowed for the backhaul link, the registration area and the network slice being determined based on the user location information.

[0086] In some example embodiments, the IAB node 130 may obtain, from the OAM, a configuration regarding at least one network slice to be supported by the IAB node, the configuration being determined by the OAM based on the user location information.

[0087] In some example embodiments, the OAM may obtain user location information from the IAB node or the AMF.

[0088] In some example embodiments, IAB node 130 may provide information about at least one network slice to an IAB donor node (e.g., IAB donor node 120), such that the IAB donor node sends information about one or more network slices in the at least one network slice to the AMF.

[0089] In some example embodiments, the information about the IAB node may include identification information of the IAB node. The IAB node 130 may receive a message from the AMF indicating a registration area and at least one allowed network slice, the registration area and the at least one allowed network slice being determined based on at least one network slice supported by the IAB donor node and the identification information.

[0090] In some example embodiments, the identification information may include at least one of: an indication of an operating mode of the IAB node, a physical cell identity, a tracking area identity, and a cell global identity.

[0091] In some example embodiments, the indication may indicate that the IAB node is a mobile, fixed, or nomadic IAB node.

[0092] In some example embodiments, the IAB node 130 may provide information about at least one allowed network slice to the IAB donor node, such that the IAB donor node sends information about one or more allowed network slices of the at least one allowed network slice to the AMF.

[0093] In some example embodiments, the number of network slices requested by the IAB node and / or the number of network slices allowed to be accessed by the IAB node may exceed 8.

[0094] Figure 6 FIG. 6 is a flowchart showing an example method 600 for IAB communication according to some example embodiments of the present disclosure. The method 600 may be performed in a manner such as Figure 1 The method 600 is implemented at the AMF 113 shown. It should be understood that the method 600 may include additional blocks not shown and / or some of the blocks shown may be omitted, and the scope of the present disclosure is not limited in this regard.

[0095] At block 610 , the AMF 113 receives a registration request from an IAB node (eg, the IAB node 130 ), the registration request including information about the IAB node.

[0096] In box 620, the AMF 113 sends a message to the IAB node indicating a registration area and at least one allowed network slice for access by the IAB node, where the registration area and the allowed network slice are determined based on the information about the IAB node.

[0097] In some example embodiments, the information about the IAB node may include information about at least one network slice requested by the IAB node. AMF 113 may determine at least one allowed network slice based on at least one network slice requested by the IAB node, at least one network slice supported by the IAB donor node, and at least one network slice subscribed by the IAB node and obtained from the unified data repository. AMF 113 may determine a registration area based on the at least one allowed network slice.

[0098] In some example embodiments, AMF 113 may determine a network slice allowed for the backhaul link based on the information, the network slice being included in at least one allowed network slice.

[0099] In some example embodiments, the AMF 113 may send a registration accept message to the IAB node indicating the registration area and at least one allowed network slice.

[0100] In some example embodiments, AMF 113 may provide information about at least one allowed network slice to an IAB donor node (e.g., IAB donor node 120).

[0101] In some example embodiments, the information about the IAB node may include user location information of the IAB node. The AMF 113 may determine the registration area and the network slice allowed for the backhaul link based on the user location information.

[0102] In some example embodiments, the AMF 113 may send a registration accept message to the IAB node, indicating the registration area and the network slices allowed for the backhaul link.

[0103] In some example embodiments, the AMF 113 may provide user location information to the operation supervision and maintenance function so that the operation supervision and maintenance function configures at least one network slice to be supported for the IAB node based on the user location information.

[0104] In some example embodiments, the information about the IAB node may include identification information of the IAB node.AMF 113 may determine a registration area and at least one allowed network slice based on at least one network slice supported by the IAB donor node and the identification information.

[0105] In some example embodiments, the identification information may include at least one of: an indication of an operating mode of the IAB node, a physical cell identity, a tracking area identity, and a cell global identity.

[0106] In some example embodiments, the indication may indicate that the IAB node is a mobile, fixed, or nomadic IAB node.

[0107] In some example embodiments, the AMF 113 may send a message to the IAB node indicating the registration area and at least one allowed network slice.

[0108] In some example embodiments, the registration area includes a set of tracking areas in which the at least one allowed network slice is supported. The AMF 113 may receive information about one or more of the at least one allowed network slices from the IAB donor node, the one or more of the at least one allowed network slices being supported in one of the tracking areas corresponding to the tracking area identification of the IAB node.

[0109] In some example embodiments, the number of network slices requested by the IAB node and / or the number of network slices allowed to be accessed by the IAB node may exceed 8.

[0110] In some example embodiments, a device capable of executing method 500 may include a component for executing the corresponding steps of method 500. The component may be implemented in any suitable form. For example, the component may be implemented in a circuit system or a software module.

[0111] In some example embodiments, a device capable of performing method 500 (e.g., IAB node 130) includes: a component for sending a registration request including information about the device to an AMF; and a component for receiving a message from the AMF indicating a registration area and at least one allowed network slice for access by the device, wherein the registration area and the at least one allowed network slice are determined based on the information about the device.

[0112] In some example embodiments, the information about the device includes information about at least one network slice requested by the device, and the component for receiving the message includes: a component for receiving a registration acceptance message from the AMF indicating a registration area and at least one allowed network slice, wherein the registration area and the at least one allowed network slice are determined based on the indication and the at least one network slice requested by the device.

[0113] In some example embodiments, the apparatus capable of performing method 500 further includes a component for providing information about at least one network slice to the IAB donor node, such that the IAB donor node sends information about one or more of the at least one allowed network slices to the AMF.

[0114] In some example embodiments, the information about the device includes user location information of the device, and the component for receiving the message includes: a component for receiving a registration acceptance message from the AMF, the registration acceptance message indicating a registration area and a network slice allowed for a backhaul link, the registration area and the network slice being determined based on the user location information.

[0115] In some example embodiments, the apparatus capable of performing method 500 further includes a component for obtaining, from an OAM, a configuration regarding at least one network slice to be supported by the apparatus, the configuration being determined by the OAM based on user location information.

[0116] In some example embodiments, the OAM obtains the user location information from the device or AMF.

[0117] In some example embodiments, the apparatus capable of performing method 500 further includes a component for providing information about at least one network slice to the IAB donor node, such that the IAB donor node sends information about one or more network slices in the at least one network slice to the AMF.

[0118] In some example embodiments, the information about the apparatus includes identification information of the IAB node, and the component for receiving the message includes: a component for receiving a message from the AMF indicating a registration area and at least one allowed network slice, wherein the registration area and the at least one allowed network slice are determined based on at least one network slice supported by the IAB donor node and the identification information.

[0119] In some example embodiments, the identification information comprises at least one of: an indication of an operating mode, a physical cell identity, a tracking area identity, and a cell global identity.

[0120] In some example embodiments, the indication specifies that the apparatus is a mobile, fixed or nomadic IAB node.

[0121] In some example embodiments, the apparatus capable of performing method 500 further includes a component for providing information about at least one allowed network slice to the IAB donor node, such that the IAB donor node sends information about one or more allowed network slices of the at least one allowed network slice to the AMF.

[0122] In some example embodiments, the number of network slices requested by the device and / or the number of network slices allowed to be accessed by the device exceeds 8.

[0123] In some example embodiments, an apparatus capable of executing method 600 may include a component for executing the corresponding steps of method 600. The component may be implemented in any suitable form. For example, the component may be implemented in a circuit system or a software module.

[0124] In some example embodiments, an apparatus (e.g., AMF 113) capable of performing method 600 includes: a component for receiving a registration request including information about the IAB node from an IAB node; and a component for sending a message to the IAB node, the message indicating a registration area and at least one allowed network slice for access by the IAB node, the registration area and the at least one allowed network slice being determined based on the information about the IAB node.

[0125] In some example embodiments, the information about the IAB node includes information about at least one network slice requested by the IAB node, and the apparatus capable of performing method 600 further includes: a component for determining at least one allowed network slice based on at least one network slice requested by the IAB node, at least one network slice supported by the IAB donor node, and at least one network slice subscribed by the IAB node and obtained from a unified data repository; and a component for determining a registration area based on the at least one allowed network slice.

[0126] In some example embodiments, the apparatus capable of performing method 600 further includes a component for determining a network slice allowed for a backhaul link based on the information, the network slice being included in at least one allowed network slice.

[0127] In some example embodiments, the component for sending the message includes: a component for sending a registration acceptance message indicating a registration area and at least one allowed network slice to the IAB node.

[0128] In some example embodiments, the apparatus capable of performing method 600 further includes means for providing information about at least one allowed network slice to the IAB donor node.

[0129] In some example embodiments, the information about the IAB node includes user location information of the IAB node, and the apparatus capable of executing method 600 further includes: a component for determining a registration area and a network slice allowed for a backhaul link based on the user location information.

[0130] In some example embodiments, the component for sending the message includes: a component for sending a registration acceptance message to the IAB node, the registration acceptance message indicating the registration area and the network slices allowed for the backhaul link.

[0131] In some example embodiments, the apparatus capable of executing method 600 further includes: a component for providing user location information to an operation supervision and maintenance function, so that the operation supervision and maintenance function configures at least one network slice to be supported for the IAB node based on the user location information.

[0132] In some example embodiments, the information about the IAB node includes identification information of the IAB node, and the apparatus capable of performing method 600 further includes: a component for determining a registration area and at least one allowed network slice based on at least one network slice supported by the IAB donor node and the identification information.

[0133] In some example embodiments, the identification information comprises at least one of: an indication of an operating mode, a physical cell identity, a tracking area identity, and a cell global identity.

[0134] In some example embodiments, the indication specifies whether the IAB node is a mobile, fixed, or nomadic IAB node.

[0135] In some example embodiments, the component for sending a message includes: a component for sending a message to the IAB node indicating a registration area and at least one allowed network slice.

[0136] In some example embodiments, the registration area includes a set of tracking areas in which at least one allowed network slice is supported, and the apparatus capable of performing method 600 further includes: a component for receiving information about one or more of the at least one allowed network slices from the IAB donor node, wherein the one or more of the at least one allowed network slices are supported in one of the tracking areas corresponding to the tracking area identifier of the IAB node.

[0137] In some example embodiments, the number of network slices requested by the IAB node and / or the number of network slices allowed to be accessed by the IAB node exceeds 8.

[0138] Figure 7 is a simplified block diagram of a device 700 suitable for implementing an embodiment of the present disclosure. For example, Figure 1 The IAB donor node 120, IAB node 130, terminal device 150 and / or AMF 113 shown may be implemented by device 700. As shown, device 700 includes one or more processors 710, one or more memories 720 coupled to processor 710, and one or more communication modules 740 coupled to processor 710.

[0139] The communication module 740 is used for two-way communication. The communication module 740 has at least one antenna to facilitate communication. The communication interface may represent any interface necessary to communicate with other network elements.

[0140] Processor 710 may be of any type suitable for the local technology network, and may include, as non-limiting examples, one or more of a general purpose computer, a special purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture. Device 700 may have multiple processors, such as application specific integrated circuit chips that are time slaved to a clock synchronized with a main processor.

[0141] The memory 720 may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memories include, but are not limited to, read-only memory (ROM) 724, electrically programmable read-only memory (EPROM), flash memory, hard disk, compact disk (CD), digital video disk (DVD), and other magnetic storage and / or optical storage. Examples of volatile memories include, but are not limited to, random access memory (RAM) 722 and other volatile memories that do not persist during power outages.

[0142] The computer program 730 includes computer executable instructions that are executed by the associated processor 710. The program 730 may be stored in the ROM 724. The processor 710 may perform any suitable actions and processes by loading the program 730 into the RAM 722.

[0143] The embodiments of the present disclosure may be implemented by a program 730, so that the device 700 may execute the reference Figure 2-Figure 6 Any process of the present disclosure discussed. The embodiments of the present disclosure may also be implemented by hardware or a combination of software and hardware.

[0144] In some example embodiments, the program 730 may be tangibly embodied in a computer-readable medium that may be included in the device 700 (such as in the memory 720) or in other storage devices accessible to the device 700. The device 700 may load the program 730 from the computer-readable medium to the RAM 722 for execution. The computer-readable medium may include any type of tangible non-volatile memory, such as ROM, EPROM, flash memory, hard disk, CD, DVD, etc. Figure 8 An example of a computer readable medium 800 is shown which may be in the form of a CD or DVD. The computer readable medium has a program 730 stored thereon.

[0145] It should be recognized that future networks may utilize network function virtualization (NFV), which is a network architecture concept that proposes virtualizing network node functions into "building blocks" or entities that can be operationally connected or linked together to provide services. A virtualized network function (VNF) may include one or more virtual machines that run computer program code using standard or general-purpose servers rather than custom hardware. Cloud computing or data storage may also be utilized. In radio communications, this may mean that node operations are at least partially performed in a central / centralized unit CU (e.g., a server, host, or node) that is operationally coupled to a distributed unit DU (e.g., a radio head / node). Node operations may also be distributed among multiple servers, nodes, or hosts. It should also be understood that the distribution of work between core network operations and base station operations may vary from implementation to implementation.

[0146] In one embodiment, the server can generate a virtual network through which the server communicates with the distributed unit. In general, a virtual network can involve the process of combining hardware and software network resources and network functions into a single software-based management entity (virtual network). Such a virtual network can provide a flexible distribution of operations between the server and the radio head / node. In practice, any digital signal processing task can be performed in the CU or DU, and the boundary at which responsibility is transferred between the CU and the DU can be selected according to the implementation.

[0147] Thus, in one embodiment, a CU-DU architecture is implemented. In this case, the device 700 may be included in a central unit (e.g., a control unit, an edge cloud server, a server), which is operably coupled (e.g., via a wireless or wired network) to a distributed unit (e.g., a remote radio head / node). That is, the central unit (e.g., an edge cloud server) and the distributed units may be independent devices that communicate with each other via a radio path or via a wired connection. Alternatively, they may be located in the same entity that communicates via a wired connection, etc. The edge cloud or edge cloud server may serve multiple distributed units or radio access networks. In one embodiment, at least some of the above processes may be performed by the central unit. In another embodiment, the device 700 may instead be included in a distributed unit, and at least some of the above processes may be performed by the distributed unit.

[0148] In one embodiment, the execution of at least some of the functions of the device 700 can be shared between two physically separate devices (DU and CU) that form an operating entity. Therefore, it can be seen that the device depicts an operating entity including one or more physically separate devices for performing at least some of the above-mentioned processes. In one embodiment, such a CU-DU architecture can provide a flexible allocation of operations between the CU and the DU. In practice, any digital signal processing task can be performed in the CU or the DU, and the boundary at which responsibility is transferred between the CU and the DU can be selected according to the implementation. In one embodiment, the device 700 controls the execution of the above-mentioned processes, regardless of the location of the above-mentioned devices, and also regardless of where the above-mentioned processes / functions are executed.

[0149] Generally, various embodiments of the present disclosure may be implemented using hardware or dedicated circuits, software, logic, or any combination thereof. Some aspects may be implemented using hardware, while other aspects may be implemented using firmware or software that may be executed by a controller, microprocessor, or other computing device. Although various aspects of the embodiments of the present disclosure are illustrated and described as block diagrams, flow charts, or using some other graphical representations, it should be understood that, as non-limiting examples, the blocks, devices, systems, techniques, or methods described herein may be implemented using hardware, software, firmware, dedicated circuits or logic, general-purpose hardware or controllers or other computing devices, or some combination thereof.

[0150] The present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer-readable storage medium. The computer program product includes computer executable instructions, such as instructions included in a program module, which are executed in a device on a target real or virtual processor to perform the above referenced Figure 5 The method 500 described and / or referenced above Figure 6 Method 600 described. Typically, program modules include routines, programs, libraries, objects, classes, components, data structures, etc. that perform specific tasks or implement specific abstract data types. In various embodiments, the functions of program modules can be combined or split between program modules as needed. The machine executable instructions of program modules can be executed in local or distributed devices. In distributed devices, program modules can be located in both local and remote storage media.

[0151] The program code for executing the disclosed method can be written in any combination of one or more programming languages. These program codes can be provided to a processor or controller of a general-purpose computer, a special-purpose computer or other programmable data processing device so that the program code causes the function / operation specified in the flow chart and / or block diagram to be realized when executed by the processor or controller. The program code can be executed completely on the machine, partially on the machine, as an independent software package, partially on the machine and partially on a remote machine, or completely on a remote machine or server.

[0152] In the context of the present disclosure, computer program codes or related data may be carried by any suitable carrier to enable a device, apparatus or processor to perform various processes and operations as described above. Examples of carriers include signals, computer readable media, etc.

[0153] The computer readable medium can be a computer readable signal medium or a computer readable storage medium. The computer readable medium can include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared or semiconductor systems, devices or equipment, or any suitable combination of the foregoing. A more specific example of a computer readable storage medium will include an electrical connection with one or more wires, a portable computer floppy disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0154] In addition, although the operations are described in a particular order, this should not be understood as requiring such operations to be performed in the particular order shown or in order or performing all the operations shown to obtain the desired result. In some cases, multitasking and parallel processing may be advantageous. Similarly, although several specific implementation details are included in the above discussion, these should not be interpreted as limitations on the scope of the present disclosure, but rather descriptions of features that may be specific to a particular embodiment. Certain features described in the context of a separate embodiment may also be implemented in combination in a single embodiment. On the contrary, the various features described in the context of a single embodiment may also be implemented in multiple embodiments individually or in any suitable sub-combination.

[0155] Although the present disclosure has been described in language specific to structural features and / or methodological acts, it should be understood that the present disclosure defined in the appended claims is not necessarily limited to the specific features or acts described above. Instead, the specific features and acts described above are disclosed as example forms of implementing the claims.

Claims

1. A method comprising: sending a registration request from an integrated access and backhaul node to an access and mobility management function, the registration request including information about the integrated access and backhaul node; receiving a message from the access and mobility management function, the message indicating a registration area and at least one allowed network slice for access by the integrated access and backhaul node, the registration area and the at least one allowed network slice being determined based on the information about the integrated access and backhaul node; as well as providing information about the at least one allowed network slice to an integrated access and backhaul donor node, such that the integrated access and backhaul donor node sends information about one or more allowed network slices of the at least one allowed network slice to the access and mobility management function; The information about the integrated access and backhaul node includes identification information of the integrated access and backhaul node, and receiving the message includes: receiving, from the access and mobility management function, the message indicating the registration area and the at least one allowed network slice, the registration area and the at least one allowed network slice being determined based on the identification information and at least one network slice supported by an integrated access and backhaul donor node; The identification information includes at least an indication of an operation mode, the indication indicating whether the integrated access and backhaul node is a mobile, fixed or nomadic integrated access and backhaul node; The registration area includes a set of tracking areas, the at least one allowed network slice is supported in the set of tracking areas, and the method further includes: The integrated access and backhaul donor node sends information about one or more allowed network slices of the at least one allowed network slice, wherein the one or more allowed network slices of the at least one allowed network slice are supported in one of the tracking areas, and the one tracking area corresponds to the tracking area identifier of the integrated access and backhaul node.

2. The method of claim 1 , wherein the information about the integrated access and backhaul node comprises information about at least one network slice requested by the integrated access and backhaul node, and receiving a message comprises: A registration accept message is received from the access and mobility management function indicating the registration area and the at least one allowed network slice, wherein the registration area and the at least one allowed network slice are determined based on the at least one network slice requested by the integrated access and backhaul node.

3. The method of claim 1 , wherein the information about the integrated access and backhaul node comprises user location information of the integrated access and backhaul node, and receiving a message comprises: A registration accept message is received from the access and mobility management function, the registration accept message indicating the registration area and the network slice allowed for the backhaul link, the registration area and the network slice being determined based on the user location information.

4. The method according to claim 3, further comprising: Obtaining, from an operations supervision and maintenance function, a configuration of at least one network slice to be supported by the integrated access and backhaul node, the configuration being determined by the operations supervision and maintenance function based on the user location information.

5. The method according to claim 4, wherein the operation supervision and maintenance function obtains the user location information from the integrated access and backhaul node or the access and mobility management function.

6. The method according to claim 4, further comprising: Providing information about the at least one network slice to an integrated access and backhaul donor node so that the integrated access and backhaul donor node sends information about one or more of the at least one network slice to the access and mobility management function.

7. The method according to claim 1, wherein the identification information further includes at least one of the following: Physical cell identification, Tracking area identifier, and Cell global identifier.

8. The method according to claim 1, further comprising: Providing information about the at least one allowed network slice to the integrated access and backhaul donor node so that the integrated access and backhaul donor node sends information about one or more allowed network slices of the at least one allowed network slice to the access and mobility management function.

9. The method according to any one of claims 1 to 8, wherein the number of network slices requested by the integrated access and backhaul node and / or the number of network slices allowed for access by the integrated access and backhaul node exceeds 8.

10. A method comprising: receiving, at an access and mobility management function and from an integrated access and backhaul node, a registration request including information about the integrated access and backhaul node; sending a message to the integrated access and backhaul node, the message indicating a registration area and at least one allowed network slice for access by the integrated access and backhaul node, the registration area and the at least one allowed network slice being determined based on the information about the integrated access and backhaul node; as well as providing information about the at least one allowed network slice to an integrated access and backhaul donor node; The information about the integrated access and backhaul node includes identification information of the integrated access and backhaul node, and the method further includes: determining the registration area and the at least one allowed network slice based on the identification information and at least one network slice supported by the integrated access and backhaul donor node; The identification information includes at least an indication of an operation mode, the indication indicating whether the integrated access and backhaul node is a mobile, fixed or nomadic integrated access and backhaul node; The registration area includes a set of tracking areas, the at least one allowed network slice is supported in the set of tracking areas, and the method further includes: Information about one or more of the at least one allowed network slices is received from an integrated access and backhaul donor node, wherein the one or more of the at least one allowed network slices are supported in one of the tracking areas, and the one tracking area corresponds to a tracking area identifier of the integrated access and backhaul node.

11. The method of claim 10, wherein the information about the integrated access and backhaul node comprises information about at least one network slice requested by the integrated access and backhaul node, and the method further comprises: determining the at least one allowed network slice based on the at least one network slice requested by the integrated access and backhaul node, at least one network slice supported by an integrated access and backhaul donor node, and at least one network slice subscribed by the integrated access and backhaul node and obtained from a unified data repository; as well as The registration area is determined based on the at least one allowed network slice.

12. The method according to claim 11, further comprising: A network slice allowed for the backhaul link is determined based on the information, and the network slice is included in the at least one allowed network slice.

13. The method of claim 11, wherein sending the message comprises: A registration accept message is sent to the integrated access and backhaul node, wherein the registration accept message indicates the registration area and the at least one allowed network slice.

14. The method according to claim 10, wherein the information about the integrated access and backhaul node includes user location information of the integrated access and backhaul node, and the method further comprises: The registration area and the network slice allowed for the backhaul link are determined based on the user location information.

15. The method of claim 14, wherein sending the message comprises: A registration accept message is sent to the integrated access and backhaul node, the registration accept message indicating the registration area and the network slice allowed to be used for the backhaul link.

16. The method according to claim 14, further comprising: The user location information is provided to an operation supervision and maintenance function so that the operation supervision and maintenance function configures at least one network slice to be supported by the integrated access and backhaul node based on the user location information.

17. The method according to claim 10, wherein the identification information further includes at least one of the following: Physical cell identification, Tracking area identifier, and Cell global identifier.

18. The method of claim 10, wherein sending a message comprises: The message indicating the registration area and the at least one allowed network slice is sent to the integrated access and backhaul node.

19. The method according to any one of claims 10 to 18, wherein the number of network slices requested by the integrated access and backhaul node and / or the number of network slices allowed for access by the integrated access and backhaul node exceeds 8.

20. An apparatus comprising: at least one processor; as well as at least one memory including computer program code; The at least one memory and the computer program code are configured to, together with the at least one processor, cause the apparatus to perform the method according to any one of claims 1 to 9.

21. An apparatus comprising: at least one processor; as well as at least one memory including computer program code; The at least one memory and the computer program code are configured to, together with the at least one processor, cause the apparatus to perform a method according to any one of claims 10 to 19.

22. An apparatus comprising means for performing the method according to any one of claims 1 to 9.

23. An apparatus comprising means for performing the method according to any one of claims 10 to 19.

24. A computer program product stored on a computer readable medium and comprising machine executable instructions, wherein the machine executable instructions, when executed, cause a machine to perform the method according to any one of claims 1 to 19.

25. A computer-readable storage medium comprising program instructions stored thereon, which instructions, when executed by a device, cause the device to perform the method according to any one of claims 1 to 19.

Images