Great research starts with great data.

Learn More
More >
Patent Analysis of

Method for processing a packet data convergence protocol service data unit at a user equipment in a dual connectivity system and device therefor

Updated Time 15 March 2019

Patent Registration Data

Publication Number

US10028170

Application Number

US15/113002

Application Date

03 February 2015

Publication Date

17 July 2018

Current Assignee

LG ELECTRONICS INC.

Original Assignee (Applicant)

LG ELECTRONICS INC.

International Classification

H04W80/02,H04L5/00,H04L12/26,H04W24/08,H04W74/08

Cooperative Classification

H04W28/06,H04L5/0078,H04L43/08,H04L69/28,H04W74/0833

Inventor

LEE, SUNYOUNG,YI, SEUNGJUNE

Patent Images

This patent contains figures and images illustrating the invention and its embodiment.

Method for processing a packet data convergence protocol service data unit at a user equipment in a dual connectivity system and device therefor Method for processing a packet data convergence protocol service data unit at a user equipment in a dual connectivity system and device therefor Method for processing a packet data convergence protocol service data unit at a user equipment in a dual connectivity system and device therefor
See all 16 images

Abstract

The present invention relates to a wireless communication system. More specifically, the present invention relates to a method and a device for processing a PDCP SDU in a dual connectivity system, the method comprising: receiving a PDCP SDU (Packet Data Convergence Protocol Service Data Unit) from a upper layer; starting a timer associated with the PDCP SDU; checking whether a certain condition related to the PDCP SDU process is satisfied or not if the timer expires; and discarding the PDCP SDU if the certain condition related to the PDCP SDU process is satisfied.

Read more

Claims

1. A method for a User Equipment (UE) operating in a wireless communication system, the method comprising: receiving, by a Packet Data Convergence Protocol (PDCP) entity of the UE, a PDCP Service Data Unit (SDU) from a upper layer; starting, by the PDCP entity, a timer associated with the PDCP SDU; checking whether the PDCP SDU is ready to be submitted or is already submitted to a lower layer of the UE, while a PDCP reordering function based on a reordering timer is operating in the PDCP entity; discarding the PDCP SDU if the PDCP SDU is not ready to be submitted nor is not submitted to the lower layer of the UE upon the discard timer expiry; and submitting a PDCP Protocol Data Unit (PDU) including the PDCP SDU to the lower layer of the UE without discarding the PDCP SDU if the PDCP SDU is ready to be submitted or is already submitted to the lower layer of the UE upon the discard timer expiry.

2. The method according to claim 1, wherein the PDCP SDU ready to be submitted to the lower layer of the UE is a PDCP SDU which is already associated with a PDCP sequence number (SN), or is a PDCP SDU included in the PDCP PDU that is already generated.

3. The method according to claim 1, wherein the PDCP PDU submitted to the lower layer of the UE includes the PDCP SDU and a PDCP SN associated with the PDCP SDU.

4. The method according to claim 1, further comprising: performing, by the PDCP entity, a re-numbering of consecutive PDCP SDUs that follow the discarded PDCP SDU so that there is no PDCP Sequence Number gap between the consecutive PDCP SDUs if the PDCP SDU is discarded.

5. The method according to claim 1, wherein the PDCP entity is associated with a first RLC for a first eNB and a second RLC for a second eNB.

6. A User Equipment (UE) for operating in a wireless communication system, the UE comprising: a Radio Frequency (RF) module; and a processor configured to control the RF module,wherein the processor is configured to: receive a Packet Data Convergence Protocol (PDCP) Service Data Unit (SDU) from a upper layer, start a timer associated with the PDCP SDU, check whether the PDCP SDU is ready to be submitted or is already submitted to a lower layer of the UE, while a PDCP reordering function based on a reordering timer is operating in the PDCP entity when the timer expires, discard the PDCP SDU if the PDCP SDU is not ready to be submitted nor is not submitted to the lower layer of the UE upon the discard timer expiry, and submit a PDCP Protocol Data Unit (PDU) including the PDCP SDU to the lower layer of the UE without discarding the PDCP SDU if the PDCP SDU is ready to be submitted or is already submitted to the lower layer of the UE upon the discard timer expiry.

7. The UE according to claim 6, wherein the PDCP SDU ready to be submitted to the lower layer of the UE is a PDCP SDU which is already associated with a PDCP sequence number (SN), or is a PDCP SDU included in the PDCP PDU that is already generated.

8. The UE according to claim 6, wherein the PDCP PDU submitted to the lower layer of the UE includes the PDCP SDU and a PDCP SN associated with the PDCP SDU.

9. The UE according to claim 6, wherein the processor is further configured to: perform, by the PDCP entity, a re-numbering of consecutive PDCP SDUs that follow the discarded PDCP SDU so that there is no PDCP Sequence Number gap between the consecutive PDCP SDUs if the PDCP SDU is discarded.

10. The UE according to claim 6, wherein the PDCP entity is associated with a first RLC for a first eNB and a second RLC for a second eNB.

Read more

