(19)
(11)EP 3 684 100 B1

(12)EUROPEAN PATENT SPECIFICATION

(45)Mention of the grant of the patent:
27.07.2022 Bulletin 2022/30

(21)Application number: 19861348.1

(22)Date of filing:  06.06.2019
(51)International Patent Classification (IPC): 
H04W 76/12(2018.01)
H04W 36/00(2009.01)
H04W 76/11(2018.01)
(52)Cooperative Patent Classification (CPC):
H04W 76/11; H04W 76/12; H04W 36/0011
(86)International application number:
PCT/CN2019/090433
(87)International publication number:
WO 2020/057179 (26.03.2020 Gazette  2020/13)

(54)

POLICY CONTROL METHODS, DEVICE AND SYSTEM

VERFAHREN, VORRICHTUNG UND SYSTEM ZUR RICHTLINIENSTEUERUNG

PROCÉDÉS, DISPOSITIF ET SYSTÈME DE COMMANDE DE POLITIQUE


(84)Designated Contracting States:
AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

(30)Priority: 19.09.2018 CN 201811096126
31.10.2018 CN 201811288799

(43)Date of publication of application:
22.07.2020 Bulletin 2020/30

(73)Proprietor: HUAWEI TECHNOLOGIES CO., LTD.
Shenzhen Guangdong 518129 (CN)

(72)Inventor:
  • YAN, Yali
    Shenzhen, Guangdong 518129 (CN)

(74)Representative: Roth, Sebastian 
Mitscherlich PartmbB Patent- und Rechtsanwälte Sonnenstraße 33
80331 München
80331 München (DE)


(56)References cited: : 
CN-A- 108 401 275
US-A1- 2017 359 768
  
  • ANONYMOUS: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Procedures for the 5G System; Stage 2 (Release 15)", 3GPP STANDARD; TECHNICAL SPECIFICATION; 3GPP TS 23.502, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, no. V15.3.0, 17 September 2018 (2018-09-17), pages 1-330, XP051487017,
  • "3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 5G System; Policy and Charging Control signalling flows and QoS parameter mapping; Stage 3 (Release 15)", 3GPP DRAFT; 29513-F10, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE , 18 September 2018 (2018-09-18), XP051573149, Retrieved from the Internet: URL:http://www.3gpp.org/ftp/tsg%5Fct/WG3%5 Finterworking%5Fex%2DCN3/DRAFT%5FSPEC%5FIM PLEMENTATIONS/CT%5F81 [retrieved on 2018-09-18]
  • ANONYMOUS: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System Architecture for the 5G System; Stage 2 (Release 15)", 3GPP STANDARD; TECHNICAL SPECIFICATION; 3GPP TS 23.501, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, no. V15.3.0, 17 September 2018 (2018-09-17), pages 1-226, XP051487016,
  • Huawei: "Cleanup to PCF selection in AMF and SMF", 3GPP TSG-SA WG2 meeting #127, no. S2-183332, 10 April 2018 (2018-04-10), pages 1,8-16,22, XP051437675, Sanya, China
  • Cisco: "BSF storing the selected PCF Address in UDR structured data should be optional", 3GPP TSG-SA WG2 meeting #125, 22 January 2018 (2018-01-22), page 2, XP051389534,
  
Note: Within nine months from the publication of the mention of the grant of the European patent, any person may give notice to the European Patent Office of opposition to the European patent granted. Notice of opposition shall be filed in a written reasoned statement. It shall not be deemed to have been filed until the opposition fee has been paid. (Art. 99(1) European Patent Convention).


Description

TECHNICAL FIELD



[0001] This application relates to the field of communications technologies, and in particular, to a policy control method, a device, and a system.

BACKGROUND



[0002] In an existing 5th generation (5th generation, 5G) network, in a procedure in which a terminal requests to establish a plurality of protocol data unit (protocol data unit, PDU) sessions having same single network slice selection assistance information (single network slice selection assistance information, S-NSSAI) and a same data network name (data network name, DNN), for different PDU sessions, an access and mobility management function (access and mobility management function, AMF) network element selects different session management function (session management function, SMF) network elements, and different SMF network elements select different policy control function (policy control function, PCF) network elements, to obtain a policy and charging control (policy and charging control, PCC) rule and another PDU session-related policy from a corresponding PCF network element.

[0003] However, the PCF network element formulates the PCC rule and the another PDU session-related policy based on subscription information obtained from a unified data repository (unified data repository, UDR) network element. The subscription information may include, for example, a maximum guaranteed bandwidth that is allowed to be authorized by the PCF to the terminal, or remaining usage that is authorized by the PCF network element to the terminal. In this case, a plurality of PCF network elements each make a policy decision based on the subscription information. Consequently, a conflict between the subscription information and policies formulated for a plurality of PDU sessions of a same terminal that have same S-NSSAI and a same DNN may be caused. For example, a total maximum guaranteed bandwidth authorized to the plurality of PDU sessions of the same terminal that have the same S-NSSAI and the same DNN exceeds the maximum guaranteed bandwidth that is allowed to be authorized by the PCF network element to the terminal in the subscription information, or a total amount of accumulated usage for the plurality of PDU sessions of the same terminal that have the same S-NSSAI and the same DNN exceeds an amount of the remaining usage that is authorized by the PCF network element to the terminal in the subscription information.

[0004] Therefore, how to avoid the conflict between the policies formulated for the plurality of PDU sessions of the same terminal that have the same S-NSSAI and the same DNN and the subscription information obtained from the UDR network element is an urgent problem to be resolved currently.

[0005] "3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 5G System; Policy and Charging Control signalling flows and QoS parameter mapping; Stage 3 (Release 15)", 3GPP DRAFT; TS 29.513 V15.1.0 (2018-09) discloses call flows of Policy and Charging Control (PCC) over the Npcf, Nsmf, Namf, Nudr, Nnef and Nnwdaf service-based interfaces and their relationship with the flow level signalling in a 5G system.

[0006] "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System Architecture for the SG System; Stage 2 (Release 15)", 3GPP Technical Specification 23.501 V15.3.0 (2018-09) discloses a Stage 2 system architecture for the 5G System, while the 5G System provides data connectivity and services. The specification covers both roaming and non-roaming scenarios in all aspects, including interworking between 5GS and EPS, mobility within 5GS, QoS, policy control and charging, authentication and in general 5G System wide features e.g. SMS, Location Services, Emergency Services.

SUMMARY



[0007] Embodiments of this application provide a method for selecting a policy control network element, a device, and a system, to avoid a conflict between policies formulated for a plurality of PDU sessions of a same terminal that have same S-NSSAI and a same DNN and subscription information obtained from a unified data repository network element.

[0008] To achieve the foregoing objective, the following technical solutions are used in the embodiments of this application.

[0009] The present invention is defined by a method for selecting a policy control network element according to independent claim 1 and 13, a first policy network element according to independent claim 3, a policy control system according to independent claim 4 and a computer-readable storage medium according to independent claim 12. Additional features of the invention are provided in the dependent claims.

BRIEF DESCRIPTION OF DRAWINGS



[0010] The embodiments of Figs. 1, 2, 2a, 8-11, 15 and 17, to which the following section refers to, are not part of the invention, but illustrative examples necessary for understanding the invention.

FIG. 1 is a schematic architectural diagram 1 of a policy control system according to an embodiment of this application;

FIG. 2 is a schematic architectural diagram 2 of a policy control system according to an embodiment of this application;

FIG. 2a is a schematic architectural diagram 3 of a policy control system according to an embodiment of this application;

FIG. 2b is a schematic architectural diagram 4 of a policy control system according to an embodiment of this application;

FIG. 3a is a schematic diagram in which a policy control system is applied to a non-roaming 5G network architecture according to an embodiment of this application;

FIG. 3b is a schematic diagram in which a policy control system is applied to a home routing 5G network architecture according to an embodiment of this application;

FIG. 4 is a schematic diagram of a hardware structure of a communications device according to an embodiment of this application;

FIG. 5A and FIG. 5B are a schematic flowchart 1 of a policy control method according to an embodiment of this application;

FIG. 6A and FIG. 6B are a schematic flowchart 2 of a policy control method according to an embodiment of this application;

FIG. 7A and FIG. 7B are a schematic flowchart 3 of a policy control method according to an embodiment of this application;

FIG. 8 is a schematic structural diagram of a mobility management network element according to an embodiment of this application;

FIG. 9 is a schematic structural diagram of a network device according to an embodiment of this application;

FIG. 10 is a schematic structural diagram of a first session management network element according to an embodiment of this application;

FIG. 11 is a schematic structural diagram of a second session management network element according to an embodiment of this application;

FIG. 12A and FIG. 12B are a schematic flowchart 4 of a policy control method according to an embodiment of this application;

FIG. 13A and FIG. 13B are a schematic flowchart 5 of a policy control method according to an embodiment of this application;

FIG. 14A and FIG. 14B are a schematic flowchart 6 of a policy control method according to an embodiment of this application;

FIG. 15 is a schematic structural diagram of a unified data management network element according to an embodiment of this application;

FIG. 16 is a schematic structural diagram of a first policy control network element according to an embodiment of this application; and

FIG. 17 is a schematic structural diagram of a binding support network element according to an embodiment of this application.


DESCRIPTION OF EMBODIMENTS



[0011] The following describes technical solutions in embodiments of this application with reference to accompanying drawings in the embodiments of this application. In description of this application, "/" represents an "or" relationship between associated objects unless otherwise specified. For example, A/B may represent A or B. The term "and/or" in this application describes only an association relationship for describing associated objects and represents that three relationships may exist. For example, A and/or B may represent the following three cases: Only A exists, both A and B exist, and only B exists, where A and B may be singular or plural. In addition, in the description of this application, "a plurality of" means two or more unless otherwise specified. "At least one (one piece) of the following" or a similar expression thereof refers to any combination of these items, including any combination of a singular item (piece) or plural items (pieces). For example, at least one (piece) of a, b, or c may represent a, b, c, a combination of a and b, a combination of a and c, a combination of b and c, or a combination of a, b, and c, where a, b, and c may be in a singular or plural form. In addition, to clearly describe the technical solutions in the embodiments of this application, terms such as "first" and "second" are used in the embodiments of this application to distinguish between same items or similar items that have basically the same functions or purposes. A person skilled in the art may understand that the terms such as "first" and "second" do not limit a quantity or an execution sequence, and that the terms such as "first" and "second" do not indicate a definite difference.

[0012] In addition, network architectures and service scenarios described in the embodiments of this application are intended to more clearly describe the technical solutions in the embodiments of this application, but do not limit the technical solutions provided in the embodiments of this application. A person of ordinary skill in the art may know that as the network architectures evolve and a new service scenario emerges, the technical solutions provided in the embodiments of this application are also applicable to a similar technical problem.

[0013] The embodiments described in reference to Figs. 1, 2 and 2a are not part of the invention, but an illustrative examples necessary for understanding the invention.

[0014] FIG. 1 shows a policy control system 10 according to an embodiment of this application. The policy control system 10 includes a mobility management network element 101 and a first session management network element 102.

[0015] The mobility management network element 101 is configured to send, to the first session management network element 102, a first request message used to create a first session. The first request message includes an identifier of a terminal, S-NSSAI, and a DNN

[0016] The first session management network element 102 is configured to: receive, from the mobility management network element 101, the first request message used to create the first session, and send a second request message to a binding support network element. The second request message includes the identifier of the terminal, the S-NSSAI, and the DNN

[0017] The first session management network element 102 is further configured to: receive an identifier of a policy control network element from the binding support network element, and select the policy control network element based on the identifier of the policy control network element.

[0018] In this embodiment of this application, the request message is used to request a corresponding identifier of a policy control network element, and the policy control network element may be a policy control network element corresponding to a second session. This is not specifically limited in this embodiment of this application.

[0019] Optionally, the mobility management network element 101 is further configured to: before sending, to the first session management network element 102, the first request message used to create the first session, determine that the first session that is of the terminal and that is being established has the same S-NSSAI and the same DNN as the established second session of the terminal. Correspondingly, the first request message further includes indication information, and the indication information is used to instruct the first session management network element 102 to obtain the identifier of the policy control network element from the binding support network element; or the indication information is used to indicate that a session that is of the terminal and that has the same S-NSSAI and the same DNN as the first session is established.

[0020] Optionally, the session in this embodiment of this application may be, for example, a PDU session. A general description is provided herein. This is not specifically limited in this embodiment of this application.

[0021] Optionally, in this embodiment of this application, the mobility management network element 101 and the first session management network element 102 may directly communicate with each other, or may communicate with each other through forwarding performed by another device. This is not specifically limited in this embodiment of this application.

[0022] Based on the policy control system provided in this embodiment of this application, the mobility management network element may send, to the first session management network element, the first request message used to create the first session, and the first request message includes the identifier of the terminal, the S-NSSAI, and the DNN. Therefore, the first session management network element may obtain the corresponding identifier of the policy control network element from the binding support network element based on the identifier of the terminal, the S-NSSAI, and the DNN, and select the policy control network element based on the identifier of the policy control network element. The policy control network element may be the policy control network element corresponding to the second session. In other words, it can be ensured that a same policy control network element is selected for a plurality of sessions of a same terminal that have same S-NSSAI and a same DNN. Therefore, a conflict between policies formulated for the plurality of PDU sessions of the same terminal that have the same S-NSSAI and the same DNN and subscription information obtained from a unified data repository network element can be avoided.

[0023] Optionally, as shown in FIG. 1, the policy control system 10 provided in this embodiment of this application may further include a second session management network element 103.

[0024] The mobility management network element 101 is further configured to send, to the second session management network element 103, a third request message used to create the second session.

[0025] The second session management network element 103 is configured to: receive, from the mobility management network element 101, the third request message used to create the second session, further select the policy control network element, and send a registration request to the binding support network element. The registration request includes the identifier of the terminal, the S-NSSAI, the DNN, and the identifier of the policy control network element.

[0026] Optionally, in this embodiment of this application, the mobility management network element 101 and the second session management network element 103 may directly communicate with each other, or may communicate with each other through forwarding performed by another device. This is not specifically limited in this embodiment of this application.

[0027] Alternatively, FIG. 2 shows a policy control system 20 according to an embodiment of this application. The policy control system 20 includes a network device 201 and a first session management network element 202.

[0028] The network device 201 is configured to: determine that a first session that is of a terminal and that is being established has the same S-NSSAI and the same DNN as an established second session of the terminal, and further send, to the first session management network element 202 corresponding to the first session, an identifier of a policy control network element selected by a second session management network element corresponding to the second session.

[0029] The first session management network element 202 is configured to: receive the identifier of the policy control network element from the network device 201, and select the policy control network element based on the identifier of the policy control network element.

[0030] Optionally, the network device in this embodiment of this application may be, for example, a unified data management network element or a mobility management network element. This is not specifically limited in this embodiment of this application.

[0031] Optionally, in this embodiment of this application, the network device 201 and the first session management network element 202 may directly communicate with each other, or may communicate with each other through forwarding performed by another device. This is not specifically limited in this embodiment of this application.

[0032] Based on the policy control system provided in this embodiment of this application, after determining that the first session that is of the terminal and that is being established has the same S-NSSAI and the same DNN as the established second session of the terminal, the network device sends, to the first session management network element, the identifier of the policy control network element selected by the second session management network element corresponding to the second session, so that the second session management network element can select the corresponding policy control network element based on the identifier of the policy control network element. In other words, it can be ensured that a same policy control network element is selected for a plurality of sessions of a same terminal that have same S-NSSAI and a same DNN. Therefore, a conflict between policies formulated for the plurality of PDU sessions of the same terminal that have the same S-NSSAI and the same DNN and subscription information obtained from the unified data repository network element can be avoided.

[0033] Optionally, as shown in FIG. 2, the policy control system 20 provided in this embodiment of this application may further include a second session management network element 203.

[0034] The second session management network element 203 is configured to: in a process of establishing the second session, select the policy control network element, and send the identifier of the policy control network element to the network device 201.

[0035] The network device 201 is configured to receive the identifier of the policy control network element from the second session management network element.

[0036] Optionally, in this embodiment of this application, the network device 201 and the second session management network element 203 may directly communicate with each other, or may communicate with each other through forwarding performed by another device. This is not specifically limited in this embodiment of this application.

[0037] Alternatively, FIG. 2a shows a policy control system 20a according to an embodiment of this application. The policy control system 20a includes a unified data management network element 204 and a first session management network element 205.

[0038] The unified data management network element 204 is configured to determine that a first session that is of a terminal and that is being established has the same S-NSSAI and the same DNN as an established second session of the terminal.

[0039] The unified data management network element 204 is further configured to send indication information to the first session management network element 205 corresponding to the first session. The indication information is used to instruct the first session management network element 205 to obtain an identifier of a policy control network element from a binding support network element; or the indication information is used to indicate that a session that is of the terminal and that has the same S-NSSAI and the same DNN as the first session is established; or the indication information is used to indicate that the first session has corresponding binding information.

[0040] The first session management network element 205 is configured to: receive the indication information from the unified data management network element 204, and send a request message to the binding support network element based on the indication information. The request message includes an identifier of the terminal, the S-NSSAI, and the DNN

[0041] The first session management network element 205 is further configured to: receive the identifier of the policy control network element from the binding support network element, and select the policy control network element based on the identifier of the policy control network element.

[0042] Optionally, in this embodiment of this application, the unified data management network element 204 and the first session management network element 205 may directly communicate with each other, or may communicate with each other through forwarding performed by another device. This is not specifically limited in this embodiment of this application.

[0043] Based on the policy control system provided in this embodiment of this application, after determining that the first session that is of the terminal and that is being established has the same S-NSSAI and the same DNN as the established second session of the terminal, the unified data management network element may send the indication information to the first session management network element, so that the first session management network element may obtain, from the binding support network element based on the indication information, an identifier that is of a policy control network element and that corresponds to the identifier of the terminal, the S-NSSAI, and the DNN, and select the policy control network element based on the identifier of the policy control network element. The policy control network element may be a policy control network element corresponding to the second session. In other words, it can be ensured that a same policy control network element is selected for a plurality of sessions of a same terminal that have same S-NSSAI and a same DNN. Therefore, a conflict between policies formulated for the plurality of PDU sessions of the same terminal that have the same S-NSSAI and the same DNN and subscription information obtained from a unified data repository network element can be avoided.

[0044] Alternatively, FIG. 2b shows a policy control system 20b. The policy control system 20b includes a first policy control network device 206 and a first session management network element 207.

[0045] In a possible implementation, the first session management network element 207 is configured to receive, from a mobility management network element, a first request message used to create a first session. The first request message includes an identifier of a terminal, S-NSSAI, and a DNN

[0046] The first session management network element 207 is further configured to: select the first policy control network element 206 for the first session, and send a policy control creation request to the first policy control network element 206. The policy control creation request includes the identifier of the terminal, the S-NSSAI, and the DNN

[0047] The first policy control network element 206 is configured to: receive the policy control creation request from the first session management network element 207, and send the identifier of the terminal, the S-NSSAI, the DNN, and an identifier of the first policy control network element 206 to a binding support network element.

[0048] The first policy control network element 206 is further configured to: receive a rejection indication from the binding support network element, and send the rejection indication to the first session management network element 207. The rejection indication includes the identifier of the terminal, the S-NSSAI, the DNN, and an identifier of a second policy control network element.

[0049] The first session management network element 207 is configured to: receive the rejection indication, and select the second policy control network element for the first session based on the identifier of the second policy control network element.

[0050] Alternatively and according to an embodiment of the present invention, the first session management network element 207 is configured to send a policy control creation request to the first policy control network element 206, where the policy control creation request includes an identifier of a terminal, S-NSSAI, and a DNN; the first policy control network element 206 is configured to: receive the policy control creation request from the first session management network element 207, and send the identifier of the terminal, the S-NSSAI, the DNN, and an identifier of the first policy control network element to a binding support network element; the first policy control network element 206 is configured to: receive an identifier of a second policy control network element from the binding support network element, and send the identifier of the second policy control network element to the first session management network element 207, where the identifier of the second policy control network element is an identifier that is of a policy control network element, that corresponds to the identifier of the terminal, the S-NSSAI, and the DNN, and that is stored by the binding support network element; and the first session management network element 207 is configured to: receive the identifier of the second policy control network element from the first policy control network element 206, and select the second policy control network element for a first session based on the identifier of the second policy control network element.

