KR101851328B1 - Apparatus and method for setting a bearer for transmission of the user data - Google Patents

Apparatus and method for setting a bearer for transmission of the user data Download PDF

Info

Publication number
KR101851328B1
KR101851328B1 KR1020160023912A KR20160023912A KR101851328B1 KR 101851328 B1 KR101851328 B1 KR 101851328B1 KR 1020160023912 A KR1020160023912 A KR 1020160023912A KR 20160023912 A KR20160023912 A KR 20160023912A KR 101851328 B1 KR101851328 B1 KR 101851328B1
Authority
KR
South Korea
Prior art keywords
terminal
bearer
base station
core network
leg
Prior art date
Application number
KR1020160023912A
Other languages
Korean (ko)
Other versions
KR20170101420A (en
Inventor
조준하
Original Assignee
콘텔라 주식회사
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 콘텔라 주식회사 filed Critical 콘텔라 주식회사
Priority to KR1020160023912A priority Critical patent/KR101851328B1/en
Publication of KR20170101420A publication Critical patent/KR20170101420A/en
Application granted granted Critical
Publication of KR101851328B1 publication Critical patent/KR101851328B1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/16—Gateway arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0215—Traffic management, e.g. flow control or congestion control based on user or device properties, e.g. MTC-capable devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0252—Traffic management, e.g. flow control or congestion control per individual bearer or channel
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H04W8/20—Transfer of user or subscriber data
    • H04W8/205—Transfer to or from user equipment or user record carrier

Abstract

The present invention discloses an apparatus and method for establishing a bearer for transmission of user data. An apparatus for establishing a bearer for transmission of user data, which is located between a base station and a core network according to an aspect of the present invention, determines whether a terminal generating the call is a corporate terminal upon receiving a call origination signal message from the base station And transmitting the bearer setup information according to the determination result to the base station and the core network; And if the terminal generating the call by the terminal determination unit determines that the terminal is a corporate terminal, using the bearer setup information for the base station and the bearer setup information for the core network received from the terminal determination unit, And a bearer setting unit for setting a bearer between the base station and the core network.

Description

[0001] APPARATUS AND METHOD FOR SETTING A BEARER FOR TRANSMISSION OF THE USER DATA [0002]

The present invention relates to an apparatus and method for setting bearer for transmission of user data, and more particularly, to a method and apparatus for setting bearer for transmission of user data by judging a type of terminal (a corporation terminal or a general terminal) To an apparatus and method for setting up a bearer for transmission of user data for setting up a bearer to transmit user data.

The LIPA (Loacl IP Access) technology allows access to an enterprise network using a base station (HeNB) and an evolved packet core (EPC), which is already defined in the 3GPP. According to the related art, a Loacl Enterprise Gateway (LEG) is provided between the base station (HeNB) and the core network (EPC) by applying the LIPA technique to perform a local breakout (Loack Breakout). The corporation terminal (terminal that can be connected to the corporation network) performs local breakout through the local enterprise gateway (LEG). At this time, the local enterprise gateway (LEG) can smoothly transmit / receive user data (packet) of the corporation terminal to the corporation network by applying a technique such as NAT.

At this time, the local enterprise gateway (LEG) establishes an S1 bearer between the base station and the core network, and transmits / receives user data (packet) of the terminal through the S1 bearer. According to the related art, the local enterprise gateway (LEG) locally breaks out the user data (packet) of the terminal according to the type of terminal (corporation terminal or general terminal). The corporate terminal means a terminal connectable to a corporation network, and the general terminal means a terminal connectable to a core network (EPC). That is, the local enterprise gateway (LEG) checks the User IP address in the user data (packet) of the received terminal and locally breaks out the user data (packet) of the terminal according to the result. For example, when the S1 bearer is set up, the LAG transmits user data (packet) to the corporate network when the User IP address is a corporate terminal, (Packet) to the core network (EPC).

As described above, according to the above-described conventional technology, the S1 bearer is unconditionally generated between the base station-local enterprise gateway (LEG) -core network (EPC) regardless of whether it is a corporation terminal or a general terminal, After the user data (packet) is transmitted to the gateway (LEG), the local enterprise gateway (LEG) judges whether it is a corporate terminal or a general terminal and transmits the user data to the corresponding network (corporation network or core network). Therefore, the local enterprise gateway (LEG) is also connected between the base station-local enterprise gateway (LEG) and the core network (EPC) to relay the user data (packet) of the terminal not connected to the corporation network S1 bearer is generated and user data (packet) is processed. Therefore, an increase in cost due to the setting of unnecessary S1 bearer (setting of maximum capacity and maximum bandwidth) and the performance of local corporate gateway (LEG) do.

Korean Patent Laid-Open Publication No. 2015-0143201 (published Dec. 23, 2015)

SUMMARY OF THE INVENTION The present invention has been proposed in order to solve the above problems, and it is an object of the present invention to provide a method and apparatus for determining a type of a terminal (a corporation terminal or a general terminal) at the time of creating a bearer, And an apparatus and method for setting up a bearer.

Other objects and advantages of the present invention can be understood by the following description, and will be more clearly understood by one embodiment of the present invention. It will also be readily apparent that the objects and advantages of the invention may be realized and attained by means of the instrumentalities and combinations particularly pointed out in the appended claims.

According to another aspect of the present invention, there is provided an apparatus for establishing a bearer for transmitting user data, the base station being located between a base station and a core network, the base station comprising: Determining whether the generated terminal is a corporate terminal, and transmitting the bearer setup information according to the determination result to the base station and the core network; And if the terminal generating the call by the terminal determination unit determines that the terminal is a corporate terminal, using the bearer setup information for the base station and the bearer setup information for the core network received from the terminal determination unit, And a bearer setting unit for setting a bearer between the base station and the core network.

The terminal determination unit transmits bearer setup information for the device to the base station and the core network when the terminal is a corporate terminal.

The terminal determination unit transmits bearer setup information for the core network to the base station and bearer setup information for the base station to the core network when the terminal is a general terminal other than a corporation terminal.

The terminal determination unit obtains the identification information from the terminal using the NAS Transport message, and compares the acquired identification information with the identification information of the corporate terminal stored in the repository to determine whether the terminal is a corporate terminal.

The device is a Local Enterprise Gateway (LEG) that performs a Local Breakout (Loack BreakOut) using a LIPA (Loacl IP Access) between the base station and the core network.

The identification information is IMSI.

According to another aspect of the present invention, there is provided a method for transmitting user data in an apparatus for establishing a bearer for transmission of user data, the apparatus being located between a base station and a core network, Requesting and receiving identification information on a terminal that originated the call to the base station upon receiving a call origination signal message from the base station; Comparing the received identification information with identification information of a corporate terminal stored in a storage; And a step of the device determining a type of a terminal according to the comparison result and setting a bearer.

The step of setting bearer includes the steps of: transmitting bearer setup information for the apparatus to the base station and the core network, when the bearer is a corporation terminal as a result of the comparison; And transmitting the bearer setup information for the core network to the base station and the bearer setup information for the base station to the core network when the comparison result is a general terminal.

The receiving step receives the identification information from the terminal using the NAS Transport message.

The device is a Local Enterprise Gateway (LEG) that performs a Local Breakout (Loack BreakOut) using a LIPA (Loacl IP Access) between the base station and the core network.

The identification information is IMSI.

According to an aspect of the present invention, a local enterprise gateway (LEG) determines a type of a terminal (a corporation terminal or a general terminal) at the time of creation of a bearer, EPC) to transmit and receive user data (packet) of the UE, thereby reducing the cost.

