CN1642264A - General user management system for digital television set and interface communication method of authorization management system - Google Patents
General user management system for digital television set and interface communication method of authorization management system Download PDFInfo
- Publication number
- CN1642264A CN1642264A CN 200410000619 CN200410000619A CN1642264A CN 1642264 A CN1642264 A CN 1642264A CN 200410000619 CN200410000619 CN 200410000619 CN 200410000619 A CN200410000619 A CN 200410000619A CN 1642264 A CN1642264 A CN 1642264A
- Authority
- CN
- China
- Prior art keywords
- management system
- request
- sms
- thread
- data
- 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.)
- Granted
Links
Images
Landscapes
- Computer And Data Communications (AREA)
Abstract
The invention is a method for universal digital TV subscriber management system (SMS) with SAS interface, including arranging SMS secret key set, network protocol, port and SMS indication symbol; arranging counter and making the SMS establish database read thread, data transmission request thread, data response request thread and response data analyzing and database write thread; judging if the SMS sends a request to the SAS: if yes, the SMS database read thread is started up and reading the data to be requested from the SMS database and putting the read request information in an request intelligent array to wait for sending; according to the request form of the SMS, the sending thread of the SMS detects the sent network protocol data packet and sends request data in exact form to the SAS, after the SAS processes the data, the receiving thread of the SMS receives the response data: if the data form is exact, send them into a response intelligent array to wait for data analysis; the response analyzing thread of the SMS analyzes the response data: if they are legal data, transmit the exact processed result back to the database.
Description
Technical field
The invention belongs to the digital television techniques field, particularly a kind of universal digital TV Subscriber Management System (SMS) and authentication management system (SAS) method for interface communication, this interface can with a plurality of Subscriber Management Systems (SMS) database communication, also can and a plurality of user authorization management systems (SAS) between carry out network communication.
Background technology
At digital television broadcasting condition receiving system (CA, Condition Access) in, SAS Subscriber Authorization System (SAS, Subscriber Authorization System) Entitlement Management Message (EMM) is to come from Subscriber Management System (SMS essentially, Subscriber Management System) business operation such as user order a certain service product, order cancellation and transmission decoded data generator (DDG, Decode Data Generator) request that produced such as message, so need between Subscriber Management System and SAS Subscriber Authorization System, set up the SMS-SAS interface, Subscriber Management System can send the authorization requests that business operation produced to SAS Subscriber Authorization System by interface, and SAS Subscriber Authorization System also returns to Subscriber Management System by interface with result after the authorization requests of Subscriber Management System is handled.
In the prior art, the SAS system of difference CA product vendor all has towards SMS communication interface separately, owing to there is not unified standard, the standard of the SMS-SAS interface of each manufacturer has nothing in common with each other, make that the adaptability of SAS system is not high, cause a kind of SAS system can only use fixing a kind of SMS system situation.On the one hand, because the national conditions difference, external CA supplier's SMS system can't use at home at all, need seek domestic SMS system and support its SAS system.On the other hand, for the manufacturer of exploitation SMS system, in order to support different SAS systems, need carry out undying secondary development at the SMS-SAS interface specification that different SAS supplier provides, not only waste time and energy, also make a mistake easily, cause unnecessary loss.
Common SMS-SAS interface all be make executable program and and SMS be installed together, because the SMS-SAS interface specification of each CA manufacturer definition is different, if SMS will with a plurality of CA communications simultaneously, then a plurality of SMS-SAS interfaces to be installed simultaneously, occupying system resources is bigger, communication efficiency is lower, and is difficult to carry out effective telecommunication, does not also just reach the purpose of the control of SMS remote authorization, management.
Summary of the invention
For overcoming the deficiencies in the prior art, the object of the present invention is to provide a kind of universal digital TV Subscriber Management System and authentication management system method for interface communication.
For finishing the foregoing invention purpose, universal digital TV Subscriber Management System of the present invention and authentication management system method for interface communication, described Digital Television comprises a cover front end user management subsystem, two cover different condition receiving front-end subsystems, Subscriber Management System and authentication management system interface module access client and long-range issue Subscriber Management System and authentication management system interface component services device, this method may further comprise the steps:
A., key set, procotol, the port of authentication management system, the indications of Subscriber Management System are set;
B., counter is set, and creates database read line taking journey, request msg transmission thread, request response data receiving thread, analyze response data write-back storehouse thread at Subscriber Management System;
C. judge whether Subscriber Management System sends request to authentication management system, if, then Subscriber Management System reading database thread starts and read the data that need request from the Subscriber Management System database, and it is medium to be sent that the solicited message of reading is put into the intelligent array of request;
D. Subscriber Management System sends thread according to the Internet protocol data bag that Subscriber Management System request format detection sends, and the request msg of correct format is sent to authentication management system;
E. after authentication management system was handled data, the Subscriber Management System receiving thread received processing to response data, if formatted data is correct, sent into and responded the medium pending data analysis of intelligent array;
F. Subscriber Management System analysis response process thread carries out analyzing and processing to response data, if legal data return correct result to database.
Procotol among the described step a adopts transmission Control Network agreement, uses port to be 4000-6999.
Request msg among the described step b sends the request msg employing Internet protocol packet format that thread sends, packet header length is 17, the indications, request indications and the request type sign indicating number that comprise Subscriber Management System, authentication management system also adopts the Internet protocol packet format, it is 12 that packet header adds inclusion length, comprises indications, request indications and the authentication management system respond style sign indicating number of Subscriber Management System.
Request among the described step b comprises the connection test request, increases authorization requests, cancels authorization requests, covers original authorization requests, sends message request, sends mail requests, password reset request, except that connecting test request, the form of all requests comprises packet header and inclusion, inclusion comprises smart card quantity, smart card number list field, and the inclusion that increases authorization requests, cancellation authorization requests, the original authorization requests of covering also comprises product indicia symbol list field.
In the described increase authorization requests field, ' 00 ' expression is to all smart card mandates, and ' 01 ' is the single deck tape-recorder mandate, ' 02 '-' 50 ' expression batch authorization.
In the described cancellation authorization requests, the product mandate of ' 01 ' expression cancellation one sheet smart card, the product mandate of a collection of smart card of ' 02 '-' 50 ' expression cancellation.
In the original authorization requests of described covering, original mandate that ' 01 ' expression covers a sheet smart card, original mandate that ' 02 '-' 50 ' expression covers a collection of smart card.
Intelligent array among the described step b is equivalent to the shared region between process, is used for each thread is connected, and intelligent array can dynamically increase.
Request among the described step c-e sends, responds to receive and adopt cycle wheel to seek mode, asks and respond thread obstruction for some time, blocks and is finished by timer and synchronous event.
Three kinds of timer, regular check network timers are checked in the free interval timer of described timer, connection, the time interval, control of controlling accessing database respectively regularly sends to the user authorization management system and checks and whether connect effectively the faulty operation that when avoiding network to connect having interrupted program still sends the request accessing database, or with time interval timer whether be used the regular check network normal, the assurance program is normally moved.
Described synchronous event comprises transmission incident, reception incident, analysis incident, driving data storehouse incident, sends event-driven and sends thread, receives the event-driven receiving thread, analyzes event-driven and analyzes thread, driving data storehouse event-driven reading database thread.
The key set of authentication management system, procotol, port, Subscriber Management System indications among described step a, the b, counter, adopt the global unique identification device to be provided with or establishment with database read line taking journey, request msg transmission thread, request response data receiving thread, analysis response data write-back storehouse thread, generate dynamic link library file afterwards, and by registration table distribution protocol information.
The present invention has tangible advantage and beneficial effect is: 1, relatively independent.Use the general SMS-SAS interface specification can be so that the exploitation of Subscriber Management System (SMS) and SAS Subscriber Authorization System (SAS) can disperse, independently carry out.The SMS system only need send mandate, message request and reception return information to the SMS-SAS interface according to set standard, the SAS system only needs to receive mandate, message request according to standard from the SMS-SAS interface, returns the processing procedure that result can be finished mandate, message etc. to the SMS-SAS interface again after disposing.In addition, relatively independent relation between SMS system and the SAS system, can guarantee the opening of SMS system and SAS system, promptly a kind of Subscriber Management System (SMS) can be supported Any user authoring system (SAS), and a kind of SAS Subscriber Authorization System (SAS) can be selected the SMS system of any appropriate.So not only can standard SMS system and the development process of SAS system, and make operator have very loose range of choice.2, safety.The application of mutual independent structures of SMS and SAS and assembly makes the request of SMS promptly can also can improve the popularity that Subscriber Management System distributes from wide area network (WAN) from Local Area Network.In addition, the SMS-SAS interface is kept apart SMS and SAS, both can verify by interface requests such as mandate, message, but also can fire compartment wall be installed on the computer that the SMS-SAS interface is installed requests such as mandate, message are filtered, preventing malice is attacked, the fail safe that has improved the CA system.3, authorize fast.When SMS carries out batch user's Authorized operation, when for example giving the mandate of a certain or multinomial service product to all users under a certain collective, general method of operation is that the SMS system retrieves all intelligent card datas under this collective of ownership from self database, sends identical authorization requests at every card one by one to the SMS-SAS interface then.But because the restriction of network and hardware must have certain time interval could guarantee the integrality and the standardization of transmission data between the continuous authorization requests, so both increased the load of network, also reduced the speed of batch authorization.If in standard, adopt reasonably definition, in an authorization requests, just can comprise the authorization message of a plurality of smart cards so, can improve the speed of Authorized operation greatly.4, communication efficiency height.Only need re-register, issue new SMS-SAS interface module when running into the SMS-SAS interface upgrade, visit new interface module and get final product, need not revise code, improve the development efficiency of Subscriber Management System software.Interface module is irrelevant with development language, is based on binary code, so to the developer more selection has been arranged, its occupying system resources is few, can be connected by a plurality of SMS simultaneously to use, and link speed is fast, has improved communication efficiency.
Description of drawings
Fig. 1 is the main flow chart of communication of the present invention;
Fig. 2 is the comparison diagram before and after the SMS-SAS interface moduleization;
Fig. 3 is the network communication schematic diagram between SMS and the SAS.
Embodiment
The present invention is further described in more detail below in conjunction with accompanying drawing.
Consult shown in Fig. 1 main flow chart of the present invention, the key set (keyset) of SAS at first is set, the indications (id) of procotol (ip), port, SMS, then, when reading the SMS database, to timer be set according to the ID of the IP of key set, SAS, port, SMS, create four threads and SAS and connect, carry out the analyzing and processing of request of data, response.These four threads are: the SMS database reads processing threads, request msg sends to SAS processing threads, request response data reception processing threads, analyzes response data write-back SMS database thread.
The present invention proposes a kind of universal digital TV Subscriber Management System and authentication management system method for interface communication, realize Componentized SMS-SAS communication interface according to the general-purpose interface standard, described Digital Television comprises a cover front end user management subsystem, two cover different conditions are accepted sub-front end system, SMS-SAS interface module access client and long-range issue SMS-SAS interface component services device.
The definition of general SMS-SAS interface communication standard comprises following contents:
1, procotol: Subscriber Management System (SMS) adopts ICP/IP protocol and SMS-SAS interface to communicate, and the end employing Transmission Control Protocol towards the SMS system uses port 4000-6999, and IP bag content is used ASCII character, and the data type code description sees Table 1.
2, SMS request IP packet format and SAS response IP packet format
Table 1 data type code description
| Code | Data type | Explanation | Example |
| D | Decimal (decimal number) | A decimal number, each comprises one from ' 0 '-' 9 ' ASCII character.The definition in one of IP packet format ' field length ' of concrete length, a field value figure place left side inadequately mends 0. | 4 D value ' 0014 ' → represent decimal system numerical value 14 |
| A | Ascii string | An ascii string, the definition in one of IP packet format ' field length ' of concrete length | 3 A value ' DVB ' → represent ascii string DVB |
SMS request IP packet format sees Table 2, and in any request command, the length in packet header is always 17.
Table 2 SMS request IP packet format
| Component part | Field name | Data type | Field length | Explanation |
| Packet header | Inclusion length | ????D | ????4 | The length of inclusion part does not comprise packet header in the IP bag |
| SMS?ID | ????D | ????5 | The SMS numbering | |
| SMS asks ID | ????D | ????5 | SMS asks numbering | |
| The request type sign indicating number | ????A | ????2 | Represent different authorization requests by this field | |
| The packet header end mark | ????A | ????1 | Constant ' E ', the end (End) of expression header part | |
| Inclusion | The request particular content | Decide on particular content | ＜inclusion length 〉 | And different, tabulate referring to request type subsequently by concrete form according to request type for particular content |
The IP packet format of SAS response sees Table 3.In any request command, the length that packet header adds inclusion is always 12.
Table 3 SAS response IP packet format
| Component part | Field name | Data type | Field length | Explanation |
| Packet header | SMS?ID | ????D | ????5 | The SMS numbering |
| SMS asks ID | ????D | ????5 | SMS asks numbering | |
| Inclusion | Answer code | ????A | ????2 | Prompting SAS handles the result of authorization requests, and concrete meaning sees Table 4 |
SAS answer code form sees Table 4.
The tabulation of table 4 SAS answer code
| Answer code | The meaning of expression |
| ????00 | The SMS request runs succeeded |
| ????01 | SMS request form is wrong |
| ????02 | In the SMS bag＜the smart card number〉not registration |
| ????03 | Fatal system mistake please reconnect |
3, tabulation of SMS request type and SAS answer code
(1) connects test (Are You Alive)
SMS connects the test request form and sees Table 5, and whether normally this order is used to detect SAS operation, and the SAS answer code is referring to table 4.
(2) increase mandate (Add Product (s))
SMS increases the authorization requests form and sees Table 6.Its function is that the service product that will list in " product IDs tabulation " licenses to the smart card of listing in " tabulation of smart card number ".The SAS answer code is referring to table 4.
(3) (Cancel Product (s)) authorized in cancellation
SMS cancellation authorization requests form sees Table 7, and its function is the service product mandate of listing in contained " product IDs tabulation " on the smart card of listing in the cancellation " tabulation of smart card number ".The SAS answer code is referring to table 4.
Table 5 SMS connects the test request form
| Component part | Field name (length) | Data type | Field value | Explanation |
| Packet header | Inclusion length (4) | ????D | ????0000 | The length of inclusion part does not comprise packet header in the IP bag |
| SMS?ID(5) | ????D | ??<SMS?ID> | The SMS numbering | |
| SMS asks ID (5) | ????D | ＜request ID 〉 | SMS asks numbering | |
| Request type sign indicating number (2) | ????A | ????01 | Normally whether inquiry SAS operation | |
| Packet header end mark (1) | ????A | ????E | The end (End) of expression header part |
Table 6 SMS increases the authorization requests form
| Component part | Field name (length) | Data type | Field value | Explanation | ||
| Packet header | Inclusion length (4) | ????D | 3+13*＜smart card quantity 〉+6*＜service product quantity 〉 | The length of inclusion part does not comprise packet header in the IP bag | ||
| ????SMS?ID(5) | ????D | ????<SMS?ID> | The SMS numbering | |||
| SMS asks ID (5) | ????D | ＜request ID 〉 | SMS asks numbering | |||
| Request type sign indicating number (2) | ????A | ????11 | Increase the request code of authorizing | |||
| Packet header end mark (1) | ????A | ????E | The sign that finish in packet header | |||
| Inclusion | Smart card quantity (2) | ????D | ＜smart card quantity〉(00-50) | Increase the smart card of Authorized operation | ' 00 ' to all smart card mandate ' 01 ' single deck tape-recorder mandates | |
| The tabulation of smart card number | Intelligent card numbers 1 (13) | ????D | ＜smart card number 〉 | The tabulation of smart card number is when＜smart card quantity〉when being ' 00 ', do not have card number tabulation when＜smart card quantity〉when being ' 01 ', have only a card number | ||
| Intelligent card numbers 2 (13) | ????D | ＜smart card number 〉 | ||||
| ??? | ??? | ? | ||||
| Intelligent card numbers＜smart card quantity〉(13) | ????D | ＜smart card number 〉 | ||||
| Service product quantity (1) | ????D | ＜service product quantity〉(1-9) | Increase the service product quantity of mandate | |||
| Product I D tabulation | Service product 1 (6) | ????D | ＜product IDs 〉 | Increase the product IDs tabulation of mandate | ||
| Service product 2 (6) | ????D | ＜product IDs 〉 | ||||
| ?? | ??? | ? | ||||
| Service product＜service product quantity〉(6) | ????D | ＜product IDs 〉 | ||||
Table 7 SMS cancellation authorization requests form
| Component part | Field name (length) | Data type | Field value | Explanation | |||
| Packet header | Length (4) | D | 3+13*＜smart card quantity 〉+6*＜service product quantity 〉 | The length of inclusion part does not comprise packet header in the IP bag | |||
| SMS ID (5) | D | ＜SMS ID 〉 | The SMS numbering | ||||
| SMS asks ID (5) | D | ＜request ID 〉 | SMS asks numbering | ||||
| Request type sign indicating number (2) | A | 12 | The request code that cancellation is authorized | ||||
| Packet header end mark (1) | A | E | The sign that finish in packet header | ||||
| Inclusion | Smart card quantity (2) | D | ＜smart card quantity〉(01-50) | Cancel the smart card quantity of Authorized operation. | The product mandate of ' 01 ' cancellation one sheet smart card | ||
| The tabulation of smart card number | Intelligent card numbers 1 (13) | D | ＜smart card number 〉 | The tabulation of smart card number is when＜smart card quantity〉when being ' 01 ', have only a card number | |||
| Intelligent card numbers 2 (13) | D | ＜smart card number 〉 | |||||
| | | | |||||
| Intelligent card numbers＜smart card quantity〉(13) | D | ＜smart card number 〉 | |||||
| Service product quantity (1) | D | ＜service product quantity〉(0-9) | Cancel the service product quantity of mandate | The mandate of original all products on ' 0 ' the cancellation smart card | |||
| Product I D tabulation | Service product 1 (6) | D | ＜product IDs 〉 | The product IDs tabulation of cancelling mandate does not have the product IDs tabulation when service product quantity is ' 0 ' | |||
| Service product 2 (6) | D | ＜product IDs 〉 | |||||
| | | | |||||
| Service product＜service product quantity〉(6) | D | ＜product IDs 〉 | |||||
(4) cover original mandate (Overwr ite Entitlement)
SMS covers original authorization requests form and sees Table 8, its function uses the service product of listing in " product IDs tabulation " that the original service product mandate on the smart card of listing in " tabulation of smart card number " is covered, promptly cancel original all mandates on the smart card, give its new product mandate again.The SAS answer code is referring to table 4.
Table 8 SMS covers original authorization requests form
| Component part | Field name (length) | Data type | Field value | Explanation | ||
| Packet header | Length (4) | D | 3+13*＜smart card quantity 〉+6*＜service product quantity 〉 | The length of inclusion part does not comprise packet header in the IP bag | ||
| SMS ID (5) | D | ＜SMS ID 〉 | The SMS numbering | |||
| SMS asks ID (5) | D | ＜request ID 〉 | SMS asks numbering | |||
| Request type sign indicating number (2) | A | 13 | Cover the request code of authorizing | |||
| Packet header end mark (1) | A | E | The sign that finish in packet header | |||
| Inclusion | Smart card quantity (2) | D | ＜smart card quantity〉(01-50) | Cover the smart card quantity of Authorized operation.Be subjected to the restriction of IP bag size, the smart card quantity when asking in batches should be less than 50 | Original mandate that ' 01 ' the original mandate ' 02 '-' 50 ' that covers a sheet smart card covers a collection of smart card | |
| The tabulation of smart card number | Intelligent card numbers 1 (13) | D | ＜smart card number 〉 | The tabulation of intelligent card numbers is when＜smart card quantity〉when being ' 01 ', have only a card number | ||
| Intelligent card numbers 2 (13) | D | ＜smart card number 〉 | ||||
| | | | ||||
| Intelligent card numbers＜smart card quantity〉(13) | D | ＜smart card number 〉 | ||||
| Service product quantity (1) | D | ＜service product quantity〉(1-9) | Increase the service product quantity of mandate | |||
| The product IDs tabulation | Service product 1 (6) | D | ＜product IDs 〉 | Increase the product IDs tabulation of mandate | ||
| Service product 2 (6) | D | ＜product IDs 〉 | ||||
| | | | ||||
| Service product＜service product quantity〉(6) | D | ＜product IDs 〉 | ||||
(5) send message (Send IRD Message)
SMS sends the message request form and sees Table 9, and its function is that the smart card of listing in " tabulation of smart card number " sends message, and message content is presented on user's the video screen at once.The SAS answer code is referring to table 4.
Table 9 SMS sends the message request form
| Component part | Field name (length) | Data type | Field value | Explanation | ||
| Packet header | Length (4) | D | 13*＜smart card quantity 〉+＜message content 〉 | The length of inclusion part does not comprise packet header in the IP bag | ||
| SMS ID (5) | D | ＜SMS ID 〉 | The SMS numbering | |||
| SMS asks ID (5) | D | ＜request ID 〉 | SMS asks numbering | |||
| Request type sign indicating number (2) | A | 21 | Send the request code of message | |||
| Packet header end mark (1) | A | E | The sign that finish in packet header | |||
| Inclusion | Smart card quantity (2) | D | ＜smart card quantity〉(00-50) | Need to send the smart card quantity of message.Be subjected to the restriction of IP bag size, smart card quantity should be less than 50 | ' 00 ' sends message ' 01 ' to all smart cards sends message ' 02 '-' 50 ' to a collection of smart card transmission message to certain sheet smart card | |
| The tabulation of smart card number | Intelligent card numbers 1 (13) | D | ＜smart card number 〉 | The tabulation of intelligent card numbers is when＜smart card quantity〉when being ' 00 ', do not have card number tabulation when＜smart card quantity〉when being ' 01 ', have only a card number | ||
| Intelligent card numbers 2 (13) | D | ＜smart card number 〉 | ||||
| | | | ||||
| Intelligent card numbers＜smart card quantity〉(13) | D | ＜smart card number 〉 | ||||
| The content of message (＜300) | A | ＜message content 〉 | The particular content of message is subjected to the big or small restriction of IP bag as ' good night ', and its length should be less than 300 bytes | |||
(6) send mail (Send IRD Mail)
SMS sends the mail requests form and sees Table 10, and its function is that the smart card of listing in " tabulation of smart card number " sends mail, and Mail Contents directly is not presented on user's the video screen, checks but be stored in the set-top box waits for user.The SAS answer code is referring to table 4.
Table 10 SMS sends the mail requests form
| Component part | Field name (length) | Data type | Field value | Explanation | ||
| Packet header | Length (4) | D | 13*＜smart card quantity 〉+＜Mail Contents 〉 | The length of inclusion part does not comprise packet header in the IP bag | ||
| SMS ID (5) | D | ＜SMS ID 〉 | The SMS numbering | |||
| SMS asks ID (5) | D | ＜request ID 〉 | SMS asks numbering | |||
| Request type sign indicating number (2) | A | 22 | Send the request code of mail | |||
| Packet header end mark (1) | A | E | The sign that finish in packet header | |||
| Inclusion | Smart card quantity (2) | D | ＜smart card quantity〉(00-50) | Need to send the smart card quantity of mail.Be subjected to the restriction of IP bag size, smart card quantity should be less than 50 | ' 00 ' sends mail ' 01 ' to all smart cards sends mail ' 02 '-' 50 ' to a collection of smart card transmission mail to certain sheet smart card | |
| The tabulation of smart card number | Intelligent card numbers 1 (13) | D | ＜smart card number 〉 | The tabulation of intelligent card numbers is when＜smart card quantity〉when being ' 00 ', do not have card number tabulation when＜smart card quantity〉when being ' 01 ', have only a card number | ||
| Intelligent card numbers 2 (13) | D | ＜smart card number 〉 | ||||
| | | | ||||
| Intelligent card numbers＜smart card quantity〉(13) | D | ＜smart card number 〉 | ||||
| The content of mail (＜300) | A | ＜Mail Contents 〉 | The particular content of mail is subjected to the big or small restriction of IP bag as ' happy birthday ', and its length should be less than 300 bytes | |||
(7) reset password (Reset Password)
SMS resets the password request form and sees Table 11, and its function is reset smart card＜smart card number〉password be initial password, the SAS answer code is referring to table 4.
Table 11 SMS resets the password request form
| Component part | Field name (length) | Data type | Field value | Explanation | ||
| Packet header | Length (4) | D | 13*＜smart card quantity 〉+＜Mail Contents 〉 | The length of inclusion part does not comprise packet header in the IP bag | ||
| SMS ID (5) | D | ＜SMS ID 〉 | The SMS numbering | |||
| SMS asks ID (5) | D | ＜request ID 〉 | SMS asks numbering | |||
| Request type sign indicating number (2) | A | 31 | The password of smart card is re-set as initial password | |||
| Packet header end mark (1) | A | E | The sign that finish in packet header | |||
| Inclusion | Smart card quantity (2) | D | ＜smart card quantity〉(00-50) | Need reset the smart card quantity of password.Be subjected to the restriction of IP bag size, smart card quantity should be less than 50 | The password of ' 00 ' all smart cards is set to initial password ' 01 ' and resets the password that the password ' 02 '-' 50 ' of certain sheet smart card is reseted a collection of smart card | |
| The tabulation of smart card number | Intelligent card numbers 1 (13) | D | ＜smart card number 〉 | The tabulation of intelligent card numbers is when＜smart card quantity〉when being ' 00 ', do not have card number tabulation when＜smart card quantity〉when being ' 01 ', have only a card number | ||
| Intelligent card numbers 2 (13) | D | ＜smart card number 〉 | ||||
| | | | ||||
| Intelligent card numbers＜smart card quantity〉(13) | D | ＜smart card number 〉 | ||||
4, instruction type sign indicating number resource of Bao Liuing and instruction set expansion regulation
More than listed some basic command forms of SMS request, each manufacturer can be according to the needs of self, increase order on the basis of above command format and carry out the command set expansion following.Simultaneously, for the needs of this standard expansion, request type sign indicating number 00-49 keeps to this standard use, and each manufacturer can use the request type sign indicating number of 50-99 to carry out the command set expansion.
SMS request type code listing sees Table 12.
As shown in Figure 2, the SMS1 on the left side, top, SMS2, SMS3 line can only be selected one, and synchronization SMS-SAS interface can only be connected communication by unique SMS visit.Explanation synchronization general SMS-SAS interface module in lower part can be connected communication by a plurality of SMS visits, be connected contrast with common SAS interface communication, the more common SAS interface of general SMS-SAS interface module of the present invention has the convenience of greater flexibility and link.SMS can be connected communication with the SAS of a plurality of different CA simultaneously, a plurality of SMS can visit same SMS-SAS interface module simultaneously, common SMS-SAS interface can only be connected communication with a SMS, same SMS will must set up a plurality of the connection with the SAS communication of a plurality of different CA, this must increase the resource occupation rate, reduces communication efficiency.
Table 12 SMS request type code listing
| The request type sign indicating number | Explanation |
| ????00 | Keep |
| ????01 | Normally whether inquiry SAS operation |
| ????02-10 | Keep |
| ????11 | Increase and authorize |
| ????12 | Cancellation is authorized |
| ????13 | Cover original mandate |
| ????14-20 | Keep |
| ????21 | Send message |
| ????22 | Send mail |
| ????23-30 | Keep |
| ????31 | Reset password |
| ????32-49 | Keep |
| ????50-99 | Manufacturer's extended instruction |
The present invention's interface specification that different CA provide of giving chapter and verse, concrete interface functions such as interface type, interface instruction, calling interface mode are carried out abstract separation, set up general mandate, the message management interface specification of a cover, on this basis, realize its general-purpose interface modularization, then can reach the purpose of management such as the general SMS-SAS interface module communication of different CA system's employings is authorized, message.The SMS-SAS interface communication is embodied in two aspects: the one, and the communication between SMS-SAS interface and the SMS database, the 2nd, the network communication between SMS-SAS interface and the SAS.
Be illustrated in figure 3 as, the operating process of SMS database and SMS-SAS interface, the reading database thread is arranged in the program and analyze the response thread, handle the position all between database and intelligent array, intelligent array in the program is equivalent to the shared region between process, utilize these arrays that each thread is connected, class libraries (the MFC of MS-Visual C++, Microsoft Foundation Class) the intelligent array in can dynamically increase, so very suitable here, the flexibility that has increased program is as shown in dotted line among the figure is included.Reading database thread (nettoDB) is carried out and is read the oracle database, and it is medium to be sent then the solicited message of reading to be put into corresponding intelligence response array.When the reading database content, with open type data storehouse connectivity (ODBC, Open Database Connectivity,) be connected with database, so guarantee to have on the main frame of working procedure ORACLE ODBC to drive, and and data source connect. the communication of reading of data is with the CRECODERSET class of MFC, and the respective element in this class object correspondence database table is changed in the time of in adding corresponding array possibly.
Owing to send the request array data is to relate to the array inquiry, thus excessive if array becomes, when inquiry, can influence efficient, so when each accessing database, check array size earlier and it is limited within the scope of 50 elements.
Each connect database after, the transmission that ask, the reception of response, and database is needn't connected reference, but cycle wheel seek, so thread will block a period of time, concrete communication is finished by timer and synchronous event.
Respond the echo message of analyzing in thread (analysisThread) the analysis response array, corresponding with the request that sends and the processing of request result fed back to the SMS client database, wait for SMS user's further processing, in this thread with being connected of database, since will be in database writing information, no longer be fit to come communication, and come communication, use SQL﹠amp like this with the Cdatabase class object with the CRECODERSET class of MFC; It is more flexible and efficient that the PLUS statement writes back database to echo message and operation.
Because program will constantly receive when carrying out and respond and write back database, to refer to Seeking Truth intermittent and accessing database is concurrent, so the execution of this thread also has obstruction, concrete communication is by timer and synchronous event control.
Above-mentioned described timer comprises macrodefined RDBDATA, CHECKNET, three timers of ALIVETIMER, utilize these three timers to come the operation of drive thread, wherein RDBDATA controls the time interval of accessing database, CHECKNET is used for control and regularly sends to SAS and check and whether connect effective information, heavy and avoid network to connect having interrupted, program still sends the faulty operation of request accessing database, whether ALIVETIMER regular check network is normal, be used with CHECKNET, the assurance program is normally moved.
Above-mentioned described synchronous event is meant, thread has obstruction in the program, except timer, also will utilize synchronous event to come drive thread, sendEvent, recvEvent, four synchronous events of analysisEvent, DBEvent are arranged, when the then corresponding thread startup of incident by the time in the program.SendEvent drives and sends thread, and recvEvent drives receiving thread, and analysisEvent drives and analyzes thread, and DBEvent drives the reading database thread.
Because each thread is shared array, comes protected data safety so will introduce critical quantity, the present invention finishes defencive function with critical quantity criticalprotect, and criticalprotect is the variable of CcriticalSection class.
Two, the communication of SMS-SAS interface and SAS system
As shown in Figure 4, the communication of SMS-SAS interface and SAS system realizes: judge whether Subscriber Management System sends request to authentication management system, if, then Subscriber Management System reading database thread starts and read the data that need request from the Subscriber Management System database, and it is medium to be sent that the solicited message of reading is put into the intelligent array of request.Subscriber Management System sends thread according to the Internet protocol data bag that Subscriber Management System request format detection sends, and the request msg of correct format is sent to authentication management system.
Send thread (sendThread) and check the request array, seeing if there is the request array needs to send, if having, then utilize TCP the IP network communications agreement, by the WINSOCK connection SAS is mail in request,, check once more after then waiting for a period of time if request does not need to send.
After request of every transmission, need reserve some time to program allows receiving thread receive data, because each request is different in the processing time of SAS end, so there is delay the response time of request, and the response order and the order of transmission unanimity of getting along well are responded so should receive to the receiving thread stationary point time after sending a request.
Request has been sent out in the array but has not received that as yet the solicited message of response should not send once more, so there is a serial number to differentiate whether this request sends in each element in array.
The same with the reading database thread, this thread has obstruction, equally by timer and synchronous event communication.
After SAS handles data, the SMS receiving thread receives processing to response data, if formatted data is correct, send into and respond the medium pending data analysis of intelligent array, SMS analyzes the response process thread response data is carried out analyzing and processing, if legal data return correct result to database.
Whether data and analysis that receiving thread (recvThread) reception network transmits are legal echo messages, as not being, then ignore, and are then to put into to respond array, wait for the processing of analysis thread.
Because receiving thread receives the data of network, and the data not timing that network transmits has randomness, so this thread should not get clogged, listening port prepares to receive data at any time always.
In the process of request, response, occur unusually then carrying out abnormality processing,, repeat above-mentioned steps, otherwise finish as not disposing.
The realization key technology of SMS-SAS interface moduleization shows three aspects: realize the Iunknown interface, realize self defined interface, realize the interface inquiry, management object life cycle (numeration).Because the Iunknown interface is pure empty class, the function that it comprised all is a pure virtual function, and they do not have member variable, the SAS self defined interface is to inherit the derived class of getting off from these pure empty classes, so these Virtual Functions of communication just become by into important, Virtual Function all comes communication by calling virtual table.
Iunknown comprises three very important functions, is respectively QueryInterface, AddRef, Release.And putting in order of they also is unmodifiable.QueryInterface is used for other interface of enquiring component communication, just also has which interface class in the parent of enquiring component, and AddRef is used to increase reference count, and Release is used to reduce reference count.Making good use of these three functions can effectively manage the com assembly, make the client to inquire any other interface from the arbitrary interface in the assembly, this flexibility makes the client can obtain the relevant interface that he can know easily, and can be more reasonable, problem life cycle of safe and effective Management Unit.Communication above step, can communication class factory, inherit the IclassFactory interface, be used to create general SAS interface module example.
For guaranteeing the uniqueness of interface, adopt GUID (Globally Unique IDentifier, the global unique identification device) method produces general SAS interface module, after creating general SAS interface module example, through compiling, generate dynamic link libraries (dll) file, by the information of registration table issue assembly, the information of object, the information of interface.
The SMS assembly is a DLL, two kinds of operational modes is arranged: local, long-range.This locality is meant that DLL process and caller are on same machine but different in-process; Long-range be meant the DLL process basic just and caller on two machines.
When visiting local SAS interface module, because CLIENT PROGRAM is to be between different processes with invoked SMS assembly, they have different separately addressing spaces, so must be through scheduling to CLIENT PROGRAM at the passing interface pointer.Windows provides ready-made scheduling function.
When visiting long-range SAS interface module, DCOM (distributed component) is based on RPC, and the online Data Transport Protocol that Data transmission must adherence to standard between network will be packed earlier before the data passes, unpacks after being delivered to the destination.
The present invention proposes general Subscriber Management System and authentication management system interface specification, realizes Componentized SMS-SAS communication interface according to the general-purpose interface standard.The SMS-SAS assembly is registered, is issued by certain mode, and by visit SMS-SAS assembly, the CA that SMS just can be connected with needs carries out communication in the SMS client, finishes the whole service processing procedure of product subscription or transmission message etc.
It should be noted last that: above embodiment is the unrestricted technical scheme of the present invention in order to explanation only, although the present invention is had been described in detail with reference to the foregoing description, those of ordinary skill in the art is to be understood that: still can make amendment or be equal to replacement the present invention, for any modification or partial replacement that does not break away from the spirit and scope of the present invention, it all should be encompassed in the middle of the claim scope of the present invention.
Claims (12)
1. universal digital TV Subscriber Management System and authentication management system method for interface communication, described Digital Television comprises a cover front end user management subsystem, two cover different condition receiving front-end subsystems, Subscriber Management System and authentication management system interface module access client and long-range issue Subscriber Management System and authentication management system interface component services device is characterized in that: may further comprise the steps:
A., key set, procotol, the port of authentication management system, the indications of Subscriber Management System are set;
B., counter is set, and creates database read line taking journey, request msg transmission thread, request response data receiving thread, analyze response data write-back storehouse thread at Subscriber Management System;
C. judge whether Subscriber Management System sends request to authentication management system, if, then Subscriber Management System reading database thread starts and read the data that need request from the Subscriber Management System database, and it is medium to be sent that the solicited message of reading is put into the intelligent array of request;
D. Subscriber Management System sends thread according to the Internet protocol data bag that Subscriber Management System request format detection sends, and the request msg of correct format is sent to authentication management system;
E. after authentication management system was handled data, the Subscriber Management System receiving thread received processing to response data, if formatted data is correct, sent into and responded the medium pending data analysis of intelligent array;
F. Subscriber Management System analysis response process thread carries out analyzing and processing to response data, if legal data return correct result to database.
2. universal digital TV Subscriber Management System according to claim 1 and authentication management system method for interface communication is characterized in that: the procotol among the described step a adopts transmission Control Network agreement, uses port to be 4000-6999.
3. universal digital TV Subscriber Management System according to claim 1 and authentication management system method for interface communication, it is characterized in that: the request msg among the described step b sends the request msg employing Internet protocol packet format that thread sends, packet header length is 17, the indications, request indications and the request type sign indicating number that comprise Subscriber Management System, authentication management system also adopts the Internet protocol packet format, it is 12 that packet header adds inclusion length, comprises indications, request indications and the authentication management system respond style sign indicating number of Subscriber Management System.
4. universal digital TV Subscriber Management System according to claim 1 and authentication management system method for interface communication, it is characterized in that: the request among the described step b comprises the connection test request, increase authorization requests, the cancellation authorization requests, cover original authorization requests, send message request, send mail requests, the password reset request, except that connecting test request, the form of all requests comprises packet header and inclusion, inclusion comprises smart card quantity, smart card number list field increases authorization requests, the cancellation authorization requests, the inclusion that covers original authorization requests also comprises product indicia symbol list field.
5. universal digital TV Subscriber Management System according to claim 4 and authentication management system method for interface communication, it is characterized in that: in the described increase authorization requests field, ' 00 ' expression is to all smart card mandates, and ' 01 ' is the single deck tape-recorder mandate, ' 02 '-' 50 ' expression batch authorization.
6. universal digital TV Subscriber Management System according to claim 4 and authentication management system method for interface communication, it is characterized in that: in the described cancellation authorization requests, the product mandate of ' 01 ' expression cancellation one sheet smart card, the product mandate of a collection of smart card of ' 02 '-' 50 ' expression cancellation.
7. universal digital TV Subscriber Management System according to claim 4 and authentication management system method for interface communication, it is characterized in that: in the original authorization requests of described covering, original mandate that ' 01 ' expression covers a sheet smart card, original mandate that ' 02 '-' 50 ' expression covers a collection of smart card.
8. digital television system common user management system according to claim 1 and authentication management system method for interface communication, it is characterized in that: the intelligent array among the described step b is equivalent to the shared region between process, be used for each thread is connected, intelligent array can dynamically increase.
9. digital television system common user management system according to claim 1 and authentication management system method for interface communication, it is characterized in that: the request among the described step c-e sends, responds to receive and adopt cycle wheel to seek mode, request and response thread obstruction for some time block and are finished by timer and synchronous event.
10. digital television system common user management system according to claim 9 and authentication management system method for interface communication, it is characterized in that: the free interval timer of described timer, connect and check timer, three kinds of regular check network timers, control the time interval of accessing database respectively, control regularly sends to the user authorization management system and checks and whether connect effectively the faulty operation that when avoiding network to connect having interrupted program still sends the request accessing database, or with time interval timer whether be used the regular check network normal, the assurance program is normally moved.
11. digital television system common user management system according to claim 9 and authentication management system method for interface communication, it is characterized in that: described synchronous event comprises transmission incident, reception incident, analysis incident, driving data storehouse incident, send event-driven and send thread, receive the event-driven receiving thread, analyze event-driven and analyze thread, driving data storehouse event-driven reading database thread.
12. digital television system common user management system according to claim 1 and authentication management system method for interface communication, it is characterized in that: the key set of authentication management system, procotol, port, Subscriber Management System indications among described step a, the b, counter, adopt the global unique identification device to be provided with or establishment with database read line taking journey, request msg transmission thread, request response data receiving thread, analysis response data write-back storehouse thread, generate dynamic link library file afterwards, and by registration table distribution protocol information.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2004100006199A CN100346648C (en) | 2004-01-13 | 2004-01-13 | General user management system for digital television set and interface communication method of authorization management system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2004100006199A CN100346648C (en) | 2004-01-13 | 2004-01-13 | General user management system for digital television set and interface communication method of authorization management system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN1642264A true CN1642264A (en) | 2005-07-20 |
| CN100346648C CN100346648C (en) | 2007-10-31 |
Family
ID=34866819
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNB2004100006199A Expired - Fee Related CN100346648C (en) | 2004-01-13 | 2004-01-13 | General user management system for digital television set and interface communication method of authorization management system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN100346648C (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106790035A (en) * | 2016-12-15 | 2017-05-31 | 郑州云海信息技术有限公司 | A kind of protocol analysis device, method and system |
| CN107197018A (en) * | 2017-05-23 | 2017-09-22 | 北京奇艺世纪科技有限公司 | A kind of method and apparatus of inter-system data synchronization |
| CN107659379A (en) * | 2016-08-03 | 2018-02-02 | 平安科技（深圳）有限公司 | Ask feedback method and service server |
Family Cites Families (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| NZ500194A (en) * | 1997-03-21 | 2000-12-22 | Canal Plus Sa | Broadcasting randomized subscriber entitlement management messages for digital television |
| ATE345645T1 (en) * | 1997-03-21 | 2006-12-15 | Canal Plus Technologies | BROADCASTING AND RECEPTION SYSTEM AND CONDITIONAL ACCESS SYSTEM THEREOF |
| JP2004501579A (en) * | 2000-06-19 | 2004-01-15 | オン コマンド コーポレーション | Secure multimedia communication system |
| CN1284818A (en) * | 2000-09-29 | 2001-02-21 | 清华大学 | Full digital conditioned receiving method for video broadcost in cable TV network |
| CN1111335C (en) * | 2000-12-15 | 2003-06-11 | 上海南广电子技术有限公司 | Conditioned narrow-band reception scheme in wide-band data broadcast |
| CN1413024A (en) * | 2001-10-08 | 2003-04-23 | 北京中视联数字系统有限公司 | Digital TV user management system |
| CN1175666C (en) * | 2001-11-26 | 2004-11-10 | 国家广播电影电视总局广播科学研究院 | Digital TV subscriber management system and multiple-condition receiving system connection realizing method |
-
2004
- 2004-01-13 CN CNB2004100006199A patent/CN100346648C/en not_active Expired - Fee Related
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107659379A (en) * | 2016-08-03 | 2018-02-02 | 平安科技（深圳）有限公司 | Ask feedback method and service server |
| CN107659379B (en) * | 2016-08-03 | 2020-09-18 | 平安科技（深圳）有限公司 | Request feedback method and service server |
| CN106790035A (en) * | 2016-12-15 | 2017-05-31 | 郑州云海信息技术有限公司 | A kind of protocol analysis device, method and system |
| CN107197018A (en) * | 2017-05-23 | 2017-09-22 | 北京奇艺世纪科技有限公司 | A kind of method and apparatus of inter-system data synchronization |
| CN107197018B (en) * | 2017-05-23 | 2020-01-21 | 北京奇艺世纪科技有限公司 | Method and device for data synchronization between systems |
Also Published As
| Publication number | Publication date |
|---|---|
| CN100346648C (en) | 2007-10-31 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101034990A (en) | Right management method and device | |
| CN1503942A (en) | Resource action in clustered computer system incorporating prepare operation | |
| CN1933425A (en) | Module and method for realizing equipment access interface, equipment access system and method | |
| CN1960287A (en) | Method and apparatus for scheduling jobs on a network | |
| CN1943160A (en) | System for invoking a privileged function in a device | |
| CN100346298C (en) | System and method for remotely loading or upgrading program | |
| CN1752896A (en) | Power source management method of embedded equipment under operation system cooperation and its system | |
| CN1894649A (en) | Display apparatus management system and method thereof | |
| CN101056175A (en) | Disk array and its access right control method and device, server and server system | |
| CN1852175A (en) | Data-logging method and system therefor | |
| CN1632774A (en) | Identification method for USB interface equipment | |
| CN111651738B (en) | Fine-grained role authority unified management method based on front-end and back-end separation architecture and electronic device | |
| CN110851802A (en) | Authority control method, device, equipment and computer readable medium | |
| CN100346648C (en) | General user management system for digital television set and interface communication method of authorization management system | |
| CN1665240A (en) | Apparatus and method for reporting operation state of digital rights management | |
| CN1256663C (en) | Management method possessing real time helping function in insertion type system | |
| CN1801086A (en) | Equipment support implementing method applied in Java operation system | |
| CN1292115A (en) | Apparatus and method for dynamically verifying information in distributed system | |
| CN100340978C (en) | Component processing system and component processing method | |
| CN1100299C (en) | System, method, and article of manufacture for access control on method invocation on protected object in object oriented system | |
| CN1889038A (en) | Method for managing long-distance structural components service cycle with class as unit | |
| CN1905443A (en) | Method and system of automatic login server for client | |
| CN101819524B (en) | Access method of RFID (Radio Frequency Identification Device) reader and interface driving device thereof | |
| CN1298506A (en) | Method and system for facilitating access to a lookup service | |
| CN1889036A (en) | Family network system user interface system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| C19 | Lapse of patent right due to non-payment of the annual fee | ||
| CF01 | Termination of patent right due to non-payment of annual fee |