WO2019141120A1

WO2019141120A1 - Pcf paging method, apparatus and device, and storage medium

Info

Publication number: WO2019141120A1
Application number: PCT/CN2019/071029
Authority: WO
Inventors: 黄震宁; 陈旭; 杜晓宁; 尼凌飞; 施南翔; 魏彬
Original assignee: 中国移动通信有限公司研究院; 中国移动通信集团有限公司
Priority date: 2018-01-16
Filing date: 2019-01-09
Publication date: 2019-07-25
Also published as: CN110048951A; CN110048951B

Abstract

Disclosed are a PCF paging method, apparatus and device, and a storage medium. The method comprises: an NEF or NFR receiving an AF sending request, wherein the request carries first IP information of a user and second IP information of the user; and the NEF or NRF querying associated information according to the first IP address information and the second IP address information, to obtain session information for managing the user's packet data network (PDN) sessions, wherein the associated information is used for finding, through the first IP address information of the user and the second IP address information of the user, related session information for providing session management for the user.

Description

PCF addressing method and device, device and storage medium

Cross-reference to related applications

The present application is based on the Chinese Patent Application No. 201810041374.6, filed on Jan. 16, s. .

Technical field

The present application relates to the 3GPP (3rd Generation Partnership Project) technology, and in particular, to a PCF (Policy Control Function) addressing method and device, device, and storage medium.

Background technique

The existing methods are to separately store the session binding relationship of all UEs in the network in a new function (functional entity) or a data storage function entity, or directly to a session-related NF (Network Functionality, which has UE session binding information, Network function) Query to avoid additional separate storage and dynamic maintenance of session binding information. But there are several problems in the following:

Data consistency: A separate database is used to store session binding information, and data consistency must be guaranteed in real time—the session binding relationship of the database is completely consistent with the actual binding relationship in the network. Otherwise, the original IP address will be assigned to other users when the session is released. If it is not updated in time, the IP address in the session binding information will be duplicated, causing an addressing error.

Additional signaling overhead and signaling processing: In addition to query signaling for session binding information, when creating and deleting a session (when an IP address is allocated or released for a PDU session), the database needs to be accessed. Signaling processing overhead. (Proxy (proxy) or redirect (redirect) signaling routing mode does not have additional database access signaling, but requires NF to perform additional processing on N7 and N5 interface signaling, requiring signaling routing NF to have certain signaling processing capabilities. .)

Storage and query of session binding data in a roaming scenario: For the roaming scenario, it is necessary to further analyze whether the session binding information is saved in the home network or visited the network, or both. In the three roaming scenarios, Roaming 5G System architecture-local breakout scenario with AF in the VPLMN, the application function (the application function is located in the visited network), and the Roaming 5G System architecture- Local breakout scenario with AF in the HPLMN (AF is located in the home network), Roaming 5G System architecture-Home routed scenario (AF) SMF (Session Management Function) and PCF may be visiting the network and the home network. Further consideration needs to be given to the routing of storage and queries.

It is only applicable to PCF addressing where the IP address is not duplicated. The IP address pools allocated to different SMFs are planned in advance. If there is no overlap, the SMF that provides session management for the user can be found through the IP address segment to which the IP address belongs. The session binding information on the implementation implements addressing to the PCF. When a technology such as Network Address Translation (NAT) is used to cause the SMF to divide the address pool, the scheme fails.

Summary of the invention

In view of this, the embodiment of the present application provides a PCF addressing method, apparatus, device, and storage medium for solving at least one problem existing in the prior art.

The technical solution of the embodiment of the present application is implemented as follows:

The embodiment of the present application provides a PCF addressing method for a policy control function, where the method includes:

Receiving, by the NEF or the NRF, an AF sending request, where the request carries the first IP information and the second IP address of the user;

The NEF or the NRF queries the association information according to the first IP information and the second IP address to obtain session information for managing a PDN session of the user's packet data network; the association information is used to pass the first IP information of the user and the user. The second IP address finds relevant session information for the user to provide session management.

The embodiment of the present application further provides a PCF addressing device of a policy control function, where the device includes:

The first receiving unit is configured to receive a network open function NEF sending request, where the request carries the first IP information and the second IP address of the user;

The query unit is configured to query the association information according to the first IP information and the second IP address to obtain session information for managing the PDN session of the user's packet data network; wherein the association information is used to pass the first IP information of the user and the user The second IP address finds relevant session information for the user to provide session management.

The embodiment of the present application further provides a network device, including a memory and a processor, where the memory stores a computer program executable on a processor, and when the processor executes the program, the steps in the PCF addressing method are implemented. .

The embodiment of the present application further provides a computer readable storage medium, on which a computer program is stored, and when the computer program is executed by the processor, the steps in the PCF addressing method are implemented.

The PCF addressing method and device, the device, and the storage medium provided by the embodiment of the present application, wherein the NEF or the NRF receives an AF sending request, where the request carries the first IP information and the second IP address of the user; the NEF or NRF And querying the association information according to the first IP information and the second IP address to obtain session information for managing a PDN session of the user's packet data network; the association information is used to find the first IP information of the user and the second IP address of the user. Provides users with session information related to session management; thus, it can solve the problem that the private network IP address cannot be addressed (the SMF cannot be found, and the PCF cannot be found).

