JP7683750B2 - METHOD AND COMMUNICATION APPARATUS FOR DETERMINING ISOLATION BETWEEN USER PLANE NETWORK ELEMENTS - Patent application - Google Patents

Description

Embodiments of the present application relate to the field of communications technologies, and in particular to a method and a communications device for determining separation between user plane network elements.

The user plane and the control plane can be located centrally or separately. In a control and user plane separation scenario, for example, most of the control plane network elements are located centrally in state capitals or regional centers, and the user plane network elements are located in cities close to the users. In this deployment scenario, a moving terminal device is likely to cross the areas managed by the user plane service network elements. However, during the movement of the terminal device, the user plane network elements are usually anchored and do not change. For example, in an evolved packet core (EPC) scenario or when a 5th generation (5G) terminal device activates a session and service continuity (SSC) mode 1 (Mode 1) protocol data unit (PDU) session, the 3rd generation partnership project (3GPP) protocol requires that the user plane network providing data services to the terminal device must be anchored and unchanged during the movement of the terminal device. In this case, the two user plane network elements may be separated, resulting in traffic diversion.

In view of this, it needs to be determined whether the user plane network elements are separated in the control and user plane split scenario, and further measures need to be taken to avoid traffic diversion. Therefore, how to determine whether the user plane network elements are separated in the control and user plane split scenario is a problem to be solved.

Embodiments of the present application provide a method and a communication device for determining separation between user plane network elements to determine whether the user plane network elements are separated in a control and user plane separation scenario.

According to a first aspect, a method for determining separation between user plane network elements is provided. The method may be applied to a control and user plane separation scenario, or the method may be applied to a control and user plane separation communication system. The method may be executed by a first control plane network element, or may be executed by a component of the first control plane network element. For example, the method is executed by the first control plane network element. The method may be implemented by using the following steps: the first control plane network element obtains a first node identifier of the first user plane network element and a second node identifier of the second user plane network element, the first control plane network element including a serving gateway for control plane SGW-C (which may be denoted as the first SGW-C), a data network PDN gateway for control plane PGW-C (which may be denoted as the first PGW-C), a session management function network element SMF, or an intermediate session management function network element I-SMF. The first user plane network element is a user plane anchor. The first control plane network element determines whether the first user plane network element is isolated from the second user plane network element based on the first node identifier and the second node identifier. The first control plane network element compares the node identifiers of the two user plane network elements to determine whether the user plane network elements are isolated, so that whether the user plane gateways are isolated can be determined in a control and user plane isolation scenario, and the efficiency and accuracy of determining isolation between the user plane gateways can be improved, so that measures can be taken in a timely manner when the user plane gateways are isolated to avoid traffic diversion.

The following is explained based on a first type of control plane network element.

When the first control plane network element is the first SGW-C or the first PGW-C, the following possible designs may be provided:

According to the first aspect, the method may be implemented by using the following steps: a first control plane network element obtains a node identifier of a first PGW-U and a node identifier of a first SGW-U. The first control plane network element determines whether a user plane gateway is disjoint based on the node identifier of the first PGW-U and the node identifier of the first SGW-U, the user plane gateway including an SGW-U and a PGW-U denoted as the first SGW-U and the first PGW-U. That is, the first control plane network element determines whether the first SGW-U is disjoint from the first PGW-U based on the node identifier of the first PGW-U and the node identifier of the first SGW-U. The first PGW-U is a user plane anchor for a terminal device to access a PDN. The first control plane network element may be a first SGW-C or a first PGW-C. The first control plane network element determines whether the first SGW-U is isolated from the first PGW-U based on the node identifier of the first PGW-U and the node identifier of the first SGW-U, so that whether the user plane network element is isolated can be determined in a CUPS scenario, and the efficiency and accuracy of determining isolation between user plane network elements can be improved, so that measures can be taken in a timely manner when the user plane network element is isolated to avoid traffic diversion.

In a possible design, the first control plane network element is an SGW-C. The first control plane network element may obtain a node identifier of the first PGW-U in the following manner: the SGW-C obtains the node identifier of the first PGW-U from the PGW-C, and the PGW-C is a control plane anchor for the terminal device to access the PDN.

When the SGW-C and PGW-C are located in the same control plane gateway node, the SGW-C can obtain the node identifier of the first PGW-U from the local PGW-C, that is, by using an internal message, it can reduce the signaling overhead and does not require changes to the signaling of the existing protocol.

When the SGW-C and PGW-C are located in different control plane gateway nodes, the PGW-C can obtain the node identifier of the first PGW-U by exchanging messages with the SGW-C. For example, the SGW-C receives a Modify Bearer Response message from the PGW-C, and the Modify Bearer Response message carries the node identifier of the first PGW-U. In this way, the node identifier can be carried in existing signaling to determine the separation between user plane network elements.

In a possible design, the first control plane network element is a PGW-C, which is a control plane anchor for a terminal device to access the PDN. The first control plane network element may obtain a node identifier of the first SGW-U in the following manner: The PGW-C obtains a node identifier of the first SGW-U from the SGW-C.

When the SGW-C and PGW-C are located in the same control plane gateway node, the PGW-C can obtain the node identifier of the first SGW-U from the local SGW-C, that is, by using an internal message. This can reduce the signaling overhead and does not require changes to the signaling of existing protocols.

When the SGW-C and the PGW-C are located in different control plane gateway nodes, the SGW-C can obtain the node identifier of the first SGW -U by exchanging messages with the PGW-C. For example, the PGW-C receives a Modify Bearer Request message from the SGW-C, and the Modify Bearer Request message carries the node identifier of the first SGW-U. In this way, the node identifier can be carried in existing signaling to determine the separation between user plane network elements.

In the following design of the determination method for determining whether the first SGW-U is detached from the first PGW-U, the node identifier of the first SGW-U and the node identifier of the first PGW-U can be expressed by using the first node identifier and the second node identifier, respectively.

In a possible design, the first control plane network element determining whether the first SGW-U is detached from the first PGW-U based on the first node identifier and the second node identifier may include the following method: if the first node identifier is the same as the second node identifier, determine that the first SGW-U is not detached from the first PGW-U, or if the first node identifier is different from the second node identifier, determine that the first SGW-U is detached from the first PGW-U. This determination method is strict and accurate. Using this determination method to determine detachment between user plane network elements may help to improve the determination accuracy. Furthermore, in this determination method, the node identifiers do not need to be named in a structured manner. If the node identifier is currently configured in the on-net device, the on-net device does not need to change the node identifier.

In a possible design, the first control plane network element determining whether the first SGW-U is detached from the first PGW-U based on the first node identifier and the second node identifier may further include the following method: determining that the first SGW-U is not detached from the first PGW-U if the first information in the first node identifier is the same as the second information in the second node identifier, or determining that the first SGW-U is detached from the first PGW-U if the first information in the first node identifier is different from the second information in the second node identifier, the first information indicating the area in which the first SGW-U is located and the second information indicating the area in which the first PGW-U is located. When the two user plane network elements are not in the same node but in the same area, the path transmission redundancy is not so large and the requirement for PDN re-establishment is not so high. In this determination method, whether the user plane network elements are detached can be flexibly determined. Compared to the method of determining that a user plane network element is separated across user plane network elements, in this determination method, the user plane network element is determined to be separated only when an area spans between the user plane network elements, and an operation, for example, PDN re-establishment, is further performed after the separation. This can avoid signaling consumption caused by unnecessary PDN re-establishment.

In a possible design, the first control plane network element determining whether the first SGW-U is detached from the first PGW-U based on the first node identifier and the second node identifier may further include the following method: if the first node identifier and the second node identifier are in the same group, determine that the first SGW-U is not detached from the first PGW-U; or if the first node identifier and the second node identifier are not in the same group, determine that the first SGW-U is detached from the first PGW-U, and the SGW-U and PGW-U in the group are located in the same area. When the two user plane network elements are not in the same node but in the same area, the path transmission redundancy is not so large and the requirement for PDN re-establishment is not so high. In this determination method, whether the user plane network elements are detached can be flexibly determined. Compared with the method of determining that a user plane network element is separated across user plane network elements, in this determination method, the user plane network element is determined to be separated only when an area spans between the user plane network elements, and an operation, for example, PDN re-establishment, is further performed after the separation. This can avoid signaling consumption caused by unnecessary PDN re-establishment. Furthermore, in this determination method, the node identifier does not need to be named in a structured manner. If the node identifier is currently configured in the on-net device, the on-net device does not need to change the node identifier.

In a possible design, if the first control plane network element determines that the first SGW-U is detached from the first PGW-U, the first control plane network element initiates re-establishment of a PDN connection to the terminal device.

Optionally, if the first control plane network element is an SGW-C, the SGW-C may initiate re-establishment of the PDN connection to the terminal device when the S1 connection to the terminal device is released, based on when the first control plane network element determines that the first SGW-U is disassociated from the first PGW-U. Further, optionally, the SGW-C may start a timer when the S1 connection to the terminal device is released, and initiate re-establishment of the PDN connection to the terminal device after the timer has elapsed. Note that the SGW-C may initiate re-establishment of some or all of the PDN connection to the terminal device. Since the timer is started when the S1 connection to the terminal device is released, impact on ongoing data and voice services can be avoided.

Optionally, if the first control plane network element is a PGW-C, the PGW-C may initiate re-establishment of a PDN connection to the terminal device when the terminal device has no traffic within a specified time, based on which the first control plane network element initiates re-establishment of a PDN connection to the terminal device when the first control plane network element determines that the first SGW-U is disassociated from the first PGW-U. In this way, impacts to ongoing data and voice services can be avoided.

In a possible design, when initiating re-establishment of a PDN connection to the terminal device, the first control plane network element may send a delete bearer request to the MME, where the delete bearer request carries information about the deletion cause, and the information about the deletion cause indicates that re-activation is requested. The terminal device may be reactivated by carrying the information about the deletion cause. In the activation process, the first control plane network element selects a combined SGW-U/PGW-U for the terminal device, so that the user plane network elements may be combined and the path for forwarding data or voice traffic is better.

When the first control plane network element is an SMF or an I-SMF, the following possible designs may be provided:

According to the first aspect, the method may be implemented by using the following steps: a first control plane network element obtains a node identifier of a first PSA-UPF and a node identifier of a first I-UPF. The first control plane network element determines whether a user plane network element is disjoint based on the node identifier of the first I-UPF and the node identifier of the first PSA-UPF, the user plane network element including an I-UPF and a PSA-UPF, denoted as the first I-UPF and the first PSA-UPF. That is, the first control plane network element determines whether the first I-UPF is disjoint from the first PSA-UPF based on the node identifier of the I-UPF and the node identifier of the PSA-UPF. The first PSA-UPF is a user plane anchor for the terminal device.

In a possible design, the first control plane network element is an I-SMF. The first control plane network element may obtain the node identifier of the first PSA-UPF in the following manner: The I-SMF obtains the node identifier of the first PSA-UPF from the SMF.

When the I-SMF is inserted, the I-SMF may obtain the node identifier of the first PSA-UPF by exchanging messages with the SMF. Optionally, the SMF may send a PDU Session Create Response (Nsmf_PDUSession_Create Response) message to the I-SMF, where the PDU Session Create Response message carries the node identifier of the first PSA-UPF. The I-SMF receives the PDU Session Create Response message from the SMF, where the I-SMF obtains the node identifier of the first PSA-UPF from the PDU Session Create Response message. In this way, the node identifier can be carried in existing signaling to determine separation between user plane network elements.

In a possible design, the first control plane network element is an SMF. The first control plane network element may obtain the node identifier of the first I-UPF in the following manner:

When the I-SMF is inserted, the SMF may obtain the node identifier of the first I-UPF by exchanging messages with the I-SMF. Optionally, the I-SMF may send a PDU Session Create Request (Nsmf_PDUSession_Create Request) message to the SMF, and the PDU Session Create Request message may carry the node identifier of the first I-UPF. The SMF receives the PDU Session Create Request message from the I-SMF and obtains the node identifier of the first I-UPF from the PDU Session Create Request message. In this way, the node identifier can be carried in existing signaling to determine separation between user plane network elements.

In the following design of a determination method for determining whether the first I-UPF is separated from the first PSA-UPF, the node identifier of the first I-UPF and the node identifier of the first PSA-UPF may be represented by a first node identifier and a second node identifier, respectively.

In a possible design, the first control plane network element's determining whether the first I-UPF is disassociated from the first PSA-UPF based on the first node identifier and the second node identifier may include the following method: if the first node identifier is the same as the second node identifier, determining that the first I-UPF is not disassociated from the first PSA-UPF, or if the first node identifier is different from the second node identifier, determining that the first I-UPF is disassociated from the first PSA-UPF. This determination method is rigorous and accurate. Using the determination method to determine disassociation between user plane network elements may help improve the determination accuracy.

In a possible design, the first control plane network element determining whether the first I-UPF is separated from the first PSA-UPF based on the first node identifier and the second node identifier may further include the following method: determining that the first I-UPF is not separated from the first PSA-UPF if the first information in the first node identifier is the same as the second information in the second node identifier, or determining that the first I-UPF is separated from the first PSA-UPF if the first information in the first node identifier is different from the second information in the second node identifier, the first information indicating the area in which the first I-UPF is located, and the second information indicating the area in which the first PSA-UPF is located. When the two user plane network elements are not in the same node but in the same area, the path transmission redundancy is not so large and the requirement for PDU session re-establishment is not so high. In this determination method, whether the user plane network elements are separated can be flexibly determined. Only when an area spans between the user plane network elements, the user plane network elements are determined to be separated, and an operation, for example, PDU session re-establishment, is further performed after separation. This avoids signaling consumption caused by unnecessary PDU session re-establishment.

In a possible design, the first control plane network element determining whether the first I-UPF is separated from the first PSA-UPF based on the first node identifier and the second node identifier may further include the following method: if the first node identifier and the second node identifier are in the same group, determine that the first I-UPF is not separated from the first PSA-UPF, or if the first node identifier and the second node identifier are not in the same group, determine that the first I-UPF is separated from the first PSA-UPF, and the I-UPF and PSA-UPF in the group are located in the same area. When two user plane network elements are not in the same node but in the same area, the path transmission redundancy is not so large and the requirement for PDU session re-establishment is not so high. In this determination method, whether the user plane network element is separated can be flexibly determined. Only when the area spans between the user plane network elements, it is determined that the user plane network element is separated, and an operation, for example, PDU session re-establishment, is further performed after separation. This avoids signaling consumption caused by unnecessary PDU session re-establishment.

In a possible design, when the first control plane network element determines that the first I-UPF has separated from the first PSA-UPF, the first control plane network element initiates re-establishment of a PDU session to the terminal device.

Based on when the first control plane network element determines that the first I-UPF is dissociated from the first PSA-UPF, the first control plane network element initiates a re-establishment of a PDU session to the terminal device. Optionally, when the first control plane network element is an I-SMF, the I-SMF may initiate a re-establishment of a PDU session to the terminal device when the N1/N2 connection to the terminal device is released. Furthermore, optionally, the I-SMF may start a timer when the N1/N2 connection to the terminal device is released, and initiate a re-establishment of a PDU session of the terminal device after the timer has elapsed. It should be noted that the I-SMF may initiate a re-establishment of some or all of the PDU sessions to the terminal device. Since the timer is started when the N1/N2 connection to the terminal device is released, any impact on ongoing data and voice services can be avoided.

Optionally, if the first control plane network element is an SMF, the SMF may initiate re-establishment of a PDU session for the terminal device when the PDU session/terminal device has no traffic within a specified time, based on which the first control plane network element initiates re-establishment of the PDU session to the terminal device when the first control plane network element determines that the first I-UPF has dissociated from the first PSA-UPF. In this way, impacts on ongoing data and voice services can be avoided.

In a possible design, when initiating re-establishment of a PDU session of a terminal device, the first control plane network element may send a delete bearer request to the AMF, where the delete bearer request carries information about the deletion cause, and the information about the deletion cause indicates that reactivation is requested. The terminal device may be reactivated by carrying the information about the deletion cause. In the activation process, the first control plane network element selects a nearby PSA-UPF for the terminal device to avoid I-UPF insertion, thereby providing a better path for forwarding data or voice traffic.

According to a second aspect, there is provided a method for determining separation between user plane network elements. The method may be performed by a serving gateway for the control plane SGW-C or may be performed by a component of the serving gateway for the control plane SGW-C. For example, the method is performed by the serving gateway for the control plane SGW-C. The method may be implemented by using the following steps: the SGW-C obtains an address of a first PGW-C. The SGW-C determines whether the serving gateway for user plane SGW-U is disjointed from the first PGW-U based on the address of the first PGW-C and the preset address, or determines whether the PDN connection of the terminal device should be re-established based on the address of the first PGW-C and the preset address, the preset address including the address of one or more PGW-C located in the same area as the SGW-C, the first PGW-U is a user plane anchor for the terminal device to access the PDN, and the first PGW-C is a control plane anchor for the terminal device to access the PDN. The SGW-C determines whether the user plane network element is disjointed based on the address of the control plane gateway, and determines that the user plane network element is disjointed when it determines that the control plane gateway is disjointed (i.e., the address of the first PGW-C is not in the preset address) by presetting the control plane gateway group based on the area. The preset address is the address of the PGW-C in the same area as the SGW-C. In this way, the area can be divided based on the service requirements, and the preset address is set so that the separation between the user plane network elements can be more flexibly determined to meet the service requirements. Furthermore, since the gateway nodes do not need to be named in a normative and structured manner and the decision granularity is large, the decision result of the separation between the user planes can be reduced, and the actions taken after determining that the user planes are separated, such as PDN re-establishment, can be further reduced to reduce the signaling overhead.

In a possible design, the control plane serving gateway SGW-C and the first control plane data network PDN gateway PGW-C are located in different control plane gateway nodes. In general, when the SGW-C and the first PGW-C are located in different control plane gateway nodes, i.e., when the control plane gateways are separated, the user plane network elements are considered to be separated by default. In the solution of the second aspect, when the SGW-C and the first PGW-C are located in different control plane gateway nodes, whether the user plane network elements are separated needs to be further determined based on the address and the preset address of the first PGW-C. Based on the service requirements, the operator considers the SGW-U and the PGW-U to be separated only when a wide area range needs to be crossed between the SGW-U and the PGW-U. The solution of the second aspect is applicable to such service requirements of the operator.

In a possible design, the SGW-C may determine whether the serving gateway for user plane SGW-U is detached from the first PGW-U based on the address of the first PGW-C and the preset address in the following manner: if the preset address includes the address of the first PGW-C, the SGW-C determines that the SGW-U is not detached from the first PGW-U, or if the preset address does not include the address of the first PGW-C, the SGW-C determines that the SGW-U is detached from the first PGW-U.

In a possible design, when the SGW-C determines that the SGW-U has detached from the first PGW-U, the SGW-C initiates re-establishment of the PDN connection to the terminal device.

Optionally, the SGW-C initiates re-establishment of a PDN connection to the terminal device when the S1 connection to the terminal device is released, based on when the SGW-C determines that the SGW-U is detached from the first PGW-U. In this way, impacts on ongoing data and voice services can be avoided. Furthermore, optionally, the SGW-C may start a timer when the S1 connection to the terminal device is released, and initiate re-establishment of a PDN connection to the terminal device after the timer has elapsed. Since the timer is started when the S1 connection to the terminal device is released, impacts on ongoing data and voice services can be avoided.

