WO2004107645A1 - Procede de mise a jour d'une cle partagee - Google Patents

Procede de mise a jour d'une cle partagee Download PDF

Info

Publication number
WO2004107645A1
WO2004107645A1 PCT/CN2004/000560 CN2004000560W WO2004107645A1 WO 2004107645 A1 WO2004107645 A1 WO 2004107645A1 CN 2004000560 W CN2004000560 W CN 2004000560W WO 2004107645 A1 WO2004107645 A1 WO 2004107645A1
Authority
WO
WIPO (PCT)
Prior art keywords
shared key
multicast
user
broadcast server
update
Prior art date
Application number
PCT/CN2004/000560
Other languages
English (en)
French (fr)
Inventor
Yingxin Huang
Original Assignee
Huawei Technologies Co., Ltd.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co., Ltd. filed Critical Huawei Technologies Co., Ltd.
Publication of WO2004107645A1 publication Critical patent/WO2004107645A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/08—Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
    • H04L9/0816—Key establishment, i.e. cryptographic processes or cryptographic protocols whereby a shared secret becomes available to two or more parties, for subsequent use
    • H04L9/0819—Key transport or distribution, i.e. key establishment techniques where one party creates or otherwise obtains a secret value, and securely transfers it to the other(s)
    • H04L9/083—Key transport or distribution, i.e. key establishment techniques where one party creates or otherwise obtains a secret value, and securely transfers it to the other(s) involving central third party, e.g. key distribution center [KDC] or trusted third party [TTP]
    • H04L9/0833—Key transport or distribution, i.e. key establishment techniques where one party creates or otherwise obtains a secret value, and securely transfers it to the other(s) involving central third party, e.g. key distribution center [KDC] or trusted third party [TTP] involving conference or group key
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/08—Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
    • H04L9/0891—Revocation or update of secret information, e.g. encryption key update or rekeying
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2209/00—Additional information or applications relating to cryptographic mechanisms or cryptographic arrangements for secret or secure communication H04L9/00
    • H04L2209/80—Wireless

