CN101989978A - Method, device and system for forwarding data by real time streaming protocol (RTSP) proxy - Google Patents

Abstract

The embodiment of the present invention discloses a method, device and system for forwarding data by a real-time streaming protocol proxy. The method includes: receiving a real-time streaming protocol RTSP request from a real-time streaming protocol client through a real-time streaming protocol proxy; The association relation table of terminal identification and service identification; According to this association relation table, described RTSP response message is forwarded to the real-time stream protocol client corresponding with described client identification, has solved the response that real-time stream protocol agent can't distinguish server to return The real-time streaming protocol client to which the message belongs leads to the problem that the client cannot receive the response message, improves the function of RTSP Proxy, and simplifies the processing flow of the real-time streaming protocol proxy.

Description

A method, device and system for proxy forwarding data of a real-time streaming protocol

technical field

The invention relates to the field of communication technology, in particular to a method, device and system for forwarding data by a real-time streaming protocol agent.

Background technique

Real Time Streaming Protocol (RTSP) is a protocol dedicated to media on-demand control, based on server/client architecture. Both the client and the server can actively send messages to each other. A TCP connection must first be established between the client and the server, and all subsequent session control message exchanges will take place on this connection. Real-time streaming protocol 2.0 defines several main message methods to express the main functions required for control, and use these messages to control media stream transmission. For example, the message has description query DESCRIBE, get parameter GET_PARAMETER, option OPTIONS , Pause PAUSE, play PLAY, redirect REDIRECT, build session SETUP, set parameter SET_PARAMETER, end session TEARDOWN.

Real-time streaming protocol proxy RTSP Proxy is a network device between the client RTSP Client (hereinafter referred to as Client) of the RTSP protocol and the server RTSP Server (hereinafter referred to as Server) of the RTSP protocol. Figure 1 shows the real-time streaming protocol proxy architecture As shown in the figure, RTSP Proxy has the function of forwarding RTSP signaling and forwarding the RTP media stream from Server to Client. RTSP Proxy plays the role of server and client at the same time, as shown in Figure 1, for RTSP Client, RTSP Proxy is its server, and for RTSP Server, RTSP Proxy is its client. When the RTSP Client sends an RTSP request message to the RTSP Server, the RTSP Proxy forwards it to the RTSP Server after receiving the request message; when the RTSP Server returns a response message to the RTSP Client, the RTSP Proxy forwards it to the RTSP Client after receiving the response message from the Server.

During the research and practice of the prior art, the inventor found that the prior art has the following problems: when an RTSP Proxy accesses multiple RTSP Clients, it will receive multiple RTSP request messages from multiple RTSP Clients, but due to The messages between an RTSP Proxy and the RTSP Server are carried on the same network link (TCP link or UDP link), so when the RTSP Proxy forwards the multiple request messages to the RTSP Server, the RTSP Server cannot distinguish which messages these messages belong to RTSP Client cannot create a session for each RTSP Client, and RTSPProxy cannot send the response message returned by the RTSP Server to the corresponding requesting RTSPClient, resulting in the client being unable to receive the response message and affecting the interaction of signaling messages.

Contents of the invention

Embodiments of the present invention provide a method, device and system for forwarding data by a real-time streaming protocol proxy RTSP Proxy, which is used to solve the problem that the RTSP Proxy accesses multiple RTSP protocol clients, and the RTSP Proxy cannot send the response message returned by the RTSP Server to the corresponding RTSP Client at the requesting end, which causes the problem that the client cannot receive the response message.

The embodiment of the present invention provides a real-time streaming protocol agent RTSP Proxy forwarding data method, including:

receiving a first real-time streaming protocol RTSP request from a plurality of real-time streaming protocol clients;

According to the RTSP request, assign a client identifier and a service identifier to the real-time streaming protocol client, and generate an association table of the client identifier and the service identifier;

Forwarding the RTSP request carrying the service identifier to a real-time streaming protocol server;

receiving the first RTSP response message from the real-time streaming protocol server, the first RTSP response message carrying the service identifier, and using the service identifier as an index to obtain the client identifier by searching the association table, and The first RTSP response message is forwarded to the real-time streaming protocol client corresponding to the client identifier.

The embodiment of the present invention provides a real-time streaming protocol proxy RTSP Proxy device for forwarding data, including:

A first receiving unit, configured to receive a first real-time streaming protocol RTSP request from multiple real-time streaming protocol clients;

An association table generation unit, configured to assign the client ID and service ID to the real-time streaming protocol client according to the RTSP request, and generate an association table between the client ID and the service ID;

A first sending unit, configured to forward the RTSP request carrying the service identifier to a real-time streaming protocol server;

A second receiving unit, configured to receive a first RTSP response message from the real-time streaming protocol server, where the RTSP response message carries the service identifier;

The second sending unit is configured to use the service identifier carried in the RTSP response message received by the second receiving unit as an index, obtain the client identifier by searching the association table, and forward the RTSP response message to the The client identifier corresponds to the real-time streaming protocol client.

The embodiment of the present invention provides a real-time streaming protocol proxy RTSP Proxy system for forwarding data, including: a plurality of real-time streaming protocol clients, real-time streaming protocol agents and real-time streaming protocol servers:

The real-time streaming protocol client is connected with the real-time streaming protocol agent, and is used to send the first real-time streaming protocol RTSP request to the real-time streaming protocol agent, and receive the RTSP response message returned by the real-time streaming protocol agent;

The real-time streaming protocol agent is connected with the real-time streaming protocol client and the real-time streaming protocol server respectively, and is used to receive the first real-time streaming protocol RTSP request from multiple real-time streaming protocol clients; according to the RTSP request , distributing the client identifier and service identifier for the real-time streaming protocol client, and generating an association relationship table between the real-time streaming protocol client identifier and the service identifier; forwarding the RTSP request carrying the service identifier to the real-time streaming protocol server; and receive the RTSP response message of the server, the RTSP response message carries the service identifier, and uses the service identifier as an index to obtain all the corresponding service identifiers by searching the association table The client identifier is used to forward the RTSP response message to the real-time streaming protocol client corresponding to the client identifier.

