WO2020052463A1

WO2020052463A1 - Communication method and network element

Info

Publication number: WO2020052463A1
Application number: PCT/CN2019/104086
Authority: WO
Inventors: 宗在峰; 朱奋勤; 杨文进; 张继东
Original assignee: 华为技术有限公司
Priority date: 2018-09-14
Filing date: 2019-09-03
Publication date: 2020-03-19
Also published as: CN110913437A; CN110913437B

Abstract

The present application provides a communication method and a network element. The communication method comprises: a first network element determining the identifier of a first session, the first session being a session served by a source second network element among at least two second network elements, the identifier of the first session being used to uniquely indicate the first session among a plurality of sessions served by the at least two second network elements; the plurality of sessions served by the at least two second network elements being divided into a plurality of session groups, the identifier of the first session including a first identifier and a second identifier, the first identifier being used to uniquely indicate a first session group to which the first session belongs among the plurality of session groups, the second identifier being used to uniquely indicate the first session among the sessions included in the first session group; when the first session is migrated from the source second network element to a target second network element of the at least two second network elements, the first network element sending the identifier of the first session to the target second network element. The present application provides a communication method and a network element, facilitating a target network element providing a service for a terminal device.

Description

Communication method and network element

This application claims the priority of a Chinese patent application filed with the State Intellectual Property Office of China on September 14, 2018, with application number 201811075872.9, and the invention name is "communication method and network element", the entire contents of which are incorporated herein by reference. .

Technical field

Embodiments of the present application relate to the field of communications, and more specifically, to a communication method and a network element.

Background technique

In a communication network, when a control plane network element, such as a session management function (SMF) network element, provides services to a terminal equipment (UE), the terminal equipment allocates related resources. The control plane network element can send the identifiers of these resources to other network elements, so that other network elements can communicate with the control plane network element according to the identifier, thereby achieving the purpose of the control plane network element and the other network elements serving the terminal device.

For example, when creating a protocol data unit (PDU) session, the SMF network element assigns a context reference identifier (SmContextRef) to each PDU session, and sends the context reference identifier to the access and mobility management function (access and mobility management (AMF) network elements. The AMF network element needs to initiate a related operation of a PDU session to the SMF. For example, when modifying a PDU session, the AMF network element sends the context reference identifier to the SMF network element as part of a uniform resource identifier (URI). . After receiving the URI, the SMF network element finds the corresponding PDU session according to the context reference identifier therein, and modifies the PDU session.

In communication networks, control plane network elements usually perform load balancing, that is, the terminal equipment served by a control plane network element (which can be referred to as a source control plane network element) is migrated to other control plane network elements (which can be referred to as a target control plane network). The target network element is controlled by the target to serve these terminal devices.

Therefore, how to communicate with the target control plane network element and the other network elements that communicate with the source control plane network element to provide services for the migrated terminal device during load balancing is an urgent technical problem to be solved.

Summary of the Invention

The communication method and network element provided in this application are convenient for a target network element to provide services for the terminal device.

In a first aspect, the present application provides a communication method. The communication method includes: a first network element determining an identifier of a first session, the first session being a session served by a source second network element among at least two second network elements, the first session identifier being used for Uniquely indicating the first session among a plurality of sessions served by the at least two second network elements, wherein the plurality of sessions served by the at least two second network elements are divided into a plurality of session groups, The identifier of the first session includes a first identifier and a second identifier, where the first identifier is used to uniquely indicate, among the multiple conversation groups, a first conversation group to which the first session belongs, and the second The identifier is used to uniquely indicate the first session among the sessions included in the first session group; when the first session is migrated from the source second network element to the at least two second network elements When the second network element is targeted, the first network element sends the identifier of the first session to the target second network element.

According to the communication method provided in the embodiment of the present application, the first network element sends an identifier of the first session to the target second network element, and the identifier of the first session includes an identifier of a first session group to which the first session belongs and The identity of the first session in the first conversation group, so when the first session is migrated from the source second network element to the target second network element in the at least two second network elements, the target The second network element can obtain the context of the first session according to the identifier of the first session, so that the target second network element can provide services for the first session.

Optionally, the at least two second network elements belong to a second network element set. For example, the second network element set may include at least a source second network element and a target second network element. The identifier of the first session is used to uniquely indicate the first session among a plurality of sessions served by the second network element set.

Optionally, the capabilities of multiple second network elements in the at least two second network elements may be the same. A plurality of second network elements of the at least two second network elements may manage the same user plane function (UPF) network element, have the same network slicing capability, and support the same deep neural network (deep neural network). networks, DNN), etc. It should be understood that the capacities of multiple second network elements in the at least two second network elements may be the same or different, which is not limited in this embodiment.

In some possible implementation manners, the sending, by the first network element, the identifier of the first session to the target second network element includes: the first network element sending the first network element to the target second network element Information, the first information includes identification information of the target second network element and identification of the first session.

In some possible implementations, the first information is a fully qualified session identifier (F-SEID), a uniform resource descriptor URI, a callback uniform resource descriptor (callback uniform URI), or Notify any of the associated identifiers.

In some possible implementation manners, before the first network element sends the first information to the target second network element, the communication method further includes that the first network element receives the second network element from the source second network element. Receive second information, the second information includes identification information of the source second network element and the identification of the first session; the first network element includes the second information of the source second network element The identification information is replaced with the identification information of the target second network element to obtain the first information.

In some possible implementation manners, the communication method further includes: the first network element receives third information from the target second network element, and the third information includes identification information of the target second network element And a conversation group identifier of a conversation group served by the target second network element.

Optionally, if the first network element receives a notification message that the source second network element no longer serves the session group to which the first session belongs, and the notification message specifies the target second network element corresponding to the session group, the first The network element may determine the target second network element corresponding to the session according to the session group corresponding to the first session and the notification message.

Optionally, the first network element may determine the identification information of the target second network element and the session group identifier of the session group served by the target second network element according to the session group corresponding to the first session and the notification message.

Optionally, the first network element may query a network element storage function (NRF) network element for the target second network element. For example, the first network element may provide the NRF network element with a session group identifier corresponding to the first session. The NRF network element determines the target second network element according to the session group identifier, and notifies the first network element.

Optionally, the NRF network element may determine the identification information of the target second network element and the session group ID of the session group served by the target second network element according to the session group identifier corresponding to the first session, and notify the first network yuan.

Optionally, the first network element may query the NRF network element for the target second network element. For example, the first network element may provide the NRF network element with the identifiers of the at least two second network elements, and the NRF network element receives One of the at least two second network elements is selected as the target SMF network element.

Optionally, the NRF network element may select one second network element from the at least two second network elements as the target SMF network element, and determine the identification information of the target second network element and the session group service of the target second network element. The session group is identified and notified to the first network element.

Optionally, the first network element may receive a redirection response from the source second network element, and carry the identification information of the target second network element in the response message, and the first network element may The identification information determines the target second network element.

Optionally, the first network element may determine the target second network element and the session group identifier of the session group served by the target second network element according to the identification information of the target second network element in the response message.

In some possible implementation manners, the second information is a fully qualified session identifier (F-SEID), a uniform resource descriptor URI, a callback uniform resource descriptor (callback uniform URI), or Notify any of the associated identifiers.

In some possible implementation manners, the replacing, by the first network element, the identification information of the source second network element in the second information with the identification information of the target second network element includes: when the first network element When the second information is F-SEID, replace the IP address carried in the Internet Protocol (IP) address field in the F-SEID from the IP address of the source second network element to the target second network. Element's IP address; or when the second information is a URI, the fully qualified domain name (FQDN) carried by the host name authorized domain field in the URI is taken from the FQDN of the source second network element The FQDN of the target second network element, or the IP address carried in the authorized domain host name field in the URI from the IP address of the source second network element to the IP of the target second network element Address; or when the second information is a callback URI, replace the FQDN carried by the host name authorization domain field in the callback URI from the FQDN of the source second network element to the FQDN of the target second network element Or the IP address carried in the hostname authorization field in the callback URI Replacing the IP address of the source second network element with the IP address of the target second network element; or when the second information is a notification association identifier, the FQDN carried in the host name authorization domain field in the callback URI Replace the FQDN of the source second network element with the FQDN of the target second network element, or replace the IP address carried in the host name authorization domain field in the callback URI from the IP address of the source second network element It is replaced with the IP address of the target second network element, wherein the callback URI and the notification association identifier are sent in the same message.

In some possible implementation manners, the first network element is any one of the following: a user plane function (UPF) network element, an access and mobility management function, an AMF network element, and a session management function, an SMF network element , Policy management function (PCF) network element, authentication server function (AUSF) network element, unified data management (UDM) network element, network element storage function (NRF) ) Network element or unstructured data storage function (UDSF) network element.

In some possible implementation manners, the second network element is any one of the following: an access and mobility management function network element, a session management function network element, a policy management function network element, an authentication server function network element, and unified data Management network element, network element storage function network element or unstructured data storage function network element.

In a second aspect, the present application provides a communication method. The communication method includes: a first network element determines an identifier of a first session, the first session is a session served by at least two second network elements, and the identifier of the first session is used in the at least two first network elements; The plurality of sessions served by two network elements uniquely indicate the first session, wherein the plurality of sessions served by the at least two second network elements are divided into a plurality of session groups, and The identifier includes a first identifier and a second identifier, where the first identifier is used to uniquely indicate, among the multiple conversation groups, a first conversation group to which the first session belongs, and the second identifier is used to The session included in the first session group uniquely indicates the first session; the first network element sends an identifier of the first session to a target second network element among the at least two second network elements.

According to the communication method provided in the embodiment of the present application, the first network element sends an identifier of the first session to the target second network element, and the identifier of the first session includes an identifier of a first session group to which the first session belongs and The identification of the first session in the first session group, so that the target second network element can obtain the context of the first session according to the identification of the first session, so that the target second network element can provide services for the first session .

Optionally, the capabilities of multiple second network elements in the at least two second network elements may be the same. A plurality of second network elements of the at least two second network elements may manage the same UPF network element, have the same network slicing capability, support the same DNN, and the like. It should be understood that the capacities of multiple second network elements in the at least two second network elements may be the same or different, which is not limited in this embodiment.

In some possible implementation manners, the sending, by the first network element, the identifier of the first session to the target second network element includes: the first network element sending the first network element to the target second network element Information, the first information includes an identifier of the first session.

In some possible implementation manners, the first information is a fully-qualified session identifier (F-SEID).

In some possible implementation manners, before the first network element sends the first information to the target second network element, the communication method further includes: changing an Internet protocol (internet protocol) in the F-SEID, IP) The IP address carried in the address field is replaced from the IP address of the source second network element by the IP address of the target second network element; or the IP address carried in the Internet Protocol address field in the F-SEID is set Is the IP address of the service framework.

In some possible implementation manners, before the first network element determines the identity of the first session, the communication method further includes: the first network element receives the second information from the source second network element, so that The second information includes an identifier of the first session.

In some possible implementation manners, the second information is a full session identifier F-SEID.

In some possible implementation manners, the second message further includes an IP address of a service frame network element corresponding to the second network element.

In some possible implementation manners, the first network element is a user plane function UPF network element.

In some possible implementation manners, the source second network element is a session management function SMF network element.

According to a third aspect, the present application provides a communication method including: a source second network element generating an identifier of a first session, the first session being the source second network of at least two second network elements A session served by an element, and the identifier of the first session is used to uniquely indicate the first session among multiple sessions served by the at least two second network elements, wherein the at least two second networks The multiple sessions served by the meta are divided into multiple session groups, and the identifier of the first session includes a first identifier and a second identifier, and the first identifier is used to uniquely indicate the multiple session groups. The first session group to which the first session belongs, and the second identifier is used to uniquely indicate the first session among the sessions included in the first session group; the source second network element reports to the first network The meta sends the identity of the first session.

According to the communication method provided in the embodiment of the present application, the identifier of the first session generated by the source second network element includes an identifier of a first session group to which the first session belongs and a first session in the first session group. The identifier, and sends the identifier of the first session to the first network element. Therefore, after the first session is migrated from the source second network element to the target second network element among the at least two second network elements, the target second network element may obtain the first session according to the identifier of the first session. The context of a session is convenient for the target second network element to provide services for the first session.

