WO2021159523A1 - Procédé, appareil et système de communication - Google Patents

Procédé, appareil et système de communication Download PDF

Info

Publication number
WO2021159523A1
WO2021159523A1 PCT/CN2020/075417 CN2020075417W WO2021159523A1 WO 2021159523 A1 WO2021159523 A1 WO 2021159523A1 CN 2020075417 W CN2020075417 W CN 2020075417W WO 2021159523 A1 WO2021159523 A1 WO 2021159523A1
Authority
WO
WIPO (PCT)
Prior art keywords
nssai
network element
slice
allowed
amf
Prior art date
Application number
PCT/CN2020/075417
Other languages
English (en)
Chinese (zh)
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 PCT/CN2020/075417 priority Critical patent/WO2021159523A1/fr
Publication of WO2021159523A1 publication Critical patent/WO2021159523A1/fr

Links

Images

Classifications

    • 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
    • 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

Definitions

  • This application relates to the field of communication technology, and in particular to communication methods, devices and systems.
  • the mobility management network element In the registration process of the terminal device, if the mobility management network element decides to establish a policy association with the policy control network element, the mobility management network element will select the assistance information (network slice selection assistance information, NSSAI) according to the network slice requested by the terminal device. ) Determine the allowed NSSAI, where the requested NSSAI includes identification information of one or more network slices that the terminal device requests to access, and the allowed NSSAI includes identification information of one or more network slices that the terminal device is allowed to access. Then, the mobility management network element controls the network element according to the allowed NSSAI selection policy.
  • NSSAI network slice selection assistance information
  • the mobility management network element After the mobility management network element selects the policy control network element, it initiates a policy association establishment process to request the policy control network element to obtain the policy. At the same time, the policy control network element returns a policy control request trigger to the mobility management network element. Request Triggers). When the mobility management network element subsequently determines that the triggering condition of the policy control request trigger is satisfied, the mobility management network element needs to request the policy control network element to update the policy.
  • the trigger condition of the policy control request trigger includes: the allowed NSSAI of the terminal device is changed. That is, a change in the allowed NSSAI of the terminal device will trigger the mobility management network element to request the policy control network element to update the policy.
  • the network After the registration process, the network enters the slice authentication process of the network slice, that is, performs the slice authentication process on the network slices that need to perform slice authentication in the requested NSSAI. If the slice authentication of a certain network slice is successful, a new allowed NSSAI is obtained according to the identification information of the network slice.
  • the new allowed NSSAI includes the allowed NSSAI determined in the registration process and the network that contains the successful slice authentication. The identification information of the slice.
  • the new allowed NSSAI obtained after the slice authentication process may be different from the allowed NSSAI determined in the registration process, that is, the allowed NSSAI of the terminal device changes, which triggers the mobility management network element to change to the policy control network element Request an update policy.
  • the policy control network element selected in the registration process may not support the new allowed NSSAI, which leads to the need to reselect a policy control network element that supports the new allowed NSSAI, that is, trigger the reselection of the policy control network element, and thus Cause a waste of resources.
  • the present application provides a communication method, device, and system to reduce the reselection of policy control network elements, thereby saving resources.
  • an embodiment of the present application provides a communication method, including: after the first slice performs slice authentication, the first mobility management network element determines the allowed network slice selection auxiliary information NSSAI, and the allowed NSSAI includes the allowed terminal
  • the identification information of the slice accessed by the device, the first slice is the slice for which slice authentication needs to be performed among the slices that the terminal device requests to access; the first mobility management network element selects the policy control network element according to the allowed NSSAI; where, The slice corresponding to the NSSAI allowed by the first mobility management network element service.
  • the policy control network element before performing the slice authentication process, is not selected.
  • the mobility management network element selects the policy control network element according to the final NSSAI of the terminal device, thereby avoiding the slice authentication process.
  • the policy control network element selected before the right process does not support the slice after the slice authentication process, which leads to the problem of reselecting the policy control network element. Furthermore, the problem of reselection strategy can also be avoided, so that resources can be saved.
  • the first mobility management network element obtains the first policy associated with the allowed NSSAI from the policy control network element.
  • the first mobility management network element before the first slice performs slice authentication, receives the requested NSSAI from the terminal device in the registration process, and the requested NSSAI includes the terminal device requests to access the NSSAI.
  • the identification information of the slice; the first mobility management network element determines that the first slice in the slice requested for access needs to perform slice authentication, and then determines that the policy control network element is not selected in the registration process.
  • the first mobility management network element selects the policy control network element according to the allowed NSSAI, including: the first mobility management network element obtains the context of the terminal device from the second mobility management network element, The context of the terminal device does not include the information of the policy control network element.
  • the second mobility management network element is the network element that receives the requested NSSAI from the terminal device during the registration process, and the requested NSSAI includes the slice that the terminal device requests to access. Identification information; the first mobility management network element selects a policy control network element according to the context of the terminal device and the allowed NSSAI.
  • the allowed NSSAI when the first slice performs slice authentication successfully, includes the identification information of the first slice; or, when the first slice fails to perform slice authentication, the allowed NSSAI does not include Identification information of the first slice.
  • an embodiment of the present application provides a communication method, including: a first mobility management network element determines a first NSSAI, the first NSSAI includes the first allowed NSSAI and the pending NSSAI, or the first NSSAI includes the terminal equipment For the signed NSSAI, the pending NSSAI includes the identification information of the slice that needs to perform slice authentication among the slices that the terminal device requests to access; the first mobility management network element selects the policy control network element according to the first NSSAI.
  • the first mobility management network element controls the network element according to the allowed NSSAI and the pending NSSAI selection strategy, or according to the NSSAI selection strategy contracted by the terminal device, so that even if the subsequent allowed NSSAI changes,
  • the new allowed NSSAI is also determined from the allowed NSSAI and the pending NSSAI, or if it is determined from the NSSAI contracted by the terminal device, the policy control network element still supports the new allowed NSSAI, so that it does not
  • the policy control network element needs to be reselected, that is, the reselection of the policy control network element will not be triggered. Therefore, resource expenditure can be saved.
  • the first mobility management network element obtains the first policy associated with the first allowed NSSAI from the policy control network element.
  • the first mobility management network element determines the second allowed NSSAI, and the second allowed NSSAI includes the slice authentication performed in the pending NSSAI Identification information of the successful slice; the first mobility management network element obtains the second policy associated with the second allowed NSSAI from the policy control network element.
  • the first mobility management network element if the first mobility management network element cannot serve the second allowed NSSAI, the first mobility management network element sends the second policy to the terminal device.
  • the first mobility management network element determines the second allowed NSSAI, and the second allowed NSSAI includes the slice authentication performed in the pending NSSAI The identification information of the successful slice; if the first mobility management network element cannot serve the second allowed NSSAI, the first mobility management network element sets the first indication information in the context of the terminal device, and the first indication information is used to indicate the second 2.
  • the mobility management network element obtains the policy from the policy control network element.
  • an embodiment of the present application provides a communication method, including: a second mobility management network element obtains a context of a terminal device from a first mobility management network element, and the context of the terminal device includes identification information of the policy control network element and The first indication information; the second mobility management network element determines the allowed NSSAI; the second mobility management network element obtains the policy associated with the allowed NSSAI from the policy control network element according to the first indication information.
  • the first indication information is used to instruct the second mobility management network element to obtain the policy from the policy control network element.
  • an embodiment of the present application provides a communication method, including: after the first slice performs slice authentication, the first mobility management network element determines the allowed NSSAI, and the allowed NSSAI includes the slice that allows the terminal device to access
  • the first slice is the slice for which slice authentication needs to be performed among the slices that the terminal device requests to access;
  • the first mobility management network element obtains the first policy associated with the allowed NSSAI from the policy control network element;
  • the mobility management network element stores the first strategy and indication information in the context of the terminal device, and the indication information is used to instruct the second mobility management network element to send the first strategy to the terminal device.
  • the old mobility management network element obtains the new policy from the policy control network element and stores it in the context of the terminal device, and then the new mobility management network The element obtains the new strategy from the context of the terminal device and sends it to the terminal device, thereby solving the problem of how to trigger the new mobility management network element to send the updated strategy to the terminal device in a scenario where the mobility management network element changes.
  • the allowed NSSAI when the first slice performs slice authentication successfully, includes the identification information of the first slice; or, when the first slice fails to perform slice authentication, the allowed NSSAI does not include Identification information of the first slice.
  • an embodiment of the present application provides a communication method, including: after the first slice performs slice authentication, the first mobility management network element determines the allowed NSSAI, and the allowed NSSAI includes the slice that allows the terminal device to access
  • the first slice is the slice for which slice authentication needs to be performed among the slices that the terminal device requests to access; if the first mobility management network element cannot serve the allowed NSSAI, the first mobility management network element is in the terminal device’s
  • the identification information of the policy control network element and the first indication information are set in the context, and the first indication information is used to instruct the second mobility management network element to obtain the policy from the policy control network element.
  • the first mobility management network element sends the allowed NSSAI and second indication information to the terminal device, the second indication information is used to instruct the terminal device to register with the second mobility management network element according to the allowed NSSAI.
  • the old mobility management network element selects the strategy control network element and sets the identification information and an indication information of the strategy control network element in the context of the terminal device, and then The new mobility management network element obtains the identification information of the policy control network element from the context of the terminal device, and triggers the new mobility management network element to obtain a new policy from the policy control network element according to the first indication information, thereby solving In the scenario where the mobility management network element changes, how to trigger the new mobility management network element to send an updated strategy to the terminal device.
  • the allowed NSSAI when the first slice performs slice authentication successfully, includes the identification information of the first slice; or, when the first slice fails to perform slice authentication, the allowed NSSAI does not include Identification information of the first slice.
  • an embodiment of the present application provides a communication device, which may be a mobility management network element, or a chip used for a mobility management network element.
  • the device has the function of realizing any of the first aspect to the fifth aspect, or any embodiment of the first aspect or the fifth aspect. This function can be realized by hardware, or by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above-mentioned functions.
  • an embodiment of the present application provides a communication device including a processor and a memory; the memory is used to store computer-executable instructions, and when the device is running, the processor executes the computer-executable instructions stored in the memory to enable The device executes the method of any one of the above-mentioned first aspect to the fifth aspect, or any embodiment of the first aspect or the fifth aspect.
  • an embodiment of the present application provides a communication device, including a unit or means for performing any of the above-mentioned first aspect to the fifth aspect, or each step of any embodiment of the first aspect or the fifth aspect (means).
  • an embodiment of the present application provides a communication device, including a processor and an interface circuit, the processor is configured to communicate with other devices through the interface circuit, and execute any of the first to fifth aspects, or The method of any embodiment of the first or fifth aspect.
  • the processor includes one or more.
  • an embodiment of the present application provides a communication device, including a processor, configured to be connected to a memory, and configured to call a program stored in the memory to execute any of the above-mentioned first to fifth aspects, Or the method of any embodiment of the first or fifth aspect.
  • the memory can be located inside the device or outside the device.
  • the processor includes one or more.
  • an embodiment of the present application also provides a computer-readable storage medium having instructions stored in the computer-readable storage medium, which when run on a computer, cause a processor to execute the above-mentioned first to fifth aspects.
  • the embodiments of the present application also provide a computer program product.
  • the computer product includes a computer program. The method described in any embodiment of the five aspects is executed.
  • an embodiment of the present application also provides a chip system, including a processor, configured to execute any aspect of the first aspect to the fifth aspect, or any of the first aspect or the fifth aspect of the embodiment. The method described.
  • an embodiment of the present application also provides a communication system, including: a mobility management network element and a policy control network element.
  • the mobility management network element is configured to determine the allowed network slice selection auxiliary information NSSAI after the first slice performs slice authentication, and the allowed NSSAI includes identification information of the slice that is allowed to be accessed by the terminal device.
  • the first slice is the slice for which slice authentication needs to be performed among the slices that the terminal device requests to access; select the policy control network element according to the allowed NSSAI; and, obtain the data from the policy control network element.
  • the policy control network element is used to send the first policy to the mobility management network element.
  • an embodiment of the present application also provides a communication system, including: a first mobility management network element and a policy control network element.
  • the first mobility management network element is used to determine a first NSSAI, where the first NSSAI includes a first allowed NSSAI and a pending NSSAI, or the first NSSAI includes a contracted NSSAI of a terminal device, and the pending NSSAI
  • the NSSAI includes the identification information of the slice that needs to perform slice authentication among the slices that the terminal device requests to access; selects the policy control network element according to the first NSSAI; and, obtains it from the policy control network element The first policy associated with the first allowed NSSAI.
  • the policy control network element is configured to send the first policy to the first mobility management network element.
  • Figure 1A is a schematic diagram of a 5G network architecture based on a service-oriented architecture
  • Figure 1B is a schematic diagram of a 5G network architecture based on a point-to-point interface
  • Figure 2 is a schematic diagram of the NSSAA process in the prior art
  • FIG. 3A is a schematic flowchart of a communication method provided by this application.
  • FIG. 3B is a schematic flowchart of another communication method provided by this application.
  • FIG. 3C is a schematic flowchart of another communication method provided by this application.
  • FIG. 3D is a schematic flowchart of another communication method provided by this application.
  • FIG. 4 is a schematic flow diagram of another communication method provided by this application.
  • FIG. 5 is a schematic flowchart of another communication method provided by this application.
  • FIG. 6 is a schematic flowchart of another communication method provided by this application.
  • FIG. 7 is a schematic flowchart of another communication method provided by this application.
  • FIG. 8 is a schematic flowchart of another communication method provided by this application.
  • FIG. 9 is a schematic flowchart of another communication method provided by this application.
  • FIG. 10 is a schematic diagram of a communication device provided by this application.
  • FIG. 11 is a schematic diagram of a mobility management network element provided by this application.
  • FIG. 1A it is a schematic diagram of a fifth generation (5G) network architecture based on a service-oriented architecture.
  • the 5G network architecture shown in FIG. 1A may include three parts, namely a terminal equipment part, a data network (DN), and an operator network part.
  • DN data network
  • Operator network part The functions of some of the network elements are briefly introduced below.
  • the operator network may include one or more of the following network elements: Authentication Server Function (AUSF) network elements, network exposure function (NEF) network elements, policy control function (policy control) function, PCF) network element, unified data management (UDM) network element, unified database (Unified Data Repository, UDR), network storage function (Network Repository Function, NRF) network element, application function (AF) ) Network element, access and mobility management function (AMF) network element, session management function (SMF) network element, radio access network (RAN) and user plane function (user plane function, UPF) network element, network slice selection function (Network Slice Selection Function, NSSF) network element (not shown in the figure), etc.
  • AUSF Authentication Server Function
  • NEF network exposure function
  • policy control policy control
  • PCF policy control function
  • UDM unified data management
  • UDR Unified Data Repository
  • NRF Network Repository Function
  • AMF access and mobility management function
  • SMS session management function
  • RAN radio access network
  • UPF User Plan
  • Terminal device is a device with wireless transceiver function. It can be deployed on land, including indoor or outdoor, handheld or vehicle-mounted; it can also be deployed on the water (such as ships, etc.); it can also be deployed in the air ( For example, airplanes, balloons, satellites, etc.).
  • the terminal device may be a mobile phone (mobile phone), a tablet computer (pad), a computer with wireless transceiver function, a virtual reality (VR) terminal, an augmented reality (AR) terminal, an industrial control (industrial control) Wireless terminals in ), wireless terminals in self-driving, wireless terminals in remote medical, wireless terminals in smart grid, and wireless terminals in transportation safety , Wireless terminals in smart cities, wireless terminals in smart homes, user equipment (UE), etc.
  • a mobile phone mobile phone
  • a tablet computer pad
  • a computer with wireless transceiver function a virtual reality (VR) terminal, an augmented reality (AR) terminal, an industrial control (industrial control) Wireless terminals in ), wireless terminals in self-driving, wireless terminals in remote medical, wireless terminals in smart grid, and wireless terminals in transportation safety , Wireless terminals in smart cities, wireless terminals in smart homes, user equipment (UE), etc.
  • VR virtual reality
  • AR augmented reality
  • industrial control industrial control
  • the above-mentioned terminal device may establish a connection with the operator's network through an interface (such as N1, etc.) provided by the operator's network, and use services such as data and/or voice provided by the operator's network.
  • the terminal device can also access the DN through the operator's network, and use the operator's service deployed on the DN and/or the service provided by a third party.
  • the above-mentioned third party may be a service party other than the operator's network and terminal equipment, and may provide other services such as data and/or voice for the terminal equipment.
  • the specific form of expression of the above-mentioned third party can be determined according to actual application scenarios, and is not limited here.
  • RAN is a sub-network of an operator's network, and an implementation system between service nodes and terminal equipment in the operator's network.
  • the terminal device To access the operator's network, the terminal device first passes through the RAN, and then can be connected to the service node of the operator's network through the RAN.
  • RAN equipment is a type of equipment that provides wireless communication functions for terminal equipment.
  • RAN equipment is also called access network equipment.
  • RAN equipment includes but is not limited to: next-generation base stations (gnodeB, gNB) in 5G, evolved node B (evolved node B, eNB), radio network controller (RNC), node B (node B, NB), base station controller (BSC), base transceiver station (BTS), home base station (for example, home evolved nodeB, or home node B, HNB), baseband unit (BBU) , Transmission point (transmitting and receiving point, TRP), transmitting point (transmitting point, TP), mobile switching center, etc.
  • next-generation base stations gnodeB, gNB
  • 5G evolved node B (evolved node B, eNB), radio network controller (RNC), node B (node B, NB), base station controller (BSC), base transceiver station (BTS), home base station (for example, home evolved nodeB, or home node B, HNB), baseband unit (BBU) , Transmission point (transmitting and receiving
  • the AMF network element mainly performs functions such as mobility management and access authentication/authorization. In addition, it is also responsible for transferring user policies between UE and PCF.
  • the SMF network element mainly performs functions such as session management, execution of control policies issued by PCF, selection of UPF, and UE Internet Protocol (IP) address allocation.
  • functions such as session management, execution of control policies issued by PCF, selection of UPF, and UE Internet Protocol (IP) address allocation.
  • IP Internet Protocol
  • the UPF network element as the interface UPF with the data network, completes functions such as user plane data forwarding, session/stream-based billing statistics, and bandwidth limitation.
  • the UDM network element is mainly responsible for functions such as management of contract data and user access authorization.
  • UDR is mainly responsible for the access function of contract data, strategy data, application data and other types of data.
  • NEF network elements are mainly used to support the opening of capabilities and events.
  • the AF network element mainly conveys the requirements of the application side to the network side, for example, quality of service (QoS) requirements or user status event subscriptions.
  • QoS quality of service
  • the AF can be a third-party functional entity, or an application service deployed by an operator, such as an IP Multimedia Subsystem (IMS) voice call service.
  • IMS IP Multimedia Subsystem
  • the PCF network element is mainly responsible for policy control functions such as billing, QoS bandwidth guarantee and mobility management, and UE policy decision-making for the session and service flow levels.
  • the PCF connected to the AMF and the SMF corresponds to AM PCF (PCF for Access and Mobility Control) and SM PCF (PCF for Session Management) respectively, and may not be the same PCF entity in actual deployment scenarios.
  • the NRF network element can be used to provide the network element discovery function, and provide the network element information corresponding to the network element type based on the request of other network elements.
  • NRF also provides network element management services, such as network element registration, update, de-registration, and network element status subscription and push.
  • AUSF network element Mainly responsible for authenticating users to determine whether users or devices are allowed to access the network.
  • NSSF network elements are mainly used to select network slices and count users in the network slices.
  • a DN is a network located outside the operator's network.
  • the operator's network can access multiple DNs.
  • a variety of services can be deployed on the DN to provide terminal equipment with services such as data and/or voice.
  • DN is the private network of a smart factory.
  • the sensors installed in the workshop of the smart factory can be terminal devices.
  • a control server for the sensors is deployed in the DN, and the control server can provide services for the sensors.
  • the sensor can communicate with the control server, obtain instructions from the control server, and transmit the collected sensor data to the control server according to the instructions.
  • the DN is the internal office network of a company.
  • the mobile phones or computers of the employees of the company can be terminal devices, and the mobile phones or computers of the employees can access the information and data resources on the internal office network of the company.
  • Nausf, Nnef, Npcf, Nudm, Naf, Namf, Nsmf, N1, N2, N3, N4, and N6 are interface serial numbers.
  • the meaning of these interface serial numbers can be referred to the meaning defined in the 3rd generation partnership project (3rd generation partnership project, 3GPP) standard protocol, which is not limited here.
  • FIG. 1B it is a schematic diagram of a 5G network architecture based on a point-to-point interface.
  • FIG. 1A For the introduction of the functions of the network elements therein, reference may be made to the introduction of the functions of the corresponding network elements in FIG. 1A, which will not be repeated.
  • the main difference between Fig. 1B and Fig. 1A is that the interfaces between the various network elements in Fig. 1B are point-to-point interfaces, rather than service-oriented interfaces.
  • N7 The interface between PCF and SMF, which can be used to issue protocol data unit (protocol data unit, PDU) session granularity and service data flow granularity control strategy.
  • protocol data unit protocol data unit
  • PDU protocol data unit
  • N15 The interface between PCF and AMF, which can be used to issue UE policies and access control related policies.
  • N5 The interface between AF and PCF, which can be used for application service request issuance and network event reporting.
  • N4 The interface between SMF and UPF, which can be used to transfer information between the control plane and the user plane, including controlling the issuance of user-oriented forwarding rules, QoS control rules, traffic statistics rules, etc., and user-plane Information reported.
  • N11 The interface between SMF and AMF, which can be used to transfer PDU session tunnel information between RAN and UPF, transfer control messages sent to UE, and transfer radio resource control information sent to RAN.
  • N2 The interface between AMF and RAN, which can be used to transfer radio bearer control information from the core network side to the RAN.
  • N1 The interface between the AMF and the UE, which can be used to transfer QoS control rules to the UE.
  • N8 The interface between AMF and UDM, which can be used for AMF to obtain access and mobility management related subscription data and authentication data from UDM, and AMF to register UE current mobility management related information with UDM, etc.
  • N10 The interface between SMF and UDM, which can be used for SMF to obtain session management related subscription data from UDM, and SMF to register UE current session related information with UDM, etc.
  • N35 The interface between UDM and UDR, which can be used for UDM to obtain user subscription data information from UDR.
  • N36 The interface between the PCF and the UDR, which can be used for the PCF to obtain policy-related contract data and application data-related information from the UDR.
  • N12 The interface between AMF and AUSF, which can be used for AMF to initiate an authentication process to AUSF, where SUCI can be carried as a contract identifier;
  • N13 The interface between UDM and AUSF, which can be used for AUSF to obtain user authentication vector from UDM to execute the authentication process.
  • the aforementioned network elements or functions may be network elements in hardware devices, software functions running on dedicated hardware, or virtualization functions instantiated on a platform (for example, a cloud platform).
  • a platform for example, a cloud platform.
  • the foregoing network element or function may be implemented by one device, or jointly implemented by multiple devices, or may be a functional module in one device, which is not specifically limited in the embodiment of the present application.
  • the mobility management network elements, session management network elements, policy control network elements, application function network elements, access network equipment, network opening function network elements, user plane network elements, and network slice selection network elements in this application can be respectively shown in the figure.
  • the AMF, SMF, PCF, AF, RAN, NEF, UPF, NSSF in 1A or Figure 1B can also be future communications such as the 6th generation (6G) network with the above AMF, SMF, PCF, AF, RAN , NEF, UPF, and NSSF function network elements, this application is not limited to this.
  • this application uses mobility management network elements, session management network elements, policy control network elements, application function network elements, access network equipment, network open function network elements, user plane network elements, and network slice selection network elements respectively.
  • AMF Access Management Function
  • SMF Packet Control Function
  • PCF Packet Control Function
  • AF Application Function Function
  • RAN Radio Access Management Function
  • NEF Network Element Function
  • UPF User Plane Function
  • NSSF Network Slice Selection Function
  • 5G network slicing technology provides isolated network environments for different application scenarios by virtual independent logical networks on the same network infrastructure, so that different application scenarios can customize network functions and features according to their own needs, and can effectively guarantee the performance of different services. QoS requirements.
  • the goal of 5G network slicing is to organically combine terminal equipment, access network resources, core network resources, and network operation and maintenance and management systems, so as to provide independent operation and maintenance for different business scenarios or types of services.
  • the internet The internet.
  • 3GPP emphasizes that there is no mutual influence between network slices, for example, a large number of sudden meter reading services should not affect normal mobile broadband services.
  • 3GPP emphasizes that there is no mutual influence between network slices, for example, a large number of sudden meter reading services should not affect normal mobile broadband services.
  • relatively independent management and operation and maintenance between businesses are required, and tailor-made business functions and analysis capabilities are provided.
  • Instances of different types of services are deployed on different network slices, and different instances of the same service type can also be deployed on different network slices.
  • the selection process of the network slice will be triggered.
  • the selection process of the network slice depends on the user's subscription data, local configuration information, roaming agreement, operator's strategy, and so on. In the selection process of the network slice, the above parameters need to be considered comprehensively to select the best slice type for the UE.
  • the UE may provide a requested (Requested) NSSAI to the core network for the core network to select a network slice instance for the UE.
  • a UE when a UE needs to use network services, it first needs to register with the network.
  • the registration process is divided into the following scenarios:
  • the registration process may trigger the establishment of one or more PDU sessions. For example, in the scenario of mobility registration update, the UE has uplink data to send. At this time, the PDU session will be created during the registration process.
  • the network may also determine whether it needs to perform the network based on the NSSAI requested by the UE and the subscription data of the UE.
  • a slice-specific authentication and authorization (Network Slice Specific Authentication and Authorization, NSSAA) process which may also be referred to as a secondary authentication process or a network slice secondary authentication process.
  • step 201 the UE initiates a registration process and sends a Registration Request (Registration Request) message to the AMF.
  • the Registration Request message carries the requested NSSAI (Requested NSSAI).
  • the AMF executes the main authentication procedure of the permanent identity of the UE. After the procedure is successful, the AMF obtains the UE's subscription data from the UDM.
  • the subscription data includes the S-NSSAI subscribed by the UE and indication information corresponding to each S-NSSAI, and the indication information is used to indicate whether the S-NSSAI needs to perform NSSAA.
  • the contracted S-NSSAI refers to the slice type (HPLMN S-NSSAI) of the home domain network where the UE is located.
  • the S-NSSAI and indication information of the subscription in the subscription data of the UE are shown in Table 1.
  • Signed S-NSSAI Instruction information whether the S-NSSAI needs to execute NSSAA S-NSSAI-1 Yes S-NSSAI-2 no S-NSSAI-3 no
  • step 203 the AMF determines whether the NSSAA process needs to be executed.
  • the AMF determines that the S-NSSAI in the requested NSSAI needs to execute NSSAA can have two meanings:
  • the first type a certain S-NSSAI in the requested NSSAI belongs to the contracted S-NSSAI, and the contracted S-NSSAI needs to execute NSSAA, then the AMF determines that the S-NSSAI in the requested NSSAI needs to execute NSSAA.
  • the AMF determines whether the S-NSSAI that needs to perform the NSSAA process is included in the Requested NSSAI according to the UE's subscription data. If it is included, the AMF determines that the UE needs to perform the NSSAA process after this registration process. That is, it can be understood that the requested NSSAI includes the slice type (HPLMN S-NSSAI) of the home domain network.
  • the slice type HPLMN S-NSSAI
  • Example 1 For example, the Requested NSSAI carried by the UE is S-NSSAI-1 and S-NSSAI-2, where S-NSSAI-1 needs to execute the NSSAA process, and S-NSSAI-2 does not need to execute the NSSAA process.
  • the second type a certain S-NSSAI in the requested NSSAI can be mapped to a contracted S-NSSAI, and the contracted S-NSSAI needs to execute NSSAA, then the AMF determines that the S-NSSAI in the requested NSSAI needs to execute NSSAA.
  • AMF determines that a certain S-NSSAI included in the Requested NSSAI can be mapped to HPLMN S-NSSAI, and the HPLMN S-NSSAI needs to perform the NSSAA process, then the AMF determines that the UE is after this registration process The NSSAA process needs to be performed.
  • Example 2 For example, the Requested NSSAI carried by the UE is S-NSSAI-A and S-NSSAI-B, where S-NSSAI-A is mapped to S-NSSAI-1, and S-NSSAI-B is mapped to S-NSSAI-2, and S-NSSAI-1 needs to execute the NSSAA process, and S-NSSAI-2 does not need to execute the NSSAA process. Then the AMF determines that the UE needs to perform the NSSAA procedure on the S-NSSAI-1 after this registration procedure.
  • Step 204 The Registration Accept message sent by the AMF to the UE carries the allowed NSSAI (Allowed NSSAI), the pending NSSAI (Pending NSSAI), and the pending reason value.
  • Allowed NSSAI only includes S-NSSAI that does not require NSSAA
  • Pending NSSAI includes S-NSSAI that requires NSSAA
  • the pending reason value is waiting for NSSAA.
  • the cause value is used to indicate to the UE that those S-NSSAIs that require NSSAA are in a pending state.
  • Pending NSSAI can also be called pending NSSAI.
  • the embodiment of the present application takes Pending NSSAI referred to as pending NSSAI as an example for description.
  • Step 205 After the registration acceptance message is sent, the AMF executes the NSSAA procedure for the pending S-NSSAI.
  • AMF can have two meanings for executing NSSAA on the S-NSSAI in the pending NSSAI:
  • the first type a certain S-NSSAI in the pending NSSAI belongs to the contracted S-NSSAI, and the contracted S-NSSAI needs to perform NSSAA, then the AMF performs NSSAA on the S-NSSAI.
  • Pending NSSAI S-NSSAI-1
  • S-NSSAI-1 HPLMN S-NSSAI
  • AMF performs the NSSAA process on S-NSSAI-1.
  • the second type a certain S-NSSAI in the pending NSSAI is mapped to the contracted S-NSSAI, and the contracted S-NSSAI needs to perform NSSAA, then the AMF performs NSSAA for the contracted S-NSSAI.
  • step 205 is an optional step. When there is an S-NSSAI that needs to execute the NSSAA process, step 205 is executed. Otherwise, step 205 is not executed.
  • step 205 can be executed multiple times.
  • Step 206 After the execution of the NSSAA process is completed, the AMF determines whether the Allowed NSSAI of the UE needs to be updated according to the result of the process, and if necessary, sends a new Allowed NSSAI (new Allowed NSSAI) to the UE in the configuration update process.
  • the S-NSSAI will be added to the Allowed NSSAI in step 204 to generate a new Allowed NSSAI. If the execution of the NSSAA procedure fails, the AMF does not need to update the Allowed NSSAI of the UE.
  • This step 206 is an optional step. When the above step 205 is performed and the Allowed NSSAI of the UE needs to be updated, step 206 is performed.
  • the NSSAA procedure can be performed on the S-NSSAI, and the Allowed NSSAI of the UE can be updated.
  • the AMF and SMF initiate the PCF discovery and selection process respectively.
  • the PCF After the PCF is selected, it initiates access and mobility (Access and Mobility, AM) policy association establishment and session management (Session Management) , SM) policy association establishment process, obtain corresponding policies (including Policy and Charging Control (PCC) rules) and policy event reporting triggers (also known as policy control request triggers (Policy Control Request Triggers)) , And deploy execution strategies.
  • the SMF After receiving the SM policy, the SMF performs QoS mapping and sends the corresponding QoS information to the UPF, RAN and UE, thereby performing end-to-end QoS control.
  • the PCF or AMF can initiate the AM policy association update process, and the PCF or SMF can initiate the SM policy association update Process to update the corresponding strategy.
  • the PCF detects that the UE's subscription information is deleted, the UE is registered from the network, or other corresponding trigger conditions are met the PCF or AMF can initiate the AM policy association release process, and the PCF or SMF can initiate the SM policy association release process.
  • the AMF in the registration process of the UE, if the AMF decides to establish a policy association with the PCF, for example, when the AMF has not obtained the AM policy of the UE or the AMF does not have a legal AM policy, the AMF will select the PCF. If the AMF obtains the PCF ID (PCF ID) from the old AMF, it can directly locate the PCF. If the PCF ID cannot be located or the PCF ID is not obtained, the AMF will select a new PCF. In this process, the parameters used by the AMF to select the PCF include the subscription permanent identifier (SUPI), allowed NSSAI (Allowed NSSAI), and so on.
  • SUPI subscription permanent identifier
  • allowed NSSAI Allowed NSSAI
  • the AMF After the AMF selects the PCF, it initiates the AM policy association establishment process to request the PCF to obtain the AM policy. At the same time, the PCF returns the Policy Control Request Triggers to the AMF. When the AMF subsequently determines that the Policy Control Request Triggers is satisfied , Need to request the PCF to refresh the AM policy.
  • the trigger events included in Policy Control Request Triggers include but are not limited to the following: the tracking area of the UE changes, the UE enters/leaves the presence reporting area (PRA), and the UE's allowed NSSAI (Allowed NSSAI) When the change occurs, the public land mobile network (PLMN) of the UE changes.
  • the AMF selects the PCF according to the temporary Allowed NSSAI of the UE during the registration process . It is very likely that when the NSSAA process is successfully completed (the UE’s Allowed NSSAI is refreshed and new Allowed NSSAI is obtained), the PCF previously selected in the NSSAA process does not support the new Allowed NSSAI, it will cause the PCF to be reselected. Or it can be understood that AMF selected a PCF during the registration process. After the NSSAA process ends, AMF needs to reselect a PCF according to new Allowed NSSAI, that is, PCF reselection occurs.
  • the schemes adopted in the embodiments corresponding to Figs. 3A, 4, and 5 are summarized as follows: AMF does not select PCF before the NSSAA process, and after the NSSAA process ends, AMF according to the UE’s final Allowed NSSAI (ie new Allowed NSSAI) ) Select a suitable PCF and obtain policy information, so that the problems of PCF reselection and frequent refresh of the policy can be avoided. That is, the embodiments corresponding to FIG. 3A, FIG. 4, and FIG. 5 can solve the above-mentioned problem 1 and problem 2. Further, the embodiment corresponding to FIG. 3A is an overview of the solution, including a scene where the AMF does not change and a scene where the AMF changes.
  • the embodiments corresponding to FIG. 4 and FIG. 5 are specific examples.
  • the embodiment corresponding to FIG. 4 is applicable to a scenario where AMF does not change, that is, AMF supports both Allowed NSSAI and new Allowed NSSAI.
  • the embodiment corresponding to FIG. 5 is applicable to a scenario where AMF changes, that is, old AMF supports Allowed NSSAI but does not support new Allowed NSSAI, and new AMF supports new Allowed NSSAI.
  • the solutions adopted in the embodiments corresponding to Figures 3B, 6 and 7 are summarized as follows: Use Allowed NSSAI and Pending NSSAI to select PCF, or use contracted NSSAI to select PCF, so if NSSAA succeeds, the Allowed NSSAI is updated to new Allowed NSSAI, the PCF also supports new Allowed NSSAI, so that PCF reselection can be avoided. That is, the embodiments corresponding to FIG. 3B, FIG. 6 and FIG. 7 can solve the above-mentioned problem 1. Further, the embodiment corresponding to FIG. 3B is an overview of the solution, including a scene where the AMF does not change and a scene where the AMF changes. The embodiments corresponding to FIG. 6 and FIG.
  • the embodiment corresponding to FIG. 6 is applicable to a scenario where AMF does not change, that is, AMF supports both Allowed NSSAI and new Allowed NSSAI.
  • the embodiment corresponding to FIG. 7 is applicable to a scenario where AMF changes, that is, old AMF supports Allowed NSSAI but does not support new Allowed NSSAI, and new AMF supports new Allowed NSSAI.
  • the PCF is still selected according to the method of the prior art, that is, the Allowed NSSAI is used to select the PCF before the NSSAA process
  • the target scenario is: the PCF It also supports the new Allowed NSSAI obtained after the NSSAA process, that is, the PCF does not change and the AMF changes, that is, old AMF supports Allowed NSSAI, but does not support new Allowed NSSAI, and new AMF supports new Allowed NSSAI.
  • the old AMF obtains the AM policy from the PCF according to the Allowed NSSAI during the registration process and sends it to the UE
  • the old AMF obtains the updated AM policy from the PCF according to the new Allowed NSSAI after the NSSAA process and stores it in the context of the UE. Therefore, when the new AMF obtains the UE context from the old AMF, it can obtain the updated AM policy by the way, and the new AMF sends the updated AM policy to the UE.
  • the embodiment corresponding to FIG. 3C is an overview of the solution, and the embodiment corresponding to FIG. 8 is a specific example. Therefore, the embodiment corresponding to FIG. 3C and FIG. 8 can solve the above-mentioned problem 3.
  • PCF is still selected according to the method of the prior art, that is, Allowed NSSAI is used to select PCF before the NSSAA process
  • target scenario is: the PCF It also supports the new Allowed NSSAI obtained after the NSSAA process, that is, the PCF does not change and the AMF changes, that is, old AMF supports Allowed NSSAI, but does not support new Allowed NSSAI, and new AMF supports new Allowed NSSAI.
  • the old AMF obtains the AM policy from the PCF according to the Allowed NSSAI during the registration process and sends it to the UE, and the old AMF generates an indication message according to the new Allowed NSSAI after the NSSAA process and stores the indication information in the context of the UE.
  • the indication information is used to trigger the new AMF to obtain the updated AM policy from the PCF, so when the new AMF obtains the UE context from the old AMF, it can obtain the updated AM policy from the PCF according to the indication information in the UE context, and the new The AMF sends the updated AM policy to the UE.
  • the embodiment corresponding to Fig. 3D is an overview of the solution
  • the embodiment corresponding to Fig. 9 is a specific example. Therefore, the embodiment corresponding to FIG. 3D and FIG. 8 can solve the above-mentioned problem 3.
  • Allowed NSSAI in the embodiments of this application refers to the set of slices that the AMF determines to allow UE access before the NSSAA process
  • the new Allowed NSSAI refers to the slices that the AMF determines to allow UE access after the NSSAA process. Collection, unified description here.
  • the network slice may also be referred to as a slice, and the two have the same meaning.
  • Performing NSSAA on the S-NSSAI means performing NSSAA on the network slice corresponding to the S-NSSAI.
  • NSSAI is a unified description, and will not be repeated in the follow-up.
  • the present application provides a communication method.
  • the method includes the following steps:
  • Step 301a After the slice authentication is performed on the first slice, the first AMF determines the allowed NSSAI.
  • the allowed NSSAI includes the identification information of the slice that the UE is allowed to access.
  • the first slice is the slice that the UE requests to access. Slice for slice authentication.
  • the first slice here refers to the slice that needs to perform slice authentication in the requested NSSAI sent by the UE.
  • the first slice may be one or more slices.
  • the allowed NSSAI includes the identification information of the slice in the requested NSSAI after the slice authentication is successfully performed. For example, when the first slice performs slice authentication successfully, the allowed NSSAI includes the identification information of the first slice. When the first slice fails to perform slice authentication, the allowed NSSAI does not include the identification information of the first slice.
  • the allowed NSSAI here may refer to the aforementioned new Allowed NSSAI. Therefore, if the first slice performs slice authentication successfully, the first AMF may add the identification information of the first slice to the previously determined allowed NSSAI to obtain the new allowed NSSAI.
  • the allowed NSSAI also contains the identification information of the slices in the requested NSSAI that do not need to perform slice authentication.
  • the first AMF here refers to the changed AMF, that is, the new AMF.
  • no PCF is selected for the UE in the registration procedure of the UE.
  • Step 302a the first AMF selects a PCF based on the allowed NSSAI.
  • step 302a the following steps may be further included:
  • Step 303a the first AMF obtains the first policy associated with the allowed NSSAI from the PCF.
  • the first AMF sends a request message to the PCF, which contains the allowed NSSAI, and then the PCF determines the first policy according to the allowed NSSAI and sends it to the first AMF.
  • the first AMF receives the requested NSSAI from the UE during the registration process, and the first AMF determines the slice to be accessed. If the first slice in, needs to perform slice authentication, it is determined not to select PCF in the registration process.
  • the process for the first AMF to select the PCF is: the first AMF obtains the UE context from the second AMF, and the UE context does not include PCF information, then the first AMF according to the UE context and the allowed NSSAI , Select PCF. That is, when the first AMF determines that the context of the UE does not contain PCF information, it selects a PCF according to the allowed NSSAI.
  • the PCF is not selected before the slice authentication process is performed.
  • the AMF selects the PCF based on the final NSSAI of the UE, so as to avoid the occurrence of the slice authentication process before the selected PCF does not support slice authentication.
  • the slicing after the right process leads to the problem of PCF reselection. Furthermore, the problem of reselection strategy can also be avoided.
  • the first mobility management network element determines the allowed network slice selection auxiliary information NSSAI.
  • the allowed NSSAI includes the identification information of the slice that the terminal device is allowed to access, and the first slice is the terminal device Among the slices for which access is requested, the slice for performing slice authentication is required; the first mobility management network element selects a policy control network element according to the allowed NSSAI; wherein, the first mobility management network element serves the slice corresponding to the allowed NSSAI.
  • the first mobility management network element obtains the first policy associated with the allowed NSSAI from the policy control network element.
  • the first mobility management network element before the first slice performs slice authentication, receives the requested NSSAI from the terminal device in the registration process, and the requested NSSAI includes the terminal device requests to access the NSSAI.
  • the identification information of the slice; the first mobility management network element determines that the first slice in the slice requested for access needs to perform slice authentication, and then determines that the policy control network element is not selected in the registration process.
  • the first mobility management network element selects the policy control network element according to the allowed NSSAI, including: the first mobility management network element obtains the context of the terminal device from the second mobility management network element, The context of the terminal device does not include the information of the policy control network element.
  • the second mobility management network element is the network element that receives the requested NSSAI from the terminal device during the registration process, and the requested NSSAI includes the slice that the terminal device requests to access. Identification information; the first mobility management network element selects a policy control network element according to the context of the terminal device and the allowed NSSAI.
  • the allowed NSSAI when the first slice performs slice authentication successfully, includes the identification information of the first slice; or, when the first slice fails to perform slice authentication, the allowed NSSAI does not include Identification information of the first slice.
  • the present application provides yet another communication method.
  • the method includes the following steps:
  • Step 301b the first AMF determines the first NSSAI, the first NSSAI includes the first allowed NSSAI and the pending NSSAI, or the first NSSAI includes the NSSAI subscribed by the UE, and the pending NSSAI includes the required execution in the slice that the UE requests to access The identification information of the slice for slice authentication.
  • this step is executed before slice authentication is performed on the slice corresponding to the pending NSSAI.
  • the first AMF here refers to the AMF before the change, that is, the old AMF.
  • the first allowed NSSAI here refers to the allowed NSSAI determined in the registration process.
  • Step 302b the first AMF selects a PCF according to the first NSSAI.
  • the above solution can be executed in the registration procedure of the UE.
  • the first AMF selects the PCF based on the allowed NSSAI and pending NSSAI, or selects the PCF based on the UE’s contracted NSSAI, so that even if the subsequent allowed NSSAI changes, the new allowed NSSAI will be changed from the allowed NSSAI and NSSAI.
  • the PCF Determined from the pending NSSAI, or determined from the NSSAI subscribed by the UE, the PCF still supports the newly allowed NSSAI, so there is no need to reselect the PCF, that is, it will not trigger the reselection of the PCF . Therefore, resource expenditure can be saved.
  • step 302b the following steps may be further included:
  • Step 303b the first AMF obtains the first policy associated with the first allowed NSSAI from the PCF.
  • the first AMF sends a request message to the PCF, which contains the first allowed NSSAI, and then the PCF determines the first policy according to the first allowed NSSAI and sends it to the first AMF.
  • step 302b the following steps may be further included:
  • Step 304b After performing slice authentication on the slice corresponding to the pending NSSAI, the first AMF determines the second allowed NSSAI.
  • the second allowed NSSAI includes the identification information of the slice in the pending NSSAI that successfully performs slice authentication.
  • the second permitted NSSAI also includes the above-mentioned first permitted NSSAI.
  • Step 305b the first AMF obtains the second policy associated with the second allowed NSSAI from the PCF.
  • the first AMF sends a request message to the PCF, which contains the second allowed NSSAI, and then the PCF determines the second policy according to the second allowed NSSAI and sends it to the first AMF.
  • the first AMF may send the second policy to the UE. That is, the first AMF (that is, the old AMF) obtains the new strategy (that is, the second strategy) from the PCF and sends it to the UE.
  • the first AMF determines the second allowed NSSAI, and the second allowed NSSAI includes the pending NSSAI that performs slice authentication successfully.
  • the identification information of the slice If the first AMF cannot serve the second allowed NSSAI, the first AMF sets the first indication information in the context of the UE, and the first indication information is used to instruct the second AMF (that is, the new AMF) to obtain a policy from the PCF.
  • the second AMF obtains the context of the UE from the first AMF, it obtains a new policy (may be referred to as the third policy) from the PCF according to the first indication information therein, and then the second AMF sends the third policy to the UE . That is, in this method, the second AMF (that is, the new AMF) obtains the new strategy (that is, the third strategy) from the PCF and sends it to the UE.
  • the second AMF that is, the new AMF
  • the new strategy that is, the third strategy
  • the first mobility management network element determines the first NSSAI, the first NSSAI includes the first allowed NSSAI and the pending NSSAI, or the first NSSAI includes the NSSAI subscribed by the terminal device, and the pending NSSAI includes the slice that the terminal device requests to access The identification information of the slice that needs to perform slice authentication; the first mobility management network element selects the policy control network element according to the first NSSAI.
  • the first mobility management network element obtains the first policy associated with the first allowed NSSAI from the policy control network element.
  • the first mobility management network element determines the second allowed NSSAI, and the second allowed NSSAI includes the slice authentication performed in the pending NSSAI Identification information of the successful slice; the first mobility management network element obtains the second policy associated with the second allowed NSSAI from the policy control network element.
  • the first mobility management network element if the first mobility management network element cannot serve the second allowed NSSAI, the first mobility management network element sends the second policy to the terminal device.
  • the first mobility management network element determines the second allowed NSSAI, and the second allowed NSSAI includes the slice authentication performed in the pending NSSAI The identification information of the successful slice; if the first mobility management network element cannot serve the second allowed NSSAI, the first mobility management network element sets the first indication information in the context of the terminal device, and the first indication information is used to indicate the second 2.
  • the mobility management network element obtains the policy from the policy control network element.
  • the second mobility management network element obtains the context of the terminal device from the first mobility management network element, the context of the terminal device includes the identification information of the policy control network element and the first indication information; the second mobility management network element determines the allowed NSSAI ; The second mobility management network element obtains the policy associated with the allowed NSSAI from the policy control network element according to the first indication information.
  • the first indication information is used to instruct the second mobility management network element to obtain the policy from the policy control network element.
  • the present application provides yet another communication method.
  • the method includes the following steps:
  • Step 301c After the slice authentication is performed on the first slice, the first AMF determines the allowed NSSAI.
  • the allowed NSSAI includes the identification information of the slice that the UE is allowed to access.
  • the first slice is the slice that the UE requests to access. Slice for slice authentication.
  • the first slice here refers to the slice that needs to perform slice authentication in the requested NSSAI sent by the UE.
  • the first slice may be one or more slices.
  • the allowed NSSAI contains the identification information of the slices in the requested NSSAI that do not need to perform slice authentication.
  • the first AMF here refers to the AMF before the change, that is, the old AMF.
  • Step 302c the first AMF obtains the first policy associated with the allowed NSSAI from the PCF.
  • the PCF here is selected in the registration process of the UE, that is, selected before the slice authentication is performed on the first slice.
  • Step 303c The first AMF stores the first policy and indication information in the context of the UE, and the indication information is used to instruct the second AMF to send the first policy to the UE.
  • the second AMF After obtaining the context of the UE from the first AMF, the second AMF sends the first policy to the UE according to the indication information therein.
  • the second AMF refers to the changed AMF, which is also called the new AMF.
  • the old AMF obtains the new policy from the PCF and stores it in the context of the UE, and then the new AMF obtains the new policy from the context of the UE and sends it to the UE. It solves the problem of how to trigger a new AMF to send an updated policy to the UE in a scenario where the AMF changes.
  • the allowed NSSAI includes the identification information of the first slice, or is understood as The identification information is added to the permitted NSSAI, and a new permitted NSSAI is obtained.
  • the allowed NSSAI does not include the identification information of the first slice.
  • the first mobility management network element determines the allowed NSSAI.
  • the allowed NSSAI includes the identification information of the slice that the terminal device is allowed to access.
  • the first slice is the slice that the terminal device requests to access.
  • the first mobility management network element acquires the first policy associated with the allowed NSSAI from the policy control network element; the first mobility management network element stores the first policy and the first policy in the context of the terminal device. Instruction information, the instruction information is used to instruct the second mobility management network element to send the first policy to the terminal device.
  • the allowed NSSAI when the first slice performs slice authentication successfully, includes the identification information of the first slice; or, when the first slice fails to perform slice authentication, the allowed NSSAI does not include Identification information of the first slice.
  • the present application provides yet another communication method.
  • the method includes the following steps:
  • Step 301d After the first slice performs slice authentication, the first AMF determines the allowed NSSAI.
  • the allowed NSSAI includes the identification information of the slice to which the UE is allowed to access, and the first slice is the slice for which slice authentication needs to be performed among the slices that the UE requests to access.
  • the first AMF here refers to the AMF before the change, that is, the old AMF.
  • Step 302d If the first AMF cannot serve the allowed NSSAI, the first AMF sets the identification information of the PCF and the first indication information in the context of the UE, and the first indication information is used to instruct the second AMF to obtain a policy from the PCF.
  • Step 303d The first AMF sends the allowed NSSAI and second indication information to the UE, where the second indication information is used to instruct the UE to register with the second AMF according to the allowed NSSAI.
  • the second AMF obtains the UE context from the first AMF, which contains the identification information of the PCF and the first indication information.
  • the second AMF obtains the new policy from the PCF according to the first indication information and sends it to UE.
  • the old AMF selects the PCF and sets the identification information of the PCF and an indication information in the context of the UE, and then the new AMF obtains the identification information of the PCF from the context of the UE. And according to the first indication information, the new AMF is triggered to obtain a new policy from the PCF, thereby solving the problem of how to trigger the new AMF to send the updated policy to the UE in a scenario where the AMF changes.
  • the allowed NSSAI includes the identification information of the first slice, or is understood as The identification information is added to the permitted NSSAI, and a new permitted NSSAI is obtained.
  • the allowed NSSAI does not include the identification information of the first slice.
  • the first mobility management network element determines the allowed NSSAI.
  • the allowed NSSAI includes the identification information of the slice that the terminal device is allowed to access.
  • the first slice is the slice that the terminal device requests to access. If the first mobility management network element cannot serve the allowed NSSAI, the first mobility management network element sets the identification information and first indication information of the policy control network element in the context of the terminal device, The first indication information is used to instruct the second mobility management network element to obtain a policy from the policy control network element. ;
  • the first mobility management network element sends the allowed NSSAI and second indication information to the terminal device, the second indication information is used to instruct the terminal device to register with the second mobility management network element according to the allowed NSSAI.
  • the allowed NSSAI when the first slice performs slice authentication successfully, includes the identification information of the first slice; or, when the first slice fails to perform slice authentication, the allowed NSSAI does not include Identification information of the first slice.
  • FIG. 4 it is a schematic flowchart of another communication method provided by this application. This embodiment is aimed at a scenario where AMF does not change before and after the NSSAA process.
  • the method includes the following steps:
  • Step 401 The UE initiates a registration process, and sends a Registration Request (Registration Request) message to the AMF.
  • the Registration Request message carries the requested NSSAI (Requested NSSAI).
  • the AMF executes the main authentication procedure of the permanent identity of the UE. After the procedure is successful, the AMF obtains the UE's subscription data from the UDM.
  • the subscription data includes the S-NSSAI subscribed by the UE and indication information corresponding to each S-NSSAI, and the indication information is used to indicate whether the S-NSSAI needs to perform NSSAA.
  • the S-NSSAI and indication information of the subscription in the subscription data of the UE are shown in Table 2.
  • Signed S-NSSAI Instruction information whether the S-NSSAI needs to execute NSSAA S-NSSAI-1 Yes S-NSSAI-2 Yes S-NSSAI-3 no
  • the AMF can call the UDM service operation Nudm_SDM_Get to obtain the UE's subscription data, and the UDM sends the UE's subscription data to the AMF through Nudm_SDM_Get response.
  • step 403 the AMF determines whether the NSSAA process needs to be executed, and if the NSSAA process needs to be executed, it determines not to select the PCF first.
  • the AMF determines that the S-NSSAI in the requested NSSAI needs to execute NSSAA can have two meanings:
  • the first type a certain S-NSSAI in the requested NSSAI belongs to the contracted S-NSSAI, and the contracted S-NSSAI needs to execute NSSAA, then the AMF determines that the S-NSSAI in the requested NSSAI needs to execute NSSAA.
  • the AMF determines whether the S-NSSAI that needs to perform the NSSAA process is included in the Requested NSSAI according to the UE's subscription data. If it is included, the AMF determines that the UE needs to perform the NSSAA process after this registration process. That is, it can be understood that the requested NSSAI includes the slice type (HPLMN S-NSSAI) of the home domain network.
  • the slice type HPLMN S-NSSAI
  • the Requested NSSAI carried by the UE includes S-NSSAI-1, S-NSSAI-2, and S-NSSAI-3, where S-NSSAI-1 and S-NSSAI-2 need to perform the NSSAA process, S-NSSAI-3 There is no need to perform the NSSAA process, the AMF determines that the UE needs to perform the NSSAA process after this registration process.
  • the second type a certain S-NSSAI in the requested NSSAI can be mapped to a contracted S-NSSAI, and the contracted S-NSSAI needs to execute NSSAA, then the AMF determines that the S-NSSAI in the requested NSSAI needs to execute NSSAA.
  • AMF determines that a certain S-NSSAI included in the Requested NSSAI can be mapped to HPLMN S-NSSAI, and the HPLMN S-NSSAI needs to perform the NSSAA process, then the AMF determines that the UE is after this registration process The NSSAA process needs to be performed.
  • Example 2 For example, the Requested NSSAI carried by the UE is S-NSSAI-A, S-NSSAI-B, and S-NSSAI-C, where S-NSSAI-A is mapped to S-NSSAI-1, and S-NSSAI-B is mapped to S-NSSAI-B.
  • NSSAI-2 mapping, S-NSSAI-C and S-NSSAI-3 mapping, and S-NSSAI-1 and S-NSSAI-2 need to perform the NSSAA process, and S-NSSAI-3 does not need to perform the NSSAA process.
  • the AMF determines that the UE needs to perform the NSSAA procedure on S-NSSAI-1 and S-NSSAI-2 after this registration procedure.
  • Step 404 The Registration Accept message sent by the AMF to the UE carries one or more of allowed NSSAI (Allowed NSSAI), pending NSSAI (Pending NSSAI), and rejected NSSAI (Rejected NSSAI).
  • allowed NSSAI Allowed NSSAI
  • pending NSSAI Pending NSSAI
  • rejected NSSAI Rejected NSSAI
  • the AMF may also send a pending cause value to the UE: waiting for NSSAA, and the cause value is used to indicate to the UE that those S-NSSAIs that require NSSAA are in a pending state.
  • the AMF may also send a rejection reason value to the UE: the current area is not available.
  • Allowed NSSAI includes S-NSSAI in the requested NSSAI that does not require NSSAA, Pending NSSAI includes S-NSSAI in the requested NSSAI that requires NSSAA, and Rejected NSSAI includes the UE in the requested NSSAI that is not available in the current area. S-NSSAI.
  • Allowed NSSAI S-NSSAI-3
  • Pending NSSAI S-NSSAI-1+S-NSSAI-2
  • the reason value to be determined waiting for NSSAA.
  • Rejected NSSAI is empty.
  • Allowed NSSAI S-NSSAI-C
  • Pending NSSAI S-NSSAI-A+S-NSSAI-C
  • the AMF stores the Allowed NSSAI in this step in the context of the UE on the AMF.
  • Step 405 After the registration acceptance message is sent, the AMF executes the NSSAA procedure for the pending S-NSSAI.
  • AMF can have two meanings for executing NSSAA on the S-NSSAI in the pending NSSAI:
  • the first type a certain S-NSSAI in the pending NSSAI belongs to the contracted S-NSSAI, and the contracted S-NSSAI needs to perform NSSAA, then the AMF performs NSSAA on the S-NSSAI.
  • the second type a certain S-NSSAI in the pending NSSAI is mapped to the contracted S-NSSAI, and the contracted S-NSSAI needs to perform NSSAA, then the AMF performs NSSAA for the contracted S-NSSAI.
  • NSSAA result of S-NSSAI-1 is NSSAA success
  • NSSAA result of S-NSSAI-A is NSSAA success
  • access to S-NSSAI-A is allowed
  • NSSAA result of S-NSSAI-1 is NSSAA Failure
  • NSSAA result of S-NSSAI-A is NSSAA failure
  • access to S-NSSAI-A is denied.
  • NSSAA result of S-NSSAI-2 is NSSAA success
  • NSSAA result of S-NSSAI-B is NSSAA success
  • access to S-NSSAI-B is allowed
  • NSSAA result of S-NSSAI-2 is NSSAA Failure
  • NSSAA failure can also be understood as the result of NSSAA of S-NSSAI-B as NSSAA failure, and access to S-NSSAI-B is denied.
  • This step 405 is an optional step. When there is an S-NSSAI that needs to execute the NSSAA process, step 405 is executed. Otherwise, step 405 is not executed.
  • step 405 can be executed multiple times.
  • Step 406 After the execution of the NSSAA process is completed, the AMF determines whether the Allowed NSSAI of the UE needs to be updated according to the result of the process. If there is a successful NSSAA slice, the S-NSSAI corresponding to the successful NSSAA slice is added to step 404 and sent to In the Allowed NSSAI of the UE, a new Allowed NSSAI (new Allowed NSSAI) is obtained.
  • the AMF also determines Rejected NSSAI, and the Rejected NSSAI includes the S-NSSAI corresponding to the NSSAA failed slice in the Pending NSSAI.
  • the AMF is stored in the context of the UE in accordance with Allowed in step 404 NSSAI, add S-NSSAI-1 to the Allowed NSSAI of the UE, that is, the Allowed NSSAI is updated to: S-NSSAI-1+S-NSSAI-3. And generate a rejected NSSAI.
  • the rejected NSSAI includes S-NSSAI-2. Optionally, it also generates a rejection reason value: NSSAA failed.
  • the AMF is stored according to the Allowed in the context of the UE in step 404.
  • NSSAI adding S-NSSAI-A to the Allowed NSSAI of the UE, that is, the Allowed NSSAI is updated to: S-NSSAI-A+S-NSSAI-C.
  • the rejected NSSAI includes S-NSSAI-B.
  • it also generates a rejection reason value: NSSAA failed.
  • Step 407 If the current AMF can continue to serve the UE, the AMF requests the NRF to find a suitable PCF according to the new Allowed NSSAI determined in step 406.
  • the AMF calls the NRF service operation Nnrf_NFDiscovery_Request, which carries the SUPI of the UE and the new Allowed NSSAI determined in step 406.
  • the current AMF can continue to serve the UE means that the AMF can support the new Allowed NSSAI determined in step 406. So AMF does not need to be changed.
  • Step 408 The NRF determines a suitable PCF, and sends the PCF ID (PCF ID) to the AMF.
  • NEF determines the appropriate PCF based on SUPI and new Allowed NSSAI.
  • NRF can return Nnrf_NFDiscovery_Response to AMF, carrying PCF ID.
  • Step 409 Based on the PCF ID returned by the NRF, the AMF sends an AM Policy Association Establishment (AM Policy Association) request to the PCF.
  • AM Policy Association AM Policy Association
  • AMF calls the service operation of PCF: Npcf_AMPolicyControl_Create, which carries SUPI, new Allowed NSSAI.
  • Step 410 The PCF sends an AM policy (AM policy for new Allowed NSSAI) and a policy control request trigger (Policy Control Request Triggers) generated based on the new Allowed NSSAI to the AMF.
  • AM policy AM policy for new Allowed NSSAI
  • Policy Control Request Triggers Policy Control Request Triggers
  • PCF returns Npcf_AMPolicyControl_Create Response to AMF, which carries AM policy for new Allowed NSSAI and Policy Control Request Triggers.
  • the AM policy is generated by the PCF according to the new Allowed NSSAI, and the AM policy of this step can also be called the AM policy for new Allowed NSSAI.
  • AM policy includes but is not limited to: air interface access technology/spectrum selection priority index (Index to RAT/Frequency Selection Priority, RFSP index), user aggregate maximum bit rate (Aggregate Maximum Bit Rate, UE-AMBR), and service area restriction ( Service Area Restrictions).
  • Policy Control Request Triggers refers to policy control request triggers, or policy event reporting triggers.
  • the AMF can initiate the AM policy association update process, thereby Update the corresponding strategy.
  • step 410 it further includes step 410a and step 410b:
  • Step 410a Based on the PCF ID returned by the NRF, the AMF sends a UE Policy Association Establishment (UE Policy Association) request to the PCF.
  • UE Policy Association UE Policy Association
  • AMF calls PCF's servicing operation: Npcf_UEPolicyControl Create Request, which carries SUPI.
  • Step 410b the PCF sends a UE policy (UE policy) to the AMF.
  • UE policy UE policy
  • PCF returns Npcf_UEPolicyControl Create Response to AMF, which carries UE policy.
  • the UE policy includes but is not limited to: UE access selection policy, such as Access Network Discovery&Selection Policy (ANDSP), and PDU Session Selection related policies, such as UE routing policy (UE Route Selection Policy, URSP)).
  • UE access selection policy such as Access Network Discovery&Selection Policy (ANDSP)
  • PDU Session Selection related policies such as UE routing policy (UE Route Selection Policy, URSP)).
  • UE routing policy UE Route Selection Policy, URSP
  • Step 411 The AMF sends a configuration update request (configuration update request) message to the UE, which carries the new Allowed NSSAI, and is based on the AM policy and the UE policy generated by the new Allowed NSSAI.
  • the configuration update request message may also carry the rejected NSSAI.
  • the AMF determines that it needs to perform the NSAA process on some S-NSSAI in the Requested NSSAI, the AMF does not select the PCF first, but waits for the end of the NSSAA process, the AMF according to the UE’s final Allowed NSSAI (new Allowed NSSAI) selects the appropriate PCF and obtains the AM policy.
  • This method can avoid the problems of PCF reselection and frequent refresh of policies.
  • FIG. 5 it is a schematic flowchart of another communication method provided by this application. This embodiment is aimed at a scenario where AMF changes before and after the NSSAA process.
  • the method includes the following steps:
  • Step 501 The UE initiates a registration process, and sends a Registration Request (Registration Request) message to the old AMF (old AMF), and the Registration Request message carries the requested NSSAI (Requested NSSAI).
  • the old AMF here refers to the AMF selected by the access network to serve the UE during the registration process, or can be understood as the AMF that serves the UE for the first time in the registration process.
  • the old AMF involved in the present invention may also be called initial AMF (initial AMF) or current AMF (serving AMF).
  • the old AMF executes the primary authentication procedure of the permanent identity of the UE. After the procedure is successful, the old AMF obtains the UE's subscription data from the UDM.
  • the subscription data includes the S-NSSAI subscribed by the UE and indication information corresponding to each S-NSSAI, and the indication information is used to indicate whether the S-NSSAI needs to perform NSSAA.
  • the S-NSSAI and indication information of the subscription in the subscription data of the UE are as shown in Table 2 above.
  • the old AMF can call the servicing operation Nudm_SDM_Get of UDM to obtain the subscription data of the UE, and the UDM sends the subscription data of the UE to the old AMF through Nudm_SDM_Get response.
  • step 503 the old AMF determines whether the NSSAA process needs to be executed, and if the NSSAA process needs to be executed, it determines not to select PCF first.
  • the method by which the old AMF determines that the S-NSSAI in the requested NSSAI needs to execute the NSSAA can have two meanings:
  • the first type a certain S-NSSAI in the requested NSSAI belongs to the contracted S-NSSAI, and the contracted S-NSSAI needs to execute NSSAA, then old AMF determines that the S-NSSAI in the requested NSSAI needs to execute NSSAA.
  • the old AMF determines whether the S-NSSAI that needs to perform the NSSAA process is included in the Requested NSSAI based on the UE's subscription data. If it does, the old AMF determines that the UE needs to perform the NSSAA process after this registration process. That is, it can be understood that the requested NSSAI includes the slice type (HPLMN S-NSSAI) of the home domain network.
  • the Requested NSSAI carried by the UE includes S-NSSAI-1, S-NSSAI-2, and S-NSSAI-3, where S-NSSAI-1 and S-NSSAI-2 need to perform the NSSAA process, S-NSSAI-3 There is no need to perform the NSSAA process, the old AMF determines that the UE needs to perform the NSSAA process after this registration process.
  • the second type a certain S-NSSAI in the requested NSSAI can be mapped to a contracted S-NSSAI, and the contracted S-NSSAI needs to execute NSSAA, then old AMF determines that the S-NSSAI in the requested NSSAI needs to execute NSSAA.
  • the old AMF judges that a certain S-NSSAI included in the Requested NSSAI can be mapped to the HPLMN S-NSSAI based on the UE’s subscription data, and the HPLMN S-NSSAI needs to perform the NSSAA process, then the old AMF determines that the UE is registered this time After the process, the NSSAA process needs to be executed.
  • Example 2 For example, the Requested NSSAI carried by the UE is S-NSSAI-A, S-NSSAI-B, and S-NSSAI-C, where S-NSSAI-A is mapped to S-NSSAI-1, and S-NSSAI-B is mapped to S-NSSAI-B.
  • NSSAI-2 mapping, S-NSSAI-C and S-NSSAI-3 mapping, and S-NSSAI-1 and S-NSSAI-2 need to perform the NSSAA process, and S-NSSAI-3 does not need to perform the NSSAA process.
  • the old AMF determines that the UE needs to perform the NSSAA process on S-NSSAI-1 and S-NSSAI-2 after this registration process.
  • NSSAA result of S-NSSAI-1 is NSSAA success
  • NSSAA result of S-NSSAI-A is NSSAA success
  • access to S-NSSAI-A is allowed
  • NSSAA result of S-NSSAI-1 is NSSAA Failure
  • NSSAA result of S-NSSAI-A is NSSAA failure
  • access to S-NSSAI-A is denied.
  • NSSAA result of S-NSSAI-2 is NSSAA success
  • NSSAA result of S-NSSAI-B is NSSAA success
  • access to S-NSSAI-B is allowed
  • NSSAA result of S-NSSAI-2 is NSSAA Failure
  • NSSAA failure can also be understood as the result of NSSAA of S-NSSAI-B as NSSAA failure, and access to S-NSSAI-B is denied.
  • Step 504 The Registration Accept message sent by the old AMF to the UE carries one or more of allowed NSSAI (Allowed NSSAI), pending NSSAI (Pending NSSAI), and rejected NSSAI (Rejected NSSAI).
  • allowed NSSAI Allowed NSSAI
  • pending NSSAI Pending NSSAI
  • rejected NSSAI Rejected NSSAI
  • Allowed NSSAI includes S-NSSAI in the requested NSSAI that does not require NSSAA, Pending NSSAI includes S-NSSAI in the requested NSSAI that requires NSSAA, and Rejected NSSAI includes the UE in the requested NSSAI that is not available in the current area. S-NSSAI.
  • Allowed NSSAI S-NSSAI-3
  • Pending NSSAI S-NSSAI-1+S-NSSAI-2
  • the reason value to be determined waiting for NSSAA.
  • Rejected NSSAI is empty.
  • Allowed NSSAI S-NSSAI-C
  • Pending NSSAI S-NSSAI-A+S-NSSAI-C
  • the old AMF stores the Allowed NSSAI in this step in the context of the UE on the old AMF.
  • Step 505 After the registration acceptance message is sent, the old AMF executes the NSSAA process for the pending S-NSSAI.
  • the old AMF performing NSSAA for the S-NSSAI in the pending NSSAI can have two meanings:
  • the first type a certain S-NSSAI in the pending NSSAI belongs to the contracted S-NSSAI, and the contracted S-NSSAI needs to perform NSSAA, then the old AMF performs NSSAA on the S-NSSAI.
  • the second type a certain S-NSSAI in the pending NSSAI is mapped to the contracted S-NSSAI, and the contracted S-NSSAI needs to perform NSSAA, then old AMF performs NSSAA for the contracted S-NSSAI.
  • step 505 is an optional step. When there is an S-NSSAI that needs to execute the NSSAA process, step 505 is executed. Otherwise, step 505 is not executed.
  • step 505 can be executed multiple times.
  • Step 506 After the execution of the NSSAA process is completed, the old AMF determines whether the Allowed NSSAI of the UE needs to be updated according to the result of the process. If there is a successful NSSAA slice, the S-NSSAI corresponding to the successful NSSAA slice is added to step 504 and sent In the Allowed NSSAI of the UE, a new Allowed NSSAI (new Allowed NSSAI) is obtained.
  • the old AMF also determines Rejected NSSAI, and the Rejected NSSAI includes the S-NSSAI corresponding to the NSSAA failed slice in the Pending NSSAI.
  • the AMF is based on the Allowed NSSAI stored in the context of the UE in step 504 , Add S-NSSAI-1 to the Allowed NSSAI of the UE, that is, the Allowed NSSAI is updated to: S-NSSAI-1+S-NSSAI-3. And generate a rejected NSSAI.
  • the rejected NSSAI includes S-NSSAI-2. Optionally, it also generates a rejection reason value: NSSAA failed.
  • the old AMF is based on the Allowed stored in the context of the UE in step 504.
  • NSSAI adding S-NSSAI-A to the Allowed NSSAI of the UE, that is, the Allowed NSSAI is updated to: S-NSSAI-A+S-NSSAI-C.
  • the rejected NSSAI includes S-NSSAI-B.
  • it also generates a rejection reason value: NSSAA failed.
  • Step 507 If the current AMF (ie, old AMF) cannot continue to serve the UE, the old AMF needs to trigger the AMF reallocation.
  • the old AMF sends a configuration update request message to the UE, which carries new Allowed NSSAI and indication information.
  • the indication information is used to instruct the UE to use new Allowed NSSAI as the requested NSSAI to initiate the registration process immediately after receiving the new Allowed NSSAI.
  • the current AMF cannot continue to serve the UE means that the current AMF does not support the new Allowed NSSAI determined in step 506, so the AMF needs to be changed.
  • Step 508 The UE initiates a registration process according to the new Allowed NSSAI and the indication information.
  • the UE registers with a new AMF (new AMF), that is, the new AMF serves the UE, where the new AMF supports the slice indicated by the new Allowed NSSAI.
  • new AMF new AMF
  • the UE sends a Requested NSSAI during the registration process, and the Requested NSSAI includes the new Allowed NSSAI in step 507 above.
  • Step 509 The new AMF obtains the context of the UE from the old AMF request.
  • Step 510 The new AMF determines the new Allowed NSSAI for the UE and stores it in the context of the UE.
  • the new Allowed NSSAI of the UE determined by the new AMF and the new Allowed NSSAI sent by the old AMF to the UE in step 507 may be the same or different. This is because the new AMF needs to further determine the final Allowed NSSAI for the UE based on the congestion of the current network slice.
  • step 511 the AMF requests the NRF to find a suitable PCF according to the new Allowed NSSAI determined in step 510.
  • the AMF calls the NRF service operation Nnrf_NFDiscovery_Request, which carries the SUPI of the UE and the new Allowed NSSAI determined in step 510.
  • step 512 the NRF determines a suitable PCF, and sends the PCF ID (PCF ID) to the AMF.
  • NEF determines the appropriate PCF based on SUPI and new Allowed NSSAI.
  • NRF can return Nnrf_NFDiscovery_Response to AMF, carrying PCF ID.
  • Step 513 The new AMF sends an AM Policy Association Establishment (AM Policy Association) request to the PCF based on the PCF ID returned by the NRF.
  • AM Policy Association AM Policy Association
  • AMF calls the PCF service operation: Npcf_AMPolicyControl_Create, which carries SUPI, new Allowed NSSAI).
  • Step 514 The PCF sends an AM policy (AM policy for new Allowed NSSAI) and a policy control request trigger (Policy Control Request Triggers) generated based on the new Allowed NSSAI to the new AMF.
  • AM policy AM policy for new Allowed NSSAI
  • Policy Control Request Triggers Policy Control Request Triggers
  • PCF returns Npcf_AMPolicyControl_Create Response to new AMF, which carries AM policy for new Allowed NSSAI and Policy Control Request Triggers.
  • the AM policy is generated by the PCF according to the new Allowed NSSAI, and the AM policy of this step can also be called the AM policy for new Allowed NSSAI.
  • AM policy includes but is not limited to: air interface access technology/spectrum selection priority index, user aggregation maximum bit rate, and service area limitation.
  • Policy Control Request Triggers refers to policy control request triggers, or policy event reporting triggers.
  • the corresponding trigger conditions are met (such as the UE’s Allowed NSSAI changes)
  • new AMF can initiate the AM policy association update process. Thereby updating the corresponding strategy.
  • step 514 it also includes step 514a and step 514b:
  • step 514a the new AMF sends a UE Policy Association Establishment (UE Policy Association Establishment) request to the PCF based on the PCF ID returned by the NRF.
  • UE Policy Association Establishment UE Policy Association Establishment
  • new AMF calls the PCF service operation: Npcf_UEPolicyControl Create Request, which carries SUPI.
  • step 514b the PCF sends a UE policy (UE policy) to the new AMF.
  • UE policy UE policy
  • PCF returns Npcf_UEPolicyControl Create Response to new AMF, which carries UE policy.
  • the UE policy includes but is not limited to: UE access selection strategy (such as access network discovery and selection strategy), and PDU session selection-related strategies (such as UE routing selection strategy).
  • UE access selection strategy such as access network discovery and selection strategy
  • PDU session selection-related strategies such as UE routing selection strategy
  • Step 515 The AMF sends a registration acceptance message to the UE, which carries the new Allowed NSSAI, based on the AM policy and the UE policy generated by the new Allowed NSSAI.
  • old AMF determines that it needs to perform the NSAA process on some S-NSSAI in the requested NSSAI, then old AMF does not select PCF.
  • old AMF does not support new Allowed NSSAI, AMF relocation is required and reselected to new AMF. Since the new AMF does not obtain the PCF ID from the old AMF, the new AMF selects the appropriate PCF according to the final allowed NSSAI of the UE and obtains policy information.
  • This embodiment can avoid the problems of PCF reselection and frequent policy refresh. Therefore, resource expenditure can be saved.
  • FIG. 6 a schematic flow diagram of another communication method provided by this application. This embodiment is aimed at a scenario where AMF does not change before and after the NSSAA process.
  • the method includes the following steps:
  • step 601 the UE initiates a registration process and sends a registration request (Registration Request) message to the AMF.
  • the registration request message carries the requested NSSAI (Requested NSSAI).
  • the AMF executes the main authentication procedure of the permanent identity of the UE. After the procedure is successful, the AMF obtains the UE's subscription data from the UDM.
  • the subscription data includes the S-NSSAI subscribed by the UE and indication information corresponding to each S-NSSAI, and the indication information is used to indicate whether the S-NSSAI needs to perform NSSAA.
  • the S-NSSAI and indication information of the subscription in the subscription data of the UE are as shown in Table 2 above.
  • the AMF can call the UDM service operation Nudm_SDM_Get to obtain the UE's subscription data, and the UDM sends the UE's subscription data to the AMF through Nudm_SDM_Get response.
  • step 603 the AMF requests the NRF to find a suitable PCF according to the first NSSAI and SUPI.
  • the first NSSAI here includes Allowed NSSAI and Pending S-NSSAI.
  • Allowed NSSAI includes S-NSSAI that does not require NSSAA among requested NSSAIs, and Pending NSSAI includes S-NSSAI that requires NSSAA among requested NSSAIs.
  • step 602 the method in which the AMF determines in step 602 that the S-NSSAI in the requested NSSAI needs to execute NSSAA is the same as step 403, and will not be repeated.
  • the first NSSAI here may include an S-NSSAI (subscribed NSSAI) subscribed by the UE.
  • S-NSSAI subscribed NSSAI
  • the AMF can call the NRF service operation Nnrf_NFDiscovery_Request, which carries the SUPI and the first NSSAI of the UE.
  • step 604 the NRF determines a suitable PCF, and sends the PCF ID (PCF ID) to the AMF.
  • NEF determines a suitable PCF based on SUPI and the first NSSAI.
  • NRF can return Nnrf_NFDiscovery_Response to AMF, carrying PCF ID.
  • the slice information used by the PCF selected in this step is the first NSSAI. If the first NSSAI includes Allowed NSSAI and Pending S-NSSAI, then the PCF selected by NRF must support the slices corresponding to Allowed NSSAI and Pending S-NSSAI . If the first NSSAI includes subscribed NSSAI, then the PCF selected by NRF must support the slice corresponding to subscribed NSSAI.
  • Step 605 Based on the PCF ID returned by the NRF, the AMF sends an AM Policy Association Establishment (AM Policy Association) request to the PCF.
  • AM Policy Association AM Policy Association
  • AMF calls the PCF service operation: Npcf_AMPolicyControl_Create, which carries SUPI, Allowed NSSAI).
  • Step 606 The PCF sends an AM policy (AM policy for Allowed NSSAI) and a policy control request trigger (Policy Control Request Triggers) generated based on the Allowed NSSAI to the AMF.
  • AM policy AM policy for Allowed NSSAI
  • Policy Control Request Triggers Policy Control Request Triggers
  • PCF returns Npcf_AMPolicyControl_Create Response to AMF, which carries AM policy for Allowed NSSAI and Policy Control Request Triggers.
  • the AM policy is generated by the PCF according to Allowed NSSAI, and the AM policy of this step can also be called AM policy for Allowed NSSAI.
  • AM policy includes but is not limited to: air interface access technology/spectrum selection priority index, user aggregation maximum bit rate, and service area limitation.
  • Policy Control Request Triggers refers to policy control request triggers, or policy event reporting triggers.
  • the AMF can initiate the AM policy association update process, thereby Update the corresponding strategy.
  • Step 607 The Registration Accept message sent by the AMF to the UE carries one or more of allowed NSSAI (Allowed NSSAI), pending NSSAI (Pending NSSAI), and rejected NSSAI (Rejected NSSAI).
  • allowed NSSAI Allowed NSSAI
  • pending NSSAI Pending NSSAI
  • rejected NSSAI Rejected NSSAI
  • the registration acceptance message also carries the AM policy generated based on the Allowed NSSAI that the AMF received from the PCF in step 606.
  • the AMF may also send a pending cause value to the UE: waiting for NSSAA, and the cause value is used to indicate to the UE that those S-NSSAIs that require NSSAA are in a pending state.
  • the AMF may also send a rejection reason value to the UE: the current area is not available.
  • Allowed NSSAI includes S-NSSAI that does not require NSSAA
  • Pending NSSAI includes S-NSSAI that requires NSSAA
  • Rejected NSSAI includes S-NSSAI that is not available in the current area for the UE in the requested NSSAI.
  • the Requested NSSAI carried by the UE includes S-NSSAI-1, S-NSSAI-2, and S-NSSAI-3.
  • S-NSSAI-1 and S-NSSAI-2 need to perform the NSSAA process
  • Rejected NSSAI is empty.
  • the AMF stores the Allowed NSSAI in this step in the context of the UE on the AMF.
  • step 607 it further includes step 607a, step 607b, and step 607c:
  • Step 607a Based on the PCF ID returned by the NRF, the AMF sends a UE Policy Association Establishment (UE Policy Association) request to the PCF.
  • UE Policy Association UE Policy Association
  • AMF calls PCF's servicing operation: Npcf_UEPolicyControl Create Request, which carries SUPI.
  • step 607b the PCF sends a UE policy (UE policy) to the AMF.
  • UE policy UE policy
  • PCF returns Npcf_UEPolicyControl Create Response to AMF, which carries UE policy.
  • the UE policy includes but is not limited to: UE access selection strategy (such as access network discovery and selection strategy), and PDU session selection-related strategies (such as UE routing selection strategy).
  • UE access selection strategy such as access network discovery and selection strategy
  • PDU session selection-related strategies such as UE routing selection strategy
  • Step 607c The AMF sends a configuration update request (configuration update request) message to the UE, which carries the UE policy.
  • step 608 the AMF executes the NSSAA process for the pending S-NSSAI.
  • step 608 the AMF executes NSSAA in the S-NSSAI of the pending NSSAI, and the method is the same as step 405.
  • Pending NSSAI S-NSSAI-1+S-NSSAI-2, since both S-NSSAI-1 and S-NSSAI-2 are HPLMN S-NSSAI, then AMF will compare S-NSSAI -1 and S-NSSAI-2 execute the NSSAA process.
  • Pending NSSAI S-NSSAI-A and S-NSSAI-B, since S-NSSAI-A is mapped to S-NSSAI-1, and S-NSSAI-B is mapped to S-NSSAI-2, Then AMF executes the NSSAA process on S-NSSAI-1 and S-NSSAI-2.
  • NSSAA result of S-NSSAI-1 is NSSAA success
  • NSSAA result of S-NSSAI-A is NSSAA success
  • access to S-NSSAI-A is allowed
  • NSSAA result of S-NSSAI-1 is NSSAA Failure
  • NSSAA result of S-NSSAI-A is NSSAA failure
  • access to S-NSSAI-A is denied.
  • NSSAA result of S-NSSAI-2 is NSSAA success
  • NSSAA result of S-NSSAI-B is NSSAA success
  • access to S-NSSAI-B is allowed
  • NSSAA result of S-NSSAI-2 is NSSAA Failure
  • NSSAA failure can also be understood as the result of NSSAA of S-NSSAI-B as NSSAA failure, and access to S-NSSAI-B is denied.
  • step 608 is an optional step. When there is an S-NSSAI that needs to execute the NSSAA process, step 608 is executed. Otherwise, step 608 is not executed.
  • step 608 can be executed multiple times.
  • Step 609 After the execution of the NSSAA process is completed, the AMF determines whether the Allowed NSSAI of the UE needs to be updated according to the result of the process. If there is a successful NSSAA slice, the S-NSSAI corresponding to the successful NSSAA slice is added to step 607 and sent to In the Allowed NSSAI of the UE, a new Allowed NSSAI (new Allowed NSSAI) is obtained.
  • the AMF also determines Rejected NSSAI, and the Rejected NSSAI includes the S-NSSAI corresponding to the NSSAA failed slice in the Pending NSSAI.
  • the AMF is stored in the context of the UE in accordance with Allowed in step 607 NSSAI, add S-NSSAI-1 to the Allowed NSSAI of the UE, that is, the Allowed NSSAI is updated to: S-NSSAI-1+S-NSSAI-3. And generate a rejected NSSAI.
  • the rejected NSSAI includes S-NSSAI-2. Optionally, it also generates a rejection reason value: NSSAA failed.
  • the AMF is based on the Allowed NSSAI stored in the context of the UE in step 607.
  • Add S-NSSAI-A to the Allowed NSSAI of the UE, that is, the Allowed NSSAI is updated to: S-NSSAI-A+S-NSSAI-C.
  • the rejected NSSAI includes S-NSSAI-B.
  • it also generates a rejection reason value: NSSAA failed.
  • Step 610 If the current AMF can continue to serve the UE, the AMF decides to send an AM Policy Association Modification (AM Policy Association Modification) request to the PCF according to the Allowed NSSAI change (or change of allowed NSSAI) of the UE included in the Policy Control Request Triggers.
  • the AM policy association modification request includes SUPI and new Allowed NSSAI, and the new Allowed NSSAI is the new Allowed NSSAI determined in step 609.
  • the AMF determines that the allowed NSSAI has changed, and determines that the Policy Control Request Triggers is triggered, so it re-requests the PCF for a new AM policy.
  • AMF calls the PCF service operation: Npcf_AMPolicyControl_Update, which carries SUPI, new Allowed NSSAI).
  • Step 611 The PCF sends an AM policy (AM policy for new Allowed NSSAI) generated based on the new Allowed NSSAI to the AMF.
  • AM policy AM policy for new Allowed NSSAI
  • PCF returns Npcf_AMPolicyControl_Update Response to AMF, which carries AM policy for new Allowed NSSAI.
  • Step 612 The AMF sends a configuration update request (configuration update request) message to the UE, which carries a new Allowed NSSAI and an AM policy generated based on the new Allowed NSSAI.
  • the configuration update request message may also carry the rejected NSSAI.
  • AMF uses a set consisting of Allowed NSSAI and Pending NSSAI or AMF uses subscribed NSSAI to select PCF.
  • the NSSAA succeeds, it can avoid that the PCF selected before the NSSAA process does not support the new Allowed NSSAI of the UE after the NSSAA process, thereby avoiding reselecting the PCF. Therefore, resource expenditure can be saved.
  • FIG. 7 a schematic flowchart of another communication method provided by this application. This embodiment is aimed at a scenario where AMF changes before and after the NSSAA process.
  • the method includes the following steps:
  • Step 701 The UE initiates a registration process, and sends a Registration Request (Registration Request) message to the old AMF (old AMF), and the Registration Request message carries the requested NSSAI (Requested NSSAI).
  • Registration Request Registration Request
  • NSSAI Requested NSSAI
  • the old AMF here refers to the AMF selected by the access network to serve the UE during the registration process, or can be understood as the AMF that serves the UE for the first time in the registration process.
  • the old AMF involved in the present invention may also be called initial AMF (initial AMF) or current AMF (serving AMF).
  • the old AMF executes the primary authentication procedure of the permanent identity of the UE. After the procedure is successful, the old AMF obtains the UE's subscription data from the UDM.
  • the subscription data includes the S-NSSAI subscribed by the UE and indication information corresponding to each S-NSSAI, and the indication information is used to indicate whether the S-NSSAI needs to perform NSSAA.
  • the S-NSSAI and indication information of the subscription in the subscription data of the UE are as shown in Table 2 above.
  • the old AMF can call the servicing operation Nudm_SDM_Get of UDM to obtain the subscription data of the UE, and the UDM sends the subscription data of the UE to the AMF through Nudm_SDM_Get response.
  • Step 703 The old AMF requests the NRF to find a suitable PCF according to the first NSSAI and SUPI.
  • the first NSSAI here includes Allowed NSSAI and Pending S-NSSAI.
  • Allowed NSSAI includes S-NSSAI that does not require NSSAA among requested NSSAIs, and Pending NSSAI includes S-NSSAI that requires NSSAA among requested NSSAIs.
  • step 703 the old AMF determines that the S-NSSAI in the requested NSSAI needs to execute NSSAA.
  • the method is the same as that in step 503, and will not be repeated.
  • the first NSSAI here may include an S-NSSAI (subscribed NSSAI) subscribed by the UE.
  • S-NSSAI subscribed NSSAI
  • the old AMF can call the NRF service operation Nnrf_NFDiscovery_Request, which carries the SUPI and the first NSSAI of the UE.
  • Step 704 The NRF determines a suitable PCF, and sends the PCF ID (PCF ID) to the old AMF.
  • NEF determines a suitable PCF based on SUPI and the first NSSAI.
  • NRF can return Nnrf_NFDiscovery_Response to old AMF, carrying PCF ID.
  • the slice information used by the PCF selected in this step is the first NSSAI. If the first NSSAI includes Allowed NSSAI and Pending S-NSSAI, then the PCF selected by NRF must support the slices corresponding to Allowed NSSAI and Pending S-NSSAI ability. If the first NSSAI includes subscribed NSSAI, then the PCF selected by NRF must support the slice corresponding to subscribed NSSAI.
  • Step 705 Based on the PCF ID returned by the NRF, the old AMF sends an AM Policy Association Establishment (AM Policy Association) request to the PCF.
  • AM Policy Association AM Policy Association
  • the AM policy association establishment request carries SUPI and Allowed NSSAI.
  • the old AMF calls the PCF service operation: Npcf_AMPolicyControl_Create, which carries SUPI, Allowed NSSAI).
  • Step 706 The PCF sends an AM policy (AM policy for Allowed NSSAI) and a policy control request trigger (Policy Control Request Triggers) generated based on the Allowed NSSAI to the old AMF.
  • AM policy AM policy for Allowed NSSAI
  • Policy Control Request Triggers Policy Control Request Triggers
  • PCF returns Npcf_AMPolicyControl_Create Response to old AMF, which carries AM policy for Allowed NSSAI and Policy Control Request Triggers.
  • the AM policy is generated by the PCF according to Allowed NSSAI, and the AM policy of this step can also be called AM policy for Allowed NSSAI.
  • AM policy includes but is not limited to: air interface access technology/spectrum selection priority index, user aggregation maximum bit rate, and service area limitation.
  • Policy Control Request Triggers refers to policy control request triggers, or policy event reporting triggers.
  • the corresponding trigger conditions are met (for example, the UE's Allowed NSSAI changes)
  • the old AMF can initiate the AM policy association update process. Thereby updating the corresponding strategy.
  • Step 707 The Registration Accept message sent by the old AMF to the UE carries one or more of allowed NSSAI (Allowed NSSAI), pending NSSAI (Pending NSSAI), and rejected NSSAI (Rejected NSSAI), and Carry the AM policy generated based on the allowed NSSAI.
  • allowed NSSAI Allowed NSSAI
  • pending NSSAI Pending NSSAI
  • rejected NSSAI Rejected NSSAI
  • the old AMF may also send a pending cause value to the UE: waiting for NSSAA, and the cause value is used to indicate to the UE that those S-NSSAIs that require NSSAA are in a pending state.
  • old AMF may also send a rejection reason value to the UE: the current area is not available.
  • Allowed NSSAI includes S-NSSAI in the requested NSSAI that does not require NSSAA, Pending NSSAI includes S-NSSAI in the requested NSSAI that requires NSSAA, and Rejected NSSAI includes the UE in the requested NSSAI that is not available in the current area. S-NSSAI.
  • the Requested NSSAI carried by the UE includes S-NSSAI-1, S-NSSAI-2, and S-NSSAI-3.
  • S-NSSAI-1 and S-NSSAI-2 need to perform the NSSAA process
  • Rejected NSSAI is empty.
  • the old AMF stores the Allowed NSSAI in this step in the context of the UE on the old AMF.
  • step 707 it also includes step 707a, step 707b, and step 707c:
  • Step 707a Based on the PCF ID returned by the NRF, the old AMF sends a UE Policy Association Establishment (UE Policy Association) request to the PCF.
  • UE Policy Association UE Policy Association
  • Npcf_UEPolicyControl Create Request which carries SUPI.
  • step 707b the PCF sends a UE policy (UE policy) to the old AMF.
  • UE policy UE policy
  • PCF returns Npcf_UEPolicyControl Create Response to old AMF, which carries UE policy.
  • the UE policy includes but is not limited to: UE access selection strategy (such as access network discovery and selection strategy), and PDU session selection-related strategies (such as UE routing selection strategy).
  • UE access selection strategy such as access network discovery and selection strategy
  • PDU session selection-related strategies such as UE routing selection strategy
  • Step 707c The AMF sends a configuration update request (configuration update request) message to the UE, which carries the UE policy.
  • Step 708 the old AMF executes the NSSAA process for the pending S-NSSAI.
  • Pending NSSAI S-NSSAI-1+S-NSSAI-2, since both S-NSSAI-1 and S-NSSAI-2 are HPLMN S-NSSAI, then old AMF is against S- NSSAI-1 and S-NSSAI-2 execute the NSSAA process.
  • Pending NSSAI S-NSSAI-A and S-NSSAI-B, since S-NSSAI-A is mapped to S-NSSAI-1, and S-NSSAI-B is mapped to S-NSSAI-2, Then AMF executes the NSSAA process on S-NSSAI-1 and S-NSSAI-2.
  • NSSAA result of S-NSSAI-1 is NSSAA success
  • NSSAA result of S-NSSAI-A is NSSAA success
  • access to S-NSSAI-A is allowed
  • NSSAA result of S-NSSAI-1 is NSSAA Failure
  • NSSAA result of S-NSSAI-A is NSSAA failure
  • access to S-NSSAI-A is denied.
  • NSSAA result of S-NSSAI-2 is NSSAA success
  • NSSAA result of S-NSSAI-B is NSSAA success
  • access to S-NSSAI-B is allowed
  • NSSAA result of S-NSSAI-2 is NSSAA Failure
  • NSSAA failure can also be understood as the result of NSSAA of S-NSSAI-B as NSSAA failure, and access to S-NSSAI-B is denied.
  • step 708 is an optional step. When there is an S-NSSAI that needs to execute the NSSAA process, step 708 is executed. Otherwise, step 708 is not executed.
  • step 708 can be executed multiple times.
  • step 709 after the execution of the NSSAA process is completed, the AMF determines whether the Allowed NSSAI of the UE needs to be updated according to the result of the process. If there is a successful NSSAA slice, the S-NSSAI corresponding to the successful NSSAA slice is added to step 707 and sent to In the Allowed NSSAI of the UE, a new Allowed NSSAI (new Allowed NSSAI) is obtained.
  • the AMF also determines Rejected NSSAI, and the Rejected NSSAI includes the S-NSSAI corresponding to the NSSAA failed slice in the Pending NSSAI.
  • the AMF will store the Allowed NSSAI in the context of the UE in step 707.
  • Add S-NSSAI-1 to the Allowed NSSAI of the UE, that is, the Allowed NSSAI is updated to: S-NSSAI-1+S-NSSAI-3.
  • the rejected NSSAI includes S-NSSAI-2.
  • it also generates a rejection reason value: NSSAA failed.
  • AMF will store the Allowed NSSAI in the context of the UE in step 707.
  • Add S-NSSAI-A to the Allowed NSSAI of the UE, that is, the Allowed NSSAI is updated to: S-NSSAI-A+S-NSSAI-C.
  • the rejected NSSAI includes S-NSSAI-B.
  • it also generates a rejection reason value: NSSAA failed.
  • Step 710 If the current AMF (ie, old AMF) cannot continue to serve the UE, the old AMF needs to trigger the AMF reallocation. At the same time, the old AMF sets indication information in the context of the UE to indicate that the allowed NSSAI change satisfies the Policy Control Request Triggers.
  • the current AMF cannot continue to serve the UE means that the current AMF does not support the new Allowed NSSAI determined in step 709, so the AMF needs to be changed.
  • the old AMF also adds the policy control request triggers (Policy Control Request Triggers) obtained from the PCF to the context of the UE.
  • Policy Control Request Triggers Policy Control Request Triggers
  • Step 711 The old AMF sends a configuration update request message to the UE, which carries new Allowed NSSAI and indication information.
  • the indication information is used to instruct the UE to use the new Allowed NSSAI as the requested NSSAI to initiate a registration process immediately after receiving the new Allowed NSSAI.
  • Step 712 The UE initiates a registration process according to the new Allowed NSSAI and the indication information.
  • the UE registers with a new AMF (new AMF), that is, the new AMF serves the UE, where the new AMF supports the slice indicated by the new Allowed NSSAI.
  • new AMF new AMF
  • the UE sends a Requested NSSAI during the registration process, and the Requested NSSAI includes the new Allowed NSSAI in step 709.
  • Step 713 The new AMF obtains the context of the UE from the old AMF request.
  • the context of the UE on the old AMF contains the PCF ID and indication information.
  • the indication information is used to indicate that the allowed NSSAI change satisfies the Policy Control Request Triggers. Or it can be understood that the indication information is used to instruct the new AMF to obtain a new policy from the PCF. Therefore, the new AMF obtains the PCF ID and indication information from the old AMF, and triggers the acquisition of an updated policy from the PCF according to the indication information.
  • Step 714 The new AMF determines the new Allowed NSSAI for the UE and stores it in the context of the UE.
  • the new Allowed NSSAI of the UE determined by the new AMF may be the same or different from the new Allowed NSSAI determined by the old AMF in step 709. This is because the new AMF needs to further determine the final Allowed NSSAI for the UE based on the congestion of the current network slice.
  • Step 715 The new AMF decides to send an AM Policy Association Modification (AM Policy Association Modification) request to the PCF according to the indication information in the context of the UE.
  • the AM policy association modification request includes SUPI and new Allowed NSSAI, and the new Allowed NSSAI is the new Allowed NSSAI determined in step 714.
  • the new AMF determines that the allowed NSSAI has changed, and the Policy Control Request Triggers is determined to be triggered, so it re-requests the PCF for a new AM policy.
  • new AMF calls the PCF service operation: Npcf_AMPolicyControl_Update, which carries SUPI, new Allowed NSSAI).
  • Step 716 The PCF sends an AM policy (AM policy for new Allowed NSSAI) generated based on the new Allowed NSSAI to the AMF.
  • AM policy AM policy for new Allowed NSSAI
  • PCF returns Npcf_AMPolicyControl_Update Response to new AMF, which carries AM policy for new Allowed NSSAI.
  • Step 717 The new AMF sends a registration acceptance message to the UE, which carries the new Allowed NSSAI and the AM policy generated based on the new Allowed NSSAI.
  • old AMF uses a set consisting of Allowed NSSAI and Pending NSSAI, or AMF uses subscribed NSSAI to select PCF.
  • NSSAA succeeds, it can avoid that the PCF selected before the NSSAA process does not support the new Allowed NSSAI of the UE after the NSSAA process, thereby avoiding reselecting the PCF.
  • the new AMF can trigger the acquisition of a new AM policy from the PCF according to the indication information stored in the context of the UE by the old AMF, and the new AMF can re-determine the new Allowed NSSAI according to the new Allowed NSSAI determined by the old AMF, and add the new AM The new Allowed NSSAI determined by the policy and new AMF is sent to the UE.
  • FIG. 8 it is a schematic flowchart of another communication method provided by this application. This embodiment is aimed at a scenario where AMF changes before and after the NSSAA process.
  • the method includes the following steps:
  • step 801 the UE initiates a registration process and sends a registration request (Registration Request) message to the old AMF (old AMF), and the registration request message carries the requested NSSAI (Requested NSSAI).
  • the old AMF here refers to the AMF selected by the access network to serve the UE during the registration process, or can be understood as the AMF that serves the UE for the first time in the registration process.
  • the old AMF involved in the present invention may also be called initial AMF (initial AMF) or current AMF (serving AMF).
  • the old AMF executes the primary authentication procedure of the permanent identity of the UE. After the procedure is successful, the old AMF obtains the UE's subscription data from the UDM.
  • the subscription data includes the S-NSSAI subscribed by the UE and indication information corresponding to each S-NSSAI, and the indication information is used to indicate whether the S-NSSAI needs to perform NSSAA.
  • the S-NSSAI and indication information of the subscription in the subscription data of the UE are as shown in Table 2 above.
  • the old AMF can call the servicing operation Nudm_SDM_Get of UDM to obtain the subscription data of the UE, and the UDM sends the subscription data of the UE to the AMF through Nudm_SDM_Get response.
  • step 803 the old AMF requests the NRF to find a suitable PCF according to Allowed NSSAI and SUPI.
  • Allowed NSSAI includes S-NSSAI that does not require NSSAA among the requested NSSAI.
  • the old AMF can call the NRF service operation Nnrf_NFDiscovery_Request, which carries the SUPI and Allowed NSSAI of the UE.
  • step 804 the NRF determines a suitable PCF, and sends the PCF ID (PCF ID) to the old AMF.
  • NEF determines a suitable PCF based on SUPI and Allowed NSSAI.
  • NRF can return Nnrf_NFDiscovery_Response to old AMF, carrying PCF ID.
  • step 805 the old AMF sends an AM Policy Association Establishment (AM Policy Association) request to the PCF based on the PCF ID returned by the NRF.
  • AM Policy Association AM Policy Association
  • the AM policy association establishment request carries SUPI and Allowed NSSAI.
  • old AMF calls the servicing operation of PCF: Npcf_AMPolicyControl_Create, which carries SUPI, Allowed NSSAI).
  • Step 806 The PCF sends an AM policy (AM policy for Allowed NSSAI) and a policy control request trigger (Policy Control Request Triggers) generated based on the Allowed NSSAI to the old AMF.
  • AM policy AM policy for Allowed NSSAI
  • Policy Control Request Triggers Policy Control Request Triggers
  • PCF returns Npcf_AMPolicyControl_Create Response to old AMF, which carries AM policy for Allowed NSSAI and Policy Control Request Triggers.
  • the AM policy is generated by the PCF according to Allowed NSSAI, and the AM policy of this step can also be called AM policy for Allowed NSSAI.
  • AM policy includes but is not limited to: air interface access technology/spectrum selection priority index, user aggregation maximum bit rate, and service area limitation.
  • Policy Control Request Triggers refers to policy control request triggers, or policy event reporting triggers.
  • the corresponding trigger conditions are met (such as the UE’s Allowed NSSAI changes)
  • the old AMF can initiate the AM policy association update process. Thereby updating the corresponding strategy.
  • Step 807 The Registration Accept message sent by the old AMF to the UE carries one or more of Allowed NSSAI (Allowed NSSAI), Pending NSSAI (Pending NSSAI), and Rejected NSSAI (Rejected NSSAI), and Carry the AM policy generated based on the allowed NSSAI.
  • Allowed NSSAI Allowed NSSAI
  • Pending NSSAI Pending NSSAI
  • Rejected NSSAI Rejected NSSAI
  • step 807 the old AMF determines that the S-NSSAI in the requested NSSAI needs to execute the NSSAA.
  • the method is the same as that in step 503, and will not be repeated.
  • the old AMF may also send a pending cause value to the UE: waiting for NSSAA, and the cause value is used to indicate to the UE that those S-NSSAIs that require NSSAA are in a pending state.
  • old AMF may also send a rejection reason value to the UE: the current area is not available.
  • Allowed NSSAI includes S-NSSAI in the requested NSSAI that does not require NSSAA, Pending NSSAI includes S-NSSAI in the requested NSSAI that requires NSSAA, and Rejected NSSAI includes the UE in the requested NSSAI that is not available in the current area. S-NSSAI.
  • the Requested NSSAI carried by the UE includes S-NSSAI-1, S-NSSAI-2, and S-NSSAI-3.
  • S-NSSAI-1 and S-NSSAI-2 need to perform the NSSAA process
  • Rejected NSSAI is empty.
  • the old AMF stores the Allowed NSSAI in this step in the context of the UE on the old AMF.
  • step 807 it also includes step 807a, step 807b, and step 807c:
  • Step 807a Based on the PCF ID returned by the NRF, the old AMF sends a UE Policy Association Establishment (UE Policy Association) request to the PCF.
  • UE Policy Association UE Policy Association
  • Npcf_UEPolicyControl Create Request which carries SUPI.
  • Step 807b the PCF sends a UE policy (UE policy) to the old AMF.
  • UE policy UE policy
  • PCF returns Npcf_UEPolicyControl Create Response to old AMF, which carries UE policy.
  • the UE policy includes but is not limited to: UE access selection strategy (such as access network discovery and selection strategy), and PDU session selection-related strategies (such as UE routing selection strategy).
  • UE access selection strategy such as access network discovery and selection strategy
  • PDU session selection-related strategies such as UE routing selection strategy
  • Step 807c The old AMF sends a configuration update request (configuration update request) message to the UE, which carries the UE policy.
  • Step 808 the old AMF executes the NSSAA process for the pending S-NSSAI.
  • Pending NSSAI S-NSSAI-1+S-NSSAI-2, since both S-NSSAI-1 and S-NSSAI-2 are HPLMN S-NSSAI, then old AMF is against S- NSSAI-1 and S-NSSAI-2 execute the NSSAA process.
  • Pending NSSAI S-NSSAI-A and S-NSSAI-B, since S-NSSAI-A is mapped to S-NSSAI-1, and S-NSSAI-B is mapped to S-NSSAI-2, Then AMF executes the NSSAA process on S-NSSAI-1 and S-NSSAI-2.
  • NSSAA result of S-NSSAI-1 is NSSAA success
  • NSSAA result of S-NSSAI-A is NSSAA success
  • access to S-NSSAI-A is allowed
  • NSSAA result of S-NSSAI-1 is NSSAA Failure
  • NSSAA result of S-NSSAI-A is NSSAA failure
  • access to S-NSSAI-A is denied.
  • NSSAA result of S-NSSAI-2 is NSSAA success
  • NSSAA result of S-NSSAI-B is NSSAA success
  • access to S-NSSAI-B is allowed
  • NSSAA result of S-NSSAI-2 is NSSAA Failure
  • NSSAA failure can also be understood as the result of NSSAA of S-NSSAI-B as NSSAA failure, and access to S-NSSAI-B is denied.
  • step 808 is an optional step. When there is an S-NSSAI that needs to execute the NSSAA process, step 808 is executed. Otherwise, step 808 is not executed.
  • step 808 can be executed multiple times.
  • step 809 after the execution of the NSSAA process is completed, the AMF determines whether the Allowed NSSAI of the UE needs to be updated according to the result of the process. If there is a successful NSSAA slice, the S-NSSAI corresponding to the successful NSSAA slice is added to step 807 and sent to In the Allowed NSSAI of the UE, a new Allowed NSSAI (new Allowed NSSAI) is obtained.
  • the AMF also determines Rejected NSSAI, and the Rejected NSSAI includes the S-NSSAI corresponding to the NSSAA failed slice in the Pending NSSAI.
  • the AMF will store the Allowed NSSAI in the context of the UE in step 807.
  • Add S-NSSAI-1 to the Allowed NSSAI of the UE, that is, the Allowed NSSAI is updated to: S-NSSAI-1+S-NSSAI-3.
  • the rejected NSSAI includes S-NSSAI-2.
  • it also generates a rejection reason value: NSSAA failed.
  • Step 810 If the current AMF (ie, old AMF) cannot continue to serve the UE, the old AMF needs to trigger the AMF reallocation. At the same time, the old AMF judges that the allowed NSSAI change satisfies the Policy Control Request Triggers based on the Policy Control Request Triggers, and the old AMF decides to first obtain the new allowed NSSAI corresponding new AM policy from the PCF.
  • the current AMF ie, old AMF
  • the old AMF needs to trigger the AMF reallocation.
  • the old AMF judges that the allowed NSSAI change satisfies the Policy Control Request Triggers based on the Policy Control Request Triggers, and the old AMF decides to first obtain the new allowed NSSAI corresponding new AM policy from the PCF.
  • the current AMF cannot continue to serve the UE means that the current AMF does not support the new Allowed NSSAI determined in step 709, so the AMF needs to be changed.
  • Step 811 The old AMF sends an AM Policy Association Modification (AM Policy Association Modification) request to the PCF.
  • the AM policy association modification request includes SUPI and new Allowed NSSAI, and the new Allowed NSSAI is the new Allowed NSSAI determined in step 809.
  • Npcf_AMPolicyControl_Update which carries SUPI, new Allowed NSSAI.
  • step 812 the PCF sends an AM policy (AM policy for new Allowed NSSAI) generated based on the new Allowed NSSAI to the old AMF.
  • AM policy AM policy for new Allowed NSSAI
  • PCF returns Npcf_AMPolicyControl_Update Response to new AMF, which carries AM policy for new Allowed NSSAI.
  • Step 813 The old AMF stores the AM policy generated based on the new Allowed NSSAI in the context of the UE.
  • the old AMF also adds the policy control request triggers (Policy Control Request Triggers) obtained from the PCF to the context of the UE.
  • Policy Control Request Triggers Policy Control Request Triggers
  • Step 814 The old AMF sends a configuration update request message to the UE, which carries new Allowed NSSAI and indication information.
  • the indication information is used to instruct the UE to use the new Allowed NSSAI as the requested NSSAI to initiate a registration process immediately after receiving the new Allowed NSSAI.
  • the configuration update request message also carries AM policy information generated based on new Allowed NSSAI. In this way, the subsequent new AMF does not need to send the AM policy information generated based on the new Allowed NSSAI to the UE.
  • old AMF can set an indication information in the context of the UE on old AMF.
  • the information is used to indicate: new AMF sends AM policy information in the context of the UE (that is, AM policy information generated based on new Allowed NSSAI) to the UE.
  • new AMF sends AM policy information in the context of the UE (that is, AM policy information generated based on new Allowed NSSAI) to the UE.
  • the subsequent new AMF obtains the UE context from the old AMF, it can determine to send the AM policy information generated based on the new Allowed NSSAI to the UE according to the above indication information in the UE context.
  • Step 815 The UE initiates a registration process according to the new Allowed NSSAI and the instruction information.
  • the UE registers with a new AMF (new AMF), that is, the new AMF serves the UE, where the new AMF supports the slice indicated by the new Allowed NSSAI.
  • new AMF new AMF
  • the UE sends a Requested NSSAI during the registration process, and the Requested NSSAI includes the new Allowed NSSAI in step 809 above.
  • Step 816 the new AMF obtains the context of the UE from the old AMF request.
  • the new AMF obtains the PCF ID and the AM policy generated based on the new Allowed NSSAI from the old AMF.
  • the context of the UE also includes indication information, which is used to indicate that new AMF sends AM policy information in the context of the UE (that is, AM policy information generated based on new Allowed NSSAI) to the UE.
  • indication information is used to indicate that new AMF sends AM policy information in the context of the UE (that is, AM policy information generated based on new Allowed NSSAI) to the UE.
  • the new AMF determines the new Allowed NSSAI for the UE and stores it in the context of the UE.
  • the new Allowed NSSAI of the UE determined by the new AMF and the new Allowed NSSAI determined by the old AMF in step 809 may be the same or different. This is because the new AMF needs to further determine the final Allowed NSSAI for the UE based on the congestion of the current network slice.
  • Step 818 The new AMF sends a registration acceptance message to the UE, which carries new Allowed NSSAI.
  • the new AMF carries AM policy information in the registration acceptance message according to the indication information, and the AM policy information is obtained by the new AMF from the context of the UE.
  • old AMF uses the method of the prior art and Allowed NSSAI to select PCF.
  • the old AMF determines the new Allowed NSSAI, and obtains the updated AM policy from the PCF according to the new Allowed NSSAI and stores it in the context of the UE on the old AMF.
  • new AMF obtains the UE context from old AMF, it can obtain the updated AM policy from the UE context, which eliminates the need to obtain the updated AM policy from the PCF again.
  • FIG. 9 it is a schematic flowchart of another communication method provided by this application. This embodiment is aimed at a scenario where AMF changes before and after the NSSAA process.
  • the method includes the following steps:
  • Step 901 The UE initiates a registration process, and sends a Registration Request (Registration Request) message to the old AMF (old AMF), and the Registration Request message carries the requested NSSAI (Requested NSSAI).
  • Registration Request Registration Request
  • NSSAI Requested NSSAI
  • the old AMF here refers to the AMF selected by the access network to serve the UE during the registration process, or can be understood as the AMF that serves the UE for the first time in the registration process.
  • the old AMF involved in the present invention may also be called initial AMF (initial AMF) or current AMF (serving AMF).
  • the old AMF executes the primary authentication procedure of the permanent identity of the UE. After the procedure is successful, the old AMF obtains the UE's subscription data from the UDM.
  • the subscription data includes the S-NSSAI subscribed by the UE and indication information corresponding to each S-NSSAI, and the indication information is used to indicate whether the S-NSSAI needs to perform NSSAA.
  • the S-NSSAI and indication information of the subscription in the subscription data of the UE are as shown in Table 1 above.
  • the old AMF can call the servicing operation Nudm_SDM_Get of UDM to obtain the subscription data of the UE, and the UDM sends the subscription data of the UE to the AMF through Nudm_SDM_Get response.
  • step 903 the old AMF requests the NRF to find a suitable PCF according to the Allowed NSSAI and SUPI.
  • Allowed NSSAI includes S-NSSAI that does not require NSSAA in the requested NSSAI.
  • the old AMF can call the NRF service operation Nnrf_NFDiscovery_Request, which carries the SUPI and Allowed NSSAI of the UE.
  • step 904 the NRF determines a suitable PCF, and sends the PCF ID (PCF ID) to the old AMF.
  • NEF determines a suitable PCF based on SUPI and Allowed NSSAI.
  • NRF can return Nnrf_NFDiscovery_Response to old AMF, carrying PCF ID.
  • Step 905 Based on the PCF ID returned by the NRF, the old AMF sends an AM Policy Association Establishment (AM Policy Association) request to the PCF.
  • AM Policy Association AM Policy Association
  • the AM policy association establishment request carries SUPI and Allowed NSSAI.
  • old AMF calls the servicing operation of PCF: Npcf_AMPolicyControl_Create, which carries SUPI, Allowed NSSAI).
  • step 906 the PCF sends an AM policy (AM policy for Allowed NSSAI) and a policy control request trigger (Policy Control Request Triggers) generated based on the Allowed NSSAI to the old AMF.
  • AM policy AM policy for Allowed NSSAI
  • Policy Control Request Triggers Policy Control Request Triggers
  • PCF returns Npcf_AMPolicyControl_Create Response to old AMF, which carries AM policy for Allowed NSSAI and Policy Control Request Triggers.
  • the AM policy is generated by the PCF according to Allowed NSSAI, and the AM policy of this step can also be called AM policy for Allowed NSSAI.
  • AM policy includes but is not limited to: air interface access technology/spectrum selection priority index, user aggregation maximum bit rate, and service area limitation.
  • Policy Control Request Triggers refers to policy control request triggers, or policy event reporting triggers.
  • the corresponding trigger conditions are met (for example, the UE's Allowed NSSAI changes)
  • the old AMF can initiate the AM policy association update process. Thereby updating the corresponding strategy.
  • Step 907 The Registration Accept message sent by the old AMF to the UE carries one or more of allowed NSSAI (Allowed NSSAI), pending NSSAI (Pending NSSAI), and rejected NSSAI (Rejected NSSAI), and Carry the AM policy generated based on the allowed NSSAI.
  • allowed NSSAI Allowed NSSAI
  • pending NSSAI Pending NSSAI
  • rejected NSSAI Rejected NSSAI
  • step 907 the old AMF determines that the S-NSSAI in the requested NSSAI needs to execute NSSAA.
  • the method is the same as that in step 503, and will not be repeated.
  • the old AMF may also send a pending cause value to the UE: waiting for NSSAA, and the cause value is used to indicate to the UE that those S-NSSAIs that require NSSAA are in a pending state.
  • old AMF may also send a rejection reason value to the UE: the current area is not available.
  • Allowed NSSAI includes S-NSSAI in the requested NSSAI that does not require NSSAA, Pending NSSAI includes S-NSSAI in the requested NSSAI that requires NSSAA, and Rejected NSSAI includes the UE in the requested NSSAI that is not available in the current area. S-NSSAI.
  • the old AMF stores the Allowed NSSAI in this step in the context of the UE on the old AMF.
  • step 907 it also includes step 907a, step 907b, and step 907c:
  • Step 907a Based on the PCF ID returned by the NRF, the old AMF sends a UE Policy Association Establishment (UE Policy Association) request to the PCF.
  • UE Policy Association UE Policy Association
  • Npcf_UEPolicyControl Create Request which carries SUPI.
  • step 907b the PCF sends a UE policy (UE policy) to the old AMF.
  • UE policy UE policy
  • PCF returns Npcf_UEPolicyControl Create Response to old AMF, which carries UE policy.
  • the UE policy includes but is not limited to: UE access selection strategy (such as access network discovery and selection strategy), and PDU session selection-related strategies (such as UE routing selection strategy).
  • UE access selection strategy such as access network discovery and selection strategy
  • PDU session selection-related strategies such as UE routing selection strategy
  • Step 907c The old AMF sends a configuration update request (configuration update request) message to the UE, which carries the UE policy.
  • step 908 the old AMF executes the NSSAA process for the pending S-NSSAI.
  • Pending NSSAI S-NSSAI-1+S-NSSAI-2, since both S-NSSAI-1 and S-NSSAI-2 are HPLMN S-NSSAI, then old AMF is against S- NSSAI-1 and S-NSSAI-2 execute the NSSAA process.
  • Pending NSSAI S-NSSAI-A and S-NSSAI-B, since S-NSSAI-A is mapped to S-NSSAI-1, and S-NSSAI-B is mapped to S-NSSAI-2, Then AMF executes the NSSAA process on S-NSSAI-1 and S-NSSAI-2.
  • NSSAA result of S-NSSAI-1 is NSSAA success
  • NSSAA result of S-NSSAI-A is NSSAA success
  • access to S-NSSAI-A is allowed
  • NSSAA result of S-NSSAI-1 is NSSAA Failure
  • NSSAA result of S-NSSAI-A is NSSAA failure
  • access to S-NSSAI-A is denied.
  • NSSAA result of S-NSSAI-2 is NSSAA success
  • NSSAA result of S-NSSAI-B is NSSAA success
  • access to S-NSSAI-B is allowed
  • NSSAA result of S-NSSAI-2 is NSSAA Failure
  • NSSAA failure can also be understood as the result of NSSAA of S-NSSAI-B as NSSAA failure, and access to S-NSSAI-B is denied.
  • step 908 is an optional step. When there is an S-NSSAI that needs to execute the NSSAA process, step 908 is executed. Otherwise, step 908 is not executed.
  • step 908 can be executed multiple times.
  • step 909 after the execution of the NSSAA process is completed, the AMF determines whether the Allowed NSSAI of the UE needs to be updated according to the result of the process. If there is a successful NSSAA slice, the S-NSSAI corresponding to the successful NSSAA slice is added to step 907 and sent to In the Allowed NSSAI of the UE, a new Allowed NSSAI (new Allowed NSSAI) is obtained.
  • the AMF also determines Rejected NSSAI, and the Rejected NSSAI includes the S-NSSAI corresponding to the NSSAA failed slice in the Pending NSSAI.
  • NSSAI-1 NSSAA success
  • S-NSSAI-2 NSSAA failure
  • AMF will store the Allowed NSSAI in the context of the UE in step 907.
  • Add S-NSSAI-1 to the Allowed NSSAI of the UE, that is, the Allowed NSSAI is updated to: S-NSSAI-1+S-NSSAI-3.
  • the rejected NSSAI includes S-NSSAI-2.
  • the AMF is based on the Allowed NSSAI stored in the context of the UE in step 907 , Add S-NSSAI-A to the Allowed NSSAI of the UE, that is, the Allowed NSSAI is updated to: S-NSSAI-A+S-NSSAI-C. And generate a rejected NSSAI.
  • the rejected NSSAI includes S-NSSAI-B. Optionally, it also generates a rejection reason value: NSSAA failed.
  • Step 910 If the current AMF (ie, old AMF) cannot continue to serve the UE, the old AMF needs to trigger the AMF reallocation. At the same time, the old AMF sets indication information in the context of the UE to indicate that the allowed NSSAI change satisfies the Policy Control Request Triggers.
  • the current AMF cannot continue to serve the UE means that the current AMF does not support the new Allowed NSSAI determined in step 709, so the AMF needs to be changed.
  • the old AMF also adds the policy control request triggers (Policy Control Request Triggers) obtained from the PCF to the context of the UE.
  • Policy Control Request Triggers Policy Control Request Triggers
  • Step 911 The old AMF sends a configuration update request message to the UE, which carries new Allowed NSSAI and indication information.
  • the indication information is used to instruct the UE to use the new Allowed NSSAI as the requested NSSAI to initiate a registration process immediately after receiving the new Allowed NSSAI.
  • Step 912 the UE initiates a registration process according to the new Allowed NSSAI and the instruction information.
  • the UE registers with a new AMF (new AMF), that is, the new AMF serves the UE, where the new AMF supports the slice indicated by the new Allowed NSSAI.
  • new AMF new AMF
  • the UE sends a Requested NSSAI during the registration process, and the Requested NSSAI includes the new Allowed NSSAI in step 709.
  • Step 913 the new AMF obtains the context of the UE from the old AMF request.
  • the context of the UE on the old AMF contains the PCF ID and indication information.
  • the indication information is used to indicate that the allowed NSSAI change satisfies the Policy Control Request Triggers. Or it can be understood that the indication information is used to instruct the new AMF to obtain a new policy from the PCF. Therefore, the new AMF obtains the PCF ID and indication information from the old AMF, and triggers the acquisition of an updated policy from the PCF according to the indication information.
  • Step 914 The new AMF determines the new Allowed NSSAI for the UE and stores it in the context of the UE.
  • the new Allowed NSSAI of the UE determined by the new AMF may be the same or different from the new Allowed NSSAI determined by the old AMF in step 709. This is because the new AMF needs to further determine the final Allowed NSSAI for the UE based on the congestion of the current network slice.
  • Step 915 The new AMF decides to send an AM Policy Association Modification (AM Policy Association Modification) request to the PCF according to the indication information in the context of the UE.
  • the AM policy association modification request includes SUPI and new Allowed NSSAI, and the new Allowed NSSAI is the new Allowed NSSAI determined in step 714.
  • the new AMF determines that the allowed NSSAI has changed, and the Policy Control Request Triggers is determined to be triggered, so it re-requests the PCF for a new AM policy.
  • new AMF calls the PCF service operation: Npcf_AMPolicyControl_Update, which carries SUPI, new Allowed NSSAI).
  • step 916 the PCF sends an AM policy (AM policy for new Allowed NSSAI) generated based on the new Allowed NSSAI to the AMF.
  • AM policy AM policy for new Allowed NSSAI
  • PCF returns Npcf_AMPolicyControl_Update Response to new AMF, which carries AM policy for new Allowed NSSAI.
  • Step 917 The new AMF sends a registration acceptance message to the UE, which carries the new Allowed NSSAI and the AM policy generated based on the new Allowed NSSAI.
  • old AMF uses the method of the prior art and Allowed NSSAI to select PCF.
  • the new AMF may trigger the acquisition of a new AM policy from the PCF according to the indication information stored in the context of the UE by the old AMF, and the new AMF may determine the new Allowed NSSAI according to the requested NSSAI, and send the new AM policy to the UE.
  • each network element described above includes hardware structures and/or software modules corresponding to each function.
  • the present invention can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed by hardware or computer software-driven hardware depends on the specific application and design constraint conditions of the technical solution. Professionals and technicians can use different methods for each specific application to implement the described functions, but such implementation should not be considered as going beyond the scope of the present invention.
  • the device 1000 includes The acquiring unit 1010, the determining unit 1020, and the selecting unit 1030. Optionally, it further includes a receiving unit 1040, a sending unit 1050, and a setting unit 1060.
  • the determining unit 1020 is configured to determine the allowed network slice selection auxiliary information NSSAI after the first slice performs slice authentication, where the allowed NSSAI includes the identification information of the slice that the terminal device is allowed to access, and the first slice Among the slices for which access is requested for the terminal device, slices that need to perform slice authentication; a selection unit 1030, configured to select a policy control network element according to the allowed NSSAI; wherein, the communication device serves the allowed NSSAI The corresponding slice.
  • the obtaining unit 1010 is configured to obtain the first policy associated with the allowed NSSAI from the policy control network element.
  • the receiving unit 1040 is configured to receive the requested NSSAI from the terminal device in the registration process before the first slice performs slice authentication, and the requested NSSAI includes all The identification information of the slice that the terminal device requests to access; the determining unit 1020 is further configured to determine that the first slice in the slice that is requested to access needs to perform slice authentication, and then it is determined in the registration process The policy control network element is not selected.
  • the selection unit 1030 is specifically configured to obtain the context of the terminal device from the second mobility management network element, and the context of the terminal device does not include the information of the policy control network element
  • the second mobility management network element is a network element that receives the requested NSSAI from the terminal device during the registration process, and the requested NSSAI includes the identification information of the slice that the terminal device requests to access;
  • the context of the terminal device and the allowed NSSAI select the policy control network element.
  • the allowed NSSAI when the first slice performs slice authentication successfully, includes the identification information of the first slice; or, when the first slice performs slice authentication If the permission fails, the allowed NSSAI does not include the identification information of the first slice.
  • the determining unit 1020 is configured to determine a first NSSAI, where the first NSSAI includes a first allowed NSSAI and a pending NSSAI, or the first NSSAI includes a contracted NSSAI of a terminal device, and the pending NSSAI includes the terminal Identification information of the slice that needs to perform slice authentication among the slices that the device requests to access; the selection unit 1030 is configured to select a policy control network element according to the first NSSAI.
  • the obtaining unit 1010 is configured to obtain the first policy associated with the first allowed NSSAI from the policy control network element.
  • the determining unit 1020 is further configured to determine a second allowed NSSAI after the slice corresponding to the pending NSSAI performs slice authentication, and the second allowed NSSAI includes the Identification information of the slice that successfully performs slice authentication in the pending NSSAI; the obtaining unit 1010 is configured to obtain the second policy associated with the second allowed NSSAI from the policy control network element.
  • the sending unit 1050 is configured to send the second policy to the terminal device if the communication device cannot serve the second allowed NSSAI.
  • the determining unit 1020 is further configured to determine a second allowed NSSAI after the slice corresponding to the pending NSSAI performs slice authentication, and the second allowed NSSAI includes the Identification information of the slice that successfully performs slice authentication in the pending NSSAI;
  • the setting unit 1060 is configured to set first indication information in the context of the terminal device if the communication device cannot serve the second allowed NSSAI, The first indication information is used to instruct the second mobility management network element to obtain a policy from the policy control network element.
  • the obtaining unit 1010 is configured to obtain a context of a terminal device from a first mobility management network element, where the context of the terminal device includes identification information of the policy control network element and first indication information; and, according to the first indication information, Obtain the policy associated with the allowed NSSAI from the policy control network element.
  • the determining unit 1020 is configured to determine the allowed NSSAI.
  • the first indication information is used to instruct the communication device to obtain a policy from the policy control network element.
  • the determining unit 1020 is configured to determine the allowed NSSAI after the first slice performs slice authentication, the allowed NSSAI includes identification information of the slice that the terminal device is allowed to access, and the first slice is the slice that the terminal device requests to access The slice that needs to perform slice authentication; the obtaining unit 1010 is used to obtain the first policy associated with the allowed NSSAI from the policy control network element; the sending unit 1050 is used to store the first policy and instruction information in the context of the terminal device, The indication information is used to instruct the second mobility management network element to send the first policy to the terminal device.
  • the allowed NSSAI when the first slice performs slice authentication successfully, includes the identification information of the first slice; or, when the first slice fails to perform slice authentication, the allowed NSSAI does not include Identification information of the first slice.
  • the determining unit 1020 is configured to determine the allowed NSSAI after the first slice performs slice authentication, the allowed NSSAI includes identification information of the slice that the terminal device is allowed to access, and the first slice is the slice that the terminal device requests to access The slice that needs to perform slice authentication; the setting unit 1060 is used to set the identification information and first indication information of the policy control network element in the context of the terminal device if the communication device cannot serve the allowed NSSAI, and the first indication information is used to indicate The second mobility management network element obtains the policy from the policy control network element.
  • the sending unit 1050 is configured to send the allowed NSSAI and second indication information to the terminal device, where the second indication information is used to instruct the terminal device to register with the second mobility management network element according to the allowed NSSAI.
  • the allowed NSSAI when the first slice performs slice authentication successfully, includes the identification information of the first slice; or, when the first slice fails to perform slice authentication, the allowed NSSAI does not include Identification information of the first slice.
  • each of the above-mentioned units may also be referred to as a module or a circuit, etc., and each of the above-mentioned units may be provided independently, or may be fully or partially integrated.
  • the foregoing receiving unit 1040 and sending unit 1050 may also be implemented by a transceiving unit, or in other words, the receiving unit 1040 and the sending unit 1050 may also be collectively referred to as a transceiving unit.
  • the above-mentioned acquisition unit 1010, determination unit 1020, selection unit 1030, and setting unit 1060 may also be implemented by processing units, or the acquisition unit 1010, determination unit 1020, selection unit 1030, and setting unit 1060 may also be collectively referred to as processing units.
  • the foregoing receiving unit 1040, sending unit 1050, or transceiving unit may also be referred to as a communication interface, and the foregoing processing unit may also be referred to as a processor.
  • the above-mentioned communication device 1000 may further include a storage unit for storing data or instructions (also referred to as codes or programs), and each of the above-mentioned units may interact or couple with the storage unit to implement the corresponding method or Function.
  • the processing unit may read data or instructions in the storage unit, so that the communication device implements the method in the foregoing embodiment.
  • each unit in the device can be all implemented in the form of software called by processing elements; they can also be all implemented in the form of hardware; part of the units can also be implemented in the form of software called by the processing elements, and some of the units can be implemented in the form of hardware.
  • each unit can be a separate processing element, or it can be integrated in a certain chip of the device for implementation.
  • it can also be stored in the memory in the form of a program, which is called and executed by a certain processing element of the device. Function.
  • each step of the above method or each of the above units may be implemented by an integrated logic circuit of hardware in a processor element or implemented in a form of being called by software through a processing element.
  • the unit in any of the above devices may be one or more integrated circuits configured to implement the above methods, for example: one or more application specific integrated circuits (ASICs), or, one or Multiple microprocessors (digital singnal processors, DSPs), or, one or more field programmable gate arrays (Field Programmable Gate Arrays, FPGAs), or a combination of at least two of these integrated circuits.
  • ASICs application specific integrated circuits
  • DSPs digital singnal processors
  • FPGAs Field Programmable Gate Arrays
  • the unit in the device can be implemented in the form of a processing element scheduler
  • the processing element can be a general-purpose processor, such as a central processing unit (CPU) or other processors that can call programs.
  • CPU central processing unit
  • these units can be integrated together and implemented in the form of a system-on-a-chip (SOC).
  • the above receiving unit is an interface circuit of the device for receiving signals from other devices.
  • the receiving unit is an interface circuit used by the chip to receive signals from other chips or devices.
  • the above unit for sending is an interface circuit of the device for sending signals to other devices.
  • the sending unit is an interface circuit used by the chip to send signals to other chips or devices.
  • the mobility management network element includes: a processor 1110, an interface 1130, and optionally, a memory 1120.
  • the interface 1130 is used to implement communication with other devices.
  • the method executed by the mobility management network element in the above embodiment can be implemented by the processor 1110 calling a program stored in a memory (which may be the memory 1120 in the mobility management network element or an external memory). That is, the apparatus for a mobility management network element may include a processor 1110 that calls a program in a memory to execute the method executed by the mobility management network element in the above method embodiment.
  • the processor here may be an integrated circuit with signal processing capability, such as a CPU.
  • the apparatus for the mobility management network element may be implemented by one or more integrated circuits configured to implement the above method. For example: one or more ASICs, or, one or more microprocessors DSP, or, one or more FPGAs, etc., or a combination of at least two of these integrated circuit forms. Or, the above implementations can be combined.
  • the computer program product includes one or more computer instructions.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices.
  • the computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from a website, computer, server, or data center.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or a data center integrated with one or more available media.
  • the usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, and a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid state disk (SSD)).
  • At least one refers to any combination of these items, including any combination of a single item (a) or a plurality of items (a).
  • at least one (piece, species) of a, b, or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or Multiple.
  • Multiple refers to two or more than two, and other quantifiers are similar.
  • the size of the sequence numbers of the above-mentioned processes does not mean the order of execution.
  • the execution order of the processes should be determined by their functions and internal logic, and should not be used in the embodiments of the present invention.
  • the implementation process constitutes any limitation.
  • the disclosed system, device, and method can be implemented in other ways.
  • the device embodiments described above are merely illustrative, for example, the division of the units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components may be combined or It can be integrated into another system, or some features can be ignored or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.
  • the functional units in the various embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.
  • the computer program product includes one or more computer instructions.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices.
  • the computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from a website, computer, server, or data center.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or a data center integrated with one or more available media.
  • the usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, and a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid state disk (SSD)).
  • the various illustrative logic units and circuits described in the embodiments of this application can be implemented by general-purpose processors, digital signal processors, application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, Discrete gates or transistor logic, discrete hardware components, or any combination of the above are designed to implement or operate the described functions.
  • the general-purpose processor may be a microprocessor.
  • the general-purpose processor may also be any traditional processor, controller, microcontroller, or state machine.
  • the processor can also be implemented by a combination of computing devices, such as a digital signal processor and a microprocessor, multiple microprocessors, one or more microprocessors combined with a digital signal processor core, or any other similar configuration. accomplish.
  • the steps of the method or algorithm described in the embodiments of the present application can be directly embedded in hardware, a software unit executed by a processor, or a combination of the two.
  • the software unit can be stored in random access memory (Random Access Memory, RAM), flash memory, read-only memory (Read-Only Memory, ROM), EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM or this Any other storage media in the field.
  • the storage medium may be connected to the processor, so that the processor can read information from the storage medium, and can store and write information to the storage medium.
  • the storage medium may also be integrated into the processor.
  • the processor and the storage medium can be arranged in the ASIC.
  • These computer program instructions can also be loaded on a computer or other programmable data processing equipment, so that a series of operation steps are executed on the computer or other programmable equipment to produce computer-implemented processing, so as to execute on the computer or other programmable equipment.
  • the instructions provide steps for implementing the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.
  • the aforementioned functions described in this application can be implemented in hardware, software, firmware, or any combination of the three. If implemented in software, these functions can be stored on a computer-readable medium, or transmitted on the computer-readable medium in the form of one or more instructions or codes.
  • Computer-readable media include computer storage media and communication media that facilitate the transfer of computer programs from one place to another. The storage medium can be any available medium that can be accessed by a general-purpose or special computer.
  • Such computer-readable media may include, but are not limited to, RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other device that can be used to carry or store instructions or data structures and Other program code media that can be read by general-purpose or special computers, or general-purpose or special processors.
  • any connection can be appropriately defined as a computer-readable medium, for example, if the software is from a website, server, or other remote source through a coaxial cable, fiber optic computer, twisted pair, or digital subscriber line (DSL) Or transmitted by wireless means such as infrared, wireless and microwave are also included in the definition of computer-readable media.
  • DSL digital subscriber line
  • the said disks and discs include compressed disks, laser disks, optical discs, digital versatile discs (English: Digital Versatile Disc, abbreviated as: DVD), floppy disks and Blu-ray discs.
  • Disks usually copy data with magnetism.
  • Discs usually use lasers to copy data optically.
  • the combination of the above can also be contained in a computer readable medium.
  • the functions described in this application can be implemented by hardware, software, firmware, or any combination thereof. When implemented by software, these functions can be stored in a computer-readable medium or transmitted as one or more instructions or codes on the computer-readable medium.
  • the computer-readable medium includes a computer storage medium and a communication medium, where the communication medium includes any medium that facilitates the transfer of a computer program from one place to another.
  • the storage medium may be any available medium that can be accessed by a general-purpose or special-purpose computer.

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)

