WO2020034930A1

WO2020034930A1 - Pdu session management, node association and upf discovery methods and entities

Info

Publication number: WO2020034930A1
Application number: PCT/CN2019/100306
Authority: WO
Inventors: 艾明
Original assignee: 电信科学技术研究院有限公司
Priority date: 2018-08-13
Filing date: 2019-08-13
Publication date: 2020-02-20
Also published as: CN113347673A; CN113347673B; CN110831092A; CN110831092B

Abstract

Disclosed in the present application are PDU session management, node association and UPF discovery methods and entities, for use in implementing a mixed deployment scenario of a UPF entity that supports a PTP interface and a UPF entity that supports an SBI interface, and implementing the interaction between a control plane entity and the UPF entity. The PDU session management method comprises: a session management function (SMF) entity selects at least one user plane function (UPF) entity for a PDU session to be established; the SMF entity determines, for a first UPF entity in the at least one UPF entity, a mode of interaction with the first UPF entity, wherein configuration information of a UPF entity comprises modes of interaction supported by said UPF entity, and the modes of interaction comprise a mode of performing interaction by means of a point-to-point (PTP) interface, and a mode of performing interaction by invoking a service by means of a service based interface (SBI); the SMF entity interacts with the first UPF entity on the basis of the determined mode of interaction.

Description

Method and entity for PDU session management, node association and UPF discovery

Cross-reference to related applications

This application claims the priority of a Chinese patent application filed on August 13, 2018 with the Chinese Patent Office, application number 201810918468.7, and application name "PDU Session Management, Node Association, and UPF Discovery Methods and Equipment", all of which passed Citations are incorporated in this application.

Technical field

The present application relates to the field of communication technologies, and in particular, to a method and entity for packet data unit (PDU) session management, node association, and user plane function (UPF) discovery.

Background technique

At present, in the fifth generation (5Generation, 5G) mobile communication system, a service-oriented architecture is introduced to the control plane, as shown in FIG. 1, which is a network architecture diagram using a Service-Based Interface (SBI) interface. Among them, the SBI interface is used for interaction between control plane entities. For example, when a Session Management Function (SMF) entity needs to interact with a Network Repository Function (NRF) entity, This can be achieved by calling the services provided by the NRF entity; and point-to-point (PTP) interfaces are used for interaction between user plane entities and between control plane entities and user plane entities.

In the current research process, it is considered to introduce the idea of service to the user. For example, the UPF entity also uses the SBI interface. However, the original UPF entity cannot support the SBI interface, and the newly introduced UPF entity may support SBI. Interface, and then the original control plane entity directly interacting with the UPF entity through the PTP interface is obviously no longer applicable, so how to implement the control plane entity in a mixed deployment scenario that supports PTP interface UPF entities and SBI interface UPF entities Interaction with UPF entities is an urgent issue.

Summary of the Invention

The embodiments of the present application provide a method and entity for PDU session management, node association, and UPF discovery, which are used to implement a control plane entity and UPF in a mixed deployment scenario of a UPF entity supporting a PTP interface and a UPF entity supporting an SBI interface. Interaction between entities.

In a first aspect, an embodiment of the present application provides a PDU session management method, including:

The SMF entity selects at least one UPF entity for the PDU session to be established;

For the first UPF entity in the at least one UPF entity, the SMF entity determines an interaction mode for interacting with the first UPF entity; wherein configuration information of a UPF entity includes information supported by the one UPF entity An interactive manner, which includes a manner of interacting through a point-to-point PTP interface, and a manner of invoking a service through a serviced SBI interface for interaction;

When the SMF entity determines to interact with the first UPF entity through the SBI interface, the SMF entity invokes a session establishment service provided by the first UPF entity through the SBI interface to establish the PDU session A PDU session provided by the first UPF entity; or

When the SMF entity determines to interact with the first UPF entity through the PTP interface, the SMF entity sends a session establishment message to the first UPF entity through the PTP interface to establish the PDU session. A PDU session served by the first UPF entity.

In the embodiment of the present application, after the SMF entity selects the UPF entity serving the PDU session, it will determine the interaction mode for interacting with the UPF entity, that is, the interaction through the N4 interface between the original SMF entity and the UPF entity. , Or interact through the SBI interface provided by the UPF entity, and then establish a session according to the determined interaction mode to achieve the interaction between the SMF entity and the UPF entity.

Optionally, the SMF entity selecting at least one UPF entity for the PDU session to be established includes:

According to the list of UPF entities stored by the SMF entity itself and the configuration information of the UPF entities in the list, the SMF entity selects from the list the at least one UPF entity that meets a condition, and the condition includes the ability to provide a specified The UPF service and / or can support the specified interaction mode.

Optionally, the method further includes:

The SMF entity sends a Network Function (NF) status subscription message to the NRF entity, where the NF status subscription message is used to subscribe to a UPF entity that meets a condition, the condition including being able to provide a specified UPF service and / or Ability to support specified interaction methods;

Receiving, by the SMF entity, an NF status notification message sent by the NRF entity, where the NF status notification message carries configuration information of at least one UPF entity that already exists or is newly added in the NRF entity that meets the condition;

The SMF entity updates the list of UPF entities stored in the SMF entity according to the NF status notification message.

The SMF entity sends a NF discovery request message to an NRF entity, and the NF discovery request message is used to request the NRF entity to provide a UPF entity that meets a condition, the condition including being able to provide a specified UPF service and / or being able to support a specified interactive mode;

Receiving, by the SMF entity, an NF discovery response message sent by the NRF entity, where the NF discovery response message carries configuration information of a UPF entity that meets the condition;

The SMF entity selects the at least one UPF entity from the UPF entities that satisfy the condition.

Optionally, the determining, by the SMF entity, an interaction mode for interacting with the first UPF entity includes:

Determining, by the SMF entity, an interaction mode for interacting with the first UPF entity based on the configuration information of the first UPF entity, or

Determining, by the SMF entity, an interaction mode for interacting with the first UPF entity based on its own configuration information, wherein the configuration information of the SMF entity indicates an interaction mode supported by the SMF entity; or,

The SMF entity determines an interaction mode for interacting with the first UPF entity based on a node association context, and the node association context indicates an interaction mode determined by the SMF entity for interacting with the first UPF entity.

Optionally, the configuration information of the UPF entity includes at least one of the following information:

Fully Qualified Domain Name (FQDN) of the UPF entity;

The Internet Protocol (IP) address of the UPF entity;

Services that UPF entities can provide;

The interaction modes that the UPF entity can support;

The area identifier of the SMF entity that the UPF entity can serve.

Optionally, after the SMF entity determines an interaction mode with the first UPF entity, the method further includes:

The SMF entity records the determined interaction manner in the context of a PDU session served by the first UPF entity; or

The SMF entity records the determined first UPF entity interaction manner in a context of a terminal corresponding to the PDU session.

In the embodiment of the present application, after determining the interaction mode with the first UPF entity, the SMF entity can record the determined interaction mode in the context, so that in the subsequent management process of the PDU session, the interaction mode can be conveniently obtained from the context. .

Optionally, the method further includes:

When the PDU session served by the first UPF entity needs to be modified, the SMF entity acquires the interaction mode with the first UPF entity recorded in the context; the context is the context of the PDU session or the The context of the terminal corresponding to the PDU session;

If the acquired interaction mode is a method of invoking a service through the SBI interface, the SMF entity invokes a session modification service provided by the first UPF entity through the SBI interface to modify the first UPF entity The serving PDU session; or

If the obtained interaction mode is an interaction mode through the PTP interface, the SMF entity sends a session modification message to the first UPF entity through the PTP interface to modify the PDU served by the first UPF entity. Conversation.

Optionally, the method further includes:

When the PDU session served by the first UPF entity needs to be released, the SMF entity obtains the interaction mode with the first UPF entity recorded in the context; the context is the context of the PDU session or the The context of the terminal corresponding to the PDU session;

If the obtained interaction mode is a method of invoking a service through the SBI interface, the SMF entity calls the session release service provided by the first UPF entity through the SBI interface to release the first UPF entity The serving PDU session; or

If the obtained interaction mode is an interaction mode through the PTP interface, the SMF entity sends a session release message to the first UPF entity through the PTP interface to release the PDU served by the first UPF entity. Conversation.

In a second aspect, an embodiment of the present application provides a method for node association between an SMF entity and a UPF entity, including:

The SMF entity determines the interaction mode with the UPF entity to be associated, and the interaction modes include a manner of interacting through a PTP interface and a manner of invoking a service through an SBI interface to interact;

When the SMF entity determines to interact with the UPF entity through the SBI interface, the SMF entity invokes a node association service provided by the UPF entity through the SBI interface to perform node association with the UPF entity;

When the SMF entity determines to interact with the UPF entity through the PTP interface, the SMF entity sends a node association message to the UPF entity through the PTP interface to perform node association with the UPF entity.

Optionally, the SMF entity determining an interaction mode for interacting with the UPF entity includes:

Determining, by the SMF entity, an interaction mode for interacting with the first UPF entity based on the configuration information of the UPF entity, or

The SMF entity determines an interaction mode for interacting with the UPF entity based on its own configuration information, wherein the configuration information of the SMF entity itself indicates the interaction mode supported by the SMF entity.

Optionally, after the SMF entity determines an interaction mode with the UPF entity to be associated, the method further includes:

The SMF entity records the determined interaction mode with the UPF entity in a node association context.

Optionally, the method further includes:

When the configuration information of the UPF entity needs to be updated, the SMF entity acquires the interaction mode with the UPF entity recorded in the node association context;

If the obtained interaction mode is a method of invoking a service through the SBI interface, the SMF entity invokes a node update service provided by the UPF entity through the SBI interface to update the configuration information of the UPF entity; or,

If the obtained interaction mode is an interaction mode through the PTP interface, the SMF entity sends a node update message to the UPF entity through the PTP interface to update the configuration information of the UPF entity.

Optionally, the method further includes:

When the node association relationship with the UPF entity needs to be released, the SMF entity obtains the interaction mode with the UPF entity recorded in the node association context;

If the obtained interaction mode is a method of invoking a service through the SBI interface, the SMF entity invokes a node release service provided by the UPF entity through the SBI interface to release the connection with the UPF entity. Node associations; or,

If the obtained interaction mode is an interaction mode through the PTP interface, the SMF entity sends a node release message to the UPF entity through the PTP interface to release the node association relationship with the UPF entity. .

Optionally, the method further includes:

When the message filtering descriptor of the UPF entity needs to be configured, the SMF entity acquires the interaction mode with the UPF entity recorded in the node association context;

If the obtained interaction mode is a method of invoking a service through the SBI interface, the SMF entity invokes a message filtering descriptor provided by the UPF entity to provide services through the SBI interface to configure the UPF entity The message filtering descriptor; or

If the obtained interaction mode is an interaction mode through the PTP interface, the SMF entity sends a message filtering descriptor provision message to the UPF entity through the PTP interface to configure a message of the UPF entity Filter descriptor.

Optionally, the method further includes:

When the message filtering descriptor of the UPF entity needs to be removed, the SMF entity obtains the interaction mode with the UPF entity recorded in the node association context;

If the obtained interaction mode is a method for invoking a service through the SBI interface, the SMF entity invokes a message filtering descriptor removal service provided by the UPF entity through the SBI interface to remove the Message filtering descriptor of the UPF entity; or

If the obtained interaction mode is an interaction mode through the PTP interface, the SMF entity sends a message filtering descriptor removal message to the UPF entity through the PTP interface to remove the UPF entity. Message filtering descriptor.

In a third aspect, an embodiment of the present application provides a method for discovering a UPF entity, including:

The NRF entity receives a first request message sent by the SMF entity, the first request message is used to request to obtain configuration information of a UPF entity that meets a condition, the condition includes being able to provide a specified UPF service and / or being able to support a specified interaction mode The interaction manner includes a manner of interacting through a point-to-point PTP interface, and a manner of invoking a service for interaction through a serviced SBI interface;

The NRF entity searches among the registered UPF entities for at least one UPF entity that meets the condition;

The NRF entity sends a first response message to the SMF entity, and the first response message carries configuration information of the at least one UPF entity.