Claim Tree

  • 1
    1. A method for a User Equipment (UE) operating in a wireless communication system, the method comprising:
    • receiving, by a Packet Data Convergence Protocol (PDCP) entity of the UE, a PDCP Service Data Unit (SDU) from a upper layer
    • starting, by the PDCP entity, a timer associated with the PDCP SDU
    • checking whether the PDCP SDU is ready to be submitted or is already submitted to a lower layer of the UE, while a PDCP reordering function based on a reordering timer is operating in the PDCP entity
    • discarding the PDCP SDU if the PDCP SDU is not ready to be submitted nor is not submitted to the lower layer of the UE upon the discard timer expiry
    • and submitting a PDCP Protocol Data Unit (PDU) including the PDCP SDU to the lower layer of the UE without discarding the PDCP SDU if the PDCP SDU is ready to be submitted or is already submitted to the lower layer of the UE upon the discard timer expiry.
    • 2. The method according to claim 1, wherein
      • the PDCP SDU ready to be submitted to the lower layer of the UE is a PDCP SDU which is already associated with a PDCP sequence number (SN), or is a PDCP SDU included in the PDCP PDU that is already generated.
    • 3. The method according to claim 1, wherein
      • the PDCP PDU submitted to the lower layer of the UE includes the PDCP SDU and a PDCP SN associated with the PDCP SDU.
    • 4. The method according to claim 1, further comprising:
      • performing, by the PDCP entity, a re-numbering of consecutive PDCP SDUs that follow the discarded PDCP SDU so that there is no PDCP Sequence Number gap between the consecutive PDCP SDUs if the PDCP SDU is discarded.
    • 5. The method according to claim 1, wherein
      • the PDCP entity is associated with a first RLC for a first eNB and a second RLC for a second eNB.
  • 6
    6. A User Equipment (UE) for operating in a wireless communication system, the UE comprising:
    • a Radio Frequency (RF) module
    • and a processor configured to control the RF module,wherein the processor is configured to: receive a Packet Data Convergence Protocol (PDCP) Service Data Unit (SDU) from a upper layer, start a timer associated with the PDCP SDU, check whether the PDCP SDU is ready to be submitted or is already submitted to a lower layer of the UE, while a PDCP reordering function based on a reordering timer is operating in the PDCP entity when the timer expires, discard the PDCP SDU if the PDCP SDU is not ready to be submitted nor is not submitted to the lower layer of the UE upon the discard timer expiry, and submit a PDCP Protocol Data Unit (PDU) including the PDCP SDU to the lower layer of the UE without discarding the PDCP SDU if the PDCP SDU is ready to be submitted or is already submitted to the lower layer of the UE upon the discard timer expiry.
    • 7. The UE according to claim 6, wherein
      • the PDCP SDU ready to be submitted to the lower layer of the UE is a PDCP SDU which is already associated with a PDCP sequence number (SN), or is a PDCP SDU included in the PDCP PDU that is already generated.
    • 8. The UE according to claim 6, wherein
      • the PDCP PDU submitted to the lower layer of the UE includes the PDCP SDU and a PDCP SN associated with the PDCP SDU.
    • 9. The UE according to claim 6, wherein
      • the processor is further configured to: perform, by the PDCP entity, a re-numbering of consecutive PDCP SDUs that follow the discarded PDCP SDU so that there is no PDCP Sequence Number gap between the consecutive PDCP SDUs if the PDCP SDU is discarded.
    • 10. The UE according to claim 6, wherein
      • the PDCP entity is associated with a first RLC for a first eNB and a second RLC for a second eNB.
See all 2 independent claims

Description

TECHNICAL FIELD

The present invention relates to a wireless communication system and, more particularly, to a method for processing a PDCP SDU at a UE in a dual connectivity system and a device therefor.

BACKGROUND ART

As an example of a mobile communication system to which the present invention is applicable, a 3rd Generation Partnership Project Long Term Evolution (hereinafter, referred to as LTE) communication system is described in brief.

FIG. 1 is a view schematically illustrating a network structure of an E-UMTS as an exemplary radio communication system. An Evolved Universal Mobile Telecommunications System (E-UMTS) is an advanced version of a conventional Universal Mobile Telecommunications System (UMTS) and basic standardization thereof is currently underway in the 3GPP. E-UMTS may be generally referred to as a Long Term Evolution (LTE) system. For details of the technical specifications of the UMTS and E-UMTS, reference can be made to Release 7 and Release 8 of “3rd Generation Partnership Project; Technical Specification Group Radio Access Network”.

Referring to FIG. 1, the E-UMTS includes a User Equipment (UE), eNode Bs (eNBs), and an Access Gateway (AG) which is located at an end of the network (E-UTRAN) and connected to an external network. The eNBs may simultaneously transmit multiple data streams for a broadcast service, a multicast service, and/or a unicast service.

One or more cells may exist per eNB. The cell is set to operate in one of bandwidths such as 1.25, 2.5, 5, 10, 15, and 20 MHz and provides a downlink (DL) or uplink (UL) transmission service to a plurality of UEs in the bandwidth. Different cells may be set to provide different bandwidths. The eNB controls data transmission or reception to and from a plurality of UEs. The eNB transmits DL scheduling information of DL data to a corresponding UE so as to inform the UE of a time/frequency domain in which the DL data is supposed to be transmitted, coding, a data size, and hybrid automatic repeat and request (HARQ)-related information. In addition, the eNB transmits UL scheduling information of UL data to a corresponding UE so as to inform the UE of a time/frequency domain which may be used by the UE, coding, a data size, and HARQ-related information. An interface for transmitting user traffic or control traffic may be used between eNBs. A core network (CN) may include the AG and a network node or the like for user registration of UEs. The AG manages the mobility of a UE on a tracking area (TA) basis. One TA includes a plurality of cells.

Although wireless communication technology has been developed to LTE based on wideband code division multiple access (WCDMA), the demands and expectations of users and service providers are on the rise. In addition, considering other radio access technologies under development, new technological evolution is required to secure high competitiveness in the future. Decrease in cost per bit, increase in service availability, flexible use of frequency bands, a simplified structure, an open interface, appropriate power consumption of UEs, and the like are required.

DISCLOSURE

Technical Problem

An object of the present invention devised to solve the problem lies in a method and device for processing a PDCP SDU at a UE in a dual connectivity system. The technical problems solved by the present invention are not limited to the above technical problems and those skilled in the art may understand other technical problems from the following description.

Technical Solution

The object of the present invention can be achieved by providing a method for a User Equipment (UE) operating in a wireless communication system, the method comprising: receiving a PDCP SDU (Packet Data Convergence Protocol Service Data Unit) from a upper layer; starting a timer associated with the PDCP SDU; checking whether a certain condition related to the PDCP SDU process is satisfied or not if the timer expires; and discarding the PDCP SDU if the certain condition related to the PDCP SDU process is satisfied.

In another aspect of the present invention, provided herein is a UE (User Equipment) for performing random access procedure in a wireless communication system, the UE comprising: an RF (Radio Frequency) module; and a processor configured to control the RF module, wherein the processor is configured to receive a PDCP SDU (Packet Data Convergence Protocol Service Data Unit) from a upper layer, to start a timer associated with the PDCP SDU, to check whether a certain condition related to the PDCP SDU process is satisfied or not when the timer expires, and to discard the PDCP SDU if the certain condition related to the PDCP SDU process is satisfied.

Preferably, wherein the certain condition related to the PDCP SDU process is satisfied if the PDCP sequence number is not associated with the PDCP SDU when the timer expire.

Preferably, the method further comprise: generating a PDCP PDU (Protocol Data Unit) using the PDCP SDU and the PDCP Sequence Number associated with the PDCP SDU, if the PDCP Sequence Number is associated with the PDCP SDU when the timer expires; and submitting the generated PDCP PDU to a lower layer.

Preferably, the certain condition related to the PDCP SDU process is satisfied if a PDCP PDU (Protocol Data Unit) including the PDCP SDU and PDCP SN associated with the PDCP SDU is not generated when the timer expires.

Preferably, the method further comprise: performing a re-numbering of consecutive PDCP SDUs that follow the discarded PDCP SDU so that there is no PDCP Sequence Number gap between the consecutive PDCP SDUs

Preferably, the certain condition related to the PDCP SDU process is satisfied if the PDCP PDU (Protocol Data Unit) including the PDCP SDU and PDCP SN associated with the PDCP SDU is not submitted to the lower layer when the timer expires.

