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/1066—Session management
  • H04L65/1101—Session protocols
  • H04L65/1104—Session initiation protocol [SIP]
• • 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/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/60—Network streaming of media packets
• • 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/80—Responding to QoS

Definitions

• the invention lies in the field of media flow management during a communication session, and more particularly relates to a method of prioritizing media streams associated with a multimedia communication session between two entities.
• IETF RFC 3264 titled “An Offer / Answer Model with the Session Description Protocol” also describes a mechanism that allows two entities to use the SDP to negotiate settings for desired media streams for a session to be established or modified.
• a first entity submits an offer, called "SDP offer”, in the form of a session description to establish or modify a session, to a second entity.
• This offer includes a list of media flow descriptions specifying in particular for each stream a type of media (e.g. audio, video, text), a destination port number, a transport protocol, or encoding information.
• the entity submitting the offer can thus indicate to the entity receiving the offer, the different media and characteristics (e.g. type of encoding) associated that it is able to support.
• the entity receiving the offer accepts the offer by issuing a response, called "SDP response", indicating to the issuing entity of the offers the media feeds it is able to process.
• the entity receiving the offer may also issue a new offer to the first entity, including for example other media it wishes to add to the session.
• the two entities are thus likely to play indifferently the role of the issuer of an offer and that of the recipient of an offer.
• This offer / answer mechanism is also applicable for communication sessions involving more than two participants (eg videoconferencing with more than two participants).
• RFC 4412 "Communications Resource Priority for the Session Initiation Protocol (SIP)" defines a "Resource-Priority" SIP header field to identify a SIP request as requiring priority access to certain network resources. (eg network gateways, routers, SIP proxy).
• the SIP header field "Resource-Priority” is populated by one or more domain names.
• ETSI Specification Document TS 129 214 v7.4.0 (for "European Telecommunications Standards Institute"), entitled “Universal Mobile Telecommunications System (UMTS); Rx reference point "also describes a mechanism for prioritizing an IP flow within an application session between an application application entity (AF) and a PCRF entity (for” Policy and Charging "). Rules Function ”) via a" Reservation-Priority "attribute inserted into a Diameter message. This attribute makes it possible to indicate in a flow descriptor a relative priority for this flow within a session with which the latter is associated.
• the state of the art does not provide a mechanism for the application entity to determine or be aware of the existence of flow priority within the session relative to other possible flows of the session.
• the priority of a flow within a session is unknown to the control entities of the network, which does not allow the latter to take into account the importance of a flow relative to the other flows of the same session. network congestion, for example, or to transmit such information to other network entities. End-to-end processing of the priority of a stream is thus impossible to date.
• One of the aims of the invention is to remedy the shortcomings / disadvantages of the state of the art and / or to make improvements thereto.
• the invention relates to a method for prioritizing a media stream belonging to a plurality of media streams associated with a communication session, comprising:
• the prioritization method thus enables the control entity to obtain priority information relating to a media stream associated with a session from a session control message.
• This message is for example related to a session between a calling entity and a called entity, and received from the calling entity, the called entity or from an intermediary entity of the network located on a network path between the calling entity and the called entity.
• the method advantageously makes it possible to transmit the priority information from such an entity to the control entity.
• the message can also be directly generated by the control entity. This is particularly the case when this control entity is a user terminal. An end-to-end processing of this information from the sending entity of the session control message, or from the control entity if applicable, to the receiving media entity of the resource control message sent by the entity control is thus offered.
• the method makes it possible, for example, in the event of network congestion, to preempt a particular media stream in favor of other flows associated with the session.
• the method also makes it possible to favor the sending of a particular stream according to its type.
• the method makes it possible, for example, to process a video surveillance video marked with a high priority in the session control message, in priority with respect to other streams (eg video and audio streams of a videoconference) of the session marked with a lower priority.
• the method makes it possible, for example, to take into account a low priority associated with an audio stream of a videoconference held in sign language between hearing impaired participants by the control entity of the network.
• the method further comprises a modification of the priority information prior to its insertion in the resource control message.
• the method thus enables the controlling entity to directly intervene on the respective priorities assigned to the flows of the session.
• These priorities are, for example, redefined or deleted by the control entity according to flow information (e.g. flow content, flow user, feed source) or network information.
• a zero priority can advantageously be associated with the audio stream by the control entity of the network.
• a media entity of the network receiving the resource control message containing the priority information thus modified can thus decide not to transmit this stream. This can also result in a release of resources from the network.
• the modification of the priority information by the control entity also makes it possible to protect the network from the effects (eg saturation of the network) of a prioritization of one or more streams received from an unrecognized trusted entity issuing the session control message.
• the method notably makes it possible to prohibit or redefine the priorities of certain streams before transmission of the priority information to other entities of the network via the resource control message.
• the priority information is an attribute of a flow description included in an SDP offer or response associated with the session control message.
• an SDP message can easily be encapsulated in a control message of a higher layer protocol using the SDP protocol. It is not necessary to provide extensions to such a protocol to implement the method.
• MGCF Media Gateway Control Function
• IMS-MGW IP Multimedia Subsystem - Media Gateway
• the stream belongs to a plurality of media streams respectively associated with a flow description for the communication session.
• These flow descriptions are ordered in an SDP offer or response associated with the session control message, and the priority information is an ordered list of values, included in a header of the session control message, whose order corresponds to the order of flow descriptions in the SDP offer or response.
• the values then indicate a relative priority for each of the streams within the session in the order of the list.
• Obtaining the priority information from a header of the session control message makes it possible to group all the priorities relating to the flows of a session in one and the same place. In particular, it is possible to predetermine the priorities of the flows described in an SDP offer or response without prior analysis of this SDP offer or response.
• the session control message is a message
• the invention relates to a control entity, called a "primary control entity", in a communication network, arranged to prioritize a media stream belonging to a plurality of media streams associated with a communication session.
• the controlling entity includes:
• a obtaining module and / or a generation module arranged to obtain from a session control message, or to generate, priority information indicating a relative priority of the flow within the session with respect to the others; flow of the plurality of media streams; and
• an insertion module arranged to insert the priority information into a resource control message intended for a media entity.
• control entity further comprises a modification module, arranged to modify the priority information prior to its insertion into the resource control message by the insertion module.
• the obtaining module is arranged to obtain the priority information from an SDP offer or response included in the session control message.
• the priority information is then an attribute of a flow description included in the SDP offer or response.
• the control entity comprises a reception module, arranged to receive a session control message comprising an offer or an SDP response, said SDP offer or response comprising an ordered list of descriptions of the streams. associated with the session, and the obtaining module is arranged to obtain the priority information from a header of the session control message, this priority information being an ordered list of values included in the header, ordered in the same order as the flow descriptions associated with the session.
• the control entity further comprises a determination module, arranged to determine, from the ordered list of values, and from the ordered list of flow descriptions associated with the session, a relative priority for each of the flows within the session according to the order of the lists.
• the invention relates to a control entity, called a "secondary control entity", in a communication network, implementing session control signals, comprising:
• a generation module arranged to extract and modify from a session control message, or to generate, priority information indicating a relative priority of a flow within a communication session, with respect to other streams of a plurality of media streams associated with the session;
• the invention relates to a media entity, in a communication network, capable of retrieving, from an H.248 resource control message received from a control entity according to any of the characteristics of the second aspect, priority information indicating a relative priority of a stream within a communication session, relative to other streams of a plurality of media streams associated with the session.
• the invention also relates to a program for a control entity, comprising program code instructions for controlling the execution of the steps of the prioritization method described above, when the program is executed by the control entity.
• control and a computer-readable recording medium on which is recorded a computer program comprising program code instructions for performing the steps of the prioritization method described above.
• FIG. 1 shows two IMS communication networks (for "IP Multimedia Subsystem") according to a particular embodiment
• FIG. 2 represents steps of a prioritization method of a media stream, implemented by entities of an IMS communication network according to a particular embodiment
• FIG. 3 shows a control entity, called "secondary control entity", according to a particular embodiment
• FIG. 4 shows a control entity, called "primary control entity", according to a second particular embodiment.
• FIG. 1 represents two IMS communication networks 100 and 200 in which control entities according to the invention implement a method for prioritizing one or more media streams associated with a session between a calling user terminal 10 and a user terminal. called 20.
• An IMS network architecture as defined by the 3GPP standardization group (for 3rd "Generation Partnership Project") allows the establishment and control of multimedia sessions between user terminals, as well as the reservation of resources for flows Multimedia at the level of a data transport network. With this architecture, network operators can conveniently control the quality of service offered.
• the IMS architecture offers services such as telephony, video telephony, presence, instant messaging, or television, and also manages the interaction of these services. It typically implements the Session Initiation Protocol (SIP) as defined by the Internet Engineering Task Force (IETF) in RFC 3261 as the session management protocol, which allows the establishment, modification and termination of multimedia sessions in a network using the IP protocol.
• SIP Session Initiation Protocol
• IETF Internet Engineering Task Force
• the communication network 100 more particularly comprises control entities 30-33, and a both media and control entity 15.
• the communication network 200 comprises control entities 52, 53, and a media entity 40.
• the control entities and media entities are respectively entities capable of processing signaling messages relating to a communication session, and entities able to process the transport of data relating to a communication session.
• the control entities are said to belong to a control plane, while the media entities are said to belong to a media plan.
• control entity 30 is an application server AS (for example,
• control entity 31 is a PCRF (Policy Control and Charging Rules Function) control entity
• control entities 32 and 52 are P-CSCF proxy servers (for "Proxy - Call Server Control Function ")
• control entities 33 and 53 are entities grouping I-CSCF interrogation functions (for” Interrogating - Call Server Control Function ") and S-CSCF registration functions (for" Serving - Call Server Control Function ")
• the both media and control entity 15 is a PDN-GW gateway (for" Packet Data Network - Gateway ")
• media entity 40 is an IMS-AGW gateway (for "IMS-Access Gateway”).
• the entities of the network are implemented to manage the communication session between the calling user terminals 10 and 20 called.
• the calling user terminal 10 is subscribed to the communication network 100 to which it accesses via the PDN-GW gateway 15
• the called user terminal 20 is subscribed to the communication network 200.
• control entity 32 serves as a connection entity between the heart of the communication network 100 and the access network used by the calling user terminal 10, and is able to retransmit all the messages of signaling between the calling user terminal 10 and the control entity 33.
• the control entity 33 notably makes it possible to interrogate a subscriber server (not shown) in order to manage the registration procedure of the calling user terminal 10. It also makes it possible to request the control entity 30 for one or more services. associated with the communication session.
• the control entity 31 is responsible for adapting and controlling the use of the network resources of the communication network 100 by providing control rules for the session as a function, for example, of the services required by the calling user terminal 10 or its subscriber profile.
• the control entity 52 has a role equivalent to that of the control entity 32 in the communication network 200. It serves as a connection entity between the heart of the communication network 200 and the access network used by the user terminal called 20, and is able to retransmit all the signaling messages between the called user terminal 20 and the control entity 53.
• the control entity 52 also communicates with the media entity 40.
• the control entity 53 has a role equivalent to that of the control entity 33 in the communication network 200. It notably makes it possible to interrogate a subscriber server (not shown) in order to manage the registration procedure of the called user terminal 20.
• Diameter 1 signaling messages such as as defined in IETF RFC 4740.
• the exchanges between the control entity 52 and the media entity 40 are in turn supported by signaling messages 2 conforming to the H.248 protocol defined by the ITU-T ITU Working Group (for "Union Internationale of Telecommunications ").
• control entities 30 and 52 which will be respectively called “primary control entity” and “secondary control entity” respectively. This will be detailed later in connection with FIG.
• FIG. 1 is a simplified representation of the communication networks 100 and 200. No limitation is attached to the number of control entities and media entities belonging to the communication networks 100 and 200.
• control entities may be further grouped within the same entity.
• certain functions provided by the same entity may be separated and implemented by separate entities. This is for example the case of the I-CSCF interrogation and S-CSCF registration functions of the control entities 33 and 53.
• FIG. 2 represents steps of a prioritization method of a media stream, implemented by entities of an IMS communication network according to a particular embodiment. Subsequently, one places oneself in a network configuration such as that described with reference to FIG.
• the calling user terminal 10 sends a SIP session control message "INVITE" comprising an SDP offer to the communication network 200 to which the called user terminal 20 subscribes.
• This message is intended to establish a communication session between the calling user terminal 10 and the called user terminal 20.
• the SIP session control message "INVITE" sent for example has the following content: INVITE sip: [email protected] SIP / 2.0
• a header of the SIP session control message "INVITE" more particularly indicates that the communication session that the calling user terminal 10 wishes to establish is a videoconferencing session with subtitling. This is indicated by the "Contact" header of the SIP session control message "INVITE" which includes the value "VisioConferenceAvecSousTitration".
• the SDP offer contained in the SIP session control message "INVITE" further comprises three media flow descriptions each identified by the letter "m".
• the first description describes an audio stream, the second a video stream, and the third a stream of instant messaging.
• the SIP session control message "INVITE" does not contain any information relating to a priority of the flows associated with the communication session.
• the control entity 32 (a proxy server P-CSCF) receives the session control message "INVITE" transmitted by the calling user terminal 10.
• the control entity 32 then issues a request for reservation of media flows, for the three media streams of the SDP offer, with the control entity 31 (control entity PCRF rules).
• the media stream reservation request is more precisely a Diameter Resource Check message "AAR" (for "AA-Request”) as defined in RFC 4005.
• the control entity 31 sends an acknowledgment message of the stream reservation request to the control entity 32.
• This acknowledgment message is a Diameter resource control message "AAA” (for "AA-Answer") as defined in RFC 4005.
• the control entity 32 relays the SIP session control message "INVITE" to the control entity 33 (entity supporting I-CSCF interrogation and S-CSCF registration functions) .
• the control entity 33 receives the SIP session control message "INVITE", and determines from the header "Contact” including the value "VisioConferenceAvecSousTitrage", that a video conference service with subtitling is to be implemented.
• This service is provided by the primary control entity 30 (application server AS), and consists, for example, in real-time captioning in an instant messaging stream the words of a called user of the called user terminal 20 the language of a calling user of the calling user terminal 10.
• the language of the calling user is for example determined from his subscriber profile obtained from a subscriber server HSS (for "Home Subscriber Server") .
• the control entity 33 transmits the SIP session control message "INVITE" to the primary control entity 30.
• the primary control entity 30 receives the SIP session control message "INVITE" and identifies the three media streams contained in the SDP offer.
• a local flow prioritization policy at the primary control entity 30 provides that for this videoconferencing service with closed captioning, a video stream has a lower priority than an audio stream, the latter stream being itself of lower priority than an instant messaging stream associated with real-time subtitling.
• the primary control entity 30 applies the prioritization policy to the media streams contained in the SDP offer. For this, the primary control entity 30 generates priority information indicating a relative priority of each of the media streams within the session compared to other flows associated with the session.
• the value "0" corresponding to the minimum priority for a stream .
• the priority information thus indicates that the video stream has the lowest priority, that the audio stream is of higher priority than that of the video stream, and that the instant messaging stream has a higher priority than the other two streams of video. the session.
• the SIP session control message "INVITE" then contains a new SDP offer.
• the resulting "INVITE" SIP session control message has, for example, the following content:
• INVITE sip [email protected] SIP / 2.0
• the primary control entity 30 stores it pending an SDP response, and returns the SIP session control message. "INVITE" to the controlling entity 33.
• control entity 33 conveys the session control message
• control entity 53 then routes the SIP signaling control message "INVITE" to the secondary control entity 52 (proxy server of the communication network 200).
• the secondary control entity 52 inserts the priority information in an H.248 resource control message "Add Request", and sends it to the entity media 40 (IMS-AGW gateway of the communication network 200).
• the H.248 resource control message "Add Request” is for example a reservation request for three separate streams ("stream" in the H.248 resource control message) for each of the media streams of the SDP offer.
• the description of each of the media streams of the SDP offer containing the priority information is more precisely inserted in the H.248 resource check message "Add Request”.
• the H.248 resource check message "Add Request" has the following form:
• the media entity 40 receives the resource control message H.248 "Add Request”, and determines from the priority information contained in the message, the respective priorities of the media streams within of the communication session.
• the priority information is then known to the media entity 40, which can advantageously exploit it by implementing, for example, different queues to process the flows of the session with differentiated priorities.
• the media entity 40 after processing the H.248 resource control message "Add Request”, responds to the secondary control entity 52 with an H.248 "Add Reply" resource control message.
• the secondary control entity 52 transmits the SIP session control message "INVITE" to the called user terminal 20.
• the called user terminal 20 receives the SDP offer containing the priority information. It is thus informed of the priority of each stream associated with the session relative to the other streams.
• the called user terminal 20 applies one or more flow prioritization policies configured at the terminal.
• the called user terminal 20 generates, for example, a SIP session control message "200 OK" comprising an SDP response with valued attributes identical to those of the received SDP offer.
• the called user terminal 20 sends this SDP response to the secondary control entity 52.
• the content of the SIP session control message "200 OK" is for example the following: SIP / 2.0 200 OK
• the secondary control entity 52 receives the SDP response sent by the called user terminal 20 and sends an H.248 resource control message "Modify Request" to the media entity 40.
• the message H.248 resource control system "Modify Request” is used to inform the media entity 40 of the priorities associated with the flows of the session described in the SDP response.
• the H.248 resource control message "Modify Request” has the following content:
• a prio: 2
• the media entity 40 acknowledges the resource control message received in step E13 by sending a resource control message "Modify Reply" to the secondary control entity 52.
• step E15 the secondary control entity 52 relays the SIP session control message "200 OK" to the control entity 53, which itself relays it during a step E16 to the entity control 33 of the communication network 100.
• control entity 33 transmits the SIP session control message "200 OK" to the primary control entity 30.
• the latter then has the SDP offer stored in step E6 and the corresponding SDP response obtained from the SIP session control message "200 OK".
• the primary control entity 30 can then update, if necessary, the priority information contained in the SDP response. This is for example the case when the primary control entity 30 determines, from an element inserted by the called user terminal 20 in the session control message containing the SDP response in step E12, that the called user of the called user terminal 20 uses a language that turns out to be identical to that used by the calling user. Since the latter stream no longer has the same importance for the calling user (with few exceptions), the primary control entity 30 modifies the priority information so that the priority of the instant messaging stream is less than that of the stream. audio.
• the priority associated with the instant messaging flow for real-time video-conference captioning is decreased by decrementing its value by one unit, and the priority associated with the audio stream is increased by incrementing its value by one unit.
• the primary control entity 30 then returns a SIP session control message "200 OK" with an SDP response with the new priority information.
• control entity 33 transmits the SIP session control message "200 OK" to the control entity 32.
• a step E20 the control entity 32 receives the session control message "200 OK".
• the control entity 32 then issues a new media flow reservation request, for the three media streams of the SDP response, to the control entity 31.
• the reservation request for media streams, as well as to the step E2, is a Diameter Resource Control message "AAR”.
• the Diameter Resource Check message "AAR” further includes for each media stream of the session, a "Reservation-Priority" attribute valued with the new priority values associated with those streams in the SDP response.
• the Diameter "AAR" Resource Check message sent is for example: Diameter Protocol
• AVP Length ..
• AVP Vendor Id 3GPP (10415)
• step E21 the control entity 31 sends an acknowledgment message of the flow reservation request to the control entity 32.
• this acknowledgment message is a Diameter Resource Check message "AAA”.
• the control entity 32 transmits the SIP session control message "200 OK" to the calling user terminal 10.
• This message includes the relative priorities associated with each stream of the session as configured by the user.
• primary control entity 30 in step E18.
• the calling user terminal may optionally locally reuse the priority information contained in the SDP response, in order to implement priority processing of one or more streams relative to the other streams of the session.
• the priority information is directly inserted into a header of a SIP session control message, for example a "Flow-Priority" header, rather than in an SDP offer or response contained in this message.
• the priority information then corresponds to an ordered list of values whose order corresponds to the order of the flow descriptions associated with the session in the SDP offer or response contained in the SIP session control message.
• the values in the list then indicate a relative priority for each of the streams within the session in the order of the list. More precisely, at an nth flow description of an SDP offer or response corresponds the n-th priority value of the list of values associated with the "Flow-Priority" header.
• a SIP session control message "INVITE" has the following form: INVITE sip: [email protected] SIP / 2.0
• the called user terminal indicates in its SDP response valuated attributes different from those included in the SDP offer it has received.
• the called user terminal can thus propose a prioritization of the flows of the session different from that proposed or retained by a control entity or, where appropriate, by a media entity or a user terminal of one of the networks 100 or 200.
• a policy of prioritizing the media streams associated with the session is implemented by the calling user terminal 10 which indicates the priority information in the SDP offer sent to the step E1.
• step E6 the primary control entity 30, according to a predefined parameter setting, can then modify the prioritization of the media streams described in the SDP offer or still retain the priority information as indicated by the calling user terminal 10.
• the primary control entity 30 obtains the priority information indicating a relative priority of said flow within the session with respect to the other flows associated with the session, directly from the SIP session control message "INVITE " received.
• the primary control entity and the secondary control entity are the same entity.
• the controlling entity obtaining from a session control message, or generating, the priority information, also inserts this priority information into a resource control message.
• the secondary control entity 52 implements an optional step of modifying the priority information before inserting the latter into a resource control message in step E9.
• Priority information is, for example, modified according to an operator policy aimed at giving a lower priority to the most important flows. bandwidth consumers in case of network congestion.
• Identical processing can also be implemented by the control entity 32 in the communication network 100.
• the method has been described with implementation in two communication networks 100 and 200. There is however no limitation as to the number of communication networks in which the method is implemented. The method can for example easily be implemented in the same network for a communication session between subscriber terminals of this network.
• control entity there is also no limitation as to the control entities likely to implement the described method.
• a control entity belongs for example to the following group of control entities: entity P-CSCF (for "Proxy - Call Server Control Function"), entity I-CSCF (for "Interrogating - Call Server Control Function"), entity S-CSCF ("Serving - Call Server Control Function"), AS entity (for "Application Server”), MGCF entity (for "Media Gateway Controller Function"), IBCF entity (for "Interconnection Border Control Function”), user terminal .
• Such a media entity belongs, for example, to the following group of media entities: AGW entity (for "Access Gateway”), C-BGF entity (for "Core - Border Gateway Function"), P-GW entity (for "PDN Gateway”) ), MRFP entity (for "Multimedia Resource Function Processor”), TrGW entity (for "Transition Gateway”), user terminal.
• AGW entity for "Access Gateway”
• C-BGF entity for "Core - Border Gateway Function
• P-GW entity for "PDN Gateway”
• MRFP entity for "Multimedia Resource Function Processor”
• TrGW entity for "Transition Gateway”
• FIG. 3 represents a secondary control entity 52 arranged to prioritize a media stream belonging to a plurality of media streams associated with a communication session.
• the secondary control entity 52 comprises:
• a obtaining module 310 and / or a generation module 320 arranged to obtain from a session control message, or to generate, priority information indicating a relative priority of a flow within the session; relative to the other streams of the plurality of media streams; an insertion module 330, arranged to insert said priority information in a resource control message intended for a media entity.
• the control entity also comprises a modification module 340, arranged to modify the priority information prior to its insertion into the resource control message by the insertion module 330.
• the obtaining module 310 is arranged to obtain the priority information from an SDP offer or response included in the session control message, the priority information being an attribute of a flow description included in the SDP offer or response.
• control entity 52 comprises a reception module 350 arranged to receive a session control message comprising an offer or an SDP response.
• This SDP offer or response includes an ordered list of flow descriptions associated with the session.
• the obtaining module is also arranged to obtain the priority information from a header of the session control message. This header includes the priority information in the form of an ordered list of values. The values are ordered in the same order as the flow descriptions associated with the session.
• the control entity further comprises a determination module 360, arranged to determine, from the ordered list of values, and from the ordered list of descriptions of the flows associated with the session, a relative priority for each of the flows within of the session according to the order of the lists.
• FIG. 4 represents a primary control entity 30, in a communication network. This entity implements session control signals.
• the control entity 30 comprises:
• a generation module 410 arranged to extract and modify from a session control message, or to generate, priority information indicating a relative priority of a flow within a communication session, with respect to other streams of a plurality of media streams associated with the session;
• an insertion module 420 arranged to insert the information in a session control message to a secondary control entity.
• module may correspond in this document to both a software component, a hardware component or a set of hardware and / or software components, capable of implementing a function or a set of functions, as described above for the module concerned.
• a software component corresponds to one or more computer programs, one or more subroutines of a program, or more generally to any element of a program or software.
• Such a software component is stored in memory and then loaded and executed by a data processor of a physical entity and is capable of accessing hardware resources of this physical entity (memories, recording media, communication bus, input / output electronic boards, user interfaces, etc.).
• a material component corresponds to any element of a material set (or hardware). It may be a programmable hardware component or not, with or without an integrated processor for running software. This is for example an integrated circuit, a smart card, an electronic card for executing a firmware, etc.
• the modules 310, 320, 330, 340, 350 and 360 are arranged to implement the prioritization method described above.
• These are preferably software modules comprising software instructions for executing those of the steps of the prioritization method described above, implemented by a secondary control entity.
• the invention therefore also relates to:
• a program for a secondary control entity comprising program code instructions intended to control the execution of the steps of the previously described prioritization method, when said program is executed by said secondary control entity;
• a recording medium readable by a secondary control entity on which the program is recorded for a secondary control entity.
• modules 410 and 420 are arranged to implement the prioritization method described above.
• These are preferably software modules comprising software instructions for executing those of the steps of the prioritization method described above, implemented by a primary control entity.
• the invention therefore also relates to:
• a program for a primary control entity comprising program code instructions for controlling the execution of the steps of the previously described prioritization method, when said program is executed by said primary control entity;
• a recording medium readable by a primary control entity on which the program is recorded for a primary control entity.
• the software modules can be stored in or transmitted by a data carrier.
• a data carrier This may be a hardware storage medium, for example a CD-ROM, a magnetic diskette or a hard disk, or a transmission medium such as an electrical signal, optical or radio, or a telecommunications network.

Landscapes

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

Applications Claiming Priority (2)

Publications (1)

Family

ID=54260835

Family Applications (1)

Country Status (4)

Families Citing this family (5)

Family Cites Families (37)

• 2015
  • 2015-03-31 FR FR1552771A patent/FR3034608A1/fr not_active Withdrawn
• 2016
  • 2016-03-16 US US15/562,742 patent/US11223658B2/en active Active
  • 2016-03-16 EP EP16714490.6A patent/EP3278532A1/de not_active Ceased
  • 2016-03-16 WO PCT/FR2016/050584 patent/WO2016156694A1/fr active Application Filing

Also Published As

Similar Documents

Legal Events