Patent Description:
As communications technologies quickly develop, a 5th generation (Fifth Generation, <NUM>) mobile communications technology emerges. At an early stage of network deployment, because of insufficient coverage of a <NUM> network, when a location of user equipment (User Equipment, UE) changes, a session of the UE needs to be handed over between the <NUM> network and a 4th generation (Fourth Generation, <NUM>) network.

In the prior art, as shown in <FIG>, when UE accesses a <NUM> system, if a mobility management entity (Mobility Management Entity, MME) determines that the UE can support the <NUM> system and a <NUM> system, the MME selects a co-located session management function network element for the UE to establish a connection. However, in some scenarios, the UE does not need to use a service of a <NUM> network or does not subscribe to a service of a <NUM> network, in other words, the UE supporting the <NUM> system and the <NUM> system has no interworking requirement. Therefore, in this case, the MME does not need to select a co-located session management function network element for the UE. Therefore, a network element is improperly selected in the foregoing case, and relatively heavy load of the co-located session management function network element may be caused.

<NPL>, discloses PGW selection based on UE network capability.

Embodiments of this application provide a network element selection method and apparatus, so that UE that supports a <NUM> system and a <NUM> system and that has no interworking requirement can properly select a network element.

According to a first aspect, this application provides a network element selection method, and the method includes:.

Therefore, the first network element in the first communications system can select a suitable network element as the target session management function network element based on the subscription information of the terminal device, which is also called the third subscription information of the terminal below. Compared with selecting a network element based only on whether the terminal device supports a <NUM> system and a <NUM> system in the prior art, a terminal device that supports the <NUM> system and the <NUM> system and that has no interworking requirement can properly select a network element, and load of a co-located session management function network element can be reduced.

In a possible design, the first communications system is a <NUM> system, the second communications system is a <NUM> system, and the first network element in the first communications system is an MME. The third subscription information of the terminal may be indication information indicating whether a data network identity APN corresponding to the session supports interworking with the <NUM> system (or referred to as a 5GC). Optionally, the indicating whether a data network identity APN corresponding to the session supports interworking with the <NUM> system (or referred to as a 5GC) further includes: The third subscription information of the terminal is indication information indicating whether the data network identity APN corresponding to the session supports interworking with a DNN and a network slice identification S-NSSAI. The determining, by the first network element in the first communications system, a target session management function network element based on a capability of the terminal device and third subscription information of the terminal includes: if the terminal device supports the first communications system and the second communications system, and the third subscription information of the terminal indicates that a data network identity APN corresponding to the session supports interworking with the <NUM> system, selecting, by the MME, a co-located session management function network element as the target session management network element. The co-located session management function network element may be a network element having both a session management capability of the <NUM> system and a session management capability of the <NUM> system, for example, an SMF+PGW-C. Therefore, the MME may select the co-located session management function network element as the target session management function network element for a terminal device having both an interworking capability and an interworking requirement.

In a possible design, the first communications system is a <NUM> system, the second communications system is a <NUM> system, and the first network element in the first communications system is an MME. The third subscription information of the terminal may be indication information indicating whether a data network identity APN corresponding to the session supports interworking with the <NUM> system (or referred to as a 5GC). Optionally, the indicating whether a data network identity APN corresponding to the session supports interworking with the <NUM> system (or referred to as a 5GC) further includes: The third subscription information of the terminal is indication information indicating whether the data network identity APN corresponding to the session supports interworking with a DNN and a network slice identification S-NSSAI. The determining, by the first network element in the first communications system, a target session management function network element based on a capability of the terminal device and third subscription information of the terminal includes: if the terminal device supports the first communications system and the second communications system, and the third subscription information indicates that a data network identity APN of the session does not support interworking with the <NUM> system, skipping, by the MME, selecting a co-located session management function network element as the target session management network element. The skipping, by the MME, selecting a co-located session management function network element as the target session management network element includes: selecting, by the MME as the target session management network element, a session management function network element that is not specially used for interworking. Therefore, the MME may select a session management function network element in the <NUM> system as the target session management network element for a terminal device having an interworking capability but having no interworking requirement (that is, an APN that does not support interworking with <NUM>). In this way, a session requirement can be met, so that load of the co-located session management function network element can be reduced.

In a possible design, the first communications system is a <NUM> system, the second communications system is a <NUM> system, and the first network element in the first communications system is an AMF. The third subscription information of the terminal may be indication information indicating whether a data network identity DNN corresponding to the session supports interworking with the <NUM> system (or referred to as an EPS). Optionally, the indicating whether a data network identity DNN corresponding to the session supports interworking with the <NUM> system (or referred to as an EPS) further includes: The third subscription information of the terminal is indication information indicating whether the data network identity DNN and a network slice identification S-NSSAI that correspond to the session support interworking with <NUM> (or referred to as an EPS). The determining, by the first network element in the first communications system, a target session management function network element based on a capability of the terminal device and third subscription information of the terminal includes: if the terminal device supports the first communications system and the second communications system, and the third subscription information of the terminal indicates that a data network identity DNN corresponding to the session supports interworking with the <NUM> system (or referred to as an EPS), selecting, by the AMF, a co-located session management function network element as the target session management network element. The co-located session management function network element may be a network element having both a session management capability of the <NUM> system and a session management capability of the <NUM> system, for example, an SMF+PGW-C. Therefore, the AMF may select the co-located session management function network element as the target session management function network element for a terminal device having both an interworking capability and an interworking requirement.

In a possible design, the first communications system is a <NUM> system, the second communications system is a <NUM> system, and the first network element in the first communications system is an AMF. The third subscription information of the terminal may be indication information indicating whether a data network identity DNN corresponding to the session supports interworking with the <NUM> system (or referred to as an EPS). Optionally, the indicating whether a data network identity DNN corresponding to the session supports interworking with the <NUM> system (or referred to as an EPS) further includes: The third subscription information of the terminal is indication information indicating whether the data network identity DNN and a network slice identification S-NSSAI that correspond to the session support interworking with <NUM> (or referred to as an EPS). The determining, by the first network element in the first communications system, a target session management function network element based on a capability of the terminal device and third subscription information of the terminal includes: if the terminal device supports the first communications system and the second communications system, and the third subscription information indicates that a data network identity DNN of the session does not support interworking with the <NUM> system, skipping, by the AMF, selecting a co-located session management function network element as the target session management network element. The skipping, by the AMF, selecting a co-located session management function network element as the target session management network element includes: selecting, by the AMF as the target session management network element, a session management function network element that is not specially used for interworking. Therefore, the AMF may select a session management function network element in the <NUM> system as the target session management network element for a terminal device having an interworking capability but having no interworking requirement (that is, a DNN that does not support interworking with <NUM>). In this way, a session requirement can be met, so that load of the co-located session management function network element can be reduced.

In a possible design, the session request message includes instruction information instructing the target session management function network element to select a co-located policy control network element and a co-located charging system, or a policy control network element and a charging system that are in the first communications system. When the first communications system is a <NUM> system, the second communications system is a <NUM> system, and the first network element in the first communications system is an MME, the MME may instruct, by using the second message, a co-located session management function network element to select a policy control network element and a charging system that are in the <NUM> system for a terminal device having an interworking capability but having no interworking requirement (that is, the terminal device does not need to use a service of a <NUM> network or does not subscribe to a service of a <NUM> network), so that load of the co-located policy control network element and load of the co-located charging system can be reduced. When the first communications system is a <NUM> system, the second communications system is a <NUM> system, and the first network element in the first communications system is an AMF, the AMF may instruct, by using the second message, a co-located session management function network element to select a policy control network element and a charging system that are in the <NUM> system for a terminal device having an interworking capability but having no interworking requirement (that is, the terminal device does not need to use a service of a <NUM> network or does not subscribe to a service of a <NUM> network), so that load of the co-located policy control network element and load of the co-located charging system can be reduced.

A second aspect of the present invention discloses a network element selection system, and the network element selection system includes:.

In a possible implementation, the first communications system is a <NUM> system, the second communications system is a <NUM> system, and the network element selection apparatus is an access and mobility management function network element AMF in the <NUM> system; and
the first network element is specifically configured to: if the terminal device supports the first communications system and the second communications system, and the third subscription information of the terminal indicates that a data network identity DNN corresponding to the session supports interworking with the <NUM> system, select a co-located session management function network element as the target session management network element.

In a possible implementation, the first communications system is a <NUM> system, the second communications system is a <NUM> system, and the network element selection apparatus is an access and mobility management function network element AMF in the <NUM> system; and
the first network element is specifically configured to: if the terminal device supports the first communications system and the second communications system, and the third subscription information indicates that a data network identity DNN of the session does not support interworking with the <NUM> system, skip selecting a co-located session management function network element as the target session management network element. Specifically, the skipping selecting a co-located session management function network element as the target session management network element includes: selecting a session management function network element in the <NUM> system as the target session management network element.

