JP7306753B2 - Methods of providing services to user equipment and methods of receiving services at user equipment - Google Patents

Description

The present invention relates to a method of providing services to a user equipment and a method of receiving services on a user equipment.

For example, Mobile Edge Computing (MEC), as described in US Pat. information technology) to provide a service environment. In addition to ultra-low latency and high bandwidth, this environment will be able to provide direct access to wireless network information (subscriber location, cell load, etc.) that can be leveraged by applications and services.

WO2017/099165

There are several methods for realizing MEC as follows, but there is no standard method as defined by 3GPP (3rd Generation Partnership Project).

For example, the method of installing a DPI (Deep Packet Inspection) in the S1 section and changing the route of the destination IP packet for the MEC service has the following problems. That is, since the location of UE (User Equipment) is unknown in the service provision area for the MEC service, the UE cannot receive downlink packets from the network.

Also, if a PGW is deployed in the service area for MEC services and the PGW is interlocked with mobility control, the UE can receive downlink packets, but the PDN session needs to be reconfigured. That is, there is a service impact in that the UE is reassigned an IP address. Further, when the PGW is deployed in a service area for MEC services, facilities such as IPX (Internetwork Packet exchange) are required in the service area for MEC services in order to maintain connection for the Internet.

SUMMARY OF THE INVENTION It is an object of the present invention to provide a method for properly providing services to a user equipment and enabling the user equipment to properly receive services.

According to a first aspect of the present invention, a gateway device includes a first communication processing unit that communicates with a packet data network gateway that sets an address for a terminal device in an EPC (Evolved Packet Core) network; a second communication processing unit that communicates with a MEC server that provides services by Mobile Edge Computing); and an address management unit that manages information related to the address of the MEC server. When the destination address of the data for the terminal device is an address other than the address of the MEC server, the data is transferred between the terminal device and the packet data network gateway, and the second communication processing unit , when the destination address of the data for the terminal device is the address of the MEC server, data is transferred between the terminal device and the MEC server.

In the first aspect, the data transfer destination is determined by managing and comparing the address of the MEC server and other addresses. Here, the addresses used in this determination are IPv4 (Internet Protocol version 4) address, IPv4 address group, IPv6 (Internet Protocol version 6) address, IPv6 address group, Port number used in transport layer, and It may be a group of port numbers to be used, or information used to limit services in an upper layer.

According to a second aspect of the present invention, a method comprises communicating with a packet data network gateway that sets an address for a terminal device in an EPC (Evolved Packet Core) network; communicating with a serving MEC server; and managing information about an address of the MEC server, wherein in communicating with the packet data network gateway, a destination address of data for the terminal device. is an address other than the address of the MEC server, data is transferred between the terminal device and the packet data network gateway, and in communication with the MEC server, a data destination for the terminal device A method for transferring data between the terminal device and the MEC server when the address is the address of the MEC server.

According to a third aspect of the present invention, a program communicates with a packet data network gateway that sets an address for a terminal device in an EPC (Evolved Packet Core) network; A program that causes a processor to execute communication with a MEC server that provides a service and management of information related to the address of the MEC server. data is transferred between the terminal device and the packet data network gateway when the destination address of the data for the purpose is an address other than the address of the MEC server, and in the communication with the MEC server, the terminal device is the address of the MEC server, the program transfers data between the terminal device and the MEC server.

According to a fourth aspect of the present invention, a recording medium communicates with a packet data network gateway that sets an address for a terminal device in an EPC (Evolved Packet Core) network; A computer-readable non-temporary recording medium recording a program that causes a processor to perform communication with a MEC server that provides services by and to manage information about the address of the MEC server, In communication with the packet data network gateway, data transfer between the terminal device and the packet data network gateway when the destination address of the data for the terminal device is an address other than the address of the MEC server. and in communication with the MEC server, when the destination address of the data for the terminal device is the address of the MEC server, data is transferred between the terminal device and the MEC server. is a medium.

