WO2009138028A1 - 用户生成内容的注册方法、装置和系统 - Google Patents

用户生成内容的注册方法、装置和系统 Download PDF

Info

Publication number
WO2009138028A1
WO2009138028A1 PCT/CN2009/071752 CN2009071752W WO2009138028A1 WO 2009138028 A1 WO2009138028 A1 WO 2009138028A1 CN 2009071752 W CN2009071752 W CN 2009071752W WO 2009138028 A1 WO2009138028 A1 WO 2009138028A1
Authority
WO
WIPO (PCT)
Prior art keywords
content
user
registration
guarantee
certificate
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2009/071752
Other languages
English (en)
French (fr)
Inventor
刘义俊
高洪涛
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
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
Priority to EP09745412A priority Critical patent/EP2262165B1/en
Publication of WO2009138028A1 publication Critical patent/WO2009138028A1/zh
Priority to US12/939,030 priority patent/US20110093705A1/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0823—Network architectures or network communication protocols for network security for authentication of entities using certificates
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/60—Protecting data
    • G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
    • G06F21/6218—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
    • G06F21/6272—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database by registering files or documents with a third party
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0884—Network architectures or network communication protocols for network security for authentication of entities by delegation of authentication, e.g. a proxy authenticates an entity to be authenticated on behalf of this entity vis-à-vis an authentication entity
    • 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/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
    • H04L9/321—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving a third party or a trusted authority
    • 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/60—Digital content management, e.g. content distribution
    • 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/76—Proxy, i.e. using intermediary entity to perform cryptographic operations
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/06—Network architectures or network communication protocols for network security for supporting key management in a packet data network
    • H04L63/062—Network architectures or network communication protocols for network security for supporting key management in a packet data network for key distribution, e.g. centrally by trusted party