In the embodiment of the present application, when the SMF entity requests the UPF process, it needs to specify which UPF entity it needs, that is, the UPF entity that can provide which services, and / or the UPF entity that can support which interfaces, so that the feedback from the NRF entity The UPF entity meets the requirements of the SMF entity, and the NRF also informs the SMF entity of the configuration information of these UPF entities when the UPF entity list is fed back, so that in the mixed deployment scenario of the SBI interface and the PTP interface, the SMF entity and the UPF entity are Interactions provide the foundation.

Optionally, the first request message is an NF discovery request message, and the first response message is an NF discovery response message.

Optionally, the first request message is a NF status subscription message, the NF status subscription message is used to subscribe to a UPF entity that meets a condition, and the first response message is a NF status notification message.

Optionally, the method further includes:

The NRF entity receives an NF registration request message sent by a second UPF entity, and the NF registration request message carries configuration information of the second UPF entity, where the configuration information includes services that the second UPF entity can provide and / Or an interaction mode that can be supported by the second UPF entity;

The NRF entity stores configuration information of the second UPF entity;

The NRF entity sends a NF registration response message to the second UPF entity to notify the second UPF entity that the registration is accepted.

Optionally, the method further includes:

Determining, by the NRF entity, whether the second UPF entity meets the condition;

If the determination result is yes, the NRF entity sends an NF status notification message to the SMF entity, and the NF status notification message carries configuration information of the second UPF entity.

Fully qualified domain name FQDN of the UPF entity;

Network protocol IP address of the UPF entity;

Services that UPF entities can provide;

The interaction modes that the UPF entity can support;

The area identifier of the SMF entity that the UPF entity can serve.

In a fourth aspect, an embodiment of the present application provides an SMF entity, including:

A selection unit, configured to select at least one user plane function UPF entity for a PDU session to be established;

A determining unit, configured to determine an interaction mode for interacting with the first UPF entity for the first UPF entity in the at least one UPF entity; wherein the configuration information of a UPF entity includes the information supported by the UPF entity Interactive methods, including interactive methods through a point-to-point PTP interface, and invoking services through a serviced SBI interface for interaction;

An execution unit, configured to, when determining to interact with the first UPF entity through the SBI interface, invoke a session establishment service provided by the first UPF entity through the SBI interface to establish the PDU session The PDU session provided by the first UPF entity; or when determining to interact with the first UPF entity through the PTP interface, sending a session establishment message to the first UPF entity through the PTP interface to establish A PDU session provided by the first UPF entity in the PDU session.

Optionally, the selection unit is specifically configured to:

Selecting from the list at least one UPF entity that satisfies a condition according to the list of UPF entities stored in the SMF entity and the configuration information of the UPF entity in the list, the condition including being able to provide a specified UPF service and / or Ability to support specified interaction methods.

Optionally, the SMF entity further includes an update unit;

The execution unit is further configured to send an NF status subscription message to the NRF entity, where the NF status subscription message is used to subscribe to a UPF entity that meets a condition, the condition includes being able to provide a specified UPF service and / or being able to support a specified And an NF status notification message sent by the NRF entity, where the NF status notification message carries configuration information of at least one UPF entity that already exists or is newly added in the NRF entity that meets the condition;

The updating unit is configured to update the list of UPF entities stored in the SMF entity according to the NF status notification message.

Optionally, the selection unit is specifically configured to:

Sending a NF discovery request message to an NRF entity, the NF discovery request message is used to request the NRF entity to provide a UPF entity that meets a condition, the condition including being able to provide a specified UPF service and / or being able to support a specified interaction mode;

Receiving a NF discovery response message sent by the NRF entity, where the NF discovery response message carries configuration information of a UPF entity that meets the condition;

The at least one UPF entity is selected from the UPF entities that satisfy the condition.

Optionally, the determining unit is specifically configured to:

Determining an interaction mode for interacting with the first UPF entity based on the configuration information of the first UPF entity, or

Determining an interaction mode for interacting with the first UPF entity based on the configuration information of the SMF entity, wherein the configuration information of the SMF entity indicates the interaction mode supported by the SMF entity; or

An interaction mode for interacting with the first UPF entity is determined based on a node association context, and the node association context indicates an interaction mode determined by the SMF entity to interact with the first UPF entity.

Fully qualified domain name FQDN of the UPF entity;

Network protocol IP address of the UPF entity;

Services that UPF entities can provide;

The interaction modes that the UPF entity can support;

The area identifier of the SMF entity that the UPF entity can serve.

Optionally, the execution unit is further configured to:

Record the determined interaction manner in the context of a PDU session served by the first UPF entity; or

Record the determined first UPF entity interaction mode in the context of the terminal corresponding to the PDU session.

Optionally, the execution unit is further configured to:

When the PDU session served by the first UPF entity needs to be modified, the interaction mode with the first UPF entity recorded in the context is obtained; the context is the context of the PDU session or the corresponding one of the PDU session The context of the terminal;

If the obtained interaction mode is a method for invoking a service through the SBI interface, then call the session modification service provided by the first UPF entity through the SBI interface to modify the PDU session served by the first UPF entity ;or,

If the obtained interaction mode is an interaction mode through the PTP interface, a session modification message is sent to the first UPF entity through the PTP interface to modify a PDU session served by the first UPF entity.

Optionally, the execution unit is further configured to:

When the PDU session served by the first UPF entity needs to be released, the interaction mode with the first UPF entity recorded in the context is acquired; the context is the context of the PDU session or the corresponding one of the PDU session The context of the terminal;

If the obtained interaction mode is a method of invoking a service through the SBI interface, then call the session release service provided by the first UPF entity through the SBI interface to release the PDU session served by the first UPF entity ;or,

If the obtained interaction mode is an interaction mode through the PTP interface, a session release message is sent to the first UPF entity through the PTP interface to release a PDU session served by the first UPF entity.

In a fifth aspect, an embodiment of the present application provides an SMF entity, including:

A determining unit, configured to determine an interaction manner with a UPF entity to be associated, the interaction manner includes a manner of interacting through a PTP interface, and a manner of invoking a service through an SBI interface to interact;

An execution unit, configured to, when the SMF entity determines to interact with the UPF entity through the SBI interface, invoke the node association service provided by the UPF entity through the SBI interface to perform node association with the UPF entity And, when the SMF entity determines to interact with the UPF entity through the PTP interface, the SMF entity sends a node association message to the UPF entity through the PTP interface to perform a node with the UPF entity; Associated.

Optionally, the determining unit is specifically configured to:

Determining an interaction mode for interacting with the first UPF entity based on the configuration information of the UPF entity, or

An interaction mode for interacting with the UPF entity is determined based on the configuration information of the SMF entity, wherein the configuration information of the SMF entity indicates the interaction mode supported by the SMF entity.

Optionally, the SMF entity further includes a recording unit, configured to:

The determined interaction manner with the UPF entity is recorded in a node association context.

Optionally, the execution unit is further configured to:

When the configuration information of the UPF entity needs to be updated, acquiring the interaction mode with the UPF entity recorded in the node association context;

If the obtained interaction mode is a method of invoking a service through the SBI interface, then the node update service provided by the UPF entity is called through the SBI interface to update the configuration information of the UPF entity; or,

If the obtained interaction mode is an interaction mode through the PTP interface, a node update message is sent to the UPF entity through the PTP interface to update the configuration information of the UPF entity.

Optionally, the execution unit is further configured to:

When the node association relationship with the UPF entity needs to be released, obtaining the interaction mode with the UPF entity recorded in the node association context;

If the obtained interaction mode is a method of invoking a service through the SBI interface, calling the node release service provided by the UPF entity through the SBI interface to release the node association relationship with the UPF entity; or,

If the obtained interaction mode is an interaction mode through the PTP interface, a node release message is sent to the UPF entity through the PTP interface to release the node association relationship with the UPF entity.

Optionally, the execution unit is further configured to:

When the message filtering descriptor of the UPF entity needs to be configured, obtaining the interaction mode with the UPF entity recorded in the node association context;

If the obtained interaction mode is a method for invoking a service through the SBI interface, then the SBI interface is used to call a message filtering descriptor provided by the UPF entity to provide a service to configure the message filtering of the UPF entity. Descriptor; or,

If the obtained interaction mode is an interaction mode through the PTP interface, a message filtering descriptor provision message is sent to the UPF entity through the PTP interface to configure the message filtering descriptor of the UPF entity.

Optionally, the execution unit is further configured to:

When the message filtering descriptor of the UPF entity needs to be removed, obtaining the interaction mode with the UPF entity recorded in the node association context;

If the obtained interaction mode is a method of invoking a service through the SBI interface, then the message filtering descriptor removal service provided by the UPF entity is called through the SBI interface to remove the UPF entity's report. Text filtering descriptor; or,

If the obtained interaction mode is the interaction mode through the PTP interface, sending a message filtering descriptor removal message to the UPF entity through the PTP interface to remove the message filtering description of the UPF entity symbol.

In a sixth aspect, an embodiment of the present application provides an NRF entity, including:

A transceiver unit, configured to receive a first request message sent by an SMF entity, where the first request message is used to request configuration information of a UPF entity that meets a condition, where the condition includes being able to provide a specified UPF service and / or being able to support a specified UPF service Interactive methods, including interactive methods through a point-to-point PTP interface, and invoking services through a serviced SBI interface for interaction;

A searching unit, configured to search at least one UPF entity that meets the condition among registered UPF entities;

The transceiver unit is further configured to send a first response message to the SMF entity, where the first response message carries configuration information of the at least one UPF entity.

Optionally, the transceiver unit is further configured to:

Receiving an NF registration request message sent by a second UPF entity, where the NF registration request message carries configuration information of the second UPF entity, where the configuration information includes services that the second UPF entity can provide and / or the first Interaction modes supported by the two UPF entities;

Storing configuration information of the second UPF entity;

Sending a NF registration response message to the second UPF entity to notify the second UPF entity that the registration is accepted.

Optionally, the NRF entity further includes a determining unit;

The determining unit is configured to determine whether the second UPF entity meets the condition;

The transceiver unit is further configured to send a NF status notification message to the SMF entity if the determination result is yes, and the NF status notification message carries the configuration information of the second UPF entity.

Fully qualified domain name FQDN of the UPF entity;

Network protocol IP address of the UPF entity;

Services that UPF entities can provide;

The interaction modes that the UPF entity can support;

The area identifier of the SMF entity that the UPF entity can serve.

In a seventh aspect, an embodiment of the present application provides an SMF entity, including:

At least one processor; and

A memory connected in communication with the at least one processor; wherein,

The memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to execute the method according to the first aspect.

In an eighth aspect, an embodiment of the present application provides an SMF entity, including:

At least one processor; and

A memory connected in communication with the at least one processor; wherein,

The memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform the method according to the second aspect.

In a ninth aspect, an embodiment of the present application provides an NRF entity, including:

At least one processor; and

A memory connected in communication with the at least one processor; wherein,

The memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform the method according to the third aspect.

According to a tenth aspect, an embodiment of the present application provides a computer storage medium. The computer storage medium stores computer instructions, and when the computer instructions are run on a computer, the computer executes the method according to the first aspect.

According to an eleventh aspect, an embodiment of the present application provides a computer storage medium. The computer storage medium stores computer instructions, and when the computer instructions are run on a computer, the computer executes the method according to the second aspect.

According to a twelfth aspect, an embodiment of the present application provides a computer storage medium. The computer storage medium stores computer instructions, and when the computer instructions are run on a computer, the computer executes the method according to the third aspect.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a network architecture diagram of a 5G communication system according to an embodiment of the present application;

2 is a schematic flowchart of a PDU session management method according to an embodiment of the present application;

3 is a schematic flowchart of an association process between nodes according to an embodiment of the present application;

4 is a schematic flowchart of a UPF discovery process according to an embodiment of the present application;

5 is a schematic flowchart of a first implementation manner of a UPF discovery process according to an embodiment of the present application;

6 is a schematic flowchart of a second implementation manner of a UPF discovery process according to an embodiment of the present application;

7 is a schematic structural diagram of an SMF entity according to an embodiment of the present application;

8 is a schematic structural diagram of another SMF entity according to an embodiment of the present application;

9 is a schematic structural diagram of an NRF entity according to an embodiment of the present application;

10 is a schematic structural diagram of an SMF entity according to an embodiment of the present application;