According to a fifth aspect of the present invention, there is provided a method for providing a service to a user device, wherein a first MEC (Mobile Edge Computing) server is changed to a second MEC server according to movement of the user device. and changing from the first core network device to the second core network device, and providing the service provided by the first MEC server via the first core network device to the second MEC server continuing to provide the user equipment via the second core network device by.

According to a sixth aspect of the present invention, there is provided a method for receiving service in a user equipment, wherein service is received by a first MEC (Mobile Edge Computing) server via a first core network equipment, and is changed from the first MEC server to the second MEC server and from the first core network device to the second core network device according to the movement of the second MEC continuing to receive said service via said second core network device by a server.

ADVANTAGE OF THE INVENTION According to this invention, it becomes possible to provide a service suitably to a user equipment, and to receive a service suitably by a user equipment. It should be noted that other effects may be achieved by the present invention instead of or in addition to the above effects.

FIG. 1 is an explanatory diagram showing an example of a schematic configuration of a system 1 according to an embodiment of the invention. FIG. 2 is a block diagram showing an example of a schematic configuration of the gateway device 100 according to the first embodiment. FIG. 3 is a diagram illustrating an example of a schematic configuration of an EPC network according to the embodiment; FIG. 4 is a diagram schematically showing the operation flow of each network node in the EPC network. FIG. 5 is a sequence diagram for explaining the tracking area update procedure. FIG. 6 is a diagram showing an example of a schematic configuration of an EPC network according to another embodiment. FIG. 7 is a block diagram showing an example of a schematic configuration of the gateway device 100 according to the second embodiment.

Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings. In addition, in the present specification and drawings, elements that can be described in the same manner can be omitted from redundant description by assigning the same reference numerals.

The description is given in the following order.
1. Overview of Embodiments of the Invention 2 . System configuration 3 . First embodiment 3.1. Configuration of Gateway Device 100 3.2. Technical features 3.3. Example 4. Second Embodiment 4.1. Configuration of Gateway Device 100 4.2. Technical features5. other forms

<<1. Overview of Embodiments of the Present Invention>>
First, an outline of an embodiment of the present invention will be described.

(1) Technical Issues MEC (Mobile Edge Computing) provides application developers and content providers with cloud computing capabilities and IT (information technology) service environments within wireless access networks close to mobile subscribers. do. In addition to ultra-low latency and high bandwidth, this environment will be able to provide direct access to wireless network information (subscriber location, cell load, etc.) that can be leveraged by applications and services.

There are several methods for realizing MEC as follows, but there is no standard method as defined by 3GPP (3rd Generation Partnership Project).

For example, the method of installing a DPI (Deep Packet Inspection) in the S1 section and changing the route of the destination IP packet for the MEC service has the following problems. That is, since the location of UE (User Equipment) is unknown in the service provision area for the MEC service, the UE cannot receive downlink packets from the network.

Also, if a PGW is deployed in the service area for MEC services and the PGW is interlocked with mobility control, the UE can receive downlink packets, but the PDN session needs to be reconfigured. That is, there is a service impact in that the UE is reassigned an IP address. Further, when the PGW is deployed in a service area for MEC services, facilities such as IPX (Internetwork Packet exchange) are required in the service area for MEC services in order to maintain connection for the Internet.

The purpose of the present embodiment is to appropriately provide both a service via a packet data network gateway and a service for MEC (Mobile Edge Computing) to a terminal device in an EPC (Evolved Packet Core) network. is to enable

(2) Technical Features In an embodiment of the present invention, for example, a gateway device communicates with a packet data network gateway that sets addresses for terminal devices in an EPC (Evolved Packet Core) network. The gateway device also communicates with an MEC server that provides services by MEC (Mobile Edge Computing). Also, the gateway device manages information on the address of the MEC server. Then, when the destination address of the data for the terminal device is an address other than the address of the MEC server, the gateway device transfers data between the terminal device and the packet data network gateway, If the destination address of the data for the terminal device is the address of the MEC server, data is transferred between the terminal device and the MEC server.

