CN117014863A

CN117014863A - Network sharing in UE-to-network relay scenarios

Info

Publication number: CN117014863A
Application number: CN202310495572.0A
Authority: CN
Inventors: 许翔; 于�玲; V·范潘; G·T·沃尔纳; J·L·布特勒
Original assignee: Nokia Shanghai Bell Co Ltd; Nokia Solutions and Networks Oy
Current assignee: Nokia Shanghai Bell Co Ltd; Nokia Solutions and Networks Oy
Priority date: 2022-05-06
Filing date: 2023-05-05
Publication date: 2023-11-07
Also published as: WO2023212892A1

Abstract

Example embodiments of the present disclosure relate to apparatuses, methods, devices, and computer-readable storage media for network sharing in U2N relay scenarios. In an example embodiment, the first network device receives a first message from the first terminal device via the second terminal device or from the third network device, the first message comprising information for determining a target network device of the first terminal device. The first network device determines, based on the first message, that the target network device of the first terminal device is the second network device. The first network device transmits a second message to the second network device, the second message indicating that the first terminal device intends to communicate with the second network device via the second terminal device and the first network device. The second network device then transmits a third message to the third network device requesting configuration of at least one communication channel between the first network device and the second terminal device and/or at least one communication channel between the first terminal device and the second terminal device.

Description

Network sharing in UE-to-network relay scenarios

Technical Field

Example embodiments of the present disclosure relate generally to the field of communications and, in particular, relate to an apparatus, method, device, and computer-readable storage medium for network sharing in a User Equipment (UE) to network (U2N) relay scenario.

Background

With the development of communication technology, there is a new network architecture deployed to split the functions of base stations in an access network to improve flexibility of deployment. Some functions of the base station are deployed on a Centralized Unit (CU), while other functions are deployed on a Distributed Unit (DU). For example, a CU may be responsible for some higher-level protocol stack functions, and a DU may be responsible for lower-level functions.

Furthermore, network sharing is proposed. With this technique, a DU can be separated into many logical DU entities connected to many CUs. For example, if a DU is split into two logical DU entities, referred to as a first DU and a second DU, the first DU may be connected to the first CU and the second DU may be connected to the second CU. However, in a U2N relay scenario, the use of network sharing may lead to many compatibility issues.

Disclosure of Invention

In general, example embodiments of the present disclosure provide apparatuses, methods, devices, and computer-readable storage media for network sharing in a U2N relay scenario.

In a first aspect, a method is provided. In the method, the first network device receives a first message from the first terminal device via the second terminal device or from the third network device, the first message comprising information for determining a target network device of the first terminal device. The first network device then determines, based on the first message, that the target network device of the first terminal device is the second network device. Furthermore, the first network device transmits a second message to the second network device, the second message indicating that the first terminal device intends to communicate with the second network device via the second terminal device and the first network device.

In a second aspect, a method is provided. In the method, the second network device receives a second message from the first network device, the second message indicating that the first terminal device intends to communicate with the second network device via the second terminal device and the first network device. Furthermore, the second network device transmits a third message to the third network device requesting configuration of at least one communication channel between the first network device and the second terminal device and/or at least one communication channel between the first terminal device and the second terminal device. The second network device then receives a fourth message from the third network device, the fourth message comprising information for configuring at least one communication channel between the first network device and the second terminal device and/or at least one communication channel between the first terminal device and the second terminal device. Furthermore, the second network device transmits a fifth message towards the first terminal device, the fifth message being used to configure at least one communication channel between the first terminal device and the second terminal device.

In a third aspect, a method is provided. In the method, a third message is received by a third network device from a second network device, the third message requesting configuration of at least one communication channel between the first network device and the second terminal device and/or at least one communication channel between the first terminal device and the second terminal device for communication between the second network device and the first terminal device via the first network device and the second terminal device. The third network device then configures at least one communication channel between the first network device and the second terminal device and/or at least one communication channel between the first terminal device and the second terminal device based on the third message. Furthermore, the third network device transmits a fourth message to the second network device, the fourth message comprising information for configuring at least one communication channel between the first network device and the second terminal device and/or at least one communication channel between the first terminal device and the second terminal device.

In a fourth aspect, a first network device is provided that 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 first network device to receive a first message from the first terminal device via the second terminal device, or from the third network device, the first message comprising information for determining a target network device of the first terminal device; determining, based on the first message, that the target network device of the first terminal device is a second network device; and transmitting a second message to the second network device, the second message indicating that the first terminal device intends to communicate with the second network device via the second terminal device and the first network device.

In a fifth aspect, a second network device is provided that 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 second network device to receive a second message from the first network device, the second message indicating that the first terminal device intends to communicate with the second network device via the second terminal device and the first network device; transmitting a third message to the third network device requesting configuration of at least one communication channel between the first network device and the second terminal device and/or at least one communication channel between the first terminal device and the second terminal device; receiving a fourth message from the third network device, the fourth message comprising information for configuring at least one communication channel between the first network device and the second terminal device and/or at least one communication channel between the first terminal device and the second terminal device; and transmitting a fifth message towards the first terminal device, the fifth message being for configuring at least one communication channel between the first terminal device and the second terminal device.

In a sixth aspect, a third network device is provided that 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 third network device to receive a third message from the second network device requesting configuration of at least one communication channel between the first network device and the second terminal device and/or at least one communication channel between the first terminal device and the second terminal device for communication between the second network device and the first terminal device via the first network device and the second terminal device; configuring at least one communication channel between the first network device and the second terminal device and/or at least one communication channel between the first terminal device and the second terminal device based on the third message; and transmitting a fourth message to the second network device, the fourth message comprising information for configuring at least one communication channel between the first network device and the second terminal device and/or at least one communication channel between the first terminal device and the second terminal device.

In a seventh aspect, there is provided an apparatus comprising means for performing the method according to the first or second or third aspect.

In an eighth aspect, a computer readable storage medium is provided, the computer readable storage medium including program instructions stored thereon. The instructions, when executed by a processor of a device, cause the device to perform a method according to the first or second or third aspect.

It should be understood that the summary is not intended to identify key or essential features of the example embodiments of the disclosure, nor is it intended to be used to limit the scope of the disclosure. Other features of the present disclosure will become apparent from the following description.

Drawings

Some example embodiments will now be described with reference to the accompanying drawings, in which:

fig. 1 shows a schematic diagram for sharing a relay UE and a remote UE;

FIG. 2 illustrates an example environment in which example embodiments of the present disclosure may be implemented;

fig. 3 illustrates signaling flows between a first network device, a second network device, and a third network device according to some example embodiments of the present disclosure;

FIG. 4 illustrates an example process according to some example embodiments of the present disclosure;

FIG. 5 illustrates a flowchart of an example method according to some example embodiments of the present disclosure;

FIG. 6 illustrates a flowchart of an example method according to some other example embodiments of the present disclosure;

FIG. 7 illustrates a flowchart of an example method according to some further example embodiments of the present disclosure; and

fig. 8 shows a simplified block diagram of a device suitable for implementing example embodiments of the present disclosure.

Throughout the drawings, the same or similar reference numerals denote the same or similar elements.

Detailed Description

Principles of the present disclosure will now be described with reference to some example embodiments. It should be understood that these example embodiments are described for illustrative purposes only and to assist those skilled in the art in understanding and practicing the present disclosure without placing any limitation on the scope of the disclosure. The disclosure described herein may be implemented in various other ways than described below.

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.

