WO2016019985A1 - Procédé, produit-programme d'ordinateur et appareil permettant une différentiation de flux de trafic - Google Patents

Procédé, produit-programme d'ordinateur et appareil permettant une différentiation de flux de trafic Download PDF

Info

Publication number
WO2016019985A1
WO2016019985A1 PCT/EP2014/066900 EP2014066900W WO2016019985A1 WO 2016019985 A1 WO2016019985 A1 WO 2016019985A1 EP 2014066900 W EP2014066900 W EP 2014066900W WO 2016019985 A1 WO2016019985 A1 WO 2016019985A1
Authority
WO
WIPO (PCT)
Prior art keywords
message
network element
priority level
tunnel
determined
Prior art date
Application number
PCT/EP2014/066900
Other languages
English (en)
Inventor
Rainer Liebhart
Giorgi Gulbani
Original Assignee
Nokia Solutions And Networks Oy
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 Nokia Solutions And Networks Oy filed Critical Nokia Solutions And Networks Oy
Priority to PCT/EP2014/066900 priority Critical patent/WO2016019985A1/fr
Publication of WO2016019985A1 publication Critical patent/WO2016019985A1/fr

Links

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/10—Architectures or entities
    • H04L65/1045—Proxies, e.g. for 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/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/1066—Session management
    • H04L65/1101—Session protocols
    • H04L65/1104—Session initiation protocol [SIP]