Thus, in the embodiment of the present invention, the destination of data transfer is determined by managing and comparing the address of the MEC server and other addresses. Addresses used in this judgment are IPv4 (Internet Protocol version 4) address, IPv4 address group, IPv6 (Internet Protocol version 6) address, IPv6 address group, Port number used in transport layer, Port number used in transport layer It may be information used for limiting services in groups or higher layers.

As a result, for example, in an EPC network, it becomes possible to appropriately provide both a service via a packet data network gateway and a service via an MEC to a terminal device.

The technical features described above are specific examples of the embodiments of the present invention, and the embodiments of the present invention are not limited to the technical features described above.

<<2. System configuration >>
An example of the configuration of a system 1 according to an embodiment of the present invention will be described with reference to FIG. FIG. 1 is an explanatory diagram showing an example of a schematic configuration of a system 1 according to an embodiment of the invention. Referring to FIG. 1, system 1 includes gateway device 100, packet data network gateway 200 (hereinafter also referred to as PGW 200), mobile edge computing server 300 (hereinafter also referred to as MEC server 300), base station 400, and A terminal device 500 is included.

For example, the system 1 is a system conforming to the standards/specifications of the 3GPP (Third Generation Partnership Project). More specifically, for example, the system 1 may be a system conforming to the standards/specifications of LTE/LTE-Advanced and/or SAE (System Architecture Evolution). Alternatively, the system 1 may be a system conforming to the fifth generation (5G)/NR (New Radio) standards/specifications. Of course, system 1 is not limited to these examples.

(1) Gateway device 100
The gateway device 100 is a node of the core network and communicates with each of the PGW 200, the MEC server 300, and the base station 400 via the network.

(2) PGW200
The PGW 200 is a junction point with the Internet 2, that is, a junction point with a PDN (Packet data network), and is a gateway that performs IP address assignment, packet transfer to a serving gateway (SGW), and the like. Also, the PGW 200 communicates with the gateway device 100 via the network, as shown in FIG.

(3) MEC server 300
The MEC server 300 is a server that provides an MEC service, is communicably connected to the gateway device 100 , and transmits and receives data used for the MEC service to and from the terminal device 500 via the gateway device 100 and the base station 400 .

(4) Base station 400
The base station 400 is a node of a radio access network (RAN), and performs radio communication with a terminal device (for example, the terminal device 500) located within its coverage area.

For example, the base station 400 may be an evolved Node B (eNB) or a generation Node B (gNB) in 5G.

(5) Terminal device 500
A terminal device 500 performs wireless communication with a base station. For example, the terminal device 500 performs wireless communication with the base station 400 when located within the coverage area of the base station 400 . For example, the terminal device 500 is UE (User Equipment).

<<3. First Embodiment>>
Next, a first embodiment of the present invention will be described with reference to FIGS. 2 to 6. FIG.

<3.1. Configuration of Gateway Device 100>
Next, an example of the configuration of the gateway device 100 according to the first embodiment will be described with reference to FIG. FIG. 2 is a block diagram showing an example of a schematic configuration of the gateway device 100 according to the first embodiment. Referring to FIG. 2, gateway device 100 includes network communication unit 110 , storage unit 120 and processing unit 130 .

(1) Network communication unit 110
Network communication unit 110 receives signals from a network and transmits signals to the network.

(2) Storage unit 120
The storage unit 120 temporarily or permanently stores programs (instructions) and parameters for the operation of the gateway device 100 and various data. The program includes one or more instructions for operation of gateway device 100 .

(3) Processing unit 130
The processing unit 130 provides various functions of the gateway device 100 . The processing unit 130 includes a first communication processing unit 131 , a second communication processing unit 133 and a management unit 135 . Note that the processing unit 130 may further include components other than these components. That is, the processing unit 130 can perform operations other than those of these components. Specific operations of the first communication processing unit 131, the second communication processing unit 133, and the management unit 135 will be described later in detail.

For example, the processing unit 130 (first communication processing unit 131 ) communicates with the packet data network gateway 200 via the network communication unit 110 . Also, the processing unit 130 (second communication processing unit 133 ) communicates with the MEC server 300 via the network communication unit 110 .