The real-time streaming protocol server is connected to the real-time streaming protocol agent, and is used to receive the first RTSP request sent by the real-time streaming protocol agent, and establish an different sessions, and return the RTSP response message to the real-time streaming protocol agent, wherein the RTSP response message carries the service identifier.

Embodiments of the present invention provide a method, device and system for forwarding data by a real-time streaming protocol agent, by receiving the first real-time streaming protocol RTSP request from multiple real-time streaming protocol clients; according to the RTSP request, the real-time streaming protocol The client allocates a client ID and a service ID, and generates an association table between the client ID and the service ID; forwards the RTSP request carrying the service ID to a real-time streaming protocol server; receives the first request from the real-time streaming protocol server An RTSP response message, carrying the service identifier in the first RTSP response message, and using the service identifier as an index, obtaining the client identifier by searching the association table, and forwarding the first RTSP response message to The real-time streaming protocol client corresponding to the client ID solves the problem that the RTSP Proxy accesses multiple RTSP protocol clients, and the RTSP Proxy cannot send the response message returned by the RTSP Server to the corresponding requesting RTSP Client, resulting in the client The problem of not being able to receive the response message has improved the function of RTSP Proxy and simplified the processing flow of RTSP Proxy.

Description of drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the following will briefly introduce the drawings that need to be used in the description of the embodiments or the prior art. Obviously, the accompanying drawings in the following description are only These are some embodiments of the present invention. For those skilled in the art, other drawings can also be obtained according to these drawings without any creative effort.

Fig. 1 is a kind of real-time streaming protocol proxy architecture diagram in the prior art of the present invention;

Fig. 2 is a flow chart of a method for forwarding data by a real-time streaming protocol agent in an embodiment of the present invention;

FIG. 3 is a flow chart of a specific implementation of forwarding data by a real-time streaming protocol proxy in an embodiment of the present invention;

Fig. 4 is a kind of session correlation table in the embodiment of the present invention;

Fig. 5 is another kind of session correlation table in the embodiment of the present invention;

FIG. 6 is a flow chart of a specific implementation of another real-time streaming protocol agent forwarding data in an embodiment of the present invention;

FIG. 7 is a transaction association table in an embodiment of the present invention;

Fig. 8 is a device structure diagram of a real-time streaming protocol proxy forwarding data in an embodiment of the present invention;

FIG. 9 is a system structure diagram of a real-time streaming protocol proxy forwarding data in an embodiment of the present invention.

Detailed ways

The following will clearly and completely describe the technical solutions in the embodiments of the present invention with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are some of the embodiments of the present invention, but not all of them. Based on the embodiments of the present invention, all other embodiments obtained by persons of ordinary skill in the art without making creative efforts belong to the protection scope of the present invention.

As shown in Figure 2, it is a flow chart of a method for forwarding data by a real-time streaming protocol proxy RTSP Proxy in an embodiment of the present invention, including the following steps:

Step S202, receiving a first real-time streaming protocol RTSP request from multiple real-time streaming protocol clients RTSP Client.

Specifically: RTSP Proxy receives different RTSP requests sent by multiple RTSP Clients.

Step S204, according to the real-time streaming protocol RTSP request, assign client identifiers and service identifiers to the multiple RTSP clients respectively, and generate an association table of the real-time streaming protocol client identifiers and service identifiers, wherein the client The terminal identifier includes: the transaction identifier of the client, or the session identifier of the client.

When the client identifier is the transaction identifier of the client, the assigning the client identifier and the service identifier to the RTSPClient, and generating the association table of the real-time streaming protocol client identifier and the service identifier specifically includes :

The RTSP Proxy assigns the client transaction identifier and service identifier to the RTSP Client, and generates an association table of the client transaction identifier and service identifier.

When the Client ID is the session identifier of the client, the distribution of the client identifier and the service identifier for the RTSPClient, and generating the association table of the real-time streaming protocol client identifier and the service identifier specifically includes:

RTSP Proxy distributes the session identifier and service identifier of the client for the RTSP Client;

Generating an association table of the client session ID, the service ID, and the server session ID assigned by the server to the client, wherein the server session ID is obtained by receiving an RTSP response message from the Server.

Wherein, when the RTSP Server server side is processing the RTSP request of the session, it simultaneously stores the association relationship table about the service identifier and the server session identifier assigned by the RTSP Server to the client, so that the next time the session is processed It can be used at any time, of course, the association relationship table can not be stored on the server side, and the session can be further processed through the service identifier and server session identifier carried in the RTSP request message.

Step S206, forwarding the RTSP request carrying the service identifier to the RTSP Server.

Step S208, receiving the first RTSP response message of the RTSP Server, the first RTSP response message carries the service identifier, and uses the service identifier as an index to obtain the corresponding client by searching the association table A session identifier, forwarding the first RTSP response message to the RTSP Client corresponding to the client session identifier.

When the client identifier is the session identifier of the client, the method further includes:

RTSP Proxy receives the second real-time streaming protocol RTSP request from the RTSP Client, and the second real-time streaming protocol RTSP request carries the client session identifier;

Obtaining the server session ID and service ID corresponding to the client by searching the association table with the client session ID as an index;

Carry the server session identifier and the service identifier in the second RTSP request, and forward them to the RTSP Server corresponding to the server session identifier, so that the RTSP Server performs session processing according to the server session identifier;

Receiving the second RTSP response message returned by the RTSP Server, the RTSP response message carries the service identifier, and uses the service identifier as an index to forward the RTSP response message to The RTSPClient corresponding to the client ID.

Wherein the first RTSP request message and the second RTSP request message can be: query DESCRIBE, obtain parameter GET_PARAMETER, option OPTIONS, pause PAUSE, play PLAY, redirect REDIRECT, build session SETUP, set parameter SET_PARAMETER, end session TEARDOWN Any one or several kinds of messages, and when the first RTSP request message is a session, the second RTSP request message can be the second or third time to request RTSP Rroxy in turn, and is not limited to the number of times.

