Improved ProSe Relay UE Enablement

By having the radio base station control relay activation through broadcast messages and persistence checks, the method addresses inefficient relay activation in 3GPP LTE-A networks, optimizing relay usage and reducing interference.

JP7578787B2Active Publication Date: 2024-11-06PANASONIC INTELLECTUAL PROPERTY CORP OF AMERICA
View PDF 8 Cites 0 Cited by

Patent Information

Application Number
JP2023207906
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Priority Date
2015-07-24
Filing Date
2023-12-08
Publication Date
2024-11-06
Estimated Expiration
2036-06-15

AI Technical Summary

Technical Problem

The challenge in 3GPP LTE-A networks is the inefficient activation of relay functionality in user equipment, leading to unnecessary relay activations that increase contention and interference on relay discovery resources, and the need for improved control mechanisms to manage relay activation.

Method used

A method where a radio base station determines the need for additional relays in a cell, sends a broadcast message with a persistence check value, and requires relay user equipment to perform checks before activating relay functionality, ensuring only necessary relays are activated, thereby controlling the number of relays and reducing unnecessary resource usage.

Benefits of technology

This approach effectively manages relay activation, minimizing interference and resource congestion while ensuring adequate relay coverage, optimizing network performance by activating only the required number of relays.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007578787000007
    Figure 0007578787000007
  • Figure 0007578787000008
    Figure 0007578787000008
  • Figure 0007578787000009
    Figure 0007578787000009
Patent Text Reader

Abstract

To provide a method of activating the relay function of a ProSe enabled and relay enabled user equipment within a mobile communication network.SOLUTION: A radio base station connected with a relay UE determines whether or not additional relay is needed within the radio cell controlled by the radio base station. When additional relays are needed within the radio cell, the radio base station selects a persistence check value and sends a broadcast message in the wireless cell. The broadcast message indicates at least that more relays are needed, and includes the selected persistence check value. When the broadcast message is received, and when the relay UE determines that the relay requirements to activate its relay function within the radio cell are met, and when it is determined the persistence check performed by the relay UE succeeds based on the received persistence check value, the relay UE activates the relay function.SELECTED DRAWING: Figure 13
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present disclosure relates to a method for enabling a relay function of a relay user equipment, and also to provide a radio base station and a relay user equipment for participating in the method described herein. [Background technology]

[0002] LTE (Long Term Evolution) 3G (Third Generation Mobile Communication System) based on WCDMA radio access technology is being deployed on a wide scale all over the world. As a first step in enhancing or evolving this technology, HSDPA (High Speed ​​Downlink Packet Access) and enhanced uplink also called HSUPA (High Speed ​​Uplink Packet Access) have been introduced, providing a highly competitive radio access technology.

[0003] To meet the ever-increasing demands from users and to ensure competitiveness against new radio access technologies, 3GPP has introduced a new mobile communication system called LTE (Long Term Evolution). LTE is designed to meet carriers' needs for high-speed transmission of data and media, as well as high-capacity voice support, over the next decade. The ability to provide high bit rates is an important measure for LTE.