Definitions

  • the present invention relates to a shared key update technology, and in particular, to a method for updating a group shared key. Background of the invention
  • a multicast / broadcast service refers to a one-to-multipoint unidirectional bearer service. Data is sent by one original entity to multiple receiving entities. As shown in FIG. 1, data is sent by a multicast / broadcast server to multiple terminal. In a certain area, users who have subscribed to the multicast / broadcast service can enjoy the services of the multicast / broadcast service. In the multicast / broadcast service, in order to prevent users who have not subscribed to the multicast / broadcast service or have not paid to enjoy the service of the multicast / broadcast service, a key needs to be set in the multicast / broadcast service, and the key is only multicast Only users in the / broadcast service group and the multicast / broadcast server can know.
  • a multicast / broadcast server refers to a functional entity that can provide multicast / broadcast services and has key generation management functions. It can be a new functional entity in a wireless communication network or one of the existing wireless communication networks. Functional entity or combination of multiple functional entities.
  • the multicast / broadcast server shares the set key with all users in the group, so this set of keys can be referred to as the multicast / broadcast service group shared key.
  • the multicast / broadcast server sends the encrypted shared key to the users in the group. This sending process is performed by the multicast / broadcast server and each user one-to-one.
  • the users in the group and the multicast / broadcast server perform mutual widow rights through authentication and key agreement protocol (AA).
  • AA authentication and key agreement protocol
  • the user and the multicast / broadcast server generate and own the encryption key (KEK) at the same time.
  • the encryption key is used to encrypt the shared key.
  • the encryption key of each user in the group is unique, that is, the encryption keys owned by the users in the group are different.
  • the multicast / broadcast server uses the encryption key corresponding to the users in the group to encrypt the shared secret. Key, and then send the encrypted shared key to the corresponding users in the group.
  • the user uses the corresponding encryption key to decrypt the shared key, and finally realizes the key sharing between the multicast / broadcast server and the users in the group.
  • the multicast / broadcast server uses the shared key to encrypt the multicast / broadcast service information, and then sends it to each user in the group.
  • the user uses the shared key to decrypt the multicast / broadcast service information, obtain the multicast / broadcast service information, and finally enjoy Services to multicast / broadcast services.
  • the security of the shared key needs to be ensured, so the shared key is not static and needs to be updated frequently.
  • the update process of the shared key requires one-to-one between the multicast / broadcast server and users in the group.
  • the multicast / broadcast server initiates the update of the shared key according to the trigger condition. After the shared key update is triggered, the multicast / broadcast server sends a new shared key to each user in the group at the same time.
  • an object of the present invention is to provide a method for updating a shared key, so as to avoid communication blockage of a wireless communication network caused by simultaneous updates of shared keys by users in a group.
  • the present invention provides a method for updating a shared key.
  • the method includes the following steps:
  • the multicast / broadcast server sends the current shared key and updated shared key to the user;
  • the multicast / broadcast server issues a switching command to the users in the group.
  • the multicast / broadcast server and the users in the group perform the shared key switch at the same time, and updates the shared key as the current Shared key C.
  • the user determines whether the updated shared key has been updated to a new shared key. If it is not updated, a request for updating the shared key is sent to the multicast / broadcast server, and the multicast / broadcast After receiving the shared key update request, the server sends the shared key update to the user, and the user stores the updated shared key. If the shared key is updated, no operation is performed, and the next shared key switching period expires. point.
  • the shared key has a corresponding serial number, and when the multicast / broadcast server delivers the shared key, the serial number is also carried at the same time.
  • the setting of the serial number count indicates the serial number of the updated shared key to be used next, and determining whether the updated shared key has been updated to a new shared key in step C includes: comparing the serial number count with the updated shared key. Whether the serial numbers are consistent. If they are consistent, it means that they have been updated; if they are not consistent, it means that they have not been updated.
  • the step A further includes: when the multicast / broadcast server delivers the current shared key and the updated shared key to the user, it simultaneously issues the serial number of the next updated shared key to be used, and the user uses the serial number As the initial value of the serial number count;
  • the handover command issued by the multicast / broadcast server in step B to the users in the group further carries a sequence number count, and the users in the group update the sequence number count with the sequence number.
  • the multicast / broadcast server sends the handover command to users in the group in a broadcast manner.
  • the shared key switching period of the multicast / broadcast server is longer than the update shared key application period of users in the group.
  • the method further includes: generating an encryption key corresponding to the user simultaneously with the user.
  • the method further includes: using the encryption key corresponding to the user to encrypt the current shared key and updating the shared key, and the user uses The encryption key corresponding to itself decrypts the current shared key and updates the shared key.
  • the method further includes: the multicast / broadcast server sends to the user an application cycle for updating the shared key, and after receiving the application, the user uses this cycle as his current application cycle and starts The update shared key application period is timed.
  • the method further includes: updating the update of the shared key application cycle, the multicast / broadcast server sends the current update shared key application cycle to the user through a point-to-point communication process or broadcast with the user, The user uses the received updated shared key application period as its current updated shared key application period, and starts the timer of the updated shared key application period after the original updated shared key application period expires.
  • the time point when each user in the group enters the multicast / broadcast service is taken as the starting point of the user's application period for updating the shared key, and the user updates the shared secret at each time.
  • the key application period expires, determine whether to initiate a shared key update request to the multicast / broadcast server. Because the time point for each user in the group to enter the multicast / broadcast service is randomly distributed, that is, each user in the group The time points for entering the multicast / broadcast service are basically different.
  • the expiration points of the user's own update shared key application cycle in the group are basically different, and the time point when the user initiates the update of the shared key to the multicast / broadcast server It is also basically different, achieving the purpose of decentralizing the time points when users initiate a request to update the shared key to the multicast / broadcast server, and thereby effectively preventing the communication of the wireless communication network from being blocked.
  • Figure 1 shows a schematic diagram of multiple / broadcast services
  • FIG. 2 shows a flowchart for implementing a shared key update in the present invention
  • Fig. 3 is a flowchart showing an embodiment of the present invention. Mode of Carrying Out the Invention
  • K_COUNT Shared key serial number count next time
  • C-SHARE Current shared key data
  • N-SHARE Update shared key data
  • Shared key switching cycle In a shared key switching cycle, the shared key used by the multicast / broadcast server and users in the group is the current shared key, that is, the shared key in the C-SHARE data structure; When the shared key switching cycle ends, that is, at the beginning of the next shared key switching cycle, the multicast / broadcast server broadcasts the shared key switching command to all users in the group. The multicast / broadcast server and all users in the group simultaneously The shared key is switched to update the shared key, that is, the updated shared key in the Si-SHARE data structure. At this time, the updated shared key becomes the current shared key.
  • Update shared key application cycle Users in the group periodically check whether to initiate a request to update the shared key to the multicast / broadcast server according to their shared key application cycle.
  • a multicast / broadcast server shared key switching period and a user's own update shared key application period in the group are set, and the multicast / broadcast server sends a request to users in the group when each shared key switching period expires.
  • a shared key switch command is issued, and the multicast / broadcast server and the users in the group complete the update of the shared key at the same time; when the user of the group updates each shared key application period, it checks whether it is multicast.
  • / Broadcast server initiates a shared key update request, using the time point when each user in the group enters the multicast / broadcast service as the starting point for starting the user's update shared key application cycle, and each user in the group enters the multicast
  • the time points of the / broadcast service are randomly distributed, that is, the time points at which each user in the group enters the multicast / broadcast service are basically different, so the starting points of the user's own update shared key application cycle in the group are basically different.
  • the time point of initiating the request to update the shared key to the multicast / broadcast server is also basically different, which effectively prevents users in the group from sending multicast / broadcast services at the same time.
  • the router initiates a request to update the shared key, thereby effectively preventing communication congestion in the wireless communication network.
  • the shared key switching period of the multicast / broadcast server should be greater than the user's own application for updating the shared key. cycle.
  • the user's own update shared key application period in the group can be set by the multicast / broadcast server.
  • the multicast / broadcast server may send the set update shared key application period together with other key information and the like to the user.
  • the user uses the application period for updating the shared key as the period for applying for updating the shared key.
  • the multicast / broadcast server can set the same update shared key application cycle for the users in the group. Because the users join the multicast / broadcast service at different time points, the users apply for the update key update time. It can effectively avoid network congestion. At this time, the multicast / broadcast server can broadcast a new update shared key application cycle to the users in the group by broadcasting.
  • the multicast / broadcast server can also set different update and update key application periods for users in the group, so that users can apply to update the shared key ⁇ random distribution of time points is larger, which can effectively avoid network congestion.
  • the update shared key application period for users in the group can also be updated.
  • the multicast / broadcast server can update the users in the group. Notify the corresponding user of the updated shared key application period, the users in the group use the current updated shared key application period as the period for themselves to apply to update the shared key, and start the update after the original shared key application period expires Shared key application cycle timing.
  • the multicast / broadcast server uses the current shared key to encrypt the multicast / broadcast service information. Accordingly, users in the group use the current shared key. Key decryption of multicast / broadcast service information.
  • the multicast / broadcast server broadcasts the shared key switching command to all users in the group, the multicast / broadcast server and the group All users within the group switch the shared key at the same time. At this time, the updated shared key becomes the current shared key.
  • the shared key switch command broadcast by the multicast / broadcast server to all users in the group carries K_COUNT corresponding to the next shared key switch. Because the shared key switch command is issued in a broadcast form, it will not occupy too much system resources, so it will not block the communication of the wireless communication network.
  • the time when each user in the group enters the multicast / broadcast service is taken as the starting point for starting the user's update shared key application cycle.
  • the point in time when the user enters the multi-cast / broadcast service means that after the multicast / broadcast server has authenticated the user as a user in the group that has subscribed to the multicast / broadcast service, the user receives the message sent by the multicast / broadcast server to it The point in time when the key was shared.
  • the multicast / broadcast server After the user is authenticated by the multicast / broadcast service server as a user in the group that has subscribed to the multicast / broadcast service, the multicast / broadcast server uses the encryption key corresponding to the user to encrypt
  • C—SHARE and N—SHARE that is, encrypting the current shared key and the serial number corresponding to the current shared key, and updating the shared key and the serial number corresponding to the updated shared key, and then sending the encryption to the user C—SHARE and N—SHARE, and simultaneously send K_COUNT corresponding to the shared key for the next switch;
  • the user uses the corresponding encryption key to decrypt C—SHARE and N—SHARE, and stores C—SHARE and N— SHARE, that is, storing the current shared key and a serial number corresponding to the current shared key and an updated shared key and a serial number corresponding to the updated shared key, and simultaneously storing a corresponding number for the next shared key switch K-COUNT.
  • the time point of K_COUNT corresponding to the key is used as the starting point for starting the user's application cycle for updating the shared key.
  • the point in time when each user in the group enters the multicast / broadcast service is randomly distributed, so the starting point of the user's shared key application cycle in the group is basically different, and the time point at which each user initiates a request to update the shared key will also be Differently, the time points when the users in the group initiate the request to update the shared key are effectively dispersed.
  • FIG. 2 shows a flowchart of implementing a shared key update in the present invention.
  • the implementation process of updating a shared key includes the following steps:
  • Step 201 The multicast / broadcast server broadcasts a shared key switch command to users in the group at the expiration point of each shared key switch cycle, and the multicast / broadcast server and the users in the group are simultaneously The update of the shared key is completed. At this time, the update shared key is switched to the current shared key.
  • the shared key switch command broadcast by the multicast / broadcast server to the users in the group carries the K_COUNT corresponding to the shared key for the next switch, and the users in the group store this. K_COUNT, which updates the K_COUNT stored by itself .
  • Step 202 to step 203 At the expiration point of each user's own update shared key application period in the group, determine whether the serial number corresponding to the update shared key stored by itself is consistent with the K_COUNT currently stored, That is, it is determined whether the update shared key stored in itself has been updated. If the update shared key is not consistent, that is, the update shared key is not updated, the user sends a multicast / broadcast server to update the shared key.
  • the multicast / broadcast server After the multicast / broadcast server receives the request to update the shared key, it uses the encryption key corresponding to the user to encrypt N-SHARE, that is, to encrypt the updated shared key and the serial number corresponding to the updated shared key, and then The encrypted N-SHARE is sent to the user; after receiving the encrypted N-SHARE, the user uses the encryption key corresponding to itself to decrypt the N-SHARE, and then stores the currently acquired N-SHARE, that is, stores the updated shared key. And the serial number corresponding to the updated shared secret. If they are the same, that is, the update shared key has been updated, the process of initiating a request for updating the shared key by a subsequent user is omitted, and the user waits for the expiration point of the next application period for updating the shared key.
  • the multicast / broadcast server performs the respective operations according to the shared key switching cycle, and the users in the group cyclically update the shared key application cycle.
  • FIG. 3 shows a flowchart of an embodiment of the present invention.
  • an implementation process of updating a shared key includes the following steps:
  • Step 301 The multicast / broadcast server expires at a shared key switching period, and broadcasts the shared key switch command to users in the group.
  • the multicast / broadcast server and users in the group complete the update of the shared key at the same time.
  • the shared key switch command broadcast by the multicast / broadcast server to the users in the group carries a K_COUNT corresponding to the next shared key switch, and the users in the group store the K_COUNT, that is, more New self stored K_COUNT.
  • Steps 302 to 303 During the current shared key switching period of the multicast / broadcast server, user A is powered on and authenticated by the wireless communication network to confirm that user A is a user in the group that has subscribed to the multicast / broadcast service. / Broadcast server and user A generate and own the encryption key corresponding to user A at the same time. Multicast / broadcast server uses the encryption key corresponding to user A to encrypt C_SHARE and N_SHARE, that is, to encrypt the current shared key and the current shared key.
  • the serial number corresponding to the shared key and the updated shared key and the serial number corresponding to the updated shared key and then send the encrypted C_SHARE and> _81 ⁇ 1 £ to user A, and send it to user A at the same time
  • the K_COUNT corresponding to the next shared key switch and the user in the group update the shared key application cycle.
  • User A uses the encryption key corresponding to itself to decrypt C_SHARE and N_SHARE, and then stores C_SHARE And N-SHARE, that is, storing the current shared key and the serial number corresponding to the current shared key and the updated shared key and corresponding to the updated shared key
  • the serial number, and the K_COUNT corresponding to the next shared key switch and the update shared key application period are stored.
  • the received shared key application period is used as the period for itself to update the shared key.
  • user A Taking the time points of the received encrypted C_SHARE and N_SHARE and K_COU T as the starting point for starting their own application period for updating the shared key, user A starts the timing of the application period for updating their shared key.
  • the shared key application cycle for users in the group can also be updated.
  • the multicast / broadcast server can update the users in the group. Notify the corresponding user of the updated shared key application cycle.
  • Step 304 The expiration point of the next shared key switching cycle of the multicast / broadcast server is basically the same as step 301.
  • User A updates the shared key.
  • the update shared key is switched to the current shared key, and K_COUNT corresponding to the next shared key switch is updated.
  • Step 305 User A's next update shared key application cycle begins. User A Determine whether the serial number corresponding to the update shared key stored by itself is the same as the currently stored
  • K_COUNT is the same, it is judged whether the updated shared key stored by itself is updated. If it is not the same, that is, the updated shared key is not updated, go to step 306; if they are the same, that is, the updated shared key has been updated and wait for the next self update. At the beginning of the shared key application cycle, it is determined whether the serial number corresponding to the updated shared key stored by itself is consistent with the currently stored K_COUNT.
  • Steps 306 to 307 User A sends a shared key update request to the multicast / broadcast server; after the multicast / broadcast server receives the shared key update request, the multicast / broadcast server uses an encryption key corresponding to user A Encrypt N-SHARE, that is, to encrypt the updated shared key and the serial number corresponding to the updated shared key, and then send the encrypted N-SHARE to user A; After user A receives the encrypted N-SHARE, he uses it with himself The corresponding encryption key decrypts the N-SHARE, and then stores the currently acquired N-SHARE, that is, stores the updated shared key and the serial number corresponding to the updated shared key.
  • the multicast / broadcast server can reset the user A's update shared key application cycle.
  • the multicast / broadcast server can add the new Update the shared key application cycle notification to the user.
  • the user regards the new update shared key application period as the period for itself to apply for updating the shared key, and starts the update after the original update shared key application period expires. Shared key application cycle timing.
  • the subsequent process is basically the same as steps 304 to 307, and is not repeated here.

