WO2024023962A1

WO2024023962A1 - Protocol relay device, protocol relay system, protocol relay method, and protocol relay program

Info

Publication number: WO2024023962A1
Application number: PCT/JP2022/028895
Authority: WO
Inventors: 剛史山田; 健太篠原
Original assignee: 日本電信電話株式会社
Priority date: 2022-07-27
Filing date: 2022-07-27
Publication date: 2024-02-01

Abstract

A protocol relay device (100) comprises a C-plane processing unit (10), a U-plane processing unit (20), and a UPF container management unit (30). The UPF container management unit (30) notifies a UPF pod (300) of the establishment of connection. The C-plane processing unit (10) determines a UPF pod (300) for performing transfer processing on a PDU session designated in a request packet, and notifies the UPF pod (300) of the result of the determination. The U-plane processing unit (20) identifies the session ID of user plane traffic received from a base station (202), and transfers the session ID to the corresponding UPF pod (300) on the basis of the result of the determination.

Description

Protocol relay device, protocol relay system, protocol relay method, and protocol relay program

The present invention relates to a protocol relay device, a protocol relay system, a protocol relay method, and a protocol relay program.

In recent years, 5GC (5th Generation Core network) has been provided. 5GC is a mobile core network system that accommodates 5G wireless. On the other hand, in the conventional 4GC (4th Generation Core network) core network (EPC: Evolved Packet Core), the interface between devices is specified as point-to-point, and the interface between the control plane and user plane ) functions were not separated.

On the other hand, in 5GC, the functions of the control plane and user plane are clearly separated (this is also called C/U separation (CUPS: Control and User Plane Separation)), and by separating the C/U, , each function of the control plane and user plane can be developed independently. As a result, in 5GC, a Service Based Architecture (SBA) is introduced for control plane processing.

With the introduction of a service-based architecture in 5GC, a service mesh is incorporated, and a microservice architecture can be configured through containerization in control plane-related devices.

Within the service-based architecture, communication is performed via a service mesh using istio or the like using HTTP (Hyper Text Transfer Protocol). On the other hand, the N4 interface between the session management unit and the user plane function (UPF) uses a protocol called RFCP (Packet Transfer Control Protocol). Furthermore, a protocol called GTP-U (GPRS Tunneling Protocol for User Plane) is used in the N3 interface between the user plane device and the base station (gNB: next Generation Node B).

Here, for example, free5gc, which is open source software for 5GC, discloses that a user plane device can be constructed using a container (Non-Patent Document 1).

Additionally, in free5gc, each of the RFCP and GTP-U protocols requires the device to disclose its own unique IP (Internet Protocol) address to the opposing device. Therefore, in each of the RFCP and GTP-U protocols, it is necessary to assign an IP (Internet Protocol) address to each containerized user plane device.

Therefore, for example, Multus has been disclosed as a technology for giving each user plane device an IP address that allows communication with an external device (Non-Patent Document 2).

When communicating by giving a unique IP address to a containerized user plane device, there is a problem that flexible operation is difficult. For example, if each container is assigned a unique IP address for communication, settings must be changed for each device in operational scenarios that require container scale-out or scale-in. It is difficult to operate containers.

The present invention has been made in view of the above points, and provides a protocol relay device, a protocol relay system, a protocol relay method, and a protocol relay program that enable flexible operation of containerized user plane devices. The challenge is to provide.

The protocol relay device according to the present invention is a protocol relay device that is connected to one or more UPFs (User Plane Functions), and receives a connection request from the UPF, and responds to the interface of the connection request source. The UPF container management unit stores the IP address and notifies the UPF of connection establishment, and upon receiving a packet transfer control protocol request packet, transfers the PDU (Protocol Data Unit) session specified in the request packet. A control plane processing unit that determines a UPF and notifies the UPF of the determined result; and a control plane processing unit that identifies a session ID (identification) of user plane traffic received from a base station, and based on the result, identifies a session ID (identification) of user plane traffic received from a base station; and a user plane processing unit that performs network address translation on the UPF and transfers the translated address to the corresponding UPF.

According to the present invention, flexible operation of a containerized user plane device can be achieved using a protocol relay device, a protocol relay system, a protocol relay method, and a protocol relay program.