In a possible design, when initiating re-establishment of a PDN connection to a terminal device, the SGW-C may send a delete bearer request to the MME, where the delete bearer request carries information about the deletion cause, and the information about the deletion cause indicates that reactivation is requested. The terminal device may be reactivated by carrying the information about the deletion cause. In the activation process, the SGW-C selects a combined SGW-U/PGW-U for the terminal device, so that the user plane network elements may be combined and the path for forwarding data or voice traffic is better.

According to a third aspect, there is provided a method for determining disjoint between user plane network elements. The method may be performed by a first control plane network element, or may be performed by a component of the first control plane network element, where the first control plane network element may be a PGW-C. For example, the method may be performed by the PGW-C. The method may be implemented by using the following steps: the PGW-C obtains an address of a first SGW-C. The PGW-C determines whether a PGW-U is disjoint from the first SGW-U based on the address of the first SGW-C and a preset address, where the preset address includes addresses of one or more SGW-C located in the same area as the PGW-C, where the PGW-U is a user plane anchor for terminal devices to access the PDN, and the PGW-C is a control plane anchor for terminal devices to access the PDN. The PGW-C determines whether the user plane network element is separated based on the address of the control plane gateway, and determines that the user plane network element is separated when it determines that the control plane gateway is separated (i.e., the address of the first SGW-C is not in the preset address) by presetting the control plane gateway group based on the area. The preset address is the address of the SGW-C in the same area as the PGW-C. In this way, the area can be divided based on the service requirements, and the preset address is set so that the separation between the user plane network elements is more flexibly determined to meet the service requirements. Furthermore, since the gateway nodes do not need to be named in a normative and structured manner and the granularity of the decision is large, the decision result of the separation between the user planes can be reduced, and the actions taken after the user plane is determined to be separated, such as PDN re-establishment, can be further reduced to reduce the signaling overhead.

In a possible design, the PGW-C and the first SGW-C are located in different control plane gateway nodes. In general, when the PGW -C and the first SGW -C are located in different control plane gateway nodes, i.e., when the control plane gateways are separated, the user plane network elements are considered to be separated by default. In the solution of the third aspect, when the PGW -C and the first SGW -C are located in different control plane gateway nodes, whether the user plane network elements are separated needs to be further determined based on the address of the first SGW -C and the preset address. Based on the service requirements, the operator considers the SGW-U and the PGW-U to be separated only when a wide area range needs to be crossed between the SGW-U and the PGW-U. The solution of the third aspect is applicable to such service requirements of the operator.

In a possible design, the PGW-C may determine whether the PGW-U is detached from the first user plane serving gateway SGW-U based on the address of the first SGW-C and the preset address in the following manner: if the preset address includes the address of the first SGW-C, the PGW-C determines that the PGW-U is not detached from the first SGW-U, or if the preset address does not include the address of the first SGW-C, the PGW-C determines that the PGW-U is detached from the first SGW-U.

In a possible design, when the PGW-C determines that the PGW-U has detached from the first SGW-U, the PGW-C initiates re-establishment of the PDN connection to the terminal device.

Optionally, based on when the PGW-C initiates re-establishment of a PDN connection to the terminal device when the terminal device has no traffic within a specified time, if the PGW-C determines that the PGW-U is detached from the first SGW-U, the PGW-C initiates re-establishment of a PDN connection to the terminal device. In this way, impact on ongoing data and voice services can be avoided.

In a possible design, when initiating re-establishment of a PDN connection to a terminal device, the PGW-C may send a delete bearer request to the MME, where the delete bearer request carries information about the deletion cause, and the information about the deletion cause indicates that reactivation is requested. The terminal device may be reactivated by carrying the information about the deletion cause. In the activation process, the PGW-C selects a combined SGW-U/PGW-U for the terminal device, so that the user plane network elements may be combined and the path for forwarding data or voice traffic is better.

According to a fourth aspect, a method for determining disassociation between user plane network elements is provided. The method may be performed by a first control plane network element or may be performed by a component of the first control plane network element. The first control plane network element may be an I-SMF. For example, the method is performed by the I-SMF. The method may be implemented by using the following steps: the I-SMF obtains an address of the first SMF, and the I-SMF determines whether the I-UPF has disassociated from the first PSA-UPF or whether to initiate re-establishment of a PDU session of the terminal device based on the address of the first SMF and the preset address.

The preset address includes the addresses of one or more SMFs located in the same area as the I-SMF, the first PSA-UPF is a user plane anchor for the terminal device, and the first SMF is a control plane anchor for the terminal device.

In a possible design, if the I-SMF determines, based on the address of the first SMF and the preset address, that the I-UPF has disassociated from the first PSA-UPF, the I-SMF may trigger re-establishment of a PDU session of the terminal device.

In a possible design, the I-SMF may determine whether the I-UPF has detached from the first PSA-UPF based on the address of the first SMF and the preset address in the following manner: if the preset address includes the address of the first SMF, the I-SMF determines that the I-UPF has not detached from the first PSA-UPF, or if the preset address does not include the address of the first SMF, the I-SMF determines that the I-UPF has detached from the first PSA-UPF.

Optionally, the I-SMF may start a re-establishment of the PDU session of the terminal device when the N1/N2 connection to the terminal device is released, and may start a re-establishment of the PDU session of the terminal device after the timer has elapsed. Since the timer is started when the N1/N2 connection to the terminal device is released, an impact on ongoing data and voice services can be avoided. Optionally, the I-SMF may also start a timer when the N1/N2 connection to the terminal device is released, and start a re-establishment of the PDU session of the terminal device after the timer has elapsed. Since the timer is started when the N1/N2 connection to the terminal device is released, an impact on ongoing data and voice services can be avoided.

According to a fifth aspect, a method for determining disassociation between user plane network elements is provided. The method may be performed by a first control plane network element or may be performed by a component of the first control plane network element. The first control plane network element may be an SMF. For example, the method may be performed by the SMF. The method may be implemented by using the following steps: the SMF obtains an address of a first I-SMF, and the SMF determines whether the PSA-UPF has disassociated from the first I-UPF or whether to initiate a re-establishment of a PDU session of the terminal device based on the address of the first I-SMF and a preset address, the preset address including an address of one or more I-SMFs located in the same area as the SMF, the PSA-UPF may be a user plane anchor of the terminal device, and the SMF may be a control plane anchor of the terminal device.

In a possible design, the SMF may determine whether the PSA-UPF has detached from the first I-UPF based on the address of the first I-SMF and the preset address in the following manner: if the preset address includes the address of the first I-SMF, the SMF determines that the PSA-UPF has not detached from the first I-UPF, or if the preset address does not include the address of the first I-SMF, the SMF determines that the PSA-UPF has detached from the first I-UPF.

In a possible design, if the SMF determines that the PSA-UPF has separated from the first I-UPF, the SMF initiates re-establishment of a PDU session for the terminal device.

Optionally, the SMF initiates re-establishment of a PDU session of the terminal device when the terminal device has no traffic within a specified time, based on which the SMF initiates re-establishment of the PDU session of the terminal device when the SMF determines that the PSA-UPF has detached from the first I-UPF. In this way, impact on ongoing data and voice services can be avoided.

According to a sixth aspect, a communication device is provided. The device may be a first control plane network element or a component (e.g., a chip, a chip system, or a circuit) of the first control plane network element. The first control plane network element includes a serving gateway for control plane SGW-C (which may be denoted as first SGW-C), a data network PDN gateway for control plane PGW-C (which may be denoted as first PGW-C), a session management function network element SMF, or an intermediate session management function network element I-SMF. The device comprises a function for performing a method according to the first aspect or any one of the possible designs of the first aspect. The function may be implemented by hardware or may be implemented by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the above functions. In the design, the device may include an obtaining unit and a determining unit. For example, the obtaining unit is configured to obtain a first node identifier of the first user plane network element and a second node identifier of the second user plane network element. The first user plane network element is a user plane anchor. The determination unit is configured to determine whether the first user plane network element is isolated from the second user plane network element based on the first node identifier and the second node identifier.

In a possible design, when acquiring the first node identifier of the first user plane network element, the acquisition unit is configured to acquire the first node identifier of the first user plane network element from the second control plane network element, and the device is an SGW-C and the first user plane network element is a first user plane data network PDN gateway PGW-U, or the device is a PGW-C and the first user plane network element is a first user plane serving gateway SGW-U, or the device is an SMF and the first user plane network element is an intermediate user plane management function I-UPF, or the device is an I-SMF and the first user plane network element is a protocol data unit session anchor user plane management function PSA-UPF.

In a possible design, when determining whether the first user plane network element is detached from the second user plane network element based on the first node identifier and the second node identifier, the determination unit is configured to determine that the first user plane network element is not detached from the second user plane network element if the first node identifier is the same as the second node identifier, or to determine that the first user plane network element is detached from the second user plane network element if the first node identifier is different from the second node identifier.

In a possible design, when determining whether the first user plane network element is isolated from the second user plane network element based on the first node identifier and the second node identifier, the determination unit is configured to determine that the first user plane network element is not isolated from the second user plane network element if the first information in the first node identifier is the same as the second information in the second node identifier, or to determine that the first user plane network element is isolated from the second user plane network element if the first information in the first node identifier is different from the second information in the second node identifier, where the first information indicates an area in which the first user plane network element is located and the second information indicates an area in which the second user plane network element is located.

In a possible design, when determining whether the first user plane network element is detached from the second user plane network element based on the first node identifier and the second node identifier, the determination unit is configured to determine that the first user plane network element is not detached from the second user plane network element if the first node identifier and the second node identifier are in the same group, or to determine that the first user plane network element is detached from the second user plane network element if the first node identifier and the second node identifier are not in the same group.

In a possible design, the apparatus further includes a re-establishment unit configured to initiate re-establishment of a data transmission path of the terminal device when the determination unit determines that the first user plane network element is separated from the second user plane network element.

In a possible design, the device is an SGW-C. When initiating re-establishment of a data transmission path for a terminal device, the re-establishment unit is configured to initiate re-establishment of a packet data network PDN connection to the terminal device when the S1 connection to the terminal device is released.

In a possible design, the device is an I-SMF. When initiating re-establishment of a data transmission path of a terminal device, the re-establishment unit is configured to initiate re-establishment of a protocol data unit PDU session of the terminal device when the N1/N2 connection to the terminal device is released.

In a possible design, the device is a PGW-C or an SMF. When initiating re-establishment of a data transmission path of a terminal device, the re-establishment unit is configured to initiate re-establishment of a data transmission path of the terminal device when the terminal device has no traffic within a specified time.

For the advantageous effects of the sixth aspect and possible designs, please refer to the description of the first aspect and possible designs. The details will not be described again here.

According to a seventh aspect, a communication apparatus is provided. The apparatus may be a serving gateway for control plane SGW-C or may be a component of a serving gateway for control plane SGW-C. The serving gateway for control plane SGW-C and the first data network PDN gateway for control plane PGW-C are located at different control plane gateway nodes. The apparatus comprises functionality for implementing a method according to the second aspect or any one of the possible designs of the second aspect. The functionality may be implemented by hardware or by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the above functionality. In a design, the apparatus may include an obtaining unit and a determining unit.

For example, the acquisition unit is configured to acquire an address of the first PGW-C, and the determination unit is configured to determine whether the serving gateway for user plane SGW-U is disassociated from the first PGW-U based on the address of the first PGW-C and the preset address, or the determination unit is configured to determine whether the PDN connection of the terminal device should be re-established based on the address of the first PGW-C and the preset address, the preset address includes addresses of one or more PGW-C located in the same area as the SGW-C, the first PGW-U is a user plane anchor for the terminal device to access the PDN, and the first PGW-C is a control plane anchor for the terminal device to access the PDN.

In a possible design, when the determination unit determines whether the serving gateway for user plane SGW-U is detached from the first PGW-U based on the address of the first PGW-C and the preset address, the determination unit is specifically configured to determine that, for the SGW-C, the SGW-U is not detached from the first PGW-U if the preset address includes the address of the first PGW-C, or to determine that, for the SGW-C, the SGW-U is detached from the first PGW-U if the preset address does not include the address of the first PGW-C.

In a possible design, the apparatus further includes a re-establishment unit configured to initiate re-establishment of a PDN connection to the terminal device when the determination unit determines that the SGW-U is detached from the first PGW-U.

Optionally, the re-establishment unit is further configured to initiate re-establishment of a PDN connection to the terminal device when the S1 connection to the terminal device is released.

Optionally, the re-establishment unit may be further configured to start a timer when the S1 connection to the terminal device is released and to initiate re-establishment of the PDN connection to the terminal device after the timer has elapsed.

For the advantageous effects of the seventh aspect and possible designs, please refer to the second aspect and possible design description. The details will not be described again here.

According to an eighth aspect, there is provided a communications apparatus. The apparatus may be a PGW-C or may be a component of a PGW-C. A serving gateway for the control plane SGW-C and a first data network PDN gateway for the control plane PGW-C are located in different control plane gateway nodes. The apparatus comprises functionality for performing a method according to the third aspect or any one of the possible designs of the third aspect. The functionality may be implemented by hardware or by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the above functionality. In a design, the apparatus may include an obtaining unit and a determining unit. For example, the acquisition unit is configured to acquire an address of a first SGW-C, and the determination unit is configured to determine whether the PGW-U is disjoint from a first user plane serving gateway SGW-U based on the address of the first SGW-C and a preset address, the preset address includes addresses of one or more SGW-Cs located in the same area as the PGW-C, the PGW-U is a user plane anchor for terminal devices to access the PDN, and the PGW-C is a control plane anchor for terminal devices to access the PDN.

In a possible design, when determining whether the PGW-U is detached from the first user plane serving gateway SGW-U based on the address of the first SGW-C and the preset address, the determination unit is specifically configured to determine that, for the PGW-C, the PGW-U is not detached from the first SGW-U if the preset address includes the address of the first SGW-C, or to determine that, for the PGW-C, the PGW-U is detached from the first SGW-U if the preset address does not include the address of the first SGW-C.

In a possible design, the apparatus further includes a re-establishment unit configured to initiate re-establishment of a PDN connection to the terminal device when the determination unit determines that the PGW-U is detached from the first SGW-U.

Optionally, the re-establishment unit may be further configured to initiate a re-establishment of the PDN connection to the terminal device when the terminal device has no traffic within a specified time.

For advantageous effects of the eighth aspect and possible designs, please refer to the third aspect and possible design description. Details will not be described again here.

According to a ninth aspect, a communication device is provided. The device may be an I-SMF or a component of an I-SMF. The device comprises a function for implementing a method according to the fourth aspect or any one of the possible designs of the fourth aspect. The function may be implemented by hardware or by executing corresponding software by the hardware. The hardware or software includes one or more modules corresponding to the above functions. In a design, the device may include an acquisition unit and a determination unit. For example, the acquisition unit is configured to acquire an address of a first SMF, and the determination unit is configured to determine whether the I-UPF has dissociated from the first PSA-UPF or whether to initiate a re-establishment of a PDU session of the terminal device based on the address of the first SMF and the preset address. The preset address includes addresses of one or more SMFs located in the same area as the I-SMF, the first PSA-UPF is a user plane anchor of the terminal device, and the first SMF is a control plane anchor of the terminal device.

In a possible design, the device further includes a re-establishment unit. The re-establishment unit is configured to trigger re-establishment of a PDU session of the terminal device when the determination unit determines, based on the address of the first SMF and the preset address, that the I-UPF is disassociated from the first PSA-UPF.

In a possible design, when determining whether the I-UPF has detached from the first PSA-UPF based on the address of the first SMF and the preset address, the determination unit is specifically configured to determine that, for the I-SMF, the I-UPF has not detached from the first PSA-UPF if the preset address includes the address of the first SMF, or to determine that, for the I-SMF, the I-UPF has detached from the first PSA-UPF if the preset address does not include the address of the first SMF.

Optionally, the re-establishment unit may be configured to initiate a re-establishment of the PDU session of the terminal device when the N1/N2 connection to the terminal device is released, based on the determination unit determining that the I-UPF is dissociated from the first PSA-UPF based on the address of the first SMF and the preset address, based on which the re-establishment unit triggers a re-establishment of the PDU session of the terminal device. In this way, impacts on ongoing data and voice services can be avoided. Furthermore, optionally, the re-establishment unit may be further configured to start a timer when the N1/N2 connection to the terminal device is released, and to start a re-establishment of the PDU session of the terminal device after the timer has elapsed. Since the timer is started when the N1/N2 connection to the terminal device is released, impacts on ongoing data and voice services can be avoided.

According to a tenth aspect, a communication device is provided. The device may be an SMF or a component of an SMF. The device comprises a function for implementing a method according to the fifth aspect or any one of the possible designs of the fifth aspect. The function may be implemented by hardware or by executing corresponding software by the hardware. The hardware or software includes one or more modules corresponding to the above functions. In a design, the device may include an acquisition unit and a determination unit. For example, the acquisition unit is configured to acquire an address of a first I-SMF, and the determination unit is configured to determine whether the PSA-UPF has dissociated from the first I-UPF or whether to initiate a re-establishment of a PDU session of the terminal device based on the address of the first I-SMF and a preset address, the preset address including addresses of one or more I-SMFs located in the same area as the SMF, the PSA-UPF may be a user plane anchor of the terminal device, and the SMF may be a control plane anchor of the terminal device.

In a possible design, when determining whether the PSA-UPF is detached from the first I-UPF based on the address of the first I-SMF and the preset address, the determination unit is specifically configured to determine that the PSA-UPF is not detached from the first I-UPF if the preset address includes the address of the first I-SMF, or to determine that the PSA-UPF is detached from the first I-UPF for the SMF if the preset address does not include the address of the first I-SMF.

In a possible design, the apparatus further includes a re-establishment unit configured to initiate re-establishment of a PDU session of the terminal device when the determination unit determines that the PSA-UPF is separated from the first I-UPF.

Optionally, the re-establishment unit may be further configured to initiate re-establishment of the PDU session of the terminal device when the terminal device has no traffic within a specified time, based on which the re-establishment unit initiates re-establishment of the PDU session of the terminal device when the determination unit determines that the PSA-UPF is detached from the first I-UPF. In this way, impact on ongoing data and voice services can be avoided.

According to an eleventh aspect, an embodiment of the present application provides a communication device. The communication device includes an interface circuit and a processor, the processor and the interface circuit being coupled to each other. The processor is configured to implement the method described in the above aspects and possible designs of the aspects by using logic circuits or executing code instructions. The interface circuit is configured to receive a signal from a communication device other than the communication device and send the signal to the processor or send a signal from the processor to a communication device other than the communication device. The interface circuit may be a transceiver or an input/output interface.

Optionally, the communication device may further include a memory configured to store instructions to be executed by the processor, or to store input data required for execution of the instructions by the processor, or to store data generated after the processor executes the instructions. The memory may be a physically separate unit or may be coupled to the processor, or the processor may include the memory.

According to a twelfth aspect, an embodiment of the present application provides a computer-readable storage medium. The computer-readable storage medium stores a computer program or readable instructions, and when the computer program or readable instructions are executed by a communication device, a method of the above aspect or possible design of the aspect is performed.

According to a thirteenth aspect, an embodiment of the present application provides a chip system. The chip system includes a processor and may further include a memory. The memory is configured to store a program, instructions, or code. The processor is configured to execute the program, instructions, or code stored in the memory to implement the method of the above aspect or the possible design of the jobber aspect. The chip system may include a chip, or may include a chip and other discrete components.