In addition, when the type of the terminal is a general terminal, the LAG generates a bearer directly between the base station and the core network (EPC) to transmit / receive user data (packet) of the terminal, There is an effect that the problem that the user data is concentrated on the LEG causes deterioration of the performance due to the occurrence of the load can be solved.

The effects obtained in the present invention are not limited to the effects mentioned above, and other effects not mentioned can be clearly understood by those skilled in the art from the following description .

BRIEF DESCRIPTION OF THE DRAWINGS The accompanying drawings, which are incorporated in and constitute a part of the specification, illustrate exemplary embodiments of the invention and, together with the specific details for carrying out the invention, And shall not be construed as limited to the matters described.
FIG. 1 schematically illustrates a system configuration according to an embodiment of the present invention; FIG.
FIG. 2 is a flowchart for acquiring identification information of a terminal in a local enterprise gateway (LEG) according to an embodiment of the present invention;
FIG. 3 is a flowchart illustrating a bearer setup process in a local enterprise gateway (LEG) according to an exemplary embodiment of the present invention;
4 is a flowchart illustrating a bearer setup process in a local enterprise gateway (LEG) according to another embodiment of the present invention.

BRIEF DESCRIPTION OF THE DRAWINGS The above and other objects, features and advantages of the present invention will become more apparent from the following detailed description of the present invention when taken in conjunction with the accompanying drawings, in which: There will be. In the following description, well-known functions or constructions are not described in detail since they would obscure the invention in unnecessary detail. Hereinafter, a preferred embodiment of the present invention will be described in detail with reference to the accompanying drawings.