FIG. 1 is a block diagram showing the overall configuration of a protocol relay system according to the present embodiment. FIG. 2 is a block diagram showing the overall configuration of a protocol relay system, showing a method of concealment for base stations. FIG. 2 is a block diagram showing the configuration of a protocol relay device and a UPF pod of a protocol relay system according to the present embodiment. 12 is a flowchart showing the overall flow of a protocol relay device of the protocol relay system performing UPF pod concealment processing. 2 is a flowchart illustrating a flow in which a protocol relay device of a protocol relay system executes connection establishment with a UPF pod. 2 is a flowchart illustrating a flow in which a protocol relay device of a protocol relay system executes communication with a session management unit. 2 is a flowchart illustrating a flow in which the protocol relay device of the protocol relay system executes transfer using U-plane processing. 3 is a flowchart showing a flow in which a protocol relay device of a protocol relay system executes separation of a UPF pod. FIG. 2 is a hardware configuration diagram showing an example of a computer that implements the functions of a protocol relay device. FIG. 2 is a block diagram showing the system architecture of 5GC. FIG. 2 is an explanatory diagram showing the environment before the update in Blue/Green update. FIG. 2 is an explanatory diagram showing the environment after the update in Blue/Green update. It is an explanatory diagram showing a state before hiding a UPF container. FIG. 3 is an explanatory diagram showing a state after hiding the UPF container.

Next, a mode for carrying out the present invention (hereinafter referred to as "this embodiment") will be described. First, in an overview of the present technology, a conventional technology will be explained as a comparative example. Hereinafter, the same members and configurations will be denoted by the same reference numerals, and the description will be omitted as appropriate.

<Overview of this technology>
FIG. 10 is a block diagram showing the system architecture of 5GC. As shown in FIG. 10, the 5GC system architecture 500P includes a terminal 201, a base station 202, an access/mobility management unit 203, a session management unit 204, a network function disclosure management unit 205, a network function registration management unit 206, and a policy control unit. 207, an integrated data management section 208, an authentication server management section 209, a UPF pod 300, and a data network 400. Note that "/" is used with the intent of "and".

A terminal 201 indicates a wireless terminal (UE: User Equipment).
The base station 202 indicates a wireless base station (gNB: next generation Node B) compatible with the 5G wireless system.

The access/mobility management unit 203 indicates a function (AMF: Access and Mobility Management Function) that manages access and mobility.
The session management unit 204 represents a session management function (SMF).

The network exposure management unit 205 functions as a centralized point for publishing services (Network Exposure Function (NEF)), and has the role of approving all connection requests issued from outside the system.
The network function registration management unit 206 indicates a function (NRF: Network Repository Function) for registering network functions and services generated by them.

The policy control unit 207 indicates a function (PCF: Policy Control Function) that controls policies and rules of the 5G system.
The unified data management unit 208 represents a function (UDM: Unified Data Management) that is responsible for many services related to users and subscriptions.
The authentication server management unit 209 indicates a function (AUSF: Authentication Server Function) that processes procedures related to authentication.

The UPF pod 300 indicates a function (UPF: User Plane Function) that transfers user data packets. The data network 400 is a general term (DN: Data Network) for a network to which the Internet or a server providing some kind of service is connected.

Although only one UPF pod 300 is illustrated, a plurality of UPF pods 300 are interconnected to form a network. Further, the UPF pod 300 is an example of a UPF, and a UPF can be realized by, for example, a container, a virtual machine, a server, or the like. Note that the UPF pod 300 is displayed as the minimum unit configuring the UPF container.

The service-based architecture 500Q also includes an access/movement management unit 203, a session management unit 204, a network function disclosure management unit 205, a network function registration management unit 206, a policy control unit 207, an integrated data management unit 208, and an authentication server management unit. This is realized by the section 209.

In this technology, a comparative example when updating a UPF container will be described. There are reversible and irreversible methods for updating the UPF container under new and old environments, and business companies that operate public communication networks such as 5G often require a reversible method. .

For example, the Blue/Green update is a reversible method, and it is possible to prepare two environments, an old and a new environment, and then switch back to the old environment after switching to the new environment. On the other hand, the rolling update method is an irreversible method, in which the container environment is sequentially migrated to the new environment and the old environment is released, so it is not possible to switch back to the old environment.

When updating the UPF container to Blue/Green, the route of U-plane traffic is changed from the Blue environment to the Green environment. Therefore, in the Blue/Green update of the UPF container, the U-plane traffic connection established between the terminal 201 and the UPF pod 300 in the Blue environment is disconnected, and communication from the terminal 201 is temporarily interrupted. It becomes unusable.

FIG. 11A is an explanatory diagram showing the environment before update in Blue/Green update, and FIG. 11B is an explanatory diagram showing the environment after update in Blue/Green update.

As shown in FIG. 11A, the route T of U-plane traffic before the update is suitable for the Blue environment. Further, the UPF pods 301P to 303P are to be used in a blue environment, and the UPF pods 304P to 306P are to be used in a green environment.

As shown in FIG. 11B, after the update, the route T of the U-plane traffic that was being transferred by the UPF pods 301P to 303P in the Blue environment is disconnected due to the update, and the route T of the new U-plane traffic that has occurred after the update is U is transferred in the Green environment.