Optionally, the capabilities of multiple second network elements in the at least two second network elements may be the same. A plurality of second network elements in the at least two second network elements may manage the same UPF network element, have the same network slicing capability, support the same DNN, and the like. It should be understood that the capacities of multiple second network elements in the at least two second network elements may be the same or different, which is not limited in this embodiment.

In some possible implementation manners, the sending, by the source second network element, the identifier of the first session to the first network element includes: sending, by the source second network element, the second network element to the first network element Information, the second information includes identification information of a target second network element among the at least two second network elements and an identification of the first session.

In some possible implementation manners, the second information is any one of a full session identifier F-SEID, a uniform resource descriptor URI, a callback uniform resource descriptor callback URI, or a notification association identifier.

In some possible implementation manners, the first network element is any one of the following: a UPF network element, an AMF network element, an SMF network element, a PCF network element, an AUSF network element, a UDM network element, an NRF network element, or a UDSF network yuan.

In some possible implementation manners, the second network element is any one of the following: an access and mobility management function AMF network element, a session management function SMF network element, a policy management function PCF network element, and an authentication server function AUSF network Element, unified data management UDM network element, network element storage function NRF network element or unstructured data storage function UDSF network element.

In a fourth aspect, the present application provides a communication method. The communication method includes: a target second network element receives an identifier of a first session from a first network element, and the first session is in at least two second network elements. A session served by a source second network element, and the identifier of the first session is used to uniquely indicate the first session among multiple sessions served by the at least two second network elements, wherein the at least two Multiple sessions served by two second network elements are divided into multiple session groups, and the identifier of the first session includes a first identifier and a second identifier, and the first identifier is used in the multiple conversation groups Uniquely indicating a first session group to which the first session belongs, and the second identifier is used to uniquely indicate the first session among sessions included in the first session group; the target second network element The identification of the first session determines the first session.

According to the communication method provided in the embodiment of the present application, the identifier of the first session received by the target second network element from the first network element includes the identifier of the first session group to which the first session belongs and the first session in the first session. An identifier in a session group. Therefore, when a first session is migrated from the source second network element to a target second network element in the at least two second network elements, the target second network element may The identity of a session obtains the context of the first session, which is convenient for the target second network element to provide services for the first session.

In some possible implementation manners, the receiving, by the target second network element, the identifier of the first session from the first network element includes: receiving, by the target second network element, the first information from the first network element, the The first information includes identification information of the target second network element and identification of the first session.

In some possible implementation manners, the first information is any one of a full session identifier F-SEID, a uniform resource descriptor URI, a callback uniform resource descriptor callback URI, or a notification association identifier.

According to a fifth aspect, a network element is provided. The network element includes a processing module configured to determine an identifier of a first session, where the first session is served by a source second network element among at least two second network elements. , The identifier of the first session is used to uniquely indicate the first session among multiple sessions served by the at least two second network elements, wherein the at least two second network elements serve Multiple sessions are divided into multiple session groups, and the identifier of the first session includes a first identifier and a second identifier, and the first identifier is used to uniquely indicate the first session among the multiple conversation groups A first conversation group that belongs to, the second identifier is used to uniquely indicate the first conversation among the conversations included in the first conversation group; a sending module is configured to: when the first conversation is from the source When the second network element is migrated to a target second network element among the at least two second network elements, the first network element sends the identifier of the first session to the target second network element.

According to the network element provided in the embodiment of the present application, the network element sends an identifier of the first session to the target second network element, and the identifier of the first session includes an identifier of a first session group to which the first session belongs and The identity of the first session in the first conversation group, so when the first session is migrated from the source second network element to the target second network element in the at least two second network elements, the target The second network element can obtain the context of the first session according to the identifier of the first session, so that the target second network element can provide services for the first session.

In some possible implementation manners, the sending module is specifically configured to send first information to the target second network element, where the first information includes identification information of the target second network element and the first session Logo.

In some possible implementation manners, the network element further includes a receiving module, configured to receive the second information from the source second network element before the network element sends the first information to the target second network element. The second information includes identification information of the source second network element and the identification of the first session; wherein the processing module is further configured to identify the source second network element in the second information The information is replaced with identification information of the target second network element to obtain the first information.

In some possible implementation manners, the receiving module is further configured to receive third information from the target second network element, where the third information includes identification information of the target second network element and the target first network element. The conversation group identifier of the conversation group served by the second network element.

Optionally, if the network element receives a notification message that the source second network element no longer serves the session group to which the first session belongs, and the notification message specifies the target second network element corresponding to the session group, the The network element may determine the target second network element corresponding to the session according to the session group corresponding to the first session and the notification message.

Optionally, the network element may determine the identification information of the target second network element and the session group identifier of the session group served by the target second network element according to the session group corresponding to the first session and the notification message.

Optionally, the network element may query the NRF network element for the target second network element. For example, the network element may provide the NRF network element with a session group identifier corresponding to the first session, and the NRF network element determines the target according to the session group identifier. The second network element and notifies the network element.

Optionally, the NRF network element may determine the identification information of the target second network element and the session group ID of the session group served by the target second network element according to the session group ID corresponding to the first session, and notify the network of the yuan.

Optionally, the network element may query the NRF network element for the target second network element. For example, the network element may provide the NRF network element with the identifiers of the at least two second network elements, and the NRF network element receives One of the at least two second network elements is selected as the target SMF network element.

Optionally, the NRF network element may select one second network element from the at least two second network elements as the target SMF network element, and determine the identification information of the target second network element and the session group service of the target second network element. The session group is identified and notified to the network element.

Optionally, the network element may receive a redirection response from the source second network element, and carry the identification information of the target second network element in the response message, and the network element is configured according to the target second network element in the response message. The identification information determines the target second network element.

Optionally, the network element may determine the target second network element and the session group identifier of the session group served by the target second network element according to the identification information of the target second network element in the response message.

In some possible implementation manners, the second information is any one of a full session identifier F-SEID, a uniform resource descriptor URI, a callback uniform resource descriptor callback URI, or a notification association identifier, and the first information includes all Said the identification of the first session.

In some possible implementation manners, the processing module is further configured to: when the second information is an F-SEID, remove an IP address carried by an Internet Protocol IP address field in the F-SEID from the source address. Replace the IP address of the second network element with the IP address of the target second network element; or when the second information is a URI, replace the fully qualified domain name FQDN carried in the authorized domain field in the URI from the source Replace the FQDN of the second network element with the FQDN of the target second network element, or replace the IP address carried in the authorized domain field in the URI from the IP address of the source second network element with the target second network The IP address of the element; or when the second information is a callback URI, replace the FQDN carried in the authorized domain field in the callback URI from the FQDN of the source second network element to the target second network element FQDN, or replace the IP address carried in the authorization field in the callback URI from the IP address of the source second network element with the IP address of the target second network element; or when the second information is a notification association When identifying, the FQDN carried in the authorization domain field in the callback URI is removed from the source second network. The FQDN of the element is replaced with the FQDN of the target second network element, or the IP address carried in the authorized domain field in the callback URI is replaced from the IP address of the source second network element with the target second network element , The callback URI and the notification association identifier are sent in the same message.

In some possible implementation manners, the network element is any of the following: a user plane function UPF network element, an access and mobility management function AMF network element, a session management function SMF network element, a policy management function PCF network element, Authentication server functions AUSF network elements, unified data management UDM network elements, network element storage functions NRF network elements or unstructured data storage functions UDSF network elements.

In a sixth aspect, the present application provides a network element. The network element includes: a processing module, configured to determine an identifier of a first session, where the first session is a session served by at least two second network elements, and the identifier of the first session is used in the at least two The plurality of sessions served by the second network element uniquely indicate the first session, wherein the plurality of sessions served by the at least two second network elements are divided into a plurality of session groups, and the first session The identifier includes a first identifier and a second identifier, where the first identifier is used to uniquely indicate, among the multiple conversation groups, a first conversation group to which the first session belongs, and the second identifier is used to The session included in the first session group uniquely indicates the first session; and a sending module is configured to send an identifier of the first session to a target second network element among the at least two second network elements.

According to the network element provided in the embodiment of the present application, the network element sends an identifier of the first session to the target second network element, and the identifier of the first session includes an identifier of a first session group to which the first session belongs and The identification of the first session in the first session group, so that the target second network element can obtain the context of the first session according to the identification of the first session, and it is convenient for the target second network element to provide services for the first session .

In some possible implementation manners, the sending module is specifically configured to send first information to the target second network element, where the first information includes an identifier of the first session.

In some possible implementation manners, the processing module is further configured to: replace an IP address carried in an Internet Protocol (IP) address field in the F-SEID with an IP address of the source second network element Is the IP address of the target second network element; or the IP address carried in the Internet Protocol address field in the F-SEID is set to the IP address of the service frame.

In some possible implementation manners, the network element further includes a receiving module, configured to receive second information from the source second network element, where the second information includes an identifier of the first session.

In some possible implementation manners, the network element is a user plane function UPF network element.

According to a seventh aspect, a network element is provided. The network element includes a processing module configured to generate an identifier of a first session, where the first session is the source second network element of at least two second network elements. A serviced session, the identifier of the first session is used to uniquely indicate the first session among a plurality of sessions served by the at least two second network elements, wherein the at least two second network elements The plurality of sessions served are divided into a plurality of session groups, and the identifier of the first session includes a first identifier and a second identifier, and the first identifier is used to uniquely indicate the first identifier among the multiple conversation groups. A first conversation group to which a session belongs, the second identifier is used to uniquely indicate the first conversation among the sessions included in the first conversation group; and a sending module is configured to send all the information to the first network element Said the identification of the first session.

According to the network element provided in the embodiment of the present application, the identifier of the first session generated by the network element includes an identifier of a first session group to which the first session belongs and an identifier of the first session in the first session group. And sending the identifier of the first session to the first network element. Therefore, after the first session is migrated from the network element to the target second network element in the at least two second network elements, the target second network element may obtain the first session according to the identifier of the first session. Context to facilitate the target second network element to provide services for the first session.

Optionally, the at least two second network elements belong to a second network element set. For example, the second network element set may include at least the network element and the target second network element. The identifier of the first session is used to uniquely indicate the first session among a plurality of sessions served by the second network element set.

In some possible implementation manners, the sending module is specifically configured to send second information to the first network element, where the second information includes a target second network element among the at least two second network elements And identification information of the first session.

In some possible implementation manners, the network element is any one of the following: an access and mobility management function AMF network element, a session management function SMF network element, a policy management function PCF network element, an authentication server function AUSF network element, Unified data management UDM network element, network element storage function NRF network element or unstructured data storage function UDSF network element.

According to an eighth aspect, a network element is provided. The network element includes a receiving module configured to receive an identifier of a first session from a first network element, where the first session is a source node in at least two second network elements. A session served by two network elements, and the identifier of the first session is used to uniquely indicate the first session among multiple sessions served by the at least two second network elements, wherein the at least two first The multiple sessions served by the two network elements are divided into multiple session groups. The identifier of the first session includes a first identifier and a second identifier. The first identifier is used to uniquely indicate among the multiple conversation groups. A first session group to which the first session belongs, and the second identifier is used to uniquely indicate the first session among sessions included in the first session group; a processing module is configured to The identification of the first session.

According to the network element provided in the embodiment of the present application, the identifier of the first session received by the network element from the first network element includes the identifier of the first session group to which the first session belongs and the first session is in the first The identifier in the session group. Therefore, after a first session is migrated from the source second network element to the network element in the at least two second network elements, the network element may The identifier acquires the context of the first session, which facilitates the network element to provide services for the first session.

Optionally, the at least two second network elements belong to a second network element set. For example, the second network element set may include at least the source second network element and the network element. The identifier of the first session is used to uniquely indicate the first session among a plurality of sessions served by the second network element set.

In some possible implementation manners, the receiving module is specifically configured to receive first information from the first network element, where the first information includes identification information of the network element and identification of the first session.

In a ninth aspect, a network element is provided. The network element includes a processor and a transmitter. The processor is configured to execute a program. When the processor executes the program, the processor and the transmitter implement the first aspect or any one of the first aspect. Communication method in one possible implementation.

