Embodiment
Below, describe the preferred embodiments of the present invention in detail with reference to accompanying drawing.
Fig. 1 is used to illustrate the flow chart that enters the method for session (in session) notice according to the reception of one embodiment of the invention.The situation that Fig. 1 illustrates the notice that receives from provider'snetwork 12 when being the notice relevant with the service of setting session.
With reference to Fig. 1end entity 10 are the entities that receive reservation service from provider's network 12.End entity 10 utilizes the service of provider'snetwork 12 by thegateway entity 11 that is contained in same household network (residential network).
Service can be IPTV (IPTV)service.End entity 10 can be the end entity according to open IPTV functional architecture, andgateway entity 11 can be the IP Multimedia System gateway according to open IPTV functional architecture.The entity of provider'snetwork 12 can be to provide IPTV all entities of service to the household network according to open IPTV functional architecture.
In step 110,end entity 10 drives the application program of the service that the entity that is used to utilize provider'snetwork 12 provides.The application program thatend entity 10 drives be the application program relevant with the IPTV service comprise be used to utilize multimedia service, with the application program of selecting content (content on demand) service, chatting service, attending multiple services such as (presence) service.For example, drive the multimedia regeneration application program of the multi-medium data that is used to regenerate, perhaps drive the chat application that is used to utilize chatting service.
In step 112,end entity 10 is asked the predetermined service ofgateway entity 11 initialization according to the driving of the application program of step 110.Can be by being sent togateway entity 11 according to the HTTP request message that open IPTV functional architecture generates, the initialization of request service thus.
In step 114,gateway entity 11 is to the entity requests initialization service of provider's network 12.The initialization request message that end entity in the step 112 10 is transmitted is transmitted in the entity of provider's network 12.And, the HTTP request message that receives in the step 112 can be converted to according to Session initiation Protocol (Session Initiation Protocol, conversation initialization message SIP), and be sent to the entity of provider'snetwork 12, the initialization of request service thus.
In step 116, the entity of provider's network 120 will be circulated a notice of requested service has been initialised in the step 114 initialization and finish message and be transmitted in gateway entity 11.And, can transmit the response message that generates according to SIP togateway entity 11.
In step 118,gateway entity 11 transmits the initialization that requested service has been initialised in the circular step 112 to endentity 10 and finishes message.And, can convert the response message that generates according to SIP that receives in the step 116 to http response message, and be transmitted inend entity 10.
In step 120,end entity 10 transmits at the information of carrying out the session of initialized service by step 112 to step 118 to gateway entity 11.To be transmitted ingateway entity 11 at the information of service conversation, and makegateway entity 11 can exactly notice be relayed to application program in the driving.
Think to makeend entity 10 utilize service #1~#n, the example of driver application #1~#n describes.When the notice that receives from provider'snetwork 12 was the notice of the relevant service #1 that utilizes by application program #1,gateway entity 11 need be transmitted in this notice application program #1.
The situation that household network possesses a plurality of end entity is also identical therewith.Gateway entity 11 step 112 to endentity 10 transmission of 118 initialization service of passing through in a plurality of end entity is exactly notified.
Thus, in step 120,end entity 10 will be as can particularterminal entity 10 and the information of application program, promptly at being transmitted ingateway entity 11 by step 112 to the information of 118 initialized services.
In the step that step 112 to 118 initialization is served, the message that generates according to SIP of entity transmitting-receiving comprises the call identifier (identifier) that can discern various service conversations, i.e. " call ID ".In step 120,end entity 10 can be sent togateway entity 11 as the information of carrying out initialized service conversation in step 112 in to 118 with these call identifiers.
In step 122, the entity of provider'snetwork 12 will with step 112 to 118 in the relevant notice of initialized service be sent togateway entity 11.
In step 124,gateway entity 11 is with reference to the information at service conversation that receives in the step 120, and the notice that will receive in step 122 is sent to end entity 10.To compare at the call identifier of step 120 call identifier that receives and the notice that receives in step 122, and notice is sent to the application program that is driving in theend entity 11.
Notice can be according to for making the agreement transmission that define as communication between theend entity 10 of household network entity and the gateway entity 11.For example, the notice that receives in step 122 can be transmitted inend entity 10 according to the form that open IPTV functional architecture becomes the HTTP document.And, when the notice of step 122 reception generates according to SIP, can be that the form of HTTP document is sent toend entity 10 with each field (field) value transform of SIP.
Step 120 is to 124 can (Asynchronous JavaScript and XML AJAX) realizes according to asynchronous JavaScript and extend markup language.In other words,, whenend entity 10 transmits information 120 at service conversation, askgateway entity 11 simultaneously if receive the notice of related service, then be given to endentity 10 in the notice that will receive according to AJAX in step 120.Should be according to the request continuously effective of AJAXgateway entity 11 reception notifications to the step 122, and be sent toend entity 10 in the notice that step 124 will receive.
Fig. 2 is used to illustrate that reception according to another embodiment of the present invention enters the flow chart of the method for session (in session) notice.Fig. 2 is as Fig. 1, the notice that receives from provider'snetwork 12 is shown is the situation of the notice relevant with the service of setting session.
With reference to Fig. 2, in step 210end entity 10 driver application, the service that provides with the entity that utilizes provider's network 12.Identical with the step 210 of Fig. 1.
In step 212,end entity 10request gateway entities 11 are according to the application driven of step 210 and the predetermined service of initialization.Identical with the step 212 of Fig. 1.
In step 214,gateway entity 11 is to the predetermined entity request initialization service of provider's network 12.Identical with the step 214 of Fig. 1.
In step 216, the entity of provider's network 120 will be circulated a notice of the message that requested service has been initialised in step 214 and be sent to gateway entity 11.Identical with the step 216 of Fig. 1.
In step 218,gateway entity 11 will be circulated a notice of to finish message in the initialization that step 212 requested service has been initialised and be sent to end entity 10.The response message according to the SIP generation that receives in step 216 can be become http response message and be sent to endentity 10.
In step 218, the response message that the circular service that transmits to endentity 10 has been initialised can comprise the information at the socket communication that receives the notice relevant with service.
In step 218 to 228, the method that the reception according to another embodiment of the present invention shown in Fig. 2 enters conversation informing utilize the socket communication transmitting-receiving with step 212 to 218 in the relevant notice of initialized service.
Therefore, in step 218, the information that message comprises the socket communication that is used to set up the transmitting-receiving notice is finished in the initialization thatgateway entity 11 is sent to end entity 10.For example, can comprise in order to receive and dispatch the socket communication of notice, and the information at socket of distributing bygateway entity 11, i.e. associated internet protocol (Internet protocol, IP) information of address and portnumbers.Gateway entity 11 is given service conversation, and promptly each call identifier distributes different sockets, makes the notice that receives from the entity ofhousehold network 12 be sent to application program accurately.Describe with reference to Fig. 3 a and Fig. 3 b.
Fig. 3 a and Fig. 3 b illustrate the HTTP(Hypertext Transport Protocol) response message at the information of socket (Socket) of comprising according to one embodiment of the invention.
With reference to Fig. 3 a and Fig. 3 b, be sent to the header of http response message ofend entity 10 or newspaper (body) in step 218 and can comprise information at socket.
Refer again to Fig. 2, instep 220,end entity 10 is finished the socket information that message comprises based on the initialization that receives in step 218, realizes socket communication, be used for receiving with in step 212 to the relevant notice of 218 services that are initialised.
In step 210, can in the application plug that has driven (plug-in), drive and be used to receive and dispatch the plug-in unit of notice, to realize socket communication.At this moment, also can together be sent togateway entity 11 at step 212 to the call identifier of 218 service conversations that are initialised.
In step 222,gateway entity 11 receives and the relevant notice of service that is initialised to 218 in step 212 from the entity of provider'snetwork 12.
In step 224,gateway entity 11 will be sent to endentity 10 in the notice that step 222 receives.To be sent to endentity 10 in the notice that step 222 receives based on the call identifier that receives fromend entity 10 at the information of the socket that is sent to endentity 10 in step 218 and instep 220.
Whether judgement is identical with the call identifier that receives instep 220 at the information of the call identifier that comprises among the notice #1 that receives in step 222, if judged result is identical, then in step 224,gateway entity 11 is transmitted in the notice that step 222 receives by the socket communication of setting up instep 220.
If the call identifier difference, socket then, i.e. IP address and port numbers difference, even thereby in the end entity 10 a plurality of application programs drive, the notice that receives in step 222 also can be sent to the application program that drives in step 210.
In step 226,gateway entity 11 receives another notice from the entity of provider's network 12.As with step 212 relevant notice of initialized service in 218, be sent to endentity 10 by step 228.Be different from the transmitting-receiving of the communication that utilizes AJAX, the transmitting-receiving of the notice of thestep 220 shown in Fig. 2 to 228 utilizes socket communication.Thus, in a single day socket communication is set up, and even without the other request of request transfer notice,gateway entity 11 can continue the notice of related service is sent to endentity 10.
Fig. 4 is used to illustrate the flow chart that leaves the method for session (out of session) notice according to the reception of one embodiment of the invention.Fig. 4 illustrates the notice that receives from provider'snetwork 12 situation for the notice relevant with the service of not setting session.
In step 410,gateway entity 11 is from the entity reception notification of provider's network 12.The notice that receives is and the current relevant notice of service of not setting session, can be the notice that generates according to SIP.
Instep 412,gateway entity 11 will be sent to endentity 10 in the data at notification type that step 410 receives.
Instep 412, gateway entity will comprise at the transfer of data of notification type to the method for end entity and transfer to the method for end entity based on IP multiplex broadcasting (multicast) from gateway entity; When the user logins end entity, utilize AJAX in advance to the conversation informing of leaving of gateway entity request at the user, and the method for transmitting as this request responding; When perhaps the user logined end entity, gateway entity transmission was used for the IP address and the port of socket communication, so that end entity connects particular socket, and passed through the method for the socket communication transmission that connected.
Instep 412,gateway entity 11 judges that at first whether the notice that receives in step 410 is the notice at the end entity user who signs in togateway entity 11.
When the notice that receives in step 410 is the notice that generates according to SIP, because specific notification received user in ' To ' field, therefore in step 214,gateway entity 11 will compare the field value of ' To ' field with at logining in the user profile of gateway entity 11.If identical with the field value of ' To ' field, then will be sent to endentity 10 at the data of notification type to logining in the user profile ofgateway entity 11.
According to one embodiment of the invention, instep 412, the data at notification type thatgateway entity 11 transmits can also comprise the URL(uniform resource locator) at application program (Uniform Resource Locator, information URL) thatend entity 10 needs drive.To be contained at the data of notification type for the URL that handles notice and needs the application program of driving and be sent to endentity 10, and makeend entity 10 only drive the application program of appointment.
And, can comprise the parameter relevant at the data of notification type with the driving of application program.For example, driver application can be contained among the data at notification type that are sent to endentity 10 instep 412 with the field value of initialization service conversation necessary ' CallID ' according to SIP, ' To ', ' From ' etc.
Instep 414,end entity 10 is based on the information to notification type that receives instep 412, drives the application program of the notice that is used to handle reception.And, the application program that will drive based on Information Selection at notification type, and drive the application program of selecting.For example, instep 412, when the notice that receives fromgateway entity 11 be notice at chat invitation, the driving chat application; When this notice during, drive the down load application program, with received content for the notice that transmits at content.
As previously mentioned, when the data at notification type comprise the URL information of the application program that needs drive, the application program specific according to the URL information-driven.At this moment, also can be according to the driving parameter application program relevant with the driving of application program.
In step 416,end entity 10 is based on the application program that drives instep 414, from the data ofgateway entity 11 receptions at content of announcement.
In step 416, can receive and dispatch according to AJAX at the data of content of announcement.The data that 11 transfers receive in step 410 according to AJAX request gateway entity at content of announcement, and as the data that receive at request responding at content of announcement.
And, in step 416, can realize by socket communication at the transmitting-receiving of the data of content ofannouncement.In step 412, whenend entity 10 receives at the data of notification type, receive the information thatgateway entity 11 distributes simultaneously at socket, and in step 416 based on information to socket, set up the socket communication of the transmitting-receiving that is used to notify.Afterwards, the socket communication ofend entity 10 by setting up, transmitting-receiving is at the content of notice.
Fig. 5 a and Fig. 5 b illustrate at data request information and response message according to the content of announcement of one embodiment of the invention.
Request letter message and response message when Fig. 5 a and Fig. 5 b illustrate according to AJAX transmitting-receiving the data of content of announcement.
Shown in Fig. 5 a, in step 416,end entity 10 will comprise the information at the session of serving relevant with the notice of step 410, and the HTTP request message that promptly comprises call identifier is sent togateway entity 11, as response, receive http response message as shown in Figure 5 to this.Http response message comprises " paramdata " as content of announcement.
The call identifier of request message that is contained in Fig. 5 a is with identical from the call identifier that notice comprised that provider'snetwork 12 receives at step 410gateway entity 11, whengateway entity 11 will be sent to endentity 10 at the data of notification type instep 412, transmit information simultaneously at call identifier.
Gateway entity 11 only when the call identifier that is contained in request message is identical with the call identifier that is contained in the notice that receives in step 410, just is sent to endentity 10 with response message.
In step 416, by socket communication or be sent to the data at content of announcement ofend entity 10 according to AJAX, shown in Fig. 5 b, can transmit with the HTTP document form, also can be sent to endentity 10 with the general XML document form of non-HTTP document form.
Fig. 6 is used to illustrate that according to another embodiment of the present invention reception leaves the flow chart of the method for session (out of session) notice.
With reference to Fig. 6, in step 610,gateway entity 11 notifies 410 from what the entity reception of provider'snetwork 12 was scheduled to.Identical with the step 410 of Fig. 4.
In step 612,gateway entity 11 will be sent to endentity 11 in the notice that step 410 receives.That is, will be sent to endentity 10 at the data of notification type and the data of content of announcement.
In step 612, gateway entity will comprise at the data of notification type and at the transfer of data of content of announcement to the method for end entity and transfer to the method for end entity based on IP multiplex broadcasting (multicast) from gateway entity; When the user logins end entity, utilize AJAX in advance to the conversation informing of leaving of gateway entity request at the user, and as the request of this response and the method for transmitting; When perhaps the user logined end entity, gateway entity transmission was used for the IP address and the port of socket communication, connected particular socket at end entity thus, and passed through the method for the socket communication transmission that connected.
In step 614,end entity 10 is used to handle the application program of the notice of reception based on driving at the information of notification type of receiving in step 612.And, the application program that will drive based on the Information Selection of notification type, and drive application program for using service to select.
In step 616,end entity 10 obtains content of announcement based on the application program that drives in step 614 from the data at content of announcement.(application programming interface API) obtains content of announcement from the data at application content at the application programming interfaces of the application program of step 614 driving in utilization.When the data at application content are XML document, obtain the value that preset label comprised in the XML document.
For example, when utilizing " getdata " among the API to obtain the text line of " paramdata " label that is contained in XML document, can utilize grammer to obtain content of announcement from XML document as " getdata (paramdata) ".
Fig. 7 a is the notice receiving system that illustrates according to anotherend entity 10 of one embodiment of the invention.Fig. 7 a illustrates the structure that endentity 10 receives the notice receiving system when entering conversation informing.
With reference to Fig. 7, comprise application drivenportion 710 andnotice acceptance division 720 according to theend entity 10 of one embodiment of the invention.
Application drivenportion 710 drives the application program relevant with reservation service.Along with the driving of application program, the service that initialization provides from the outside of household network, and the initialization service realizes by the gateway entity of same household network.
To be sent to gateway entity according to the HTTP request message that open IPTV functional architecture generates, gateway entity is converted to conversation initialization message according to SIP with the HTTP request message thus, and be sent to the entity of provider's network, with request service initialization.
In the process of initialization service, also can be received as the socket communication of transmitting-receiving notice and socket that gateway entity distributes, promptly at the information of IP address and port numbers from gateway entity.
Notice acceptance division 720 from gateway entity receive with in the relevant notice of application drivenportion 710 initialized services.To be sent to gateway entity at information, and, receive the notice that gateway entity transmitted based on the information that is transmitted at service conversation at application drivenportion 710 initialized service conversations.Information at service conversation can be the information at call identifier that endentity 10 utilizes in the initialization service conversation.
Notice acceptance division 720 can be according to the AJAX reception notification.Transmission is during at the information of service conversation, to the gateway entity request, with when the reception notification, be given to endentity 10 in the notice that will receive according to AJAX.This receives the notice of related service according to the request of AJAX valid till gateway entity, and the notice that will receive is sent to end entity.
And noticeacceptance division 720 can pass through the socket communication reception notification.The socket that noticeacceptance division 720 distributes based on gateway entity, promptly, information to IP address and port numbers is set up socket communication, to be used for process in the 710 initialization service of application driven portion, the socket communication of the notice that transmitting-receiving receives, and the socket communication reception notice relevant with service by setting up.
Fig. 7 b is the notice receiving system that endentity 10 according to another embodiment of the present invention is shown.Fig. 7 b illustrates the structure that endentity 10 receives the notice receiving system when withdrawing from conversation informing.
With reference to Fig. 7 b,end entity 10 according to the present invention comprises application drivenportion 730 andnotice control part 740, andnotice control part 740 comprises applicationprogram selection portion 742 andnotice acceptance division 744.
Application drivenportion 710 receives at the data of notification type fromnotice control part 740 and drives predetermined application program.That is the service that provides for the entity that utilizes by the household network outside and drive predetermined application.
Notice control part 740 receives at the information of notification type and at the data of content of announcement from gateway entity, and selects the application program that will drive in application drivenportion 710.
Applicationprogram selection portion 742 is from the data of gateway entity reception at notification type, and selection need be in the application program of application drivenportion 730 drivings.If comprise the URL information of the application program of needs driving in the information to notification type, then the application program that need drive based on the URL Information Selection.
Notice acceptance division 744 is from the data of gateway entity reception at content of announcement.
Notice acceptance division 744 can be according to the AJAX reception notification.That is, transmit notice, and, receive data at content of announcement as to request responding to the gateway entity request.
And noticeacceptance division 744 can be by socket communication from the data of gateway entity reception at content of announcement, and wherein this socket communication is set up by the plug-in unit of the application program that is driving in application drivenportion 730, and is used for the transmitting-receiving notice.
Notice acceptance division 744 receives at the data of content of announcement and during at the data of notification type from gateway entity simultaneously, need not again to receive data, utilize the API that obtains content of announcement that the data of content of announcement are obtained content of announcement at content of announcement from gateway entity.
Fig. 8 is the flow chart that is used to illustrate the method for notifying according to the gateway entity transfer of one embodiment of the invention.
Instep 810, whether gateway entity is judged and is in the driving at end entity from the relevant application program of the notice of the entity reception of household network outside.
At first, with being contained in notice end entity user's information and the information of logining in the user of gateway entity are compared, judge thus whether notification received user is the user who logins in gateway entity.For example, the notice that generates according to SIP, " To " field specific notification received user, field value that therefore will " To " field and logining in the user's of gateway entity information compares.
If the user in the notice is exactly the user who logins in gateway entity, judge then whether the relevant application program of notice that receives with the user drives.Gateway entity compares by at least one information and the notice to service conversation that compares at the user in the transfer, judges thus whether relevant application program drives.
Gateway entity can also judge whether the socket of the notice that is used to receive and dispatch reception distributes.If the socket that is used to receive and dispatch notice at the call identifier of notice distributes, then can judge with notifying relevant application program to drive.
And, if the call identifier that the request of the notice that has received from end entity according to AJAX transmits is identical with the call identifier of the notice that the entity from the household network outside receives, then gateway entity can judge that the application program relevant with the notice of reception drives.
Instep 810, if being judged as the application program relevant with the notice that receives drives, then instep 820, gateway entity will enter conversation informing and be sent to end entity.To enter the method that conversation informing is sent to end entity for gateway entity and carry out explanation with reference to Fig. 1 and Fig. 2.
Instep 810, do not drive if be judged as the application program relevant with the notice that receives, then instep 830, gateway entity will withdraw from conversation informing and be sent to end entity.To withdraw from the method that conversation informing is sent to end entity for gateway entity and carry out explanation with reference to Fig. 1 and Fig. 2
Fig. 9 is the gateway entity that illustrates according to one embodiment of the invention.
With reference to Fig. 9, comprisenotice transhipment department 910 andmapping portion 920 according to thegateway entity 11 of one embodiment of the invention.
The notice that noticetranshipment department 910 will receive from the entity of provider's network is sent to end entity.And judge at end entity whether the application program relevant with the notice that is received is driving, and will enter conversation informing thus or withdraw from conversation informing to be sent to terminal.
Mapping portion was used in the socket of transmitting-receiving notice in 920 minutes, that is, and and IP address and port numbers, and the map information that shines upon one to one of the storage socket that will distribute and call identifier.Notice transhipment department 910 will enter conversation informing when being sent to end entity,notice transhipment department 910 is with reference to map information, by distributing the socket of the call identifier identical, notice is sent to end entity with the notification call identifier of the entity reception of provider network.
As above-mentioned, though the present invention describes by embodiment and the accompanying drawing that limits, the invention is not restricted to the foregoing description, those skilled in the art can carry out multiple modification and distortion according to these records.Thus, thought of the present invention should be grasped by the claim scope, and equates or distortion of equal value all should belong to the scope of the inventive concept in this.And, can realize with computer-readable code at computer-readable recording medium according to system of the present invention.
For example, as Fig. 7 a, Fig. 7 b and shown in Figure 8, the notice receiving system of the embodiment that illustrates according to the present invention and notice transferring device can comprise the bus that is coupled in each unit and be incorporated at least one processor of described bus.And, can also comprise with the message of stored command, reception or the message of generation, and be incorporated into described bus, and be coupled at least one processor that is used for carrying out foregoing order.
And computer-readable recording medium comprises the tape deck that stores by all kinds of the data of computer system-readable.For example, recording medium has read-only memory (ROM), random-access memory (ram), CD (CD-ROM), tape, floppy disk (floppy disk), optical data storage device etc., and also comprise situation with the form realization of carrier wave (for example, transmitting) by the Internet.Again, can store and carry out the computer system that is dispersed in networking in the computer readable recording medium storing program for performing, in the mode of disperseing by computer-readable code.