KR20190129378A - Method and apparatus for transmitting and receiving packet through unified transport network in communication system - Google Patents

Abstract

Disclosed are a method and apparatus for transmitting and receiving a packet through a unified transport network in a communication system. According to the present invention, a packet transmission method performed by a gateway comprises the steps of: receiving an IP packet including 5-tuple from a core network; if the destination indicated by the 5-tuple included in the IP packet is a base station, performing an encapsulation operation on the IP packet to include an address of communication node #1 connected to the base station among communication nodes constituting the unified transport network; and transmitting the encapsulated IP packet to the base station via the communication nodes. Accordingly, performance of the communication system can be improved.

Description

METHOD AND APPARATUS FOR TRANSMITTING AND RECEIVING PACKET THROUGH UNIFIED TRANSPORT NETWORK IN COMMUNICATION SYSTEM}

The present invention relates to a technique for transmitting and receiving packets through an integrated delivery network, and more particularly, to a technique for transmitting and receiving packets between a base station and an evolved packet core (EPC) in an integrated delivery network.

5G service requirements (e.g., delay, jitter, capacity, etc.) for backhaul and fronthaul networks are becoming more stringent due to the rapid increase in user traffic. Is getting. To meet 5G service requirements, an unified transport network can be introduced that integrates the backhaul network and the fronthaul network. An integrated delivery network may consist of a plurality of communication nodes, which may be connected using a wired link (eg, optical, high performance copper, etc.) or a wireless link (eg, mmWave based wireless link). have.

