KR20200015303A - Apparatus and method for reporting packet - Google Patents

Abstract

The present invention relates to a packet reporting method to increase real-time properties in billing and a packet reporting system thereof. According to one embodiment of the present invention, the packet reporting system comprises: a session management function (SMF) setting a flow information reporting format and transmitting the set flow information reporting format to a user plane function (UPF); and the UPF receiving the flow information reporting format from the SMF, generating a reporting flow appropriate to the received flow information reporting format based on each of a plurality of flows forming a session, and transmitting at least one of the generated reporting flows to the SMF.

Description

Packet reporting method and system {APPARATUS AND METHOD FOR REPORTING PACKET}

The present invention relates to a packet reporting method and system.

As the types of communication services and transmission request rates vary in the LTE communication system, the LTE frequency expansion and the evolution to the 5G communication system are actively progressing.

This rapidly evolving 5G communication system accommodates as many terminals as possible based on limited radio resources, while enabling enhanced mobile broadband (eMBB) / massive machine type communications (mMTC) / It supports scenarios of ultra-reliable and low latency communications (URLLC).

In the 5G communication system, a network structure for supporting a terminal, a base station (access), a core, and a server from end to end is defined, and a single node (for example, S-GW, P-GW, etc.) in LTE (4G) is defined. Separates the functions of control signaling and data transmission / reception, which are performed in a complex manner, and divides an area (or control area) of a control signaling function and a user plane of a data transmission / reception function. It defines.

In this case, various nodes are included in the control plane. For example, AMF (Access and Mobility Function) to control access to the wireless section of the terminal, PCF (Policy Control Function) to manage / control policies such as terminal information, subscription service information for each terminal, billing, and sessions for using data services for each terminal. Examples include a Session Management Function (SMF) that manages / controls a network, and a Network Exposure Function (NEF) that manages information sharing with an external network.

In addition, the user plane may include things such as UPF.

PCT Patent Publication, 2018-008944 (published Jan. 11, 2018)

In the 5G communication system, a 'session' refers to a service provided to the terminal by connecting the terminal to the 5G communication system through a predetermined relation. In a process in which a session is supplied to a terminal, a packet (the packet at this time may be referred to as a user plane packet) is transmitted and received between the 5G communication system and the terminal through the UPF.

Here, a plurality of packets transmitted and received within a session may be classified and aggregated according to a predetermined criterion with reference to a packet header field and the like. Such a plurality of packets are classified and aggregated as a flow. Can be. Here, the criteria for classification and aggregation may include, for example, an address (source IP address) of a terminal or a service address (destination IP address) for which the terminal wants to receive a service.

The UPF receives a predetermined rule or command from the SMF, processes the packet accordingly, and generates usage information. The generated usage information is transferred from the UPF to the SMF, and the SMF receives the usage information from the UPF and collects them. The SMF transmits the collected usage information to the charging system through a converged charging system (CCS).

At this time, the process of collecting and receiving usage information from the UPF may affect the control performance on the real-time of billing (how real-time charging is possible), latency, or QoS. It can affect your satisfaction with 5G service.

Accordingly, the problem to be solved of the present invention is to provide a technique for the optimal process of the SMF is collected by receiving the usage information from the UPF, through this technique to improve or improve the real-time of billing, and also the latency (latency) Is to minimize).

In addition, the present invention is to provide the above-described technology without adding additional hardware to the 5G communication system, that is, without additional cost.

However, the problem to be solved of the present invention is not limited to the above-mentioned thing, another problem to be solved is not mentioned can be clearly understood by those skilled in the art from the following description. will be.

The packet reporting system according to an embodiment sets a flow information reporting format and transmits the set flow information reporting format to a user plane function device (UPF). a management flow (SMF) and the flow information report format from the session management function device, and a reporting flow conforming to the received flow information report format based on each of a plurality of flows constituting a session. And a user plane function device for transmitting at least one of the generated reporting flows to the session management function device.

According to an exemplary embodiment, a packet reporting method includes setting a session management function (SMF) flow information reporting format, and wherein the session management function apparatus sets the set flow information reporting format. Transmitting to a user plane function device (UPF); receiving, by the user plane function device, the flow information report format from the session management function device; and a plurality of flows constituting a session Generating, by the user plane function device, a reporting flow that conforms to the received flow information report format, and wherein the user plane function device uses the session management function to generate at least one of the generated reporting flows. Transmitting to the device.

