US20150148034A1 - Method and system for managing mass registration scenario in two-way radio system - Google Patents
Method and system for managing mass registration scenario in two-way radio system Download PDFInfo
- Publication number
- US20150148034A1 US20150148034A1 US14/090,341 US201314090341A US2015148034A1 US 20150148034 A1 US20150148034 A1 US 20150148034A1 US 201314090341 A US201314090341 A US 201314090341A US 2015148034 A1 US2015148034 A1 US 2015148034A1
- Authority
- US
- United States
- Prior art keywords
- registration
- talkgroup
- restriction
- control channel
- restriction period
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 38
- 230000000977 initiatory effect Effects 0.000 claims description 17
- 230000004044 response Effects 0.000 claims description 9
- 230000001052 transient effect Effects 0.000 claims 1
- 238000004891 communication Methods 0.000 description 24
- 230000008901 benefit Effects 0.000 description 7
- 238000010586 diagram Methods 0.000 description 6
- 230000008569 process Effects 0.000 description 6
- 230000006870 function Effects 0.000 description 4
- 230000009471 action Effects 0.000 description 3
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012544 monitoring process Methods 0.000 description 2
- 238000013459 approach Methods 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 230000001934 delay Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000013213 extrapolation Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 238000001228 spectrum Methods 0.000 description 1
- 238000004148 unit process Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
- H04W60/005—Multiple registrations, e.g. multihoming
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
- H04W60/04—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration using triggered events
-
- 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
- H04W48/00—Access restriction; Network selection; Access point selection
- H04W48/02—Access restriction performed under specific conditions
- H04W48/06—Access restriction performed under specific conditions based on traffic conditions
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W64/00—Locating users or terminals or network equipment for network management purposes, e.g. mobility management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W74/00—Wireless channel access
Definitions
- Trunked radio systems are one solution for permitting two-way radio communications, such as voice and data communications, not only between individual users equipped with subscriber radio units, but also among all active members of particular talkgroups.
- Conventional two-way radio systems permit group communications among radio users who tune in to a particular communications channel, such as a particular frequency, that has been assigned in advance.
- Trunked radio systems do not require members of a talkgroup to select any particular communications channel in advance. Instead, communications channels are assigned only as they are needed. The assignment of communications channels is performed by a site controller. Users of subscriber units remain in wireless communication with a site controller over a duplex control channel, which is comprised of an inbound channel for communications to the site controller and an outbound channel for communications from the site controller to the subscriber units.
- a request is made to the site controller over the inbound control channel.
- the site controller alerts the relevant subscriber units to the communications channel to be used.
- Subscriber units can be turned on or off, or they can enter and leave an area served by a particular site controller, and site controllers themselves can be in and out of service at various times.
- subscriber units engage in a registration process in which subscriber units send registration requests to a site controller and identify the talkgroup or groups with which they are affiliated.
- the site controller registers the presence of the subscriber units and confirms the registration by sending registration grants to the respective subscriber units.
- a site controller may also be affiliated with one or more relays that allow subscriber units to communicate with one another despite being served by different site controllers. Such communications may take place through the intermediary of a backend network.
- Trunked radio systems have several advantages over conventional radio systems, such as a more efficient allocation of the radio spectrum and greater flexibility in the assignment of subscriber units to multiple different talkgroups.
- the use of a trunked radio system poses other challenges. For example, it is possible for the control channel, which can be shared by numerous subscriber units, to be overloaded by radio traffic. Such a situation can arise when several subscriber units are attempting to send registration requests at the same time. When two subscriber units attempt to send messages, such as registration requests, on the same channel at the same time, it is often the case that neither message is intelligible. The two subscriber units whose requests have collided then need to make a new attempt to send their messages.
- a random back-off routine works well during ordinary radio traffic conditions.
- a situation can arise in which the amount of subscriber unit registration traffic is too high to be satisfactorily handled by only a random back-off routine.
- One such situation is a mass registration event, where some occurrence leads to a large number of registration requests to be sent at substantially the same time.
- a situation may arise in which one site controller fails, leading many of the subscriber units that were formerly registered with that site controller to inundate neighboring site controllers with new registration requests.
- FIG. 1 is a schematic block diagram illustrating an architecture of a trunked radio system in accordance with some embodiments.
- FIG. 2 is a schematic message flow diagram illustrating exemplary communications between a site controller and talkgroup members in some embodiments.
- FIG. 3 is a flowchart illustrating an operation of a site controller in some embodiments.
- FIG. 4 is a schematic message flow diagram illustrating exemplary communications between a site controller and talkgroup members in some embodiments.
- FIG. 5 is a flowchart illustrating an operation of a site controller in some embodiments.
- FIG. 6 is a flowchart illustrating an operation of a subscriber unit in some embodiments.
- a site controller detects that an inbound control channel is in a mass registration condition. During the mass registration condition, the site controller receives a plurality of registration requests over the inbound control channel. Among the requests are at least a first registration request from a member of a first talkgroup. In response to the first registration request, the site controller initiates a restriction period by sending a restriction message on an outbound control channel. The restriction message instructs members of the first talkgroup to cease registration requests. When the restriction period ends, the site controller sends an invitation message on the outbound control channel. The invitation message invites members of the first talkgroup to resume registration requests.
- FIG. 1 is a schematic block diagram illustrating an architecture of a trunked radio system in accordance with some embodiments.
- the system includes a site controller 100 equipped with a transceiver 101 for conducting wireless communications with a plurality of subscriber units.
- the transceiver 101 may include several antennas for communications on different communications channels, including a duplex control channel that includes an inbound control channel for communications to the site controller and an outbound control channel for communications to the subscriber units.
- the site controller 100 includes a control module 102 , which comprises a general- or special-purpose processor 103 and a non-transitory computer-readable memory 104 operatively coupled to the processor 103 .
- the memory 103 stores instructions executable by the processor and operative to perform the site controller steps described in further detail below.
- a subscriber unit apparatus may comprise a transceiver for communicating on an inbound control channel and an outbound control channel, and a processor coupled to a non-transitory computer-readable medium storing executable instructions that, when executed on the processor, are operative to (i) receive a restriction message on the outbound control channel, wherein the restriction message initiates a restriction period by instructing subscribers who are not members of the first talkgroup to cease registration requests; (ii) to determine that the subscriber unit is not a member of the first talkgroup; and in response to the determination that the subscriber unit is not a member of the first talkgroup, (iii) to determine the end of the restriction period, where the restriction period ends at the earlier of the following times: (a) when a predetermined delay time has passed since the initiation of the restriction period; and (b) when a predetermined silence time has passed since the receipt of a registration acknowledgement on the outbound control channel; and only after the expiration of the restriction period, to send
- the site controller 100 is in wireless communication with a plurality of subscriber units, such as subscriber units 110 , 111 , 112 , and 113 .
- subscriber 110 is a member of talkgroup A
- subscriber 111 is a member of talkgroup B
- subscriber 112 is a member of talkgroup C.
- a subscriber unit may be a member of different talkgroups or multiple talkgroups at different times, as illustrated by subscriber unit 113 , which can be a member either or both of talkgroup A or of talkgroup B.
- the site controller 100 is coupled with a backend network 120 to permit subscriber units registered with site controller 100 to communicate over the backend network with other subscriber units being served by other site controllers.
- subscriber units 110 , 111 , 112 , and 113 register with site controller 100 by sending registration messages to site controller 100 over the inbound control channel identifying themselves and the talkgroups of which they are members. To complete the registration, site controller 100 sends registration grants to the respective subscriber units over the outbound control channel.
- a large number of subscriber units may attempt to send registration messages to site controller 100 at substantially a same time. This leads to multiple collisions between messages on the inbound control channel. Many of these messages are likely to be unintelligible to the site controller 100 . Site controller 100 will be unable to register the subscriber units whose messages were not received or were unintelligible, and in turn, site controller 100 will be unable to send registration grants to the requesting subscriber units. Consequently, the subscriber units will attempt to re-send their registration requests, which will further increase the traffic on the inbound control channel. This situation is referred to herein as a mass registration condition.
- a mass registration condition may arise from several possible scenarios. For example, if a site is temporarily out of service, a mass registration condition may arise when the site comes back online. A mass registration condition may arise when a large number of subscriber units are turned on at substantially the same time, or they all arrive in the vicinity of a site controller at substantially the same time. Such situations may arise when, for example, workers equipped with subscriber units begin their shift at the same time, or when rescue or law enforcement personnel arrive at a particular location at substantially the same time. A mass registration condition may arise when one site controller fails, and the subscriber units that were formerly registered with the failed site controller begin sending registration requests to nearby site controllers.
- FIG. 2 is a schematic message flow diagram illustrating exemplary communications between a site controller 200 and subscriber units that are members of three talkgroups during a mass registration condition. Subscriber units that are members of talkgroup A are represented by entity 210 , subscriber units that are members of talkgroup B are represented by entity 211 , and subscriber units that are members of talkgroup C are represented by entity 212 . Extrapolation of the principles described in FIG. 2 to situations involving any number of talkgroups will be apparent to one of ordinary skill in the art.
- horizontal arrows are representative of messages exchanged between the site controller 200 and the subscriber units.
- Leftward arrows represent one or more messages sent on the inbound control channel to the site controller 200 .
- Rightward arrows represent one or more messages sent on the outbound control channel by the site controller 200 .
- Messages sent by the controller 200 may typically be received by members of multiple talkgroups, even if they pertain only to a single talkgroup, but for efficiency of illustration, the arrows are shown to terminate at the talkgroup to which the outbound message is intended to pertain. It should also be noted that, for efficiency of conveying the concepts described herein, not every message exchanged between subscriber units and site controller is illustrated. Moreover, a single horizontal line may represent more than one message.
- step 220 during a mass registration condition, the site controller 200 receives at least one registration request from members 210 of talkgroup A.
- the received registration request or requests may be one of many attempted requests sent by members of talkgroups A, B, and C. However, many of the attempted registration requests may not be received by site controller 200 due to the mass registration condition.
- the site controller 200 In response to the registration request received from a member of talkgroup A, the site controller 200 sends a restriction message 222 on the outbound control channel.
- the restriction message instructs the members 210 of talkgroup A to hold off temporarily on the sending of registration requests.
- the site controller 200 operates to alleviate the immediate demands on the inbound control channel.
- the restriction message 222 may be a separate dedicated message, the sole purpose of which is to convey the restriction period.
- the restriction message 222 may itself be a registration grant for a member of talkgroup A.
- the restriction message may be a registration grant that makes use of a specialized opcode, or it may include particular flags or other information in the message payload that indicates that the registration grant is also a restriction message.
- Such information in a registration grant that identifies the registration grant as a restriction message is referred to herein as a restriction code.
- the restriction message 222 may indicate to the subscriber units that the associated talkgroup is registered with the site controller 200 . A restriction message may be sent several times to ensure receipt by members of a restricted talkgroup.
- the restriction message 222 is sent at the beginning of a first restriction period 224 , during which members 210 of talkgroup A hold off on sending registration requests. Members 211 and 212 of other talkgroups are not restricted from sending registration requests by restriction message 222 . As a result, those subscriber units may continue to attempt to send registration requests. For example, in step 226 , one or more members of talkgroup B send registration requests to the site controller 200 . If the imposition of the first restriction period 224 has been sufficient to alleviate the mass registration condition, then the site controller 200 may respond to the talkgroup B requests with ordinary registration grants. However, in the example illustrated in FIG. 2 , the mass registration condition persists despite the imposition of the first restriction period.
- the site controller 200 initiates a second restriction period 228 by sending a restriction message 230 that instructs members 211 of talkgroup B to hold off temporarily on the sending of registration requests.
- the imposition of the second restriction period 228 further alleviates the demands on the inbound control channel.
- the first restriction period 224 can overlap with the second restriction period 228 , although this is not necessarily always the case.
- both the first and second restriction periods is sufficient to eliminate the mass registration condition. Consequently, registration requests 232 sent by members 212 of talkgroup C do not lead to the imposition of a third restriction period. Instead, site controller 200 responds to the registration requests 232 by registering the members 212 of talkgroup C and responding to the registration requests 232 with registration grants 234 . It should be understood that, in other situations, the site controller 200 may impose a third restriction period, and so on with additional talkgroups, until sufficient restrictions have been imposed to alleviate the mass registration condition.
- the site controller 200 sends an invitation message at the end of the first restriction period 224 .
- the invitation message 236 indicates to members 210 of talkgroup A that they may resume their individual registration requests.
- the time at which a restriction period ends may be different in different embodiments.
- the restriction period ends when a predetermined delay time has passed since the initiation of the restriction period.
- the restriction period may last for a predetermined delay time of 5-10 seconds.
- the use of a predetermined delay time imposes a reasonable upper bound on the length of a restriction period.
- the restriction message can include information identifying the length of the delay time to be used for the relevant restriction period. If, in a particular instance, the mass registration persists even after the delay time has expired and an invitation message has been sent, the site controller 200 can initiate a new restriction period.
- the site controller 200 may determine the end of the restriction period (and consequently the timing of the invitation message) by monitoring the traffic on the inbound control channel. For instance, the site controller 200 may end the restriction period when a predetermined silence time has passed during which the site controller 200 has not received any registration message on the inbound control channel. For example, the site controller 200 may end the restriction period when a silence time of 2-5 seconds has passed without receipt of any inbound registration message.
- the use of a silence time helps to ensure that the restriction period does not last substantially longer than necessary to register those members of talkgroups that have not been restricted, but last sufficiently long to at least temporarily alleviate the condition. As a result, it is not necessary for the site controller 200 to calculate in advance an estimate of the amount of time that will be required for registration of unrestricted talkgroups to be completed.
- the site controller 200 makes use of both a delay time and a silence time.
- the site controller may end the restriction period at the earlier of the following times: (a) when the delay time has passed since the initiation of the restriction period; and (b) when the silence time has passed since the receipt of a registration request.
- This places an upper bound on the length of a restriction period while allowing that the restriction period can be shortened if the inbound control channel is at least momentarily clear of registration request traffic.
- the duration of the silence time is selected to be shorter than the duration of the delay time.
- a substantial majority of registration requests received by the site controller 200 are likely to be requests from members of talkgroups that have not been subjected to a restriction message. However it is still possible to receive a registration request from a member of a talkgroup that is subject to a restriction period. In particular, some subscriber units may have been turned off or out of range, or served by a different site controller when the restriction message was sent. In some embodiments, registration requests sent by members of restricted talkgroups are processed as if the restriction were not in place, as such requests were likely to have been innocently sent. In other embodiments, the restriction message 222 may be re-sent.
- the site controller 200 After the site controller 200 sends an invitation 236 to the members 210 of talkgroup A, those subscriber units may submit registration requests 238 .
- the members 210 of talkgroup A avoid collision between their registration requests by introducing a random delay in the timing of their respective registration requests.
- the site controller 200 responds to the registration requests 238 by registering the members 210 of talkgroup A and responding to the registration requests 238 with registration grants 240 .
- the site controller 200 sends an invitation message 242 inviting the members 211 of talkgroup B to submit registration requests. Immediately or after a random delay, the members 211 of talkgroup B submit their registration requests 244 .
- the site controller 200 responds to the registration requests 244 by registering the members 211 of talkgroup B and responding to the registration requests 244 with registration grants 246 .
- FIG. 3 is a flow chart illustrating the operation of a site controller in accordance with some embodiments.
- the site controller receives a registration request from a subscriber unit that is a member of talkgroup A.
- the site controller determines whether the inbound control channel is in a mass registration condition. This determination may be made using one or more of various different techniques in different embodiments. For example, the determination that the inbound control channel is in a mass registration condition may be made by determining whether the rate of incoming registration request messages exceeds a predetermined threshold rate. In some embodiments, the determination may be made by predicting that a large amount of registration requests will be made at particular times, such as at the beginning of a work shift, or when a site controller has come back online after a period of being offline, or when service has been lost at a neighboring site controller. Other possibilities exist as well.
- step 306 the site controller responds to the registration request by registering the subscriber unit and responding to the registration request with a registration grant. If there is a mass registration condition, then in step 308 , the site controller determines whether talkgroup A is currently subject to a restriction period. If talkgroup A is not yet subject to a restriction period, then in step 310 , the site controller sends a restriction message to the members of talkgroup A, thereby initiating a restriction period for talkgroup A.
- the site controller is then responsible for identifying the end of the restriction period.
- the site controller determines whether the predetermined delay time has expired since the restriction message was sent in step 310 , and in step 314 , the site controller determines whether a predetermined silence time has expired since a registration request was last received by the site controller. If either of those conditions has occurred, the site controller progresses toward the sending of an invitation message.
- the site controller may wait until the end of the call before sending an invitation message.
- the site controller sends an invitation message to the members of talkgroup A.
- step 316 is not performed, and the site controller does not wait until the end of the call before sending an invitation message.
- members of talkgroup A can register and, if the call is in progress and if it relates to talkgroup A, those newly-registered members can join the call in progress.
- the site controller may then process the registration request and send a registration grant despite the imposition of the restriction period (see step 306 ). In other embodiments, the site controller may re-send the restriction message in a manner similar to that set forth in step 310 .
- restriction messages singled out particular talkgroups whose members were requested not to send registration requests.
- restriction messages request that all subscriber units except for a selected talkgroup refrain from sending registration requests.
- a site controller detects that an inbound control channel is in a mass registration condition. During the mass registration condition, the site controller receives a plurality of registration requests from subscribers over the inbound control channel. The registration requests include requests from subscribers associated with a plurality of different talkgroups. The site controller selects a first talkgroup from among the first plurality of talkgroups. The site controller then initiates a first restriction period by sending a first restriction message on an outbound control channel, wherein the first restriction message instructs subscribers who are not members of the first talkgroup to cease registration requests. During the first restriction period, the site controller registers members of the first talkgroup. During the first restriction period, a substantial majority of talkgroup members registered by the site controller may be members of the first talkgroup.
- the first restriction message is received at a subscriber unit. If the subscriber unit determines that it is not a member of the first talkgroup, it determines the expiration of the restriction period by identifying one of, or the earlier of, the following times: (a) when a predetermined delay time has passed since the initiation of the first restriction period; and (b) when a predetermined silence time has passed since the receipt of a registration acknowledgement on the outbound control channel. Only after the restriction period has expired, and assuming no further restriction period is established in the interim, the subscriber unit sends a registration request to the site controller on the inbound control channel.
- FIG. 4 is a schematic message flow diagram illustrating exemplary communications between a site controller 400 and talkgroup members during a mass registration condition in some embodiments.
- the schema of FIG. 4 should be interpreted as described above with respect to FIG. 2 .
- the site controller 400 receives registration requests 402 , 404 , and 406 from one or more members 410 of talkgroup A, members 411 of talkgroup B, and members 412 of talkgroup C, respectively.
- the site controller 400 selects one of the talkgroups from which it received a registration request. In this example, the site controller selects talkgroup A.
- the site controller 400 initiates a first restriction period 414 by sending a restriction message 408 on the outbound control channel.
- the restriction message 408 requests that registration during the first restriction period be restricted to members 410 of talkgroup A.
- the restriction message 408 may itself be a registration grant for one or more subscriber units that are members of talkgroup A.
- the restriction message may be a registration grant that makes use of a specialized opcode, or it may include particular flags or other information in the message payload that indicates that the registration grant is also a restriction message for subscriber units that are not members of talkgroup A.
- Such information in a registration grant that identifies the registration grant as a restriction message is referred to herein as a restriction code.
- the restriction message 408 further includes information identifying the selected talkgroup (in this example, talkgroup A) that is permitted to individually register its members during the restriction period.
- the restriction message 408 may indicate to the subscriber units that the associated talkgroup is registered with the site controller 400 .
- a restriction message may be sent several times to ensure receipt by members of the restricted talkgroups and/or the selected talkgroup A.
- members 410 of the selected talkgroup, talkgroup A continue to submit individual registration requests 416 to the site controller 400 .
- the site controller 400 registers the requesting members 410 of talkgroup A and confirms the registration by sending registration grants 418 to the respective subscriber units.
- each of the restricted subscriber units is responsible for determining the end of a restriction period.
- the time at which a restriction period ends may be different in different embodiments.
- the restriction period ends when a predetermined delay time has passed since the initiation of the restriction period.
- the restriction period may last for a predetermined delay time of 5-10 seconds.
- the use of a predetermined delay time imposes a reasonable upper bound on the length of a restriction period. If, in a particular instance, the mass registration persists even after the delay time has expired and an invitation message has been sent, the site controller 200 can initiate a new restriction period.
- the restriction message can include information identifying the length of the delay time to be used for the relevant restriction period.
- the subscriber units may determine the end of the restriction period (and consequently the time at which they are permitted to send registration requests) by monitoring the traffic on the outbound control channel. For instance, a subscriber unit may determine that the restriction period has ended when a predetermined silence time has passed during which the subscriber unit has not detected any registration grant sent on the outbound control channel. For example, a subscriber unit may determine that the restriction period has ended when a silence time of 2-5 seconds has passed without the detection of any outbound registration grant. The use of a silence time helps to ensure that the restriction period does not last substantially longer than necessary to register the members of the selected talkgroup.
- the subscriber units make use of both a delay time and a silence time. For example, a subscriber unit may determine that the restriction period has ended at the earlier of the following times: (a) when the delay time has passed since the initiation of the restriction period; and (b) when the silence time has passed since the receipt of a registration grant. This places an upper bound on the length of a restriction period while allowing that the restriction period can be shortened if the outbound control channel is at least momentarily clear of registration grant traffic. In such an embodiment, the duration of the silence time is selected to be shorter than the duration of the delay time.
- members 411 of talkgroup B and members 412 of talkgroup C determine that the first restriction period 414 has ended, they begin to send registration requests 420 and 422 , respectively.
- the subscriber units of talkgroup B 411 and talkgroup C 412 avoid collision between their registration requests by introducing a random delay in the timing of their respective registration requests.
- the imposition of the first restriction period 414 may be sufficient to alleviate the mass registration condition, in which case further restriction periods may not be necessary.
- the site controller 400 makes a new selection of a talkgroup from among the registration requests 420 and 422 that it has received.
- the site controller 400 selects talkgroup B.
- the site controller 400 then initiates a second restriction period 424 by sending a restriction message 426 on the outbound control channel, identifying talkgroup B as the selected talkgroup and restricting the remaining talkgroups (talkgroup C).
- the second restriction period 424 does not apply to members 410 of talkgroup A. This way, if the first restriction period 414 was not sufficiently long to permit registration of all members 410 of talkgroup A, those members can continue to submit registration requests during the second restriction period 424 .
- a substantial majority of registration requests received by the site controller 400 are likely to be requests from members of talkgroups A and B, which are the talkgroups that have been selected for registration during the restriction periods.
- the site controller 400 may receive a registration request from a member of another talkgroup during the restriction periods 414 and 424 , such as a member of talkgroup C 412 .
- some subscriber units that are members of talkgroup C 412 or other talkgroups that have not yet been selected may have been turned off, out of range, or served by a different site controller when the restriction messages 408 and/or 426 were sent.
- registration requests sent by members of such unselected talkgroups are processed as if the restriction were not in place, as such requests were likely to have been innocently sent.
- the site controller may re-send the restriction message.
- members 411 of the selected talkgroup, talkgroup B continue to submit registration requests 428 to the site controller 400 .
- the site controller 400 registers the requesting members 411 of talkgroup B and confirms the registration by sending registration grants 430 to the respective subscriber units.
- the members 412 of the restricted talkgroup C then make a determination of when the second restriction period 424 has ended. After the end of the second restriction period 424 , subscriber units 412 begin to send registration requests 432 . In some embodiments, the subscriber units 412 avoid collision between their registration requests 432 by introducing a random delay in the timing of their respective registration requests 432 . The use of such random delays is well understood by those skilled in the art.
- the site controller 400 registers the requesting members 412 of talkgroup C and confirms the registration by sending registration grants 434 to the respective subscriber units.
- FIG. 5 is a flowchart illustrating the operation of a site controller in some embodiments.
- the site controller receives a plurality of registration requests from subscriber units.
- the registration requests correspond to at least two different talkgroups.
- step 502 the site controller determines whether it is in a mass registration condition. This determination may be made using one or more of various different techniques in different embodiments, as set forth above.
- step 504 the site controller responds to the registration request by registering the subscriber units and responding to the registration requests with registration grants that do not include a restriction code. If the inbound control channel is in a mass registration condition, then in step 506 , the site controller selects a particular talkgroup from among the talkgroups associated with registration requests received in step 500 .
- the selection of a particular talkgroup may be conducted in various ways. For example, the selection may be random, it may depend on the order in which registration requests are received, it may depend on the relative number of registration requests being received from different talkgroups, it may depend on some predetermined priority between talkgroups, or it may depend on some combination of these factors. Other possibilities exist as well.
- the site controller in step 508 sends a restriction message that temporarily restricts registration to members of the selected talkgroup.
- the restriction message may be a registration grant message that includes a restriction code that identifies the registration grant as a restriction message, or may be a dedicated restriction message.
- the restriction message also includes information identifying the selected talkgroup. More than one restriction message may be sent out at step 508 .
- FIG. 6 is a flowchart illustrating the operation of a subscriber unit in some embodiments, such as the embodiments depicted in FIGS. 4 and 5 .
- the subscriber unit receives a restriction message on the outbound control channel, which in some embodiments, may also be a registration grant.
- the restriction message may not be addressed to that particular subscriber unit. Nevertheless, the subscriber unit processes the restriction message by determining in step 602 whether a restriction code is present in the restriction message. If no restriction code is present, the subscriber unit may then send its own registration request on the inbound control channel in step 604 according to known collision-avoidance techniques.
- the subscriber unit continues to process the restriction message by determining in step 606 whether it is a member of the selected talkgroup identified in the restriction message. If the subscriber unit is a member of the selected talkgroup, the subscriber unit may then proceed with sending its own registration request in step 604 .
- the subscriber unit recognizes that it is subject to a restriction period, and waits until the expiration of the restriction period before sending its own registration request.
- the subscriber unit determines in step 608 whether a predetermined delay time has expired. If so, the restriction period is considered to have ended, and the subscriber unit can send its own registration request in step 604 , perhaps using a collision-avoidance technique.
- the subscriber unit determines in step 610 whether a predetermined silence time has passed since a registration grant was last received over the outbound control channel. If so, the restriction period is considered to have ended, and the subscriber unit can send its own registration request in step 604 , perhaps using a collision-avoidance technique.
- a includes . . . a”, “contains . . . a” does not, without more constraints, preclude the existence of additional identical elements in the process, method, article, or apparatus that comprises, has, includes, contains the element.
- the terms “a” and “an” are defined as one or more unless explicitly stated otherwise herein.
- the terms “substantially”, “essentially”, “approximately”, “about” or any other version thereof, are defined as being close to as understood by one of ordinary skill in the art, and in one non-limiting embodiment the term is defined to be within 10%, in another embodiment within 5%, in another embodiment within 1% and in another embodiment within 0.5%.
- the term “coupled” as used herein is defined as connected, although not necessarily directly and not necessarily mechanically.
- a device or structure that is “configured” in a certain way is configured in at least that way, but may also be configured in ways that are not listed.
- processors such as microprocessors, digital signal processors, customized processors and field programmable gate arrays (FPGAs) and unique stored program instructions (including both software and firmware) that control the one or more processors to implement, in conjunction with certain non-processor circuits, some, most, or all of the functions of the method and/or apparatus described herein.
- processors or “processing devices” such as microprocessors, digital signal processors, customized processors and field programmable gate arrays (FPGAs) and unique stored program instructions (including both software and firmware) that control the one or more processors to implement, in conjunction with certain non-processor circuits, some, most, or all of the functions of the method and/or apparatus described herein.
- FPGAs field programmable gate arrays
- unique stored program instructions including both software and firmware
- an embodiment can be implemented as a computer-readable storage medium having computer readable code stored thereon for programming a computer (e.g., comprising a processor) to perform a method as described and claimed herein.
- Examples of such computer-readable storage mediums include, but are not limited to, a hard disk, a CD-ROM, an optical storage device, a magnetic storage device, a ROM (Read Only Memory), a PROM (Programmable Read Only Memory), an EPROM (Erasable Programmable Read Only Memory), an EEPROM (Electrically Erasable Programmable Read Only Memory) and a Flash memory.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Multimedia (AREA)
- Computer Security & Cryptography (AREA)
- Mobile Radio Communication Systems (AREA)
- Telephonic Communication Services (AREA)
Abstract
Description
- Trunked radio systems are one solution for permitting two-way radio communications, such as voice and data communications, not only between individual users equipped with subscriber radio units, but also among all active members of particular talkgroups. Conventional two-way radio systems permit group communications among radio users who tune in to a particular communications channel, such as a particular frequency, that has been assigned in advance. Trunked radio systems, on the other hand, do not require members of a talkgroup to select any particular communications channel in advance. Instead, communications channels are assigned only as they are needed. The assignment of communications channels is performed by a site controller. Users of subscriber units remain in wireless communication with a site controller over a duplex control channel, which is comprised of an inbound channel for communications to the site controller and an outbound channel for communications from the site controller to the subscriber units.
- When a communications channel is needed for talkgroup or individual communications, a request is made to the site controller over the inbound control channel. Over the outbound control channel, the site controller alerts the relevant subscriber units to the communications channel to be used.
- Subscriber units can be turned on or off, or they can enter and leave an area served by a particular site controller, and site controllers themselves can be in and out of service at various times. To keep track of which subscriber units are being served by which site controller, subscriber units engage in a registration process in which subscriber units send registration requests to a site controller and identify the talkgroup or groups with which they are affiliated. In turn, the site controller registers the presence of the subscriber units and confirms the registration by sending registration grants to the respective subscriber units. A site controller may also be affiliated with one or more relays that allow subscriber units to communicate with one another despite being served by different site controllers. Such communications may take place through the intermediary of a backend network.
- Trunked radio systems have several advantages over conventional radio systems, such as a more efficient allocation of the radio spectrum and greater flexibility in the assignment of subscriber units to multiple different talkgroups. However, the use of a trunked radio system poses other challenges. For example, it is possible for the control channel, which can be shared by numerous subscriber units, to be overloaded by radio traffic. Such a situation can arise when several subscriber units are attempting to send registration requests at the same time. When two subscriber units attempt to send messages, such as registration requests, on the same channel at the same time, it is often the case that neither message is intelligible. The two subscriber units whose requests have collided then need to make a new attempt to send their messages. It is known in the art for the subscriber units whose messages have collided to employ a random back-off routine and to make a new attempt to send the message after a random delay period has passed. Since both subscriber units are not likely to select the same random delay period, the messages are not likely to collide in the second attempt.
- The use of a random back-off routine works well during ordinary radio traffic conditions. However, on occasion, a situation can arise in which the amount of subscriber unit registration traffic is too high to be satisfactorily handled by only a random back-off routine. One such situation is a mass registration event, where some occurrence leads to a large number of registration requests to be sent at substantially the same time. For example, a situation may arise in which one site controller fails, leading many of the subscriber units that were formerly registered with that site controller to inundate neighboring site controllers with new registration requests.
- Accordingly, there is a need for an improved method and system for managing a mass registration scenario in a two-way radio system.
- The accompanying figures, where like reference numerals refer to identical or functionally similar elements throughout the separate views, together with the detailed description below, are incorporated in and form part of the specification, and serve to further illustrate embodiments of concepts that include the claimed invention, and explain various principles and advantages of those embodiments.
-
FIG. 1 is a schematic block diagram illustrating an architecture of a trunked radio system in accordance with some embodiments. -
FIG. 2 is a schematic message flow diagram illustrating exemplary communications between a site controller and talkgroup members in some embodiments. -
FIG. 3 is a flowchart illustrating an operation of a site controller in some embodiments. -
FIG. 4 is a schematic message flow diagram illustrating exemplary communications between a site controller and talkgroup members in some embodiments. -
FIG. 5 is a flowchart illustrating an operation of a site controller in some embodiments. -
FIG. 6 is a flowchart illustrating an operation of a subscriber unit in some embodiments. - Skilled artisans will appreciate that elements in the figures are illustrated for simplicity and clarity and have not necessarily been drawn to scale. For example, the dimensions of some of the elements in the figures may be exaggerated relative to other elements to help to improve understanding of embodiments of the present invention.
- The apparatus and method components have been represented where appropriate by conventional symbols in the drawings, showing only those specific details that are pertinent to understanding the embodiments of the present invention so as not to obscure the disclosure with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein.
- According to an embodiment described herein, a site controller detects that an inbound control channel is in a mass registration condition. During the mass registration condition, the site controller receives a plurality of registration requests over the inbound control channel. Among the requests are at least a first registration request from a member of a first talkgroup. In response to the first registration request, the site controller initiates a restriction period by sending a restriction message on an outbound control channel. The restriction message instructs members of the first talkgroup to cease registration requests. When the restriction period ends, the site controller sends an invitation message on the outbound control channel. The invitation message invites members of the first talkgroup to resume registration requests.
-
FIG. 1 is a schematic block diagram illustrating an architecture of a trunked radio system in accordance with some embodiments. The system includes asite controller 100 equipped with atransceiver 101 for conducting wireless communications with a plurality of subscriber units. Thetransceiver 101 may include several antennas for communications on different communications channels, including a duplex control channel that includes an inbound control channel for communications to the site controller and an outbound control channel for communications to the subscriber units. Thesite controller 100 includes acontrol module 102, which comprises a general- or special-purpose processor 103 and a non-transitory computer-readable memory 104 operatively coupled to theprocessor 103. Thememory 103 stores instructions executable by the processor and operative to perform the site controller steps described in further detail below. - In a further embodiment, a subscriber unit apparatus is provided. The subscriber unit may comprise a transceiver for communicating on an inbound control channel and an outbound control channel, and a processor coupled to a non-transitory computer-readable medium storing executable instructions that, when executed on the processor, are operative to (i) receive a restriction message on the outbound control channel, wherein the restriction message initiates a restriction period by instructing subscribers who are not members of the first talkgroup to cease registration requests; (ii) to determine that the subscriber unit is not a member of the first talkgroup; and in response to the determination that the subscriber unit is not a member of the first talkgroup, (iii) to determine the end of the restriction period, where the restriction period ends at the earlier of the following times: (a) when a predetermined delay time has passed since the initiation of the restriction period; and (b) when a predetermined silence time has passed since the receipt of a registration acknowledgement on the outbound control channel; and only after the expiration of the restriction period, to send a registration request from the subscriber unit on the inbound control channel.
- The
site controller 100 is in wireless communication with a plurality of subscriber units, such assubscriber units subscriber 110 is a member of talkgroup A,subscriber 111 is a member of talkgroup B, and subscriber 112 is a member of talkgroup C. A subscriber unit may be a member of different talkgroups or multiple talkgroups at different times, as illustrated bysubscriber unit 113, which can be a member either or both of talkgroup A or of talkgroup B. - In the exemplary embodiment of
FIG. 1 , thesite controller 100 is coupled with abackend network 120 to permit subscriber units registered withsite controller 100 to communicate over the backend network with other subscriber units being served by other site controllers. - Before they can be served by
site controller 100,subscriber units site controller 100 by sending registration messages tosite controller 100 over the inbound control channel identifying themselves and the talkgroups of which they are members. To complete the registration,site controller 100 sends registration grants to the respective subscriber units over the outbound control channel. - Under some conditions, a large number of subscriber units may attempt to send registration messages to
site controller 100 at substantially a same time. This leads to multiple collisions between messages on the inbound control channel. Many of these messages are likely to be unintelligible to thesite controller 100.Site controller 100 will be unable to register the subscriber units whose messages were not received or were unintelligible, and in turn,site controller 100 will be unable to send registration grants to the requesting subscriber units. Consequently, the subscriber units will attempt to re-send their registration requests, which will further increase the traffic on the inbound control channel. This situation is referred to herein as a mass registration condition. - A mass registration condition may arise from several possible scenarios. For example, if a site is temporarily out of service, a mass registration condition may arise when the site comes back online. A mass registration condition may arise when a large number of subscriber units are turned on at substantially the same time, or they all arrive in the vicinity of a site controller at substantially the same time. Such situations may arise when, for example, workers equipped with subscriber units begin their shift at the same time, or when rescue or law enforcement personnel arrive at a particular location at substantially the same time. A mass registration condition may arise when one site controller fails, and the subscriber units that were formerly registered with the failed site controller begin sending registration requests to nearby site controllers.
-
FIG. 2 is a schematic message flow diagram illustrating exemplary communications between asite controller 200 and subscriber units that are members of three talkgroups during a mass registration condition. Subscriber units that are members of talkgroup A are represented byentity 210, subscriber units that are members of talkgroup B are represented byentity 211, and subscriber units that are members of talkgroup C are represented byentity 212. Extrapolation of the principles described inFIG. 2 to situations involving any number of talkgroups will be apparent to one of ordinary skill in the art. - In
FIG. 2 , horizontal arrows are representative of messages exchanged between thesite controller 200 and the subscriber units. Leftward arrows represent one or more messages sent on the inbound control channel to thesite controller 200. Rightward arrows represent one or more messages sent on the outbound control channel by thesite controller 200. Messages sent by thecontroller 200 may typically be received by members of multiple talkgroups, even if they pertain only to a single talkgroup, but for efficiency of illustration, the arrows are shown to terminate at the talkgroup to which the outbound message is intended to pertain. It should also be noted that, for efficiency of conveying the concepts described herein, not every message exchanged between subscriber units and site controller is illustrated. Moreover, a single horizontal line may represent more than one message. - In
step 220, during a mass registration condition, thesite controller 200 receives at least one registration request frommembers 210 of talkgroup A. It should be noted that the received registration request or requests may be one of many attempted requests sent by members of talkgroups A, B, and C. However, many of the attempted registration requests may not be received bysite controller 200 due to the mass registration condition. - In response to the registration request received from a member of talkgroup A, the
site controller 200 sends arestriction message 222 on the outbound control channel. The restriction message instructs themembers 210 of talkgroup A to hold off temporarily on the sending of registration requests. By postponing registration requests from members of a particular talkgroup (in this example, talkgroup A), thesite controller 200 operates to alleviate the immediate demands on the inbound control channel. - The
restriction message 222 may be a separate dedicated message, the sole purpose of which is to convey the restriction period. In other embodiments, and to make the most efficient use of the control channel, therestriction message 222 may itself be a registration grant for a member of talkgroup A. For example, the restriction message may be a registration grant that makes use of a specialized opcode, or it may include particular flags or other information in the message payload that indicates that the registration grant is also a restriction message. Such information in a registration grant that identifies the registration grant as a restriction message is referred to herein as a restriction code. Moreover, therestriction message 222 may indicate to the subscriber units that the associated talkgroup is registered with thesite controller 200. A restriction message may be sent several times to ensure receipt by members of a restricted talkgroup. - The
restriction message 222 is sent at the beginning of afirst restriction period 224, during whichmembers 210 of talkgroup A hold off on sending registration requests.Members restriction message 222. As a result, those subscriber units may continue to attempt to send registration requests. For example, instep 226, one or more members of talkgroup B send registration requests to thesite controller 200. If the imposition of thefirst restriction period 224 has been sufficient to alleviate the mass registration condition, then thesite controller 200 may respond to the talkgroup B requests with ordinary registration grants. However, in the example illustrated inFIG. 2 , the mass registration condition persists despite the imposition of the first restriction period. - Since the mass registration condition persists when the
requests 226 are sent, thesite controller 200 initiates asecond restriction period 228 by sending arestriction message 230 that instructsmembers 211 of talkgroup B to hold off temporarily on the sending of registration requests. The imposition of thesecond restriction period 228 further alleviates the demands on the inbound control channel. As illustrated inFIG. 2 , thefirst restriction period 224 can overlap with thesecond restriction period 228, although this is not necessarily always the case. - In this example, the imposition of both the first and second restriction periods is sufficient to eliminate the mass registration condition. Consequently,
registration requests 232 sent bymembers 212 of talkgroup C do not lead to the imposition of a third restriction period. Instead,site controller 200 responds to the registration requests 232 by registering themembers 212 of talkgroup C and responding to the registration requests 232 with registration grants 234. It should be understood that, in other situations, thesite controller 200 may impose a third restriction period, and so on with additional talkgroups, until sufficient restrictions have been imposed to alleviate the mass registration condition. - As illustrated at
step 236, thesite controller 200 sends an invitation message at the end of thefirst restriction period 224. Theinvitation message 236 indicates tomembers 210 of talkgroup A that they may resume their individual registration requests. - The time at which a restriction period ends may be different in different embodiments. In some embodiments, the restriction period ends when a predetermined delay time has passed since the initiation of the restriction period. For example, the restriction period may last for a predetermined delay time of 5-10 seconds. The use of a predetermined delay time imposes a reasonable upper bound on the length of a restriction period. As an alternative to a predetermined delay time, the restriction message can include information identifying the length of the delay time to be used for the relevant restriction period. If, in a particular instance, the mass registration persists even after the delay time has expired and an invitation message has been sent, the
site controller 200 can initiate a new restriction period. - In some embodiments, the
site controller 200 may determine the end of the restriction period (and consequently the timing of the invitation message) by monitoring the traffic on the inbound control channel. For instance, thesite controller 200 may end the restriction period when a predetermined silence time has passed during which thesite controller 200 has not received any registration message on the inbound control channel. For example, thesite controller 200 may end the restriction period when a silence time of 2-5 seconds has passed without receipt of any inbound registration message. The use of a silence time helps to ensure that the restriction period does not last substantially longer than necessary to register those members of talkgroups that have not been restricted, but last sufficiently long to at least temporarily alleviate the condition. As a result, it is not necessary for thesite controller 200 to calculate in advance an estimate of the amount of time that will be required for registration of unrestricted talkgroups to be completed. - In some embodiments, the
site controller 200 makes use of both a delay time and a silence time. For example, the site controller may end the restriction period at the earlier of the following times: (a) when the delay time has passed since the initiation of the restriction period; and (b) when the silence time has passed since the receipt of a registration request. This places an upper bound on the length of a restriction period while allowing that the restriction period can be shortened if the inbound control channel is at least momentarily clear of registration request traffic. In such an embodiment, the duration of the silence time is selected to be shorter than the duration of the delay time. - During the restriction period, a substantial majority of registration requests received by the
site controller 200 are likely to be requests from members of talkgroups that have not been subjected to a restriction message. However it is still possible to receive a registration request from a member of a talkgroup that is subject to a restriction period. In particular, some subscriber units may have been turned off or out of range, or served by a different site controller when the restriction message was sent. In some embodiments, registration requests sent by members of restricted talkgroups are processed as if the restriction were not in place, as such requests were likely to have been innocently sent. In other embodiments, therestriction message 222 may be re-sent. - After the
site controller 200 sends aninvitation 236 to themembers 210 of talkgroup A, those subscriber units may submitregistration requests 238. In some embodiments, themembers 210 of talkgroup A avoid collision between their registration requests by introducing a random delay in the timing of their respective registration requests. Thesite controller 200 responds to the registration requests 238 by registering themembers 210 of talkgroup A and responding to the registration requests 238 with registration grants 240. - When the
second restriction period 228 ends, thesite controller 200 sends aninvitation message 242 inviting themembers 211 of talkgroup B to submit registration requests. Immediately or after a random delay, themembers 211 of talkgroup B submit their registration requests 244. Thesite controller 200 responds to the registration requests 244 by registering themembers 211 of talkgroup B and responding to the registration requests 244 with registration grants 246. -
FIG. 3 is a flow chart illustrating the operation of a site controller in accordance with some embodiments. Instep 302, the site controller receives a registration request from a subscriber unit that is a member of talkgroup A. - In
step 304, the site controller determines whether the inbound control channel is in a mass registration condition. This determination may be made using one or more of various different techniques in different embodiments. For example, the determination that the inbound control channel is in a mass registration condition may be made by determining whether the rate of incoming registration request messages exceeds a predetermined threshold rate. In some embodiments, the determination may be made by predicting that a large amount of registration requests will be made at particular times, such as at the beginning of a work shift, or when a site controller has come back online after a period of being offline, or when service has been lost at a neighboring site controller. Other possibilities exist as well. - If there is no mass registration condition, then in
step 306, the site controller responds to the registration request by registering the subscriber unit and responding to the registration request with a registration grant. If there is a mass registration condition, then instep 308, the site controller determines whether talkgroup A is currently subject to a restriction period. If talkgroup A is not yet subject to a restriction period, then instep 310, the site controller sends a restriction message to the members of talkgroup A, thereby initiating a restriction period for talkgroup A. - The site controller is then responsible for identifying the end of the restriction period. In
step 312, the site controller determines whether the predetermined delay time has expired since the restriction message was sent instep 310, and instep 314, the site controller determines whether a predetermined silence time has expired since a registration request was last received by the site controller. If either of those conditions has occurred, the site controller progresses toward the sending of an invitation message. In some embodiments, as illustrated instep 316, if there is a call in progress, the site controller may wait until the end of the call before sending an invitation message. Instep 318, the site controller sends an invitation message to the members of talkgroup A. In some embodiments,step 316 is not performed, and the site controller does not wait until the end of the call before sending an invitation message. In such embodiments, members of talkgroup A can register and, if the call is in progress and if it relates to talkgroup A, those newly-registered members can join the call in progress. - Returning to step 308, if a member of talkgroup A sends a registration request despite the restriction period already being imposed on talkgroup A, it is likely that the subscriber unit did not receive the restriction message. In some embodiments, the site controller may then process the registration request and send a registration grant despite the imposition of the restriction period (see step 306). In other embodiments, the site controller may re-send the restriction message in a manner similar to that set forth in
step 310. - In the embodiments described above the restriction messages singled out particular talkgroups whose members were requested not to send registration requests. In other embodiments, described below, restriction messages request that all subscriber units except for a selected talkgroup refrain from sending registration requests.
- According to an embodiment described herein, a site controller detects that an inbound control channel is in a mass registration condition. During the mass registration condition, the site controller receives a plurality of registration requests from subscribers over the inbound control channel. The registration requests include requests from subscribers associated with a plurality of different talkgroups. The site controller selects a first talkgroup from among the first plurality of talkgroups. The site controller then initiates a first restriction period by sending a first restriction message on an outbound control channel, wherein the first restriction message instructs subscribers who are not members of the first talkgroup to cease registration requests. During the first restriction period, the site controller registers members of the first talkgroup. During the first restriction period, a substantial majority of talkgroup members registered by the site controller may be members of the first talkgroup.
- The first restriction message is received at a subscriber unit. If the subscriber unit determines that it is not a member of the first talkgroup, it determines the expiration of the restriction period by identifying one of, or the earlier of, the following times: (a) when a predetermined delay time has passed since the initiation of the first restriction period; and (b) when a predetermined silence time has passed since the receipt of a registration acknowledgement on the outbound control channel. Only after the restriction period has expired, and assuming no further restriction period is established in the interim, the subscriber unit sends a registration request to the site controller on the inbound control channel.
-
FIG. 4 is a schematic message flow diagram illustrating exemplary communications between asite controller 400 and talkgroup members during a mass registration condition in some embodiments. The schema ofFIG. 4 should be interpreted as described above with respect toFIG. 2 . - The
site controller 400 receivesregistration requests more members 410 of talkgroup A,members 411 of talkgroup B, andmembers 412 of talkgroup C, respectively. Thesite controller 400 then selects one of the talkgroups from which it received a registration request. In this example, the site controller selects talkgroup A. Instep 408, thesite controller 400 initiates afirst restriction period 414 by sending arestriction message 408 on the outbound control channel. Therestriction message 408 requests that registration during the first restriction period be restricted tomembers 410 of talkgroup A. - The
restriction message 408 may itself be a registration grant for one or more subscriber units that are members of talkgroup A. For example, the restriction message may be a registration grant that makes use of a specialized opcode, or it may include particular flags or other information in the message payload that indicates that the registration grant is also a restriction message for subscriber units that are not members of talkgroup A. Such information in a registration grant that identifies the registration grant as a restriction message is referred to herein as a restriction code. Therestriction message 408 further includes information identifying the selected talkgroup (in this example, talkgroup A) that is permitted to individually register its members during the restriction period. Moreover, therestriction message 408 may indicate to the subscriber units that the associated talkgroup is registered with thesite controller 400. A restriction message may be sent several times to ensure receipt by members of the restricted talkgroups and/or the selected talkgroup A. - During the
first restriction period 414,members 410 of the selected talkgroup, talkgroup A, continue to submitindividual registration requests 416 to thesite controller 400. Thesite controller 400 registers the requestingmembers 410 of talkgroup A and confirms the registration by sendingregistration grants 418 to the respective subscriber units. - In some embodiments, each of the restricted subscriber units is responsible for determining the end of a restriction period. The time at which a restriction period ends may be different in different embodiments. In some embodiments, the restriction period ends when a predetermined delay time has passed since the initiation of the restriction period. For example, the restriction period may last for a predetermined delay time of 5-10 seconds. The use of a predetermined delay time imposes a reasonable upper bound on the length of a restriction period. If, in a particular instance, the mass registration persists even after the delay time has expired and an invitation message has been sent, the
site controller 200 can initiate a new restriction period. As an alternative to a predetermined delay time, the restriction message can include information identifying the length of the delay time to be used for the relevant restriction period. - In some embodiments, the subscriber units may determine the end of the restriction period (and consequently the time at which they are permitted to send registration requests) by monitoring the traffic on the outbound control channel. For instance, a subscriber unit may determine that the restriction period has ended when a predetermined silence time has passed during which the subscriber unit has not detected any registration grant sent on the outbound control channel. For example, a subscriber unit may determine that the restriction period has ended when a silence time of 2-5 seconds has passed without the detection of any outbound registration grant. The use of a silence time helps to ensure that the restriction period does not last substantially longer than necessary to register the members of the selected talkgroup. As a result, it is not necessary for the
site controller 400 or for the subscriber units to calculate in advance an estimate of the amount of time that will be required for registration of members of the selected talkgroup to be completed. Subscriber units that have already registered with thesite controller 400 need not dedicate any resources to determining an end to the restriction period. - In some embodiments, the subscriber units make use of both a delay time and a silence time. For example, a subscriber unit may determine that the restriction period has ended at the earlier of the following times: (a) when the delay time has passed since the initiation of the restriction period; and (b) when the silence time has passed since the receipt of a registration grant. This places an upper bound on the length of a restriction period while allowing that the restriction period can be shortened if the outbound control channel is at least momentarily clear of registration grant traffic. In such an embodiment, the duration of the silence time is selected to be shorter than the duration of the delay time.
- Once
members 411 of talkgroup B andmembers 412 of talkgroup C determine that thefirst restriction period 414 has ended, they begin to sendregistration requests talkgroup B 411 andtalkgroup C 412 avoid collision between their registration requests by introducing a random delay in the timing of their respective registration requests. - In some situations, the imposition of the
first restriction period 414 may be sufficient to alleviate the mass registration condition, in which case further restriction periods may not be necessary. However, in the example illustrated inFIG. 4 , the inbound control channel is still in a mass registration condition despite thefirst restriction period 414. As a result, thesite controller 400 makes a new selection of a talkgroup from among the registration requests 420 and 422 that it has received. In this example, thesite controller 400 selects talkgroup B. Thesite controller 400 then initiates asecond restriction period 424 by sending arestriction message 426 on the outbound control channel, identifying talkgroup B as the selected talkgroup and restricting the remaining talkgroups (talkgroup C). - In some embodiments, the
second restriction period 424 does not apply tomembers 410 of talkgroup A. This way, if thefirst restriction period 414 was not sufficiently long to permit registration of allmembers 410 of talkgroup A, those members can continue to submit registration requests during thesecond restriction period 424. - During the
first restriction period 414 andsecond restriction period 424, a substantial majority of registration requests received by thesite controller 400 are likely to be requests from members of talkgroups A and B, which are the talkgroups that have been selected for registration during the restriction periods. However it is still possible for thesite controller 400 to receive a registration request from a member of another talkgroup during therestriction periods talkgroup C 412. In particular, some subscriber units that are members oftalkgroup C 412 or other talkgroups that have not yet been selected may have been turned off, out of range, or served by a different site controller when therestriction messages 408 and/or 426 were sent. In some embodiments, registration requests sent by members of such unselected talkgroups are processed as if the restriction were not in place, as such requests were likely to have been innocently sent. In other embodiments, the site controller may re-send the restriction message. - During the
second restriction period 424,members 411 of the selected talkgroup, talkgroup B, continue to submitregistration requests 428 to thesite controller 400. Thesite controller 400 registers the requestingmembers 411 of talkgroup B and confirms the registration by sendingregistration grants 430 to the respective subscriber units. - The
members 412 of the restricted talkgroup C then make a determination of when thesecond restriction period 424 has ended. After the end of thesecond restriction period 424,subscriber units 412 begin to sendregistration requests 432. In some embodiments, thesubscriber units 412 avoid collision between theirregistration requests 432 by introducing a random delay in the timing of their respective registration requests 432. The use of such random delays is well understood by those skilled in the art. Thesite controller 400 registers the requestingmembers 412 of talkgroup C and confirms the registration by sendingregistration grants 434 to the respective subscriber units. -
FIG. 5 is a flowchart illustrating the operation of a site controller in some embodiments. Instep 500, the site controller receives a plurality of registration requests from subscriber units. The registration requests correspond to at least two different talkgroups. - In
step 502, the site controller determines whether it is in a mass registration condition. This determination may be made using one or more of various different techniques in different embodiments, as set forth above. - If there is no mass registration condition, then in
step 504, the site controller responds to the registration request by registering the subscriber units and responding to the registration requests with registration grants that do not include a restriction code. If the inbound control channel is in a mass registration condition, then instep 506, the site controller selects a particular talkgroup from among the talkgroups associated with registration requests received instep 500. - The selection of a particular talkgroup may be conducted in various ways. For example, the selection may be random, it may depend on the order in which registration requests are received, it may depend on the relative number of registration requests being received from different talkgroups, it may depend on some predetermined priority between talkgroups, or it may depend on some combination of these factors. Other possibilities exist as well.
- Having selected a particular talkgroup, the site controller in
step 508 sends a restriction message that temporarily restricts registration to members of the selected talkgroup. As set forth above, the restriction message may be a registration grant message that includes a restriction code that identifies the registration grant as a restriction message, or may be a dedicated restriction message. The restriction message also includes information identifying the selected talkgroup. More than one restriction message may be sent out atstep 508. -
FIG. 6 is a flowchart illustrating the operation of a subscriber unit in some embodiments, such as the embodiments depicted inFIGS. 4 and 5 . Instep 600, the subscriber unit receives a restriction message on the outbound control channel, which in some embodiments, may also be a registration grant. The restriction message may not be addressed to that particular subscriber unit. Nevertheless, the subscriber unit processes the restriction message by determining instep 602 whether a restriction code is present in the restriction message. If no restriction code is present, the subscriber unit may then send its own registration request on the inbound control channel instep 604 according to known collision-avoidance techniques. - If the restriction message does include a restriction code, the subscriber unit continues to process the restriction message by determining in
step 606 whether it is a member of the selected talkgroup identified in the restriction message. If the subscriber unit is a member of the selected talkgroup, the subscriber unit may then proceed with sending its own registration request instep 604. - If, on the other hand, the subscriber unit is not a member of the selected talkgroup identified in the restriction message, then the subscriber unit recognizes that it is subject to a restriction period, and waits until the expiration of the restriction period before sending its own registration request. To determine whether the restriction period has expired, the subscriber unit determines in
step 608 whether a predetermined delay time has expired. If so, the restriction period is considered to have ended, and the subscriber unit can send its own registration request instep 604, perhaps using a collision-avoidance technique. - If the delay time has not expired, the subscriber unit determines in
step 610 whether a predetermined silence time has passed since a registration grant was last received over the outbound control channel. If so, the restriction period is considered to have ended, and the subscriber unit can send its own registration request instep 604, perhaps using a collision-avoidance technique. - In the foregoing specification, specific embodiments have been described. However, one of ordinary skill in the art appreciates that various modifications and changes can be made without departing from the scope of the invention as set forth in the claims below. Accordingly, the specification and figures are to be regarded in an illustrative rather than a restrictive sense, and all such modifications are intended to be included within the scope of present teachings.
- The benefits, advantages, solutions to problems, and any element(s) that may cause any benefit, advantage, or solution to occur or become more pronounced are not to be construed as a critical, required, or essential features or elements of any or all the claims. The invention is defined solely by the appended claims including any amendments made during the pendency of this application and all equivalents of those claims as issued.
- Moreover in this document, relational terms such as first and second, top and bottom, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. The terms “comprises,” “comprising,” “has”, “having,” “includes”, “including,” “contains”, “containing” or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises, has, includes, contains a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. An element proceeded by “comprises . . . a”, “has . . . a”, “includes . . . a”, “contains . . . a” does not, without more constraints, preclude the existence of additional identical elements in the process, method, article, or apparatus that comprises, has, includes, contains the element. The terms “a” and “an” are defined as one or more unless explicitly stated otherwise herein. The terms “substantially”, “essentially”, “approximately”, “about” or any other version thereof, are defined as being close to as understood by one of ordinary skill in the art, and in one non-limiting embodiment the term is defined to be within 10%, in another embodiment within 5%, in another embodiment within 1% and in another embodiment within 0.5%. The term “coupled” as used herein is defined as connected, although not necessarily directly and not necessarily mechanically. A device or structure that is “configured” in a certain way is configured in at least that way, but may also be configured in ways that are not listed.
- It will be appreciated that some embodiments may be comprised of one or more generic or specialized processors (or “processing devices”) such as microprocessors, digital signal processors, customized processors and field programmable gate arrays (FPGAs) and unique stored program instructions (including both software and firmware) that control the one or more processors to implement, in conjunction with certain non-processor circuits, some, most, or all of the functions of the method and/or apparatus described herein. Alternatively, some or all functions could be implemented by a state machine that has no stored program instructions, or in one or more application specific integrated circuits (ASICs), in which each function or some combinations of certain of the functions are implemented as custom logic. Of course, a combination of the two approaches could be used.
- Moreover, an embodiment can be implemented as a computer-readable storage medium having computer readable code stored thereon for programming a computer (e.g., comprising a processor) to perform a method as described and claimed herein. Examples of such computer-readable storage mediums include, but are not limited to, a hard disk, a CD-ROM, an optical storage device, a magnetic storage device, a ROM (Read Only Memory), a PROM (Programmable Read Only Memory), an EPROM (Erasable Programmable Read Only Memory), an EEPROM (Electrically Erasable Programmable Read Only Memory) and a Flash memory. Further, it is expected that one of ordinary skill, notwithstanding possibly significant effort and many design choices motivated by, for example, available time, current technology, and economic considerations, when guided by the concepts and principles disclosed herein will be readily capable of generating such software instructions and programs and ICs with minimal experimentation.
- The Abstract of the Disclosure is provided to allow the reader to quickly ascertain the nature of the technical disclosure. It is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. In addition, in the foregoing Detailed Description, it can be seen that various features are grouped together in various embodiments for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed embodiments require more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter lies in less than all features of a single disclosed embodiment. Thus the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separately claimed subject matter.
Claims (20)
Priority Applications (8)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/090,341 US9271253B2 (en) | 2013-11-26 | 2013-11-26 | Method and system for managing mass registration scenario in two-way radio system |
DE112014005414.3T DE112014005414B4 (en) | 2013-11-26 | 2014-11-19 | Method and system for handling a bulk registration scenario in a two-way radio system |
CN201480064783.8A CN105794236B (en) | 2013-11-26 | 2014-11-19 | Manage the method and system of the magnanimity registration scene in two-way radio system |
PCT/US2014/066326 WO2015080914A1 (en) | 2013-11-26 | 2014-11-19 | Method and system for managing mass registration scenario in two-way radio system |
GB1608802.3A GB2535095B (en) | 2013-11-26 | 2014-11-19 | Method and system for managing mass registration scenario in two-way radio system |
AU2014355008A AU2014355008B2 (en) | 2013-11-26 | 2014-11-19 | Method and system for managing mass registration scenario in two-way radio system |
CA2931199A CA2931199C (en) | 2013-11-26 | 2014-11-19 | Method and system for managing mass registration scenario in two-way radio system |
US14/927,764 US9344988B2 (en) | 2013-11-26 | 2015-10-30 | Method and system for managing mass registration scenario in two-way radio system |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/090,341 US9271253B2 (en) | 2013-11-26 | 2013-11-26 | Method and system for managing mass registration scenario in two-way radio system |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/927,764 Division US9344988B2 (en) | 2013-11-26 | 2015-10-30 | Method and system for managing mass registration scenario in two-way radio system |
Publications (2)
Publication Number | Publication Date |
---|---|
US20150148034A1 true US20150148034A1 (en) | 2015-05-28 |
US9271253B2 US9271253B2 (en) | 2016-02-23 |
Family
ID=52103166
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/090,341 Active 2034-06-24 US9271253B2 (en) | 2013-11-26 | 2013-11-26 | Method and system for managing mass registration scenario in two-way radio system |
US14/927,764 Active US9344988B2 (en) | 2013-11-26 | 2015-10-30 | Method and system for managing mass registration scenario in two-way radio system |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/927,764 Active US9344988B2 (en) | 2013-11-26 | 2015-10-30 | Method and system for managing mass registration scenario in two-way radio system |
Country Status (7)
Country | Link |
---|---|
US (2) | US9271253B2 (en) |
CN (1) | CN105794236B (en) |
AU (1) | AU2014355008B2 (en) |
CA (1) | CA2931199C (en) |
DE (1) | DE112014005414B4 (en) |
GB (1) | GB2535095B (en) |
WO (1) | WO2015080914A1 (en) |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20160183066A1 (en) * | 2014-12-19 | 2016-06-23 | Iridium Satellite Llc | Scanning talkgroups |
US9402166B1 (en) * | 2015-01-07 | 2016-07-26 | Motorola Solutions, Inc. | Method and apparatus for assigning a talk group to a radio within a communication system |
CN114979982A (en) * | 2022-04-13 | 2022-08-30 | 中移互联网有限公司 | Message issuing method and device, electronic equipment and storage medium |
Families Citing this family (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9277428B2 (en) * | 2014-04-29 | 2016-03-01 | Motorola Solutions, Inc. | Method and apparatus for responding to a potential mass random access event |
US10021588B1 (en) | 2017-05-04 | 2018-07-10 | Motorola Solutions, Inc. | Methods and systems for reducing inbound request traffic in a wireless network |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5923742A (en) * | 1997-02-14 | 1999-07-13 | At&T Grp. | System and method for detecting mass addressing events |
US20130195081A1 (en) * | 2011-09-29 | 2013-08-01 | Qualcomm Incorporated | Collision reduction mechanisms for wireless communication networks |
US20150119034A1 (en) * | 2013-10-31 | 2015-04-30 | At&T Mobility Ii, Llc | Method and system for managing wireless access to a communication system |
Family Cites Families (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5097499A (en) | 1990-08-22 | 1992-03-17 | At&T Bell Laboratories | Autonomous registration overload control for cellular mobile radio systems |
US5574728A (en) * | 1995-06-27 | 1996-11-12 | Motorola, Inc. | Methods of terminal registration |
US5946620A (en) | 1997-07-25 | 1999-08-31 | Motorola, Inc. | Method for subscriber registration in a radio communication system |
US6119017A (en) | 1997-11-25 | 2000-09-12 | Motorola, Inc. | Method of registration in a communication system |
DE60036731T2 (en) | 2000-06-14 | 2008-07-17 | Nokia Corp. | METHOD AND DEVICE FOR IMPLEMENTING POSITION REGISTRATION |
JP3466999B2 (en) | 2000-07-13 | 2003-11-17 | キヤノン株式会社 | Wireless communication system, wireless communication device, and control method thereof |
EP2183231B1 (en) * | 2007-07-24 | 2019-02-20 | Mobileum, Inc. | Testing of roaming transactions |
CN102045810B (en) * | 2009-10-09 | 2014-01-08 | 华为技术有限公司 | Method, device and system for accessing machine type communication terminal equipment to network |
US9253798B2 (en) | 2010-02-12 | 2016-02-02 | Interdigital Patent Holdings, Inc. | Method and apparatus for optimizing uplink random access channel transmission |
CN102238629A (en) * | 2010-05-07 | 2011-11-09 | 华为技术有限公司 | Access control method for machine type communication, equipment and communication system |
CN102404792A (en) * | 2010-09-14 | 2012-04-04 | 中兴通讯股份有限公司 | Control method and system of overload |
KR20120099568A (en) * | 2011-01-18 | 2012-09-11 | 삼성전자주식회사 | Method and appratus for measuring inteference from in-device communication module in wireless communication system |
-
2013
- 2013-11-26 US US14/090,341 patent/US9271253B2/en active Active
-
2014
- 2014-11-19 CA CA2931199A patent/CA2931199C/en active Active
- 2014-11-19 CN CN201480064783.8A patent/CN105794236B/en active Active
- 2014-11-19 GB GB1608802.3A patent/GB2535095B/en active Active
- 2014-11-19 AU AU2014355008A patent/AU2014355008B2/en active Active
- 2014-11-19 DE DE112014005414.3T patent/DE112014005414B4/en active Active
- 2014-11-19 WO PCT/US2014/066326 patent/WO2015080914A1/en active Application Filing
-
2015
- 2015-10-30 US US14/927,764 patent/US9344988B2/en active Active
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5923742A (en) * | 1997-02-14 | 1999-07-13 | At&T Grp. | System and method for detecting mass addressing events |
US20130195081A1 (en) * | 2011-09-29 | 2013-08-01 | Qualcomm Incorporated | Collision reduction mechanisms for wireless communication networks |
US20150119034A1 (en) * | 2013-10-31 | 2015-04-30 | At&T Mobility Ii, Llc | Method and system for managing wireless access to a communication system |
Cited By (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20160183066A1 (en) * | 2014-12-19 | 2016-06-23 | Iridium Satellite Llc | Scanning talkgroups |
US9525982B2 (en) * | 2014-12-19 | 2016-12-20 | Iridium Satellite Llc | Scanning talkgroups |
US20170064744A1 (en) * | 2014-12-19 | 2017-03-02 | Iridium Satellite Llc | Scanning talkgroups |
US9807805B2 (en) * | 2014-12-19 | 2017-10-31 | Iridium Satellite Llc | Scanning talkgroups |
US10034328B2 (en) | 2014-12-19 | 2018-07-24 | Iridium Satellite Llc | Scanning talkgroups |
US9402166B1 (en) * | 2015-01-07 | 2016-07-26 | Motorola Solutions, Inc. | Method and apparatus for assigning a talk group to a radio within a communication system |
CN114979982A (en) * | 2022-04-13 | 2022-08-30 | 中移互联网有限公司 | Message issuing method and device, electronic equipment and storage medium |
Also Published As
Publication number | Publication date |
---|---|
DE112014005414T5 (en) | 2016-08-04 |
CA2931199A1 (en) | 2015-06-04 |
US9271253B2 (en) | 2016-02-23 |
US9344988B2 (en) | 2016-05-17 |
GB2535095A (en) | 2016-08-10 |
CN105794236A (en) | 2016-07-20 |
CN105794236B (en) | 2018-11-30 |
GB2535095B (en) | 2019-10-23 |
CA2931199C (en) | 2018-03-13 |
AU2014355008B2 (en) | 2017-02-02 |
AU2014355008A1 (en) | 2016-06-02 |
DE112014005414B4 (en) | 2021-07-01 |
US20160081052A1 (en) | 2016-03-17 |
WO2015080914A1 (en) | 2015-06-04 |
GB201608802D0 (en) | 2016-07-06 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US9344988B2 (en) | Method and system for managing mass registration scenario in two-way radio system | |
US10123350B2 (en) | Communication device and wireless communication system for handling random access procedure | |
US10028150B2 (en) | Method and system for contending for channel of unlicensed frequency band, and apparatus | |
US20180167977A1 (en) | Ofdma contention method and access point | |
EP2166809B1 (en) | Method and related device of scheduling request behavior in a wireless communication system | |
CN102067651B (en) | Apparatus for multicast transmissions in wireless local area networks | |
WO2017117990A1 (en) | Random access method, random access device, and terminal | |
US10462827B2 (en) | Random access method and apparatus | |
US10820350B2 (en) | Data transmission method and device | |
EP3595395B1 (en) | User equipment and method | |
EP3277045A1 (en) | Method and device for preempting transmission resources on unlicensed carriers | |
TWI575989B (en) | Wireless communication system, method and device under contention-based protocol | |
US9801005B2 (en) | Method of period allocation for medium and wireless communication system thereof | |
CA2899549C (en) | Methods and systems for talkgroup-state-dependent routing of group data | |
EP2903364B1 (en) | Prioritising requests for communication resources for device to device wireless communication | |
US8917709B2 (en) | Scheduled absence on a wireless local area network | |
CN113676297B (en) | Multi-card UE data transmission method and device, storage medium, user equipment and base station | |
US20160241650A1 (en) | Method, apparatus and system for requesting association | |
CN113632579A (en) | System and method for reducing delay of timer-based transmissions on a shared carrier | |
CN103327640A (en) | Ordering method and device of multicast medium based on competition in wireless local area network |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: MOTOROLA SOLUTIONS, INC., ILLINOIS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:ROUSSEV, ALEXANDER D.;BOHN, THOMAS B.;SIGNING DATES FROM 20131121 TO 20131125;REEL/FRAME:031678/0742 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 4 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 8TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1552); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 8 |