Optionally, the network element may further include a memory. The memory is used to store programs executed by the processor.

Optionally, the network element may further include a receiver. The receiver is used to receive information from other equipment or devices.

According to a tenth aspect, a network element is provided. The communication device includes a processor and a transmitter. The processor is configured to execute a program. When the processor executes the program, the processor and the transmitter implement any one of the second aspect or the second aspect. Communication method in one possible implementation.

According to an eleventh aspect, a network element is provided. The network element includes a processor and a receiver. The processor is configured to execute a program. When the processor executes the program, the processor and the receiver implement the third aspect or any Communication method in one possible implementation.

Optionally, the communication device may further include a memory. The memory is used to store programs executed by the processor.

Optionally, the communication device may further include a transmitter. The sender is used to send information to other devices or devices.

According to a twelfth aspect, a network element is provided. The network element includes a processor and a receiver. The processor is configured to execute a program. When the processor executes the program, the processor and the receiver implement any of the fourth aspect or the fourth aspect. Communication method in one possible implementation.

According to a thirteenth aspect, a computer-readable storage medium is provided. The computer-readable storage medium stores program code for execution by a network element, where the program code includes the first aspect or any one of the first aspect. Instructions for implementing a communication method.

According to a fourteenth aspect, a computer-readable storage medium is provided. The computer-readable storage medium stores program code for execution by a network element, and the program code includes a second aspect or any one of the second aspect. Instructions for implementing a communication method.

According to a fifteenth aspect, a computer-readable storage medium is provided. The computer-readable storage medium stores program code for execution by a network element, where the program code includes the third aspect or any one of the third aspect. Instructions for implementing a communication method.

According to a sixteenth aspect, a computer-readable storage medium is provided. The computer-readable storage medium stores program code for execution by a network element, and the program code includes the fourth aspect or any one of the fourth aspect. Instructions for implementing a communication method.

According to a seventeenth aspect, a chip is provided. The chip includes a processor and a communication interface. The communication interface is used to travel with an external device. The processor is used to implement the first aspect or any possible implementation manner of the first aspect. Communication method in.

Optionally, the chip may further include a memory, and the memory stores instructions. The processor is configured to execute the instructions stored in the memory. When the instructions are executed, the processor is configured to implement the first aspect or any one of the first aspect. Communication methods in possible implementations.

According to an eighteenth aspect, a chip is provided. The chip includes a processor and a communication interface. The communication interface is used to travel with external devices. The processor is used to implement the second aspect or any possible implementation manner of the second aspect. Communication method in.

Optionally, the chip may further include a memory, and the memory stores instructions. The processor is configured to execute the instructions stored in the memory. When the instructions are executed, the processor is configured to implement the second aspect or any one of the second aspect. Communication methods in possible implementations.

In a nineteenth aspect, a chip is provided. The chip includes a processor and a communication interface. The communication interface is used to travel with external devices. The processor is used to implement the third aspect or any possible implementation manner of the third aspect. Communication method in.

Optionally, the chip may further include a memory, and the memory stores instructions. The processor is configured to execute the instructions stored in the memory. When the instructions are executed, the processor is configured to implement the third aspect or any one of the third aspect. Communication methods in possible implementations.

In a twentieth aspect, a chip is provided. The chip includes a processor and a communication interface. The communication interface is used to travel with external devices. The processor is used to implement the fourth aspect or any possible implementation manner of the fourth aspect. Communication method in.

Optionally, the chip may further include a memory, and the memory stores instructions. The processor is configured to execute the instructions stored in the memory. When the instructions are executed, the processor is configured to implement the fourth aspect or any one of the fourth aspect. Communication methods in possible implementations.

In a twenty-first aspect, a computer program product is provided, including instructions that, when run on a network element, cause the network element to perform communication in the first aspect or any possible implementation manner of the first aspect method.

In a twenty-second aspect, a computer program product is provided, including instructions that, when run on a network element, cause the network element to perform communication in the second aspect or any possible implementation manner of the second aspect method.

In a twenty-third aspect, a computer program product is provided, including instructions that, when run on a network element, cause the network element to perform communication in the third aspect or any possible implementation manner of the third aspect method.

According to a twenty-fourth aspect, a computer program product is provided, including instructions that, when running on a network element, cause the network element to perform communication in the fourth aspect or any possible implementation manner of the fourth aspect. method.

In a twenty-fifth aspect, an embodiment of the present application provides a communication system including the network element according to one or more of the fifth aspect to the eighth aspect.

In a possible design, the communication system further includes other devices that interact with any one of the network elements in one or more of the fifth aspect to the eighth aspect in the solution provided in the embodiments of the present application, For example, access network and / or DN network element.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic architecture diagram of a communication system to which a communication method according to an embodiment of the present application can be applied.

FIG. 2 is a schematic flowchart of a communication method according to an embodiment of the present application.

FIG. 3 is a schematic flowchart of a communication method according to another embodiment of the present application.

FIG. 4 is a schematic flowchart of a communication method according to another embodiment of the present application.

FIG. 5 is a schematic flowchart of a communication method according to another embodiment of the present application.

FIG. 6 is a schematic structural diagram of a network element according to an embodiment of the present application.

FIG. 7 is a schematic structural diagram of a network element according to another embodiment of the present application.

FIG. 8 is a schematic structural diagram of a network element according to another embodiment of the present application.

FIG. 9 is a schematic structural diagram of a network element according to another embodiment of the present application.

FIG. 10 is a schematic structural diagram of a network element according to another embodiment of the present application.

detailed description

The technical solutions in this application will be described below with reference to the drawings.

The technical solutions of the embodiments of the present application can be applied to various communication systems, for example: a global mobile communication (GSM) system, a code division multiple access (CDMA) system, and a broadband code division multiple access (wideband code division multiple access (WCDMA) system, general packet radio service (GPRS), long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE Time Division Duplex (TDD), Universal Mobile Telecommunications System (UMTS), Global Interoperability for Microwave Access (WiMAX) communication system, 5th generation in the future, 5G) system or new radio (NR).

The terminal device in the embodiments of the present application may refer to user equipment, access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or User device. Terminal equipment can also be cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), and wireless communications Functional handheld devices, computing devices, or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, terminal devices in the future 5G network, or public land mobile network (PLMN) in future evolution Terminal equipment and the like are not limited in this embodiment of the present application.

The network device in the embodiment of the present application may be a device for communicating with a terminal device, and the network device may be a Global System for Mobile Communication (GSM) system or a Code Division Multiple Access (CDMA) system. The base station (Base Transceiver Station (BTS)) can also be a base station (NodeB, NB) in a wideband code division multiple access (WCDMA) system, or an evolved base station (evolved) in an LTE system. (NodeB, eNB or eNodeB), can also be a wireless controller in a cloud radio access network (CRAN) scenario, or the network device can be a relay station, access point, in-vehicle device, wearable device, and future The network equipment in the 5G network or the network equipment in the future evolved PLMN network is not limited in the embodiments of the present application.

FIG. 1 is a network architecture applied to an embodiment of the present application. As shown in FIG. 1, each network element involved in the network architecture is described separately.

1. (radio access network (R) AN) network element: It is used to provide network access functions for authorized users in specific areas, and can use different quality transmission tunnels according to user levels and business needs . The (R) AN network element can manage wireless resources and provide access services for terminal equipment, thereby completing the transfer of control signals and user data between the terminal equipment and the core network. The (R) AN network element can also be understood as a traditional network Base station

2. User plane network element: used for packet routing and forwarding and quality of service (QoS) processing of user plane data.

In a 5G communication system, the user plane network element may be a user plane function (user plane function (UPF) network element). In the future communication system, the user plane network element may still be a UPF network element, or may have another name, which is not limited in this application.

3. Data network network element: A network for providing data transmission. In a 5G communication system, the data network network element may be a data network (DN) network element. In the future communication system, the data network network element may still be a DN network element, or may have another name, which is not limited in this application.

4. Access management network element: It is mainly used for mobility management and access management. It can be used to implement functions other than session management in mobility management entity (MME) functions, such as legal monitoring. And access authorization / authentication.

In a 5G communication system, the access management network element may be an access management function (access management function (AMF) network element). In the future communication system, the access management network element may still be an AMF network element, or may have another name, which is not limited in this application.

5. Session management network element: It is mainly used for session management, terminal equipment's Internet Protocol (IP) address allocation and management, selection of endpoints that can manage user plane functions, policy control and charging function interfaces, and downstream data Notice, etc.

In a 5G communication system, the session management network element may be a session management function (session management function (SMF) network element). In the future communication system, the session management network element may still be an SMF network element, or may have another name, which is not limited in this application.

6. Policy control network element: a unified policy framework for guiding network behavior, providing policy rule information for control plane function network elements (such as AMF, SMF network elements, etc.).

In a 5G communication system, the policy control network element may be a policy control function (policy control function (PCF) network element). In the future communication system, the policy control network element may still be a PCF network element, or may have another name, which is not limited in this application.

7. Authentication service network element: used to implement user authentication and authentication.

In a 5G communication system, the authentication service network element may be an authentication server function (authentication server function, AUSF) network element. In the future communication system, the authentication service network element may still be an AUSF network element, or may have another name, which is not limited in this application.

8. Unified data management network element: used to handle user identification, access authentication, registration, and mobility management.

In a 5G communication system, the unified data management network element may be a unified data management (UDM) network element. In the future communication system, the unified data management network element may still be a UDM network element, or may have another name, which is not limited in this application.

9. Terminal equipment: It can include various handheld devices with wireless communication functions, vehicle-mounted devices, wearable devices, computing devices or other processing devices connected to wireless modems, as well as various forms of terminals, mobile stations (mobile stations, MS ), Terminal (terminal), user equipment (UE), soft terminal, etc., such as water meters, electricity meters, sensors, etc.

It can be understood that the foregoing network element or function may be a network element in a hardware device, may also be a software function running on dedicated hardware, or a virtualization function instantiated on a platform (for example, a cloud platform).

It should be noted that, in the embodiments of the present application, a network element or function is used as an example for description. However, in a future network, the network element or function may be replaced by a service. For example, an AMF network element is replaced with an AMF. Communication services, AMF event notification services, etc., this application is also applicable to services. For example, when each network element or function in this application is replaced with a service, the method in this application is still applicable. Specifically, the first network element in this application may be not only the network element or function defined above, but also the first service. Similarly, the second network element in this application may also be the second service. This application does not limit this.

In this network architecture, N1 is the reference point between UE110 and AMF network element 150, and N2 is the reference point for (R) AN network element 120 and AMF network element 150, which is used for the non-access stratum, NAS) messages, etc .; N3 is the reference point between (R) AN network element 120 and UPF network element 130, used to transmit user plane data, etc .; N4 is the distance between SMF network element 160 and UPF network element 130. Reference point, used to transmit information such as tunnel identification information for N3 connections, data cache indication information, and downlink data notification messages; N6 interface is the reference point between UPF network element 130 and DN network element 140, and is used to transmit the user plane N11 is the reference point between AMF network element 150 and SMF network element 160; N8 and N10 are the reference points between AMF network element 150, SMF network element 160 and UDM network element 190, respectively, for obtaining users Contract data; N15 and N7 are reference points between AMF network element 150, SMF network element 160 and PCF network element 170, respectively, for obtaining policy data; N12 is a reference point between AMF network element 150 and AUSF network element 180 N13 is the reference point between UDM network element 190 and AUSF network element 180.

It should be understood that the foregoing network architecture applied to the embodiments of the present application is merely an exemplary network architecture for illustration, and the network architecture applicable to the embodiments of the present application is not limited to this. The network architecture is applicable to the embodiments of the present application.

In the above network architecture, network elements such as AMF network element 150, SMF network element 160, PCF network element 170, AUSF network element 180, and UDM network element 190 can be referred to as control plane network elements, and UPF network element 130 can be referred to as a user Network element. Optionally, the network architecture in the embodiment of the present application may further include network elements such as a network element storage function (NRF) network element or an unstructured data storage function (UDSF) network element, NRF Network elements and UDSF network elements can also be called control plane network elements.

In the embodiment of the present application, when the control plane network element provides services to the UE, the control plane network element may allocate relevant resources to the UE and send the resource identifier to other network elements. In this way, other network elements are in a subsequent communication process. You can find resources based on the ID.

