WO2020221018A1 - 一种实时媒体流接入的方法、装置、通信设备和终端 - Google Patents

一种实时媒体流接入的方法、装置、通信设备和终端 Download PDF

Info

Publication number
WO2020221018A1
WO2020221018A1 PCT/CN2020/085179 CN2020085179W WO2020221018A1 WO 2020221018 A1 WO2020221018 A1 WO 2020221018A1 CN 2020085179 W CN2020085179 W CN 2020085179W WO 2020221018 A1 WO2020221018 A1 WO 2020221018A1
Authority
WO
WIPO (PCT)
Prior art keywords
media stream
real
communication device
time
time media
Prior art date
Application number
PCT/CN2020/085179
Other languages
English (en)
French (fr)
Inventor
章璐
曾德勇
缪永生
王梦晓
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to EP20798033.5A priority Critical patent/EP3962018A4/en
Publication of WO2020221018A1 publication Critical patent/WO2020221018A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/1016—IP multimedia subsystem [IMS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/60—Network streaming of media packets
    • H04L65/75—Media network packet handling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/1059—End-user terminal functionalities specially adapted for real-time communication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1069—Session establishment or de-establishment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/40—Support for services or applications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/60—Network streaming of media packets
    • H04L65/61—Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/60—Network streaming of media packets
    • H04L65/65—Network streaming protocols, e.g. real-time transport protocol [RTP] or real-time control protocol [RTCP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H04L67/141—Setup of application sessions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H04L67/146—Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/22—Parsing or analysis of headers

Definitions

  • This article relates to but not limited to a method, device, communication device, terminal and computer-readable storage medium for real-time media stream access.
  • IMS IP Multimedia Subsystem, Internet Protocol Multimedia Subsystem
  • 3GPP Third Generation Partnership Project
  • SIP Session Initial Protocol
  • Control functions are separated from bearing capacity, call and session separation, application and service separation, business and network separation, and mobile network and Internet business integration and other capabilities.
  • IMSALG Application Level Gateway
  • IMS Access Gateway IMS Access Gateway
  • P- CSCF Proxy-Call Session Control Function
  • SBC Session Border Controller, Session Border Controller
  • the real-time media stream sent or received by the terminal needs to be forwarded through the SBC. Since the messages sent by the terminal generally undergo NAT, the media messages that actually reach the SBC are different from the address and port carried in the SIP signaling of the terminal. In order to obtain the terminal NAT A common method for the converted IP address and port information is that the SBC usually learns through the first packet, and determines the corresponding relationship with the terminal by detecting the media message information arriving at a specific port of the SBC local end (see Table 1).
  • Terminal ID IP address of the terminal after NAT Port behind terminal NAT SBC local IP address SBC local port 138xxxx 221.135.8.9 17533 202.198.5.5 10000 139xxxx 211.178.9.10 24550 202.198.5.5 20000 ... ... ... ... ... ...
  • this method can identify the IP address and port number of the terminal after NAT, it has defects such as excessive port occupation.
  • the embodiments of the present application provide a method, device, communication device, terminal, and computer-readable storage medium for real-time media stream access.
  • the embodiment of the present application provides a method for real-time media stream access, including: a communication device determines a media stream identifier corresponding to the real-time media stream during the establishment of a real-time media stream session; the communication device allocates the real-time media stream Local port; wherein, each local port corresponds to one or more real-time media streams; the communication device forwards the media message carrying the real-time media stream after the establishment of the real-time media stream session is completed, the media message Carry the media stream identifier.
  • An embodiment of the present application also provides a method for real-time media stream access, including: the terminal determines the media stream identifier corresponding to the real-time media stream during the establishment of the real-time media stream session; after the terminal has established the real-time media stream session, Sending a media message carrying the real-time media stream, the media message carrying the media stream identifier.
  • An embodiment of the present application also provides an apparatus for real-time media stream access, including: a first determining module, configured to determine a media stream identifier corresponding to the real-time media stream during the establishment of a real-time media stream session; an allocation module, configured to: The real-time media stream is allocated a local port; wherein each local port corresponds to one or more real-time media streams; a forwarding module is used to forward the media report that carries the real-time media stream after the establishment of the real-time media stream session is completed The media message carries the media stream identifier.
  • An embodiment of the present application also provides a communication device, including: a memory, a processor, and a computer program stored in the memory and capable of running on the processor, and the processor implements the real-time media stream access when the program is executed Methods.
  • An embodiment of the present application also provides a device for real-time media stream access, including: a second determining module, configured to determine the media stream identifier corresponding to the real-time media stream during the establishment of a real-time media stream session; and a sending module, used to After the establishment of the real-time media stream session is completed, a media message carrying the real-time media stream is sent, and the media message carries the media stream identifier.
  • An embodiment of the present application also provides a terminal, including: a memory, a processor, and a computer program stored in the memory and capable of running on the processor.
  • the processor implements the real-time media stream access when the program is executed. method.
  • An embodiment of the present application also provides a computer-readable storage medium that stores computer-executable instructions, and the computer-executable instructions are used to execute the real-time media stream access method.
  • Figure 1 is a schematic diagram of the logical functions of an IMS application layer gateway and an IMS access gateway;
  • Figure 2 is a schematic diagram of the principle of a media stream access method in related technologies
  • FIG. 3 is a schematic diagram of the system architecture of an embodiment of the application.
  • FIG. 4 is a flowchart of a method for real-time media stream access according to an embodiment of the application (applied to a communication device);
  • Figure 5 is a flowchart of a method for real-time media stream access according to an embodiment of the application (applied to a terminal);
  • Fig. 6 is a flowchart of a method for real-time media stream access according to an embodiment of the application (applied to an IMS system);
  • Figure 7 is a schematic diagram of the network side allocating ports for each real-time media stream in an embodiment of the application
  • FIG. 8 is a schematic diagram of the network side allocating a unified port for each real-time media stream according to an embodiment of the application
  • FIG. 9 is a logic diagram of user-side media processing according to an embodiment of the application, describing the SBC processing logic for user-side media;
  • Figure 10 is a network-side media processing logic diagram of an embodiment of this application, describing the SBC processing logic for network-side media;
  • Figure 11 is a call flow chart in an IMS network of an application example of this application.
  • Figure 12 is a flow chart of SBC signaling negotiation in an IMS network for an application example of this application, where the calling party does not support media stream identification negotiation, and the called party supports media stream identification negotiation;
  • Figure 13 is a flow chart of SBC signaling negotiation in an IMS network for an application example of this application, where the calling party supports media stream identification negotiation, and the called party does not support media stream identification negotiation;
  • Figure 14 is a flow chart of SBC signaling negotiation in an IMS network for an application example of this application, where the calling party does not support media stream identification negotiation, and the calling side SBC directly rejects it;
  • Figure 15 is a flow chart of SBC signaling negotiation in an IMS network for an application example of this application, where the called party does not support media stream identification negotiation, and the called side SBC directly rejects it;
  • FIG. 16 is a schematic diagram of an apparatus for real-time media stream access according to an embodiment of the application (applied to a communication device);
  • FIG. 17 is a schematic diagram of a device for real-time media stream access according to an embodiment of the application (applied to a terminal);
  • FIG. 19 is a schematic diagram of the composition of a terminal according to an embodiment of the application.
  • this method needs to allocate a different port number on the SBC for each terminal, and establish a corresponding mapping relationship by detecting the message sent to the local port.
  • An IP address can only have 65535 ports at most, which means that an IP address supports 65535 media channels at most. If you need to increase the number of media channels, you need to increase the number of IP addresses. With the deployment of 5G networks, the number of terminal accesses has greatly increased, and existing models cannot meet the requirements.
  • a media stream identification negotiation and authentication link is added, and functions such as secure access to the media stream and anti-malicious attacks are provided.
  • the IMS network architecture of the embodiment of the application mainly includes the following network elements:
  • SBC100 is used to provide access services for terminals, which may include:
  • SBC-signaling processing module 101 used to assign a media stream identifier to a media stream, or record the media stream identifier when receiving the media stream identifier, and notify the media processing module 102 of the media stream identifier;
  • the SBC-media processing module 102 is used to verify the media stream identifier and establish a media message transmission path according to a preset strategy.
  • Call Session Control Function (CSCF) 110 used for service triggering and call routing, and there is no special requirement in the embodiment of this application.
  • Application server (AS) 115 used to provide communication services for users, and there is no special requirement in the embodiment of this application.
  • Terminal (UE) 120 Indicate supporting media authentication capability in the call request/response, record the media stream identifier, and carry the media stream identifier in the sent media message, which may include:
  • Signaling processing module 121 used to indicate support for media authentication capabilities in the call request/response in the call request, record the media stream identifier, and deliver the media stream identifier and the SBC IP address and port information to the media processing module 122;
  • the media processing module 122 is used to send a media message to the IP address and port of the SBC, and carry the media stream identifier in the media message.
  • the method for real-time media stream access in the embodiment of the present application, applied to a communication device includes:
  • Step 201 The communication device determines the media stream identifier corresponding to the real-time media stream during the establishment of the real-time media stream session.
  • the communication device may include an SBC, and the SBC may be an SBC on the calling side or an SBC on the called side.
  • the communication device includes the SBC on the calling side:
  • the media stream identifier is allocated by the communication device, and step 201 may include:
  • the communication device receives a real-time media stream service request sent by the calling terminal, where the service request carries the capability to support media stream authentication;
  • the communication device allocates a globally unique identifier as the media stream identifier corresponding to the real-time media stream.
  • Step 201 may include:
  • the communication device determines that the media stream identifier assigned by the calling terminal is not occupied, and then determines that the media stream identifier assigned by the calling terminal is the media stream identifier corresponding to the real-time media stream.
  • the calling terminal assigns a media stream identifier
  • the communication device determines whether the media stream identifier is available. When it is not available, the communication device assigns the media stream identifier.
  • Step 201 may include:
  • the communication device determines that the media stream identifier assigned by the calling terminal is occupied, it assigns a globally unique identifier as the media stream identifier corresponding to the real-time media stream;
  • the communication device notifies the calling terminal of the media stream identifier corresponding to the real-time media stream.
  • the communication device receives a real-time media stream service request sent by the calling terminal, and the service request does not carry a media stream authentication capability;
  • the communication device refuses the access of the calling terminal.
  • the communication device can directly refuse access, or can perform compatibility processing according to the existing process.
  • the communication device includes the SBC on the called side:
  • step 201 may include:
  • the communication device receives a real-time media stream service request sent by the SBC on the calling side, and obtains the media stream identifier from the service request.
  • the communication device receives a response to the service request sent by the called terminal, and the service request does not carry a media stream authentication capability
  • the communication device rejects the called terminal to access.
  • the communication device may directly refuse access, or may perform compatibility processing according to the existing process.
  • a response to the service request is received, it is determined that the response does not carry a media stream identifier, and the response corresponding to the real-time media stream is added to the response.
  • the media stream identifier forwards the response carrying the media stream identifier.
  • a response to the service request is received, it is determined that the response carries a media stream identifier, and the media stream identifier carried in the response is compared with the real-time media Whether the media stream identifiers corresponding to the streams are consistent, in the case of inconsistencies, replace the media stream identifier carried in the response with the media stream identifier corresponding to the real-time media stream, and forward the response.
  • Step 202 The communication device allocates a local port for the real-time media stream; wherein each local port corresponds to one or more real-time media streams.
  • multiple real-time media streams may share one local port.
  • the SBC establishes the correspondence between a local port and multiple real-time media streams, it determines the total bandwidth corresponding to all media streams so that the traffic of a UDP port does not exceed the traffic range of a physical port.
  • Step 203 After the establishment of the real-time media stream session is completed, the communication device forwards the media message that carries the real-time media stream, and the media message carries the media stream identifier.
  • multiple real-time media streams can share a local port, so as to improve media port utilization, increase system capacity, and meet the requirements of ultra-large-scale terminal access.
  • the method further includes:
  • the communication device judges the legality of the media stream by checking the media stream identifier in the media message.
  • judging the legality of the media stream may include:
  • the communication device determines that one or more media stream identifiers corresponding to the local port include the media stream identifiers in the media message, determine that the real-time media stream is legal;
  • the communication device determines that one or more media stream identifiers corresponding to the local port does not include the media stream identifier in the media message, it determines that the real-time media stream is illegal.
  • the forwarding route corresponding to the source address information in the media message is recorded, and when a media message carrying the real-time media stream is subsequently received, it is directly forwarded.
  • the source address information includes a combination of source IP address and port number (ie, IP+Port).
  • the media stream legality judgment is performed.
  • the SBC establishes the mapping relationship between the media stream identifier and the terminal source IP+Port, which can realize fast forwarding.
  • the network side of the SBC can allocate a separate IP+Port combination for each real-time media stream to realize the rapid forwarding of messages; the network side of the SBC can adopt the method of sharing one port for multiple real-time media streams, and the network side analyzes the media report The globally unique media stream identifier in the text determines the forwarding rule.
  • the source address information in the media message carrying the real-time media stream is recorded as a blacklist, and when a media message carrying the source address information is subsequently received , Directly discarded.
  • the legality of the media stream is judged to provide secure access to the media stream and prevent malicious attacks.
  • the method for real-time media stream access in the embodiment of the present application, applied to a terminal includes:
  • Step 301 The terminal determines the media stream identifier corresponding to the real-time media stream during the establishment of the real-time media stream session.
  • step 301 when the terminal serves as a calling terminal, the communication device allocates a media stream identifier, and step 301 includes:
  • the terminal sends a service request for a real-time media stream, and the service request carries a media stream authentication capability;
  • the terminal receives a response to the service request, and the response carries the media stream identifier.
  • Step 301 when the terminal serves as the calling terminal, the terminal allocates a media stream identifier and the communication device confirms it.
  • Step 301 includes:
  • the terminal receives the response to the service request, and determines the media stream identifier corresponding to the real-time media stream according to the media stream identifier carried in the response.
  • step 301 when the terminal is used as a called terminal, step 301 includes:
  • the terminal receives a service request for a real-time media stream, and obtains the media stream identifier from the service request.
  • Step 302 After the establishment of the real-time media stream session is completed, the terminal sends a media message that carries the real-time media stream, and the media message carries the media stream identifier.
  • the media message includes an RTP (Real-time Transport Protocol, Real-time Transport Protocol) message
  • the terminal carries the parameter of the media stream identifier in the synchronization source SSRC field of the RTP message.
  • the terminal extends the RTP message, and carries the media stream identifier in the extension header of the RTP message.
  • the real-time media stream access process of the embodiment of the present application may include the following steps:
  • Step 401 When the calling terminal initiates a service request, the service request carries a media stream authentication capability
  • Step 402 When receiving the service request from the calling terminal, the SBC on the calling side creates a globally unique identifier for each real-time media stream in this session, and inserts the unique identifier into the service request;
  • the SBC records the corresponding relationship between the terminal user ID and the real-time media stream ID at the local end, and specifies a local port for each real-time media stream, and multiple real-time media streams can share a local port.
  • the SBC when the SBC establishes a correspondence between a local port and multiple real-time media streams, it determines the total bandwidth corresponding to all media streams, so as to adapt to the fact that the traffic of one UDP port does not exceed the traffic range of one physical port;
  • Step 403 When sending a service request to the calling CSCF, the SBC on the calling side replaces the terminal media address and port in the original SIP request with the media address and port of the SBC on the calling side;
  • IP+Port When the IP address on the SBC network side is sufficient, use a separate IP+Port combination to correspond to the real-time media stream (refer to Table 2 and Figure 7); when the IP address on the SBC network side is not sufficient, multiple media streams can share a network Side IP+Port combination (refer to Table 3 and Figure 8).
  • the user plane port on the SBC side allows the media streams of multiple terminals to share the same user plane port of the SBC.
  • each media stream of each terminal is assigned a user plane port for mapping.
  • the user plane port on the SBC side allows the media streams of multiple terminals to share the user plane port of the same SBC.
  • each media stream of each terminal is assigned a shared user plane port for mapping.
  • Step 404 the calling CSCF forwards the service request to the called SBC according to the IMS basic call flow
  • Step 405 The SBC on the called side extracts the real-time media stream identifier, and assigns a local port to be associated with the real-time media stream identifier, and multiple real-time media streams can share a local port.
  • the SBC when the SBC establishes the correspondence between a local port and multiple real-time media streams, it considers the total bandwidth corresponding to all media streams, so as to adapt to the fact that the traffic of one UDP port does not exceed the traffic range of one physical port;
  • Step 406 The SBC on the called side forwards the service request to the called terminal;
  • Step 407 The called terminal parses the media information in the service request, and records the corresponding relationship between the media stream identifier and the IP+Port of the media stream;
  • Step 408 When the called terminal sends the response, it carries the media stream identifier in the service response;
  • Step 409 When receiving the response from the called terminal, the SBC on the called side inserts the real-time media stream identifier in the service response;
  • the SBC compares whether the content is consistent with the locally recorded content, and if it is inconsistent, replace it;
  • Step 410 The SBC on the called side routes the response to the SBC on the calling side according to the standard IMS call flow;
  • Step 411 The SBC on the calling side parses the information in the service response and determines whether the response carries a unified real-time media stream identifier. If it does not carry it, inserts the real-time media stream identifier corresponding to the local end in the request; if the service response already carries it If the real-time media stream uniform identification is used, compare whether it is consistent with the real-time media stream identification in the request. If not, replace it with the real-time media stream identification in the request; SBC will modify the address information of the real-time media stream in the response to the corresponding end IP+Port;
  • Step 412 After receiving the response forwarded by the SBC on the calling side, the calling terminal extracts the real-time media stream identifier and the IP+Port of the SBC;
  • both the calling terminal and the called terminal have established the corresponding relationship between the real-time media stream identifier and the IP+Port of the receiving end of the SBC user side (UNI).
  • Step 413 The calling or called terminal sends a real-time media stream to the IP+Port of the SBC, and carries the real-time media stream identifier in the real-time media stream;
  • Step 414 When the SBC receives the real-time media stream, it first checks whether the source IP+Port has a corresponding forwarding route, that is, according to the source IP+Port, it can go to the destination IP+Port that needs to be forwarded, and if it can be found, it will forward it directly; If it is not found, SBC checks and analyzes the real-time media stream identifier in the media message, and queries whether the real-time media stream identifier corresponding to the local port of the SBC contains the identifier.
  • the real-time media stream is legal, and the source IP of the terminal +Port is recorded in the forwarding route, and then the real-time media stream sent by the IP+Port can be directly forwarded, without the need to judge the real-time media stream identifier, which improves processing efficiency. If it is not included in the real-time media stream identifier list corresponding to the port, it means that the media stream is illegal and is directly discarded, as shown in Figure 9.
  • the IP+Port corresponding to the terminal can be recorded in the blacklist, and subsequent messages from this source can be directly discarded.
  • the SBC forwards the real-time media stream to the peer SBC.
  • the SBC receives the media stream sent by the network side, the SBC according to whether the local IP+Port has a unique forwarding relationship, if the local end allocates each real-time media stream If a separate port is used, the forwarding relationship can be determined, and the peer SBC forwards directly according to the corresponding routing relationship; if the IP+Port of the network side (NNI) receiving end corresponds to multiple real-time media streams, the only media in the real-time media stream is analyzed The flow identifier determines the destination port of the corresponding user side (UNI) for forwarding. If the forwarding route cannot be determined according to the media stream identifier in the media stream, the packet is directly discarded, as shown in Figure 10.
  • the embodiment of the application adds media stream identification negotiation and authentication links, provides secure media stream access, anti-malicious attacks and other functions, and can greatly improve the utilization rate of user-side IP+Port and reduce the demand for IP addresses.
  • step 502 the SBC1 generates a unique identifier of the media stream for each media stream, which is used to authenticate the media. SBC1 carries the media stream identifier when forwarding the service request to the next hop;
  • Step 503 The IMS routes the service request to the SBC2 where the called terminal is located, and the media stream identifier is included in the request.
  • the SBC2 records the media stream identifier, and carries the media stream identifier in the request forwarded to the terminal UE2. If the called terminal is required to support media authentication compulsorily, the request should include the header "Require:media-auth" that requires the terminal to support media authentication capabilities; if the called terminal is not required to compulsorily support media authentication, the request should include the local end The header "Supported:media-auth" that supports media authentication capabilities;
  • UE2 carries the media stream identifier in the returned 18x (180 or 183 temporary response) response, indicating that the local end accepts the media stream identifier corresponding to the media stream, and carries the capability flag "Supported: media- auth";
  • Step 506 SBC2 carries the media stream identifier in the forwarded 18x response
  • Step 507 The IMS carries the media stream identifier in the 18x response forwarded to SBC1;
  • Step 508 SBC1 carries the media stream identifier in the 18x response forwarded to the terminal;
  • Step 509 The calling terminal UE1 records the authentication identifier of each media in the 18x response;
  • Step 510 After the user answers, UE2 returns a 200 OK (response response) response to SBC2;
  • Step 511 SBC2 is forwarding the 200 OK response to the IMS
  • Step 512 the IMS is forwarding the 200 OK response to SBC1;
  • Step 513 SBC1 forwards the 200 OK response to the terminal UE1;
  • Step 514 The calling terminal UE1 sends an ACK (Acknowledgement Request) to SBC1, indicating that the session is established;
  • Step 515 SBC1 forwards the ACK request to IMS
  • Step 516 IMS forwards the ACK request to SBC2;
  • Step 517 SBC2 forwards the ACK request to UE2;
  • step 518 the RTP media streams sent by UE1 and UE2 carry the media stream identifier.
  • step 601 the terminal UE1 initiates a service request to SBC1, and the "media authentication" capability is not carried in the INVITE request, indicating that the local terminal does not support media authentication;
  • step 602 the SBC1 generates a unique identifier of the media stream for each media stream, which is used to authenticate the media. SBC1 carries the media stream identifier when forwarding the service request to the next hop;
  • Step 603 The IMS routes the service request to the SBC2 where the called terminal is located, and the media stream identifier is included in the request.
  • the SBC2 records the media stream identifier, and carries the media stream identifier in the request forwarded to the terminal UE2. If the called terminal is required to support media authentication compulsorily, the request should include the header "Require:media-auth" that requires the terminal to support media authentication capabilities; if the called terminal is not required to compulsorily support media authentication, the request should include the local end The header "Supported:media-auth" that supports media authentication capabilities; in this example, the called terminal is not required to force media authentication;
  • Step 605 UE2 carries the media stream identifier in the returned 18x response, indicating that the local end accepts the media stream identifier corresponding to the media stream, and carries the capability flag "Supported: media-auth" that supports media authentication;
  • Step 606 SBC2 carries the media stream identifier in the forwarded 18x response
  • Step 607 The IMS carries the media stream identifier in the 18x response forwarded to SBC1;
  • Step 608 SBC1 carries the media stream identifier in the 18x response forwarded to the terminal;
  • Step 609 The calling terminal UE1 ignores the media stream identifier in the 18x response, does not insert the media stream identifier in the media stream, and at the same time, conducts media negotiation in a media-free authentication mode;
  • Step 610 After the user answers, UE2 returns a 200 OK response to SBC2;
  • Step 611 SBC2 is forwarding the 200 OK response to the IMS
  • Step 612 the IMS is forwarding the 200 OK response to SBC1;
  • Step 613 SBC1 forwards the 200 OK response to the terminal UE1;
  • Step 614 the calling terminal UE1 sends an ACK to SBC1, indicating that the session is established;
  • Step 615 SBC1 forwards the ACK request to the IMS
  • Step 616 IMS forwards the ACK request to SBC2;
  • Step 617 SBC2 forwards the ACK request to UE2;
  • Step 618 the RTP media stream sent by UE1 does not carry the media stream identifier, and the RTP media stream sent by UE2 carries the media stream identifier.
  • step 701 the terminal UE1 initiates a service request to SBC1, and carries the "media authentication" capability in the INVITE request, indicating that the local end supports media authentication;
  • Step 702 SBC1 generates a unique identifier of the media stream for each media stream, which is used to authenticate the media. SBC1 carries the media stream identifier when forwarding the service request to the next hop;
  • Step 703 The IMS routes the service request to the SBC2 where the called terminal is located, and the media stream identifier is included in the request.
  • Step 704 The SBC2 records the media stream identifier, and carries the media stream identifier in the request forwarded to the terminal UE2. If the called terminal is required to support media authentication compulsorily, the request should include the header "Require:media-auth" that requires the terminal to support media authentication capabilities; if the called terminal is not required to compulsorily support media authentication, the request should include the local end The header "Supported:media-auth" that supports media authentication capabilities; in this example, the called terminal is not required to force media authentication;
  • step 705 the 18x response returned by UE2 does not carry the media stream identifier and the capability flag "Supported: media-auth" that supports media authentication, indicating that the local end does not support media authentication;
  • Step 706 SBC2 does not carry the media stream identifier in the forwarded 18x response
  • Step 707 the IMS does not carry the media stream identifier in the 18x response forwarded to the SBC1;
  • Step 708 SBC1 inserts the previously generated media stream identifier into the 18x response forwarded to the terminal;
  • Step 709 The calling terminal UE1 saves the media stream identifier, inserts the media stream identifier in the media stream, and at the same time, conducts media negotiation according to the media authentication mode;
  • Step 710 After the user answers, UE2 returns a 200 OK response to SBC2;
  • Step 711 SBC2 is forwarding the 200 OK response to the IMS
  • Step 712 the IMS is forwarding the 200 OK response to SBC1;
  • Step 713 SBC1 is forwarding the 200 OK response to the terminal UE1;
  • Step 714 the calling terminal UE1 sends an ACK to SBC1, indicating that the session is established;
  • Step 715 SBC1 forwards the ACK request to the IMS
  • Step 716 IMS forwards the ACK request to SBC2;
  • Step 717 SBC2 forwards the ACK request to UE2;
  • step 718 the RTP media stream sent by UE1 does not carry the media stream identifier, and the RTP media stream sent by UE2 does not carry the media stream identifier.
  • step 801 the terminal UE1 initiates a service request to the SBC1, and the "media authentication" capability is not carried in the INVITE request, indicating that the local terminal does not support media authentication;
  • Step 802 SBC1 determines that media authentication is required this time, but the calling terminal does not support it, and returns a 421 Extension Required failure response, which indicates that the terminal requires media authentication to be supported;
  • Step 803 The terminal UE1 sends an ACK to end this session.
  • Step 901 The terminal UE1 initiates a service request to SBC1, and carries the "media authentication" capability in the INVITE request, indicating that the local end supports media authentication;
  • step 902 the SBC1 generates a unique identifier of the media stream for each media stream, which is used to authenticate the media. SBC1 carries the media stream identifier when forwarding the service request to the next hop;
  • Step 903 the IMS routes the service request to the SBC2 where the called terminal is located, and the media stream identifier is included in the request.
  • step 904 the SBC2 records the media stream identifier, and carries the media stream identifier in the request forwarded to the terminal UE2.
  • the called terminal is required to support media authentication compulsorily, and the header "Require:media-auth" that requires the terminal to support media authentication capabilities is carried in the request;
  • step 905 UE2 finds that the local end does not support media authentication, and returns a 420Bad Extension failure response, which indicates that the media authentication capability "Supported: media-auth" is not supported;
  • Step 906 SBC2 sends the 420 response to the IMS in the forwarded 420 response;
  • Step 907 the IMS forwards the 420 response of SBC1;
  • Step 908 SBC1 is forwarding the response to the terminal 420;
  • Step 909 the calling terminal UE1 sends an ACK to SBC1, indicating that the session is over;
  • Step 910 SBC1 forwards the ACK request to the IMS
  • Step 911 IMS forwards the ACK request to SBC2;
  • Step 912 SBC2 forwards the ACK request to UE2.
  • an embodiment of the present application also provides a real-time media stream access device, which is applied to communication equipment, and includes:
  • the first determining module 1001 is configured to determine the media stream identifier corresponding to the real-time media stream during the establishment of the real-time media stream session;
  • the allocation module 1002 is configured to allocate local ports for the real-time media streams; wherein each local port corresponds to one or more real-time media streams;
  • the forwarding module 1003 is configured to forward a media message carrying the real-time media stream after the establishment of the real-time media stream session is completed, and the media message carries the media stream identifier.
  • an embodiment of the present application also provides a real-time media stream access device, which is applied to a terminal, and includes:
  • the second determining module 1101 is configured to determine the media stream identifier corresponding to the real-time media stream during the establishment of the real-time media stream session;
  • the sending module 1102 is configured to send a media message carrying the real-time media stream after the establishment of the real-time media stream session is completed, and the media message carries the media stream identifier.
  • an embodiment of the present application also provides a communication device, including: a memory 1201, a processor 1202, and a computer program 1203 stored in the memory 1201 and running on the processor 1202, and the processor 1202 executes The program realizes the method of real-time media stream access as shown in FIG. 4.
  • an embodiment of the present application further provides a terminal, including: a memory 1301, a processor 1302, and a computer program 1303 stored on the memory 1301 and running on the processor 1302, and the processor 1302 executes all When the program is described, the method for real-time media stream access as shown in Figure 5 is realized.
  • An embodiment of the present application also provides a computer-readable storage medium that stores computer-executable instructions, and the computer-executable instructions are used to execute the method for real-time media stream access.
  • the above-mentioned storage medium may include, but is not limited to: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, magnetic disk or optical disk, etc.
  • U disk read-only memory
  • RAM Random Access Memory
  • mobile hard disk magnetic disk or optical disk, etc.
  • Such software may be distributed on a computer-readable medium, and the computer-readable medium may include a computer storage medium (or a non-transitory medium) and a communication medium (or a transitory medium).
  • the term computer storage medium includes volatile and non-volatile memory implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules, or other data). Sexual, removable and non-removable media.
  • Computer storage media include but are not limited to RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disk (DVD) or other optical disk storage, magnetic cassette, tape, magnetic disk storage or other magnetic storage device, or Any other medium used to store desired information and that can be accessed by a computer.
  • communication media usually contain computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as carrier waves or other transmission mechanisms, and may include any information delivery media .

Landscapes

  • Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

一种实时媒体流接入的方法、装置、通信设备和终端，所述方法包括：通信设备在实时媒体流会话建立过程中，确定实时媒体流对应的媒体流标识；所述通信设备为所述实时媒体流分配本端端口；其中，每个本端端口对应一个或多个实时媒体流；所述通信设备在实时媒体流会话建立完成后，转发承载所述实时媒体流的媒体报文，所述媒体报文携带所述媒体流标识。

Description

一种实时媒体流接入的方法、装置、通信设备和终端
相关申请的交叉引用
本申请基于申请号为201910351703.1、申请日为2019年4月28日的中国专利申请提出，并要求该中国专利申请的优先权，该中国专利申请的全部内容在此以引入方式并入本申请。
技术领域
本文涉及但不限于一种实时媒体流接入的方法、装置、通信设备、终端和计算机可读存储介质。
背景技术
IMS(IP Multimedia Subsystem，网际协议多媒体子系统)是3GPP(Third Generation Partnership Project，第三代合作伙伴计划)提出的支持IP多媒体业务的子系统，是多媒体通信的发展方向，作为4G时代中的应用子系统，能很好的满足4G时代中人与人之间的通信，其显著特征是采用了SIP(Session Initial Protocol，会话初始协议)体系，通信与接入方式无关，具备多种多媒体业务的控制功能与承载能力分离、呼叫与会话分离、应用与服务分离、业务与网络分离，以及移动网与因特网业务融合等多种能力。
在3GPP TS 23.228标准中，定义了IMSALG(Application Level Gateway，应用层网关)和IMS接入网关(IMS Access Gateway)的逻辑功能(见图1)，实际应用中会将两个逻辑功能组成P-CSCF(Proxy-Call Session Control Function，代理呼叫会话控制功能)或者称为SBC(Session Border Controller，会话边界控制器)，该逻辑功能作为边界控制设备，提供了接入网与IMS核心网之间的NAT(Net Address Translation，网络地址翻译)穿越、接入控制、QoS(Quality of Service，服务质量)控制、信令和承载安全以及IP互通等功能。
终端发送或接收的实时媒体流需要经过SBC进行转发，由于终端一般发送的报文会进行NAT，实际到达SBC的媒体报文与终端在SIP信令中携带的地址和端口不同，为了获得终端NAT转换后的IP地址和端口信息，一种常见的方法是SBC通常通过首包学习的方法，通过检测到达SBC本端特定端口的媒体报文信息，确定与终端的对应关系(见表1)。
表1首包学习方式建立的终端信息表
终端标识 终端NAT后的IP地址 终端NAT后的端口 SBC本端的IP地址 SBC本端的端口
138xxxx 221.135.8.9 17533 202.198.5.5 10000
139xxxx 211.178.9.10 24550 202.198.5.5 20000
...... ...... ...... ...... ......
这种方法虽然能识别出终端NAT后的IP地址和端口号，但存在端口占用过多等缺陷。
发明内容
以下是对本文详细描述的主题的概述。本概述并非是为了限制权利要求的保护范围。
本申请实施例提供了一种实时媒体流接入的方法、装置、通信设备、终端和计算机可读存储介质。
本申请实施例提供了一种实时媒体流接入的方法，包括：通信设备在实时媒体流会话建立过程中，确定实时媒体流对应的媒体流标识；所述通信设备为所述实时媒体流分配本端端口；其中，每个本端端口对应一个或多个实时媒体流；所述通信设备在实时媒体流会话建立完成后，转发承载所述实时媒体流的媒体报文，所述媒体报文携带所述媒体流标识。
本申请实施例还提供一种实时媒体流接入的方法，包括：终端在实时媒体流会话建立过程中，确定实时媒体流对应的媒体流标识；所述终端在实时媒体流会话建立完成后，发送承载所述实时媒体流的媒体报文，所述媒体报文携带所述媒体流标识。
本申请实施例还提供一种实时媒体流接入的装置，包括：第一确定模块，用于在实时媒体流会话建立过程中，确定实时媒体流对应的媒体流标识；分配模块，用于为所述实时媒体流分配本端端口；其中，每个本端端口对应一个或多个实时媒体流；转发模块，用于在实时媒体流会话建立完成后，转发承载所述实时媒体流的媒体报文，所述媒体报文携带所述媒体流标识。
本申请实施例还提供一种通信设备，包括：存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序，所述处理器执行所述程序时实现所述实时媒体流接入的方法。
本申请实施例还提供一种实时媒体流接入的装置，包括：第二确定模块，用于在实时媒体流会话建立过程中，确定实时媒体流对应的媒体流标识；发送模块，用于在实时媒体流会话建立完成后，发送承载所述实时媒体流的媒体报文，所述媒体报文携带所述媒体流标识。
本申请实施例还提供一种终端，包括：存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序，所述处理器执行所述程序时实现所述实时媒体流接入的方法。
本申请实施例还提供一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令用 于执行所述实时媒体流接入的方法。
在阅读并理解了附图和详细描述后，可以明白其他方面。
附图说明
图1为IMS应用层网关和IMS接入网关的逻辑功能的示意图；
图2为相关技术的媒体流接入方式的原理示意图；
图3为本申请实施例的系统架构示意图；
图4为本申请实施例的实时媒体流接入的方法的流程图(应用于通信设备)；
图5为本申请实施例的实时媒体流接入的方法的流程图(应用于终端)；
图6为本申请实施例的实时媒体流接入的方法的流程图(应用于IMS系统)；
图7为本申请实施例的网络侧为每个实时媒体流分配端口的示意图；
图8为本申请实施例的网络侧为每个实时媒体流分配统一端口的示意图；
图9为本申请实施例的用户侧媒体处理逻辑图，描述了SBC对于用户侧媒体的处理逻辑；
图10为本申请实施例的网络侧媒体处理逻辑图，描述了SBC对于网络侧媒体的处理逻辑；
图11为本申请应用实例的在IMS网络中的呼叫流程图；
图12为本申请应用实例的在IMS网络中SBC信令协商流程图，其中主叫不支持媒体流标识协商，被叫支持媒体流标识协商；
图13为本申请应用实例的在IMS网络中SBC信令协商流程图，其中主叫支持媒体流标识协商，被叫不支持媒体流标识协商；
图14为本申请应用实例的在IMS网络中SBC信令协商流程图，其中主叫不支持媒体流标识协商，主叫侧SBC直接拒绝；
图15为本申请应用实例的在IMS网络中SBC信令协商流程图，其中被叫不支持媒体流标识协商，被叫侧SBC直接拒绝；
图16为本申请实施例的实时媒体流接入的装置的示意图(应用于通信设备)；
图17为本申请实施例的实时媒体流接入的装置的示意图(应用于终端)；
图18为本申请实施例的通信设备的组成示意图；
图19为本申请实施例的终端的组成示意图。
具体实施方式
下文中将结合附图对本申请的实施例进行详细说明。
在附图的流程图示出的步骤可以在诸如一组计算机可执行指令的计算机系统中执行。并且，虽然在流 程图中示出了逻辑顺序，但是在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤。
目前SBC接入终端实时媒体流的方法中存在如下情况：
1、SBC侧的端口使用量大，公网IP地址需求多
参照图2，该方法需要为每个终端在SBC上分配一个不同的端口号，通过检测发送到本端端口的报文，建立对应的映射关系。而一个IP地址最多只能有65535个端口，意味着一个IP地址最多支持65535个媒体通道。如果需要提升媒体通道数，就需要增加IP地址数量。随着5G网络的部署，终端接入数大大增加，现有模式无法满足要求。
2、容易被恶意扫描占用
当有恶意软件获悉SBC的IP地址后，可以构造媒体报文发送给所有端口，由于SBC不判断媒体内容，只是判断是否是媒体报文，这就使得SBC误认为是构造的媒体报文是真实媒体，分配对应的端口给恶意软件，从而使得端口被非法占用。
在本申请实施例中，增加了媒体流标识协商和认证环节，提供了媒体流安全接入、防恶意攻击等功能。
参照图3，本申请实施例的IMS网络架构主要包括如下网元：
SBC100，用于为终端提供接入服务，在本申请实施例中可以包括：
SBC-信令处理模块101：用于为媒体流分配媒体流标识，或收到媒体流标识时记录媒体流标识，以及将媒体流标识通知媒体处理模块102；
SBC-媒体处理模块102：用于对媒体流标识进行验证，并根据预设策略建立媒体报文传输路径。
呼叫会话控制功能(CSCF)110：用于进行业务触发和呼叫路由，在本申请实施例中无特殊要求。
应用服务器(AS)115：用于为用户提供通信业务，在本申请实施例中无特殊要求。
终端(UE)120：在呼叫请求/响应中指示支持媒体认证能力，记录媒体流标识，以及在发送的媒体报文中携带媒体流标识，可以包括：
信令处理模块121：用于在呼叫请求中在呼叫请求/响应中指示支持媒体认证能力，记录媒体流标识，并传递媒体流标识以及SBC的IP地址和端口信息给媒体处理模块122；
媒体处理模块122：用于向SBC的IP地址和端口发送媒体报文，并在媒体报文中携带媒体流标识。
如图4所示，本申请实施例的实时媒体流接入的方法，应用于通信设备，包括：
步骤201，通信设备在实时媒体流会话建立过程中，确定实时媒体流对应的媒体流标识。
所述通信设备可以包括SBC，所述SBC可以是主叫侧的SBC，也可以是被叫侧的SBC。
对于所述通信设备包括主叫侧的SBC的情况：
在一实施例中，由所述通信设备分配媒体流标识，步骤201可以包括：
所述通信设备接收所述主叫终端发送的实时媒体流的业务请求，所述业务请求携带支持媒体流认证能 力；
所述通信设备分配全局唯一的标识作为所述实时媒体流对应的媒体流标识。
在一实施例中，由所述主叫终端分配媒体流标识，通信设备确定该媒体流标识是否可用，步骤201可以包括：
所述通信设备接收所述主叫终端发送的实时媒体流的业务请求，所述业务请求携带支持媒体流认证能力以及所述主叫终端分配的媒体流标识；
所述通信设备确定所述主叫终端分配的媒体流标识未被占用，则确定所述主叫终端分配的媒体流标识为所述实时媒体流对应的媒体流标识。
在一实施例中，由所述主叫终端分配媒体流标识，通信设备确定该媒体流标识是否可用，在不可用时，由通信设备分配媒体流标识，步骤201可以包括：
所述通信设备接收所述主叫终端发送的实时媒体流的业务请求，所述业务请求携带支持媒体流认证能力以及所述主叫终端分配的媒体流标识；
所述通信设备确定所述主叫终端分配的媒体流标识已被占用，则分配全局唯一的标识作为所述实时媒体流对应的媒体流标识；
所述通信设备将所述实时媒体流对应的媒体流标识告知所述主叫终端。
在一实施例中，所述通信设备接收主叫终端发送的实时媒体流的业务请求，所述业务请求未携带支持媒体流认证能力；
所述通信设备拒绝所述主叫终端接入。
其中，在主叫终端不支持媒体流认证能力时，所述通信设备可以直接拒绝接入，也可以按照现有流程进行兼容处理。
对于所述通信设备包括被叫侧的SBC的情况：
在一实施例中，步骤201可以包括：
所述通信设备接收主叫侧SBC发送的实时媒体流的业务请求，从所述业务请求中获得所述媒体流标识。
在一实施例中，所述通信设备接收被叫终端发送的实所述业务请求的响应，所述业务请求未携带支持媒体流认证能力；
所述通信设备拒绝所述被叫终端接入。
其中，在被叫终端不支持媒体流认证能力时，所述通信设备可以直接拒绝接入，也可以按照现有流程进行兼容处理。
对于主叫侧的SBC和被叫侧的SBC，在一实施例中，接收所述业务请求的响应，确定所述响应未携带媒体流标识，在所述响应中加入所述实时媒体流对应的媒体流标识，转发所述携带所述媒体流标识的响应。
对于主叫侧的SBC和被叫侧的SBC，在一实施例中，接收所述业务请求的响应，确定所述响应携带媒体流标识，比较所述响应携带的媒体流标识与所述实时媒体流对应的媒体流标识是否一致，在不一致的情况下，将所述响应携带的媒体流标识替换为所述实时媒体流对应的媒体流标识，转发所述响应。
其中，在一致的情况下，直接转发所述响应。
步骤202，所述通信设备为所述实时媒体流分配本端端口；其中，每个本端端口对应一个或多个实时媒体流。
在本申请实施例中，多个实时媒体流可以共用一个本端端口。SBC在建立一个本端端口与多个实时媒体流的对应关系时，确定所有媒体流对应的总带宽，以适应一个UDP端口的流量不超过一个物理端口的流量范围。
步骤203，所述通信设备在实时媒体流会话建立完成后，转发承载所述实时媒体流的媒体报文，所述媒体报文携带所述媒体流标识。
本申请实施例通过在媒体报文中携带终端媒体流标识，多个实时媒体流可以共用一个本端端口的方式，实现提升媒体端口利用率，提升系统容量，满足超大规模终端接入的要求。
在一实施例中，所述方法还包括：
所述通信设备通过检查所述媒体报文中的媒体流标识，进行媒体流合法性判断。
其中，进行媒体流合法性判断，可以包括：
所述通信设备确定本端端口对应的一个或多个媒体流标识包含所述媒体报文中的媒体流标识时，判断所述实时媒体流合法；
所述通信设备确定本端端口对应的一个或多个媒体流标识不包含所述媒体报文中的媒体流标识时，判断所述实时媒体流非法。
1、对于判断所述实时媒体流合法的情况：
记录所述媒体报文中源地址信息对应的转发路由，后续接到承载所述实时媒体流的媒体报文时，直接进行转发。
其中，所述源地址信息包括源IP地址和端口号的组合(即IP+Port)。
在所述通信设备确定接收到的媒体报文中源地址信息没有对应的转发路由时，才进行媒体流合法性判断。
SBC建立媒体流标识和终端源IP+Port的映射关系，可以实现快速转发。
SBC的网络侧可以为每个实时媒体流分配单独的IP+Port组合，以实现报文的快速转发；SBC的网络侧可以采用多个实时媒体流共用一个端口的方法，网络侧通过分析媒体报文的中全局唯一媒体流标识确定转发规则。
2、对于判断所述实时媒体流非合法的情况：
丢弃承载所述实时媒体流的媒体报文。
在一实施例中，在判断所述实时媒体流非法时，将承载所述实时媒体流的媒体报文中源地址信息记录为黑名单，后续接到携带所述源地址信息的媒体报文时，直接丢弃。
本申请实施例中，通过进行媒体流合法性判断，提供了媒体流安全接入，防止恶意攻击。
如图5所示，本申请实施例的实时媒体流接入的方法，应用于终端，包括：
步骤301，终端在实时媒体流会话建立过程中，确定实时媒体流对应的媒体流标识。
在一实施例中，所述终端作为主叫终端时，由所述通信设备分配媒体流标识，步骤301包括：
所述终端发送实时媒体流的业务请求，所述业务请求携带支持媒体流认证能力；
所述终端接收所述业务请求的响应，所述响应携带所述媒体流标识。
在一实施例中，所述终端作为主叫终端时，由所述终端分配媒体流标识，通信设备确认，步骤301包括：
所述终端发送实时媒体流的业务请求，所述业务请求携带支持媒体流认证能力以及所述终端分配的媒体流标识；
所述终端接收所述业务请求的响应，根据所述响应携带的媒体流标识确定所述实时媒体流对应的媒体流标识。
在一实施例中，所述终端作为被叫终端时，步骤301包括：
所述终端接收实时媒体流的业务请求，从所述业务请求获得所述媒体流标识。
步骤302，所述终端在实时媒体流会话建立完成后，发送承载所述实时媒体流的媒体报文，所述媒体报文携带所述媒体流标识。
在一实施例中，所述媒体报文包括RTP(Real-time Transport Protocol，实时传输协议)报文，所述终端在所述RTP报文的同步源SSRC字段携带所述媒体流标识的参数。
在一实施例中，所述终端扩展所述RTP报文，在所述RTP报文的扩展头部携带所述媒体流标识。
如图6所示，本申请实施例的实时媒体流接入过程可以包括如下步骤：
步骤401，主叫终端在发起业务请求时，所述业务请求携带支持媒体流认证能力；
步骤402，主叫侧SBC收到主叫终端的业务请求时，为本次会话中的每个实时媒体流创建全局唯一的标识，将该唯一标识插入到业务请求中；
SBC在本端记录终端用户标识与实时媒体流标识的对应关系，并为该每个实时媒体流指定本端端口，多个实时媒体流可以共用一个本端端口。
在一实施例中，SBC在建立一个本端端口与多个实时媒体流的对应关系时，确定所有媒体流对应的总 带宽，以适应一个UDP端口的流量不超过一个物理端口的流量范围；
步骤403，主叫侧SBC向主叫CSCF发送业务请求时，将原始SIP请求中的终端媒体地址和端口替换成主叫侧SBC的媒体地址和端口；
当SBC网络侧的IP地址充裕时，使用单独的IP+Port组合对应该实时媒体流(参照表2和图7)；当SBC网络侧的IP地址不充裕时，可以多个媒体流共用一个网络侧IP+Port组合(参照表3和图8)。
表2
Figure PCTCN2020085179-appb-000001
表2中，SBC侧的用户面端口允许多个终端的媒体流共用同一个SBC的用户面端口，在网络侧为每个终端的每个媒体流分配一个用户面端口进行映射。
表3
Figure PCTCN2020085179-appb-000002
表3中，SBC侧的用户面端口允许多个终端的媒体流共用同一个SBC的用户面端口，在网络侧为每 个终端的每个媒体流分配共享的用户面端口进行映射。
步骤404，主叫CSCF根据IMS基本呼叫的流程，将业务请求转发到被叫SBC；
步骤405，被叫侧SBC提取实时媒体流标识，并分配本端端口与该实时媒体流标识关联，多个实时媒体流可以共用一个本端端口。
在一实施例中，SBC在建立一个本端端口与多个实时媒体流的对应关系时，考虑所有媒体流对应的总带宽，以适应一个UDP端口的流量不超过一个物理端口的流量范围；
步骤406，被叫侧SBC转发业务请求给被叫终端；
步骤407，被叫终端解析业务请求中的媒体信息，记录该媒体流标识、媒体流的IP+Port的对应关系；
步骤408，被叫终端在发送响应时，在业务响应中携带媒体流标识；
步骤409，被叫侧SBC在收到被叫终端的响应时，在业务响应中插入实时媒体流标识；
在一实施例中，如果被叫终端在发送的响应中携带了实时媒体流标识，SBC比较与本地记录的内容是否一致，如果不一致，则进行替换；
步骤410，被叫侧SBC按照标准IMS的呼叫流程，路由响应给主叫侧SBC；
步骤411，主叫侧SBC解析业务响应中的信息，判断响应中是否携带了实时媒体流统一标识，如果未携带，则插入本端在请求中对应的实时媒体流标识；如果业务响应中已经携带了实时媒体流统一标识，则比较与请求中的实时媒体流标识是否一致，如果不一致，则替换成请求中的实时媒体流标识；SBC将响应中的实时媒体流的地址信息修改为本端对应的IP+Port；
步骤412，主叫终端在收到主叫侧SBC转发的响应后，提取实时媒体流标识以及SBC的IP+Port；
至此，主叫终端和被叫终端都建立实时媒体流标识与SBC用户侧(UNI)接收端的IP+Port的对应关系。
步骤413，主叫或被叫终端发送实时媒体流给SBC的IP+Port，在实时媒体流中携带实时媒体流标识；
步骤414，SBC收到实时媒体流时，先检查源IP+Port是否有对应的转发路由，即根据源IP+Port能转到需要转发的目的IP+Port，如果能找到，则直接进行转发；如果未找到，SBC检查分析媒体报文中的实时媒体流标识，查询SBC本端端口对应的实时媒体流标识中是否包含该标识，如果包含，则表示该实时媒体流合法，将终端的源IP+Port记录到转发路由中，后续该IP+Port发送的实时媒体流可以直接进行转发，不需要再判断实时媒体流标识，提高处理效率。如果未包含在端口对应的实时媒体流标识列表中，则表示该媒体流非法，直接进行丢弃，参见图9。
可以将该终端对应的IP+Port记录黑名单，后续收到该来源的报文时，可以直接丢弃。
步骤415，SBC转发实时媒体流给对端SBC，对端SBC收到网络侧发送的媒体流时，SBC根据本端的IP+Port是否有唯一的转发关系，如果本端为每个实时媒体流分配了单独的端口，则可以确定转发关系，对端SBC根据对应路由关系直接转发；如果网络侧(NNI)接收端的IP+Port对应了多个实时媒体流，则通 过分析实时媒体流中的唯一媒体流标识，确定对应的用户侧(UNI)的目标端口进行转发。如果根据媒体流中的媒体流标识无法确定转发路由，则直接丢弃该报文，参见图10。
至此，SBC实现了实时媒体流的接收和转发。
本申请实施例增加了媒体流标识协商和认证环节，提供了媒体流安全接入、防恶意攻击等功能，而且可以大大提升了用户侧IP+Port的利用率，减少了IP地址的需求量。
下面以一些应用实例进行说明：
如图11所示，为在IMS网络中的呼叫流程应用实例，以SIP(Session Initiation Protocol)协议为例，描述在IMS网络中实现本方法，包括如下步骤：
步骤501，终端UE1发起业务请求给SBC1，在INVITE(邀请)请求中携带“媒体认证”能力“Supported:media-auth，m＝audio”；
步骤502，SBC1为每个媒体流生成媒体流唯一的标识，用于对媒体进行认证。SBC1在转发业务请求给下一跳时，携带媒体流标识；
步骤503，IMS将业务请求路由到被叫终端所在SBC2，在请求中包括了媒体流标识。
步骤504，SBC2记录媒体流标识，并在转发给终端UE2的请求中携带媒体流标识。如果要求被叫终端强制支持媒体认证，则在请求中携带要求终端支持媒体认证能力的头部“Require:media-auth”；如果不要求被叫终端强制支持媒体认证，则在请求中携带本端支持媒体认证能力的头部“Supported:media-auth”；
步骤505，UE2在返回的18x(180或183等临时响应的统称)响应中携带媒体流标识，表示本端接受媒体流对应的媒体流标识，并携带支持媒体认证的能力标志“Supported:media-auth”；
步骤506，SBC2在转发的18x响应中携带媒体流标识；
步骤507，IMS在转发给SBC1的18x响应中携带媒体流标识；
步骤508，SBC1在转发给终端的18x响应中携带媒体流标识；
步骤509，主叫终端UE1记录18x响应中每个媒体的认证标识；
步骤510，用户应答后，UE2返回200OK(应答响应)响应给SBC2；
步骤511，SBC2在转发200OK响应给IMS；
步骤512，IMS在转发给SBC1的200OK响应；
步骤513，SBC1在转发200OK响应给终端UE1；
步骤514，主叫终端UE1发送ACK(确认请求)给SBC1，表示会话建立；
步骤515，SBC1转发ACK请求给IMS；
步骤516，IMS转发ACK请求给SBC2；
步骤517，SBC2转发ACK请求给UE2；
步骤518，UE1和UE2发送的RTP媒体流中携带媒体流标识。
如图12所示，为在IMS网络中SBC信令协商流程的应用实例，其中主叫不支持媒体流标识协商，被叫支持媒体流标识协商，包括如下步骤：
步骤601，终端UE1发起业务请求给SBC1，在INVITE请求中未携带“媒体认证”能力，表示本端不支持媒体认证；
步骤602，SBC1为每个媒体流生成媒体流唯一的标识，用于对媒体进行认证。SBC1在转发业务请求给下一跳时，携带媒体流标识；
步骤603，IMS将业务请求路由到被叫终端所在SBC2，在请求中包括了媒体流标识。
步骤604，SBC2记录媒体流标识，并在转发给终端UE2的请求中携带媒体流标识。如果要求被叫终端强制支持媒体认证，则在请求中携带要求终端支持媒体认证能力的头部“Require:media-auth”；如果不要求被叫终端强制支持媒体认证，则在请求中携带本端支持媒体认证能力的头部“Supported:media-auth”；在本例中，不要求被叫终端强制支持媒体认证；
步骤605，UE2在返回的18x响应中携带媒体流标识，表示本端接受媒体流对应的媒体流标识，并携带支持媒体认证的能力标志“Supported:media-auth”；
步骤606，SBC2在转发的18x响应中携带媒体流标识；
步骤607，IMS在转发给SBC1的18x响应中携带媒体流标识；
步骤608，SBC1在转发给终端的18x响应中携带媒体流标识；
步骤609，主叫终端UE1忽略18x响应中的媒体流标识，在媒体流中不插入媒体流标识，同时，按照无媒体认证方式进行媒体协商；
步骤610，用户应答后，UE2返回200OK响应给SBC2；
步骤611，SBC2在转发200OK响应给IMS；
步骤612，IMS在转发给SBC1的200OK响应；
步骤613，SBC1在转发200OK响应给终端UE1；
步骤614，主叫终端UE1发送ACK给SBC1，表示会话建立；
步骤615，SBC1转发ACK请求给IMS；
步骤616，IMS转发ACK请求给SBC2；
步骤617，SBC2转发ACK请求给UE2；
步骤618，UE1发送的RTP媒体流中不携带媒体流标识，UE2发送的RTP媒体流中携带媒体流标识。
如图13所示，为在IMS网络中SBC信令协商流程的应用实例，其中主叫支持媒体流标识协商，被叫 不支持媒体流标识协商，包括如下步骤：
步骤701，终端UE1发起业务请求给SBC1，在INVITE请求中携带“媒体认证”能力，表示本端支持媒体认证；
步骤702，SBC1为每个媒体流生成媒体流唯一的标识，用于对媒体进行认证。SBC1在转发业务请求给下一跳时，携带媒体流标识；
步骤703，IMS将业务请求路由到被叫终端所在SBC2，在请求中包括了媒体流标识。
步骤704，SBC2记录媒体流标识，并在转发给终端UE2的请求中携带媒体流标识。如果要求被叫终端强制支持媒体认证，则在请求中携带要求终端支持媒体认证能力的头部“Require:media-auth”；如果不要求被叫终端强制支持媒体认证，则在请求中携带本端支持媒体认证能力的头部“Supported:media-auth”；在本例中，不要求被叫终端强制支持媒体认证；
步骤705，UE2在返回的18x响应中未携带媒体流标识，以及支持媒体认证的能力标志“Supported:media-auth”，表示本端不支持媒体认证；
步骤706，SBC2在转发的18x响应中不携带媒体流标识；
步骤707，IMS在转发给SBC1的18x响应中不携带媒体流标识；
步骤708，SBC1在转发给终端的18x响应中插入之前生成的媒体流标识；
步骤709，主叫终端UE1保存媒体流标识，在媒体流中插入媒体流标识，同时，按照媒体认证方式进行媒体协商；
步骤710，用户应答后，UE2返回200OK响应给SBC2；
步骤711，SBC2在转发200OK响应给IMS；
步骤712，IMS在转发给SBC1的200OK响应；
步骤713，SBC1在转发200OK响应给终端UE1；
步骤714，主叫终端UE1发送ACK给SBC1，表示会话建立；
步骤715，SBC1转发ACK请求给IMS；
步骤716，IMS转发ACK请求给SBC2；
步骤717，SBC2转发ACK请求给UE2；
步骤718，UE1发送的RTP媒体流不携带媒体流标识，UE2发送的RTP媒体流中不携带媒体流标识。
如图14所示，为在IMS网络中SBC信令协商流程的应用实例，其中主叫不支持媒体流标识协商，主叫侧SBC直接拒绝，包括如下步骤：
步骤801，终端UE1发起业务请求给SBC1，在INVITE请求中未携带“媒体认证”能力，表示本端不支持媒体认证；
步骤802，SBC1确定本次需要进行媒体认证，而主叫终端不支持，返回421Extension Required失败响应，其中，指示终端要求支持媒体认证；
步骤803，终端UE1发送ACK，结束本次会话。
如图15所示，为在IMS网络中SBC信令协商流程的应用实例，其中被叫不支持媒体流标识协商，被叫侧SBC直接拒绝，包括如下步骤：
步骤901，终端UE1发起业务请求给SBC1，在INVITE请求中携带“媒体认证”能力，表示本端支持媒体认证；
步骤902，SBC1为每个媒体流生成媒体流唯一的标识，用于对媒体进行认证。SBC1在转发业务请求给下一跳时，携带媒体流标识；
步骤903，IMS将业务请求路由到被叫终端所在SBC2，在请求中包括了媒体流标识。
步骤904，SBC2记录媒体流标识，并在转发给终端UE2的请求中携带媒体流标识。要求被叫终端强制支持媒体认证，在请求中携带要求终端支持媒体认证能力的头部“Require:media-auth”；
步骤905，UE2发现本端不支持媒体认证，返回420Bad Extension失败响应，其中，指明不支持媒体认证能力“Supported:media-auth”；
步骤906，SBC2在转发的420响应中给IMS；
步骤907，IMS转发SBC1的420响应；
步骤908，SBC1在转发给终端420响应；
步骤909，主叫终端UE1发送ACK给SBC1，表示会话结束；
步骤910，SBC1转发ACK请求给IMS；
步骤911，IMS转发ACK请求给SBC2；
步骤912，SBC2转发ACK请求给UE2。
如图16所示，本申请实施例还提供一种实时媒体流接入的装置，应用于通信设备，包括：
第一确定模块1001，用于在实时媒体流会话建立过程中，确定实时媒体流对应的媒体流标识；
分配模块1002，用于为所述实时媒体流分配本端端口；其中，每个本端端口对应一个或多个实时媒体流；
转发模块1003，用于在实时媒体流会话建立完成后，转发承载所述实时媒体流的媒体报文，所述媒体报文携带所述媒体流标识。
如图17所示，本申请实施例还提供一种实时媒体流接入的装置，应用于终端，包括：
第二确定模块1101，用于在实时媒体流会话建立过程中，确定实时媒体流对应的媒体流标识；
发送模块1102，用于在实时媒体流会话建立完成后，发送承载所述实时媒体流的媒体报文，所述媒体报文携带所述媒体流标识。
如图18所示，本申请实施例还提供一种通信设备，包括：存储器1201、处理器1202及存储在存储器1201上并可在处理器1202上运行的计算机程序1203，所述处理器1202执行所述程序时实现如图4所述实时媒体流接入的方法。
如图19所示，本申请实施例还提供一种终端，包括：存储器1301、处理器1302及存储在存储器1301上并可在处理器1302上运行的计算机程序1303，所述处理器1302执行所述程序时实现如图5所述实时媒体流接入的方法。
本申请实施例还提供一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令用于执行所述实时媒体流接入的方法。
在本实施例中，上述存储介质可以包括但不限于：U盘、只读存储器(ROM，Read-OnlyMemory)、随机存取存储器(RAM，Random Access Memory)、移动硬盘、磁碟或者光盘等各种可以存储程序代码的介质。
本领域普通技术人员可以理解，上文中所公开方法中的全部或某些步骤、系统、装置中的功能模块/单元可以被实施为软件、固件、硬件及其适当的组合。在硬件实施方式中，在以上描述中提及的功能模块/单元之间的划分不一定对应于物理组件的划分；例如，一个物理组件可以具有多个功能，或者一个功能或步骤可以由若干物理组件合作执行。某些组件或所有组件可以被实施为由处理器，如数字信号处理器或微处理器执行的软件，或者被实施为硬件，或者被实施为集成电路，如专用集成电路。这样的软件可以分布在计算机可读介质上，计算机可读介质可以包括计算机存储介质(或非暂时性介质)和通信介质(或暂时性介质)。如本领域普通技术人员公知的，术语计算机存储介质包括在用于存储信息(诸如计算机可读指令、数据结构、程序模块或其他数据)的任何方法或技术中实施的易失性和非易失性、可移除和不可移除介质。计算机存储介质包括但不限于RAM、ROM、EEPROM、闪存或其他存储器技术、CD-ROM、数字多功能盘(DVD)或其他光盘存储、磁盒、磁带、磁盘存储或其他磁存储装置、或者可以用于存储期望的信息并且可以被计算机访问的任何其他的介质。此外，本领域普通技术人员公知的是，通信介质通常包含计算机可读指令、数据结构、程序模块或者诸如载波或其他传输机制之类的调制数据信号中的其他数据，并且可包括任何信息递送介质。

Claims (18)

  1. 一种实时媒体流接入的方法，包括：
    通信设备在实时媒体流会话建立过程中，确定实时媒体流对应的媒体流标识；
    所述通信设备为所述实时媒体流分配本端端口；其中，每个本端端口对应一个或多个实时媒体流；
    所述通信设备在实时媒体流会话建立完成后，转发承载所述实时媒体流的媒体报文，所述媒体报文携带所述媒体流标识。
  2. 如权利要求1所述的方法，其中，所述通信设备包括主叫侧的会话边界控制器SBC，所述通信设备在实时媒体流会话建立过程中，确定实时媒体流对应的媒体流标识，包括：
    所述通信设备接收所述主叫终端发送的实时媒体流的业务请求，所述业务请求携带支持媒体流认证能力；
    所述通信设备分配全局唯一的标识作为所述实时媒体流对应的媒体流标识。
  3. 如权利要求1所述的方法，其中，所述通信设备包括主叫侧的SBC，所述通信设备在实时媒体流会话建立过程中，确定实时媒体流对应的媒体流标识，包括：
    所述通信设备接收所述主叫终端发送的实时媒体流的业务请求，所述业务请求携带支持媒体流认证能力以及所述主叫终端分配的媒体流标识；
    所述通信设备确定所述主叫终端分配的媒体流标识未被占用，则确定所述主叫终端分配的媒体流标识为所述实时媒体流对应的媒体流标识。
  4. 如权利要求1所述的方法，其中，所述通信设备包括主叫侧的SBC，所述通信设备在实时媒体流会话建立过程中，确定实时媒体流对应的媒体流标识，包括：
    所述通信设备接收所述主叫终端发送的实时媒体流的业务请求，所述业务请求携带支持媒体流认证能力以及所述主叫终端分配的媒体流标识；
    所述通信设备确定所述主叫终端分配的媒体流标识已被占用，则分配全局唯一的标识作为所述实时媒体流对应的媒体流标识；
    所述通信设备将所述实时媒体流对应的媒体流标识告知所述主叫终端。
  5. 如权利要求1所述的方法，其中，所述通信设备包括主叫侧的SBC，所述方法还包括：
    所述通信设备接收主叫终端发送的实时媒体流的业务请求，所述业务请求未携带支持媒体流认证能力；
    所述通信设备拒绝所述主叫终端接入。
  6. 如权利要求1所述的方法，其中，所述通信设备包括被叫侧的SBC，所述通信设备在实时媒体流会话建立过程中，确定实时媒体流对应的媒体流标识，包括：
    所述通信设备接收主叫侧SBC发送的实时媒体流的业务请求，从所述业务请求中获得所述媒体流标识。
  7. 如权利要求6所述的方法，其中，所述方法还包括：
    所述通信设备接收被叫终端发送的实所述业务请求的响应，所述业务请求未携带支持媒体流认证能力；
    所述通信设备拒绝所述被叫终端接入。
  8. 如权利要求2、3、4和6中任意一项所述的方法，其中，所述方法还包括：
    所述通信设备接收所述业务请求的响应，确定所述响应未携带媒体流标识，在所述响应中加入所述实时媒体流对应的媒体流标识，转发所述携带所述媒体流标识的响应。
  9. 如权利要求2、3、4和6中任意一项所述的方法，其中，所述方法还包括：
    所述通信设备接收所述业务请求的响应，确定所述响应携带媒体流标识，比较所述响应携带的媒体流标识与所述实时媒体流对应的媒体流标识是否一致，在不一致的情况下，将所述响应携带的媒体流标识替换为所述实时媒体流对应的媒体流标识，转发所述响应。
  10. 如权利要求1所述的方法，其中，所述方法还包括：
    所述通信设备通过检查所述媒体报文中的媒体流标识，进行媒体流合法性判断。
  11. 如权利要求10所述的方法，其中，所述通信设备通过检查所述媒体报文中的媒体流标识，进行媒体流合法性判断，包括：
    所述通信设备确定本端端口对应的一个或多个媒体流标识包含所述媒体报文中的媒体流标识时，判断所述实时媒体流合法；
    所述通信设备确定本端端口对应的一个或多个媒体流标识不包含所述媒体报文中的媒体流标识时，判断所述实时媒体流非法。
  12. 如权利要求10所述的方法，其中，所述通信设备进行媒体流合法性判断之前，所述方法还包括：
    所述通信设备确定接收到的媒体报文中源地址信息没有对应的转发路由；
    其中，所述源地址信息包括源IP地址和端口号的组合。
  13. 如权利要求10所述的方法，其中，所述通信设备进行媒体流合法性判断之后，所述方法还包括：
    在判断所述实时媒体流合法时，记录所述媒体报文中源地址信息对应的转发路由，后续接到承载所述实时媒体流的媒体报文时，直接进行转发；
    在判断所述实时媒体流非法时，丢弃承载所述实时媒体流的媒体报文。
  14. 如权利要求10所述的方法，其中，所述通信设备进行媒体流合法性判断之后，所述方法还包括：
    在判断所述实时媒体流非法时，将承载所述实时媒体流的媒体报文中源地址信息记录为黑名单，后续接到携带所述源地址信息的媒体报文时，直接丢弃。
  15. 一种实时媒体流接入的方法，包括：
    终端在实时媒体流会话建立过程中，确定实时媒体流对应的媒体流标识；
    所述终端在实时媒体流会话建立完成后，发送承载所述实时媒体流的媒体报文，所述媒体报文携带所述媒体流标识。
  16. 一种通信设备，包括：存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序，其中，所述处理器执行所述程序时实现如权利要求1～14中任意一项所述实时媒体流接入的方法。
  17. 一种终端，包括：存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序，其中，所述处理器执行所述程序时实现如权利要求15所述实时媒体流接入的方法。
  18. 一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令用于执行权利要求1～15中任意一项所述实时媒体流接入的方法。
PCT/CN2020/085179 2019-04-28 2020-04-16 一种实时媒体流接入的方法、装置、通信设备和终端 WO2020221018A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP20798033.5A EP3962018A4 (en) 2019-04-28 2020-04-16 METHOD AND DEVICE FOR ACCESSING REAL-TIME MULTIMEDIA STREAMS, COMMUNICATION DEVICE AND TERMINAL

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910351703.1 2019-04-28
CN201910351703.1A CN111865875B (zh) 2019-04-28 2019-04-28 一种实时媒体流接入的方法、装置、通信设备和终端

Publications (1)

Publication Number Publication Date
WO2020221018A1 true WO2020221018A1 (zh) 2020-11-05

Family

ID=72966325

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/085179 WO2020221018A1 (zh) 2019-04-28 2020-04-16 一种实时媒体流接入的方法、装置、通信设备和终端

Country Status (3)

Country Link
EP (1) EP3962018A4 (zh)
CN (1) CN111865875B (zh)
WO (1) WO2020221018A1 (zh)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2008155174A1 (en) * 2007-06-20 2008-12-24 Alcatel Lucent Method and apparatuses of setting up a call-back by a user receiving a media stream
CN101378535A (zh) * 2007-08-27 2009-03-04 华为技术有限公司 一种传输媒体流控制消息的方法、系统及装置
CN101447893A (zh) * 2008-12-31 2009-06-03 华为技术有限公司 多媒体业务备份的方法和系统及终端、呼叫会话控制服务器

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7756120B2 (en) * 2007-03-09 2010-07-13 Siemens Enterprise Communications, Inc. Method for tagging SIP contact headers while preserving the contact header format towards softswitches
CN101202749B (zh) * 2007-11-16 2011-12-07 华为技术有限公司 一种sip网络中处理媒体流请求的方法、系统及装置
CN104243422A (zh) * 2013-06-19 2014-12-24 中兴通讯股份有限公司 用户终端接入ims网络的注册实现方法及ims
CA2882968C (en) * 2015-02-23 2023-04-25 Sulfur Heron Cognitive Systems Inc. Facilitating generation of autonomous control information

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2008155174A1 (en) * 2007-06-20 2008-12-24 Alcatel Lucent Method and apparatuses of setting up a call-back by a user receiving a media stream
CN101378535A (zh) * 2007-08-27 2009-03-04 华为技术有限公司 一种传输媒体流控制消息的方法、系统及装置
CN101447893A (zh) * 2008-12-31 2009-06-03 华为技术有限公司 多媒体业务备份的方法和系统及终端、呼叫会话控制服务器

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
3GPP TS 23.228
NOKIA: "Service information", 3GPP TSG-SA2 MEETING #38 TDOC S2-040997, 20 February 2004 (2004-02-20), XP050247875, DOI: 20200706153751Y *
See also references of EP3962018A4

Also Published As

Publication number Publication date
CN111865875A (zh) 2020-10-30
EP3962018A1 (en) 2022-03-02
CN111865875B (zh) 2023-04-18
EP3962018A4 (en) 2022-06-08

Similar Documents

Publication Publication Date Title
EP2605471B1 (en) Relay-based media channel establishing method and the system thereof
US8356092B2 (en) Methods, apparatuses, system, and related computer program product for policy control
US11206291B2 (en) Session control logic with internet protocol (IP)-based routing
EP2543226B1 (en) Method and apparatus for policy control within network comprising a mobile network and a fixed line network
US20040249887A1 (en) Conversational bearer negotiation
US7697471B2 (en) Address translation in a communication system
EP1760986A1 (en) Communication method and device for preventing media stream circuity (tromboning)
US8325707B2 (en) Session initiation from application servers in an IP multimedia subsystem
KR20050095625A (ko) 부하 제어 정보의 메시지 기반의 운반
KR100928247B1 (ko) 통신 네트워크들 간의 보안 통신을 제공하기 위한 방법 및시스템
JP2018503886A (ja) オペレータネットワークを介したブラウザベースのサービスの認証
US20100002701A1 (en) System and method for media communication through network address translation
EP1981246B1 (en) A method, apparatus and system for checking the validity for globally routable user agent uri
WO2008095430A1 (fr) Procédé et système pour protéger un organisme médiatique contre une attaque de pirates informatiques
JP6101644B2 (ja) 通信システム、識別子付与装置および通信方法
WO2020221018A1 (zh) 一种实时媒体流接入的方法、装置、通信设备和终端
US9456390B2 (en) Method and apparatuses for maintaining service continuity to a centralization and continuity application server
US20100023998A1 (en) Method, entity and system for realizing network address translation
US7639698B1 (en) Trusted multimedia communications
KR100929083B1 (ko) 이종망간 서비스 제공 방법
JP5135257B2 (ja) ホームゲートウェイ及びセッション制御サーバによって異なる経路の複数のセッションを確立する方法及びシステム
JP2007318707A (ja) Ｉｐ通信網の相互接続システム及びｉｐ通信網の相互接続方法
JP5247534B2 (ja) ホームゲートウェイによって異なる経路の複数のセッションを確立する方法及びシステム
KR101017497B1 (ko) ＳＩＰ메시지 처리 장치, ＮＡＴ―Ｔｒａｖｅｒｓａｌ 시스템 및 방법
KR20070076556A (ko) 인터넷 멀티미디어 서브시스템기반의 차세대 네트워크에서인터넷 프로토콜 옵션 헤더를 이용한 자원예약 기법

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20798033

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2020798033

Country of ref document: EP

Effective date: 20211127