[go: up one dir, main page]
More Web Proxy on the site http://driver.im/

CN110831092A - Method and equipment for PDU session management, node association and UPF discovery - Google Patents

Method and equipment for PDU session management, node association and UPF discovery Download PDF

Info

Publication number
CN110831092A
CN110831092A CN201810918468.7A CN201810918468A CN110831092A CN 110831092 A CN110831092 A CN 110831092A CN 201810918468 A CN201810918468 A CN 201810918468A CN 110831092 A CN110831092 A CN 110831092A
Authority
CN
China
Prior art keywords
entity
upf
upf entity
smf
mode
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
CN201810918468.7A
Other languages
Chinese (zh)
Other versions
CN110831092B (en
Inventor
艾明
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Datang Mobile Communications Equipment Co Ltd
Original Assignee
China Academy of Telecommunications Technology CATT
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by China Academy of Telecommunications Technology CATT filed Critical China Academy of Telecommunications Technology CATT
Priority to CN201810918468.7A priority Critical patent/CN110831092B/en
Priority to CN202110610366.0A priority patent/CN113347673B/en
Priority to PCT/CN2019/100306 priority patent/WO2020034930A1/en
Publication of CN110831092A publication Critical patent/CN110831092A/en
Application granted granted Critical
Publication of CN110831092B publication Critical patent/CN110831092B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0033—Control or signalling for completing the hand-off for data sessions of end-to-end connection with transfer of context information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/19—Connection re-establishment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/25—Maintenance of established connections

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

The invention discloses a method and equipment for PDU session management, node association and UPF discovery, which are used for realizing a mixed deployment scene of a UPF entity supporting a PTP interface and a UPF entity supporting an SBI interface and realizing interaction between a control plane entity and the UPF entity. The PDU session management method comprises the following steps: a Session Management Function (SMF) entity selects at least one User Plane Function (UPF) entity for a PDU session to be established; aiming at a first UPF entity in at least one UPF entity, the SMF entity determines an interactive mode of interacting with the first UPF entity; the configuration information of one UPF entity comprises interaction modes supported by the UPF entity, wherein the interaction modes comprise a mode of interacting through a point-to-point PTP interface and a mode of calling service for interacting through a service SBI interface; and interacting with the first UPF entity based on the determined interaction mode.

Description

Method and equipment for PDU session management, node association and UPF discovery
Technical Field
The present invention relates to the field of communications technologies, and in particular, to a method and an apparatus for PDU session management, node association, and UPF discovery.
Background
Currently, in the fifth Generation (5Generation, 5G) mobile communication system, a Service architecture is introduced into the control plane, as shown in fig. 1, which is a network architecture diagram using a Service Based Interface (SBI) Interface. The control plane entities are interacted by adopting an SBI interface, for example, when a Session Management Function (SMF) entity needs to interact with a Network warehousing Function (NRF) entity, the interaction can be realized by calling a service provided by the NRF entity; and Point-To-Point (PTP) interfaces are used for interaction between the user plane entities and between the control plane entity and the user plane entity.
In the current research process, a service concept is considered to be introduced into a User Plane, for example, a User Plane Function (UPF) entity also adopts an SBI interface, but an original UPF entity cannot support the SBI interface, and a newly introduced UPF entity may support the SBI interface, and further, a mode that an original control Plane entity directly interacts with a UPF entity through a PTP interface is obviously not applicable, so how to implement interaction between the control Plane entity and the UPF entity in a hybrid deployment scenario of the UPF entity supporting the PTP interface and the UPF entity supporting the SBI interface is an urgent problem to be solved.
Disclosure of Invention
The embodiment of the invention provides a method and equipment for PDU session management, node association and UPF discovery, which are used for realizing a mixed deployment scene of a UPF entity supporting a PTP interface and a UPF entity supporting an SBI interface and realizing interaction between a control plane entity and the UPF entity.
In a first aspect, a PDU session management method is provided, including:
the SMF entity selects at least one UPF entity for the PDU session to be established;
aiming at a first UPF entity in the at least one UPF entity, the SMF entity determines an interactive mode of interacting with the first UPF entity; the configuration information of one UPF entity comprises interaction modes supported by the UPF entity, wherein the interaction modes comprise a mode of interacting through a point-to-point PTP interface and a mode of calling service for interacting through a service SBI interface;
when the SMF entity determines to interact with the first UPF entity through the SBI interface, the SMF entity calls session establishment services provided by the first UPF entity through the SBI interface so as to establish a PDU session in the PDU session, wherein the PDU session is served by the first UPF entity; or,
and 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 so as to establish the PDU session in which the first UPF entity provides service in the PDU session.
In the embodiment of the invention, after the SMF entity selects the UPF entity providing service for the PDU session, the interactive mode of interacting with the UPF entity is determined, namely, the interaction is performed through an N4 interface between the original SMF entity and the UPF entity or through an SBI interface provided by the UPF entity, and the session is established according to the determined interactive mode, so that the interaction between the SMF entity and the UPF entity is realized.
Optionally, the selecting, by the SMF entity, at least one UPF entity for the PDU session to be established includes:
and according to the UPF entity list stored by the SMF entity and the configuration information of the UPF entities in the list, the SMF entity selects the at least one UPF entity meeting the conditions from the list, wherein the conditions comprise that the specified UPF service can be provided and/or the specified interaction mode can be supported.
Optionally, the method further includes:
the SMF entity sends NF status subscription information to the NRF entity, wherein the NF status subscription information is used for subscribing UPF entities meeting conditions, and the conditions comprise that appointed UPF service can be provided and/or appointed interaction modes can be supported;
the SMF entity receives a NF status notification message sent by the NRF entity, wherein the NF status notification message carries configuration information of at least one UPF entity which is already or newly added in the NRF entity and meets the condition;
and the SMF entity updates a self-stored UPF entity list according to the NF state notification message.
Optionally, the selecting, by the SMF entity, at least one UPF entity for the PDU session to be established includes:
the SMF entity sends a NF discovery request message to a NRF entity, wherein the NF discovery request message is used for requesting the NRF entity to provide a UPF entity meeting conditions, and the conditions comprise that a specified UPF service can be provided and/or a specified interaction mode can be supported;
the SMF entity receives a NF discovery response message sent by the NRF entity, wherein the NF discovery response message carries the configuration information of the UPF entity meeting the condition;
the SMF entity selects the at least one UPF entity from the UPF entities meeting the condition.
Optionally, the determining, by the SMF entity, an interaction manner of interacting with the first UPF entity includes:
the SMF entity determines an interaction mode for interacting with the first UPF entity based on the configuration information of the first UPF entity, or,
the SMF entity determines an interactive mode interacting with the first UPF entity based on configuration information of the SMF entity, wherein the configuration information of the SMF entity indicates the interactive mode supported by the SMF entity; or,
and the SMF entity determines an interactive mode of interacting with the first UPF entity based on a node association context, wherein the node association context indicates the interactive mode of interacting with the first UPF entity determined by the SMF entity.
Optionally, the configuration information of the UPF entity includes at least one of the following information:
a fully qualified domain name FQDN of the UPF entity;
the network protocol IP address of the UPF entity;
services that the UPF entity is capable of providing;
the interaction mode supported by the UPF entity;
the area identification of the SMF entity that the UPF entity can serve.
Optionally, after the SMF entity determines the interaction manner with the first UPF entity, the method further includes:
the SMF entity records the determined interactive mode in the context of the PDU session served by the first UPF entity; or,
and the SMF entity records the determined interaction mode of the first UPF entity in the context of the terminal corresponding to the PDU session.
In the embodiment of the present invention, after determining the interaction mode with the first UPF entity, the SMF entity may record the determined interaction mode in the context, so that the interaction mode can be conveniently obtained from the context in the subsequent management process of the PDU session.
Optionally, the method further includes:
when the PDU session served by the first UPF entity needs to be modified, the SMF entity acquires an interaction mode recorded in a context and the first UPF entity; 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 mode for carrying out interaction by calling service through the SBI, the SMF entity calls session modification service provided by the first UPF entity through the SBI to modify the PDU session of the first UPF entity service; or,
and if the acquired interaction mode is the interaction mode through the PTP interface, the SMF entity sends a session modification message to the first UPF entity through the PTP interface so as to modify the PDU session served by the first UPF entity.
Optionally, the method further includes:
when the PDU session served by the first UPF entity needs to be released, the SMF entity acquires an interaction mode recorded in a context and the first UPF entity; 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 mode for carrying out interaction by calling service through the SBI, the SMF entity calls session release service provided by the first UPF entity through the SBI so as to release the PDU session of the first UPF entity service; or,
and if the acquired interaction mode is the interaction mode through the PTP interface, the SMF entity sends a session release message to the first UPF entity through the PTP interface so as to release the PDU session served by the first UPF entity.
In a second aspect, a method for node association between an SMF entity and a UPF entity is provided, which includes:
the SMF entity determines an interaction mode with a UPF entity to be associated, wherein the interaction mode comprises a mode of interaction through a PTP interface and a mode of interaction through service calling through an SBI interface;
when the SMF entity determines to interact with the UPF entity through the SBI, the SMF entity calls a node association service provided by the UPF entity through the SBI so as 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 so as to perform node association with the UPF entity.
Optionally, the determining, by the SMF entity, an interaction manner of interacting with the UPF entity includes:
the SMF entity determines an interaction mode for interacting with the first UPF entity based on the configuration information of the UPF entity, or,
and the SMF entity determines an interaction mode interacting with the UPF entity based on configuration information of the SMF entity, wherein the configuration information of the SMF entity indicates the interaction mode supported by the SMF entity.
Optionally, after the SMF entity determines the interaction mode with the UPF entity to be associated, the method further includes:
and the SMF entity records the determined interaction mode with the UPF entity in the context of node association.
Optionally, the method further includes:
when the configuration information of the UPF entity needs to be updated, the SMF entity acquires an interaction mode with the UPF entity recorded in the node association context;
if the acquired interaction mode is a mode for carrying out interaction by calling service through the SBI, the SMF entity calls node updating service provided by the UPF entity through the SBI to update the configuration information of the UPF entity; or,
and if the acquired interaction mode is the interaction mode through the PTP interface, the SMF entity sends a node update message to the UPF entity through the PTP interface so as to update the configuration information of the UPF entity.
Optionally, the method further includes:
when the node association relation between the SMF entity and the UPF entity needs to be released, the SMF entity acquires the interaction mode with the UPF entity recorded in the node association context;
if the acquired interaction mode is a mode of carrying out interaction by calling service through the SBI, the SMF entity calls a node release service provided by the UPF entity through the SBI to release the node association relation with the UPF entity; or,
and if the acquired interaction mode is the interaction mode through the PTP interface, the SMF entity sends a node release message to the UPF entity through the PTP interface so as to release the node association relation between the SMF entity and 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 acquired interaction mode is a mode of carrying out interaction by calling service through the SBI, the SMF entity calls a message filtering descriptor provided by the UPF entity through the SBI to provide service so as to configure the message filtering descriptor of the UPF entity; or,
and if the acquired interaction mode is the interaction mode through the PTP interface, the SMF entity sends a message filtering descriptor providing message to the UPF entity through the PTP interface so as to configure the message filtering descriptor of the UPF entity.
Optionally, the method further includes:
when the message filtering descriptor of the UPF entity needs to be removed, the SMF entity acquires the interaction mode with the UPF entity recorded in the node association context;
if the acquired interaction mode is a mode of carrying out interaction by calling service through the SBI, the SMF entity calls a message filtering descriptor removal service provided by the UPF entity through the SBI so as to remove the message filtering descriptor of the UPF entity; or,
and if the acquired interaction mode is the interaction mode through the PTP interface, the SMF entity sends a message filtering descriptor removing message to the UPF entity through the PTP interface so as to remove the message filtering descriptor of the UPF entity.
In a third aspect, a method for discovering a UPF entity is provided, including:
the method comprises the steps that an NRF entity receives a first request message sent by an SMF entity, wherein the first request message is used for requesting to acquire configuration information of a UPF entity meeting conditions, the conditions comprise that a specified UPF service can be provided and/or a specified interaction mode can be supported, and the interaction mode comprises a mode of interacting through a point-to-point PTP interface and a mode of interacting through service calling SBI interface;
the NRF entity searches at least one UPF entity meeting the condition in the registered UPF entities;
and the NRF entity sends a first response message to the SMF entity, wherein the first response message carries the configuration information of the at least one UPF entity.
In the embodiment of the invention, the SMF entity requests which UPF entity is needed to be described in the UPF process, that is, the UPF entity which can provide which services, and/or the UPF entity which can support which interfaces, so that the UPF entity fed back by the NRF entity meets the requirements of the SMF entity, and the NRF also informs the SMF entity of the configuration information of the UPF entities when feeding back the UPF entity list, so as to provide a basis for interaction between the SMF entity and the UPF entity in the mixed deployment scenario of the SBI interface and the PTP interface.
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 an 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 an NF status notification message.
Optionally, the method further includes:
the NRF entity receives a NF registration request message sent by a second UPF entity, wherein the NF registration request message carries configuration information of the second UPF entity, and the configuration information comprises services which can be provided by the second UPF entity and/or interaction modes which 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 inform the second UPF entity that registration is accepted.
Optionally, the method further includes:
the NRF entity determining whether the second UPF entity satisfies the condition;
and if the result is positive, the NRF entity sends a NF status notification message to the SMF entity, wherein the NF status notification message carries the configuration information of the second UPF entity.
Optionally, the configuration information of the UPF entity includes at least one of the following information:
a fully qualified domain name FQDN of the UPF entity;
the network protocol IP address of the UPF entity;
services that the UPF entity is capable of providing;
the interaction mode supported by the UPF entity;
the area identification of the SMF entity that the UPF entity can serve.
In a fourth aspect, there is provided an SMF entity comprising:
the selection unit is used for selecting at least one user plane function UPF entity for the PDU session to be established;
a determining unit, configured to determine, for a first UPF entity in the at least one UPF entity, an interaction manner for interacting with the first UPF entity; the configuration information of one UPF entity comprises interaction modes supported by the UPF entity, wherein the interaction modes comprise a mode of interacting through a point-to-point PTP interface and a mode of calling service for interacting through a service SBI interface;
an execution unit, configured to, when it is determined that the PDU session is interacted with the first UPF entity through the SBI interface, invoke, through the SBI interface, a session establishment service provided by the first UPF entity, so as to establish the PDU session serviced by the first UPF entity in the PDU session; or when the interaction with the first UPF entity through the PTP interface is determined, sending a session establishment message to the first UPF entity through the PTP interface so as to establish the PDU session in which the service is provided by the first UPF entity in the PDU session.
Optionally, the selecting unit is specifically configured to:
and selecting the at least one UPF entity meeting the conditions from the list according to the UPF entity list stored by the SMF entity and the configuration information of the UPF entities in the list, wherein the conditions comprise that the specified UPF service can be provided and/or the specified interaction mode can be supported.
Optionally, the SMF entity further includes an updating unit;
the execution unit is further configured to send a 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, and the condition includes that a specified UPF service can be provided and/or a specified interaction mode can be supported; receiving a NF status notification message sent by the NRF entity, wherein the NF status notification message carries configuration information of at least one UPF entity which is already or newly added in the NRF entity and meets the condition;
and the updating unit is used for updating the UPF entity list stored in the SMF entity according to the NF status notification message.
Optionally, the selecting unit is specifically configured to:
sending a NF discovery request message to a NRF entity, wherein the NF discovery request message is used for requesting the NRF entity to provide a UPF entity meeting conditions, and the conditions comprise that a specified UPF service can be provided and/or a specified interaction mode can be supported;
receiving a NF discovery response message sent by the NRF entity, wherein the NF discovery response message carries the configuration information of the UPF entity meeting the condition;
and selecting the at least one UPF entity from the UPF entities meeting 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,
and determining an interactive mode of interacting with the first UPF entity based on a node association context, wherein the node association context indicates the interactive mode of interacting with the first UPF entity determined by the SMF entity.
Optionally, the configuration information of the UPF entity includes at least one of the following information:
a fully qualified domain name FQDN of the UPF entity;
the network protocol IP address of the UPF entity;
services that the UPF entity is capable of providing;
the interaction mode supported by the UPF entity;
the area identification of the SMF entity that the UPF entity can serve.
Optionally, the execution unit is further configured to:
recording the determined interaction mode in the context of the PDU session served by the first UPF entity; or,
and recording the determined interaction mode of the first UPF entity in the context of the terminal corresponding to the PDU session.
Optionally, the execution unit is further configured to:
when the PDU session of the first UPF entity service needs to be modified, the interaction mode recorded in the context and the first UPF entity is obtained; 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 mode for carrying out interaction by calling service through the SBI, calling session modification service provided by the first UPF entity through the SBI to modify the PDU session of the first UPF entity service; or,
and if the acquired interaction mode is the interaction mode through the PTP interface, sending a session modification message to the first UPF entity through the PTP interface so as to modify the 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, acquiring the interaction mode recorded in the context and the first UPF entity; 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 mode for carrying out interaction by calling service through the SBI, calling session release service provided by the first UPF entity through the SBI to release the PDU session of the first UPF entity service; or,
and if the acquired interaction mode is the interaction mode through the PTP interface, sending a session release message to the first UPF entity through the PTP interface so as to release the PDU session served by the first UPF entity.
In a fifth aspect, there is provided an SMF entity comprising:
the device comprises a determining unit, a determining unit and a judging unit, wherein the determining unit is used for determining an interaction mode of a UPF entity to be associated, and the interaction mode comprises a mode of carrying out interaction through a PTP interface and a mode of carrying out interaction through an SBI interface calling service;
the execution unit is used for calling the 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 SBI interface; 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 so as to perform node association with the UPF entity.
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,
and determining an interactive mode interacting with the UPF entity based on the configuration information of the SMF entity, wherein the configuration information of the SMF entity indicates the interactive mode supported by the SMF entity.
Optionally, the SMF entity further includes a recording unit, configured to:
and recording the determined interaction mode with the UPF entity in the 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 recorded in the node association context and the UPF entity;
if the acquired interaction mode is a mode of carrying out interaction through the SBI interface calling service, calling a node updating service provided by the UPF entity through the SBI interface to update the configuration information of the UPF entity; or,
and if the acquired interaction mode is the interaction mode through the PTP interface, sending a node update message to the UPF entity through the PTP interface so as to update the configuration information of the UPF entity.
Optionally, the execution unit is further configured to:
when the node association relation with the UPF entity needs to be released, acquiring the interaction mode with the UPF entity recorded in the node association context;
if the acquired interaction mode is a mode of carrying out interaction by calling service through the SBI, calling node release service provided by the UPF entity through the SBI to remove the node association relation with the UPF entity; or,
and if the acquired interaction mode is the mode of interaction through the PTP interface, sending a node release message to the UPF entity through the PTP interface so as to release the node association relation between the UPF entity and the node release message.
Optionally, the execution unit is further configured to:
when the message filtering descriptor of the UPF entity needs to be configured, acquiring the interaction mode of the UPF entity and the record in the context associated with the node;
if the acquired interaction mode is a mode of carrying out interaction by calling service through the SBI, calling a message filtering descriptor provided by the UPF entity through the SBI to provide service so as to configure the message filtering descriptor of the UPF entity; or,
and if the acquired interaction mode is the interaction mode through the PTP interface, sending a message filtering descriptor providing message to the UPF entity through the PTP interface so as 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, acquiring the interaction mode of the UPF entity and the record in the context associated with the node;
if the acquired interaction mode is a mode of carrying out interaction by calling service through the SBI, calling a message filtering descriptor removal service provided by the UPF entity through the SBI so as to remove the message filtering descriptor of the UPF entity; or,
and if the acquired 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 so as to remove the message filtering descriptor of the UPF entity.
In a sixth aspect, there is provided an NRF entity comprising:
a transceiver unit, configured to receive a first request message sent by an SMF entity, where the first request message is used to request to acquire configuration information of a UPF entity that meets a condition, where the condition includes that a specified UPF service can be provided and/or a specified interaction mode can be supported, and the interaction mode includes a mode of performing interaction through a point-to-point PTP interface and a mode of performing interaction by invoking a service through a serving SBI interface;
a searching unit, configured to search at least one UPF entity that meets the condition in the 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 the configuration information of the at least one UPF entity.
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 an 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 an NF status notification message.
Optionally, the transceiver unit is further configured to:
receiving a NF registration request message sent by a second UPF entity, wherein the NF registration request message carries configuration information of the second UPF entity, and the configuration information comprises services which can be provided by the second UPF entity and/or interaction modes which can be supported by the second UPF entity;
storing configuration information of the second UPF entity;
sending a NF registration response message to the second UPF entity to inform the second UPF entity that registration is accepted.
Optionally, the NRF entity further includes a determining unit;
the determining unit is configured to determine whether the second UPF entity satisfies the condition;
the transceiver unit is further configured to send an NF status notification message to the SMF entity if the determination result is yes, where the NF status notification message carries the configuration information of the second UPF entity.
Optionally, the configuration information of the UPF entity includes at least one of the following information:
a fully qualified domain name FQDN of the UPF entity;
the network protocol IP address of the UPF entity;
services that the UPF entity is capable of providing;
the interaction mode supported by the UPF entity;
the area identification of the SMF entity that the UPF entity can serve.
In a seventh aspect, a communication device is provided, including:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein,
the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of the first aspect; or to enable the at least one processor to perform a method as described in the second aspect; or to enable the at least one processor to perform a method as described in the third aspect.
In an eighth aspect, a computer storage medium is provided,
the computer storage medium stores computer instructions which, when run on a computer, cause the computer to perform a method according to the first aspect, or cause the computer to perform a method according to the second aspect, or cause the computer to perform a method according to the third aspect.
Drawings
Fig. 1 is a network architecture diagram of a 5G communication system according to an embodiment of the present invention;
fig. 2 is a flowchart illustrating a PDU session management method according to an embodiment of the present invention;
fig. 3 is a schematic flowchart of an association process between nodes according to an embodiment of the present invention;
fig. 4 is a flowchart illustrating a UPF discovery process according to an embodiment of the present invention;
fig. 5 is a flowchart illustrating a first implementation manner of a UPF discovery process according to an embodiment of the present invention;
fig. 6 is a flowchart illustrating a second implementation manner of a UPF discovery process according to an embodiment of the present invention;
fig. 7 is a schematic structural diagram of an SMF entity according to an embodiment of the present invention;
fig. 8 is a schematic structural diagram of another SMF entity according to an embodiment of the present invention;
FIG. 9 is a schematic diagram of a NRF entity according to an embodiment of the present invention;
fig. 10 is a schematic structural diagram of a communication device according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention.
The technical background of the embodiments of the present invention is described below.
In the current research process, a service concept is considered to be introduced into a User Plane, for example, a User Plane Function (UPF) entity also adopts an SBI interface, but an original UPF entity cannot support the SBI interface, and a newly introduced UPF entity may support the SBI interface, and an original interaction mode directly through a PTP interface is obviously not applicable, so that in a mixed deployment scenario of a UPF entity supporting a PTP interface and a UPF entity supporting an SBI interface, how to implement interaction between a control Plane entity and a UPF entity is an urgent problem to be solved.
In view of this, an embodiment of the present invention provides a method for PDU session management, in which when or after an SMF entity selects a UPF entity that provides a service for a PDU session, an interaction mode for interacting with the UPF entity is determined, that is, interaction is performed through an N4 interface between an original SMF entity and the UPF entity or interaction is performed through an SBI interface provided by the UPF entity, and a session is established according to the determined interaction mode, so as to implement interaction between the SMF entity and the UPF entity. In other words, the SMF entity needs to determine whether the UPF entity is using the PTP interface or the SBI interface when or after selecting the UPF entity that serves the PDU session. When the SMF entity determines that the UPF entity uses the PTP interface, the SMF entity can adopt an N4 interface to interact with the UPF entity; when the SMF entity determines that the UPF entity uses the SBI, the SMF may interact with the UPF entity by calling the UPF to provide services.
In the invention, the interactive mode of interaction with the UPF entity is determined, namely whether the UPF uses a PTP interface or an SBI is determined; i.e., to determine whether to interact with a UPF using a PTP interface or a UPF using an SBI interface.
The technical scheme provided by the embodiment of the invention is described below by combining the accompanying drawings.
Referring to fig. 2, a flowchart of a PDU session management method provided in the present invention may involve an interactive process among an SMF entity, a UPF entity and an NRF entity, so that the following steps performed by these entities are described together.
Step 201: the SMF entity selects at least one UPF entity for the PDU session to be established.
In the embodiment of the present invention, when a terminal initially accesses, a new PDU Session needs to be established for the terminal, and then the SMF entity selects a Session and Service Continuity (SSC) mode for the PDU Session and at least one UPF entity for serving the PDU Session, where the number of UPF entities for serving the PDU Session may be one or more.
Specifically, the SMF entity selects at least one UPF entity, and may select at least one UPF entity that satisfies a condition from a UPF entity list stored in the SMF entity itself. The SMF entity stores configuration information of each UPF entity in the UPF entity list, for example, stores interaction modes that the UPF entity can support or services that the UPF entity can provide, and the like, so that the SMF entity can determine whether the UPF entity satisfies the condition based on the configuration information of the UPF entity.
In an actual application process, the UPF entity list stored in the SMF entity may be updated based on the UPF entity obtained in the UPF discovery process. For example, the UPF entity list stored in the SMF entity may be updated based on receiving a NF discovery response message sent by the NRF entity, that is, the UPF entity carried in the NF discovery response message may be updated to the UPF entity list. Or, the UPF entity list stored in the SMF entity may also be updated based on receiving a NF status notification message sent by the NRF entity, that is, the UPF entity carried in the NF status notification message may be updated to the UPF entity list.
Specifically, the SMF entity selects at least one UPF entity, and may also select from UPF entities obtained in a UPF discovery process. For example, the SMF entity may select from the UPF entities indicated in the NF discovery response message or the NF status notification message fed back by the NRF entity. The NF discovery response message and the NF status notification message both carry configuration information of the UPF entity, so that the SMF entity can determine whether the UPF entity meets the condition based on the configuration information of the UPF entity.
The UPF discovery process will be specifically described later, and will not be described herein again.
Step 202: the SMF entity determines the interaction mode with the first UPF entity.
In the embodiment of the present invention, if the SMF entity selects at least one UPF entity for the PDU session that needs to be newly created, the SMF entity determines an interaction manner with the UPF entities, and a process of determining the interaction manner is described below by taking the first UPF entity as an example, where the first UPF entity may be any one of the at least one UPF entity.
Specifically, the SMF entity can know the interfaces supported by the first UPF entity based on the configuration information of the first UPF entity, and can further interact with the UPF entities through which interface. For example, when the first UPF entity only supports the interaction mode 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 interaction mode through the SBI interface, and when the interaction mode through the PTP interface, the SMF entity may select any one of the interaction modes from among the interaction modes to interact with the first UPF entity.
The configuration information of the UPF entity may include at least one of the following information:
a Fully Qualified Domain Name (FQDN) of the UPF entity;
a network Protocol (IP) address of the UPF entity;
the services that the UPF entity is capable of providing are illustrated in the following table as part of the services provided by the UPF entity. Wherein 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 NupfWhen the service operation is established, namely the service operation is used for requesting the UPF entity to establish the PDU session, and when the service operation is modified or released, the service operation is used for requesting 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 a PDU Session Establishment service of the UPF entity, and sends a Nupf Session _ Establishment _ Request to the UPF entity, and then after the UPF entity completes the Session Establishment, sends a NupfSession _ Establishment _ response to the SMF entity.
Figure BDA0001763634860000191
The interaction mode supported by the UPF entity; in order to enable the SMF entity to know which interface to interact with the UPF entity through, the configuration information may include an interaction mode that the UPF entity can support, where the interaction mode may include a mode that the UPF entity supports interaction through a PTP interface or a mode that the UPF entity supports interaction through an SBI interface, or both the modes. The interaction mode that the UPF entity can support, in other words, the interface that the UPF entity uses, i.e. whether the UPF entity uses the PTP interface or the UPF entity uses the SBI interface.
The parameter list supported by the UPF entity may include, for example, Single-Network Slice Selection Assistance Information (S-NSSAI) and a Data Network Name (DNN).
Uniform Resource Locator (URL) of UPF entity.
The area identities of SMF entities that a UPF entity can serve, e.g. only SMF entities are allowed to interact with UPF entities belonging to a particular SMF area identity.
Specifically, the SMF entity may further determine an interaction mode with the first UPF entity based on configuration information of the SMF entity, where the configuration information of the SMF entity indicates the interaction mode supported by the SMF entity. For example, the interaction mode configured for the SMF entity is a mode of interacting only through the SBI interface, so that the SMF entity selects a UPF entity supporting the SBI interface when selecting the UPF entity, and the SMF entity can directly determine that the interaction mode with the first UPF entity is the mode of interacting through the SBI interface; or, the interaction mode configured for the SMF entity is a mode of interacting only through a PTP interface, and then the SMF entity selects a UPF entity supporting the PTP interface when selecting a UPF entity, and the SMF entity can directly determine that the interaction mode with the first UPF entity is the mode of interacting through the PTP interface.
Optionally, if the SMF entity has already established a node association relationship with the first UPF entity, the SMF entity may determine an interaction manner with the UPF entity through the above node association relationship. For details, refer to the method for performing node association between the SMF entity and the UPF entity, which is described in the following fig. 3, which is not repeated herein.
Step 203 a: the SMF entity sends a session establishment service request message to the first UPF entity.
In the embodiment of the invention, when the SMF entity determines to interact with the first UPF entity through the SBI, the SMF entity sends a Session Establishment service Request message, namely Nupf Session _ Establishment _ Request, to the first UPF entity through the SBI so as to call the Session Establishment service provided by the first UPF entity and establish the PDU Session provided by the first UPF entity.
Step 204 a: the first UPF entity sends a session setup service response message to the SMF entity.
In the embodiment of the invention, 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, namely NupfSession _ availability _ reply, to the SMF entity.
Step 203 b: the SMF entity sends a session establishment message to the first UPF entity.
In the embodiment of the present invention, 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 N4Session Establishment Request message (N4Session Establishment Request) to the first UPF entity through the N4 interface, so as to establish a PDU Session in the PDU Session, which is served by the first UPF entity.
Step 204 b: the first UPF entity sends a session establishment response message to the SMF entity.
In the embodiment of the present invention, after receiving the Session Establishment message, the first UPF entity performs corresponding processing according to the Session Establishment message, and feeds back a Session Establishment response message to the SMF entity, that is, sends an N4Session Establishment response message (N4Session Establishment response) to the SMF entity through the N4 interface.
Step 205: and the SMF entity records the determined interaction mode.
In the embodiment of the invention, after the SMF entity determines the interaction mode with the first UPF entity, the determined interaction mode is recorded so that the interaction mode can be acquired in the subsequent session management process.
Specifically, the SMF entity may record the determined interaction manner in a context (context) of the PDU session serviced by the first UPF entity, or the SMF entity may record the determined interaction manner in a context of a terminal corresponding to the PDU session.
Steps 203a and 204a are two different alternatives from steps 203b and 204b, and in the specific implementation process, one of the alternatives may be executed according to the determination result of the SMF, and the subsequent session modification or release is similar to this, and will not be described in detail later. 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, so that in an actual process, the two processes may be executed sequentially or simultaneously.
Step 206: the SMF entity determines the interaction mode with the first UPF entity based on the interaction mode recorded in the context.
When the PDU session served by the first UPF entity needs to be modified or released, the interaction with the first UPF entity can be carried out based on the interaction mode recorded in the context because the previously determined interaction mode is 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 207 a: the SMF entity sends a session modification service request message to the first UPF entity.
In the embodiment of the invention, when an SMF entity needs to modify a PDU Session served by a first UPF entity and the SMF entity determines to interact with the first UPF entity through an SBI interface based on context, the SMF entity sends a Session Modification service Request message, namely Nupf Session _ Modification _ Request, to the first UPF entity through the SBI interface so as to call a Session Modification service provided by the first UPF entity and modify the PDU Session served by the first UPF entity. The session modification service request message carries Access Network (AN) tunnel information and a forwarding rule.
Step 208 a: the first UPF entity sends a session modification service response message to the SMF entity.
In the embodiment of the invention, after receiving the session modification service request message, the first UPF entity performs corresponding processing according to the session modification service request message, and feeds back a session modification service response message to the SMF entity through the SBI interface.
Step 207 b: the SMF entity sends a session modification message to the first UPF entity.
In the embodiment of the present invention, when the SMF entity needs to modify the PDU Session serviced 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 a Session Modification message to the first UPF entity through the PTP interface, that is, initiates an N4Session Modification Request message (N4Session Modification Request) to the first UPF entity through the N4 interface, so as to modify the PDU Session serviced by the first UPF entity in the uppdu Session. Wherein, the N4session modification request message carries the AN tunnel information and the forwarding rule.
Step 208 b: the first UPF entity sends a session modification response message to the SMF entity.
In the embodiment of the present invention, after receiving the Session Modification message, the first UPF entity performs corresponding processing according to the Session Modification message, and feeds back a Session Modification response message to the SMF entity, that is, sends an N4Session Modification response message (N4Session Modification response) to the SMF entity through an N4 interface.
Step 209 a: the SMF entity sends a session release service request message to the first UPF entity.
In the embodiment of the invention, when the SMF entity needs to Release the PDU Session of the first UPF entity service and the SMF entity determines to interact with the first UPF entity through the SBI based on the context, the SMF entity releases a service Request message, namely Nupf Session _ Release _ Request, to the first UPF entity Session through the SBI so as to call the Session Release service provided by the first UPF entity and Release the PDU Session provided by the first UPF entity.
Step 210 a: the first UPF entity sends a session release service response message to the SMF entity.
In the embodiment of the invention, 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 a session release service response message to the SMF entity through the SBI interface.
Step 209 b: the SMF entity sends a session release message to the first UPF entity.
In the embodiment of the present invention, when the SMF entity needs to Release the PDU Session serviced 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 a Session Release message to the first UPF entity through the PTP interface, that is, initiates an N4Session Release Request message (N4Session Release Request) to the first UPF entity through the N4 interface, so as to Release the PDU Session serviced by the first UPF entity in the PDU Session.
Step 210 b: the first UPF entity sends a session release response message to the SMF entity.
In the embodiment of the present invention, after receiving the Session Release message, the first UPF entity performs corresponding processing according to the Session Release message, and feeds back a Session Release response message to the SMF entity, that is, sends an N4Session Release response message (N4Session Release response) to the SMF entity through the N4 interface.
It should be noted that, since the steps 207a to 210b are respectively interactive processes based on different processes, there is no substantial precedence relationship in the actual application process, for example, the steps 207a and 208a are PDU session modification processes, the steps 209a and 210a are PDU session release processes, and there is no precedence order in the flow between the two processes, so that the processes are executed according to specific requirements in actual execution, and the processes in the subsequent technical solutions are similar and are not described in detail.
Referring to fig. 3, a flowchart of a method for performing node association between an SMF entity and a UPF entity according to an embodiment of the present invention is shown, and a specific flowchart is described as follows.
Step 301: the SMF entity determines the interaction mode with the UPF entity to be associated.
In the embodiment of the invention, when the SMF entity needs to be associated with the UPF entity, the SMF entity needs to interact with the UPF entity to be associated, and the SMF entity needs to determine an interaction mode of interacting with the UPF entity. The interaction mode comprises a mode of calling service through an SBI interface for interaction and a mode of carrying out interaction through a PTP interface.
Specifically, the SMF entity may determine an interaction manner with the UPF entity based on the configuration information of the UPF entity, where the configuration manner of the UPF entity includes an interaction manner that the UPF entity can support and a service that the UPF entity can provide, and specifically, may refer to the service shown in the table in the embodiment shown in fig. 2.
Specifically, the SMF entity may also determine an interaction manner with the UPF entity based on its own configuration information, where the configuration information of the SMF entity indicates an interaction manner supported by the SMF entity.
Step 302 a: the SMF entity sends a node association service request message to the UPF entity.
In the embodiment of the invention, when the SMF entity determines to interact with the UPF entity through the SBI, the SMF entity sends a Node Association service Request message, namely Nupf _ Node _ Association _ Setup _ Request, to the UPF entity through the SBI so as to call the Node Association service provided by the UPF entity and perform Node Association with the UPF entity.
Step 303 a: and the UPF entity sends a node association service response message to the SMF entity.
In the embodiment of the invention, 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 a Node Association service response message, namely Nupf _ Node _ Association _ Setup _ response, to the SMF entity.
Step 302 b: the SMF entity sends a node association message to the UPF entity.
In the embodiment of the invention, when the SMF entity determines to interact with the UPF entity through the PTP interface, the SMF entity sends the node association message to the UPF entity through the PTP interface so as to perform node association with the UPF entity.
Step 303 b: and the UPF entity sends a node association response message to the SMF entity.
In the embodiment of the invention, after receiving the node association message, the UPF entity carries out corresponding processing according to the node association message and feeds back a node association response message to the SMF entity.
Step 304: and the SMF entity records the determined interaction mode.
In the embodiment of the invention, after the SMF entity determines the interactive mode with the UPF entity, the determined interactive mode is recorded so that the interactive mode can be acquired in the subsequent session management process. For example, a new node association context is defined, and the determined interaction mode is recorded in the node association context.
Steps 302a and 303a are two different alternatives from steps 302b and 303b, and in the specific implementation process, one of the alternatives may be selected to be executed according to the determination result of the SMF, and the subsequent session modification or release is similar to this, and will not be described in detail later. In addition, the process of initiating node association and the process of recording the interaction mode, 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, so that in an actual process, the two processes may be executed sequentially or simultaneously.
Step 305: and 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 is already recorded in the node association context, the interaction with the UPF entity can be performed in the subsequent interaction process based on the interaction mode recorded in the node association context. For example, when configuration information of a UPF entity needs to be updated, or a node association relationship between the UPF entity and the UPF entity is released, or a packet filter descriptor of the UPF entity needs to be configured, or the packet filter descriptor of the UPF entity is removed, the UPF entity may interact with the UPF entity based on an interaction manner recorded in a node association context.
Step 306 a: the SMF entity sends a node update service request message to the UPF entity.
In the embodiment of the invention, 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 based on the Node Association context, the SMF entity sends a Node Association service Request message, namely Nupf _ Node _ Association _ Update _ Request, to the UPF entity through the SBI so as to call the Node Association service provided by the UPF entity and Update the configuration information of the UPF entity. The node association service request message carries configuration information to be updated.
Step 307 a: the UPF entity sends a node update service response message to the SMF entity.
In the embodiment of the invention, after receiving the Node Update service request message, the UPF entity performs corresponding processing according to the Node Update service request message, and feeds back a Node Update service response message, namely Nupf _ Node _ Association _ Update _ response, to the SMF entity through the SBI interface.
Step 306 b: the SMF entity sends a node update message to the UPF entity.
In the embodiment of the invention, 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, namely sends the node update message to the UPF entity through the N4 interface, so as to update the configuration information of the UPF entity. Wherein, the node update message carries the configuration information to be updated.
Step 307 b: and the UPF entity sends a node update response message to the SMF entity.
In the embodiment of the present invention, after receiving the node update message, the UPF entity performs corresponding processing according to the node update message, and feeds back a node update response message to the SMF entity, that is, sends the node update response message to the SMF entity through the N4 interface.
Step 308 a: the SMF entity sends a node release service request message to the UPF entity.
In the embodiment of the invention, when the SMF entity needs to Release the Node Association relation with the UPF entity and the SMF entity determines to interact with the UPF entity through the SBI based on the Node Association context, the SMF entity releases a service Request message, namely Nupf _ Node _ Association _ Release _ Request, to the UPF entity Node through the SBI so as to call the Node Release service provided by the UPF entity and Release the PDU session provided by the UPF entity.
Step 309 a: and the UPF entity sends a node release service response message to the SMF entity.
In the embodiment of the invention, after receiving the Node Release service request message, the UPF entity performs corresponding processing according to the Node Release service request message, and feeds back a Node Release service response message, namely Nupf _ Node _ Association _ Release _ Reverse, to the SMF entity through the SBI interface.
Step 308 b: the SMF entity sends a node release message to the UPF entity.
In the embodiment of the invention, when the SMF entity releases the node association relation with the UPF entity and 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, namely, the SMF entity initiates an N4 node release message to the UPF entity through the N4 interface so as to release the PDU session in which the UPF entity provides service in the PDU session.
Step 309 b: and the UPF entity sends a node release response message to the SMF entity.
In the embodiment of the present invention, after receiving the session node release message, the UPF entity performs corresponding processing according to the node release message, and feeds back a node release response message to the SMF entity, that is, sends the node release response message to the SMF entity through the N4 interface.
Step 310 a: the SMF entity sends a message filter descriptor providing service request message to the UPF entity.
In the embodiment of the invention, 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 based on the node association context, the SMF entity provides a service Request message, namely Nupf _ PFD _ Mgt _ Provision _ Request, to the message filtering descriptor of the UPF entity through the SBI so as to call the message filtering descriptor provided by the UPF entity to provide service and configure the message filtering descriptor for the UPF entity.
Step 311 a: the UPF entity sends a message filter descriptor providing service response message to the SMF entity.
In the embodiment of the present invention, after receiving the message filter descriptor service Provision request message, the UPF entity performs corresponding processing according to the message filter descriptor service Provision request message, and feeds back a message filter descriptor service Provision response message, that is, Nupf _ PFD _ Mgt _ Provision _ reply, to the SMF entity through the SBI interface.
Step 310 b: the SMF entity sends a message filter descriptor providing message to the UPF entity.
In the embodiment of the invention, 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 PTP interface based on the node association context, the SMF entity sends the message filtering descriptor providing message to the UPF entity through the PTP interface, namely, the SMF entity initiates the N4 message filtering descriptor providing message to the UPF entity through the N4 interface, so as to configure the message filtering descriptor for the UPF entity.
Step 311 b: the UPF entity sends a message filter descriptor providing response message to the SMF entity.
In the embodiment of the present invention, after receiving the session packet filtering descriptor providing message, the UPF entity performs corresponding processing according to the packet filtering descriptor providing message, and feeds back the packet filtering descriptor providing response message to the SMF entity, that is, sends the packet filtering descriptor providing response message to the SMF entity through the N4 interface.
Step 312 a: the SMF entity sends a message filter descriptor removal service request message to the UPF entity.
In the embodiment of the present invention, when the SMF entity needs to Remove a Packet Filter 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 removes a service Request message, that is, Nupf _ PFD _ Mgt _ Remove _ Request, from the UPF entity packet filter descriptor through the SBI interface, so as to invoke a packet filter descriptor removal service provided by the UPF entity, so as to Remove the packet filter descriptor already configured for the UPF entity.
Step 313 a: the UPF entity sends a message filter descriptor removal service response message to the SMF entity.
In the embodiment of the present invention, after receiving the message filter descriptor removal service request message, the UPF entity performs corresponding processing according to the message filter descriptor removal service request message, and feeds back a message filter descriptor removal service response message, that is, Nupf _ PFD _ Mgt _ Remove _ response, to the SMF entity through the SBI interface.
Step 312 b: the SMF entity sends a message filter descriptor removal message to the UPF entity.
In the embodiment of the present invention, when the SMF entity needs to remove the packet 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 packet filtering descriptor removal message to the UPF entity through the PTP interface, that is, initiates an N4 packet filtering descriptor removal message to the UPF entity through the N4 interface, so as to remove the packet filtering descriptor already configured for the UPF entity.
Step 313 b: and the UPF entity sends a message filtering descriptor removal response message to the SMF entity.
In the embodiment of the present invention, after receiving the session packet filter descriptor removal message, the UPF entity performs corresponding processing according to the packet filter descriptor removal message, and feeds back a packet filter descriptor removal response message to the SMF entity, that is, sends the packet filter descriptor removal response message to the SMF entity through the N4 interface.
It should be noted that the related process of the node association as described in the embodiment shown in fig. 3, such as the establishment process of the node association, generally occurs before the PDU session establishment process. Therefore, the interaction mode of the UPF entity recorded in the node association context can be used by the SMF entity to determine the interaction mode with the UPF entity in the PDU session establishment process.
Fig. 4 is a schematic flow chart of a UPF discovery process according to an embodiment of the present invention.
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 invention, when an SMF entity wants to search for an available UPF entity in a network, the SMF entity may send a first request message to the SMF, where the first request message is used to request to acquire configuration information of a UPF entity that meets a condition, where the condition may include that the UPF entity can provide a specified UPF service, and/or that the UPF entity can support a specified interaction mode.
Optionally, the UPF entity supporting the SBI interface and the UPF entity supporting the PTP interface may be divided into two different types, for example, the UPF entity supporting the SBI interface may be a first type, and the UPF entity supporting the PTP interface may be a second type, and then the condition may also be that the UPF entity is a designated type.
Specifically, the interaction manner may include a manner of interacting through a PTP interface, i.e., an N4 interface, between the SMF entity and the UPF entity, and a manner of interacting through a service provided by invoking the UPF entity through an SBI interface between the SMF entity and the UPF entity. Then, the specified interaction mode may be a mode capable of supporting a PTP interface to interact, or may also be a mode capable of supporting an SBI interface to interact, or may also be a mode capable of supporting a PTP interface and an SBI interface to interact simultaneously.
Step 402: the NRF entity finds at least one UPF entity among the registered UPF entities that satisfies the condition.
In this embodiment of the present invention, after receiving the first request message, the NRF entity performs a search in the registered UPF entities stored in the NRF entity, so as to search for at least one UPF entity that meets the conditions required by the SMF.
Specifically, before the NRF entity performs the search, the NRF entity also performs authorization verification on the SMF entity, and whether to provide the SMF entity with the UPF entity satisfying the condition is verified, which is not described herein in detail since the process of authorization verification belongs to the scope of the prior art.
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 invention, after finding the at least one UPF entity meeting the above condition, the NRF entity sends a first response message carrying the configuration information of the at least one UPF entity to the SMF entity, so as to send the configuration information of the at least one UPF entity to the SMF entity.
Step 404: and the SMF entity updates the self-stored UPF entity list based on the first response message.
In a specific implementation process, the steps 401 to 403 may include the following two implementation manners.
Referring to fig. 5, a first implementation manner of steps 401 to 403 is shown, in which steps 501 to 503 correspond to steps 401 to 403 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 this embodiment of the present invention, the first request message may be an NF discovery request message. Since the service architecture is already adopted in the control plane, the SMF entity may invoke the NF discovery service, that is, the nrrf _ NFDiscovery _ Request, provided by the NRF entity through the SBI interface between the SMF entity and the NRF entity to implement discovery of the UPF entity.
The nrf _ NFDiscovery _ Request may carry an expected NF service name, an NF entity type, and a type of the NF entity, where the NF service name is an UPF service, the NF entity type is an UPF entity, and the type of the NF entity is an SMF entity. Of course, the nrf _ NFDiscovery _ Request may also carry a condition that a UPF entity that the SMF entity wants to find needs to satisfy, that is, a specified UPF service can be provided, and/or a specified interaction mode can be supported.
Step 502: the NRF entity finds at least one UPF entity among the registered UPF entities that satisfies the condition.
Step 503: the NRF entity sends a NF discovery response message to the SMF entity, and the SMF entity receives the NF discovery response message.
In this embodiment of the present invention, the first response message may be an NF discovery response message. Specifically, the NRF entity may call a Response service corresponding to the NF discovery service, that is, nrrf _ NFDiscovery _ Request Response, to feed back the configuration information of the at least one UPF entity that satisfies the condition to the UPF entity.
For example, if the NF discovery request message called by the SMF entity is used to request to acquire a UPF entity supporting an SBI interface, the configuration information of the UPF entity included in the NF discovery response message fed back by the NRF entity carries, in addition to the conventional FQDN, IP address, and URL to be provided, the interaction methods that these UPF entities can support and the services that these UPF entities can provide to the SMF entity.
Step 504: the SMF entity updates the UPF entity list stored by the SMF entity based on the NF discovery response message.
After receiving the NF discovery response message, the SMF entity updates the UPF entity and the corresponding configuration information indicated in the NF discovery response message to the UPF entity list stored in the SMF entity.
Referring to fig. 6, a second implementation manner of steps 401 to 403 is shown, in which steps 601 to 603 correspond to steps 401 to 403 one by one in sequence.
Step 601: and the SMF entity sends the NF status subscription message to the SMF entity, and the SMF entity receives the NF status subscription message.
In this embodiment of the present invention, the first request message may be an NF status subscription message. Specifically, the SMF entity may invoke an NF status subscription service provided by the NRF entity, that is, an nrrf _ NFDiscovery _ nfstatussussubscribe, through an SBI interface between the SMF entity and the NRF entity, to subscribe to the UPF entity that satisfies the condition. Specifically, the subscription means that after the NRF entity receives the NF status subscription message, the NRF entity sends the configuration information of the UPF entity that is currently registered and satisfies the condition to the SMF entity, and when a new UPF entity is registered and the UPF entity satisfies the condition, the NRF entity also actively sends the configuration information of the UPF entity to the SMF entity.
The nfrf _ NFDiscovery _ NFStatusSubscribe may also carry an expected NF service name, an NF entity type, and a type of the NF entity, where the NF service name is a UPF service, the NF entity type is a UPF entity, and the type of the NF entity is an SMF entity. However, the nrf _ NFDiscovery _ Request may also carry a condition that a UPF entity that the SMF entity wants to find needs to satisfy, that is, a specified UPF service can be provided, and/or a specified interaction mode can be supported.
Step 602: the NRF entity finds at least one UPF entity among the registered UPF entities that satisfies the condition.
Step 603: the NRF entity sends a NF status notification message to the SMF entity, and the SMF entity receives the NF status notification message.
In this embodiment of the present invention, the first response message may be an NF status notification message. Specifically, the NRF entity may invoke its own NF status notification service, that is, nrrf _ NFDiscovery nfstatunotify, to notify the UPF entity of the configuration information of at least one UPF entity that satisfies the condition.
For example, if the SMF entity does not explicitly indicate the required interface capability at the time of subscription, the UPF entity of the at least one UPF entity provided in the nrf _ NFManagement _ nfstatusionnotify may include a UPF entity supporting an SBI interface or may be a UPF entity supporting a PTP interface, and of course, the interface that can be supported by the UPF entity and the service that can be provided need to be explicitly indicated in the nrf _ NFManagement _ nfstatusionnotify.
Step 604: and 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 invention, after a new UPF entity, that is, a second UPF entity is deployed, the second UPF entity needs to be registered in the NRF, and then the second UPF entity may send a NF registration request message to the NRF entity. The NF registration request message may carry configuration information of the second UPF entity, for example, the NF registration request message may include, in addition to the FQDN or the IP address of the second UPF entity, an interaction mode that the second UPF entity can support, and a service that can be provided.
For example, if the second UPF entity supports the SBI interface, the second UPF entity may call the nrrf _ NFManagement _ NFRegister Request of the NRF entity, informing the NRF entity of its own configuration information.
Step 605: the NRF entity stores 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 invention, the NRF entity stores the configuration information of the second UPF entity carried by the NF registration request message and feeds back a NF registration response message to the second UPF entity, wherein the NF registration response message is used for notifying that the registration of the second UPF entity is accepted by the NRF entity, namely the registration is successful. Of course, when the registration of the second UPF is in problem, the NRF entity may also send 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 of the failure.
Following the above 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 may also call its nrrf _ NFManagement _ NF Register response to notify the NRF entity of the registration result.
Step 607: the NRF entity determines whether the second UPF entity satisfies the above condition.
Step 608: when the determination result of step 607 is yes, the NRF entity transmits a NF status notification message to the SMF entity, and the SMF entity receives the NF status notification message.
In the embodiment of the invention, after the second UPF entity is successfully registered, the NRF entity determines whether the second UPF entity meets the conditions in the NF status subscription message, and if so, the NRF entity also sends an NF status notification message to the SMF entity, and the NF status notification message carries the configuration information of the second UPF entity.
For example, the SMF entity indicates to subscribe to a UPF entity supporting an SBI interface when subscribing, or if the SMF entity does not explicitly indicate required interface capabilities when subscribing, the NRF entity determines that the configuration information of the second UPF entity satisfies the above-mentioned subscription condition of the SMF entity, and the NRF entity invokes its own NRF _ NFManagement _ nfstatusionnotify to send the configuration information of the second UPF entity to the SMF entity.
Step 609: and the SMF entity updates the UPF entity list stored by the SMF entity based on the NF status notification message.
After receiving the NF status notification message, the SMF entity updates the UPF entity and the corresponding configuration information indicated in the NF status notification message to a UPF entity list stored in the SMF entity. For example, the SMF entity may update the second UPF entity and the configuration information of the second UPF entity into its own stored UPF entity list.
Referring to fig. 7, based on the same inventive concept, an embodiment of the present invention 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, configured to determine, for a first UPF entity in at least one UPF entity, an interaction manner for interacting with the first UPF entity; the configuration information of one UPF entity comprises an interaction mode supported by the UPF entity, wherein the interaction mode comprises a mode of interacting through a point-to-point PTP interface and a mode of calling service for interacting through a service SBI interface;
an executing unit 703, configured to, when it is determined that the first UPF entity interacts with the SBI interface, invoke, through the SBI interface, a session establishment service provided by the first UPF entity, so as to establish a PDU session in the PDU session, where the PDU session is served by the first UPF entity; or when the first UPF entity is determined 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, so that the PDU session served by the first UPF entity in the PDU session is established.
Optionally, the selecting unit 701 is specifically configured to:
and selecting at least one UPF entity meeting the conditions from the list according to the UPF entity list stored by the SMF entity and the configuration information of the UPF entities in the list, wherein the conditions comprise that the specified UPF service can be provided and/or the specified interaction mode can be supported.
Optionally, the SMF entity further includes an updating unit 704;
the execution unit 703 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, and the condition includes that a specified UPF service can be provided and/or a specified interaction mode can be supported; receiving a NF status notification message sent by the NRF entity, wherein the NF status notification message carries configuration information of at least one UPF entity which is present in the NRF entity or newly added and meets the conditions;
and the updating unit 704 is configured to update the UPF entity list stored by the SMF entity according to the NF status notification message.
Optionally, the selecting unit 701 is specifically configured to:
sending a NF discovery request message to an NRF entity, wherein the NF discovery request message is used for requesting the NRF entity to provide a UPF entity meeting conditions, and the conditions comprise that a specified UPF service can be provided and/or a specified interaction mode can be supported;
receiving NF discovery response message sent by the NRF entity, wherein the NF discovery response message carries the configuration information of the UPF entity meeting the condition;
at least one UPF entity is selected from the UPF entities that satisfy the condition.
Optionally, the determining unit 702 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 interactive mode interacting with a first UPF entity based on the configuration information of the SMF entity, wherein the configuration information of the SMF entity indicates the interactive mode supported by the SMF entity; or,
and determining an interactive mode of interacting with the first UPF entity based on the node association context, wherein the node association context indicates the interactive mode of interacting with the first UPF entity determined by the SMF entity.
Optionally, the configuration information of the UPF entity includes at least one of the following information:
a fully qualified domain name FQDN of the UPF entity;
the network protocol IP address of the UPF entity;
services that the UPF entity is capable of providing;
the interaction mode supported by the UPF entity;
the area identification of the SMF entity that the UPF entity can serve.
Optionally, the execution unit 703 is further configured to:
recording the determined interactive mode in the context of the PDU session served by the first UPF entity; or the like, or a combination thereof,
and recording the determined interaction mode of the first UPF entity in the context of the terminal corresponding to the PDU session.
Optionally, the execution unit 703 is further configured to:
when a PDU session served by a first UPF entity needs to be modified, acquiring an interaction mode recorded in a context and the first UPF entity; the context is the context of the PDU conversation or the context of the terminal corresponding to the PDU conversation;
if the acquired interaction mode is a mode for carrying out interaction by calling service through an SBI interface, calling session modification service provided by the first UPF entity through the SBI interface so as to modify the PDU session of the first UPF entity service; or,
and if the acquired interaction mode is the interaction mode through the PTP interface, sending a session modification message to the first UPF entity through the PTP interface so as to modify the PDU session served by the first UPF entity.
Optionally, the execution unit 703 is further configured to:
when a PDU session served by a first UPF entity needs to be released, acquiring an interaction mode recorded in a context and the first UPF entity; the context is the context of the PDU conversation or the context of the terminal corresponding to the PDU conversation;
if the acquired interaction mode is a mode for carrying out interaction by calling service through an SBI interface, calling session release service provided by the first UPF entity through the SBI interface so as to release the PDU session served by the first UPF entity; or,
and if the acquired interaction mode is the interaction mode through the PTP interface, sending a session release message to the first UPF entity through the PTP interface so as to release the PDU session served by the first UPF entity.
The SMF entity may be configured to execute steps performed by the SMF entity in the embodiments shown in fig. 2 to 6, and therefore, for functions and the like that can be realized by each functional module of the device, reference may be made to the description of the embodiments shown in fig. 2 to 6, which is not described in detail. Although fig. 7 also shows the update unit 704, it is not an essential functional unit and is therefore shown by a dotted line.
Referring to fig. 8, based on the same inventive concept, an embodiment of the present invention provides an SMF entity, including:
a determining unit 801, configured to determine an interaction mode with a UPF entity to be associated, where the interaction mode includes a mode of performing interaction through a PTP interface and a mode of performing interaction by invoking a service through an SBI interface;
an execution unit 802, configured to, when the SMF entity determines to interact with the UPF entity through the SBI interface, invoke a node association service provided by the UPF entity through the SBI interface, so as 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 so as to perform node association with the UPF entity.
Optionally, the determining unit 801 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,
and determining an interactive mode interacting with the UPF entity based on the configuration information of the SMF entity, wherein the configuration information of the SMF entity indicates the interactive mode supported by the SMF entity.
Optionally, the SMF entity further includes a recording unit 803, configured to:
and recording the determined interaction mode with the UPF entity in the node association context.
Optionally, the execution unit 802 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 acquired interaction mode is a mode of carrying out interaction by calling service through an SBI interface, calling node update service provided by the UPF entity through the SBI interface so as to update the configuration information of the UPF entity; or,
and if the acquired interaction mode is the interaction mode through the PTP interface, sending a node update message to the UPF entity through the PTP interface so as to update the configuration information of the UPF entity.
Optionally, the execution unit 802 is further configured to:
when the node association relation with the UPF entity needs to be released, acquiring the interaction mode with the UPF entity recorded in the node association context;
if the acquired interaction mode is a mode of calling service for interaction through an SBI interface, calling a node release service provided by the UPF entity through the SBI interface so as to remove the node association relation with the UPF entity; or,
and if the acquired interaction mode is the interaction mode through the PTP interface, sending a node release message to the UPF entity through the PTP interface so as to release the node association relation with the UPF entity.
Optionally, the execution unit 802 is further configured to:
when a message filtering descriptor of a UPF entity needs to be configured, acquiring an interaction mode with the UPF entity recorded in a node association context;
if the acquired interaction mode is a mode of calling service for interaction through an SBI interface, calling a message filtering descriptor provided by the UPF entity through the SBI interface to provide service so as to configure the message filtering descriptor of the UPF entity; or,
and if the acquired interaction mode is the interaction mode through the PTP interface, sending a message filtering descriptor providing message to the UPF entity through the PTP interface so as to configure the message filtering descriptor of the UPF entity.
Optionally, the execution unit 802 is further configured to:
when a message filtering descriptor of the UPF entity needs to be removed, acquiring an interaction mode with the UPF entity recorded in a node association context;
if the acquired interaction mode is a mode of calling service for interaction through an SBI interface, calling a message filtering descriptor removal service provided by the UPF entity through the SBI interface so as to remove the message filtering descriptor of the UPF entity; or,
and if the acquired interaction mode is the interaction mode through the PTP interface, sending a message filtering descriptor removing message to the UPF entity through the PTP interface so as to remove the message filtering descriptor of the UPF entity.
The SMF entity may be configured to execute steps executed by the NRF entity in the embodiments shown in fig. 2 to 6, and therefore, for functions and the like that can be realized by each functional module of the device, reference may be made to the description of the embodiments shown in fig. 2 to 6, which is not described in detail. Note that although fig. 8 also shows the determination unit 803, it is not an essential functional unit and is therefore shown by a broken line.
Referring to fig. 9, based on the same inventive concept, an embodiment of the present invention provides an NRF entity, including:
a transceiver 901, configured to receive a first request message sent by an SMF entity, where the first request message is used to request to acquire configuration information of a UPF entity that meets conditions, where the conditions include that a specified UPF service can be provided and/or a specified interaction mode can be supported, and the interaction mode includes a mode of performing interaction through a point-to-point PTP interface and a mode of performing interaction through a service invoked by a serving SBI interface;
a searching unit 902, configured to search at least one UPF entity that meets a condition in the registered UPF entities;
the transceiving unit 901 is further configured to send a first response message to the SMF entity, where the first response message carries the configuration information of the at least one UPF entity.
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 an NF status subscription message, the NF status subscription message is used for subscribing to a UPF entity meeting a condition, and the first response message is an NF status notification message.
Optionally, the transceiver 901 is further configured to:
receiving a NF registration request message sent by a second UPF entity, wherein the NF registration request message carries configuration information of the second UPF entity, and the configuration information comprises services which can be provided by the second UPF entity and/or interaction modes which can be supported by the second UPF entity;
storing configuration information of a second UPF entity;
a NF registration response message is sent to the second UPF entity to inform 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 the second UPF entity satisfies a condition;
the transceiving unit 901 is further configured to send an NF status notification message to the SMF entity if the determination result is yes, where the NF status notification message carries the configuration information of the second UPF entity.
Optionally, the configuration information of the UPF entity includes at least one of the following information:
a fully qualified domain name FQDN of the UPF entity;
the network protocol IP address of the UPF entity;
services that the UPF entity is capable of providing;
the interaction mode supported by the UPF entity;
the area identification of the SMF entity that the UPF entity can serve.
The SMF entity may be configured to execute steps executed by the NRF entity in the embodiments shown in fig. 2 to 6, and therefore, for functions and the like that can be realized by each functional module of the device, reference may be made to the description of the embodiments shown in fig. 2 to 6, which is not described in detail. Although the determination unit 903 is also shown in fig. 9, it is not an essential functional unit and is therefore shown by a dotted line.
Based on the same inventive concept, an embodiment of the present invention provides a communication device, including:
at least one processor 1001, the at least one processor 1001 being adapted to carry out the steps of the method provided by the embodiments shown in fig. 2-6 when executing a computer program stored in a memory.
Optionally, at least one of the processors 1001 may specifically include a Central Processing Unit (CPU), an Application Specific Integrated Circuit (ASIC), one or more integrated circuits for controlling program execution, a hardware circuit developed by using a Field Programmable Gate Array (FPGA), or a baseband processor.
Optionally, at least one processor 1001 may include at least one processing core.
Optionally, the device further includes a memory 1002, and the memory 1002 may include a Read Only Memory (ROM), a Random Access Memory (RAM), and a disk memory. The memory 1002 is used for storing data required by the at least one processor 1001 in operation. The number of the memories 1002 is one or more. The memory 1002 is shown together in fig. 10, but it should be noted that the memory 1002 is not an optional functional block, and is shown by a dotted line in fig. 10.
Based on the same inventive concept, the embodiments of the present invention provide a computer storage medium storing computer instructions, which, when executed on a computer, cause the computer to perform the method provided by the embodiments shown in fig. 2 to 6.
In particular implementations, computer storage media include: various storage media capable of storing program codes, such as a universal serial Bus flash drive (USB), a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, and an optical disk.
In embodiments of the present invention, it should be understood that the disclosed apparatus and methods may be implemented in other ways. For example, the above-described embodiments of the apparatus are merely illustrative, and for example, the unit or the division of the unit is only one type of division of logic functions, and there may be other ways of dividing the actual implementation, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be electrical or in other forms.
The functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may be an independent physical module.
The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. With this understanding, all or part of the technical solutions of the embodiments of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes instructions for causing a computer device, such as a personal computer, a server, or a network device, or a processor (processor), to execute all or part of the steps of the methods according to the embodiments of the present invention. And the aforementioned storage medium includes: various media that can store program codes, such as a universal serial bus flash drive (usb flash drive), a removable hard disk, a ROM, a RAM, a magnetic disk, or an optical disk.
The above embodiments are only used to describe the technical solutions of the present application in detail, but the above description of the embodiments is only used to help understanding the method of the embodiments of the present invention, and should not be construed as limiting the embodiments of the present invention. Variations or substitutions that may be readily apparent to one skilled in the art are intended to be included within the scope of the embodiments of the present invention.

Claims (46)

1. A Packet Data Unit (PDU) session management method, comprising:
a Session Management Function (SMF) entity selects at least one User Plane Function (UPF) entity for a PDU session to be established;
aiming at a first UPF entity in the at least one UPF entity, the SMF entity determines an interactive mode of interacting with the first UPF entity; the configuration information of one UPF entity comprises interaction modes supported by the UPF entity, wherein the interaction modes comprise a mode of interacting through a point-to-point PTP interface and a mode of calling service for interacting through a service SBI interface;
when the SMF entity determines to interact with the first UPF entity through the SBI interface, the SMF entity calls session establishment services provided by the first UPF entity through the SBI interface so as to establish a PDU session in the PDU session, wherein the PDU session is served by the first UPF entity; or,
and 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 so as to establish the PDU session in which the first UPF entity provides service in the PDU session.
2. The method of claim 1, wherein the SMF entity selecting at least one UPF entity for the PDU session to be established, comprising:
and according to the UPF entity list stored by the SMF entity and the configuration information of the UPF entities in the list, the SMF entity selects the at least one UPF entity meeting the conditions from the list, wherein the conditions comprise that the specified UPF service can be provided and/or the specified interactive mode can be supported.
3. The method of claim 2, wherein the method further comprises:
the SMF entity sends NF status subscription information to the NRF entity, wherein the NF status subscription information is used for subscribing UPF entities meeting conditions, and the conditions comprise that appointed UPF service can be provided and/or appointed interaction modes can be supported;
the SMF entity receives a NF status notification message sent by the NRF entity, wherein the NF status notification message carries configuration information of at least one UPF entity which is already or newly added in the NRF entity and meets the condition;
and the SMF entity updates a self-stored UPF entity list according to the NF state notification message.
4. The method of claim 1, wherein the SMF entity selecting at least one UPF entity for the PDU session to be established, comprising:
the SMF entity sends a NF discovery request message to a NRF entity, wherein the NF discovery request message is used for requesting the NRF entity to provide a UPF entity meeting conditions, and the conditions comprise that a specified UPF service can be provided and/or a specified interaction mode can be supported;
the SMF entity receives a NF discovery response message sent by the NRF entity, wherein the NF discovery response message carries the configuration information of the UPF entity meeting the condition;
the SMF entity selects the at least one UPF entity from the UPF entities meeting the condition.
5. The method of claim 1, wherein the SMF entity determining the manner of interaction with the first UPF entity comprises:
the SMF entity determines an interactive mode for interacting with the first UPF entity based on the configuration information of the first UPF entity; or,
the SMF entity determines an interactive mode interacting with the first UPF entity based on configuration information of the SMF entity, wherein the configuration information of the SMF entity indicates the interactive mode supported by the SMF entity; or,
and the SMF entity determines an interactive mode of interacting with the first UPF entity based on a node association context, wherein the node association context indicates the interactive mode of interacting with the first UPF entity determined by the SMF entity.
6. The method according to any of claims 1-5, wherein the configuration information of the UPF entity comprises at least one of the following information:
a fully qualified domain name FQDN of the UPF entity;
the network protocol IP address of the UPF entity;
services that the UPF entity is capable of providing;
the interaction mode supported by the UPF entity;
the area identification of the SMF entity that the UPF entity can serve.
7. The method of claim 1, wherein after the SMF entity determines the manner of interaction with the first UPF entity, the method further comprises:
the SMF entity records the determined interactive mode in the context of the PDU session served by the first UPF entity; or,
and the SMF entity records the determined interaction mode of the first UPF entity in the context of the terminal corresponding to the PDU session.
8. The method of claim 7, wherein the method further comprises:
when the PDU session served by the first UPF entity needs to be modified, the SMF entity acquires an interaction mode recorded in a context and the first UPF entity; 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 mode for carrying out interaction by calling service through the SBI, the SMF entity calls session modification service provided by the first UPF entity through the SBI to modify the PDU session of the first UPF entity service; or,
and if the acquired interaction mode is the interaction mode through the PTP interface, the SMF entity sends a session modification message to the first UPF entity through the PTP interface so as to modify the PDU session served by the first UPF entity.
9. The method of claim 7, wherein the method further comprises:
when the PDU session served by the first UPF entity needs to be released, the SMF entity acquires an interaction mode recorded in a context and the first UPF entity; 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 mode for carrying out interaction by calling service through the SBI, the SMF entity calls session release service provided by the first UPF entity through the SBI so as to release the PDU session of the first UPF entity service; or,
and if the acquired interaction mode is the interaction mode through the PTP interface, the SMF entity sends a session release message to the first UPF entity through the PTP interface so as to release the PDU session served by the first UPF entity.
10. A method for node association between an SMF entity and a UPF entity is characterized by comprising the following steps:
the SMF entity determines an interaction mode with a UPF entity to be associated, wherein the interaction mode comprises a mode of interaction through a PTP interface and a mode of interaction through service calling through an SBI interface;
when the SMF entity determines to interact with the UPF entity through the SBI, the SMF entity calls a node association service provided by the UPF entity through the SBI so as 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 so as to perform node association with the UPF entity.
11. The method of claim 10, wherein the SMF entity determining the manner of interaction with the UPF entity comprises:
the SMF entity determines an interaction mode for interacting with the first UPF entity based on the configuration information of the UPF entity, or,
and the SMF entity determines an interactive mode interacting with the UPF entity based on configuration information of the SMF entity, wherein the configuration information of the SMF entity indicates the interactive mode supported by the SMF entity.
12. The method of claim 10, wherein after the SMF entity determines the manner of interaction with the UPF entity to be associated, the method further comprises:
and the SMF entity records the determined interaction mode with the UPF entity in the context of node association.
13. The method of claim 12, wherein the method further comprises:
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 acquired interaction mode is a mode of carrying out interaction by calling service through the SBI, the SMF entity calls node updating service provided by the UPF entity through the SBI so as to update the configuration information of the UPF entity; or,
and if the acquired interaction mode is the interaction mode through the PTP interface, the SMF entity sends a node update message to the UPF entity through the PTP interface so as to update the configuration information of the UPF entity.
14. The method of claim 12, wherein the method further comprises:
when the node association relation between the SMF entity and the UPF entity needs to be released, the SMF entity acquires the interaction mode with the UPF entity recorded in the node association context;
if the acquired interaction mode is a mode of carrying out interaction by calling service through the SBI, the SMF entity calls a node release service provided by the UPF entity through the SBI so as to release the node association relation with the UPF entity; or,
and if the acquired interaction mode is the interaction mode through the PTP interface, the SMF entity sends a node release message to the UPF entity through the PTP interface so as to release the node association relation between the SMF entity and the UPF entity.
15. The method of claim 12, wherein the method further comprises:
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 acquired interaction mode is a mode of carrying out interaction by calling service through the SBI, the SMF entity calls a message filtering descriptor provided by the UPF entity through the SBI to provide service so as to configure the message filtering descriptor of the UPF entity; or,
and if the acquired interaction mode is the interaction mode through the PTP interface, the SMF entity sends a message filtering descriptor providing message to the UPF entity through the PTP interface so as to configure the message filtering descriptor of the UPF entity.
16. The method of claim 12, wherein the method further comprises:
when the message filtering descriptor of the UPF entity needs to be removed, the SMF entity acquires the interaction mode with the UPF entity recorded in the node association context;
if the acquired interaction mode is a mode of carrying out interaction by calling service through the SBI, the SMF entity calls a message filtering descriptor removal service provided by the UPF entity through the SBI so as to remove the message filtering descriptor of the UPF entity; or,
and if the acquired interaction mode is the interaction mode through the PTP interface, the SMF entity sends a message filtering descriptor removing message to the UPF entity through the PTP interface so as to remove the message filtering descriptor of the UPF entity.
17. A UPF entity discovery method, comprising:
the method comprises the steps that an NRF entity receives a first request message sent by an SMF entity, wherein the first request message is used for requesting to acquire configuration information of a UPF entity meeting conditions, the conditions comprise that a specified UPF service can be provided and/or a specified interaction mode can be supported, and the interaction mode comprises a mode of interacting through a point-to-point PTP interface and a mode of interacting through service calling of a service through a service-oriented SBI interface;
the NRF entity searches at least one UPF entity meeting the condition in the registered UPF entities;
and the NRF entity sends a first response message to the SMF entity, wherein the first response message carries the configuration information of the at least one UPF entity.
18. The method of claim 17, wherein the first request message is an NF discovery request message and the first response message is an NF discovery response message.
19. The method of 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 satisfies a condition, and the first response message is a NF status notification message.
20. The method of claim 17, wherein the method further comprises:
the NRF entity receives a NF registration request message sent by a second UPF entity, wherein the NF registration request message carries configuration information of the second UPF entity, and the configuration information comprises services which can be provided by the second UPF entity and/or interaction modes which 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 inform the second UPF entity that registration is accepted.
21. The method of claim 20, wherein the method further comprises:
the NRF entity determining whether the second UPF entity satisfies the condition;
and if the result is positive, the NRF entity sends a NF status notification message to the SMF entity, wherein the NF status notification message carries the configuration information of the second UPF entity.
22. The method according to any of claims 17-21, wherein the configuration information of the UPF entity comprises at least one of the following information:
a fully qualified domain name FQDN of the UPF entity;
the network protocol IP address of the UPF entity;
services that the UPF entity is capable of providing;
the interaction mode supported by the UPF entity;
the area identification of the SMF entity that the UPF entity can serve.
23. An SMF entity, comprising:
the selection unit is used for selecting at least one user plane function UPF entity for the PDU session to be established;
a determining unit, configured to determine, for a first UPF entity in the at least one UPF entity, an interaction manner for interacting with the first UPF entity; the configuration information of one UPF entity comprises interaction modes supported by the UPF entity, wherein the interaction modes comprise a mode of interacting through a point-to-point PTP interface and a mode of calling service for interacting through a service SBI interface;
an execution unit, configured to, when it is determined that the PDU session is interacted with the first UPF entity through the SBI interface, invoke, through the SBI interface, a session establishment service provided by the first UPF entity, so as to establish the PDU session serviced by the first UPF entity in the PDU session; or when the interaction with the first UPF entity through the PTP interface is determined, sending a session establishment message to the first UPF entity through the PTP interface so as to establish the PDU session in which the service is provided by the first UPF entity in the PDU session.
24. The SMF entity of claim 23, wherein said selection unit is specifically configured to:
and selecting the at least one UPF entity meeting the conditions from the list according to the UPF entity list stored by the SMF entity and the configuration information of the UPF entities in the list, wherein the conditions comprise that the specified UPF service can be provided and/or the specified interaction mode can be supported.
25. The SMF entity of claim 24, wherein the SMF entity further comprises an update unit;
the execution unit is further configured to send a 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, and the condition includes that a specified UPF service can be provided and/or a specified interaction mode can be supported; receiving a NF status notification message sent by the NRF entity, wherein the NF status notification message carries configuration information of at least one UPF entity which is already or newly added in the NRF entity and meets the condition;
and the updating unit is used for updating the UPF entity list stored in the SMF entity according to the NF status notification message.
26. The SMF entity of claim 23, wherein said selection unit is specifically configured to:
sending a NF discovery request message to a NRF entity, wherein the NF discovery request message is used for requesting the NRF entity to provide a UPF entity meeting conditions, and the conditions comprise that a specified UPF service can be provided and/or a specified interaction mode can be supported;
receiving a NF discovery response message sent by the NRF entity, wherein the NF discovery response message carries the configuration information of the UPF entity meeting the condition;
and selecting the at least one UPF entity from the UPF entities meeting the condition.
27. The SMF entity of claim 23, wherein said 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 interactive mode 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 interactive mode supported by the SMF entity; or,
and determining an interactive mode of interacting with the first UPF entity based on a node association context, wherein the node association context indicates the interactive mode of interacting with the first UPF entity determined by the SMF entity.
28. The SMF entity of claim 23, wherein the configuration information of the UPF entity comprises at least one of:
a fully qualified domain name FQDN of the UPF entity;
the network protocol IP address of the UPF entity;
services that the UPF entity is capable of providing;
the interaction mode supported by the UPF entity;
the area identification of the SMF entity that the UPF entity can serve.
29. The SMF entity of claim 23, wherein the execution unit is further to:
recording the determined interaction mode in the context of the PDU session served by the first UPF entity; or,
and recording the determined interaction mode of the first UPF entity in the context of the terminal corresponding to the PDU session.
30. The SMF entity of claim 29, wherein the execution unit is further to:
when the PDU session of the first UPF entity service needs to be modified, the interaction mode recorded in the context and the first UPF entity is obtained; 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 mode for carrying out interaction by calling service through the SBI, calling session modification service provided by the first UPF entity through the SBI to modify the PDU session of the first UPF entity service; or,
and if the acquired interaction mode is the interaction mode through the PTP interface, sending a session modification message to the first UPF entity through the PTP interface so as to modify the PDU session served by the first UPF entity.
31. The SMF entity of claim 29, wherein the execution unit is further to:
when the PDU session served by the first UPF entity needs to be released, acquiring the interaction mode recorded in the context and the first UPF entity; 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 mode for carrying out interaction by calling service through the SBI, calling session release service provided by the first UPF entity through the SBI to release the PDU session of the first UPF entity service; or,
and if the acquired interaction mode is the interaction mode through the PTP interface, sending a session release message to the first UPF entity through the PTP interface so as to release the PDU session served by the first UPF entity.
32. An SMF entity, comprising:
the device comprises a determining unit, a determining unit and a judging unit, wherein the determining unit is used for determining an interaction mode of a UPF entity to be associated, and the interaction mode comprises a mode of carrying out interaction through a PTP interface and a mode of calling service for interaction through an SBI interface;
the execution unit is used for calling the 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 SBI interface; 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 so as to perform node association with the UPF entity.
33. The SMF entity of claim 32, wherein said 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,
and determining an interactive mode interacting with the UPF entity based on the configuration information of the SMF entity, wherein the configuration information of the SMF entity indicates the interactive mode supported by the SMF entity.
34. The SMF entity of claim 32, wherein said SMF entity further comprises a recording unit for:
and recording the determined interaction mode with the UPF entity in the node association context.
35. The SMF entity of claim 34, wherein the execution unit is further 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 acquired interaction mode is a mode of carrying out interaction by calling service through the SBI, calling node update service provided by the UPF entity through the SBI to update the configuration information of the UPF entity; or,
and if the acquired interaction mode is the interaction mode through the PTP interface, sending a node update message to the UPF entity through the PTP interface so as to update the configuration information of the UPF entity.
36. The SMF entity of claim 34, wherein the execution unit is further to:
when the node association relation between the UPF entity and the node is required to be released, acquiring the interaction mode of the UPF entity and the node association context;
if the acquired interaction mode is a mode of carrying out interaction by calling service through the SBI, calling node release service provided by the UPF entity through the SBI to remove the node association relation with the UPF entity; or,
and if the acquired interaction mode is the mode of interaction through the PTP interface, sending a node release message to the UPF entity through the PTP interface so as to release the node association relation between the UPF entity and the node release message.
37. The SMF entity of claim 34, wherein the execution unit is further to:
when the message filtering descriptor of the UPF entity needs to be configured, acquiring the interaction mode with the UPF entity recorded in the node association context;
if the acquired interaction mode is a mode of carrying out interaction by calling service through the SBI, calling a message filtering descriptor provided by the UPF entity through the SBI to provide service so as to configure the message filtering descriptor of the UPF entity; or,
and if the acquired interaction mode is the interaction mode through the PTP interface, sending a message filtering descriptor providing message to the UPF entity through the PTP interface so as to configure the message filtering descriptor of the UPF entity.
38. The SMF entity of claim 34, wherein the execution unit is further to:
when the message filtering descriptor of the UPF entity needs to be removed, acquiring the interaction mode with the UPF entity recorded in the node association context;
if the acquired interaction mode is a mode of carrying out interaction by calling service through the SBI, calling a message filtering descriptor removal service provided by the UPF entity through the SBI so as to remove the message filtering descriptor of the UPF entity; or,
and if the acquired 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 so as to remove the message filtering descriptor of the UPF entity.
39. An NRF entity, comprising:
a transceiver unit, configured to receive a first request message sent by an SMF entity, where the first request message is used to request to acquire configuration information of a UPF entity that meets a condition, where the condition includes that a specified UPF service can be provided and/or a specified interaction mode can be supported, and the interaction mode includes a mode of performing interaction through a point-to-point PTP interface and a mode of performing interaction by invoking a service through a serving SBI interface;
a searching unit, configured to search at least one UPF entity that meets the condition in the 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 the configuration information of the at least one UPF entity.
40. The NRF entity of claim 39, wherein the first request message is an NF discovery request message and the first response message is an NF discovery response message.
41. The NRF entity of claim 39, wherein the first request message is a NF status subscription message, the NF status subscription message is for subscribing to a UPF entity that satisfies a condition, and the first response message is a NF status notification message.
42. The NRF entity of claim 39, wherein said transceiving unit is further to:
receiving a NF registration request message sent by a second UPF entity, wherein the NF registration request message carries configuration information of the second UPF entity, and the configuration information comprises services which can be provided by the second UPF entity and/or interaction modes which can be supported by the second UPF entity;
storing configuration information of the second UPF entity;
sending a NF registration response message to the second UPF entity to inform the second UPF entity that registration is accepted.
43. The NRF entity of claim 42, wherein said NRF entity further comprises a determining unit;
the determining unit is configured to determine whether the second UPF entity satisfies the condition;
the transceiver unit is further configured to send an NF status notification message to the SMF entity if the determination result is yes, where the NF status notification message carries the configuration information of the second UPF entity.
44. The NRF entity of any of claims 39-43, wherein the configuration information of the UPF entity comprises at least one of the following information:
a fully qualified domain name FQDN of the UPF entity;
the network protocol IP address of the UPF entity;
services that the UPF entity is capable of providing;
the interaction mode supported by the UPF entity;
the area identification of the SMF entity that the UPF entity can serve.
45. A communication device, comprising:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein,
the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of any one of claims 1 to 9; or to enable the at least one processor to perform the method of any of claims 10 to 16; or to enable the at least one processor to perform the method of any of claims 17-22.
46. A computer storage medium, characterized in that:
the computer storage medium stores computer instructions that, when executed on a computer, cause the computer to perform the method of any one of claims 1-9, or cause the computer to perform the method of any one of claims 10-16, or cause the computer to perform the method of any one of claims 17-22.
CN201810918468.7A 2018-08-13 2018-08-13 Method and equipment for PDU session management, node association and UPF discovery Active CN110831092B (en)

Priority Applications (3)

Application Number Priority Date Filing Date Title
CN201810918468.7A CN110831092B (en) 2018-08-13 2018-08-13 Method and equipment for PDU session management, node association and UPF discovery
CN202110610366.0A CN113347673B (en) 2018-08-13 2018-08-13 PDU session management, node association and UPF discovery method and device
PCT/CN2019/100306 WO2020034930A1 (en) 2018-08-13 2019-08-13 Pdu session management, node association and upf discovery methods and entities

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201810918468.7A CN110831092B (en) 2018-08-13 2018-08-13 Method and equipment for PDU session management, node association and UPF discovery

Related Child Applications (1)

Application Number Title Priority Date Filing Date
CN202110610366.0A Division CN113347673B (en) 2018-08-13 2018-08-13 PDU session management, node association and UPF discovery method and device

Publications (2)

Publication Number Publication Date
CN110831092A true CN110831092A (en) 2020-02-21
CN110831092B CN110831092B (en) 2021-08-06

Family

ID=69525223

Family Applications (2)

Application Number Title Priority Date Filing Date
CN202110610366.0A Active CN113347673B (en) 2018-08-13 2018-08-13 PDU session management, node association and UPF discovery method and device
CN201810918468.7A Active CN110831092B (en) 2018-08-13 2018-08-13 Method and equipment for PDU session management, node association and UPF discovery

Family Applications Before (1)

Application Number Title Priority Date Filing Date
CN202110610366.0A Active CN113347673B (en) 2018-08-13 2018-08-13 PDU session management, node association and UPF discovery method and device

Country Status (2)

Country Link
CN (2) CN113347673B (en)
WO (1) WO2020034930A1 (en)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113973076A (en) * 2020-07-24 2022-01-25 华为技术有限公司 Multicast switching method and device
CN114125921A (en) * 2021-11-11 2022-03-01 中国电信股份有限公司 Time delay measuring method and system and anchor point UPF entity
US20220132602A1 (en) * 2019-01-15 2022-04-28 Datang Mobile Communications Equipment Co.,Ltd. Pdu session activation method and apparatus, and paging method and apparatus
CN114980064A (en) * 2022-05-16 2022-08-30 中国电信股份有限公司 Information association method and device, electronic equipment and storage medium

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR102346648B1 (en) * 2019-08-26 2022-01-03 삼성전자 주식회사 Apparatus and method for processing traffic of service in wireless communication system
KR20210031297A (en) * 2019-09-11 2021-03-19 삼성전자주식회사 Apparatus and method for processing traffic in wireless communication system

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017177364A1 (en) * 2016-04-11 2017-10-19 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for communication over network slices in wireless communication systems
CN108370600A (en) * 2017-05-09 2018-08-03 华为技术有限公司 A kind of conversation managing method, terminal and system

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106982473B (en) * 2016-01-19 2021-09-07 中兴通讯股份有限公司 Method for establishing transmission channel and wireless communication device
US10531420B2 (en) * 2017-01-05 2020-01-07 Huawei Technologies Co., Ltd. Systems and methods for application-friendly protocol data unit (PDU) session management
US11228949B2 (en) * 2017-01-06 2022-01-18 Samsung Electronics Co., Ltd. Intra-RAT handover for next generation system
CN108323245B (en) * 2017-06-19 2021-02-12 华为技术有限公司 Registration and session establishment method, terminal and AMF entity

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017177364A1 (en) * 2016-04-11 2017-10-19 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for communication over network slices in wireless communication systems
CN108370600A (en) * 2017-05-09 2018-08-03 华为技术有限公司 A kind of conversation managing method, terminal and system

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
CHINA MOBILE: ""S2-186500-UPF service introduced in SBA"", 《SA WG2 MEETING #128》 *
TECHNICAL SPECIFICATION GROUP SERVICES AND SYSTEM ASPECTS: ""TR 23.742-Study on Enhancements to the Service-Based Architecture"", 《3RD GENERATION PARTNERSHIP PROJECT》 *

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220132602A1 (en) * 2019-01-15 2022-04-28 Datang Mobile Communications Equipment Co.,Ltd. Pdu session activation method and apparatus, and paging method and apparatus
US11997729B2 (en) * 2019-01-15 2024-05-28 Datang Mobile Communications Equipment Co., Ltd. PDU session activation method and apparatus, and paging method and apparatus
CN113973076A (en) * 2020-07-24 2022-01-25 华为技术有限公司 Multicast switching method and device
CN114125921A (en) * 2021-11-11 2022-03-01 中国电信股份有限公司 Time delay measuring method and system and anchor point UPF entity
CN114125921B (en) * 2021-11-11 2024-03-05 中国电信股份有限公司 Time delay measurement method and system, anchor point UPF entity
CN114980064A (en) * 2022-05-16 2022-08-30 中国电信股份有限公司 Information association method and device, electronic equipment and storage medium
CN114980064B (en) * 2022-05-16 2023-10-03 中国电信股份有限公司 Information association method, device, electronic equipment and storage medium

Also Published As

Publication number Publication date
CN110831092B (en) 2021-08-06
CN113347673B (en) 2022-06-24
WO2020034930A1 (en) 2020-02-20
CN113347673A (en) 2021-09-03

Similar Documents

Publication Publication Date Title
CN110831092B (en) Method and equipment for PDU session management, node association and UPF discovery
CN110291837B (en) Network registration and network slice selection system and method
CN109429295B (en) Method for selecting AMF, system and storage medium
CN113115480A (en) Address information sending method, address information obtaining method, address information sending device, address information obtaining device, address information equipment and address information medium
EP3836515A1 (en) Communication method and communication device
US10764742B1 (en) Subscriber management with a stateless network architecture in a fifth generation (5G) network
KR20190118072A (en) Method and apparatus using network slicing
JP6314221B2 (en) Method and apparatus for realizing terminal WIFI talkback
WO2018024121A1 (en) Network function (nf) management method and nf management device
WO2021031592A1 (en) Method and device for reporting user plane functional entity information, storage medium and electronic device
EP4346286A1 (en) Session management function entity discovery method, network function node, access and mobility management function entity, electronic device, and computer-readable storage medium
JP2023520378A (en) Method and apparatus for PDU session establishment
JP2024081633A (en) Processing of service request
JP7086853B2 (en) Network access methods, related equipment and systems
JP2023518344A (en) Exposure and Discovery of Distributed Network Functions Serving User Equipment or PPDU Sessions
CN110913437B (en) Communication method and network element
WO2022022907A1 (en) Network functionality (nf) aware service provision based on service communication proxy (scp)
CN111935651B (en) Cluster service implementation method, device, medium, base station and system
EP4189944B1 (en) Bound service request handling
CN114258088B (en) Method, device and system for discovering intermediate session management function device, and storage medium
CN113873493A (en) Method and system for session binding
EP4075762A1 (en) Edge computing
RU2783809C2 (en) Communication method and communication device
US20230396983A1 (en) Facilitating services for devices in private mobile networks based on device authentications in an operator network
CN115515218B (en) Session management method, system and storage medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
TA01 Transfer of patent application right
TA01 Transfer of patent application right

Effective date of registration: 20210531

Address after: 100085 1st floor, building 1, yard 5, Shangdi East Road, Haidian District, Beijing

Applicant after: DATANG MOBILE COMMUNICATIONS EQUIPMENT Co.,Ltd.

Address before: 100191 No. 40, Haidian District, Beijing, Xueyuan Road

Applicant before: Telecommunications Science and Technology Research Institute Co.,Ltd.

GR01 Patent grant
GR01 Patent grant