According to one embodiment, the SMF can receive the reporting flow generated from the UPF according to the method optimized for aggregation, thereby improving the real-time of billing (how real-time billing is possible) and the control of QoS. It is possible to implement a system having a low latency (low latency).

1 conceptually illustrates the architecture of a 5G communication system according to one embodiment.
2 conceptually illustrates sessions and flows in a 5G communication system.
3 exemplarily illustrates a flow information reporting format and a reporting flow according to an embodiment.
4 illustrates a flow of data associated with a flow, transmitted and received between UPF and SMF, according to one embodiment.
5 exemplarily illustrates various ways of constructing tuples.
6 exemplarily shows the number of flows to be transferred from the UPF to the SMF in one turn.
7 exemplarily illustrates a plurality of flows ordered by a predetermined reference.
FIG. 8 illustrates a first flow information report format delivered by an SMF to a UPF according to an embodiment.
9 illustrates a second flow information report format delivered by the SMF to the UPF according to an embodiment.
FIG. 10 illustrates a format of a reporting flow delivered by the UPF to the SMF according to an embodiment.

Advantages and features of the present invention, and methods for achieving them will be apparent with reference to the embodiments described below in detail in conjunction with the accompanying drawings. However, the present invention is not limited to the embodiments disclosed below, but may be embodied in various different forms, and the present embodiments merely make the disclosure of the present invention complete, and those of ordinary skill in the art to which the present invention belongs. It is provided to fully inform the person having the scope of the invention, which is defined only by the scope of the claims.

In describing the embodiments of the present invention, if it is determined that a detailed description of a known function or configuration may unnecessarily obscure the gist of the present invention, the detailed description thereof will be omitted. In addition, terms to be described below are terms defined in consideration of functions in the embodiments of the present invention, which may vary according to intentions or customs of users and operators. Therefore, the definition should be made based on the contents throughout the specification.

1 conceptually illustrates an architecture 10 of a 5G communication system according to one embodiment.

The 5G communication system itself represented by the architecture 10 of FIG. 1 will be described. The 5G communication system is an advanced technology from the fourth generation LTE mobile communication technology. The 5G communication system is an extension of new radio access technology (RAT) and long term evolution (LTE) through an evolution or clean-state structure of an existing mobile communication network structure. eLTE (extended LTE) and non-3GPP access are supported.

However, since the architecture 10 shown in FIG. 1 is merely exemplary, the spirit of the present invention is not interpreted to be limited to the architecture 10 shown in FIG. 1, and the idea of the present invention is 5G communication. It is not to be construed as limited to systems.

The architecture 10 includes various components (ie, network function (NF)). Hereinafter, these components will be described.

Referring to FIG. 1, an authentication server function (AUSF: Authentication Server Function), an access and mobility management function (AMF: (Core) Access and Mobility Management Function), a session management function (SMF: Session Management Function) 200, a policy Policy Control Function (PCF), Application Function (AF), Unified Data Management (UDM), Data Network (DN), User Plane Function (UPF) 100, a (wireless) access network (R) AN (Radio) Access Network (UE), and a user equipment (UE) 300 are shown, although not shown in FIG. 1, a billing system (FIG. 4). Shown in) may be included in or coupled to architecture 10.

Here, the remaining components except for the user plane function (UPF) 100 and the session management function (SMF) 200 each perform well-known functions required in the 5G communication system, and thus description thereof will be omitted. .

The user plane function (UPF) 100 is a component belonging to a user plane in the 5G communication system, and may be referred to as a user plane function device 100 or a UPF 100 in the present specification. It will be referred to as (100). In addition, the session management function (SMF) 200 is a component belonging to a control plane separated from the above-described user plane in the 5G communication system, in the present specification, the session management function device 200 or the SMF 200. ), And hereinafter referred to as SMF (200). The system including the UPF 100 and the SMF 200 may be referred to as a packet reporting system.

The UPF 100 and the SMF 200 each perform well-known functions required by a 5G communication system. In addition, the UPF 100 and the SMF 200 perform functions to be provided in one embodiment. Accordingly, a description of the known technology itself performed by each of the UPF 100 and the SMF 200 will be briefly described or omitted, and the functions to be provided in one embodiment will be described in more detail. Let's look at it.