[0051] Alternatively, in still another possible implementation, the first session management network element 207 is configured to send a policy control creation request to the first policy control network element 206, where the policy control creation request includes an identifier of a terminal, S-NSSAI, and a DNN; the first policy control network element 206 is configured to: receive the policy control creation request from the first session management network element 207, and send, to a binding support network element, the identifier of the terminal, the S-NSSAI, the DNN, and an identifier of a first policy control network element set to which the first policy control network element 206 belongs; the first policy control network element 206 is configured to: receive an identifier of a second policy control network element set from the binding support network element, and send the identifier of the second policy control network element set to the first session management network element 207, where the identifier of the second policy control network element set is an identifier that is of a policy control network element set, that corresponds to the identifier of the terminal, the S-NSSAI, and the DNN, and that is stored by the binding support network element; and the first session management network element 207 is configured to: receive the identifier of the second policy control network element set from the first policy control network element 206, and select a second policy control network element for a first session based on the identifier of the second policy control network element set, where the second policy control network element belongs to the second policy control network element set.

[0052] Optionally, in this embodiment of this application, the first policy control network element 206 and the first session management network element 207 may directly communicate with each other, or may communicate with each other through forwarding performed by another device. This is not specifically limited in this embodiment of this application.

[0053] Based on the policy control system provided in this embodiment of this application, it can be ensured that a same policy control network element is selected for a plurality of sessions of a same terminal that have same S-NSSAI and a same DNN Therefore, a conflict between policies formulated for the plurality of PDU sessions of the same terminal that have the same S-NSSAI and the same DNN and subscription information obtained from a unified data repository network element can be avoided.

[0054] Optionally, the policy control system shown in FIG. 1, FIG. 2, FIG. 2a, or FIG. 2b may be applied to a current 5G network architecture and another future network architecture. This is not specifically limited in the embodiments of this application.

[0055] For example, it is assumed that the policy control system 10 shown in FIG. 1, the policy control system 20 shown in FIG. 2, the policy control system 20a shown in FIG. 2a, or the policy control system 20b shown in FIG. 2b is applied to a current non-roaming 5G network architecture. As shown in FIG. 3a, a network element or an entity corresponding to the foregoing first session management network element or the foregoing second session management network element may be an SMF network element in the non-roaming 5G network architecture; a network element or an entity corresponding to the foregoing unified data management network element may be a unified data management (unified data management, UDM) network element in the non-roaming 5G network architecture; a network element or an entity corresponding to the foregoing mobility management network element may be an AMF network element in the non-roaming 5G network architecture; a network element or an entity corresponding to the foregoing binding support network element may be a binding support function (binding support function, BSF) network element in the non-roaming 5G network architecture; and a network element or an entity corresponding to the foregoing first policy control network element may be a PCF network element in the non-roaming 5G network architecture.

[0056] In addition, as shown in FIG. 3a, the non-roaming 5G network architecture may further include an access device, a user plane function (user plane function, UPF) network element, a UDR network element, or the like. This is not specifically limited in the embodiments of this application.

[0057] The terminal communicates with the AMF network element through a next generation network (Next generation, N) 1 interface (N1 for short), the access device communicates with the AMF network element through an N2 interface (N2 for short), the access device communicates with the UPF network element through an N3 interface (N3 for short), the AMF network element communicates with the SMF network element through an N11 interface (N11 for short), the AMF network element communicates with the UDM network element through an N8 interface (N8 for short), the SMF network element communicates with the PCF network element through an N7 interface (N7 for short), the SMF network element communicates with the UPF network element through an N4 interface (N4 for short), the SMF network element communicates with the UDM network element through an N10 interface (N10 for short), the UDM network element communicates with the UDR network element, the PCF network element communicates with the UDR network element, and the BSF network element communicates with the PCF network element and the SMF network element.

[0058] It should be noted that FIG. 3a merely shows an example that there is one SMF network element and one UPF network element. Certainly, the non-roaming 5G network architecture may include a plurality of SMF network elements and a plurality of UPF network elements. For example, the non-roaming 5G network architecture includes an SMF network element 1 and an SMF network element 2. The SMF network element 1 communicates with a UPF network element 1, and the SMF network element 2 communicates with a UPF network element 2. This is not specifically limited in the embodiments of this application. For a manner in which network elements are connected, refer to the non-roaming 5G network architecture shown in FIG. 3a. Details are not described herein again.

[0059] Alternatively, for example, it is assumed that the policy control system 10 shown in FIG. 1, the policy control system 20 shown in FIG. 2, the policy control system 20a shown in FIG. 2a, or the policy control system 20b shown in FIG. 2b is applied to a current home routing 5G network architecture. As shown in FIG. 3b, a network element or an entity corresponding to the foregoing first session management network element or the foregoing second session management network element may be a home SMF (home SMF, H-SMF) network element in the home routing 5G network architecture; a network element or an entity corresponding to the foregoing unified data management network element may be a UDM network element in the home routing 5G network architecture; a network element or an entity corresponding to the foregoing mobility management network element may be an AMF network element in the home routing 5G network architecture; a network element or an entity corresponding to the foregoing binding support network element may be a BSF network element in the home routing 5G network architecture; and a network element or an entity corresponding to the foregoing first policy control network element may be a PCF network element in the home routing 5G network architecture.

[0060] In addition, as shown in FIG. 3b, the home routing 5G network architecture may further include an access device, a visited SMF (visited SMF, V-SMF) network element, a home UPF (home UPF, H-UPF) network element, a visited UPF (visited UPF, V-UPF) network element, a UDR network element, or the like. This is not specifically limited in the embodiments of this application. The terminal, the access device, the AMF network element, the V-SMF network element, and the V-UPF network element belong to a visited public land mobile network (visited public land mobile network, VPLMN). The UDM network element, the UDR network element, the H-SMF network element, the PCF network element, the H-UPF network element, and the BSF network element belong to a home public land mobile network (home public land mobile network, HPLMN).

[0061] As shown in FIG. 3b, the terminal communicates with the AMF network element through N1, the access device communicates with the AMF network element through N2, the access device communicates with the V-UPF network element through N3, the V-UPF network element communicates with the H-UPF network element through an N9 interface (N9 for short), the AMF network element communicates with the V-SMF network element through N11, the AMF network element communicates with the UDM network element through N8, the V-SMF network element communicates with the H-SMF network element through an N16 interface (N16 for short), the H-SMF network element communicates with the PCF network element through N7, the H-SMF network element communicates with the H-UPF network element through N4, the V-SMF network element communicates with the V-UPF network element through N4, the H-SMF network element communicates with the UDM network element through N10, the PCF network element communicates with the UDR network element, and the BSF network element communicates with the PCF network element and the H-SMF network element.

[0062] It should be noted that FIG. 3b merely shows an example that there is one V-SMF network element, one H-SMF network element, one H-UPF network element, and one V-UPF network element. Certainly, the home routing 5G network architecture may include a plurality of V-SMF network elements, a plurality of H-SMF network elements, a plurality of V-UPF network elements, and a plurality of H-UPF network elements. For example, the home routing 5G network architecture includes a V-SMF network element 1, an H-SMF network element 1 communicating with the V-SMF network element 1, a V-SMF network element 2, and an H-SMF network element 2 communicating with the V-SMF network element 2. The V-SMF network element 1 communicates with a V-UPF network element 1, the V-SMF network element 2 communicates with a V-UPF network element 2, the H-SMF network element 1 communicates with an H-UPF network element 1, and the H-SMF network element 2 communicates with an H-UPF network element 2. This is not specifically limited in the embodiments of this application. For a manner in which network elements are connected, refer to the home routing 5G network architecture shown in FIG. 3b. Details are not described herein again.

[0063] It should be noted that names of the network elements or names of interfaces between the network elements in FIG. 3a or FIG. 3b are merely examples. In a specific implementation, a name of a network element or a name of an interface may be another name. This is not specifically limited in the embodiments of this application.

[0064] In addition, it should be noted that, a control plane network element such as the AMF network element, the SMF network element, the H-SMF network element, the V-SMF network element, the UDM network element, the UDR network element, or the PCF network element in the non-roaming 5G network architecture shown in FIG. 3a or in the home routing 5G network architecture shown in FIG. 3b may alternatively perform interaction by using a service-based interface. For example, a service-based interface externally provided by the AMF network element may be Namf; a service-based interface externally provided by the SMF network element may be Nsmf; a service-based interface externally provided by the H-SMF network element may be Nhsmf; a service-based interface externally provided by the V-SMF network element may be Nvsmf; a service-based interface externally provided by the UDM network element may be Nudm; a service-based interface externally provided by the UDR network element may be Nudr; a service-based interface externally provided by the PCF network element may be Npcf; and a service-based interface externally provided by the BSF network element may be Nbsf. For related descriptions, refer to a diagram of a 5G system architecture (5G system architecture) in the 23501 standard. Details are not described herein.

[0065] Optionally, the terminal (terminal) in the embodiments of this application may include various handheld devices, vehicle-mounted devices, wearable devices, and computing devices that have a wireless communication function, or other processing devices connected to a wireless modem. The terminal may further include a subscriber unit (subscriber unit), a cellular phone (cellular phone), a smartphone (smartphone), a wireless data card, a personal digital assistant (personal digital assistant, PDA) computer, a tablet computer, a wireless modem (modem), a handheld (handheld) device, a laptop computer (laptop computer), a cordless phone (cordless phone) or a wireless local loop (wireless local loop, WLL) station, a machine type communication (machine type communication, MTC) terminal, user equipment (user equipment, UE), a mobile station (mobile station, MS), a terminal device (terminal device), relay user equipment, or the like. The relay user equipment may be, for example, a 5G residential gateway (residential gateway, RG). For ease of description, in this application, the devices mentioned above are collectively referred to as terminals.

[0066] Optionally, the access device included in the embodiments of this application is a device that accesses a core network. For example, the access device may be a base station, a broadband network gateway (broadband network gateway, BNG), an aggregation switch, or a non-3rd generation partnership project (3rd generation partnership project, 3GPP) access device. The base station may include base stations in various forms such as a macro base station, a micro base station (also referred to as a small cell), a relay station, and an access point.

[0067] Optionally, in the embodiments of this application, the mobility management network element or the first session management network element in FIG. 1, or the network device or the first session management network element in FIG. 2, or the unified data management network element or the first session management network element in FIG. 2a, or the first policy control network element or the first session management network element in FIG. 2b may be implemented by one device, or may be jointly implemented by a plurality of devices, or may be a function module in one device. This is not specifically limited in the embodiments of this application. It may be understood that the foregoing functions may be network elements in a hardware device, or may be software functions running on dedicated hardware, or may be virtualization functions instantiated on a platform (for example, a cloud platform).

[0068] For example, in the embodiments of this application, the mobility management network element or the first session management network element in FIG. 1, or the network device or the first session management network element in FIG. 2, or the unified data management network element or the first session management network element in FIG. 2a, or the first policy control network element or the first session management network element in FIG. 2b may be implemented by a communications device in FIG. 4. FIG. 4 is a schematic diagram of a hardware structure of a communications device according to an embodiment of this application. The communications device 400 includes a processor 401, a communications line 402, a memory 403, and at least one communications interface (In FIG. 4, that the communications device 400 includes a communications interface 404 is only used as an example for description).

[0069] The processor 401 may be a general-purpose central processing unit (central processing unit, CPU), a microprocessor, an application-specific integrated circuit (application-specific integrated circuit, ASIC), or one or more integrated circuits configured to control execution of a program in solutions of this application.

[0070] The communications line 402 may include a path for transmitting information between the foregoing components.

[0071] The communications interface 404 uses any apparatus such as a transceiver to communicate with another device or a communications network, such as the Ethernet, a radio access network (radio access network, RAN), or a wireless local area network (wireless local area networks, WLAN).

[0072] The memory 403 may be a read-only memory (read-only memory, ROM), another type of static storage device that can store static information and a static instruction, a random access memory (random access memory, RAM), or another type of dynamic storage device that can store information and an instruction, or may be an electrically erasable programmable read-only memory (electrically erasable programmable read-only memory, EEPROM), a compact disc read-only memory (compact disc read-only memory, CD-ROM) or another compact disc storage, an optical disc storage (including a compact disc, a laser disc, an optical disc, a digital versatile disc, a Blu-ray disc, and the like), a magnetic disk storage medium or another magnetic storage device, or any other medium that can be configured to carry or store expected program code in a form of an instruction or a data structure and that can be accessed by a computer. However, this is not limited thereto. The memory may exist independently, and is connected to the processor by using the communications line 402. The memory may alternatively be integrated with the processor.

[0073] The memory 403 is configured to store a computer executable instruction for performing the solutions in this application, and the processor 401 controls execution. The processor 401 is configured to execute the computer executable instruction stored in the memory 403, to implement a policy control method provided in the following embodiments of this application.

[0074] Optionally, the computer executable instruction in this embodiment of this application may also be referred to as application program code. This is not specifically limited in this embodiment of the application.

[0075] In a specific implementation, in an embodiment, the processor 401 may include one or more CPUs, for example, a CPU 0 and a CPU 1 in FIG. 4.

[0076] In a specific implementation, in an embodiment, the communications device 400 may include a plurality of processors, for example, the processor 401 and a processor 408 in FIG. 4. Each of the processors may be a single-core processor (single-CPU), or may be a multi-core processor (multi-CPU). The processor herein may be one or more devices, circuits, and/or processing cores configured to process data (for example, a computer program instruction).

[0077] In a specific implementation, in an embodiment, the communications device 400 may further include an output device 405 and an input device 406. The output device 405 communicates with the processor 401, and may display information in a plurality of manners. For example, the output device 405 may be a liquid crystal display (liquid crystal display, LCD), a light emitting diode (light emitting diode, LED) display device, a cathode ray tube (cathode ray tube, CRT) display device, or a projector (Projector). The input device 406 communicates with the processor 401, and may receive user input in a plurality of manners. For example, the input device 406 may be a mouse, a keyboard, a touchscreen device, or a sensing device.

[0078] The communications device 400 may be a general-purpose device or a dedicated device. In a specific implementation, the communications device 400 may be a desktop computer, a portable computer, a network server, a palmtop computer (personal digital assistant, PDA), a mobile phone, a tablet computer, a wireless terminal device, an embedded device, or a device with a structure similar to that in FIG. 4. A type of the communications device 400 is not limited in this embodiment of this application.

[0079] The policy control method provided in the embodiments of this application is described below in detail with reference to FIG. 1 to FIG. 4.

[0080] It should be noted that in the following embodiments of this application, names of messages between network elements, names of parameters in the messages, or the like are merely examples, and may be other names in a specific implementation. This is not specifically limited in the embodiments of this application.

[0081] First, for example, the policy control system shown in FIG. 1 or the policy control system shown in FIG. 2a is applied to the non-roaming 5G network architecture shown in FIG. 3a, the first session management network element is an SMF network element 2, and the second session management network element is an SMF network element 1. FIG. 5A and FIG. 5B show a policy control method according to an embodiment of this application. The policy control method includes the following steps.

[0082] S501. A terminal sends a PDU session establishment request (PDU session establishment request) 1 to an AMF network element, so that the AMF network element receives the PDU session establishment request 1 from the terminal.

[0083] The PDU session establishment request 1 includes a PDU session identifier 2, and is used to request to establish a second session.

[0084] Optionally, the PDU session establishment request 1 in this embodiment of this application may further include at least one of S-NSSAI or a DNN. This is not specifically limited in this embodiment of this application.

[0085] Optionally, in this embodiment of this application, the AMF network element may determine, based on at least one of subscription data of the terminal, an operator policy, or the PDU session establishment request 1 from the terminal, S-NSSAI and a DNN that correspond to the second session.

[0086] For example, if the PDU session establishment request 1 includes the S-NSSAI and the DNN, the AMF network element may determine, based on the PDU session establishment request 1, the S-NSSAI and the DNN that correspond to the second session.

[0087] Alternatively, for example, if the PDU session establishment request 1 includes the S-NSSAI, the AMF network element may obtain, from the subscription data of the terminal or the operator policy, the DNN corresponding to the second session. Alternatively, for example, if the PDU session establishment request 1 includes the DNN, the AMF network element may obtain, from the subscription data of the terminal or the operator policy, the S-NSSAI corresponding to the second session. In other words, the AMF network element may determine, based on the PDU session establishment request 1 in combination with the subscription data of the terminal or the operator policy, the S-NSSAI and the DNN that correspond to the second session.

[0088] Alternatively, for example, if the PDU session establishment request 1 does not include the S-NSSAI or the DNN, the AMF network element may obtain, from at least one of the subscription data of the terminal or the operator policy, the DNN and the S-NSSAI that correspond to the second session. In other words, the AMF network element may determine, based on the at least one of the subscription data of the terminal or the operator policy, the S-NSSAI and the DNN that correspond to the second session.

[0089] A manner in which the AMF network element determines the S-NSSAI and the DNN that correspond to the second session is not limited in this embodiment of this application.

[0090] S502. The AMF network element selects the SMF network element 1 for the second session.

[0091] Optionally, the AMF network element may further select a PCF network element for the second session. This is not specifically limited in this embodiment of this application.

[0092] For a manner in which the AMF network element selects the SMF network element 1 and the PCF network element for the second session, refer to the prior art. Details are not described herein.

[0093] S503. The AMF network element sends, to the SMF network element 1, a creation request message 1 used to create the second session, so that the SMF network element 1 receives the creation request message 1 from the AMF network element.

[0094] The creation request message 1 includes an identifier of the terminal, the S-NSSAI, the DNN, and the PDU session identifier 2.

[0095] Optionally, if the AMF network element may further select the PCF network element for the second session, the creation request message 1 may further include an identifier of the PCF network element selected by the AMF network element for the second session, and the identifier is represented as PCF Ida. This is not specifically limited in this embodiment of this application.

[0096] For example, in this embodiment of this application, the identifier of the terminal may be, for example, a subscription permanent identifier (subscription permanent identifier, SUPI). A general description is provided herein. This is not specifically limited in this embodiment of this application.

[0097] Optionally, the creation request message 1 in this embodiment of this application may be a PDU session creation session management (session management, SM) context request (PDU session create SM context request) message 1. This is not specifically limited in this embodiment of this application.

[0098] S504. The SMF network element 1 registers the second session with a UDM network element, and the SMF network element 1 obtains, from the UDM network element, session management subscription data (session management subscription data) corresponding to a combination of the identifier of the terminal, the DNN, and the S-NSSAI.

[0099] In addition, optionally, in this embodiment of this application, the SMF network element 1 may further subscribe to a subscription data change notification from the UDM network element. This is not specifically limited in this embodiment of this application.

[0100] For related implementation of step S504, refer to the prior art. Details are not described herein.

[0101] S505. After selecting a PCF network element for the second session, the SMF network element 1 sends a policy control creation request 1 to the PCF network element, so that the PCF network element receives the policy control creation request 1 from the SMF network element 1.

[0102] The policy control creation request 1 may include the identifier of the terminal, the PDU session identifier 2, the DNN, the S-NSSAI, and an internet protocol (Internet Protocol, IP) address 2 assigned by the SMF network element 1 to the second session.

[0103] Optionally, in this embodiment of this application, the SMF network element 1 may select the PCF network element for the second session based on a local policy and the identifier (which is PCF Ida herein) that is of the PCF network element and that is sent by the AMF network element, or in a manner such as performing interaction with a network repository function (network repository function, NRF) network element. For details, refer to an existing implementation. The details are not described herein.

[0104] S506. The PCF network element sends a query request (query request) 1 to a UDR network element, so that the UDR network element receives the query request 1 from the PCF network element.

[0105] The query request 1 includes the identifier of the terminal, the S-NSSAI, and the DNN, and is used to query session policy-related subscription information, for example, PDU session policy control data (PDU session policy control data), and a remaining maximum allowed data amount (remaining allowed usage data). The PDU session policy control data may include, for example, a subscribed guaranteed bit rate (guaranteed bit rate, GBR), and the subscribed GBR indicates a maximum guaranteed bandwidth that is allowed to be authorized by the PCF network element to the terminal. The remaining maximum allowed data amount indicates remaining usage that is allowed to be authorized by the PCF network element to the terminal.

