Fast indirect path establishment for sidelink user equipment to network relay

Abstract

Systems, methods, apparatuses, and computer program products are provided for establishing an indirect path as an additional path if a relay user equipment may be in an idle or inactive state, such as a radio resource control idle / inactive state. For example, a method may include receiving a configuration of a relay user equipment container from a network element, the relay user equipment container relating to addition or modification of an indirect path between a user equipment and the network element. The method may also include indicating the relay user equipment container to the relay user equipment.

Description

Technical Field

[0001] Some example embodiments may generally relate to communications including mobile or wireless telecommunications systems, such as Long Term Evolution (LTE) or fifth generation (5G) radio access technology or new radio (NR) access technology, or other communications systems including subsequent generations of the same or similar standards. For example, certain example embodiments may generally relate to establishing an indirect path as an additional path in situations where a relay user equipment may be in an idle or inactive state, such as a radio resource control idle / inactive state. Background Art

[0002] Examples of mobile or wireless telecommunication systems may include Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UTRAN), Long Term Evolution (LTE) Evolved UTRAN (E-UTRAN), LTE Advanced (LTE-A), MulteFire, LTE-A Pro, and / or fifth generation (5G) radio access technology or new radio (NR) access technology. 5G wireless systems refer to next generation (NG) radio systems and network architectures. 5G systems are mostly built on 5G New Radio (NR), but 5G (or NG) networks can also be built on E-UTRA radio. Starting with Release 18 (Rel-18), 5G is referred to as 5G Advanced. It is estimated that NR provides bit rates of about 10-20Gbit / s or higher, and can support at least service categories such as enhanced mobile broadband (eMBB) and ultra-reliable low latency communication (URLLC) and massive machine type communication (mMTC). NR is expected to deliver extremely wide bandwidth and ultra-robust, low latency connectivity and large-scale networking to support the Internet of Things (IoT). As IoT and machine-to-machine (M2M) communications become more widespread, the demand for networks that meet the needs of lower power consumption, low data rates and long battery life will continue to grow. The next generation radio access network (NG-RAN) represents a RAN for 5G that is capable of providing both NR and LTE (and LTE Advanced) radio access. Note that in 5G, a node that can provide radio access functions to user equipment (i.e., similar to a Node B, NB in ​​UTRAN or an evolved NB, eNB in ​​LTE) can be named a next generation NB (gNB) when established on an NR radio, and the node can be named a next generation eNB (NG-eNB) when established on an E-UTRA radio. 6G is currently under development and may replace 5G and 5G Advanced. Summary of the invention

[0003] Embodiments may be directed to an apparatus. The apparatus may include at least one processor and at least one memory storing instructions. The instructions, when executed by the at least one processor, may cause the apparatus to at least perform receiving a configuration of a relay user equipment container from a network element, the relay user equipment container being related to adding or modifying an indirect path between the apparatus and the network element. The instructions, when executed by the at least one processor, may also cause the apparatus to at least perform indicating the relay user equipment container to the relay user equipment.

[0004] Embodiments may relate to an apparatus. The apparatus may include at least one processor and at least one memory storing instructions. When the instructions are executed by the at least one processor, the apparatus may at least perform receiving a relay user equipment container from a remote user equipment. When the instructions are executed by the at least one processor, the apparatus may also at least perform connecting to a network element based on the relay user equipment container to provide an indirect path for the remote user equipment.

[0005] Embodiments may be directed to an apparatus. The apparatus may include at least one processor and at least one memory storing instructions. The instructions, when executed by the at least one processor, may cause the apparatus to at least configure a remote user device using a relay user device container, the relay user device container being associated with adding or modifying an indirect path between the remote user device and the apparatus. The instructions, when executed by the at least one processor, may also cause the apparatus to at least receive a confirmation of a transfer of the relay user device container to the relay user device.

[0006] Embodiments may be directed to a method. The method may include receiving, at a user equipment, from a network element, a configuration of a relay user equipment container, the relay user equipment container being associated with adding or modifying an indirect path between the user equipment and the network element. The method may also include indicating the relay user equipment container to the relay user equipment.

[0007] Embodiments may be directed to a method. The method may include receiving, at a user equipment, a relay user equipment container from a remote user equipment. The method may also include connecting to a network element to provide an indirect path for the remote user equipment based on the relay user equipment container.

[0008] Embodiments may be directed to a method. The method may include configuring a remote user equipment with a relay user equipment container, the relay user equipment container being associated with adding or modifying an indirect path between the remote user equipment and a network element. The method may also include receiving confirmation of delivery of the relay user equipment container to the relay user equipment.

[0009] Embodiments may be directed to an apparatus. The apparatus may include: a component for receiving a configuration of a relay user equipment container from a network element, the relay user equipment container being related to adding or modifying an indirect path between the apparatus and the network element. The apparatus may also include a component for indicating the relay user equipment container to the relay user equipment.

[0010] Embodiments may be directed to an apparatus. The apparatus may include a component for receiving a relay user equipment container from a remote user equipment. The apparatus may also include a component for providing an indirect path for the remote user equipment based on the relay user equipment container and connecting to a network element.

[0011] Embodiments may be directed to an apparatus. The apparatus may include means for configuring a remote user equipment with a relay user equipment container, the relay user equipment container being associated with adding or modifying an indirect path between the remote user equipment and the apparatus. The apparatus may also include means for receiving confirmation of delivery of the relay user equipment container to the relay user equipment. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] For a proper understanding of the example embodiments, reference should be made to the accompanying drawings, in which:

[0013] Figure 1 The target multipath to the remote user equipment is shown;

[0014] Figure 2 shows a signaling flow of a method according to some embodiments;

[0015] Figure 3 A radio resource control setup message is shown; and

[0016] Figure 4 An example block diagram of a system according to an embodiment is shown. DETAILED DESCRIPTION

[0017] It will be readily appreciated that the components of certain example embodiments as generally described and illustrated in the figures herein may be arranged and designed in a variety of different configurations. Therefore, the following detailed description of some example embodiments of systems, methods, apparatuses, and computer program products for establishing an indirect path as an additional path when relay user equipment may be in an idle or inactive state (such as a radio resource control idle / inactive state) is not intended to limit the scope of certain embodiments, but rather represents selected example embodiments.