DRAWINGS

1A is a schematic diagram of a network architecture of a PCC according to an embodiment of the present application;

FIG. 1B is a schematic diagram of a flow of NEF addressing a PCF through a BSF;

2 is a schematic diagram of a flow of NEF addressing a PCF through a user IP;

FIG. 3 is a schematic flowchart of the SMF querying the user session binding information to address the PCF;

4 is a schematic flowchart of an implementation process of a PCF addressing method according to an embodiment of the present application;

FIG. 5 is a schematic flowchart of an implementation manner of a PCF addressing method according to still another embodiment of the present application;

6 is a schematic structural diagram of a PCF addressing device according to an embodiment of the present application;

FIG. 7 is a schematic diagram of a hardware entity of a network device according to an embodiment of the present application.

Detailed ways

In order to achieve differentiated service capabilities, resource grooming capabilities, and network traffic optimization capabilities, the PCC (Policy and Charging Control) system architecture is introduced into the existing packet network to implement QoS for packet data services. (Quality of Service) control.

As shown in FIG. 1A, the main network elements of the PCC architecture include a Policy and Charging Rules Function (PCRF), a Policy and Charging Enforcement Function (PCEF), and an AF (Application). Function, application function), OCS/OFCS (Online Charging System/Offline Charging System) and SPR (Subscription Profile Repository). Among them, 1) PCRF: has the function of policy control decision and flow-based charging control, and provides PCEF with network control functions for service data flow detection, gating, QoS-based and flow-based charging (except credit control). 2) PCEF: responsible for service data flow detection, policy enforcement, and flow-based charging functions, generally set on the GGSN or P-GW. 3) AF: Mainly implement dynamic policy/accounting control for IP-CAN user plane behavior, and set it on the service platform. 4) SPR: is a logical entity for storing information related to all contracted users or subscriptions, including services allowed by the contracted users. 5) OCS/OFCS: for online/offline billing. The function in this embodiment can be understood as a functional entity, for example, AF represents an application function or an application function entity.

With the development of LTE (Long Term Evolution) LTE services and the introduction of VoLTE (Voice over LTE), DRA (Diameter Routing Agent) devices form a Diameter signaling network. Diameter signaling such as PCC Gx/Rx, IMS (IP Multimedia Subsystem), Cx/Sh/Zh interface, and positioning service SLg/SLh interface.

The DRA addresses the status of the PCRF. At this stage, the LDRA (Lower Diameter Routing Agent) locates the PCRF according to the locally configured number segment and the PCRF correspondence. When the Rx interface message arrives, the DRA performs PCRF addressing according to the code number carried in the message, the public network, and the private network IP address. LDRA is a special name in the deployment. It is actually a type of DRA. In the deployment, the DRA is divided into two levels. The provincial level is called LDRA, and the LDRA is aggregated by the HDRA (Higher Diameter Routing Agent).

5G (5 ^th Generation, fifth generation communication system) session is bound to 4G (4 ^th Generation, fourth-generation communication system) Similarly, achieved by BSF (Binding Support Function, binding support).

In order to better understand the embodiment of the present application, the process of addressing the PCF by the BSF through the BSF, the process of the NEF addressing the PCF through the user IP, and the SMF querying the user session binding information to address the PCF are first introduced, where:

FIG. 1B is a schematic diagram of a process in which the NEF addresses the PCF through the BSF. As shown in FIG. 1B, the process includes:

Step S101, a PDU session is established;

In the process of establishing a PDU session, the bound proxy NF (BSF) selects an appropriate PCF according to a search routing rule, and the PCF creates session binding data (Create the session binding data);

Steps S102 and N5 initiate a request, and the NEF maps the request to the N5 interface.

When the AF initiates the request, the NEF maps the request to the N5 interface, and sends the request to the BSF. The BSF searches for the session binding data to find the corresponding mapping relationship, and the BSF forwards the request to the PCF according to the mapping relationship.

Step S103: When the PDU session is released, the BSF deletes the corresponding session binding data.

2 is a schematic diagram of a process in which a phase NEF addresses a PCF through a user IP. As shown in FIG. 2, the process includes:

Step S201: During the PDU session establishment process, the PCF stores the session binding data in an SDSF (Structured Data Storage Network function), and the SDSF creates session binding data.

In step S202, when the AF initiates the request, the NEF requests the PCF address from the SDSF, and the service request carries the IP address of the user. After the SDSF finds the session binding data, the SDSF returns the PCF address to the NEF.

Step S203, the NEF maps the request to the N5 interface, and sends the request to the PCF.

Step S204: When the PDU session is released, the PCF deletes the corresponding session binding data to the SDSF, and the SDSF deletes the session binding data.

FIG. 3 is a schematic flowchart of the SMF querying the user session binding information to address the PCF. As shown in FIG. 3, the process includes:

Step S301, a PDU session is established, and a user context is established.

Step S302: When the AF initiates a service request, the NEF relies on the IP address information configured by the SMF, and maps the IP address of the user to the SMF.

Step S303: The NEF requests a PCF address from the SMF, where the request carries the user IP address, and after the SMF searches for the user context, returns the PCF address.

Step S304, the NEF maps the request to the N5 interface, and sends the request to the PCF.

Step S305, the PDU session is released;

It can be seen from the above that the user session binding information is used to address the PCF through the SMF; the existing methods are to separately store the session binding relationship of all UEs in the network in the new functional entity or the data storage functional entity. Or directly query the session-related NF with UE session binding information to avoid additional separate storage and dynamic maintenance of session binding information. But there are several problems in the following:

Additional signaling overhead and signaling processing: In addition to query signaling for session binding information, when creating and deleting a session (when an IP address is allocated or released for a PDU session), the database needs to be accessed. Signaling processing overhead. The signaling routing method of the proxy or the redirection does not have additional database access signaling, but the NF needs to perform additional processing on the N7 and N5 interface signaling, and the signaling routing NF is required to have certain signaling processing capability.

Storage and query of session binding data in a roaming scenario: For the roaming scenario, it is necessary to further analyze whether the session binding information is saved in the home network or visited the network, or both. AF, SMF, and PCF may be visiting the network and the home network in the three roaming scenarios. Further consideration needs to be given to the routing of storage and queries.

It is only applicable to PCF addressing where the IP address is not duplicated. The IP address pools allocated to different SMFs are planned in advance. If there is no overlap, the SMF that provides session management for the user can be found through the IP address segment to which the IP address belongs. The session binding information on the implementation implements addressing to the PCF. When a technology such as NAT is used, the SMF divides the address pool repeatedly, and the scheme fails.

Applicable only to PCF bindings where the IP address is not duplicated. When the PCF receives a service request, if the user IP address is duplicated, the binding cannot be implemented.

In order to solve the above problem, in the embodiment of the present application, the public-private network IP (Internet Protocol) address is used to be combined with the session-related NF of the UE (User Equipment, terminal) session binding information, and the SMF address is caused when there is a scenario such as NAT. When the pool is duplicated, the corresponding NF can also be found. When the message is sent to the NF, the SMF identifier is carried along with the private IP-assisted NF of the user for session binding.

The technical solutions of the present application are further elaborated below in conjunction with the accompanying drawings and embodiments.

This embodiment provides a PCF addressing method, which is applied to a network device (for example, NEF or NRF). The functions implemented by the method can be implemented by using a processor in the network device to call program code. Of course, the program code can be saved in As seen in computer storage media, the network device includes at least a processor and a storage medium.

4 is a schematic flowchart of an implementation manner of a PCF addressing method according to an embodiment of the present application. As shown in FIG. 4, the method includes:

Step S401, the NEF or the NRF receives an application function AF sending request, where the request carries the first IP information and the second IP address of the user;

In some embodiments, the first IP information may be public network IP information, and the second IP address may be a private network address. The first IP information includes at least one of the following: a public network IP address, a public network IP address mask, a public network IP corresponding to the NAT name, a public network IP domain name, and a NF information indicating the user's location. The second IP address includes a private network IP address of the user.

Step S402, the NEF or the NRF queries the association information according to the first IP information and the second IP address to obtain session information for managing a PDN session of the user's packet data network; the association information is used to pass the first IP information of the user. And the second IP address of the user finds relevant session information for providing session management for the user.

In some embodiments, the association information includes a first mapping relationship table and a second mapping relationship table, such that the first mapping relationship table and the second mapping relationship table are queried, and session related management of the user's packet data network PDN session can be obtained. The first mapping relationship table is used to find a network address translation NAT that provides session management for the user through the public network internet protocol IP information of the user, thereby finding a session related network function NF list existing under the NAT; the second mapping The relationship table is used to find a session-related NF for providing session management for the user under the current NAT through the private IP address of the user.

In some embodiments, the method further includes:

In step S11, the NEF or the NRF sends a query request for querying the address of the PCF to the session-related network function NF according to the identifier of the session-related NF, where the query request carries the second IP address of the user terminal; the NEF or NRF Receiving an address of the bound PCF returned by the session related NF;

Step S12: The NEF or NRF sends a request to the PCF according to the address of the PCF, where the request carries an SMF identifier and a second IP address of the user.

In some embodiments, the method further includes:

In step S21, the mapping between the NAT and the first IP information of the user is mapped one by one to obtain a first mapping relationship table, so as to find a NAT for providing session management for the user by using the first IP information of the user, so as to find a list of session-related NFs existing under NAT;

In step S22, the session-related NF identifier is mapped to the second IP address of the user in the same NAT to obtain a second mapping relationship table, so as to find the user under the current NAT by using the second IP address of the user. Session-managed NF for session management.

In some embodiments, the first mapping relationship table includes a first correspondence relationship table, where the first correspondence relationship table is used to represent a correspondence between correspondence between the first IP information and the identifier of the session-related NF. ;or,

The first mapping relationship table includes a second correspondence relationship table and a third correspondence relationship table, where the second correspondence relationship table is used to represent a correspondence between the identifier of the NAT to which the session-related NF belongs and the first IP information, and second The correspondence table is used to characterize the correspondence between the identifier of the NAT and the identifier of the session-related NF.

In some embodiments, the NEF or the NRF queries the first mapping relationship table and the second mapping relationship table according to the first IP information and the second IP address, to obtain an identifier of the session-related NF that manages the PDN session of the user, including :