[0106] Optionally, in this embodiment of this application, the PCF network element may further subscribe to a data change notification from the UDR network element. After receiving a subscription request, the UDR network element returns an acknowledgement message to the PCF network element. This is not specifically limited in this embodiment of this application. A data change herein is a change in the session policy-related subscription information. A general description is provided herein. This is not specifically limited in this embodiment of this application.

[0107] S507. The UDR network element sends a query response (query response) 1 to the PCF network element, so that the PCF network element receives the query response 1 from the UDR network element.

[0108] The query response 1 includes the session policy-related subscription information.

[0109] S508. The PCF network element makes a policy decision based on the obtained session policy-related subscription information, and after formulating a PCC rule and another PDU session-related policy, the PCF network element sends a policy control creation response (policy control created response) 1 to the SMF network element 1, so that the SMF network element 1 receives the policy control creation response 1 from the PCF network element.

[0110] The policy control creation response 1 includes a session policy formulated by the PCF network element.

[0111] S509. The PCF network element performs management registration with a BSF network element.

[0112] Specifically, the PCF network element may send a management registration request (management register request) to the BSF network element. The management registration request includes the identifier of the terminal, the DNN, the S-NSSAI, an identifier of the PCF network element selected by the SMF network element 1 for the second session, and the IP address 2 assigned by the SMF network element 1 to the second session. Further, after storing a correspondence among the identifier of the terminal, the DNN, the S-NSSAI, the identifier of the PCF network element, and the IP address 2, the BSF network element sends a management registration response (management register response) to the PCF network element.

[0113] S510. The SMF network element 1 formulates, based on the received session policy, a related policy (for example, a PDR, and an associated QER, URR, or FAR) to be executed on a user plane. In addition, the SMF network element 1 selects a UPF network element 1 for the second session, interacts with the UPF network element 1 to establish an N4 session, and sends the formulated policy to be executed on the user plane to the UPF network element 1. For related implementation, refer to the prior art. Details are not described herein.

[0114] S511. The SMF network element 1 sends a creation response message 1 to the AMF network element, so that the AMF network element receives the creation response message 1 from the SMF network element 1.

[0115] The creation response message 1 includes the IP address 2 assigned by the SMF network element 1 to the second session and other information. For details, refer to the prior art. The details are not described herein.

[0116] Optionally, the creation response message 1 in this embodiment of this application may be, for example, a PDU session creation SM context response (PDU session create SM context response) message 1. This is not specifically limited in this embodiment of this application.

[0117] S512. The AMF network element interacts with an access device, the terminal, or the like, to complete a subsequent establishment procedure of the second session. For related implementation, refer to the prior art. Details are not described herein.

[0118] S513. The terminal determines that a first session that has the same S-NSSAI and the same DNN as the established second session of the terminal needs to be established.

[0119] In this embodiment of this application, the terminal may determine, after being triggered by a network or the terminal, that the first session that has the same S-NSSAI and the same DNN as the established second session of the terminal needs to be established. This is not specifically limited in this embodiment of this application.

[0120] S514. The terminal sends a PDU session establishment request 2 to the AMF network element, so that the AMF network element receives the PDU session establishment request 2 from the terminal.

[0121] The PDU session establishment request 2 includes a PDU session identifier 1, and is used to request to establish the first session.

[0122] Optionally, the PDU session establishment request 2 in this embodiment of this application may further include the at least one of the S-NSSAI or the DNN. This is not specifically limited in this embodiment of this application.

[0123] For a manner in which the AMF network element determines the S-NSSAI and the DNN that correspond to the first session, refer to the manner in which the AMF network element determines the S-NSSAI and the DNN that correspond to the second session in step S501. Details are not described herein again.

[0124] S515. The AMF network element selects the SMF network element 2 for the first session.

[0125] Optionally, the AMF network element may further select a PCF network element for the first session. This is not specifically limited in this embodiment of this application.

[0126] For a manner in which the AMF network element selects the SMF network element 1 and the PCF network element for the first session, refer to the prior art. Details are not described herein.

[0127] It should be noted that in this embodiment of this application, the AMF network element may select different SMF network elements for different sessions of the terminal because load balancing of the SMF network element is considered, the SMF network element needs to be disabled, or the like. This is not specifically limited in this embodiment of this application.

[0128] S516. The AMF network element sends, to the SMF network element 2, a creation request message 2 used to create the first session, so that the SMF network element 2 receives the creation request message 2 from the AMF network element.

[0129] The creation request message 2 includes the identifier of the terminal, the S-NSSAI, the DNN, and the PDU session identifier 1.

[0130] Optionally, if the AMF network element may further select the PCF network element for the first session, the creation request message 2 may further include an identifier of the PCF network element selected by the AMF network element for the first session, and the identifier is represented as PCF Ida. This is not specifically limited in this embodiment of this application.

[0131] Optionally, in this embodiment of this application, if the AMF network element determines that the first session that is of the terminal and that is being established has the same S-NSSAI and the same DNN as the established second session of the terminal, the creation request message 2 may further include indication information. The indication information is used to instruct the SMF network element 2 to obtain the identifier of the PCF network element from the BSF network element; or the indication information is used to indicate that a session that is of the terminal and that has the same S-NSSAI and the same DNN as the first session is established; or the indication information is used to indicate that the first session has corresponding PCF binding information. The PCF binding information is a correspondence between the identifier of the PCF network element and a combination of the identifier of the terminal, the S-NSSAI, and the DNN. In this case, after receiving the indication information, the SMF network element 2 may request, from the BSF network element, the identifier that is of the PCF network element and that corresponds to the identifier of the terminal, the S-NSSAI, and the DNN. This is not specifically limited in this embodiment of this application.

[0132] Optionally, in this embodiment of this application, after determining that the terminal establishes the first session in a non-roaming scenario, the AMF network element may add the indication information to the creation request message 2 sent to the SMF network element 2. This is not specifically limited in this embodiment of this application. For example, that the AMF network element determines that the terminal establishes the first session in the non-roaming scenario may be as follows: The AMF network element determines that the terminal that establishes the first session is located in a home network. A description is provided herein. Details are not described below again.

[0133] Optionally, in this embodiment of this application, that the AMF network element determines that the first session that is of the terminal and that is being established has the same S-NSSAI and the same DNN as the established second session of the terminal may specifically include: The AMF network element determines, based on at least one of the subscription data of the terminal, the operator policy, and the PDU session establishment request 2 from the terminal, that the first session that is of the terminal and that is being established has the same S-NSSAI and the same DNN as the established second session of the terminal.

[0134] For example, the AMF network element may determine, based on the at least one of the subscription data of the terminal, the operator policy, or the PDU session establishment request 2 from the terminal, the S-NSSAI and the DNN that correspond to the first session. Further, the AMF network element determines, based on the S-NSSAI and the DNN that correspond to the first session, and the S-NSSAI and the DNN that correspond to the second session, that the first session that is of the terminal and that is being established has the same S-NSSAI and the same DNN as the established second session of the terminal.

[0135] For a manner in which the AMF network element determines, based on the at least one of the subscription data of the terminal, the operator policy, or the PDU session establishment request 2 from the terminal, the S-NSSAI and the DNN that correspond to the first session, refer to the foregoing embodiment. Details are not described herein again.

[0136] Optionally, the creation request message 2 in this embodiment of this application may be, for example, a PDU session creation session management SM context request message 2. This is not specifically limited in this embodiment of this application.

[0137] Optionally, in this embodiment of this application, that the AMF network element determines that the first session that is of the terminal and that is being established has the same S-NSSAI and the same DNN as the established second session of the terminal may alternatively be replaced with a case in which the AMF network element determines that the first session has the corresponding PCF binding information. The PCF binding information is the correspondence between the identifier of the PCF network element and the combination of the identifier of the terminal, the S-NSSAI, and the DNN. This is not specifically limited in this embodiment of this application.

[0138] S517. The SMF network element 2 registers the first session with the UDM network element, and the SMF network element 2 obtains, from the UDM network element, session management subscription data corresponding to the combination of the identifier of the terminal, the DNN, and the S-NSSAI.

[0139] In addition, optionally, in this embodiment of this application, the SMF network element 2 may further subscribe to the subscription data change notification from the UDM network element. This is not specifically limited in this embodiment of this application.

[0140] Optionally, in this embodiment of this application, if the UDM network element determines that the first session that is of the terminal and that is being established has the same S-NSSAI and the same DNN as the established second session of the terminal, the UDM network element further sends indication information to the SMF network element 2. The indication information is used to instruct the SMF network element 2 to obtain the identifier of the PCF network element from the BSF network element; or the indication information is used to indicate that a session that is of the terminal and that has the same S-NSSAI and the same DNN as the first session is established; or the indication information is used to indicate that the first session has the corresponding PCF binding information. The PCF binding information is the correspondence between the identifier of the PCF network element and the combination of the identifier of the terminal, the S-NSSAI, and the DNN. In this case, after receiving the indication information, the SMF network element 2 may request, from the BSF network element, the identifier that is of the PCF network element and that corresponds to the identifier of the terminal, the S-NSSAI, and the DNN

[0141] Optionally, in this embodiment of this application, if the UDM network element determines that the first session that is of the terminal and that is being established has the same S-NSSAI and the same DNN as the established second session of the terminal, the UDM network element may send the indication information to the SMF network element 2 after determining that the terminal establishes the first session in the non-roaming scenario. This is not specifically limited in this embodiment of this application. For example, that the UDM network element determines that the terminal establishes the first session in the non-roaming scenario may be as follows: The UDM network element determines that the terminal that establishes the first session is located in the home network. A description is provided herein. Details are not described below again.

[0142] Optionally, in this embodiment of this application, that the UDM network element determines that the first session that is of the terminal and that is being established has the same S-NSSAI and the same DNN as the established second session of the terminal may alternatively be replaced with a case in which the UDM network element determines that the first session has the corresponding PCF binding information. The PCF binding information is the correspondence between the identifier of the PCF network element and the combination of the identifier of the terminal, the S-NSSAI, and the DNN. This is not specifically limited in this embodiment of this application.

[0143] For related implementation of step S517, refer to the prior art. Details are not described herein.

[0144] S518. The SMF network element 2 sends a management discovery request (management discovery request) to the BSF network element based on a configuration, so that the BSF network element receives the management discovery request from the SMF network element 2.

[0145] The management discovery request includes the identifier of the terminal, the S-NSSAI, and the DNN, and is used to request the identifier that is of the PCF network element and that corresponds to the identifier of the terminal, the S-NSSAI, and the DNN

[0146] S519. The BSF network element sends a management discovery response (management discovery response) to the SMF network element 2, so that the SMF network element 2 receives the management discovery response from the BSF network element.

[0147] The management discovery response includes the identifier that is of the PCF network element and that corresponds to the identifier of the terminal, the S-NSSAI, and the DNN

[0148] Optionally, in this embodiment of this application, the BSF network element may determine, based on the identifier of the terminal, the S-NSSAI, and the DNN that are carried in the management discovery request, and in combination with the prestored correspondence between the PCF network element and the combination of the identifier of the terminal, the S-NSSAI, and the DNN, the identifier that is of the PCF network element and that corresponds to the identifier of the terminal, the S-NSSAI, and the DNN. This is not specifically limited in this embodiment of this application.

[0149] Optionally, in this embodiment of this application, the SMF network element 2 may always interact with the BSF network element based on the configuration in the foregoing manner, to attempt to obtain the identifier that is of the PCF network element and that corresponds to the identifier of the terminal, the S-NSSAI, and the DNN. If no sessions of the terminal have a same DNN and same S-NSSAI, the BSF network element does not return an identifier of any PCF network element. In this case, the SMF network element 2 may select the PCF network element in another manner. For example, the SMF network element 2 selects the PCF network element based on a local configuration, the identifier that is of the PCF network element and that is provided by the AMF network element, or an identifier that is of the PCF network element and that is provided by the NRF network element. This is not specifically limited in this embodiment of this application.

[0150] Optionally, in this embodiment of this application, if the creation request message 2 in step S516 includes the indication information, or the UDM network element sends the indication information to the SMF 2 in step S517, the SMF network element 2 may send the management discovery request to the BSF network element based on the indication information, and therefore, obtain the corresponding identifier of the PCF network element. This is not specifically limited in this embodiment of this application.

[0151] S520. The SMF network element 2 sends a policy control creation request 2 to the corresponding PCF network element based on the identifier of the PCF network element, so that the PCF network element receives the policy control creation request 2 from the SMF network element 2.

[0152] The policy control creation request 2 may include the identifier of the terminal, the PDU session identifier 1, the DNN, the S-NSSAI, and an IP address 1 assigned by the SMF network element 2 to the first session.

[0153] S521. The PCF network element sends a policy control creation response 2 to the SMF network element 2, so that the SMF network element 2 receives the policy control creation response 2 from the PCF network element.

[0154] The policy control creation response 2 includes a session policy formulated by the PCF network element.

[0155] S522. The SMF network element 2 formulates, based on the received session policy, a related policy (for example, a PDR, and an associated QER, URR, or FAR) to be executed on the user plane. In addition, the SMF network element 2 selects a UPF network element 2 for the first session, interacts with the UPF network element 2 to establish an N4 session, and sends the formulated policy to be executed on the user plane to the UPF network element 2. For related implementation, refer to the prior art. Details are not described herein.

[0156] S523. The SMF network element 2 sends a creation response message 2 to the AMF network element, so that the AMF network element receives the creation response message 2 from the SMF network element 2.

[0157] The creation response message 2 includes the IP address 1 assigned by the SMF network element 2 to the first session and other information. For details, refer to the prior art. The details are not described herein.

[0158] Optionally, the creation response message 2 in this embodiment of this application may be, for example, a PDU session creation SM context response message 2. This is not specifically limited in this embodiment of this application.

[0159] S524. The AMF network element interacts with the access device, the terminal, or the like, to complete a subsequent establishment procedure of the first session. For related implementation, refer to the prior art. Details are not described herein.

[0160] According to the policy control method provided in this embodiment of this application, it can be ensured that a same PCF network element is selected for a plurality of sessions of a same terminal that have same S-NSSAI and a same DNN. Therefore, a conflict between policies formulated for the plurality of PDU sessions of the same terminal that have the same S-NSSAI and the same DNN and the subscription information obtained from the UDR network element can be avoided. For an analysis of a related technical effect, refer to the foregoing policy control system part. Details are not described herein again.

[0161] Actions of the AMF network element or actions of the SMF network element 2 in steps S501 to S524 may be performed by the processor 401 in the communications device 400 shown in FIG. 4 by invoking the application program code stored in the memory 403. This is not limited in this embodiment.

[0162] Optionally, for example, the policy control system shown in FIG. 1 is applied to the home routing 5G network architecture shown in FIG. 3b, the first session management network element is an H-SMF network element 2, and the second session management network element is an H-SMF network element 1. An embodiment of this application may further provide a policy control method similar to the embodiment shown in FIG. 5A and FIG. 5B. For example, a difference lies in the following: The SMF network element 1 in the embodiment shown in FIG. 5A and FIG. 5B is replaced with the H-SMF network element 1 in this embodiment of this application, the SMF network element 2 shown in FIG. 5A and FIG. 5B is replaced with the H-SMF network element 2 in this embodiment of this application, the UPF network element 1 in the embodiment shown in FIG. 5A and FIG. 5B is replaced with an H-UPF network element 1 in this embodiment of this application, and the UPF network element 2 in the embodiment shown in FIG. 5A and FIG. 5B is replaced with an H-UPF network element 2 in this embodiment of this application. Correspondingly, when selecting the H-SMF network element 1, the AMF network element needs to select a V-SMF network element 1 in a visited place. Information exchanged between the AMF network element and the H-SMF network element 1 needs to be forwarded by the V-SMF network element 1. When selecting the H-SMF network element 2, the AMF network element needs to select a V-SMF network element 2 in the visited place (the V-SMF network element 1 and the V-SMF network element 2 may be the same or different, and this is not specifically limited in this embodiment of this application). Information exchanged between the AMF network element and the H-SMF network element 2 needs to be forwarded by the V-SMF network element 2. For example, the AMF network element sends, to the H-SMF network element 1 by using the V-SMF network element 1, a creation request message 1 used to create a second session, so that the H-SMF network element 1 receives the creation request message 1 from the AMF network element. The AMF network element sends, to the H-SMF network element 2 by using the V-SMF network element 2, a creation request message 2 used to create a first session, so that the H-SMF network element 2 receives the creation request message 2 from the AMF network element. In addition, the H-SMF network element 1 and the H-SMF network element 2 interact with a UDM network element, to register the second session and the first session respectively. Optionally, after determining that a terminal establishes the first session in a home routing scenario, the AMF network element may add indication information to the creation request message 2 sent to the H-SMF network element 2 by using the V-SMF network element 2. The indication information is used to instruct the H-SMF network element 2 to obtain an identifier of a PCF network element from a BSF network element; or the indication information is used to indicate that a session that is of the terminal and that has the same S-NSSAI and the same DNN as the first session is established; or the indication information is used to indicate that the first session has corresponding binding information. For example, that the AMF network element determines that the terminal establishes the first session in the home routing scenario may be: determining, based on the at least one of subscription data of the terminal, an operator policy, and a PDU session establishment request 2 from the terminal, that the terminal establishes the first session in the home routing scenario. For other related descriptions, refer to the embodiment shown in FIG. 5A and FIG. 5B. Details are not described herein again. Optionally, after determining that a terminal establishes the first session in a home routing scenario, the UDM network element may add indication information to an answer message that is of a registration request and that is sent to the H-SMF network element 2. The indication information is used to instruct the H-SMF network element 2 to obtain an identifier of a PCF network element from a BSF network element; or the indication information is used to indicate that a session that is of the terminal and that has the same S-NSSAI and the same DNN as the first session is established; or the indication information is used to indicate that the first session has corresponding binding information. For example, that the UDM network element determines that the terminal establishes the first session in the home routing scenario may be as follows: The UDM network element determines that the H-SMF network element 2 that requests to perform registration is an SMF network element located in a home network. For other related descriptions, refer to the embodiment shown in FIG. 5A and FIG. 5B. Details are not described herein again.

[0163] Optionally, for example, the policy control system shown in FIG. 2 is applied to the 5G network shown in FIG. 3a, the first session management network element is an SMF network element 2, the second session management network element is an SMF network element 1, and the network device is an AMF network element. FIG. 6A and FIG. 6B show a policy control method according to an embodiment of this application. The policy control method includes the following steps.

[0164] Steps S601 to S608 are the same as steps S501 to S508 in the embodiment shown in FIG. 5A and FIG. 5B. For related descriptions, refer to the embodiment shown in FIG. 5A and FIG. 5B. Details are not described herein again.

[0165] Step S609 is the same as step S510 in the embodiment shown in FIG. 5A and FIG. 5B. For related descriptions, refer to the embodiment shown in FIG. 5A and FIG. 5B. Details are not described herein again.

[0166] Step S610 is similar to step S511 in the embodiment shown in FIG. 5A and FIG. 5B. For example, a difference lies in the following: In this embodiment of this application, a creation response message 1 needs to carry an identifier of the PCF network element selected by the SMF network element 1 for the second session. In this case, after receiving the creation response message 1, the AMF network element may store a correspondence between the identifier of the PCF network element and a combination of an identifier of a terminal, S-NSSAI, and a DNN. For other related descriptions, refer to the embodiment shown in FIG. 5A and FIG. 5B. Details are not described herein again.

[0167] Steps S611 to S614 are the same as steps S512 to S515 in the embodiment shown in FIG. 5A and FIG. 5B. For related descriptions, refer to the embodiment shown in FIG. 5A and FIG. 5B. Details are not described herein again.

[0168] S615. Optionally, the AMF network element determines that the terminal establishes the first session in the non-roaming scenario. For related descriptions, refer to step S516 in the embodiment shown in FIG. 5A and FIG. 5B. Details are not described herein again.

[0169] S616. If the AMF network element determines that the first session that is of the terminal and that is being established has the same S-NSSAI and the same DNN as the established second session of the terminal, the AMF network element sends, to the SMF network element 2, a creation request message 2 used to create the first session, so that the SMF network element 2 receives the creation request message 2 from the AMF network element.

[0170] The creation request message 2 includes the identifier of the terminal, the S-NSSAI, the DNN, the identifier of the PCF network element selected by the SMF network element 1 for the second session, and a PDU session identifier 1.