(4) Implementation Example The network communication unit 110 may be implemented by a network adapter and/or a network interface card or the like. The storage unit 120 may be implemented by memory (eg, non-volatile memory and/or volatile memory) and/or hard disk or the like. Processing unit 130 may be implemented by one or more processors, such as a Baseband (BB) processor and/or other types of processors. The first communication processing unit 131, the second communication processing unit 133, and the management unit 135 may be implemented by the same processor, or may be separately implemented by different processors. The memory (storage unit 120) may be included within the one or more processors or may be external to the one or more processors.

Gateway device 100 may include a memory that stores a program (instruction) and one or more processors that can execute the program (instruction). The one or more processors may execute the program to perform the operations of the processing unit 130 (the operations of the first communication processing unit 131, the second communication processing unit 133, and/or the management unit 135). The program may be a program for causing the processor to execute the operation of the processing unit 130 (the operation of the first communication processing unit 131, the second communication processing unit 133, and/or the management unit 135).

Note that the gateway device 100 may be virtualized. That is, the gateway device 100 may be implemented as a virtual machine. In this case, the gateway device 100 (virtual machine) may operate as a virtual machine on a physical machine (hardware) including a processor, memory, etc. and a hypervisor.

<3.2. Technical features>
Next, technical features of the first embodiment will be described.

The gateway device 100 (first communication processing unit 131) communicates with the packet data network gateway 200 that sets addresses for terminal devices (eg, terminal device 500) in the EPC network. Also, the gateway device 100 (second communication processing unit 133) communicates with the MEC server 300 that provides MEC services. Also, the gateway device 100 (management unit 135 ) manages information about the address of the MEC server 300 .

Then, when the destination address of the data for the terminal device (for example, the terminal device 500) is an address other than the address of the MEC server 300, the gateway device 100 (the first communication processing unit 131) For example, data is transferred between the terminal device 500 ) and the packet data network gateway 200 . Further, when the destination address of the data for the terminal device (for example, the terminal device 500) is the address of the MEC server, the gateway device 100 (the second communication processing unit 133) and the MEC server 300.

Thus, the gateway device 100 determines the data transfer destination by managing and comparing the address of the MEC server and other addresses. Addresses used in this judgment are IPv4 (Internet Protocol version 4) address, IPv4 address group, IPv6 (Internet Protocol version 6) address, IPv6 address group, Port number used in transport layer, Port number used in transport layer It may be information used for limiting services in groups or higher layers.

For example, the gateway device 100 (first communication processing unit 131, second communication processing unit 133, management unit 135) functions as an MME (Mobility Management Entity), SGW, and PGW for the service area of the MEC server 300.

(1) Address Specifically, the address for the terminal device is an IP (Internet Protocol) address assigned by the PGW 200 to the terminal device (for example, the terminal device 500).

Further, the address of the MEC server 300 is specifically the IP address of the MEC server 300 . Further, the information about the address of the MEC server 300 managed by the gateway device 100 (management unit 135) is, for example, the IP address and domain of the MEC server 300 that can be recognized within the gateway device 100 (eg, DNS server). This is information about the correspondence with the first name.

(2) Service Area of MEC Server 300 The service area of the MEC server 300 is specifically an area identified by a tracking area identifier.

As described above, when the service area of the MEC server 300 is identified by the tracking identifier, the gateway device 100 performs the following processing, for example, in processing related to tracking area update.

For example, when receiving a tracking area update request to the service area of the MEC server 300 from the terminal device 500, the gateway device 100 (management unit 135) acquires the information about the address of the MEC server 300. managed by

Further, the gateway device 100 (first communication processing unit 131), for example, when receiving a tracking area update request to the service area of the MEC server 300 from the terminal device 500, to the packet data network gateway 200 , send a Modify Bearer Request message.

Subsequently, gateway device 100 (first communication processing unit 131 ) receives a Modify Bearer Response message from packet data network gateway 200 . Thereby, the S5 interface is set between the gateway device 100 and the packet data network gateway 200 . That is, after receiving the Modify Bearer Response message from packet data network gateway 200, gateway device 100 (first communication processing unit 131) communicates with packet data network gateway 200 using the S5 interface.