In this case, if the configurations of the UPF containers in the Blue environment and the Green environment can be hidden, the effect of the U-plane traffic route T being disconnected can be avoided.

<Consideration of concealment>
In order to operate a flexible UPF container, it is possible to hide the configuration of the UPF container.

FIG. 12A is an explanatory diagram showing the state before hiding the UPF container, while FIG. 12B is an explanatory diagram showing the state after hiding the UPF container.

In order to hide the configuration of the UPF containers (UPF pods 301P to 303P), it is conceivable to provide a gateway called the relay device 100P between the UPF pods 301P to 303P and the session management unit 204 (see FIG. 12B). In this case, the session management unit 204 will communicate with the IP address of the relay device 100P, and the UPF pods 301P to 303P will be recognized as one device.

The session management unit 204 not only communicates with the UPF pods 301P to 303P, but also has a function of notifying the terminal 201 side of the IP addresses of the UPF pods 301P to 303P as C-plane processing. Therefore, if the UPF pods 301P to 303P are hidden as shown in FIG. 12B, a single IP address will be notified to the terminal 201 side.

In this case, the relay device 100P needs to appropriately distribute PDU sessions to each of the UPF pods 301P to 303P in the U-plane communication processed between the terminal 201 and the UPF pods 301P to 303P (solid line in FIG. 12B). (see arrow).

Here, GTP-U for the N3 interface and FRCP for the N4 interface do not use a method like service-based architecture (a common communication method for Kubernetes). Therefore, when hiding the UPF container, it is necessary to hide both the N3 interface and the N4 interface at the same time.

Therefore, the protocol relay device according to the present embodiment enables flexible operation of the containerized UPF by appropriately hiding the configuration of the UPF container.

<Overview of concealment in protocol relay systems>
[1. Hiding UPF pod from session management section]
FIG. 1 is a block diagram showing the overall configuration of a protocol relay system according to this embodiment. Note that FIG. 1 shows a method of hiding the UPF pods 300 to 303 from the session management unit 204.

As shown in FIG. 1, the protocol relay system 500 includes a terminal 201, a base station 202, an access/mobility management unit 203, a session management unit 204, a protocol relay device 100, and UPF pods 301 to 303. . UPF pods 301 to 303 are simply referred to as UPF pod 300 unless there is a need to limit them to any one of them.

The protocol relay device 100 executes C-plane processing with the session management unit 204 to terminate the PFCP communication. The protocol relay device 100 also performs C-plane adjustment to the UPF pods 301 to 303, and notifies each UPF pod 301 to 303 of the adjustment results. Note that C-plane adjustment means determining the UPF pod 300 for a PDU session.

[2. Concealment of UPF pod from base station]
FIG. 2 is a block diagram showing the overall configuration of a protocol relay system, showing a method of concealment for base stations.

As shown in FIG. 2, protocol relay device 100 receives U-plane communication from terminal 201 or base station 202. The protocol relay device 100 transfers C-plane traffic to the corresponding UPF pods 301 to 303 based on the C-plane adjustment result.

<Overview of protocol relay device>
FIG. 3 is a block diagram showing the configuration of the protocol relay device and UPF pod of the protocol relay system according to the present embodiment.

As shown in FIG. 3, the protocol relay device 100 includes a C plane processing section 10 (control plane processing section), a U plane processing section 20 (user plane processing section), and a UPF container management section 30. .

The C-plane processing unit 10 temporarily stores the RFCP request packet from the session management unit 204 in a buffer. When the C-plane processing unit 10 receives an RFCP request packet, it determines the UPF that will transfer the PDU session specified in the request packet. The C-plane processing unit 10 generates an RFCP packet to be exchanged with the UPF pods 301 and 302, and notifies the UPF pods 301 and 302 of PDU session information to be transferred using a modified RFCP packet. In this way, the C-plane processing unit 10 notifies the UPF pods 301 and 302 of the adjustment result (determined result) of the transfer process.

The U-plane processing unit 20 identifies the session ID of the U-plane traffic received from the base station 202, performs network address translation on the U-plane traffic based on the adjustment result, and transfers it to the corresponding UPF 301, 302.

The UPF container management unit 30 receives a connection request from one or more UPF pods 301, 302, stores an IP address according to the interface of the connection request source, and establishes a connection to the UPF pod 301, 302. Notify. Further, when the UPF container management unit 30 receives a disconnection request from the UPF pod 301, 302, it deletes the IP address corresponding to the UPF pod 301, 302 that is the source of the disconnection request, and deletes the IP address corresponding to the UPF pod 301, 302 that is the source of the disconnection request. , 302. Delete the settings for converting the network address to the IP address of , 302. In this way, the UPF container management unit 30 can communicate with the connection management unit 310 of the UPF pod 300 and understand the configuration of the UPF container.