Throughout the specification, when an element is referred to as " comprising ", it means that it can include other elements as well, without excluding other elements unless specifically stated otherwise. In addition, the term "Quot; and " part " refer to a unit that processes at least one function or operation, which may be implemented in hardware, software, or a combination of hardware and software.

BRIEF DESCRIPTION OF THE DRAWINGS FIG. 1 is a schematic diagram of a system according to an embodiment of the present invention; FIG.

1, a system according to an exemplary embodiment of the present invention includes a terminal 100, a base station (HeNB) 130, a local enterprise gateway (LEG) 150, a core network (EPC) 170, (Not shown).

The UE 100 transmits the user data (packet) to the network (the core network 170 or the corporation network 190). The terminal 100 may be a general terminal or a corporate terminal. The general terminal means a terminal capable of accessing the core network (EPC) 170 (that is, a terminal transmitting user data (packets) to the core network), and the corporate terminal can be connected to the corporation network 190 (I.e., a terminal that transmits user data (packets) to a corporate network). The terminal 100 may include user IP address information corresponding to a general terminal or a corporate terminal and identification information (e.g., IMSI) of the terminal.

The base station (HeNB) 130 is located between the UE 100 and the LEG 150 and relays user data (packets) of the UE 100 do.

The core network (EPC) 170 may be set up with a local enterprise gateway (LEG) 150 or bearer directly with the base station 130. The EPC 170 may include a Mobile Management Entity (MME) 171, a Serving GateWay (SGW) 173, and the like.

The corporation network 190 interlocks with the local enterprise gateway (LEG) 150 and transmits and receives user data (packets) to and from the corporation terminal. In this case, the corporate network 190 may include a corporation server, an IP-PBX, a PBX, and the like.