Abstract

La présente invention concerne un procédé, un appareil et un système de communication. Le procédé comprend les étapes suivantes : après qu'une première tranche effectue une authentification de tranche, un premier élément de réseau de gestion de mobilité détermine des NSSAI admissibles, la première tranche étant une tranche nécessitant une authentification de tranche dans des tranches auxquelles un dispositif terminal demande d'accéder ; et le premier élément de réseau de gestion de mobilité sélectionne un élément de réseau de commande de politique selon les NSSAI admissibles. Sur la base de la solution, avant que le processus d'authentification de tranche ne soit effectué, aucun élément de réseau de commande de politique n'est sélectionné, et après que le processus d'authentification de tranche a été effectué, l'élément de réseau de gestion de mobilité sélectionne l'élément de réseau de commande de politique selon les NSSAI du dispositif terminal final, de manière à éviter le problème de resélection d'un élément de réseau de commande de politique puisque l'élément de réseau de commande de politique sélectionné avant le processus d'authentification de tranche ne prend pas en charge la tranche après le processus d'authentification de tranche. En outre, le problème de resélection de politique peut également être évité, ce qui permet d'économiser des ressources.
PCT/CN2020/075417 2020-02-14 2020-02-14 Procédé, appareil et système de communication WO2021159523A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/075417 WO2021159523A1 (fr) 2020-02-14 2020-02-14 Procédé, appareil et système de communication

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/075417 WO2021159523A1 (fr) 2020-02-14 2020-02-14 Procédé, appareil et système de communication