Landscapes

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

Description

一种更新共享密钥的方法
技术领域
本发明涉及共享密钥更新技术， 特别是指一种更新群组共享密钥的 方法。 发明背景
在无线通信网络中， 多播 /广播业务是指一点到多点的单向承载业 务， 数据由一个原实体发送至多个接收实体， 如图 1所示， 数据由多播 /广播服务器发送至多个终端。 在一定区域内， 已经订阅多播 /广播业务 的用户能够享受多播 /广播业务的服务。 在多播 /广播业务中， 为防止没 有订阅多播 /广播业务或未付费的用户享受到多播 /广播业务的服务， 需 要在多播 /广播业务中设置密钥， 并且密钥只有多播 /广播业务群组内用 户和多播 /广播服务器才能知道。 多播 /广播服务器是指能够提供多播 /广 播服务， 兼具密钥生成管理功能的功能实体， 可为在无线通信网络中新 增的功能实体， 也可为现有无线通信网络中的一个功能实体或多个功能 实体的组合。
多播 /广播服务器和群组内所有用户共享设置的密钥， 因此可将这个 设置的密钥称为多播 /广播业务群組共享密钥。 多播 /广播服务器向群组 内用户发送加密的共享密钥，这个发送过程是多播 /广播服务器和每个用 户一对一进行的。群组内用户和多播 /广播服务器通过鉴权和密钥协商协 议（A A )进行互婆权， 在互鉴权过程中， 用户和多播 /广播服务器同时 生成并拥有加密密钥 （KEK ), 该加密密钥用来加密共享密钥， 群组内 每个用户的加密密钥是唯一的， 即群组内用户拥有的加密密钥各不相 同。 多播 /广播服务器使用与群組内用户相对应的加密密钥加密共享密 钥， 然后将经过加密的共享密钥发送给群组内相应用户， 用户使用与其 相对应的加密密钥解密共享密钥，最终实现多播 /广播服务器和群组内用 户的密钥共享。 多播 /广播服务器使用共享密钥加密多播 /广播业务信息， 然后发送给群组内每个用户， 用户使用共享密钥解密多播 /广播业务信 息， 获取多播 /广播业务信息， 最终享受到多播 /广播业务的服务。
为防止群组外的用户为享受多播 /广播业务而非法截取共享密钥， 需 要保证共享密钥的安全性， 因此共享密钥不是一成不变的， 需要经常更 新。共享密钥的更新过程需要多播 /广播服务器与群组内用户之间一对一 进行。 多播 /广播服务器根据触发条件发起共享密钥的更新， 触发共享密 钥更新后， 多播 /广播服务器向群组内每个用户同时发送新的共享密钥。 如果群组内存在大量可享受多播 /广播业务服务的用户，共享密钥的同时 更新导致无线通信网络中的信息量在瞬间激增， 势必使无线通信网络的 通信受到阻塞。 发明内容
有鉴于此， 本发明的目的在于提供一种更新共享密钥的方法， 避免 因群组内用户同时进行共享密钥的更新而导致的无线通信网络通信阻 塞。
为了达到上述目的， 本发明提供了一种更新共享密钥的方法， 该方 法包含以下步驟：
A、用户接入多播 /广播业务时，通过多播 /广播服务器的身份验证后， 多播 /广播服务器向用户发送将当前共享密钥和更新共享密钥；
B、 共享密钥切换周期到期点， 多播 /广播服务器向群组内用户下发 切换命令， 多播 /广播服务器与群组内用户同时进行共享密钥切换， 将更 新共享密钥作为当前共享密钥； C、 更新共享密钥申请周期到期点， 用户判断更新共享密钥是否已 更新为新的共享密钥， 如果未更新， 则向多播 /广播服务器发送更新共享 密钥请求， 多播 /广播服务器收到更新共享密钥请求后， 向所述用户发送 更新共享密钥， 所述用户存储更新共享密钥， 如果已更新， 则不进行任 何操作， 等待下一个共享密钥切换周期的到期点。
所述共享密钥具有与其相对应的序列号， 多播 /广播服务器下发共享 密钥时， 同时携带所述序列号。
设置序列号计数， 表示下一个将要使用的更新共享密钥的序列号， 所述步驟 C中判断更新共享密钥是否已更新为新的共享密钥包括： 比较序列号计数与更新共享密钥的序列号是否一致， 如果一致， 则表示 已更新； 如果不一致， 表示未更新。
所述步骤 A进一步包括：多播 /广播服务器向用户下发当前共享密钥 和更新共享密钥时， 同时下发下一个将要使用的更新共享密钥的序列 号， 所述用户以该序列号作为序列号计数的初始值；
步骤 B 中所述多播 /广播服务器向群组内用户下发的切换命令中进 一步携带有序列号计数， 群组内用户以所述序列号更新序列号计数。
多播 /广播服务器通过广播方式向群组内用户下发所述的切换命令。 所述多播 /广播服务器的共享密钥切换周期大于群组内用户的更新 共享密钥申请周期。
步骤 A中所述通过多播 /广播服务器的身份验证后，进一步包括： 与 用户同时生成与该用户相对应的加密密钥。
步骤 A 中多播 /广播服务器在下发当前共享密钥和更新更新密钥之 前， 进一步包括： 使用与所述用户相对应的加密密钥加密当前共享密钥 和更新共享密钥， 所述用户使用与自身相对应的加密密钥解密当前共享 密钥和更新共享密钥。 步骤 A中所述通过多播 /广播服务器的身份验证后，进一步包括： 多 播 /广播服务器向用户发送更新共享密钥申请周期，用户收到后将该周期 作为自身当前的申请周期， 并启动该更新共享密钥申请周期计时。
该方法进一步包括： 更新共享密钥申请周期的更新， 是由多播 /广播 月良务器通过与用户的点到点通信过程或广播方式， 向用户下发当前的更 新共享密钥申请周期， 所述用户将收到的该更新共享密钥申请周期作为 自身当前的更新共享密钥申请周期， 并在原有更新共享密钥申请周期到 期后启动所述更新共享密钥申请周期计时。
根据本发明提出的更新共享密钥的方法 , 以群组内每个用户进入多 播 /广播业务的时间点作为该用户更新共享密钥申请周期的起始点，用户 在自身的每个更新共享密钥申请周期到期时，确定是否向多播 /广播服务 器发起更新共享密钥请求，由于群组内每个用户进入多播 /广播业务的时 间点是随机分布的，即群组内每个用户进入多播 /广播业务的时间点基本 各不相同， 因此， 群组内用户自身的更新共享密钥申请周期的到期点基 本不同， 用户向多播 /广播服务器发起更新共享密钥的时间点也基本不 同，实现了分散用户向多播 /广播服务器发起更新共享密钥请求的时间点 的目的， 进而有效避免无线通信网络的通信受到阻塞。 附图简要说明
图 1示出了多番 /广播业务示意图；
图 2示出了本发明中共享密钥更新实现流程图；
图 3为示出了本发明中一实施例流程图。 实施本发明的方式
下面结合附图对本发明进行详细描述。 在对本发明提出的技术方案进行描述之前， 首先介绍本发明中将要 涉及的几个概念。
下次切换共享密钥序列号计数 ( K_COUNT ): 表示下一个将要使用 的更新共享密钥的序列号。 K—COU T存储在用户端, 由多播 /广播月良务 器来通知用户更新， 多播 /广播服务器下发共享密钥切换命令时， 同时携 带与下一次将要切换的共享密钥相对应的序列号， 用户以该值更新自身 存储的 K— COUNT, 序列号和 K—COUNT的取值范围一致， 可以为 0 ~ 128。 多播 /广播服务器可以指定序列号每次递增， 例如： 1、 2、 3...... , 也可以不按顺序灵活指定， 例如， 当前共享密钥的序列号是 4, 多播 /广 播服务器可指定下一个即将使用的共享密钥序列号为 8。
当前共享密钥数据 ( C— SHARE ): 多播 /广播服务器和群组内用户当 前正在使用的共享密钥， 实际应为数据结构， 即多播 /广播服务器和群组 内用户当前正在使用的共享密钥及与该共享密钥相对应的序列号。
更新共享密钥数据（N— SHARE ): 多播 /广播服务器和群組内用户即 将使用的共享密钥， 实际应为数据结构， 即多播 /广播月艮务器和群組内用 户即将使用的共享密钥及与该共享密钥相对应的序列号。
共享密钥切换周期： 在一个共享密钥切换周期内， 多播 /广播服务器 和群组内用户使用的共享密钥为当前共享密钥， 即 C一 SHARE数据结构 中的共享密钥； 在当前共享密钥切换周期结束时， 即下一个共享密钥切 换周期开始时，多播 /广播服务器向群组内所有用户广播共享密钥切换命 令，多播 /广播服务器和群组内所有用户同时将共享密钥切换为更新共享 密钥， 即] Si—SHARE数据结构中的更新共享密钥， 此时， 更新共享密钥 成为当前共享密钥。
更新共享密钥申请周期： 群组内用户根据自身的共享密钥申请周期 定时检查是否向多播 /广播服务器发起更新共享密钥请求。 本发明中，设置多播 /广播服务器共享密钥切换周期和群组内用户自 身的更新共享密钥申请周期，多播 /广播服务器在每个共享密钥切换周期 到期时向群组内用户下发共享密钥切换命令，多播 /广播服务器和群組内 用户同时完成共享密钥的更新； 群组内用户在自身的每个更新共享密钥 申请周期到期时 , 检查是否向多播 /广播服务器发起更新共享密钥请求， 以群组内每个用户进入多播 /广播业务的时间点作为启动该用户更新共 享密钥申请周期的起始点 ,而群组内每个用户进入多播 /广播业务的时间 点是随机分布的，即群组内每个用户进入多播 /广播业务的时间点基本不 同， 因此群组内用户自身的更新共享密钥申请周期的起始点基本不同， 用户向多播 /广播服务器发起更新共享密钥请求的时间点也基本不同，有 效地避免了群组内用户在同一时间点向多播 /广播服务器发起更新共享 密钥请求， 从而有效地避免了无线通信网络的通信阻塞。
为保证每次共享密钥切换前， 群组内用户能够发起一次更新共享密 钥请求，多播 /广播月艮务器的共享密钥切换周期应大于群组内用户自身的 更新共享密钥申请周期。
群组内用户自身的更新共享密钥申请周期可由多播 /广播服务器进 行设置。 在用户加入多播 /广播业务时， 多播 /广播服务器可将设定的更 新共享密钥申请周期同其它的密钥信息等一同发送给用户。 用户以该更 新共享密钥申请周期作为自身申请更新共享密钥的周期。多播 /广播良务 器可为群组内用户设置相同的更新共享密钥申请周期， 因为用户加入多 播 /广播业务的时间点不同，所以用户申请更新更新密钥的时间点也会不 同， 可以有效的避免网络阻塞， 此时， 多播 /广播 ^ 务器可通过广播方式 向群组内用户广播新的更新共享密钥申请周期。多播 /广播服务器也可以 为群组内用户设置不同的更新更新密钥申请周期， 这样用户申请更新共 享密钥 ^时间点的随机分布也就更大了， 更能够有效地避免网络阻塞。 群组内用户的更新共享密钥申请周期， 也可以被更新， 在后续多播 /广播 服务器与用户进行的任何一次点到点通信过程中 ,多播 /广播服务器都可 以将群组内用户新的更新共享密钥申请周期通知给相应用户， 群組内用 户以当前更新共享密钥申请周期作为自身申请更新共享密钥的周期， 并 在原有更新共享密钥申请周期到期后启动所述更新共享密钥申请周期 计时。
设置多播 /广播服务器的共享密钥切换周期，每个共享密钥切换周期 内， 多播 /广播服务器使用当前共享密钥加密多播 /广播业务信息， 相应 地，群组内用户使用当前共享密钥解密多播 /广播业务信息。 当一个共享 密钥切换周期结束时， 即下一个共享密钥切换周期开始时， 多播 /广播月良 务器向群组内所有用户广播共享密钥切换命令，多播 /广播服务器和群组 内所有用户同时切换共享密钥，此时，更新共享密钥成为当前共享密钥。 在多播 /广播服务器向群组内所有用户广播的共享密钥切换命令中携带 有与下次切换共享密钥相对应的 K— COUNT。 由于共享密钥切换命令是 以广播形式下发的， 不会过多地占用系统资源， 因此， 不会使无线通信 网络的通信受到阻塞。
设置群组内每个用户的更新共享密钥申请周期， 每个群组内用户总 是存储有两个共享密钥数据 C_SHARE和 N— SHARE, 即当前共享密钥 及与该当前共享密钥相对应的序列号和更新共享密钥及与该更新共享 密钥相对应的序列号， 并且存储有与下次切换共享密钥相对应的 K— COU T。 群组内用户通过多播 /广播服务器广播的切换命令中携带的 与下次切换共享密钥相对应的 K_ COUNT , 不断更新自身存储的 K— COU T。 群组内用户在一个更新共享密钥申请周期结束时， 即下一 个更新共享密钥申请周期开始时， 通过判断与自身存储的更新共享密钥 相对应的序列号与 K— COUNT的一致性 ,确定是否向多播 /广播服务器发 起更新共享密钥请求。
将群组内每个用户进入多播 /广播业务的时间点作为启动该用户更 新共享密钥申请周期的起始点。用户进入多 4番 /广播业务的时间点是指多 播 /广播服务器已认证该用户为已订购多播 /广播业务的群组内用户后， 该用户收到多播 /广播服务器向其发送的共享密钥的时间点。
用户经多播 /广播业务服务器认证为已订购多播 /广播业务的群组内 用户后， 多播 /广播服务器使用与该用户相对应的加密密钥加密
C— SHARE和 N— SHARE,即加密当前共享密钥及与该当前共享密钥相对 应的序列号和更新共享密钥及与该更新共享密钥相对应的序列号， 然后 向该用户发送加密的 C—SHARE和 N— SHARE, 并且同时发送与下次切 换共享密钥相对应的 K_COUNT; 该用户使用与其相对应的加密密钥解 密 C— SHARE和 N— SHARE,存储 C— SHARE和 N— SHARE, 即存储当前 共享密钥及与该当前共享密钥相对应的序列号和更新共享密钥及与该 更新共享密钥相对应的序列号， 同时存储与下次切换共享密钥相对应的 K—COUNT。 群组内用户将其加入多播 /广播业务的时间点作为启动更新 共享密钥申请周期的起始点， 即将群组内用户收到加密的 C—SHARE、 N— SHARE以及与下次切换共享密钥相对应的 K— COUNT的时间点作为 启动该用户更新共享密钥申请周期的起始点。 群组内每个用户进入多播 /广播业务的时间点是随机分布的，因此群组内用户共享密钥申请周期的 起始点基本不同， 进而各用户发起更新共享密钥请求的时间点也会不 同， 有效地分散了群组内用户发起更新共享密钥请求的时间点。
图 2示出了本发明中共享密钥更新实现流程图， 如图 2所示， 更新 共享密钥的实现过程包括以下步骤：
步骤 201: 多播 /广播服务器在每个共享密钥切换周期的到期点， 向 群组内用户广播共享密钥切换命令，多播 /广播服务器和群组内用户同时 完成共享密钥的更新， 此时， 更新共享密钥切换成为当前共享密钥。 多 播 /广播服务器向群组内用户广播的共享密钥切换命令中携带与下次切 换共享密钥相对应的 K— COUNT, 群组内用户存储该. K— COUNT, 即更 新自身存储的 K_COUNT。
步骤 202〜步骤 203: 群组内用户在每个自身更新共享密钥申请周期 的到期点， 判断与自身存储的更新共享密钥相对应的序列号是否与当前 存储的 K— COUNT相一致，即判断自身存储的更新共享密钥是否更新过， 如果不一致， 即更新共享密钥未更新， 则该用户向多播 /广播服务器发送 更新共享密钥请求。 多播 /广播服务器收到更新共享密钥请求后， 使用与 该用户相对应的加密密钥加密 N— SHARE, 即加密更新共享密钥及与该 更新共享密钥相对应的序列号，然后将加密的 N— SHARE发送给该用户； 该用户收到加密的 N— SHARE后， 使用与自身相对应的加密密钥解密 N— SHARE, 然后存储当前获取的 N— SHARE, 即存储更新共享密钥及与 该更新共享密钥相对应的序列号。 如果一致， 即更新共享密钥已更新， 则后续用户发起更新共享密钥请求的过程省略， 该用户等待下一个自身 更新共享密钥申请周期的到期点。
根据以上所述过程， 多播 /广播服务器根据共享密钥切换周期、 群组 内用户根据更新共享密钥申请周期循环进行各自操作。
图 3示出了本发明中一实施例流程图， 如图 3所示， 本实施例中， 更新共享密钥的实现过程包括以下步骤：
步骤 301: 多播 /广播服务器一个共享密钥切换周期的到期点， 向群 组内用户广播共享密钥切换命令，多播 /广播服务器和群组内用户同时完 成共享密钥的更新， 此时， 更新共享密钥切换为当前共享密钥。 多播 / 广播服务器向群组内用户广播的共享密钥切换命令中携带有与下次切 换共享密钥相对应的 K_COUNT, 群组内用户存储该 K_COUNT, 即更 新自身存储的 K_COUNT。
步骤 302〜步骤 303: 当前多播 /广播服务器的共享密钥切换周期内， 用户 A开机， 经过无线通信网络的认证， 确认用户 A为已订购多播 /广 播业务的群组内用户， 多播 /广播服务器和用户 A 同时生成并拥有与用 户 A相对应的加密密钥， 多昏 /广播服务器使用与用户 A相对应的加密 密钥加密 C_SHARE和 N_SHARE， 即加密当前共享密钥及与该当前共 享密钥相对应的序列号和更新共享密钥及与该更新共享密钥相对应的 序列号， 然后将加密的 C— SHARE和> _81^1£发送给用户 A, 并且同 时向用户 A发送与下次切换共享密钥相对应的 K— COUNT及群组内用户 更新共享密钥申请周期， 用户 A使用与自身相对应的加密密钥解密 C— SHARE和 N— SHARE, 然后存储 C— SHARE和 N— SHARE, 即存储当 前共享密钥及与该当前共享密钥相对应的序列号和更新共享密钥及与 该更新共享密钥相对应的序列号， 并且存储与下次切换共享密钥相对应 的 K— COUNT及更新共享密钥申请周期，将收到的更新共享密钥申请周 期作为其自身申请更新共享密钥的周期， 同时用户 A将收到的加密 C— SHARE和 N— SHARE及 K_COU T的时间点作为启动其自身更新共 享密钥申请周期的起始点，用户 A启动其自身更新共享密钥申请周期的 计时。 群组内用户的更新共享密钥申请周期， 也可以被更新， 在后续多 播 /广播服务器与用户进行的任何一次点到点通信过程中 , 多播 /广播服 务器都可将群组内用户新的更新共享密钥申请周期通知给相应用户。
步骤 304: 多播 /广播服务器的下一个共享密钥切换周期的到期点， 与步骤 301基本相同。 用户 A进行共享密钥的更新， 此时， 更新共享密 钥切换为当前共享密钥， 并且更新与下次切换共享密钥相对应的 K— COUNT。
步骤 305: 用户 A的下一个更新共享密钥申请周期的开始， 用户 A 判断与自身存储的更新共享密钥相对应的序列号是否与当前存储的
K— COUNT相一致， 即判断自身存储的更新共享密钥是否更新过， 如果 不一致， 即更新共享密钥未更新， 执行步骤 306; 如果一致， 即更新共 享密钥已更新， 等待下一个自身更新共享密钥申请周期的开始， 再对与 自身存储的更新共享密钥相对应的序列号是否与当前存储的 K— COUNT 相一致进行判断。
步骤 306〜步骤 307: 用户 A向多播 /广播服务器发送更新共享密钥 请求； 多播 /广播服务器收到更新共享密钥请求后， 多播 /广播服务器使 用与用户 A相对应的加密密钥加密 N— SHARE, 即加密更新共享密钥及 与该更新共享密钥相对应的序列号， 然后将加密的 N一 SHARE发送给用 户 A; 用户 A收到加密的 N— SHARE后， 使用与自身相对应的加密密钥 解密 N— SHARE, 然后存储当前获取的 N— SHARE, 即存储更新共享密 钥及与该更新共享密钥相对应的序列号。在当前多播 /广播服务器与用户 A的点到点通信过程中， 多播 /广播服务器就可以重新设置用户 A的更 新共享密钥申请周期，多播 /广播服务器可在步骤 307中将新的更新共享 密钥申请周期通知给用户。 用户在收到新的更新共享密钥申请周期后， 将新的更新共享密钥申请周期作为其自身申请更新共享密钥的周期， 并 在原有更新共享密钥申请周期到期后启动所述更新共享密钥申请周期 计时。
后续过程与步骤 304~步骤 307基本相同， 在此不再赘述。
总之， 以上所述仅为本发明的较佳实施例而已， 并非用于限定本发 明的保护范围。

