KR101780402B1 - Method and apparatus for transmitting data - Google Patents

Method and apparatus for transmitting data Download PDF

Info

Publication number
KR101780402B1
KR101780402B1 KR1020160031644A KR20160031644A KR101780402B1 KR 101780402 B1 KR101780402 B1 KR 101780402B1 KR 1020160031644 A KR1020160031644 A KR 1020160031644A KR 20160031644 A KR20160031644 A KR 20160031644A KR 101780402 B1 KR101780402 B1 KR 101780402B1
Authority
KR
South Korea
Prior art keywords
service request
base station
request message
terminal
data
Prior art date
Application number
KR1020160031644A
Other languages
Korean (ko)
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 KR1020160031644A priority Critical patent/KR101780402B1/en
Application granted granted Critical
Publication of KR101780402B1 publication Critical patent/KR101780402B1/en

Links

Images

Classifications

    • H04L67/2809—
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/66—Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
    • H04W76/046—

Abstract

The present invention discloses a method and apparatus for transmitting data. According to an aspect of the present invention, there is provided a method for transmitting data in a device located between a base station and a core network and providing communication service between a terminal and a corporate network, the method comprising: receiving data to be transmitted from the enterprise network to the terminal; Transmitting a local paging message to the base station; Receiving a service request message from the base station; Confirming whether the service request message is received by the local paging message; And selectively changing a value of an RRC Establishment Cause (RRC Establishment Cause) included in the service request message according to a result of the confirmation and transmitting the RRC establishment cause to the core network.

Figure R1020160031644

Description

[0001] METHOD AND APPARATUS FOR TRANSMITTING DATA [0002]

The present invention relates to a method and an apparatus for transmitting data, and more particularly to a method of transmitting downlink data to a terminal when receiving a downlink packet (data) from a server of a corporate network in a state in which radio resources are released And apparatus.

The mobile communication company provides the mobile data service to the subscriber terminal through the system having the configuration as shown in FIG. 1 to be described later.

1 is a configuration diagram of a system for illustrating an environment of a mobile communication network providing data services according to the related art.

