KR20200040134A - Method for determining traffic size - Google Patents

Abstract

According to an embodiment of the present invention, a method for calculating a recommended size of a packet performed by a session management function comprises the steps of: receiving size information of a user plane packet; calculating a recommended size for the user plane packet based on the received size information of the user plane packet; and controlling the calculated recommended size to be transmitted to a terminal.

Description

Traffic size calculation method {METHOD FOR DETERMINING TRAFFIC SIZE}

The present invention relates to a method for calculating traffic size.

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

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

In the 5G system, a network structure is defined to support the terminal, base station (access), core, and server from end to end, and a single node (eg, S-GW, P-GW, etc.) in the existing LTE (4G) is defined. By separating the functions of control signaling and data transmission / reception, which have been performed in a complex manner, a network structure in which a control signaling function area (or control area) (Control Plane) and a data transmission / reception function area (or user area) is divided is separated. Is defined.

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

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

PCT Patent Publication, 2018-008944 (released on January 11, 2018)

In general, the larger the packet size, the better the delivery efficiency while the longer the latency, whereas the smaller the packet size, the lower the delivery efficiency while the shorter the latency.

In a 5G system supporting a high-reliability-low-latency (URLLC) service, it is important to calculate a packet size capable of meeting delivery efficiency and latency above a certain level in packet delivery.

The problem to be solved by the present invention is to calculate a packet size that satisfies a certain level of delivery efficiency and latency in a 5G system, and then allow a terminal to set and transmit a packet according to the packet size. Is to provide

However, the problem to be solved of the present invention is not limited to those mentioned above, and another problem not to be solved can be clearly understood by a person having ordinary knowledge to which the present invention belongs from the following description. will be.

A method for calculating a recommended size of a packet performed by a session management function according to an embodiment is based on receiving size information of a user plane packet and based on size information of the received user plane packet. And calculating the recommended size for the user flat packet, and controlling the calculated recommended size to be transmitted to the terminal.

The method for setting the size of a user plane packet performed by a terminal according to an embodiment includes receiving a recommended size of a user plane packet, setting a user plane packet to have the received recommended size, and having the recommended size. And transmitting the set user plane packet to the base station.

According to an embodiment, the terminal may dynamically set the packet size itself. In addition, the terminal can perform the above-described packet size setting not only when a packet is newly transmitted, or even when a packet is already being transmitted.

In addition, the terminal may set the packet size for each packet, for each flow, or for each session. Accordingly, if there is a packet requiring a low-latency service, it is possible to select the packet and set the packet size.

1 exemplarily illustrates an architecture of a 5G system according to an embodiment.
FIG. 2 exemplarily shows a part of the configuration shown in FIG. 1.
Figure 3 shows the session and the flow and the packets included in the flow.
4 exemplarily shows a table managed by the SMF.
5 exemplarily shows a table used when the terminal sets the packet size.
6 exemplarily shows a procedure of a traffic size calculation method according to an embodiment.

Advantages and features of the present invention, and methods for achieving them will be clarified with reference to embodiments described below in detail together with the accompanying drawings. However, the present invention is not limited to the embodiments disclosed below, but may be implemented in various different forms, and only the embodiments allow the disclosure of the present invention to be complete, and common knowledge in the art to which the present invention pertains It is provided to completely inform the person having the scope of the invention, and the present invention is only defined by the scope of the claims.

In describing embodiments of the present invention, when it is determined that a detailed description of known functions or configurations may unnecessarily obscure the subject matter of the present invention, the detailed description will be omitted. In addition, terms to be described later are terms defined in consideration of functions in an embodiment of the present invention, which may vary according to a user's or operator's intention or practice. Therefore, the definition should be made based on the contents throughout this specification.

Hereinafter, 'packet' and 'traffic' are used interchangeably.

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

The 5G system itself shown in the architecture 10 of FIG. 1 will be described. 5G system is an advanced technology from 4G LTE mobile communication technology. This 5G system is an extension of the existing mobile communication network structure (Evolution) or a clean-state structure through a new radio access technology (RAT), an extended technology of Long Tern Evolution (LTE), and eLTE. (extended LTE), non-3GPP access, etc. are supported.

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

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