In a possible implementation manner of the embodiment of the present application, the control plane network element may fail to continue to provide services. At this time, another control plane network element may be required to continue the service instead of the current control plane network element. For example, in the scenario where the control plane network element is load balanced, when the current control plane network element is shut down, fails, or is downsized, another control plane network element may be required to replace or partially replace the current control plane network element. Service.

It should be understood that in this application, resources corresponding to SMF network elements may be referred to as sessions, resources corresponding to PCF network elements may be referred to as policy sessions, and resources corresponding to other control plane network elements may also have other names, which are unified in the embodiments of this application. The resources corresponding to various network elements are called sessions.

To facilitate understanding, in the following description, the source control plane network element refers to the control plane network element that originally allocated resources and resource identifiers, and other network elements refer to the network elements that need to interact with the source control plane network element during the communication process. Control plane refers to the control plane network element that continues to provide services to the source control plane network element when it can no longer provide services for the resource. It should be understood that the other network elements here may be control plane network elements or user plane network elements.

Taking the source control plane network element as an SMF network element as an example, when creating a session, the source SMF network element assigns a context reference identifier (SmContextRef) to each session, and sends the context reference identifier to other network elements that interact with it. For example, other network elements may be AMF network elements. When a subsequent AMF network element operates the session, such as modifying or deleting a session, the AMF network element needs to send the context reference identifier to the source SMF network element, and the source SMF network element can find the session based on the context reference identifier. Modify or delete the conversation.

In a possible implementation manner of the embodiment of the present application, when the source SMF network element no longer provides service for the session, a target SMF network element needs to be determined. In the subsequent communication process, the target SMF network element replaces the source SMF. Network elements continue to provide services. However, at this time, the context reference identifier assigned to the session by the source SMF network element may have been assigned to other sessions in the target SMF network element. This may cause the target SMF network element to mistakenly upload the target SMF network element after receiving the request from the AMF network element. Another session with the same context reference identifier is regarded as the session, thereby causing the target SMF network element to operate the wrong session.

Therefore, this application proposes a communication method that can enable the target control plane network element to provide services for the session when the source control plane network element cannot continue to provide services for the session.

The following uses a control plane network element in the network architecture of FIG. 1 as an example to describe a communication method according to an embodiment of the present application. FIG. 2 shows an exemplary flowchart of a communication method according to an embodiment of the present application. The method includes the following steps.

S210. The source second network element generates an identifier of the first session.

Specifically, the first session may be one of a plurality of sessions served by the source second network element, where the plurality of sessions may be divided into a plurality of session groups, and an identifier of the first session may include a first identifier and A second identifier, the first identifier is an identifier of a first conversation group to which the first session belongs, and the second identifier is an identifier of the first session in the first conversation group.

In the embodiment of the present application, the second network element may be any control plane network element in the network architecture of FIG. 1. For example, the second network element may be an AMF network element, an SMF network element, a PCF network element, an AUSF network element, UDM network element, NRF network element or UDSF network element. The second network element here may include a source second network element and a target second network element, that is, the source second network element and the target second network element may be AMF network elements, SMF network elements, PCF network elements, and AUSF. Network element, UDM network element, NRF network element or UDSF network element.

Accordingly, in the embodiment of the present application, the first network element may be a network element connected to the second network element in the network architecture of FIG. 1.

For example, as shown in FIG. 1, the SMF network element is connected to the UPF network element, the AMF network element, the PCF network element, and the UDM network element, and the AMF network element is connected to the AUSF network element, the SMF network element, and the UDM network element. When the element is an SMF network element, the first network element may be a UPF network element, an AMF network element, a PCF network element, or a UDM network element; when the second network element is an AMF network element, the first network element may be an AUSF network element, SMF network element or UDM network element.

For ease of understanding, in the following description, the second network element is an SMF network element as an example for description. It should be understood that the second network element here is an SMF network element only as an example and not a limitation.

In the embodiment of the present application, multiple SMF network elements may form an SMF network element set. For example, the second network element set may be composed of an SMF1 network element, an SMF2 network element, and an SMF3 network element. Optionally, the capabilities of multiple second network elements in the second network element set may be the same.

The same capabilities of multiple second network elements can be understood as: the same UPF network element can be managed, the same network slice capability, and the same DNN can be supported. It should be understood that the capacities of multiple second network elements in the second network element set may be the same or different, which is not limited in this embodiment.

Multiple session group identifiers may be configured in multiple second network elements in the second network element set. For example, as shown in Table 1, the session group identifiers 000 and 001 are configured on the SMF1 network element, the session group identifiers 010 and 011 are configured on the SMF2 network element, and the session group identifiers 100 and 101 are configured on the SMF3.

Table 1 Correspondence between the second network element and the session group identifier 1

It should be understood that the second network element set may support multiple session groups, where one session group may correspond to a unique session group identifier in the set, and one session group may be served by a second network element.

When the second network element creates the first session, the first session group identifier in the session group identifier configured by the second network element is selected for the first session as the session group identifier of the first session, and one is allocated for the first session. The identity in the first conversation group. Then, the second network element may send the identity of the session to the first network element.

In some possible implementation manners, before the SMF1 network element is ready to shut down, the SMF1 network element may save all or part of the session context to the UDSF network element shared by the second network element set.

In other possible implementation manners, when a UDSF network element is not deployed in the second network element set, a target second network element corresponding to the session group may be configured for the second network element.

For example, during system initialization, a backup target second network element may be determined for multiple session groups served by the second network element set. For example, as shown in Table 2, the backup target second network element corresponding to the session group 000 served by the SMF1 network element may be an SMF2 network element, and the backup target second network element corresponding to the session group 001 served by the SMF1 network element may be SMF3 network element. At this time, SMF1 network element is the source second network element, and SMF2 network element and SMF3 network element are the target second network element.

Similarly, the backup target second network element can be determined for the session groups 010 and 011 served by the SMF2 network element, and the backup target second network element can be determined for the session groups 100 and 101 served by the SMF3 network element.

During system initialization, the correspondence between the session group identifier and the backup target second network element can be configured in other related network elements, for example, it can be configured in AMF network elements, NRF network elements, UPF network elements, etc., or between nodes. In the signaling, the second network element sends the foregoing pair relationship to other related network elements.

After the system is started, the second network element can synchronize the session context in the session group to the backup target second network element corresponding to the session group. The synchronization can be performed periodically or triggered by a change.

The change trigger can be understood as that when the session context in the session group changes, the second network element synchronizes the session context in the session group to the backup target second network element corresponding to the session group.

If the session context in the session group is not synchronized to the corresponding backup target second network element when the system is started, the second network element in the second network element set may be shut down or reduced in size. The session context in one or more session groups in the network element is migrated to the backup target second network element or the UDSF network element.

For example, when the SMF1 network element needs to be upgraded and maintained and the SMF1 network element needs to be shut down or the SMF1 network element needs to be downsized, the SMF1 network element can obtain the backup target second network element corresponding to the session group to be migrated from the SMF1 network element, and Send all session contexts in the session group to the target second network element.

For example, when the SMF1 network element is shut down or fails, the context of all sessions with the group ID of 000 can be sent to the SMF2 network element, and the context of all sessions with the group ID of 001 is sent to the SMF3 network element according to the content in Table 2.

Table 2 Correspondence between the backup target second network element and the session group identifier

Alternatively, when the SMF1 network element is downsized, according to the content in Table 3, only the context of all sessions with the group ID of 001 is sent to the SMF3 network element.

Table 3 Correspondence between the second network element and the session group identifier 2

S220. The source second network element sends the identification information of the source second network element and the identification of the first session to the first network element. Accordingly, the first network element may receive the identification information of the source second network element and the identification of the first session from the source second network element.

In the above description, the second network element is an SMF network element as an example. In this case, the first network element may be a UPF network element, an AMF network element, a PCF network element, a UDM network element, an NRF network element, or a UDSF network. yuan.

In the communication method in the embodiment of the present application, optionally, the source second network element may send second information to the first network element, where the second information may be a fully qualified session identifier (F-SEID). , A uniform resource descriptor (uniform resource identifier), a callback uniform resource descriptor (callback uniform resource identifier, callback URI), or a notification association identifier. The second information may include the identifier of the first session.

In the communication method in the embodiment of the present application, optionally, when the source second network element determines that it is no longer serving the session in the session group to which the first session belongs, it may send a notification message to the first network element. The notification message carries a conversation group identifier to which the first session belongs, and the notification message is used to notify the first network element that the second network element no longer provides services for the conversation group.

Optionally, if the source second network element can obtain the target second network element corresponding to the session group, the notification message may also carry identification information of the target second network element corresponding to the session group, so that other network elements correspond to the session corresponding Can determine the target second network element corresponding to the session.

The other network elements sent by the message include, for example, related AMF network elements, related UPF network elements, and related PCF network elements.

In the communication method in the embodiment of the present application, optionally, when the source second network element determines that it is no longer serving the session in the conversation group to which the first session belongs, the source second network element may send a registration request to the NRF network element or Registration update request message. The deregistration request is used to notify the NRF network element to register the source second network element. The registration update request message is used to notify the NRF network element that the source second network element no longer serves one or more session groups. In the update request message, the source second network element sends the no longer serviced session group identifier to the NRF. The network element, the NRF network element deletes the conversation group from the service list of the source second network element, and the subsequent NRF network element no longer selects the second network element when selecting the second network element according to the conversation group described in the first session. In this step, the OAM network element may send a registration request or a registration update request to the NRF network element instead of the source second network element.

In the communication method in the embodiment of the present application, optionally, the target second network element may send a registration update request to the NRF network element after receiving the session context, or the target second network element may detect the second network element Send a registration update request to the NRF network element after shutdown or failure. The registration update request is used to register the conversation group described in the first session as being served by the target second network element.

For example, the SMF2 network element sends a registration update request to the NRF network element, registers the session group 000 as being served by the SMF2 network element, the SMF3 network element sends a registration update request message to the NRF network element, and registers the session group 001 as being serviced by the SMF3 network element. . Subsequently, when other network elements query the corresponding second network element according to the session group identifier, the NRF network element selects the target second network element and sends the identification information of the target second network element to the other network elements.

S230. The first network element determines an identity of the first session.

For example, when the first network element needs to send a message related to the first session to the source second network element or the target second network element, the first network element determines the identity of the first session.

S240. The first network element sends the identifier of the first session to the target second network element. Accordingly, the target second network element may receive the identity of the first session from the first network element.

For example, when determining that the source second network element no longer serves the first session, the first network element may determine the target second network element and send the identification of the first session to the target second network element.

The first network element may determine that the source second network element is no longer serving the first session in any of the following situations:

The first network element receives a notification message sent by the source second network element in S220, and determines that the source second network element no longer provides services for the session according to the notification message;

The first network element sends a session-related message to the source second network element, and the first network element does not receive a response message from the source second network element;

The first network element sends a session-related message to the source second network element, and the first network element receives a rejection response message or a redirection response message from the source second network element.

The method for the first network element to determine the target second network element may include any one of the following:

If the first network element receives a notification message of the source second network element in S220, and the target second network element corresponding to the session group is specified in the notification message, the first network element may according to the session group corresponding to the first session The target second network element corresponding to the session is determined with the notification message.

The first network element queries the NRF network element for the target second network element. The first network element provides the NRF network element with a session group identifier corresponding to the first session, and the NRF network element determines the target second network element according to the session group identifier.

The first network element queries the NRF network element for the target second network element. The first network element provides the identifier of the second network element set to the NRF network element. The NRF network element selects a second network element from the second network element set as the target. SMF network element.

The first network element receives the redirection response from the source network element, and carries the identification information of the target second network element in the response message. The first network element determines the target second network according to the identification information of the target second network element in the response message. yuan.

In the communication method in the embodiment of the present application, optionally, the first network element may send the first information to the target second network element, where the first information may be any of F-SEID, URI, callback, URI, or notification association identifier. One item, the first information may include an identifier of the first session.

S250. The target second network element determines the first session according to the identifier of the first session.