The UPF 100 detects a flow. In more detail, in a process in which a session is supplied to the terminal 300, a packet is transmitted and received between at least some components of the architecture 10 and the terminal 300. These packets are transmitted and received through the UPF 100, and thus, the UPF 100 generates one or a plurality of flows, which are the flows of the transmitted and received packets. 2 illustrates a process in which the session 110 is supplied to the terminal 300, and the session 110 and a plurality of flows (flow1 to flow5) constituting the session 110 are illustrated as an example. However, the number of flows of five is merely exemplary.

Here, the process of generating the flow by the UPF 100, the process of detecting the flow by the UPF 100 described above, or the process of transmitting the information about the detected flow to the SMF 200 by the UPF 100 will be described later. The UPF 100 may be performed based on a predetermined rule or command received from the SMF 200. Such rules and commands include Packet Detection Rule (PDR), Forwarding Action Rule (FAR), QoS Enforcement Rule (QER) or User Reporting Rule (URR). May be included. Among these, FAR represents a rule regarding packet delivery, and QER represents a rule regarding QoS control. In addition, the URR represents a rule for measuring usage information. The URR measures a packet transmitted and received in a session and a process in which information (eg, usage information, etc.) generated based on the measurement result is transmitted to the SMF 200. Etc. Reference is made again to FIG. Looking at flow detection in more detail, the UPF 100 specifies a specific flow designated from the SMF 200 among the flows constituting the session, for example, a source IP, a destination IP, a source port, a destination port, and a protocol specified by the SMF 200. Although only a specific flow corresponding to this may be detected, the UPF 100 according to an exemplary embodiment may detect all flows constituting a session supplied to the corresponding terminal 300.

The UPF 100 generates a flow detected by the UPF 100 in the form of a reporting flow having a predetermined format, and orders a plurality of generated reporting flows according to a predetermined criterion. In addition, when a predetermined transmission condition (or trigger condition) is satisfied, the UPF 100 performs one turn of a reporting flow of a preset number (X, where X is a natural number of 1 or more) among the plurality of flows arranged in this manner ( It transmits to the SMF 200 in bulk on a turn. Here, the term 'one turn' refers to a process of transmitting one unit message (for example, a transaction) in view of a protocol for transmitting a predetermined message.

Here, the reporting flow refers to information processed by the above-described predetermined format of the flow detected by the UPF 100, and such a reporting flow may be referred to as usage information in that it may include 'usage information'. It may be.

On the other hand, the format of the above-described reporting flow, the criteria for sorting the plurality of flows described above, the number X of flows to be transmitted in one turn among the plurality of the sorted flows described above, and the aforementioned X flows are transmitted to the SMF 200. The transmission condition for doing so may be according to the rule (SRR) received from the SMF (200) UPF (100). That is, the UPF 100 may generate, arrange, and transmit a reporting flow according to a condition required by the SMF 200.

Thus, according to one embodiment, the SMF can receive the reporting flow generated in accordance with the method optimized to collect from the UPF, thereby controlling the real-time of billing (how real-time billing is possible) or QoS control This can be improved and the implementation of a system with low latency is possible.

Next, the SMF 200 will be described.

The SMF 200 may determine the state of the communication interface (ie, N4) with the UPF 100 based on bandwidth or latency.

The SMF 200 sets a flow information report format (format). The set flow information report format is transferred from the SMF 200 to the UPF 100.

The flow information reporting format includes the following items, but is not limited thereto.

(1) Types of tuples to be included in a reporting flow among n tuples (specified by N, where N is a natural number of 1 or more) and their order

(2) The number X of reporting flows to be transmitted from the UPF 100 to the SMF 200 in one turn, where X is a natural number of 1 or more.

(3) the order in which X flows are ordered (specified by O, such as high order / low order, high order or low order)

(4) Whether the measurement method is based on the volume of the flow (the aggregated capacity of packets to be transmitted in one turn) / duration based / event based

(5) When the UPF 100 will report to the SMF 200, i.e., when to report

(6) Triggering conditions for reporting (volume threshold / duration threshold / event type)

Here, a tuple refers to an item that can be used to identify and specify each flow. As described above, tuples may have n types, and based on this, the flow information reporting format may be referred to as n-tuple flow (NTF), but the flow information reporting format is not limited to NTF.

The tuple type may include, but is not limited to, five such as a source IP (srcIP), a destination IP (dstIP), a source port (srcPort), a destination port (dstPort), and a protocol (Protocol).

On the other hand, detailed description or examples of each flow information reporting format will be described later.

The SMF 200 generates the aforementioned flow information reporting format in consideration of various factors. Factors that can be considered include types of services or products that the terminal 300 subscribes to, information on entry points or exit points in the area where the terminal 300 has entered, and whether the terminal 300 has handed over them. It may include, but is not limited to, whether the UPF 100 connected to the terminal 300 has changed or the state of a communication interface between the UPF 100 and the SMF 200.

For example, the SMF 200 may expand the type of tuple to the maximum and set X to 1 with respect to the terminal 300 subscribed to a relatively expensive plan. In this case, a reporting flow containing as much information as possible (since the type of tuple has been expanded to the maximum) may be transmitted from the UPF 100 to the SMF 200 in real time.

To this end, the SMF 200 may store a mapping table for setting each item constituting the flow information reporting format to what value or content when the above-mentioned various elements have any value, or may be equipped with an algorithm for setting the same. Can be.

The SMF 200 may reset the preset flow information reporting format. For example, if the UPF 100 attempts to transmit X reporting flows to the SMF 200 according to a preset flow information reporting format, the communication interface between the above-mentioned SMF 200 and the UPF 100 (N4). ) May not be able to handle this. In this case, the SMF 200 may reset the flow information reporting format itself by employing at least one of the following methods, but is not limited thereto.