As used herein, the term "network device" refers to a device via which services can be provided to terminal devices in a communication network. For example, the network device may include a base station or a device that may implement some of the functions of a base station, such as a CU or DU. As used herein, the term "base station" (BS) refers to a network device via which services may be provided to terminal devices in a communication network. A base station may comprise any suitable device via which a terminal device or UE may access a communication network. Examples of base stations include relays, access Points (APs), transmission points (TRPs), node bs (nodebs or NB), evolved nodebs (eNodeB or eNB), new Radio (NR) nodebs (gNB), remote radio modules (RRU), radio Headers (RH), remote Radio Heads (RRH), low power nodes (such as femto, pico), etc.

As used herein, the term "terminal device" or "user equipment" (UE) refers to any terminal device capable of wireless communication with each other or with a base station. Communication may involve the transmission and/or reception of wireless signals using electromagnetic signals, radio waves, infrared signals, and/or other types of signals suitable for conveying information over the air. In some example embodiments, the UE may be configured to transmit and/or receive information without direct human interaction. For example, the UE may transmit information to the base station upon being triggered by an internal or external event, or in response to a request from the network side, according to a predetermined schedule.

Examples of UEs include, but are not limited to, smartphones, wireless enabled tablet computers, laptop embedded devices (LEEs), laptop installed devices (LMEs), wireless Customer Premise Equipment (CPE), sensors, metering devices, personal wearable devices (such as watches), and/or vehicles capable of communication. For purposes of discussion, some example embodiments will be described with reference to a UE as an example of a terminal device, and the terms "terminal device" and "user equipment" (UE) may be used interchangeably in the context of this disclosure.

As used herein, the term "circuitry" may refer to one or more or all of the following:

(a) Hardware-only circuit implementations (such as implementations in analog and/or digital circuitry only), and

(b) A combination of hardware circuitry and software, such as (as applicable):

(i) Combination of analog and/or digital hardware circuit(s) and software/firmware, and

(ii) Any portion of the hardware processor(s) having software, including digital signal processor(s), software, and memory(s), work together to cause a device (such as a mobile phone or server) to perform various functions, and (c) hardware circuit(s) and/or processor(s), such as microprocessor(s) or a portion of microprocessor(s), that require software (e.g., firmware) to operate, but software may not be present when software is not required to operate.

This definition of circuitry applies to all uses of this term in this application, including in any claims. As a further example, as used in this disclosure, the term circuitry also encompasses hardware-only circuits or processors (or multiple processors) or a portion of a hardware circuit or processor and its attendant software and/or firmware implementations. For example, if applicable to the particular claim elements, the term circuitry also encompasses a baseband integrated circuit or processor integrated circuit for a mobile device, or a similar integrated circuit in a server, a cellular base station, or other computing or base station.

As used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. The term "comprising" and variants thereof should be understood as open-ended terms, meaning "including, but not limited to. The term "based on" should be understood as "based at least in part on". The terms "one embodiment" and "an embodiment" should be understood as "at least one embodiment". The term "another embodiment" should be understood as "at least one other embodiment". Other explicit and implicit definitions may be included below.

As used herein, the terms "first," "second," and the like may be used to describe various elements, which should not be limited by these terms. These terms are only used to distinguish one element from another element. For example, a first element could be termed a second element, and, similarly, a second element could be termed a first element, without departing from the scope of example embodiments. As used herein, the term "and/or" includes any and all combinations of one or more of the listed terms.

In release 17 of the third generation partnership project (3 GPP), side link relay is discussed. The remote UE may connect with the relay UE via a PC5 interface. The relay UE may connect with the DU via the Uu interface. The DU may be connected with the CU via an F1 interface. Thus, the remote UE may communicate with the CU via the relay UE and the DU.

In 3GPP, there are some discussions about network sharing (or RAN sharing) in U2N relay. Details will be discussed with reference to fig. 1.

Fig. 1 shows a schematic diagram for sharing a relay UE and a remote UE. As shown in fig. 1, the home Public Land Mobile Network (PLMN) for the remote UE 121 is a first PLMN, e.g., the remote UE 121 has a Universal Subscriber Identity Module (USIM) from the first PLMN. The home PLMN for the remote UE 123 is a second PLMN, e.g., the remote UE 123 has a Universal Subscriber Identity Module (USIM) from the second PLMN. The home PLMN for the relay UE 125 is a first PLMN, e.g., the relay UE 125 has a Universal Subscriber Identity Module (USIM) from the first PLMN. Relay UE 125 is shared with the first PLMN and the second PLMN. Relay UE 125 may provide UE-to-network relay services to remote UE(s) from a first PLMN and remote UE(s) from a second PLMN. The gNB-DU 127, the first gNB-CU 129, and the first access and mobility management function (AMF) 133 are deployed or owned by the operator of the first PLMN. The second gNB-CU 131 and the second AMF 135 are deployed or owned by the operator of the second PLMN. The gNB-DU 127 is shared for the first PLMN and the second PLMN. The gNB-DU 127 includes two logical DU entities, referred to as a first DU entity and a second DU entity. The RRC of remote UE 121 and relay UE 125 terminates at a first gNB-CU 129. That is, gNB-CU 129 configures relay UE 125 and remote UE 121. The RRC of the remote UE 123 terminates at the second gNB-CU 131. That is, the second gNB-CU 131 configures the remote UE 123. Communication (e.g., control plane traffic (e.g., RRC signaling) and user plane traffic) between the remote UE 123 and the second gNB-CU 131 uses the relay UE 125 and the gNB-DU 127.

Since the first gNB-CU 129 configures the PC5 Radio Link Control (RLC) Channel (CH) of the relay UE 125, but the second gNB-CU 131 configures the PC5 RLC CH of the UE 123, there is a problem of ensuring that they are aligned so that the relay UE 125 and the UE 123 can establish a PC5 connection.

Further, the first gNB-CU 129 configures a first DU entity for Downlink (DL) mapping of control plane traffic and user plane traffic of the remote UE 121, e.g., from the F1-U tunnel to the Uu RLC CH between the gNB-DU 127 and the relay UE 125. The second gNB-CU 131 configures a second DU entity for DL mapping of control plane traffic and user plane traffic of the UE 123, e.g. from F1-U tunnels to Uu RLC CH between the gNB-DU 127 and the relay UE 125. The Uu RLC CH between the gNB-DU 127 and the relay UE 125 is configured only by the first gNB-CU 129.

Since the establishment/modification of the Uu RLC CH is related to the remote UE 123, e.g. the establishment of a new Uu RLC CH when the remote UE 123 is connected or when a Data Radio Bearer (DRB) of the remote UE 123 is added/modified/released, there is another problem of enabling the first gNB-CU 129 to know the quality of service (QoS) of the DRB of the UE 123, which is currently known only to the second gNB-CU 131.

Further, since the Uu RLC CH of the relay UE 125 is configured by the first gNB-CU 129, there is another problem of enabling the second gNB-CU 131 to know the Uu RLC CH of the relay UE 125 in order to configure the gNB-DU 127 to perform DL mapping.

Further, typically, the gNB-CU is responsible for local ID allocation for the remote UE. In this case, it may occur that the second gNB-CU 131 may assign a local ID to the UE 123, but that local ID may have been assigned to the remote UE 121 by the first gNB-CU 129. Since the local ID is assumed to be unique per relay UE, for example, when DL mapping from Uu RLC CH to PC5 RLC CH is performed, assigning the same local ID to the remote UE 121 and the remote UE 123 connected to the same relay UE 125 may cause a problem in the relay UE 125 and may also cause the same problem for Uplink (UL).