<3.3. Example>
Next, examples according to the first embodiment will be described.

(1) Network configuration example FIG. 3 is a diagram illustrating an example of a schematic configuration of an EPC network according to an embodiment. In the example shown in FIG. 3, MME0 is a mobility management entity that controls base stations in the Macro area, and SGW0 is a serving gateway for transmitting signals for terminal devices (eg, UEs) in the Macro area. .

Also, PGW0 or PGW3 corresponds to the packet data network gateway 200 described above.

Also, MEC Server1 or MEC Server2 corresponds to the MEC server 300 described above.

A set of MME1, SGW1 and PGW1 or a set of MME2, SGW2 and PGW2 corresponds to the gateway device 100 described above.

As described above, the gateway device 100 functions as a packet data network gateway (PGW1 or PGW2) for the MEC server 300 (MEC Server1 or MEC Server2). For this reason, the packet data network gateway, which is the EPC session anchor, is composed of a total of two gateways: PGW0 for the Internet and PGW for the MEC server 300 (for example, PGW1 or PGW2, one function of the gateway device 100). will be

With such a configuration, for example, when a terminal device (UE) reaches MEC area1, it becomes possible to access services provided by MEC Server1. Here, the PGW0 for the Internet recognizes the movement of the terminal device (UE) as a handover of an SGW change (for example, a change from SGW0 to SGW1). In other words, since there is no need to change the PDN session setting due to the PGW change, the IP address reassignment to the terminal device (UE) is not performed, and the service is not affected.

More specifically, the gateway device 100 functioning as a gateway for MEC Server1 confirms the destination IP address of the user packet, for example, by DPI provided in PGW1, and confirms that the destination IP address is the IP address of the destination of MEC Server1. , it acts as a PGW (PGW1) for MEC Server1. On the other hand, when the destination IP address is not the IP address of the destination of MEC Server 1, the gateway device 100 operates as an SGW (SGW1), and transfers the data contained in the user packet to the PGW (PWG0) for Internet via the S5 interface. transfer. Such an operation enables the terminal device (UE) to receive services provided by MEC Server1 while maintaining connectivity with PGW0. In other words, the PGW (PGW1) for MEC Server1 can hide its operation as an anchor from existing facilities (for example, PGW0). In other words, there is no need to reconfigure the session to the PGW, and there is no reconfiguration of the IP address for the terminal equipment (UE), so there is an advantage that application services are not affected.

Here, in MEC area1, the S5 reference point has a cascade configuration consisting of PGW0 and PWG1. In addition, the SGW (SGW1) to which the terminal device (UE) is connected in the MEC area1 can be treated as including the PGW (PGW1) for the MEC Server1. Therefore, the set of PGW1 and SGW1 may be called TGW (Tandem GW, Transit GW). Also, the End user IP address provided by PGW0 for Internet can be used by PGW1 for MEC Server1. Moreover, PGW1 for MEC Server11 may implement NAT (Network Address Translation) at an application layer level.

Also, since PGW1 for MEC Server1 works in conjunction with C-Plane mobility control, it is possible to transmit downlink packets from PGW0 to terminal equipment (UE). Moreover, MME1, SGW1, and PGW1, that is, the gateway device 100 is installed as facilities for MEC Server1. For this reason, there is an advantage that it is not necessary to add functions to existing equipment, and it is easy to introduce MEC services.

(2) Tracking Area Update Next, the tracking area update performed when the terminal device (UE) moves will be described with reference to FIGS. 4 and 5. FIG. FIG. 4 is a diagram schematically showing the operation flow of each network node in the EPC network. Also, FIG. 5 is a sequence diagram for explaining the tracking area update procedure.

(Movement from Macro area to MEC area1: ST1)
When the terminal device (UE) moves from the macro area to the MEC area1 and connects to the base station (eNodeB) of the MEC area1, there is a change in the tracking area across the TAI list, so TAU with MME, SGW change is activated. .

