WO2013102392A1 - 一种实现集群组呼业务的方法及装置 - Google Patents

一种实现集群组呼业务的方法及装置 Download PDF

Info

Publication number
WO2013102392A1
WO2013102392A1 PCT/CN2012/086457 CN2012086457W WO2013102392A1 WO 2013102392 A1 WO2013102392 A1 WO 2013102392A1 CN 2012086457 W CN2012086457 W CN 2012086457W WO 2013102392 A1 WO2013102392 A1 WO 2013102392A1
Authority
WO
WIPO (PCT)
Prior art keywords
cluster
group
call service
user terminal
group call
Prior art date
Application number
PCT/CN2012/086457
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 EP12864427.5A priority Critical patent/EP2793492B1/en
Publication of WO2013102392A1 publication Critical patent/WO2013102392A1/zh
Priority to US14/323,963 priority patent/US9661478B2/en

Links

Classifications

    • 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
    • H04W4/10—Push-to-Talk [PTT] or Push-On-Call services
    • 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
    • H04W72/00—Local resource management
    • H04W72/30—Resource management for broadcast services

Definitions

  • the cluster group call service is the most basic service provided in the trunking communication technology, and allows the user terminal to establish a cluster call to a certain group of user terminals in a given area, where the given area is called a group call area.
  • the members of the two types of identities that is, the dispatcher and the user terminal that has signed the cluster call service are included.
  • the dispatcher Within a cluster, there can be no dispatchers.
  • the user terminals in the cluster use half-duplex mode for communication. During the call, only one user terminal in the cluster speaks at the same time (the user terminal in the group sending state), and other user terminals passively answer ( User terminal in the group receiving state).
  • Each user terminal in the cluster can seize the voice by pressing the PTT button (push to talk: key) to obtain a speech opportunity. Only when the user terminal that obtains the voice right releases the PTT button, other user terminals in the cluster can Get the right to speak.
  • Each cluster has a unique group identification number for implementing cluster group call services. Any user terminal in the cluster can initiate a group call of the cluster. After the user terminal in the cluster enters the cluster identification number of the cluster and then presses the PTT button, the group call of the cluster can be initiated to implement the cluster group call service.
  • the cluster group call service is implemented in the GSM network, there are two special working states: Group receiving status: The user terminal acts as the cluster group call service data receiver, and the cell does not A dedicated channel is allocated, and the user terminal can only listen to the group call information.
  • the user terminal is the sender of the cluster group call service data, and the cell allocates two dedicated uplink channels to the user terminal for respectively transmitting the data information and the control information sent by the mobile user terminal.
  • An object of the present invention is to provide a method, a system, and a network entity for implementing a group call service, which can reduce the number of evolved cells that belong to the evolved cell in the same cluster and are in a group receiving state.
  • the cost of the configuration command brought by the configuration of the scheduling resource by the user terminal improves the resource utilization of the evolved cell.
  • the present invention employs the following technical solutions:
  • a method for implementing a group call service includes:
  • the user terminal of the trunking group call service receives cluster configuration information, a downlink authorization message, and/or an uplink grant message from the evolved cell;
  • the user terminal of the cluster group call service saves the cluster configuration information, a downlink grant message, and/or an uplink grant message;
  • the downlink resource indicated by the downlink grant message is shared in a semi-persistent scheduling manner, and the cluster group is received. Calling business data; and/or
  • the present invention also provides a method for implementing a trunking group call service, including: the evolved cell configuring cluster configuration information, a downlink grant message, and/or an uplink for a user terminal of the cluster group call service in the evolved cell.
  • An authorization message the downlink grant message indicating a downlink resource shared by the user terminal in a group receiving state at a different time in a semi-persistent scheduling manner; the uplink grant message indicating a user in a group sending state at different times The uplink resources used by the terminal in a semi-persistent scheduling manner;
  • the evolved cell sends the cluster configuration information, a downlink grant message, and/or an uplink grant message to a user terminal of the cluster group call service.
  • the present invention further provides an apparatus for implementing a trunking group call service, comprising: a receiving module, configured to receive cluster configuration information, a downlink grant message, and/or an uplink grant message from an evolved cell;
  • a saving module configured to save cluster configuration information, a downlink grant message, and/or an uplink grant message received by the receiving module
  • a first processing module configured to share downlink resources indicated by the downlink grant message in a semi-persistent scheduling manner according to the cluster configuration information saved by the save module when the group is in a group receiving state at different times, and receive the set Group call service data;
  • a second processing module configured to: when the group is in a group sending state at different times, use the uplink resource indicated by the uplink grant message in a semi-persistent scheduling manner according to the cluster configuration information saved by the saving module, and send The cluster group calls the service data.
  • the present invention further provides an apparatus for implementing a trunking group call service, comprising: a configuration module, configured to configure, by an evolved cell, cluster configuration information, a downlink, for a user terminal of a cluster group call service in the evolved cell An authorization message and/or an uplink grant message, the downlink grant message indicating a downlink resource shared by the user terminal in a group receiving state at different times in a semi-persistent scheduling manner; the uplink grant message indicating Uplink resources used by user terminals in the group transmission state at different times in a semi-persistent scheduling manner;
  • a sending module configured to send the cluster configuration information, the downlink grant message, and/or the uplink grant message configured by the configuration module to the user terminal of the cluster group call.
  • the beneficial effects of the present invention are: when the cluster group call service is implemented, if the user terminal of the cluster group call service is in the group receiving state at different times, the cluster configuration information may be semi-static according to the cluster configuration information.
  • the scheduling mode shares the downlink resource indicated by the downlink grant message, and/or if the user terminal of the cluster group call service is in the group sending state at different times, the uplink may be used in a semi-persistent scheduling manner according to the cluster configuration information.
  • the uplink resource indicated by the link grant message In this way, the evolved cell does not need to separately configure the downlink resources and/or the uplink resources for the user terminals in the cluster, thereby reducing the evolved cell by configuring the downlink for the user terminals in the cluster separately and repeatedly.
  • the overhead of configuration instructions brought by resources and/or uplink resources thereby improving resource utilization of the evolved cell.
  • FIG. 1 is a schematic flowchart of a first embodiment of a method for implementing a group call service according to the present invention
  • FIG. 2 is a schematic flowchart of a second embodiment of a method for implementing a group call service according to the present invention
  • FIG. 3 is a schematic flowchart of a third embodiment of a method for implementing a group call service according to the present invention.
  • FIG. 4 is a schematic flowchart of a fourth embodiment of a method for implementing a group call service according to the present invention.
  • FIG. 5 is a schematic flowchart of a fifth embodiment of a method for implementing a group call service according to the present invention.
  • FIG. 6 is a schematic structural diagram of a first embodiment of an apparatus for implementing a trunking group call service according to the present invention
  • FIG. 7 is a schematic structural diagram of a second embodiment of an apparatus for implementing a trunking group call service according to the present invention
  • FIG. Figure 8 is a schematic structural view of an embodiment of the first processing module of Figure 6 of the present invention
  • FIG. 9 is a schematic structural view of an embodiment of a second processing module of FIG. 6 of the present invention.
  • FIG. 10 is a schematic structural diagram of a third embodiment of an apparatus for implementing a trunking group call service according to the present invention.
  • the technical solutions in the embodiments of the present invention are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present invention. It is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of them. Example. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present invention without creative efforts are within the scope of the present invention.
  • the present invention discloses a method and apparatus for implementing a cluster group call service.
  • the semi-persistent scheduling mode specifically refers to the process of transmitting or receiving service data at the same time-frequency resource location by the user terminal in a fixed period of time in the LTE scheduling resource transmission process, so that the evolved cell does not need to be the user terminal again. Reconfigure the scheduling resources. That is to say, when using the semi-static scheduling mode, the characteristics of the voice data packets periodically reaching the user terminal can be fully utilized, and the scheduling resources required for the same user terminal need only be configured once and activated once, and can be used periodically.
  • the cluster group call service is a service in which the packet size is relatively fixed, and the data packet arrives at the user terminal to satisfy a certain periodicity.
  • the user terminals in the cluster use the half-duplex mode to communicate, and only one user terminal occupies the voice at the same time (the user in the group sending state) Terminal occupies the right to speak), multiple uses The terminal does not have the right to speak at the same time (the user terminal in the group receiving state has no right to speak).
  • Step S11 The user terminal of the trunking group call service receives the cluster configuration information, the downlink grant message, and/or the uplink grant message from the evolved cell.
  • the user terminal of the cluster group call service is any one of the multiple user terminals.
  • the received cluster configuration information from the evolved cell includes: a semi-persistent scheduling period for indicating a time interval for receiving or transmitting the cluster group call service data, and a PCI (physical cell identity) for uniquely identifying the evolved cell Identification).
  • the cluster configuration information also includes the group cell radio network temporary identifier Group C-RNTI used by the cluster group scheduling, and some feedback information.
  • the downlink grant message and/or uplink grant message being used to correspondingly indicate downlink resources and/or uplink resources.
  • the user terminal of the trunking group call service first receives the cluster configuration information from the evolved cell, and after receiving the received cluster configuration information, receives the downlink grant message from the evolved cell and/or Uplink grant message.
  • Step S12 The user terminal of the cluster group call service saves the cluster configuration information, a downlink grant message, and/or an uplink grant message.
  • Step S13 If the user terminal of the trunking group call service is in the group receiving state at different times, according to the cluster configuration information, share the downlink resource indicated by the downlink grant message in a semi-persistent scheduling manner, and receive the cluster.
  • Group call business data
  • the user terminal of the trunking group call service may be in the group receiving state or may be in the group receiving state.
  • the user terminal in the group receiving state does not need to send the cluster group call service data, and only needs to passively receive the cluster group call service data. Therefore, when the user terminal of the cluster group call service is in the group receiving state, the user terminal in the group receiving state may Receiving cluster group call service data according to the downlink resource indicated by the downlink grant message;
  • the user terminal of the trunking group call service may be in a group sending state or may be in a group receiving state; at different times, when the user terminal of the cluster group call service is in a group receiving state, The user terminal in the group receiving state may receive the cluster group call service data according to the downlink resource indicated by the downlink grant message. For example, at time T1, the user terminal of the cluster group call service is in a group receiving state, and the downlink resource F1 indicated by the downlink grant message is used in a semi-persistent scheduling manner to receive the cluster group call service data.
  • the user terminal of the cluster group call service is in the group receiving state, and the downlink resource F1 indicated by the downlink grant message can still be used in the semi-persistent scheduling manner to receive the cluster group call service data.
  • the user terminal of the trunking group call service can receive the cluster group call service data by using the downlink resource indicated by the downlink grant message in a semi-persistent scheduling manner as long as it is in the group receiving state.
  • the user terminal of the cluster group call service is any user terminal in the process of implementing the group call service.
  • the user terminals in the group receiving state can share the downlink resources. Therefore, it can be understood that, in the implementation process of the group call service, all user terminals in the group receiving state can share the downlink resources indicated by the downlink grant message.
  • Step S14 If the user terminal of the trunking group call service is in the group sending state at different times, according to the cluster configuration information, the uplink resource is used in turn in a semi-persistent scheduling manner, and the group call service data is sent.
  • the user terminal of the trunking group call service may be in the group sending state or may be in the group receiving state.
  • the user terminal in the group sending state uses the uplink resource indicated by the uplink grant message in a semi-persistent scheduling manner to send the cluster group call service. data.
  • the user terminal of the group call service is in the group sending state, it can still send the cluster group call service data by using the uplink resource indicated by the uplink grant message in a semi-persistent scheduling manner. It can be understood that the user terminal of the trunking group call service can receive the cluster group call service by using the uplink resource indicated by the uplink grant message in a semi-persistent scheduling manner as long as it is in the group sending state. Data.
  • the user terminal of the cluster group call service is any user terminal in the process of implementing the group call service.
  • the uplink resource indicated by the uplink grant message is in the group sending state, because the group transmitting state may not be the same user terminal at different times. User terminals are used in turn.
  • step S13 may be performed and step S14 may be performed; or only step S13 or step S14 may be performed.
  • the execution of step S13 and step S14 has no clear sequence.
  • the downlink resource indicated by the downlink grant message may be shared in a semi-persistent scheduling manner according to the cluster configuration information, and/or If the user terminal of the trunking group call service is in the group sending state at different times, the uplink resource indicated by the uplink grant message may be used in a semi-persistent scheduling manner according to the cluster configuration information.
  • the evolved cell does not need to separately configure the downlink resources and/or the uplink resources for the user terminals in the cluster, thereby reducing the evolved cells by configuring the downlink resources for the user terminals in the cluster separately and repeatedly. And the overhead of configuration instructions brought by the uplink resources, thereby improving the resource utilization of the evolved cell.
  • FIG. 2 it is a schematic flowchart of a second embodiment of an apparatus for implementing a group call service according to the present invention.
  • the method includes:
  • Step S21 The user terminal of the cluster group call service receives the cluster configuration information from the evolved cell.
  • Step S22 The user terminal of the cluster group call service determines whether the cluster configuration information is sent by an evolved cell to which it belongs.
  • the user terminal of the trunking group call service needs to determine whether the cluster configuration information received by the user terminal is sent by the evolved cell to which the UE belongs.
  • the user terminal of the cluster group call service can only use the evolved cell to which the group is called.
  • the downlink resource and/or uplink resource indicated by the cluster configuration information is not limited.
  • whether the cluster configuration information is sent by the evolved cell to which it belongs may be determined in the following manner:
  • the user terminal of the cluster group call service determines that the cluster configuration information is Whether it is sent by the evolved cell to which it belongs, including:
  • the user terminal of the cluster group call service determines whether the physical layer cell identifier PCI included in the received cluster configuration information matches the physical layer cell identifier PCI of the evolved cell, and if yes, determines that the cluster configuration information is the evolved cell to which the cluster configuration information belongs. dispatched.
  • Step S23 the user terminal of the cluster group call service saves the cluster configuration information
  • Step S24 the user terminal of the cluster group call service receives a downlink grant message and/or an uplink grant from an evolved cell. Message
  • Step S25 The user terminal of the cluster group call service saves the downlink grant message and/or an uplink grant message.
  • Step S26 If the user terminal of the trunking group call service is in the group receiving state at different times, according to the cluster configuration information, the downlink resource indicated by the downlink grant message is shared in a semi-persistent scheduling manner, and the receiving cluster is received.
  • Group call business data
  • Step S27 If the user terminal of the cluster group call service is in the group sending state at different times, according to the cluster configuration information, the uplink resource indicated by the uplink grant message is used in turn in a semi-persistent scheduling manner, and the sending set is sent. Group calls business data.
  • step S25 to step S27 is the same as the operation of step S12 to step S14 in the embodiment shown in FIG. 1, and details are not described herein.
  • FIG. 3 it is a schematic flowchart of a third embodiment of a method for implementing a group call service according to the present invention.
  • the method includes:
  • Step S31 The user terminal of the trunking group call service receives the cluster configuration information, the downlink grant message, and/or the uplink grant message from the evolved cell.
  • Step S32 the user terminal of the cluster group call service saves the cluster configuration information, a downlink grant message, and/or an uplink grant message;
  • step S31 - step S32 are the same as the operations of step S11 - step S22 in the embodiment shown in Fig. 1, and the description will not be repeated here. It can be understood that, before saving the cluster configuration information, the user terminal that includes the cluster group call service can determine whether the cluster configuration information received by the UE is sent by the evolved cell to which it belongs.
  • Step S33 If the user terminal of the trunking group call service is in the group receiving state at the initial moment, activate the downlink resource indicated by the downlink grant message, and according to the downlink resource
  • the source receives the cluster group call service data
  • the initial time refers to the time when the user terminal of the trunking group call service receives the downlink resource from the evolved cell.
  • the downlink grant message sent by the evolved cell is physical downlink control channel PDCCH signaling scrambled by the Group C-RNTI.
  • the user terminal of the trunk group call service is in a different state, and the operation after receiving the downlink grant message is different.
  • the downlink resource indicated by the downlink grant message is activated, and the cluster group call service data is received according to the downlink resource; Since the downlink grant message can be in the cluster configuration information
  • the Group C-RNTI de-scrambled PDCCH signaling Therefore, the user terminal in the group receiving state needs to use the Group C-RNTI included in the cluster configuration information before activating the downlink resource indicated by the downlink grant message. Desmut the PDCCH signaling.
  • step S35 the process proceeds to step S35.
  • Step S34 If the user terminal of the cluster group call service is in the group sending state at the initial time, record the time point at which the first user terminal activates the downlink resource indicated by the downlink grant message; the first user terminal a user terminal that is in a group receiving state during the implementation of the cluster group call service;
  • the other user terminals of the trunking group call service are in the group sending state at the initial moment and the activation of the downlink authorization message is performed.
  • the operation of the downlink resource for example, the first user terminal is in a group reception state, and performs an operation of activating a downlink resource indicated by the downlink grant message. Therefore, the user terminal of the trunking group call service needs to record the time point at which the first user terminal activates the downlink resource indicated by the downlink grant message.
  • the user terminal of the cluster group call service can know the time when the first user terminal activates the downlink resource, because the user terminal of the cluster group call service belongs to the same cluster as the first user terminal. point.
  • the user terminal of the trunking group call service is in a group sending state, which records the time T2 at which the downlink resource is activated, and after two semi-static periods have elapsed, the cluster group
  • the user terminal of the call service is in a group receiving state, and according to the semi-persistent scheduling periods T and T2, the downlink receiving time is calculated as 2T+T2, and the downlink is indicated according to the saved downlink grant message.
  • the resource receives the cluster group call service data.
  • the user terminal of the trunking group call service needs to activate the downlink resource before using the downlink resource. If the user terminal of the trunking group call service is in the group receiving state at the initial time, it is necessary to record the time point at which the other user terminal activates the downlink resource. In the implementation of the subsequent cluster group call service, if the user terminal of the cluster group call service is in the group receiving state, the downlink resource does not need to be activated. That is to say, in the implementation of the entire cluster group call service, the downlink resource only needs to be activated once, and the downlink terminal can be periodically used if the user terminal of the cluster group call service is in the group receiving state. Resources.
  • the evolved cell does not need to separately send the downlink grant message for the user terminal, so the overhead of the evolved cell configuration command can be further reduced, and the evolution is further improved. Resource utilization of the community.
  • step S33-step S34 is equivalent to the operation of step S13 in the embodiment shown in FIG. 1.
  • Step S35 If the user terminal of the trunking group call service is in the group sending state at the initial time, activate the uplink resource indicated by the uplink grant message, and send the cluster group call according to the uplink resource.
  • Business data
  • the initial time refers to the time when the user terminal of the trunking group call service receives the uplink resource from the evolved cell.
  • the uplink grant message sent by the evolved cell may be PDCCH signaling scrambled by the Group C-RNTI.
  • the user terminal of the trunking group call service After receiving the uplink grant message, the user terminal of the trunking group call service is in a different state, and the operation after receiving the uplink grant message is different.
  • the uplink resource indicated by the uplink grant message is activated, and the cluster group call service data is sent according to the uplink resource. Since the uplink grant message is PDCCH signaling scrambled by the Group C-RNTI, the user terminal in the group receiving state needs to use the cluster before activating the uplink resource indicated by the uplink grant message.
  • the Group C-RNTI included in the configuration information is used to descramble the PDCCH signaling.
  • step S36 the process proceeds to step S36.
  • Step S36 If the user terminal of the cluster group call service is in the group receiving state at the initial time, record a time point at which the second user terminal activates the uplink resource indicated by the uplink grant message, where the second The user terminal is a user terminal that is in a group sending state during the implementation of the cluster group call service;
  • the user terminal of the trunking group call service If the user terminal of the trunking group call service is in the group receiving state at the initial moment, it indicates that other user terminals of the trunking group call service are in the group receiving state at the initial moment and perform the activation of the uplink grant message indication.
  • the operation of the uplink resource for example, the second user terminal is in a group transmission state, and performs an operation of activating an uplink resource indicated by the uplink grant message. Therefore, the user terminal of the trunking group call service needs to record the time point at which the second user terminal activates the uplink resource indicated by the uplink grant message.
  • the user terminal of the cluster group call service can know the time when the second user terminal activates the uplink resource, because the user terminal of the cluster group call service and the second user terminal belong to the same cluster. point.
  • the user terminal of the cluster group call service is in a group sending state at different times, according to the semi-persistent scheduling period and the record, in the implementation process of the subsequent cluster group call service.
  • the user terminal of the trunking group call service is in a group receiving state, which records a time point T4 at which the uplink resource is activated, and after two semi-static periods have elapsed, the cluster
  • the user terminal of the group call service is in a group sending state, and according to the semi-persistent scheduling period T and T4, the uplink transmission time is calculated as 2T+T4, and according to the saved uplink grant message.
  • the indicated uplink resource sends the cluster group call service data.
  • the user terminal of the trunking group call service needs to activate the uplink resource before using the uplink resource;
  • the user terminal of the group call service is in the group sending state at the initial time, it is necessary to record the time point at which the other user terminal activates the uplink resource.
  • the uplink resource does not need to be activated. That is to say, in the implementation of the entire cluster group call service, the uplink resource only needs to be activated once, and if the user terminal of the cluster group call service is in the group sending state, the uplink can be used periodically.
  • Resource send cluster group call service data.
  • the evolved cell does not need to separately send an uplink grant message, so the overhead of the evolved cell configuration command can be further reduced, and the evolved cell is further improved.
  • step S35-step S36 corresponds to the operation of step S13 in the embodiment shown in FIG. 1.
  • FIG. 4 it is a schematic flowchart of a fourth embodiment of a method for implementing a group call service according to the present invention.
  • the method includes:
  • Step S41 The evolved cell configures cluster configuration information, a downlink grant message, and/or an uplink grant message for the user terminal of the cluster group call service in the evolved cell;
  • the downlink grant message indication is at different times a downlink resource shared by the user terminal in the receiving state in a semi-persistent scheduling manner;
  • the uplink grant message indicating an uplink resource that is used by the user terminal in the group transmitting state at different times in a semi-persistent scheduling manner;
  • the cluster configuration information configured by the evolved cell includes a semi-persistent scheduling period for indicating a time interval for receiving or transmitting the cluster group call service data, a physical layer cell identifier for uniquely identifying the evolved cell, and a cluster group scheduling use.
  • Group cell wireless network temporary identity Group C-RNTL Group cell wireless network temporary identity Group C-RNTL
  • Step S42 The evolved cell sends the cluster configuration information, a downlink grant message, and/or an uplink grant message to a user terminal of the cluster group call service.
  • the evolved cell is a user terminal that first sends the cluster configuration information to the cluster group call service, and after the user terminal of the cluster group call service receives the cluster configuration information, and then sends the downlink. A way authorization message and/or an uplink grant message is sent to the user terminal.
  • the cluster group call notification message is sent to the user terminal of the cluster group call service in the form of a paging message or a new public control message.
  • the cluster group call notification message carries the cluster configuration information.
  • the cluster group call notification message becomes a paging message, and the paging message carries the cluster configuration information.
  • the paging message is scrambled by the paging radio network temporary identifier P-RNTI.
  • P-RNTI is the same. Therefore, the user terminal of the trunking group call service can receive and save the cluster configuration information.
  • the cluster group call notification message may also be a new public control message that is redefined.
  • cell A defines a new common control message in which the cluster configuration information is included, and cell A sends the new common control message.
  • the new public control message may be scrambled using other public wireless network temporary identifiers RNTI. All user terminals of the trunking group call service have the same RNTI, so the user terminals of the cluster group call service can receive and save the cluster configuration information.
  • the downlink resource configured by the evolved cell indicates that the downlink resource shared by the semi-persistent scheduling mode when the user terminal of the cluster group call service is in the group receiving state, and/or the configured uplink
  • the authorization message indicates that there is an uplink resource that is used in a semi-persistent scheduling manner when the user terminal of the cluster group call service is in the group transmission state.
  • the evolved cell does not need to separately configure the downlink resources and/or the uplink resources for the user terminals in the cluster, thereby reducing the evolved cell by configuring the downlink for the user terminals in the cluster separately and repeatedly.
  • the overhead of configuration instructions brought by resources and/or uplink resources thereby improving resource utilization of the evolved cell.
  • FIG. 5 it is a schematic flowchart of a fifth embodiment of a method for implementing a group call service according to the present invention.
  • the method includes:
  • Step S51 The evolved cell configures cluster configuration information, a downlink grant message, and/or an uplink grant message for the user terminal of the cluster group call service in the evolved cell, where the downlink grant message indication is at different times.
  • User terminals in the group receiving state are shared in a semi-static scheduling mode.
  • Downlink resource; the uplink grant message indicates an uplink resource that is used by a user terminal in a group transmission state at different times in a semi-persistent scheduling manner;
  • Step S52 The evolved cell sends the cluster configuration information, a downlink grant message, and/or an uplink grant message to a user terminal of the cluster group call service.
  • step S51-step S52 is the same as the operation of step S41-step S42 in the embodiment shown in FIG. 4, and the description is not repeated here.
  • Step S53 In the process of implementing the subsequent cluster group call service, the evolved cell sends the cluster group call service data to the user terminal in the group receiving state according to the semi-persistent scheduling period according to the time point of activating the downlink resource. ;
  • the time point at which the downlink resource is activated is the time when the user terminal in the group receiving state at the initial time activates the downlink resource; in the process of implementing the cluster group call service, the evolved cell only sends A downlink grant message, the downlink grant message is scrambled by using a group cell radio network temporary identifier Group C-RNTI used by the cluster group scheduling in the cluster configuration information.
  • the downlink grant message may be PDCCH signaling scrambled by using a Group C-RNTI.
  • the downlink grant message may be a PDCCH signaling that is scrambled by the group C-RNTI. Therefore, the user terminal in the group receiving state needs to activate the downlink resource.
  • the PDCCH signaling is descrambled using the Group C-RNTI included in the cluster configuration information.
  • the initial moment is specifically a moment when the user terminal of the trunking group call service receives the downlink grant message.
  • the time point at which the downlink resource is activated is the time at which the user terminal in the group receiving state activates the downlink resource at the initial time.
  • the user terminal of the trunking group call service uses the semi-static scheduling mode to perform resource scheduling. Therefore, in the implementation process of the cluster group call service, the evolved cell sends only one downlink grant to the user terminal of the trunking group call service. Message. In the process of implementing the subsequent cluster group call service, the evolved cell according to the semi-static scheduling period according to the time point of activating the downlink resource The user terminal in the group receiving state sends the cluster group call service data. In this way, the evolved cell does not need to separately and repeatedly send the downlink grant message to the user terminal in the group receiving state, thereby reducing the overhead of the configuration command of the evolved cell, and further improving the resource utilization rate of the evolved cell.
  • Step S54 In the process of implementing the subsequent cluster group call service, the evolved cell receives the cluster group call service sent by the user terminal in the group sending state according to the semi-persistent scheduling period according to the time point of activating the uplink resource.
  • the time point at which the uplink resource is activated is the time when the user terminal in the group sending state activates the uplink resource at the initial time; in the process of implementing the cluster group call service, the evolved cell only sends An uplink grant message, the uplink grant message is scrambled by using a group cell radio network temporary identifier Group C-RNTI used by the cluster group scheduling in the cluster configuration information.
  • the uplink grant message may be PDCCH signaling scrambled by using a Group C-RNTI.
  • the user terminal in the group sending state After the uplink cell grants an uplink grant message to the user terminal of the cluster group call service, the user terminal in the group sending state at the initial time activates the uplink resource indicated by the uplink grant message, and according to the The uplink resource sends the cluster group call service; since the uplink grant message can be the PDCCH signaling that is scrambled by the Group C-RNTI, the user terminal in the group sending state needs to activate the uplink resource.
  • the PDCCH signaling is descrambled using the Group C-RNTI included in the cluster configuration information.
  • the initial moment is specifically a moment when the user terminal of the trunking group call service receives the uplink grant message.
  • the time point at which the uplink resource is activated is the time at which the user terminal in the group receiving state activates the uplink resource at the initial time.
  • the user terminal of the trunking group call service uses the semi-static scheduling mode to perform resource scheduling. Therefore, in the implementation process of the cluster group call service, the evolved cell sends only one uplink grant to the user terminal of the trunking group call service. Message. In the process of implementing the subsequent cluster group call service, the evolved cell receives the cluster group call service data sent by the user terminal in the group sending state according to the semi-persistent scheduling period according to the time point of activating the uplink resource. In this way, the evolved cell does not need to separately and repeatedly send an uplink grant to the user terminal in the group receiving state. The information, in turn, reduces the overhead of the configuration instructions of the evolved cell, and further improves the resource utilization of the evolved cell.
  • step S53 and step S54 After the evolved cell is configured with the uplink grant message and the downlink grant message for the user terminal of the trunking group call service, the evolved cell simultaneously uses the uplink grant message and the downlink grant message. User terminal sent to the cluster group call service. It can be understood that there is no clear sequence of execution of step S53 and step S54.
  • FIG. 1 is a detailed description of a method for implementing a trunking group call service according to an embodiment of the present invention.
  • a device for implementing a cluster group call service by using the foregoing method is described with reference to FIG. 6 to FIG. Carry out a detailed introduction.
  • FIG. 6 is a schematic structural diagram of a first embodiment of an apparatus for implementing a group call service according to the present invention.
  • the apparatus 6 includes:
  • the receiving module 61 is configured to receive cluster configuration information, a downlink grant message, and/or an uplink grant message from the evolved cell.
  • the device for implementing the cluster group call service is any one of the multiple devices.
  • the cluster configuration information received by the receiving module 61 from the evolved cell includes: a semi-persistent scheduling period used to indicate a time interval for receiving or transmitting the cluster group call service data, and a PCI (hysical cell) for uniquely identifying the evolved cell. Identity: physical layer cell identity).
  • the cluster configuration information further includes a group cell radio network temporary identifier Group C-RNTI used by the cluster group scheduling, and some feedback information.
  • the receiving by the receiving module 61, the evolved cell downlink grant message and/or the uplink grant message, where the downlink grant message and/or the uplink grant message are used to indicate the downlink resource and/or uplink. Link resource.
  • the receiving module 61 receives the cluster configuration information from the evolved cell first, and after the device 6 saves the received cluster configuration information, the receiving module 61 receives the downlink grant message from the evolved cell and/or Uplink grant message.
  • the saving module 62 is configured to save the cluster configuration information and the downlink information received by the receiving module 61.
  • the first processing module 63 is configured to share the downlink resource indicated by the downlink grant message in a semi-persistent scheduling manner according to the cluster configuration information saved by the saving module 62 when the group receiving state is in a group receiving state at different times. Receiving cluster group call service data; and/or
  • the device implementing the cluster group call service may be in the group receiving state or may be in the group receiving state. Since the device in the group receiving state does not need to send the cluster group call service data, only the cluster group call service data needs to be passively received. Therefore, when the device is in the group receiving state, the first processing module 63 may receive the cluster group call service data according to the downlink resource indicated by the downlink grant message.
  • the device implementing the cluster group call service may be in the group receiving state or may be in the group receiving state.
  • the first processing module 63 may receive the cluster group call service data according to the downlink resource indicated by the downlink grant message. For example, at time T1, the device 6 is in the group receiving state, and the first processing module 63 receives the cluster group call service data by using the downlink resource F1 indicated by the downlink grant message in a semi-persistent scheduling manner; The device 6 is in the group receiving state, and the first processing module 63 can still receive the cluster group call service data by using the downlink resource F1 indicated by the downlink grant message in a semi-persistent scheduling manner. That is, the device that implements the cluster group call service can receive the cluster group call service by using the downlink resource indicated by the downlink grant message in the semi-persistent scheduling mode as long as it is in the group receiving state. data.
  • the device is any one of the implementation processes of the cluster group call service. Since the devices in the group receiving state can share the downlink resources at the same time in the implementation of the group call service. Therefore, it can be understood that, in the implementation of the cluster group call service, all devices in the group receiving state can share the downlink resources indicated by the downlink grant message.
  • the second processing module 64 is configured to: when the group is in the group sending state at different times, use the uplink resource indicated by the uplink grant message in a semi-persistent scheduling manner according to the cluster configuration information saved by the saving module 62. , Send cluster group call service data.
  • the device 6 implementing the cluster group call service may be in the group sending state or in the group receiving state.
  • the second processing module 64 When the device 6 is in the group transmission state, the second processing module 64 Then, the cluster group call service data is sent by using the uplink resource indicated by the uplink grant message in a semi-persistent scheduling manner.
  • the second processing module 64 can still send the cluster group call service data by using the uplink resource indicated by the uplink grant message in a semi-persistent scheduling manner. It can be understood that the second processing module 64 can receive the cluster group call service data by using the uplink resource indicated by the uplink grant message in a semi-persistent scheduling manner as long as the device 6 is in the group sending state.
  • the device 6 of the cluster group call service is any one of the cluster group call service implementation processes.
  • the group transmission status may not be the same device at different times. Therefore, the uplink resource indicated by the uplink grant message is rotated by the device in the group sending state. in use.
  • the downlink resource indicated by the downlink grant message may be shared in a semi-persistent scheduling manner according to the cluster configuration information, and/or If the device that implements the group call service is in the group sending state at different times, the uplink resource indicated by the uplink grant message may be used in a semi-persistent scheduling manner according to the cluster configuration information.
  • the evolved cell does not need to separately and repeatedly configure the downlink resource and/or the uplink resource for the device that implements the trunking group call service, thereby reducing the evolved cell to configure the downlink for the device in the cluster separately and repeatedly.
  • the overhead of configuration instructions brought by the path resources and/or uplink resources thereby improving the resource utilization of the evolved cells.
  • FIG. 7 is a schematic structural diagram of a second embodiment of an apparatus for implementing a group call service according to the present invention.
  • the difference between this embodiment and the embodiment shown in FIG. 6 is that the apparatus 6 further includes :
  • the determining module 65 is configured to determine whether the cluster configuration information received by the receiving module 61 is sent by an evolved cell to which the receiving module 61 belongs;
  • the reason for determining whether the received cluster configuration information is sent by the evolved cell to which it belongs is that: the device that implements the cluster group call service can only use the downlink information indicated by the cluster configuration information sent by the evolved cell to which it belongs. Road resources and/or uplink resources.
  • the evolved cell to which the device that implements the trunking group call service belongs is that the device is within the coverage area of the evolved cell.
  • the determining module 65 is specifically configured to determine a physical layer cell of the evolved cell to which the cell belongs And determining whether the physical layer cell identifier included in the cluster configuration information matches, and if yes, determining that the cluster configuration information is sent by an evolved cell to which the cluster configuration information belongs.
  • the saving module 62 is specifically configured to: if the determining module 65 determines that the cluster configuration information is sent by the evolved cell to which the clustering configuration information belongs, save the semi-static scheduling configuration information received by the receiving module 61.
  • FIG. 8 is a schematic structural diagram of an embodiment of the first processing module 63 in FIG. 6 of the present invention.
  • the first processing module 63 includes:
  • a first activation unit 631 configured to activate a downlink resource indicated by a downlink grant message received by the receiving module when the initial time is in a group sending state
  • the initial moment refers to the moment when the device implementing the cluster group call service receives the downlink resource from the evolved cell.
  • the downlink grant message sent by the evolved cell is PDCCH signaling scrambled by the Group C-RNTI.
  • the receiving module 61 of the device 6 After the receiving module 61 of the device 6 receives the downlink grant message, the device 6 is currently in a different state, and the operations after receiving the downlink grant message are different.
  • the first activation unit 631 activates the downlink resource indicated by the downlink grant message, and controls the first processing unit 632 to receive the cluster according to the downlink resource.
  • Group call service data since the downlink grant message may be PDCCH signaling that is scrambled using the Group C-RNTI in the cluster configuration information, the first activation unit 631 activates the downlink indicated by the downlink grant message Before the link resource, the Group C-RNTI included in the cluster configuration information received by the receiving module 61 is used to descramble the PDCCH signaling.
  • a first processing unit 632 configured to receive cluster group call service data by using the downlink resource after the first activation unit 631 activates the downlink resource
  • a first recording unit 633 configured to record, when the initial time is in the group sending state, a time point at which the first user terminal activates the downlink resource indicated by the downlink grant message; the first user terminal is a cluster a user terminal in a group receiving state during the group call service implementation process;
  • the device 6 If the device 6 is in the group sending state at the initial moment, it indicates that other devices implementing the cluster group call service are in the group sending state at the initial moment and activate the downlink grant message.
  • the operation of the illustrated downlink resource for example, the first device is in a group receive state, and the operation of activating the downlink resource indicated by the downlink grant message is performed. Therefore, the device needs to record the time point at which the first device activates the downlink resource indicated by the downlink grant message. Since the device belongs to the same cluster as the first device, the device can know the point in time at which the first device activates the downlink resource.
  • the first processing unit 632 is further configured to: when the group is in the group receiving state at different times in the subsequent cluster group call service implementation, according to the semi-static scheduling period and the activation location recorded by the first recording unit 633 The time point of the downlink resource is obtained as a downlink receiving time, and the cluster group call service data is received according to the downlink grant message saved by the saving module.
  • the first processing unit 632 may be configured according to the semi-static scheduling period and the first recording unit 632. Recording the time point of the activation of the downlink resource, obtaining a downlink reception time, and receiving the cluster group call service data according to the saved downlink authorization message. For example, at an initial moment, the device is in a group transmission state, and its first recording unit 632 records the time T2 at which the downlink resource is activated, and after two semi-static periods have elapsed, the device is in a group receiving state. According to the semi-persistent scheduling period T and T2, the downlink receiving time is calculated as 2T+T2, and the cluster group call service data is received according to the downlink resource indicated by the saved downlink grant message. .
  • the device needs to activate the downlink resource before using the downlink resource; if the device is in the group transmitting state at the initial moment, other devices need to be recorded.
  • the device does not need to activate the downlink resource again. That is to say, in the implementation of the entire cluster group call service, the downlink resource only needs to be activated once, and the device can periodically use the downlink resource. In this way, when the device is in the group receiving state at different times, the evolved cell does not need to separately send a downlink grant message for the device, so the overhead of the evolved cell configuration command can be further reduced, and the resource utilization rate of the evolved cell is further improved.
  • the second processing module 64 includes: a second activation unit 641, configured to activate an uplink resource indicated by the uplink grant message when the initial time is in a group sending state;
  • the initial moment refers to the moment when the device that implements the trunking group call service receives the uplink resource from the evolved cell.
  • the uplink grant message sent by the evolved cell is PDCCH signaling scrambled by the Group C-RNTI.
  • the receiving module 61 of the device After the receiving module 61 of the device receives the uplink grant message, the device is currently in a different state, and the operation after receiving the uplink grant message is different.
  • the second activation unit 641 activates the uplink resource indicated by the uplink grant message, and controls the second processing unit 642 to send the cluster group according to the uplink resource.
  • the uplink grant message may be PDCCH signaling descrambled using the Group C-RNTI in the cluster configuration information
  • the second activation unit 641 activates the uplink indicated by the uplink grant message
  • the Group C-RNTI included in the cluster configuration information received by the receiving module 61 is used to descramble the PDCCH signaling.
  • the second processing unit 642 is configured to send the cluster group call service data by using the uplink resource after the second activation unit 641 activates the uplink resource;
  • a second recording unit 643, configured to: when the initial time is in the group receiving state, record a time point at which the second user terminal activates the uplink resource indicated by the uplink grant message, where the second user terminal is a cluster If the device is in the group receiving state at the initial time, the device that implements the group call service at the initial time is in the group sending state and activates the uplink. The operation of the uplink resource indicated by the link grant message. For example, the second device is in a group transmission state and performs an operation of activating an uplink resource indicated by the uplink grant message. Accordingly, the apparatus then needs to record a point in time at which the second device activates the uplink resource indicated by the uplink grant message. Since the device and the second device belong to the same cluster, the device can know the time point at which the second device activates the downlink resource.
  • the second processing unit 642 is further configured to record, according to the semi-persistent scheduling period and the second recording unit 643, when the group is in a group sending state at a different time in the subsequent cluster group call service implementation process.
  • the time point at which the uplink resource is activated is obtained as an uplink transmission time, And sending the cluster group call service data according to the initial uplink resource grant message.
  • the second processing unit 642 may be configured according to the semi-persistent scheduling period and the second recording unit 642.
  • the recorded time point of activating the uplink resource is obtained as an uplink receiving time, and the cluster group call service data is received according to the saved uplink grant message.
  • the device is in a group receiving state, and its second recording unit 642 records the time T2 at which the second device activates the uplink resource, and after two semi-static periods have elapsed, the device is in a group receiving state, which calculates an uplink receiving time of 2T+T4 according to the semi-persistent scheduling period T and T4, and sends a cluster group according to the uplink resource indicated by the saved uplink grant message.
  • T2 time at an initial moment
  • T4 the device is in a group receiving state
  • T4 the device is in a group receiving state, which calculates an uplink receiving time of 2T+T4 according to the semi-persistent scheduling period T and T4, and sends a cluster group according to the uplink resource indicated by the saved uplink grant message.
  • the device needs to activate the uplink resource before using the uplink resource, and if the device is in the group receiving state at the initial time, it is necessary to record other device activation.
  • the point in time at which the uplink resources are described.
  • the device does not need to activate the uplink resource again. That is to say, in the implementation of the entire cluster group call service, the uplink resource only needs to be activated once, and the device can periodically use the uplink resource when in the group transmission state. In this way, when the device is in the group receiving state at different times, the evolved cell does not need to separately send an uplink grant message thereto, so the overhead of the evolved cell configuration command can be further reduced, and the resource utilization rate of the evolved cell is further improved.
  • the device 6 and the first device and the second device may each be a user terminal, such as a device such as a mobile phone.
  • FIG. 10 it is a schematic structural diagram of a third embodiment of an apparatus for implementing a group call service according to the present invention.
  • the apparatus 10 includes:
  • the configuration module 101 is configured to configure, by the evolved cell, cluster configuration information, a downlink grant message, and/or an uplink grant message for the user terminal of the cluster group call service in the evolved cell, where the downlink grant message indicates a downlink resource shared by a user terminal in a group receiving state at different times in a semi-persistent scheduling manner; the uplink grant message indicating an uplink used by a user terminal in a group transmitting state at different times in a semi-persistent scheduling manner Resource
  • the cluster configuration information configured by the configuration module 101 is used to indicate a receiving or sending set. a semi-persistent scheduling period of the group call service data interval, a physical layer cell identifier for uniquely identifying the evolved cell, and a group cell radio network temporary identifier Group C-RNTL used by the cluster group scheduling
  • the sending module 102 is configured to send the cluster configuration information, the downlink grant message, and/or the uplink grant message configured by the configuration module 101 to the user terminal of the cluster group call.
  • the sending module 102 is a user terminal that first sends the cluster configuration information to the cluster group call service, and after the user terminal of the cluster group call service receives the cluster configuration information, and then sends the downlink grant message and/or uplink.
  • the link authorization message is sent to the user terminal.
  • the sending module 102 is configured to send a cluster group call notification message to the user terminal of the cluster group call in the form of a paging message or a new public control message, where the cluster group call notification message carries The cluster configuration information.
  • the sending module 102 sends only one downlink grant message and/or an uplink grant message, the downlink grant message and/or the downlink grant message, in a cluster group call service implementation process.
  • the group cell radio network temporary identifier Group C-RNTI used by the cluster group scheduling included in the cluster configuration information is scrambled.
  • the downlink grant message may be PDCCH signaling scrambled by using a Group C-RNTI.
  • the sending module 102 is further configured to perform the group receiving state according to the semi-persistent scheduling period configured by the configuration module 101 according to the time point of activating the downlink resource in the subsequent cluster group call service implementation process.
  • the user terminal sends the cluster group call service data; the time point of activating the downlink resource is a time when the user terminal in the group receiving state at the initial time activates the downlink resource.
  • the initial time is specifically a time when the device that implements the group call service sends a downlink grant message to the user terminal that sets the group call service.
  • the time point at which the downlink resource is activated is the time at which the user terminal in the group receiving state activates the downlink resource at an initial time.
  • the device Since the device is configured with the downlink resource scheduled by the semi-static scheduling mode, the device only needs to send a downlink authorization to the user terminal of the cluster group call service during the implementation of the cluster group call service. Message.
  • the device is semi-static according to the configuration module 101 according to the time point of activating the downlink resource.
  • the scheduling period sends cluster group call service data to the user terminal in the group receiving state. In this way, the device does not need to separately and repeatedly send the downlink grant message to the user terminals that are in the group receiving state at different times, thereby reducing the overhead of the configuration command of the evolved cell, and further improving the resource utilization rate of the evolved cell.
  • the device 10 further includes:
  • the network side receiving module 103 is configured to receive the user terminal in the group sending state according to the semi-persistent scheduling period configured by the configuration module 101 according to the time point of activating the uplink resource in the subsequent cluster group call service implementation process.
  • the initial time is specifically the time when the device 10 sends an uplink authorization message to the user terminal of the trunking group call service.
  • the time point at which the uplink resource is activated is the time at which the user terminal in the group transmission state activates the uplink resource at the initial time.
  • the device 10 Since the device 10 is configured with an uplink resource scheduled by the semi-static scheduling mode, the device only needs to send an uplink to the user terminal of the cluster group call service during the implementation of the cluster group call service.
  • Authorization message In the subsequent implementation of the cluster call service, the device receives the cluster group call sent by the user terminal in the group sending state according to the semi-persistent scheduling period configured by the configuration module 101 according to the time point of activating the uplink resource.
  • Business data In this way, the device does not need to separately and repeatedly send an uplink grant message to the user terminal that is in the group sending state at different times, thereby reducing the overhead of the configuration command of the evolved cell, and further improving the resource utilization rate of the evolved cell.
  • the downlink resource configured by the device 10 indicates that the downlink resource shared by the semi-persistent scheduling mode when the user terminal of the cluster group call service is in the group receiving state, and/or the configured uplink.
  • the authorization message indicates that there is a downlink resource that is used in a semi-persistent scheduling manner when the user terminal of the cluster group call service is in the group transmission state.
  • the device does not need to separately configure the downlink resources and/or the uplink resources for the user terminals in the cluster, thereby reducing the evolved cell by configuring the downlink for the user terminals in the cluster separately and repeatedly.
  • the overhead of configuration instructions brought by resources and/or uplink resources thereby improving resource utilization of the evolved cell.
  • the device 10 may be a network entity such as a base station.

