Classifications

• • 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/30—Definitions, standards or architectural aspects of layered protocol stacks
  • H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
  • H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
  • H04L69/326—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the transport layer [OSI layer 4]
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L1/00—Arrangements for detecting or preventing errors in the information received
  • H04L1/004—Arrangements for detecting or preventing errors in the information received by using forward error control
  • H04L1/0056—Systems characterized by the type of code used
  • H04L1/0061—Error detection codes
• • 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

• the invention is located in communications networks, and more specifically in networks in which the data streams are routed using a stream transport protocol, such as the SCTP protocol (in English Stream Control Transport Protocol), these streams of data relating to multiple applications.
• a stream transport protocol such as the SCTP protocol (in English Stream Control Transport Protocol)
• SCTP in English Stream Control Transport Protocol
• the network architectures specified and deployed today are based on a layered communication system where each layer is responsible for a routing service.
• the Internet architectures commonly used for a variety of needs and services are based on the TCP/IP protocols (in English Transmission control Protocol/Internet Protocol) comprising a set of protocols.
• TCP/IP protocols in English Transmission control Protocol/Internet Protocol
• IP layer makes it possible in particular to reach a correspondent by using an IP address
• transport layer ensuring in particular the correct routing of data between two correspondents as well as the integrity of this data.
• the protocols UDP in English User Data Protocol
• TCP as well as the SCTP protocol specified in the document IETF RFC 4960 (September 2007) can be identified.
• This SCTP protocol notably has characteristics of reliability, redundancy, security and reliability that are particularly relevant for constrained services, such as IP telephony services.
• the transport protocols used in the networks carry data streams for various applications.
• the application data routed via the transport protocols, including the SCTP protocol are multiplexed using a common IP address and using a port number relating to the transport protocol associated with a specific application.
• a node 400 transmitting application data from applications App1, App2 to a node 410 transmits IP packets comprising the IP address (source) of the node 400, the IP address (destination) of the node 410, the port PS (source) of the transport protocol, the port (destination) of the SCTP transport protocol.
• the destination port used unambiguously identifies the application data transported over the transport protocol. Thereby, the data from the application App1 will be identified by a destination port PI, the data from the application App2 by a destination port P2.
• the transport layer routes multiple application data streams App1, App2 by differentiating these streams with specific port numbers P1 and P2.
• the node 410 is thus able to transmit the data received from the node 400 and relating to the applications App1, App2 to the entities in charge of the applications App1, App2 by analyzing the destination port used at the transport protocol SCTP level.
• the node 410 For each application deployed in networks, according to current techniques, especially when the application is used on the public Internet, it is necessary to allocate a transport protocol port. It is therefore necessary to request the IANA (https://www. iana.org/ assignments/ service-names-port-numbers/ service-names-port-numbers. xhtml) which allocates these ports.
• IANA https://www. iana.org/ assignments/ service-names-port-numbers/ service-names-port-numbers. xhtml
• the allocation procedures are increasingly strict, because IANA is afraid of having all the port numbers assigned and running out of port numbers. This makes it very difficult to obtain these port numbers.
• the object of the present invention is to provide improvements over the state of the art.
• the invention improves the situation with the aid of a method of routing data relating to an application transported in a data fragment of a packet of a stream transport protocol, such as the Stream protocol Control Transport Protocol, implemented by a multiplexing device able to transfer data relating to a plurality of applications to processing entities, and comprising the reception, from a terminal device, of the transport protocol packet of flow comprising a header containing a first destination port identifier common to the plurality of applications, and the data fragment comprising a second identifier specific to the application, the determination of the application according to the first and the second identifier received and in the case where the application is determined, the transmission of the data to an entity in charge of processing the data of the application.
• a stream transport protocol such as the Stream protocol Control Transport Protocol
• a multiplexing device receiving several packets of the transport protocol, such as SCTP can thus transfer the application data to the various entities in charge of receiving, processing, and possibly constructing a response according to the two identifiers present in the header and each of the fragments transporting the application data. For example, if two voice over IP and video over IP applications are activated, the switching device present for example in a voice over IP client, will receive the voice over IP and video over IP streams and will transmit the data from voice over IP to the process managing the voice over IP sessions and the video over IP data to the process managing the video over IP application, possibly deployed on a terminal other than the voice over IP client.
• the switching device present for example in a voice over IP client, will receive the voice over IP and video over IP streams and will transmit the data from voice over IP to the process managing the voice over IP sessions and the video over IP data to the process managing the video over IP application, possibly deployed on a terminal other than the voice over IP client.
• the multiplexing device comprises means for being able to analyze the identifiers received and on the other hand to determine whether the two identifiers correspond to an application for which the multiplexing device is able to manage the data.
• the routing process thus makes it possible to unambiguously differentiate data relating to several applications transported simultaneously on the same transport protocol.
• the routing method further comprises sending an error message to the terminal device in the event that an application is not determined.
• the terminal device can advantageously be informed of a problem of selection of identifiers, parameterization of identifiers, and/or of a compatibility problem of the referral device in order to be able, if necessary, to change the referral device, to initialize a new SCTP connection and/or verify one or other of the identifiers transmitted.
• the error message is a stream transport protocol packet comprising a fragment containing an Abort type error code.
• the error message comprises a cause of failure intended for the application implemented in the terminal device.
• the first destination port identifier is a port identifier dedicated to the referral method.
• the destination port identifier can be a port dedicated to the routing process, thus allowing the routing device to resort directly and without further examination of the packets to a routing process.
• a port dedicated to the routing process avoids problems of conflicting identifiers if the same identifier is used for two processes or two distinct applications.
• Such a dedicated port can thus be put implemented in a public network (Internet) or a private network (mobile network based on 3GPP specifications).
• the first destination port identifier is a port identifier already allocated for the TCPMux protocol.
• the TCPMux protocol already uses a specific port for the multiplexing of application streams on a TCP connection according to a method distinct from the routing process.
• the use of the same port identifier for the two methods has the advantage of simplifying the management of multiplexing services based on one or other of the protocols and process.
• the first destination port identifier is a port identifier allocated for an application based on the SCTP protocol.
• the first destination port identifier can be an identifier of an SCTP application, therefore an identifier already used for another need, making it possible not to have recourse to a specific identifier and thus preserving the identifiers to be used for the applications and processes. pressing SCTP.
• the invention also relates to a method for configuring a packet of a stream transport protocol such as the Stream Control Transport Protocol, the packet comprising a header and a data fragment, the method being implemented by a terminal device capable of transmitting data relating to an application to a multiplexing device, and comprising the parameterization of the packet with a first destination port identifier in the header and with a second identifier specific to the application in the data fragment, as well as the transmission to the multiplexing device of the configured packet.
• a stream transport protocol such as the Stream Control Transport Protocol
• the configuration method further comprises receiving an error message if no application is determined by the multiplexing device from the first identifier and the second identifier configured.
• the invention also relates to a routing device capable of transferring data relating to a plurality of applications to processing entities, one of the data being transported in a data fragment of a packet of a stream transport protocol , such as the Stream Control Transport Protocol, comprising
• a receiver capable of receiving from a terminal device, the stream transport protocol packet comprising a header containing a first destination port identifier common to the plurality of applications, and the data fragment comprising a second identifier specific to the application,
• a determination module able to determine the application according to the first and the second identifier received
• sender able to send the data to an entity in charge of processing the data of the application in the case where the application is determined.
• This device capable of implementing in all its embodiments the routing method which has just been described, is intended to be implemented in an application server, in a router of a communication network or of a intermediate equipment (DPI (Deep Packet Inspection) or firewall) or even in equipment of a mobile network (access gateway, server of an MEC (Mobile Edge computing) architecture).
• Device 100 can also be implemented in user equipment.
• the invention also relates to a device for configuring a packet of a stream transport protocol such as the Stream Control Transport Protocol, the packet comprising a header and a data fragment, comprising
• a configuration module able to configure the packet with a first destination port identifier in the header and with a second application-specific identifier in the data fragment
• a transmitter capable of transmitting the configured packet to a multiplexing device.
• This device capable of implementing in all its embodiments the configuration method which has just been described, is intended to be implemented in user equipment or else a gateway of a personal network. It can also be implemented in an application server, in a router of a communication network or in intermediate equipment (DPI (in English Deep Packet Inspection) or firewall) or else again in equipment of a mobile network (access gateway, server of an MEC architecture (in English Mobile Edge computing)).
• DPI in English Deep Packet Inspection
• MEC architecture English Mobile Edge computing
• the invention also relates to a system for routing data relating to an application transported in a fragment of a packet of a stream transport protocol, such as the Stream Control Transport Protocol, comprising
• a multiplexing device comprising a switching device
• a terminal device comprising a configuration device.
• the invention also relates to computer programs comprising instructions for implementing the steps of the respective routing and configuration methods which have just been described, when these programs are both executed by a processor and a recording medium respectively readable by a switching and configuration device on which the computer programs are recorded.
• the invention further improves the situation with the aid of a method of mediating a plurality of user applications through an application relating to the flow control transport protocol, such as the Stream protocol.
• Control Transport Protocol called generic application, the method being implemented in a proxy device, able to establish a connection based on the stream transport protocol with a terminal device, and comprising the reception from the terminal device of a packet flow control transport protocol request comprising a data fragment containing an identifier of a user application required by the terminal device, the verification that the requested user application is an application of the plurality, and in the event that the 'user application required is an application of the plurality, the transmission to the terminal device of an agreement message.
• the association of an SCTP connection between the terminal device and the proxy device is established by an exchange of INIT, INIT ACK, COOKIE-ECHO and COOKIE-ACK messages.
• the devices can exchange user application data.
• the method allows the exchange of data from various user applications (voice over IP, video over IP, monitoring, etc.) by resorting to a mediation application, or generic, implemented in a mediation device.
• the destination port of the SCTP protocol header is specific to this mediation application, saving ports that would be used to distinguish data from user applications, this destination port dedicated to the application generic is additionally used in SCTP messages exchanged during association establishment.
• the terminal device transmits a new and inventive SCTP request message, making it possible to interrogate the proxy device on its ability to mediate for the user applications whose identifiers it transmits. Only in the event that the proxy device is actually able to provide mediation for a user application, the terminal device can transmit data from the user application that the proxy device will be able to transmit to an application server, to a client data of the user application or to a process managing the user application deployed on the proxy server. The method therefore allows the terminal device to transmit user data with a guarantee of their processing by the proxy device and the proxy device to dynamically inform the terminal devices of its user data processing capabilities while also preserving the destination ports used for transporting user application data.
• the request packet further comprises a header containing a destination port identifier dedicated to the generic application.
• the identification of the received request packet is facilitated by the exploitation of the destination port present in the SCTP packets transmitted by the terminal device. Furthermore, in the case where a large number of user applications are managed by the proxy device, it may be advantageous to deploy several generic applications, and to distribute the mediation of the user applications over these different generic applications. In this case in particular, the use of the destination port present in the header of the received SCTP packet is particularly advantageous.
• the agreement message comprises at least one user application identifier of the plurality accessible from the generic application.
• the proxy device effectively relies on the received request message to inform the terminal device of its capabilities in terms of user applications for which it is mediating.
• the received request message can be used to transmit the list of identifiers of the user applications, independently of the identifiers received in the received request message, thus corresponding to a Push method implemented by the proxy device to inform the terminal device.
• the mediation method further comprises the reception from the terminal device of an application packet of the stream transport protocol comprising a data fragment containing the identifier specific to the user application required and application data specific to the requested user application, and the transmission to the required user application of the received application data.
• the terminal device for example a user equipment, uses the agreement message received and the information present in this message to send the application data using application protocols above SCTP to the proxy device and more specifically to the generic app.
• the advantage of the method is in particular for the terminal device to obtain application identifiers preventively (in push mode) allowing it to transmit data relating to these applications without requiring the sending of a new request message SCTP.
• the mediation method comprises sending a failure message to the terminal device in the event that the identifier of the required user application does not correspond to a user application of the plurality.
• the terminal device can advantageously be informed of a problem of selection of identifiers, parameterization of identifiers, and/or of a problem of compatibility of the proxy device, of availability of the generic application to receive data streams from user applications, in order to be able to change the proxy device, if necessary, initialize a new SCTP connection and/or check one or other of the identifiers transmitted, store the data of the user applications to be transmitted.
• the failure message is a stream transport protocol packet, comprising an Abort-type fragment terminating an association established between the terminal device and the proxy device.
• the failure message further comprises a cause of failure intended for the entity of the terminal device requesting the application.
• the invention also relates to a method for parameterizing a request packet of a stream control transport protocol, such as the Stream Control Transport Protocol, sent to a proxy device, the method being implemented by terminal device capable of communicating with the proxy device, and comprising the determination of a flow control transport protocol request packet, comprising a data fragment comprising identification data of a user application required by the terminal device, and the transmission to the proxy device of the determined request packet.
• a stream control transport protocol such as the Stream Control Transport Protocol
• the parameterization method further comprises the transmission to the proxy device of an application packet of the stream transport protocol comprising a data fragment containing an identifier specific to the required application and a application data specific to the required application.
• the determined request packet further comprises a header containing a destination port identifier dedicated to an application relating to the flow control transport protocol, referred to as a generic application.
• the invention also relates to a device for mediating a plurality of user applications via an application relating to a stream control transport protocol, such as the Stream Control Transport Protocol, referred to as a generic application, capable establishing a connection based on the stream transport protocol with a terminal device, and comprising
• a receiver capable of receiving a request packet from the terminal device the flow control transport protocol comprising a data fragment containing an identifier of a user application required by the terminal device,
• a verification module capable of verifying that the required user application is a plurality application
• a transmitter capable of transmitting to the terminal device an agreement message in the case where the required user application is an application of the plurality.
• This device capable of implementing in all its embodiments the mediation method which has just been described, is intended to be implemented in an application server, in a router of a communication network or of a intermediate equipment (DPI (Deep Packet Inspection) or firewall) or even in equipment of a mobile network (access gateway, server of an MEC (Mobile Edge computing) architecture).
• Device 100 can also be implemented in user equipment
• the invention also relates to a device for configuring a request packet of a stream control transport protocol, such as the Stream Control Transport Protocol, sent to a proxy device, implemented in a device terminal and comprising
• a determination module capable of determining a flow control transport protocol request packet, comprising a data fragment comprising identification data of a user application required by the terminal device
• This device capable of implementing in all its embodiments the parameter setting method which has just been described, is intended to be implemented in user equipment or else a gateway of a personal network. It can also be implemented in an application server, in a router of a communication network or in intermediate equipment (DPI (Deep Packet Inspection) or firewall) or even in equipment of a mobile network (access gateway, server of an MEC (Mobile Edge computing) architecture).
• DPI Deep Packet Inspection
• MEC Mobile Edge computing
• the invention also relates to a system for mediating a plurality of user applications via an application relating to a stream control transport protocol, such as the Stream Control Transport Protocol, referred to as a generic application, comprising - an agent device comprising a mediation device,
• a terminal device comprising a setting device.
• the invention also relates to computer programs comprising instructions for implementing the steps of the respective methods of mediation and parameterization which have just been described, when these programs are both executed by a processor and a recording medium readable respectively by a mediation and parameterization device on which the computer programs are recorded.
• the programs mentioned above may use any programming language, and be in the form of source code, object code, or intermediate code between source code and object code, such as in partially compiled form, or in n any other desirable shape.
• a medium may comprise a storage means, such as a ROM, for example a CD ROM or a microelectronic circuit ROM, or even a magnetic recording means.
• a storage means such as a ROM, for example a CD ROM or a microelectronic circuit ROM, or even a magnetic recording means.
• Such a storage means can for example be a hard disk, a flash memory, etc.
• an information medium can be a transmissible medium such as an electrical or optical signal, which can be conveyed via an electrical or optical cable, by radio or by other means.
• a program according to the invention can in particular be downloaded from an Internet-type network.
• an information carrier may be an integrated circuit in which a program is incorporated, the circuit being adapted to execute or to be used in the execution of the methods in question.
• FIG. 1 presents a simplified view of a communication between two nodes according to the prior art
• FIG 2 presents a simplified view of a communication between two nodes according to one aspect of the invention
• FIG 3 presents a simplified view of a communication between two nodes according to another aspect of the invention
• FIG 4 presents an overview of the method of routing data relating to an application and of the configuration method according to one embodiment of the invention
• FIG 5 presents an overview of the method of mediation of a plurality of applications via a generic application and the parameterization method according to an embodiment of the invention
• FIG 6 presents a device for routing data relating to an application according to one embodiment of the invention
• FIG 7 presents a device for configuring a stream transport protocol packet according to one embodiment of the invention
• FIG 8 presents a device for mediating a plurality of applications via a generic application according to one embodiment of the invention
• FIG 9 presents a device for parameterizing a packet flow control transport protocol according to an embodiment of the invention.
• FIG 2 presents a simplified view of a communication between two nodes according to one aspect of the invention.
• a node 100 transmits application data from the applications App 1 , App2 to a node 110, and sends IP packets comprising the IP address ( source) of the node 100, the IP address (destination) of the node 110, the port PS (source) of the transport protocol SCTP, the port (destination) of the transport protocol SCTP and application data relating to the applications App1 and App2.
• the nodes 100 and 110 can be either terminals, servers, telephony and/or videophone communication equipment, routing and/or communication network management entities.
• the applications App1 and App2 can be applications allowing users of the nodes 100 and 110 to access value-added services, applications for managing a communication network, or indifferently any application whose data is transported on an Internet network. Only two applications Appl and App2 are represented in [Fig 1] and [Fig 2] but there are no a priori limits as to the number of applications that can benefit from the referral process.
• the SCTP protocol used for transporting the data of the App1 and App2 applications comprises a header comprising the source port PS and the destination port PO.
• the destination port PO is common to the two applications Appl and App2 and therefore does not make it possible to differentiate the Appl and App2 application data.
• the node 110 corresponding to a multiplexing device comprising a routing device cannot differentiate the data from the App1 and App2 applications by simply reading and interpreting the destination port of the protocol header SCTP.
• other information present in a data fragment (in English DATA Chunk) of the SCTP packet is used in addition to the destination port PO .
• This information is a PPI1 (Payload Protocol Identifier 1) identifier present in each data fragment of the SCTP protocol.
• the multiplexing device is capable of routing the data of the application Appl, corresponding to the identifiers PO - PPI1, to the entity in charge of the Appl application.
• the node 110 Upon receipt of a packet comprising the two identifiers PO and PPI1, the node 110, able to analyze the SCTP packets, verifies that these identifiers correspond to applications for which it can route the data and if so, it transmits the data to the Appl application.
• the Appl application here corresponds to a physical or software entity able to manage the data of the Appl application.
• the data of the application App1 relates to a voice over IP service
• the data of the application can be transferred to a software entity present on the node 110 or else to another physical entity possibly by using a communication protocol between the node 110 and this other physical entity different from the SCTP protocol.
• the node 110 receives an SCTP packet comprising a header containing a destination port PO and a fragment comprising an identifier PPI2
• the application App2 corresponding to the identifiers PO and PPI2 is part of the applications multiplexed by the node 110, then it transmits the data from the application App2 to the entity in charge of the application App2.
• the implementation of the invention presented in [Fig 2] is symmetrical and the nodes 100 and 110 can be switched, the node 100 being able to correspond to the multiplexing device and the node 110 to a terminal device. Both nodes 100 and 110 can thus comprise multiplexing devices, each node 100 and 110 being able to comprise a configuration device and a multiplexing device. During a two-way communication, one of the two nodes acts as the multiplexing device and the other node acts as the configuration device.
• the application data transmitted by the node 110 or via the node 110 to the destination of the node 100 are transmitted in SCTP packets in accordance with the specifications of the protocol, in particular by using the information source IP address, destination IP address, source port and destination port.
• an error message is transmitted to node 100.
• this message can advantageously be an SCTP packet comprising an Abort error code.
• the error message can also include a failure code allowing the node 100 to identify the cause, depending on whether it is a bad formation of the SCTP packet transmitted to the node 110 or even that the node 110 n has not been correctly selected or even that the identifiers have not been correctly positioned.
• the first destination port identifier positioned in the header of the SCTP protocol is a port dedicated to the multiplexing process facilitating the processing to be performed on the packet received for the node 110.
• the dedicated port used as the first identifier may be port number 1 used in particular by the TCPMux protocol, specified in document IETF RFC 1078, thus making it possible to identify a common multiplexing port for a variety of transport protocols.
• the first destination port identifier corresponds to a port already used for an application based on SCTP, for example assigned by the IANA, thus avoiding having to resort to a new destination port number .
• FIG 3 presents a simplified view of a communication between two nodes according to another aspect of the invention.
• a node 300 transmits application data from the applications App1, App2 to a node 310, corresponding to a proxy device, and transmits IP packets comprising the (source) IP address of node 300, the IP address (destination) of the node 310, the port PS (source) of the transport protocol SCTP, the port (destination) of the transport protocol SCTP and application data relating to the applications App1 and App2.
• an application AppM relating to the SCTP protocol referred to as a generic application, is also deployed on the node 310.
• the applications App1 and App2 can, according to one example, be implemented in equipment separate from the node 310 .
• the SCTP protocol used for transporting the data of the App1 and App2 applications comprises a header comprising the source port PS and the destination port PM.
• the destination ports for PI and P2 recall
• the destination port PO although common to the two applications Appl and App2
• the destination port PM of the SCTP protocol unambiguously identifies the generic application AppM.
• all SCTP association packets comprising the destination port PM are routed to the AppM application.
• the PM port is certainly specific to the generic application, but since only one port is required, responding to the problem of port availability.
• the node 310 Independently of the application App1 and App2 recipients of the packets sent to the node 310, these are routed to the application AppM and therefore does not make it possible to differentiate the data of the applications App1 and App2.
• the node 310 through the application AppM, comprises a mediation device for the data flows intended for the user applications App1 and App2.
• the node 310 on receipt of the SCTP request packets, uses an identification data item, respectively RPPI1 (Required Payload Protocol Identifier 1) and RPPI2 corresponding to application identifiers App1 and App2 required by the node 100
• RPPI1 Required Payload Protocol Identifier 1
• RPPI2 corresponding to application identifiers App1 and App2 required by the node 100
• These identifiers transmitted in a single request message or in two separate request messages are present in the fragments of the SCTP protocol to verify that the applications App1 and App2 are indeed part of the applications for which the proxy node 310 mediates. If so, the node 310 transmits an agreement message, for example using the SCTP protocol, to the node 300 the information that an SCTP connection for the Appl application can be operated between the node 300 and the node 310, this connection being operated via the generic application AppM.
• the node 310 can also use the destination port identifier PM in addition to the required user application identifiers (here RPPI1 and RPPI2) to verify that the user applications App1 and App2 determined from these identifiers are part of the applications for which the proxy node 310 mediates.
• RPPI1 and RPPI2 required user application identifiers
• the agreement message includes an identifier PPI1 (respectively PPI2) corresponding to the application for which the success message is transmitted to the node 100 and which can be used to mark the fragment comprising the data of the application Appl (respectively App2) transmitted to node 310 when sending this data to node 310.
• PPI1 identifier 1
• Appl application Appl
• the node 300 transmits to the node 310, an SCTP packet comprising the header containing the destination port PM and an identifier PPI1 (respectively PPI2) corresponding to the application Appl (respectively PPI2) obtained in the message from response received or else stored in the node 300.
• the node 310 Upon receipt, in accordance with the success message transmitted, the node 310 transmits the application data relating to the application App1 (respectively App2) to the application App1 (respectively App2) or to the entity in charge of receiving and processing this application data present in the SCTP fragments.
• a failure message is transmitted to the node 300 thus indicating to it that the node 310 is not able to to receive and, if necessary, to transfer to a separate entity, the data relating to the Appl application for which the node 310 has been requested via the association packet received.
• the success message comprises all of the identifiers, for example PPI1 and PPI2, of the applications for which the node 310 mediates independently of the identifiers of the user applications requested by the node 300.
• nodes 300 and 310 can include both devices, namely the end device and the mediator device, and use them depending on which node initiates the SCTP connection.
• two nodes 100 and 110 communicate for example via a communication network, such as the Internet network, an infrastructure mobile, a corporate network or any type of infrastructure allowing the node 100 and the node 110 to exchange SCTP packets.
• a communication network such as the Internet network, an infrastructure mobile, a corporate network or any type of infrastructure allowing the node 100 and the node 110 to exchange SCTP packets.
• the node 100 comprising a configuration device, transmits an SCTP INIT message to the node 110.
• This SCTP message more specifically comprises an INIT control fragment to establish an association with the node 110.
• node 110 transmits during step 210 to node 100 an SCTP INIT ACK message to node 100 during step 210.
• This message includes in particular an INIT control fragment ACK as well as Cookie State information.
• the node 100 In response to the SCTP INIT ACK message received, the node 100 sends a COOKIE-ECHO response SCTP message to the node 110 during step 220.
• This message makes it possible to finalize the SCTP association between the nodes 100 and 110, initialized by node 100.
• the message includes a fragment containing the Status Cookie value received in the SCTP INIT ACK message.
• the node 110 transmits during step 230 an SCTP COOKIE-ACK message after having verified the authenticity of the value of the received cookie state.
• This COOKIE-ACK message acknowledges the COOKIE-ECHO message and the SCTP session is effectively established between node 100 and node 110 once this message has been received by node 100.
• the node 100 sends application data relating to an App1 application to the node 110 during a step 240. More specifically, the SCTP message sent by the node 100 comprises a header whose port destination is a port not specific to an application but a port common to a set of applications. The SCTP message further comprises at least one fragment comprising an identifier of the Appl application, such as a sequence of characters identifying the App 1 application, as well as application data intended for a process or an entity in charge of receiving, process, and send application data Appl.
• an identifier of the Appl application such as a sequence of characters identifying the App 1 application
• the node 100 from a configuration device, during a step 235, configures the SCTP packet comprising the header and the at least one fragment, and transmits, during step 240, the packet configured for node 110, this node 110 comprising a referral device.
• the node 110 comprising the routing device, verifies during a step 245 that the destination port identifier and the identifier of the application received in the SCTP packet correspond to an application for which the routing device is routing the application data, and if so, the device switch sends the application data of the application Appl to the entities in charge of the application Appl.
• the node 110 transmits an error message, for example an SCTP message comprising an ABORT fragment to the node 100 during a step 250.
• FIG 5 presents an overview of the method of mediating a plurality of applications via a generic application and of the parameterization method according to one embodiment of the invention.
• the first four steps 500, 510, 520, 530 are equivalent to the respective steps 200, 210, 220, 230 except that the destination port of the message header 300 and 320 is a source port corresponding to an application generic SCTP mediation.
• the nodes 300 and 310 have established an SCTP session based on a generic mediation application.
• the node 300 parameters an SCTP packet with a header comprising the destination port corresponding to a generic mediation application and with a data fragment comprising application identifiers required by the device 300. identifiers required corresponds to identifiers for which the node 300 wishes to know whether the generic application mediates for the application data of the applications corresponding to these identifiers.
• the node 300 transmits to the node 310 an SCTP request message whose header contains the destination port configured with an identifier of the generic application, and at least one fragment comprising one or several identifiers of user applications required by the node 300.
• the node 300 by this message, indicates to the node 310 that it wishes to know if the node 310 agrees to receive data and to transmit them to software entities present on the node 310 or to nodes distinct from node 310 for one or more user applications whose identifier or identifiers are found in the fragment of the SCTP request packet.
• Node 300 can choose to transmit one request message per user application or to transmit one request message for a set of user applications.
• the node 310 Upon receipt of the request message, the node 310 examines during a step 545 if it is mediating for the identifier or identifiers received and transmits to the node 300 during a step 550, in response to the request message , an agreement message indicating at node 300 that it is able to receive SCTP messages for the user application or user applications whose identifier or identifiers have been received. In this favorable case, the node 300 can transmit during a step 560 SCTP packets comprising user data specific to the application or to one of the applications for which the node 300 has transmitted a success message.
• the node 310 can transmit during step 550 the list of identifiers corresponding to the applications for which it mediates via the application.
• the node 310 can also inform the node 300 of the applications for which it is mediating by transmitting their identifiers, independently of the identifier or identifiers received from the node 300.
• the node 310 may issue a failure message, for example including an ABORT fragment, if none of the identifiers received matches an application it is mediating, possibly terminating the SCTP session between node 300 and node 310.
• Such a device 100 can be implemented in user equipment or else a gateway of a personal network. It can also be implemented in an application server, in a router of a communication network or in intermediate equipment (DPI (Deep Packet Inspection) or firewall) or even in equipment of a mobile network (access gateway, server of an MEC (Mobile Edge computing) architecture).
• DPI Deep Packet Inspection
• MEC Mobile Edge computing
• the device 100 comprises a processing unit 1030, equipped for example with a microprocessor uP, and controlled by a computer program 1010, stored in a memory 1020 and implementing the determination method according to the invention.
• a computer program 1010 stored in a memory 1020 and implementing the determination method according to the invention.
• the code instructions of the computer program 1010 are by example loaded into a RAM memory, before being executed by the processor of the processing unit 1030.
• Such a device 100 comprises:
• a parameterization module 1001 capable of parameterizing the packet with a first destination port identifier in the header and with a second identifier specific to an application in the data fragment
• a transmitter 1002 capable of transmitting the configured packet to a multiplexing device.
• Such a device 110 can be implemented in an application server, in a router of a communication network or in intermediate equipment (DPI (Deep Packet Inspection) or firewall) or even in equipment of a mobile network (access gateway, server of an MEC (Mobile Edge computing) architecture).
• Device 100 can also be implemented in user equipment.
• the device 110 comprises a processing unit 1130, equipped for example with a microprocessor uP, and controlled by a computer program 1110, stored in a memory 1120 and implementing the determination method according to the invention.
• a computer program 1110 stored in a memory 1120 and implementing the determination method according to the invention.
• the code instructions of the computer program 1110 are for example loaded into a RAM memory, before being executed by the processor of the processing unit 1130.
• Such a device 110 comprises:
• a receiver 1101 capable of receiving from a terminal device, the stream transport protocol packet Paq comprising a header containing a first destination port identifier common to the plurality of applications, and the fragment of data comprising a second identifier specific to the application,
• a transmitter 1102 capable of transmitting the Don data to an entity in charge of processing the data of the application in the case where the application is determined.
• a device for parameterizing a flow control transport protocol packet according to one embodiment of the invention is presented.
• a device 300 also called a terminal device, can be implemented in user equipment or else a gateway of a personal network. It can also be implemented in an application server, in a router of a communication network or in intermediate equipment (DPI (Deep Packet Inspection) or firewall) or even in equipment of a mobile network (access gateway, server of an MEC (Mobile Edge computing) architecture).
• DPI Deep Packet Inspection
• MEC Mobile Edge computing
• the device 300 comprises a processing unit 3030, equipped for example with a microprocessor uP, and controlled by a computer program 3010, stored in a memory 3020 and implementing the determination method according to the invention.
• a computer program 3010 stored in a memory 3020 and implementing the determination method according to the invention.
• the code instructions of the computer program 3010 are for example loaded into a RAM memory, before being executed by the processor of the processing unit 030.
• Such a device 300 comprises:
• a determination module 3001 capable of determining a request packet Req of the flow control transport protocol, comprising a data fragment comprising identification data of a user application required by the terminal device,
• a transmitter 3002 capable of transmitting the determined request packet to the proxy device.
• Such a device 310 can be implemented in an application server, in a router of a communication network or in intermediate equipment (DPI (Deep Packet Inspection) or firewall) or even more so in equipment of a mobile network (access gateway, server of an MEC architecture (in English Mobile Edge computing)).
• Device 100 can also be implemented in user equipment.
• the device 310 comprises a processing unit 3130, equipped for example with a microprocessor uP, and controlled by a computer program 3110, stored in a memory 3120 and implementing the determination method according to the invention.
• a computer program 3110 stored in a memory 3120 and implementing the determination method according to the invention.
• the code instructions of the computer program 3110 are by example loaded into a RAM memory, before being executed by the processor of the processing unit 3130.
• Such a device 310 comprises:
• a receiver 3101 able to receive from the terminal device a request packet Req of the flow control transport protocol comprising a data fragment containing an identifier of a user application required by the terminal device,
• a verification module 3102 capable of verifying that the required user application is an application of the plurality
• a transmitter 3103 capable of transmitting to the terminal device an agreement message Acc in the event that the required user application is an application of plurality.

Landscapes

• Engineering & Computer Science (AREA)
• Computer Networks & Wireless Communication (AREA)
• Signal Processing (AREA)
• Computer Security & Cryptography (AREA)
• Data Exchanges In Wide-Area Networks (AREA)
• Two-Way Televisions, Distribution Of Moving Picture Or The Like (AREA)

Applications Claiming Priority (2)

Publications (1)

Family

ID=74125438

Family Applications (1)

Country Status (5)

Family Cites Families (5)

• 2020
  • 2020-10-23 FR FR2010883A patent/FR3115644A1/fr not_active Withdrawn
• 2021
  • 2021-10-14 EP EP21806010.1A patent/EP4233302A1/de active Pending
  • 2021-10-14 WO PCT/FR2021/051789 patent/WO2022084605A1/fr not_active Ceased
  • 2021-10-14 CN CN202180072482.XA patent/CN116391351A/zh active Pending
  • 2021-10-14 US US18/250,094 patent/US20240007549A1/en active Pending

Non-Patent Citations (4)

Also Published As

Similar Documents

Legal Events