For example, the target second network element may determine the session context of the first session according to the identifier of the first session and the session context of the session group to which the target second network element receives the first session from the source second network element in S210. . Alternatively, the target second network element may obtain the session context of the first session from the UDSF network element according to the identifier of the first session.

Optionally, after the target second network element determines the first session, related processing may be performed on the first session. For example, modify the session context of the first session.

In the embodiment of the present application, the identifier of the first session received by the target second network element from the first network element includes the identifier of the first session group to which the first session belongs and the first session in the first session group. Therefore, when the first session is migrated from the source second network element to the target second network element in the at least two second network elements, the target second network element can be caused to The identification of a session determines the first session, thereby continuing to provide services for the first session.

The following uses the source second network element as an SMF network element as an example to explain how the other network elements and the target control plane network element are different after the source SMF network element fails to work when other network elements are user plane network elements and control plane network elements. For communication.

FIG. 3 shows an exemplary flowchart of a communication method according to an embodiment of the present application. The other network elements in FIG. 3 are user plane network element UPF network elements, SMF1 network element is a source second network element, and SMF2 network element is a target network element. Two network elements.

In a possible implementation manner of the embodiment of the present application, an F-SEID identifier may be used between the SMF1 network element and the UPF network element to identify a session.

When establishing a session, the SMF1 network element may assign an F-SEID identifier to the session and send it to the UPF network element; or, the UPF network element may assign the F-SEID identifier to the session and send it to the SMF1 network element. In this way, in subsequent operations such as modifying or deleting the session, the SMF1 network element may carry the F-SEID identifier when sending a message to the UPF network element, or it needs to send to the SMF1 network element when the UPF network element has a session-related message. At this time, the UPF network element can carry the F-SEID identifier in the message sent to the SMF1 network element, so that both the SMF1 network element and the UPF network element can find the session according to the F-SEID identifier in the message.

Optionally, the F-SEID identifier assigned to the session by the SMF1 network element may include identification information of the SMF1 network element and a session identifier. The session identifier is used to uniquely identify the session in the SMF network element set. The identification information herein may refer to the FQDN. Or IP address. In a possible implementation manner of the embodiment of the present application, the session identifier may be composed of a session group identifier and a session group identifier.

When the SMF1 network element fails to work normally, for example, when the SMF1 network element is shut down, fails, or is reduced in capacity, the session needs to be migrated from the SMF1 network element to the SMF2 network element. If the UPF network element needs to modify or delete the session, the UPF network element first selects the SMF2 network element, and then the UPF network element needs to carry the above session identifier, because the session identifier can uniquely identify the session in the SMF network element set The SMF2 network element can find the corresponding session according to the session identifier.

In the embodiment of the present application, multiple control plane network elements may be regarded as one network element set. For example, in this application, the SMF network element set may be composed of the SMF1 network element and the SMF2 network element. The SMF network element in the SMF network element set may be configured with multiple session group identifiers. For example, the SMF1 network element is configured with the session group identifier 000. And 001, and the session group IDs 010 and 011 are configured in the SMF2 network element.

In a possible implementation manner of the embodiment of the present application, when a SMF1 network element creates a session (referred to as a first session in the embodiment of the present application), a session group configured by the SMF1 network element may be selected for the first session. The first conversation group identifier in the identifier is used as the conversation group identifier of the first session, and an intra-group identifier is determined for the session in the conversation group. The intra-group identifier can uniquely identify the session within the conversation group. . Then, the SMF1 network element uses the session group identifier and the session group identifier corresponding to the session to generate an F-SEID and sends it to the UPF network element.

Optionally, when the session group identifier is only provided by the SMF1 network element, the intra-session group identifier is allocated by the SMF1 network element; or, when the session group identifier can be shared by SMF network elements in the SMF network element set (for example, a session The group identity can also be provided by the SMF2 network element.) When assigning the identity within a conversation group, ensure that the identity within the conversation group allocated by different SMF network elements does not conflict in the conversation group. For example, one can be set in the SMF network element set. The network element is used to allocate the identity within the session group. Since the identity within the session group is uniformly allocated by one network element in the SMF network element set, the network element can be any one of the network elements in the SMF network element set, so the assigned The ID within a conversation group is unique among the conversation groups corresponding to the conversation. For example, when the SMF1 network element requests the network element to allocate a session group identifier for the first session, the network element can ensure that the allocated session group identifier is unique among the session groups corresponding to the first session.

Because the session group identifier is unique in the SMF network element set and the session group identifier is unique in the session group, the session identifier is unique in the SMF network element set.

In a possible implementation manner of the embodiment of the present application, the SMF1 network element may carry the session group identifier and the session group identifier in the F-SEID identifier allocated for the session. The F-SEID identifier may include the identification information of the SMF1 network element, the session group identifier corresponding to the session, and the session group identifier. The session identifier includes the session group identifier and the session group identifier corresponding to the session. The session group identifier may be in the session. The session is uniquely identified within the group.

Optionally, the identification information of the SMF network element may refer to an FQDN or an IP address

In a possible implementation manner of the embodiment of the present application, when the UPF network element finds that the SMF1 network element no longer provides services for the session, the UPF network element may obtain the identification information of the target SMF network element serving the session, and The identification information of the SMF1 network element in the F-SEID identification is replaced with the identification information of the target SMF network element.

In the embodiment of the present application, the method by which the UPF network element determines that the SMF1 network element no longer provides services for the session may be as described in FIG. 2, and details are not described herein again. Optionally, in the embodiments of the present application, other methods may also be used to determine that the SMF1 network element no longer provides services for the session, which is not limited in this application.

Similarly, when the SMF1 network element no longer provides services for the session, the method for the UPF network element to determine the target SMF network element for the session can be as described in FIG. 2, and will not be repeated here. Optionally, in the embodiments of the present application, other methods may also be used to determine the target SMF network element serving the session, which is not limited in this application.

Optionally, the session identifier in the F-SEID identifier may remain unchanged.

In the embodiment of the present application, since the session identifier is unique in the SMF network element set, the SMF2 network element can find a corresponding session according to the session identifier.

The processing flow when the UPF network element finds that the SMF1 network element is no longer serving the session is shown in FIG. 3 and includes the following steps.

S301. When the N4 interface between the UPF network element and the SMF1 network element is established, the SMF1 network element may send a session group identifier corresponding to the session group served by the SMF1 network element to the UPF network element through a network element level message. The conversation group ID can be a number.

Optionally, the SMF1 network element may send the identification information of the target SMF network element corresponding to the session group served by the SMF1 network element (for example, the target SMF network element corresponding to the session group 000 is an SMF2 network element) to the UPF network element. The identification information of the SMF network element may be, for example, the identification information of the target SMF network element, such as the FQDN or IP address of the SMF network element, or the instance identification of the SMF network element, which may be used to identify the target SMF network element.

S302. When establishing the first session, the SMF1 network element may determine an identifier corresponding to the first session, and send the identifier of the first session to the UPF network element, where the identifier of the first session may include the first session group identifier and the first ID within a conversation group.

As a possible implementation manner of this embodiment of the present application, the identifier of the first session may be sent to the UPF network element as a part of the F-SEID identifier.

S303. When the SMF1 network element no longer serves the first session, for example, when the SMF1 network element is shut down, fails, or is downsized, the SMF1 network element may send a network element level notification message to the UPF network element. The SMF1 network element may carry the identifier of the session group that it no longer serves, such as the first session group identifier, in the notification message.

For example, when the SMF1 network element is shut down, the SMF1 network element may carry the first conversation group identifier in the notification message sent to the UPF network element.

Optionally, the SMF1 network element may carry the information of the target SMF network element (for example, the SMF2 network element) corresponding to the session group corresponding to the first session in the notification message sent to the UPF network element.

S304. When the UPF network element needs to send a message to the target SMF network element serving the first session, the UPF network element may first determine that the target SMF network element is an SMF2 network element.

Specifically, the method for determining the target SMF network element serving as the first session by the UPF network element may be as described in FIG. 2, and details are not described herein again. Optionally, in the embodiments of the present application, other methods may also be used to determine the target SMF network element serving the first session, which is not limited in this application.

In the embodiment of the present application, the UPF network element generates a new F-SEID identifier according to the F-SEID identifier received in S302. The UPF network element replaces the IP address part of the original F-SEID identification with the IP address of the SMF2 network element, and the other parts remain unchanged. The UPF network element uses the new F-SEID identifier to send a message to the SMF2 network element.

S305. The UPF network element sends the new F-SEID identifier to the SMF2 network element.

S306. After receiving the new F-SEID identifier, the SMF2 network element determines the first session according to the identifier of the first session in the new F-SEID identifier, that is, the resource corresponding to the first session is determined. The subsequent information may be based on the received information. Process the first session accordingly.

Optionally, the SMF2 network element may also move the first session into another session group. For example, the session group identifiers configured for the SMF1 and SMF2 network elements are shown in Table 2. If the session group identifier of the first session is 000, the SMF2 network element is migrated after the first session is migrated from the SMF1 network element to the SMF2 network element. The first session can be moved into the conversation group 010 or 011, that is, the conversation group identifier of the first conversation can be changed from 000 to 010 or 011.

As a possible implementation manner of the embodiment of the present application, if the SMF2 network element moves the first session into another session group, the SMF2 network element may carry a new session group identifier of the first session in a response message sent to the UPF network element.

In the embodiment of the present application, the identifier of the first session in the F-SEID identifier is composed of the conversation group identifier and the identifier within the conversation group. In this way, when sending a message to the SMF2 network element, the UPF network element only needs to replace the The identification information is replaced with the identification information of the SMF2 network element, and other parts remain unchanged. Since the identifier of the first session is unique within the SMF network element set, the SMF network element can uniquely determine the first session according to the identifier of the first session.

FIG. 4 shows an exemplary flowchart of a communication method according to an embodiment of the present application. The other network elements in FIG. 4 are user plane network element UPF network elements, SMF1 network element is the source second network element, and SMF2 network element is the target network element. Two network elements. In the embodiment of the present application, as shown in FIG. 4, in order to support dynamic load balancing between SMF1 and SMF2, a service framework (Framework) network element may be added. At this time, the message sent to the SMF1 network element or the SMF2 network element may be sent to the Framework network element first, and the Framework network element decides which SMF network element to choose to provide services for it according to the load conditions of the SMF1 network element and the SMF2 network element.

It should be noted that the foregoing framework network element is only an example, and may also be implemented by other network elements or functions. In future networks, it may also be implemented by other services, which is not limited in this application. In the embodiment of the present application, Framework is used as an example for description.

It should be understood that, in this embodiment, a session may have a long-term or short-term binding relationship with a certain SMF network element. For example, the first session is served by the SMF1 network element within a certain period of time; There may be no binding relationship with the SMF network element. For example, the first session may be provided with a service by a different SMF network element in each different process or in each different message interaction process.

It should be understood that in this embodiment, the session context may be stored in the UDSF network element. When the SMF network element receives a message from another network element, the SMF network element may receive the message from the UDSF according to the first session identifier in the message. The network element obtains the context and processes the session.

In this embodiment, when the first session is established, the SMF network element serving it sends the identity of the first session to the UPF network element. When the UPF network element subsequently needs to send a message to the SMF network element, regardless of the actual Whether the SMF network element serving the session is an SMF1 network element or an SMF2 network element, the UPF network element sends the identity of the first session to the SMF network element.

Optionally, the session group identifier in the identifier of the first session may be the identifier of multiple session groups in the second network element set (that is, the identifier of the SMF network element set), or may be multiple sessions in the second network element set. The ID of a conversation group in the group.

Optionally, in order to enable the message to be sent to the framework network element, the SMF network element may send the identification information of the framework network element to the UPF network element when the first session is established.

S401. When the first session is established, the SMF1 network element provides services for the establishment of the first session. The SMF1 network element sends the identifier of the first session to the UPF network element, and the identifier of the first session includes a session group identifier and a session group identifier. In this embodiment, the identity of the first session is included in the F-SEID and sent to the UPF network element.

Optionally, SMF1 also sends identification information of the Framework network element to the UPF network element, for example, the IP address of the Framework network element.

Optionally, when the identification information of the framework network element is an IP address, the IP address of the framework network element may be sent to the UPF network element as an IP address in the F-SEID.

