WO2015081844A1 - 一种下行控制信道处理方法、装置和系统 - Google Patents

一种下行控制信道处理方法、装置和系统 Download PDF

Info

Publication number
WO2015081844A1
WO2015081844A1 PCT/CN2014/092770 CN2014092770W WO2015081844A1 WO 2015081844 A1 WO2015081844 A1 WO 2015081844A1 CN 2014092770 W CN2014092770 W CN 2014092770W WO 2015081844 A1 WO2015081844 A1 WO 2015081844A1
Authority
WO
WIPO (PCT)
Prior art keywords
rnti
scheduled
service
group call
sps
Prior art date
Application number
PCT/CN2014/092770
Other languages
English (en)
French (fr)
Inventor
谭源春
张文忠
黄其华
许瑞锋
Original Assignee
北京信威通信技术股份有限公司
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 北京信威通信技术股份有限公司 filed Critical 北京信威通信技术股份有限公司
Priority to US15/309,455 priority Critical patent/US20170188341A1/en
Publication of WO2015081844A1 publication Critical patent/WO2015081844A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
    • H04W48/12—Access restriction or access information delivery, e.g. discovery data delivery using downlink control channel
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0446—Resources in time domain, e.g. slots or frames
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states

Definitions

  • the present application relates to the field of wireless communications, and in particular, to a downlink control channel processing method, apparatus, and system.
  • GP-RNTI Group Paging Radio Network Temporary Identifier
  • G-RNTI Group Radio Network Temporary Identifier supporting cluster services.
  • the GP-RNTI is used for paging of group users
  • the G-RNTI is used for group signaling and physical layer scrambling of services.
  • the space occupied by the RNTI scrambled control command on the control channel resource CCE is divided into a common space and a dedicated space.
  • the public space is shared by multiple common commands, and the dedicated space can be shared by multiple users or exclusively by one user.
  • the public space begins with a fixed CCE space index of 0, and the terminal's search for the private space begins with the starting position determined by the C-RNTI.
  • the GP-RNTI scrambled paging command and the like are generally placed in the public space, and the G-RNTI scrambled downlink group service command can be placed in the public space or in the dedicated space. If the G-RNTI scrambled command is placed in the public space, the G-RNTI will inevitably occupy a limited public space due to the tight public resources, which will reduce the system throughput; if the G-RNTI is placed in a relatively sufficient resource In the dedicated space, the complexity of the UE search space will be increased, so that the UE battery capacity is also required.
  • the applicant proposes a method for allocating the G-RNTI of the trunking service in the dedicated space, and using the G-RNTI to perform the clustering service scheduling; for the UE in the RRC_Connected state of the clustering service group, If there is a cluster service and a UE individual service, the cluster service and the UE individual service are first combined, and the combined service is scheduled by using the C-RNTI of the UE; and the receiving end: in the downlink TTI, the ⁇ G-RNTI is adopted.
  • the ⁇ or ⁇ C-RNTI, G-RNTI ⁇ set performs a dedicated space blind check; the blind check is terminated once any RNTI is blindly detected.
  • the applicant also proposes a method for performing the cluster service scheduling by using the G-RNTI when there is a G-RNTI cluster service in a downlink TTI; for each UE in the cluster service group, if the downlink TTI exists The UE individual service does not schedule the individual service in the TTI, but schedules the individual service in the next downlink TTI.
  • the UE performs PDCCH dedicated space blind detection using the ⁇ G-RNTI ⁇ or ⁇ C-RNTI, G-RNTI ⁇ set.
  • the present application provides a method for downlink control channel allocation.
  • the method includes: when a group call service is to be scheduled in a downlink TTI, if there is a UE in the downlink call in the current cell, there is an individual service to be scheduled in the downlink TTI.
  • the transmitting end schedules the group call service by using a G-RNTI or an SPS G-RNTI in a public space, and performs scheduling on a dedicated space by using the C-RNTI or the SPS C-RNTI for the individual service of the UE; All the UEs in the group call have no individual service to be scheduled in the downlink TTI, and the sender uses the G-RNTI or the SPS G-RNTI to schedule the group call service in the dedicated space.
  • the scheduling is dynamic scheduling or semi-static scheduling.
  • the group call service is one or more.
  • the number of UEs that have individual services to be scheduled in the downlink TTI is one or more.
  • the individual The business is a point-to-point business.
  • the UE with individual service to be scheduled in the downlink TTI is in an RRC_Connected state.
  • the method further includes: determining whether the UE has an individual service to be scheduled in the downlink TTI, and determining whether the UE is in the group call.
  • There are individual services to be scheduled in the downlink TTI including:
  • the present application further provides a downlink control channel processing apparatus, including a first scheduling module and a second scheduling module.
  • the first scheduling module is configured to use the group scheduling service.
  • the scheduling includes: when the UE in the group call has an individual service to be scheduled in the downlink TTI, scheduling the group call service by using a G-RNTI or an SPS G-RNTI in a public space; When all the UEs in the group call have no individual service to be scheduled in the downlink TTI, the group call service is scheduled in a dedicated space by using a G-RNTI or an SPS G-RNTI; the second scheduling module is used to When there is an individual service to be scheduled in the downlink TTI, the UE performs scheduling in a dedicated space by using the C-RNTI or the SPS C-RNTI for the individual service of the UE.
  • the device further includes a service monitoring module, configured to monitor whether each UE in the cell in the cell has an individual service to be scheduled in the downlink TTI, and notify the first scheduling module and the second scheduling module.
  • the monitoring includes: learning, by the network side, whether the UE with the individual service to be scheduled belongs to the group call; or learning the UE participating in the group call from the network side, monitoring the UE with the individual service to be scheduled in the current cell, and determining the UE Whether it belongs to the group call.
  • the scheduling is dynamic scheduling or semi-static scheduling.
  • the group call service is one or more.
  • the number of UEs that have individual services to be scheduled in the downlink TTI is one or more.
  • the individual business is a point-to-point service.
  • the present application further provides a downlink control channel processing method.
  • the UE performs PDCCH blind detection in the public space by using G-RNTI or SPS G-RNTI, if the G-RNTI or SPS G is not blindly detected in the public space.
  • - RNTI then continue PDCCH blind detection in the dedicated space, and then exit the blind check.
  • the UE blindly detects the G-RNTI or the SPS G-RNTI in the public space, and the UE is in the RRC_Idle state, the blind check is exited.
  • the UE blindly detects the G-RNTI or the SPS G-RNTI in the public space, and the UE is in the RRC_Connected state, continue to perform PDCCH blind detection in the dedicated space by using the C-RNTI or the SPS C-RNTI, and then exit.
  • the blind test if the UE blindly detects the G-RNTI or the SPS G-RNTI in the public space, and the UE is in the RRC_Connected state, continue to perform PDCCH blind detection in the dedicated space by using the C-RNTI or the SPS C-RNTI, and then exit. The blind test.
  • the present application further provides a terminal for downlink control channel processing, where the terminal includes a first module, and the first module is configured to perform PDCCH blindness in a public space by using G-RNTI or SPS G-RNTI in one downlink TTI. If the G-RNTI or SPS G-RNTI is not blindly detected in the public space, the PDCCH blind check is continued in the dedicated space, and then the blind check is exited. Further, the first module is further configured to: if the G-RNTI or the SPS G-RNTI is blindly detected in the public space, and the terminal is in an RRC_Idle state, the first module exits the blind detection.
  • the terminal further includes a second module, if the G-RNTI or SPS G-RNTI is blindly detected in the public space, and the terminal is in an RRC_Connected state, the second module is used to adopt C-RNTI or SPS C
  • the RNTI performs a PDCCH blind check in the dedicated space and then exits the blind check.
  • the terminal further includes a third module, configured to record that the terminal is in an RRC_Connected state or an RRC_Idle state.
  • the present application also proposes a downlink control channel processing system, which includes any of the devices and terminals as described above.
  • the downlink control channel processing method, device and system proposed by the present application can not only support concurrent scheduling of multiple groups of cluster services, but also enhance the cluster service system gain, and increase the number of UE blind detections and reduce the UE search complexity.
  • FIG. 1 is a flowchart of processing of a method according to the present application at a transmitting end
  • FIG. 5 is a flowchart of processing on the UE1 side in the first embodiment
  • FIG. 8 is a schematic structural diagram of a downlink control channel processing apparatus according to an embodiment of the present disclosure.
  • FIG. 9 is a schematic structural diagram of a terminal used for downlink control channel processing according to an embodiment of the present disclosure.
  • FIG. 10 is a schematic structural diagram of another downlink control channel processing apparatus according to an embodiment of the present disclosure.
  • FIG. 11 is a schematic structural diagram of another terminal used for downlink control channel processing according to an embodiment of the present disclosure.
  • LTE Long Term Evolution system, Long Term Evolution System
  • RNTI Radio Network Temporary Identifier, wireless network temporary identifier
  • GP-RNTI Group Paging RNTI, group paging wireless network temporary identifier
  • G-RNTI Group RNTI, group wireless network temporary identifier
  • CCE Control Channel Elements, control channel resources
  • C-RNTI Cell-RNTI, temporary identifier of the cell wireless network
  • UE User Equipment, user equipment
  • TTI Transmit Time Interval, the transmission interval
  • PDCCH Physical Downlink Control Channel, physical downlink control channel
  • SPS Semi-Persistent Scheduling, semi-static scheduling
  • RRC Radio Resource Control, radio resource control
  • FIG. 1 is a flowchart of processing of a downlink control channel processing method at a transmitting end according to the present application. Its specific operation is as follows:
  • step 101 When there is a group call service to be scheduled in a downlink TTI, step 101 is performed.
  • Step 101 The sender determines whether there is a UE in the group of the current cell that has an individual service to be scheduled in the downlink TTI. If yes, step 102 is performed; if all the UEs in the group of the current cell have no individual service to be scheduled in the downlink TTI, step 104 is performed.
  • Step 102 The group call service is scheduled in a public space by using a G-RNTI or an SPS G-RNTI, and then step 103 is performed.
  • Step 103 Perform scheduling in a dedicated space by using C-RNTI or SPS C-RNTI for individual services.
  • Step 104 Perform scheduling on the group call service by using a G-RNTI or an SPS G-RNTI in a dedicated space.
  • the scheduling may be dynamic scheduling or semi-static scheduling; the foregoing individual service may be a point-to-point service.
  • step 101 can be implemented by the following method. Obtaining, by the network side, whether the UE with the individual service to be scheduled belongs to the group call; or, knowing from the network side, participating in the group call The UE monitors a UE in the cell that has an individual service to be scheduled and determines whether it belongs to the group call.
  • FIG. 2 is a processing flow of a receiving end of a downlink control channel processing method according to the present application, and the specific operations include the following steps.
  • Step 201 In a downlink TTI, the UE first performs PDCCH blind detection in the public space by using the G-RNTI or the SPS G-RNTI, and then performs step 202.
  • Step 202 Determine whether the G-RNTI or the SPS G-RNTI is blindly detected in the public space. If the UE does not blindly detect the G-RNTI or the SPS G-RNTI in the public space, step 205 is performed; if the UE blindly detects the G-RNTI or the SPS G-RNTI in the public space, step 203 is performed.
  • Step 203 Determine whether the UE status is in the RRC_Connected state. If yes, go to step 204; if no, go to step 206.
  • Step 204 The UE continues to perform PDCCH blind detection in the dedicated space by using the C-RNTI or the SPS C-RNTI, and then performs step 206.
  • Step 205 The UE performs PDCCH blind detection in the dedicated space by using the G-RNTI or the SPS G-RNTI, and then performs step 206.
  • Step 206 ending the blind check.
  • the system can support multiple groups of cluster services well, and the number of blind detections of the downlink control channel by the UE does not increase.
  • Embodiment 1 is a diagrammatic representation of Embodiment 1:
  • the cell has one cluster service, and its G-RNTI is 15, and the corresponding UEs are UE0 to UE2 respectively.
  • UE0 is in RRC_Connected state
  • UE1 and UE2 are in RRC_Idle. status. If the C-RNTI of UE0 is 5, there is a G-RNTI cluster group call service and a UE0 data download service in a certain downlink TTI.
  • a downlink TTI of the cell has a group call service
  • the UE0 has a data download service to be scheduled in the downlink TTI
  • the base station side that is, the network side
  • the processing flow includes the following steps.
  • Step 301 For the group call service, use G-RNTI, that is, 15, to perform scheduling in the public space, and then perform step 302.
  • Step 302 For the data download service of UE0, use C-RNTI, that is, 5, to perform scheduling in a dedicated space.
  • the processing flow of the receiving end such as the UE0 side
  • the processing flow on the UE0 side includes the following steps.
  • step 401 UE0 adopts G-RNTI, that is, 15, to perform PDCCH blind detection in the public space. If the G-RNTI is blindly detected, then step 402 is performed.
  • step 402 the UE0 continues to adopt the C-RNTI, that is, 5, and performs PDCCH blind detection in the dedicated space. If the C-RNTI is blindly detected, step 403 is performed.
  • step 403 UE0 ends the blind check.
  • the processing flow of the receiving side such as the UE1 side, please refer to FIG. 5.
  • the UE1 in the downlink TTI, the UE1 is in the RRC_Idle state, and the processing procedure of the UE1 includes the following steps.
  • step 501 the UE1 performs a PDCCH blind check in the public space by using a G-RNTI, that is, 15. If the G-RNTI is blindly detected, step 502 is performed.
  • Step 502 UE1 ends the PDCCH blind check.
  • the processing flow on the UE2 side is the same as the processing flow on the UE1 side, and will not be described again.
  • Embodiment 2 is a diagrammatic representation of Embodiment 1:
  • the G-RNTI is 21, and the corresponding UEs are UE0 to UE1, respectively, where UE0 is in the RRC_Idle state, UE1 is in the RRC_Connected state, and the C-RNTI of UE1 is assumed to be 17, and only one G-RNTI set is in one downlink TTI. Group call business.
  • the processing flow at the transmitting end can be referred to FIG.
  • the transmitting end such as the base station side
  • the processing flow includes the following steps.
  • step 601 the G-RNTI, that is, 21, is used for the group call service, and scheduling is performed in a dedicated space.
  • UE0 in one downlink TTI, UE0 is in the RRC_Idle state, and the processing flow on the UE0 side is as follows.
  • step 701 UE0 first performs a blind check on the public space by using G-RNTI, that is, 21. If the G-RNTI is not blindly detected, step 702 is performed.
  • step 702 the UE0 continues to adopt the G-RNTI, that is, 21, and performs PDCCH blind detection in the dedicated space. If the G-RNTI is blindly detected, step 703 is performed.
  • step 703 UE0 ends the blind check on the PDCCH.
  • UE1 in one downlink TTI, UE1 is in the RRC_Connected state, and the processing flow on the UE1 side is as follows (not shown in the figure).
  • the UE1 performs PDCCH blind detection on the common space, and does not blindly detect the G-RNTI in the public space. Then, the G-RNTI is used to perform PDCCH blind detection in the dedicated space, and the G-RNTI is blindly detected, and the blind detection of the PDCCH is exited.
  • Embodiment 3 is a diagrammatic representation of Embodiment 3
  • the third embodiment of the present application discloses a downlink control channel processing apparatus 800, where the apparatus includes a first scheduling module 801 and a second scheduling module 802.
  • the first schedule The module 801 is configured to schedule the group call service, where the method includes: when the UE in the group call has an individual service to be scheduled in the downlink TTI, adopting G-RNTI or SPS G for the group call service.
  • the second scheduling module 802 is configured to: when the UE has the individual service to be scheduled in the downlink TTI, use the C-RNTI or the SPS C-RNTI in the dedicated space for the individual service of the UE. Schedule.
  • the device further includes a service monitoring module 803, configured to monitor, in the group call, whether each UE in the cell has an individual service to be scheduled in the downlink TTI, and notify the first scheduling module 801 and the second scheduling Module 802.
  • the monitoring includes: determining, by the network side, whether the UE with the individual service to be scheduled belongs to the group call; or obtaining the UE participating in the group call from the network side, monitoring the UE with the individual service to be scheduled in the current cell, and determining Whether it belongs to the group call.
  • the scheduling is dynamic scheduling or semi-static scheduling; the group call service is one or more; and there are one or more UEs in the downlink TTI that have individual services to be scheduled.
  • the individual business is a point-to-point service.
  • Embodiment 4 is a diagrammatic representation of Embodiment 4:
  • a fourth embodiment of the present application further includes a terminal 900, where the first module 901 is configured to use a G-RNTI or an SPS G-RNTI in a downlink TTI.
  • the PDCCH is blindly detected in the space. If the G-RNTI or the SPS G-RNTI is not blindly detected in the public space, the PDCCH blind check is continued in the dedicated space, and then the blind check is exited.
  • the first module 901 is further configured to: if the G-RNTI or the SPS G-RNTI is blindly detected in the public space, and the terminal is in the RRC_Idle state, the first module 901 exits the blind detection.
  • the terminal further includes a second module 902, if the G-RNTI or the SPS G-RNTI is blindly detected in the public space, and the terminal is in the RRC_Connected state, the second module 902 is configured to adopt the C-RNTI. Or the SPS C-RNTI performs a PDCCH blind check in the dedicated space, and then exits the blind check.
  • the terminal further includes a third module 903, configured to record that the terminal is in an RRC_Connected state or an RRC_Idle state.
  • the present application also discloses a downlink control channel processing apparatus, which includes a central processing unit (CPU) 101, a memory 102, and a nonvolatile memory 103.
  • CPU central processing unit
  • memory 102 volatile memory
  • nonvolatile memory 103 nonvolatile memory
  • the nonvolatile memory 103 stores a computer program for implementing downlink control channel processing.
  • the CPU 101 can load the computer program from the non-volatile memory 103 into the memory 102 to form computer executable instructions.
  • the computer executable instructions include a first scheduling instruction 1021 and a second scheduling instruction 1022.
  • the first scheduling instruction 1021 is configured to indicate that the group call service is scheduled, and the method includes: when the UE in the group call has an individual service to be scheduled in the downlink TTI, indicating that the group call service is used by the G- The RNTI or the SPS G-RNTI is scheduled in the public space; when all the UEs in the group call have no individual service to be scheduled in the downlink TTI, the G-RNTI or the SPS G-RNTI is used for the group call service. Scheduling in a dedicated space; the second scheduling instruction 1022 is configured to indicate, when the UE has an individual service to be scheduled in the downlink TTI, to use C-RNTI or SPS for the individual service of the UE. The C-RNTI is scheduled in a dedicated space.
  • the computer executable instructions further include a service monitoring instruction 1023, configured to indicate whether each UE in the cell in the group call has an individual service to be scheduled in the downlink TTI.
  • the monitoring includes: obtaining, from the network side, whether the UE with the individual service to be scheduled is The UEs that are involved in the group call are learned from the network side, and the UEs in the cell that have individual services to be scheduled are monitored and determined whether they belong to the group call.
  • the scheduling is dynamic scheduling or semi-static scheduling; the group call service is one or more; and there are one or more UEs in the downlink TTI that have individual services to be scheduled.
  • the individual business is a point-to-point service.
  • the present application also discloses a terminal, which includes a central processing unit (CPU) 111, a memory 112, and a nonvolatile memory 113.
  • CPU central processing unit
  • memory 112 a nonvolatile memory 113.
  • the nonvolatile memory 113 stores a computer program for implementing downlink control channel processing.
  • the CPU 111 can load the computer program from the non-volatile memory 113 into the memory 112 to form computer executable instructions.
  • the computer executable instructions comprise a first instruction 1121.
  • the first instruction 1121 is configured to indicate, in a downlink TTI, that the PDCCH is blindly detected in the public space by using the G-RNTI or the SPS G-RNTI, and if the G-RNTI or the SPS G-RNTI is not blindly detected in the public space, The indication continues to perform a PDCCH blind check in the dedicated space and then exits the blind check.
  • the first instruction 1121 is further used to indicate that the blind check is exited.
  • the computer executable instructions further include a second instruction 1122, if the G-RNTI or SPS G-RNTI is blindly detected in the common space, and the terminal is in an RRC_Connected state, the second instruction 1122 is used to indicate The PDCCH blind check is performed in a dedicated space using C-RNTI or SPS C-RNTI, and then the blind check is exited.
  • the computer executable instructions further include a third instruction 1123, configured to indicate that the recording terminal is in an RRC_Connected state or an RRC_Idle state.
  • the present application also discloses a downlink control channel processing system, which is composed of a downlink control channel processing apparatus as described above and a terminal as described above.
  • the downlink control channel processing method, apparatus, and system provided by the present application can not only support concurrent scheduling of multiple sets of cluster services, but also enhance the cluster service system gain, without increasing the number of blind detections of the UE, and reducing The UE search complexity.