[0018] The features, structures, or characteristics of the example embodiments described throughout this specification may be combined in any suitable manner in one or more example embodiments. For example, the phrases "certain embodiments," "some embodiments," or other similar language used throughout this specification refer to the fact that a particular feature, structure, or characteristic described in conjunction with an embodiment may be included in at least one embodiment. Therefore, the phrases "certain embodiments," "in some embodiments," "in other embodiments," or other similar language appearing throughout this specification do not necessarily all refer to the same set of embodiments, and the described features, structures, or characteristics may be combined in any suitable manner in one or more example embodiments.

[0019] Certain embodiments may have various aspects and features. These aspects and features may be applied individually or in any desired combination with each other. Other features, processes and elements may also be applied in combination with some or all of the aspects and features disclosed herein.

[0020] Additionally, if desired, the different functions or processes discussed below may be performed in different orders and / or performed simultaneously with each other. In addition, if desired, one or more of the described functions or processes may be optional or may be combined. Therefore, the following description should be considered as an explanation of the principles and teachings of some example embodiments, rather than a limitation thereof.

[0021] Certain embodiments relate to support of multipath (MP) for a user equipment (UE), in which one path uses a second layer (L2) UE-to-network (U2N) relay based on a new radio (NR) sidelink (SL), also referred to as an indirect path, and the other path uses direct Uu access, also referred to as a direct path. Multipath with U2N relaying or UE aggregation has the potential to improve the throughput and reliability or robustness of communications, for example, for UEs at the edge of a cell and UEs with limited uplink (UL) transmission power. In wireless communications, the use of the term multipath also refers to the condition where a signal propagates along a direct path from a transmitter to a receiver and along a second path due to, for example, reflections. MP for a UE may alternatively refer to an intentionally created situation in which there are different signals providing (multiple) communication links to the user equipment over different transmission paths. The present discussion focuses on MP for a UE rather than signal reflections and related signal interference / attenuation issues.

[0022] Figure 1The target multipath for the remote user equipment is shown. If the same mechanism of the network (NW) controlled SL U2N relay indirect path switching is used, the MP management can be under the control of the NW (e.g., next generation node (gNB)) for managing the MP, especially for L2-based U2N relay in the indirect path. MP management can include decisions about the establishment of MP, the selection of relay UEs for the indirect path, the configuration of the indirect path, etc.

[0023] Certain embodiments involve Figure 1 The scenario shown in Figure 1, where the UE has at least established a direct path with the serving gNB. In addition to the established direct path, the gNB may also determine to add a new path or modify an existing indirect path via the selected relay UE ( Figure 1 ), where the relay UE may be in an RRC idle or inactive state before an indirect path to the remote UE via the relay UE is established.

[0024] The gNB may identify that the direct path may not meet the throughput or reliability requirements of the service traffic of the remote UE, for example based on the gNB's own measurements and / or measurement reports from the remote UE. As a result, the serving gNB of the remote UE may determine to add or modify an indirect path via the selected relay UE. It may be beneficial to establish the indirect path as quickly as possible in order to maintain good quality of service (QoS) for the service to the remote UE.

[0025] Following one mechanism for indirect path handover via a relay UE in RRC idle / inactive state, when the serving gNB configures the remote UE for indirect path handover, the relay UE in RRC idle / inactive state can be triggered by the remote UE through sidelink (SL) or PC5 to establish the relay UE's own RRC connection with the serving gNB. The indirect path of the remote UE can be established using this example mechanism only after the relay UE enters the RRC connected state. For a direct connection between the UE and the serving gNB, the total RRC connection establishment process delay can be between 70ms and 80ms, and with the delay improvement feature described in the Third Generation Partnership Project (3GPP) Technical Specification (TS) 36.912, the delay can be 50ms.

[0026] Therefore, if the relay UE is in RRC idle / inactive state, the indirect path establishment in the MP scenario can be delayed by at least tens of milliseconds. This may be unacceptable when the remote UE service has a guaranteed bit rate or high reliability and low latency expectations.

[0027] Certain embodiments provide ways to establish an indirect path as a second path in a fast and efficient manner when the indirect path is configured via a relay UE in an RRC idle / inactive state.

[0028] Therefore, certain embodiments may leverage an existing direct path between a remote UE and a serving gNB to facilitate fast and efficient RRC connection establishment for (multiple) relay UEs in an RRC idle / inactive state when an indirect path is added or modified with a new relay UE.

[0029] The remote UE may be configured by a network element such as a gNB or any other access node. Specifically, the remote UE may be configured with a relay UE RRC connection configuration container, which may be referred to as a relay UE container. The relay UE container may provide RRC reconfiguration parameters related to the addition or modification of an indirect path.

[0030] The relay UE container may include configurations for the relay UE that would otherwise be included in the RRC setup message, such as, but not limited to, Uu signaling radio bearer 1 (SRB1) configuration, PC5 configuration for the SRB1 message, and an optional cell radio network temporary identifier (C-RNTI). The PC5 configuration may include sidelink relay adaptation protocol (SRAP), radio link control (RLC) channels, medium access control (MAC), and physical layer (PHY) configurations.

[0031] The relay UE container may also include uplink (UL) synchronization related configuration. For example, the configuration may include a dedicated RACH preamble for the relay UE to obtain fast UL synchronization with the serving gNB via a contention-free RACH procedure. Additionally or alternatively, the relay UE container may include timing advance (TA) information for RACH-free access, which may be determined by the serving gNB based on the TA information of the remote UE and measurement reports from the remote UE via PC5 between the remote UE and the relay UE. The relay UE container may also include more information, such as Uu SRB1 configuration, PC5 configuration of the SRB1 message (e.g., SRAP, RLC channel, MAC and PHY configuration), and optional C-RNTI. Other information may also be included in the relay UE container.

[0032] After receiving the MP add / modify configuration with the relay UE container, the remote UE can establish a PC5 connection with the relay UE and can indicate the relay UE container to the relay UE. After receiving the relay UE container, the relay UE can omit at least some of the conventional RRC connection establishment procedures. The following are some examples, and other procedures of the conventional RRC connection establishment procedure can also be considered and optionally omitted.