As shown in FIG. 1, in a general EPC network environment, the data triggered by the UE is normally serviced. However, if the packet is not transmitted or received for a predetermined time, the eNB may transmit a resource (e.g., a radio resource (e.g., LTE-Uu) between the terminal and the base station, a base station and an EPC (e.g., MME and SGW (E.g., S1, S11, etc.) between the mobile station UE and the mobile station UE to be used by other UEs.

At this time, if there is a packet (data) received from the PDN network (for example, the Internet network) by keeping the resources (for example, S5) established between the serving gateway SGW and the packet data network gateway PGW, Resources can be reallocated through a paging procedure through a device (MME) to enable mobile data services to be provided to subscriber terminals.

On the other hand, in the system as described above, a packet (data) can be offloaded by locating a device capable of breaking out the packet (data) (Local Enterprise Gateway). That is, a device (e.g., a LEG (regional enterprise gateway)) capable of breaking out the packet (data) can be located between the base station and the core network (e.g., MME and SGW) . At this time, if the data trunked by the terminal is in a normal environment, that is, in an environment in which an interface capable of transmitting and receiving data is normally connected, there is no problem in transmitting and receiving the data. The local enterprise gateway (LEG) is located between a base station and a core network (for example, MME and SGW), and is connected to a corporate network. The LEG relays packets (data) between a terminal and an Internet network or between a terminal and a corporate network Can play a role.

However, if the transmission / reception of the packet (data) does not occur for a predetermined time, the base station may release resources (e.g., radio resources and S1, etc.) connected to the terminal and the local enterprise gateway (LEG). In the environment as in the prior art, when packets (data) occur from the Internet network, the mobility management apparatus wakes up the terminal through the paging procedure, sets up a bearer, and transmits packets (data) buffered in the serving gateway As shown in FIG. However, in an environment in which a packet (data) break-out service is provided, when a packet (data) to be transmitted in the enterprise network occurs, a local enterprise gateway (LEG) located between the base station and the core networks (e.g., MME and SGW) The transmission procedure is performed to allocate resources, and the buffered packet (data) received from the enterprise network must be transmitted to the corresponding terminal. At this time, when the local enterprise gateway (LEG) proceeds with the paging message transmission procedure, it receives a message for ECM connection (RRC connection and S1 signaling connection) from the terminal and relays it to the mobility management device (MME). However, the mobility management apparatus (MME) may cause confusion because it has never transmitted a paging message. That is, since the mobility management apparatus MME has not transmitted the paging message, the mobility management apparatus MME requests a call release to the base station that has transmitted the message for the ECM connection, The call between the mobile station and the base station can be released, and the packet (data) generated in the enterprise network can not be transmitted to the mobile station.

Korean Laid-Open Patent No. 2015-0117836 (published on October 21, 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 packet breakout service environment in which packet data is generated from a corporate network to a terminal, And it is an object of the present invention to provide a method and apparatus for transmitting data such that the packet (data) is normally transmitted from an enterprise network to a terminal.

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 a method for transmitting data between a base station and a core network, the method comprising the steps of: ; Transmitting a local paging message to the base station; Receiving a service request message from the base station; Confirming whether the service request message is received by the local paging message; And selectively changing a value of an RRC Establishment Cause (RRC Establishment Cause) included in the service request message according to a result of the confirmation and transmitting the RRC establishment cause to the core network.

Wherein the step of transmitting the RRC establishing cause to the core network comprises the steps of: if the service request message is not confirmed to have been received by the local paging message, Transmitting to the network; And when the service request message is confirmed to be received by the local paging message, changing the value of the RRC Establishment cause of the service request message to a value indicating the service request message by the terminal's own trigger To the core network.

Further comprising the step of extracting and storing identification information of the terminal to receive the data after receiving the data, wherein the confirming step comprises: extracting identification information of the terminal corresponding to the service request message Requesting and receiving; And comparing the identification information of the received terminal with the identification information of the terminal stored in the storing step.

According to another aspect of the present invention, there is provided an apparatus for providing a communication service between a terminal and a core network, the communication network including a local gateway interface module; The base station transmits a local paging message to the base station. Upon receiving the service request message from the base station, the base station checks whether the service request message is received by the local paging message. A proxy MME module for changing a value of an included RRC establishing cause and transmitting the modified RRC establishment cause to the core network; And a proxy serving gateway module for transmitting the data received from the local gateway interface module to the base station.

The proxy MME module transmits the service request message to the core network without changing the value of the RRC Establishment cause of the service request message if the service request message is not confirmed to have been received by the local paging message. (RRC Establishment cause) value of the service request message to a value indicating that the service request message is a service triggered by the terminal's own trigger when the service request message is confirmed to be received by the local paging message To the core network.

Wherein the proxy MME module extracts and stores the identification information of the terminal to receive the data and then requests and receives identification information of the terminal corresponding to the service request message to the base station, And compares the stored identification information to check whether the service request message is received by the local paging message.

According to an aspect of the present invention, it is possible to seamlessly provide an incoming service of packets (data) generated in an enterprise network without changing an existing EPC network (MME / SGW).

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.
1 is a configuration diagram of a system illustrating an environment of a mobile communication network providing data service according to the related art,
2 is a diagram illustrating a configuration of a system according to an embodiment of the present invention.
FIG. 3 is a diagram illustrating a configuration of a local enterprise gateway (LEG) according to an embodiment of the present invention.
FIG. 4 is a flowchart illustrating packet (data) processing of a local enterprise gateway (LEG) according to an embodiment of the present invention.
5 is a diagram showing a flow of a packet (data) transmission method in a device according to an embodiment of the present invention.
6A and 6B illustrate a procedure for managing a matching table in a device according to an 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.

2 is a diagram illustrating a configuration of a system according to an embodiment of the present invention.

2, the system according to the present embodiment includes a mobile terminal (UE) 200, a base station (eNB) 300, a local enterprise gateway (LEG) 400, a mobility management apparatus (MME) 500, a serving gateway (SGW) 600, and a corporate network 900.

The UE 200 is a device for providing data communication and may be referred to as another term such as UE (User Equipment), MS (Mobile Station), UT (User Terminal), SS (Subscriber Station) The UE 200 may use a mobile communication network in which an LTE network including an EUTRAN (Evolved Universal Terrestrial Radio Access Network) is interworked. In addition, the UE 200 may use a mobile communication network in which a WCDMA network including a UTRAN is interworked. For example, conventional mobile phones such as a cellular phone, a PCS phone, a GSM phone, a CDMA-2000 phone, a WCDMA phone, etc., and a mobile phone using a smart phone, a tablet PC and a 4G network, .

The base station (eNB) 300 includes a femto base station, which is a small base station, and a macro base station. Here, the mat is a base station such as an eNB. A femto base station is a node located in a region of a macro base station with a large radius or outside a region of a macro base station and providing a specific communication service with a femtocell coverage for a small number of subscribers. Such a femto base station may be used in various terms such as an ultra-small base station, a pico base station, a Ubicell base station, and a 3GPP standard term HeNodeB.

The mobility management apparatus (MME) 500 is a node for managing subscriber information and mobility of a mobile terminal, and is responsible for session management, idle subscriber management, paging, and subscriber authentication functions. That is, the mobility management apparatus (MME) 500 is connected to the mobile terminal 200 or another network node such as a packet data network gateway (PGW) 700 or a Serving-GateWay (SGW) 600 or the like), and processing control signals when there is a request for setting up a radio bearer. In addition, it performs various functions of a control plane such as an EPS bearer or an IP tunnel, And performs mobility management and the like.

The serving gateway SGW 600 is a node for performing a session control and a data plane function for processing payload traffic according to a set session and includes a base station 300 and an S1 -U interface, supports inter-LTE / 3GPP handover, sets packet data network gateway (PGW) 700 and an EPS bearer (Evolved Packet System bearer), and transmits packet data using tunneling.

The packet data network gateway (PGW) 700 is connected to the serving gateway (SGW) 600 and forms an interface between the mobile communication network and the Internet network 800.

A local enterprise gateway (LEG) 400 is installed between the base station 300 and a core network (e.g., mobility management device / serving gateway) 500 (600). In the conventional LTE mobile communication network, there exist a 3G / LTE dual mode terminal and a base station that performs LTE based wireless communication with the terminals, and a mobility management apparatus 500 and a serving gateway 600 for communicating with such base stations exist do. The local enterprise gateway (LEG) 400 is added in the form of a proxy between the base station 300 and the mobility management apparatus (MME) / serving gateway (SGW) 500 (600).

The local enterprise gateway (LEG) 400 is added between the base station 300 and the core network (MME / SGW) 500 and 600 to transmit the signaling and packet Data) traffic through the network. The LAG 400 determines whether the mobile terminal 200 desires to access the enterprise network 900 and routes the packet to the enterprise network 900. [ The base station 300 transmits a radio resource (LTE-Uu) between itself and the terminal and a radio resource (LTE-Uu) between itself and the area The local enterprise gateway (LEG) 400 receives a packet to be transmitted from the enterprise network 900 to the terminal 200 in a state where resources (S1, etc.) between the enterprise gateway (LEG) 400 are released) It is buffered in a separate storage, and a local paging message is transmitted to the base station 300 to be allocated resources. The LEG 400 then changes the value of the RRC Establishment Cause (RRC Establishment Cause) included in the message (Service Request Message) for ECM setting received from the BS 300 To the mobility management apparatus (MME) 500, and transmits the buffered packet (data) to the destination terminal through the base station when the resource and bearer setup is completed.

A more detailed description of the regional enterprise gateway (LEG) 400 will be given later with reference to FIG. A method of transmitting packets (data) by the regional enterprise gateway (LEG) 400 according to the present embodiment will be described later with reference to FIG.

FIG. 3 is a diagram illustrating a configuration of a local enterprise gateway (LEG) according to an embodiment of the present invention.

Referring to FIG. 3, a local enterprise gateway (LEG) 400 according to the present embodiment includes a proxy MME module 310, a proxy base station (Proxy eNB) module 320, a proxy serving gateway (Proxy SGW) Module 330, a proxy base station (Proxy eNB) module 340, a packet distributor module 350, and a local gateway interface (GW) In describing the present embodiment, the detailed configuration of the regional enterprise gateway (LEG) is described as being executed individually according to the functions thereof, but the present invention is not limited thereto. The functions of the configurations Lt; / RTI >

The Proxy MME (Proxy MME) module 310 performs an MME role for a lower actual base station (femto base station, eNB, etc.) It does not actually perform the function, but it relays the signaling message. At the same time, the proxy base station (Proxy eNB) module 320 also performs a base station for the received signaling messages and performs interworking with the MME of the actual communication service provider network.

The proxy MME module 310 acquires information (e.g., IMSI information) from a signaling message transmitted and received between the base station 300 and the mobility management apparatus (MME) 500 and stores the information in a matching table And manage it. The Proxy MME module 310 transmits a local paging message to the base station 300 to wake up the terminal when the base station 300 receives packets (data) from the enterprise network 900 in a state where resources with the base station are released do.

Upon receiving the Service Request message from the base station 300, the proxy MME module 310 transmits an Identity Request message to the base station 300, requests identification information (IMSI) of the terminal that transmitted the Service Request message, And acquires identification information (IMSI) of the terminal by receiving a response message (an Identity Response message).

The proxy MME module 310 checks whether the acquired IMSI is present in the matching table and confirms whether the Service Request message is transmitted from the terminal that received the local paging message. For example, the proxy MME module 310 obtains the IMSI of the terminal from the base station 300 and determines whether the identification information (IMSI) exists in the matching table. When the IMSI is present in the matching table, the proxy MME module 310 determines whether the packet received from the base station 300 has been received from the base station 300, if the packet (data) having the destination IP address corresponding to the matching IP address is buffered The service request message can be confirmed as a response from the terminal receiving the local paging message.

If the service request message received from the base station is not answered from the terminal receiving the local paging message, the proxy MME module 310 transmits the received service request message to the proxy base station module 320 as it is.

When the Service Request message received from the base station 300 is a response from the terminal receiving the local paging message, the proxy MME module 310 transmits an RRC establishment cause cause) information to Mo-Data, and then transmits the Service Request message. This means that the Mo-Data wakes up and connects to the network by calling (for example, meaning that there is a packet (data) to be transmitted from the terminal).