1, the authentication server function (AUSF: Authentication Server Function), access and mobility management function (AMF: (Core) Access and Mobility Management Function) 230, session management function (SMF: Session Management Function) 220 ), Policy Control Function (PCF), Application Function (AF), Unified Data Management (UDM), Data Network (DN) 500, User Plane Function ( UPF: User plane function (100), (wireless) access network ((R) AN: (Radio) access network, or base station) 400 and UE (User Equipment) 300 are illustrated.

Among them, the UPF 100 is a component belonging to a user plane in a 5G system, and may be referred to as the user plane device 100 or the UPF 100 in this specification.

In addition, SMF 220, AMF 230, AUSF, NSSF, NEF, NRF, PCF, UDM and AF are components belonging to a control plane separate from the user plane, each of which is a control plane. It may be referred to as a device (control plane function, CPF).

On the other hand, UPF (100), SMF (220), AMF (230), AUSF, NSSF, NEF, NRF, PCF, UDM and AF are combined will be referred to hereinafter as the core network network (200).

Some of the components belonging to the core network network 200 are connected by a service based interface (SBI) 210. In addition, the SMF 220 and the UPF 100 are connected by an N4 interface, the AMF 230 and the UE 300 are connected by an N1 interface, and the AMF 230 and the base station 400 are N2. It is connected by an interface, and the base station 400 and the UPF 100 are connected by an N3 interface.

FIG. 2 exemplarily shows a part of the configuration shown in FIG. 1. 2 shows a terminal 300, a base station 400, a core network network 200, and a data network 500. Packets sent from the terminal 300 to the base station 400 may be delivered to the data network 500 through the core network network 200, and conversely, packets from the data network 500 are processed by the core network 200. It can be transmitted to the terminal 300 through the base station 400. In the process of transmitting the packet, the terminal 300 may be provided with various services, such as a session, called URLLC, eMBB, mMTC.

Here, the packet transmitted between the above-described terminal 300 and the data network 500 is referred to as a 'user plane packet', and in this specification, the 'packet' refers to a user plane packet.

According to an embodiment, when a session is provided to the terminal 300, a packet (user plane packet) associated with the session passes through the UPF 100. The UPF 100 acquires information about the packet size of a packet passing through it per packet, per flow, or per session. The SMF 220 receives this packet size information from the UPF 100. Based on the received packet size information, the SMF 220 calculates the recommended size of the packet. The recommended size of the packet thus calculated is delivered to the terminal 300. Upon receiving the recommended size, the terminal 300 sets (changes) the packet size according to the recommended size. In this case, the terminal 300 may set (change) the packet size for each packet, for each flow, or for each session.

That is, according to an embodiment, the terminal 300 that sets the packet size according to the recommended size is the terminal 300. In addition, the terminal 300 may set the packet size to the recommended size at any time, for example, when a new packet is to be transmitted or while the packet is already being transmitted. That is, according to an embodiment, the terminal 300 may dynamically set (change) the packet size.

Also, the terminal 300 may set a packet size for each packet, for each flow, or for each session. Accordingly, if there is a packet requiring a low-latency service, it is possible to select the packet and set the packet size.

Hereinafter, a technical idea according to one embodiment will be described in more detail.

When a session is provided to the terminal 300, a packet (user plane packet) associated with the session passes through the UPF 100. 3 shows the relationship between packets 311 to 316, flows 310 to 330, and session 301 passing through UPF 100. Referring to FIG. 3, the session 301 is composed of a plurality of flows 310 to 330. Each of the plurality of flows 310 to 330 includes at least one packet 311 to 316 (FIG. 3 shows that only the packet is included in the flow 310, but at least one packet is included in other flows 320 and 330). This may be included).

In the flows 310 to 330, packets having the same packet size may be included, or packets having different packet sizes from each other may be included. For example, referring to FIG. 3, in the case of the first flow 310, packets marked with IDs 311, 312, 314, and 315 indicate packets having the same packet size, and packets marked with IDs 313 and 316 also have packet sizes with each other. Represents the same packet. On the other hand, the packet size of the packets indicated by the identification numbers 311, 312, 314, 315 is different from the packet size of the packets indicated by the identification numbers 313 and 316. This is applicable to the second flow 320 and the third flow 330 as well.

The UPF 100 measures the packet size of packets passing through it. At this time, the header of the packet (Outer Header and Inner Header) may or may not be included in the measurement target.

Meanwhile, the packet size can be measured for each packet. When measuring for each packet, the packet can be identified using n-tuple (source IP, destination IP, source port, destination port and protocol), and the packet size as a result of measurement is Matching with this n-tuple, it can be stored for each packet.

Of course, the packet size may be measured per flow or per session as well as packets. Here, measuring per flow means collecting packet sizes of at least one packet included in a flow, and measuring per session means collecting packet sizes of at least one packet included in each of a plurality of flows constituting a session. to be.