However, to date, there is no effective and efficient way to implement network sharing communications in a U2N relay scenario.

Example embodiments of the present disclosure provide a network sharing scheme in a U2N relay scenario. With this scheme, a network device such as a DU (referred to as a first network device) receives a first message including information for determining a target network device of the first terminal device from a terminal device such as a remote UE (referred to as a first terminal device) or from another network device such as a CU (referred to as a third network device) via another terminal device such as a relay UE (referred to as a second terminal device). The first network device determines, based on the first message, that the target network device of the first terminal device is another network device (referred to as a second network device), such as another CU. The first terminal device transmits a second message to the second network device, the second message indicating that the first terminal device intends to communicate with the second network device via the second terminal device and the first network device. The second network device then transmits a third message to the third network device requesting configuration of at least one communication channel between the first network device and the second terminal device and/or at least one communication channel between the first terminal device and the second terminal device. Accordingly, the third network device configures at least one communication channel between the first network device and the second terminal device and/or at least one communication channel between the first terminal device and the second terminal device based on the third message. Furthermore, the third network device transmits a fourth message to the second network device, the fourth message comprising information for configuring at least one communication channel between the first network device and the second terminal device and/or at least one communication channel between the first terminal device and the second terminal device. Furthermore, the second network device transmits a fifth message towards the first terminal device for configuring at least one communication channel between the first terminal device and the second terminal device. In an example embodiment, the communication channel is an RLC channel.

The scheme solves the compatibility problem of network sharing in the U2N relay scene. Accordingly, communication between a remote UE and its corresponding CU can be efficiently performed.

FIG. 2 illustrates an example environment 200 in which example embodiments of the present disclosure may be implemented.

Environment 200, which may be part of a communication network, includes three network devices 210, 220, and 230 that communicate with each other or with other devices via each other. For discussion purposes, network devices 210, 220, and 230 will be referred to as first network device 210, second network device 220, and third network device 230, respectively. For example, the first network device 210 may be under control of the third network device 230.

The environment 200 also includes two terminal devices 240 and 250 that communicate with each other or with other devices via each other. For discussion purposes, the terminal devices 240 and 250 will be referred to as a first terminal device 240 and a second terminal device 250, respectively. The first terminal device 240 may be intended to communicate with the second network device 220 via the second terminal device 250 and the first network device 210. For example, the second terminal device 250 may be under control of the third network device 230.

In some example embodiments, a DU will be referred to as an example of the first network device 210, a first CU will be referred to as an example of the second network device 220, and a second CU will be referred to as an example of the third network device 230. The remote UE will be referred to as an example of the first terminal device 240 and the relay UE will be referred to as an example of the second terminal device 250.

It should be understood that five devices are shown in environment 200 for illustrative purposes only and are not intended to suggest any limitation as to the scope of the disclosure. In some example embodiments, environment 200 may include additional devices for communicating information with one or more of the devices described above.

Communications in environment 200 may conform to any suitable communications standard or protocol that already exists or will be developed in the future, such as Universal Mobile Telecommunications System (UMTS), long Term Evolution (LTE), LTE-advanced (LTE-a), fifth generation (5G) New Radio (NR), wireless fidelity (Wi-Fi), and Worldwide Interoperability for Microwave Access (WiMAX) standards, and employ any suitable communications technology including, for example, multiple Input Multiple Output (MIMO), orthogonal Frequency Division Multiplexing (OFDM), time Division Multiplexing (TDM), frequency Division Multiplexing (FDM), code Division Multiplexing (CDM), bluetooth, zigBee, and Machine Type Communications (MTC), enhanced mobile broadband (eMBB), large-scale machine type communications, ultra-reliable low delay communications, carrier Aggregation (CA), dual Connectivity (DC), and new radio unlicensed (NR-U) technologies.

Fig. 3 illustrates a signaling flow 300 between a first network device 210, a second network device 220, and a third network device 230 according to some example embodiments of the present disclosure. For discussion purposes, signaling flow 300 will be described with reference to fig. 2. For example, the first terminal device 240 may be a remote terminal device and the second terminal device 250 may be a relay terminal device and the first network device 210 may be a distributed unit and the second network device 220 may be a first centralized unit and the third network device 230 may be a second centralized unit. For example, the third network device 230 may control the second terminal device 250.

In some example embodiments, the first terminal device 240 may initiate an RRC procedure, e.g., an RRC connection setup procedure or an RRC connection re-establishment procedure. Due to the lack of information about the PLMN (e.g., PLMN identification) of the first terminal device 240, the RRC procedure is performed with the third network device 230 controlling the second terminal device 250. During the RRC procedure, the third network device 230 assigns a local identity to the first terminal device 240. For example, in case the first terminal device 240 initiates the RRC connection setup procedure, at the end of the RRC connection establishment procedure, the first terminal device 240 transmits (305) a first message to the first network device 210 via the second terminal device 250, which first message indicates information about the PLMN of the first terminal device 240 (e.g. PLMN identity), e.g. information about the PLMN in an rrcsetup complete message, as shown in fig. 3. The first network device 210 then determines (310) that the target network device of the first terminal device 240 is the second network device 220 based on the first message (e.g., information about the PLMN). In another example, the first terminal device 240 initiates an RRC connection re-establishment procedure (not shown in the figure). Due to the lack of information about the PLMN of the first terminal device 240 (e.g. PLMN identity), the RRC connection re-establishment procedure is performed with the third network device 230 controlling the second terminal device 250. The first network device 210 receives a first message from the third network device 230 indicating that the third network device 230 does not support the PLMN of the first terminal device 240. In other words, in this case, the first message comprises information indicating that the third network device 230 has failed to be used for the first terminal device 240. Based on the indication, the first network device 210 determines (310) that another network device (i.e., the second network device 220) should be used for the RRC connection re-establishment procedure of the first terminal device 240.

The first network device 210 transmits (315) a second message to the second network device 220 indicating that the first terminal device 240 is intended to communicate with the second network device 220 via the second terminal device 250 and the first network device 210. For example, the second message may be an F1AP message, such as an "F1AP initial UL RRC message transmission" message.

For example, the second message may include an identifier of the first terminal device 240. For example, the identifier of the first terminal device 240 may be assigned by the third network device 230. In an example embodiment, the identifier of the first terminal device 240 may be a local ID assigned by the third network device 230. For example, the second message may include an identifier of the second terminal device 250, e.g., a cell radio network temporary identity (C-RNTI) or a layer 2 (L2) ID of the ProSe communication 5 (PC 5) connection of the second terminal device 250. For example, the second message may include an identifier of the first network device 210. Alternatively or additionally, the second message may include an identifier of the third network device 230 or any identifier that may be used to identify the third network device 230, e.g., a New Radio (NR) cell global identifier (NCGI), or a gNB-CU name, or a global NG-RAN node ID, etc.

The second network device 220 then transmits (320) a third message to the third network device 230 requesting configuration of at least one communication channel between the first network device 210 and the second terminal device 250 and/or at least one communication channel between the first terminal device 240 and the second terminal device 250. For example, the communication channel may include an RLC channel. For example, the second network device 220 may initiate an Xn adaptation protocol (XnAP) request message to request Uu RLC channel establishment or modification from the third network device 230 for the relay connection of the second terminal device 250.