Step S31, the NEF or the NRF queries the first mapping relationship table according to the first IP information, and obtains the identifier of the NAT to which the session-related NF belongs.

Step S32: The NEF or the NRF obtains a second mapping relationship table according to the identifier of the NAT to which the session-related NF belongs.

In step S33, the NEF or the NRF queries the second mapping relationship table according to the private network IP address to obtain the identifier of the session-related NF.

This embodiment further proposes a PCF addressing method, the method comprising:

In step S401, the NEF or the NRF receives an AF transmission request, where the request carries the public network IP information of the user and the private network IP address.

Step S402, the NEF or the NRF queries the first mapping relationship table and the second mapping relationship table according to the public network IP information and the private network IP address, and obtains the identifier of the session-related NF for managing the PDN session of the user's packet data network; A mapping relationship table is used to find a network address translation NAT that provides session management for the user through the public network Internet Protocol (IP) information of the user, thereby finding a session-related network function NF list existing under the NAT; the second mapping relationship table is used to pass The user's private network IP address is found under the current NAT to provide session-related session-related NF for the user.

The identifier of the session-related NF may be the address of the session-related NF.

In some embodiments, the method further includes: presetting the first mapping relationship table and the second mapping relationship table on the NEF or the NRF by the NEF or the NRF.

The second mapping relationship table is used to represent the correspondence between the identifier of the session-related NF and the private network IP address in the same NAT, where the first mapping relationship table is used to identify the identifier of the NAT to which the session-related NF belongs. Correspondence between public network IP information;

In some embodiments, the method further includes:

In step S41, the NEF or the NRF sends a query request for querying the address of the PCF to the session-related network function NF according to the identifier of the session-related NF, where the query request carries the private network internet protocol IP address of the user terminal;

The session-related NF searches for the session binding information according to the private network IP address, and obtains the address of the binding policy control function PCF.

Step S42, the NEF or NRF receives the address of the bound PCF returned by the session related NF;

Step S43: The NEF or the NRF sends a request to the PCF according to the address of the PCF, where the request carries an SMF identifier and a private network IP address of the user.

In this way, the PCF performs session binding and provides services for the user according to the first mapping table of the first mapping relationship and the identifier of the session-related NF in the request and the private network IP address.

In some embodiments, the method further includes: mapping, between the NATs, the identifier of the NAT and the public network IP information of the user, to obtain a first mapping relationship table, which is found by using the public network IP information of the user. The user provides the session-managed NAT to find the session-related NF list that exists in the NAT. In the same NAT, the session-related NF identifier is mapped to the user's private network IP address one by one to obtain a second mapping relationship table. The session-related NF that provides session management for the user is found under the current NAT by the private IP address of the user.

As can be seen from the above, the assigned public IP address is planned in advance and there is no overlap. Therefore, the IP address segment to which the user's public network IP address belongs can be found to provide the session management NAT for the user, thereby finding the SMF list existing under the NAT. The private network IP address (SMF address pool) allocated to different SMFs is planned in advance, and there is no overlap. Therefore, the SMF that provides session management for the user can be found under the current NAT through the IP address segment to which the user private network IP address belongs. In this way, the user's public network and private network IP address can be combined to uniquely determine the SM serving the user.

In some embodiments, the NEF or the NRF queries the first mapping relationship table and the second mapping relationship table according to the public network IP information and the private network IP address, and obtains the identifier of the session-related NF for managing the PDN session of the user, including :

Step S51, the NEF or the NRF queries the first mapping relationship table according to the public network IP information, and obtains the identifier of the NAT to which the session-related NF belongs.

Step S52: The NEF or the NRF obtains a second mapping relationship table according to the identifier of the NAT to which the session-related NF belongs.

Step S53: The NEF or the NRF queries the second mapping relationship table according to the private network IP address to obtain the identifier of the session-related NF.

In some embodiments, the session related NF comprises one of: SMF, SDSF, BSF.

In some embodiments, the first mapping relationship table is used to represent a correspondence between an identifier of a NAT to which the session-related NF belongs and public network IP information; and the second mapping relationship table is used to represent the same NAT. Correspondence between the identifier of the session-related NF and the IP address of the private network.

In some embodiments, the first mapping relationship table includes a first correspondence relationship table, where the first correspondence relationship table is used to represent a correspondence between correspondence between public network IP information and identifiers of session-related NFs. Or the first mapping relationship table includes a second correspondence relationship table and a third correspondence relationship table, where the second correspondence relationship table is used to represent a correspondence between the identifier of the NAT to which the session-related NF belongs and the public network IP information. The second correspondence table is used to represent the correspondence between the identifier of the NAT and the identifier of the session-related NF.

It can be seen from the above that the mapping table between the pre-made NAT and the public network IP address segment and the correspondence table between the NAT and the SMF(s), or the public IP address segment and the SMF(s) directly on the NEF or NRF. Correspondence table. The second correspondence table is used to identify the identity of the session-related NF under the same NAT.

In some embodiments, the public network IP information includes at least one of the following: a public network IP address, a public network IP address mask, a public network IP corresponding NAT name, and information indicating a public network IP domain name.

In the embodiment of the present application, the public-private network IP address is used to combine the session-related NF with the UE session binding information to query, and the corresponding NF can be found when the SMF address pool is duplicated in the presence of a scenario such as NAT (for example, PCF, etc.) When the NEF/AF sends an interface message to a PCF (for example, a network element such as a PCF), it also carries the SMF identifier and the private IP address of the user to assist the NF for session binding. The session related NF includes one of the following: SMF, SDSF, and BSF. The interface message may be an N5 interface message, or a Naf or Nnef interface message, and is mapped to an N5 interface or a message on the NEF slave service platform (AF/SCS/AS). The N5 interface message is a service request, and the request sent by the AF is mapped to a message on the N5 interface or the NEF slave service platform (AF/SCS/AS). Session binding generally has two steps: 1) SMF/BSF for session binding, used to query PCF address; 2) PCF for session binding, used to generate new policy rules.

In a 5G network, the SMF is responsible for assigning an IP address to the user, having a correspondence between the user identifier (ID) and the IP address, and during the PDU Session Establishment process, the SMF can obtain a session binding of a certain PDU session. Information, saved in the context of the UE. The session binding information includes session information, such as user private network IP, SMF ID, PCF ID, and the like. The user ID can be a user code number, an APN, or the like, that is, a mapping relationship between the user ID and the private network IP address of the user.

In the same NAT (multiple SMFs may exist under one NAT gateway), the private network IP addresses assigned to different SMFs (that is, the SMF address pool, one NAT, and the private network IP of the user cannot be duplicated) are planned in advance. There is no overlap. Therefore, the SMF that provides the session management for the user can be found under the current NAT through the IP address segment to which the user's private network IP address belongs.

The IP addresses of the public network are allocated in advance and are not overlapped. Therefore, you can find the NAT that provides session management for the user through the IP address segment to which the user's public IP address belongs. . Combined with the user's public network and private network IP address, the SMF that serves the user can be uniquely determined. After finding the SMF, NEF/AF can achieve addressing to the PCF by directly querying the session binding information on the SMF. The NEF/AF sends a query request to the SMF, where the query request carries the private network IP address of the user; after receiving the query request, the SMF searches for the user context according to the private network IP address, and obtains the address of the PCF bound; then the SMF to the NEF Return the address of the bound PCF or return the address and SMF identifier of the PCF;

When the NEF/AF sends a service request (for example, an N5 request) to the PCF, the service request carries the user SMF identifier and the private network IP of the user, and is used for the PCF to perform session binding. The PCF also needs to be bound. After receiving the message, the PCF needs to bind to the session on the PCF.

The technical solution of this embodiment is as follows:

Step 1: Plan the private network IP address pool of the SMF, and preset the mapping relationship between the SMF identifier and the private network IP address segment on the NEF (Network Opensure Functionality) or NRF (NF Repository Function). (Remarked as mapping table 1), where the identifier of the SMF can be the address of the SMF.

Step 2: Plan the public network IP address pool of the NAT function or functional entity, pre-cast the NAT function or the mapping relationship between the functional entity and the public IP address segment on the NEF or NRF (referred to as mapping table 2a.1) and the NAT function or Correspondence table of functional entities and SMF(s) (denoted as mapping table 2a.2), or correspondence table of public IP address segments and SMF(s) directly on NEF or NRF (recorded as mapping table) 2b).

In the process of implementation, two mapping relationship tables may be used, or three mapping relationship tables may be used. For example, two mapping relationship tables may be implemented by mapping table 1 and mapping table 2b; for example, mapping table 1 may be adopted. , mapping table 2a.1 and mapping table 2a.2 three mapping relationship table to achieve.

Step 3: The AF sends a request to the NEF, where the request carries the public network IP address and the private network IP address of the terminal, and the NEF combination queries the mapping relationship between the SMF and the public network IP address segment and the mapping relationship between the SMF and the private network IP address segment. The table finds the address of the SMF that manages the PDN session of the UE.

Step 4: The NEF sends a query request to the SMF, where the query request carries the private network IP address of the user.

Step 5: The SMF queries the user context according to the private network IP address, and the SMF returns the address of the PCF bound to the NEF or the SMF returns the PCF address and the SMF identifier to the NEF.

Step 6: The NEF sends a request to the PCF according to the address of the PCF, where the request carries the SMF identifier and the private network IP address of the user.

Step 7: The PCF performs binding according to the correspondence between the SMF identifier and the private IP address of the user, and provides services for the user.

The embodiment further provides a PCF addressing method, in which the private network IP address pool of the SMF is first planned, and the NEF (Network Exposure Functionality) or the NRF (NF Repository Function) is pre-prepared. Set the mapping table between the SMF and the IP address segment of the private network; plan the mapping table between the NAT and the public IP address segment on the NEF or NRF, and the mapping between NAT and SMF(s) on the NEF or NRF. Or, the correspondence table between the IP address segment and the SMF(s) of the public network directly on the NEF or NRF. FIG. 5 is a schematic diagram of an implementation process of a PCF addressing method according to another embodiment of the present application. As shown in FIG. 5, the method includes:

Step S501, a PDU session is established;

Step S502: The AF sends a request to the NEF.

The request carries the public network IP address and the private network IP address of the terminal.