<Configuration of UPF pod>
Each of the UPF pods 301 and 302 includes a connection management section 310. The connection management unit 310 notifies the protocol relay device 100 of the connection request and establishes the connection. The connection management unit 310 communicates with the UPF container management unit 30 of the protocol relay device 100 and notifies the protocol relay device 100 of the configuration of the UPF pod 300.

<Initial state>
As shown in FIG. 3, as an example, the protocol relay system 500 includes two UPF pods 301 and 302. The two UPF pods 301 and 302 constitute a UPF container.

The protocol relay device 100 has an interface facing the base station 202 of the protocol relay device 100 (gNB facing interface), an interface facing the session management unit 204 of the protocol relay device 100 (SMF facing interface), and An interface facing the UPF pod 300 (UPF facing interface) is provided.

The UPF pods 301 and 302 include an interface facing the base station 202 of each UPF pod 300 (gNB facing interface), and an interface facing the session management unit 204 of each UPF pod 300 (SMF facing interface).

<UPF pod concealment process>
In the protocol relay system 500 according to this embodiment, the protocol relay device 100 executes a process of hiding the UPF pod 300.

FIGS. 4 to 8 are flowcharts showing how the protocol relay device of the protocol relay system executes the UPF pod concealment process. FIG. 4 shows a flowchart showing the overall flow of the protocol relay device 100 executing the UPF pod concealment process, and FIGS. 5 to 8 show flowcharts showing the detailed flow of each step.

First, in FIG. 4, the protocol relay device 100 establishes a connection with the UPF pod 300 (step S1). Specifically, the protocol relay device 100 receives a connection request from a UPF pod 300 in the UPF container management unit 30, stores an IP address corresponding to the interface of the connection request source, and connects to the UPF pod 300. Notify the establishment of. Note that detailed processing in step S1 will be described later using FIG. 5.

Next, the protocol relay device 100 communicates with the session management unit 204 (step S2). Specifically, upon receiving an RFCP request packet in the C-plane processing unit 10, the protocol relay device 100 determines the UPF pod 300 that transfers the PDU session specified in the request packet, and transfers the PDU session specified in the request packet. 300 of the determined result. Note that detailed processing in step S2 will be described later using FIG. 6.

Additionally, the protocol relay device 100 performs transfer using U-plane processing (step S3). Specifically, the protocol relay device 100 uses the U-plane processing unit 20 to identify the session ID of the U-plane traffic received from the base station 202, and performs network address translation on the U-plane traffic based on the determined result. and transfers it to the corresponding UPF pod 300. Note that detailed processing in step S3 will be described later using FIG. 7.

Then, the protocol relay device 100 disconnects the UPF pod 300 (step S4). Specifically, when the UPF container management unit 30 receives a disconnection request from the UPF pod 300, the protocol relay device 100 deletes the IP address corresponding to the UPF pod 300 that is the source of the disconnection request, and The settings for converting the network address to the IP address of the UPF pod 300 are deleted. Note that detailed processing in step S4 will be described later using FIG. 8.

When the UPF container management unit 30 deletes the setting for converting the network address to the IP address of the UPF pod 300 that is the source of the disconnection request, the protocol relay device 100 ends the hiding process for the UPF pod 300.

In this way, the protocol relay device 100 of the protocol relay system 500 can hide the UPF pod 300 from the base station 202 and the session management unit 204, so even if the configuration of the UPF pod 300 is changed, the protocol relay device 100 of the protocol relay system 500 can It is possible to flexibly operate the containerized UPF pod 300 without affecting the operation of the containerized UPF pod 300.

In particular, since the UPF container management unit 30 of the protocol relay device 100 can disconnect the UPF pod 300 that has stopped due to scale-in or the like, flexible operation can be achieved according to the configuration of the UPF pod 300.

Next, the process of establishing a connection with the UPF pod 300 in step S1 shown in FIG. 4 will be described in detail using the flowchart shown in FIG.

[Establishing connection with UPF pod]
Each UPF pod 300 notifies the UPF container management unit 30 of the protocol relay device 100 of a connection request from the connection management unit 310. Thereby, the protocol relay device 100 receives a connection request from each UPF pod 300 in the UPF container management unit 30 (step S11). This connection request includes the IP address of the interface of the opposing base station 202 of the UPF pod 300 that is the source of the connection request, and the IP address of the interface of the opposing session management unit 204.

The UPF container management unit 30 stores the received IP address of the interface of the opposing base station 202 of the UPF pod 300 that is the connection request source and the IP address of the interface of the opposing session management unit 204 as connection UPF information. (Step S12).