The local enterprise gateway (LEG) 150 determines the type of terminal (corporation terminal or general terminal), sets the bearer according to the determination result, and transmits user data (packet) of the terminal through the bearer. In more detail, the local enterprise gateway (LEG) 150 receives the identification information of the terminal (for example, IMSI) from the terminal, compares the identification information with the identification information of the corporate terminal stored in the repository, do. At this time, the regional enterprise gateway (LEG) 150 pre-stores and manages the identification information (e.g., IMSI) of the corporate terminal in the repository. For example, an administrator can store and manage identification information (e.g., IMSI) of a corporate terminal in a repository of a local enterprise gateway (LEG) 150 using management functions (addition, deletion, inquiry,

When the result of the determination is affirmative, the local enterprise gateway (LEG) 150 transmits a bearer (S1 Bearer) between the base station 130, the regional enterprise gateway (LEG) 150 and the core network (EPC) And the user data (packet) of the corporation terminal is transmitted to the corporation network 190 through the set bearer. If the result of the determination is affirmative, the LAG 150 establishes an S1 Bearer directly between the Node B 130 and the EPC 170, User data (packet) of the general terminal is transmitted to the core network 170 through the established bearer.

The regional enterprise gateway (LEG) 150 includes a terminal determination unit (S1-MME) 151 and a bearer configuration unit (S1-U) 153 according to its functions. The detailed configuration of the regional enterprise gateway (LEG) 150 is described as being executed individually according to the functions thereof, but the present invention is not limited to this. The terminal determination unit (S1-MME) 151 and the bearer setting unit (S1-U) 153 can be executed.

The terminal determination unit (S1-MME) 151 compares the identification information (e.g., IMSI) of the terminal received from the base station 130 with the identification information (e.g., IMSI) of the corporate terminal stored in the repository, And transmits and receives messages for bearer establishment according to the type of the UE to the base station 130, the mobility management apparatus (MME) 171 and the bearer setup unit (S1-U) 153 of the core network.

The bearer setting unit S1-U 153 sets the bearer setting unit S1-MME 151 to the bearer setting unit S1-MME 151 when the terminal determination unit (S1-MME) 151 determines that the type of the terminal is a corporation terminal. Lt; / RTI >

Hereinafter, the process of acquiring the terminal's identification information in the local enterprise gateway (LEG) 150 according to the above configuration and the bearer establishment process according to the determination of the terminal type will be described in more detail with reference to FIG. 2 to FIG.

FIG. 2 is a flowchart for acquiring identification information of a terminal from a local enterprise gateway (LEG) according to an embodiment of the present invention. The operation of the local enterprise gateway (LEG) 150 illustrated in FIG. 2 may be understood as an operation performed by the terminal determination unit (S1-MME) 151 of the local enterprise gateway (LEG) 150 .

2, the local enterprise gateway (LEG) 150 receives the S1 Initial UE message from the base station 130 (S210). The call origination signal message is a message generated according to the UE generating a call and transmitted to the base station 130. The call origination signal message may include subscriber location information, information of the mobility management unit (MME) 171, and the like.

The local corporate gateway (LEG) 150 may transmit and receive a message requesting the identification information of the terminal to the base station 130 (S220) (S230). That is, the local enterprise gateway (LEG) 150 transmits an S1 Downlink NAS Transport (NAS Identity Request) message including information requesting the IMSI, which is the identification information of the UE, to the base station 130. Thereafter, the LAG 150 receives the S1 Uplink NAS Transport (NAS Identity Response) message including the IMSI, which is the identification information of the UE, from the BS 130.

The local enterprise gateway (LEG) 150 compares the identification information of the terminal (for example, IMSI) included in the message received from the base station 130 with the identification information of the corporation terminal stored in its own repository, Or a general terminal (S240).

The local enterprise gateway 150 transmits the S1 Initial UE message received from the base station 130 to the core network 170 (more specifically, the mobility management unit (MME) 171) The MME 171 receives the S1 Initial Context Setup Request message (S250) (S260). At this time, S1 bearer setup information (e.g., SGW GPT IP / TEID) may be included in the S1 Initial Context Setup Request message. At this time, the S1 bearer setup information (e.g., SGW GPT IP / TEID) may be requested by the MME 171 to the serving gateway (SGW) 173 and received (S253) (S255). After the mobility management unit (MME) 171 receives the S1 Initial UE Message from the local enterprise gateway (LEG) 150, the S1 bearer setup information (for example, SGW GPT IP / TEID) is transmitted to the serving gateway SGW 173). ≪ / RTI > Steps S250 and S260 are performed in the same manner regardless of the type of the terminal.

The local corporate gateway (LEG) 150 may set up a bearer (S1 bearer) according to the type of the terminal determined in step S240 described above, and the setting procedure thereof will be described in detail with reference to FIGS. 3 and 4 .