In some example embodiments, the third message may include both the identifier of the first terminal device 240 and/or the identifier of the second terminal device 250 received in the second message. As another example, the third message may include an identifier of the first network device 210. Alternatively or additionally, the third message may comprise the context of the first terminal device 240.

For example, the context of the first terminal device 240 may include information of one or more DRBs. The information for each DRB includes an identifier of the DRB of the first terminal device 240 and/or a QoS of the DRB of the first terminal device 240, which may be used by, for example, the third network device 230 to establish or modify at least one communication channel between the first network device 210 and the second terminal device 250. As another example, the context of the first terminal device 240 may include information of one or more SRBs. The information of each SRB includes an identifier of a Signaling Radio Bearer (SRB) of the first terminal device 240 and/or a QoS of the SRB of the first terminal device 240. Alternatively or additionally, the context of the first terminal device 240 may include side link capability information of the first terminal device 240. For example, the side link capability information may include PC5 capability information of the first terminal device 240. Then, the third network device 230 may perform a corresponding PC5 configuration based on the PC5 capabilities of the first terminal device 240 and the QoS of the DRB or SRB.

As shown in fig. 3, the third network device 230 configures (325) at least one communication channel between the first network device 210 and the second terminal device 250 and/or at least one communication channel between the first terminal device 240 and the second terminal device 250 based on the third message. In some example embodiments, the third network device 230 may determine a configuration of at least one communication channel (e.g., uu RLC channel) between the first network device 210 and the second terminal device 250 and/or a configuration of at least one communication channel (e.g., PC5 RLC channel) between the first terminal device 240 and the second terminal device 250 based on the third message. The third network device 230 may then transmit to the first network device 210 a configuration of at least one communication channel between the first network device 210 and the second terminal device 250 and/or a configuration of at least one communication channel between the first terminal device 240 and the second terminal device 250. The third network device 230 may transmit the configuration of the at least one communication channel between the first terminal device 240 and the second terminal device 250 to the second terminal device 250 via the first network device 210. For example, the third network device 230 may initiate establishment or modification of at least one communication channel between the first network device 210 and the second terminal device 250. For example, the third network device 230 may decide whether to establish a new Uu RLC channel or modify an existing Uu RLC channel. For example, the third network device 230 may initiate the UE context modification procedure with a "UE context modification request" message that includes a Uu RLC channel list Information Element (IE) to be established and/or a Uu RLC channel list IE to be modified. For example, the third network device 230 may also configure the PC5 RLC channel for the second terminal device 250 in the same UE context modification procedure, e.g., via a PC5 RLC channel list IE to be established and/or a PC5 RLC channel list IE to be modified.

Further, the third network device 230 transmits (330) a fourth message to the second network device 220, the fourth message comprising information for configuring at least one communication channel between the first network device 210 and the second terminal device 250 and/or at least one communication channel between the first terminal device 240 and the second terminal device 250. Based on the configuration information received from the third network device 230, the second network device 220 then configures (335) the first terminal 240 for at least one communication channel between the first terminal device 240 and the second terminal device 250. The second network device 220 also configures the first network device 210, e.g., the mapping of DL control plane traffic and user plane traffic of the first terminal device 240 to Uu RLC CH between the first network device 210 and the second terminal device 250.

In some example embodiments, the fourth message may include an identifier of the first terminal device 240 and/or an identifier of the second terminal device 250. As another example, the fourth message may include information (or configuration information) associated with at least one communication channel between the first network device 210 and the second terminal device 250. For example, uu RLC channel information may include Uu RLC channel Identification (ID), qoS of Uu RLC channel, and the like. The Uu RLC channel information included in the fourth message may also be used by the second network device 220 to configure a DL mapping in the first network device 210. Alternatively or additionally, the fourth message may comprise information (or configuration information) associated with at least one communication channel between the first terminal device 240 and the second terminal device 250. For example, the PC5 RLC channel configuration information may include PC5 RLC CH ID, qoS of the PC5 RLC CH, and the like. The PC5 RLC channel configuration information may also be used by the second network device 220 to configure the first terminal device 240. As another example, the fourth message may include a side chain relay adaptation protocol (SRAP) (adaptation layer configuration) for the first terminal device 240, such as an egress RLC channel of PC5, so that the first terminal device 240 can know to which RLC channel the DRB should map.

As shown in fig. 3, the second network device 220 transmits a fifth message towards the first terminal device 240, the fifth message being used to configure at least one communication channel between the first terminal device 240 and the second terminal device 250. Accordingly, the first terminal device 240 may communicate with the second terminal device 250 based on the fifth message.

In some example embodiments, the DRB of the first terminal device 240 may be modified or released after the initial access procedure. The second network device 220 may initiate a new procedure (e.g., an XnAP procedure) to request the third network device 230 to modify or release the associated at least one communication channel. For example, the "XnAP request" message may include at least one of the following: an identifier of the first terminal device 240, an identifier of the second terminal device 250, an index of the Uu RLC channel to be modified or released. For each Uu RLC channel to be modified, the "request" message may include a new QoS for the DRB of the first terminal device 240, which the third network device 230 may use to establish or modify the Uu RLC channel between the first network device 210 and the second terminal device 250. For example, the "XnAP response" message may include at least one of the following: the identifier of the first terminal device 240, the identifier of the second terminal device 250, the index of Uu RLC channels that have been successfully modified, the index of Uu RLC channels that have not been modified, updated PC5 RLC CH configuration and SRAP configuration (if needed).

In this way, the compatibility problem of network sharing use in the U2N relay scenario can be solved. In this way, communication between a remote UE and its corresponding CU can be efficiently performed.

Fig. 4 illustrates an example process according to some example embodiments of the present disclosure. For discussion purposes, the process 400 will be described with reference to fig. 2. For example, the first network device 210 as shown in fig. 2 may be implemented by a gNB-DU 401, where the gNB-DU 401 may include a first DU entity and a second DU entity. The third network device 230 as shown in fig. 2 may be implemented by the gNB-CU 403 and the second network device 220 as shown in fig. 2 may be implemented by the gNB-CU 405. The first terminal device 240 as shown in fig. 2 may be implemented by the remote UE 407 and the second terminal device 250 as shown in fig. 2 may be implemented by the relay UE 409. The first DU entity is connected to the gNB-CU 403 and the second DU entity is connected to the second gNB-CU 405. The remote UE 407, the second DU entity and the gNB-CU 405 use (or support) the first PLMN. The relay UE 409, the first DU entity and the gNB-CU 403 use (or support) the second PLMN. The relay UE 409 is shared for the first PLMN. The relay UE 409 is controlled by the gNB-CU 403 and the RRC of the relay UE 409 terminates at the gNB-CU 403. The remote UE 407 is controlled by the gNB-CU 405 and the RRC of the remote UE 407 terminates at the gNB-CU 405.

As shown in fig. 4, a Radio Resource Control (RRC) setup procedure is performed at 411-426. Due to the lack of information about the PLMN of the remote UE 407, the RRC setup procedure is performed with the gNB-CU 403 controlling the relay UE 409. During the RRC establishment procedure, the gNB-CU 403 assigns a local identity to the remote UE 407. At 427, the gNB-DU 401 interprets the RRCSetup complete message and determines that the remote UE 407 is intended to communicate with the gNB-CU 405. Then, at 428, the gNB-DU 401 transmits a UE context release request message to the gNB-CU 403 to inform the gNB-CU 403 that the target network device of the remote UE 407 is not the gNB-CU 403.