[0033] If the relay UE container from the serving gNB includes valid TA information or the remote UE indicates valid TA information to the relay UE, the relay UE may use the indicated TA for communication with the gNB over Uu and start monitoring the PDCCH over Uu to send a confirmation message to the gNB to immediately complete the RRC connection establishment procedure for the relay UE.

[0034] If the relay UE container from the serving gNB indicates a RACH preamble, the relay UE may initiate a RACH procedure using the RACH preamble and may send an acknowledgement message instead of an RRC establishment request in msg3 of the RACH procedure to complete the RRC connection establishment procedure for the relay UE.

[0035] Additionally, the remote UE may respond to the serving gNB with an RRC Reconfiguration Complete message. The message may indicate the transfer of the relay UE container to the relay UE. The indication of the transfer of the relay UE container may be particularly useful for the above-mentioned No RACH option. The indication may be used by the serving gNB to start scheduling the relay UE for acknowledgement message transmission in the UL.

[0036] Figure 2 A signaling flow of a method according to some embodiments is shown. Figure 2 An implementation example for fast and efficient indirect path establishment for multipathing is shown.

[0037] At process 205, the remote UE may have at least an established direct path with the serving gNB. At process 210, the gNB may configure the remote UE with a measurement configuration, which may include measurements of the relay UE over the PC5 interface. Based on the measurement configuration, at process 210, the remote UE may report Uu and PC5 measurement results, where the PC5 measurement results may include the ID of the discovered candidate relay UE, the serving cell ID, the PC5 measurement result, the location information of the remote UE (if available), etc.

[0038] Based on the measurement report from the remote UE, at 215, the serving gNB may make a decision to add or modify an indirect path via a relay UE selected for the remote UE. If the remote UE has only an established direct path with the serving gNB, then adding an indirect path for the remote UE may be applied. If the remote UE has both an established direct path and an established indirect path with the serving gNB, and the serving gNB decides to modify the indirect path with a relay reselection from the current relay UE or source relay UE to a newly selected relay UE or target relay UE, then modifying the indirect path for the remote UE may be applied. While it is possible to modify the characteristics of an indirect path with an existing relay UE without changing the new relay UE, in this case, the existing relay UE may already be connected to the serving gNB, and therefore techniques to accelerate connection establishment may not be necessary. However, if such accelerated connection establishment is desired, the same techniques as described herein may be applied.

[0039] Based on the ID of the relay UE reported by the remote UE, the serving gNB can identify that the (re)selected relay UE is not in the RRC connected state and therefore the relay UE needs to establish its own RRC connection with the serving gNB before the indirect path can be established.

[0040] In process 220, in order to facilitate fast and efficient indirect path establishment for the remote UE, the serving gNB may decide to include the RRC connection configuration of the relay UE in a relay UE container within an RRC reconfiguration message to be sent to the remote UE to configure the remote UE to add or modify the indirect path via the (re)selected relay UE, and provide the relay UE container to the relay UE via the PC5 interface.

[0041] In process 225, the remote UE may establish a PC5 connection to the selected relay UE if not already connected.Then, in process 230, the UE may transmit the configuration received in the container to the relay UE.

[0042] Figure 3 The radio resource control setup message is shown. Figure 2 The configuration information in the relay UE container provided in process 220 may include the following: Figure 3 Some, many, or all of the configuration parameters in the RRC setup message shown, as well as other configuration parameters.

[0043] In addition to configuration parameters such as those associated with the RRC setup message, the relay UE container may also include configuration parameters for UL synchronization for the relay UE. In one option, RACH configuration parameters (such as a dedicated RACH preamble) may be provided. The RACH configuration parameters may be used by the relay UE to initiate a RACH procedure for acquiring timing advance (TA) information from the gNB. For example, the relay may send a RACH preamble at 240 and receive a RACH response at 245.

[0044] As another option, the TA information may be provided by the gNB in ​​the relay container and the TA may be used by the relay UE for UL transmissions of the relay UE to the serving gNB. In this option, the gNB may provide the TA information based on the TA of the remote UE in the direct path and / or the location information of the relay UE and the remote UE if such information is available.

[0045] As yet another option, the serving gNB may not provide the RACH preamble or TA, but may instruct the remote UE to provide the relay UE with the remote UE's TA information.

[0046] Depending on whether the RACH configuration is provided in the relay UE container, the C-RNTI for the relay UE may or may not be provided in the relay UE container. For example, if the RACH configuration is provided, the relay UE may obtain the temporary C-RNTI assigned in the RACH response message, and if the RACH procedure is successful, the temporary C-RNTI may be upgraded to a normal C-RNTI. In this case, the C-RNTI does not need to be included in the relay UE's container. However, if the TA is configured in the relay UE container from the gNB, or the gNB instructs / requests the remote UE to provide the TA to the relay UE, the C-RNTI of the relay UE may be included in the relay UE container.

[0047] As an implementation option, the relay UE container may be provided by the serving gNB without indicating the (re)selected target relay UE. In this case, the remote UE may select a relay UE for the indirect path. As described below, the relay UE container received from the serving gNB may be indicated by the remote UE to the selected relay UE.

[0048] In addition to the relay UE container, the allocated PC5 resources (such as SL configured grants) may be provided by the gNB to the remote UE in an RRC reconfiguration message. Such indication of the allocated PC5 resources may facilitate faster and more reliable transmission of the remote UE's SL control signaling and data to the relay UE over the PC5 interface without the need for resource sensing and selection.

[0049] The configuration of SRB1 for Uu and PC5 in the RRC Setup message may not take into account the UE capabilities, since the UE capabilities may not be available in the serving gNB when the RRC Setup message is transmitted. In addition, the RRC Setup message may not be encrypted, since the security mode may not have been activated when the message is transmitted from the gNB to the remote UE. Therefore, there may be no UE capability mismatch issue or security issue in passing the RRC connection configuration parameters to the relay UE via the remote UE.

[0050] When the remote UE receives the RRC reconfiguration message for adding or modifying the indirect path, if the PC5 connection has not been established with the relay UE before, the remote UE may need to establish a PC5 connection with the indicated target relay UE for the indirect path. The remote UE can then forward the relay UE container to the relay UE via the PC5 connection.