The process described in the above steps can be applied to a session interaction process and a transaction interaction process, for example, a typical playback and end session interaction process, which will be described in detail in the following embodiments.

The embodiment of the present invention receives the first real-time streaming protocol RTSP request from a plurality of real-time streaming protocol clients RTSP Client; according to the RTSP request, generates the association table of the real-time streaming protocol client identifier and the service identifier; will carry The RTSP request of the service identifier is forwarded to the real-time streaming protocol server RTSP Server; by receiving the RTSP response message of the RTSP Server, and using the service identifier carried in the RTSP response message as an index, the association table is searched, and the The RTSP response message is forwarded to the RTSPClient corresponding to the client session identifier, which solves the problem that the RTSP Proxy accesses multiple RTSP protocol clients, and the RTSP Proxy cannot send the response message returned by the RTSP Server to the corresponding requesting end RTSP Client, which leads to the problem that the client cannot receive the response message, improves the function of RTSP Proxy, and simplifies the processing flow of RTSP Proxy.

As shown in Figure 3, it is a flow chart of a specific implementation of RTSP Proxy forwarding data for a real-time streaming protocol agent in the embodiment of the present invention, including the following steps:

The following embodiments describe in detail that when the real-time streaming protocol client RTSP Client sends the first real-time streaming protocol RTSP request message as a session request message, and the real-time streaming protocol client identifier Client ID is the session identifier Client Session ID of the client Circumstances, but not only limited to the application scenario of the session, but also can be applied to other request messages.

Step S300, the real-time streaming protocol client RTSP Client sends the real-time streaming protocol RTSP request to the real-time streaming protocol proxy RTSP Proxy.

Wherein, there are multiple RTSP Clients connected to the RTSP Proxy, and the RTSP request refers to the request message that the RTSP Client sends to the RTSP Proxy for the first time, and the request message can be a session request message or other request messages .

Step S302, RTSP Proxy receives the first RTSP request sent by multiple RTSP Clients, distributes the client session identifier and service identifier for the RTSP Client, and generates the real-time streaming protocol client session identifier, service identifier and server session An association relationship table of identifiers, wherein the server session identifier is acquired from the returned first RTSP response message.

Specifically, the association relationship table of the client session ID, the service ID and the server session ID is shown in FIG. 4 .

Fig. 4 is a kind of session correlation table in the embodiment of the present invention, includes in the table: client session identification, is the client session identification that RTSP Proxy distributes for described RTSP Client, sends for each RTSP Client in a plurality of RTSP Clients For different RTSP requests, RTSP Proxy uses the client session ID to distinguish which RTSP Client sent the RTSP request; the server session ID is assigned by the RTSP Server to the RTSP Client, specifically through the response message returned by the RTSP Server The returned one is used by the RTSP Server to distinguish the RTSPClient; the service identifier is used by the RTSP Proxy to distinguish the business data area corresponding to the response message returned by the RTSP Server, and is also used by the RTSP Server to distinguish different session requests from the same RTSP Proxy . RTSP Proxy assigns a service identifier to a session, and the service identifier remains unchanged during a session interaction. For example: RTSP Proxy generates the client's session ID as "1", which can be expressed as: client's session ID -1; business ID is "X", then it is expressed as: business ID -x; according to the server-side session returned by the RTSP response message If the identifier is "A", it means: session identifier-A on the server side.

Wherein, the session association relationship table may also include: a session information Session-Info option, which is used to record information such as the session information of the Client, the session information of the Server, the address of the Client or message parameters in the option, which One point needs to be described in the current conversation, and will not be described in detail here.

In step S304, the RTSP Proxy forwards the first RTSP request carrying the service identifier to the RTSP Server.

Specifically: by extending the RTSP request message, carrying the ServiceID in the message, the message is sent to the corresponding RTSP Server for processing, wherein the RTSP Server can be multiple, but the RTSP request is specifically received as RTSP Proxy decides to select a specific RTSP Server among multiple RTSP Servers for processing according to the content of the request.

Step S306, the RTSP Server receives the RTSP request, and according to the request, establishes different sessions for request messages from different service identifiers of the same Proxy.

In step S308, the RTSP Server assigns a server session ID to the RTSP Client, and returns a first RTSP response request to the RTSP Proxy, and the RTSP response request carries the server session ID and service ID.

Step S310, the RTSP Server stores the association relationship table between the server session identifier and the service identifier assigned to the RTSP Client.

The specific relationship table between the server session identifier and the service identifier is shown in FIG. 5 .

Fig. 5 is another kind of session correlation table in the embodiment of the present invention, is stored in RTSP Server side, and described correlation table comprises: server session identification and service identification; This server session identification, is used for RTSP Server to client already A session is established, so that the next time the RTSP Client requests again, the session will continue to be processed to avoid repeated session establishment; the service identifier is used by the RTSP Proxy to distinguish the service data area corresponding to the response message returned by the RTSP Server, and also used The RTSP Server distinguishes different session requests from the same RTSP Proxy. RTSPProxy assigns a service identifier to a session, and the service identifier remains unchanged during a session interaction. For example: RTSP Proxy generates the client's session ID as "1", which can be expressed as: client's session ID -1; business ID is "X", then it is expressed as: business ID -x; according to the server-side session returned by the RTSP response message If the identifier is "A", it means: session identifier-A on the server side.

For details, please refer to the detailed description of the following examples.

It should be noted that this step 310 is an optional step, that is, the RTSP Server side may store the association table of the server session identifier and the service identifier allocated for the RTSP Client, or may not store it. If the RTSP Server does not store the association table, it can also perform session processing according to the server session identifier carried in the RTSP request.

Wherein, step S308 and step S310 have no sequence limitation.

Step S312, the RTSP Proxy receives the RTSP response message returned by the RTSP Server, and writes the server session identifier carried in the RTSP response message into the server session identifier option in the association table