Landscapes

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

Abstract

本发明实施例公开了一种实现组呼业务的方法及装置，所述方法包括：集群组呼业务的用户终端接收来自演进小区的集群配置信息、下行链路授权消息和/或上行链路授权消息；所述用户终端保存所述集群配置信息、下行链路授权消息和/或上行链路授权消息；若所述用户终端在不同时刻处于组接收状态，根据所述集群配置信息，以半静态调度方式共享所述下行链路授权消息指示的下行链路资源，接收集群组呼业务数据；和/或若所述用户终端在不同时刻处于组发送状态，根据所述集群配置信息，以半静态调度方式轮流使用所述上行链路授权消息指示的上行链路资源，发送集群组呼业务数据。实施本发明实施例，能够减少了演进小区配置指令的开销，提高资源利用率。

Description

一种实现集群组呼业务的方法及装置 本申请要求于 2012 年 01 月 05 日提交中国专利局、 申请号为 201210001585.X、发明名称为 "一种实现集群组呼业务的方法及装置"的中国 专利申请的优先权， 其全部内容通过引用结合在本申请中。 技术领域 本发明涉及集群通信技术领域， 具体而言， 尤其涉及一种实现集群组 呼业务的方法及装置。 背景技术 集群通信技术具有特有的调度、 组呼以及快速呼叫等特性， 因此在专 业通信领域得到了广泛的应用。
集群组呼业务是集群通信技术中提供的最基本业务， 允许用户终端建 立到给定区域内的某一组用户终端的集群呼叫， 其中， 该给定区域称为集 群组呼区域。 在集群组呼业务的实现过程中， 包括两类身份的成员， 即调 度员和签约了集群组呼业务的用户终端。 在一个集群内， 可以没有调度员。 除了调度员以外， 集群内的用户终端均釆用半双工模式进行通信， 在通话 过程中， 同一时刻集群内只有一个用户终端讲话 (处于组发送状态的用户终 端）， 其它用户终端被动接听（处于组接收状态的用户终端）。 集群内的各个 用户终端均可以通过按下 PTT键（push to talk: —键通）抢占话语权， 获 得讲话机会， 只有获得话语权的用户终端松开 PTT键后， 集群内的其他用 户终端才能获得讲话权。
每个集群都有一个唯一组标识号， 用于实现集群组呼业务。 集群内的 任一用户终端都可以发起一个集群的组呼。 集群内的用户终端通过输入该 集群的集群标识号， 然后按下 PTT键， 就可发起该集群的组呼， 实现集群 组呼业务。 在 GSM网络中实现集群组呼业务时， 有两个特殊的工作状态： 组接收状态： 用户终端作为集群组呼业务数据接收者， 小区不会为其 分配专用信道， 用户终端只能收听组呼信息。
组发送状态： 用户终端作为集群组呼业务数据发送者， 小区给用户终 端分配两条专用的上行信道， 用于分别传送移动用户终端发送的数据信息 和控制信息。
随着 LTE系统的发展， 用户有了在 LTE系统内实现集群通信的需求， 如在 LTE系统中实现集群组呼业务等。 但由于 LTE系统中只有分组域， 釆 用共享信道进行分组数据的调度与传输， 因此在 LTE系统中， 演进小区无 法为集群组呼业务分配专用的信道。 因此， 如何在 LTE系统中实现集群组 呼业务成了一个重要的课题。
发明内容 本发明的目的在于提供一种实现集群组呼业务的方法、 系统及一种网 络实体， 能够减少演进小区因单独、 重复地为同一集群内属于该演进小区 且处于组接收状态的多个用户终端配置调度资源所带来的配置指令的开 销， 提高了演进小区的资源利用率。
为了解决上述问题， 本发明釆用了以下技术方案：
一种实现集群组呼业务的方法， 包括：
集群组呼业务的用户终端接收来自演进小区的集群配置信息、 下行链 路授权消息和 /或上行链路授权消息；
所述集群组呼业务的用户终端保存所述集群配置信息、 下行链路授权 消息和 /或上行链路授权消息；
若所述集群组呼业务的用户终端在不同时刻处于组接收状态， 根据所 述集群配置信息， 以半静态调度方式共享所述下行链路授权消息指示的下 行链路资源， 接收集群组呼业务数据； 和 /或
若集群组呼业务的用户终端在不同时刻处于组发送状态， 根据所述集 群配置信息， 以半静态调度方式轮流使用所述上行链路授权消息指示的上 行链路资源， 发送集群组呼业务数据。 本发明还提供了一种实现集群组呼业务的方法， 包括： 演进小区为所述演进小区内集群组呼业务的用户终端配置集群配置信 息、 下行链路授权消息和 /或上行链路授权消息， 所述下行链路授权消息指 示在不同时刻处于组接收状态的用户终端以半静态调度方式共享的下行链 路资源； 所述上行链路授权消息指示在不同时刻处于组发送状态的用户终 端以半静态调度方式轮流使用的上行链路资源；
所述演进小区向所述集群组呼业务的用户终端发送所述集群配置信 息、 下行链路授权消息和 /或上行链路授权消息。
相应地， 本发明还提供了一种实现集群组呼业务的装置， 包括： 接收模块， 用于接收来自演进小区的集群配置信息、 下行链路授权消 息和 /或上行链路授权消息；
保存模块， 用于保存所述接收模块接收的集群配置信息、 下行链路授 权消息和 /或上行链路授权消息；
第一处理模块， 用于当在不同时刻处于组接收状态时， 根据所述保存 模块保存的集群配置信息， 以半静态调度方式共享所述下行链路授权消息 指示的下行链路资源， 接收集群组呼业务数据； 和 /或
第二处理模块， 用于当在不同时刻处于组发送状态时， 根据所述保存 模块保存的集群配置信息， 以半静态调度方式轮流使用所述上行链路授权 消息指示的上行链路资源， 发送集群组呼业务数据。
相应地， 本发明还提供了一种实现集群组呼业务的装置， 包括： 配置模块， 用于演进小区为所述演进小区内集群组呼业务的用户终端 配置集群配置信息、 下行链路授权消息和 /或上行链路授权消息， 所述下行 链路授权消息指示在不同时刻处于组接收状态的用户终端以半静态调度方 式共享的下行链路资源； 所述上行链路授权消息指示在不同时刻处于组发 送状态的用户终端以半静态调度方式轮流使用的上行链路资源；
发送模块， 用于向集群组呼的用户终端发送所述配置模块配置的集群 配置信息、 下行链路授权消息和 /或上行链路授权消息。
本发明的有益效果是： 在实现集群组呼业务时， 若集群组呼业务的用 户终端在不同时刻处于组接收状态， 则可以根据集群配置信息， 以半静态 调度方式共享下行链路授权消息指示的下行链路资源， 和 /或若集群组呼业 务的用户终端在不同时刻处于组发送状态， 则可以根据集群配置信息， 以 半静态调度方式轮流使用上行链路授权消息指示的上行链路资源。 如此， 演进小区则不用单独、 重复地为该集群内的用户终端配置下行链路资源和 / 或上行链路资源， 从而减少了演进小区因单独、 重复地为集群内的用户终 端配置下行链路资源和 /或上行链路资源所带来的配置指令的开销， 进而提 高了演进小区的资源利用率。
附图说明 为了更清楚地说明本发明实施例或现有技术中的技术方案， 下面将对 实施例或现有技术描述中所需要使用的附图作简单地介绍， 显而易见地， 下面描述中的附图仅仅是本发明的一些实施例， 对于本领域普通技术人员 来讲， 在不付出创造性劳动的前提下， 还可以根据这些附图获得其它的附 图。
图 1 是本发明提供的一种实现集群组呼业务方法的第一实施例的流程 示意图；
图 2是本发明提供的一种实现集群组呼业务方法的第二实施例的流程 示意图；
图 3是本发明提供的一种实现集群组呼业务方法的第三实施例的流程 示意图；
图 4是本发明提供的一种实现集群组呼业务方法的第四实施例的流程 示意图；
图 5 是本发明提供的一种实现集群组呼业务方法的第五实施例的流程 示意图；
图 6是本发明提供的一种实现集群组呼业务的装置的第一实施例的结 构示意图；
图 7是本发明提供的一种实现集群组呼业务的装置的第二实施例的结 构示意图； 图 8是本发明图 6中第一处理模块的实施例的结构示意图；
图 9是本发明图 6中第二处理模块的实施例的结构示意图；
图 10是本发明提供的一种实现集群组呼业务的装置的第三实施例的结 构示意图。 具体实施方式 下面将结合本发明实施例中的附图， 对本发明实施例中的技术方案进 行清楚、 完整地描述， 显然， 所描述的实施例仅仅是本发明的一部分实施 例， 而不是全部的实施例。 基于本发明中的实施例， 本领域普通技术人员 在没有作出创造性劳动前提下所获得的所有其它实施例， 都属于本发明保 护的范围。
随着集群通信技术的发展， 用户希望能够在 LTE系统中实现集群组呼 业务。 但由于现有 LTE 系统无法像在 GSM 网络一样， 专门为 UE(User Equipment: 用户终端）分配专用的信道来发送集群组呼业务数据， 而如果 直接釆用 1对 1的全双工模式来实现集群组呼业务又使得资源利用率不高。 为此， 本发明公开了一种实现集群组呼业务的方法及装置。
在此部分， 首先对本发明中各个实施例均涉及的一些基本概念进行说 明。
半静态调度方式， 具体是指在 LTE的调度资源传输过程中， 用户终端 每隔固定的周期在相同的时频资源位置上进行业务数据的发送或接收， 如 此演进小区则不用再为该用户终端重新配置调度资源。 也就是说， 使用半 静态调度方式时， 可以充分利用话音数据包周期性到达用户终端的特点， 对同一个用户终端所需的调度资源， 只需要配置一次、 激活一次， 便可周 期使用。
集群组呼业务， 是属于数据包大小比较固定， 且数据包到达用户终端 满足一定周期性的业务。 根据集群组呼业务的特性， 即在不考虑调度员的 情况下， 集群内的用户终端都釆用半双工模式进行通信， 同一时刻只有一 个用户终端占用话语权（处于组发送状态的用户终端占用话语权）， 多个用 户终端在同一时刻没有话语权 (处于组接收状态的用户终端没有话语权)。 下面，请参考图 1 , 是本发明提供的实现集群组呼业务方法的第一实施 例的流程图， 包括：
步骤 S11 , 集群组呼业务的用户终端接收来自演进小区的集群配置信 息、 下行链路授权消息和 /或上行链路授权消息；
其中， 在集群组呼业务的实现过程中， 会涉及到多个用户终端。 在同 一时刻， 该多个用户终端中有一个用户终端处于组发送状态， 其余的用户 终端均处于组接收状态。 在本发明实施例中， 所述集群组呼业务的用户终 端为所述多个用户终端中的任一用户终端。
接收到的来自演进小区的集群配置信息包括： 用于指示接收或发送集 群组呼业务数据时间间隔的半静态调度周期和用于唯一标识所述演进小区 的 PCI ( physical cell identity: 物理层小区标识）。 当然， 集群配置信息还包 括集群组调度使用的组小区无线网络临时标识 Group C-RNTI以及一些反馈 信息等。
接收到的来自演进小区下行链路授权消息和 /或上行链路授权消息， 该 下行链路授权消息和 /或上行链路授权消息用于对应指示下行链路资源和 / 或上行链路资源。
一般地， 集群组呼业务的用户终端是先接收到来自演进小区的集群配 置信息， 在保存了接收到的集群配置信息之后， 才会接收到来自演进小区 的下行链路授权消息和 /或上行链路授权消息。
步骤 S12, 所述集群组呼业务的用户终端保存所述集群配置信息、下行 链路授权消息和 /或上行链路授权消息；
步骤 S13 , 若集群组呼业务的用户终端在不同时刻处于组接收状态，根 据所述集群配置信息， 以半静态调度方式共享所述下行链路授权消息指示 的下行链路资源， 接收集群组呼业务数据；
在同一时刻， 集群组呼业务的用户终端有可能处于组接收状态， 也有 可能处于组接收状态。 由于处于组接收状态的用户终端不需要发送集群组 呼业务数据， 只需要被动的接收集群组呼业务数据。 因此， 当所述集群组 呼业务的用户终端处于组接收状态时， 该处于组接收状态的用户终端则可 以根据所述下行链路授权消息指示的下行链路资源， 接收集群组呼业务数 据；
在不同时刻， 所述集群组呼业务的用户终端有可能处于组发送状态， 也有可能处于组接收状态； 在不同时刻， 当所述集群组呼业务的用户终端 处于组接收状态时， 该处于组接收状态的用户终端则可以根据下行链路授 权消息指示的下行链路资源， 接收集群组呼业务数据。 例如， 在 T1时刻， 所述集群组呼业务的用户终端处于组接收状态， 其则以半静态调度方式使 用下行链路授权消息指示的下行链路资源 F1 , 接收集群组呼业务数据； 在 T3时刻， 所述集群组呼业务的用户终端又处于组接收状态， 其则仍然可以 以半静态调度方式使用下行链路授权消息指示的下行链路资源 F1 , 接收集 群组呼业务数据。 也就是说， 集群组呼业务的用户终端只要处于组接收状 态， 其均可以以半静态调度方式使用下行链路授权消息指示的下行链路资 源， 接收集群组呼业务数据。
其中， 由于所述集群组呼业务的用户终端为集群组呼业务实现过程中 的任一用户终端。 由于在集群组呼业务的实现过程中， 在同一时刻， 处于 组接收状态的用户终端可以共享下行链路资源。 因此可以这样理解， 在集 群组呼业务的实现过程中， 所有处于组接收状态的用户终端均可以共享下 行链路授权消息指示的下行链路资源。
步骤 S14, 若集群组呼业务的用户终端在不同时刻处于组发送状态，根 据所述集群配置信息， 以半静态调度方式轮流使用上行链路资源， 发送集 群组呼业务数据。
在同一时刻， 集群组呼业务的用户终端有可能处于组发送状态， 也有 可能处于组接收状态。 当所述集群组呼业务的用户终端处于组发送状态时， 该处于组发送状态的用户终端则以半静态调度方式使用上行链路授权消息 指示的上行链路资源， 发送集群组呼业务数据。 在另一时刻， 若所述群组 呼业务的用户终端又处于组发送状态， 其仍可以半静态调度方式使用所述 上行链路授权消息指示的上行链路资源发送集群组呼业务数据。 可以这样 理解， 集群组呼业务的用户终端只要处于组发送状态， 其均可以以半静态 调度方式使用上行链路授权消息指示的上行链路资源， 接收集群组呼业务 数据。
其中， 由于所述集群组呼业务的用户终端为集群组呼业务实现过程中 的任一用户终端。 而在集群组呼业务的实现过程中， 由于在不同时刻， 处 于组发送状态的可能不是同一用户终端， 因此， 所述上行链路授权消息指 示的上行链路资源是由处于组发送状态的用户终端轮流使用的。
另外， 需要说明的是， 在具体实施时， 既可以执行步骤 S13 , 又执行步 骤 S14; 或者只执行步骤 S13或步骤 S14。 并且， 步骤 S13与步骤 S14的执 行没有明确的先后顺序。
本实施例中， 若集群组呼业务的用户终端在不同时刻处于组接收状态， 则可以根据集群配置信息， 以半静态调度方式共享下行链路授权消息指示 的下行链路资源， 和 /或若集群组呼业务的用户终端在不同时刻处于组发送 状态， 则可以根据集群配置信息， 以半静态调度方式轮流使用上行链路授 权消息指示的上行链路资源。 如此， 演进小区则不用单独、 重复地为集群 内的用户终端配置下行链路资源和 /或上行链路资源， 从而减少了演进小区 因单独、 重复地为集群内的用户终端配置下行链路资源和 /或上行链路资源 所带来的配置指令的开销， 进而提高了演进小区的资源利用率。
请参考图 2 ,是本发明提供的一种实现集群组呼业务的装置的第二实施 例的流程示意图， 所述方法包括：
步骤 S21 , 集群组呼业务的用户终端接收来自演进小区的集群配置信 息；
步骤 S22,所述集群组呼业务的用户终端判断所述集群配置信息是否由 其所属的演进小区发送；
其中， 集群组呼业务的用户终端需要判断其接收到的集群配置信息是 否是其所属的演进小区发出来的原因是： 集群组呼业务的用户终端只能使 用其所属的演进小区发来的集群配置信息指示的下行链路资源和 /或上行链 路资源。
本步骤具体实现中， 可釆用下述方式判断所述集群配置信息是否由其 所属的演进小区发送：
具体实现中， 所述集群组呼业务的用户终端判断所述集群配置信息是 否由其所属的演进小区发送， 包括：
集群组呼业务的用户终端判断接收到的集群配置信息包括的物理层小 区标识 PCI与其所属演进小区的物理层小区标识 PCI是否匹配， 若匹配， 则判断该集群配置信息是其所属的演进小区发出的。
步骤 S23, 所述集群组呼业务的用户终端保存所述集群配置信息； 步骤 S24, 所述集群组呼业务的用户终端接收来自演进小区的下行链 路授权消息和 /或上行链路授权消息；
步骤 S25 ,所述集群组呼业务的用户终端保存所述下行链路授权消息和 /或上行链路授权消息；
步骤 S26, 若集群组呼业务的用户终端在不同时刻处于组接收状态，根 据所述集群配置信息， 以半静态调度方式共享所述下行链路授权消息指示 的下行链路资源， 接收集群组呼业务数据；
步骤 S27 , 若集群组呼业务的用户终端在不同时刻处于组发送状态，根 据所述集群配置信息， 以半静态调度方式轮流使用所述上行链路授权消息 指示的上行链路资源， 发送集群组呼业务数据。
其中， 步骤 S25-步骤 S27的操作与图 1所示的实施例中步骤 S12-步骤 S14的操作相同， 在此不重复赘述。
请参考图 3 ,是本发明提供的一种实现集群组呼业务的方法的第三实施 例的流程示意图， 所述方法包括：
步骤 S31 , 集群组呼业务的用户终端接收来自演进小区的集群配置信 息、 下行链路授权消息和 /或上行链路授权消息；
步骤 S32, 所述集群组呼业务的用户终端保存所述集群配置信息、下行 链路授权消息和 /或上行链路授权消息；
步骤 S31-步骤 S32的操作与图 1所示的实施例中步骤 S11-步骤 S22的 操作相同， 在此不重复描述。 可以理解的是， 在保存所述集群配置信息之 前， 还可以包括集群组呼业务的用户终端判断其接收到的集群配置信息是 否由其所属的演进小区发送的操作。
步骤 S33 , 若集群组呼业务的用户终端在初始时刻处于组接收状态， 则 激活所述下行链路授权消息指示的下行链路资源， 并根据所述下行链路资 源接收集群组呼业务数据；
其中， 初始时刻， 指的是集群组呼业务的用户终端接收到来自演进小 区的下行链路资源的时刻。
具体地，演进小区发送的下行链路授权消息为使用 Group C-RNTI加扰 的物理下行控制信道 PDCCH信令。在接收到下行链路授权消息之后， 集群 组呼业务的用户终端所处的状态不同， 其接收到下行链路授权消息之后的 操作也不同。
在初始时刻， 若集群组呼业务的用户终端处于组接收状态， 则激活所 述下行链路授权消息指示的下行链路资源， 并根据所述下行链路资源接收 集群组呼业务数据； 由于下行链路授权消息可以是使用集群配置信息中的
Group C-RNTI去加扰的 PDCCH信令， 因此， 处于组接收状态的用户终端 在激活所述下行链路授权消息指示的下行链路资源之前， 还需要使用集群 配置信息包括的 Group C-RNTI去解扰该 PDCCH信令。
在初始时刻， 若集群组呼业务的用户终端处于组发送状态， 则进入步 骤 S35。
步骤 S34, 若集群组呼业务的用户终端在初始时刻处于组发送状态， 则 记录第一用户终端激活所述下行链路授权消息指示的下行链路资源的时间 点； 所述第一用户终端为集群组呼业务实现过程中处于组接收状态的用户 终端；
若所述集群组呼业务的用户终端在初始时刻处于组发送状态， 则说明 集群组呼业务的其它用户终端在初始时刻处于组发送状态并进行了激活所 述下行链路授权消息指示的下行链路资源的操作， 例如， 第一用户终端处 于组接收状态， 并进行了激活所述下行链路授权消息指示的下行链路资源 的操作。 因此， 所述集群组呼业务的用户终端则需要记录所述第一用户终 端激活所述下行链路授权消息指示的下行链路资源的时间点。 由于所述集 群组呼业务的用户终端与所述第一用户终端属于同一集群， 所以所述集群 组呼业务的用户终端能够知道所述第一用户终端激活所述下行链路资源的 时间点。
其中， 需要说明的是， 在后续集群组呼业务实现过程中， 当所述集群 组呼业务的用户终端在不同时刻处于组接收状态时， 根据所述半静态调度 周期和记录的所述激活下行链路资源的时间点， 得到下行链路接收时刻， 并根据保存的所述下行链路授权消息接收集群组呼业务数据。 例如， 在初 始时刻， 所述集群组呼业务的用户终端处于组发送状态， 其记录了激活所 述下行链路资源的时间 T2,若经过了两个半静态周期之后， 所述集群组呼业 务的用户终端处于组接收状态， 其根据所述半静态调度周期 T以及 T2, 计 算得到其下行链路接收时刻为 2T+ T2, 并根据保存的所述下行链路授权消 息指示的下行链路资源， 接收集群组呼业务数据。
可以这样理解， 若所述集群组呼业务的用户终端在初始时刻处于组接 收状态， 那么在使用该下行链路资源之前， 所述集群组呼业务的用户终端 需要激活该下行链路资源； 若所述集群组呼业务的用户终端在初始时刻处 于组接收状态， 则需要记录其它用户终端激活所述下行链路资源的时间点。 而在后续的集群组呼业务的实现中， 若所述集群组呼业务的用户终端处于 组接收状态， 则不需要再激活该下行链路资源。 也就是说在， 在整个集群 组呼业务的实现中， 下行链路资源只需要激活一次， 若所述集群组呼业务 的用户终端处于组接收状态便可周期性地使用该下行链路资源。 如此， 集 群组呼业务的用户终端在不同时刻处于组接收状态时， 演进小区则不用为 该用户终端分别发送下行链路授权消息， 因此能够进一步减少演进小区配 置指令的开销， 进一步提高了演进小区的资源利用率。
其中， 步骤 S33-步骤 S34的操作相当于图 1所示的实施例中步骤 S13 的操作。
步骤 S35, 若集群组呼业务的用户终端在初始时刻处于组发送状态， 则 激活所述上行链路授权消息指示的上行链路资源， 并根据所述上行链路资 源， 发送集群组呼业务数据；
其中， 初始时刻， 指的是集群组呼业务的用户终端接收到来自演进小 区的上行链路资源的时刻。
具体地， 演进小区发送的上行链路授权消息可以为使用 Group C-RNTI 加扰的 PDCCH信令。在接收到上行链路授权消息之后， 集群组呼业务的用 户终端所处的状态不同， 其接收到上行链路授权消息之后的操作也不同。 在初始时刻， 若集群组呼业务的用户终端处于组发送状态时， 则激活 所述上行链路授权消息指示的上行链路资源， 并根据所述上行链路资源发 送集群组呼业务数据； 由于上行链路授权消息为使用 Group C-RNTI加扰的 PDCCH信令， 因此， 处于组接收状态的用户终端在激活所述上行链路授权 消息指示的上行链路资源之前， 还需要使用集群配置信息包括的 Group C-RNTI去解扰该 PDCCH信令。
在初始时刻， 若集群组呼业务的用户终端处于组发送状态时， 则进入 步骤 S36。
步骤 S36, 若所述集群组呼业务的用户终端在初始时刻处于组接收状 态， 则记录第二用户终端激活所述上行链路授权消息指示的上行链路资源 的时间点， 所述第二用户终端为集群组呼业务实现过程中处于组发送状态 的用户终端；
若所述集群组呼业务的用户终端在初始时刻处于组接收状态， 则说明 集群组呼业务的其它用户终端在初始时刻处于组接收状态并进行了激活所 述上行链路授权消息指示的上行链路资源的操作， 例如， 第二用户终端处 于组发送状态， 并进行了激活所述上行链路授权消息指示的上行链路资源 的操作。 因此， 所述集群组呼业务的用户终端则需要记录所述第二用户终 端激活所述上行链路授权消息指示的上行链路资源的时间点。 由于所述集 群组呼业务的用户终端与所述第二用户终端属于同一集群， 所以所述集群 组呼业务的用户终端能够知道所述第二用户终端激活所述上行链路资源的 时间点。
其中， 需要说明的是， 在后续集群组呼业务实现过程中， 当所述集群 组呼业务的用户终端在不同时刻处于组发送状态， 则根据所述半静态调度 周期和记录的所述激活上行链路资源的时间点， 得到上行链路发送时刻， 并根据所述下行链路配置信息指示送集群组呼业务数据。 例如， 在初始时 刻， 所述集群组呼业务的用户终端处于组接收状态， 其记录了激活所述上 行链路资源的时间点 T4,若经过了两个半静态周期之后，所述集群组呼业务 的用户终端处于组发送状态， 其根据所述半静态调度周期 T以及 T4, 计算 得到其上行链路发送时刻为 2T+ T4, 并根据保存的所述上行链路授权消息 指示的上行链路资源， 发送集群组呼业务数据。
可以这样理解， 若集群组呼业务的用户终端在初始时刻处于组发送状 态， 那么在使用该上行链路资源之前， 该集群组呼业务的用户终端需要激 活该上行链路资源； 若集群组呼业务的用户终端在初始时刻处于组发送状 态， 则需要记录其它用户终端激活所述上行链路资源的时间点。 而在后续 的集群组呼业务的实现中， 若集群组呼业务的用户终端处于组发送状态， 则不需要再激活该上行链路资源。 也就是说在， 在整个集群组呼业务的实 现中， 上行链路资源只需要激活一次， 若集群组呼业务的用户终端在处于 组发送状态时便可周期性地使用该上行链路资源， 发送集群组呼业务数据。 如此， 集群组呼业务的用户终端在不同时刻处于组发送状态时， 演进小区 则不用为其分别发送上行链路授权消息， 因此能够进一步减少演进小区配 置指令的开销， 进一步提高了演进小区的资源利用率。
其中， 步骤 S35-步骤 S36的操作相当于图 1所示的实施例中步骤 S13 的操作。
请参考图 4 ,是本发明提供的一种实现集群组呼业务方法的第四实施例 的流程示意图， 所述方法包括：
步骤 S41 ,演进小区为所述演进小区内集群组呼业务的用户终端配置集 群配置信息， 下行链路授权消息和 /或上行链路授权消息； 所述下行链路授 权消息指示在不同时刻处于组接收状态的用户终端以半静态调度方式共享 的下行链路资源； 所述上行链路授权消息指示在不同时刻处于组发送状态 的用户终端以半静态调度方式轮流使用的上行链路资源；
其中， 演进小区配置的集群配置信息包括用于指示接收或发送集群组 呼业务数据时间间隔的半静态调度周期、 用于唯一标识所述演进小区的物 理层小区标识、 以及集群组调度使用的组小区无线网络临时标识 Group C-RNTL
步骤 S42,所述演进小区向所述集群组呼业务的用户终端发送所述集群 配置信息、 下行链路授权消息和 /或上行链路授权消息。
一般地， 演进小区是先发送集群配置信息给集群组呼业务的用户终端， 在集群组呼业务的用户终端接收了集群配置信息之后， 然后再发送下行链 路授权消息和 /或上行链路授权消息给用户终端。
具体地， 演进小区发送集群配置消息给集群组呼业务的用户终端时， 以寻呼消息形式或新的公共控制消息形式向所述集群组呼业务的用户终端 发送集群组呼通知消息， 所述集群组呼通知消息中携带有所述集群配置信 息。
例如， 若演进小区 cell A将集群组呼通知消息以寻呼消息形式发送出 去， 那么该集群组呼通知消息则变成了一个寻呼消息， 该寻呼消息中携带 有集群配置信息。 该寻呼消息釆用寻呼无线网络临时标识 P-RNTI 进行加 扰。对于集群组呼业务的所有用户终端来说，其 P-RNTI都是相同的。 因此， 集群组呼业务的用户终端能够接收并保存该集群配置信息。
当然， 集群组呼通知消息也可以是重新定义的一个新的公共控制消息。 例如， cell A定义了一个新的公共控制消息， 在该新公共控制消息中包括集 群配置信息， cell A将该新的公共控制消息发送出去。 其中， 该新公共控制 消息可以使用其它公共的无线网络临时标识 RNTI进行加扰。集群组呼业务 的所有用户终端拥有该相同的 RNTI, 因此集群组呼业务的用户终端都能够 接收并保存该集群配置信息。
本实施例中， 由于演进小区配置的下行链路资源指示有当集群组呼业务 的用户终端处于组接收状态时以半静态调度方式共享的下行链路资源， 和 / 或配置的上行链路授权消息指示有当集群组呼业务的用户终端处于组发送 状态时以半静态调度方式轮流使用的上行链路资源。 如此， 演进小区则不 用单独、 重复地为该集群内的用户终端配置下行链路资源和 /或上行链路资 源， 从而减少了演进小区因单独、 重复地为集群内的用户终端配置下行链 路资源和 /或上行链路资源所带来的配置指令的开销， 进而提高了演进小区 的资源利用率。
请参考图 5 ,是本发明提供的一种实现集群组呼业务方法的第五实施例 的流程示意图， 所述方法包括：
步骤 S51 ,演进小区为所述演进小区内集群组呼业务的用户终端配置集 群配置信息、 下行链路授权消息和 /或上行链路授权消息， 所述下行链路授 权消息指示在不同时刻处于组接收状态的用户终端以半静态调度方式共享 的下行链路资源； 所述上行链路授权消息指示在不同时刻处于组发送状态 的用户终端以半静态调度方式轮流使用的上行链路资源；
步骤 S52,所述演进小区向所述集群组呼业务的用户终端发送所述集群 配置信息、 下行链路授权消息和 /或上行链路授权消息；
其中， 步骤 S51-步骤 S52的操作与图 4所示的实施例中步骤 S41-步骤 S42的操作相同， 在此不重复描述。
步骤 S53 ,在后续集群组呼业务实现过程中， 所述演进小区根据激活下 行链路资源的时间点， 按照所述半静态调度周期向处于组接收状态的用户 终端发送集群组呼业务数据；
其中， 所述激活下行链路资源的时间点是在初始时刻处于组接收状态 的用户终端激活所述下行链路资源的时间； 在一次集群组呼业务实现过程 中， 所述演进小区只发送一次下行链路授权消息， 所述下行链路授权消息 使用所述集群配置信息中集群组调度使用的组小区无线网络临时标识 Group C-RNTI进行加扰。
具体地， 所述下行链路授权消息可以为使用 Group C-RNTI 加扰的 PDCCH信令。
演进小区在向集群组呼业务的用户终端发送下行链路授权消息后， 在 初始时刻处于组接收状态的用户终端则激活所述下行链路授权消息指示的 下行链路资源， 并根据所述下行链路资源接收集群组呼业务； 由于下行链 路授权消息可以为使用 Group C-RNTI加扰的 PDCCH信令， 因此， 处于组 接收状态的用户终端在激活下行链路资源之前， 还需要使用集群配置信息 包括的 Group C-RNTI来解扰该 PDCCH信令。
其中， 初始时刻具体为集群组呼业务的用户终端接收到下行链路授权 消息的时刻。 激活下行链路资源的时间点则为在初始时刻， 处于组接收状 态的用户终端激活所述下行链路资源的时间。
由于集群组呼业务的用户终端釆用半静态调度方式进行资源调度， 所 以在一次集群组呼业务的实现过程中， 演进小区只向集群组呼业务的用户 终端发送一次下行链路授权消息。 在后续集群组呼业务实现过程中， 所述 演进小区则根据激活下行链路资源的时间点， 按照所述半静态调度周期向 处于组接收状态的用户终端发送集群组呼业务数据。 如此， 演进小区不用 单独、 重复地向处于组接收状态的用户终端分别发送下行链路授权消息， 进而减少了演进小区的配置指令的开销， 进一步提高了演进小区的资源利 用率。
步骤 S54,在后续集群组呼业务实现过程中， 所述演进小区根据激活上 行链路资源的时间点， 按照所述半静态调度周期接收处于组发送状态的用 户终端发送的集群组呼业务数据；
其中， 所述激活上行链路资源的时间点是在初始时刻处于组发送状态 的用户终端激活所述上行链路资源的时间； 在一次集群组呼业务实现过程 中， 所述演进小区只发送一次上行链路授权消息， 所述上行链路授权消息 使用所述集群配置信息中集群组调度使用的组小区无线网络临时标识 Group C-RNTI进行加扰。
具体地， 所述上行链路授权消息可以为使用 Group C-RNTI 加扰的 PDCCH信令。
演进小区在向集群组呼业务的用户终端发送上行链路授权消息后， 在 初始时刻处于组发送状态的用户终端则激活所述上行链路授权消息指示的 上行链路资源， 并根据所述上行链路资源发送集群组呼业务； 由于上行链 路授权消息可以为使用 Group C-RNTI加扰的 PDCCH信令， 因此， 处于组 发送状态的用户终端在激活上行链路资源之前， 还需要使用集群配置信息 包括的 Group C-RNTI来解扰该 PDCCH信令。
其中， 初始时刻具体为集群组呼业务的用户终端接收到上行链路授权 消息的时刻。 激活上行链路资源的时间点则为在初始时刻， 处于组接收状 态的用户终端激活所述上行链路资源的时间。
由于集群组呼业务的用户终端釆用半静态调度方式进行资源调度， 所 以在一次集群组呼业务的实现过程中， 演进小区只向集群组呼业务的用户 终端发送一次上行链路授权消息。 在后续集群组呼业务实现过程中， 所述 演进小区则根据激活上行链路资源的时间点， 按照所述半静态调度周期接 收处于组发送状态的用户终端发送的集群组呼业务数据。 如此， 演进小区 不用单独、 重复地向处于组接收状态的用户终端分别发送上行链路授权消 息， 进而减少了演进小区的配置指令的开销， 进一步提高了演进小区的资 源利用率。
其中， 需要说明的是， 当演进小区为集群组呼业务的用户终端同时配 置了上行链路授权消息和下行链路授权消息之后， 演进小区同时将上行链 路授权消息和下行链路授权消息发送给集群组呼业务的用户终端。 可以这 样理解， 步骤 S53与步骤 S54的执行没有明确的先后顺序。
图 1-图 5对本发明实施例公开的实现集群组呼业务的方法进行了详细 的介绍， 下面， 结合附图 6-图 10, 对釆用了上述方法来实现集群组呼业务 的装置进行详细介绍。
请参考图 6,是本发明提供的一种实现集群组呼业务的装置的第一实施 例的结构示意图， 所述装置 6包括：
接收模块 61 , 用于接收来自演进小区的集群配置信息、 下行链路授权 消息和 /或上行链路授权消息；
其中， 在集群组呼业务的实现过程中， 会涉及到多个装置。 在同一时 刻， 该多个装置中有一个装置处于组发送状态， 其余的装置均处于组接收 状态。 在本发明实施例中， 所述实现集群组呼业务的装置为所述多个装置 中的任一个。
其中， 接收模块 61接收到的来自演进小区的集群配置信息包括： 用于 指示接收或发送集群组呼业务数据时间间隔的半静态调度周期和用于唯一 标识所述演进小区的 PCI ( hysical cell identity: 物理层小区标识）。 当然， 集群配置信息还包括集群组调度使用的组小区无线网络临时标识 Group C-RNTI以及一些反馈信息等。
其中，接收模块 61接收到的来自演进小区下行链路授权消息和 /或上行 链路授权消息， 该下行链路授权消息和 /或上行链路授权消息用于对应指示 下行链路资源和 /上行链路资源。
一般地， 接收模块 61是先接收到来自演进小区的集群配置信息， 在装 置 6保存了接收到的集群配置信息之后， 接收模块 61才会接收到来自演进 小区的下行链路授权消息和 /或上行链路授权消息。
保存模块 62, 用于保存所述接收模块 61接收的集群配置信息、 下行链 路授权消息和 /或上行链路授权消息；
第一处理模块 63 , 用于当在不同时刻处于组接收状态时， 根据所述保 存模块 62保存的集群配置信息， 以半静态调度方式共享所述下行链路授权 消息指示的下行链路资源， 接收集群组呼业务数据； 和 /或
在同一时刻， 该实现集群组呼业务的装置有可能处于组接收状态， 也 有可能处于组接收状态。 由于处于组接收状态的该装置不需要发送集群组 呼业务数据， 只需要被动的接收集群组呼业务数据。 因此， 当该装置处于 组接收状态时， 第一处理模块 63则可以根据所述下行链路授权消息指示的 下行链路资源， 接收集群组呼业务数据；
在不同时刻， 该实现集群组呼业务的装置有可能处于组接收状态， 也 有可能处于组接收状态。 在不同时刻， 当该装置处于组接收状态时， 第一 处理模块 63可以根据下行链路授权消息指示的下行链路资源， 接收集群组 呼业务数据。 例如， 在 T1时刻， 该装置 6处于组接收状态， 第一处理模块 63则以半静态调度方式使用下行链路授权消息指示的下行链路资源 F1 ,接 收集群组呼业务数据； 在 T3时刻， 该装置 6又处于组接收状态， 第一处理 模块 63则仍然可以以半静态调度方式使用下行链路授权消息指示的下行链 路资源 F1 , 接收集群组呼业务数据。 也就是说， 实现集群组呼业务的装置 只要处于组接收状态， 第一处理模块 63则均可以以半静态调度方式使用下 行链路授权消息指示的下行链路资源， 接收集群组呼业务数据。
其中， 由于所述装置为集群组呼业务实现过程中的任一个。 由于在集 群组呼业务的实现过程中， 在同一时刻， 处于组接收状态的装置可以共享 下行链路资源。 因此可以这样理解， 在集群组呼业务的实现过程中， 所有 处于组接收状态的装置均可以共享该下行链路授权消息指示的下行链路资 源。
第二处理模块 64 , 用于当在不同时刻处于组发送状态时， 根据所述保 存模块 62保存的集群配置信息， 以半静态调度方式轮流使用所述上行链路 授权消息指示的上行链路资源， 发送集群组呼业务数据。
在同一时刻， 实现集群组呼业务的装置 6有可能处于组发送状态， 也 有可能处于组接收状态。 当该装置 6处于组发送状态时， 第二处理模块 64 则以半静态调度方式使用上行链路授权消息指示的上行链路资源， 发送集 群组呼业务数据。 在另一时刻， 若该装置 6处于组发送状态， 第二处理模 块 64则仍可以半静态调度方式使用所述上行链路授权消息指示的上行链路 资源发送集群组呼业务数据。 可以这样理解， 该装置 6 只要处于组发送状 态， 第二处理模块 64均可以以半静态调度方式使用上行链路授权消息指示 的上行链路资源， 接收集群组呼业务数据。
其中， 由于所述集群组呼业务的装置 6 为集群组呼业务实现过程中的 任一个。 而在集群组呼业务的实现过程中， 在不同时刻， 处于组发送状态 的可能不是同一装置， 因此， 所述上行链路授权消息指示的上行链路资源 是由处于组发送状态的装置轮流使用的。
本实施例中， 若实现集群组呼业务的装置在不同时刻处于组接收状态， 则可以根据集群配置信息， 以半静态调度方式共享下行链路授权消息指示 的下行链路资源， 和 /或若实现集群组呼业务的装置在不同时刻处于组发送 状态， 则可以根据集群配置信息， 以半静态调度方式轮流使用上行链路授 权消息指示的上行链路资源。 如此， 演进小区则不用单独、 重复地该实现 集群组呼业务的装置配置下行链路资源和 /或上行链路资源， 从而减少了演 进小区因单独、 重复地为集群内的装置配置下行链路资源和 /或上行链路资 源所带来的配置指令的开销， 进而提高了演进小区的资源利用率。
请参考图 7 ,是本发明提供的一种实现集群组呼业务的装置的第二实施 例的结构示意图， 本实施例与图 6 所示的实施例的区别在于， 所述装置 6 还包括：
判断模块 65 ,用于判断所述接收模块 61接收的集群配置信息是否由其 所属的演进小区发送；
其中， 需要判断其接收到的集群配置信息是否是其所属的演进小区发 出来的原因是： 实现集群组呼业务的装置只能使用其所属的演进小区发来 的集群配置信息指示的下行链路资源和 /或上行链路资源。 其中， 实现集群 组呼业务的装置所属的演进小区， 指的是该装置在演进小区的覆盖区域之 内。
具体是， 所述判断模块 65具体用于判断其所属演进小区的物理层小区 标识与所述集群配置信息包括的物理层小区标识是否匹配， 若匹配， 则判 断所述集群配置信息是由其所属的演进小区发送。
所述保存模块 62具体用于， 若所述判断模块 65判断所述集群配置信 息是由其所属的演进小区发送的， 则保存所述接收模块 61接收的半静态调 度配置信息。
请参看图 8,是本发明图 6中第一处理模块 63的实施例的结构示意图， 所述第一处理模块 63包括：
第一激活单元 631 , 用于在初始时刻处于组发送状态时， 激活所述接收 模块接收的下行链路授权消息指示的下行链路资源；
其中， 初始时刻， 指的是实现集群组呼业务的装置接收到来自演进小 区的下行链路资源的时刻。
具体地，演进小区发送的下行链路授权消息为使用 Group C-RNTI加扰 的 PDCCH信令。 在装置 6的接收模块 61接收到下行链路授权消息之后， 装置 6 当前所处的状态不同， 其接收到下行链路授权消息之后的操作也不 同。
在初始时刻， 若装置 6处于组接收状态， 则第一激活单元 631激活所 述下行链路授权消息指示的下行链路资源， 并控制第一处理单元 632根据 所述下行链路资源接收集群组呼业务数据； 由于下行链路授权消息可以是 使用集群配置信息中的 Group C-RNTI去加扰的 PDCCH信令， 因此， 第一 激活单元 631 在激活所述下行链路授权消息指示的下行链路资源之前， 还 需要使用接收模块 61接收的集群配置信息包括的 Group C-RNTI去解扰该 PDCCH信令。
第一处理单元 632,用于在所述第一激活单元 631激活所述下行链路资 源后， 利用所述下行链路资源接收集群组呼业务数据；
第一记录单元 633 , 用于在初始时刻处于组发送状态时， 则记录第一用 户终端激活所述下行链路授权消息指示的下行链路资源的时间点； 所述第 一用户终端为集群组呼业务实现过程中处于组接收状态的用户终端；
若装置 6在初始时刻处于组发送状态， 则说明实现集群组呼业务的其 它装置在初始时刻处于组发送状态并进行了激活所述下行链路授权消息指 示的下行链路资源的操作， 例如， 第一装置处于组接收状态， 并进行了激 活所述下行链路授权消息指示的下行链路资源的操作。 因此， 所述装置则 需要记录所述第一装置激活所述下行链路授权消息指示的下行链路资源的 时间点。 由于所述装置与所述第一装置属于同一集群， 所以所述装置能够 知道所述第一装置激活所述下行链路资源的时间点。
第一处理单元 632 ,还用于在后续集群组呼业务实现过程中， 当在不同 时刻处于组接收状态时， 则根据所述半静态调度周期和所述第一记录单元 633记录的激活所述下行链路资源的时间点得到下行链路接收时刻，并根据 所述保存模块保存的下行链路授权消息接收集群组呼业务数据。
其中， 需要说明的是， 在后续集群组呼业务实现过程中， 当所述装置 在不同时刻处于组接收状态时， 第一处理单元 632可以根据所述半静态调 度周期和第一记录单元 632记录的所述激活下行链路资源的时间点， 得到 下行链路接收时刻， 并根据保存的所述下行链路授权消息接收集群组呼业 务数据。 例如， 在初始时刻， 所述装置处于组发送状态， 其第一记录单元 632 记录了激活所述下行链路资源的时间 T2,若经过了两个半静态周期之 后， 所述装置处于组接收状态， 其根据所述半静态调度周期 T以及 T2 , 计 算得到其下行链路接收时刻为 2T+ T2 , 并根据保存的所述下行链路授权消 息指示的下行链路资源， 接收集群组呼业务数据。
可以这样理解， 若装置在初始时刻处于组接收状态时， 那么在使用该 下行链路资源之前， 该装置需要激活该下行链路资源； 若装置在初始时刻 处于组发送状态， 则需要记录其它装置激活所述下行链路资源的时间点。 而在后续的集群组呼业务的实现中， 若该装置处于组接收状态， 该装置则 不需要再激活该下行链路资源。 也就是说， 在整个集群组呼业务的实现中， 下行链路资源只需要激活一次， 该装置便可周期性地使用该下行链路资源。 如此， 该装置在不同时刻处于组接收状态时， 演进小区则不用分别为其发 送下行链路授权消息， 因此能够进一步减少演进小区配置指令的开销， 进 一步提高了演进小区的资源利用率。
请参看图 9 ,是本发明图 6中第二处理模块 64的实施例的结构示意图， 所述第二处理模块 64包括： 第二激活单元 641 , 用于在初始时刻处于组发送状态时， 则激活所述上 行链路授权消息指示的上行链路资源；
其中， 初始时刻， 指的是实现集群组呼业务的装置接收到来自演进小 区的上行链路资源的时刻。
具体地，演进小区发送的上行链路授权消息为使用 Group C-RNTI加扰 的 PDCCH信令。 在装置的接收模块 61接收到上行链路授权消息之后， 装 置当前所处的状态不同， 其接收到上行链路授权消息之后的操作也不同。
在初始时刻， 若装置处于组发送状态， 则第二激活单元 641 激活所述 上行链路授权消息指示的上行链路资源， 并控制第二处理单元 642根据所 述上行链路资源发送集群组呼业务数据； 由于上行链路授权消息可以是使 用集群配置信息中的 Group C-RNTI去加扰的 PDCCH信令， 因此， 第二激 活单元 641 在激活所述上行链路授权消息指示的上行链路资源之前， 还需 要使用接收模块 61 接收的集群配置信息包括的 Group C-RNTI去解扰该 PDCCH信令。
第二处理单元 642,用于在所述第二激活单元 641激活所述上行链路资 源后， 利用所述上行链路资源发送集群组呼业务数据；
第二记录单元 643 , 用于在初始时刻处于组接收状态时， 则记录第二用 户终端激活所述上行链路授权消息指示的上行链路资源的时间点， 所述第 二用户终端为集群组呼业务的用户终端中处于组发送状态的用户终端； 若装置在初始时刻处于组接收状态， 则说明实现集群组呼业务的其它 装置在初始时刻处于组发送状态并进行了激活所述上行链路授权消息指示 的上行链路资源的操作。 例如， 第二装置处于组发送状态， 并进行了激活 所述上行链路授权消息指示的上行链路资源的操作。 因此， 所述装置则需 要记录所述第二装置激活所述上行链路授权消息指示的上行链路资源的时 间点。 由于所述装置与所述第二装置属于同一集群， 所以所述装置能够知 道所述第二装置激活所述下行链路资源的时间点。
所述第二处理单元 642,还用于在后续集群组呼业务实现过程中， 当在 不同时刻处于组发送状态时， 则根据所述半静态调度周期和所述第二记录 单元 643 记录的激活所述上行链路资源的时间点得到上行链路发送时刻， 并根据所述初始上行链路资源授权消息发送集群组呼业务数据。
其中， 需要说明的是， 在后续集群组呼业务实现过程中， 当所述装置 在不同时刻处于组发送状态时， 第二处理单元 642可以根据所述半静态调 度周期和第二记录单元 642记录的所述激活上行链路资源的时间点， 得到 上行链路接收时刻， 并根据保存的所述上行链路授权消息接收集群组呼业 务数据。 例如， 在初始时刻， 所述装置处于组接收状态， 其第二记录单元 642记录了第二装置激活所述上行链路资源的时间 T2,若经过了两个半静态 周期之后， 所述装置处于组接收状态， 其根据所述半静态调度周期 T 以及 T4, 计算得到其上行链路接收时刻为 2T+ T4, 并根据保存的所述上行链路 授权消息指示的上行链路资源， 发送集群组呼业务数据。
可以这样理解， 若装置在初始时刻处于组发送状态， 在使用该上行链 路资源之前， 该装置需要激活该上行链路资源， 若装置在初始时刻处于组 接收状态， 则需要记录其它装置激活所述上行链路资源的时间点。 而在后 续的集群组呼业务的实现中， 该装置则不需要再激活该上行链路资源。 也 就是说在， 在整个集群组呼业务的实现中， 上行链路资源只需要激活一次， 该装置在处于组发送状态时便可周期性地使用该上行链路资源。 如此， 该 装置在不同时刻处于组接收状态时， 演进小区不用分别为其发送上行链路 授权消息， 因此能够进一步减少演进小区配置指令的开销， 进一步提高了 演进小区的资源利用率。
其中， 所述装置 6与所述第一装置第二装置均可以为用户终端， 如手 机等设备。
请参考图 10, 是本发明提供的一种实现集群组呼业务的装置的第三实 施例的结构示意图， 所述装置 10包括：
配置模块 101 ,用于演进小区为所述演进小区内集群组呼业务的用户终 端配置集群配置信息、 下行链路授权消息和 /或上行链路授权消息， 所述下 行链路授权消息指示在不同时刻处于组接收状态的用户终端以半静态调度 方式共享的下行链路资源； 所述上行链路授权消息指示在不同时刻处于组 发送状态的用户终端以半静态调度方式轮流使用的上行链路资源；
其中， 配置模块 101 配置的集群配置信息包括用于指示接收或发送集 群组呼业务数据时间间隔的半静态调度周期、 用于唯一标识所述演进小区 的物理层小区标识、以及集群组调度使用的组小区无线网络临时标识 Group C-RNTL
发送模块 102,用于向集群组呼的用户终端发送所述配置模块 101配置 的集群配置信息、 下行链路授权消息和 /或上行链路授权消息。
一般地， 发送模块 102是先发送集群配置信息给集群组呼业务的用户 终端， 在集群组呼业务的用户终端接收了集群配置信息之后， 然后再发送 下行链路授权消息和 /或上行链路授权消息给用户终端。
具体地， 发送模块 102用于以寻呼消息形式或新的公共控制消息形式 向所述集群组呼的用户终端发送集群组呼通知消息， 所述集群组呼通知消 息中携带有所述集群配置信息。
其中， 在一次集群组呼业务实现过程中， 所述发送模块 102只发送一 次下行链路授权消息和 /或上行链路授权消息， 所述下行链路授权消息和 / 或下行链路授权消息使用所述集群配置信息包括的集群组调度使用的组小 区无线网络临时标识 Group C-RNTI进行加扰。
具体地， 所述下行链路授权消息可以为使用 Group C-RNTI 加扰的 PDCCH信令。
其中， 所述发送模块 102, 还用于在后续集群组呼业务实现过程中， 根 据激活下行链路资源的时间点， 按照所述配置模块 101 配置的半静态调度 周期， 向处于组接收状态的用户终端发送集群组呼业务数据； 所述激活下 行链路资源的时间点是在初始时刻处于组接收状态的用户终端激活所述下 行链路资源的时间。 其中， 初始时刻具体为实现集群组呼业务的装置向集 群组呼业务的用户终端发送下行链路授权消息的时刻。
其中， 所述激活下行链路资源的时间点是在初始时刻， 处于组接收状 态的用户终端激活所述下行链路资源的时间。
由于装置配置的是釆用半静态调度方式进行调度的下行链路资源， 所 以在一次集群组呼业务的实现过程中， 装置只需要向集群组呼业务的用户 终端发送一次下行链路授权消息。 在后续集群组呼业务实现过程中， 装置 则根据激活下行链路资源的时间点， 按照所述配置模块 101 配置的半静态 调度周期， 向处于组接收状态的用户终端发送集群组呼业务数据。 如此， 该装置则不用单独、 重复地向在不同时刻处于组接收状态的用户终端分别 发送下行链路授权消息， 进而减少了演进小区的配置指令的开销， 进一步 提高了演进小区的资源利用率。
进一步地， 所述装置 10还包括：
网侧接收模块 103 , 用于在后续集群组呼业务实现过程中，根据激活上 行链路资源的时间点， 按照所述配置模块 101 配置的半静态调度周期， 接 收处于组发送状态的用户终端发送的集群组呼业务数据；
其中， 初始时刻具体为装置 10向集群组呼业务的用户终端发送上行链 路授权消息的时刻。 所述激活上行链路资源的时间点是在初始时刻， 处于 组发送状态的用户终端激活所述上行链路资源的时间。
由于装置 10配置的是釆用半静态调度方式进行调度的上行链路资源， 所以在一次集群组呼业务的实现过程中， 装置只需要向集群组呼业务的用 户终端发送一次上行链路授权消息。 在后续集群组呼业务实现过程中， 装 置则根据激活上行链路资源的时间点， 按照所述配置模块 101 配置的半静 态调度周期， 接收处于组发送状态的用户终端发送的集群组呼业务数据。 如此， 该装置则不用单独、 重复地向在不同时刻处于组发送状态的用户终 端分别发送上行链路授权消息， 进而减少了演进小区的配置指令的开销， 进一步提高了演进小区的资源利用率。
本实施例中， 由于装置 10 配置的下行链路资源指示有当集群组呼业务 的用户终端处于组接收状态时以半静态调度方式共享的下行链路资源， 和 / 或配置的上行链路授权消息指示有当集群组呼业务的用户终端处于组发送 状态时以半静态调度方式轮流使用的下行链路资源。 如此， 该装置则不用 单独、重复地为该集群内的用户终端配置下行链路资源和 /或上行链路资源 , 从而减少了演进小区因单独、 重复地为集群内的用户终端配置下行链路资 源和 /或上行链路资源所带来的配置指令的开销， 进而提高了演进小区的资 源利用率。
其中， 所述装置 10可以为基站等网络实体。
以上对本发明所提供的实施例进行了详细介绍， 本文中应用了具体个 例对本发明的原理及实施方式进行了阐述， 以上实施例的说明只是用于帮 助理解本发明的方法及其核心思想； 同时， 对于本领域的一般技术人员， 依据本发明的思想， 在具体实施方式及应用范围上均会有改变之处， 综上 所述， 本说明书内容不应理解为对本发明的限制。

Claims

权利要求
1、 一种实现集群组呼业务的方法， 其特征在于， 包括：
集群组呼业务的用户终端接收来自演进小区的集群配置信息、 下行链 路授权消息和 /或上行链路授权消息；
所述集群组呼业务的用户终端保存所述集群配置信息、 下行链路授权 消息和 /或上行链路授权消息；
若所述集群组呼业务的用户终端在不同时刻处于组接收状态， 根据所 述集群配置信息， 以半静态调度方式共享所述下行链路授权消息指示的下 行链路资源， 接收集群组呼业务数据； 和 /或
若所述集群组呼业务的用户终端在不同时刻处于组发送状态， 根据所 述集群配置信息， 以半静态调度方式轮流使用所述上行链路授权消息指示 的上行链路资源， 发送集群组呼业务数据。
2、 如权利要求 1所述的方法， 其特征在于， 所述集群配置信息包括用 于指示接收或发送集群组呼业务数据时间间隔的半静态调度周期和用于唯 一标识所述演进小区的物理层小区标识。
3、 如权利要求 2所述的方法， 其特征在于， 在所述集群组呼业务的用 户终端保存所述集群配置信息之前， 还包括：
所述集群组呼业务的用户终端判断所述集群配置信息是否由其所属的 演进小区发送；
若是， 则所述集群组呼业务的用户终端保存所述集群配置信息。
4、 如权利要求 3所述的方法， 其特征在于， 所述集群组呼业务的用户 终端判断所述集群配置信息是否由其所属的演进小区发送， 包括：
所述集群组呼业务的用户终端判断其所属演进小区的物理层小区标识 与所述集群配置信息包括的物理层小区标识是否匹配， 若匹配， 则判断所 述集群配置信息是由其所属的演进小区发送。
5、 如权利要求 2-4任一项所述的方法， 其特征在于， 所述集群组呼业 务的用户终端在不同时刻处于组接收状态， 根据所述集群配置信息， 以半 静态调度方式共享所述下行链路授权消息指示的下行链路资源， 接收集群 组呼业务数据， 包括：
若所述集群组呼业务的用户终端在初始时刻处于组接收状态， 则激活 所述下行链路授权消息指示的下行链路资源， 并利用所述下行链路资源接 收集群组呼业务数据；
若所述集群组呼业务的用户终端在初始时刻处于组发送状态， 则记录 第一用户终端激活所述下行链路授权消息指示的下行链路资源的时间点； 所述第一用户终端为集群组呼业务实现过程中处于组接收状态的用户终 端；
在后续集群组呼业务实现过程中， 当所述集群组呼业务的用户终端在 不同时刻处于组接收状态时， 则根据所述半静态调度周期和记录的激活所 述下行链路资源的时间点得到下行链路接收时刻， 并根据保存的所述下行 链路授权消息接收集群组呼业务数据。
6、 如权利要求 2-4任一权利要求所述的方法， 其特征在于， 若所述集 群组呼业务的用户终端在不同时刻处于组发送状态， 根据所述集群配置信 息， 以半静态调度方式轮流使用所述上行链路授权消息指示的上行链路资 源， 发送集群组呼业务数据， 包括：
若所述集群组呼业务的用户终端在初始时刻处于组发送状态， 则激活 所述上行链路授权消息指示的上行链路资源， 并利用所述上行链路资源发 送集群组呼业务数据；
若所述集群组呼业务的用户终端在初始时刻处于组接收状态， 则记录 第二用户终端激活所述上行链路授权消息指示的上行链路资源的时间点， 所述第二用户终端为集群组呼业务的用户终端中处于组发送状态的用户终 在后续集群组呼业务实现过程中， 当所述集群组呼业务的用户终端在 不同时刻处于组发送状态时， 则根据所述半静态调度周期和记录的激活所 述上行链路资源的时间点得到上行链路发送时刻， 并根据保存的所述上行 链路授权消息发送集群组呼业务数据。
7、 一种实现集群组呼业务的方法， 其特征在于， 包括：
演进小区为所述演进小区内集群组呼业务的用户终端配置集群配置信 息、 下行链路授权消息和 /或上行链路授权消息， 所述下行链路授权消息指 示在不同时刻处于组接收状态的用户终端以半静态调度方式共享的下行链 路资源； 所述上行链路授权消息指示在不同时刻处于组发送状态的用户终 端以半静态调度方式轮流使用的上行链路资源；
所述演进小区向所述集群组呼业务的用户终端发送所述集群配置信 息、 下行链路授权消息和 /或上行链路授权消息。
8、 如权利求 7所述的方法， 其特征在于， 所述集群配置信息包括： 用 于指示接收或发送集群组呼业务数据时间间隔的半静态调度周期、 用于唯 一标识所述演进小区的物理层小区标识、 以及集群组调度使用的组小区无 线网络临时标识 Group C-RNTL
9、 如权利要求 7-8任一项所述的方法， 其特征在于， 所述演进小区向 所述集群组呼业务的用户终端发送所述集群配置信息， 包括：
所述演进小区以寻呼消息形式或新的公共控制消息形式向所述集群组 呼业务的用户终端发送集群组呼通知消息， 所述集群组呼通知消息中携带 有所述集群配置信息。
10、 如权利要求 7-9任一项所述的方法， 其特征在于， 在一次集群组呼 业务实现过程中， 所述演进小区只发送一次下行和 /或上行链路授权消息， 所述下行和 /或上行链路授权消息分别使用所述集群配置信息中集群组调度 使用的组小区无线网络临时标识 Group C-RNTI进行加扰。
11、如权利要求 7-9任一项所述的方法，其特征在于，所述方法还包括： 在后续集群组呼业务实现过程中， 所述演进小区根据激活下行链路资 源的时间点， 按照所述半静态调度周期向处于组接收状态的用户终端发送 集群组呼业务数据；
其中， 所述激活下行链路资源的时间点是在初始时刻处于组接收状态 的用户终端激活所述下行链路资源的时间。
12、如权利要求 7-9任一项所述的方法，其特征在于，所述方法还包括： 在后续集群组呼业务实现过程中， 所述演进小区根据激活上行链路资 源的时间点， 按照所述半静态调度周期接收处于组发送状态的用户终端发 送的集群组呼业务数据；
其中， 所述激活上行链路资源的时间点是在初始时刻处于组发送状态 的用户终端激活所述上行链路资源的时间。
13、 一种实现集群组呼业务的装置， 其特征在于， 包括：
接收模块， 用于接收来自演进小区的集群配置信息、 下行链路授权消 息和 /或上行链路授权消息；
保存模块， 用于保存所述接收模块接收的集群配置信息、 下行链路授 权消息和 /或上行链路授权消息；
第一处理模块， 用于当在不同时刻处于组接收状态时， 根据所述保存 模块保存的集群配置信息， 以半静态调度方式共享所述下行链路授权消息 指示的下行链路资源， 接收集群组呼业务数据； 和 /或
第二处理模块， 用于当在不同时刻处于组发送状态时， 根据所述保存 模块保存的集群配置信息， 以半静态调度方式轮流使用所述上行链路授权 消息指示的上行链路资源， 发送集群组呼业务数据。
14、 根据权利要求 13所述的装置， 其特征在于， 所述接收模块接收的 集群配置信息包括用于指示接收或发送集群组呼业务数据时间间隔的半静 态调度周期和用于唯一标识所述演进小区的物理层小区标识。
15、 根据权利要求 14所述的装置， 其特征在于， 所述装置还包括： 判断模块， 用于判断所述接收模块接收的集群配置信息是否由其所属 的演进小区发送；
所述保存模块具体用于， 若所述判断模块判断所述集群配置信息是由 其所属的演进小区发送的， 则保存所述接收模块接收的半静态调度配置信 息。
16、 根据权利要求 15所述的装置， 其特征在于， 所述判断模块具体用 于判断其所属演进小区的物理层小区标识与所述集群配置信息包括的物理 层小区标识是否匹配， 若匹配， 则判断所述集群配置信息是由其所属的演 进小区发送。
17、 根据权利要求 14至 16任一项所述的装置， 其特征在于， 所述第 一处理模块包括：
第一激活单元， 用于在初始时刻处于组发送状态时， 激活所述接收模 块接收的下行链路授权消息指示的下行链路资源；
第一处理单元， 用于在所述第一激活单元激活所述下行链路资源后， 利用所述下行链路资源接收集群组呼业务数据；
第一记录单元， 用于在初始时刻处于组发送状态时， 则记录第一用户 终端激活所述下行链路授权消息指示的下行链路资源的时间点； 所述第一 用户终端为集群组呼业务实现过程中处于组接收状态的用户终端；
所述第一处理单元， 还用于在后续集群组呼业务实现过程中， 当在不 同时刻处于组接收状态时， 则根据所述半静态调度周期和所述第一记录单 元记录的激活所述下行链路资源的时间点得到下行链路接收时刻， 并根据 所述保存模块保存的下行链路授权消息接收集群组呼业务数据。
18、 根据权利要求 14至 16任一项所述的装置， 其特征在于， 第二处 理模块包括：
第二激活单元， 用于在初始时刻处于组发送状态时， 则激活所述上行 链路授权消息指示的上行链路资源；
第二处理单元， 用于在所述第二激活单元激活所述上行链路资源后， 利用所述上行链路资源发送集群组呼业务数据；
第二记录单元， 用于在初始时刻处于组接收状态时， 则记录第二用户 终端激活所述上行链路授权消息指示的上行链路资源的时间点， 所述第二 用户终端为集群组呼业务实现过程中处于组发送状态的用户终端；
所述第二处理单元， 还用于在后续集群组呼业务实现过程中， 当在不 同时刻处于组发送状态时， 则根据所述半静态调度周期和所述第二记录单 元记录的激活所述上行链路资源的时间点得到上行链路发送时刻， 并根据 所述初始上行链路资源授权消息发送集群组呼业务数据。
19、 一种实现集群组呼业务的装置， 其特征在于， 包括：
配置模块， 用于演进小区为所述演进小区内集群组呼业务的用户终端 配置集群配置信息、 下行链路授权消息和 /或上行链路授权消息， 所述下行 链路授权消息指示在不同时刻处于组接收状态的用户终端以半静态调度方 式共享的下行链路资源； 所述上行链路授权消息指示在不同时刻处于组发 送状态的用户终端以半静态调度方式轮流使用的上行链路资源；
发送模块， 用于向集群组呼的用户终端发送所述配置模块配置的集群 配置信息、 下行链路授权消息和 /或上行链路授权消息。
20、 根据权利要求 19所述的装置， 其特征在于， 所述配置模块配置的 集群配置信息包括： 用于指示接收或发送集群组呼业务数据时间间隔的半 静态调度周期、 用于唯一标识所述演进小区的物理层小区标识、 以及集群 组调度使用的组小区无线网络临时标识 Group C-RNTI。
21、 根据权利要求 19或 20所述的装置， 其特征在于， 所述发送模块， 具体用于以寻呼消息形式或新的公共控制消息形式向所述集群组呼的用户 终端发送集群组呼通知消息， 所述集群组呼通知消息中携带有所述集群配 置信息。
22、 如权利要求 20或 21所述的装置， 其特征在于， 在一次集群组呼 业务实现过程中， 所述发送模块只发送一次下行链路授权消息和 /或上行链 路授权消息， 所述下行链路授权消息和 /或下行链路授权消息使用所述集群 配置信息包括的集群组调度使用的组小区无线网络临时标识 Group C-RNTI 进行力口扰。
23、如权利要求 20-22任一项所述的装置，其特征在于，所述发送模块， 还用于在后续集群组呼业务实现过程中， 根据激活下行链路资源的时间点， 按照所述配置模块配置的半静态调度周期， 向处于组接收状态的用户终端 发送集群组呼业务数据；
其中， 所述激活下行链路资源的时间点是在初始时刻处于组接收状态 的用户终端激活所述下行链路资源的时间。
24、 如权利要求 20-22任一项所述的装置， 其特征在于， 所述装置还包 括：
网侧接收模块， 用于在后续集群组呼业务实现过程中， 根据激活上行 链路资源的时间点， 按照所述配置模块配置的半静态调度周期， 接收处于 组发送状态的用户终端发送的集群组呼业务数据；
其中， 所述激活上行链路资源的时间点是在初始时刻处于组发送状态 的用户终端激活所述上行链路资源的时间。
PCT/CN2012/086457 2012-01-05 2012-12-12 一种实现集群组呼业务的方法及装置 WO2013102392A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP12864427.5A EP2793492B1 (en) 2012-01-05 2012-12-12 Method and device for implementing cluster group call service
US14/323,963 US9661478B2 (en) 2012-01-05 2014-07-03 Method and apparatus for implementing trunking group call service

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201210001585.X 2012-01-05
CN201210001585.XA CN103200530B (zh) 2012-01-05 2012-01-05 一种实现集群组呼业务的方法及装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US14/323,963 Continuation US9661478B2 (en) 2012-01-05 2014-07-03 Method and apparatus for implementing trunking group call service

Publications (1)

Publication Number Publication Date
WO2013102392A1 true WO2013102392A1 (zh) 2013-07-11

Family

ID=48722854

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2012/086457 WO2013102392A1 (zh) 2012-01-05 2012-12-12 一种实现集群组呼业务的方法及装置

Country Status (4)

Country Link
US (1) US9661478B2 (zh)
EP (1) EP2793492B1 (zh)
CN (1) CN103200530B (zh)
WO (1) WO2013102392A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104469948A (zh) * 2013-09-23 2015-03-25 成都鼎桥通信技术有限公司 一种上行半静态资源的分配方法

Families Citing this family (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104378188B (zh) * 2013-08-12 2019-02-22 北京信威通信技术股份有限公司 一种下行控制信道处理方法、装置和系统
CN104427626B (zh) * 2013-08-23 2018-02-23 普天信息技术有限公司 半静态调度方法和系统
WO2015051504A1 (zh) * 2013-10-09 2015-04-16 华为技术有限公司 半静态共享资源调度方法和装置
WO2016029933A1 (en) * 2014-08-26 2016-03-03 Telefonaktiebolaget L M Ericsson (Publ) Periodic uplink grant alignment in a cellular network
CN104602201B (zh) * 2015-02-09 2017-11-07 重庆邮电大学 Lte集群专网中单终端同时接收多组呼业务的方法
CN105992161B (zh) * 2015-03-03 2019-04-19 普天信息技术有限公司 一种组呼下行用户面建立方法、基站以及演进分组核心
CN106358159A (zh) * 2015-07-17 2017-01-25 中兴通讯股份有限公司 宽带集群系统的共享信道管理方法、系统、终端和基站
EP3217741A1 (en) * 2016-03-11 2017-09-13 ASUSTek Computer Inc. Method and apparatus for multicasting data to a group in a wireless communication system
CN107787043B (zh) * 2016-08-24 2020-06-16 大唐移动通信设备有限公司 一种下行调度方法及装置
US10342038B2 (en) * 2016-10-04 2019-07-02 Qualcomm Incorporated Method and apparatus for scheduling multiple uplink grants of different types
US11558923B2 (en) 2019-09-09 2023-01-17 Qualcomm Incorporated Uplink resource grant release in wireless communication systems
US11849430B2 (en) 2019-09-09 2023-12-19 Qualcomm Incorporated Uplink resource allocation and activation
CN115348547B (zh) * 2022-08-09 2023-11-07 北京长焜科技有限公司 B-Trunc永久业务的发起、休眠、中止方法、装置及电子设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1984379A (zh) * 2005-12-12 2007-06-20 中兴通讯股份有限公司 一种cdma数字集群传统式组呼通话过程的实现方法
CN101321327A (zh) * 2008-07-03 2008-12-10 中兴通讯股份有限公司 一种集群系统中长码掩码的生成方法
CN101998643A (zh) * 2009-08-26 2011-03-30 中兴通讯股份有限公司 一种半静态调度上行激活及重激活的系统及方法
WO2011135555A1 (en) * 2010-04-30 2011-11-03 Nokia Corporation Network controlled device to device / machine to machine cluster operation

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR100948799B1 (ko) * 2006-08-07 2010-03-24 삼성전자주식회사 광대역 무선 통신시스템에서 단방향 통신을 위한 자원 할당 장치 및 방법
KR101473229B1 (ko) * 2007-02-02 2014-12-16 미쓰비시덴키 가부시키가이샤 통신 방법, 기지국, 이동 통신 시스템 및 이동 단말
US8027696B2 (en) * 2007-12-28 2011-09-27 Motorola Solutions, Inc. Method and apparatus for allocating channel resources in a wireless communication system
JP4384700B1 (ja) * 2008-06-23 2009-12-16 株式会社エヌ・ティ・ティ・ドコモ 移動通信方法、移動局及び無線基地局
WO2010068011A2 (en) * 2008-12-08 2010-06-17 Lg Electronics Inc. Method of transmitting and receiving physical downlink shared channel in wireless communication system
US8422448B2 (en) * 2010-08-09 2013-04-16 Alcatel Lucent Group call control in a wireless broadband communication network

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1984379A (zh) * 2005-12-12 2007-06-20 中兴通讯股份有限公司 一种cdma数字集群传统式组呼通话过程的实现方法
CN101321327A (zh) * 2008-07-03 2008-12-10 中兴通讯股份有限公司 一种集群系统中长码掩码的生成方法
CN101998643A (zh) * 2009-08-26 2011-03-30 中兴通讯股份有限公司 一种半静态调度上行激活及重激活的系统及方法
WO2011135555A1 (en) * 2010-04-30 2011-11-03 Nokia Corporation Network controlled device to device / machine to machine cluster operation

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP2793492A4 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104469948A (zh) * 2013-09-23 2015-03-25 成都鼎桥通信技术有限公司 一种上行半静态资源的分配方法

Also Published As

Publication number Publication date
CN103200530A (zh) 2013-07-10
CN103200530B (zh) 2016-12-14
US20140323171A1 (en) 2014-10-30
EP2793492B1 (en) 2018-04-04
EP2793492A4 (en) 2014-12-10
EP2793492A1 (en) 2014-10-22
US9661478B2 (en) 2017-05-23

Similar Documents

Publication Publication Date Title
WO2013102392A1 (zh) 一种实现集群组呼业务的方法及装置
RU2584825C1 (ru) Способ конфигурации ресурсов для кластерного полупостоянного планирования, базовой станции и терминала
US9467900B2 (en) Service scheduling method and apparatus
CN101616364B (zh) 一种组呼业务实现方法
CN102215458B (zh) 基于长期演进技术的数字集群通信系统以及基站和终端
KR101407056B1 (ko) 피어 투 피어 통신을 위한 페이징 메시지들을 전송하기 위한 장치 및 방법들
WO2016191943A1 (zh) 一种资源调度方法、基站以及用户设备
CA2563029C (en) Method 0f uplink preemption by users in a trunking group
CN106068669A (zh) 通信设备和通过无线接入接口进行通信以执行设备到设备通信的方法
WO2011018037A1 (zh) 一种配置mbms控制信息的方法、设备和系统
EP3657887B1 (en) Resource allocation method and device
CN102625256B (zh) 一种集群传输通知、处理方法及装置
CN104427626A (zh) 半静态调度方法和系统
CN102857882A (zh) 群组呼叫建立、群组信息发送方法及对应用户设备和网元
WO2016019739A1 (zh) 用户状态的处理方法及装置
CN102547596A (zh) 一种话权指示信息的传输方法及装置
WO2013107216A1 (zh) Td-lte数字集群通信系统及群组业务实现方法
WO2007014528A1 (fr) Procédé pour réaliser un appel unique dans un système de groupe
CN111865525A (zh) 资源配置方法及装置
WO2014067300A1 (zh) 一种集群信息的传送方法及相应的集群终端和接入节点
WO2014121679A1 (zh) 一种设备到设备通信数据传输方法、系统和用户设备
WO2013131447A1 (zh) 一种组呼会话信息的传输方法和设备
WO2008095419A1 (en) Method for allocating dedicated channel and base station device thereof
CN101453789B (zh) 一种集群组呼被叫接续时间的方法及系统
WO2016176843A1 (zh) 数据发送、接收方法、基站和用户设备

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: 12864427

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: 2012864427

Country of ref document: EP