Definitions

  • the present invention relates to the field of network technologies, and in particular, to a method, device and system for registering user generated content. Background technique
  • UGC User Generated Content
  • users are free to upload personally created content on a fixed website.
  • UGC is usually uploaded to a fixed website, which will bring certain benefits to the website. Due to the free upload, there is no guarantee that the uploader is the real creator of the content, thus damaging the interests of the real creators of UGC and damaging the creative enthusiasm of the users; at the same time, because of the free upload, other websites can be freely reposted, allowing users to upload The influence of the website is limited. Therefore, the content needs to be registered for subsequent management.
  • the process of using the existing registration method is too cumbersome.
  • UGC's content creation process is easy to register the content. Therefore, the existing content registration method is applied to the UGC registration process, and the registration cost is Too high, the registration method is cumbersome. Summary of the invention
  • the embodiment of the invention provides a method, a device and a system for registering user-generated content, which solves the problem that the existing content registration method is cumbersome and the cost is too high.
  • an embodiment of the present invention provides a method for registering user-generated content, including: receiving a content registration request, where the content registration request carries user-generated content and a security certificate corresponding to the user-generated content, the guarantee The voucher is generated by a third-party network entity;
  • the user generated content is registered according to the guarantee voucher.
  • the embodiment of the invention further provides a device for registering user generated content, including: a receiving module, configured to receive a content registration request, where the content registration request carries a user-generated content and a security certificate corresponding to the user-generated content, where the security certificate is generated by a third-party network entity;
  • a registration system for user generated content including:
  • a website configured to receive user generated content sent by a user, and generate a corresponding guarantee certificate for the user generated content
  • a content identification manager configured to receive a content registration request, where the content registration request carries the user generated content and a security certificate, and the user generated content is registered according to the guarantee certificate.
  • the embodiment of the present invention provides guarantee by the website uploaded by UGC, and the content identification manager registers UGC according to the guarantee of the website, and UGC registration can be realized and the registration process is simple and easy.
  • FIG. 1 is a schematic flow chart of an embodiment of a UGC registration method according to the present invention.
  • FIG. 2 is a schematic flowchart of a first embodiment of a UGC registration method according to an embodiment of the present invention
  • FIG. 3 is a schematic flowchart of identity registration in an embodiment of a UGC registration method according to the present invention
  • FIG. 5 is a schematic structural diagram of Embodiment 1 of a device for generating user-generated content according to the present invention
  • FIG. 6 is a schematic structural diagram of Embodiment 2 of a device for registering user-generated content according to the present invention
  • FIG. 8 is a schematic structural diagram of Embodiment 2 of a registration system for user generated content according to the present invention.
  • Content registration refers to the process of applying content as a separate entity to the relevant authority for the characterization of the individual.
  • the content provider is usually required to provide relevant legally valid documents when providing content to the management agency, for example, Content Identity Manager (CIM), so that the content provided can be authenticated as Apply for a registrant.
  • CIM Content Identity Manager
  • a software developer wants to register for a newly completed software, it needs to provide a certificate issued by an authority, a legal person certificate issued by the enterprise, and a new report issued by the national authority.
  • the security certificate is provided by a trusted third party. The specific process is as follows:
  • Step 11 A CIM receives a content registration request, where the content registration request carries a UGC and a security certificate corresponding to the UGC, and the guarantee The credentials are generated by a third party network entity, such as by a website that is to receive the UGC.
  • Step 12 The CIM registers the UGC according to the guarantee voucher.
  • the website to be uploaded by the UGC provides the UGC with a guarantee certificate, so that the CIM completes the registration of the UGC according to the guarantee certificate, so that the registration is simple and easy.
  • FIG. 2 is a schematic flowchart of a first example of a method for registering a UGC according to the present invention. Compared with the embodiment shown in FIG. 1, the embodiment includes steps 201-203 before step 11.
  • Step 201 The user registers with the website, such as the Website Proxy Agent (WPA), to obtain the identity User-ID.
  • WPA Website Proxy Agent
  • the website is used to receive and publish the uploaded UGC.
  • the UGC needs to be forwarded before the website is published.
  • CIM conducts content registration to ensure the benefit of UGC's true creators.
  • Step 202 The user sends a proxy content registration request to the website to be received by the UGC.
  • the proxy registration content request carries UGC, identity, and registration mode, such as adopting a user self-application mode or a website direct proxy mode.
  • the parameter description specifically used for the content registration request may be Content_Hash+User-ID+Regist_Mode. Among them, including the content of UGC to be applied for registration Hash Content - Hash, Identity User - ID and Registration Mode Regist - Mode.
  • the UGC uploaded by the user to the website in this embodiment is the content hash value Content_Hash.
  • the user can also upload the UGC content itself Gontent.
  • Step 203 The website generates a guarantee certificate according to the UGC and the identity identifier, and the guarantee certificate is used to bind the UGC and the identity identifier.
  • the specific parameter description of the guarantee certificate can be
  • Sign WPA Hash (Content _ Hash + User _ ID + TimeStamp)
  • the WPA receives the content hash value Content_Hash and the assigned identity User-ID and the more accurate time when the operation is performed (or the timestamp obtained from the time authority) TimeStamp is hashed and hashed.
  • the signature operation is performed by using the private key corresponding to the public certificate of the WPA, and the guarantee certificate is obtained to confirm that the UGC is owned by the user having the User ID.
  • the UGC can perform content registration with the CIM.
  • the step 11 in the embodiment is that the CIM receives the content registration request sent by the user, and specifically includes 204. -207:
  • Step 204 If the registration mode carried in the proxy content registration request indicates that the user self-application mode is adopted, the website returns the guarantee certificate ⁇ 1 ⁇ to the user.
  • Step 205 The user verifies the validity of the guarantee certificate to determine whether the website generates a guarantee certificate for the UGC to be registered with the content, and the user verifies the guarantee certificate to determine that the WPA has initially guaranteed the ownership of the UGC. User execution )operating. If the guarantee certificate is valid, go to step 206.
  • Step 206 The user sends a content registration request to the CIM.
  • the content registration request carries the UGC to be registered and the security certificate corresponding to the UGC generated by the website.
  • the specific code of the content registration request may be En CRA (Content + User _ ID + Sign WPA (P*) + WPA _ URL) + Enc CIM PubKey (RAND), where each parameter is: Content is the content of the UGC to be registered itself; User—ID is the user The identity obtained after registration on the website; the website obtains the guarantee certificate signed by the UGC provided by the user, SignwpA (P *); WPA - URL is the resource identifier of the website to receive UGC.
  • the above-mentioned parameter transmission requires encrypted transmission.
  • the session key RAND can be used to encrypt the above parameters and then transmitted.
  • the RAND as the session key is encrypted by the CIM public key certificate and then transmitted to the CIM.
  • the transmission parameter may include an attribute description table for the content.
  • step 12 in this embodiment specifically includes steps 207-209: Step 207: CIM verifies the validity of the guarantee certificate, that is, whether the guarantee certificate is from a trusted website, if valid Then, step 208 is performed.
  • Step 208 The CIM verifies the applicability of the UGC, that is, whether the UGC can apply for registration in the CIM management domain, and if yes, step 209 is performed.
  • the above verification can also be verified by UGC applicability first, and then the verification of the guarantee voucher. If one of the above verifications fails, an error message is generated.
  • Step 209 Generate a content identifier Cntnt_ID corresponding to the UGC and a corresponding attribute description table Attribute_List and an approval certificate.
  • the specific operation parameter description can be:
  • the specific algorithm is as follows: First, a Cntnt_ID and an Attribute_List are generated, and the corresponding content identifier Cntnt_ID and the corresponding attribute description table are stored in a dedicated database, and the attribute description table can be used to determine whether the content of the subsequent application registration can be in the CIM. Apply within the domain,
  • the Generate(Cntnt_ID+Attribute_List) operation is executed; then, the private key corresponding to the content identification issuing certificate of the CIM is used for the signature operation, and the approved certificate for binding the parameter set and the Cntnt_ID is generated, and the approved certificate is used.
  • the website that is to receive the UGC is informed that the content of the application for registration has been successfully registered, so as to legally publicly register the successfully registered UGC.
  • the embodiment may further include steps l 210-214:
  • Step 210 The CIM sends the content identifier and the approval credential to the user through a secure channel, and the specific operation code is E nCRAND (Sign CIM Prv y (P* + Cntnt _ ID) + Cntnt_ID); or the generated error information is sent to the user. user.
  • Step 211 After receiving the information returned by the CIM, the user confirms the validity of the approved certificate generated by the CIM after confirming the non-error information, and if the authorized certificate is valid, that is, from the valid CIM, step 212 is performed.
  • the specific operation parameters are described as
  • Veri (Sign CIM PrvKey (P* + Cntnt- ID)) + Get(CntntJD) .
  • the specific algorithm is as follows: After receiving the data sent by the CIM, if the CIM does not send the error information, the RAND decrypts the data packet. And approval certificate + Gntnt _ID) to verify Veri (Sign CM Prv y (P* + Qit nt _ID)), if the verification is obtained by obtaining the content identifier
  • Step 212 The user will apply for registration of the UGC content itself and the corresponding approval
  • the certificate is uploaded to the website, or the decryption key of the originally uploaded encrypted UGC (such as content hash Content-Hash) is sent to the website.
  • the specific operation parameter description can be sent to the website for the user.
  • Step 213 The website verifies the validity of the approval voucher. If the approval voucher is valid, compares the content of the uploaded UGC content with the content hash value Content_Hash. If yes, go to step 214. Otherwise, follow the predetermined policy. Other operations.
  • the specific operation parameter description can be
  • Step 214 Publish the UGC outward according to a predetermined policy.
  • FIG. 3 is a schematic flowchart of the identity registration in the UGC registration method embodiment, where the step 201 specifically includes:
  • Step 31 The user sends an identity registration request to the website, such as WPA, where the identity registration request carries the identity information of the user.
  • the identity registration request carries the identity information of the user.
  • the user registers for identity they can use real-name registration or real-name registration.
  • Real-name registration refers to the identity information submitted by the website when the user is required to register. It is the real information of the user, such as the real name, ID number, contact information, such as phone number and home address, and some necessary information on the website. Other personal information, etc.
  • Quasi-real name registration refers to the use of a certificate from an authoritative third party, such as a bank certificate commonly used by a user, and a signature for the private key required to use the certificate when submitting an identity registration request.
  • the specific parameter description of the identity registration request may be
  • Authenticated third-party credentials including extended applications for digital certificates or digital certificates, and may include information such as mobile phone numbers for managing identities
  • the mode used to verify the voucher data needs to interact with the data of the Ministry of Public Security. If the certificate data is a digital certificate, it needs to interact with the certificate authority of the digital certificate.
  • Step 32 The WPA verifies the validity of the identity information sent by the user. If yes, go to step 33. Otherwise, return an error message to the user. WPA can verify the identity information provided by the user to a Trusted Third Party (TPP).
  • TPP Trusted Third Party
  • Step 33 The WPA generates an identity corresponding to the identity information used to upload the UGC and generates an identity recognition signature for binding the identity information and the identity.
  • the specific operation is that if the identity information provided by the user is authentic, the user identity User-ID generated in the site is generated for the user, and the user identity identifier is connected with the identity registration information submitted by the user.
  • WPA signs the private key corresponding to the public key certificate issued by the outside world
  • Sign WPA Sign WPA
  • Step 34 Encrypt the identity approval signature and return it to the user.
  • the specific operation code can return EnC R ND ( S i g n WPA ( p " )) to the user for WPA.
  • Step 35 The user verifies whether the identity approval signature is valid, to determine whether the identity registration is successful, and if yes, go to step 36.
  • Step 36 Obtain an identity.
  • the specific operation code can be Get ( User - ID ).
  • the UGC registration is implemented by the user self-application mode, and the website provides the guarantee certificate for the UGC.
  • the user registers the content with the CIM
  • the UGC and the website provide the responsibility to be registered.
  • the certificate is sent to the CIM together, and the UMC is registered by the CIM according to the guarantee certificate, and the registration method is simple and easy.
  • Figure 4 A schematic diagram of the process of the second embodiment, the embodiment includes:
  • Step 401 The user obtains an identity by registering the UGC website, such as WPA.
  • the process for the user to register the identity with the website is the same as the process shown in the first example.
  • Step 402 The user sends a proxy content registration request to the website.
  • the proxy registration content request carries the UGC, identity, and registration mode, such as the user self-application mode or the direct proxy mode.
  • the specific code for the content registration request can be
  • the content of the UGC content to be applied for registration is a hash value Content_Hash, an identity user-ID, and a registration mode Regist_Mode.
  • the content value encrypted by the user-generated random number RAND is used in the transmitted parameter set, that is, Enc RAND ( C. ntent ).
  • Step 403 The website generates a guarantee certificate according to the UGC and the identity identifier, and the guarantee certificate is used to bind the UGC and the identity identifier.
  • the specific code of the guarantee certificate can be
  • Step 404 If the registration mode indicates that the website direct proxy mode is adopted, the website directly sends a content registration request to the CIM.
  • the content registration request carries the content hash value of the UGC to be registered and the security certificate corresponding to the UGC generated by the website. That is, the parameter description of the content registration request may be
  • Step 405 Verify the validity of the guarantee certificate. If yes, go to step 406.
  • Step 406 Verify the applicability of the user-generated content, that is, verify whether the UGC can apply for registration in the CIM management domain. If the applicability verification is passed, go to step 407.
  • the above verification process may be as follows: First, after decrypting the encrypted data packet, the obtained WPA extracts the verification of the UGC guarantee signature SignwpA (p *). After the visa is passed, it is checked whether the UGC that wants to apply for registration can apply, that is, to ensure that there is no duplicate application in this CIM management domain, and to review the attribute description related to UGC.
  • Step 407 Generate a content identifier Cntnt_ID corresponding to the UGC and an approval certificate, where the approval certificate is used to bind the content identifier and the guarantee certificate, and the approval certificate is used to make the website of the UGC to be received aware that the content of the application for registration is registered.
  • Successful in order to legally publicly register a successful UGC. If one of the above verifications fails, an error message is generated.
  • the specific method can be triggered to generate Cntnt-ID and attribute description table corresponding to UGC, and Content-Hash to UGC after verification is completed.
  • Step 408 The CIM returns the content identifier and the approved certificate to the website via the secure channel, or returns the error information to the website. That is, CIM returns Sl g n ciM_ PrvKey + Cntnt_ID to the website.
  • Step 409 After receiving the information returned by the CIM, the website verifies the validity of the approved certificate generated by the CIM after confirming the non-error information, and if yes, executing step 410, otherwise ending the process of registering the content of the proxy application.
  • the specific operating parameters are described as Veri ( si g n c IM _ ey (*).
  • Step 410 The website sends the content identifier, the accreditation certificate generated by the CIM, and the guarantee certificate generated by the website itself to the user, or sends the generated error information to the user.
  • the website returns S nCM—PrvKey + Sign ⁇ AC to the user.
  • Step 411 After receiving the information returned by the CIM, the user confirms that it is not an error message, and then verifies the CIM.
  • the specific operating parameter description can be: Veri (Sign CIM PrvKey (*)) + Veri (Sign WPA (P*))
  • Step 412 The user uploads the UGC and the corresponding content identifier applied for registration to the website, or sends the decrypted key of the originally uploaded encrypted UGC to the website.
  • the user uploads Content+Cntnt_ID to the website.
  • Step 413 The website compares whether the uploaded content is consistent. If yes, go to step 414.
  • the specific action code can be Comp(Content, Content_Hash).
  • Step 414 Publish the UGC outward according to a predetermined policy, otherwise, perform other operations according to a predetermined policy.
  • the UGC registration is implemented by the user self-application mode, and the website provides the guarantee certificate for UGC. After the website generates the guarantee certificate, the guarantee certificate is sent to the CIM together with the UGC uploaded by the user to be registered, and the CIM The guarantee certificate is registered for the UGC, and the registration method is simple and easy.
  • FIG. 5 is a schematic structural diagram of Embodiment 1 of a device for generating user-generated content according to the present invention.
  • This embodiment includes a receiving module 51 and a registration module 52.
  • the receiving module 51 is configured to receive a content registration request, where the content registration request carries a UGC and a security certificate corresponding to the UGC, where the security certificate is generated by a third-party network entity, such as a website to be received by the UGC; 52 is configured to register the UGC according to the guarantee voucher.
  • the receiving module 51 may be configured to receive a content registration request sent by the user or may also receive a content registration request sent by the website.
  • the registration module 52 is specifically configured to verify the validity of the guarantee certificate, if the guarantee certificate has And verifying the applicability of the user-generated content, and if the user-generated content is applicable, generating a content identifier corresponding to the user-generated content.
  • the registration module can also generate an approval certificate while generating the content identifier, and the approval certificate is used to make the receipt
  • the website provides UGC with a guarantee voucher, so that UGC can implement content registration, and the registration method is simple and easy.
  • FIG. 6 is a schematic structural diagram of Embodiment 2 of a device for generating user-generated content according to the present invention.
  • the embodiment further includes a sending module 53 for sending the content identifier and the approval certificate generated by the registration module 52. Sent directly to the user, or used to send the content identification and approval credentials to the website.
  • the website provides UGC with a guarantee voucher, so that UGC can implement content registration, and the registration method is simple and easy. Moreover, it is possible to directly interact with the user or to interact with the website according to the registration mode, so that the registration method is various.
  • FIG. 1 is a schematic structural diagram of Embodiment 1 of a registration system for generating content of a user of the present invention, and the embodiment includes a website 71 and a CIM 72.
  • the website 71 is configured to receive the user-generated content sent by the user, and generate a corresponding security certificate for the user-generated content;
  • the CIM 72 is configured to receive a content registration request, where the content registration request carries the user-generated content and the identity identifier, according to the The identity identifies the user generated content.
  • the website provides a guarantee voucher for the UGC submitted by the user, so that the UGC registration method avoids the cumbersome and high-cost problem existing in the prior art.
  • FIG. 8 is a schematic structural diagram of Embodiment 2 of a user-generated content registration system according to the present invention.
  • the website 71 of the embodiment specifically includes an identity identification module 711, a proxy receiving module 712, and a guarantee generation module 713.
  • the identity identification module 711 is configured to provide the user with an identity identifier;
  • the proxy receiving module 712 is configured to receive a proxy content registration request sent by the user, where the proxy content registration request carries the user generated content and the identity identifier; 713 is used to generate tie The security certificate of the user generated content and the identity identifier received by the proxy receiving module 712 is determined.
  • the proxy content registration request received by the proxy receiving module 712 further carries a registration mode.
  • the website may also include: a registration sending module 714.
  • the registration sending module 714 is configured to: when the registration mode received by the proxy receiving module 712 indicates that the registration adopts the user self-application mode, send the guarantee credential generated by the guarantee generating module 713 to the user, so that the user is in the verification office. After the security certificate is valid, the content registration request is sent to the content identification manager; or the registration sending module 714 is configured to generate, in the guarantee generation module, when the registration mode indicates that the registration adopts the website direct proxy mode After the guarantee voucher, the content registration request is directly sent to the content identification manager.
  • the website provides a guarantee voucher for the UGC submitted by the user, so that the UGC registration method avoids the cumbersome and high-cost problem existing in the prior art.
  • the user can directly register according to the registration mode selected by the user or register the UGC by using a website proxy, so that the UGC registration method is not only simple and easy, but also can implement various methods.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Hardware Design (AREA)
  • General Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computing Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Health & Medical Sciences (AREA)
  • Bioethics (AREA)
  • General Health & Medical Sciences (AREA)
  • Software Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Databases & Information Systems (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Information Transfer Between Computers (AREA)

Description

用户生成内容的注册方法、 装置和系统 技术领域
本发明涉及网络技术领域， 尤其是一种用户生成内容的注册方法、 装置 和系统。 背景技术
用户生成内容（ User Generated Content, UGC )通常是指一种由普通用户 生成的内容， 如在群组、 博客中上传的文本、 图片、 视频、 音频等各种形式 的、 由用户创作的作品。 通常， 用户是在某一固定网站自由上传个人创作的 内容， 即 UGC通常是上传至某一固定网站， 会为该网站带来一定的利益。 由 于自由上传的原因， 不能保证上传者是内容的真正创作者， 因此损害了 UGC 真正的创作者的利益， 打击用户的创作热情； 同时， 因为自由上传， 其他网 站可以自由转贴， 使用户上传的网站的影响力受到限制。 因此， 需要对内容 进行注册， 以便后续管理。 但是， 对于 UGC的制作者来说， 采用现有的注册 方式过程太过繁瑣， UGC的内容制作过程都易于内容注册的过程， 因此， 将 现有内容注册方式应用到 UGC注册过程中， 注册成本太高， 注册方式繁瑣。 发明内容
本发明实施例提供一种用户生成内容的注册方法、 装置和系统， 解决现 有内容注册方式繁瑣、 成本太高的问题。
为此， 本发明实施例提供了一种用户生成内容的注册方法， 包括： 接收内容注册请求， 所述内容注册请求中携带用户生成内容及与所述用 户生成内容对应的担保凭证， 所述担保凭证由第三方网络实体生成；
根据所述担保凭证对所述用户生成内容进行注册。
本发明实施例还提供了一种用户生成内容的注册装置， 包括： 接收模块， 用于接收内容注册请求， 所述内容注册请求中携带用户生成 内容及与所述用户生成内容对应的担保凭证， 所述担保凭证由第三方网络实 体生成； 本发明实施例还提供了一种用户生成内容的注册系统， 包括：
网站， 用于接收用户发送的用户生成内容， 为所述用户生成内容生成对 应的担保凭证；
内容标识管理者， 用于接收内容注册请求， 所述内容注册请求中携带所述 用户生成内容和担保凭证， 根据所述担保凭证对所述用户生成内容进行注册。
由上述技术方案可知， 本发明实施例通过由 UGC上传的网站提供担保， 内容标识管理者根据该网站的担保对 UGC进行注册， 可以实现 UGC的注册 并且注册流程简单易行。 附图说明
图 1为本发明 UGC的注册方法实施例的流程示意图；
图 2为本发明 UGC的注册方法实施例提供的例一的流程示意图； 图 3为本发明 UGC的注册方法实施例中的身份注册的流程示意图； 图；
图 5为本发明用户生成内容的注册装置实施例一的结构示意图； 图 6为本发明用户生成内容的注册装置实施例二的结构示意图； 图 Ί为本发明用户生成内容的注册系统实施例一的结构示意图； 图 8为本发明用户生成内容的注册系统实施例二的结构示意图。 具体实施方式
下面通过附图和实施例， 对本发明的技术方案做进一步的详细描述。 内容注册是指将内容作为一种独立个体， 在权威机构申请相关的对于该 个体的特征描述的过程。 在后续的与该内容相关的操作与管理过程中， 可以 根据该特征描述关联到该个体的其他的属性描述。 对于内容的注册， 通常要 求内容提供者在提供内容至管理机构，例如，内容标识管理者（ Content Identity Manager, CIM )进行注册时， 提供相关具有法律效力的证明文件， 以便可认 证所提供内容为申请注册者所有。 例如， 软件开发商要针对新完成的软件进 行注册， 需要提供权威机构出具的证明、 企业出具的法人证明、 国家权威部 门出具的查新报告等。 下面的实施例中是由可信第三方提供担保凭证， 具体 流程如下：
图 1为本发明 UGC的注册方法实施例的流程示意图， 该实施例包括： 步骤 11： CIM接收内容注册请求， 所述内容注册请求中携带 UGC及与 所述 UGC对应的担保凭证， 所述担保凭证由第三方网络实体生成，如由待接 收所述 UGC的网站生成。
步骤 12: CIM根据所述担保凭证对所述 UGC进行注册。
本实施例由 UGC待上传的网站为该 UGC提供担保凭证，使 CIM根据该 担保凭证完成对该 UGC的注册， 使注册简便易行。
图 2为本发明 UGC的注册方法实施例提供的例一的流程示意图， 与图 1 所示的实施例相比， 该实施例在步骤 11之前包括步骤 201-203:
步骤 201 : 用户向网站， 如网站代理服务模块 （Website Proxy Agent, WPA ), 进行身份注册， 获取身份标识 User— ID, 该网站用于接收及公布上传 的 UGC, 该 UGC在网站公布之前需要向 CIM进行内容注册， 以保证 UGC 真正创作者的利益。
步骤 202: 用户向待接收 UGC的网站发送代理内容注册请求。 该代理注 册内容请求中携带 UGC、 身份标识和注册模式， 如采用用户自申请模式还是 采用网站直接代理模式。 内容注册请求具体采用的参数描述可以为 Content— Hash+User—ID+Regist— Mode。 其中， 包括待申请注册的 UGC的内容 哈希值 Content— Hash、身份标识 User— ID和注册模式 Regist— Mode。为了 UGC 的安全性， 本实施例中用户向网站上传的 UGC为内容哈希值 Content— Hash , 可替代的是， 如在网站足够可信的情况下， 用户也可以上传 UGC 内容本身 Gontent
步骤 203: 网站根据 UGC和身份标识生成担保凭证， 该担保凭证用于绑 定该 UGC和身份标识。 担保凭证的具体参数描述可以为
Sign WPA (Hash(Content _ Hash + User _ ID + TimeStamp))， 以下为简单起见， 简写 为
Figure imgf000006_0001
。具体做法为 WPA将接收到的内容哈希值 Content— Hash与分配 的身份标识 User— ID与进行运算时的较准确时刻 （或获取自时间权威管理机 构的时间戳 ) TimeStamp串接后进行哈希运算后， 用 WPA的相关的公开的证 书对应的私钥进行签名运算， 得到该担保凭证， 用于确证该 UGC 为具有该 User— ID的用户所有。
当网站为 UGC生成对应的担保凭证后， UGC可以向 CIM进行内容注册， 相比于图 1所示的实施例， 本实施例中的步骤 11是 CIM接收用户发送的内 容注册请求， 具体包括 204-207:
步骤 204: 若上述代理内容注册请求中携带的注册模式表明采用用户自 申请模式， 则网站向用户返回该担保凭证^ 1^。
步骤 205: 用户验证该担保凭证的有效性， 以确定网站是否为待内容注 册的 UGC生成了担保凭证， 用户验证该担保凭证， 以确定 WPA 已对 UGC 的归属权进行了初步担保。 即用户执行
Figure imgf000006_0002
)操作。 若担保凭证有 效， 则执行步骤 206
步骤 206: 用户向 CIM发送内容注册请求。 该内容注册请求中携带待注册 的 UGC和网站生成的对应于该 UGC的担保凭证。 内容注册请求的具体代码可 以为 EnCRA (Content + User _ ID + Sign WPA (P* ) + WPA _ URL) + EncCIM PubKey (RAND) 其中各参数为： Content为待注册的 UGC的内容本身； User— ID为用户在 网站上注册后获得的身份标识； 网站对用户所提供的 UGC进行确认签名得到 的担保凭证 SignwpA (P*) ; WPA— URL为待接收 UGC的网站的资源标识。 因为用 户与 CIM间未事先建立起安全通道， 所以以上所述的参数传送时需要加密传 送。 具体可以用会话密钥 RAND加密上述参数后进行传送， 同时将作为会话 密钥的 RAND用 CIM公开的公钥证书加密后传送给 CIM,传送参数可包括对内 容的属性描述表。
即分别进行力口密处理 EncRAND (Content + User _ ID + Sign WPA (P* ) + WPA _ URL) , 和 EncCIM— PubKey(RAND)。 相比于图 1所示的实施例，本实施例中的步骤 12具体包括步骤 207-209: 步骤 207: CIM验证该担保凭证的有效性， 即确认担保凭证是否来自可 信的网站， 若有效， 则执行步骤 208。
步骤 208: CIM验证该 UGC的可申请性，即验证该 UGC是否可在本 CIM 管理域内申请注册， 若可申请， 则执行步骤 209。
上述验证也可以先进行 UGC可申请性的验证， 再进行担保凭证的验证。 若上述有一项验证不通过则生成错误信息。
上述验证流程具体参数描述可以为
Extract(Content + User ID + Sign A(P*)) + VeriCM PrvKey (Sign^ (P* ))。 即 CIM首先用相应私钥解密得到会话密钥 RAND, 然后用该会话密钥解 密得到相应的参数集包括 Content, User— ID和 sign AC , 即执行解密操作 Extract(Content + User _ ID + SignWPA (P*))得到上述参数集。
之后， 验证用户所提供的 Content是否可在本 CIM管理域内注册， 若可 以， 验证 WPA 提供的担保凭证8^11^^^ 的有效性， 即执行验证操作 VeriCIM_Prv y(SignWPA(P*))。 若验证通过， 则触发下一步生成内容标识等的操作， 反之则生成错误信息。 步骤 209: 生成对应于该 UGC的内容标识 Cntnt— ID与相应的属性描述表 Attribute— List及认可凭证。 具体操作参数描述可以为：
Generate(Cntnt_ID+Attribute_List) + Slgllci -PrvK^(P + Cntnt— ID)。
具体算法为： 首先生成 Cntnt— ID 和 Attribute— List, 将相应的内容标识 Cntnt— ID与相应的属性描述表存储入专用数据库， 属性描述表可以用于确定 后续申请注册的内容是否可以在本 CIM域内进行申请，
即执行 Generate(Cntnt— ID+Attribute— List)操作； 然后用 CIM的与内容标 识颁发证书对应的私钥进行签名运算， 生成用于绑定参数集和 Cntnt— ID的认 可凭证，该认可凭证用于使待接收 UGC的网站获知申请注册的内容已注册成 功， 以便合法公开注册成功的 UGC。
即执行 Sign — + Cntnt _ ID)操作。
为了在网站上公布该内容注册后的 UGC, 本实施例还可以进一步包括步 l 210-214:
步骤 210: CIM将内容标识和认可凭证通过安全通道发送给用户， 具体 操作代码为 EnCRAND(SignCIM Prv y(P* + Cntnt _ ID) + Cntnt— ID)； 或者将生成的错误 信息发送给用户。
步骤 211 :用户接收 CIM返回的信息后，确认为非错误信息后，验证 CIM 生成的认可凭证的有效性， 若认可凭证有效， 即来自有效的 CIM, 则执行步 骤 212。 具体操作参数描述为
Veri(SignCIM PrvKey (P* + Cntnt― ID)) + Get(CntntJD)。 具体算法为： 用户在接收到 CIM发送的数据后， 若 CIM发送的不是错 误信息时，采用 RAND解密数据包。并对认可凭证
Figure imgf000008_0001
+ Gntnt _ID)进 行验证 Veri(SignCM Prv y(P* + Qitnt _ID)) , 若验证通过获取内 容标识
Get(CntntJD), 即表明 UGC在 CIM的内容注册成功。
步骤 212: 用户将申请注册的 UGC的内容本身 Content及对应的认可凭 证上传给网站， 或将原上传的加密的 UGC (如内容哈希值 Content—Hash )的 解密密钥发送给网站。 具体操作参数描述可以为用户向网站发送
Content+Cntnt_ID+Sign--— (pi + Cntnt-ID)。
步骤 213: 网站验证认可凭证的有效性， 若认可凭证有效， 则比较上传 的 UGC的内容本身 Content和内容哈希值 Content—Hash的一致性， 若一致， 执行步骤 214, 否则， 按照预定策略进行其他操作。 具体操作参数描述可以 为
Veri(SignCIM PrvKey (P + Cntcn _ ID)) +Comp(Content,Content— Hash)。 步骤 214: 按照预定的策略向外公布 UGC。
图 3为本发明 UGC的注册方法实施例中的身份注册的流程示意图，即步 骤 201具体包括：
步骤 31 : 用户向该网站， 如 WPA发送身份注册请求， 该身份注册请求 中携带用户的身份信息。 用户在身份注册时， 可以采用实名注册或准实名注 册。 实名注册是指网站要求用户身份注册时提交的身份信息是用户本身所具 有的真实信息， 如真实的姓名、 身份证号、 联系方式， 如电话号码和家庭住 址等， 以及网站认为的一些必要的其他个人信息等。 准实名注册是指用户采 用权威第三方的证明， 如用户常用的银行的证书， 并在提交身份注册请求时 包含针对使用该证书需要的私钥的签名。
身份注册请求的具体参数描述可以为
RealName_ Params) + EncWAP PubKey (RAND + Hash(RAND + RealName _ Params)) 采用实名注册时需要用户提供个人的真实身份信息， 部分字段的 XML表 述如下所示：
<Real_Name>
<Name>
实名
</Name> <Credential_Material>
可认证的第三方凭证， 包括数字证书或数字证书的扩展应用， 还可以包 括手机号等管理身份的信息
</Credential_Marerial>
<Veri_Mode>
验证凭证资料采用的模式， 如身份证号需要与公安部的数据交互， 若凭 证资料是数字证书， 需要与该数字证书的发证中心进行交互
</Veri_Mode>
</Real_Name>
步骤 32: WPA验证用户发送的身份信息的有效性， 若有效， 执行步骤 33 ,否则，向用户返回错误信息。 WPA可以向可信第三方（ Trusted Third Party, TTP )验证用户提供的身份信息是否属实。
步骤 33: WPA生成用于上传 UGC的与身份信息对应的身份标识并生成 用于绑定身份信息和身份标识的身份认可签名。 具体操作为若验证用户所提 供的身份信息是可信的，则为用户生成在本站内的用户身份标识 User— ID,并 将该用户身份标识与用户所提交的身份注册信息串接后采用 WPA 的向外界 发布的公钥证书对应的私钥进行签名
Sign (Hash(Authorized Material) + User lD) , 以下简称 SignWPA (P** )即认可用 户在网站上的实名或准实名注册。 为安全起见， 可以加密身份认可签名。
步骤 34: 将身份认可签名加密后返回给用户。具体操作代码可以为 WPA 向用户返回 EnCR ND (S ign WPA (p " ))。
步骤 35: 用户验证身份认可签名是否有效， 以确定身份注册是否成功， 若有效， 执行步骤 36。
Figure imgf000010_0001
步骤 36: 获取身份标识。 具体操作代码可以为 Get(User-ID)。
本实施例采用用户自申请模式实现 UGC的注册， 由网站为 UGC提供担 保凭证， 用户在向 CIM进行内容注册时， 将待注册的 UGC和网站提供的担 保凭证一起发送给 CIM, 由 CIM根据该担保凭证对该 UGC进行注册， 注册 方法简单易行。
图 4
Figure imgf000011_0001
二的流程示意 图， 该实施例包括：
步骤 401 : 用户向待上传 UGC的网站， 如 WPA进行身份注册获取身份 标识。 其中， 用户向网站进行身份注册的流程与例一所示的流程相同。
步骤 402: 用户向网站发送代理内容注册请求。 该代理注册内容请求中 携带 UGC、 身份标识和注册模式， 如采用用户自申请模式还是采用网站直接 代理模式。 内容注册请求的具体代码可以为
Content— Hash+User—ID+Regist— Mode。 其中， 包括待申请注册的 UGC的内容 哈希值 Content— Hash、 身份标识 User— ID和注册模式 Regist— Mode。 同时在发 送的参数集中可选地发送采用由用户生成的随机数 RAND作为密钥加密的内 容值， 即 EncRAND (C。ntent)。
步骤 403: 网站根据 UGC和身份标识生成担保凭证， 该担保凭证用于绑 定该 UGC和身份标识。 担保凭证的具体代码可以为
Sign (Hash(Content _ Hash + User _ ID + TimeStamp))， 以下为简单起见 简写 为 P 。具体做法为 WAp将接收到的内容哈希值 Content— Hash与分配 的身份标识 User— ID与进行运算时的较准确时刻 （或获取自时间权威管理机 构的时间戳 ) TimeStamp串接后进行哈希运算后， 用 WPA的相关的公开的证 书对应的私钥进行签名运算， 得到该担保凭证， 用于确证该 UGC 为具有该 User— ID的用户所有。
步骤 404: 若注册模式表明采用网站直接代理模式， 则网站直接向 CIM发 送内容注册请求。 该内容注册请求中携带待注册的 UGC的内容哈希值和网站 生成的对应于该 UGC的担保凭证。 即内容注册请求的参数描述可以为
Content—Hash + User ID + Sign ¾ (Ρ ) + TimeStamp
+ Sign (Hash(RANDWPA )) + Enc CIM PubKey (RAND 步骤 405: 验证所述担保凭证的有效性， 若有效， 则执行步骤 406。 步骤 406: 验证所述用户生成内容的可申请性， 即验证该 UGC是否可在 本 CIM管理域内申请注册， 若可申请性验证通过， 则执行步骤 407。
上述验证流程可以具体算法可以为： 首先解密加密数据包后提取得到的 的 WPA对 UGC的担保签名 SignwpA (p*)的验证。 签证通过后， 查验欲申请注 册的 UGC是否可进行申请， 即确保在本 CIM管理域中无重复的申请， 同时 审核与 UGC相关的属性描述。
步骤 407: 生成对应于该 UGC的内容标识 Cntnt— ID及认可凭证， 所述认 可凭证用于绑定内容标识和担保凭证，该认可凭证用于使待接收 UGC的网站 获知申请注册的内容已注册成功， 以便合法公开注册成功的 UGC。 若上述有 一项验证不通过则生成错误信息。 具体做法可以为验证完成后， 触发生成对 应于 UGC 的 Cntnt— ID 与属性描述表， 以及对 UGC 的 Content— Hash 与
User— ID、 WPA— URL、 CIM新获取的 TimeStamp的绑定认可凭证， 并存储相 关的数据。 认可凭证具体参数描述可以为
SignCIM PrvKey (Content _ hash + Cntnt _ ID + User _ ID + WPA _ URL + TimeStamp) 以下简写为 SigncIM_PrvKey (*)
步骤 408: CIM将内容标识、 认可凭证经安全通道返回给网站， 或将错 误信息返回给网站。 即 CIM向网站返回 SlgnciM_PrvKey +Cntnt_ID。
步骤 409: 网站接收到 CIM返回的信息后， 确认为非错误信息后， 验证 CIM生成的认可凭证的有效性， 若有效， 执行步骤 410, 否则结束代理申请 内容注册的流程。 具体操作参数描述为 Veri(signcIM_ ey (*》。
步骤 410: 网站将内容标识、 CIM生成的认可凭证和网站自身生成的担 保凭证发送给用户， 或将生成的错误信息发送给用户。
即网站向用户返回 S nCM—PrvKey + Sign^AC。
步骤 411 :用户接收 CIM返回的信息后，确认为非错误信息后，验证 CIM 生成的认可凭证， 网站生成的担保凭证， 若验证通过， 则执行步骤 412。 具体操作参数描述可以为： Veri(SignCIM PrvKey(*)) + Veri(SignWPA(P*))
步骤 412: 用户将申请注册的 UGC及对应的内容标识上传给网站， 或将 原上传的加密的 UGC的解密密钥发送给网站。
即用户向网站上传 Content+Cntnt— ID。
步骤 413: 网站比较上传内容是否一致， 若一致， 执行步骤 414。 具体操 作代码可以为 Comp(Content,Content— Hash)。
步骤 414: 按照预定的策略向外公布 UGC, 否则， 按照预定策略进行其 他操作。
本实施例采用用户自申请模式实现 UGC的注册， 由网站为 UGC提供担 保凭证， 在网站生成该担保凭证后， 将该担保凭证和用户上传的待注册的 UGC一起发送给 CIM, 由 CIM根据该担保凭证对该 UGC进行注册， 注册方 法简单易行。
本领域普通技术人员可以理解： 实现上述方法实施例的全部或部分步骤 可以通过程序指令相关的硬件来完成， 前述的程序可以存储于一计算机可读 取存储介质中， 该程序在执行时， 执行包括上述方法实施例的步骤； 而前述 的存储介质包括： ROM, RAM, 磁碟或者光盘等各种可以存储程序代码的介 图 5为本发明用户生成内容的注册装置实施例一的结构示意图， 该实施 例包括接收模块 51和注册模块 52。 接收模块 51用于接收内容注册请求， 所 述内容注册请求中携带 UGC及与所述 UGC对应的担保凭证， 所述担保凭证 由第三方网络实体， 如待接收所述 UGC的网站生成； 注册模块 52用于根据 所述担保凭证对所述 UGC进行注册。
其中，接收模块 51可以用于接收用户发送的内容注册请求或者也可以接 收网站发送的内容注册请求。
注册模块 52 具体用于验证所述担保凭证的有效性， 若所述担保凭证有 效， 则验证所述用户生成内容的可申请性， 若所述用户生成内容可申请， 则 生成对应于所述用户生成内容的内容标识。 为了使网站合法公开 UGC, 注册 模块在生成内容标识的同时还可以生成认可凭证， 该认可凭证用于使待接收
UGC 的网站获知申请注册的内容已注册成功， 以便合法公开注册成功的 UGC。
本实施例由网站为 UGC提供担保凭证， 使 UGC可以实现内容注册， 并 且注册方法简单易行。
图 6为本发明用户生成内容的注册装置实施例二的结构示意图， 与实施 例一相比， 本实施例还包括发送模块 53 , 发送模块 53用于将注册模块 52产 生的内容标识和认可凭证直接发送给用户， 或者用于将所述内容标识和认可 凭证发送给网站。
本实施例由网站为 UGC提供担保凭证， 使 UGC可以实现内容注册， 并 且注册方法简单易行。 并且， 可以根据注册模式选择直接与用户交互或者选 择与网站进行交互， 使注册方式多样。
图 Ί为本发明用户生成内容的注册系统实施例一的结构示意图， 该实施 例包括网站 71和 CIM72。 网站 71用于接收用户发送的用户生成内容， 为所 述用户生成内容生成对应担保凭证； CIM72用于接收内容注册请求， 所述内 容注册请求中携带所述用户生成内容和身份标识， 根据所述身份标识对所述 用户生成内容进行注册。
本实施例由网站为用户提交的 UGC提供担保凭证， 使 UGC的注册方法 避免现有技术中存在的流程繁瑣、 成本高的问题。
图 8为本发明用户生成内容的注册系统实施例二的结构示意图， 与实施 例一相比，该实施例的网站 71具体包括身份标识模块 711、代理接收模块 712 和担保生成模块 713。 身份标识模块 711 用于为所述用户提供身份标识； 代 理接收模块 712用于接收用户发送的代理内容注册请求， 所述代理内容注册 请求中携带用户生成内容和所述身份标识的； 担保生成模块 713用于生成绑 定所述代理接收模块 712接收的用户生成内容和身份标识的担保凭证。
其中， 代理接收模块 712接收的所述代理内容注册请求中还携带注册模 式。 该网站还可以包括： 注册发送模块 714。 注册发送模块 714用于在所述 代理接收模块 712接收的注册模式表明注册采用用户自申请模式时， 将所述 担保生成模块 713生成的担保凭证发送给所述用户， 使所述用户在验证所述 担保凭证有效后， 向所述内容标识管理者发送所述内容注册请求； 或者所述 注册发送模块 714用于在所述注册模式表明注册采用网站直接代理模式时， 在所述担保生成模块生成担保凭证后， 直接向所述内容标识管理者发送所述 内容注册请求。
本实施例由网站为用户提交的 UGC提供担保凭证， 使 UGC的注册方法 避免现有技术中存在的流程繁瑣、 成本高的问题。 并且， 本实施例可以根据 用户选择的注册模式实现用户直接注册或有网站代理实现 UGC 的注册， 使 UGC的注册方法不仅简便易行， 还可以使实现方法多样。
最后应说明的是： 以上实施例仅用以说明本发明的技术方案而非对其进 行限制， 尽管参照较佳实施例对本发明进行了详细的说明， 本领域的普通技 术人员应当理解： 其依然可以对本发明的技术方案进行修改或者等同替换， 而这些修改或者等同替换亦不能使修改后的技术方案脱离本发明技术方案的 ^"神和范围。

Claims

权 利 要求
1、 一种用户生成内容的注册方法， 其特征在于， 包括：
接收内容注册请求， 所述内容注册请求中携带用户生成内容及与所述用 户生成内容对应的担保凭证， 所述担保凭证由第三方网络实体生成；
根据所述担保凭证对所述用户生成内容进行注册。
2、 根据权利要求 1所述的方法， 其特征在于， 所述第三方网络实体生成 所述担保凭证包括：
接收用户发送的代理内容注册请求， 所述代理内容注册请求中携带所述 用户生成内容；
生成对应于所述用户的身份标识；
生成所述担保凭证， 所述担保凭证用于绑定所述用户生成内容和身份标识。
3、 根据权利要求 2所述的方法， 其特征在于， 所述代理内容注册请求中 还携带注册模式， 所述注册模式表明注册采用用户自申请模式。
4、 根据权利要求 1所述的方法， 其特征在于， 所述接收内容注册请求具 体包括： 接收所述用户发送的内容注册请求； 所述第三方网络实体生成所述 担保凭证后发送给所述用户， 所述用户验证所述担保凭证有效后， 将所述担 保凭证携带在所述内容注册请求中。
5、 根据权利要求 2所述的方法， 其特征在于， 所述第三方网络实体为待 接收所述用户生成内容的网站， 所述代理内容注册请求中还携带注册模式， 所述注册模式表明注册采用网站直接代理模式。
6、 根据权利要求 5所述的方法， 其特征在于， 所述接收内容注姻请求具体包 括： 接收所述网站发送的内容注册请求； 所述网站在生成所述担保凭证后， 将所述担保凭证携带在所述内容注册请求中。
7、 根据权利要求 1所述的方法， 其特征在于， 根据所述担保凭证对所述 用户生成内容进行注册包括：
验证所述担保凭证的有效性； 若所述担保凭证有效， 则验证所述用户生成内容的可申请性； 若所述用户生成内容可申请， 则生成对应于所述用户生成内容的内容标识。
8、 根据权利要求 7所述的方法， 其特征在于， 还包括： 生成对应于所述 用户生成内容的认可凭证， 所述认可凭证用于使待接收所述用户生成内容的 网站获知内容注册成功。
9、 根据权利要求 8所述的方法， 其特征在于， 还包括：
接收用户上传的所述认可凭证和对应的用户生成内容或上传所述认可凭 证和对应的解密密钥，所述解密密钥用于解密预上传的加密的用户生成内容； 验证所述认可凭证的有效性， 若所述认可凭证有效， 则公布上传的用户 生成内容或公布预上传的根据所述解密密钥解密后的用户生成内容。
10、 根据权利要求 9所述的方法， 其特征在于， 还包括：
内容标识管理者将所述内容标识和认可凭证发送给用户； 所述认可凭证 通过所述用户的验证； 或者
内容标识管理者将所述内容标识和认可凭证发送给所述网站； 所述网站 验证所述认可凭证的有效性， 若所述认可凭证有效， 将所述内容标识、 认可 凭证和担保凭证发送给所述用户； 所述认可凭证和担保凭证通过所述用户的 验证。
11、 一种用户生成内容的注册装置， 其特征在于， 包括：
接收模块， 用于接收内容注册请求， 所述内容注册请求中携带用户生成 内容及与所述用户生成内容对应的担保凭证， 所述担保凭证由第三方网络实 体生成；
12、 根据权利要求 11所述的装置， 其特征在于： 所述注册模块具体用于 验证所述担保凭证的有效性， 若所述担保凭证有效， 则验证所述用户生成内 容的可申请性， 若所述用户生成内容可申请， 则生成对应于所述用户生成内 容的内容标识。
13、 根据权利要求 12所述的装置， 其特征在于， 所述注册模块还用于生 成对应于所述用户生成内容的认可凭证， 所述认可凭证用于使待接收所述用 户生成内容的网站获知内容注册成功。
14、 根据权利要求 13所述的装置， 其特征在于， 还包括： 发送模块， 用 于将所述内容标识和认可凭证发送给用户， 或者用于将所述内容标识和认可 凭证发送给网站。
15、 一种用户生成内容的注册系统， 其特征在于， 包括：
网站， 用于接收用户发送的用户生成内容， 为所述用户生成内容生成对 应的担保凭证；
内容标识管理者， 用于接收内容注册请求， 所述内容注册请求中携带所述 用户生成内容和担保凭证， 根据所述担保凭证对所述用户生成内容进行注册。
16、 根据权利要求 15所述的系统， 其特征在于， 所述网站包括： 身份标识模块， 用于为所述用户提供身份标识；
代理接收模块， 用于接收用户发送的代理内容注册请求， 所述代理内容 注册请求中携带用户生成内容和所述身份标识的；
担保生成模块，用于生成绑定所述用户生成内容和身份标识的担保凭证。
17、 根据权利要求 16所述的系统， 其特征在于：
所述代理接收模块接收的所述代理内容注册请求中还携带注册模式； 所述网站还包括注册发送模块；
所述注册发送模块用于在所述注册模式表明注册采用用户自申请模式 时， 将所述担保生成模块生成的担保凭证发送给所述用户， 使所述用户在验 证所述担保凭证有效后， 向所述内容标识管理者发送所述内容注册请求； 或 者
所述注册发送模块用于在所述注册模式表明注册采用网站直接代理模式 时， 在所述担保生成模块生成担保凭证后， 直接向所述内容标识管理者发送 所述内容注册请求。
PCT/CN2009/071752 2008-05-12 2009-05-12 用户生成内容的注册方法、装置和系统 Ceased WO2009138028A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP09745412A EP2262165B1 (en) 2008-05-12 2009-05-12 User generated content registering method, apparatus and system
US12/939,030 US20110093705A1 (en) 2008-05-12 2010-11-03 Method, device, and system for registering user generated content

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200810106367.6 2008-05-12
CNA2008101063676A CN101582876A (zh) 2008-05-12 2008-05-12 用户生成内容的注册方法、装置和系统

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US12/939,030 Continuation US20110093705A1 (en) 2008-05-12 2010-11-03 Method, device, and system for registering user generated content

Publications (1)

Publication Number Publication Date
WO2009138028A1 true WO2009138028A1 (zh) 2009-11-19

Family

ID=41318366

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2009/071752 Ceased WO2009138028A1 (zh) 2008-05-12 2009-05-12 用户生成内容的注册方法、装置和系统

Country Status (4)

Country Link
US (1) US20110093705A1 (zh)
EP (1) EP2262165B1 (zh)
CN (1) CN101582876A (zh)
WO (1) WO2009138028A1 (zh)

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20090011152A (ko) * 2007-07-25 2009-02-02 삼성전자주식회사 콘텐츠 제공 방법 및 시스템
KR101657442B1 (ko) * 2009-10-15 2016-09-13 인터디지탈 패튼 홀딩스, 인크 가입 기반 서비스에 액세스하기 위한 등록 및 크리덴셜 롤 아웃
US20120072982A1 (en) * 2010-09-17 2012-03-22 Microsoft Corporation Detecting potential fraudulent online user activity
KR101878682B1 (ko) * 2011-11-14 2018-07-18 삼성전자주식회사 컨텐츠를 보호하기 위한 방법 및 저장 매체
CN102752280B (zh) * 2012-05-16 2016-06-01 中国科学院计算机网络信息中心 域名注册处理方法、装置和系统
CN104252424B (zh) * 2013-06-26 2018-04-17 腾讯科技（深圳）有限公司 一种用户原创内容消息的缓存处理方法及装置
US10509921B2 (en) * 2017-05-31 2019-12-17 Intuit Inc. System for managing transactional data
CN109660546B (zh) * 2018-12-27 2021-05-07 泰华智慧产业集团股份有限公司 基于NetflixZuul的API网关实现鉴权的方法

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1411224A (zh) * 2001-09-29 2003-04-16 华为技术有限公司 一种pc客户端的安全认证方法
CN1588849A (zh) * 2004-07-02 2005-03-02 清华大学 一种基于数字权利管理的大规模数字直播方法
CN101047504A (zh) * 2006-03-29 2007-10-03 腾讯科技（深圳）有限公司 一种网站登录认证方法及认证系统

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6789188B1 (en) * 2000-02-07 2004-09-07 Koninklijke Philips Electronics N.V. Methods and apparatus for secure content distribution
JP4309629B2 (ja) * 2002-09-13 2009-08-05 株式会社日立製作所 ネットワークシステム
US7716243B2 (en) * 2005-02-25 2010-05-11 Microsoft Corporation Provisions for validating content using a content registration authority
US7617246B2 (en) * 2006-02-21 2009-11-10 Geopeg, Inc. System and method for geo-coding user generated content
US20070250526A1 (en) * 2006-04-24 2007-10-25 Hanna Michael S Using speech to text functionality to create specific user generated content metadata for digital content files (eg images) during capture, review, and/or playback process
US20070294222A1 (en) * 2006-06-15 2007-12-20 Nokia Corporation On-demand news service based on end-user requested and generated content
US20080005125A1 (en) * 2006-07-03 2008-01-03 Dewey Gaedeke System for displaying user generated content in a web browser
US20080005282A1 (en) * 2006-07-03 2008-01-03 Dewey Gaedcke Method for displaying user generated content in a web browser

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1411224A (zh) * 2001-09-29 2003-04-16 华为技术有限公司 一种pc客户端的安全认证方法
CN1588849A (zh) * 2004-07-02 2005-03-02 清华大学 一种基于数字权利管理的大规模数字直播方法
CN101047504A (zh) * 2006-03-29 2007-10-03 腾讯科技（深圳）有限公司 一种网站登录认证方法及认证系统

Also Published As

Publication number Publication date
EP2262165A4 (en) 2011-09-21
US20110093705A1 (en) 2011-04-21
EP2262165A1 (en) 2010-12-15
CN101582876A (zh) 2009-11-18
EP2262165B1 (en) 2012-12-05

Similar Documents

Publication Publication Date Title
US10027670B2 (en) Distributed authentication
US20210367795A1 (en) Identity-Linked Authentication Through A User Certificate System
CN106487743B (zh) 用于支持多用户集群身份验证的方法和设备
CN101521569B (zh) 实现服务访问的方法、设备及系统
WO2022121461A1 (zh) 一种云平台资源访问控制的令牌构造方法、装置及设备
CN106713279B (zh) 一种视频终端身份认证系统
CN102823217B (zh) 证书机构
WO2020062668A1 (zh) 一种身份认证方法、身份认证装置及计算机可读介质
WO2019233204A1 (zh) 密钥管理方法、装置、系统、存储介质和计算机设备
CN114008968B (zh) 用于计算环境中的许可授权的系统、方法和存储介质
CN105933315B (zh) 一种网络服务安全通信方法、装置和系统
CN108322469A (zh) 信息处理系统、方法和装置
WO2009138028A1 (zh) 用户生成内容的注册方法、装置和系统
MXPA04007546A (es) Metodo y sistema para proporcionar una tercera autenticacion de autorizacion.
KR101452708B1 (ko) Ｃｅ 장치 관리 서버, ｃｅ 장치 관리 서버를 이용한ｄｒｍ 키 발급 방법, 및 그 방법을 실행하기 위한프로그램 기록매체
JP5988747B2 (ja) 鍵管理装置、アプリケーション署名付加装置および受信端末、ならびに、それらのプログラム
CN114218548B (zh) 身份验证证书生成方法、认证方法、装置、设备及介质
CN114124441B (zh) 一种基于jwt的客户端认证方法及系统
CN101305542B (zh) 一种数字证书与密钥下载方法
TWI698113B (zh) 電子裝置之認證方法及系統
CN115242471A (zh) 信息传输方法、装置、电子设备及计算机可读存储介质
EP4455908A1 (en) Method for receiving content in user device over cdn
CN114266057B (zh) 一种数据分发方法及系统
JP2016115162A (ja) 認証システム、認証端末装置、登録端末装置、認証方法、及びプログラム
JP2025035942A (ja) データ構造、情報処理装置、情報処理方法、情報処理システム

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: 09745412

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2009745412

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE