KR20190090904A - Method and system for allocating ip address in distributed network - Google Patents

Abstract

Provided are an IP address allocation apparatus and an IP address allocation method, the IP address allocation apparatus comprising: an access and mobility management function (AMF) entity for receiving a registration request of a UE through one of base stations of a plurality of access networks; a session management function (SMF) entity for receiving an IP address assignment request sent from AMF after a registration request and assigning an IP address to the UE; and a user plane function (UPF) entity for providing a service based on the IP address assigned to the UE.

Description

METHOD AND SYSTEM FOR ALLOCATING IP ADDRESS IN DISTRIBUTED NETWORK}

The present disclosure relates to a method and system for allocating IP addresses in a distributed network.

A software defined network (SDN) may define a control plane (CP) and a user plane (UP), respectively, to deliver communication traffic to the mobile terminal. The CP is in charge of the control function of the network, and the UP routes communication traffic according to the control of the CP. In this case, the UP performs a data transfer function based on hardware, and the control of the switch is performed based on software in the CP so that the network can be efficiently managed and operated.

Recently, in order to reduce the load on the network as the traffic of the user continuously increases, a technique for processing the traffic of the user at the edge (Edge) close to the point where the user is connected has been studied. Such techniques may appear in the form of distributed networks. In the conventional LTE network, a part of the CP function is included in the UP. For example, a packet data network (PDN) gateway (GW) (PGW), which is an entity that allocates and releases an Internet Protocol (IP) address, has a function of CP and UP. Included. In the conventional LTE network, since the IP address is centrally allocated by the P-GW in charge of IP routing, the path of communication traffic is centralized, which is not suitable for processing large traffic.

One embodiment provides a system for assigning an IP address to a UE in a distributed network.

Another embodiment provides a method of assigning an IP address to a UE in a distributed network.

According to an embodiment, a system for allocating an IP address to a user equipment (UE) in a distributed network is provided. The IP address allocation system is an access and mobility management function (AMF) entity that receives a registration request of a UE through one of base stations of a plurality of access networks, and is transmitted from an AMF entity after a registration request. A session management function (SMF) entity that receives an IP address assignment request, assigns an IP address to the UE, and a user plane function (UPF) that provides services based on the IP address assigned to the UE. Entity, the SMF entity controls a plurality of UPF entities, the AMF entity and the SMF entity belong to the control plane of the distributed network, and the UPF entity belong to the user plane of the distributed network.

In the IP address assignment system, the SMF entity may be located at a point geographically close to the UE.

In the IP address allocation system, the UPF entity may correspond to a converged gateway (CGW).

In the IP address allocation system, the UPF entity may provide a service to the UE through at least one of a base station of a 5G network, a base station of a WiFi network, or a switch of a fixed network.

In the IP address allocation system, the SMF entity may manage IP addresses that the UPF entity can provide to the UE in the form of a list.

In the IP address allocation system, the SMF entity may manage an IP address using NetworkID and Netmask.

In the IP address assignment system, when the SMF entity allocates an IP address to the UE, the SMF entity may also perform a tunnel setup or a flow setup to be provided to the UE.

In the IP address allocation system, when the SMF entity allocates an IP address to the UE, the SMF entity determines a UPF entity to provide a service to the UE from among a plurality of UPF entities, and within a range of IP addresses that the determined UPF entity can provide. You can assign an IP address.

In the IP address assignment system, when the SMF entity receives the termination message for the session established from the AMF entity to the UE, the SMF entity may retrieve the allocated IP address.

In the IP address assignment system, the SMF entity uses an IP address pool to manage IP addresses, and the IP address pool includes an IP address assigned by the SMF entity or is associated with an SMF entity with an IP address assigned by the SMF entity. It may also include IP addresses assigned by other SMF entities.

In the IP address assignment system, the SMF entity may return the pre-assigned IP address to the UE when it is determined to continue to use the pre-assigned IP address to the UE that sent the registration request.

According to another embodiment, a method for allocating an Internet Protocol (IP) address of a session management function (SMF) entity of a distributed network is provided. The method for allocating an IP address may include: from an access and mobility management function (AMF) entity that receives a registration request of a user equipment (UE) from one base station of a plurality of access networks, Receiving an address assignment request, assigning an IP address to the UE, delivering the assigned IP address through the AMF entity to the UE through a session response, and providing a service based on the IP address assigned to the UE. Controlling at least one User Plane Function (UPF) entity so that the SMF entity belongs to the control plane of the distributed network along with the AMF entity, and the UPF entity belongs to the user plane of the distributed network.

In the IP address allocation method, the SMF entity may be located at a point geographically close to the UE.

The IP address allocation method may further include managing IP addresses that the UPF entity can provide to the UE in the form of a list.

The IP address allocation method may further include managing an IP address using a NetworkID and a Netmask.

In the IP address allocation method, allocating an IP address to the UE may include performing a tunnel setup or a flow setup together with the UE.

In the IP address allocation method, allocating an IP address for a UE includes determining an UPF entity to provide a service to the UE from among a plurality of UPF entities, and assigning an IP address within a range of IP addresses that the determined UPF entity can provide. May include assigning.

The IP address allocation method may further include retrieving the allocated IP address when receiving a termination message for the session established to the UE from the AMF entity.

The IP address allocation method further includes managing an IP address using an IP address pool, wherein the IP address pool includes an IP address assigned by an SMF entity or an SMF with an IP address assigned by an SMF entity. It can also include IP addresses assigned by entities and other SMF entities.

Allocating an IP address for the UE in the IP address allocation method may include returning the preallocated IP address to the UE when it is determined to continue using the IP address previously assigned to the UE that sent the registration request. .

IP addresses can be efficiently allocated and managed in a distributed network with separate control and user planes.

1 is a conceptual diagram illustrating the structure of an LTE network.
2 is a conceptual diagram illustrating a traffic path of an LTE network.
3 is a conceptual diagram illustrating a distributed network for supporting various access technologies according to an embodiment.
4 is a conceptual diagram illustrating a relationship between a control plane and a data plane of an integrated core network of a distributed network according to an embodiment.
5 illustrates a relationship between components of a 3GPP network to which an integrated core network is applied according to an embodiment.
FIG. 6 is a diagram illustrating another aspect of a relationship between components of a 3GPP network to which an integrated core network is applied according to an embodiment.
7A and 7B are flowcharts illustrating a method for allocating an IP address to a user by an integrated core network according to an embodiment.
8 is a conceptual diagram illustrating an IP address storage method of an SMF according to an embodiment.
9 is a conceptual diagram illustrating a method of managing an assigned IP address and a category of IP addresses that can be used in the UPF according to an embodiment.
10 is a flowchart illustrating a method of allocating an IP address according to an embodiment.
11 is a flowchart illustrating a method of retrieving an allocated IP address according to an embodiment.
12 is a flowchart illustrating a method for managing a path traveled between different UPFs by a UE according to an embodiment.
13 is a block diagram illustrating a wireless communication system according to an embodiment.
14 is a block diagram illustrating a functional entity of a wireless communication system according to one embodiment.

DETAILED DESCRIPTION Hereinafter, exemplary embodiments of the present disclosure will be described in detail with reference to the accompanying drawings so that those skilled in the art may easily implement the present disclosure. As those skilled in the art would realize, the described embodiments may be modified in various different ways, all without departing from the spirit or scope of the present invention. In the drawings, parts irrelevant to the description are omitted for simplicity of explanation, and like reference numerals designate like parts throughout the specification.

Throughout the specification, a terminal includes a mobile station (MS), a mobile terminal (MT), an advanced mobile station (AMS), a high reliability mobile station (HR-MS). ), Subscriber station (SS), portable subscriber station (PSS), access terminal (AT), user equipment (user equipment (UE)), machine type communication device ( MTC device) and the like, and may include all or some functions of MT, MS, AMS, HR-MS, SS, PSS, AT, UE, and the like.

In addition, a base station (BS) may be an advanced base station (ABS), a high reliability base station (HR-BS), a node B (node B), an advanced node B (evolved node B, eNodeB), access point (AP), radio access station (RAS), base transceiver station (BTS), mobile multihop relay (MMR) -BS, relay serving as a base station station (RS), relay node (RN) serving as base station, advanced relay station (ARS) serving as base station, high reliability relay station (HR) serving as base station -RS), small base station (femto BS, home node B (HNB), home eNodeB (HeNB), pico base station (pico BS), macro base station (macro BS), micro base station (micro BS) ), Etc., and all or one of ABS, Node B, eNodeB, AP, RAS, BTS, MMR-BS, RS, RN, ARS, HR-RS, small base station, and the like. It may also include negative functions.

1 is a conceptual diagram illustrating the structure of an LTE network, and FIG. 2 is a conceptual diagram illustrating a traffic path of an LTE network.

Referring to FIG. 1, a user equipment (UE) is connected to an evolved NodeB (eNB) through an air interface, and a UE is connected to a core network through an eNB. The serving gateway (SGW) performs an anchor function when the UE performs an inter-eNB handover, and the PGW performs an anchor function when the UE performs an inter-SGW handover. The PGW then assigns an IP address to the UE. The Mobility Management Entity (MME) manages the mobility of the UE and manages the Evolved Packet System (EPS) bearer.

Referring to FIG. 2, since the PGW manages an IP address assigned to the UE, all traffic between UE1 and the UEs (UE1-UE2, UE1-UE3, and UE1-UE4) must always go through the PGW. This is because the PGW is an entity that assigns IP and is an entity that is in charge of IP routing of user data. In the network of FIG. 2, since traffic is transmitted from the eNB to the PGW through IP tunneling, IP routing of user data is performed by the PGW.

3 is a conceptual diagram illustrating a distributed network for supporting various connection technologies according to an embodiment, and FIG. 4 is a conceptual diagram illustrating a relationship between a control plane and a data plane of an integrated core network of a distributed network according to an embodiment.

In FIG. 3, the integrated core network includes a converged gateway (CGW), a universal control entity (UCE), an edge UCE (eUCE), and the like.

The CGW is an UP entity that performs IP routing of data. IP tunneling is performed on user data received from base stations (5G base station (BS), WiFi BS, fixed switch (SW), etc.) of various access networks to which the UE is connected. UCE is in charge of the control in the integrated core network, CGW is in charge of data processing in the integrated core network, and provides the access service to the data network (DN) of the UE.

UCE supports mobility between UEs' eUCEs. In FIG. 3, the integrated core network according to an embodiment may support connection technologies such as 5G, WiFi, and fixed. 5G is an example of a mobile radio access technology, WiFi is an example of an IEEE 802.11 series wireless access technology, and Fixed is an example of a wired IP access technology. Therefore, 5G BS is a base station of 5G mobile radio access technology, WiFi BS is a base station of WiFi network, FixedSW is an L3 switch of wired IP access technology. The eUCE is located at the boundary of the distributed network, and when the UE accesses the integrated core network, the UE can access the eUCE located close to the UE among a plurality of geographically dispersed eUCEs.

In FIG. 3, the 5G BS connected to the UE is connected to the integrated core network through the CGW, but the 5G BS, the WiFi BS, and the FixedSW may be directly connected to the eUCE without passing through the CGW.

The UE is a terminal that supports one or more of the various access technologies (5G, WiFi, or Fixed) shown in FIG. 3, and a device corresponding to each access technology is individually implemented in the UE, or various access technologies are used. An integrated form of device to support may be included.

Referring to FIG. 4, the eUCE included in the control plane is an entity in charge of controlling the network, and the CGW included in the data plane is an entity processing data. The eUCE and the CGW may be in a 1: 1 relationship, a 1: n relationship, or an n: m relationship.

FIG. 5 is a diagram illustrating a relationship between components of a 3GPP network to which an integrated core network is applied according to an embodiment, and FIG. 6 is a diagram illustrating another perspective of relationships between components of a 3GPP network to which an integrated core network is applied according to an embodiment. Drawing.

Referring to FIG. 5, an Access and Mobility Management Function (AMF) entity (hereinafter referred to as 'AMF') and a Session Management Function (SMF) entity (hereinafter referred to as 'SMF') included in the control plane 'Corresponds to eUCE, and a User Plane Function (UPF) entity (hereinafter referred to as' UPF') included in the data plane corresponds to the CGW. SMF assigns IP addresses to users, manages IP addresses, and controls UPF. According to an embodiment, a method for managing an IP address by the SMF is provided so that the UPF can smoothly provide a user with an access service to a data network based on an IP address assigned to the user. The UPF may provide a service to the UE through at least one of a base station of a 5G network, a base station of a WiFi network, or a switch of a fixed network.