Preferably, the method further comprise: performing a re-numbering of consecutive PDCP SDUs that follow the discarded PDCP SDU so that there is no PDCP Sequence Number gap between the consecutive PDCP SDUs.

It is to be understood that both the foregoing general description and the following detailed description of the present invention are exemplary and explanatory and are intended to provide further explanation of the invention as claimed.

Advantageous Effects

According to the present invention, processing PDCP SDU can be efficiently performed in a dual connectivity system. It will be appreciated by persons skilled in the art that that the effects achieved by the present invention are not limited to what has been particularly described hereinabove and other advantages of the present invention will be more clearly understood from the following detailed description taken in conjunction with the accompanying drawings.

DESCRIPTION OF DRAWINGS

The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the invention and together with the description serve to explain the principle of the invention.

FIG. 1 is a diagram showing a network structure of an Evolved Universal Mobile Telecommunications System (E-UMTS) as an example of a wireless communication system;

FIG. 2A is a block diagram illustrating network structure of an evolved universal mobile telecommunication system (E-UMTS), and FIG. 2B is a block diagram depicting architecture of a typical E-UTRAN and a typical EPC;

FIG. 3 is a diagram showing a control plane and a user plane of a radio interface protocol between a UE and an E-UTRAN based on a 3rd generation partnership project (3GPP) radio access network standard;

FIG. 4 is a diagram of an example physical channel structure used in an E-UMTS system;

FIG. 5 is a block diagram of a communication apparatus according to an embodiment of the present invention;

FIG. 6 is a diagram for carrier aggregation;

FIG. 7 is a conceptual diagram for dual connectivity between a Master Cell Group (MCS) and a Secondary Cell Group (SCG);

FIG. 8a is a conceptual diagram for C-Plane connectivity of base stations involved in dual connectivity, and FIG. 8b is a conceptual diagram for U-Plane connectivity of base stations involved in dual connectivity;

FIG. 9 is a conceptual diagram for radio protocol architecture for dual connectivity;

FIG. 10 is a diagram for a general overview of the LTE protocol architecture for the downlink;

FIG. 11 is a conceptual diagram for a PDCP entity architecture;

FIG. 12 is a conceptual diagram for functional view of a PDCP entity; and

FIGS. 13A to 13D are conceptual diagrams for processing a PDCP SDU in a dual connectivity system according to embodiments of the present invention.

BEST MODE

Universal mobile telecommunications system (UMTS) is a 3rd Generation (3G) asynchronous mobile communication system operating in wideband code division multiple access (WCDMA) based on European systems, global system for mobile communications (GSM) and general packet radio services (GPRS). The long-term evolution (LTE) of UMTS is under discussion by the 3rd generation partnership project (3GPP) that standardized UMTS.

The 3GPP LTE is a technology for enabling high-speed packet communications. Many schemes have been proposed for the LTE objective including those that aim to reduce user and provider costs, improve service quality, and expand and improve coverage and system capacity. The 3G LTE requires reduced cost per bit, increased service availability, flexible use of a frequency band, a simple structure, an open interface, and adequate power consumption of a terminal as an upper-level requirement.

Hereinafter, structures, operations, and other features of the present invention will be readily understood from the embodiments of the present invention, examples of which are illustrated in the accompanying drawings. Embodiments described later are examples in which technical features of the present invention are applied to a 3GPP system.

Although the embodiments of the present invention are described using a long term evolution (LTE) system and a LTE-advanced (LTE-A) system in the present specification, they are purely exemplary. Therefore, the embodiments of the present invention are applicable to any other communication system corresponding to the above definition. In addition, although the embodiments of the present invention are described based on a frequency division duplex (FDD) scheme in the present specification, the embodiments of the present invention may be easily modified and applied to a half-duplex FDD (H-FDD) scheme or a time division duplex (TDD) scheme.

FIG. 2A is a block diagram illustrating network structure of an evolved universal mobile telecommunication system (E-UMTS). The E-UMTS may be also referred to as an LTE system. The communication network is widely deployed to provide a variety of communication services such as voice (VoIP) through IMS and packet data.

As illustrated in FIG. 2A, the E-UMTS network includes an evolved UMTS terrestrial radio access network (E-UTRAN), an Evolved Packet Core (EPC) and one or more user equipment. The E-UTRAN may include one or more evolved NodeB (eNodeB) 20, and a plurality of user equipment (UE) 10 may be located in one cell. One or more E-UTRAN mobility management entity (MME)/system architecture evolution (SAE) gateways 30 may be positioned at the end of the network and connected to an external network.

As used herein, “downlink” refers to communication from eNodeB 20 to UE 10, and “uplink” refers to communication from the UE to an eNodeB. UE 10 refers to communication equipment carried by a user and may be also referred to as a mobile station (MS), a user terminal (UT), a subscriber station (SS) or a wireless device.

FIG. 2B is a block diagram depicting architecture of a typical E-UTRAN and a typical EPC.

As illustrated in FIG. 2B, an eNodeB 20 provides end points of a user plane and a control plane to the UE 10. MME/SAE gateway 30 provides an end point of a session and mobility management function for UE 10. The eNodeB and MME/SAE gateway may be connected via an S1 interface.

The eNodeB 20 is generally a fixed station that communicates with a UE 10, and may also be referred to as a base station (BS) or an access point. One eNodeB 20 may be deployed per cell. An interface for transmitting user traffic or control traffic may be used between eNodeBs 20.

The MME provides various functions including NAS signaling to eNodeBs 20, NAS signaling security, AS Security control, Inter CN node signaling for mobility between 3GPP access networks, Idle mode UE Reachability (including control and execution of paging retransmission), Tracking Area list management (for UE in idle and active mode), PDN GW and Serving GW selection, MME selection for handovers with MME change, SGSN selection for handovers to 2G or 3G 3GPP access networks, Roaming, Authentication, Bearer management functions including dedicated bearer establishment, Support for PWS (which includes ETWS and CMAS) message transmission. The SAE gateway host provides assorted functions including Per-user based packet filtering (by e.g. deep packet inspection), Lawful Interception, UE IP address allocation, Transport level packet marking in the downlink, UL and DL service level charging, gating and rate enforcement, DL rate enforcement based on APN-AMBR. For clarity MME/SAE gateway 30 will be referred to herein simply as a “gateway,” but it is understood that this entity includes both an MME and an SAE gateway.

A plurality of nodes may be connected between eNodeB 20 and gateway 30 via the S1 interface. The eNodeBs 20 may be connected to each other via an X2 interface and neighboring eNodeBs may have a meshed network structure that has the X2 interface.