Landscapes

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

Abstract

本申请提出一种下行控制信道处理方法，包括：如果当前小区的所述组呼中有UE在该下行TTI中有个体业务待调度，则发送端对所述组呼业务采用G-RNTI在公共空间进行调度，对个体业务采用C-RNTI在专用空间进行调度；如果当前小区的组呼中的所有UE在该下行TTI中均没有个体业务待调度，则对组呼业务采用G-RNTI在专用空间进行调度。

Description

一种下行控制信道处理方法、装置和系统
本申请要求于2013年12月3日提交中国专利局、申请号为201310642353.7、发明名称为“一种下行控制信道处理方法、装置和系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及无线通信领域，尤其涉及一种下行控制信道处理方法、装置和系统。
发明背景
在LTE集群系统中，除了原LTE标准中支持的RNTI外，额外增加了支持集群业务的GP-RNTI(群组寻呼无线网络临时标识符)和G-RNTI(群组无线网络临时标识符)，其中，GP-RNTI用于群组用户的寻呼，G-RNTI用于群组信令和业务的物理层加扰等。
RNTI加扰的控制命令在控制信道资源CCE上所占的空间分为公共空间和专用空间，公共空间由多个公共命令共享，专用空间可以多个用户共享，也可以一个用户专享。公共空间从固定的CCE空间索引0开始，而终端对专用空间的搜索从C-RNTI所确定的起始位置开始。
上述GP-RNTI加扰的寻呼命令等一般放在公共空间，而G-RNTI加扰的下行群组业务命令既可以放在公共空间，也可以放在专用空间。而如果G-RNTI加扰的命令放在公共空间，因公共资源比较紧张，G-RNTI势必会抢占有限的公共空间，这样就会降低系统的吞吐量；如果G-RNTI放在资源相对充足的专用空间上，则将加大UE搜索空间的复杂度，因此对UE电池容量也提出了较高的要求。
针对上述问题，申请人提出了一种方法：为集群业务的G-RNTI在专用空间进行分配，并采用所述G-RNTI进行集群业务调度；对集群业务组中处于RRC_Connected状态的UE，若同时有集群业务和UE个体业务，则先将所述集群业务和UE个体业务合并，再使用所述UE的C-RNTI对合并后的业务进行调度；接收端：在下行TTI，采用{G-RNTI}或{C-RNTI,G-RNTI}集合进行专用空间盲检；一旦盲检到任何一个RNTI则结束所述盲检。
申请人还提出了一种方法：在一个下行TTI中有G-RNTI的集群业务时，通过所述G-RNTI进行所述集群业务调度；对集群业务组中各UE，若该下行TTI中存在UE个体业务，则在该TTI不调度该个体业务，而在下一个下行TTI中调度该个体业务。在下行TTI，UE采用{G-RNTI}或{C-RNTI,G-RNTI}集合进行PDCCH专用空间盲检。
通过采用上述两种方法，尽管可以大幅降低终端盲检次数，但是仍然需要增加至多4次PDCCH盲检次数。
发明内容
本申请提出一种下行控制信道分配的方法，该方法包括：在一个下行TTI中有组呼业务待调度时，如果当前小区的所述组呼中有UE在该下行TTI中有个体业务待调度，则发送端对所述组呼业务采用G-RNTI或SPS G-RNTI在公共空间进行调度，对所述UE的个体业务采用C-RNTI或SPS C-RNTI在专用空间进行调度；如果当前小区的所述组呼中的所有UE在该下行TTI中均没有个体业务待调度，则发送端对所述组呼业务采用G-RNTI或SPS G-RNTI在专用空间进行调度。
所述调度为动态调度或半静态调度。所述组呼业务为一个或多个。所述在该下行TTI中有个体业务待调度的UE为1个或多个。所述个体 业务为点到点业务。所述在该下行TTI中有个体业务待调度的UE处于RRC_Connected状态。
在发送端调度所述组呼业务之前，所述方法进一步包括：判断所述组呼中是否有UE在该下行TTI中有个体业务待调度，所述判断所述组呼中是否有UE在该下行TTI中有个体业务待调度包括：
从网络侧获知有个体业务待调度的UE是否属于所述组呼；或从网络侧获知参与所述组呼的UE，监控本小区中有个体业务待调度的UE并判断其是否属于所述组呼。
本申请还提出一种下行控制信道处理装置，包括第一调度模块和第二调度模块，在一个下行TTI中有组呼业务待调度时，所述第一调度模块用于对所述组呼业务进行调度，具体包括：当所述组呼中有UE在该下行TTI中有个体业务待调度时，对所述组呼业务采用G-RNTI或SPS G-RNTI在公共空间进行调度；当所述组呼中的所有UE在该下行TTI中均没有个体业务待调度时，对所述组呼业务采用G-RNTI或SPS G-RNTI在专用空间进行调度；所述第二调度模块，用于当所述组呼中有UE在该下行TTI中有个体业务待调度时，对所述UE的个体业务采用C-RNTI或SPS C-RNTI在专用空间进行调度。
进一步的，该装置还包括业务监控模块，用于监控所述组呼中在该小区的各UE在该下行TTI是否有个体业务待调度，并通知所述第一调度模块和第二调度模块。所述监控包括：从网络侧获知有个体业务待调度的UE是否属于所述组呼；或从网络侧获知参与所述组呼的UE，监控本小区中有个体业务待调度的UE并判断其是否属于所述组呼。
所述调度为动态调度或半静态调度。所述组呼业务为一个或多个。所述在该下行TTI中有个体业务待调度的UE为1个或多个。所述个体业务为点到点业务。
本申请还提出一种下行控制信道处理方法，在一个下行TTI中，UE采用G-RNTI或SPS G-RNTI在公共空间进行PDCCH盲检，如果在公共空间未盲检到G-RNTI或SPS G-RNTI，则继续在专用空间进行PDCCH盲检，然后退出所述盲检。
进一步的，如果UE在公共空间盲检到G-RNTI或SPS G-RNTI，且所述UE处于RRC_Idle状态，则退出所述盲检。
更进一步的，如果UE在公共空间盲检到G-RNTI或SPS G-RNTI，且所述UE处于RRC_Connected状态，则继续采用C-RNTI或SPS C-RNTI在专用空间进行PDCCH盲检，然后退出所述盲检。
本申请还提出一种用于下行控制信道处理的终端，该终端包括第一模块，所述第一模块用于在一个下行TTI中，采用G-RNTI或SPS G-RNTI在公共空间进行PDCCH盲检，如果在公共空间未盲检到G-RNTI或SPS G-RNTI，则继续在专用空间进行PDCCH盲检，然后退出所述盲检。进一步的，所述第一模块还用于，如果在公共空间盲检到G-RNTI或SPS G-RNTI，且所述终端为RRC_Idle状态，则所述第一模块退出所述盲检。进一步的，该终端还包括第二模块，如果在公共空间盲检到G-RNTI或SPS G-RNTI，且所述终端为RRC_Connected状态，则所述第二模块用于采用C-RNTI或SPS C-RNTI在专用空间进行PDCCH盲检，然后退出所述盲检。更进一步的，该终端还包括第三模块，用于记录所述终端为RRC_Connected状态或RRC_Idle状态。
本申请还提出一种下行控制信道处理系统，该系统包括如前所述的任意一项装置和终端。
本申请提出的下行控制信道处理方法、装置和系统不仅能够支持多组集群业务的并发调度，增强了集群业务系统增益，同时无需增加UE盲检次数，降低了UE搜索复杂度。
附图简要说明
图1为本申请提出的方法在发送端的处理流程图；
图2为本申请提出的方法在接收端的处理流程图；
图3为实施例一中网络侧的处理流程图；
图4为实施例一中UE0侧的处理流程图；
图5为实施例一中UE1侧的处理流程图；
图6为实施例二中网络侧的处理流程图；
图7为实施例二中终端侧的处理流程图；
图8为本申请实施例提供的一种下行控制信道处理装置的结构示意图；
图9为本申请实施例提供的一种用于下行控制信道处理的终端的结构示意图；
图10为本申请实施例提供的另外一种下行控制信道处理装置的结构示意图；
图11为本申请实施例提供的另外一种用于下行控制信道处理的终端的结构示意图。
实施本发明的方式
为了引用和清楚起见，下文中使用的技术名词的说明总结如下：
LTE：Long Term Evolution system，长期演进系统；
RNTI：Radio Network Temporary Identifier，无线网络临时标识；
GP-RNTI：Group Paging RNTI，群组寻呼无线网络临时标识；
G-RNTI：Group RNTI，群组无线网络临时标识；
CCE：Control Channel Elements，控制信道资源；
C-RNTI：Cell-RNTI,小区无线网络临时标识；
UE：User Equipment，用户设备；
TTI：Transmit Time Interval，发送时间间隔；
PDCCH：Physical Downlink Control Channel，物理下行控制信道；
SPS:Semi-Persistent Scheduling,半静态调度；
RRC:Radio Resource Control,无线资源控制；
本申请提出的下行控制信道处理方法的具体流程、装置和系统的具体结构将通过以下实施例进行具体描述。
请参阅附图1，图1为本申请提出的一种下行控制信道处理方法在发送端的处理流程图。其具体操作如下：
在一个下行TTI中有组呼业务待调度时，执行步骤101。
步骤101，发送端判断，当前小区的该组呼中是否有UE在该下行TTI中同时有个体业务待调度。如果有，执行步骤102；如果当前小区的该组呼中的所有UE在该下行TTI中均没有个体业务待调度，执行步骤104。
步骤102，对该组呼业务采用G-RNTI或SPS G-RNTI在公共空间进行调度，然后执行步骤103。
步骤103，对个体业务采用C-RNTI或SPS C-RNTI在专用空间进行调度。
步骤104，对所述组呼业务采用G-RNTI或SPS G-RNTI在专用空间进行调度。
其中，调度可以是动态调度，也可以是半静态调度；上述的个体业务可以是点到点的业务。一个下行TTI中待调度的组呼业务可能有一个，也可能有多个，对每一个组呼业务均可以采用上述方法进行调度。
其中，步骤101可以通过以下方法实现。从网络侧获知有个体业务待调度的UE是否属于所述组呼；或者，从网络侧获知参与所述组呼的 UE，监控本小区中有个体业务待调度的UE并判断其是否属于所述组呼。
请参阅附图2，图2为本申请提出的一种下行控制信道处理方法的接收端的处理流程，其具体操作包括以下步骤。
步骤201，在一个下行TTI中，UE首先采用G-RNTI或SPS G-RNTI在公共空间进行PDCCH盲检，然后执行步骤202。
步骤202，判断是否在公共空间盲检到G-RNTI或SPS G-RNTI。如果UE在公共空间未盲检到G-RNTI或SPS G-RNTI，则执行步骤205；如果UE在公共空间盲检到G-RNTI或SPS G-RNTI，则执行步骤203。
步骤203，判断UE状态是否为RRC_Connected状态，若是，执行步骤204；若否，执行步骤206。
步骤204，UE继续采用C-RNTI或SPS C-RNTI在专用空间进行PDCCH盲检，然后执行步骤206。
步骤205，UE采用G-RNTI或SPS G-RNTI在专用空间进行PDCCH盲检，然后执行步骤206。
步骤206，结束所述盲检。
采用上述方法，系统可以很好的支持多组集群业务，而UE对下行控制信道的盲检次数不会增加。
下面结合实施例一和实施例二对上述方法的部分应用进行具体描述：
实施例一：
假设基站的小区存在3个UE，分别为UE0～UE2，该小区存在一个集群业务，其G-RNTI为15，对应的UE分别为UE0～UE2；其中，UE0处于RRC_Connected状态，UE1和UE2处于RRC_Idle状态。假如UE0的C-RNTI为5，在某个下行TTI同时有G-RNTI集群组呼业务和UE0的数据下载业务。
关于发射端，比如基站侧的处理流程，请参阅附图3。根据上面的描述可知，该小区的一个下行TTI有组呼业务，且UE0在该下行TTI有数据下载业务待调度，所述基站侧，即网络侧，处理流程包括下列步骤。
步骤301，对于组呼业务，采用G-RNTI，即15，在公共空间进行调度，然后执行步骤302。
步骤302，对于UE0的数据下载业务，采用C-RNTI，即5，在专用空间进行调度。
关于接收端，比如UE0侧的处理流程，请参照附图4。根据上面的描述可知，在该下行TTI中，UE0处于RRC_Connected状态，所以UE0侧的处理流程包括以下步骤。
步骤401，UE0采用G-RNTI,即15，在公共空间进行PDCCH盲检。若盲检到G-RNTI,然后执行步骤402。
步骤402，UE0继续采用C-RNTI，即5，在专用空间进行PDCCH盲检。若盲检到C-RNTI，执行步骤403。
步骤403，UE0结束所述盲检。
关于接收侧，比如UE1侧的处理流程，请参照附图5。根据上面的描述可知，在该下行TTI中，UE1处于RRC_Idle状态，UE1的处理流程包括以下步骤。
步骤501，UE1采用G-RNTI,即15，在公共空间进行PDCCH盲检。若盲检到G-RNTI,执行步骤502。
步骤502，UE1结束所述PDCCH盲检。
UE2侧的处理流程与UE1侧的处理流程相同，不再赘述。
实施例二：
假设一个基站的小区存在两个UE，分别为UE0～UE1；该小区存在 一个集群业务，其G-RNTI为21，对应的UE分别为UE0～UE1，其中，UE0处于RRC_Idle态，UE1处于RRC_Connected状态，假设UE1的C-RNTI为17，在一个下行TTI只有G-RNTI集群组呼业务。
发射端，比如基站侧的处理流程，可参照附图6。根据上面的描述可知，该小区的上述下行TTI中仅有组呼业务，且该组呼中所有的UE(UE0和UE1)在该TTI都没有个体业务待调度，则发射端，即，网络侧，处理流程包括下列步骤。
步骤601，对该组呼业务采用G-RNTI，即21，在专用空间进行调度。
接收端的处理流程，请参照附图7。
根据上面的描述可知，在一个下行TTI中，UE0处于RRC_Idle状态，UE0侧的处理流程如下。
步骤701，UE0首先采用G-RNTI，即21，对公共空间进行盲检。若未盲检到G-RNTI，则执行步骤702。
步骤702，UE0继续采用G-RNTI，即21，在专用空间进行PDCCH盲检。若盲检到G-RNTI，则执行步骤703。
步骤703，UE0结束对PDCCH的盲检。
根据上面的描述可知，在一个下行TTI中，UE1处于RRC_Connected状态，UE1侧的处理流程如下(图中未示出)。
UE1对公共空间进行PDCCH盲检，在公共空间未盲检到G-RNTI，则继续采用G-RNTI在专用空间进行PDCCH盲检，盲检到G-RNTI，并退出对PDCCH的盲检。
实施例三：
如图8所示，本申请实施例三公开了一种下行控制信道处理装置800，该装置包括第一调度模块801和第二调度模块802。所述第一调度 模块801，用于对所述组呼业务进行调度，具体包括：当所述组呼中有UE在该下行TTI中有个体业务待调度时，对所述组呼业务采用G-RNTI或SPS G-RNTI在公共空间进行调度；当所述组呼中的所有UE在该下行TTI中均没有个体业务待调度时，对所述组呼业务采用G-RNTI或SPS G-RNTI在专用空间进行调度；所述第二调度模块802，用于当所述组呼中有UE在该下行TTI中有个体业务待调度时，对所述UE的个体业务采用C-RNTI或SPS C-RNTI在专用空间进行调度。
进一步的，该装置还包括业务监控模块803，用于监控所述组呼中在该小区的各UE在该下行TTI是否有个体业务待调度，并通知所述第一调度模块801和第二调度模块802。其中所述监控包括：从网络侧获知有个体业务待调度的UE是否属于所述组呼；或从网络侧获知参与所述组呼的UE，监控本小区中有个体业务待调度的UE并判断其是否属于所述组呼。
所述调度为动态调度或半静态调度；所述组呼业务为一个或多个；在该下行TTI中有个体业务待调度的UE为1个或多个。其中所述个体业务为点到点业务。
实施例四：
如图9所示，本申请实施例四还公开了一种终端900，包括第一模块901，所述第一模块901用于在一个下行TTI中，采用G-RNTI或SPS G-RNTI在公共空间进行PDCCH盲检，如果在公共空间未盲检到G-RNTI或SPS G-RNTI，则继续在专用空间进行PDCCH盲检，然后退出所述盲检。
进一步的，所述第一模块901还用于，如果在公共空间盲检到G-RNTI或SPS G-RNTI，且所述终端为RRC_Idle状态，则所述第一模块901退出所述盲检。
更进一步的，该终端还包括第二模块902，如果在公共空间盲检到G-RNTI或SPS G-RNTI，且所述终端为RRC_Connected状态，则所述第二模块902用于采用C-RNTI或SPS C-RNTI在专用空间进行PDCCH盲检，然后退出所述盲检。
优选的，该终端还包括第三模块903，用于记录终端为RRC_Connected状态或RRC_Idle状态。
实施例五
如图10所示，本申请还公开了一种下行控制信道处理装置，该装置包括一中央处理器(CPU)101、一内存102以及一非易失存储器103。
其中，非易失性存储器103存储有用于实现下行控制信道处理的计算机程序。
CPU101可以从非易失性存储器103中将所述计算机程序加载到内存102中运行，形成计算机可执行指令。其中所述计算机可执行指令包括第一调度指令1021和第二调度指令1022。
第一调度指令1021用于指示对所述组呼业务进行调度，具体包括：当所述组呼中有UE在该下行TTI中有个体业务待调度时，指示对所述组呼业务采用G-RNTI或SPS G-RNTI在公共空间进行调度；当所述组呼中的所有UE在该下行TTI中均没有个体业务待调度时，指示对所述组呼业务采用G-RNTI或SPS G-RNTI在专用空间进行调度；所述第二调度指令1022，用于当所述组呼中有UE在该下行TTI中有个体业务待调度时，指示对所述UE的个体业务采用C-RNTI或SPS C-RNTI在专用空间进行调度。
进一步的，所述计算机可执行指令还包括业务监控指令1023，用于指示监控所述组呼中在该小区的各UE在该下行TTI是否有个体业务待调度。其中所述监控包括：从网络侧获知有个体业务待调度的UE是否 属于所述组呼；或从网络侧获知参与所述组呼的UE，监控本小区中有个体业务待调度的UE并判断其是否属于所述组呼。
所述调度为动态调度或半静态调度；所述组呼业务为一个或多个；在该下行TTI中有个体业务待调度的UE为1个或多个。其中所述个体业务为点到点业务。
实施例六
如图11所示，本申请还公开了一种终端，该终端包括一中央处理器(CPU)111、一内存112以及一非易失存储器113。
其中，非易失性存储器113存储有用于实现下行控制信道处理的计算机程序。
CPU111可以从非易失性存储器113中将所述计算机程序加载到内存112中运行，形成计算机可执行指令。其中所述计算机可执行指令包括第一指令1121。
所述第一指令1121用于在一个下行TTI中，指示采用G-RNTI或SPS G-RNTI在公共空间进行PDCCH盲检，如果在公共空间未盲检到G-RNTI或SPS G-RNTI，则指示继续在专用空间进行PDCCH盲检，然后退出所述盲检。
进一步的，如果在公共空间盲检到G-RNTI或SPS G-RNTI，且所述终端为RRC_Idle状态，则所述第一指令1121还用于指示退出所述盲检。
进一步的，所述计算机可执行指令还包括第二指令1122，如果在公共空间盲检到G-RNTI或SPS G-RNTI，且所述终端为RRC_Connected状态，则所述第二指令1122用于指示采用C-RNTI或SPS C-RNTI在专用空间进行PDCCH盲检，然后退出所述盲检。
更进一步的，所述计算机可执行指令还包括第三指令1123，用于指示记录终端为RRC_Connected状态或RRC_Idle状态。
本申请还公开了一种下行控制信道处理系统，该系统由如上述的一种下行控制信道处理装置和上述的一种终端组成。
通过以上实施例可以看出，本申请提出的下行控制信道处理方法、装置和系统中，不仅能够支持多组集群业务的并发调度，增强了集群业务系统增益，同时无需增加UE盲检次数，降低了UE搜索复杂度。
上述实施例仅仅是本申请一部分实施例，而不是全部的实施例。凡在本申请的精神和原则之内，本领域普通技术人员在没有做出创造性劳动前提下所作的任何修改、等同替换或改进等，均应属于本申请保护的范围之内。