Referring to FIG. 6, a UE assigned an IP address by SMF1 is provided with a service through UPF1 and then connected to UPF2. At this time, since the UE moves from UPF1 to UPF2, a tunnel is formed between UPF1 and UPF2. Although the IP address of the UE is generated by SMF1, the packet to be delivered to the UE in the integrated core network is transmitted by UPF1 to UPF2. Instructions for packet delivery are sent by SMF1 or SMF2 to UPF1 and UPF2. SMF1 and SMF2 may be the same SMF.

7A and 7B are flowcharts illustrating a method for allocating an IP address to a user by an integrated core network according to an embodiment.

Referring to FIG. 7A, the AMF receives a registration request of a UE through one of base stations of a plurality of access networks (S710) and transmits a session request to the SMF (S720). That is, according to FIG. 7A, the AMF requests a session from the SMF by a registration request of the UE. A session request sent by the AMF to the SMF may be considered an assignment request for an IP address. AMF and SMF correspond to eUCE, AMF and SMF correspond to the same eUCE (i.e. AMF and SMF are included in one eUCE) or each correspond to a different eUCE (i.e. AMF and SMF are each included in different eUCE) Can be. The SMF allocates an IP address to the UE (S730) and instructs the UPF of a service based on the allocated IP address (data plane (DP) configuration instruction) (S740). The SMF may select one of the plurality of UPFs in consideration of the data network requested by the UE, the capacity of the UPF, the location of the network slice to which the UE is connected, and the like. The SMF transmits the IP address assigned to the UE after the DP setup ACK to the UE through the AMF (Session Response) (S750). Alternatively, the SMF may send a session response to the AMF before sending a DP configuration indication to the UPF.

Referring to FIG. 7B, after the registration procedure between the UE and the AMF is completed, the UE requests a session from the AMF (S711). According to FIG. 7B, once the registration procedure is completed, the UE may perform the session request separately from the registration procedure. Thereafter, the AMF delivers the session request of the UE to the SMF (S721). The SMF allocates an IP address for the UE (S731) and instructs the UPF a service based on the assigned IP address (S741). The SMF transmits the IP address allocated to the UE after the DP setup ACK to the UE through the AMF (S751). Alternatively, the SMF may send a session response to the AMF before sending a DP configuration indication to the UPF.

8 is a conceptual diagram illustrating an IP address storage method of an SMF according to an embodiment.

According to one embodiment, the relationship between SMF and UPF is one of 1: 1, 1: n, and n: m. The UE may move to another UPF while receiving a service by one UPF (corresponding to the CGW). The UPF connected to the UE before the movement is called UPF1, and the connected UPF after the movement is called the UPF2. SMF1 controls UPF1 and SMF2 controls UPF2. SMF1 and SMF2 may be the same SMF. In FIG. 8, SMF1 assigns an IP address to a UE and a UE assigned an IP address is provided with service from UPF1, and then SMF3 assigns IP3, which is an IP address, to the UE after the UE moves to UPF2, and an IP address is assigned. A scenario is assumed where the UE is served from UPF3.

FIG. 8A illustrates a system in which each SMF independently manages its assigned IP address, and FIGS. 8B and 8C illustrate a system in which a plurality of SMFs manage IP addresses together. In FIG. 8C, an IP address manager is located between the plurality of SMFs and the IP address pool. In FIG. 8A, SMF1 may allocate IP1, and IP1 may be used when providing services of UPF1 and UPF2. In addition, SMF3 can allocate IP3, and IP3 can be used to provide services of UPF3. In FIGS. 8B and 8C, IP1 and IP3 which can be allocated by SMF1 and SMF3 are stored in one IP address pool. That is, different SMFs can share a pool of IP addresses for managing IP addresses.