[0171] For a manner in which the AMF network element determines that the first session that is of the terminal and that is being established has the same S-NSSAI and the same DNN as the established second session of the terminal, refer to the embodiment shown in FIG. 5A and FIG. 5B. Details are not described herein again.

[0172] Optionally, in this embodiment of this application, the AMF network element may determine, based on the obtained identifier of the terminal, the S-NSSAI, and the DNN, and in combination with the prestored correspondence between the PCF network element and a combination of an identifier of a terminal, S-NSSAI, and a DNN, the identifier that is of the PCF network element and that corresponds to the identifier of the terminal, the S-NSSAI, and the DNN, namely, the identifier of the PCF network element selected by the SMF network element 1 for the second session. This is not specifically limited in this embodiment of this application.

[0173] Optionally, if the AMF network element may further select a PCF network element for the first session, the creation request message 2 may further include an identifier of the PCF network element selected by the AMF network element for the first session, and the identifier is represented as PCF Ida. This is not specifically limited in this embodiment of this application.

[0174] To distinguish, from an identifier of a PCF network element selected by an AMF in the prior art, the identifier of the PCF network element selected by the SMF network element 1 for the second session, in a possible implementation, a special field in a message carries the identifier of the PCF network element selected by the SMF network element 1 for the second session, to indicate that the PCF network element corresponding to the identifier of the PCF network element is a PCF network element selected by an SMF network element. This is not specifically limited in this embodiment of this application. The special field may be an existing field in the message, or may be a newly added field. This is not limited herein.

[0175] Alternatively, to distinguish, from an identifier of a PCF network element selected by an AMF in the prior art, the identifier of the PCF network element selected by the SMF network element 1 for the second session, in a possible implementation, indication information may be added to the creation request message 2. The indication information is used to indicate that the PCF network element corresponding to the identifier of the PCF network element is the PCF network element selected by the SMF network element 1; or the indication information is used to instruct the SMF network element 2 to select the PCF network element corresponding to the identifier of the PCF network element. This is not specifically limited in this embodiment of this application.

[0176] Step S617 is the same as step S517 in the embodiment shown in FIG. 5A and FIG. 5B. For related descriptions, refer to the embodiment shown in FIG. 5A and FIG. 5B. Details are not described herein again.

[0177] Steps S618 to S622 are the same as steps S520 to S524 in the embodiment shown in FIG. 5A and FIG. 5B. For related descriptions, refer to the embodiment shown in FIG. 5A and FIG. 5B. Details are not described herein again.

[0178] According to the policy control method provided in this embodiment of this application, it can be ensured that a same PCF network element is selected for a plurality of sessions of a same terminal that have same S-NSSAI and a same DNN. Therefore, a conflict between policies formulated for the plurality of PDU sessions of the same terminal that have the same S-NSSAI and the same DNN and subscription information obtained from a UDR network element can be avoided. For an analysis of a related technical effect, refer to the foregoing policy control system part. Details are not described herein again.

[0179] Actions of the AMF network element or actions of the SMF network element 2 in steps S601 to S622 may be performed by the processor 401 in the communications device 400 shown in FIG. 4 by invoking the application program code stored in the memory 403. This is not limited in this embodiment.

[0180] Optionally, for example, the policy control system shown in FIG. 2 is applied to the home routing 5G network architecture shown in FIG. 3b, the first session management network element is an H-SMF network element 2, the second session management network element is an H-SMF network element 1, and the network device is an AMF network element. An embodiment of this application may further provide a policy control method similar to the embodiment shown in FIG. 6A and FIG. 6B. For example, a difference lies in the following: The SMF network element 1 in the embodiment shown in FIG. 6A and FIG. 6B is replaced with the H-SMF network element 1 in this embodiment of this application, the SMF network element 2 shown in FIG. 6A and FIG. 6B is replaced with the H-SMF network element 2 in this embodiment of this application, the UPF network element 1 in the embodiment shown in FIG. 6A and FIG. 6B is replaced with an H-UPF network element 1 in this embodiment of this application, and the UPF network element 2 in the embodiment shown in FIG. 6A and FIG. 6B is replaced with an H-UPF network element 2 in this embodiment of this application. Correspondingly, when selecting the H-SMF network element 1, the AMF network element needs to select a V-SMF network element 1 in a visited place. Information exchanged between the AMF network element and the H-SMF network element 1 needs to be forwarded by the V-SMF network element 1. When selecting the H-SMF network element 2, the AMF network element needs to select a V-SMF network element 2 in the visited place (the V-SMF network element 1 and the V-SMF network element 2 may be the same or different, and this is not specifically limited in this embodiment of this application). Information exchanged between the AMF network element and the H-SMF network element 2 needs to be forwarded by the V-SMF network element 2. For example, the AMF network element sends, to the H-SMF network element 1 by using the V-SMF network element 1, a creation request message 1 used to create a second session, so that the H-SMF network element 1 receives the creation request message 1 from the AMF network element. The AMF network element sends, to the H-SMF network element 2 by using the V-SMF network element 2, a creation request message 2 used to create a first session, so that the H-SMF network element 2 receives the creation request message 2 from the AMF network element. Optionally, after determining that a terminal establishes the first session in a home routing scenario, the AMF network element may perform a step similar to step S616. For example, that the AMF network element determines that the terminal requests to establish the first session in the home routing scenario may be: determining, based on at least one of subscription data of the terminal, an operator policy, and a PDU session establishment request 2 from the terminal, that the terminal establishes the first session in the home routing scenario. For other related descriptions, refer to the embodiment shown in FIG. 6A and FIG. 6B. Details are not described herein again.

[0181] Optionally, for example, the policy control system shown in FIG. 2 is applied to the 5G network shown in FIG. 3a, the first session management network element is an SMF network element 2, the second session management network element is an SMF network element 1, and the network device is a UDM network element. FIG. 7A and FIG. 7B show a policy control method according to an embodiment of this application. The policy control method includes the following steps.

[0182] Steps S701 to S703 are the same as steps S501 to S503 in the embodiment shown in FIG. 5A and FIG. 5B. For related descriptions, refer to the embodiment shown in FIG. 5A and FIG. 5B. Details are not described herein again.

[0183] Optionally, in this embodiment of this application, the AMF network element may add indication information in step S703. The indication information is used to instruct the SMF network element 1 to preferably select a PCF network element. This is not specifically limited in this embodiment of this application.

[0184] Step S704 is similar to step S504 in the embodiment shown in FIG. 5A and FIG. 5B. For example, a difference lies in the following: In this embodiment of this application, the SMF 1 selects the PCF network element based on a configuration, and when the SMF network element 1 performs registration with the UDM network element, an identifier of a PCF network element selected by the SMF network element 1 for the second session needs to be carried. In this case, the UDM network element may store a correspondence between the identifier of the PCF network element and a combination of an identifier of the terminal, S-NSSAI, and a DNN. For other related descriptions, refer to the embodiment shown in FIG. 5A and FIG. 5B. Details are not described herein again.

[0185] Optionally, in this embodiment of this application, if the indication information is included in step S703, the SMF network element 1 may preferably select the PCF network element based on the indication information, and then perform step S704. This is not specifically limited in this embodiment of this application.

[0186] Optionally, in this embodiment of this application, if the SMF network element 1 does not preferably select the PCF network element, a request message for performing, by the SMF network element 1, registration with the UDM network element does not carry the identifier of the PCF network element. Instead, after selecting the PCF network element, the SMF network element 1 sends, to the UDM network element, the request message that carries the identifier of the PCF network element selected by the SMF network element 1 for the second session. This is not specifically limited in this embodiment of this application.

[0187] Steps S705 to S708 are the same as steps S505 to S508 in the embodiment shown in FIG. 5A and FIG. 5B. For related descriptions, refer to the embodiment shown in FIG. 5A and FIG. 5B. Details are not described herein again.

[0188] Steps S709 to S714 are the same as steps S510 to S515 in the embodiment shown in FIG. 5A and FIG. 5B. For related descriptions, refer to the embodiment shown in FIG. 5A and FIG. 5B. Details are not described herein again.

[0189] S715. The AMF network element sends, to the SMF network element 2, a creation request message 2 used to create the first session, so that the SMF network element 2 receives the creation request message 2 from the AMF network element.

[0190] The creation request message 2 includes the identifier of the terminal, the S-NSSAI, the DNN, and a PDU session identifier 1.

[0191] Optionally, if the AMF network element may further select a PCF network element for the first session, the creation request message 2 may further include an identifier of the PCF network element selected by the AMF network element for the first session, and the identifier is represented as PCF Ida. This is not specifically limited in this embodiment of this application.

[0192] Step S716 is similar to step S517 in the embodiment shown in FIG. 5A and FIG. 5B. For example, a difference lies in the following: In this embodiment of this application, when the SMF network element 2 performs registration with the UDM network element, if the UDM network element determines that the first session that is of the terminal and that is being established has the same S-NSSAI and the same DNN as the established second session of the terminal, the UDM network element may determine, based on the identifier of the terminal, the S-NSSAI, and the DNN that are carried in a registration request and in combination with the prestored correspondence between the PCF network element and a combination of an identifier of the terminal, S-NSSAI, and a DNN, the identifier that is of the PCF network element and that corresponds to the identifier of the terminal, the S-NSSAI, and the DNN, and further send the identifier of the PCF network element to the SMF network element 2. This is not specifically limited in this embodiment of this application.

[0193] Optionally, in this embodiment of this application, the UDM network element may determine, based on the identifier of the terminal, the S-NSSAI, and the DNN that are carried in the registration request sent when the SMF network element 2 performs registration with the UDM network element, that the first session that is of the terminal and that is being established has the same S-NSSAI and the same DNN as the established second session of the terminal. This is not specifically limited in this embodiment of this application.

[0194] Optionally, in this embodiment of this application, after determining that the terminal establishes the first session in a non-roaming scenario, the UDM network element may send, to the SMF network element 2, the identifier that is of the PCF network element and that corresponds to the identifier of the terminal, the S-NSSAI, and the DNN. This is not specifically limited in this embodiment of this application. For example, that the UDM network element determines that the terminal establishes the first session in the non-roaming scenario may be as follows: The UDM network element determines that the SMF network element 2 that requests to perform registration is an SMF network element located in a home network. A description is provided herein. Details are not described below again.

[0195] Optionally, in this embodiment of this application, that the UDM network element determines that the first session that is of the terminal and that is being established has the same S-NSSAI and the same DNN as the established second session of the terminal may alternatively be replaced with a case in which the UDM network element determines that the first session has corresponding PCF binding information. The PCF binding information is the correspondence between the identifier of the PCF network element and a combination of an identifier of the terminal, S-NSSAI, and a DNN. This is not specifically limited in this embodiment of this application.

[0196] Steps S717 to S721 are the same as steps S520 to S524 in the embodiment shown in FIG. 5A and FIG. 5B. For related descriptions, refer to the embodiment shown in FIG. 5A and FIG. 5B. Details are not described herein again.

[0197] According to the policy control method provided in this embodiment of this application, it can be ensured that a same PCF network element is selected for a plurality of sessions of a same terminal that have same S-NSSAI and a same DNN. Therefore, a conflict between policies formulated for the plurality of PDU sessions of the same terminal that have the same S-NSSAI and the same DNN and subscription information obtained from a UDR network element can be avoided. For an analysis of a related technical effect, refer to the foregoing policy control system part. Details are not described herein again.

[0198] Actions of the UDM network element or actions of the SMF network element 2 in steps S701 to S721 may be performed by the processor 401 in the communications device 400 shown in FIG. 4 by invoking the application program code stored in the memory 403. This is not limited in this embodiment.

[0199] Optionally, for example, the policy control system shown in FIG. 2 is applied to the home routing 5G network architecture shown in FIG. 3b, the first session management network element is an H-SMF network element 2, the second session management network element is an H-SMF network element 1, and the network device is a UDM network element. An embodiment of this application may further provide a policy control method similar to the embodiment shown in FIG. 7A and FIG. 7B. For example, a difference lies in the following: The SMF network element 1 in the embodiment shown in FIG. 7A and FIG. 7B is replaced with the H-SMF network element 1 in this embodiment of this application, the SMF network element 2 shown in FIG. 7A and FIG. 7B is replaced with the H-SMF network element 2 in this embodiment of this application, the UPF network element 1 in the embodiment shown in FIG. 7A and FIG. 7B is replaced with an H-UPF network element 1 in this embodiment of this application, and the UPF network element 2 in the embodiment shown in FIG. 7A and FIG. 7B is replaced with an H-UPF network element 2 in this embodiment of this application. Correspondingly, when selecting the H-SMF network element 1, the AMF network element needs to select a V-SMF network element 1 in a visited place. Information exchanged between the AMF network element and the H-SMF network element 1 needs to be forwarded by the V-SMF network element 1. When selecting the H-SMF network element 2, the AMF network element needs to select a V-SMF network element 2 in the visited place (the V-SMF network element 1 and the V-SMF network element 2 may be the same or different, and this is not specifically limited in this embodiment of this application). Information exchanged between the AMF network element and the H-SMF network element 2 needs to be forwarded by the V-SMF network element 2. For example, the AMF network element sends, to the H-SMF network element 1 by using the V-SMF network element 1, a creation request message 1 used to create a second session, so that the H-SMF network element 1 receives the creation request message 1 from the AMF network element. The AMF network element sends, to the H-SMF network element 2 by using the V-SMF network element 2, a creation request message 2 used to create a first session, so that the H-SMF network element 2 receives the creation request message 2 from the AMF network element. Optionally, after determining that a terminal establishes a first session in a home routing scenario, the UDM network element may send, to the H-SMF network element 2, an identifier that is of a PCF network element and that corresponds to an identifier of a terminal, S-NSSAI, and a DNN. This is not specifically limited in this embodiment of this application. For example, that the UDM network element determines that the terminal establishes the first session in the home routing scenario may be as follows: The UDM network element determines that an H-SMF network element 2 that requests to perform registration is an SMF network element located in a home network. For other related descriptions, refer to the embodiment shown in FIG. 7A and FIG. 7B. Details are not described herein again.

[0200] It should be noted that descriptions, in FIG. 7A and FIG. 7B, of a difference between a case in which the policy control system shown in FIG. 2 is applied to the 5G network shown in FIG. 3a and a case in which the policy control system shown in FIG. 2 is applied to the home routing 5G network architecture shown in FIG. 3b is also applicable to the following FIG. 12A and FIG. 12B to FIG. 14A and FIG. 14B. A description is provided herein. Details are not described below again.

[0201] Optionally, for example, the policy control system shown in FIG. 2 is applied to the 5G network shown in FIG. 3a, the first session management network element is an SMF network element 2, the second session management network element is an SMF network element 1, and the network device is a UDM network element. FIG. 12A and FIG. 12B show a policy control method according to an embodiment of this application. The policy control method includes the following steps.

[0202] Steps S1201 to S1203 are the same as steps S501 to S503 in the embodiment shown in FIG. 5A and FIG. 5B. For related descriptions, refer to the embodiment shown in FIG. 5A and FIG. 5B. Details are not described herein again.

[0203] S1204. The SMF network element 1 registers the second session with the UDM network element, and the SMF network element 1 obtains, from the UDM network element, session management subscription data corresponding to a combination of an identifier of the terminal, a DNN, and S-NSSAI.

[0204] Optionally, in this embodiment of this application, if the UDM network element has no corresponding session management subscription data, the UDM network element further queries a UDR network element, and the UDR network element returns, to the UDM network element, the session management subscription data corresponding to the combination of the identifier of the terminal, the DNN, and the S-NSSAI. Therefore, the UDM network element further returns, to the SMF network element 1, the session management subscription data corresponding to the combination of the identifier of the terminal, the DNN, and the S-NSSAI.

[0205] Optionally, in this embodiment of this application, the SMF network element 1 may further subscribe to a subscription data change notification from the UDM network element. Optionally, the UDM network element may further subscribe to a subscription data change notification from the UDR network element.

[0206] Optionally, in this embodiment of this application, the SMF network element 1 may further subscribe to a PCF binding information change notification from the UDM network element. Optionally, the UDM network element may further subscribe to a PCF binding information change notification from the UDR network element. The PCF binding information is a correspondence between a corresponding identifier of a PCF network element and a combination of an identifier of a terminal, a DNN, and S-NSSAI.

[0207] Step S1205 is the same as step S505 in the embodiment shown in FIG. 5A and FIG. 5B. For related descriptions, refer to the embodiment shown in FIG. 5A and FIG. 5B. Details are not described herein again.

[0208] S1206. The PCF network element sends a query request 1 to the UDR network element, so that the UDR network element receives the query request 1 from the PCF network element.

[0209] The query request 1 carries the identifier of the terminal, the S-NSSAI, and the DNN, and is used to query session policy-related subscription information. For related descriptions of the session policy-related subscription information, refer to step S506 in the embodiment shown in FIG. 5A and FIG. 5B. Details are not described herein again.

[0210] In addition, the query request 1 carries an identifier of the PCF network element selected by the SMF network element 1 for the second session.

[0211] Optionally, in this embodiment of this application, the PCF network element may further subscribe to a data change notification from the UDR network element. After receiving a subscription request, the UDR network element returns an acknowledgement message.

[0212] S1207. The UDR network element sends a query response 1 to the PCF network element, so that the PCF network element receives the query response 1 from the UDR network element.

[0213] The query response 1 carries session policy-related subscription information corresponding to the combination of the identifier of the terminal, the DNN, and the S-NSSAI.

[0214] In addition, in this embodiment of this application, after obtaining the identifier of the PCF network element selected by the SMF network element 1 for the second session, the UDR network element stores the correspondence between the identifier of the PCF network element and a combination of an identifier of a terminal, a DNN, and S-NSSAI, in other words, stores the PCF binding information.

[0215] Step S1208 is the same as step S508 in the embodiment shown in FIG. 5A and FIG. 5B. For related descriptions, refer to the embodiment shown in FIG. 5A and FIG. 5B. Details are not described herein again.

[0216] Steps S1209 to S1214 are the same as steps S510 to S515 in the embodiment shown in FIG. 5A and FIG. 5B. For related descriptions, refer to the embodiment shown in FIG. 5A and FIG. 5B. Details are not described herein again.

[0217] S1215. The AMF network element sends, to the SMF network element 2, a creation request message 2 used to create the first session, so that the SMF network element 2 receives the creation request message 2 from the AMF network element.

[0218] The creation request message 2 includes the identifier of the terminal, the S-NSSAI, the DNN, and a PDU session identifier 1.

[0219] Optionally, if the AMF network element may further select a PCF network element for the first session, the creation request message 2 may further include an identifier of the PCF network element selected by the AMF network element for the first session, and the identifier is represented as PCF Ida. This is not specifically limited in this embodiment of this application.

[0220] S1216. The SMF network element 2 registers the first session with the UDM network element, and the SMF network element 2 obtains, from the UDM network element, the session management subscription data corresponding to the combination of the identifier of the terminal, the DNN, and the S-NSSAI.

[0221] In addition, in this embodiment of this application, if the UDM network element determines that the first session is established in a non-roaming scenario, the UDM network element may further return the PCF binding information to the SMF network element 2. The PCF binding information is the correspondence between the identifier of the PCF network element selected by the SMF network element 1 and the combination of the identifier of the terminal, the DNN, and the S-NSSAI.

[0222] In a possible implementation, the UDM network element may obtain the PCF binding information in the following manner: If the UDM network element determines that another SMF network element (namely, the SMF network element 1) has registered a PDU session with the identifier of the terminal, the DNN, and the S-NSSAI, the UDM network element sends a query request 2 to the UDR network element. The query request 2 includes the identifier of the terminal, the DNN, and the S-NSSAI, to request to obtain the PCF binding information. Further, the UDR network element sends the PCF binding information to the UDM network element, and the UDM network element receives the PCF binding information.

[0223] Alternatively, in another possible implementation, the UDM network element may obtain the PCF binding information in the following manner: If the UDM network element subscribes to the PCF binding information change notification in step S 1204, after the UDR network element stores the correspondence between an identifier of a PCF network element and a combination of an identifier of a terminal, a DNN, and S-NSSAI in step S 1207, the UDR network element sends the PCF binding information change notification to the UDM network element, and the PCF binding information change notification carries the PCF binding information. Further, the UDM network element receives the PCF binding information.