According to a fourteenth aspect, there is provided a computer program product including instructions. When the computer program product is executed by a communication device, a method of the above aspect or a possible design of the above aspect is performed.

According to a fifteenth aspect, a communication system is provided. The system includes a first control plane network element, a first user plane network element, and a second user plane network element. The first control plane network element is configured to perform a method of the above aspect or a possible design of the above aspect.

In a possible design, the system includes a second control plane network element, which may be configured to perform the operations performed by the second control plane network element in the above aspect or a possible design of the above aspect.

FIG. 1 is a schematic diagram of a CUPS EPC network architecture according to an embodiment of the present application. FIG. 1 is a schematic diagram of the architecture of a communication system according to an embodiment of the present application; 1 is a schematic flowchart 1 of a method for determining isolation between user plane network elements according to an embodiment of the present application; 2 is a schematic flowchart 2 of a method for determining isolation between user plane network elements according to an embodiment of the present application; 3 is a schematic flowchart 3 of a method for determining isolation between user plane network elements according to an embodiment of the present application; FIG. 1 is a schematic diagram of determining separation between user plane network elements according to an embodiment of the present application; FIG. 2 is a schematic diagram of determining separation between user plane network elements according to an embodiment of the present application; 1 is a schematic flowchart 1 of PDN re-establishment according to an embodiment of the present application; 2 is a schematic flowchart 2 of PDN re-establishment according to an embodiment of the present application; 3 is a schematic flowchart 3 of PDN re-establishment according to an embodiment of the present application; 4 is a schematic flowchart 4 of a method for determining isolation between user plane network elements according to an embodiment of the present application; 3 is a schematic diagram of determining separation between user plane network elements according to an embodiment of the present application; 5 is a schematic flowchart 5 of a method for determining isolation between user plane network elements according to an embodiment of the present application; 1 is a schematic flowchart 1 of a method for determining separation between user plane network elements in a 5G communication system according to an embodiment of the present application; 2 is a schematic flowchart 2 of a method for determining separation between user plane network elements in a 5G communication system according to an embodiment of the present application; FIG. 1 is a schematic diagram of an operational procedure performed after a user plane network element is separated according to an embodiment of the present application; FIG. 2 is a schematic diagram of an operational procedure performed after a user plane network element is separated according to an embodiment of the present application; 3 is a schematic diagram of an operational procedure performed after a user plane network element is separated according to an embodiment of the present application; 6 is a schematic flowchart 6 of a method for determining isolation between user plane network elements according to an embodiment of the present application; 7 is a schematic flowchart 7 of a method for determining isolation between user plane network elements according to an embodiment of the present application; 1 is a schematic diagram of a structure of a communication device according to an embodiment of the present application; 1 is a schematic diagram of a structure of a communication device according to an embodiment of the present application;

The embodiments of the present application provide a method and a communication device for determining separation between user plane network elements, to determine whether the user plane network elements are separated in a control and user plane separation scenario. The method and the device are conceived based on the same or similar technical concept. The method and the device have similar principles for solving problems. Therefore, the implementations of the device and the method should be mutually referenced. The repeated details will not be described.

In describing the embodiments of this application, the character "/" generally indicates a "logical OR" relationship between related objects. Words such as "first," "second," and "third" are used for distinction and explanation only and cannot be understood as an indication or implication of relative importance or of order.

The method for determining isolation between user plane network elements provided in the embodiments of the present application may be applied to a 4th generation (4G) communication system, such as long term evolution (LTE), or to a 5G communication system, such as 5G new radio (NR), or to various future evolved communication systems, such as a 6th generation (6G) communication system or an eia-space-sea integrated communication system.

The following describes in detail the embodiments of the present application with reference to the accompanying drawings. Figures 1a and 1b show examples of a 4G communication system architecture and a 5G communication system architecture, respectively.

First, the architecture of a 4G communication system is used as an example for explanation.

3GPP protocols describe an evolved packet core (EPC) network architecture, based on which data flow transmission between a terminal device and a server can be performed. In general, the EPC network architecture includes a serving gateway (SGW) and a packet data network (PDN) gateway (PGW). 3GPP protocols describe a control and user plane separation (CUPS) case in the EPC network architecture. Figure 1a shows a CUPS EPC network architecture. The method for determining separation between user plane gateways provided in the embodiments of the present application can be applied to the network architecture shown in Figure 1a. CUPS means that gateways are divided into control plane gateways and user plane gateways based on functions. As shown in Figure 1a, the SGW is divided into a serving gateway for user plane (SGW-U) and a serving gateway for control plane (SGW-C). The SGW-U may implement the user plane function of an SGW in a non-CUPS EPC network architecture, and the SGW-C may implement the control plane function of an SGW in a non-CUPS EPC network architecture. Similarly, the PGW is divided into a PDN gateway for user plane (PGW-U) and a PDN gateway for control plane (PGW-C). The PGW-U may implement the user plane functions of a PGW in a non-CUPS EPC network architecture, and the PGW-C may implement the control plane functions of a PGW in a non-CUPS EPC network architecture.

