MOBILE COMMUNICATION NETWORK CONTROL DEVICE, MOBILE COMMUNICATION NETWORK, AND COMPUTER PROGRAM
By integrating SGW-U and PGW-U functions in a single device and controlling them through PGW-C, the network achieves efficient packet transfer and simplified control in mobile communication networks, addressing the inefficiencies of separate SGW-C and PGW-C configurations.
Patent Information
- Application Number
- JP2024086433
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2023-05-29
- Filing Date
- 2024-05-28
- Publication Date
- 2024-12-04
- Estimated Expiration
- 2044-05-28
AI Technical Summary
Existing mobile communication networks face inefficiencies and complexity due to the separation of SGW-C and PGW-C functions, leading to unnecessary device changes and control complications when user equipment moves between areas.
Implementing SGW-U and PGW-U functions in a single device (SGW-U+PGW-U) while maintaining SGW-C and PGW-C as separate devices, with SGW-C controlling SGW-U+PGW-U through PGW-C, and using management devices to manage bearer settings based on request messages.
Enhances packet transfer efficiency and simplifies control operations by minimizing unnecessary device changes during user equipment movement, allowing coexistence of devices with combined and separate functions without complicating control.
Smart Images

Figure 0007594705000001_ABST
Abstract
Description
[Technical field]
[0001] The present disclosure relates to control architectures for mobile communication networks. [Background technology]
[0002] Regarding a mobile communication network based on the 3GPP (registered trademark) standard, Non-Patent Document 1 discloses a CUPS architecture in which a control plane (CP) and a user plane (UP) are separated.
[0003] According to Non-Patent Document 1, the serving gateway (SGW) is separated into an SGW-C, which is a function of the control plane (CP), and an SGW-U, which is a function of the user plane (UP), and the packet data network gateway (PGW) is separated into a PGW-C, which is a function of the CP, and a PGW-U, which is a function of the UP. The SGW and PGW are functions / devices of the 4th generation (also referred to as Long Term Evolution (LTE)) core network. The LTE core network is also referred to as the EPC.
[0004] The SGW-C can control one or more SGW-Us. Similarly, the PGW-C can control one or more PGW-Us. The SGW-U accommodates a base station (BS), and the PGW-U accommodates another SGW-U. The PGW-U is also connected to an external data network (DN) such as the Internet. The BS communicates wirelessly with a user equipment (UE). The UE is also called a wireless device (WD). In the EPC, in order to connect the UE and the DN, a connection called an "EPS bearer" is set between the UE and the PGW-U connected to the DN. The section of the EPS bearer between the UE and the BS is referred to as a "data radio bearer". The section of the EPS bearer between the BS and the SGW-U is referred to as an "S1 bearer". The section of the EPS bearer between the SGW-U and the PGW-U is referred to as an "S5 / S8 bearer". In the following, the EPS bearer is simply referred to as a "bearer". Non-Patent Document 1 also discloses a configuration in which the functions of the SGW-U and PGW-U are implemented in one device, and the functions of the SGW-C and PGW-C are implemented in one device.
[0005] In the 5th generation (also referred to as New Radio (NR)) core network (5GC), a session management function (SMF) and a user plane function (UPF) are defined. The UPF may be connected to a DN. In 5GC, in order to connect a UE and a DN, a connection called a protocol data unit (PDU) session is set between the UE and the UPF connected to the DN. The SMF controls the setting of the PDU session, etc. The SMF in 5GC corresponds to the PGW-C in the EPC, and the UPF in 5GC corresponds to the PGW-U in the EPC. For this reason, Non-Patent Document 2 discloses a configuration in which the functions of the SMF and PGW-C are implemented in one device, and the functions of the UPF and PGW-U are implemented in one device. [Prior art documents] [Non-patent literature]
[0006] [Non-Patent Document 1] 3GPP TS 23.214 V16.2.0 (2020-09) [Non-Patent Document 2] 3GPP TS 23.501 V16.10.0 (2021-09) Summary of the Invention [Problem to be solved by the invention]
[0007] FIG. 1 shows an example of an EPC that employs the CUPS architecture described in Non-Patent Document 1. Although the BS is not a core network device, it is shown for understanding the configuration. In FIG. 1, the dotted lines indicate the paths of control signaling, and the solid lines indicate the paths of user packets. The lines connecting the devices indicate the interface names between the devices. FIG. 1 shows a configuration in which the functions of the SGW-U, PGW-U, SGW-C, and PGW-C are each treated as separate devices. The mobility management function (MME) manages the location of the UE and has a function as a gateway for control signaling transmitted from the UE to the core network. For example, control signaling transmitted from the UE requesting the setting of a bearer is transferred to the MME. When the MME receives control signaling from the UE requesting the setting of a bearer, the MME cooperates with the SGW-C and PGW-C to set up a bearer between the UE and the PGW-U via the BS and SGW-U. The MME is associated with an area obtained by dividing the geographical range in which the mobile communication network provides services, for example. The MME transmits and receives control signaling to and from UEs located in the associated area.
[0008] Figure 2 shows another example of an EPC that employs the CUPS architecture described in Non-Patent Document 1. SGW-U+PGW-U in Figure 2 indicates a device that implements the functions of SGW-U and PGW-U, and SGW-C+PGW-C indicates a device that implements the functions of SGW-C and PGW-C.
[0009] In the configuration of Fig. 2, the number of devices that forward user packets between DN and UE is fewer than in the configuration of Fig. 1, so the packet forwarding efficiency is higher in the configuration of Fig. 2 than in the configuration of Fig. 1. However, like the MME, the SGW-C is associated with an area, and when the UE moves between areas, the SGW-C that controls the bearer for the UE may change. On the other hand, the PGW-C is associated with a DN, and even if the UE moves, the PGW-C that controls the bearer for the UE does not change. Therefore, if the functions of the SGW-C and PGW-C are implemented in one device, unnecessary changes to the PGW-C occur as the UE moves, making control complicated.
[0010] Furthermore, even if the SGW-U and PGW-U are implemented in one device, it is difficult to replace the existing SGW-U and the existing PGW-U with a device that implements both the SGW-U and the PGW-U at once. Therefore, it is necessary to operate the core network in a situation where a device that implements both the SGW-U (first function) and the PGW-U (second function) functions and a device that implements the SGW-U (first function) but does not implement the PGW-U (second function) are mixed.
[0011] The present disclosure provides a technique for operating a core network in a situation in which devices that implement both a first function and a second function and devices that implement the first function but do not implement the second function are mixed. [Means for solving the problem]
[0012] According to one aspect of the present invention, a first device including a first function for accommodating a base station and a second function for connecting to an external data network, a second device including the first function, and a first control device for controlling the first device; a management device for receiving control signaling from a user equipment; In a mobile communication network including the above, a control device that controls the second device sends a request message requesting the establishment of a bearer connecting a user device and the first device. From the management deviceThe device is equipped with a receiving means for receiving the request message, and a processing means for executing either a first process for setting up the bearer that passes through the second device or a second process for setting up the bearer that does not pass through the second device based on information contained in the request message. Effect of the Invention
[0013] According to the present disclosure, a core network can be operated in a situation where there is a mixture of devices that implement both the first function and the second function and devices that implement the first function but do not implement the second function. [Brief description of the drawings]
[0014] [Figure 1] FIG. 1 is a diagram showing an example of the configuration of a mobile communication network disclosed in Non-Patent Document 1. [Diagram 2] FIG. 1 is a diagram showing an example of the configuration of a mobile communication network disclosed in Non-Patent Document 1. [Diagram 3] FIG. 1 is a configuration diagram of a mobile communication network according to an embodiment. [Figure 4] FIG. 1 is a diagram showing an example of the configuration of a mobile communication network according to an embodiment. [Diagram 5] FIG. 5 is a diagram showing a state in which the UE has been handed over from the state shown in FIG. 4. [Figure 6] FIG. 11 is a sequence diagram showing an example of a bearer setting process. [Figure 7] FIG. 11 is a sequence diagram showing an example of a handover process. [Figure 8] FIG. 1 is a diagram showing an example of the configuration of a mobile communication network according to an embodiment. [Figure 9] FIG. 11 is a diagram showing an example of determination information. [Figure 10] FIG. 11 is a sequence diagram showing another example of a bearer setting process. [Figure 11] FIG. 11 is a sequence diagram showing yet another example of a bearer setting process. [Figure 12] FIG. 1 is a diagram showing an example of the configuration of a mobile communication network according to an embodiment. [Figure 13]FIG. 13 is a diagram showing a state in which the UE has been handed over from the state shown in FIG. 12; [Figure 14] FIG. 11 is a sequence diagram showing an example of a handover process. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0015] Hereinafter, the embodiments will be described in detail with reference to the accompanying drawings. Note that the following embodiments do not limit the invention according to the claims, and not all combinations of features described in the embodiments are essential to the invention. Two or more features among the multiple features described in the embodiments may be arbitrarily combined. In addition, the same reference numbers are used for the same or similar configurations, and duplicated descriptions are omitted.
[0016] First Embodiment FIG. 3 is a configuration diagram of a core network of a mobile communication network according to this embodiment. Although the BS is not a device of the core network, it is shown for understanding the configuration. In this embodiment, the functions of both the SGW-U and the PGW-U are implemented in one device (hereinafter, written as SGW-U+PGW-U), but the functions of the PGW-C and the SGW-C are implemented as separate devices. The PGW-C controls the functions of the PGW-U in the SGW-U+PGW-U. The SGW-C controls the functions of the SGW-U in the SGW-U+PGW-U. The SGW-C is associated with an area, for example, like the MME, and controls a bearer for UE in the area. When controlling the SGW-U+PGW-U, the SGW-C does not directly transmit control signaling to the SGW-U+PGW-U, but transmits control signaling to the PGW-C and controls the SGW-U in the SGW-U+PGW-U via the PGW-C.
[0017] Fig. 4 shows an example of the configuration of a mobile communication network according to this embodiment. In Fig. 4, MME#1 and SGW-C#1 are responsible for controlling UEs connected to one or more BSs including BS#1 in area#1. Similarly, MME#2 and SGW-C#2 are responsible for controlling UEs connected to one or more BSs including BS#2 in area#2. SGW-U+PGW-U connect to DN. PGW-C transmits and receives control signaling to and from SGW-U+PGW-U.
[0018] In Fig. 4, UE#1 is connected to BS#1 in area#1, and a bearer is set between UE#1 and SGW-U+PGW-U via BS#1. Fig. 6 is a sequence diagram of a process for setting up a new bearer for UE#1. Note that the sequence in Fig. 6 is basically the same as the sequence disclosed in Non-Patent Document 1, so the following description will focus on the differences from the sequence in the configuration of Fig. 1 disclosed in Non-Patent Document 1. The sequence in Fig. 6 is started when UE#1 transmits a bearer setting request to MME#1 via BS#1.
[0019] In S10, MME#1 transmits a session creation request to SGW-C#1. The session creation request in S10 corresponds to a setting request message requesting the setting of a new bearer for UE#1. In the case of the configuration of FIG. 1, when SGW-C#1 receives a session creation request from MME#1, it transmits and receives control signaling based on the packet forwarding control protocol (PFCP) with SGW-U and performs necessary control for bearer setting on SGW-U. However, in this embodiment, SGW-C#1 controls SGW-U of SGW-U+PGW-U via PGW-C and does not directly communicate with SGW-U+PGW-U by PFCP. Therefore, SGW-C#1 transmits a session creation request to PGW-C in S11. Note that SGW-C#1 includes information necessary for controlling SGW-U of SGW-U+PGW-U in the session creation request transmitted to PGW-C.
[0020] Upon receiving the session creation request from SGW-C#1, the PGW-C transmits a PFCP session establishment request to SGW-U+PGW-U in S12, and receives a PFCP session establishment response from SGW-U+PGW-U in S13. That is, the PGW-C performs control required for bearer setup on SGW-U+PGW-U. The processes of S12 and S13 are the same as those performed between SGW-C+PGW-C and SGW-U+PGW-U in the configuration of FIG. 2. Upon receiving the PFCP session establishment response, the PGW-C transmits a session creation response to SGW-C#1 in S14, and the SGW-C#1 generates a session creation response based on the session information in the session creation response received from PGW-C in S15, and transmits it to MME#1. After that, MME#1 transmits and receives control signaling to BS#1 and UE#1 to perform processing for the wireless section side of the bearer.
[0021] When the processing for the wireless section side of the bearer is completed, MME#1 transmits a bearer modification request to SGW-C#1 in S16 to notify the processing result of the wireless section side. In the case of the configuration of FIG. 1, when SGW-C#1 receives the bearer modification request from MME#1, it performs necessary control on SGW-U to reflect the processing result of the wireless section in SGW-U. However, in this embodiment, SGW-C#1 controls SGW-U of SGW-U+PGW-U via PGW-C, and does not directly communicate with SGW-U+PGW-U. Therefore, SGW-C#1 transmits a bearer modification request to PGW-C in S17. Note that SGW-C#1 includes information necessary for reflecting the processing result of the wireless section in SGW-U of SGW-U+PGW-U in the bearer modification request transmitted to PGW-C.
[0022] Upon receiving the bearer modification request from the SGW-C#1, the PGW-C transmits a PFCP session modification request to the SGW-U+PGW-U in S18, and receives a PFCP session modification response from the SGW-U+PGW-U in S19. That is, the PGW-C performs a process to reflect the processing result of the wireless section in the SGW-U+PGW-U. The processes of S18 and S19 are the same as the processes performed between the SGW-C+PGW-C and the SGW-U+PGW-U in the configuration of FIG. 2. Upon receiving the PFCP session modification response, the PGW-C transmits a bearer modification response to the SGW-C#1 in S20, and the SGW-C#1 transmits the bearer modification response to the MME#1 in S21. As a result, a bearer between the UE#1 and the SGW-U+PGW-U is established.
[0023] Fig. 5 shows a state where UE#1 in the state shown in Fig. 4 moves towards area#2 and is handed over from BS#1 to BS#2. Fig. 7 is a sequence diagram of handover processing from BS#1 to BS#2. As with Fig. 6, Fig. 7 will mainly explain the differences from the sequence in the configuration shown in Fig. 1. The sequence in Fig. 7 starts when processing in the wireless section is completed and the target BS#2 transmits a switching request to MME#2.
[0024] In S30, MME#2 transmits a session creation request to SGW-C#2. The session creation request in S30 corresponds to a change request message that requests a change in the path of the bearer connecting UE#1 and SGW-U+PGW-U due to handover of UE#1. In the case of the configuration of FIG. 1, when SGW-C#2 receives a session creation request from MME#2, it transmits and receives control signaling based on the packet forwarding control protocol (PFCP) with SGW-U and performs necessary control for bearer setting on SGW-U. However, as described in the processing of S10 and S11 in FIG. 6, in this embodiment, it is not necessary to transmit and receive control signaling with SGW-U. Therefore, SGW-C#2 transmits a bearer modification request to PGW-C in S31. The bearer modification request includes information necessary for the control of SGW-U by SGW-U+PGW-U.
[0025] Upon receiving the bearer modification request from SGW-C#2, the PGW-C transmits a PFCP session modification request to SGW-U+PGW-U in S32, and receives a PFCP session modification response from SGW-U+PGW-U in S33. Through the processes of S32 and S33, the bearer route is changed from the route via BS#1 to the route via BS#2. The processes of S32 and S33 are similar to the processes performed between SGW-C+PGW-C and SGW-U+PGW-U in the configuration of FIG. 2. Upon receiving the PFCP session modification response, the PGW-C transmits a bearer modification response to SGW-C#2 in S34, and the SGW-C#2 transmits a session creation response to MME#2 in S35.
[0026] As described above, the UP SGW-U and PGW-U are implemented as a single device to improve the transfer efficiency of user packets. On the other hand, the SGW-C, which may be changed due to UE movement, and the PGW-C, which does not change due to UE movement, are implemented as separate devices rather than as a single device. This configuration makes it possible to improve the transfer efficiency of user packets without complicating the control associated with UE movement. Furthermore, the PGW-C can also be implemented as a single device, the same as the 5GC SMF. In this case, the 5GC UPF can be implemented as a single device, the same as the SGW-U + PGW-U.
[0027] Second Embodiment Next, the second embodiment will be described focusing on the differences from the first embodiment. In the first embodiment, all of the individual SGW-Us and individual PGW-Us in the core network are replaced with SGW-U+PGW-Us, and therefore, the SGW-U+PGW-Us only directly accommodate the BS. However, since there are many individual SGW-Us, there may be a period in which the core network is operated in a situation where individual SGW-Us and SGW-U+PGW-Us are mixed. This embodiment relates to the control of a core network in which individual SGW-Us and SGW-U+PGW-Us are mixed.
[0028] Fig. 8 shows a configuration example of a mobile communication network according to this embodiment. In Fig. 8, SGW-U+PGW-U may connect to a DN and accommodate one or more BSs including BS#1 in area #1. In addition, SGW-U+PGW-U may accommodate an individual SGW-U in area #1. SGW-U#1 is an individual SGW-U and may accommodate one or more BSs including BS#1 in area #1. Note that, although only one SGW-U#1 is shown as an individual SGW-U in Fig. 8, multiple individual SGW-Us may exist in area #1.
[0029] MME#1 and SGW-C#1 are responsible for controlling UEs connected to one or more BSs including BS#1 in area#1. SGW-C#1 can control individual SGW-Us and the SGW-U function in SGW-U+PGW-U. SGW-C#1 is configured to transmit and receive control signaling to and from PGW-C, and to transmit and receive control signaling based on PFCP to and from individual SGW-Us. PGW-C is configured to transmit and receive control signaling to and from SGW-C#1, and to transmit and receive control signaling based on PFCP to and from SGW-U+PGW-U. PGW-C controls a device implementing SGW-U+PGW-U.
[0030] In this embodiment, the determination information shown in Fig. 9(A) is stored in the SGW-C#1. Alternatively, in this embodiment, the determination information shown in Fig. 9(A) is stored in a node having a database function in the core network, and the SGW-C#1 is configured to access the node having the database function and refer to the determination information shown in Fig. 9(A). The determination information is information for the SGW-C to determine whether to set a bearer that goes through an individual SGW-U or to set a bearer that does not go through an individual SGW-U. Note that when going through an individual SGW-U, the individual SGW-U is accommodated in the PGW-U function in the SGW-U+PGW-U.
[0031] The "accommodation" in the determination information shown in Fig. 9(A) being "SGW-U+PGW-U" indicates that a bearer that does not go through an individual SGW-U is set, that is, the SGW-U function in SGW-U+PGW-U accommodates the BS. On the other hand, the "accommodation" in the determination information shown in Fig. 9(A) being "SGW-U" indicates that a bearer that goes through an individual SGW-U is set, that is, the individual SGW-U accommodates the BS, and the PGW-U function in SGW-U+PGW-U accommodates the individual SGW-U.
[0032] According to Fig. 9(A), when the access point name (APN) is APN#1, a bearer that passes through an individual SGW-U is set for the UE. Similarly, when the APN is APN#2 or APN#3, a bearer that passes through an individual SGW-U is set for the UE. Also, when the APN is other than APN#1 to APN#3, a bearer that does not pass through an individual SGW-U is set for the UE. Note that the APN is information for determining the termination point on the DN side of the bearer, that is, information for identifying the PGW-U that terminates the bearer.
[0033] Fig. 10 is a sequence diagram showing an example of a bearer setting process for UE#1. In Fig. 10, it is assumed that APN#4 is set in UE#1 as the APN to be used when connecting to a DN. Note that the same step numbers are given to the process steps in the sequence shown in Fig. 10 that are similar to those in the sequence of the first embodiment shown in Fig. 6, and only the extent necessary for understanding the embodiment will be described.
[0034] At S10, MME#1 transmits a session creation request to SGW-C#1. The session creation request at S10 corresponds to a setting request message requesting the setting of a new bearer for UE#1. The session creation request includes information indicating APN#4 transmitted by UE#1 to MME#1. At S40, SGW-C#1 determines to set a bearer for UE#1 that does not pass through an individual SGW-U based on the determination information shown in FIG. 9(A). Therefore, the subsequent sequence is similar to that of the first embodiment shown in FIG. 6. Reference numeral 1 in FIG. 8 indicates a path between BS1#1 and SGW-U+PGW-U among the bearers set in the sequence of FIG. 10. Since the APN indicates the PGW-U that terminates the bearer, when multiple SGW-U+PGW-U are operated in the core network, which SGW-U+PGW-U the bearer is set to is determined based on the APN.
[0035] Fig. 11 is a sequence diagram showing another example of the bearer setting process for UE#1. In Fig. 11, it is assumed that APN#1 is set in UE#1 as the APN to be used when connecting to DN. Note that the same step numbers are given to the process steps in the sequence shown in Fig. 11 that are similar to the sequence of the first embodiment shown in Fig. 6, and the description will be given only to the extent necessary for understanding the embodiment.
[0036] At S10, MME#1 transmits a session creation request to SGW-C#1. The session creation request at S10 corresponds to a setting request message requesting the setting of a new bearer for UE#1. The session creation request includes information indicating APN#1 transmitted by UE#1 to MME#1. At S40, SGW-C#1 determines to set a bearer for UE#1 via an individual SGW-U based on the determination information shown in FIG. 9(A). When there are multiple individual SGW-Us in area#1, SGW-C#1 selects an SGW-U through which the bearer for UE#1 will be routed from the multiple individual SGW-Us. This selection may be based on, for example, the identifier of UE#1. Alternatively, this selection may be based on the processing load of the individual SGW-U, for example, the number of bearers that the individual SGW-U is processing at that time. In FIG. 11, it is assumed that SGW-C#1 selects SGW-U#1.
[0037] In S50, SGW-C#1 transmits a PFCP session establishment request to SGW-U#1. The PFCP session establishment request includes information for SGW-U#1 to establish an S5 / S8 bearer with the PGW-U function of SGW-U+PGW-U. Upon receiving a session creation request from SGW-C#1, SGW-U#1 transmits a PFCP session establishment response to SGW-C#1 in S51, which is a response to the session establishment request received from SGW-C#1.
[0038] In S52, the SGW-C#1 transmits a session creation request to the PGW-C. This session creation request includes information for establishing an S5 / S8 bearer with the SGW-U#1. Upon receiving the session creation request from the SGW-C#1, the PGW-C transmits a PFCP session establishment request to the SGW-U+PGW-U in S53, and receives a PFCP session establishment response from the SGW-U+PGW-U in S54. This PFCP session establishment request includes information for establishing a bearer with the SGW-U#1. Upon receiving the PFCP session establishment response, the PGW-C transmits a session creation response to the SGW-C#1 in S55, and the SGW-C#1 transmits the session creation response to the MME#1 in S56. Thereafter, the MME#1 transmits and receives control signaling to the BS#1 and the UE#1 to perform processing for the wireless section side of the bearer.
[0039] When the processing for the wireless section side of the bearer is completed, MME#1 transmits a bearer modification request to SGW-C#1 in S57 to notify the processing result for the wireless section side. In response to the bearer modification request from MME#1 in S58, SGW-C#1 transmits a PFCP session modification request to SGW-U#1 to perform processing to reflect the processing result for the wireless section side in SGW-U#1. In S59, SGW-U#1 transmits a PFCP session modification response to SGW-C#1 as a response to the PFCP session modification request. Upon receiving the PFCP session modification response, SGW-C#1 transmits a bearer modification response to MME#1 in S60. As a result, a bearer is established between UE#1 and the PGW-U function of SGW-U+PGW-U via SGW-U#1 and BS#1. Reference numeral 2 in FIG. 8 indicates a path between BS1#1 and SGW-U+PGW-U of the bearer established in the sequence in FIG.
[0040] The determination information in FIG. 9(A) indicates whether or not to set a bearer via an individual SGW-U in association with the APN, but does not indicate which SGW-U to pass through. Therefore, when there are multiple individual SGW-Us in the area, the SGW-C#1 selects an individual SGW-U to pass the bearer through. However, as shown in FIG. 9(B), the determination information may be configured to indicate an individual SGW-U to pass the bearer through. According to the determination information shown in FIG. 9(B), when the APN is APN#1, the bearer is set through SGW-U#1, and when the APN is APN#2, the bearer is set through SGW-U#2.
[0041] In this embodiment, the SGW-C determines whether or not to set a bearer that passes through an individual SGW-U based on the APN. However, the SGW-C may be configured to determine whether or not to set a bearer that passes through an individual SGW-U based on other information included in a session creation request transmitted from the MME to the SGW-C.
[0042] The same applies to handover across MME areas, that is, handover involving a change of MME, and the SGW-C determines the path of the bearer based on the APN included in the session creation request from the MME. Explaining the sequence of FIG. 7, when the SGW-C#2 receives a session creation request from the MME#2 in S30, it determines the path of the bearer based on the APN included in the session creation request. Even if a bearer that goes through an individual SGW-U is set in area #1, a bearer that does not go through an individual SGW-U can be set in area #2. That is, the determination information used by the SGW-C#1 indicates that a bearer that goes through an individual SGW-U is set in the case of APN#1, but the determination information used by the SGW-C#2 can indicate that a bearer that does not go through an individual SGW-U is set in the case of APN#1. The same applies vice versa, and even if a bearer that does not go through an individual SGW-U is set in area #1, a bearer that goes through an individual SGW-U can be set in area #2.
[0043] When setting a bearer that does not go through an individual SGW-U, the process from S31 onwards in Fig. 7 is executed. When going through an individual SGW-U, the SGW-C#1 sets up a bearer that goes through an individual SGW-U by transmitting and receiving control signalling to each of the individual SGW-U and PGW-C through which the bearer goes.
[0044] Next, a handover that does not cross areas, i.e., when the MME is not changed, will be described. Specifically, a process will be described when UE#1 connected to BS#1 as shown in Fig. 12 is handed over to BS#3 as shown in Fig. 13. The sequence in Fig. 14 is started when the process of the wireless section is completed and the target BS#3 transmits a switching request to MME#1.
[0045] In S70, MME#1 transmits a bearer modification request to SGW-C#1. The bearer modification request in S70 corresponds to a change request message that requests a change in the path of an existing bearer that connects UE#1 and SGW-U+PGW-U due to handover of UE#1. The bearer modification request does not include APN information. Therefore, in the case of a handover that does not involve a change in MME, SGW-C is configured to determine whether or not to pass through an individual SGW-U using the determination information shown in FIG. 9(C). The determination information in FIG. 9(C) indicates the relationship between the identifier (bearer ID) of the EPS bearer included in the bearer modification request and whether or not to pass through an individual SGW-U. According to FIG. 9(C), when the bearer ID is B_ID#1 or B_ID#2, a bearer that passes through an individual SGW-U is set. On the other hand, when the bearer ID is different from B_ID#1 or B_ID#2, a bearer that does not pass through an individual SGW-U is set.
[0046] In Fig. 14, since the bearer ID is B_ID#3, the SGW-C#1 determines in S71 to set a bearer that does not go through an individual SGW-U. Therefore, the SGW-C#1 performs the same process as S31 to S34 in Fig. 7. When the SGW-C#1 receives a bearer modification response from the PGW-C in S34, it transmits a bearer modification response, which is a response to the bearer modification request received in S70, to the MME#1 in S72. Note that, when the bearer ID is B_ID#1 or B_ID#2, that is, when the bearer is to go through an individual SGW-U, the SGW-C#1 sets a bearer that goes through an individual SGW-U by transmitting and receiving control signaling to each of the individual SGW-U and PGW-C through which the bearer is to go through. Incidentally, if the individual SGW-U is the same before and after the handover, that is, if the S5 / S8 bearer is the same before and after the handover, the SGW-C#1 transmits and receives control signaling only to the individual SGW-U.
[0047] In addition, in the case of a handover that does not involve a change in MME, the configuration before the handover can be inherited. In other words, if a bearer went through an individual SGW-U before the handover, the bearer after the handover can also go through the individual SGW-U, and if a bearer did not go through an individual SGW-U before the handover, the bearer after the handover can also not go through an individual SGW-U.
[0048] As described above, the request message that the MME transmits to the SGW-C to request the setting of a bearer includes information for the SGW-C to determine whether or not to set a bearer that passes through an individual SGW-U. The request message is a message that requests the setting of a new bearer. The information for the SGW-C to determine whether or not to set a bearer that passes through an individual SGW-U may be, for example, an APN. When the SGW-C determines that a bearer that passes through an individual SGW-U is to be set, the SGW-C executes a first process of transmitting and receiving control signaling with both the PGW-C and the individual SGW-U. The first process is the process from S50 onwards in FIG. 11. On the other hand, when the SGW-C determines that a bearer that does not pass through an individual SGW-U is to be set, the SGW-C executes a second process of transmitting and receiving control signaling only with the PGW-C. The second process is the process from S11 onwards in FIG. 10.
[0049] Also, the change request message that the MME transmits to the SGW-C in association with the handover, requesting a change in the path of the bearer, includes information for the SGW-C to determine whether or not to set a bearer that passes through an individual SGW-U. The information for the SGW-C to determine whether or not to set a bearer that passes through an individual SGW-U during a handover involving a change in the MME may be, for example, an APN. On the other hand, the information for the SGW-C to determine whether or not to set a bearer that passes through an individual SGW-U during a handover that does not involve a change in the MME may be, for example, a bearer identifier. When the SGW-C determines that a bearer that passes through an individual SGW-U is to be set, the SGW-C transmits and receives control signaling to both the PGW-C and the individual SGW-U. Note that, when the individual SGW-U is the same before and after the handover, the SGW-C transmits and receives control signaling only to the individual SGW-U. When the SGW-C determines that a bearer that does not pass through an individual SGW-U is to be set, the SGW-C transmits and receives control signaling only to the PGW-C.
[0050] This configuration makes it possible to operate and control the core network in a situation where SGW-U+PGW-U and individual SGW-Us are mixed. In particular, in a situation where SGW-U+PGW-U and individual SGW-Us are mixed, it is possible to distribute the load between individual SGW-Us and the SGW-U functions within the SGW-U+PGW-U.
[0051] The SGW-C, PGW-C, SGW-U, and SGW-U+PGW-U according to the present disclosure may be realized by a computer program that, when executed by one or more processors of an apparatus having one or more processors, causes the apparatus to function as the SGW-C, PGW-C, SGW-U, and SGW-U+PGW-U described in the above embodiments. The computer program may include program instructions executable by one or more processors. The computer program may be stored in a computer-readable non-transitory storage medium or distributed via a network.
[0052] With the above configuration, it is possible to operate the core network in a situation where devices that implement both the first and second functions are mixed with devices that implement the first function but do not implement the second function. Therefore, it is possible to contribute to Goal 9 of the Sustainable Development Goals (SDGs) led by the United Nations, which is to "build resilient infrastructure, promote sustainable industrialization and foster innovation."
[0053] The invention is not limited to the above-described embodiment, and various modifications and variations are possible within the scope of the gist of the invention.
Claims
1. A first device including a first function for accommodating a base station and a second function for connecting to an external data network; a second device including the first function; A first control device that controls the first device; a management device for receiving control signaling from a user equipment; A control device for controlling the second device in a mobile communication network comprising: A receiving means for receiving from the management device a request message requesting the setting of a bearer connecting a user device and the first device; A processing means for executing one of a first process for setting the bearer via the second device and a second process for setting the bearer not via the second device based on information included in the request message; The control device is provided with:
2. The control device according to claim 1, wherein the processing means executes either the first process or the second process based on determination information for determining whether or not to set up the bearer via the second device from the information included in the request message.
3. The control device according to claim 1 , wherein, when executing the first process, the processing means selects, from a plurality of the second devices, a second device through which the bearer is to be routed, based on an identifier of the user device.
4. The control device according to claim 1 , wherein, when executing the first process, the processing means selects a second device through which the bearer is to be routed from a plurality of second devices based on a processing load of each of the plurality of second devices.
5. When performing the first process, the processing means transmits and receives control signaling to and from each of the first control device and the second device; The control device according to claim 1 , wherein, when performing the second process, the processing means transmits and receives control signaling to and from the first control device but does not transmit and receive control signaling to and from the second device.
6. The control device described in claim 1, wherein, when performing the second processing, the processing means notifies the first control device of the bearer setting, and when receiving a response to the notification from the first control device, creates a response to the request message based on the information contained in the response.
7. The control device according to any one of claims 1 to 6, wherein the first function is a user plane function (SGW-U) of a serving gateway (SGW), the second function is a user plane function (PGW-U) of a packet data network gateway (PGW), the first control device is a device that implements a control plane function (PGW-C) of a PGW, and the control device is a device that implements a control plane function (SGW-C) of an SGW.
8. The control device according to claim 1 , wherein the information included in the request message includes information for determining the second function that terminates the bearer.
9. The control device according to claim 1 , wherein the information included in the request message includes information indicating an access point name (APN).
10. A control device as described in any one of claims 1 to 6, wherein when the receiving means receives from the management device a change request message requesting a change in the path of a bearer associated with a handover of a user device, the processing means determines whether or not to pass through the second device on the path of the changed bearer based on information contained in the change request message.
11. The control device according to claim 10 , wherein the information included in the change request message includes information indicating an access point name (APN) or information indicating an identifier of the bearer.
12. A control device described in any one of claims 1 to 6, wherein the management device is a device that implements a mobility management function (MME).
13. A computer program which, when executed on one or more processors of an apparatus, causes said apparatus to function as a control device according to any one of claims 1 to 6.
14. 1. A mobile communications network, comprising: A first device including a first function for accommodating a base station and a second function for connecting to an external data network; a second device including the first function; A first control device that controls the first device; A second control device that controls the second device; a management device for receiving control signaling from a user equipment; Equipped with A mobile communications network, wherein when the second control device receives a request message from the management device requesting the setting up of a bearer connecting a user device and the first device, based on information contained in the request message, the second control device executes either a first process for setting up the bearer that passes through the second device or a second process for setting up the bearer that does not pass through the second device.
Citation Information
Patent Citations
Method and apparatus for use in communication systems comprising serving gateway control plane functionality
EP4093087A1
Optimized selection of user plane node in cups based 5g NSA or EPC networks during UE relocation
US20220095420A1
Communication system and communication method
WO2017122531A1
Transmission device selection method, gateway selection method, and communication system
WO2017141810A1
Tracking area identity list updating method
WO2017169281A1
