WO2009064596A1 - Secure communication system comprising terminals with different security capability levels - Google Patents
Secure communication system comprising terminals with different security capability levels Download PDFInfo
- Publication number
- WO2009064596A1 WO2009064596A1 PCT/US2008/080944 US2008080944W WO2009064596A1 WO 2009064596 A1 WO2009064596 A1 WO 2009064596A1 US 2008080944 W US2008080944 W US 2008080944W WO 2009064596 A1 WO2009064596 A1 WO 2009064596A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- terminals
- group
- sub
- encrypted
- clear
- Prior art date
Links
- 238000004891 communication Methods 0.000 title claims abstract description 115
- 238000000034 method Methods 0.000 claims abstract description 56
- 230000010267 cellular communication Effects 0.000 claims description 5
- 230000006870 function Effects 0.000 description 14
- 238000013519 translation Methods 0.000 description 12
- 230000014616 translation Effects 0.000 description 12
- 230000008901 benefit Effects 0.000 description 9
- 230000005540 biological transmission Effects 0.000 description 7
- 230000009471 action Effects 0.000 description 5
- 238000010295 mobile communication Methods 0.000 description 5
- 230000008569 process Effects 0.000 description 5
- 238000010586 diagram Methods 0.000 description 4
- 238000012545 processing Methods 0.000 description 4
- 230000000593 degrading effect Effects 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 230000011664 signaling Effects 0.000 description 3
- 230000001413 cellular effect Effects 0.000 description 2
- 230000008859 change Effects 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 230000001360 synchronised effect Effects 0.000 description 2
- 238000013459 approach Methods 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 230000006399 behavior Effects 0.000 description 1
- 230000015572 biosynthetic process Effects 0.000 description 1
- 239000000470 constituent Substances 0.000 description 1
- 238000010276 construction Methods 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
- 238000003780 insertion Methods 0.000 description 1
- 230000037431 insertion Effects 0.000 description 1
- 238000009434 installation Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000009877 rendering Methods 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/04—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
- H04L63/0428—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload
- H04L63/0471—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload applying encryption by an intermediary, e.g. receiving clear information at the intermediary and encrypting the received information at the intermediary before forwarding
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/22—Arrangements for preventing the taking of data from a data transmission channel without authorisation
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/04—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
- H04L63/0428—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload
- H04L63/0464—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload using hop-by-hop encryption, i.e. wherein an intermediate entity decrypts the information and re-encrypts it before forwarding it
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/03—Protecting confidentiality, e.g. by encryption
- H04W12/033—Protecting confidentiality, e.g. by encryption of the user plane, e.g. user's traffic
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/06—Authentication
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/08—Access security
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/10—Integrity
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/12—Detection or prevention of fraud
-
- 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/08—User group management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/90—Services for handling of emergency or hazardous situations, e.g. earthquake and tsunami warning systems [ETWS]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/50—Connection management for emergency connections
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W84/00—Network topologies
- H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
- H04W84/04—Large scale networks; Deep hierarchical networks
- H04W84/042—Public Land Mobile systems, e.g. cellular systems
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
- H04W88/02—Terminal devices
Definitions
- the technical field relates generally to a communication system, and a method and processor for use in the system.
- the technical field relates to a mobile communication system, and a method and processor for use in the system, in which communication terminals can have different security capability levels for sending or receiving encrypted communications to maintain security of user information communicated.
- End-to-end encryption may be employed. This means that the encryption can be applied by a sending terminal or source of the information and is removed by a receiving terminal or destination of the information. Encryption is usually achieved by producing a random or pseudorandom sequence of numbers (binary digits) and using an encryption algorithm to combine the sequence with a secret user number, referred to as an 'encryption key', applied by a user of the sending terminal. The combination generates another number sequence which is known as a keystream. The keystream, or a portion of it, is then combined with the user speech, data or other information to be transmitted to encrypt the information. This combination may use a known combining function such as an exclusive OR (XOR) combining function.
- XOR exclusive OR
- the encryption process has to be synchronised between the transmitter in the sending terminal and the receiver in the receiving terminal.
- the transmitter must send information concerning the state of the encryption algorithm to the receiver to allow the receiver to synchronise its algorithm for decryption.
- the receiving terminal must have the same encryption algorithm and the same encryption key as the transmitting terminal in order to decrypt the encrypted information it receives.
- the system in which end-to-end encryption is employed may be a mobile communication system which is a cellular system.
- a mobile communication system which is a cellular system.
- the user terminals include mobile stations, such as portable or vehicle carried telephones or radios, wireless enabled computing devices, personal digital assistants and the like, which can communicate via a network infrastructure.
- the infrastructure generally includes a plurality of base stations (base transceiver stations) which may be fixed in position and which may form a communication network.
- Each base station has one or more transceivers which serve mobile stations in a given region or area, known as a 'cell', by wireless communication.
- the cells of neighbouring base stations are often overlapping.
- Communications to and from mobile stations in a cellular communication system include system control communications and traffic communications.
- System control communications are made to establish and maintain operation in the system in accordance with a pre-determined operating protocol.
- Traffic communications are made between user terminals, such as a mobile station and another terminal or a plurality of other terminals, which may include one or more mobile stations, to transmit user communicated information known as 'traffic' information; such information may include speech or data, e.g. numerical or text data, picture information or video information.
- a traffic communication between mobile stations which are currently in the same cell may be established by a single base station or even directly between the mobile stations without the involvement of a base station.
- Traffic communications between mobile stations which are currently in different cells may be established by involvement of a plurality of base stations serving the various cells.
- a TETRA system which is a system operating according to the protocols defined by the TETRA operating standard defined by the European Telecommunications Standards Institute (ETSI). Such systems are widely used by (amongst others) emergency services organisations, such as police, fire brigades and ambulance services.
- ETSI European Telecommunications Standards Institute
- wireless communications to and from mobile stations and other user terminals are controlled in a synchronised sequence of time slots.
- the duration of each time slot is 14.167 ms, for example.
- a set of four slots represent four physical channels in a time division multiple access (TDMA) protocol and form, for example, one time frame of duration 56.67ms in an 18 time frame multiframe timing structure.
- TDMA time division multiple access
- Each communication is generally made on a channel allocated by the system infrastructure.
- the channel may thus comprise a series of specified time slots, and the slots may be on a specified carrier frequency.
- traffic information may be communicated between a transmitting terminal and a plurality of receiving terminals.
- the terminals may be referred to as a 'group' (or 'talk group') which may have an assigned identifier within the system.
- Each user terminal which may be a mobile or fixed terminal, operating within the system may be a member of one or more groups. Allocation of membership to groups may be carried out by an operator having control or management functions in operation of the system. For example, the operator may be a person operating a terminal comprising a control console (also known as a 'dispatcher console') who may be responsible for other management or control duties such as issuing group work assignments using the system.
- a control console also known as a 'dispatcher console'
- Such an operator is often referred to as a 'dispatcher'.
- a 'dispatcher' In use of communication systems, such as TETRA systems, it may be desirable to join or connect together different existing groups so that a traffic communication taking place in one group may be received by terminals of one or more other groups.
- the different groups may be different police groups and the communication may be a call which should be heard by the members of the different police groups.
- the operation of joining or connecting groups together is known as 'patching'.
- patching is carried out by an operator, such as a dispatcher, using a communication terminal comprising a control console.
- the user terminals operating in different groups in a communication system may have different security capabilities. For example, some terminals may be capable of communicating in a secure mode using end-to-end encryption. Other terminals may not be capable of using end-to-end encryption and may therefore communicate in a clear mode, in other words, a mode in which wireless communications are unencrypted.
- a clear mode in other words, a mode in which wireless communications are unencrypted.
- the patching process may be difficult to achieve and operational problems may result.
- FIG. 1 is a block schematic diagram of an illustrative communication system 100 which may be adapted in accordance with embodiments of the invention.
- FIG. 2 is a flow diagram of a method of operation embodying the invention in the system of FIG. 1.
- FIG. 3 is a flow diagram of a further method of operation embodying the invention in the system of FIG. 1.
- the communication system includes a group management processor operable to divide an enlarged group of user terminals formed by patching of smaller groups into sub-sets of user terminals including: (1) at least one encrypted sub-set of terminals which are operable to undertake only encrypted communications; and (2) at least one selectable-clear sub-set of terminals which includes: (i) selectable terminals that are able to undertake clear communications and, when selected, encrypted communications; and (ii) clear terminals that are operable to undertake only clear communications; and a translator operable to translate a communication sent in a first encrypted form from a user terminal of one of the sub-sets into a second encrypted form suitable for decryption by user terminals of another of the sub-sets.
- the translator may conveniently operate by translating an encrypted communication received in the first encrypted form into the second encrypted form by decrypting the communication of the first encrypted form and re-encrypting the decrypted communication into the second encrypted form.
- the first encrypted form and the second encrypted form may use at least one encryption parameter which differs between the first encrypted form and the second encrypted form.
- the at least one encryption parameter which differs may be selected from: (i) an encryption key; (ii) an encryption algorithm; (iii) a synchronisation parameter.
- the system may include a group patching processor operable to patch together communication resources of smaller groups of user terminals to form the enlarged group of the terminals.
- the functions of the group management processor and of the group patching processor may be operated in a combined processor or in separate processors.
- a combined processor or console may incorporate the function of the translator as well as the function of group management processor and optionally the group patching processor.
- the improved system embodying the invention allows communications to be made as widely as possible to all members of an enlarged patched group, without degrading the security of communications by allowing encrypted communications to be retransmitted in a clear form.
- the improved system allows efficient operation within a patched enlarged group including user terminals of smaller groups having different security capabilities.
- the operation may take place in a manner which is consistent in different operational scenarios.
- All user terminals such as mobile stations operating in an enlarged group formed or connected together by patching, may receive a call taking place in the enlarged group irrespective of the security capability of the receiving terminal relative to that of the transmitting terminal provided that the security state of an encrypted call is not degraded to clear, if such degrading is not desired. Users of the terminals do not need to be aware that patching of resources of different capabilities has been carried out.
- the improved system embodying the invention may suitably be a system in which end-to-end encrypted communications may take place by multicast transmission, such as a mobile cellular communication system or a wired network or the internet.
- the system may for example be a TETRA system, i.e. a system which operates in accordance with the protocols defined by the TETRA standard, or an APCO 25 system, i.e. a system which operates in accordance with the protocols defined by the APCO Project 25 standard defined by the Association of Public-Safety Communications Officials- International, Inc.
- FIG. 1 a block schematic diagram of a communication system 100 which may be adapted to operate in accordance with embodiments of the invention.
- the system 100 is a cellular communication system, for example.
- the system 100 includes a fixed infrastructure including a plurality of base stations (BSs) which serve with wireless communications mobile stations (MSs) in a cell defined by the position of each of the BSs.
- BSs base stations
- MSs wireless communications mobile stations
- the system 100 may be a TETRA system, i.e. may operate in accordance with the protocols defined by the TETRA standard, although it could alternatively be a system operating according to another industry standard for communications, e.g. wireless communications, in which multicast transmissions are possible, such as an APCO 25 system.
- the system 100 includes a BS 101 which provides wireless communication service to user terminals in the form of MSs within range of the BS 101, i.e. within a cell having the BS 101 at its centre. Two such MSs, namely MS 103 and MS 105, are shown having respectively radio links 107 and 109 to the BS 101.
- the system 100 also includes another BS 111 which provides wireless communication service to user terminals in the form of MSs within range of the BS 111, i.e. within a cell having the BS 111 at its centre. Two such MSs, namely MS 113 and MS 115, are shown having respectively radio links 117 and 119 to the BS 111.
- the system 100 also includes a BS 121 which provides wireless communication service to user terminals in the form of MSs (mobile stations) within range of the BS 121, i.e. within a cell having the BS 121 at its centre. Two such MSs, namely MS 123 and MS 125, are shown having respectively radio links 127 and 129 to the BS 121.
- the BS 101 is operationally associated via a link 104 with a router 102, e.g. a core router, which routes communications from the BS 101 (on behalf of MSs served by the BS 101) to other terminals, e.g. MSs served by other BSs, within the system 100 and in other systems (not shown) operably connected to the system 100.
- a router 102 e.g. a core router
- the router 102 also routes incoming communications to the BS 101.
- the BS 111 is operationally associated via a link 114 with a router 112, e.g. a core router, which routes communications from the BS 111 (on behalf of MSs served by the BS 111) to other terminals, e.g. MSs served by other BSs, within the system 100 and in other systems operably connected to the system 100.
- the router 112 also routes incoming communications to the BS 111.
- the BS 121 is operationally associated via a link 124 with a router 122, e.g. a core router, which routes communications from the BS 121 (on behalf of MSs served by the BS 121) to other terminals, e.g.
- the router 122 also routes incoming communications to the BS 121.
- the routers 102, 112 and 122 are operably connected via further links 132, 134 and 136 to a network 131 which may, for example, include a plurality of further routers and/or other nodes (not shown) which may include one or more telephony gateways and/or gateways to other communication systems.
- the routers 102, 112 and 122 are mutually connected to one another and to other routers (not shown) via the network 131.
- the links 104, 114, 124, 132, 134 and 136, and individual links (not shown) between nodes and/or routers (not shown) in the network 131, may comprise wired and/or wireless links.
- the system 100 may include a zone controller 133, which may be one of a plurality of zone controllers operating within the system 100.
- the zone controller 133 is a controller which comprises a processor which provides co-ordination and control of operation involving the different BSs, routers and other nodes of the system 100.
- the zone controller 133 may control allocation of routing paths and communication channels employed for communication by BSs and their served MSs within the system 100 in a given zone of the system.
- the zone controller 133 has a link 135 to the router 102, a link 137 to the router 112 and a link 139 to the router 122.
- the links 135, 137 and 139 may be wired and/or wireless links.
- the links 135, 137 and 139 are shown as direct links but could optionally pass via the network 131.
- the zone controller 133 is also operably connected to a database 138 which holds details relating to composition of the system 100 including current identities and locations of MSs and membership of groups of MSs operating within the system 100.
- the database 138 may be a single database unit or may comprise a plurality of units, which may be located in the same part or different parts of the system 100.
- the system 100 includes a control console 145 operably connected to the infrastructure of the system 100, in particular to the database 138, the zone controller 133 and the network 131 (and thereby to user terminals of the system 100).
- the control console 145 may be a fixed installation within the system 100.
- the control console 145 includes various operably interconnected components including a control terminal 141, via which communications with user terminals of the system 100 may be made, and a user interface 142.
- the user interface 142 may comprise a single interface unit or a plurality of interface units at which an operator may in a known manner apply input control signals and information, and monitor activities being controlled within the system 100.
- the control console 145 and its constituent components may thereby be operated via the user interface 142 by an operator who is a system manager or other person having authority to change operational conditions within the system 100 via inputs made at the user interface 142.
- the operator of the control console 145 may, for example, be able to establish groups of MSs within the system 100 as talk groups or may change the membership of such groups, e.g. by adding MSs as new members to each group or by removing MSs as group members.
- the details relating to the membership and capabilities of restrictions on the various groups added at the user interface 142 may be delivered to a group management processor 144 and may be recorded by the group management processor 144 in the database 138.
- the group management processor 144 may be incorporated within the control console 145 as shown in FIG. 1, although it could be located elsewhere in the system 100, either as a separate component or as part of another functional component of the system 100, e.g. part of the zone controller 133.
- the operator of the control console 145 may also be able to patch existing groups together in a known manner by controlling a suitable group patching processor which carries out the patching operation, e.g. the group management processor 144, via the user interface 142.
- a suitable group patching processor which carries out the patching operation
- the group management processor 144 may be controlled by controlling a suitable group patching processor which carries out the patching operation, e.g. the group management processor 144, via the user interface 142.
- the action of 'patching' either joining or connecting, the groups including the first and second groups so that they may communicate together, may be carried out by insertion of suitable information at the user interface 142.
- the inserted information includes the identities of the groups to be patched together and a control signal indicating that a patching operation is required to be carried out.
- the group patching processor which is to carry out the patching may retrieve data relating to the first and second groups from the database 138 and may issue signals, as necessary, to ensure that MSs of the patched groups participate together in the same call (traffic communication).
- the configuration used to determine the method of patching e.g. by the group management processor 144, may be derived from the database 138 or provided by the control console 145.
- the system 100 also includes, for example operably connected to the group management processor 144, a translator 143.
- the translator 143 is a processor which may be incorporated within the control console 145, as shown in FIG. 1, or may alternatively be located elsewhere in the system 100, e.g.
- the translator 143 translates encrypted calls from one encrypted form to another as described later with reference to FIG. 3.
- the translator 143 also translates calls from an unencrypted form to an encrypted form using an encryption procedure.
- the translator 143 may also be used optionally to translate calls from an encrypted form to an unencrypted form using a decryption procedure, although such use may only be selected for use in circumstances when the security status of the call is unimportant.
- the translator 143 may translate calls taking place in an enlarged group formed by patching of smaller groups in which the smaller groups employ different encryption forms, e.g. in a manner described later with reference to FIG. 3.
- the translator 143 uses the encryption parameters, including encryption keys, available to the user terminals in each of the smaller groups employing the different encryption forms.
- the translator 143 may carry out a translation procedure in only one call in one enlarged group.
- the translator 143 may carry out translation procedures in different calls which take place in different specified enlarged groups, either at the same time or at different times, and the encryption parameters, such as encryption keys, used for translation of the calls in each of the different enlarged groups may generally be different, although they could be the same in some cases.
- the translator 143 may hold or have access to (e.g.
- a plurality of sets of data including encryption keys, each set relating to an encryption form used by a particular group, together with an identity of the group in which each of the keys and other data is to be used.
- the translator 143 may be a single processor or may comprise a plurality of processors, which may be located in the same part or different parts of the system 100.
- the translator 143 may be part of a processor having at least one other function in addition to translation.
- the functions of the translator 143 and of the group management processor 144 may be combined in a common processing unit.
- the translator 143 may comprise a single processor or different processors operable to carry out its different translation procedures, e.g. the different encryption and decryption procedures described later with reference to FIG. 3.
- the system 100 may not include a zone controller.
- another processor of the system 100 such as a processor of the control console 145, may carry out functions, such as routing and channel allocation, attributed herein to the zone controller 133.
- FIG. 2 is a flow chart of a method 200 of operation in the system 100, illustrating operation embodying the invention.
- a step 201 details of each MS are recorded in the database 138. The details may be recorded at different times for different MSs. The details may be entered by an operator of the control console 145 at the user interface 142.
- the control terminal 141 may send a signal indicating the details to be recorded in the database 138 either directly to the database 138 or via an intermediate processor, such as the zone controller 133.
- the details to be recorded in step 201 may be in pre-defined data fields of the database 138. Illustrative examples of data fields in which data may be entered in step 201 are as follows:
- an identity of the MS e.g. an Individual Subscriber Short Identity (ISSI) for an MS operable in a TETRA system;
- ISSI Individual Subscriber Short Identity
- step 203 which may be carried out before, at the same time as, or after step 201, group details are entered, e.g. initially at the user interface 142, for a particular group which is to operate in the system 100.
- a new group may be established by this action or details of an existing group may be changed.
- the details of the group may be recorded in the database 138 by a signal sent from the control terminal 141.
- the details of the group recorded may include its security capability.
- Each group established may have a security capability which is one of three possibilities, as follows: (a) the group may be encrypted only, meaning that each MS of the group can transmit and receive communications which are only in end-to-end encrypted form while the MS is in that group;
- the group may be clear only, meaning that each MS of the group can transmit and receive communications which are only in clear (unencrypted) form while the MS is in that group; or (c) the group may be selectable, meaning that each MS while in the group can transmit and/or receive communications which are clear or, if selected, each
- MS of the group can transmit and/or receive communications which are encrypted.
- each group may be configured (or re-configured) by an operator in step 203.
- Each MS of a given group may have a security capability which is fixed or selectable depending on the construction of the MS.
- its security capability may be determined at any particular time by either: (i) configuration of the MS (which may be selected manually by a user or automatically by receipt of a control signal from a control processor of the system 100) or (ii) by configuration of the security capability of the group(s) in which the MS is to participate; or (iii) by a combination of the two.
- a step 205 which may be carried out at the same time as step 201 or at a different time, at least one group membership of each MS is allocated. The membership may be recorded at different times for different MSs or for membership of different groups.
- the membership may be entered by an operator of the control console 145 at the user interface 142 and/or configured in the MS in a known way, e.g. by receipt of a control signal from the system 100, e.g. from the group management processor 144 via the control terminal 141.
- the control terminal 141 may send a signal indicating the membership details to be recorded in the database 138 either directly to the database 138 or via an intermediate processor, such as the zone controller 133.
- the operator of the control console 145 may, at the user interface 142, identify, by a group identity number, a group, or each of a plurality of groups, which each MS is to join as a member. Alternatively, or in addition, the operator may identify, by an MS identity, each MS that is to be a member of a given group.
- the MSs which are members of each group are usually operated by users in the same organisation, although the MSs do not need to be in the same communication cell of the system 100.
- the MSs 103, 113 and 123 shown in FIG. 1 could be members of a first group and the MSs 105, 115 and 125 shown in FIG. 1 could be members of a second group.
- each MS registers with the system 100.
- the MS seeks to establish a wireless link with a selected one of the BSs of the system 100 in a known way.
- the MS normally identifies itself to the BS and the BS verifies the identity before proceeding to allow the MS to become attached to it for service.
- This procedure generally establishes for each MS a link to the nearest BS; so, for example, the link 107 between the MS 103 and the BS 101 is established in this way.
- the BS to which the MS becomes attached may notify the zone controller 133 of the link which has been established and the zone controller 133 may register the same information, e.g. in the database 138. In this way, the current cell of each MS actively operating in the system 100 is recorded in the database 138.
- each MS attaches to a group.
- the relevant group is one which has already been configured in step 203 and membership of which is recorded in a memory of the MS as well as in the database 138.
- the group to which the MS currently attaches may be selected by a user of the MS, e.g. at a control interface (not shown) of the MS, or may be selected automatically by receipt of a control signal from the system 100. Details of the current attachment are recorded in the database 138.
- the MS is ready for participating in a group call.
- This is represented by a step 211 in the method 200.
- the expression 'call' relates generally to a communication between a first user terminal, e.g. a first MS, and one or more other user terminals, e.g. MSs, of traffic information.
- the traffic information may be user speech although it could alternatively, or in addition, be user communicated data, such as alphanumeric or other characters, picture information or a video stream.
- two or more already established groups which are smaller groups are patched together into an enlarged group.
- the patching operation may be carried out by a procedure which is initiated by an operator of the control console 145 at the user interface 142 identifying the groups to be patched and entering an indication that the groups identified are to be patched.
- Step 213 may, for example, be applied when the operator of the control console 145 becomes aware that the enlarged group needs to be formed for operational reasons, e.g. where an emergency situation has occurred and emergency service personnel of different units or different organisations need to participate in a single group call. Where more than two smaller groups are to be patched together, step 213 may be carried out in a series of patching stages.
- a suitable processor e.g.
- the group management processor 144 may proceed to issue an instruction, details of which may be entered into the database 138, indicating that the identified smaller groups are to be treated in the system 100 as patched as a single enlarged group.
- the single enlarged group may be given a single group identity which is different from the identities of the individual smaller groups making up the enlarged group. Details of the enlarged group, the smaller groups that were patched to form it, and the MSs that are members of it, may thus be recorded in the database 138.
- a step 217 the identity of the enlarged group is provided to, e.g. by the group management processor 144 or by the zone controller 133, and recorded by MSs that are members of the patched groups. These MSs may receive a signal, which may include an identity of the enlarged group, e.g. from the group management processor 144 or by the zone controller 133, instructing each of the MSs to attach to the enlarged group.
- the single enlarged group established in steps 213 and 215 may be a so-called 'supergroup' in which many groups existing over a wide area are patched together. In this case, standard signalling may be employed to indicate to MSs an identity of the supergroup.
- DGNA Dynamic Group Number Assignment
- a step 219 the set comprising the enlarged group formed in step 213 is divided, e.g. by the group management processor 144, into different sub-sets having different security capabilities. It is important to note that the division is applied to ensure, where required, that an encrypted call made in the enlarged group is not sent in clear form to any clear or selectable MS.
- the step is further used in the method 300 to be described with reference to FIG. 3.
- the division carried out in step 219 may be an automatic procedure, using data obtained from the database 138, especially data relating to MS and/or group identities and MS and/or group security capabilities.
- a step may be carried out after step 213 and before step 215 in order to determine if there can be one enlarged group or if sub-set groups are needed, and if so, how many.
- Step 219 may then follow where it is determined that one enlarged group can be formed.
- Step 215 may then follow step 219 to allow an identity of the enlarged group or of each sub-set group that is part of the enlarged group (one or more) to be established and recorded.
- Step 217 may then follow step 219 to provide to the MSs the appropriate identity of the enlarged group or of the sub-set group.
- the sub-sets formed by the division in step 219 are not necessarily the same as the groups that were patched to form the enlarged group.
- Each sub-set formed by the division may itself be an enlarged group, even a supergroup.
- the members of each sub-set may be MSs drawn from one or more of the original groups patched together in step 213.
- each of the sub-sets formed in step 219 comprises an integral number of the original smaller groups that were patched in step 213.
- the different sub-sets formed in step 219 have different security capabilities.
- the sub-sets may comprise only two sub-sets as follows: (i) an encrypted or secure sub-set; and (ii) a selectable-clear sub-set.
- the encrypted sub-set is a sub-set consisting of all of the MSs of the enlarged group which can transmit and receive calls only in encrypted form.
- the selectable-clear sub-set is all of the other MSs of the enlarged group.
- the MSs of the selectable-clear sub-set includes: (i) MSs in one or more groups that can transmit and receive calls only in clear (unencrypted) form; and (ii) MSs in one or more groups which can be selected to transmit and/or receive calls in either encrypted form or in clear form.
- the sub-set which each MS of the enlarged group joins or is connected to may be recorded in data in the database 138. Details of the allocation of the smaller groups to the enlarged group and the sub-sets of the enlarged group produced by step 219 may be recorded in data appertaining to the groups in the database 138.
- the enlarged group is ready to establish a group call with routing of the call to include, where appropriate, routing via the translator 143 to translate the call between one encrypted form and another encrypted form or from unencrypted form to one or more encrypted forms.
- FIG. 3 is a flow chart 300 illustrating how a call may take place in an enlarged group which is formed by patching of smaller groups in accordance with embodiments of the present invention.
- the enlarged group comprises mainly MSs; user terminals of the enlarged group are thus referred to as 'MSs'.
- the enlarged group and each sub-set of the enlarged group may also include one or more fixed terminals, such as control terminals, one or more traffic signal recorders and one or more control terminals, such as the control terminal 141.
- the method 300 begins in a step 301, in which a group patch is initiated and an enlarged group is created.
- Step 301 may be carried out as in the method 200 described earlier.
- a call set-up is requested in the enlarged group.
- This step may be carried out in a known manner.
- one of the MSs of the enlarged group a 'calling' MS, sends a call set-up request signal to its serving BS.
- the MS 103 may be the calling MS.
- the signal may be delivered onward by the serving BS to the zone controller 133.
- the call set up request signal indicates the group identity of the group which is to participate in the call.
- This may normally be the identity of one of the smaller groups which has been patched together to form the enlarged group although it could alternatively be the identity of the enlarged group which may have been notified to the calling MS and other MSs of the enlarged group or even the identity of a sub-set produced by step 303.
- the zone controller 133 may identify the enlarged group from the group identity provided.
- the zone controller 133 may refer to data held in the database 138 to identify the other participants of the identified enlarged group which are to participate in the call.
- the control console 145 (which may have created the patch) may make these identifications, and may send any needed call requests to the zone controller 133 to make sure all members of the enlarged group are set-up to receive the call of the originating MS.
- routing and one or more allocated channels for the requested call are established, e.g. by the zone controller 133, in a known manner.
- the routing may be a multicast tree route which includes various routers of the system 100 selected depending on the location of the cells of the respective groups and/or members of the groups which are to participate in the call and possibly also with reference to current loading of resources within the system 100.
- the routing is established also to include the translator 143, e.g. to operate as in steps 319 to 323, steps 329 to 333, or steps 339 and 341 to be described later.
- the communication channels e.g. specified time slots of a specified carrier frequency in a TETRA system, may also be allocated for the call by the zone controller 133.
- the method 300 proceeds with a step 309 in which the sub-set (sub-group) of the calling MS is determined, e.g. by the group management processor 144.
- the calling MS is identified to be either: (i) an 'encrypted' MS which is in the encrypted sub-set; or (ii) a 'selectable' or 'clear' MS which is in the 'selectable-clear' sub-set. If the calling MS is identified as being in the 'encrypted' sub-set, the method proceeds in a step 311. If the calling MS is identified as being in the 'selectable-clear' sub-set, the method proceeds in a step 313.
- the calling MS in the encrypted sub-set thus proceeds in step 311 to make the call, i.e. to transmit traffic information, in encrypted form.
- the calling MS may use a known procedure, e.g. as described in the Background section earlier, to encrypt the traffic information sent in step 311.
- the calling MS may use an encryption key previously and separately supplied in a known way to the calling MS and other encrypted MSs of the enlarged group.
- the encryption key used may be a single key to be used only in participation in the enlarged group call by the encrypted MS members of the enlarged group.
- the calling MS may include within the information it transmits synchronisation information to allow the encrypted MSs that receive the call to decrypt the call.
- the encrypted MSs of the enlarged group i.e.
- the MSs 113 and 115 may be members of the encrypted sub-set and may receive the call in step 315.
- the encrypted MSs that receive the call in encrypted form in step 315 decrypt the call.
- the encrypted MSs use a reverse of the encryption procedure (employed by the calling
- the translator 143 receives the call in encrypted form in a step 319.
- the translator 143 may relay the call in the same encrypted form in which it was received, if that is suitable for any selectable-clear groups that are to receive it.
- the translator 143 translates the call suitable for receipt by the selectable-clear sub-set in the case where the sub-set uses for encryption and decryption a different encryption parameter from that used by the originating encrypted sub-set, particularly the encrypted MS making the call.
- the different encryption parameter may be one or more of: (i) a different encryption key; (ii) a different encryption and decryption algorithm; and (iii) a different synchronisation parameter.
- Step 321 may thus be carried out by the translator 143 decrypting the encrypted call received in step 319 which was encrypted using a first encryption form and re-encrypting it using a second encryption form different from the first form, the first and second encryption forms using at least one encryption parameter which is different.
- This translation procedure requires the translator 143 to have previously received, e.g. in a known manner, prior to step 321 and recorded, e.g. in a memory (not shown) of the control console 145, the different parameters applicable.
- the translator 143 will have previously received and recorded the relevant keys, which are respectively: (i) the same encryption key as provided to the encrypted MS making the call in the first encrypted form so that the translator 143 may decrypt the call it receives in the first encrypted form; and (ii) the same encryption key as provided to the selectable-clear MSs that are to receive the call in the second encrypted form, so that the translator 143 may suitably re-encrypt the call suitable for receipt and decryption by those MSs.
- the translator 143 sends the translated call in the second encrypted form to the selectable-clear MSs.
- the MSs 105, 115 and 125 may be considered to be receiving MSs in a selectable-clear sub-set that receives the call in step 323.
- the selectable MSs that receive the call in the second encrypted form as sent by the translator 143 in step 323 decrypt the call.
- the selectable MSs use a reverse of the encryption procedure (employed by the translator 143 in step 323) involving the same previously and separately supplied encryption key used by the translator 143.
- the selectable MSs provide a clear output of the received traffic information to their users.
- a step 312 which follows step 311 and step 321 represents the clear MSs, which are MSs in the selectable-clear sub-set which are clear only MSs, receiving the encrypted call sent in step 311.
- the clear MSs do not have the capability to decrypt the encrypted call, so do not hear the call sent in step 311 or translated in step 321.
- the call sent in step 311 is received by MSs of the enlarged group only in an encrypted form. None of the MSs receives the call in clear form.
- Step 313 is the next step after step 309 in the case in which one of the MSs of the selectable-clear sub-set is the calling MS.
- the call may be made in either: (i) an encrypted form by one of the selectable MSs; or (ii) a clear form either by one of the clear MSs or by one of the selectable MSs.
- the MS 105 may be considered to be the calling MS in step 313.
- step 325 which follows step 313, the MSs in the selectable-clear sub-set of the originating MS of the enlarged group receive the call in the same encrypted form in which it was transmitted.
- step 327 which follows step 325, the selectable MSs that receive the call in same encrypted form in step 325 are able to decrypt the call.
- the selectable MSs may have been selected by their users to operate in an encrypted mode or may have been put automatically into that mode by receipt of a control signal from the system 100, e.g. from the group management processor 144 via the control terminal 141, e.g. following determination in steps 309 and 313 of the security mode of the calling MS.
- the selectable MSs use a reverse of the encryption procedure (employed by the calling MS in step 313) involving a previously and separately supplied encryption key.
- the selectable MSs provide a clear output of the received traffic information to their users.
- the translator 143 receives the call in encrypted form in a step 329.
- the translator 143 may relay the call in the same encrypted form as that in which it was received.
- the translator 143 translates the call suitable for receipt by the encrypted sub-set (sub-group) MSs in the case where the encrypted sub-set MSs use a different encryption form, e.g. an encryption key or other encryption parameter different from that used by the originating selectable-clear sub-set MS.
- Step 331 may thus be carried out by the translator 143 decrypting the encrypted call received in step 329 and re-encrypting it using another encryption parameter. This requires the translator 143 to receive, e.g.
- step 331 records prior to step 331 the appropriate different encryption parameters, e.g. different encryption keys. These parameters may be the same as those used by the translator 143 to carry out the reverse translation in step 321.
- the parameters required in step 331 are thus respectively: (i) the same encryption parameters as used by the selectable MS making the call in one encrypted form, e.g. the second encrypted form referred to in relation to steps 321, so that the translator 143 may decrypt the call it receives in that encrypted form; and (ii) the same encryption parameters as used by the encrypted sub-set MSs that are to receive the call, so that the translator 143 may suitably re-encrypt the call in another encrypted form suitable for those MSs, e.g. the first encrypted form referred to in relation to step 321.
- a step 333 the translator 143 sends the translated call in the second encrypted form to the encrypted sub-set MSs.
- step 335 which follows step 333, the encrypted MSs that receive the call in the second encrypted form as sent by the translator 143 in step 333 decrypt the call.
- the encrypted MSs use a reverse of the encryption procedure (employed by the translator 143 in step 333) involving previously supplied and recorded encryption parameters.
- the encrypted MSs provide a clear output of the received traffic information to their users.
- Step 312 already referred to above also follows step 313 (and step 333) and represents the clear MSs receiving the encrypted call sent in step 313 (and step 333).
- the clear MSs do not have the capability to decrypt the encrypted call, so do not hear the call sent in step 313 (or step 333). Thus, the call made in step 313 is received by MSs of the enlarged group only in an encrypted form. None of the MSs of the enlarged group receives the call in clear form.
- steps 337 and 339 follow.
- Selectable-clear sub-set MSs are able to receive the call in clear form in step 337.
- the translator 143 also receives the call in clear form in a step 339.
- the translator 143 translates the call from clear form to an encrypted form.
- the encrypted MSs i.e. the MSs that are members of the encrypted sub-set, receive the call in encrypted form from the translator 143.
- the encrypted MSs decrypt the call received in step 343 in the same manner as in step 317.
- the call which takes place in the method 300 may be continued in a known manner by an MS of the enlarged group other than the MS that was the original calling MS.
- Such a continuation is typically requested by one of the MSs sending promptly a continuation request signal to the zone controller 133. Detection of such a call continuation request made promptly to the zone controller 133 is indicated as a step 347.
- Step 347 results in the routing and channels allocated in step 307 remaining available for continuation of the call.
- the call continuation takes place by returning the method to step 309; step 309 and the appropriate steps following it are repeated.
- the 'calling' MS identified in step 309 is the MS that requested continuation of the call. That MS continues the call, i.e.
- control console 145 may be employed to make transmissions of traffic information within the enlarged patched group. Traffic information for transmission may be entered at the user interface 142 and transmitted by the control terminal 141. The transmissions may be made in encrypted or unencrypted form. Desirably, one of these forms is selected for all of the transmissions to be made by the control console 145.
- the control console 145 may thus be a member of the encrypted sub-set or of the selectable-clear sub-set, as appropriate, for this purpose.
- the translator 143 may be employed to carry out encryption of the information to be transmitted.
- more than two sub-sets may be created, although each sub-set would still be classified as either 'encrypted' or 'selectable-clear'.
- the behaviour of the MSs of each subset would therefore be as described above with reference to FIG. 3.
- communications about the group assignments may be made by DGNA signalling.
- the translator 143 may carry out all of the translation operations for the various sub-sets. Alternatively, translations required for different sub-sets of the same type, e.g. different encrypted sub-sets, may be carried out by different translators.
- At least two of the original groups may be connected together without the formation of a new enlarged group, e.g. a new supergroup, between them.
- a new enlarged group e.g. a new supergroup
- This is known in the art as a 'non-regroupable' patch.
- Such a connection may be made either with or without one or more enlarged groups being formed between other groups as well.
- calls to or from the members of the groups would be made as described above with reference to FIG. 3.
- the encrypted sub-set or in the selectable-clear sub-set referred to above there may be member groups that use different encryption forms, e.g. use at least one encryption parameter that is different in one group of the sub-set from that used in at least one other group of the sub-set.
- the translator 143 may be employed to translate the call into another encrypted form suitable for use by MSs in one of the other groups of the same sub-set.
- the translator 143 may, if required, carry out multiple translations for multiple recipient groups. In all cases, however, it may be arranged that clear MSs would not hear an encrypted call. Clear calls can, if required, be translated and encrypted (as in steps 339 and 341) before sending to another group or sub-set.
- any step shown in FIG. 3 requiring translation for the other sub-set is not used.
- the call set-up may be cancelled.
- 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 or 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.
- some embodiments may include 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 apparatus for synchronization in a digital mobile communication system as described herein.
- the non-processor circuits may include, but are not limited to, a radio receiver, a radio transmitter, signal drivers, clock circuits, power source circuits, and user input devices.
- these functions may be interpreted as steps of a method to perform the synchronization in a digital mobile communication system as described herein.
- 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.
- ASICs application specific integrated circuits
- Both the state machine and ASIC are considered herein as a 'processing device' for purposes of the foregoing discussion and claim language.
- an embodiment including a memory can be implemented as a computer-readable storage element having computer readable code stored thereon for programming a computer (e.g., comprising a processing device) to perform a method as described and claimed herein.
- Examples of such computer-readable storage elements include, but are not limited to, a hard disk, a CD-ROM, an optical storage device, a magnetic storage device, a Read Only Memory (ROM), a Programmable Read Only Memory (PROM), an Erasable Programmable Read Only Memory (EPROM), an Electrically Erasable Programmable Read Only Memory (EEPROM) and a Flash memory.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Hardware Design (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
A communication system (100) including a group management processor (144) operable to divide an enlarged group of user terminals formed by patching of smaller groups into sub-sets of user terminals including: (1) an encrypted sub-set of terminals (103, 113, 123) which are operable to undertake only encrypted communications; and (2) a selectable-clear sub-set of terminals (105, 115, 125) which includes: (i) selectable terminals that are able to undertake clear communications and, when selected, encrypted communications; and (ii) clear terminals that are operable to undertake only clear communications; and a translator (143) operable to translate a communication sent in a first encrypted form from a user terminal (103) of one of the sub-sets into the second encrypted form suitable for decryption by user terminals (105, 115) of the other sub-set. Also described is a method (300) and a processor (144) for use in the system.
Description
SECURE COMMUNICATION SYSTEM COMPRISING TERMINALS WITH DIFFERENT SECURITY CAPABILITY LEVELS
TECHNICAL FIELD
The technical field relates generally to a communication system, and a method and processor for use in the system. In particular, the technical field relates to a mobile communication system, and a method and processor for use in the system, in which communication terminals can have different security capability levels for sending or receiving encrypted communications to maintain security of user information communicated.
BACKGROUND
Many communication systems employ a procedure to protect sensitive communicated information by encryption especially if the information is to be sent via insecure channels, e.g. by wireless signals or via the internet. End-to-end encryption may be employed. This means that the encryption can be applied by a sending terminal or source of the information and is removed by a receiving terminal or destination of the information. Encryption is usually achieved by producing a random or pseudorandom sequence of numbers (binary digits) and using an encryption algorithm to combine the sequence with a secret user number, referred to as an 'encryption key', applied by a user of the sending terminal. The combination generates another number sequence which is known as a keystream. The keystream, or a portion of it, is then combined with the user speech, data or other information to be transmitted to encrypt the information. This combination may use a known combining function such as an exclusive OR (XOR) combining function.
The encryption process has to be synchronised between the transmitter in the sending terminal and the receiver in the receiving terminal. The transmitter must send information concerning the state of the encryption algorithm to the receiver to allow the receiver to synchronise its algorithm for decryption. The receiving terminal must
have the same encryption algorithm and the same encryption key as the transmitting terminal in order to decrypt the encrypted information it receives.
The system in which end-to-end encryption is employed may be a mobile communication system which is a cellular system. Such a system is one in which the user terminals include mobile stations, such as portable or vehicle carried telephones or radios, wireless enabled computing devices, personal digital assistants and the like, which can communicate via a network infrastructure. The infrastructure generally includes a plurality of base stations (base transceiver stations) which may be fixed in position and which may form a communication network. Each base station has one or more transceivers which serve mobile stations in a given region or area, known as a 'cell', by wireless communication. The cells of neighbouring base stations are often overlapping.
Communications to and from mobile stations in a cellular communication system include system control communications and traffic communications. System control communications are made to establish and maintain operation in the system in accordance with a pre-determined operating protocol. Traffic communications are made between user terminals, such as a mobile station and another terminal or a plurality of other terminals, which may include one or more mobile stations, to transmit user communicated information known as 'traffic' information; such information may include speech or data, e.g. numerical or text data, picture information or video information. A traffic communication between mobile stations which are currently in the same cell may be established by a single base station or even directly between the mobile stations without the involvement of a base station. Traffic communications between mobile stations which are currently in different cells may be established by involvement of a plurality of base stations serving the various cells.
An example of a cellular system is a TETRA system, which is a system operating according to the protocols defined by the TETRA operating standard defined by the European Telecommunications Standards Institute (ETSI). Such systems are widely used by (amongst others) emergency services organisations, such as police, fire brigades and ambulance services. In a TETRA system, wireless
communications to and from mobile stations and other user terminals are controlled in a synchronised sequence of time slots. The duration of each time slot is 14.167 ms, for example. A set of four slots represent four physical channels in a time division multiple access (TDMA) protocol and form, for example, one time frame of duration 56.67ms in an 18 time frame multiframe timing structure. Each communication is generally made on a channel allocated by the system infrastructure. The channel may thus comprise a series of specified time slots, and the slots may be on a specified carrier frequency.
In communication systems, such as TETRA systems, traffic information may be communicated between a transmitting terminal and a plurality of receiving terminals. The terminals may be referred to as a 'group' (or 'talk group') which may have an assigned identifier within the system. Each user terminal, which may be a mobile or fixed terminal, operating within the system may be a member of one or more groups. Allocation of membership to groups may be carried out by an operator having control or management functions in operation of the system. For example, the operator may be a person operating a terminal comprising a control console (also known as a 'dispatcher console') who may be responsible for other management or control duties such as issuing group work assignments using the system. Such an operator is often referred to as a 'dispatcher'. In use of communication systems, such as TETRA systems, it may be desirable to join or connect together different existing groups so that a traffic communication taking place in one group may be received by terminals of one or more other groups. For example, the different groups may be different police groups and the communication may be a call which should be heard by the members of the different police groups. The operation of joining or connecting groups together is known as 'patching'. Usually, patching is carried out by an operator, such as a dispatcher, using a communication terminal comprising a control console.
The user terminals operating in different groups in a communication system, such as a TETRA system, may have different security capabilities. For example, some terminals may be capable of communicating in a secure mode using end-to-end encryption. Other terminals may not be capable of using end-to-end encryption and
may therefore communicate in a clear mode, in other words, a mode in which wireless communications are unencrypted. Where groups are to be patched together and the groups have different security capabilities and normally communicate in different modes, the patching process may be difficult to achieve and operational problems may result. In particular, it may be desirable to allow communications to be made as widely as possible to all members of a patched group, without degrading the security of communications by allowing encrypted communications to be retransmitted in a clear form.
Thus, there exists a need for a system, a method and a processor for use in communications, especially for use in mobile communications, which addresses at least some of the shortcomings of past and present systems, methods and processors for use in group communications.
BRIEF DESCRIPTION OF THE ACCOMPANYING DRAWINGS The accompanying drawings, in which like reference numerals refer to identical or functionally similar items throughout the separate views which, together with the detailed description below, are incorporated in and form part of this patent specification and serve to further illustrate various embodiments of concepts that include the claimed invention, and to explain various principles and advantages of those embodiments.
FIG. 1 is a block schematic diagram of an illustrative communication system 100 which may be adapted in accordance with embodiments of the invention.
FIG. 2 is a flow diagram of a method of operation embodying the invention in the system of FIG. 1. FIG. 3 is a flow diagram of a further method of operation embodying the invention in the system of FIG. 1.
Skilled artisans will appreciate that items shown in the accompanying drawings are illustrated for simplicity and clarity and have not necessarily been drawn to scale. For example, the dimensions of some of the items may be exaggerated relative to other items to assist understanding of various embodiments. In addition, the description and drawings do not necessarily require the order illustrated. 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 various embodiments 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. Thus, it will be appreciated that for simplicity and clarity of illustration, common and well-understood items that are useful or necessary in a commercially feasible embodiment may not be depicted in order to facilitate a less obstructed view of these various embodiments.
DETAILED DESCRIPTION
Generally speaking, pursuant to the various embodiments of the invention to be described, there is provided an improved communication system, and a method and processor for use therein. The communication system includes a group management processor operable to divide an enlarged group of user terminals formed by patching of smaller groups into sub-sets of user terminals including: (1) at least one encrypted sub-set of terminals which are operable to undertake only encrypted communications; and (2) at least one selectable-clear sub-set of terminals which includes: (i) selectable terminals that are able to undertake clear communications and, when selected, encrypted communications; and (ii) clear terminals that are operable to undertake only clear communications; and a translator operable to translate a communication sent in a first encrypted form from a user terminal of one of the sub-sets into a second encrypted form suitable for decryption by user terminals of another of the sub-sets.
In the improved communication system, the translator may conveniently operate by translating an encrypted communication received in the first encrypted form into the second encrypted form by decrypting the communication of the first encrypted form and re-encrypting the decrypted communication into the second encrypted form. The first encrypted form and the second encrypted form may use at least one encryption parameter which differs between the first encrypted form and the second encrypted form. The at least one encryption parameter which differs may be selected from: (i) an encryption key; (ii) an encryption algorithm; (iii) a synchronisation parameter.
The system may include a group patching processor operable to patch together communication resources of smaller groups of user terminals to form the enlarged group of the terminals.
The functions of the group management processor and of the group patching processor may be operated in a combined processor or in separate processors. A combined processor or console may incorporate the function of the translator as well as the function of group management processor and optionally the group patching processor.
The improved system embodying the invention allows communications to be made as widely as possible to all members of an enlarged patched group, without degrading the security of communications by allowing encrypted communications to be retransmitted in a clear form.
The improved system allows efficient operation within a patched enlarged group including user terminals of smaller groups having different security capabilities. The operation may take place in a manner which is consistent in different operational scenarios. All user terminals, such as mobile stations operating in an enlarged group formed or connected together by patching, may receive a call taking place in the enlarged group irrespective of the security capability of the receiving terminal relative to that of the transmitting terminal provided that the security state of an encrypted call is not degraded to clear, if such degrading is not desired. Users of the terminals do not need to be aware that patching of resources of different capabilities has been carried out.
The improved system embodying the invention may suitably be a system in which end-to-end encrypted communications may take place by multicast transmission, such as a mobile cellular communication system or a wired network or the internet. Where the system is a mobile cellular communication system, it may for example be a TETRA system, i.e. a system which operates in accordance with the protocols defined by the TETRA standard, or an APCO 25 system, i.e. a system which operates in accordance with the protocols defined by the APCO Project 25 standard defined by the Association of Public-Safety Communications Officials- International, Inc.
Those skilled in the art will appreciate that these recognized advantages and other advantages described herein are merely illustrative and are not meant to be a complete rendering of all of the advantages of the various embodiments of the invention. Referring now to the accompanying drawings, and in particular to FIG. 1, there is shown a block schematic diagram of a communication system 100 which may be adapted to operate in accordance with embodiments of the invention. The system 100 is a cellular communication system, for example. The system 100 includes a fixed infrastructure including a plurality of base stations (BSs) which serve with wireless communications mobile stations (MSs) in a cell defined by the position of each of the BSs. It will be apparent to those skilled in the art that the system 100 and the component operational units which are to be described as operating therein, particularly the BSs and the MSs, may take a number of known forms. Thus, the form of the system 100, and of its operational component units, to be described should be regarded as illustrative rather than limiting. The system 100 may be a TETRA system, i.e. may operate in accordance with the protocols defined by the TETRA standard, although it could alternatively be a system operating according to another industry standard for communications, e.g. wireless communications, in which multicast transmissions are possible, such as an APCO 25 system. The system 100 includes a BS 101 which provides wireless communication service to user terminals in the form of MSs within range of the BS 101, i.e. within a cell having the BS 101 at its centre. Two such MSs, namely MS 103 and MS 105, are shown having respectively radio links 107 and 109 to the BS 101. The system 100 also includes another BS 111 which provides wireless communication service to user terminals in the form of MSs within range of the BS 111, i.e. within a cell having the BS 111 at its centre. Two such MSs, namely MS 113 and MS 115, are shown having respectively radio links 117 and 119 to the BS 111. The system 100 also includes a BS 121 which provides wireless communication service to user terminals in the form of MSs (mobile stations) within range of the BS 121, i.e. within a cell having the BS 121 at its centre. Two such MSs, namely MS 123 and MS 125, are shown having respectively radio links 127 and 129 to the BS 121.
The BS 101 is operationally associated via a link 104 with a router 102, e.g. a core router, which routes communications from the BS 101 (on behalf of MSs served by the BS 101) to other terminals, e.g. MSs served by other BSs, within the system 100 and in other systems (not shown) operably connected to the system 100. The router 102 also routes incoming communications to the BS 101. The BS 111 is operationally associated via a link 114 with a router 112, e.g. a core router, which routes communications from the BS 111 (on behalf of MSs served by the BS 111) to other terminals, e.g. MSs served by other BSs, within the system 100 and in other systems operably connected to the system 100. The router 112 also routes incoming communications to the BS 111. The BS 121 is operationally associated via a link 124 with a router 122, e.g. a core router, which routes communications from the BS 121 (on behalf of MSs served by the BS 121) to other terminals, e.g. MSs served by other BSs, within the system 100 and in other systems operably connected to the system 100. The router 122 also routes incoming communications to the BS 121. The routers 102, 112 and 122 are operably connected via further links 132, 134 and 136 to a network 131 which may, for example, include a plurality of further routers and/or other nodes (not shown) which may include one or more telephony gateways and/or gateways to other communication systems. The routers 102, 112 and 122 are mutually connected to one another and to other routers (not shown) via the network 131. The links 104, 114, 124, 132, 134 and 136, and individual links (not shown) between nodes and/or routers (not shown) in the network 131, may comprise wired and/or wireless links. The routers 102, 112 and 122, together with any routers in the network 131, form a router network in the system 100. Although each of these routers is shown in FIG. 1 serving one associated BS, each router of the router network may serve each of a plurality of associated BSs, as will be apparent to those skilled in the art.
The system 100 may include a zone controller 133, which may be one of a plurality of zone controllers operating within the system 100. The zone controller 133 is a controller which comprises a processor which provides co-ordination and control of operation involving the different BSs, routers and other nodes of the system 100. For example, the zone controller 133 may control allocation of routing paths and
communication channels employed for communication by BSs and their served MSs within the system 100 in a given zone of the system. The zone controller 133 has a link 135 to the router 102, a link 137 to the router 112 and a link 139 to the router 122. The links 135, 137 and 139 may be wired and/or wireless links. The links 135, 137 and 139 are shown as direct links but could optionally pass via the network 131. The zone controller 133 is also operably connected to a database 138 which holds details relating to composition of the system 100 including current identities and locations of MSs and membership of groups of MSs operating within the system 100. The database 138 may be a single database unit or may comprise a plurality of units, which may be located in the same part or different parts of the system 100.
The system 100 includes a control console 145 operably connected to the infrastructure of the system 100, in particular to the database 138, the zone controller 133 and the network 131 (and thereby to user terminals of the system 100). The control console 145 may be a fixed installation within the system 100. The control console 145 includes various operably interconnected components including a control terminal 141, via which communications with user terminals of the system 100 may be made, and a user interface 142. The user interface 142 may comprise a single interface unit or a plurality of interface units at which an operator may in a known manner apply input control signals and information, and monitor activities being controlled within the system 100. The control console 145 and its constituent components may thereby be operated via the user interface 142 by an operator who is a system manager or other person having authority to change operational conditions within the system 100 via inputs made at the user interface 142. The operator of the control console 145 may, for example, be able to establish groups of MSs within the system 100 as talk groups or may change the membership of such groups, e.g. by adding MSs as new members to each group or by removing MSs as group members. The details relating to the membership and capabilities of restrictions on the various groups added at the user interface 142 may be delivered to a group management processor 144 and may be recorded by the group management processor 144 in the database 138. The group management processor 144 may be incorporated within the control console 145 as shown in FIG. 1, although it could be located elsewhere in the
system 100, either as a separate component or as part of another functional component of the system 100, e.g. part of the zone controller 133.
The operator of the control console 145 may also be able to patch existing groups together in a known manner by controlling a suitable group patching processor which carries out the patching operation, e.g. the group management processor 144, via the user interface 142. For example, if a call is established between a first group of MSs and it is required to join or connect a second group of MSs (and possibly other groups) into the same call, the action of 'patching', either joining or connecting, the groups including the first and second groups so that they may communicate together, may be carried out by insertion of suitable information at the user interface 142. The inserted information includes the identities of the groups to be patched together and a control signal indicating that a patching operation is required to be carried out. The group patching processor which is to carry out the patching, e.g. the group management processor 144, may retrieve data relating to the first and second groups from the database 138 and may issue signals, as necessary, to ensure that MSs of the patched groups participate together in the same call (traffic communication). The configuration used to determine the method of patching, e.g. by the group management processor 144, may be derived from the database 138 or provided by the control console 145. The system 100 also includes, for example operably connected to the group management processor 144, a translator 143. The translator 143 is a processor which may be incorporated within the control console 145, as shown in FIG. 1, or may alternatively be located elsewhere in the system 100, e.g. as a separate processor or as part of another functional processor, such as the zone controller 133. The translator 143 translates encrypted calls from one encrypted form to another as described later with reference to FIG. 3. The translator 143 also translates calls from an unencrypted form to an encrypted form using an encryption procedure. The translator 143 may also be used optionally to translate calls from an encrypted form to an unencrypted form using a decryption procedure, although such use may only be selected for use in circumstances when the security status of the call is unimportant. The translator 143 may translate calls taking place in an enlarged group formed by patching of smaller
groups in which the smaller groups employ different encryption forms, e.g. in a manner described later with reference to FIG. 3.
In order to carry out the translation operation, the translator 143 uses the encryption parameters, including encryption keys, available to the user terminals in each of the smaller groups employing the different encryption forms. The translator 143 may carry out a translation procedure in only one call in one enlarged group. Alternatively, the translator 143 may carry out translation procedures in different calls which take place in different specified enlarged groups, either at the same time or at different times, and the encryption parameters, such as encryption keys, used for translation of the calls in each of the different enlarged groups may generally be different, although they could be the same in some cases. Thus, the translator 143 may hold or have access to (e.g. in an associated memory of the control console 145 or in the database 138) a plurality of sets of data, including encryption keys, each set relating to an encryption form used by a particular group, together with an identity of the group in which each of the keys and other data is to be used.
The translator 143 may be a single processor or may comprise a plurality of processors, which may be located in the same part or different parts of the system 100. The translator 143 may be part of a processor having at least one other function in addition to translation. For example, the functions of the translator 143 and of the group management processor 144 may be combined in a common processing unit.
The translator 143 may comprise a single processor or different processors operable to carry out its different translation procedures, e.g. the different encryption and decryption procedures described later with reference to FIG. 3.
In a simpler form of the system 100, the system 100 may not include a zone controller. In that case, another processor of the system 100, such as a processor of the control console 145, may carry out functions, such as routing and channel allocation, attributed herein to the zone controller 133.
FIG. 2 is a flow chart of a method 200 of operation in the system 100, illustrating operation embodying the invention. In a step 201, details of each MS are recorded in the database 138. The details may be recorded at different times for different MSs. The details may be entered by an operator of the control console 145 at
the user interface 142. The control terminal 141 may send a signal indicating the details to be recorded in the database 138 either directly to the database 138 or via an intermediate processor, such as the zone controller 133. The details to be recorded in step 201 may be in pre-defined data fields of the database 138. Illustrative examples of data fields in which data may be entered in step 201 are as follows:
(i) an identity of the MS, e.g. an Individual Subscriber Short Identity (ISSI) for an MS operable in a TETRA system;
(ii) an indication of an organisation (e.g. police), department and unit in which a user of the MS will operate; (iii) an indication of a seniority or rank of the user;
(iv) an indication of any privileges provided to the user of the MS and of any restrictions on use of the MS by its user;
(v) a location of a communication cell or zone which will be considered as the home location of the MS; or (vi) a security capability of the MS.
In a step 203, which may be carried out before, at the same time as, or after step 201, group details are entered, e.g. initially at the user interface 142, for a particular group which is to operate in the system 100. A new group may be established by this action or details of an existing group may be changed. The details of the group may be recorded in the database 138 by a signal sent from the control terminal 141. The details of the group recorded may include its security capability. Each group established may have a security capability which is one of three possibilities, as follows: (a) the group may be encrypted only, meaning that each MS of the group can transmit and receive communications which are only in end-to-end encrypted form while the MS is in that group;
(b) the group may be clear only, meaning that each MS of the group can transmit and receive communications which are only in clear (unencrypted) form while the MS is in that group; or
(c) the group may be selectable, meaning that each MS while in the group can transmit and/or receive communications which are clear or, if selected, each
MS of the group can transmit and/or receive communications which are encrypted.
The security capability of each group may be configured (or re-configured) by an operator in step 203.
Each MS of a given group may have a security capability which is fixed or selectable depending on the construction of the MS. Where the security capability is selectable, its security capability may be determined at any particular time by either: (i) configuration of the MS (which may be selected manually by a user or automatically by receipt of a control signal from a control processor of the system 100) or (ii) by configuration of the security capability of the group(s) in which the MS is to participate; or (iii) by a combination of the two. In a step 205, which may be carried out at the same time as step 201 or at a different time, at least one group membership of each MS is allocated. The membership may be recorded at different times for different MSs or for membership of different groups. The membership may be entered by an operator of the control console 145 at the user interface 142 and/or configured in the MS in a known way, e.g. by receipt of a control signal from the system 100, e.g. from the group management processor 144 via the control terminal 141. The control terminal 141 may send a signal indicating the membership details to be recorded in the database 138 either directly to the database 138 or via an intermediate processor, such as the zone controller 133. The operator of the control console 145 may, at the user interface 142, identify, by a group identity number, a group, or each of a plurality of groups, which each MS is to join as a member. Alternatively, or in addition, the operator may identify, by an MS identity, each MS that is to be a member of a given group.
The MSs which are members of each group are usually operated by users in the same organisation, although the MSs do not need to be in the same communication cell of the system 100. Thus, for example, the MSs 103, 113 and 123
shown in FIG. 1 could be members of a first group and the MSs 105, 115 and 125 shown in FIG. 1 could be members of a second group.
In a step 207, each MS registers with the system 100. When each MS is first operated in an active mode after a period of inactivity, the MS seeks to establish a wireless link with a selected one of the BSs of the system 100 in a known way. The MS normally identifies itself to the BS and the BS verifies the identity before proceeding to allow the MS to become attached to it for service. This procedure generally establishes for each MS a link to the nearest BS; so, for example, the link 107 between the MS 103 and the BS 101 is established in this way. The BS to which the MS becomes attached may notify the zone controller 133 of the link which has been established and the zone controller 133 may register the same information, e.g. in the database 138. In this way, the current cell of each MS actively operating in the system 100 is recorded in the database 138.
In a step 209, which may take place during or after registration in step 207, each MS attaches to a group. This means that the MS actively joins or is connected to the group, causing a notification signal to the system 100, e.g. by the MS. The relevant group is one which has already been configured in step 203 and membership of which is recorded in a memory of the MS as well as in the database 138. Where the MS is a member of several groups, the group to which the MS currently attaches may be selected by a user of the MS, e.g. at a control interface (not shown) of the MS, or may be selected automatically by receipt of a control signal from the system 100. Details of the current attachment are recorded in the database 138.
Following each MS successfully registering in step 207 and successfully attaching to a group in step 209, the MS is ready for participating in a group call. This is represented by a step 211 in the method 200. In this specification, the expression 'call' relates generally to a communication between a first user terminal, e.g. a first MS, and one or more other user terminals, e.g. MSs, of traffic information. The traffic information may be user speech although it could alternatively, or in addition, be user communicated data, such as alphanumeric or other characters, picture information or a video stream.
In a step 213, two or more already established groups which are smaller groups are patched together into an enlarged group. The patching operation may be carried out by a procedure which is initiated by an operator of the control console 145 at the user interface 142 identifying the groups to be patched and entering an indication that the groups identified are to be patched. Step 213 may, for example, be applied when the operator of the control console 145 becomes aware that the enlarged group needs to be formed for operational reasons, e.g. where an emergency situation has occurred and emergency service personnel of different units or different organisations need to participate in a single group call. Where more than two smaller groups are to be patched together, step 213 may be carried out in a series of patching stages. When the relevant information about the required patching has been entered at the user interface 142, one or more signals, including the entered information, may be delivered to a suitable processor, e.g. the group management processor 144, to effect the patching operation in a known way, e.g. using pre-recorded operational algorithms and data retrieved from the database 138. The group management processor 144 (or another processor, such as the zone controller 133) may proceed to issue an instruction, details of which may be entered into the database 138, indicating that the identified smaller groups are to be treated in the system 100 as patched as a single enlarged group. The single enlarged group may be given a single group identity which is different from the identities of the individual smaller groups making up the enlarged group. Details of the enlarged group, the smaller groups that were patched to form it, and the MSs that are members of it, may thus be recorded in the database 138. Establishment and recording of the enlarged group are indicated in the method 200 by the step 215. In a step 217, the identity of the enlarged group is provided to, e.g. by the group management processor 144 or by the zone controller 133, and recorded by MSs that are members of the patched groups. These MSs may receive a signal, which may include an identity of the enlarged group, e.g. from the group management processor 144 or by the zone controller 133, instructing each of the MSs to attach to the enlarged group.
The single enlarged group established in steps 213 and 215 may be a so-called 'supergroup' in which many groups existing over a wide area are patched together. In this case, standard signalling may be employed to indicate to MSs an identity of the supergroup. In particular, where the system 100 is a TETRA system, Dynamic Group Number Assignment (DGNA) signalling may be employed in step 217 in which each MS on one or more of the patch groups is notified, e.g. by the zone controller 133, of the identity of the supergroup.
In a step 219, the set comprising the enlarged group formed in step 213 is divided, e.g. by the group management processor 144, into different sub-sets having different security capabilities. It is important to note that the division is applied to ensure, where required, that an encrypted call made in the enlarged group is not sent in clear form to any clear or selectable MS. The step is further used in the method 300 to be described with reference to FIG. 3. The division carried out in step 219 may be an automatic procedure, using data obtained from the database 138, especially data relating to MS and/or group identities and MS and/or group security capabilities.
In an alternative form of the method 200, a step may be carried out after step 213 and before step 215 in order to determine if there can be one enlarged group or if sub-set groups are needed, and if so, how many. Step 219 may then follow where it is determined that one enlarged group can be formed. Step 215 may then follow step 219 to allow an identity of the enlarged group or of each sub-set group that is part of the enlarged group (one or more) to be established and recorded. Step 217 may then follow step 219 to provide to the MSs the appropriate identity of the enlarged group or of the sub-set group.
The sub-sets formed by the division in step 219 are not necessarily the same as the groups that were patched to form the enlarged group. Each sub-set formed by the division may itself be an enlarged group, even a supergroup. In other words, the members of each sub-set may be MSs drawn from one or more of the original groups patched together in step 213. Conveniently, each of the sub-sets formed in step 219 comprises an integral number of the original smaller groups that were patched in step 213.
The different sub-sets formed in step 219 have different security capabilities. The sub-sets may comprise only two sub-sets as follows: (i) an encrypted or secure sub-set; and (ii) a selectable-clear sub-set. The encrypted sub-set is a sub-set consisting of all of the MSs of the enlarged group which can transmit and receive calls only in encrypted form. The selectable-clear sub-set is all of the other MSs of the enlarged group. The MSs of the selectable-clear sub-set includes: (i) MSs in one or more groups that can transmit and receive calls only in clear (unencrypted) form; and (ii) MSs in one or more groups which can be selected to transmit and/or receive calls in either encrypted form or in clear form. The sub-set which each MS of the enlarged group joins or is connected to may be recorded in data in the database 138. Details of the allocation of the smaller groups to the enlarged group and the sub-sets of the enlarged group produced by step 219 may be recorded in data appertaining to the groups in the database 138.
Following the method 200, the enlarged group is ready to establish a group call with routing of the call to include, where appropriate, routing via the translator 143 to translate the call between one encrypted form and another encrypted form or from unencrypted form to one or more encrypted forms.
FIG. 3 is a flow chart 300 illustrating how a call may take place in an enlarged group which is formed by patching of smaller groups in accordance with embodiments of the present invention. In the following description of the method 300, it is assumed that the enlarged group comprises mainly MSs; user terminals of the enlarged group are thus referred to as 'MSs'. However, it should be noted that the enlarged group and each sub-set of the enlarged group may also include one or more fixed terminals, such as control terminals, one or more traffic signal recorders and one or more control terminals, such as the control terminal 141.
The method 300 begins in a step 301, in which a group patch is initiated and an enlarged group is created. Step 301 may be carried out as in the method 200 described earlier.
In a step 303, the enlarged group is divided into sub-sets in the manner of step 219 described earlier.
Next, in a step 305, a call set-up is requested in the enlarged group. This step may be carried out in a known manner. Typically, one of the MSs of the enlarged group, a 'calling' MS, sends a call set-up request signal to its serving BS. For the purposes of illustration, the MS 103 may be the calling MS. The signal may be delivered onward by the serving BS to the zone controller 133. The call set up request signal indicates the group identity of the group which is to participate in the call. This may normally be the identity of one of the smaller groups which has been patched together to form the enlarged group although it could alternatively be the identity of the enlarged group which may have been notified to the calling MS and other MSs of the enlarged group or even the identity of a sub-set produced by step 303.
In each of these cases, the zone controller 133 may identify the enlarged group from the group identity provided. The zone controller 133 may refer to data held in the database 138 to identify the other participants of the identified enlarged group which are to participate in the call. Alternatively, the control console 145 (which may have created the patch) may make these identifications, and may send any needed call requests to the zone controller 133 to make sure all members of the enlarged group are set-up to receive the call of the originating MS.
In a step 307 which follows step 305, routing and one or more allocated channels for the requested call are established, e.g. by the zone controller 133, in a known manner. The routing may be a multicast tree route which includes various routers of the system 100 selected depending on the location of the cells of the respective groups and/or members of the groups which are to participate in the call and possibly also with reference to current loading of resources within the system 100. The routing is established also to include the translator 143, e.g. to operate as in steps 319 to 323, steps 329 to 333, or steps 339 and 341 to be described later. The communication channels, e.g. specified time slots of a specified carrier frequency in a TETRA system, may also be allocated for the call by the zone controller 133.
The method 300 proceeds with a step 309 in which the sub-set (sub-group) of the calling MS is determined, e.g. by the group management processor 144. In other words, the calling MS is identified to be either: (i) an 'encrypted' MS which is in the
encrypted sub-set; or (ii) a 'selectable' or 'clear' MS which is in the 'selectable-clear' sub-set. If the calling MS is identified as being in the 'encrypted' sub-set, the method proceeds in a step 311. If the calling MS is identified as being in the 'selectable-clear' sub-set, the method proceeds in a step 313. The calling MS in the encrypted sub-set thus proceeds in step 311 to make the call, i.e. to transmit traffic information, in encrypted form. The calling MS, may use a known procedure, e.g. as described in the Background section earlier, to encrypt the traffic information sent in step 311. The calling MS may use an encryption key previously and separately supplied in a known way to the calling MS and other encrypted MSs of the enlarged group. The encryption key used may be a single key to be used only in participation in the enlarged group call by the encrypted MS members of the enlarged group. The calling MS may include within the information it transmits synchronisation information to allow the encrypted MSs that receive the call to decrypt the call. In a step 315 which follows step 311, the encrypted MSs of the enlarged group, i.e. the MSs that are in the same encrypted sub-set (sub-group), receive the call in the same encrypted form in which it was transmitted. For illustration purposes, the MSs 113 and 115 may be members of the encrypted sub-set and may receive the call in step 315. In a step 317 which follows step 315, the encrypted MSs that receive the call in encrypted form in step 315 decrypt the call. The encrypted MSs use a reverse of the encryption procedure (employed by the calling
MS in step 311) involving the previously and separately supplied encryption key. The encrypted MSs provide a clear output of the received traffic information to their users. Following step 311, the translator 143 receives the call in encrypted form in a step 319. The translator 143 may relay the call in the same encrypted form in which it was received, if that is suitable for any selectable-clear groups that are to receive it. Alternatively, or in addition, in a step 321, the translator 143 translates the call suitable for receipt by the selectable-clear sub-set in the case where the sub-set uses for encryption and decryption a different encryption parameter from that used by the originating encrypted sub-set, particularly the encrypted MS making the call. The different encryption parameter may be one or more of: (i) a different encryption key; (ii) a different encryption and decryption algorithm; and (iii) a different
synchronisation parameter. Step 321 may thus be carried out by the translator 143 decrypting the encrypted call received in step 319 which was encrypted using a first encryption form and re-encrypting it using a second encryption form different from the first form, the first and second encryption forms using at least one encryption parameter which is different. This translation procedure requires the translator 143 to have previously received, e.g. in a known manner, prior to step 321 and recorded, e.g. in a memory (not shown) of the control console 145, the different parameters applicable. For example, where the different parameters are different encryption keys, the translator 143 will have previously received and recorded the relevant keys, which are respectively: (i) the same encryption key as provided to the encrypted MS making the call in the first encrypted form so that the translator 143 may decrypt the call it receives in the first encrypted form; and (ii) the same encryption key as provided to the selectable-clear MSs that are to receive the call in the second encrypted form, so that the translator 143 may suitably re-encrypt the call suitable for receipt and decryption by those MSs.
In a step 323, the translator 143 sends the translated call in the second encrypted form to the selectable-clear MSs. For illustration purposes, the MSs 105, 115 and 125 may be considered to be receiving MSs in a selectable-clear sub-set that receives the call in step 323. In a step 324 which follows step 323, the selectable MSs that receive the call in the second encrypted form as sent by the translator 143 in step 323 decrypt the call. The selectable MSs use a reverse of the encryption procedure (employed by the translator 143 in step 323) involving the same previously and separately supplied encryption key used by the translator 143. The selectable MSs provide a clear output of the received traffic information to their users. A step 312 which follows step 311 and step 321 represents the clear MSs, which are MSs in the selectable-clear sub-set which are clear only MSs, receiving the encrypted call sent in step 311. The clear MSs do not have the capability to decrypt the encrypted call, so do not hear the call sent in step 311 or translated in step 321. Thus, the call sent in step 311 is received by MSs of the enlarged group only in an encrypted form. None of the MSs receives the call in clear form.
Step 313 is the next step after step 309 in the case in which one of the MSs of the selectable-clear sub-set is the calling MS. The call may be made in either: (i) an encrypted form by one of the selectable MSs; or (ii) a clear form either by one of the clear MSs or by one of the selectable MSs. For illustration purposes, the MS 105 may be considered to be the calling MS in step 313.
In a step 325 which follows step 313, the MSs in the selectable-clear sub-set of the originating MS of the enlarged group receive the call in the same encrypted form in which it was transmitted. In a step 327 which follows step 325, the selectable MSs that receive the call in same encrypted form in step 325 are able to decrypt the call. In order to be able to carry out the decryption operation, the selectable MSs may have been selected by their users to operate in an encrypted mode or may have been put automatically into that mode by receipt of a control signal from the system 100, e.g. from the group management processor 144 via the control terminal 141, e.g. following determination in steps 309 and 313 of the security mode of the calling MS. In carrying out the decryption operation, the selectable MSs use a reverse of the encryption procedure (employed by the calling MS in step 313) involving a previously and separately supplied encryption key. The selectable MSs provide a clear output of the received traffic information to their users.
Following step 313, the translator 143 receives the call in encrypted form in a step 329. The translator 143 may relay the call in the same encrypted form as that in which it was received. Alternatively, or in addition, in a step 331, the translator 143 translates the call suitable for receipt by the encrypted sub-set (sub-group) MSs in the case where the encrypted sub-set MSs use a different encryption form, e.g. an encryption key or other encryption parameter different from that used by the originating selectable-clear sub-set MS. Step 331 may thus be carried out by the translator 143 decrypting the encrypted call received in step 329 and re-encrypting it using another encryption parameter. This requires the translator 143 to receive, e.g. in a known manner, and record prior to step 331 the appropriate different encryption parameters, e.g. different encryption keys. These parameters may be the same as those used by the translator 143 to carry out the reverse translation in step 321. The parameters required in step 331 are thus respectively: (i) the same encryption
parameters as used by the selectable MS making the call in one encrypted form, e.g. the second encrypted form referred to in relation to steps 321, so that the translator 143 may decrypt the call it receives in that encrypted form; and (ii) the same encryption parameters as used by the encrypted sub-set MSs that are to receive the call, so that the translator 143 may suitably re-encrypt the call in another encrypted form suitable for those MSs, e.g. the first encrypted form referred to in relation to step 321.
In a step 333, the translator 143 sends the translated call in the second encrypted form to the encrypted sub-set MSs. In a step 335 which follows step 333, the encrypted MSs that receive the call in the second encrypted form as sent by the translator 143 in step 333 decrypt the call. The encrypted MSs use a reverse of the encryption procedure (employed by the translator 143 in step 333) involving previously supplied and recorded encryption parameters. The encrypted MSs provide a clear output of the received traffic information to their users. Step 312 already referred to above also follows step 313 (and step 333) and represents the clear MSs receiving the encrypted call sent in step 313 (and step 333). The clear MSs do not have the capability to decrypt the encrypted call, so do not hear the call sent in step 313 (or step 333). Thus, the call made in step 313 is received by MSs of the enlarged group only in an encrypted form. None of the MSs of the enlarged group receives the call in clear form.
Where the call made in step 313 is in a clear (unencrypted) form, steps 337 and 339 follow. Selectable-clear sub-set MSs are able to receive the call in clear form in step 337. The translator 143 also receives the call in clear form in a step 339. In a step 341 which follows step 339, the translator 143 translates the call from clear form to an encrypted form. In a step 343, the encrypted MSs, i.e. the MSs that are members of the encrypted sub-set, receive the call in encrypted form from the translator 143. In a step 345, the encrypted MSs decrypt the call received in step 343 in the same manner as in step 317. These MSs provide a clear output of the received traffic information to their users. The call which takes place in the method 300 may be continued in a known manner by an MS of the enlarged group other than the MS that was the original
calling MS. Such a continuation is typically requested by one of the MSs sending promptly a continuation request signal to the zone controller 133. Detection of such a call continuation request made promptly to the zone controller 133 is indicated as a step 347. Step 347 results in the routing and channels allocated in step 307 remaining available for continuation of the call. The call continuation takes place by returning the method to step 309; step 309 and the appropriate steps following it are repeated. In this case, the 'calling' MS identified in step 309 is the MS that requested continuation of the call. That MS continues the call, i.e. sends further traffic information, in step 311 or step 313, as appropriate. In a further embodiment of the invention, the control console 145 may be employed to make transmissions of traffic information within the enlarged patched group. Traffic information for transmission may be entered at the user interface 142 and transmitted by the control terminal 141. The transmissions may be made in encrypted or unencrypted form. Desirably, one of these forms is selected for all of the transmissions to be made by the control console 145. The control console 145 may thus be a member of the encrypted sub-set or of the selectable-clear sub-set, as appropriate, for this purpose. Where the transmission is to be made in encrypted form, the translator 143 may be employed to carry out encryption of the information to be transmitted. In a further embodiment which is a modification of the method 300, more than two sub-sets may be created, although each sub-set would still be classified as either 'encrypted' or 'selectable-clear'. Thus, there may be more than one encrypted sub-set and/or more than one selectable-clear sub-set. The behaviour of the MSs of each subset would therefore be as described above with reference to FIG. 3. Where the system 100 is a TETRA system, communications about the group assignments may be made by DGNA signalling. The translator 143 may carry out all of the translation operations for the various sub-sets. Alternatively, translations required for different sub-sets of the same type, e.g. different encrypted sub-sets, may be carried out by different translators. In the embodiments of the invention which have been described, at least two of the original groups may be connected together without the formation of a new
enlarged group, e.g. a new supergroup, between them. This is known in the art as a 'non-regroupable' patch. Such a connection may be made either with or without one or more enlarged groups being formed between other groups as well. In this case, depending on whether the connected groups are 'secure', 'selectable' or 'clear', calls to or from the members of the groups would be made as described above with reference to FIG. 3.
In a further embodiment of the invention, in the encrypted sub-set or in the selectable-clear sub-set referred to above there may be member groups that use different encryption forms, e.g. use at least one encryption parameter that is different in one group of the sub-set from that used in at least one other group of the sub-set. In this case, where a call is initiated in encrypted form by an MS in one of the groups, the translator 143 may be employed to translate the call into another encrypted form suitable for use by MSs in one of the other groups of the same sub-set. The translator 143 may, if required, carry out multiple translations for multiple recipient groups. In all cases, however, it may be arranged that clear MSs would not hear an encrypted call. Clear calls can, if required, be translated and encrypted (as in steps 339 and 341) before sending to another group or sub-set.
In a further embodiment of the invention, where, in the method 300, it is detected that in addition to the calling MS there are MSs and/or groups in only one of the sub-set types, i.e. only the selectable-clear sub-set(s) or only the encrypted subsets), then any step shown in FIG. 3 requiring translation for the other sub-set is not used. Where it is detected that, apart from the calling MS, there are only clear MSs and/or clear groups in rest of the enlarged group, the call set-up may be cancelled. In the foregoing specification, specific embodiments have been described. However, one of ordinary skill in the art will appreciate that various modifications and changes can be made without departing from the scope of the invention as set forth in the accompanying claims. Accordingly, the specification and drawings 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
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 patent 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 or 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 preceded by 'comprises ...a', 'has ...a', 'includes ...a', or '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%, of a stated value. 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 include 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
apparatus for synchronization in a digital mobile communication system as described herein. The non-processor circuits may include, but are not limited to, a radio receiver, a radio transmitter, signal drivers, clock circuits, power source circuits, and user input devices. As such, these functions may be interpreted as steps of a method to perform the synchronization in a digital mobile communication system as 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. Both the state machine and ASIC are considered herein as a 'processing device' for purposes of the foregoing discussion and claim language.
Moreover, an embodiment including a memory can be implemented as a computer-readable storage element having computer readable code stored thereon for programming a computer (e.g., comprising a processing device) to perform a method as described and claimed herein. Examples of such computer-readable storage elements include, but are not limited to, a hard disk, a CD-ROM, an optical storage device, a magnetic storage device, a Read Only Memory (ROM), a Programmable Read Only Memory (PROM), an Erasable Programmable Read Only Memory (EPROM), an Electrically Erasable Programmable Read Only Memory (EEPROM) 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.
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 may lie 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
1. A communication system comprising: a group management processor operable to divide an enlarged group of user terminals formed by patching of smaller groups into sub-sets of user terminals comprising:
(1) an encrypted sub-set of terminals which are operable to undertake only encrypted communications; and
(2) a selectable-clear sub-set of terminals which comprises: (i) selectable terminals that are able to undertake clear communications and, when selected, encrypted communications; and
(ii) clear terminals that are operable to undertake only clear communications; and a translator operable to translate a communication sent in a first encrypted form from a user terminal of one of the sub-sets of terminals into a second encrypted form suitable for decryption by user terminals of the other sub-set of terminals.
2. A communication system according to claim 1 wherein the translator is further operable to translate a communication sent in a clear form from a user terminal of the selectable-clear sub-set of terminals into an encrypted form suitable for decryption by user terminals of the encrypted sub-set of terminals.
3. A communication system according to claim 1 or claim 2 wherein one of the sub-sets of terminals comprises a first group of user terminals operable to communicate in a first encrypted form and the other of the sub-set of terminals comprises a second group of user terminals operable to communicate in a second encrypted form and a third group of user terminals operable to communicate in a third encrypted form, wherein the translator is operable to translate a communication sent in the first encrypted form from a user terminal of the first group into multiple encrypted forms suitable for decryption by the user terminals of the second group and the user terminals of the third group of user terminals.
4. A communication system according to any one of the preceding claims, wherein the translator is further operable to translate a communication sent in an encrypted form by a user terminal of one of the sub-set of terminals into a clear form suitable for receipt by the clear user terminals of the selectable-clear sub-set of terminals.
5. A communication system according to any one of the preceding claims wherein the translator is operable to translate an encrypted communication received in the first encrypted form into the second encrypted form by decrypting the communication of the first encrypted form and re-encrypting the decrypted communication in the second encrypted form.
6. A communication system according to any one of the preceding claims wherein the first encrypted form and the second encrypted form use at least one encryption parameter which differs between the first encrypted form and the second encrypted form, wherein the at least one encryption parameter is selected from: (i) an encryption key; (ii) an encryption algorithm; (iii) a synchronisation parameter.
7. A system according to any one of the preceding claims wherein the group management processor is operable to patch together communication resources of at least a first group of user terminals and a second group of user terminals to form the enlarged group of the terminals.
8. A communication system according to any one of the preceding claims which is a cellular communication system and includes: (i) mobile stations which are user terminals of the encrypted sub-set of terminals; and mobile stations which are user terminals of the selectable-clear sub-set of terminals; (ii) an infrastructure including a plurality of base stations each operable to serve mobile stations of the sub-sets of terminals with wireless communications; and (iii) a control console operably connected to the infrastructure, the control console including a user interface operable to obtain operator instructions relating to operation of the group management processor.
9. A communication system according to claim 8 wherein the control console incorporates the translator and the group management processor.
10. A communication system according to any one of the preceding claims including, operably connected to the group management processor, a database operable to store for each of the user terminals or smaller groups of user terminals included in the enlarged group a security capability defining whether the user terminals or the smaller group are capable of being assigned to one of the sub-sets of terminals of the enlarged group and a group identity of the enlarged group together with an identity of each of the smaller groups or user terminals or both making up the enlarged group.
11. A communication system according to any one of the preceding claims, wherein the group management processor is operable to select whether communications between user terminals of the enlarged group are passed through the translator.
12. A communication system according to any one of the preceding claims which is a TETRA system.
13. A method of operation in a communication system comprising: dividing an enlarged group of user terminals formed by patching of smaller groups into sub-sets of user terminals comprising:
(1) an encrypted sub-set of terminals which are operable to undertake only encrypted communications; and
(2) a selectable-clear sub-set of terminals which comprises:
(i) selectable terminals that are able to undertake clear communications and, when selected, encrypted communications; and
(ii) clear terminals that are operable to undertake only clear communications ; sending an encrypted communication in a first encrypted form from a user terminal of a first one of the sub-sets of terminals; receiving the communication by a translator; and translating the communication from the first encrypted form to a second encrypted form suitable for decryption by user terminals of the other sub-set of terminals.
14. A method according to claim 13 wherein when a communication is sent in an encrypted form from a user terminal of one of the sub-sets of terminals, the communication is received by user terminals of the enlarged group in only an encrypted form.
15. A processor or console which includes the group management processor and the translator of the system claimed in any one of claims 1 to 12.
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
AT08850079T ATE515902T1 (en) | 2007-11-16 | 2008-10-23 | SECURE COMMUNICATION SYSTEM WITH TERMINAL DEVICES WITH DIFFERENT SECURITY PERFORMANCE LEVELS |
EP08850079A EP2208371B1 (en) | 2007-11-16 | 2008-10-23 | Secure communication system comprising terminals with different security capability levels |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
GB0722497.5A GB2454871B (en) | 2007-11-16 | 2007-11-16 | System, method and processor for use in communication |
GB0722497.5 | 2007-11-16 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2009064596A1 true WO2009064596A1 (en) | 2009-05-22 |
Family
ID=38896415
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US2008/080944 WO2009064596A1 (en) | 2007-11-16 | 2008-10-23 | Secure communication system comprising terminals with different security capability levels |
Country Status (4)
Country | Link |
---|---|
EP (1) | EP2208371B1 (en) |
AT (1) | ATE515902T1 (en) |
GB (1) | GB2454871B (en) |
WO (1) | WO2009064596A1 (en) |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2013113368A1 (en) * | 2012-01-31 | 2013-08-08 | Nokia Siemens Networks Oy | Encrypting device-to-device messages for a public safety network mobile communication system |
WO2014019857A3 (en) * | 2012-07-31 | 2015-11-05 | Sirran Technologies Limited | Improved telecommunication system |
US11876788B2 (en) | 2016-09-06 | 2024-01-16 | Assac (S.Z.) Networks Israel Ltd. | Mobile device system and method for preventing network signal interception and hacking |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20030012149A1 (en) | 2000-03-03 | 2003-01-16 | Qualcomm, Inc. | System and method for providing group communication services |
EP1324541A2 (en) * | 2001-12-26 | 2003-07-02 | Kabushiki Kaisha Toshiba | Communication system, wireless communication apparatus, and communication method |
US20060031586A1 (en) * | 2004-04-26 | 2006-02-09 | Jp Morgan Chase Bank | System and method for routing messages |
US20070055891A1 (en) * | 2005-09-08 | 2007-03-08 | Serge Plotkin | Protocol translation |
Family Cites Families (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5392357A (en) * | 1991-12-09 | 1995-02-21 | At&T Corp. | Secure telecommunications |
FI108827B (en) * | 1998-01-08 | 2002-03-28 | Nokia Corp | A method for implementing connection security in a wireless network |
US7039800B1 (en) * | 1999-05-24 | 2006-05-02 | Rockwell Collins, Inc. | Translator terminal for two or more wireless networks |
GB2418320B (en) * | 2004-09-15 | 2007-09-19 | Motorola Inc | A communication system and method of call group management therefor |
-
2007
- 2007-11-16 GB GB0722497.5A patent/GB2454871B/en not_active Expired - Fee Related
-
2008
- 2008-10-23 EP EP08850079A patent/EP2208371B1/en active Active
- 2008-10-23 WO PCT/US2008/080944 patent/WO2009064596A1/en active Application Filing
- 2008-10-23 AT AT08850079T patent/ATE515902T1/en not_active IP Right Cessation
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20030012149A1 (en) | 2000-03-03 | 2003-01-16 | Qualcomm, Inc. | System and method for providing group communication services |
EP1324541A2 (en) * | 2001-12-26 | 2003-07-02 | Kabushiki Kaisha Toshiba | Communication system, wireless communication apparatus, and communication method |
US20060031586A1 (en) * | 2004-04-26 | 2006-02-09 | Jp Morgan Chase Bank | System and method for routing messages |
US20070055891A1 (en) * | 2005-09-08 | 2007-03-08 | Serge Plotkin | Protocol translation |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2013113368A1 (en) * | 2012-01-31 | 2013-08-08 | Nokia Siemens Networks Oy | Encrypting device-to-device messages for a public safety network mobile communication system |
WO2014019857A3 (en) * | 2012-07-31 | 2015-11-05 | Sirran Technologies Limited | Improved telecommunication system |
US11876788B2 (en) | 2016-09-06 | 2024-01-16 | Assac (S.Z.) Networks Israel Ltd. | Mobile device system and method for preventing network signal interception and hacking |
Also Published As
Publication number | Publication date |
---|---|
GB0722497D0 (en) | 2007-12-27 |
EP2208371B1 (en) | 2011-07-06 |
GB2454871A (en) | 2009-05-27 |
ATE515902T1 (en) | 2011-07-15 |
GB2454871B (en) | 2012-01-18 |
EP2208371A1 (en) | 2010-07-21 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US5410602A (en) | Method for key management of point-to-point communications | |
JP4445005B2 (en) | Method and apparatus for providing a private communication system in a public telephone network | |
CN101124770B (en) | System, method and computer program product for detecting a rogue member in a multicast group | |
CN100484274C (en) | Packet mode speech communication | |
JP4700064B2 (en) | Efficient push-to-talk (PTT) communication system and method | |
US7643817B2 (en) | Method and apparatus for rapid secure session establishment on half-duplex AD-hoc group voice cellular network channels | |
CN100349480C (en) | System for establishing data transmission path between mobile phone terminals | |
CN102379134B (en) | Securing messages associated with a multicast communication session within a wireless communications system | |
EP1638355B1 (en) | A communication system and method of call group management therefor | |
US20110130119A1 (en) | Staging a mobile device to an enterprise network securely using voice channel of a wireless wide area network (wwan) | |
EP3187020B1 (en) | User device and method thereof | |
KR101482696B1 (en) | End-to-end encrypted communication | |
KR20100008326A (en) | Method of supporting location privacy | |
CN1168331C (en) | System and method of communicating encrypted group broadcast messages | |
EP2208371B1 (en) | Secure communication system comprising terminals with different security capability levels | |
EP1428403B1 (en) | Communications methods, systems and terminals | |
US8868057B2 (en) | Staging a mobile device to an enterprise network securely using voice channel of a wireless wide area network (WWAN) | |
CA2481368C (en) | Method and apparatus for providing a private communication system in a public switched telephone network | |
WO2008019178A2 (en) | Processor, method and terminal for use in communications | |
JP2000165943A (en) | Subscriber information managing system | |
GB2418575A (en) | Decryption for mixed groups of users | |
JPH08317066A (en) | Conference connection system by radio communication equipment | |
JP2000269954A (en) | Push-type broadcasting service method |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 08850079 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2008850079 Country of ref document: EP |
|
NENP | Non-entry into the national phase |
Ref country code: DE |