[0051] In one option, the relay UE container may be forwarded to the relay UE during PC5 connection establishment. For example, the container may be integrated into the SL RRC reconfiguration message. In another option, a new SL RRC message may be introduced to forward the relay UE container to the relay UE.

[0052] If HARQ feedback is enabled for delivery of relay UE containers through PC5, the remote UE may determine delivery of the relay UE container to the relay UE based on hybrid automatic repeat request (HARQ) acknowledgement (ACK) feedback from the PHY / MAC layer. Alternatively, the remote UE may determine delivery of the relay UE container to the relay UE based on the SL RRC procedure. For example, an RRC confirmation message (which may be a SL RRC reconfiguration complete) may be used as a delivery confirmation from the relay UE.

[0053] In process 235, after determining the transfer of the relay UE container to the relay UE, the remote UE may respond to the serving gNB with an RRC reconfiguration complete message in which an indication of the transfer of the relay UE container to the relay UE is indicated. Based on the indication, the serving gNB may know that the relay UE received the RRC connection configuration and is therefore ready to perform the following actions.

[0054] In the case where the RACH configuration is included in the relay UE container, when the dedicated RACH preamble is provided at 240, the gNB can detect the dedicated RACH preamble and then schedule UL resources to the relay UE for RACH msg3 transmission to allow the relay UE to send an acknowledgement message to the gNB in ​​process 255 for RRC connection establishment or resumption when the relay UE is in an RRC inactive state.

[0055] In case the RACH configuration is not included in the relay UE container, the gNB may schedule UL resources to the relay UE after receiving a delivery indication from the remote UE. The UL resources may be used by the relay UE to send an acknowledgement message to the gNB for RRC connection establishment / recovery.

[0056] Accordingly, after receiving the relay UE container forwarded from the remote UE, the relay UE may initiate a RACH procedure if the RACH configuration is provided in the container, or detect the PDCCH for UL resource allocation using the C-RNTI included in the container to send a confirmation message for RRC connection establishment / recovery in process 250. The confirmation message may be a new RRC message or a reused RRC establishment complete message or RRC recovery complete message.

[0057] Upon receiving a candidate relay UE report from a remote UE, based on the ID of the relay UE, the serving gNB may only identify that the relay UE is not in an RRC connected state, but may not be able to distinguish whether the relay UE is in an RRC idle state or an RRC inactive state. Therefore, the relay UE container may only include configuration parameters similar to those in the RRC establishment message. It may not be possible to provide additional configurations, such as data radio bearer (DRB) configurations as in an RRC resume message. However, the relay UE may provide different information in the confirmation message based on the RRC state of the relay UE. For example, different UE IDs, such as the fifth generation temporary mobile subscriber identity (5G-TMSI) or an inactive radio network temporary identifier (I-RNTI), may be provided in confirmation messages for relay UEs in an RRC idle or RRC inactive state, respectively.

[0058] describe Figure 2 The implementation example is described for the scenario where the direct path and the indirect path are connected to the same serving gNB. The same mechanism can also be applied to the scenario where the direct path and the indirect path are connected to different gNBs. In this case, the gNB to which the indirect path is connected can provide the relay UE container to the gNB to which the direct path is connected via an inter-gNB interface (such as an Xn interface or an N2 interface).

[0059] Certain embodiments are described in a multipath scenario where the UE has at least a direct path to the gNB with or without a second profile path, and it is up to the gNB to add a second indirect path via a (re)selected relay UE or to modify the second indirect path (if the second indirect path exists) while the direct path is maintained. The method for fast establishment of an indirect path may also be applicable to a single path scenario where a path switch from direct to indirect is triggered, such that the remote UE receives a configuration or TA via the current path of the remote UE and transmits it to the target relay UE for fast path switching. Similarly, certain embodiments may also be applicable to adding a third path where a direct path and an indirect path already exist and are to be maintained.

[0060] Figure 4 An example of a system including an apparatus 10 according to an embodiment is shown. In an embodiment, the apparatus 10 may be a node, a host, or a server in a communication network or serving such a network. For example, the apparatus 10 may be a network node, a satellite, a base station, a Node B, an evolved Node B (eNB), a 5G Node B or access point associated with a radio access network (such as an LTE network, 5G or NR), a next generation Node B (NG-NB or gNB), a TRP, a HAPS, an integrated access and backhaul (IAB) node, and / or a WLAN access point. In some example embodiments, the apparatus 10 may be, for example, a gNB or other similar radio node.

[0061] It should be understood that in some example embodiments, the device 10 may include an edge cloud server as a distributed computing system, where the server and the radio node may be independent devices that communicate with each other via a radio path or via a wired connection, or they may be located in the same entity that communicates via a wired connection. For example, in certain example embodiments where the device 10 represents a gNB, the device 10 may be configured in a central unit (CU) and distributed unit (DU) architecture that divides the gNB functionality. In such an architecture, the CU may be a logical node that includes gNB functionality (such as transmission of user data, mobility control, radio access network sharing, positioning and / or session management, etc.). The CU may control the operation of (one or more) DUs via a midhaul interface referred to as an F1 interface, and the (one or more) DUs may have one or more radio units (RUs) that are connected to the (one or more) DUs via a fronthaul interface. Depending on the functional split option, the DU may be a logical node that includes a subset of the gNB functionality. It should be noted that a person of ordinary skill in the art will understand that the device 10 may include Figure 4 Components or features not shown.

[0062] like Figure 4As shown in the example of , the device 10 may include a processor 12 for processing information and executing instructions or operations. The processor 12 may be any type of general-purpose or special-purpose processor. In fact, as an example, the processor 12 may include one or more of a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), a field programmable gate array (FPGA), an application-specific integrated circuit (ASIC), and a processor based on a multi-core processor architecture or any other processing component. Although Figure 4 A single processor 12 is shown in FIG. 1 , but according to other embodiments, multiple processors may be utilized. For example, it should be understood that in some embodiments, the apparatus 10 may include two or more processors that may form a multiprocessor system that may support multiprocessing (e.g., in which case the processor 12 may represent a multiprocessor). In some embodiments, the multiprocessor system may be tightly coupled or loosely coupled (e.g., to form a computer cluster).