In this case, the MME (MME1) for MEC Server1 performs DNS settings so as to recognize only the SGW (SGW1) for MEC Server1. Also, the SGW (SGW1) for MEC Server1 sends a Modify Bearer Request to the PGW (for example, PGW0) to which the terminal device (UE) is connected. Thereby, the setting change of the S5 interface is executed.

(Movement from MEC area1 to MEC area2: ST2)
When the terminal device (UE) moves from MEC area 1 to MEC area 2 and connects to the base station (eNodeB) of MEC area 2, there is a change in the tracking area across the TAI list, so TAU with MME, SGW change is activated. .

In this case, the MME for MEC Server2 (MME2) performs DNS settings so as to recognize only the SGW for MEC Server2 (SGW2). Also, the SGW (SGW2) for MEC Server2 sends a Modify Bearer Request to the PGW (for example, PGW0) to which the terminal device (UE) is connected. Thereby, the setting change of the S5 interface is executed.

(Movement from MEC area 2 to Macro area: ST2)
When the terminal device (UE) moves from MEC area 2 to Macro area and connects to the macro area base station (eNodeB), there is a change in the tracking area across the TAI list, so TAU with MME, SGW change is activated. .

In this case, the SGW to which the terminal device (UE) is connected may be any SGW (for example, SGW0, SGW1, SGW2). SGW0 transmits a Modify Bearer Request to the PGW (for example, PGW0) to which the UE was connected. Thereby, the setting change of the S5 interface is executed.

- Effects According to this embodiment, it is possible to provide MEC services without changing the IP address of the terminal equipment (UE). Further, according to the present embodiment, PGW0 for Macro area can be used without changing the PDN session settings to PGWs (for example, PGW1 and PGW2) for MEC services in order to connect to MEC Servers 1 and 2. In other words, the terminal device (UE) can receive the MEC service without changing the settings related to the APN for Internet.

In addition, setting the APN for the MEC service in order to set the bearer for the MEC service is troublesome for the user because it takes time and effort. On the other hand, according to the present embodiment, the DPI provided in the PGW for MEC service (for example, PGW1, PGW2) sees the destination IP address of the user packet and sends it to the MEC server 3 only for MEC service. transfer processing. Therefore, the APN can provide the MEC service to the terminal equipment (UE) while being configured for the Internet.

Furthermore, according to this embodiment, the provided MEC service is enabled to take advantage of all mobility controls of EPC, including downlink. As a comparative example, when a DPI device is installed in the S1 section, the destination IP address of user packets can be checked and only those for the MEC service can be transferred to the MEC server, so that allocation is possible, but the position of the UE is not known. Therefore, the downlink from the MEC service to the UE cannot be implemented. On the other hand, in the present embodiment, as equipment for MEC services, for example, there is a set of MME1, SGW1 and PGW1, that is, the gateway device 100, so all mobility control of EPC can be used. This also allows operators to easily introduce equipment for MEC services. For example, the set of MME1, SGW1 and PGW1, that is, the points of contact between the gateway device 100 and the existing facility can be aggregated only at points S10 and S5.

(3) Other Embodiments FIG. 6 is a diagram showing an example of a schematic configuration of an EPC network according to another embodiment. As shown in FIG. 6, a gateway device 100 that functions as MMEs (MME1, MME2) is accommodated as equipment for MEC services. In this way, it becomes possible to notify SMS (Short Message Service) via the MME (gateway device 100) for the MEC service to the terminal device (UE) that has reached the MEC area1 or MEC area2. In other words, a terminal equipment (UE) located in the MEC area can recognize that the MEC service is available. In this case, the MMEs (MME1, MME2) for the MEC service can select the MEC server according to the user's country and send an SMS notification according to the language by confirming the MCC (Mobile country code).

Also, MMEs (MME1, MME2) for MEC services identify terminal capabilities and terminal contracts to determine whether or not to support MEC services, and reject tracking area update requests from terminal equipment (UE). You may This allows the MMEs (MME1, MME2) for the MEC service to control not to provide the MEC service to the terminal equipment (UE).

