WO2019114684A1 - 用户策略的获取 - Google Patents

用户策略的获取 Download PDF

Info

Publication number
WO2019114684A1
WO2019114684A1 PCT/CN2018/120226 CN2018120226W WO2019114684A1 WO 2019114684 A1 WO2019114684 A1 WO 2019114684A1 CN 2018120226 W CN2018120226 W CN 2018120226W WO 2019114684 A1 WO2019114684 A1 WO 2019114684A1
Authority
WO
WIPO (PCT)
Prior art keywords
rule
identification information
network
policy
network element
Prior art date
Application number
PCT/CN2018/120226
Other languages
English (en)
French (fr)
Inventor
朱方园
李岩
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP18889766.4A priority Critical patent/EP3720048B1/en
Publication of WO2019114684A1 publication Critical patent/WO2019114684A1/zh
Priority to US16/897,548 priority patent/US11381956B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08—Mobility data transfer
    • H04W8/082—Mobility data transfer for traffic bypassing of mobility servers, e.g. location registers, home PLMNs or home agents
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0894—Policy-based network configuration management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H04W8/20—Transfer of user or subscriber data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/18—Selecting a network or a communication service
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08—Mobility data transfer
    • H04W8/14—Mobility data transfer between corresponding nodes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
    • H04W8/24—Transfer of terminal data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/26—Network addressing or numbering for mobility support

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a method, device, and system for acquiring a user policy.
  • the network segmentation technology provides a network environment that is isolated from each other in different application scenarios by means of a virtual independent logical network on the same network infrastructure, so that different application scenarios can customize network functions and features according to their respective requirements, thereby ensuring the requirements of different services. .
  • APPs Applications, APPs
  • 5G communication there are multiple applications (Applications, APPs) on the user equipment. Because different APPs have different requirements for delay and bandwidth, the types of network slices required by users to start different APPs are also different. Different network slice types may be identified by network slice identification information.
  • the network slice identification information is Single Network Slice Selection Assistance Information (S-NSSAI).
  • the user equipment can obtain a UE Route Selection Policy (URSP) from the 5G core network, and then, according to the URSP, decide how to route the service flow to an existing Packet Data Unit (PDU) session. Or trigger the establishment of a new PDU session based on URSP.
  • URSP UE Route Selection Policy
  • the network slice selection policy (NSSP) in the URSP includes the S-NSSAI corresponding to different APPs, so the user equipment can Correspondence of S-NSSAI, select a network slice that satisfies the APP requirements and establish a session.
  • the URSP of the visited public land mobile network (VPLMN) in the user equipment is based on the URSP and the VPLMN in the home public land mobile network (HPLMN). Generated by the mapping relationship between NSSAI and S-NSSAI in HPLMN. Therefore, the user equipment may not obtain the information of the APP that can be used locally in the VPLMN according to the URSP of the VPLMN, and the user equipment cannot use the APP in the VPLMN, thereby reducing the service experience of the user.
  • the United States deployed a server that provides services for an application (for example, Facebook), but China does not deploy it, so the user device cannot access the application's server in China, and the application cannot be used.
  • an application for example, Facebook
  • the Chinese URSP obtained by the Chinese mobile user does not have the information of the application, so the user cannot use the application in the United States, thereby causing The user experience is reduced.
  • Embodiments of the present invention provide a method, device, and system for acquiring a user policy.
  • an embodiment of the present application provides a method for obtaining a user policy, where the method includes:
  • the first policy control function network element (eg, the first PCF network element) of the VPLMN receives the first user policy of the HPLMN from the second policy control function network element (eg, the second PCF network element) of the HPLMN (eg, the first URSP) ).
  • the first user policy includes a first rule, where the first rule is used to indicate first network slice identification information (eg, the first S-NSSAI), the first application, and the first data network identification information (eg, the first DNN).
  • the association between the three, the first data network identification information is used to identify the first data network (eg, the first DN), the first data network allows the LBO and supports the first application and the second application.
  • the first policy control function network element sends a second user policy (eg, a second URSP) of the VPLMN to the user equipment, where the second user policy includes a second rule and a third rule, and the second rule is used to indicate the second network slice identification information.
  • the second user policy includes a second rule and a third rule
  • the second rule is used to indicate the second network slice identification information.
  • the second S-NSSAI the association between the first application and the first data network identification information
  • the third rule is used to indicate the second network slice identification information, the second application, and the first data network identification information The connection between the three.
  • the second user policy of the VPLMN acquired by the user equipment includes information of the APP that is not present in the first user policy of the HPLMN, but can be used in the LBO scenario of the VPLMN, such as the information of the second application.
  • the user equipment can use more APP services in the LBO scenario of the VPLMN according to the second user policy obtained in the solution, thereby improving the user experience.
  • the first policy control function network element also sends the identity of the VPLMN to the user equipment.
  • the identifier of the VPLMN is associated with the second user policy. Therefore, when the user equipment moves from the other area to the VPLMN, the second user policy can be learned according to the identifier of the VPLMN, thereby preventing the user equipment from requesting the second user policy again, and the interaction between the user equipment and the network can be reduced, thereby reducing The delay has increased efficiency.
  • the first policy control function network element also sends the first user policy and the identity of the HPLMN to the user equipment.
  • the identifier of the HPLMN is associated with the first user policy.
  • the user equipment can obtain the identity of the first user policy and the HPLMN. Therefore, when the user equipment moves from the other area to the HPLMN and starts the APP, the first URSP can be learned according to the identifier of the HPLMN, thereby preventing the user equipment from requesting to acquire the first user policy, thereby reducing interaction between the user equipment and the network, thereby Reduced latency and increased efficiency.
  • the first policy control function network element receives the indication information from the second policy control function network element before transmitting the first user policy and the identity of the HPLMN to the user equipment.
  • the indication information is used to trigger the transmission of the first user policy and the identity of the HPLMN to the user equipment. Therefore, the first policy control function network element can learn the scenario in which the user equipment does not have the first user policy. In this scenario, the indication information triggers the first policy control function network element to send the first user policy and the HPLMN to the user equipment. logo. Therefore, the user equipment is repeatedly obtained from the first user policy, and the interaction between the user equipment and the network can be reduced, thereby reducing the delay.
  • the method further includes: the first policy control function network element adds the fourth rule to the first user policy.
  • the fourth rule includes an association between the first network slice identification information, the second application, and the first data network identification information.
  • the first policy control function network element determines the second user policy according to the first user policy after joining the fourth rule.
  • the second user policy includes information of the APP that is not present in the first user policy of the HPLMN but that can be used in the LBO scenario of the VPLMN.
  • the method further includes: the first policy control function network element determines that the first data network allows the LBO, and determines that the first data network supports the second application. Therefore, the first policy control function network element can learn the first data network that allows the LBO, and then determine the second application supported by the first data network.
  • the first policy control function network element may generate the second user policy according to the first user policy after joining the fourth rule.
  • the first policy control function network element determines the second user policy according to the first user policy after joining the fourth rule, including The first policy control function network element receives the first mapping relationship between the first network slice identifier information and the second network slice identifier information from the access and mobility management function network element (for example, the AMF network element) of the VPLMN, and Determining the second user policy according to the first mapping relationship and the first user policy after joining the fourth rule. Therefore, the first policy control function network element may generate the second user policy according to the first user policy after joining the fourth rule and the first mapping relationship.
  • the access and mobility management function network element for example, the AMF network element
  • the first policy control function network element determines the second user policy according to the first mapping relationship and the first user policy after joining the fourth rule, including: the first policy control function network element according to the first mapping
  • the first network slice identifier information in the first user policy after the fourth rule is added to the second network slice identifier information to generate a second user policy. Therefore, when the second network slice identifier information is associated with the first network slice identifier information, the first policy control function network element can generate the second user by mapping the first network slice identifier information to the second network slice identifier information.
  • the method further includes: receiving, by the first policy control function network element, the first network slice identifier information and the second network slice identifier information from the access and mobility management function network element of the VPLMN A mapping relationship, the first mapping relationship being used for generating a second user policy. Therefore, when the second network slice identifier information corresponds to the first network slice identifier information, the first policy control function network element can implement the network slice identifier information in the HPLMN to the network slice identifier information in the VPLMN according to the obtained first mapping relationship. The mapping, which generates a second user policy.
  • the first user policy also includes a fifth rule.
  • the fifth rule is used to indicate the association between the third network slice identification information, the third application and the second data network identification information
  • the second data network identification information is used to identify the second data network
  • the second data network prohibits the LBO .
  • the second user policy further includes a sixth rule, where the sixth rule is used to indicate an association between the fourth network slice identification information, the third application, and the second data network identification information.
  • the fourth network slice identifier information is the same as the third network slice identifier information.
  • the first user policy also includes a fifth rule.
  • the fifth rule is used to indicate the association between the third network slice identification information, the third application and the second data network identification information
  • the second data network identification information is used to identify the second data network
  • the second data network prohibits the LBO .
  • the second user policy further includes a sixth rule, where the sixth rule is used to indicate an association between the fourth network slice identification information, the third application, and the second data network identification information.
  • the fourth network slice identifier information corresponds to the third network slice identifier information. Therefore, the second user policy further includes an application supported by the data network that prohibits the LBO, so that the user equipment can also use an application that cannot be used in the LBO scenario in the VPLMN.
  • the method further includes: receiving, by the first policy control function network element, the third network slice identifier information and the fourth network slice identifier information from the access and mobility management function network element of the VPLMN a second mapping relationship; and determining fourth network slice identification information according to the third network slice identification information and the second mapping relationship. Therefore, when the second network slice identifier information corresponds to the first network slice identifier information, the first policy control function network element can implement the network slice identifier information in the HPLMN to the network slice identifier information in the VPLMN according to the obtained second mapping relationship.
  • the mapping so that the generated second user policy also includes applications supported by the data network that prohibits LBO.
  • the present application further discloses a method for acquiring a user policy, the method comprising: a second policy control function network element (eg, a second PCF network element) of the HPLMN to the first policy control function network element of the VPLMN (eg, the first PCF network element sends a user policy (eg, URSP) of the HPLMN.
  • the second policy control function network element sends the indication information to the first policy control function network element.
  • the indication information is used to trigger the sending of the user policy and the identifier of the HPLMN to the user equipment, and the identifier of the HPLMN is associated with the user policy.
  • the first policy control function network element of the VPLMN can receive the user policy of the HPLMN, thereby generating a user policy of the VPLMN according to the user policy of the HPLMN.
  • the user policy of the VPLMN includes the information of the APP that is not present in the user policy of the HPLMN but can be used in the LBO scenario of the VPLMN.
  • the user equipment can use more APP services in the LBO scenario of the VPLMN according to the obtained second user policy, thereby improving the user experience.
  • the first policy control function network element of the VPLMN after receiving the triggering of the indication information, the first policy control function network element of the VPLMN sends the user policy and the identifier of the HPLMN to the user equipment, which avoids the user equipment repeatedly acquiring the user policy of the HPLMN, and can reduce the interaction between the user equipment and the network. , which reduces the delay.
  • the present application also discloses a method for acquiring a user policy, the method comprising: a VPLMN access and mobility management function network element (eg, an AMF network element) to a policy control function network element of the VPLMN (eg, The PCF network element transmits a mapping relationship between the first network slice identification information (eg, the first S-NSSAI) and the second network slice identification information (eg, the second S-NSSAI).
  • the first network slice identification information is network slice identification information (for example, S-NSSAI) in the HPLMN supported by the data network (for example, DN), and the second network slice identification information is a network slice identifier in the VPLMN supported by the data network.
  • the mapping relationship is used for determining the second network slice identification information.
  • the user equipment needs to obtain the mapping relationship between the first network slice identifier information and the second network slice identifier information from the access and mobility management function network element of the VPLMN, and generate a second user policy.
  • the user equipment perceives the roaming agreement between the VPLMN and the HPLMN through the above mapping relationship.
  • the user equipment acquires the second user policy from the network side, so that the roaming agreement between the VPLMN and the HPLMN is not required to be perceived, thereby improving the security performance of the network.
  • the embodiment of the present application provides a device for acquiring a user policy, where the device for acquiring a user policy has a function of implementing a behavior of a first policy control function network element (for example, a first PCF network element) in the foregoing method.
  • the functions may be implemented by hardware or by corresponding software implemented by hardware.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the above-described apparatus for acquiring a user policy includes a processor and a transceiver configured to process the device for acquiring a user policy to perform a corresponding function in the above method.
  • the transceiver is configured to implement communication between the device for acquiring the user policy and the second policy control function network element/access and mobility management function network element/user equipment.
  • the means for obtaining a user policy may further comprise a memory for coupling with the processor, the program instructions and data necessary to acquire the user policy.
  • the embodiment of the present application provides an apparatus for acquiring a user policy, where the apparatus for acquiring a user policy has a function of implementing a behavior of a second policy control function network element (for example, a second PCF network element) in the foregoing method.
  • the functions may be implemented by hardware or by corresponding software implemented by hardware.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the structure of the device for obtaining the user policy includes a processor and a transceiver, the processor being configured to acquire a user policy to perform a corresponding function in the above method.
  • the transceiver is configured to implement communication between a device that acquires a user policy and a first policy control function network element.
  • the means for obtaining a user policy may further comprise a memory for coupling with the processor, the program instructions and data necessary to acquire the user policy.
  • an embodiment of the present application provides an apparatus for acquiring a user policy, where the apparatus for acquiring a user policy has a function of implementing an access and mobility management function network element (for example, an AMF network element) in the foregoing method.
  • the functions may be implemented by hardware or by corresponding software implemented by hardware.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the above-described apparatus for acquiring a user policy includes a processor and a transceiver configured to process a device for acquiring a user policy to perform a corresponding function in the above method.
  • the transceiver is configured to implement communication between a device that acquires a user policy and a policy control function network element of the VPLMN.
  • the means for obtaining a user policy may further comprise a memory for coupling with the processor, the program instructions and data necessary to acquire the user policy.
  • embodiments of the present application provide a computer readable storage medium having instructions stored therein that, when run on a computer, cause the computer to perform the methods described in the above aspects.
  • embodiments of the present application provide a computer program product comprising instructions that, when run on a computer, cause the computer to perform the methods described in the various aspects above.
  • the present application provides a chip system including a processor for supporting the above-mentioned device for acquiring a user policy to implement the functions involved in the above aspects, for example, generating or processing information involved in the above method.
  • the chip system further includes a memory for storing program instructions and data necessary for the device that acquires the user policy.
  • the chip system can be composed of chips, and can also include chips and other discrete devices.
  • FIG. 1 is a schematic diagram of a 5G roaming communication system in a local break-out (LBO) scenario according to an embodiment of the present application;
  • FIG. 2 is a flowchart of a method for acquiring a user policy according to an embodiment of the present application
  • FIG. 3 is a flowchart of still another method for acquiring a user policy according to an embodiment of the present application
  • FIG. 4 is a flowchart of still another method for acquiring a user policy according to an embodiment of the present application.
  • FIG. 5 is a signaling interaction diagram of still another method for acquiring a user policy according to an embodiment of the present application
  • FIG. 6 is a signaling interaction diagram of still another method for acquiring a user policy according to an embodiment of the present application.
  • FIG. 7 is a signaling interaction diagram of still another method for acquiring a user policy according to an embodiment of the present application.
  • FIGS. 8A and 8B are schematic diagrams showing the structure of an apparatus for acquiring a user policy according to an embodiment of the present application.
  • FIG. 1 is a schematic diagram of a 5G roaming communication system in an LBO scenario according to an embodiment of the present application.
  • the control plane function and the forwarding plane function of the mobile gateway are decoupled, and the separated control plane functions and the third generation partnership project (3GPP) traditional control network element mobility management
  • 3GPP third generation partnership project
  • MME mobility management entity
  • the user plane function (UPF) network element can implement user plane functions (SGW-U and PGW-U) of a serving gateway (SGW) and a packet data network gateway (PGW).
  • SGW-U and PGW-U user plane functions
  • SGW serving gateway
  • PGW packet data network gateway
  • the unified control plane network element can be decomposed into an access and mobility management function (AMF) network element and a session management function (SMF) network element.
  • AMF access and mobility management function
  • SMF session management function
  • the communication system includes at least a User Equipment (UE) 101, each network device in the VPLMN, and each network device in the HPLMN.
  • the network device in the VPLMN and the network device in the HPLMN respectively include a policy control function (PCF) network element 105 and a PCF network element 107.
  • PCF policy control function
  • the user equipment 101 involved in the system is not limited to a 5G network, and includes: a mobile phone, an Internet of Things device, a smart home device, an industrial control device, a vehicle device, and the like.
  • the user equipment may also be referred to as a terminal equipment, a mobile station, a mobile station, a remote station, a remote terminal, an access terminal, or an access terminal.
  • the user terminal (User Terminal) and the user agent (User Agent) are not limited herein.
  • the above-mentioned user equipment may also be a vehicle in a vehicle-to-vehicle communication in communication with a vehicle-to-vehicle (V2V).
  • V2V vehicle-to-vehicle
  • the PCF network elements (e.g., PCF network element 105, PCF network element 107) involved in the system include policy control functions.
  • the PCF network element also supports a unified policy framework to manage network behavior.
  • the PCF network element can also access subscription information related to policies in the unified data repository.
  • a PCF network element may also be referred to as a PCF entity or a PCF device.
  • the network device in the VPLMN further includes a Radio Access Network (RAN) device 102 and an AMF network element 103.
  • the AMF network element 103 can be responsible for attaching, mobility management, tracking area update process, and the like of the terminal device.
  • AMF network elements can also be referred to as AMF devices or AMF entities.
  • the RAN device 102 is a device for providing wireless communication functionality to the UE 101.
  • the RAN device may include various forms of base stations, such as a macro base station, a micro base station (also referred to as a small station), a relay station, an access point, and the like.
  • base stations such as a macro base station, a micro base station (also referred to as a small station), a relay station, an access point, and the like.
  • the name of a device having a base station function may be different, for example, in an LTE system, an evolved Node B (evolved NodeB, eNB or eNodeB), in the third In a 3rd generation (3G) system, it is called a Node B or the like.
  • gNB gNodeB
  • the network device in the VPLMN also includes a Network Slice Selection Function (NSSF) network element 104 in the VPLMN.
  • the NSSF network element 104 can select a network slice for the user equipment.
  • the NSSF network element may also be referred to as an NSSF device or an NSSF entity.
  • the network device in the HPLMN further includes a Unified Data Management (UDM) network element 106.
  • the UDM network element 106 is capable of storing subscription data for the user.
  • the user's subscription data includes contract management data related to mobility management and subscription data related to session management.
  • the UDM network element may also be referred to as a UDM device or a UPF entity.
  • the UE 101 can access the services of the VPLMN by registering in the VPLMN. During the registration process, the UE 101 selects an initial AMF device 103 through the RAN device 102, and the initial AMF device 103 requests the UDM network element 106 of the HPLMN to acquire the subscription data of the UE 101. If the initial AMF device 103 is unable to provide service to the UE 101, the initial AMF device 103 requests the NSSF network element 104 to select another AMF device that can satisfy the user's needs to provide services to the user.
  • the PCF network element 105 in the VPLMN may request the PCF network element 107 in the HPLMN to acquire the URSP of the HPLMN, then generate the URSP of the VPLMN and send it to the UE 101.
  • the UE 101 initiates the service of the APP in the VPLMN, the session is established according to the URSP of the VPLMN.
  • Each of the foregoing network elements may be a network component implemented on dedicated hardware, an instance of software running on dedicated hardware, or an instance of a virtualization function on an appropriate platform.
  • the virtualization platform may be a cloud platform. .
  • the embodiments of the present application can also be applied to other communication technologies for the future.
  • the network architecture and the service scenario described in this application are for the purpose of more clearly explaining the technical solutions of the present application, and do not constitute a limitation of the technical solutions provided by the present application.
  • Those skilled in the art may know that with the evolution of the network architecture and new business scenarios, The technical solution provided by the present application is equally applicable to similar technical problems.
  • the following takes the 5G roaming communication system in the LBO scenario as shown in FIG. 1 as an example.
  • the technical solutions of the present application are described in detail through some embodiments.
  • the following embodiments may be combined with each other, and the same or similar concepts or processes may not be described in some embodiments.
  • FIG. 2 is a flowchart of a method for acquiring a user policy according to an embodiment of the present application.
  • the method can be used in the scenario that the user equipment acquires the user policy of the VPLMN from the policy control function network element of the VPLMN.
  • the method may include:
  • the second policy control function network element of the HPLMN sends the first user policy of the HPLMN to the first policy control function network element of the VPLMN.
  • the first policy control function network element of the VPLMN receives the first user policy of the HPLMN from the second policy control function network element of the HPLMN.
  • the first user policy includes a first rule.
  • the first rule is used to indicate an association between the first network slice identifier information, the first application, and the first data network identifier information, where the first data network identifier information is used to identify the first data network, and the first data network allows the LBO And supporting the first application and the second application.
  • the first policy control function network element is the PCF network element 105 of the VPLMN in FIG. 1
  • the second policy control function network element is the PCF network element 107 of the HPLMN in FIG.
  • the first user policy may be the first URSP.
  • the first network slice identification information may be the first S-NSSAI.
  • the first data network can be the first DN.
  • the first data network identification information used to identify the first data network may be a first data network name (DNN).
  • the first URSP described above is as shown in Table 1.
  • the DNN corresponding to the network slice identified as S-NSSAI 1 is DNN 1, where DNN 1 is the identity of DN 1, and DN 1 supports APP 1.
  • the first rule included in the first URSP is used to indicate an association between S-NSSAI 1, APP 1 and DNN 1.
  • the S-NSSAI corresponding to the APP 1 is determined as the S-NSSAI 1 according to the first URSP, and then the session establishment process is initiated according to the S-NSSAI 1 identifier, thereby establishing communication between the user equipment and the DN 1. connection.
  • DN 1 allows LBO
  • DN1 also supports APP 2.
  • the second PCF network element when the second PCF network element receives the request message for obtaining the first URSP sent by the first PCF network element, or when the first PCF invokes the first URSP service, the second PCF network element sends the first PCF network element to the first PCF network element.
  • the first URSP The process of obtaining the first URSP from the second PCF network element by the first PCF network element may be further described in conjunction with FIG. 5 or FIG. 6.
  • the first policy control function network element sends a second user policy to the user equipment.
  • the user equipment receives the second user policy from the first policy control function network element.
  • the second user policy includes a second rule and a third rule, where the second rule is used to indicate association between the second network slice identification information, the first application, and the first data network identification information, where the third rule is used. An association between the second network slice identification information, the second application, and the first data network identification information is indicated.
  • the user equipment is the UE 101 in FIG.
  • the second user policy can be a second URSP.
  • the second network slice identification information may be a second S-NSSAI.
  • the first policy control function network element may first send a second user policy to the access and mobility management network element (for example, the AMF network element 103 in FIG. 1 by the access and mobility management network element). Forwarding the second user policy to the user equipment.
  • the access and mobility management network element for example, the AMF network element 103 in FIG. 1 by the access and mobility management network element.
  • the second URSP of the VPLMN obtained by the user equipment includes information of the APP that is not present in the first URSP of the HPLMN, but can be used in the LBO scenario of the VPLMN, for example, with the second application described above.
  • the third rule of association The user equipment can use more APP services in the LBO scenario of the VPLMN according to the second URSP obtained in the solution, thereby improving the user experience.
  • a network slice with a network slice type of S-NSSAI 1 is deployed in the HPLMN, and the first URSP of the HPLMN includes the correspondence between APP 1, S-NSSAI 1, and DNN 1.
  • the user equipment can establish a session connection with the APP 1 server.
  • the second URSP in the VPLMN obtained by the user equipment is obtained according to the first URSP in the HPLMN, so the second URSP of the VPLMN includes the correspondence relationship associated with APP 1 and DNN 1. Therefore, in VPLMN, the user equipment can still only establish a session connection with the APP 1 server, that is, only APP 1 can be used.
  • DN 1 is allowed for LBO, and DN 1 also includes APP 2 server, so in VPLMN, APP 2 server can substantially provide APP 2 service for user equipment.
  • APP 2 server can substantially provide APP 2 service for user equipment.
  • the second URSP of the VPLMN includes the association corresponding to the APP 2. Therefore, the user equipment can use APP2, which improves the user experience.
  • the first S-NSSAI in the second URSP of the VPMN is the same as the second S-NSSAI in the first URSP of the HPMN, or the second S-NSSAI corresponds to the first S-NSSAI, the two The aspects are described in detail.
  • the second rule in the second URSP is the same as the first rule of the first URSP. Since the DN of the DNN1 identifier allows LBO, and the DN1 supports APP2 in addition to APP1. Therefore, the second URSP also includes the association between S-NSSAI 1, APP 2, and DNN 1, as shown in Table 2. The association between S-NSSAI 1, APP 2 and DNN 1 is the third rule in the second URSP.
  • the second rule in the second URSP corresponds to the first rule of the first URSP.
  • the first S-NSSAI is the above S-NSSAI 1
  • the second S-NSSAI corresponding to the S-NSSAI 1 is eMBB. Therefore, the association between the three of APP1, eMBB, and DNN1 (ie, the second rule described above) is included in the second URSP. Since the DN of the DNN1 identifier allows LBO, and the DN1 supports APP2 in addition to APP1. Therefore, the second URSP also includes the association between APP 2, eMBB, and DNN 1 (ie, the third rule), as shown in Table 3. The determination of the second URSP can be further described in conjunction with FIG.
  • the first policy control function network element may determine the second URSP through steps S202 to S205.
  • Steps S202 and S203 are optional steps, that is, the first policy control function network element may also determine the first DN and the second application by other means, which is not limited in this embodiment.
  • the first policy control function network element determines that the first data network allows LBO.
  • the first policy control function network element controls the correspondence between the DNN and the LBO in the function network element according to the first policy, and determines the DN of the LUR allowed in the first URSP, for example, First DN.
  • the correspondence between the DNN and the LBO may be configured in advance by the network management system in the first policy control function network element.
  • the correspondence between the DNN and the LBO can be expressed in the form of a DNN that allows the LBO, for example:
  • the correspondence between the DNN and the LBO can also be expressed in the form of a table, as shown in Table 4.
  • the correspondence between the DNN and the LBO includes: the DN 1 identified by the DNN 1 is the LBO allowed, and the DN 2 identified by the DNN 2 is the LBO disabled.
  • the first policy control function network element may further determine that the second DN is not the DN of the allowed LBO.
  • the first URSP mentioned above also includes a second DN that prohibits LBO.
  • the first URSP further includes a fifth rule for indicating an association between the third S-NSSAI, the third application, and the second DNN.
  • the second DNN is used to identify the second DN
  • the second DN is used to support the third application.
  • the third S-NSSAI is S-NSSAI 2
  • the third application is APP 3
  • the second DNN is DNN 2.
  • the first URSP including the fifth rule may be as shown in Table 5.
  • the fifth rule included in the first URSP is used to indicate the association between S-NSSAI 2, APP 3, and DNN 2.
  • the difference between the first rule and the fifth rule is that the DN 1 identified by the DNN 1 in the first rule is the DN of the LBO, and the DN 2 identified by the DNN 2 in the fifth rule is not the DN of the LBO, or Said that DN 2 is the DN that prohibits LBO.
  • the first policy control function network element determines that the first data network supports the second application.
  • the first policy control function network element determines that the first DN of the LBO is allowed, the corresponding relationship between the DNN and the APP in the function network element is determined according to the first policy, and the APP supported by the first DN is determined, for example, the first application. And the second application.
  • the first policy control function network element determines, from the APP supported by the first DN, an APP that is not involved in the first URSP, such as a second application.
  • the correspondence between the DNN and the APP may be configured in advance by the network management system in the first policy control function network element. For example, the above correspondence is as shown in Table 6. In the example of Table 6, DN 1 corresponding to DNN 1 supports APP 1 and APP 2.
  • the first URSP includes the association between S-NSSAI 1, APP 1 and DNN 1, but APP 2 is not involved in the first URSP. Therefore, the first policy control function network element may determine that the second application that is also supported by the first DN is APP 2. That is, the user equipment cannot use APP 2 in the HPLMN, but the user equipment can use APP 2 in the LBO scenario of the VPLMN.
  • step S203 and subsequent S204 and S205 need not be performed.
  • the first policy control function network element adds the fourth rule to the first user policy, where the fourth rule includes an association between the first network slice identifier information, the second application, and the first data network identifier information.
  • the first S-NSSAI associated with the first DNN is S-NSSAI 1.
  • the second application that is supported by the DN of the DNN identifier determined according to the foregoing step S203 is APP 2. Therefore, the fourth rule includes an association between S-NSSAI 1, APP 2, and the first DNN. Combined with the first URSP shown in Table 1, the first URSP after adding the fourth rule can be as shown in Table 2.
  • the first URSP when the first URSP includes the foregoing fifth rule, after the fourth rule is added, the first URSP may be as shown in Table 7, and details are not described herein again.
  • the first policy control function network element determines the second user policy according to the first user policy after joining the fourth rule.
  • the second URSP is the first URSP after the fourth rule is added.
  • the second URSP may be as shown in Table 2, the second URSP includes a second rule indicating an association between the second S-NSSAI, the first APP, and the first DNN, and indicating the second S-NSSAI, the second The third rule associated between the APP and the first DNN.
  • the second URSP when the first URSP includes a second DN that prohibits LBO, and the corresponding third S-NSSAI of the DNN 2 in the VPLMN is the same as the fourth S-NSSAI in the HPLMN, the second URSP may be as shown in Table 7. As shown, the second URSP further includes a sixth rule indicating an association between the fourth S-NSSAI, the third APP, and the second DNN. That is to say, the above fifth rule and the sixth rule are the same.
  • the first policy control function network element determines the second URSP.
  • the step 205 includes: the first policy control function network element acquires the S-NSSAI and the HPLMN in the VPLMN.
  • the second user policy is determined according to the mapping relationship and the first user policy after the fourth rule is added, which may be further described in conjunction with FIG. 3 .
  • the second URSP determined by the first policy control function network element includes information of an APP that can be used in the LBO scenario of the VPLMN.
  • the user equipment can use the APP service supported in the scenario in the LBO scenario of the VPLMN according to the second URSP obtained in the solution.
  • FIG. 3 is a flowchart of still another method for acquiring a user policy according to an embodiment of the present application.
  • the method may be used to obtain a scenario of a VPLMN user policy from a policy control function network element of the VPLMN when the S-NSSAI in the VPLMN corresponds to the S-NSSAI in the HPLMN.
  • the policy control function network element of the VPLMN generates a second URSP by means of mapping.
  • the method may include:
  • Step S301 can refer to the description of S201 in FIG. 2, and step S307 can refer to the description of S206 in FIG. 2, and details are not described herein again.
  • the first policy control function network element may further determine the second URSP through steps S302 to S306.
  • Steps S302 to S304 can refer to descriptions of S202 to S204 in FIG. 2, and details are not described herein again.
  • the first policy control function network element may perform the following steps S305 and S306.
  • the first policy control function network element receives a first mapping relationship between the first network slice identifier information and the second network slice identifier information from the access and mobility management function network element of the VPLMN.
  • the first mapping relationship can be used for generation of a second user policy.
  • the mobility management function network element is the AMF network element 103 in FIG.
  • the first mapping relationship between the first S-NSSAI and the second S-NSSAI may be generated and provided by a network slice selection function network element (eg, NSSF network element 104 in FIG. 1) according to a roaming agreement between the VPLMN and the HPLMN.
  • a network slice selection function network element eg, NSSF network element 104 in FIG. 1
  • the first mapping relationship between the first S-NSSAI and the second S-NSSAI may also be generated by the AMF network element according to the foregoing roaming protocol.
  • the roaming agreement can be a Service Level Agreement (SLA).
  • SLA Service Level Agreement
  • Different operators can deploy different types of network slices.
  • Different network slice types can be identified by standard S-NSSAI or by unique S-NSSAI.
  • the standard S-NSSAI is an S-NSSAI that can be recognized by operators.
  • 3GPP third generation partnership project
  • eMBB enhanced mobile broadband
  • URLLC ultra-reliable low latency communications
  • MIoT Massive IoT
  • the network slice identified by the unique S-NSSAI may not be recognized by all operators. Only the operator deploying the network slice identified by the S-NSSAI can identify the unique S-NSSAI.
  • network slice types other than the three network slice types specified in the above 3GPP standards can be considered as unique types, such as vehicle-to-everything (V2X).
  • V2X vehicle-to-everything
  • mapping of standard S-NSSAI to another standard S-NSSAI or mapping of unique S-NSSAI to standard S-NSSAI
  • mapping of unique S-NSSAI to standard S-NSSAI Alternatively, a mapping of standard S-NSSAI to a unique S-NSSAI, or a mapping of a unique S-NSSAI to another unique S-NSSAI.
  • the first policy control function network element maps, according to the first mapping relationship, the first network slice identifier information in the first user policy that is added to the fourth rule to the second network slice identifier information, to generate a second user policy.
  • Steps S305 and S306 will be described in detail below for the mapping scenarios of the above four modes.
  • Both the first S-NSSAI and the second S-NSSAI are standard S-NSSAI.
  • the NSSF network element generates a mapping relationship between the first S-NSSAI and the second S-NSSAI.
  • the first mapping relationship can be as shown in Table 8.
  • the first S-NSSAI is the eMBB in the HPLMN
  • the second S-NSSAI is the MIoT in the VPLMN
  • the first mapping relationship is that the eMBB corresponds to the MIoT.
  • the network slice type corresponding to the APP in the first URSP is the first S-NSSAI. Because the load of the network slice corresponding to the first S-NSSAI in the VPLMN is too large, in order to implement load balancing, the NSSF network element maps the first S-NSSAI to the second S-NSSAI, so that the user equipment establishes a session through the network slice corresponding to the second S-NSSAI.
  • the user equipment carries the S-NSSAI that identifies the eMBB slice type to request to establish a session, but the network slice load of the eMBB type is too large in the VPLMN, so the NSSF network element maps the eMBB identifier to the MIoT identifier.
  • the first mapping relationship is: the S-NSSAI of the eMBB slice type corresponds to the S-NSSAI of the MioT slice type, when the user equipment initiates the APP.
  • the specific manner in which the first policy control function network element performs step S306 to generate the second URSP is as follows:
  • the first URSP after adding the fourth rule is as shown in Table 9.
  • the DNN corresponding to the network slice identified as eMBB is DNN 1, where DNN 1 is the identity of DN 1, and DN 1 supports APP 1 and APP 2.
  • the first rule is used to indicate the association between the eMBB, the APP 1 and the DNN 1
  • the fourth rule is used to indicate the association between the eMBB, the APP 2 and the DNN 1.
  • the eMBB in the HPLMN corresponds to the MIOT in the VPLMN, so the first S-NSSAI (for example, eMBB) can be mapped to the second S-NSSAI (for example, MIoT), thereby generating the first Two URSP.
  • the generated second URSP can be as shown in Table 10.
  • the second URSP includes a second rule and a third rule, wherein the second rule is for indicating a second S-NSSAI (eg, MIoT), a first application (eg, APP 1), and a first DNN ( For example, DNN 1) association between the three, the third rule is used to indicate the association between the second S-NSSAI (eg MIoT), the second application (eg APP 2) and the first DNN (eg DNN 1) .
  • the second rule is for indicating a second S-NSSAI (eg, MIoT), a first application (eg, APP 1), and a first DNN ( For example, DNN 1) association between the three
  • the third rule is used to indicate the association between the second S-NSSAI (eg MIoT), the second application (eg APP 2) and the first DNN (eg DNN 1) .
  • the NSSF network element When the first S-NSSAI is the HP-NSN-specific S-NSSAI and the second S-NSSAI is the standard S-NSSAI, the NSSF network element generates the first S-NSSAI and the standard S- according to the roaming agreement between the VPLMN and the HPLMN.
  • the first mapping relationship can be as shown in Table 11.
  • the first S-NSSAI is the S-NSSAI 1 in the HPLMN
  • the second S-NSSAI is the URLLC in the VPLMN.
  • the first mapping relationship is that the S-NSSAI 1 corresponds to the URLLC.
  • the specific manner in which the first policy control function network element performs the step S306 to generate the second URSP is as follows:
  • the first URSP after adding the fourth rule is as shown in Table 2.
  • the DNN corresponding to the network slice identified as S-NSSAI 1 is DNN 1, where DNN 1 is the identity of DN 1, and DN 1 supports APP 1 and APP 2.
  • the S-NSSAI 1 in the HPLMN corresponds to the URLLC in the VPLMN, so the first S-NSSAI (for example, S-NSSAI 1) can be mapped to the second S-NSSAI (for example, URLLC) to generate a second URSP.
  • the generated second URSP can be as shown in Table 12.
  • the second URSP includes a second rule and a third rule, wherein the second rule is for indicating a second S-NSSAI (eg, URLLC), a first application (eg, APP 1), and a first DNN ( For example, DNN 1) association between the three, the third rule is used to indicate the association between the second S-NSSAI (eg URLLC), the second application (eg APP 2) and the first DNN (eg DNN 1) .
  • the second rule is for indicating a second S-NSSAI (eg, URLLC), a first application (eg, APP 1), and a first DNN ( For example, DNN 1) association between the three
  • the third rule is used to indicate the association between the second S-NSSAI (eg URLLC), the second application (eg APP 2) and the first DNN (eg DNN 1) .
  • the third type is the third type.
  • the NSSF network element is based on the VPLMN and The roaming agreement between the HPLMNs generates a first mapping relationship between the first S-NSSAI and the V-VPMN-specific S-NSSAI.
  • the second S-NSSAI is a S-NSSAI unique to VPLMN.
  • the first mapping relationship can be as shown in Table 13.
  • the first S-NSSAI is eMBB (standard S-NSSAI) in the HPLMN
  • the second S-NSSAI is S-NSSAI A in the VPLMN
  • the first mapping relationship is that eMBB corresponds to S-NSSAI A.
  • the specific manner in which the first policy control function network element performs step S306 to generate the second URSP is as follows:
  • the first S-NSSAI is a standard S-NSSAI
  • the first S-NSSAI is assumed to be eMBB
  • the first URSP after the fourth rule is added as shown in Table 9.
  • the identifier is eMBB.
  • the corresponding DNN of the network slice is DNN 1, where DNN 1 is the identifier of DN 1, and DN 1 supports APP 1 and APP 2.
  • the first rule is used to indicate the association between the eMBB, the APP 1 and the DNN 1
  • the fourth rule is used to indicate the association between the eMBB, the APP 2 and the DNN 1.
  • the eMBB in the HPLMN corresponds to the S-NSSAI A in the VPLMN, so the first S-NSSAI (for example, eMBB) can be mapped to the second S-NSSAI (for example, S-NSSAI). A), thereby generating a second URSP.
  • the generated second URSP can be as shown in Table 14.
  • the second URSP includes a second rule and a third rule, wherein the second rule is used to indicate the second S-NSSAI (eg, S-NSSAI A), the first application (eg, APP 1), and the An association between three DNNs (eg, DNN 1) for indicating a second S-NSSAI (eg, S-NSSAI A), a second application (eg, APP 2), and a first DNN (eg, DNN 1) The connection between the three.
  • the second rule is used to indicate the second S-NSSAI (eg, S-NSSAI A), the first application (eg, APP 1)
  • An association between three DNNs eg, DNN 1 for indicating a second S-NSSAI (eg, S-NSSAI A), a second application (eg, APP 2), and a first DNN (eg, DNN 1) The connection between the three.
  • the NSSF network element When the first S-NSSAI is the S-NSSAI unique to the HPLMN, and the network slice identified by the above-mentioned HPLMN-specific S-NSSAI is not deployed in the VPLMN, the NSSF network element generates the first S- according to the roaming agreement between the VPLMN and the HPLMN.
  • the second S-NSSAI is a S-NSSAI unique to VPLMN.
  • the first mapping relationship can be as shown in Table 15.
  • the first S-NSSAI is S-NSSAI 1 (HPLMN-specific S-NSSAI) in the HPLMN
  • the second S-NSSAI is S-NSSAI A in the VPLMN
  • the first mapping relationship is S-NSSAI 1 For S-NSSAI A.
  • the specific manner in which the first policy control function network element performs step S306 to generate the second URSP is as follows:
  • the first S-NSSAI is the S-NSSAI specific to the HPLMN
  • the first S-NSSAI is the S-NSSAI 1 in the HPLMN
  • the first URSP after the fourth rule is added is shown in Table 2.
  • the DNN corresponding to the network slice identified as S-NSSAI 1 is DNN 1, where DNN 1 is the identity of DN 1, and DN 1 supports APP 1 and APP 2.
  • the S-NSSAI 1 in the HPLMN corresponds to the S-NSSAI A in the VPLMN, so the first S-NSSAI (for example, S-NSSAI 1) can be mapped to the second S-NSSAI. (eg, S-NSSAI A) to generate a second URSP.
  • the generated second URSP can be as shown in Table 14. Therefore, for any one of the foregoing four mapping modes, the first policy control function network element may determine the second URSP according to the first mapping relationship and the first URSP after adding the fourth rule.
  • the second URSP includes an APP that does not exist in the first URSP in the HPLMN, but can be used in the LBO scenario of the VPLMN. Therefore, the user equipment can use more APPs in the LBO scenario of the VPLMN according to the second URSP obtained in the solution, thereby improving the user experience.
  • the first policy control function network element may further receive the third S-NSSAI and the fourth S from the access and mobility management function network element of the VPLMN.
  • the mapping of the third S-NSSAI to the fourth S-NSSAI may refer to the mapping of the first S-NSSAI to the second S-NSSAI, and details are not described herein again.
  • FIG. 4 is a flowchart of still another method for obtaining a user policy according to an embodiment of the present application.
  • Figure 4 will be described in conjunction with Figures 2 and 3.
  • Steps S401 to S404 may refer to S201 to S204 in FIG. 2 or S301 to S304 in FIG. 3, and details are not described herein again.
  • Step S405 can refer to the description of S205 in FIG.
  • the second URSP is the first URSP after joining the fourth rule.
  • step S405 can refer to the description of steps S305 and S306 in FIG. 3, and details are not described herein again.
  • the method may further include:
  • the first policy control function network element sends the identifiers of the second URSP and the VPLMN to the user equipment.
  • the user equipment receives the identifiers of the second URSP and the VPLMN from the first policy control function network element.
  • the identifier of the VPLMN is associated with the second URSP.
  • the second URSP can be learned according to the identifier of the VPLMN, thereby preventing the user equipment from requesting to obtain the second URSP again, and the interaction between the user equipment and the network can be reduced, thereby reducing the time. Delay, improve efficiency.
  • the first policy control function network element further sends the identifiers of the first URSP and the HPLMN to the user equipment.
  • the user equipment receives the identifiers of the first URSP and the HPLMN from the first policy control function network element.
  • the identifier of the HPLMN is associated with the first URSP.
  • the user equipment can obtain the identifiers of the first URSP and the HPLMN. Therefore, when the user equipment moves from the other area to the HPLMN and starts the APP, the first URSP can be learned according to the identifier of the HPLMN, thereby preventing the user equipment from requesting to acquire the first URSP, and the interaction between the user equipment and the network can be reduced, thereby reducing The delay reduces latency and improves efficiency.
  • the identifiers of the first URSP and the HPLMN, and the identifiers of the second URSP and the VPLMN may be sent to the user equipment through the same message, or may be sent to the user equipment through different messages, which is not limited herein.
  • the first policy control function network element may perform step S406. It should be noted that the present application does not limit the sequence between step S406 and step S401. That is to say, step S401 may be performed after step S406 is performed first, or step S406 may be performed after step S401 is performed first, or steps S401 and S406 may be performed at the same time.
  • the second policy control function network element sends the indication information to the first policy control function network element.
  • the first policy control function network element receives the indication information from the second policy control function network element.
  • the indication information is used to trigger the sending of the identifiers of the first URSP and the HPLMN to the user equipment.
  • the indication information may be a flag, which is not limited in this embodiment.
  • the second policy control function network element determines that there is no context information of the user equipment in the second policy control function network element, indicating that the user The device has not been registered in the HPLMN, and thus the user device has not obtained the first URSP from the second policy control function network element.
  • the second policy control function network element may send the indication information to the first policy control function network element, and may trigger the first policy control function network element to send the identifiers of the first URSP and the HPLMN to the user equipment.
  • the first policy control function network element can learn the scenario in which the first URSP is not in the user equipment.
  • the indication information triggers the first policy control function network element to send the first URSP to the user equipment.
  • the identity of the HPLMN Therefore, the first policy control function network element can learn the scenario in which the user equipment does not have the first user policy.
  • the indication information triggers the first policy control function network element to send the first user policy and the HPLMN to the user equipment. Logo. Therefore, the user equipment is repeatedly obtained from the first user policy, and the interaction between the user equipment and the network is reduced, thereby reducing the delay.
  • FIG. 5 is a signaling interaction diagram of another method for obtaining a URSP according to an embodiment of the present disclosure.
  • the method can be used to obtain the URSP scenario of the VPLMN from the policy control function network element of the VPLMN when the user equipment registers in the VPLMN.
  • the user equipment in FIG. 5 is the UE 101 in FIG. 1
  • the RAN device is the RAN device 102 in FIG. 1
  • the first AMF network element and the second AMF network element are the AMF network element 103 in FIG.
  • the element is the NSSF network element 104 in FIG. 1
  • the first PCF network element is the PCF network element 105 of the VPLMN in FIG.
  • the method may include:
  • NSSAI network slicing selection assistance information
  • the user equipment sends the requested network slicing selection assistance information (NSSAI) to the RAN device.
  • the RAN device receives the requested NSSAI from the user equipment.
  • NSSAI is a collection of S-NSSAI, that is, NSSAI includes one or more S-NSSAI.
  • the user equipment selects a network slice according to the requested NSSAI when initially entering the network.
  • step S501 may be performed.
  • the NSSAI of the above request may be an NSSAI configured before the user equipment interacts with the VPLMN.
  • the user equipment may also send a subscriber permanent identifier (SUPI) of the user equipment and a radio access network type requesting access to the RAN device.
  • SUPI subscriber permanent identifier
  • the RAN device determines the first AMF network element in the VPLMN according to the requested NSSAI.
  • the first AMF network element that is determined is the initial AMF network element.
  • the RAN device selects the first AMF network element according to the SUPI and the requested NSSAI and the radio access network type. If the RAN device cannot select the AMF network element that meets the requirements, the default AMF network element is determined according to the local policy information. An AMF network element.
  • the RAN device sends the requested NSSAI to the first AMF network element.
  • the first AMF network element receives the requested NSSAI from the RAN device.
  • the RAN device can also send a SUPI to the first AMF network element.
  • the first AMF network element obtains the first subscription data from the UDM network element of the HPLMN.
  • the first AMF network element may obtain the first subscription data from the UDM network element of the HPLMN by sending a request message or by calling a service.
  • the first AMF network element sends a request message including the SUPI to the UDM network element, or the first AMF network element requests to acquire the first subscription data by calling the Nudm_SubscriberDataManagement_Get service, and the UDM network element returns the first subscription by calling the Nudm_SubscriberDataManagement_Get response service. data.
  • the first subscription data includes the association of the contracted S-NSSAI with the DNN.
  • the association between the contracted S-NSSAI and the DNN is shown in Table 16.
  • the contracted S-NSSAIs include S-NSSAI 1 and S-NSSAI 2, where S-NSSAI 1 corresponds to DNN 1, and S-NSSAI 2 corresponds to DNN 2 and DNN 3.
  • the method for the user equipment to acquire the URSP may be further described in conjunction with FIG. 6.
  • the first AMF network element If the first AMF network element does not support the network slice corresponding to the NSSAI requested by the user equipment, the first AMF network element performs step S505 after step S504.
  • the first AMF network element acquires a mapping relationship from the NSSF network element of the VPLMN.
  • the request for the first AMF network element to obtain the mapping relationship from the NSSF network element of the VPLMN may be a method of sending a request message or a method of calling a service.
  • the first AMF network element requests the acquisition of the mapping relationship by calling the Slice Selection request service, and the UDM network element returns the mapping relationship by calling the Slice Selection response service.
  • the mapping relationship includes the first mapping relationship.
  • the first mapping relationship may refer to the description of step S305 in FIG. 3, and details are not described herein again.
  • the above mapping relationship may further include a second mapping relationship.
  • the first AMF network element requests the NSSF network element to obtain the mapping relationship by sending the requested NSSAI, the subscribed NSSAI, and the PLMN identity in the SUPI to the NSSF network element of the VPLMN.
  • the NSSF network element learns that the user equipment is a roaming user according to the PLMN identity in the SUPI, and determines the target AMF set and the first allowed NSSAI.
  • the target AMF set refers to one or more AMFs that meet the requirements of the user equipment, and the S-NSSAI included in the first allowed NSSAI is the S-NSSAI of the network slice that the user equipment can use in the VPLMN.
  • the NSSF network element also generates the above mapping relationship according to the roaming protocol between the VPLMN and the HPLMN.
  • the mapping relationship is a mapping relationship between the S-NSSAI in the HPLMN and the S-NSSAI in the VPLMN.
  • the first AMF network element is also used to request the NSSF network element to select an AMF network element that satisfies the NSSAI requested by the user equipment by calling the Slice Selection request service.
  • the first AMF network element sends redirection information to the second AMF network element.
  • the second MF network element receives the redirection information from the first AMF network element.
  • the second AMF network element is an AMF network element selected by the first AMF network element from the target AMF set in the second response information.
  • the redirection information includes the first allowed NSSAI.
  • the redirect message further includes the mapping relationship obtained in the foregoing step S505.
  • the redirect information further includes the requested NSSAI and the contracted S-NSSAI.
  • the second AMF network element determines the first temporarily rejected S-NSSAI.
  • the first temporarily rejected S-NSSAI refers to the S-NSSAI included in the requested NSSAI and belongs to the contracted S-NSSAI, but there is no network slice deployed in the current registration area. That is, the first temporarily rejected S-NSSAI is included in the contracted S-NSSAI, but is not included in the first allowed NSSAI.
  • the relationship between the requested NSSAI, the contracted S-NSSAIs, the first allowed NSSAI, and the first temporarily rejected S-NSSAI may be as shown in Table 17.
  • the NSSAI requested by the user equipment includes S-NSSAI 1, S-NSSAI 2, S-NSSAI 3, and S-NSSAI 4.
  • the S-NSSAIs subscribed by the user equipment include S-NSSAI 1, S-NSSAI 2, S. -NSSAI 3, the first allowed S-NSSAIs include S-NSSAI 1 and S-NSSAI 2, and the first temporarily rejected NSSAI includes S-NSSAI 3.
  • S-NSSAI 4 is an S-NSSAI that is not allowed to sign up.
  • the first temporarily rejected S-NSSAI is the S-NSSAI in the signed S-NSSAI except the first allowed S-NSSAI.
  • the S-NSSAI that is not allowed to sign up is the S-NSSAI other than the contracted S-NSSAI in the requested NSSAI.
  • NSSAI 1 Requested NSSAI S-NSSAI 1, S-NSSAI 2, S-NSSAI 3, S-NSSAI 4 Signed S-NSSAIs S-NSSAI 1, S-NSSAI 2, S-NSSAI 3 First allowed NSSAI S-NSSAI 1, S-NSSAI 2 The first temporary rejection of S-NSSAI S-NSSAI 3
  • the second AMF network element requests the first PCF network element to generate a second URSP.
  • the first PCF network element is a PCF network element selected by the second AMF network element in the VPLMN.
  • the second AMF network element may also request the first PCF network element to generate the second URSP in the VPLMN by calling the Npcf_AMPolicyControl_Get service.
  • the second AMF network element may further send the mapping relationship to the first PCF network element, and the first PCF network element receives the mapping relationship from the second AMF network element.
  • the second AMF network element sends the first allowed NSSAI to the first PCF network element, or the first allowed NSSAI and the first temporarily rejected S-NSSAI.
  • the second AMF network element may further send the first subscription data to the first PCF network element.
  • the first PCF network element acquires the first URSP from the second PCF network element.
  • the request for the first PCF network element to obtain the first URSP from the second PCF network element may be by sending a request message or by calling a service.
  • the first PCF network element obtains the first URSP by calling the Npcf_AMPolicyControl_Get (SUPI) service request
  • the second PCF network element returns the first URSP by calling the Npcf_AMPolicyControl_Response service.
  • the first URSP includes a first rule.
  • the first rule is used to indicate an association between the first S-NSSAI, the first application, and the first DNN
  • the first DNN is used to identify the first DN
  • the first DN allows the LBO and supports the first application and the second application. .
  • the second PCF network element sends the first subscription data to the first PCF network element.
  • the first PCF network element receives the first subscription data from the second PCF network element.
  • the first PCF network element may send the first subscription data and the first URSP by using the same message, or may be sent by using different messages.
  • the first PCF can obtain the subscription data from the second PCF network element by the optional step in the above S509.
  • the first PCF can also obtain the subscription data from the second AMF through step S508.
  • the first PCF may obtain the subscription data in any of the foregoing manners, or the first PCF may obtain the subscription data in other manners, which is not limited in this embodiment.
  • the first PCF network element determines that the first DN allows LBO.
  • the first PCF network element determines that the first DN supports the second application.
  • the first PCF network element adds the fourth rule to the first URSP, where the fourth rule includes an association between the first S-NSSAI, the second application, and the first DNN.
  • the first PCF network element determines the second URSP according to the first URSP after adding the fourth rule.
  • the first PCF network element sends a second URSP to the second AMF network element.
  • the second AMF network element receives the second URSP from the first PCF network element.
  • the second URSP includes a second rule and a third rule, where the second rule is used to indicate an association between the second S-NSSAI, the first application, and the first DNN, and the third rule is used to indicate the second S- The association between the NSSAI, the second application, and the first DNN.
  • the second S-NSSAI is the same as or corresponds to the first S-NSSAI.
  • the first PCF network element may send the second URSP to the second AMF network element by sending a message or by calling a service.
  • the first PCF network element sends a second URSP by calling the Npcf_AMPolicyControl_Response service.
  • the first PCF network element may further send the identifier of the VPLMN to the second AMF network element, where the identifier of the VPLMN is associated with the second URSP.
  • the first PCF network element may further send the identifiers of the first URSP and the HPLMN to the second AMF network element, where the identifier of the HPLMN is associated with the first URSP.
  • the first PCF network element may perform step S514.
  • the second PCF network element sends the indication information to the first PCF network element.
  • the first PCF network element receives the indication information from the second PCF network element.
  • the indication information is used to trigger the transmission of the identification of the first URSP and the HPLMN to the user equipment.
  • steps S510 to S512 can refer to the description of S203 to S205 in FIG. 2; the above step S513 can refer to the description of S205 in FIG. 2 or S306 in FIG. 3; the above step S514 can refer to the description in S406 in FIG. Therefore, steps S510 to S514 will not be described here.
  • the first PCF network element sends a second URSP to the second AMF network element.
  • the second AMF network element sends the first allowed NSSAI and the second URSP to the user equipment.
  • the user equipment receives the first allowed NSSAI and the second URSP from the second AMF network element.
  • the first allowed NSSAI and the second URSP may be transmitted by a Registration_Accepet message.
  • the user equipment saves the first allowed NSSAI and the second URSP.
  • the S-NSSAI carrying the network slice corresponding to the APP in the second URSP initiates a session establishment process to the network side when the APP is started in the VPLMN.
  • the user equipment may obtain the second URSP of the VPLMN according to the method of the embodiment of the present invention.
  • the second URSP also includes an APP that is not present in the first URSP of the HPLMN, but can be used in the LBO scenario of the VPLMN.
  • the user equipment can use more APPs in the LBO scenario of the VPLMN according to the second URSP obtained in the solution, thereby improving the user experience.
  • the user equipment can obtain the second URSP in the registration process, compared to the method in which the user equipment generates the second URSP according to the roaming protocol between the first URSP, the VPLMN and the HPLMN of the received HPLMN.
  • the user equipment does not need to perceive the roaming protocol on the network side, thereby enhancing the security of the network.
  • FIG. 6 is a signaling interaction diagram of another method for obtaining a URSP according to an embodiment of the present disclosure.
  • the applicable scenario of the method is the same as the embodiment shown in FIG.
  • the difference between the embodiment shown in FIG. 6 and FIG. 5 is that, in the embodiment of FIG. 5, the first AMF network element does not support the network slice corresponding to the NSSAI requested by the user equipment; and in the embodiment of FIG. 6, the first AMF network.
  • the element supports the network slice corresponding to the NSSAI requested by the user equipment.
  • Figure 6 will be described in conjunction with Figure 5.
  • Steps S601 to S604 may refer to descriptions of S501 to S504 in FIG. 5, and details are not described herein again.
  • the first AMF network element determines a mapping relationship.
  • the first AMF network element when HPLMN and VPLMN adopt different S-NSSAIs, the first AMF network element generates a mapping relationship according to a roaming protocol between the VPLMN and the HPLMN.
  • the mapping relationship is a mapping relationship between the S-NSSAI in the HPLMN and the S-NSSAI in the VPLMN.
  • the first AMF network element determines the first allowed NSSAI.
  • the S-NSSAI included in the first allowed NSSAI is the S-NSSAI of the network slice that the user equipment can use in the VPLMN.
  • the first AMF network element may perform an operation similar to the second AMF network element in FIG. 5 from step S607.
  • the first AMF network element may perform an operation similar to the second AMF network element in FIG. 5 from step S607.
  • the first AMF network element determines the first temporarily rejected S-NSSAI.
  • the first AMF network element determines the S-NSSAI of the first temporary refusal.
  • the second AMF network element determines the description of the first temporarily rejected S-NSSAI, and details are not described herein again. .
  • the first AMF network element sends a mapping relationship to the first PCF network element.
  • the first PCF network element receives the mapping relationship from the first AMF network element.
  • the first AMF network element sends a mapping relationship to the first PCF network element.
  • the second AMF network element sends a mapping relationship to the first PCF network element, and details are not described herein. .
  • Steps S609 to S614 may refer to the descriptions of S509 to S514 in FIG. 5, and details are not described herein again.
  • the first PCF network element sends a second URSP to the first AMF network element.
  • the first AMF network element receives the second URSP from the first PCF network element.
  • the first AMF network element sends the first allowed NSSAI and the second URSP to the user equipment.
  • the user equipment receives the first allowed NSSAI and the second URSP from the first AMF network element.
  • the first AMF network element sends the first allowed NSSAI and the second URSP to the user equipment.
  • the second AMF network element sends the first allowed NSSAI and the second URSP to the user equipment. The description is not repeated here.
  • Step S617 can refer to the description of S517 in FIG. 5, and details are not described herein again.
  • the user equipment may obtain the second URSP of the VPLMN according to the method of the embodiment of the present invention.
  • the second URSP also includes an APP that is not present in the first URSP of the HPLMN, but that can be used in the LBO scenario of the VPLMN.
  • the user equipment can use more APPs in the LBO scenario of the VPLMN according to the second URSP obtained in the solution, thereby improving the user experience.
  • the user equipment can obtain the second URSP in the registration process, compared to the method in which the user equipment generates the second URSP according to the roaming protocol between the first URSP, the VPLMN and the HPLMN of the received HPLMN.
  • the user equipment does not need to perceive the roaming protocol on the network side, thereby enhancing the security of the network.
  • FIG. 7 is a flowchart of still another method for obtaining a URSP according to an embodiment of the present application.
  • the method can be used when the user equipment acquires the URSP scenario of the VPLMN when the subscription information of the user equipment changes.
  • Figure 7 will be described in conjunction with Figure 5.
  • the UDM network element of the HPLMN sends the second subscription data to the second AMF network element.
  • the second AMF network element receives the second subscription data from the UDM network element.
  • the second subscription data is the subscription data after the first subscription data is updated.
  • the UDM network element of the HPLMN may send the second subscription data to the second AMF network element by sending a message or by calling a service.
  • the UDM network element sends the second subscription data by calling the Nudm_SubscriberData_Get response service.
  • the second AMF network element subscribes to the subscription data.
  • the UDM network element sends the second subscription data updated by the first subscription data to the second AMF network element.
  • the first subscription data is as shown in Table 16
  • the updated second subscription data is as shown in Table 18.
  • the second contracted S-NSSAIs include S-NSSAI 1, S-NSSAI 2, and S-NSSAI 3, where S-NSSAI 1 corresponds to DNN 1, S-NSSAI 2 corresponds to DNN 2 and DNN 3.
  • S-NSSAI 3 corresponds to DNN 4.
  • the second subscription data increases the association of S-NSSAI 3 with DNN 4 relative to the first subscription data in Table 16.
  • the second AMF network element acquires the second allowed NSSAI from the NSSF network element of the VPLMN.
  • the second allowed NSSAI is the updated allowed NSSAI.
  • steps S703 to S713 may refer to descriptions of steps S707 to S717 in FIG. 5, and details are not described herein again.
  • the second temporarily rejected S-NSSAI is the updated temporarily rejected S-NSSAI
  • the third URSP is the first URSP updated URSP
  • the fourth URSP is the second URSP updated URSP.
  • the first policy control function network element may generate a new one by using the first URSP updated third URSP and the updated first mapping relationship.
  • the second URSP, the fourth URSP is sent to the user equipment.
  • the user equipment can obtain the fourth URSP after the subscription information is updated, and obtain the information of the APP that can be used locally after the update according to the fourth URSP, thereby improving the user experience.
  • the rule for indicating the association between the network slice identification information, the application, and the data network identification information may be identified by a network slice.
  • the correspondence between the information, the application, and the data network identification information is implemented, or a combination of any two of the three relationships may be adopted (for example, the correspondence between the network slice identification information and the application, and, This is achieved by the relationship between the application and the data network name.
  • This application is not limited here.
  • each solution of the communication method provided by the embodiment of the present application is introduced from the perspective of the interaction between the network elements and the network elements.
  • each network element for example, the first PCF network element, the second PCF network element and the AMF network element, in order to implement the above functions, includes hardware structures and/or software modules corresponding to the respective functions.
  • the present application can be implemented in a combination of hardware or hardware and computer software in combination with the elements and algorithm steps of the various examples described in the embodiments disclosed herein. Whether a function is implemented in hardware or computer software to drive hardware depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods to implement the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present application.
  • the means for obtaining the user policy may include a receiving module 801 and a transmitting module 803, as shown in FIG. 8A.
  • the device for obtaining a user policy further includes a processing module 802.
  • the device for acquiring a user policy may be used to perform operations of the first policy control function network element (eg, the first PCF network element) in FIG. 2 to FIG. 7 above.
  • the first policy control function network element eg, the first PCF network element
  • the receiving module 801 is configured to receive a first user policy for the HPLMN from a policy control function network element for the HPLMN.
  • the first user policy includes a first rule, where the first rule is used to indicate an association between the first network slice identifier information, the first application, and the first data network identifier information, where the first data network identifier information is used to identify The first data network, the first data network allows the LBO and supports the first application and the second application.
  • the sending module 803 is configured to send a second user policy of the VPLMN to the user equipment.
  • the second user policy includes a second rule and a third rule, where the second rule is used to indicate association between the second network slice identification information, the first application, and the first data network identification information, where the third rule is used. An association between the second network slice identification information, the second application, and the first data network identification information is indicated.
  • the device that obtains the user policy in the embodiment of the present invention includes the information of the APP that can be used in the LPU scenario of the VPLMN, in the second URSP of the VPLMN obtained by the user equipment, but not in the first URSP of the HPLMN.
  • the information of the second application described above The user equipment can use more APP services in the LBO scenario of the VPLMN according to the obtained second URSP, thereby improving the user experience.
  • the sending module 803 is further configured to send an identifier of the VPLMN to the user equipment, where the identifier of the VPLMN is associated with the second user policy.
  • the sending module 803 is further configured to send, to the user equipment, the identifier of the first user policy and the HPLMN, where the identifier of the HPLMN is associated with the first user policy.
  • the receiving module 801 is further configured to receive indication information from the policy control function network element, where the indication information is used to trigger the first user policy and the HPLMN. Identifies the transmission to the user device.
  • the processing module 802 for acquiring the user policy is configured to add the fourth rule to the first user policy.
  • the fourth rule includes an association between the first network slice identifier information, the second application, and the first data network identifier information, and the processing module is further configured to determine the second user according to the first user policy after joining the fourth rule. Strategy.
  • processing module 802 is further configured to determine that the first data network allows the LBO, and determine that the first data network supports the second application.
  • the second user policy is the first user policy after the fourth rule is added.
  • the receiving module 801 is configured to receive, by the access and mobility management function network element of the VPLMN, the first network slice identifier information and the second network.
  • the first mapping relationship between the slice identification information; the processing module 802 is configured to determine the second user policy according to the first mapping relationship and the first user policy after joining the fourth rule.
  • the processing module 802 is configured to map, by using the first mapping relationship, the first network slice identifier information in the first user policy that is added to the fourth rule to the second network slice identifier information, to generate a second user policy.
  • the receiving module 801 is further configured to receive, by the access and mobility management function network element of the VPLMN, a first mapping relationship between the first network slice identifier information and the second network slice identifier information, where the first mapping relationship is used. Generation of a second user policy.
  • the first user policy further includes a fifth rule, where the fifth rule is used to indicate association between the third network slice identifier information, the third application, and the second data network identifier information, where the second data network identifier information is used. Identifying a second data network, the second data network disabling the LBO; the second user policy further includes a sixth rule, where the sixth rule is used to indicate the association between the fourth network slice identification information, the third application, and the second data network identification information The fourth network slice identification information is the same as the third network slice identification information.
  • the first user policy further includes a fifth rule, where the fifth rule is used to indicate association between the third network slice identifier information, the third application, and the second data network identifier information, where the second data network identifier information is used. Identifying a second data network, the second data network disabling the LBO; the second user policy further includes a sixth rule, where the sixth rule is used to indicate the association between the fourth network slice identification information, the third application, and the second data network identification information The fourth network slice identification information corresponds to the third network slice identification information.
  • the receiving module 801 is further configured to receive, by the access and mobility management function network element of the VPLMN, a second mapping relationship between the third network slice identifier information and the fourth network slice identifier information; the processing module 802 is further configured to: And determining fourth network slice identification information according to the third network slice identification information and the second mapping relationship.
  • the receiving module 801, the processing module 802, and the sending module 803 in the device for acquiring the user policy may further implement other operations or functions of the first policy control function network element in the foregoing method, and details are not described herein again.
  • the apparatus for acquiring a user policy shown in FIG. 8A is further configured to perform the operations of the second policy control function network element (eg, the second PCF network element) in FIG. 4 above.
  • the second policy control function network element eg, the second PCF network element
  • the sending module 803 is configured to send the user policy of the HPLMN to the first policy control function network element of the VPLMN, and is further configured to send the indication information to the first policy control function network element.
  • the indication information is used to trigger the sending module 803 to send the user policy of the HPLMN and the identifier of the HPLMN to the user equipment.
  • the identity of the HPLMN described above is associated with the user policy of the HPLMN.
  • the first policy control function network element of the VPLMN can receive the user policy of the HPLMN, thereby generating a user policy of the VPLMN according to the user policy of the HPLMN.
  • the user policy of the VPLMN includes the information of the APP that is not present in the user policy of the HPLMN but can be used in the LBO scenario of the VPLMN.
  • the user equipment can use more APP services in the LBO scenario of the VPLMN according to the obtained second user policy, thereby improving the user experience.
  • the policy control function network element of the VPLMN sends the user policy and the identifier of the HPLMN to the user equipment after receiving the triggering of the indication information, thereby avoiding the user equipment repeatedly acquiring the user policy of the HPLMN, thereby reducing the interaction between the user equipment and the network, thereby Reduced latency.
  • the receiving module 801, the processing module 802, and the sending module 803 in the device for acquiring the user policy may further implement other operations or functions of the second policy control function network element in the foregoing method, and details are not described herein again.
  • the apparatus for acquiring a user policy shown in FIG. 8A can also be used to perform the operations of the access and mobility management function network element (eg, AMF network element) in FIG. 3 above.
  • the access and mobility management function network element eg, AMF network element
  • the sending module 803 is configured to send, to the first policy control function network element, a mapping relationship between the first network slice identifier information and the second network slice identifier information.
  • the first network slice identifier information is the network slice identifier information in the HPLMN supported by the data network
  • the second network slice identifier information is the network slice identifier information in the VPLMN supported by the data network, where the mapping relationship is used for the second network slice identifier. Determination of information.
  • the user equipment needs to obtain the mapping relationship between the first network slice identifier information and the second network slice identifier information from the access and mobility management function network element of the VPLMN, and generate a second user policy.
  • the user equipment perceives the roaming agreement between the VPLMN and the HPLMN through the above mapping relationship.
  • the user equipment acquires the second user policy from the network side, so that the roaming agreement between the VPLMN and the HPLMN is not required to be perceived, thereby improving the security performance of the network.
  • the receiving module 801, the processing module 802, and the sending module 803 in the user policy can also implement other operations or functions of the access and mobility management function network element in the foregoing method, and details are not described herein.
  • FIG. 8B is a schematic diagram showing another possible structure of the apparatus for acquiring a user policy involved in the foregoing embodiment.
  • the means for obtaining the user policy includes a transceiver 804 and a processor 805, as shown in Figure 8B.
  • the processor 805 can be a general purpose microprocessor, a data processing circuit, an application specific integrated circuit (ASIC), or a field-programmable gate arrays (FPGA) circuit.
  • the device for acquiring a user policy may further include a memory 806.
  • the memory is a random access memory (RAM).
  • the memory is for coupling with a processor 805 that holds the computer program 8061 necessary for the device that acquires the user policy.
  • the method for acquiring a user policy involved in the foregoing embodiment further provides a carrier 807, where the computer program 8071 of the device for acquiring the user policy is stored, and the computer program 8071 can be loaded into the processor 805.
  • the carrier may be an optical signal, an electrical signal, an electromagnetic signal, or a computer readable storage medium (eg, a hard disk).
  • the computer can be caused to perform the methods described above.
  • processor 805 is configured as other operations or functions of the first policy control function network element.
  • the transceiver 804 is configured to implement communication between the device for acquiring the user policy and the second policy control function network element/access and mobility management function network element/user equipment.
  • the processor 805 is configured as a second policy to control other operations or functions of the functional network element.
  • the transceiver 804 is configured to implement communication between the device that acquires the user policy and the policy control function network element of the VPLMN.
  • the processor 805 is configured to perform the corresponding function of the first NF network element in the above method by the communication device.
  • the transceiver 804 is configured to implement communication between the device that acquires the user policy and the first NRF network element.
  • the controller/processor for performing the above wireless access network device of the present application may be a central processing unit (CPU), a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), and a field programmable gate array. (FPGA) or other programmable logic device, transistor logic device, hardware component, or any combination thereof. It is possible to implement or carry out the various illustrative logical blocks, modules and circuits described in connection with the present disclosure.
  • the processor may also be a combination of computing functions, for example, including one or more microprocessor combinations, a combination of a DSP and a microprocessor, and the like.
  • the steps of a method or algorithm described in connection with the present disclosure may be implemented in a hardware or may be implemented by a processor executing software instructions.
  • the software instructions may be comprised of corresponding software modules that may be stored in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable hard disk, CD-ROM, or any other form of storage well known in the art.
  • An exemplary storage medium is coupled to the processor to enable the processor to read information from, and write information to, the storage medium.
  • the storage medium can also be an integral part of the processor.
  • the processor and the storage medium can be located in an ASIC. Additionally, the ASIC can be located in a wireless access network device.
  • the processor and the storage medium can also exist as discrete components in the radio access network device.
  • the above embodiments it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • software it may be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions.
  • the computer program instructions When the computer program instructions are loaded and executed on a computer, the processes or functions described in accordance with embodiments of the present invention are generated in whole or in part.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • the computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be from a website site, computer, server or data center Transfer to another website site, computer, server, or data center by wire (eg, coaxial cable, fiber optic, digital subscriber line (DSL), or wireless (eg, infrared, wireless, microwave, etc.).
  • the computer readable storage medium can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or the like that includes one or more available media.
  • the usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (such as a solid state disk (SSD)).

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Computer Security & Cryptography (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本申请涉及无线通信技术领域，提供了一种获取URSP的方法，包括：VPLMN的第一PCF网元从HPLMN的第二PCF网元接收包括第一规则的HPLMN的第一URSP，向UE发送包括第二规则和第三规则的VPLMN的第二URSP。其中，第一规则用于指示第一S-NSSAI、第一应用和第一DNN三者之间的关联，第一DNN用于标识第一DN，第一DN允许LBO且支持第一应用和第二应用。第二规则用于指示第二S-NSSAI、第一应用和第一DNN三者之间的关联，第三规则用于指示第二S-NSSAI、第二应用和第一DNN三者之间的关联。通过本实施例提供的方案，UE获得的VPLMN的URSP相比于HPLMN的URSP，还包含了VPLMN中允许LBO的DN支持的其他应用，使UE在VPLMN中可以使用更多的应用，从而提高了用户体验。

Description

用户策略的获取
本申请要求于2017年12月13日提交中国国家知识产权局、申请号为201711330705.X、申请名称为“用户策略的获取”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本发明涉及通信技术领域，特别涉及一种获取用户策略的方法、装置及***。
背景技术
第五代(the 5th-Generation，5G)通信时代将有数以千亿计的物联网设备接入网络，不同类型应用场景对网络的需求是差异化的。网络切片技术通过在同一网络基础设施上虚拟独立逻辑网络的方式，为不同的应用场景提供相互隔离的网络环境，使得不同应用场景可以按照各自的需求定制网络功能和特性，从而保障不同业务的需求。在5G通信时代，用户设备上具有多种应用程序(Application，APP)，由于不同的APP对时延和带宽的需求不同，所以用户在启动不同APP时所需要的网络切片类型也不同。不同的网络切片类型可以通过网络切片标识信息进行标识，例如，网络切片标识信息为单网络切片选择辅助信息(Single Network Slice Selection Assistance Information，S-NSSAI)。
目前，用户设备可以从5G核心网中获取用户路由选择策略(UE Route Selection Policy，URSP)，然后根据URSP决定如何将业务流路由到已有的分组数据单元(Packet Data Unit，PDU)会话中，或者根据URSP触发新的PDU会话的建立。当用户设备在启动不同的APP并需要建立新的PDU会话时，由于URSP中的网络切片选择策略(Network Slice Selection Policy，NSSP)包括了不同APP对应的S-NSSAI，所以用户设备可以根据APP与S-NSSAI的对应关系，选择能够满足APP需求的网络切片并建立会话。
在现有技术中，用户设备中拜访的公用陆地移动网(Visited Public Land Mobile Network，VPLMN)的URSP，是根据归属公用陆地移动网(Home Public Land Mobile Network，HPLMN)的URSP和VPLMN中S-NSSAI与HPLMN中S-NSSAI的映射关系生成的。因此，用户设备根据VPLMN的URSP可能获取不到能够在VPLMN本地使用的APP的信息，进而用户设备在VPLMN中无法使用上述APP，从而降低了用户的业务体验。
例如，美国部署了为某应用(例如，脸书facebook)提供服务的服务器，而中国没有部署，所以用户设备在中国是无法访问该应用的服务器的，也就无法使用该应用。当***用户漫游到美国的运营商(例如，沃达丰)服务的区域时，该***用户获取到的美国的URSP中没有该应用的信息，所以用户在美国也无法使用该应用，从而造成了用户体验降低。
发明内容
本发明实施例提供了一种获取用户策略的方法、装置及***。
一方面，本申请的实施例提供了一种获取用户策略的方法，该方法包括：
VPLMN的第一策略控制功能网元(例如，第一PCF网元)从HPLMN的第二策略控制功能网元(例如，第二PCF网元)接收HPLMN的第一用户策略(例如，第一URSP)。其中，第一用户策略包括第一规则，第一规则用于指示第一网络切片标识信息(例如，第一S-NSSAI)、第一应用和第一数据网络标识信息(例如，第一DNN)三者之间的关联，第一数据网络标识信息用于标识第一数据网络(例如，第一DN)，第一数据网络允许LBO且支持第一应用和第二应用。第一策略控制功能网元向用户设备发送VPLMN的第二用户策略(例如，第二URSP)，第二用户策略包括第二规则和第三规则，第二规则用于指示第二网络切片标识信息(例如，第二S-NSSAI)、第一应用和第一数据网络标识信息三者之间的关联，第三规则用于指示第二网络切片标识信息、第二应用和第一数据网络标识信息三者之间的关联。
根据上述方法，用户设备获取的VPLMN的第二用户策略中包括了不存在于HPLMN的第一用户策略中，但是能够在VPLMN的LBO场景下使用的APP的信息，例如上述第二应用的信息。用户设备可以根据本方案中获得的第二用户策略在VPLMN的LBO场景下使用更多的APP业务，从而提高了用户体验。
在一种可能的设计中，第一策略控制功能网元还向用户设备发送VPLMN的标识。其中，VPLMN的标识与第二用户策略关联。由此，当用户设备从其他区域移动到VPLMN中时，能够根据VPLMN的标识获知第二用户策略，从而避免了用户设备再次请求获取第二用户策略，可以减少用户设备与网络的交互，从而降低了时延，提高了效率。
在一种可能的设计中，第一策略控制功能网元还向用户设备发送第一用户策略和HPLMN的标识。其中，HPLMN的标识与第一用户策略关联。由此，用户设备可以获得第一用户策略与HPLMN的标识。由此，当用户设备从其他区域移动到HPLMN中并启动APP时，能够根据HPLMN的标识获知第一URSP，从而避免了用户设备请求获取第一用户策略，可以减少用户设备与网络的交互，从而降低了时延，提高了效率。
在一种可能的设计中，第一策略控制功能网元在向用户设备发送第一用户策略和所述HPLMN的标识之前，从第二策略控制功能网元接收指示信息。指示信息用于触发第一用户策略和HPLMN的标识至用户设备的发送。由此，第一策略控制功能网元能够获知用户设备中没有第一用户策略的场景，在这种场景下，指示信息会触发第一策略控制功能网元向用户设备发送第一用户策略和HPLMN的标识。由此，避免了用户设备重复获取第一用户策略，可以减少用户设备与网络的交互，从而降低了时延。
在一种可能的设计中，该方法还包括：第一策略控制功能网元将第四规则加入第一用户策略。其中，第四规则包括第一网络切片标识信息、第二应用和第一数据网络标识信息三者之间的关联。第一策略控制功能网元根据加入第四规则后的第一用户策略确定第二用户策略。由此，第二用户策略中包括了不存在于HPLMN的第一用户策略中，但是能够在VPLMN的LBO场景下使用的APP的信息。
在一种可能的设计中，该方法还包括：第一策略控制功能网元确定第一数据网络允许LBO，并且确定第一数据网络支持第二应用。由此，第一策略控制功能网元可以获知允许LBO的第一数据网络，进而确定第一数据网络支持的第二应用。
在一种可能的设计中，当第二网络切片标识信息与第一网络切片标识信息相同时，第二用户策略为加入第四规则后的第一用户策略。由此，第一策略控制功能网元可以根据加入第四规则后的第一用户策略生成第二用户策略。
在一种可能的设计中，当第二网络切片标识信息与第一网络切片标识信息对应时，第一策略控制功能网元根据加入第四规则后的第一用户策略确定第二用户策略，包括：第一策略 控制功能网元从VPLMN的接入和移动性管理功能网元(例如，AMF网元)接收第一网络切片标识信息和第二网络切片标识信息之间的第一映射关系，并根据第一映射关系和加入第四规则后的第一用户策略确定第二用户策略。由此，第一策略控制功能网元可以根据加入第四规则后的第一用户策略，以及第一映射关系生成第二用户策略。
在一种可能的设计中，第一策略控制功能网元根据第一映射关系和加入第四规则后的第一用户策略确定第二用户策略，包括：第一策略控制功能网元根据第一映射关系，将加入第四规则后的第一用户策略中的第一网络切片标识信息映射为第二网络切片标识信息，以生成第二用户策略。由此，当第二网络切片标识信息与第一网络切片标识信息对应时，第一策略控制功能网元通过将第一网络切片标识信息映射为第二网络切片标识信息，从而可以生成第二用户策略。
在一种可能的设计中，该方法还包括：第一策略控制功能网元从VPLMN的接入和移动性管理功能网元接收第一网络切片标识信息和第二网络切片标识信息之间的第一映射关系，第一映射关系用于第二用户策略的生成。由此，当第二网络切片标识信息与第一网络切片标识信息对应时，第一策略控制功能网元根据获得的第一映射关系，可以实现HPLMN中网络切片标识信息到VPLMN中网络切片标识信息的映射，从而生成了第二用户策略。
在一种可能的设计中，第一用户策略还包括第五规则。其中，第五规则用于指示第三网络切片标识信息、第三应用和第二数据网络标识信息之间的关联，第二数据网络标识信息用于标识第二数据网络，第二数据网络禁止LBO。第二用户策略还包括第六规则，第六规则用于指示第四网络切片标识信息、第三应用和第二数据网络标识信息之间的关联。其中，第四网络切片标识信息与第三网络切片标识信息相同。
在一种可能的设计中，第一用户策略还包括第五规则。其中，第五规则用于指示第三网络切片标识信息、第三应用和第二数据网络标识信息之间的关联，第二数据网络标识信息用于标识第二数据网络，第二数据网络禁止LBO。第二用户策略还包括第六规则，第六规则用于指示第四网络切片标识信息、第三应用和第二数据网络标识信息之间的关联。其中，第四网络切片标识信息与第三网络切片标识信息对应。由此，第二用户策略中还包括了禁止LBO的数据网络所支持的应用，使用户设备在VPLMN中还可以使用不能在LBO场景下使用的应用。
在一种可能的设计中，该方法还包括：第一策略控制功能网元从VPLMN的接入和移动性管理功能网元接收第三网络切片标识信息和第四网络切片标识信息之间的第二映射关系；并且根据第三网络切片标识信息和第二映射关系确定第四网络切片标识信息。由此，当第二网络切片标识信息与第一网络切片标识信息对应时，第一策略控制功能网元根据获得的第二映射关系，可以实现HPLMN中网络切片标识信息到VPLMN中网络切片标识信息的映射，从而使生成的第二用户策略中还包括了禁止LBO的数据网络所支持的应用。
又一方面，本申请还公开了一种获取用户策略的方法，该方法包括：HPLMN的第二策略控制功能网元(例如，第二PCF网元)向VPLMN的第一策略控制功能网元(例如，第一PCF网元)发送HPLMN的用户策略(例如，URSP)。第二策略控制功能网元向第一策略控制功能网元发送指示信息。其中，指示信息用于触发用户策略和HPLMN的标识至用户设备的发送，HPLMN的标识与用户策略关联。
根据上述方法，VPLMN的第一策略控制功能网元可以接收到HPLMN的用户策略，从而根据该HPLMN的用户策略生成VPLMN的用户策略。其中，该VPLMN的用户策略中包括了不存在于HPLMN的用户策略中，但是能够在VPLMN的LBO场景下使用的APP的信息。用户设备可以根据获得的第二用户策略在VPLMN的LBO场景下使用更多的APP业务，从而提高了用户体验。 此外，VPLMN的第一策略控制功能网元接收到指示信息的触发后，将用户策略和HPLMN的标识发送到用户设备，避免了用户设备重复获取HPLMN的用户策略，可以减少用户设备与网络的交互，从而降低了时延。
又一方面，本申请还公开了一种获取用户策略的方法，该方法包括：VPLMN的接入和移动性管理功能网元(例如，AMF网元)向VPLMN的策略控制功能网元(例如，PCF网元)发送第一网络切片标识信息(例如，第一S-NSSAI)和第二网络切片标识信息(例如，第二S-NSSAI)之间的映射关系。其中，第一网络切片标识信息为数据网络(例如，DN)支持的HPLMN中的网络切片标识信息(例如，S-NSSAI)，第二网络切片标识信息为数据网络支持的VPLMN中的网络切片标识信息，映射关系用于第二网络切片标识信息的确定。
由于在现有技术中用户设备需要从VPLMN的接入和移动性管理功能网元获取上述第一网络切片标识信息和第二网络切片标识信息之间的映射关系，进而生成第二用户策略。根据现有技术，用户设备会通过上述映射关系感知到VPLMN与HPLMN之间的漫游协议。而根据本申请提出的上述方法，用户设备从网络侧获取第二用户策略，从而不需要感知VPLMN与HPLMN之间的漫游协议，由此提高了网络的安全性能。
又一方面，本申请实施例提供了一种获取用户策略的装置，该获取用户策略的装置具有实现上述方法中第一策略控制功能网元(例如，第一PCF网元)行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。在一个可能的设计中，上述获取用户策略的装置的结构中包括处理器和收发器，所述处理器被配置为处理该获取用户策略的装置执行上述方法中相应的功能。所述收发器用于实现上述获取用户策略的装置与第二策略控制功能网元/接入和移动性管理功能网元/用户设备之间的通信。所述获取用户策略的装置还可以包括存储器，所述存储器用于与处理器耦合，其保存该获取用户策略的装置必要的程序指令和数据。
又一方面，本申请实施例提供了一种获取用户策略的装置，该获取用户策略的装置具有实现上述方法中第二策略控制功能网元(例如，第二PCF网元)行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。在一个可能的设计中，获取用户策略的装置的结构中包括处理器和收发器，所述处理器被配置为获取用户策略的装置执行上述方法中相应的功能。所述收发器用于实现获取用户策略的装置和第一策略控制功能网元之间的通信。所述获取用户策略的装置还可以包括存储器，所述存储器用于与处理器耦合，其保存该获取用户策略的装置必要的程序指令和数据。
又一方面，本申请实施例提供了一种获取用户策略的装置，该获取用户策略的装置具有实现上述方法中接入和移动性管理功能网元(例如，AMF网元)行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。在一个可能的设计中，上述获取用户策略的装置的结构中包括处理器和收发器，所述处理器被配置为处理获取用户策略的装置执行上述方法中相应的功能。所述收发器用于实现获取用户策略的装置与VPLMN的策略控制功能网元之间的通信。所述获取用户策略的装置还可以包括存储器，所述存储器用于与处理器耦合，其保存该获取用户策略的装置必要的程序指令和数据。又一方面，本申请实施例提供了一种计算机可读存储介质，所述计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机执行上述各方面所述的方法。
又一方面，本申请实施例提供了一种包含指令的计算机程序产品，当其在计算机上运行 时，使得计算机执行上述各方面所述的方法。
又一方面，本申请提供了一种芯片***，该芯片***包括处理器，用于支持上述获取用户策略的装置实现上述方面中所涉及的功能，例如，生成或处理上述方法中所涉及的信息。在一种可能的设计中，所述芯片***还包括存储器，所述存储器，用于保存获取用户策略的装置必要的程序指令和数据。该芯片***，可以由芯片构成，也可以包含芯片和其他分立器件。
附图说明
为了更清楚地说明本发明实施例或背景技术中的技术方案，下面将对本发明实施例或背景技术中所需要使用的附图进行说明。
图1为根据本申请实施例提供的一种在本地路由(local break-out，LBO)场景下的5G漫游通信***示意图；
图2为根据本申请实施例提供的一种获取用户策略的方法的流程图；
图3为根据本申请实施例提供的又一种获取用户策略的方法的流程图；
图4为根据本申请实施例提供的又一种获取用户策略的方法的流程图；
图5为根据本申请实施例提供的又一种获取用户策略的方法的信令交互图；
图6为根据本申请实施例提供的又一种获取用户策略的方法的信令交互图；
图7为根据本申请实施例提供的又一种获取用户策略的方法的信令交互图；
图8A、8B为根据本申请实施例中提供的一种获取用户策略的装置的结构示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚地描述。本申请中，“多个”是指两个或两个以上。
图1示出了本申请实施例提供的一种在LBO场景下的5G漫游通信***示意图。在5G移动网络架构中，移动网关的控制面功能和转发面功能解耦，其分离出来的控制面功能与第三代合作伙伴计划(third generation partnership project，3GPP)传统的控制网元移动性管理实体(mobility management entity，MME)等合并成统一的控制面(control plane)。用户面功能(User plane function，UPF)网元能实现服务网关(serving gateway，SGW)和分组数据网络网关(packet data network gateway，PGW)的用户面功能(SGW-U和PGW-U)。进一步的，统一的控制面网元可以分解成接入和移动性管理功能(access and mobility management function，AMF)网元和会话管理功能(session management function，SMF)网元。
如图1所示，该通信***至少包括用户设备(User Equipment，UE)101、VPLMN中的各网络设备，以及HPLMN中的各网络设备。其中，VPLMN中的网络设备和HPLMN中的网络设备分别包括策略控制功能(policy control function，PCF)网元105和PCF网元107。
其中，本***中所涉及到的用户设备101不受限于5G网络，包括：手机、物联网设备、智能家居设备、工业控制设备、车辆设备等等。所述用户设备也可以称为终端设备(Terminal Equipment)、移动站(Mobile Station)、移动台(Mobile)、远程站(Remote Station)、远程终端(Remote Terminal)、接入终端(Access Terminal)、用户设备(User Terminal)、用户代理(User Agent)，在此不作限定。上述用户设备还可以车与车(Vehicle-to-vehicle，V2V)通信中的汽车、机器类通信中的机器等。
本***中所涉及到的PCF网元(例如，PCF网元105，PCF网元107)包含策略控制的功能。可选的，PCF网元还支持统一的策略架构来管理网络行为。可选的，PCF网元还可以访问与统一数据存储库中策略相关的订阅信息。PCF网元可也称为PCF实体或PCF设备。
可选的，VPLMN中的网络设备还包括无线接入网络(Radio Access Network，RAN)设备102和AMF网元103。其中，AMF网元103可负责终端设备的附着、移动性管理、跟踪区更新流程等。AMF网元也可称为AMF设备或AMF实体。
RAN设备102是一种用于为UE101提供无线通信功能的装置。所述RAN设备可以包括各种形式的基站，例如：宏基站，微基站(也称为小站)，中继站，接入点等。在采用不同的无线接入技术的***中，具备基站功能的设备的名称可能会有所不同，例如，在LTE***中，称为演进的节点B(evolved NodeB，eNB或者eNodeB),在第三代(3rd generation，3G)***中，称为节点B(Node B)等。在新一代***中，称为gNB(gNodeB)。
此外，VPLMN中的网络设备还包括VPLMN中的网络切片选择功能(Network Slice Selection Function，NSSF)网元104。NSSF网元104能为用户设备选择网络切片。所述NSSF网元也可称为NSSF设备或NSSF实体。
可选的，HPLMN中的网络设备还包括统一数据管理(Unified Data Management，UDM)网元106。UDM网元106能够存储用户的签约数据。例如，用户的签约数据包括移动性管理相关的签约数据以及会话管理相关的签约数据。所述UDM网元也可称为UDM设备或UPF实体。
在图1所示的LBO场景下的5G漫游通信***中，UE 101通过在VPLMN中进行注册，从而可以访问VPLMN的业务。UE 101在注册过程中，会通过RAN设备102选择一个初始的AMF设备103，初始的AMF设备103会向HPLMN的UDM网元106请求获取UE 101的签约数据。如果初始的AMF设备103不能为UE 101提供服务时，则初始的AMF设备103请求NSSF网元104选择能满足用户需求的另一AMF设备为用户提供服务。VPLMN中的PCF网元105可以向HPLMN中的PCF网元107请求获取HPLMN的URSP，然后生成VPLMN的URSP并发送给UE 101。当UE 101在VPLMN中发起APP的业务时，根据VPLMN的URSP建立会话。
上述各网元既可以是在专用硬件上实现的网络元件，也可以是在专用硬件上运行的软件实例，或者是在适当平台上虚拟化功能的实例，例如，上述虚拟化平台可以为云平台。
此外，本申请实施例还可以适用于面向未来的其他通信技术。本申请描述的网络架构以及业务场景是为了更加清楚的说明本申请的技术方案，并不构成对本申请提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请提供的技术方案对于类似的技术问题，同样适用。
下面以图1所示的在LBO场景下的5G漫游通信***为例，通过一些实施例对本申请的技术方案进行详细说明。下面这几个实施例可以相互结合，对于相同或相似的概念或过程可能在某些实施例不再赘述。
图2为本申请实施例提供的一种获取用户策略的方法的流程图。该方法可用于用户设备从VPLMN的策略控制功能网元获取VPLMN的用户策略的场景。如图2所示，该方法可以包括：
S201、HPLMN的第二策略控制功能网元向VPLMN的第一策略控制功能网元发送HPLMN的第一用户策略。相应的，VPLMN的第一策略控制功能网元从HPLMN的第二策略控制功能网元接收HPLMN的第一用户策略。其中，第一用户策略包括第一规则。第一规则用于指示第一网络切片标识信息、第一应用和第一数据网络标识信息三者之间的关联，第一数据网络标识信息用于标识第一数据网络，第一数据网络允许LBO且支持第一应用和第二应用。
例如，第一策略控制功能网元为图1中VPLMN的PCF网元105，第二策略控制功能网元为图1中HPLMN的PCF网元107。上述第一用户策略可以为第一URSP。第一网络切片标识信息可以为第一S-NSSAI。第一数据网络可以为第一DN。用于标识第一数据网络的第一数据网络标识信息可以为第一数据网络名称(data network name，DNN)。
例如，上述第一URSP如表1所示。在表1的例子中：标识为S-NSSAI 1的网络切片对应的DNN为DNN 1，其中，DNN 1是DN 1的标识，DN 1支持APP 1。第一URSP包括的第一规则用于指示S-NSSAI 1、APP 1和DNN 1三者之间的关联。用户设备在启动APP 1时，根据第一URSP确定APP 1对应的S-NSSAI为S-NSSAI 1，然后根据S-NSSAI 1标识发起会话建立流程，进而建立该用户设备与DN 1之间的通信连接。此外，DN 1允许LBO，且DN1还支持APP 2。
表1
APP S-NSSAI DNN
APP 1 S-NSSAI 1 DNN 1
例如，当第二PCF网元接收到第一PCF网元发送的获取第一URSP的请求消息，或者当第一PCF调用获取第一URSP服务时，第二PCF网元向第一PCF网元发送第一URSP。第一PCF网元从第二PCF网元获取第一URSP的过程可以结合图5或图6进一步描述。
S206、第一策略控制功能网元向用户设备发送第二用户策略。相应的，用户设备从第一策略控制功能网元接收第二用户策略。其中，第二用户策略包括第二规则和第三规则，第二规则用于指示第二网络切片标识信息、第一应用和第一数据网络标识信息三者之间的关联，第三规则用于指示第二网络切片标识信息、第二应用和第一数据网络标识信息三者之间的关联。
例如，用户设备为图1中的UE 101。第二用户策略可以为第二URSP。第二网络切片标识信息可以为第二S-NSSAI。
需要说明的是，第一策略控制功能网元可先向接入和移动性管理网元(例如，图1中的AMF网元103发送第二用户策略，由该接入和移动性管理网元向用户设备转发该第二用户策略。
根据本发明实施例的方法，用户设备获取的VPLMN的第二URSP中包括了不存在于HPLMN的第一URSP中，但是能够在VPLMN的LBO场景下使用的APP的信息，例如与上述第二应用的关联的第三规则。用户设备可以根据本方案中获得的第二URSP在VPLMN的LBO场景下使用更多的APP业务，从而提高了用户体验。
举例来说，HPLMN中部署了网络切片类型为S-NSSAI 1的网络切片，HPLMN的第一URSP中包含了APP 1、S-NSSAI 1、DNN 1三者的对应关系。所以在HPLMN中，用户设备可以建立与APP 1服务器之间的会话连接。在现有技术中，用户设备获得的VPLMN中的第二URSP，是根据HPLMN中的第一URSP得到，所以VPLMN的第二URSP中包含了与APP 1和DNN 1关联的对应关系。因此，在VPLMN中，用户设备依然只能建立与APP 1服务器之间的会话连接，也就是说，只能使用APP 1。但是在VPLMN中，DN 1是允许LBO的，DN 1中还包括APP 2服务器，所以在VPLMN中，APP 2服务器实质上可以为用户设备提供APP 2的服务。但是由于现有技术中VPLMN的第二URSP中没有APP 2对应的关联，所以用户设备无法使用APP 2，从而降低了用户的业务体验。然而，根据本申请实施例，VPLMN的第二URSP中包括APP 2对应的关联。因此，用户设备可以使用APP2，提高了用户体验。
以下将从VPMN的第二URSP中的第一S-NSSAI与HPMN的第一URSP中的第二S-NSSAI相同，或者，该第二S-NSSAI与该第一S-NSSAI对应，这两个方面进行详细描述。
例如，当第二S-NSSAI与第一S-NSSAI相同时，第二URSP中的第二规则与第一URSP的第 一规则相同。由于DNN1标识的DN允许LBO，且该DN1除了支持APP1外，还支持APP2。因此，第二URSP还包括S-NSSAI 1、APP 2和DNN 1三者之间的关联，如表2所示。S-NSSAI 1、APP 2和DNN 1三者之间的关联即为第二URSP中的第三规则。
表2
APP S-NSSAI DNN
APP 1 S-NSSAI 1 DNN 1
APP 2 S-NSSAI 1 DNN 1
当第二S-NSSAI与第一S-NSSAI对应时，第二URSP中的第二规则与第一URSP的第一规则对应。例如，第一S-NSSAI为上述S-NSSAI 1，与S-NSSAI 1对应的第二S-NSSAI为eMBB。因此，第二URSP中包括APP1、eMBB和DNN 1三者之间的关联(即，上述第二规则)。由于DNN1标识的DN允许LBO，且该DN1除了支持APP1外，还支持APP2。因此，第二URSP还包括APP 2、eMBB和DNN 1三者之间的关联(即，第三规则)，如表3所示。第二URSP的确定可结合图3进一步描述。
表3
APP S-NSSAI DNN
APP 1 eMBB DNN 1
APP 2 eMBB DNN 1
例如，在步骤S206之前，第一策略控制功能网元可以通过步骤S202至S205来确定第二URSP。其中，步骤S202和S203为可选的步骤，也就是说，第一策略控制功能网元也可通过其他方式确定第一DN和第二应用，本实施例中不做限定。
S202、第一策略控制功能网元确定第一数据网络允许LBO。
例如，第一策略控制功能网元从第二策略控制功能网元接收第一URSP后，根据第一策略控制功能网元中DNN与LBO的对应关系，确定第一URSP中允许LBO的DN，比如第一DN。例如，DNN与LBO的对应关系可以由网络管理***提前配置在第一策略控制功能网元中。
在一种可能的实现方式中，DNN与LBO的对应关系可以用允许LBO的DNN的形式表示，例如：
允许LBO的DNN：DNN 1，DNN 3，…
上述例子表示：DNN 1标识的DN 1和DNN 3标识的DN 3都允许LBO。
在另一种可能的实现方式中，DNN与LBO的对应关系也可以用表格的形式表示，如表4所示。在表4的例子中，DNN与LBO的对应关系包括：DNN 1标识的DN 1是允许LBO的，DNN 2标识的DN 2是禁止LBO的。
表4
DNN 允许/禁止LBO
DNN 1 允许
DNN 2 禁止
可选的，第一策略控制功能网元还可以确定第二DN不是允许LBO的DN。
例如，上述第一URSP中还包括禁止LBO的第二DN。举例来说，第一URSP中还包括用于指示第三S-NSSAI、第三应用和第二DNN之间的关联的第五规则。其中，第二DNN用于标识第二DN，第二DN支持第三应用。举例来说，第三S-NSSAI为S-NSSAI 2，第三应用为APP 3，第二DNN为DNN 2，则上述包括第五规则的第一URSP可以如表5所示。第一URSP包括的第 五规则用于指示S-NSSAI 2、APP 3和DNN 2三者之间的关联。
表5
APP S-NSSAI DNN
APP 1 S-NSSAI 1 DNN 1
APP 3 S-NSSAI 2 DNN 2
需要说明的是，第一规则和第五规则的区别在于，第一规则中DNN 1标识的DN 1是允许LBO的DN，而第五规则中DNN 2标识的DN 2不是允许LBO的DN，或者说，DN 2是禁止LBO的DN。
S203、第一策略控制功能网元确定第一数据网络支持第二应用。
例如，第一策略控制功能网元通过步骤S202确定允许LBO的第一DN之后，根据第一策略控制功能网元中DNN与APP的对应关系，确定第一DN支持的APP，例如，第一应用和第二应用。进而，第一策略控制功能网元从第一DN支持的APP中确定第一URSP中不涉及的APP，比如第二应用。例如，DNN与APP的对应关系可以通过网络管理***提前配置在第一策略控制功能网元中。例如，上述对应关系如表6所示。在表6的例子中：DNN 1对应的DN 1支持APP 1和APP 2。结合上述表1可看出，第一URSP中包括了S-NSSAI 1、APP 1和DNN 1三者之间的关联，但是第一URSP中不涉及APP 2。所以第一策略控制功能网元可以确定第一DN还支持的第二应用为APP 2。也就是说，用户设备在HPLMN中不能使用APP 2，但是，该用户设备可以在VPLMN的LBO场景使用APP 2。
表6
DNN APP
DNN 1 APP 1，APP 2
可选的，当第一URSP还包括上述第五规则时，由于第五规则中DNN 2标识的DN 2不是允许LBO的DN，无需执行步骤S203以及后续的S204和S205。
S204、第一策略控制功能网元将第四规则加入第一用户策略，其中，第四规则包括第一网络切片标识信息、第二应用和第一数据网络标识信息三者之间的关联。
例如，在第一规则中，与第一DNN(DNN 1)关联的第一S-NSSAI为S-NSSAI 1。此外，根据上述步骤S203确定的该DNN标识的DN还支持的第二应用为APP 2。所以，第四规则包括S-NSSAI 1、APP 2和第一DNN三者之间的关联。结合表1所示的第一URSP，加入第四规则后的第一URSP可以如表2所示。
可选的，当第一URSP中还包括上述第五规则时，加入了第四规则后第一URSP可以如表7所示，此处不再赘述。
表7
APP S-NSSAI DNN
APP 1 S-NSSAI 1 DNN 1
APP 2 S-NSSAI 1 DNN 1
APP 3 S-NSSAI 2 DNN 2
S205、第一策略控制功能网元根据加入第四规则后的第一用户策略确定第二用户策略。
可选的，当DNN 1在VPLMN中对应的第二S-NSSAI与在HPLMN中的第一S-NSSAI相同时，第二URSP即为加入第四规则后的第一URSP。例如，第二URSP可以如表2所示，第二URSP包括指示第二S-NSSAI、第一APP和第一DNN三者之间关联的第二规则，和指示第二S-NSSAI、 第二APP和第一DNN三者之间关联的第三规则。
可选的，当第一URSP中包括禁止LBO的第二DN，且DNN 2在VPLMN中对应的第三S-NSSAI与在HPLMN中的第四S-NSSAI相同时，第二URSP可以如表7所示，第二URSP还包括了指示第四S-NSSAI、第三APP和第二DNN三者之间关联的第六规则。也就是说，上述第五规则和第六规则相同。
由此，第一策略控制功能网元确定了第二URSP。
可选的，当DNN 1在VPLMN中对应的S-NSSAI与在HPLMN中的第一S-NSSAI对应时，步骤205包括：第一策略控制功能网元获取VPLMN中的S-NSSAI与HPLMN中的S-NSSAI之间的映射关系，根据该映射关系和加入第四规则后的第一用户策略确定第二用户策略，具体可以结合图3进一步描述。
由此，通过上述方案，第一策略控制功能网元确定的第二URSP包括了能够在VPLMN的LBO场景下使用的APP的信息。用户设备可以根据本方案中获得的第二URSP在VPLMN的LBO场景中使用该场景下支持的APP业务。
图3为本申请实施例提供的又一种获取用户策略的方法的流程图。该方法可用于当VPLMN中的S-NSSAI与HPLMN中的S-NSSAI对应时，用户设备从VPLMN的策略控制功能网元获取VPLMN的用户策略的场景。在该场景下，VPLMN的策略控制功能网元通过映射的方式生成第二URSP。如图3所示，该方法可以包括：
步骤S301可参考图2中S201的描述,步骤S307可参考图2中S206的描述,此处不再赘述。
例如，在步骤S307之前，第一策略控制功能网元还可以通过步骤S302至S306来确定第二URSP。步骤S302至S304可参考图2中S202至S204的描述,此处不再赘述。
在步骤S307之前，第一策略控制功能网元可执行如下步骤S305和S306。
S305、第一策略控制功能网元从VPLMN的接入和移动性管理功能网元接收第一网络切片标识信息和第二网络切片标识信息之间的第一映射关系。该第一映射关系可用于第二用户策略的生成。
例如，移动性管理功能网元为图1中的AMF网元103。第一S-NSSAI和第二S-NSSAI之间的第一映射关系可以由网络切片选择功能网元(例如，图1中的NSSF网元104)根据VPLMN与HPLMN之间的漫游协议生成并提供至AMF网元。或者，上述第一S-NSSAI和第二S-NSSAI之间的第一映射关系也可以由AMF网元根据上述漫游协议生成。例如，漫游协议可以为服务级别协议(Service Level Agreement，SLA)。
不同的运营商可以部署不同类型的网络切片，不同的网络切片类型可以通过标准的S-NSSAI进行标识，也可以通过特有的S-NSSAI进行标识。其中，标准的S-NSSAI为运营商都能识别的S-NSSAI，例如，目前第三代合作伙伴计划(third generation partnership project，3GPP)标准中已经规定的三种网络切片类型，增强的移动宽带(enhanced Mobile Broadband，eMBB)、超可靠的低延时通信(ultra-reliable low latency communications，URLLC)和海量物联网(massive IoT，MIoT)。而特有的S-NSSAI所标识的网络切片并不一定能被所有的运营商都识别出来，只有部署了该S-NSSAI所标识的网络切片的运营商才能识别特有的S-NSSAI。例如，除了上述3GPP标准中规定的三种网络切片类型之外的网络切片类型，都可以认为是特有的类型，例如车联网(vehicle-to-everything，V2X)。
通过S-NSSAI之间的映射关系，可实现四种方式的映射：标准的S-NSSAI至另一标准的 S-NSSAI的映射，或者，特有的S-NSSAI至标准的S-NSSAI的映射，或者，标准的S-NSSAI至特有的S-NSSAI的映射，或者，特有的S-NSSAI至另一特有的S-NSSAI的映射。
S306、第一策略控制功能网元根据第一映射关系，将加入第四规则后的第一用户策略中的第一网络切片标识信息映射为第二网络切片标识信息，生成第二用户策略。
以下将针对上述四种方式的映射场景，分别对步骤S305、S306进行详细描述。
第一种：
第一S-NSSAI和第二S-NSSAI都是标准的S-NSSAI。例如，为了实现负载均衡，NSSF网元生成第一S-NSSAI至第二S-NSSAI的映射关系。
例如，第一映射关系可以如表8所示。表8中，第一S-NSSAI为HPLMN中的eMBB，第二S-NSSAI为VPLMN中的MIoT，第一映射关系为eMBB对应于MIoT。
表8
第一S-NSSAI 第二S-NSSAI
eMBB MIoT
在上述第一映射关系中，第一URSP中APP对应的网络切片类型为第一S-NSSAI，由于在VPLMN中第一S-NSSAI所对应的网络切片的负载过大，所以为了实现负载均衡，NSSF网元将第一S-NSSAI映射为第二S-NSSAI，使用户设备通过第二S-NSSAI对应的网络切片建立会话。例如，在表8所对应的场景中，用户设备携带标识eMBB切片类型的S-NSSAI请求建立会话，但是在VPLMN中eMBB类型的网络切片负载过大，所以NSSF网元将eMBB标识映射为MIoT标识，使用户设备发起APP时使用MIoT类型的网络切片建立会话，此时第一映射关系为：eMBB切片类型的S-NSSAI对应MIoT切片类型的S-NSSAI。
在上述第一种映射方式下，第一策略控制功能网元执行步骤S306生成第二URSP的具体方式如下：
例如，加入第四规则后的第一URSP如表9所示。在表9的例子中，标识为eMBB的网络切片对应的DNN为DNN 1，其中，DNN 1是DN 1的标识，DN 1支持APP 1和APP 2。其中，第一规则用于指示eMBB、APP 1和DNN 1三者之间的关联，第四规则用于指示eMBB、APP 2和DNN 1三者之间的关联。
表9
APP S-NSSAI DNN
APP 1 eMBB DNN 1
APP 2 eMBB DNN 1
根据表8中的映射关系可以得到，HPLMN中的eMBB对应于VPLMN中的MIoT，所以可以将第一S-NSSAI(例如，eMBB)映射为第二S-NSSAI(例如，MIoT)，从而生成第二URSP。生成的第二URSP可以如表10所示。在表10的例子中：第二URSP包括第二规则和第三规则，其中，第二规则用于指示第二S-NSSAI(例如MIoT)、第一应用(例如APP 1)和第一DNN(例如DNN 1)三者之间的关联，第三规则用于指示第二S-NSSAI(例如MIoT)、第二应用(例如APP 2)和第一DNN(例如DNN 1)三者之间的关联。
表10
APP S-NSSAI DNN
APP 1 MIoT DNN 1
APP 2 MIoT DNN 1
第二种：
当第一S-NSSAI为HPLMN特有的S-NSSAI，第二S-NSSAI为标准的S-NSSAI时，NSSF网元根据VPLMN与HPLMN之间的漫游协议生成第一S-NSSAI与标准的S-NSSAI之间的第一映射关系。
例如，第一映射关系可以如表11所示。表11中，第一S-NSSAI为HPLMN中的S-NSSAI 1，第二S-NSSAI为VPLMN中的URLLC，第一映射关系为S-NSSAI 1对应于URLLC。
表11
第一S-NSSAI 第二S-NSSAI
S-NSSAI 1 URLLC
在上述第二种映射方式下，第一策略控制功能网元执行步骤S306生成第二URSP的具体方式如下：
例如，加入第四规则后的第一URSP如表2所示。在表2的例子中，标识为S-NSSAI 1的网络切片对应的DNN为DNN 1，其中，DNN 1是DN 1的标识，DN 1支持APP 1和APP 2。
根据表11中的映射关系可以得到，HPLMN中的S-NSSAI 1对应于VPLMN中的URLLC，所以可以将第一S-NSSAI(例如，S-NSSAI 1)映射为第二S-NSSAI(例如，URLLC)，从而生成第二URSP。生成的第二URSP可以如表12所示。在表12的例子中：第二URSP包括第二规则和第三规则，其中，第二规则用于指示第二S-NSSAI(例如URLLC)、第一应用(例如APP 1)和第一DNN(例如DNN 1)三者之间的关联，第三规则用于指示第二S-NSSAI(例如URLLC)、第二应用(例如APP 2)和第一DNN(例如DNN 1)三者之间的关联。
表12
APP S-NSSAI DNN
APP 1 URLLC DNN 1
APP 2 URLLC DNN 1
第三种：
当HPLMN中部署的第一S-NSSAI对应的网络切片是标准的S-NSSAI所标识的网络切片，而VPLMN中没有部署上述标准的S-NSSAI所标识的网络切片时，NSSF网元根据VPLMN与HPLMN之间的漫游协议生成第一S-NSSAI与VPLMN特有的S-NSSAI之间的第一映射关系。第二S-NSSAI为VPLMN特有的S-NSSAI。
例如，第一映射关系可以如表13所示。表13中，第一S-NSSAI为HPLMN中的eMBB(标准的S-NSSAI)，第二S-NSSAI为VPLMN中的S-NSSAI A，第一映射关系为eMBB对应于S-NSSAI A。
表13
第一S-NSSAI 第二S-NSSAI
eMBB S-NSSAI A
在上述第三种映射方式下，第一策略控制功能网元执行步骤S306生成第二URSP的具体方式如下：
例如，当第一S-NSSAI为标准的S-NSSAI时，假设第一S-NSSAI为eMBB，加入第四规则后的第一URSP如表9所示，在表9的例子中，标识为eMBB的网络切片对应的DNN为DNN 1， 其中，DNN 1是DN 1的标识，DN 1支持APP 1和APP 2。其中，第一规则用于指示eMBB、APP 1和DNN 1三者之间的关联，第四规则用于指示eMBB、APP 2和DNN 1三者之间的关联。
根据表13中的映射关系可以得到，HPLMN中的eMBB对应于VPLMN中的S-NSSAI A，所以可以将第一S-NSSAI(例如，eMBB)映射为第二S-NSSAI(例如，S-NSSAI A)，从而生成第二URSP。生成的第二URSP可以如表14所示。在表14的例子中：第二URSP包括第二规则和第三规则，其中，第二规则用于指示第二S-NSSAI(例如S-NSSAI A)、第一应用(例如APP 1)和第一DNN(例如DNN 1)三者之间的关联，第三规则用于指示第二S-NSSAI(例如S-NSSAI A)、第二应用(例如APP 2)和第一DNN(例如DNN 1)三者之间的关联。
表14
APP S-NSSAI DNN
APP 1 S-NSSAI A DNN 1
APP 2 S-NSSAI A DNN 1
第四种：
当第一S-NSSAI为HPLMN特有的S-NSSAI，而VPLMN中没有部署上述HPLMN特有的S-NSSAI所标识的网络切片时，NSSF网元根据VPLMN与HPLMN之间的漫游协议生成第一S-NSSAI与VPLMN特有的S-NSSAI之间的第一映射关系。第二S-NSSAI为VPLMN特有的S-NSSAI。
例如，第一映射关系可以如表15所示。表15中，第一S-NSSAI为HPLMN中的S-NSSAI 1(HPLMN特有的S-NSSAI)，第二S-NSSAI为VPLMN中的S-NSSAI A，第一映射关系为S-NSSAI 1对应于S-NSSAI A。
表15
第一S-NSSAI 第二S-NSSAI
S-NSSAI 1 S-NSSAI A
在上述第四种映射方式下，第一策略控制功能网元执行步骤S306生成第二URSP的具体方式如下：
例如，当第一S-NSSAI为HPLMN特有的S-NSSAI时，假设第一S-NSSAI为HPLMN中的S-NSSAI 1，加入第四规则后的第一URSP如表2所示。在表2的例子中，标识为S-NSSAI 1的网络切片对应的DNN为DNN 1，其中，DNN 1是DN 1的标识，DN 1支持APP 1和APP 2。
根据表15中的映射关系可以得到，HPLMN中的S-NSSAI 1对应于VPLMN中的S-NSSAI A，所以可以将第一S-NSSAI(例如，S-NSSAI 1)映射为第二S-NSSAI(例如，S-NSSAI A)，从而生成第二URSP。生成的第二URSP可以如表14所示。因此，对于上述四种映射方式中的任一种，通过上述方案，第一策略控制功能网元可以根据第一映射关系和加入第四规则后的第一URSP确定第二URSP。上述第二URSP中包括了在HPLMN中的第一URSP中不存在，但是能够在VPLMN的LBO场景下使用的APP。由此，用户设备可以根据本方案中获得的第二URSP在VPLMN的LBO场景下使用更多的APP，从而提高了用户体验。
可选的，当第一URSP中还包括禁止LBO的第二DN时，第一策略控制功能网元还可以从VPLMN的接入和移动性管理功能网元接收第三S-NSSAI和第四S-NSSAI之间的第二映射关系。其中，第三S-NSSAI至第四S-NSSAI的映射可参考第一S-NSSAI至第二S-NSSAI的映射，此处不再赘述。
图4为本申请实施例提供的又一种获取用户策略的方法的流程图。图4将结合图2和图3进行描述。
步骤S401至步骤S404可参考图2中S201至S204，或图3中S301至S304的描述，此处不再赘述。
步骤S405可参考图2中S205的描述。例如，第二URSP即为加入第四规则后的第一URSP。或者，步骤S405可参考图3中步骤S305和S306的描述，此处不再赘述。
在图4的例子中，该方法还可以包括：
S407、第一策略控制功能网元向用户设备发送第二URSP和VPLMN的标识。相应的，用户设备从第一策略控制功能网元接收第二URSP和VPLMN的标识。其中，VPLMN的标识与第二URSP关联。
由此，当用户设备从其他区域移动到VPLMN中时，能够根据VPLMN的标识获知第二URSP，从而避免了用户设备再次请求获取第二URSP，可以减少用户设备与网络的交互，从而降低了时延，提高了效率。
可选的，第一策略控制功能网元还向用户设备发送第一URSP和HPLMN的标识。相应的，用户设备从第一策略控制功能网元接收第一URSP和HPLMN的标识。其中，HPLMN的标识与第一URSP关联。
通过上述方案，用户设备可以获得第一URSP与HPLMN的标识。由此，当用户设备从其他区域移动到HPLMN中并启动APP时，能够根据HPLMN的标识获知第一URSP，从而避免了用户设备请求获取第一URSP，可以减少用户设备与网络的交互，从而降低了时延降低了时延，提高了效率。
需要说明的是，第一URSP和HPLMN的标识，和，第二URSP和VPLMN的标识可通过同一条消息发送至用户设备，也可通过不同的消息发送至用户设备，本申请并不在此限制。
可选的，在步骤S407之前，第一策略控制功能网元可执行步骤S406。需要说明的是，本申请并不限定步骤S406和步骤S401之间的先后顺序。也就是说，可以先执行步骤S406后执行步骤S401，也可以先执行步骤S401后执行步骤S406，或者，同时执行步骤S401和S406。
S406、第二策略控制功能网元向第一策略控制功能网元发送指示信息。相应的，第一策略控制功能网元从第二策略控制功能网元接收指示信息。其中，指示信息用于触发第一URSP和HPLMN的标识至用户设备的发送。例如，指示信息可以是一个标志位(flag)，本实施例不做限制。
例如，当第一策略控制功能网元向第二策略控制功能网元请求获取第一URSP时，第二策略控制功能网元判断第二策略控制功能网元中没有用户设备的上下文信息，说明用户设备没有在HPLMN中注册过，因而用户设备没有从第二策略控制功能网元中获取过第一URSP。在这种场景下，第二策略控制功能网元通过向第一策略控制功能网元发送指示信息，可以触发第一策略控制功能网元将第一URSP和HPLMN的标识发送给用户设备。
因此，通过上述方案，第一策略控制功能网元能够获知用户设备中没有第一URSP的场景，在这种场景下，指示信息会触发第一策略控制功能网元向用户设备发送第一URSP和HPLMN的标识。由此，第一策略控制功能网元能够获知用户设备中没有第一用户策略的场景，在这种场景下，指示信息会触发第一策略控制功能网元向用户设备发送第一用户策略和HPLMN的标识。从而避免了用户设备重复获取第一用户策略，可以减少用户设备与网络的交互，进而降低了时延。
图5为本申请实施例提供的又一种获取URSP的方法的信令交互图。该方法可用于用户设备在VPLMN中注册时，从VPLMN的策略控制功能网元获取VPLMN的URSP的场景。例如，图5中的用户设备为图1中的UE 101，RAN设备为图1中的RAN设备102，第一AMF网元和第二 AMF网元为图1中的AMF网元103，NSSF网元为图1中的NSSF网元104，第一PCF网元为图1中VPLMN的PCF网元105，第二PCF网元为图1中HPLMN的PCF网元107，UDM网元为图1中的UDM网元106。图5将结合图2至图4进行描述。如图5所示，该方法可以包括：
S501、用户设备向RAN设备发送请求的网络切片选择辅助信息(network slicing selection assistance information，NSSAI)，相应的，RAN设备从用户设备接收请求的NSSAI。其中，NSSAI是S-NSSAI的集合，即NSSAI中包括一个或者多个S-NSSAI。用户设备在初始入网的时候根据请求的NSSAI选择网络切片。
例如，用户设备移动到VPLMN之后发起初始注册时，可执行步骤S501。
上述请求的NSSAI可以为用户设备与VPLMN交互之前配置的NSSAI。
用户设备还可以向RAN设备发送用户设备的永久标识(subscriber permanent identifier，SUPI)和请求接入的无线接入网类型。
S502、RAN设备根据请求的NSSAI在VPLMN中确定第一AMF网元。其中，确定出的第一AMF网元为初始的AMF网元。
例如，RAN设备根据SUPI和请求的NSSAI以及无线接入网类型选择第一AMF网元，如果RAN设备无法选择出满足要求的AMF网元，则根据本地策略信息确定缺省的AMF网元为第一AMF网元。
S503、RAN设备向第一AMF网元发送请求的NSSAI，相应的，第一AMF网元从RAN设备接收请求的NSSAI。
例如，RAN设备还可以向第一AMF网元发送SUPI。
S504、第一AMF网元从HPLMN的UDM网元中获取第一签约数据。
例如，第一AMF网元从HPLMN的UDM网元获取第一签约数据可以通过发送请求消息的方式，也可以通过调用服务的方式。例如，第一AMF网元向UDM网元发送包含有SUPI的请求消息，或者第一AMF网元通过调用Nudm_SubscriberDataManagement_Get服务以请求获取第一签约数据，UDM网元通过调用Nudm_SubscriberDataManagement_Get response服务以返回第一签约数据。
例如，第一签约数据中包含了签约的S-NSSAI与DNN的关联。签约的S-NSSAI与DNN的关联如表16所示。在表16的例子中：签约S-NSSAIs包括S-NSSAI 1和S-NSSAI 2，其中，S-NSSAI 1对应于DNN 1，S-NSSAI 2对应于DNN 2和DNN 3。
表16
签约S-NSSAIs DNN
S-NSSAI 1 DNN 1
S-NSSAI 2 DNN 2，DNN 3
如果第一AMF网元支持用户设备请求的NSSAI所对应的网络切片，则用户设备获取URSP的方法可结合图6进一步描述。
如果第一AMF网元不支持用户设备请求的NSSAI所对应的网络切片，则第一AMF网元在步骤S504之后执行步骤S505。
S505、第一AMF网元从VPLMN的NSSF网元中获取映射关系。
例如，第一AMF网元从VPLMN的NSSF网元获取映射关系的请求可以通过发送请求消息的方式，也可以通过调用服务的方式。例如，第一AMF网元通过调用Slice Selection request服务以请求获取映射关系，UDM网元通过调用Slice Selection response服务以返回映射关系。其中，上述映射关系包括第一映射关系。例如，第一映射关系可参考图3中的步骤S305 的描述，此处不再赘述。此外，上述映射关系还可以包括第二映射关系。
例如，第一AMF网元通过向VPLMN的NSSF网元发送请求的NSSAI,签约的NSSAI和SUPI中的PLMN标识，从而向NSSF网元请求获取映射关系。NSSF网元根据SUPI中的PLMN标识获知用户设备是漫游用户，并确定目标AMF集合和第一允许的NSSAI。其中，目标AMF集合是指一个或者多个满足用户设备需求的AMF，第一允许的NSSAI中包含的S-NSSAI是用户设备在VPLMN中能够使用的网络切片的S-NSSAI。若HPLMN和VPLMN采用不同的S-NSSAI，NSSF网元还会根据VPLMN和HPLMN之间的漫游协议生成上述映射关系。其中，上述映射关系为HPLMN中的S-NSSAI与VPLMN中的S-NSSAI的映射关系。
例如，第一AMF网元通过调用Slice Selection request服务还用于向NSSF网元请求选择一个满足用户设备所请求的NSSAI的AMF网元。
S506、第一AMF网元向第二AMF网元发送重定向信息，相应的，第二MF网元从第一AMF网元接收重定向信息。其中，第二AMF网元为第一AMF网元从第二响应信息中的目标AMF集合中选择的一个AMF网元。
例如，重定向信息包括第一允许的NSSAI。可选的，重定向消息还包括上述步骤S505中获得的映射关系。
可选的，重定向信息还包括请求的NSSAI和签约的S-NSSAI。
S507、第二AMF网元确定第一临时拒绝的S-NSSAI。其中，第一临时拒绝的S-NSSAI是指包含在请求的NSSAI中，且属于签约的S-NSSAI，但是在当前注册区域没有被部署的网络切片的S-NSSAI。也就是说，第一临时拒绝的S-NSSAI包含在签约的S-NSSAI中，但是不包含在第一允许的NSSAI中。
例如，请求的NSSAI、签约的S-NSSAIs、第一允许的NSSAI和第一临时拒绝的S-NSSAI的关系可以如表17所示。在表17中，用户设备请求的NSSAI包括S-NSSAI 1、S-NSSAI 2、S-NSSAI 3和S-NSSAI 4，用户设备签约的S-NSSAIs包括S-NSSAI 1、S-NSSAI 2、S-NSSAI 3，第一允许的S-NSSAIs包括S-NSSAI 1和S-NSSAI 2，第一临时拒绝的NSSAI包括S-NSSAI 3。S-NSSAI 4为签约不允许的S-NSSAI。例如，上述第一临时拒绝的S-NSSAI为签约的S-NSSAI中除了第一允许的S-NSSAI之外的S-NSSAI。签约不允许的S-NSSAI为请求的NSSAI中除了签约的S-NSSAI之外的S-NSSAI。
表17
请求的NSSAI S-NSSAI 1，S-NSSAI 2，S-NSSAI 3，S-NSSAI 4
签约的S-NSSAIs S-NSSAI 1，S-NSSAI 2，S-NSSAI 3
第一允许的NSSAI S-NSSAI 1，S-NSSAI 2
第一临时拒绝的S-NSSAI S-NSSAI 3
S508、第二AMF网元向第一PCF网元请求生成第二URSP。其中，第一PCF网元为第二AMF网元在VPLMN中选择的一个PCF网元。例如，第二AMF网元还可以通过调用Npcf_AMPolicyControl_Get服务来请求第一PCF网元生成VPLMN中的第二URSP。
可选的，通过步骤S508，第二AMF网元还可以向第一PCF网元发送上述映射关系，相应的，第一PCF网元从第二AMF网元接收该映射关系。
可选的，第二AMF网元向第一PCF网元发送第一允许的NSSAI，或者，第一允许的NSSAI和第一临时拒绝的S-NSSAI。
可选的，第二AMF网元还可以向第一PCF网元发送第一签约数据。
S509、第一PCF网元从第二PCF网元获取第一URSP。
例如，第一PCF网元从第二PCF网元获取第一URSP的请求可以通过发送请求消息的方式，也可以通过调用服务的方式。例如，第一PCF网元通过调用Npcf_AMPolicyControl_Get(SUPI)服务请求获取第一URSP，第二PCF网元通过调用Npcf_AMPolicyControl_Response服务返回第一URSP。其中，第一URSP包括第一规则。第一规则用于指示第一S-NSSAI、第一应用和第一DNN三者之间的关联，第一DNN用于标识第一DN，第一DN允许LBO且支持第一应用和第二应用。
可选的，第二PCF网元向第一PCF网元发送第一签约数据。相应的，第一PCF网元从第二PCF网元接收第一签约数据。需要说明的是，第一PCF网元既可以通过同一条消息来发送第一签约数据和第一URSP，也可以通过不同的消息来发送。
由此，第一PCF可以通过上述S509中的可选步骤能够从第二PCF网元中获取签约数据。或者，第一PCF也可以通过步骤S508能够从第二AMF中获取签约数据。需要说明的是，第一PCF可以通过上述两种方式中的任一方式获取签约数据，或者第一PCF也可以通过其他方式获取签约数据，本实施例不做限制。
S510、第一PCF网元确定第一DN允许LBO。
S511、第一PCF网元确定第一DN支持第二应用。
S512、第一PCF网元将第四规则加入第一URSP，其中，第四规则包括第一S-NSSAI、第二应用和第一DNN三者之间的关联。
S513、第一PCF网元根据加入第四规则后的第一URSP确定第二URSP。
S515、第一PCF网元向第二AMF网元发送第二URSP，相应的，第二AMF网元从第一PCF网元接收第二URSP。其中，第二URSP包括第二规则和第三规则，第二规则用于指示第二S-NSSAI、第一应用和第一DNN三者之间的关联，第三规则用于指示第二S-NSSAI、第二应用和第一DNN三者之间的关联。其中，第二S-NSSAI与第一S-NSSAI相同或对应。
例如，第一PCF网元可以通过发送消息的方式，也可以通过调用服务的方式向第二AMF网元发送第二URSP。举例来说，第一PCF网元通过调用Npcf_AMPolicyControl_Response服务发送第二URSP。
可选的，第一PCF网元还可以向第二AMF网元发送VPLMN的标识，其中，VPLMN的标识与第二URSP关联。
可选的，第一PCF网元还可以向第二AMF网元发送第一URSP和HPLMN的标识，其中，HPLMN的标识与第一URSP关联。
可选的，在步骤S515之前，第一PCF网元可执行步骤S514。
S514、第二PCF网元向第一PCF网元发送指示信息。相应的，第一PCF网元从第二PCF网元接收指示信息。该指示信息用于触发第一URSP和HPLMN的标识至用户设备的发送。
上述步骤S510至S512可参考图2中S203至S205的描述；上述步骤S513可参考图2中S205或者图3中S306的描述；上述步骤S514可参考图4中S406的描述。所以此处对步骤S510至S514不再赘述。
S515、第一PCF网元向第二AMF网元发送第二URSP。
S516、第二AMF网元向用户设备发送第一允许的NSSAI和第二URSP。相应的，用户设备从第二AMF网元接收第一允许的NSSAI和第二URSP。例如，第一允许的NSSAI和第二URSP可以通过注册接受(Registration_Accepet)消息进行传输。
S517、用户设备保存第一允许的NSSAI和第二URSP。
例如，用户设备保存了第一允许的NSSAI和第二URSP后，在VPLMN中启动APP时通过携 带第二URSP中APP对应的网络切片的S-NSSAI向网络侧发起会话建立流程。
因此，当用户设备向VPLMN注册过程中，RAN设备选择的第一AMF网元不支持用户设备请求的NSSAI所对应的网络切片时，用户设备可以根据本发明实施例的方法获取VPLMN的第二URSP。上述第二URSP中还包括了不存在于HPLMN的第一URSP中，但是能够在VPLMN的LBO场景下使用的APP。用户设备可以根据本方案中获得的第二URSP在VPLMN的LBO场景下使用更多的APP，从而提高了用户体验。
此外，在本方案中，用户设备在注册过程中可以获得第二URSP，相对于用户设备根据接收到的HPLMN的第一URSP、VPLMN和HPLMN之间漫游协议来生成第二URSP的方法相比，用户设备不需要感知网络侧的漫游协议，由此增强了网络的安全性。
图6为本申请实施例提供的又一种获取URSP的方法的信令交互图。该方法的适用场景与图5所示的实施例相同。图6与图5所示实施例的区别为：图5的实施例中，第一AMF网元不支持用户设备请求的NSSAI所对应的网络切片；而图6的实施例中，第一AMF网元支持用户设备请求的NSSAI所对应的网络切片。图6将结合图5进行描述。
步骤S601至步骤S604可参考图5中S501至S504的描述，此处不再赘述。
S605、第一AMF网元确定映射关系。
例如，当HPLMN和VPLMN采用不同的S-NSSAI时，第一AMF网元根据VPLMN和HPLMN之间的漫游协议生成映射关系。其中，上述映射关系为HPLMN中的S-NSSAI与VPLMN中的S-NSSAI的映射关系。
S606、第一AMF网元确定第一允许的NSSAI。其中，第一允许的NSSAI中包含的S-NSSAI是用户设备在VPLMN中能够使用的网络切片的S-NSSAI。
由于第一AMF网元支持用户设备请求的NSSAI所对应的网络切片，从步骤S607开始，第一AMF网元可执行与图5中第二AMF网元类似的操作。例如，
S607、第一AMF网元确定第一临时拒绝的S-NSSAI。
上述步骤S607中第一AMF网元确定第一临时拒绝的S-NSSAI，可参考图5的步骤S507中，第二AMF网元确定第一临时拒绝的S-NSSAI的描述，此处不再赘述。
S608、第一AMF网元向第一PCF网元发送映射关系，相应的，第一PCF网元从第一AMF网元接收映射关系。
上述步骤S608中第一AMF网元向第一PCF网元发送映射关系，可参考图5的步骤S508中，第二AMF网元向第一PCF网元发送映射关系的描述，此处不再赘述。
步骤S609至步骤S614可参考图5中S509至S514的描述，此处不再赘述。
S615、第一PCF网元向第一AMF网元发送第二URSP，相应的，第一AMF网元从第一PCF网元接收第二URSP。
S616、第一AMF网元向用户设备发送第一允许的NSSAI和第二URSP。相应的，用户设备从第一AMF网元接收第一允许的NSSAI和第二URSP。
上述步骤S616中第一AMF网元向用户设备发送第一允许的NSSAI和第二URSP，可参考图5的步骤S516中，第二AMF网元向用户设备发送第一允许的NSSAI和第二URSP的描述，此处不再赘述。
步骤S617可参考图5中S517的描述，此处不再赘述。
因此，当用户设备向VPLMN注册过程中，RAN设备选择的第一AMF网元支持用户设备请求的NSSAI所对应的网络切片时，用户设备可以根据本发明实施例的方法获取VPLMN的第二URSP。上述第二URSP中还包括了不存在于HPLMN的第一URSP中，但是能够在VPLMN的LBO 场景下使用的APP。用户设备可以根据本方案中获得的第二URSP在VPLMN的LBO场景下使用更多的APP，从而提高了用户体验。此外，在本方案中，用户设备在注册过程中可以获得第二URSP，相对于用户设备根据接收到的HPLMN的第一URSP、VPLMN和HPLMN之间漫游协议来生成第二URSP的方法相比，用户设备不需要感知网络侧的漫游协议，由此增强了网络的安全性。
图7为本申请实施例提供的又一种获取URSP的方法的流程图。该方法可用于用户设备的签约信息改变时，用户设备获取VPLMN的URSP的场景。图7将结合图5进行描述。
S701、HPLMN的UDM网元向第二AMF网元发送第二签约数据，相应的，第二AMF网元从UDM网元接收第二签约数据。其中，第二签约数据为第一签约数据更新后的签约数据。
例如，HPLMN的UDM网元可以通过发送消息的方式，也可以通过调用服务的方式向第二AMF网元发送第二签约数据。举例来说，UDM网元通过调用Nudm_SubscriberData_Get response服务发送第二签约数据。
例如，第二AMF网元订阅了签约数据，当签约数据更新后，UDM网元将第一签约数据更新后的第二签约数据发送给第二AMF网元。假设第一签约数据如表16所示，更新后的第二签约数据如表18所示。在表18的例子中：第二签约S-NSSAIs包括S-NSSAI 1、S-NSSAI 2和S-NSSAI 3，其中，S-NSSAI 1对应于DNN 1，S-NSSAI 2对应于DNN 2和DNN 3，S-NSSAI 3对应于DNN 4。第二签约数据相对于表16中的第一签约数据，增加了S-NSSAI 3与DNN 4的关联。
表18
签约S-NSSAIs DNN
S-NSSAI 1 DNN 1
S-NSSAI 2 DNN 2，DNN 3
S-NSSAI 3 DNN 4
S702、第二AMF网元从VPLMN的NSSF网元获取第二允许的NSSAI。其中，第二允许的NSSAI为更新后的允许的NSSAI。
例如，步骤S703至S713可参考图5中的步骤S707至S717的描述，此处不再赘述。在步骤S703至S713中，第二临时拒绝的S-NSSAI为更新后的临时拒绝的S-NSSAI，第三URSP为第一URSP更新后的URSP，第四URSP为第二URSP更新后的URSP。
因此，根据本发明实施例的方法，当用户设备的签约信息发生改变时，第一策略控制功能网元可以通过第一URSP更新后的第三URSP，以及更新后的第一映射关系生成新的第二URSP，即第四URSP，并发送给用户设备。用户设备在签约信息更新后能够获得第四URSP，并根据第四URSP获取更新之后的能够在本地使用的APP的信息，从而提高了用户体验。
在上述描述中，用于指示网络切片标识信息、应用和数据网络标识信息三者之间的关联的规则(例如，上述第一至第六规则中的任一项)，可通过一条网络切片标识信息、应用和数据网络标识信息三者之间的对应关系来实现，或者，也可以通过该三者中任意两种的对应关系的组合(例如，网络切片标识信息和应用的对应关系，以及，应用和数据网络名称之间的关系)来实现，本申请并不在此限制。
上述本申请提供的实施例中，分别从各个网元本身、以及从各个网元之间交互的角度对本申请实施例提供的通信方法的各方案进行了介绍。可以理解的是，各个网元，例如上述第一PCF网元、第二PCF网元和AMF网元为了实现上述功能，其包含了执行各个功能相应的硬 件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
例如，当上述网元通过软件模块来实现相应的功能。获取用户策略的装置可包括接收模块801和发送模块803，如图8A所示。可选的，该获取用户策略的装置还包括处理模块802。
在一个实施例中，该获取用户策略的装置可用于执行上述图2至图7中第一策略控制功能网元(例如，第一PCF网元)的操作。例如：
接收模块801用于从用于从HPLMN的策略控制功能网元接收HPLMN的第一用户策略。其中，第一用户策略包括第一规则，第一规则用于指示第一网络切片标识信息、第一应用和第一数据网络标识信息三者之间的关联，第一数据网络标识信息用于标识第一数据网络，第一数据网络允许LBO且支持第一应用和第二应用。发送模块803，用于向用户设备发送VPLMN的第二用户策略。其中，第二用户策略包括第二规则和第三规则，第二规则用于指示第二网络切片标识信息、第一应用和第一数据网络标识信息三者之间的关联，第三规则用于指示第二网络切片标识信息、第二应用和第一数据网络标识信息三者之间的关联。
由此，通过本发明实施例中获取用户策略的装置，用户设备获取的VPLMN的第二URSP中包括了不存在于HPLMN的第一URSP中，但是能够在VPLMN的LBO场景下使用的APP的信息，例如上述第二应用的信息。用户设备可以根据获得的第二URSP在VPLMN的LBO场景下使用更多的APP业务，从而提高了用户体验。
可选的，发送模块803还用于向用户设备发送VPLMN的标识，VPLMN的标识与第二用户策略关联。
可选的，发送模块803还用于向用户设备发送第一用户策略和HPLMN的标识，HPLMN的标识与第一用户策略关联。
可选的，在发送模块803向用户设备发送第一用户策略和HPLMN的标识之前，接收模块801还用于从策略控制功能网元接收指示信息，指示信息用于触发第一用户策略和HPLMN的标识至用户设备的发送。
可选的，该获取用户策略的处理模块802用于将第四规则加入第一用户策略。其中，第四规则包括第一网络切片标识信息、第二应用和第一数据网络标识信息三者之间的关联，处理模块还用于根据加入第四规则后的第一用户策略确定第二用户策略。
可选的，处理模块802还用于确定第一数据网络允许LBO，以及确定第一数据网络支持第二应用。
可选的，当第二网络切片标识信息与第一网络切片标识信息相同时，第二用户策略为加入第四规则后的第一用户策略。
可选的，当第二网络切片标识信息与第一网络切片标识信息对应时，处接收模块801用于从VPLMN的接入和移动性管理功能网元接收第一网络切片标识信息和第二网络切片标识信息之间的第一映射关系；处理模块802用于根据第一映射关系和加入第四规则后的第一用户策略确定第二用户策略。
可选的，处理模块802用于根据第一映射关系，将加入第四规则后的第一用户策略中的第一网络切片标识信息映射为第二网络切片标识信息，以生成第二用户策略。
可选的，接收模块801还用于从VPLMN的接入和移动性管理功能网元接收第一网络切片标 识信息和第二网络切片标识信息之间的第一映射关系，第一映射关系用于第二用户策略的生成。
可选的，第一用户策略还包括第五规则，第五规则用于指示第三网络切片标识信息、第三应用和第二数据网络标识信息之间的关联，第二数据网络标识信息用于标识第二数据网络，第二数据网络禁止LBO；第二用户策略还包括第六规则，第六规则用于指示第四网络切片标识信息、第三应用和第二数据网络标识信息之间的关联，其中，第四网络切片标识信息与第三网络切片标识信息相同。
可选的，第一用户策略还包括第五规则，第五规则用于指示第三网络切片标识信息、第三应用和第二数据网络标识信息之间的关联，第二数据网络标识信息用于标识第二数据网络，第二数据网络禁止LBO；第二用户策略还包括第六规则，第六规则用于指示第四网络切片标识信息、第三应用和第二数据网络标识信息之间的关联，其中，第四网络切片标识信息与第三网络切片标识信息对应。
可选的，接收模块801还用于从VPLMN的接入和移动性管理功能网元接收第三网络切片标识信息和第四网络切片标识信息之间的第二映射关系；处理模块802还用于根据第三网络切片标识信息和第二映射关系确定第四网络切片标识信息。
此外，获取用户策略的装置中的接收模块801、处理模块802和发送模块803还可实现上述方法中第一策略控制功能网元的其他操作或功能，此处不再赘述。
在另一个实施例中，图8A所示的获取用户策略的装置还可用于执行上述图4中第二策略控制功能网元(例如，第二PCF网元)的操作。例如：
发送模块803用于向VPLMN的第一策略控制功能网元发送HPLMN的用户策略，还用于向第一策略控制功能网元发送指示信息。其中指示信息用于触发该发送模块803将HPLMN的用户策略和HPLMN的标识发送到用户设备。上述HPLMN的标识与HPLMN的用户策略关联。
由此，VPLMN的第一策略控制功能网元可以接收到HPLMN的用户策略，从而根据该HPLMN的用户策略生成VPLMN的用户策略。其中，该VPLMN的用户策略中包括了不存在于HPLMN的用户策略中，但是能够在VPLMN的LBO场景下使用的APP的信息。用户设备可以根据获得的第二用户策略在VPLMN的LBO场景下使用更多的APP业务，从而提高了用户体验。此外，VPLMN的策略控制功能网元接收到指示信息的触发后，将用户策略和HPLMN的标识发送到用户设备，避免了用户设备重复获取HPLMN的用户策略，可以减少用户设备与网络的交互，从而降低了时延。
此外，上述获取用户策略的装置中的接收模块801、处理模块802和发送模块803还可实现上述方法中第二策略控制功能网元的其他操作或功能，此处不再赘述。
在又一个实施例中，图8A所示的获取用户策略的装置还可用于执行上述图3中接入和移动性管理功能网元(例如，AMF网元)的操作。例如：
发送模块803用于向第一策略控制功能网元发送第一网络切片标识信息和第二网络切片标识信息之间的映射关系。其中，第一网络切片标识信息为数据网络支持的HPLMN中的网络切片标识信息，第二网络切片标识信息为数据网络支持的VPLMN中的网络切片标识信息，上述映射关系用于第二网络切片标识信息的确定。
由于在现有技术中用户设备需要从VPLMN的接入和移动性管理功能网元获取上述第一网络切片标识信息和第二网络切片标识信息之间的映射关系，进而生成第二用户策略。根据现 有技术，用户设备会通过上述映射关系感知到VPLMN与HPLMN之间的漫游协议。而根据本申请提出的上述方法，用户设备从网络侧获取第二用户策略，从而不需要感知VPLMN与HPLMN之间的漫游协议，由此提高了网络的安全性能。
此外，获取用户策略的中的接收模块801、处理模块802和发送模块803还可实现上述方法中接入和移动性管理功能网元的其他操作或功能，此处不再赘述。
图8B示出了上述实施例中所涉及的获取用户策略的装置的另一种可能的结构示意图。获取用户策略的装置包括收发器804和处理器805，如图8B所示。例如，处理器805可以为通用微处理器、数据处理电路、专用集成电路(application specific integrated circuit，ASIC)或者现场可编程门阵列(field-programmable gate arrays，FPGA)电路。所述获取用户策略的装置还可以包括存储器806，例如，存储器为随机存取存储器(random access memory，RAM)。所述存储器用于与处理器805耦合，其保存该获取用户策略的装置必要的计算机程序8061。
此外，上述实施例中所涉及的获取用户策略的方法还提供了一种载体807，所述载体内保存有该获取用户策略的装置的计算机程序8071，可以将计算机程序8071加载到处理器805中。上述载体可以为光信号、电信号、电磁信号或者计算机可读存储介质(例如，硬盘)。
当上述计算机程序8061或8071在计算机(例如，处理器805)上运行时，可使得计算机执行上述的方法。
例如，在一个实施例中，处理器805被配置为第一策略控制功能网元的其他操作或功能。收发器804用于实现获取用户策略的装置与第二策略控制功能网元/接入和移动性管理功能网元/用户设备的通信。
在另一个实施例中，处理器805被配置为第二策略控制功能网元的其他操作或功能。收发器804用于实现获取用户策略的装置与VPLMN的策略控制功能网元之间的通信。
在另一个实施例中，处理器805被配置为通信装置执行上述方法中第一NF网元相应的功能。收发器804用于实现获取用户策略的装置和第一NRF网元之间的通信。
用于执行本申请上述无线接入网设备的控制器/处理器可以是中央处理器(CPU)，通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)，现场可编程门阵列(FPGA)或者其他可编程逻辑器件、晶体管逻辑器件，硬件部件或者其任意组合。其可以实现或执行结合本申请公开内容所描述的各种示例性的逻辑方框，模块和电路。所述处理器也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，DSP和微处理器的组合等等。
结合本申请公开内容所描述的方法或者算法的步骤可以硬件的方式来实现，也可以是由处理器执行软件指令的方式来实现。软件指令可以由相应的软件模块组成，软件模块可以被存放于RAM存储器、闪存、ROM存储器、EPROM存储器、EEPROM存储器、寄存器、硬盘、移动硬盘、CD-ROM或者本领域熟知的任何其它形式的存储介质中。一种示例性的存储介质耦合至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息。当然，存储介质也可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。另外，该ASIC可以位于无线接入网设备中。当然，处理器和存储介质也可以作为分立组件存在于无线接入网设备中。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包 括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本发明实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘Solid State Disk(SSD))等。
以上所述的具体实施方式，对本发明的目的、技术方案和有益效果进行了进一步详细说明，所应理解的是，以上所述仅为本发明的具体实施方式而已，并不用于限定本发明的保护范围，凡在本发明的技术方案的基础之上，所做的任何修改、等同替换、改进等，均应包括在本发明的保护范围之内。

Claims (29)

  1. 一种获取用户策略的方法，其特征在于，包括：
    拜访的公用陆地移动网VPLMN的第一策略控制功能网元从归属公用陆地移动网HPLMN的第二策略控制功能网元接收所述HPLMN的第一用户策略，其中，所述第一用户策略包括第一规则，所述第一规则用于指示第一网络切片标识信息、第一应用和第一数据网络标识信息三者之间的关联，所述第一数据网络标识信息用于标识第一数据网络，所述第一数据网络允许本地路由LBO且支持所述第一应用和第二应用；
    所述第一策略控制功能网元向用户设备发送所述VPLMN的第二用户策略，所述第二用户策略包括第二规则和第三规则，所述第二规则用于指示第二网络切片标识信息、所述第一应用和所述第一数据网络标识信息三者之间的关联，所述第三规则用于指示所述第二网络切片标识信息、所述第二应用和所述第一数据网络标识信息三者之间的关联。
  2. 根据权利要求1所述的方法，其特征在于，还包括：
    所述第一策略控制功能网元向所述用户设备发送所述VPLMN的标识，所述VPLMN的标识与所述第二用户策略关联。
  3. 根据权利要求2所述的方法，其特征在于，还包括：
    所述第一策略控制功能网元向所述用户设备发送所述第一用户策略和所述HPLMN的标识，所述HPLMN的标识与所述第一用户策略关联。
  4. 根据权利要求3所述的方法，其特征在于，在所述第一策略控制功能网元向所述用户设备发送所述第一用户策略和所述HPLMN的标识之前，还包括：
    所述第一策略控制功能网元从所述第二策略控制功能网元接收指示信息，所述指示信息用于触发所述第一用户策略和所述HPLMN的标识至所述用户设备的发送。
  5. 根据权利要求1至4中任一项所述的方法，其特征在于，还包括：
    所述第一策略控制功能网元将第四规则加入所述第一用户策略，所述第四规则包括所述第一网络切片标识信息、所述第二应用和所述第一数据网络标识信息三者之间的关联；
    所述第一策略控制功能网元根据加入所述第四规则后的第一用户策略确定所述第二用户策略。
  6. 根据权利要求1至5中任一项所述的方法，其特征在于，还包括：
    所述第一策略控制功能网元确定所述第一数据网络允许LBO；
    所述第一策略控制功能网元确定所述第一数据网络支持所述第二应用。
  7. 根据权利要求5或6所述的方法，其特征在于，当所述第二网络切片标识信息与所述第一网络切片标识信息相同时，
    所述第二用户策略为所述加入所述第四规则后的第一用户策略。
  8. 根据权利要求5或6所述的方法，其特征在于，当所述第二网络切片标识信息与所述第一网络切片标识信息对应时，所述第一策略控制功能网元根据所述加入所述第四规则后的第一用户策略确定所述第二用户策略，包括：
    所述第一策略控制功能网元从所述VPLMN的接入和移动性管理功能网元接收所述第一网络切片标识信息和所述第二网络切片标识信息之间的第一映射关系；
    所述第一策略控制功能网元根据所述第一映射关系和所述加入所述第四规则后的第一用户策略确定所述第二用户策略。
  9. 根据权利要求8所述的方法，其特征在于，所述第一策略控制功能网元根据所述第一 映射关系和所述加入所述第四规则后的第一用户策略确定所述第二用户策略，包括：
    所述第一策略控制功能网元根据所述第一映射关系，将所述加入所述第四规则后的第一用户策略中的所述第一网络切片标识信息映射为所述第二网络切片标识信息，以生成所述第二用户策略。
  10. 根据权利要求1至6中任一项所述的方法，其特征在于，还包括：
    所述第一策略控制功能网元从所述VPLMN的接入和移动性管理功能网元接收所述第一网络切片标识信息和所述第二网络切片标识信息之间的第一映射关系，所述第一映射关系用于所述第二用户策略的生成。
  11. 根据权利要求7所述的方法，其特征在于，
    所述第一用户策略还包括第五规则，所述第五规则用于指示第三网络切片标识信息、第三应用和第二数据网络标识信息之间的关联，所述第二数据网络标识信息用于标识第二数据网络，所述第二数据网络禁止LBO；
    所述第二用户策略还包括第六规则，所述第六规则用于指示第四网络切片标识信息、所述第三应用和所述第二数据网络标识信息之间的关联，其中，所述第四网络切片标识信息与所述第三网络切片标识信息相同。
  12. 根据权利要求8至10中任一项所述的方法，其特征在于，
    所述第一用户策略还包括第五规则，所述第五规则用于指示第三网络切片标识信息、第三应用和第二数据网络标识信息之间的关联，所述第二数据网络标识信息用于标识第二数据网络，所述第二数据网络禁止LBO；
    所述第二用户策略还包括第六规则，所述第六规则用于指示第四网络切片标识信息、所述第三应用和所述第二数据网络标识信息之间的关联，其中，所述第四网络切片标识信息与所述第三网络切片标识信息对应。
  13. 根据权利要求12所述的方法，其特征在于，还包括：
    所述第一策略控制功能网元从所述VPLMN的接入和移动性管理功能网元接收所述第三网络切片标识信息和所述第四网络切片标识信息之间的第二映射关系；
    所述第一策略控制功能网元根据所述第三网络切片标识信息和所述第二映射关系确定所述第四网络切片标识信息。
  14. 一种获取用户策略的装置，其特征在于，包括：
    接收模块，用于从归属公用陆地移动网HPLMN的策略控制功能网元接收所述HPLMN的第一用户策略，其中，所述第一用户策略包括第一规则，所述第一规则用于指示第一网络切片标识信息、第一应用和第一数据网络标识信息三者之间的关联，所述第一数据网络标识信息用于标识第一数据网络，所述第一数据网络允许本地路由LBO且支持所述第一应用和第二应用；
    发送模块，用于向用户设备发送拜访的公用陆地移动网VPLMN的第二用户策略，所述第二用户策略包括第二规则和第三规则，所述第二规则用于指示第二网络切片标识信息、所述第一应用和所述第一数据网络标识信息三者之间的关联，所述第三规则用于指示所述第二网络切片标识信息、所述第二应用和所述第一数据网络标识信息三者之间的关联。
  15. 根据权利要求14所述的获取用户策略的装置，其特征在于，
    所述发送模块还用于向所述用户设备发送所述VPLMN的标识，所述VPLMN的标识与所述第二用户策略关联。
  16. 根据权利要求15所述的获取用户策略的装置，其特征在于，
    所述发送模块还用于向所述用户设备发送所述第一用户策略和所述HPLMN的标识，所述 HPLMN的标识与所述第一用户策略关联。
  17. 根据权利要求16所述的获取用户策略的装置，其特征在于，
    在所述发送模块向所述用户设备发送所述所述第一用户策略和所述HPLMN的标识之前，所述接收模块还用于从所述策略控制功能网元接收指示信息，所述指示信息用于触发所述第一用户策略和所述HPLMN的标识至所述用户设备的发送。
  18. 根据权利要求14至17中任一项所述的获取用户策略的装置，其特征在于，所述获取用户策略的装置还包括：
    处理模块，用于将第四规则加入所述第一用户策略，所述第四规则包括所述第一网络切片标识信息、所述第二应用和所述第一数据网络标识信息三者之间的关联；
    所述处理模块还用于根据加入所述第四规则后的第一用户策略确定所述第二用户策略。
  19. 根据权利要求18所述的获取用户策略的装置，其特征在于，
    所述处理模块还用于确定所述第一数据网络允许LBO；
    所述处理模块还用于确定所述第一数据网络支持所述第二应用。
  20. 根据权利要求18或19所述的获取用户策略的装置，其特征在于，当所述第二网络切片标识信息与所述第一网络切片标识信息相同时，
    所述第二用户策略为所述加入所述第四规则后的第一用户策略。
  21. 根据权利要求18或19所述的获取用户策略的装置，其特征在于，当所述第二网络切片标识信息与所述第一网络切片标识信息对应时，
    所述接收模块用于从所述VPLMN的接入和移动性管理功能网元接收所述第一网络切片标识信息和所述第二网络切片标识信息之间的第一映射关系；
    所述处理模块用于根据所述第一映射关系和所述加入所述第四规则后的第一用户策略确定所述第二用户策略。
  22. 根据权利要求21所述的获取用户策略的装置，其特征在于，
    所述处理模块用于根据所述第一映射关系，将所述加入所述第四规则后的第一用户策略中的所述第一网络切片标识信息映射为所述第二网络切片标识信息，以生成所述第二用户策略。
  23. 根据权利要求14至19中任一项所述的获取用户策略的装置，其特征在于，
    所述接收模块还用于从所述VPLMN的接入和移动性管理功能网元接收所述第一网络切片标识信息和所述第二网络切片标识信息之间的第一映射关系，所述第一映射关系用于所述第二用户策略的生成。
  24. 根据权利要求20所述的获取用户策略的装置，其特征在于，
    所述第一用户策略还包括第五规则，所述第五规则用于指示第三网络切片标识信息、第三应用和第二数据网络标识信息之间的关联，所述第二数据网络标识信息用于标识第二数据网络，所述第二数据网络禁止LBO；
    所述第二用户策略还包括第六规则，所述第六规则用于指示第四网络切片标识信息、所述第三应用和所述第二数据网络标识信息之间的关联，其中，所述第四网络切片标识信息与所述第三网络切片标识信息相同。
  25. 根据权利要求21至23中任一项所述的获取用户策略的装置，其特征在于，
    所述第一用户策略还包括第五规则，所述第五规则用于指示第三网络切片标识信息、第三应用和第二数据网络标识信息之间的关联，所述第二数据网络标识信息用于标识第二数据网络，所述第二数据网络禁止LBO；
    所述第二用户策略还包括第六规则，所述第六规则用于指示第四网络切片标识信息、所述 第三应用和所述第二数据网络标识信息之间的关联，其中，所述第四网络切片标识信息与所述第三网络切片标识信息对应。
  26. 根据权利要求25所述的获取用户策略的装置，其特征在于，
    所述接收模块还用于从所述VPLMN的接入和移动性管理功能网元接收所述第三网络切片标识信息和所述第四网络切片标识信息之间的第二映射关系；
    所述处理模块还用于根据所述第三网络切片标识信息和所述第二映射关系确定所述第四网络切片标识信息。
  27. 一种计算机可读存储介质，包括指令，当其在计算机上运行时，使得计算机执行如权利要求1至13任意一项所述的方法。
  28. 一种获取用户策略的***，其特征在于，包括：
    归属公用陆地移动网HPLMN的第二策略控制功能网元，用于发送所述HPLMN的第一用户策略，其中，所述第一用户策略包括第一规则，所述第一规则用于指示第一网络切片标识信息、第一应用和第一数据网络标识信息三者之间的关联，所述第一数据网络标识信息用于标识第一数据网络，所述第一数据网络允许本地路由LBO且支持所述第一应用和第二应用；
    拜访的公用陆地移动网VPLMN的第一策略控制功能网元，用于从所述第二策略控制功能网元接收所述第一用户策略，发送所述VPLMN的第二用户策略，所述第二用户策略包括第二规则和第三规则，所述第二规则用于指示第二网络切片标识信息、所述第一应用和所述第一数据网络标识信息三者之间的关联，所述第三规则用于指示所述第二网络切片标识信息、所述第二应用和所述第一数据网络标识信息三者之间的关联；
  29. 根据权利要求28所述的获取用户策略的***，其特征在于，还包括：
    用户设备，用于从所述第一策略控制功能网元接收所述第二用户策略。
PCT/CN2018/120226 2017-12-13 2018-12-11 用户策略的获取 WO2019114684A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP18889766.4A EP3720048B1 (en) 2017-12-13 2018-12-11 User policy acquisition
US16/897,548 US11381956B2 (en) 2017-12-13 2020-06-10 Obtaining of UE policy

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201711330705.XA CN109922472B (zh) 2017-12-13 2017-12-13 用户策略的获取
CN201711330705.X 2017-12-13

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/897,548 Continuation US11381956B2 (en) 2017-12-13 2020-06-10 Obtaining of UE policy

Publications (1)

Publication Number Publication Date
WO2019114684A1 true WO2019114684A1 (zh) 2019-06-20

Family

ID=66819962

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/120226 WO2019114684A1 (zh) 2017-12-13 2018-12-11 用户策略的获取

Country Status (4)

Country Link
US (1) US11381956B2 (zh)
EP (1) EP3720048B1 (zh)
CN (2) CN109922472B (zh)
WO (1) WO2019114684A1 (zh)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4007360A4 (en) * 2019-08-05 2022-08-17 Guangdong Oppo Mobile Telecommunications Corp., Ltd. SESSION VERIFICATION METHOD, ELECTRONIC DEVICE AND STORAGE MEDIA
RU2787208C2 (ru) * 2019-07-16 2022-12-29 Гуандун Оппо Мобайл Телекоммьюникейшнс Корп., Лтд. Способ, и устройство, и пользовательское оборудование для отображения политик
US11637780B2 (en) 2019-07-16 2023-04-25 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Policy mapping method and device, and user equipment
EP4247115A3 (en) * 2019-10-04 2023-11-15 Samsung Electronics Co., Ltd. Method and device for activating 5g user
EP4192184A4 (en) * 2020-08-13 2024-01-24 Huawei Technologies Co., Ltd. PDU SESSION SETUP METHOD, TERMINAL DEVICE AND CHIP SYSTEM

Families Citing this family (29)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
AU2016364681B2 (en) * 2015-12-01 2019-11-07 Telefonaktiebolaget Lm Ericsson (Publ) Predictive acknowledgment feedback mechanism
SG11202008917QA (en) 2018-03-14 2020-10-29 Guangdong Oppo Mobile Telecommunications Corp Ltd Method for using cross-system policy, user equipment, and computer storage media
JP7079141B2 (ja) * 2018-05-11 2022-06-01 シャープ株式会社 Ｕｅ通信制御方法
US11362955B2 (en) * 2018-06-28 2022-06-14 Qualcomm Incorporated Applicability of policies for wireless communication
KR20200031900A (ko) * 2018-09-17 2020-03-25 삼성전자주식회사 Pdu 세션 제어 방법 및 장치
CN112189361B (zh) * 2019-05-06 2023-09-29 联发科技股份有限公司 无线通信方法及用户设备
CN112312539B (zh) * 2019-07-30 2022-01-14 华为技术有限公司 策略控制功能网元的选择方法、装置、***及存储介质
US20230232205A1 (en) * 2019-08-09 2023-07-20 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for group-based network management
EP3780734B1 (en) 2019-08-14 2024-04-17 MediaTek Singapore Pte. Ltd. Reregistration to slices with mapped s-nssais alone in 5g system
CN112449399B (zh) * 2019-09-02 2023-03-10 华为技术有限公司 一种通信方法、装置及***
KR20210030771A (ko) * 2019-09-10 2021-03-18 삼성전자주식회사 무선 통신 시스템에서 단말의 정책을 제공하는 방법 및 장치
WO2021056576A1 (zh) * 2019-09-29 2021-04-01 Oppo广东移动通信有限公司 一种业务传输方法及装置、通信设备
WO2021089158A1 (en) * 2019-11-07 2021-05-14 Huawei Technologies Co., Ltd. Network entities for supporting analytics generation
CN111404814B (zh) * 2020-02-28 2021-06-15 华为技术有限公司 一种数据传输的方法及通信装置
US11622323B2 (en) * 2020-03-27 2023-04-04 Qualcomm Incorporated Slice allocation and interface to applications
WO2021243690A1 (en) * 2020-06-05 2021-12-09 Qualcomm Incorporated Public land mobile network search after protocol data unit rejection
WO2022021088A1 (en) * 2020-07-28 2022-02-03 Qualcomm Incorporated Restriction on single network slice selection assistance information in ue route selection policy
WO2022021435A1 (zh) * 2020-07-31 2022-02-03 Oppo广东移动通信有限公司 数据传输方法、设备及存储介质
US20220053444A1 (en) * 2020-08-13 2022-02-17 Alibaba Group Holding Limited Network Communication Method and Apparatus
CN112153698B (zh) * 2020-09-10 2023-06-23 中国联合网络通信集团有限公司 一种跨域多接入边缘计算策略生成的方法及设备
CN114363918B (zh) * 2020-09-30 2023-05-09 中国联合网络通信集团有限公司 网络切片签约方法、用户设备、核心网设备及***
CN114521004A (zh) * 2020-11-19 2022-05-20 ***通信集团有限公司 数据发送方法、装置、设备及存储介质
CN113259929B (zh) * 2021-05-11 2022-04-26 中国联合网络通信集团有限公司 漫游用户会话建立方法、应用服务器、nssf及ue
WO2022245053A1 (en) * 2021-05-17 2022-11-24 Samsung Electronics Co., Ltd. Method and apparatus for selecting route selection descriptor in wireless network
CN115484582A (zh) * 2021-05-31 2022-12-16 华为技术有限公司 通信方法和通信装置
CN113423078B (zh) * 2021-06-03 2022-08-09 中国联合网络通信集团有限公司 应用程序网络分片选择方法、应用服务器及pcf
CN113993176B (zh) * 2021-09-26 2024-06-21 深圳市广和通无线股份有限公司 路由选择策略更新方法、终端及网络侧设备
WO2023214043A1 (en) * 2022-05-06 2023-11-09 Telefonaktiebolaget Lm Ericsson (Publ) Ursp rule provisioning in roaming
CN114980276A (zh) * 2022-06-17 2022-08-30 中国电信股份有限公司 专网切片接入方法、装置和***

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106375987A (zh) * 2015-07-22 2017-02-01 中兴通讯股份有限公司 一种网络切片的选择方法及***
WO2017113100A1 (en) * 2015-12-29 2017-07-06 Telefonaktiebolaget Lm Ericsson (Publ) Network nodes and methods performed therein for enabling communication in a communication network
CN106982458A (zh) * 2017-03-09 2017-07-25 华为技术有限公司 一种网络切片的选择方法及装置
WO2017175714A1 (ja) * 2016-04-05 2017-10-12 シャープ株式会社 端末装置、基地局装置、ＭＭＥ（Ｍｏｂｉｌｉｔｙ Ｍａｎａｇｅｍｅｎｔ Ｅｎｔｉｔｙ）及び通信制御方法

Family Cites Families (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2007079682A1 (fr) * 2006-01-10 2007-07-19 Huawei Technologies Co., Ltd. Procédé et système utilisant la commande de politique et de facturation du service de la fonction d'application
US8995389B2 (en) * 2006-07-05 2015-03-31 Telefonaktiebolaget L M Ericsson (Publ) Policy management in multi-access scenarios
JP5340304B2 (ja) * 2007-12-05 2013-11-13 テレフオンアクチーボラゲット エル エム エリクソン（パブル） 周波数帯域を共有する運用者に対するリソース割り当て
CN101217383A (zh) * 2008-01-04 2008-07-09 中兴通讯股份有限公司 一种策略和计费规则功能关联关系的删除方法
US11080790B2 (en) * 2009-09-24 2021-08-03 Guidewire Software, Inc. Method and apparatus for managing revisions and tracking of insurance policy elements
US8548463B2 (en) * 2011-10-18 2013-10-01 Alcatel Lucent PCRN roaming agreement
EP2725831B1 (en) 2012-10-23 2018-04-25 Deutsche Telekom AG Method for using a user equipment in a coverage area of a visited public land mobile network, public land mobile network and computer program product
EP3032872B1 (en) * 2013-08-08 2018-07-04 LG Electronics Inc. Method and apparatus for steering traffic in wireless communication system
US20150079979A1 (en) * 2013-09-16 2015-03-19 Qualcomm Incorporated Seamless and resource efficient roaming for group call services on broadcast/multicast networks
US9467480B2 (en) * 2013-09-16 2016-10-11 Qualcomm Incorporated Selectively multiplexing incoming WebRTC traffic and/or de-multiplexing outgoing WebRTC traffic by a client-based WebRTC proxy on behalf of a WebRTC multimedia client application
US10616820B2 (en) * 2015-08-25 2020-04-07 Lg Electronics Inc. Base station connecting method and user equipment performing same
WO2017053742A1 (en) * 2015-09-23 2017-03-30 Convida Wireless, Llc Aggregated handover in integrated small cell and wifi networks
US11019154B2 (en) * 2016-07-11 2021-05-25 Nokia Solutions And Networks Oy Methods and apparatuses for correlating intercept related information with call content

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106375987A (zh) * 2015-07-22 2017-02-01 中兴通讯股份有限公司 一种网络切片的选择方法及***
WO2017113100A1 (en) * 2015-12-29 2017-07-06 Telefonaktiebolaget Lm Ericsson (Publ) Network nodes and methods performed therein for enabling communication in a communication network
WO2017175714A1 (ja) * 2016-04-05 2017-10-12 シャープ株式会社 端末装置、基地局装置、ＭＭＥ（Ｍｏｂｉｌｉｔｙ Ｍａｎａｇｅｍｅｎｔ Ｅｎｔｉｔｙ）及び通信制御方法
CN106982458A (zh) * 2017-03-09 2017-07-25 华为技术有限公司 一种网络切片的选择方法及装置

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
HUAWEI ET AL.: "Network slice instance selection", S2-175296, SA WG2 MEETING #122, 26 June 2017 (2017-06-26), Cabo, Mexico, XP051310264 *
See also references of EP3720048A4

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
RU2787208C2 (ru) * 2019-07-16 2022-12-29 Гуандун Оппо Мобайл Телекоммьюникейшнс Корп., Лтд. Способ, и устройство, и пользовательское оборудование для отображения политик
US11637780B2 (en) 2019-07-16 2023-04-25 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Policy mapping method and device, and user equipment
EP4007360A4 (en) * 2019-08-05 2022-08-17 Guangdong Oppo Mobile Telecommunications Corp., Ltd. SESSION VERIFICATION METHOD, ELECTRONIC DEVICE AND STORAGE MEDIA
EP4247115A3 (en) * 2019-10-04 2023-11-15 Samsung Electronics Co., Ltd. Method and device for activating 5g user
EP4192184A4 (en) * 2020-08-13 2024-01-24 Huawei Technologies Co., Ltd. PDU SESSION SETUP METHOD, TERMINAL DEVICE AND CHIP SYSTEM

Also Published As

Publication number Publication date
EP3720048A1 (en) 2020-10-07
CN114125817A (zh) 2022-03-01
US20200304983A1 (en) 2020-09-24
EP3720048B1 (en) 2024-06-19
EP3720048A4 (en) 2021-01-20
CN109922472B (zh) 2021-10-26
US11381956B2 (en) 2022-07-05
CN109922472A (zh) 2019-06-21

Similar Documents

Publication Publication Date Title
WO2019114684A1 (zh) 用户策略的获取
US11172521B2 (en) System and method for management of session information in data communication network
CN108574969B (zh) 多接入场景中的连接处理方法和装置
US10939276B2 (en) Method and apparatus for session management function selection
WO2019174505A1 (zh) 一种基于网络切片的通信方法及装置
WO2020224622A1 (zh) 一种信息配置方法及装置
WO2019001204A1 (zh) 切片选择方法和装置
US11962998B2 (en) Method and device for accessing a network
WO2023280121A1 (zh) 一种获取边缘服务的方法和装置
US10893574B2 (en) Packet data unit session release method and network entity performing the same
CN111031538B (zh) 一种鉴权的方法及装置
US20120063437A1 (en) Method for supporting pdn gw selection
WO2018086123A1 (zh) 会话处理方法、装置和***
CN111615844B (zh) 用于选择服务无线通信设备的会话管理实体的方法和装置
EP3445072B1 (en) Mobile radio communication network and method for associating a mobile radio terminal device to a network slice instance of a mobile radio communication network
JP2021503199A (ja) 通信端末、接続を要求する方法、ネットワーク構成要素および通信端末にサービスを提供する方法
WO2019037500A1 (zh) 一种选择无线接入网设备的方法及装置
WO2019184721A1 (zh) 一种重定向的方法及装置
JP2021513825A (ja) Ｓｓｃモードを決定するための方法および装置
CN115396865B (zh) 终端漫游数据处理方法及网络设备
WO2023143212A1 (zh) 一种通信方法及装置
CN116647832A (zh) 一种通信方法及装置
CN116567587A (zh) 通信方法及通信装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18889766

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2018889766

Country of ref document: EP

Effective date: 20200629