The UPF 100 calculates a distribution value or statistical value for the measured packet size. For example, the UPF 100 may calculate a distribution chart for the number of sections by dividing the maximum and minimum values of the measured packet size into a plurality of sections, and then measuring the number of packet sizes corresponding to each section. Alternatively, the UPF 100 may calculate statistical values. For example, the UPF 100 may calculate and store as a statistical value by calculating a section (max), a section (min), an average value (average), or a quartile (quartile) having the largest number of packet sizes among each section described above. have.

These results, measured by the UPF 100, are transmitted to the SMF 220.

The SMF 220 receives the measurement result for the packet size from the UPF 100. The received measurement results may be measured for each packet, but are not limited thereto. For example, according to an embodiment, the received measurement result is a collection of size information of at least one packet included in a predetermined flow, or the size of at least one packet included in each of a plurality of flows constituting a predetermined session. The information may be collected.

Based on the above-mentioned measurement result received from the UPF 100, the SMF 220 calculates at least one recommended size. There can be several methods of calculation. Let's take one of them as an example. As described above, the measurement result may include a distribution chart for the number of packet sizes for each section. The SMF 220 is the average packet size and the packet size in the section min having the smallest number of packet sizes among each section. The size or the packet size in the largest section (max) can be calculated as the recommended size, respectively.

At this time, according to an embodiment, the recommended size may be calculated for each flow or for each session.

The SMF 220 may control the recommended size to be transmitted to the terminal 300. The transmission method may include, for example, a method that is transmitted to the terminal 300 through an AMF (Access and Mobility Function) or a method that is transmitted to the terminal 300 through a predetermined application in the session management device 220, but is not limited thereto. It is not.

Meanwhile, the SMF 220 may store and manage the calculated recommended size as a table shown in FIG. 4. Referring to FIG. 4, the first row indicates what items the table contains. Among them, Flow ID indicates the ID of the flow to which the packet belongs, and Flow Information Description indicates the n-tuple (source IP, destination IP, source port, destination port, and protocol) of the packet. Service (Slice ID Description) indicates what service the packet is related to, and the Latency distribution (Min, Avg, Max) is the minimum / average / maximum value of the latency measured in advance for transmission of the packet. The packet distribution diagram (Min, Avg, Max) sequentially represents the minimum / average / maximum value of the packet size.The setting method is that the information stored and managed in the table of Fig. 4 is transmitted to the terminal 300 For example, 3GPP is a method in which the recommended size is transmitted to the terminal 300 through the AMF 230, and Non-3GPP (App setting) has a recommended size of NEF or a predetermined size by a predetermined application included in the SMF 220. It shows a method transmitted to the terminal 300 through AF or the like.

Here, latency can be measured per flow, per session, or per slice ID. In addition, latency can be unidirectional or bidirectional. Here, 'bidirectional' may generally mean a round trip time (RTT), where RTT means, for example, a time difference between a point when an uplink packet passes and a point when a downlink packet passes. That is, the RTT may be a value calculated by including a packet error, timeout or retransmission according to wire / wireless condition and terminal / termination.

From the second row, each represents a packet and information about the packet. Looking at the packet in the second row, the packet is included in the flow with the flow ID of 0xF0212, the service ID is mMTC, the latency distribution is (1ms, 2ms, 4ms), and the packet distribution is (30,35,100). The second packet is transmitted to the terminal 300 through the 3GPP method, that is, through the AMF 230.

Next, the AMF 230 will be described. The AMF 230 may receive the recommended size for a specific packet from the SMF 220 and deliver it to the terminal 300 through NAS signaling, and in some cases, a recommended size for a specific flow or a recommended size for a specific session It may be received and delivered to the terminal 300 through NAS signaling.

Next, the terminal 300 will be described. The terminal 300 receives the recommended size and information about the packet. It is as described above that the source providing the recommended size and information on the terminal 300 is a predetermined application in the Access and Mobility Function (AMF) or SMF 220.

The terminal 300 stores and manages the received recommendation size and information related thereto. In FIG. 5, the recommended size managed by the terminal 300 and information related thereto are exemplarily illustrated in the form of a table. Referring to FIG. 5, the first row indicates what items the table contains. Among them, Flow / Wildcard indicates the n-tuple (source IP, destination IP, source port, destination port and protocol) of the corresponding packet. Slice / Description indicates which service the packet relates to. The data size set represents a candidate value of a recommended size for a corresponding packet, and the candidate value may be calculated based on a minimum / average / maximum value of a packet distribution diagram created by the SMF 220. The size change setting indicates the critical latency, which will be described later.

