Group Call Management
Claim Score by NHIP
Abstract
Embodiments of the present invention relate to the coordination of group calls involving mobile terminals in telecommunications networks. In one aspect, embodiments of the invention provide a method of managing a group call involving a plurality of mobile communications devices, said plurality of mobile communications devices being registered with a telecommunications network via a serving node, the serving node being operable to transceive data to and from a plurality of radio access nodes so as to communicate with said registered mobile communications devices, in which at least a first of said radio access nodes has established a data communications channel with a mobile communications device of the plurality for conducting the group call, the method comprising: identifying a radio access node adjacent the first radio access node; defining the Group Call Area on basis of the first and adjacent radio access nodes; and establishing a signalling channel within a cell corresponding to said adjacent radio access node, said signalling channel having an identifier corresponding to the Group Call Area. The radio access nodes, or base stations, that have established a data communications channel with the mobile communications device have traffic and signalling channels established therein and are marked as an active cell of the Group Call Area; according to embodiments of the invention, base stations adjacent the active base station are added to the Group Call Area and signalling channels are established in these adjacent cells. Each signalling channel has an identifier corresponding to the Group Call Area. This method of channel allocation and deallocation provides a solution to the problem in the prior art in which channels have to be created as a mobile station moves into a new cell; by contrast, and because a signalling channel in any potential "next" cell has already been established, it is relatively straightforward to allocate a traffic channel therein.