Publications (1)

Publication Number Publication Date
WO2021159523A1 true WO2021159523A1 (fr) 2021-08-19

Family

ID=77292706

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/075417 WO2021159523A1 (fr) 2020-02-14 2020-02-14 Procédé, appareil et système de communication

Country Status (1)

Country Link
WO (1) WO2021159523A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108323245A (zh) * 2017-06-19 2018-07-24 华为技术有限公司 一种注册及会话建立的方法、终端和amf实体
CN109219111A (zh) * 2017-06-29 2019-01-15 华为技术有限公司 切片选择方法和装置
US20190098537A1 (en) * 2017-09-28 2019-03-28 Weihua QIAO SMF, AMF and UPF Relocation During UE Registration
US20190261260A1 (en) * 2018-02-17 2019-08-22 Huawei Technologies Co., Ltd. System and method for ue context and pdu session context management
US20190313236A1 (en) * 2018-04-09 2019-10-10 Samsung Electronics Co., Ltd. Method and device using network slicing in mobile communication system

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108323245A (zh) * 2017-06-19 2018-07-24 华为技术有限公司 一种注册及会话建立的方法、终端和amf实体
CN109219111A (zh) * 2017-06-29 2019-01-15 华为技术有限公司 切片选择方法和装置
US20190098537A1 (en) * 2017-09-28 2019-03-28 Weihua QIAO SMF, AMF and UPF Relocation During UE Registration
US20190261260A1 (en) * 2018-02-17 2019-08-22 Huawei Technologies Co., Ltd. System and method for ue context and pdu session context management
US20190313236A1 (en) * 2018-04-09 2019-10-10 Samsung Electronics Co., Ltd. Method and device using network slicing in mobile communication system

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
NOKIA, NOKIA SHANGHAI BELL: "Update to PCF discovery and selection", 3GPP DRAFT; S2-188851_WAS_S2-188787_WAS_S2-188130_23501_UPDATE TO PCF DISCOVERY AND SELECTION, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. Sophia-Antipolis, France; 20180820 - 20180824, 26 August 2018 (2018-08-26), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051503045 *