As illustrated, eNodeB 20 may perform functions of selection for gateway 30, routing toward the gateway during a Radio Resource Control (RRC) activation, scheduling and transmitting of paging messages, scheduling and transmitting of Broadcast Channel (BCCH) information, dynamic allocation of resources to UEs 10 in both uplink and downlink, configuration and provisioning of eNodeB measurements, radio bearer control, radio admission control (RAC), and connection mobility control in LTE_ACTIVE state. In the EPC, and as noted above, gateway 30 may perform functions of paging origination, LTE-IDLE state management, ciphering of the user plane, System Architecture Evolution (SAE) bearer control, and ciphering and integrity protection of Non-Access Stratum (NAS) signaling.

The EPC includes a mobility management entity (MME), a serving-gateway (S-GW), and a packet data network-gateway (PDN-GW). The MME has information about connections and capabilities of UEs, mainly for use in managing the mobility of the UEs. The S-GW is a gateway having the E-UTRAN as an end point, and the PDN-GW is a gateway having a packet data network (PDN) as an end point.

FIG. 3 is a diagram showing a control plane and a user plane of a radio interface protocol between a UE and an E-UTRAN based on a 3GPP radio access network standard. The control plane refers to a path used for transmitting control messages used for managing a call between the UE and the E-UTRAN. The user plane refers to a path used for transmitting data generated in an application layer, e.g., voice data or Internet packet data.

A physical (PHY) layer of a first layer provides an information transfer service to a higher layer using a physical channel. The PHY layer is connected to a medium access control (MAC) layer located on the higher layer via a transport channel. Data is transported between the MAC layer and the PHY layer via the transport channel. Data is transported between a physical layer of a transmitting side and a physical layer of a receiving side via physical channels. The physical channels use time and frequency as radio resources. In detail, the physical channel is modulated using an orthogonal frequency division multiple access (OFDMA) scheme in downlink and is modulated using a single carrier frequency division multiple access (SC-FDMA) scheme in uplink.

The MAC layer of a second layer provides a service to a radio link control (RLC) layer of a higher layer via a logical channel. The RLC layer of the second layer supports reliable data transmission. A function of the RLC layer may be implemented by a functional block of the MAC layer. A packet data convergence protocol (PDCP) layer of the second layer performs a header compression function to reduce unnecessary control information for efficient transmission of an Internet protocol (IP) packet such as an IP version 4 (IPv4) packet or an IP version 6 (IPv6) packet in a radio interface having a relatively small bandwidth.

A radio resource control (RRC) layer located at the bottom of a third layer is defined only in the control plane. The RRC layer controls logical channels, transport channels, and physical channels in relation to configuration, re-configuration, and release of radio bearers (RBs). An RB refers to a service that the second layer provides for data transmission between the UE and the E-UTRAN. To this end, the RRC layer of the UE and the RRC layer of the E-UTRAN exchange RRC messages with each other.

One cell of the eNB is set to operate in one of bandwidths such as 1.25, 2.5, 5, 10, 15, and 20 MHz and provides a downlink or uplink transmission service to a plurality of UEs in the bandwidth. Different cells may be set to provide different bandwidths.

Downlink transport channels for transmission of data from the E-UTRAN to the UE include a broadcast channel (BCH) for transmission of system information, a paging channel (PCH) for transmission of paging messages, and a downlink shared channel (SCH) for transmission of user traffic or control messages. Traffic or control messages of a downlink multicast or broadcast service may be transmitted through the downlink SCH and may also be transmitted through a separate downlink multicast channel (MCH).

Uplink transport channels for transmission of data from the UE to the E-UTRAN include a random access channel (RACH) for transmission of initial control messages and an uplink SCH for transmission of user traffic or control messages. Logical channels that are defined above the transport channels and mapped to the transport channels include a broadcast control channel (BCCH), a paging control channel (PCCH), a common control channel (CCCH), a multicast control channel (MCCH), and a multicast traffic channel (MTCH).

FIG. 4 is a view showing an example of a physical channel structure used in an E-UMTS system. A physical channel includes several subframes on a time axis and several subcarriers on a frequency axis. Here, one subframe includes a plurality of symbols on the time axis. One subframe includes a plurality of resource blocks and one resource block includes a plurality of symbols and a plurality of subcarriers. In addition, each subframe may use certain subcarriers of certain symbols (e.g., a first symbol) of a subframe for a physical downlink control channel (PDCCH), that is, an L1/L2 control channel. In FIG. 4, an L1/L2 control information transmission area (PDCCH) and a data area (PDSCH) are shown. In one embodiment, a radio frame of 10 ms is used and one radio frame includes 10 subframes. In addition, one subframe includes two consecutive slots. The length of one slot may be 0.5 ms. In addition, one subframe includes a plurality of OFDM symbols and a portion (e.g., a first symbol) of the plurality of OFDM symbols may be used for transmitting the L1/L2 control information. A transmission time interval (TTI) which is a unit time for transmitting data is 1 ms.

A base station and a UE mostly transmit/receive data via a PDSCH, which is a physical channel, using a DL-SCH which is a transmission channel, except a certain control signal or certain service data. Information indicating to which UE (one or a plurality of UEs) PDSCH data is transmitted and how the UE receive and decode PDSCH data is transmitted in a state of being included in the PDCCH.

For example, in one embodiment, a certain PDCCH is CRC-masked with a radio network temporary identity (RNTI) “A” and information about data is transmitted using a radio resource “B” (e.g., a frequency location) and transmission format information “C” (e.g., a transmission block size, modulation, coding information or the like) via a certain subframe. Then, one or more UEs located in a cell monitor the PDCCH using its RNTI information. And, a specific UE with RNTI “A” reads the PDCCH and then receive the PDSCH indicated by B and C in the PDCCH information.

FIG. 5 is a block diagram of a communication apparatus according to an embodiment of the present invention.

The apparatus shown in FIG. 5 can be a user equipment (UE) and/or eNB adapted to perform the above mechanism, but it can be any apparatus for performing the same operation.

As shown in FIG. 5, the apparatus may comprises a DSP/microprocessor (110) and RF module (transceiver; 135). The DSP/microprocessor (110) is electrically connected with the transceiver (135) and controls it. The apparatus may further include power management module (105), battery (155), display (115), keypad (120), SIM card (125), memory device (130), speaker (145) and input device (150), based on its implementation and designer's choice.

Specifically, FIG. 5 may represent a UE comprising a receiver (135) configured to receive a request message from a network, and a transmitter (135) configured to transmit the transmission or reception timing information to the network. These receiver and the transmitter can constitute the transceiver (135). The UE further comprises a processor (110) connected to the transceiver (135: receiver and transmitter).