[0224] Steps S1217 to S1221 are the same as steps S520 to S524 in the embodiment shown in FIG. 5A and FIG. 5B. For related descriptions, refer to the embodiment shown in FIG. 5A and FIG. 5B. Details are not described herein again.

[0225] According to the policy control method provided in this embodiment of this application, it can be ensured that a same PCF network element is selected for a plurality of sessions of a same terminal that have same S-NSSAI and a same DNN. Therefore, a conflict between policies formulated for the plurality of PDU sessions of the same terminal that have the same S-NSSAI and the same DNN and the subscription information obtained from the UDR network element can be avoided. For an analysis of a related technical effect, refer to the foregoing policy control system part. Details are not described herein again.

[0226] Actions of the UDM network element or actions of the SMF network element 2 in steps S1201 to S1221 may be performed by the processor 401 in the communications device 400 shown in FIG. 4 by invoking the application program code stored in the memory 403. This is not limited in this embodiment.

[0227] Optionally, for example, the policy control system shown in FIG. 2 is applied to the 5G network shown in FIG. 3a, the first session management network element is an SMF network element 2, the second session management network element is an SMF network element 1, and the network device is a UDM network element. FIG. 13A and FIG. 13B show a policy control method according to an embodiment of this application. The policy control method includes the following steps.

[0228] Steps S1301 to S1303 are the same as steps S501 to S503 in the embodiment shown in FIG. 5A and FIG. 5B. For related descriptions, refer to the embodiment shown in FIG. 5A and FIG. 5B. Details are not described herein again.

[0229] Steps S1304 and S1305 are the same as steps S804 and S805 in the embodiment shown in FIG. 8. For related descriptions, refer to the embodiment shown in FIG. 5A and FIG. 5B. Details are not described herein again.

[0230] Steps S1306 to S1309 are the same as steps S506 to S509 in the embodiment shown in FIG. 5A and FIG. 5B. For related descriptions, refer to the embodiment shown in FIG. 5A and FIG. 5B. Details are not described herein again.

[0231] S1310. The BSF network element sends a data update request message to the UDR network element, so that the UDR network element receives the data update request message from the BSF network element.

[0232] The data update request message includes the PCF binding information. The PCF binding information is a correspondence between an identifier of a PCF network element and a combination of the identifier of the terminal, the DNN, and the S-NSSAI. After obtaining the PCF binding information, the UDR network element stores the PCF binding information.

[0233] Steps S1311 to S1316 are the same as steps S510 to S515 in the embodiment shown in FIG. 5A and FIG. 5B. For related descriptions, refer to the embodiment shown in FIG. 5A and FIG. 5B. Details are not described herein again.

[0234] S1317. The AMF network element sends, to the SMF network element 2, a creation request message 2 used to create the first session, so that the SMF network element 2 receives the creation request message 2 from the AMF network element.

[0235] The creation request message 2 includes the identifier of the terminal, the S-NSSAI, the DNN, and a PDU session identifier 1.

[0236] Optionally, if the AMF network element may further select a PCF network element for the first session, the creation request message 2 may further include an identifier of the PCF network element selected by the AMF network element for the first session, and the identifier is represented as PCF Ida. This is not specifically limited in this embodiment of this application.

[0237] Step S1318 is similar to step S1216 in the embodiment shown in FIG. 12A and FIG. 12B. For example, a difference lies in the following: In this embodiment of this application, in step S1310, the UDR network element sends the PCF binding information to the UDM network element. For other related descriptions, refer to the embodiment shown in FIG. 12A and FIG. 12B. Details are not described herein again.

[0238] Steps S1319 to S1323 are the same as steps S520 to S524 in the embodiment shown in FIG. 5A and FIG. 5B. For related descriptions, refer to the embodiment shown in FIG. 5A and FIG. 5B. Details are not described herein again.

[0239] According to the policy control method provided in this embodiment of this application, it can be ensured that a same PCF network element is selected for a plurality of sessions of a same terminal that have same S-NSSAI and a same DNN. Therefore, a conflict between policies formulated for the plurality of PDU sessions of the same terminal that have the same S-NSSAI and the same DNN and subscription information obtained from the UDR network element can be avoided. For an analysis of a related technical effect, refer to the foregoing policy control system part. Details are not described herein again.

[0240] Actions of the UDM network element or actions of the SMF network element 2 in steps S1301 to S1323 may be performed by the processor 401 in the communications device 400 shown in FIG. 4 by invoking the application program code stored in the memory 403. This is not limited in this embodiment.

[0241] Optionally, for example, the policy control system shown in FIG. 2b is applied to the 5G network shown in FIG. 3a, the first session management network element is an SMF network element 2, the second session management network element is an SMF network element 1, and the network device is a UDM network element. FIG. 14 A and FIG. 14B show a policy control method according to an embodiment of this application. The policy control method includes the following steps.

[0242] Steps S1401 to S1417 are the same as steps S501 to S517 in the embodiment shown in FIG. 5A and FIG. 5B. For related descriptions, refer to the embodiment shown in FIG. 5A and FIG. 5B. Details are not described herein again.

[0243] S1418. After selecting a PCFx network element for the first session, the SMF network element 2 sends a policy control creation request 2 to the PCFx network element, so that the PCFx network element receives the policy control creation request 2 from the SMF network element 2.

[0244] The policy control creation request 2 may include the identifier of the terminal, a PDU session identifier 2, the DNN, the S-NSSAI, and an IP address 1 assigned by the SMF network element 2 to the first session.

[0245] Optionally, in this embodiment of this application, the SMF network element 2 may select the PCFx network element for the first session based on a local policy and an identifier (which is PCF Ida herein) that is of a PCF network element and that is sent by the AMF network element, or in a manner such as performing interaction with an NRF network element. For details, refer to an existing implementation. The details are not described herein.

[0246] S1419. The PCFx network element performs management registration with the BSF network element.

[0247] Specifically, the PCFx network element may send a management registration request to the BSF network element. The management registration request includes the identifier of the terminal, the DNN, the S-NSSAI, an identifier of the PCFx network element selected by the SMF network element 2 for the first session, and the IP address 1 assigned by the SMF network element 2 to the first session. Further, after the BSF network element receives the management registration request, if the BSF network element determines that there is an identifier that is of a PCF network element (namely, the PCF network element selected by the SMF network element 1 for the second session) and that corresponds to the identifier of the terminal, the DNN, and the S-NSSAI, the BSF network element returns a rejection indication to the PCFx, and adds, to the rejection indication, the identifier that is of the PCF network element and that corresponds to the identifier of the terminal, the DNN, and the S-NSSAI.

[0248] S1420. The PCFx network element sends the rejection indication to the SMF network element 2, so that the SMF network element 2 receives the rejection indication from the PCFx network element.

[0249] S1421. The SMF 2 sends a policy control creation request 3 to the PCF network element corresponding to the identifier of the PCF network element, so that the PCF network element receives the policy control creation request 3 from the SMF network element 1.

[0250] S1422. The PCF network element performs management registration with the BSF network element.

[0251] Specifically, the PCF network element may send a management registration request to the BSF network element. The management registration request includes the identifier of the terminal, the DNN, the S-NSSAI, the identifier of the PCF network element selected by the SMF network element 1 for the second session, and the IP address 1 assigned by the SMF network element 2 to the first session. Further, after storing a correspondence among the identifier of the terminal, the DNN, the S-NSSAI, the identifier of the PCF network element, and the IP address 1, the BSF network element sends a management registration response to the PCF network element.

[0252] Steps S1423 to S1426 are the same as steps S521 to S524 in the embodiment shown in FIG. 5A and FIG. 5B. For related descriptions, refer to the embodiment shown in FIG. 5A and FIG. 5B. Details are not described herein again.

[0253] According to the policy control method provided in this embodiment of this application, it can be ensured that a same PCF network element is selected for a plurality of sessions of a same terminal that have same S-NSSAI and a same DNN. Therefore, a conflict between policies formulated for the plurality of PDU sessions of the same terminal that have the same S-NSSAI and the same DNN and subscription information obtained from the UDR network element can be avoided. For an analysis of a related technical effect, refer to the foregoing policy control system part. Details are not described herein again.

[0254] Optionally, for example, the policy control system shown in FIG. 2b is applied to the 5G network shown in FIG. 3a, the first session management network element is an SMF network element 2, the second session management network element is an SMF network element 1, and the network device is a UDM network element. FIG. 14A and FIG. 14B show a policy control method according to an embodiment of this application. The policy control method includes the following steps.

[0255] Steps S1401 to S1408 are the same as steps S501 to S508 in the embodiment shown in FIG. 5A and FIG. 5B. For related descriptions, refer to the embodiment shown in FIG. 5A and FIG. 5B. Details are not described herein again.

[0256] S 1409. The PCF network element performs management registration with a BSF network element.

[0257] Specifically, the PCF network element may send a management registration request (management register request) to the BSF network element. The management registration request includes the identifier of the terminal, the DNN, the S-NSSAI, an identifier of the PCF network element selected by the SMF network element 1 for the second session, and an IP address 2 assigned by the SMF network element 1 to the second session. Further, after storing a correspondence among the identifier of the terminal, the DNN, the S-NSSAI, the identifier of the PCF network element, and the IP address 2, the BSF network element sends a management registration response (management register response) to the PCF network element. In this embodiment of this application, the PCF network element may be a PCF network function instance (network function instance) or a PCF network function service instance (network function service instance). Correspondingly, the identifier of the PCF network element may be a network function instance identifier (network function instance Id) of the PCF network element or a network function service instance identifier (network function service instance Id) of the PCF network element. This is not specifically limited herein.

[0258] Optionally, in this embodiment of this application, if a PCF network element set is supported in a network, the PCF network element may alternatively add, to the management registration request, the identifier of the terminal, the DNN, the S-NSSAI, the identifier of the PCF network element selected by the SMF network element 1 for the second session (optional), an identifier 1 of a PCF network element set to which the PCF network element selected by the SMF network element 1 for the second session belongs, and the IP address 2 assigned by the SMF network element 1 to the second session. Further, after storing a correspondence among the identifier of the terminal, the DNN, the S-NSSAI, the identifier of the PCF network element (optional), the identifier 1 of the PCF network element set, and the IP address 2, the BSF network element sends the management registration response to the PCF network element. One PCF network element set usually includes a plurality of PCF network elements, and the plurality of PCF network elements share one unstructured data storage function (unstructured data storage function, UDSF) network element. The UDSF network element can ensure that subscription data assigned to different PCF network elements does not conflict with each other. In this embodiment of this application, the PCF network element set is a network function set (network function set) of a policy control function or a network function service set (network function service set) of the policy control function. Correspondingly, the identifier of the PCF network element set may be a network function set identifier (network function set Id) of the PCF network element or a network function service set identifier (network function service set Id) of the PCF network element. This is not specifically limited herein.

[0259] Optionally, in this embodiment of this application, before the PCF network element sends the management registration request to the BSF network element, the PCF network element may further determine, based on an operator policy, a configuration, and/or user subscription (for example, it is indicated, in the user subscription, that usage amount monitoring needs to be applied to the user, and the user subscription is obtained in step 1407), that a same PCF network element needs to be selected for a combination of the identifier of the terminal, the DNN, and the S-NSSAI. A management registration request message sent by the PCF network element to the BSF network element further carries an indication for selecting a same PCF network element. However, because the BSF network element has no binding relationship corresponding to the combination of the identifier of the terminal, the DNN, and the S-NSSAI, the BSF network element returns a success response to the PCF network element.

[0260] Optionally, in this embodiment of this application, when determining that the terminal establishes the second session in a non-roaming scenario or a home routing scenario, the PCF network element adds, to the management registration request message, an indication for selecting a same PCF network element.

[0261] Optionally, in this embodiment of this application, if a PCF network element set is supported in a network, the PCF network element may further determine, based on the operator policy, the configuration, and/or the user subscription (for example, it is indicated, in the user subscription, that usage amount monitoring needs to be applied to the user, and the user subscription is obtained in step 1407), that a same PCF network element set needs to be selected for the combination of the identifier of the terminal, the DNN, and the S-NSSAI. The management registration request message sent by the PCF network element to the BSF network element further carries an indication for selecting a same PCF network element set. However, because the BSF network element has no binding relationship corresponding to the combination of the identifier of the terminal, the DNN, and the S-NSSAI, the BSF network element returns the success response to the PCF network element.

[0262] Optionally, in this embodiment of this application, when determining that the terminal establishes the second session in the non-roaming scenario or the home routing scenario, the PCF network element adds, to the management registration request message, an indication for selecting a same PCF network element set.

[0263] Steps S1410 to S1417 are the same as steps S510 to S517 in the embodiment shown in FIG. 5A and FIG. 5B. For related descriptions, refer to the embodiment shown in FIG. 5A and FIG. 5B. Details are not described herein again.

[0264] Optionally, in this embodiment of this application, the AMF network element in step S1414 may be the same as or different from the AMF network element in step 1401. That the AMF network elements are the same is only an example used for description in this embodiment of this application. A description is provided herein. Details are not described below again.

[0265] S1418. After selecting a PCFx network element for the first session, the SMF network element 2 sends a policy control creation request 2 to the PCFx network element, so that the PCFx network element receives the policy control creation request 2 from the SMF network element 2.

[0266] The policy control creation request 2 may include the identifier of the terminal, a PDU session identifier 2, the DNN, the S-NSSAI, and an IP address 1 assigned by the SMF network element 2 to the first session.

[0267] Optionally, in this embodiment of this application, the SMF network element 2 may select the PCFx network element for the first session based on a local policy and an identifier (which is PCF Ida herein) that is of a PCF network element and that is sent by the AMF network element, or in a manner such as interacting with an NRF network element. For details, refer to an existing implementation. The details are not described herein.

[0268] S1419. The PCFx network element performs management registration with the BSF network element.

[0269] Specifically, the PCFx network element may send a management registration request to the BSF network element. The management registration request includes the identifier of the terminal, the DNN, the S-NSSAI, an identifier of the PCFx network element selected by the SMF network element 2 for the first session, and the IP address 1 assigned by the SMF network element 2 to the first session. Further, after the BSF network element receives the management registration request, if the BSF network element determines that there is an identifier that is of a PCF network element (namely, the PCF network element selected by the SMF network element 1 for the second session) and that corresponds to the identifier of the terminal, the DNN, and the S-NSSAI, the BSF network element returns a rejection indication to the PCFx network element, and adds, to the rejection indication, the identifier that is of the PCF network element and that corresponds to the identifier of the terminal, the DNN, and the S-NSSAI.

[0270] Optionally, in this embodiment of this application, if a PCF network element set is supported in the network, the SMF network element 2 may alternatively add, to the management registration request, the identifier of the terminal, the DNN, the S-NSSAI, the identifier of the PCFx network element selected by the SMF network element 2 for the first session (optional), an identifier 2 of a PCF network element set to which the PCFx network element selected by the SMF network element 2 for the first session belongs, and the IP address 1 assigned by the SMF network element 2 to the first session. Further, after the BSF network element receives the management registration request, if the BSF network element determines that there is an identifier (namely, the identifier 1 of the PCF network element set selected by the SMF network element 1 for the second session) that is of a PCF network element set and that corresponds to the identifier of the terminal, the DNN, and the S-NSSAI, the BSF network element returns a rejection indication to the PCFx network element, and adds, to the rejection indication, the identifier 1 that is of the PCF network element set and that corresponds to the identifier of the terminal, the DNN, and the S-NSSAI.

[0271] Optionally, in this embodiment of this application, before the PCFx network element sends the management registration request to the BSF network element, the PCFx network element may further determine, based on the operator policy, the configuration, and/or the user subscription (for example, it is indicated, in the user subscription, that usage amount monitoring needs to be applied to the user, and the user subscription is obtained through interaction between the PCFx and the UDR), that a same PCF network element needs to be selected for the combination of the identifier of the terminal, the DNN, and the S-NSSAI. A management registration request message sent by the PCFx network element to the BSF network element further carries an indication for selecting a same PCF network element. The BSF network element receives the indication for selecting a same PCF network element, and the BSF network element has the binding relationship (the binding relationship registered in step 1409) corresponding to the combination of the identifier of the terminal, the DNN, and the S-NSSAI. Therefore, the BSF network element returns a rejection indication to the PCFx network element, and adds, to the rejection indication, the identifier that is of the PCF network element and that corresponds to the identifier of the terminal, the DNN, and the S-NSSAI.

[0272] Optionally, in this embodiment of this application, when determining that the terminal establishes the first session in the non-roaming scenario or the home routing scenario, the PCFx network element adds, to the management registration request message, the indication for selecting a same PCF network element.

[0273] Optionally, in this embodiment of this application, if the PCF network element set is supported in the network, before the PCFx network element sends the management registration request to the BSF network element, the PCFx network element may further determine, based on the operator policy, the configuration, and/or the user subscription (for example, it is indicated, in the user subscription, that usage amount monitoring needs to be applied to the user, and the user subscription is obtained through interaction between the PCFx and the UDR), that a same PCF network element set needs to be selected for the combination of the identifier of the terminal, the DNN, and the S-NSSAI. The management registration request message sent by the PCFx network element to the BSF network element further carries an indication for selecting a same PCF network element set. The BSF network element receives the indication for selecting a same PCF network element set, and the BSF network element has the binding relationship (the binding relationship registered in step 1409) corresponding to the combination of the identifier of the terminal, the DNN, and the S-NSSAI. Therefore, the BSF network element returns the rejection indication to the PCFx network element, and adds, to the rejection indication, the identifier 1 that is of the PCF network element set and that corresponds to the identifier of the terminal, the DNN, and the S-NSSAI.

[0274] Optionally, in this embodiment of this application, when determining that the terminal establishes the first session in the non-roaming scenario or the home routing scenario, the PCFx network element adds, to the management registration request message, the indication for selecting a same PCF network element set.

[0275] Optionally, in this embodiment of this application, the rejection indication may carry the identifier of the PCF network element for indication, or carry a rejected hypertext transfer protocol (hyperText transfer protocol, HTTP) status code and the identifier of the PCF network element for indication. A description is provided herein. Details are not described below again.

[0276] Optionally, in this embodiment of this application, if the PCF network element set is supported in the network, the rejection indication may carry the identifier of the PCF network element set for indication, or carry a rejected hypertext transfer protocol (hyperText transfer protocol, HTTP) status code and the identifier of the PCF network element set for indication. A description is provided herein. Details are not described below again.

[0277] S1420. The PCFx network element sends the rejection indication to the SMF network element 2, so that the SMF network element 2 receives the rejection indication from the PCFx network element.

[0278] S1421. The SMF 2 sends a policy control creation request 3 to the PCF network element corresponding to the identifier of the PCF network element, so that the PCF network element receives the policy control creation request 3 from the SMF network element 2.

[0279] Optionally, in this embodiment of this application, if the PCF network element set is supported in the network, after selecting one PCF network element corresponding to the identifier 1 of the PCF network element set, the SMF network element 2 sends the policy control creation request 3 to the PCF network element, so that the PCF network element receives the policy control creation request 3 from the SMF network element 2.

[0280] Optionally, the SMF network element 2 interacts with the PCFx network element, to terminate a policy association established in step S1418.

[0281] S1422. The PCF network element performs management registration with the BSF network element.

[0282] Specifically, the PCF network element may send a management registration request to the BSF network element. The management registration request includes the identifier of the terminal, the DNN, the S-NSSAI, the identifier of the PCF network element selected by the SMF network element 1 for the second session, and the IP address 1 assigned by the SMF network element 2 to the first session. Further, after storing a correspondence among the identifier of the terminal, the DNN, the S-NSSAI, the identifier of the PCF network element, and the IP address 1, the BSF network element sends a management registration response to the PCF network element.

[0283] Optionally, if the PCF network element set is supported in the network, the PCF network element may send the management registration request to the BSF network element. The management registration request includes the identifier of the terminal, the DNN, the S-NSSAI, the identifier of the PCF network element selected by the SMF network element 2 for the first session (optional), an identifier of a set to which the PCF network element belongs, and the IP address 1 assigned by the SMF network element 2 to the first session. Further, after storing the correspondence among the identifier of the terminal, the DNN, the S-NSSAI, the identifier of the PCF network element (optional), the identifier of the PCF network element set, and the IP address 1, the BSF network element sends the management registration response to the PCF network element.