After storing the connection UPF information, the protocol relay device 100 notifies the connection management unit 310 of the UPF pod 300 that is the connection request source from the UPF container management unit 30 of the establishment of the connection (step S13).

In this case, the connection management unit 310 of the UPF pod 300 establishes a connection with the protocol relay device 100, and sets the opposite device as the protocol relay device 100 to a state where it can accept processing during GTP-U transfer. . Note that the GTP-U transfer process itself is assumed to be equivalent to, for example, the known technology free5gc.

In step S13, the protocol relay device 100 notifies the connection management unit 310 of the UPF pod 300 that is the connection request source of the establishment of the connection, and then proceeds to step S2 in FIG. 4.

Next, the communication process with the session management unit 204 in step S2 shown in FIG. 4 will be described in detail using the flowchart in FIG. 6.

[Communication with session management department]
In the protocol relay device 100, the C-plane processing unit 10 receives an RFCP request packet from the session management unit 204 (step S21). The protocol relay device 100 stores the received request packet in the buffer of the C-plane processing unit 10.

Next, in the protocol relay device 100, the C-plane processing unit 10 determines the UPF pod 300 specified in the RFCP request packet to transfer the PDU session (step S22). In this case, for example, two types of decision logic are illustrated below, and the protocol relay device 100 stores the decided result (adjustment result) in the C-plane processing unit 10 while the PDU session continues to exist.

The first decision logic is a method of allocating processing to all UPF pods. The second decision logic is how to allocate processing to specific UPF pods.

When allocating processing to all UPF pods, the C-plane processing unit 10 of the protocol relay device 100 determines all the UPF pods 300 as transfer devices for the U-plane traffic of the PDU session ID. Thereby, the protocol relay device 100 can load balance the U-plane traffic of the PDU session ID using round robin or the like.

Specifically, the C-plane processing unit 10 allocates all the UPF pods 301, 302, . . . as transfer destinations for each predetermined PDU session ID, for example.

On the other hand, when assigning processing to a specific UPF pod, for example, a hash that selects a specific UPF pod 300 within the range of options of UPF pods 300 in a connected state using a PDU session ID that identifies a PDU session as a key, etc. The following logic is prepared to determine the transfer destination UPF pod 300 corresponding to the PDU session ID. Thereby, when the protocol relay device 100 receives U-plane traffic, it can transfer it to a specific UPF pod 300 in units of PDU session IDs.

Specifically, the C plane processing unit 10 allocates the UPF pod 301 as a transfer destination UPF container to a certain PDU session ID, and assigns a UPF pod 301 as a transfer destination UPF container to another specific PDU session ID. Assign 302.

Next, the protocol relay device 100 changes the transmission source of the packet to the IP address of the UPF facing interface of the protocol relay device 100 in the C-plane processing unit 10, and changes the transmission destination to the UPF pod 300 of the determined transfer destination. The packet is transferred with the IP address of the SMF facing interface (step S23). In addition, in step S22, when allocating the process to all the UPF pods 300, multiple UPF pods 300 will be notified, so in that case, the C-plane processing unit 10 will A plurality of packets are generated and transferred to the UPF pod 300.

Next, the C-plane processing unit 10 receives a response packet from the UPF pod 300 (step S24).

Then, in the C-plane processing unit 10 of the protocol relay device 100, the source of the received response packet is changed to the IP address of the SMF facing interface of the protocol relay device 100, and the destination is changed to the session management unit 204, The packet is transferred (step S25). In this case, the protocol relay device 100 uses the C-plane processing unit 10 to delete the PFCP request packet stored in the buffer in step S21.

In step S25, the protocol relay device 100 deletes the PFCP request packet stored in the buffer, and then proceeds to step S3 in FIG. 4.

Next, the transfer process by the U plane process in step S3 shown in FIG. 4 will be described in detail using the flowchart in FIG.

[Transfer using U-plane processing]
In the U-plane processing unit 20, the protocol relay device 100 identifies the PDU session ID when receiving U-plane traffic at the gNB facing interface of the protocol relay device 100 and the UPF facing interface of the protocol relay device 100 (step S31).

The protocol relay device 100 uses the U-plane processing unit 20 to configure the transfer of U-plane traffic from both directions, from the base station 202 to the protocol relay device 100 and from the UPF pod 300 to the protocol relay device 100 (step S32).

In this case, the protocol relay device 100 uses the U-plane processing unit 20 to obtain the information (i.e., the adjustment result) of the UPF pod 300 to which the U-plane traffic of the PDU session ID is transferred, determined by the C-plane processing unit 10. , this is also referred to as forwarding destination UPF pod information.), the IP address of the gNB facing interface of the protocol relay device 100 and the gNB facing interface of the UPF pod 300, which is the forwarding destination of the U plane traffic of the PDU session ID. Set up network address translation according to the IP address of .