[0063] The processor 12 may perform functions associated with the operation of the device 10, which may include, for example, precoding of antenna gain / phase parameters, encoding and decoding of individual bits that form communication messages, formatting of information, and overall control of the device 10, including processes associated with establishing or modifying an indirect path to an additional path when the relay user equipment may be in an idle or inactive state (such as radio resource control idle / inactive).

[0064] The device 10 may also include or be coupled to a memory 14 (internal or external), which may be coupled to the processor 12 for storing information and instructions that may be executed by the processor 12. The memory 14 may be one or more memories and may be of any type suitable for the local application environment and may be implemented using any suitable volatile or non-volatile data storage technology, such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and / or removable memory. For example, the memory 14 may include any combination of random access memory (RAM), read-only memory (ROM), static memory such as a magnetic disk or optical disk, a hard disk drive (HDD), or any other type of non-transitory machine or computer readable medium or other suitable storage components. The instructions stored in the memory 14 may include program instructions or computer program code that, when executed by the processor 12, enables the device 10 to perform tasks as described herein.

[0065] In an embodiment, the device 10 may also include or be coupled to a drive or port (internal or external) that is configured to accept and read an external computer-readable storage medium, such as an optical disk, a USB drive, a flash drive, or any other storage medium. For example, the external computer-readable storage medium may store a computer program or software for execution by the processor 12 and / or the device 10.

[0066] In some embodiments, the device 10 may also include or be coupled to one or more antennas 15 for transmitting signals and / or data to the device 10 and receiving signals and / or data from the device 10. The device 10 may also include or be coupled to a transceiver 18, which is configured to transmit and receive information. The transceiver 18 may include, for example, multiple radio interfaces that may be coupled to (one or more) antennas 15, or may include any other suitable transceiver components. The radio interface may correspond to a variety of radio access technologies including one or more of the Global System for Mobile Communications (GSM), Narrowband Internet of Things (NB-IoT), LTE, 5G, WLAN, Bluetooth (BT), Bluetooth Low Energy (BT-LE), Near Field Communication (NFC), Radio Frequency Identifier (RFID), Ultra Wideband (UWB), MulteFire, etc. The radio interface may include components such as filters, converters (e.g., digital-to-analog converters, etc.), mappers, Fast Fourier Transform (FFT) modules, etc., to generate symbols for transmission via one or more downlinks and receive symbols (e.g., via uplinks).

[0067] As such, the transceiver 18 may be configured to modulate information onto a carrier waveform for transmission by the antenna(s) 15, and demodulate information received via the antenna(s) 15 for further processing by other elements of the apparatus 10. In other embodiments, the transceiver 18 may be capable of directly transmitting and receiving signals or data. Additionally or alternatively, in some embodiments, the apparatus 10 may include input and / or output devices (I / O devices) or input / output components.

[0068] In an embodiment, memory 14 may store software modules that provide functionality when executed by processor 12. The modules may include, for example, an operating system that provides operating system functionality for device 10. The memory may also store one or more functional modules, such as applications or programs, to provide additional functionality for device 10. The components of device 10 may be implemented in hardware, or as any suitable combination of hardware and software.

[0069] According to some embodiments, processor 12 and memory 14 may be included in or may form part of a processing circuit system / component or a control circuit system / component. In addition, in some embodiments, transceiver 18 may be included in or may form part of a transceiver circuit system / component.

[0070] As used herein, the term "circuitry" may refer to a hardware circuit implementation only (such as, analog and / or digital circuitry), a combination of hardware circuitry and software, a combination of analog and / or digital hardware circuitry and software / firmware, any portion of a hardware processor(s) with software that work together to enable a device (e.g., device 10) to perform various functions, and / or hardware circuit(s) and / or processor(s), or portions thereof, which operate using software, but where the software may not be present when the software is not needed for operation. As another example, as used herein, the term "circuitry" may also encompass an implementation of a hardware circuit or processor (or multiple processors), or a portion of a hardware circuit or processor, and its accompanying software and / or firmware. The term "circuitry" may also encompass, for example, a baseband integrated circuit in a server, a cellular network node or device, or other computing device or network device.

[0071] As introduced above, in some embodiments, the device 10 may be a network element or RAN node (e.g., a base station, an access point, a Node B, an eNB, a gNB, a TRP, a HAPS, an IAB node, a relay node, a WLAN access point, a satellite, etc.) or may be a part thereof. In an example embodiment, the device 10 may be a gNB or other radio node, or may be a CU and / or DU of a gNB. According to some embodiments, the device 10 may be controlled by the memory 14 and the processor 12 to perform functions associated with any of the embodiments described herein. For example, in some embodiments, the device 10 may be configured to perform one or more of the processes depicted in any of the flowcharts or signaling diagrams described herein (such as Figures 1 to 3 In some embodiments, as discussed herein, the apparatus 10 may be configured to perform processes related to establishing an indirect path as an additional path in a situation where the relay user equipment may be in an idle or inactive state (such as radio resource control idle / inactive).

[0072] Figure 4An example of an apparatus 20 according to an embodiment is also shown. In an embodiment, the apparatus 20 may be a node or element in a communication network or associated with such a network, such as a UE, a communication node, a mobile equipment (ME), a mobile station, a mobile device, a fixed device, an IoT device, or other device. As described herein, a UE may alternatively be referred to as, for example, a mobile station, a mobile equipment, a mobile unit, a mobile device, a user device, a subscriber station, a wireless terminal, a tablet, a smart phone, an IoT device, a sensor or a NB-IoT device, a watch or other wearable device, a head mounted display (HMD), a vehicle, a drone, a medical device and its application (e.g., remote surgery), an industrial device and its application (e.g., a robot and / or other wireless device operating in the context of an industrial and / or automated processing chain), a consumer electronic device, a device operating on a commercial and / or industrial wireless network, etc. As an example, the apparatus 20 may be implemented in, for example, a wireless handheld device, a wireless plug-in accessory, etc.

[0073] In some example embodiments, the apparatus 20 may include one or more processors, one or more computer-readable storage media (e.g., memory, storage, etc.), one or more radio access components (e.g., modems, transceivers, etc.), and / or a user interface. In some embodiments, the apparatus 20 may be configured to operate using one or more radio access technologies (such as GSM, LTE, LTE-A, NR, 5G, WLAN, WiFi, NB-IoT, Bluetooth, NFC, MulteFire, and / or any other radio access technology). It should be noted that those skilled in the art will appreciate that the apparatus 20 may include Figure 4 Components or functions not shown.

[0074] like Figure 4 As shown in the example of , the device 20 may include or be coupled to a processor 22 for processing information and executing instructions or operations. The processor 22 may be any type of general or special purpose processor. In fact, as examples, the processor 22 may include one or more of a general purpose computer, a special purpose computer, a microprocessor, a digital signal processor (DSP), a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), and a processor based on a multi-core processor architecture. Although Figure 4 A single processor 22 is shown in FIG. 1 , but according to other embodiments, multiple processors may be utilized. For example, it should be understood that in some embodiments, the device 20 may include two or more processors that may form a multiprocessor system that may support multiprocessing (e.g., in this case, the processor 22 may represent a multiprocessor). In some embodiments, the multiprocessor system may be tightly coupled or loosely coupled (e.g., to form a computer cluster).