[0284] Steps S1423 to S1426 are the same as steps S521 to S524 in the embodiment shown in FIG. 5A and FIG. 5B. For related descriptions, refer to the embodiment shown in FIG. 5A and FIG. 5B. Details are not described herein again.

[0285] According to the policy control method provided in this embodiment of this application, it can be ensured that a same PCF network element or a same PCF network element set is selected for a plurality of sessions of a same terminal that have same S-NSSAI and a same DNN. Therefore, a conflict between policies formulated for the plurality of PDU sessions of the same terminal that have the same S-NSSAI and the same DNN and subscription information obtained from a UDR network element can be avoided. For an analysis of a related technical effect, refer to the foregoing policy control system part. Details are not described herein again.

[0286] Actions of the BSF network element or actions of the SMF network element 2 in steps S1401 to S1426 may be performed by the processor 401 in the communications device 400 shown in FIG. 4 by invoking the application program code stored in the memory 403. This is not limited in this embodiment.

[0287] The solutions provided in the embodiments of this application are mainly described from a perspective of interaction between network elements. It may be understood that, to implement the foregoing functions, the mobility management network element, the network device, the first session management network element, the second session management network element, the first policy control network element, or the binding support network element includes corresponding hardware structures and/or software modules for performing the functions. A person skilled in the art should easily be aware that, in combination with the examples described in the embodiments disclosed in this specification, units and algorithm steps can be implemented by hardware or a combination of hardware and computer software in this application. Whether a function is performed by hardware or hardware driven by computer software depends on particular applications and design constraints of the technical solutions. A person skilled in the art may use different methods to implement the described functions for each particular application, but it should not be considered that the implementation goes beyond the scope of this application.

[0288] In the embodiments of this application, the mobility management network element, the network device, the first session management network element, the second session management network element, the first policy control network element, or the binding support network element may be divided into function modules based on the foregoing method examples. For example, each function module may be obtained through division based on each corresponding function, or two or more functions may be integrated into one processing module. The integrated module may be implemented in a form of hardware, or may be implemented in a form of a software function module. It should be noted that the division into module in this embodiment of this application is an example, and is merely logical function division. In an actual implementation, another division manner may be used.

[0289] For example, when the function modules are obtained through division performed in an integrated manner, FIG. 8 is a schematic structural diagram of a mobility management network element 80. The mobility management network element 80 includes a processing module 801 and a transceiver module 802. The processing module 801 is configured to determine that a first session that is of a terminal and that is being established has the same S-NSSAI and the same DNN as an established second session of the terminal. The transceiver module 802 is configured to send, to a first session management network element, a first request message used to create the first session. The first request message includes an identifier of the terminal, the S-NSSAI, the DNN, and indication information, and the indication information is used to instruct the first session management network element to obtain an identifier of a policy control network element from a binding support network element; or the indication information is used to indicate that a session that is of the terminal and that has the same S-NSSAI and the same DNN as the first session is established; or the indication information is used to indicate that the first session has corresponding binding information.

[0290] Optionally, the processing module 801 is specifically configured to: determine, based on at least one of subscription data of the terminal, an operator policy, and a session establishment request from the terminal, that the first session that is of the terminal and that is being established has the same S-NSSAI and the same DNN as the established second session of the terminal.

[0291] Optionally, the processing module 801 is further configured to determine that the terminal establishes the first session in a non-roaming scenario or a home routing scenario.

[0292] All related content of the steps in the foregoing method embodiments may be cited in function descriptions of corresponding function modules. Details are not described herein again.

[0293] In this embodiment, the mobility management network element 80 is presented in a form of function modules obtained through division performed in an integrated manner. The "module" herein may be a specific ASIC, a circuit, a processor and a memory that execute one or more software programs or firmware programs, an integrated logic circuit, and/or another component that can provide the foregoing functions. In a simple embodiment, a person skilled in the art may figure out that the mobility management network element 80 may be in a form shown in FIG. 4.

[0294] For example, the processor 401 in FIG. 4 may invoke the computer executable instruction stored in the memory 403, so that the mobility management network element 80 performs the policy control methods in the foregoing method embodiments.

[0295] Specifically, functions/implementation processes of the transceiver module 802 and the processing module 801 in FIG. 8 may be implemented by the processor 401 in FIG. 4 by invoking the computer executable instruction stored in the memory 403. Alternatively, functions/implementation processes of the processing module 801 in FIG. 8 may be implemented by the processor 401 in FIG. 4 by invoking the computer executable instruction stored in the memory 403, and functions/implementation processes of the transceiver module 802 in FIG. 8 may be implemented by the communications interface 404 in FIG. 4.

[0296] The mobility management network element 80 provided in this embodiment may perform the foregoing policy control method. Therefore, for technical effects that can be achieved by the mobility management network element 80, refer to the foregoing method embodiments. Details are not described herein again.

[0297] Optionally, an embodiment of this application further provides an apparatus (for example, the apparatus may be a chip system). The apparatus includes a processor, configured to support a mobility management network element in implementing the foregoing policy control methods, for example, in determining that a first session that is of a terminal and that is being established has the same S-NSSAI and the same DNN as an established second session of the terminal. In a possible design, the apparatus further includes a memory. The memory is configured to store a program instruction and data that are necessary for the mobility management network element. Certainly, the memory may not be in the apparatus. When the apparatus is a chip system, the apparatus may include a chip, or may include a chip and another discrete component. This is not specifically limited in this embodiment of this application.

[0298] Alternatively, for example, when the function modules are obtained through division performed in an integrated manner, FIG. 9 is a schematic structural diagram of a network device 90. The network device 90 includes a processing module 901 and a transceiver module 902. The processing module 901 is configured to determine that a first session that is of a terminal and that is being established has same S-NSSAI and a same DNN as an established second session of the terminal. The transceiver module 902 is configured to send, to a first session management network element corresponding to the first session, an identifier of a policy control network element selected by a second session management network element corresponding to the second session. The identifier of the policy control network element is used by the first session management network element to select the policy control network element.

[0299] Optionally, the transceiver module 902 is further configured to receive the identifier of the policy control network element from the second session management network element in a process of establishing the second session.

[0300] Optionally, the network device 90 may be a unified data management network element. The transceiver module 902 is further configured to send a subscription request for a binding information change notification to a unified data repository network element in the process of establishing the second session. The transceiver module 902 is further configured to receive the binding information change notification from the unified data repository network element. The binding information change notification includes an identifier that is of a policy control network element and that corresponds to an identifier of the terminal, the S-NSSAI, and the DNN

[0301] Optionally, as shown in FIG. 9, the network device 90 further includes a storage module 903. The storage module 903 is configured to store a correspondence between the identifier of the policy control network element and a combination of the identifier of the terminal, the S-NSSAI, the DNN

[0302] Optionally, the processing module 901 is further configured to determine the identifier of the policy control network element based on the identifier of the terminal, the S-NSSAI, the DNN, and the correspondence.

[0303] Optionally, the network device 90 may be a unified data management network element. The transceiver module 902 is further configured to send a request message to the unified data repository network element. The request message includes an identifier of the terminal, an S-NSSAI, and a DNN. The transceiver module 902 is further configured to receive an identifier that is of a policy control network element, that corresponds to the identifier of the terminal, the S-NSSAI, and the DNN, and that is from the unified data repository network element.

[0304] Optionally, the processing module 901 is further configured to determine that the terminal establishes the first session in a non-roaming scenario or a home routing scenario.

[0305] Optionally, the network device 90 is a mobility management network element. That the processing module 901 is configured to determine that a first session that is of a terminal and that is being established has the same S-NSSAI and the same DNN as an established second session of the terminal is specifically: determining, based on at least one of subscription data of the terminal, an operator policy, and a session establishment request from the terminal, that the first session that is of the terminal and that is being established has the same S-NSSAI and the same DNN as the established second session of the terminal.

[0306] Optionally, the network device 90 is a mobility management network element. The transceiver module 902 is further configured to send indication information to the first session management network element. The indication information is used to indicate that the policy control network element corresponding to the identifier of the policy control network element is a policy control network element selected by a session management network element; or the indication information is used to instruct the first session management network element to select the policy control network element corresponding to the identifier of the policy control network element; or the indication information is used to indicate that the first session has corresponding binding information.

[0307] Optionally, the network device 90 is a mobility management network element. The transceiver module 902 is further configured to add the identifier of the policy control network element to a special field. The special field is used to indicate that the policy control network element corresponding to the identifier of the policy control network element is a policy control network element selected by a session management network element.

[0308] Optionally, the network device 90 is a unified data management network element. The transceiver module 902 is further configured to receive a registration request from the first session management network element. The registration request includes an identifier of the terminal, S-NSSAI, and a DNN. Correspondingly, that the processing module 901 is configured to determine that a first session that is of a terminal and that is being established has the same S-NSSAI and the same DNN as an established second session of the terminal is specifically: determining, based on the identifier of the terminal, the S-NSSAI, and the DNN, that the first session that is of the terminal and that is being established has the same S-NSSAI and the same DNN as the established second session of the terminal.

[0309] All related content of the steps in the foregoing method embodiments may be cited in function descriptions of corresponding function modules. Details are not described herein again.

[0310] In this embodiment, the network device 90 is presented in a form of function modules obtained through division performed in an integrated manner. The "module" herein may be a specific ASIC, a circuit, a processor and a memory that execute one or more software programs or firmware programs, an integrated logic circuit, and/or another component that can provide the foregoing functions. In a simple embodiment, a person skilled in the art may figure out that the network device 90 may be in a form shown in FIG. 4.

[0311] For example, the processor 401 in FIG. 4 may invoke the computer executable instruction stored in the memory 403, so that the network device 90 performs the policy control methods in the foregoing method embodiments.

[0312] Specifically, functions/implementation processes of the transceiver module 902, the processing module 901, and storage module 903 in FIG. 9 may be implemented by the processor 401 in FIG. 4 by invoking the computer executable instruction stored in the memory 403. Alternatively, functions/implementation processes of the processing module 901 in FIG. 9 may be implemented by the processor 401 in FIG. 4 by invoking the computer executable instruction stored in the memory 403, functions/implementation processes of the transceiver module 902 in FIG. 9 may be implemented by the communications interface 404 in FIG. 4, and functions/implementation processes of the storage module 903 in FIG. 9 may be implemented by the memory 403 in FIG. 4.

[0313] The network device 90 provided in this embodiment may perform the foregoing policy control methods. Therefore, for technical effects that can be achieved by the network device 90, refer to the foregoing method embodiments. Details are not described herein again.

[0314] Optionally, an embodiment of this application further provides an apparatus (for example, the apparatus may be a chip system). The apparatus includes a processor, configured to support a network device in implementing the foregoing policy control methods, for example, in determining that a first session that is of a terminal and that is being established has the same S-NSSAI and the same DNN as an established second session of the terminal. In a possible design, the apparatus further includes a memory. The memory is configured to store a program instruction and data that are necessary for the network device. Certainly, the memory may not be in the apparatus. When the apparatus is a chip system, the apparatus may include a chip, or may include a chip and another discrete component. This is not specifically limited in this embodiment of this application.

[0315] For example, when the function modules are obtained through division performed in an integrated manner, FIG. 10 is a schematic structural diagram of a first session management network element 100. The first session management network element 100 includes a processing module 1001 and a transceiver module 1002.

[0316] In a possible implementation, the transceiver module 1002 is configured to receive, from a mobility management network element, a first request message used to create a first session. The first request message includes an identifier of a terminal, S-NSSAI, and a DNN. The transceiver module 1002 is further configured to send a second request message to a binding support network element. The second request message includes the identifier of the terminal, the S-NSSAI, and the DNN, and is used to request a corresponding identifier of a policy control network element, the policy control network element is a policy control network element corresponding to a second session, and the second session is an established session that is of the terminal and that has the same S-NSSAI and the same DNN as the first session. The transceiver module 1002 is further configured to receive the identifier of the policy control network element from the binding support network element. The processing module 1001 is configured to select the policy control network element based on the identifier of the policy control network element.

[0317] Optionally, the first request message further includes indication information, and the indication information is used to instruct the first session management network element to obtain the identifier of the policy control network element from the binding support network element; or the indication information is used to indicate that a session that is of the terminal and that has the same S-NSSAI and the same DNN as the first session is established; or the indication information is used to indicate that the first session has corresponding binding information.

[0318] Optionally, the transceiver module 1002 is further configured to send a registration request to a unified data management network element. The registration request includes the identifier of the terminal, and the S-NSSAI and the DNN that correspond to the first session that is of the terminal and that are being established. The transceiver module 1002 is further configured to receive indication information from the unified data management network element. The indication information is used to instruct the first session management network element to obtain the identifier of the policy control network element from the binding support network element; or the indication information is used to indicate that a session that is of the terminal and that has the same S-NSSAI and the same DNN as the first session is established; or the indication information is used to indicate that the first session has corresponding binding information. That the transceiver module 1002 is configured to send a second request message to a binding support network element includes: sending the second request message to the binding support network element based on the indication information.

[0319] In another possible implementation, the transceiver module 1002 is configured to receive, from a mobility management network element, a first request message used to create a first session. The first request message includes an identifier of a terminal, S-NSSAI, and a DNN. The transceiver module is further configured to send a second request message to a binding support network element. The second request message includes the identifier of the terminal, the S-NSSAI, and the DNN, and is used to request a corresponding identifier of a policy control network element, the policy control network element is a policy control network element corresponding to a second session, and the second session is an established session that is of the terminal and that has the same S-NSSAI and the same DNN as the first session. The processing module 1001 is configured to: if determining that an identifier that is of a policy control network element and that is from the binding support network element cannot be received, select the first session selection policy control network element based on at least one of a local configuration, an identifier that is of a policy control network element and that is provided by a mobility management network element, or an identifier that is of a policy control network element and that is provided by a network repository function network element.

[0320] All related content of the steps in the foregoing method embodiments may be cited in function descriptions of corresponding function modules. Details are not described herein again.

[0321] In this embodiment, the first session management network element 100 is presented in a form of function modules obtained through division performed in an integrated manner. The "module" herein may be a specific ASIC, a circuit, a processor and a memory that execute one or more software programs or firmware programs, an integrated logic circuit, and/or another component that can provide the foregoing functions. In a simple embodiment, a person skilled in the art may figure out that the first session management network element 100 may be in a form shown in FIG. 4.

[0322] For example, the processor 401 in FIG. 4 may invoke the computer executable instruction stored in the memory 403, so that the first session management network element 100 performs the policy control methods in the foregoing method embodiments.

[0323] Specifically, functions/implementation processes of the transceiver module 1002 and the processing module 1001 in FIG. 10 may be implemented by the processor 401 in FIG. 4 by invoking the computer executable instruction stored in the memory 403. Alternatively, functions/implementation processes of the processing module 1001 in FIG. 10 may be implemented by the processor 401 in FIG. 4 by invoking the computer executable instruction stored in the memory 403, and functions/implementation processes of the transceiver module 1002 in FIG. 10 may be implemented by the communications interface 404 in FIG. 4.

[0324] The first session management network element 100 provided in this embodiment may perform the foregoing policy control methods. Therefore, for technical effects that can be achieved by the first session management network element 100, refer to the foregoing method embodiments. Details are not described herein again.

[0325] Optionally, an embodiment of this application further provides an apparatus (for example, the apparatus may be a chip system). The apparatus includes a processor, configured to support a first session management network element in implementing the foregoing policy control methods, for example, in selecting a policy control network element based on an identifier of the policy control network element. In a possible design, the apparatus further includes a memory. The memory is configured to store a program instruction and data that are necessary for the first management network element. Certainly, the memory may not be in the apparatus. When the apparatus is a chip system, the apparatus may include a chip, or may include a chip and another discrete component. This is not specifically limited in this embodiment of this application.

[0326] Alternatively, for example, when function modules are obtained through division performed in an integrated manner, FIG. 11 is a schematic structural diagram of a second session management network element 110. The second session management network element 110 includes a processing module 1101 and a transceiver module 1102.

[0327] The processing module 1101 is configured to select a policy control network element in a process of establishing a second session of a terminal. The transceiver module 1102 is configured to send an identifier of the policy control network element to a network device. The identifier of the policy control network element is used by a first session management network element to select the policy control network element, the first session management network element is a session management network element corresponding to a first session, and the first session is a to-be-established session that is of the terminal and that has the same S-NSSAI and the same DNN as the second session.

[0328] Optionally, the network device is a mobility management network element or a unified data management network element.

[0329] Optionally, the second session is the 1st session that has the S-NSSAI and the DNN and that is processed by the second session management network element for the terminal.

[0330] Optionally, the transceiver module 1102 is further configured to receive indication information from the mobility management network element, and the indication information is used to instruct to preferably select the policy control network element. For example, after selecting the policy control network element, the second session management network element sends a registration request including the identifier of the policy control network element to the unified data management network element.

[0331] All related content of the steps in the foregoing method embodiments may be cited in function descriptions of corresponding function modules. Details are not described herein again.

[0332] In this embodiment, the second session management network element 110 is presented in a form of function modules obtained through division performed in an integrated manner. The "module" herein may be a specific ASIC, a circuit, a processor and a memory that execute one or more software programs or firmware programs, an integrated logic circuit, and/or another component that can provide the foregoing functions. In a simple embodiment, a person skilled in the art may figure out that the second session management network element 110 may be in a form shown in FIG. 4.

[0333] For example, the processor 401 in FIG. 4 may invoke the computer executable instruction stored in the memory 403, so that the second session management network element 110 performs the policy control methods in the foregoing method embodiments.

[0334] Specifically, functions/implementation processes of the transceiver module 1102 and the processing module 1101 in FIG. 11 may be implemented by the processor 401 in FIG. 4 by invoking the computer executable instruction stored in the memory 403. Alternatively, functions/implementation processes of the processing module 1101 in FIG. 11 may be implemented by the processor 401 in FIG. 4 by invoking the computer executable instruction stored in the memory 403, and functions/implementation processes of the transceiver module 1102 in FIG. 11 may be implemented by the communications interface 404 in FIG. 4.

[0335] The second session management network element 110 provided in this embodiment may perform the foregoing policy control methods. Therefore, for technical effects that can be achieved by the second session management network element 110, refer to the foregoing method embodiments. Details are not described herein again.

[0336] Optionally, an embodiment of this application further provides an apparatus (for example, the apparatus may be a chip system). The apparatus includes a processor, configured to support a second session management network element in implementing the foregoing policy control methods, for example, in selecting a policy control network element in a process of establishing a second session of a terminal. In a possible design, the apparatus further includes a memory. The memory is configured to store a program instruction and data that are necessary for the second management network element. Certainly, the memory may not be in the apparatus. When the apparatus is a chip system, the apparatus may include a chip, or may include a chip and another discrete component. This is not specifically limited in this embodiment of this application.

[0337] The embodiments described in reference to Fig. 15 are not part of the invention, but illustrative examples necessary for understanding the invention.

[0338] Alternatively, for example, when function modules are obtained through division performed in an integrated manner, FIG. 15 is a schematic structural diagram of a unified data management network element 150. The unified data management network element 150 includes a receiving module 1501 and a sending module 1502. The receiving module 1501 is configured to receive a registration request from a first session management network element. The registration request includes an identifier of a terminal, and an S-NSSAI and a DNN that correspond to a first session that is of the terminal and that is being established. The sending module 1502 is configured to send indication information to the first session management network element. The indication information is used to instruct the first session management network element to obtain an identifier of a policy control network element from a binding support network element; or the indication information is used to indicate that a session that is of the terminal and that has the same S-NSSAI and the same DNN as the first session is established; or the indication information is used to indicate that the first session has corresponding binding information.

[0339] Optionally, as shown in FIG. 15, the unified data management network element 150 may further include a processing module 1503. The processing module 1503 is configured to determine that the first session that is of the terminal and that is being established has the same S-NSSAI and the same DNN as an established second session of the terminal.

[0340] Optionally, the processing module 1503 is further configured to determine that the terminal establishes the first session in a non-roaming scenario or a home routing scenario.

[0341] All related content of the steps in the foregoing method embodiments may be cited in function descriptions of corresponding function modules. Details are not described herein again.