The proxy MME module 310 may acquire and store IMSI information using signaling message information transmitted and received between the base station 300 and the EPC network (MME)

The Proxy SGW module 330 serves as a Serving-GW for the lower-level real base station (femto base station, eNB, etc.) 300. It actually plays a role of relaying packets (data) instead of performing functions. The proxy serving gateway module 330 transmits the packet (data) received from the base station 300 to the upper packet distributor 350 and transmits the packet (data) received from the packet distributor 350 to the base station 300 do.

The proxy serving gateway module 330 may relay the packet (data) buffered in the repository to the base station 300.

The proxy serving gateway module 330 can acquire TeID information when packets (data) are generated from the terminal. The packet (data) may include the TeID and the IP address information of the terminal. The proxy serving gateway module 330 may retrieve the session information using the TeID and then store and manage the IP address information of the terminal by matching with the IMSI.

The packet distributor 350 analyzes the packet (data) received from the proxy serving gateway module 330 and determines whether to forward the packet to the enterprise network 900. If the packet is distributed to the enterprise network 900, And transfers the packet (data) to the gateway interface module 360. On the other hand, when the packet (data) is a packet (data) which should not be transmitted to the enterprise network 900, that is, a packet (data) to be transmitted to a business network 350 transmits the packet (data) to the proxy base station module 340. At this time, the packet distributor 350 checks the destination IP address of the received packet (data), and transmits the packet (data) to the enterprise network 900 when the destination IP address is the IP address of the enterprise network. (Data) to a business network (e.g., the Internet network) 800 to provide a packet breakout service. Meanwhile, the IP address of the enterprise network 900 may be previously stored in a separate repository. The proxy base station module 340 acts as a base station with respect to the received packet (data) and performs interworking with the serving gateway 600 of the actual communication service provider network.

The packet distributor 350 buffers (stores) the packet (data) in a separate storage when the packet (data) is received from the base station 300 and the enterprise network 900 in a state in which resources are released, do. The packet distributor 350 transmits the buffered packet (data) to a destination terminal when a resource is allocated and a bearer is established between the base station and the terminals.

FIG. 4 is a flowchart illustrating packet (data) processing of a local enterprise gateway (LEG) according to an embodiment of the present invention.

In the description of the present embodiment, it is assumed that a system including a local enterprise gateway (LEG) 400 is capable of sending and receiving a signaling message and transmitting and receiving a packet (data) in a normal state in which connections between respective components are established.

Referring to FIG. 4, a local enterprise gateway (LEG) 400 according to the present embodiment receives packets (data) from a base station 300 (S410). The local enterprise gateway (LEG) 400 extracts a destination IP address from the received packet (data) (S420).

The local enterprise gateway (LEG) 400 compares the extracted destination IP address with a corporate network IP address (S430). That is, it is determined whether the packet (data) is a packet to be transmitted to the enterprise network. At this time, the IP address of the enterprise network may be stored and managed in a separate storage in advance by a manager or the like.

If the result of the determination is negative, the local enterprise gateway (LEG) 400 routes the packet (data) to the enterprise network 900 (S440). At this time, the local enterprise gateway (LEG) 400 may change the header information of the packet (data) through the NAT function so that the packet (data) is normally transmitted to the enterprise network 900. On the other hand, if they do not match, the packet (data) is routed to the EPC network (e.g., the serving gateway SGW 600) (S450).