In a possible implementation, the first communications system is a <NUM> system, the second communications system is a <NUM> system, and the network element selection apparatus is a mobility management function network element MME in the <NUM> system; and
the first network element is specifically configured to: if the terminal device supports the first communications system and the second communications system, and the third subscription information of the terminal indicates that a data network identity APN corresponding to the session supports interworking with the <NUM> system, select a co-located session management function network element as the target session management network element.

In a possible implementation, the first communications system is a <NUM> system, the second communications system is a <NUM> system, and the network element selection apparatus is a mobility management function network element MME in the <NUM> system; and
the first network element is specifically configured to: if the terminal device supports the first communications system and the second communications system, and the third subscription information indicates that a data network identity APN of the session does not support interworking with the <NUM> system, skip selecting a co-located session management function network element as the target session management network element. Specifically, the skipping selecting a co-located session management function network element as the target session management network element includes: selecting a session management function network element in the <NUM> system as the target session management network element.

According to a third aspect, an embodiment of this application provides a network element selection apparatus, and the apparatus may be a first network element in a first communications system, or may be a chip in a first network element in a first communications system. The apparatus may include a processing unit and a transceiver unit. When the apparatus is the first network element in the first communications system, the processing unit may be a processor, and the transceiver unit may be a transceiver. The first network element in the first communications system may further include a storage unit, and the storage unit may be a memory. The storage unit is configured to store an instruction, and the processing unit executes the instruction stored in the storage unit, so that the first network element in the first communications system performs the method in any one of the first aspect or the possible designs of the first aspect. When the apparatus is the chip in the first network element in the first communications system, the processing unit may be a processor, and the transceiver unit may be an input/output interface, a pin, a circuit, or the like. The processing unit executes an instruction stored in the storage unit, and the storage unit is configured to store the instruction. The storage unit may be a storage unit (for example, a register or a cache) in the chip, or may be a storage unit (for example, a read-only memory or a random access memory) that is located out of the chip and that is in the first network element in the first communications system, so that the first network element in the first communications system performs the method including:.

According to a fourth aspect, an embodiment of this application further provides a computer program product including a program. When the computer program product runs on a computer, the computer is enabled to perform the method including:.

<FIG> is a schematic diagram of a specific application scenario according to an embodiment of this application. It should be understood that <FIG> is only an example and is not used to limit this application.

In an interworking architecture of a <NUM> system and a <NUM> system shown in <FIG>, a <NUM> network and a <NUM> network share a user plane function (User Plane Function, UPF)+packet data network gateway user plane function (Packet Data Network Gateway User Plane Function, PGW-U), a session management function (Session Management Function, SMF)+protocol data unit gateway control plane function (Protocol Data Unit Gateway Control plane function, PGW-C), a policy control function (Policy Control Function, PCF)+policy and charging rules function (Policy and Charging Rules Function, PCRF), and a home subscriber server (Home Subscriber Server, HSS)+unified data management (Unified Data Management, UDM). "+" herein represents co-location, and the "co-location" herein means that one device has functions of two entities. The UPF is a user plane function network element in <NUM>, the PGW-U is a PDU gateway user plane function network element that is in <NUM> and that corresponds to the UPF, and the UPF+PGW-U is a co-located user plane function network element, and has a user plane function of the <NUM> system and a user plane function of the <NUM> system. The SMF is a session management function network element in <NUM>, the PGW-C is a PDU gateway control plane function network element that is in <NUM> and that corresponds to the SMF, and the SMF+PGW-C is a co-located session management function network element, and has a session management capability of the <NUM> system and a session management capability of the <NUM> system. The PCF is a policy and charging rules function network element in <NUM>, the PCRF is a policy control function network element in <NUM>, an offline charging system (online charging system, OCS) and an offline charging system (offline charging system, OFCS) are charging system network elements in <NUM>, and the PCF+PCRF is a co-located policy and charging rules function network element, and has a policy and charging rules function of the <NUM> system and a policy and charging rules function of the <NUM> system. The UDM is configured to manage user data in <NUM>, for example, the user data in <NUM> includes subscription information of a user in <NUM>. The HSS corresponds to the UDM, and is configured to manage user data in <NUM>, for example, the user data in <NUM> includes subscription information of a user in <NUM>. The HSS+UDM is a co-located user data management network element. It should be noted that a next generation radio access network (Next Generation Radio Access Networks, NG-RAN) in <FIG> is an access network device in <NUM>, and an evolved UMTS terrestrial radio access network (Evolved UMTS Terrestrial Radio Access Network, E-UTRAN) is an access network device in <NUM>. In the interworking architecture, an MME communicates with the E-UTRAN by using a serving gateway (Serving Gateway, SGW) and the UPF+PGW-U or by using a serving gateway and the SMF+PGW-C. In addition, the interworking architecture may further include a pure <NUM> network element, for example, may include at least one of the PGW-U, the PGW-C, the PCRF, and the HSS. Likewise, the interworking architecture may further include a pure <NUM> network element, for example, may include at least one of the UPF, the SMF, the PCF, and the UDM.

It should be understood that when UE in the <NUM> system performs access, if an access and mobility management function (Core Access and Mobility Management Function, AMF) determines that the UE can support the <NUM> system and the <NUM> system, the AMF selects a co-located session management function network element for the UE to establish a connection. In some scenarios, the UE does not need to use a service of the <NUM> network or does not subscribe to a service of the <NUM> network. That is, UE supporting the <NUM> system and the <NUM> system may have no interworking requirement. Therefore, in this case, the AMF does not need to select a co-located session management function network element for the UE. Therefore, when the UE in the <NUM> system performs access, a problem that a network element is improperly selected also exists. Therefore, to resolve the problem that a network element is improperly selected, an example of this application provides a network element selection method. As shown in <FIG>, to enable UE that supports a <NUM> system and a <NUM> system and that has no interworking requirement to properly select a network element, the method includes the following steps.

Step <NUM>: A first network element in a first communications system receives a first message sent by a terminal device, where the first message is used to request to establish a session. The first message is used to request to establish a session. In a possible design, the first network element determines, based on a message type or a message name of the first message, that the message is used to request to establish a session. For example, the first message is a PDU session establishment request (PDU Session Establishment Request), or the first message is a PDU connectivity request (PDN Connectivity Request), and the first network element may determine, based on the message name, that the message is used to request to establish a session. Alternatively, the first message is an attach request (Attach Request), and the first network element may determine, based on the message type, that after successfully registering on a network side, the UE needs to request to establish a session.

Step <NUM>: In response to the first message, the first network element in the first communications system determines a target session management function network element based on first subscription information and second subscription information, where the first subscription information includes subscription information of the terminal device in the first communications system, and the second subscription information includes subscription information of the terminal device in a second communications system. In a possible design, the first subscription information may be subscription information corresponding to one or more data network identities of the terminal device in the first communications system. The second subscription information may also be subscription information corresponding to one or more data network identities of the terminal device in the second communications system. In another possible design, the first subscription information may be indication information that indicates whether the terminal device subscribes to a data network identity in the first communications system, and the second subscription information may also be indication information that indicates whether the terminal device subscribes to a data network identity in the second communications system.

The first network element in the first communications system needs to obtain the first subscription information and the second subscription information. In a possible design, before step <NUM>, the first network element in the first communications system sends a third message to a co-located user data management network element, and the third message is used to obtain the first subscription information and the second subscription information. The first network element in the first communications system stores the first subscription information and the second subscription information. Alternatively, the first network element in the first communications system separately queries a user data management network element in the first communications system for the first subscription information, and queries a user data management network element in the second communications system for the second subscription information. Therefore, the first network element in the first communications system may prestore the first subscription information and the second subscription information. In another possible design, after step <NUM>, before step <NUM>, the first network element in the first communications system sends a fourth message to a co-located user data management network element, and the fourth message is used to query the first subscription information and the second subscription information. Alternatively, the first network element in the first communications system separately queries a user data management network element in the first communications system for the first subscription information, and queries a user data management network element in the second communications system for the second subscription information. Therefore, the first network element in the first communications system may query the first subscription information and the second subscription information in real time. It should be understood that the co-located user data management network element may be the HSS+UDM shown in <FIG>. In addition, before obtaining the first subscription information and the second subscription information, the first network element in the first communications system may further determine a data network identity of a current session, then obtain, as the first subscription information, subscription information corresponding to the data network identity of the terminal device in the first communications system, and obtain, as the second subscription information, subscription information corresponding to a data network identity that corresponds to the data network identity and that is of the terminal device in the second communications system.

It should be understood that an order in which the first network element in the first communications system obtains the first subscription information and the second subscription information is not limited in this application. In other words, the first network element may simultaneously obtain the first subscription information and the second subscription information, or may first obtain the first subscription information and then obtain the second subscription information. In a possible design, the first network element in the first communications system first obtains the first subscription information; and if it is determined that the first subscription information exists, the first network element then obtains the second subscription information; or if it is determined that the first subscription information does not exist, the first network element rejects a current session establishment request, and optionally, no longer obtains the second subscription information.

In a possible implementation of step <NUM>, the first network element in the first communications system may determine the target session management function network element based on a capability of the terminal device, the first subscription information, and the second subscription information. Optionally, before step <NUM>, the first network element in the first communications system receives a non-access stratum (Non Access Stratum, NAS) message sent by the terminal device, and the NAS message carries capability information of the terminal device. Alternatively, the first message carries capability information of the terminal device. For example, the capability information of the terminal device includes information about whether the terminal device supports the first communications system and information about whether the terminal device supports the second communications system; or the capability information of the terminal device includes indication information indicating whether the terminal device supports the first communications system and the second communications system. Therefore, the first network element in the first communications system may determine, based on the capability information of the terminal device, whether the terminal device supports the first communications system and the second communications system.

A specific process in which the first network element in the first communications system determines the target session management function network element based on the capability of the terminal device, the first subscription information, and the second subscription information is described below with reference to specific application scenarios.

Scenario <NUM>: The first communications system is a <NUM> system, the second communications system is a <NUM> system, and the first network element in the first communications system is an MME.

The scenario <NUM> may specifically include two possible cases.

In a first possible case, if the terminal device supports the first communications system and the second communications system, and both the first subscription information and the second subscription information include subscription information corresponding to a data network identity of the session, the MME selects a co-located session management function network element as the target session management network element, for example, the SMF+PGW-C shown in <FIG>.

In a second possible case, if the terminal device supports the first communications system and the second communications system, the first subscription information includes subscription information corresponding to a data network identity of the session, and the second subscription information does not include the subscription information corresponding to the data network identity of the session, the MME selects a session management function network element in the <NUM> system as the target session management network element, for example, the PGW-C shown in <FIG>.

In the foregoing two possible cases, the MME needs to determine the target session management network element by using two determining steps. An order of performing the two determining steps is not limited in this application.

One determining step is determining whether the terminal device supports the first communications system and the second communications system. Specifically, the MME may determine, based on the capability information of the terminal device, that the terminal device supports the first communications system and the second communications system.

The other determining step is determining whether both the first subscription information and the second subscription information include the subscription information corresponding to the data network identity of the session.

First, the MME needs to determine the data network identity of the session. When the first communications system is the <NUM> system and the second communications system is the <NUM> system, the data network identity of the session is an access point name (Access Point Name, APN). A specific APN determining manner is not limited in this application. In a possible design, the first message carries the data network identity of the session, and the MME may determine the data network identity of the session based on the first message. In another possible design, the first message does not carry the data network identity, and the MME may determine an APN, for example, a default APN, or determine a configured APN for the session based on a local policy, a local configuration, or the like. The following method of determining the data network identity of the session by the MME is consistent with the method herein. Repeated content is not described again.

In a first implementation, the MME determines or obtains the first subscription information and the second subscription information based on the determined APN. In this case, the first subscription information is subscription information of the APN of the terminal device in the <NUM> system, or may be indication information that indicates whether the terminal device subscribes to the APN. The second subscription information is subscription information of a data network name (Data Network Name, DNN) that corresponds to the APN and that is of the terminal device in the <NUM> system, or may be indication information that indicates whether the terminal device subscribes to the DNN, and the APN corresponds to the DNN. Alternatively, the second subscription information is subscription information of a DNN+single network slice selection assistance information (Single Network Slice Selection Assistance information, S-NSSAI) that corresponds to the APN and that is of the terminal device in the <NUM> system, or may be indication information that indicates whether the terminal device subscribes to the DNN+S-NSSAI, and the APN corresponds to the DNN+S-NSSAI. Specifically, for the first possibility, a manner in which the MME determines that both the first subscription information and the second subscription information include the subscription information corresponding to the data network identity of the session is as follows: The terminal device has the subscription information of the APN in the <NUM> system, and the terminal device has the subscription information of the DNN that corresponds to the APN and that is in the <NUM> system; or the terminal device has the subscription information of the APN in the <NUM> system, and the terminal device has the subscription information of the DNN+S-NSSAI that corresponds to the APN and that is in the <NUM> system. For the second possibility, a manner in which the MME determines that the first subscription information includes the subscription information corresponding to the data network identity of the session, and that the second subscription information does not include the subscription information corresponding to the data network identity of the session is as follows: The terminal device has the subscription information of the APN in the <NUM> system, and the terminal device has no subscription information of the DNN that corresponds to the APN and that is in the <NUM> system; or the terminal device has the subscription information of the APN in the <NUM> system, and the terminal device has no subscription information of the DNN+S-NSSAI that corresponds to the APN and that is in the <NUM> system. It should be noted that the subscription information of the DNN+S-NSSAI in this application is subscription information having a granularity of a DNN plus S-NSSAI. Subscription information of a DNN+S-NSSAI below has a same meaning as the subscription information of the DNN+S-NSSAI herein. Repeated content is not described again.

In a second possible implementation, the MME first obtains all subscription information of the terminal device in the <NUM> system and all subscription information of the terminal device in the <NUM> system. In this case, the first subscription information includes subscription information corresponding to each APN to which the terminal device subscribes in the <NUM> system, and the second subscription information includes subscription information corresponding to each DNN to which the terminal device subscribes in the <NUM> system, or the second subscription information includes subscription information corresponding to each DNN+S-NSSAI to which the terminal device subscribes in the <NUM> system. Specifically, for the first possibility, a manner in which the MME determines that both the first subscription information and the second subscription information include the subscription information corresponding to the data network identity of the session is as follows: The MME determines that the first subscription information includes subscription information corresponding to the APN, and the second subscription information includes subscription information of a DNN corresponding to the APN; or the first subscription information includes subscription information corresponding to the APN, and the second subscription information includes subscription information of a DNN+S-NSSAI corresponding to the APN. For the second possibility, a manner in which the MME determines that the first subscription information includes the subscription information corresponding to the data network identity of the session, and that the second subscription information does not include the subscription information corresponding to the data network identity of the session is as follows: The MME determines that the first subscription information includes subscription information corresponding to the APN, and that the second subscription information does not include subscription information of a DNN corresponding to the APN; or the MME determines that the first subscription information includes subscription information corresponding to the APN, and that the second subscription information does not include subscription information of a DNN+S-NSSAI corresponding to the APN.

In a third possible implementation, the MME first obtains all subscription information of the terminal device in the <NUM> system, and the first subscription information includes subscription information corresponding to each APN to which the terminal device subscribes in the <NUM> system. Then the MME determines or obtains the second subscription information based on the determined APN, and the second subscription information is subscription information of a DNN that corresponds to the APN and that is of the terminal device in the <NUM> system, or may be indication information that indicates whether the terminal device subscribes to the DNN. Alternatively, the second subscription information is subscription information of a DNN+S-NSSAI that corresponds to the APN and that is of the terminal device in the <NUM> system, or may be indication information that indicates whether the terminal device subscribes to the DNN+S-NSSAI. Specifically, for the first possibility, a manner in which the MME determines that both the first subscription information and the second subscription information include the subscription information corresponding to the data network identity of the session is as follows: The first subscription information includes subscription information corresponding to the APN, and the terminal device has the subscription information of the DNN that corresponds to the APN and that is in the <NUM> system; or the first subscription information includes subscription information corresponding to the APN, and the terminal device has the subscription information of the DNN+S-NSSAI that corresponds to the APN and that is in the <NUM> system. For the second possibility, a manner in which the MME determines that the first subscription information includes the subscription information corresponding to the data network identity of the session, and that the second subscription information does not include the subscription information corresponding to the data network identity of the session is as follows: The first subscription information includes subscription information corresponding to the APN, and the terminal device has no subscription information of the DNN that corresponds to the APN and that is in the <NUM> system; or the first subscription information includes subscription information corresponding to the APN, and the terminal device has no subscription information of the DNN+S-NSSAI that corresponds to the APN and that is in the <NUM> system.

It should be understood that subscription information corresponding to all APNs included in the first subscription information is not in a one-to-one correspondence with subscription information of DNNs in the second subscription information, and subscription information of only some APNs is in a one-to-one correspondence with subscription information of DNNs in the <NUM> system. Likewise, subscription information corresponding to all APNs included in the first subscription information is not in a one-to-one correspondence with subscription information of DNNs+S-NSSAI in the second subscription information, and subscription information of only some APNs is in a one-to-one correspondence with subscription information of DNNs+S-NSSAI in the <NUM> system.