Also, FIG. 5 may represent a network apparatus comprising a transmitter (135) configured to transmit a request message to a UE and a receiver (135) configured to receive the transmission or reception timing information from the UE. These transmitter and receiver may constitute the transceiver (135). The network further comprises a processor (110) connected to the transmitter and the receiver. This processor (110) may be configured to calculate latency based on the transmission or reception timing information.

FIG. 6 is a diagram for carrier aggregation.

Carrier aggregation technology for supporting multiple carriers is described with reference to FIG. 6 as follows. As mentioned in the foregoing description, it may be able to support system bandwidth up to maximum 100 MHz in a manner of bundling maximum 5 carriers (component carriers: CCs) of bandwidth unit (e.g., 20 MHz) defined in a legacy wireless communication system (e.g., LTE system) by carrier aggregation. Component carriers used for carrier aggregation may be equal to or different from each other in bandwidth size. And, each of the component carriers may have a different frequency band (or center frequency). The component carriers may exist on contiguous frequency bands. Yet, component carriers existing on non-contiguous frequency bands may be used for carrier aggregation as well. In the carrier aggregation technology, bandwidth sizes of uplink and downlink may be allocated symmetrically or asymmetrically.

Multiple carriers (component carriers) used for carrier aggregation may be categorized into primary component carrier (PCC) and secondary component carrier (SCC). The PCC may be called P-cell (primary cell) and the SCC may be called S-cell (secondary cell). The primary component carrier is the carrier used by a base station to exchange traffic and control signaling with a user equipment. In this case, the control signaling may include addition of component carrier, setting for primary component carrier, uplink (UL) grant, downlink (DL) assignment and the like. Although a base station may be able to use a plurality of component carriers, a user equipment belonging to the corresponding base station may be set to have one primary component carrier only. If a user equipment operates in a single carrier mode, the primary component carrier is used. Hence, in order to be independently used, the primary component carrier should be set to meet all requirements for the data and control signaling exchange between a base station and a user equipment.

Meanwhile, the secondary component carrier may include an additional component carrier that can be activated or deactivated in accordance with a required size of transceived data. The secondary component carrier may be set to be used only in accordance with a specific command and rule received from a base station. In order to support an additional bandwidth, the secondary component carrier may be set to be used together with the primary component carrier. Through an activated component carrier, such a control signal as a UL grant, a DL assignment and the like can be received by a user equipment from a base station. Through an activated component carrier, such a control signal in UL as a channel quality indicator (CQI), a precoding matrix index (PMI), a rank indicator (RI), a sounding reference signal (SRS) and the like can be transmitted to a base station from a user equipment.

Resource allocation to a user equipment can have a range of a primary component carrier and a plurality of secondary component carriers. In a multi-carrier aggregation mode, based on a system load (i.e., static/dynamic load balancing), a peak data rate or a service quality requirement, a system may be able to allocate secondary component carriers to DL and/or UL asymmetrically. In using the carrier aggregation technology, the setting of the component carriers may be provided to a user equipment by a base station after RRC connection procedure. In this case, the RRC connection may mean that a radio resource is allocated to a user equipment based on RRC signaling exchanged between an RRC layer of the user equipment and a network via SRB. After completion of the RRC connection procedure between the user equipment and the base station, the user equipment may be provided by the base station with the setting information on the primary component carrier and the secondary component carrier. The setting information on the secondary component carrier may include addition/deletion (or activation/deactivation) of the secondary component carrier. Therefore, in order to activate a secondary component carrier between a base station and a user equipment or deactivate a previous secondary component carrier, it may be necessary to perform an exchange of RRC signaling and MAC control element.

The activation or deactivation of the secondary component carrier may be determined by a base station based on a quality of service (QoS), a load condition of carrier and other factors. And, the base station may be able to instruct a user equipment of secondary component carrier setting using a control message including such information as an indication type (activation/deactivation) for DL/UL, a secondary component carrier list and the like.

FIG. 7 is a conceptual diagram for dual connectivity (DC) between a Master Cell Group (MCS) and a Secondary Cell Group (SCG).

The dual connectivity means that the UE can be connected to both a Master eNode-B (MeNB) and a Secondary eNode-B (SeNB) at the same time. The MCG is a group of serving cells associated with the MeNB, comprising of a PCell and optionally one or more SCells. And the SCG is a group of serving cells associated with the SeNB, comprising of the special SCell and optionally one or more SCells. The MeNB is an eNB which terminates at least S1-MME (S1 for the control plane) and the SeNB is an eNB that is providing additional radio resources for the UE but is not the MeNB.

The dual connectivity is a kind of carrier aggregation in that the UE is configured a plurality serving cells. However, unlike all serving cells supporting carrier aggregation of FIG. 8 are served by a same eNB, all serving cells supporting dual connectivity of FIG. 10 are served by different eNBs, respectively at same time. The different eNBs are connected via non-ideal backhaul interface because the UE is connected with the different eNBs at same time.

With dual connectivity, some of the data radio bearers (DRBs) can be offloaded to the SCG to provide high throughput while keeping scheduling radio bearers (SRBs) or other DRBs in the MCG to reduce the handover possibility. The MCG is operated by the MeNB via the frequency of f1, and the SCG is operated by the SeNB via the frequency of f2. The frequency f1 and f2 may be equal. The backhaul interface (BH) between the MeNB and the SeNB is non-ideal (e.g. X2 interface), which means that there is considerable delay in the backhaul and therefore the centralized scheduling in one node is not possible.

FIG. 8a shows C-plane (Control Plane) connectivity of eNBs involved in dual connectivity for a certain UE: The MeNB is C-plane connected to the MME via S1-MME, the MeNB and the SeNB are interconnected via X2-C (X2-Control plane). As FIG. 8a, Inter-eNB control plane signaling for dual connectivity is performed by means of X2 interface signaling. Control plane signaling towards the MME is performed by means of S1 interface signaling. There is only one S1-MME connection per UE between the MeNB and the MME. Each eNB should be able to handle UEs independently, i.e. provide the PCell to some UEs while providing SCell(s) for SCG to others. Each eNB involved in dual connectivity for a certain UE owns its radio resources and is primarily responsible for allocating radio resources of its cells, respective coordination between MeNB and SeNB is performed by means of X2 interface signaling.

FIG. 8b shows U-plane connectivity of eNBs involved in dual connectivity for a certain UE. U-plane connectivity depends on the bearer option configured: i) For MCG bearers, the MeNB is U-plane connected to the S-GW via S1-U, the SeNB is not involved in the transport of user plane data, ii) For split bearers, the MeNB is U-plane connected to the S-GW via S1-U and in addition, the MeNB and the SeNB are interconnected via X2-U, and iii) For SCG bearers, the SeNB is directly connected with the S-GW via S1-U. If only MCG and split bearers are configured, there is no S1-U termination in the SeNB. In the dual connectivity, enhancement of the small cell is required in order to data offloading from the group of macro cells to the group of small cells. Since the small cells can be deployed apart from the macro cells, multiple schedulers can be separately located in different nodes and operate independently from the UE point of view. This means that different scheduling node would encounter different radio resource environment, and hence, each scheduling node may have different scheduling results.

