Method and apparatus for improved packet detection rule provision
Various embodiments of the present disclosure provide methods and apparatuses for improved packet detection rule provision. A method performed by a first network entity comprises: transmitting packet detection information, PDI, to a second network entity, wherein the PDI indicates information on one or more traffic endpoints on which packets are to be detected.
1. A method performed by a first network entity, comprising:
receiving from a second network entity an indication that the second network entity supports multiple instances of traffic endpoint identifiers (IDs) in packet detection information (PDI);
transmitting to the second network entity a session establishment request comprising a PDI information element (IE) comprising a first traffic endpoint ID IE and a second traffic endpoint ID IE, wherein
the first traffic endpoint ID IE includes a first traffic endpoint value, and
the second traffic endpoint ID IE includes a second traffic endpoint value, wherein
the session establishment request further comprises a create traffic endpoint IE that comprises a QoS flow identifier (QFI) and the QFI is not included in the PDI IE.
2. The method of claim 1 , wherein
the first traffic endpoint value pertains to a first service data flow, and
the second traffic endpoint value also pertains to said first service data flow.
3. The method of claim 1 , wherein
the first network entity is a control plane network entity, and
the second network entity is a user plane network entity.
4. A method performed by a second network entity, comprising:
receiving from a first network entity a session establishment request comprising a packet detection information (PDI) information element (IE) comprising i) a first traffic endpoint ID IE comprising a first traffic endpoint value and ii) a second traffic endpoint ID IE comprising a second traffic endpoint value;
performing packet detection based on information included in the PDI IE; and
transmitting an indication indicating support of multiple traffic endpoints, wherein
the session establishment request further comprises a create traffic endpoint IE that comprises a QoS flow identifier (QFI) and the QFI is not included in the PDI IE.
5. The method of claim 4 , wherein
the first traffic endpoint value pertains to a first service data flow, and
the second traffic endpoint value also pertains to said first service data flow.
6. The method of claim 4 , wherein
the session establishment request is a request for establishing a Packet Forwarding Control Protocol (PFCP) session,
the first traffic endpoint ID IE comprises information uniquely identifying a first traffic endpoint for the PFCP session, and
the second traffic endpoint ID IE comprises information uniquely identifying a second traffic endpoint for the PFCP session.
7. The method of claim 4 , further comprising:
configuring an applicability of a quality-of-service (QOS) flow identifier for packets to be detected on a traffic endpoint.
8. The method of claim 4 , wherein
the first network entity is a control plane network entity, and
the second network entity is a user plane network entity.
9. A first network entity comprising:
memory; and
processing circuitry, wherein the first network entity is configured to perform a method comprising:
transmitting to the second network entity a session establishment request comprising a packet detection information (PDI) information element (IE) comprising a first traffic endpoint ID IE and a second traffic endpoint ID IE, wherein
the first traffic endpoint ID IE includes a first traffic endpoint value,
the second traffic endpoint ID IE includes a second traffic endpoint value, and
the session establishment request further comprises a create traffic endpoint IE that comprises a QoS flow identifier (QFI) and the QFI is not included in the PDI IE.
10. The first network entity of claim 9 , wherein
the first traffic endpoint value pertains to a first service data flow, and
the second traffic endpoint value also pertains to said first service data flow.
11. The first network entity of claim 9 , wherein
session establishment request is a request for establishing a Packet Forwarding Control Protocol (PFCP) session,
the first traffic endpoint ID IE comprises information uniquely identifying a first traffic endpoint for the PFCP session, and
the second traffic endpoint ID IE comprises information uniquely identifying a second traffic endpoint for the PFCP session.
12. The first network entity of claim 9 , wherein the first network entity is further configured to receive, from the second network entity, an indication indicating support of multiple traffic endpoints in the PDI.
13. The first network entity of claim 9 , wherein
the first network entity is a control plane network entity, and
the second network entity is a user plane network entity.
14. A second network entity comprising:
memory;
processing circuitry; and
a receiver for receiving from a first network entity a session establishment request comprising a packet detection information (PDI) information element (IE) comprising i) a first traffic endpoint ID IE comprising a first traffic endpoint value and ii) a second traffic endpoint ID IE comprising a second traffic endpoint value, wherein
the second network entity is configured to perform packet detection based on information included in the received PDI IE, and
the session establishment request further comprises a create traffic endpoint IE that comprises a QoS flow identifier (QFI) and the QFI is not included in the PDI IE.
15. The second network entity of claim 14 , wherein the network entity is further configured to:
transmit an indication indicating support of multiple traffic endpoints in the PDI.
16. The second network entity of claim 14 , wherein
the first traffic endpoint value pertains to a first service data flow, and
the second traffic endpoint value also pertains to said first service data flow.
17. The second network entity of claim 14 , wherein
the session establishment request is a request for establishing a Packet Forwarding Control Protocol (PFCP) session,
the first traffic endpoint ID IE comprises information uniquely identifying a first traffic endpoint for the PFCP session, and
the second traffic endpoint ID IE comprises information uniquely identifying a second traffic endpoint for the PFCP session.
18. The second network entity of claim 14 , wherein the second network entity is further configured to configure an applicability of a quality-of-service (QOS) flow identifier for packets to be detected on a traffic endpoint.
19. The second network entity of claim 14 , wherein the first network entity is a control plane network entity, and the second network entity is a user plane network entity.