In a fourth possible implementation, if the terminal device supports the first communications system and the second communications system, after the MME determines the APN, the MME sends a fifth message to a co-located user data management network element, and the fifth message is used to query whether subscription information corresponding to a DNN corresponding to the APN exists in subscription information corresponding to the APN. The MME receives a query result sent by the co-located user data management network element. If the query result indicates that the subscription information corresponding to the DNN corresponding to the APN exists in the subscription information corresponding to the APN, the MME selects the co-located session management function network element. If the query result indicates that the subscription information corresponding to the DNN corresponding to the APN does not exist in the subscription information corresponding to the APN, the MME selects the session management function network element in the <NUM> system. Alternatively, if the terminal device supports the first communications system and the second communications system, after the MME determines the APN, the MME sends a fifth message to a co-located user data management network element, and the fifth message is used to query whether subscription information corresponding to a DNN+S-NSSAI corresponding to the APN exists in subscription information corresponding to the APN. The MME receives a query result sent by the co-located user data management network element. If the query result indicates that the subscription information corresponding to the DNN+S-NSSAI corresponding to the APN exists in the subscription information corresponding to the APN, the MME selects the co-located session management function network element. If the query result indicates that the subscription information corresponding to the DNN+S-NSSAI corresponding to the APN does not exist in the subscription information corresponding to the APN, the MME selects the session management function network element in the <NUM> system.

In a fifth possible implementation, the MME sends a sixth message to a co-located user data management network element, the sixth message is used to obtain a mapping relationship between an APN and a DNN, and the mapping relationship indicates that subscription information of the APN corresponds to subscription information of a DNN. The MME receives the mapping relationship sent by the co-located user data management network element, and stores the mapping relationship. For example, the MME may send the sixth message to the co-located user data management network element before receiving the first message sent by the terminal device, or the MME may send the sixth message to the co-located user data management network element after receiving the first message sent by the terminal device. After determining the APN, the MME queries the mapping relationship based on the APN. If the mapping relationship indicates that the APN corresponds to a DNN, the MME selects the co-located session management function network element. If the mapping relationship indicates that the APN corresponds to no DNN, the MME selects the session management function network element in the <NUM> system. Likewise, the foregoing design is also applicable to a case in which the APN corresponds to a DNN and S-NSSAI.

For example, the terminal device subscribes to three APNs in the <NUM> system, including an APN <NUM>, an APN <NUM>, and an APN <NUM>, and subscribes to four DNNs in the <NUM> system, including a DNN <NUM>, a DNN <NUM>, a DNN <NUM>, and a DNN <NUM>. The APN <NUM> corresponds to the DNN <NUM>, and the APN <NUM> corresponds to the DNN <NUM>. In this way, the mapping relationship includes a mapping relationship between the APN <NUM> and the DNN <NUM> and a mapping relationship between the APN <NUM> and the DNN <NUM>. If the MME determines the APN <NUM>, the MME queries the mapping relationship based on the APN <NUM> and determines that the APN <NUM> corresponds to no DNN, and the MME selects the session management function network element in the <NUM> system. If the MME determines the APN <NUM>, the MME queries the mapping relationship based on the APN <NUM> and determines that a DNN corresponding to the APN <NUM> is the DNN <NUM>, and the MME selects the co-located session management function network element.

Therefore, in the foregoing possible implementations, the MME may select the co-located session management function network element as the target session management function network element for a terminal device having both an interworking capability and an interworking requirement. The MME may select the session management function network element in the <NUM> system as the target session management network element for a terminal device having an interworking capability but having no interworking requirement (that is, the terminal device does not need to use a service of a <NUM> network or does not subscribe to a service of a <NUM> network). In this way, a session requirement can be met, so that load of a co-located session management function network element can be reduced. Scenario <NUM>: The first communications system is a <NUM> system, the second communications system is a <NUM> system, and the first network element in the first communications system is an AMF.

In a first possible case, if the terminal device supports the first communications system and the second communications system, and both the first subscription information and the second subscription information include subscription information corresponding to a data network identity of the session, the AMF selects a co-located session management function network element as the target session management network element, for example, the SMF+PGW-C shown in <FIG>.

In a second possible case, if the terminal device supports the first communications system and the second communications system, the first subscription information includes subscription information corresponding to a data network identity of the session, and the second subscription information does not include the subscription information corresponding to the data network identity of the session, the AMF selects a session management function network element in the <NUM> system as the target session management network element, and the session management function network element in the <NUM> system is an SMF.

Similar to the scenario <NUM>, in the foregoing two possible cases, the AMF needs to determine the target session management network element by using two determining steps. An order of performing the two determining steps is not limited.

One determining step is determining whether the terminal device supports the first communications system and the second communications system. Specifically, the AMF may determine, based on the capability information of the terminal device, that the terminal device supports the first communications system and the second communications system.

The other determining step is determining, by the AMF, whether both the first subscription information and the second subscription information include the subscription information corresponding to the data network identity of the session.

First, the AMF determines the data network identity of the current session. When the first communications system is the <NUM> system and the second communications system is the <NUM> system, the data network identity of the session is a DNN, or a DNN and S-NSSAI. A specific DNN determining manner or a specific manner of determining the DNN and S-NSSAI is not limited in this application. In a possible design, the first message carries the data network identity of the session, and the AMF may determine the data network identity of the session based on the first message. In another possible design, the first message does not carry the data network identity, and the AMF may determine a DNN, or a DNN and S-NSSAI, for example, a default DNN, or a default DNN and S-NSSAI, or determine a configured DNN or a configured DNN and S-NSSAI for the session based on a local policy, a local configuration, or the like. The following method of determining the data network identity of the session by the AMF is consistent with the method herein. Repeated content is not described again.

In a first implementation, the AMF determines or obtains the first subscription information and the second subscription information based on the determined DNN. In this case, the first subscription information is subscription information of the DNN of the terminal device in the <NUM> system, or may be indication information that indicates whether the terminal device subscribes to the DNN. The second subscription information is subscription information of an APN that corresponds to the DNN and that is of the terminal device in the <NUM> system, and the APN corresponds to the DNN; or the second subscription information is subscription information of an APN that corresponds to the DNN and S-NSSAI and that is of the terminal device in the <NUM> system, and the APN corresponds to the DNN+S-NSSAI, or the second subscription information may be indication information that indicates whether the terminal device subscribes to the APN. Specifically, for the first possibility, a manner in which the AMF determines that both the first subscription information and the second subscription information include the subscription information corresponding to the data network identity of the session is as follows: The terminal device has the subscription information of the DNN in the <NUM> system, and the terminal device has the subscription information of the APN that corresponds to the DNN and that is in the <NUM> system; or the terminal device has subscription information of the DNN+S-NSSAI in the <NUM> system, and the terminal device has the subscription information of the APN that corresponds to the DNN+S-NSSAI and that is in the <NUM> system. For the second possibility, a manner in which the AMF determines that the first subscription information includes the subscription information corresponding to the data network identity of the session, and that the second subscription information does not include the subscription information corresponding to the data network identity of the session is as follows: The terminal device has the subscription information of the DNN in the <NUM> system, and the terminal device has no subscription information of the APN that corresponds to the DNN and that is in the <NUM> system; or the terminal device has subscription information of the DNN+S-NSSAI in the <NUM> system, and the terminal device has no subscription information of the APN that corresponds to the DNN+S-NSSAI and that is in the <NUM> system.

In a second possible implementation, the AMF first obtains all subscription information of the terminal device in the <NUM> system and all subscription information of the terminal device in the <NUM> system. In this case, the first subscription information includes subscription information corresponding to each DNN to which the terminal device subscribes in the <NUM> system, or the first subscription information includes subscription information corresponding to each DNN+S-NSSAI to which the terminal device subscribes in the <NUM> system. The second subscription information includes subscription information of each APN to which the terminal device subscribes in the <NUM> system. Specifically, for the first possibility, a manner in which the AMF determines that both the first subscription information and the second subscription information include the subscription information corresponding to the data network identity of the session is as follows: The AMF determines that the first subscription information includes subscription information corresponding to the DNN, and that the second subscription information includes subscription information of an APN corresponding to the DNN. Alternatively, the AMF determines that the first subscription information includes subscription information corresponding to the DNN+S-NSSAI, and that the second subscription information includes subscription information of an APN corresponding to the DNN+S-NSSAI. For the second possibility, a manner in which the AMF determines that the first subscription information includes the subscription information corresponding to the data network identity of the session, and that the second subscription information does not include the subscription information corresponding to the data network identity of the session is as follows: The AMF determines that the first subscription information includes subscription information corresponding to the DNN, and that the second subscription information does not include subscription information of an APN corresponding to the DNN. Alternatively, the AMF determines that the first subscription information includes subscription information corresponding to the DNN+S-NSSAI, and that the second subscription information does not include subscription information of an APN corresponding to the DNN+S-NSSAI. In a third possible implementation, the AMF first obtains all subscription information of the terminal device in the <NUM> system, and the first subscription information includes subscription information of each DNN to which the terminal device subscribes in the <NUM> system, or the first subscription information includes subscription information corresponding to each DNN+S-NSSAI to which the terminal device subscribes in the <NUM> system. The AMF determines or obtains the second subscription information based on the determined DNN or the determined DNN+S-NSSA, and the second subscription information is subscription information of an APN that corresponds to the DNN or the DNN+S-NSSA and that is of the terminal device in the <NUM> system, or may be indication information that indicates whether the terminal device subscribes to the APN. Specifically, for the first possibility, a manner in which the AMF determines that both the first subscription information and the second subscription information include the subscription information corresponding to the data network identity of the session is as follows: The first subscription information includes subscription information corresponding to the DNN, and the terminal device has subscription information of the APN that corresponds to the DNN and that is in the <NUM> system; or the first subscription information includes subscription information corresponding to the DNN+S-NSSAI, and the terminal device has subscription information of the APN that corresponds to the DNN+S-NSSAI and that is in the <NUM> system. For the second possibility, a manner in which the AMF determines that the first subscription information includes the subscription information corresponding to the data network identity of the session, and that the second subscription information does not include the subscription information corresponding to the data network identity of the session is as follows: The first subscription information includes subscription information corresponding to the DNN, and the terminal device has no subscription information of the APN that corresponds to the DNN and that is in the <NUM> system; or the first subscription information includes subscription information corresponding to the DNN+S-NSSAI, and the terminal device has no subscription information of the APN that corresponds to the DNN+S-NSSAI and that is in the <NUM> system.

It should be understood that subscription information corresponding to all DNNs included in the first subscription information is not in a one-to-one correspondence with subscription information of APNs in the second subscription information, and subscription information of only some DNNs is in a one-to-one correspondence with subscription information of APNs in the <NUM> system. Likewise, subscription information corresponding to all DNNs+S-NSSAI included in the first subscription information is not in a one-to-one correspondence with subscription information of APNs in the second subscription information, and subscription information of only some DNNs+S-NSSAI is in a one-to-one correspondence with subscription information of APNs in the <NUM> system.

In a fourth possible implementation, if the terminal device supports the first communications system and the second communications system, after the AMF determines the DNN, the AMF sends a seventh message to a co-located user data management network element, and the seventh message is used to query whether subscription information corresponding to an APN corresponding to the DNN exists in subscription information corresponding to the DNN. The AMF receives a query result sent by the co-located user data management network element. If the query result indicates that it is determined that the subscription information corresponding to the APN corresponding to the DNN exists, the AMF selects the co-located session management function network element. If the query result indicates that the subscription information corresponding to the APN corresponding to the DNN does not exist in the subscription information corresponding to the DNN, the AMF selects the session management function network element in the <NUM> system. Alternatively, if the terminal device supports the first communications system and the second communications system, after the AMF determines the DNN+S-NSSAI, the AMF sends a seventh message to a co-located user data management network element, and the seventh message is used to query whether subscription information of an APN corresponding to the DNN+S-NSSAI exists in subscription information corresponding to the DNN+S-NSSAI. The AMF receives a query result sent by the co-located user data management network element. If the query result indicates that it is determined that the subscription information corresponding to the APN corresponding to the DNN+S-NSSAI exists, the AMF selects the co-located session management function network element. If the query result indicates that the subscription information corresponding to the APN corresponding to the DNN+S-NSSAI does not exist in the subscription information corresponding to the DNN+S-NSSAI, the AMF selects the session management function network element in the <NUM> system.

In a fifth possible implementation, if the terminal device supports the first communications system and the second communications system, the AMF sends an eighth message to a co-located user data management network element, the eighth message is used to obtain a mapping relationship between a DNN and an APN, and the AMF receives the mapping relationship sent by the co-located user data management network element, and stores the mapping relationship. For example, the AMF may send the eighth message to the co-located user data management network element before receiving the first message sent by the terminal device, or the AMF may send the eighth message to the co-located user data management network element after receiving the first message sent by the terminal device. After determining the DNN, the AMF queries the mapping relationship based on the DNN. If the mapping relationship indicates that the DNN corresponds to an APN, the AMF selects the co-located session management function network element. If the mapping relationship indicates that the DNN corresponds to no APN, the AMF selects the session management function network element in the <NUM> system. Likewise, the foregoing design is also applicable to a case in which the DNN+S-NSSAI corresponds to the APN.

For example, the terminal device subscribes to three APNs in the <NUM> system, including an APN <NUM>, an APN <NUM>, and an APN <NUM>, and subscribes to four DNNs in the <NUM> system, including a DNN <NUM>, a DNN <NUM>, a DNN <NUM>, and a DNN <NUM>. The APN <NUM> corresponds to the DNN <NUM>, and the APN <NUM> corresponds to the DNN <NUM>. In this way, the mapping relationship includes a mapping relationship between the APN <NUM> and the DNN <NUM> and a mapping relationship between the APN <NUM> and the DNN <NUM>. If the AMF determines the DNN <NUM>, the AMF queries the mapping relationship based on the DNN <NUM> and determines that an APN corresponding to the DNN <NUM> is the APN <NUM>, and the AMF selects the co-located session management function network element. If the AMF determines the DNN <NUM>, the AMF queries the mapping relationship based on the DNN <NUM> and determines that the DNN <NUM> corresponds to no APN, and the AMF selects the session management function network element in the <NUM> system.

Therefore, in the foregoing possible implementations, the AMF may select the co-located session management function network element as the target session management function network element for a terminal device having both an interworking capability and an interworking requirement. The AMF may select the session management function network element in the <NUM> system as the target session management network element for a terminal device having an interworking capability but having no interworking requirement (that is, the terminal device does not need to use a service of a <NUM> network or does not subscribe to a service of a <NUM> network). In this way, a session requirement can be met, so that load of the co-located session management function network element can be reduced.

In addition, the first network element in the first communications system may further determine a second message based on the capability of the terminal device, the first subscription information, and the second subscription information, and send the second message to the target session management function network element, so that the target session management function network element determines a policy control network element and a charging system based on the second message. The second message includes instruction information instructing the target session management function network element to select a co-located policy control network element and a co-located charging system, or a policy control network element and a charging system that are in the first communications system.

The scenario <NUM> and the scenario <NUM> are separately specifically described below.

If the terminal device supports the first communications system and the second communications system, the first subscription information includes the subscription information corresponding to the data network identity of the session, and the second subscription information does not include the subscription information corresponding to the data network identity of the session, the MME selects a co-located session management function network element, and the MME sends the second message to the co-located session management function network element, so that the co-located session management function network element determines, based on the second message, that a policy control network element and a charging system are a policy control network element and a charging system that are in the <NUM> system. The second message includes the instruction information instructing the co-located session management function network element to select the policy control network element and the charging system that are in the <NUM> system. Therefore, the MME may instruct, by using the second message, the co-located session management function network element to select the policy control network element and the charging system that are in the <NUM> system for a terminal device that has an interworking capability but has no interworking requirement (in other words, the terminal device does not need to use a service of the <NUM> network or does not subscribe to a service of the <NUM> network), so that load of the co-located policy control network element and load of the co-located charging system can be reduced.

For example, in possible networking, all PGW-Cs are upgraded to SMFs+PGW-Cs, but a policy control network element and a charging system network element are not upgraded, in other words, a policy control network element in <NUM> may be a PCRF, and charging system network elements in <NUM> may be an OCS and an OFCS. In this case, even though the MME selects an SMF+PGW-C, the SMF+PGW-C is unaware that UE has no interworking requirement currently, in other words, the UE is not to access the <NUM> system. Therefore, the MME may send the second message to the SMF+PGW-C, and the second message includes instruction information instructing the SMF+PGW-C to select and access the policy control network element and the charging system that are in <NUM>.

It should be understood that, usually, when the MME selects the session management function network element in <NUM> the session management function network element in <NUM> selects the policy control network element and the charging system that are in <NUM>; when the MME selects the co-located session management function network element, the co-located session management function network element selects the co-located policy control network element and the co-located charging system. However, according to the method provided in this example of this application, the MME may instruct the co-located session management function network element to select the policy control network element and the charging system that are in the <NUM> system, so that load of the co-located policy control network element and load of the co-located charging system can be reduced.

Scenario <NUM>: The first communications system is a <NUM> system, the second communications system is a <NUM> system, and the first network element in the first communications system is an AMF.