Further, at 429, gNB-DU 401 transmits an F1 initial UL RRC message (i.e., a second message) to gNB-CU 405. For example, the F1 initial UL RRC message may include an identifier of the remote UE 407 (e.g., a local identity assigned by the gNB-CU 403), an identifier of the relay UE 409, and an identifier of the gNB-CU 403. Then, in step 430, the gNB-CU 405 sends an "initial UE message" message to the AMF 410 (i.e., the second AMF 135 in FIG. 1). In step 431, AMF 410 sends an "initial context setup request" message to gNB-CU 405. At 432, gNB-CU 405 transmits a "request" message (i.e., a third message) to gNB-CU 403. The "request" message may include an identifier of the remote UE 407 (e.g., a local identifier assigned by the gNB-CU 403), an identifier of the relay UE 409, a remote UE 407 context (e.g., qoS for DRB or SRB), and so on. Further, at 433, gNB-CU 403 prepares PC5 and/or Uu RLC channels for DRB/SRB. At 434, gNB-CU 403 transmits a "response" message (i.e., a fourth message) to gNB-CU 405. The quench response may include an identifier of the remote UE 407, an identifier of the relay UE 409, uu RLC channel information, and/or PC5 RLC channel message. Then, at 435-445, the process 400 continues with the subsequent access procedure.

All of the operations and features described above with reference to fig. 2-3 are equally applicable to process 400 and have similar effects. Details will be omitted for simplicity.

Fig. 5 illustrates a flowchart of an example method 500 according to some example embodiments of the present disclosure. The method 500 may be implemented at a first network device 210 as shown in fig. 2. For discussion purposes, the method 500 will be described with reference to fig. 2.

At block 510, the first network device 210 receives a first message from the first terminal device 240, or from the third network device 230, via the second terminal device 250, the first message including information for determining a target network device of the first terminal device. At block 520, the first network device 210 determines, based on the first message, that the target network device of the first terminal device 240 is the second network device 220. At block 530, the first network device 210 transmits a second message to the second network device 220 indicating that the first terminal device 240 is intended to communicate with the second network device 220 via the second terminal device 250 and the first network device 210.

In some example embodiments, the first network device 210 may receive a configuration of at least one communication channel between the first network device 210 and the second terminal device 250 and/or a configuration of at least one communication channel between the first terminal device 240 and the second terminal device 250 from the third network device 230.

In some example embodiments, the second message may include at least one of: an identifier of the first terminal device 240; an identifier of the second terminal device 250; an identifier of the first network device 210; or an identifier of the third network device 230, the identifier of the first terminal device 240 being assigned by the third network device 230.

In some example embodiments, the first terminal device 240 may be a remote terminal device and the second terminal device 250 may be a relay terminal device and the first network device 210 may be a distributed unit and the second network device 220 may be a first centralized unit and the third network device 230 may be a second centralized unit and the third network device controls the second terminal device.

Those skilled in the art will appreciate that all of the operations and features described above with reference to fig. 2-4 are equally applicable to the method 500 and have similar effects.

Fig. 6 illustrates a flowchart of an example method 600 according to some example embodiments of the present disclosure. The method 600 may be implemented at the second network device 220 as shown in fig. 2. For discussion purposes, the method 600 will be described with reference to fig. 2.

At block 610, the second network device 220 receives a second message from the first network device 210 indicating that the first terminal device 240 is intended to communicate with the second network device 220 via the second terminal device 250 and the first network device 210. At block 620, the second network device 220 transmits a third message to the third network device 230 requesting configuration of at least one communication channel between the first network device 210 and the second terminal device 250 and/or at least one communication channel between the first terminal device 240 and the second terminal device 250. At block 630, the second network device 220 receives a fourth message from the third network device 230, the fourth message comprising information for configuring at least one communication channel between the first network device 210 and the second terminal device 250 and/or at least one communication channel between the first terminal device 240 and the second terminal device 250. At block 640, the second network device 220 transmits a fifth message towards the first terminal device 240, the fifth message being used to configure at least one communication channel between the first terminal device 240 and the second terminal device 250.

In some example embodiments, the third message may include at least one of: an identifier of the first terminal device 240; an identifier of the second terminal device 250; an identifier of the first network device 210; or the context of the first terminal device 240.

In some example embodiments, the context of the first terminal device may include at least one of: an identifier of the data radio bearer of the first terminal device 240; quality of service of the data radio bearer of the first terminal device 240; or side link capability information of the first terminal device 240.

In some example embodiments, the context of the first terminal device 240 may include at least one of: an identifier of the signaling radio bearer of the first terminal device 240; quality of service of the signaling radio bearer of the first terminal device 240; or side link capability information of the first terminal device 240.

In some example embodiments, the fourth message may include at least one of: an identifier of the first terminal device 240; an identifier of the second terminal device 250; information associated with at least one communication channel between the first network device 210 and the second terminal device 250; or information associated with at least one communication channel between the first terminal device 240 and the second terminal device 250.

Those skilled in the art will appreciate that all of the operations and features described above with reference to fig. 2-4 are equally applicable to the method 600 and have similar effects.

Fig. 7 illustrates a flowchart of an example method 700 according to some example embodiments of the present disclosure. The method 700 may be implemented at the third network device 230 as shown in fig. 2. For discussion purposes, the method 700 will be described with reference to fig. 2.

At block 710, the third network device 230 receives a third message from the second network device 220 requesting configuration of at least one communication channel between the first network device 210 and the second terminal device 250 and/or at least one communication channel between the first terminal device 240 and the second terminal device 250 for communication between the second network device 220 and the first terminal device 240 via the first network device 210 and the second terminal device 250. At block 720, the third network device 230 configures at least one communication channel between the first network device 210 and the second terminal device 250 and/or at least one communication channel between the first terminal device 240 and the second terminal device 250 based on the third message. At block 730, the third network device 230 transmits a fourth message to the second network device 220, the fourth message including information for configuring at least one communication channel between the first network device 210 and the second terminal device 250 and/or at least one communication channel between the first terminal device 240 and the second terminal device 250.

In some example embodiments, the third network device 230 may determine a configuration of at least one communication channel between the first network device 210 and the second terminal device 250 and/or a configuration of at least one communication channel between the first terminal device 240 and the second terminal device 250 based on the third message. The third network device 230 may transmit to the first network device 210 a configuration of at least one communication channel between the first network device 210 and the second terminal device 250 and/or a configuration of at least one communication channel between the first terminal device 240 and the second terminal device 250.

In some example embodiments, the context of the first terminal device includes at least one of: an identifier of the data radio bearer of the first terminal device 240; quality of service of the data radio bearer of the first terminal device 240; or side link capability information of the first terminal device 240.

In some example embodiments, the context of the first terminal device may include at least one of: an identifier of the signaling radio bearer of the first terminal device 240; quality of service of the signaling radio bearer of the first terminal device 240; or side link capability information of the first terminal device 240.

Those skilled in the art will appreciate that all of the operations and features described above with reference to fig. 2-4 are equally applicable to the method 700 and have similar effects.

Fig. 8 is a simplified block diagram of a device 800 suitable for implementing example embodiments of the present disclosure. The device 800 may be implemented at or as part of the first network device 210, the second network device 220, or the third network device 230 as shown in fig. 2.