FIG. 3 is a flowchart illustrating a bearer setup process in a local enterprise gateway (LEG) according to an exemplary embodiment of the present invention.

That is, the bearer setup process of FIG. 3 is a flowchart of a bearer setup process according to a case where a call originated by a local enterprise gateway (LEG) 150 according to the present embodiment is determined to be a corporate terminal.

3, a terminal determination unit (S1-MME) 151 of a local enterprise gateway (LEG) 150 transmits an S1 Initial UE Message to a mobility management apparatus (MME) 171, (SGW GTP IP / TEID) message from the MME (MME) 171 (S310) (S320). The S1 Initial UE message is a message received from the terminal through the base station 130 by the local enterprise gateway (LEG) 150, and is generated and transmitted to the base station 130 as the terminal generates a call. The call origination signal message may include subscriber location information, information of the MME, and the like. Also, S1 bearer setup information (e.g., SGW GPT IP / TEID) may be included in the S1 Initial Context Setup Request message. Step S310 and step S320 described in FIG. 3 correspond to steps S250 and S260 described with reference to FIG. That is, the process of FIG. 3 is performed in succession of the operation of FIG.

The terminal determination unit (S1-MME) 151 of the regional enterprise gateway (LEG) 150 compares the identification information of the terminal received through the base station 130 with the identification information of the corporate terminal stored in the repository, . As shown in FIG. 2, upon receiving the identification information of the terminal through the base station 130, the type of the terminal is determined based on the type of the terminal It is possible to check only the result determined in the process of FIG. 2 after step S320, and proceed to the procedure after step S330 to be described later.