Various information used in the integrated core network according to an embodiment may be managed together with the IP address of FIG. 8. For example, context information about a user connection managed by the AMF (for example, information on which access network the terminal is accessing to a base station, and user ID (ID) (international mobile subscriber ID) User-specific information, such as the International Mobile Subscriber Identity (IMSI) or Globally Unique Temporary Identifier (GUTI), and the user's session information (tunnel information, flow information, QoS information, etc.) along with the IP address pool. Information contained in each functional element in the integrated core network (information on which IP address or port the terminal can find the required functional element, and the ability of each functional element to provide) Information required for network operations, such as capacities, etc., can be managed along with the IP address pool In the IP address pool, a list of IP addresses that can be assigned by the UPF is listed. Each IP address in the list can be flagged, or the category of IP addresses that the UPF can provide in the IP address pool is defined by its NetworkID and Netmask. The IP address, which has been represented and already assigned, can be displayed in the assignment list.

9 is a conceptual diagram illustrating a method of managing an assigned IP address and a category of IP addresses that can be used in the UPF according to an embodiment.

In (a) of FIG. 9, IP addresses that can be provided by the UPF, which are managed by the SMF, are managed in a list form. All IP addresses that can be provided by UPF are maintained in a list, and already assigned and unassigned IP addresses are flagged. In (a), IP1 and IP3 are already assigned and IP2 and IPn are not. In this case, as described above, to which UE the corresponding IP address is allocated (relationship between the IP address and the UE) may be managed together.

In FIG. 9B, the SMF manages IP addresses of the plurality of UPFs in the manner of (a).

In FIG. 9C, an IP address that can be provided by the UPF, which is managed by the SMF, is managed by a NetworkID and a Netmask. That is, the IP address prefix of the IP address that can be assigned by the UPF represents NetworkID, and the valid bits of the prefix may be represented by a netmask. The remaining portion of the IP address except for the prefix is allocated to the UE. The SMF may generate an IP address using NetworkID and Netmask and assign the generated IP address to the UE. Already assigned IP addresses are managed as separate allocation lists, so IP addresses are not duplicated. In (b), IP1 and IP3 are assigned.

In FIG. 9D, the SMF manages IP addresses of the plurality of UPFs in the manner of (b).

In the IP address management method shown in FIG. 9, when a user terminates the session and the assigned IP address is also revoked, a flag in the IP address pool may be changed so that the revoked IP address can be used again. For example, in FIG. 9A, the flag is changed, and in FIG. 9B, the revoked IP address is deleted from the list.

10 is a flowchart illustrating a method of allocating an IP address according to an embodiment.

Referring to FIG. 10, the SMF receives a session allocation request of a UE from an AMF (S1010) and verifies the authority of a session requested by a user (S1020). The session allocation request from the UE is considered to be the same as the IP allocation request. For example, if there is no need to assign additional IPs during the session request (i.e. when the SMF decides to continue to use the IP addresses already assigned to the UE), the IP addresses already assigned to the user are returned. If the user has not subscribed to the IP data service, the SMF fails the authorization verification, and the SMF informs the AMF of the IP allocation failure without assigning the IP address to the UE. If the bandwidth of the session requested by the user is greater than the bandwidth of the service subscribed to by the user, the SMF may reject the session assignment (or IP address assignment) or allocate as much as the bandwidth of the service subscribed to by the user.

If the SMF succeeds in verifying the authority, the SMF allocates an IP address to the UE (S1030). When allocating an IP address, the SMF may also set up a tunnel or a flow to be provided to the UE. The SMF transmits allocation information of the IP address to the UE (S1040). The allocation information of the IP address includes information of an IP address previously assigned to the UE (when a pre-assigned IP address is still used) or information of a newly allocated IP address (when a new IP address is assigned to the UE). S1040 corresponds to S750 and S751 of FIGS. 7A and 7B. The allocation information of the IP address may be delivered to the UE via the AMF. The allocation information of the IP address is stored in the SMF (S1050). The step of transmitting the allocation information of the IP address of S1040 and storing the allocation information of the IP address of S1050 may be performed regardless of the order shown.

In step S1030, the SMF first determines an UPF to provide a service to the UE in order to allocate an IP address (S1031). Thereafter, the SMF determines an IP address that can be allocated within a range of IP addresses that the determined UPF can provide (S1032).

11 is a flowchart illustrating a method of retrieving an allocated IP address according to an embodiment.

Referring to FIG. 11, when the SMF receives an end message for a session established to the UE from the AMF (S1110), the SMF retrieves an allocated IP address (S1120). The UE informs the UE that the recovery of the IP address is completed (S1130). Completion of retrieval of the IP address may be delivered to the UE via AMF. The notification for notifying the retrieval of the IP address may be delivered through a confirmation message of the session termination. Thereafter, the SMF stores the retrieval information of the IP address (S1140). Storing retrieval information of an IP address means that the assigned IP address is marked in the IP address pool as being available again (ie, assignable). Informing the completion of the recovery of the IP address of S1130 and storing the recovery information of the IP address of S1140 may be performed regardless of the order shown.

12 is a flowchart illustrating a method for managing a path traveled between different UPFs by a UE according to an embodiment.

Referring to FIG. 12, when the SMF receives a path change request directly from the BS or via an AMF, the SMF performs a procedure for changing a path between UPFs (S1210). When a plurality of UPFs are controlled by different SMFs, one SMF may receive a path change request from another SMF. Alternatively, when a plurality of UPFs are controlled by the same SMF, if the SMF recognizes a path change, it may be considered that a path change request has occurred.

When the plurality of UPFs are controlled by different SMFs, the SMF that receives the path change request transmits a path change confirmation message to the SMF that sent the path change request (S1220), and stores the path change information (S1230). Referring to FIG. 8, IP1 allocated to UE by SMF1 in UPF1 may be used in UPF2. That is, FIG. 8 illustrates a scenario in which the UE changes the path to the area of UPF2 while the UE is assigned an IP address by UPF1. If the UE moves to UPF2 after being assigned IP1 by UPF1 and back to UPF3, the route change information is displayed as [SMF1: IP1: UPF1: UPF2: UPF3] (first route change information) or [SMF1: IP1]. UPF1: UPF3] (second path change information). When the packet of the UE is transferred from UPF1 to UPF3 via UPF2, the first path change information is applied, and when the packet is transferred from UPF1 to UPF3 without UPF2, the second path change information is applied.

