WO2008037220A1 - Procédé, système et dispositif pour autoriser une émission de télévision en direct sur un canal par un réseau - Google Patents
Procédé, système et dispositif pour autoriser une émission de télévision en direct sur un canal par un réseau Download PDFInfo
- Publication number
- WO2008037220A1 WO2008037220A1 PCT/CN2007/070780 CN2007070780W WO2008037220A1 WO 2008037220 A1 WO2008037220 A1 WO 2008037220A1 CN 2007070780 W CN2007070780 W CN 2007070780W WO 2008037220 A1 WO2008037220 A1 WO 2008037220A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- entity
- bearer
- service
- user
- authorization
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client
- H04N21/63—Control signaling related to video distribution between client, server and network components; Network processes for video distribution between server and clients or between remote clients, e.g. transmitting basic layer and enhancement layers over different transmission paths, setting up a peer-to-peer communication via Internet between remote STB's; Communication protocols; Addressing
- H04N21/643—Communication protocols
- H04N21/64322—IP
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
- H04N21/25—Management operations performed by the server for facilitating the content distribution or administrating data related to end-users or client devices, e.g. end-user or client device authentication, learning user preferences for recommending movies
- H04N21/254—Management at additional data server, e.g. shopping server, rights management server
- H04N21/2541—Rights Management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
- H04N21/25—Management operations performed by the server for facilitating the content distribution or administrating data related to end-users or client devices, e.g. end-user or client device authentication, learning user preferences for recommending movies
- H04N21/258—Client or end-user data management, e.g. managing client capabilities, user preferences or demographics, processing of multiple end-users preferences to derive collaborative data
- H04N21/25808—Management of client data
- H04N21/25816—Management of client data involving client authentication
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
- H04N21/25—Management operations performed by the server for facilitating the content distribution or administrating data related to end-users or client devices, e.g. end-user or client device authentication, learning user preferences for recommending movies
- H04N21/258—Client or end-user data management, e.g. managing client capabilities, user preferences or demographics, processing of multiple end-users preferences to derive collaborative data
- H04N21/25808—Management of client data
- H04N21/25841—Management of client data involving the geographical location of the client
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client
- H04N21/61—Network physical structure; Signal processing
- H04N21/6106—Network physical structure; Signal processing specially adapted to the downstream path of the transmission network
- H04N21/6125—Network physical structure; Signal processing specially adapted to the downstream path of the transmission network involving transmission via Internet
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client
- H04N21/61—Network physical structure; Signal processing
- H04N21/6106—Network physical structure; Signal processing specially adapted to the downstream path of the transmission network
- H04N21/6131—Network physical structure; Signal processing specially adapted to the downstream path of the transmission network involving transmission via a mobile phone network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client
- H04N21/63—Control signaling related to video distribution between client, server and network components; Network processes for video distribution between server and clients or between remote clients, e.g. transmitting basic layer and enhancement layers over different transmission paths, setting up a peer-to-peer communication via Internet between remote STB's; Communication protocols; Addressing
- H04N21/64—Addressing
- H04N21/6405—Multicasting
Definitions
- the invention relates to the technical field of network live television service, in particular to a method, system and device for authorizing a network live television service channel. Background of the invention
- IP Internet Protocol
- the user equipment requests the channel to join or leave by sending an Internet Group Management Protocol (IGMP) message to the multicast router of the neighboring user on the network side, for example: requesting to view a certain message through an IGMP Join message.
- IGMP Internet Group Management Protocol
- the multicast router After receiving the IGMP join message, the multicast router forwards the corresponding channel program to the user equipment; the IGMP Leave message stops watching a certain channel, and the multicast router stops forwarding to the user equipment according to the received IGMP Leave message. program.
- NGN Next Generation Network
- PSTN Public Switched Telephone Network
- ISDN integrated services digital network
- IP narrowband networks Users, IP broadband network users and even users accessing via satellite can communicate with each other as a member of the NGN.
- the NGN network adopts a layered architecture and is divided into a service layer and a transport layer (bearer layer).
- the service layer implements specific services through the service control entity
- the transport layer (bearer layer) implements the transmission of specific content through the control entity.
- the IP Multimedia Services Subsystem is a component of the NGN network architecture defined by the 3rd Generation Partnership Project (3GPP) R5 or R6 standard and is attributed to the service control function.
- the IMS adopts the IP packet domain as the bearer channel for its control signaling and media transmission, and uses Session Initiation Protocol (SIP) as the call control signaling, which realizes the separation of service management, session control and bearer access.
- SIP Session Initiation Protocol
- the existing policy and charging control (PCC) architecture is shown in Figure 2.
- the PCC architecture includes: a subscription profile repository (SPR), an application function entity (AF), a policy and charging rules function (PCRF), including a policy and a meter.
- PCEF Policy and charging Enforcement Functions
- GW gateway
- OFCS Offline Charging System
- CAMEL Customized Application for Mobile Network Enhanced Logic
- SCP Service Control Point
- OCS Online Charging System
- the traditional billing system is divided into a flow-based billing system, and the policy control function in billing is not considered.
- policy control is integrated on the basis of flow-based charging.
- the PCRF combines the functions of the Policy Decision Function Entity (PDF) to implement policy control.
- PDF Policy Decision Function Entity
- Specific business related information is obtained through SPR.
- the SPR stores the subscription information of the user, which is equivalent to the database of the bearer layer.
- the digital subscriber line is a commonly used broadband access method
- ADSL Asymmetric Digital Subscriber Line
- DSL Asymmetric Digital Subscriber Line
- DSL Digital Subscriber Line Access Multiplexer
- BRAS Broadband Remote Access Server
- IGMP joins or leaves the request to join or leave a channel After receiving the IGMP join request, the multicast router of the neighboring user terminal in the network directly forwards the program of the corresponding channel to the terminal device, and does not authorize the user. Similarly, when the group When the broadcast router receives the IGMP Leave message, if it finds that the user is the last user to watch the channel, the program of the channel is no longer forwarded, and the user is not authorized to judge.
- the network entity responsible for processing the relevant IGMP message such as a multicast router, does not determine the authority of the user's IGMP message. Therefore, a user who does not have permission to view a certain program can send the IMGP. Adding a message and illegally watching a TV program caused the theft of the live TV service. Similarly, malicious users can also send IGMP leave messages, so that legitimate users cannot continue to watch TV programs, thus affecting the normal deployment of the live TV service and reducing the user experience.
- the embodiment of the present invention provides a method for authorizing a channel for a live broadcast television service to implement authorization for a channel request for a live broadcast television service.
- Another object of an embodiment of the present invention is to provide a system for performing network live television service channel authorization.
- Still another object of embodiments of the present invention is to provide an apparatus for performing network live television service channel authorization.
- an embodiment of the present invention provides a method for performing network channel authorization for a live television service, and the method includes the following steps:
- the authorized entity determines the authorization of the channel request according to the user rights information
- the host entity is required to execute the channel of the terminal device. begging.
- the embodiment of the invention further provides a system for authorizing a network live television service channel, the system comprising:
- An authorization entity configured to perform authorization judgment on a channel request of the terminal device according to the user authority information
- the bearer entity is configured to perform a channel request of the terminal device if the authorization is passed.
- the embodiment of the invention further provides a device for authorizing a network live television service channel, the device comprising:
- a receiving unit configured to receive a channel request of the terminal device for the network live television service, and forward the request to the authorization determining unit;
- the authorization judging unit is configured to perform authorization judgment on the channel request according to the user authority information.
- the embodiment of the present invention is based on the NGN network, a method, system and device for channel request authorization judgment for users of the network live television service are proposed.
- the authorized entity authorizes the channel request, and executes the user's channel request only when the authorization is passed, otherwise the user's channel request is rejected, thereby avoiding the unauthorized access of the channel program by the unauthorized user in the prior art.
- the problem is also to avoid the problem of maliciously sending away messages that prevent legitimate users from continuing to watch channel programs.
- the embodiment of the present invention closely combines the characteristics of the NGN network with the establishment process of the network live television service, solves the problem of user channel authorization, and lays a foundation for the deployment of the network live television service in the NGN network.
- Figure 1 is a schematic diagram of the network architecture of the NGN
- 2 is a schematic diagram of a network architecture of a PCC
- 3 is a schematic diagram of a process of joining or leaving a certain channel of a live network television service in the prior art
- FIG. 4 is a schematic structural diagram of a system according to an embodiment of the present invention.
- FIG. 5 is a schematic flowchart of an embodiment of the present invention.
- FIG. 6 is a schematic flow chart of another embodiment of the present invention.
- FIG. 7 is a schematic flow chart of a first embodiment of the present invention.
- FIG. 8 is a schematic flow chart of a second embodiment of the present invention.
- FIG. 9 is a schematic flow chart of a third embodiment of the present invention.
- FIG. 10 is a schematic flowchart of a fourth embodiment of the present invention.
- FIG. 11 is a schematic flow chart of a fifth embodiment of the present invention.
- FIG. 12 is a schematic structural diagram of an authorization entity in an embodiment of the present invention. Mode for carrying out the invention
- the core idea of the embodiment of the present invention is that the service layer entity obtains user rights information according to the channel request of the user, and uses some user identifier to perform index identification, and then passes the user rights information.
- the static configuration is dynamically transmitted to the bearer layer entity, and the bearer layer entity determines the user channel request according to the request, that is, only performs the corresponding channel request to the authorized user, and rejects the channel request of the unauthorized user.
- the authorization of the user channel request may be directly performed by the service layer entity. If the authorization is passed, the bearer entity is notified to perform the channel request of the user, otherwise the channel request of the user is rejected.
- the authorization entity may be a bearer layer entity or a service layer entity, and the authorization entity authorizes the channel request from the terminal device according to the user authority information, and if the authorization is passed, The frequency of the terminal device is performed by the bearer entity Road request.
- a system includes: a terminal device; a service layer entity including a service entity and a service control entity; and a bearer layer entity including a bearer entity and a bearer control entity.
- the system may further include a database that is directly or indirectly connected to the bearer control entity.
- the terminal device is used to initiate a channel request, for example: requesting a program stream of a channel, leaving a channel, or joining a channel.
- the bearer control entity is SPDF or A-RACF in Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN), PDF in 3GPP or PCEF in PCC system. .
- the database in Tispan is an entity in a Network Attachment Sub-System (NASS), such as CLF, PDBF; or SPDF in RACF, or A-RACF; or SPR in PCC; or A separate database connected to the bearer control entity.
- NASS Network Attachment Sub-System
- the entities in Figure 4 add some functionality compared to the prior art.
- the functions added by the business entity are: receiving channel requests from the terminal device, and obtaining user rights information.
- the functions added by the service control entity are: forwarding user rights information to the bearer control entity, and converting the service layer identifier and the bearer layer identifier.
- the service layer identifier is, for example, a public user identifier (IMPU), and the bearer layer identifier is an IP address or the like.
- the functions added by the bearer control entity are as follows: The receiving service layer sends the user rights information, performs the association between the user rights information and the user bearer layer channel request, and judges the user authorization.
- the functions added by the bearer entity are as follows: Receiving user rights information delivered by the service layer, associating user rights information with user bearer layer channel requests, and determining user authorization.
- a database directly or indirectly connected to the bearer control entity is also introduced in the prior art architecture, and the database is mainly used to store user rights information corresponding to the user.
- the II interface between the service entity and the service control entity the 12 interface between the service control entity and the bearer control entity, the bearer control entity and the bearer entity between the 13 interfaces, the user rights information can be queried and delivered.
- the 14 interface between the bearer control entity and the database can implement the query and response of the user rights information.
- the above II, 12, 13, and 14 interfaces may be newly added interfaces, or may be implemented by using an existing interface. Based on the foregoing architecture, the embodiment of the present invention provides a manner in which two bearer layer entities perform authorization judgment.
- the bearer and the service are separated.
- the service layer entity obtains the user's channel authority according to the user request, and uses some user identifier to perform the index.
- the user's channel authority information can be statically configured and dynamically transmitted to the bearer layer entity.
- the bearer layer entity determines the user channel authority accordingly, that is, only performs the corresponding request to the authorized user, and rejects the request of the unauthorized user.
- the specific bearer layer entity may be a bearer entity or a bearer control entity, where the bearer entity such as DSLAM, BRAS, General Packet Radio Service (GPRS) Gateway Support Node (GGSN), Broadcast Multicast Service (BCMCS) support node (BCMCS Support Node) , BSN), IP Encapsulation Entity (IPE), etc., bearer control entities such as Business Policy Decision Function Entity (SPDF), Policy Decision Function (PDF) Entity, PCEF, etc.
- the bearer entity such as DSLAM, BRAS, General Packet Radio Service (GPRS) Gateway Support Node (GGSN), Broadcast Multicast Service (BCMCS) support node (BCMCS Support Node) , BSN), IP Encapsulation Entity (IPE), etc.
- bearer control entities such as Business Policy Decision Function Entity (SPDF), Policy Decision Function (PDF) Entity, PCEF, etc.
- the method shown in Figure 5 is to deliver the user rights information to the bearer layer entity of the bearer entity.
- the method shown in Figure 6 is to send the user rights to the database, and the bearer control entity performs authorization judgment.
- Step 101 The terminal device initiates a channel request to the service entity by using the service control entity.
- Step 102 The business entity obtains specific user rights information.
- Step 103 The service entity delivers the service authority of the user, that is, the user authority information, to the bearer entity by using the bearer control entity.
- Step 104 The bearer entity saves the service authority of the delivered user.
- the user's business Service permissions can also be statically configured to the carrier layer entity.
- Step 105 The bearer entity notifies the service entity that the user rights are successfully sent, and may further notify the terminal device.
- Step 106 The user requests a service from the terminal device to the bearer entity through the bearer.
- Step 107 to step 108 the bearer entity performs authorization judgment on the user according to the saved user authority, performs a corresponding request on the authorized user, and rejects the request of the unauthorized user.
- the flow of the method shown in Figure 6 is as follows:
- Step 201 The terminal device requests a service from the service entity by using the service control entity.
- Step 202 The business entity obtains the service authority of the user.
- Step 203 The service entity sends the service authority of the user to the bearer control entity, and the bearer control entity sends the user service authority to the database.
- Step 204 The database saves the user service authority issued by the database.
- the user's business rights can also be statically configured to the database.
- Step 205 The database notifies the service entity that the user rights are successfully sent, and may further notify the terminal device.
- Step 206 The user requests a service from the terminal device to the bearer entity by using the bearer.
- Step 207 The bearer entity sends a service authorization request to the bearer control entity.
- Step 208 The bearer control entity interacts with the database to obtain the user service authority.
- Step 209 The bearer control entity determines the user's authority according to the obtained user service authority, and sends a channel request to the bearer entity through the service authorization response.
- Step 210 The bearer entity performs a corresponding request on the authorized user according to the authorization result, and rejects the request of the unauthorized user.
- the bearer entity forwards the IGMP message from the user equipment to the bearer control entity; in a subsequent step, the bearer control entity performs an authorization judgment, and notifies the bearer entity whether to allow the The user's channel join request.
- the user first requests the media stream from the bearer plane entity such as the DSLAM or the GGSN through the IGMP message at the beginning of the step 106 or the step 206. If the bearer entity has the authority of the user, The authorization judgment is directly performed, which is equivalent to step 107 to step 108; if not, the bearer plane entity requests channel authorization from the bearer control entity such as SPDF or PDF.
- the bearer plane entity such as the DSLAM or the GGSN
- the authorization judgment is directly performed, which is equivalent to step 107 to step 108; if not, the bearer plane entity requests channel authorization from the bearer control entity such as SPDF or PDF.
- the bearer control entity saves the user's channel authority, the authorization judgment is directly performed, which is equivalent to step 208 to step 211; if not, the bearer control entity initiates a request to the service layer, requests the user channel authority, and obtains the channel authorization judgment after obtaining .
- the bearer entity can also initiate a request to the service layer through an interface with the service plane, such as the Gmb interface in Multimedia Broadcast Multicast (MBMS), request the user channel authority, and perform channel authorization judgment after obtaining.
- MBMS Multimedia Broadcast Multicast
- the first embodiment is: in the xDSL network, the user's channel authority information is statically configured or dynamically sent to the DSLAM or the BRAS; when the DSLAM or the BRAS receives the IGMP message, the user channel request authorization judgment is performed according to the above permission information.
- Fig. 7 is a flow chart showing the first embodiment.
- the entities involved include: Set Top Box (STB), Proxy Call Session Control Function Entity (P-CSCF), Application Server (AS), User Profile Server Function (UPSF) ), Business Policy Decision Functional Entity (Service Policy Decision) Function, SPDF), Access-Resource Admission Control Function (A-RACF) and DSLAM or BRAS.
- STB Set Top Box
- P-CSCF Proxy Call Session Control Function Entity
- AS Application Server
- UPSF User Profile Server Function
- SPDF Service Policy Decision
- A-RACF Access-Resource Admission Control Function
- DSLAM or BRAS DSLAM or BRAS.
- Step 301 The STB sends a SIP request or a SIP Invite or Subscribe message to the AS to request or subscribe to a specific channel.
- Step 302 If the user rights information is stored in the UPSF, the AS obtains the channel rights information subscribed by the user to the UPSF.
- Step 303 The AS sends the channel authority information to the P-CSCF.
- Step 304 The P-CSCF forwards the above message to the SPDF.
- Step 305 to step 305 the SPDF acquires the user physical location information from the network attached sub-system (NASS) according to the IP address of the STB. NASS returns the user's physical location information to the SPDF, such as the line ID (LineID).
- NSS network attached sub-system
- the NASS here is the network attachment system in TISPAN. If it is in ITU-T, the network attachment system is the Network Attachment Control Function Entity (NACF).
- NACF Network Attachment Control Function Entity
- Step 306 The SPDF sends the channel authority information to the DSLAM or the BRAS where the user is located through the A-RACF according to the obtained physical location information.
- Step 307 The DSLAM or the BRAS may further store the user rights information by using a certain keyword as an index, such as an IP address or a physical location identifier.
- step 308 the DSLAM or the BRAS can further send a message for successfully issuing the rights to the STB through the P-CSCF.
- Step 309 The STB sends an IGMP join message to the DSLAM or the BRAS to request a certain channel.
- Step 310 The DSLAM or the BRAS performs authorization determination according to the saved channel authority information, and may be associated by LinelD or by an IP address.
- Step 311 If the user authorizes to pass, forward the program stream of the channel requested by the user. Such as If it fails, the user's request is rejected.
- step 304 to step 305 may also be:
- the P-CSCF queries the NASS and obtains the physical location information of the user, and then the P-CSCF forwards the channel authority information and the physical location information to the SPDF.
- step 307 after receiving the delivered user right, the bearer entity DSLAM or BRAS needs to use a certain keyword as an index to save the rights information, so that after receiving the IGMP message of the user, the IGMP message is sent in step 310.
- the assigned channel permissions are associated, and the channel permissions corresponding to the user are found, rather than the channel permissions of other users.
- the keyword may be a physical location identifier, such as the LinelD of the DSLAM, or the IP address of the user. If only the user's IP address is used, step 305 to step 305 may not be performed.
- Second Embodiment In an xDSL network, channel rights are statically configured or dynamically sent to a database in the SPDF or bearer layer. When the DSLAM or BRAS receives the IGMP message, it requests the SPDF or the database of the bearer layer to verify the channel rights of the user.
- the flow of the second embodiment is as shown in FIG. Referring to Figure 8, the process includes:
- Step 401 The STB sends a SIP Invite or Subscribe message to the AS to request or subscribe to a specific channel.
- Step 402 If the user rights information is stored in the UPSF, the AS obtains the channel rights information subscribed by the user to the UPSF.
- Step 403 The AS sends the channel authority information to the P-CSCF.
- Step 404 to step 404 the P-CSCF obtains the user physical location information from the NASS according to the IP address.
- the NASS returns the user's physical location information to the P-CSCF, such as the LinelD identifier.
- Step 405 The P-CSCF channel authority information and the physical location information are forwarded to the SPDF, and the SPDF is forwarded to the database.
- Step 406 The database is indexed by a certain keyword, such as an IP address or a physical location identifier. Knowledge, save user permission information.
- a certain keyword such as an IP address or a physical location identifier. Knowledge, save user permission information.
- Step 406 The database sends a message for successfully issuing the rights to the STB through the P-CSCF.
- Step 407 The STB sends an IGMP join message to the DSLAM to request a certain channel.
- Step 409 to step 409 the SPDF requests the user service authority from the database, and the database returns the user service authority information to the SPDF.
- Step 410 The SPDF performs a permission judgment on the user according to the returned user service authority information.
- step 411 the SPDF will authorize the result, that is, whether the channel request of the user is allowed to be sent to the DSLAM.
- Step 412 The DSLAM performs corresponding operations according to the authorization result, that is, if the user authorizes the passage, the program stream of the channel requested by the user is forwarded to the STB, otherwise the request of the unauthorized user is rejected.
- the third embodiment is: in the PCC architecture, the channel authority is statically configured or dynamically sent to the SPR; when the GGSN receives the IGMP message, it requests the PCEF to verify the channel authority of the user, and the PCEF obtains the channel authority information of the user from the SPR. Perform channel authorization judgment.
- the PCEF can also be a PDF. The following description uses PCEF as an example.
- the flow of the third embodiment is shown in FIG. 9. Referring to FIG. 9, the flow includes:
- Step 501 The terminal device sends a SIP Invite or Subscribe message to the AS to request or subscribe to a specific channel.
- Step 502 If the subscription information is stored in the HSS, the AS acquires the channel authority information subscribed by the user to the HSS.
- Step 503 The AS sends the channel authority information to the P-CSCF.
- Step 504 The P-CSCF performs a conversion between the service layer identifier and the bearer layer identifier.
- the service layer identifier is an IMPU
- the 7 layer identifier is an IP address.
- Step 505 The P-CSCF sends the channel authority information to the SPR through the PCRF or the PDF, and carries the bearer layer identifier, such as an IP address.
- Step 506 The SPR saves user rights information by using a bearer layer identifier, such as an IP address, as an index.
- Step 507 The terminal sends an IGMP join message to the GGSN to request a certain channel.
- Step 509 to step 509 the PCRF or the PDF carries the carrier layer identifier, requests the user service authority from the SPR, and the SPR returns the user service authority information to the PCRF or the PDF.
- Step 510 The PCRF or the PDF determines the authority of the user according to the returned user service authority information.
- Step 511 the PCRF or PDF sends the authorization result, that is, whether the user's channel request is allowed to be sent to the GGSN.
- Step 512 The GGSN performs corresponding operations according to the authorization result, that is, if the user authorizes to pass, the program stream of the channel requested by the user is forwarded to the terminal, otherwise the request of the unauthorized user is rejected.
- the channel authority in the PCC architecture, is statically configured or dynamically sent to the PCEF or PDF; when the GGSN receives the IGMP message, it requests the PCEF or PDF to verify the channel rights of the user, and the PCEF or PDF is saved according to the Channel permission information, for channel authorization judgment.
- Step 601 The terminal sends a SIP Invite or Subscribe message to the AS to request or subscribe to a specific channel.
- Step 602 If the user rights information is stored in the HSS, the AS obtains the channel rights information subscribed by the user to the HSS.
- Step 603 The AS sends the channel authority information to the P-CSCF.
- Step 604 The P-CSCF performs a conversion between the service layer identifier and the bearer layer identifier.
- the service layer identifier is an IMPU
- the 7 layer identifier is an IP address.
- Step 605 The P-CSCF sends the channel authority information to the PCRF or PDF, and carries a 7-layer identifier, such as an IP address.
- Step 606 The PCRF or the PDF stores the user authority information by using a layer identifier such as an IP address as an index.
- Step 606 the PCRF or the PDF sends a message to the terminal through the P-CSCF to successfully send the permission.
- Step 607 The terminal sends an IGMP join message to the GGSN to request a certain channel.
- Step 609 The PCRF or the PDF determines the authority of the user according to the saved user service authority information.
- Step 610 The PCRF or PDF sends the authorization result, that is, whether the user's channel request is allowed to be sent to the GGSN.
- Step 611 The GGSN performs corresponding operations according to the authorization result, that is, if the user authorizes to pass, the program stream of the channel requested by the user is forwarded to the terminal, otherwise the request of the unauthorized user is rejected.
- the PCEF may also carry the locally generated session identifier to the user in the channel request response, and the user carries the IGMP request.
- the session identifier so that when the GGSN requests authorization from the PCEF, the PCEF can associate by the session identifier.
- the PCEF may carry its own identifier in the channel request response, so that when the GGSN requests authorization from the PCEF, the GGSN may request the authorization by using the identifier of the PCEF. Sent to the PCEF.
- the bearer layer does not trigger the service through the IGMP message, and the service layer directly controls the bearer layer entity to authorize the user.
- Step 701 The STB sends a SIP Invite or Subscribe message to the service entity AS to request or subscribe to a channel.
- Step 702 The AS acquires channel rights information subscribed by the user from the UPSF.
- Step 703 The AS performs authorization judgment on the user according to the obtained channel authority information. If yes, the AS is notified in the following process that the bearer layer entity forwards the media stream requested by the user to the user. Otherwise, the user's request is rejected.
- Step 704 The AS sends a message to the P-CSCF, where the message is used to notify the bearer entity user to request a certain channel and authorize the passage.
- Step 705 The P-CSCF forwards the foregoing message to the control entity SPDF.
- Step 707 the SPDF notification 7 carries the entity DSLAM or the BRAS user requests a certain channel and authorizes the passage, and the notification message also carries the user physical location information.
- step 708 the DSLAM or the BRAS may save the user rights information or not.
- Step 709 The DSLAM or the BRAS sends a user authorization success response message to the STB through the P-CSCF, or may not send the message.
- Step 710 because the user authorization is passed, the DSLAM or BRAS forwards the program stream of the channel requested by the user to the STB.
- the rights information stored in the HSS or the UPSF user of the user's channel rights information may also have other storage manners, such as being stored in the service entity AS, where the AS locally obtains the rights information; or On a separate database, the AS obtains permission information from the database.
- FIG. 12 is a schematic structural diagram of an authorized entity in an embodiment of the present invention.
- the authorized entity is a device for performing network live television service channel authorization.
- the authorization entity includes at least a receiving unit and an authorization judging unit.
- the receiving unit receives the channel request of the terminal device for the network live television service, and sends the channel request to the authorization judging unit, and the authorization judging unit performs authorization judgment on the channel request according to the user authority information.
- the authorization entity further includes a sending unit, where the sending unit notifies the bearer entity to perform the channel request if the result of the authorization determining unit is authorized to pass .
- the above-mentioned sending unit is not required, but further includes a service executing unit, which is not shown in the figure.
- the service execution unit is configured to execute the channel request if the result of the authorization determination unit is authorization to pass.
- the authorization entity may further include a user rights information obtaining unit, configured to obtain the user rights information from the outside, and provide the information to the authorization determining unit.
- a user rights information obtaining unit configured to obtain the user rights information from the outside, and provide the information to the authorization determining unit.
- the user rights information acquiring unit performs different specific operations.
- the user rights The limit information obtaining unit is configured to obtain the user right information from the HSS or the UPSF; in the case that the authorized entity is the bearer control entity, the user right information acquiring unit is configured to request the user layer or the database to obtain the user right information;
- the user rights information obtaining unit is configured to request the user layer or the database to obtain the user rights information by using the bearer control entity, and may also directly request the user layer to obtain the user rights information.
- the authorization entity may further include a user rights information storage unit, where the user rights information storage unit is configured to save the user rights information and provide the authorization authority.
Landscapes
- Engineering & Computer Science (AREA)
- Multimedia (AREA)
- Signal Processing (AREA)
- Databases & Information Systems (AREA)
- Computer Security & Cryptography (AREA)
- Computer Graphics (AREA)
- Computer Networks & Wireless Communication (AREA)
- Mobile Radio Communication Systems (AREA)
Description
进行网络直播电视业务频道授权的方法、 系统及装置 技术领域
本发明涉及网络直播电视业务技术领域, 特别是进行网络直播电视 业务频道授权的方法、 系统及装置。 发明背景
随着因特网技术的发展, 近年来迅速发展起来了将传统电视业务引 入到因特网协议(IP ) 网络中的网络直播电视业务。
在传统的网络直播电视业务中, 用户设备通过发送因特网组管理协 议( IGMP ) 消息给网络侧邻近用户的组播路由器, 请求频道的加入或 者离开, 例如: 通过 IGMP加入(Join ) 消息请求观看某个电视频道, 组播路由器收到 IGMP加入消息后转发相应的频道节目给用户设备; 通 过 IGMP离开(Leave )消息停止观看某个频道, 组播路由器根据收到的 IGMP离开消息停止向用户设备转发节目。
下一代网络(NGN ) 于分组技术的综合型网络, 以分组交换为 主, 采用承载与控制分离的架构。 NGN 继承了原有公用电话交换网 ( PSTN )的所有业务, 同时也继承了移动网络的业务能力。 因此, NGN 综合了固定电话网、 移动电话网和 IP网络的优势, 使得模拟用户、 数字 用户、 移动用户、 非对称数字用户线路(ADSL )用户、 综合业务数字 网 (ISDN )用户、 IP窄带网络用户、 IP宽带网络用户甚至是通过卫星 接入的用户都能作为 NGN中的一员相互通信。
如图 1所示, NGN网络采用分层架构, 分为业务层和传送层(承载 层)。 业务层通过业务控制实体实现具体的业务, 传送层(承载层)通 过^载控制实体实现具体内容的传送。
IP 多媒体业务子系统(IMS )是第三代合作伙伴计划 (3GPP ) R5 或 R6标准定义的 NGN网络架构中的一个组件, 归属于业务控制功能。 IMS采用 IP分组域作为其控制信令和媒体传输的承载通道,采用会话发 起协议(SIP )作为呼叫控制信令, 实现了业务管理、 会话控制及承载接 入的三者分离。
另外, 现有的策略和计费控制 ( policy and charging control, PCC ) 架构如图 2所示。参见图 2, PCC架构包括: 订阅信息仓库(subscription Profile repository, SPR )、 应用功能实体 ( Application Function , AF )、 策略和计费规则功能实体( Policy and charging Rules Functions, PCRF ), 包括策略和计费规则功能实体 ( Policy and charging Enforcement Functions , PCEF )的网关( GW )、离线计费系统( Offline Charging System , OFCS ) 以及包括移动网络增强逻辑的客户化应用 ( Customized Application for Mobile network Enhanced Logic , CAMEL )业务控制点 ( SCP )和基于信用控制的服务数据流( Service Data Flow Based Credit Control ) 的在线计费系统 ( Online Charging System, OCS )。
传统的计费系统分为基于流的计费系统, 没有考虑计费中的策略控 制功能。 如图 2所示的 PCC系统中, 在基于流进行计费的基础上, 和策 略控制融合到一起。 此时 PCRF融合了策略决策功能实体(PDF ) 的功 能, 进行策略控制。 具体的业务相关信息通过 SPR获取。 SPR存储用户 的订阅信息, 相当于承载层的数据库。
另外, 数字用户线路(xDSL )是目前常用的一种宽带接入方式, 其 中常见的有非对称数字用户线路(ADSL )等。 xDSL网络中主要有两种 接入设备: 数字用户线路接入复用器(DSLAM )和宽带远程接入服务 器(BRAS ), 负责把用户接入到网络中。 这两种设备对应到 NGN网络 中, 都属于承载层设备。
如图 3所示, 在现有系统中, 终端设备直接通过向组播路由器发送
IGMP加入或者离开请求来加入或退出某个频道, 网络中邻近用户终端 的组播路由器收到 IGMP加入请求后, 直接转发相应频道的节目给终端 设备, 并不对用户进行授权判断, 同样, 当组播路由器收到 IGMP离开 消息时, 如果发现该用户是最后一个收看该频道的用户, 则不再转发该 频道的节目, 也没有对用户进行授权判断。
由于用户通过 IGMP协议加入或者离开某个频道时, 组播路由器等 负责处理相关 IGMP消息的网络实体不对用户的 IGMP消息进行权限的 判别, 所以一个没有权限观看某个节目的用户, 可以通过发送 IMGP加 入消息而非法收看电视节目, 引起网络直播电视业务的盗用。 同样, 恶 意用户也可以通过发送 IGMP离开消息, 使得合法的用户无法继续观看 电视节目, 从而影响网络直播电视业务的正常部署, 降低了用户的业务 体验。 发明内容
有鉴于此, 本发明实施例提出了一种进行网络直播电视业务频道授 权的方法, 用以实现对网络直播电视业务频道请求的授权。 本发明实施 例的另一个目的在于, 提出一种进行网络直播电视业务频道授权的系 统。 本发明实施例的再一个目的是, 提出一种进行网络直播电视业务频 道授权的装置。
根据上述目的, 本发明实施例提供了一种网络进行直播电视业务频 道授权的方法, 该方法包括以下步骤:
授权实体在业务实体接收到终端设备对网络直播电视业务的频道请 求之后, 根据用户权限信息对所述频道请求进行授权判断;
授权实体在授权通过的情况下, 使承载实体执行终端设备的频道请
求。
本发明实施例还提供了一种进行网络直播电视业务频道授权的系 统, 该系统包括:
授权实体, 用于根据用户权限信息, 对终端设备的频道请求进行授 权判断;
承载实体, 用于在授权通过的情况下, 执行终端设备的频道请求。 本发明实施例还提供了一种进行网络直播电视业务频道授权的装 置, 该装置包括:
接收单元, 用于接收终端设备对网络直播电视业务的频道请求, 并 转发给授权判断单元;
授权判断单元, 用于根据用户权限信息对所述频道请求进行授权判 断。
从上述方案中可以看出, 由于本发明实施例基于 NGN 网络, 提出 了对网络直播电视业务的用户进行频道请求授权判断的方法、 系统和装 置。 通过本发明实施例的实施, 授权实体对频道请求进行授权, 在授权 通过的情况下才执行用户的频道请求, 否则决绝用户的频道请求, 避免 了现有技术中无权限用户非法收看频道节目的问题, 还能避免恶意发送 离开消息导致合法用户无法继续收看频道节目的问题。 因此, 本发明实 施例把 NGN网络的特点和网络直播电视业务的建立过程紧密结合到一 起, 解决了用户频道授权的问题, 为网络直播电视业务在 NGN网络中 的部署奠定了基础。 附图简要说明
图 1为 NGN的网络架构示意图;
图 2为 PCC的网络架构示意图;
图 3为现有技术加入或离开网络直播电视业务某个频道的流程示意 图;
图 4为本发明实施例的系统结构示意图;
图 5为本发明一种实施方式的流程示意图;
图 6为本发明另一种实施方式的流程示意图;
图 7为本发明第一实施例的流程示意图;
图 8为本发明第二实施例的流程示意图;
图 9为本发明第三实施例的流程示意图;
图 10为本发明第四实施例的流程示意图;
图 11为本发明第五实施例的流程示意图;
图 12为本发明实施例中授权实体的结构示意图。 实施本发明的方式
为使本发明的目的、 技术方案和优点更加清楚, 以下举实施例对本 发明进一步详细说明。
由于在 NGN 中, 承载和业务相分离, 因此本发明实施例的核心思 想是, 业务层实体根据用户的频道请求获取用户权限信息, 并采用某种 用户标识进行标识索引, 然后将用户权限信息通过静态配置、 动态传送 给承载层实体, 承载层实体据此进行用户频道请求的判断, 即只对授权 的用户执行相应的频道请求, 拒绝未授权用户的频道请求。 另外, 本发 明实施例还可以由业务层实体直接进行用户频道请求的授权判断, 如果 授权通过, 则通知承载实体执行用户的频道请, 否则拒绝该用户的频道 请求。 也就是说, 在本发明实施例中, 授权实体可以是承载层实体, 也 可以是业务层实体, 授权实体根据用户权限信息对来自终端设备的频道 请求进行授权, 并在授权通过的情况下, 由承载实体执行终端设备的频
道请求。
如图 4所示, 根据本发明实施例的系统包括: 终端设备; 包括业务 实体和业务控制实体的业务层实体; 包括承载实体和承载控制实体的承 载层实体。 该系统还可以进一步包括与承载控制实体直接或者间接相连 接的数据库。 其中, 终端设备用于发起频道请求, 例如: 请求频道的节 目流、 离开频道或加入频道。 所述承载控制实体在电信和互联网融合业 务及高级网给协议 ( Telecommunications and Internet converged Services and Protocols for Advanced Networking , TISPAN ) 中为 SPDF 或者 A-RACF、 在 3GPP中为 PDF或者在 PCC系统中为 PCEF。 所述数据库 在 Tispan中为网络附着子系统( Network Attachment Sub-System, NASS ) 中的实体, 如 CLF、 PDBF; 或者为 RACF中的 SPDF, 或者 A-RACF; 或者为 PCC中的 SPR; 或者为与承载控制实体相连的独立的数据库。
与现有技术相比, 图 4中的各实体增加了一些功能。 业务实体增加 的功能有: 接收终端设备的频道请求, 以及获取用户权限信息。 业务控 制实体增加的功能有: 转发用户权限信息给承载控制实体, 以及进行业 务层标识和承载层标识的转换。 所述业务层标识如公有用户标识 ( IMPU )等, 所述承载层标识如 IP地址等。 承载控制实体增加的功能 有: 接收业务层下发用户权限信息, 进行用户权限信息和用户承载层频 道请求的关联, 以及进行用户授权的判断。 承载实体增加的功能有: 接 收业务层下发的用户权限信息, 进行用户权限信息和用户承载层频道请 求的关联, 以及进行用户授权的判断。 另外, 在现有技术的架构上还引 入了和承载控制实体直接或者间接相连的数据库, 该数据库主要用于存 储与用户对应的用户权限信息。
在如图 4所示的系统中, 业务实体与业务控制实体之间的 II接口、 业务控制实体与承载控制实体之间的 12接口、承载控制实体与承载实体
之间 13接口能够实现用户权限信息的查询与下发。承载控制实体与数据 库之间的 14接口能够实现用户权限信息的查询与响应。上述 II、 12、 13、 14接口可以是新增加的接口, 也可以是利用已有的接口实现上述功能。 基于上述架构, 本发明实施例给出两种承载层实体进行授权判断的 方式。
NGN网络环境中, 承载和业务分离, 业务层实体根据用户请求获取 用户的频道权限, 并采用某种用户标识进行标识索引。 该用户的频道权 限信息可以静态配置、 动态传送给承载层实体, 承载层实体据此进行用 户频道权限的判断, 即只对授权的用户执行相应的请求, 拒绝未授权用 户的请求。
具体的承载层实体可以为承载实体或者承载控制实体, 其中承载实 体如 DSLAM、: BRAS、通用分组无线服务( GPRS )网关支撑节点( GGSN )、 广播多播业务(BCMCS ) 支撑节点 ( BCMCS Support Node, BSN )、 IP 封装实体(IPE )等, 承载控制实体如业务策略决策功能实体(SPDF )、 策略决策功能(PDF ) 实体、 PCEF等。
图 5 所示的方式是将用户权限信息下发到承载实体这一承载层实 体。 而图 6所示的方式是将用户权限下发到数据库, 并由承载控制实体 进行授权判断。
图 5所示方式的流程如下:
步骤 101 , 终端设备通过业务控制实体向业务实体发起频道请求。 步骤 102, 业务实体获得具体的用户权限信息。
步骤 103, 业务实体通过承载控制实体向承载实体下发用户的业务 权限, 即用户权限信息。
步骤 104, 承载实体保存所下发的用户的业务权限。 当然用户的业
务权限也可以静态配置到承载层实体上。
步骤 105 , 承载实体通知业务实体上述下发用户权限成功, 并且可 以进一步通知到终端设备。
步骤 106, 用户从终端设备通过承载面向承载实体请求业务。
步骤 107至步骤 108, 承载实体根据所保存的用户权限对用户进行 授权判断, 对授权的用户执行相应的请求, 拒绝未授权用户的请求。 图 6所示方式的流程如下:
步骤 201 , 终端设备通过业务控制实体向业务实体请求业务。
步骤 202, 业务实体获得用户的业务权限。
步骤 203 , 业务实体向承载控制实体下发用户的业务权限, 承载控 制实体将用户业务权限发送给数据库。
步骤 204, 数据库保存所下发的用户业务权限。 当然用户的业务权 限也可以静态配置到数据库上。
步骤 205 , 数据库通知业务实体上述下发用户权限成功, 并且可以 进一步通知到终端设备。
步骤 206, 用户从终端设备通过承载面向承载实体请求业务。
步骤 207, 承载实体向承载控制实体发出业务授权请求。
步骤 208, 承载控制实体与数据库进行交互, 获取上述用户业务权 限。
步骤 209, 承载控制实体根据所获取的用户业务权限对用户进行授 权判断, 并将结果即是否允许该用户的频道请求, 通过业务授权应答发 送给承载实体。
步骤 210, 承载实体根据授权结果对授权的用户执行相应的请求, 拒绝未授权用户的请求。
在上述流程中, 还可以有如下变化: 在步骤 207中, 承载实体将来 自用户设备的 IGMP消息转发给承载控制实体; 在后续步骤中, 承载控 制实体进行授权判断, 并通知承载实体是否允许该用户的频道加入请 求。
从图 5和图 6的流程可以看出, 在步骤 106或步骤 206开始, 用户 首先在承载面通过 IGMP消息向 DSLAM或 GGSN等承载面实体请求媒 体流, 如果承载面实体有该用户的权限, 直接进行授权判断, 相当于步 骤 107至步骤 108; 如果没有, 则承载面实体向 SPDF或 PDF等承载控 制实体请求频道授权。
如果承载控制实体保存有用户的频道权限, 则直接进行授权判断, 相当于步骤 208至步骤 211; 如果没有保存, 则承载控制实体向业务层 面发起请求, 请求用户频道权限, 获得后进行频道授权判断。 另外, 承 载面实体还可以通过和业务面的接口, 如多媒体广播组播(MBMS ) 中 的 Gmb接口, 向业务层面发起请求, 请求用户频道权限, 并在获得后 进行频道授权判断。 基于上述方式, 下面分别说明在不同的承载网络环境下, 用户频道 权限判断的具体实施过程。
第一实施例: 在 xDSL网络中, 用户的频道权限信息静态配置或者 动态下发到 DSLAM或 BRAS上; 当 DSLAM或 BRAS收到 IGMP消息 时, 根据上述权限信息进行用户频道请求的授权判断。
图 7为第一实施例的流程示意图。 在图 7中, 所涉及的实体包括: 机顶盒(Set Top Box, STB ), 代理呼叫会话控制功能实体( P-CSCF )、 应用服务器 (AS )、 用户数据服务器功能实体 (User Profile Server Function , UPSF )、 业务策略决策功能实体 ( Service Policy Decision
Function , SPDF )、 接入 -资源和接纳控制功能实体 ( Access-Resource Admission Control Function, A-RACF ) 以及 DSLAM或 BRAS。
参照图 7, 本发明第一实施例的流程如下:
步骤 301 , STB向 AS发送 SIP请求或订阅( SIP Invite或 Subscribe ) 消息, 请求或订阅特定频道。
步骤 302, 如果用户权限信息在 UPSF存储, 则 AS向 UPSF获取用 户订阅的频道权限信息。
步骤 303, AS下发频道权限信息给 P-CSCF。
步骤 304, P-CSCF转发上述消息给 SPDF。
步骤 305至步骤 305,, SPDF根据 STB的 IP地址, 向网络附着子 系统(NASS )获取用户物理位置信息。 NASS返回用户物理位置信息给 SPDF, 如线路标识(LineID )。
需要注意的是, 这里的 NASS为 TISPAN中网络附着系统, 如果在 ITU-T中, 则网络附着系统为网络附着控制功能实体(NACF )。
步骤 306, SPDF根据所获得的物理位置信息,通过 A-RACF下发频 道权限信息给用户所在的 DSLAM或 BRAS。
步骤 307, DSLAM或 BRAS可以进一步以某个关键字为索引, 如 IP地址或者物理位置标识, 保存用户权限信息。
步骤 308, DSLAM或 BRAS还可以进一步通过 P-CSCF向 STB发 送成功进行权限下发的消息。
步骤 309, STB向 DSLAM或 BRAS发送 IGMP加入消息, 请求某 个频道。
步骤 310, DSLAM或 BRAS根据所保存频道权限信息进行授权判 断, 可以通过 LinelD关联, 也可以通过 IP地址关联。
步骤 311 , 如果用户授权通过, 转发用户所请求频道的节目流。 如
果未通过, 则拒绝用户的请求。
在上述流程中, 步骤 304至步骤 305, 也可以为: P-CSCF向 NASS 查询并获得用户的物理位置信息, 然后 P-CSCF将频道权限信息和物理 位置信息转发给 SPDF。
在步骤 307中,承载实体 DSLAM或 BRAS收到下发的用户权限后, 需要以某关键字为索引,保存权限信息,以便收到用户的 IGMP消息后, 在步骤 310中把该 IGMP消息和下发的频道权限进行关联, 找到对应到 该用户的频道权限, 而不是其他用户的频道权限。 所述关键字可以是物 理位置标识, 如 DSLAM的 LinelD, 也可以是用户的 IP地址。 如果只 使用用户的 IP地址, 则可以不执行步骤 305至步骤 305,。 第二实施例: xDSL网络中,频道权限静态配置或者动态下发到 SPDF 或者承载层的某个数据库上。 当 DSLAM或 BRAS收到 IGMP消息时, 向 SPDF或者该承载层的数据库请求验证该用户的频道权限。
第二实施例的流程如图 8所示。 参照图 8, 该流程包括:
步骤 401 , STB向 AS发送 SIP Invite或 Subscribe消息,请求或订阅 特定频道。
步骤 402, 如果用户权限信息在 UPSF存储, 则 AS向 UPSF获取用 户订阅的频道权限信息。
步骤 403, AS下发频道权限信息给 P-CSCF。
步骤 404至步骤 404,, P-CSCF根据 IP地址, 向 NASS获取用户物 理位置信息。 NASS返回用户物理位置信息给 P-CSCF, 如 LinelD标识。
步骤 405 , P-CSCF频道权限信息和物理位置信息转发给 SPDF, SPDF 转发给数据库。
步骤 406, 数据库以某个关键字为索引, 如 IP地址或者物理位置标
识, 保存用户权限信息。
步骤 406,,数据库通过 P-CSCF向 STB发送成功进行权限下发的消 息。
步骤 407 , STB向 DSLAM发送 IGMP加入消息, 请求某个频道。 步骤 408 , DSLAM向 SPDF发出业务授权请求。
步骤 409至步骤 409,, SPDF向数据库请求用户业务权限, 数据库 向 SPDF返回用户业务权限信息。
步骤 410, SPDF根据所返回的用户业务权限信息, 对用户进行权限 判断。
步骤 411 , SPDF将授权结果, 即是否允许该用户的频道请求, 发送 给 DSLAM。
步骤 412, DSLAM根据授权结果进行相应操作, 即: 如果用户授权 通过, 则向 STB转发用户所请求频道的节目流, 否则拒绝未授权用户的 请求。 第三实施例: 在 PCC 架构中, 频道权限静态配置或者动态下发到 SPR上; 当 GGSN收到 IGMP消息时, 向 PCEF请求验证该用户的频道 权限, PCEF从 SPR取得用户的频道权限信息, 进行频道授权判断。 其 中 PCEF也可以为 PDF, 以下描述以 PCEF为例说明。
第三实施例的流程如图 9所示, 参照图 9, 该流程包括:
步骤 501 , 终端设备 ( Terminal ) 向 AS发送 SIP Invite或 Subscribe 消息, 请求或订阅特定频道。
步骤 502, 如果订阅信息在 HSS存储, 则 AS向 HSS获取用户订阅 的频道权限信息。
步骤 503, AS下发频道权限信息给 P-CSCF。
步骤 504, P-CSCF进行业务层标识和承载层标识之间的转换。 所述 业务层标识如 IMPU, 所述 7 载层标识如 IP地址。
步骤 505, P-CSCF经过 PCRF或 PDF,将频道权限信息下发给 SPR, 并且携带承载层标识, 例如 IP地址。
步骤 506, SPR以承载层标识如 IP地址为索引,保存用户权限信息。 步骤 506,, SPR通过 P-CSCF向 Terminal发送成功进行权限下发的 消息。
步骤 507, Terminal向 GGSN发送 IGMP加入消息, 请求某个频道。 步骤 508 , GGSN向 PCRF或 PDF发出业务授权请求, 并携带承载 层标识, 如 IP地址。
步骤 509至步骤 509,, PCRF或 PDF携带^载层标识,向 SPR请求 用户业务权限, SPR向 PCRF或 PDF返回用户业务权限信息。
步骤 510, PCRF或 PDF根据所返回的用户业务权限信息, 对用户 进行权限判断。
步骤 511 , PCRF或 PDF将授权结果, 即是否允许该用户的频道请 求, 发送给 GGSN。
步骤 512, GGSN根据授权结果进行相应操作, 即: 如果用户授权 通过, 则向 Terminal转发用户所请求频道的节目流, 否则拒绝未授权用 户的请求。 第四实施例: 在 PCC 架构中, 频道权限静态配置或者动态下发到 PCEF或 PDF上; 当 GGSN收到 IGMP消息时, 向 PCEF或 PDF请求验 证该用户的频道权限, PCEF或 PDF根据保存的频道权限信息, 进行频 道授权判断。
第四实施例的流程如图 10所示, 参照图 10, 该流程包括:
步骤 601 , Terminal向 AS发送 SIP Invite或 Subscribe消息, 请求或 订阅特定频道。
步骤 602, 如果用户权限信息在 HSS存储, 则 AS向 HSS获取用户 订阅的频道权限信息。
步骤 603, AS下发频道权限信息给 P-CSCF。
步骤 604, P-CSCF进行业务层标识和承载层标识之间的转换。 所述 业务层标识如 IMPU, 所述 7 载层标识如 IP地址。
步骤 605, P-CSCF将频道权限信息下发给 PCRF或 PDF, 并且携带 7 载层标识, 例如 IP地址。
步骤 606, PCRF或 PDF以 载层标识如 IP地址为索引, 保存用户 权限信息。
步骤 606,, PCRF或 PDF通过 P-CSCF向 Terminal发送成功进行 权限下发的消息。
步骤 607, Terminal向 GGSN发送 IGMP加入消息, 请求某个频道。 步骤 608 , GGSN向 PCRF或 PDF发出业务授权请求, 并携带承载 层标识, 如 IP地址。
步骤 609, PCRF或 PDF根据所保存的用户业务权限信息, 对用户 进行权限判断。
步骤 610, PCRF或 PDF将授权结果, 即是否允许该用户的频道请 求, 发送给 GGSN。
步骤 611 , GGSN根据授权结果进行相应操作, 即: 如果用户授权 通过, 则向 Terminal转发用户所请求频道的节目流, 否则拒绝未授权用 户的请求。
需要说明的是, 在上述流程中 PCEF也可以通过在频道请求响应中 携带自己本地生成的本次会话标识给用户, 用户在 IGMP请求中携带该
会话标识, 从而在 GGSN向 PCEF请求授权时, PCEF可以通过会话标 识进行关联。
另夕卜, 在本实施例中, 由于网络中可能有多个 PCEF, PCEF可以通 过在频道请求响应中携带自己的标识, 从而在 GGSN向 PCEF请求授权 时, GGSN可以通过 PCEF的标识把授权请求发送给该 PCEF。 第五实施例: 承载层面不通过 IGMP消息触发业务, 业务层面直接 通过业务信令, 控制承载层实体为用户授权。
第五实施例的流程如图 10所示, 参照图 10, 该流程包括: 步骤 701 , STB向业务实体 AS发送 SIP Invite或 Subscribe消息,请 求或订阅某频道。
步骤 702 , AS从 UPSF获取用户订阅的频道权限信息。
步骤 703 , AS根据所获取的频道权限信息, 对用户进行授权判断, 如果通过, 则在下面流程中通知承载层实体向用户转发用户所请求的媒 体流, 否则, 拒绝该用户的请求。
步骤 704, AS发送消息给 P-CSCF, 该消息用于通知承载实体用户 请求某频道并且授权通过。
步骤 705 , P-CSCF转发上述消息给^载控制实体 SPDF。
步骤 706至步骤 706,, SPDF向 NASS中的 CLF发送消息, 以获取 用户物理位置信息, NASS中的 CLF收到消息后, 向 SPDF返回用户物 理位置信息。
步骤 707, SPDF通知 7 载实体 DSLAM或 BRAS用户请求某频道并 且授权通过, 通知消息中还携带有用户物理位置信息。
步骤 708, DSLAM或 BRAS可以保存用户权限信息, 也可以不保 存。
步骤 709, DSLAM或 BRAS通过 P-CSCF向 STB发送用户授权成 功响应消息, 也可以不发送该消息。
步骤 710, 因为用户授权通过, 所以 DSLAM或 BRAS向 STB转发 用户所请求频道的节目流。
上述所有实施例中, 以用户的频道权限信息的存储在 HSS或 UPSF 户的权限信息还可能有其他的存储方式, 如存储在业务实体 AS上, 此 时 AS本地获取权限信息即可; 或者存储在一个独立的数据库上, 此时 AS从该数据库获取权限信息。
如图 12所示的是本发明实施例中授权实体的结构示意图,该授权实 体为进行网络直播电视业务频道授权的装置。
参照图 12, 授权实体至少包括接收单元和授权判断单元。 其中, 接 收单元接收终端设备对网络直播电视业务的频道请求, 并将频道请求发 送给授权判断单元, 而授权判断单元则根据用户权限信息对所述频道请 求进行授权判断。
如果授权实体不是承载实体, 而是业务层实体或承载控制实体时, 该授权实体进一步包括发送单元, 该发送单元在授权判断单元的结果是 授权通过的情况下, 通知承载实体执行所述频道请求。
如果授权实体是承载实体, 则不需要上述发送单元, 而是进一步包 括业务执行单元, 该业务执行单元在图中并未画出。 业务执行单元用于 在授权判断单元的结果是授权通过的情况下执行所述频道请求。
如图 12 所示, 该授权实体还可以进一步包括用户权限信息获取单 元, 用于从外界获取所述用户权限信息, 并提供给授权判断单元。
在授权实体为不同网络实体的时候, 所述用户权限信息获取单元进 行不同的具体操作。 例如, 在授权实体为业务层实体的情况下, 用户权
限信息获取单元用于从 HSS或 UPSF获取所述用户权限信息;在授权实 体为承载控制实体的情况下, 用户权限信息获取单元用于向业务层或数 据库请求获取所述用户权限信息; 在授权实体为承载实体的情况下, 用 户权限信息获取单元用于通过承载控制实体向业务层或数据库请求获 取所述用户权限信息, 还可以直接向业务层请求获取所述用户权限信 息。
另夕卜,如图 12所示,该授权实体还可以进一步包括用户权限信息存 储单元, 该用户权限信息存储单元用于保存所述用户权限信息, 并提供 给授权判断单元。
以上所述仅为本发明的较佳实施例而已, 并不用以限制本发明, 凡 在本发明的精神和原则之内, 所作的任何修改、 等同替换、 改进等, 均 应包含在本发明的保护范围之内。
Claims
1、 一种进行网络直播电视业务频道授权的方法, 其特征在于, 该方 法包括:
授权实体在业务实体接收到终端设备对网络直播电视业务的频道请 求之后, 根据用户权限信息对所述频道请求进行授权判断;
授权实体在授权通过的情况下, 使承载实体执行终端设备的频道请 求。
2、 根据权利要求 1所述的方法, 其特征在于, 该方法进一步包括: 在授权没有通过的情况下, 拒绝终端设备的频道请求。
3、根据权利要求 1所述的方法, 其特征在于, 所述授权实体为业务 层实体或承载层实体;
在授权实体进行授权判断之前进一步包括在授权实体上配置所述用 户权限信息的步骤。
4、根据权利要求 1所述的方法, 其特征在于, 所述授权实体为承载 层实体;
在授权实体进行授权判断之前进一步包括: 在数据库上配置所述用 户权限信息; 承载层实体从数据库获取所述用户权限信息。
5、根据权利要求 4所述的方法, 其特征在于, 所述承载层实体为承 载实体, 所述承载层实体从数据库获取所述用户权限信息的步骤包括: 承载实体向承载控制实体发出授权请求, 承载控制实体从数据库获取用 户权限信息并发送给承载实体。
6、根据权利要求 4所述的方法, 其特征在于, 所述承载层实体为承 载控制实体。
7、根据权利要求 1所述的方法, 其特征在于, 所述授权实体为承载
层实体;
在接收终端设备对网络直播电视业务的频道请求之前进一步包括: 业务实体接收终端设备发起的用以请求或订阅网络直播电视业务的请 求或订阅消息, 从归属用户服务器 HSS 或用户数据服务器功能实体
UPSF、业务实体自身或者存储有用户权限信息的数据库获取用户权限信 息, 并下发给^载层实体。
8、根据权利要求 7所述的方法, 其特征在于, 所述承载层实体为承 载实体。
9、根据权利要求 1所述的方法, 其特征在于, 所述授权实体为承载 实体;
在接收终端设备对网络直播电视业务的频道请求之前进一步包括: 业务实体接收终端设备发起的用以请求或订阅网络直播电视业务的频 道的请求或订阅消息, 从 HSS、 UPSF、 业务实体自身或者存储有用户 权限信息的数据库获取用户权限信息, 并下发给承载控制实体, 承载控 制实体将所述用户权限信息保存到数据库;
在授权实体进行授权判断之前进一步包括: 承载实体向承载控制实 体发出授权请求, 承载控制实体从数据库获取用户权限信息, 并发送给 承载实体。
10、 根据权利要求 7所述的方法, 其特征在于, 所述承载层实体为 承载控制实体。
11、根据权利要求 10所述的方法, 其特征在于, 在授权实体进行授 权判断之前进一步包括: 承载控制实体将所述用户权限信息保存到数据 库; 承载控制实体从数据库获取所述用户权限信息。
12、 根据权利要求 1所述的方法, 其特征在于, 所述授权实体为承 载实体;
在接收终端设备对网络直播电视业务的频道请求之前进一步包括: 业务实体接收终端设备发起的用以请求或订阅网络直播电视业务的请 求或订阅消息, 从 HSS、 UPSF、 业务实体自身或者存储有用户权限信 息的数据库获取用户权限信息, 并下发给承载控制实体;
在授权实体进行授权判断之前进一步包括: 承载实体向承载控制实 体发出授权请求, 承载控制实体将所述用户权限信息发送给承载实体。
13、 根据权利要求 7所述的方法, 其特征在于, 在接收终端设备对 网络直播电视业务的频道请求之前进一步包括: 承载层实体将本次会话 标识或该承载层实体的标识发送给终端设备;
终端设备发起请求时进一步携带所述本次会话标识或所述承载层实 体的标识。
14、 根据权利要求 7所述的方法, 其特征在于, 承载层实体所保存 的用户权限信息以业务层标识或承载层标识为索引;
在以承载层标识为索引时, 该方法进一步包括: 在用户权限信息下 发过程中, 由业务控制实体或承载控制实体进行业务层标识到承载层标 识的转换。
15、 根据权利要求 9所述的方法, 其特征在于, 数据库所保存的用 户权限信息以业务层标识或承载层标识为索引;
在以承载层标识为索引时, 该方法进一步包括: 在用户权限信息下 发过程中, 由业务控制实体或承载控制实体进行业务层标识到承载层标 识的转换。
16、 根据权利要求 14或 15所述的方法, 其特征在于,
所述业务层标识为公有用户标识 IMPU; 或者,
所述承载层标识为终端设备的 IP地址或者终端物理位置标识; 或 者,
所述物理位置标识在数字用户环路接入复用器 DSLAM中为线路标 识 LinelDo
17、 根据权利要求 1所述的方法, 其特征在于, 所述授权实体为承 载控制实体;
在授权实体进行授权判断之前进一步包括: 承载控制实体通过承载 控制实体、 业务控制实体向业务实体请求用户权限信息, 业务实体从 HSS、 UPSF、 业务实体自身或者存储有用户权限信息的数据库获取用户 权限信息, 并通过业务控制实体、 承载控制实体下发给承载实体。
18、 根据权利要求 1所述的方法, 其特征在于, 所述授权实体为承 载实体;
在授权实体进行授权判断之前进一步包括: 承载实体通过业务控制 实体向业务实体请求用户权限信息, 业务实体从 HSS、 UPSF、 业务实 体自身或者存储有用户权限信息的数据库获取用户权限信息, 并通过业 务控制实体下发给承载实体。
19、根据权利要求 18所述的方法, 其特征在于, 在多媒体广播组播 MBMS系统中, 承载实体通过 Gmb接口与业务控制实体通信。
20、 根据权利要求 1所述的方法, 其特征在于, 所述授权实体为承 载控制实体;
在授权实体进行授权判断之前进一步包括: 承载控制实体通过业务 控制实体向业务实体请求用户权限信息, 业务实体从 HSS、 UPSF、 业 务实体自身或者存储有用户权限信息的数据库获取用户权限信息, 并通 过业务控制实体下发给承载控制实体。
21、 根据权利要求 1所述的方法, 其特征在于, 所述授权实体为业 务层实体;
授权实体进行授权判断并在授权通过的情况下由承载层实体执行频
道请求的步骤包括: 业务层实体从 HSS、 UPSF、 业务实体自身或者存 储有用户权限信息的数据库获取用户权限信息, 根据所述用户权限信息 对频道请求进行授权, 并在授权通过的情况下, 将用户的频道请求以及 授权通过信息通知给承载实体; 承载实体执行所述频道请求。
22、根据权利要求 21所述的方法, 其特征在于, 所述业务层实体为 业务实体。
23、根据权利要求 21所述的方法, 其特征在于, 在通知用户的频道 请求以及授权通过信息的过程中, 由业务控制实体或承载控制实体从网 络附着系统获取所述承载层标识并通知给承载实体;
所述的网络附着系统在 TISPAN 中为网络附着子系统 NASS , 在 ITU-T中为网络附着控制功能实体 NACF。
24、 根据权利要求 14、 15或 23所述的方法, 其特征在于, 所述业 务控制实体在 IP 多媒体子系统 IMS 中为代理呼叫会话控制功能实体 P-CSCF; 或者,
所述承载控制实体为业务策略决策功能实体 SPDF 、或者接入 -资源 和接纳控制功能实体 A-RACF、 或者策略决策功能实体 PDF、 或者策略 和计费规则功能实体 PCEF。
25、根据权利要求 1所述的方法, 其特征在于, 该方法进一步包括: 授权实体通知终端设备下发用户权限信息成功。
26、根据权利要求 1所述的方法, 其特征在于, 该方法进一步包括: 授权实体收到用户权限信息后, 保存所述用户权限信息。
27、 根据权利要求 1所述的方法, 其特征在于, 所述频道请求为: 请求频道的节目流、 离开频道、 加入频道或频道切换。
28、根据权利要求 27所述的方法, 其特征在于, 所述频道请求采用 因特网组管理协议 IGMP或组播侦听者发现协议 MLD。
29、 一种进行网络直播电视业务频道授权的系统, 其特征在于, 该 系统包括:
授权实体, 用于根据用户权限信息, 对终端设备的频道请求进行授 权判断;
承载实体, 用于在授权通过的情况下, 执行终端设备的频道请求。
30、根据权利要求 29所述的系统, 其特征在于, 所述授权实体进一 步包括用于在授权没有通过的情况下拒绝终端设备的频道请求的单元。
31、根据权利要求 29所述的系统, 其特征在于, 所述授权实体为承 载层实体;
该系统进一步包括: 保存用户权限信息的 HSS或 UPSF、 以及用于 从所述 HSS或 UPSF获取用户权限信息并下发给承载层实体的业务实 体; 或者, 保存有用户权限信息、 并且从自身获取用户权限信息并下发 给承载层实体的业务实体; 或者, 存储有用户权限信息的数据库、 以及 用于从所述存储有用户权限信息的数据库获取用户权限信息并下发给 承载层实体的业务实体。
32、根据权利要求 31所述的系统, 其特征在于, 所述承载层实体为 承载实体。
33、 根据权利要求 32所述的系统, 其特征在于, 所述承载实体为: 数字用户环路接入复用器 DSLAM、 宽带远程接入服务器 BRAS、 通用 分组无线服务网关支撑节点 GGSN、 广播多播业务 BCMCS 支撑节点 BSN或者 IP封装实体 IPE。
34、根据权利要求 31所述的系统, 其特征在于, 所述承载层实体为 承载控制实体。
35、 根据权利要求 32或 34所述的系统, 其特征在于, 该系统进一 步包括与承载控制实体相连接的数据库, 用于保存所下发的用户权限信
息。
36、根据权利要求 35所述的系统,其特征在于,所述数据库为 NASS 中的 CLF或 PDBF; 或者为 RACF中的 SPDF或 A-RACF; 或者为 PCC 中的 SPR; 或者为与承载控制实体相连的独立的数据库。
37、根据权利要求 34所述的系统, 其特征在于, 所述承载控制实体 为: 在 TISPAN中为 SPDF、 在 3GPP中为策略决策功能实体 PDF或者 在 PCC系统中为 PCEF。
38、根据权利要求 31所述的系统, 其特征在于, 该系统进一步包括 业务控制实体或承载控制实体, 用于在用户权限信息的下发过程中进行 业务层标识和承载层标识的转换。
39、根据权利要求 38所述的系统, 其特征在于, 所述业务控制实体 为在 IMS系统中为 P-CSCF; 或者, 所述^载控制实体为在 TISPAN中 为 SPDF或 A-RACF, 在 3GPP中为 PDF, 在 PCC系统中为 PCEF。
40、根据权利要求 29所述的系统, 其特征在于, 所述授权实体为业 务层实体, 所述业务层实体根据配置的或从 HSS、 UPSF、 业务实体自 身或者存储有用户权限信息的数据库获取的用户权限信息, 对频道请求 进行授权, 并在授权通过的情况下, 将用户的频道请求以及授权通过信 息通知给承载层实体。
41、 一种进行网络直播电视业务频道授权的装置, 其特征在于, 该 装置包括:
接收单元, 用于接收终端设备对网络直播电视业务的频道请求, 并 转发给授权判断单元;
授权判断单元, 用于根据用户权限信息对所述频道请求进行授权判 断。
42、根据权利要求 41所述的装置, 其特征在于, 该装置为业务层实
体;
所述业务层实体进一步包括发送单元和用户权限信息获取单元中的 至少一个, 其中:
发送单元用于在授权判断单元的结果是授权通过的情况下, 通知承 载实体执行所述频道请求;
用户权限信息获取单元用于从 HSS、 UPSF、业务实体或者存储有用 户权限信息的数据库获取所述用户权限信息。
43、根据权利要求 41所述的装置, 其特征在于, 该装置为承载控制 实体;
所述承载控制实体进一步包括发送单元和用户权限信息获取单元中 的至少一个, 其中:
发送单元用于在授权判断单元的结果是授权通过的情况下, 通知承 载实体执行所述频道请求;
用户权限信息获取单元用于向业务层或数据库请求获取所述用户权 限信息。
44、根据权利要求 41所述的装置,其特征在于,该装置为承载实体; 所述承载实体进一步包括业务执行单元和用户权限信息获取单元中 的至少一个, 其中:
业务执行单元用于在授权判断单元的结果是授权通过的情况下, 执 行所述频道请求;
用户权限信息获取单元用于向承载控制实体、 业务层或数据库请求 获取所述用户权限信息。
45、根据权利要求 41 ~ 44中任意一项所述的装置, 其特征在于, 该 装置进一步包括:
用户权限信息存储单元, 用于保存所述用户权限信息, 并提供给授
权判断单元。
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP07816971A EP2071839A4 (en) | 2006-09-25 | 2007-09-25 | METHOD, SYSTEM AND DEVICE FOR CHANNEL AUTHORIZATION OF LIVE TV EMISSIONS BY NETWORK |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN2006101394773A CN101155293B (zh) | 2006-09-25 | 2006-09-25 | 一种进行网络直播电视业务频道授权的方法、系统及装置 |
CN200610139477.3 | 2006-09-25 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2008037220A1 true WO2008037220A1 (fr) | 2008-04-03 |
Family
ID=39229755
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2007/070780 WO2008037220A1 (fr) | 2006-09-25 | 2007-09-25 | Procédé, système et dispositif pour autoriser une émission de télévision en direct sur un canal par un réseau |
Country Status (3)
Country | Link |
---|---|
EP (1) | EP2071839A4 (zh) |
CN (1) | CN101155293B (zh) |
WO (1) | WO2008037220A1 (zh) |
Families Citing this family (16)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101729176B (zh) * | 2008-10-22 | 2012-10-03 | 华为技术有限公司 | 直播业务中同步鉴权信息的方法、系统和装置 |
CN101552903B (zh) * | 2009-05-04 | 2011-10-26 | 中兴通讯股份有限公司 | 一种电视节目分发方法及系统 |
CN101938628B (zh) * | 2009-06-29 | 2014-07-02 | 传线网络科技(上海)有限公司 | 互联网直播信号动态切换方法 |
CN101997697B (zh) * | 2009-08-12 | 2012-06-20 | 华为终端有限公司 | 一种i1接口的业务控制方法和装置 |
US8621099B2 (en) | 2009-09-21 | 2013-12-31 | Sling Media, Inc. | Systems and methods for formatting media content for distribution |
US9015225B2 (en) | 2009-11-16 | 2015-04-21 | Echostar Technologies L.L.C. | Systems and methods for delivering messages over a network |
CN102088634A (zh) * | 2009-12-07 | 2011-06-08 | 华为技术有限公司 | 网络电视系统业务权限的控制方法、装置及系统 |
US9178923B2 (en) | 2009-12-23 | 2015-11-03 | Echostar Technologies L.L.C. | Systems and methods for remotely controlling a media server via a network |
US9275054B2 (en) | 2009-12-28 | 2016-03-01 | Sling Media, Inc. | Systems and methods for searching media content |
DE102010007718B4 (de) * | 2010-02-10 | 2011-10-27 | Teveo Interactive Gmbh | Verfahren und Vorrichtung zur Authentifizierung von Benutzern eines Hybridendgerätes |
US9113185B2 (en) | 2010-06-23 | 2015-08-18 | Sling Media Inc. | Systems and methods for authorizing access to network services using information obtained from subscriber equipment |
US20140137223A1 (en) * | 2011-06-16 | 2014-05-15 | Teveo Interactive Gmbh | Method and apparatus for authenticating users of a hybrid terminal |
CN102387419B (zh) * | 2011-11-04 | 2014-04-30 | 深圳市网合科技股份有限公司 | 网络电视接收机及其防止文件非法传播的方法 |
CN102821304B (zh) * | 2012-04-17 | 2015-07-01 | 国家广播电影电视总局广播科学研究院 | 数字电视系统的数据推送方法、设备和数字电视系统 |
CN103974092B (zh) * | 2013-01-31 | 2018-05-15 | 中兴通讯股份有限公司 | 一种基于网络电视实现网络广播的方法、装置及网络电视 |
CN105450506B (zh) * | 2015-11-27 | 2018-11-06 | 广州华多网络科技有限公司 | 一种实时信息交互方法、装置及系统 |
Citations (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20010050979A1 (en) * | 1997-01-17 | 2001-12-13 | Hrastar Scott E. | Two-tiered authorization and authentication for a cable data delivery system |
JP2004048557A (ja) * | 2002-07-15 | 2004-02-12 | Nippon Telegraph & Telephone East Corp | コンテンツ配信装置、コンテンツ配信方法、コンテンツ配信プログラムおよび記録媒体 |
US20040039906A1 (en) * | 2002-06-07 | 2004-02-26 | Makoto Oka | Access authorization management system, relay server, access authorization management method, and computer program |
US20040163113A1 (en) * | 2002-11-26 | 2004-08-19 | Kianoush Namvar | Interactive media transmission method and system for direct purchase of goods and services over a TV-broadcast network |
US20050081249A1 (en) * | 2001-12-27 | 2005-04-14 | Soederqvist Erik Richard | Method for connecting a plurality of computer terminals to a broadband cable |
CN1633173A (zh) * | 2003-12-24 | 2005-06-29 | 华为技术有限公司 | 获知用户上线/下线/在线信息的方法和系统 |
CN1633169A (zh) * | 2003-12-24 | 2005-06-29 | 华为技术有限公司 | 数字电视网络中上线用户鉴权方法 |
CN1633170A (zh) * | 2003-12-24 | 2005-06-29 | 华为技术有限公司 | 数字电视网络中在线用户鉴权方法 |
JP2005333402A (ja) * | 2004-05-19 | 2005-12-02 | Dowango:Kk | 情報提供システム、情報提供方法および情報提供プログラム |
Family Cites Families (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1558676A (zh) * | 2004-01-19 | 2004-12-29 | 大唐电信科技股份有限公司光通信分公 | 多媒体信息点播系统及点播方法 |
CN1297124C (zh) * | 2004-09-30 | 2007-01-24 | 华为技术有限公司 | Ip多媒体子系统中利用电路交换承载业务的系统及方法 |
-
2006
- 2006-09-25 CN CN2006101394773A patent/CN101155293B/zh not_active Expired - Fee Related
-
2007
- 2007-09-25 WO PCT/CN2007/070780 patent/WO2008037220A1/zh active Application Filing
- 2007-09-25 EP EP07816971A patent/EP2071839A4/en not_active Ceased
Patent Citations (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20010050979A1 (en) * | 1997-01-17 | 2001-12-13 | Hrastar Scott E. | Two-tiered authorization and authentication for a cable data delivery system |
US20050081249A1 (en) * | 2001-12-27 | 2005-04-14 | Soederqvist Erik Richard | Method for connecting a plurality of computer terminals to a broadband cable |
US20040039906A1 (en) * | 2002-06-07 | 2004-02-26 | Makoto Oka | Access authorization management system, relay server, access authorization management method, and computer program |
JP2004048557A (ja) * | 2002-07-15 | 2004-02-12 | Nippon Telegraph & Telephone East Corp | コンテンツ配信装置、コンテンツ配信方法、コンテンツ配信プログラムおよび記録媒体 |
US20040163113A1 (en) * | 2002-11-26 | 2004-08-19 | Kianoush Namvar | Interactive media transmission method and system for direct purchase of goods and services over a TV-broadcast network |
CN1633173A (zh) * | 2003-12-24 | 2005-06-29 | 华为技术有限公司 | 获知用户上线/下线/在线信息的方法和系统 |
CN1633169A (zh) * | 2003-12-24 | 2005-06-29 | 华为技术有限公司 | 数字电视网络中上线用户鉴权方法 |
CN1633170A (zh) * | 2003-12-24 | 2005-06-29 | 华为技术有限公司 | 数字电视网络中在线用户鉴权方法 |
JP2005333402A (ja) * | 2004-05-19 | 2005-12-02 | Dowango:Kk | 情報提供システム、情報提供方法および情報提供プログラム |
Also Published As
Publication number | Publication date |
---|---|
CN101155293A (zh) | 2008-04-02 |
EP2071839A4 (en) | 2010-08-25 |
EP2071839A1 (en) | 2009-06-17 |
CN101155293B (zh) | 2011-11-30 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2008037220A1 (fr) | Procédé, système et dispositif pour autoriser une émission de télévision en direct sur un canal par un réseau | |
US8077717B2 (en) | Method and system for providing multicast services | |
WO2008025211A1 (fr) | Système de réseau de communication, procédé assurant une fonction de prestation de services, et dispositif de prestation de services | |
WO2020255033A1 (en) | Method and apparatus for adding notifications related with user equipment multicast group and leave | |
WO2008049314A1 (fr) | Procédé et système pour implémenter un service de multidiffusion ou un service de diffusion générale sur la base d'un réseau de nouvelle génération | |
EP1976186B1 (en) | A method for realizing the legal listening in the next generation network and a system thereof | |
WO2009010008A1 (fr) | Procédé, système et dispositif de réseau de gestion des ressources | |
WO2009024092A1 (fr) | Procédé et système permettant la commande d'autorisation de ressource de service | |
WO2009049505A1 (fr) | Procédé et système de vidéo-conférence, serveur d'application et serveur de ressources multimédia | |
EP2109275A1 (en) | Method and device of controlling the number of sessions of user | |
WO2007143926A1 (fr) | Système et procédé de chargement de réseau ims | |
WO2009146593A1 (zh) | 一种资源接纳控制方法及系统 | |
CN101155046B (zh) | 实现组播控制的网络控制系统和方法 | |
WO2008046336A1 (fr) | Système et procédé permettant un contrôle d'accès réparti dans un service multidiffusion | |
CN101489266A (zh) | 一种基于签约数据的ims用户级控制方法及系统 | |
WO2008089702A1 (fr) | Système et procédé de mise en oeuvre de service multimédia en flux, et entité de fonction de commande de ce service | |
CN101360222B (zh) | 一种基于下一代网络的iptv节目产生方法及系统 | |
CN102377577B (zh) | 实现视频监控中音频广播的方法及系统 | |
WO2007082435A1 (fr) | Système, procédé et équipement réseau d'écoute légale dans un réseau de nouvelle génération | |
WO2007056925A1 (fr) | Procede et materiel de controle de session dans un reseau ims | |
WO2007012279A1 (fr) | Procédé d’association de facturation et système de service d’application | |
WO2008098504A1 (fr) | Procédé et système pour fournir un service multidiffusion et dispositif pour fournir un paramètre de service multidiffusion | |
WO2009006816A1 (fr) | Procédé, dispositif et système de contrôle de politique pour une application | |
CN101588277B (zh) | 基于ims的iptv系统的互连装置及其启动、点播和直播方法 | |
WO2009100625A1 (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: 07816971 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2007816971 Country of ref document: EP |
|
NENP | Non-entry into the national phase |
Ref country code: DE |