Patent Application
20160254896
Example embodiments presented herein are directed towards a Radio Network Controller (RNC) and a radio network node, for example a eNodeB and/or a wireless terminal, and corresponding methods therein, for establishing a radio link without a Dedicated Physical Channel (DPCH) or a Fractional-DPCH (F-DPCH).
In a typical cellular system, also referred to as a wireless communications network, wireless terminals, also known as mobile stations and/or user equipment units communicate via a Radio Access Network (RAN) to one or more core networks. The wireless terminals can be mobile stations or user equipment units such as mobile telephones also known as “cellular” telephones, and laptops with wireless capability, e.g., mobile termination, and thus can be, for example, portable, pocket, hand-held, computer-comprised, or car-mounted mobile devices which communicate voice and/or data with radio access network.
The radio access network covers a geographical area which is divided into cell areas, with each cell area being served by a base station, e.g., a Radio Base Station (RBS), which in some networks is also called “NodeB” or “B node” or “Evolved NodeB” or “eNodeB” or “eNB” and which in this document also is referred to as a base station. A cell is a geographical area where radio coverage is provided by the radio base station equipment at a base station site. Each cell is identified by an identity within the local radio area, which is broadcast in the cell. The base stations communicate over the air interface operating on radio frequencies with the user equipment units within range of the base stations.
In some versions of the radio access network, several base stations are typically connected, e.g., by landlines or microwave, to a Radio Network Controller (RNC). The radio network controller, also sometimes termed a Base Station Controller (BSC), supervises and coordinates various activities of the plural base stations connected thereto. The radio network controllers are typically connected to one or more core networks.
The Universal Mobile Telecommunications System (UMTS) is a third generation mobile communication system, which evolved from the Global System for Mobile Communications (GSM), and is intended to provide improved mobile communication services based on Wideband Code Division Multiple Access (WCDMA) access technology. UMTS Terrestrial Radio Access Network (UTRAN) is essentially a radio access network using wideband code division multiple access for user equipment units (UEs). The Third Generation Partnership Project (3GPP) has undertaken to evolve further the UTRAN and GSM based radio access network technologies. Long Term Evolution (LTE) together with Evolved Packet Core (EPC) is the newest addition to the 3GPP family.
A heterogeneous network often indicates the use of multiple types of access nodes in a wireless network. A Wide Area Network can use Macro cells, Pico cells, and/or Femto cells in order to offer wireless coverage in an environment with a wide variety of wireless coverage zones, ranging from an open outdoor environment to office buildings, homes, and underground areas.
In heterogeneous networks, there is a need to mitigate an uplink (UL) and/or downlink (DL) imbalance due to different transmission powers between, for example, macro and Low Power Nodes (LPN) and to minimize the uplink interference to lower power nodes created by users in a non-soft handover area. Two example methods for means for solving the above mentioned issues are the use of ‘extended Enhanced Dedicated Channel (E-DCH) comprises only an E-DCH Acknowledgement Indicator Channel (E-HICH)’ or an E-DCH Acknowledgement Indicator Channel (E-HICH)’ and ‘common E-DCH Relative Grant Channel (E-RGCH)’. Both of means require the establishment of a radio link without the use of Dedicated Physical Channel (DPCH) or a Fractional-DPCH (F-DPCH).
The 3GPP specification 25.331 Radio Resource Control RRC Protocol Specification version 12.2.0 doesn't support the signalling of a radio link (RL) without the use of DPCH/F-DPCH, which therefore makes it impossible for the UE to indicate that it has the capability to support a RL without DPCH/F-DPCH. Furthermore, the network cannot configure the RL in UE without the use of DPCH/F-DPCH because the current signalling procedures are not configured to allow such an operation.
A need exists to convey information to configure a radio link which can be added to the LPN without DPCH/F-DPCH. Thus, the example embodiments presented herein provide a means for establishing a radio link without a DPCH/F-DPCH. An example advantage of the example embodiments presented herein is providing a radio link without the use of DPCH/F-DPCH, while solving any backwards compatibility issues.
Accordingly, some of the example embodiments are directed towards a method, in a RNC, for establishing a radio link without a DPCH/F-DPCH in a wireless communications network. The method comprises sending, to a radio network node, a communication message associated with the establishment of the radio link. The communication message comprises an indicator providing an indication to set up the radio link without the DPCH/F-DPCH. It should be appreciated that herein a radio network may be a Node B or a wireless terminal.
Some of the example embodiments are directed towards a Radio Network Controller (RNC) for establishing a radio link without a DPCH/ F-DPCH in a wireless communications network. The RNC comprises a transmitter configured to transmit, to a radio network node, a communication message associated with the establishment of the radio link. The communication message comprises an indicator providing an indication to set up the radio link without the DPCH/F-DPCH.
Some of the example embodiments are directed towards a method, in a radio network node, for establishing a radio link without a DPCH/ F-DPCH in a wireless communications network. The method comprises receiving, from a RNC, a communication message associated with the establishment of the radio link. The communication message comprises an indicator providing an indication for establishing the radio link without the DPCH/F-DPCH.
Some of the example embodiments are directed towards a radio network node for establishing a radio link without a DPCH/ F-DPCH in a wireless communications network. The radio network node comprises a receiver configured to receive, from a RNC, a communication message associated with the establishment of the radio link. The communication message comprises an indicator providing an indication for establishing the radio link without the DPCH/F-DPCH.
The foregoing will be apparent from the following more particular description of the example embodiments, as illustrated in the accompanying drawings in which like reference characters refer to the same parts throughout the different views. The drawings are not necessarily to scale, emphasis instead being placed upon illustrating the example embodiments.
In the following description, for purposes of explanation and not limitation, specific details are set forth, such as particular components, elements, techniques, etc. in order to provide a thorough understanding of the example embodiments. However, it will be apparent to one skilled in the art that the example embodiments may be practiced in other manners that depart from these specific details. In other instances, detailed descriptions of well-known methods and elements are omitted so as not to obscure the description of the example embodiments. The terminology used herein is for the purpose of describing the example embodiments and is not intended to limit the embodiments presented herein. It should be appreciated herein that the term user equipment (UE) and wireless terminal may be used interchangeably. It should be appreciated that all of the example embodiments presented herein may be applicable to a GERAN, UTRAN, E-UTRAN, Wi-Fi based system.
In order to provide a better explanation of the example embodiments presented herein, a problem is first identified and discussed. In the 3GPP Universal Mobile Telecommunications System (UMTS) R12 Heterogeneous Network work item 3GPPTM Work Item Description RP-131348 was proposed, thereby it is discussed about how to mitigate the uplink (UL)/downlink (DL) imbalance due to different transmission powers between Macros and Low Power Nodes (LPNs) and to minimize the uplink interference to LPNs created by the users in the non-soft hand over area. Companies have discussed different alternatives. There are mainly two alternatives agreed by Radio Access Network layer 1 (RAN1) that require the specification changes.
One alternative is called ‘extended Enhanced Dedicated Channel (E-DCH) which is designed to extend the soft handover area to cover those users who create high interference to the neighbour cells. Those users can be identified by the early triggering of the intra-frequency measurement event 1A. Upon the detection of those users, the Network (NW) orders those users to setup the radio link and add the detected neighbouring cell to the active set following the normal signalling procedure except without the setup of the DL channel F-DPCH/DPCH in the newly added cell. Such operation can achieve the benefit of the increased Macro diversity due to the extended active set. Meantime, the extra downlink control overhead due to the transmission of F-DPCH/DPCH is avoided.
The second alternative is called ‘common E-DCH Relative Grant Channel (E-RGCH)’. Its design purpose is to make it possible for the interfered neighbour cells in the active set to control the serving grant of the interfering E-DCH users. The common E-RGCH in CELL_DCH can operate like the operations in CELL_FACH. This channel is common channel and in principle may be monitored by users in the neighbour cells of the victim cell, which is the cell that experiences high interferences from the neighbour cells in the imbalance region. The common E-RGCH channel carries the control information “grant down”. The users who are monitor the common E-RGCH channel will have to reduce the serving grant for the data transmission in subsequent TTIs. With respect to RAN1, it has been concluded that the common E-RGCH in CELL_DCH is not a new channel, and it is achievable to establish this channel based on the existing technology, in example, share the traditional E-RGCH channel among the users, which is already possible in the current standard. Same as the first alternative, the users who are in the imbalance region and monitor the common E-RGCH channel are not required to receive the DL F-DPCH/DPCH channel from the interfered neighbour cell in imbalance region hence those cells can avoid to setup DL F-DPCH/DPCH channel in order to save the control channel overhead.
In fact, the above two alternatives are achievable by reusing the existing standard with limited changes. However, the both alternatives require the same operation to disable DL F-DPCH/DPCH when adding the radio link to the active set.
In the current RAN3 Node B Application Part (NBAP) and Radio Access Network Application Part (RNSAP) specification (3GPP TS 25.433 UTRAN lub interface Node B Application Part (NBAP) signaling version 12.1.0 and TS 25.423 UTRAN lur interface Radio Network Subsystem Application Part (RNSAP) signaling version 12.1.0), a radio link (RL) is setup either with DL DPCH or F-DPCH as a mandatory option. If the RNC includes the DL DPCH information, then the Node B shall configure DPCH in the downlink, for example, with a DL Dedicated Physical Control Channel (DPCCH) and a DL Dedicated Physical Data Channel (DPDCH), if the RNC includes the F-DPCH Information Element (IE). Then the Node B shall use F-DPCH in the downlink, for example, with transmission of only the Transmit Power Control (TPC) field for the given context.
There is no support to setup a radio link without using DPCH/F-DPCH. The current specification 25.331 Radio Resource Control RRC Protocol Specification version 12.2.0 doesn't support the signalling of a RL without DPCH/F-DPCH, which makes it impossible for the UE to indicate that it has the capability to support a RL without DPCH/F-DPCH. Furthermore, the network cannot configure the RL in UE without DPCH/F-DPCH because the current signalling doesn't allow that.
A need exists to convey information to configure a radio link which can be added to the LPN without DPCH/F-DPCH. Thus, the example embodiments presented herein provide a means for establishing a radio link without a DPCH/F-DPCH while solving any backwards compatibility issues.
According to some of the example embodiments, the establishment of the radio link without the F-DPCH/DPCH is allowed by not establishing the DL F-DPCH/DPCH configuration, for example, the Radio Resource Control (RRC) excludes the configuration information of F-DPCH/DPCH from the signalling. Thus, DPCH/F-DPCH free signalling is provided. It should be appreciated that DPCH/F-DPCH free signalling shall be interpreted as establishing a radio link without F-DPCH or DPCH. Thus, such a radio link will not include any channel of DPCH or F-DPCH, but that radio link (F-DPCH/DPCH less Radio Link) may comprise, for example, E-HICH channel only or another example that radio link (F-DPCH/DPCH less Radio Link) may comprise E-HICH and E-RGCH channels.
According to some of the example embodiments, the Node B who supports the establishment of the radio link without DPCH/F-DPCH may indicate to the RNC its capability, so there will not be an ambiguity. A new capability, for example, “Support of Radio Link without DPCH/F-DPCH for CELL_DCH”, may also be added to UE's radio access capability in 25.331 specification Radio Resource Control RRC Protocol Specification version 12.2.0 to indicate to the Network UE's capability of setting up a RL without DPCH/F-DPCH as specified below: This capability indicator may be added to the IE UE radio access capability.
The remainder of the text is organized as follows. First, example embodiments directed towards the exclusion of configuration information related to a F-DPCH/DPCH channel is provided under the sub-heading ‘Excluding F-DPCH/DPCH configuration information in signalling’. Thereafter, an example node configuration of a node which may be a radio network node (e.g., a wireless/mobile device/terminal or a Node B) or a RNC, as well as example operations of such nodes, are provided under the sub-headings ‘Example node configuration’ and ‘Example node operations’, respectively.
It should be appreciated that the example embodiments presented herein may be utilized signally or in any combination. The example embodiments presented herein have the example advantage of enabling a network to be setup without DL F-DPCH/DPCH while not providing any backwards compatibility problems.
According to some of the example embodiments, the establishment of a radio link without F-DPCH/DPCH may be provided in an explicit way by explicitly avoiding the sending of the configuration information for the F-DPCH/DPCH channel in specifications. A simplified overview of the example embodiments provided under this subheading are provided in
According to some of the example embodiments, a UE 101 may send an Event 1A measurement report to the RNC 400 via the Node B 201 (message 1). Thereafter the Node B 201 may send a capability indication that the Node B and/or the UE 101 supports the establishment of a radio link without DPCH/F-DPCH (message 2). This allows the RNC 400 to only setup the a radio link without the use of the DPCH/F-DPCH towards the new Node B, while the legacy Node B will not receive any related operation/information with respect to the radio link establishment without the DPCH/F-DPCH. The RNC 400 will thereafter send additional radio link information to the Node B 201 (message 3). The RNC 400 will also send an Active set update to the UE 101 (message 4). Both the additional radio link information and the Active set update do not comprise information for DPCH/F-PCH configuration.
When a radio link is setup/added/reconfigured, RNC will not include any configuration information for DL DPCH/F-DPCH in lub/lur specifications. Such configuration information is typically provided in the form of optional IEs Therefore, the removal of the optional parameters may be performed without the necessity of additional IEs or messaging. When the Node B, which supports the establishment of a radio link without the use of DPCH/F-DPCH, receives such a configuration, it interprets such information as an indication to allow the radio link establishment without DPCH/F-DPCH. A legacy Node B which does not support the establishment of a radio link without DPCH/F-DPCH would report a failure of the radio link setup/addition/reconfiguration as specified in the legacy procedures.
According to some of the example embodiments, for RRC signalling between the UE and the RNC, in order to configure the UE a RL without the DPCH/F-DPCH operation a new IE can be added to the IEs “Radio Link addition information” and “Downlink information for each radio link” as another option for R12 UE. For example, this new IE can have the name “Downlink without DPCH/F-DPCH info for each RL” as specified below: The text in bold and underlined represents the IE associated with the example embodiments presented herein.
According to Radio Resource Control RRC Protocol Specification version 12.2.0: Downlink information for each radio link
>Downlink without DPCH/F-
REL-12
DPCH info for each RL
According to Radio Resource Control RRC Protocol Specification version 12.2.0: TheRadio link addition information
>Downlink without DPCH/F-
REL-12
DPCH info for each RL
The RNC may also comprise a processing unit, module or circuitry 403 which may be configured to provide and retrieve information as described herein. The processing circuitry 403 may be any suitable type of computation unit, for example, a microprocessor, digital signal processor (DSP), field programmable gate array (FPGA), or application specific integrated circuit (ASIC), or any other form of circuitry. The RNC may further comprise a memory unit or circuitry 405 which may be any suitable type of computer readable memory and may be of volatile and/or non-volatile type. The memory 405 may be configured to store received, transmitted, and/or measured data, device parameters, and information, compatibility and/or executable program instructions.
The radio network node may also comprise a processing unit, module or circuitry 503 which may be configured to provide and retrieve information as described herein. The processing circuitry 503 may be any suitable type of computation unit, for example, a microprocessor, digital signal processor (DSP), field programmable gate array (FPGA), or application specific integrated circuit (ASIC), or any other form of circuitry. The radio network node may further comprise a memory unit or circuitry 505 which may be any suitable type of computer readable memory and may be of volatile and/or non-volatile type. The memory 505 may be configured to store received, transmitted, and/or measured data, device parameters, information, compatibility and/or executable program instructions.
Example Operation 10
According to some of the example embodiments, the radio network node 101 or 201 is configured to send 10, to the RNC 400, a capability indicator that indicates the radio network node is able to establish a radio link without DPCH/F-DPCH. The receiver 501A is configured to send, to the RNC, the capability indicator that indicates the radio network node is able to establish the radio link without DPCH/F-DPCH.
It should be appreciated that the radio network node may be either a wireless terminal 101 or a Node B 201. An example of the capability indicator of example operation 10 is provided in
Example Operation 12
According to some of the example embodiments, the RNC 400 is configured to receive 12, from the radio network node 101 or 201, a capability indicator that indicates a wireless terminal is able to establish a radio link without a DPCH/F-DPCH. The receiver 401 A is configured to receive, from the radio network node 101 or 201, the capability indicator that indicates the wireless terminal is able to establish a radio link without a DPCH/F-DPCH.
An example of the capability indicator of example operation 10 is provided in
Operation 14
The RNC 400 is configured to send, to a radio network node 101 or 201, a communication message associated with the establishment of the radio link. The communication message comprises an indicator providing an indication to set up the radio link without the DPCH/F-DPCH. The transmitter 401 B is configured to send, to the radio network node, the communication message associated with the establishment of the radio link. The sending module 14A is configured to perform operation 14.
According to some of the example embodiments, the indicator may be a message type, a cause code, instructions or an IE comprising an absence of a DPCH/F-DPCH configuration. According to some of the example embodiments, the communication message comprises an indication to establish the radio link with only an E-HICH or both a E-DCH and a E-RGCH.
Example Operation 16
According to some example embodiments, in which the radio network node is a wireless terminal 101, the RNC 400 is further configured to indicate, via the indicator described in operation 14, not to monitor or receive data via the DPCH/F-DPCH.
Example embodiment 16 is applicable with other channels currently allowed by the standard. For example, the wireless terminal will be informed by the RNC not to monitor or receive data via the DPCH/F-DPCH but the wireless terminal will use the E-HICH only or in another configuration the wireless terminal will use the E-HICH and the E-RGCH.
Operation 18
The radio network node 101 or 201 is configured to receive 18, from the RNC 400, the communication message associated with the establishment of the radio link. The communication message comprises the indicator providing the indication for establishing the radio link without the DPCH/F-DPCH. The receiver 501A is configured to receive, from the RNC, the communication message associated with the establishment of the radio link. The receiving module 18A is configured to perform operation 18.
As described in relation to operation 14, it should be appreciated that according to some of the example embodiments, the indicator may be a message type, a cause code, instructions or an IE comprising an absence of a DPCH/F-DPCH configuration. According to some of the example embodiments, the communication message comprises an indication to establish the radio link with only an E-HICH or both a E-DCH and a E-RGCH.
It should be noted that although terminology from 3GPP LTE has been used herein to explain the example embodiments, this should not be seen as limiting the scope of the example embodiments to only the aforementioned system. Other wireless systems, including WCDMA, WiMax, UMB, WiFi and GSM, may also benefit from the example embodiments disclosed herein.
The description of the example embodiments provided herein have been presented for purposes of illustration. The description is not intended to be exhaustive or to limit example embodiments to the precise form disclosed, and modifications and variations are possible in light of the above teachings or may be acquired from practice of various alternatives to the provided embodiments. The examples discussed herein were chosen and described in order to explain the principles and the nature of various example embodiments and its practical application to enable one skilled in the art to utilize the example embodiments in various manners and with various modifications as are suited to the particular use contemplated. The features of the embodiments described herein may be combined in all possible combinations of methods, apparatus, modules, systems, and computer program products. It should be appreciated that the example embodiments presented herein may be practiced in any combination with each other.
It should be noted that the word “comprising” does not necessarily exclude the presence of other elements or steps than those listed and the words “a” or “an” preceding an element do not exclude the presence of a plurality of such elements. It should further be noted that any reference signs do not limit the scope of the claims, that the example embodiments may be implemented at least in part by means of both hardware and software, and that several “means”, “units” or “devices” may be represented by the same item of hardware.
Also note that terminology such as user equipment should be considered as non-limiting. A device or user equipment as the term is used herein, is to be broadly interpreted to include a radiotelephone having ability for Internet/intranet access, web browser, organizer, calendar, a camera (e.g., video and/or still image camera), a sound recorder (e.g., a microphone), and/or global positioning system (GPS) receiver; a personal communications system (PCS) user equipment that may combine a cellular radiotelephone with data processing; a personal digital assistant (PDA) that can include a radiotelephone or wireless communication system; a laptop; a camera (e.g., video and/or still image camera) having communication ability; and any other computation or communication device capable of transceiving, such as a personal computer, a home entertainment system, a television, etc. It should be appreciated that the term user equipment may also comprise any number of connected devices. Furthermore, it should be appreciated that the term ‘user equipment’ shall be interpreted as defining any device which may have an internet or network access.
The various example embodiments described herein are described in the general context of method steps or processes, which may be implemented in one aspect by a computer program product, embodied in a computer-readable medium, including computer-executable instructions, such as program code, executed by computers in networked environments. A computer-readable medium may include removable and non-removable storage devices including, but not limited to, Read Only Memory (ROM), Random Access Memory (RAM), compact discs (CDs), digital versatile discs (DVD), etc. Generally, program modules may include routines, programs, objects, components, data structures, etc. that performs particular tasks or implement particular abstract data types. Computer-executable instructions, associated data structures, and program modules represent examples of program code for executing steps of the methods disclosed herein. The particular sequence of such executable instructions or associated data structures represents examples of corresponding acts for implementing the functions described in such steps or processes.
In the drawings and specification, there have been disclosed exemplary embodiments. However, many variations and modifications can be made to these embodiments. Accordingly, although specific terms are employed, they are used in a generic and descriptive sense only and not for purposes of limitation, the scope of the embodiments being defined by the following claims.
| Filing Document | Filing Date | Country | Kind |
|---|---|---|---|
| PCT/SE2015/050711 | 6/16/2015 | WO | 00 |
| Number | Date | Country | |
|---|---|---|---|
| 62038464 | Aug 2014 | US |