<<4. Second Embodiment>>
Next, a second embodiment of the present invention will be described with reference to FIG. While the first embodiment described above is a specific embodiment, the second embodiment is a more generalized embodiment.

<4.1. Configuration of Gateway Device 100>
First, an example of the configuration of the gateway device 100 according to the second embodiment will be described with reference to FIG. FIG. 7 is a block diagram showing an example of a schematic configuration of the gateway device 100 according to the second embodiment. Referring to FIG. 7 , the gateway device 100 includes a first communication processing section 141 , a second communication processing section 143 and a management section 145 . Specific operations of the first communication processing unit 141, the second communication processing unit 143, and the management unit 145 will be described later.

The first communication processing unit 141, the second communication processing unit 143, and the management unit 145 may be implemented by the same processor, or may be separately implemented by different processors. The first communication processing unit 141, the second communication processing unit 143, and the management unit 145 may include a memory for storing a program (instruction) and one or more processors capable of executing the program (instruction), The one or more processors may perform operations of the first communication processing unit 141 , the second communication processing unit 143 , and the management unit 145 . The program may be a program for causing the processor to execute the operations of the first communication processing unit 141 , the second communication processing unit 143 and the management unit 145 .

Note that each processor described above may be a virtual processor realized by a hypervisor or the like installed in a general-purpose computer, for example. Also, each memory described above may be a virtual memory realized by, for example, a hypervisor installed in a general-purpose computer.

<4.2. Technical features>
Next, technical features of the second embodiment will be described.

In the second embodiment, the gateway device 100 (first communication processing unit 141) communicates with the packet data network gateway 200 that sets addresses for terminal devices (eg, terminal device 500) in the EPC network. Also, the gateway device 100 (second communication processing unit 143) communicates with the MEC server 300 that provides the MEC service. Also, the gateway device 100 (management unit 145 ) manages information about the address of the MEC server 300 .

Then, when the destination address of the data for the terminal device (for example, the terminal device 500) is an address other than the address of the MEC server 300, the gateway device 100 (the first communication processing unit 141) For example, data is transferred between the terminal device 500 ) and the packet data network gateway 200 . In addition, when the destination address of the data for the terminal device (for example, the terminal device 500) is the address of the MEC server, the gateway device 100 (the second communication processing unit 143) and the MEC server 300.

For example, the first communication processing unit 141 may perform the operation of the first communication processing unit 131 according to the first embodiment described above. Also, the second communication processing unit 143 may perform the operation of the second communication processing unit 133 according to the first embodiment described above. Furthermore, the management unit 145 may perform the operation of the management unit 135 according to the first embodiment described above.

The second embodiment has been described above. According to the second embodiment, for example, in an EPC network, it is possible to appropriately provide both services via a packet data network gateway and services via an MEC to terminal devices.

<<5. Other forms>>
Although the embodiments of the present invention have been described above, the present invention is not limited to these embodiments. Those skilled in the art will appreciate that these embodiments are illustrative only and that various modifications can be made without departing from the scope and spirit of the invention.

For example, the steps in the processes described herein do not necessarily have to be executed in chronological order according to the order described in the sequence diagrams. For example, the steps in the process may be performed in an order different from that depicted in the sequence diagrams, or may be performed in parallel. Also, some of the steps in the process may be deleted and additional steps may be added to the process.

In addition, a device (for example, a plurality of devices (or unit) or a module for one of said plurality of devices (or units)) may be provided. A method may also be provided that includes the processing of the above components, and a program may be provided for causing a processor to execute the processing of the above components. Also, a non-transitory computer readable medium recording the program may be provided. Of course, such devices, modules, methods, programs, and computer-readable non-transitory recording media are also included in the present invention.

Some or all of the above embodiments may also be described in the following additional remarks, but are not limited to the following.

(Appendix 1)
a first communication processing unit that communicates with a packet data network gateway that sets an address for a terminal device in an EPC (Evolved Packet Core) network;
a second communication processing unit that communicates with a MEC server that provides services by MEC (Mobile Edge Computing);
a management unit that manages information about the address of the MEC server;
with
When the destination address of the data for the terminal device is an address other than the address of the MEC server, the first communication processing unit transfers data between the terminal device and the packet data network gateway. do,
The gateway device, wherein the second communication processing unit transfers data between the terminal device and the MEC server when a destination address of data for the terminal device is the address of the MEC server.