FIG. 9 is a conceptual diagram for radio protocol architecture for dual connectivity.

E-UTRAN of the present example can support dual connectivity operation whereby a multiple receptions/transmissions (RX/TX) UE in RRC_CONNECTED is configured to utilize radio resources provided by two distinct schedulers, located in two eNBs (or base stations) connected via a non-ideal backhaul over the X2 interface. The eNBs involved in dual connectivity for a certain UE may assume two different roles: an eNB may either act as the MeNB or as the SeNB. In dual connectivity, a UE can be connected to one MeNB and one SeNB.

In the dual connectivity operation, the radio protocol architecture that a particular bearer uses depends on how the bearer is setup. Three alternatives exist, MCG bearer (901), split bearer (903) and SCG bearer (905). Those three alternatives are depicted on FIG. 9. The SRBs (Signaling Radio Bearers) are always of the MCG bearer and therefore only use the radio resources provided by the MeNB. The MCG bearer (901) is a radio protocol only located in the MeNB to use MeNB resources only in the dual connectivity. And the SCG bearer (905) is a radio protocol only located in the SeNB to use SeNB resources in the dual connectivity.

Specially, the split bearer (903) is a radio protocol located in both the MeNB and the SeNB to use both MeNB and SeNB resources in the dual connectivity and the split bearer (903) may be a radio bearer comprising one Packet Data Convergence Protocol (PDCP) entity, two Radio Link Control (RLC) entities and two Medium Access Control (MAC) entities for one direction. Specially, the dual connectivity operation can also be described as having at least one bearer configured to use radio resources provided by the SeNB.

The expected benefits of the split bearer (903) are: i) the SeNB mobility hidden to CN, ii) no security impacts with ciphering being required in MeNB only, iii) no data forwarding between SeNBs required at SeNB change, iv) offloads RLC processing of SeNB traffic from MeNB to SeNB, v) little or no impacts to RLC, vi) utilization of radio resources across MeNB and SeNB for the same bearer possible, vii) relaxed requirements for SeNB mobility (MeNB can be used in the meantime).

The expected drawbacks of the split bearer (903) are: i) need to route, process and buffer all dual connectivity traffic in the MeNB, ii) a PDCP entity to become responsible for routing PDCP PDUs towards eNBs for transmission and reordering them for reception, iii) flow control required between the MeNB and the SeNB, iv) in the uplink, logical channel prioritization impacts for handling RLC retransmissions and RLC Status PDUs (restricted to the eNB where the corresponding RLC entity resides) and v) no support of local break-out and content caching at SeNB for dual connectivity UEs.

In Dual Connectivity, two MAC entities are configured in the UE: one for the MCG and one for the SCG. Each MAC entity is configured by RRC with a serving cell supporting PUCCH transmission and contention based Random Access. The term SpCell refers to such cell, whereas the term SCell refers to other serving cells. The term SpCell either refers to the PCell of the MCG or the PSCell of the SCG depending on if the MAC entity is associated to the MCG or the SCG, respectively. A Timing Advance Group containing the SpCell of a MAC entity is referred to as pTAG, whereas the term sTAG refers to other TAGs.

The functions of the different MAC entities in the UE operate independently if not otherwise indicated. The timers and paramenters used in each MAC entity are configured independently if not otherwise indicated. The Serving Cells, C-RNTI, radio bearers, logical channels, upper and lower layer entities, LCGs, and HARQ entities considered by each MAC entity refer to those mapped to that MAC entity if not otherwise indicated

On the other hand, in the dual connectivity, one PDCP entity is configured in the UE. For one UE, there are two different eNBs that are connected via non-ideal backhaul X2. In case the split bearer (903) is transmitted to different eNBs (MeNB and SeNB), the SeNB forwards the PDCP PDU to the MeNB. Due to the delay over non-ideal backhaul, the PDCP PDUs are likely to be received out-of-sequence.

FIG. 10 is a diagram for a general overview of the LTE protocol architecture for the downlink.

A general overview of the LTE protocol architecture for the downlink is illustrated in FIG. 10. Furthermore, the LTE protocol structure related to uplink transmissions is similar to the downlink structure in FIG. 10, although there are differences with respect to transport format selection and multi-antenna transmission.

Data to be transmitted in the downlink enters in the form of IP packets on one of the SAE bearers (1001). Prior to transmission over the radio interface, incoming IP packets are passed through multiple protocol entities, summarized below and described in more detail in the following sections:

Packet Data Convergence Protocol (PDCP, 1003) performs IP header compression to reduce the number of bits necessary to transmit over the radio interface. The header-compression mechanism is based on ROHC, a standardized header-compression algorithm used in WCDMA as well as several other mobile-communication standards. PDCP (1003) is also responsible for ciphering and integrity protection of the transmitted data. At the receiver side, the PDCP protocol performs the corresponding deciphering and decompression operations. There is one PDCP entity per radio bearer configured for a mobile terminal.

Radio Link Control (RLC, 1005) is responsible for segmentation/concatenation, retransmission handling, and in-sequence delivery to higher layers. Unlike WCDMA, the RLC protocol is located in the eNodeB since there is only a single type of node in the LTE radio-access-network architecture. The RLC (1005) offers services to the PDCP (1003) in the form of radio bearers. There is one RLC entity per radio bearer configured for a terminal.

There is one RLC entity per logical channel configured for a terminal, where each RLC entity is responsible for: i) segmentation, concatenation, and reassembly of RLC SDUs; ii) RLC retransmission; and iii) in-sequence delivery and duplicate detection for the corresponding logical channel.

Other noteworthy features of the RLC are: (1) the handling of varying PDU sizes; and (2) the possibility for close interaction between the hybrid-ARQ and RLC protocols. Finally, the fact that there is one RLC entity per logical channel and one hybrid-ARQ entity per component carrier implies that one RLC entity may interact with multiple hybrid-ARQ entities in the case of carrier aggregation.

The purpose of the segmentation and concatenation mechanism is to generate RLC PDUs of appropriate size from the incoming RLC SDUs. One possibility would be to define a fixed PDU size, a size that would result in a compromise. If the size were too large, it would not be possible to support the lowest data rates. Also, excessive padding would be required in some scenarios. A single small PDU size, however, would result in a high overhead from the header included with each PDU. To avoid these drawbacks, which is especially important given the very large dynamic range of data rates supported by LTE, the RLC PDU size varies dynamically.