In some embodiments, the request includes a private network IP address, and optionally, the request may also include an IP domain, such as a public network IP address. The NEF maps the private network IP address and the IP domain (public network IP address) to the SMF address according to the public and private IP address pool assignment plan (SMFs).

Step S503: The NEF combines the query SMF with the public network IP address segment and the mapping relationship table between the SMF and the private network IP address segment to find the address of the SMF that manages the PDN session of the UE.

Step S504: The NEF sends a query request for the PCF address to the SMF, where the query request carries the private network IP address of the user.

Step S505: The SMF queries the user context according to the private network IP address to obtain the address of the PCF. The SMF returns the address of the PCF bound to the NE or returns the address of the PCF and the SMF identifier.

Step S506: The NEF sends a service request to the PCF according to the address of the PCF, where the service request carries an SMF identifier (optional) and a private network IP address of the user.

In step S507, the PDU session is deleted.

In the embodiment of the present application, 1), when applying for a QoS policy, the service carries the user IP and the user IP domain (IP domain, which can represent the public IP address of the user); 2) plan the private network IP address pool of the SMF. Pre-set the mapping relationship between the SMF and the private IP address segment on the NEF or NRF; 3) Plan the public IP address pool of the NAT, pre-cast the mapping table between the NAT and the public IP address segment on the NEF or NRF, and NAT Correspondence table with SMF(s), or a correspondence table between the IP address segment and SMF(s) of the public network directly on NEF or NRF; 4), NEF combined query SMF and public IP address segment and SMF And the mapping table of the private network IP address segment finds the address of the SMF that manages the PDN (Packet Data Network) session of the UE; 5), the NEF queries the SMF for the request, and carries the private IP address of the user. .

In the process of implementation, the public network IP address can also represent the IP domain, or use the public network mask to represent the IP domain, or directly carry the IP domain name. For example, an IP domain is configured on the NAT gateway NAT1. The public network IP address segment 171.1.1.0/23 is configured on the NAT gateway. The service can be characterized as follows: 1) Directly carrying the IP domain. IP address of the public network, 171.1.1.1; 2) IP address mask of the public network, 171.1.1.1.23 or 171.1.1.0/3; 3) Name of the NAT corresponding to the public network IP, NAT1; 4) Other users can be characterized The name of the IP domain.

Compared with the prior art, this embodiment can solve the problem that the IP address cannot be addressed when the IP address of the private network is duplicated (the SMF cannot be found, and the PCF cannot be found).

Based on the foregoing embodiments, the embodiment of the present application provides a PCF addressing apparatus, which includes all the units included, and modules included in each unit, which can be implemented by a network device, such as a processor in NEF or NRF. Of course, it can also be realized by a specific logic circuit; in the process of implementation, the processor can be a central processing unit (CPU), a microprocessor (MPU), a digital signal processor (DSP) or a field programmable gate array (FPGA). )Wait.

FIG. 6 is a schematic structural diagram of a PCF addressing apparatus according to an embodiment of the present application. As shown in FIG. 6, the apparatus 600 includes a first receiving unit 601 and a querying unit 602, where:

The first receiving unit 601 is configured to receive a network open function NEF sending request, where the request carries the first IP information and the second IP address of the user;

The query unit 602 is configured to query the association information according to the first IP information and the second IP address to obtain session information for managing a PDN session of the user's packet data network, where the association information is used to pass the first IP information of the user and the user. The second IP address finds relevant session information for the user to provide session management.

In some embodiments, the association information includes a first mapping relationship table and a second mapping relationship table, and a session for managing a packet data network PDN session of the user may be obtained by using the first mapping relationship table and the second mapping relationship table. An identifier of the related NF, where the first mapping relationship table is used to find a network address translation NAT that provides session management for the user by using the public network internet protocol IP information of the user, so as to find a session-related network function NF list existing under the NAT; The second mapping relationship table is used to find a session-related NF for providing session management for the user under the current NAT by using the private IP address of the user.

The device further includes a preset unit configured to preset the first mapping relationship table and the second mapping relationship table on the NEF or the NRF.

In some embodiments, the apparatus further includes a first sending unit, a second receiving unit, and a second sending unit, wherein: the first sending unit is configured to send to the session related network function NF according to the identifier of the session related NF a query request for querying an address of the PCF, where the query request carries a second IP address of the user terminal; the second receiving unit is configured to receive an address of the bound PCF returned by the session-related NF; The second sending unit is configured to send a request to the PCF according to the address of the PCF, where the request carries the SMF identifier and the second IP address of the user.

In some embodiments, the session related NF searches the session binding information according to the second IP address to obtain an address of the binding policy control function PCF. The PCF performs session binding and provides services for the user according to the second mapping relationship table of the second mapping and the identifier of the session-related NF and the second IP address in the request.

In some embodiments, the session related NF comprises one of: SMF, SDSF, BSF.

In some embodiments, the association information includes a first mapping relationship table and a second mapping relationship table. The apparatus further includes a mapping unit configured to perform the mapping between the NAT and the first IP information of the user. One-to-one mapping, obtaining a first mapping relationship table to find a session-managed NAT for the user through the first IP information of the user, thereby finding a session-related NF list existing under the NAT; and in the same NAT, the session-related NF The identifier is mapped to the second IP address of the user, and a second mapping relationship table is obtained to find a session-related NF for providing session management for the user under the current NAT by using the second IP address of the user.

In some embodiments, the first mapping relationship table is used to represent a correspondence between the identifier of the NAT to which the session-related NF belongs and the first IP information; and the second mapping relationship table is used to represent the same NAT. The correspondence between the identifier of the session-related NF and the second IP address.

In some embodiments, the first mapping relationship table includes a first correspondence relationship table, where the first correspondence relationship table is used to represent a correspondence between correspondence between the first IP information and the identifier of the session-related NF. Or the first mapping relationship table includes a second correspondence table and a third correspondence table, where the second correspondence table is used to represent a correspondence between the identifier of the NAT to which the session-related NF belongs and the first IP information. The second correspondence table is used to represent the correspondence between the identifier of the NAT and the identifier of the session-related NF.

As can be seen from the above, the mapping table between the pre-made NAT and the first IP address segment and the correspondence table between the NAT and the SMF(s), or directly with the first IP address segment and the SMF(s) on the NEF or NRF. Correspondence table. The second correspondence table is used to identify the identity of the session-related NF under the same NAT.

In some embodiments, the query unit includes a first query module, an acquisition module, and a second query module, wherein:

The first query module is configured to query the first mapping relationship table according to the first IP information, and obtain the identifier of the NAT to which the session-related NF belongs;

The acquiring module is configured to acquire a second mapping relationship table according to the identifier of the NAT to which the session-related NF belongs;

The second query module is configured to query the second mapping relationship table according to the second IP address to obtain an identifier of the session-related NF.

In some embodiments, the first IP information includes at least one of the following: a public network IP address, a public network IP address mask, a public network IP corresponding NAT name, information indicating a public network IP domain name, and a characterizing user. The NF information is located; the second IP address includes the private IP address of the user.

The description of the above device embodiments is similar to the description of the above method embodiments, and has similar advantages as the method embodiments. For technical details not disclosed in the device embodiments of the present application, please refer to the description of the method embodiments of the present application.

It should be noted that, in the embodiment of the present application, if the PCF addressing method described above is implemented in the form of a software function module and sold or used as a standalone product, it may also be stored in a computer readable storage medium. Based on such understanding, the technical solution of the embodiments of the present application may be embodied in the form of a software product in essence or in the form of a software product stored in a storage medium, including a plurality of instructions. Having a network device perform all or part of the methods described in various embodiments of the present application. The foregoing storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read only memory (ROM), a magnetic disk, or an optical disk. Thus, embodiments of the present application are not limited to any particular combination of hardware and software.

Correspondingly, an embodiment of the present application provides a network device, including a memory and a processor, where the memory stores a computer program executable on a processor, where the processor implements the foregoing PCF addressing method when executing the program. A step of.

Correspondingly, the embodiment of the present application provides a computer readable storage medium, where a computer program is stored thereon, and when the computer program is executed by the processor, the steps in the PCF addressing method are implemented.

It should be noted here that the description of the above storage medium and device embodiments is similar to the description of the above method embodiments, and has similar advantages as the method embodiments. For technical details not disclosed in the storage medium and device embodiments of the present application, please refer to the description of the method embodiments of the present application.

It is to be noted that FIG. 7 is a schematic diagram of a hardware entity of a network device in the embodiment of the present application. As shown in FIG. 7, the hardware entity of the network device 700 includes: a processor 701, a communication interface 702, and a memory 703.

Processor 701 typically controls the overall operation of network device 700.

Communication interface 702 can enable network devices to communicate with other terminals or servers over a network.

The memory 703 is configured to store instructions and applications executable by the processor 701, and may also cache data to be processed or processed by the processor 701 and each module in the network device 700 (eg, image data, audio data, voice communication data, and Video communication data) can be realized by flash memory (FLASH) or random access memory (RAM).

It is to be understood that the phrase "one embodiment" or "an embodiment" or "an embodiment" or "an embodiment" means that the particular features, structures, or characteristics relating to the embodiments are included in at least one embodiment of the present application. Thus, "in one embodiment" or "in an embodiment" or "an" In addition, these particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. It should be understood that, in the various embodiments of the present application, the size of the sequence numbers of the foregoing processes does not mean the order of execution sequence, and the order of execution of each process should be determined by its function and internal logic, and should not be applied to the embodiment of the present application. The implementation process constitutes any limitation. The serial numbers of the embodiments of the present application are merely for the description, and do not represent the advantages and disadvantages of the embodiments.

It is to be understood that the term "comprises", "comprising", or any other variants thereof, is intended to encompass a non-exclusive inclusion, such that a process, method, article, or device comprising a series of elements includes those elements. It also includes other elements that are not explicitly listed, or elements that are inherent to such a process, method, article, or device. An element that is defined by the phrase "comprising a ..." does not exclude the presence of additional equivalent elements in the process, method, item, or device that comprises the element.