Claims

权利要求书
1、 一种更新共享密钥的方法， 其特征在于， 该方法包含以下步骤： ' A、用户接入多播 /广播业务时，通过多播 /广播服务器的身份验证后， 多播 /广播服务器向用户发送将当前共享密钥和更新共享密钥；
B、 共享密钥切换周期到期点， 多播 /广播服务器向群组内用户下发 切换命令， 多播 /广播服务器与群组内用户同时进行共享密钥切换， 将更 新共享密钥作为当前共享密钥；
C、 更新共享密钥申请周期到期点， 用户判断更新共享密钥是否已 更新为新的共享密钥， 如果未更新， 则向多播 /广播服务器发送更新共享 密钥请求， 多播 /广播服务器收到更新共享密钥请求后， 向所述用户发送 更新共享密钥， 所述用户存储更新共享密钥， 如果已更新， 则不进行任 何操作， 等待下一个共享密钥切换周期的到期点。
2、根据权利要求 1所述的方法， 其特征在于， 所述共享密钥具有与 其相对应的序列号， 多播 /广播服务器下发共享密钥时， 同时携带所述序 列号。
3、根据权利要求 2所述的方法， 其特征在于， 设置序列号计数， 表 示下一个将要使用的更新共享密钥的序列号，
所述步骤 C中判断更新共享密钥是否已更新为新的共享密钥包括： 比较序列号计数与更新共享密钥的序列号是否一致， 如果一致， 则表示 已更新； 如果不一致， 表示未更新。
4、 根据权利要求 3所述的方法， 其特征在于，
所述步骤 A进一步包括：多播 /广播服务器向用户下发当前共享密钥 和更新共享密钥时， 同时下发下一个将要使用的更新共享密钥的序列 号， 所述用户以该序列号作为序列号计数的初始值； 步驟 B 中所述多 ·/广播服务器向群组内用户下发的切换命令中进 一步携带有序列号计数， 群组内用户以所述序列号更新序列号计数。
5、 根据权利要求 1所述的方法， 其特征在于， 多播 /广播服务器通 过广播方式向群组内用户下发所述的切换命令。
6、 根据权利要求 1所述的方法， 其特征在于， 所述多播 /广播服务 器的共享密钥切换周期大于群组内用户的更新共享密钥申请周期。
7、 根据权利要求 1所述的方法， 其特征在于， 步骤 A中所述通过 多播 /广播服务器的身份验证后， 进一步包括： 与用户同时生成与该用户 相对应的加密密钥。
8、 根据权利要求 7所述的方法， 其特征在于， 步骤 A中所述多播 / 广播服务器在下发当前共享密钥和更新更新密钥之前， 进一步包括： 使 用与所述用户相对应的加密密钥加密当前共享密钥和更新共享密钥， 所 述用户使用与自身相对应的加密密钥解密当前共享密钥和更新共享密 钥。
9、 根据权利要求 1所述的方法， 其特征在于， 步骤 A中所述通过 多播 /广播服务器的身份验证后， 进一步包括： 多播 /广播服务器向用户 发送更新共享密钥申请周期， 用户收到后将该周期作为自身当前的申请 周期， 并启动该更新共享密钥申请周期计时。
10、根据权利要求 9所述的方法， 其特征在于， 该方法进一步包括： 更新共享密钥申请周期的更新，是由多播 /广播服务器通过与用户的点到 点通信过程或广播方式， 向用户下发当前的更新共享密钥申请周期， 所 述用户将收到的该更新共享密钥申请周期作为自身当前的更新共享密 钥申请周期， 并在原有更新共享密钥申请周期到期后启动所述更新共享 密钥申请周期计时。
PCT/CN2004/000560 2003-05-29 2004-05-28 Procede de mise a jour d'une cle partagee WO2004107645A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN03123954.4 2003-05-29
CNB031239544A CN100362785C (zh) 2003-05-29 2003-05-29 一种共享密钥更新的方法