Step S313, RTSP Proxy uses the service identification carried in the RTSP response message as an index, finds the client identification corresponding to the service identification through the association relationship table stored in the RTSP Proxy, and forwards the RTSP response message to the The RTSP Client corresponding to the client identifier.

Step S314, the RTSP Client sends a second RTSP request message to the RTSP Proxy, and the second request carries the client session identifier.

Step S316, the RTSP Proxy receives the second RTSP request message, searches the session association table stored by itself according to the client session identifier carried in the request message, and obtains the server session identifier and the server session identifier corresponding to the client. Business identity.

Wherein, the association relationship table stored by itself is an association relationship table of the client session identifier, the service identifier, and the server session identifier allocated by the server to the client, as shown in FIG. 4 .

Step S318, RTSP Proxy carries the server session identifier and service identifier in the RTSP request, and forwards it to the RTSP Server corresponding to the server session identifier.

Step S320, the RTSP Server receives the second request message, and processes the session according to the server session identifier carried in the request message.

Step S322, returning a second RTSP response message to the RTSP Proxy, where the second RTSP response message carries the service identifier.

Among them, the RTSP Server also determines whether multiple services need to be generated according to the value of the service identifier. For example, when the Server receives a service request from the same Proxy, if there are different service identifiers, the Server will treat it as a different service request and generate multiple services. data area.

In step S324, the RTSP Proxy receives the second RTSP response message, uses the service identifier carried in the response message as an index, and obtains the client session identifier by searching the association table.

Step S326, forwarding the second RTSP response message to the RTSP Client corresponding to the client session identifier, so that the RTSP Client receives the RTSP response message.

Wherein, according to the service identifier, the corresponding information of the session can be updated, and the updated session information can be written into the session information Session-Info option in the association table stored by itself.

The above interaction process is also applicable to the application scenario where an RTSP Proxy needs to be connected to multiple Servers. It only needs to carry the service identification field in the signaling interaction message between the RTSP Proxy and multiple RTSP Servers.

A typical play and end session interaction process will be described in detail below. The RTSP request includes: set up session Setup, play Play, pause Pause, and end session Teardown. For example: The RTSP request sent by the RTSP Client to the RTSP Proxy is a SETUP message, the message example is as follows:

C->P:SETUP rtsp://foo/twister/video RTSO/1.0

CSeq: 1

Transport: RTP/AVP; unicast; client_port=8002-8003

RTSP Proxy generates client session ID Client Session ID: client session ID Client Session ID-1 and service ID ServiceID: service ID ServiceID-x, and forwards the message to RTSP Server, the message carries the service ID ServiceID-x field or option , the message example is as follows (ServiceID is used to represent the service identifier below, but it does not mean that the only service ID is used to represent the service identifier, and this is only used as an example for illustration. The service identifier is used by the RTSP Proxy to distinguish the corresponding response message returned by the RTSP Server The business data area is also used by the RTSP Server to distinguish different session requests from the same RTSP Proxy. RTSPProxy assigns a business identifier to a session. During a session interaction, any service identifier that remains unchanged can represent the business logo):

P->S: SETUP rtsp://foo/twister/video RTSP/1.0

CSeq: 1

Transport: RTP/AVP; unicast; client_port=10000-10001

Service-ID: 1234

The server session identifier ServerSession ID assigned by the RTSP Server to the client: Server Session ID-A, and record the service identifier ServiceID-x received, after processing, the response message returned to the RTSP Proxy needs to carry ServiceID-x, Examples are as follows:

S->P: RTSP/1.0 200 OK

CSeq: 1

Transport: RTP/AVP; unicast; client_port=10000-10001;

Server_port＝12004-12005

Session: 22345679

Service-ID: 1234

RTSP Proxy searches the association table stored by itself according to the service ID ServiceID-x, finds the corresponding Client Session ID-1, and records the session ID generated by the RTSP Server: Server Session ID-A, according to the session ID Server Session ID- A. Forward the response message to the Client, for example as follows:

P->C: RTSP/1.0 200 OK

CSeq: 1

Transport: RTP/AVP; unicast; client_port=8002-8003;

server_port＝9004-9005

  Session: 12345678

When RTSP Client sends PLAY message to Proxy, the message example is as follows:

C->P: PLAY rtsp://foo/twister RTSP/1.0

CSeq: 2

Range: npt＝0-

  Session: 12345678

RTSP Proxy finds the corresponding business identifier: ServiceID-x and server session identifier Server Session ID-A according to the client's session identifier: Client Session ID-1, and carries the server session identifier Server SessionID-A in the Play message forwarded to the RTSP Server And business identifier: ServiceID-x field, the message example is as follows:

P->S: PLAY rtsp://foo/twister RTSP/1.0

CSeq: 2

Range: npt＝0-

  Session: 22345679

  Service-ID: 1234

The RTSP Server finds the corresponding data area according to the session identifier Server Session ID-A, and the response message returned to the RTSP Proxy after processing needs to carry the service identifier: ServiceID-x field, for example as follows:

S->P: RTSP/1.0 200 OK

CSeq: 2

Session: 22345679

RTP-Info:url=rtsp://foo/twister/video;

Seq=10092; rtptime=1120089

Service-ID: 1234

RTSP Proxy finds the corresponding client's session ID: Client Session ID-1 according to the service ID: ServiceID-x, and forwards the response message to the RTSP Client according to the client's session ID: Client Session ID-1, as follows:

P->C: RTSP/1.0 200 OK

CSeq: 2

  Session: 12345678

RTP-Info:url=rtsp://foo/twister/video;

  seq = 40023; rtptime = 3450012

When the RTSP Client sends a PAUSE message to the RTSP Proxy and the process of teardown is the same as the process described above, it will not be repeated here.

The embodiment of the present invention provides a specific implementation method for RTSP Proxy forwarding data of a real-time streaming protocol, by receiving real-time streaming protocol RTSP requests from multiple real-time streaming protocol client RTSP Clients; generating the real-time streaming according to the RTSP requests The protocol client identifies the ClientSession ID and the business identification Service ID association table; the RTSP request carrying the Service ID is forwarded to the real-time streaming protocol server RTSP Server; by receiving the RTSP response message of the RTSP Server, and using the RTSP response message The Service ID carried is an index, searches the association table, forwards the RTSP response message to the RTSP Client corresponding to the ClientSessionID, solves the problem of RTSP Proxy accessing multiple RTSP protocol clients, and RTSP Proxy The response message returned by the RTSP Server cannot be sent to the corresponding requesting RTSP Client, which leads to the problem that the client cannot receive the response message, improves the function of RTSP Proxy, and simplifies the processing flow of RTSP Proxy.

Fig. 6 is another kind of real-time streaming protocol agent RTSP Proxy concrete implementation manner flow chart of forwarding data in the embodiment of the present invention, the specific implementation manner of another kind of real-time streaming protocol proxy RTSP Proxy forwarding data in the embodiment of the present invention below in conjunction with Fig. 6 The flow chart is described in detail.

The following describes the application scenarios in which the real-time streaming protocol proxy RTSP Proxy can not only receive RTSP messages about sessions from the real-time streaming protocol client, but also receive RTSP messages about transactions, such as options OPTIONS, query DESCRIBE, and notify ANNOUNCE. The message flow is only Completed by a pair of request and response messages, such messages are called transactional messages. Proxies only need to create transactions for such messages. The relationship table about the transaction contains the client transaction ID and the business ID, and the interaction message with the real-time streaming protocol server RTSP Server carries the business ID, receives the response message from the RTSP Server, locates the association table according to the business ID, and sends the response message Forwarded to the client, the entire transaction is over, as follows:

Step S600, the real-time streaming protocol client RTSP Client sends the real-time streaming protocol RTSP request to the real-time streaming protocol proxy RTSP Proxy.

Wherein, there are multiple RTSP Clients connected with the RTSP Proxy, and the request message may be a transaction request message.

Step S602, the RTSP Proxy receives the RTSP requests sent by a plurality of RTSP Clients, distributes the client's transaction identifier and service identifier for the RTSP Client, and generates an association relationship table between the real-time streaming protocol client identifier and the service identifier .

Specifically, when the client identifier is a client transaction identifier, a transaction association table of the client transaction identifier and service identifier is generated as shown in FIG. 7 .

Fig. 7 is a kind of transaction correlation table in the embodiment of the present invention, is stored in RTSP Proxy, includes in the table: client transaction identification, is the client transaction identification that RTSP Proxy distributes for described RTSP Client, for a plurality of RTSP Clients For different RTSP requests sent by each RTSP Client in RTSP Proxy, RTSP Proxy uses the client transaction ID to distinguish which RTSP Client sent the RTSP request; the business ID is used for RTSP Proxy to distinguish the business data area corresponding to the response message returned by the RTSP Server , also used by RTSP Server to distinguish different session requests from the same RTSP Proxy. RTSP Proxy assigns a service identifier to a session, and the service identifier remains unchanged during a session interaction. For example: RTSP Proxy generates a client transaction ID of "1", which can be expressed as: client transaction ID -1; business ID is "Y", then it is expressed as: business ID -Y, detailed in the following specific examples instruction of.

In step S604, the RTSP Proxy forwards the RTSP request carrying the Service ID to the RTSP Server.

Specifically: the RTSP request message described by RTSP Proxy carries the service identifier through the extended field, and sends the message to the corresponding RTSP Server for processing, wherein there are multiple RTSP Servers, but specifically receives the RTSP request According to the content of the request, the RTSP Proxy decides to select a specific RTSP Server among multiple RTSP Servers for processing.

In step S606, the RTSP Server receives the RTSP request, and according to the request, the RTSP Server performs message processing for request messages from different Service IDs of the same Proxy.

Step S607, returning an RTSP response message to the responding RTSP Proxy, the response message carrying the service identifier.

Step S608, the RTSP Proxy receives the RTSP response message returned by the RTSP Server, and according to the service identification carried in the RTSP response message as an index, obtains the client transaction identification by searching the transaction association table stored in the RTSP Proxy.

Step S610, the RTSP Proxy forwards the RTSP response message to the RTSP Client corresponding to the client transaction identifier, so that the RTSP Client receives the RTSP response message returned by the RTSP Proxy.

The above interaction process is also applicable to the application scenario where an RTSP Proxy needs to be connected to multiple Servers, and only needs to carry the service identification field in the signaling interaction message between the RTSP Proxy and multiple RTSP Servers.

The following is a specific description combined with a typical transaction interaction process, taking the RTSP request message as the option OPTIONS message as an example:

The RTSP Client sends an Options message to the RTSP Proxy. Examples of messages are as follows:

C->P: OPTIONS * RTSP/1.0

CSeq: 0

  Require: implicit-play

  Proxy-Require: gzipped-messages

RTSP Proxy first generates the client transaction ID: Client Transaction ID: ClientTransaction ID-1 and the associated business ID ServiceID: ServiceID-x, RTSP Proxy forwards the options message to the RTSP Server, and adds the ServiceID field to the message. The message example is as follows (here all The above-mentioned client transaction ID is represented by Client Transaction ID, and the business ID is represented by ServiceID, but it does not mean that the only service ID is used to represent the business ID, and this is only used as an example for illustration. The business ID is used for RTSP Proxy to distinguish the returned by RTSPServer The business data area corresponding to the response message is also used by the RTSP Server to distinguish different session requests from the same RTSP Proxy. The RTSP Proxy assigns a business identifier to a session, and the service identifier remains unchanged during a session interaction. can represent the business ID):

P->S: OPTIONS * RTSP/1.0

CSeq: 0

  Require: implicit-play

  Proxy-Require: gzipped-messages

  Service-ID: 1235

After processing by RTSP Server, the response message returned to RTSP Proxy needs to carry the business identifier from RTSP Proxy: ServiceID-x, for example as follows:

S->P: RTSP/1.0 200 OK