5 is a diagram showing a flow of a packet (data) transmission method in a device according to an embodiment of the present invention.

According to the present embodiment, a device providing a packet breakout service, for example, a local enterprise gateway (LEG) 400, is located between a base station and a core network (MME / SGW) 500 (600). At this time, in the system including the local enterprise gateway (LEG) 400, the terminal does not transmit and receive packets for a predetermined period of time, and the base station 300 transmits a resource (LTE-Uu) between the base station and the local enterprise gateway (LEG), and the like). In this case, the local enterprise gateway (LEG) 400 will explain a procedure for transmitting the packet (data) to the destination terminal when the packet (data) is received from the enterprise network 900.

Referring to FIG. 5, a procedure for transmitting packets (data) in the apparatus according to the present embodiment will be described as follows.

First, the local enterprise gateway (LEG) 400 receives the packet (data) to be transmitted from the enterprise network (local server) 900 to the terminal, and buffers (stores) the packet (data) in a separate repository ). At this time, since the local enterprise gateway (LEG) 400 is in a state in which the resource connection with the base station 300 is released, the LEG 400 can transmit the buffered packet (data) to the destination terminal through the following steps.

A. Local Paging Message Send Phase

: When the packet (data) received from the enterprise network 900 is a packet (data) to be transmitted to the terminal from which the resource is released, the local enterprise gateway (LEG) Message is transmitted (S520). At this time, the confirmation of whether the packet is received from the enterprise network 900 can be confirmed by checking the source IP address of the packet (data) received by the local enterprise gateway (LEG) 400. For example, the source IP address of the packet (data) received from the enterprise network (local server) 900 is different from the source IP address of the packet (data) received from the provider network (Internet network) The local paging message may include parameter information such as a message type, a UE Identity Index Value, a UE Paging Identity, a CN Domain, and a TAI. At this time, the UE Paging Identity can set IMSI or TMSI as its value. However, since the TMSI is a temporarily generated number and is difficult to manage because of its variability, the local enterprise gateway (LEG) 400 uses the IMSI as the value of the UE Paging Identity parameter.

The local enterprise gateway (LEG) 400 determines whether there is an IMSI of the terminal mapped with the IP address of the received packet (data), and transmits the identification information (IMSI) of the terminal to the local paging message To the base station (HeNB) 300. Since the base station (HeNB) 300 stores the identification information (IMSI) of the last registered terminal, when receiving the local paging message including the identification information of the terminal (IMSI) from the local enterprise gateway (LEG) The corresponding base station can broadcast the received local paging message to the terminals located in its own area by confirming whether the identification information (IMSI) matches.