The communication node constituting the unified forwarding network may be an Xhaul control infrastructure (XCI) providing an unified control plane function or an Xhaul packet forward element (XFE) providing an unified data plane function. . The integrated delivery network may be established based on software defined network (SDN) technology. Integrated forwarding networks provide connectivity between remote radio heads (RRHs) and cloud-digital units (C-DUs) and base stations (eg, small base stations) and evolved packet cores (EPCs) (eg, EPC devices) Can provide connectivity between The connection function between the RRH and the C-DU may be a function of the fronthaul network, and the connection function between the base station and the EPC may be a function of the backhaul network.

 In a converged forwarding network, an end communication node may transmit a packet using an IP address (eg, an IP address assigned by a packet data network (PDN) -gateway (P-GW)). The IP address of a base station (eg, a small base station) connected with an end communication node of the integrated delivery network may be different from the IP address of the end communication node. In this case, the end communication node may transmit an IP packet having an IP address different from its own IP address (for example, the base station's IP address) to the P-GW belonging to the integrated delivery network. However, when a 5-tuple based packet filtering rule is applied in the P-GW, IP packets delivered from the end communication node to the P-GW may be dropped. The 5-tuple may include a source IP address, a destination IP address, a source port number, a destination port number, and a protocol identifier.

In addition, the EPC may be connected to the P-GW of the integrated delivery network, and may support a function of transmitting an IP packet to the base station through the integrated delivery network. In this case, the destination IP address of the IP packet transmitted from the EPC to the P-GW may be set to the IP address of the base station instead of the end communication node. When the 5-tuple based packet filtering rule is applied in the P-GW, IP packets delivered from the EPC to the P-GW may be dropped.

An object of the present invention for solving the above problems is to provide a method and apparatus for transmitting and receiving packets between a base station and an evolved packet core (EPC) in an integrated delivery network.

A packet transmission method performed by a gateway belonging to an integrated delivery network according to a first embodiment of the present invention for achieving the above object comprises the steps of: receiving an IP packet including 5-tuples from a core network; When the destination indicated by the included 5-tuple is a base station, an encapsulation operation for the IP packet is performed to include an address of communication node # 1 connected to the base station among the communication nodes constituting the integrated forwarding network. And transmitting the encapsulated IP packet to the base station via the communication nodes.

Here, the communication node # 1 may be connected to another communication node constituting the integrated delivery network through a wireless link, and the IP address of the communication node # 1 may be set by the gateway.

Here, the IP address of the communication node # 1 may be set differently from the IP address of the base station.

Here, the 5-tuple of the IP packet may include a source IP address, a destination IP address, a source port number, a destination port number, and a protocol ID, wherein the source IP address is an IP address of a communication node belonging to the core network. It may be set to, and the destination IP address may be set to the IP address of the base station.

Here, the encapsulated IP packet may comprise a six-tuple, wherein the six-tuple may include a communication node IP address, a source IP address, a destination IP address, a source port number, a destination port number and a protocol ID. The communication node IP address may be set to an IP address of the communication node # 1, the source IP address may be set to an IP address of a communication node belonging to the core network, and the destination IP address may be set to the IP address. It may be set to the IP address of the base station.

In this case, the encapsulation operation may be performed on the IP packet classified as SDF.

Here, the encapsulated IP packet is transmitted between the communication node # 2 and the communication node # 2 and the communication node # 1 formed between the communication node # 2 and the gateway connected through the wireless link among the communication nodes # 1. May be transmitted over the formed radio bearer.

Here, the integrated delivery network may support the operation of transmitting and receiving the IP packet between the access network to which the base station belongs and the core network.

A packet transmission method performed by communication node # 1 belonging to an integrated delivery network according to a second embodiment of the present invention for achieving the above object includes wireless communication with the communication node # 1 among communication nodes belonging to the integrated delivery network. Receiving an IP packet containing 6-tuples from communication node # 2 connected over a link, and generating a decapsulated IP packet containing 5-tuples by performing a decapsulation operation on the IP packet. And sending the decapsulated IP packet to a destination indicated by the 5-tuple of the decapsulated IP packet, wherein the six-tuple comprises a communication node IP address, a source IP address, a destination. An IP address, a source port number, a destination port number, and a protocol ID, wherein the communication node IP address indicates the IP address of the communication node # 1, and the source IP Cows indicating the IP address of a communication node belonging to the core network, and the destination IP address indicates the IP address of the base station belonging to the access network.

Here, the IP address of the communication node # 1 may be set by a gateway belonging to the integrated delivery network in an attach procedure, and the IP address of the communication node # 1 may be set differently from the IP address of the base station.

Wherein the 5-tuple of the decapsulated IP packet is the source IP address, the destination IP address, the source port number, the destination port number and the protocol ID except for the communication node IP address among the 6-tuples. It may include.

Here, the IP packet including the 6-tuple may be generated by a gateway belonging to the integrated delivery network, and the IP packet including the 6-tuple is an S5 bearer formed between the gateway and the communication node # 2. And a radio bearer formed between the communication node # 2 and the communication node # 1.

Here, the communication node # 1 may communicate with the communication node # 2 using the LTE protocol.

A packet transmission method performed by a gateway belonging to an integrated forwarding network according to a third embodiment of the present invention for achieving the above object comprises: receiving an IP packet including 6-tuple from communication node # 1 belonging to the integrated forwarding network; Receiving, generating a decapsulated IP packet comprising a 5-tuple by performing a decapsulation operation on the IP packet, and directed by the 5-tuple of the decapsulated IP packet Sending the decapsulated IP packet to a destination, wherein the six-tuple includes a communication node IP address, a source IP address, a destination IP address, a source port number, a destination port number, and a protocol ID; The communication node IP address is a communication node connected to the base station indicated by the source IP address among the communication nodes constituting the integrated forwarding network. Indicates an IP address of # 2, the source IP address indicates an IP address of the base station belonging to an access network, and the destination IP address indicates an IP address of a communication node belonging to a core network.

Here, the communication node # 2 may be connected to the communication node # 1 through a wireless link, and the IP address of the communication node # 2 may be set by the gateway.

Here, the IP address of the communication node # 2 may be set differently from the IP address of the base station.

Wherein the 5-tuple of the decapsulated IP packet is the source IP address, the destination IP address, the source port number, the destination port number and the protocol ID except for the communication node IP address among the 6-tuples. It may include.

Here, the decapsulation operation may be performed on the IP packet classified as SDF.

Here, the IP packet may be generated by the communication node # 2 and received through a radio bearer formed between the communication node # 2 and the communication node # 1 and an S5 bearer formed between the communication node # 1 and the gateway. Can be.

Here, the integrated delivery network may support the operation of transmitting and receiving the IP packet between the access network and the core network.

According to the present invention, a gateway (eg, a packet data network (PDN) -gateway (P-GW)) belonging to an integrated delivery network may use a 6-tuple based packet filtering rule. The six-tuple is an Internet Protocol (IP) address, a source IP address, a destination IP address, a source port number, a destination port number, and a protocol of an end communication node (e.g., terminal) belonging to the unified forwarding network. It may include an identifier (identifier).

In this case, the gateway may forward the IP packet (eg, IP flow) obtained from the evolved packet core (EPC) to the end communication node according to the 6-tuple based packet filtering rule. In addition, the gateway may forward the IP packet (eg, IP flow) obtained from the end node to the EPC according to the 6-tuple based packet filtering rule. Therefore, even when the IP address of the end communication node is different from the IP address of the base station connected to the end communication node, IP packets (eg, IP flows) between the base station and the EPC may be transmitted and received through the integrated delivery network. As a result, the performance of the communication system can be improved.

1 is a conceptual diagram illustrating a first embodiment of an integrated delivery network.
2 is a block diagram illustrating a first embodiment of a communication node constituting an integrated delivery network.
3 is a flowchart illustrating a first embodiment of a method for downlink transmission of an IP packet in an integrated delivery network.
4 is a conceptual diagram illustrating a first embodiment of a method for downlink transmission of an IP packet in an integrated delivery network.
5 is a conceptual diagram illustrating a first embodiment of a TFT / SDF template in a P-GW belonging to an integrated delivery network.
6 is a flowchart illustrating a first embodiment of an uplink transmission method of an IP packet in an integrated delivery network.
7 is a conceptual diagram illustrating a first embodiment of a method of uplink transmission of an IP packet in an integrated delivery network.
8 is a conceptual diagram illustrating a first embodiment of a TFT in a terminal belonging to an integrated delivery network.
9 is a conceptual diagram illustrating a second embodiment of the TFT / SDF template in the P-GW belonging to the integrated delivery network.

As the present invention allows for various changes and numerous embodiments, particular embodiments will be illustrated in the drawings and described in detail in the written description. However, this is not intended to limit the present invention to specific embodiments, it should be understood to include all modifications, equivalents, and substitutes included in the spirit and scope of the present invention.

Terms such as first and second may be used to describe various components, but the components should not be limited by the terms. The terms are used only for the purpose of distinguishing one component from another. For example, without departing from the scope of the present invention, the first component may be referred to as the second component, and similarly, the second component may also be referred to as the first component. The term and / or includes a combination of a plurality of related items or any item of a plurality of related items.

When a component is referred to as being "connected" or "connected" to another component, it may be directly connected to or connected to that other component, but it may be understood that other components may be present in between. Should be. On the other hand, when a component is said to be "directly connected" or "directly connected" to another component, it should be understood that there is no other component in between.

The terminology used herein is for the purpose of describing particular example embodiments only and is not intended to be limiting of the present invention. Singular expressions include plural expressions unless the context clearly indicates otherwise. In this application, the terms "comprise" or "have" are intended to indicate that there is a feature, number, step, operation, component, part, or combination thereof described in the specification, and one or more other features. It is to be understood that the present invention does not exclude the possibility of the presence or the addition of numbers, steps, operations, components, components, or a combination thereof.

Unless defined otherwise, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art. Terms such as those defined in the commonly used dictionaries should be construed as having meanings consistent with the meanings in the context of the related art and shall not be construed in ideal or excessively formal meanings unless expressly defined in this application. Do not.

Hereinafter, with reference to the accompanying drawings, it will be described in detail a preferred embodiment of the present invention. In the following description of the present invention, the same reference numerals are used for the same elements in the drawings and redundant descriptions of the same elements will be omitted.

A communication system to which embodiments according to the present invention are applied will be described. The communication system to which the embodiments according to the present invention are applied is not limited to the contents described below, and the embodiments according to the present invention may be applied to various communication systems. Here, the communication system may be used in the same sense as the communication network.

The long term evolution (LTE) network may be an internet protocol (IP) network, and thus all user traffic in the LTE network may be transmitted in the form of an IP packet (eg, an IP flow). In an initial access procedure (e.g., attach procedure) of an LTE network, a user equipment (UE) connects a packet data network (PDN) connection to a gateway (e.g., a PDN-gateway). You can ask)). In this case, the P-GW may assign an IP address for data transmission to the UE and set a default EPS (evolved packet system) bearer between the P-GW and the UE. The default EPS bearer may be maintained until the UE is detached from the LTE network. The default EPS bearer set for each of the PDNs and the IP address assigned to the UE (eg, PDN address) may be unique within one PDN. In order to support data transmission according to a new quality of service (QoS), a dedicated EPS bearer may be additionally established between the UE and the P-GW.