11 is a schematic structural diagram of an SMF entity according to an embodiment of the present application;

FIG. 12 is a schematic structural diagram of an NRF entity according to an embodiment of the present application.

detailed description

To make the objectives, technical solutions, and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application.

The technical background of the embodiments of the present application is described below.

In the current research process, it is considered to introduce the idea of service to the user plane. For example, the User Plane Function (UPF) entity also uses the SBI interface. However, the original UPF entity cannot support the SBI interface. The newly introduced UPF entity may support the SBI interface, and the original way of directly interacting through the PTP interface is obviously no longer applicable. Therefore, in a mixed deployment scenario of the UPF entity supporting the PTP interface and the UPF entity supporting the SBI interface, how to implement The interaction between the control plane entity and the UPF entity is an urgent problem.

In view of this, an embodiment of the present application provides a method for PDU session management. In this method, when or after an SMF entity selects a UPF entity that provides services for a PDU session, it will determine an interaction mode for interacting with the UPF entity, that is, The interaction is performed through the N4 interface between the original SMF entity and the UPF entity, or through the SBI interface provided by the UPF entity, and then the session is established according to the determined interaction mode to realize the interaction between the SMF entity and the UPF entity. In other words, when or after the SMF entity selects a UPF entity serving a PDU session, it needs to determine whether the UPF entity uses a PTP interface or an SBI interface. When the SMF entity determines that the UPF entity uses the PTP interface, the SMF entity can use the N4 interface to interact with the UPF entity; when the SMF entity determines that the UPF entity uses the SBI interface, the SMF can interact with the UPF entity by calling the UPF to provide services Interaction.

In this application, the method of determining the interaction with the UPF entity is to determine whether the UPF uses the PTP interface or the SBI; that is, determines whether to interact with the UPF using the PTP interface or the UPF using the SBI interface.

The technical solutions provided by the embodiments of the present application are described below with reference to the drawings.

Please refer to FIG. 2, which is a schematic flowchart of a PDU session management method provided for the implementation of this application. This method may involve an interaction process between an SMF entity, a UPF entity, and an NRF entity. Therefore, the subsequent steps performed by these entities will be described together. The specific process is described below.

Step 201: The SMF entity selects at least one UPF entity for the PDU session to be established.

In the embodiment of the present application, when a terminal has initial access, a new PDU session needs to be established for the terminal, then the SMF entity will select a Session and Service Continuity (SSC) mode for the PDU session and At least one UPF entity providing service for a PDU session, where the number of UPF entities providing service for the PDU session may be one or more.

Specifically, the SMF entity selects at least one UPF entity, and at least one UPF entity that satisfies the condition can be selected from the list of UPF entities stored by the SMF entity itself. Among them, the SMF entity stores the configuration information of each UPF entity in the UPF entity list, such as the interaction modes that the UPF entity can support or the services that the UPF entity can provide, so the SMF entity can be determined based on the configuration information of the UPF entity. Whether the UPF entity meets the conditions.

In an actual application process, the list of UPF entities stored in the SMF entity may be updated based on the UPF entities obtained during the UPF discovery process. For example, the UPF entity list stored in the SMF entity may be updated based on receiving the NF discovery response message sent by the NRF entity, that is, the UPF entity carried in the NF discovery response message may be updated into the UPF entity list. Alternatively, the list of UPF entities stored in the SMF entity may also be updated based on receiving the NF status notification message sent by the NRF entity, that is, the UPF entity carried in the NF status notification message may be updated into the UPF entity list.

Specifically, the SMF entity selects at least one UPF entity, and may also select from the UPF entities obtained during the UPF discovery process. For example, the SMF entity may select from the NF discovery response message or the UPF entity indicated in the NF status notification message fed back by the NRF entity. The NF discovery response message and the NF status notification message both carry the configuration information of the UPF entity, so the SMF entity can determine whether the UPF entity meets the conditions based on the configuration information of the UPF entity.

The UPF discovery process will be specifically described in the subsequent embodiments, and details are not described here.

Step 202: The SMF entity determines an interaction mode with the first UPF entity.

In the embodiment of the present application, if the SMF entity selects at least one UPF entity for the PDU session that needs to be created, then the SMF entity determines the interaction mode for interacting with these UPF entities. The first UPF entity is used as an example to describe the interaction. The process of determining the mode is described. The first UPF entity may be any one of the at least one UPF entity.

Specifically, based on the configuration information of the first UPF entity, the SMF entity can know the interfaces supported by the first UPF entity, and then can use which interface to interact with these UPF entities. For example, when the first UPF entity only supports the way of interacting through the SBI interface, the SMF entity may determine to interact with the first UPF entity through the SBI interface, or the first UPF entity simultaneously supports the way of interacting through the SBI interface, and through When the PTP interface performs an interaction mode, the SMF entity can select any interaction mode to interact with the first UPF entity.

The configuration information of the UPF entity may include at least one of the following information:

Fully Qualified Domain Name (FQDN) of the UPF entity;

The Internet Protocol (IP) address of the UPF entity;

The services that UPF entities can provide. Some of the services provided by UPF entities are listed in the following table. The service name is the name of the service provided by the UPF entity, and the service operation is a specific operation. For example, for a Nupf session, when the service operation is established, it is used to request the UPF entity to establish a PDU session. When the service operation is modified or released, that is, It is used to request the UPF entity to modify or release the established PDU session; the operation semantics indicate whether a message is a request message or a response message. For example, the SMF entity invokes the PDU session establishment service of the UPF entity, and sends a Nupf Session_Establishment_Request to the UPF entity. After the UPF entity establishes a session, it sends a Nupf Session_Establishment_Reponse to the SMF entity.

The interaction modes that the UPF entity can support. Among them, in order for the SMF entity to know through which interfaces it can interact with the UPF entity, the configuration information may include the interaction modes that the UPF entity can support. The interaction mode may include whether the UPF entity supports the The interaction through the PTP interface still supports the interaction through the SBI interface, or both. The interaction mode that the UPF entity can support, in other words, the interface used by the UPF entity, that is, whether the UPF entity uses the PTP interface or the UPF entity uses the SBI interface.

The list of parameters supported by the UPF entity may include, for example, single-network slice selection assistance information (S-NSSAI) and data network name (DNN).

Uniform Resource Locator (URL) of the UPF entity.

The area identifier of the SMF entity that the UPF entity can serve. For example, only the SMF is allowed to interact with the UPF entity that belongs to a specific SMF area identifier.

Specifically, the SMF entity may also determine an interaction mode with the first UPF entity based on its configuration information, wherein the configuration information of the SMF entity indicates the interaction mode supported by the SMF entity. For example, if the interaction mode configured for the SMF entity is only through the SBI interface, then when the SMF entity selects a UPF entity, it will select a UPF entity that supports the SBI interface, and the SMF entity can directly determine the first UPF entity. The interaction mode is the interaction mode through the SBI interface; or, the interaction mode configured for the SMF entity is only the interaction mode through the PTP interface, then when the SMF entity selects the UPF entity, it will select the UPF entity that supports the PTP interface. And, the SMF entity can directly determine that the interaction mode with the first UPF entity is a way of interacting through the PTP interface.

Optionally, if the SMF entity has established a node association relationship with the first UPF entity, based on the node association relationship above, the SMF entity may determine the interaction mode with the UPF entity. For details, refer to the method for performing node association between the SMF entity and the UPF entity provided in the implementation described in FIG. 3, and details are not described herein.

Step 203a: The SMF entity sends a session establishment service request message to the first UPF entity.

In the embodiment of the present application, when the SMF entity determines to interact with the first UPF entity through the SBI interface, the SMF entity sends a session establishment service request message, that is, Nupf Session_Establishment_Request, to the first UPF entity through the SBI interface to call the first UPF entity to provide A session establishment service for establishing a PDU session provided by the first UPF entity.

Step 204a: The first UPF entity sends a session establishment service response message to the SMF entity.

In the embodiment of the present application, after receiving the session establishment service request message, the first UPF entity performs corresponding processing according to the session establishment service request message, and feeds back a session establishment service response message to the SMF entity, that is, Nupf Session_Establishment_Reponse.

Step 203b: The SMF entity sends a session establishment message to the first UPF entity.

In the embodiment of the present application, when the SMF entity determines to interact with the first UPF entity through the PTP interface, the SMF entity sends a session establishment message to the first UPF entity through the PTP interface, that is, initiates an N4 session to the first UPF entity through the N4 interface. Establish a request message (N4Session EstablishmentRequest) to establish a PDU session provided by the first UPF entity in the PDU session.

Step 204b: The first UPF entity sends a session establishment response message to the SMF entity.

In the embodiment of the present application, after receiving the session establishment message, the first UPF entity will perform corresponding processing according to the session establishment message and feedback a session establishment response message to the SMF entity, that is, send an N4 session establishment to the SMF entity through the N4 interface. Response message (N4Session EstablishmentReponse).

Step 205: The SMF entity records the determined interaction mode.

In the embodiment of the present application, after determining the interaction mode with the first UPF entity, the SMF entity records the determined interaction mode so that the interaction mode can be obtained in the subsequent session management process.

Specifically, the SMF entity may record the determined interaction manner in the context of the PDU session served by the first UPF entity, or the SMF entity may also record the determined interaction manner in the context of the terminal corresponding to the PDU session.

Steps 203a and 204a are two different alternatives from steps 203b and 204b. In the specific implementation process, one of them can be executed according to the determination result of the SMF. This is similar to the subsequent session modification or release. In addition, the process of initiating the session establishment and the process of recording the interaction mode, that is, the processes of steps 203a and 204a and step 205, or the processes of steps 203b and 204b and step 205, have no substantial sequence. Therefore, in the actual process In China, these two processes can be performed one after the other, or they can be performed simultaneously.

Step 206: The SMF entity determines an interaction mode with the first UPF entity based on the interaction mode recorded in the context.

When the PDU session serviced by the first UPF entity needs to be modified or released, since the previously determined interaction mode has been recorded in the context, it is possible to interact with the first UPF entity based on the interaction mode recorded in the context.

The context may be a context of a PDU session or a context of a terminal corresponding to the PDU session.

Step 207a: The SMF entity sends a session modification service request message to the first UPF entity.

In the embodiment of the present application, when the SMF entity needs to modify the PDU session served by the first UPF entity and the SMF entity determines to interact with the first UPF entity through the SBI interface based on the context, the SMF entity sends the session to the first UPF entity through the SBI interface. Modify the service request message, ie, Nupf Session_Modification_Request, to call the session modification service provided by the first UPF entity, and modify the PDU session provided by the first UPF entity. The session modification service request message carries Access Network (AN) tunnel information and forwarding rules.

Step 208a: The first UPF entity sends a session modification service response message to the SMF entity.

In the embodiment of the present application, after receiving the session modification service request message, the first UPF entity will perform corresponding processing according to the session modification service request message, and feedback the session modification service response message to the SMF entity through the SBI interface.

Step 207b: The SMF entity sends a session modification message to the first UPF entity.

In the embodiment of the present application, when the SMF entity needs to modify the PDU session served by the first UPF entity and the SMF entity determines to interact with the first UPF entity through the PTP interface based on the context, the SMF entity sends the session to the first UPF entity through the PTP interface. The modification message, that is, the N4 session modification request message (N4Session Modification Request) is initiated to the first UPF entity through the N4 interface to modify the PDU session provided by the first UPF entity in the PDU session. The N4 session modification request message carries AN tunnel information and forwarding rules.

Step 208b: The first UPF entity sends a session modification response message to the SMF entity.

In the embodiment of the present application, after receiving the session modification message, the first UPF entity will perform corresponding processing according to the session modification message and feedback a session modification response message to the SMF entity, that is, send an N4 session modification to the SMF entity through the N4 interface. Response message (N4Session Modification Response).

Step 209a: The SMF entity sends a session release service request message to the first UPF entity.

In the embodiment of the present application, when the SMF entity needs to release the PDU session served by the first UPF entity, and when the SMF entity determines to interact with the first UPF entity through the SBI interface based on the context, the SMF entity releases the service to the first UPF entity session through the SBI interface. A request message, namely, Nupf Session_Release_Request, to call a session release service provided by the first UPF entity, and release a PDU session provided by the first UPF entity.