CSeq: 0

  Public: DESCRIBE, SETUP, TEARDOWN, PLAY, PAUSE

  Service-ID: 1235

RTSP Proxy searches the transaction association table according to the business identifier ServiceID-x, finds the corresponding transaction identifier Client Transaction ID-1, and forwards the response message to the corresponding RTSP Client according to the transaction identifier. The message example is as follows:

P->C: RTSP/1.0 200 OK

CSeq: 0

  Public: DESCRIBE, SETUP, TEARDOWN, PLAY, PAUSE

Similarly, when the RTSP message is other transaction messages such as DESCRIBE messages, it can also be processed through the above-mentioned flow, and details will not be repeated here.

The embodiment of the present invention provides another specific implementation method for RTSP Proxy forwarding data of a real-time streaming protocol, by receiving real-time streaming protocol RTSP requests from multiple real-time streaming protocol client RTSP Clients; according to the RTSP requests, generating the real-time The association table of the transaction identification Client Transaction ID of the streaming protocol client and the service identification Service ID; the RTSP request carrying the Service ID is forwarded to the real-time streaming protocol server RTSP Server; by receiving the RTSP response message of the RTSP Server, and The Service ID carried in the RTSP response message is an index, the association table is searched, and the RTSP response message is forwarded to the RTSP Client corresponding to the Client Transaction ID, which solves the problem of RTSPProxy accessing multiple RTSP protocols On the client side, RTSP Proxy cannot send the response message returned by RTSP Server to the corresponding requesting RTSP Client, which leads to the problem that the client cannot receive the response message, improves the function of RTSP Proxy, and simplifies the processing flow of RTSP Proxy.

As shown in Figure 8, Figure 8 is a device structure diagram of a real-time streaming protocol agent RTSP Proxy forwarding data in an embodiment of the present invention, including:

The first receiving unit 800 is configured to receive a first real-time streaming protocol RTSP request from multiple real-time streaming protocol clients;

An association relationship table generation unit 802, configured to assign the client identifier and service identifier to the real-time streaming protocol client according to the RTSP request, and generate an association relationship table between the client identifier and the service identifier;

The first sending unit 804 is configured to forward the RTSP request carrying the service identifier to a real-time streaming protocol server;

The second receiving unit 806 is configured to receive a first RTSP response message from the real-time streaming protocol server, where the RTSP response message carries the service identifier;

The second sending unit 808 is configured to use the service identifier carried in the RTSP response message received by the second receiving unit as an index, obtain the client identifier by searching the association table, and forward the RTSP response message to the The real-time streaming protocol client corresponding to the above client identifier.

Wherein, when the client identifier is the client transaction identifier, the association relationship table generation unit 802 is specifically configured to assign a client transaction identifier and a service identifier to the real-time streaming protocol client, and generate the client transaction identifier. An association relationship table between the terminal transaction identifier and the service identifier.

When the client identifier is the client's session identifier, the association table generating unit is specifically configured to assign the client's session identifier and service identifier to the real-time streaming protocol client; generate the client session An association table of identifiers, service identifiers, and server session identifiers allocated by the real-time streaming protocol server to the real-time streaming protocol client, wherein the server session identifier is obtained by receiving an RTSP response message from the real-time streaming protocol server.

And, when the client identifier is the session identifier of the client, the device further includes:

The first receiving unit 800 is further configured to receive a second real-time streaming protocol RTSP request from the real-time streaming protocol client, the request carrying the client session identifier;

The acquiring unit 810 is configured to use the client session ID of the first receiving unit as an index to obtain the server session ID and service ID corresponding to the client by searching the association table;

The first sending unit 804 is further configured to carry the server session identifier and service identifier in the second RTSP request, and forward them to the real-time streaming protocol server corresponding to the server session identifier, so that the real-time stream The protocol server performs session processing according to the server session identifier;

The second receiving unit 806 is further configured to receive a second RTSP response message returned by the real-time streaming protocol server, where the second RTSP response message carries the service identifier;

The second sending unit 808 is further configured to take the transaction identifier received by the second receiving unit as an index, obtain the client identifier corresponding to the service identifier by searching the association relationship table, and send the second The second RTSP response message is forwarded to the real-time streaming protocol client corresponding to the client identifier.

It should be noted that each module in the real-time streaming protocol proxy RTSP Proxy device for forwarding data can be built into a real-time streaming protocol proxy RTSP Proxy, or it can be an independent device. The interaction process of each part of the device can be found in The description of the embodiments shown in FIG. 3 and FIG. 6 will not be repeated here.

The embodiment of the present invention provides a real-time streaming protocol agent RTSP Proxy data forwarding device, through the mutual interaction of each module of the device, the RTSP response message returned by the RTSP server is passed through the association between the real-time streaming protocol client identifier and the service identifier The table is forwarded to the RTSP Client corresponding to the client ID, which solves the problem that the real-time streaming protocol agent cannot distinguish the real-time streaming protocol client that the response message returned by the server belongs to, thus causing the client to fail to receive the response message , improve the function of RTSP Proxy, and simplify the processing flow of real-time streaming protocol proxy.

As shown in Figure 9, Figure 9 is a system structure diagram of a real-time streaming protocol agent RTSP Proxy forwarding data in an embodiment of the present invention, including:

Multiple real-time streaming protocol clients RTSP Client902, real-time streaming protocol agent RTSPProxy904 and real-time streaming protocol server RTSP Server906;

The RTSP Client902 is connected with the agent of the real-time streaming protocol, and is used to send the first real-time streaming protocol RTSP request to the agent of the real-time streaming protocol, and receive the RTSP response message returned by the agent of the real-time streaming protocol;

The real-time streaming protocol agent RTSP Proxy904 is connected with the real-time streaming protocol client and the real-time streaming protocol server respectively, and is used to receive the first real-time streaming protocol RTSP request from multiple real-time streaming protocol clients; according to the RTSP request, assign the client identification and service mark for the real-time streaming protocol client, and generate the association table of the real-time streaming protocol client identification and service identification; forward the RTSP request carrying the service identification to Real-time streaming protocol server; and receive the RTSP response message of the server, the RTSP response message carries the service identifier, and uses the service identifier as an index to obtain the corresponding service identifier by searching the association table The client identifier of the client, forwarding the RTSP response message to the real-time streaming protocol client corresponding to the client identifier;