The P-GW may define packet filtering rules for classification of each of the downlink IP packet and the uplink IP packet. Here, the IP packet may refer to an IP flow. According to the packet filtering rule, only an IP packet having an IP address assigned to the UE may be transmitted from the P-GW to the corresponding UE. In the LTE network, an EPS bearer (eg, a user traffic transmission path) supporting various QoS may be set according to an application service of a UE. EPS bearers established between the UE and the P-GW may provide the same QoS quality for the same services. IP flows generated in each of the application services may be classified by QoS class. For example, the P-GW may classify an IP flow received from a PDN into an SDF using a service data flow (SDF) template, and map an IP flow classified into an SDF to an EPS bearer.

The SDF template may be configured as an IP packet filter. The IP packet filter may be composed of 5-tuple based filter rules. The 5-tuple may include a source IP address, a destination IP address, a source port number, a destination port number, and a protocol identifier. P-GW can classify IP flows into one SDF according to filter rules, and EPS bearer (for example, QoS of SDF that supports SDF) can be classified into IP streams classified as SDF according to traffic flow template (TFT) filter rules. EPS bearer).

SDF QoS parameters can be defined for an "IP flow-SDF" mapping. QoS parameters for each SDF may include a QoS class identifier (QCI), an allocation and retention priority (ARP), a maximum bit rate (MBR), a guaranteed bit rate (GBR), and the like. QoS parameters per EPS bearer may be defined for an “SDF to EPS bearer” mapping. QoS parameters per EPS bearer may include QCI, ARP, MBR, GBR, aggregated maximum bit rate (UE-AMBR), access point name (APN) -AMBR, and the like.

QoS parameters per SDF and QoS parameters per EPS bearer include QCI, ARP, MBR, and GBR in common, and the QoS parameters per EPS bearer are the QoS parameters (e.g., UE-AMBR) for the access network compared to the QoS parameters per SDF. , APN-AMBR, etc.) may be further included. SDFs having the same QoS parameter may be mapped to one EPS bearer. If the SDF cannot be mapped to the current EPS bearer (eg, the current EPS bearer does not support the QoS of the SDF), a new EPS bearer for the SDF may be set.

Meanwhile, in order to satisfy 5G service requirements, an unified transport network may be introduced in which a backhaul network and a fronthaul network are integrated. The integrated delivery network can be configured as follows.

1 is a conceptual diagram illustrating a first embodiment of an integrated delivery network.

Referring to FIG. 1, the integrated delivery network has a function of connecting an evolved packet core (EPC) (eg, an EPC device) 111 and a base station (eg, a small base station) 121, 122, and 123 ( For example, a backhaul function) can be performed. That is, the integrated delivery network may support the operation of transmitting and receiving IP packets between the core network and the access network. The unified delivery network may consist of a plurality of communication nodes 101, 102, 103, 104, 105, 106, 107. For example, the integrated delivery network may include a P-GW 101, a mobile Xhaul control unit (MXCU) 102, hubs 103, 104, 105, terminals 106, 107, and the like. In the following embodiments, the P-GW 101 may indicate a gateway that includes the P-GW 101, and the MXCU 102 may indicate a "mobility manager" or "mobility controller" and 103, 104, 105 and terminals 106, 107 may indicate an XHAul distributed unit (XDU). In addition, the plurality of communication nodes 101, 102, 103, 104, 105, 106, and 107 constituting the integrated delivery network may be configured as follows.

2 is a block diagram illustrating a first embodiment of a communication node constituting an integrated delivery network.

Referring to FIG. 2, the communication node 200 may include at least one processor 210, a memory 220, and a transceiver 230 that communicates with a network. In addition, the communication node 200 may further include an input interface device 240, an output interface device 250, a storage device 260, and the like. Each component included in the communication node 200 may be connected by a bus 270 to communicate with each other.