[0004] The LTE (Long Term Evolution) work item (WI) specifications, called E-UTRA (Evolved UMTS Terrestrial Radio Access (UTRA)) and E-UTRAN (Evolved UMTS Terrestrial Radio Access Network (UTRAN), will be published as Release 8 (LTE Release 8). The LTE system is a packet-based, efficient radio access and radio access network that provides full IP-based functionality with low latency and low cost. LTE specifies multiple scalable transmission bandwidths, such as 1.4 MHz, 3.0 MHz, 5.0 MHz, 10.0 MHz, 15.0 MHz, and 20.0 MHz, to achieve flexible system deployment with a given spectrum. The downlink employs OFDM (orthogonal frequency division multiplexing) based radio access. Such radio access is inherently less susceptible to multipath interference (MPI) due to its low symbol rate, uses cyclic prefixes (CP), and can accommodate various transmission bandwidth configurations. For the uplink, single-carrier frequency division multiple access (SC-FDMA) based radio access is adopted because providing a large coverage area takes precedence over increasing peak data rates, given the limited transmission power of the UE (user equipment). In LTE Release 8 / 9, a number of key packet radio access technologies are adopted, including multiple-input multiple-output (MIMO) channel transmission technology, to achieve a highly efficient control signaling structure.

[0005] LTE Architecture Figure 1 shows the overall architecture of LTE. E-UTRAN consists of eNodeBs, which terminate E-UTRA user plane (PDCP / RLC / MAC / PHY) and control plane (RRC) protocols for UEs. eNBs (eNodeBs) host the PHY (Physical), MAC (Medium Access Control), RLC (Radio Link Control), and PDCP (Packet Data Control Protocol) layers, which include the user plane header compression and encryption functions. eNBs also provide the RRC (Radio Resource Control) functions for the control plane. eNBs perform many functions, including radio resource management, admission control, scheduling, enforcement of uplink QoS (Quality of Service) through negotiation, broadcasting of cell information, encryption / decryption of user and control plane data, and compression / decompression of downlink / uplink user plane packet headers. Multiple eNodeBs are connected to each other by the X2 interface.

[0006] The eNodeBs are also connected to the EPC (Evolved Packet Core) by the S1 interface, more specifically to the MME (Mobility Management Entity) by the S1-MME and to the SGW (Serving Gateway) by the S1-U. The S1 interface supports a many-to-many relationship between the MME / Serving Gateway and the eNodeBs. The SGW routes and forwards user data packets, while also acting as a mobility anchor for the user plane during handovers between eNodeBs, and as an anchor for mobility between LTE and other 3GPP technologies (terminating the S4 interface and relaying traffic between 2G / 3G systems and the PDN GW). For idle user equipment, the SGW terminates the downlink data path and triggers paging when downlink data arrives for that user equipment. The SGW manages and stores the user equipment context, e.g., parameters of IP bearer services or network internal routing information. Furthermore, the SGW performs duplication of user traffic in case of lawful interception.

[0007] The MME is the main control node of the LTE access network. It is responsible for the paging procedures, including tracking and retransmission of idle mode user equipment. It is involved in the bearer activation / deactivation process and is also responsible for selecting the SGW for the user equipment at the time of initial attach and during intra-LTE handover with relocation of CN (core network) nodes. The MME is responsible for authenticating the user (by interacting with the HSS). NAS (non-access stratum) signaling is terminated in the MME, which is also responsible for generating and assigning temporary identities to user equipment. The MME checks the authorization of the user equipment to camp on the service provider's PLMN (public land mobile network) and enforces roaming restrictions for the user equipment. The MME is the termination point in the network for ciphering / integrity protection of the NAS signaling and handles security key management. Lawful interception of signaling is also supported by the MME. Additionally, the MME provides the control plane function for mobility between LTE and 2G / 3G access networks, and terminates the S3 interface from the SGSN at the MME, and also terminates the S6a interface towards the home HSS for roaming user equipment.

[0008] Component carrier structure in LTE The downlink component carrier of a 3GPP LTE system is divided in the time-frequency domain into so-called subframes. In 3GPP LTE, each subframe is divided into two downlink slots, the first of which contains a control channel region (PDCCH region) in the first few OFDM symbols, as shown in Figure 2. Each subframe consists of a given number of OFDM symbols in the time domain (12 or 14 OFDM symbols in 3GPP LTE (Release 8)), each OFDM symbol covering the entire bandwidth of the component carrier. Each OFDM symbol therefore consists of a number of modulation symbols transmitted on the respective subcarriers. In LTE, the signal transmitted in each slot is therefore each OFDM symbol having N DL RB ×N RB SC subcarriers and N DL symb It is described by a resource grid of N OFDM symbols. DL RB is the number of resource blocks in the bandwidth. DL RB Depends on the downlink transmission bandwidth configured in the cell and should satisfy:

number

[0009] For example, considering a multi-carrier communication system employing OFDM, which is used as an example in 3GPP LTE (Long Term Evolution), the smallest unit of resources that can be allocated by a scheduler is one "resource block". A physical resource block (PRB) is defined as consecutive OFDM symbols in the time domain (e.g., 7 OFDM symbols) and consecutive subcarriers in the frequency domain (e.g., 12 subcarriers of a component carrier), as exemplarily shown in Fig. 2. Thus, in 3GPP LTE (Release 8), a physical resource block consists of one slot in the time domain and multiple resource elements corresponding to 180 kHz in the frequency domain (for further details on the downlink resource grid, see, for example, section 6.2 of Non-Patent Document 1) (available on the 3GPP website and incorporated herein by reference).

[0010] A subframe consists of two slots, whereby there are 14 OFDM symbols in a subframe when the so-called "normal" CP (Cyclic Prefix) is used, and 12 OFDM symbols in a subframe when the so-called "extended" CP is used. As a terminology, in the following, a time-frequency resource equal to the same consecutive subcarriers across an entire subframe is referred to as a "resource block pair", or equivalently as an "RB pair" or "PRB pair".

[0011] The term "component carrier" refers to a combination of several resource blocks in the frequency domain. In future releases of LTE, the term "component carrier" will no longer be used. Instead, this term will be changed to "cell". A "cell" refers to a combination of downlink and optionally uplink resources. The link between the carrier frequency of the downlink resources and the carrier frequency of the uplink resources is indicated in the system information transmitted on the downlink resources. Similar assumptions about the component carrier structure apply to subsequent releases.

[0012] Carrier aggregation in LTE-A to support wider bandwidths At the World Radiocommunication Conference 2007 (WRC-07), the frequency spectrum for IMT-Advanced was decided. Although the overall frequency spectrum for IMT-Advanced was decided, the actual available frequency bandwidth varies from region to region or country to country. However, following the decision of the outline of the available frequency spectrum, standardization of the air interface was started in 3GPP (3rd Generation Partnership Project). At the 3GPP TSG RAN #39 meeting, a study item description on "Further Advancements for E-UTRA (LTE-Advanced)" was approved. This study item covers the technology elements to be considered in evolving E-UTRA, for example to meet the requirements of IMT-Advanced.

[0013] The bandwidth that the LTE-Advanced system can support is 100MHz, while the LTE system can only support 20MHz. Recently, the development of wireless networks has been hindered by the lack of wireless spectrum, and as a result, it is difficult to secure a sufficiently wide spectrum band for the LTE-Advanced system. Therefore, it is an urgent task to find a way to obtain a wider wireless spectrum band, and one possible answer is the carrier aggregation function.

[0014] In carrier aggregation, two or more component carriers are aggregated to support a wider transmission bandwidth of up to 100 MHz. In the LTE-Advanced system, several cells in the LTE system are aggregated into one wider channel, which is wide enough for 100 MHz even if these cells in LTE are in different frequency bands.

[0015] At least, all component carriers can be configured as LTE Rel-8 / 9 compatible when the bandwidth of the component carrier does not exceed the supported bandwidth of the LTE Rel-8 / 9 cell. Not all component carriers aggregated by a user equipment may be LTE Rel-8 / 9 compatible. Existing mechanisms (e.g., barring) can be used to prevent Rel-8 / 9 user equipment from camping on a component carrier.

[0016] Depending on its capabilities, a user equipment can simultaneously receive or transmit on one or multiple component carriers (corresponding to multiple serving cells). An LTE-A Rel-10 user equipment with reception and / or transmission capabilities for carrier aggregation can simultaneously receive and / or transmit on multiple serving cells, whereas an LTE Rel-8 / 9 user equipment can receive and transmit on only one serving cell, provided that the component carrier structure follows the Rel-8 / 9 specifications.

[0017] Carrier aggregation is supported for both contiguous and non-contiguous component carriers, where each component carrier is limited to a maximum of 110 resource blocks in the frequency domain (when using 3GPP LTE (Release 8 / 9) calculation methods).

[0018] It is possible to configure a 3GPP LTE-A (Release 10) compatible user equipment to aggregate different numbers of component carriers, possibly of different bandwidths in the uplink and downlink, originating from the same eNodeB (base station). The number of downlink component carriers that can be configured depends on the downlink aggregation capability of the user equipment. Conversely, the number of uplink component carriers that can be configured depends on the uplink aggregation capability of the user equipment. Currently, it is not possible to configure a mobile terminal with more uplink component carriers than downlink component carriers. In a typical TDD deployment, the number of component carriers and the bandwidth of each component carrier are the same in the uplink and downlink. Component carriers originating from the same eNodeB do not necessarily have to provide the same coverage.

[0019] The spacing of the center frequencies of contiguously aggregated component carriers should be a multiple of 300 kHz in order to maintain compatibility with the 100 kHz frequency raster of 3GPP LTE (Release 8 / 9) while at the same time preserving the orthogonality of the 15 kHz spaced subcarriers. In some aggregation scenarios, the n x 300 kHz spacing can be facilitated by inserting a small number of unused subcarriers between consecutive component carriers.

[0020] The impact of aggregating multiple carriers only extends to the MAC layer, where one HARQ entity is required per aggregated component carrier, both in uplink and downlink. There is a maximum of one transport block per component carrier (without SU-MIMO in uplink). A transport block and its HARQ retransmissions, if required, must be mapped to the same component carrier.

[0021] When carrier aggregation is configured, the mobile terminal has only one RRC connection with the network. At the time of RRC connection establishment / re-establishment, one cell provides security inputs (one ECGI, one PCI, and one ARFCN) and non-access stratum mobility information (e.g., TAI) similar to LTE Release 8 / 9. After RRC connection establishment / re-establishment, the component carrier corresponding to the cell is called downlink PCell (primary cell). In the connected state, there is always one and only one DL PCell (downlink PCell) and one UL PCell (uplink PCell) configured per user equipment. Among the set of configured component carriers, the cells other than the primary cell are called SCells (secondary cells). The carriers of the SCells are DL SCCs (downlink secondary component carriers) and UL SCCs (uplink secondary component carriers). Up to five serving cells including the PCell can be configured for one UE.

[0022] The characteristics of the downlink and uplink PCells are as follows: 1. For each SCell, it is configurable for the UE to use uplink resources in addition to downlink resources (hence the number of configured DL SCCs is always greater than or equal to the number of UL SCCs, and an SCell cannot be configured to use only uplink resources). 2. Downlink PCells cannot be disabled, unlike SCells. 3. Re-establishment is triggered when RLF (Rayleigh fading) occurs in the downlink PCell, but re-establishment is not triggered when RLF occurs in the downlink SCell. 4. Non-access stratum information is obtained from the downlink PCell. 5. The PCell can only be changed by handover procedures (i.e. security key change and RACH procedures). 6. PCell is used to transmit PUCCH. 7. The uplink PCell is used to transmit Layer 1 uplink control information. 8. From the user equipment point of view, each uplink resource only belongs to one serving cell.

[0023] Configuration and reconfiguration as well as addition and removal of component carriers can be done by RRC. Activation and deactivation is done via MAC control elements. During intra-LTE handover, SCells can also be added, removed or reconfigured for use in the target cell by RRC. When adding a new SCell, dedicated RRC signaling is used to send the system information of the SCell, which is required for transmission / reception (similar to handover in LTE Release 8 / 9). Each SCell is configured with a serving cell index when the SCell is added to one UE, and the PCell always has serving cell index 0.

[0024] When a user equipment is configured to use carrier aggregation, at least one pair of uplink and downlink component carriers is always active, the downlink component carrier of the pair is sometimes referred to as the "downlink anchor carrier". The same applies for the uplink.

[0025] When carrier aggregation is configured, a user equipment can be scheduled on several component carriers at the same time, but at most one random access procedure should be possible at a time. Cross-carrier scheduling allows the PDCCH of a component carrier to schedule resources of another component carrier. For this purpose, a component carrier identification field, called CIF, is introduced in the respective DCI (Downlink Control Information) format.

[0026] When cross-carrier scheduling is not performed, the uplink component carrier to which the grant applies can be identified by the link established by RRC signaling between the uplink component carrier and the downlink component carrier. The link of the downlink component carrier to the uplink component carrier does not necessarily have to be one-to-one. In other words, multiple downlink component carriers can be linked to the same uplink component carrier. At the same time, one downlink component carrier can only be linked to one uplink component carrier.

[0027] LTE D2D (Device to Device) ProSe (Proximity Services) Proximity-based applications and services represent an emerging socio-technical trend. Recognized areas include commercial and public safety services that are of interest to operators and users. The introduction of Proximity Services (ProSe) capabilities in LTE will enable the 3GPP industry to serve this evolving market, while at the same time serving the urgent needs of several public safety organizations that are also working on LTE. D2D (Device-to-Device) communication is a technology element introduced by LTE Release 12, which allows D2D as an underlay to cellular networks to increase spectrum efficiency. For example, if the cellular network is LTE, all data-carrying physical channels use SC-FDMA for D2D signaling. In D2D communication, user equipments transmit data signals to each other over a direct link using cellular resources instead of going through a radio base station. Throughout this disclosure, the terms "D2D", "ProSe" and "sidelink" are interchangeable.

[0028] D2D communication in LTE D2D communication in LTE focuses on two areas: discovery and communication. Proximity-Based Services (Proximity-Based Services) Direct Discovery is defined as a procedure used by a ProSe-enabled UE to discover other ProSe-enabled UEs in its vicinity using E-UTRA direct radio signals over the PC5 interface and is described in more detail later.

[0029] In D2D communication, UEs transmit data signals to each other over a direct link using cellular resources instead of going through a BS (base station). D2D users communicate directly while remaining under the control of the BS, i.e., when they are at least within the coverage of an eNB. Therefore, D2D can improve system performance by reusing cellular resources.

[0030] D2D is assumed to operate in the uplink LTE spectrum (in case of FDD) or in uplink subframes of the cell providing coverage (in case of TDD, except when out of coverage). Furthermore, D2D transmission / reception does not use full duplex communication on a given carrier. From an individual UE's point of view, on a given carrier, D2D signal reception and LTE uplink transmission do not use full duplex communication, i.e. simultaneous D2D signal reception and LTE UL transmission are not possible.

[0031] In D2D communication, when one particular UE1 has a transmitting role (transmitting user equipment or transmitting terminal), UE1 transmits data and another UE2 (receiving user equipment) receives it. UE1 and UE2 can alternate their transmitting and receiving roles. A transmission from UE1 can be received by one or several UEs, such as UE2. In relation to the user plane protocol, some of the agreements from the point of view of D2D communication are given below (see also section 9.2.2 of 3GPP TS 2013-01-13, which is incorporated herein by reference):

[0032] -PDCP: --1:M D2D broadcast communication data (i.e., IP packets) should be treated as normal user plane data. --Header compression / decompression in PDCP is applicable to 1:M D2D broadcast communication. --For D2D broadcast operation for public safety, U-Mode is used for header compression in PDCP. -RLC: --RLC UM is used for 1:M D2D broadcast communication. --Segmentation and reassembly is supported on L2 by RLC UM. --The receiving UE needs to maintain at least one RLC UM entity for each transmitting peer UE. --The RLC UM receiver entity does not need to be configured before receiving the first RLC UM data unit. --Therefore, there is no recognized need for RLC AM or RLC TM for D2D communications for user plane data transmission. -MAC: --1:M No HARQ feedback is assumed for D2D broadcast communication. The receiving UE needs to know the source ID to identify the receiver RLC UM entity. --The MAC header contains the L2 destination ID, which allows filtering out the packet at the MAC layer. --The L2 destination ID can be a broadcast, groupcast or unicast address. ---L2 Groupcast / Unicast: The L2 destination ID carried in the MAC header allows to discard a received RLC UM PDU even before it is delivered to the RLC receiver entity. ---L2 Broadcast: The receiving UE aims to process all received RLC PDUs from all senders, reassemble the IP packets and deliver them to the upper layers. --The MAC subheader includes the LCID (to distinguish between multiple logical channels). --At least multiplexing / demultiplexing, priority handling and padding are useful for D2D.

[0033] ProSe Direct Communication Layer 2 Link Briefly, ProSe Direct one-to-one communication is realized by establishing a secure Layer 2 link over PC5 between two UEs. Each UE has a Layer 2 ID for unicast communication that is included in the source Layer 2 ID field of every frame the UE transmits on the Layer 2 link and in the destination Layer 2 ID of every frame the UE receives on the Layer 2 link. The UE needs to ensure that the Layer 2 ID for unicast communication is at least locally unique. Therefore, the UE should be prepared to handle Layer 2 ID collisions with neighboring UEs using an unspecified mechanism (e.g., self-allocate a new Layer 2 ID for unicast communication when a collision is detected). The Layer 2 link for one-to-one ProSe Direct communication is identified by the combination of the Layer 2 IDs of the two UEs. This means that a UE can engage in multiple Layer 2 links for one-to-one ProSe Direct communication using the same Layer 2 ID.

[0034] One-to-one ProSe direct communication consists of the following steps, as described in detail in Section 7.1.2 of Non-Patent Document 3, which is incorporated herein by reference. -Establishment of a secure Layer 2 link over PC5. -IP address / prefix allocation. -Maintaining Layer 2 link over PC5. - Releasing the Layer 2 link via PC5.

[0035] FIG. 3 discloses a method for establishing a secure Layer 2 link over a PC5 interface. 1. UE-1 sends a Direct Communication Request message to UE-2 to trigger mutual authentication. The link initiator (UE-1) needs to know the Layer 2 ID of the peer (UE-2) to perform step 1. As an example, the link initiator can learn the Layer 2 ID of the peer by first performing a discovery procedure or by participating in a ProSe one-to-many communication that includes the peer. 2. UE-2 initiates the procedure for mutual authentication. Upon successful completion of the authentication procedure, the establishment of a secure Layer 2 link via PC5 is completed.

[0036] At least the following standard IETF mechanisms can be used for IP address / prefix allocation: -DHCP-based IP address configuration for IPv4 address assignment. -IPv6 stateless address autoconfiguration, as specified in RFC4862, for IPv6 prefix allocation.

[0037] One of the two UEs acts as a DHCP server or an IPv6 default router. In the case of a ProSeUE-NW relay (see also the later chapter on ProSe relay), the relay acts as a DHCP server or an IPv6 default router for all remote UEs connecting to it over a secure Layer 2 link via PC5.

[0038] UEs engaged in isolated (non-relaying) point-to-point communications may also use link-local addresses.

[0039] The PC5 signaling protocol should support a keep-alive function that is used to detect when the UE is not within ProSe communication range so that the UE can proceed with an implicit Layer 2 link release.

[0040] The Layer 2 link release via PC5 can be performed using a disconnection request message sent to the other UE, which also deletes all associated context data. Upon receiving the disconnection request message, the other UE responds with a disconnection response message and deletes all context data related to the Layer 2 link.

[0041] ProSe direct communication related identification information Non-Patent Document 4 defines in subclause 8.3 the following identification information for use in ProSe direct communication: -SL-RNTI: Unique identification information used for ProSe direct communication scheduling, Source Layer 2 ID: Identifies the sender of data in sidelink ProSe direct communication. The Source Layer 2 ID is 24 bits long and is used together with the ProSe Layer 2 destination ID and LCID for identification of the RLC UM entity and the PDCP entity at the receiver. Destination Layer 2 ID: Identifies the destination of data in sidelink ProSe direct communication. The Destination Layer 2 ID is 24 bits long and is split into two bit strings at the MAC layer. One bit string is the LSB part (8 bits) of the destination Layer 2 ID and is forwarded to the physical layer as the Sidelink Control Layer 1 ID. It identifies the intended destination of the data in the Sidelink Control and is used for packet filtering at the physical layer. --The second bit string is the most significant bit (16 bits) of the destination Layer 2 ID, which is carried in the MAC header. This is used to filter packets at the MAC layer.

[0042] Non-access stratum signaling is required for group formation and to configure the source Layer 2 ID, destination Layer 2 ID and sidelink control L1 ID in the UE. These identities are provided by higher layers or are derived from identities provided by higher layers. In case of groupcast and broadcast, the ProSe UE ID provided by higher layers is directly used as the source Layer 2 ID and the ProSe Layer 2 group ID provided by higher layers is directly used as the destination Layer 2 ID in the MAC layer.

[0043] Radio Resource Allocation for Proximity Services From the perspective of a transmitting UE, a proximity service enabled UE (ProSe enabled UE) can operate in two resource allocation modes.

[0044] Mode 1 refers to eNB-scheduled resource allocation, where the UE requests transmission resources from the eNB (or Release 10 relay node), and the eNodeB (or Release 10 relay node) schedules the resources used by the UE to transmit direct data and direct control information (e.g., scheduling assignment). The UE needs to be RRC_CONNECTED to transmit data. In particular, the UE transmits a scheduling request (D-SR or random access) to the eNB and then transmits a buffer status report (BSR) as usual (see also the following chapter "Transmission Procedures for D2D Communication"). Based on the BSR, the eNB can determine that the UE has data for ProSe direct communication transmission and can estimate the resources required for transmission.

[0045] Mode 2, on the other hand, refers to autonomous resource selection by the UE, where the UE itself selects the resources (time and frequency) for transmitting direct data and direct control information (i.e. SA) from a resource pool. One resource pool is defined, for example, by the content of SIB18, i.e. by the field commTxPoolNormalCommon, and this particular resource pool is broadcast in the cell and is then commonly available for all UEs in the cell that are still in RRC_Idle state. In practice, the eNB may define up to four different instances of the above pool, four resource pools respectively for the transmission of SA messages and direct data. However, the UE should always use the first resource pool defined in the list, even if it is configured with multiple resource pools.

[0046] Alternatively, a separate resource pool may be defined by the eNB and signaled in SIB18, i.e. by using the field commTxPoolExceptional, which may be used by the UE in exceptional cases.

[0047] The resource allocation mode that the UE will use can be configured by the eNB. Furthermore, the resource allocation mode that the UE will use for D2D data communication may also depend on the RRC state, i.e., RRC_IDLE or RRC_CONNECTED, and the coverage state of the UE, i.e., in-coverage, out-of-coverage. A UE is considered in-coverage if it has a serving cell (i.e., the UE is RRC_CONNECTED or camped on a cell in RRC_IDLE). FIG. 4 shows the transmission / reception resource usage for overlay (LTE) and underlay (D2D) systems.

[0048] Basically, the eNodeB controls whether the UE may apply transmission in Mode 1 or Mode 2. Once the UE knows which resources it can transmit (or receive) D2D communication, it will use only the corresponding resources for the corresponding transmission / reception. For example, in FIG. 4, the D2D subframe will be used only for receiving or transmitting D2D signals. Since the UE as a D2D device will operate in half-duplex mode, the UE may either receive or transmit D2D signals at any time. Similarly, the other subframes shown in FIG. 4 can be used for LTE (overlay) transmission and / or reception.

[0049] Transmission Procedure for D2D Communication The D2D data transmission procedure differs depending on the resource allocation mode. As described above for Mode 1, the eNB explicitly schedules resources for scheduling assignment and D2D data communication after a corresponding request from the UE. In particular, the UE may be informed by the eNB that D2D communication is generally allowed but not given Mode 2 resources (i.e. resource pool), which can be done for example by exchanging a D2D communication interest indication by the UE and a corresponding response, D2D communication response, and the corresponding exemplary ProseCommConfig information element described above will not include commTxPoolNormalCommon, which means that a UE wanting to initiate direct communication including a transmission needs to request the E-UTRAN to allocate resources for each individual transmission. Thus, in such a case, the UE needs to request resources for each individual transmission, and in the following the various steps of the request / grant procedure are exemplarily listed for this Mode 1 resource allocation.

[0050] Step 1: The UE sends a Scheduling Request (SR) to the eNB via the PUCCH. - Step 2: The eNB grants UL resources (for the UE to transmit the BSR) via the PDCCH, which is scrambled by the C-RNTI. Step 3: The UE sends a D2D BSR indicating the buffer status via PUSCH. - Step 4: The eNB grants D2D resources (for the UE to transmit data) via PDCCH, which is scrambled by the D2D-RNTI. Step 5: The D2D Tx UE transmits SA / D2D data according to the grant received in step 4.

[0051] The SA (Scheduling Assignment), also referred to as SCI (Sidelink Control Information), is a compact (low payload) message that contains control information, e.g. pointers to time-frequency resources, modulation and coding schemes, and group destination IDs for the corresponding D2D data transmission. The SCI carries sidelink scheduling information for one (ProSe) destination ID. The content of the SA (SCI) basically follows the grant received in step 4 above. The D2D grant and SA content (i.e. SCI content) are defined in subclause 5.4.3 of 3GPP TS 2013-010361, which is incorporated herein by reference, defining in particular SCI format 0.

[0052] On the other hand, for Mode 2 resource allocation, the above steps 1 to 4 are basically not required, and the UE autonomously selects resources for SA and D2D data transmission from a transmission resource pool configured and provided by the eNB.

[0053] FIG. 5 exemplarily illustrates the transmission of scheduling assignments and D2D data for two UEs, i.e., UE-A and UE-B, where the resources for transmitting the scheduling assignments are periodic and the resources used for D2D data transmission are indicated by the corresponding scheduling assignments.

[0054] ProSe network architecture and ProSe entities Figure 6 shows a high-level example architecture for the non-roaming case, including different ProSe applications in each UE A and B, and a ProSe application server and ProSe functions in the network. The example architecture in Figure 6 is taken from Chapter 4.2 "Architectural Reference Model" of Non-Patent Document 6, which is incorporated herein by reference.

[0055] These functional entities are presented and described in detail in subclause 4.4 “Functional Entities” of 3GPP TS 2.0, which is incorporated herein by reference. ProSe functions are logical functions used for network-related operations required for ProSe and perform various roles for each of the ProSe features. ProSe functions are part of 3GPP's EPC and provide all related network services such as authorization, authentication, data handling, etc. related to proximity services. For ProSe direct discovery and communication, the UE can obtain specific ProSe UE identity information, other configuration information, and authorization from the ProSe function via the PC3 reference point. Although multiple ProSe functions may be deployed in the network, a single ProSe function is presented for ease of illustration. ProSe functions consist of three main subordinate functions that perform different roles depending on the ProSe features: Direct Provision Function (DPF), Direct Discovery Name Management Function, and EPC-level Discovery Function. The DPF is used to provide the UE with the necessary parameters to use ProSe direct discovery and ProSe direct communication.

[0056] The term "UE" used in the above connection refers to a ProSe-enabled UE that supports the ProSe function.

[0057] The ProSe Application Server supports the storage of EPC ProSe User ID and ProSe Function ID, and the mapping of application layer User ID and EPC ProSe User ID. The ProSe AS (Application Server) is an entity outside the scope of 3GPP. The ProSe application in the UE communicates with the ProSe AS via the application layer reference point PC1. The ProSe AS is connected to the 3GPP network via the PC2 reference point.

[0058] UE Coverage Status for D2D As already mentioned before, the resource allocation mode for D2D communication, apart from the RRC state, i.e. RRC_IDLE and RRC_CONNECTED, also depends on the coverage state of the UE, i.e. in-coverage, out-of-coverage. A UE is considered in-coverage if it has a serving cell (i.e. the UE is RRC_CONNECTED or camped on a cell in RRC_IDLE). The two coverage states mentioned so far, IC (In Coverage) and OOC (Out of Coverage), are further differentiated into D2D sub-states. Figure 7 shows the four different states that a D2D UE may be associated with, which can be summarized as follows:

[0059] - State 1: UE1 has uplink and downlink coverage. In this state, the network controls each D2D communication session. Furthermore, the network configures whether UE1 should use resource allocation mode 1 or mode 2. - State 2: UE2 has downlink coverage but no uplink coverage, i.e. only DL coverage. The network broadcasts a (contention-based) resource pool. In this state the transmitting UE selects resources used for SA and data from the resource pool configured by the network, and in such state resource allocation is only possible according to mode 2 of D2D communication. - State 3: UE3 is already considered to be OOC (out of coverage) strictly speaking, since UE3 has no uplink and downlink coverage. However, UE3 is in the coverage of some UE (e.g. UE1) that is itself in the coverage of the cell, i.e., those some UEs can also be referred to as CP relay UEs or simply relay UEs (see also the later chapter on ProSe relay). Therefore, the area of ​​UEs in state 3 in Fig. 7 can be shown as CP UE relay coverage area. UEs in this state 3 are also referred to as OOC state 3 UEs. In this state, the UE can receive some cell specific information transmitted by the eNB (SIB) and forwarded to the OOC state 3 UE via PD2DSCH by CP UE relay UEs that are in the coverage of the cell. A (contention-based) network controlled resource pool is signaled by PD2DSCH. - State 4: UE4 is out of coverage and does not receive PD2DSCH from other UEs in the coverage of the cell. In this state, also referred to as State 4 OOC, the transmitting UE selects resources to be used for data transmission from a preconfigured resource pool.

[0060] The reason for distinguishing between state 3 OOC and state 4 OOC is mainly to avoid strong interference that may occur between D2D transmissions from out-of-coverage devices and legacy E-UTRA transmissions. Typically, D2D enabled UEs have a resource pool for D2D SA and data transmissions to use while out-of-coverage. If these out-of-coverage UEs transmit on these pre-configured resource pools near the cell border, interference between D2D transmissions and in-coverage legacy transmissions may adversely affect the communication within the cell. If in-coverage D2D enabled UEs forward the D2D resource pool configuration to those out-of-coverage devices near the cell border, the out-of-coverage UEs will restrict their transmissions to the resources specified by the eNodeB and therefore interference with in-coverage legacy transmissions will be minimized. Thus, RAN1 introduces a mechanism by which in-coverage UEs forward resource pool information and other D2D related configuration to those devices just outside the coverage area (state 3 IE).

[0061] The PD2DSCH (Physical D2D Synchronization Channel) is used to convey this information about in-coverage D2D resource pools to neighboring UEs in the network, thereby coordinating neighboring resource pools in the network.

[0062] D2D Discovery ProSe direct discovery is defined as a procedure used by a ProSe enabled UE to discover other ProSe enabled UEs in its vicinity using E-UTRA direct radio signals over PC5. Figure 8 shows a schematic of the PC5 interface for device-to-device direct discovery.

[0063] The upper layers handle the announcement of discovery information and the authorization of monitoring. For this purpose, the UEs need to exchange certain signals, called "discovery signals". By periodically checking for discovery signals, the UE maintains a list of nearby UEs to establish a communication link when necessary. Discovery signals should be reliably detected even in low signal-to-noise ratio (SNR) environments. Resources for discovery signals should be allocated to allow them to be transmitted periodically.

[0064] There are two types of ProSe direct discovery: open and restricted. Open is when no explicit permission is required from the UE being discovered, while restricted discovery occurs only with explicit permission from the UE being discovered.

[0065] ProSe Direct Discovery may be a standalone service enabler that can use information from a discovered UE for specific applications in a UE that is authorized to use this information, such as, for example, "find a taxi nearby," "find me a coffee shop," etc. Additionally, depending on the information obtained, ProSe Direct Discovery can be used for subsequent operations, such as for subsequent ProSe Direct communication.

[0066] ProSe Direct Discovery Model The following model for ProSe direct discovery is defined in section 5.3 of the non-patent document 6, which is incorporated herein by reference, and all its subsections.

[0067] Model A "I am here" This model defines two roles for a ProSe-enabled UE participating in ProSe direct discovery. Announcing UE: This UE announces certain information that can be used by nearby UEs that it has permission to discover. Monitoring UE: A UE that monitors certain information of interest in the vicinity of announcing UEs.

[0068] In this model, an announcing UE broadcasts discovery messages at a predefined discovery interval, and monitoring UEs interested in these messages read them and process them. Because an announcing UE broadcasts information about itself, e.g., its ProSe application code, in the discovery message, this model is sometimes referred to as "I am here".

[0069] Model B ("who is there?" / "are you there?") This model defines two roles for a ProSe-enabled UE participating in ProSe direct discovery. - Discoverer UE: This UE sends a request containing specific information about what it is interested in discovering. - Discoveree UE: A UE that receives this request message can respond with some information related to the discoverer's request.

[0070] The discoverer UE sends information of other UEs that may receive a response, for example the information may be about the group that can respond and ProSe application identity information for the members of the group, so this may be referred to as "who is there / are you there".

[0071] The content of discovery information is transparent to the AS (access layer), and no distinction is made between the AS in the ProSe direct discovery model and the type of ProSe direct discovery. The ProSe protocol ensures that only valid discovery information is delivered to the AS for announcement.

[0072] The UE may participate in advertisement and monitoring of discovery information in both RRC_IDLE and RRC_CONNECTED states by eNB configuration. The UE advertises and monitors its discovery information subject to half-duplex constraints.

[0073] Discovery Resource Allocation D2D communication can be either network controlled, where the operator manages the switching between direct transmission (D2D) and traditional cellular links, or the direct link is managed by the device without operator control. D2D allows combining infrastructure mode and ad-hoc communication.

[0074] Generally, device discovery is required periodically. Furthermore, D2D devices utilize a discovery message signaling protocol to perform device discovery. For example, one D2D enabled UE can transmit its discovery message, and another D2D enabled UE can receive this discovery message and use this information to establish a direct communication link. The advantage of a hybrid network is that a network entity such as an eNB can additionally assist in sending or configuring discovery messages when D2D devices are also within the communication range of the network infrastructure. The eNB's coordination / control in sending or configuring discovery messages is also important to ensure that D2D messages do not cause interference with cellular traffic controlled by the eNB. In addition, in-coverage devices can assist with ad-hoc discovery protocols even if some of the devices are outside the network coverage range.

[0075] For the purposes of defining the terms used further herein, at least two types of discovery procedures are defined: UE autonomous resource selection (later referred to as type 1): a resource allocation procedure in which resources for announcing discovery information are allocated in a non-UE specific manner, which is further characterized by: --The eNB provides the UE with a resource pool configuration used for announcing discovery information. The configuration can be signaled, for example, in a SIB. The UE autonomously selects radio resources from the indicated resource pool and announces discovery information. --The UE may announce discovery information on randomly selected discovery resources during each discovery period. - Scheduled resource allocation (later referred to as type 2): A resource allocation procedure in which resources for announcing discovery information are allocated specifically per UE, which is further characterized by: --A UE in RRC_CONNECTED can request resources for notification of discovery information from an eNB via RRC. The eNB allocates resources via RRC. --Resources are allocated within a resource pool configured for monitoring in the UE.

[0076] For a UE that is RRC_IDLE, the eNB may choose one of the following options: The eNB may provide a type 1 resource pool for discovery information announcement in the SIB. UEs authorized for ProSe direct discovery use these resources for discovery information announcement in RRC_IDLE. -The eNB may indicate in the SIB that the eNB supports D2D but does not provide resources for discovery information announcement. The UE needs to enter the RRC connected state to request D2D resources for discovery information announcement.

[0077] For a UE that is RRC_CONNECTED: A UE that is authorized to perform ProSe direct discovery announcement indicates to the eNB that the UE wishes to perform D2D discovery announcement. -The eNB verifies whether the UE is authorized for ProSe direct discovery announcement using the UE context received from the MME. The eNB may be configured to use a type 1 resource pool or dedicated type 2 resources (or no resources) for discovery information announcement via dedicated RRC signaling. -Resources allocated by the eNB are valid until a) the eNB deconfigures the resources via RRC signaling or b) the UE enters IDLE. A receiving UE that is RRC_IDLE and RRC_CONNECTED, upon authorization, monitors both Type 1 and Type 2 discovery resource pools. The eNB provides the resource pool configuration used for discovery information monitoring in the SIB. The SIB may also include discovery resources used for announcements in neighboring cells.

[0078] Wireless Protocol Architecture for ProSe Direct Discovery Figure 9 shows a schematic of the radio protocol stack (access stratum) for ProSe direct discovery, where the access stratum protocol consists of only MAC and PHY. The AS layer performs the following functions:

[0079] -Interface with upper layers (ProSe protocol): The MAC layer receives discovery messages from the upper layers (ProSe protocol). The IP layer is not used to send discovery messages. - Scheduling: The MAC layer determines the radio resources to be used for advertising discovery messages received from upper layers. Discovery PDU Generation: The MAC layer constructs a MAC PDU carrying the discovery message and sends the MAC PDU to the physical layer for transmission on the determined radio resource. No MAC header is added.

[0080] At the UE, the RRC protocol informs the MAC of the discovery resource pool. RRC also informs the MAC of the allocated type 2B resources for transmission. No MAC header is required. The MAC header for discovery does not contain any fields based on which filtering for L2 can be performed. Discovery message filtering at the MAC level is not expected to save processing or power compared to performing filtering at the upper layer based on the ProSe UE and / or Prose application ID. The MAC receiver forwards all received discovery messages to the upper layer. The MAC delivers only correctly received messages to the upper layer. It is assumed that L1 indicates to the MAC whether a discovery message was received correctly or not. It is assumed that the upper layer ensures that only valid discovery information is delivered to the access stratum.

[0081] ProSe UE-Network Relay The UE may also support functions and procedures such as operating as a ProSe UE-Network Relay, such that remote UEs communicate with the ProSe UE-Network Relay via the PC5 reference point. The ProSe UE-Network Relay operation will be specified in 3GPP Release 13. So far, only initial agreements have been made in the 3GPP RAN Working Group, some of which can be found, for example, in 3GPP RAN Working Group 3.0, 3GPP RAN Working Group 3.0, 3GPP RAN Working Group 3.0, 3GPP RAN Working Group 3.0, 3GPP RAN Working Group 3.1, 3GPP RAN Working Group 3.2, 3GPP RAN Working Group 3.3, 3GPP RAN Working Group 3.4, 3GPP RAN Working Group 3.5, 3GPP RAN Working Group 3.6, 3GPP RAN Working Group 3.7, 3GPP RAN Working Group 3.8, 3GPP RAN Working Group 3.9, 3GPP RAN Working Group 3.1, 3GPP RAN Working Group 3.2, 3GPP RAN Working Group 3.3, 3GPP RAN Working Group 3.4, 3GPP RAN Working Group 3.5, 3GPP RAN Working Group 3.5, 3GPP RAN Working Group 3.6, 3GPP RAN Working Group 3.7, 3GPP RAN Working Group 3.8, 3GPP RAN Working Group 3.9, 3GPP RAN Working Group 3.1, 3GPP RAN Working Group 3.2, 3GPP RAN Working Group 3.3, 3GPP RAN Working Group 3.1, 3GPP RAN Working Group 3.2, 3GPP RAN Working Group 3.3, 3GPP RAN Working Group 3.4, 3GPP RAN Working Group 3.5, 3GPP RAN

[0082] - For ProSe UE-network relay discovery and ProSe relay (re)selection, it is possible to address both scenarios where the remote UE is in coverage and out of coverage. -Relay UEs will always be in coverage: the eNB at radio level controls whether a UE can act as a relay or not, while it remains to be determined whether the network control is per relay UE, per cell (broadcast setting), or both, or in some other manner. When a remote UE is in coverage for relay discovery purposes, monitoring and transmission resources for discovery can be provided by the eNB, for example using Release 12 mechanisms (broadcast for idle mode and dedicated signaling for connected mode). The remote UE can decide when to start monitoring. When a remote UE is out of coverage, the monitoring and transmission resources for discovery and communication (actual data transfer) can be provided, for example, by pre-configuration, i.e. by specification / operator configuration (e.g. in the USIM), so that the UE knows exactly which resources to actually use.

[0083] ProSe UE-Network Relay (Re)Selection -The remote UE can take radio level measurements of the PC5 radio link quality into account for the ProSe UE-Network relay selection procedure. For the case when the remote UE is out of coverage, the radio level measurements can be used by the remote UE together with other higher layer criteria to perform relay selection. For the case where the remote UE is out of coverage, the criteria for reselection are based on PC5 measurements (RSRP or other RAN1 agreed measurements) and higher layer criteria. Relay reselection can be triggered by the remote UE. It remains to be determined whether and how these measurements (PC5 measurements) are used for the case when the remote UE is in coverage (e.g., the measurements could be used by the UE to perform a similar selection as in the out-of-coverage case or could be reported to the eNB).

[0084] The ProSe UE-Network Relay may use Layer 3 packet forwarding, e.g., for UE-Network Relay discovery and ProSe direct discovery, control information between ProSe UEs may be exchanged over the PC5 reference point.

[0085] A ProSe enabled UE will also support the exchange of ProSe control information between another ProSe enabled UE and the ProSe function via the PC3 reference point. In the case of ProSe UE-Network Relay, the remote UE sends this control information via the PC5 user plane to be relayed towards the ProSe function via the LTE-Uu interface.

[0086] The ProSe UE-Network Relay entity provides functionality to support connectivity for "unicast" services for remote UEs that are not in the coverage area of ​​an eNB, i.e., are not connected to an E-UTRAN. Figure 10 illustrates a ProSe UE-Network Relay scenario. The ProSe UE-Network Relay should relay unicast traffic (UL and / or DL) between the remote UE and the network. The ProSe UE-Network Relay should provide a general functionality to be able to relay any type of traffic related to public safety communications.

[0087] The one-to-one direct communication between the remote UE and the ProSe UE-network relay has the following characteristics: -Communication over the PC5 reference point is connectionless. - ProSe bearers are bidirectional: IP packets passed to the radio layer on a given ProSe bearer will be sent by the physical layer with the associated L2 destination address. IP packets sent from the radio layer on the same ProSe bearer will be received over the air addressed to the same L2 destination. The ProSe UE-network relay may include the following functions. - To enable a remote UE to discover a nearby ProSe UE-Network Relay, ProSe Direct Discovery according to Model A or Model B can be used. - ProSe Direct Discovery that can be used to enable a remote UE to discover the L2 address of a ProSe UE-Network Relay to be used by the remote UE for IP address allocation and user plane traffic corresponding to a particular PDN connection supported by the ProSe UE-Network Relay. - Operate as an "announced" or "discovered" UE on a PC5 reference point supporting direct discovery. - UE-ProSe UE-Network Relay acts as a default router for remote UEs forwarding IP packets between point-to-point links and the corresponding PDN connections. - Process Router Solicitation and Router Advertisement messages as defined in IETF RFC4861. -Acts as a DHCPv4 server and a stateless DHCPv6 relay agent. -When IPv4 is used, it acts as a NAT replacing the locally assigned IPv4 address of a remote UE with its own. - Map the L2 link ID used by the remote UE as the destination Layer 2 ID to the corresponding PDN connection supported by the ProSe UE-network relay. The user plane protocol architecture of ProSe UE-network relay is shown in FIG.

[0088] ProSe UE-Network Relay Discovery As previously described for normal Release 12 direct discovery between two ProSe UEs, both Model A and Model B discovery are supported, where Model A uses a single discovery protocol message (UE-Network Relay Discovery Announcement) and Model B uses two discovery protocol messages (UE-Network Relay Discovery Request and UE-Network Relay Discovery Response). More details regarding relay discovery can be found in Section 6 of 3GPP TS 2.0, which is incorporated herein by reference.

[0089] The following parameters are common to all of UE-Network Relay Discovery, Group Member Discovery, and UE-UE Relay Discovery. - Message type: Announcement (Model A) or Solicitation / Response (Model B), Relay Discovery Additional Information (Model A). - Discovery Type: Indicates whether this is UE-Network Relay Discovery, Group Member Discovery, or UE-UE Relay Discovery.

[0090] The following parameters are used in the UE-Network Relay Discovery Announcement message (Model A): - ProSe Relay UE ID: A link layer identifier used for direct communication and associated with the PDN connection established by the ProSe UE-Network Relay. -Announcer info: Provides information about the user making the announcement. Relay Service Code: A parameter that identifies the connection service that the ProSe UE-network relay provides to the public safety application. The relay service code is configured for advertisement in the ProSe UE-network relay and maps to a specific APN to which they provide a connection in the ProSe UE-network relay. In addition, the relay service code also identifies the authorized users that the ProSe UE-network relay provides services to, and can select, for example, related security policies or information required for authentication and authorization between the remote UE and the ProSe UE-network relay (for example, the relay service code of a relay for only police personnel will be different from the relay service code of a relay for only firefighters, even if they are potentially given a connection to the same APN, for example, to support Internet access). -Radio Layer Information: Radio layer information to assist the remote UE in selecting an appropriate UE-network relay, including information about the radio conditions between the eNB and the UE-network relay.

[0091] The following parameters are used in the UE-Network Relay Discovery Solicitation message (Model B): -Discoverer Information: Provides information about the discoverer user. -Relay Service Code: Information about the connection that the discoverer UE is interested in. The relay service code is set in the ProSe remote UE that is interested in the associated connection service. -ProSe UE ID: Link layer identifier of the discoverer used for direct communication (Model B)

[0092] The following parameters are used in the UE-Network Relay Discovery Response message (Model B): - ProSe Relay UE ID: A link layer identifier used for direct communication and associated with the PDN connection established by the ProSe UE-Network Relay. -Recipient Information: Provides information about the recipient. -Radio Layer Information: Radio layer information to assist the remote UE in selecting an appropriate UE-network relay, including information about the radio conditions between the eNB and the UE-network relay.

[0093] ProSe UE-ProSe direct communication via network relay The UE-Network Relay functionality will be specified based on the evolution of the ProSe functionality already documented in 3GPP TS 2.0.

[0094] A ProSe UE-network relay capable UE may attach to the network (if not already connected) and connect to a PDN connection that enables the necessary relay traffic, or may need to connect to an additional PDN connection to provide relay traffic for remote UEs. PDN connections that support UE-network relay should be used only for remote ProSe UE relay traffic. Figure 12 shows direct communication via ProSe UE-network relay.

[0095] 1. The ProSe UE-Network Relay performs an initial E-UTRAN attach (if not already attached) and / or establishes a PDN connection for the relay (if no suitable PDN connection exists yet for this relay). In case of IPv6, the ProSe UE-Network Relay obtains an IPv6 prefix from the network via a prefix delegation function as defined in 3GPP TS 2011-01-13. 2. The remote UE performs ProSe UE-Network Relay discovery using Model A or Model B discovery, the details of which are described above. 3. The remote UE uses the received relay selection information to select a ProSe UE-network relay and then establishes a connection for point-to-point communication as described above with reference to FIG. 4. When IPv6 is used on PC5, the remote IE performs IPv6 stateless address autoconfiguration, where the remote UE should send a Router Solicitation message (step 4a) to the network using the Layer 2 ID of the relay as the destination Layer 2 ID to solicit a Router Advertisement message (step 4b) as specified in IETF RFC4862. The Router Advertisement message should include the assigned IPv6 prefix. After receiving the Router Advertisement message, the remote UE constructs the entire IPv6 address via IPv6 stateless address autoconfiguration according to IETF RFC4862. However, the remote UE should not use any identifiers defined in 3GPP TS 21.0.12 as a basis for generating the interface identifier. For privacy reasons, the remote UE can change the interface identifier used to generate the entire IPv6 address as defined in 3GPP TS 21.0.13 without involving the network. The remote UE should use the autoconfigured IPv6 address while sending packets. 5. When IPv4 is used on PC5, the remote UE uses DHCPv4. The remote UE should send a DHCPv4 DISCOVER (step 5a) message using the Layer 2 ID of the relay as the destination Layer 2 ID. The ProSe UE-Network Relay acting as a DHCPv4 server sends a DHCPv4 SOLICIT (step 5b) with the assigned remote UE IPv4 address. When the remote UE receives the lease request, the UE sends a DHCP REQUEST message containing the received IPv4 address (step 5c). The ProSe UE-Network Relay acting as a DHCPv4 server sends a DHCPACK message to the remote UE containing the lease period and any other configuration information that the client may have requested (step 5d). When the DHCPACK message is received, the remote UE completes the TCP / IP configuration process.

[0096] As explained above, 3GPP introduces ProSe relay functionality, including relay discovery and relay direct communication, as a major work item. The currently defined mechanisms for ProSe relay are rather inefficient. Other mechanisms, such as how and when a relay-capable ProSe UE actually starts to act as a relay, i.e., to provide relay services in a radio cell, have not been agreed upon at all. [Prior art documents] [Non-patent literature]

[0097] [Non-Patent Document 1] 3GPP TS 36.211, "Evolved Universal Terrestrial Radio Access (E-UTRA); Physical Channels and Modulation, version 12.6.9 [Non-Patent Document 2] 3GPP TR 36.843, version 12.0.1 [Non-Patent Document 3] 3GPP TR 23.713, v1.4.0 [Non-Patent Document 4] 3GPP 36.300, version 13.3.0 [Non-Patent Document 5] 3GPP, TS 36.212, version 12.4.0 [Non-Patent Document 6] 3GPP, TS23.303, version 13.0.0 [Non-Patent Document 7] 3GPP, TR23.713, version 1.4.0 [Non-Patent Document 8] TS 25.321, version v12.2.0 [Non-Patent Document 9] TS 36.331, version 12.6.0 [Non-Patent Document 10] TS 36.304, version 12.5.0 [Non-Patent Document 11] TS 23.401 [Non-Patent Document 12] TS 23.003 [Non-Patent Document 13] TS 23.221 Summary of the Invention [Problem to be solved by the invention]

[0098] Non-limiting exemplary embodiments provide an improved method for enabling a relay functionality of a relay user equipment. The independent claims provide non-limiting exemplary embodiments. Advantageous embodiments are the subject of the dependent claims. [Means for solving the problem]

[0099] According to some aspects described herein, the enablement of the relay functionality in relay-capable user equipment is improved. To discuss these aspects, the following assumptions are made. In particular, it is assumed that the associated relay user equipment is capable of performing direct communication with other remote user equipment (i.e., via a direct side link connection). Furthermore, the term "relay-capable user equipment" should be understood in the sense that the user equipment supports a relay functionality for which it is capable of acting as a relay for one or more remote user equipments, respectively, which ultimately involves performing a relay discovery procedure and, when selected by a remote user equipment, establishing a direct side link connection via which said remote user equipment is connected. Communications between one or more remote user equipments and a radio base station (to which the relay user equipment is connected) are relayed by the relay user equipment via the established direct side link connection.

[0100] According to the first aspect, the activation of the relay functionality of the relay user equipment is controlled as follows: The radio base station first determines whether a further relay is actually required in the radio cell. For example, in order to be able to determine whether a further relay is required, the radio base station can monitor the number of relay user equipments in the radio cell with the relay functionality activated and / or the number of remote user equipments in the radio cell that may need to be served by a relay in order to remain connected by the radio base station and thus be able to further use the services provided by the communication network (e.g. backbone and radio network). For this determination, the radio base station can further take into account the number of remote user equipments performing public safety services in the radio cell. Alternatively, the ProSe function may determine whether a further relay is actually required in the radio cell of the radio base station and thus provide a corresponding indication to the radio base station, which then determines based on this indication that a further relay is actually required and continues with the relay activation.

[0101] As a result, when the radio base station determines that an additional relay is required in a radio cell, it broadcasts a corresponding broadcast message in the radio cell to indicate this, i.e. that an additional relay is required in the radio cell and that relay-capable user equipments (which do not yet have their relay functionality enabled) should initiate a relay activation procedure as described below. In other words, the broadcast message from the radio base station can be considered as a relay activation trigger for the corresponding relay user equipments (i.e. relay-capable user equipments which do not have relay functionality enabled) to initiate a relay activation procedure in the relay user equipments in order to determine whether the relay functionality should be enabled or not.

[0102] Furthermore, the radio base station will select the persistence check value based on the number of further relays required in the radio cell. In particular, the relay activation procedure to be performed in the relay user equipment includes performing a corresponding persistence check (including generating a random value to be compared with the persistence check value) so as to limit the total number of relay user equipments that will actually activate the relay function in response to the trigger. By setting the persistence check value to an appropriate value, the radio base station can implicitly control the maximum number of relay user equipments that may eventually activate the relay function.

[0103] Furthermore, the relay activation procedure to be performed in the relay user equipment includes a further check, namely whether specific relay requirements defined in the radio cell for activating the relay functionality are fulfilled by the relay user equipment.

[0104] According to this first aspect, a relay user equipment is enabled to activate its relay functionality only if the persistence check is successful and the relay user equipment fulfills all necessary relay requirements defined for the radio cell. After activating its relay functionality, the relay user equipment can start with a relay discovery procedure, which includes transmitting a relay discovery message to announce its presence as a relay in the radio cell, thus allowing the enabled relay user equipment to be discovered by other remote user equipments, i.e. performing Model A or Model B discovery. Finally, if the relay is subsequently selected by the remote user equipment to act as a relay, a direct sidelink connection will be established between the relay user equipment and the remote user equipment, which can relay communications with the radio base station.

[0105] As mentioned above, the relay activation procedure to be performed in the relay user equipment according to the first aspect includes two checks, namely a persistence check based on a received persistence check value (threshold) and a relay requirements check. It should be noted that the order in which the two checks are performed is irrelevant to the overall functionality of the first aspect. For example, the two checks may be performed in parallel or successively, but advantageously the second check should be performed only when the first (preceding) check is successful.

[0106] A possible implementation of the persistence check performed in the relay user equipment according to the first aspect will now be described. A persistence check value is selected by the radio base station from a certain range of values ​​(e.g. between 0 and 1). The relay user equipment then generates a random value within this same value range. The persistence check value provided by the radio base station can be considered as a threshold to be compared with the generated random value to determine whether the persistence check is successful or not. In this connection, one alternative is to consider the persistence check value successful if the generated random value is less than or equal to the persistence check value threshold. Of course, alternatively, the persistence check may be considered successful if the generated random value is above the persistence check value threshold. In any case, by appropriately selecting the persistence check value (threshold), the radio base station controls the percentage of successful persistence checks performed by all relay user equipments (that perform this persistence check).

[0107] An exemplary variant of the first aspect also considers whether suitable radio resources are available in the relay user equipment for performing a subsequent relay discovery procedure if the relay functionality is indeed enabled. In particular, the relay user equipment additionally determines whether such radio resources are already configured and usable for performing the relay discovery procedure. If suitable radio resources are not available for use by the relay user equipment, a corresponding request to the radio base station can be performed by the relay user equipment, which can return a response message indicating whether and which radio resources are assigned to the relay user equipment for performing the relay discovery procedure. On the other hand, in the affirmative, such a request is not necessary. Advantageously, this determination on available radio resources can be performed after the two checks of the relay activation procedure (i.e., the persistence check and the relay requirements check) have been successfully completed, thereby avoiding unnecessarily requesting radio resources from the radio base station.

[0108] According to a further variant of the first aspect, the relay user equipment may still need to seek permission from the radio base station as to whether the relay function is allowed to be activated, even when the two checks of the relay activation procedure are successfully completed. In other words, after the two steps of the relay activation procedure are successfully completed by the relay user equipment, the relay user equipment should send a relay activation request message to the radio base station to request permission to activate the relay function from the radio base station. In response, the radio base station will decide as to grant or deny permission for each of the requesting relay user equipments, and finally send back a corresponding relay activation response message to the relay user equipment, granting or denying permission to activate the relay function in the relay user equipment. Therefore, the activation of the relay function in each of the relay user equipments will ultimately be controlled by the radio base station.

[0109] In a further improvement of this variant of the first aspect, the request of resources for the relay discovery procedure can be combined with a step of requesting permission to activate the relay functionality from the radio base station. In particular, these two steps may be performed simultaneously, for example by transmitting a relay activation request message that not only requests permission to activate the relay functionality, but also requests radio resources for a possible relay discovery procedure to be performed subsequently. Similarly, the relay activation response message transmitted from the radio base station may not only include the permission or refusal to activate the relay functionality, but may also include the radio resources to be used for the relay discovery procedure (to be performed if the relay functionality is actually activated). Advantageously, the permission of radio resources, i.e. the presence of corresponding information on the granted radio resources in the relay activation response message, can already be interpreted by the receiving relay user equipment as permission to activate its relay functionality (i.e. it would be disadvantageous to reject the permission to activate the relay functionality and at the same time grant radio resources for the relay discovery procedure). Similarly, although it may be possible to make the request for permission separately from the request for radio resources in the relay activation request message, the request for radio resources for the relay discovery procedure may already be interpreted by the radio base station as the relay user equipment requesting permission to activate its relay functionality.

[0110] A further variant of the first aspect distinguishes between relay user equipment in a connected state and relay user equipment in an idle state. The relay user equipment determines which state it is in and if in an idle state, a transition to a connected state may be performed by the relay user equipment. There may be several reasons why it is advantageous for the relay user equipment to transition to a connected state. One particular reason is that, although relay discovery can be performed even when in an idle state, an enabled relay function, i.e. to act as a relay for remote UEs, requires the relay user equipment to be in a connected state in order to be able to relay communications with a radio base station. Furthermore, given the previous variant, in which radio resources may first need to be requested from the radio base station and / or the radio base station may need to be asked for permission to enable the relay function, the transmission of such a request may only be performed by the relay user equipment when in a connected state (i.e. when actively connected to the radio base station). It should be noted that the transition to a connected state may include performing a connection request procedure so that a connection with the radio base station is established. In relation to the above, it may also be advantageous to indicate as a connectivity factor that the transition is caused by a relay activation procedure (i.e. the need to request radio resources to perform a relay discovery procedure and / or the need to seek permission from the radio base station to activate the relay functionality).

[0111] In a further variant of the first aspect, the broadcast message may be extended by including additional relay requirements to be met by prospective relay user equipments before they are allowed to activate their relay functionality. An indication that additional relays are required may be given separately from the information on the relay requirements in the broadcast message, but advantageously the reception of a broadcast message including additional relay requirements may be interpreted implicitly by the relay user equipment as an indication that additional relays are indeed required in the radio cell, and thus as a trigger to initiate a relay activation procedure in the relay user equipment.

[0112] Additionally or alternatively, the broadcast message may be extended by including information on the radio resources to be used by the relay user equipment for performing a relay discovery procedure after activating the relay functionality. Here again, the indication that an additional relay is required may be given separately from the information on the radio resources to be used for the relay discovery procedure in the broadcast message, but advantageously the reception of a broadcast message including information on the radio resources for the relay discovery procedure may be interpreted implicitly by the relay user equipment as an indication that an additional relay is indeed required in the radio cell and thus as a trigger to initiate a relay activation procedure in the relay user equipment.

[0113] As mentioned above, the relay activation procedure implemented by the relay user equipment comprises a step of determining whether the relay user equipment satisfies an additional relay requirement, which may exemplarily be one of: a minimum and / or maximum threshold for a radio link quality of the link between the relay user equipment and the radio base station, such as a reference signal received power RSRP or a reference signal received quality RSRQ, a maximum threshold for a mobility level of the relay user equipment, and a minimum threshold for a charging level of the relay user equipment.

[0114] Accordingly, in one general first aspect, the techniques disclosed herein feature a method for enabling a relay function of a relay user equipment in a mobile communication network. The relay user equipment is capable of performing direct communication via a direct side link connection with one or more remote user equipments, respectively. The relay user equipment is located in a radio cell controlled by a radio base station in the mobile communication network and supports a relay function to enable the relay user equipment to act as a relay for one or more remote user equipments, respectively, to relay communication between the one or more remote user equipments and the radio base station via the direct side link connection. The radio base station determines whether an additional relay is actually needed in the radio cell. If it is determined that an additional relay is needed in the radio cell, the radio base station selects a persistence check value and transmits a broadcast message in the radio cell. The broadcast message indicates at least that an additional relay is needed in the radio cell and includes the selected persistence check value. Upon receiving the broadcast message, the relay user equipment activates its relay functionality if it determines that the relay requirements for activating its relay functionality in the radio cell are fulfilled by the relay user equipment and if a persistence check performed by the relay user equipment based on the received persistence check value is successful.

[0115] Accordingly, in one general first aspect, the techniques disclosed herein feature a relay user equipment in a mobile communication network for enabling a relay function. The relay user equipment is capable of performing direct communication via a direct side link connection with one or more remote user equipments, respectively. The relay user equipment is located in a radio cell controlled by a radio base station in the mobile communication network and supports a relay function for enabling the relay user equipment to act as a relay for one or more remote user equipments, respectively, to relay communication between the one or more remote user equipments and the radio base station via the direct side link connection. A receiver of the relay user equipment receives a broadcast message from the radio base station indicating that an additional relay is required in the radio cell and including a persistence check value selected by the radio base station. Upon receiving the broadcast message, a processor of the relay user equipment enables the relay function of the relay user equipment if the relay user equipment determines that the relay requirement for enabling its relay function in the radio cell is satisfied by the relay user equipment and if a persistence check performed by the relay user equipment based on the received persistence check value is successful.

[0116] Accordingly, in one general first aspect, the techniques disclosed herein feature a radio base station for participating in the activation of a relay function of a relay user equipment in a mobile communication network. The relay user equipment is capable of performing direct communication via a direct side link connection with one or more remote user equipments, respectively. The relay user equipment is located in a radio cell controlled by the radio base station in the mobile communication network and supports a relay function to enable the relay user equipment to act as a relay for one or more remote user equipments, respectively, to relay communication between the one or more remote user equipments and the radio base station via the direct side link connection. A processor of the radio base station determines whether an additional relay is actually required in the radio cell. The processor selects a persistence check value within a certain value range. A transmitter of the radio base station transmits to one or more remote user equipments in the radio cell relay requirements to be satisfied before activating the relay function. The transmitter transmits a broadcast message in the radio cell if the processor determines that an additional relay is required, the broadcast message indicating at least that an additional relay is required in the radio cell and including the selected persistence check value. The broadcast message indicates to one or more relay user equipments in the radio cell to activate the relay functionality if the relay user equipment successfully performs a persistence check based on the persistence check value and if the relay user equipment satisfies the relay requirements.

[0117] Additional benefits and advantages of the disclosed embodiments will become apparent from the specification and drawings, in which the benefits and / or advantages may be provided individually by the various embodiments and features of the disclosure in the specification and drawings, and not all need be provided to obtain one or more thereof.

[0118] These general and specific aspects may be implemented using systems, methods, and computer programs, and any combination of systems, methods, and computer programs. Exemplary embodiments are described in detail below with reference to the accompanying figures and drawings. [Brief description of the drawings]