Definitions

  • the present invention relates to apparatuses, methods, systems, computer programs, computer program products and computer-readable media regarding distinction of signaling messages carried over the same bearer.
  • EPS is the Evolved Packet System, the successor of GPRS (General Packet Radio System). It provides new radio interface and new packet core network functions for broadband wireless data access.
  • EPS core network functions are the Mobility Management Entity (MME), Packet Data Network Gateway (P-GW) and Serving Gateway (S-GW).
  • MME Mobility Management Entity
  • P-GW Packet Data Network Gateway
  • S-GW Serving Gateway
  • Fig. 1 is a diagram illustrating the EPS architecture as defined in 3GPP TS 23.401 . Since this architecture is well-known by the skilled person, a detailed description thereof is omitted here and it is referred to 3GPP TS 23.401 for further details.
  • a common packet domain Core Network is used for all Radio Access Networks (RAN), GERAN (GSM (Global System for Mobile Communication) EDGE (Enhanced Data rates for GSM Evolution) RAN), UTRAN (UMTS (Universal Mobile Telecommunication System) Terrestrial Radio Access Network) and E-UTRAN (Enhanced UTRAN).
  • RAN Radio Access Networks
  • GSM Global System for Mobile Communication
  • EDGE Enhanced Data rates for GSM Evolution
  • UTRAN Universal Mobile Telecommunication System
  • E-UTRAN Enhanced UTRAN
  • the PCC (Policy and Charging Control) architecture including DPI (Deep Packet Inspection) functionality in TDF (Traffic Detection Function) and PCEF (Policy and Charging Enforcement Function) enhanced with ADC (Application Detection and Control) rules, extends the architecture of an IP-CAN (Internet Protocol Connectivity Access Network), where the PCEF is a functional entity in the gateway node (PGW or GGSN) implementing the IP access to the PDN (Packet Data Network).
  • An example for an Application Function (AF) is the P-CSCF (Proxy Call Session Control Function) that is part of the IP Multimedia Subsystem (IMS) or any other application proxy and server function within the IMS or other application domains.
  • IMS IP Multimedia Subsystem
  • Fig. 2 is a diagram illustrating the overall PCC architecture (roaming with home routed access) when SPR (Subscription Profile Repository) is used, as defined in 3GPP TS 23.203. Since the overall PCC architecture is well-known by the skilled person, a detailed description thereof is omitted here and it is referred to 3GPP TS 23.203 for further details.
  • VoLTE Voice over Long Term Evolution
  • non- VoLTE signaling messages in case the UE (User Equipment) is idle.
  • a SIP (Session Initiation Protocol) INVITE message that triggers establishment of a voice call shall trigger a more "aggressive" paging (e.g. paging in a wider area as usual) of the UE than SIP MESSAGE or SIP NOTIFY messages.
  • SIP MESSAGE or SIP NOTIFY messages SIP MESSAGE or SIP NOTIFY messages.
  • the UE is transferred in most cases much faster from idle to connected mode, paging re-transmissions are avoided and voice calls are also established faster.
  • any other IMS service can also be considered for special paging.
  • the AF/P-CSCF marks SIP messages with different DSCP (Differentiated Services Code Point) value, e.g. the first TCP-SYN (Transmission Control Protocol Synchronization) followed by a SIP INVITE is marked with a different DSCP value than the TCP-SYN followed by a SIP MESSAGE.
  • SGW recognizes the DSCP value and provides a proper indication to MME within the DDN (Downlink Data Notification). Based on this indication in the DDN, MME can page the UE in different ways.
  • a method comprising: determining, at the first network element, a priority level of a message to be transmitted to a second network element, and
  • an apparatus for use in a network element comprising:
  • At least one memory for storing instructions to be executed by the processor, wherein the at least one memory and the instructions are configured to, with the at least one processor, cause the apparatus at least to perform:
  • an apparatus comprising:
  • a computer program product comprising code means adapted to produce steps of any of the methods as described above when loaded into the memory of a computer.
  • a computer program product as defined above, wherein the computer program product comprises a computer- readable medium on which the software code portions are stored.
  • Fig. 1 is a diagram illustrating the EPS architecture
  • Fig. 2 is a diagram illustrating the overall PCC architecture
  • Fig. 3 is a diagram illustrating an example of two communication paths between AF/P-CSCF and PGW/GGSN for high- and low-priority messages according to certain aspects of the present invention
  • Fig. 4 is a flowchart illustrating an example of a method according to certain aspects of the present invention.
  • Fig. 5 is block diagram illustrating an example of an apparatus according to certain aspects of the present invention. Detailed Description
  • the basic system architecture of a communication network may comprise a commonly known architecture of one or more communication systems comprising a wired or wireless access network subsystem and a core network.
  • Such an architecture may comprise of one or more communication network control elements, access network elements, radio access network elements, access service network gateways or base transceiver stations, such as a base station (BS), an access point or an eNodeB, which control a respective coverage area or cell and with which one or more communication elements or terminal devices such as a UE or another device having a similar function, such as a modem chipset, a chip, a module etc., which can also be part of a UE or attached as a separate element to a UE, or the like, are capable to communicate via one or more channels for transmitting several types of data.
  • core network elements such as gateway network elements, policy and charging control network elements, mobility management entities, operation and maintenance elements, and the like may be comprised.
  • the communication network is also able to communicate with other networks, such as a public switched telephone network or the Internet.
  • the communication network may also be able to support the usage of cloud services.
  • BSs and/or eNodeBs or their functionalities may be implemented by using any node, host, server or access node etc. entity suitable for such a usage.
  • the described network elements and communication devices such as terminal devices or user devices like UEs, communication network control elements of a cell, like a RNC or an eNodeB, access network elements like APs and the like, as well as corresponding functions as described herein may be implemented by software, e.g. by a computer program product for a computer, and/or by hardware.
  • nodes or network elements may comprise several means, modules, units, components, etc. (not shown) which are required for control, processing and/or communication/signaling functionality.
  • Such means, modules, units and components may comprise, for example, one or more processors or processor units including one or more processing portions for executing instructions and/or programs and/or for processing data, storage or memory units or means for storing instructions, programs and/or data, for serving as a work area of the processor or processing portion and the like (e.g. ROM, RAM, EEPROM, and the like), input or interface means for inputting data and instructions by software (e.g. floppy disc, CD-ROM, EEPROM, and the like), a user interface for providing monitor and manipulation possibilities to a user (e.g. a screen, a keyboard and the like), other interface or means for establishing links and/or connections under the control of the processor unit or portion (e.g.
  • radio interface means comprising e.g. an antenna unit or the like, means for forming a radio communication part etc.) and the like, wherein respective means forming an interface, such as a radio communication part, can be also located on a remote site (e.g. a radio head or a radio station etc.).
  • a remote site e.g. a radio head or a radio station etc.
  • AF Application Function
  • PGW/GGSN Packet Control Function
  • GTP-U GPRS Tunneling Protocol User Plane
  • Option 1 Usage of tunneling (additional encapsulation of packets or frames)
  • a first option according to certain aspects of the present invention proposed the usage of tunneling (additional encapsulation of packets or frames).
  • a Layer 2 (L2), a Layer 3 (L3) or a Layer 3 and Layer 4 (L3/L4) tunnel for high-priority signaling can be established. If a more fine-granular separation is required, more tunnels (several tunnels for different priority levels) are also possible.
  • tunnels Possible examples for tunnels are L2 tunnels like Virtual LANs, L3 tunnels like IP-in-IP, GRE (Generic Routing Encapsulation) and L3/L4 tunnels like IP/UDP tunnels. It is noted that other L2, L3, L3/L4 or other tunneling mechanisms are not excluded.
  • NSH Network Service Header
  • AF e.g. P- CSCF
  • PGW/GGSN PGW/GGSN
  • IP/UDP/SIP where "IP” denotes the Internet Protocol header carrying the UE's IP address), i.e. without any changes to the existing procedures (i.e. no tunneling is applied).
  • "high-priority" signaling messages are delivered to PGW/GGSN with additional encapsulation (e.g. L3 encapsulation: IP-1/IP-2/UDP/SIP or IP-1/GRE/IP-2/UDP/SIP, etc., where IP-1 denotes the encapsulating, or outer IP header and IP-2 denotes the inner IP header of the original SIP message) (cf. Fig. 3).
  • L3/L4 encapsulation would be IP-1/UDP- 1/IP-2/UDP-2/SIP, etc., where IP-1 and UDP-1 denote the encapsulating, or outer IP/UDP header and IP-2/UDP-2 denote the inner IP/UDP header of the original SIP message.
  • PGW/GGSN can discriminate signaling messages by looking into the destination IP address and in case of L3/L4 tunneling, by also checking the port number.
  • the destination IP address will be UE's IP address (which is advertised by PGW/GGSN to the routers across to Gi/SGi interface), while high-priority SIP messages can use dedicated PGW/GGSN IP addresses as destination address in the outer IP header.
  • high-priority SIP messages can use a dedicated port number in the outer Layer 4 header (e.g. in the UDP header).
  • high-priority SIP messages can be marked with a special GRE key that is known to both PGW/GGSN and AF/P-CSCF.
  • extension headers in the outer IP header can be used to indicate high-priority SIP messages.
  • the tunnels for high-priority SIP messages can be encrypted (e.g. by using IPSec or SSH).
  • PGW/GGSN When PGW/GGSN receives a tunneled packet (i.e. high priority signaling message) from AF/P-CSCF, it must determine the priority of the received SIP signaling message, which is known by the outer, tunnel specific address and port number and potentially GRE key, NSH header or any other information specific to the used tunnel mechanism. PGW/GGSN needs to strip off the additional, tunnel specific header(s) before forwarding the original SIP message to SGW/SGSN within a GTP-U tunnel (for GTP based S5/S8 or for Gn/Gp interfaces) or within a GRE tunnel (for PMIP (Proxy Mobile Internet Protocol) based S5/S8 interfaces).
  • GTP-U tunnel for GTP based S5/S8 or for Gn/Gp interfaces
  • PMIP Proxy Mobile Internet Protocol
  • PGW/GGSN shall send this information in a new or existing GTP-U header to SGW/SGSN; SGW forwards the information to MME in a way that is not defined in this invention.
  • SGW forwards the information to MME in a way that is not defined in this invention.
  • no tunneling is required, i.e. PGW/GGSN need not add extra IP or other headers to SIP messages towards AF/P- CSCF.
  • Option 1 is the most preferred solution, because it works also if SIP messages are encrypted. From option 1 , the simplest solution would be if AF/P-CSCF adds another IP header before sending a high priority SIP message. This implies PGW/GGSN must be configured with one or more special IP addresses (in case of L3/L4 tunneling with special IP addresses and special port numbers). Therefore, each of the high priority SIP messages from AF/P-CSCF should use a dedicated destination IP address and possibly also a port number configured in PGW/GGSN and AF/P-CSCF.
  • each AF/P-CSCF gets such IP addresses and port numbers for all PGW/GGSNs it can send packets to, so that both the ordinary SIP messages and the high priority SIP messages of the same UE end up in the same PGW/GGSN.
  • each priority level is mapped to a certain IP address and port number pair at the PGW/GGSN.
  • GRE GRE simplest solution is to use a special GRE key that indicates the actual priority for a high-priority SIP message. In the simplest case only one priority level is used but potentially also different priority levels can be applied with this method.
  • the above option includes splitting the interface between the PGW/GGSN and the AF/P- CSCF into two paths. This is a bigger functional change than a smart usage of certain fields in different protocol headers. In both cases however AF/P-CSCF must identify high priority SIP messages and handle them differently before sending the messages to PGW/GGSN.
  • Splitting refers to the option to use a tunneling approach for the messages that have to be treated differently, while "normal" messages do not use this path (i.e. are not tunneled). So, the solution is backward compatible, and is not creating big overhead. It can be used for the IMS/VoLTE use case but also for other IMS services or other applications. Another advantage is also that PGW/GGSN supports usually e.g. GRE and other L2/L3 tunneling techniques and even additional information can be provided in extra tunnel specific headers. In the following, a more general description of certain embodiments of the present invention is made with respect to Figs. 4 and 5.
  • Fig. 4 is a flowchart illustrating an example of a method according to example versions of the present invention.
  • the method may be implemented in a gateway, or the like.
  • the method comprises determining, at the first network element, a priority level of a message to be transmitted to a second network element in a step S41 , and transmitting, by the first network element, a message for which the priority level has been determined, to the second network element via a tunnel corresponding to the determined priority level in a step S42.
  • the method further comprises transmitting a message for which no priority level has been determined or the priority has been determined as being at the lowest level directly to the second network element without using a tunnel.
  • a message with a certain priority level uses a dedicated address or a dedicated address and port number of the second network element as destination address or destination address and port of the message.
  • the method further comprises establishing a tunnel per priority level between the first network element and a second network element, and transmitting a message with a certain priority level to the second network element via the tunnel corresponding to the certain priority level.
  • the message with a certain priority level is transmitted according to the generic routing encapsulation protocol and a high priority message is marked with a special generic routing encapsulation key.
  • the message with a certain priority level is encapsulated in an internet protocol, IP, message and the priority of the message is indicated in an extension header of the IP header.
  • the message with a certain priority level is transmitted within a layer 2 tunnel.
  • the first network element is an application function or a proxy call session control function and the second network element is a packet data network gateway.
  • the priority level of a message is determined based on operator configuration.
  • each tunnel can be established at the time of configuring the first network element or at any time before a message needs to be sent by the first network element.
  • the priority levels are predefined at the first network element.
  • the first network element can set priority levels with a certain granularity in either ascending or descending order prior to determining the priority level of a message.
  • Fig. 5 is a block diagram showing an example of an apparatus according to example versions of the present invention.
  • a block circuit diagram illustrating a configuration of an apparatus 50 is shown, which is configured to implement the above described aspects of the invention.
  • the apparatus 50 shown in Fig. 5 may comprise several further elements or functions besides those described herein below, which are omitted herein for the sake of simplicity as they are not essential for understanding the invention.
  • the apparatus may be also another device having a similar function, such as a chipset, a chip, a module etc., which can also be part of an apparatus or attached as a separate element to the apparatus, or the like.
  • the apparatus 50 may comprise a processing function or processor 51 , such as a CPU or the like, which executes instructions given by programs or the like.
  • the processor 51 may comprise one or more processing portions dedicated to specific processing as described below, or the processing may be run in a single processor. Portions for executing such specific processing may be also provided as discrete elements or within one or further processors or processing portions, such as in one physical processor like a CPU or in several physical entities, for example.
  • Reference sign 52 denotes transceiver or input/output (I/O) units (interfaces) connected to the processor 51 .
  • the I/O units 52 may be used for communicating with one or more other network elements, entities, terminals or the like.
  • the I/O units 52 may be a combined unit comprising communication equipment towards several network elements, or may comprise a distributed structure with a plurality of different interfaces for different network elements.
  • Reference sign 53 denotes a memory usable, for example, for storing data and programs to be executed by the processor 51 and/or as a working storage of the processor 51 .
  • the processor 51 is configured to execute processing related to the above described aspects.
  • the apparatus 50 may be implemented in or may be part of a first network element, or the like, and may be configured to perform a method as described in connection with Figs 4.
  • the processor 51 is configured to perform determining, at the first network element, a priority level of a message to be transmitted to a second network element, transmitting, by the first network element, a message for which the priority level has been determined, to the second network element via a tunnel corresponding to the determined priority level.
  • a second option according to certain aspects of the present invention proposed the usage of IPv6 parameters.
  • IMS uses IPv6 as transport (this is the recommended standard IP version to be used) parameter fields like 'Flow Label', 'Next Header' and 'Traffic Class' can be used to carry information that allows to differentiate between different SIP messages.
  • the parameter field 'Flow label' was designed for differentiating various services, i.e. for enabling the labeling of packets belonging to particular traffic flows for which the sender requests special handling (cf. IETF RFC2460). Further, this document defines: "Hosts or routers that do not support the functions of the Flow Label field are required to set the field to zero when originating a packet, pass the field on unchanged when forwarding a packet, and ignore the field when receiving a packet".
  • the 'Next Header' parameter field which points to the upper layer protocol, is an 8-bit selector. It identifies the type of header immediately following the IPv6 header. It uses the same values as the IPv4 Protocol field (cf. IETF RFC2460). However, changing this to differentiate between various SIP message types may require IETF changes.
  • parameter field 'Traffic Class' has the same drawback as DSCP marking for IPv4, as described above.
  • Option 3 Usage of UDP/TCP/SCTP headers, if SIP signaling is not encrypted
  • a third option according to certain aspects of the present invention proposed the usage of
  • PGW/GGSN and AF/P-CSCF may exchange SIP messages on top of UDP, TCP or SCTP.
  • these sub-options may work only if SIP signaling is not encrypted between UE and AF/P-CSCF.
  • the source port is dynamically negotiated between UE and AF/P-CSCF, while the destination port is a well-known one (5060).
  • TCP header cf. IETF RFC 793
  • source/destination ports cannot be used, like in UDP case.
  • URG flag and Urgent pointer could be used for the purpose. This will work if TCP message carries only one TCP-SYN of an INVITE.
  • options field could also be used for the purpose in two ways: - Option-Kind (1 octet) indicates the exact SIP message priority;
  • Option-Kind (1 octet) indicates that the following Option-Data (variable length) contains the exact SIP message priority. In this case Option-Length (1 octet) should also be used.
  • TCP message carries only one SIP message and (b) if such specific value range is standardized by IETF and 3GPP.
  • SCTP is message-oriented like UDP and ensures reliable, in-sequence transport of messages with congestion control like TCP:
  • Source/destination ports cannot be used, like in UDP case.
  • Chunk Value contains a SIP message, which determines the Chunk Length value.
  • Chunk Length 4 indicates Chunk Value is not present and Chunk Flags should be set to 0.
  • option 1 the most appealing solution from the above options is option 1 , because (a) it does not have limitations specific to other options and (b) it works also if SIP messages are encrypted.
  • processor or corresponding circuitry potentially in cooperation with computer program code stored in the memory of the respective apparatus, is configured to cause the apparatus to perform at least the thus mentioned function.
  • function is to be construed to be equivalently implementable by specifically configured circuitry or means for performing the respective function (i.e. the expression "unit configured to” is construed to be equivalent to an expression such as "means for").
  • any method step is suitable to be implemented as software or by hardware without changing the idea of the aspects/embodiments and its modification in terms of the functionality implemented;
  • CMOS Complementary MOS
  • BiMOS Bipolar MOS
  • BiCMOS Bipolar CMOS
  • ECL emitter Coupled Logic
  • TTL Transistor-Transistor Logic
  • ASIC Application Specific IC
  • FPGA Field- programmable Gate Arrays
  • CPLD Complex Programmable Logic Device
  • DSP Digital Signal Processor
  • - devices, units or means can be implemented as individual devices, units or means, but this does not exclude that they are implemented in a distributed fashion throughout the system, as long as the functionality of the device, unit or means is preserved;
  • an apparatus may be represented by a semiconductor chip, a chipset, or a (hardware) module comprising such chip or chipset; this, however, does not exclude the possibility that a functionality of an apparatus or module, instead of being hardware implemented, be implemented as software in a (software) module such as a computer program or a computer program product comprising executable software code portions for execution/being run on a processor;
  • a device may be regarded as an apparatus or as an assembly of more than one apparatus, whether functionally in cooperation with each other or functionally independently of each other but in a same device housing, for example.
  • respective functional blocks or elements according to above- described aspects can be implemented by any known means, either in hardware and/or software, respectively, if it is only adapted to perform the described functions of the respective parts.
  • the mentioned method steps can be realized in individual functional blocks or by individual devices, or one or more of the method steps can be realized in a single functional block or by a single device.
  • any method step is suitable to be implemented as software or by hardware without changing the idea of the present invention.
  • Devices and means can be implemented as individual devices, but this does not exclude that they are implemented in a distributed fashion throughout the system, as long as the functionality of the device is preserved. Such and similar principles are to be considered as known to a skilled person.
  • Software in the sense of the present description comprises software code as such comprising code means or portions or a computer program or a computer program product for performing the respective functions, as well as software (or a computer program or a computer program product) embodied on a tangible medium such as a computer-readable (storage) medium having stored thereon a respective data structure or code means/portions or embodied in a signal or in a chip, potentially during processing thereof.

Landscapes

  • Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente invention concerne des appareils, des procédés, des programmes informatiques, des produits-programmes d'ordinateur et des supports lisibles par ordinateur se rapportant à la distinction des messages de signalisation transportés sur la même porteuse. Certains aspects de la présente invention consistent à déterminer, au niveau du premier élément de réseau, un niveau de priorité d'un message qui doit être transmis à un second élément de réseau, à transmettre, par le premier élément de réseau, un message pour lequel le niveau de priorité a été déterminé, au second élément de réseau par l'intermédiaire d'un tunnel correspondant au niveau de priorité déterminé ou à une adresse IP spécifique et, peut-être, un numéro de port spécifique.
PCT/EP2014/066900 2014-08-06 2014-08-06 Procédé, produit-programme d'ordinateur et appareil permettant une différentiation de flux de trafic WO2016019985A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/EP2014/066900 WO2016019985A1 (fr) 2014-08-06 2014-08-06 Procédé, produit-programme d'ordinateur et appareil permettant une différentiation de flux de trafic

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2014/066900 WO2016019985A1 (fr) 2014-08-06 2014-08-06 Procédé, produit-programme d'ordinateur et appareil permettant une différentiation de flux de trafic

Publications (1)

Publication Number Publication Date
WO2016019985A1 true WO2016019985A1 (fr) 2016-02-11

Family

ID=51302968

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2014/066900 WO2016019985A1 (fr) 2014-08-06 2014-08-06 Procédé, produit-programme d'ordinateur et appareil permettant une différentiation de flux de trafic

Country Status (1)

Country Link
WO (1) WO2016019985A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109450793A (zh) * 2018-12-18 2019-03-08 锐捷网络股份有限公司 一种业务流量调度的方法和装置

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7697422B1 (en) * 2006-01-17 2010-04-13 Marvell Israel (M.I.S.L.) Ltd. Quality of service marking techniques
US20140082114A1 (en) * 2012-09-18 2014-03-20 Avaya Inc. System and method for setting wireless message priority

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7697422B1 (en) * 2006-01-17 2010-04-13 Marvell Israel (M.I.S.L.) Ltd. Quality of service marking techniques
US20140082114A1 (en) * 2012-09-18 2014-03-20 Avaya Inc. System and method for setting wireless message priority

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
CHINA TELECOM, NSN: "ADDRESSING EN RELATED TO TUNNELLING BETWEEN PGW/GGSN AND AF", SA WG2 MEETING 103, 19 May 2014 (2014-05-19) - 23 May 2014 (2014-05-23), Phoenix, Arizona, Usa, pages 1 - 2, XP002737936 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109450793A (zh) * 2018-12-18 2019-03-08 锐捷网络股份有限公司 一种业务流量调度的方法和装置

Similar Documents

Publication Publication Date Title
US11051212B2 (en) Interworking with bearer-based system
WO2020177764A1 (fr) Procédé de garantie de transmission de données et dispositif de communication
US9614656B2 (en) Providing in-line services through radio access network resources under control of a mobile packet core in a network environment
US20180331952A1 (en) Mapping selective DSCP values to GTP-U
KR101792378B1 (ko) 모바일 통신 시스템에서 서비스 품질 제어의 지원
US8917615B2 (en) Method, apparatus and system for detecting service data of a packet data connection
US9979661B2 (en) Techniques for handling network traffic
EP2441211B1 (fr) Contrôle des performances dans un réseau de communication
US10581747B2 (en) System and method for low-overhead interoperability between 4G and 5G networks
EP2560430A1 (fr) Procédé et système pour obtenir une charge de réseau
WO2012149954A1 (fr) Décharge de trafic dans des réseaux de communication
US10432518B2 (en) Packet flow optimization in a network
US10367924B2 (en) Position-based communication routing
CN111567082A (zh) Lte与nr之间的业务引导
WO2013050070A1 (fr) Dispositif pour déclencher une procédure de déchargement en cas d'encombrement du trafic
US20100299446A1 (en) Method and apparatus for controlling service data flows transmitted in a tunnel
KR20140077095A (ko) 데이터 트래픽의 전달 방법 및 장치
US9705793B2 (en) Method for informing a node in a radio access network (RAN) about a type of service associated with an IP packet
US11432121B2 (en) Service function chain interworking
WO2019122497A1 (fr) Procédure de commande de connexion de communication utilisant des tranches de connexion de communication sélectionnées
US20150245401A1 (en) Methods and apparatus for converting a single radio-access technology connection into a multiple radio-access technology connection
WO2016019985A1 (fr) Procédé, produit-programme d'ordinateur et appareil permettant une différentiation de flux de trafic
WO2018206101A1 (fr) Critères de sélection en vue de destinations de données (non ip)
WO2016102516A1 (fr) Système de communication
WO2012113154A1 (fr) Procédé et dispositif pour l'adaptation d'un chemin de données pour une entité mobile dans un réseau de communications

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: 14750453

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 14750453

Country of ref document: EP

Kind code of ref document: A1