The real-time streaming protocol server RTSP Server906 is connected with the real-time streaming protocol proxy, and is used to receive the first RTSP request sent by the real-time streaming protocol proxy, and according to different service identifiers, be the client of the real-time streaming protocol The end establishes different sessions, and returns the RTSP response message to the real-time streaming protocol agent, wherein the RTSP response message carries the service identifier.

When the client identifier is a client session identifier,

The real-time streaming protocol agent is specifically configured to assign the client identifier and service identifier to the real-time streaming protocol client according to the RTSP request, and generate an association table between the client identifier and the service identifier;

The real-time streaming protocol server is also used to obtain and store the association table of the server session identifier and the service identifier assigned by the server to the client, wherein the service identifier is obtained from the RTSP request message Obtain.

When the client identifier is the client session identifier,

The real-time streaming protocol client is further configured to send a second real-time streaming protocol RTSP request to the real-time streaming protocol agent, the request carries the client session identifier, and receives the second request returned by the real-time streaming protocol agent. 2 RTSP response;

The real-time streaming protocol agent is further configured to receive the second RTSP request, identify the client session as an index, and obtain the server session ID and the server session ID corresponding to the client session ID by searching the association table. A service identifier, carrying the server session identifier and the service identifier in the second RTSP request, forwarding to the real-time streaming protocol server corresponding to the server session identifier; and receiving the second RTSP returned by the real-time streaming protocol server Response message, the second RTSP response message carries the service identifier; using the service identifier as an index, obtains the client session identifier corresponding to the service identifier by searching the association table, and sends the RTSP response forwarding the message to the real-time streaming protocol client corresponding to the client session identifier;

The real-time streaming protocol server is further configured to receive the second RTSP request forwarded by the real-time streaming protocol proxy, process the session according to the server session identifier carried in the request, and return the second RTSP request A response message is sent to the real-time streaming protocol agent, and the second RTSP response message carries the service identifier.

When the client identifier is the client transaction identifier,

The real-time streaming protocol agent is specifically configured to assign a client transaction identifier and a service identifier to the real-time streaming protocol client according to the RTSP request, and generate an association table of the client transaction identifier and the service identifier.

The embodiment of the present invention provides a real-time streaming protocol agent RTSP Proxy forwarding data system, through the mutual interaction between RTSP Client, RTSP Proxy and RTSP Server in the system, the RTSP response message returned by the RTSP server is passed through the real-time streaming protocol The association table of the client ID and the service ID D is forwarded to the RTSP Client corresponding to the client ID, which solves the problem that the real-time streaming protocol agent cannot distinguish the real-time streaming protocol client to which the response message returned by the server belongs, resulting in The problem that the client cannot receive the response message improves the function of RTSPProxy and simplifies the processing flow of the real-time streaming protocol proxy.

Through the description of the above embodiments, those skilled in the art can clearly understand that the present invention can be implemented by means of software plus a necessary general-purpose hardware platform or by hardware. Based on this understanding, the technical solution of the present invention is essentially In other words, the part that contributes to the existing technology can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions to make a terminal device (which can be a mobile phone, a personal computer, or a server) , or a network device, etc.) execute the methods described in various embodiments of the present invention.

The above is only a preferred embodiment of the present invention, it should be pointed out that, for those of ordinary skill in the art, without departing from the principle of the present invention, some improvements and modifications can also be made, and these improvements and modifications can also be made. It should be regarded as the protection scope of the present invention.

Claims (12)

1. the method for real-time streaming protocol agency forwarding data is characterized in that, comprising:

Reception is from the first real-time streaming protocol RTSP request of a plurality of real-time streaming protocol clients;

According to described RTSP request,, and generate the incidence relation table of described client identification and service identification for described real-time streaming protocol client is distributed client identification and service identification;

The RTSP request of carrying described service identification is transmitted to the real-time streaming protocol server;

Receive a RTSP response message of described real-time streaming protocol server, carry described service identification in the described RTSP response message, and be index with described service identification, obtain client identification by searching described incidence relation table, a described RTSP response message is transmitted to the real-time streaming protocol client corresponding with described client identification.

2. method according to claim 1, it is characterized in that, when described client identification is client transaction when sign, describedly distribute described client identification and service identification, and the incidence relation table that generates described client identification and service identification comprises specifically for described real-time streaming protocol client:

For described real-time streaming protocol client is distributed client transaction sign and service identification, and generate the incidence relation table of described client transaction sign and described service identification.

3. method according to claim 1, it is characterized in that, when described client identification is described client-side session sign, describedly distribute described client identification and service identification, and the incidence relation table that generates described client identification and service identification comprises specifically for described real-time streaming protocol client:

For described real-time streaming protocol client is distributed described client-side session sign and service identification;

Generating described client session sign, service identification and described real-time streaming protocol server is the incidence relation table of the server session sign of described real-time streaming protocol client distribution, and wherein said server session sign is by receiving the RTSP response message acquisition of described real-time streaming protocol server.

4. method according to claim 3 is characterized in that, described method also comprises:

Reception is carried described client session sign from the second real-time streaming protocol RTSP request of described real-time streaming protocol client in the described request;

Be designated index with described client session, cross and search described incidence relation table, obtain described server session sign and the service identification corresponding with described client;

Described server session sign and service identification are carried in described the 2nd RTSP request, be transmitted to and the corresponding real-time streaming protocol server of described server session sign, make described real-time streaming protocol server carry out session and handle according to described server session sign;

Receive the 2nd RTSP response message that described real-time streaming protocol server returns, carry described service identification in described the 2nd RTSP response message, and be index with described service identification, obtain and described service identification clients corresponding sign by searching described incidence relation table, described the 2nd RTSP response message is transmitted to the described real-time streaming protocol client corresponding with described client identification.