If the terminal device supports the first communications system and the second communications system, the first subscription information includes the subscription information corresponding to the data network identity of the session, and the second subscription information does not include the subscription information corresponding to the data network identity of the session, the AMF selects a co-located session management function network element, and the AMF sends the second message to the co-located session management function network element, so that the co-located session management function network element determines, based on the second message, that a policy control network element and a charging system are a policy control network element and a charging system that are in <NUM>. The second message includes the instruction information instructing the co-located session management function network element to select the policy control network element and the charging system that are in the <NUM> system. Therefore, the AMF may instruct, by using the second message, the co-located session management function network element to select the policy control network element and the charging system that are in the <NUM> system for a terminal device that has an interworking capability but has no interworking requirement (in other words, the terminal device does not need to use a service of the <NUM> network or does not subscribe to a service of the <NUM> network), so that load of the co-located policy control network element and load of the co-located charging system can be reduced.

For example, in possible networking, deployment of a pure SMF device has not started, in other words, all SMFs+PGW-Cs are obtained by upgrading PGW-Cs, but a policy control network element and a charging system-related network element are not upgraded. Therefore, the AMF can select only an SMF+PGW-C. The AMF sends the second message to the SMF+PGW-C, and the second message includes the instruction information instructing the SMF+PGW-C to select and access the policy control network element and the charging system that are in <NUM>, for example, a PCF.

It should be understood that, usually, when the AMF selects the session management function network element in <NUM>, the session management function network element in <NUM> selects the policy control network element and the charging system that are in <NUM>; when the AMF selects the co-located session management function network element, the co-located session management function network element selects the co-located policy control network element and the co-located charging system. However, according to the method provided in this example of this application, the AMF may instruct the co-located session management function network element to select the policy control network element and the charging system that are in the <NUM> system, so that load of the co-located policy control network element and load of the co-located charging system can be reduced.

A network element selection process in this example of this application is specifically described below with reference to accompanying drawings.

<FIG> shows a specific process <NUM> in which UE establishes a session connection in a <NUM> network.

Step <NUM>: An MME obtains UE capability information. In a possible design, in an attach (Attach) procedure or track area update (Track area update, TAU) procedure, the UE sends a NAS message to the MME. The NAS message carries the UE capability information (UE capabilities), and the UE capabilities include information about whether the UE supports a <NUM> system, information about whether the UE supports a <NUM> system, and the like, or the UE capabilities include indication information indicating whether the UE supports both a <NUM> system and a <NUM> system. The MME stores the UE capabilities.

Step <NUM>: The UE sends a session request message to the MME, and the session request message may also be included in an attach request (Attach request). The session request message may be a NAS message.

Step <NUM>: The MME determines an APN. In a possible design, the session request message carries the APN. In another possible design, the session request message does not carry the APN, and the MME may determine an APN, for example, a default APN.

Step <NUM>: The MME determines a target session management function network element based on the UE capability information, first subscription information, and second subscription information. If the terminal device supports the <NUM> system and the <NUM> system, and both the first subscription information and the second subscription information include subscription information corresponding to the APN, the MME performs step 305a. If the terminal device supports the <NUM> system and the <NUM> system, the first subscription information includes subscription information corresponding to the APN, and the second subscription information does not include the subscription information corresponding to the APN, the MME performs step 305b. It should be understood that, for a specific process in which the MME determines the target session management function network element based on the UE capability information, the first subscription information, and the second subscription information, reference may be made to the possible implementation in the scenario <NUM>. Repeated content is not described again.

In a possible design, before step <NUM>, for example, in the attach procedure or TAU procedure, the MME sends a third message to an HSS+UDM, and the third message is used to obtain the first subscription information and the second subscription information. The MME stores the first subscription information and the second subscription information. In another possible design, after step <NUM>, the MME sends a fourth message to the HSS+UDM, and the fourth message is used to query the first subscription information and the second subscription information.

Step 305a: The MME selects an SMF+PGW-C as the target session management network element, and sends a session request message to the SMF+PGW-C.

Step 305b: The MME selects a PGW-C as the target session management network element, and sends a session request message to the PGW-C.

A subsequent session establishment procedure mainly includes configuration of radio resources, establishment of a user plane tunnel, and the like. For details, refer to the prior art.

<FIG> shows a specific process <NUM> in which UE establishes a session connection in a <NUM> network. All PGW-Cs are upgraded to SMFs+PGW-Cs, but a policy control network element and a charging system-related network element are not upgraded. The policy control network element in <NUM> is a PCRF, charging system network elements in <NUM> are an OCS and an OFCS, and a policy control network element and a charging system that are in <NUM> are PCFs.

Step <NUM> to step <NUM> are the same as step <NUM> to step <NUM>.

Step <NUM>: The MME determines a target policy control network element and a target charging system based on the UE capability information, first subscription information, and second subscription information. If the terminal device supports a <NUM> system and a <NUM> system, and both the first subscription information and the second subscription information include subscription information corresponding to the APN, the MME performs step 405a. If the terminal device supports the <NUM> system and the <NUM> system, the first subscription information includes subscription information corresponding to the APN, and the second subscription information does not include the subscription information corresponding to the APN, the MME performs step 405b.

Step 405a: The MME sends a session request message to an SMF+PGW-C. The session request message may not carry instruction information, or may carry first instruction information. The first instruction information instructs the SMF+PGW-C to select a co-located policy control network element and a co-located charging system. Therefore, the target policy control network element and the target charging system are the co-located policy control network element and the co-located charging system.

Step 405b: The MME sends a session request message to the SMF+PGW-C, the session request message carries second instruction information, and the second instruction information instructs the SMF+PGW-C to select a policy control network element and a charging system that are in <NUM>. Therefore, the target policy control network element and the target charging system are the policy control network element and the charging system that are in <NUM>.

<FIG> shows a specific process <NUM> in which UE establishes a session connection in a <NUM> network. Only an example in which a DNN corresponds to an APN is used below for description. A processing procedure in which a DNN+S-NSSAI corresponds to an APN is similar.

Step <NUM>: An AMF obtains UE capability information. In a possible design, in a registration (Registration) procedure or re-registration (Re-registration) procedure, the UE sends a NAS message to the AMF. The NAS message carries the UE capability information (UE capabilities), and the UE capabilities include information about whether the UE supports a <NUM> system, information about whether the UE supports a <NUM> system, and the like, or the UE capabilities include indication information indicating whether the UE supports both a <NUM> system and a <NUM> system. The AMF stores the UE capabilities.

Step <NUM>: The UE sends a session request message to the AMF, and the session request message is a NAS message. Step <NUM>: The AMF determines a DNN. In a possible design, the session request message carries the DNN. In another possible design, the session request message does not carry the DNN, and the AMF may determine an APN, for example, a default DNN.

Step <NUM>: The AMF determines a target session management function network element based on the UE capability information, first subscription information, and second subscription information. If the terminal device supports the <NUM> system and the <NUM> system, and both the first subscription information and the second subscription information include subscription information corresponding to the DNN, the AMF performs step 505a. If the terminal device supports the <NUM> system and the <NUM> system, the first subscription information includes subscription information corresponding to the DNN, and the second subscription information does not include the subscription information corresponding to the DNN, the AMF performs step 505b. It should be understood that, for a specific process in which the AMF determines the target session management function network element based on the UE capability information, the first subscription information, and the second subscription information, reference may be made to the possible implementation in the scenario <NUM>. Repeated content is not described again.

In a possible design, before step <NUM>, for example, in the registration procedure or re-registration procedure, the AMF sends a third message to an HSS+UDM, and the third message is used to obtain the first subscription information and the second subscription information. The AMF stores the first subscription information and the second subscription information. In another possible design, after step <NUM>, the AMF sends a fourth message to the HSS+UDM, and the fourth message is used to query the first subscription information and the second subscription information.

Step 505a: The AMF selects an SMF+PGW-C as the target session management network element, and sends a session request message to the SMF+PGW-C.

Step 505b: The AMF selects an SMF as the target session management network element, and sends a session request message to the SMF.

<FIG> shows a specific process <NUM> in which UE establishes a session connection in a <NUM> network. Deployment of a pure SMF device has not started, in other words, all SMFs+PGW-Cs are obtained by upgrading PGW-Cs, but a policy control network element and a charging system-related network element are not upgraded. For example, a policy control network element in <NUM> is a PCRF, and charging systems in <NUM> are an OCS and an OFCS. There is an independent policy control network element and an independent charging system in <NUM>, for example, a PCF.

Step <NUM>: The AMF determines a target policy control network element and a target charging system based on the UE capability information, the first subscription information, and the second subscription information. If the terminal device supports a <NUM> system and a <NUM> system, and both the first subscription information and the second subscription information include subscription information corresponding to the DNN, the AMF performs step 605a. If the terminal device supports a <NUM> system and a <NUM> system, the first subscription information includes subscription information corresponding to the DNN, and the second subscription information does not include the subscription information corresponding to the DNN, the AMF performs step 605b.