However, each component included in the communication node 200 may be connected through a separate interface or a separate bus around the processor 210, instead of the common bus 270. For example, the processor 210 may be connected to at least one of the memory 220, the transceiver 230, the input interface device 240, the output interface device 250, and the storage device 260 through a dedicated interface. .

The processor 210 may execute a program command stored in at least one of the memory 220 and the storage device 260. The processor 210 may refer to a central processing unit (CPU), a graphics processing unit (GPU), or a dedicated processor on which methods according to embodiments of the present invention are performed. Each of the memory 220 and the storage device 260 may be configured as at least one of a volatile storage medium and a nonvolatile storage medium. For example, the memory 220 may be configured as at least one of a read only memory (ROM) and a random access memory (RAM).

Referring back to FIG. 1, the P-GW 101 may support a PDN connection function for the terminals 106 and 107 and may support an IP anchoring function for mobility support. The P-GW 101 may be connected to an EPC 111 (eg, a communication node belonging to the core network) located outside the integrated forwarding network, and the MXCU 102 and the hubs 103 and 104 belonging to the integrated forwarding network. It can be connected with. The P-GW 101 is connected to other communication nodes (e.g., EPC 111, MXCU 102, hubs 103, 104) and a wired or wireless link (e.g., wireless with LTE protocol applied). Link).

The MXCU 102 may support control plane functionality (e.g., Xhaul control infrastructure (XCI) functionality) and mobility support functionality (e.g., mobility management entity (MME) functionality in an LTE network) in an integrated delivery network.

The hubs 103, 104, and 105 may support a switch function, and may be classified into general hubs and end hubs. The hubs 103, 105 connected with the terminals 106, 107 among the hubs 103, 104, 105 may be referred to as end hubs, and the terminals 106, 107 with the terminals 106, 107 among the hubs 103, 104, 105. Unconnected hub 104 may be referred to as a general hub. The hubs 103, 104, 105 may be connected via a wired link or a wireless link (eg, a wireless link to which the LTE protocol is applied).

Terminals 106 and 107 are connected to a communication node (e.g., base stations 121, 122, 123 or UE belonging to an access network) located outside of the converged forwarding network and to a wired or wireless link (e.g. It may be connected via a wireless link to be applied) and a hub (103, 105) belonging to the integrated delivery network through a wireless link (for example, a wireless link to which the LTE protocol is applied). The terminals 106 and 107 may be classified into fixed terminals and mobile terminals according to whether mobility is supported. Terminal 106 may be a fixed terminal that does not support mobility, and terminal 107 may be a mobile terminal that supports mobility.

The hubs 103, 104, 105 and the terminals 106, 107 may be installed by operators, and the end hubs 103, 105 may form a cell. When the operating state of the terminals 106 and 107 transitions from the power off state to the power on state, the terminals 106 and 107 are connected to the end hubs 103 and 105 and the radio bearer. Can be set and attach procedure can be performed. In the attach procedure, the terminals 106 and 107 may send a PDN connection request message to the P-GW 101 and the P-GW 101 if a PDN connection request message is received from the terminals 106 and 107. May assign an IP address to terminals 106 and 107. The IP addresses assigned to the terminals 106 and 107 may be unique IP addresses in the integrated delivery network. In addition, a default bearer between the P-GW 101 and the terminals 106 and 107 may be set in the attach procedure. The default bearer is an S5 bearer between the P-GW 101 and the terminating hubs 103 and 105 and a radio bearer between the terminating hubs 103 and 105 and the terminals 106 and 107 (eg, a data radio bearer (DRB)). It may include. The S5 bearer may be configured as a general packet radio service (GPRS) tunneling protocol (GTP) tunnel.

Meanwhile, the terminal 106 may support a backhaul function for the base stations 121, 122, and 123, and the P-GW 101 may support a connection function with the EPC 111. Accordingly, the terminal 106 can transmit the IP packet received from the base stations 121, 122, 123 to the end hub 103, and the end hub 103 transmits the IP packet received from the terminal 106 to the P-GW. And the P-GW 101 may transmit the IP packet received from the end hub 103 to the EPC 111. Here, the transmission function in the direction of " base station 121, 122, 123 → terminal 106 → end hub 103 → P-GW 101 → EPC 111 " For example, the uplink transmission function ”may be referred to. In addition, the transmission function in the direction of "EPC 111 → P-GW 101 → termination hub 103 → terminal 106 → base station 121, 122, 123" is a " forward link (FL) transmission function (e.g., For example, it may be referred to as a "downlink transmission function".

The IP address of each of the base stations 121, 122, 123 may be set differently from the IP address of the terminal 106, and in the uplink transmission procedure, the terminal 106 may use the IP address of the base station 121, 122, 123. That is, an IP packet having an IP address different from that of the terminal 106 may be transmitted to the P-GW 101 through the end hub 103. The P-GW 101 may receive an IP packet from the terminal 106, but when the 5-tuple based packet filtering rule is applied in the P-GW 101, the P-GW 101 may receive the IP packet. Source IP address (e.g., IP address of terminal 106) according to 5-tuple based packet filtering rule and source IP address of IP packet (i.e., IP address of base station 121, 122, 123) ), You can drop the corresponding IP packet. The 5-tuple may include a source IP address, a destination IP address, a source port number, a destination port number, and a protocol identifier.