On the other hand, according to the above description, the packet (data) received from the enterprise network 900 does not include the identification information (IMSI) of the terminal. For example, the packet (data) includes a source IP address, a destination IP address, and user data. Since the IMSI is included in the local paging message of the local enterprise gateway (LEG) 400, the identification information (IMSI) of the terminal corresponding to the destination IP address of the received packet (data) Should be extracted. Accordingly, the local enterprise gateway (LEG) 400 should manage a table in which the destination IP address of the packet (data) received from the enterprise network (local server) matches the identification information (IMSI) of the terminal. The matching table may be separately stored and managed in advance. At this time, the IMSI stored in the matching table can be managed in two ways according to the type of the terminal.

The first method of storing the matching table is when a terminal uses a fixed IP address, and the local enterprise gateway (LEG) 400 stores the IP address and identification information (IMSI) of the terminal in a separate repository .

A second method of storing the matching table is a case where the UE does not use a fixed IP address and the LEG 400 is transmitted between the base station and the EPC network (MME / SGW) 500 (600) (IMSI) and IP address information of the UE using the S1-MME information and the S1-U Data information. A more detailed description thereof will be described later with reference to FIGS. 6A and 6B.

B. Step of checking whether or not a response from the terminal receiving the local paging message

: In the above described local paging message transmission step, the base station (HeNB) 300 receiving the paging message from the local enterprise gateway (LEG) 400 transmits the paging message to the terminals And broadcasts a paging message. The UEs receiving the local paging message complete the RRC connection setup with the base station (HeNB) 300 (S530). After completing the RRC connection setup, the terminals can transmit a Service Request message to the local enterprise gateway (LEG) 400 via the base station (HeNB) 300 (S540). The Service Request message is a message transmitted from the UE to the Mobility Management Agent (MME) 500 to establish an ECM connection (RRC connection and S1 signaling connection). The Service Request message may include an Initial UE Message, and the Initial UE Message may include RRC Establishment cause information and S-TMSI information. At this time, the value of the RRC Establishment cause information is set to MT-Access (Mobile Terminating-Access). The MT-Access means that the terminal wakes up again upon reception and connects to the network. That is, the Service Request is triggered by the network. At this time, since the local enterprise gateway (LEG) 400 does not have the terminal identification information (IMSI) in the Service Request message received from the base station (HeNB) 300, it is impossible to distinguish the terminal receiving the local paging message Do. That is, it is impossible to confirm whether or not the terminal according to the reception of the local paging message has transmitted the response message. Accordingly, the local enterprise gateway (LEG) 400 transmits an Identity Request message to the base station (HeNB) 300, requests identification information (IMSI) of the terminal that transmitted the Service Request message, and transmits a response message (IMSI) by receiving the response message (S550) (S560). The local corporate gateway (LEG) 400 determines whether the acquired identification information (IMSI) of the acquired terminal exists in the matching table, and confirms whether the service request message is transmitted from the terminal receiving the local paging message . For example, the local enterprise gateway (LEG) 400 obtains the terminal identification information (IMSI) from the base station (HeNB) 300 and confirms whether the identification information (IMSI) exists in the matching table. When the IMSI exists in the matching table, the LEG 400 notifies the base station (HeNB) (400) if the packet (data) having the destination IP address corresponding to the matched IP address is buffered, The service request message received from the mobile terminal 300 can be confirmed as a response from the terminal receiving the local paging message.

C. Change the inclusion information of the Service Request message

: In the step of confirming whether or not the terminal receives the local paging message, the local enterprise gateway (LEG) 400 checks whether the Service Request message received from the base station (HeNB) 300 is received from the terminal If it is not answered, the service request message is directly transmitted to the mobility management apparatus (MME) 500. Meanwhile, if the Service Request message received from the base station (HeNB) 300 is a response from the terminal receiving the local paging message, the LAG 400 transmits the Service Request message to the mobility management apparatus (MME) 500 The value of the RRC Establishment Cause information included in the Initial UE Message is changed to Mo-Data, and the RRC Establishment cause information is included in the Service Request message and transmitted (S570). This means that the Mo-Data wakes up and connects to the network by calling (for example, meaning that there is a packet (data) to be transmitted from the terminal). That is, the service request is triggered by the terminal itself. Then, the mobility management apparatus (MME) 500 receiving the Service Request message can proceed to the bearer setup procedure defined in the existing 3GPP standard. Accordingly, when the bearer setup procedure is completed, the local enterprise gateway (LEG) 400 can transmit the buffered packet (data) to the destination terminal without being influenced by the EPC network (MME / SGW) 500 .