In the several embodiments provided by the present application, it should be understood that the disclosed apparatus and method may be implemented in other manners. The device embodiments described above are merely illustrative. For example, the division of the unit is only a logical function division. In actual implementation, there may be another division manner, such as: multiple units or components may be combined, or Can be integrated into another system, or some features can be ignored or not executed. In addition, the coupling, or direct coupling, or communication connection of the components shown or discussed may be indirect coupling or communication connection through some interfaces, devices or units, and may be electrical, mechanical or other forms. of.

The units described above as separate components may or may not be physically separated, and the components displayed as the unit may or may not be physical units; they may be located in one place or distributed on multiple network units; Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may be separately used as one unit, or two or more units may be integrated into one unit; the above integration The unit can be implemented in the form of hardware or in the form of hardware plus software functional units.

It will be understood by those skilled in the art that all or part of the steps of implementing the foregoing method embodiments may be performed by hardware related to program instructions. The foregoing program may be stored in a computer readable storage medium, and when executed, the program includes The foregoing steps of the method embodiment; and the foregoing storage medium includes: a removable storage device, a read only memory (ROM), a magnetic disk, or an optical disk, and the like, which can store program codes.

Alternatively, the above-described integrated unit of the present application may be stored in a computer readable storage medium if it is implemented in the form of a software function module and sold or used as a stand-alone product. Based on such understanding, the technical solution of the embodiments of the present application may be embodied in the form of a software product in essence or in the form of a software product stored in a storage medium, including a plurality of instructions. A network device or the like is caused to perform all or part of the method described in the various embodiments of the present application. The foregoing storage medium includes various media that can store program codes, such as a mobile storage device, a ROM, a magnetic disk, or an optical disk.

The foregoing is only an embodiment of the present application, but the scope of protection of the present application is not limited thereto, and any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed in the present application. It is covered by the scope of protection of this application. Therefore, the scope of protection of the present application should be determined by the scope of the claims.

Claims

A policy control function PCF addressing method, the method comprising:

The network open function NEF or the network function registration function NRF receives the application function AF sending request, where the request carries the first internet protocol IP information of the user and the second IP address of the user;

The NEF or the NRF queries the association information according to the first IP information and the second IP address to obtain session information for managing a PDN session of the user's packet data network; the association information is used to pass the first IP information of the user and the user. The second IP address finds relevant session information for the user to provide session management.
The method of claim 1 further comprising:

The NEF or the NRF sends a query request for querying the address of the PCF to the session-related network function NF according to the identifier of the session-related NF, where the query request carries the second IP address of the user terminal;

Receiving, by the NEF or NRF, an address of a bound PCF returned by the session related NF;

The NEF or NRF sends a request to the PCF according to the address of the PCF, where the request carries an SMF identifier and a second IP address of the user.
The method of claim 1, the session related NF comprising one of: a session management function SMF, a structured data storage network function SDSF, a binding support function BSF.
The method according to claim 1, wherein the association information comprises a first mapping relationship table and a second mapping relationship table; the method further comprising:

The mapping between the NAT and the first IP information of the user is mapped to the first mapping relationship to obtain the NAT for the session management. Session related NF list;

In the same NAT, the session-related NF identifier is mapped to the second IP address of the user, and a second mapping relationship table is obtained, so that the session management is found for the user under the current NAT by using the second IP address of the user. Session related NF.
The method according to claim 4, wherein the first mapping relationship table includes a first correspondence relationship table, where the first correspondence relationship table is used to represent a correspondence between the first IP information and the identifier of the session-related NF Correspondence; or,

The first mapping relationship table includes a second correspondence relationship table and a third correspondence relationship table, where the second correspondence relationship table is used to represent a correspondence between the identifier of the NAT to which the session-related NF belongs and the first IP information, and second The correspondence table is used to characterize the correspondence between the identifier of the NAT and the identifier of the session-related NF.
The method according to claim 4, wherein the NEF or NRF queries the first mapping relationship table and the second mapping relationship table according to the first IP information and the second IP address to obtain a session-related NF for managing a PDN session of the user. Logo, including:

The NEF or the NRF queries the first mapping relationship table according to the first IP information, and obtains the identifier of the NAT to which the session-related NF belongs.

Obtaining, by the NEF or the NRF, the second mapping relationship table according to the identifier of the NAT to which the session-related NF belongs;

The NEF or the NRF queries the second mapping relationship table according to the second IP address to obtain an identifier of the session-related NF.
The method according to any one of claims 1 to 4, wherein the first IP information comprises at least one of the following: a public network IP address, a public network IP address mask, a public network IP corresponding NAT name, and a public network IP address. The information of the name of the domain, indicating the NF information of the user; the second IP address includes the private network IP address of the user.
A policy control function PCF addressing device, the device comprising:

The first receiving unit is configured to receive a network open function NEF sending request, where the request carries the first IP information and the second IP address of the user;

The query unit is configured to query the association information according to the first IP information and the second IP address to obtain session information for managing the PDN session of the user's packet data network; wherein the association information is used to pass the first IP information of the user and the user The second IP address finds relevant session information for the user to provide session management.
A network device comprising a memory and a processor, the memory storing a computer program executable on a processor, the processor executing the program to implement the policy control function PCF according to any one of claims 1 to 7. The steps in the addressing method.
A computer readable storage medium having stored thereon a computer program, the computer program being executed by a processor to implement the steps in the PCF addressing method of the policy control function of any one of claims 1 to 7.