[0075] Processor 22 may perform functions associated with the operation of device 20, which may include, for example, precoding of antenna gain / phase parameters, encoding and decoding of individual bits that form communication messages, formatting of information, and overall control of device 20, including processes associated with management of communication resources.

[0076] The device 20 may also include or be coupled to a memory 24 (internal or external), which may be coupled to the processor 22 for storing information and instructions that may be executed by the processor 22. The memory 24 may be one or more memories and may be of any type suitable for the local application environment and may be implemented using any suitable volatile or non-volatile data storage technology, such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and / or removable memory. For example, the memory 24 may include any combination of random access memory (RAM), read-only memory (ROM), static storage devices such as magnetic disks or optical disks, hard disk drives (HDDs), or any other type of non-transitory machine or computer readable media. The instructions stored in the memory 24 may include program instructions or computer program codes that, when executed by the processor 22, enable the device 20 to perform tasks as described herein.

[0077] In an embodiment, the device 20 may also include or be coupled to a drive or port (internal or external) configured to accept and read an external computer-readable storage medium, such as an optical disk, a USB drive, a flash drive, or any other storage medium. For example, the external computer-readable storage medium may store a computer program or software for execution by the processor 22 and / or the device 20.

[0078] In some embodiments, the device 20 may also include or be coupled to one or more antennas 25 for receiving downlink signals and transmitting from the device 20 via an uplink. The device 20 may also include a transceiver 28 configured to transmit and receive information. The transceiver 28 may also include a radio interface (e.g., a modem) coupled to the antenna 25. The radio interface may correspond to a variety of radio access technologies, including one or more of GSM, LTE, LTE-A, 5G, NR, WLAN, NB-IoT, Bluetooth, BT-LE, NFC, RFID, UWB, etc. The radio interface may include other components such as filters, converters (e.g., digital-to-analog converters, etc.), symbol demappers, signal shaping components, inverse fast Fourier transform (IFFT) modules, etc., to process symbols carried by the downlink or uplink, such as OFDM symbols.

[0079] For example, the transceiver 28 may be configured to modulate information onto a carrier waveform for transmission by (one or more) antennas 25, and demodulate information received via (one or more) antennas 25 for further processing by other elements of the device 20. In other embodiments, the transceiver 28 may be capable of directly transmitting and receiving signals or data. Additionally or alternatively, in some embodiments, the device 20 may include input and / or output devices (I / O devices). In certain embodiments, the device 20 may also include a user interface, such as a graphical user interface or a touch screen.

[0080] In an embodiment, the memory 24 may store software modules that provide functionality when executed by the processor 22. The modules may include, for example, an operating system that provides operating system functionality for the device 20. The memory may also store one or more functional modules, such as applications or programs, to provide additional functionality for the device 20. The components of the device 20 may be implemented in hardware, or as any suitable combination of hardware and software. According to an example embodiment, the device 20 may optionally be configured to communicate with the device 10 via a wireless or wired communication link 70 according to any radio access technology (such as NR).

[0081] According to some embodiments, processor 22 and memory 24 may be included in processing circuitry or control circuitry or may form part of processing circuitry or control circuitry. In addition, in some embodiments, transceiver 28 may be included in transceiver circuitry or may form part of transceiver circuitry.

[0082] As described above, according to some embodiments, the apparatus 20 may be, for example, a UE, a SL UE, a relay UE, a mobile device, a mobile station, a ME, an IoT device, and / or a NB-IoT device, etc. According to some embodiments, the apparatus 20 may be controlled by the memory 24 and the processor 22 to perform functions associated with any of the embodiments described herein (such as Figures 1 to 3 shown in or about Figures 1 to 3 ), or any other method described herein. For example, in one embodiment, the apparatus 20 may be controlled to perform a process related to establishing or modifying an indirect path to an additional path when the relay user equipment may be in an idle or inactive state (such as radio resource control idle / inactive), as described in detail elsewhere herein.

[0083] In some embodiments, an apparatus (e.g., apparatus 10 and / or apparatus 20) may include components for performing the methods, processes, or any variants discussed herein. Examples of such components may include one or more processors, memories, controllers, transmitters, receivers, and / or computer program codes for causing the execution of any operations discussed herein.

[0084] In view of the foregoing, certain example embodiments provide several technical improvements, enhancements and / or advantages over prior art processes and constitute improvements in at least the technical field of wireless network control and / or management. Certain embodiments may provide a way to greatly accelerate connection establishment or modification even when relay user equipment is in RRC idle or RRC inactive. Certain embodiments may facilitate the creation and modification of indirect paths in multipath scenarios.

[0085] In some example embodiments, the functionality of any method, process, signaling diagram, algorithm, or flow chart described herein may be implemented by software and / or computer program code or portions of code stored in a memory or other computer-readable or tangible medium and executed by a processor.