In process of segmentation and concatenation of RLC SDUs into RLC PDUs, a header includes, among other fields, a sequence number, which is used by the reordering and retransmission mechanisms. The reassembly function at the receiver side performs the reverse operation to reassemble the SDUs from the received PDUs.

Medium Access Control (MAC, 1007) handles hybrid-ARQ retransmissions and uplink and downlink scheduling. The scheduling functionality is located in the eNodeB, which has one MAC entity per cell, for both uplink and downlink. The hybrid-ARQ protocol part is present in both the transmitting and receiving end of the MAC protocol. The MAC (1007) offers services to the RLC (1005) in the form of logical channels (1009).

Physical Layer (PHY, 1011), handles coding/decoding, modulation/demodulation, multi-antenna mapping, and other typical physical layer functions. The physical layer (1011) offers services to the MAC layer (1007) in the form of transport channels (1013).

FIG. 11 is a conceptual diagram for a PDCP entity architecture.

FIG. 11 represents one possible structure for the PDCP sublayer, but it should not restrict implementation. Each RB (i.e. DRB and SRB, except for SRB0) is associated with one PDCP entity. Each PDCP entity is associated with one or two (one for each direction) RLC entities depending on the RB characteristic (i.e. uni-directional or bi-directional) and RLC mode. The PDCP entities are located in the PDCP sublayer. The PDCP sublayer is configured by upper layers.

FIG. 12 is a conceptual diagram for functional view of a PDCP entity.

The PDCP entities are located in the PDCP sublayer. Several PDCP entities may be defined for a UE. Each PDCP entity carrying user plane data may be configured to use header compression. Each PDCP entity is carrying the data of one radio bearer. In this version of the specification, only the robust header compression protocol (ROHC), is supported. Every PDCP entity uses at most one ROHC compressor instance and at most one ROHC decompressor instance. A PDCP entity is associated either to the control plane or the user plane depending on which radio bearer it is carrying data for.

FIG. 12 represents the functional view of the PDCP entity for the PDCP sublayer, it should not restrict implementation. For RNs, integrity protection and verification are also performed for the u-plane.

At reception of a PDCP SDU from upper layers, the UE may start a discard timer associated with the PDCP SDU. For a PDCP SDU received from upper layers, the UE may associate a PDCP SN (Sequence Number) corresponding to Next_PDCP_TX_SN to the PDCP SDU (S1201), perform header compression of the PDCP SDU (S1203), perform integrity protection (S1205) and ciphering using COUNT based on TX_HFN and the PDCP SN associated with this PDCP SDU (S1207), increment the Next_PDCP_TX_SN by one, and submit the resulting PDCP Data PDU to lower layer (S1209).

If the Next_PDCP_TX_SN is greater than Maximum_PDCP_SN, the Next_PDCP_TX_SN is set to ‘0’ and TX_HFN is incremented by one.

When the discard timer expires for a PDCP SDU, or the successful delivery of a PDCP SDU is confirmed by PDCP status report, the UE may discard the PDCP SDU along with the corresponding PDCP PDU. If the corresponding PDCP PDU has already been submitted to lower layers the discard is indicated to lower layers. The transmitting side of each PDCP entity for DRBs may maintain the discard timer. The duration of the timer is configured by upper layers. In the transmitter, a new timer is started upon reception of an SDU from upper layer.

In dual connectivity, for one UE, there are two different eNBs that are connected via non-ideal backhaul X2. In case the split bearer is transmitted to different eNBs (MeNB and SeNB), the SeNB forwards the PDCP PDU to the MeNB. Due to the delay over non-ideal backhaul, the PDCP PDUs are likely to be received out-of-sequence. Therefore, re-ordering function is needed in the PDCP receiver side to rearrange the processing order of PDCP PDUs in sequential order.

If the PDCP reordering function is operated based on the reordering timer as in the RLC reordering function, the reordering timer starts upon detection of out-of-sequence PDCP PDU and limit the maximum waiting time for the missing PDCP PDU. Given that PDCP SDU is discarded upon PDCP SDU discard timer expiry at the transmitter side, there is a case that PDCP reordering timer starts upon detection of out-of-sequence PDCP PDU which is already discarded in the PDCP transmitter side. Consequently, the PDCP receiver in the UE side would hold re-assembly of PDCP SDUs although the missing PDCP PDU can never be received. This has negative impact on throughput performance, which is the key goal of dual connectivity.

FIG. 13 is a conceptual diagram for processing a PDCP SDU in a dual connectivity system according to embodiments of the present invention.

In this invention, in order to avoid delaying re-assembly of PDCP SDUs (Packet Data Convergence Protocol Service Data Unit) in the PDCP receiver due to the discarded PDCP SDU in the PDCP transmitter, the PDCP transmitter avoids PDCP Sequence Number gap in the transmitted PDCP PDUs. For this purpose, the PDCP transmitter keeps transmitting PDCP SDU even if a discard timer expires for the PDCP SDU if the PDCP SDU is already associated with a PDCP Sequence Number.

At reception of a PDCP SDU from upper layers (S1301), the PDCP transmitter starts a discard timer associated with the PDCP SDU (S1303).

The PDCP transmitter associates a PDCP sequence number to the PDCP SDU (S1305), generates a PDCP PDU using the PDCP SDU and the PDCP Sequence Number associated with the PDCP SDU (S1307), and submits the generated PDCP PDU to a lower layer (S1309).

The PDCP transmitter can check whether a certain condition related to the PDCP SDU process is satisfied or not when the discard timer started in the step of S1303 expires. Because who does not know when the discard timer expires, the certain condition related to the PDCP SDU process can be differently determined.

[Case 1]

If the discard timer expires during the step of S1305, the PDCP transmitter checks whether the PDCP SDU is associated with a PDCP Sequence Number or not (S1304). In this case, the certain condition related to the PDCP SDU process is satisfied if the PDCP sequence number is not associated with the PDCP SDU when the timer expires.

Thus, if the PDCP SDU is already associated with the PDCP Sequence Number when the discard timer expires (S1305), the PDCP transmitter performs transmission of the PDCP SDU, (i.e. header compression and ciphering). And the PDCP transmitter generates a PDCP PDU (Protocol Data Unit) using the PDCP SDU and the PDCP SN associated with the PDCP SDU (S1307), and submits to RLC layer (S1309). The PDCP transmitter optionally discards the corresponding PDCP SDU.

Otherwise, if the PDCP sequence number is not associated with the PDCP SDU when the timer expires, the PDCP transmitter discards the corresponding PDCP SDU (S1311).

[Case 2]