In addition, in the downlink transmission procedure, the P-GW 101 may receive an IP packet having the IP addresses of the base stations 121, 122, and 123 instead of the IP address of the terminal 106 from the EPC 111. When the 5-tuple-based packet filtering rule is applied in the P-GW 101, the destination IP address (eg, the IP address of the terminal 106) according to the 5-tuple-based packet filtering rule is EPC (111). The P-GW 101 may drop the IP packet because it is different from the destination IP address (eg, the IP addresses of the base stations 121, 122, 123) received from the IP packet.

To solve this problem, a 6-tuple based packet filtering rule can be defined. The six-tuple may include a terminal IP address (eg, communication node IP address), a source IP address, a destination IP address, a source port number, a destination port number, and a protocol ID. For example, in the FL transmission in the direction of "EPC 111 → P-GW 101 → Termination Hub 103 → Terminal 106 → Base Station # 1 121", the 6-tuple based FL TFT rule is It may be defined as shown in Table 1 below.

In addition, in the RL transmission in the direction of " base station # 1 121 → terminal 106 → end hub 103 → P-GW 101 → EPC 111 ", the 6-tuple based FL TFT rule is shown in the table below. It can be defined as 2.

The transmission method of the IP packet based on the FL TFT rule of Table 1 may be as follows.

3 is a flowchart illustrating a first embodiment of a downlink transmission method of an IP packet in an integrated delivery network, and FIG. 4 is a conceptual diagram illustrating a first embodiment of a downlink transmission method of an IP packet in an integrated delivery network.

3 and 4, a unified delivery network may include a gateway (eg, P-GW) 101, end hub 103, terminal 106, and the like. The integrated delivery network may be configured identically or similarly to the integrated delivery network shown in FIG. 1. For example, each of the P-GW 101, the termination hub 103, and the terminal 106 shown in FIGS. 3 and 4 is the P-GW 101, the termination hub 103, and the terminal shown in FIG. 1. It may be the same as (106).

A default bearer may be set between the P-GW 101 and the terminal 106 and the ID of the default bearer may be set to five. The default bearer between the P-GW 101 and the terminating hub 103 may be configured as a GTP tunnel, and the default bearer between the terminating hub 103 and the terminal 106 may be a radio bearer. The IP flow may be sent in a non-GBR manner in the default bearer. In addition, two dedicated bearers may be established between the P-GW 101 and the terminal 106. The ID of the dedicated bearer # 1 may be set to 8, and the IP flow may be transmitted in the GBR manner in the dedicated bearer # 1. The ID of the dedicated bearer # 2 may be set to 10, and the IP flow may be transmitted in the GBR manner in the dedicated bearer # 2. Dedicated bearers # 1 and # 2 between the P-GW 101 and the terminating hub 103 may be configured as GTP tunnels, and dedicated bearers # 1 and # 2 between the terminating hub 103 and the terminal 106 may be radio bearers. Can be.

The P-GW 101 may receive IP flows # 1 to # 3 from the EPC 111 (that is, the EPC 111 illustrated in FIG. 1) (S301). An IP flow may refer to an IP packet. The IP flow # 1 may be an IP flow transmitted from the EPC 111 to the base station # 1 121, and the 5-tuple of the IP flow # 1 may be set as shown in Table 3 below.

IP flow # 2 may be an IP flow transmitted from the EPC 111 to the base station # 2 122, and the 5-tuple of the IP flow # 2 may be set as shown in Table 4 below.

The IP flow # 3 may be an IP flow transmitted from the EPC 111 to the base station # 3 123, and the 5-tuple of the IP flow # 3 may be set as shown in Table 5 below. IP flow # 3 may be an IP flow transmitted in a best effort manner.

The IP flows # 1 to # 3 received from the EPC 111 do not include a terminal IP address, but the IP flows # 1 to # 3 may be received at the P-GW 101 when the FL TFT rules are satisfied. . On the other hand, IP flows # 1 to # 3 may be dropped if the FL TFT rules are not satisfied. Whether to receive / drop IP flows # 1 to # 3 may be determined based on a TFT / SDF template in a packet filter (PF) of the P-GW 101. The TFT / SDF template may be as follows.

5 is a conceptual diagram illustrating a first embodiment of a TFT / SDF template in a P-GW belonging to an integrated delivery network.

