EP2807885A1 - Avance de temporisation dans une station de base et dispositif sans fil pourvu de groupes d'avance de temporisation basés sur des capacités d'une ue - Google Patents

Avance de temporisation dans une station de base et dispositif sans fil pourvu de groupes d'avance de temporisation basés sur des capacités d'une ue

Info

Publication number
EP2807885A1
EP2807885A1 EP13703256.1A EP13703256A EP2807885A1 EP 2807885 A1 EP2807885 A1 EP 2807885A1 EP 13703256 A EP13703256 A EP 13703256A EP 2807885 A1 EP2807885 A1 EP 2807885A1
Authority
EP
European Patent Office
Prior art keywords
wireless device
cell
random access
packet
uplink
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
EP13703256.1A
Other languages
German (de)
English (en)
Inventor
Esmael Hejazi DINAN
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Comcast Cable Communications LLC
Original Assignee
Dinan Esmael Hejazi
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Dinan Esmael Hejazi filed Critical Dinan Esmael Hejazi
Priority to EP20212147.1A priority Critical patent/EP3852466A1/fr
Publication of EP2807885A1 publication Critical patent/EP2807885A1/fr
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W56/00—Synchronisation arrangements
    • H04W56/004—Synchronisation arrangements compensating for timing error of reception due to propagation delay
    • H04W56/0045—Synchronisation arrangements compensating for timing error of reception due to propagation delay compensating for timing error by altering transmission time
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/04—TPC
    • H04W52/06—TPC algorithms
    • H04W52/14—Separate analysis of uplink or downlink
    • H04W52/146—Uplink power control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/04—TPC
    • H04W52/30—TPC using constraints in the total amount of available transmission power
    • H04W52/36—TPC using constraints in the total amount of available transmission power with a discrete range or set of values, e.g. step size, ramping or offsets
    • H04W52/367—Power values between minimum and maximum limits, e.g. dynamic range
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/04—TPC
    • H04W52/18—TPC being performed according to specific parameters
    • H04W52/28—TPC being performed according to specific parameters using user profile, e.g. mobile speed, priority or network state, e.g. standby, idle or non transmission
    • H04W52/281—TPC being performed according to specific parameters using user profile, e.g. mobile speed, priority or network state, e.g. standby, idle or non transmission taking into account user or data type priority
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/04—TPC
    • H04W52/38—TPC being performed in particular situations
    • H04W52/50—TPC being performed in particular situations at the moment of starting communication in a multiple access environment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0833—Random access procedures, e.g. with 4-step access