[0119] [Figure 1] FIG. 1 illustrates an example architecture of a 3GPP LTE system. [Diagram 2] FIG. 1 illustrates an example downlink resource grid for a downlink slot of a subframe as defined for 3GPP LTE (Release 8 / 9). [Diagram 3] FIG. 1 shows a schematic diagram of how a Layer 2 link is established over PC5 for ProSe communication. [Figure 4] Diagram showing transmit / receive resource usage for overlay (LTE) and underlay (D2D) systems [Diagram 5] FIG. 1 illustrates a scheduling assignment and D2D data transmission for two UEs. [Figure 6] FIG. 1 illustrates an exemplary architecture model of ProSe for a non-roaming scenario. [Figure 7] FIG. 1 illustrates cell coverage for four different states that a D2D UE may be associated with. [Figure 8] Schematic diagram of the PC5 interface for direct discovery between devices. [Figure 9] Schematic diagram of the radio protocol stack for ProSe direct discovery. [Figure 10] Diagram showing ProSe UE-Network Relay scenario [Figure 11] Diagram showing the user plane protocol architecture of ProSe UE-Network Relay [Figure 12]Diagram showing direct communication via ProSe UE-Network Relay for relay discovery and one-to-one communication establishment [Figure 13] FIG. 1 is an alternative flow diagram of relay UE behavior according to an exemplary implementation of the first embodiment; [Figure 14] FIG. 1 is an alternative flow diagram of relay UE behavior according to an exemplary implementation of the first embodiment; [Figure 15] FIG. 13 is a flow diagram of relay UE behavior according to a further implementation of the first embodiment, in which the relay UE additionally needs to request permission from the radio base station to activate the relay function. [Figure 16] FIG. 13 is a flow diagram of a relay UE behavior according to a further implementation of the first embodiment, in which the relay UE additionally determines whether radio resources are already available for the relay discovery procedure and responds accordingly. [Figure 17] FIG. 11 is a flow diagram of relay UE behavior according to another implementation of the first embodiment. [Figure 18] FIG. 2 is a flow diagram of the relay UE behavior according to another implementation of the first embodiment, where the procedure takes into account whether the relay UE is idle or connected and responds accordingly. [Figure 19] FIG. 13 is a flow diagram of relay UE behavior according to another implementation of the first embodiment, where the ProSe function allows an additional level of control for initiating relay activation. [Figure 20] A flow diagram of relay UE behavior according to another implementation of the first embodiment, in which the ProSe function can additionally complete relay activation. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0120] A mobile station or node or user terminal or equipment is a physical entity in a communication network. A node may have several functional entities. A functional entity refers to a software or hardware module that implements and / or provides a given set of functions to other functional entities of the node or the network. A node may have one or more interfaces that attach the node to a communication facility or medium through which the node may communicate. Similarly, a network entity may have logical interfaces that attach a functional entity to a communication facility or medium through which the node may communicate with other functional entities or corresponding nodes.

[0121] A "relay user equipment" as used in the claims and the present application should be broadly understood as referring to a user equipment capable of acting as a relay for another user equipment (referred to as a "remote user equipment"). It also includes functionality supporting direct communication transmission directly between two user equipments (see D2D or ProSe below). According to one embodiment, the relay user equipment should support relay functionality as defined for 3GPP LTE-A and as described in the Background section. In the above context, the term "remote user equipment" should only indicate the role of a user equipment as a peer of a relay user equipment, i.e. with which the relay expects to establish direct communication.

[0122] The term "radio resource" as used in the claims and this application together should be understood broadly to refer to physical radio resources, such as time-frequency resources.

[0123] The term "direct communication transmission" as used in the claims and the present application together should be broadly understood as a transmission directly between two user equipments, i.e., without going through a radio base station (e.g., eNB). Accordingly, the direct communication transmission is performed via a "direct sidelink connection", which is the term used for a connection established directly between two user equipments. For example, in 3GPP, the terms D2D (device-to-device) communication, or ProSe communication, or sidelink communication are used. The term "direct sidelink connection" as used in the claims and the present application together should be broadly understood, and can be understood, as a PC5 interface, as described in the Background section, in the context of 3GPP.

[0124] The term "relay function" as used in the claims and the present application should be broadly understood as a function that acts as a relay for user equipment. In one exemplary embodiment, the relay function is a function currently being standardized in a 3GPP work item, as described in detail in the Background section.

[0125] The term "persistence check" as used in the claims and in this application should be understood broadly as a simple determination based on a comparison of a randomly generated value against a given threshold to determine whether the persistence check is successful or not. By appropriately selecting the threshold, it is possible to (approximately) control what percentage of persistence checks are successful.

[0126] 3GPP is currently in the process of introducing relay functionality for ProSe-enabled user equipment. Although some initial agreements (some of which have already been described in detail in the Background section) have already been achieved, agreement on some important issues related to the ProSe relay functionality has not yet been achieved. One important issue related to the above is the challenge of how and when a ProSe relay-enabled UE actually starts to become a relay UE, i.e., enables its relay functionality to enable it to act as a relay for other ProSe remote UEs. It should be noted that a relay UE that has been enabled for relay functionality will perform a relay discovery procedure to enable its discovery for remote UEs in its vicinity, which includes sending relay discovery messages according to Model A (periodic) or Model B (when requested by remote UEs).

[0127] One possible way of controlling relay activation for a relay UE includes determining whether a relay-capable UE meets certain prerequisites for operating as a relay in a certain radio cell. More specifically, it is assumed that a UE is generally capable of operating as a relay, but that certain (relay) requirements are defined that should additionally be met before it is enabled (e.g., by an eNB) to operate as a relay in a radio cell. For example, the quality of the link between the relay UE and the eNodeB should be good enough, i.e., higher than a minimum threshold, so that it is guaranteed that the relay-capable UE can act as a relay to relay additional traffic coming from remote UEs. In another example, the speed at which a potential relay UE is moving should also be limited to a certain maximum value, since a remote UE connected to a relay UE moving at high speed is more likely to quickly go out of the transmission range of the relay UE and thus need to select a new relay. Another possible relay requirement may refer to the charge level of the relay user equipment, which should not fall below a certain minimum threshold in order to guarantee service continuity for remote UEs that select a certain relay UE to establish a connection with the network.

[0128] However, it should be noted that using additionally defined relay requirements in a radio cell may have the drawback that too many (unnecessary) UEs will activate their relay functionality in the radio cell. As mentioned above, activation of the relay functionality involves the initiation of a relay discovery procedure, which results in the transmission of a relay discovery message (e.g. periodically in model A). This may unnecessarily increase contention and interference on relay discovery resources, and therefore may result in delayed relay selection, as a remote UE may need to try two or more possible relay devices in succession to receive a connection before successfully connecting to a relay. In that case too, the communication link quality on the PC5 interface will be affected, as many relays may be trying to access the same set of resources. This, combined with poor PC5 link quality, will result in a poor user experience due to poor Uu quality (which is why the UE is looking for a relay in the first place).

[0129] Moreover, another possibility for controlling relay activation is to use dedicated signaling in this context. In particular, when a relay-capable UE is interested in acting as a relay, it sends a corresponding dedicated signaling message to the eNodeB, which can then decide as to whether the requesting relay UE should be activated as a relay or not. It can then send a corresponding response message back to the relay UE to grant or deny permission to activate the relay function. Exchanging dedicated signaling with the eNodeB has the advantage that the eNodeB can explicitly control the number of relay UEs that have the relay function enabled, but it also entails some drawbacks. For example, it is not possible to use dedicated signaling for relay-capable UEs in idle state, since dedicated signaling can only be sent to the eNodeB when it is in connected state, i.e. when there is a valid connection with the eNodeB through which the dedicated signaling message is sent. Therefore, idle state UEs would have to transition to connected state even if they are not allowed to activate their relay function later, which would waste resources and battery. Furthermore, this approach leaves open the possibility that strictly speaking, a relay-capable UE should send a dedicated signaling to the eNodeB to request to act as a relay. For example, sending a dedicated signaling message to the eNodeB may increase the load at the eNodeB and may congest the Uu link unnecessarily, especially when many relay-capable UEs are available in the radio cell and would repeatedly ask the eNodeB for permission to activate the relay function. In addition, an idle UE that has transitioned to a connected state to request permission needs to remain in the connected state until the RRC connection is explicitly released by the eNB, for example by sending a connection release message.Furthermore, by remaining in a connected state in the hope of acting as a relay for the remote UE, the relay UE may wait a long time before the remote UE actually selects it to act as a relay. It would be better for the relay UE to have a chance to act as a relay while in idle mode itself.

[0130] Another possible solution for relay activation is to combine both approaches mentioned above, i.e., to use dedicated signaling to check additional relay requirements and to get permission from the eNB. However, this combined approach may also result in too many (unnecessary) requests being sent to the eNB, which may congest the Uu link and increase the processing load at the eNB. Furthermore, this combined approach may also result in idle UEs unnecessarily establishing an RRC connection (i.e., transitioning to connected state) when they are later refused by the eNodeB to activate their relay functions when further relays are not actually required. Moreover, this combined approach does not specify at what point in time a dedicated signaling request should be sent to the eNodeB, i.e., it is repeated as long as the relay requirements are satisfied.

[0131] The following exemplary embodiments have been conceived by the inventors to alleviate one or more of the problems discussed above.

[0132] Particular implementations of the various embodiments should be implemented in the broad specifications as given by the 3GPP standards and partially described in the Background section, with certain key features added as described below accompanying the various embodiments. It should be noted that the embodiments can be advantageously used in mobile communication systems, such as, for example, the 3GPP LTE-A (Release 10 / 11 / 12 / 13) communication systems described in the Background section above, but the embodiments are not limited to use in this particular exemplary communication network.

[0133] These descriptions should not be understood as limiting the scope of the present disclosure, but as merely examples of embodiments for better understanding of the present disclosure. Those skilled in the art should recognize that the general principles of the present disclosure as described in the claims can be applied in different scenarios and in ways not explicitly described herein. For the purpose of illustration, however, some assumptions are made that should not limit the scope of the following embodiments.

[0134] Furthermore, as mentioned above, the following embodiments can be implemented within a 3GPP LTE-A (Release 12 / 13) environment. The various embodiments mainly provide a mechanism for the relay activation procedure performed by the relay UE, such that other functionality (i.e. functionality that is not changed by the various embodiments) can remain exactly the same as described in the Background section or can be modified without any impact on the various embodiments. This is true for example for the relay discovery procedure that is initiated after the relay functionality is enabled, and the exact procedure for establishing a direct sidelink connection in which relaying takes place, and how data is relayed between the remote user equipment and the relay user equipment. A scenario may be assumed in which user equipments are enabled to perform ProSe communication, i.e., direct D2D transmission directly between UEs without detouring via an eNodeB (ProSe enabled UEs). Furthermore, at least one of these (ProSe enabled) UEs in this scenario should support a relay functionality, e.g. as described in the Background section for a specific implementation in Release 13 of the 3GPP standard. In other words, this relay UE (located in a radio cell and connected to a corresponding radio base station controlling the radio cell) should be able to act as a relay for other (ProSe enabled) UEs (remote UEs), thereby enabling these remote UEs to connect to an eNB via a relay.

[0135] First embodiment In the following, a first embodiment for solving the above problems will be described in detail. Different implementations of the first embodiment will be described in detail below. According to the first embodiment, the enabling of the relay function in a relay-capable UE is improved.

[0136] A general implementation of the first aspect is described in relation to the flow diagram of FIG. 13, which illustrates relay UE behavior with respect to a relay activation procedure to be performed in the relay UE to determine whether the relay functionality should be activated or not.