Term
Projected expiry 20 November 2030.
- Priority and filed
- Published
- Today
- Projected expiry
25 claims: 5 independent, 20 dependent
- 1Broadest claimClaim Score 65, broad(NHIP)A method of setting up a call group for participation in a group call by a plurality of mobile devices in a mobile telecommunications network, the mobile telecommunications network comprising a serving node operable to transceive data to and from the mobile telecommunications devices, the method comprising:receiving, at a serving node, data indicative of a group identifier from a said mobile terminal registered with the mobile telecommunications network;and defining a Group Call Area using the received group identifier, the defined Group Call Area being accessible by the serving node so as to enable the serving node to discriminate one call group registered with said telecommunications network from another call group registered with said telecommunications network.
- 9A method of managing a group call involving a plurality of mobile communications devices, said plurality of mobile communications devices being registered with a telecommunications network via a serving node, the serving node being operable to transceive data to and from a plurality of radio access nodes so as to communicate with said registered mobile communications devices, in which at least a first of said radio access nodes has established a data communications channel with a mobile communications device of the plurality for conducting the group call, the method comprising:identifying a radio access node adjacent the first radio access node;defining the Group Call Area on basis of the first and adjacent radio access nodes;and establishing a signalling channel within a cell corresponding to said adjacent radio access node, said signalling channel having an identifier corresponding to the Group Call Area.
- 13A method of coordinating a plurality of group calls in a mobile telecommunications network, each said plurality of group calls involving a plurality of mobile devices, the mobile telecommunications network comprising a serving node operable to transceive data to and from at least some of a first set of mobile telecommunications devices, and to transceive data to and from at least some of a second set of mobile telecommunications devices, each set being involved in respective first and second group calls, each of the first and second group calls having the same group number and different Group Call Areas associated therewith, the method comprising:receiving a trigger indicating a requirement for handover in respect of a mobile telecommunications device, said mobile telecommunications device being a member of one of the first or second sets of mobile telecommunications devices;receiving signalling data from said mobile telecommunications device indicating membership of a respective Group Call Area;and joining said mobile telecommunications device to whichever group call corresponds to the indicated Group Call Area.
- 15A network node for setting up a call group for participation in a group call by a plurality of mobile devices in a mobile telecommunications network, the mobile telecommunications network comprising a serving node operable to transceive data to and from the mobile telecommunications devices, the network node comprising:an interface arranged to receive data indicative of a group identifier from a said mobile terminal registered with the mobile telecommunications network;and a processing system arranged to define a Group Call Area using the received group identifier, wherein the network node is arranged to provide the serving node with access to the defined Group Call Area so as to enable the serving node to discriminate one call group registered with said telecommunications network from another call group registered with said telecommunications network.
- 20A group call management system for managing a group call involving a plurality of mobile communications devices, said plurality of mobile communications devices being registered with a telecommunications network via a serving node, the serving node being operable to transceive data to and from a plurality of radio access nodes so as to communicate with said registered mobile communications devices, in which at least a first of said radio access nodes has established a data communications channel with a mobile communications device of the plurality for conducting the group call, the group call management system comprising:a network node arranged to identify a radio access node adjacent the first radio access node in response to a service request message identifying the first radio access node;and means for configuring the Group Call Area on basis of the first and adjacent radio access nodes, wherein at least some said adjacent radio access nodes are arranged to establish a signalling channel, said signalling channel having an identifier corresponding to the Group Call Area.
Independent claims5
55 paragraphs in 5 sections, as filed
FIELD OF THE INVENTION
The present invention relates to mobile telecommunications networks and to the coordination of group calls involving mobile terminals operating in such networks; embodiments of the invention are particularly, but not exclusively, suited to coordinating group calls when members of the group move between cells of the mobile network.
BACKGROUND OF THE INVENTION
Conventional mobile telecommunications networks, for example, digital cellular telecommunication networks according to the GSM Standard (Global System for Mobile Communications) provide voice broadcast services that permit a subscriber to initiate a group broadcast call directed to a group of other subscribers. Such voice broadcast service for GSM systems is specified in GSM Standard <b>03</b>.<b>68</b> and a related GSM Standard, namely GSM 03.69.
Typically, a particular group is identified by a group ID. A common control channel (for example the notification channel NCH in GSM) broadcasts a notification message including the group ID and a description of the channel being used for the group call in the network. Thus, users having the correct group ID stored in their mobile terminals, for example stored in the SIM (Subscriber Identity Module) card of a GSM mobile unit, can recognize the notification message, and can then connect to the group call by tuning to the channel described in the notification message. Furthermore in conventional Voice Group Call Service (VGCS) systems a given user can request and obtain an uplink channel, thereby permitting the user to speak to the group. A given mobile user must have a subscription with the group call service provider in order to be permitted to initiate a group call or participate in a group call.
Group call attributes including, for example, a listing of the cells in which the group call is broadcasted (the Group Call Area) are conventionally compiled in a separate network node database, for example the Group Call Register (GCR) in GSM networks. The group call register is typically associated with a Mobile Switching Centre (MSC) in GSM systems.
A particular problem is encountered with group calls when multiple group calls, each having the same group ID, are conducted within overlapping cells. In one conventional arrangement, a mobile station wanting to join a group call will select whichever of the notification broadcast messages that are broadcast on the notification channel in the cell is first received by the mobile device, so that selection of a group to join can be viewed as random. In relation to mobile devices that are already engaged in a group call at the time of moving into an overlapping cell, International patent application having publication number WO0131964 describes a mechanism by which these groups will be merged so as to form a single group call (with a larger number of participants), whilst other known mechanisms constrain mobile devices to remain with the group to which they were associated prior to moving into the cell. In all of these configurations, there is no means of intelligently selecting between group calls: selection is either performed randomly, or hard wired based on initial group designations, or not possible. In addition there is no means of restricting members of a group call: provided a mobile user has a subscription with the group call service provider, its terminal can join a group call.
Another problem is encountered when mobile devices move between cells: subscribers of conventional group call services are typically allowed to move from cell to cell while remaining in the group call, assuming that the group call is broadcast in each new cell into which the subscriber roams. However, if the group call is not being broadcasted in the new cell, then the group call will no longer be available to the subscriber. Further, changing cells often requires a short interruption of the subscriber's reception of the group call until the subscriber's mobile terminal has listened to the notification channel in the new cell and tuned to the proper group call channel in the new cell.
SUMMARY OF THE INVENTION
In accordance with a first aspect of the present invention there is provided a method of setting up a call group for participation in a group call by a plurality of mobile devices in a mobile telecommunications network, the mobile telecommunications network comprising a serving node operable to transceive data to and from the mobile telecommunications devices, the method comprising: <ul><li id="ul0001-0001" num="0000"><ul><li id="ul0002-0001" num="0008">receiving, at a serving node, data indicative of a group identifier from a said mobile terminal registered with the mobile telecommunications network; and</li><li id="ul0002-0002" num="0009">defining a Group Call Area using the received group identifier, the defined Group Call Area being accessible by the serving node so as to enable the serving node to discriminate one call group registered with said telecommunications network from another call group registered with said telecommunications network.</li></ul></li></ul>
Thus with embodiments of the invention Group Call Areas are defined on the basis of an identifier that is unique to the group; this enables two or more group calls having the same group calling identifier to exist in the same cell without interfering with one another. Conveniently the telecommunications network holds data identifying group call numbers, and at least one of the group call numbers is reserved for dynamic group calls. As a result the group call number can be used to identify the group call as a static type of group call or a dynamic type of group call, and the processes performed by the network selected accordingly.
According to a further aspect of the present invention there is provided a method of managing a group call involving a plurality of mobile communications devices, said plurality of mobile communications devices being registered with a telecommunications network via a serving node, the serving node being operable to transceive data to and from a plurality of radio access nodes so as to communicate with said registered mobile communications devices, in which at least a first of said radio access nodes has established a data communications channel with a mobile communications device of the plurality for conducting the group call, the method comprising:
identifying a radio access node adjacent the first radio access node;
defining the Group Call Area on basis of the first and adjacent radio access nodes; and
establishing a signalling channel within a cell corresponding to said adjacent radio access node, said signalling channel having an identifier corresponding to the Group Call Area.
The telecommunications network comprises a plurality of radio access nodes in the form of base stations; the serving node—or switch—is operable to transceive data to and from the base stations as per conventional network arrangements. Whichever base station has established a data communications channel with the mobile communications device has traffic and signalling channels established therein and is marked as an active cell of the Group Call Area;
In addition, base stations adjacent the active base station are added to the Group Call Area, signalling channels are established in these adjacent cells, and each signalling channel has an identifier corresponding to the Group Call Area. This method of channel allocation and deallocation provides a solution to the problem in the prior art in which channels have to be created as a mobile station moves into a new cell; by contrast, and because a signalling channel in any potential “next” cell has already been established, it is relatively straightforward to allocate a traffic channel therein.
Conveniently traffic channels can be created in response to a signalling request message from the mobile communications device identifying the adjacent radio access node: this indicates that the mobile device has moved into one of the previously designated adjacent cells and thus effectively changes the “active” cell to that which received the signalling request message from the mobile device. As the active cell changes, so do the base stations that can be considered adjacent to the “active” cell, and thus the actual Group Call Area. The Group Call Area can be updated by the network in response to traffic deallocation messages sent from a base station in the event that the base station is no longer transceiving data with a mobile device associated with the group call. These deallocation messages can additionally be used to delete cells from the Group Call Area that were adjacent to a cell previously designated the active cell. As a result, in preferred arrangements the Group Call Area includes cells immediately surrounding currently active cells.
According to a further aspect of the present invention there is provided a group call management system for managing a group call involving a plurality of mobile communications devices, said plurality of mobile communications devices being registered with a telecommunications network via a serving node, the serving node being operable to transceive data to and from a plurality of radio access nodes so as to communicate with said registered mobile communications devices, in which at least a first of said radio access nodes has established a data communications channel with a mobile communications device of the plurality for conducting the group call. The group call management system comprises:
a network node arranged to identify a radio access node adjacent the first radio access node in response to a service request message identifying the first radio access node; and
means for configuring the Group Call Area on basis of the first and adjacent radio access nodes,
wherein at least some said adjacent radio access nodes are arranged to establish a signalling channel, said signalling channel having an identifier corresponding to the Group Call Area.
In one arrangement the serving node comprises the means for configuring the Group Call Area and the group call management system is collectively configured to provide the functionality described above.
It can therefore be seen that embodiments of the invention provide a means of intelligently controlling parties joining a group call and selectively coordinating signalling between cells so as to avoid interruptions to reception of the group call.
Further features and advantages of the invention will become apparent from the following description of preferred embodiments of the invention, given by way of example only, which is made with reference to the accompanying drawings.
BRIEF DESCRIPTION OF THE DRAWINGS
<figref idrefs="DRAWINGS">FIG. 1</figref> is a schematic block diagram showing various components of a standard configuration of a mobile network;
<figref idrefs="DRAWINGS">FIG. 2</figref> is a timing diagram showing communication between various of the components shown in <figref idrefs="DRAWINGS">FIG. 1</figref> when registering a mobile station for a group call according to an embodiment of the invention;
<figref idrefs="DRAWINGS">FIG. 3</figref> is a schematic block diagram showing a plurality of cells shown in <figref idrefs="DRAWINGS">FIG. 1</figref>;
<figref idrefs="DRAWINGS">FIG. 4</figref> is a timing diagram showing communication between various of the components shown in <figref idrefs="DRAWINGS">FIG. 1</figref> when setting up a group call according to an embodiment of the invention;
<figref idrefs="DRAWINGS">FIG. 5</figref> is a timing diagram showing communication between various of the components shown in <figref idrefs="DRAWINGS">FIG. 1</figref> in relation to movement of a member of the group call into a new cell according to an embodiment of the invention;
<figref idrefs="DRAWINGS">FIG. 6</figref> is a timing diagram showing communication between various of the components shown in <figref idrefs="DRAWINGS">FIG. 1</figref> in relation to movement of a member of the group call from an old cell according to an embodiment of the invention; and
<figref idrefs="DRAWINGS">FIG. 7</figref> is a timing diagram showing communication between various of the components shown in <figref idrefs="DRAWINGS">FIG. 1</figref> when coordinating termination of a group call.
DETAILED DESCRIPTION OF THE INVENTION
As described above, embodiments of the invention are concerned with coordinating movement of group calls through a cellular network, in particular with intelligently controlling parties joining a group call and selectively coordinating signalling between cells so as to avoid interruptions to reception of the group call as it moves. In order to appreciate the level at which embodiments of the invention operate, an overview of a Public Land Mobile Network (PLMN) <b>1</b>, within which such embodiments can operate, will first be described with reference to <figref idrefs="DRAWINGS">FIG. 1</figref>.
The PLMN network shown in <figref idrefs="DRAWINGS">FIG. 1</figref> comprises a cellular network such as a GSM or UMTS network (only one cell <b>100</b> being shown in <figref idrefs="DRAWINGS">FIG. 1</figref>). The cell <b>100</b> has a limited coverage and is served by the PLMN <b>1</b> via a Base Transceiver Station (BTS) <b>102</b> and a Base Station Controller (BSC) <b>103</b>, which form a Base Station System (BSS) <b>105</b>. The BSC <b>103</b> is connected to a Mobile Switching Center (MSC) <b>107</b> which is an exchange and is arranged to perform all switching functions for mobile stations such as MS <b>101</b> located in a geographical area designated as the MSC area. As shown in <figref idrefs="DRAWINGS">FIG. 1</figref>, the MSC <b>107</b> is connected to a Service Control Point SCP <b>117</b> that is arranged, on the basis of the network subscription associated with MS <b>101</b>, to provide MS <b>101</b> with access to various intelligent network services, in this case, a group call service.
In operation, the MSC <b>107</b> takes into account the impact of the allocation of radio resources and the mobile nature of the subscribers, and performs procedures required for location registration, hand-over of, and call set-up for, served mobile stations. The MSC <b>107</b> is connected to a Home Location Register (HLR) <b>115</b>, which is a database arranged to manage subscription data relating to mobile subscribers such as MS <b>101</b>. The PLMN I may include one or several HLRs <b>115</b>, depending on the number of mobile subscribers, the capacity of the equipment and the organization of the PLMN network <b>1</b>. The HLR <b>115</b> is arranged to store data identifying the location of mobile subscribers managed by each HLR <b>115</b> (e.g. in order to be able to route calls thereto); identification numbers attached to each mobile subscription (e.g. International Mobile Subscriber identity (IMSI); Mobile Subscriber ISDN Number (MSISDN)); communication service subscription information, service restrictions (e.g. roaming limitations); general subscriber attributes and preferences; and supplementary service information including parameters associated with these services. In terms of communication between the various components of the PLMN <b>1</b>, the MSC <b>107</b>, HLR <b>115</b> and SCP <b>177</b> may send and receive data via a variety of signaling protocols, including but not limited to, Signaling System Number (SS#7) Mobile Application Part (MAP).
Additionally, the MSC <b>107</b> is connected to a Visitor Location Register (VLR) <b>113</b>, which is arranged, as in known configurations, to receive data from mobile subscribers MS <b>101</b> in this MSC area and pass this information onto the HLR <b>115</b>; additionally the VLR <b>113</b> is arranged to receive data from the HLR <b>115</b> indicating sets of services and triggers available to MS <b>101</b>. One of the sets of services available to the MS <b>101</b> in an embodiment of the invention is group calls to group ID <b>888</b>, it being assumed that the subscriber corresponding to MS <b>101</b> has subscribed to a group call service that is coordinated by the SCP <b>117</b>. As a result, call setup requests from the MS <b>101</b> that contain group ID <b>888</b> have the effect of triggering the MSC <b>107</b> to send signalling messages to the SCP <b>117</b>. In addition, the SCP <b>117</b> and MSC <b>107</b> are configured with bespoke functionality so as to configure Group Call Areas according to an embodiment of the invention. This will now be described with reference to <figref idrefs="DRAWINGS">FIGS. 2-6</figref> for the particular example of a group call being coordinated in relation to train employees travelling on a train from London to Edinburgh.
Starting with <figref idrefs="DRAWINGS">FIG. 2</figref>, the steps involved in registration of the mobile station <b>101</b> with the group call service <b>117</b> will be described. At step S<b>201</b>, the mobile station <b>101</b> sends a Registration request message, which includes a unique identifier for the group, TFN. In the current example the unique identifier conveniently includes an identity of the train, this having previously been provided to the mobile station <b>101</b> (and indeed to other mobile stations corresponding to the personnel on the train). The registration request is forwarded to the MSC <b>107</b> via the BSS <b>105</b>, and this triggers a registration request message to be forwarded to the SCP <b>117</b> at step S<b>203</b>. As can be seen from <figref idrefs="DRAWINGS">FIG. 2</figref>, the registration request message received by the SCP <b>117</b> comprises the group identifier TFN and the MSISDN of the individual mobile station <b>101</b> from which the registration request originated at step S<b>201</b>. In the current example the unique identifier TFN identifies a functional number of the particular train, and can be composed by the following parts: call type (train number), train running number and function code (e.g. driver). Thus for example assuming a train to have a train number of 2, a train running number of 00175 and function code of 01, the identifier TFN received by the SCP <b>117</b> can be 2 00175-01. It will be appreciated that the identifier can be made up of data identifying other characteristics of the train.
In response to receipt of the MSISDN and TFN information, the SCP <b>117</b> firstly checks that this requesting mobile station <b>101</b> is authorised to participate in a group service and, if so, updates its mappings between mobile stations and group identities (step S<b>205</b>). These data can then be used in handling subsequent requests for group calls. Assuming registration to be successful, the SCP <b>117</b> transmits an acknowledgment message at step S<b>207</b> to the MSC <b>107</b>, which sends this back to the mobile station <b>101</b> via the BSS <b>105</b>. Whilst registration in respect of only one mobile station is shown in <figref idrefs="DRAWINGS">FIG. 3</figref>, it will be appreciated that for arrangements in which registration is a prerequisite to participation in a group call, all such mobile stations will be required to register with the service. It is, however, to be noted that the particular registration process described herein is exemplary only and entirely independent of the processes involved in setting up and managing group calls according to embodiments of the invention. Indeed registration with a group call service can be effected via Over The Air (OTA) SIM updates in one alternative arrangement, whilst embodiments of the invention do not necessarily require all participating mobile devices to have preregistered with a group service (e.g. in the event that the group call is of an open VGCS type).
Turning now to <figref idrefs="DRAWINGS">FIG. 3</figref>, in the current example it is assumed that the train is in the process of moving through cells <b>100</b><i>a</i>, <b>100</b><i>b</i>, <b>100</b><i>c</i>, and that a group call request is received from the mobile station <b>101</b> when it is located in cell <b>100</b><i>a. </i>With reference also to <figref idrefs="DRAWINGS">FIG. 4</figref>, a group call request is received by the mobile station <b>101</b> transmitting a standard group call setup message (step S<b>401</b>), the message comprising the unique identifier for this call (TFN), together with the group ID for the call (in this example 888). This is received by the SCP <b>117</b>, together with the Cell ID (in this case <b>100</b><i>a </i>corresponding to base station BS <b>105</b><i>a</i>). At step S<b>407</b> the SCP <b>117</b> performs a look-up of the database holding data indicating ongoing group calls having this group ID (888) and a unique group identity matching that received at step S<b>401</b>. In the current example the SCP <b>117</b> is configured to match the train running number portion of the Train Functional Number (TFN), but it will be appreciated that the entire string of the TFN could alternatively be used, or indeed a different part or transformation thereof. In this case no such group call exists, so at step S<b>407</b> an entry is created in the group call table managed by the SCP <b>117</b> for a new call having group identity TFN and group ID 888.
In embodiments of the invention the SCP <b>117</b> additionally stores, or has access to, a table listing static group call numbers and dynamic group call numbers. For illustrative purposes it is assumed that group IDs within the range 880-888 have been reserved for dynamic group calls, and, if a group call is determined to correspond to a dynamic group call, the functionality invoked of the SCP <b>117</b> is different to that which is invoked according to conventional methods for handling dynamic group calls. It is to be noted that static group calls are handled according to conventional methods and are outside of the scope of the present invention.
In the current example the group ID is 888, which indicates a dynamic group call. In response to identifying the group call to be of the dynamic type the SCP <b>117</b> identifies all cells that are adjacent to the current cell <b>100</b><i>a, </i>e.g. by means of a prestored cell configuration map. A message comprising the list of neighbouring cells is subsequently sent to the MSC <b>107</b> at step S<b>409</b>, together with the unique group identifier TFN. This message comprises an instruction for the MSC <b>107</b> to create a Group Call Area based on these neighbouring and originating cells (step S<b>411</b>). Referring back to <figref idrefs="DRAWINGS">FIG. 3</figref>, in the current example the cells neighbouring the cell of origin <b>100</b><i>a </i>are cells <b>100</b><i>x </i>and <b>100</b><i>b</i>; accordingly step S<b>411</b> involves the MSC <b>107</b> updating a group call register database held locally by the MSC <b>107</b> so as to include this newly created dynamic Group Call Area with cells <b>100</b><i>x, </i><b>100</b><i>a, </i><b>100</b><i>b. </i>
At step S<b>413</b> a call connection message is sent to the mobile station <b>101</b> so as to start the dynamic group call. In addition a notification message comprising the dynamic group ID 888 is broadcast to all mobile stations within the Group Call Area, which in this example comprises cells <b>100</b><i>x, </i><b>100</b><i>a </i>and <b>100</b><i>b </i>(step S<b>417</b>), the BSS <b>105</b><i>a</i>, <b>105</b><i>b </i>having previously been instructed to set up signalling and traffic channels in response to the notification received at step S<b>415</b>. This message is broadcast on the Notification channel NCH and enables all other mobile stations having the unique group identifier TFN and subscribing to group call <b>888</b> to join the call in the call group area <b>100</b><i>x, </i><b>100</b><i>a, </i><b>100</b><i>b, </i>and thereby make use of the traffic channels established therein.
The steps relating to the processes performed in respect of cells <b>100</b><i>x </i>and <b>100</b><i>b</i>—i.e. those adjacent to the cell <b>100</b><i>a </i>in which the group call originated—will now be described in relation to cell <b>100</b><i>b. </i>Having established the traffic channel in cell <b>100</b><i>b, </i>base station BSS <b>105</b><i>b </i>sends a standard TCH allocation message to the SCP <b>117</b> via the MSC <b>107</b> (step S<b>418</b>), causing the SCP <b>117</b> to store an entry in its database for this neighbouring cell <b>100</b><i>b </i>(step S<b>419</b>). Meanwhile, and in accordance with standard methods, the BSS <b>105</b><i>b </i>monitors for a reply on the uplink traffic channel from a mobile station within cell <b>100</b><i>b </i>for a predetermined time period (step S<b>421</b>). In the event that there is no response within this period, the BSS <b>105</b><i>b </i>transmits a deallocation traffic channel notification message to the SCP <b>117</b> via the MSC <b>107</b> (step S<b>423</b>), causing the SCP <b>117</b> to update its entry for traffic channel in cell <b>100</b><i>b </i>as deallocated. It is to be noted that whilst the traffic channel is removed, the signalling channel is not pulled down; furthermore the deallocation of the traffic channel has no bearing on the Group Call Area—this remaining as <b>100</b><i>x, </i><b>100</b><i>a</i>, <b>100</b><i>b. </i>
Group Call Areas created according to embodiments of the invention can therefore be characterised as comprising active cells and passive cells. The active cells are those for which signalling and traffic channels exist, and there are as many active cells as there are cells comprising participants in the group call. The passive cells are those that neighbour the active cells and in respect of which only signalling channels exist. Thus in the current example, for the time in which the train and all personnel thereon are located within cell <b>100</b><i>a, </i>there is one active cell (<b>100</b><i>a</i>) and two passive cells (<b>100</b><i>x, </i><b>100</b><i>b</i>). This method of channel allocation and deallocation provides a solution to the problem in the prior art in which channels have to be created as a mobile station moves into a new cell, because a signalling channel in any potential “next” cell has already been established, making it relatively straightforward to allocate a traffic channel therein, as will now be described with reference to <figref idrefs="DRAWINGS">FIG. 5</figref>.
Referring back briefly to <figref idrefs="DRAWINGS">FIG. 3</figref>, as the train moves along trajectory T<b>1</b>, it enters cell <b>100</b><i>b </i>after a certain period of time. As a result of the notification messages transmitted at step S<b>415</b>, cell <b>100</b><i>b </i>already has a notification channel associated with this group call (ID 888 and a Group Call Area having identifier 00175). Accordingly the mobile station <b>101</b> will detect the existence of the group call having ID 888 via the notification channel as soon as it enters cell <b>100</b><i>b; </i>in response the mobile station <b>101</b> checks the group ID (888) and the identifier of the Group Call Area (00175) against unique identifiers registered with the mobile station <b>101</b>. Since, in this case, the mobile station <b>101</b> has registered for Group Call Area having identifier 00175, the group call can be conducted in this cell <b>100</b><i>b; </i>as a result mobile station <b>101</b> subsequently sends a notification response message to the BSS <b>105</b><i>b </i>(step S<b>501</b>), the notification response message comprising the Group Call Area (00175) and group ID (888). When received by the BSS <b>105</b><i>b</i>, the BSS <b>105</b><i>b </i>allocates a traffic channel therein (step S<b>502</b>) and sends notification of the traffic channel allocation to the SCP (step S<b>503</b>) for cell <b>100</b><i>b. </i>
Upon receipt of the traffic channel allocation message the SCP <b>117</b> identifies all cells that are adjacent to the current cell <b>100</b><i>b, </i>again by referring to the prestored cell configuration map as described above in relation to step S<b>407</b>, and updates the status for cell ID <b>100</b><i>b </i>as having an active traffic channel therein (step S<b>505</b>). Thereafter, identifiers of cells adjacent to the current cell <b>100</b><i>b </i>are sent to the MSC <b>107</b>, which in this case is cell <b>100</b><i>c</i>, with an instruction to the MSC <b>107</b> to update the Group Call Area to include this cell <b>100</b><i>c </i>(step S<b>507</b>). Upon receipt of this instruction message the MSC <b>107</b> updates its table (step S<b>508</b>) and sends a notification message to cell <b>100</b><i>c </i>newly added to the Group Call Area (step S<b>509</b>); this causes the BSS <b>105</b><i>c </i>to transmit a notification message to all mobile stations in the cell <b>100</b><i>c </i>(step S<b>511</b>) and the process then proceeds as described from step S<b>415</b> in <figref idrefs="DRAWINGS">FIG. 4</figref>.
In addition to adding cells to the Group Call Area as the group call moves, cells that were previously part of the Group Call Area are deleted therefrom. Referring to <figref idrefs="DRAWINGS">FIG. 6</figref>, deletion of cells from the Call Group Area is conveniently performed on the basis of standard signalling messages, namely a traffic deallocation message. This message will be transmitted by BSS <b>105</b><i>a </i>when the train (and thus mobile station <b>101</b>) has moved out of cell <b>100</b><i>a</i>, because once the train has moved into cell <b>100</b><i>b </i>there are no mobile stations in cell <b>100</b><i>a </i>that can respond to the notification messages having Group Call Area (00175) and group ID (888). Once the traffic deallocation message has been received by the SCP <b>117</b>, the entry corresponding to cell ID <b>100</b><i>a </i>is updated with the status of the traffic channel. In addition the SCP <b>117</b> searches for cells listed in the Group Call Area that have deallocated status and that are not adjacent the currently active cell(s) (i.e. cell(s) for which the traffic channel is active). Referring back to <figref idrefs="DRAWINGS">FIG. 3</figref>, in the present example the currently active cell is <b>100</b><i>b</i>, and there are three unactive, or passive, cells <b>100</b><i>x, </i><b>100</b><i>a</i>, <b>100</b><i>c</i>. Since cell <b>100</b><i>x </i>is not a neighbour of the currently active cell <b>100</b><i>b</i>, it is removed from the Call Group Area (step <b>603</b>) by the SCP <b>117</b>. A message is then sent to the MSC <b>107</b>, instructing the MSC <b>107</b> to delete cell <b>100</b><i>x </i>from the Group Call Area that it stored at step <b>411</b>; this deletion is effected at step S<b>607</b> and the MSC <b>107</b> then proceeds to instruct the BSS <b>105</b>x corresponding to the deleted cell to stop sending notification messages via the signalling channel NCH (step S<b>607</b>).
As described above, there will be as many active cells as there are participants of the group call that occupy different cells; thus whilst in the example shown in <figref idrefs="DRAWINGS">FIG. 3</figref> it is assumed that all participants of the group call are present in a single cell at any one time, for cases where the train is long and/or participants are distributed along the length of the train, it can expected that there will be several active cells and a commensurately greater number of passive cells than those shown in <figref idrefs="DRAWINGS">FIG. 3</figref>.
It will be appreciated that the steps shown in <figref idrefs="DRAWINGS">FIGS. 5 and 6</figref> will be repeated in respect of each cell that the group call enters so as to ensure that the activation of traffic channels in any given active cell is synchronised with the activation and deactivation of signalling channels in prospective, current and previous passive cells. In summary, and by way of generalising the ongoing group call management process, allocations and deallocations of voice channels are reported to the MSC <b>107</b> by the BSS <b>105</b><i>a </i>. . . <b>105</b><i>c. </i>Voice channel allocations are used by the MSC <b>107</b> to request the service node <b>117</b> to find the adjacent cells of the active cell (i.e. the cell in which the voice channel is active). These cells are then added to the Group Call Area. Deallocation information is used to remove all cells from the Group Call Area in case they are no longer neighbour cells of a cell in which a voice channel is currently allocated.
When a group call is terminated, various messages are passed between the various mobile and network entities, as will now be described with reference to <figref idrefs="DRAWINGS">FIG. 7</figref>. Typically the group call will be terminated by the mobile station <b>101</b>, by means of a standard termination request message (step S<b>701</b>). For illustration purposes it will be assumed that the termination request is received when the mobile station is in cell <b>100</b><i>b, </i>so that this message is received from the mobile station <b>101</b> by BSS <b>105</b><i>b. </i>The BSS <b>105</b><i>b </i>relays the termination request message to the MSC <b>107</b>, which creates a group call termination instruction identifying the Group Call Area (00175) and group ID (888) and transmits this message to the SCP <b>117</b>. In response the SCP <b>117</b> removes all cells from the mapping corresponding to this Group Call Area and Group ID (step S<b>705</b>); in addition, the SCP <b>117</b> sends an instruction to the MSC <b>107</b>, instructing the MSC <b>107</b> to delete the cells from the Group Call Area associated with this group call (step S<b>707</b>). When received, the MSC <b>107</b> identifies the group call that it created at step <b>411</b> and sends termination messages to all BSS <b>105</b><i>a</i>, <b>105</b><i>b</i>, <b>105</b><i>c </i>currently listed against that Group Call Area (step S<b>709</b>) so as to effect termination of any traffic and signalling channels.
From the foregoing it can be seen that in addition to conventional functionality specified in GSM Standard 03.68, the SCP <b>117</b> is configured with a means for transmitting an instruction to the MSC <b>107</b> to define a Group Call Area including a plurality of neighbouring cells (e.g. step S<b>409</b>), and to send instructions to add and delete cells to and from the Group Call Area (e.g. S<b>507</b>, S<b>605</b>). The SCP <b>117</b> is additionally configured to receive traffic allocation and deallocation messages in relation to the neighbouring cells, these traffic channel messages triggering updates to the register holding details of group calls (S<b>407</b>, S<b>505</b>, S<b>603</b>) and causing the SCP <b>117</b> to send the afore-mentioned messages to the MSC <b>107</b>.
The MSC <b>107</b> is similarly equipped with bespoke functionality in the form of means for updating a repository holding details of group calls and cells relating thereto in the event that a group call is determined to be of the dynamic type (i.e. having a number between 880-888 in the current example); the MSC <b>107</b> can add to, and delete from, the cells belonging to a Group Call Area upon instruction from the SCP <b>117</b> as shown e.g. at step S<b>411</b>, <b>508</b>, <b>607</b>. In addition, the MSC <b>107</b> is configured to transmit traffic allocation and deallocation instruction messages to the SCP <b>107</b> (these being received from the BSS using a standard uplink reply/notification feature). This additional functionality can be implemented as software running on, and storage accessible to, the switch <b>107</b> and SCP <b>117</b>.
In addition the mobile stations are equipped with means to discriminate between dynamic group calls (i.e. group calls having Ids between 880-888) on the basis of Group Call Area (i.e. group identifiers that are unique for the group—in the foregoing example this is the train identity). This functionality can either be implemented on the mobile phone or on the removable module (SIM) associated with the subscription of the user. Such functionality is similar to the filtering of Shunting Groups in the GSM-Railway (GSM-R) environment. This therefore enables any given mobile station to participate in two dynamic group calls having the same group ID (e.g. 888) provided the mobile station has previously registered for each of the groups (i.e. in respect of each unique identifier).
It will be appreciated from the foregoing that by using an identifier to define the Group Call Area embodiments of the invention enable groups having the same group number to co-exist distinct from one another within the same group of cells. This is an improvement of the prior art, in which there is either no means of distinguishing one Group Call Area from another Group Call Area if their physical locations overlap (with the result that the groups are joined into a single group), or the joining of a group is controlled by which notification channel a mobile station communicates with first (with the result that selection of a group by the mobile station is essentially a random process).
Additional Details and Modifications
Whilst in the foregoing embodiment the use of a unique group identifier is described in the context of dynamic group calls, this aspect of the invention could also be utilised in respect of static group calls, since it provides a means of discriminating between different group calls existing in a given area. Thus while the foregoing embodiment relates to the coordination of group calls in the context of train travel, embodiments of the invention could alternatively be employed in environments that involve mobile and static group calls. Examples include groups of workers in a factory, emergency services (in particular sections of the police force or fire brigade), teams participating in sporting events such as sailing, groups of archaeologists distributed over a given area, or groups of construction workers distributed over a construction site etc.
The above embodiments are to be understood as illustrative examples of the invention. Other embodiments are envisaged, for example in relation to group calls involving more than one MSC. In such a scenario one MSC is designated as controller of the group call: the Anchor MSC. If the Group Call Area includes cells which are not under the control of the Anchor-MSC, the MSC for those cells also participate in the group call as a Relay MSC. This enables movement of the group call as and when a different MSC becomes available.
It is to be understood that any feature described in relation to any one embodiment may be used alone, or in combination with other features described, and may also be used in combination with one or more features of any other of the embodiments, or any combination of any other of the embodiments. Furthermore, equivalents and modifications not described above may also be employed without departing from the scope of the invention, which is defined in the accompanying claims.
Contents5
8 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6 Sheet 7 Sheet 8
Every citation, both ways
| Document | Relation | Office | Cited during |
|---|---|---|---|
| US2013130736A1 | Cited by | United States of America | Pre-grant |
| CN108712727A | Cited by | China | Search report |
| US10609521B2 | Cited by | United States of America | Applicant |
| US2016174142A1 | Cited by | United States of America | Pre-grant |
| US9615355B2 | Cited by | United States of America | Search report |
| WO2011069415A1 | Cited by | World Intellectual Property Organization (WIPO) | International search |
| US2017265018A1 | Cited by | United States of America | Search report |
| US2010255871A1 | Cited by | United States of America | Pre-grant |
| US10880722B1 | Cited by | United States of America | Search report |
| US9253762B2 | Cited by | United States of America | Search report |
| US9191785B2 | Cited by | United States of America | Search report |
| US2014050178A1 | Cited by | United States of America | Pre-grant |
| WO2017025934A1 | Cited by | World Intellectual Property Organization (WIPO) | International search |
| CN110582061A | Cited by | China | Search report |
| US8254978B2 | Cited by | United States of America | Search report |
| CN102547595A | Cited by | China | Search report |
| CN108696828A | Cited by | China | Search report |
| US11082823B2 | Cited by | United States of America | Search report |
| CN104244190A | Cited by | China | Search report |
| KR20170105721A | Cited by | Republic of Korea | Search report |
| CN105409281A | Cited by | China | Search report |
| CN104378740A | Cited by | China | Search report |
| US2003117976A1 | Cites | United States of America | Pre-grant |
| US2004180682A1 | Cites | United States of America | Pre-grant |
| US2010029290A1 | Cites | United States of America | Pre-grant |
| US5970417A | Cites | United States of America | Pre-grant |
| US6219548B1 | Cites | United States of America | Pre-grant |
17 members in 6 offices
Priority claims2
| Document | Office | Kind | Date |
|---|---|---|---|
| 96669007 | United States of America | A | |
| US20070966690 | – | – | – |
Members17
| Document | Office | Kind | |
|---|---|---|---|
| US2009170488A1 | United States of America | A1 | |
| WO2009083587A2 | World Intellectual Property Organization (WIPO) | A2 | |
| WO2009083587A3 | World Intellectual Property Organization (WIPO) | A3 | |
| KR20100103648A | Republic of Korea | A | |
| EP2241121A2 | European Patent Office (EPO) | A2 | |
| CN101940009A | China | A | |
| JP2011508554A | Japan | A | |
| US8364191B2 | United States of America | B2 | |
| US2013130668A1 | United States of America | A1 | |
| US2013184027A1 | United States of America | A1 | |
| JP5386505B2 | Japan | B2 | |
| CN101940009B | China | B | |
| US8649814B2 | United States of America | B2 | |
| KR101429799B1 | Republic of Korea | B1 | |
| US9282438B2 | United States of America | B2 | |
| US2016174050A1 | United States of America | A1 | |
| US9860719B2 | United States of America | B2 |
79 transactions on the USPTO file
Allowed after 1 non-final rejection, 1 final rejection, 1 RCE and 1 appeal.
- Non-final rejections
- 1
- Final rejections
- 1
- RCEs
- 1
- Appeals
- 1
Over time
Point at a mark for the transactionTransactions
| Event | Code | |
|---|---|---|
| Recordation of Patent Grant MailedPGM/ | PGM/ | |
| Patent Issue Date Used in PTA CalculationAllowedPTAC | PTAC | |
| Email NotificationEML_NTR | EML_NTR | |
| Issue Notification MailedAllowedWPIR | WPIR | |
| Dispatch to FDCD1935 | D1935 | |
| Application Is Considered Ready for IssuePILS | PILS | |
| Issue Fee Payment VerifiedN084 | N084 | |
| Issue Fee Payment ReceivedIFEE | IFEE | |
| Email NotificationEML_NTR | EML_NTR | |
| Printer Rush- No mailingTCPB | TCPB | |
| Mailing Corrected Notice of AllowabilityMCNOA | MCNOA | |
| Interview Summary- Applicant InitiatedEXIA | EXIA | |
| Examiner's Amendment CommunicationEX.A | EX.A | |
| Corrected Notice of AllowabilityCNOA | CNOA | |
| Pubs Case Remand to TCPUBTC | PUBTC | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Notice of AllowanceAllowedMN/=. | MN/=. | |
| Notice of Allowance Data Verification CompletedAllowedN/=. | N/=. | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Disposal for a RCE / CPA / R129AbandonedABN9 | ABN9 | |
| Request for Continued Examination (RCE)RCEX | RCEX | |
| Request for Extension of Time - GrantedXT/G | XT/G | |
| Workflow - Request for RCE - BeginBRCE | BRCE | |
| Email NotificationEML_NTR | EML_NTR | |
| Change in Power of Attorney (May Include Associate POA)PA.. | PA.. | |
| Correspondence Address ChangeC.AD | C.AD | |
| Mail Appeals conf. Proceed to BPAIMAPCP | MAPCP | |
| Pre-Appeals Conference Decision - Proceed to BPAIAPCP | APCP | |
| Request for Pre-Appeal Conference FiledAP.C | AP.C | |
| Notice of Appeal FiledN/AP | N/AP | |
| Request for Extension of Time - GrantedXT/G | XT/G | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Final Rejection (PTOL - 326)Final rejectionMCTFR | MCTFR | |
| Final RejectionFinal rejectionCTFR | CTFR | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Non-Final ActionA... | A... | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response to Election / Restriction FiledELC. | ELC. | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Restriction RequirementMCTRS | MCTRS | |
| Restriction/Election RequirementCTRS | CTRS | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Email NotificationEML_NTR | EML_NTR | |
| PG-Pub Issue NotificationPG-ISSUE | PG-ISSUE | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| IFW TSS Processing by Tech Center CompleteTSSCOMP | TSSCOMP | |
| Application Dispatched from OIPEOIPE | OIPE | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Email NotificationEML_NTR | EML_NTR | |
| Filing Receipt - UpdatedFLRCPT.U | FLRCPT.U | |
| Application Is Now CompleteCOMP | COMP | |
| Sent to Classification ContractorPGPC | PGPC | |
| Additional Application Filing FeesADDFLFEE | ADDFLFEE | |
| A statement by one or more inventors satisfying the requirement under 35 USC 115, Oath of the ApplicOATHDECL | OATHDECL | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTR | EML_NTR | |
| Email NotificationEML_NTF | EML_NTF | |
| Notice Mailed--Application Incomplete--Filing Date AssignedINCD | INCD | |
| Filing ReceiptFLRCPT.O | FLRCPT.O | |
| Cleared by OIPE CSRL194 | L194 | |
| IFW Scan & PACR Auto Security ReviewSCAN | SCAN | |
| Preliminary AmendmentA.PE | A.PE | |
| Initial Exam Team nnIEXX | IEXX |
11 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Lapsed due to failure to pay maintenance feeLapsedFP | FP | |
| Lapse for failure to pay maintenance feesLapsedPATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES (ORIGINAL EVENT CODE: EXP.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYLAPS | LAPS | |
| Information on status: patent discontinuationPATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362STCH | STCH | |
| Fee payment procedureMAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYFEPP | FEPP | |
| Fee paymentFPAY | FPAY | |
| Information on status: patent grantGrantedPATENTED CASESTCF | STCF | |
| Fee payment procedurePAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYFEPP | FEPP | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS |
Numbers
- Publication, DOCDB
- 2009170488
- Publication, EPODOC
- US2009170488
- Application
- 11966690
- Application, DOCDB
- 96669007
- Application, EPODOC
- US20070966690
Titles
- English
- Group Call Management
Patent term adjustment
- A delay
- +696 daysthe office missed an examination deadline
- B delay
- +425 dayspendency past three years
- Applicant delay
- −63 days
- Net adjustment
- 1,058 days
Classification
- CPC, 6
- H04W4/08
- H04M3/56
- H04M2203/2044
- H04M2207/18
- H04W76/40
- H04W72/20
- IPC, 2
- H04M3 56
- H04W4 44
- USPC, 1
- 455416000