Step 210a: The first UPF entity sends a session release service response message to the SMF entity.

In the embodiment of the present application, after receiving the session release service request message, the first UPF entity performs corresponding processing according to the session release service request message, and feeds back the session release service response message to the SMF entity through the SBI interface.

Step 209b: The SMF entity sends a session release message to the first UPF entity.

In the embodiment of the present application, when the SMF entity needs to release the PDU session served by the first UPF entity, and when the SMF entity determines to interact with the first UPF entity through the PTP interface based on the context, the SMF entity sends a session release to the first UPF entity through the PTP interface. Message, that is, an N4 Session Release Request message (N4SessionReleaseRequest) is initiated to the first UPF entity through the N4 interface to release the PDU session provided by the first UPF entity in the PDU session.

Step 210b: The first UPF entity sends a session release response message to the SMF entity.

In the embodiment of the present application, after receiving the session release message, the first UPF entity will perform corresponding processing according to the session release message and feedback a session release response message to the SMF entity, that is, send an N4 session release to the SMF entity through the N4 interface. Response message (N4SessionReleaseReponse).

It should be stated that the above steps 207a to 210b are interactive processes based on different processes. Therefore, in the actual application process, there is no substantial sequence relationship. For example, steps 207a and 208a are the processes for modifying the PDU session. 210a is a process of releasing a PDU session. There is no sequence in the process between the two processes, so it can be performed according to specific requirements during actual execution. The processes in the subsequent technical solutions are similar and will not be described again.

Please refer to FIG. 3, which is a schematic flowchart of a method for performing node association between an SMF entity and a UPF entity provided in the implementation of this application. The specific process is described below.

Step 301: The SMF entity determines an interaction mode with the UPF entity to be associated.

In the embodiment of the present application, when the SMF entity needs to associate with the UPF entity, it needs to interact with the UPF entity to be associated, and then the SMF entity needs to determine the interaction mode for interacting with the UPF entity. Among them, the interaction methods include a method of invoking a service through an SBI interface to interact, and a method of interacting through a PTP interface.

Specifically, the SMF entity can determine the interaction mode with the UPF entity based on the configuration information of the UPF entity. The configuration mode of the UPF entity includes the interaction modes that the UPF entity can support and the services that the UPF entity can provide. See the services shown in the table in the embodiment shown in FIG. 2.

Specifically, the SMF entity may also determine the interaction mode with the UPF entity based on its own configuration information, wherein the configuration information of the SMF entity indicates the interaction mode supported by the SMF entity.

Step 302a: The SMF entity sends a node association service request message to the UPF entity.

In the embodiment of the present application, when the SMF entity determines to interact with the UPF entity through the SBI interface, the SMF entity sends a node association service request message, namely, Nupf_Node_Association_Setup_Request, to the UPF entity through the SBI interface to call the node association service provided by the UPF entity to communicate with The UPF entity performs node association.

Step 303a: the UPF entity sends a node association service response message to the SMF entity.

In the embodiment of the present application, after receiving the node association service request message, the UPF entity performs corresponding processing according to the node association service request message, and feeds back the node association service response message to the SMF entity, that is, Nupf_Node_Association_Setup_Reponse.

Step 302b: The SMF entity sends a node association message to the UPF entity.

In the embodiment of the present application, when the SMF entity determines to interact with the UPF entity through the PTP interface, the SMF entity sends a node association message to the UPF entity through the PTP interface to perform node association with the UPF entity.

Step 303b: the UPF entity sends a node association response message to the SMF entity.

In the embodiment of the present application, after receiving the node association message, the UPF entity will perform corresponding processing according to the node association message, and feedback the node association response message to the SMF entity.

Step 304: The SMF entity records the determined interaction mode.

In the embodiment of the present application, after the SMF entity determines the interaction mode with the UPF entity, it records the determined interaction mode so that the interaction mode can be obtained in the subsequent session management process. For example, define a new node association context, and record the determined interaction mode in the node association context.

Steps 302a and 303a are two different options from steps 302b and 303b. In the specific implementation process, one of them can be executed according to the determination result of the SMF. The subsequent sessions are modified or released similarly, and will not be described in detail later. In addition, the process of initiating node association and the process of recording interaction modes, that is, the processes of steps 302a and 303a and step 304, or the processes of steps 302b and 303b and step 304, have no substantial sequence. Therefore, in the actual process In China, these two processes can be performed one after the other, or they can be performed simultaneously.

Step 305: The SMF entity determines the interaction mode with the UPF entity based on the interaction mode recorded in the node association context.

Since the previously determined interaction mode has been recorded in the node association context, it is possible to interact with the UPF entity based on the interaction mode recorded in the node association context in the subsequent interaction process. For example, when the configuration information of the UPF entity needs to be updated, or the node association relationship with the UPF entity is released, or the message filtering descriptor of the UPF entity needs to be configured, or the message filtering descriptor of the UPF entity is removed, Interact with UPF entities based on interactions recorded in the context of the node association.

Step 306a: The SMF entity sends a node update service request message to the UPF entity.

In the embodiment of the present application, when the configuration information of the UPF entity needs to be updated and the SMF entity determines to interact with the UPF entity through the SBI interface based on the node association context, the SMF entity sends a node association service request message to the UPF entity through the SBI interface, that is, Nupf_Node_Association_Update_Request To call the node association service provided by the UPF entity to update the configuration information of the UPF entity. The node association service request message carries configuration information that needs to be updated.

Step 307a: The UPF entity sends a node update service response message to the SMF entity.

In the embodiment of the present application, after receiving the node update service request message, the UPF entity will perform corresponding processing according to the node update service request message, and feedback the node update service response message to the SMF entity through the SBI interface, that is, Nupf_Node_Association_Update_Reponse.

Step 306b: The SMF entity sends a node update message to the UPF entity.

In the embodiment of the present application, when the configuration information of the UPF entity needs to be updated and the SMF entity determines to interact with the UPF entity through the PTP interface based on the node association context, the SMF entity sends a node update message to the UPF entity through the PTP interface, that is, through N4 The interface sends a node update message to the UPF entity to update the configuration information of the UPF entity. The node update message carries configuration information that needs to be updated.

Step 307b: The UPF entity sends a node update response message to the SMF entity.

In the embodiment of the present application, after receiving the node update message, the UPF entity will perform corresponding processing according to the node update message and feedback the node update response message to the SMF entity, that is, send the node update response message to the SMF entity through the N4 interface.

Step 308a: The SMF entity sends a node release service request message to the UPF entity.

In the embodiment of the present application, when the SMF entity needs to release the node association relationship with the UPF entity, and the SMF entity determines to interact with the UPF entity through the SBI interface based on the node association context, the SMF entity releases the service to the UPF entity node through the SBI interface. A request message, that is, Nupf_Node_Association_Release_Request, to call a node release service provided by a UPF entity, and release a PDU session provided by the UPF entity.

Step 309a: The UPF entity sends a node release service response message to the SMF entity.

In the embodiment of the present application, after receiving the node release service request message, the UPF entity will perform corresponding processing according to the node release service request message, and feedback the node release service response message to the SMF entity through the SBI interface, that is, Nupf_Node_Association_Release_Reponse.

Step 308b: The SMF entity sends a node release message to the UPF entity.

In the embodiment of the present application, when the SMF entity releases the node association relationship with the UPF entity and the SMF entity determines to interact with the UPF entity through the PTP interface based on the node association context, the SMF entity sends a node release message to the UPF entity through the PTP interface. That is, the N4 node release message is initiated to the UPF entity through the N4 interface to release the PDU session provided by the UPF entity in the PDU session.

Step 309b: The UPF entity sends a node release response message to the SMF entity.

In the embodiment of the present application, after receiving the session node release message, the UPF entity will perform corresponding processing according to the node release message and feedback the node release response message to the SMF entity, that is, send the node release response message to the SMF entity through the N4 interface. .

Step 310a: the SMF entity sends a message filtering descriptor providing service request message to the UPF entity.

In the embodiment of the present application, when the SMF entity needs to configure the message filtering descriptor of the UPF entity and the SMF entity determines to interact with the UPF entity through the SBI interface based on the node association context, the SMF entity filters the message filtering descriptor to the UPF entity through the SBI interface. Provide a service request message, that is, Nupf_PFD_Mgt_Provision_Request, to call the message filtering descriptor provided by the UPF entity to provide services, and configure the message filtering descriptor for the UPF entity.

Step 311a: the UPF entity sends a message filtering descriptor providing service response message to the SMF entity.

In the embodiment of the present application, after receiving the message filtering descriptor providing service request message, the UPF entity will perform corresponding processing according to the message filtering descriptor providing service request message, and feedback the message filtering description to the SMF entity through the SBI interface. The identifier provides a service response message, which is Nupf_PFD_Mgt_Provision_Reponse.

Step 310b: The SMF entity sends a message filtering descriptor providing message to the UPF entity.

In the embodiment of the present application, the SMF entity needs to configure a message filtering descriptor of the UPF entity, and when the SMF entity determines to interact with the UPF entity through the PTP interface based on the node association context, the SMF entity sends a message filtering description to the UPF entity through the PTP interface. To provide a message, that is, to initiate a N4 message filtering descriptor providing message to the UPF entity through the N4 interface to configure a message filtering descriptor for the UPF entity.

Step 311b: The UPF entity sends a message filtering descriptor providing response message to the SMF entity.

In the embodiment of the present application, after receiving the session message filtering descriptor providing message, the UPF entity will process the message according to the message filtering descriptor providing message and feedback the message filtering descriptor providing a response message to the SMF entity. It is to send a message filtering descriptor to the SMF entity through the N4 interface to provide a response message.

Step 312a: The SMF entity sends a message filtering descriptor removal service request message to the UPF entity.

In the embodiment of the present application, when the SMF entity needs to remove the message filtering descriptor (PFD) of the UPF entity, and the SMF entity determines to interact with the UPF entity through the SBI interface based on the node association context, the SMF entity reports to the UPF entity through the SBI interface. The message filtering descriptor removal service request message, that is, Nupf_PFD_Mgt_Remove_Request, calls the message filtering descriptor removal service provided by the UPF entity to remove the message filtering descriptor that has been configured for the UPF entity.

Step 313a: The UPF entity sends a message filtering descriptor removal service response message to the SMF entity.

In the embodiment of the present application, after receiving the message filtering descriptor removal service request message, the UPF entity will perform corresponding processing according to the message filtering descriptor removal service request message, and feedback the message to the SMF entity through the SBI interface. The filter descriptor removes the service response message, which is Nupf_PFD_Mgt_Remove_Reponse.

Step 312b: The SMF entity sends a message filtering descriptor removal message to the UPF entity.

In the embodiment of the present application, when the SMF entity needs to remove the message filtering descriptor of the UPF entity and the SMF entity determines to interact with the UPF entity through the PTP interface based on the node association context, the SMF entity sends a message filtering to the UPF entity through the PTP interface. The descriptor removal message, that is, the N4 message filtering descriptor removal message is initiated to the UPF entity through the N4 interface to remove the message filtering descriptor that has been configured for the UPF entity.

Step 313b: the UPF entity sends a message filtering descriptor removal response message to the SMF entity.

In the embodiment of the present application, after the UPF entity receives the session message filtering descriptor removal message, it will perform corresponding processing according to the message filtering descriptor removal message, and feedback the message filtering descriptor removal response to the SMF entity. The message, that is, the message filtering descriptor removal response message is sent to the SMF entity through the N4 interface.

It should be noted that the related process of the node association relationship described in the embodiment shown in FIG. 3, such as the establishment of the node association relationship, usually occurs before the PDU session establishment process. Therefore, the interaction mode of the UPF entity recorded in the context of node association can be used by the SMF entity to determine the interaction mode with the UPF entity during the establishment of the PDU session.

Please refer to FIG. 4, which is a schematic flowchart of a UPF discovery process according to an embodiment of the present application.

Step 401: The SMF entity sends a first request message to the NRF entity, and the SMF entity receives the first request message.

In the embodiment of the present application, when the SMF entity wants to find a UPF entity available in the network, it may send a first request message to the SMF, the first request message is used to request to obtain configuration information of a UPF entity that meets a condition, and the condition may It includes that the UPF entity can provide the specified UPF service, and / or the UPF entity can support the specified interaction mode.