[0137] The eNodeB manages when the relay-capable UEs in its radio cell should initiate their respective relay activation procedures, and thus can avoid unnecessary relay activation in its radio cell. In relation to the above, the eNodeB should mainly trigger a relay activation procedure when one or more additional relays are needed in the radio cell. On the other hand, if no more relays are needed in the radio cell, the eNodeB does not trigger the relay UEs to initiate a relay activation procedure in the radio cell. To this end, when the eNodeB determines that an additional relay is needed, it preferably transmits in its radio cell an appropriate broadcast message to be received by all in-coverage relay-capable UEs (e.g. also UEs at the outer edge of the eNodeB's coverage area, thereby significantly expanding the coverage area by activating the relay function). This broadcast message should contain a trigger for initiating a relay activation procedure or be interpreted as such by the receiving relay UEs. For example, the broadcast message may contain an explicit relay trigger, e.g. a one-bit flag.

[0138] Furthermore, the eNB selects an appropriate persistence check value (threshold value), e.g. a specific value being selected depending on the number of relays required in the radio cell. By using the persistence check in the relay activation procedure performed in each relay UE (explained in detail later), the eNodeB can control the number of relay UEs that will eventually activate the relay function. This persistence check value is also included in the broadcast message broadcasted by the eNodeB in the radio cell. Advantageously, instead of giving a separate indication in the broadcast message that more relays are required (i.e. a separate indication that triggers the start of the relay activation procedure in the relay UEs), the presence of the persistence check value in the broadcast message may already be considered implicitly as this indication that more relays are required.

[0139] In response, from the point of view of one of these relay-capable UEs in the radio cell (i.e. see FIG. 13), a corresponding broadcast message is received with a relay activation trigger (to initiate execution of the relay activation procedure) and a persistence check value. Reception of the broadcast message triggers a relay activation procedure in the relay UE, which includes the following tests to determine whether the relay functionality should actually be activated:

[0140] The first check has already been mentioned above, namely the persistence check performed by the relay UE based on the persistence check value received in the broadcast message. The persistence check should be performed by the relay UE and only if it is successful activation of the relay functionality should be possible. If it is not successful, the relay UE may terminate the relay activation procedure and can continue to monitor for another broadcast message that would newly trigger the relay activation procedure in the relay UE.

[0141] Another check to be performed by the relay UE during the relay activation procedure is whether the additional relay requirements, defined as necessary conditions in the radio cell in which it acts as a relay, are fulfilled by the relay UE. Again, only when the additional relay requirements are fulfilled should the activation of the relay functionality be possible. If the relay requirements are not fulfilled, the relay UE may terminate the relay activation procedure and continue to monitor for another broadcast message that would newly trigger the relay activation procedure in the relay UE.

[0142] As is evident from Fig. 13, once both checks have been successfully completed by the relay UE, the relay UE can start with a relay discovery procedure to activate its relay functionality and thus announce its presence in the cell. The relay discovery procedure can be performed by the relay UE, for example according to Model A or Model B as described in the Background section. Accordingly, the activated relay UE can be discovered and selected by a remote UE that needs to maintain or initiate a connection with an eNodeB via the relay. Further details regarding the subsequent procedures to be performed after the relay functionality is activated, such as the mentioned relay discovery procedure, relay selection procedure and relaying procedure, are omitted as such here, and instead reference is made to the Background section for possible exemplary implementations of these procedures.

[0143] The relay activation according to the first embodiment just described involves the eNodeB explicitly determining when a relay is actually needed in order to subsequently send a broadcast message in response. This allows triggering the relay activation procedure in the relay UE only when it is actually needed. The improved relay activation of the first embodiment therefore avoids initiating a relay activation procedure in unnecessary relay UEs, thereby saving processing on the relay UE side. Furthermore, by implementing a persistence check in the relay activation of the first embodiment, a further level of control of the eNodeB is provided to limit the number of relay UEs that will activate the relay function (among all relay UEs in the radio cell that initiate the relay activation procedure, i.e. those that preferably do not already have their relay function activated). In response, only the (approximately) necessary number of additional relays will be activated, thereby not congesting the relay discovery resources (which are then used by the relay UEs after their activation) with unnecessary relay discovery messages. This particular approach of the relay activation according to the first embodiment also avoids including an additional request for authorization by the eNodeB, thereby avoiding further messages being sent to the responsible eNodeB over the Uu link. Accordingly, the load at the eNodeB is not increased and congestion on the Uu link is avoided, while at the same time allowing the eNodeB to control (at least) the number of relay UEs that will eventually activate the relay function.

[0144] In the following further different alternative implementations of the first embodiment are described.

[0145] As explained for the implementation of the first embodiment according to Fig. 13 (and also part of the remaining implementations according to the remaining figures), the relay UE determines whether it meets the specific relay requirements defined in the radio cell. These specific relay requirements may be defined, for example, by the eNodeB or another responsible entity in the core network like the MME, or by the ProSe function itself. In this case, corresponding information about the specific relay requirements may be broadcasted in the radio cell by the eNodeB, for example in an appropriate SIB (System Information Block). Alternatively, the requirements may be hard-coded in the UE, or pre-configured by the operator, for example in the USIM, or configured by higher level signaling, including NAS (Non-Access Stratum) signaling, or provided by the eNB in ​​a dedicated signaling message to the relay UE if the relay UE was previously in connected state.

[0146] The specific relay requirements may vary from radio cell to radio cell and may be more or less strict depending on the current situation. Some possible relay requirements, which can be utilized separately or in combination, are presented below. However, these parameters should not be considered as something that must be used as relay requirements, but as examples. For example, the quality of the radio link (i.e., Uu link) between the relay UE and the eNodeB should not fall below a certain limit to ensure efficient relaying / forwarding by the relay UE. On the other hand, considering that a relay UE with too good Uu quality may be far away from the cell edge or from a coverage hole, thereby making such relay UE of no interest to the radio cell for acting as a relay, the Uu link quality may additionally need to remain below a certain threshold. Another possible relay requirement to be met by the prospective relay UE may relate to the mobility of the relay UE. For example, a relay UE moving at high speed is more likely to go out of range of remote UEs, thus forcing these remote UEs to select another relay UE. Accordingly, an upper limit of the mobility / movement of the relay UE can be defined as a relay requirement to be met by any relay UE that wants to act as a relay in a radio cell. A further possible relay requirement refers to the charge level of the relay UE, which should preferably be above a minimum threshold to ensure that the relay UE is able to function as a relay for a sufficiently long time. For example, if a relay UE with limited remaining battery is selected as a relay, packets going towards remote UEs may quickly deplete its battery power. This is not only detrimental for the remote UE, which has to select a new relay, but also for the normal operation of the relay UE, which will terminate faster.

[0147] Other relay requirements refer, for example, to overload situations at the relay UE that would prevent or seriously impede the relay UE from acting as a relay for a remote UE. The functional definition of "prevent or seriously impede the relay from acting as a relay" should not be interpreted narrowly as being unable for the relay user equipment to act as a relay for a single further remote user equipment. Rather, overload situations can be flexibly defined for the relay user equipment, for example, by specifying certain limitations that are understood to ensure efficient operation of the relay user equipment. Overload can refer to either hardware or software components of the relay user equipment, such as processor, memory, ports, logical channel IDs, available bandwidth in uplink / downlink, etc. Overload is characterized as being temporary, since it may change rapidly.

[0148] Accordingly, a set of one or more of these or other relay requirements may need to be checked by any relay UE during the relay activation procedure of an implementation of the first embodiment.

[0149] For the particular implementation of Fig. 13, it is assumed that the two checks are essentially performed in parallel. Meanwhile, Fig. 14 shows a different implementation of the first embodiment, where these two determinations are performed consecutively, and the particular order is irrelevant to the functionality of the present disclosure. In the exemplary implementation of Fig. 14, a simple persistence check is performed first, and only if this persistence check is successful, the relay UE continues to check whether the relay requirements are met. Therefore, if the persistence check has already failed, the relay activation procedure can be stopped immediately, since there is no need to further check whether the relay requirements are met, thereby saving processing in the relay UE.

[0150] Similarly, although not shown in the figures, the relay UE may first check whether the relay requirements are met and may continue to perform a persistence check only if the relay requirements are met. Thus, if the relay requirements check has already failed, the relay activation procedure may end since there is no need to perform further persistence checks, thereby saving processing at the relay UE.

[0151] Moreover, as mentioned above, the relay UE performs a persistence check during the relay activation procedure based on a persistence check value given by the eNodeB in a broadcast message. The persistence check value, which can be considered as a threshold against which a random value generated thereafter is compared to pass or fail the persistence check, is determined at the eNodeB, for example, based on the number of relay UEs that the eNodeB wants to be activated. In one embodiment, the eNodeB can determine the number of relay UEs required in the cell based on a number of factors including feedback from ProSe functions that the eNB can receive through its own interface or through a core network element such as the MME, or purely based on an OAM (Network Operation and Management) setting from the network stating that, for example, a certain number of relays are required per square kilometer, or purely based on its own estimation from some statistical calculation regarding the number of UEs running public safety services in the cell (revealed from the bearers of the CQI classes served by the eNB) and / or the number of relay UEs typically required per a certain number of UEs running public safety services, or the eNodeB decision regarding the number of relay UEs required in the cell may be based purely on the UEs' reporting of their requirements for relay services. Another example may be that the UEs' reporting of their requirements for relay services may be based on in-coverage public safety UEs experiencing poor radio quality (on the Uu interface), and the eNodeB extrapolating this number to include the possible number of out-of-coverage UEs.

[0152] Persistence checks are already used in prior art 3GPP standards, but for other purposes. For example, 3GPP RFC3211 defines a persistence value Pi that is used to control when a UE is allowed to access the RACH channel when a previous transmission was not deemed successful. By distributing the access in the time domain, the number of UEs accessing the RNC at any given time is tightly controlled by the RNC by adjusting the value of the persistence value Pi.

[0153] According to a variant of the first embodiment, the persistence check may be performed in the same way. Thus, a range of values ​​(for example between 0 and 1) is defined within which the persistence check value is selected by the eNodeB. In response, the relay UE generates a random value within this same value range during the relay activation procedure. To pass the persistence check, the randomly generated value of the relay UE is compared with the persistence check value selected by the eNodeB. One possibility would be to define that the persistence check is successful if the randomly generated value is less than or equal to the persistence check value given by the eNodeB, or vice versa if the randomly generated value is greater than the persistence check value given by the eNodeB. For example, by selecting an appropriate persistence check value, the eNodeB can control the rate at which the persistence check is successful or not successful. Assuming that the persistence check is successful when the randomly generated value is less than or equal to the persistence check value, the eNodeB can limit the successful persistence checks to a low percentage by setting the persistence check threshold to a low value, e.g., 0.1; correspondingly, by setting the persistence check threshold to a moderate value such as 0.5, the eNodeB can control that only about half of the persistence checks are successful. Accordingly, the persistence check provides a simple and effective mechanism that leaves the eNodeB some control over the number of relay UEs that will / can activate their relay functionality, without having to force the relay UEs to directly ask for permission from the eNodeB via dedicated signaling.

[0154] Nevertheless, while the preceding embodiment of the first embodiment does not require a dedicated request for authorization from the eNodeB, an alternative embodiment of the first embodiment includes such an additional level of control. In particular, the flow diagram of Fig. 15 illustrates such an exemplary implementation based on the previously described implementation of Fig. 14. In addition to the persistence check and the relay requirement check, the relay activation procedure according to this alternative implementation of the first embodiment illustrated in Fig. 15 additionally includes the relay UE requesting authorization from the eNodeB as to whether it is allowed to activate its relay function. This additional request for authorization can be performed, for example, after both checks of the relay activation procedure are successfully completed, as is assumed for the implementation illustrated in Fig. 15. Thus, the eNodeB will then have the opportunity to specifically reject or grant authorization for each of the requesting relay user equipments one by one. For example, this is advantageous in scenarios where the eNodeB does not know the number of relay-capable UEs in its radio cell, but the eNodeB still wants to keep the number of UEs with relay function enabled below a certain limit.

[0155] In response, after sending a corresponding message (e.g. referred to as Relay Activation Request message) to the radio base station, the relay UE will wait for and eventually receive a corresponding response message (e.g. referred to as Relay Activation Response message) containing a response from the radio base station, i.e. whether the relay UE is enabled to activate its relay functionality or not. According to the content of this response message, the relay UE thus activates or does not activate its relay functionality. In one embodiment, both the request and the response messages can be designed either as RRC messages (e.g. SidelinkUEInformation in Non-Patent Document 9, see below for details) or as MAC CE (Control Element) messages with a designated LCID (Logical Channel ID) for the request and response messages, respectively.

[0156] This relay activation request message may not only carry a request for permission to activate the relay functionality of the relay UE (and a request for radio resources, see implementation of the first embodiment below), but may also include further information as described below.

[0157] For example, the message may indicate that the purpose for which permission is being sought is to act as a relay.

[0158] Furthermore, this relay activation request message sent from the relay UE to the eNodeB may include information regarding one or more services that can be provided by the relay UE to the remote user equipment. For example, the services may be public safety services or non-public safety services. In any case, by providing such information regarding the provided services, the eNodeB can determine the priority associated with the respective one or more provided services and can therefore use such information as a basis for the decision of whether to allow or not allow the relay UE to activate its relay function. As an example, a potential relay UE may indicate an intention to provide medical emergency personnel for voice-specific calls in a flat layout, and the eNodeB, having already accepted and acknowledged five such relays, already knows that it cannot tolerate more relays in its cell (without causing interference) and that five relays are already sufficient, based on its knowledge, for example, from nearby services, whereby the eNodeB rejects the new request to become a relay.

[0159] Similarly, the relay UE may include group identity information for one or more services that may be provided by the relay UE to remote user equipment, which makes it possible to identify the group to which each of the one or more provided services belongs.

[0160] According to a specific implementation in the context of the 3GPP standard in Releases 12 and 13, the SidelinkUEInformation message (already defined in 3GPP TS 2010 / 02211, section 6.2.2, incorporated herein by reference) can be reused in this context. Accordingly, the SidelinkUEInformation message can be extended with additional information elements to allow indicating some additional information as explained above, for example: -The purpose of the permission request is to act as a relay, The relay is one in which the request for resources refers to resources for a relay discovery procedure and not for, e.g., a commercial discovery procedure or even for Release 12 D2D (direct) communication between two ProSe UEs, and therefore the corresponding additional information element allows for simultaneously requesting resources for the relay discovery procedure and for a Release 12 direct discovery procedure and / or Release 12 D2D communication.

[0161] A corresponding example of an extended definition of the SidelinkUEInformation message is given below.

[0162] SidelinkUEInformation Message [Table 1] [Table 2]

[0163] According to a further implementation of the first embodiment, the relay activation procedure also takes into account whether radio resources are already available to perform a relay discovery procedure (which is initiated following activation of the relay function). In this connection, it is noted that in standardization, there is still no final agreement on when and how radio resources to be used for relay discovery are defined and provided to the relay UE. One possible implementation is to broadcast a suitable relay discovery resource pool, which provides radio resources to be used in connection with the relay discovery procedure to be performed by the relay UE. As a result, a specific radio resource can then be automatically selected from such a suitable relay discovery resource pool by the relay UE, or a specific radio resource (from within this relay discovery resource pool) needs to be scheduled by the eNodeB (upon request by the relay UE). A relay UE in a radio cell can be configured to be enabled to automatically select radio resources from such pool, or it may need to request dedicated radio resources from the eNodeB first. In any case, the relay UE determines whether radio resources are already configured and available for use by the relay UE for the relay discovery procedure to be performed upon activation of its relay functionality. If suitable radio resources are then in fact available to the relay UE, the relay UE can continue with the relay activation procedure (e.g., activate the relay functionality). On the other hand, if suitable radio resources are not available to the relay UE for the relay discovery procedure, the relay UE can request such radio resources from the radio base station, which will respond in response by receiving and allocating suitable radio resources for relay discovery. Once suitable radio resources are allocated, the relay UE can continue with the relay activation procedure (e.g., activate the relay functionality).

[0164] As mentioned above, one possible implementation of the method for requesting radio resources is to use the SidelinkUEInformation message. In this message the relay UE can signal that resources for the relay discovery procedure are requested. Furthermore, the SidelinkUEInformation message should be extended by an information element for requesting resources for the relay discovery procedure, so that in the same SidelinkUEInformation message the relay UE can additionally request resources for commercial discovery and / or Release 12 D2D communication. A possible exemplary implementation of the SidelinkUEInformation message is given below.

[0165] SidelinkUEInformation Message [Table 3] [Table 4]

[0166] One particular exemplary embodiment of a method for checking and requesting radio resources is shown in Figure 16, which is based on the previous embodiment discussed in relation to Figure 15, which additionally requires the relay UE to first seek permission from the eNodeB before activating the relay functionality. However, it should be noted that alternatively, this particular embodiment is also possible by extending the relay activation procedure as described in relation to Figures 13 and 14, without an additional request for permission being performed by the relay UE, i.e., by the above-mentioned additional step, where the relay UE determines whether radio resources are needed or not, and if so, requests and receives permission for radio resources from the eNodeB.

[0167] A corresponding extension of the exemplary embodiment described in relation to Fig. 14 is illustrated by the flow diagram of Fig. 17, with minor modifications. As already described in relation to Fig. 16, the relay UE additionally determines whether radio resources are already available for the relay discovery procedure, and if such resources are not available, the relay UE continues such a request towards the eNodeB. Depending on whether radio resources are allocated or not, the relay UE then continues the activation of the relay functionality (if radio resources are indeed allocated) or terminates the relay activation procedure (if radio resources are not allocated). Therefore, in this advantageous embodiment, the request for resources can be reused to request permission for the relay functionality to be activated or not. In particular, the request for radio resources transmitted by the relay UE to the radio base station can be considered as an implicit request for permission, since the eNodeB will have the opportunity to grant or deny permission to a particular relay UE to activate the relay functionality by allocating or not allocating radio resources in response to the radio resource request. Accordingly, when the eNodeB determines that the requesting relay UE should not activate its relay functionality, it can simply not allocate resources to the relay UE (either by not sending a response message back to the relay UE or by responding with corresponding information that no radio resources are allocated), which is then interpreted by the relay UE as the eNodeB not giving permission to activate the relay functionality. On the other hand, when the eNodeB determines that the requesting relay UE should indeed activate its relay functionality, by providing corresponding information about the allocated radio resources, the eNodeB implicitly authorizes the relay UE to activate the relay functionality.

[0168] In the embodiment according to Fig. 17, the additional step for determining and requesting radio resources is provided after the two checks (relay request check and persistence check), since this avoids further messages being sent to the radio base station over the Uu link if one of the two checks fails. Nevertheless, in theory, these steps for determining and requesting radio resources may alternatively be provided before the persistence check and / or relay requirement check, such that the persistence check and / or relay requirement check are performed only after the radio resources are available (by making them available before or after they are requested).

[0169] A further variant of the first embodiment is described in relation to FIG. 18, which additionally takes into account whether the relay UE is in RRC idle or RRC connected state. To explain this additional improvement, it is exemplarily assumed that the relay activation procedure also includes a step in which the relay UE determines whether resources are available for the relay discovery procedure as previously described. However, it should be noted that this additional improvement of taking into account the idle / connected state of the UE can also be included in the relay activation procedure independently (i.e. without the need to have a radio resource determination). Generally, the relay UE can be in RRC connected or idle state when performing the relay discovery procedure, but since the relay UE needs to forward and receive data on the Uu link for relaying, when selected by the remote UE to act as a relay, the relay UE will need to transition to a connected state. Thus, for example, the relay UE may perform the relay discovery procedure in RRC idle state, but will subsequently transition to an RRC connected state when selected to be a relay for the remote UE. Nevertheless, when relaying eMBMS traffic to a remote UE, the relaying may also be performed by the relay UE that is RRC idle. Moreover, for an advantageous implementation of the first embodiment involving direct dedicated signaling with the radio base station (e.g. to request resources and / or to request permission to activate the relay functionality), the relay UE should be in the RRC connected state to be able to perform this dedicated signaling. Therefore, in an advantageous implementation of the first embodiment, a relay UE in the idle state will first transition to the connected state before continuing / terminating the relay activation procedure. For said purpose, the relay UE may first determine a particular RRC state, i.e. whether it is in the idle state or in the connected state, and if the relay UE is in the idle state, it will need to perform a corresponding procedure to transition to the connected state before continuing the relay activation procedure (in the particular example of Fig. 18, to request radio resources from the radio base station by dedicated signaling).

[0170] It should be noted that the step of transitioning from the idle state to the connected state can be performed, for example, by an RRC connection procedure. A specific implementation of such a procedure for transitioning from the RRC idle state to the RRC connected state has already been standardized in 3GPP, for example the RRC connection establishment procedure defined by 3GPP TS 2010-010661, incorporated herein by reference, in clause 5.3.3. In summary, after the random access is performed by the relay UE, the relay UE sends an RRC connection request message (RRCConnectionRequest message) to the eNodeB, which then responds by sending an RRC connection response message (RRCConnectionSetup) containing the necessary parameters to establish an RRC connection between the relay UE and the eNodeB, which further includes a UE context based on a UE-specific RRC level identity called C-RNTI. The UE is further identified on the Uu link based on this C-RNTI, which is kept in both the UE and the eNodeB until the RRC connection is released. Please note that once a relay UE transitions to connected state, it typically remains in connected state until the connection is released by the eNodeB or until the UE has to transition to idle mode after a radio link failure where re-establishment of the RRC connection is not possible (clause 5.3.7 of non-patent document 9).

[0171] Therefore, especially for implementations of the first embodiment where dedicated signaling is required to successfully complete the relay activation procedure, relay UEs in idle state may also be enabled to successfully complete the relay activation procedure.

[0172] According to a further variant of the first embodiment, the ProSe function in the network will also control the relay activation, as described below in connection with the exemplary illustration of Fig. 19. Specifically, the ProSe function sends a corresponding Relay Start message as a first trigger to the relay UE, which then starts monitoring the corresponding radio resource over which the broadcast message is transmitted by the eNodeB. Specifically, in order to maintain some network control over the relay situation in the respective radio cell, the ProSe function (e.g., additionally in consultation with the ProSe application server) can determine that a particular radio cell should provide relaying (even though further control may be up to the eNodeB as explained before) when, for example, some special public safety scenario is notified in a particular geographical area / cell. Thus, by sending a corresponding Relay Start message to the relay-capable UE in the radio cell, the ProSe function triggers the relay UE to broadcast a message from the eNodeB to actually trigger the relay activation procedure in the relay UE (e.g., as defined in section 5.2 of 3GPP TS 2010-010363, incorporated herein by reference). Therefore, as is clear from FIG. 19, the relay UE will monitor and eventually receive the relay start message, in which case the relay UE will start monitoring the radio resources to receive the broadcast message from the eNodeB.

[0173] Alternatively or additionally, the ProSe function may send a similar message to the eNodeB to initiate relay activation through the eNodeB. The eNodeB then immediately concludes from the corresponding relay start message received from the ProSe function that further relaying is required and therefore sends the aforementioned broadcast message to the relay UEs in the radio cell. Alternatively, when the eNodeB receives such a relay start message from the ProSe function, it then determines whether further relaying is indeed required based on, for example, the number of remote UEs in the radio cell that have a poor radio link with the eNodeB and / or the number of remote UEs performing public safety services in the radio cell. To further explain, the eNodeB can determine the number of relay UEs required in the cell based on many possible factors including feedback from ProSe functions that the eNB can receive through its own interface or through core network elements such as the MME, or purely based on OAM settings from the network stating that a certain number of relays are required per square kilometer, or purely based on its own estimation from some statistical calculation regarding the number of UEs running PS services in the cell (revealed from the bearers of the CQI classes served by the eNB) and the number of relay UEs typically required per a certain number of UEs running PS services, or the eNodeB decision on the number of relay UEs required in the cell may be purely based on the UEs' reporting of their requirements for relay services. The last one, i.e., the UEs' reporting of their requirements for relay services, may be based on in-coverage public safety UEs experiencing poor radio quality (on the Uu interface) and the eNodeB estimating this number to include the possible number of out-of-coverage UEs. This determination may be performed by the eNodeB periodically after receiving the relay start message.

[0174] This determination by the eNodeB as to whether further relaying is required, just as described above, may also be performed in implementations of the first embodiment that do not include a relay initiation message exchange from the ProSe function, for example in the implementations described in relation to Figures 13 to 18 (and their corresponding variations), in which case the eNodeB also periodically determines whether further relaying is required.

[0175] Further advantages and an extended version of the implementation of the first embodiment as described in relation to Fig. 19 are described in relation to Fig. 20. As is clear from Fig. 20, an additional, namely a decision as to whether a relay stop message is received from the ProSe function, is introduced in the relay activation procedure. Contrary to the relay start message, the ProSe function (e.g. additionally in consultation with the ProSe application server) may decide that a particular radio cell should not provide any relaying any more and may therefore send a relay stop message in the radio cell accordingly. In response, if the relay UE receives such a relay stop message, the relay UE stops monitoring for broadcast messages from the eNodeB.

[0176] According to a further advantageous implementation of the first embodiment, the broadcast message is extended by further information useful for performing a relay activation procedure in the relay UE. As explained before, the broadcast message should include a persistence check value and a function as a trigger for the relay UE to initiate a relay activation procedure. In addition, the broadcast message may include further relay requirements that should be fulfilled in the radio cell and that are checked by the relay user equipment during the relay activation procedure. As mentioned before in a particular implementation of the first embodiment, the eNodeB may be the entity for determining the specific relay requirements for its cell and thus accordingly may include information on the relay requirements in the broadcast message transmitted in its radio cell. Advantageously, the presence of this information on the relay requirements in the broadcast message may be considered as an implicit indication that further relaying is required in the radio cell (i.e. as a trigger for initiating a relay activation procedure in the relay user equipment), whereby no separate indication is necessary in this connection.

[0177] Alternatively or additionally, according to further implementations of the first embodiment, the broadcast message may be extended with information on radio resources that can be used by the relay UE to perform a relay discovery procedure after activating its relay capability. For example, the information on radio resources provided by the eNodeB in the broadcast message may be the same as or similar to the previously mentioned relay discovery resource pool from which the user equipment can then autonomously select radio resources for performing, for example, relay discovery. On the other hand, assuming that the relay discovery resource pool information is already provided to the relay UE (e.g., via system information), this information on radio resources provided by the eNodeB in the broadcast message may refer to only a portion of the entire relay discovery resource pool. In any case, by already providing the corresponding radio resources in the broadcast message transmitted by the eNodeB, it is not necessary to further request radio resources later, for example, during the relay activation procedure (see, for example, Figures 16 and 17) as described in connection with some of the implementations of the first embodiment, in which the relay activation procedure includes a step of determining whether radio resources are already available for the relay discovery procedure or not. Advantageously, the presence of such information in the broadcast message can be considered as an implicit indication that an additional relay is required in the radio cell (i.e. as a trigger for initiating a relay activation procedure in the relay user equipment), whereby no separate indication in this regard is necessary.

[0178] A further advantageous implementation of the first embodiment provides an additional mechanism to disable the relay functionality when necessary, so that the relay UE does not continue to transmit relay discovery messages unnecessarily, thereby further draining its battery and congesting the corresponding relay discovery radio resources. Accordingly, for this implementation, it is assumed that the relay UE has already activated its relay functionality and may or may not be serving as a relay for other remote UEs. According to this implementation, the eNodeB can decide not to provide any relays in its radio cell anymore, or simply decide to reduce the number of relays in its radio cell. In any case, in this embodiment, a mechanism is provided to enable the eNodeB to disable all relay UEs or only specific relay UEs. In relation to the above, the eNodeB can use a corresponding relay disable command message that can either be broadcast in the radio cell or can be sent directly to the relevant relay UEs whose relay functionality should be disabled. More specifically, if an eNodeB wants to disable all relays in its radio cell, it may decide to broadcast a corresponding deactivation command to be received by all relay UEs in its radio cell, each of which will follow this command and disable the relay function when the relay function is enabled. On the other hand, the eNodeB may also use dedicated signaling with only one relay respectively to disable the relay function of said relay UEs. However, it should be noted that the eNodeB is not able to reach relay UEs in idle state by using dedicated signaling. In this case, the eNodeB may alternatively or additionally use broadcast signaling to disable the relay function of only relay UEs in idle state, especially those with the relay function enabled.Relay UEs in idle state receive the broadcast signaling with this special indication and in response disable their relay functionality (if enabled). As a further example, the broadcast message may further use a persistence check mechanism as described above to disable only a portion of the entire enabled relay set.

[0179] Alternatively, relay deactivation may also be initiated by the relay UE, for example when any relay UE stops acting as a relay for a certain period of time or when the ProSe function informs the UE to stop being a relay. In this case, the relay UE may send a corresponding relay deactivation request message to the eNodeB, which may then decide whether the relay UE should actually deactivate its relay functionality or not. In response, the eNodeB may send a response message back to the relay UE with or without a corresponding deactivation command.

[0180] In a particular implementation according to a 3GPP environment, the RRCConnectionReconfiguration message can be reused to serve as a relay disable command.

[0181] Second embodiment In the following, a second embodiment is presented that addresses the following problems: In particular, the current standardization of the ProSe relay function does not specify when the remote user equipment starts and stops transmitting data over the PC5 interface. In other words, the current 3GPP standardization does not reach a specific agreement on when the remote UE should start transmitting / receiving data over a relay connection instead of over a direct Uu link with the eNodeB. It is also unclear when the remote UE should switch back to the Uu link.

[0182] It should be noted that in general, the remote UE should prefer the Uu link over the PC5 link. Therefore, the relay operation should be started only when the Uu link is very weak / unsustainable or inefficient, and / or stopped when the remote UE can again be served directly by the eNodeB over the Uu link. This is because dynamic scheduling based on various measurement reports, CSI reports, etc. is possible and performed on the Uu interface, but not for the PC5 link.

[0183] For the purposes of discussing the second embodiment, it is assumed that the remote UE eventually selects a relay UE from among one or more possible discovered (e.g., discovered by performing relay discovery as described in the Background section) relay UEs. Accordingly, this also involves establishing a corresponding direct connection with the relay UE through which the communication can then be relayed. In particular, such a direct connection can be established, for example, by establishing a Layer 2 link between the relay UE and the remote UE, as described in the Background section.

[0184] Now, it is important to determine when the actual data switch (to the PC5 interface) should take place (after the relay UE has been selected by the remote UE and the corresponding direct connection between the relay UE and the remote UE has been established). There are several options. For example, the remote UE can autonomously decide whether and when it should start transmitting / receiving data over the PC5 link in the first place. This autonomous decision can be based on several different options, including Uu and / or PC5 link quality, the required transmit power on each link, and other similar considerations.

[0185] For example, the remote UE may start transmitting data over the PC5 link when the corresponding Uu link quality between the remote UE and the radio base station falls below a certain configured threshold. As a further alternative, the remote UE may be configured to start transmitting data over the PC5 link immediately after successfully establishing a Layer 2 link with the relay UE.

[0186] In any case, the remote UE may inform the eNodeB of the path switch to PC5, which may enable the eNodeB to release and de-establish existing data bearers so that the remote UE's communications now continue to be relayed to the remote UE via the relay UE.

[0187] Alternatively, the remote UE may directly start using a communication link with the selected relay UE without prior notification to the eNodeB, for example by sending unacknowledged data packets (e.g., PDCP SDUs) to the relay UE. In response, the relay UE then notifies the eNodeB, which starts sending downlink (PDCP) unacknowledged data packets to the remote UE via the selected relay user equipment. Knowledge of "which" remote UE can be conveyed to the eNB via the relay using the C-RNTI that was assigned to the UE on the Uu link that was in use immediately before the UE transitioned to PC5.

[0188] In general, all data switches (Uu to PC5 and PC5 to Uu) performed by remote UEs (and relay UEs) should be notified from the access stratum to the application layer, since the application layer in this case, e.g., a proximity function, may need to map the radio network layout (e.g., cell and tracking area IDs) to its own infrastructure.

[0189] Further solutions are provided for successfully transitioning the UE's connection from the PC5 link back to the Uu link. In this context, it is assumed here that the relay UE is acting as a relay for the remote UE, whereby the remote UE's communication is relayed between the eNodeB and the remote UE via the relay UE. According to one solution, a handover-like procedure may be used to transition the remote user back to the Uu link. Specifically, the remote UE may send normal measurement reports to the eNodeB via the relay connection. For example, old measurement configurations received when previously connected to the eNodeB via the Uu link may be maintained after the PC5 data switch and thus may be used for measurements on the Uu link even when the remote user equipment is on the PC5 link. A corresponding handover message (such as the RRCConnectionReconfiguration message with MobilityControlInfo of 3GPP TS 2010-010363, incorporated herein by reference) may be sent by the eNodeB to the remote UE via the relay UE. In this particular case, the Uu link to be switched back may belong to the same old (source) cell or to any other neighboring cell. However, this solution has the problem that the UE and eNodeB retain the Uu context (including configuration) and that RRC message signaling over PC5 is disadvantageous since it is assumed that the link is only used to carry higher layer data (e.g. application data) and, in this regard, lower layer signaling transmission over PC5 may be avoided since the same complexity would need to be supported for maintaining an RRC connection over the Uu interface.

[0190] On the other hand, as mentioned above, the remote UE can switch back to using the Uu link (instead of the PC5 interface link) when the Uu link quality is good enough. In the above case, advantageously, an RRC connection establishment procedure can be performed by the remote UE, indicating as the cause of the connection establishment that the remote UE wants to transition from the PC5 interface to the Uu interface. According to an exemplary implementation in a 3GPP standard environment, the RRC connection establishment procedure according to 3GPP RFC3286 (clause 5.3.3, incorporated herein by reference) can be reused.

[0191] In order for the remote UE to properly determine when the Uu link is good again, the remote UE may perform certain radio link measurements, such as those including, for example, RSRP and / or RSRQ, and / or path loss information, etc. A corresponding minimum threshold that the Uu link must meet to be determined to be good enough to switch again may be defined for each respective radio link measurement. For example, each of the predefined thresholds may be set by the eNodeB, and information corresponding to the thresholds may be provided to the remote UE while the remote UE is still accessible via the Uu link (i.e., before performing a data switch to the PC5 link).

[0192] According to an alternative implementation of the second embodiment, the remote UE uses cell selection criteria (defined in 3GPP TS 2010-0106662) to determine when Uu is good enough to initiate data switching back to the Uu link. In particular, 3GPP TS 2010-0106662, which is incorporated herein by reference, defines in section 5.2.3.2 the cell selection criteria used to evaluate cells for the cell selection procedure described in section 5.2. The following is an excerpt from section 5.2.3.2 of 3GPP TS 2010-0106662:

[0193] The cell selection criterion S is satisfied when: Srxlev>0 and Squal>0 Where: Srxlev=Qrxlevmeas -(Q rxlevmin +Q rxlevminoffset )-Pcompensation-Qoffset temp Squal=Q qualmeas -(Q qualmin +Q qualminoffset )-Qoffset temp Where: [Table 5]

[0194] The signaled value Q rxlevminoffset and Q qualminoffset applies only when a cell is evaluated for cell selection as a result of a periodic search for a higher priority PLMN while normally camped in a VPLMN. During this periodic search for a higher priority PLMN, the UE may check the S criteria of the cell using stored parameter values ​​from different cells of this higher priority PLMN.

[0195] In response, the remote UE may reuse this cell selection criteria to determine when the Uu link is again good enough to switch back to this link.

[0196] According to a further improvement, a new monitoring behavior is provided to the remote UE. Specifically, since the remote UE is assumed to be running only public safety applications, it may selectively only need to monitor certain discovery resource pools that are specifically defined to be used for relay discovery for these public safety applications. Therefore, there is no need for the remote UE to monitor other discovery resource pools, which can save battery.

[0197] Further embodiments According to a first aspect, a method is provided for activating a relay function of a relay user equipment in a mobile communication network. The relay user equipment is capable of performing direct communication via a direct side link connection with one or more remote user equipments, respectively. The relay user equipment is located in a radio cell controlled by a radio base station in the mobile communication network and supports a relay function to enable the relay user equipment to act as a relay for one or more remote user equipments, respectively, to relay communication between the one or more remote user equipments and the radio base station via the direct side link connection. The method includes the following steps: The radio base station determines whether a further relay is required in the radio cell. If it is determined that a further relay is required in the radio cell, the radio base station selects a persistence check value and transmits a broadcast message in the radio cell. The broadcast message indicates at least that a further relay is required in the radio cell and includes the selected persistence check value. The relay user equipment receives the broadcast message and thereafter activates its relay function if the relay user equipment determines that a relay requirement for activating its relay function in the radio cell is fulfilled by the relay user equipment and if a persistence check performed by the relay user equipment based on the received persistence check value is successful.

[0198] According to a second aspect provided in addition to the first aspect, the step of performing a persistence check by the relay user equipment includes the relay user equipment generating a random value within a certain value range and comparing the generated random value with a received persistence check value selected by the radio base station within the same value range to determine whether the persistence check is successful, e.g., if the generated random value is less than or equal to the received persistence check value, the persistence check is successful.

[0199] According to a third aspect provided in addition to the first or second aspect, the method may include a further step after receiving the broadcast message and before the step of activating the relay function. Specifically, the relay user equipment determines whether radio resources are already configured for the relay user equipment to perform a relay discovery procedure for announcing its presence as a relay. If radio resources are not already configured for the relay user equipment to perform the relay discovery procedure, the relay user equipment requests radio resources for performing the relay discovery procedure from the radio base station, and then receives information from the base station regarding whether and which radio resources are allocated for performing the relay discovery procedure.

[0200] According to a fourth aspect provided in addition to any of the first to third aspects, the method may include a further step after receiving the broadcast message and before the step of activating the relay function. Specifically, the relay user equipment transmits to the radio base station a relay activation request message requesting permission from the radio base station to activate the relay function of the relay user equipment. The relay user equipment receives from the radio base station a relay activation response message granting or denying permission for the relay user equipment to activate the relay function. Thereafter, if a relay activation response message granting permission to activate the relay function is received, a step of activating the relay function by the relay user equipment is performed.

[0201] According to a fifth aspect provided in addition to the third to fourth aspects, the step performed by the relay user equipment of requesting radio resources for performing a relay discovery procedure from the radio base station includes including the request for radio resources in a relay activation request message transmitted by the relay user equipment to the radio base station for requesting permission to activate its relay functionality from the radio base station. Furthermore, the step performed by the relay user equipment of receiving information from the base station regarding whether radio resources are allocated for performing a relay discovery procedure and which radio resources are allocated includes including the information in a relay activation response message transmitted by the radio base station for granting or refusing permission for the relay user equipment to activate its relay functionality. For example, the radio base station grants permission for the relay user equipment to activate its relay functionality by allocating radio resources to the relay user equipment for the relay discovery procedure and the radio base station denies permission for the relay user equipment to activate its relay functionality by not allocating radio resources to the relay user equipment for the relay discovery procedure.

[0202] According to a sixth aspect, which is provided in addition to this fourth or fifth aspect, the relay activation request message further comprises: 1) information on one or more services that can be provided by the relay user equipment to the remote user equipment, such as a public safety service or a non-public safety service, preferably enabling the radio base station to determine a priority associated with the one or more provided services; 2) group identity information of the one or more services that can be provided by the relay user equipment to the remote user equipment, the group identity information giving information on which group each of the one or more provided services belongs to; or 3) a request for radio resources for the relay user equipment to perform direct discovery for announcing its presence as a direct communication user equipment by transmitting a discovery message in the radio cell.