5. the device of real-time streaming protocol agency forwarding data is characterized in that, comprising:

First receiving element is used to receive the first real-time streaming protocol RTSP request from a plurality of real-time streaming protocol clients;

The incidence relation table generates the unit, is used for for described real-time streaming protocol client is distributed described client identification and service identification, and generating the incidence relation table of described client identification and service identification according to described RTSP request;

First transmitting element, the RTSP request that is used for carrying described service identification is transmitted to the real-time streaming protocol server;

Second receiving element is used to receive a RTSP response message of described real-time streaming protocol server, carries described service identification in the described RTSP response message;

Second transmitting element, the service identification that is used for carrying with the RTSP response message that described second receiving element receives is an index, obtain client identification by searching described incidence relation table, described RTSP response message is transmitted to the real-time streaming protocol client corresponding with described client identification.

6. device according to claim 5, it is characterized in that, when institute's family end is designated described client transaction sign, described incidence relation table generates the unit and specifically is used to described real-time streaming protocol client to distribute client transaction sign and service identification, and generates the incidence relation table of described client transaction sign and described service identification.

7. device according to claim 5, it is characterized in that, when described client identification was described client-side session sign, described incidence relation table generated the unit and specifically is used to described real-time streaming protocol client to distribute described client-side session sign and service identification; Generating described client session sign, service identification and described real-time streaming protocol server is the incidence relation table of the server session sign of described real-time streaming protocol client distribution, and wherein said server session sign is by receiving the RTSP response message acquisition of described real-time streaming protocol server.

8. device according to claim 7 is characterized in that, when described client identification was described client-side session sign, described device also comprised:

Described first receiving element also is used to receive the second real-time streaming protocol RTSP request from described real-time streaming protocol client, carries described client session sign in the described request;

Acquiring unit is used for being designated index with the described client session of described first receiving element, crosses and searches described incidence relation table, obtains described server session sign and the service identification corresponding with described client;

Described first transmitting element, also be used for described server session sign and service identification are carried at described the 2nd RTSP request, be transmitted to and the corresponding real-time streaming protocol server of described server session sign, make described real-time streaming protocol server carry out session and handle according to described server session sign;

Described second receiving element also is used to receive the 2nd RTSP response message that described real-time streaming protocol server returns, and carries described service identification in described the 2nd RTSP response message;

Described second transmitting element, the described service identification that also is used for receiving with described second receiving element is an index, obtain and described service identification clients corresponding sign by searching described incidence relation table, described the 2nd RTSP response message is transmitted to the described real-time streaming protocol client corresponding with described client identification.

9. the system of real-time streaming protocol agency forwarding data is characterized in that, comprising: a plurality of real-time streaming protocol clients, real-time streaming protocol agency and real-time streaming protocol server;

Described real-time streaming protocol client is connected with described real-time streaming protocol agency, is used to send the first real-time streaming protocol RTSP and asks to described real-time streaming protocol agency, and receive the RTSP response message that described real-time streaming protocol agency returns;

Described real-time streaming protocol agency is connected with described real-time streaming protocol server with described real-time streaming protocol client respectively, is used to receive the first real-time streaming protocol RTSP request from a plurality of real-time streaming protocol clients; According to described RTSP request,, and generate the incidence relation table of described real-time streaming protocol client identification and service identification for described real-time streaming protocol client is distributed described client identification and professional mark; The RTSP request of carrying described service identification is transmitted to the real-time streaming protocol server; And receive the RTSP response message of described server, carry described service identification in the described RTSP response message, and be index with described service identification, by searching the described client identification that described incidence relation table is attained at described service identification correspondence, described RTSP response message is transmitted to the described real-time streaming protocol client corresponding with described client identification;

Described real-time streaming protocol server, be connected with described real-time streaming protocol agency, be used to receive the RTSP request that described real-time streaming protocol agency sends, according to different described service identifications, for described real-time streaming protocol client is set up different sessions, and return described RTSP response message and give described real-time streaming protocol agency, wherein, carry described service identification in the described RTSP response message.

10. system according to claim 9 is characterized in that, when described client identification is the client session sign,

Described real-time streaming protocol agency specifically is used for for described real-time streaming protocol client is distributed described client identification and service identification, and generating the incidence relation table of described client identification and service identification according to described RTSP request;

It is the described client described server session sign of distributing and the incidence relation table of described service identification that described real-time streaming protocol server also is used to obtain and store described server, and wherein, described service identification obtains from described RTSP request message.

11. system according to claim 9 is characterized in that, when described client identification is described client session sign,

Described real-time streaming protocol client also is used to send the second real-time streaming protocol RTSP and asks to carry described client session sign in the described request to described real-time streaming protocol agency, and receives the 2nd RTSP response that described real-time streaming protocol agency returns;

Described real-time streaming protocol agency, also be used to receive described the 2nd RTSP request, described client session is designated index, cross and search described incidence relation table, obtain described server session sign and the service identification corresponding with the client session sign, described server session sign and service identification are carried in described the 2nd RTSP request, are transmitted to and the corresponding real-time streaming protocol server of described server session sign; And receive the 2nd RTSP response message that described real-time streaming protocol server returns, carry described service identification in described the 2nd RTSP response message; With described service identification is index, obtains and described service identification clients corresponding session identification by searching described incidence relation table, and described RTSP response message is transmitted to and the corresponding described real-time streaming protocol client of described client session sign;

Described real-time streaming protocol server, also be used to receive described the 2nd RTSP request that described real-time streaming protocol agency transmits, according to the described server session sign of carrying in the described request described session is handled, and return the 2nd RTSP response message and give described real-time streaming protocol agency, carry described service identification in described the 2nd RTSP response message.

12. system according to claim 9 is characterized in that, when institute's client identification is described client transaction sign,

Described real-time streaming protocol agency specifically is used for according to described RTSP request, for described real-time streaming protocol client is distributed client transaction sign and service identification, and generates the incidence relation table of described client transaction sign and described service identification.

Images