Claims (22)

  1. 一种下行控制信道处理方法，其特征在于，在一个下行TTI中有组呼业务待调度时，包括如下步骤：
    如果当前小区的所述组呼中有UE在该下行TTI中有个体业务待调度，则发送端对所述组呼业务采用G-RNTI或SPS G-RNTI在公共空间进行调度，对所述UE的个体业务采用C-RNTI或SPS C-RNTI在专用空间进行调度；
    如果当前小区的所述组呼中的所有UE在该下行TTI中均没有个体业务待调度，则发送端对所述组呼业务采用G-RNTI或SPS G-RNTI在专用空间进行调度。
  2. 根据权利要求1所述的方法，其特征在于，所述调度为动态调度或半静态调度。
  3. 根据权利要求1所述的方法，其特征在于，所述组呼业务为一个或多个。
  4. 根据权利要求1所述的方法，其特征在于，所述在该下行TTI中有个体业务待调度的UE为1个或多个。
  5. 根据权利要求1所述的方法，其特征在于，所述在该下行TTI中有个体业务待调度的UE处于RRC_Connected状态。
  6. 根据权利要求1所述的方法，其特征在于，在发送端调度所述组呼业务之前，所述方法进一步包括：判断所述组呼中是否有UE在该下行TTI中有个体业务待调度；
    所述判断所述组呼中是否有UE在该下行TTI中有个体业务待调度包括：
    从网络侧获知有个体业务待调度的UE是否属于所述组呼；或，
    从网络侧获知参与所述组呼的UE，监控本小区中有个体业务待调度的UE并判断其是否属于所述组呼。
  7. 根据权利要求1～6任意一项所述的方法，其特征在于，所述个体业务为点到点业务。
  8. 一种下行控制信道处理装置，其特征在于，包括第一调度模块和第二调度模块，
    在一个下行TTI中有组呼业务待调度时，所述第一调度模块，用于对所述组呼业务进行调度，具体包括：
    当所述组呼中有UE在该下行TTI中有个体业务待调度时，对所述组呼业务采用G-RNTI或SPS G-RNTI在公共空间进行调度；当所述组呼中的所有UE在该下行TTI中均没有个体业务待调度时，对所述组呼业务采用G-RNTI或SPS G-RNTI在专用空间进行调度；
    所述第二调度模块，用于当所述组呼中有UE在该下行TTI中有个体业务待调度时，对所述UE的个体业务采用C-RNTI或SPS C-RNTI在专用空间进行调度。
  9. 根据权利要求8所述的装置，其特征在于，该装置还包括业务监控模块，用于监控所述组呼中在该小区的各UE在该下行TTI是否有个体业务待调度，并通知所述第一调度模块和第二调度模块。
  10. 根据权利要求9所述的装置，其特征在于，所述监控包括：
    从网络侧获知有个体业务待调度的UE是否属于所述组呼；或，
    从网络侧获知参与所述组呼的UE，监控本小区中有个体业务待调度的UE并判断其是否属于所述组呼。
  11. 根据权利要求8所述的装置，其特征在于，所述调度为动态调度或半静态调度。
  12. 根据权利要求8所述的装置，其特征在于，所述组呼业务为一 个或多个。
  13. 根据权利要求8所述的装置，其特征在于，所述在该下行TTI中有个体业务待调度的UE为1个或多个。
  14. 根据权利要求8所述的装置，其特征在于，所述个体业务为点到点业务。
  15. 一种下行控制信道处理方法，其特征在于，包括如下步骤：在一个下行TTI中，UE采用G-RNTI或SPS G-RNTI在公共空间进行PDCCH盲检，如果在公共空间未盲检到G-RNTI或SPS G-RNTI，则继续在专用空间进行PDCCH盲检，然后退出所述盲检。
  16. 根据权利要求15所述的方法，其特征在于，该方法还包括：如果UE在公共空间盲检到G-RNTI或SPS G-RNTI，且所述UE处于RRC_Idle状态，则退出所述盲检。
  17. 根据权利要求15或16所述的方法，其特征在于，该方法还包括：如果UE在公共空间盲检到G-RNTI或SPS G-RNTI，且所述UE处于RRC_Connected状态，则继续采用C-RNTI或SPS C-RNTI在专用空间进行PDCCH盲检，然后退出所述盲检。
  18. 一种用于下行控制信道处理的终端，其特征在于，该终端包括第一模块，所述第一模块用于在一个下行TTI中，采用G-RNTI或SPS G-RNTI在公共空间进行PDCCH盲检，如果在公共空间未盲检到G-RNTI或SPS G-RNTI，则继续在专用空间进行PDCCH盲检，然后退出所述盲检。
  19. 根据权利要求18所述的终端，其特征在于，所述第一模块还用于，如果在公共空间盲检到G-RNTI或SPS G-RNTI，且所述终端为RRC_Idle状态，则所述第一模块退出所述盲检。
  20. 根据权利要求18所述的终端，其特征在于，该终端还包括第二 模块，如果在公共空间盲检到G-RNTI或SPS G-RNTI，且所述终端为RRC_Connected状态，则所述第二模块用于采用C-RNTI或SPS C-RNTI在专用空间进行PDCCH盲检，然后退出所述盲检。
  21. 根据权利要求18所述的终端，其特征在于，该终端还包括第三模块，用于记录所述终端为RRC_Connected状态或RRC_Idle状态。
  22. 一种下行控制信道处理系统，其特征在于，该系统包括如权利要求8～14任意一项所述的装置和如权利要求18～21任意一项所述的终端。