[0086] In some example embodiments, the device may include or be associated with at least one software application, module, unit or entity, which is configured as (one or more) arithmetic operations, or is configured as a program or part of a program (including added or updated software routines), which can be executed by at least one computing processor or controller. Programs (also referred to as program products or computer programs, including software routines, applets and macros) can be stored in any device-readable data storage medium and can include program instructions to perform specific tasks. Computer program products may include one or more computer executable components, which are configured to implement some example embodiments when the program is running. One or more computer executable components may be at least one software code or part of a code. Modifications and configurations required to implement the functions of the example embodiments may be performed as (one or more) routines, which may be implemented as (one or more) software routines added or updated. In one example, (one or more) software routines may be downloaded into the device.

[0087] As an example, the software or computer program code or part of the code can be in source code form, object code form or some intermediate form, and can be stored in some carrier, distribution medium or computer readable medium, which can be any entity or device capable of carrying the program. Such carriers may include, for example, recording media, computer memory, read-only memory, optoelectronic and / or electrical carrier signals, telecommunication signals and / or software distribution packages. Depending on the required processing power, the computer program can be executed in a single electronic digital computer, or the computer program can be distributed in multiple computers. Computer-readable media or computer-readable storage media can be non-transient media. As used herein, the term "non-transient" is a limitation of the medium itself (i.e., tangible, rather than a signal), rather than a limitation of data storage persistence (e.g., RAM to ROM).

[0088] In other example embodiments, the functions of the example embodiments may be performed by hardware or circuitry included in a device, such as by using an application specific integrated circuit (ASIC), a programmable gate array (PGA), a field programmable gate array (FPGA), or any other combination of hardware and software. In yet another example embodiment, the functions of the example embodiments may be implemented as a signal carried by an electromagnetic signal downloaded from the Internet or other network, such as a non-tangible component.

[0089] According to example embodiments, an apparatus such as a node, a device or a corresponding component may be configured as a circuit system, a computer or a microprocessor (such as a single-chip computer element) or a chipset, which may include at least a memory for providing storage capacity used for (one or more) arithmetic operations and / or an operation processor for performing (one or more) arithmetic operations.

[0090] The example embodiments described herein may apply to both singular and plural implementations, regardless of whether singular or plural language is used in conjunction with describing a particular embodiment. For example, an embodiment describing the operation of a single network node may also apply to example embodiments including multiple instances of the network node, and vice versa.

[0091] Those skilled in the art will readily appreciate that the example embodiments described above may be practiced using processes in a different order and / or using hardware elements in a configuration different from that disclosed. Therefore, although some embodiments have been described based on these example embodiments, it will be apparent to those skilled in the art that certain modifications, variations, and alternative configurations will be apparent while remaining within the spirit and scope of the example embodiments.

[0092] Partial glossary:

[0093] ACK Acknowledgement

[0094] C-RNTI Cell Radio Network Temporary Identifier

[0095] gNB gNodeB

[0096] HARQ Hybrid Automatic Repeat Request

[0097] I-RNTI Inactive Radio Network Temporary Identifier

[0098] MP Multipath

[0099] PC5 Reference point for a UE to communicate directly with another UE via a direct channel

[0100] PDCCH Physical Downlink Control Channel

[0101] RACH Random Access Channel

[0102] RRC Radio Resource Control

[0103] SL Side Link

[0104] TA Timing Advance

[0105] TMSI Temporary Mobile Subscriber Identity

[0106] U2N UE to Network

[0107] U2U UE to UE

[0108] UE User Equipment

[0109] UL Uplink

Claims

1. A device, include: at least one processor; as well as at least one memory storing instructions, which, when executed by the at least one processor, cause the apparatus to at least perform receiving, from a network element, a configuration of a relay user equipment container, the relay user equipment container being associated with adding or modifying an indirect path between the apparatus and the network element; as well as The relay user equipment container is indicated to the relay user equipment.

2. The apparatus of claim 1 , wherein the instructions, when executed by the at least one processor, further cause the apparatus to execute A confirmation of delivery of the relay user equipment container to the relay user equipment is sent to the network element.

3. The apparatus of claim 2, wherein the acknowledgement of delivery is sent using a radio resource control configuration complete message.

4. The apparatus according to any one of claims 1 to 3, wherein the indication comprises sidelink signaling on a connection from the apparatus to the relay user equipment.

5. The apparatus according to any one of claims 1 to 4, wherein the instructions, when executed by the at least one processor, further cause the apparatus to execute In response to an instruction from the network element, the relay user equipment is provided with timing advance information associated with the apparatus to communicate with the network element.

6. The apparatus according to any one of claims 1 to 5, wherein the instructions, when executed by the at least one processor, further cause the apparatus to execute Timing advance information is provided together with the relay user equipment container.

7. The apparatus according to any one of claims 1 to 6, wherein the instructions, when executed by the at least one processor, further cause the apparatus to execute The relay network is selected by the apparatus based on the relay user equipment not being identified in the configuration.

8. A device, include: at least one processor; as well as at least one memory storing instructions, which, when executed by the at least one processor, cause the apparatus to at least perform receiving a relay user equipment container from a remote user equipment; as well as Based on the relay user equipment container, connecting to a network element provides an indirect path for the remote user equipment.

9. The device according to claim 8, wherein the connection include: A dedicated random access channel access preamble is used from the relay user equipment container.

10. The device according to claim 8 or claim 9, wherein the connection include: Based on the relay user equipment container, a random access channel preamble is sent to the network element, and a random access channel response is received from the network element.

11. The device according to claim 8, wherein the connection include: Timing advance information from the relay user equipment container is used.

12. The apparatus of claim 11, wherein the instructions, when executed by the at least one processor, further cause the apparatus to perform A downlink control channel is monitored using at least one of the timing advance information or a cell radio network temporary identifier from the relay user equipment container.

13. A device, include: at least one processor; as well as at least one memory storing instructions, which, when executed by the at least one processor, cause the apparatus to at least perform configuring a remote user equipment with a relay user equipment container associated with adding or modifying an indirect path between the remote user equipment and the apparatus; as well as A confirmation of transfer of the relay user equipment container to the relay user equipment is received.

14. The apparatus of claim 13, wherein the relay user equipment container is configured to accelerate establishment of a connection between the relay user equipment and the apparatus.

15. An apparatus according to claim 13 or claim 14, wherein the relay user equipment container comprises a dedicated random access channel preamble or a timing advance for access without a random access channel procedure.