Note that if the process is assigned to all UPF pods in step S22 of FIG. 6, the transfer destination will be all UPF pods 300, so the transfer destination UPF pod 300 whose network address is converted by load distribution logic such as round robin. The IP address of the gNB facing interface is changed.

Further, when the U-plane processing unit 20 of the protocol relay device 100 receives return U-plane traffic from the UPF pod 300, the protocol relay device 100 includes the IP address of the gNB facing interface of the UPF pod 300 that is the transfer source, and the IP address of the gNB facing interface of the UPF pod 300 that is the transfer source. Set up network address translation using the IP address of the gNB facing interface.

After the protocol relay device 100 sets bidirectional transfer of U-plane traffic in step S32, it proceeds to step S4 in FIG. 4.

Next, the process of separating the UPF pod 300 in step S4 shown in FIG. 4 will be described in detail using the flowchart in FIG. 8.

[Disconnecting the UPF pod]
The UPF pod 300 may be stopped when the UPF pod 300 scales in or the like. Each UPF pod 300 to be stopped notifies a disconnection request from the connection management unit 310 to the UPF container management unit 30 of the protocol relay device 100. As a result, the protocol relay device 100 receives a disconnection request notification from the UPF pod 300 in the UPF container management unit 30 (step S41).

The UPF container management unit 30 of the protocol relay device 100 deletes the connected UPF information corresponding to the UPF pod 300 that is the source of the disconnection request (step S42).

Additionally, the UPF container management unit 30 deletes the network address translation settings corresponding to the UPF pod 300 that is the source of the disconnection request in the U-plane processing unit 20 (step S43). Thereby, the protocol relay device 100 can stop the transfer to the UPF pod 300 deleted in step S42 in the protocol relay system 500.

The UPF container management unit 30 of the protocol relay device 100 notifies the connection management unit 310 of the UPF pod 300 that issued the disconnection request of the completion of disconnection (step S44). As a result, when the connection management unit 310 of the UPF pod 300 receives the disconnection completion notification from the UPF container management unit 30, it determines that the connection with the protocol relay device 100 is disconnected (disconnection established status), The opposite device (protocol relay device 100) is made unable to accept GTP-U transfer processing.

When the protocol relay device 100 notifies the connection management unit 310 of the UPF pod 300 of the completion of disconnection (step S44), the concealment process of the UPF pod 300 ends.

<Hardware configuration of protocol relay device>
The protocol relay device 100 according to this embodiment is realized, for example, by a computer 900 having a configuration as shown in FIG.

FIG. 9 is a hardware configuration diagram showing an example of a computer that implements the functions of the protocol relay device. The computer 900 includes a CPU (Central Processing Unit) 901, ROM (Read Only Memory) 902, RAM 903, HDD (Hard Disk Drive) 904, input/output I/F (Interface) 905, communication I/F 906, and media I/F 907. have

The CPU 901 embodies the C-plane processing unit 10, the U-plane processing unit 20, and the UPF container management unit 30 by operating based on a program (protocol relay program) stored in the ROM 902 or HDD 904. The ROM 902 stores a boot program executed by the CPU 901 when the computer 900 is started, programs related to the hardware of the computer 900, and the like.

The CPU 901 controls an input device 910 such as a mouse or a keyboard, and an output device 911 such as a display or printer via an input/output I/F 905. The CPU 901 acquires data from the input device 910 via the input/output I/F 905 and outputs the generated data to the output device 911. Note that a GPU (Graphics Processing Unit) or the like may be used in addition to the CPU 901 as the processor.

The HDD 904 stores programs executed by the CPU 901 and data used by the programs. The communication I/F 906 receives data from other devices via a communication network (for example, NW (Network) 920) and outputs it to the CPU 901, and also sends data generated by the CPU 901 to other devices via the communication network. Send to device.

The media I/F 907 reads a program (for example, a protocol relay program) or data stored in the recording medium 912 and outputs it to the CPU 901 via the RAM 903. The CPU 901 loads a program related to target processing from the recording medium 912 onto the RAM 903 via the media I/F 907, and executes the loaded program. The recording medium 912 is an optical recording medium such as a DVD (Digital Versatile Disc) or a PD (Phase change rewritable disk), a magneto-optical recording medium such as an MO (Magneto Optical disk), a magnetic recording medium, a semiconductor memory, or the like.

For example, when the computer 900 functions as the protocol relay device 100 of the present invention, the CPU 901 of the computer 900 realizes each function of the protocol relay device 100 by executing a program loaded onto the RAM 903. Furthermore, data in the RAM 903 is stored in the HDD 904 . The CPU 901 reads a program related to target processing from the recording medium 912 and executes it. In addition, the CPU 901 may read a program related to target processing from another device via a communication network (NW 920).