[0342] In this embodiment, the unified data management network element 150 is presented in a form of function modules obtained through division performed in an integrated manner. The "module" herein may be a specific ASIC, a circuit, a processor and a memory that execute one or more software programs or firmware programs, an integrated logic circuit, and/or another component that can provide the foregoing functions. In a simple embodiment, a person skilled in the art may figure out that the unified data management network element 150 may be in a form shown in FIG. 4.

[0343] For example, the processor 401 in FIG. 4 may invoke the computer executable instruction stored in the memory 403, so that the unified data management network element 150 performs the policy control methods in the foregoing method embodiments.

[0344] Specifically, functions/implementation processes of the receiving module 1501, the sending module 1502, and the processing module 1503 in FIG. 15 may be implemented by the processor 401 in FIG. 4 by invoking the computer executable instruction stored in the memory 403. Alternatively, functions/implementation processes of the processing module 1503 in FIG. 15 may be implemented by the processor 401 in FIG. 4 by invoking the computer executable instruction stored in the memory 403, and functions/implementation processes of the receiving module 1501 and the sending module 1502 in FIG. 15 may be implemented by the communications interface 404 in FIG. 4.

[0345] The unified data management network element 150 provided in this embodiment may perform the foregoing policy control methods. Therefore, for technical effects that can be achieved by the unified data management network element 150, refer to the foregoing method embodiments. Details are not described herein again.

[0346] Optionally, an embodiment of this application further provides an apparatus (for example, the apparatus may be a chip system). The apparatus includes a processor, configured to support a unified data network element in implementing the foregoing policy control methods, for example, in determining that a first session that is of a terminal and that is being established has the same S-NSSAI and the same DNN as an established second session of the terminal. In a possible design, the apparatus further includes a memory. The memory is configured to store a program instruction and data that are necessary for the unified data management network element. Certainly, the memory may not be in the apparatus. When the apparatus is a chip system, the apparatus may include a chip, or may include a chip and another discrete component. This is not specifically limited in this embodiment of this application.

[0347] Alternatively, for example, when function modules are obtained through division performed in an integrated manner, FIG. 16 is a schematic structural diagram of a first policy control network element 160. The first policy control network element 160 includes a receiving module 1601 and a sending module 1602.

[0348] In a possible implementation, the receiving module 1601 is configured to receive a policy control creation request from a first session management network element, and the policy control creation request includes an identifier of a terminal, S-NSSAI, and a DNN. The sending module 1602 is configured to send the identifier of the terminal, the S-NSSAI, the DNN, and an identifier of the first policy control network element 160 to a binding support network element. The receiving module 1601 is further configured to receive an identifier of a second policy control network element from the binding support network element. The sending module 1602 is further configured to send the identifier of the second policy control network element to the first session management network element, and the identifier of the second policy control network element is an identifier that is of a policy control network element, that corresponds to the identifier of the terminal, the S-NSSAI, and the DNN, and that is stored by the binding support network element.

[0349] Optionally, as shown in FIG. 16, the first policy control network element 160 further includes a processing module 1603. The processing module 1603 is configured to determine that a same policy control network element needs to be selected for a combination of the identifier of the terminal, the S-NSSAI, and the DNN. The sending module 1602 is further configured to send indication information to the binding support network element, and the indication information is used to instruct to select the same policy control network element for the combination of the identifier of the terminal, the S-NSSAI, and the DNN

[0350] In another possible implementation, the receiving module 1601 is configured to receive a policy control creation request from a first session management network element, and the policy control creation request includes an identifier of a terminal, S-NSSAI, and a DNN. The sending module 1602 is configured to send, to a binding support network element, the identifier of the terminal, the S-NSSAI, the DNN, and an identifier of a first policy control network element set to which the first policy control network element belongs. The receiving module 1601 is further configured to receive an identifier of a second policy control network element set from the binding support network element. The sending module 1602 is further configured to send the identifier of the second policy control network element set to the first session management network element, and the identifier of the second policy control network element set is an identifier that is of a policy control network element set, that corresponds to the identifier of the terminal, the S-NSSAI, and the DNN, and that is stored by the binding support network element.

[0351] Optionally, as shown in FIG. 16, the first policy control network element 160 further includes a processing module 1603. The processing module 1603 is configured to determine that a same policy control network element set needs to be selected for a combination of the identifier of the terminal, the S-NSSAI, and the DNN The sending module 1602 is configured to send indication information to the binding support network element, and the indication information is used to instruct to select the same policy control network element set for the combination of the identifier of the terminal, the S-NSSAI, and the DNN

[0352] All related content of the steps in the foregoing method embodiments may be cited in function descriptions of corresponding function modules. Details are not described herein again.

[0353] In this embodiment, the first policy control network element 160 is presented in a form of function modules obtained through division performed in an integrated manner. The "module" herein may be a specific ASIC, a circuit, a processor and a memory that execute one or more software programs or firmware programs, an integrated logic circuit, and/or another component that can provide the foregoing functions. In a simple embodiment, a person skilled in the art may figure out that the first policy control network element 160 may be in a form shown in FIG. 4.

[0354] For example, the processor 401 in FIG. 4 may invoke the computer executable instruction stored in the memory 403, so that the first policy control network element 160 performs the policy control methods in the foregoing method embodiments.

[0355] Specifically, functions/implementation processes of the receiving module 1601, the sending module 1602, and the processing module 1603 in FIG. 16 may be implemented by the processor 401 in FIG. 4 by invoking the computer executable instruction stored in the memory 403. Alternatively, functions/implementation processes of the processing module 1603 in FIG. 16 may be implemented by the processor 401 in FIG. 4 by invoking the computer executable instruction stored in the memory 403, and functions/implementation processes of the receiving module 1601 and the sending module 1602 in FIG. 16 may be implemented by the communications interface 404 in FIG. 4.

[0356] The first policy control network element 160 provided in this embodiment may perform the foregoing policy control methods. Therefore, for technical effects that can be achieved by the first policy control network element 160, refer to the foregoing method embodiments. Details are not described herein again.

[0357] Optionally, an embodiment of this application further provides an apparatus (for example, the apparatus may be a chip system). The apparatus includes a processor, configured to support a first policy control network element in implementing the foregoing policy control methods, for example, in determining that a same policy control network element needs to be selected for a combination of an identifier of a terminal, S-NSSAI, and a DNN. In a possible design, the apparatus further includes a memory. The memory is configured to store a program instruction and data that are necessary for the first policy control network element. Certainly, the memory may not be in the apparatus. When the apparatus is a chip system, the apparatus may include a chip, or may include a chip and another discrete component. This is not specifically limited in this embodiment of this application.

[0358] The embodiments described in reference to Fig. 17 are not part of the invention, but illustrative examples necessary for understanding the invention.

[0359] Alternatively, for example, when function modules are obtained through division performed in an integrated manner, FIG. 17 is a schematic structural diagram of a binding support network element 170. The binding support network element 170 includes a processing module 1701 and a transceiver module 1702.

[0360] In a possible implementation, the transceiver module 1702 is configured to receive an identifier of a terminal, S-NSSAI, a DNN, and an identifier of a first policy control network element from a first policy control network element. The processing module 1701 is configured to determine that an identifier that is of a second policy control network element and that corresponds to a combination of the identifier of the terminal, the S-NSSAI, and the DNN already exists. The transceiver module 1702 is further configured to send the identifier of the second policy control network element to the first policy control network element.

[0361] Optionally, as shown in FIG. 17, the binding support network element 170 further includes a storage module 1703. The transceiver module 1702 is further configured to receive the identifier of the terminal, the S-NSSAI, the DNN, and the identifier of the second policy control network element from the second policy control network element in a process of establishing a second session. The storage module 1703 is configured to store a correspondence between the identifier of the second policy control network element and the combination of the identifier of the terminal, the S-NSSAI, and the DNN

[0362] Optionally, the transceiver module 1702 is further configured to receive indication information from the first policy control network element, and the indication information is used to instruct to select a same policy control network element for the combination of the identifier of the terminal, the S-NSSAI, and the DNN. The processing module 1701 is further configured to determine, based on the indication information, to send the identifier of the second policy control network element to the first policy control network element.

[0363] In another possible implementation, the transceiver module 1702 is configured to receive, from a first policy control network element, an identifier of a terminal, S-NSSAI, a DNN, and an identifier of a first policy control network element set to which a first policy control network element belongs. The processing module 1701 is configured to determine that an identifier that is of a second policy control network element set and that corresponds to a combination of the identifier of the terminal, the S-NSSAI, and the DNN already exists. The transceiver module 1702 is further configured to send the identifier of the second policy control network element set to the first policy control network element.

[0364] Optionally, as shown in FIG. 17, the binding support network element 170 further includes a storage module 1703. The transceiver module 1702 is further configured to receive, from a second policy control network element in a process of establishing a second session, the identifier of the terminal, the S-NSSAI, the DNN, and the identifier of the second policy control network element set to which the second policy control network element belongs. The storage module 1703 is configured to store a correspondence between the identifier of the second policy control network element set and the combination of the identifier of the terminal, the S-NSSAI, and the DNN

[0365] Optionally, the transceiver module 1702 is further configured to receive indication information from the first policy control network element, and the indication information is used to instruct to select a same policy control network element set for the combination of the identifier of the terminal, the S-NSSAI, and the DNN. The processing module 1701 is further configured to determine, based on the indication information, to send the identifier of the second policy control network element set to the first policy control network element.

[0366] All related content of the steps in the foregoing method embodiments may be cited in function descriptions of corresponding function modules. Details are not described herein again.

[0367] In this embodiment, the binding support network element 170 is presented in a form of function modules obtained through division performed in an integrated manner. The "module" herein may be a specific ASIC, a circuit, a processor and a memory that execute one or more software programs or firmware programs, an integrated logic circuit, and/or another component that can provide the foregoing functions. In a simple embodiment, a person skilled in the art may figure out that the binding support network element 170 may be in a form shown in FIG. 4.

[0368] For example, the processor 401 in FIG. 4 may invoke the computer executable instruction stored in the memory 403, so that the binding support network element 170 performs the policy control methods in the foregoing method embodiments.

[0369] Specifically, functions/implementation processes of the transceiver module 1702, the processing module 1701, and storage module 1703 in FIG. 17 may be implemented by the processor 401 in FIG. 4 by invoking the computer executable instruction stored in the memory 403. Alternatively, functions/implementation processes of the processing module 1701 in FIG. 17 may be implemented by the processor 401 in FIG. 4 by invoking the computer executable instruction stored in the memory 403, functions/implementation processes of the transceiver module 1702 in FIG. 17 may be implemented by the communications interface 404 in FIG. 4, and functions/implementation processes of the storage module 1703 in FIG. 17 may be implemented by the memory 403 in FIG. 4.

[0370] The binding support network element 170 provided in this embodiment may perform the foregoing policy control method. Therefore, for technical effects that can be achieved by the binding support network element 170, refer to the foregoing method embodiments. Details are not described herein again.

[0371] Optionally, an embodiment of this application further provides an apparatus (for example, the apparatus may be a chip system). The apparatus includes a processor, configured to support a binding support network element in implementing the foregoing policy control methods, for example, in determining that an identifier that is of a second policy control network element and that corresponds to a combination of an identifier of a terminal, S-NSSAI, and a DNN already exists. In a possible design, the apparatus further includes a memory. The memory is configured to store a program instruction and data that are necessary for the binding support network element. Certainly, the memory may not be in the apparatus. When the apparatus is a chip system, the apparatus may include a chip, or may include a chip and another discrete component. This is not specifically limited in this embodiment of this application.

[0372] All or some of the foregoing embodiments may be implemented by using software, hardware, firmware, or any combination thereof. When a software program is used to implement the embodiments, the embodiments may be implemented completely or partially in a form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the procedures or functions according to the embodiments of this application are completely or partially generated. The computer may be a general-purpose computer, a dedicated computer, a computer network, or another programmable apparatus. The computer instructions may be stored in a computer-readable storage medium or may be transmitted from a computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center through a wired (for example, a coaxial cable, an optical fiber, or a digital subscriber line (digital subscriber line, DSL)) manner or a wireless (for example, infrared, wireless, or microwave) manner. The computer-readable storage medium may be any usable medium accessible by a computer, or a data storage device, such as a server or a data center, integrating one or more usable media. The usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, or a magnetic tape), an optical medium (for example, a DVD), a semiconductor medium (for example, a solid state disk (solid state disk, SSD)), or the like.

[0373] Although this application is described with reference to the embodiments, in a process of implementing this application that claims protection, a person skilled in the art may understand and implement another variation of the disclosed embodiments by viewing the accompanying drawings, disclosed content, and the appended claims. In the claims, "comprising" (comprising) "does not exclude another component or another step, and" a "or" one" does not exclude a case of a plurality. A single processor or another unit may implement several functions enumerated in the claims. Some measures are described in dependent claims that are different from each other, but this does not mean that these measures cannot be combined to produce a better effect.

[0374] (excised)


Claims

1. A method for selecting a policy control network element, wherein the method comprises:

receiving (S1418), by a first policy control network element, a policy control creation request from a first session management network element, wherein the policy control creation request comprises an identifier of a terminal, single network slice selection assistance information, S-NSSAI, and a data network name, DNN;

sending (S 1419), by the first policy control network element, the identifier of the terminal, the S-NSSAI, the DNN, and an identifier of the first policy control network element to a binding support network element; and

receiving (S1419), by the first policy control network element, an identifier of a second policy control network element from the binding support network element, and

sending the identifier of the second policy control network element to the first session management network element, wherein the identifier of the second policy control network element is an identifier that is of a policy control network element, that corresponds to the identifier of the terminal, the S-NSSAI, and the DNN, and that is stored by the binding support network element.


 
2. The method according to claim 1,
wherein the method further comprises:

determining, by the first policy control network element, that a same policy control network element needs to be selected for a combination of the identifier of the terminal, the S-NSSAI, and the DNN; and

sending, by the first policy control network element, indication information to the binding support network element, wherein the indication information is used to instruct the binding support network element to select the same policy control network element for the combination of the identifier of the terminal, the S-NSSAI, and the DNN


 
3. A first policy control network element, configured to perform the method according to any one of claims 1 to 2.
 
4. A policy control system, comprising a first session management network element (207) and a first policy control network element (206) configured to perform the method according to claim 1 or 2, wherein
the first session management network element is configured to send a policy control creation request to the first policy control network element; and receive the identifier of a second policy control network element from the first policy control network element, and select the second policy control network element for a first session based on the identifier of the second policy control network element.
 
5. The policy control system according to claim 4, wherein the system further comprises a binding support network element, configured to receive the identifier of the terminal, the S-NSSAI, the DNN, and an identifier of the first policy control network element from the first policy control network element; and sending an identifier of a second policy control network element to the first policy control network element.
 
6. The policy control system according to claim 4 or 5, wherein

the first session management network element is further configured to receive, from a first mobility management network element, a first request message used to create the first session, wherein the first request message comprises the identifier of the terminal, the S-NSSAI, and the DNN; and

the first session management network element is further configured to select the first policy control network element for the first session.


 
7. The policy control system according to any one of claims 4 to 6, wherein

the first policy control network element is further configured to determine that a same policy control network element needs to be selected for a combination of the identifier of the terminal, the S-NSSAI, and the DNN;

the first policy control network element is further configured to send indication information to the binding support network element, wherein the indication information is used to instruct the binding support network element to select the same policy control network element for the combination of the identifier of the terminal, the S-NSSAI, and the DNN


 
8. The policy control system according to claim 7, wherein the binding support network element is further configured to: receive the indication information from the first policy control network element; and determine, based on the indication information, to send the identifier of the second policy control network element to the first policy control network element.
 
9. The policy control system according to claim 7 or 8, wherein that the first policy control network element is further configured to send indication information to the binding support network element comprises:
the first policy control network element is further configured to send the indication information to the binding support network element when determining that the terminal establishes the first session in a non-roaming scenario or a home routing scenario.
 
10. The policy control system according to any one of claims 4 to 9, wherein the binding support network element is further configured to: determine that an identifier that is of a second policy control network element and that corresponds to a combination of the identifier of the terminal, the S-NSSAI, and the DNN already exists; and send the identifier of the second policy control network element to the first policy control network element.
 
11. The policy control system according to any one of claims 4 to 10, wherein the policy control system further comprises a second session management network element, the second policy control network element, and the binding support network element;

the second session management network element is configured to receive, from a second mobility management network element, a second request message used to create a second session, wherein the second request message comprises the identifier of the terminal, the S-NSSAI, and the DNN;

the second session management network element is configured to: select the second policy control network element for the second session, and send a policy control creation request to the second policy control network element, wherein the policy control creation request comprises the identifier of the terminal, the S-NSSAI, and the DNN;

the second policy control network element is configured to: receive the policy control creation request from the second session management network element, and send the identifier of the terminal, the S-NSSAI, the DNN, and the identifier of the second policy control network element to the binding support network element; and

the binding support network element is configured to: receive the identifier of the terminal, the S-NSSAI, the DNN, and the identifier of the second policy control network element from the second policy control network element, and store a correspondence between the identifier of the second policy control network element and the combination of the identifier of the terminal, the S-NSSAI, and the DNN


 
12. A computer-readable storage medium, comprising a computer program, wherein when the computer program is run on a computer, the computer is enabled to perform the policy control method according to any one of claim 1 to 2.
 
13. A method for selecting a policy control network element, wherein the method comprises:

receiving, by a first policy control network element, a policy control creation request from a first session management network element, wherein the policy control creation request comprises an identifier of a terminal, single network slice selection assistance information, S-NSSAI, and a data network name, DNN;

sending, by the first policy control network element, the identifier of the terminal, the S-NSSAI, the DNN, and an identifier of the first policy control network element to a binding support network element;

receiving, by the binding support network element from the first policy control network element, the identifier of the terminal, the S-NSSAI, the DNN, and the identifier of the first policy control network element;

sending, by the binding support network element, an identifier of a second policy control network element to the first policy control network element, wherein the identifier of the second policy control network element is an identifier that is of a policy control network element, that corresponds to the identifier of the terminal, the S-NSSAI, and the DNN, and that is stored by the binding support network element;

receiving, by the first policy control network element, the identifier of the second policy control network element from the binding support network element, and

sending the identifier of the second policy control network element to the first session management network element.


 
14. The method according to claim 13, wherein the method further comprises:

determining, by the first policy control network element, that a same policy control network element needs to be selected for a combination of the identifier of the terminal, the S-NSSAI, and the DNN; and

sending, by the first policy control network element, indication information to the binding support network element, wherein the indication information is used to instruct the binding support network element to select the same policy control network element for the combination of the identifier of the terminal, the S-NSSAI, and the DNN


 


Ansprüche

1. Verfahren zum Auswählen eines Richtliniensteuerungs-Netzwerkelements, wobei das Verfahren Folgendes umfasst:

Empfangen (S1418), durch ein erstes Richtliniensteuerungs-Netzwerkelement, einer Richtliniensteuerungs-Erstellungsanforderung aus einem ersten Sitzungsverwaltungs-Netzwerkelement, wobei die Richtliniensteuerungs-Erstellungsanforderung eine Kennung eines Endgeräts, einzelne Netzwerk-Slice-Auswahlunterstützungsinformationen, S-NSSAI, und einen Datennetzwerknamen, DNN, umfasst;

Senden (S1419), durch das erste Richtliniensteuerungs-Netzwerkelement, der Kennung des Endgeräts, der S-NSSAI, des DNN und einer Kennung des ersten Richtliniensteuerungs-Netzwerkelements an ein Bindungsunterstützungs-Netzwerkelement; und

Empfangen (S1419), durch das erste Richtliniensteuerungs-Netzwerkelement, einer Kennung eines zweiten Richtliniensteuerungs-Netzwerkelements aus dem Bindungsunterstützungs-Netzwerkelement, und

Senden der Kennung des zweiten Richtliniensteuerungs-Netzwerkelements an das erste Sitzungsverwaltungs-Netzwerkelement, wobei die Kennung des zweiten Richtliniensteuerungs-Netzwerkelements eine Kennung ist, die von einem Richtliniensteuerungs-Netzwerkelement ist, die der Kennung des Endgeräts, den S-NSSAI und dem DNN entspricht, und die von dem Bindungsunterstützungs-Netzwerkelement gespeichert wird.


 
2. Verfahren nach Anspruch 1,
wobei das Verfahren ferner Folgendes umfasst:

Bestimmen, durch das erste Richtliniensteuerungs-Netzwerkelement, dass ein gleiches Richtliniensteuerungs-Netzwerkelement für eine Kombination von der Kennung des Endgeräts, den S-NSSAI und dem DNN ausgewählt werden muss; und

Senden, durch das erste Richtliniensteuerungs-Netzwerkelement, von Angabeinformationen an das Bindungsunterstützungs-Netzwerkelement, wobei die Angabeinformationen verwendet werden, um das Bindungsunterstützungs-Netzwerkelement anzuweisen, das gleiche Richtliniensteuerungs-Netzwerkelement für die Kombination von der Kennung des Endgeräts, den S-NSSAI und dem DNN auszuwählen.


 
3. Erstes Richtliniensteuerungs-Netzwerkelement, das konfiguriert ist, um das Verfahren nach einem der Ansprüche 1 bis 2 durchzuführen.
 
4. System zur Richtliniensteuerung, das ein erstes Sitzungsverwaltungs-Netzwerkelement (207) und ein erstes Richtliniensteuerungs-Netzwerkelement (206) umfasst, die konfiguriert sind, um das Verfahren nach Anspruch 1 oder 2 durchzuführen, wobei
das erste Sitzungsverwaltungs-Netzwerkelement konfiguriert ist, um eine Richtliniensteuerungs-Erzeugungsanforderung an das erste Richtliniensteuerungs-Netzwerkelement zu senden; und die Kennung eines zweiten Richtliniensteuerungs-Netzwerkelements aus dem ersten Richtliniensteuerungs-Netzwerkelement zu empfangen, und das zweite Richtliniensteuerungs-Netzwerkelement für eine erste Sitzung basierend auf der Kennung des zweiten Richtliniensteuerungs-Netzwerkelements auszuwählen.
 
5. System zur Richtliniensteuerung nach Anspruch 4, wobei das System ferner ein Bindungsunterstützungs-Netzwerkelement umfasst, das konfiguriert ist, um die Kennung des Endgeräts, die S-NSSAI, den DNN und eine Kennung des ersten Richtliniensteuerungs-Netzwerkelements aus dem ersten Richtliniensteuerungs-Netzwerkelement zu empfangen; und eine Kennung eines zweiten Richtliniensteuerungs-Netzwerkelements an das erste Richtliniensteuerungs-Netzwerkelement zu senden.
 
6. System zur Richtliniensteuerung nach Anspruch 4 oder 5, wobei

das erste Sitzungsverwaltungs-Netzwerkelement ferner konfiguriert ist, um aus einem ersten Mobilitätsverwaltungs-Netzwerkelement eine erste Anforderungsnachricht zu empfangen, die verwendet wird, um die erste Sitzung zu erstellen, wobei die erste Anforderungsnachricht die Kennung des Endgeräts, die S-NSSAI und den DNN umfasst; und

das erste Sitzungsverwaltungs-Netzwerkelement ferner konfiguriert ist, um das erste Richtliniensteuerungs-Netzwerkelement für die erste Sitzung auszuwählen.


 
7. System zur Richtliniensteuerung nach einem der Ansprüche 4 bis 6, wobei

das erste Richtliniensteuerungs-Netzwerkelement ferner konfiguriert ist, um zu bestimmen, dass ein gleiches Richtliniensteuerungs-Netzwerkelement für eine Kombination von der Kennung des Endgeräts, den S-NSSAI und dem DNN ausgewählt werden muss;

das erste Richtliniensteuerungs-Netzwerkelement ferner konfiguriert ist, um Angabeinformationen an das Bindungsunterstützungs-Netzwerkelement zu senden, wobei die Angabeinformationen verwendet werden, um das Bindungsunterstützungs-Netzwerkelement anzuweisen, das gleiche Richtliniensteuerungs-Netzwerkelement für die Kombination von der Kennung des Endgeräts, den S-NSSAI und dem DNN auszuwählen.


 
8. System zur Richtliniensteuerung nach Anspruch 7, wobei das Bindungsunterstützungs-Netzwerkelement weiter dazu konfiguriert ist: die Angabeinformationen aus dem ersten Richtliniensteuerungs-Netzwerkelement zu empfangen; und basierend auf den Angabeinformationen zu bestimmen, die Kennung des zweiten Richtliniensteuerungs-Netzwerkelements an das erste Richtliniensteuerungs-Netzwerkelement zu senden.
 
9. System zur Richtliniensteuerung nach Anspruch 7 oder 8, wobei, dass das erste Richtliniensteuerungs-Netzwerkelement weiter dazu konfiguriert ist, Angabeinformationen an das Bindungsunterstützungs-Netzwerkelement zu senden, Folgendes umfasst:
das erste Richtliniensteuerungs-Netzwerkelement ist ferner konfiguriert, um die Angabeinformationen an das Bindungsunterstützungs-Netzwerkelement zu senden, wenn bestimmt wird, dass das Endgerät die erste Sitzung in einem Nicht-Roaming-Szenario oder einem Home-Routing-Szenario erstellt.
 
10. System zur Richtliniensteuerung nach einem der Ansprüche 4 bis 9, wobei das Bindungsunterstützungs-Netzwerkelement ferner konfiguriert ist, um: zu bestimmen, dass eine Kennung, die von einem zweiten Richtliniensteuerungs-Netzwerkelement ist und einer Kombination von der Kennung des Endgeräts, den S-NSSAI und dem DNN entspricht, bereits existiert; und die Kennung des zweiten Richtliniensteuerungs-Netzwerkelements an das erste Richtliniensteuerungs-Netzwerkelement zu senden.
 
11. System zur Richtliniensteuerung nach einem der Ansprüche 4 bis 10, wobei das System zur Richtliniensteuerung ferner ein zweites Sitzungsverwaltungs-Netzwerkelement, das zweite Richtliniensteuerungs-Netzwerkelement und das Bindungsunterstützungs-Netzwerkelement umfasst;

das zweite Sitzungsverwaltungs-Netzwerkelement konfiguriert ist, um aus einem zweiten Mobilitätsverwaltungs-Netzwerkelement eine zweite Anforderungsnachricht zu empfangen, die verwendet wird, um eine zweite Sitzung zu erstellen, wobei die zweite Anforderungsnachricht die Kennung des Endgeräts, die S-NSSAI und den DNN umfasst;

das zweite Sitzungsverwaltungs-Netzwerkelement konfiguriert ist, um: das zweite Richtliniensteuerungs-Netzwerkelement für die zweite Sitzung auszuwählen und eine Richtliniensteuerungs-Erstellungsanforderung an das zweite Richtliniensteuerungs-Netzwerkelement zu senden, wobei die Richtliniensteuerungs-Erstellungsanforderung die Kennung des Endgeräts, die S-NSSAI und den DNN umfasst;

das zweite Richtliniensteuerungs-Netzwerkelement konfiguriert ist, um: die Richtliniensteuerungs-Erstellungsanforderung aus dem zweiten Sitzungsverwaltungs-Netzwerkelement zu empfangen und die Kennung des Endgeräts, die S-NSSAI, den DNN und die Kennung des zweiten Richtliniensteuerungs-Netzwerkelements an das Bindungsunterstützungs-Netzwerkelement zu senden; und

das Bindungsunterstützungs-Netzwerkelement konfiguriert ist, um: die Kennung des Endgeräts, die S-NSSAI, den DNN zu empfangen und die Kennung des zweiten Richtliniensteuerungs-Netzwerkelements aus dem zweiten Richtliniensteuerungs-Netzwerkelement und eine Entsprechung zwischen der Kennung des zweiten Richtliniensteuerungs-Netzwerkelements und der Kombination von der Kennung des Endgeräts, den S-NSSAI und dem DNN zu speichern.


 
12. Computerlesbares Speichermedium, umfassend Computerprogramm, wobei bei Ausführung des Computerprogramms auf einem Computer der Computer dazu befähigt ist, das Verfahren zur Richtliniensteuerung nach einem der Ansprüche 1 bis 2 durchzuführen.
 
13. Verfahren zum Auswählen eines Richtliniensteuerungs-Netzwerkelements, wobei das Verfahren Folgendes umfasst:

Empfangen, durch ein erstes Richtliniensteuerungs-Netzwerkelement, einer Richtliniensteuerungs-Erstellungsanforderung aus einem ersten Sitzungsverwaltungs-Netzwerkelement, wobei die Richtliniensteuerungs-Erstellungsanforderung eine Kennung eines Endgeräts, Einzelnetzwerk-Slice-Auswahlunterstützungsinformationen, S-NSSAI, und einen Datennetzwerknamen, DNN, umfasst;

Senden, durch das erste Richtliniensteuerungs-Netzwerkelement, der Kennung des Endgeräts, der S-NSSAI, des DNN und einer Kennung des ersten Richtliniensteuerungs-Netzwerkelements an ein Bindungsunterstützungs-Netzwerkelement;

Empfangen, durch das Bindungsunterstützungs-Netzwerkelement aus dem ersten Richtliniensteuerungs-Netzwerkelement, der Kennung des Endgeräts, der S-NSSAI, des DNN und der Kennung des ersten Richtliniensteuerungs-Netzwerkelements;

Senden, durch das Bindungsunterstützungs-Netzwerkelement, einer Kennung eines zweiten Richtliniensteuerungs-Netzwerkelements an das erste Richtliniensteuerungs-Netzwerkelement, wobei die Kennung des zweiten Richtliniensteuerungs-Netzwerkelements eine Kennung ist, die von einem Richtliniensteuerungs-Netzwerkelement ist, die der Kennung des Endgeräts, den S-NSSAI und dem DNN entspricht, und die von dem Bindungsunterstützungs-Netzwerkelement gespeichert wird;

Empfangen, durch das erste Richtliniensteuerungs-Netzwerkelement, der Kennung des zweiten Richtliniensteuerungs-Netzwerkelements aus dem Bindungsunterstützungs-Netzwerkelement, und

Senden der Kennung des zweiten Richtliniensteuerungs-Netzwerkelements an das erste Sitzungsverwaltungs-Netzwerkelement.


 
14. Verfahren nach Anspruch 13, wobei das Verfahren ferner Folgendes umfasst:
Bestimmen durch das erste Richtliniensteuerungs-Netzwerkelement, dass ein gleiches Richtliniensteuerungs-Netzwerkelement für eine Kombination von der Kennung des Endgeräts, den S-NSSAI und dem DNN ausgewählt werden muss; und Senden, durch das erste Richtliniensteuerungs-Netzwerkelement, von Angabeinformationen an das Bindungsunterstützungs-Netzwerkelement, wobei die Angabeinformationen verwendet werden, um das Bindungsunterstützungs-Netzwerkelement anzuweisen, das gleiche Richtliniensteuerungs-Netzwerkelement für die Kombination von der Kennung des Endgeräts, den S-NSSAI und dem DNN auszuwählen.
 


Revendications

1. Procédé de sélection d'un élément de réseau de commande de politique, dans lequel le procédé comprend :

la réception (S1418), par un premier élément de réseau de commande de politique, d'une demande de création de commande de politique provenant d'un premier élément de réseau de gestion de session, dans lequel la demande de création de commande de politique comprend un identifiant d'un terminal, des informations d'aide à la sélection de tranche de réseau unique, S-NSSAI, et un nom de réseau de données, DNN ;

l'envoi (S1419), par le premier élément de réseau de commande de politique, de l'identifiant du terminal, des S-NSSAI, du DNN et d'un identifiant du premier élément de réseau de commande de politique à un élément de réseau de support de liaison ; et

la réception (S1419), par le premier élément de réseau de commande de politique, d'un identifiant d'un second élément de réseau de commande de politique provenant de l'élément de réseau de support de liaison, et

l'envoi de l'identifiant du second élément de réseau de commande de politique au premier élément de réseau de gestion de session, dans lequel l'identifiant du second élément de réseau de commande de politique est un identifiant qui est d'un élément de réseau de commande de politique, qui correspond à l'identifiant du terminal, aux S-NSSAI et au DNN, et qui est stocké par l'élément de réseau de support de liaison.


 
2. Procédé selon la revendication 1,
dans lequel le procédé comprend en outre :

la détermination, par le premier élément de réseau de commande de politique, qu'un même élément de réseau de commande de politique doit être sélectionné pour une combinaison de l'identifiant du terminal, des S-NSSAI et du DNN ; et

l'envoi, par le premier élément de réseau de commande de politique, d'informations d'indication à l'élément de réseau de support de liaison, dans lequel les informations d'indication sont utilisées pour ordonner à l'élément de réseau de support de liaison de sélectionner le même élément de réseau de commande de politique pour la combinaison de l'identifiant du terminal, des S-NSSAI et du DNN.


 
3. Premier élément de réseau de commande de politique, configuré pour exécuter le procédé selon l'une quelconque des revendications 1 à 2.
 
4. Système de commande de politique, comprenant un premier élément de réseau de gestion de session (207) et un premier élément de réseau de commande de politique (206) configuré pour exécuter le procédé selon la revendication 1 ou 2, dans lequel le premier élément de réseau de gestion de session est configuré pour envoyer une demande de création de commande de politique au premier élément de réseau de commande de politique ; et recevoir l'identifiant d'un second élément de réseau de commande de politique provenant du premier élément de réseau de commande de politique, et sélectionner le second élément de réseau de commande de politique pour une première session sur la base de l'identifiant du second élément de réseau de commande de politique.
 
5. Système de commande de politique selon la revendication 4, dans lequel le système comprend en outre un élément de réseau de support de liaison, configuré pour recevoir l'identifiant du terminal, les S-NSSAI, le DNN, et un identifiant du premier élément de réseau de commande de politique provenant du premier élément de réseau de commande de politique ; et l'envoi d'un identifiant d'un second élément de réseau de commande de politique au premier élément de réseau de commande de politique.
 
6. Système de commande de politique selon la revendication 4 ou 5, dans lequel

le premier élément de réseau de gestion de session est en outre configuré pour recevoir, d'un premier élément de réseau de gestion de mobilité, un premier message de demande utilisé pour créer la première session, dans lequel le premier message de demande comprend l'identifiant du terminal, les S-NSSAI, et le DNN ; et

le premier élément de réseau de gestion de session est en outre configuré pour sélectionner le premier élément de réseau de commande de politique pour la première session.


 
7. Système de commande de politique selon l'une quelconque des revendications 4 à 6, dans lequel

le premier élément de réseau de commande de politique est en outre configuré pour déterminer qu'un même élément de réseau de commande de politique doit être sélectionné pour une combinaison de l'identifiant du terminal, des S-NSSAI et du DNN ;

le premier élément de réseau de commande de politique est en outre configuré pour envoyer des informations d'indication à l'élément de réseau de support de liaison, dans lequel les informations d'indication sont utilisées pour ordonner à l'élément de réseau de support de liaison de sélectionner le même élément de réseau de commande de politique pour la combinaison de l'identifiant du terminal, des S-NSSAI et du DNN.


 
8. Système de commande de politique selon la revendication 7, dans lequel l'élément de réseau de support de liaison est en outre configuré pour : recevoir les informations d'indication provenant du premier élément de réseau de commande de politique ; et déterminer, sur la base des informations d'indication, d'envoyer l'identifiant du second élément de réseau de commande de politique au premier élément de réseau de commande de politique.
 
9. Système de commande de politique selon la revendication 7 ou 8, dans lequel le fait que le premier élément de réseau de commande de politique est en outre configuré pour envoyer des informations d'indication à l'élément de réseau de support de liaison comprend :
le premier élément de réseau de commande de politique est en outre configuré pour envoyer les informations d'indication à l'élément de réseau de support de liaison lors de la détermination que le terminal établit la première session dans un scénario non itinérant ou un scénario de routage domestique.
 
10. Système de commande de politique selon l'une quelconque des revendications 4 à 9, dans lequel l'élément de réseau de support de liaison est en outre configuré pour : déterminer qu'un identifiant qui est d'un second élément de réseau de commande de politique et qui correspond à une combinaison de l'identifiant du terminal, des S-NSSAI et du DNN existe déjà ; et envoyer l'identifiant du second élément de réseau de commande de politique au premier élément de réseau de commande de politique.
 
11. Système de commande de politique selon l'une quelconque des revendications 4 à 10, dans lequel le système de commande de politique comprend en outre un second élément de réseau de gestion de session, le second élément de réseau de commande de politique et l'élément de réseau de support de liaison ;

le second élément de réseau de gestion de session est configuré pour recevoir, d'un second élément de réseau de gestion de mobilité, un second message de demande utilisé pour créer une seconde session, dans lequel le second message de demande comprend l'identifiant du terminal, les S-NSSAI et le DNN ;

le second élément de réseau de gestion de session est configuré pour : sélectionner le second élément de réseau de commande de politique pour la seconde session, et envoyer une demande de création de commande de politique au second élément de réseau de commande de politique, dans lequel la demande de création de commande de politique comprend l'identifiant du terminal, les S-NSSAI et le DNN ;

le second élément de réseau de commande de politique est configuré pour : recevoir la demande de création de commande de politique provenant du second élément de réseau de gestion de session, et envoyer l'identifiant du terminal, les S-NSSAI, le DNN et l'identifiant du second élément de réseau de commande de politique à l'élément de réseau de support de liaison ; et

l'élément de réseau de support de liaison est configuré pour : recevoir l'identifiant du terminal, les S-NSSAI, le DNN et l'identifiant du second élément de réseau de commande de politique provenant du second élément de réseau de commande de politique, et stocker une correspondance entre l'identifiant du second élément de réseau de commande de politique et la combinaison de l'identifiant du terminal, des S-NSSAI et du DNN.


 
12. Support de stockage lisible par ordinateur, comprenant un programme informatique, dans lequel, quand le programme informatique est exécuté sur un ordinateur, l'ordinateur est capable de mettre en Ĺ“uvre le procédé de commande de politique selon l'une quelconque des revendications 1 à 2.
 
13. Procédé de sélection d'un élément de réseau de commande de politique, dans lequel le procédé comprend :

la réception, par un premier élément de réseau de commande de politique, d'une demande de création de commande de politique provenant d'un premier élément de réseau de gestion de session, dans lequel la demande de création de commande de politique comprend un identifiant d'un terminal, des informations d'aide à la sélection de tranche de réseau unique, S-NSSAI, et un nom de réseau de données, DNN ;

l'envoi, par le premier élément de réseau de commande de politique, de l'identifiant du terminal, des S-NSSAI, du DNN et d'un identifiant du premier élément de réseau de commande de politique à un élément de réseau de support de liaison ;

la réception, par l'élément de réseau de support de liaison provenant du premier élément de réseau de commande de politique, de l'identifiant du terminal, des S-NSSAI, du DNN et de l'identifiant du premier élément de réseau de commande de politique ;

l'envoi, par l'élément de réseau de support de liaison, d'un identifiant d'un second élément de réseau de commande de politique au premier élément de réseau de commande de politique, dans lequel l'identifiant du second élément de réseau de commande de politique est un identifiant qui est d'un élément de réseau de commande de politique, qui correspond à l'identifiant du terminal, aux S-NSSAI et au DNN, et qui est stocké par l'élément de réseau de support de liaison ;

la réception, par le premier élément de réseau de commande de politique, de l'identifiant du second élément de réseau de commande de politique provenant de l'élément de réseau de support de liaison, et

l'envoi de l'identifiant du second élément de réseau de commande de politique au premier élément de réseau de gestion de session.


 
14. Procédé selon la revendication 13, dans lequel le procédé comprend en outre :

la détermination, par le premier élément de réseau de commande de politique, qu'un même élément de réseau de commande de politique doit être sélectionné pour une combinaison de l'identifiant du terminal, des S-NSSAI et du DNN ; et

l'envoi, par le premier élément de réseau de commande de politique, d'informations d'indication à l'élément de réseau de support de liaison, dans lequel les informations d'indication sont utilisées pour ordonner à l'élément de réseau de support de liaison de sélectionner le même élément de réseau de commande de politique pour la combinaison de l'identifiant du terminal, des S-NSSAI et du DNN.


 




Drawing

































































Cited references

REFERENCES CITED IN THE DESCRIPTION



This list of references cited by the applicant is for the reader's convenience only. It does not form part of the European patent document. Even though great care has been taken in compiling the references, errors or omissions cannot be excluded and the EPO disclaims all liability in this regard.

Non-patent literature cited in the description