16. The apparatus according to any one of claims 13 to 15, wherein the instructions, when executed by the at least one processor, further cause the apparatus to perform Based on the relay user equipment container, receiving a random access channel preamble from the relay user equipment; and A random access channel response is provided to the relay user equipment.

17. The apparatus of claim 13, wherein the remote user equipment is configured include: The remote user equipment is instructed to provide the relay user equipment with timing advance information associated with the remote user equipment for use in communicating with the apparatus.

18. A method, include: receiving, at a user equipment, from a network element, a configuration of a relay user equipment container, the relay user equipment container being associated with adding or modifying an indirect path between the user equipment and the network element; as well as The relay user equipment container is indicated to the relay user equipment.

19. The method according to claim 18, further comprising: include: A confirmation of delivery of the relay user equipment container to the relay user equipment is sent to the network element.

20. The method of claim 19, wherein the acknowledgement of delivery is sent using a Radio Resource Control Configuration Complete message.

21. A method according to any one of claims 18 to 20, wherein the indication comprises sidelink signalling on a connection from the user equipment to the relay user equipment.

22. The method according to any one of claims 18 to 21, further comprising: include: In response to an instruction from the network element, the relay user equipment is provided with timing advance information associated with the user equipment to communicate with the network element.

23. The method according to any one of claims 18 to 22, further comprising: include: Timing advance information is provided together with the relay user equipment container.

24. The method according to any one of claims 18 to 23, further comprising: include: The relay network is selected by the user equipment based on the relay user equipment not being identified in the configuration.

25. A method, include: receiving, at the user equipment, a relay user equipment container from the remote user equipment; as well as Based on the relay user equipment container, connecting to a network element provides an indirect path for the remote user equipment.

26. The method of claim 25, wherein the connection include: A dedicated random access channel access preamble is used from the relay user equipment container.

27. A method according to claim 25 or claim 26, wherein the connection include: Based on the relay user equipment container, a random access channel preamble is sent to the network element, and a random access channel response is received from the network element.

28. The method of claim 25, wherein the connection include: Timing advance information from the relay user equipment container is used.

29. The method according to claim 28, further comprising: include: A downlink control channel is monitored using at least one of the timing advance information or a cell radio network temporary identifier from the relay user equipment container.

30. A method, include: configuring a remote user equipment with a relay user equipment container associated with adding or modifying an indirect path between the remote user equipment and a network element; as well as A confirmation of transfer of the relay user equipment container to the relay user equipment is received.

31. The method of claim 30, wherein the relay user equipment container is configured to accelerate establishment of a connection between the relay user equipment and the network element.

32. A method according to claim 30 or claim 31, wherein the relay user equipment container comprises a dedicated random access channel preamble or a timing advance for access without a random access channel procedure.

33. The method according to any one of claims 30 to 32, further comprising: include: Based on the relay user equipment container, receiving a random access channel preamble from the relay user equipment; as well as A random access channel response is provided to the relay user equipment.

34. The method of claim 30, wherein said configuring said remote user equipment include: The remote user equipment is instructed to provide the relay user equipment with timing advance information associated with the remote user equipment for use in communicating with the network element.

35. A device, include: means for receiving, from a network element, a configuration of a relay user equipment container, the relay user equipment container being associated with adding or modifying an indirect path between the apparatus and the network element; as well as Means for indicating the relay user equipment container to the relay user equipment.

36. The device according to claim 35, further comprising: include: Means for sending, to the network element, an acknowledgement of delivery of the relay user equipment container to the relay user equipment.

37. The apparatus of claim 36, wherein the acknowledgement of delivery is sent using a Radio Resource Control Configuration Complete message.

38. An apparatus according to any one of claims 35 to 37, wherein the indication comprises sidelink signalling on a connection from the apparatus to the relay user equipment.

39. The device according to any one of claims 35 to 38, further comprising: include: Means for providing, in response to an instruction from the network element, timing advance information associated with the apparatus to the relay user equipment to communicate with the network element.

40. The device according to any one of claims 35 to 39, further comprising: include: Means for providing timing advance information together with the relay user equipment container.

41. The device according to any one of claims 35 to 40, further comprising: include: Means for selecting, by the apparatus, the relay network based on the relay user equipment not being identified in the configuration.

42. A device, include: means for receiving a relay user equipment container from a remote user equipment; as well as Means for providing an indirect path for the remote user equipment based on the relay user equipment container, connected to a network element.

43. The device according to claim 42, wherein the connection include: A dedicated random access channel access preamble is used from the relay user equipment container.

44. An apparatus according to claim 42 or claim 43, wherein the connection include: Based on the relay user equipment container, a random access channel preamble is sent to the network element, and a random access channel response is received from the network element.

45. The device of claim 42, wherein the connection include: Timing advance information from the relay user equipment container is used.

46. ​​The device according to claim 45, further comprising: include: Means for monitoring a downlink control channel using at least one of the timing advance information or a cell radio network temporary identifier from the relay user equipment container.

47. A device, include: means for configuring a remote user equipment with a relay user equipment container, the relay user equipment container being associated with adding or modifying an indirect path between the remote user equipment and the apparatus; as well as Means for receiving confirmation of transfer of the relay user equipment container to the relay user equipment.

48. The apparatus of claim 47, wherein the relay user equipment container is configured to accelerate connection establishment between the relay user equipment and the apparatus.

49. An apparatus according to claim 47 or claim 48, wherein the relay user equipment container includes a dedicated random access channel preamble or a timing advance for access without a random access channel procedure.

50. The device according to any one of claims 47 to 49, further comprising: include: means for receiving a random access channel preamble from the relay user equipment based on the relay user equipment container; as well as means for providing a random access channel response to the relay user equipment.

51. The apparatus of claim 47, wherein said configuring said remote user equipment include: The remote user equipment is instructed to provide the relay user equipment with timing advance information associated with the remote user equipment for communicating with the apparatus.

52. A computer program product encoded with instructions for performing the method according to any one of claims 18 to 34.

53. A non-transitory computer readable medium encoded with instructions that, when executed in hardware, perform the method of any one of claims 18 to 34.

Images