-Reduce the number of tuples to be used in the reporting format

-Reduce the number X of reporting flows to be sent from the UPF 100 to the SMF 200 in one turn

-Increase the volume (the aggregate capacity of packets to be sent in one turn) for the flow to be sent in one turn

-Increase the transmission interval of the reporting flow according to the duration;

The SMF 200 transmits the flow information reporting format to the UPF 100, and then receives a reporting flow having the flow information reporting format from the UPF 100 and collects the flow.

Here, each of the following reporting flows received from the UPF 100 by the SMF 200 includes the following items for each flow, but is not limited thereto.

information on at least one of the tuples specified by the value N of the n tuples (eg, source IP (srcIP), destination IP (dstIP), source port (srcPort), destination port (dstPort), and protocol (Protocol) )

Volume information (at least one of the download volume, upload volume, or their combined volume)

Duration

Latency

The format of the flow information report and the flow for reporting are exemplarily shown in FIG. 3. Referring to FIG. 3, items of a flow information report format are shown in a dotted line labeled 'session Mod.Req', and items of a flow for reporting are shown in a dotted line labeled 'session Report.Req'.

More specifically, 'Measurement Method = Volume, Flow' among the items in 'session Mod.Req' indicates that the measurement method is volume based on the flow. 'Reporting Triggers = VOLTH, FLOTH' indicates that a reporting point is a point in time when the volume reaches a threshold or X, which is a threshold number of flows. 'Flow Threshold = #Flow = 256, NTF = 5' indicates that X, which is a threshold of the number of flows, is 256, and that N value of NTF is 5 in NTF.

'URT = FLOTH' among the items in 'session Report.Req' indicates that the trigger condition of the report is satisfied when the flow count reaches the threshold, and 'Flow Measure = 2MB / 1MB / 1MB' indicates the sum of the flows / Indicates download volume / upload volume. 'dstIP = 10.21.44.12, dstPort = 80, ...' indicates destination IP and destination port, respectively.

Hereinafter, a packet reporting method performed between the UPF 100 and the SMF 200 will be described with reference to FIG. 4. However, since the flow shown in FIG. 4 is merely exemplary, the spirit of the present invention is not limited to FIG. 4.

Referring to FIG. 4, the charging system 400 requests charging information for a predetermined terminal 300 from the SMF 200 (S100). The charging information refers to data that is the basis of charging, that is, information about the session itself or the flow configuring the session when the session is supplied to the terminal 300.

The SMF 200, which has received the billing information from the billing system 400, determines whether billing segmentation is necessary for the corresponding terminal 300. If billing segmentation is not needed, then a known billing process is already known, but if billing segmentation is required, the process described below is performed. The following description will be provided on the premise that billing segmentation is required.