Definitions

  • FIG. 1 is a diagram depicting example sets of OFDM subcarriers as per an aspect of an
  • FIG. 2 is a diagram depicting an example transmission time and reception time for two
  • FIG. 3 is a diagram depicting OFDM radio resources as per an aspect of an embodiment of the present invention.
  • FIG. 4 is a block diagram of a base station and a wireless device as per an aspect of an
  • FIG. 5 is a block diagram depicting a system for transmitting data traffic over an OFDM radio system as per an aspect of an embodiment of the present invention
  • FIG. 6 is a diagram depicting uplink transmission timing of one or more cells in a first timing 25 advance group (TAG) and a second TAG as per an aspect of an embodiment of the present invention
  • FIG. 7 is an example message flow in a random access process in a secondary TAG as per an aspect of an embodiment of the present invention.
  • FIG. 8 shows example TAG configurations as per an aspect of an embodiment of the present 30 invention
  • FIG. 9 is an example physical random access channel (PRACH) configuration in a primary
  • FIG. 10 is a diagram showing example parallel transmission of a random access preamble with SRS, PUCCH, or PUSCH signals as per an aspect of an embodiment of the present invention
  • FIG. 11 is an example flow diagram illustrating a mechanism to exchange radio capability parameters as per an aspect of an embodiment of the present invention.
  • FIG. 12 is an example flow diagram illustrating a process for calculating transmission powers as per an aspect of an embodiment of the present invention.
  • FIG. 13 is an example flow diagram illustrating a process for sounding reference signal transmission as per an aspect of an embodiment of the present invention.
  • FIG. 14 is an example flow diagram illustrating parallel transmission of a random access preamble with other uplink packets as per an aspect of an embodiment of the present invention.
  • Example embodiments of the present invention enable operation of multiple timing advance groups.
  • Embodiments of the technology disclosed herein may be employed in the technical field of multicarrier communication systems. More particularly, the
  • embodiments of the technology disclosed herein may relate to operation of multiple timing advance groups.
  • Example embodiments of the invention may be implemented using various physical layer modulation and transmission mechanisms.
  • Example transmission mechanisms may include, but are not limited to: CDMA (code division multiple access), OFDM (orthogonal frequency division multiplexing), TDMA (time division multiple access), Wavelet technologies, and/or the like.
  • Hybrid transmission mechanisms such as TDMA/CDMA, and OFDM/CDMA may also be employed.
  • Various modulation schemes may be applied for signal transmission in the physical layer. Examples of modulation schemes include, but are not limited to: phase, amplitude, code, a combination of these, and/or the like.
  • An example radio transmission method may implement QAM (quadrature amplitude modulation) using BPSK (binary phase shift keying), QPSK (quadrature phase shift keying), 16-QAM, 64-QAM, 256-QAM, and/or the like.
  • Physical radio transmission may be enhanced by dynamically or semi-dynamically changing the modulation and coding scheme depending on transmission requirements and radio conditions.
  • FIG. 1 is a diagram depicting example sets of OFDM subcarriers as per an aspect of an embodiment of the present invention. As illustrated in this example, arrow(s) in the diagram may depict a subcarrier in a multicarrier OFDM system.
  • the OFDM system may use technology such as OFDM technology, SC-OFDM (single carrier-OFDM) technology, or the like.
  • FIG. 1 shows a subcarrier transmitting information symbols.
  • FIG. 1 is for illustration purposes, and a typical multicarrier OFDM system may include more subcarriers in a carrier.
  • the number of subcarriers in a carrier may be in the range of 10 to 10,000 subcarriers.
  • FIG. 1 shows two guard bands 106 and 107 in a transmission band. As illustrated in FIG. 1, guard band 106 is between subcarriers 103 and subcarriers 104.
  • the example set of subcarriers A 102 includes subcarriers 103 and subcarriers 104.
  • FIG. 1 also illustrates an example set of subcarriers B 105. As illustrated, there is no guard band between any two subcarriers in the example set of subcarriers B 105.
  • Carriers in a multicarrier OFDM communication system may be contiguous carriers, noncontiguous carriers, or a combination of both contiguous and non-contiguous carriers.
  • FIG. 2 is a diagram depicting an example transmission time and reception time for two carriers as per an aspect of an embodiment of the present invention.
  • a multicarrier OFDM communication system may include one or more carriers, for example, ranging from 1 to 10 carriers.
  • Carrier A 204 and carrier B 205 may have the same or different timing structures. Although FIG. 2 shows two synchronized carriers, carrier A 204 and carrier B 205 may or may not be synchronized with each other.
  • Different radio frame structures may be supported for FDD (frequency division duplex) and TDD (time division duplex) duplex mechanisms.
  • FIG. 2 shows an example FDD frame timing.
  • Downlink and uplink transmissions may be organized into radio frames 201.
  • radio frame duration is 10 msec.
  • Other frame durations for example, in the range of 1 to 100 msec may also be supported.
  • each 10 ms radio frame 201 may be divided into ten equally sized sub-frames 202.
  • Other subframe durations such as including 0.5 msec, 1 msec, 2 msec, and 5 msec may also be supported.
  • Sub-frame(s) may consist of two or more slots 206.
  • 10 subframes may be available for downlink transmission and 10 subframes may be available for uplink transmissions in each 10 ms interval.
  • Uplink and downlink transmissions may be separated in the frequency domain.
  • Slot(s) may include a plurality of OFDM symbols 203. The number of OFDM symbols 203 in a slot 206 may depend on the cyclic prefix length and subcarrier spacing.
  • FIG. 3 is a diagram depicting OFDM radio resources as per an aspect of an embodiment of the present invention.
  • the resource grid structure in time 304 and frequency 305 is illustrated in FIG. 3.
  • the quantity of downlink subcarriers or resource blocks (RB) may depend, at least in part, on the downlink transmission bandwidth 306 configured in the cell.
  • the smallest radio resource unit may be called a resource element (e.g. 301).
  • Resource elements may be grouped into resource blocks (e.g. 302).
  • Resource blocks may be grouped into larger radio resources called Resource Block Groups (RBG) (e.g. 303).
  • the transmitted signal in slot 206 may be described by one or several resource grids of a plurality of subcarriers and a plurality of OFDM symbols.
  • Resource blocks may be used to describe the mapping of certain physical channels to resource elements. Other pre-defined groupings of physical resource elements may be implemented in the system depending on the radio technology. For example, 24 subcarriers may be grouped as a radio block for a duration of 5 msec. In an illustrative example, a resource block may correspond to one slot in the time domain and 180 kHz in the frequency domain (for 15 KHz subcarrier bandwidth and 12 subcarriers).
  • a radio resource framework using OFDM technology may be employed.
  • Alternative embodiments may be implemented employing other radio technologies.
  • Example transmission mechanisms include, but are not limited to: CDMA, OFDM, TDMA, Wavelet technologies, and/or the like.
  • Hybrid transmission mechanisms such as TDMA/CDMA, and OFDM/CDMA may also be employed.
  • FIG. 4 is an example block diagram of a base station 401 and a wireless device 406, as per an aspect of an embodiment of the present invention.
  • a communication network 400 may include at least one base station 401 and at least one wireless device 406.
  • the base station 401 may include at least one communication interface 402, at least one processor 403, and at least one set of program code instructions 405 stored in non-transitory memory 404 and executable by the at least one processor 403.
  • the wireless device 406 may include at least one communication interface 407, at least one processor 408, and at least one set of program code instructions 410 stored in non-transitory memory 409 and executable by the at least one processor 408.
  • Communication interface 402 in base station 401 may be configured to engage in communication with communication interface 407 in wireless device 406 via a communication path that includes at least one wireless link 411.
  • Wireless link 411 may be a bi-directional link.
  • Communication interface 407 in wireless device 406 may also be configured to engage in a communication with communication interface 402 in base station 401.
  • Base station 401 and wireless device 406 may be configured to send and receive data over wireless link 411 using multiple frequency carriers.
  • transceiver(s) may be employed.
  • a transceiver is a device that includes both a transmitter and receiver. Transceivers may be employed in devices such as wireless devices, base stations, relay nodes, and/or the like.
  • Example embodiments for radio technology implemented in communication interface 402, 407 and wireless link 411 are illustrated are FIG. 1, FIG. 2, and FIG. 3. and associated text.
  • FIG. 5 is a block diagram depicting a system 500 for transmitting data traffic generated by a wireless device 502 to a server 508 over a multicarrier OFDM radio according to one aspect of the illustrative embodiments.
  • the system 500 may include a Wireless Cellular Network/Internet Network 507, which may function to provide connectivity between one or more wireless devices 502 (e.g., a cell phone, PDA (personal digital assistant), other wireles sly-equipped device, and/or the like), one or more servers 508 (e.g. multimedia server, application servers, email servers, or database servers) and/or the like.
  • wireless devices 502 e.g., a cell phone, PDA (personal digital assistant), other wireles sly-equipped device, and/or the like
  • servers 508 e.g. multimedia server, application servers, email servers, or database servers
  • the access network may include a plurality of base stations 503... 504.
  • Base station 503 ... 504 of the access network may function to transmit and receive RF (radio frequency) radiation 505 ... 506 at one or more carrier frequencies, and the RF radiation may provide one or more air interfaces over which the wireless device 502 may communicate with the base stations 503 ... 504.
  • the user 501 may use the wireless device ( or UE: user equipment) to receive data traffic, such as one or more multimedia files, data files, pictures, video files, or voice mails, etc.
  • the wireless device 502 may include applications such as web email, email applications, upload and ftp applications, MMS (multimedia messaging system) applications, or file sharing applications.
  • the wireless device 502 may automatically send traffic to a server 508 without direct involvement of a user.
  • a wireless camera with automatic upload feature or a video camera uploading videos to the remote server 508, or a personal computer equipped with an application transmitting traffic to a remote server.
  • One or more base stations 503 ... 504 may define a corresponding wireless coverage area.
  • the RF radiation 505 ... 506 of the base stations 503 ... 504 may carry communications between the Wireless Cellular Network/Internet Network 507 and access device 502 according to any of a variety of protocols. For example, RF radiation 505 ...
  • WiMAX Worldwide Interoperability for Microwave Access e.g., IEEE 802.16)
  • LTE long term evolution
  • microwave satellite
  • MMDS Multichannel Multipoint Distribution Service
  • Wi-Fi e.g., IEEE 802.11
  • Bluetooth Bluetooth
  • infrared and other protocols now known or later developed.
  • the communication between the wireless device 502 and the server 508 may be enabled by any networking and transport technology for example TCP/IP (transport control protocol/Internet protocol), RTP (real time protocol), RTCP (real time control protocol), HTTP (Hypertext Transfer Protocol) or any other networking protocol.
  • TCP/IP transport control protocol/Internet protocol
  • RTP real time protocol
  • RTCP real time control protocol
  • HTTP Hypertext Transfer Protocol
  • an LTE network may include many base stations, providing a user plane (PDCP: packet data convergence protocol/RLC: radio link control/MAC: media access control/PHY: physical) and control plane (RRC: radio resource control) protocol terminations towards the wireless device.
  • the base station(s) may be interconnected with other base station(s) by means of an X2 interface.
  • the base stations may also be connected by means of an S 1 interface to an EPC (Evolved Packet Core).
  • EPC Evolved Packet Core
  • the base stations may be interconnected to the MME (Mobility Management Entity) by means of the SI -MME interface and to the Serving Gateway (S- GW) by means of the S 1 -U interface.
  • MME Mobility Management Entity
  • S- GW Serving Gateway
  • the S 1 interface may support a many-to-many relation between MMEs / Serving Gateways and base stations.
  • a base station may include many sectors for example: 1, 2, 3, 4, or 6 sectors.
  • a base station may include many cells, for example, ranging from 1 to 50 cells or more.
  • a cell may be categorized, for example, as a primary cell or secondary cell.
  • a wireless device may have one RRC connection with the network. At RRC connection
  • one serving cell may provide the NAS (non- access stratum) mobility information (e.g. TAI-tracking area identifier), and at RRC connection re-establishment/handover, one serving cell may provide the security input.
  • This cell may be referred to as the Primary Cell (PCell).
  • the carrier corresponding to the PCell may be the Downlink Primary Component Carrier (DL PCC), while in the uplink, it may be the Uplink Primary Component Carrier (UL PCC).
  • SCells Secondary Cells
  • SCells Secondary Cells
  • SCells may be configured to form together with the PCell a set of serving cells.
  • the carrier corresponding to an SCell may be a Downlink Secondary Component Carrier (DL SCC), while in the uplink, it may be an Uplink Secondary Component Carrier (UL SCC).
  • DL SCC Downlink Secondary Component Carrier
  • UL SCC Uplink Secondary Component Carrier
  • An SCell may or may not have an uplink carrier.
  • a cell comprising a downlink carrier and optionally an uplink carrier, is assigned a physical cell ID and a cell index.
  • a carrier (downlink or uplink) belongs to only one cell, the cell ID or Cell index may also identify the downlink carrier or uplink carrier of the cell (depending on the context it is used).
  • cell ID may be equally referred to a carrier ID, and cell index may be referred to carrier index.
  • the physical cell ID or cell index may be assigned to a cell. Cell ID may be determined using the
  • Cell index may be determined using RRC messages.
  • a first physical cell ID for a first downlink carrier it may mean the first physical cell ID is for a cell comprising the first downlink carrier.
  • carrier activation when the specification indicates that a first carrier is activated, it equally means that the cell comprising the first carrier is activated.
  • Embodiments may be configured to operate as needed.
  • the disclosed mechanism may be performed when certain criteria are met, for example, in wireless device, base station, radio environment, network, a combination of the above, and/or the like.
  • Example criteria may be based, at least in part, on for example, traffic load, initial system set up, packet sizes, traffic characteristics, a combination of the above, and/or the like.
  • the example embodiments may be applied. Therefore, it may be possible to implement example embodiments that selectively implement disclosed protocols.
  • Example embodiments of the invention may enable operation of multiple timing advance groups.
  • Other example embodiments may comprise a non-transitory tangible computer readable media comprising instructions executable by one or more processors to cause operation of multiple timing advance groups.
  • Yet other example embodiments may comprise an article of manufacture that comprises a non-transitory tangible computer readable machine-accessible medium having instructions encoded thereon for enabling programmable hardware to cause a device (e.g. wireless communicator, UE, base station, etc.) to enable operation of multiple timing advance groups.
  • the device may include processors, memory, interfaces, and/or the like.
  • Other example embodiments may comprise communication networks comprising devices such as base stations, wireless devices (or user equipment: UE), servers, switches, antennas, and/or the like.
  • serving cells having an uplink to which the same time alignment (TA) applies may be grouped in a TA group (TAG).
  • TAG TA group
  • Serving cells in one TAG may use the same timing reference.
  • a user equipment UE
  • the UE may use one downlink carrier as the timing reference at a given time.
  • the UE may use a downlink carrier in a TAG as the timing reference for that TAG.
  • a UE may synchronize uplink subframe and frame transmission timing of the uplink carriers belonging to the same TAG.
  • serving cells having an uplink to which the same TA applies may correspond to the serving cells hosted by the same receiver.
  • a TA group may comprise at least one serving cell with a configured uplink.
  • a UE supporting multiple TAs may support two or more TA groups.
  • One TA group may contain the PCell and may be called a primary TAG (pTAG).
  • pTAG primary TAG
  • sTAG secondary TAG
  • Carriers within the same TA group may use the same TA value and the same timing reference.
  • timing advance group, time alignment group, and cell group have the same meaning.
  • FIG. 6 is a diagram depicting uplink transmission timing of one or more cells in a first timing advance group (TAG1) and a second TAG (TAG2) as per an aspect of an embodiment of the present invention.
  • TAG1 may include one or more cells
  • TAG2 may also include one or more cells.
  • TAG timing difference in FIG. 6 may be the difference in UE uplink transmission timing for uplink carriers in TAG1 and TAG2. The timing difference may range between, for example, sub micro-seconds to about 3o micro-seconds.
  • FIG. 8 shows example TAG configurations as per an aspect of an embodiment of the present invention.
  • pTAG include PCell, and sTAG includes SCelll.
  • pTAG includes PCell and SCelll
  • sTAG includes SCell2 and SCell3.
  • pTAG includes PCell and SCelll
  • sTAGl includes SCell2 and SCell3
  • sTAG2 includes SCell4. Up to four TAGs may be supported and other example TAG
  • TA maintenance, pathloss reference handling and the timing reference for pTAG may follow LTE release 10 principles.
  • the UE may need to measure downlink pathloss to calculate the uplink transmit power.
  • the pathloss reference may be used for uplink power control and/or transmission of random access preamble(s).
  • a UE may measure downlink pathloss using the signals received on the pathloss reference cell.
  • the pathloss reference downlink cell and the corresponding uplink cell may be configured to be in the same frequency band due to the required accuracy of pathloss estimation.
  • the choice of pathloss reference for cells may be selected from and be limited to the following two options: a) the downlink SCell linked to an uplink SCell using the system information block 2 (SIB2), and b) the downlink pCell.
  • SIB2 system information block 2
  • the pathloss reference for SCells in pTAG may be configurable using RRC message(s) as a part of SCell initial configuration and/or reconfiguration.
  • PhysicalConfigDedicatedSCell information element (IE) of an SCell configuration may include the pathloss reference SCell (downlink carrier) for an SCell in pTAG.
  • the downlink SCell linked to an uplink SCell using the system information block 2 (SIB2) may be referred to as the SIB2 linked downlink of the SCell.
  • SIB2 system information block 2
  • Different TAGs may operate in different bands.
  • the signals in different TAGs may travel through different repeaters, or the signal of one SCell in an sTAG may travel through a repeater while the signal of another TAG may not go through the repeater.
  • Having flexibility in SCell pathloss reference configuration for SCells belonging to an sTAG may result in pathloss estimation errors due to mobility of wireless device.
  • the wireless device may autonomously change a timing reference SCell in an sTAG, but changing pathloss reference autonomously may result in confusion in the serving eNB, specially that different cells may have different transmit power.
  • the pathloss reference may be only configurable to the downlink SCell linked to an uplink SCell using the system information block 2 (SIB2) of the SCell. No other downlink carrier may be configured as the pathloss reference for an SCell in an sTAG. This configuration may introduce accuracy in pathloss estimation.
  • SIB2 system information block 2
  • a UE may successfully complete a random access procedure from the reception of a random access response (RAR) message within the random access (RA) response window using a random access radio network temporary identifier (RA-RNTI).
  • the UE may decode scheduling information for uplink transmission in the PDCCH common search space (CSS) with RA-RNTI.
  • RAR for a PCell and/or SCell may contain at least one of the following: a Random Access Preamble Identifier (RAPID), a UL grant, a Temporary C-RNTI, a
  • RAPID may be used to confirm the association between RAR and the transmitted preamble.
  • the UL grant may be employed for uplink transmission on the cell that the preamble was transmitted.
  • Temporary C-RNTI may be used for contention resolution in case of contention based random access (CBRA).
  • a backoff Indicator (BI) may be used in case of collisions and/or high load on PRACH.
  • eNB may initiate an RA procedure.
  • a UE may use one of any activated SCells from this sTAG as a timing reference cell.
  • the timing reference for SCells in an sTAG may be the SIB2 linked downlink of the SCell on which the preamble for the latest RA procedure was sent. There may be one timing reference and one time alignment timer
  • TAT per TA group.
  • TAT for TAGs may be configured with different values.
  • TAT associated with the pTAG expires: all TATs may be considered as expired, the UE may flush all HARQ buffers of all serving cells, the UE may clear any configured downlink assignment/uplink grants, and the RRC in the UE may release PUCCH/SRS for all configured serving cells.
  • the pTAG TAT is not running, an sTAG TAT may not be running.
  • a) SRS transmissions may be stopped on the corresponding SCells, b) SRS RRC configuration may be released, c) CSI reporting configuration for the corresponding SCells may be maintained, and/or d) the MAC in the UE may flush the uplink HARQ buffers of the corresponding SCells.
  • the UE may not stop TAT of the sTAG.
  • TAT of the TA group may not be running.
  • RA procedures in parallel may not be supported for a UE. If a new RA procedure is requested (either by UE or network) while another RA procedure is already ongoing, it may be up to the UE implementation whether to continue with the ongoing procedure or start with the new procedure.
  • the eNB may initiate the RA procedure via a PDCCH order for an activated SCell. This PDCCH order may be sent on the scheduling cell of this SCell.
  • the scheduling cell When cross carrier scheduling is configured for a cell, the scheduling cell may be different than the cell that is employed for preamble transmission, and the PDCCH order may include the SCell index. At least a non-contention based RA procedure may be supported for SCell(s) assigned to sTAG(s). Upon new UL data arrival, the UE may not trigger an RA procedure on an SCell. PDCCH order for preamble transmission may be sent on a different serving cell than the SCell in which the preamble is sent. TA grouping may be performed without requiring any additional UE assisted information.
  • FIG. 7 is an example message flow in a random access process in a secondary TAG as per an aspect of an embodiment of the present invention.
  • eNB transmits an activation command 600 to activate an SCell.
  • a preamble 602 (Msgl) may be sent by a UE in response to the PDCCH order 601 on an SCell belonging to an sTAG.
  • preamble transmission for SCells may be controlled by the network using PDCCH format 1A.
  • Msg2 message 603 RAR: random access response
  • Uplink packets 604 may be transmitted on the SCell, in which the preamble was transmitted.
  • initial timing alignment may be achieved through a random access procedure. This may involve the UE transmitting a random access preamble and the eNB responding to an initial TA command NTA (amount of time alignment) within the random access response window.
  • the eNB may estimate the uplink timing from the random access preamble transmitted by the UE.
  • the TA command may be derived by the eNB based on the estimation of the difference between the desired UL timing and the actual UL timing.
  • the UE may determine the initial uplink transmission timing relative to the corresponding downlink of the sTAG on which the preamble is transmitted.
  • PDCCH order may be used to trigger RACH for an activated SCell.
  • eNB may need to firstly activate the corresponding SCell and then trigger a RA on it.
  • activation of an SCell may need at least 8ms, which may be an extra delay for UE to acquire the valid TA value on an SCell compared to the procedure on an already activated SCell.
  • 8ms may be required for SCell activation, and at least 6ms may be required for preamble transmission, and at least 4ms may be required to receive the random access response.
  • At least 18ms may be required for a UE to get a valid TA.
  • the possible delay caused by retransmission or other configured parameters may need to be considered (e.g. the possible retransmission of an activation/deactivation command, and/or the time gap between when a RA is triggered and when a preamble is transmitted (equal or larger than 6ms)).
  • the RAR may be transmitted within the RAR window (for example, 2ms, 10ms, 50 ms), and possible retransmission of the preamble may be considered.
  • the delay for such a case may be more than 20ms or even 30ms if retransmissions are considered.
  • a base station may communicate with a mix of wireless devices.
  • Wireless devices may support multiple technologies, or multiple releases of the same technology, have some specific capability depending on the wireless device category and/or capability.
  • a base station may comprise multiple sectors.
  • this disclosure refers to a base station communicating with a plurality of wireless devices, this disclosure may refer to a subset of the total wireless devices in the coverage area.
  • This disclosure may refer to, for example, a plurality of wireless devices of a given LTE release with a given capability and in a given sector of the base station.
  • the plurality of wireless devices in this disclosure may refer to a selected plurality of wireless devices, and/or a subset of total wireless devices in the coverage area, which perform according to the disclosed methods, and/or the like.
  • a time alignment command MAC control element may be a unicast MAC command transmitted to a wireless device.
  • a wireless device may receive its own time alignment commands.
  • the base station or wireless device may group cells into a plurality of cell groups.
  • the term "cell group" may refer to a timing advance group (TAG) or a timing alignment group or a time alignment group.
  • a cell group may include at least one cell.
  • a MAC TA command may correspond to a TAG.
  • a group may explicitly or implicitly be identified by a TAG index. Cells in the same band may belong to the same cell group.
  • a first cell's frame timing may be tied to a second cell's frame timing in a TAG. When a time alignment command is received for the second cell, the frame timing of both first cell and second cell may be adjusted.
  • Base station(s) may provide TAG configuration information to the wireless device(s) by RRC
  • a base station may transmit at least two types of time alignment commands.
  • a first type command may be transmitted to a first category of wireless devices.
  • the first category may include devices compatible with at least release 8, 9, or 10 of the LTE standard.
  • a second type command may be transmitted to a second category of devices.
  • the second category may include devices with multi-time alignment group (MTG) capability and compatible with release 11 or beyond of the LTE standard.
  • the time alignment may be transmitted to wireless devices that are in connected mode and are applicable to active cells.
  • a UE may transmit a Scheduling Request (SR) and/or a buffer status report (BSR) due to uplink data arrival in the UE.
  • a UE may transmit a scheduling request on PUCCH when the UE has data for uplink transmission and UE do not have uplink grants for transmission of a buffer status report.
  • the UE may receive uplink grant in response to a SR.
  • a base station scheduler may also provide an uplink grant to a UE for some other reasons, for example, based on a previous BSR.
  • the UE may transmit a MAC BSR in the uplink resources identified in an uplink grant to inform the base station about the size of the uplink transmission buffer(s).
  • a UE BSR may be transmitted in an uplink resource identified in a received uplink grant.
  • BSR indicates the amount of data in one or more logical channel buffers.
  • Base station may determine the radio resources required for the UE in the uplink employing the received BSR and other parameters, e.g. link quality, interference, UE category, and/or the like. If the base station determines that radio resources of a first SCell which is uplink unsynchronized is required (the SCell may be inactive or may not be even configured yet), the base station may trigger an sTAG sync process to uplink synchronize the sTAG and the first SCell associated with the sTAG.
  • the SCell should be in configured (e.g. using RRC messages) and be in active state (e.g. using MAC activate commands).
  • An SCell is considered out-of-sync if it belongs to or will belong to (after RRC configuration) to an out-of-sync sTAG.
  • the sTAG sync process may also selectively be started by the base station if a GBR bit rate bearer with required uplink resources has been established.
  • the Base station may determine the radio resources required for the UE in the uplink employing the received bit rate, QoS and priority requirements of the GBR bearer and other parameters, e.g. link quality, interference, UE category, and/or the like. If the base station determines that radio resources of a first SCell which is uplink unsynchronized is required (the SCell may be inactive or may not be even configured yet), the base station may trigger an sTAG sync process to uplink synchronize the sTAG and the first SCell associated with the sTAG.
  • the SCell should be in configured (e.g. using RRC messages) and be in active state (e.g. using MAC activate commands) before uplink transmission starts.
  • eNB may select to synchronize the sTAG and then activate/configure the SCell. eNB may select to first configure/activate SCell and then to uplink synchronize it. For example, if an SCell is added and assigned to a synchronized sTAG, it will be synchronize upon its (re)configuration/addition. In another example, the SCell may be configured, then the sTAG may be synchronized using another SCell in the sTAG, and then the SCell may be activated. In another example, the SCell may be configured/activated, and then sTAG synchronization may start. Different embodiments with different orders in tasks may be implemented. Random access process for an SCell can only be initiated on configured and active SCells assigned to an sTAG.
  • the base station may trigger random access preamble transmission on an SCell of the sTAG that the SCell belongs, or on the first SCell in which its uplink resources are required.
  • the first SCell belongs to an sTAG which is uplink out-of-sync.
  • the eNB may, selectively and depending on a plurality of criteria, transmit a PDCCH order to the UE and may cause the UE to start a RA procedure on an SCell in the sTAG(in case of carrier aggregation).
  • a PDCCH order may be triggered by the BSR reception due to the UL data arrival in the UE or by the establishment of GBR bearer with uplink resource requirements.
  • Preamble transmission may be triggered in the case of UL data arrival, meaning that preamble transmission may be triggered by the BSR reception in the eNB and/or establishment of a non GBR bearer with uplink data.
  • the UE may not trigger an RA procedure on an SCell.
  • the eNB may, selectively, trigger the RA procedure based on the BSR reception due to UL data arrival in the UE. eNB may consider many parameters in triggering an RA on an SCell.
  • parameters may include current eNB load, UE buffer size(s) in BSR report(s), UE category, UE capability, QoS requirements, GBR bearer requirements and/or the like.
  • UE may determine that radio resources of the out-of-sync SCell may be required for uplink data transmission.
  • base station may transmit a MAC timing advance command with a TAG index of the out-of-sync sTAG.
  • the UE may use an stored value of N_TA for the out of sync sTAG and apply the timing advance value in the MAC timing advance command to the stored N_TA of the sTAG.
  • a UE may store or maintains N_TA (current timing advance value of an sTAG) upon expiry of associated time Alignment Timer of the sTAG.
  • the UE may apply the received timing advance command MAC control element and starts associated time Alignment Timer. This process may practically put the sTAG in an in-sync state.
  • the base station may transmit one or more MAC timing advance commands upon receiving uplink packets from the UE on the sTAG to align UE uplink transmissions in the sTAG. It is up to eNB to select the first or second embodiment for synchronizing the uplink of first SCell. For example, the eNB may operate in the second embodiment, if the SCell has not been in-sync for a long time, or the sTAG has not been in-Sync since it has been configured. In another example, the eNB may operate in the first embodiment if the sTAG has recently entered an out-of- sync state. In another example, the eNB may operate in the second embodiment if the eNB-UE distance is relatively short, for example in the range of tens or hundreds of meters.
  • the mapping of a serving cell to a TAG may be configured by the serving eNB with RRC signaling.
  • the mechanism for TAG configuration and reconfiguration may be based on RRC signalling.
  • the mapping between an SCell and a TA group may be reconfigured with RRC signaling.
  • the mapping between an SCell and a TAG may not be reconfigured with RRC while the SCell is configured. For example if there is a need to move an SCell from an sTAG to a pTAG, at least one RRC message, for example, at least one RRC reconfiguration message, may be send to the UE to reconfigure TAG configurations.
  • the PCell may not change its TA group and may always be a member of the pTAG.
  • the related TAG configuration may be configured for the SCell.
  • eNB may modify the TAG configuration of an SCell by removing (releasing) the SCell and adding a new SCell (with the same physical cell ID and frequency) with an updated TAG ID.
  • the new SCell with the updated TAG ID may be initially inactive subsequent to joining the updated TAG ID.
  • eNB may activate the updated new SCell and then start scheduling packets on the activated SCell.
  • An eNB may perform initial configuration based on initial configuration parameters received from a network node (for example a management platform), an initial eNB configuration, a UE location, a UE type, UE CSI feedback, UE uplink transmissions (for example, data, SRS, and/or the like), a combination of the above, and/or the like.
  • initial configuration may be based on UE channel state measurements. For example, depending on the signal strength received from a UE on various SCells downlink carrier or by determination of UE being in a repeater coverage area, or a combination of both, an eNB may determine the initial configuration of sTAGs and membership of SCells to sTAGs.
  • the TA value of a serving cell may change, for example due to UE's mobility from a macro-cell to a repeater or an RRH (remote radio head) coverage area.
  • the signal delay for that SCell may become different from the original value and different from other serving cells in the same TAG.
  • eNB may relocate this TA-changed serving cell to another existing TAG.
  • the eNB may create a new TAG for the SCell based on the updated TA value.
  • the TA value may be derived, for example, through eNB measurement(s) of signal reception timing, a RA mechanism, or other standard or proprietary processes.
  • An eNB may realize that the TA value of a serving cell is no longer consistent with its current TAG.
  • the eNB may need to move the reference SCell belonging to an sTAG to another TAG.
  • the sTAG would require a new reference SCell.
  • the UE may select an active SCell in the sTAG as the reference timing SCell.
  • eNB may consider UE' s capability in configuring multiple TAGs for a UE.
  • UE may be configured with a configuration that is compatible with UE capability.
  • Multiple TAG capability may be an optional feature and per band combination
  • Multiple TAG capability may be introduced.
  • UE may transmit its multiple TAG capability to eNB via an RRC message and eNB may consider UE capability in configuring TAG configuration(s).
  • RRC connection reconfiguration procedure may be to modify an RRC connection, (e.g. to establish, modify and/or release RBs, to perform handover, to setup, modify, and/or release measurements, to add, modify, and/or release SCells).
  • NAS dedicated information may be transferred from E-UTRAN to the UE. If the received RRC Connection Reconfiguration message includes the sCellToReleaseList, the UE may perform an SCell release. If the received RRC Connection Reconfiguration message includes the sCellToAddModList, the UE may perform SCell additions or modification.
  • the parameters related to SCell random access channel may be common to all UEs.
  • PRACH configuration RACH resources, configuration parameters, RAR window
  • RACH resource parameters may include prach-configuration index, and/or prach-frequency offset.
  • SCell RACH common configuration parameters may also include power: power ramping parameter(s) for preamble transmission; and max number of preamble transmission parameter. It is more efficient to use common parameters for RACH configuration, since different UEs will share the same random access channel. Using dedicated parameters for SCell RACH configuration is not preferred since it will increase the size of the radio resources required for random access process, and may reduce spectral efficiency.
  • eNB may transmit at least one RRC message to configure PCell, SCell(s) and RACH, and TAG configuration parameters.
  • MAC-MainConfig may include a
  • timeAlignmentTimerDedicated IE to indicate time alignment timer value for the pTAG.
  • MAC-MainConfig may further include an IE including a sequence of at least one (sTAG ID, and TAT value) to configure time alignment timer values for sTAGs.
  • a first RRC message may configure TAT value for pTAG
  • a second RRC message may configure TAT value for sTAGl
  • a third RRC message may configure TAT value for sTAG2.
  • they may be included in one or two RRC messages.
  • the IE including a sequence of at least one (sTAG ID, and TAT) value may also be used to update the TAT value of an existing sTAG to an updated TAT value.
  • the at least one RRC message may also include sCellToAddModList including at least one SCell configuration parameters.
  • the radioResourceConfigDedicatedSCell (dedicated radio configuration IEs) in sCellToAddModList may include an SCell MAC configuration comprising TAG ID for the corresponding SCell added or modified.
  • the radioResourceConfigDedicatedSCell may also include pathloss reference configuration for an SCell. If TAG ID is not included in SCell configuration, the SCell is assigned to the pTAG. In other word, a TAG ID may not be included in radioResourceConfigDedicatedSCell for SCells assigned to pTAG.
  • the radioResourceConfigCommonSCell (common radio configuration IEs) in
  • sCellToAddModList may include RACH resource configuration parameters, preamble transmission power control parameters, and other preamble transmission parameter(s).
  • At the least one RRC message configures PCell, SCell, RACH resources, and/or SRS transmissions and may assign each SCell to an sTAG (implicitly or explicitly). PCell is always assigned to the pTAG.
  • a base station may transmit at least one control message to a wireless device in a plurality of wireless devices.
  • the at least one control message is for example, RRC connection reconfiguration message, RRC connection establishment message, RRC connection re-establishment message, and/or other control messages configuring or reconfiguring radio interface, and/or the like.
  • the at least one control message may be configured to cause, in the wireless device, configuration of at least:
  • Each cell may comprise a downlink carrier and zero or one uplink carrier.
  • the configuration may assign a cell group index to a cell in the plurality of cells.
  • the cell group index may identify one of a plurality of cell groups.
  • a cell group in the plurality of cell groups may comprise a subset of the plurality of cells.
  • the subset may comprise a reference cell with a reference downlink carrier and a reference uplink carrier. Uplink transmissions by the wireless device in the cell group may employ a
  • a plurality of MAC dedicated parameters comprising a sequence of at least one element.
  • An element in the sequence may comprises a time alignment timer value and a secondary time alignment group index.
  • pTAG time alignment timer value may be included as a dedicated IE in MAC main configuration parameter (a dedicated IE).
  • Each time alignment timer value being selected, by the base station, from a finite set of predetermined values.
  • the time alignment timer value in the sequence may be associated with a cell group index that is specified in the same element.
  • the element may also comprise the list of cell indexes associated with the time alignment group index.
  • the base station may transmit a plurality of timing advance commands.
  • Each timing advance command may comprise: a time adjustment value, and a cell group index.
  • a time alignment timer may start or may restart when the wireless device receives a timing advance command to adjust uplink transmission timing on a cell group identified by the cell group index.
  • the cell group may be considered out-of-sync, by the wireless device, when the associated time alignment timer expires or is not running.
  • the cell group may be considered in-sync when the associated time alignment timer is running.
  • the timing advance command may causes substantial alignment of reception timing of uplink signals in frames and subframes of all activated uplink carriers in the cell group at the base station.
  • the time alignment timer value may be configured as one of a finite set of predetermined values. For example, the finite set of predetermined values may be eight. Each time alignment timer value may be encoded employing three bits.
  • TAG TAT may be a dedicated time alignment timer value and is transmitted by the base station to the wireless device.
  • TAG TAT may be configured to cause configuration of time alignment timer value for each time alignment group.
  • the IE TAG TAT may be used to control how long the UE is considered uplink time aligned. It corresponds to the timer for time alignment for each cell group. Its value may be in number of sub-frames.
  • value sf500 corresponds to 500 sub-frames
  • sf750 corresponds to 750 sub-frames and so on.
  • An uplink time alignment is common for all serving cells belonging to the same cell group.
  • Time alignment timer for pTAG may be indicated in a separate IE and may not be included in the sequence.
  • TimeAlignmentTimerDedicated IE may be sf500, and then TAG TAT may be ⁇ 1, sf500; 2, sf2560; 3, sf500 ⁇ .
  • time alignment timer for the pTAG is configured separately and is not included in the sequence.
  • TAG0 (pTAG) time alignment timer value is 500 subframes (500 m-sec)
  • TAG1 (sTAG) time alignment timer value is 500 subframes
  • TAG2 time alignment timer value is 2560 subframes
  • TAG3 time alignment timer value is 500 subframes. This is for example purposes only.
  • a TAG may take one of 8 predefined values.
  • the enumerated values could take other values.
  • the size of the sequence is 3 in the first example and 4 in the second example. In another example embodiment, the size could be 2, 3, equal to the size of configured TAGs in the wireless device, and/or the like.
  • FIG. 9 is an example physical random access channel (PRACH) configuration in a primary TAG (pTAG) and a secondary TAG (sTAG) as per an aspect of an embodiment of the present invention.
  • PRACH resources are configured for the PCell in pTAG and SCell2 and SCell3 in sTAG.
  • SCelll and SCell4 are not configured with PRACH resources.
  • no SCell in pTAG is configured with PRACH resources.
  • PRACH resources for an SCell in pTAG may be configured, but eNB is not configured to trigger a preamble transmission on PRACH resources of an SCell in pTAG. Basically, PRACH resources in SCells in pTAG cannot be used for preamble transmissions by a UE.
  • an eNB may transmit a first control message to a wireless device (UE) on a primary downlink carrier of a PCell to establish a first signaling bearer with the UE on the primary cell.
  • the UE may transmit radio capability parameters from to the base station.
  • the radio capability parameters may be transmitted on the first signaling bearer on a primary uplink carrier of the primary cell.
  • a wireless device (UE) may transfer UE radio access capability information from the UE to E-UTRAN (e.g. base station). If the UE has changed its radio access capabilities, the UE may request higher layers to initiate the necessary procedures that would result in the update of UE radio access capabilities, e.g., using a new RRC connection.
  • a base station may initiate the procedure to a UE in RRC_CONNECTED when it needs (additional) UE radio access capability information.
  • radio capability parameters may include a parameter indicating support for multiple time alignment (MTA).
  • MTA multiple time alignment
  • Support for MTA may be considered an optional feature in release 11 , and an eNB may not know if a UE supports MTA capabilities until it receives a UE capability message from the UE indicating that the UE supports MTA feature.
  • eNB Before eNB configures pTAG and sTAG(s), eNB may receive and process UE capability regarding UE multiple time alignment capabilities. Supporting MTA capability may require that UE includes new hardware and/or software features that provide such a capability.
  • Multiple time alignment capability may be an optional capability for Rel-11 UE and its support may depend on UE's hardware, DSP and software designs.
  • a UE may send at least one time alignment capability parameter to the eNB.
  • eNB may configure UE's sTAG(s) and pTAG within the UE capability. For example, a UE may indicate how many sTAGs it may support. eNB may configure UE sTAG(s) based, at least in part, on the number of supported sTAGs in a UE. In another example, UE may explicitly or implicitly indicate if it supports inter-band or intra-band multiple TA, or both. In an example embodiment, support for MTA may be provided per band combination for one or more band combinations supported by a wireless device.
  • inter-band and/or intra-band carrier aggregation may be configured with multiple TAGs.
  • UE may send multiple TAG capability based on each supported band combinations.
  • UEs that could be configured with inter-band carrier aggregation may need MTA (multiple time alignment or multiple-TAG) configuration.
  • Carriers in a band may experience a different delay compared with a different band and a band may need its own TAG configuration.
  • a TAG configuration for carriers for a band may be required.
  • multiple TAGs may be configured, for example one TAG per band.
  • UE may comprise a plurality of RF chains to support inter-band carrier aggregation.
  • a UE may support multiple TAGs if the UE support inter-band carrier aggregation.
  • UE transceiver architectures may support non-contiguous and/or contiguous carrier aggregation in intra-band.
  • UE may support multiple TAGs in partial or all supportable intra-band carrier aggregation. Support for multiple TAG may depend on UE architecture, and some UEs may not support intra-band multiple TAG configurations in one or more bands depending on UEs transceiver structure.
  • a UE may communicate its multiple TAG capability to the eNB for intra-band communication.
  • a UE may transmit the MTA capability information for contiguous intra-band CA and/or noncontiguous intra-band carrier aggregation.
  • a UE may also communicate UE inter-band and/or intra-band TAG capability to the eNB.
  • UE may indicate its MTA
  • MTA capability in information elements (IEs) for each band combination including inter-band and intra-band combinations may be communicated employing at least one radio parameter.
  • MTA capability IE may be ordered (indexed) according to a band combination index determining the order of a band combination in a sequence of one or more band combinations.
  • the eNB may employ an internally stored look-up table to interpret the index of MTA capability and a band combination.
  • UE may transmit MTA capability including a sequence of MTA capability to the eNB.
  • the eNB may use a set of configuration options (for example in a look-up table, information list for band combinations, and/or the like format) to identify the band combination corresponding to an MTA capability (supported/not-supported) in a first sequence of one or more MTA capabilities.
  • the eNB may receive the indexed list of MTA capability(ies) and determine the MTA capabilities of the wireless device.
  • an information element in the form of a first sequence of one or more radio configuration parameters may be introduced.
  • Each of the radio configuration parameters may comprise a Multiple Timing Advance IE.
  • the Multiple Timing Advance IE for example, could be a binary variable indicating that Multiple Timing Advance capability is supported or not supported.
  • the first sequence comprising The Multiple Timing Advance IE may Indicate whether the wireless device supports multiple timing advances for each band combination listed in a second sequence of supported Band Combinations. If the band combination comprised of more than one band entry (i.e., inter-band or intra-band non-contiguous band combination), the Multiple Timing Advance IE field indicates whether different timing advances on different band entries are supported or not supported. If the band combination comprised of one band entry (i.e., intra-band contiguous band combination), the Multiple Timing Advance IE field indicates whether different timing advances across component carriers of the band entry are supported.
  • the first sequence including MTA capability IEs may include the same number of entries listed and in the same order as in the second sequence of Band Combination Parameters.
  • both inter-band and intra-band CA may support multiple time alignment configurations.
  • carriers in the same TAG may be in the same or different bands.
  • carriers in the same band may belong to same or different TAGs.
  • a UE may report its multiple time alignment capability based on supported band combinations.
  • Support for multiple TAG configurations may imply that at least one of the following features is supported by the UE: a) Parallel transmission of a preamble on an uplink carrier (PRACH) and PUSCH on at least one other carrier; b) Parallel transmission of a preamble on an uplink carrier (SCell PRACH) and PUCCH (e.g. on at least one other carrier , for example, the pCell); c) Parallel transmission of preamble on an uplink carrier, PUCCH (for example on PCell, if preamble is on an SCell), and PUSCH on at least one other carrier.
  • PRACH uplink carrier
  • SCell PRACH uplink carrier
  • PUCCH Physical channels allocation
  • This feature may be supported if parallel transmission of PUCCH and PUSCH is supported by the UE.
  • a UE may need to synchronize and track synchronization signals of multiple downlink carriers, one reference cell synchronization signal for a TAG.
  • a TAG may have its own timing reference SCell, which is different than the timing reference cell of another TAG.
  • the preamble may be any preamble.
  • the preamble may be any preamble.
  • transmission in the above items may refer to preamble transmission on an SCell uplink carrier and may not include preamble on a PCell.
  • a UE supporting multiple time alignment feature may support one or more of the above features.
  • the supported feature may be based, at least in part, on the parameters of the UE capability message and other predetermined parameters (explicitly or implicitly determined by signaling messages or technology specifications) and/or other signaling messages.
  • a UE supporting multiple time alignment feature may support all the features itemized in bullets (above).
  • a UE that does not support multiple time alignment feature may support none of the above features.
  • a UE supporting multiple time alignment feature may support all the above features.
  • a UE that does not support multiple time alignment feature may not support all-of-the-above features.
  • FIG. 11 is an example flow diagram illustrating a mechanism to exchange radio capability parameters as per an aspect of an embodiment of the present invention.
  • a first signaling bearer may be established between a wireless device and a base station on a primary cell at block 1100.
  • the establishing may comprise the wireless device receiving a first control message from the base station on the primary cell in a plurality of cells.
  • the plurality of cells may comprise the primary cell and at least one secondary cell.
  • the first control message may be, for example, a radio resource control connection establishment message, a radio resource control connection set up message, radio resource control connection reconfiguration message and/or the like.
  • the wireless device may initiate the
  • the base station may respond by transmitting a random access response comprising the preamble ID and an uplink grant.
  • the establishing may further comprise the wireless device transmitting a radio resource connection request message to the base station.
  • the wireless device may transmit the radio resource connection request in uplink radio resources identified in an uplink grant of a random access response message received from the base station.
  • the base station and wireless device may further communicate messages, for example, for authentication, security, configuration changes, and/or the like.
  • the wireless device may transmit a plurality of radio capability parameters to the base station.
  • the plurality of radio capability parameters may be transmitted on the first signaling bearer on the primary cell.
  • the plurality of radio capability parameters may comprise at least one parameter indicating whether the wireless device supports a plurality of timing advance groups.
  • the wireless device may support the plurality of timing advance groups for at least one band combination.
  • the parameter(s) may further indicate whether the wireless device supports a plurality of timing advance groups for each of one or more band combinations supported by the wireless device.
  • the wireless device may support (capable of performing the task when needed) transmission of a random access preamble on at least one of the secondary cell(s) in a secondary cell group. If the at least one parameter indicates the wireless device supports the plurality of timing advance groups, the wireless device may support parallel transmission of: a random access preamble on an uplink carrier on one of the secondary cell(s) in the secondary cell group; and uplink data on at least one other uplink carrier of other cell(s) in the plurality of cells.
  • the wireless device may support parallel transmission of: a random access preamble on an uplink carrier on one of the secondary cell(s) in the secondary cell group; and control data on an uplink physical control channel on at least one other uplink carrier of other cell(s) in the plurality of cells.
  • the other cell(s) in the plurality of cells may not comprise the one of the secondary cell(s) in the secondary cell group.
  • the wireless device may apply each of a plurality of MAC timing advance commands comprising a timing advance group index to uplink transmission timing of a cell group identified by the timing advance group index. If the at least one parameter indicates the wireless device supports the plurality of timing advance groups, the wireless device may be capable of maintaining a plurality of timing advance timers. If the at least one parameter indicates the wireless device supports a plurality of timing advance groups, the wireless device may support configuration of the plurality of timing advance groups. Each of the plurality of timing advance groups may comprise a distinct subset of the plurality of cells. Each cell is associated to only one timing advance group.
  • Uplink transmissions on each timing advance group may employ a synchronization signal on a downlink carrier of one active cell in the distinct subset as a timing reference.
  • Each of a plurality of MAC timing advance commands may comprise a timing advance value and a TAG index (TAG- ID).
  • the wireless device may further support parallel transmission of: a random access preamble on an uplink carrier on one of the secondary cell(s) in the secondary cell group; and an uplink sounding reference signal on other uplink carrier(s) of other cell(s) in the plurality of cells.
  • the wireless device may comprise
  • the communication interface(s), processor(s), and memory may store instructions.
  • the processor(s) may execute the instructions to cause actions described herein.
  • a wireless device may establish a first signaling bearer between a wireless device and a base station on a primary cell in a plurality of cells.
  • the plurality of cells may comprise the primary cell and secondary cell(s).
  • a plurality of radio capability parameters may be transmitted to the base station on the first signaling bearer on the primary cell.
  • the plurality of radio capability parameters may comprise parameter(s) indicating whether the wireless device supports a plurality of timing advance groups.
  • the wireless device may supports all of a multitude of features.
  • One of the features may comprise transmitting a random access preamble on at least one of the at least one secondary cell(s) in a secondary cell group.
  • Another of the features may comprise parallel transmission of: a random access preamble on an uplink carrier on one of secondary cell(s) in the secondary cell group; and uplink data on at least one other uplink carrier of at least one other cell in the plurality of cells.
  • Another of the features may comprise parallel transmission of a random access preamble on an uplink carrier on one of the at least one secondary cell in the secondary cell group; and control data on an uplink physical control channel on at least one other uplink carrier of other cell(s) in the plurality of cells.
  • Another of the features may comprise applying each of a plurality of MAC timing advance commands comprising a timing advance group index to uplink transmission timing of a cell group identified by the timing advance group index.
  • Another of the features may comprise maintaining a plurality of timing advance timers.
  • Another of the features may comprise configuring the plurality of timing advance groups.
  • Each of the plurality of timing advance groups may comprise a distinct subset of the plurality of cells. Uplink transmissions on each timing advance group may employ a synchronization signal on a downlink carrier of one active cell in the distinct subset as a timing reference.
  • the plurality of timing advance timers may correspond to a timing advance group in the plurality of timing advance groups.
  • the configuring of the plurality of timing advance groups may comprise assigning each cell in the plurality of cells to a timing advance group in the plurality of timing advance groups.
  • the random access preamble may be any random access preamble. According to some of the various embodiments, the random access preamble.
  • the control command may comprise an identifier of the random access preamble.
  • each of a plurality of MAC timing advance commands may comprise a timing advance value.
  • FIG. 11 is an example flow diagram illustrating a mechanism to exchange radio capability parameters as per an aspect of an embodiment of the present invention.
  • a first signaling bearer may be established between a base station and a wireless device on a primary cell.
  • the establishing may comprise the base station transmitting a first control message to the wireless device on the primary cell in a plurality of cells.
  • the plurality of cells may comprise the primary cell and at least one secondary cell.
  • the base station may receive a plurality of radio capability parameters from the wireless device.
  • the plurality of radio capability parameters are received on the first signaling bearer on the primary cell.
  • the plurality of radio capability parameters may be received on other signaling or data bearers on the primary or a secondary cell.
  • Many different factors may initiate the transmission of radio capability parameters, for example, establishing the connection, another example is when the capabilities have been change. Other examples may be provide.
  • the plurality of radio capability parameters may comprise at least one parameter indicating whether the wireless device supports a plurality of timing advance groups.
  • second control message(s) may be selectively transmitted to the wireless device by the base station if the second parameter(s) indicate that the wireless device supports the plurality of timing advance groups.
  • the second control message(s) may be configured to cause in the wireless device configuration of secondary cell(s) in the plurality of cells.
  • the control message(s) may be configured to cause in the wireless device assignment of each of the secondary cell(s) to a timing advance group in the plurality of timing advance groups.
  • the plurality of timing advance groups may comprise a primary timing advance group and a secondary timing advance group.
  • the primary timing advance group may comprise a first subset of the plurality of cells. The first subset may comprise the primary cell.
  • Uplink transmissions by the wireless device in the primary timing advance group may employ a first synchronization signal transmitted on the primary cell.
  • the secondary timing advance group may comprise a second subset of the secondary cell(s).
  • the second subset may comprise a reference secondary cell.
  • Uplink transmissions in the secondary timing advance group may employ a second synchronization signal on the reference secondary cell as a secondary timing reference.
  • the parameter(s) may further indicate whether the wireless device supports a plurality of timing advance groups for each of one or more band combinations supported by the wireless device.
  • the second control message(s) may be configured to further cause in the wireless device, configuration of a timing advance timer for each of the plurality of timing advance groups.
  • the timing advance timer may start or restart in response to the wireless device receiving a timing advance command to adjust uplink transmission timing of a commanded timing advance group in the plurality of timing advance groups.
  • the first control message may be a radio resource control connection establishment message.
  • the second control message(s) may be configured to further cause in the wireless device configuration of random access resources on a secondary cell in the secondary timing advance group.
  • FIG. 11 is an example flow diagram illustrating a mechanism to exchange radio capability parameters as per an aspect of an embodiment of the present invention.
  • a first signaling bearer may be established between a base station and a wireless device on a primary cell in a plurality of cells.
  • the plurality of cells may comprise the primary cell and at least one secondary cell.
  • the wireless device may initiate the establishing by transmitting a random access preamble to the base station.
  • the establishing may further comprise the wireless device transmitting a radio resource connection request message to the base station.
  • the wireless device may transmit the radio resource connection request in uplink radio resources identified in an uplink grant of a random access response message received from the base station.
  • the base station may receive a plurality of radio capability parameters from the wireless device.
  • various parameters may trigger transmission of radio capability parameters by a wireless device to the base station employing a signaling or data bearer.
  • the capability may be received on the first signaling bearer on the primary cell.
  • the plurality of radio capability parameters may comprise a first sequence of one or more radio configuration parameters.
  • a first radio configuration parameter in the first sequence may comprise a first parameter indicating whether multiple timing advance groups may be supported for a first band combination.
  • the first band combination may be in a second sequence of one or more band combinations.
  • the index of the first radio configuration parameter in the first sequence may determine the index of the first band combination in the second sequence.
  • the size of the first sequence may be the same as the size of the second sequence.
  • the index may determine the order of: the first radio configuration parameter in the first sequence; and the first band combination in the second sequence.
  • the first band combination may be identified by a first band combination parameter.
  • the first band combination parameter may comprise a list of band identifier(s). Each of the band identifier(s) may be one of a finite set of numbers. Each of the numbers may identify a specific band.
  • the wireless device may support multiple inter-band timing advance groups if the list of band identifier(s) includes more than one band; and the first parameter indicates that multiple timing advance groups are supported.
  • the wireless device may support multiple intra-band timing advance groups if the list of band identifier(s) includes one band; and the first parameter indicates that multiple timing advance groups are supported.
  • the wireless device may not support multiple timing advance configurations if none of the radio configuration parameters comprise a parameter indicating that multiple timing advance groups are supported.
  • a first signaling bearer may be established between a base station and a wireless device on a primary cell at block 1104.
  • the establishing may comprise the base station transmitting a control message to the wireless device on the primary cell in a plurality of cells.
  • the plurality of cells may comprise the primary cell and secondary cell(s).
  • the base station may receive a plurality of radio capability parameters from the wireless device.
  • the plurality of radio capability parameters may comprise a first sequence of one or more radio configuration parameters.
  • a first radio configuration parameter in the first sequence may comprise a first parameter indicating whether multiple timing advance groups are supported for a first band combination.
  • the first band combination may be in a second sequence of one or more band combinations.
  • the index of the first radio configuration parameter in the first sequence may determine the index of the first band combination in the second sequence.
  • the size of the first sequence may be the same as the size of the second sequence.
  • control message(s) may be selectively transmitted to the wireless device by the base station if the first sequence of one or more radio configuration parameters indicates that the wireless device supports the plurality of timing advance groups.
  • the control message(s) may be configured to cause in the wireless device configuration of secondary cell(s) in the plurality of cells.
  • the control message(s) may assign each of the secondary cell(s) to a time advance group in the plurality of timing advance groups.
  • the plurality of timing advance groups may comprise a primary timing advance group and a secondary timing advance group.
  • the primary timing advance group may comprise a first subset of the plurality of cells. The first subset may comprise the primary cell.
  • Uplink transmissions by the wireless device in the primary timing advance group may employ a first synchronization signal transmitted on the primary cell.
  • the secondary timing advance group may comprise a second subset of the at least one secondary cell.
  • the second subset may comprise a reference secondary cell.
  • Uplink transmissions in the secondary timing advance group may employ a second
  • control message(s) may be configured to further cause in the wireless device configuration of a timing advance timer for each of the plurality of timing advance groups.
  • the timing advance timer may start or restart in response to the wireless device receiving a timing advance command to adjust uplink transmission timing of a commanded timing advance group in the plurality of timing advance groups.
  • a first control message may be a radio resource configuration connection set up message.
  • Second control message(s) may be configured to further cause in the wireless device configuration of random access resources on a secondary cell in the secondary timing advance group.
  • the wireless device may comprise
  • a first signaling bearer may be established between a wireless device and a base station on a primary cell in a plurality of cells.
  • the plurality of cells may comprise the primary cell and secondary cell(s).
  • the wireless device may transmit a plurality of radio capability parameters to the base station on the first signaling bearer on the primary cell.
  • the plurality of radio capability parameters may comprise a first sequence of one or more radio configuration parameters.
  • a first radio configuration parameter in the first sequence may comprise a first parameter indicating whether multiple timing advance groups are supported for a first band combination.
  • the first band combination may be in a second sequence of one or more band combinations.
  • the index of the first radio configuration parameter in the first sequence may determine the index of the first band combination in the second sequence.
  • the size of the first sequence may be the same as the size of the second sequence. The index may determine the order of: the first radio configuration parameter in the first sequence; and the first band combination in the second sequence.
  • the first band combination may be identified by a first band combination parameter.
  • the first band combination parameter may comprise a list of band identifier(s).
  • the wireless device may support multiple inter-band timing advance groups if: the list of band identifier(s) includes more than one band; and the first parameter indicates that multiple timing advance groups are supported.
  • the wireless device may support multiple intra-band timing advance groups if: the list of band identifier(s) includes one band; and the first parameter indicates that multiple timing advance groups is or is not supported.
  • a wireless device may transmit an RRC message comprising UE capability information.
  • the UE capability information may comprise an information element comprising a wireless device LTE radio capability parameters.
  • the LTE radio capability parameters may comprise a plurality of parameters indicating various capability of the wireless device LTE radio.
  • the plurality of radio capability parameters may comprise a second sequence of one or more band combinations.
  • Each band combination IE parameter in the second sequence of one or more band combinations may comprise a list of one or more band identifier(s).
  • An example band combination IE may be ⁇ (band-id 1, band-parameters 1), (band-id2, band-parameters 2), (band-id3, band-parameters3).
  • the example band combination IE comprises a sequence of band identifier(s): band-idl, band-id2, band-id3, and a sequence of band parameters.
  • Band parameters may be uplink parameter(s) and/or downlink parameter(s).
  • Each of the band identifier(s) may be one of a finite set of numbers, for example from a set of (1..64).
  • the second sequence of one or more band combinations are considered an array of one or more band combination IEs.
  • two band combinations are in the second sequence of one or more band combinations.
  • a first sequence of one or more radio configuration parameters for example could be ⁇ (TAG-not- supported, other parameters 1),( TAG-supported, other parameters2) ⁇ .
  • the first radio configuration parameter is TAG-non-supported (with index 1)
  • the second radio configuration parameter is TAG-supported (with index 2).
  • Index 2 in the first sequence comprise (TAG-supported) corresponds to index 2 in the second sequence (the second band combination band-idl and band-id4).
  • TAG configuration is supported for band
  • the example embodiments provides a solution for network, base station, UE signaling to reduce signaling overhead required for configuring wireless devices in a network.
  • the example embodiments for communication of radio capability parameters provide flexibility in providing TAG capability for one or more band combinations. It reduces the required overhead for communicating this information by indexing TAG capability according to band combination IE. This increases radio efficiency.
  • eNB is able to selectively configure multiple UEs for capable UEs without introducing new signaling messages. This improvement would have minimal impact in the UE and eNB messaging system. eNB does is not required to receive this information from UE subscription information in the core, and this simplifies core network signaling and requirements.
  • SCell(s) belonging to an sTAG may need to perform random access process in order to achieve UL synchronization. For example, this may happen when an SCell belonging to an un unsynchronized sTAG is activated.
  • the UE may be uplink out-of-synch for that SCell, but is uplink synchronized for the pTAG and other sTAG(s).
  • eNB may trigger RACH on an SCell to let a UE to acquire uplink synchronization. Random access process may also be initiated on a synchronized sTAG, for example, for acquiring uplink timing of an SCell, and/or the like.
  • Random access on an SCell may be initiated while the UE is schedule to transmit other uplink data or control packets.
  • a random access on a pCell may be initiated by a UE and/or eNB.
  • a random access on a pCell for example may be initiated by an eNB to acquire uplink timing for a pCell.
  • Random access on a pCell may be initiated while the UE is scheduled to transmit other uplink data and/or control packets.
  • random access preamble When random access preamble is transmitted, for example, on an SCell of an sTAG, there is the possibility of transmission of: a) PUSCH, SRS, and/or PUCCH on PCell, and/or b) PUSCH and/or SRS on other serving cells belonging to pTAG and/or other sTAGs.
  • random access preamble When random access preamble is transmitted, for example, on a pCell of the pTAG, there is the possibility of transmission of PUSCH and/or SRS on other serving cells belonging sTAGs.
  • RACH random access channel
  • PRACH physical random access channel
  • UE may support parallel PRACH and PUSCH/PUCCH/SRS transmissions. This issue may not apply to LTE release 10, since no uplink transmission may be allowed when random access preamble is transmitted on a PCell uplink random access resource.
  • Parallel transmission of other UL packets during the time the random access preamble is sent may require special solution. There could be more than one TA group and hence one TA group may already be in sync while another TA (time alignment) group may not be in- sync. This means that UL transmission may be on-going on other cells while the UE receives a PDCCH order to transmit a preamble on a cell. Parallel transmission of a preamble, and other UL transmissions on cells in other TAGs may happen. Parallel and/or simultaneous transmission in this specification may imply that transmissions are substantially parallel and/or substantially simultaneous, and/or transmissions may overlap during a time period.
  • the overlap time period may be greater than a threshold, for example: zero, half a symbol, a symbol, 30 us, and/or the like.
  • Parallel and/or simultaneous transmissions may imply that transmissions are in the same subframe, include the same subframe and/or may overlap during a time period. Minor inaccuracies/errors in transmission time within a limited range may be accepted.
  • parallel transmission of a preamble and of other UL data, control packets and/or SRS transmission on cells in other TA groups could have many advantages.
  • the network may not need to coordinate the time when an RA is ordered on a cell of a TAG and with other UL transmissions in other TAGs. This may slightly increase UE complexity and it may make the power handling of the UE a bit more complex, but radio resources may be used more efficiently if parallel transmission is allowed.
  • Supporting parallel transmission of a preamble and transmission of other UL data or control messages may reduce the complexity in an eNB and increase uplink radio efficiency. Allowing parallel PRACH and PUSCH/PUCCH/SRS transmissions may reduce scheduling restrictions in an eNB.
  • a limitation applies that when a random access preamble is transmitted in a random access channel of a cell of a given TAG, no other parallel transmission is allowed in the cells belonging to the same TAG. For example, when a preamble is transmitted on an SCell of an sTAG no other
  • PUSCH packet and/or SRS signal may be transmitted in parallel with the preamble in the sTAG.
  • a UE configured with N active carriers and supporting multiple-TAG configuration may transmit some of following signals in parallel: k x PRACH; m x PUCCH; p x PUSCH; q x SRS signals.
  • the values of k, m, p, q depends on UE capability and configuration. In an example, K may be equal to zero or one; m may be equal to zero or one; p may be equal or less than N; and q may be equal or less than N.
  • Transmission rules may be define to constraints some parallel transmissions of the above signals.
  • PRACH, PUCCH, PUSCH If any of the PUCCH, PUSCH, and PRACH transmissions in a given TAG coincides with an SRS symbol transmission in a symbol of the given TAG, then SRS may be dropped. Therefore, no parallel transmission of SRS is allowed in a symbol of a given TAG, if any other signal is carried in the given TAG. Avoiding parallel transmission of a preamble with any other signal in the same TAG, and avoiding parallel transmission of an SRS signal with any other signal in the same TAG may simplify UE transmission operation.
  • a preamble may have a higher transmission priority compared with other uplink signals (PUCCH/SRS/PUSCH), and therefore may not be dropped because of other parallel transmissions.
  • SRS may have a lower transmission priority compared with other uplink signals (PUCCH/Preamble/PUSCH), and therefore may be dropped because of other parallel transmissions.
  • a UE if a UE is not configured to transmit in parallel PUCCH packet and PUSCH packet(s) then the above conditions may apply except that no parallel PUCCH and PUSCH transmission is allowed in the UE.
  • PRACH transmitted in a TAG with c cells can be transmitted in parallel with one PUCCH and up to (N-c) PUSCH packets. If PRACH preamble is transmitted in pTAG, no parallel transmission of PUCCH packet and the preamble is allowed. In general no uplink signals may be transmitted with preamble in the TAG that is used for preamble transmission. If a UE is not configured with parallel PUCCH and PUSCH channel transmission, then this limitation may be applied.
  • SRS transmission is dropped in a given TAG, if SRS transmission symbol coincides with an uplink transmission symbol (any of the preamble, PUCCH packet, and PUSCH) in the given TAG.
  • Multiple SRS signals may be transmitted in different cells of a given TAG in parallel with each other (assuming no PUCCH, PUSCH, and preamble is transmitted in parallel in the given TAG).
  • a shortened format of PUCCH may not coincide with SRS transmission, since a shortened PUCCH packet is not transmitted in the last symbol of a subframe. For example, if UE transmits in parallel an SRS signal, a preamble, and a PUSCH packet, then each of the SRS signal, the preamble, and the PUSCH packet is transmitted on a different cell group. In another example, if a UE transmits in parallel an SRS signal, a preamble, and a PUCCH packet, then PUCCH packet is transmitted on pTAG, preamble is transmitted on a first sTAG, and SRS signal is transmitted on a TAG different from pTAG and the first sTAG. In another example, if UE transmits in parallel an SRS signal and a PUSCH packet, then each of the SRS signal and the PUSCH packet is transmitted on a different cell group. Other examples could be provided based on the rules disclosed in this disclosure.
  • power scaling may be applied when the UE is in power limited scenario, for example when UE is in poor coverage areas.
  • RACH preamble may be transmitted on an SCell.
  • TTI where RACH preamble transmission or retransmissions may coincide with either PUCCH or PUSCH on PCell/SCell or both.
  • simultaneous PRACH on SCell with other UL transmissions may occur in a UE:
  • UE behaviour may be defined when total power is not sufficient. There may be multiple solutions to address this issue.
  • the priorities for power scaling between different channels may be determined. According to the priorities the powers may be scaled to ensure transmit
  • the PRACH may be assigned the highest priority.
  • UCI uplink control information
  • the order of priorities may be
  • PRACH has the highest priority.
  • the UE may scale I pusci i c W for the serving cell c in subframe i such that the condition
  • UE total configured maximum output power CMAX in subframe i and w ⁇ l ⁇ may be a scaling factor of ⁇ w ® ⁇ 1 .
  • Other functions in addition to linear value may be supported. For exam le, average power, and/or the like.
  • PUCCH transmission in subframe i ma y be lne ii near value of P J(i) or cou id be another function of the preamble transmission power on an uplink
  • the UE may scale I pusci i c W for the serving cells without UCI in subframe i such that the
  • some other power constraints may be applied to limit transmission power for a carrier below a maximum carrier transmission power. For example, when a simultaneous PUCCH and PUSCH on the same carrier is transmitted, the UE may perform a power scaling inside a carrier before applying the above power limitations on the overall transmit power.
  • SRS may not be transmitted (may be dropped) by the UE, when there is power constraint in the UE.
  • UE may not scale SRS power when SRS signal is transmitted in paralle with PUCCH packet, PUSCH packet, and/or a preamble.
  • UE may drop all SRSs transmitted in a symbol if the UE is power limited in the uplink for transmission of parallel SRS with PUCCH packet, PUSCH packet, and/or a preamble.
  • FIG. 12 is an example flow diagram illustrating a process for calculating transmission powers as per an aspect of an embodiment of the present invention.
  • a wireless device may receive control message(s) from a base station 1200.
  • the control message(s) may cause in the wireless device configuration of a plurality of cells comprising a primary cell and secondary cell(s).
  • the control message(s) may cause in the wireless device assignment of each of the secondary cell(s) to a cell group in a plurality of cell groups.
  • the plurality of cell groups may comprise a primary cell group and a secondary cell group.
  • the primary cell group may comprise a first subset of the plurality of cells.
  • the subset may comprise the primary cell.
  • the secondary cell group may comprise a second subset of the secondary cell(s).
  • the control message(s) may further causes in the wireless device configuration of a plurality of channel parameters for the following channels: the uplink control channel on the primary cell; the one uplink data channel(s); and an uplink random access channel on the first
  • the wireless device may receive a control command for transmission of a random access preamble on a first cell in the plurality of cells.
  • the random access preamble may be transmitted in parallel with at least one of the following parallel uplink transmissions: a first control packet on an uplink control channel of the primary cell; a second packet comprising uplink control information on an uplink data channel of one of the plurality of cells; and third packet(s) on one uplink data channel(s) of the plurality of cells.
  • the first cell may be the primary cell.
  • the wireless device may determine a
  • preamble transmission power for the random access preamble at block 1204.
  • the wireless device may obtain a transmission power of the parallel uplink transmission(s) according to a series of priorities as follows.
  • the random access preamble transmission may have a first priority.
  • the first control packet may have a second priority lower than the first priority.
  • the second packet may have a third priority lower than the second priority.
  • the third packet(s) may have a fourth priority lower than the third priority.
  • the priorities may be employed by the wireless device to reduce or scale linear transmission power of one or more of the parallel transmission(s) such that an updated value of the total calculated transmission power is equal to or less than the predefined value.
  • the total calculated transmission power may be calculated for a subframe.
  • the scaling linear transmission power may comprise scaling linear transmission power by a scaling factor: greater than or equal to zero; and smaller than or equal to one.
  • transmission power may comprise adding all of the following transmission powers: a linear transmission power of the random access preamble; a linear transmission power of the first control packet if the first control packet is transmitted; a linear transmission power of the second packet if the second packet is transmitted; and a linear transmission power of the third packet(s) if the third packet(s) are transmitted.
  • a calculated linear transmission power of the first control packet may be equal to a minimum of: the linear transmission power of the first control packet; and the predefined value minus the linear transmission power of the random access preamble.
  • the parallel uplink transmission(s) are the signals transmitted in parallel "with" the random access preamble (preamble is inherently not in the parallel uplink transmission(s) but is transmitted in parallel with the parallel uplink transmission(s)).
  • a calculated linear transmission power of the second packet may be equal to a minimum of: the linear transmission power of the second packet; and the predefined value minus the linear transmission power of the random access preamble.
  • a calculated linear transmission power of the first control packet may be equal to a minimum of: the linear transmission power of the first control packet; and the predefined value minus the linear transmission power of the random access preamble.
  • a calculated linear transmission power of the second control packet may be equal to a minimum of: the linear transmission power of the second control packet; and the predefined value minus a sum of the linear transmission power of the random access preamble and the calculated linear transmission power of the first control packet.
  • a calculated linear transmission power of the first control packet may be equal to a minimum of: the linear transmission power of the first control packet; and the predefined value minus the linear transmission power of the random access preamble.
  • a calculated linear transmission power for each of the third packet(s) may be calculated by scaling the linear transmission power of each of the third packet(s) by a scaling factor such that the total calculated transmission power is equal to or less than the predefined value, the scaling factor being equal to or less than one.
  • a wireless device may receive control message(s) from a base station at 1200.
  • the control message(s) may cause in the wireless device the configuration of a plurality of cells.
  • the plurality of cells may comprise a primary cell and secondary cell(s).
  • the control message(s) may cause in the wireless device the assignment of each of the secondary cell(s) to a cell group in a plurality of cell groups.
  • the plurality of cell groups may comprise a primary cell group and a secondary cell group.
  • the primary cell group may comprise a first subset of the plurality of cells.
  • the subset may comprise the primary cell.
  • the secondary cell group may comprise a second subset of the secondary cell(s).
  • the wireless device may receive a control command for transmission of a random access preamble on a first cell in the plurality of cells.
  • the random access preamble may be transmitted in parallel with at least one of the following parallel uplink transmissions: a first control packet; a second packet; and third packet(s).
  • the first control packet may be on an uplink control channel of the primary cell.
  • the second packet may comprise uplink control information on an uplink data channel of one of the plurality of cells.
  • the third packet(s) may be on uplink data channel(s) of the plurality of cells.
  • the wireless device may determine a transmission power for the random access preamble.
  • the wireless device may reduce or scale the linear transmission power of one or more of the parallel uplink transmission(s) according to a predefined rule.
  • the predefined rule may consider a higher priority for the transmission power of the random access preamble compared with a transmission priority of: the first control packet; the second packet; and the third packet(s).
  • the reduction or scaling of the linear transmission power may be performed over a period of one subframe.
  • the calculation of the total calculated transmission power may comprises adding all of the following transmission powers: a linear transmission power of the random access preamble; a linear transmission power of the first control packet if the first control packet is transmitted; a linear transmission power of the second packet if the second packet is transmitted; and a linear transmission power of the third packet(s) if the third packet(s) are transmitted.
  • a calculated linear transmission power of the first control packet may be equal to a minimum of: the linear transmission power of the first control packet; and the predefined value minus the linear transmission power of the random access preamble.
  • a calculated linear transmission power of the second packet may be equal to a minimum of: the linear transmission power of the second packet; and the predefined value minus the linear transmission power of the random access preamble.
  • the wireless device may comprise
  • a wireless device may receive control message(s) from a base station 1200.
  • the control message(s) may cause in the wireless device configuration of a plurality of cells comprising a primary cell and secondary cell(s).
  • the control message(s) may cause in the wireless device assignment of each of the secondary cell(s) to a cell group in a plurality of cell groups.
  • the plurality of cell groups may comprise a primary cell group and a secondary cell group.
  • the primary cell group may comprise a first subset of the plurality of cells. The subset may comprise the primary cell.
  • the secondary cell group may comprise a second subset of the secondary cell(s).
  • the control message(s) may further causes in the wireless device configuration of a plurality of channel parameters for the following channels: the uplink control channel on the primary cell; the uplink data channel(s); and an uplink random access channel on the first cell.
  • the wireless device may receive a control command for transmission of a random access preamble on a first cell in the plurality of cells.
  • the random access preamble may be transmitted in parallel with at least one of the following parallel uplink transmissions: a first control packet on an uplink control channel of the primary cell; a second packet comprising uplink control information on an uplink data channel of one of the plurality of cells; and the third packet(s) on the uplink data channel(s) of the plurality of cells.
  • the first cell may be the primary cell.
  • the wireless device may determine a preamble transmission power for the random access preamble at block 1204.
  • the wireless device may reduce or scale linear transmission power of one or more of the parallel uplink transmission(s) according to a predefined rule considering a higher priority for the transmission power of the random access preamble compared with a transmission priority of: the first control packet; the second packet; and the third packet(s).
  • the predefined value may be a configured maximum transmission power of the wireless device.
  • a configured sounding reference signal transmission may be dropped if the total calculated transmission power exceeds a predefined value.
  • a transmission period of the random access preamble may be more than one subframe.
  • a transmission period of the random access preamble may overlap a first subframe and a second subframe.
  • FIG. 13 is an example flow diagram illustrating a process for sounding reference signal transmission as per an aspect of an embodiment of the present invention.
  • a wireless device may receive control message(s) from a base station at 1300. The control message(s) may cause in the wireless device the configuration of a plurality of cells.
  • the plurality of cells may comprise a primary cell and secondary cell(s).
  • the control message(s) may cause in the wireless device the assignment of each of the secondary cell(s) to a cell group in a plurality of cell groups.
  • the plurality of cell groups may comprise a primary cell group and a secondary cell group.
  • the primary cell group may comprise a first subset of the plurality of cells.
  • the subset may comprise the primary cell.
  • a secondary cell group may comprise a second subset of the secondary cell(s).
  • the control message(s) may cause in the wireless device configuration of transmissions of sounding reference signals on a first cell in the plurality of cells.
  • the first cell may be assigned to a first cell group in the plurality of cell groups.
  • the control message(s) may cause in the wireless device configuration of random access channel(s).
  • the control message(s) may cause in the wireless device configuration of data channel(s).
  • the first random access preamble may be transmitted on one of the random access channel(s) and the first uplink data packet may be transmitted on one of the data channel(s).
  • the first cell group may be one of: the primary cell group; and the secondary cell group.
  • the wireless device may transmit one or more of the sounding reference signals on the first cell in parallel with the transmission of at least one of: a first random access preamble; and a first uplink data packet.
  • the sounding reference signals may be configured to be transmitted during a time period.
  • the one or more of the sounding reference signals may be transmitted on the last symbol of a plurality of subframes.
  • he sounding reference signals may be type zero sounding reference signals and/or type one sounding reference signals.
  • a first sounding reference signal may be one of the sounding reference signals.
  • the wireless device may be configured to not transmit the first sounding reference signal on the first cell if the first sounding reference signal transmission and a second random access preamble transmission in the first cell group coincide in the same subframe.
  • the first SRS may be dropped because the first SRS transmission coincides with the second random preamble transmission and both are scheduled for transmission in the same first cell group.
  • the wireless device may be configured to not transmit the first sounding reference signal on the first cell if the wireless device has insufficient power to transmit the first sounding reference signal in parallel with a third random access preamble when the third random access preamble transmission and the first sounding reference signal coincide in the same subframe.
  • SRS signal may have a lower transmission priority compared with any of the PUCCH, random access preamble, PUSCH packet, and then UE does not have insufficient power to transmit SRS with any of these signals, the UE may drop SRS transmission.
  • the wireless device may be configured to not transmit the first sounding reference signal on the first cell if the wireless device has insufficient power to transmit the first sounding reference signal in parallel with a second uplink data packet transmission when the second uplink data packet transmission and the first sounding reference signal coincide in the same subframe.
  • the first cell group may be out of sync when the second random access preamble is transmitted on the first cell group.
  • transmission of said first SRS signal is dropped if the first sounding reference signal transmission and a third uplink data packet transmission in the first cell group coincide in the same subframe.
  • Transmission of said first SRS signal is dropped if the first sounding reference signal transmission and an uplink physical control packet transmission in the first cell group may coincide in the same subframe.
  • an SRS signal may be dropped if any of PUCCH packet, PUSCH packet, and preamble packet coincides with SRS transmission symbol in the same cell group.
  • the wireless device may give the sounding reference signal transmission power a lower priority compared with: a priority of a transmission power of the third random access preamble; and a priority of a transmission power of the second uplink data packet transmission.
  • the first random access preamble may be transmitted on a second cell of a second cell group.
  • the second cell group may be different from the first cell group.
  • the first uplink data packet may be transmitted on a second cell of a second cell group.
  • the second cell group may be different from the first cell group.
  • a wireless device may receive control message(s) from a base station at block 1300.
  • the control message(s) may cause in the wireless device the configuration of a plurality of cells comprising a primary cell and secondary cell(s).
  • the control message(s) may cause in the wireless device assignment of each of the secondary cell(s) to a cell group in a plurality of cell groups.
  • the control message(s) may cause in the wireless device the configuration of transmissions of sounding reference signals on a first cell in the plurality of cells.
  • the first cell may be assigned to a first cell group in the plurality of cell groups.
  • FIG. 14 is an example flow diagram illustrating parallel transmission of a random access preamble with other uplink packets as per an aspect of an embodiment of the present invention.
  • a wireless device may receive control message(s) from a base station at 1400.
  • the control message(s) may cause in the wireless device the configuration of a plurality of cells.
  • the plurality of cells may comprise a primary cell and secondary cell(s).
  • the control message(s) may cause in the wireless device the assignment of each of the secondary cell(s) to a cell group in a plurality of cell groups.
  • the plurality of cell groups may comprise a primary cell group and a secondary cell group.
  • the primary cell group may comprise a first subset of the plurality of cells.
  • the subset may comprise the primary cell.
  • the secondary cell group may comprise a second subset of the secondary cell(s).
  • the control message(s) may cause in the wireless device the configuration of random access channel(s).
  • the control message(s) may cause in the wireless device the configuration of uplink data channel(s) on the plurality of cells.
  • the control message(s) may cause in the wireless device the configuration of an uplink control channel of the primary cell.
  • the control message(s) may further cause in the wireless device the configuration of a plurality of channel parameters for: the uplink control channel on the primary cell; the uplink data channel(s); and an uplink random access channel on the first cell.
  • the wireless device may receive a control command for transmission of a random access preamble on a first cell in the plurality of cells.
  • a fourth packet may be scheduled for parallel uplink transmission with the random access preamble transmission.
  • the fourth packet may be a first control packet on the uplink control channel.
  • the fourth packet may be a second packet.
  • the second packet may comprise uplink control information on an uplink data channel in the uplink channel(s).
  • the fourth packet may be a third packet on an uplink data channel of the plurality of cells.
  • the first cell may be the primary cell or a secondary cell.
  • the wireless device may transmit the random access preamble on one of the random access channel(s).
  • the wireless device may transmit the fourth packet in parallel with the random access preamble, unless the random access preamble and the fourth packet are scheduled for transmission in the same cell group. It is assumed that the wireless device is capable of transmission of the fourth packet if the random access preamble was not scheduled in the same subframe. It is also assumed that the wireless device has at least some power for transmission of the fourth packet according to a power allocation scheme. Examples of power allocation schemes and power prioritization are disclosed in the embodiment. Therefore, the assumption is that other reasons for dropping transmission of the fourth packet do not exist.
  • the wireless device may reduce or scale the transmission power of the fourth packet such that a total calculated transmission power is equal to or less than a predefined value.
  • the transmission power priorities may be employed by the wireless device to reduce or scale the linear transmission power of the packet such that a total calculated transmission power is equal to or less than a predefined value.
  • the random access preamble transmission may have a higher priority compared with a transmission priority of the packet.
  • the reduction and scaling of the linear transmission power may be performed over a period of one subframe.
  • the first cell group may be out of sync when the random access preamble is transmitted on the first cell group.
  • the transmission period of the random access preamble may be more than one subframe.
  • the transmission period of the random access preamble may overlap a first subframe and a second subframe.
  • the wireless device may transmit each of the following in parallel only if they are transmitted on different cell groups: the random access preamble; the first control packet; and a sounding reference signal.
  • the wireless device may transmit each of the following in parallel only if they are transmitted on different cell groups: the random access preamble; the third data packet; and a sounding reference signal.
  • a wireless device may receive control message(s) from a base station at 1400.
  • the control message(s) may cause in the wireless device the configuration of a plurality of cells.
  • the plurality of cells may comprise a primary cell and secondary cell(s).
  • the control message(s) may cause in the wireless device the assignment of each of the secondary cell(s) to a cell group in a plurality of cell groups.
  • the plurality of cell groups may comprise a comprise primary cell group and a secondary cell group.
  • the primary cell group may comprise the primary cell.
  • the secondary cell group may comprise a subset of the secondary cell(s).
  • the wireless device may receive a control command for transmission of a random access preamble on a first cell in the plurality of cells.
  • a fourth packet may be scheduled for parallel uplink transmission with the random access preamble transmission.
  • the fourth packet may be a first control packet on the uplink control channel of the primary cell.
  • the fourth packet may be a second packet.
  • the second packet may comprise uplink control information on an uplink data channel of one of the plurality of cells.
  • the fourth packet may be a third packet on an uplink data channel of the plurality of cells.
  • the wireless device may transmit the random access preamble.
  • the wireless device may transmit the fourth packet in parallel with the random access preamble, unless the random access preamble and the fourth packet are scheduled for transmission in the same cell group.
  • a transmission period of the random access preamble may overlap a first subframe and a second subframe.
  • the wireless device may transmit each of the following in parallel only if they are transmitted on different cell groups: the random access preamble; the first control packet; and a sounding reference signal.
  • the wireless device may transmit each of the following in parallel only if they are transmitted on different cell groups: the random access preamble; the third data packet; and a sounding reference signal.
  • the wireless device may comprise
  • the communication interface(s), processor(s), and memory may store instructions.
  • the processor(s) may execute the instructions to cause actions described herein.
  • the random access procedure may be initiated by a PDCCH order or by the MAC sublayer itself. Random access procedure on an SCell may be initiated by a PDCCH order. If a UE receives a PDCCH transmission consistent with a PDCCH order masked with its C-RNTI (radio network temporary identifier), and for a specific serving cell, the UE may initiate a random access procedure on this serving cell.
  • C-RNTI radio network temporary identifier
  • a PDCCH order or RRC optionally indicate the ra-Preamblelndex and the ra-PRACH-Masklndex; and for random access on an SCell, the PDCCH order indicates the ra-Preamblelndex with a value different from zero and the ra-PRACH-Masklndex.
  • the PDCCH order indicates the ra-Preamblelndex with a value different from zero and the ra-PRACH-Masklndex.
  • the procedure may use some of the following information: a) the available set of PRACH resources for the transmission of the random access preamble, prach-Configlndex., b) for PCell, the groups of random access preambles and/or the set of available random access preambles in each group, c) for PCell, the preambles that are contained in random access preambles group A and Random Access Preambles group B are calculated, d) the RA response window size ra- ResponseWindowSize, e) the power-ramping factor powerRampingStep, f) the maximum number of preamble transmission preambleTransMax, g) the initial preamble power preamblelnitialReceivedTargetPower, h) the preamble format based offset
  • DELTA_PREAMBLE i) for PCell, the maximum number of Msg3 HARQ transmissions maxHARQ-Msg3Tx, j) for PCell, the Contention Resolution Timer mac- ContentionResolutionTimer. These parameters may be updated from upper layers before each Random Access procedure is initiated.
  • the Random Access procedure may be performed as follows: Flush the Msg3 buffer; set the Random Access procedure
  • PREAMBLE_TRANSMISSION_COUNTER 1; set the backoff parameter value in the UE to 0 ms; for the RN (relay node), suspend any RN subframe configuration; proceed to the selection of the Random Access Resource.
  • the Random Access Resource selection procedure may be performed as follows. If ra-Preamblelndex (Random Access Preamble) and ra-PRACH-Masklndex (PRACH Mask Index) have been explicitly signalled and ra-Preamblelndex is not zero, then the Random Access Preamble and the PRACH Mask Index may be those explicitly signalled. Otherwise, the Random Access Preamble may be selected by the UE.
  • ra-Preamblelndex Random Access Preamble
  • PRACH Mask Index PRACH Mask Index
  • the UE may determine the next available subframe containing PRACH permitted by the restrictions given by the prach-Configlndex, the PRACH Mask Index and physical layer timing requirements (a UE may take into account the possible occurrence of measurement gaps when determining the next available PRACH subframe). If the transmission mode is TDD and the PRACH Mask Index is equal to zero, then if ra-Preamblelndex was explicitly signalled and it was not 0 (i.e., not selected by MAC), then randomly select, with equal probability, one PRACH from the PRACHs available in the determined subframe. Else, the UE may randomly select, with equal probability, one PRACH from the PRACHs available in the determined subframe and the next two consecutive subframes.
  • a UE may determine a PRACH within the determined subframe in accordance with the requirements of the PRACH Mask Index. Then the UE may proceed to the transmission of the Random Access Preamble.
  • PRACH mask index values may range for example from 0 to 16.
  • PRACH mask index value may determine the allowed PRACH resource index that may be used for transmission.
  • PRACH mask index 0 may mean that all PRACH resource indeces are allowed; or PRACH mask index 1 may mean that PRACH resource index 0 may be used.
  • PRACH mask index may have different meaning in TDD and FDD systems.
  • the random-access procedure may be performed by UE setting
  • PREAMBLE_RECEIVED_TARGET_POWER to preamblelnitialReceivedTargetPower + DELT A_PRE AMB LE + (PREAMBLE_TRANSMISSION_COUNTER - 1) *
  • the UE may instruct the physical layer to transmit a preamble using the selected PRACH, corresponding RA-RNTI, preamble index and
  • the UE may monitor the PDCCH of the PCell for random access response(s) identified by the RA-RNTI (random access radio network identifier) a specific RA-RNTI defined below, in the random access response (RAR) window which may start at the subframe that contains the end of the preamble transmission plus three subframes and has length ra-ResponseWindowSize subframes.
  • RA-RNTI random access radio network identifier
  • RAR random access response
  • RA-RNTI 1 + t_id+10*f_id.
  • t_id is the index of the first subframe of the specified PRACH (0 ⁇ t_id ⁇ 10)
  • f_id is the index of the specified PRACH within that subframe, in ascending order of frequency domain (0 ⁇ f_id ⁇ 6).
  • the UE may stop monitoring for RAR(s) after successful reception of a RAR containing random access preamble identifiers that matches the transmitted random access preamble.
  • the UE may regardless of the possible occurrence of a measurement gap: if the RAR contains a backoff indicator (BI) subheader, set the backoff parameter value in the UE employing the BI field of the backoff indicator subheader, else, set the backoff parameter value in the UE to zero ms.
  • BI backoff indicator
  • the UE may consider this RAR reception successful and apply the following actions for the serving cell where the random access preamble was transmitted: process the received riming advance command for the cell group in which the preamble was transmitted, indicate the preamblelnitialReceivedTargetPower and the amount of power ramping applied to the latest preamble transmission to lower layers (i.e.,
  • the random access response reception may considered not successful. If RAR is not received, UE may increment PREAMBLE_TRANSMISSION_COUNTER by 1. If
  • PREAMBLE_TRANSMISSION_COUNTER preambleTransMax + 1 and random access preamble is transmitted on the PCell, then UE may indicate a random access problem to upper layers (RRC). This may result in radio link failure. If
  • PREAMBLE_TRANSMISSION_COUNTER preambleTransMax + 1 and the random access preamble is transmitted on an SCell, then UE may consider the random access procedure unsuccessfully completed. UE may stay in RRC connected mode and keep the RRC connection active eventhough a random access procedure unsuccessfully completed on a secondary TAG. According to some of the various aspects of embodiments, at completion of the random access procedure, the UE may discard explicitly signalled ra- Preamblelndex and ra-PRACH-Masklndex, if any; and flush the HARQ buffer used for transmission of the MAC PDU in the Msg3 buffer. In addition, the RN may resume the suspended RN subframe configuration, if any.
  • the UE may have a configurable timer timeAlignmentTimer per TAG.
  • the timeAlignmentTimer is used to control how long the UE considers the Serving Cells belonging to the associated TAG to be uplink time aligned (in-sync).
  • the UE may apply the riming advance command for the indicated TAG, and start or restart the timeAlignmentTimer associated with the indicated TAG.
  • the UE may apply the timing advance command for this TAG, and may start or restart the timeAlignmentTimer associated with this TAG.
  • the UE may: flush all HARQ buffers for all serving cells; notify RRC to release
  • PUCCH/SRS for all serving cells; clear any configured downlink assignments and uplink grants; and consider all running timeAlignmentTimers as expired.
  • timeAlignmentTimer associated with an sTAG expires, then for all Serving Cells belonging to this TAG, the UE may flush all HARQ buffers; and notify RRC to release SRS.
  • the UE may not perform any uplink transmission on a serving Cell except the random access preamble transmission when the timeAlignmentTimer associated with the TAG to which this serving cell belongs is not running.
  • the timeAlignmentTimer associated with the pTAG is not running, the UE may not perform any uplink transmission on any serving cell except the random access preamble transmission on the PCell.
  • a UE stores or maintains N_TA (current timing advance value of an sTAG) upon expiry of associated timeAlignmentTimer.
  • the UE may apply a received timing advance command MAC control element and starts associated timeAlignmentTimer. Transmission of the uplink radio frame number z' from the UE may start ⁇ TA + ⁇ ? ⁇ offset ) x T s seconds before the start of the corresponding downlink radio frame at the UE, where 0 ⁇ ⁇ TA ⁇ 20512 .
  • the UE may adjust uplink transmission timing for PUCCH/PUSCH/SRS of the primary cell based on the received timing advance command.
  • the UL transmission timing for PUSCH/SRS of a secondary cell may be the same as the primary cell if the secondary cell and the primary cell belong to the same TAG.
  • the UE may adjust uplink transmission timing for PUSCH/SRS of secondary cells in the TAG based on the received timing advance command where the UL transmission timing for PUSCH /SRS is the same for all the secondary cells in the TAG.
  • the timing advance command for a TAG may indicates the change of the uplink timing relative to the current uplink timing for the TAG as multiples of 16Ts (Ts: sampling time unit).
  • Ts sampling time unit
  • the start timing of the random access preamble may obtained employing a downlink synchronization time in the same TAG.
  • adjustment of NTA value by a positive or a negative amount indicates advancing or delaying the uplink transmission timing for the TAG by a given amount respectively.
  • the corresponding adjustment of the uplink transmission timing may apply from the beginning of subframe n+6.
  • the UE may complete transmission of subframe n and not transmit the overlapped part of subframe n+1. If the received downlink timing changes and is not compensated or is only partly compensated by the uplink timing adjustment without timing advance command, the UE may change NTA accordingly.
  • Downlink frames and subframes of downlink carriers are time aligned (by the base station) in carrier aggregation and multiple TAG configuration.
  • Time alignment errors may be tolerated to some extend. For example, for intra-band contiguous carrier aggregation, time alignment error may not exceed 130 ns. In another example, for intra-band non-contiguous carrier aggregation, time alignment error may not exceed 260 ns. In another example, for inter-band carrier aggregation, time alignment error may not exceed 1.3 ⁇ 8.
  • the UE may have capability to follow the frame timing change of the connected base station.
  • the uplink frame transmission may take place ⁇ TA + ⁇ ⁇ offset ) x r s before the reception of the first detected path (in time) of the corresponding downlink frame from the reference cell.
  • the UE may be configured with a pTAG containing the PCell.
  • the pTAG may also contain one or more SCells, if configured.
  • the UE may also be configured with one or more sTAGs, in which case the pTAG may contain one PCell and the sTAG may contain at least one SCell with configured uplink.
  • UE may use the PCell as the reference cell for deriving the UE transmit timing for cells in the pTAG.
  • the UE may employ a synchronization signal on the reference cell to drive downlink timing.
  • uplink physical channel(s) may correspond to a set of resource elements carrying information originating from higher layers.
  • the following example uplink physical channel(s) may be defined for uplink: a) Physical Uplink Shared Channel (PUSCH), b) Physical Uplink Control Channel (PUCCH), c) Physical Random Access Channel (PRACH), and/or the like.
  • Uplink physical signal(s) may be used by the physical layer and may not carry information originating from higher layers. For example, reference signal(s) may be considered as uplink physical signal(s).
  • Transmitted signal(s) in slot(s) may be described by one or several resource grids including, for example, subcarriers and SC-FDMA or OFDMA symbols.
  • Antenna port(s) may be defined such that the channel over which symbol(s) on antenna port(s) may be conveyed and/or inferred from the channel over which other symbol(s) on the same antenna port(s) is/are conveyed. There may be one resource grid per antenna port. The antenna port(s) used for
  • transmission of physical channel(s) or signal(s) may depend on the number of antenna port(s) configured for the physical channel(s) or signal(s).
  • cell search may be the procedure by which a wireless device may acquire time and frequency synchronization with a cell and may detect the physical layer Cell ID of that cell (transmitter).
  • An example embodiment for synchronization signal and cell search is presented below.
  • a cell search may support a scalable overall transmission bandwidth corresponding to 6 resource blocks and upwards.
  • Primary and secondary synchronization signals may be transmitted in the downlink and may facilitate cell search.
  • 504 unique physical-layer cell identities may be defined using synchronization signals.
  • the physical-layer cell identities may be grouped into 168 unique physical-layer cell-identity groups, group(s) containing three unique identities. The grouping may be such that physical-layer cell identit(ies) is part of a physical-layer cell-identity group.
  • a physical-layer cell identity may be defined by a number in the range of 0 to 167, representing the physical-layer cell-identity group, and a number in the range of 0 to 2, representing the physical-layer identity within the physical- layer cell-identity group.
  • the synchronization signal may include a primary
  • physical downlink control channel(s) may carry transport format, scheduling assignments, uplink power control, and other control information.
  • PDCCH may support multiple formats. Multiple PDCCH packets may be transmitted in a subframe.
  • scheduling control packet(s) may be transmitted for packet(s) or group(s) of packets transmitted in downlink shared channel(s). Scheduling control packet(s) may include information about subcarriers used for packet transmission(s).
  • PDCCH may also provide power control commands for uplink channels.
  • PDCCH channel(s) may carry a plurality of downlink control packets in subframe(s). Enhance PDCCH may be implemented in a cell as an option to carrier control information.
  • PHICH may carry the hybrid- ARQ (automatic repeat request) ACK/NACK.
  • PCFICH, PHICH, PDCCH, enhanced PDCCH, and/or PDSCH may be supported.
  • the configurations presented here are for example purposes.
  • resources PCFICH, PHICH, and/or PDCCH radio resources may be transmitted in radio resources including a subset of subcarriers and pre-defined time duration in each or some of the subframes.
  • PUSCH resource(s) may start from the first symbol.
  • radio resource configuration(s) for PUSCH, PUCCH, and/or PRACH (physical random access channel) may use a different configuration.
  • channels may be time multiplexed, or time/frequency multiplexed when mapped to uplink radio resources.
  • the physical layer random access preamble may comprise a cyclic prefix of length Tcp and a sequence part of length Tseq.
  • the parameter values may be pre-defined and depend on the frame structure and a random access configuration.
  • Tcp may be 0.1 msec
  • Tseq may be 0.9 msec.
  • Higher layers may control the preamble format.
  • the transmission of a random access preamble, if triggered by the MAC layer, may be restricted to certain time and frequency resources.
  • the start of a random access preamble may be aligned with the start of the corresponding uplink subframe at a wireless device.
  • random access preambles may be generated from
  • Zadoff-Chu sequences with a zero correlation zone generated from one or several root Zadoff-Chu sequences.
  • the preambles may also be generated using other random sequences such as Gold sequences.
  • the network may configure the set of preamble sequences a wireless device may be allowed to use.
  • the physical layer random access procedure may include the transmission of random access preamble(s) and random access response(s).
  • Remaining message(s) may be scheduled for transmission by a higher layer on the shared data channel and may not be considered part of the physical layer random access procedure.
  • a random access channel may occupy 6 resource blocks in a subframe or set of consecutive subframes reserved for random access preamble transmissions.
  • layer 1 procedure may be triggered upon request of a preamble transmission by higher layers; 2) a preamble index, a target preamble received power, a corresponding RA-RNTI (random access-radio network temporary identifier) and/or a PRACH resource may be indicated by higher layers as part of a request; 3) a preamble transmission power P_PRACH may be determined; 4) a preamble sequence may be selected from the preamble sequence set using the preamble index; 5) a single preamble may be transmitted using selected preamble sequence(s) with transmission power
  • P_PRACH on the indicated PRACH resource 6) detection of a PDCCH with the indicated RAR may be attempted during a window controlled by higher layers; and/or the like. If detected, the corresponding downlink shared channel transport block may be passed to higher layers.
  • the higher layers may parse transport block(s) and/or indicate an uplink grant to the physical layer(s).
  • a random access procedure may be initiated by a physical downlink control channel (PDCCH) order and/or by the MAC sublayer in a wireless device. If a wireless device receives a PDCCH transmission consistent with a PDCCH order masked with its radio identifier, the wireless device may initiate a random access procedure. Preamble transmission(s) on physical random access channel(s) (PRACH) may be supported on a first uplink carrier and reception of a PDCCH order may be supported on a first downlink carrier.
  • PDCCH physical downlink control channel
  • a wireless device Before a wireless device initiates transmission of a random access preamble, it may access one or many of the following types of information: a) available set(s) of PRACH resources for the transmission of a random access preamble; b) group(s) of random access preambles and set(s) of available random access preambles in group(s); c) random access response window size(s); d) power-ramping factor(s); e) maximum number(s) of preamble transmission(s); f) initial preamble power; g) preamble format based offset(s); h) contention resolution timer(s); and/or the like. These parameters may be updated from upper layers or may be received from the base station before random access procedure(s) may be initiated.
  • a wireless device may select a random access preamble using available information.
  • the preamble may be signaled by a base station or the preamble may be randomly selected by the wireless device.
  • the wireless device may determine the next available subframe containing PRACH permitted by restrictions given by the base station and the physical layer timing requirements for TDD or FDD. Subframe timing and the timing of transmitting the random access preamble may be determined based, at least in part, on synchronization signals received from the base station and/or the information received from the base station.
  • the wireless device may proceed to the transmission of the random access preamble when it has determined the timing.
  • the random access preamble may be transmitted on a second plurality of subcarriers on the first uplink carrier.
  • a wireless device may monitor the PDCCH of a primary carrier for random access response(s), in a random access response window. There may be a pre-known identifier in PDCCH that identifies a random access response. The wireless device may stop monitoring for random access response(s) after successful reception of a random access response containing random access preamble identifiers that matches the transmitted random access preamble and/or a random access response address to a wireless device identifier.
  • a base station random access response may include a time alignment command. The wireless device may process the received time alignment command and may adjust its uplink transmission timing according the time alignment value in the command.
  • a time alignment command may be coded using 11 bits, where an amount of the time alignment may be based on the value in the command.
  • the base station may provide the wireless device a grant for uplink transmission.
  • the random access response reception may be considered unsuccessful and the wireless device may, based on the backoff parameter in the wireless device, select a random backoff time and delay the subsequent random access transmission by the backoff time, and may retransmit another random access preamble.
  • a wireless device may transmit packets on an uplink carrier.
  • Uplink packet transmission timing may be calculated in the wireless device using the timing of synchronization signal(s) received in a downlink.
  • the wireless device may adjust its uplink transmission timing.
  • the timing alignment command may indicate the change of the uplink timing relative to the current uplink timing.
  • the uplink transmission timing for an uplink carrier may be determined using time alignment commands and/or downlink reference signals.
  • a time alignment command may indicate timing adjustment for transmission of signals on uplink carriers.
  • a time alignment command may use 6 bits. Adjustment of the uplink timing by a positive or a negative amount indicates advancing or delaying the uplink transmission timing by a given amount respectively.
  • control message(s) or control packet(s) may be scheduled for transmission in a physical downlink shared channel
  • PDSCH and/or physical uplink shared channel PUSCH may carry control and data message(s)/packet(s).
  • Control message(s) and/or packet(s) may be processed before transmission.
  • the control message(s) and/or packet(s) may be fragmented or multiplexed before transmission.
  • a control message in an upper layer may be processed as a data packet in the MAC or physical layer.
  • system information block(s), radio resource control messages, and data traffic may be scheduled for transmission in PDSCH.
  • a wireless device may be
  • the base station and/or wireless device may activate and/or deactivate the configured carriers.
  • One of the carriers (the primary carrier) may always be activated.
  • Other carriers may be deactivated by default and/or may be activated by a base station when needed.
  • a base station may activate and deactivate carriers by sending an activation/deactivation MAC control element.
  • the UE may maintain a carrier deactivation timer per configured carrier and deactivate the associated carrier upon its expiry. The same initial timer value may apply to instance(s) of the carrier deactivation timer.
  • the initial value of the timer may be configured by a network.
  • the configured carriers may be initially deactivated upon addition and after a handover.
  • the wireless device may activate the carrier, and/or may apply normal carrier operation including: sounding reference signal transmissions on the carrier (if the carrier is uplink time aligned), CQI (channel quality indicator)/PMI(precoding matrix indicator)/RI(ranking indicator) reporting for the carrier, PDCCH monitoring on the carrier, PDCCH monitoring for the carrier, start or restart the carrier deactivation timer associated with the carrier, and/or the like.
  • the base station or device may deactivate the carrier, and may stop the carrier deactivation timer associated with the carrier, and/or may flush HARQ buffers associated with the carrier. If PDCCH on a carrier scheduling the activated carrier indicates an uplink grant or a downlink assignment for the activated carrier, the device may restart the carrier deactivation timer associated with the carrier.
  • the wireless device may not transmit SRS (sounding reference signal) for the carrier, may not report CQI/PMI/RI for the carrier, may not transmit on UL-SCH for the carrier, may not monitor the PDCCH on the carrier, and/or may not monitor the PDCCH for the carrier.
  • SRS sounding reference signal
  • a process to assign subcarriers to data packets may be executed by a MAC layer scheduler.
  • the decision on assigning subcarriers to a packet may be made based on data packet size, resources required for transmission of data packets (number of radio resource blocks), modulation and coding assigned to data packet(s), QoS required by the data packets (i.e. QoS parameters assigned to data packet bearer), the service class of a subscriber receiving the data packet, or subscriber device capability, a combination of the above, and/or the like.
  • packets may be referred to service data units and/or protocols data units at Layer 1 , Layer 2 and/or Layer 3 of the
  • Layer 2 in an LTE network may include three sub-layers: PDCP sub-layer, RLC sub-layer, and MAC sub-layer.
  • a layer 2 packet may be a PDCP packet, an RLC packet or a MAC layer packet.
  • Layer 3 in an LTE network may be Internet Protocol (IP) layer, and a layer 3 packet may be an IP data packet. Packets may be transmitted and received via an air interface physical layer.
  • a packet at the physical layer may be called a transport block.
  • Many of the various embodiments may be implemented at one or many different communication network layers. For example, some of the actions may be executed by the PDCP layer and some others by the MAC layer or PHY layer.
  • a radio bearer may be a GBR (guaranteed bit rate) bearer and/or a non-GBR bearer.
  • a GBR and/or guaranteed bit rate bearer may be employed for transfer of real-time packets, and/or a non-GBR bearer may be used for transfer of non-real-time packets.
  • the non-GBR bearer may be assigned a plurality of attributes including: a scheduling priority, an allocation and retention priority, a portable device aggregate maximum bit rate, and/or the like. These parameters may be used by the scheduler in scheduling non-GBR packets.
  • GBR bearers may be assigned attributes such as delay, jitter, packet loss parameters, and/or the like.
  • the transmitter in the disclosed embodiments of the present invention may be a wireless device (also called user equipment), a base station (also called eNodeB), a relay node transmitter, and/or the like.
  • the receiver in the disclosed embodiments of the present invention may be a wireless device (also called user equipment-UE), a base station (also called eNodeB), a relay node receiver, and/or the like.
  • the MAC layer in some wireless device(s) may report buffer size(s) of either a single Logical Channel Group (LCG) or a group of LCGs to a base station.
  • An LCG may be a group of logical channels identified by an LCG ID. The mapping of logical channel(s) to LCG may be set up during radio configuration.
  • Buffer status report(s) may be used by a MAC scheduler to assign radio resources for packet transmission from wireless device(s).
  • HARQ and ARQ processes may be used for packet retransmission to enhance the reliability of radio transmission and reduce the overall probability of packet loss.
  • parameters may comprise one or more objects, and each of those objects may comprise one or more other objects.
  • IE Information elements
  • N comprises parameter (IE) M
  • IE parameter (IE) K
  • IE) K comprises parameter (information element) J
  • N comprises K
  • N comprises J
  • modules are defined here as an isolatable element that performs a defined function and has a defined interface to other elements.
  • the modules described in this disclosure may be implemented in hardware, software in combination with hardware, firmware, wetware (i.e hardware with a biological element) or a combination thereof, all of which are behaviorally equivalent.
  • modules may be implemented as a software routine written in a computer language configured to be executed by a hardware machine (such as C, C++, Fortran, Java, Basic, Matlab or the like) or a hardware machine (such as C, C++, Fortran, Java, Basic, Matlab or the like) or a hardware machine (such as C, C++, Fortran, Java, Basic, Matlab or the like) or a hardware machine (such as C, C++, Fortran, Java, Basic, Matlab or the like) or a hardware machine (such as C, C++, Fortran, Java, Basic, Matlab or the like) or a hardware machine (such as C, C++, Fortran, Java, Basic, Matlab or the like
  • LabVIEWMathScript it may be possible to implement modules using physical hardware that incorporates discrete or programmable analog, digital and/or quantum hardware.
  • programmable hardware comprise: computers, microcontrollers, microprocessors, application-specific integrated circuits (ASICs); field programmable gate arrays (FPGAs); and complex programmable logic devices (CPLDs).
  • Computers, microcontrollers and microprocessors are programmed using languages such as assembly, C, C++ or the like.
  • FPGAs, ASICs and CPLDs are often programmed using hardware description languages (HDL) such as VHSIC hardware description language (VHDL) or Verilog that configure connections between internal hardware modules with lesser functionality on a programmable device.
  • HDL hardware description languages
  • VHDL VHSIC hardware description language
  • Verilog Verilog that configure connections between internal hardware modules with lesser functionality on a programmable device.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Introduction d'un concept de groupe d'avance de temporisation dans LTE TS 36.321 pour la version 11. Un groupe d'avance de temporisation (groupe TA) comprend jusqu'à cinq cellules. L'UE ne nécessite qu'un seul temporisateur TA pour chaque groupe TA. Une procédure RACH initiée par une station de base permet d'obtenir l'alignement de temporisation initial. La configuration de multiples groupes TA dépend du compte-rendu des capacités de l'UE qui définit la capacité multi-TA de l'UE sur la base de chaque combinaison de bandes prise en charge. Une station de base reçoit des paramètres de capacité radio provenant d'un dispositif sans fil sur un premier support de signalisation sur une cellule primaire. Les paramètres de capacité radio comprennent une première séquence de paramètres de configuration radio. Un premier paramètre de configuration radio dans la première séquence comprend un premier paramètre indiquant si de multiples groupes d'avance de temporisation sont pris en charge pour une première combinaison de bandes. La première combinaison de bandes se trouve dans une seconde séquence de combinaisons de bandes. L'indice du premier paramètre de configuration radio dans la première séquence détermine l'indice de la première combinaison de bandes dans la seconde séquence.
EP13703256.1A 2012-01-25 2013-01-25 Avance de temporisation dans une station de base et dispositif sans fil pourvu de groupes d'avance de temporisation basés sur des capacités d'une ue Ceased EP2807885A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP20212147.1A EP3852466A1 (fr) 2012-01-25 2013-01-25 Configuration de group de cellules dans un terminal et danse une station de base avec "timing advance groups"

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US201261590366P 2012-01-25 2012-01-25
US201261618830P 2012-04-01 2012-04-01
US201261662191P 2012-06-20 2012-06-20
PCT/US2013/023316 WO2013112952A1 (fr) 2012-01-25 2013-01-25 Avance de temporisation dans une station de base et dispositif sans fil pourvu de groupes d'avance de temporisation basés sur des capacités d'une ue

Related Child Applications (1)

Application Number Title Priority Date Filing Date
EP20212147.1A Division EP3852466A1 (fr) 2012-01-25 2013-01-25 Configuration de group de cellules dans un terminal et danse une station de base avec "timing advance groups"

Publications (1)

Publication Number Publication Date
EP2807885A1 true EP2807885A1 (fr) 2014-12-03

Family

ID=47679076

Family Applications (2)

Application Number Title Priority Date Filing Date
EP13703256.1A Ceased EP2807885A1 (fr) 2012-01-25 2013-01-25 Avance de temporisation dans une station de base et dispositif sans fil pourvu de groupes d'avance de temporisation basés sur des capacités d'une ue
EP20212147.1A Pending EP3852466A1 (fr) 2012-01-25 2013-01-25 Configuration de group de cellules dans un terminal et danse une station de base avec "timing advance groups"

Family Applications After (1)

Application Number Title Priority Date Filing Date
EP20212147.1A Pending EP3852466A1 (fr) 2012-01-25 2013-01-25 Configuration de group de cellules dans un terminal et danse une station de base avec "timing advance groups"

Country Status (2)

Country Link
EP (2) EP2807885A1 (fr)
WO (1) WO2013112952A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108111285A (zh) * 2017-11-17 2018-06-01 中兴通讯股份有限公司 一种传输参考信号的方法及装置
CN114554478A (zh) * 2020-11-25 2022-05-27 深圳市万普拉斯科技有限公司 用户设备能力信息处理方法、装置、移动设备和存储介质

Families Citing this family (25)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102291711B (zh) 2011-08-12 2014-03-19 电信科学技术研究院 终端设备的能力上报方法和设备
KR20130126427A (ko) * 2012-05-11 2013-11-20 주식회사 팬택 다중 요소 반송파 시스템에서 단말의 성능정보의 전송장치 및 방법
US9226290B2 (en) 2012-08-16 2015-12-29 Qualcomm Incorporated Multiple timing advance groups (TAGS) for UL carrier aggregation (CA)
WO2015018044A1 (fr) * 2013-08-08 2015-02-12 Telefonaktiebolaget L M Ericsson (Publ) Procédés et dispositifs d'accès aléatoire
KR102157798B1 (ko) 2013-10-29 2020-09-18 삼성전자 주식회사 이동 통신 시스템에서 복수의 캐리어를 이용하는 데이터 송수신 방법 및 장치
WO2015130034A1 (fr) * 2014-02-27 2015-09-03 Lg Electronics Inc. Procédé et appareil permettant d'acquérir une synchronisation temporelle dans un système de communication sans fil
US9949269B2 (en) 2014-08-15 2018-04-17 Telefonaktiebolaget Lm Ericsson (Publ) Conditional network capabilities for improved system performance
EP3255830B1 (fr) 2015-04-05 2020-06-03 Ofinno, LLC Signal de référence de sondage dans un réseau sans fil
CN114944897B (zh) 2016-03-30 2024-07-16 交互数字专利控股公司 使用签名的初始接入方法
US20180124673A1 (en) * 2016-11-02 2018-05-03 Futurewei Technologies, Inc. Method of Operating Uplink Beacons to Support Inter-Frequency Mobility
CN108024325B (zh) * 2016-11-03 2020-04-03 华为技术有限公司 无线通信方法和装置
CN106658620B (zh) * 2017-03-06 2020-09-08 北京小米移动软件有限公司 一种接入点切换的方法和装置
CN109475010B (zh) * 2017-09-08 2024-06-18 华为技术有限公司 信息传输的方法和装置
CN111165032B (zh) 2017-10-02 2022-07-19 瑞典爱立信有限公司 新无线电中的定时提前范围适配
CN114258118B (zh) 2018-05-31 2023-11-03 阿里巴巴集团控股有限公司 终端与基站的通信方法和装置
KR20240052857A (ko) 2019-01-11 2024-04-23 지티이 코포레이션 무선 통신의 타이밍 어드밴스 조정 스킴들
CN116614894A (zh) * 2019-02-25 2023-08-18 华为技术有限公司 通信方法、终端设备和网络设备
MX2021013414A (es) * 2019-05-02 2021-12-10 Nokia Technologies Oy Resolucion de contencion en procedimiento de acceso aleatorio.
US11653279B2 (en) * 2019-07-24 2023-05-16 Qualcomm Incorporated UE capability exchange for handover
EP3890208A1 (fr) * 2020-03-20 2021-10-06 Nokia Technologies Oy Ajustement de synchronisation de groupe pour la transmission de liaison montante et activation de commande dans des réseaux non terrestres
US11388690B1 (en) * 2021-01-04 2022-07-12 Qualcomm Incorporated Dynamic timing advance adjustment schemes
KR102571049B1 (ko) * 2021-05-11 2023-08-28 엘지전자 주식회사 무선 통신 시스템에서 랜덤 액세스 절차 수행 방법 및 장치
US20240235781A1 (en) * 2022-03-15 2024-07-11 Samsung Electronics Co., Ltd. Ta indication and application with multiple transmission and reception points
WO2024011081A1 (fr) * 2022-07-08 2024-01-11 Cisco Technology, Inc. Optimisation de del d'infrastructure pour des dispositifs à liaisons multiples wi-fi 7
WO2024026767A1 (fr) * 2022-08-04 2024-02-08 Qualcomm Incorporated Commutation de transmission de liaison montante pour porteuses associées à de multiples groupes d'avance de temps (tag)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120008600A1 (en) * 2010-01-08 2012-01-12 Interdigital Patent Holdings, Inc. Maintaining time alignment with multiple uplink carriers

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120008600A1 (en) * 2010-01-08 2012-01-12 Interdigital Patent Holdings, Inc. Maintaining time alignment with multiple uplink carriers

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
CATT: "Consideration on Multi-TA Capability", vol. RAN WG2, no. Bratislava, Slovakia; 20121008 - 20121012, 28 September 2012 (2012-09-28), XP050666450, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_ran/WG2_RL2/TSGR2_79bis/Docs/> [retrieved on 20120928] *
CATT: "Multi-TA capability", vol. RAN WG2, no. New Orleans, USA; 20121112 - 20121116, 3 November 2012 (2012-11-03), XP050667456, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_ran/WG2_RL2/TSGR2_80/Docs/> [retrieved on 20121103] *
See also references of WO2013112952A1 *

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108111285A (zh) * 2017-11-17 2018-06-01 中兴通讯股份有限公司 一种传输参考信号的方法及装置
CN108111285B (zh) * 2017-11-17 2021-10-26 中兴通讯股份有限公司 一种传输参考信号的方法及装置
CN114554478A (zh) * 2020-11-25 2022-05-27 深圳市万普拉斯科技有限公司 用户设备能力信息处理方法、装置、移动设备和存储介质
CN114554478B (zh) * 2020-11-25 2023-12-15 深圳市万普拉斯科技有限公司 用户设备能力信息处理方法、装置、移动设备和存储介质

Also Published As

Publication number Publication date
EP3852466A1 (fr) 2021-07-21
WO2013112952A1 (fr) 2013-08-01

Similar Documents

Publication Publication Date Title
US12101828B2 (en) Multicarrier signal transmission in wireless communications
US11516812B2 (en) Resource allocation for multicarrier communications
US10588155B2 (en) Configuration of multiple timing advance groups in wireless communication devices
EP3852466A1 (fr) Configuration de group de cellules dans un terminal et danse une station de base avec &#34;timing advance groups&#34;
WO2013112646A1 (fr) Canal d&#39;accès aléatoire dans des communications sans fil à ondes porteuses multiples et pourvues de groupes d&#39;avance de temporisation

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20140819

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: OFINNO TECHNOLOGIES, LLC

RIN1 Information on inventor provided before grant (corrected)

Inventor name: DINAN HEJAZI ESMAEL

DAX Request for extension of the european patent (deleted)
17Q First examination report despatched

Effective date: 20160404

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: COMCAST CABLE COMMUNICATIONS, LLC

REG Reference to a national code

Ref country code: DE

Ref legal event code: R003

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION HAS BEEN REFUSED

18R Application refused

Effective date: 20200922