Optionally, the identification information of the Framework network element may be sent to the UPF through a cell independent of the F-SEID. At this time, the IP address in the F-SEID may be the IP address of the SMF1 network element.

S402. The SMF1 network element decides to no longer provide services for the first session.

For example, in one possible implementation, the SMF network element only serves a transaction once, and the session no longer provides service for the session; or, in another possible implementation, the SMF1 network element may be in When it is about to shut down, or when it is downsized, it is decided to no longer provide services for the first session. In this case, the SMF1 network element needs to notify the Framework network element to no longer provide services for the first session.

S403. The UPF network element needs to send a message related to the first session. For example, when the UPF network element receives a downlink data packet related to the first session and finds that there is no corresponding downlink tunnel, the UPF network element needs to send a downlink to the SMF network element. Data notification.

The UPF network element obtains the F-SEID corresponding to the first session. In this embodiment, the F-SEID includes the identifier of the first session. If the identification information of the Framework network element is received in S401, the F-SEID further includes the identification information of the Framework network element in order to send the message to the Framework network element.

Step 404: The Framework network element selects a target SMF network element for the first session. After the framework network element receives the message related to the first session, the framework network element selects the target SMF network element according to the identifier of the first session in the F-SEID. As shown in FIG. 4, in this embodiment, an SMF2 network element may be selected as a target SMF network element.

Specifically, the Framework network element selects the target SMF network element according to the session group identifier in the F-SEID. For example, when the framework network element saves the correspondence between the session group identifier and the target SMF network element, the framework network element can select the target SMF network element based on the correspondence; or, the framework network element can identify the session group identifier from the session group identifier. Any SMF network element is selected from the corresponding SMF network element set; or the target SMF network element is selected by other methods, which is not limited in this embodiment.

S405. The Framework network element sends a message related to the first session to the SMF2 network element. The message includes the F-SEID, and the F-SEID includes the identifier of the first session.

S406. The SMF2 network element determines the first session according to the identifier of the first session in the F-SEID identifier, that is, determines the resource corresponding to the first session, and then the first session may be processed accordingly according to the received information.

In the embodiment of the present application, the identifier of the first session in the F-SEID identifier is composed of a session group identifier and an identifier within the session group. In this way, when sending a message to the SMF2 network element, the UPF network element only needs to carry the The identity of the first session. Since the identifier of the first session is unique within the SMF network element set, the SMF network element can uniquely determine the first session according to the identifier of the first session.

FIG. 5 shows an exemplary flowchart of a communication method according to an embodiment of the present application. The other network elements in FIG. 5 are control plane network elements other than the SMF network element, and the other network elements in FIG. 5 are taken as an example of an AMF network element. Instructions. As shown in FIG. 5, the SMF1 network element is a source SMF network element, and the SMF2 network element is a target SMF network element.

In a possible implementation manner, when the SMF1 network element establishes a session, it may assign a context reference identifier to the session, and send the context reference identifier to the AMF network element. The AMF network element may use the context reference identifier to generate a URI when it subsequently needs to send a message related to the session, and send the URI to the SMF1 network element, where the URI may include the SMF identification information, the session identifier, and the session identifier. Includes the session group ID corresponding to the session and the session group ID of the session. The identification information of the SMF may be the FQDN of the SMF or the IP address of the SMF.

An exemplary format of the URI is: https: // <SMF name> / nsmf-pdusession / v1 / sm-contexts / SmContextRef, where SMF Name refers to the identification information of SMF, nsmf-pdusession is the service name, and V1 corresponds to the service Version, sm-contexts indicates that the URI operation object is the session context, and SmContextRef is the session ID.

Optionally, according to HTTP 2.0, the authorization domain (Authority) of the URI includes the identity of the SMF.

It should be understood that the URI in this embodiment is only exemplary. In actual use, except that the authorized domain must include the SMF identifier, other parts can be adjusted as needed, such as between the authorized domain and nsmf-pdusession. Inserting other content, etc., is not limited in this embodiment.

Optionally, the context reference identifier may be allocated by the SMF1 network element, and may be used to uniquely determine a resource corresponding to the session in the SMF1 network element.

When the SMF1 network element fails to work normally, for example, when the SMF1 network element is shut down, fails, or is reduced in capacity, the session needs to be migrated from the SMF1 network element to the SMF2 network element. If the AMF network element needs to modify or delete the session, the AMF network element first selects the SMF2 network element. Then, the AMF network element needs to send to the SMF2 network element an identifier that can be used to find the corresponding session for the SMF2 network element. A corresponding session is found according to the identifier corresponding to the session. At this time, the session identifier needs to be unique among the SMF1 network element and the SMF2 network element.

In this embodiment of the present application, multiple control plane network elements can be regarded as one network element set, and multiple session group identifiers are configured for each SMF network element in the SMF network element set. For example, it can be configured in the SMF1 network element. Conversation group identifiers 000 and 001. Configure the conversation group identifiers 010 and 011 in the SMF2 network element.

In a possible implementation manner of the embodiment of the present application, when a SMF1 network element creates a session, one of the session group identifiers configured by the SMF1 network element may be selected for the session as the session group identifier of the session, and in the session, In the group, a session ID is determined for the session, and the session ID can uniquely identify the session in the session group. Then, the SMF1 network element sends the session group identifier and the session group identifier corresponding to the session to the AMF network element.

In a possible implementation manner of the embodiment of the present application, the session identifier may be composed of a session group identifier and a session group identifier.

In the embodiment of the present application, the AMF network element may use a SmContextRef to generate a URI and send the URI to the SMF2 network element. The SmContextRef may include a session group identifier and a session group identifier corresponding to the session, thereby ensuring that the SmContextRef is in the SMF network element Unique within the collection. For example, the format of SmContextRef can be:

SmContextRef = / session-group-id <session group id> / SessionRefID

For example, if the session group identifier corresponding to the session is 000, the corresponding SmContextRef = / session-group-id000 / SessionRefIdInGroup.

It should be understood that the above is only an example. In actual application, as long as the Session-group-id field includes a session group identifier, and the SessioonRefID is unique in the session group or the SMF network element, it can be ensured that the SmContextRef is unique in the SMF network element set.

In this way, when the AMF network element needs to send the session-related message to the SMF2 network element, the AMF network element only needs to generate a URI in a certain format according to the identification information of the SMF2 network element and the original SmContextRef, and send the URI to SMF2. The network element is sufficient, and the authorized domain of the URI includes identification information of SMF2. The SMF2 network element can uniquely locate the session based on the SmContextRef in the received URI.

The SmContextRef includes a session group identifier and a session group identifier corresponding to the session. The identifier within the conversation group can uniquely identify the conversation within the conversation group.

In a possible implementation manner of the embodiment of the present application, when the AMF network element finds that the SMF1 network element no longer provides services for the session, the AMF network element can obtain the identification information of the SMF2 network element serving the session, and according to the SMF2 network Element identification information and the original SmContextRef, generate a URI according to a certain format, and use the URI to send the message related to the session to the SMF2 network element.

In the embodiment of the present application, the method by which the AMF network element determines that the SMF1 network element no longer provides services for the session may be as described in FIG. 2, and details are not described herein again. Optionally, in the embodiments of the present application, other methods may also be used to determine that the SMF1 network element no longer provides services for the session, which is not limited in this application.

Similarly, when the SMF1 network element no longer provides services for the session, the method by which the AMF network element determines the target SMF network element for the session can be as described in FIG. 2, and will not be repeated here. Optionally, in the embodiments of the present application, other methods may also be used to determine the target SMF network element serving the session, which is not limited in this application.

The processing flow when the AMF network element finds that the SMF1 network element is no longer serving the session is shown in FIG. 5 and includes the following steps.

S501. In a network element level initialization message or when the AMF network element and the SMF1 network element first exchange messages, the SMF1 network element may send the session group identifier corresponding to the session group served by the SMF1 network element to the AMF network element.

Optionally, the SMF1 network element may send the identification information of the target SMF network element (SMF2 network element) corresponding to the session group served by the SMF1 network element to the UPF network element, for example, the FQDN or IP address of the SMF2 network element may be sent. To UPF network element.

S502. When establishing the first session, the SMF1 network element may determine the identity of the first session and send the identity of the first session to the AMF network element, where the identity of the first session may include a session group identifier and a session group identifier. .

The SMF1 network element allocates the SmContextRef identifier. The SmContextRef identifier includes a session group identifier and a session group identifier. The SMF1 network element sends the SmContextRef identifier to the AMF network element.

S503. When the SMF1 network element no longer serves the first session, for example, when the SMF1 network element is shut down, fails, or is downsized, the SMF1 network element may send a network element level notification message to the AMF network element. The SMF1 network element may carry the identifier of the session group that it no longer serves in the notification message.

For example, when the SMF1 network element is shut down, the SMF1 network element may carry the identifier of the session group corresponding to the first session in the notification message sent to the AMF network element.

Optionally, the SMF1 network element may carry the identification information of the corresponding target SMF network element (SMF2 network element) in the notification message sent to the AMF network element.

S504. When the AMF network element needs to send a message to the target SMF network element serving the first session, the AMF network element may first determine that the target SMF network element is a SMF2 network element.

Specifically, the method for determining the target SMF network element serving the first session by the AMF network element may be as described in FIG. 2, and details are not described herein again. Optionally, in the embodiments of the present application, other methods may also be used to determine the target SMF network element serving the first session, which is not limited in this application.

S505: A new URI generated by the AMF network element according to the identification information of the SMF2 network element, and using the new URI to send a message to the SMF2 network element.

In the embodiment of the present application, the AMF network element generates a URI according to the identification information of the SMF2 network element and the SmContextRef identifier, and uses the newly generated URI to send a message (for example, a session update request) related to the first session to the SMF2 network element. .

S506. After receiving the message, the SMF2 network element determines the first session according to the identifier of the first session in the SmContextRef identifier in the URI, that is, determines the resource corresponding to the first session, and subsequently performs the first session according to the received information. Handle accordingly.

In the embodiment of the present application, if the SMF2 network element moves the first session into another conversation group, the SMF2 network element may carry a new session identifier of the first session in a response message sent to the AMF network element.

In the embodiment of the present application, the SmContextRef identifier is composed of a session group identifier and a session group identifier. In this way, when the other control plane sends a message to the SMF2 network element, it only needs to replace the authorized domain part in the original URI with the IP of the SMF2 network element. The address or FQDN, other parts remain unchanged. Because the SmContextRe identifier is unique within the SMF network element set, the SMF2 network element can uniquely determine the first session according to the SmContextRef identifier.

As a possible implementation manner of the embodiment of the present application, the source second network element may subscribe to events from other network elements.

For example, the SMF1 network element is a source second network element, the SMF2 network element is a target second network element, and the first network element is an AMF network element.

The SMF1 network element may subscribe to the AMF for a mobility event. For example, the SMF1 network element subscribes to a notification message that the UE moves out of or into a certain area. The subscription event is related to the session. Therefore, after the session is migrated to the SMF2 network element, if the event occurs, for example, the UE moves out of a certain area, the AMF network element needs to send a notification message of the event to the SMF network element.

In order to support notification of mobility events, the SMF1 network element sends a callback URI to the AMF network element when sending a notification message to the AMF network element.

Optionally, the SMF1 network element may also send a notification association identifier to the AMF network element.

In the embodiment of the present application, the SMF1 network element may determine the session subscribing to the notification message in the following two ways:

Method 1: uniquely determine the session through the callback URI.

In this way, the SMF1 network element may include sufficient information for positioning the session in the Callback URI sent to the AMF network element.

Method 2: Use the notification association identifier to uniquely determine the session.

In this manner, the SMF1 network element may send a notification association identifier to the AMF network element, where the notification association identifier may be used to uniquely determine the session.

After the session is migrated to the SMF2 network element, in order to ensure that the AMF network element can send the message to the SMF2 network element, the SMF2 network element can find the session. This embodiment uses the following method.

For the first method, the callback URI allocated by the source SMF network element includes a session group identifier and a session resource identifier, and the session resource identifier is unique within the session group. In this way, when the AMF network element needs to send a notification message, when generating the callback URI of the target SMF network element based on the callback URI provided by the source SMF network element, it is only necessary to replace the authorized domain part in the callback URI with the IP address or FQDN. Because the callback URI includes a session group identifier and a session resource identifier, the target SMF network element can uniquely locate the session context based on these two pieces of information. The format of the session group identifier and the session resource identifier in the callback URI may be similar to the foregoing definition of SmContextRef.

