WO2017124425A1 - 密钥的生成及下发方法、相关设备及系统 - Google Patents
密钥的生成及下发方法、相关设备及系统 Download PDFInfo
- Publication number
- WO2017124425A1 WO2017124425A1 PCT/CN2016/071707 CN2016071707W WO2017124425A1 WO 2017124425 A1 WO2017124425 A1 WO 2017124425A1 CN 2016071707 W CN2016071707 W CN 2016071707W WO 2017124425 A1 WO2017124425 A1 WO 2017124425A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- gsk
- mcptt server
- group
- group session
- message
- Prior art date
Links
Images
Classifications
-
- 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
Definitions
- the present invention relates to the field of communications, and in particular, to a key generation and delivery method, related device and system.
- the urgent task is called "mission critical push to talk over LTE" (English abbreviation: MCPTT) defines the long-term evolution (English full name: long term evolution, English abbreviation: LTE) network push-to-talk business function realization standard.
- MCPTT security protection is through secure real-time transport protocol (English name: secure real-time transport protocol, English abbreviation: SRTP) / secure real-time transmission control protocol (English full name: secure real-time transport control protocol, English abbreviation: SRTCP)
- secure real-time transport protocol English name: secure real-time transport protocol, English abbreviation: SRTP
- secure real-time transmission control protocol English full name: secure real-time transport control protocol, English abbreviation: SRTCP
- MCPTT group session members directly use the group management server (English name: group management server, English abbreviation: GMS) to distribute the GMK, combined with random values (English: rand), encrypted session bundle (English full name: crypto session bundle, English Abbreviation: CSB) - ID (English full name: identity, English abbreviation: ID) and encrypted session (English full name: crypto session, English abbreviation: CS) - ID to generate SRTP / SRTCP key.
- group management server English name: group management server, English abbreviation: GMS
- GMS group management server
- the SRTP/SRTCP keys for each group session are the same, If a group session is frequently initiated, the SRTP/SRTCP key will be used too frequently, resulting in an increased likelihood of being compromised.
- different group sessions use the same SRTP/SRTCP key, and if the SRTP/SRTCP key is compromised, the keys of subsequent group sessions will be revealed.
- the MCPTT group Session members directly use the GMK distributed by GMS. Combining rand, CSB-ID, and CS-ID to generate SRTP/SRTCP keys reduces the security level.
- the embodiment of the present invention provides a key generation and delivery method, a related device, and a system, to at least solve the current GMK that the MCPTT group session member directly uses the GMS to distribute, and combines the rand, the CSB-ID, and the CS-ID to generate the SRTP/SRTCP.
- the key will reduce the security level.
- the embodiment of the present invention adopts the following technical solutions:
- the first aspect provides a key generation and delivery method, including:
- the emergency task is said to be the MCPTT server to obtain the group identifier of the group corresponding to the group session, the group session key GSK and the GSK identification ID of the group session;
- the MCPTT server acquires the associated UEs in the group according to the group identifier, and sends the GSK and the GSK ID to at least one of the associated UEs.
- the MCPTT server may obtain the group identifier of the group corresponding to the group session, the GSK and the GSK ID of the group session in multiple manners, and the following two exemplary implementations are provided by way of example. .
- the MCPTT server obtains the group identifier of the group corresponding to the group session, the GSK and the GSK ID of the group session, and specifically includes:
- the MCPTT server receives the group session request sent by the first UE, where the group session request carries the group identifier of the group corresponding to the group session, and the GSK and GSK ID of the group session generated by the first UE;
- the MCPTT server sends the GSK and the GSK ID to the at least one of the associated UEs, which may include:
- the MCPTT server separately transmits the GSK and the GSK ID to each UE other than the first UE in the associated UE.
- the GSK and GSK IDs of the group session can be secured in the following two ways:
- the GSK and the GSK ID are encapsulated in a Mikey message, where the Mikey message is pre-configured Group key GMK for security protection;
- the MCPTT server sends the GSK and the GSK ID to each of the UEs except the first UE, which may include:
- the MCPTT server separately sends the Mikey message to each UE except the first UE in the associated UE.
- the security of the Mikey message with the pre-configured GMK specifically means:
- the encryption key for encrypting the GSK and GSK ID
- the integrity protection key integrated protection GSK
- the encryption key for encrypting the GSK and GSK ID
- the integrity protection key integrated protection GSK
- the GSK and the GSK ID of the group session generated by the first UE are encapsulated in the first S The /MIME message, wherein the first S/MIME message is secured by using a security key between the pre-configured MCPTT server and the first UE;
- the method may further include:
- the MCPTT server parses the first S/MIME message to obtain the GSK and the GSK ID;
- the MCPTT server sends the GSK and the GSK ID to each of the UEs except the first UE, which may include:
- the MCPTT server For each UE in the associated UE except the first UE, the MCPTT server processes according to the following operations for the second UE:
- the MCPTT server encapsulates the GSK and the GSK ID in the second S/MIME
- the second S/MIME message is secured by using a security key between the pre-configured MCPTT server and the second UE;
- the MCPTT server sends the second S/MIME message to the second UE.
- the MCPTT server obtains the group identifier of the group corresponding to the group session, the GSK and the GSK ID of the group session, and specifically includes:
- the MCPTT server receives the group session request sent by the first UE, where the group session request carries the group identifier of the group corresponding to the group session; and the MCPTT server generates the GSK and GSK ID of the group session;
- the MCPTT server sends the GSK and the GSK ID to the at least one of the associated UEs, which may include:
- the MCPTT server separately transmits the GSK and the GSK ID to each of the associated UEs.
- the GSK and GSK IDs of the group session can be secured in the following three ways:
- the group session request further carries a group key identifier GMK ID of the group session;
- the method may further include:
- the MCPTT server searches for the GMK corresponding to the GMK ID according to the GMK ID;
- the MCPTT server sends the GSK and the GSK ID to each of the associated UEs, which may include:
- the MCPTT server encapsulates the GSK and the GSK ID in a Mikey message, where the Mikey message is secured by the GMK;
- the MCPTT server separately sends the Mikey message to each of the associated UEs.
- the MCPTT server sends the GSK and the GSK ID to each of the UEs in the associated UE, which may include:
- the MCPTT server For each UE in the associated UE, the MCPTT server processes according to the following operations for the second UE:
- the MCPTT server encapsulates the GSK and the GSK ID in an S/MIME message, where the S/MIME message is secured by using a security key between the pre-configured MCPTT server and the second UE;
- the MCPTT server sends the S/MIME message to the second UE.
- the MCPTT server separately sends the GSK and the GSK ID to each UE in the associated UE, where Can include:
- the MCPTT server For each UE in the associated UE, the MCPTT server processes according to the following operations for the second UE:
- the MCPTT server encapsulates the GSK and the GSK ID in a Hypertext Transfer Protocol HTTP message
- the MCPTT server sends the HTTP message to the second UE through a secure transport layer protocol TLS secure channel between the pre-established MCPTT server and the second UE.
- the MCPTT server may obtain the group identifier of the group corresponding to the group session, and the group The GSK and the GSK ID of the session, and then, after the MCPTT server obtains the associated UEs in the group according to the group identifier, the GSK and the GSK ID may be separately sent to at least one of the associated UEs. That is to say, in the embodiment of the present invention, each group session has a fresh independent GSK.
- the SRTP/SRTCP key of each group session is the same. If the group session is frequently initiated, the SRTP/SRTCP key will be used too frequently, which may increase the possibility of being compromised.
- the method for generating and delivering a key can solve the problem that the MCPTT group session member directly uses the GMS distributed by the GMS, and combines the rand, the CSB-ID, and the CS-ID to generate the SRTP/SRTCP key.
- the key will reduce the security level, not only provides end-to-end security protection for group sessions between MCPTT UEs, but also ensures that each group session uses a new security key, which improves the security level.
- an emergency task push-to-talk MCPTT server including: a processing unit and a sending unit;
- a processing unit configured to: when the first user equipment UE initiates a group session, acquire a group identifier of the group corresponding to the group session, a group session key GSK and a GSK identifier ID of the group session;
- the processing unit is further configured to acquire, according to the group identifier, an associated UE in the group;
- a sending unit configured to separately send the GSK and the GSK ID to at least one of the associated UEs.
- the processing unit may obtain the group identifier of the group conversation corresponding group, the GSK and the GSK ID of the group session in multiple manners, and the following two exemplary implementations are provided by way of example. .
- the MCPTT server further includes: a receiving unit;
- the processing unit is specifically used to:
- a group session request sent by the first UE where the group session request carries a group identifier of the group corresponding to the group session, a GSK and a GSK ID of the group session generated by the first UE;
- the sending unit is specifically used to:
- the GSK and the GSK ID are respectively sent to each of the associated UEs except the first UE.
- the GSK and GSK IDs of the group session can be secured in the following two ways:
- the GSK and the GSK ID are encapsulated in a Mikey message, where the Mike message is pre-configured Group key GMK for security protection;
- the sending unit is specifically used to:
- the Mikey message is sent to each UE except the first UE in the associated UE.
- the GSK and the GSK ID of the group session generated by the first UE are encapsulated in the first S The /MIME message, wherein the first S/MIME message is secured by using a security key between the pre-configured MCPTT server and the first UE;
- the processing unit is further configured to: after receiving the group session request sent by the first UE by the receiving unit, parsing the first S/MIME message to obtain the GSK and the GSK ID;
- the sending unit is specifically used to:
- the MCPTT server further includes: a receiving unit;
- the processing unit is specifically used to:
- the sending unit is specifically used to:
- the GSK and the GSK ID are respectively sent to each of the associated UEs.
- the GSK and GSK IDs of the group session can be secured in the following three ways:
- the group session request further carries a group key identifier GMK ID of the group session;
- the processing unit is further configured to: before sending, by the sending unit, the GSK and the GSK ID to each of the associated UEs, searching for a GMK corresponding to the GMK ID according to the GMK ID;
- the sending unit is specifically used to:
- the Mikey message is sent to each of the associated UEs.
- the sending unit is specifically configured to:
- the S/MIME message is sent to the second UE.
- the sending unit is specifically configured to:
- the HTTP message is sent to the second UE by a secure transport layer protocol TLS secure channel between the pre-established MCPTT server and the second UE.
- the MCPTT server provided by the embodiment of the present invention may be used to perform the method for generating and delivering a key according to the foregoing first aspect or the optional implementation of any of the foregoing aspects.
- the effect refer to the technical effects of the method for generating and issuing a key executed by the MCPTT server in the above first aspect, and details are not described herein again.
- an emergency task push-to-talk MCPTT server including: a processor, a memory, a bus, and a communication interface;
- the memory is used to store a computer execution instruction, and the processor and the memory are connected by a bus.
- the processor executes a memory storage computer execution instruction, so that the MCPTT server performs the first aspect or the first aspect as described above.
- a key generation and delivery method as described in a possible implementation.
- the MCPTT server provided by the embodiment of the present invention may be used to perform the method for generating and delivering a key according to the foregoing first aspect or the optional implementation of any of the foregoing aspects.
- the effect refer to the technical effects of the method for generating and issuing a key executed by the MCPTT server in the above first aspect, and details are not described herein again.
- the fourth aspect provides a key generation and delivery system, including the emergency task push-to-talk MCPTT server as described in the foregoing second aspect or the optional implementation of the second aspect, and Multiple user equipment UEs connected by the MCPTT server.
- the system for generating and delivering a key according to the embodiment of the present invention includes the MCPTT server as described in the foregoing second aspect or the optional implementation of any of the second aspect. Therefore, the technical effects that can be obtained can be obtained. Refer to the technical effects of the MCPTT server in the second aspect above, and details are not described herein again.
- a key generation and delivery system including the emergency task push-to-talk MCPTT server according to the above third aspect, and Multiple user equipment UEs connected by the MCPTT server.
- the system for generating and delivering a key according to the embodiment of the present invention includes the MCPTT server as described in the foregoing third aspect. Therefore, the technical effects that can be obtained can refer to the technical effects of the MCPTT server in the foregoing third aspect. I won't go into details here.
- a readable medium comprising computer-executable instructions, when the processor of the MCPTT server executes the computer to execute an instruction, the MCPTT server performs any of the foregoing first aspect or the optional implementation of the first aspect The method for generating and issuing a key as described above.
- 1 is a schematic diagram of an existing MCPTT architecture
- FIG. 2 is a schematic structural diagram of a key generation and delivery system according to an embodiment of the present invention.
- FIG. 3 is a schematic flowchart 1 of a method for generating and sending a key according to an embodiment of the present invention
- FIG. 4 is a second schematic flowchart of a method for generating and sending a key according to an embodiment of the present invention
- FIG. 5 is a schematic diagram 1 of a key generation and delivery method according to an embodiment of the present invention.
- FIG. 6 is a schematic diagram 2 of a key generation and delivery method according to an embodiment of the present invention.
- FIG. 7 is a schematic flowchart 3 of a method for generating and sending a key according to an embodiment of the present invention.
- FIG. 8 is a schematic diagram 3 of a key generation and delivery method according to an embodiment of the present invention.
- FIG. 9 is a schematic diagram 4 of a key generation and delivery method according to an embodiment of the present invention.
- FIG. 10 is a schematic diagram 5 of a key generation and delivery method according to an embodiment of the present invention.
- FIG. 11 is a schematic structural diagram 1 of an MCPTT server according to an embodiment of the present disclosure.
- FIG. 12 is a schematic structural diagram 2 of an MCPTT server according to an embodiment of the present disclosure.
- FIG. 13 is a schematic structural diagram 3 of an MCPTT server according to an embodiment of the present invention.
- FIG 1 is a schematic diagram of an existing MCPTT architecture.
- the key management server (KMS) is responsible for delivering identity-based security parameters to all related entities, including: through the generic service core node. (English full name: common service core, English abbreviation: CSC) -8 interface is distributed to MCPTT user equipment (English full name: English abbreviation: UE), distributed to MCPTT server through CSC-9 interface, and distributed to CSC-10 interface GMS.
- the functional entities can perform integrity protection (private key signature corresponding to the identity of the sender) and encryption (identity encryption at the receiving end) based on the identity-based security parameters.
- the session initiation protocol (English abbreviation: SIP) signaling is used, which relies on IPsec security.
- PS packet switching
- MNO mobile network operator
- SIP core (English: core ) may be deployed by the MNO, so some sensitive data (such as identity) at the application layer between the MCPTT UE and the MCPTT server may require additional security.
- KMS will pre-share the key (English full name: pre-shared key, English abbreviation: PSK) configured to MCPTT UE and MCPTT server; 2, based on KMS configuration I Identity-based security parameters; 3, certificate mechanism.
- the GMK used to protect the group session is sent by the GMS to the MCPTT group session member (ie, MCPTT UE) through the Mikey-SAKKE message; then the MCPTT group session member directly combines rand, CSB according to the GMK. - ID and CS-ID to generate an SRTP/SRTCP key. That is, as described in the background art, currently, MCPTT group session members directly use the GMK distributed by the GMS, and combine the rand, CSB-ID, and CS-ID to generate an SRTP/SRTCP key.
- the SRTP of each group session is caused.
- the /SRTCP key is the same. If the group session is initiated frequently, the SRTP/SRTCP key will be used too frequently, which will increase the possibility of being compromised.
- different group sessions use the same SRTP/SRTCP key, and if the SRTP/SRTCP key is compromised, the keys of subsequent group sessions will be revealed. That is to say, MCPTT group session members directly use GMS distributed GMK, combined with rand, CSB-ID and CS-ID to generate SRTP/SRTCP key will reduce the security level.
- the embodiment of the present invention provides a method for generating and delivering a key, a related device, and a system, to at least solve the GMK that the current MCPTT group session member directly uses the GMS to distribute, combining rand, CSB-ID, and CS-
- the ID to generate the SRTP/SRTCP key reduces the security level. It not only provides end-to-end security protection for group sessions between MCPTT UEs, but also ensures that each group session uses a new security key. , improved the level of security.
- a component can be, but is not limited to being, a process running on a processor, a processor, an object, an executable, a thread in execution, a program, and/or a computer.
- an application running on a computing device and the computing device can be a component.
- One or more components can reside within a process and/or thread of execution, and a component can be located in a computer and/or distributed between two or more computers. Moreover, these components can execute from various computer readable media having various data structures thereon.
- These components may be passed, for example, by having one or more data packets (eg, data from one component that interacts with the local system, another component of the distributed system, and/or signaled through, such as the Internet)
- the network interacts with other systems to communicate in a local and/or remote process.
- the communication network in this application includes a wired communication network and a wireless communication network.
- the wireless communication network is a network that provides wireless communication functions.
- the wireless communication network can adopt different communication technologies, such as code division multiple access (English name: CDMA), wideband code division multiple access (English name: wideband code division multiple access, English abbreviation: WCDMA) Time division multiple access (English full name: time division multiple access, English abbreviation: TDMA), frequency division multiple access (English full name: frequency division multiple access, English abbreviation: FDMA), orthogonal frequency division multiple access (English: Orthogonal frequency-division multiple access, English abbreviation: OFDMA), single carrier frequency division multiple access (English full name: single carrier FDMA, English abbreviation: SC-FDMA), carrier sense multiple access / collision avoidance (English full name: carrier sense Multiple access with collision avoidance).
- CDMA code division multiple access
- WCDMA wideband code division multiple access
- TDMA Time division multiple access
- TDMA Time division multiple
- the network can be divided into 2G (English: generation) network, 3G network or 4G network.
- a typical 2G network includes a global mobile communication system (global system for mobile communications/general packet radio service, English abbreviation: GSM) network or a general packet radio service (English name: general packet radio service, English abbreviation: GPRS) network.
- GSM global system for mobile communications/general packet radio service
- GPRS general packet radio service
- a typical 3G network includes a universal mobile telecommunications system (English name: UMTS) network.
- a typical 4G network includes a long term evolution (English term: LTE) network.
- the UMTS network can also be called the universal terrestrial radio access network (English full name: UTRAN), and the LTE network can sometimes also be called the evolved universal terrestrial radio access network (English full name: Evolved universal terrestrial radio access network, English abbreviation: E-UTRAN).
- E-UTRAN evolved universal terrestrial radio access network
- it can be divided into cellular communication network and wireless local area network (English name: wireless local area networks, English abbreviation: WLAN), wherein the cellular communication network is dominated by scheduling, and WLAN is dominant.
- the aforementioned 2G, 3G and 4G networks are all cellular communication networks.
- the embodiments of the present invention are equally applicable to other wireless communication networks, such as 4.5G or 5G networks, or other non-cellular communication networks.
- the embodiment of the present invention sometimes abbreviates the wireless communication network into a network.
- a UE is a terminal device, which may be a mobile terminal device or a non-mobile terminal device.
- the terminal device is mainly used for receiving or transmitting service data.
- User equipment can be distributed in the network. User equipments have different names in different networks, such as: terminals, mobile stations, subscriber units, stations, cellular phones, Human digital assistants, wireless modems, wireless communication devices, handheld devices, laptops, cordless phones, wireless local loop stations, etc.
- the user equipment can communicate with one or more core networks via a radio access network (radio access network, English abbreviation: RAN) (for accessing a wireless communication network), for example, exchanging voice and voice with a radio access network. / or data.
- radio access network radio access network, English abbreviation: RAN
- RAN for accessing a wireless communication network
- the present application will present various aspects, embodiments, or features in a system that can include multiple devices, components, modules, and the like. It is to be understood and appreciated that the various systems may include additional devices, components, modules, etc. and/or may not include all of the devices, components, modules, etc. discussed in connection with the figures. In addition, a combination of these schemes can also be used.
- the words “exemplary” or “such as” are used to mean an example, an illustration, or a description. Any embodiment or design described as “example” or “such as” in this application should not be construed as preferred or advantageous over other embodiments or designs. Rather, the use of the words “exemplary” or “such as” is intended to present a concept in a specific manner.
- the network architecture and the service scenario described in the embodiments of the present invention are used to more clearly illustrate the technical solutions of the embodiments of the present invention, and do not constitute a limitation of the technical solutions provided by the embodiments of the present invention.
- the technical solutions provided by the embodiments of the present invention are equally applicable to similar technical problems.
- the key generation and delivery system includes an MCPTT server and multiple MCPTTs connected to the MCPTT server.
- UE hereinafter referred to as UE, such as UE1, UE2, and UE3, etc.
- connection means that they can communicate with each other, and can be connected by wire or wirelessly.
- the embodiment of the present invention does not specifically limit this.
- the devices connected to each other may be directly connected to each other, or may be connected through other devices, which is not specifically limited in this embodiment of the present invention.
- the key generation and delivery system shown in FIG. 2 only a group corresponding to an MCPTT group session is exemplarily drawn, and only the exemplary UE1 is drawn in the group.
- the UE, the UE2, and the UE3 have a total of three UEs.
- the key generation and delivery system may not be limited to a group corresponding to only one MCPTT group session, and may include any group of MCPTT group sessions.
- the group may not be limited to include three UEs, and may include any number of UEs that are not less than two, which is not specifically limited in this embodiment of the present invention.
- the embodiment of the present invention provides a method for generating and delivering a key, including steps S301-S303:
- the MCPTT server obtains the group identifier of the group corresponding to the group session, the group session key of the group session (English name: group session key, English abbreviation: GSK), and GSK. ID.
- the first UE in the embodiment of the present invention is a UE that initiates a group session in a scenario in which a group session exists, and the first UE may be any of the key generation and delivery system shown in FIG.
- a UE is not specifically limited in this embodiment of the present invention.
- the MCPTT server acquires an associated UE in the group according to the group identifier.
- the associated UE in the embodiment of the present invention specifically refers to a UE in the group that is allowed to perform an MCPTT group session.
- the MCPTT server can obtain the associated UEs in the group according to the group identifier.
- the MCPTT server needs to verify the first according to the group identifier, the received MCPTT ID, and the pre-stored group policy/user policy.
- the MCPTT server acquires the associated UE in the group according to the group identifier.
- the embodiment of the present invention does not elaborate on the situation, and may refer to the existing implementation.
- the MCPTT server separately sends the GSK and the GSK ID to at least one of the associated UEs.
- the MCPTT server may obtain the group identifier of the group corresponding to the group session, and the group The GSK and the GSK ID of the session, and then, after the MCPTT server obtains the associated UEs in the group according to the group identifier, the GSK and the GSK ID may be separately sent to at least one of the associated UEs. That is to say, in the embodiment of the present invention, each group session has a fresh independent GSK.
- the SRTP/SRTCP key of each group session is the same. If the group session is frequently initiated, the SRTP/SRTCP key will be used too frequently, which will increase the possibility of being compromised and improve the generation of SRTP/.
- the security level of the SRTCP key since the GSK belongs to the key of a group session, security isolation between different group sessions can be achieved, so that if the SRTP/SRTCP key is generated according to the GSK, the current can be avoided.
- the SRTP/SRTCP key of each group session is the same. If the SRTP/SRTCP key is compromised, the key of the subsequent group session will be leaked, and the security level of generating the SRTP/SRTCP key is improved. .
- the method for generating and delivering a key can solve the problem that the MCPTT group session member directly uses the GMS distributed by the GMS, and combines the rand, the CSB-ID, and the CS-ID to generate the SRTP/SRTCP key.
- the key will reduce the security level, not only provides end-to-end security protection for group sessions between MCPTT UEs, but also ensures that each group session uses a new security key, which improves the security level.
- the MCPTT server can pass multiple The method obtains the group identifier of the group corresponding to the group session, the GSK and the GSK ID of the group session, and two possible implementations are exemplarily provided below.
- the MCPTT server acquires the group identifier of the group corresponding to the group session, the GSK and the GSK of the group session.
- the ID may specifically include:
- the MCPTT server receives the group session request sent by the first UE, where the group session request carries the group identifier of the group corresponding to the group session, and the group generated by the first UE The GSK and GSK ID of the session.
- the MCPTT server sends the GSK and the GSK ID to the at least one of the associated UEs respectively (step S303), which may include:
- the MCPTT server sends a GSK and a GSK ID to each UE except the first UE in the associated UE.
- the GSK and GSK IDs of the group session can be secured in the following two ways:
- the GSK and GSK IDs are encapsulated in a Mikey message, wherein the Mikey message is secured with a pre-configured GMK.
- the MCPTT server sends the GSK and the GSK ID to each of the UEs except the first UE in the UE (step S303a), which may include:
- the MCPTT server separately sends the Mikey message to each UE except the first UE in the associated UE.
- the security of the Mikey message with the pre-configured GMK specifically means:
- the encryption key for encrypting the GSK and GSK ID
- the integrity protection key integrated protection GSK
- the encryption key for encrypting the GSK and GSK ID
- the integrity protection key integrated protection GSK
- the first UE is the UE1 in FIG. 2, and the associated UEs in the group session corresponding group include UE1, UE2, and UE3 as an example, and the MCPTT server and the group are used.
- the manner in which the group session corresponds to the associated UE interaction in the group is expanded.
- the method for generating and delivering a key according to an embodiment of the present invention includes steps S501-S510:
- S501, UE1, UE2, and UE3 are respectively registered to the MCPTT server and belong to the group corresponding to one group session.
- the S502, UE1, UE2, UE3, and MCPTT servers are all pre-configured with GMK and GMK IDs.
- UE1 When UE1 initiates a group session, UE1 generates a GSK and a GSK ID of the group session, and is encapsulated in a Mikey message.
- the Mikey message is secured by a pre-configured GMK.
- the GMK ID is carried in the Mikey message shown in FIG. 5, which is for the receiving end to parse the Mikey message.
- the group identifier of the corresponding group of the group session corresponds to the GMK one by one, that is, one
- the group identifier is not limited to the GMK, and the GMK ID is not included in the embodiment of the present invention.
- the UE1 sends a group session request to the MCPTT server, where the group session request carries the group identifier and the Mikey message of the group corresponding to the group session.
- the MCPTT server receives the group session request, and obtains an associated UE in the group according to the group identifier.
- the MCPTT server may also parse the Mikey message to obtain the GSK and the GSK ID (for example, for the LI), which is not specifically limited in this embodiment of the present invention.
- the MCPTT server sends a GSK and a GSK ID to each UE except the UE1 in the associated UE.
- step S506 specifically includes steps S506a and S506b:
- the S506a and the MCPTT server send a group session request to the UE2, where the group session request carries the group identifier and the Mikey message of the group corresponding to the group session.
- the S506b and the MCPTT server send a group session request to the UE3, where the group session request carries the group identifier and the Mikey message of the group corresponding to the group session.
- the group identifiers of the group corresponding to the group session are carried in steps S506a and S506b, so as to notify the receiving end that they are invited to join the group session corresponding to the group identifier.
- S507a and UE2 parse the Mikey message to obtain the GSK and GSK IDs.
- S507b and UE3 parse the Mikey message to obtain the GSK and GSK IDs.
- the MCPTT server replies with a confirmation message to UE1.
- UE1, UE2, and UE3 use the GSK and GSK IDs and other parameters to generate a key of SRTP/SRTCP.
- the GSK and the GSK ID of the group session are generated by the UE that initiates the group session, and the GMS allocates the GMK to the group member.
- the release of GSK is protected by the Mikey message.
- the GSK and GSK ID of the group session generated by the first UE are encapsulated in a first S/MIME message, where the first S/MIME message uses a pre-configured MCPTT server and The security key between the first UEs is secured.
- the method may further include:
- the MCPTT server parses the first S/MIME message to obtain the GSK and the GSK ID.
- the MCPTT server sends the GSK and the GSK to each of the UEs except the first UE in the UE (step S303a), which may include:
- the MCPTT server For each UE in the associated UE except the first UE, the MCPTT server processes according to the following operations for the second UE:
- the MCPTT server encapsulates the GSK and GSK IDs in the second S/MIME message
- the second S/MIME message is secured by using a security key between the pre-configured MCPTT server and the second UE;
- the MCPTT server sends the second S/MIME message to the second UE.
- the first UE is the UE1 in FIG. 2, and the associated UEs in the group session corresponding group include the UE1, the UE2, and the UE3, and the MCPTT server interacts with the associated UE in the group corresponding to the group session.
- the way to expand the implementation is described.
- the method for generating and delivering a key according to an embodiment of the present invention includes steps S601-S611:
- S601, UE1, UE2, and UE3 are respectively registered to the MCPTT server and belong to the group corresponding to one group session.
- S602, UE1, UE2, UE3, and MCPTT servers are all pre-configured with security keys or certificates that protect sensitive information in SIP signaling.
- UE1 When UE1 initiates a group session, UE1 generates a GSK and a GSK ID of the group session, and is encapsulated in a first S/MIME message (S/MIME message 1).
- the first S/MIME message is secured by using a security key between the pre-configured MCPTT server and the UE1.
- the UE1 sends a group session request to the MCPTT server, where the group session request carries the group identifier and the first S/MIME message of the group corresponding to the group session.
- the MCPTT server receives the group session request, and obtains an associated UE in the group according to the group identifier, and parses the first S/MIME message to obtain the GSK and the GSK ID.
- the MCPTT server For each UE in the associated UE except UE1, the MCPTT server processes according to the following operations for the second UE (including steps S606 and S607):
- the MCPTT server encapsulates the GSK and the GSK ID in the second S/MIME message, where the second S/MIME message is secured by using a security key between the pre-configured MCPTT server and the second UE.
- the MCPTT server sends a second S/MIME message to the second UE.
- the associated UEs in the group corresponding to the group include UE1, UE2, and UE3 as an example. Therefore, at this time, the associated UEs in the group are excluded.
- the associated UEs other than UE1 include UE2 and UE3.
- step S606 specifically includes steps S606a and S606b
- step S607 specifically includes steps S607a and S607b:
- the MCPTT server encapsulates the GSK and GSK IDs in S/MIME message 2.
- the S/MIME message 2 is secured by using a security key between the pre-configured MCPTT server and the UE2.
- the MCPTT server sends a group session request to the UE2, where the group session request carries the group identity and the S/MIME message 2 of the group corresponding to the group session.
- the MCPTT server encapsulates the GSK and GSK IDs in S/MIME message 3.
- the S/MIME message 3 is secured by using a security key between the pre-configured MCPTT server and the UE3.
- the MCPTT server sends a group session request to the UE3, where the group session request carries the group identity and the S/MIME message 3 of the group corresponding to the group session.
- the group identifiers of the group corresponding to the group session are carried in steps S607a and S607b, so as to notify the receiving end that they are invited to join the group session corresponding to the group identifier.
- UE2 parses the S/MIME message 2 to obtain the GSK and GSK ID.
- UE3 parses the S/MIME message 3 to obtain the GSK and GSK ID.
- the MCPTT server replies to the UE1 with a confirmation message.
- UE1, UE2, and UE3 use the GSK and GSK IDs and other parameters to generate a key of SRTP/SRTCP.
- the GSK and the GSK ID of the group session are generated by the UE that initiates the group session, and the GMS is not allocated for the group member.
- the GMK but the MCPTT server and each UE are configured with a security key or certificate for protecting sensitive information in the SIP signaling, and the S/MIME message in the SIP signaling is used to protect the delivery of the GSK.
- the GSK and the GSK ID may also be used as security information, and are separately encapsulated and secured by the Mikey message, and the pre-configured protection SIP signaling between the UE and the MCPTT server is used.
- the security key or the certificate of the sensitive information is not specifically limited in this embodiment of the present invention.
- the MCPTT server acquires the group identifier of the group corresponding to the group session, the GSK of the group session, and
- the GSK ID may specifically include:
- the MCPTT server receives the group session request sent by the first UE, where the group session request carries the group identifier of the group corresponding to the group session.
- the MCPTT server generates the GSK and GSK ID of the group session.
- the MCPTT server sends the GSK and the GSK ID to the at least one of the associated UEs respectively (step S303), which may include:
- the MCPTT server separately sends the GSK and GSK IDs to each of the associated UEs.
- the GSK and GSK IDs of the group session can be secured in the following three ways:
- the group session request in step S301b1 also carries the GMK ID of the group session.
- the method may further include:
- the MCPTT server searches for the GMK corresponding to the GMK ID according to the GMK ID.
- the MCPTT server sends the GSK and the GSK ID to each of the associated UEs respectively (step S303b), which may specifically include:
- the MCPTT server encapsulates the GSK and GSK IDs in the Mikey message, wherein the Mikey message is secured by the GMK;
- the MCPTT server separately sends the Mikey message to each of the associated UEs.
- the first UE is the UE1 in FIG. 2, and the associated UEs in the group session corresponding group include the UE1, the UE2, and the UE3, and the MCPTT server interacts with the associated UE in the group corresponding to the group session.
- the method for generating and delivering a key includes steps S801-S809:
- S801, UE1, UE2, and UE3 are respectively registered to the MCPTT server and belong to the group corresponding to one group session.
- the S802, UE1, UE2, UE3, and MCPTT servers are all pre-configured with GMK and GMK IDs.
- the UE1 initiates a group session.
- the UE1 sends a group session request to the MCPTT server, where the group session request carries the group identifier and the GMK ID of the group corresponding to the group session.
- the MCPTT server receives the group session request, and obtains an associated UE in the group according to the group identifier; and the MCPTT server generates a GSK and a GSK ID of the group session; and the MCPTT server determines, according to the GMK ID, After the GMK corresponding to the GMK ID is searched, the GSK and the GSK ID are encapsulated in the Mikey message, and the Mikey message is secured by using the GMK corresponding to the GMK ID.
- the MCPTT server separately sends the GSK and the GSK ID to each of the associated UEs.
- step S806 specifically includes steps S806a, S806b, and S806c:
- the S806a and the MCPTT server send a group session request to the UE2, where the group session request carries the group identifier and the Mikey message of the group corresponding to the group session.
- the MCPTT server sends a group session request to UE3, and the group will The message request carries the group identifier and the Mikey message of the group corresponding to the group session.
- UE2 parse the Mikey message to obtain the GSK and GSK ID.
- UE3 parses the Mikey message to obtain the GSK and GSK ID.
- the S806c and the MCPTT server send an acknowledgment message to the UE1, where the acknowledgment message carries the group identifier and the Mikey message of the group corresponding to the group session.
- UE1 parses the Mikey message to obtain the GSK and GSK ID
- UE1, UE2, and UE3 use the GSK and GSK IDs and other parameters to generate a key of SRTP/SRTCP.
- the group identifiers of the group corresponding to the group session are carried in steps S806a, S806b, and S806c, so as to notify the receiving end that they are invited to join the group session corresponding to the group identifier.
- the Mikey message in the embodiment shown in FIG. 8 also carries the GMK ID, so that the receiving end searches for the corresponding GMK according to the GMK ID, and then obtains and decrypts the GSK according to the security parameters derived by the GMK. And GSK ID.
- the GSK and GSK IDs of the group session are generated by the MCPTT server, and the GMS allocates the GMK to the group member by the Mikey message. Protect the delivery of GSK.
- the MCPTT server sends the GSK and the GSK ID to each of the associated UEs respectively (step S303b), which may specifically include:
- the MCPTT server For each UE in the associated UE, the MCPTT server processes according to the following operations for the second UE:
- the MCPTT server encapsulates the GSK and the GSK ID in an S/MIME message, where the S/MIME message is secured by a security key between the pre-configured MCPTT server and the second UE;
- the MCPTT server sends the S/MIME message to the second UE.
- the first UE will be the UE1 in FIG. 2, and the group session corresponds to the group.
- the associated UE includes the UE1, the UE2, and the UE3 as an example.
- the implementation manner is extended by the MCPTT server interacting with the associated UE in the group corresponding to the group session.
- the method for generating and delivering a key includes steps S901-S910:
- S901, UE1, UE2, and UE3 are respectively registered to the MCPTT server and belong to the group corresponding to one group session.
- S902, UE1, UE2, UE3, and MCPTT servers are all pre-configured with security keys or certificates that protect sensitive information in SIP signaling.
- the UE1 initiates a group session.
- the UE1 sends a group session request to the MCPTT server, where the group session request carries the group identifier of the group corresponding to the group session.
- the MCPTT server receives the group session request, and obtains an associated UE in the group according to the group identifier.
- the MCPTT server generates a GSK and a GSK ID of the group session.
- the MCPTT server For each UE in the associated UE, the MCPTT server processes according to the following operations for the second UE (including steps S906 and S907):
- the MCPTT server encapsulates the GSK and the GSK ID in an S/MIME message, where the S/MIME message is secured by using a security key between the pre-configured MCPTT server and the second UE.
- the MCPTT server sends the S/MIME message to the second UE.
- the associated UEs in the group corresponding to the group include UE1, UE2, and UE3.
- the associated UEs in the group include UE1, UE2, and UE3.
- step S906 specifically includes steps S906a, S906b, and S906c
- step S907 specifically includes steps S907a, S907b, and S907c:
- the S906a, MCPTT server encapsulates the GSK and GSK IDs in S/MIME message 2.
- the S/MIME message 2 is secured by using a security key between the pre-configured MCPTT server and the UE2.
- the MCPTT server sends a group session request to UE2, and the group will
- the message request carries the group identity and S/MIME message 2 of the group corresponding to the group session.
- the S906b, MCPTT server encapsulates the GSK and GSK IDs in S/MIME message 3.
- the S/MIME message 3 is secured by using a security key between the pre-configured MCPTT server and the UE3.
- the MCPTT server sends a group session request to the UE3, where the group session request carries the group identity and the S/MIME message 3 of the group corresponding to the group session.
- the group identifiers of the group corresponding to the group session are carried in steps S907a and S907b to inform the receiving end that they are invited to join the group session corresponding to the group identifier.
- UE2 parses S/MIME message 2 to obtain GSK and GSK ID.
- UE3 parses the S/MIME message 3 to obtain the GSK and GSK ID.
- the S906c, MCPTT server encapsulates the GSK and GSK IDs in S/MIME message 1.
- the MCPTT server replies to the UE1 with an acknowledgment message carrying the S/MIME message 1.
- UE1 parses S/MIME message 1 to obtain GSK and GSK ID.
- UE1, UE2, and UE3 use the GSK and GSK IDs and other parameters to generate a key of SRTP/SRTCP.
- the GSK and the GSK ID of the group session are generated by the MCPTT server, and the GMS does not allocate the GMK for the group member, but A security key or certificate for protecting sensitive information in the SIP signaling is configured between the MCPTT server and each UE, and the SGS is sent through the S/MIME message in the SIP signaling.
- the GSK and the GSK ID may also be used as security information, and are separately encapsulated and secured by the Mikey message, and the pre-configured protection between the UE and the MCPTT server is used to protect the SIP signaling.
- Security of information The embodiment of the present invention does not specifically limit the key or the certificate.
- the MCPTT server sends the GSK and the GSK ID to each of the UEs in the associated UE (step S303b), which may include:
- the MCPTT server For each UE in the associated UE, the MCPTT server processes according to the following operations for the second UE:
- the MCPTT server encapsulates the GSK and GSK IDs in a hypertext transfer protocol (English: abbreviation: HTTP) message;
- the MCPTT server sends an HTTP message to the second UE through a secure channel of a secure transport layer protocol (English: TLS) between the MCPTT server and the second UE.
- a secure transport layer protocol English: TLS
- the first UE is the UE1 in FIG. 2, and the associated UEs in the group session corresponding group include the UE1, the UE2, and the UE3, and the MCPTT server interacts with the associated UE in the group corresponding to the group session.
- the method for generating and delivering a key includes steps S1001-S1012:
- S1001, UE1, UE2, and UE3 are respectively registered to the MCPTT server and belong to the group corresponding to one group session.
- the S1002, UE1, UE2, UE3, and MCPTT servers all have a TLS secure channel established in advance.
- the UE1 initiates a group session.
- the UE1 sends a group session request to the MCPTT server, where the group session request carries the group identifier of the group corresponding to the group session.
- the MCPTT server receives the group session request, and obtains an associated UE in the group according to the group identifier; and the MCPTT server generates a GSK and a GSK ID of the group session.
- the MCPTT server For each UE in the associated UE, the MCPTT server processes according to the following operations for the second UE (including steps S1006 and S1007):
- the S1006 and MCPTT servers encapsulate the GSK and GSK IDs in an HTTP message.
- the MCPTT server sends an HTTP message to the second UE by using a TLS secure channel between the pre-established MCPTT server and the second UE.
- step S1007 specifically includes steps S1007a, S1007b, and S1007c:
- the S1007a and the MCPTT server send an HTTP message to the UE2 through the TLS secure channel 2 between the pre-established MCPTT server and the UE2.
- the S1007b and the MCPTT server send an HTTP message to the UE3 through the TLS secure channel 3 between the pre-established MCPTT server and the UE3.
- the S1007c and the MCPTT server send an HTTP message to the UE1 through the TLS secure channel 1 between the pre-established MCPTT server and the UE1.
- UE2 parses the HTTP message to obtain the GSK and GSK ID.
- UE3 parses the HTTP message to obtain the GSK and GSK ID.
- UE1 parses the HTTP message to obtain the GSK and GSK ID.
- the S1009a and the MCPTT server send a group session request to the UE2, where the group session request carries the group identifier of the group corresponding to the group session.
- the S1009b and the MCPTT server send a group session request to the UE3, where the group session request carries the group identifier of the group corresponding to the group session.
- S1010a and UE2 reply a confirmation message to the MCPTT server.
- S1010b and UE3 reply a confirmation message to the MCPTT server.
- the MCPTT server replies with a confirmation message to UE1.
- S1012 When performing group session communication, UE1, UE2, and UE3 use the GSK and GSK ID and other parameters to generate a key of SRTP/SRTCP.
- the group identifiers of the group corresponding to the group session are carried in steps S1009a and S1009b, so as to notify the receiving end that they are invited to join the group session corresponding to the group identifier.
- the HTTP message in the embodiment shown in FIG. 10 also carries the group identifier of the group corresponding to the group session, which is to notify the receiving end of the GSK and the The GSK ID is used for the group session corresponding to the group identifier.
- the GSK and the GSK identification ID of the group session are generated by the MCPTT server, and the GMS does not allocate the GMK for the group member.
- the MCPTT server delivers the GSK through the HTTP message, and the TLS security channel established between the MCPTT server and each UE is used to protect the GSK delivery.
- each group session is performed.
- the GSK is highly fresh, if the SRTP/SRTCP key is generated according to the GSK, the existing one can be avoided.
- the SRTP/SRTCP key of each group session is the same.
- the SRTP/SRTCP key will be used too frequently, which will increase the possibility of being compromised and improve the generation of SRTP/.
- the security level of the SRTCP key since the GSK belongs to the key of a group session, security isolation between different group sessions can be achieved, so that if the SRTP/SRTCP key is generated according to the GSK, the current can be avoided.
- the SRTP/SRTCP key of each group session is the same. If the SRTP/SRTCP key is compromised, the key of the subsequent group session will be leaked, and the security level of generating the SRTP/SRTCP key is improved. .
- the method for generating and delivering a key can solve the problem that the MCPTT group session member directly uses the GMS distributed by the GMS, and combines the rand, the CSB-ID, and the CS-ID to generate the SRTP/SRTCP key.
- the key will reduce the security level, not only provides end-to-end security protection for group sessions between MCPTT UEs, but also ensures that each group session uses a new security key, which improves the security level.
- all the foregoing embodiments of the present invention are directed to a scenario in which a group session initiation process exists.
- a scenario without a group session initiation process (such as pre-configuring a group session and then activating the group session by floor control), it may also be by the MCPTT server or a group session.
- One UE GSK and GSK IDs are generated to protect the GSK delivery through the Mikey message.
- This scenario carries the GSK's Mikey message and can be embedded in the real-time transport protocol (English name: Real-time Transport Protocol, English abbreviation: RTP) control protocol (English full name: RTP Control Protocol, English abbreviation: RTCP)) (for example: Floor request, floor granted, floor taken), these messages can be secured by the GSK-derived SRTCP key (full protection and / or encryption). However, if there is encryption, the Mikey message part cannot be encrypted, but is protected by the GMK-derived Mikey key, so that the receiving end decrypts the GSK.
- the embodiment of the present invention does not specifically describe the scenario of the group-free session initiation process.
- an embodiment of the present invention provides an MCPTT server 110, which is used to perform the steps performed by the MCPTT server in the method for generating and delivering a key shown in FIG.
- the MCPTT server 110 can include units corresponding to the respective steps.
- the processing unit 1101 and the sending unit 1102 may be included.
- the processing unit 1101 is configured to acquire, when the first UE initiates the group session, the group identifier of the group corresponding to the group session, the GSK and the GSK ID of the group session.
- the processing unit 1101 is further configured to acquire, according to the group identifier, an associated UE in the group.
- the sending unit 1102 is configured to separately send the GSK and the GSK ID to at least one of the associated UEs.
- the processing unit 1101 may obtain the group identifier of the group corresponding to the group session, the GSK and the GSK ID of the group session in multiple manners, and the following two exemplary implementations are provided by way of example. .
- the MCPTT server 110 further includes: a receiving unit 1103.
- the processing unit 1101 is specifically configured to:
- a group session request sent by the first UE where the group session request carries a group identifier of the group session corresponding group, a GSK and a GSK ID of the group session generated by the first UE.
- the sending unit 1102 is specifically configured to:
- the GSK and GSK IDs are respectively transmitted to each of the associated UEs except the first UE.
- the GSK and GSK IDs of the group session can be secured in the following two ways:
- the GSK and the GSK ID are encapsulated in a Mikey message, wherein the Mikey message is secured by a pre-configured GMK;
- the sending unit 1102 is specifically configured to:
- the Mikey message is sent to each UE except the first UE in the associated UE.
- the GSK and GSK ID of the group session generated by the first UE are encapsulated in a first S/MIME message, where the first S/MIME message adopts a pre-configured MCPTT server 110.
- the security key between the first UE and the first UE is secured.
- the processing unit 1101 is further configured to parse the first S/MIME message after obtaining the group session request sent by the first UE by the receiving unit 1103, and obtain the GSK and the GSK ID.
- the sending unit 1102 is specifically configured to:
- the GSK and the GSK ID are encapsulated in a second S/MIME message, wherein the second S/MIME message is secured by a security key between the pre-configured MCPTT server 110 and the second UE.
- the MCPTT server 110 further includes: a receiving unit 1103.
- the processing unit 1101 is specifically configured to:
- the sending unit 1102 is specifically configured to:
- the GSK and GSK IDs are respectively sent to each of the associated UEs.
- the GSK and GSK IDs of the group session can be secured in the following two ways:
- the group session request further carries the GMK ID of the group session.
- the processing unit 1101 is further configured to search for a GMK corresponding to the GMK ID according to the GMK ID before the sending unit 1102 separately sends the GSK and the GSK ID to each of the associated UEs.
- the sending unit 1102 is specifically configured to:
- the GSK and GSK IDs are encapsulated in a Mikey message, wherein the Mikey message is secured by the GMK.
- the Mikey message is sent to each of the associated UEs.
- the sending unit 1102 is specifically configured to:
- the GSK and GSK IDs are encapsulated in an S/MIME message, wherein the S/MIME message is secured by a security key between the pre-configured MCPTT server 110 and the second UE.
- the S/MIME message is sent to the second UE.
- the sending unit 1102 is specifically configured to:
- the GSK and the GSK ID are encapsulated in an HTTP message.
- the HTTP message is sent to the second UE through a pre-established TLS secure channel between the MCPTT server 110 and the second UE.
- the MCPTT server 110 of the embodiment of the present invention may correspond to the MCPTT server in the method for generating and delivering the key shown in FIG. 3 to FIG. 10 above, and
- the division and/or function of each unit in the MCPTT server 110 of the embodiment of the present invention is to implement the method for generating and delivering the key shown in FIG. 3 to FIG. 10 .
- details are not described herein again.
- the MCPTT server 110 in the embodiment of the present invention may be used to perform the foregoing method, and therefore, the technical effects that can be obtained are also referred to the foregoing method embodiments, and details are not described herein again.
- an embodiment of the present invention further provides an MCPTT server 130, including: a processor 1301, a memory 1302, a bus 1303, and a communication interface 1304.
- the memory 1302 is used to store computer execution instructions
- the processor 1301 is connected to the memory 1302 via the bus 1303, and when the MCPTT server 130 is running, the processor 1301 executes the computer execution instructions stored in the memory 1302, so that the MCPTT server 130 executes the above FIG. -
- the processor 1301 in the embodiment of the present invention may be a central processing unit (English name: central processing unit, English abbreviation: CPU), and may also be other general-purpose processors and digital signal processors (English full name: digital signal) Processing, English abbreviation: DSP), ASIC (English full name: application specific integrated circuit, English abbreviation: ASIC), field programmable gate array (English full name: field-programmable gate array, English abbreviation: FPGA) or other programmable Logic devices, discrete gates or transistor logic devices, discrete hardware components, and more.
- the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
- the processor may also be a dedicated processor, which may include at least one of a baseband processing chip, a radio frequency processing chip, and the like. Further, the dedicated processor may also include a chip having other dedicated processing functions of the MCPTT server 130.
- the memory 1302 may include a volatile memory (English: volatile memory), such as a random access memory (English name: random-access memory, English abbreviation: RAM); the memory 1302 may also include a non-volatile memory (English: non- Volatile memory), such as read-only memory (English full name: Read-only memory, English abbreviation: ROM), flash memory (English: flash memory), hard disk (English full name: hard disk drive, English abbreviation: HDD) or solid state drive (English full name: solid-state drive, English abbreviation: In addition, the memory 1302 may further include a combination of the above types of memories.
- a volatile memory such as a random access memory (English name: random-access memory, English abbreviation: RAM)
- the memory 1302 may also include a non-volatile memory (English: non- Volatile memory), such as read-only memory (English full name: Read-only memory, English abbreviation: ROM), flash memory (English: flash memory), hard disk (English full name
- the bus 1303 can include a data bus, a power bus, a control bus, and a signal status bus. For the sake of clarity in the present embodiment, various buses are illustrated as a bus 1303 in FIG.
- Communication interface 1304 may specifically be a transceiver on MCPTT server 130.
- the transceiver can be a wireless transceiver.
- the wireless transceiver can be an antenna of the MCPTT server 130 or the like.
- the processor 1301 performs data transmission and reception with other devices, such as the UE, through the communication interface 1304.
- the steps performed by the MCPTT server in the method flow shown in FIG. 3 to FIG. 10 can be implemented by the processor 1301 in the hardware form executing the computer-executed instructions in the form of software stored in the memory 1302. To avoid repetition, we will not repeat them here.
- the MCPTT server 130 provided by the embodiment of the present invention can be used to perform the foregoing method, and the technical effects can be obtained by referring to the foregoing method embodiments, and details are not described herein again.
- the embodiment further provides a readable medium, including a computer executing instruction, when the processor of the MCPTT server executes the computer to execute the instruction, the MCPTT server may perform the foregoing key as shown in FIG. 3-10.
- a readable medium including a computer executing instruction
- the MCPTT server may perform the foregoing key as shown in FIG. 3-10.
- the disclosed system, apparatus, and method may be implemented in other manners.
- the device embodiments described above are merely illustrative.
- the division of the modules or units is only a logical function division.
- there may be another division manner for example, multiple units or components may be used. Combinations can be integrated into another system, or some features can be ignored or not executed.
- the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
- the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
- each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
- the above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.
- the integrated unit if implemented in the form of a software functional unit and sold or used as a standalone product, may be stored in a computer readable storage medium.
- the technical solution of the present invention which is essential or contributes to the prior art, or all or part of the technical solution, may be embodied in the form of a software product stored in a storage medium.
- a number of instructions are included to cause a computer device (which may be a personal computer, server, or network device, etc.) or a processor to perform all or part of the steps of the methods described in various embodiments of the present invention.
- the foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
本发明实施例提供密钥的生成及下发方法、相关设备及系统,以至少解决目前MCPTT群组会话成员直接使用GMS分发的GMK和GMK ID来生成SRTP/SRTCP密钥会降低安全等级的问题。方法包括:在第一用户设备UE发起群组会话时,MCPTT服务器获取所述群组会话对应群组的组标识、所述群组会话的组会话密钥GSK和GSK ID;所述MCPTT服务器根据所述组标识,获取所述群组内的关联UE,并向所述关联UE中的至少一个UE分别发送所述GSK和所述GSK ID。本发明适用于通信领域。
Description
本发明涉及通信领域,尤其涉及密钥的生成及下发方法、相关设备及系统。
紧急任务即按即说(英文全称:mission critical push to talk over LTE,英文缩写:MCPTT)定义了长期演进(英文全称:long term evolution,英文缩写:LTE)网络下即按即说业务功能的实现标准。
其中,MCPTT安全保护是通过安全实时传输协议(英文全称:secure real-time transport protocol,英文缩写:SRTP)/安全实时传输控制协议(英文全称:secure real-time transport control protocol,英文缩写:SRTCP)中定义的安全机制来实现的,这要求所有MCPTT群组会话成员之间共享一个组密钥(英文全称:group master key,英文缩写:GMK),然后基于该GMK来实现后续通信的安全保护。目前,MCPTT群组会话成员直接使用组管理服务器(英文全称:group management server,英文缩写:GMS)分发的GMK,结合随机值(英文:rand)、加密会话束(英文全称:crypto session bundle,英文缩写:CSB)-标识(英文全称:identity,英文缩写:ID)和加密会话(英文全称:crypto session,英文缩写:CS)-ID来生成SRTP/SRTCP密钥。然而,一方面,对于每个MCPTT群组会话成员来说,由于GMK、rand、CSB-ID和CS-ID通常不会改变,从而会导致每次群组会话的SRTP/SRTCP密钥都一样,若群组会话频繁发起,将导致SRTP/SRTCP密钥过于频繁地被使用,从而导致被攻破的可能性增加。另一方面,不同的群组会话使用相同的SRTP/SRTCP密钥,那么如果SRTP/SRTCP密钥被攻破,则后续的群组会话的密钥都会泄露。也就是说,MCPTT群组
会话成员直接使用GMS分发的GMK,结合rand、CSB-ID和CS-ID来生成SRTP/SRTCP密钥会降低安全等级。
发明内容
本发明实施例提供密钥的生成及下发方法、相关设备及系统,以至少解决目前MCPTT群组会话成员直接使用GMS分发的GMK,结合rand、CSB-ID和CS-ID来生成SRTP/SRTCP密钥会降低安全等级的问题。
为达到上述目的,本发明实施例采用如下技术方案:
第一方面,提供一种密钥的生成及下发方法,包括:
在第一用户设备UE发起群组会话时,紧急任务即按即说MCPTT服务器获取该群组会话对应群组的组标识、该群组会话的组会话密钥GSK和GSK标识ID;
MCPTT服务器根据该组标识,获取该群组内的关联UE,并向该关联UE中的至少一个UE分别发送该GSK和该GSK ID。
具体的,在上述第一方面中,MCPTT服务器可以通过多种方式获取该群组会话对应群组的组标识、该群组会话的GSK和GSK ID,下面将示例性的提供两种可能的实现。
可选的,在第一方面第一种可能的实现方式中,结合第一方面,MCPTT服务器获取该群组会话对应群组的组标识、该群组会话的GSK和GSK ID,具体可以包括:
MCPTT服务器接收第一UE发送的群组会话请求,该群组会话请求携带该群组会话对应群组的组标识、第一UE生成的该群组会话的GSK和GSK ID;
MCPTT服务器向该关联UE中的至少一个UE分别发送该GSK和该GSK ID,具体可以包括:
MCPTT服务器向该关联UE中除第一UE之外的每个UE分别发送该GSK和该GSK ID。
其中,在该实现方式中,可以通过如下两种方式对该群组会话的GSK和GSK ID进行安全保护:
可选的,在第一方面第二种可能的实现方式中,结合第一方面第一种可能的实现方式,该GSK和该GSK ID被封装在Mikey消息中,其中,该Mikey消息用预先配置的组密钥GMK进行安全保护;
MCPTT服务器向该关联UE中除第一UE之外的每个UE分别发送该GSK和该GSK ID,具体可以包括:
MCPTT服务器向该关联UE中除第一UE之外的每个UE分别发送该Mikey消息。
需要说明的是,该Mikey消息用预先配置的GMK进行安全保护具体是指:
该Mikey消息中,可以根据GMK得出加密密钥(用于加密GSK和GSK ID)和完整性保护密钥(完整性保护GSK)来保护Mikey消息。也就是说,该Mikey消息采用GMK所推演的安全参数(包括加密密钥和完整性保护密钥)进行安全保护。该说明适用于下述各实施例,以下实施例中就不再一一赘述。
可选的,在第一方面第三种可能的实现方式中,结合第一方面第一种可能的实现方式,该第一UE生成的该群组会话的GSK和GSK ID被封装在第一S/MIME消息中,其中,该第一S/MIME消息采用预先配置的MCPTT服务器和该第一UE之间的安全密钥进行安全保护;
在MCPTT服务器接收第一UE发送的群组会话请求之后,还可以包括:
MCPTT服务器解析该第一S/MIME消息,获得该GSK和该GSK ID;
MCPTT服务器向该关联UE中除第一UE之外的每个UE分别发送该GSK和该GSK ID,具体可以包括:
对于该关联UE中除第一UE之外的每个UE,MCPTT服务器均按照下面针对第二UE的操作进行处理:
MCPTT服务器将该GSK和该GSK ID封装在第二S/MIME消
息中,其中,该第二S/MIME消息采用预先配置的MCPTT服务器和该第二UE之间的安全密钥进行安全保护;
MCPTT服务器向该第二UE发送该第二S/MIME消息。
可选的,在第一方面第四种可能的实现方式中,结合第一方面,MCPTT服务器获取该群组会话对应群组的组标识、该群组会话的GSK和GSK ID,具体可以包括:
MCPTT服务器接收第一UE发送的群组会话请求,该群组会话请求携带该群组会话对应群组的组标识;以及,MCPTT服务器生成该群组会话的GSK和GSK ID;
MCPTT服务器向该关联UE中的至少一个UE分别发送该GSK和该GSK ID,具体可以包括:
MCPTT服务器向该关联UE中的每个UE分别发送该GSK和该GSK ID。
其中,在该实现方式中,可以通过如下三种方式对该群组会话的GSK和GSK ID进行安全保护:
可选的,在第一方面第五种可能的实现方式中,结合第一方面第四种可能的实现方式,该群组会话请求还携带该群组会话的组密钥标识GMK ID;
在MCPTT服务器向该关联UE中的每个UE分别发送该GSK和该GSK ID之前,还可以包括:
MCPTT服务器根据该GMK ID,查找该GMK ID对应的GMK;
MCPTT服务器向该关联UE中的每个UE分别发送该GSK和该GSK ID,具体可以包括:
MCPTT服务器将该GSK和该GSK ID封装在Mikey消息中,其中,该Mikey消息采用该GMK进行安全保护;
MCPTT服务器向该关联UE中的每个UE分别发送该Mikey消息。
可选的,在第一方面第六种可能的实现方式中,结合第一方
面第四种可能的实现方式,MCPTT服务器向该关联UE中的每个UE分别发送该GSK和该GSK ID,具体可以包括:
对于该关联UE中的每个UE,MCPTT服务器均按照下面针对第二UE的操作进行处理:
MCPTT服务器将该GSK和该GSK ID封装在S/MIME消息中,其中,该S/MIME消息采用预先配置的MCPTT服务器和该第二UE之间的安全密钥进行安全保护;
MCPTT服务器向该第二UE发送该S/MIME消息。
可选的,在第一方面第七种可能的实现方式中,结合第一方面第四种可能的实现方式,MCPTT服务器向该关联UE中的每个UE分别发送该GSK和该GSK ID,具体可以包括:
对于该关联UE中的每个UE,MCPTT服务器均按照下面针对第二UE的操作进行处理:
MCPTT服务器将该GSK和该GSK ID封装在超文本传输协议HTTP消息中;
MCPTT服务器通过预先建立的MCPTT服务器和该第二UE之间安全传输层协议TLS安全通道向该第二UE发送该HTTP消息。
基于本发明实施例提供的密钥的生成及下发方法,本发明实施例中,在第一UE发起群组会话时,MCPTT服务器可以获取该群组会话对应群组的组标识、该群组会话的GSK和GSK ID,进而在MCPTT服务器根据该组标识,获取该群组内的关联UE之后,可以向该关联UE中的至少一个UE分别发送GSK和GSK ID。也就是说,本发明实施例中,每次群组会话,都有一个新鲜独立的GSK。这样,不仅为MCPTT UE之间的群组会话提供了端到端的安全保护;同时,一方面,由于该GSK新鲜性高较高,从而若根据该GSK生成SRTP/SRTCP密钥,可以避免现有技术中每次群组会话的SRTP/SRTCP密钥都一样,若群组会话频繁发起,将导致SRTP/SRTCP密钥过于频繁地被使用,从而导致被攻破的可能性增
加问题,提升生成SRTP/SRTCP密钥的安全等级;另一方面,由于该GSK属于一次群组会话的密钥,可以做到不同群组会话之间的安全隔离,从而若根据GSK生成SRTP/SRTCP密钥,可以避免现有技术中每次群组会话的SRTP/SRTCP密钥都一样,如果SRTP/SRTCP密钥被攻破,则后续的群组会话的密钥都会泄露的问题,提升生成SRTP/SRTCP密钥的安全等级。综上,基于本发明实施例提供的密钥的生成及下发方法,可以解决目前MCPTT群组会话成员直接使用GMS分发的GMK,结合rand、CSB-ID和CS-ID来生成SRTP/SRTCP密钥会降低安全等级的问题,不仅为MCPTT UE之间的群组会话提供了端到端的安全保护;同时,还保证了每次群组会话都使用新的安全密钥,提高了安全等级。
第二方面,提供一种紧急任务即按即说MCPTT服务器,包括:处理单元和发送单元;
处理单元,用于在第一用户设备UE发起群组会话时,获取该群组会话对应群组的组标识、该群组会话的组会话密钥GSK和GSK标识ID;
处理单元,还用于根据该组标识,获取该群组内的关联UE;
发送单元,用于向该关联UE中的至少一个UE分别发送该GSK和该GSK ID。
具体的,在上述第二方面中,处理单元可以通过多种方式获取该群组会话对应群组的组标识、该群组会话的GSK和GSK ID,下面将示例性的提供两种可能的实现。
可选的,在第二方面第一种可能的实现方式中,结合第二方面,MCPTT服务器还包括:接收单元;
处理单元具体用于:
通过接收单元接收第一UE发送的群组会话请求,该群组会话请求携带该群组会话对应群组的组标识、第一UE生成的该群组会话的GSK和GSK ID;
发送单元具体用于:
向该关联UE中除第一UE之外的每个UE分别发送该GSK和该GSK ID。
其中,在该实现方式中,可以通过如下两种方式对该群组会话的GSK和GSK ID进行安全保护:
可选的,在第二方面第二种可能的实现方式中,结合第二方面第一种可能的实现方式,该GSK和该GSK ID被封装在Mikey消息中,其中,该Mikey消息用预先配置的组密钥GMK进行安全保护;
发送单元具体用于:
向该关联UE中除第一UE之外的每个UE分别发送该Mikey消息。
可选的,在第二方面第三种可能的实现方式中,结合第二方面第一种可能的实现方式,该第一UE生成的该群组会话的GSK和GSK ID被封装在第一S/MIME消息中,其中,该第一S/MIME消息采用预先配置的MCPTT服务器和该第一UE之间的安全密钥进行安全保护;
处理单元,还用于在通过接收单元接收第一UE发送的群组会话请求之后,解析该第一S/MIME消息,获得该GSK和该GSK ID;
发送单元具体用于:
对于该关联UE中除第一UE之外的每个UE,均按照下面针对第二UE的操作进行处理:
将该GSK和该GSK ID封装在第二S/MIME消息中,其中,该第二S/MIME消息采用预先配置的MCPTT服务器和该第二UE之间的安全密钥进行安全保护;
向该第二UE发送该第二S/MIME消息。
可选的,在第二方面第四种可能的实现方式中,结合第二方面,MCPTT服务器还包括:接收单元;
处理单元具体用于:
通过接收单元接收第一UE发送的群组会话请求,该群组会话请求携带该群组会话对应群组的组标识;以及,生成该群组会话的GSK和GSK ID;
发送单元具体用于:
向该关联UE中的每个UE分别发送该GSK和该GSK ID。
其中,在该实现方式中,可以通过如下三种方式对该群组会话的GSK和GSK ID进行安全保护:
可选的,在第二方面第五种可能的实现方式中,结合第二方面第四种可能的实现方式,该群组会话请求还携带该群组会话的组密钥标识GMK ID;
处理单元,还用于在发送单元向该关联UE中的每个UE分别发送该GSK和该GSK ID之前,根据该GMK ID,查找该GMK ID对应的GMK;
发送单元具体用于:
将该GSK和该GSK ID封装在Mikey消息中,其中,该Mikey消息采用该GMK进行安全保护;
向该关联UE中的每个UE分别发送该Mikey消息。
可选的,在第二方面第六种可能的实现方式中,结合第二方面第四种可能的实现方式,发送单元具体用于:
对于该关联UE中的每个UE,均按照下面针对第二UE的操作进行处理:
将该GSK和该GSK ID封装在S/MIME消息中,其中,该S/MIME消息采用预先配置的MCPTT服务器和该第二UE之间的安全密钥进行安全保护;
向该第二UE发送该S/MIME消息。
可选的,在第二方面第七种可能的实现方式中,结合第二方面第四种可能的实现方式,发送单元具体用于:
对于该关联UE中的每个UE,均按照下面针对第二UE的操作进行处理:
将该GSK和该GSK ID封装在超文本传输协议HTTP消息中;
通过预先建立的MCPTT服务器和该第二UE之间安全传输层协议TLS安全通道向该第二UE发送该HTTP消息。
由于本发明实施例提供的MCPTT服务器可以用于执行上述第一方面或者第一方面任一种可选的实现方式中所述的密钥的生成及下发方法,因此,其所能获得的技术效果可以参考上述第一方面中MCPTT服务器执行的密钥的生成及下发方法的技术效果,此处不再赘述。
第三方面,提供一种紧急任务即按即说MCPTT服务器,包括:处理器、存储器、总线和通信接口;
其中,存储器用于存储计算机执行指令,处理器与存储器通过总线连接,当MCPTT服务器运行时,处理器执行存储器存储的计算机执行指令,以使MCPTT服务器执行如上述第一方面或第一方面任一种可能的实现方式中所述的密钥的生成及下发方法。
由于本发明实施例提供的MCPTT服务器可以用于执行上述第一方面或者第一方面任一种可选的实现方式中所述的密钥的生成及下发方法,因此,其所能获得的技术效果可以参考上述第一方面中MCPTT服务器执行的密钥的生成及下发方法的技术效果,此处不再赘述。
第四方面,提供一种密钥的生成及下发系统,包括如上述第二方面或者第二方面任一种可选的实现方式中所述的紧急任务即按即说MCPTT服务器、以及与该MCPTT服务器连接的多个用户设备UE。
由于本发明实施例提供的密钥的生成及下发系统包括如上述第二方面或者第二方面任一种可选的实现方式中所述的MCPTT服务器,因此,其所能获得的技术效果可以参考上述第二方面中MCPTT服务器的技术效果,此处不再赘述。
第五方面,提供一种密钥的生成及下发系统,包括如上述第三方面所述的紧急任务即按即说MCPTT服务器、以及与该
MCPTT服务器连接的多个用户设备UE。
由于本发明实施例提供的密钥的生成及下发系统包括如上述第三方面所述的MCPTT服务器,因此,其所能获得的技术效果可以参考上述第三方面中MCPTT服务器的技术效果,此处不再赘述。
第六方面,提供一种可读介质,包括计算机执行指令,当MCPTT服务器的处理器执行该计算机执行指令时,该MCPTT服务器执行如上述第一方面或者第一方面任一种可选的实现方式中所述的密钥的生成及下发方法。
图1为现有MCPTT架构的示意图;
图2为本发明实施例提供的密钥的生成及下发系统架构示意图;
图3为本发明实施例提供的密钥的生成及下发方法流程示意图一;
图4为本发明实施例提供的密钥的生成及下发方法流程示意图二;
图5为本发明实施例提供的密钥的生成及下发方法交互示意图一;
图6为本发明实施例提供的密钥的生成及下发方法交互示意图二;
图7为本发明实施例提供的密钥的生成及下发方法流程示意图三;
图8为本发明实施例提供的密钥的生成及下发方法交互示意图三;
图9为本发明实施例提供的密钥的生成及下发方法交互示意图四;
图10为本发明实施例提供的密钥的生成及下发方法交互示意图五;
图11为本发明实施例提供的MCPTT服务器的结构示意图一;
图12为本发明实施例提供的MCPTT服务器的结构示意图二;
图13为本发明实施例提供的MCPTT服务器的结构示意图三。
为了下述各实施例的描述清楚简洁,首先给出MCPTT架构的简要介绍:
图1为现有MCPTT架构的示意图。如图1所示,密钥管理服务器(key management server,英文缩写:KMS)负责将基于身份的安全参数(英文:identity-based security parameters)下发给所有相关实体,包括:通过通用服务核心节点(英文全称:common service core,英文缩写:CSC)-8接口分发给MCPTT用户设备(英文全称:,英文缩写:UE),通过CSC-9接口分发给MCPTT服务器,以及通过CSC-10接口分发给GMS。这样,这些功能实体之间就可以基于identity-based security parameters来对消息进行完整性保护(发送端identity对应的私钥签名)和加密(接收端的identity加密)。
其中,关于图1的详细描述可参考现有的MCPTT标准,本发明实施例在此不再赘述。
对于MCPTT UE和MCPTT服务器之间的信令面的信令,使用的是会话初始协议(英文全称:session initiation protocol,英文缩写:SIP)信令,其依赖于IPsec安全。由于分组交换(英文全称:packet switching,英文缩写:PS)代理(英文:agency)可能不信任移动网络运营商(英文全称:mobile network operator,英文缩写:MNO)网络,而SIP核心(英文:core)可能由MNO部署,因此MCPTT UE和MCPTT服务器之间的应用层的一些敏感数据(比如身份标识),可能需要得带额外的安全保护。目前考虑使用多用途网际邮件扩充协议(英文全称:secure multipurpose internet mail extensions,英文缩写:S/MIME)来封装及保护这些敏感数据,保护方法可能存在几种可能:1、KMS将预共享密钥
(英文全称:pre-shared key,英文缩写:PSK)配置到MCPTT UE和MCPTT服务器上;2、基于KMS配置的I Identity-based security parameters;3、证书机制。
对于用户面的数据,用于保护群组会话的GMK是由GMS通过Mikey-SAKKE消息发给MCPTT群组会话成员(即MCPTT UE)的;然后MCPTT群组会话成员直接根据GMK,结合rand、CSB-ID和CS-ID来生成SRTP/SRTCP密钥。即,如背景技术中所述,目前,MCPTT群组会话成员直接使用GMS分发的GMK,结合rand、CSB-ID和CS-ID来生成SRTP/SRTCP密钥。
然而,如背景技术中所述,一方面,对于每个MCPTT群组会话成员来说,由于GMK、rand、CSB-ID和CS-ID通常不会改变,从而会导致每次群组会话的SRTP/SRTCP密钥都一样,若群组会话频繁发起,将导致SRTP/SRTCP密钥过于频繁地被使用,从而导致被攻破的可能性增加。另一方面,不同的群组会话使用相同的SRTP/SRTCP密钥,那么如果SRTP/SRTCP密钥被攻破,则后续的群组会话的密钥都会泄露。也就是说,MCPTT群组会话成员直接使用GMS分发的GMK,结合rand、CSB-ID和CS-ID来生成SRTP/SRTCP密钥会降低安全等级。
为了解决该问题,本发明实施例提供了密钥的生成及下发方法、相关设备及系统,以至少解决目前MCPTT群组会话成员直接使用GMS分发的GMK,结合rand、CSB-ID和CS-ID来生成SRTP/SRTCP密钥会降低安全等级的问题,不仅为MCPTT UE之间的群组会话提供了端到端的安全保护;同时,还保证了每次群组会话都使用新的安全密钥,提高了安全等级。下面将结合本发明实施例中的附图,对本发明实施例中的技术方案进行清楚、完整地描述。
需要说明的是,为了便于清楚描述本发明实施例的技术方案,在本发明的实施例中,采用了“第一”、“第二”等字样对功能和作用基本相同的相同项或相似项进行区分,本领域技术人
员可以理解“第一”、“第二”等字样并不对数量和执行次序进行限定。
需要说明的是,本文中的“/”表示或的意思,例如,A/B可以表示A或B;本文中的“和/或”仅仅是一种描述关联对象的关联关系,表示可以存在三种关系,例如,A和/或B,可以表示:单独存在A,同时存在A和B,单独存在B这三种情况。“多个”是指两个或多于两个。
如本申请所使用的,术语“组件”、“模块”、“系统”等等旨在指代计算机相关实体,该计算机相关实体可以是硬件、固件、硬件和软件的结合、软件或者运行中的软件。例如,组件可以是,但不限于是:在处理器上运行的处理、处理器、对象、可执行文件、执行中的线程、程序和/或计算机。作为示例,在计算设备上运行的应用和该计算设备都可以是组件。一个或多个组件可以存在于执行中的过程和/或线程中,并且组件可以位于一个计算机中以及/或者分布在两个或更多个计算机之间。此外,这些组件能够从在其上具有各种数据结构的各种计算机可读介质中执行。这些组件可以通过诸如根据具有一个或多个数据分组(例如,来自一个组件的数据,该组件与本地系统、分布式系统中的另一个组件进行交互和/或以信号的方式通过诸如互联网之类的网络与其它系统进行交互)的信号,以本地和/或远程过程的方式进行通信。
本申请中的通信网络包括有线通信网络和无线通信网络。其中,无线通信网络,是一种提供无线通信功能的网络。无线通信网络可以采用不同的通信技术,例如码分多址(英文全称:code division multiple access,英文缩写:CDMA)、宽带码分多址(英文全称:wideband code division multiple access,英文缩写:WCDMA)、时分多址(英文全称:time division multiple access,英文缩写:TDMA)、频分多址(英文全称:frequency division multiple access,英文缩写:FDMA)、正交频分多址(英文:
orthogonal frequency-division multiple access,英文缩写:OFDMA)、单载波频分多址(英文全称:single carrier FDMA,英文缩写:SC-FDMA)、载波侦听多路访问/冲突避免(英文全称:carrier sense multiple access with collision avoidance)。根据不同网络的容量、速率、时延等因素可以将网络分为2G(英文:generation)网络、3G网络或者4G网络。典型的2G网络包括全球移动通信系统(英文全称:global system for mobile communications/general packet radio service,英文缩写:GSM)网络或者通用分组无线业务(英文全称:general packet radio service,英文缩写:GPRS)网络,典型的3G网络包括通用移动通信系统(英文全称:universal mobile telecommunications system,英文缩写:UMTS)网络,典型的4G网络包括长期演进(英文全称:long term evolution,英文缩写:LTE)网络。其中,UMTS网络有时也可以称为通用陆地无线接入网(英文全称:universal terrestrial radio access network,英文缩写:UTRAN),LTE网络有时也可以称为演进型通用陆地无线接入网(英文全称:evolved universal terrestrial radio access network,英文缩写:E-UTRAN)。根据资源分配方式的不同,可以分为蜂窝通信网络和无线局域网络(英文全称:wireless local area networks,英文缩写:WLAN),其中,蜂窝通信网络为调度主导,WLAN为竞争主导。前述的2G、3G和4G网络,均为蜂窝通信网络。本领域技术人员应知,随着技术的发展本发明实施例提供的技术方案同样可以应用于其他的无线通信网络,例如4.5G或者5G网络,或其他非蜂窝通信网络。为了简洁,本发明实施例有时会将无线通信网络英文缩写为网络。
UE是一种终端设备,可以是可移动的终端设备,也可以是不可移动的终端设备。该终端设备主要用于接收或者发送业务数据。用户设备可分布于网络中,在不同的网络中用户设备有不同的名称,例如:终端,移动台,用户单元,站台,蜂窝电话,个
人数字助理,无线调制解调器,无线通信设备,手持设备,膝上型电脑,无绳电话,无线本地环路台等。该用户设备可以经无线接入网(英文全称:radio access network,英文缩写:RAN)(无线通信网络的接入部分)与一个或多个核心网进行通信,例如与无线接入网交换语音和/或数据。
此外,本申请将围绕可包括多个设备、组件、模块等的系统来呈现各个方面、实施例或特征。应当理解和明白的是,各个系统可以包括另外的设备、组件、模块等,并且/或者可以并不包括结合附图讨论的所有设备、组件、模块等。此外,还可以使用这些方案的组合。
另外,在本发明实施例中,“示例的”、或者“比如”等词用于表示作例子、例证或说明。本申请中被描述为“示例”或“比如”的任何实施例或设计方案不应被解释为比其它实施例或设计方案更优选或更具优势。确切而言,使用“示例的”、或者“比如”等词旨在以具体方式呈现概念。
本发明实施例中,“的(英文:of)”,“相应的(英文:corresponding,relevant)”和“对应的(英文:corresponding)”有时可以混用,应当指出的是,在不强调其区别时,其所要表达的含义是一致的。
本发明实施例描述的网络架构以及业务场景是为了更加清楚的说明本发明实施例的技术方案,并不构成对于本发明实施例提供的技术方案的限定,本领域普通技术人员可知,随着网络架构的演变和新业务场景的出现,本发明实施例提供的技术方案对于类似的技术问题,同样适用。
下面将给出本发明实施例所适用的密钥的生成及下发系统架构示意图,如图2所示,该密钥的生成及下发系统包括MCPTT服务器以及与该MCPTT服务器连接的多个MCPTT UE(以下简称UE,如UE1、UE2、和UE3等)。其中,此处的“连接”是指可以相互通信,具体可以通过有线方式连接,也可以通过无线方式连
接,本发明实施例对此不作具体限定。其中,相互连接的设备之间可能是直连,也可能是通过其它设备连接,本发明实施例对此不作具体限定。
需要说明的是,图2所示的密钥的生成及下发系统中仅是示例性的画出了一个MCPTT群组会话对应的群组,该群组中仅是示例性的画出了UE1、UE2、和UE3共3个UE,当然,该密钥的生成及下发系统中可能不限于仅包含一个MCPTT群组会话对应的群组,可以包含任意数量个MCPTT群组会话对应的群组;该群组中也可能不限于包含3个UE,可以包含不小于2的任意数量个UE,本发明实施例对此不作具体限定。
下面将基于图2所示的密钥的生成及下发系统,对本发明进行详细阐述。
如图3所示,本发明实施例提供密钥的生成及下发方法,包括步骤S301-S303:
S301、在第一UE发起群组会话时,MCPTT服务器获取该群组会话对应群组的组标识、该群组会话的组会话密钥(英文全称:group session key,英文缩写:GSK)和GSK ID。
具体的,本发明实施例中的第一UE为存在群组会话的场景下,发起群组会话的UE,该第一UE可以为图2所示的密钥的生成及下发系统中的任意一个UE,本发明实施例对此不作具体限定。
S302、MCPTT服务器根据该组标识,获取该群组内的关联UE。
具体的,本发明实施例中的关联UE具体是指,该群组内被允许进行MCPTT群组会话的UE。
MCPTT服务器根据该组标识,即可获取该群组内的关联UE。
需要说明的是,在MCPTT服务器根据该组标识,获取该群组内的关联UE之前,MCPTT服务器需要根据该组标识,结合接收到的MCPTT ID以及预先存储的组策略/用户策略来验证该第一
UE是否有权限发起该群组会话,当第一UE有权限发起该群组会话时,MCPTT服务器才会根据该组标识,获取该群组内的关联UE。本发明实施例对该情况不作详细阐述,具体可参考现有的实现。
S303、MCPTT服务器向该关联UE中的至少一个UE分别发送GSK和GSK ID。
基于本发明实施例提供的密钥的生成及下发方法,本发明实施例中,在第一UE发起群组会话时,MCPTT服务器可以获取该群组会话对应群组的组标识、该群组会话的GSK和GSK ID,进而在MCPTT服务器根据该组标识,获取该群组内的关联UE之后,可以向该关联UE中的至少一个UE分别发送GSK和GSK ID。也就是说,本发明实施例中,每次群组会话,都有一个新鲜独立的GSK。这样,不仅为MCPTT UE之间的群组会话提供了端到端的安全保护;同时,一方面,由于该GSK新鲜性高较高,从而若根据该GSK生成SRTP/SRTCP密钥,可以避免现有技术中每次群组会话的SRTP/SRTCP密钥都一样,若群组会话频繁发起,将导致SRTP/SRTCP密钥过于频繁地被使用,从而导致被攻破的可能性增加问题,提升生成SRTP/SRTCP密钥的安全等级;另一方面,由于该GSK属于一次群组会话的密钥,可以做到不同群组会话之间的安全隔离,从而若根据GSK生成SRTP/SRTCP密钥,可以避免现有技术中每次群组会话的SRTP/SRTCP密钥都一样,如果SRTP/SRTCP密钥被攻破,则后续的群组会话的密钥都会泄露的问题,提升生成SRTP/SRTCP密钥的安全等级。综上,基于本发明实施例提供的密钥的生成及下发方法,可以解决目前MCPTT群组会话成员直接使用GMS分发的GMK,结合rand、CSB-ID和CS-ID来生成SRTP/SRTCP密钥会降低安全等级的问题,不仅为MCPTT UE之间的群组会话提供了端到端的安全保护;同时,还保证了每次群组会话都使用新的安全密钥,提高了安全等级。
具体的,在图3所示的实施例中,MCPTT服务器可以通过多
种方式获取该群组会话对应群组的组标识、该群组会话的GSK和GSK ID,下面将示例性的提供两种可能的实现。
可选的,如图4所示,一种可能的实现方式中,在第一UE发起群组会话时,MCPTT服务器获取该群组会话对应群组的组标识、该群组会话的GSK和GSK ID(步骤S301),具体可以包括:
S301a、在第一UE发起群组会话时,MCPTT服务器接收第一UE发送的群组会话请求,该群组会话请求携带该群组会话对应群组的组标识、第一UE生成的该群组会话的GSK和GSK ID。
进而,MCPTT服务器向该关联UE中的至少一个UE分别发送GSK和GSK ID(步骤S303),具体可以包括:
S303a、MCPTT服务器向该关联UE中除第一UE之外的每个UE分别发送GSK和GSK ID。
其中,在该实现方式中,可以通过如下两种方式对该群组会话的GSK和GSK ID进行安全保护:
一种可能的实现方式中,GSK和GSK ID被封装在Mikey消息中,其中,该Mikey消息用预先配置的GMK进行安全保护。
进而,MCPTT服务器向该关联UE中除第一UE之外的每个UE分别发送GSK和GSK ID(步骤S303a),具体可以包括:
MCPTT服务器向该关联UE中除第一UE之外的每个UE分别发送该Mikey消息。
需要说明的是,该Mikey消息用预先配置的GMK进行安全保护具体是指:
该Mikey消息中,可以根据GMK得出加密密钥(用于加密GSK和GSK ID)和完整性保护密钥(完整性保护GSK)来保护Mikey消息。也就是说,该Mikey消息采用GMK所推演的安全参数(包括加密密钥和完整性保护密钥)进行安全保护。该说明适用于下述各实施例,以下实施例中就不再一一赘述。
下面将以第一UE为图2中的UE1,该群组会话对应群组内的关联UE包括UE1、UE2和UE3为例,通过MCPTT服务器与该群
组会话对应群组内的关联UE交互的方式,对该实现方式进行展开说明。如图5所示,本发明实施例提供的密钥的生成及下发方法包括步骤S501-S510:
S501、UE1、UE2和UE3分别注册到MCPTT服务器并同属于一个群组会话对应的群组。
S502、UE1、UE2、UE3和MCPTT服务器都预先配置了GMK和GMK ID。
S503、在UE1发起群组会话时,UE1生成该群组会话的GSK和GSK ID,并封装在Mikey消息中。
其中,该Mikey消息用预先配置的GMK进行安全保护。
需要说明的是,图5所示的Mikey消息中携带了GMK ID,这是为了接收端解析该Mikey消息,当然,若该群组会话对应群组的组标识与GMK一一对应,也就是一个组标识对应一个GMK,则也可以不携带GMK ID,本发明实施例对此不作具体限定。
S504、UE1向MCPTT服务器发送群组会话请求,该群组会话请求携带该群组会话对应群组的组标识和Mikey消息。
S505、MCPTT服务器接收该群组会话请求,并根据该组标识,获取该群组内的关联UE。
需要说明的是,本发明实施例中,若有需要,MCPTT服务器还可以解析Mikey消息以获取GSK和GSK ID(如用于LI),本发明实施例对此不作具体限定。
S506、MCPTT服务器向该关联UE中除UE1之外的每个UE分别发送GSK和GSK ID。
由于该实施例以该群组会话对应群组内的关联UE包括UE1、UE2和UE3为例进行说明,因此,此时,该群组内的关联UE中除UE1之外的关联UE包括UE2和UE3。进而,步骤S506具体包括步骤S506a和S506b:
S506a、MCPTT服务器向UE2发送群组会话请求,该群组会话请求携带该群组会话对应群组的组标识和Mikey消息。
S506b、MCPTT服务器向UE3发送群组会话请求,该群组会话请求携带该群组会话对应群组的组标识和Mikey消息。
需要说明的是,步骤S506a和S506b中之所以携带该群组会话对应群组的组标识,是为了通知接收端其被邀请加入该组标识所对应的群组会话。
S507a、UE2解析Mikey消息获取GSK和GSK ID。
S507b、UE3解析Mikey消息获取GSK和GSK ID。
S508a、UE2向MCPTT服务器回复确认消息。
S508b、UE3向MCPTT服务器回复确认消息。
S509、MCPTT服务器向UE1回复确认消息。
S510、当进行群组会话通信时,UE1、UE2和UE3用该GSK和GSK ID以及其它参数来生成SRTP/SRTCP的密钥。
由步骤S501-S510可以看出,本发明实施例提供的密钥的生成及下发方法中,由发起群组会话的UE生成该群组会话的GSK和GSK ID,并且GMS为组成员分配GMK,由Mikey消息保护GSK的下发。
另一种可能的实现方式中,第一UE生成的该群组会话的GSK和GSK ID被封装在第一S/MIME消息中,其中,该第一S/MIME消息采用预先配置的MCPTT服务器和第一UE之间的安全密钥进行安全保护。
在MCPTT服务器接收第一UE发送的群组会话请求(步骤S301a)之后,还可以包括:
MCPTT服务器解析该第一S/MIME消息,获得GSK和所述GSK ID。
进而,MCPTT服务器向该关联UE中除第一UE之外的每个UE分别发送GSK和GSK(步骤S303a),具体可以包括:
对于该关联UE中除第一UE之外的每个UE,MCPTT服务器均按照下面针对第二UE的操作进行处理:
MCPTT服务器将GSK和GSK ID封装在第二S/MIME消息
中,其中,该第二S/MIME消息采用预先配置的MCPTT服务器和第二UE之间的安全密钥进行安全保护;
MCPTT服务器向第二UE发送该第二S/MIME消息。
下面将以第一UE为图2中的UE1,该群组会话对应群组内的关联UE包括UE1、UE2和UE3为例,通过MCPTT服务器与该群组会话对应群组内的关联UE交互的方式,对该实现方式进行展开说明。如图6所示,本发明实施例提供的密钥的生成及下发方法包括步骤S601-S611:
S601、UE1、UE2和UE3分别注册到MCPTT服务器并同属于一个群组会话对应的群组。
S602、UE1、UE2、UE3和MCPTT服务器都预先配置了保护SIP信令中敏感信息的安全密钥或证书。
S603、在UE1发起群组会话时,UE1生成该群组会话的GSK和GSK ID,并封装在第一S/MIME消息(S/MIME消息1)中。
其中,该第一S/MIME消息采用预先配置的MCPTT服务器和UE1之间的安全密钥进行安全保护。
S604、UE1向MCPTT服务器发送群组会话请求,该群组会话请求携带该群组会话对应群组的组标识和第一S/MIME消息。
S605、MCPTT服务器接收该群组会话请求,并根据该组标识,获取该群组内的关联UE;以及解析第一S/MIME消息以获取GSK和GSK ID。
对于该关联UE中除UE1之外的每个UE,MCPTT服务器均按照下面针对第二UE的操作(包括步骤S606和S607)进行处理:
S606、MCPTT服务器将GSK和GSK ID封装在第二S/MIME消息中,其中,第二S/MIME消息采用预先配置的MCPTT服务器和第二UE之间的安全密钥进行安全保护。
S607、MCPTT服务器向第二UE发送第二S/MIME消息。
由于该实施例以该群组会话对应群组内的关联UE包括UE1、UE2和UE3为例进行说明,因此,此时,该群组内的关联UE中除
UE1之外的关联UE包括UE2和UE3。进而,步骤S606具体包括步骤S606a和S606b,步骤S607具体包括步骤S607a和S607b:
S606a、MCPTT服务器将GSK和GSK ID封装在S/MIME消息2中。
其中,该S/MIME消息2采用预先配置的MCPTT服务器和UE2之间的安全密钥进行安全保护。
S607a、MCPTT服务器向UE2发送群组会话请求,该群组会话请求携带该群组会话对应群组的组标识和S/MIME消息2。
S606b、MCPTT服务器将GSK和GSK ID封装在S/MIME消息3中。
其中,该S/MIME消息3采用预先配置的MCPTT服务器和UE3之间的安全密钥进行安全保护。
S607b、MCPTT服务器向UE3发送群组会话请求,该群组会话请求携带该群组会话对应群组的组标识和S/MIME消息3。
需要说明的是,步骤S607a和S607b中之所以携带该群组会话对应群组的组标识,是为了通知接收端其被邀请加入该组标识所对应的群组会话。
S608a、UE2解析S/MIME消息2获取GSK和GSK ID。
S608b、UE3解析S/MIME消息3获取GSK和GSK ID。
S609a、UE2向MCPTT服务器回复确认消息。
S609b、UE3向MCPTT服务器回复确认消息。
S610、MCPTT服务器向UE1回复确认消息。
S611、当进行群组会话通信时,UE1、UE2和UE3用该GSK和GSK ID以及其它参数来生成SRTP/SRTCP的密钥。
由步骤S601-S611可以看出,本发明实施例提供的密钥的生成及下发方法中,由发起群组会话的UE生成该群组会话的GSK和GSK ID,并且GMS不为组成员分配GMK,而是MCPTT服务器和每个UE之间配置了保护SIP信令中敏感信息的安全密钥或证书,通过SIP信令中的S/MIME消息来保护GSK的下发。
可选的,图6所示的实施例中,GSK和GSK ID也可以作为安全信息,单独由Mikey消息封装并进行安全保护,使用的是UE和MCPTT服务器之间预先配置的保护SIP信令中敏感信息的安全密钥或证书,本发明实施例对该情况不作具体限定。
可选的,如图7所示,另一种可能的实现方式中,在第一UE发起群组会话时,MCPTT服务器获取该群组会话对应群组的组标识、该群组会话的GSK和GSK ID(步骤S301),具体可以包括:
S301b1、在第一UE发起群组会话时,MCPTT服务器接收第一UE发送的群组会话请求,该群组会话请求携带该群组会话对应群组的组标识。
S301b2、MCPTT服务器生成该群组会话的GSK和GSK ID。
进而,MCPTT服务器向该关联UE中的至少一个UE分别发送GSK和GSK ID(步骤S303),具体可以包括:
S303b、MCPTT服务器向该关联UE中的每个UE分别发送GSK和GSK ID。
其中,在该实现方式中,可以通过如下三种方式对该群组会话的GSK和GSK ID进行安全保护:
一种可能的实现方式中,步骤S301b1中的群组会话请求还携带该群组会话的GMK ID。
进而,在MCPTT服务器向该关联UE中的每个UE分别发送GSK和GSK ID(步骤S303b)之前,还可以包括:
MCPTT服务器根据该GMK ID,查找该GMK ID对应的GMK。
MCPTT服务器向关联UE中的每个UE分别发送GSK和GSK ID(步骤S303b),具体可以包括:
MCPTT服务器将GSK和GSK ID封装在Mikey消息中,其中,该Mikey消息采用GMK进行安全保护;
MCPTT服务器向关联UE中的每个UE分别发送该Mikey消息。
具体的,Mikey消息采用GMK进行安全保护的相关说明可参考图4所示的实施例,本发明实施例在此不再赘述。
下面将以第一UE为图2中的UE1,该群组会话对应群组内的关联UE包括UE1、UE2和UE3为例,通过MCPTT服务器与该群组会话对应群组内的关联UE交互的方式,对该实现方式进行展开说明。如图8所示,本发明实施例提供的密钥的生成及下发方法包括步骤S801-S809:
S801、UE1、UE2和UE3分别注册到MCPTT服务器并同属于一个群组会话对应的群组。
S802、UE1、UE2、UE3和MCPTT服务器都预先配置了GMK和GMK ID。
S803、UE1发起群组会话。
S804、UE1向MCPTT服务器发送群组会话请求,该群组会话请求携带该群组会话对应群组的组标识和GMK ID。
S805、MCPTT服务器接收该群组会话请求,并根据该组标识,获取该群组内的关联UE;以及,MCPTT服务器生成该群组会话的GSK和GSK ID;以及,MCPTT服务器根据该GMK ID,查找该GMK ID对应的GMK之后,将GSK和GSK ID封装在Mikey消息中,其中,该Mikey消息采用该GMK ID对应的GMK进行安全保护。
S806、MCPTT服务器向该关联UE中的每个UE分别发送GSK和GSK ID。
由于该实施例以该群组会话对应群组内的关联UE包括UE1、UE2和UE3为例进行说明,因此,此时,该群组内的关联UE包括UE1、UE2和UE3。进而,步骤S806具体包括步骤S806a、S806b和S806c:
S806a、MCPTT服务器向UE2发送群组会话请求,该群组会话请求携带该群组会话对应群组的组标识和Mikey消息。
S806b、MCPTT服务器向UE3发送群组会话请求,该群组会
话请求携带该群组会话对应群组的组标识和Mikey消息。
S807a、UE2解析Mikey消息获取GSK和GSK ID。
S807b、UE3解析Mikey消息获取GSK和GSK ID。
S808a、UE2向MCPTT服务器回复确认消息。
S808b、UE3向MCPTT服务器回复确认消息。
S806c、MCPTT服务器向UE1回复确认消息,该确认消息携带该群组会话对应群组的组标识和Mikey消息。
S807c、UE1解析Mikey消息获取GSK和GSK ID
S809、当进行群组会话通信时,UE1、UE2和UE3用该GSK和GSK ID以及其它参数来生成SRTP/SRTCP的密钥。
需要说明的是,步骤S806a、S806b和S806c中之所以携带该群组会话对应群组的组标识,是为了通知接收端其被邀请加入该组标识所对应的群组会话。
需要说明的是,图8所示的实施例中的Mikey消息中还携带了GMK ID,这是为了让接收端根据GMK ID查找对应的GMK,进而根据GMK推演的安全参数来验证和解密获取GSK和GSK ID。
由步骤S801-S809可以看出,本发明实施例提供的密钥的生成及下发方法中,由MCPTT服务器生成该群组会话的GSK和GSK ID,并且GMS为组成员分配GMK,由Mikey消息保护GSK的下发。
另一种可能的实现方式中,MCPTT服务器向关联UE中的每个UE分别发送GSK和GSK ID(步骤S303b),具体可以包括:
对于该关联UE中的每个UE,MCPTT服务器均按照下面针对第二UE的操作进行处理:
MCPTT服务器将GSK和GSK ID封装在S/MIME消息中,其中,该S/MIME消息采用预先配置的MCPTT服务器和第二UE之间的安全密钥进行安全保护;
MCPTT服务器向第二UE发送该S/MIME消息。
下面将以第一UE为图2中的UE1,该群组会话对应群组内的
关联UE包括UE1、UE2和UE3为例,通过MCPTT服务器与该群组会话对应群组内的关联UE交互的方式,对该实现方式进行展开说明。如图9所示,本发明实施例提供的密钥的生成及下发方法包括步骤S901-S910:
S901、UE1、UE2和UE3分别注册到MCPTT服务器并同属于一个群组会话对应的群组。
S902、UE1、UE2、UE3和MCPTT服务器都预先配置了保护SIP信令中敏感信息的安全密钥或证书。
S903、UE1发起群组会话。
S904、UE1向MCPTT服务器发送群组会话请求,该群组会话请求携带该群组会话对应群组的组标识。
S905、MCPTT服务器接收该群组会话请求,并根据该组标识,获取该群组内的关联UE;以及,MCPTT服务器生成该群组会话的GSK和GSK ID。
对于关联UE中的每个UE,MCPTT服务器均按照下面针对第二UE的操作(包括步骤S906和S907)进行处理:
S906、MCPTT服务器将GSK和GSK ID封装在S/MIME消息中,其中,该S/MIME消息采用预先配置的MCPTT服务器和第二UE之间的安全密钥进行安全保护。
S907、MCPTT服务器向第二UE发送该S/MIME消息。
由于该实施例以该群组会话对应群组内的关联UE包括UE1、UE2和UE3为例进行说明,因此,此时,该群组内的关联UE包括UE1、UE2和UE3。进而,步骤S906具体包括步骤S906a、S906b和S906c,步骤S907具体包括步骤S907a、S907b和S907c:
S906a、MCPTT服务器将GSK和GSK ID封装在S/MIME消息2中。
其中,该S/MIME消息2采用预先配置的MCPTT服务器和UE2之间的安全密钥进行安全保护。
S907a、MCPTT服务器向UE2发送群组会话请求,该群组会
话请求携带该群组会话对应群组的组标识和S/MIME消息2。
S906b、MCPTT服务器将GSK和GSK ID封装在S/MIME消息3中。
其中,该S/MIME消息3采用预先配置的MCPTT服务器和UE3之间的安全密钥进行安全保护。
S907b、MCPTT服务器向UE3发送群组会话请求,该群组会话请求携带该群组会话对应群组的组标识和S/MIME消息3。
需要说明的是,步骤S907a和S907b中之所以携带该群组会话对应群组的组标识,是为了通知接收端其被邀请加入该组标识所对应的群组会话。
S908a、UE2解析S/MIME消息2获取GSK和GSK ID。
S908b、UE3解析S/MIME消息3获取GSK和GSK ID。
S909a、UE2向MCPTT服务器回复确认消息。
S909b、UE3向MCPTT服务器回复确认消息。
S906c、MCPTT服务器将GSK和GSK ID封装在S/MIME消息1中。
S907c、MCPTT服务器向UE1回复确认消息,该确认消息携带S/MIME消息1。
S908c、UE1解析S/MIME消息1获取GSK和GSK ID。
S910、当进行群组会话通信时,UE1、UE2和UE3用该GSK和GSK ID以及其它参数来生成SRTP/SRTCP的密钥。
由步骤S901-S910可以看出,本发明实施例提供的密钥的生成及下发方法中,由MCPTT服务器生成该群组会话的GSK和GSK ID,并且GMS不为组成员分配GMK,而是MCPTT服务器和每个UE之间配置了保护SIP信令中敏感信息的安全密钥或证书,通过SIP信令中的S/MIME消息来保护GSK的下发。
可选的,图9所示的实施例中,GSK和GSK ID也可以作为安全信息,单独由Mikey消息封装并安全保护,使用的是UE和MCPTT服务器之间预先配置的保护SIP信令中敏感信息的安全密
钥或证书,本发明实施例对该情况不作具体限定。
再一种可能的实现方式中,MCPTT服务器向关联UE中的每个UE分别发送GSK和GSK ID(步骤S303b),具体可以包括:
对于关联UE中的每个UE,MCPTT服务器均按照下面针对第二UE的操作进行处理:
MCPTT服务器将GSK和GSK ID封装在超文本传输协议(英文全称:hyper text transfer protocol,英文缩写:HTTP)消息中;
MCPTT服务器通过预先建立的MCPTT服务器和第二UE之间安全传输层协议(英文全称:transport layer security,英文缩写:TLS)安全通道向第二UE发送HTTP消息。
下面将以第一UE为图2中的UE1,该群组会话对应群组内的关联UE包括UE1、UE2和UE3为例,通过MCPTT服务器与该群组会话对应群组内的关联UE交互的方式,对该实现方式进行展开说明。如图10所示,本发明实施例提供的密钥的生成及下发方法包括步骤S1001-S1012:
S1001、UE1、UE2和UE3分别注册到MCPTT服务器并同属于一个群组会话对应的群组。
S1002、UE1、UE2、UE3和MCPTT服务器都预先建立好了TLS安全通道。
S1003、UE1发起群组会话。
S1004、UE1向MCPTT服务器发送群组会话请求,该群组会话请求携带该群组会话对应群组的组标识。
S1005、MCPTT服务器接收该群组会话请求,并根据该组标识,获取该群组内的关联UE;以及,MCPTT服务器生成该群组会话的GSK和GSK ID。
对于关联UE中的每个UE,MCPTT服务器均按照下面针对第二UE的操作(包括步骤S1006和S1007)进行处理:
S1006、MCPTT服务器将GSK和GSK ID封装在HTTP消息中。
S1007、MCPTT服务器通过预先建立的MCPTT服务器和第二UE之间TLS安全通道向第二UE发送HTTP消息。
由于该实施例以该群组会话对应群组内的关联UE包括UE1、UE2和UE3为例进行说明,因此,此时,该群组内的关联UE包括UE1、UE2和UE3。进而,步骤S1007具体包括步骤S1007a、S1007b和S1007c:
S1007a、MCPTT服务器通过预先建立的MCPTT服务器和UE2之间TLS安全通道2向UE2发送HTTP消息。
S1007b、MCPTT服务器通过预先建立的MCPTT服务器和UE3之间TLS安全通道3向UE3发送HTTP消息。
S1007c、MCPTT服务器通过预先建立的MCPTT服务器和UE1之间TLS安全通道1向UE1发送HTTP消息。
S1008a、UE2解析HTTP消息获取GSK和GSK ID。
S1008b、UE3解析HTTP消息获取GSK和GSK ID。
S1008c、UE1解析HTTP消息获取GSK和GSK ID。
S1009a、MCPTT服务器向UE2发送群组会话请求,该群组会话请求携带该群组会话对应群组的组标识。
S1009b、MCPTT服务器向UE3发送群组会话请求,该群组会话请求携带该群组会话对应群组的组标识。
S1010a、UE2向MCPTT服务器回复确认消息。
S1010b、UE3向MCPTT服务器回复确认消息。
S1011、MCPTT服务器向UE1回复确认消息。
S1012、当进行群组会话通信时,UE1、UE2和UE3用该GSK和GSK ID以及其它参数来生成SRTP/SRTCP的密钥。
需要说明的是,步骤S1009a和S1009b中之所以携带该群组会话对应群组的组标识,是为了通知接收端其被邀请加入该组标识所对应的群组会话。
需要说明的是,图10所示的实施例中的HTTP消息中还携带了该群组会话对应群组的组标识,这是为了通知接收端该GSK和
GSK ID用于该组标识所对应的群组会话。
由步骤S1001-S1012可以看出,本发明实施例提供的密钥的生成及下发方法中,由MCPTT服务器生成该群组会话的GSK和GSK标识ID,并且GMS不为组成员分配GMK,而是MCPTT服务器通过HTTP消息下发GSK,由MCPTT服务器和每个UE之间建立的TLS安全通道来保护GSK的下发。
综上,由图5、图6、图8、图9和图10这五个具体实施例可以看出,本发明实施例提供的密钥的生成及下发方法中,每次群组会话,都有一个新鲜独立的GSK。这样,不仅为MCPTT UE之间的群组会话提供了端到端的安全保护;同时,一方面,由于该GSK新鲜性高较高,从而若根据该GSK生成SRTP/SRTCP密钥,可以避免现有技术中每次群组会话的SRTP/SRTCP密钥都一样,若群组会话频繁发起,将导致SRTP/SRTCP密钥过于频繁地被使用,从而导致被攻破的可能性增加问题,提升生成SRTP/SRTCP密钥的安全等级;另一方面,由于该GSK属于一次群组会话的密钥,可以做到不同群组会话之间的安全隔离,从而若根据GSK生成SRTP/SRTCP密钥,可以避免现有技术中每次群组会话的SRTP/SRTCP密钥都一样,如果SRTP/SRTCP密钥被攻破,则后续的群组会话的密钥都会泄露的问题,提升生成SRTP/SRTCP密钥的安全等级。综上,基于本发明实施例提供的密钥的生成及下发方法,可以解决目前MCPTT群组会话成员直接使用GMS分发的GMK,结合rand、CSB-ID和CS-ID来生成SRTP/SRTCP密钥会降低安全等级的问题,不仅为MCPTT UE之间的群组会话提供了端到端的安全保护;同时,还保证了每次群组会话都使用新的安全密钥,提高了安全等级。
需要说明的是,本发明上述各实施例均是针对的存在群组会话发起过程的场景。另外,对于无群组会话发起过程的场景(比如预配置群组会话,然后由话权控制(英文:floor control)来激活该群组会话),也可以由MCPTT服务器或者群组会话中的某一个UE
生成GSK和GSK ID,进而通过Mikey消息来保护GSK的下发。这种场景携带GSK的Mikey消息可以嵌入到实时传输协议(英文全称:Real-time Transport Protocol,英文缩写:RTP)控制协议(英文全称:RTP Control Protocol,英文缩写:RTCP))消息中(比如:floor request,floor granted,floor taken),这几条消息本身可以用GSK衍生的SRTCP密钥来进行安全保护(完全保护和/或加密)。但是,如果有加密,Mikey消息部分不能被加密,而是由GMK推导的Mikey密钥来进行保护,以便接收端解密得到GSK。本发明实施例在此对该无群组会话发起过程的场景不再作具体阐述。
如图11所示,本发明实施例提供一种MCPTT服务器110,该MCPTT服务器110用于执行以上图3-图10所示的密钥的生成及下发方法中MCPTT服务器所执行的步骤。该MCPTT服务器110可以包括相应步骤所对应的单元。示例性的,可以包括:处理单元1101和发送单元1102。
其中,处理单元1101,用于在第一UE发起群组会话时,获取该群组会话对应群组的组标识、该群组会话的GSK和GSK ID。
处理单元1101,还用于根据该组标识,获取该群组内的关联UE。
发送单元1102,用于向该关联UE中的至少一个UE分别发送GSK和GSK ID。
具体的,本发明实施例中,处理单元1101可以通过多种方式获取该群组会话对应群组的组标识、该群组会话的GSK和GSK ID,下面将示例性的提供两种可能的实现。
可选的,如图12所示,MCPTT服务器110还包括:接收单元1103。
处理单元1101具体用于:
通过接收单元1103接收第一UE发送的群组会话请求,该群组会话请求携带该群组会话对应群组的组标识、第一UE生成的该群组会话的GSK和GSK ID。
发送单元1102具体用于:
向该关联UE中除第一UE之外的每个UE分别发送GSK和GSK ID。
其中,在该实现方式中,可以通过如下两种方式对该群组会话的GSK和GSK ID进行安全保护:
一种可能的实现方式中,GSK和GSK ID被封装在Mikey消息中,其中,该Mikey消息用预先配置的GMK进行安全保护;
发送单元1102具体用于:
向该关联UE中除第一UE之外的每个UE分别发送该Mikey消息。
另一种可能的实现方式中,第一UE生成的该群组会话的GSK和GSK ID被封装在第一S/MIME消息中,其中,该第一S/MIME消息采用预先配置的MCPTT服务器110和第一UE之间的安全密钥进行安全保护。
处理单元1101,还用于在通过接收单元1103接收第一UE发送的群组会话请求之后,解析第一S/MIME消息,获得GSK和所述GSK ID。
发送单元1102具体用于:
对于该关联UE中除第一UE之外的每个UE,均按照下面针对第二UE的操作进行处理:
将GSK和GSK ID封装在第二S/MIME消息中,其中,该第二S/MIME消息采用预先配置的MCPTT服务器110和第二UE之间的安全密钥进行安全保护。
向第二UE发送第二S/MIME消息。
或者,可选的,如图12所示,MCPTT服务器110还包括:接收单元1103。
处理单元1101具体用于:
通过接收单元1103接收第一UE发送的群组会话请求,该群组会话请求携带群组会话对应群组的组标识;以及生成该群组会
话的GSK和GSK ID。
发送单元1102具体用于:
向该关联UE中的每个UE分别发送GSK和GSK ID。
其中,在该实现方式中,可以通过如下两种方式对该群组会话的GSK和GSK ID进行安全保护:
一种可能的实现方式中,该群组会话请求还携带该群组会话的GMK ID。
处理单元1101,还用于在发送单元1102向该关联UE中的每个UE分别发送GSK和GSK ID之前,根据该GMK ID,查找GMK ID对应的GMK。
发送单元1102具体用于:
将GSK和GSK ID封装在Mikey消息中,其中,该Mikey消息采用该GMK进行安全保护。
向该关联UE中的每个UE分别发送该Mikey消息。
另一种可能的实现方式中,发送单元1102具体用于:
对于该关联UE中的每个UE,均按照下面针对第二UE的操作进行处理:
将GSK和GSK ID封装在S/MIME消息中,其中,S/MIME消息采用预先配置的MCPTT服务器110和第二UE之间的安全密钥进行安全保护。
向第二UE发送该S/MIME消息。
再一种可能的实现方式中,发送单元1102具体用于:
对于该关联UE中的每个UE,均按照下面针对第二UE的操作进行处理:
将GSK和所述GSK ID封装在HTTP消息中。
通过预先建立的MCPTT服务器110和第二UE之间TLS安全通道向第二UE发送该HTTP消息。
可以理解,本发明实施例的MCPTT服务器110可对应于上述图3-图10所示的密钥的生成及下发方法中MCPTT服务器,并且本
发明实施例的MCPTT服务器110中的各个单元的划分和/或功能等均是为了实现上述图3-图10所示的密钥的生成及下发方法流程,为了简洁,在此不再赘述。
由于本发明实施例中的MCPTT服务器110可以用于执行上述方法流程,因此,其所能获得的技术效果也可参考上述方法实施例,本发明实施例在此不再赘述。
如图13所示,本发明实施例还提供一种MCPTT服务器130,包括:处理器1301、存储器1302、总线1303和通信接口1304。
其中,存储器1302用于存储计算机执行指令,处理器1301与存储器1302通过总线1303连接,当MCPTT服务器130运行时,处理器1301执行存储器1302存储的计算机执行指令,以使MCPTT服务器130执行上述图3-图10所示的密钥的生成及下发方法中MCPTT服务器所执行的步骤。
具体的,本发明实施例中的处理器1301可以是一个中央处理器(英文全称:central processing unit,英文缩写:CPU),还可以为其他通用处理器、数字信号处理器(英文全称:digital signal processing,英文缩写:DSP)、专用集成电路(英文全称:application specific integrated circuit,英文缩写:ASIC)、现场可编程门阵列(英文全称:field-programmable gate array,英文缩写:FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。另外,该处理器还可以为专用处理器,该专用处理器可以包括基带处理芯片、射频处理芯片等中的至少一个。进一步地,该专用处理器还可以包括具有MCPTT服务器130其他专用处理功能的芯片。
存储器1302可以包括易失性存储器(英文:volatile memory),例如随机存取存储器(英文全称:random-access memory,英文缩写:RAM);存储器1302也可以包括非易失性存储器(英文:non-volatile memory),例如只读存储器(英文全称:
read-only memory,英文缩写:ROM),快闪存储器(英文:flash memory),硬盘(英文全称:hard disk drive,英文缩写:HDD)或固态硬盘(英文全称:solid-state drive,英文缩写:SSD);另外,存储器1302还可以包括上述种类的存储器的组合。
总线1303可以包括数据总线、电源总线、控制总线和信号状态总线等。本实施例中为了清楚说明,在图13中将各种总线都示意为总线1303。
通信接口1304具体可以是MCPTT服务器130上的收发器。该收发器可以为无线收发器。例如,无线收发器可以是MCPTT服务器130的天线等。处理器1301通过通信接口1304与其他设备,例如UE之间进行数据的收发。
在具体实现过程中,上述如图3-图10所示的方法流程中MCPTT服务器所执行的各步骤均可以通过硬件形式的处理器1301执行存储器1302中存储的软件形式的计算机执行指令实现。为避免重复,此处不再赘述。
由于本发明实施例提供的MCPTT服务器130可用于执行上述方法流程,因此其所能获得的技术效果可参考上述方法实施例,此处不再赘述。
可选的,本实施例还提供一种可读介质,包括计算机执行指令,当MCPTT服务器的处理器执行该计算机执行指令时,该MCPTT服务器可以执行上述如图3-图10所示的密钥的生成及下发方法流程中MCPTT服务器所执行的各步骤。具体的密钥的生成及下发方法可参见上述如图3-图10所示的实施例中的相关描述,此处不再赘述。
所属领域的技术人员可以清楚地了解到,为描述的方便和简洁,上述描述的装置,仅以上述各功能模块的划分进行举例说明,实际应用中,可以根据需要而将上述功能分配由不同的功能模块完成,即将装置的内部结构划分成不同的功能模块,以完成以上描述的全部或者部分功能。上述描述的系统、装置和单元的
具体工作过程,可以参考前述方法实施例中的对应过程,在此不再赘述。
在本申请所提供的几个实施例中,应该理解到,所揭露的系统,装置和方法,可以通过其它的方式实现。例如,以上所描述的装置实施例仅仅是示意性的,例如,所述模块或单元的划分,仅仅为一种逻辑功能划分,实际实现时可以有另外的划分方式,例如多个单元或组件可以结合或者可以集成到另一个系统,或一些特征可以忽略,或不执行。另一点,所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口,装置或单元的间接耦合或通信连接,可以是电性,机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的,作为单元显示的部件可以是或者也可以不是物理单元,即可以位于一个地方,或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外,在本发明各个实施例中的各功能单元可以集成在一个处理单元中,也可以是各个单元单独物理存在,也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现,也可以采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时,可以存储在一个计算机可读取存储介质中。基于这样的理解,本发明的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来,该计算机软件产品存储在一个存储介质中,包括若干指令用以使得一台计算机设备(可以是个人计算机,服务器,或者网络设备等)或处理器(processor)执行本发明各个实施例所述方法的全部或部分步骤。而前述的存储介质包括:U盘、移动硬盘、只读存储器(ROM,Read-Only Memory)、随机存取存储器(RAM,Random Access Memory)、磁碟或者光盘等各种可以存
储程序代码的介质。
以上所述,仅为本发明的具体实施方式,但本发明的保护范围并不局限于此,任何熟悉本技术领域的技术人员在本发明揭露的技术范围内,可轻易想到变化或替换,都应涵盖在本发明的保护范围之内。因此,本发明的保护范围应以所述权利要求的保护范围为准。
Claims (18)
- 一种密钥的生成及下发方法,其特征在于,所述方法包括:在第一用户设备UE发起群组会话时,紧急任务即按即说MCPTT服务器获取所述群组会话对应群组的组标识、所述群组会话的组会话密钥GSK和GSK标识ID;所述MCPTT服务器根据所述组标识,获取所述群组内的关联UE,并向所述关联UE中的至少一个UE分别发送所述GSK和所述GSK ID。
- 根据权利要求1所述的方法,其特征在于,所述MCPTT服务器获取所述群组会话对应群组的组标识、所述群组会话的GSK和GSK ID,包括:所述MCPTT服务器接收所述第一UE发送的群组会话请求,所述群组会话请求携带所述群组会话对应群组的组标识、所述第一UE生成的所述群组会话的GSK和GSK ID;所述MCPTT服务器向所述关联UE中的至少一个UE分别发送所述GSK和所述GSK ID,包括:所述MCPTT服务器向所述关联UE中除所述第一UE之外的每个UE分别发送所述GSK和所述GSK ID。
- 根据权利要求2所述的方法,其特征在于,所述GSK和所述GSK ID被封装在Mikey消息中,其中,所述Mikey消息用预先配置的组密钥GMK进行安全保护;所述MCPTT服务器向所述关联UE中除所述第一UE之外的每个UE分别发送所述GSK和所述GSK ID,包括:所述MCPTT服务器向所述关联UE中除所述第一UE之外的每个UE分别发送所述Mikey消息。
- 根据权利要求2所述的方法,其特征在于,所述第一UE生成的所述群组会话的GSK和GSK ID被封装在第一S/MIME消息中,其中,所述第一S/MIME消息采用预先配置的所述MCPTT服务器和所述第一UE之间的安全密钥进行安全保护;在所述MCPTT服务器接收所述第一UE发送的群组会话请求之后,还包括:所述MCPTT服务器解析所述第一S/MIME消息,获得所述GSK和所述GSK ID;所述MCPTT服务器向所述关联UE中除所述第一UE之外的每个UE分别发送所述GSK和所述GSK ID,包括:对于所述关联UE中除所述第一UE之外的每个UE,所述MCPTT服务器均按照下面针对第二UE的操作进行处理:所述MCPTT服务器将所述GSK和所述GSK ID封装在第二S/MIME消息中,其中,所述第二S/MIME消息采用预先配置的所述MCPTT服务器和所述第二UE之间的安全密钥进行安全保护;所述MCPTT服务器向所述第二UE发送所述第二S/MIME消息。
- 根据权利要求1所述的方法,其特征在于,所述MCPTT服务器获取所述群组会话对应群组的组标识、所述群组会话的GSK和GSK ID,包括:所述MCPTT服务器接收所述第一UE发送的群组会话请求,所述群组会话请求携带所述群组会话对应群组的组标识;以及所述MCPTT服务器生成所述群组会话的GSK和GSK ID;所述MCPTT服务器向所述关联UE中的至少一个UE分别发送所述GSK和所述GSK ID,包括:所述MCPTT服务器向所述关联UE中的每个UE分别发送所述GSK和所述GSK ID。
- 根据权利要求5所述的方法,其特征在于,所述群组会话请求还携带所述群组会话的组密钥标识GMK ID;在所述MCPTT服务器向所述关联UE中的每个UE分别发送所述GSK和所述GSK ID之前,还包括:所述MCPTT服务器根据所述GMK ID,查找所述GMK ID对应的GMK;所述MCPTT服务器向所述关联UE中的每个UE分别发送所述GSK和所述GSK ID,包括:所述MCPTT服务器将所述GSK和所述GSK ID封装在Mikey消息中,其中,所述Mikey消息采用所述GMK进行安全保护;所述MCPTT服务器向所述关联UE中的每个UE分别发送所述Mikey消息。
- 根据权利要求5所述的方法,其特征在于,所述MCPTT服务器向所述关联UE中的每个UE分别发送所述GSK和所述GSK ID,包括:对于所述关联UE中的每个UE,所述MCPTT服务器均按照下面针对第二UE的操作进行处理:所述MCPTT服务器将所述GSK和所述GSK ID封装在S/MIME消息中,其中,所述S/MIME消息采用预先配置的所述MCPTT服务器和所述第二UE之间的安全密钥进行安全保护;所述MCPTT服务器向所述第二UE发送所述S/MIME消息。
- 根据权利要求5所述的方法,其特征在于,所述MCPTT服务器向所述关联UE中的每个UE分别发送所述GSK和所述GSK ID,包括:对于所述关联UE中的每个UE,所述MCPTT服务器均按照下面针对第二UE的操作进行处理:所述MCPTT服务器将所述GSK和所述GSK ID封装在超文本传输协议HTTP消息中;所述MCPTT服务器通过预先建立的所述MCPTT服务器和所述第二UE之间安全传输层协议TLS安全通道向所述第二UE发送所述HTTP消息。
- 一种紧急任务即按即说MCPTT服务器,其特征在于,所述MCPTT服务器包括:处理单元和发送单元;所述处理单元,用于在第一用户设备UE发起群组会话时,获取所述群组会话对应群组的组标识、所述群组会话的组会话密钥GSK 和GSK标识ID;所述处理单元,还用于根据所述组标识,获取所述群组内的关联UE;所述发送单元,用于向所述关联UE中的至少一个UE分别发送所述GSK和所述GSK ID。
- 根据权利要求9所述的MCPTT服务器,其特征在于,所述MCPTT服务器还包括:接收单元;所述处理单元具体用于:通过所述接收单元接收所述第一UE发送的群组会话请求,所述群组会话请求携带所述群组会话对应群组的组标识、所述第一UE生成的所述群组会话的GSK和GSK ID;所述发送单元具体用于:向所述关联UE中除所述第一UE之外的每个UE分别发送所述GSK和所述GSK ID。
- 根据权利要求10所述的MCPTT服务器,其特征在于,所述GSK和所述GSK ID被封装在Mikey消息中,其中,所述Mikey消息用预先配置的组密钥GMK进行安全保护;所述发送单元具体用于:向所述关联UE中除所述第一UE之外的每个UE分别发送所述Mikey消息。
- 根据权利要求10所述的MCPTT服务器,其特征在于,所述第一UE生成的所述群组会话的GSK和GSK ID被封装在第一S/MIME消息中,其中,所述第一S/MIME消息采用预先配置的所述MCPTT服务器和所述第一UE之间的安全密钥进行安全保护;所述处理单元,还用于在通过所述接收单元接收所述第一UE发送的群组会话请求之后,解析所述第一S/MIME消息,获得所述GSK和所述GSK ID;所述发送单元具体用于:对于所述关联UE中除所述第一UE之外的每个UE,均按照下 面针对第二UE的操作进行处理:将所述GSK和所述GSK ID封装在第二S/MIME消息中,其中,所述第二S/MIME消息采用预先配置的所述MCPTT服务器和所述第二UE之间的安全密钥进行安全保护;向所述第二UE发送所述第二S/MIME消息。
- 根据权利要求9所述的MCPTT服务器,其特征在于,所述MCPTT服务器还包括:接收单元;所述处理单元具体用于:通过所述接收单元接收所述第一UE发送的群组会话请求,所述群组会话请求携带所述群组会话对应群组的组标识;以及生成所述群组会话的GSK和GSK ID;所述发送单元具体用于:向所述关联UE中的每个UE分别发送所述GSK和所述GSKID。
- 根据权利要求13所述的MCPTT服务器,其特征在于,所述群组会话请求还携带所述群组会话的组密钥标识GMK ID;所述处理单元,还用于在所述发送单元向所述关联UE中的每个UE分别发送所述GSK和所述GSK ID之前,根据所述GMK ID,查找所述GMK ID对应的GMK;所述发送单元具体用于:将所述GSK和所述GSK ID封装在Mikey消息中,其中,所述Mikey消息采用所述GMK进行安全保护;向所述关联UE中的每个UE分别发送所述Mikey消息。
- 根据权利要求13所述的MCPTT服务器,其特征在于,所述发送单元具体用于:对于所述关联UE中的每个UE,均按照下面针对第二UE的操作进行处理:将所述GSK和所述GSK ID封装在S/MIME消息中,其中,所述S/MIME消息采用预先配置的所述MCPTT服务器和所述第二UE 之间的安全密钥进行安全保护;向所述第二UE发送所述S/MIME消息。
- 根据权利要求13所述的MCPTT服务器,其特征在于,所述发送单元具体用于:对于所述关联UE中的每个UE,均按照下面针对第二UE的操作进行处理:将所述GSK和所述GSK ID封装在超文本传输协议HTTP消息中;通过预先建立的所述MCPTT服务器和所述第二UE之间安全传输层协议TLS安全通道向所述第二UE发送所述HTTP消息。
- 一种紧急任务即按即说MCPTT服务器,其特征在于,所述MCPTT服务器包括:处理器、存储器、总线和通信接口;所述存储器用于存储计算机执行指令,所述处理器与所述存储器通过所述总线连接,当所述MCPTT服务器运行时,所述处理器执行所述存储器存储的所述计算机执行指令,以使所述MCPTT服务器执行如权利要求1-8任一项所述的密钥的生成及下发方法。
- 一种密钥的生成及下发系统,其特征在于,所述系统包括如权利要求9-16任一项所述的紧急任务即按即说MCPTT服务器、以及与所述MCPTT服务器连接的多个用户设备UE;或者,所述系统包括如权利要求17所述的MCPTT服务器、以及与所述MCPTT服务器连接的多个UE。
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/CN2016/071707 WO2017124425A1 (zh) | 2016-01-22 | 2016-01-22 | 密钥的生成及下发方法、相关设备及系统 |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/CN2016/071707 WO2017124425A1 (zh) | 2016-01-22 | 2016-01-22 | 密钥的生成及下发方法、相关设备及系统 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2017124425A1 true WO2017124425A1 (zh) | 2017-07-27 |
Family
ID=59361327
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2016/071707 WO2017124425A1 (zh) | 2016-01-22 | 2016-01-22 | 密钥的生成及下发方法、相关设备及系统 |
Country Status (1)
Country | Link |
---|---|
WO (1) | WO2017124425A1 (zh) |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN113498030A (zh) * | 2020-04-02 | 2021-10-12 | 海能达通信股份有限公司 | 一种支持mcptt匿名回呼的系统和方法 |
WO2022237421A1 (zh) * | 2021-05-10 | 2022-11-17 | 大唐移动通信设备有限公司 | 临时组的密钥传输方法、装置、终端及网络侧设备 |
EP4243461A1 (fr) * | 2022-03-08 | 2023-09-13 | Airbus DS SLC | Procédé de gestion de chiffrement par une entité émettrice dans un réseau 3gpp mcs |
EP4243470A1 (fr) * | 2022-03-08 | 2023-09-13 | Airbus DS SLC | Procédé de gestion d'identité par une entité émettrice dans un réseau 3gpp mcs |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1421080A (zh) * | 1999-12-10 | 2003-05-28 | 皇家菲利浦电子有限公司 | 会话密钥的同步 |
CN101431414A (zh) * | 2008-12-15 | 2009-05-13 | 西安电子科技大学 | 基于身份的认证群组密钥管理方法 |
CN101895878A (zh) * | 2010-07-02 | 2010-11-24 | 武汉大学 | 基于动态密码配置的移动通信方法及系统 |
CN102379134A (zh) * | 2009-04-03 | 2012-03-14 | 高通股份有限公司 | 保护与无线通信系统内的多播通信会话相关联的消息 |
CN103051457A (zh) * | 2012-12-25 | 2013-04-17 | 桂林电子科技大学 | 一种网络群组安全通信的建立方法 |
-
2016
- 2016-01-22 WO PCT/CN2016/071707 patent/WO2017124425A1/zh active Application Filing
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1421080A (zh) * | 1999-12-10 | 2003-05-28 | 皇家菲利浦电子有限公司 | 会话密钥的同步 |
CN101431414A (zh) * | 2008-12-15 | 2009-05-13 | 西安电子科技大学 | 基于身份的认证群组密钥管理方法 |
CN102379134A (zh) * | 2009-04-03 | 2012-03-14 | 高通股份有限公司 | 保护与无线通信系统内的多播通信会话相关联的消息 |
CN101895878A (zh) * | 2010-07-02 | 2010-11-24 | 武汉大学 | 基于动态密码配置的移动通信方法及系统 |
CN103051457A (zh) * | 2012-12-25 | 2013-04-17 | 桂林电子科技大学 | 一种网络群组安全通信的建立方法 |
Cited By (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN113498030A (zh) * | 2020-04-02 | 2021-10-12 | 海能达通信股份有限公司 | 一种支持mcptt匿名回呼的系统和方法 |
WO2022237421A1 (zh) * | 2021-05-10 | 2022-11-17 | 大唐移动通信设备有限公司 | 临时组的密钥传输方法、装置、终端及网络侧设备 |
EP4243461A1 (fr) * | 2022-03-08 | 2023-09-13 | Airbus DS SLC | Procédé de gestion de chiffrement par une entité émettrice dans un réseau 3gpp mcs |
EP4243470A1 (fr) * | 2022-03-08 | 2023-09-13 | Airbus DS SLC | Procédé de gestion d'identité par une entité émettrice dans un réseau 3gpp mcs |
FR3133512A1 (fr) * | 2022-03-08 | 2023-09-15 | Airbus Ds Slc | Procédé de gestion d’identité par une entité émettrice dans un réseau 3GPP MCS |
FR3133511A1 (fr) * | 2022-03-08 | 2023-09-15 | Airbus Ds Slc | Procédé de gestion de chiffrement par une entité émettrice dans un réseau 3GPP MCS |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20210289351A1 (en) | Methods and systems for privacy protection of 5g slice identifier | |
KR101915373B1 (ko) | 크리티컬 통신 서비스와 연관된 크리티컬 통신 콘텐츠를 안전하게 수신하기 위한 기술 | |
CN109548017B (zh) | 一种密钥交互方法及装置 | |
EP2903322B1 (en) | Security management method and apparatus for group communication in mobile communication system | |
WO2017114123A1 (zh) | 一种密钥配置方法及密钥管理中心、网元 | |
KR20170128230A (ko) | 디바이스 간 디스커버리 및 통신을 보장하기 위한 시스템, 방법 및 장치 | |
WO2020248624A1 (zh) | 一种通信方法、网络设备、用户设备和接入网设备 | |
EP3535998B1 (en) | Mission-critical push-to-talk | |
WO2019034014A1 (zh) | 接入认证的方法和装置 | |
CN109952777B (zh) | 对关键任务即按即说多媒体广播和多播服务子信道控制消息的保护 | |
KR20230054421A (ko) | 셀룰러 슬라이싱된 네트워크들에서의 중계기 선택의 프라이버시 | |
WO2017133021A1 (zh) | 一种安全处理方法及相关设备 | |
WO2018219181A1 (zh) | 确定终端设备的标识的方法和装置 | |
WO2017124425A1 (zh) | 密钥的生成及下发方法、相关设备及系统 | |
US11275852B2 (en) | Security procedure | |
US11770247B2 (en) | Method for providing end-to-end security over signaling plane in mission critical data communication system | |
EP3183839B1 (en) | Group communication service enabler security | |
WO2022134089A1 (zh) | 一种安全上下文生成方法、装置及计算机可读存储介质 | |
WO2024041498A1 (zh) | 一种保密通信处理方法、第一终端及存储介质 | |
EP4184860A1 (en) | Key management method and communication apparatus | |
WO2018049689A1 (zh) | 密钥协商方法及装置 | |
WO2022174802A1 (zh) | 密钥更新的方法和装置 | |
WO2016176902A1 (zh) | 一种终端认证方法、管理终端及申请终端 | |
US11632235B2 (en) | Method and apparatus for handling security procedure in mc communication system | |
WO2022237671A1 (zh) | 组寻呼的方法和装置 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 16885698 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 16885698 Country of ref document: EP Kind code of ref document: A1 |