The SMF 200 determines the state of the communication interface (ie, N4) with the UPF 100 based on the bandwidth or the latency (S110).

In addition, the SMF 200 sets a flow information report format (S120). In the setting process, the SMF 200 may use a pre-stored mapping table or a preloaded algorithm, and as a basis of the setting, the SMF 200 may be a type of a service or a product subscribed to by the terminal 300 and the terminal 300. Where is the entry point or exit point of the entry area, whether the terminal 300 has handed over, whether the UPF 100 connected to the terminal 300 has been changed, or between the UPF 100 and the SMF 200. The state of the communication interface can be taken into account.

The item of the flow information report format set in step S120 may include at least one of the above (1) to (6).

Among these, depending on how to set the value of N in (1), the type or number of tuples to be included in the item of the flow information reporting format may be set or changed. 5 illustrates this. Referring to FIG. 5, when N = 2, source IP and destination IP are included (2), when N = 3, source IP, destination IP and destination port are included (3), and when N = 5. Source IP, destination IP, source port, destination port and protocol are included (five).

Here, as the value of N increases, the number of reporting flows to be transmitted in one turn may increase because the flow may be generated by further classifying and grouping packets. This difference in the number of reporting flows to be transmitted in one turn according to the difference in the value of N may affect when the communication interface between the SMF 200 and the UPF 100 is not good. Therefore, in one embodiment, the value (eg, the number of tuples) of each item included in the flow information report format may be adaptively set according to the state of the communication interface between the SMF and the UPF.

In addition, although not shown in FIG. 5, the order of tuples to be included in an item of a flow information report format may be set or changed. For example, an item in the flow information reporting format may include an item, 'Create a flow for reporting in the order of source IP, destination IP, source port, destination port, and protocol'.In contrast,' destination IP, source IP, destination port ' Create a reporting flow in the following order: source port, protocol. To this end, after the SMF 200 obtains order information of tuples required by the charging system 400, the SMF 200 may set an order based on the information, but is not limited thereto.

Depending on how the value of X is set in (2), the number of reporting flows to be transmitted from the UPF 100 to the SMF 200 in one turn may be set or changed. 6 illustrates this. Referring to FIG. 6, since X = 999, a total of 999 reporting flows may be transmitted in one turn from X = 1 to X = 999. How many reporting flows are transmitted from the UPF 100 to the SMF 200 in a turn may affect the state of the communication interface between the SMF 200 and the UPF 100. That is, in one embodiment, the number of reporting flows to be transmitted in one turn may be adaptively set according to the state of the communication interface between the SMF and the UPF.

In addition, if X = 1, the UPF 100 transmits a reporting flow to the SMF 200 each time one flow is detected. That is, in this case, it is possible to transmit the flow for reporting in real time, which can improve the real time or QoS control performance of billing.

Depending on how the content or value of O is set in (3), the order of ordering the X flows to be transmitted in one turn can be set. The sort order may include, but is not limited to, the size of the latency or the size of the volume. 7 shows a reporting flow arranged according to the size of the latency. Referring to FIG. 7, since X = 10, a total of 10 reporting flows may be transmitted in one turn from X = 1 to X = 10. In addition, O = highest latency, that is, the latency is set to be sorted in order of highest (highest), so that the reporting flow with the largest latency is placed at the position of X = 1, and the latency is the highest. A small reporting flow is placed at the position X = 10. Whether the latency is transmitted first or the smaller first, or the volume is transmitted first or the smallest among the reporting flows transmitted in one turn may affect the real-time of charging. That is, in one embodiment, the transmission order or the sorting order of the reporting flow to be transmitted in one turn may be adaptively set.

In item (4), the measurement method may be set to one of volume (sum of capacity to be transmitted in one turn) based on the flow, duration based and event based. According to the volume based on the flow, the UPF 100 measures the volume, which is the sum of the packets to be transmitted in one turn, and according to the duration, the UPF 100 measures how much time has passed since the flow started. That is, the duration is measured, and according to the event basis, the UPF 100 measures whether a predetermined event (eg, whether the session is interrupted while the session is supplied or whether the terminal 300 is handed over) occurs. do. According to an embodiment, two or more of the three measurement methods may be combined, and in this case, each measurement method is performed in the UPF 100.