PCT/CN2014/092770 2013-12-03 2014-12-02 一种下行控制信道处理方法、装置和系统 WO2015081844A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US15/309,455 US20170188341A1 (en) 2013-12-03 2014-12-02 Method, Apparatus and System for Processing Downlink Control Channels

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201310642353.7 2013-12-03
CN201310642353.7A CN104683957B (zh) 2013-12-03 2013-12-03 一种下行控制信道处理方法、装置和系统

Publications (1)

Publication Number Publication Date
WO2015081844A1 true WO2015081844A1 (zh) 2015-06-11

Family

ID=53272890

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2014/092770 WO2015081844A1 (zh) 2013-12-03 2014-12-02 一种下行控制信道处理方法、装置和系统

Country Status (3)

Country Link
US (1) US20170188341A1 (zh)
CN (1) CN104683957B (zh)
WO (1) WO2015081844A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107071747A (zh) * 2017-02-14 2017-08-18 北京北方烽火科技有限公司 群组业务调度方法、装置及基站

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104703145B (zh) * 2013-12-09 2018-05-11 北京信威通信技术股份有限公司 集群组呼盲检能力处理方法、装置和系统
US10772101B2 (en) 2015-12-08 2020-09-08 Huawei Technologies Co., Ltd. Systems and methods for determining air interface configuration
US10536946B2 (en) * 2015-12-08 2020-01-14 Huawei Technologies Co., Ltd. Method and system for performing network slicing in a radio access network
CN108934070B (zh) * 2017-05-24 2020-08-21 大唐移动通信设备有限公司 一种物理下行控制信道资源调度方法及装置
CN109428698B (zh) * 2017-08-25 2021-05-18 成都鼎桥通信技术有限公司 基于终端能力上报的信道资源调度方法及基站
US10314061B1 (en) * 2017-10-05 2019-06-04 Sprint Spectrum L.P. Systems and methods for performing a group call using a data bearer
CN110139226B (zh) * 2018-02-09 2021-07-16 成都鼎桥通信技术有限公司 一种基于B-TrunC的群组状态处理方法和设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2013025086A2 (ko) * 2011-08-18 2013-02-21 엘지전자 주식회사 제어 채널의 할당 방법 및 이를 위한 장치
CN103052167A (zh) * 2011-10-17 2013-04-17 鼎桥通信技术有限公司 一种下行调度命令空间的配置方法
CN103052033A (zh) * 2011-10-17 2013-04-17 鼎桥通信技术有限公司 专网中用户设备的数据处理方法
CN103166737A (zh) * 2011-12-16 2013-06-19 鼎桥通信技术有限公司 群组业务加扰方法、解扰方法、基站和用户设备

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101699901B (zh) * 2009-09-28 2012-08-08 上海华为技术有限公司 优化用户设备搜索空间的方法及装置
CN102958047B (zh) * 2011-08-26 2015-04-15 普天信息技术研究院有限公司 一种宽带集群通信系统的终端下行分配接收方法
CN103108285A (zh) * 2011-11-10 2013-05-15 中兴通讯股份有限公司 一种集群业务的实现方法及基于eMBMS的集群系统
US9277533B2 (en) * 2012-05-17 2016-03-01 Vid Scale, Inc. Scalable video coding over simultaneous unicast/multicast LTE DL shared channel
CN102802269B (zh) * 2012-08-23 2014-12-10 合肥东芯通信股份有限公司 调度信息处理的方法、装置及系统
CN102882644B (zh) * 2012-09-21 2015-09-16 中兴通讯股份有限公司 下行控制信息的检测处理、检测方法及装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2013025086A2 (ko) * 2011-08-18 2013-02-21 엘지전자 주식회사 제어 채널의 할당 방법 및 이를 위한 장치
CN103052167A (zh) * 2011-10-17 2013-04-17 鼎桥通信技术有限公司 一种下行调度命令空间的配置方法
CN103052033A (zh) * 2011-10-17 2013-04-17 鼎桥通信技术有限公司 专网中用户设备的数据处理方法
CN103166737A (zh) * 2011-12-16 2013-06-19 鼎桥通信技术有限公司 群组业务加扰方法、解扰方法、基站和用户设备

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107071747A (zh) * 2017-02-14 2017-08-18 北京北方烽火科技有限公司 群组业务调度方法、装置及基站