Similar Documents

Publication Publication Date Title
US11564284B2 (en) Communication method, apparatus, and system for determining a target user plan function entity
WO2020224463A1 (fr) Procédé et appareil d'analyse de données
WO2020224622A1 (fr) Procédé et dispositif de configuration d'informations
WO2021223507A1 (fr) Procédé et appareil de communication, et puce
US12041135B2 (en) Session establishment method and apparatus
WO2021042742A1 (fr) Procédé, appareil et système de communication
US20230070712A1 (en) Communication method, apparatus, and system
US20220217611A1 (en) Service Configuration Method, Communication Apparatus, and Communication System
WO2021012736A1 (fr) Procédé, dispositif et système de sélection d'un élément de réseau de gestion de session
WO2020200254A1 (fr) Procédé et appareil de communication
US11956691B2 (en) Communication method, device, and system
US20220272607A1 (en) Network Access Method and Communication Apparatus
WO2021174859A1 (fr) Procédé, dispositif et système de communication
WO2020103517A1 (fr) Procédé, appareil, et système d'obtention d'informations de capacité de terminal
WO2021051420A1 (fr) Procédé et appareil de détermination d'un enregistrement de cache dns
WO2022222745A1 (fr) Procédé et appareil de communication
JP2021524204A (ja) サービス品質監視方法、及びシステム、並びに装置
US20220394595A1 (en) Communication method, apparatus, and system
WO2020001465A1 (fr) Procédé et dispositif de gestion de données utilisateur
WO2022237516A1 (fr) Procédé de communication sans fil et appareil de communication
WO2021218244A1 (fr) Procédé, appareil et système de communication
WO2021159523A1 (fr) Procédé, appareil et système de communication
WO2021081712A1 (fr) Procédé et appareil de requête de dns
WO2023197737A1 (fr) Procédé d'envoi de message, procédé de gestion de pin, appareil de communication et système de communication
WO2023061207A1 (fr) Procédé de communication, appareil de communication et système de communication

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: 20918630

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20918630

Country of ref document: EP

Kind code of ref document: A1