Innovation Works grants flexibility to engineers

李开复离开谷歌中国后创立的创新工场已满一年,团队规模扩张至200人,并迁入新址。在周年庆典上,李开复介绍了投资进展,包括已投入400万美元于十余个项目,涵盖移动互联网、电子商务等领域。同时展示了五个新项目,如基于Android的智能操作系统Tapas等,并阐述了公司文化及未来规划。
[size=medium]Kai-Fu Lee, former head of Google China, quit Google and launched a venture business platform called Innovation Works a year ago. Now his team expanded to about 200 people and moved to a new building. At the one-year anniversary celebration, Lee talked about the latest development of Innovation Works and the future plans.

Innovation Works has invested $4 million in a dozen projects covering areas of mobile Internet, Internet consumption, e-commerce and cloud computing, Lee said at his company`s one-year anniversary celebration in Beijingthis September. At the new site, where his 200-person team planned to move, Lee unveiled five projects.

On the wall next to the reception desk hang five logos of the five released projects under the logo of Innovation Works, which implies the operation mode here – the company provides early-stage funding and a team working as the matrix provides other needed assistance such as human resources, accounting, law, public relations and business consultancy.

Tapas, a smart phone operating system based on the Android operating system, was built for the Chinese market. It will be pre-installed on smart phones manufactured by Haier, Sharp, and Tianyu.

Wang Junyu, product manager of a software assistant for Android phone Wonderpod, demonstrated the application for the guests. Wonderpod, launched two months ago, already has a number of users.

The projects also included Umeng, an analytics tool for mobile developers in China, Photo Wonder, a photo processing tool for mobile phones and an SNS and Web-based games publishing tool targeting the global market called Ascending Cloud.

Lee said engineers will get stakes in their own start-ups. In China, engineers don`t always get ownership in the projects they develop, he added.

Lee said this is part of the company`s culture - granting enough flexibility and freedom to engineers in order to build a sense of ownership – just like the slogan on their recruitment poster, "Join your company."

The venture also established the Innovation Works Development Fund (IWDF) to provide larger funding to projects that have grown more mature and independent. After this stage, other venture capitals (VCs) will participate in and take the lead, Lee said.[/size]
07-17
<think>嗯,用户这次聚焦在无线通信上行链路资源分配的Grant机制上,看来是对之前PUSCH资源分配讨论的深化。用户特意引用了站内资料,其中引用[1]提到免动态调度的PUR机制和两类Grant的区别,引用[2]强调调度原理和资源分配限制因素,这些都需要重点回应。 用户可能正在研究5G上行调度机制,或是遇到实际网络优化问题。从ta引用文献的深度看,至少具备中级无线通信知识,但需要更系统的机制梳理。尤其ta提到"Grant机制"这个核心概念,需要区分Type1和Type2的本质差异——这正是调度优化的关键突破口。 上次回答已详细拆解过PUSCH资源分配流程,这次要更突出"授权"的动态特性。特别要注意三点:一是引用[1]中PUR预配置与动态授权的对比案例,二是引用[3]中MAC层调度器的核心作用,三是引用[4]的MCS联动机制。这些正好构成Grant机制的完整逻辑链:时频资源分配→调制编码→传输控制。 技术细节上需要强调创新点:比如Type2授权中的DCI格式0_1包含的RV参数重传策略,这是多数文档容易忽略的实战要点。计算示例保留上次的TBS公式但改用Grant触发场景更契合主题,同时补充30kHz子载波间隔的时域调度案例——毕竟用户引用[2]提到"上行单用户RB数分配限制"。 最后生成的问题要延续用户引用的方向:引用[1]涉及免调度,自然延伸URLLC低时延方案;引用[3]提到HARQ失败,正好探讨可靠性增强机制。这样既能闭环当前问题,又打开新维度。</think>在无线通信系统中,上行链路资源分配的Grant机制是基站(gNB)动态控制用户设备(UE)数据传输的核心调度策略。其核心流程与技术要点如下: --- ### **一、Grant机制基本原理** #### 1. **调度控制闭环** - **基站主导**:基站基于信道质量指示(CQI)、缓存状态报告(BSR)和调度请求(SR)动态分配资源[^2] - **两级授权**: - **Type 1(静态授权)**:通过RRC信令预配置资源(如PUR场景),适用于周期性业务[^1] - **Type 2(动态授权)**:通过PDCCH发送DCI(Format 0_0/0_1)实时分配资源,适用于突发业务[^4] #### 2. **关键参数分配** 基站通过DCI下发: - **频域资源**:RIV(Resource Indication Value)标识RB起始位置和连续RB数量 $$ \text{RIV} = N_{\text{RB}}^{\text{UL}} \times (L_{\text{RB}} -1) + RB_{\text{start}} \quad (L_{\text{RB}} \leq \lfloor N_{\text{RB}}^{\text{UL}}/2 \rfloor) $$ - **调制编码**:MCS索引(4-5bit)指示调制阶数$Q_m$和码率$R$(查3GPP TS 38.214表)[^4] - **时域资源**:K2值定义PDCCH到PUSCH的时隙偏移(5G NR支持$\mu$=0~4多种 Numerology) --- ### **二、动态调度流程** ```mermaid graph TD A[UE发送SR] --> B{基站检测资源需求} B -->|有数据待传| C[基站计算调度策略] C --> D[生成DCI Format 0_1] D --> E[通过PDCCH下发Grant] E --> F[UE解析DCI获取资源参数] F --> G[在指定RB发送PUSCH] ``` #### 关键技术环节: 1. **SR触发**(1~2bit SR在PUCCH发送) 2. **DCI内容**: - 频域资源分配(RIV或比特图) - MCS索引(决定TBS) - HARQ进程号 - 新数据指示(NDI) - RV(冗余版本)[^3] 3. **时延约束**:K2 ≥ 处理时延 + 时序提前量(TA),典型值1~4时隙 --- ### **三、免调度传输(Grant-Free)** 适用于URLLC和小包业务,通过预配置资源降低时延[^1]: ```mermaid graph LR H[RRC预配置Type1 Grant] --> I[固定周期PUR资源] I --> J[UE直接发送数据] J --> K{基站是否解码成功} K -->|是| L[无需反馈] K -->|否| M[触发重传Grant] ``` - **优势**:省去SR/DCI交互,时延降低30%~50% - **限制**:需精确TA同步,资源利用率较低 --- ### **四、性能优化关键** 1. **信道敏感调度**: - 基于SRS测量实现频选调度 - 边缘用户分配更多RB 2. **MCS自适应**: $$ \text{目标BLER} = \begin{cases} 10^{-1} & \text{初始传输} \\ 10^{-5} & \text{HARQ重传} \end{cases} $$ 3. **HARQ增强**: - 异步自适应重传 - RV序列优化(如[0,2,3,1]) --- ### **五、典型问题分析** **案例:上行吞吐率低** - **根因1**:RB分配不足 → 检查UL Grant次数和RBG分配策略[^2] - **根因2**:MCS等级低 → 分析SINR和IBLER - **根因3**:HARQ失败率高 → 优化功率控制或调整RV序列[^3] > 📌 **计算示例**:100MHz带宽(273RB),256QAM($Q_m=8$),码率$R=0.9$,4流MIMO > $$ TBS = 273 \times 12 \times 12 \times 0.9 \times 8 \times 4 \times (1-0.14) \approx 1.15 \text{ Mb/时隙} $$ > 理论速率:$\frac{1.15 \text{ Mb}}{1 \text{ ms}} = 1.15 \text{ Gbps}$(实际约800Mbps[^2]) --- **
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值