Optionally, the UPF entity supporting the SBI interface and the UPF entity supporting the PTP interface can be divided into two different types. For example, the UPF entity supporting the SBI interface can be the first type, and the UPF entity supporting the PTP interface can be the second type. , Then the above condition may also be that the UPF entity is a specified type.

Specifically, the interaction method may include a method of interacting through a PTP interface between the SMF entity and the UPF entity, that is, an N4 interface, and a method of invoking a service provided by the UPF entity through the SBI interface between the SMF entity and the UPF entity to interact. . Then, the interaction method specified above may be a method capable of supporting a PTP interface for interaction, or a method capable of supporting an SBI interface for interaction, or a manner of supporting both a PTP interface and an SBI interface for interaction.

Step 402: The NRF entity searches among the registered UPF entities for at least one UPF entity that meets the conditions.

In the embodiment of the present application, after receiving the first request message, the NRF entity searches for the registered UPF entity stored in itself to find at least one UPF entity that meets the conditions required by the SMF.

Specifically, before the NRF entity performs a search, the NRF entity also performs authorization verification on the SMF entity. It has been verified whether to provide the SMF entity with a qualified UPF entity. Since the authorization verification process belongs to the scope of the existing technology, This will not be repeated here.

Step 403: The NRF entity sends a first response message to the SMF entity, and the SMF entity receives the first response message.

In the embodiment of the present application, after the NRF entity finds at least one UPF entity that meets the above conditions, it sends a first response message to the SMF entity that carries the configuration information of the at least one UPF entity, so as to send the configuration information of the at least one UPF entity. Sent to the SMF entity.

Step 404: The SMF entity updates its list of UPF entities stored based on the first response message.

In a specific implementation process, the foregoing steps 401 to 403 may include the following two implementation manners.

Please refer to FIG. 5, which is a first implementation manner of steps 401 to 403, where steps 501 to 503 and steps 401 to 403 correspond one by one in sequence.

Step 501: The SMF entity sends a Network Function (NF) discovery request message to the SMF entity, and the SMF entity receives the NF discovery request message.

In the embodiment of the present application, the first request message may be a NF discovery request message. As a service-oriented architecture has been adopted on the control plane, the SMF entity can use the SBI interface between the SMF entity and the NRF entity to invoke the NF discovery service provided by the NRF entity, namely Nnrf_NFDiscovery_Request, to realize the discovery of the UPF entity.

Among them, the Nnrf_NFDiscovery_Request can carry the desired NF service name, NF entity type, and its own type. Specifically, the NF service name here is the UPF service, the NF entity type is the UPF entity here, and its own type is the SMF entity. . Of course, the Nnrf_NFDiscovery_Request can also carry the conditions that the UPF entity that the SMF entity wants to find needs to meet, that is, it can provide the specified UPF service, and / or it can support the specified interaction mode.

Step 502: The NRF entity searches among the registered UPF entities for at least one UPF entity that meets the conditions.

Step 503: The NRF entity sends an NF discovery response message to the SMF entity, and the SMF entity receives the NF discovery response message.

In the embodiment of the present application, the first response message may be a NF discovery response message. Specifically, the NRF entity may call a response service corresponding to the NF discovery service, that is, Nnrf_NFDiscovery_RequestResponse, to feed back the configuration information of at least one UPF entity that meets the conditions to the UPF entity.

For example, if the NF discovery request message invoked by the SMF entity is used to request to obtain a UPF entity that supports the SBI interface, the configuration information of the UPF entity included in the NF discovery response message fed back by the NRF entity is in addition to the FQDN that is normally provided. In addition to the IP address, and URL, it also carries the interaction methods that these UPF entities can support and the services that can be provided to the SMF entity.

Step 504: The SMF entity updates its list of UPF entities stored based on the NF discovery response message.

After receiving the NF discovery response message, the SMF entity updates the UPF entity indicated in the NF discovery response message and the corresponding configuration information to the UPF entity list stored by itself.

Please refer to FIG. 6, which is a second implementation manner of steps 401 to 403, where steps 601 to 603 and steps 401 to 403 correspond one by one in sequence.

Step 601: The SMF entity sends an NF status subscription message to the SMF entity, and the SMF entity receives the NF status subscription message.

In the embodiment of the present application, the first request message may be a NF status subscription message. Specifically, the SMF entity can use the SBI interface between the SMF entity and the NRF entity to call the NF status subscription service provided by the NRF entity, that is, Nnrf_NFDiscovery_NFStatusSubscribe, to subscribe to the UPF entity that meets the conditions. Specifically, the subscription means that after the NRF entity receives the NF status subscription message, it will send the configuration information of the currently registered UPF entity that meets the conditions to the SMF entity, and register with a new UPF entity, and the UPF When the entity meets the above conditions, the NRF entity will also actively send the configuration information of the UPF entity to the SMF entity.

Among them, the Nnrf_NFDiscovery_NFStatusSubscribe can also carry the desired NF service name, NF entity type, and its own type. Specifically, the NF service name here is the UPF service, the NF entity type is the UPF entity, and its own type is SMF entity. Of course, the Nnrf_NFDiscovery_Request can also carry the conditions that the UPF entity that the SMF entity wants to find needs to meet, that is, it can provide the specified UPF service, and / or it can support the specified interaction mode.

Step 602: The NRF entity searches among the registered UPF entities for at least one UPF entity that meets the conditions.

Step 603: The NRF entity sends an NF status notification message to the SMF entity, and the SMF entity receives the NF status notification message.

In the embodiment of the present application, the first response message may be an NF status notification message. Specifically, the NRF entity can call its own NF status notification service, that is, Nnrf_NFDiscoveryNFStatusNotify, to notify the UPF entity of the configuration information of at least one UPF entity that meets the conditions.

For example, if the SMF entity does not clearly indicate the required interface capabilities when subscribing, then the UPF entity in at least one UPF entity provided in the Nnrf_NFManagement_NFStatusNotify may include a UPF entity supporting an SBI interface or a UPF entity supporting a PTP interface. Of course, the interfaces that the UPF entity can support and the services that it can provide need to be clearly indicated in Nnrf_NFManagement_NFStatusNotify.

Step 604: The second UPF entity sends a NF registration request message to the NRF entity, and the NRF entity receives the NF registration request message.

In the embodiment of the present application, after a new UPF entity is deployed, that is, a second UPF entity, the second UPF entity needs to register with the NRF, and then the second UPF entity may send a NF registration request message to the NRF entity. The NF registration request message can carry the configuration information of the second UPF entity. For example, in addition to the FQDN or IP address of the second UPF entity, it can also include the interaction modes that the second UPF entity can support, and can provide Services.

For example, if the second UPF entity supports the SBI interface, the second UPF entity can call the Nnrf_NFManagement_NFRegister Request of the NRF entity to notify the NRF entity of its configuration information.

Step 605: The NRF entity stores the configuration information of the second UPF entity.

Step 606: The NRF entity sends a NF registration response message to the second UPF entity.

In the embodiment of the present application, the NRF entity stores the configuration information of the second UPF entity carried in the NF registration request message, and feeds back a NF registration response message to the second UPF entity, where the NF registration response message is used to notify that the registration of the second UPF entity has been completed. Accepted by the NRF entity, that is, the registration was successful. Of course, when there is a problem with the registration of the second UPF, the NRF entity also sends a NF registration response message to the second UPF entity, and then the NF registration response message is used to notify the second UPF entity of the registration failure and the reason for the failure.

Following the example in which the second UPF entity supports the SBI interface, when the NRF entity feeds back the NF registration response message to the second UPF entity, it can also call its own Nnrf_NFManagement_NF Register response to notify the NRF entity of the registration result.

Step 607: The NRF entity determines whether the second UPF entity meets the foregoing conditions.

Step 608: When the determination result in step 607 is yes, the NRF entity sends an NF status notification message to the SMF entity, and the SMF entity receives the NF status notification message.

In the embodiment of the present application, after the second UPF entity is successfully registered, the NRF entity will determine whether the second UPF entity meets the conditions in the NF status subscription message. If it is satisfied, the NRF entity will also send an NF status notification to the SMF entity. Message, and the configuration information of the second UPF entity is carried in the NF status notification message.

For example, the SMF entity instructs the subscription to a UPF entity that supports the SBI interface when subscribing, or if the SMF entity does not explicitly indicate the required interface capabilities when subscribing, the NRF entity will determine that the configuration information of the second UPF entity meets the above SMF entity's For the condition of the subscription, the NRF entity will call its own Nnrf_NFManagement_NFStatusNotify to send the configuration information of the second UPF entity to the SMF entity.

Step 609: The SMF entity updates its list of UPF entities stored based on the NF status notification message.

After receiving the NF status notification message, the SMF entity updates the UPF entity indicated in the NF status notification message and the corresponding configuration information to the UPF entity list stored by itself. For example, the SMF entity may update the configuration information of the second UPF entity and the second UPF entity into the list of UPF entities stored by itself.

Referring to FIG. 7, based on the same inventive concept, an embodiment of the present application provides an SMF entity, including:

A selecting unit 701, configured to select at least one user plane function UPF entity for a PDU session to be established;

A determining unit 702 is configured to determine an interaction mode for interacting with the first UPF entity for the first UPF entity in the at least one UPF entity; wherein the configuration information of a UPF entity includes an interaction mode supported by the UPF entity. The methods include a method of interacting through a point-to-point PTP interface, and a method of invoking a service through a serviced SBI interface to interact;

The execution unit 703 is configured to call a session establishment service provided by the first UPF entity through the SBI interface when determining to interact with the first UPF entity through the SBI interface, so as to establish a PDU session provided by the first UPF entity in the PDU session; Alternatively, when determining to interact with the first UPF entity through the PTP interface, a session establishment message is sent to the first UPF entity through the PTP interface to establish a PDU session provided by the first UPF entity in the PDU session.

Optionally, the selection unit 701 is specifically configured to:

According to the list of UPF entities stored in the SMF entity and the configuration information of the UPF entities in the list, at least one UPF entity that meets the conditions is selected from the list, and the conditions include being able to provide the specified UPF service and / or being able to support the specified interaction mode.

Optionally, the SMF entity further includes an update unit 704;

The execution unit 703 is further configured to send an NF status subscription message to the NRF entity. The NF status subscription message is used to subscribe to a UPF entity that meets a condition, and the condition includes being able to provide a specified UPF service and / or supporting a specified interaction mode; and, receiving An NF status notification message sent by the NRF entity, and the NF status notification message carries configuration information of at least one UPF entity that already exists or is newly added in the NRF entity that meets the conditions;

The updating unit 704 is configured to update the list of UPF entities stored in the SMF entity according to the NF status notification message.

Optionally, the selection unit 701 is specifically configured to:

Send a NF discovery request message to the NRF entity. The NF discovery request message is used to request the NRF entity to provide a UPF entity that meets the conditions, and the conditions include being able to provide the specified UPF service and / or being able to support the specified interaction mode;

Receive the NF discovery response message sent by the NRF entity, and the NF discovery response message carries the configuration information of the UPF entity that meets the conditions;

At least one UPF entity is selected from the UPF entities that meet the conditions.

Optionally, the determining unit 702 is specifically configured to:

Determining the interaction mode for interacting with the first UPF entity based on the configuration information of the SMF entity, wherein the configuration information of the SMF entity indicates the interaction mode supported by the SMF entity; or,

Based on the node association context, an interaction mode for interacting with the first UPF entity is determined. The node association context indicates an interaction mode determined by the SMF entity to interact with the first UPF entity.

Fully qualified domain name FQDN of the UPF entity;

Network protocol IP address of the UPF entity;

Services that UPF entities can provide;

The interaction modes that the UPF entity can support;

The area identifier of the SMF entity that the UPF entity can serve.

Optionally, the execution unit 703 is further configured to:

Record the determined interaction manner in the context of the PDU session served by the first UPF entity; or

Optionally, the execution unit 703 is further configured to:

When the PDU session served by the first UPF entity needs to be modified, the interaction mode with the first UPF entity recorded in the context is obtained; the context is the context of the PDU session or the context of the terminal corresponding to the PDU session;