As shown, device 800 includes a processor 810, a memory 820 coupled to processor 810, a communication module 830 coupled to processor 810, and a communication interface (not shown) coupled to communication module 830. Memory 820 stores at least program 840. The communication module 830 is used for bi-directional communication via multiple antennas, for example. The communication interface may represent any interface necessary for communication.

Assume that program 840 includes program instructions that, when executed by associated processor 810, enable device 800 to operate in accordance with example embodiments of the present disclosure, as discussed herein with reference to fig. 2-7. The example embodiments herein may be implemented by computer software executable by the processor 810 of the device 800, or by hardware, or by a combination of software and hardware. The processor 810 may be configured to implement various example embodiments of the present disclosure.

Memory 820 may be of any type suitable to the local technical network and may be implemented using any suitable data storage technology, such as non-transitory computer-readable storage media, semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and removable memory, as non-limiting examples. Although only one memory 820 is shown in device 800, there may be multiple physically distinct memory modules within device 800. The processor 810 may be of any type suitable to the local technology network and may include 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, as non-limiting examples. The device 800 may have multiple processors, such as an application specific integrated circuit chip that is temporally subject to a clock that synchronizes the main processor.

When device 800 is acting as first network device 210 or as part of first network device 210, processor 810 and communication module 830 may cooperate to implement method 500 as described above with reference to fig. 5. When the device 800 is acting as the second network device 220 or as part of the second network device 220, the processor 810 and the communication module 830 may cooperate to implement the method 600 as described above with reference to fig. 6. When device 800 is acting as third network device 230 or as part of third network device 230, processor 810 and communication module 830 may cooperate to implement method 700 as described above with reference to fig. 7. All of the operations and features described above with reference to fig. 2-7 are equally applicable to the device 800 and have similar effects. Details will be omitted for simplicity.

In general, the various example embodiments of the disclosure may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device. While various aspects of the example embodiments of the present disclosure are shown and described as block diagrams, flowcharts, or using some other illustration, it is to be understood that the blocks, apparatus, systems, techniques, or methods described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.

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 instructions that are executed in a device on a target real or virtual processor to perform the method 500, 600, or 700 as described above with reference to fig. 5-7. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, etc. that perform particular tasks or implement particular abstract data types. In various example embodiments, the functionality of the program modules may be combined or split between program modules as desired. Machine-executable instructions for program modules may be executed within local or distributed devices. In a distributed device, program modules may be located in both local and remote memory storage media.

Program code for carrying out the methods of the present disclosure may be written in any combination of one or more programming languages. These program code may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus such that the program code, when executed by the processor or controller, causes the functions/operations specified in the flowchart and/or block diagram to be implemented. The program code may execute entirely on the machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote computer or server.

In the context of this disclosure, computer program code or related data may be carried by any suitable carrier to enable an apparatus, device, or processor to perform the various processes and operations described above. Examples of carrier waves include signals, computer readable media.

The computer readable medium may be a computer readable signal medium or a computer readable storage medium. The computer readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a computer-readable storage medium would include an electrical connection having one or more wires, a portable computer diskette, 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 disc read-only memory (CD-ROM), a Digital Versatile Disc (DVD), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

Moreover, although operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In some cases, multitasking and parallel processing may be advantageous. Also, while several specific implementation details are included in the above discussion, these details should not be construed as limiting the scope of the disclosure, but rather as descriptions of features that may be specific to particular example embodiments. Certain features that are described in the context of separate example embodiments may also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple exemplary embodiments separately or in any suitable subcombination.

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

Various example embodiments of these techniques have been described. In addition to or instead of the above, the following examples are described. Features described in any of the examples below may be used with any of the other examples described herein.

In some aspects, a method comprises: at the first network device, receiving a first message from the first terminal device via the second terminal device, or from the third network device, the first message comprising information for determining a target network device of the first terminal device; determining, based on the first message, that the target network device of the first terminal device is a second network device; and transmitting a second message to the second network device, the second message indicating that the first terminal device intends to communicate with the second network device via the second terminal device and the first network device.

In some example embodiments, the first message is received from a first terminal device and the information includes information about a public land mobile network of the first terminal device.

In some example embodiments, the first message is received from a third network device, and the information includes information indicating that the third network device has failed to be used for the first terminal device.

In some example embodiments, the method further comprises: the configuration of the at least one communication channel between the first network device and the second terminal device and/or the configuration of the at least one communication channel between the first terminal device and the second terminal device is received from the third network device.

In some example embodiments, the second message includes at least one of: an identifier of the first terminal device; an identifier of the second terminal device; an identifier of the first network device; or an identifier of the third network device, the identifier of the first terminal device being assigned by the third network device.

In some example embodiments, the first terminal device is a remote terminal device and the second terminal device is a relay terminal device and the first network device is a distributed unit and the second network device is a first centralized unit and the third network device is a second centralized unit and the third network device controls the second terminal device.

In some aspects, a method comprises: at the second network device, receiving a second message from the first network device, the second message indicating that the first terminal device intends to communicate with the second network device via the second terminal device and the first network device; transmitting a third message to the third network device, the third message requesting configuration of at least one communication channel between the first network device and the second terminal device and/or at least one communication channel between the first terminal device and the second terminal device; receiving a fourth message from the third network device, the fourth message comprising information for configuring at least one communication channel between the first network device and the second terminal device and/or at least one communication channel between the first terminal device and the second terminal device; and transmitting a fifth message towards the first terminal device, the fifth message being for configuring at least one communication channel between the first terminal device and the second terminal device.

In some example embodiments, the third message includes at least one of: an identifier of the first terminal device; an identifier of the second terminal device; an identifier of the first network device; or the context of the first terminal device.

In some example embodiments, the context of the first terminal device includes at least one of: an identifier of a data radio bearer or an identifier of a signaling radio bearer of the first terminal device; the quality of service of the data radio bearer or the signaling radio bearer of the first terminal device; or side link capability information of the first terminal device.

In some example embodiments, the fourth message includes at least one of: an identifier of the first terminal device; an identifier of the second terminal device; information associated with at least one communication channel between the first network device and the second terminal device; or information associated with at least one communication channel between the first terminal device and the second terminal device.

In some aspects, a method comprises: at the third network device, receiving a third message from the second network device requesting configuration of at least one communication channel between the first network device and the second terminal device and/or at least one communication channel between the first terminal device and the second terminal device for communication between the second network device and the first terminal device via the first network device and the second terminal device; configuring at least one communication channel between the first network device and the second terminal device and/or at least one communication channel between the first terminal device and the second terminal device based on the third message; and transmitting a fourth message to the second network device, the fourth message comprising information for configuring at least one communication channel between the first network device and the second terminal device and/or at least one communication channel between the first terminal device and the second terminal device.

In some example embodiments, configuring at least one communication channel between the first network device and the second terminal device and/or at least one communication channel between the first terminal device and the second terminal device comprises: determining a configuration of at least one communication channel between the first network device and the second terminal device and/or a configuration of at least one communication channel between the first terminal device and the second terminal device based on the third message; and transmitting to the first network device a configuration of at least one communication channel between the first network device and the second terminal device and/or a configuration of at least one communication channel between the first terminal device and the second terminal device.

In some aspects, a first network device comprises: at least one processor; 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 first network device to receive a first message from the first terminal device via the second terminal device, or from the third network device, the first message comprising information for determining a target network device of the first terminal device; determining, based on the first message, that the target network device of the first terminal device is a second network device; and transmitting a second message to the second network device, the second message indicating that the first terminal device intends to communicate with the second network device via the second terminal device and the first network device.