6A and 6B illustrate a procedure for managing a matching table in a device according to an embodiment of the present invention.

The LAG 400 includes a base station (HeNB) 300 and an EPC 300. The base station (HeNB) 300 and the local enterprise gateway (LEG) (IMSI) and IP address information using a signaling message and a packet (S1-U Data) transmitted and received between the MME / SGW 500 and the MME / SGW 500, 600,

6A is a diagram illustrating a procedure for a local corporate gateway (LEG) 400 to acquire and store IMSI information using signaling message information transmitted between a base station and an EPC network (MME / SGW) 500 (600).

Referring to FIG. 6A, a local enterprise gateway (LEG) 400 receives an Attach Request message from a base station (HeNB) 300. The Attach Request message may include IMSI or S-TMSI information. At this time, the Attach Request message may include an S1 Initial UE Message, and the Initial UE Message may include an eNB UE S1AP ID (bearer setting information) (S611).

When the IMSI is included in the received message, the LAG 400 stores the IMSI in the matching table. Otherwise, the LAG 400 transmits an Identity Request including a Downlink NAS Transport message to the base station (HeNB) Message to request IMSI information (S613) (S615). Thereafter, the LAG 400 may receive an Identity Response message including an uplink NAS transport message from the base station (HeNB) 300 (S617). At this time, the Identity Response message includes the IMSI, and the IMSI may be stored in the matching table (S619). Then, the local enterprise gateway (LEG) 400 transmits an Attach Request message including an Initial UE Message to the mobility management apparatus (MME) 500 (S621). At this time, the Initial UE Message may include an LEG UE S1AP ID (bearer setting information), and the Attach Request message may include IMSI or S-TMSI information.

As described above, a session (bearer) can be established according to the transmission of a signaling message between the base station (HeNB) 300 and the EPC network (MME / SGW) Also, according to the present embodiment, the local enterprise gateway (LEG) 400 can acquire and store IMSI information.

Thereafter, when packet (data) is generated from the terminal as shown in FIG. 6B, the local corporate gateway (LEG) 400 can acquire TeID information (S623). The packet (data) may include the TeID and the IP address information of the terminal. Then, the local corporate gateway (LEG) 400 searches session information using the TeID, and then stores and manages the IP address information of the terminal by matching with the IMSI (S625).

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.

200: UE (UE)
300: base station (eNB)
310: Proxy MME (Proxy MME) module
320: Proxy eNB module
330: Proxy serving gateway (Proxy SGW) module
340: Proxy eNB module
350: Packet Distributor module
360: Local GW Interface module
400: Local Enterprise Gateway (LEG)
500: Mobility Management Device (MME)
600: Serving gateway (SGW)
700: packet data network gateway (PGW)
800: Business network (Internet network)
900: Enterprise network

Claims (6)