For the second method, the notification association identifier allocated by the source SMF network element also includes a session group identifier and a session resource identifier. The target SMF network element locates the session context according to the session group identifier and the session resource identifier in the notification association identifier. When an AMF network element sends a notification message, it only needs to replace the authorized domain part of the callback URI provided by the source SMF network element with the IP address or FQDN of the target SMF network element, and notify the association identifier to remain unchanged. The format of the notification association identifier may be similar to the definition of the aforementioned SmContextRef or similar to the definition of the session identifier in the F-SEID.

In this embodiment, the Callback URI or the notification association identifier includes a session group identifier and a session unique identifier. In this way, when other control planes send a notification message to the target SMF network element, only the SMF authorization domain part in the original URI needs to be replaced with The IP address or FQDN of the target SMF network element remains unchanged.

FIG. 6 is a schematic block diagram of a network element 600 according to an embodiment of the present application. It should be understood that the network element 600 is only an example. The network element in the embodiment of the present application may further include other modules or units, or include modules similar in function to each module in FIG. 6, or may not include all modules in FIG. 6.

A processing module 610 is configured to determine an identifier of a first session, where the first session is a session served by a source second network element among at least two second network elements, and the identifier of the first session is used in the The plurality of sessions served by the at least two second network elements uniquely indicate the first session, wherein the plurality of sessions served by the at least two second network elements are divided into a plurality of session groups, and the first The identifier of a session includes a first identifier and a second identifier. The first identifier is used to indicate a first conversation group to which the first session belongs, and the second identifier is used to include the first conversation group in the first conversation group. The first session is uniquely indicated in the session;

A sending module 620, configured to: when the first session is migrated from the source second network element to a target second network element among the at least two second network elements, the first network element sends The target second network element sends the identifier of the first session.

Optionally, the sending module is specifically configured to send first information to the target second network element, where the first information includes identification information of the target second network element and identification of the first session.

Optionally, the network element further includes a receiving module, configured to receive the second information from the source second network element before the network element sends the first information to the target second network element. The second information includes identification information of the source second network element and the identification of the first session. The processing module is further configured to replace the identification information of the source second network element in the second information with the identification information of the target second network element to obtain the first information.

Optionally, the receiving module is further configured to receive third information from the target second network element, where the third information includes identification information of the target second network element and the target second network element The conversation group ID of the conversation group for the service.

Optionally, the second information is any one of a full session identifier F-SEID, a uniform resource descriptor URI, a callback universal resource descriptor callback URI, or a notification association identifier, and the first information includes the first session Logo.

Optionally, the processing module 610 is further configured to: when the second information is an F-SEID, the IP address carried by the Internet Protocol IP address field in the F-SEID is obtained from the source second network element. The IP address is replaced with the IP address of the target second network element; or when the second information is a URI, the fully qualified domain name FQDN carried in the authorized domain field in the URI is removed from the source second network element. FQDN is replaced with the FQDN of the target second network element, or the IP address carried in the authorized domain field in the URI is replaced from the IP address of the source second network element with the IP address of the target second network element Or when the second information is a callback URI, replace the FQDN carried in the authorized domain field in the callback URI from the FQDN of the source second network element with the FQDN of the target second network element, or Replacing the IP address carried in the authorization field in the callback URI from the IP address of the source second network element with the IP address of the target second network element; or when the second information is a notification association identifier, The FQDN carried in the authorization domain field in the callbackURI is replaced with the FQDN of the source second network element by The FQDN of the target second network element, or replace the IP address carried in the authorized domain field in the callback URI from the IP address of the source second network element with the IP address of the target second network element, where The callback URI and the notification association identifier are sent in the same message.

Optionally, the network element 600 is any of the following: a user plane function UPF network element, an access and mobility management function AMF network element, a session management function SMF network element, a policy management function PCF network element, and an authentication server function AUSF network element, unified data management UDM network element, network element storage function NRF network element or unstructured data storage function UDSF network element.

Optionally, the second network element is any one of the following: an access and mobility management network element, a session management network element, a policy management network element, an authentication server network element, a unified data management network element, Network element storage function network element or unstructured data storage function network element.

The network element 600 may be used to perform the steps performed by the first network element in the method described in FIG. 2. For brevity, details are not described herein again.

FIG. 7 is a schematic block diagram of a network element 700 according to an embodiment of the present application. It should be understood that the network element 700 is only an example. The network element in the embodiment of the present application may further include other modules or units, or include modules similar in function to each module in FIG. 7, or not all modules in FIG. 7.

A processing module 710, configured to determine an identifier of a first session, where the first session is a session served by at least two second network elements, and the identifier of the first session is used to The plurality of sessions served uniquely indicates the first session, wherein the plurality of sessions served in the at least two second network elements are divided into a plurality of session groups, and an identifier of the first session includes a first session. An identifier and a second identifier, where the first identifier is used to uniquely indicate, among the multiple conversation groups, a first conversation group to which the first session belongs, and the second identifier is used to identify The session included in the group uniquely indicates the first session;

The sending module 720 is configured to send the identifier of the first session to a target second network element among the at least two second network elements.

Optionally, the sending module 720 is specifically configured to send first information to the target second network element, where the first information includes an identifier of the first session.

Optionally, the first information is a full session identifier F-SEID.

Optionally, the processing module 710 is further configured to: replace an IP address carried in an Internet Protocol (IP) address field in the F-SEID from the IP address of the source second network element with the The IP address of the target second network element; or the IP address carried in the Internet Protocol address field in the F-SEID is set to the IP address of the service frame.

Optionally, the network element further includes a receiving module 730, configured to receive second information from the source second network element, where the second information includes an identifier of the first session.

Optionally, the second information is a full session identifier F-SEID.

Optionally, the second message further includes an IP address of a service frame network element corresponding to the second network element.

Optionally, the network element 700 is a user plane function UPF network element.

Optionally, the source second network element is a session management function SMF network element.

FIG. 8 is a schematic block diagram of a network element 800 according to an embodiment of the present application. It should be understood that the network element 800 is only an example. The network element in the embodiment of the present application may further include other modules or units, or include modules similar in function to each module in FIG. 8, or may not include all modules in FIG. 8.

The processing module 810 is configured to generate an identifier of a first session, where the first session is a session served by the source second network element among at least two second network elements, and the identifier of the first session is used at The plurality of sessions served by the at least two second network elements uniquely indicate the first session, wherein the plurality of sessions served by the at least two second network elements are divided into a plurality of session groups, so The identifier of the first session includes a first identifier and a second identifier, and the first identifier is used to uniquely indicate, among the multiple conversation groups, a first conversation group to which the first session belongs, and the second identifier Configured to uniquely indicate the first session among the sessions included in the first session group;

The sending module 820 is configured to send the identifier of the first session to the first network element.

Optionally, the sending module 820 is specifically configured to send second information to the first network element, where the second information includes identification information of a target second network element among the at least two second network elements And the identity of the first session.

Optionally, the second information is any one of a full session identifier F-SEID, a uniform resource descriptor URI, a callback uniform resource descriptor callback URI, or a notification association identifier.

Optionally, the network element 800 is any of the following: an access and mobility management function AMF network element, a session management function SMF network element, a policy management function PCF network element, an authentication server function AUSF network element, and unified data management UDM network element, network element storage function NRF network element or unstructured data storage function UDSF network element.

The network element 800 may be used to perform the steps performed by the source second network element in the method described in FIG. 2. For brevity, details are not described herein again.

FIG. 9 is a schematic block diagram of a network element 900 according to an embodiment of the present application. It should be understood that the network element 900 is merely an example. The network element in the embodiment of the present application may further include other modules or units, or include modules similar in function to each module in FIG. 9, or may not include all modules in FIG. 9.

The receiving module 910 is configured to receive an identifier of a first session from a first network element, where the first session is a session served by a source second network element among at least two second network elements, and the identifier of the first session is Configured to uniquely indicate the first session among multiple sessions served by the at least two second network elements, where the multiple sessions served by the at least two second network elements are divided into multiple sessions Group, the identifier of the first session includes a first identifier and a second identifier, and the first identifier is used to uniquely indicate, among the multiple conversation groups, a first conversation group to which the first session belongs, the The second identifier is used to uniquely indicate the first session among the sessions included in the first session group;

The processing module 920 is configured to determine the first session according to the identifier of the first session.

Optionally, the receiving module 910 is specifically configured to receive first information from the first network element, where the first information includes identification information of the network element and an identification of the first session.

Optionally, the first information is any one of a full session identifier F-SEID, a uniform resource descriptor URI, a callback uniform resource descriptor callback URI, or a notification association identifier.

Optionally, the network element 900 is any of the following: an access and mobility management function AMF network element, a session management function SMF network element, a policy management function PCF network element, an authentication server function AUSF network element, and unified data management UDM network element, network element storage function NRF network element or unstructured data storage function UDSF network element.

The network element 900 may be used to perform the steps performed by the target second network element in the method described in FIG. 2. For brevity, details are not described herein again.

FIG. 10 is a schematic structural diagram of a network element according to an embodiment of the present application. It should be understood that the network element 10100 shown in FIG. 10 is merely an example, and the network element in the embodiment of the present application may further include other modules or units, or include modules similar in function to each module in FIG. 10.

The network element 1000 may include one or more processors 1010, one or more memories 1020, a receiver 1030, and a transmitter 1040. The receiver 1030 and the transmitter 1040 may be integrated together and called a transceiver. The memory 1020 is configured to store a program code executed by the processor 1010. Wherein, the processor 1010 may be integrated with a memory 1020, or the processor 1010 is coupled to one or more memories 1020, and is configured to retrieve instructions in the memory 1020.

In one embodiment, the processor 1010 may be used to implement operations or steps that can be implemented by the processing module 610 in FIG. 6, and the transmitter 1040 may be used to implement operations or steps that can be implemented by the sending module 620 in FIG. 6. 1030 may be used to implement operations or steps that can be implemented by the receiving module 630 in FIG. 6.

In another embodiment, the processor 1010 may be used to implement operations or steps that can be implemented by the processing module 710 in FIG. 7, and the transmitter 1040 may be used to implement operations or steps that can be implemented by the sending module 720 in FIG. 7, and receive The receiver 1030 may be used to implement operations or steps that can be implemented by the receiving module 730 in FIG. 7.

In another embodiment, the processor 1010 may be used to implement operations or steps that can be implemented by the determination module 810 in FIG. 8, and the transmitter 1040 may be used to implement operations or steps that can be implemented by the sending module 820 in FIG.

In another embodiment, the processor 1010 may be used to implement operations or steps that can be implemented by the processing module 920 in FIG. 9, and the receiver 1030 may be used to implement operations or steps that can be implemented by the receiving module 910 in FIG. 9.