(Appendix 2)
The gateway device according to appendix 1, wherein the service area of the MEC server is an area identified by a tracking area identifier.

(Appendix 3)
Supplementary note 2, wherein the first communication processing unit transmits a Modify Bearer Request message to the packet data network gateway when a tracking area update request to the service area of the MEC server is received from the terminal device. Gateway device as described.

(Appendix 4)
The gateway device according to supplementary note 3, wherein the first communication processing unit receives a Modify Bearer Response message from the packet data network gateway.

(Appendix 5)
5. The gateway device according to appendix 4, wherein the first communication processing unit communicates with the packet data network gateway using an S5 interface after receiving the Modify Bearer Response message from the packet data network gateway.

(Appendix 6)
Communicating with a packet data network gateway that sets addresses for terminal devices in an Evolved Packet Core (EPC) network;
communicating with a MEC server that provides services by MEC (Mobile Edge Computing);
managing information about addresses of the MEC servers;
including
in communication with the packet data network gateway, transferring data between the terminal device and the packet data network gateway when the destination address of the data for the terminal device is an address other than the address of the MEC server; and
wherein, in communicating with the MEC server, transferring data between the terminal device and the MEC server when a destination address of the data for the terminal device is the address of the MEC server.

(Appendix 7)
Communicating with a packet data network gateway that sets addresses for terminal devices in an Evolved Packet Core (EPC) network;
communicating with a MEC server that provides services by MEC (Mobile Edge Computing);
managing information about addresses of the MEC servers;
is a program that causes the processor to execute
in communication with the packet data network gateway, transferring data between the terminal device and the packet data network gateway when the destination address of the data for the terminal device is an address other than the address of the MEC server; and
A program that, in communication with the MEC server, transfers data between the terminal device and the MEC server when a destination address of data for the terminal device is the address of the MEC server.

(Appendix 8)
Communicating with a packet data network gateway that sets addresses for terminal devices in an Evolved Packet Core (EPC) network;
communicating with a MEC server that provides services by MEC (Mobile Edge Computing);
managing information about addresses of the MEC servers;
A computer-readable non-temporary recording medium that records a program that causes a processor to execute
in communication with the packet data network gateway, transferring data between the terminal device and the packet data network gateway when the destination address of the data for the terminal device is an address other than the address of the MEC server; and
A recording medium that, in communication with the MEC server, transfers data between the terminal device and the MEC server when a destination address of data for the terminal device is the address of the MEC server.

In the EPC network, both services via packet data network gateway and services via mobile edge computing can be appropriately provided to terminal devices.

1 system 100 gateway device 131, 141 first communication processing unit 133, 143 second communication processing unit 135, 145 management unit 200 packet data network gateway 300 MEC server 400 base station 500 terminal device

Claims (4)

A method of providing a service to a user equipment, comprising:
changing an edge server providing services to the user device from a first edge server to a second edge server according to movement of the user device;
changing a core network device that communicates user packets for the user device via a radio access network from a first core network device to a second core network device;
The service provided to the user device via the first core network device by the first edge server is provided to the user device using the same IP address as the IP address assigned to the user device, using the second edge server. serving the user device via the second core network device by an edge server of . A method of obtaining service on a user device, comprising:
According to the movement of the user equipment, an edge server providing service to the user equipment is changed from a first edge server to a second edge server , and user packets relating to the user equipment are sent to the radio access network. is received from the first edge server via the first core network device by changing the core network device from the first core network device to the second core network device. continuing to receive services from said second edge server via said second core network device using the same IP address that was assigned to said user device . 3. The method according to claim 1 or 2, wherein said core network device acts as an anchor for said edge server and data network. 4. The method according to any one of claims 1 to 3, wherein data is transferred from the core network device to the edge server based on destination information of the data for the user equipment.

Images