CN108234344B - Method and device for identifying service data flow - Google Patents
Method and device for identifying service data flow Download PDFInfo
- Publication number
- CN108234344B CN108234344B CN201611160464.4A CN201611160464A CN108234344B CN 108234344 B CN108234344 B CN 108234344B CN 201611160464 A CN201611160464 A CN 201611160464A CN 108234344 B CN108234344 B CN 108234344B
- Authority
- CN
- China
- Prior art keywords
- service data
- data stream
- universal
- identifier
- offset
- Prior art date
- Legal status (The legal status 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 status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
- H04L47/2483—Traffic characterised by specific attributes, e.g. priority or QoS involving identification of individual flows
Abstract
The embodiment of the invention provides a method and a device for identifying service data flow, wherein the method comprises the following steps: determining a universal service data stream identifier, wherein the universal service data stream identifier comprises one or more service data stream feature items describing service data streams; and identifying the service data stream to be judged according to the service data stream characteristic item in the universal service data stream identifier. The method can identify and distinguish the service data flow without adopting the general service data flow identification depending on a specific protocol, realizes the identification and processing of the cross-protocol service data flow by clustering the various general service data flow identifications, and is suitable for the identification of various service data flows such as IP, Non-IP (Non-IP), Ethernet frame (Ethernet frame format) and the like.
Description
Technical Field
The present invention relates to the field of communications technologies, and in particular, to a method and an apparatus for identifying a service data stream.
Background
A current mobile communication network EPS (Evolved Packet System) architecture (taking a non-roaming scenario as an example) is shown in fig. 1.
As can be seen from fig. 1, the UE accesses the network through the E-UTRAN (evolved universal terrestrial radio access network), and directly/indirectly interacts with the control plane network element MME and the user plane network element Serving Gateway/PDN Gateway through the E-UTRAN, respectively. It is worth noting that the user plane message of the UE is forwarded through the E-UTRAN, the Serving Gateway and the PDNGateway in sequence, and finally the support of the PDN connection service between the UE and the external PDN network is realized.
The concept of Packet Data Network (PDN) connectivity service is defined in the EPS system, which refers to the IP connection provided by the EPS network between the UE and an external PDN of one PLMN (public land mobile network), the PDN connectivity service supporting the transport of one or more Service Data Flows (SDFs).
When the S5/S8 interface between the Serving Gateway (SGW) and the PDN GW is based on the GPRS Tunneling Protocol (GTP), PDN connectivity traffic in the EPS network is provided by EPS bearers (bearers). An aggregation of EPS bearer unique identifier SDFs, corresponding to an aggregation of multiple SDFs with the same bearer level QoS (quality of service), each SDF corresponding to a packet filter in a transport stream template (TFT), that is, each EPS S5/S8 bears an uplink TFT associated with a UE and a downlink TFT associated with a PDN-GW; s1 loading is similar.
As can be seen from fig. 2, there is a radio bearer (radio bearer) between the UE (user equipment) and the eNB (base station), an S1bearer between the eNB and the Serving GW (SGW), and an S5/S8bearer between the SGW and the PDN GW (PGW); these bearers are all 1:1 mapped. For the same UE, the system may establish multiple bearers for the same UE at the same time.
The existing method is designed based on an IP network, and needs to identify and process service data flow according to quintuple information of an IP message. In the 5G network, different protocols such as IP, Non-IP, EtherNet frame and the like need to be supported, and the prior art is not applicable any more. Further, when a new protocol type needs to be carried subsequently, the network will have to be greatly modified in both the control plane and the forwarding plane to support the protocol type, and related services will also need a long time for the network to be on-line.
On the other hand, there is also a need to identify and support multiple different protocols on the base station and UE sides. Considering the huge number of base stations and UEs, if the existing scheme and its simple extended version are adopted, the overall implementation cost is very high.
Therefore, a protocol-independent method for identifying service data streams is needed to solve the problem that service data streams cannot be distinguished in a transport stream template-based manner when the type of service data stream carried in a network is not limited to IP.
Disclosure of Invention
In view of the foregoing technical problems, embodiments of the present invention provide a method and an apparatus for identifying a service data flow, so as to solve the problem that when a type of a service data flow carried in a network is not limited to an IP, the service data flow cannot be distinguished in a manner based on a transport stream template.
According to a first aspect of the embodiments of the present invention, there is provided a method for identifying a service data stream, including:
determining a universal service data stream identifier, wherein the universal service data stream identifier comprises one or more service data stream feature items describing service data streams;
and identifying the service data stream to be judged according to the service data stream characteristic item in the universal service data stream identifier.
Optionally, the identifying the service data stream according to the service data stream feature item in the universal service data stream identifier includes:
performing logic operation on each service data stream feature item in the universal service data stream identifier and the service data stream to be judged;
and if the logical operation results are the first preset values, judging that the universal service data stream identifier is successfully matched with the service data stream to be judged, and identifying the service data stream to be judged as the service data stream corresponding to the universal service data stream identifier.
Optionally, the identifying the service data stream according to the service data stream feature item in the universal service data stream identifier includes:
substituting the characteristic items of each service data stream contained in the universal service data stream identification and the logical operation result of the service data stream to be judged into the logical operation rule contained in the universal service data stream identification for logical operation;
and if the logical operation result is the second preset value, judging that the universal service data stream identifier is successfully matched with the service data stream to be judged, and identifying the service data stream to be judged as the service data stream logical operation rule corresponding to the universal service data stream identifier.
Optionally, the service data flow characteristic item includes one or more of the following items: the feature item identification, the Offset of the part needing to be matched, the Length of the part needing to be matched, the matching Mask and the expected matching result Value.
Optionally, the condition for determining that the matching between one service data stream feature item and the service data stream to be determined is as follows: the result of the following operation is a first predetermined value:
(Packet [ Offset to (Offset + Length-predetermined Value) ] & Mask) = Value, or (Packet [ Offset to (Offset + Length-predetermined Value) ] & Mask) > (bit number on the right side of Mask, which is continuously zero) } Value;
packet represents a service data stream;
offset represents an Offset of a portion to be matched;
length represents the Length of the portion to be matched;
mask represents a matching Mask;
value represents the expected matching result;
the & represents bitwise and operator;
> > represents the shift operator.
Optionally, the generic service data stream identifier includes: a first field and a second field, wherein the first field represents the number of characteristic items of the service data flow, the second field represents characteristic information for describing the service data flow, the characteristic information includes one or more service data flow characteristic items, or the characteristic information includes: and one or more service data stream characteristic items and the logic operation rule of the matching result of each service data stream characteristic item.
Optionally, the structure of the generic service data stream identifier further includes: the third field represents the name or identification of the service data flow, and the fourth field represents the description information of the service data flow.
Optionally, the generic service data stream identifier is obtained from a policy function; and/or
The universal service data stream identifier is obtained from local configuration data; and/or
The universal service data stream identifier is a group or a plurality of groups of universal service data stream identifiers which are sent by the UE during session establishment or at other moments or are adopted by the UE.
Optionally, the generic service data stream identifier is issued to the user plane function by the control plane function; and/or
The universal service data stream identifier is obtained by the user plane function according to the type identifier of the service data stream sent by the control plane function.
According to a second aspect of the embodiments of the present invention, there is also provided an apparatus for identifying a service data stream, including:
the system comprises a determining module, a judging module and a judging module, wherein the determining module is used for determining a universal service data stream identifier, and the universal service data stream identifier comprises one or more service data stream characteristic items describing service data streams;
and the identification module is used for identifying the service data stream to be judged according to the service data stream feature item in the universal service data stream identifier.
Optionally, the identification module is further configured to: performing logic operation on each service data stream feature item in the universal service data stream identifier and the service data stream to be judged; and if the logical operation results are the first preset values, judging that the universal service data stream identifier is successfully matched with the service data stream to be judged, and identifying the service data stream to be judged as the service data stream corresponding to the universal service data stream identifier.
Optionally, the identification module is further configured to: substituting the characteristic items of each service data stream contained in the universal service data stream identification and the logical operation result of the service data stream to be judged into the logical operation rule contained in the universal service data stream identification for logical operation; and if the logical operation result is the second preset value, judging that the universal service data stream identifier is successfully matched with the service data stream to be judged, and identifying the service data stream to be judged as the service data stream corresponding to the universal service data stream identifier.
Optionally, the service data flow characteristic item includes one or more of the following items: the feature item identification, the Offset of the part needing to be matched, the Length of the part needing to be matched, the matching Mask and the expected matching result Value.
Optionally, the condition for determining that the matching between one service data stream feature item and the service data stream to be determined is as follows: the result of the following operation is a first predetermined value:
(Packet [ Offset to (Offset + Length-predetermined Value) ] & Mask) > (the number of bits on the right side of the Mask that are continuously zero) ═ Value, or (Packet [ Offset to (Offset + Length-predetermined Value) ] & Mask) > (the number of bits on the right side of the Mask that are continuously zero) > (Value);
packet represents a service data stream;
offset represents an Offset of a portion to be matched;
length represents the Length of the portion to be matched;
mask represents a matching Mask;
value represents the expected matching result;
the & represents bitwise and operator;
> > represents the shift operator.
Optionally, the generic service data stream identifier includes: a first field and a second field, wherein the first field represents the number of characteristic items of the service data flow, the second field represents characteristic information for describing the service data flow, the characteristic information includes one or more service data flow characteristic items, or the characteristic information includes: and one or more service data stream characteristic items and the logic operation rule of the matching result of each service data stream characteristic item.
Optionally, the structure of the generic service data stream identifier further includes: the third field represents the name or identification of the service data flow, and the fourth field represents the description information of the service data flow.
Optionally, the generic service data stream identifier is obtained from a policy function; and/or
The universal service data stream identifier is obtained from local configuration data; and/or
The universal service data stream identifier is one or more groups of universal service data stream identifiers sent by the UE during session establishment or at other moments or adopted by the UE.
Optionally, the generic service data stream identifier is issued to the user plane function by the control plane function; and/or
The universal service data stream identifier is obtained by the user plane function according to the type identifier of the service data stream sent by the control plane function.
One of the above technical solutions has the following advantages or beneficial effects: the method can identify and distinguish the service data flow without adopting the general service data flow identification depending on a specific protocol, realizes the identification and processing of the cross-protocol service data flow by clustering the various general service data flow identifications, and is suitable for the identification of various service data flows such as IP, Non-IP (Non-IP), Ethernet frame (Ethernet frame format) and the like. And the universal service data stream identifier in this embodiment can implement flexible and rapid adaptation and deployment for a new service type through configuration of an operator, and based on the universal service data stream identifier in this embodiment, flexible QoS control for a service data stream can be implemented.
Drawings
Fig. 1 is a schematic diagram of a conventional EPS network architecture;
FIG. 2 is a diagram of two conventional unicast EPS bearings (GTP-based S5/S8);
fig. 3 is a flowchart of identifying a service data flow according to a first embodiment of the present invention;
FIG. 4 is a diagram illustrating a network architecture according to a second embodiment of the present invention;
fig. 5 is a flowchart of acquiring a generic service data stream identifier according to a second embodiment of the present invention;
fig. 6 is a flowchart of issuing a generic service data stream identifier in the third embodiment of the present invention;
fig. 7 is a block diagram of an apparatus for identifying a service data flow in the fourth embodiment of the present invention.
Detailed Description
Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.
As will be appreciated by one skilled in the art, embodiments of the present invention may be embodied as a system, apparatus, device, method, or computer program product. Thus, embodiments of the invention may be embodied in the form of: entirely hardware, entirely software (including firmware, resident software, micro-code, etc.), or a combination of hardware and software.
In a mobile communication system, a User Equipment (UE) obtains a Data service through a PDN connection (Packet Data Network connection) established in advance for the UE. Multiple core network bearers may be included in each PDN connection. Each core network bearer will correspond one-to-one to a bearer (bearer) on the radio side. The same QoS guarantee can be obtained through the data message transmitted by the same bearer.
The mapping relationship between the user traffic and the bearer is realized in an EPC system through a transport stream template (TFT), that is, the IP quintuple of traffic is matched, and then different data messages are borne by corresponding bearers according to the matching result.
In the research of 3GPP on 5G network architecture, it is clear that the mobile network needs to support IP, Non-IP and Ethernet Frame type data packets. However, when the type of the packet carried in the network is not limited to IP, the TFT-based method cannot be used to distinguish the traffic data flow.
Example one
Referring to fig. 3, a method for identifying a traffic data flow is shown, which includes:
the above-mentioned generic Flow Identification can be expressed by General Flow Identification (GFI);
the service data Flow Characteristic Item can be represented by a Flow charateristic Item.
In this embodiment, the generic service data stream identifier (GFI) may include: a first field and a second field, wherein the first field represents the number (Count) of service data flow feature items, the second field represents service data flow features and describes feature information of a service data flow, the feature information includes one or more service data flow feature items, or the feature information includes: and one or more service data stream characteristic items and the logic operation rule of the matching result of each service data stream characteristic item.
Further, the structure of the generic service data stream identifier may further include: the third field represents the name or identification of the service data flow, and the fourth field represents the description information of the service data flow.
Optionally, the basic structure of the generic service data stream identifier (GFI) in this embodiment may be:
TABLE 1
| Flow Identification | Flow Description | Count | Flow Characteristic |
Wherein the meaning of each field is as follows:
flow Identification (traffic data Flow Identification): name and/or ID representing service data flow, belonging to selectable item;
flow Description (traffic data Flow Description): description information representing a service data stream, belonging to the selectable item;
count (number): indicating a number of characteristics for the traffic data stream;
flow charateristic (traffic data Flow feature): the representation is used for describing the Characteristic information of the service data Flow, and comprises one or more service data Flow Characteristic items (Flow charateristic items (s)) and logical rule (logical operation rule).
The Logical Rule is an optional Item, and is a Logical operation Rule (or referred to as a Logical operation relationship) including a matching result of each Flow probabilistic Item.
When the Logical Rule exists, the GFI matching is judged to be successful according to the Logical operation result of the Logical operation Rule;
when the Logical Rule does not exist, the Logical operation result of each Flow Characteriodic Item is represented as true, and the GFI matching can be judged to be successful.
Wherein, Flow charateristic Item: representing a piece of characteristic information for describing service data flow, the structure may be:
TABLE 2
| Flow Characteristic Item Identification | Offset | Length | Mask | Value |
Wherein the sub-fields have the following meanings:
flow charateristic Item Identification (service data Flow Characteristic Item Identification): name and/or ID of the Characteriodic Item, i.e. the identification of the feature Item;
offset: the offset of the portion to be matched, for example, calculated from the first byte of the message or other fixed location;
length: the length of the portion to be matched, in bytes or other units;
mask: a matching mask used for precisely selecting a part to be matched (with bit granularity) when matching is carried out;
value: expected matching results.
And step 302, identifying the service data stream to be judged according to the service data stream feature item in the universal service data stream identifier.
In this embodiment, the universal service data stream identifier and the service data stream to be determined are used to perform logical operation, so as to identify the service data stream corresponding to the universal service data stream identifier according to the logical operation result.
The first method is to perform logical operation on each service data stream feature item in the universal service data stream identifier and the service data stream to be judged, and if the logical operation result is a first predetermined value (for example, the first predetermined value is set to be true), it is determined that the universal service data stream identifier and the service data stream to be judged are successfully matched, and the service data stream to be judged is identified as the service data stream corresponding to the universal service data stream identifier.
The first method is suitable for the Flow charateristic (service data Flow Characteristic) without logical rule.
And a second mode, substituting the Logical operation result of each service data stream feature item contained in the universal service data stream identifier and the service data stream to be judged into a Logical operation Rule contained in the universal service data stream identifier for Logical operation, if the Logical operation result is a second preset value (for example, the second preset value is set as true), judging that the universal service data stream identifier is successfully matched with the service data stream to be judged, and identifying the service data stream to be judged as the service data stream corresponding to the universal service data stream identifier.
The second method is suitable for Flow charateristic (service data Flow characteristics) including Logical Rule (Logical operation Rule).
For example, the condition for determining that a service data Flow feature Item (Flow probabilistic Item) is successfully matched with a service data Flow (packet) is as follows: the result of the logical operation (alternatively referred to as the matching result) of the following operation is a first predetermined value (e.g., the first predetermined value is set to true):
(Packet [ Offset + Length-1) ] & Mask) ═ Value, or
(Packet [ Offset to (Offset + Length-1) ] & Mask) > (bit number on the right side of Mask, which is zero continuously) ═ Value >
Wherein, Packet represents service data flow;
offset represents an Offset of a portion to be matched;
length represents the Length of the portion to be matched;
mask represents a matching Mask;
value represents the expected matching result;
and represents a bitwise and operator, e.g., a & b represents a bitwise and operation of a and b, and > > represents a shift operator, e.g., a > > i represents a shift operation of a to i bits right.
For another example, the condition for determining that a generic service data stream identifier (GFI) is successfully matched with a service data stream (packet) is as follows:
if the Flow Characteric of the general service data stream identification contains Logical Rule, substituting the Logical operation result of each Flow Characteric Item contained in the GFI and a certain service data stream into the Logical Rule for carrying out Logical operation, if the Logical operation result is more than, judging that the GFI is successfully matched with the certain service data stream, otherwise, judging that the GFI is not successfully matched with the certain service data stream.
If the Flow Characteriodic of the general service data Flow identification does not contain Logical Rule (Logical operation Rule), the Logical operation result of each Flow Characteriodic Item and a certain service data Flow is both true, the successful matching of the GFI and the certain service data Flow is judged, and otherwise, the unsuccessful matching of the GFI and the certain service data Flow is judged.
It should be noted that, the generic service data stream identifier (GFI) can be obtained as follows:
the universal service data stream identifier is obtained from the strategy function; and/or
The universal service data stream identification is obtained from the local configuration data; and/or
The generic service data stream identifier is one or more sets of generic service data stream identifiers transmitted by the UE at session establishment or other times or employed by the UE itself.
For example, the generic service data stream is identified as id 1, and after a certain time the UE generates a new service requirement (e.g. opens a new app), the UE needs to send a new id (e.g. id 2) to the CN (core network).
In this embodiment, optionally, the generic service data flow identifier is issued by a control plane function (or referred to as a core network control plane function) to a user plane function (or referred to as a core network user plane function); and/or the generic traffic data flow identification is obtained by the user plane function from the type identification of the traffic data flow sent by the control plane function (e.g. from a provisioned policy of the user plane function).
In this embodiment, the service data streams may not be identified and distinguished by using the general service data stream identifier depending on a specific protocol, and the identification and processing of the cross-protocol service data stream are implemented by clustering the multiple general service data stream identifiers, which is suitable for identifying multiple types of service data streams such as IP, Non-IP (Non-IP), Ethernet frame (Ethernet frame format), and the like. And the universal service data stream identifier in this embodiment can implement flexible and rapid adaptation and deployment for a new service type through configuration of an operator, and based on the universal service data stream identifier in this embodiment, flexible QoS control for a service data stream can be implemented.
Example two
Referring to fig. 4, in a new generation network architecture, a Control Plane function (or referred to as a Control Plane function entity) and a user Plane function (or referred to as a user Plane function entity) of a network are respectively implemented by Control Plane (CP) functions(s) and user Plane (up) functions(s). Wherein, the UP can be flexibly deployed at different positions of the network, such as Local-UP deployed at the position close to the base station/network edge, CN-UP deployed at the higher position of the network, etc.; and the CP may be deployed in a cloud form, and may reconstruct the control plane functions as one or more independent logical nodes (e.g., MM (mobility management), SM (Session management), etc.). If Policy functions (otherwise known as Policy function entities) are deployed in the network, the ability to achieve finer control through the Policy information will be available.
On the basis of the first embodiment, in this embodiment, the universal service data stream identifier may be obtained in any one or more of the following manners:
scheme a: obtained from a policy function (policy function), which may optionally obtain a generic service data stream identification from an application function, AF;
scheme b: obtaining from local configuration data;
scheme c: the generic service data flow identification(s) employed by the UE itself are transmitted or appended by the UE at session (session) setup or other times. (this information may be for the UL and/or DL direction).
Referring to fig. 5, a flow for acquiring a generic service data stream identifier is shown, which includes the following specific steps:
the scheme a includes a step 2a and a step 2b, in which, in the step 2a, the application function AF sends an AF FlowDescription (application function data service flow description) to the Policy function, and in the step 2b, the Policy function sends a FlowDescription Policy (data service flow description Policy) to the Core Network (CN).
It should be noted that, the step 2a in the scheme a is an optional step.
In the scheme b, the core network obtains a Local Flow Description Policy (Local data service Flow Description Policy).
The scheme c comprises a step 2a and a step 2b, wherein in the step 2a, the UE sends UE Flow Description (terminal service data Flow Description) to the CN; and 2b, the core network obtains Local Flow Description Policy (Local data service Flow Description Policy).
Note that in scenario c, when step 2a contains GFI, step 2b is no longer present; when step 2a only includes the Flow Identification, step 2b is a mandatory option for determining the corresponding GFI according to the local configuration or the obtained Flow Description Policy based on the Flow Identification.
The Flow Identification is a field in the GFI, as shown in table 1 in example two.
Alternatively, the Flow Identification may be standardized, customized by the operator, or a mixture of the two.
EXAMPLE III
Referring to fig. 4, in the architecture with CU separation (control plane function and user plane function separation), on the basis of the first embodiment, the following follow-up delivery and processing can be performed:
scheme a: the core network control plane function issues to the core network user plane function, and/or,
scheme b: the core network control plane function sends the type identification of the particular service data flow (the type identification may be standardized or assigned by the operator) and the core network user plane function obtains the corresponding (non-agreed) representation method from its own provisioning policy based on the identification.
Referring to fig. 6, a flow for issuing a generic service data flow identifier is shown, which includes the following specific steps:
scheme a, comprising step 3: and the core network control plane function sends the universal service data stream identifier to the core network user plane function.
Scheme b, comprising step 3a and step 3b, step 3 a: the core network control plane function sends the service data flow identification (FlowIdentification) to the core network user plane function; and step 3 b: and the core network user plane function acquires a general service data stream identifier (GFI) according to the service data stream identifier.
and step 5, the core network control plane function sends the service data Flow Identification (Flow Identification) to User Equipment (UE).
It should be noted that there is no necessary timing relationship among the above steps 3, 4 and 5, that is, the steps 3, 4 and 5 may be executed sequentially or simultaneously.
It should be noted that the Flow Identification referred to in step 3a in the above-mentioned scheme b is a field in the GFI, and can be seen in table 1 in example two.
Alternatively, the Flow Identification may be standardized, customized by the operator, or a mixture of the two.
Example four
Referring to fig. 7, an apparatus for identifying a traffic data flow is shown, the apparatus 700 comprising:
a determining module 701, configured to determine a generic service data stream identifier, where the generic service data stream identifier includes one or more service data stream feature items describing a service data stream;
an identifying module 702, configured to identify the service data stream to be determined according to the service data stream feature item in the universal service data stream identifier.
In this embodiment, optionally, the identifying module 702 is further configured to: performing logic operation on each service data stream feature item in the universal service data stream identifier and the service data stream to be judged; if the logical operation results are all the first predetermined values (for example, the first predetermined value is true), it is determined that the universal service data stream identifier is successfully matched with the service data stream to be determined, and the service data stream to be determined is identified as the service data stream corresponding to the universal service data stream identifier.
In this embodiment, optionally, the identifying module 702 is further configured to: substituting the characteristic items of each service data stream contained in the universal service data stream identification and the logical operation result of the service data stream to be judged into the logical operation rule contained in the universal service data stream identification for logical operation; if the logical operation result is the second predetermined value (for example, the second predetermined value is true), it is determined that the universal service data stream identifier is successfully matched with the service data stream to be determined, and the service data stream to be determined is identified as the service data stream corresponding to the universal service data stream identifier.
In this embodiment, optionally, the service data flow feature item includes one or more of the following items: the feature item identification, the Offset of the part needing to be matched, the Length of the part needing to be matched, the matching Mask and the expected matching result Value.
In this embodiment, the condition for determining that one service data stream feature item is successfully matched with the service data stream to be determined is as follows: the result of the following operation is a first predetermined value:
(Packet [ Offset to (Offset + Length-predetermined Value) ] & Mask) = Value, or (Packet [ Offset to (Offset + Length-predetermined Value) ] & Mask) > (bit number on the right side of Mask, which is continuously zero) } Value;
packet represents a service data stream;
offset represents an Offset of a portion to be matched;
length represents the Length of the portion to be matched;
mask represents a matching Mask;
value represents the expected matching result;
the & represents bitwise and operator;
> > represents the shift operator.
In this embodiment, optionally, the universal service data stream identifier includes: a first field and a second field, wherein the first field is used for identifying the number of characteristic items of the service data flow, the second field is used for describing characteristic information of the service data flow, the characteristic information includes one or more service data flow characteristic items, or the characteristic information includes: and one or more service data stream characteristic items and the logic operation rule of the matching result of each service data stream characteristic item.
In this embodiment, optionally, the structure of the generic service data stream identifier further includes: the third field represents the name or identification of the service data flow, and the fourth field represents the description information of the service data flow.
In this embodiment, optionally, the generic service data stream identifier is obtained from a policy function; and/or
The universal service data stream identifier is obtained from local configuration data; and/or
The universal service data stream identifier is one or more groups of universal service data stream identifiers sent by the UE at session establishment or other moments or adopted by the UE.
In this embodiment, optionally, the generic service data flow identifier is issued to the user plane function by the control plane function; and/or
The universal service data stream identifier is obtained by the user plane function according to the type identifier of the service data stream sent by the control plane function.
In this embodiment, the service data streams may not be identified and distinguished by using the general service data stream identifier depending on a specific protocol, and the identification and processing of the cross-protocol service data stream are implemented by clustering the multiple general service data stream identifiers, which is suitable for identifying multiple types of service data streams such as IP, Non-IP (Non-IP), Ethernet frame (Ethernet frame format), and the like. And the universal service data stream identifier in this embodiment can implement flexible and rapid adaptation and deployment for a new service type through configuration of an operator, and based on the universal service data stream identifier in this embodiment, flexible QoS control for a service data stream can be implemented.
It should be appreciated that reference throughout this specification to "one embodiment" or "an embodiment" means that a particular feature, structure or characteristic described in connection with the embodiment is included in at least one embodiment of the present invention. Thus, the appearances of the phrases "in one embodiment" or "in an embodiment" in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.
In various embodiments of the present invention, it should be understood that the sequence numbers of the above-mentioned processes do not mean the execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation on the implementation process of the embodiments of the present invention.
In addition, the terms "system" and "network" are often used interchangeably herein.
It should be understood that the term "and/or" herein is merely one type of association relationship that describes an associated object, meaning that three relationships may exist, e.g., a and/or B may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" herein generally indicates that the former and latter related objects are in an "or" relationship.
In the embodiments provided herein, it should be understood that "B corresponding to a" means that B is associated with a from which B can be determined. It should also be understood that determining B from a does not mean determining B from a alone, but may be determined from a and/or other information.
In the several embodiments provided in the present application, it should be understood that the disclosed method and apparatus may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may be physically included alone, or two or more units may be integrated into one unit. The integrated unit can be realized in a form of hardware, or in a form of hardware plus a software functional unit.
The integrated unit implemented in the form of a software functional unit may be stored in a computer readable storage medium. The software functional unit is stored in a storage medium and includes several instructions to enable a computer device (which may be a personal computer, a server, or a network device) to execute some steps of the transceiving method according to various embodiments of the present invention. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.
While the preferred embodiments of the present invention have been described, it should be understood that modifications and adaptations to those embodiments may occur to one skilled in the art without departing from the principles of the present invention and are within the scope of the present invention.
Claims (16)
1. A method for identifying a traffic data stream, comprising:
determining a universal service data stream identifier, wherein the universal service data stream identifier comprises one or more service data stream feature items describing service data streams;
identifying the service data stream to be judged according to the service data stream feature item in the universal service data stream identifier;
the identifying the service data stream according to the service data stream feature item in the universal service data stream identifier includes:
performing logic operation on each service data stream feature item in the universal service data stream identifier and the service data stream to be judged;
and if the logical operation results are the first preset values, judging that the universal service data stream identifier is successfully matched with the service data stream to be judged, and identifying the service data stream to be judged as the service data stream corresponding to the universal service data stream identifier.
2. The method of claim 1, wherein the identifying the service data flow according to the service data flow characteristic item in the generic service data flow identifier comprises:
substituting the characteristic items of each service data stream contained in the universal service data stream identification and the logical operation result of the service data stream to be judged into the logical operation rule contained in the universal service data stream identification for logical operation;
and if the logical operation result is the second preset value, judging that the universal service data stream identifier is successfully matched with the service data stream to be judged, and identifying the service data stream to be judged as the service data stream logical operation rule corresponding to the universal service data stream identifier.
3. The method of claim 1 or 2, wherein the traffic data stream characteristics items comprise one or more of: the feature item identification, the Offset of the part needing to be matched, the Length of the part needing to be matched, the matching Mask and the expected matching result Value.
4. The method of claim 3,
the condition for judging the successful matching of one service data stream characteristic item and the service data stream to be judged is as follows: the result of the following operation is a first predetermined value:
(Packet [ Offset to (Offset + Length-predetermined Value) ] & Mask) = Value, or (Packet [ Offset to (Offset + Length-predetermined Value) ] & Mask) > (bit number on the right side of Mask, which is continuously zero) } Value;
packet represents a service data stream;
offset represents an Offset of a portion to be matched;
length represents the Length of the portion to be matched;
mask represents a matching Mask;
value represents the expected matching result;
the & represents bitwise and operator;
> > represents the shift operator;
the field representing the Packet from Offset start to (Offset + Length-predetermined value) cutoff.
5. The method according to claim 1 or 2, wherein the generic service data flow identifier comprises: a first field and a second field, wherein the first field represents the number of characteristic items of the service data flow, the second field represents characteristic information for describing the service data flow, the characteristic information includes one or more service data flow characteristic items, or the characteristic information includes: and one or more service data stream characteristic items and the logic operation rule of the matching result of each service data stream characteristic item.
6. The method of claim 5, wherein the structure of the generic service data flow identifier further comprises: the third field represents the name or identification of the service data flow, and the fourth field represents the description information of the service data flow.
7. The method of claim 1,
the universal service data stream identifier is obtained from a policy function; and/or
The universal service data stream identifier is obtained from local configuration data; and/or
The universal service data stream identifier is a group or a plurality of groups of universal service data stream identifiers which are sent by the UE during session establishment or at other moments or are adopted by the UE.
8. The method of claim 1,
the universal service data stream identification is issued to the user plane function by the control plane function; and/or
The universal service data stream identifier is obtained by the user plane function according to the type identifier of the service data stream sent by the control plane function.
9. An apparatus for identifying traffic data streams, comprising:
the system comprises a determining module, a judging module and a judging module, wherein the determining module is used for determining a universal service data stream identifier, and the universal service data stream identifier comprises one or more service data stream characteristic items describing service data streams;
the identification module is used for identifying the service data stream to be judged according to the service data stream feature item in the universal service data stream identifier;
the identification module is further to: performing logic operation on each service data stream feature item in the universal service data stream identifier and the service data stream to be judged; and if the logical operation results are the first preset values, judging that the universal service data stream identifier is successfully matched with the service data stream to be judged, and identifying the service data stream to be judged as the service data stream corresponding to the universal service data stream identifier.
10. The apparatus of claim 9, wherein the identification module is further configured to: substituting the characteristic items of each service data stream contained in the universal service data stream identification and the logical operation result of the service data stream to be judged into the logical operation rule contained in the universal service data stream identification for logical operation; and if the logical operation result is the second preset value, judging that the universal service data stream identifier is successfully matched with the service data stream to be judged, and identifying the service data stream to be judged as the service data stream corresponding to the universal service data stream identifier.
11. The apparatus of claim 9 or 10, wherein the traffic data stream characteristics item comprises one or more of: the feature item identification, the Offset of the part needing to be matched, the Length of the part needing to be matched, the matching Mask and the expected matching result Value.
12. The apparatus of claim 11,
the condition for judging the successful matching of one service data stream characteristic item and the service data stream to be judged is as follows: the result of the following operation is a first predetermined value:
(Packet [ Offset to (Offset + Length-predetermined Value) ] & Mask) > (the number of bits on the right side of the Mask that are continuously zero) ═ Value, or (Packet [ Offset to (Offset + Length-predetermined Value) ] & Mask) > (the number of bits on the right side of the Mask that are continuously zero) > (Value);
packet represents a service data stream;
offset represents an Offset of a portion to be matched;
length represents the Length of the portion to be matched;
mask represents a matching Mask;
value represents the expected matching result;
the & represents bitwise and operator;
> > represents the shift operator;
the field representing the Packet from Offset start to (Offset + Length-predetermined value) cutoff.
13. The apparatus of claim 9 or 10, wherein the generic service data flow identifier comprises: a first field and a second field, wherein the first field represents the number of characteristic items of the service data flow, the second field represents characteristic information for describing the service data flow, the characteristic information includes one or more service data flow characteristic items, or the characteristic information includes: and one or more service data stream characteristic items and the logic operation rule of the matching result of each service data stream characteristic item.
14. The apparatus of claim 13, wherein the structure of the generic service data flow identifier further comprises: the third field represents the name or identification of the service data flow, and the fourth field represents the description information of the service data flow.
15. The apparatus of claim 9,
the universal service data stream identifier is obtained from a policy function; and/or
The universal service data stream identifier is obtained from local configuration data; and/or
The universal service data stream identifier is one or more groups of universal service data stream identifiers sent by the UE during session establishment or at other moments or adopted by the UE.
16. The apparatus of claim 9,
the universal service data stream identification is issued to the user plane function by the control plane function; and/or
The universal service data stream identifier is obtained by the user plane function according to the type identifier of the service data stream sent by the control plane function.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201611160464.4A CN108234344B (en) | 2016-12-15 | 2016-12-15 | Method and device for identifying service data flow |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201611160464.4A CN108234344B (en) | 2016-12-15 | 2016-12-15 | Method and device for identifying service data flow |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108234344A CN108234344A (en) | 2018-06-29 |
| CN108234344B true CN108234344B (en) | 2020-09-11 |
Family
ID=62651466
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201611160464.4A Active CN108234344B (en) | 2016-12-15 | 2016-12-15 | Method and device for identifying service data flow |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108234344B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111327649B (en) * | 2018-12-14 | 2023-04-21 | 中国电信股份有限公司 | Service data processing method, device, SMF, system and storage medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101005445A (en) * | 2006-01-18 | 2007-07-25 | 华为技术有限公司 | Method for mapping service flow to service transmission path and optical network terminal |
| CN101631336A (en) * | 2009-08-06 | 2010-01-20 | 中兴通讯股份有限公司 | Method and device for managing uplink transmission stream template |
| CN102238743A (en) * | 2010-05-05 | 2011-11-09 | 联芯科技有限公司 | Multiplex bearer management method and device |
| CN102752796A (en) * | 2011-04-21 | 2012-10-24 | 中兴通讯股份有限公司 | Machine communication resource management method and device |
| EP2983443A1 (en) * | 2013-04-05 | 2016-02-10 | Ntt Docomo, Inc. | Radio base station and mobile station |
-
2016
- 2016-12-15 CN CN201611160464.4A patent/CN108234344B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101005445A (en) * | 2006-01-18 | 2007-07-25 | 华为技术有限公司 | Method for mapping service flow to service transmission path and optical network terminal |
| CN101631336A (en) * | 2009-08-06 | 2010-01-20 | 中兴通讯股份有限公司 | Method and device for managing uplink transmission stream template |
| CN102238743A (en) * | 2010-05-05 | 2011-11-09 | 联芯科技有限公司 | Multiplex bearer management method and device |
| CN102752796A (en) * | 2011-04-21 | 2012-10-24 | 中兴通讯股份有限公司 | Machine communication resource management method and device |
| EP2983443A1 (en) * | 2013-04-05 | 2016-02-10 | Ntt Docomo, Inc. | Radio base station and mobile station |
Non-Patent Citations (1)
| Title |
|---|
| 4G_LTE网络流量分析系统的设计与实现;鞠冰卿;《中国优秀硕士学位论文全文数据库》;20150601;6-11页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108234344A (en) | 2018-06-29 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111052792B (en) | Method for processing QOS operation error and user equipment | |
| CN109314695B (en) | Method for determining user plane protocol stack, control plane network element and system | |
| US20190166016A1 (en) | Subscription-Based Event Notification Techniques for Reducing Data Buffering in Mobile Networks | |
| US8451764B2 (en) | Method and apparatus for supporting MBMS in system architecture evolution | |
| CN105027664B (en) | Grouped data in the wireless communication system using WLAN connects | |
| EP3783987A1 (en) | Information transmission method and device | |
| GB2600892A (en) | Establishing a group session in a mobile network for subscribers associated with a group | |
| US10084925B2 (en) | Method and apparatus for processing charging in wireless communication system and method and apparatus for providing policy service using the same | |
| EP2908464A1 (en) | Method, system, and controller for routing forwarding | |
| CN109417682B (en) | Method, equipment and system for processing service | |
| US8867471B2 (en) | Method, device, and system for reporting radio access network element information | |
| US9119219B2 (en) | Bandwidth control method, apparatus and system | |
| US20150264580A1 (en) | Mobile communication system, control apparatus, communication control method, and non-transitory computer readable medium | |
| US10484906B2 (en) | Method and apparatus for applying different priorities to packets | |
| EP2608581A1 (en) | Method, system and apparatus for indicating type of messages | |
| WO2013037208A1 (en) | Transport stream template matching method and device in lte system | |
| CN108306843B (en) | Service data stream transmission method, system and PGW | |
| CN108234344B (en) | Method and device for identifying service data flow | |
| US20190335413A1 (en) | Terminal apparatus, core network apparatus, and communication control method | |
| CN101352004A (en) | Redirection of B-grade PDP data stream to A-grade PDP before establishing B-grade PDP context | |
| EP2740310B1 (en) | Implementation of packet data service in a mobile communication network | |
| WO2017197641A1 (en) | Method, device, and system for transmitting message | |
| WO2011157177A2 (en) | Method and device for controlling service stream | |
| US20230362709A1 (en) | Multiple tags handling for qos rules and packet filters | |
| US20220294739A1 (en) | Method and apparatus for improved packet detection rule provision |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| CP01 | Change in the name or title of a patent holder |
Address after: 100191 No. 40, Haidian District, Beijing, Xueyuan Road Patentee after: CHINA ACADEMY OF TELECOMMUNICATIONS TECHNOLOGY Address before: 100191 No. 40, Haidian District, Beijing, Xueyuan Road Patentee before: CHINA ACADEMY OF TELECOMMUNICATIONS TECHNOLOGY |
|
| CP01 | Change in the name or title of a patent holder | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20210603 Address after: 100085 1st floor, building 1, yard 5, Shangdi East Road, Haidian District, Beijing Patentee after: DATANG MOBILE COMMUNICATIONS EQUIPMENT Co.,Ltd. Address before: 100191 No. 40, Haidian District, Beijing, Xueyuan Road Patentee before: CHINA ACADEMY OF TELECOMMUNICATIONS TECHNOLOGY |
|
| TR01 | Transfer of patent right |