[0203] According to a seventh aspect provided in addition to any of the first to sixth aspects, the method further comprises the following steps after receiving the broadcast message and before the step of activating the relay functionality: The relay user equipment determines whether the relay user equipment is in an idle state or a connected state. If the relay user equipment is in an idle state, the relay user equipment transitions to a connected state to be able to request resources for performing a relay discovery procedure from the radio base station and / or to request permission from the radio base station to activate the relay functionality of the relay user equipment. For example, the step of the relay user equipment transitioning to the connected state includes performing, by the relay user equipment, a connection request procedure with the radio base station. The connection request procedure may indicate as an establishment cause the need to request radio resources for performing a relay discovery procedure and / or the need to seek permission to activate the relay functionality. In response, the radio base station determines whether to reject or grant the connection request based on the establishment cause. The establishment cause may be determined by the radio base station during the connection request procedure from a Radio Resource Control Protocol header of a message of the connection request procedure, or from a Medium Access Control Protocol header of a message of the connection request procedure, or from a random access preamble sent by the relay user equipment during the connection request procedure.

[0204] According to an eighth aspect provided in addition to any of the first to seventh aspects, the broadcast message transmitted by the radio base station in the radio cell further comprises information on relaying requirements to be fulfilled by the relay user equipment in the radio cell, for example an indication that further relaying is required is included in the broadcast message separately from the information on the relaying requirements or the relay user equipment determines that further relaying is required from the presence of the information on the relaying requirements in the broadcast message and / or from the presence of a persistence check value in the broadcast message.