Publications (1)

Publication Number Publication Date
WO2004107645A1 true WO2004107645A1 (fr) 2004-12-09

Family

ID=33480382

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2004/000560 WO2004107645A1 (fr) 2003-05-29 2004-05-28 Procede de mise a jour d'une cle partagee

Country Status (2)

Country Link
CN (1) CN100362785C (zh)
WO (1) WO2004107645A1 (zh)

Families Citing this family (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101242274B (zh) * 2005-06-24 2011-04-13 华为技术有限公司 保证消息序列号不重复、防止重放攻击的方法及移动终端
CN100571124C (zh) * 2005-06-24 2009-12-16 华为技术有限公司 防止重放攻击的方法以及保证消息序列号不重复的方法
JP4148246B2 (ja) * 2005-06-30 2008-09-10 ブラザー工業株式会社 通信システム、証明書更新装置、証明書更新プログラム、通信装置及び代替更新プログラム
US20070124807A1 (en) * 2005-11-29 2007-05-31 Taiwan Semiconductor Manufacturing Co., Ltd. Password update systems and methods
CN101087188B (zh) * 2006-06-08 2011-04-13 华为技术有限公司 无线网络中mbs授权密钥的管理方法及系统
CN101155027B (zh) * 2006-09-27 2012-07-04 华为技术有限公司 密钥共享方法和系统
CN1929373B (zh) * 2006-10-19 2011-04-20 中控科技集团有限公司 工业安全控制系统及其控制方法
CN100461974C (zh) * 2007-05-09 2009-02-11 中兴通讯股份有限公司 密钥更新触发方法及装置
CN101162997B (zh) * 2007-08-09 2010-06-02 四川长虹电器股份有限公司 一种电子设备接口间广播共享密钥的更新方法
CN101102552B (zh) * 2007-08-16 2012-12-19 中兴通讯股份有限公司 业务密钥更新方法和系统
US8923811B2 (en) * 2008-03-14 2014-12-30 Alcatel Lucent Methods and apparatuses for dynamic management of security associations in a wireless network
CN102333280B (zh) * 2011-09-26 2018-02-09 中兴通讯股份有限公司 一种业务密钥更新的方法、系统及业务处理服务器
WO2021212413A1 (zh) * 2020-04-23 2021-10-28 华为技术有限公司 一种密钥的传输方法及装置
EP4290790A4 (en) * 2021-02-26 2024-03-20 Huawei Technologies Co., Ltd. KEY ACQUISITION METHOD AND APPARATUS AND KEY MANAGEMENT SYSTEM

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH06339036A (ja) * 1993-05-28 1994-12-06 Mita Ind Co Ltd ファクシミリ装置の暗号化装置および暗号化方法
JP2001156767A (ja) * 1999-11-29 2001-06-08 Murata Mach Ltd 暗号通信方法及び暗号通信システム

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6834111B1 (en) * 1998-04-01 2004-12-21 Matsushita Electric Industrial Co., Ltd. Data transmitting/receiving method, data transmitter, data receiver, data transmitting/receiving system, av content transmitting method, av content receiving method, av content transmitter, av content receiver, and program recording medium

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH06339036A (ja) * 1993-05-28 1994-12-06 Mita Ind Co Ltd ファクシミリ装置の暗号化装置および暗号化方法
JP2001156767A (ja) * 1999-11-29 2001-06-08 Murata Mach Ltd 暗号通信方法及び暗号通信システム

Also Published As

Publication number Publication date
CN100362785C (zh) 2008-01-16
CN1553600A (zh) 2004-12-08

Similar Documents

Publication Publication Date Title
JP5288210B2 (ja) ネットワークでのユニキャスト鍵の管理方法およびマルチキャスト鍵の管理方法
US9520996B2 (en) Ciphering data for transmission in a network
EP1721409B1 (en) Method for managing traffic encryption key in wireless portable internet system and protocol configuration method thereof, and operation method of traffic encryption key state machine in subscriber station
KR101049021B1 (ko) 애드 혹 무선 네트워크의 노드들 간의 보안 연계 확립 방법 및 장치
JP4772776B2 (ja) 無線携帯インターネットシステムにおけるトラフィック暗号化キー管理方法及びそのプロトコル構成方法、そして、加入者端末でのトラフィック暗号化キー状態マシンの動作方法
WO2004107645A1 (fr) Procede de mise a jour d'une cle partagee
JP2011519510A (ja) 通信システムにおける暗号化キーを用いるブロードキャストサービスを提供する方法及び装置
EP1889399B1 (en) Method for managing group traffic encryption key in wireless portable internet system
US10382955B2 (en) Security method and system for supporting prose group communication or public safety in mobile communication
US20230179400A1 (en) Key management method and communication apparatus
JP2007515112A (ja) 放送サービスを送受信するための装置および方法
CN106888083B (zh) 物联网下组密钥生成方法及通信节点
CN101150396B (zh) 组播广播业务的密钥获取方法、网络及终端设备
WO2011072513A1 (zh) 交换设备间安全连接的建立方法及系统
JP2023550280A (ja) マルチキャスト暗号化鍵を分配するための方法及びデバイス
WO2009109133A1 (zh) 恢复连接的方法和装置
WO2005008949A1 (fr) Procede de mise a jour d'une cle partagee au sein d'un groupe de trafic en multidiffusion
CN105592433B (zh) 设备到设备限制发现业务广播、监听方法、装置及系统
WO2005006790A1 (en) Method for registering broadcast/multicast service in a high-rate packet data system
WO2010012148A1 (zh) 用于基于广播或多播进行安全通信的方法及其装置
CN116830533A (zh) 用于分发多播加密密钥的方法和设备
WO2008040242A1 (fr) Procédé, réseau et dispositif de terminal permettant d'obtenir une clé de service de multidiffusion/diffusion
JP2017201832A (ja) 通信制御装置及び通信装置
CN101521582A (zh) 一种组播数据的传输方法、装置及系统
WO2012055171A1 (zh) 通告式安全连接建立系统、方法及装置

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BW BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE EG ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NA NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SY TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): BW GH GM KE LS MW MZ NA SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LU MC NL PL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
122 Ep: pct application non-entry in european phase