13 is a block diagram illustrating a wireless communication system according to an embodiment.

Referring to FIG. 13, a wireless communication system according to an embodiment includes a base station 1310 and a terminal 1320.

The base station 1310 includes a processor 1311, a memory 1312, and a radio frequency unit (RF unit) 1313. The memory 1312 may be connected to the processor 1311 to store various information for driving the processor 1311 or at least one program executed by the processor 1311. The wireless communication unit 1313 may be connected to the processor 1311 to transmit and receive wireless signals. The processor 1311 may implement a function, process, or method proposed in the embodiments of the present disclosure. In this case, in the wireless communication system according to the exemplary embodiment of the present disclosure, the air interface protocol layer may be implemented by the processor 1311. The operation of the base station 1310 according to an embodiment may be implemented by the processor 1311.

The terminal 1320 includes a processor 1321, a memory 1322, and a wireless communication unit 1323. The memory 1322 may be connected to the processor 1321 to store various information for driving the processor 1321 or at least one program executed by the processor 1321. The wireless communication unit 1323 may be connected to the processor 1321 to transmit and receive a wireless signal. The processor 1321 may implement the functions, steps, or methods proposed in the embodiments of the present disclosure. In this case, in the wireless communication system according to the exemplary embodiment of the present disclosure, the air interface protocol layer may be implemented by the processor 1321. An operation of the terminal 1320 according to an embodiment may be implemented by the processor 1321.

In an embodiment of the present disclosure, the memory may be located inside or outside the processor, and the memory may be connected to the processor through various known means. The memory is various types of volatile or nonvolatile storage media, and for example, the memory may include read-only memory (ROM) or random access memory (RAM).

14 is a block diagram illustrating a functional entity of a wireless communication system according to one embodiment.

A functional entity (eg, AMF, SMF, UPF, etc.) of a wireless communication system according to one embodiment may be implemented as a computer system, eg, a computer readable medium. Referring to FIG. 14, the computer system 1400 includes a processor 1410, a memory 1430, a user interface input device 1460, a user interface output device 14140, and a storage device that communicate over a bus 1420. It may include at least one of (1480). Computer system 1400 may also include a network interface 1490 coupled to the network. The processor 1410 may be a central processing unit (CPU) or a semiconductor device that executes instructions stored in the memory 1430 or the storage device 1480. The memory 1430 and the storage device 1480 may include various types of volatile or nonvolatile storage media. For example, the memory may include read only memory (ROM) 1431 and random access memory (RAM).

