WO2012155702A1 - 一种业务密钥更新的方法、系统及业务处理服务器 - Google Patents
一种业务密钥更新的方法、系统及业务处理服务器 Download PDFInfo
- Publication number
- WO2012155702A1 WO2012155702A1 PCT/CN2012/073256 CN2012073256W WO2012155702A1 WO 2012155702 A1 WO2012155702 A1 WO 2012155702A1 CN 2012073256 W CN2012073256 W CN 2012073256W WO 2012155702 A1 WO2012155702 A1 WO 2012155702A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- user terminal
- service key
- service
- sorting
- push
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
Definitions
- the present invention relates to the field of mobile multimedia broadcast services, and in particular, to a method, system, and service processing server for service key update. Background technique
- the Multimedia Broadcast Business Management System which is a mobile TV system, is a mobile TV service application system based on broadcast technology.
- MBBMS not only enables the use of broadcast-based video streams on mobile phones to be as popular as TV, but also makes the application of video streams on mobile phones operational and manageable.
- MBBMS needs to update the service key frequently.
- the user terminal with customized relationship needs to obtain the updated service key through the service key update process to realize its own service key and MBBMS.
- the business key is updated synchronously so that it can continue to use its customized mobile TV service.
- Step 1 The MBBMS generates an updated business key when the business key update time arrives.
- Step 2 The MBBMS determines that there is still a user terminal for an effective customized relationship for the mobile TV service after the service key update time.
- Step 3 The MBBMS pushes the service key update notification to the determined user terminal having a valid customized relationship in turn according to the customized relationship of each user terminal recorded in the customized list when the service key push time arrives.
- the service key update notification carries a service key identifier corresponding to the updated service key.
- Step 4 After receiving the service key update notification, the user terminal initiates the service key acquisition process by using the service key identifier carried in the service key update notification.
- Step 5 The user terminal obtains the updated service key and stores it locally. After the service key effective time arrives, the user terminal uses the updated service key to obtain the broadcast content.
- the period from the service key push time to the service key effective time may be referred to as a push validity period.
- the MBBMS pushes the updated service key to the user terminal in advance before the service key is valid.
- the advantage of the user is that the user terminal does not use the mobile phone service during the use of the mobile phone service.
- the service key is obtained from the MBBMS due to the update of the service key, which avoids large-scale system congestion and affects the normal use of the mobile TV service by the user terminal.
- the number of user terminals for custom mobile TV services is also increasing. If the number of user terminals for custom mobile TV services is greater than the number of user terminals that can be pushed by system resources during the push validity period, some will appear. The user terminal cannot receive the service key update notification correctly.
- the embodiment of the present invention provides a method, a system, and a service processing server for updating a service key, which can improve the effectiveness of service key push.
- a method for service key update comprising: Determining a user terminal having an effective customized relationship of the service when the service key update time arrives;
- the user terminal is sorted according to the service key acquisition request sent by the recorded user terminal according to the set duration before the service key push time arrives;
- the user terminal that has a valid customized relationship with the service pushes the service key update notification according to the sorting result, and indicates that the user terminal that received the service key update notification acquires the updated service key.
- the sorting the determined user terminals is:
- Each user terminal is sorted in descending order of activity.
- the determining, by the user terminal, the activity level of the service key request in the set duration is: the shorter the time from the last time the service key acquisition request is sent within the set duration, the shorter the service key push time
- the user terminal is set to be a user terminal with a higher degree of activity; or, the number of times the user terminal sends a service key acquisition request within the set duration is counted, and the number of times the service key acquisition request is sent is increased.
- User terminal set to a user terminal with higher activity; or
- the first sorting value and the second sorting value of each user terminal are weighted and summed to obtain an actual sorting value, and the active level is set for each user terminal according to the actual sorting value.
- the user terminal that has a valid customized relationship with the service pushes the service key update notification according to the sorting result: Determining the number N of user terminals that the system resource can support to push during the push validity period, where N is a positive integer;
- a system for service key update comprising:
- a service processing server configured to determine a user terminal having a valid customized relationship of the service when the service key update time arrives; the recorded service key sent by the user terminal according to a set time period before the service key push time arrives Obtaining a request, sorting the user terminal, and pushing a service key update notification according to the sorting result by the user terminal having a valid customized relationship of the service during the push validity period;
- At least one user terminal is configured to receive a service key update notification pushed by the service processing server, and obtain an updated service key according to the received service key update notification.
- the service processing server is specifically configured to determine the number N of user terminals that the system resources can support to push during the push validity period, and push the service key update notification to the top N user terminals according to the sorting result. Let N be a positive integer.
- a service processing server where the service processing server includes:
- a customization determining module configured to determine a user terminal that has an effective customized relationship of the service when the service key update time arrives;
- a sorting module configured to sort the user terminal according to a service key acquisition request sent by the recorded user terminal according to a set duration before the service key push time arrives; and a pushing module, used in the push validity period
- the user terminal that has an effective customized relationship with the service pushes the service key update notification according to the sort result.
- the sorting module is specifically configured to determine, according to the service key acquisition request sent by each user terminal in the set duration, the activity level of each user terminal requesting the service key in the set duration, and according to The user terminals are sorted in order of activity from high to low.
- the sorting module is specifically configured to be used for the last time in the set time period.
- the user terminal whose request key acquisition request is shorter than the service key push time is set as the user terminal with higher activity; or, for each user terminal to send the service key acquisition request within the set duration Counting the number of times, the user terminal that sends the service key acquisition request is set to the user terminal with the higher activity degree; or, according to the time when the service key acquisition request is last sent within the set time period
- Assigning a first sorting value to each user terminal according to the length of the service key pushing time, and assigning a second sorting value to each user terminal according to the number of times the user terminal sends the service key obtaining request within the set time period and
- the first sorting value and the second sorting value of each user terminal are weighted and summed to obtain an actual sorting value, and the active level is set for each user terminal according to the actual sorting value.
- the pushing module is specifically configured to determine the number N of user terminals that the system resources can support to push during the push validity period, and push the service key update notification to the N user terminals that are ranked according to the sorting result, where N is a positive integer.
- the embodiment of the present invention analyzes the behavior of the user terminal having the effective customized relationship of the service within the set duration before the service key push time arrives, sorts the user terminal according to the analysis result, and sorts according to the validity period of the push.
- the service key update notification is sequentially pushed to the user terminal, so that the user terminal having the service use requirement when the service key is updated can correctly receive the service key update notification during the push validity period, thereby avoiding the system due to the part of the user terminal. Focusing on the situation that the service key is obtained from the server when the service key update takes effect and congestion or crash occurs, which improves the effectiveness of the service key push.
- FIG. 1 is a schematic diagram of steps of a method for updating a service key according to Embodiment 1 of the present invention
- FIG. 2 is a schematic structural diagram of a system for updating a service key according to Embodiment 2 of the present invention
- FIG. 3 is a schematic diagram of a service processing server according to Embodiment 3 of the present invention. detailed description
- an embodiment of the present invention provides a method, a system, and a service processing server for service key update, which are provided before a service key push time arrives by a user terminal having an effective customized relationship with a service.
- the behavior within the time length is analyzed, that is, according to the situation that the user terminal requests to obtain the service key within the set duration, the user terminal is sorted according to the analysis result, and in the push validity period, the ranking result is sequentially
- the user terminal pushes the service key update notification, so that the user terminal having the service usage requirement when the service key is updated can correctly receive the service key update notification during the push validity period, thereby avoiding the system being concentrated in the service by the part of the user terminal.
- the service key takes effect, the service key is obtained from the server and congestion or crash occurs, which improves the effectiveness of the service key push.
- FIG. 1 it is a schematic diagram of a method for updating a service key in the first embodiment of the present invention, where the method specifically includes the following steps:
- Step 101 The service processing server records the service key acquisition request sent by each user terminal.
- the user terminal can perform information interaction with the service processing server through the mobile communication network during the use of the service, such as the mobile TV service. , get the current business key.
- the service processing server can receive and record the service key acquisition request sent by the user terminal in real time, and the service key acquisition request includes, but is not limited to, the user terminal identifier, the request time, and the service identifier corresponding to the request key.
- the service processing server may separately record service key requests sent by different user terminals each time.
- step 101 can be performed in real time, for example, can be continuously executed during the running process of the first embodiment, and the business confidentiality recorded in the service processing server can be performed in step 104.
- the key acquisition request is selectively used.
- Step 102 The service processing server generates an updated service key when the service key update time arrives.
- the service key update time may be a time when the service processing server confirms that the service key needs to be updated, and may be determined by the service operation provider.
- the service key update time should be earlier than the service time of the currently used service key, and should be earlier than the effective time of the updated service key.
- Step 103 The service processing server determines the user terminal that still has a valid customized relationship of the service when the service key update time arrives.
- Step 104 The service processing server determines, in the set duration before the service key push time arrives, the recorded service key acquisition request sent by the user terminal that still has a valid customized relationship of the service.
- Step 105 The service processing server sorts the user terminals of the valid customized relationship of the existing services according to the determined service key acquisition request sent by the user terminal that has the valid customized relationship of the service.
- the service processing server analyzes the service key acquisition request sent by the user terminal that has the effective customized relationship of the service, and determines the activity level of each user terminal for the service key request in the set duration.
- the user terminal with high activity ranks in front, and the user terminal with low activity ranks behind. This is because the user terminal with high activity needs to use the updated service key to perform the service after the service key is valid. The possibility is high. Therefore, in order to prevent the user terminal with high activity from being able to obtain the service key update notification during the push validity period, this step sorts the user terminals with high activity priority, and ensures that such user terminals can obtain business confidentiality. Key update notification.
- the activity of the user terminal may be determined in the following manner, and then sorted: The first way:
- the service processing server sorts the order of the request time, and the user terminal that sends the service key acquisition request is shorter than the service key push time. , set the user terminal with higher activity, and arrange it in front, and so on, sort each user terminal.
- the user terminal that sends the service key acquisition request is the user terminal with the shortest service key push time as the user terminal with the highest activity, as the user terminal ranked first, with the sending service key acquisition request
- the time from the service key push time is longer and longer, and the corresponding user terminal is ranked later.
- the service processing server When the service key acquisition request includes the user terminal identifier and the request time, the service processing server counts the number of times the user terminal initiates the service key acquisition request within the set duration, and sends the service key acquisition request. The more the number of user terminals, the higher the more active user terminals are arranged in front, and so on, the user terminals are sorted.
- the user terminal that sends the service key acquisition request the most times may be the user terminal with the highest activity as the user terminal ranked first, and the number of times the service key acquisition request is sent is less, corresponding to The user terminal is also ranked lower.
- the third sorting method is a third sorting method
- the service processing server When the service key acquisition request includes the user terminal identifier and the request time, the service processing server combines the first sorting manner and the second sorting manner, and the time when the user terminal sends the service key acquisition request and the user terminal The number of times the service key acquisition request is sent within the set duration is combined with the judgment basis of the activity level, that is, as a sorting basis.
- the service processing server may allocate the first sorting value to the user terminal of the effective customized relationship of each existing service according to the length of the service key to be sent according to the time when the service key acquisition request is sent, and according to the set duration The number of times the service key acquisition request is sent, for each purpose
- the user terminal allocates a second sort value, at which time, each of the user terminals that have a valid custom relationship of the service is assigned two sort values.
- the service processing server performs weighted summation on the two sorting values of each user terminal to obtain an actual sorting value of the user terminal, and sorts the user terminals according to the level of the actual sorting value.
- the first order value allocated by the user terminal is larger, and the number of times the service key acquisition request is sent within the set time period is larger.
- the larger the second sorting value assigned by the user terminal is, the more the user terminal with the actual sorting value is ranked higher.
- the solution of the embodiment of the present invention is not limited to the foregoing three sorting manners. Others can use the service key acquisition request sent by the user terminal to analyze the activity level of the user terminal, and determine that the user terminal is valid in the service key. After the time, various ways are needed to perform the business with the updated service key.
- the steps 102 to 105 are not performed in an orderly manner. In the solution of the embodiment, the steps 102 to 105 may be performed in an arbitrary order, or may be performed in any number of steps.
- Step 106 The service processing server pushes the service key update notification according to the sorting result by the user terminal that has the effective customized relationship of the service during the push validity period.
- the number of user terminals that have an effective custom relationship of the service may be greater than the number of user terminals that can be pushed by the system resources during the push validity period.
- the user who has an effective customized relationship with the service may be used.
- the service key update notification is preferentially pushed to the user terminal that can support the system resource during the push validity period.
- the number of user terminals that need to push the service key update notification in step 105 is M, but the threshold of the number of user terminals that can be pushed by the system resource during the push validity period is N, and the M is greater than N, then the preferred solution of this step is Yes: Sort the first N user terminals in step 105 Push the business key update notification according to the sort result.
- the M and N are positive integers.
- Step 107 After receiving the service key update notification, the user terminal initiates the service key acquisition process by using the service key identifier carried therein.
- Step 108 The user terminal obtains the updated service key and stores it locally. After the service key effective time arrives, the user terminal can directly use the updated service key to obtain the broadcast content.
- the user terminal may perform the service transmission with the service processing server by using the updated service key, where the service may be a broadcast service, that is, the user terminal may directly use the updated service key to obtain the broadcast content.
- the solution of the first embodiment can be applied to the multimedia service.
- the service processing server involved in the first embodiment may be a network application function (NAF).
- NAF network application function
- the solution of the first embodiment is especially applicable to the multimedia broadcast service system. If the solution of the first embodiment is applied to the multimedia broadcast service system, the service processing server involved in the first embodiment may be an MBBMS.
- the solution of the first embodiment of the present invention analyzes the service key acquisition request sent by the user terminal within the set duration, and sorts the user terminals that determine the effective customized relationship of the service according to the activity level of the user terminal, so that the user terminal is active.
- the user terminal with high degree can obtain the service key update notification preferentially, which improves the validity and purpose of the service key update notification push, and avoids the system from the business process when the user terminal with high activity is concentrated when the service key update is effective.
- the system resource can be pushed according to the push validity period.
- the threshold of the number of user terminals is pushed to avoid the occurrence of packet loss in the pushed service key update notification.
- FIG. 1 it is a schematic structural diagram of a system for updating a service key in Embodiment 2 of the present invention.
- the service key update system includes: a service processing server 21 and at least one user terminal 22. among them:
- the service processing server 21 has two main functions, one is to generate and store the service key, and the other is to control the push of the service key, which will be separately described below.
- the service processing server 21 is configured to determine a user terminal that has a valid customized relationship of the service when the service key update time arrives, and sends the recorded user terminal according to the set time period before the service key push time arrives.
- the user terminal 22 is configured to receive a service key update notification pushed by the service processing server 21, and obtain an updated service key according to the received service key update notification.
- the service processing server 21 is configured to determine, according to the service key acquisition request sent by the user terminal 11 within the set duration, the activity level of each user terminal 22 for the service key request in the set duration, and The user terminals 22 are sorted in descending order of activity.
- the service processing server 21 is configured to set, as a user terminal with a shorter activity time, a service terminal with a shorter service time to send the service key acquisition request for the last time in the set time period, or a user terminal with a higher activity level, or Counting the number of times that each user terminal sends a service key acquisition request within the set duration, and setting the user terminal that transmits the service key acquisition request to a user terminal with a higher activity level, or And assigning a first sorting value to each user terminal according to the length of the last time the service key acquisition request is sent in the set time period, and transmitting the service according to the user terminal in the set time period.
- the number of times of the key acquisition request, the second sort value is assigned to each user terminal, and the first sort value and the second sort value of each user terminal are weighted and summed to obtain an actual sort value, and the actual sort value is the user.
- the terminal sets the activity level.
- the service processing server 21 is specifically configured to determine that system resources can be valid during the push period Supporting the number N of pushed user terminals, and pushing the service key update notification to the top N user terminals according to the sort result, the N being a positive integer.
- the service processing server 21 is further configured to process the service key acquisition request of the user terminal, store the service key acquisition request sent by the at least one user terminal 22 through the mobile communication network, and the service customization relationship of the user terminal, and generate the updated information when needed. Business key.
- the user terminal 22 is further configured to send a service key acquisition request to the service processing server 21 and store the obtained updated service key.
- the service key update system can be used in a multimedia broadcast service system.
- FIG. 3 it is a schematic diagram of a service processing server in Embodiment 3 of the present invention, where the service processing server includes: a customization determining module 31, a sorting module 32, and a pushing module 33.
- a customization determining module 31 configured to determine a user terminal that has an effective customized relationship of the service when the service key update time arrives;
- the sorting module 32 is configured to sort the user terminal according to the recorded service key acquisition request sent by the user terminal, according to the set duration before the service key push time arrives;
- the pushing module 33 is configured to push the service key update notification to the user terminal sequentially according to the sorting result of the sorting module 32 in the push validity period.
- the sorting module 32 is specifically configured to determine, according to the service key acquisition request sent by the user terminal in the set duration, the activity level of each user terminal requesting the service key in the set duration, and according to The user terminals are sorted in descending order of activity.
- the sorting module 32 is specifically configured to set the user terminal with the shorter time of the service key acquisition request to be sent for the last time the service key acquisition request is set to be active.
- User terminal or,
- the user terminal that transmits the service key acquisition request is set to be the user terminal with higher activity
- the terminal sets the activity level.
- the pushing module 33 is specifically configured to determine the number N of user terminals that the system resource can support to push during the push validity period, and push the service key update notification to the N user terminals that are arranged in advance according to the sorting result, where the N Is a positive integer.
- the service processing server further includes: a storage module 30, configured to store a service customization relationship and service key acquisition request information of the user terminal.
- the customization determining module 31 is configured to determine, from the storage module 30, a user terminal that has an effective customized relationship of the service when the service key update time arrives.
- the ranking module 32 can determine the user terminals that need to be sorted from the customization determination module 31, and can determine the service key acquisition request information of the user terminals that need to be sorted from the storage module 30.
- the service processing server further includes: a request processing module 34, configured to process a service key acquisition request of the user terminal, and store the information carried in the service key acquisition request into the storage module 30.
- a request processing module 34 configured to process a service key acquisition request of the user terminal, and store the information carried in the service key acquisition request into the storage module 30.
- the service processing server in this embodiment further has logic components capable of implementing the features of the first embodiment to the second embodiment, and details are not described herein again.
- the method, the system and the service key processing apparatus for updating the service key improve the validity and purpose of the push service key update notification when the service key is updated, and improve the use of the service by the system for the user terminal. Perception, reduces system appearance when business key updates The possibility of congestion and collapse.
- embodiments of the present application can be provided as a method, system, or computer program product.
- the application can take the form of an entirely hardware embodiment, an entirely software embodiment, or a combination of software and hardware.
- the application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.
- the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
- the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
- These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
- the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.
Landscapes
- Engineering & Computer Science (AREA)
- Multimedia (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Telephonic Communication Services (AREA)
Abstract
摘要本发明实施例提供一种业务密钥更新的方法、系统及业务处理服务器，所述方法包括：确定在业务密钥更新时间到达时存在业务的有效定制关系的用户终端；根据在业务密钥推送时间到达之前的设定时长内，已记录的用户终端发送的业务密钥获取请求，对所述用户终端进行排序；在推送有效期内，对存在业务的有效定制关系的用户终端按照排序结果推送业务密钥更新通知，指示接收到业务密钥更新通知的用户终端获取更新后的业务密钥。本发明提高了业务密钥更新时推送业务密钥更新通知的有效性和目的性，避免了系统因这部分用户终端集中在业务密钥更新生效时从服务器处获取业务密钥而出现拥塞或崩溃的情况，提高了业务密钥推送的有效性。
Description
一种业务密钥更新的方法、 系统及业务处理服务器 技术领域
本发明涉及移动多媒体广播业务领域， 尤其涉及一种业务密钥更新的 方法、 系统及业务处理服务器。 背景技术
多媒体广播业务管理系统 ( Multimedia Broadcast Business Management System, MBBMS )即手机电视系统， 是基于广播技术的手机电视业务应用 系统。 MBBMS 不仅能使基于广播方式播出的视频流在手机上的应用像电 视那样普及， 同时还能使视频流在手机上的应用变得可运营、 可管理。 为 保证手机电视业务内容的安全性， MBBMS 需经常更新业务密钥， 同时， 具有定制关系的用户终端需通过业务密钥更新流程获取已更新的业务密钥 来实现其自身的业务密钥与 MBBMS的业务密钥的同步更新， 以便能继续 使用其定制的手机电视业务。
在现有技术中， 实现业务密钥更新的流程如下：
第一步： MBBMS 在业务密钥更新时间到达时， 生成更新后的业务密 钥。
第二步： MBBMS确定业务密钥更新时间后仍存在针对手机电视业务 的有效定制关系的用户终端。
第三步： MBBMS根据定制列表中记录的各用户终端的定制关系， 在 业务密钥推送时间到达时， 依次向所述确定的具有有效定制关系的用户终 端推送业务密钥更新通知。
所述业务密钥更新通知中携带有与更新后的业务密钥对应的业务密钥 标识。
第四步： 用户终端在接收到业务密钥更新通知后， 利用业务密钥更新 通知中携带的业务密钥标识， 发起业务密钥获取流程。
第五步： 用户终端获取更新后的业务密钥并存储在本地， 在业务密钥 生效时间到达后， 用户终端使用更新后的业务密钥， 获取广播内容。
上述第一步至第五步的方案中， 从业务密钥推送时间至业务密钥生效 时间的这段时间可称之为推送有效期。
在上述业务密钥更新的流程中， MBBMS 在业务密钥生效时间到达之 前， 提前向用户终端推送更新后的业务密钥， 这样做的好处是： 用户终端 在手机电视业务的使用过程中， 不会因为业务密钥更新而出现集中从 MBBMS 获取业务密钥的情况， 避免出现大规模的系统拥塞， 影响用户终 端正常使用手机电视业务。
但是， 随着手机电视业务的不断普及， 定制手机电视业务的用户终端 数量也不断增加， 若定制手机电视业务的用户终端数量大于在推送有效期 内系统资源能够推送的用户终端数量， 则会出现部分用户终端无法正确接 收业务密钥更新通知的情况。
如果按照上述业务密钥更新的流程中规定的以用户终端定制手机电视 业务的定制关系来推送业务密钥更新通知， 则可能出现部分有业务使用需 求的用户终端无法正确接收到业务密钥更新通知， 导致这部分用户终端只 能在业务密钥生效时间到达时， 集中从 MBBMS获取密钥， 可能出现系统 拥塞或崩溃， 因此， 目前的业务密钥更新流程中， 业务密钥推送的有效性 低。 发明内容
有鉴于此， 本发明实施例提供一种业务密钥更新的方法、 系统及业务 处理服务器， 能够提高业务密钥推送的有效性。
一种业务密钥更新的方法， 所述方法包括：
确定在业务密钥更新时间到达时存在业务的有效定制关系的用户终 端；
根据在业务密钥推送时间到达之前的设定时长内， 已记录的用户终端 发送的业务密钥获取请求， 对所述用户终端进行排序；
在推送有效期内， 对存在业务的有效定制关系的用户终端按照排序结 果推送业务密钥更新通知， 指示接收到业务密钥更新通知的用户终端获取 更新后的业务密钥。
其中， 所述对所述确定的用户终端进行排序为：
根据在所述设定时长内各用户终端发送的业务密钥获取请求， 确定各 用户终端在所述设定时长对业务密钥请求的活跃度；
按照活跃度由高至低的顺序对各用户终端进行排序。
其中， 所述确定用户终端在所述设定时长对业务密钥请求的活跃度为： 将在所述设定时长内最后一次发送业务密钥获取请求的时间距离业务 密钥推送时间越短的用户终端， 设定为活跃度越高的用户终端； 或者， 对在所述设定时长内各用户终端发送业务密钥获取请求的次数进行统 计， 将发送业务密钥获取请求的次数越多的用户终端， 设定为活跃度越高 的用户终端； 或者，
根据在所述设定时长内最后一次发送业务密钥获取请求的时间距离业 务密钥推送时间的长短， 为各用户终端分配第一排序值；
根据在所述设定时长内用户终端发送业务密钥获取请求的次数， 为各 用户终端分配第二排序值；
为各用户终端的第一排序值和第二排序值进行加权求和， 得到实际排 序值， 并按照所述实际排序值为各用户终端设定活跃度。
其中， 所述对存在业务的有效定制关系的用户终端按照排序结果推送 业务密钥更新通知为：
确定在推送有效期内系统资源能够支持推送的用户终端的数量 N, 所 述 N为正整数；
按照排序结果， 向排列在前的 N个用户终端推送业务密钥更新通知。 一种业务密钥更新的系统， 包括：
业务处理服务器， 用于确定在业务密钥更新时间到达时存在业务的有 效定制关系的用户终端； 根据在业务密钥推送时间到达之前的设定时长内， 已记录的用户终端发送的业务密钥获取请求， 对所述用户终端进行排序， 并在推送有效期内， 对存在业务的有效定制关系的用户终端按照排序结果 推送业务密钥更新通知；
至少一个用户终端， 用于接收业务处理服务器推送的业务密钥更新通 知， 并根据接收到业务密钥更新通知获取更新后的业务密钥。
其中， 所述业务处理服务器， 具体用于确定在推送有效期内系统资源 能够支持推送的用户终端的数量 N, 并按照排序结果， 向排列在前的 N个 用户终端推送业务密钥更新通知， 所述 N为正整数。
一种业务处理服务器， 所述业务处理服务器包括：
定制确定模块， 用于确定在业务密钥更新时间到达时存在业务的有效 定制关系的用户终端；
排序模块， 用于根据在业务密钥推送时间到达之前的设定时长内， 已 记录的用户终端发送的业务密钥获取请求， 对所述用户终端进行排序； 推送模块， 用于在推送有效期内， 对存在业务的有效定制关系的用户 终端按照排序结果推送业务密钥更新通知。
其中， 所述排序模块， 具体用于根据在所述设定时长内各用户终端发 送的业务密钥获取请求， 确定各用户终端在所述设定时长对业务密钥请求 的活跃度， 并按照活跃度由高至低的顺序对各用户终端进行排序。
其中， 所述排序模块， 具体用于将在所述设定时长内最后一次发送业
务密钥获取请求的时间距离业务密钥推送时间越短的用户终端， 设定为活 跃度越高的用户终端； 或者， 对在所述设定时长内各用户终端发送业务密 钥获取请求的次数进行统计， 将发送业务密钥获取请求的次数越多的用户 终端， 设定为活跃度越高的用户终端； 或者， 根据在所述设定时长内最后 一次发送业务密钥获取请求的时间距离业务密钥推送时间的长短， 为各用 户终端分配第一排序值， 并根据在所述设定时长内用户终端发送业务密钥 获取请求的次数， 为各用户终端分配第二排序值， 以及为各用户终端的第 一排序值和第二排序值进行加权求和， 得到实际排序值， 并按照所述该实 际排序值为各用户终端设定活跃度。
其中， 所述推送模块， 具体用于确定在推送有效期内系统资源能够支 持推送的用户终端的数量 N, 并按照排序结果， 向排列在前的 N个用户终 端推送业务密钥更新通知， 所述 N为正整数。
本发明实施例通过对具有业务的有效定制关系的用户终端在业务密钥 推送时间到达之前的设定时长内的行为进行分析， 根据分析结果对用户终 端进行排序， 并在推送有效期内， 按照排序结果依次向用户终端推送业务 密钥更新通知， 使得在业务密钥更新时有业务使用需求的用户终端可以在 所述推送有效期内正确接收到业务密钥更新通知， 避免了系统因这部分用 户终端集中在业务密钥更新生效时从服务器处获取业务密钥而出现拥塞或 崩溃的情况， 提高了业务密钥推送的有效性。 附图说明
图 1为本发明实施例一中业务密钥更新的方法步驟示意图；
图 2为本发明实施例二中业务密钥更新的系统结构示意图；
图 3为本发明实施例三中业务处理服务器示意图。
具体实施方式
为了解决本发明提出的技术问题， 本发明实施例提出一种业务密钥更 新的方法、 系统及业务处理服务器， 通过对具有业务的有效定制关系的用 户终端在业务密钥推送时间到达之前的设定时长内的行为进行分析， 也即 根据用户终端在所述设定时长内请求获取业务密钥的情况进行分析， 根据 分析结果对用户终端进行排序， 并在推送有效期内， 按照排序结果依次向 用户终端推送业务密钥更新通知， 使得在业务密钥更新时有业务使用需求 的用户终端可以在所述推送有效期内正确接收到业务密钥更新通知， 避免 了系统因这部分用户终端集中在业务密钥更新生效时从服务器处获取业务 密钥而出现拥塞或崩溃的情况， 提高了业务密钥推送的有效性。
下面结合具体实施例详细描述本发明方案。
实施例一
如图 1 所示， 为本发明实施例一中业务密钥更新的方法步驟示意图， 所述方法具体包括以下步驟：
步驟 101 : 业务处理服务器记录各用户终端发送的业务密钥获取请求； 在本步驟中， 用户终端可以在业务， 如手机电视业务的使用过程中， 通过移动通信网络， 与业务处理服务器进行信息交互， 获取当前的业务密 钥。
业务处理服务器可以实时接收并记录用户终端发送的业务密钥获取请 求， 所述业务密钥获取请求包括但不限于： 用户终端标识、 请求时间、 请 求密钥对应的业务标识。
所述业务处理服务器可以分别记录不同的用户终端每次发送的业务密 钥请求。
需要说明的是， 本步驟 101 可以实时执行， 如可以在本实施例一的运 行过程中不断执行， 在步驟 104 中可以对业务处理服务器内记录的业务密
钥获取请求选择性地使用。
步驟 102: 业务处理服务器在业务密钥更新时间到达时， 生成更新后的 业务密钥。
所述业务密钥更新时间可以是业务处理服务器确认需要对业务密钥进 行更新的时间， 可由业务运营提供商确定。
需要说明的是， 所述业务密钥更新时间应早于当前使用的业务密钥的 失效时间， 也应早于更新后的业务密钥的生效时间。
步驟 103 :业务处理服务器确定业务密钥更新时间到达时仍存在业务的 有效定制关系的用户终端。
步驟 104:业务处理服务器确定业务密钥推送时间到达之前的设定时长 内， 已记录的所述仍存在业务的有效定制关系的用户终端发送的业务密钥 获取请求。
步驟 105:业务处理服务器根据确定的存在业务的有效定制关系的用户 终端发送的业务密钥获取请求， 对所述存在业务的有效定制关系的用户终 端进行排序。
在本步驟的方案中， 业务处理服务器对存在业务的有效定制关系的用 户终端发送的业务密钥获取请求进行分析， 确定各用户终端在所述设定时 长对业务密钥请求的活跃度， 将活跃度高的用户终端排在前面， 将活跃度 低的用户终端排在后面， 这是因为， 活跃度高的用户终端在业务密钥生效 时间后， 需要利用更新后的业务密钥执行业务的可能性高， 因此， 为了避 免活跃度高的用户终端不能在推送有效期内获得业务密钥更新通知的情 况， 本步驟将活跃度高的用户终端排序在前， 确保这类用户终端能获得业 务密钥更新通知。
具体地， 本步驟可以按照以下方式确定用户终端的活跃度， 进而进行 排序：
第一种方式：
在所述业务密钥获取请求中包含用户终端标识和请求时间时， 业务处 理服务器对请求时间的先后顺序进行排序， 将发送业务密钥获取请求的时 间距离业务密钥推送时间越短的用户终端， 设定为活跃度越高的用户终端， 并排列在前， 以此类推， 对各用户终端进行排序。
具体地， 可将发送业务密钥获取请求的时间是距离业务密钥推送时间 最短的用户终端作为活跃度最高的用户终端， 作为排序在第一位的用户终 端， 随着发送业务密钥获取请求的时间距离业务密钥推送时间越来越长， 对应的用户终端排序也越靠后。
第二种方式：
在所述业务密钥获取请求中包含用户终端标识和请求时间时， 业务处 理服务器对在设定时长内， 各用户终端发起业务密钥获取请求的次数进行 统计， 将发送业务密钥获取请求的次数越多的用户终端， 设定为活跃度越 高的用户终端并排列在前， 以此类推， 对各用户终端进行排序。
具体地， 可将发送业务密钥获取请求的次数最多的用户终端作为活跃 度最高的用户终端， 作为排序在第一位的用户终端， 随着发送业务密钥获 取请求的次数越少， 对应的用户终端排序也越靠后。
第三种排序方式：
在所述业务密钥获取请求中包含用户终端标识和请求时间时， 业务处 理服务器结合第一种排序方式和第二种排序方式， 将用户终端发送业务密 钥获取请求的时间和用户终端在所述设定时长内发送业务密钥获取请求的 次数结合作为活跃度的判断依据， 也即作为排序依据。
较优的， 业务处理服务器可按照发送业务密钥获取请求的时间距离业 务密钥推送时间长短， 为各存在业务的有效定制关系的用户终端分配第一 排序值， 并按照在所述设定时长内发送业务密钥获取请求的次数， 为各用
户终端分配第二排序值， 此时， 每个存在业务的有效定制关系的用户终端 被分配的两个排序值。 业务处理服务器对各用户终端的两个排序值进行加 权求和， 得到该用户终端的实际排序值， 并按照该实际排序值的高低， 为 用户终端进行排序。
例如， 若发送业务密钥获取请求的时间距离业务密钥推送时间越短， 用户终端分配的的第一排序值越大， 在所述设定时长内发送业务密钥获取 请求的次数越多， 用户终端分配的的第二排序值越大， 则实际排序值越大 的用户终端， 排列越靠前。
需要说明的是， 本发明实施例的方案并不限于上述三种排序方式， 其 他能够利用用户终端发送的业务密钥获取请求， 对用户终端的活跃度进行 分析， 确定用户终端在业务密钥生效时间后， 需要利用更新后的业务密钥 执行业务的可能性的各种方式都可。
所述步驟 102〜步驟 105没有必然的顺序执行关系， 本实施例的方案中 可以将步驟 102〜步驟 105按照任意排列顺序执行， 也可以任意多个步驟并 行执行。
步驟 106: 业务处理服务器在推送有效期内，对存在业务的有效定制关 系的用户终端按照排序结果推送业务密钥更新通知。
较优地， 考虑到存在业务的有效定制关系的用户终端数量可能大于在 推送有效期内系统资源能够推送的用户终端数量的情况， 在本步驟的方案 中， 可以对存在业务的有效定制关系的用户终端进行排序后， 按照该排序 顺序， 优先向在推送有效期内系统资源能够支持数量的用户终端推送业务 密钥更新通知。
例如：在步驟 105中需要推送业务密钥更新通知的用户终端数量为 M, 但在推送有效期内系统资源能够推送的用户终端数量的阈值为 N, 所述 M 大于 N, 则本步驟的优选方案是： 向步驟 105中排序在前的 N个用户终端
按照排序结果推送业务密钥更新通知。 所述 M和 N为正整数。
步驟 107: 用户终端在接收到业务密钥更新通知后， 利用其中携带的业 务密钥标识， 发起业务密钥获取流程。
步驟 108: 用户终端获取更新后的业务密钥并存储在本地， 在业务密钥 生效时间到达后， 用户终端可以直接使用所述更新后的业务密钥获取广播 内容。
本步驟 108 中， 用户终端可以与业务处理服务器之间通过更新后的业 务密钥进行业务传输， 所述业务可以是广播业务， 即用户终端可以直接使 用所述更新后的业务密钥获取广播内容。
本实施例一的方案可以应用在多媒体业务中， 实施例一中涉及的业务 处理服务器可以是网络应用功能实体（ Network Application Function, NAF )。 本实施例一的方案尤其可用于多媒体广播业务系统中， 若本实施例一的方 案应用于多媒体广播业务系统， 则本实施例一中涉及的业务处理服务器可 以是 MBBMS。
本发明实施例一的方案根据用户终端在所述设定时长内发送的业务密 钥获取请求进行分析， 按照用户终端的活跃度， 对确定存在业务的有效定 制关系的用户终端进行排序， 使活跃度高的用户终端能够优先获得业务密 钥更新通知， 提高了业务密钥更新通知推送的有效性和目的性， 避免了系 统因活跃度高的用户终端集中在业务密钥更新生效时从业务处理服务器处 获取更新后的业务密钥而出现拥塞或崩溃的情况； 较优地， 本实施例一的 方案中， 在向用户终端推送业务密钥更新通知时， 按照推送有效期内系统 资源能够推送的用户终端数量的阈值进行推送， 避免出现推送的业务密钥 更新通知出现丟包的情况。
实施例二
如图 1所示， 为本发明实施例二中业务密钥更新的系统结构示意图，
所述业务密钥更新系统包括： 业务处理服务器 21和至少一个用户终端 22。 其中：
业务处理服务器 21有两大主要功能， 一方面是生成并存储业务密钥， 另一方面是对业务密钥的推送进行控制， 下面分别予以说明。
业务处理服务器 21 , 用于确定在业务密钥更新时间到达时存在业务的 有效定制关系的用户终端， 并根据在业务密钥推送时间到达之前的设定时 长内， 已记录的所述用户终端发送的业务密钥获取请求， 对所述用户终端 进行排序， 以及， 在推送有效期内， 对存在业务的有效定制关系的用户终 端按照排序结果推送业务密钥更新通知；
用户终端 22, 用于接收业务处理服务器 21推送的业务密钥更新通知， 并根据接收到业务密钥更新通知获取更新后的业务密钥。
业务处理服务器 21 , 具体用于根据在所述设定时长内所述用户终端 11 发送的业务密钥获取请求， 确定各用户终端 22在所述设定时长对业务密钥 请求的活跃度， 并按照活跃度由高至低的顺序对用户终端 22进行排序。
业务处理服务器 21 , 具体用于将在所述设定时长内最后一次发送业务 密钥获取请求的时间距离业务密钥推送时间越短的用户终端设定为活跃度 越高的用户终端， 或者， 对在所述设定时长内各用户终端发送业务密钥获 取请求的次数进行统计， 将发送业务密钥获取请求的次数越多的用户终端， 设定为活跃度越高的用户终端， 或者， 根据在所述设定时长内最后一次发 送业务密钥获取请求的时间距离业务密钥推送时间的长短， 为各用户终端 分配第一排序值， 并根据在所述设定时长内用户终端发送业务密钥获取请 求的次数， 为各用户终端分配第二排序值， 以及为各用户终端的第一排序 值和第二排序值进行加权求和， 得到实际排序值， 并按照该实际排序值为 用户终端设定活跃度。
所述业务处理服务器 21 , 具体用于确定在推送有效期内系统资源能够
支持推送的用户终端的数量 N, 以及按照排序结果， 向排列在前的 N个用 户终端推送业务密钥更新通知， 所述 N为正整数。
业务处理服务器 21 , 还可用于处理用户终端的业务密钥获取请求、 存 储至少一个用户终端 22通过移动通信网络发送的业务密钥获取请求及用户 终端的业务定制关系、 在需要时生成更新后的业务密钥。
用户终端 22, 还可用于向业务处理服务器 21发送业务密钥获取请求、 存储获取的更新后的业务密钥。
所述业务密钥更新系统可以用于多媒体广播业务系统。
实施例三
如图 3 所示， 为本发明实施例三中业务处理服务器示意图， 所述业务 处理服务器包括： 定制确定模块 31、 排序模块 32和推送模块 33。 其中： 定制确定模块 31 , 用于确定在业务密钥更新时间到达时存在业务的有 效定制关系的用户终端；
排序模块 32 , 用于根据在业务密钥推送时间到达之前的设定时长内， 已记录的所述用户终端发送的业务密钥获取请求， 对所述用户终端进行排 序；
推送模块 33 , 用于根据排序模块 32的排序结果， 在推送有效期内， 顺 序向用户终端推送业务密钥更新通知。
所述排序模块 32, 具体用于根据在所述设定时长内所述用户终端发送 的业务密钥获取请求， 确定各用户终端在所述设定时长对业务密钥请求的 活跃度， 并按照活跃度由高至低的顺序对用户终端进行排序。
具体地， 所述排序模块 32, 具体用于将在所述设定时长内最后一次发 送业务密钥获取请求的时间距离业务密钥推送时间越短的用户终端， 设定 为活跃度越高的用户终端； 或者，
对在所述设定时长内各用户终端发送业务密钥获取请求的次数进行统
计， 将发送业务密钥获取请求的次数越多的用户终端， 设定为活跃度越高 的用户终端； 或者，
根据在所述设定时长内最后一次发送业务密钥获取请求的时间距离业 务密钥推送时间的长短， 为各用户终端分配第一排序值， 并根据在所述设 定时长内用户终端发送业务密钥获取请求的次数， 为各用户终端分配第二 排序值， 以及为各用户终端的第一排序值和第二排序值进行加权求和， 得 到实际排序值， 并按照该实际排序值为用户终端设定活跃度。
所述推送模块 33 , 具体用于确定在推送有效期内系统资源能够支持推 送的用户终端的数量 N, 并按照排序结果， 向排列在前的 N个用户终端推 送业务密钥更新通知， 所述 N为正整数。
所述业务处理服务器还包括： 存储模块 30, 用于存储用户终端的业务 定制关系和业务密钥获取请求信息。
定制确定模块 31 ,用于从存储模块 30中确定在业务密钥更新时间到达 时存在业务的有效定制关系的用户终端。
排序模块 32可以从定制确定模块 31确定需要进行排序的用户终端， 以及， 可以从存储模块 30中确定需要进行排序的用户终端的业务密钥获取 请求信息。
所述业务处理服务器还包括： 请求处理模块 34, 用于处理用户终端的 业务密钥获取请求， 并将业务密钥获取请求中携带的信息存储至存储模块 30中。
本实施例中的业务处理服务器还具有能够实现实施例一至实施例二各 特征的逻辑部件， 此处不再赘述。
通过本发明实施例描述的业务密钥更新的方法、 系统及业务密钥处理 装置， 提高了业务密钥更新时推送业务密钥更新通知的有效性和目的性， 提高了系统对用户终端使用业务的感知， 减小了业务密钥更新时系统出现
拥塞和崩溃的可能性。
本领域内的技术人员应明白， 本申请的实施例可提供为方法、 系统、 或计算机程序产品。 因此， 本申请可采用完全硬件实施例、 完全软件实施 例、 或结合软件和硬件方面的实施例的形式。 而且， 本申请可采用在一个 或多个其中包含有计算机可用程序代码的计算机可用存储介质 (包括但不 限于磁盘存储器、 CD-ROM、 光学存储器等）上实施的计算机程序产品的 形式。
本申请是参照根据本申请实施例的方法、 设备（系统）、 和计算机程序 产品的流程图和 /或方框图来描述的。 应理解可由计算机程序指令实现流 程图和 /或方框图中的每一流程和 /或方框、 以及流程图和 /或方框图中 的流程和 /或方框的结合。 可提供这些计算机程序指令到通用计算机、 专 机器， 使得通过计算机或其他可编程数据处理设备的处理器执行的指令产 生用于实现在流程图一个流程或多个流程和 /或方框图一个方框或多个方 框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理 设备以特定方式工作的计算机可读存储器中， 使得存储在该计算机可读存 储器中的指令产生包括指令装置的制造品， 该指令装置实现在流程图一个 流程或多个流程和 /或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备 上， 使得在计算机或其他可编程设备上执行一系列操作步驟以产生计算机 实现的处理， 从而在计算机或其他可编程设备上执行的指令提供用于实现 在流程图一个流程或多个流程和 /或方框图一个方框或多个方框中指定的 功能的步驟。
尽管已描述了本申请的优选实施例， 但本领域内的技术人员一旦得知
了基本创造性概念， 则可对这些实施例做出另外的变更和修改。 所以， 所 附权利要求意欲解释为包括优选实施例以及落入本申请范围的所有变更和 修改。
显然， 本领域的技术人员可以对本发明进行各种改动和变型而不脱离 本发明的精神和范围。 这样， 倘若本发明的这些修改和变型属于本发明权 利要求及其等同技术的范围之内， 则本发明也意图包含这些改动和变型在 内。
Claims
1、 一种业务密钥更新的方法， 其特征在于， 所述方法包括： 确定在业务密钥更新时间到达时存在业务的有效定制关系的用户终 端；
根据在业务密钥推送时间到达之前的设定时长内， 已记录的用户终端 发送的业务密钥获取请求， 对所述用户终端进行排序；
在推送有效期内， 对存在业务的有效定制关系的用户终端按照排序结 果推送业务密钥更新通知， 指示接收到业务密钥更新通知的用户终端获取 更新后的业务密钥。
2、 如权利要求 1所述的业务密钥更新的方法， 其特征在于， 所述对所 述用户终端进行排序为：
根据在所述设定时长内各用户终端发送的业务密钥获取请求， 确定各 用户终端在所述设定时长对业务密钥请求的活跃度；
按照活跃度由高至低的顺序对各用户终端进行排序。
3、 如权利要求 2所述的业务密钥更新的方法， 其特征在于， 所述确定 用户终端在所述设定时长对业务密钥请求的活跃度为：
将在所述设定时长内最后一次发送业务密钥获取请求的时间距离业务 密钥推送时间越短的用户终端， 设定为活跃度越高的用户终端； 或者， 对在所述设定时长内各用户终端发送业务密钥获取请求的次数进行统 计， 将发送业务密钥获取请求的次数越多的用户终端， 设定为活跃度越高 的用户终端； 或者，
根据在所述设定时长内最后一次发送业务密钥获取请求的时间距离业 务密钥推送时间的长短， 为各用户终端分配第一排序值；
根据在所述设定时长内用户终端发送业务密钥获取请求的次数， 为各 用户终端分配第二排序值； 为各用户终端的第一排序值和第二排序值进行加权求和， 得到实际排 序值， 并按照所述实际排序值为各用户终端设定活跃度。
4、如权利要求 1至 3任一项所述的业务密钥更新的方法，其特征在于， 所述对存在业务的有效定制关系的用户终端按照排序结果推送业务密钥更 新通知为：
确定在推送有效期内系统资源能够支持推送的用户终端的数量 N, 所 述 N为正整数；
按照排序结果， 向排列在前的 N个用户终端推送业务密钥更新通知。
5、 一种业务密钥更新的系统， 其特征在于， 所述系统包括：
业务处理服务器， 用于确定在业务密钥更新时间到达时存在业务的有 效定制关系的用户终端； 根据在业务密钥推送时间到达之前的设定时长内， 已记录的用户终端发送的业务密钥获取请求， 对所述用户终端进行排序， 并在推送有效期内， 对存在业务的有效定制关系的用户终端按照排序结果 推送业务密钥更新通知；
至少一个用户终端， 用于接收业务处理服务器推送的业务密钥更新通 知， 并根据接收到业务密钥更新通知获取更新后的业务密钥。
6、 如权利要求 5所述的业务密钥更新的系统， 其特征在于，
所述业务处理服务器， 具体用于确定在推送有效期内系统资源能够支 持推送的用户终端的数量 N, 并按照排序结果， 向排列在前的 N个用户终 端推送业务密钥更新通知， 所述 N为正整数。
7、 一种业务处理服务器， 其特征在于， 所述业务处理服务器包括： 定制确定模块， 用于确定在业务密钥更新时间到达时存在业务的有效 定制关系的用户终端；
排序模块， 用于根据在业务密钥推送时间到达之前的设定时长内， 已 记录的用户终端发送的业务密钥获取请求， 对所述用户终端进行排序； 推送模块， 用于在推送有效期内， 对存在业务的有效定制关系的用户 终端按照排序结果推送业务密钥更新通知。
8、 如权利要求 7所述的业务处理服务器， 其特征在于，
所述排序模块， 具体用于根据在所述设定时长内各用户终端发送的业 务密钥获取请求， 确定各用户终端在所述设定时长对业务密钥请求的活跃 度， 并按照活跃度由高至低的顺序对各用户终端进行排序。
9、 如权利要求 8所述的业务处理服务器， 其特征在于，
所述排序模块， 具体用于将在所述设定时长内最后一次发送业务密钥 获取请求的时间距离业务密钥推送时间越短的用户终端， 设定为活跃度越 高的用户终端； 或者， 对在所述设定时长内各用户终端发送业务密钥获取 请求的次数进行统计， 将发送业务密钥获取请求的次数越多的用户终端， 设定为活跃度越高的用户终端； 或者， 根据在所述设定时长内最后一次发 送业务密钥获取请求的时间距离业务密钥推送时间的长短， 为各用户终端 分配第一排序值， 并根据在所述设定时长内用户终端发送业务密钥获取请 求的次数， 为各用户终端分配第二排序值， 以及为各用户终端的第一排序 值和第二排序值进行加权求和， 得到实际排序值， 并按照所述该实际排序 值为各用户终端设定活跃度。
10、 如权利要求 7至 9任一项所述的业务处理服务器， 其特征在于， 所述推送模块， 具体用于确定在推送有效期内系统资源能够支持推送的用 户终端的数量 N, 并按照排序结果， 向排列在前的 N个用户终端推送业务 密钥更新通知， 所述 N为正整数。
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201110287855.3 | 2011-09-26 | ||
| CN201110287855.3A CN102333280B (zh) | 2011-09-26 | 2011-09-26 | 一种业务密钥更新的方法、系统及业务处理服务器 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2012155702A1 true WO2012155702A1 (zh) | 2012-11-22 |
Family
ID=45484857
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/CN2012/073256 WO2012155702A1 (zh) | 2011-09-26 | 2012-03-29 | 一种业务密钥更新的方法、系统及业务处理服务器 |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN102333280B (zh) |
| WO (1) | WO2012155702A1 (zh) |
Families Citing this family (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102333280B (zh) * | 2011-09-26 | 2018-02-09 | 中兴通讯股份有限公司 | 一种业务密钥更新的方法、系统及业务处理服务器 |
| CN103874024B (zh) * | 2012-12-13 | 2017-06-20 | 中国移动通信集团公司 | 一种广播下载业务的任务调度方法、装置及系统 |
| CN105630544A (zh) * | 2015-12-21 | 2016-06-01 | 小米科技有限责任公司 | 系统更新控制方法、装置及服务器设备 |
| CN110661786B (zh) * | 2019-09-04 | 2021-10-08 | 杭州利项科技有限公司 | 一种基于链条关系的用户数据系统 |
| CN111193585B (zh) * | 2019-09-24 | 2021-11-30 | 腾讯科技（深圳）有限公司 | 通信请求管理方法及装置 |
| CN111246229B (zh) * | 2020-01-07 | 2022-01-25 | 北京字节跳动网络技术有限公司 | 直播间礼物资源更新方法、装置、介质及电子设备 |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20040123313A1 (en) * | 2002-12-14 | 2004-06-24 | Han-Seung Koo | Method for updating key in DCATV conditional access system |
| CN1553600A (zh) * | 2003-05-29 | 2004-12-08 | 华为技术有限公司 | 一种共享密钥更新的方法 |
| CN1567812A (zh) * | 2003-06-19 | 2005-01-19 | 华为技术有限公司 | 一种实现共享密钥更新的方法 |
| CN101102552A (zh) * | 2007-08-16 | 2008-01-09 | 中兴通讯股份有限公司 | 业务密钥更新方法和系统 |
| CN102333280A (zh) * | 2011-09-26 | 2012-01-25 | 中兴通讯股份有限公司 | 一种业务密钥更新的方法、系统及业务处理服务器 |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20040120527A1 (en) * | 2001-08-20 | 2004-06-24 | Hawkes Philip Michael | Method and apparatus for security in a data processing system |
| CN101267294B (zh) * | 2007-03-14 | 2012-05-09 | 中国移动通信集团公司 | 密钥分发方法 |
-
2011
- 2011-09-26 CN CN201110287855.3A patent/CN102333280B/zh active Active
-
2012
- 2012-03-29 WO PCT/CN2012/073256 patent/WO2012155702A1/zh active Application Filing
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20040123313A1 (en) * | 2002-12-14 | 2004-06-24 | Han-Seung Koo | Method for updating key in DCATV conditional access system |
| CN1553600A (zh) * | 2003-05-29 | 2004-12-08 | 华为技术有限公司 | 一种共享密钥更新的方法 |
| CN1567812A (zh) * | 2003-06-19 | 2005-01-19 | 华为技术有限公司 | 一种实现共享密钥更新的方法 |
| CN101102552A (zh) * | 2007-08-16 | 2008-01-09 | 中兴通讯股份有限公司 | 业务密钥更新方法和系统 |
| CN102333280A (zh) * | 2011-09-26 | 2012-01-25 | 中兴通讯股份有限公司 | 一种业务密钥更新的方法、系统及业务处理服务器 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN102333280A (zh) | 2012-01-25 |
| CN102333280B (zh) | 2018-02-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105451087B (zh) | 弹幕信息的推送方法、终端、历史数据服务器及系统 | |
| CN110336885B (zh) | 边缘节点分配方法、装置、调度服务器及存储介质 | |
| WO2012155702A1 (zh) | 一种业务密钥更新的方法、系统及业务处理服务器 | |
| US9407492B2 (en) | System and method for enabling control of mobile device functional components | |
| US20140344286A1 (en) | Method and apparatus for displaying webcast roomss | |
| WO2014183427A1 (en) | Method and apparatus for displaying webcast rooms | |
| CN109756528B (zh) | 频率控制方法及装置、设备、存储介质、服务器 | |
| CN111787345B (zh) | 基于网络直播间的互动资源处理方法、装置、服务器及存储介质 | |
| US9936241B2 (en) | Method and apparatus for providing dynamic channel and content provisioning | |
| US10212194B2 (en) | Server controlled throttling of client to server requests | |
| CN110460879B (zh) | 一种视频请求调度方法、装置、服务器及存储介质 | |
| CN103747286A (zh) | 一种用于提供视频的方法和设备 | |
| US10700879B2 (en) | Charging method and device, access device, service quality control method and device | |
| CN108415908B (zh) | 一种多媒体数据的处理方法及服务器 | |
| CN110099292B (zh) | 一种数据中心节点确定方法、装置及电子设备 | |
| CN108235063A (zh) | 一种视频处理方法、装置、电子设备及存储介质 | |
| EP3053128A1 (en) | Conditional pre-delivery of content to a user device | |
| CN105637904A (zh) | 针对涉及无线终端和服务器设备的通信会话的业务协调 | |
| CN110996114B (zh) | 一种直播调度方法、装置、电子设备和存储介质 | |
| WO2013189421A2 (zh) | 分布式的话单统计方法、装置以及系统 | |
| WO2014153843A1 (zh) | 一种数字电视用户的分类方法、装置及系统 | |
| WO2022242470A1 (zh) | Cdn的调度方法、装置、设备及存储介质 | |
| EP3051769A1 (en) | Dynamic switching to broadcast transmission of multimedia content over a mobile communication network | |
| WO2016110063A1 (zh) | 一种网络控制的方法及装置 | |
| CN103686224A (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: 12786397 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: 12786397 Country of ref document: EP Kind code of ref document: A1 |