In item (6), a condition under which UPF 100 reports to SMF 200, that is, a trigger condition, is set. For example, the volume threshold (total amount of download packets / total amount of upload packets / total amount of download + upload packets) may be set, duration may be set, type of event may be set, and number of flows may be set. Can be.

The flow information reporting format described so far is illustrated by way of example in FIGS. 8 and 9. Fig. 8 shows the above items (1) to (3) in the flow information reporting format, and Fig. 9 shows (4) to (6) among the items in the flow information reporting format.

Referring to FIG. 8, if the bit of the ORDER is 1, it means to consider the sort order of the flow, and if it is 0, it is not considered. If the bit of NTFLW is 1, it means to consider the type or number of tuples. If it is 0, it is not considered. A bit of NOFLOW of 1 means to consider the number of reporting flows to be transmitted in one turn, and 0 means not to consider.

Referring to FIG. 9, NFLOW is a bit indicating whether a 'flow' is to be reported, EVENT is a bit indicating whether an event is a trigger condition of a report, and VOLUM is a packet condition indicating whether a total amount of packets is a trigger condition of a report. Bit is a bit indicating that the duration is a trigger condition of a report.

Referring back to FIG. 4, the SMR 200 determines whether the flow information report format set in step S120 is appropriate (S210). In the determination process of S210, it is determined whether the UPF 100 transmits a reporting flow to the SMF 200 according to the flow information report format set in step S120. In this process, resources of the UPF 100, resources of the SMF 200, or a state of a communication interface between the UPF 100 and the SMF 200 may be considered.

If it is determined that it is not appropriate, the SMF 200 may reset the flow information report format as follows, but is not limited thereto (S120).

-Reduce the number of tuples to be used in the reporting format

-Reduce the number X of flows to be sent from the UPF 100 to the SMF 200 in one turn

-Increase the volume (the aggregate capacity of packets to be sent in one turn) for the flow to be sent in one turn

-Increase the transmission interval of the reporting flow according to the duration;

If it is determined in step 210 that the flow information report format is appropriate, the SMF 200 transmits the flow information report format determined to be appropriate in step S210 to the UPF 100 (S300).

Then, the UPF 100 detects (or retrieves) all flows constituting the session with respect to the session of the terminal 300 in which the charging system 400 requests the charging information (S300).

All flows detected in step S300 are generated as flows for reporting according to the flow information report format received in step S230, and are sorted (organized) according to a predetermined criterion (S310).

For example, each reporting flow may include a tuple according to the method defined in (1) of the above-described flow information reporting format. In addition, the number (X) of reporting flows to be transmitted in one turn may be determined according to the scheme determined in (2), and each reporting flow may be arranged according to the scheme determined in (3).

The UPF 100 determines whether the reporting condition is satisfied (S320). If not satisfied, the UPF 100 goes to step S300 and repeats the following steps.

However, the UPF 100 transmits a reporting flow if the aforementioned reporting condition is satisfied (S330). Conditions are met, for example, whether the number of reporting flows has reached X, whether any flows have reached a volume threshold among reporting flows, whether there are flows that have reached a duration threshold during reporting flows, and during reporting flows. It may be considered whether there is a flow corresponding to a predefined event. In addition, if any one of at least two of these conditions is satisfied, a satisfactory reporting flow may be transmitted at each satisfying condition.

At this time, FIG. 10 exemplarily shows the format of X reporting flows transmitted from the UPF 100 to the SMF 200 in one turn. Referring to FIG. 10, an ORDER indicates whether a plurality of flows transmitted in one turn are arranged in a predetermined order, and the NTFLW indicates matters related to the types and order of tuples included in each of the plurality of flows transmitted in one turn. NOFLOW indicates whether reference should be made to the number of flows transmitted in one turn.

Referring back to FIG. 4, the SMF 200 collects X reporting flows received in step S330 (S400). The X reporting flows are collected and finally passed to the charging system 400.

As described above, according to an embodiment, the SMF may receive a reporting flow generated according to a method optimized to be collected from the UPF, so that the real time (how real-time charging is possible) or QoS of the billing may be applied. The control performance can be improved, and it becomes possible to implement a system having low latency.