In some example embodiments, the at least one memory and the computer program code are configured to, with the at least one processor, cause the first network device to: the configuration of the at least one communication channel between the first network device and the second terminal device and/or the configuration of the at least one communication channel between the first terminal device and the second terminal device is received from the third network device.

In some aspects, a second network device comprises: at least one processor; 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 second network device to receive a second message from the first network device, the second message indicating that the first terminal device intends to communicate with the second network device via the second terminal device and the first network device; transmitting a third message to the third network device, the third message requesting configuration of at least one communication channel between the first network device and the second terminal device and/or at least one communication channel between the first terminal device and the second terminal device; receiving a fourth message from the third network device, the fourth message comprising information for configuring at least one communication channel between the first network device and the second terminal device and/or at least one communication channel between the first terminal device and the second terminal device; and transmitting a fifth message towards the first terminal device, the fifth message being for configuring at least one communication channel between the first terminal device and the second terminal device.

In some aspects, a third network device comprises: at least one processor; 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 third network device to: receiving a third message from the second network device requesting configuration of at least one communication channel between the first network device and the second terminal device and/or at least one communication channel between the first terminal device and the second terminal device for communication between the second network device and the first terminal device via the first network device and the second terminal device; configuring at least one communication channel between the first network device and the second terminal device and/or at least one communication channel between the first terminal device and the second terminal device based on the third message; and transmitting a fourth message to the second network device, the fourth message comprising information for configuring at least one communication channel between the first network device and the second terminal device and/or at least one communication channel between the first terminal device and the second terminal device.

In some example embodiments, when configuring at least one communication channel between the first network device and the second terminal device and/or at least one communication channel between the first terminal device and the second terminal device, the at least one memory and the computer program code are configured to, with the at least one processor, cause the third network device to determine a configuration of the at least one communication channel between the first network device and the second terminal device and/or a configuration of the at least one communication channel between the first terminal device and the second terminal device based on the third message; and transmitting to the first network device a configuration of at least one communication channel between the first network device and the second terminal device and/or a configuration of at least one communication channel between the first terminal device and the second terminal device.

In some aspects, an apparatus comprises: means for receiving a first message from the first terminal device via the second terminal device, or from the third network device, the first message comprising information for determining a target network device of the first terminal device; means for determining, based on the first message, that the target network device of the first terminal device is the second network device; and means for transmitting a second message to the second network device, the second message indicating that the first terminal device is intended to communicate with the second network device via the second terminal device and the first network device.

In some example embodiments, the apparatus further comprises: means for receiving from the third network device a configuration of at least one communication channel between the first network device and the second terminal device and/or a configuration of at least one communication channel between the first terminal device and the second terminal device.

In some aspects, an apparatus comprises: means for receiving a second message from the first network device, the second message indicating that the first terminal device intends to communicate with the second network device via the second terminal device and the first network device; means for transmitting a third message to the third network device requesting configuration of at least one communication channel between the first network device and the second terminal device and/or at least one communication channel between the first terminal device and the second terminal device; means for receiving a fourth message from the third network device, the fourth message comprising information for configuring at least one communication channel between the first network device and the second terminal device and/or at least one communication channel between the first terminal device and the second terminal device; and means for transmitting a fifth message towards the first terminal device, the fifth message being for configuring at least one communication channel between the first terminal device and the second terminal device.

In some aspects, an apparatus comprises: means for receiving a third message from the second network device requesting configuration of at least one communication channel between the first network device and the second terminal device and/or at least one communication channel between the first terminal device and the second terminal device for communication between the second network device and the first terminal device via the first network device and the second terminal device; means for configuring at least one communication channel between the first network device and the second terminal device and/or at least one communication channel between the first terminal device and the second terminal device based on the third message; and means for transmitting a fourth message to the second network device, the fourth message comprising information for configuring at least one communication channel between the first network device and the second terminal device and/or at least one communication channel between the first terminal device and the second terminal device.

In some example embodiments, the means for configuring at least one communication channel between the first network device and the second terminal device and/or at least one communication channel between the first terminal device and the second terminal device comprises: means for determining a configuration of at least one communication channel between the first network device and the second terminal device and/or a configuration of at least one communication channel between the first terminal device and the second terminal device based on the third message; and means for transmitting to the first network device a configuration of at least one communication channel between the first network device and the second terminal device and/or a configuration of at least one communication channel between the first terminal device and the second terminal device.

In some aspects, a computer-readable storage medium includes program instructions stored thereon that, when executed by a processor of a device, cause the device to perform a method according to some example embodiments of the present disclosure.

Claims

1. A first network device for communication, comprising:

means for receiving a first message from a first terminal device via a second terminal device, or from a third network device, the first message comprising information for determining a target network device of the first terminal device;

Means for determining, based on the first message, that the target network device of the first terminal device is a second network device; and

means for transmitting a second message to the second network device, the second message indicating that the first terminal device is intended to communicate with the second network device via the second terminal device and the first network device.

2. The first network device of claim 1, wherein the first message is received from the first terminal device, and wherein the information comprises information about a public land mobile network of the first terminal device.

3. The first network device of claim 1, wherein the first message is received from the third network device, and wherein the information comprises information indicating that the third network device failed to be used for the first terminal device.

4. The first network device of claim 1, further comprising:

means for receiving from the third network device a configuration of at least one communication channel between the first network device and the second terminal device, and/or a configuration of at least one communication channel between the first terminal device and the second terminal device.

5. The first network device of claim 1, wherein the second message comprises at least one of:

an identifier of the first terminal device;

an identifier of the second terminal device;

an identifier of the first network device; or alternatively

An identifier of the third network device, the identifier of the first terminal device being assigned by the third network device.

6. The first network device of any of claims 1-5, wherein the first terminal device is a remote terminal device and the second terminal device is a relay terminal device and the first network device is a distributed unit and the second network device is a first centralized unit and the third network device is a second centralized unit and the third network device controls the second terminal device.

7. A second network device for communication, comprising:

means for receiving a second message from a first network device, the second message indicating that a first terminal device intends to communicate with the second network device via a second terminal device and the first network device;

means for transmitting a third message to a third network device, the third message requesting configuration of at least one communication channel between the first network device and the second terminal device, and/or at least one communication channel between the first terminal device and the second terminal device;

Means for receiving a fourth message from the third network device, the fourth message comprising information for configuring the at least one communication channel between the first network device and the second terminal device, and/or the at least one communication channel between the first terminal device and the second terminal device; and

means for transmitting a fifth message towards the first terminal device, the fifth message being for configuring the at least one communication channel between the first terminal device and the second terminal device.

8. The second network device of claim 7, wherein the second message comprises at least one of:

an identifier of the first terminal device;

an identifier of the second terminal device;

an identifier of the first network device; or alternatively

9. The second network device of claim 7, wherein the third message comprises at least one of:

an identifier of the first terminal device;

an identifier of the second terminal device;

An identifier of the first network device; or alternatively

The context of the first terminal device.

10. The second network device of claim 9, wherein the context of the first terminal device comprises at least one of:

an identifier of a data radio bearer or an identifier of a signaling radio bearer of the first terminal device;

the quality of service of the data radio bearer or the signaling radio bearer of the first terminal device; or alternatively

And the side link capacity information of the first terminal equipment.

11. The second network device of claim 7, wherein the fourth message comprises at least one of:

an identifier of the first terminal device;

an identifier of the second terminal device;

information associated with the at least one communication channel between the first network device and the second terminal device; or alternatively

Information associated with the at least one communication channel between the first terminal device and the second terminal device.

12. The second network device according to any of claims 7 to 11, wherein the first terminal device is a remote terminal device and the second terminal device is a relay terminal device and the first network device is a distributed unit and the second network device is a first centralized unit and the third network device is a second centralized unit and the third network device controls the second terminal device.

13. A third network device for communication, comprising:

means for receiving a third message from a second network device, the third message requesting configuration of at least one communication channel between a first network device and a second terminal device, and/or at least one communication channel between a first terminal device and the second terminal device, for communication between the second network device and the first terminal device via the first network device and the second terminal device;

means for configuring the at least one communication channel between the first network device and the second terminal device, and/or the at least one communication channel between the first terminal device and the second terminal device, based on the third message; and

means for transmitting a fourth message to the second network device, the fourth message comprising information for configuring the at least one communication channel between the first network device and the second terminal device, and/or the at least one communication channel between the first terminal device and the second terminal device.

14. The third network device of claim 13, wherein the means for configuring comprises:

Means for determining a configuration of the at least one communication channel between the first network device and the second terminal device and/or a configuration of the at least one communication channel between the first terminal device and the second terminal device based on the third message; and

means for transmitting to the first network device the configuration of the at least one communication channel between the first network device and the second terminal device, and/or the configuration of the at least one communication channel between the first terminal device and the second terminal device.

15. The third network device of claim 13, wherein the third message comprises at least one of:

an identifier of the first terminal device;

an identifier of the second terminal device;

an identifier of the first network device; or alternatively

The context of the first terminal device.

16. The third network device of claim 15, wherein the context of the first terminal device comprises at least one of:

And the side link capacity information of the first terminal equipment.

17. The third network device of claim 13, wherein the fourth message comprises at least one of:

an identifier of the first terminal device;

an identifier of the second terminal device;

18. The third network device of any of claims 13-17, wherein the first terminal device is a remote terminal device and the second terminal device is a relay terminal device and the first network device is a distributed unit and the second network device is a first centralized unit and the third network device is a second centralized unit and the third network device controls the second terminal device.

19. A method for communication, comprising:

At the first network device,

receiving, via the second terminal device, a first message from the first terminal device, or from a third network device, the first message comprising information for determining a target network device of the first terminal device;

determining, based on the first message, that the target network device of the first terminal device is a second network device; and

transmitting a second message to the second network device, the second message indicating that the first terminal device is intended to communicate with the second network device via the second terminal device and the first network device.

20. The method of claim 19, wherein the first message is received from the first terminal device, and wherein the information comprises information about a public land mobile network of the first terminal device.

21. The method of claim 19, wherein the first message is received from the third network device, and wherein the information comprises information indicating that the third network device failed to be used for the first terminal device.

22. The method of claim 19, further comprising:

a configuration of at least one communication channel between the first network device and the second terminal device, and/or a configuration of at least one communication channel between the first terminal device and the second terminal device, is received from the third network device.

23. The method of claim 19, wherein the second message comprises at least one of:

an identifier of the first terminal device;

an identifier of the second terminal device;

an identifier of the first network device; or alternatively

24. The method of any of claims 19 to 23, wherein the first terminal device is a remote terminal device and the second terminal device is a relay terminal device and the first network device is a distributed unit and the second network device is a first centralized unit and the third network device is a second centralized unit and the third network device controls the second terminal device.

25. A method for communication, comprising:

at the location of the second network device,

receiving a second message from the first network device, the second message indicating that the first terminal device intends to communicate with the second network device via the second terminal device and the first network device;

transmitting a third message to a third network device, the third message requesting configuration of at least one communication channel between the first network device and the second terminal device, and/or at least one communication channel between the first terminal device and the second terminal device;

Receiving a fourth message from the third network device, the fourth message comprising information for configuring the at least one communication channel between the first network device and the second terminal device, and/or the at least one communication channel between the first terminal device and the second terminal device; and

transmitting a fifth message towards the first terminal device, the fifth message being used to configure the at least one communication channel between the first terminal device and the second terminal device.

26. The method of claim 25, wherein the second message comprises at least one of:

an identifier of the first terminal device;

an identifier of the second terminal device;

an identifier of the first network device; or alternatively

27. The method of claim 25, wherein the third message comprises at least one of:

an identifier of the first terminal device;

an identifier of the second terminal device;

an identifier of the first network device; or alternatively

The context of the first terminal device.

28. The method of claim 27, wherein the context of the first terminal device comprises at least one of:

And the side link capacity information of the first terminal equipment.

29. The method of claim 25, wherein the fourth message comprises at least one of:

an identifier of the first terminal device;

an identifier of the second terminal device;

30. The method of any of claims 25 to 29, wherein the first terminal device is a remote terminal device and the second terminal device is a relay terminal device and the first network device is a distributed unit and the second network device is a first centralized unit and the third network device is a second centralized unit and the third network device controls the second terminal device.

31. A method for communication, comprising:

at the third network device,

receiving a third message from a second network device, the third message requesting configuration of at least one communication channel between a first network device and a second terminal device, and/or at least one communication channel between a first terminal device and the second terminal device, for communication between the second network device and the first terminal device via the first network device and the second terminal device;

configuring the at least one communication channel between the first network device and the second terminal device, and/or the at least one communication channel between the first terminal device and the second terminal device, based on the third message; and

transmitting a fourth message to the second network device, the fourth message comprising information for configuring the at least one communication channel between the first network device and the second terminal device, and/or the at least one communication channel between the first terminal device and the second terminal device.

32. The method of claim 31, wherein configuring the at least one communication channel between the first network device and the second terminal device, and/or the at least one communication channel between the first terminal device and the second terminal device, comprises:

Determining a configuration of the at least one communication channel between the first network device and the second terminal device and/or a configuration of the at least one communication channel between the first terminal device and the second terminal device based on the third message; and

transmitting the configuration of the at least one communication channel between the first network device and the second terminal device and/or the configuration of the at least one communication channel between the first terminal device and the second terminal device to the first network device.

33. The method of claim 31, wherein the third message comprises at least one of:

an identifier of the first terminal device;

an identifier of the second terminal device;

an identifier of the first network device; or alternatively

The context of the first terminal device.

34. The method of claim 33, wherein the context of the first terminal device comprises at least one of:

And the side link capacity information of the first terminal equipment.

35. The method of claim 31, wherein the fourth message comprises at least one of:

an identifier of the first terminal device;

an identifier of the second terminal device;

36. The method of any of claims 31 to 35, wherein the first terminal device is a remote terminal device and the second terminal device is a relay terminal device and the first network device is a distributed unit and the second network device is a first centralized unit and the third network device is a second centralized unit and the third network device controls the second terminal device.

37. An apparatus for communication, comprising:

at least one processor; and

at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to:

38. An apparatus for communication, comprising:

at least one processor; and

39. An apparatus for communication, comprising:

at least one processor; and

40. A computer readable medium for communication, comprising program instructions which, when executed by an apparatus, cause the apparatus to at least:

at the first network device,

41. A computer readable medium for communication, comprising program instructions which, when executed by an apparatus, cause the apparatus to at least:

at the location of the second network device,

42. A computer readable medium for communication, comprising program instructions which, when executed by an apparatus, cause the apparatus to at least:

at the third network device,