If the discard timer expires during the step of S1307, the PDCP transmitter checks whether a PDCP PDU including the PDCP SDU and PDCP SN associated with the PDCP SDU is generated or not (S1306). In this case, the certain condition related to the PDCP SDU process is satisfied if the PDCP PDU including the PDCP SDU and PDCP SN associated with the PDCP SDU is not generated when the timer expires.

If the PDCP PDU including the PDCP SDU and the associated PDCP Sequence Number is already generated (S1307), the PDCP transmitter submits the generated PDCP PDU to the RLC layer (S1309). The PDCP transmitter optionally discards the corresponding PDCP SDU.

Otherwise, if the PDCP PDU including the PDCP SDU and the associated PDCP Sequence Number has not been generated, the PDCP transmitter discards the corresponding PDCP SDU (S1311). The PDCP transmitter performs renumbering of the PDCP SDUs that follow the discarded PDCP SDU so that there is no PDCP Sequence Number gap between transmitted PDCP SDUs (S1313). For example, if PDCP SDU with PDCP SN=3 is discarded, all the following PDCP SDUs, i.e. PDCP SN=4, 5, 6, . . . are renumbered to PDCP SN=3, 4, 5, . . . .

[Case 3]

If the discard timer expires during the step of S1309, the PDCP transmitter checks whether a PDCP PDU including the PDCP SDU and PDCP SN associated with the PDCP SDU is submitted or not (S1308). In this case, the certain condition related to the PDCP SDU process is satisfied if the PDCP PDU including the PDCP SDU and PDCP SN associated with the PDCP SDU is not submitted to a lower layer when the timer expires.

If the PDCP PDU including the PDCP SDU and the associated PDCP Sequence Number is already submitted to the RLC layer, the PDCP transmitter does nothing (S1309). The PDCP transmitter optionally discards the corresponding PDCP SDU.

If the PDCP PDU including the PDCP SDU and the associated PDCP Sequence Number has not been submitted to the RLC layer, the PDCP transmitter discards the corresponding PDCP PDU and PDCP SDU (S1311). The PDCP transmitter performs renumbering of the PDCP SDUs that follow the discarded PDCP SDU so that there is no PDCP Sequence Number gap between transmitted PDCP SDUs (S1313). For example, if PDCP SDU with PDCP SN=3 is discarded, all the following PDCP SDUs, i.e. PDCP SN=4, 5, 6, . . . are renumbered to PDCP SN=3, 4, 5, . . . .

It will be apparent to those skilled in the art that various modifications and variations can be made in the present invention without departing from the spirit or scope of the invention. Thus, it is intended that the present invention cover the modifications and variations of this invention provided they come within the scope of the appended claims and their equivalents.

The embodiments of the present invention described hereinbelow are combinations of elements and features of the present invention. The elements or features may be considered selective unless otherwise mentioned. Each element or feature may be practiced without being combined with other elements or features. Further, an embodiment of the present invention may be constructed by combining parts of the elements and/or features. Operation orders described in embodiments of the present invention may be rearranged. Some constructions of any one embodiment may be included in another embodiment and may be replaced with corresponding constructions of another embodiment. It is obvious to those skilled in the art that claims that are not explicitly cited in each other in the appended claims may be presented in combination as an embodiment of the present invention or included as a new claim by subsequent amendment after the application is filed.

In the embodiments of the present invention, a specific operation described as performed by the BS may be performed by an upper node of the BS. Namely, it is apparent that, in a network comprised of a plurality of network nodes including a BS, various operations performed for communication with an MS may be performed by the BS, or network nodes other than the BS. The term ‘eNB’ may be replaced with the term ‘fixed station’, ‘Node B’, ‘Base Station (BS)’, ‘access point’, etc.

The above-described embodiments may be implemented by various means, for example, by hardware, firmware, software, or a combination thereof.

In a hardware configuration, the method according to the embodiments of the present invention may be implemented by one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), Digital Signal Processing Devices (DSPDs), Programmable Logic Devices (PLDs), Field Programmable Gate Arrays (FPGAs), processors, controllers, microcontrollers, or microprocessors.

In a firmware or software configuration, the method according to the embodiments of the present invention may be implemented in the form of modules, procedures, functions, etc. performing the above-described functions or operations. Software code may be stored in a memory unit and executed by a processor. The memory unit may be located at the interior or exterior of the processor and may transmit and receive data to and from the processor via various known means.

Those skilled in the art will appreciate that the present invention may be carried out in other specific ways than those set forth herein without departing from the spirit and essential characteristics of the present invention. The above embodiments are therefore to be construed in all aspects as illustrative and not restrictive. The scope of the invention should be determined by the appended claims and their legal equivalents, not by the above description, and all changes coming within the meaning and equivalency range of the appended claims are intended to be embraced therein.

INDUSTRIAL APPLICABILITY

While the above-described method has been described centering on an example applied to the 3GPP LTE system, the present invention is applicable to a variety of wireless communication systems in addition to the 3GPP LTE system.

Read more
PatSnap Solutions

Great research starts with great data.

Use the most comprehensive innovation intelligence platform to maximise ROI on research.

Learn More

Patent Valuation

28.0/100 Score

Market Attractiveness

It shows from an IP point of view how many competitors are active and innovations are made in the different technical fields of the company. On a company level, the market attractiveness is often also an indicator of how diversified a company is. Here we look into the commercial relevance of the market.

29.0/100 Score

Market Coverage

It shows the sizes of the market that is covered with the IP and in how many countries the IP guarantees protection. It reflects a market size that is potentially addressable with the invented technology/formulation with a legal protection which also includes a freedom to operate. Here we look into the size of the impacted market.

75.0/100 Score

Technology Quality

It shows the degree of innovation that can be derived from a company’s IP. Here we look into ease of detection, ability to design around and significance of the patented feature to the product/service.

57.0/100 Score

Assignee Score

It takes the R&D behavior of the company itself into account that results in IP. During the invention phase, larger companies are considered to assign a higher R&D budget on a certain technology field, these companies have a better influence on their market, on what is marketable and what might lead to a standard.

24.0/100 Score

Legal Score

It shows the legal strength of IP in terms of its degree of protecting effect. Here we look into claim scope, claim breadth, claim quality, stability and priority.

PatSnap Solutions

PatSnap solutions are used by R&D teams, legal and IP professionals, those in business intelligence and strategic planning roles and by research staff at academic institutions globally.

PatSnap Solutions
Search & Analyze
The widest range of IP search tools makes getting the right answers—and asking the right questions—easier than ever. One click analysis extracts meaningful information on competitors and technology trends from IP data.
Business Intelligence
Gain powerful insights into future technology changes, market shifts and competitor strategies.
Workflow
Manage IP-related processes across multiple teams and departments with integrated collaboration and workflow tools.
Contact Sales