If the obtained interaction mode is a method of invoking a service through the SBI interface, then call the session modification service provided by the first UPF entity through the SBI interface to modify the PDU session served by the first UPF entity; or,

If the obtained interaction mode is an interaction mode through a PTP interface, a session modification message is sent to the first UPF entity through the PTP interface to modify the PDU session served by the first UPF entity.

Optionally, the execution unit 703 is further configured to:

When the PDU session served by the first UPF entity needs to be released, the interaction mode with the first UPF entity recorded in the context is acquired; the context is the context of the PDU session or the context of the terminal corresponding to the PDU session;

If the acquired interaction mode is a method of invoking a service through the SBI interface, then the session release service provided by the first UPF entity is called through the SBI interface to release the PDU session served by the first UPF entity; or,

If the obtained interaction mode is an interaction mode through a PTP interface, a session release message is sent to the first UPF entity through the PTP interface to release the PDU session served by the first UPF entity.

The SMF entity can be used to perform the steps performed by the SMF entity in the embodiment shown in FIG. 2-6. Therefore, for the functions that can be implemented by each functional module of the entity, refer to the embodiment shown in FIG. 2-6. The description is not redundant. The updating unit 704 is shown in FIG. 7 together, but it is not a required functional unit, and therefore is shown by a dotted line.

Referring to FIG. 8, based on the same inventive concept, an embodiment of the present application provides an SMF entity, including:

A determining unit 801, configured to determine an interaction mode with a UPF entity to be associated, and the interaction modes include a method of interacting through a PTP interface, and a method of invoking a service through an SBI interface to interact;

An execution unit 802 is configured to, when the SMF entity determines to interact with the UPF entity through the SBI interface, invoke the node association service provided by the UPF entity through the SBI interface to perform node association with the UPF entity; and, when the SMF entity determines to communicate with the UPF entity through the PTP interface, When the UPF entity interacts, the SMF entity sends a node association message to the UPF entity through the PTP interface to perform node association with the UPF entity.

Optionally, the determining unit 801 is specifically configured to:

Determine the interaction mode for interacting with the first UPF entity based on the configuration information of the UPF entity, or

Based on the configuration information of the SMF entity, an interaction mode for interacting with the UPF entity is determined. The configuration information of the SMF entity indicates the interaction mode supported by the SMF entity.

Optionally, the SMF entity further includes a recording unit 803, configured to:

Record the determined interaction with the UPF entity in the context of the node association.

Optionally, the execution unit 802 is further configured to:

When the configuration information of the UPF entity needs to be updated, the interaction mode with the UPF entity recorded in the node association context is obtained;

If the obtained interaction mode is a method of invoking a service through the SBI interface, the node update service provided by the UPF entity is called through the SBI interface to update the configuration information of the UPF entity; or,

If the obtained interaction mode is an interaction mode through a PTP interface, a node update message is sent to the UPF entity through the PTP interface to update the configuration information of the UPF entity.

Optionally, the execution unit 802 is further configured to:

When it is necessary to cancel the node association relationship with the UPF entity, obtain the interaction mode with the UPF entity recorded in the node association context;

If the obtained interaction mode is a method of invoking a service through the SBI interface, then the node release service provided by the UPF entity is called through the SBI interface to release the node association relationship with the UPF entity; or,

If the obtained interaction mode is an interaction mode through a PTP interface, a node release message is sent to the UPF entity through the PTP interface to release the node association relationship with the UPF entity.

Optionally, the execution unit 802 is further configured to:

When the message filtering descriptor of the UPF entity needs to be configured, obtain the interaction mode with the UPF entity recorded in the node association context;

If the obtained interaction mode is a method of invoking a service through the SBI interface, then the SBI interface is used to invoke the message filtering descriptor provided by the UPF entity to provide services to configure the message filtering descriptor of the UPF entity; or

If the obtained interaction mode is an interaction mode through a PTP interface, a message filtering descriptor is provided to the UPF entity through the PTP interface to configure a message filtering descriptor of the UPF entity.

Optionally, the execution unit 802 is further configured to:

When the message filtering descriptor of the UPF entity needs to be removed, obtain the interaction mode with the UPF entity recorded in the node association context;

If the obtained interaction mode is a method of invoking a service through the SBI interface, then the message filtering descriptor removal service provided by the UPF entity is called through the SBI interface to remove the message filtering descriptor of the UPF entity; or,

If the obtained interaction mode is the interaction mode through the PTP interface, the message filtering descriptor removal message is sent to the UPF entity through the PTP interface to remove the message filtering descriptor of the UPF entity.

The SMF entity can be used to perform the steps performed by the NRF entity in the embodiment shown in FIG. 2-6. Therefore, for the functions that can be implemented by the functional modules of the entity, refer to the embodiment shown in FIG. 2-6. The description is not redundant. Among them, the determining unit 803 is shown in FIG. 8 together, but it is not a required functional unit, and therefore is shown by a dotted line.

Referring to FIG. 9, based on the same inventive concept, an embodiment of the present application provides an NRF entity, including:

The transceiver unit 901 is configured to receive a first request message sent by the SMF entity. The first request message is used to request configuration information of a UPF entity that meets a condition, and the condition includes being able to provide a specified UPF service and / or supporting a specified interaction mode. The interaction methods include a method of interacting through a point-to-point PTP interface, and a method of invoking a service through a serviced SBI interface for interaction;

A searching unit 902, configured to search at least one UPF entity that meets a condition among registered UPF entities;

The transceiver unit 901 is further configured to send a first response message to the SMF entity, where the first response message carries configuration information of at least one UPF entity.

Optionally, the first request message is a NF status subscription message, the NF status subscription message is used to subscribe to a UPF entity that meets the conditions, and the first response message is a NF status notification message.

Optionally, the transceiver unit 901 is further configured to:

Receiving a NF registration request message sent by a second UPF entity, the NF registration request message carries configuration information of the second UPF entity, and the configuration information includes services that the second UPF entity can provide and / or an interaction mode that the second UPF entity can support;

Storing configuration information of the second UPF entity;

Send a NF registration response message to the second UPF entity to notify the second UPF entity that the registration is accepted.

Optionally, the NRF entity further includes a determining unit 903;

A determining unit 903, configured to determine whether a second UPF entity meets a condition;

The transceiver unit 901 is further configured to send an NF status notification message to the SMF entity if the determination result is yes, and the NF status notification message carries the configuration information of the second UPF entity.

Fully qualified domain name FQDN of the UPF entity;

Network protocol IP address of the UPF entity;

Services that UPF entities can provide;

The interaction modes that the UPF entity can support;

The area identifier of the SMF entity that the UPF entity can serve.

The SMF entity can be used to perform the steps performed by the NRF entity in the embodiment shown in FIG. 2-6. Therefore, for the functions that can be implemented by the functional modules of the entity, refer to the embodiment shown in FIG. 2-6. The description is not redundant. The determining unit 903 is shown in FIG. 9 together, but it is not a required functional unit, and therefore is shown by a dotted line.

Based on the same inventive concept, as shown in FIG. 10, an embodiment of the present application provides an SMF entity, including:

At least one processor 1001, and

A memory 1002 that is communicatively connected to the at least one processor 1001;

The memory 1002 stores instructions executable by the at least one processor 1001, and the instructions execute the following processes by the at least one processor 1001:

Selecting at least one user plane function UPF entity for the PDU session to be established;

For the first UPF entity in the at least one UPF entity, determining an interaction manner for interacting with the first UPF entity; wherein configuration information of a UPF entity includes an interaction manner supported by the one UPF entity, so The interaction methods include a method of interacting through a point-to-point PTP interface, and a method of invoking a service through a serviced SBI interface for interaction;

When determining to interact with the first UPF entity through the SBI interface, call the session establishment service provided by the first UPF entity through the SBI interface to establish the first UPF entity in the PDU session The serving PDU session; or

When determining to interact with the first UPF entity through the PTP interface, send a session establishment message to the first UPF entity through the PTP interface to establish the PDU session provided by the first UPF entity Serviced PDU session.

Optionally, the at least one processor 1001 is specifically configured to:

According to the list of UPF entities stored by the SMF entity itself and the configuration information of the UPF entities in the list, the at least one UPF entity that satisfies a condition is selected from the list, and the condition includes the ability to provide a specified UPF service and / Or able to support the specified interaction method.

Optionally, the at least one processor 1001 is further configured to:

Sending an NF status subscription message to the NRF entity, where the NF status subscription message is used to subscribe to a UPF entity that meets a condition, the condition including being able to provide a specified UPF service and / or being able to support a specified interaction mode;

Receiving an NF status notification message sent by the NRF entity, where the NF status notification message carries configuration information of at least one UPF entity that already exists or is newly added in the NRF entity that meets the condition;

Update the UPF entity list stored by itself according to the NF status notification message.

Optionally, the at least one processor 1001 is specifically configured to:

Determining an interaction manner for interacting with the first UPF entity based on the configuration information of the first UPF entity; or

Determining an interaction mode for interacting with the first UPF entity based on its own configuration information, wherein the configuration information of the SMF entity itself indicates the interaction mode supported by the SMF entity; or,

Fully qualified domain name FQDN of the UPF entity;

Network protocol IP address of the UPF entity;

Services that UPF entities can provide;

The interaction modes that the UPF entity can support;

The area identifier of the SMF entity that the UPF entity can serve.

Optionally, the at least one processor 1001 is further configured to:

Optionally, at least one processor 1001 may specifically include a central processing unit (CPU), an application specific integrated circuit (ASIC), may be one or more integrated circuits for controlling program execution, and may be used The hardware circuit developed by Field Programmable Gate Array (FPGA) can be a baseband processor.

Optionally, the at least one processor 1001 may include at least one processing core.

Optionally, the SMF entity further includes a memory 1002, and the memory 1002 may include a read-only memory (Read Only Memory, ROM), a random access memory (Random Access Memory, RAM), and a disk memory. The memory 1002 is configured to store data required by the at least one processor 1001 during operation. The number of memories 1002 is one or more. Among them, the memory 1002 is shown in FIG. 10 together, but it needs to be known that the memory 1002 is not a required functional module, so it is shown with a dashed line in FIG. 10.

Based on the same inventive concept, as shown in FIG. 11, an embodiment of the present application provides an SMF entity, including:

At least one processor 1101, and

A memory 1102 that is communicatively connected to the at least one processor 1101;

The memory 1102 stores instructions executable by the at least one processor 1101, and the instructions execute the following processes by the at least one processor 1101:

Determining the interaction mode with the UPF entity to be associated, the interaction mode includes a way of interacting through a PTP interface, and a way of invoking a service through an SBI interface to interact;

When determining to interact with the UPF entity through the SBI interface, calling the node association service provided by the UPF entity through the SBI interface to perform node association with the UPF entity;

When determining to interact with the UPF entity through the PTP interface, a node association message is sent to the UPF entity through the PTP interface to perform node association with the UPF entity.

Optionally, the at least one processor 1101 is specifically configured to:

An interaction mode for interacting with the UPF entity is determined based on its own configuration information, wherein the configuration information of the SMF entity itself indicates the interaction mode supported by the SMF entity.

Optionally, the at least one processor 1101 is further configured to:

If the obtained interaction mode is a method for invoking a service through the SBI interface, then the SBI interface is used to call a message filtering descriptor provided by the UPF entity to provide services to configure the message filtering of the UPF entity Descriptor; or,

Optionally, the at least one processor 1101 is further configured to:

Optionally, the at least one processor 1101 may specifically include a central processing unit (CPU), an application-specific integrated circuit (ASIC), may be one or more integrated circuits for controlling program execution, or may use a field programmable gate array The hardware circuit developed by (FPGA) can be a baseband processor.

Optionally, the at least one processor 1101 may include at least one processing core.

Optionally, the SMF entity further includes a memory 1102. The memory 1102 may include a read-only memory (ROM), a random access memory (RAM), and a magnetic disk memory. The memory 1102 is configured to store data required by the at least one processor 1101 during operation. The number of the memories 1102 is one or more. Among them, the memory 1102 is shown in FIG. 11 together, but it needs to be known that the memory 1102 is not a required functional module, so it is shown with a dashed line in FIG. 11.

Based on the same inventive concept, as shown in FIG. 12, an embodiment of the present application further provides an NRF entity, including:

At least one processor 1201, and