Thus, embodiments of the invention may be implemented as computer-implemented methods or as non-transitory computer readable media having computer executable instructions stored thereon. In one embodiment, when executed by the processor, the computer readable instructions may perform the method according to at least one aspect of the present disclosure. Although the embodiments of the present invention have been described in detail above, the scope of the present invention is not limited thereto, and various modifications and improvements of those skilled in the art using the basic concepts of the present invention defined in the following claims are also provided. It belongs to the scope of rights.

Claims (20)

A system for allocating IP addresses to user equipment (UE) in a distributed network,
An access and mobility management function (AMF) entity for receiving a registration request of the UE through one base station of a plurality of access networks;
A Session Management Function (SMF) entity that receives an IP address assignment request sent from the AMF entity after the registration request and assigns the IP address to the UE;
User Plane Function (UPF) entity providing a service based on the IP address assigned to the UE
Including,
Wherein the SMF entity controls a plurality of UPF entities, the AMF entity and the SMF entity belong to a control plane of the distributed network, and the UPF entity belongs to a user plane of the distributed network. In claim 1,
And the SMF entity is located at a point geographically close to the UE. In claim 1,
And the UPF entity corresponds to a converged gateway (CGW). 4. The method of claim 3,
And the UPF entity provides the service to the UE via at least one of a base station of a 5G network, a base station of a WiFi network, or a switch of a fixed network. In claim 1,
The SMF entity, the IP address allocation system for managing the IP address that the UPF entity can provide to the UE in the form of a list. In claim 1,
And the SMF entity manages the IP address using NetworkID and Netmask. In claim 1,
When the SMF entity assigns the IP address to the UE, the SMF entity performs a setup of a tunnel or a setup of a flow to be provided to the UE. In claim 1,
When the SMF entity allocates the IP address to the UE, the SMF entity determines a UPF entity to provide a service to the UE among a plurality of UPF entities, and the IP within a range of IP addresses that the determined UPF entity can provide. IP address allocation system for assigning addresses. In claim 1,
And when the SMF entity receives an end message for the session established to the UE from the AMF entity, retrieves the assigned IP address. In claim 1,
The SMF entity manages the IP address using an IP address pool, the IP address pool including the IP address assigned by the SMF entity or with the SMF entity along with the IP address assigned by the SMF entity. An IP address assignment system that also includes an IP address assigned by another SMF entity. In claim 1,
And the SMF entity returns the pre-assigned IP address to the UE when it determines to continue using the pre-assigned IP address to the UE that sent the registration request. A method of allocating an Internet Protocol (IP) address of a Session Management Function (SMF) entity in a distributed network.
Receiving an IP address allocation request from an access and mobility management function (AMF) entity that receives a registration request of a user equipment (UE) from one of the base stations of the plurality of access networks; ,
Assigning the IP address to the UE and delivering the assigned IP address to the UE via the AMF entity, and
Controlling at least one user plane function (UPF) entity to provide a service based on an IP address assigned to the UE
Including,
And the SMF entity belongs to the control plane of the distributed network together with the AMF entity, and the UPF entity belongs to the user plane of the distributed network. In claim 12,
And the SMF entity is located at a point geographically close to the UE. In claim 12,
Managing IP addresses that the UPF entity can provide to the UE in the form of a list
IP address assignment method further comprising. In claim 12,
Steps to manage IP address using NetworkID and Netmask
IP address assignment method further comprising. In claim 12,
Allocating the IP address for the UE,
Performing the setting of the tunnel or the setting of the flow to be provided to the UE
Including, IP address allocation method. In claim 12,
Allocating the IP address for the UE,
Determining a UPF entity to provide service to the UE among a plurality of UPF entities, and allocating the IP address within a range of IP addresses that the determined UPF entity can provide
Including, IP address allocation method. In claim 12,
Retrieving an allocated IP address upon receiving a termination message for a session established to the UE from the AMF entity.
IP address assignment method further comprising. In claim 12,
Managing the IP address using an IP address pool
Further comprising:
Wherein the IP address pool includes an IP address assigned by the SMF entity or includes an IP address assigned by an SMF entity different from the SMF entity with an IP address assigned by the SMF entity. . In claim 12,
Allocating the IP address for the UE,
Returning the pre-assigned IP address to the UE when it is determined to continue to use the pre-assigned IP address to the UE that sent the registration request.
IP address allocation method comprising a.

Images