Step 605a: The AMF sends a session request message to an SMF+PGW-C. The session request message may not carry instruction information, or may carry first instruction information. The first instruction information instructs the SMF+PGW-C to select a co-located policy control network element and a co-located charging system. Therefore, the target policy control network element and the target charging system are the co-located policy control network element and the co-located charging system.

Step 605b: The AMF sends a session request message to the SMF+PGW-C, the session request message carries second instruction information, and the second instruction information instructs the SMF+PGW-C to select and access a policy control network element and a charging system that are in <NUM>. Therefore, the target policy control network element and the target charging system are the policy control network element and the charging system that are in <NUM>.

Based on the foregoing embodiment, an embodiment of this application provides a network element selection apparatus. As shown in <FIG>, the apparatus <NUM> includes:.

In a possible design, the processing unit <NUM> is specifically configured to determine the target session management function network element based on a capability of the terminal device, the first subscription information, and the second subscription information.

In a possible design, the first communications system is a <NUM> system, the second communications system is a <NUM> system, and the apparatus is an MME; and the processing unit <NUM> is specifically configured to: if the terminal device supports the first communications system and the second communications system, and both the first subscription information and the second subscription information include subscription information corresponding to a data network identity of the session, select a co-located session management function network element as the target session management network element, where a network element having a session management capability of the <NUM> system and a session management capability of the <NUM> system is the co-located session management function network element.

In a possible design, the first communications system is a <NUM> system, the second communications system is a <NUM> system, and the apparatus is an MME; and the processing unit <NUM> is specifically configured to: if the terminal device supports the first communications system and the second communications system, the first subscription information includes subscription information corresponding to a data network identity of the session, and the second subscription information does not include the subscription information corresponding to the data network identity of the session, select a session management function network element in the <NUM> system as the target session management network element.

In a possible design, the first communications system is a <NUM> system, the second communications system is a <NUM> system, and the apparatus is an AMF; and the processing unit <NUM> is specifically configured to: if the terminal device supports the first communications system and the second communications system, and both the first subscription information and the second subscription information include subscription information corresponding to a data network identity of the session, select a co-located session management function network element as the target session management network element, where a network element having a session management capability of the <NUM> system and a session management capability of the <NUM> system is the co-located session management function network element.

In a possible design, the first communications system is a <NUM> system, the second communications system is a <NUM> system, and the apparatus is an AMF; and the processing unit <NUM> is specifically configured to: if the terminal device supports the first communications system and the second communications system, the first subscription information includes subscription information corresponding to a data network identity of the session, and the second subscription information does not include the subscription information corresponding to the data network identity of the session, select a session management function network element in the <NUM> system as the target session management network element.

In a possible design, the apparatus further includes: a sending unit <NUM>, configured to send a second message to the target session management function network element, so that the target session management function network element determines a policy control network element and a charging system based on the second message.

It can be understood that, for specific implementations of function modules included in the network element selection apparatus in <FIG> and corresponding benefits, reference may be made to the specific descriptions of the example shown in <FIG>.

It should be understood that division of the units is merely division of logical functions, and during actual implementation, all or some of the units may be integrated into one physical entity, or may be physically separated. In addition, these units may all be implemented by using software through invoking by a processing element, or may all be implemented in a form of hardware. Alternatively, some units are implemented by using software through invoking by a processing element, and some units are implemented in a form of hardware. During implementation, steps in the foregoing methods or the foregoing units can be implemented by using a hardware integrated logic circuit in a processing element, or by using instructions in a form of software.

For example, the foregoing units may be configured as one or more integrated circuits for implementing the foregoing methods, for example, one or more application-specific integrated circuits (Application Specific Integrated Circuit, ASIC), or one or more microprocessors (digital signal processor, DSP), or one or more field programmable gate arrays (Field Programmable Gate Array, FPGA). For another example, when one of the foregoing units is implemented by invoking a program by a processing element, the processing element may be a general-purpose processor, such as a central processing unit (Central Processing Unit, CPU) or another processor that can invoke the program. For another example, these units may be integrated together, and are implemented in a form of a system-on-a-chip (system-on-a-chip, SOC).

In another optional variant, an embodiment of this application provides a network element selection apparatus. For example, the network element selection apparatus may be a chip, the apparatus includes a processor and an interface, and the interface may be an input/output interface. The processor implements the functions of the processing unit <NUM>, and the interface implements the functions of the receiving unit <NUM> and the functions of the sending unit <NUM>. The apparatus may further include a memory. The memory is configured to store a program that can run on the processor. When the processor executes the program, the method of the example shown in <FIG> is performed. Based on the foregoing embodiment, an embodiment of this application further provides a first network element in a first communications system. As shown in <FIG>, the network element <NUM> includes a transceiver <NUM>, a processor <NUM>, and a memory <NUM>. The memory <NUM> is configured to store a computer program. The processor <NUM> invokes the computer program stored in the memory <NUM>, and performs, by using the transceiver <NUM>, the method shown in <FIG>. The processor may be a CPU, a network processor (network processor, NP), a hardware chip, or any combination thereof. The memory may include a volatile memory (volatile memory), for example, a random access memory (random access memory, RAM). Alternatively, the memory may include a non-volatile memory (non-volatile memory), such as a read-only memory (read-only memory, ROM), a flash memory (flash memory), a hard disk drive (hard disk drive, HDD), or a solid-state drive (solid-state drive, SSD). Alternatively, the memory may include a combination of the foregoing types of memories.

It can be understood that the apparatus in the embodiment shown in <FIG> may be implemented by using the network element <NUM> shown in <FIG>. Specifically, the processing unit <NUM> may be implemented by the processor <NUM>, and the receiving unit <NUM> and the sending unit <NUM> may be implemented by the transceiver <NUM>. A structure of the network element <NUM> does not constitute a limitation on the embodiments of this application.

Step <NUM>: The MME determines an APN. In a possible design, the session request message in step <NUM> carries the APN. In another possible design, the session request message does not carry the APN, and the MME may determine an APN, for example, a default APN. An APN determining manner is described above. Details are not described again.

Step <NUM>: The MME determines a target session management function network element based on the UE capability information (or referred to as a capability of a terminal) and third subscription information. Specifically, if the capability of the terminal indicates that the UE supports the <NUM> system and the <NUM> system, and the third subscription of the terminal indicates that a data network identity APN corresponding to the session supports interworking with the <NUM> system (or referred to as a 5GC), the MME selects a co-located session management function network element as the target session management network element, and performs step 905a. Optionally, that the third subscription of the terminal indicates that a data network identity APN corresponding to the session supports interworking with the <NUM> system (or referred to as a 5GC) further includes: The third subscription information of the terminal is indication information indicating that the data network identity APN corresponding to the session supports interworking with a DNN and a network slice identification S-NSSAI. The co-located session management function network element may be a network element having both a session management capability of the <NUM> system and a session management capability of the <NUM> system, for example, an SMF+PGW-C. If the capability of the terminal indicates that the UE supports the <NUM> system and the <NUM> system, and the third subscription information indicates that a data network identity APN of the session does not support interworking with the <NUM> system, the MME does not select a co-located session management function network element as the target session management network element, and performs step 905b. That the MME does not select a co-located session management function network element as the target session management network element includes: selecting, by the MME as the target session management network element, a session management function network element that is not specially used for interworking, for example, a PGW-C or a PGW in a pure <NUM> system. Therefore, the MME may select the co-located session management function network element as the target session management function network element for a terminal device having both an interworking capability and an interworking requirement.

In addition, the MME may further determine a second message based on the capability of the terminal device and the third subscription information, and send the second message to the target session management function network element, so that the target session management function network element determines a policy control network element and a charging system based on the second message. The second message includes instruction information instructing the target session management function network element to select a co-located policy control network element and a co-located charging system, or a policy control network element and a charging system that are in the first communications system. For a specific process, refer to the example corresponding to <FIG>.

Step 905a: The MME selects an SMF+PGW-C as the target session management network element, and sends a session request message to the SMF+PGW-C.

Step 905b: The MME selects a PGW-C as the target session management network element, and sends a session request message to the PGW-C.

Therefore, the MME may select a session management function network element in the <NUM> system as the target session management network element for a terminal device having an interworking capability but having no interworking requirement (that is, the terminal device does not support interworking with <NUM>). In this way, a session requirement can be met, so that load of the co-located session management function network element can be reduced. Optionally, the MME may instruct the co-located session management network element to select a policy control network element and a charging system that are in the <NUM> system for a terminal device having an interworking capability but having no interworking requirement (that is, the terminal device does not support interworking with <NUM>), so that load of the co-located policy control network element and load of the co-located charging system can be reduced.

Further, it can be understood that, for content that is not clearly described in the descriptions in the embodiment corresponding to <FIG>, reference may be made to an explanation of the foregoing embodiments.