<Effect>
Hereinafter, effects such as concealment processing of the UPF pod 300 in the protocol relay system 500 according to the present invention will be explained.

The protocol relay device 100 according to the present invention is a protocol relay device connected to one or more UPF pods 300, and receives a connection request from the UPF pods 300 and uses the IP address according to the interface of the connection request source. The UPF container management unit 30 stores the address and notifies the UPF pod 300 of connection establishment, and upon receiving an RFCP request packet, determines the UPF pod 300 that will transfer the PDU session specified in the request packet. The C-plane processing unit 10 notifies the UPF pod 300 of the determined result, identifies the session ID of the user plane traffic received from the base station 202, and assigns a network address to the user plane traffic based on the determined result. It is characterized by comprising a U-plane processing unit 20 that executes the conversion and transfers it to the corresponding UPF pod 300.

According to the protocol relay device 100 according to the present invention, the UPF container management unit 30 receives a connection request from the UPF pod 300 and establishes a connection with the UPF pod 300. The C-plane processing unit 10 receives the RFCP request packet and determines the UPF pod 300 to which the PDU session is to be transferred. Further, the C-plane processing unit 10 notifies the UPF pod 300 of the determined result of the transfer process. When the U-plane processing unit 20 receives user-plane traffic from the base station 202, it identifies its session ID, performs network address translation on the user-plane traffic based on the determined result of the forwarding process, and converts the user-plane traffic to the corresponding UPF. Forward user plane traffic to pod 300.

Thereby, the protocol relay device 100 can hide the configuration of the UPF pod 300 that constitutes the container from the base station 202 and the session management unit 204. Therefore, the protocol relay device 100 can operate the containerized UPF pod 300 flexibly.

Furthermore, when the UPF container management unit 30 receives a disconnection request from the UPF pod 300, the protocol relay device 100 according to the present invention deletes the IP address corresponding to the UPF pod 300 that is the source of the disconnection request, and The feature is that the setting for converting the network address to the original IP address of the UPF pod 300 is deleted.

According to the protocol relay device 100 according to the present invention, upon receiving a disconnection request from a UPF pod 300, the UPF container management unit 30 deletes the IP address corresponding to the UPF pod 300 that has issued the disconnection request, and Delete the settings to convert the network address to the IP address of .

Thereby, the protocol relay device 100 can determine the UPF pod 300 on which the C-plane processing unit 10 executes the transfer process according to the configuration of the UPF pod 300, so that flexible operation of the UPF pod 300 can be achieved. Can be done.

A protocol relay system 500 according to the present invention is a protocol relay system comprising one or more UPF pods 300 and a protocol relay device 100 connected to the UPF pod 300, and the UPF pod 300 is a protocol relay device. The protocol relay device 100 includes a connection management unit 310 that notifies the UPF pod 300 of a connection request and establishes the connection, and the protocol relay device 100 receives the connection request from the UPF pod 300 and assigns an IP address according to the interface of the connection request source. When the UPF container management unit 30 receives the RFCP request packet, it determines the UPF pod 300 that will transfer the PDU session specified in the request packet. The C-plane processing unit 10 notifies the UPF pod 300 of the determined result, identifies the session ID of the user plane traffic received from the base station 202, and performs network address translation on the user plane traffic based on the determined result. It is characterized by comprising a U-plane processing unit 20 that executes the processing and transfers it to the corresponding UPF pod 300.

According to the protocol relay system 500 according to the present invention, the UPF container management unit 30 of the protocol relay device 100 receives a connection request from the UPF pod 300 and establishes a connection with the UPF pod 300. The C-plane processing unit 10 receives the RFCP request packet and determines the UPF pod 300 to which the PDU session is to be transferred. Further, the C-plane processing unit 10 notifies the UPF pod 300 of the determined result. When the U-plane processing unit 20 receives user-plane traffic from the base station 202, it identifies the session ID, performs network address translation on the user-plane traffic based on the determined result, and sends the user-plane traffic to the corresponding UPF pod 300. Forward user plane traffic.

Thereby, the protocol relay system 500 can hide the configuration of the UPF pod 300 that constitutes the container from the base station 202 and the session management unit 204. Therefore, the protocol relay system 500 can operate the containerized UPF pod 300 flexibly.

Furthermore, when the UPF container management unit 30 of the protocol relay device 100 receives a disconnection request from the UPF pod 300, the protocol relay system 500 according to the present invention deletes the IP address corresponding to the UPF pod 300 that is the source of the disconnection request. At the same time, the setting for converting the network address to the IP address of the UPF pod 300 that is the source of the disconnection request is deleted.