It should be understood that the processor in the embodiment of the present application may be a central processing unit (CPU), and the processor may also be other general-purpose processors, digital signal processors (DSPs), and application-specific integrated circuits. (application specific integrated circuit (ASIC)), ready-made programmable gate array (field programmable gate array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

It should also be understood that the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory. Among them, the non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (erasable PROM, EPROM), electrical memory Erase programmable read-only memory (EPROM, EEPROM) or flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example but not limitation, many forms of random access memory (RAM) are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access Access memory (synchronous DRAM (SDRAM)), double data rate synchronous dynamic random access memory (double SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection dynamic random access memory Fetch memory (synchlink DRAM, SLDRAM) and direct memory bus random access memory (direct RAMbus RAM, DR RAM).

The above embodiments may be implemented in whole or in part by software, hardware, firmware, or any other combination. When implemented using software, the above embodiments may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions or computer programs. When the computer instructions or computer programs are loaded or executed on a computer, the processes or functions according to the embodiments of the present application are wholly or partially generated. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be from a website site, computer, server, or data center Transmission by wire (for example, infrared, wireless, microwave, etc.) to another website site, computer, server, or data center. The computer-readable storage medium may be any available medium that can be accessed by a computer, or a data storage device such as a server, a data center, or the like, containing one or more sets of available media. The usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium. The semiconductor medium may be a solid state drive.

It should be understood that the term “and / or” in this document is only an association relationship describing an associated object, which means that there can be three kinds of relationships, for example, A and / or B can mean: A exists alone, and A and B exist simultaneously. There are three cases of B alone. In addition, the character "/" in this article generally indicates that the related objects are an "or" relationship.

It should be understood that, in the various embodiments of the present application, the size of the sequence numbers of the above processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not deal with the embodiments of this application The implementation process constitutes any limitation.

Those of ordinary skill in the art may realize that the units and algorithm steps of each example described in connection with the embodiments disclosed herein can be implemented by electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices, and units described above can refer to the corresponding processes in the foregoing method embodiments, and are not repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods may be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the unit is only a logical function division. In actual implementation, there may be another division manner. For example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not implemented. In addition, the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, which may be electrical, mechanical or other forms.

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

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each of the units may exist separately physically, or two or more units may be integrated into one unit.

If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application is essentially a part that contributes to the existing technology or a part of the technical solution can be embodied in the form of a software product. The computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in the embodiments of the present application. The aforementioned storage media include: U disks, mobile hard disks, read-only memories (ROMs), random access memories (RAMs), magnetic disks or compact discs and other media that can store program codes .

The above is only a specific implementation of this application, but the scope of protection of this application is not limited to this. Any person skilled in the art can easily think of changes or replacements within the technical scope disclosed in this application. It should be covered by the protection scope of this application. Therefore, the protection scope of this application shall be subject to the protection scope of the claims.

Claims

A communication method, comprising:

The first network element determines an identifier of a first session, where the first session is a session served by a source second network element, and the identifier of the first session is used for multiple sessions served by at least two second network elements The only indication is the first session, wherein the plurality of sessions served by the at least two second network elements are divided into a plurality of session groups, and an identifier of the first session includes a first identifier and a second identifier, The first identifier is used to uniquely indicate, among the multiple conversation groups, a first conversation group to which the first session belongs, and the second identifier is used to uniquely indicate among the sessions included in the first conversation group. The first session;

When the first session is migrated from the source second network element to a target second network element among the at least two second network elements, the first network element sends to the target second network element The identity of the first session.
The communication method according to claim 1, wherein the sending, by the first network element, the identifier of the first session to the target second network element comprises:

The first network element sends first information to the target second network element, and the first information includes identification information of the target second network element and the identification of the first session.
The communication method according to claim 2, wherein before the first network element sends the first information to the target second network element, the communication method further comprises:

Receiving, by the first network element, second information from the source second network element, where the second information includes identification information of the source second network element and the identification of the first session;

The first network element replaces the identification information of the source second network element in the second information with the identification information of the target second network element to obtain the first information.
The communication method according to claim 3, wherein the second information is any one of a full session identifier F-SEID, a uniform resource descriptor URI, a callback uniform resource descriptor callback URI, or a notification association identifier.
The communication method according to claim 4, wherein the first network element replaces the identification information of the source second network element in the second information with the identification information of the target second network element ,include:

When the second information is F-SEID, replace the IP address carried in the IP address field of the Internet Protocol in the F-SEID from the IP address of the source second network element to the target second network element. IP address; or

When the second information is a URI, replace the fully qualified domain name FQDN carried in the authorized domain field in the URI from the FQDN of the source second network element to the FQDN of the target second network element, or replace the Replacing the IP address carried in the authorized domain field in the URI from the IP address of the source second network element with the IP address of the target second network element; or

When the second information is a callback URI, replacing the FQDN carried in the authorization domain field in the callback URI from the FQDN of the source second network element with the FQDN of the target second network element, or replace the IP address carried in the authorization field in the callback URI from the IP address of the source second network element with the IP address of the target second network element; or

When the second information is a notification association identifier, replace the FQDN carried in the authorized domain field in the callback URI from the FQDN of the source second network element with the FQDN of the target second network element, or replace the callback The IP address carried in the authorized domain field in the URI is replaced from the IP address of the source second network element by the IP address of the target second network element, wherein the callback URI and the notification association identifier are in the same message Sending.
A communication method, comprising:

The source second network element generates an identifier of a first session, where the first session is a session served by the source second network element in at least two second network elements, and the identifier of the first session is used to The plurality of sessions served by the at least two second network elements uniquely indicate the first session, wherein the plurality of sessions served by the at least two second network elements are divided into a plurality of session groups, and The identifier of the first session includes a first identifier and a second identifier, and the first identifier is used to uniquely indicate, among the multiple conversation groups, a first conversation group to which the first session belongs, and the second identifier is used for Uniquely indicating the first session among the sessions included in the first session group;

Sending, by the source second network element, the identity of the first session to the first network element.
The communication method according to claim 6, wherein the source second network element sending the identifier of the first session to the first network element comprises:

The source second network element sends second information to the first network element, the second information includes identification information of the target second network element in the at least two second network elements and the first session Logo.
The communication method according to claim 7, wherein the second information is any one of a full session identifier F-SEID, a uniform resource descriptor URI, a callback uniform resource descriptor callback URI, or a notification association identifier.
A communication method, comprising:

The target second network element receives the identifier of the first session from the first network element. The first session is a session served by the source second network element in at least two second network elements, and the identifier of the first session is The first session is uniquely indicated among a plurality of sessions served by the at least two second network elements, wherein the plurality of sessions served by the at least two second network elements are divided into a plurality of session groups The identifier of the first session includes a first identifier and a second identifier, and the first identifier is used to uniquely indicate, among the multiple conversation groups, a first conversation group to which the first session belongs, and the first Two identifiers are used to uniquely indicate the first session among the sessions included in the first session group;

The target second network element determines the first session according to the identifier of the first session.
The communication method according to claim 9, wherein the target second network element receiving the identifier of the first session from the first network element comprises:

The target second network element receives first information from the first network element, and the first information includes identification information of the target second network element and identification of the first session.
The communication method according to claim 10, wherein the first information is any one of a full session identifier F-SEID, a uniform resource descriptor URI, a callback uniform resource descriptor callback URI, or a notification association identifier.
The communication method according to any one of claims 1 to 11, wherein the first network element is any one of the following:

User plane function UPF network element, access and mobility management function AMF network element, session management function SMF network element, policy management function PCF network element, authentication server function AUSF network element, unified data management UDM network element, network element storage function NRF network element or unstructured data storage function UDSF network element.
The communication method according to any one of claims 1 to 12, wherein the second network element is any one of the following:

Access and mobility management function AMF network element, session management function SMF network element, policy management function PCF network element, authentication server function AUSF network element, unified data management UDM network element, network element storage function NRF network element or unstructured Data storage function UDSF network element.
A network element, comprising:

A processing module, configured to determine an identifier of a first session, where the first session is a session served by a source second network element in at least two second network elements, and the identifier of the first session is used in the at least two The plurality of sessions served by two second network elements uniquely indicate the first session, wherein the plurality of sessions served by the at least two second network elements are divided into a plurality of session groups, and the first The identifier of the session includes a first identifier and a second identifier, and the first identifier is used to uniquely indicate, among the multiple conversation groups, a first conversation group to which the first session belongs, and the second identifier is used to The session included in the first session group uniquely indicates the first session;

A sending module, configured to: when the first session is migrated from the source second network element to a target second network element among the at least two second network elements, the first network element sends the The target second network element sends the identifier of the first session.
The network element according to claim 14, wherein the sending module is specifically configured to send first information to the target second network element, and the first information includes identification information of the target second network element And the identity of the first session.
The network element according to claim 15, wherein the network element further comprises a receiving module, configured to receive the second information from the source before the network element sends the first information to the target second network element. The network element receives second information, the second information includes identification information of the source second network element and the identification of the first session;

The processing module is further configured to replace the identification information of the source second network element in the second information with the identification information of the target second network element to obtain the first information.
The network element according to claim 16, wherein the second information is any one of a full session identifier F-SEID, a uniform resource descriptor URI, a callback uniform resource descriptor callback URI, or a notification association identifier. The first information includes an identifier of the first session.
The network element according to claim 17, wherein the processing module is further configured to:

When the second information is F-SEID, replace the IP address carried in the IP address field of the Internet Protocol in the F-SEID from the IP address of the source second network element to the target second network element. IP address; or

When the second information is a URI, replace the fully qualified domain name FQDN carried in the authorized domain field in the URI from the FQDN of the source second network element to the FQDN of the target second network element, or replace the Replacing the IP address carried in the authorized domain field in the URI from the IP address of the source second network element with the IP address of the target second network element; or

When the second information is a callback URI, replacing the FQDN carried in the authorization domain field in the callback URI from the FQDN of the source second network element with the FQDN of the target second network element, or replace the IP address carried in the authorization field in the callback URI from the IP address of the source second network element with the IP address of the target second network element; or

When the second information is a notification association identifier, replace the FQDN carried in the authorized domain field in the callback URI from the FQDN of the source second network element with the FQDN of the target second network element, or replace the callback The IP address carried in the authorized domain field in the URI is replaced from the IP address of the source second network element by the IP address of the target second network element, wherein the callback URI and the notification association identifier are in the same message Sending.
The network element according to any one of claims 14 to 18, wherein the network element is any one of the following: a user plane function UPF network element, an access and mobility management function AMF network element, and session management Function SMF network element, policy management function PCF network element, authentication server function AUSF network element, unified data management UDM network element, network element storage function NRF network element or unstructured data storage function UDSF network element.
The network element according to any one of claims 14 to 19, wherein the source second network element is any one of the following:

Access and mobility management network elements, session management network elements, policy management network elements, authentication server network elements, unified data management network elements, network element storage network elements, or unstructured data storage network elements.
A network element, comprising:

A processing module, configured to generate an identifier of a first session, where the first session is a session served by the source second network element in at least two second network elements, and the identifier of the first session is used in The plurality of sessions served by the at least two second network elements uniquely indicate the first session, wherein the plurality of sessions served by the at least two second network elements are divided into a plurality of session groups, and The identifier of the first session includes a first identifier and a second identifier, and the first identifier is used to uniquely indicate, among the multiple conversation groups, a first conversation group to which the first session belongs, and the second identifier is used for Uniquely indicating the first session among the sessions included in the first session group;

A sending module, configured to send the identifier of the first session to the first network element.
The network element according to claim 21, wherein the sending module is specifically configured to:

And sending second information to the first network element, where the second information includes identification information of a target second network element in the at least two second network elements and an identifier of the first session.
The network element according to claim 22, wherein the second information is any one of a full session identifier F-SEID, a uniform resource descriptor URI, a callback uniform resource descriptor callback URI, or a notification association identifier.
The network element according to any one of claims 21 to 23, wherein the network element is any one of the following: an access and mobility management function AMF network element, a session management function SMF network element, and policy management Function PCF network element, authentication server function AUSF network element, unified data management UDM network element, network element storage function NRF network element or unstructured data storage function UDSF network element.
A network element, comprising:

A receiving module, configured to receive an identifier of a first session from a first network element, where the first session is a session served by a source second network element in at least two second network elements, and the identifier of the first session is The first session is uniquely indicated among a plurality of sessions served by the at least two second network elements, wherein the plurality of sessions served by the at least two second network elements are divided into a plurality of session groups The identifier of the first session includes a first identifier and a second identifier, and the first identifier is used to uniquely indicate, among the multiple conversation groups, a first conversation group to which the first session belongs, and the first Two identifiers are used to uniquely indicate the first session among the sessions included in the first session group;

A processing module, configured to determine the first session according to the identifier of the first session.
The network element according to claim 25, wherein the receiving module is specifically configured to:

Receiving first information from the first network element, where the first information includes identification information of the network element and an identification of the first session.
The network element according to claim 26, wherein the first information is any one of a full session identifier F-SEID, a uniform resource descriptor URI, a callback uniform resource descriptor callback URI, or a notification association identifier.
The network element according to any one of claims 25 to 27, wherein the network element is any one of the following: an access and mobility management function AMF network element, a session management function SMF network element, and policy management Function PCF network element, authentication server function AUSF network element, unified data management UDM network element, network element storage function NRF network element or unstructured data storage function UDSF network element.