In addition, a logical structure of the MME in <FIG> may be shown in <FIG>, and the steps described in <FIG> may be implemented by using the processing unit, the receiving unit, and the sending unit that are in <FIG>. It can be understood that the apparatus in the embodiment shown in <FIG> may be implemented by using the network element <NUM> shown in <FIG>. Specifically, the processing unit <NUM> may be implemented by the processor <NUM>, and the receiving unit <NUM> and the sending unit <NUM> may be implemented by the transceiver <NUM>. A structure of the network element <NUM> does not constitute a limitation on the embodiments of this application.

Step <NUM>: The UE sends a session request message to the AMF, and the session request message is a NAS message. Step <NUM>: The AMF determines a DNN. In a possible design, the session request message in step <NUM> carries the DNN. In another possible design, the session request message does not carry the DNN, and the AMF may determine an APN, for example, a default DNN. A DNN determining manner is described above. Details are not described again.

Step <NUM>: The AMF determines a target session management function network element based on the UE capability information (or referred to as a capability of a terminal) and third subscription information. Specifically, if the capability of the terminal indicates that the UE supports the <NUM> system and the <NUM> system, and the third subscription of the terminal indicates that a data network identity DNN corresponding to the session supports interworking with the <NUM> system (or referred to as an EPS or an EPC), the AMF selects a co-located session management function network element as the target session management network element, and performs step 1005a. Optionally, that the third subscription of the terminal indicates that a data network identity DNN corresponding to the session supports interworking with the <NUM> system (or referred to as an EPS or an EPC) further includes: The third subscription information of the terminal is indication information indicating that the data network identity DNN and a network slice identification S-NSSAI that correspond to the session support interworking. The co-located session management function network element may be a network element having both a session management capability of the <NUM> system and a session management capability of the <NUM> system, for example, an SMF+PGW-C. If the capability of the terminal indicates that the UE supports the <NUM> system and the <NUM> system, and the third subscription information indicates that a data network identity DNN of the session does not support interworking with the <NUM> system, the AMF does not select a co-located session management function network element as the target session management network element, and performs step 1005b. That the AMF does not select a co-located session management function network element as the target session management network element includes: selecting, by the AMF as the target session management network element, a session management function network element that is not specially used for interworking, for example, an SMF in a pure <NUM> system. Therefore, the AMF may select the co-located session management function network element as the target session management function network element for a terminal device having both an interworking capability and an interworking requirement.

In addition, the AMF may further determine a second message based on the capability of the terminal device and the third subscription information, and send the second message to the target session management function network element, so that the target session management function network element determines a policy control network element and a charging system based on the second message. The second message includes instruction information instructing the target session management function network element to select a co-located policy control network element and a co-located charging system, or a policy control network element and a charging system that are in the first communications system. For a specific process, refer to the example corresponding to <FIG>.

Step 1005a: The AMF selects an SMF+PGW-C as the target session management network element, and sends a session request message to the SMF+PGW-C.

Step 1005b: The AMF selects an SMF as the target session management network element, and sends a session request message to the SMF.

Therefore, the AMF may select a session management function network element in the <NUM> system as the target session management network element for a terminal device having an interworking capability but having no interworking requirement (that is, the terminal device does not support interworking with <NUM>). In this way, a session requirement can be met, so that load of a co-located session management function network element can be reduced. Optionally, the AMF may instruct the co-located session management network element to select a policy control network element and a charging system that are in the <NUM> system for a terminal device having an interworking capability but having no interworking requirement (that is, the terminal device does not support interworking with <NUM>), so that load of the co-located policy control network element and load of the co-located charging system can be reduced.

In addition, a logical structure of the AMF in <FIG> may be shown in <FIG>, and the steps described in <FIG> may be implemented by using the processing unit, the receiving unit, and the sending unit that are in <FIG>. It can be understood that the apparatus in the embodiment shown in <FIG> may be implemented by using the network element <NUM> shown in <FIG>. Specifically, the processing unit <NUM> may be implemented by the processor <NUM>, and the receiving unit <NUM> and the sending unit <NUM> may be implemented by the transceiver <NUM>. A structure of the network element <NUM> does not constitute a limitation on the embodiments of this application.

An embodiment of this application further provides a computer readable storage medium. The computer readable storage medium stores a computer program. When the computer program runs on a computer, the computer is enabled to perform the method of the embodiment shown in <FIG>, the processor is enabled to perform the steps corresponding to the MME shown in <FIG>, and the processor is also enabled to perform the steps corresponding to the AMF shown in <FIG>.

To sum up, in the method provided in this embodiment of this application, a first network element in a first communications system receives a first message sent by a terminal device, and the first message is used to request to establish a session. In response to the first message, the first network element in the first communications system determines a target session management function network element based on first subscription information and second subscription information. Compared with selecting a network element based only on whether the terminal device supports a <NUM> system and a <NUM> system in the prior art, a terminal device that supports the <NUM> system and the <NUM> system and that has no interworking requirement can properly select a network element, and load of a co-located session management function network element can be reduced.

When the first communications system is a <NUM> system, the second communications system is a <NUM> system, and the first network element in the first communications system is an MME, the MME may select a co-located session management function network element as the target session management function network element for a terminal device having both an interworking capability and an interworking requirement. The MME may select a session management function network element in the <NUM> system as the target session management network element for a terminal device having an interworking capability but having no interworking requirement (that is, the terminal device does not need to use a service of a <NUM> network or does not subscribe to a service of a <NUM> network). In this way, a session requirement can be met, so that load of a co-located session management function network element can be reduced.

When the first communications system is a <NUM> system, the second communications system is a <NUM> system, and the first network element in the first communications system is an AMF, the AMF may select a co-located session management function network element as the target session management function network element for a terminal device having both an interworking capability and an interworking requirement. The AMF may select a session management function network element in the <NUM> system as the target session management network element for a terminal device having an interworking capability but having no interworking requirement (that is, the terminal device does not need to use a service of a <NUM> network or does not subscribe to a service of a <NUM> network). In this way, a session requirement can be met, so that load of a co-located session management function network element can be reduced.

When the first communications system is a <NUM> system, the second communications system is a <NUM> system, and the first network element in the first communications system is an MME, the MME may instruct, by using a second message, a co-located session management function network element to select a policy control network element and a charging system that are in the <NUM> system for a terminal device having an interworking capability but having no interworking requirement (that is, the terminal device does not need to use a service of a <NUM> network or does not subscribe to a service of a <NUM> network), so that load of a co-located policy control network element and load of a co-located charging system can be reduced. When the first communications system is a <NUM> system, the second communications system is a <NUM> system, and the first network element in the first communications system is an AMF, the AMF may instruct, by using a second message, a co-located session management function network element to select a policy control network element and a charging system that are in the <NUM> system for a terminal device having an interworking capability but having no interworking requirement (that is, the terminal device does not need to use a service of a <NUM> network or does not subscribe to a service of a <NUM> network), so that load of a co-located policy control network element and load of a co-located charging system can be reduced.

Therefore, the embodiments of this application may use a form of hardware only embodiments, software only embodiments, or embodiments with a combination of software and hardware. Moreover, the embodiments of this application may use a form of a computer program product that is implemented on one or more computer-usable storage media (including but not limited to a magnetic disk memory, a CD-ROM, an optical memory, and the like) that include computer-usable program code.

The embodiments of this application are described with reference to the flowcharts and/or block diagrams of the method, the device (system), and the computer program product according to the embodiments of this application. It should be understood that computer program instructions may be used to implement each process and/or each block in the flowcharts and/or the block diagrams and a combination of a process and/or a block in the flowcharts and/or the block diagrams. These computer program instructions may be provided for a general-purpose computer, a dedicated computer, an embedded processor, or a processor of another programmable data processing device to generate a machine, so that the instructions executed by a computer or a processor of another programmable data processing device generate an apparatus for implementing a specific function in one or more processes in the flowcharts and/or in one or more blocks in the block diagrams.

These computer program instructions may be stored in a computer readable memory that can instruct the computer or another programmable data processing device to work in a specific manner, so that the instructions stored in the computer readable memory generate an artifact that includes an instruction apparatus.

Claim 1:
A network element selection method, wherein the method comprises:
receiving (<NUM>, <NUM>), by a first network element in a first communications system, a first message from a terminal device, wherein the first message is used to request to establish a session;
in response to the first message, determining (<NUM>, <NUM>), by the first network element, a target session management function network element based on a capability of the terminal device and subscription information of the terminal device, wherein the subscription information indicates whether a data network identity corresponding to the session supports interworking with a second communications system or not;
sending (905a, 905b, 1005a, 1005b), by the first network element, a session request message to the target session management function network element; and
receiving (905a, 905b, 1005a, 1005b), by the target session management function network element, the session request message from the first network element.