Also Published As

Publication number Publication date
CN104683957A (zh) 2015-06-03
US20170188341A1 (en) 2017-06-29
CN104683957B (zh) 2018-12-04

Similar Documents

Publication Publication Date Title
WO2015081844A1 (zh) 一种下行控制信道处理方法、装置和系统
US9877278B2 (en) Monitoring a narrowband control channel for a wideband system to reduce power consumption
US20220279479A1 (en) User Equipment (UE) Grouping Criteria and Mechanisms for False Paging Reduction
WO2019214596A1 (zh) 参数确定的方法、监控方法、通信装置
WO2020029945A1 (zh) 确定载波聚合下监控pdcch候选数目的方法和装置
WO2018201784A1 (zh) 资源配置和调度方法、基站以及用户设备
WO2016146073A1 (zh) 一种支持多用户叠加的ue、基站中的方法和设备
JP5852253B2 (ja) 下りリンクのリソースのスケジューリング
WO2012149848A1 (zh) 一种数据传输的方法、系统和设备
JP2012529239A5 (zh)
JP7407307B2 (ja) マルチキャリアスケジューリング方法、及び装置
WO2013023541A1 (zh) 一种下行控制信息传输方法及装置
CN102958047B (zh) 一种宽带集群通信系统的终端下行分配接收方法
WO2018058485A1 (zh) 下行控制信息监听、发送、接收方法及装置
US20170202032A1 (en) Method, Apparatus and System for Processing Blind Detection Capability During Trunking Group Call
JP2016059062A (ja) 下りリンクのリソースのスケジューリング
WO2019153201A1 (zh) 一种信道检测方法及装置、计算机存储介质
CN113455080A (zh) 未授权带宽部分中的资源分配
WO2019047659A1 (zh) 一种指示以及下行控制信道检测方法、设备、装置
CN107295660B (zh) 一种资源调度及数据检测方法、装置、相关设备和系统
JP2022515877A (ja) 制御リソースセットの周波数領域ロケーションを決定するための方法および関係するデバイス
WO2016062072A1 (zh) 一种资源分配装置、系统及方法
TWI482471B (zh) 處理控制通道的方法及其通訊裝置
CN113647163B (zh) 一种通信方法及设备
KR20230017276A (ko) 다운링크 제어 정보(dci) 전송 방법 및 관련 기기

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 14866939

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 15309455

Country of ref document: US

122 Ep: pct application non-entry in european phase

Ref document number: 14866939

Country of ref document: EP

Kind code of ref document: A1