The present invention relates to a method for transmitting data in a device located between a base station and a core network and providing communication services between a terminal and a corporate network,
Receiving data to be transmitted from the enterprise network to the terminal;
Transmitting a local paging message to the base station;
Receiving a service request message from the base station;
Confirming whether the service request message is received by the local paging message; And
Modifying a value of an RRC Establishment Cause (RRC Establishment Cause) included in the service request message according to a result of the checking, and transmitting the changed RRC Establishment Cause to the core network;
Wherein the step of transmitting to the core network comprises:
Transmitting to the core network the value of the RRC establishment cause of the service request message without changing the value of the service request message if the service request message is not confirmed to have been received by the local paging message; And
When the service request message is confirmed to be received by the local paging message, changes the value of the RRC Establishment cause of the service request message to a value indicating that the service request message is a self- Lt; RTI ID = 0.0 > core network. ≪ / RTI > delete The method according to claim 1,
After receiving the data,
Further comprising extracting and storing identification information of the terminal to receive the data,
Wherein the verifying step comprises:
Requesting and receiving identification information of a terminal corresponding to the service request message to the base station; And
And comparing the identification information of the received terminal with the identification information of the terminal stored in the storing step. An apparatus for providing a communication service between a base station and a core network and between a terminal and a corporate network,
A local gateway interface module for receiving data to be transmitted from the enterprise network to the terminal;
The base station transmits a local paging message to the base station. Upon receiving the service request message from the base station, the base station checks whether the service request message is received by the local paging message. A proxy MME module for changing a value of an included RRC establishing cause and transmitting the modified RRC establishment cause to the core network; And
And a proxy serving gateway module for transmitting the data received from the local gateway interface module to the base station,
The proxy MME module comprises:
And transmits the service request message to the core network without changing the value of the RRC Establishment cause of the service request message if the service request message is not confirmed to be received by the local paging message, (RRC Establishment cause) value of the service request message to a value indicating that the RRC Establishment cause is a service request message by the terminal's own trigger, and transmits the RRC establishment cause to the core network . delete 5. The method of claim 4,
The proxy MME module comprises:
Extracting and storing identification information of the terminal to receive the data, requesting and receiving identification information of a terminal corresponding to the service request message to the base station, comparing the received identification information with the stored identification information, Thereby confirming whether the service request message is received by the local paging message.
KR1020160031644A 2016-03-16 2016-03-16 Method and apparatus for transmitting data KR101780402B1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
KR1020160031644A KR101780402B1 (en) 2016-03-16 2016-03-16 Method and apparatus for transmitting data

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
KR1020160031644A KR101780402B1 (en) 2016-03-16 2016-03-16 Method and apparatus for transmitting data

Publications (1)

Publication Number Publication Date
KR101780402B1 true KR101780402B1 (en) 2017-09-20

Family

ID=60033734

Family Applications (1)

Application Number Title Priority Date Filing Date
KR1020160031644A KR101780402B1 (en) 2016-03-16 2016-03-16 Method and apparatus for transmitting data

Country Status (1)

Country Link
KR (1) KR101780402B1 (en)

Citations (2)

* 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
US20150173121A1 (en) * 2012-08-02 2015-06-18 Telefonaktiebolaget L M Ericsson (Publ) Method and apparatus for reducing signaling in a core network

Patent Citations (2)

* 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
US20150173121A1 (en) * 2012-08-02 2015-06-18 Telefonaktiebolaget L M Ericsson (Publ) Method and apparatus for reducing signaling in a core network

Similar Documents

Publication Publication Date Title
US20200358657A1 (en) Method and apparatus for performing cell specific procedure or mobility procedure for network slice-based nr in wireless communication system
US10721738B2 (en) Base station device, gateway device, call connecting method, and wireless communication system
EP3493648B1 (en) Method and apparatus for performing cell specification procedure for network slice-based nr in wireless communication system
JP6005816B2 (en) Local IP access support method and apparatus in wireless communication network including femtocell
US10219143B2 (en) Data transmission method, mobility management entity, and mobile terminal
US9357571B2 (en) Local network and method for establishing connection between local gateway and home base station
EP2291052B1 (en) Circuit-switched services over LTE
US9635122B2 (en) Wireless communication system and method for transmitting content in wireless communication system
US20160150513A1 (en) Method and device for host configuration
CN101998549A (en) Method and system for configuring data carrying channel for user data by relay access system
KR20100110417A (en) Method and apparatus for supporting local breakout service at wireless communication network comprising femto cell
KR101663655B1 (en) Method handing handover in private network environment and private environment therefor
KR101383294B1 (en) Base station and virtual base station system for controllling connection of data offloading
KR101780402B1 (en) Method and apparatus for transmitting data
KR101587416B1 (en) method for obtaining IP addrss of mobile telecommunication terminal in LTE femtocell
AU2013201325B2 (en) A Traffic Offloading Apparatus
KR101555648B1 (en) Method for supporting interconnection between femto node and macro node, and femto gateway therefor
KR20160092388A (en) Method and Apparatus for Controlling Session for Providing Local Service in Mobile Small Cell

Legal Events

Date Code Title Description
E701 Decision to grant or registration of patent right
GRNT Written decision to grant