From the second row, each represents a packet and information about the packet. Looking at the packet in the second row, the packet has a destination IP of 11.121.88.41, a destination port of 443, and is a packet delivered to the stock trading server by URLLC service. The recommended size is 4, and 40,50,80,90. In addition, the critical latency is 2ms.

The terminal 300 sets the packet size based on the stored information. There can be various types of settings, and one of them will be described as an example. Looking at the packet in the second row as an example, first, select '40', the recommended size having the lowest value among the data size sets. Accordingly, the packet size of the packet to be transmitted to the base station 400 is set to '40'. The terminal 300 acquires the latency required in the process of transmitting a packet with a packet size of 40 to the base station 400. If the latency is within 2 ms for a predetermined period, the terminal 300 changes the packet size to a value greater than 40, for example, 50. Accordingly, the packet size of the packet transmitted to the base station 400 is '50'. However, when the latency exceeds 2 ms for a predetermined period, the terminal 300 maintains the packet size at 40 or sets it to a value smaller than that.

If the latency is within 2ms within a predetermined period, and the packet size is 50, the terminal 300 acquires latency again. If the latency is within 2ms for a predetermined period, the terminal 300 once again sets the packet size to a value greater than 50, for example, 80, but if the latency exceeds 2ms for a predetermined period, leave the packet size as it is, or Lower it from 50 to 40.

The above-described procedure in which the terminal 300 sets the recommended size of the packet is performed when, for example, handover is performed, NAS signaling is performed, or radio access technology (RAT) used by the terminal 300 is changed. It can be, but is not limited to.

That is, in one embodiment, the terminal 300 may dynamically set the packet size in consideration of latency. Accordingly, a packet size capable of satisfying transmission efficiency and latency above a certain level can be calculated, and thus it is possible to simultaneously satisfy two conditions of low-latency conditions and delivery efficiency.

Meanwhile, so far, only the terminal 300 sets a recommended size for each packet, but the spirit of the present invention is not limited to this. For example, according to an embodiment, the terminal 300 may set a different recommended size for each flow or for each session, and may set the recommended size in consideration of latency even when setting for each flow or for each session.

On the other hand, the terminal 300 may set the recommended size of the packet before sending the packet, but may set (change) the recommended size of the packet at any time in the middle of sending the packet. Therefore, when the communication situation changes rapidly depending on the situation, it is possible to set (change) the recommended size of the packet to reflect this situation.

6 exemplarily shows a procedure of a traffic size calculation method according to an embodiment. However, since FIG. 6 is merely exemplary, the spirit of the present invention is not limited to being illustrated in FIG. 6.

Referring to FIG. 6, the terminal 300 exchanges packets with a predetermined packet size through the PDU session with the data network 500 (S100).

During step S100, the SMF 220 transmits a request for measuring the packet size to the UPF 100 (S200).

Then, the UPF 100 measures the packet size according to the request (S210).

The UPF 100 may measure the packet size for each packet. When measuring for each packet, the packet can be identified using n-tuple (source IP, destination IP, source port, destination port and protocol), and the packet size as a result of measurement can be stored for each packet by matching this n-tuple. have. Of course, the packet size may be measured per flow or per session as well as per packet. Measuring per flow means collecting packet sizes of at least one packet included in a flow, and measuring per session is a plurality of sessions. This means that the packet sizes of at least one packet included in each of the four flows are collected.

The UPF 100 calculates a distribution value or statistical value for the measured packet size. For example, the UPF 100 may calculate a distribution chart for the number of sections by dividing the maximum and minimum values of the measured packet size into a plurality of sections, and then measuring the number of packet sizes corresponding to each section. Alternatively, the UPF 100 may calculate statistical values. For example, the UPF 100 may calculate and store as a statistical value by calculating a section (max), a section (min), an average value (average), or a quartile (quartile) having the largest number of packet sizes among each section described above. have.

The UPF 100 transmits the measured result to the SMF 220 (S220).

Based on the measurement result received in step S220, the SMF 220 calculates at least one recommended size for each packet (S230). There can be a variety of calculation methods. Since this has already been described, a detailed description will be omitted.

The SMF 220 may control the recommended size calculated in step S230 to be transmitted to the terminal 300. For example, the SMF 220 may be controlled to be transmitted to the terminal 300 through an Access and Mobility Function (AMF) as shown in FIG. 6, and unlike the one shown in FIG. 6, a predetermined application in the SMF 220 may be used. It may be controlled to be transmitted directly to the terminal 300 through.