When the determination result is a corporation terminal, the SGSN (S-MME) 151 of the LAG 150 transmits an SGW GTP Setup Request (SGW (GTP IP / TEID) message from the bearer setup unit (S1-U) 153 (S330) S340). The SGW GTP Setup Request message includes bearer setup information (e.g., SGW GTP IP / TEID), and the SGW GTP Setup Response message includes bearer setup information (e.g., LEG GTP UL IP / TEID, LEG GTP DL IP / . ≪ / RTI >

Then, the terminal determination unit (S1-MME) 151 of the local enterprise gateway (LEG) 150 transmits an S1 Initial Context Setup Request (LEG GTP UL IP / TEID) message to the base station, Context Setup Response (HeNB GTP IP / TEID) message (S350) (S360). The S1 Initial Context Setup Request message includes bearer setup information (e.g., LEG GTP UL IP / TEID), and the S1 Initial Context Setup Response message includes bearer setup information (e.g., HeNB GTP IP / TEID).

The terminal determination unit (S1-MME) 151 of the regional enterprise gateway (LEG) 150 transmits a response message (S1 Initial Context Setup Response) for the step S320 to the mobility management apparatus (MME) (S370). At this time, the response message includes bearer setup information (e.g., LEG GTP DL IP / TEID).

Then, the terminal determination unit (S1-MME) 151 of the local enterprise gateway (LEG) 150 transmits bearer setup information such as the HeNB GTP IP / TEID to the bearer setup unit (S1-U) (HeNB GTP IP / TEID) message and transmits the HeNB GTP Setup Response message from the bearer setup unit (S1-U) When the above procedure is completed, a bearer (S1 Bearer) is established between the base station 130 and the local enterprise gateway (LEG) 150 and between the local enterprise gateway (LEG) 150 and the serving gateway (SGW) And the user data (packet) of the user terminal, that is, the corporation terminal, can be transmitted to the corporation network 190.

That is, the base station 130 does not acquire the SGW information (SGW GTP IP / TEID) of the core network 170 as the bearer setting information but the information of the local enterprise gateway (LEG) 150 (LEG STP UL IP / TEID And the bearer setting unit S1-U 153 of the local enterprise gateway (LEG) 150 obtains the base station information (HeNB GTP IP / TEID) and the SGW information (SGW GTP IP / TEID) And the core network 130 acquires the LEG 150 information (LEG GTP DL IP / TEID) as the bearer information and the bearer of the corporate terminal obtains the LEG 150 .

4 is a flowchart illustrating a bearer setup process in a local enterprise gateway (LEG) according to another embodiment of the present invention.

That is, the bearer setup process of FIG. 4 is a flowchart of a bearer setup process according to a case where a call originating at a local enterprise gateway (LEG) 150 according to the present embodiment is determined as a general terminal.

4, a terminal determination unit (S1-MME) 151 of a regional enterprise gateway (LEG) 150 transmits an S1 Initial UE Message to a mobility management apparatus (MME) 171, (SGW GTP IP / TEID) message from the MME (MME) 171 (S410) (S420). The S1 Initial UE message is a message received from the terminal through the base station 130 by the local enterprise gateway (LEG) 150, and is generated and transmitted to the base station 130 as the terminal generates a call. The call origination signal message may include subscriber location information, information of the mobility management unit (MME) 171, and the like. Also, S1 bearer setup information (e.g., SGW GPT IP / TEID) may be included in the S1 Initial Context Setup Request message. Step S410 and step S420 described in FIG. 4 correspond to steps S250 and S260 described with reference to FIG. That is, the process of FIG. 4 is performed in succession of the operation of FIG.

The terminal determination unit (S1-MME) 151 of the regional enterprise gateway (LEG) 150 compares the identification information of the terminal received through the base station 130 with the identification information of the corporate terminal stored in the repository, . In this embodiment, it is described that the type of the terminal is determined after step S420. However, the type of the terminal is determined immediately after receiving the terminal identification information through the base station as shown in FIG. 2 , Only the result determined in the process of FIG. 2 may be checked after step S420, and the procedure after step S430 to be described later may be performed.

If the result of the determination is a general terminal, the terminal determination unit (S1-MME) 151 of the LEG 150 transmits an S1 Initial Context Setup Request (SGW GTP IP / TEID) message to the base station 130 And receives the S1 Initial Context Setup Response message from the BS 130 in step S440. In this case, the S1 Initial Context Setup Request message includes bearer setup information (e.g., SGW GTP IP / TEID) and the S1 Initial Context Setup Response message may include bearer setup information (e.g., HeNB GTP IP / TEID) have.

Then, the terminal determination unit (S1-MME) 151 of the local enterprise gateway (LEG) 150 transmits a S1 Initial Context Setup Response message (HeNB GTP IP / TEID) A response message to step S420) (S450). At this time, the S1 Initial Context Setup Response message may include bearer setup information (e.g., HeNB GTP IP / TEID).

When the above procedure is completed, bearer (S1 Bearer) is established between the base station 130 and the serving gateway (SGW) 173, and user data (packet) Lt; / RTI >

That is, the base station 130 does not acquire the information (LEG STP UL IP / TEID) of the local enterprise gateway (LEG) 150 as the bearer setup information but also the SGW information (SGW GTP IP / TEID The core network 170 acquires base station information (HeNB GTP IP / TEID) instead of LEG 150 information (LEG GTP DL IP / TEID) as the bearer information, The bearer of the core network 170 is directly set from the base station 130 to the core network 170 without passing through the regional enterprise gateway (LEG)

According to the above description, the local enterprise gateway (LEG) 150 in this embodiment determines the type of terminal (corporate terminal or general terminal) using the identification information of the terminal and sets the bearer according to the determination result , It is possible to reduce the cost of setting an unnecessary bearer. Also, in the prior art, a bearer is established between the base station 130, the regional enterprise gateway (LEG) 150 and the core network (EPC) 170 regardless of the type of the terminal, and the generated user data (LEG) 150 to increase the load. Meanwhile, the local enterprise gateway (LEG) 150 according to the present embodiment sets a bearer (S1 Bearer) according to the type of the terminal and transmits the user data (packet) before transmitting the user data The load of the local enterprise gateway (LEG) 150 is reduced.

While the specification contains many features, such features should not be construed as limiting the scope of the invention or the scope of the claims. In addition, the features described in the individual embodiments herein may be combined and implemented in a single embodiment. On the contrary, the various features described in the singular embodiments may be individually implemented in various embodiments or properly combined.

Although the operations are described in a particular order in the figures, it should be understood that such operations are performed in a particular order as shown, or that all described operations are performed in a series of sequential orders, or to obtain the desired result. In certain circumstances, multitasking and parallel processing may be advantageous. It should also be understood that the division of various system components in the above embodiments does not require such distinction in all embodiments. The above-described application components and systems can generally be packaged into a single software product or multiple software products.

The method of the present invention as described above can be implemented in an application and stored in a computer-readable recording medium (CD-ROM, RAM, ROM, floppy disk, hard disk, magneto-optical disk, etc.). Such a process can be easily carried out by those skilled in the art and will not be described in detail.

It will be apparent to those skilled in the art that various modifications and variations can be made in the present invention without departing from the spirit or scope of the invention. The present invention is not limited to the drawings.

100: terminal (UE)
130: Base Station (HeNB)
150: Local Enterprise Gateway (LEG)
151: terminal determination unit (S1-MME)
153: Bearer setting unit (S1-U)
170: Core network
171: Mobility Management Device (MME)
173: Serving gateway (SGW)
190: Corporate Network

Claims (11)

An apparatus for determining a type of a terminal located at a time of generating a bearer for transmission of user data and setting a bearer according to a type of a terminal located between a base station and a core network,
A terminal determination unit for determining whether the terminal generating the call is a corporate terminal upon receiving a call origination signal message from the base station and for transmitting the bearer configuration information according to the determination result to the base station and the core network; And
When the terminal determining unit determines that the terminal generating the call is a corporation terminal, it transmits bearer setup information for the apparatus to the base station and the core network, and transmits a bearer between the base station and the core network via the apparatus And if bearer setup information for the core network is transmitted to the base station and bearer setup information for the base station is transmitted to the core network, A bearer setting unit for setting a bearer between the core networks;
/ RTI > delete delete The method according to claim 1,
The terminal determination unit,
A device for obtaining identification information from a terminal using a NAS Transport message and comparing the obtained identification information with identification information of a corporation terminal stored in a repository to determine whether the terminal is a corporation terminal. The method according to claim 1,
The apparatus comprises:
And a local corporate gateway (LEG) for performing a local breakout using a LoIP IP access between the base station and the core network. 5. The method of claim 4,
Wherein the identification information is an IMSI. A method for transmitting user data in a device located between a base station and a core network to determine a type of a terminal at a time of generating a bearer for transmission of user data and to set a bearer according to a type of the determined terminal,
Requesting and receiving identification information on a terminal that originated the call to the base station when the apparatus receives a call origination signal message from the base station;
Comparing the received identification information with identification information of a corporate terminal stored in a storage;
The apparatus transmits bearer setup information for the apparatus to the base station and the core network when the terminal generating the call is determined to be a corporate terminal, and establishes a bearer between the base station and the core network via the apparatus ; And
The base station transmits bearer setup information for the core network to the base station and transmits bearer setup information for the base station to the core network, Establishing a bearer between the core network and the core network;
/ RTI > for the transmission of user data. delete 8. The method of claim 7,
Wherein the receiving comprises:
And obtaining identification information from the terminal using the NAS Transport message. 8. The method of claim 7,
The apparatus comprises:
Is a local enterprise gateway (LEG) that performs a local breakout (Loack BreakOut) using an LIPA (Loacl IP Access) between the base station and the core network. 10. The method of claim 9,
Wherein the identification information is IMSI.
KR1020160023912A 2016-02-29 2016-02-29 Apparatus and method for setting a bearer for transmission of the user data KR101851328B1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
KR1020160023912A KR101851328B1 (en) 2016-02-29 2016-02-29 Apparatus and method for setting a bearer for transmission of the user data

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
KR1020160023912A KR101851328B1 (en) 2016-02-29 2016-02-29 Apparatus and method for setting a bearer for transmission of the user data

Publications (2)

Publication Number Publication Date
KR20170101420A KR20170101420A (en) 2017-09-06
KR101851328B1 true KR101851328B1 (en) 2018-04-23

Family

ID=59925628

Family Applications (1)

Application Number Title Priority Date Filing Date
KR1020160023912A KR101851328B1 (en) 2016-02-29 2016-02-29 Apparatus and method for setting a bearer for transmission of the user data

Country Status (1)

Country Link
KR (1) KR101851328B1 (en)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101297783B1 (en) * 2012-07-26 2013-08-20 콘텔라 주식회사 System for lte enterprise local communication and method therefor
US20130294403A1 (en) 2011-10-27 2013-11-07 Spidercloud Wireless, Inc. Long term evolution architecture and mobility
EP2422577B1 (en) 2009-04-23 2015-03-25 Telefonaktiebolaget LM Ericsson (publ) Local ip access through a femto base station

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2422577B1 (en) 2009-04-23 2015-03-25 Telefonaktiebolaget LM Ericsson (publ) Local ip access through a femto base station
US20130294403A1 (en) 2011-10-27 2013-11-07 Spidercloud Wireless, Inc. Long term evolution architecture and mobility
KR101297783B1 (en) * 2012-07-26 2013-08-20 콘텔라 주식회사 System for lte enterprise local communication and method therefor

Also Published As

Publication number Publication date
KR20170101420A (en) 2017-09-06

Similar Documents

Publication Publication Date Title
US10667187B2 (en) Method and apparatus for determining a bearer for mobile edge computing
KR101564855B1 (en) Traffic offload via local network based on apn-specific or non-apn-specific information
US8259673B2 (en) System and method for providing voice service in a mobile network with multiple wireless technologies
KR102044847B1 (en) Data transfer methods, devices and systems
US9706444B2 (en) Method and system for enabling circuit switched fallback service in evolved packet system
US20170094699A1 (en) Method, apparatus, system, computer program and computer program products for providing a plmn identifier to a node of a ran
US10827395B2 (en) Methods and apparatus for selecting a serving gateway for a session of a user equipment (UE) in a mobile network having 5G non-standalone (NSA) architecture deployments
WO2018070172A1 (en) User equipment, system and communication method for managing overload in the context of control plane cellular internet of things evolved packet system optimisation
US9572194B2 (en) Method and device for determining continuous session support during support of LIMONET in mobile communication system
JP2019521588A (en) Communication control method and related network element
CN108293228B (en) Method for establishing voice call and user equipment
CN105873241B (en) Method and device for establishing call connection
KR20190032505A (en) Paging method and paging device
EP2677784B1 (en) Method and device for establishing selected ip traffic offload connection under h(e)nb
WO2019085728A1 (en) Communication method and apparatus
WO2016201796A1 (en) Method and system for realizing private network registration, network element devices and computer storage medium
CN107277882B (en) Data routing method, device and base station
WO2021047454A1 (en) Location information acquisition method, location service configuration method, and communication device
KR101851328B1 (en) Apparatus and method for setting a bearer for transmission of the user data
EP3618558B1 (en) Method for enabling network to fall back and access network device
US20160227594A1 (en) Method, device and system for establishing connection
CN107294867B (en) Method and apparatus for facilitating peer-to-peer communication
US10524178B2 (en) SRVCC capability information transmission method and apparatus, and system
CN110278618B (en) Data processing method and system
KR101917831B1 (en) Method and apparatus for supporting local breakout service at serving gateway

Legal Events

Date Code Title Description
A201 Request for examination
E902 Notification of reason for refusal
E90F Notification of reason for final refusal
E701 Decision to grant or registration of patent right
GRNT Written decision to grant