A memory 1202 that is communicatively connected to the at least one processor 1201;

The memory 1202 stores instructions executable by the at least one processor 1201, and the instructions execute the following processes by the at least one processor 1201:

Receive a first request message sent by an SMF entity, the first request message is used to request to obtain configuration information of a UPF entity that meets a condition, where the condition includes the ability to provide a specified UPF service and / or support a specified interaction mode The interaction methods include a method of interacting through a point-to-point PTP interface, and a method of invoking a service through a serviced SBI interface for interaction;

Find at least one UPF entity that meets the conditions among registered UPF entities;

Sending a first response message to the SMF entity, where the first response message carries configuration information of the at least one UPF entity.

Optionally, the at least one processor 1201 is further configured to:

Storing configuration information of the second UPF entity;

Optionally, the at least one processor 1201 is further configured to:

Determining whether the second UPF entity meets the condition;

If the determination result is yes, send an NF status notification message to the SMF entity, where the NF status notification message carries the configuration information of the second UPF entity.

Fully qualified domain name FQDN of the UPF entity;

Network protocol IP address of the UPF entity;

Services that UPF entities can provide;

The interaction modes that the UPF entity can support;

The area identifier of the SMF entity that the UPF entity can serve.

Optionally, the at least one processor 1201 may specifically include a central processing unit (CPU), an application specific integrated circuit (ASIC), may be one or more integrated circuits for controlling program execution, and may be a field programmable gate array The hardware circuit developed by (FPGA) can be a baseband processor.

Optionally, the at least one processor 1201 may include at least one processing core.

Optionally, the NRF entity further includes a memory 1202, and the memory 1202 may include a read-only memory (ROM), a random access memory (RAM), and a magnetic disk memory. The memory 1202 is configured to store data required by the at least one processor 1201 during operation. The number of the memories 1202 is one or more. Among them, the memory 1202 is shown in FIG. 12 together, but it needs to be known that the memory 1202 is not a required functional module, so it is shown with a dashed line in FIG. 12.

Based on the same inventive concept, an embodiment of the present application provides a computer storage medium, where the computer storage medium stores computer instructions, and when the computer instructions are run on a computer, the computer executes the embodiments shown in FIG. 2-6 Provided methods.

In the specific implementation process, the computer storage medium includes: universal serial bus flash disk (Universal Serial Bus flash drive (USB), mobile hard disk, read only memory (Read Only Memory, ROM), random access memory (Random Access Memory) , RAM), magnetic disks or optical disks and other storage media that can store program code.

In the embodiments of the present application, it should be understood that the disclosed entities and methods may be implemented in other ways. For example, the physical embodiments described above are only schematic. For example, the division of the unit or unit is only a logical function division. In actual implementation, there may be another division manner, such as multiple units or components. The combination can either be integrated into another system, or some features can be ignored or not implemented. In addition, the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or entities or units, and may be electrical or other forms.

Each functional unit in the embodiment of the present application may be integrated into one processing unit, or each unit may also be an independent physical module.

When the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it may be stored in a computer-readable storage medium. Based on such an understanding, all or part of the technical solutions in the embodiments of the present application may be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for making a computer device, for example, may be A personal computer, a server, or a network device, or a processor executes all or part of the steps of the method described in each embodiment of the present application. The foregoing storage medium includes: a universal serial bus flash disk (Universal Serial Bus flash drive, USB), a mobile hard disk, a ROM, a RAM, a magnetic disk, or an optical disk, and other media that can store program codes.

As mentioned above, the above embodiments are only used to introduce the technical solution of the present application in detail, but the description of the above embodiments is only used to help understand the methods of the embodiments of the present application, and should not be construed as limiting the embodiments of the present application. Changes or substitutions that can be easily conceived by those skilled in the art should be covered within the protection scope of the embodiments of the present application.

Claims

A packet data unit PDU session management method is characterized in that it includes:

The session management function SMF entity selects at least one user plane function UPF entity for the PDU session to be established;

For the first UPF entity in the at least one UPF entity, the SMF entity determines an interaction mode for interacting with the first UPF entity; wherein configuration information of a UPF entity includes information supported by the one UPF entity An interactive manner, which includes a manner of interacting through a point-to-point PTP interface, and a manner of invoking a service through a serviced SBI interface for interaction;

When the SMF entity determines to interact with the first UPF entity through the SBI interface, the SMF entity invokes a session establishment service provided by the first UPF entity through the SBI interface to establish the PDU session A PDU session provided by the first UPF entity; or

When the SMF entity determines to interact with the first UPF entity through the PTP interface, the SMF entity sends a session establishment message to the first UPF entity through the PTP interface to establish the PDU session. A PDU session served by the first UPF entity.
The method according to claim 1, wherein the SMF entity selecting at least one UPF entity for a PDU session to be established comprises:

According to the list of UPF entities stored by the SMF entity itself and the configuration information of the UPF entities in the list, the SMF entity selects from the list the at least one UPF entity that meets a condition, and the condition includes the ability to provide a specified The UPF service and / or can support the specified interaction mode.
The method of claim 2, further comprising:

Sending, by the SMF entity, an NF status subscription message to the NRF entity, the NF status subscription message is used to subscribe to a UPF entity that meets a condition, the condition including being able to provide a specified UPF service and / or being able to support a specified interaction mode;

Receiving, by the SMF entity, an NF status notification message sent by the NRF entity, where the NF status notification message carries configuration information of at least one UPF entity that already exists or is newly added in the NRF entity that meets the condition;

The SMF entity updates the list of UPF entities stored in the SMF entity according to the NF status notification message.
The method according to claim 1, wherein the SMF entity selecting at least one UPF entity for a PDU session to be established comprises:

The SMF entity sends a NF discovery request message to an NRF entity, and the NF discovery request message is used to request the NRF entity to provide a UPF entity that meets a condition, the condition including being able to provide a specified UPF service and / or being able to support a specified interactive mode;

Receiving, by the SMF entity, an NF discovery response message sent by the NRF entity, where the NF discovery response message carries configuration information of a UPF entity that meets the condition;

The SMF entity selects the at least one UPF entity from the UPF entities that satisfy the condition.
The method according to claim 1, wherein the determining, by the SMF entity, an interaction mode for interacting with the first UPF entity comprises:

Determining, by the SMF entity, an interaction mode for interacting with the first UPF entity based on the configuration information of the first UPF entity; or

Determining, by the SMF entity, an interaction mode for interacting with the first UPF entity based on its own configuration information, wherein the configuration information of the SMF entity indicates an interaction mode supported by the SMF entity; or,

The SMF entity determines an interaction mode for interacting with the first UPF entity based on a node association context, and the node association context indicates an interaction mode determined by the SMF entity for interacting with the first UPF entity.
The method according to any one of claims 1-5, wherein the configuration information of the UPF entity includes at least one of the following information:

Fully qualified domain name FQDN of the UPF entity;

Network protocol IP address of the UPF entity;

Services that UPF entities can provide;

The interaction modes that the UPF entity can support;

The area identifier of the SMF entity that the UPF entity can serve.
The method according to claim 1, wherein after the SMF entity determines an interaction mode with the first UPF entity, the method further comprises:

The SMF entity records the determined interaction manner in the context of a PDU session served by the first UPF entity; or

The SMF entity records the determined first UPF entity interaction manner in a context of a terminal corresponding to the PDU session.
The method according to claim 7, further comprising:

When the PDU session served by the first UPF entity needs to be modified, the SMF entity acquires the interaction mode with the first UPF entity recorded in the context; the context is the context of the PDU session or the The context of the terminal corresponding to the PDU session;

If the acquired interaction mode is a method of invoking a service through the SBI interface, the SMF entity invokes a session modification service provided by the first UPF entity through the SBI interface to modify the first UPF entity The serving PDU session; or

If the obtained interaction mode is an interaction mode through the PTP interface, the SMF entity sends a session modification message to the first UPF entity through the PTP interface to modify the PDU served by the first UPF entity. Conversation.
The method according to claim 7, further comprising:

When the PDU session served by the first UPF entity needs to be released, the SMF entity obtains the interaction mode with the first UPF entity recorded in the context; the context is the context of the PDU session or the The context of the terminal corresponding to the PDU session;

If the obtained interaction mode is a method of invoking a service through the SBI interface, the SMF entity calls the session release service provided by the first UPF entity through the SBI interface to release the first UPF entity The serving PDU session; or

If the obtained interaction mode is an interaction mode through the PTP interface, the SMF entity sends a session release message to the first UPF entity through the PTP interface to release the PDU served by the first UPF entity. Conversation.
A method for node association between an SMF entity and a UPF entity, comprising:

The SMF entity determines the interaction mode with the UPF entity to be associated, and the interaction modes include a manner of interacting through a PTP interface and a manner of invoking a service through an SBI interface to interact;

When the SMF entity determines to interact with the UPF entity through the SBI interface, the SMF entity invokes a node association service provided by the UPF entity through the SBI interface to perform node association with the UPF entity;

When the SMF entity determines to interact with the UPF entity through the PTP interface, the SMF entity sends a node association message to the UPF entity through the PTP interface to perform node association with the UPF entity.
The method according to claim 10, wherein the determining, by the SMF entity, an interaction mode for interacting with the UPF entity comprises:

Determining, by the SMF entity, an interaction mode for interacting with the first UPF entity based on the configuration information of the UPF entity, or

The SMF entity determines an interaction mode for interacting with the UPF entity based on its own configuration information, wherein the configuration information of the SMF entity itself indicates the interaction mode supported by the SMF entity.
The method according to claim 10, wherein after the SMF entity determines an interaction mode with the UPF entity to be associated, the method further comprises:

The SMF entity records the determined interaction manner with the UPF entity in a node association context.
The method of claim 12, further comprising:

When the configuration information of the UPF entity needs to be updated, the SMF entity acquires the interaction mode with the UPF entity recorded in the node association context;

If the obtained interaction mode is a method of invoking a service through the SBI interface, the SMF entity invokes a node update service provided by the UPF entity through the SBI interface to update the configuration information of the UPF entity; or,

If the obtained interaction mode is an interaction mode through the PTP interface, the SMF entity sends a node update message to the UPF entity through the PTP interface to update the configuration information of the UPF entity.
The method of claim 12, further comprising:

When the node association relationship with the UPF entity needs to be released, the SMF entity obtains the interaction mode with the UPF entity recorded in the node association context;

If the obtained interaction mode is a method of invoking a service through the SBI interface, the SMF entity invokes a node release service provided by the UPF entity through the SBI interface to release the connection with the UPF entity. Node associations; or,

If the obtained interaction mode is an interaction mode through the PTP interface, the SMF entity sends a node release message to the UPF entity through the PTP interface to release the node association relationship with the UPF entity. .
The method of claim 12, further comprising:

When the message filtering descriptor of the UPF entity needs to be configured, the SMF entity acquires the interaction mode with the UPF entity recorded in the node association context;

If the obtained interaction mode is a method of invoking a service through the SBI interface, the SMF entity invokes a message filtering descriptor provided by the UPF entity to provide services through the SBI interface to configure the UPF entity The message filtering descriptor; or

If the obtained interaction mode is an interaction mode through the PTP interface, the SMF entity sends a message filtering descriptor provision message to the UPF entity through the PTP interface to configure a message of the UPF entity Filter descriptor.
The method of claim 12, further comprising:

When the message filtering descriptor of the UPF entity needs to be removed, the SMF entity obtains the interaction mode with the UPF entity recorded in the node association context;

If the obtained interaction mode is a method for invoking a service through the SBI interface, the SMF entity invokes a message filtering descriptor removal service provided by the UPF entity through the SBI interface to remove the Message filtering descriptor of the UPF entity; or

If the obtained interaction mode is the interaction mode through the PTP interface, the SMF entity sends a message filtering descriptor removal message to the UPF entity through the PTP interface to remove the UPF entity. Message filtering descriptor.
A UPF entity discovery method, which is characterized by:

The NRF entity receives a first request message sent by the SMF entity, the first request message is used to request to obtain configuration information of a UPF entity that meets a condition, the condition includes being able to provide a specified UPF service and / or being able to support a specified interaction mode The interaction manner includes a manner of interacting through a point-to-point PTP interface, and a manner of invoking a service for interaction through a serviced SBI interface;