Referring to FIG. 5, an IP flow (eg, IP flow # 1) that satisfies the filtering rule of “index # 1” may be classified as SDF # 1, and the IP flow classified as SDF # 1 may bearer ID. May be mapped to a bearer with 10. IP flows that satisfy the filtering rule of "index # 2" (eg, IP flow # 2) may be classified as SDF # 2, and IP flows classified as SDF # 2 are mapped to bearers with a bearer ID of 8. Can be. IP flows that satisfy the filtering rule of "index # 3" (eg, IP flow # 3) may be classified as SDF # 3, and IP flows classified as SDF # 3 are mapped to bearers with bearer ID 5. Can be.

Referring again to FIGS. 3 and 4, the P-GW 101 may classify IP flows # 1 to # 3 as SDFs based on the TFT / SDF template (eg, SDF template) of FIG. 5 ( S302). For example, IP flow # 1 may be classified as SDF # 1, IP flow # 2 may be classified as SDF # 2, and IP flow # 3 may be classified as SDF # 3. Each of the SDFs # 1 to # 3 may support different QoS. After the step S302 is completed, the P-GW 101 uses the IP address of the terminal 106 connected with the base stations # 1 to # 3 (121, 122, 123) to the IP flows # 1 to # 3 classified as SDF. An encapsulation operation may be performed (S303). When the encapsulation operation is completed, 6-tuples for IP flows # 1 to # 3 may be set. The six-tuple of IP flow # 1 can be set as shown in Table 6 below, the six-tuple of IP flow # 2 can be set as shown in Table 7 below, and the six-tuple of IP flow # 3 is shown in Table 8 below. It can be set as follows. That is, the 6-tuple may further include a terminal IP address compared to the 5-tuple.

After step S303 is completed, P-GW 101 performs IP flow # 1 to # 3 (e.g., IP flow # classified as SDF) based on the TFT / SDF template (e.g., TFT rule) of FIG. 1 to # 3) may be mapped to the bearer (S304). IP flow # 1 may be mapped to dedicated bearer # 2 with a bearer ID of 10 (eg, dedicated bearer # 2 supporting GBR), and IP flow # 2 may be mapped to dedicated bearer # 1 with a bearer ID of 8 (eg For example, it may be mapped to dedicated bearer # 1 supporting GBR, and IP flow # 3 may be mapped to a default bearer having a bearer ID of 5 (eg, a default bearer supporting non-GBR). The P-GW 101 may transmit IP flows # 1 to # 3 through the mapped bearer (S305). MBR rate policing may be applied to IP flows # 1 and # 2 transmitted through dedicated bearers # 1 and # 2. In this case, the P-GW 101 may drop the IP flow exceeding the FL MBR. In addition, UE-AMBR rate polishing may be applied to IP flow # 3 transmitted through the default bearer. In this case, the P-GW 101 may drop the IP flow exceeding the UE-AMBR.

The end hub 103 may receive IP flow # 1 classified as SDF # 1 via dedicated bearer # 2, and receive IP flow # 2 classified as SDF # 2 via dedicated bearer # 1. The IP flow # 3 classified as SDF # 3 can be received through the default bearer. The end hub 103 may map IP flows # 1 to # 3 to the radio bearer to satisfy the QoS (S306). For example, the end hub 103 may send IP flows # 1 and # 2 to the radio bearers (eg, dedicated bearers # 1 and # 2 between the end hub 103 and the terminal 106) to satisfy GBR QoS. IP flow # 3 may be mapped to a radio bearer (eg, a default bearer between the end hub 103 and the terminal 106) to satisfy the best edge QoS. The end hub 103 may transmit IP flows # 1 to # 3 through the mapped bearer (S307).

Terminal 106 may receive IP flow # 1 through dedicated bearer # 2, receive IP flow # 2 through dedicated bearer # 1, and receive IP flow # 3 through default bearer. Can be. Each of IP flows # 1 through # 3 received at terminal 106 may include the six-tuples of Tables 6-8. The terminal 106 may perform a decapsulation operation for the IP flows # 1 to # 3 (S308). By the decapsulation operation, IP flows # 1 to # 3 including 5-tuples of Tables 3 to 5 may be generated. That is, the terminal IP address may be removed from the IP flows # 1 to # 3. The terminal 106 may transmit IP flows # 1 to # 3 to the base stations # 1 to # 3 (121, 122, 123) based on the 5-tuple (S309). For example, terminal 106 may send IP flow # 1 to base station # 1 121, send IP flow # 2 to base station # 2 122, and may transmit IP flow # 3 to base station # 3 ( 123).

Meanwhile, a method of transmitting an IP packet based on the RL TFT rules of Table 2 may be as follows.

6 is a flowchart illustrating a first embodiment of an uplink transmission method of an IP packet in an integrated delivery network, and FIG. 7 is a conceptual diagram illustrating a first embodiment of an uplink transmission method of an IP packet in an integrated delivery network.

6 and 7, the integrated delivery network may include a gateway (eg, P-GW) 101, end hub 103, terminal 106, and the like. The integrated delivery network may be configured identically or similarly to the integrated delivery network shown in FIG. 1. For example, each of the P-GW 101, the termination hub 103, and the terminal 106 shown in FIGS. 3 and 4 is the P-GW 101, the termination hub 103, and the terminal shown in FIG. 1. It may be the same as (106).

A default bearer may be set between the P-GW 101 and the terminal 106 and the ID of the default bearer may be set to five. The default bearer between the P-GW 101 and the terminating hub 103 may be configured as a GTP tunnel, and the default bearer between the terminating hub 103 and the terminal 106 may be a radio bearer. The IP flow may be sent in a non-GBR manner in the default bearer. In addition, two dedicated bearers may be established between the P-GW 101 and the terminal 106. The ID of the dedicated bearer # 1 may be set to 8, and the IP flow may be transmitted in the GBR manner in the dedicated bearer # 1. The ID of the dedicated bearer # 2 may be set to 10, and the IP flow may be transmitted in the GBR manner in the dedicated bearer # 2. Dedicated bearers # 1 and # 2 between the P-GW 101 and the terminating hub 103 may be configured as GTP tunnels, and dedicated bearers # 1 and # 2 between the terminating hub 103 and the terminal 106 may be radio bearers. Can be.

The terminal 106 may receive the IP flows # 1 to # 3 from the base stations # 1 to # 3 (121, 122, 123) (S601). An IP flow may refer to an IP packet. IP flow # 1 may be an IP flow transmitted from the base station # 1 121 to the EPC 111, and the 5-tuple of the IP flow # 1 may be set as shown in Table 9 below.

IP flow # 2 may be an IP flow transmitted from the base station # 2 122 to the EPC 111, and the 5-tuple of the IP flow # 2 may be set as shown in Table 10 below.

IP flow # 3 may be an IP flow transmitted from the base station # 3 123 to the EPC 111, and the 5-tuple of the IP flow # 3 may be set as shown in Table 11 below. IP flow # 3 may be an IP flow transmitted in a best effort manner.

IP flows # 1 to # 3 received from the base stations # 1 to # 3 (121, 122, 123) do not include a terminal IP address, but IP flows # 1 to # 3 are terminal (s) if they satisfy the RL TFT rule. 106 may be received. On the other hand, IP flows # 1 to # 3 may be dropped if the RL TFT rules are not satisfied. Whether to receive / drop IP flows # 1 to # 3 may be determined based on the TFT in the PF of the terminal 106. The TFT may be as follows.

8 is a conceptual diagram illustrating a first embodiment of a TFT in a terminal belonging to an integrated delivery network.

Referring to FIG. 8, an IP flow (eg, IP flow # 1) that satisfies the filtering rule of “index # 1” may be mapped to a bearer having a bearer ID of 10. An IP flow (eg, IP flow # 2) that satisfies the filtering rule of "index # 2" may be mapped to a bearer whose bearer ID is eight. An IP flow (eg, IP flow # 3) that satisfies the filtering rule of "index # 3" may be mapped to a bearer with a bearer ID of 5.

6 and 7 again, the terminal 106 can perform an encapsulation operation for IP flows # 1 to # 3 using the IP address of the terminal 106 (S602). When the encapsulation operation is completed, 6-tuples for IP flows # 1 to # 3 may be set. The six-tuple of IP flow # 1 may be set as shown in Table 12 below, the six-tuple of IP flow # 2 may be set as shown in Table 13 below, and the six-tuple of IP flow # 3 is shown in Table 14 below. It can be set as follows.

After step S602 is completed, the terminal 106 may map IP flows # 1 to # 3 to the bearer based on the TFT of FIG. 8 (S603). IP flow # 1 may be mapped to dedicated bearer # 2 with a bearer ID of 10 (eg, dedicated bearer # 2 supporting GBR), and IP flow # 2 may be mapped to dedicated bearer # 1 with a bearer ID of 8 (eg For example, it may be mapped to dedicated bearer # 1 supporting GBR, and IP flow # 3 may be mapped to a default bearer having a bearer ID of 5 (eg, a default bearer supporting non-GBR). The terminal 106 may transmit IP flows # 1 to # 3 through the mapped bearer (S604). Here, radio resources for IP flows # 1 and # 2 transmitted through dedicated bearers # 1 and # 2 supporting GBR may be periodically allocated, and IP flows transmitted through a default bearer supporting non-GBR. Radio resources for # 3 may be allocated aperiodically.

End hub 103 may receive IP flow # 1 through dedicated bearer # 2, receive IP flow # 2 through dedicated bearer # 1, and receive P flow # 3 through default bearer. can do. The end hub 103 may map IP flows # 1 to # 3 to bearers established between the end hub 103 and the P-GW 101 so as to satisfy QoS (S605). For example, the end hub 103 may map IP flows # 1 and # 2 to dedicated bearers # 2 and # 1, respectively, to satisfy GBR QoS, and assign IP flow # 3 to the default bearer to satisfy best edge QoS. Can be mapped to The end hub 103 may transmit IP flows # 1 to # 3 through the mapped bearer (S606). MBR rate polishing may be applied to IP flows # 2 and # 1 transmitted through dedicated bearers # 1 and # 2. In this case, the termination hub 103 may drop the IP flow exceeding the FL MBR. In addition, UE-AMBR rate polishing may be applied to IP flow # 3 transmitted through the default bearer. In this case, the termination hub 103 may drop the IP flow exceeding the UE-AMBR.

P-GW 101 may receive IP flow # 1 through dedicated bearer # 2, P-GW 101 may receive IP flow # 2 through dedicated bearer # 1, and receive IP flow # 3 through default bearer. Can be received. Each of IP flows # 1 through # 3 received at the P-GW 101 may include the six-tuples of Tables 12-14. The P-GW 101 may classify IP flows # 1 to # 3 as SDF based on the TFT / SDF template (eg, SDF template) (S607). The TFT / SDF template may be as follows.

9 is a conceptual diagram illustrating a second embodiment of a TFT / SDF template in a P-GW belonging to an integrated delivery network.

9, an IP flow received through a bearer having a bearer ID of 10 (eg, IP flow # 1) may be classified as SDF # 1, and an IP flow received through a bearer having a bearer ID of 8. (Eg, IP flow # 2) may be classified as SDF # 2, and an IP flow received through a bearer with a bearer ID of 5 (eg, IP flow # 3) may be classified as SDF # 3. have.

6 and 7 again, IP flow # 1 may be classified as SDF # 1, IP flow # 2 may be classified as SDF # 2, and IP flow # 3 may be classified as SDF # 3. have. Each of the SDFs # 1 to # 3 may support different QoS. In addition, the P-GW 101 may perform a rate polishing operation on the IP flows # 1 to # 3.

After step S607 is completed, the P-GW 101 uses the IP address of the terminal 106 to decode the IP flows # 1 to # 3 (eg, IP flows # 1 to # 3 classified as SDF). An encapsulation operation may be performed (S608). When the decapsulation operation is completed, IP flows # 1 to # 3 including 5-tuples may be set. The 5-tuples of the IP flows # 1 to # 3 may be set as shown in Tables 9 to 11. The P-GW 101 may transmit IP flows # 1 to # 3 to the EPC 111 based on the 5-tuple (S609).

The methods according to the invention can be implemented in the form of program instructions that can be executed by various computer means and recorded on a computer readable medium. Computer-readable media may include, alone or in combination with the program instructions, data files, data structures, and the like. The program instructions recorded on the computer readable medium may be those specially designed and constructed for the present invention, or may be known and available to those skilled in computer software.

Examples of computer readable media include hardware devices that are specifically configured to store and execute program instructions, such as ROM, RAM, flash memory, and the like. Examples of program instructions include machine language code, such as produced by a compiler, as well as high-level language code that can be executed by a computer using an interpreter or the like. The hardware device described above may be configured to operate with at least one software module to perform the operations of the present invention, and vice versa.

Although described with reference to the above embodiments, those skilled in the art will understand that various modifications and changes can be made without departing from the spirit and scope of the invention as set forth in the claims below. Could be.

Claims (20)

A packet transmission method performed by a gateway belonging to an integrated forwarding network.
Receiving an internet protocol (IP) packet comprising a 5-tuple from a core network;
If the destination indicated by the 5-tuple included in the IP packet is a base station, the IP packet includes an address of communication node # 1 connected to the base station among the communication nodes constituting the integrated forwarding network. Performing an encapsulation operation on the network; And
Sending the encapsulated IP packet to the base station via the communication nodes. The method according to claim 1,
The communication node # 1 is connected via a wireless link with other communication nodes constituting the integrated forwarding network, and the IP address of the communication node # 1 is set by the gateway. The method according to claim 1,
The IP address of the communication node # 1 is set differently from the IP address of the base station. The method according to claim 1,
The 5-tuple of the IP packet includes a source IP address, a destination IP address, a source port number, a destination port number, and a protocol identifier, wherein the source IP address belongs to the core network. And a destination IP address is set to an IP address of the base station. The method according to claim 1,
The encapsulated IP packet includes six tuples, the six tuples comprising a communication node IP address, a source IP address, a destination IP address, a source port number, a destination port number and a protocol ID, and the communication node. An IP address is set to an IP address of the communication node # 1, the source IP address is set to an IP address of a communication node belonging to the core network, and the destination IP address is set to an IP address of the base station Way. The method according to claim 1,
The encapsulation operation is performed on the IP packet classified as service data flow (SDF). The method according to claim 1,
The encapsulated IP packet includes an S5 bearer formed between the communication node # 2 and the gateway connected to the communication node # 1 through a wireless link among the communication nodes, and the communication node # 2 and the communication node # 1. A packet transmission method transmitted through a radio bearer formed in the liver. The method according to claim 1,
The integrated forwarding network supports packet transmission and reception between the access network to which the base station belongs and the core network. A packet transmission method performed by communication node # 1 belonging to an integrated forwarding network,
Receiving an Internet Protocol (IP) packet including 6-tuples from communication nodes # 2 connected to the communication node # 1 via a wireless link among communication nodes belonging to the integrated forwarding network;
Generating a decapsulated IP packet including a 5-tuple by performing a decapsulation operation on the IP packet; And
Sending the decapsulated IP packet to a destination indicated by the 5-tuple of the decapsulated IP packet,
The six-tuple includes a communication node IP address, a source IP address, a destination IP address, a source port number, a destination port number, and a protocol ID, wherein the communication node IP address is the address of the communication node # 1. An IP address, the source IP address indicating an IP address of a communication node belonging to a core network, and the destination IP address indicating an IP address of a base station belonging to an access network. . The method according to claim 9,
The IP address of the communication node # 1 is set by a gateway belonging to the integrated delivery network in an attach procedure, and the IP address of the communication node # 1 is set differently from the IP address of the base station. . The method according to claim 9,
The 5-tuple of the decapsulated IP packet includes the source IP address, the destination IP address, the source port number, the destination port number, and the protocol ID among the 6-tuples except the communication node IP address. Packet transmission method. The method according to claim 9,
The IP packet including the 6-tuple is generated by a gateway belonging to the unified forwarding network, the IP packet including the 6-tuple is an S5 bearer formed between the gateway and the communication node # 2 and And a radio bearer formed between the communication node # 2 and the communication node # 1. The method according to claim 9,
And the communication node # 1 communicates with the communication node # 2 using a long term evolution (LTE) protocol. A packet transmission method performed by a gateway belonging to an integrated forwarding network.
Receiving an Internet Protocol (IP) packet including a six-tuple from communication node # 1 belonging to the unified delivery network;
Generating a decapsulated IP packet including a 5-tuple by performing a decapsulation operation on the IP packet; And
Sending the decapsulated IP packet to a destination indicated by the 5-tuple of the decapsulated IP packet,
The six-tuple includes a communication node IP address, a source IP address, a destination IP address, a source port number, a destination port number, and a protocol ID, wherein the communication node IP address constitutes the integrated forwarding network. Indicating the IP address of communication node # 2 connected to the base station indicated by the source IP address among the communication nodes, the source IP address indicating the IP address of the base station belonging to an access network, and the destination IP address indicates the IP address of the communication node belonging to the core (core) network. The method according to claim 14,
The communication node # 2 is connected to the communication node # 1 via a wireless link, and the IP address of the communication node # 2 is set by the gateway. The method according to claim 14,
The IP address of the communication node # 2 is set differently from the IP address of the base station. The method according to claim 14,
The 5-tuple of the decapsulated IP packet includes the source IP address, the destination IP address, the source port number, the destination port number, and the protocol ID among the 6-tuples except the communication node IP address. Packet transmission method. The method according to claim 14,
The decapsulation operation is performed on the IP packet classified as a service data flow (SDF). The method according to claim 14,
The IP packet is generated by the communication node # 2 and received through a radio bearer formed between the communication node # 2 and the communication node # 1 and an S5 bearer formed between the communication node # 1 and the gateway. Packet transmission method. The method according to claim 14,
The integrated forwarding network supports the transmission and reception of the IP packet between the access network and the core network.

Images