The AMF 230 delivers the result received according to step S240 to the terminal 300 through NAS signaling (S250).

The terminal 300 receives the recommended size and information about the packet (S300). At this time, as described above, the terminal 300 can receive the recommended size through a predetermined application in the Access and Mobility Function (AMF) or SMF 220.

The terminal 300 sets the packet to be transmitted to the base station 400 to have a recommended size based on the information received in step S300. Since the setting method has already been described, a description thereof will be omitted.

When the setting of the recommended size is completed, the terminal 300 responds to the AMF 230 that the setting is completed (S310), and thereafter the AMF 230 and the SMF 220 sequentially respond (S320, S330).

Thereafter, the terminal 300 exchanges a packet having a recommended size through the PDU session with the data network 500 (S400).

Here, FIG. 6 illustrates a process in which the packet size is set (changed) to the recommended size while the terminal 300 exchanges packets with the data network 500 through a PDU session. That is, according to one embodiment, the terminal may set the packet size to the recommended size at any time even while transmitting the packet.

In addition, the terminal may set the packet size per packet, per flow, or per session. Accordingly, if there is a packet requiring a low-latency service, it is possible to select the packet and set the packet size.

On the other hand, the method for setting the size of the above-described packet is stored in a computer-readable recording medium or a computer-readable recording medium that stores a computer program programmed to perform each step included in the method. It may be implemented in the form of a computer program programmed to perform the steps.

The above description is merely illustrative of the technical idea of the present invention, and those of ordinary skill in the art to which the present invention pertains may make various modifications and variations 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 spirit of the present invention, but to explain, and the scope of the technical spirit 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 within the scope equivalent thereto should be interpreted as being included in the scope of the present invention.

According to an embodiment, in a 5G system supporting a high-reliability-low-delay (URLLC) service, a packet size capable of satisfying delivery efficiency and latency in a packet delivery to a certain level or more may be calculated.

100: user flat device

Claims (13)

A method for calculating a recommended size of a packet performed by a session management function,
Receiving size information of a user plane packet;
Calculating a recommended size for the user plane packet based on the received size information of the user plane packet;
And controlling the calculated recommended size to be transmitted to the terminal.
How to calculate the recommended packet size. According to claim 1,
The received user plane packet size information,
The size information of at least one user plane packet included in a given flow is aggregated, or the size information of at least one user plane packet included in each of a plurality of flows constituting a given session is included. Aggregated
How to calculate the recommended packet size. According to claim 1,
The calculating step,
The recommended size to be set in the flow is set differently for each flow, or the recommended size to be set in the session is set differently for each session.
How to calculate the recommended packet size. According to claim 1,
The calculating step,
Calculating the recommended size based on the distribution or statistics of the received user plane packet size
How to calculate the recommended packet size. According to claim 1,
The controlling step,
The calculated recommended size is controlled to be transmitted to the terminal through an AMF (Access and Mobility Function) or controlled to be transmitted to the terminal through a predetermined application in the session management device
How to calculate the recommended packet size.
As a method for setting the size of a user plane packet performed by the terminal,
Receiving a recommended size of the user plane packet,
Setting a user plane packet to have the received recommended size,
And transmitting a user plane packet set to have the recommended size to a base station.
How to set the size of user plane packets. The method of claim 6,
The recommended size received above,
It is received from the AMF or received from the session management device through a predetermined application in the session management device.
How to set the size of user plane packets. The method of claim 6,
The setting step,
The recommended size to be set in the flow is set differently for each flow, or the recommended size to be set in the session is set differently for each session.
How to set the size of user plane packets. The method of claim 6,
The recommended size received above,
Containing a plurality of different values
How to set the size of user plane packets. The method of claim 9,
The above method,
Further comprising the step of measuring the latency when the user plane packet is set to have any one of the plurality of recommended sizes to be transmitted to the base station,
The setting step,
If the measured latency is within a reference range, each user plane packet is set to have a recommendation size other than the one recommendation size.
How to set the size of user plane packets. The method of claim 9,
When handover is performed, NAS signaling is performed, or when a radio access technology (RAT) used by the terminal is changed, a recommended size set for each of the user plane packets among the plurality of recommended sizes is the plurality of recommended sizes Further comprising the step of changing to another recommended size included in
How to set the size of user plane packets. A computer program stored on a computer readable recording medium programmed to perform each step of the method of claim 1. A computer-readable recording medium storing a computer program programmed to perform, including each step of the method of claim 1.

Images