The NRF entity searches among the registered UPF entities for at least one UPF entity that meets the condition;

The NRF entity sends a first response message to the SMF entity, and the first response message carries configuration information of the at least one UPF entity.
The method according to claim 17, wherein the first request message is an NF discovery request message, and the first response message is an NF discovery response message.
The method according to claim 17, wherein the first request message is a NF status subscription message, the NF status subscription message is used to subscribe to a UPF entity that meets a condition, and the first response message is a NF status notification Message.
The method of claim 17, further comprising:

The NRF entity receives an NF registration request message sent by a second UPF entity, and the NF registration request message carries configuration information of the second UPF entity, where the configuration information includes services that the second UPF entity can provide and / Or an interaction mode that can be supported by the second UPF entity;

The NRF entity stores configuration information of the second UPF entity;

The NRF entity sends a NF registration response message to the second UPF entity to notify the second UPF entity that the registration is accepted.
The method of claim 20, further comprising:

Determining, by the NRF entity, whether the second UPF entity meets the condition;

If the determination result is yes, the NRF entity sends an NF status notification message to the SMF entity, and the NF status notification message carries configuration information of the second UPF entity.
The method according to any one of claims 17 to 21, wherein the configuration information of the UPF entity includes at least one of the following information:

Fully qualified domain name FQDN of the UPF entity;

Network protocol IP address of the UPF entity;

Services that UPF entities can provide;

The interaction modes that the UPF entity can support;

The area identifier of the SMF entity that the UPF entity can serve.
An SMF entity is characterized in that it includes:

A selection unit, configured to select at least one user plane function UPF entity for a PDU session to be established;

A determining unit, configured to determine an interaction mode for interacting with the first UPF entity for the first UPF entity in the at least one UPF entity; wherein the configuration information of a UPF entity includes the information supported by the UPF entity Interactive methods, including interactive methods through a point-to-point PTP interface, and invoking services through a serviced SBI interface for interaction;

An execution unit, configured to, when determining to interact with the first UPF entity through the SBI interface, invoke a session establishment service provided by the first UPF entity through the SBI interface to establish the PDU session The PDU session provided by the first UPF entity; or when determining to interact with the first UPF entity through the PTP interface, sending a session establishment message to the first UPF entity through the PTP interface to establish A PDU session provided by the first UPF entity in the PDU session.
The SMF entity according to claim 23, wherein the selection unit is specifically configured to:

Selecting from the list at least one UPF entity that satisfies a condition according to the list of UPF entities stored in the SMF entity and the configuration information of the UPF entity in the list, the condition including being able to provide a specified UPF service and / or Ability to support specified interaction methods.
The SMF entity according to claim 24, wherein the SMF entity further comprises an update unit;

The execution unit is further configured to send an NF status subscription message to the NRF entity, where the NF status subscription message is used to subscribe to a UPF entity that meets a condition, the condition includes being able to provide a specified UPF service and / or being able to support a specified And an NF status notification message sent by the NRF entity, where the NF status notification message carries configuration information of at least one UPF entity that already exists or is newly added in the NRF entity that meets the condition;

The updating unit is configured to update the list of UPF entities stored in the SMF entity according to the NF status notification message.
The SMF entity according to claim 23, wherein the selection unit is specifically configured to:

Sending a NF discovery request message to an NRF entity, the NF discovery request message is used to request the NRF entity to provide a UPF entity that meets a condition, the condition including being able to provide a specified UPF service and / or being able to support a specified interaction mode;

Receiving a NF discovery response message sent by the NRF entity, where the NF discovery response message carries configuration information of a UPF entity that meets the condition;

The at least one UPF entity is selected from the UPF entities that satisfy the condition.
The SMF entity according to claim 23, wherein the determining unit is specifically configured to:

Determining an interaction mode for interacting with the first UPF entity based on the configuration information of the first UPF entity, or

Determining an interaction mode for interacting with the first UPF entity based on the configuration information of the SMF entity, wherein the configuration information of the SMF entity indicates the interaction mode supported by the SMF entity; or

An interaction mode for interacting with the first UPF entity is determined based on a node association context, and the node association context indicates an interaction mode determined by the SMF entity to interact with the first UPF entity.
The SMF entity according to claim 23, wherein the configuration information of the UPF entity includes at least one of the following information:

Fully qualified domain name FQDN of the UPF entity;

Network protocol IP address of the UPF entity;

Services that UPF entities can provide;

The interaction modes that the UPF entity can support;

The area identifier of the SMF entity that the UPF entity can serve.
The SMF entity according to claim 23, wherein the execution unit is further configured to:

Record the determined interaction manner in the context of a PDU session served by the first UPF entity; or

Record the determined first UPF entity interaction mode in the context of the terminal corresponding to the PDU session.
The SMF entity according to claim 29, wherein the execution unit is further configured to:

When the PDU session served by the first UPF entity needs to be modified, the interaction mode with the first UPF entity recorded in the context is obtained; the context is the context of the PDU session or the corresponding one of the PDU session The context of the terminal;

If the obtained interaction mode is a method for invoking a service through the SBI interface, then call the session modification service provided by the first UPF entity through the SBI interface to modify the PDU session served by the first UPF entity ;or,

If the obtained interaction mode is an interaction mode through the PTP interface, a session modification message is sent to the first UPF entity through the PTP interface to modify a PDU session served by the first UPF entity.
The SMF entity according to claim 29, wherein the execution unit is further configured to:

When the PDU session served by the first UPF entity needs to be released, the interaction mode with the first UPF entity recorded in the context is acquired; the context is the context of the PDU session or the corresponding one of the PDU session The context of the terminal;

If the obtained interaction mode is a method of invoking a service through the SBI interface, then call the session release service provided by the first UPF entity through the SBI interface to release the PDU session served by the first UPF entity ;or,

If the obtained interaction mode is an interaction mode through the PTP interface, a session release message is sent to the first UPF entity through the PTP interface to release a PDU session served by the first UPF entity.
An SMF entity is characterized in that it includes:

A determining unit, configured to determine an interaction manner with a UPF entity to be associated, the interaction manner includes a manner of interacting through a PTP interface, and a manner of invoking a service through an SBI interface to interact;

An execution unit, configured to, when the SMF entity determines to interact with the UPF entity through the SBI interface, invoke the node association service provided by the UPF entity through the SBI interface to perform node association with the UPF entity And, when the SMF entity determines to interact with the UPF entity through the PTP interface, the SMF entity sends a node association message to the UPF entity through the PTP interface to perform a node with the UPF entity; Associated.
The SMF entity according to claim 32, wherein the determining unit is specifically configured to:

Determining an interaction mode for interacting with the first UPF entity based on the configuration information of the UPF entity, or

An interaction mode for interacting with the UPF entity is determined based on the configuration information of the SMF entity, wherein the configuration information of the SMF entity indicates the interaction mode supported by the SMF entity.
The SMF entity according to claim 32, wherein the SMF entity further comprises a recording unit, configured to:

The determined interaction manner with the UPF entity is recorded in a node association context.
The SMF entity according to claim 34, wherein the execution unit is further configured to:

When the configuration information of the UPF entity needs to be updated, acquiring the interaction mode with the UPF entity recorded in the node association context;

If the obtained interaction mode is a method of invoking a service through the SBI interface, then the node update service provided by the UPF entity is called through the SBI interface to update the configuration information of the UPF entity; or,

If the obtained interaction mode is an interaction mode through the PTP interface, a node update message is sent to the UPF entity through the PTP interface to update the configuration information of the UPF entity.
The SMF entity according to claim 34, wherein the execution unit is further configured to:

When the node association relationship with the UPF entity needs to be released, obtaining the interaction mode with the UPF entity recorded in the node association context;

If the obtained interaction mode is a method of invoking a service through the SBI interface, calling the node release service provided by the UPF entity through the SBI interface to release the node association relationship with the UPF entity; or,

If the obtained interaction mode is an interaction mode through the PTP interface, a node release message is sent to the UPF entity through the PTP interface to release the node association relationship with the UPF entity.
The SMF entity according to claim 34, wherein the execution unit is further configured to:

When the message filtering descriptor of the UPF entity needs to be configured, obtaining the interaction mode with the UPF entity recorded in the node association context;

If the obtained interaction mode is a method for invoking a service through the SBI interface, then the SBI interface is used to call a message filtering descriptor provided by the UPF entity to provide services to configure the message filtering of the UPF entity Descriptor; or,

If the obtained interaction mode is the interaction mode through the PTP interface, then a message filtering descriptor providing message is sent to the UPF entity through the PTP interface to configure the message filtering descriptor of the UPF entity.
The SMF entity according to claim 34, wherein the execution unit is further configured to:

When the message filtering descriptor of the UPF entity needs to be removed, obtaining the interaction mode with the UPF entity recorded in the node association context;

If the obtained interaction mode is a method of invoking a service through the SBI interface, then the message filtering descriptor removal service provided by the UPF entity is called through the SBI interface to remove the UPF entity's report. Text filtering descriptor; or,

If the obtained interaction mode is the interaction mode through the PTP interface, sending a message filtering descriptor removal message to the UPF entity through the PTP interface to remove the message filtering description of the UPF entity symbol.
An NRF entity is characterized in that it includes:

A transceiver unit, configured to receive a first request message sent by an SMF entity, where the first request message is used to request configuration information of a UPF entity that meets a condition, where the condition includes being able to provide a specified UPF service and / or being capable of supporting a specified Interactive methods, including interactive methods through a point-to-point PTP interface, and invoking services through a serviced SBI interface for interaction;

A searching unit, configured to search at least one UPF entity that meets the condition among registered UPF entities;

The transceiver unit is further configured to send a first response message to the SMF entity, where the first response message carries configuration information of the at least one UPF entity.
The NRF entity according to claim 39, wherein the first request message is an NF discovery request message, and the first response message is an NF discovery response message.
The NRF entity according to claim 39, wherein the first request message is a NF status subscription message, the NF status subscription message is used to subscribe to a UPF entity that meets a condition, and the first response message is a NF status Notification message.
The NRF entity according to claim 39, wherein the transceiver unit is further configured to:

Receiving an NF registration request message sent by a second UPF entity, where the NF registration request message carries configuration information of the second UPF entity, where the configuration information includes services that the second UPF entity can provide and / or the first Interaction modes supported by the two UPF entities;

Storing configuration information of the second UPF entity;

Sending a NF registration response message to the second UPF entity to notify the second UPF entity that the registration is accepted.
The NRF entity according to claim 42, wherein the NRF entity further comprises a determining unit;

The determining unit is configured to determine whether the second UPF entity meets the condition;

The transceiver unit is further configured to send a NF status notification message to the SMF entity if the determination result is yes, and the NF status notification message carries the configuration information of the second UPF entity.
The NRF entity according to any one of claims 39-43, wherein the configuration information of the UPF entity includes at least one of the following information:

Fully qualified domain name FQDN of the UPF entity;

Network protocol IP address of the UPF entity;

Services that UPF entities can provide;

The interaction modes that the UPF entity can support;

The area identifier of the SMF entity that the UPF entity can serve.
An SMF entity is characterized in that it includes:

At least one processor; and

A memory connected in communication with the at least one processor; wherein,

The memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor, so that the at least one processor can execute the instructions as claimed in any one of claims 1 to 9. The method described.
An SMF entity is characterized in that it includes:

At least one processor; and

A memory connected in communication with the at least one processor; wherein,

The memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor, so that the at least one processor can execute the instructions as claimed in any one of claims 10 to 16. The method described.
An NRF entity is characterized in that it includes:

At least one processor; and

A memory connected in communication with the at least one processor; wherein,

The memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor, so that the at least one processor can execute as claimed in any one of claims 17-22. The method described.
A computer storage medium, characterized in that the computer storage medium stores computer instructions, and when the computer instructions are run on a computer, the computer is caused to execute the method according to any one of claims 1-9.
A computer storage medium, wherein the computer storage medium stores computer instructions, and when the computer instructions are run on a computer, the computer causes the computer to execute the method according to any one of claims 10-16.
A computer storage medium, characterized in that the computer storage medium stores computer instructions, and when the computer instructions are run on a computer, the computer is caused to execute the method according to any one of claims 17-22.