The EPC network architecture further includes a terminal device. The terminal device may also be called user equipment (UE), mobile station (MS), mobile terminal (MT), etc., and may be a device that provides voice or data connectivity to a user, or may be an Internet of Things device. For example, the terminal device may include a handheld device, a vehicle-mounted device, etc., that has wireless communication capabilities. The terminal device may be a mobile phone, a tablet computer, a notebook computer, a palmtop computer, a mobile internet device (MID), a wearable device (e.g., a smart watch, a smart band, or a pedometer), an in-vehicle device (e.g., an in-vehicle device for a car, a motorcycle, an electric car, an airplane, a ship, a train, or a high-speed rail), a virtual reality (VR) device, an augmented reality (AR) device, a wireless terminal in industrial control, a smart home device (e.g., for a refrigerator, a television, an air conditioner, or an electric meter), an intelligent robot, a workshop device, a wireless terminal in self driving, a wireless terminal in remote medical surgery, a smart grid (SGT), a smart home device (e.g., for a smart home device ... The terminal device may be a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, a flying device (e.g., an intelligent robot, a hot air balloon, an unmanned aerial vehicle, or an airplane), etc. Alternatively, the terminal device may be other devices equipped with terminal functions. For example, the terminal device may be a device that functions as a terminal in Internet of Vehicle communication.

Optionally, the EPC network architecture may further include a mobility management entity (MME) and a home subscriber server (HSS), where the MME is configured to manage the mobile context and session context of a user equipment (UE). In addition, the EPC network architecture may further include monitoring network elements related to the monitoring function, such as a charging gateway (CG), an online charging system (OCS), and a lawful interception gateway (LIG). The PGW-C can use these monitoring network elements to perform monitoring of terminal services, such as billing and lawful interception for terminal services.

In a CUPS session, the control plane network elements include SGW-C and PGW-C, and the user plane network elements include SGW-U and PGW-U. Typically, the control plane network elements (SGW-C and PGW-C) are centrally located in state capitals and regional centers, and the user plane network elements (SGW-U and PGW-U) are located in cities closer to users. This can shorten the service access path, improve the user's service experience, and save the transmission bandwidth on the bearer network.

How to determine whether user plane network elements are separated is a problem that needs to be solved. In a non-CUPS scenario, the MME may determine separation between the SGW and PGW based on the canonical-node-names of the SGW and PGW. Specifically, when the SGW changes during the movement of a terminal device, the MME selects a new SGW for the terminal. The MME obtains the hostname of the new SGW by querying based on the tracking area (TA) in which the terminal device is currently located. The MME extracts the canonical-node-name from the hostname of the new SGW and compares the canonical-node-name with the locally stored canonical-node-name of the PGW anchored by the terminal device. If the MME finds that the canonical node names of the SGW and PGW are different, or that some fields within the areas identified by the standardized node names are different, the MME considers the SGW to be detached from the PGW and triggers PDN re-establishment.

However, the way in which the MME determines the separation between user plane network elements in the non-CUPS scenario is not applicable to the CUPS scenario. In the CUPS scenario, the control plane network elements (SGW-C and PGW-C) and the user plane network elements (SGW-U and PGW-U) are located in different physical nodes. When selecting a gateway, the MME obtains the hostnames of the SGW-C and PGW-C respectively based on the TA and access point name (APN) by query, extracts the regular node name from the hostname, and finally obtains the interface internet protocol (IP) information of the SGW-C and PGW-C by query. The SGW-U and PGW-U are selected by the SGW-C and PGW-C respectively according to a specific rule. It can be seen that in the CUPS scenario, the canonical node names are used by the MME to select the control plane network elements (SGW-C and PGW-C) instead of the user plane network elements (SGW-U and PGW-U). Based on the canonical node names, the MME can only determine whether the SGW-C is detached from the PGW-C, but cannot determine whether the SGW-U is detached from the PGW-U.

When the same set of control plane network elements are connected to user plane network elements in multiple areas and the terminal device moves between these user plane network elements, the MME cannot accurately determine whether the SGW-U is detached from the PGW-U. For example, in the CUPS scenario, the network deployment principle in most areas is that the SGW-C and PGW-C are centrally deployed in large areas/state capitals, and correspondingly manage the area access across the state and all user plane network elements across the state, and the SGW-U and PGW-U are deployed in cities. In this scenario, when the user moves within the state, the control plane node where the SGW-C is located remains unchanged. The MME cannot determine whether the SGW-U is detached from the PGW-U by using the decision mechanism after the user moves.

The following describes the architecture of a 5G communication system based on the example of Figure 1b.

As shown in FIG. 1b, the architecture of the communication system may include an access network and a core network. The core network mainly includes the following important logical network elements: access and mobility management function network element, session management function network element, user plane function network element, policy control function network element, integrated data management function network element, etc. For example, FIG. 1b shows a possible example of the architecture of the communication system, and the network elements or devices in the architecture of the communication system are illustrated by using concrete examples. Specifically, the architecture of the communication system shown in FIG. 1b includes a terminal device (UE is used as an example), an access and mobility management function (AMF) network element, a session management function (SMF) network element, a user plane function (UPF) network element, a policy control function (PCF) network element, a unified data management function (UDM), an authentication server function (authentication server function) network element, and a network element. The network functions may include an access function (ASF) network element, a network exposure function (NEF) network element, an application function (AF) network element, a network slice selection function (NSSF) network element, a (radio) access network ((R)AN) device, and a network repository function (NRF) network element. The AMF network element may be connected to the access network element through an N2 interface, the access network device may be connected to the UPF through an N3 interface, the SMF may be connected to the UPF through an N4 interface, and the AMF network element may be connected to the UE through an N1 interface. The interface names are merely examples for explanation. This is not particularly limited in the embodiments of the present application. It should be understood that the embodiments of the present application are not limited to the communication system shown in FIG. 1b. The names of the network elements shown in FIG. 1b are merely examples for explanation here and are not intended to limit the network elements included in the architecture of the communication system to which the communication method of the present application is applied.

The following describes in more detail the functionality of some network elements or devices within the communication system of FIG. 1b.

For a description of the terminal device and the access network device, please refer to the description of FIG. 1a. The details will not be described again here.

The access and mobility management function network element is mainly responsible for functions such as signaling processing, e.g., access control, mobility management, attachment and detachment, and gateway selection. When the AMF network element provides a service to a session in a terminal device, the AMF network element provides control plane storage resources for the session to store a session identifier, an SMF network element identifier associated with the session identifier, and the like. For example, in 5G, the access and mobility management function network element may be an AMF network element, e.g., as shown in FIG. 1b. In future communications, e.g., in 6G, the access and mobility management function network element may still be an AMF network element or may have other names. This is not limited in this application. When the access and mobility management function network element is an AMF network element, the AMF may provide Namf services.

The session management function network element is mainly responsible for session management in a mobile network, for example, establishing, modifying, and releasing a session. For example, specific functions include assigning an IP address to a user, selecting a UPF that provides a message forwarding function, etc. For example, in 5G, the session management function network element may be an SMF network element, for example, as shown in FIG. 1b. In future communications, for example, in 6G, the session management function network element may still be an SMF network element or have other names. This is not limited in this application. When the session management function network element is an SMF network element, the SMF may provide Namf services.

The user plane function network element is responsible for forwarding and receiving user data at the terminal device. The UPF network element may receive user data from a data network and transmit the user data to the terminal device via an access network device. The UPF network element may further receive user data from the terminal device via the access network device and forward the user data to the data network. The transmission resources and scheduling functions used by the UPF network element to provide services to the terminal device are managed and controlled by the SMF network element. For example, in 5G, the user plane function network element may be a UPF network element, for example as shown in FIG. 1b. In future communications, for example in 6G, the user plane function network element may still be a UPF network element or may have another name. This is not limited in this application.

It should be noted that the architecture of the communication system shown in FIG. 1b is not limited to including only the network elements shown in the figure, but may further include other devices shown in FIG. 1b. The details will not be described one by one here in this application. The distribution format of the network elements is not limited in the embodiment of this application. The distribution format shown in FIG. 1a and FIG. 1b is only an example. This is not limited in this application.

Each network element in the core network may also be referred to as a functional entity or device, and may be a network element implemented on dedicated hardware, or a software instance running on dedicated hardware, or an instance with functionality virtualized on a suitable platform. For example, the virtualization platform may be a class and platform.

For ease of explanation, the network element shown in FIG. 1b is used hereinafter as an example for explanation, and the XX network element is directly referred to as XX. It should be understood that the names of all network elements in this application are used merely as examples, and may be referred to by other names in future communications, or the network elements in this application may be replaced by other entities or devices having the same functions in future communications. This is not limited in this application. A unified description is given here. Details will not be described again below.

Based on the communication system shown in FIG. 1b, the control plane network element may be an SMF, and the user plane anchor gateway may be a PDU session anchor UPF (PSA-UPF). When the terminal device goes out of the coverage area of the PSA-UPF, the SMF selects an intermediate UPF (I-UPF) based on the location of the terminal device, and inserts the intermediate UPF between the access network device and the PSA-UPF for relaying to implement end-to-end network communication. The SMF needs to determine whether the PSA-UPF is separated from the I-UPF. When the terminal device goes out of the SMF service range, the AMF network element selects to insert an intermediate SMF (I-) based on the location of the terminal device, and the I-SMF selects the I-UPF for relaying. The I-SMF or SMF must determine whether the PSA-UPF is separated from the I-UPF.

Based on this, an embodiment of the present application provides a method for determining separation between user plane network elements in a control and user plane separation scenario.

As shown in FIG. 2a, the specific procedure of the method for determining isolation between user plane network elements provided in the embodiment of the present application is as follows: The method may be performed by a first control plane network element, and the first control plane network element may be an SGW-C, a PGW-C, an SMF, or an I-SMF.

S201a: The first control plane network element obtains a first node identifier of the first user plane network element and a second node identifier of the second user plane network element.

The first user plane network element is a user plane anchor.

S202a: The first control plane network element determines whether the user plane network elements are disjoint based on the first node identifier and the second node identifier, i.e., determines whether the first user plane network element is disjoint from the second user plane network element.

In the present application, whether the user plane network element is separated may also be understood as determining whether to re-establish a data transmission path connection to the terminal device, or determining whether to optimize a traffic forwarding path (or data transmission path), or determining whether a traffic diversion (or data transmission diversion) exists. For example, the first control plane network element may determine whether the first user plane network element is separated from the second user plane network element based on the first node identifier and the second node identifier, and may further perform operations performed after the separation, such as re-establishing a data transmission path connection to the terminal device, upon determining that the user plane network element is separated. Alternatively, the first control plane network element may directly determine whether to re-establish a data transmission path connection to the terminal device based on the first node identifier and the second node identifier, and re-establish the data transmission path when the first control plane network element determines that the data transmission path connection to the terminal device is re-established. As another example, the first control plane network element may determine whether a traffic diversion exists based on the first node identifier and the second node identifier, and upon determining that a traffic diversion exists, perform an action, e.g., re-establishment of a data transmission path for the terminal device.

In the embodiment of FIG. 2a, the first control plane network element determines whether the user plane network elements are separated based on the node identifiers of the two user plane network elements, so that whether the user plane network elements are separated can be determined in a control and user plane separation scenario, and the efficiency and accuracy of determining separation between user plane network elements can be improved, so that measures can be taken in a timely manner when the user plane gateway is separated to avoid traffic diversion.

Optionally, in S201a, the first control plane network element obtains a first node identifier of the first user plane network element and a second node identifier of the second user plane network element. The first control plane network element may obtain the node identifier of one user plane network element locally and obtain the node identifier of the other user plane network element from the second control plane network element. Based on different types of the first control plane network element, the following provides separate descriptions by using examples. For example, the first control plane network element is an SGW-C, and the SGW-C may obtain the node identifier of the first PGW-U from the PGW-C. As another example, the first control plane network element is a PGW-C, and the PGW-C may obtain the node identifier of the first SGW-U from the SGW-C. As another example, the first control plane network element is an SMF, and when an I-SMF is not inserted, the node identifiers of the two user plane network elements may be obtained locally. As another example, the first control plane network element may be an SMF, and the SMF may obtain a node identifier of the first I-UPF from the I-SMF when the I-SMF is inserted. As another example, the first control plane network element may be an I-SMF, and the I-SMF may obtain a node identifier of the first PSA-UPF from the SMF.

Based on the embodiment of FIG. 2a, the following separately describes a corresponding method for determining isolation between user plane network elements when the first control plane network element is a different network element.

As shown in FIG. 2b, when the first control plane network element is an SGW-C or a PGW-C, the procedure of the method for determining separation between user plane network elements is as follows:

S201b: The first control plane network element obtains the node identifier of the first PGW-U and the node identifier of the first SGW-U.

The first PGW-U is a user plane anchor through which the terminal device accesses the PDN. 3GPP specifies that the PGW-U cannot be changed during the movement of the terminal device, and the first PGW-U is a user plane anchor for the terminal device, and the first PGW-U cannot be changed during the movement process of the terminal device.

S202b: The first control plane network element determines whether the first SGW-U is detached from the first PGW-U based on the node identifier of the first PGW-U and the node identifier of the first SGW-U.

In the embodiment of FIG. 2b, the first control plane network element determines whether the first SGW-U is isolated from the first PGW-U based on the node identifier of the first PGW-U and the node identifier of the first SGW-U, so that whether the user plane network element is isolated can be determined in a CUPS scenario, and the efficiency and accuracy of determining isolation between user plane network elements can be improved, so that measures can be taken in a timely manner when the user plane network element is isolated to avoid traffic diversion.

As shown in FIG. 2c, when the first control plane network element is an I-SMF or an SMF, the procedure of the method for determining separation between user plane network elements is as follows:

S201c: The first control plane network element obtains the node identifier of the first PSA-UPF and the node identifier of the first I-UPF.

The first PSA-UPF is a user plane anchor through which the terminal device accesses the data network (DN). The first PSA-UPF is a user plane anchor for the terminal device.

S202c: The first control plane network element determines whether the first I-UPF is detached from the first PSA-UPF based on the node identifier of the first PSA-UPF and the node identifier of the first I-UPF.

In the embodiment of FIG. 2c, the first control plane network element determines whether the first I-UPF is separated from the first PSA-UPF based on the node identifier of the first PSA-UPF and the node identifier of the first I-UPF, so that whether the user plane network element is separated can be determined in a control and user plane separation scenario, and the efficiency and accuracy of the determination of separation between the user plane network elements can be improved, so that measures can be taken in a timely manner when the user plane network element is separated to avoid traffic diversion.

The following describes some possible implementations based on the embodiment of Figure 2b.

The first control plane network element may be an SGW-C or a PGW-C, and the SGW-C may be an SGW-C reselected by the MME for a terminal device when the terminal device moves. The first SGW-U is an SGW-U reselected by the SGW-C for a terminal device. The PGW-C is the control plane anchor through which the terminal device accesses the PDN. 3GPP protocols specify that the PGW-C cannot be changed during the movement of the terminal device.

According to the definition of the 3GPP TS 29.244 protocol, when the gateway is deployed in the CUPS, the control plane network elements and the user plane network elements are interconnected via the Sx interface and identified by node identifiers (Node IDs). That is, during the CUPS deployment, the SGW-C can obtain the node identifier of the SGW-U via the Sx interface, and the PGW-C can obtain the node identifier of the PGW-U via the Sx interface. When the terminal device moves between areas, the MME reselects the SGW-U based on the current location of the terminal device and records the node identifier of the SGW-U where the terminal device is located. The PGW-C and the PGW-U are anchored and unchanged during the movement of the terminal device. It can be seen that the SGW-C knows the second node identifier of the first SGW-U, and the PGW-C knows the first node identifier of the first PGW-U.

The following describes an optional implementation in which the first control plane network element obtains the first node identifier and the second node identifier at S201b.

When the first control plane network element is an SGW-C, the SGW-C knows the second node identifier of the first SGW-U (e.g., the SGW-C obtains the second node identifier of the first SGW-U from local storage), and the SGW-C may obtain the first node identifier of the first PGW-U from the PGW-C.

When the first control plane network element is a PGW-C, the PGW-C knows the first node identifier of the first PGW-U (e.g., the PGW-C obtains the first node identifier of the first PGW-U from local storage), and the PGW-C may obtain the second node identifier of the first SGW-U from the SGW-C.

The following describes separately an optional implementation in which the first control plane network element obtains a first node identifier when the first control plane network element is an SGW-C, and an optional implementation in which the first control plane network element obtains a second node identifier when the first control plane network element is a PGW-C.

SGW-c and PGW-C may be integrated or separated. Integrated SGW-C and PGW-C means that SGW-C and PGW-C are located in the same control plane network element node. Separated SGW-C and PGW-C means that SGW-C and PGW-C are located in different control plane network element nodes. For example, when SGW-C and PGW-C are integrated, the node identifiers of SGW-C and PGW-C may be the same, and when SGW-C and PGW-C are separated, the node identifiers of SGW-C and PGW-C may be different. A control plane network element may also be called a physical device, a physical node, or a functional network element. A control plane network element node may be a network element implemented on dedicated hardware, or may be a software instance running on dedicated hardware, or may be an instance with functions virtualized on a suitable platform. For example, the virtualization platform may be a cloud platform. An example of a control plane network element is a centralized gateway (CGW).

When the SGW-C and PGW-C are located in the same control plane network element node, the SGW-C can obtain the first node identifier of the first PGW-U from the local PGW-C, where the local PGW-C is the control plane network element node. The PGW-C can forward the first node identifier to the SGW-C by using the internal signaling of the control plane network element node, and the SGW-C can obtain the first node identifier from the PGW-C by using the internal signaling of the control plane network element node.

Similarly, when the SGW-C and PGW-C are located in the same control plane network element node, the PGW-C can obtain the second node identifier of the first SGW-U from the local SGW-C, where the local SGW-C is the control plane network element node. The SGW-C can forward the second node identifier to the PGW-C by using the internal signaling of the control plane network element node, and the PGW-C can obtain the second node identifier from the SGW-C by using the internal signaling of the control plane network element node.

When the SGW-C and the PGW-C are located in different control plane network element nodes, the PGW-C may obtain the second node identifier of the first SGW-U by exchanging messages with the SGW-C. Optionally, the SGW-C may send a Modify Bearer Request message to the PGW-C, where the Modify Bearer Request message may carry the second node identifier of the first SGW-U. The PGW-C receives the Modify Bearer Request message from the SGW-C and obtains the second node identifier of the first SGW-U from the Modify Bearer Request message.

Similarly, when the SGW-C and PGW-C are located in different control plane network element nodes, the SGW-C may obtain the first node identifier of the first PGW-U by exchanging messages with the PGW-C. Optionally, the PGW-C may send a Modify Bearer Response message to the SGW-C, where the Modify Bearer Response message carries the first node identifier of the first PGW-U. The SGW-C receives the Modify Bearer Response message from the PGW-C, and the SGW-C obtains the first node identifier of the first PGW-U from the Modify Bearer Response message. According to 3GPP 29.274 protocol, when a terminal device moves, an SGW is reselected and the new SGW-C sends a Modify Bearer Request message to the PGW-C anchored by the terminal device, which can be used to update the local IP address and the TEID of the GTP tunnel. The PGW-C returns a Modify Bearer Response message to the SGW-C, which carries the local IP address and the tunnel endpoint identifier (TEID) of the GPRS Tunneling Protocol (GTP) tunnel to complete the S5/S8 path switching. In this embodiment of the present application, when the SGW-C and the PGW-C are located in different control plane network element nodes and the SGW-C obtains the first node identifier, the SGW-C may extend the modify bearer response message in the 3GPP 29.274 protocol, add a first private information element, which may indicate the first node identifier of the first PGW-U, to the modify bearer response message sent by the PGW-C to the SGW-C, and stuff the first node identifier of the first PGW-U into the first private information element of the modify bearer response message. In this way, the SGW-C obtains the first node identifier of the first PGW-U from the modify bearer response message. When the SGW-C and the PGW-C are located in different control plane network element nodes and the PGW-C obtains the second node identifier, the PGW-C can extend the modify bearer request message in the 3GPP 29.274 protocol, add a second private information element that can indicate the second node identifier of the first SGW-U to the modify bearer request message sent by the SGW-C and the PGW-C to the PGW-C, and stuff the second node identifier of the first SGW-U into the second private information element of the modify bearer request message. In this way, the PGW-C can obtain the second node identifier of the first SGW-U from the bearer request message.

The following describes some possible implementations based on the embodiment of Figure 2c.

The following describes an optional implementation in which the first control plane network element obtains the node identifier of the first PSA-UPF and the node identifier of the first I-UPF at S201c.

The first control plane network element may be an SMF or an I-SMF.

When the first control plane network element is an I-SMF, the I-SMF knows the node identifier of the first I-UPF (e.g., the I-SMF obtains the node identifier of the first I-UPF from local storage) and the I-SMF may obtain the node identifier of the first PSA-UPF from the SMF.

When the first control plane network element is an SMF, in a scenario where an I-SMF is not inserted, the SMF may locally obtain the node identifier of the first PSA-UPF and the node identifier of the first I-UPF.

When the first control plane network element is an SMF, in a scenario where an I-SMF is inserted, the SMF knows the node identifier of the first PSA-UPF (e.g., the SMF obtains the node identifier of the first PSA-UPF from local storage) and the SMF may obtain the node identifier of the first I-UPF from the I-SMF.

The following describes separately an optional implementation in which the first control plane network element obtains a first node identifier when the first control plane network element is an I-SMF and an optional implementation in which the first control plane network element obtains a second node identifier when the first control plane network element is an SMF.

When the I-SMF is inserted, the SMF may obtain the node identifier of the first I-UPF by exchanging messages with the I-SMF. Optionally, the I-SMF may send a PDU Session Create Request (Nsmf_PDUSession_Create Request) message to the SMF, and the PDU Session Create Request message may carry the node identifier of the first I-UPF. The SMF receives the PDU Session Create Request message from the I-SMF and obtains the node identifier of the first I-UPF from the PDU Session Create Request message.

When the I-SMF is inserted, the I-SMF may obtain the node identifier of the first PSA-UPF by exchanging messages with the SMF. Optionally, the SMF may send a PDU Session Create Response (Nsmf_PDUSession_Create Response) message to the I-SMF, where the PDU Session Create Response message carries the node identifier of the first PSA-UPF. The I-SMF receives the PDU Session Create Response message from the SMF, where the I-SMF obtains the node identifier of the first PSA-UPF from the PDU Session Create Response message. In this embodiment of the present application, when an I-SMF is inserted and the I-SMF obtains a first node identifier, the I-SMF may extend the Create PDU Session Response message, add a private information element that may indicate the node identifier of the first PSA-UPF to the Create PDU Session Response message sent by the SMF to the I-SMF, and stuff the node identifier of the first PSA-UPF into the private information element of the Create PDU Session Response message. In this way, the I-SMF obtains the node identifier of the first PSA-UPF from the Create PDU Session Response message. When an I-SMF is inserted and the SMF obtains a node identifier of the first I-UPF, the SMF may extend the Create PDU Session Request message, add a private information element that may indicate the node identifier of the first I-UPF to the Create PDU Session Request message sent by the I-SMF to the SMF, and stuff the node identifier of the first I-UPF into the private information element of the Create PDU Session Request message. In this way, the SMF can obtain the node identifier of the first I-UPF from the PDU session creation request message.

In summary, an optional implementation has been described in which a first control plane network element obtains a first node identifier and a second node identifier. The following describes an optional implementation in which a first control plane network element determines whether a first user plane network element is disjoint from a second user plane network element based on the first node identifier and the second node identifier.

Determination method 1: Whether the first user plane network element is separated from the second user plane network element is determined by determining whether the first node identifier is the same as the second node identifier.

For example, if the first node identifier is the same as the second node identifier, the first control plane network element determines that the first user plane network element is not isolated from the second user plane network element, or, if the first node identifier is different from the second node identifier, the first control plane network element determines that the first user plane network element is isolated from the second user plane network element.

Similar to the control plane network elements, the two user plane network elements SGW-U and PGW-U may also be integrated or separated. The two user plane network elements being integrated means that the two user plane network elements are located in the same user plane network element node. The two user plane network elements being separated means that the two user plane network elements are located in different user plane network element nodes.

An example in which the user plane network elements are SGW-U and PGW-U is used to describe decision method 1 in detail.

The SGW-U and PGW-U are integrated means that the SGW-U and PGW-U are located in the same user plane network element node. The SGW-U and PGW-U are separated means that the SGW-U and PGW-U are located in different control plane network element nodes. The user plane network element node may also be called a physical device, a physical node, or a functional network element. The user plane network element node may be a network element implemented on dedicated hardware, or may be a software instance running on dedicated hardware, or may be an instance with virtualized functions on a suitable platform. For example, the virtualization platform may be a cloud platform. The user plane network element node is, for example, a distributed gateway (DGW).

When the SGW-U and the PGW-U are located in the same user plane network element node, the SGW-U and the PGW-U use the same node identifier, and the respective node identifiers of the SGW-U and the PGW-U may be set to the name of the user plane network element node, the IP address of the user plane network element node, or other identifiers of the user plane network element node. When the first node identifier is different from the second node identifier, the SGW-U and the PGW-U are located in different user plane network element nodes, that is, the SGW-U is separated from the PGW-U. Therefore, in the determination method 1, whether the first SGW-U is separated from the first PGW-U can be determined by determining whether the first node identifier is the same as the second node identifier. This determination method is strict and accurate. Using the determination method 1 to determine separation between user plane network elements may help improve the determination accuracy.

Determination method 2:

If the first information in the first node identifier is the same as the second information in the second node identifier, the first control plane network element determines that the first user plane network element is not detached from the second user plane network element, or if the first information in the first node identifier is different from the second information in the second node identifier, the first control plane network element determines that the first user plane network element is detached from the second user plane network element.

The first information indicates an area in which the first user plane network element is located, and the second information indicates an area in which the second user plane network element is located.

In this application, an area may be a geographic area or a region agreed upon between network elements or devices. The area may vary based on service requirements. An area may be at the granularity of a state, city, or county. For example, an area may be City A in State A. As another example, an area may be City B in State B.

In the determination method 2, whether the first user plane network element is separate from the second user plane network element is determined based on the information included in the node identifier and indicating the area. It can be understood that when the first user plane network element and the second user plane network element are located in different user plane gateway nodes, the first user plane network element and the second user plane network element may be located in the same area. In this case, although the first user plane network element and the second user plane network element are located in different user plane gateway nodes, when the determination method 2 is used, the first control plane network element determines that the first user plane network element is not separate from the second user plane network element.

When two user plane network elements are not on the same node but in the same area, the path transmission redundancy is not so large and the demand for PDN re-establishment is not so high. In this determination method, whether a user plane network element is separated can be flexibly determined. Compared with the method of determining that a user plane network element is separated across user plane network elements, in this determination method, the user plane network element is determined to be separated only when an area spans between the user plane network elements, and further operations are performed after separation. This can avoid signaling consumption caused by unnecessary operations performed after separation.

For example, the two user plane network elements are SGW-U and PGW-U. In decision method 2, the first node identifier and the second node identifier need to be named in a structured manner. Some fields, for example, first information in the first node identifier that identifies the area and second information in the second node identifier that identifies the area, identify the area.

Determination method 3:

If the first node identifier and the second node identifier are in the same group, the first control plane network element determines that the first user plane network element is not isolated from the second user plane network element, or if the first node identifier and the second node identifier are not in the same group, i.e., the first node identifier and the second node identifier are in different groups, the first control plane network element determines that the first user plane network element is isolated from the second user plane network element.

In this application, a "group" may also be referred to as a set, a list, or a combination. Optionally, the first user plane network element and the second user plane network element in a group may be located in the same area. The first control plane network element may pre-configure one or more groups, and the node identifiers of the first user plane network element and the second user plane network element located in the same area are set to the same group.

In the determination method 3, whether the first user plane network element is isolated from the second user plane network element is determined based on whether the first node identifier and the second node identifier are in the same group. It can be understood that even if the first user plane network element and the second user plane network element are located in different user plane gateway nodes, the node identifiers of the first user plane network element and the second user plane network element may be located in the same group. In this case, although the first user plane network element and the second user plane network element are located in different user plane gateway nodes, when the determination method 3 is used, the first control plane network element determines that the first user plane network element is not isolated from the second user plane network element.

When two user plane network elements are not on the same node but in the same area, the path transmission redundancy is not so large and the demand for PDN re-establishment is not so high. In this determination method, whether a user plane network element is separated can be flexibly determined. Compared with the method of determining that a user plane network element is separated across user plane network elements, in this determination method, the user plane network element is determined to be separated only when an area spans between the user plane network elements, and further operations are performed after separation. This can avoid signaling consumption caused by unnecessary operations performed after separation.

When the two user plane network elements are SGW-U and PGW-U, in decision method 1 and decision method 3, the node identifier does not need to be named in a structured manner. If the node identifier is currently configured in the on-net device, the on-net device does not need to change the node identifier.

In summary, any implementation in which a first control plane network element determines whether a first user plane network element is isolated from a second user plane network element based on a first node identifier and a second node identifier is described, including determination method 1, determination method 2, and determination method 3.

The following describes Decision Method 1, Decision Method 2, and Decision Method 3 by using examples with reference to specific application scenarios.

First, an application scenario in a 4G communication system is used as an example for illustration.

Figure 3 shows two scenarios of the movement process of a terminal device. In scenario 1, the terminal device moves from a district in city A to b district in city A. In scenario 2, the terminal device moves from b district in city A to city B.

In County a of City A, County b of City A, and City B, both SGW-U and PGW-U are deployed on the same user plane gateway node. In County a of City A, SGW-U1 and PGW-U1 are deployed on DGW1. In County b of City A, SGW-U2 and PGW-U2 are deployed on DGW2. In City B, SGW-U3 and PGW-U3 are deployed on DGW3. County a of City A, County b of City A, and City B belong to State A. The control plane network elements are located in State A. SGW-C and PGW-C are deployed on the same control plane gateway node. In State A, SGW-C and PGW-C are deployed on the CGW. The same set of control plane network elements is connected to user plane network elements in multiple areas. The SGW-C in State A is connected to SGW-U1, SGW-U2, and SGW-U3, and the PGW-C in State A is connected to PGW-U1, PGW-U2, and PGW-U3. Figure 3 further shows that the SGW-C in State A is connected to an MME.

From Figure 3, it can be seen that in scenario 1, when the terminal device moves from a-county in city A to b-county in city A, the SGW-U is reselected and changes from SGW-U1 to SGW-U2, while PGW-U1 is anchored and remains unchanged. Thus, SGW-U2 is located in DGW2, and PGW-U1 is located in DGW1. That is, SGW-U2 and PGW-U1 are located in different user plane gateway nodes. In scenario 2, when the terminal device moves from b-county in city A to city B, the SGW-U is reselected and changes from SGW-U2 to SGW-U3, while PGW-U2 is anchored and remains unchanged.

The control plane network element may determine whether the user plane network element is isolated using determination method 1 to determination method 3. The first control plane network element may be an SGW-C in State A or a PGW-C in State A.

When the first control plane network element determines whether the user plane network elements are separated in scenario 1 in determination method 1, the first control plane network element may determine whether the node identifier of SGW-U2 is the same as the node identifier of PGW-U1. For example, the node identifier of SGW-U2 is "DGW2" and the node identifier of PGW-U1 is "DGW1". If the first control plane network element determines by comparison that "DGW2" is different from "DGW1" (i.e., DGW2 ≠ DGW1), the first control plane network element considers the SGW-U to be separated from the PGW-U.

When the first control plane network element determines whether the user plane network element is detached in scenario 1 in decision method 2, the first control plane network element may determine whether the first information in the node identifier of SGW-U2 is the same as the second information in the node identifier of PGW-U1. If the first information in the node identifier of SGW-U2 is the same as the second information in the node identifier of PGW-U1, the user plane network element is not detached. If the first information in the node identifier of SGW-U2 is different from the second information in the node identifier of PGW-U1, the user plane network element is detached. For example, the node identifier of SGW-U2 is "DGW2.cityA.provinceA", the first information indicating the area in which SGW-U2 is located is "cityA.provinceA", the node identifier of PGW-U1 is "DGW1.cityA.provinceA", and the second information indicating the area in which PGW-U1 is located is "cityA.provinceA". The first information is the same as the second information. In this case, the first control plane network element determines that the user plane network element is not separated. It can be seen that the results of determining whether the user plane network element is separated in scenario 1 by the first control plane network element based on determination method 1 and determination method 2 are different.

When the first control plane network element determines whether the user plane network element is detached in scenario 2 in decision method 2, the first control plane network element may determine whether the first information in the node identifier of SGW-U3 is the same as the second information in the node identifier of PGW-U2. If the first information in the node identifier of SGW-U3 is the same as the second information in the node identifier of PGW-U2, the user plane network element is not detached. If the first information in the node identifier of SGW-U3 is different from the second information in the node identifier of PGW-U2, the user plane network element is detached. For example, the node identifier of SGW-U3 is "DGW3.cityB.provinceA", the first information indicating the area in which SGW-U3 is located is "cityB.provinceA", the node identifier of PGW-U2 is "DGW2.cityA.provinceA", and the second information indicating the area in which PGW-U2 is located is "cityA.provinceA". The first information is different from the second information. In this case, the first control plane network element determines that the user plane network elements are separated.

When the first control plane network element determines whether the user plane network elements are separated in scenario 1 in decision method 3, the first control plane network element may determine whether the node identifier of SGW-U2 and the node identifier of PGW-U1 are in the same group. If the node identifier of SGW-U2 and the node identifier of PGW-U1 are in the same group, the user plane network elements are not separated. If the node identifier of SGW-U2 and the node identifier of PGW-U1 are not in the same group, the user plane network elements are separated. The first control plane network element may pre-configure one or more groups. For example, the first control plane network element configures group 1 as {DGW1, DGW2} and group 2 as {DGW3}. The node identifier of SGW-U2 is "DGW2" and the node identifier of PGW-U1 is "DGW1". If the first control plane network element determines that the node identifier of SGW-U2 and the node identifier of PGW-U1 are in the same group, the first control plane network element determines that the user plane network elements are not separated.

When the first control plane network element determines whether the user plane network elements are separated in scenario 2 in decision method 3, the first control plane network element may determine whether the node identifier of SGW-U3 and the node identifier of PGW-U2 are in the same group. If the node identifier of SGW-U3 and the node identifier of PGW-U2 are in the same group, the user plane network elements are not separated. If the node identifier of SGW-U3 and the node identifier of PGW-U2 are not in the same group, the user plane network elements are separated. The first control plane network element may pre-configure one or more groups. For example, the first control plane network element configures group 1 as {DGW1, DGW2} and group 2 as {DGW3}. The node identifier of SGW-U3 is "DGW3" and the node identifier of PGW-U2 is "DGW2". If the first control plane network element determines that the node identifier of SGW-U3 and the node identifier of PGW-U2 are not in the same group, the first control plane network element determines that the user plane network elements are disjoint.

In the example shown in FIG. 3, the SGW-C and PGW-C are located in the same control plane network element node. The following uses FIG. 4 as an example to describe a communication scenario in which the SGW-C and PGW-C are located in different control plane network element nodes. It should be noted that the scenario shown in FIG. 4 shows a possible deployment case. In practical applications, there may be communication scenarios in which one DGW is connected to multiple CGWs.

Figure 4 shows two scenarios of the movement process of a terminal device. In scenario 3, the terminal device moves from city B in state A to city C in state A. In scenario 4, the terminal device moves from city C in state A to city D in state B.

In City B in State A, City C in State A, and City D in State B, both SGW-U and PGW-U are deployed in the same user plane gateway node. In City B in State A, SGW-U2 and PGW-U2 are deployed in DGW2. In City C in State A, SGW-U3 and PGW-U3 are deployed in DGW3. In City C in State B, SGW-U4 and PGW-U4 are deployed in DGW4. PGW-C1 in State A is located in CGW1, and PGW-C1 is connected to PGW-U2, SGW-C2 and PGW-C2 in State A are located in CGW2, and SGW-C2 is connected to SGW-U3, and PGW-C2 is connected to PGW-U3. SGW-C3 and PGW-C3 in State B are located in CGW3, SGW-C3 is connected to SGW-U4, and PGW-C3 is connected to PGW-U4. Figure 4 further shows that MME1 in State A is connected to CGW1 and CGW2, and MME2 in State B is connected to CGW3.

From Figure 4, we can see that in Scenario 3, when the terminal device moves from City B in State A to City C in State A, MME1 reselects an SGW-C based on the location of the terminal device and reselects SGW-C2 from the original SGW-C1. SGW-C2 selects SGW-U3 for the terminal device. Thus, SGW-U is changed from SGW-U2 to SGW-U3. PGW-C1 and PGW-U2 are anchored and remain unchanged. SGW-C2 and PGW-C1 are located in different CGWs.

The first control plane network element may obtain a node identifier to be used for comparison by exchanging messages. The first control plane network element may be SGW-C2 or PGW-C1. Messages may be forwarded between PGW-C1 and SGW-C2 to exchange node identifiers of user plane network elements. For example, SGW-C2 may send a Modify Bearer Request message to PGW-C1, where the Modify Bearer Request message may carry the node identifier of SGW-U3. PGW-C1 receives the Modify Bearer Request message from SGW-C2 and obtains the node identifier of SGW-U3 from the Modify Bearer Request message. PGW-C1 may send a Modify Bearer Response message to SGW-C2, where the Modify Bearer Response message carries the node identifier of PGW-U2. SGW-C2 receives a change bearer response message from PGW-C1, and SGW-C2 obtains the node identifier of PGW-U2 from the change bearer response message.

The first control plane network element may determine whether the user plane network element is isolated in scenario 3 using determination methods 1 to 3.

When the first control plane network element determines whether the user plane network elements are separated in scenario 3 in determination method 1, the first control plane network element may determine whether the node identifier of SGW-U3 is the same as the node identifier of PGW-U2. For example, the node identifier of SGW-U3 is "DGW3" and the node identifier of PGW-U2 is "DGW2". If the first control plane network element determines by comparison that "DGW3" is different from "DGW2" (i.e., DGW3 ≠ DGW2), the first control plane network element considers the user plane network elements to be separated.

When the first control plane network element determines whether the user plane network element is isolated in scenario 3 in decision method 2, the first control plane network element may determine whether the first information in the node identifier of SGW-U3 is the same as the second information in the node identifier of PGW-U2. If the first information in the node identifier of SGW-U3 is the same as the second information in the node identifier of PGW-U2, the user plane network element is not isolated. If the first information in the node identifier of SGW-U3 is different from the second information in the node identifier of PGW-U2, the user plane network element is isolated. The first information and the second information are information indicating an area. The information indicating an area may be information indicating a state. For example, the node identifier of SGW-U3 is "DGW3.cityC.provinceA", the first information indicating the area in which SGW-U3 is located is "provinceA", the node identifier of PGW-U2 is "DGW2.cityB.provinceA", and the second information indicating the area in which PGW-U2 is located is "provinceA". "provinceA" = "provinceA", that is, the first information is the same as the second information. In this case, the first control plane network element determines that the user plane network element is not separated. The information indicating the area may be information indicating a city. For example, the node identifier of SGW-U3 is "DGW3.cityC.provinceA", the first information indicating the area in which SGW-U3 is located is "cityC.provinceA", the node identifier of PGW-U2 is "DGW2.cityB.provinceA", and the second information indicating the area in which PGW-U2 is located is "cityB.provinceA". The first information is different from the second information. In this case, the first control plane network element determines that the user plane network elements are separated.

When the first control plane network element determines whether the user plane network elements are separated in scenario 3 in decision method 3, the first control plane network element may determine whether the node identifier of SGW-U3 and the node identifier of PGW-U2 are in the same group. If the node identifier of SGW-U3 and the node identifier of PGW-U2 are in the same group, the user plane network elements are not separated. If the node identifier of SGW-U3 and the node identifier of PGW-U2 are not in the same group, the user plane network elements are separated. The first control plane network element may pre-configure one or more groups. For example, the first control plane network element configures group 1 as {DGW1, DGW2, DGW3} and group 2 as {DGW4}. The node identifier of SGW-U3 is "DGW3" and the node identifier of PGW-U2 is "DGW2". If the first control plane network element determines that the node identifier of SGW-U3 and the node identifier of PGW-U2 are in the same group, the first control plane network element determines that the user plane network elements are not separated.

As shown in Figure 4, in Scenario 4, when the terminal device moves from City C in State A to City D in State B, MME2 reselects an SGW-C based on the location of the terminal device and reselects SGW-C3 from the original SGW-C2. SGW-C3 selects SGW-U4 for the terminal device. Thus, SGW-U is changed from SGW-U3 to SGW-U4. PGW-C2 and PGW-U3 are anchored and remain unchanged. SGW-C3 and PGW-C2 are located in different CGWs.

The first control plane network element may obtain a node identifier to be used for comparison by exchanging messages. The first control plane network element may be SGW-C3 or PGW-C2. Messages may be forwarded between PGW-C2 and SGW-C3 to exchange node identifiers of user plane network elements. For example, SGW-C3 may send a Modify Bearer Request message to PGW-C2, where the Modify Bearer Request message may carry the node identifier of SGW-U4. PGW-C2 receives the Modify Bearer Request message from SGW-C3 and obtains the node identifier of SGW-U4 from the Modify Bearer Request message. PGW-C2 may send a Modify Bearer Response message to SGW-C3, where the Modify Bearer Response message carries the node identifier of PGW-U3. SGW-C3 receives a change bearer response message from PGW-C2, and SGW-C3 obtains the node identifier of PGW-U3 from the change bearer response message.

The first control plane network element may determine whether the user plane network element is isolated in scenario 4 using determination methods 1 to 3. The following uses determination method 2 and determination method 3 as examples for explanation.

When the first control plane network element determines whether the user plane network element is isolated in scenario 4 in decision method 2, the first control plane network element may determine whether the first information in the node identifier of the SGW-U4 is the same as the second information in the node identifier of the PGW-U3. If the first information in the node identifier of the SGW-U4 is the same as the second information in the node identifier of the PGW-U3, the user plane network element is not isolated. If the first information in the node identifier of the SGW-U4 is different from the second information in the node identifier of the PGW-U3, the user plane network element is isolated. The first information and the second information are information indicative of an area. The information indicative of an area may be information indicative of a state. For example, the node identifier of SGW-U 4 is "DGW4.cityD.provinceB", the first information indicating the area in which SGW-U 4 is located is "provinceB", the node identifier of PGW-U 3 is "DGW3.cityC.provinceA", the second information indicating the area in which PGW-U 3 is located is "provinceA". "provinceA" ≠ "provinceB", i.e. the first information is different from the second information. In this case, the first control plane network element determines that the user plane network elements are separated.

When the first control plane network element determines whether the user plane network elements are separated in scenario 4 in decision method 3, the first control plane network element may determine whether the node identifier of SGW-U4 and the node identifier of PGW-U3 are in the same group. If the node identifier of SGW-U4 and the node identifier of PGW-U3 are in the same group, the user plane network elements are not separated. If the node identifier of SGW-U4 and the node identifier of PGW-U3 are not in the same group, the user plane network elements are separated. The first control plane network element may pre-configure one or more groups. For example, the first control plane network element configures group 1 as {DGW1, DGW2, DGW3} and group 2 as {DGW4}. The node identifier of SGW-U4 is "DGW4" and the node identifier of PGW-U3 is "DGW3". If the first control plane network element determines that the node identifier of SGW-U4 and the node identifier of PGW-U3 are not in the same group, the first control plane network element determines that the user plane network elements are isolated.

In summary, an implementation has been described in which a first control plane network element determines whether a user plane network element is isolated based on a first node identifier and a second node identifier. The following describes subsequent actions that may be performed by the first control plane network element if the first control plane network element determines that the user plane network element is isolated.

In an embodiment, when the first control plane network element determines that the first SGW-U is disassociated from the first PGW-U, the first control plane network element initiates re-establishment of a PDN connection to the terminal device. Optionally, the first control plane network element is an SGW-C. When the SGW-C determines that the first SGW-U is disassociated from the first PGW-U, the SGW-C initiates re-establishment of a PDN connection to the terminal device when the S1 connection to the terminal device is released. In this way, impact on ongoing data and voice services can be avoided. The release of the S1 connection may also be replaced by the terminal device not transmitting data for a certain period of time, or may be replaced by the terminal device entering an idle state. Alternatively, the first control plane network element is a PGW-C. If the PGW-C determines that the first SGW-U is disassociated from the first PGW-U, the PGW-C initiates re-establishment of the PDN connection to the terminal device when the terminal device has no traffic within a specified time. In this way, impacts to ongoing data and voice services can be avoided.

In a possible design, the first control plane network element may use a timer before initiating PDN re-establishment. For example, the first control plane network element is the SGW-C. The SGW-C starts the timer when the S1 connection to the terminal device is released. After the timer has elapsed, if the first SGW-U is still detached from the first PGW-U and the terminal device is still in idle state, the SGW-C initiates re-establishment of the PDN connection to the terminal device.

As shown in FIG. 5, an example in which the first control plane network element is an SGW-C is used below to describe the procedure in which the first control plane network element triggers a detachment decision with reference to a specific scenario. During the movement of the terminal device, the MME reselects an SGW-C based on the location of the terminal device. The reselected SGW-C is the first control plane network element, and the PGW-C is anchored and remains unchanged.

S501: The terminal device sends a tracking area update (TAU) request to the network device, and the network device receives the TAU request.

S502: The network device sends a TAU request to the MME, and the MME receives the TAU request.

S503: The MME sends a create session request to the SGW-C, and the SGW-C receives the create session request.

S504: The SGW-C sends a modify bearer request to the PGW-C, and the PGW-C receives the modify bearer request.

S505: The PGW-C sends a modify bearer response to the SGW-C, and the SGW-C receives the modify bearer response.

S506: The SGW-C determines whether the user plane network elements are separated (i.e., whether the SGW-U is separated from the PGW-U) and marks the PDN connection for separation between the SGW-U and the PGW-U if the SGW-C determines that the user plane network elements are separated.

The user plane network elements are separate, i.e. the SGW-U and PGW-U activated over the PDN connection are not on the same physical node/user plane network element.

S507: The SGW-C returns a create session response to the MME, and the MME receives the create session response.

S508: The MME returns a TAU accept message to the terminal device.

In this embodiment, for example, it may be understood that the TAU procedure causes SGW reselection. Other procedures (e.g., S1/X2 handover procedure) may also cause SGW reselection. For procedures to be performed after other procedures cause SGW reselection, please refer to this embodiment.

Based on the embodiment of FIG. 5, as shown in FIG. 6, an example in which the first control plane network element is an SGW-C is used below to describe the procedure in which the first control plane network element starts a timer with reference to a specific scenario. During the movement of the terminal device, the MME reselects the SGW-C based on the location of the terminal device. The reselected SGW-C is the first control plane network element, and the PGW-C is anchored and unchanged. When the S1 connection to the terminal device is released, the SGW-C triggers the re-establishment of the PDN connection for the separation between the SGW-U and the PGW-U.

S601: The network device sends an S1 user context release request to the MME, and the MME receives the S1 user context release request.

S602: The MME sends a release access bearer request to the SGW-C, and the SGW-C receives the release access bearer request.

S603: SGW-C starts the timer.

S604: The SGW-C returns a release access bearer response to the MME, and the MME receives the release access bearer response.

S605: The MME returns an S1 user context release command to the network device, and the network device receives the S1 user context release command.

S606: The network device sends a radio resource control (RRC) connection release message to the terminal device, and the terminal device receives the RRC connection release message.

S607: The network device sends an S1 user context release complete message to the MME, and the MME receives the S1 user context release complete message.

S608: The SGW-C determines that the timer has expired and triggers a PDN re-establishment procedure for the terminal device.

Based on the embodiment of FIG. 5 and/or FIG. 6, an example in which the first control plane network element is an SGW-C, as shown in FIG. 7, is used below to describe the procedure in which the first control plane network element initiates PDN re-establishment with reference to a specific scenario. During the movement of the terminal device, the MME reselects the SGW-C based on the location of the terminal device. The reselected SGW-C is the first control plane network element, and the PGW-C is anchored and unchanged.

S701: The SGW-C sends a delete session request to the PGW-C, and the PGW-C receives the delete session request from the SGW-C.

S702: The PGW-C sends a delete session response to the SGW-C, and the SGW-C receives the delete session response from the PGW-C.

S703: The SGW-C sends a delete bearer request to the MME, and the MME receives the delete bearer request.

The delete bearer request carries one or more of the following information: associated evolved packet system (EPS) bearer identifier and deletion cause. For example, the deletion cause is reactivation requested. The terminal device can be reactivated by carrying information about the deletion cause. In the activation process, the SGW-C/PGW-C selects a combined SGW-U/PGW-U for the terminal device, so that the user plane network elements can be combined and the path for forwarding data or voice traffic is better.

S704: The MME initiates paging to the terminal device.

S705: The MME sends a radio access bearer (E-UTRAN radio access bearer, E-RAB) release command or a deactive EPS bearer context request to the network device, and the network device receives the E-RAB release command or the deactive EPS bearer context request.

S706: The network device sends a radio bearer release request to the terminal device, and the terminal device receives the radio bearer release request.

S707: The terminal device sends a radio bearer release response to the network device, and the network device receives the radio bearer release response.

S708: The network device sends an E-RAB release response to the MME, and the MME receives the E-RAB release response.

S709: The terminal device sends a deactive EPS bearer context accept message to the network device, and the network device receives the deactive EPS bearer context accept message.

S710: The network device sends a deactive EPS bearer context accept message to the MME, and the MME receives the deactive EPS bearer context accept message.

S711: The MME sends a delete bearer response to the SGW-C, and the SGW-C receives the delete bearer response.

It can be understood that in Figures 5 to 7, an example in which the first control plane network element is an SGW-C is used to describe the procedure of initiating PDN re-establishment. When the first control plane network element is a PGW-C, the procedure of initiating PDN re-establishment can be obtained by using a similar process. It should be noted that when the first control plane network element is a PGW-C, the PGW-C may trigger the PDN re-establishment procedure of the terminal device after the terminal device has no traffic for a certain time. The PGW-C may send a delete bearer request to the new SGW-C. After receiving the delete bearer request from the PGW-C, the new SGW-C executes steps S703 to S711.

Based on the same technical concept, an embodiment of the present application further provides a method for determining isolation between user plane network elements. As shown in FIG. 8, the procedure of the method for determining isolation between user plane network elements is as follows: the method is performed by an SGW-C, and the SGW-C and the first PGW-C are located in different control plane network element nodes.

S801: The SGW-C obtains the address of the first PGW-C.

S802: Based on the address of the first PGW-C and the preset address, the SGW-C determines whether the SGW-U has disassociated from the first PGW-U or whether to initiate re-establishment of a PDN connection to the terminal device.

The preset addresses include the addresses of one or more PGW-Cs located in the same area as the SGW-C. The address of the PGW-C may be, for example, an S5/S8 interface IP address. The first PGW-U is a user plane anchor through which the terminal device accesses the PDN, and the first PGW-C is a control plane anchor through which the terminal device accesses the PDN.

When the SGW-C determines, based on the address of the first PGW-C and the preset address, whether the SGW-U has disassociated from the first PGW-U, the SGW-C may trigger re-establishment of a PDN connection to the terminal device.

Alternatively, the SGW-C may determine whether to re-establish a PDN connection to the terminal device based on the address of the first PGW-C and the preset address.

Optionally, if the preset address includes the address of the first PGW-C, the SGW-C determines that the SGW-U has not disassociated from the first PGW-U or that re-establishment of the PDN connection does not need to be initiated.

If the preset address does not include the address of the first PGW-C, the SGW-C determines that the SGW-U has detached from the first PGW-U or decides to initiate re-establishment of the PDN connection to the terminal device.

Optionally, the SGW-C may obtain the address of the first PGW-C in the following manner: During the movement of the terminal device, the MME selects a new SGW-C based on the location of the terminal device. According to the 3GPP 29.274 protocol, the MME sends a Create Session Request message to the new SGW-C, which carries the S5/S8 interface address of the first PGW-C anchored by the terminal device. The SGW-C determines whether the SGW-U is disassociated from the first PGW-U based on whether the S5/S8 interface address of the first PGW-C is in the preset addresses.

In the embodiment of FIG. 8, the SGW-C determines whether the user plane network elements are isolated based on the address of the control plane network element, and determines that the user plane network elements are isolated when it determines that the control plane network elements are isolated (i.e., the address of the first PGW-C is not in the preset address) by presetting the control plane network element group based on the area. The preset address is the address of the PGW-C in the same area as the SGW-C. In this way, the area can be divided based on the service requirements, and the preset address is set so that the separation between the user plane network elements is more flexibly determined to satisfy the service requirements. The embodiment of FIG. 8 is applicable to a scenario in which the separation between the user plane network elements is determined over a wide area range. In a non-CUPS scenario, the MME determines the separation between the SGW and the PGW based on the canonical node names of the SGW and the PGW. In this solution in which the MME determines the separation between user planes, the gateway node needs to be named in a regular and structured manner, and the UE needs to ensure that the name information of the gateway node is effectively transferred and not lost during 2G/3G/4G/5G interworking. Compared with the above solution in which the MME determines the separation between user planes, in the embodiment of FIG. 8, the separation between user plane network elements can also be determined based on the address of the control plane network element. Note that in the embodiment of FIG. 8, the gateway node does not need to be named in a regular and structured manner, and the UE does not need to ensure that the name information of the gateway node is effectively transferred and not lost during 2G/3G/4G/5G interworking.

In the embodiment of FIG. 8, in a scenario where the management area of the control plane network element spans between the SGW-U and the PGW-U, it can be determined whether the user plane network element is split. In this scenario, the determination is performed by using the embodiment of FIG. 8, so the decision granularity is large. In solution A, when the SGW-C determines that the control plane network element is split, the SGW-C determines that the user plane network element is split. For example, if the SGW-C determines by comparison that the PGW-C S5/S8 IP in the create session request message is different from the local PGW-C S5/S8 IP, the SGW-C determines that the PGW-C and the SGW-C are not in the same control plane network element node. Compared to solution A, in the embodiment of FIG. 8, the decision granularity is large, so the result of the decision of split between the user planes can be reduced, and the actions performed after it is determined that the user plane is split, such as PDN re-establishment, can be further reduced to reduce signaling overhead.

The embodiment of FIG. 8 is described in more detail below with reference to a specific application scenario.

Figure 9 shows two scenarios of the mobility process of a terminal device. In scenario 5, the terminal device moves from city B in state A to city C. In scenario 6, the terminal device moves from city C in state A to city D in state B. As shown in Figure 9, in cities B and C in state A and city D in state B, SGW-U and PGW-U are both deployed in the same user plane network element node. In city B in state A, SGW-U2 and PGW-U2 are deployed in DGW2. In city C in state A, SGW-U3 and PGW-U3 are deployed in DGW3. In city C in state B, SGW-U4 and PGW-U4 are deployed in DGW4. PGW-C1 in State A is located in CGW1, and PGW-C1 is connected to PGW-U2, SGW-C2 and PGW-C2 in State A are located in CGW2, SGW-C2 is connected to SGW-U3, and PGW-C2 is connected to PGW-U3. SGW-C3 and PGW-C3 in State B are located in CGW3, SGW-C3 is connected to SGW-U4, and PGW-C3 is connected to PGW-U4. Figure 9 further shows that MME1 in State A is connected to CGW2 and CGW2, and MME2 in State B is connected to CGW3.

In Scenario 5, when the terminal device moves from City B to City C in State A, the MME reselects an SGW-C based on the location of the terminal device and reselects SGW-C2 from the original SGW-C1. SGW-C2 selects SGW-U3 for the terminal device. Thus, SGW-U is changed from SGW-U2 to SGW-U3. PGW-C1 and PGW-U2 are anchored and remain unchanged.

SGW-C2 may obtain the address of PGW-C1 from the create session request message from the MME. For example, the address of PGW-C1 is S5/S8 IP "1.1.1.1". When using solution A to determine whether the user plane network elements are disjoint, SGW-C2, by default, considers the SGW-U to be disjoint from the PGW-U when it determines that the address of PGW-C1 is different from the local PGW-C2 address S5/S8 IP "2.2.2.2". When the solution of the embodiment of FIG. 8 is used, the preset address is configured in SGW-C2, and the preset address includes {1.1.1.1}. If SGW-C2 determines that the address of PGW-C1 is within the preset address, SGW-C2 considers that the SGW-U is not disjoint from the PGW-U. According to the embodiment of FIG. 8, the address of PGW-C1 is different from the address of the local PGW-C2, S5/S8 IP "2.2.2.2", but if the address of PGW-C1 is in the preset addresses, SGW-C2 still considers that SGW-U is not detached from PGW-U.

In Scenario 6, when the terminal device moves from City C in State A to City D in State B, the MME reselects an SGW-C based on the location of the terminal device, reselects SGW-C3 from the original SGW-C2, and SGW-C3 selects SGW-U4 for the terminal device. PGW-C2 and PGW-U3 are anchored and remain unchanged.

The preset address {4.4.4.4, 5.5.5.5} is configured in SGW-C3. SGW-C3 obtains the address of PGW-C2, i.e., S5/S8 IP "2.2.2.2", from the Create Session Request message sent by the MME. If SGW-C3 determines that the address of PGW-C2 is different from the local PGW-C3 address S5/S8 IP "3.3.3.3" and that the address of PGW-C2 is not within the preset addresses {4.4.4.4, 5.5.5.5}, SGW-C3 considers the SGW-U to be detached from the PGW-U.

From the scenario of FIG. 9, it can be seen that, according to the embodiment of FIG. 8, when the terminal device moves within state A, the user plane network elements are typically determined to be not separated. When the terminal device moves between states, a separation between the user planes is determined.

Similar to the technical concept of the embodiment of FIG. 8, the embodiment of the present application further provides a method for determining separation between user plane network elements. As shown in FIG. 10, the procedure of the method for determining separation between user plane network elements is as follows: the method is performed by a PGW-C, and the PGW-C and the first SGW-C are located in different control plane network element nodes.

S1001: The PGW-C obtains the address of the first SGW-C.

S1002: The PSGW-C determines whether the PGW-U has disassociated from the first SGW-U or whether to initiate re-establishment of a PDN connection to the terminal device based on the address of the first SGW-C and the preset address. For ease of description, the preset address in the embodiment of FIG. 10 may be referred to as the second preset address.

The second preset address includes the address of one or more SGW-Cs located in the same area as the PGW-C, and the address of the SGW-C may be, for example, an S5/S8 interface IP address.

The PGW-U is the user plane anchor through which terminal devices access the PDN, and the PGW-C is the control plane anchor through which terminal devices access the PDN.

When the PGW-C determines, based on the address of the first SGW-C and the preset address, whether the PGW-U has disassociated from the first SGW-U, the PGW-C may trigger re-establishment of a PDN connection to the terminal device.

Alternatively, the PGW-C may determine whether to re-establish a PDN connection to the terminal device based on the address of the first SGW-C and the preset address.

Optionally, if the preset address includes the address of the first SGW-C, the PGW-C determines that the PGW-U has not disassociated from the first SGW-U or that re-establishment of the PDN connection does not need to be initiated.

If the preset address does not include the address of the first SGW-C, the PGW-C determines that the PGW-U has detached from the first SGW-U or decides to initiate re-establishment of the PDN connection to the terminal device.

Optionally, the PGW-C may obtain the address of the first SGW-C in the following manner: During the movement of the terminal device, the MME selects a new SGW-C, i.e., the first SGW-C, based on the location of the terminal device, and the first SGW-C sends a modify bearer request message to the PGW-C, where the message carries the S5/S8 interface address of the new SGW-C. The PGW-C determines whether the PGW-U is detached from the first SGW-U based on whether the S5/S8 interface address of the first SGW-C is in the preset addresses.

The embodiment of FIG. 10 and the embodiment of FIG. 8 are based on the same technical concept, but are executed by different entities. Based on the example application scenario in the embodiment of FIG. 10, it can be understood that the application scenario shown in the embodiment of FIG. 9 may be referred to, provided that the executing entity is changed from the SGW-C to the PGW-C.

For the advantageous effects brought by the embodiment of FIG. 10, please refer to the description of the embodiment of FIG. 8. In FIG. 10, the PGW-C determines whether the user plane network element is separated based on the address of the control plane network element, and determines that the user plane network element is separated when it determines that the control plane network element is separated (i.e., the address of the first SGW-C is not in the preset address) by presetting the control plane network element group based on the area. The preset address is the address of the SGW-C in the same area as the PGW-C. In this way, the area can be divided based on the service requirements, and the preset address is set so that the separation between the user plane network elements is more flexibly determined to meet the service requirements. Similar to the effect of the embodiment of FIG. 8, in the embodiment of FIG. 10, the gateway nodes do not need to be named in a regular and structured manner, and the decision granularity is large, so that the result of the determination of the separation between the user planes can be reduced, and the operations performed after it is determined that the user plane is separated, such as PDN re-establishment, can be further reduced to reduce the signaling overhead.

For the method of determining separation between user plane network elements provided in the embodiments of Figures 8 and 10, for operations performed after it is determined that the user plane network elements are separated, please refer to the operations performed after it is determined that the user plane network elements are separated in the embodiment of Figure 2b. Details will not be described again here. For example, after it is determined that the user plane network elements are separated, re-establishment of a PDN connection to the terminal device is initiated.

When this embodiment of the present application is applied to a 5G communication system, based on the method for determining separation between user plane network elements provided in FIG. 2c, the following further describes in detail the method for determining separation between user plane network elements by using some specific application scenarios.

As shown in FIG. 11, in a 5G communication system, the procedure of the method for determining separation between user plane network elements is as follows:

S1101: The terminal device sends a service request to the access network device, and the access network device receives the service request from the terminal device.

When a terminal device moves within the management area of the SMF, if the terminal device needs to perform a data service, the terminal device initiates a service request procedure.

S1102: The access network device sends N2 information to the AMF, and the AMF receives N2 information from the access network device.

N2 information carries service requests.

S1103: The AMF sends a PDU session update context request (Nsmf_PDUsession_updateSMcontext request) to the SMF, and the SMF receives the PDU session update context request from the AMF.

S1104: SMF selects UPF.

When the terminal device moves out of the coverage area of the PSA-UPF, the SMF determines, based on the access area of the terminal device, whether the PSA-UPF (i.e., the PDU session anchor UPF) can serve the area. If the PSA-UPF cannot serve the area, the SMF selects an I-UPF for relaying to interact with wireless networks in the area to implement end-to-end network connectivity.

S1105: The SMF sends an N4 session establishment request to the I-UPF, and the I-UPF receives the N4 session establishment request.

S1106: The I-UPF returns an N4 session establishment response to the SMF, and the SMF receives the N4 session establishment response.

S1107: The SMF sends an N4 session modification request to the PSA-UPF, and the PSA-UPF receives the N4 session modification request.

S1108: The PSA-UPF returns an N4 session modification response to the SMF, and the SMF receives the N4 session modification response.

S1109: The SMF determines whether the user plane network element is separated.

If the SMF determines that the user plane network elements are separated, the SMF marks the bearers corresponding to the separation between the user plane network elements.

The SMF may perform a separation decision based on the node identifier of the I-UPF and the node identifier of the PSA-UPF. For the determination method, please refer to any one of the determination methods 1 to 3. The node identifier of the I-UPF and the node identifier of the PSA-UPF may be, for example, a UPF node identifier (UPF Node ID), or may be other identifiers, for example, a UPF NfInstance ID (3GPP 29.571). The SMF determines whether the user plane is separated, i.e., whether the PSA-UPF is separated from the I-UPF, based on the node identifier of the PSA-UPF and the node identifier of the I-UPF. Upon determining that the PSA-UPF is separated from the I-UPF, the SMF may trigger a re-establishment of the PDU of the terminal device.

S1110: The SMF sends a PDU session update context response (Nsmf_PDUsession_updateSMcontext response) to the AMF, and the AMF receives the PDU session update context response.

S1111: The AMF sends an N2 response (N2 request) to the access network device, and the access network device receives the N2 response and responds to it.

S1112: The AMF sends a PDU session update context request (Nsmf_PDUSession_updateSMcontext request) to the SMF, and the SMF receives the PDU session update context request from the AMF.

S1113: The SMF sends an N4 session modification request to the I-UPF, and the I-UPF receives the N4 session modification request.

S1114: The I-UPF returns an N4 session modification response to the SMF, and the SMF receives the N4 session modification response.

S1115: The SMF sends a PDU session update context response (Nsmf_PDUsession_updateSMcontext response) to the AMF, and the AMF receives the PDU session update context response.

It may be understood that the conditions triggering the decision to separate between user plane network elements in the embodiment of FIG. 11 are an example. Upon finding an I-UPF, the SMF decides to separate between user plane network elements. Other conditions may be similar to an Xn/N2 handover, causing the insertion of an I-UPF and triggering the SMF to decide to separate between user plane network elements.

As shown in FIG. 12, in a 5G communication system, based on the method for determining separation between user plane network elements provided in FIG. 2c, the procedure of the method for determining separation between user plane network elements is as follows:

S1201: The terminal device sends a service request to the access network device, and the access network device receives the service request from the terminal device.

When a terminal device moves within the management area of the SMF, if the terminal device needs to perform a data service, the terminal device initiates a service request procedure.

S1202: The access network device sends N2 information to the AMF, and the AMF receives N2 information from the access network device.

N2 information carries service requests.

S1203: AMF selects SMF.

When the terminal device moves out of the service area of the SMF, the AMF determines that the terminal device has moved out of the management area of the original SMF based on the access area of the terminal device, and the AMF selects to insert an I-SMF based on the access area of the terminal device.

S1204: The AMF sends a PDU session creation context request (Nsmf_PDUSession_CreateSMContext Request) to the I-SMF, and the I-SMF receives the PDU session creation context request from the AMF.

S1205: I-SMF and SMF transfer PDU session context.

S1206: I-SMF and I-UPF establish an N4 session.

The I-SMF selects an I-UPF for relaying. The I-SMF selects an I-UPF in the new area to interact with the wireless network in the new area.

S1207: The I-SMF sends a PDU session creation request (Nsmf_PDUSession_Create Request) message to the SMF.

The Nsmf_PDUSession_Create Request message may carry a private information element indicating the node identifier of the I-UPF.

Alternatively, the Nsmf_PDUSession_Create Request message may carry the N16a interface address of the I-SMF. For example, the N16a interface address of the I-SMF may be carried in the ismfPduSessionUri information element in the PDU Session Create Request message. Alternatively, the Nsmf_PDUSession_Create Request message may carry the node identifier of the I-SMF, for example, the ismId. The ismId may be the I-SMF NfInstanceId in the 3GPP 29.502 protocol.

S1208: SMF and PSA-UPF perform the N4 session modification procedure.

S1209: The SMF sends a PDU session create response (Nsmf_PDUSession_Create Response) message to the I-SMF.

The PDU Session Create Response (Nsmf_PDUSession_Create Response) message sent by the SMF to the I-SMF carries a private information element indicating the node identifier of the PSA-UPF.

Alternatively, the Nsmf_PDUSession_Create Response message may carry the N16a interface address of the SMF. For example, the N16a interface address of the SMF may be carried in the http message header "Location" in the PDU Session Create Response message. Alternatively, the Nsmf_PDUSession_Create Response message may carry the node identifier of the SMF, for example, smfInstanceId. The smfInstanceId may be the SMF NfInstanceId in the 3GPP 29.502 protocol.

S1210: The SMF or I-SMF determines separation between user plane network elements.

For the determination method by which the SMF or I-SMF determines separation between user plane network elements, please refer to any one of determination methods 1 to 3.

For example, the SMF or I-SMF may perform the separation decision based on the node identifier of the I-UPF and the node identifier of the PSA-UPF. As another example, when separation between user plane gateways is determined in a scenario where a large area range is crossed, the separation between user plane gateways may be determined by separation between control plane gateways. The SMF or I-SMF may determine separation between control plane gateways and further determine separation between user plane gateways based on whether the node identifier of the I-SMF or the node identifier of the SMF is within a pre-set group. Alternatively, the SMF or I-SMF may determine separation between control plane gateways and further determine separation between user plane gateways by determining whether the node identifier of the I-SMF is the same as the node identifier of the SMF by comparison.

In the 5G protocol, when an I-SMF is inserted and the I-SMF and SMF exchange Nsmf_PDUSession_Create Request (ismfId) and Nsmf_PDUSession_Create Response (smfInstanceId) messages, the I-SMF and SMF exchange their node identifiers, i.e., ismfId and smfInstanceId. The I-SMF/SMF can determine whether the control plane gateway is separated by comparing the node identifiers, and can also determine whether the user plane gateway is separated without comparing the interface addresses.

Upon determining that the PSA-UPF has separated from the I-UPF, the SMF or I-SMF may trigger re-establishment of the PDU session of the terminal device.

S1211: The I-SMF sends a PDU session creation context response (Nsmf_PDUSession_CreateSMContextResponse) to the AMF, and the AMF receives the PDU session creation context response.

S1212: The AMF sends an N2 response (N2 request) to the access network device, and the access network device receives the N2 response and responds thereto.

S1213: The AMF sends a PDU session update context request (Nsmf_PDUsession updateSMcontext request) to the I-SMF, and the I-SMF receives the PDU session update context request from the AMF.

S1214: I-SMF and I-UPF perform the N4 session modification request procedure.

S1215: I-SMF and SMF perform PDU session update procedure.

S1216: The I-SMF sends a PDU session update context response (Nsmf_PDUsession updateSMcontext response) to the AMF, and the AMF receives the PDU session update context response.

In the embodiment of FIG. 12, it can be understood that the condition that triggers the decision to separate between user plane network elements is an example. Other conditions may be similar to Xn/N2 handover, causing the insertion of an I-SMF, triggering the SMF/I-SMF to decide to separate between user plane network elements.

As shown in FIG. 13, the following describes the operations performed after the user plane network elements are separated based on the method for determining separation between user plane network elements provided in FIG. 2c, and by using as an example a scenario in which the I-UPF is inserted but the I-SMF is not inserted.

S1301: The terminal device and the access network device perform an access network connection release ((R)AN Connection Release) procedure.

S1302: The access network device and the AMF perform the N2 user equipment context release procedure.

The process may include the access network device sending an N2 User Equipment Context Release Request message to the AMF, the AMF sending an N2 User Equipment Context Release Command message to the access network device, and the access network device sending an N2 User Equipment Context Release Complete message to the AMF.

S1303: The AMF sends a PDU session update context request to the SMF, and the SMF receives the PDU session update context request.

S1304: The SMF starts the PDU re-establishment timer.

S1305: SMF and PSA-UPF/I-UPF perform the N4 session modification procedure.

S1306: The SMF returns a PDU session update context response to the AMF.

S1307: The SMF determines that the PDU re-establishment timer has expired and triggers a PDU session re-establishment procedure in the terminal device.

S1308: The SMF sends an N4 session release request to the PSA-UPF/I-UPF.

S1309: PSA-UPF/I-UPF sends an N4 session release response to SMF.

S1310: The SMF sends a communication N1/N2 message transfer (Namf_Communication_N1N2MessageTransfer) to the AMF.

The N1 SM container includes a PDU Session Release Command, which carries a cause value, which may be a reactivation requested.

S1311: AMF and UE perform PDU session release procedure.

S1312: The AMF sends a PDU session update context request to the SMF.

The PDU session update context request contains an N1 SM container, which carries a PDU session release acknowledgement (ACK) indication.

S1313: The SMF sends a PDU session update context response to the AMF.

S1314: The SMF sends a PDU session context status notification (Nsmf_PDUSession_SMContextStatusNotify) message to the AMF, the PDU session context status notification message carries a release instruction, and the AMF receives and responds to the PDU session context status notification message.

As shown in FIG. 14, the following describes the operations performed after the user plane network elements are separated based on the method for determining separation between user plane network elements provided in FIG. 2c, and by using the scenario in which an I-UPF is inserted and an I-SMF is inserted as an example.

S1401: The terminal device and the access network device perform an access network connection release procedure.

S1402: The access network device and the AMF perform the N2 user equipment context release procedure.

S1403: The AMF sends a PDU session update context request to the I-SMF, and the I-SMF receives the PDU session update context request.

S1404: The I-SMF starts the PDU re-establishment timer.

S1405: I-SMF and I-UPF perform the N4 session modification procedure.

The I-SMF instructs the I-UPF to delete the N3 tunnel information.

S1406: The I-SMF returns a PDU session update context response to the AMF.

S1407: The I-SMF determines that the PDU re-establishment timer has expired and triggers a PDU session re-establishment procedure in the terminal device.

S1408: I-SMF and I-UPF perform the N4 session modification procedure.

The I-SMF instructs the I-UPF to stop transferring data.

S1409: I-SMF sends an N4 session release request (Nsmf_PDUSession_Release Request) to the SMF.

S1410: SMF and PSA-UPF perform the N4 session release procedure.

S1411: The SMF sends an N4 session release response (Nsmf_PDUSession_Release Response) to the I-SMF.

S1412: I-SMF and I-UPF perform the N4 session release procedure.

S1413: I-SMF sends communication N1/N2 message transfer (Namf_Communication_N1N2MessageTransfer) to AMF.

The N1 SM container contains a PDU Session Release Command, which carries a cause value, which is Reactivation requested.

S1414: The AMF and UE perform the PDU session release procedure.

S1415: The AMF sends a PDU session update context request to the I-SMF.

The PDU session update context request contains an N1 SM container, which carries a PDU session release acknowledgement (ACK) indication.

S1416: I-SMF sends a PDU session update context response to AMF.

S1417: The I-SMF sends a PDU session context status notification (Nsmf_PDUSession_SMContextStatusNotify) message to the AMF, the PDU session context status notification message carries a release instruction, and the AMF receives the notification message and responds to it.

As shown in FIG. 15, the following describes the operations performed after the user plane network element is separated based on the method for determining separation between user plane network elements provided in FIG. 2c, and by using the scenario in which an I-SMF is inserted as an example.

S1501: The SMF initiates re-establishment of a PDU session of a terminal device when it determines that the terminal device has no traffic within a specified time.

S1502: SMF and PSA-UPF perform the N4 session modification procedure.

S1503: The SMF sends a PDU session update request (Nsmf_PDUSession_Update Request) to the I-SMF.

S1504: I-SMF and I-UPF perform the N4 session release procedure.

S1505: I-SMF sends communication N1/N2 message transfer (Namf_Communication_N1N2MessageTransfer) to AMF.

The N1 SM container contains a PDU Session Release Command, which carries a cause value, which is Reactivation requested.

S1506: The AMF and UE perform the PDU session release procedure.

S1507: The AMF sends a PDU session update context request to the I-SMF.

The PDU session update context request contains an N1 SM container, which carries a PDU session release acknowledgement (ACK) indication.

S1508: I-SMF sends a PDU session update context response to AMF.

S1509: I-SMF sends a PDU session update response to the SMF.

S1510: SMF and PSA-UPF perform the N4 session release procedure.

S1511: The SMF sends a PDU session status notification (Nsmf_PDUSession_StatusNotify) message to the I-SMF, and the PDU session status notification message carries a release instruction.

S1512: The I-SMF sends a PDU session context status notification (Nsmf_PDUSession_SMContextStatusNotify) message to the AMF, and the PDU session context status notification carries a release instruction.

The following further describes in detail how to determine separation between user plane network elements in scenarios where large area ranges are crossed in a 5G communication system.

As shown in FIG. 16, the procedure of the method for determining isolation between user plane network elements is as follows: The method is performed by the I-SMF.

S1601: The I-SMF obtains the address of the first SMF.

S1602: The I-SMF determines, based on the address of the first SMF and the preset address, whether the I-UPF has dissociated from the first PSA-UPF or whether to initiate re-establishment of a PDU session of the terminal device.

The preset address includes the addresses of one or more SMFs located within the same area as the I-SMF, where the first PSA-UPF is a user plane anchor for the terminal device and the first SMF is a control plane anchor for the terminal device.

If the I-SMF determines, based on the address of the first SMF and the preset address, that the I-UPF has disassociated from the first PSA-UPF, the I-SMF may trigger re-establishment of a PDU session of the terminal device.

Alternatively, the I-SMF may determine whether to re-establish a PDU session for the terminal device based on the address of the first SMF and the preset address.

Optionally, if the preset address includes the address of the first SMF, the I-SMF determines that the I-UPF has not disassociated from the first PSA-UPF or that re-establishment of the PDU session does not need to be initiated.

If the preset address does not include the address of the first SMF, the I-SMF determines that the I-UPF has dissociated from the first PSA-UPF or decides to initiate re-establishment of the PDU session of the terminal device.

In the embodiment of FIG. 16, in a scenario where the management area of a control plane network element spans between the I-UPF and the PSA-UPF, it can be determined whether the user plane network element is isolated. In this scenario, the determination is performed by using the embodiment of FIG. 16, so the determination granularity is large. In solution B, when the I-SMF determines that the control plane network element is isolated, the I-SMF determines that the user plane network element is isolated. For example, the I-SMF compares the address of the SMF with the address of the local SMF. If the I-SMF determines that the address of the SMF is different from the address of the local SMF, the I-SMF considers the user plane network element to be isolated as well, since it determines that the SMF and the I-SMF are not in the same control plane network element node. Compared to solution B, in the embodiment of FIG. 16, the decision granularity is larger, so the consequences of the decision to separate between user planes can be reduced, and the actions performed after it is determined that the user planes are separate, e.g., PDU session re-establishment, can be further reduced to reduce signaling overhead.

Similar to the technical concept of the embodiment of FIG. 16, the embodiment of the present application further provides a method for determining isolation between user plane network elements. As shown in FIG. 17, the procedure of the method for determining isolation between user plane network elements is as follows: the method is performed by an SMF, and the SMF and the first I-SMF are located in different control plane network element nodes.

S1701: The SMF obtains the address of the first I-SMF.

S1702: The SMF determines whether the PSA-UPF has dissociated from the first I-UPF or whether to initiate re-establishment of a PDU session of the terminal device based on the address of the first I-SMF and the preset address. For ease of description, the preset address of the embodiment of FIG. 17 may be referred to as the third preset address.

The third preset address includes the addresses of one or more I-SMFs located within the same area as the SMF.

The PSA-UPF is the user plane anchor for the terminal device, and the SMF address is the control plane anchor for the terminal device.

If the SMF determines, based on the address of the first I-SMF and the preset address, that the PSA-UPF has disassociated from the first I-UPF, the SMF may trigger re-establishment of the PDU session of the terminal device.

Alternatively, the SMF may determine whether to re-establish a PDU session for the terminal device based on the address of the first I-SMF and the preset address.

Optionally, if the preset address includes the address of the first I-SMF, the SMF determines that the PSA-UPF has not disassociated from the first I-UPF or that re-establishment of the PDU session does not need to be initiated.

If the preset address does not include the address of the first I-SMF, the SMF determines that the PSA-UPF has dissociated from the first I-UPF or decides to initiate a re-establishment of the PDU session of the terminal device.

For the advantageous effects provided by the embodiment of FIG. 17, please refer to the description of the embodiment of FIG. 16.

To implement the functions in the aforementioned embodiments, it can be understood that the first control plane network element, SGW-C, or PGW-C includes corresponding hardware structures and/or software modules for performing each function. Those skilled in the art should easily realize that the present application can be implemented by using hardware or a combination of hardware and computer software by combining the units and method steps in the examples described in the embodiments disclosed in the present application. Whether the functions are implemented by using hardware or hardware driven by computer software depends on the specific application scenario and design constraints of the technical solution.

Figures 18 and 19 are schematic diagrams of possible communication device structures according to the embodiments of the present application, respectively. The communication device may be configured to implement the functions of the first control plane network element, SGW-C, PGW-C, I-SMF, or SMF in the above-mentioned method embodiments, so that the advantageous effects of the above-mentioned method embodiments can also be implemented. In this embodiment of the present application, the communication device may be the SGW-C shown in Figure 1a, or may be the PGW-C shown in Figure 1a. The communication device may be a module (e.g., a chip) applied to the SGW-C or PGW-C. The communication device may be the SMF shown in Figure 1b. The communication device may be a module (e.g., a chip) applied to the SMF.

As shown in FIG. 18, the communication device 1800 includes an obtaining unit 1810 and a determining unit 1820. The communication device 1800 is configured to perform the functions of the first control plane network element in the embodiment of the method shown in FIG. 2a, FIG. 2b, or FIG. 2c, or to perform the functions of the SGW-C in the embodiment of the method shown in FIG. 8, or to perform the functions of the PGW-C in the embodiment of the method shown in FIG. 10, or to perform the functions of the I-SMF in the embodiment of the method shown in FIG. 16, or to perform the functions of the SMF in the embodiment of the method shown in FIG. 17.

When the communication device 1800 is configured to perform the function of a first control plane network element in the embodiment of the method shown in FIG. 2a, the obtaining unit 1810 is configured to obtain a first node identifier of the first user plane network element and a second node identifier of the second user plane network element, and the device includes a serving gateway for control plane SGW-C, a data network PDN gateway for control plane PGW-C, a session management function SMF, or an intermediate session management function I-SMF, and the first user plane network element is a user plane anchor;
The determining unit 1820 is configured to determine whether the first user plane network element is isolated from the second user plane network element based on the first node identifier and the second node identifier.

Optionally, when obtaining the first node identifier of the first user plane network element, the obtaining unit 1810 is configured to obtain the first node identifier of the first user plane network element from the second control plane network element, where the device is an SGW-C and the first user plane network element is a first user plane data network PDN gateway PGW-U, or the device is a PGW-C and the first user plane network element is a first user plane serving gateway SGW-U, or the device is an SMF and the first user plane network element is an intermediate user plane management function I-UPF, or the device is an I-SMF and the first user plane network element is a protocol data unit session anchor user plane management function PSA-UPF.

Optionally, when determining whether the first user plane network element is detached from the second user plane network element based on the first node identifier and the second node identifier, the determination unit 1820 is configured to: determine that the first user plane network element is not detached from the second user plane network element if the first node identifier is the same as the second node identifier; or determine that the first user plane network element is detached from the second user plane network element if the first node identifier is different from the second node identifier.

Optionally, when determining whether the first user plane network element is disjoint from the second user plane network element based on the first node identifier and the second node identifier, the determining unit 1820 is configured to determine that the first user plane network element is not disjoint from the second user plane network element if the first information in the first node identifier is the same as the second information in the second node identifier, or to determine that the first user plane network element is disjoint from the second user plane network element if the first information in the first node identifier is different from the second information in the second node identifier, the first information indicating an area in which the first user plane network element is located and the second information indicating an area in which the second user plane network element is located.

Optionally, when determining whether the first user plane network element is disjoint from the second user plane network element based on the first node identifier and the second node identifier, the determining unit 1820 is configured to: determine that the first user plane network element is not disjoint from the second user plane network element if the first node identifier and the second node identifier are in the same group; or determine that the first user plane network element is disjoint from the second user plane network element if the first node identifier and the second node identifier are not in the same group.

Optionally, the communication device 1800 further includes a re-establishment unit 1830 configured to initiate re-establishment of a data transmission path of the terminal device when the determination unit determines that the first user plane network element is separated from the second user plane network element.

Optionally, the communication device 1800 is an SGW-C. When initiating re-establishment of a data transmission path for a terminal device, the re-establishment unit 1830 is configured to initiate re-establishment of a packet data network PDN connection to the terminal device when the S1 connection to the terminal device is released.

Optionally, the communication device 1800 is an I-SMF. When initiating re-establishment of a data transmission path of the terminal device, the re-establishment unit 1830 is configured to initiate re-establishment of a protocol data unit PDU session of the terminal device when the N1/N2 connection to the terminal device is released.

Optionally, the communication device 1800 is a PGW-C or an SMF. When initiating re-establishment of a data transmission path of a terminal device, the re-establishment unit 1830 is configured to initiate re-establishment of a data transmission path of the terminal device when the terminal device has no traffic within a specified time.

When the communication device 1800 is configured to perform the functions of the first control plane network element in the embodiment of the method shown in FIG. 2b, the obtaining unit 1810 is configured to obtain a first node identifier of the first user plane data network PDN gateway PGW-U and a second node identifier of the first user plane serving gateway SGW-U, and the determining unit 1820 is configured to determine whether the first SGW-U is detached from the first PGW-U based on the first node identifier and the second node identifier.

Optionally, the first control plane network element is an SGW-C. When acquiring the first node identifier of the first PGW-U, the acquiring unit 1810 is configured to acquire the first node identifier of the first PGW-U from the PGW-C, where the PGW-C is a control plane anchor for the terminal device to access the PDN.

Optionally, the first control plane network element is a PGW-C, which is a control plane anchor for a terminal device to access the PDN. When obtaining the second node identifier of the first SGW-U, the obtaining unit 1810 is configured to obtain the second node identifier of the first SGW-U from the SGW-C.

Optionally, when determining whether the first SGW-U has detached from the first PGW-U based on the first node identifier and the second node identifier, the determination unit 1820 is configured to determine that the first SGW-U has not detached from the first PGW-U if the first node identifier is the same as the second node identifier, or to determine that the first SGW-U has detached from the first PGW-U if the first node identifier is different from the second node identifier.

Optionally, when determining whether the first SGW-U is detached from the first PGW-U based on the first node identifier and the second node identifier, the determination unit 1820 is configured to determine that the first SGW-U is not detached from the first PGW-U if the first information in the first node identifier is the same as the second information in the second node identifier, or to determine that the first SGW-U is detached from the first PGW-U if the first information in the first node identifier is different from the second information in the second node identifier, the first information indicating an area in which the first SGW-U is located and the second information indicating an area in which the first PGW-U is located.

Optionally, when determining whether the first SGW-U is detached from the first PGW-U based on the first node identifier and the second node identifier, the determining unit 1820 is configured to determine that the first SGW-U is not detached from the first PGW-U if the first node identifier and the second node identifier are in the same group, or to determine that the first SGW-U is detached from the first PGW-U if the first node identifier and the second node identifier are not in the same group, and the SGW-U and PGW-U in the group are located in the same area.

Optionally, the apparatus 1800 further includes a re-establishment unit 1830 configured to initiate re-establishment of a PDN connection to the terminal device when the determination unit 1820 determines that the first SGW-U is detached from the first PGW-U.

In a possible design, the first control plane network element is an SGW-C. When initiating re-establishment of a PDN connection to the terminal device, the re-establishment unit is configured to initiate re-establishment of a PDN connection to the terminal device when the S1 connection to the terminal device is released.

In a possible design, the first control plane network element is a PGW-C. When initiating re-establishment of a PDN connection to a terminal device, the re-establishment unit is configured to initiate re-establishment of the PDN connection of the terminal device when the terminal device has no traffic within a specified time.

When the communication device 1800 is configured to perform the function of the SGW-C in the embodiment of the method shown in FIG. 8, the acquisition unit 1810 is configured to acquire the address of the first PGW-C, and the determination unit 1820 is configured to determine whether the serving gateway for the user plane SGW-U is disassociated from the first PGW-U based on the address of the first PGW-C and the preset address, or the determination unit 1820 is configured to determine whether the PDN connection of the terminal device should be re-established based on the address of the first PGW-C and the preset address, the preset address includes the address of one or more PGW-C located in the same area as the SGW-C, the first PGW-U is a user plane anchor for the terminal device to access the PDN, and the first PGW-C is a control plane anchor for the terminal device to access the PDN.

Optionally, when determining whether the serving gateway for user plane SGW-U is detached from the first PGW-U based on the address of the first PGW-C and the preset address, the determination unit 1820 is specifically configured to determine that for the SGW-C, the SGW-U is not detached from the first PGW-U if the preset address includes the address of the first PGW-C, or to determine that for the SGW-C, the SGW-U is detached from the first PGW-U if the preset address does not include the address of the first PGW-C.

Optionally, the apparatus 1800 further includes a re-establishment unit 1830 configured to initiate re-establishment of a PDN connection to the terminal device when the determination unit 1820 determines that the SGW-U is detached from the first PGW-U.

Optionally, the re-establishment unit 1830 is further configured to initiate re-establishment of a PDN connection to the terminal device when the S1 connection to the terminal device is released.

Optionally, the re-establishment unit 1830 may be further configured to start a timer when the S1 connection to the terminal device is released and to initiate re-establishment of the PDN connection to the terminal device after the timer has elapsed.

When the communication device 1800 is configured to perform the functions of the PGW-C in the embodiment of the method shown in FIG. 10, the acquisition unit 1810 is configured to acquire an address of a first SGW-C, and the determination unit 1820 is configured to determine whether the PGW-U is disjoint from a first user plane serving gateway SGW-U based on the address of the first SGW-C and the preset address, where the preset address includes addresses of one or more SGW-Cs located in the same area as the PGW-C, the PGW-U is a user plane anchor for terminal devices to access the PDN, and the PGW-C is a control plane anchor for terminal devices to access the PDN.

Optionally, when determining whether the PGW-U is detached from the first user plane serving gateway SGW-U based on the address of the first SGW-C and the preset address, the determination unit 1820 is specifically configured to determine that for the PGW-C, the PGW-U is not detached from the first SGW-U if the preset address includes the address of the first SGW-C, or to determine that for the PGW-C, the PGW-U is detached from the first SGW-U if the preset address does not include the address of the first SGW-C.

Optionally, the apparatus 1800 further includes a re-establishment unit 1830 configured to initiate re-establishment of a PDN connection to the terminal device when the determination unit determines that the PGW-U is detached from the first SGW-U.

Optionally, the re-establishment unit 1830 may be further configured to initiate re-establishment of a PDN connection to the terminal device when the terminal device has no traffic within a specified time.

Optionally, the re-establishment unit 1830 may be further configured to start a timer if the terminal device has no traffic within a specified time and to initiate re-establishment of the PDN connection to the terminal device after the timer has elapsed.

When the communication device 1800 is configured to perform the functions of the I-SMF in the embodiment of the method shown in FIG. 16, the acquisition unit 1810 is configured to acquire an address of a first SMF, and the determination unit 1820 is configured to determine whether the I-UPF has dissociated from the first PSA-UPF or whether re-establishment of a PDU session of the terminal device should be initiated based on the address of the first SMF and the preset address, where the preset address includes addresses of one or more SMFs located in the same area as the I-SMF, the first PSA-UPF is a user plane anchor of the terminal device, and the first SMF is a control plane anchor of the terminal device.

In a possible design, the communication device 1800 further includes a re-establishment unit 1830. The re-establishment unit 1830 is configured to trigger re-establishment of a PDU session of the terminal device when the determination unit determines, based on the address of the first SMF and the preset address, that the I-UPF is dissociated from the first PSA-UPF.

In a possible design, when determining whether the I-UPF is detached from the first PSA-UPF based on the address of the first SMF and the preset address, the determination unit 1820 is specifically configured to determine that, for the I-SMF, the I-UPF is not detached from the first PSA-UPF if the preset address includes the address of the first SMF, or to determine that, for the I-SMF, the I-UPF is detached from the first PSA-UPF if the preset address does not include the address of the first SMF.

Optionally, the re-establishment unit 1830 may be configured to initiate a re-establishment of the PDU session of the terminal device when the N1/N2 connection to the terminal device is released, based on when the determination unit determines that the I-UPF is dissociated from the first PSA-UPF based on the address of the first SMF and the preset address, and the re-establishment unit may trigger a re-establishment of the PDU session of the terminal device. Further, optionally, the re-establishment unit 1830 may be further configured to start a timer when the N1/N2 connection to the terminal device is released, and to initiate a re-establishment of the PDU session of the terminal device after the timer has elapsed.

When the communication device 1800 is configured to perform the functions of the SMF in the embodiment of the method shown in FIG. 17, the acquisition unit 1810 is configured to acquire an address of the first I-SMF, and the determination unit 1820 is configured to determine whether the PSA-UPF has dissociated from the first I-UPF or whether re-establishment of a PDU session of the terminal device should be initiated based on the address of the first I-SMF and the preset address, where the preset address includes addresses of one or more I-SMFs located in the same area as the SMF, and the PSA-UPF may be a user plane anchor of the terminal device, and the SMF may be a control plane anchor of the terminal device.

In a possible design, when determining whether the PSA-UPF is detached from the first I-UPF based on the address of the first I-SMF and the preset address, the determination unit 1820 is specifically configured to determine that the PSA-UPF is not detached from the first I-UPF if the preset address includes the address of the first I-SMF, or to determine that the PSA-UPF is detached from the first I-UPF for the SMF if the preset address does not include the address of the first I-SMF.

In a possible design, the communication device 1800 further includes a re-establishment unit 1830 configured to initiate re-establishment of a PDU session of the terminal device when the determination unit determines that the PSA-UPF is separated from the first I-UPF.

Optionally, the re-establishment unit 1830 may be further configured to initiate re-establishment of the PDU session of the terminal device when the terminal device has no traffic within a specified time, based on when the re-establishment unit initiates re-establishment of the PDU session of the terminal device when the determination unit determines that the PSA-UPF is separated from the first I-UPF.

For further detailed descriptions of the acquisition unit 1810, the determination unit 1820, and the re-establishment unit 1830, please directly refer to the relevant descriptions in the above method embodiments. The details will not be described again here. The acquisition unit 1810, the determination unit 1820, and the re-establishment unit 1830 may further perform steps in other method embodiments.

As shown in FIG. 19, the communication device 1900 includes a processor 1910 and may optionally further include an interface circuit 1920. The processor 1910 and the interface circuit 1920 are coupled to each other. The interface circuit 1920 may be a transceiver or an input/output interface. Optionally, the communication device 1900 may further include a memory 1930 configured to store instructions to be executed by the processor 1910, or to store input data required to execute the instructions by the processor 1910, or to store data generated after the processor 1910 executes the instructions.

When the communication device 1900 is configured to perform the method shown in FIG. 2a, FIG. 2b, FIG. 2c, FIG. 8, FIG. 10, FIG. 16 or FIG. 17, the processor 1910 may be configured to perform the functions of the acquisition unit 1810, the determination unit 1820 and/or the re-establishment unit 1830, and the interface circuit 1920 may be configured to perform some of the functions of the acquisition unit 1810.

When the communication device is a chip applied to a first control plane network element, the chip of the first control plane network element performs the functions of the first control plane network element in the embodiment of the aforementioned method.

When the communication device is a chip applied to a PGW-C or SGW-C, the chip of the PGW-C or SGW-C performs the functions of the PGW-C or SGW-C in the above-mentioned method embodiments.

When the communication device is a chip applied to I-SMF or SMF, the I-SMF or SMF chip performs the functions of the I-SMF or SMF in the embodiment of the method described above.

The processor in this embodiment of the present application may be a Central Processing Unit (CPU) or other general-purpose processor, a Digital Signal Processor (DSP), an Application-Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, a transistor logic device, a hardware component, or any combination thereof. The general-purpose processor may be a microprocessor, any conventional processor, etc.

In the present embodiment, the memory may be a non-volatile memory, such as a hard disk drive (HDD) or solid-state drive (SSD), or a volatile memory, such as a random access memory (RAM). The memory may be any other medium capable of carrying or storing the expected program code in the form of instructions or data structures and accessible by a computer, but is not limited thereto. The memory in the present embodiment may alternatively be a circuit or any other device capable of implementing a storage function and configured to store program instructions and/or data.

Some or all of the operations and functions performed by the first control plane network element, PGW-C, SGW-C, I-SMF, or SMF described in the above method embodiments of the present application may be implemented by using chips or integrated circuits.

Embodiments of the present application further provide a chip including a processor configured to support a communications device in performing the functions of the first control plane network element, PGW-C, SGW-C, I-SMF, or SMF in the embodiments of the method described above. In a possible design, the chip is connected to or includes a memory, the memory being configured to store program instructions and data required by the communications device.

An embodiment of the present application provides a computer-readable storage medium storing a computer program. The computer program includes instructions used to execute an embodiment of the method described above.

Embodiments of the present application provide a computer program product that includes instructions. When the computer program product is executed on a computer, the aforementioned method embodiments are performed.

Those skilled in the art should understand that the embodiments of the present application may be provided as a method, a system, or a computer program product. Thus, the present application may take the form of a hardware-only embodiment, a software-only embodiment, or an embodiment that combines software and hardware. Furthermore, the present application may take the form of a computer program product embodied in one or more computer usable storage media (including, but not limited to, disk memory, CD-ROM, optical memory, etc.) that contains program code usable by a computer.

This application is described with reference to flowcharts and/or block diagrams of methods, devices (systems), and computer program products according to embodiments of this application. It should be understood that computer program instructions can be used to implement each process and/or each block in the flowcharts and/or block diagrams, and combinations of processes and/or blocks in the flowcharts and/or block diagrams. These computer program instructions may be provided to a processor of a general purpose computer, a special purpose computer, an embedded processor, or other programmable data processing device to generate a machine, whereby the instructions executed by the processor of the computer or other programmable data processing device generate an apparatus for implementing the specific functions of one or more processes in the flowcharts and/or one or more blocks in the block diagrams.

These computer program instructions may alternatively be stored in a computer readable memory capable of directing a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer readable memory cause an artifact to be generated that includes an instruction apparatus that implements the specific functions of one or more processes in the flowcharts and/or one or more blocks in the block diagrams.

These computer program instructions may alternatively be loaded onto a computer or other programmable data processing device such that a sequence of operations and steps are executed on the computer or other programmable data processing device, thereby generating a computer-implemented process. Thus, the instructions executed on the computer or other programmable data processing device provide steps to implement the specific functions of one or more processes in the flowcharts and/or one or more blocks in the block diagrams.

Although several embodiments of the present application have been described, those skilled in the art may change and modify those embodiments by knowing the basic inventive concept. Therefore, the following claims are intended to be interpreted as covering the embodiments and all changes and modifications that are within the scope of the present application.

It is clear that a person skilled in the art can make various modifications and variations to the embodiments of the present application without departing from the scope of the embodiments of the present application. This application is intended to cover those modifications and variations, provided that they are within the scope of protection claimed by the following claims and their equivalent technologies.

CROSS-REFERENCE TO RELATED APPLICATIONS
This application claims priority to Chinese Patent Application No. 202111356850.1, filed with the State Intellectual Property Office of the People's Republic of China on November 16, 2021, entitled "METHOD FOR DETERMINING SEPARATION BETWEEN USER PLANE NETWORK ELEMENTS AND COMMUNICATION APPARATUS," which is incorporated herein by reference in its entirety.

Claims (32)

A method for determining separation between user plane network elements over which a terminal device roams , any one of the user plane network elements acting as a user plane anchor, comprising:
acquiring, by a first control plane network element, a first node identifier of a first user plane network element and a second node identifier of a second user plane network element, the first control plane network element having a serving gateway for a control plane, a data network gateway for a control plane, a session management function, or an intermediate session management function;
determining, by the first control plane network element, whether the first user plane network element is disassociated from the second user plane network element based on the first node identifier and the second node identifier. Obtaining a first node identifier of a first user plane network element by the first control plane network element comprises obtaining, by the first control plane network element, the first node identifier of the first user plane network element from a second control plane network element;
the first control plane network element is a serving gateway for the control plane, the second control plane network element is a data network gateway for the control plane, and the first user plane network element is a data network gateway for the first user plane; or
the first control plane network element is a data network gateway for the control plane, the second control plane network element is a serving gateway for the control plane, and the first user plane network element is a serving gateway for the first user plane; or
the first control plane network element is the session management function, the second control plane network element is the intermediate session management function, and the first user plane network element is an intermediate user plane management function; or the first control plane network element is the intermediate session management function, the second control plane network element is the session management function, and the first user plane network element is a protocol data unit session anchor user plane management function.
The method of claim 1. determining, by the first control plane network element, whether the first user plane network element is disassociated from the second user plane network element based on the first node identifier and the second node identifier,
determining that the first user plane network element is not disjointed from the second user plane network element if the first node identifier is the same as the second node identifier, or determining that the first user plane network element is disjointed from the second user plane network element if the first node identifier is different from the second node identifier.
The method of claim 1. determining, by the first control plane network element, whether the first user plane network element is disassociated from the second user plane network element based on the first node identifier and the second node identifier,
determining that the first user plane network element is not disjointed from the second user plane network element if first information in the first node identifier is the same as second information in the second node identifier, or determining that the first user plane network element is disjointed from the second user plane network element if first information in the first node identifier differs from second information in the second node identifier;
The first information indicates an area in which the first user plane network element is located, and the second information indicates an area in which the second user plane network element is located.
The method of claim 1. determining, by the first control plane network element, whether the first user plane network element is disassociated from the second user plane network element based on the first node identifier and the second node identifier,
determining that the first user plane network element is not disjoint from the second user plane network element if the first node identifier and the second node identifier are in the same group, or determining that the first user plane network element is disjoint from the second user plane network element if the first node identifier and the second node identifier are not in the same group.
The method of claim 1. The method comprises:
and initiating, by the first control plane network element, a re-establishment of a data transmission path of the terminal device when the first control plane network element determines that the first user plane network element is isolated from the second user plane network element.
The method of claim 1. the first control plane network element is a serving gateway for the control plane;
Initiating re-establishment of a data transmission path of the terminal device includes initiating re-establishment of a packet data network (PDN) connection to the terminal device by the control plane serving gateway when an S1 connection to the terminal device is released.
The method according to claim 6. the first control plane network element is the intermediate session management function;
Initiating re-establishment of the data transmission path of the terminal device includes initiating re-establishment of a protocol data unit (PDU) session of the terminal device when an N1/N2 connection to the terminal device is released by the intermediate session management function.
The method according to claim 6. the first control plane network element is the control plane data network gateway or the session management function;
Initiating re-establishment of the data transmission path of the terminal device includes initiating re-establishment of the data transmission path of the terminal device by the control plane data network gateway or the session management function when the terminal device has no traffic within a specified time.
The method according to claim 6. An apparatus for determining separation between user plane network elements over which a terminal device roams , any one of the user plane network elements acting as a user plane anchor, comprising:
An acquisition unit configured to acquire a first node identifier of a first user plane network element and a second node identifier of a second user plane network element, the acquisition unit having a serving gateway for a control plane, a data network gateway for a control plane, a session management function, or an intermediate session management function;
a determining unit configured to determine whether the first user plane network element is disjoint from the second user plane network element based on the first node identifier and the second node identifier. When acquiring the first node identifier of the first user plane network element, the acquiring unit is configured to acquire the first node identifier of the first user plane network element from a second control plane network element;
the device is a serving gateway for the control plane, the second control plane network element is a data network gateway for the control plane, and the first user plane network element is a data network gateway for the first user plane; or
the device is a data network gateway for the control plane, the second control plane network element is a serving gateway for the control plane, and the first user plane network element is a serving gateway for the first user plane; or
the device is the session management function, the second control plane network element is the intermediate session management function, and the first user plane network element is an intermediate user plane management function; or the device is the intermediate session management function, the second control plane network element is the session management function, and the first user plane network element is a protocol data unit session anchor user plane management function.
11. The apparatus of claim 10. When determining whether the first user plane network element is disjoint from the second user plane network element based on the first node identifier and the second node identifier, the determining unit:
determining that the first user plane network element is not disjointed from the second user plane network element if the first node identifier is the same as the second node identifier, or determining that the first user plane network element is disjointed from the second user plane network element if the first node identifier is different from the second node identifier.
11. The apparatus of claim 10. When determining whether the first user plane network element is disjoint from the second user plane network element based on the first node identifier and the second node identifier, the determining unit:
determining that the first user plane network element is not disjointed from the second user plane network element if first information in the first node identifier is the same as second information in the second node identifier, or determining that the first user plane network element is disjointed from the second user plane network element if the first information in the first node identifier is different from the second information in the second node identifier;
The first information indicates an area in which the first user plane network element is located, and the second information indicates an area in which the second user plane network element is located.
11. The apparatus of claim 10. When determining whether the first user plane network element is disjoint from the second user plane network element based on the first node identifier and the second node identifier, the determining unit:
determining that the first user plane network element is not disjointed from the second user plane network element if the first node identifier and the second node identifier are in the same group, or determining that the first user plane network element is disjointed from the second user plane network element if the first node identifier and the second node identifier are not in the same group.
11. The apparatus of claim 10. The apparatus comprises:
a re-establishment unit configured to initiate a re-establishment of a data transmission path of the terminal device when the determining unit determines that the first user plane network element is separated from the second user plane network element.
11. The apparatus of claim 10. the device is a serving gateway for the control plane;
When initiating re-establishment of the data transmission path of the terminal device, the re-establishment unit is configured to initiate re-establishment of a packet data network (PDN) connection to the terminal device when an S1 connection to the terminal device is released;
16. The apparatus of claim 15. the apparatus is the intermediate session management function;
When initiating re-establishment of the data transmission path of the terminal device, the re-establishment unit is configured to initiate re-establishment of a protocol data unit (PDU) session of the terminal device when an N1/N2 connection to the terminal device is released;
16. The apparatus of claim 15. the device is the control plane data network gateway or the session management function;
When initiating re-establishment of the data transmission path of the terminal device, the re-establishment unit is configured to initiate re-establishment of the data transmission path of the terminal device when the terminal device has no traffic within a specified time.
16. The apparatus of claim 15. 1. A method for determining isolation between user plane network elements, comprising:
obtaining, by a control plane serving gateway, an address of a first control plane data network gateway;
determining, by the control plane serving gateway, whether a user plane serving gateway is disjoint from a first user plane data network gateway based on the address of the first control plane data network gateway and a preset address, the preset address including addresses of one or more control plane data network gateways located in the same area as the control plane serving gateway, the first user plane data network gateway being a user plane anchor for a terminal device to access a PDN, and the first control plane data network gateway being a control plane anchor for the terminal device to access the PDN. determining, by the control plane serving gateway, whether a user plane serving gateway is disassociated from a first user plane data network gateway based on the address and a preset address of the first control plane data network gateway;
determining, by the control plane serving gateway, that the user plane serving gateway is not disjoint from the first user plane data network gateway if the preset address has the address of the first control plane data network gateway, or determining, by the control plane serving gateway, that the user plane serving gateway is disjoint from the first user plane data network gateway if the preset address does not have the address of the first control plane data network gateway.
20. The method of claim 19. The method comprises:
and initiating, by the control plane serving gateway, a re-establishment of a PDN connection to the terminal device when the control plane serving gateway determines that the user plane serving gateway is disassociated from the first user plane data network gateway.
20. The method of claim 19. Initiating re-establishment of a PDN connection to the terminal device includes initiating re-establishment of the PDN connection to the terminal device by the control plane serving gateway when an S1 connection to the terminal device is released.
22. The method of claim 21. 1. A method for determining isolation between user plane network elements, comprising:
obtaining, by the intermediate session management function, an address of the first session management function;
determining, by the intermediate session management function, whether the intermediate user plane management function is disjoint from a first protocol data unit session anchor user plane management function based on the address of the first session management function and a preset address, the preset address including addresses of one or more session management functions located in the same area as the intermediate session management function, the first protocol data unit session anchor user plane management function being a user plane anchor for a terminal device and the first session management function being a control plane anchor for the terminal device. determining, by the intermediate session management function, based on the address of the first session management function and a preset address, whether an intermediate user plane management function is disassociated from a first protocol data unit session anchor user plane management function;
determining, by the intermediate session management function, if the preset address comprises the address of the first session management function, that the intermediate user plane management function is not disjoint from the first protocol data unit session anchor user plane management function, or, if the preset address does not comprise the address of the first session management function, determining, by the intermediate session management function, that the intermediate user plane management function is disjoint from the first protocol data unit session anchor user plane management function.
24. The method of claim 23. If the intermediate session management function determines that the intermediate user plane management function is dissociated from the first protocol data unit session anchor user plane management function, the method further comprises:
and initiating, by the intermediate session management function, a re-establishment of a PDN connection of the terminal device.
24. The method of claim 23. 1. A method for determining isolation between user plane network elements, comprising:
obtaining, by a session management function, an address of a first intermediate session management function;
determining, by the session management function, whether a protocol data unit session anchor user plane management function is disjoint from a first intermediate user plane management function based on the address of the first intermediate session management function and a preset address, the preset address including addresses of one or more intermediate session management functions located in the same area as the session management function, the protocol data unit session anchor user plane management function being a user plane anchor for a terminal device, and the session management function being a control plane anchor for the terminal device. determining, by the session management function, whether a protocol data unit session anchor user plane management function is dissociated from a first intermediate user plane management function based on the address of the first intermediate session management function and a preset address;
determining by the session management function that the protocol data unit session anchor user plane management function is not disjoint from the first intermediate user plane management function if the preset address has the address of the first intermediate session management function, or determining by the session management function that the protocol data unit session anchor user plane management function is disjoint from the first intermediate user plane management function if the preset address does not have the address of the first intermediate session management function.
27. The method of claim 26. If the session management function determines that the protocol data unit session anchor user plane management function is disjoint from the first intermediate user plane management function, the method further comprises:
and initiating, by the session management function, a re-establishment of a PDN connection of the terminal device.
27. The method of claim 26. An apparatus for determining isolation between user plane network elements, comprising:
Apparatus comprising a unit arranged to carry out a method according to any one of claims 19 to 22, or a method according to any one of claims 23 to 25, or a method according to any one of claims 26 to 28. storing computer programs or instructions;
When the computer program or the instructions are executed by a communication device, the method according to any one of claims 1 to 9, or the method according to any one of claims 19 to 22, or the method according to any one of claims 23 to 25, or the method according to any one of claims 26 to 28 is performed.
A computer-readable storage medium. a first control plane network element, a first user plane network element, and a second user plane network element;
- the first control plane network element is configured to perform a method according to any one of claims 1 to 9, or a method according to any one of claims 19 to 22, or a method according to any one of claims 23 to 25, or a method according to any one of claims 26 to 28
Communication systems. at least one processor;
The processor is configured to perform a method according to any one of claims 1 to 9, or a method according to any one of claims 19 to 22, or a method according to any one of claims 23 to 25, or a method according to any one of claims 26 to 28.
Tips.

Images