[0205] According to a ninth aspect provided in addition to any of the first to eighth aspects, the broadcast message transmitted by the radio base station in the radio cell further comprises information on radio resources to be used by the relay user equipment for a relay discovery procedure for announcing its presence as a relay, for example an indication that a further relay is required is included in the broadcast message separately from the information on radio resources for the relay discovery procedure or the relay user equipment determines that a further relay is required from the presence of information on radio resources for the relay discovery procedure in the broadcast message and / or from the presence of a persistence check value in the broadcast message.

[0206] According to a tenth aspect provided in addition to any of the first to ninth aspects, the relay requirements include at least one of: 1) minimum and / or maximum thresholds for a radio link quality of a link between the relay user equipment and the radio base station, preferably the radio link quality being determined based on a reference signal received power RSRP and / or a reference signal received quality RSRQ; 2) a maximum threshold for a mobility level of the relay user equipment, such as a speed of the relay user equipment; and 3) a minimum threshold for a charge level of the relay user equipment.

[0207] According to an eleventh aspect provided in addition to any of the first to tenth aspects, when the relay functionality is enabled, the relay user equipment performs a relay discovery procedure for announcing its presence as a relay in the radio cell by transmitting relay discovery messages in the radio cell. Each of the relay discovery messages is transmitted either periodically or after reception of a relay request message from a remote user equipment requesting discovery of the relay user equipment. For example, the relay user equipment is selected to act as a relay for a first remote user equipment to relay communications, and a first direct side link connection is established between the relay user equipment and the first remote user equipment such that communications exchanged by the first remote user equipment with the radio base station are relayed between the relay user equipment and the first remote user equipment via the first direct side link connection.

[0208] According to a twelfth aspect, provided in addition to any of the first to eleventh aspects, it is assumed that the relay user equipment has its relay functionality enabled, in which case the method further comprises the following steps: the relay user equipment receives a relay disable command from the radio base station and in response disables its relay functionality; alternatively, the relay user equipment transmits a relay disable request message to the radio base station and then in response receives a relay disable response message from the radio base station instructing the relay user equipment to disable or not disable its relay functionality; in response, the relay user equipment disables its relay functionality if the relay disable response message instructs to disable the relay functionality.

[0209] According to a thirteenth aspect provided in addition to any of the first to twelfth aspects, the method includes the steps of: a relay user equipment receiving a relay start message from a proximity service function in a mobile communication network, and in response starting monitoring by the relay user equipment for reception of a broadcast message from a radio base station. For example, the method further includes the steps of: a relay user equipment receiving a relay stop message from the proximity service function, and in response stopping monitoring by the relay user equipment for reception of a broadcast message from the radio base station.

[0210] According to a fourteenth aspect provided in addition to any of the first to thirteenth aspects, the step of determining whether a further relay is required, performed by the radio base station, determines that a further relay is required if a relay start message is received from a proximity service function in the mobile communication network. Alternatively or additionally, the step of determining whether a further relay is required, performed by the radio base station, is based on a number of remote user equipments in the radio cell having poor radio links with the radio base station and / or a number of remote user equipments performing public safety services in the radio cell.

[0211] According to a fifteenth aspect, there is provided a relay user equipment in a mobile communication network for activating a relay function. The relay user equipment is capable of performing direct communication via a direct side link connection with one or more remote user equipments, respectively. The relay user equipment is located in a radio cell controlled by a radio base station in the mobile communication network and supports a relay function for enabling the relay user equipment to act as a relay for one or more remote user equipments, respectively, to relay communication between the one or more remote user equipments and the radio base station via the direct side link connection. A receiver of the relay user equipment receives a broadcast message from the radio base station indicating that a further relay is required in the radio cell and including a persistence check value selected by the radio base station. Upon receiving the broadcast message, a processor of the relay user equipment activates the relay function of the relay user equipment if the relay user equipment determines that the relay requirement for activating its relay function in the radio cell is fulfilled by the relay user equipment and if a persistence check performed by the relay user equipment based on the received persistence check value is successful.

[0212] According to a sixteenth aspect provided in addition to the fifteenth aspect, the processor is configured to: 1) generate a random value within a certain value range; and 2) compare the generated random value with a received persistence check value selected by the radio base station within the same value range to determine whether the persistence check is successful. For example, the processor determines that the persistence check is successful if the generated random value is less than or equal to the received persistence check value.

[0213] According to a 17th aspect provided in addition to the 15th or 16th aspects, the processor determines whether radio resources are already configured for the relay user equipment to perform a relay discovery procedure for announcing its presence as a relay after the receiver receives the broadcast message and before the processor enables the relay function. If the processor determines that radio resources are not already configured for the relay user equipment to perform the relay discovery procedure, the processor requests radio resources for performing the relay discovery procedure from a radio base station, and the receiver receives information from the base station regarding whether radio resources are allocated for performing the relay discovery procedure and which radio resources are allocated.

[0214] According to an 18th aspect provided in addition to any of the 15th to 17th aspects, after the receiver receives the broadcast message and before the processor enables the relay function, a transmitter of the relay user equipment transmits to a radio base station a relay enable request message requesting permission from the radio base station to enable the relay function of the relay user equipment. The receiver receives from the radio base station a relay enable response message granting or denying permission for the relay user equipment to enable the relay function. If the relay enable response message granting permission to enable the relay function is received, the processor enables the relay function.

[0215] According to a 19th aspect provided in addition to the 17th and 18th aspects, a processor requests radio resources for performing a relay discovery procedure from a radio base station by including a request for radio resources in a relay activation request message to be transmitted by a transmitter to the radio base station for requesting permission to activate its relay functionality from the radio base station, and a receiver receives information from the radio base station about whether and which radio resources are allocated for performing a relay discovery procedure, thereby receiving a relay activation response message transmitted by the radio base station to grant or deny permission for the relay user equipment to activate its relay functionality.

[0216] According to a twentieth aspect provided in addition to any of the fifteenth to nineteenth aspects, after the receiver receives the broadcast message and the processor enables the relay function, the processor determines whether the relay user equipment is in an idle state or a connected state. If the processor determines that the relay user equipment is in an idle state, the processor transitions the relay user equipment to a connected state to enable requesting resources for performing a relay discovery procedure from the radio base station and / or to request permission from the radio base station to enable the relay function of the relay user equipment.

[0217] According to a twenty-first aspect provided in addition to any of the fifteenth to twentieth aspects, a receiver receives a broadcast message including information on relay requirements to be fulfilled by a relay user equipment in a radio cell. Additionally or alternatively, the receiver receives a broadcast message including information on radio resources to be used by the relay user equipment for a relay discovery procedure for announcing the presence of the relay user equipment as a relay. According to a 22nd aspect, provided in addition to any of the 15th to 21st aspects, a processor determines whether at least one of the following relay requirements is met: minimum and / or maximum thresholds for a radio link quality of a link between the relay user equipment and the radio base station, preferably the radio link quality being determined based on a reference signal received power RSRP and / or a reference signal received quality RSRQ, a maximum threshold for a mobility level of the relay user equipment, such as a speed of the relay user equipment, and a minimum threshold for a charge level of the relay user equipment.

[0218] According to a 23rd aspect provided in addition to any one of the 15th to 22nd aspects, a relay user equipment activates its relay function, and a receiver receives a relay disable command from a radio base station. A processor disables the relay function in response to the relay disable command. For example, a transmitter transmits to the radio base station a relay disable request message requesting the radio base station to disable or not disable the relay function of the relay user equipment.

[0219] According to a twenty-fourth aspect, a radio base station is provided for participating in the activation of a relay function of a relay user equipment in a mobile communication network. The relay user equipment is capable of performing direct communication via a direct side link connection with one or more remote user equipments, respectively. The relay user equipment is located in a radio cell controlled by the radio base station in the mobile communication network and supports a relay function for enabling the relay user equipment to act as a relay for one or more remote user equipments, respectively, to relay communication between the one or more remote user equipments and the radio base station via the direct side link connection. A processor of the radio base station determines whether an additional relay is required in the radio cell. The processor selects a persistence check value within a certain value range. A transmitter transmits to one or more remote user equipments in the radio cell relay requirements to be met before activating the relay function. The transmitter transmits a broadcast message in the radio cell if the processor determines that an additional relay is required. The broadcast message indicates at least that an additional relay is required in the radio cell and includes the selected persistence check value. The broadcast message indicates to one or more relay user equipments in the radio cell to activate the relay functionality if the relay user equipment successfully performs a persistence check based on the persistence check value and if the relay user equipment satisfies the relay requirements.

[0220] According to a twenty-fifth aspect provided in addition to the twenty-fourth aspect, when the receiver receives a relay start message from a proximity service function in the mobile communication network, the processor determines that an additional relay is required. Additionally or alternatively, the processor determines that an additional relay is required based on a number of remote user equipment in the radio cell that have poor radio links with the radio base station and / or a number of remote user equipment performing public safety services in the radio cell.

[0221] Hardware and Software Implementations of the Disclosure Other exemplary embodiments relate to the implementation of the various embodiments described above using hardware, software, or software in cooperation with hardware. In this regard, a user terminal (mobile terminal) and an eNodeB (base station) are provided. The user terminal and the base station are adapted to perform the methods described herein, which include corresponding entities appropriately involved in the methods, such as a receiver, a transmitter, a processor.

[0222] It is further recognized that the various embodiments may be implemented or performed using a computing device (processor). The computing device or processor may be, for example, a general-purpose processor, a DSP (digital signal processor), an ASIC (application-specific integrated circuit), an FPGA (field programmable gate array), or other programmable logic device. The various embodiments may also be implemented or embodied by a combination of these devices. In particular, each functional block used in the description of each embodiment above may be realized as an integrated circuit by LSI. They may be individually formed as chips, or one chip may be formed to include some or all of the functional blocks. They may include data inputs and outputs coupled thereto. In this specification, the LSI may be referred to as an IC, a system LSI, a super LSI, or an ultra LSI depending on the difference in integration degree. However, the technique of implementing an integrated circuit is not limited to LSI, and may be realized by using a dedicated circuit or a general-purpose processor. In addition, an FPGA (field programmable gate array) that can be programmed after the LSI is manufactured, or a reconfigurable processor that can reconfigure the connections and settings of circuit cells located inside the LSI may be used.

[0223] Furthermore, the various embodiments can also be implemented by software modules executed by a processor or directly in hardware. A combination of software modules and hardware implementations can also be possible. The software modules can be stored in any kind of computer-readable storage medium, for example RAM, EPROM, EEPROM, flash memory, registers, hard disks, CD-ROM, DVD, etc. Furthermore, it is further noted that individual features of the different embodiments can be the subject of another embodiment, individually or in any combination.

[0224] It will be appreciated by those skilled in the art that numerous and various changes and / or modifications may be made to the present disclosure as shown in the specific embodiments, and therefore the present embodiments are to be considered in all respects as illustrative and not restrictive.

Claims

1. A wireless communication network system including a relay user equipment and a radio base station that controls a process for enabling a relay function of the relay user equipment, the relay user equipment being capable of performing direct communication with one or more remote user equipments via a direct side link connection, the relay user equipments being located in radio cells controlled by the radio base station in the wireless communication network, and supporting a relay function to enable each of the relay user equipments to act as a relay for the one or more remote user equipments to relay communication between the one or more remote user equipments and the radio base station via the direct side link connection, The wireless base station a processor for determining whether an additional relay is needed in the radio cell; a transmitter for selecting, by the radio base station, a relay requirement for activating a relay function if it is determined that a further relay is required in the radio cell, and for transmitting, by the radio base station, a broadcast message in the radio cell, the broadcast message indicating at least that a further relay is required in the radio cell, and for transmitting the selected relay requirement for activating the relay function, a relay requirement for activating the relay function is to satisfy minimum and maximum thresholds for a radio link quality of a link between the relay user equipment and the radio base station, and activating the relay function includes activating the relay function when the radio link quality of the link between the relay user equipment and the radio base station satisfies the minimum and maximum thresholds; The relay user equipment: A receiving unit for receiving the relay requirement, when the relay user equipment receives the broadcast message, if the relay user equipment determines that a relay requirement for activating the relay function in the radio cell is satisfied by the relay user equipment, then activate the relay function. Wireless communication network system.

2. the broadcast message transmitted by the radio base station in the radio cell further comprises information on radio resources to be used by the relay user equipment for a relay discovery procedure for announcing its presence as a relay, Preferably, an indication that a further relay is required is included in the broadcast message separately from the information on the radio resources for the relay discovery procedure, or the relay user equipment determines that a further relay is required from the presence of the information on the radio resources for the relay discovery procedure in the broadcast message. The wireless communication network system according to claim 1 .

3. The process of determining whether an additional relay is required, which is performed by the processor of the radio base station, comprises: determining that a further relay is required when a relay initiation message is received from a proximity services function in the wireless communication network; and / or and / or based on the number of remote user equipments in the radio cell that have a poor radio link with the radio base station; The wireless communication network system according to claim 1 or 2, based on the number of remote user equipments performing public safety services within the wireless cell.

4. A method performed by a wireless communication network system including a relay user equipment and a radio base station that controls a process for enabling a relay function of the relay user equipment, the method comprising: the relay user equipments being capable of performing direct communication via a direct side link connection with one or more remote user equipments, the relay user equipments being located in radio cells controlled by the radio base station in the wireless communication network, and supporting a relay functionality to enable each of the relay user equipments to act as a relay for the one or more remote user equipments to relay communication between the one or more remote user equipments and the radio base station via the direct side link connection; By the wireless base station, determining whether a further relay is needed in the radio cell; if it is determined that a further relay is required in the radio cell, selecting, by the radio base station, a relay requirement for activating a relay function, and transmitting, by the radio base station, a broadcast message in the radio cell, the broadcast message indicating at least that a further relay is required in the radio cell, and transmitting the relay requirement for activating the selected relay function; a relay requirement for activating the relay function is to satisfy minimum and maximum thresholds for a radio link quality of a link between the relay user equipment and the radio base station, and activating the relay function includes activating the relay function when the radio link quality of the link between the relay user equipment and the radio base station satisfies the minimum and maximum thresholds; by the relay user equipment, receiving the relay requirement; when the relay user equipment receives the broadcast message, if the relay user equipment determines that a relay requirement for enabling the relay function in the radio cell is satisfied by the relay user equipment, then the relay user equipment enables its relay function. method.

Citation Information

Patent Citations

  • Method of relay discovery and communication in a wireless communications system

    EP2833694A2

  • Radio communication system, and radio communication method

    JP2013005322A

  • JPP7013505B

  • Cooperative relay transmission method for wireless communication system

    US20070002766A1

  • Device-to-Device Communications in Cellular System

    US20110134827A1