According to the protocol relay system 500 according to the present invention, when the UPF container management unit 30 receives a disconnection request from the UPF pod 300, it deletes the IP address corresponding to the UPF pod 300 that is the source of the disconnection request, and Delete the settings to convert the network address to the IP address of .

As a result, the protocol relay system 500 can determine the UPF pod 300 on which the C-plane processing unit 10 executes the transfer process according to the configuration of the UPF pod 300, so that flexible operation of the UPF pod 300 can be achieved. Can be done.

Note that the present invention is not limited to the embodiments described above, and many modifications can be made within the technical idea of the present invention by those having ordinary knowledge in this field.

10 C plane processing section (control plane processing section)
20 U plane processing unit (user plane processing unit)
30 UPF container management unit 100 protocol relay device 100P relay device 201 terminal 202 base station 203 access/movement management unit 204 session management unit 205 network function disclosure management unit 206 network function registration management unit 207 policy control unit 208 integrated data management unit 209 authentication Server management section 300-303, 301P-306P UPF pod 310 Connection management section 400 Data network 500 Protocol relay system 500P System architecture

Claims

A protocol relay device connected to one or more UPFs (User Plane Functions),
a UPF container management unit that receives a connection request from the UPF, stores an IP (Internet Protocol) address corresponding to the interface of the connection request source, and notifies the UPF of establishment of the connection;
Upon receiving a packet transfer control protocol request packet, a control plane processing unit determines a UPF that will transfer the PDU (Protocol Data Unit) session specified in the request packet, and notifies the UPF of the determined result. ,
a user plane processing unit that identifies a session ID (identification) of user plane traffic received from a base station, performs network address translation on the user plane traffic based on the result, and forwards it to a corresponding UPF;
A protocol relay device comprising:
The UPF container management department is
When a disconnection request is received from the UPF, deleting the IP address corresponding to the UPF that is the source of the disconnection request, and deleting a setting for converting the network address to the IP address of the UPF that is the source of the disconnection request;
The protocol relay device according to claim 1, characterized in that:
A protocol relay system comprising one or more UPFs and a protocol relay device connected to the UPFs,
The UPF is
comprising a connection management unit that notifies the protocol relay device of a connection request and establishes a connection;
The protocol relay device is
a UPF container management unit that receives the connection request from the UPF, stores an IP address according to the interface of the connection request source, and notifies the UPF of establishment of the connection;
a control plane processing unit that, upon receiving a packet transfer control protocol request packet, determines a UPF that will perform transfer processing for the PDU session specified in the request packet, and notifies the UPF of the determined result;
a user plane processing unit that identifies a session ID of user plane traffic received from a base station, performs network address translation on the user plane traffic based on the result, and forwards it to a corresponding UPF;
A protocol relay system comprising:
The UPF container management department is
When a disconnection request is received from the UPF, deleting an IP address corresponding to the UPF that is the source of the disconnection request, and deleting a setting for converting the network address to the IP address of the UPF that is the source of the disconnection request;
The protocol relay system according to claim 3, characterized in that:
A protocol relay method for a protocol relay device connected to one or more UPFs, the method comprising:
The protocol relay device is
receiving a connection request from the UPF and storing an IP address according to the interface of the connection request source;
notifying the UPF of the establishment of a connection;
Upon receiving a packet transfer control protocol request packet, determining a UPF that will transfer the PDU session specified in the request packet, and notifying the UPF of the determined result;
identifying a session ID of user plane traffic received from a base station, and based on the result, performing network address translation on the user plane traffic and forwarding it to a corresponding UPF;
A protocol relay method characterized by performing the following.
The protocol relay device includes:
When a disconnection request is received from the UPF, the step of deleting an IP address corresponding to the UPF that is the source of the disconnection request, and deleting a setting for converting the network address to the IP address of the UPF that is the source of the disconnection request;
The protocol relay method according to claim 5, further comprising: performing a protocol relay method.
to the computer,
a step of receiving a connection request from one or more UPFs, storing an IP address corresponding to the interface of the connection request source, and notifying the UPF of the establishment of the connection;
Upon receiving a packet transfer control protocol request packet, determining a UPF that will transfer the PDU session specified in the request packet, and notifying the UPF of the determined result;
identifying a session ID of user plane traffic received from a base station, performing network address translation on the user plane traffic based on the result, and forwarding it to a corresponding UPF;
A protocol relay program for executing .
When a disconnection request is received from the UPF, a step of deleting an IP address corresponding to the UPF that is the source of the disconnection request, and a setting for converting the network address to the IP address of the UPF that is the source of the disconnection request;
8. The protocol relay program according to claim 7, for further executing.