Meanwhile, the packet reporting method according to an embodiment may be implemented in a computer readable recording medium storing a computer program programmed to perform each step according to the method, and also the computer reading programmed to perform each step according to the method. It can be implemented by a computer program stored in a possible recording medium.

The above description is merely illustrative of the technical idea of the present invention, and those skilled in the art to which the present invention pertains may make various modifications and changes without departing from the essential quality of the present invention. Therefore, the embodiments disclosed in the present invention are not intended to limit the technical idea of the present invention but to describe the present invention, and the scope of the technical idea of the present invention is not limited by these embodiments. The scope of protection of the present invention should be interpreted by the following claims, and all technical ideas falling within the equivalent scope of the present invention should be construed as being included in the scope of the present invention.

According to one embodiment, the SMF can receive flows from the UPF in a manner suitable for the SMF itself, which is optimized for aggregating a plurality of flows. The control performance can be improved, and it becomes possible to implement a system having low latency.

100: User Plane Function Unit (UPF)
200: Session Management Facility (SMF)

Claims (16)

A session management function (SMF) for setting a flow information reporting format and transmitting the set flow information reporting format to a user plane function (UPF);
Receiving the flow information reporting format from the session management function device, generating a reporting flow conforming to the received flow information reporting format based on each of a plurality of flows constituting a session, A user plane function device for sending at least one of the reporting flows to the session management function device;
Packet reporting system. The method of claim 1,
The flow information report format,
It includes information about the number or arrangement order of tuples included in the reporting flow or capacity information of packets included in the reporting flow.
Packet reporting system. The method of claim 2,
The session management function device,
Setting the number of tuples based on a state of a communication interface connecting the session management function device and the user plane function device;
Packet reporting system. The method of claim 1,
The flow information report format,
Including information about the number of flows for reporting to be sent in one turn from the user plane functional device to the session management functional device.
Packet reporting system. The method of claim 4, wherein
The session management function device,
Setting the number of reporting flows to be transmitted in one turn based on a state of a communication interface connecting the session management function device and the user plane function device.
Packet reporting system. The method of claim 4, wherein
The flow information report format,
And further comprising information about a plurality of ordering flows to be sent on the turn.
Packet reporting system. The method of claim 6,
The information on the alignment,
Sorting based on at least one of a volume of each of the reporting flows or a latency of each of the reporting flows
Packet reporting system. The method of claim 1,
The reporting flow sent to the session management function device is
Contains information corresponding to at least one of a source IP (srcIP), a destination IP (dstIP), a source port (srcPort), a destination port (dstPort) and a protocol (Protocol)
Packet reporting system. The method of claim 1,
The reporting flow sent to the session management function device is
At least one of the capacity of the upload packet, the capacity of the download packet or the sum of the capacity of the upload packet and the download packet included in the transmission flow for reporting.
Packet reporting system. The method of claim 1,
The reporting flow sent to the session management function device is
Including duration information or latency information of a flow included in the transmitted reporting flow
Packet reporting system. The method of claim 1,
The user plane function device,
Whenever one flow is detected, a reporting flow generated based on the detected one flow is transmitted to the session function management apparatus.
Packet reporting system. The method of claim 1,
The user plane function device,
When a number of flows to be transmitted to the session management function device is detected in one turn, a reporting flow generated based on the detected number of flows is transmitted to the session management function device in one turn.
Packet reporting system. The method of claim 1,
The user plane function device,
If the flow detected by the user plane function device includes a packet equal to or greater than a predefined summation capacity, a reporting flow generated based on the detected flow is transmitted to the session management function device in one turn.
Packet reporting system. The method of claim 1,
The user plane function device,
When a predefined event occurs, a reporting flow generated on the basis of the flow detected by the user plane function device is transmitted to the session management function device in one turn until the occurrence of the event.
Packet reporting system. The method according to any one of claims 12 to 14,
If there are a plurality of reporting flows transmitted to the session management function device in one turn, the plurality of reporting flows may be either latency for each reporting flow or capacity of a packet included in each reporting flow. Transmitted to the session management function device in one turn according to a sorted order based on
Packet reporting system. A packet reporting method performed by a user plane functional device,
Receiving a flow information report format from a session management function device;
Generating a reporting flow conforming to the received flow information reporting format based on each of the plurality of flows constituting the session;
Transmitting at least one of the generated reporting flows to the session management function device;
Packet report method

Images