WO2019120109A1 - 一种切片信息更新方法及装置 - Google Patents

一种切片信息更新方法及装置 Download PDF

Info

Publication number
WO2019120109A1
WO2019120109A1 PCT/CN2018/120415 CN2018120415W WO2019120109A1 WO 2019120109 A1 WO2019120109 A1 WO 2019120109A1 CN 2018120415 W CN2018120415 W CN 2018120415W WO 2019120109 A1 WO2019120109 A1 WO 2019120109A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal
slice
network slice
network
network element
Prior art date
Application number
PCT/CN2018/120415
Other languages
English (en)
French (fr)
Inventor
朱方园
李岩
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from CN201811505349.5A external-priority patent/CN109951877B/zh
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP18892843.6A priority Critical patent/EP3709707B1/en
Publication of WO2019120109A1 publication Critical patent/WO2019120109A1/zh
Priority to US16/905,383 priority patent/US11425634B2/en
Priority to US17/880,457 priority patent/US20220377653A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/16—Discovering, processing access restriction or access information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • 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
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08—Mobility data transfer
    • H04W8/12—Mobility data transfer between location registers or mobility servers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/12—Setup of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/18—Management of setup rejection or failure
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data

Definitions

  • the present application relates to the field of mobile communications technologies, and in particular, to a method and an apparatus for updating slice information.
  • the network slice selection process is triggered.
  • the network side selects a network slice that is allowed to access according to the network slice requested by the terminal, the subscription data of the terminal, and the like.
  • the terminal After the network side selects the network slice allowed to access, the terminal notifies the terminal of the selected network slice. If the network side determines that the subscription data of the terminal includes a network slice that is not supported by the Public Land Mobile Network (PLMN), the network side also notifies the terminal of the network slice that is not supported by the PLMN.
  • PLMN Public Land Mobile Network
  • the present application provides a method and an apparatus for updating a slice information, so as to notify a corresponding terminal when a network slice that is not supported by the PLMN is updated to support the PLMN.
  • the present application provides a method for updating a slice information.
  • the method includes: first, the communication network element receives a notification message from the network slice selection network element, the notification message includes identification information of the network slice, and the notification message is used to indicate that the PLMN supports the network slice, wherein the PLMN does not support the network slice. Then, the communication network element notifies the terminal PLMN to support the network slice, and the terminal is the terminal that has requested the network slice failure and has signed the network slice.
  • the communication network element is a mobility management network element or a policy control network element.
  • the network slice selection network element determines that the network slice update that the PLMN has not supported is supported, sends a notification message to the communication network element, where the notification message is used to indicate that the PLMN supports the network slice, and then the communication network element notifies that the network slice is requested.
  • a terminal that failed and signed a network slice The PLMN currently supports the network slice. Therefore, the corresponding terminal is informed that the PLMN currently supports the network slice, and the terminal can use the network slice when there is a demand for the service corresponding to the network slice, which helps to improve the service capability of the terminal.
  • the communication network element may determine the terminal according to the terminal context.
  • the communication network element is a mobility management network element.
  • the method further includes: the mobility management network element adds the identifier information of the network slice to the network slice set of the terminal that is allowed to access. Then, the communication network element notifies the terminal PLMN to support the network slice, and specifically includes: the mobility management network element sends the updated network slice set that is allowed to access to the terminal. Further, the mobility management network element sends indication information to the terminal, the indication information being used to indicate that the PLMN supports the network slice.
  • the mobility management network element sends a configuration update message to the terminal, where the configuration update message includes the updated network slice set that is allowed to access.
  • the configuration update message further includes indication information.
  • the mobility management network element notifies the terminal PLMN to support the network slice by means of the updated network slice set that is allowed to access.
  • the communication network element is a policy control network element.
  • the method further includes: the policy control network element determining the mobility management network element registered by the terminal.
  • the communication network element notifies the terminal PLMN to support the network slice, and the method includes: the policy control network element sends the indication information to the terminal by using the mobility management network element, where the indication information is used to indicate that the PLMN supports the network slice.
  • the policy control network element further receives the identifier information of the network slice sent by the mobility management network element, the identifier information of the mobility management network element, and the identifier information of the terminal.
  • the policy control network element sends the indication information to the terminal, indicating that the PLMN supports the network slice.
  • the present application provides a method for updating slice information.
  • the method includes: the mobility management network element receives an update message from the policy control network element, where the update message includes indication information and identification information of the terminal, where the indication information is used to indicate that the public land mobile network PLMN supports the network slice, wherein the PLMN does not support Network slicing. Then, the mobility management network element notifies the terminal PLMN to support the network slice, and the terminal is the terminal that has requested the network slice failure and has signed the network slice.
  • the notification message is used to indicate that the PLMN supports the network slice, and the mobility management network element sends a notification to the terminal indicated in the notification message: the PLMN currently supports The network is sliced. Therefore, the corresponding terminal is informed that the PLMN currently supports the network slice, and the terminal can use the network slice when there is a demand for the service corresponding to the network slice, which helps to improve the service capability of the terminal.
  • the method further includes: the mobility management network element adds the identifier information of the network slice to the network slice set of the terminal that is allowed to access.
  • the mobility management network element notifies the terminal PLMN to support the network slice, and specifically includes: the mobility management network element sends the updated network slice set that is allowed to access to the terminal.
  • the mobility management network element further sends indication information to the terminal, where the indication information is used to indicate that the PLMN supports the network slice.
  • the mobility management network element sends a configuration update message to the terminal, where the configuration update message includes the updated network slice set that is allowed to access.
  • the configuration update message further includes indication information.
  • the mobility management network element notifies the terminal PLMN to support the network slice by means of the updated network slice set that is allowed to access.
  • the mobility management network element notifies the terminal PLMN to support the network slice, and the mobility management network element sends the NAS message to the terminal, where the NAS message includes the indication information.
  • the method further includes: the mobility management network element sends the identifier information of the terminal, the identifier information of the mobility management network element, and the identifier information of the network slice to the policy control network element.
  • the present application provides a method for updating a slice information.
  • the method includes: the policy control network element receives the identification information of the terminal from the mobility management network element and the identifier information of the network slice, where the network slice is a network slice that is not supported by the current registration area of the terminal. Then, the policy control network element obtains the service area corresponding to the network slice from the network slice selection network element. If the policy control network element learns that the terminal moves to the service area, it notifies the terminal that the network slice is available.
  • the network slice is notified that the terminal is currently available.
  • the network slice is a network slice that is not supported by the area where the terminal does not move to the service area corresponding to the network slice. Therefore, the corresponding terminal is notified: the network slice is currently available, and the terminal can use the network slice when there is a demand for the service corresponding to the network slice, which helps to improve the service capability of the terminal.
  • the method further includes: the policy control network element subscribing to the mobility management network element: when the location of the terminal is updated, the mobility management network element sends the updated location of the terminal to the policy control network element.
  • the policy control network element notifies the terminal that the network slice is currently available, and the method includes: the policy control network element sends the indication information to the terminal by using the mobility management network element, where the indication information is used to indicate that the network slice is available.
  • the present application provides a method for updating a slice information.
  • the method includes: the network slice selection network element determines that the PLMN supports the network slice, wherein the PLMN does not support the network slice. Then, the network slice selection network element sends a notification message to the communication network element, where the notification message includes identification information of the network slice, and the notification message is used to indicate that the PLMN supports the network slice.
  • the communication network element is a policy control network element or a mobility management network element.
  • the network slice selection network element determines that the network slice update that the PLMN has not supported is supported, sends a notification message to the communication network element, where the notification message is used to indicate that the PLMN supports the network slice, and then the communication network element can notify the request.
  • the network slice fails and the network sliced terminal is signed: the PLMN currently supports the network slice. Therefore, the corresponding terminal is informed that the PLMN currently supports the network slice, and the terminal can use the network slice when there is a demand for the service corresponding to the network slice, which helps to improve the service capability of the terminal.
  • the method further includes: the network slice selection network element receives the subscription from the communication network element: when the PLMN supports the network slice, the network slice selection network element notifies the communication network element.
  • the network slice selection network element determines, according to the slice type supported by the mobility management network element in the PLMN, that the mobility management network element supporting the network slice is a communication network element that needs to send a notification message. .
  • the present application provides a method for updating a slice information.
  • the method includes: the mobility management network element receives a notification message from the network slice selection network element, where the notification message includes identifier information of the network slice and identification information of the at least one tracking area, where the network slice is available in the at least one tracking area, The network slice is unavailable in the at least one tracking area; the mobility management network element determines an updated network slice set that is allowed to access, and the updated network slice set that is allowed to access includes the identification information of the network slice, The terminal is located in the registration area of the terminal, and the terminal can access the network slice; the mobility management network element sends the updated network slice set that is allowed to access to the terminal.
  • the terminal can access the network slice, which means that the network slice is available in any tracking area in the registration area of the terminal.
  • the network slice selection network element determines that the network slice is updated to be available by the unavailable update in the at least one tracking area, sending a notification message to the mobility management network element, where the notification message includes the identifier information of the network slice and the at least one tracking area. Identification information, and then the mobility management network element determines an updated network slice set that is allowed to access, the updated network slice set that is allowed to access includes the identification information of the network slice, and the allowed access to send the update to the terminal Network slice collection. Therefore, the corresponding terminal can be informed that the current network segment can be accessed, and the terminal can use the network slice when there is a demand for the service corresponding to the network slice, which helps to improve the service capability of the terminal.
  • the mobility management network element determines that the network slice is available in the registration area of the terminal, and determines that the terminal can access the network slice.
  • the mobility management network element before receiving the notification message from the network slice selection network element, the mobility management network element further stores a network slice set of the terminal that is denied access, and the network slice set of the denied access includes the foregoing network.
  • the identification information of the slice is not limited to the network slice set of the terminal that is denied access.
  • the terminal before the mobility management network element sends the updated network slice set that is allowed to access, the terminal further receives a registration request message from the terminal, where the registration request message includes the identifier information of the network slice.
  • the mobility management network element sends the updated network slice set that is allowed to access to the terminal, where the mobility management network element sends a registration accept message to the terminal, where the registration accept message includes the updated A set of network slices that are allowed to access.
  • the present application provides a method for updating a slice information.
  • the method includes: receiving, by the terminal, a set of network slices allowed to access from a terminal of the mobility management network element and a network slice set for denying access, where the network slice set of the denied access includes identification information of the network slice, where the terminal is located Within the registration area of the terminal; the terminal sends a registration request message to the mobility management network element, the registration request message includes identification information of the network slice; and the terminal receives the updated network slice of the access allowed from the mobility management network element.
  • the set of network segments of the updated allowed access includes the identification information of the network slice, the network slice being available in the registration area of the terminal, the network slice being unavailable in the registration area of the terminal.
  • the terminal may carry the identifier information of the network slice that the terminal has been denied to access in the registration request message. If the mobility management network element determines that the terminal currently supports the network slice, the identifier information of the network slice is added to the update. A set of network slices that are allowed to be accessed and the set of network slices that are allowed to be accessed are sent to the terminal, so that the network can subsequently use the network slice. Therefore, the corresponding terminal can be informed that the current network segment can be accessed, and the network can use the network slice when the terminal needs the service corresponding to the network slice, which helps to improve the service capability of the terminal.
  • the terminal receives the updated set of network slices allowed to access from the mobility management network element, and specifically includes: receiving, by the terminal, a registration accept message from the mobility management network element, where the registration accept message includes The above updated set of network slices that allow access.
  • the application provides a device, which may be a communication network element or a chip.
  • the communication network element may be a mobility management network element or a policy control network element.
  • the device has the functionality to implement the various embodiments of the first aspect described above. This function can be implemented in hardware or in hardware by executing the corresponding software.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • an apparatus comprising: a processor and a memory; the memory is configured to store a computer execution instruction, and when the apparatus is in operation, the processor executes the computer execution instruction stored in the memory to cause the apparatus to execute A slice information updating method as described in any one of the above first aspects.
  • the application provides a device, which may be a mobility management network element or a chip.
  • the device has the functionality to implement the various embodiments of the second aspect described above. This function can be implemented in hardware or in hardware by executing the corresponding software.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • an apparatus comprising: a processor and a memory; the memory is configured to store a computer execution instruction, and when the apparatus is running, the processor executes the computer execution instruction stored in the memory to cause the apparatus to execute A slice information updating method as described in any one of the above second aspects.
  • the application provides a device, which may be a policy control network element or a chip.
  • the device has the functionality to implement the various embodiments of the third aspect described above. This function can be implemented in hardware or in hardware by executing the corresponding software.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • an apparatus comprising: a processor and a memory; the memory is configured to store a computer execution instruction, and when the apparatus is in operation, the processor executes the computer execution instruction stored in the memory to cause the apparatus A slice information updating method as described in any one of the above third aspects is performed.
  • the application provides a device, which may be a network slice selection network element or a chip.
  • the device has the functionality to implement the various embodiments of the fourth aspect described above. This function can be implemented in hardware or in hardware by executing the corresponding software.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • an apparatus comprising: a processor and a memory; the memory is configured to store a computer execution instruction, and when the apparatus is in operation, the processor executes the computer execution instruction stored in the memory to cause the apparatus A slice information updating method as described in any one of the above fourth aspects is performed.
  • the application provides a device, which may be a mobility management network element or a chip.
  • the device has the functionality to implement the various embodiments of the fifth aspect described above. This function can be implemented in hardware or in hardware by executing the corresponding software.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • an apparatus comprising: a processor and a memory; the memory is configured to store a computer execution instruction, and when the apparatus is in operation, the processor executes the computer execution instruction stored in the memory to cause the apparatus A slice information updating method as described in any one of the above fifth aspects is performed.
  • the application provides a device, which may be a terminal or a chip.
  • the device has the function of implementing the various embodiments of the sixth aspect described above. This function can be implemented in hardware or in hardware by executing the corresponding software.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • an apparatus comprising: a processor and a memory; the memory is configured to store a computer execution instruction, and when the apparatus is in operation, the processor executes the computer execution instruction stored in the memory to cause the apparatus
  • a slice information update method as described in any one of the sixth aspects above is performed.
  • the present application also provides a computer readable storage medium having instructions stored therein that, when executed on a computer, cause the computer to perform the methods described in the above aspects.
  • the present application also provides a computer program product comprising instructions which, when run on a computer, cause the computer to perform the methods described in the above aspects.
  • the present application further provides a system comprising the apparatus of the seventh aspect or the eighth aspect, and the apparatus of the thirteenth aspect or the fourteenth aspect.
  • the present application further provides a system comprising the apparatus of the above ninth or tenth aspect, and the apparatus of the thirteenth aspect or the fourteenth aspect.
  • the present application further provides a system comprising the apparatus of the fifteenth aspect or the sixteenth aspect, and the apparatus of the seventeenth aspect or the eighteenth aspect.
  • FIG. 1 is a schematic diagram of a possible network architecture provided by the present application
  • FIG. 2 is a schematic diagram of a specific system architecture provided by the present application.
  • FIG. 3 is a schematic diagram of a first application scenario provided by the present application.
  • FIG. 4 is a schematic diagram of a second application scenario provided by the present application.
  • FIG. 5 is a schematic diagram of a method for updating slice information according to the present application.
  • FIG. 6 is a schematic diagram of another method for updating slice information provided by the present application.
  • FIG. 7 is a schematic diagram of another method for updating slice information provided by the present application.
  • FIG. 8 is a schematic diagram of another method for updating slice information according to the present application.
  • FIG. 9 is a schematic diagram of a third application scenario provided by the present application.
  • FIG. 10 is a schematic diagram of another method for updating slice information provided by the present application.
  • FIG. 11 is a schematic diagram of another method for updating slice information according to the present application.
  • Figure 12 is a schematic diagram of a device provided by the present application.
  • Figure 13 is a schematic view of another apparatus provided by the present application.
  • Figure 14 is a schematic view of another apparatus provided by the present application.
  • Figure 15 is a schematic view of another apparatus provided by the present application.
  • Figure 16 is a schematic diagram of another apparatus provided by the present application.
  • Figure 17 is a schematic diagram of another apparatus provided by the present application.
  • the network architecture and the service scenario described in the embodiments of the present application are for the purpose of more clearly illustrating the technical solutions of the embodiments of the present application, and do not constitute a limitation of the technical solutions provided by the embodiments of the present application.
  • the technical solutions provided by the embodiments of the present application are equally applicable to similar technical problems.
  • the network architecture includes a terminal, a mobility management network element, a policy control network element, and a network slice selection network element.
  • the mobility management network element and the policy control network element may be referred to as a communication network element, that is, the communication network element in the present application is a mobility management network element or a policy control network element.
  • a terminal is a wireless transceiver that can be deployed on land, indoors or outdoors, handheld or on-board; it can also be deployed on the water (such as ships); it can also be deployed in the air (such as airplanes, balloons, and satellites). Superior).
  • the terminal may be a mobile phone, a tablet, a computer with wireless transceiver function, a virtual reality (VR) terminal, an augmented reality (AR) terminal, industrial control (industrial control) Wireless terminal, wireless terminal in self driving, wireless terminal in remote medical, wireless terminal in smart grid, wireless terminal in transportation safety, A wireless terminal in a smart city, a wireless terminal in a smart home, and the like.
  • the mobility management network element is responsible for user mobility management, including mobile state management, assigning user temporary identity, authenticating and authorizing users.
  • the policy control network element includes user subscription data management function, policy control function, charging policy control function, and quality of service (QoS) control.
  • QoS quality of service
  • the network slice selects the network element and is responsible for determining the network slice instance and selecting the mobility management network element.
  • the above functions can be either a network component in a hardware device, a software function running on dedicated hardware, or a virtualization function instantiated on a platform (for example, a cloud platform).
  • the mobility management network element may be referred to as an access and mobility management function (AMF) network element at 5G.
  • the policy control network element can be called a Policy Control Function (PCF) network element at 5G.
  • the network slice selection network element can be called a Network Slice Selection Function (NSSF) network element at 5G.
  • the mobility management network element may still be referred to as an AMF network element or have other names.
  • the policy control network element may still be referred to as a PCF network element or have other names, and the network slice selects the network element. It can still be called an NSSF network element or has other names, which is not limited in this application.
  • the mobility management network element is referred to as an AMF network element
  • the policy control network element is referred to as a PCF network element
  • the network slice selection network element is referred to as an NSSF network element as an example for description.
  • the AMF network element is simply referred to as AMF
  • the PCF network element is abbreviated as PCF
  • the NSSF network element is abbreviated as NSSF. That is, the AMF described in this application can be replaced with a mobility management network element, and the PCF can be replaced with a policy control network element, and the NSSF can be replaced with a network slice selection network element.
  • FIG. 2 it is a schematic diagram of a specific system architecture based on the system architecture shown in FIG. 1.
  • the system architecture includes a terminal, a radio access network device, and a control plane network element of the core network.
  • the control plane network elements of the core network include AMF, PCF, and NSSF.
  • a RAN device is a device that provides wireless communication functions for a terminal.
  • the RAN device includes, for example but not limited to: a next-generation base station (g node B, gNB), an evolved node B (eNB), a radio network controller (RNC), and a node B (node B) in 5G. , NB), base station controller (BSC), base transceiver station (BTS), home base station (for example, home evolved node B, or home node B, HNB), baseband unit (BBU) ), transmitting and receiving point (TRP), transmitting point (TP), mobile switching center, and the like.
  • g node B next-generation base station
  • eNB evolved node B
  • RNC radio network controller
  • node B node B
  • BSC base station controller
  • BTS base transceiver station
  • home base station for example, home evolved node B, or home node B, HNB
  • BBU baseband unit
  • TRP transmitting and receiving point
  • the RAN device can be used to forward a Non Access Stratum (NAS) message for communication between the terminal and the AMF.
  • NAS Non Access Stratum
  • the slice information update provided by the present application will be specifically described below in conjunction with FIG. 1 to FIG. 2 to solve the problems mentioned in the background art. It should be noted that the present application is not limited to the system architecture shown in FIG. 1 to FIG. 2, and can be applied to other communication systems in the future, such as a 6G system architecture. Moreover, the names of the respective network elements used in the above application may remain the same in the future communication system, but the names may change.
  • 3GPP 3rd Generation Partnership Project
  • 3GPP 3rd Generation Partnership Project
  • network slices do not interact with each other. For example, a large number of burst meter reading services should not affect normal mobile broadband services.
  • 3GPP In order to meet the diversity needs and isolation between slices, relatively independent management and operation and maintenance between services 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 user When the core network deploys a network slice, the user initially attaches (or registers) to the network, triggering the selection process of the network slice.
  • the selection process of the slice depends on the user's subscription data, local configuration information, roaming agreement, operator's policy, and so on. In the selection process of the network slice, it is necessary to comprehensively consider the above parameters in order to select the optimal slice type for the terminal.
  • the terminal may provide the requested network slice to the core network, and the core network selects a network slice instance for the terminal.
  • the network slice requested by the terminal may be represented by a requested network slice selection assistance information (requested NSSAI).
  • the requested NSSAI is composed of one or more single network slice selection assistance information (S-NSSAI).
  • S-NSSAI single network slice selection assistance information
  • Each S-NSSAI is used to identify a network slice type. It can also be understood as S-NSSAI. To identify the network slice, or it can be understood that the S-NSSAI is the identification information of the network slice.
  • the terminal stores a pre-configured NSSAI locally before registering the network.
  • the S-NSSAI included in the configured NSSAI and the S-NSSAI included in the NSSAI signed by the terminal are both S-NSSAI defined by the HPLMN.
  • One possible implementation method is that the S-NSSAI included in the configured NSSAI is a subset or a complete set in the S-NSSAI included in the NSSAI that the terminal subscribes to. For example, if the NSSAI of the terminal is ⁇ S-NSSAI1, S-NSSAI2, S-NSSAI3, S-NSSAI4, S-NSSAI5 ⁇ , then the configured NSSAI is ⁇ S-NSSAI1, S-NSSAI2, S-NSSAI3, S-NSSAI4. , a subset or complete set of S-NSSAI5 ⁇ .
  • the terminal carries a requested NSSAI when initially registered in the network, wherein the requested NSSAI is a subset or a complete set of S-NSSAI included in the configured NSSAI.
  • the configured NSSAI is ⁇ S-NSSAI1, S-NSSAI2, S-NSSAI3, S-NSSAI4 ⁇
  • the requested NSSAI is a subset or a complete set of ⁇ S-NSSAI1, S-NSSAI2, S-NSSAI3, S-NSSAI4 ⁇ .
  • the core network element (such as AMF or NSSF) comprehensively judges the network slice set that is allowed to access according to the subscription data of the terminal, the requested NSSAI of the terminal, the roaming protocol, and the local configuration.
  • the allowed network slice set can be represented by an allowed NSSAI, and the allowed NSSAI includes an S-NSSAI that is a subset or a complete set of S-NSSAIs included in the NSSAI of the terminal, or allowed NSSAI is requested NSSAI. A subset or a complete set of S-NSSAs included in .
  • the core network element sends the allowed NSSAI to the terminal, for example, it is carried in the registration accept message and sent to the terminal.
  • the S-NSSAI can be selected from the allowed NSSAI to initiate the service.
  • the core network element when the core network element sends the allowed NSSAI to the terminal, it also returns to the terminal the reason why the rejected NSSAI and each S-NSSAI in the rejected NSSAI are rejected.
  • the following is an example.
  • the subscription NSSAI of the terminal is ⁇ S-NSSAI1, S-NSSAI2, S-NSSAI3, S-NSSAI4 ⁇ , and the terminal is currently located in the service scope of AMF set 1.
  • the network side includes two AMF sets, which are AMF set 1 and AMF set 2.
  • the network slice supported by any AMF in AMF set 1 is: ⁇ Slice 1, Slice 2 ⁇
  • the network slice supported by any AMF in AMF set 2 is: ⁇ Slice 4 ⁇
  • the network also Includes a slice 3 that is temporarily not supported by the PLMN. The reason for temporarily not supporting may be temporarily not deployed or temporarily closed. If the slice 3 is later updated to PLMN support, ie updated to be available, then the slice 3 belongs to AMF set 1.
  • slice 1, slice 2, slice 3, and slice 4 can be identified by S-NSSAI1, S-NSSAI2, S-NSSAI3, and S-NSSAI4, respectively. That is, S-NSSAI1 is the identification information of slice 1, S-NSSAI2 is the identification information of slice 2, S-NSSAI3 is the identification information of slice 3, and S-NSSAI4 is the identification information of slice 4.
  • Each network slice corresponds to one or more Session Management Function (SMF) network elements and one or more User Plane Function (UPF) network elements.
  • SMF Session Management Function
  • UPF User Plane Function
  • slice 1 corresponds to SMF1 and UPF1
  • slice 2 corresponds to SMF2 and UPF2
  • slice 3 corresponds to SMF3 and UPF3
  • slice 4 corresponds to SMF4 and UPF4.
  • the currently accessed AMF (the AMF is also referred to as the AMF serving the terminal) is an AMF in the AMF set 1, and the AMF serving the terminal is provided.
  • the slices that can be used are Slice 1 and Slice 2.
  • the slice 3 may be referred to as a network slice that is not supported by the PLMN, or a network slice that is not temporarily supported by the PLMN, or a network slice that is not currently supported by the PLMN.
  • the slice 3 can also be used by the AMF serving the terminal.
  • the slice 4 may A network slice that is not supported by the current registration area of the terminal. It can also be understood that the slice 4 cannot be used by the terminal at the current location.
  • the slice 4 can be used by the terminal only when the terminal moves within the range that the slice 4 can serve. For example, when the terminal moves to the coverage of an AMF in the AMF set 2, the terminal can use the slice 4 as long as the terminal registers with the AMF, that is, the slice 4 can be used to initiate a business process.
  • the slice 4 is isolated from the slice 1, the slice 2, and the slice 3. It can also be understood that when the terminal uses the slice 4, the slice 1, the slice 2 or the slice 3 cannot be used; when the terminal uses the slice 1, the slice 2 or the slice 3, the slice 4 cannot be used.
  • slice 3 cannot be used in the PLMN, since slice 1, slice 2, and slice 3 belong to AMF set1, slice 3 and slice 1 and slice 2 are not isolated from each other.
  • the subscription NSSAI of the terminal is ⁇ S-NSSAI1, S-NSSAI2, S-NSSAI3, S-NSSAI4 ⁇ , and the terminal is currently located in the service range of the AMF set 1, the terminal is registered with the requested request.
  • the NSSAI is ⁇ S-NSSAI1, S-NSSAI2, S-NSSAI3, S-NSSAI4 ⁇
  • the slice 3 identified by the S-NSSAI3 is a network slice that is not supported by the PLMN
  • the slice 4 identified by the S-NSSAI4 is the current registration area of the terminal. Supported network slices.
  • the information sent by the core network element such as NSSF or AMF to the terminal is as follows:
  • Rejected NSSAI ⁇ S-NSSAI3:1, S-NSSAI4:2 ⁇ .
  • the allowed NSSAI includes the identification information of the network slice allowed to be accessed by the core network side, that is, the core network side allows the terminal to access the slice 1 and the slice 2.
  • the rejected NSSAI includes the identification information of the network slice that the core network side refuses to access, that is, the core network side rejects the terminal access slice 3 and slice 4.
  • the reason for rejecting the terminal accessing slice 3 is 1 and the reason for rejecting the terminal accessing slice 4 is 2.
  • the reason value 1 indicates that the PLMN does not support, and the reason value 2 indicates that the current registration area of the terminal is not supported.
  • the core network element may also send an isolation rule (or a coexistence rule) to the terminal: S-NSSAI1, S-NSSAI2, S-NSSAI3, and S-NSSAI4 are isolated from each other (or referred to as non-coexistence).
  • an isolation rule or a coexistence rule
  • the coexistence rule may also be pre-configured on the terminal, which is not limited in this application.
  • the terminal can know according to the coexistence rule that: NSSAI1, S-NSSAI2, S-NSSAI3, and S-NSSAI4 are isolated from each other (or are not coexisting). Then, the terminal does not request NSSAI1, S-NSSAI2, S-NSSAI3, and S-NSSAI4 at the same time. Based on the scenario of FIG.
  • the subscription NSSAI of the terminal is ⁇ S-NSSAI1, S-NSSAI2, S-NSSAI3, S-NSSAI4 ⁇ and the terminal is currently located in the service range of AMF set 1, and the terminal is registered.
  • the requested NSSAI carried in the network is ⁇ S-NSSAI1, S-NSSAI2, S-NSSAI3 ⁇ , and the information sent by the core network element (such as NSSF or AMF) to the terminal is as follows:
  • the rejected NSSAI includes the identification information of the network slice that the core network side refuses to access, that is, the core network side rejects the terminal access slice 3.
  • the cause value of 1 indicates that the PLMN does not support it.
  • FIG. 4 a schematic diagram of a second application scenario provided by the present application is provided.
  • the main difference between the application scenario and the application scenario shown in FIG. 3 is that the slice 3 that is not supported by the PLMN belongs to the AMF set 2. Therefore, in this application scenario, slice 1, slice 2, and slice 4 are isolated from each other. That is, when the terminal uses slice 1 or slice 2, slice 4 cannot be used, and when the terminal uses slice 4, slice 1 or slice 2 cannot be used.
  • slice 1, slice 2, slice 3, and slice 4 are isolated from each other. That is, when the terminal uses slice 1 or slice 2, slice 3 or slice 4 cannot be used; when the terminal is using slice 3 or slice 4, slice 1 or slice 2 cannot be used.
  • the subscription NSSAI of the terminal is ⁇ S-NSSAI1, S-NSSAI2, S-NSSAI3, S-NSSAI4 ⁇ and the terminal is currently in the service range of AMF set 1
  • the ⁇ S-NSSAI1, S-NSSAI2, S-NSSAI3, S-NSSAI4 ⁇ , and the slice 3 identified by the S-NSSAI3 is a network slice that is not supported by the PLMN, and the slice 4 identified by the S-NSSAI4 is not supported by the current registration area of the terminal.
  • the information sent by the core network element such as NSSF or AMF
  • Rejected NSSAI ⁇ S-NSSAI3:1, S-NSSAI4:2 ⁇ .
  • the allowed NSSAI includes the identification information of the network slice allowed to be accessed by the core network side, that is, the core network side allows the terminal to access the slice 1 and the slice 2.
  • the rejected NSSAI includes the identification information of the network slice that the core network side refuses to access, that is, the core network side rejects the terminal access slice 3 and slice 4.
  • the reason for rejecting the terminal accessing slice 3 is 1 and the reason for rejecting the terminal accessing slice 4 is 2.
  • the reason value 1 indicates that the PLMN does not support, and the reason value 2 indicates that the current registration area of the terminal is not supported.
  • the core network element may also send an isolation rule (or a coexistence rule) to the terminal: S-NSSAI1, S-NSSAI2 and S-NSSAI3, and S-NSSAI4 are isolated from each other (or referred to as non-coexistence).
  • an isolation rule or a coexistence rule
  • the present application provides a plurality of methods for updating slice information, which are respectively described in detail below.
  • a slice information update method provided by the present application is provided.
  • the method can be used to solve the problem of how the core network side notifies the terminal and which terminals are notified when the slice 3 that is not supported by the PLMN as shown in FIG. 3 is updated to support the PLMN.
  • the terminal initiates a registration process, and the core network side returns allowed NSSAI and rejected NSSAI, wherein the rejected NSSAI includes identification information of a slice (eg, slice 3 in FIG. 3) (eg, S- NSSAI3) and the reason value of the rejection, the reason value of the rejection indicates that the slice is a network slice that is not supported by the PLMN.
  • the rejected NSSAI includes identification information of a slice (eg, slice 3 in FIG. 3) (eg, S- NSSAI3) and the reason value of the rejection, the reason value of the rejection indicates that the slice is a network slice that is not supported by the PLMN.
  • the AMF currently registered by the terminal ie, the AMF serving the terminal
  • the information stored on the terminal includes: allowed NSSAI, rejected NSSAI (including S-NSSAI3), and reject reason values.
  • the information stored on the AMF serving the terminal includes: the requested NSSAI of the terminal, and the NSSAI of the subscription of the terminal.
  • the rejected NSSAI returned by the core network side may actually include the identification information of the slice 4 (for example, S-NSSAI4) and the reason value of the rejection, the reason value of the rejection.
  • the network slice is not supported by indicating that the slice is the current registration area of the terminal.
  • description will be made only when the slice 3 indicated by the S-NSSAI3 in the rejected NSSAI is updated to be available for the PLMN.
  • the slice 4 indicated by the S-NSSAI4 in the rejected NSSAI is updated to be available for the current registration area of the terminal, refer to the related description of the embodiment shown in FIG. 8 .
  • the terminals In the network, there are one or more terminals as described above. Therefore, if the slice update that is not supported by the PLMN is subsequently supported by the PLMN, the terminals that have requested the network slice but are rejected should be notified.
  • the slice information update method shown in FIG. 5 includes the following steps:
  • step 501 the NSSF determines that the PLMN supports the network slice.
  • the NSSF can learn from the network management system (operation, administration and maintenance, OAM) that the network slice that the PLMN originally does not support is updated to be supported by the PLMN.
  • OAM operation, administration and maintenance
  • the NSSF learns from the network management system that slice 3 of Figure 3 is supported by PLMN not supported for updating.
  • a possible implementation manner is that the operator deploys the network resource corresponding to the slice 3 at a certain time.
  • the network resource may include the SMF network element corresponding to the slice 3, the UPF network element, and the like.
  • the network management system sends a notification message to the NSSF, where the notification message includes the identification information of the slice 3 and the indication information: the slice 3 is not supported by the PLMN for updating to the PLMN.
  • the NSSF learns from the network management system that the slice 3 is not supported by the PLMN for updating to PLMN support.
  • step 502 the NSSF sends a notification message to the AMF, and the AMF receives the notification message from the NSSF.
  • the NSSF needs to send a notification message to the specific AMF, where the notification message includes the identifier information of the network slice determined in the foregoing step 501, and the notification message is used to indicate that the PLMN supports the network slice.
  • the notification message includes S-NSSAI3 for indicating that the PLMN currently supports slice 3.
  • the AMF that needs to send the notification message may be determined according to any of the following methods, that is, which AMF needs to be sent to the notification message:
  • the NSSF determines, according to the slice type supported by the AMF in the PLMN, that the AMF supporting the network slice is an AMF that needs to send a notification message.
  • the method is used. Since the AMF in the AMF set 1 supports the slice 3, the NSSF determines that the AMF that needs to send the notification message includes the AMF in the AMF set 1, that is, the NSSF determines that it needs to be set to the AMF. The AMF in (for example, all AMFs) sends a notification message. Of course, as an implementation manner, it may also be determined that the AMF that needs to send the notification message includes a part of the AMF in the AMF set 1.
  • the AMF determined by the NSSF to send the notification message also includes these AMFs.
  • the NSSF determines that the AMF that has subscribed to the NSSF to the above network slice is the AMF that needs to send a notification message.
  • the AMF that has subscribed to the NSSF for the above network slice means that the AMF subscribes to the NSSF: when the PLMN supports the network slice, the NSSF notifies the AMF.
  • This network slice is not supported by the above PLMN, but has been updated to support network slices. For example, slice 3 of Figure 3.
  • the AMF that provides the service for the terminal determines in the registration process of the terminal that the core network rejects the request of the network slice that is not supported by the PLMN
  • the NSSF notifies the AMF.
  • the AMF that provides services to the terminal may be subscribed to the NSSF prior to step 501.
  • the AMF that provides the service to the terminal sends a subscription request message to the NSSF, where the subscription request message includes the identifier of the AMF and the identifier information of the network slice, and the network slice is the network slice that the core network network rejects the terminal request to use.
  • the AMF serving the terminal invokes the subscription service by transmitting the AMF identification information and the network slice identification information to the NSSF: when the PLMN supports the network slice, the NSSF notifies the AMF.
  • the NSSF determines that the network slice update that is not supported by the PLMN is supported, it is determined that the AMF that sent the subscription request message to the NSSF or invokes the subscription service is the AMF that needs to send the notification message.
  • the NSSF can determine the AMF that needs to send the notification message. For example, if the method 1 is used, the determined AMF that needs to send the notification message includes: an AMF that supports the above network slice. If the method 2 is used, the determined AMF that needs to send the notification message includes: the AMF that has subscribed to the NSSF for the status of the network slice.
  • step 503 the AMF notifies the terminal PLMN to support the network slice.
  • the AMF in the step 503 is the AMF that receives the notification message in the above step 502.
  • the terminal that the AMF needs to notify includes a terminal that has requested the above network slice failure and has signed the above network slice.
  • the AMF can determine the terminal that needs to be notified according to the context of the terminal stored by the AMF.
  • the PLMN does not support, The core network thus rejects the terminal's request for the network slice. Therefore, when the network slice is not supported by the PLMN for updating to the PLMN, the AMF serving the terminal needs to notify the terminal PLMN to support the network slice.
  • the AMF can notify the terminal by:
  • the AMF adds the identification information of the network slice to the set of network slices allowed by the terminal, that is, the allowed NSSAI, and then sends the updated allowed NSSAI to the terminal.
  • the allowed NSSAI sent to the terminal before the AMF is ⁇ S-NSSAI1, S-NSSAI 2 ⁇ , and the rejected NSSAI sent to the terminal includes S-NSSAI3.
  • an updated allowed NSSAI may be generated, including ⁇ S-NSSAI1, S-NSSAI 2, S-NSSAI 3 ⁇ , and then an update is sent to the terminal. Allowed NSSAI.
  • the updated allowed NSSAI may be sent to the terminal in a configuration update message, and after receiving the configuration update message, the terminal obtains the updated allowed NSSAI, so that the slice 3 has been learned.
  • the PLMN does not support updating to PLMN support, so the slice 3 can be used to initiate a service request procedure.
  • the AMF can immediately send the updated allowed NSSAI to the terminal.
  • the AMF may send the updated allowed NSSAI to the corresponding terminal after determining the updated allowed NSSAI according to the local configuration information.
  • the AMF sends the updated NSSAI to the terminal, and sends the indication information to the terminal, where the indication information is used to indicate that the PLMN supports the network slice.
  • the indication information may be generated by the AMF, or may be generated by the NSSF and sent to the AMF through the notification message of the foregoing step 502.
  • the AMF may also not immediately send the updated allowed NSSAI to the terminal.
  • the AMF stores the updated allowed NSSAI according to the local configuration information, and then waits for the terminal to initiate the registration update process, and sends the updated allowed NSSAI to the terminal in the registration update process.
  • the AMF is first determined, and then the notification message is sent to the determined AMF, where the notification message is used to indicate that the PLMN supports the network slice, and then receives the notification.
  • the AMF of the message informs the terminal that was registered in the AMF and has requested the network slice but was rejected: the PLMN currently supports the network slice. Therefore, when the network slice that is not supported by the PLMN is updated to be supported by the PLMN, the corresponding AMF is notified to the corresponding terminal, and then the terminal can use the network slice when there is a demand for the service corresponding to the network slice, which is helpful to improve.
  • the business capabilities of the terminal are examples of the terminal.
  • another slice information update method provided by the present application is provided.
  • the method can be used to solve the problem of how the core network side notifies the terminal and which terminals are notified when the slice 3 that is not supported by the PLMN as shown in FIG. 3 is updated to support the PLMN.
  • the terminal initiates a registration process, and the core network side returns allowed NSSAI and rejected NSSAI, wherein the rejected NSSAI includes identification information of a slice (eg, slice 3 in FIG. 3) (eg, S- NSSAI3) and the reason value of the rejection, the reason value of the rejection indicates that the slice is a network slice that is not supported by the PLMN.
  • the rejected NSSAI includes identification information of a slice (eg, slice 3 in FIG. 3) (eg, S- NSSAI3) and the reason value of the rejection, the reason value of the rejection indicates that the slice is a network slice that is not supported by the PLMN.
  • the AMF currently registered by the terminal (that is, the AMF serving the terminal) is an AMF in the AMF set (for example, AMF set1 in FIG. 3).
  • the information stored on the terminal includes: allowed NSSAI, rejected NSSAI (including S-NSSAI3), and reject reason values.
  • the information stored on the AMF serving the terminal includes: the requested NSSAI of the terminal, and the NSSAI of the subscription of the terminal.
  • the rejected NSSAI returned by the core network side may actually include the identification information of the slice 4 (for example, S-NSSAI4) and the reason value of the rejection, the reason value of the rejection.
  • the network slice is not supported by indicating that the slice is the current registration area of the terminal.
  • description will be made only when the slice 3 indicated by the S-NSSAI3 in the rejected NSSAI is updated to be available for the PLMN.
  • the slice 4 indicated by the S-NSSAI4 in the rejected NSSAI is updated to be available for the current registration area of the terminal, refer to the related description of the embodiment shown in FIG. 8 .
  • the terminals In the network, there are one or more terminals as described above. Therefore, if the slice update that is not supported by the PLMN is subsequently supported by the PLMN, the terminals that have requested the network slice but are rejected should be notified.
  • the slice information update method shown in FIG. 6 includes the following steps:
  • step 601 the NSSF determines that the PLMN supports the network slice.
  • step 601 The specific implementation of the step 601 is the same as the step 501, and the foregoing description may be referred to.
  • step 602 the NSSF sends a notification message to the PCF, and the PCF receives the notification message from the NSSF.
  • the NSSF needs to send a notification message to the specific PCF, where the notification message includes the identifier information of the network slice determined in the foregoing step 601, and the notification message is used to indicate that the PLMN supports the network slice.
  • the notification message includes S-NSSAI3 for indicating that the PLMN supports slice 3.
  • the PCF that needs to send the notification message may be determined according to the following manner:
  • the NSSF determines that the PCF that has subscribed to the NSSF to the network slice is the PCF that needs to send the notification message, that is, determines which PCFs need to send the notification message.
  • step A the AMF sends a notification message to the PCF, and the PCF receives the notification message from the AMF.
  • the AMF when the AMF that provides the service for the terminal determines in the registration process of the terminal that the core network rejects the request of the network slice that is not supported by the PLMN, the AMF belongs to the AMF.
  • the PCF sends a notification message, which is used to trigger the PCF to subscribe to the NSSF for the status of the network slice.
  • the notification message includes identification information of the terminal, identification information of the AMF, and identification information of the network slice.
  • the PCF then stores the identification information of the terminal, the association information of the AMF and the identification information of the network slice.
  • Step B The PCF subscribes to the NSSF: When the PLMN supports the network slice, the NSSF notifies the PCF.
  • the PCF may send a subscription request message to the NSSF, where the subscription request message includes an identifier of the PCF and identifier information of the network slice, where the network slice is a network slice that the core network network rejects the terminal request to use.
  • the PCF invokes the subscription service by sending the identification information of the PCF and the identification information of the network slice to the NSSF: when the PLMN supports the network slice, the NSSF notifies the PCF.
  • the NSSF determines that the network slice update that is not supported by the PLMN is supported, it is determined that the PCF that has sent the subscription request message to the NSSF or invokes the subscription service is the PCF that needs to send the notification message.
  • step 603 the PCF notifies the terminal PLMN to support the network slice.
  • the PCF in the step 603 is the PCF that receives the notification message from the NSSF in the above step 602.
  • the terminal that the PCF needs to notify includes a terminal that has requested the above network slice failure and has signed the above network slice.
  • the PCF may send indication information to the terminal through the AMF, where the indication information is used to indicate that the PLMN supports the network slice. That is, step 603 can be replaced by the following steps 603a-603b:
  • step 603a the PCF sends an update message to the AMF, and the AMF receives the update message from the PCF.
  • the update message includes indication information and identification information of the terminal, the indication information is used to indicate that the PLMN supports the network slice. The network slice was not supported by the PLMN.
  • the PCF first determines the terminal to be notified and the AMF registered by the terminal according to the context of the terminal stored by the PCF. For example, in the example of performing step A-step B above, when the PCF receives the notification message of the AMF, the notification message includes the identification information of the terminal, the identification information of the AMF, and the identification information of the network slice, and the PCF may store the terminal.
  • the identification information the association relationship between the identification information of the AMF and the identification information of the network slice. Therefore, the PCF may determine the identification information of the terminal that needs to be included in the update message of step 603a according to the stored association relationship, and determine which AMFs need to send the update message to the step 603a.
  • the PCF stores the information as shown in Table 1:
  • Terminal identification information AMF identification information Network slice identification information Terminal 1 AMF1 S-NSSAI3 Terminal 2 AMF1 S-NSSAI3 Terminal 3 AMF2 S-NSSAI3
  • terminal 1 and terminal 2 are registered in AMF1
  • terminal 3 is registered in AMF2
  • AMF1 and AMF2 are AMFs in AMF set1 shown in FIG.
  • Terminal 1 - Terminal 3 in Table 1 is a terminal recorded by the PCF that has requested slice 3 identified by S-NSSAI3 and is rejected.
  • step A the AMF1 sends a notification message to the PCF1, and the notification message includes: (terminal 1, AMF1, S-NSSAI3).
  • Step B The PCF subscribes to the NSSF: When the PLMN supports the slice 3 identified by the S-NSSAI3, the NSSF notifies the PCF1.
  • the PCF1 When the PCF1 subscribes to the NSSF, it also sends the identification information of the PCF1 and the S-NSSAI3 to the NSSF.
  • step A the AMF1 sends a notification message to the PCF1, and the notification message includes: (terminal 2, AMF1, S-NSSAI3).
  • Step B The PCF subscribes to the NSSF: When the PLMN supports the slice 3 identified by the S-NSSAI3, the NSSF notifies the PCF1.
  • the PCF1 When the PCF1 subscribes to the NSSF, it also sends the identification information of the PCF1 and the S-NSSAI3 to the NSSF.
  • step A the AMF2 sends a notification message to the PCF1, and the notification message includes: (terminal 3, AMF2, S-NSSAI3).
  • Step B The PCF subscribes to the NSSF: When the PLMN supports the slice 3 identified by the S-NSSAI3, the NSSF notifies the PCF1.
  • the PCF1 When the PCF1 subscribes to the NSSF, it also sends the identification information of the PCF1 and the S-NSSAI3 to the NSSF.
  • step B since the steps B of the above-mentioned three operations are the same, in a specific implementation, it is also possible to perform step B only at the first time and step B at the second and third times.
  • step 603b the AMF informs the terminal PLMN to support the network slice, and the terminal is a terminal that has requested network slice failure and has signed the network slice.
  • the AMF is the AMF that receives the update message from the PCF in the above step 603a, and the terminal is the terminal indicated by the identification information of the terminal carried in the update message of the above step 603a.
  • step 603b needs to be performed three times:
  • AMF1 informs terminal 1: PLMN supports slice 3 identified by S-NSSAI3.
  • the AMF may notify the terminal in the following manner, that is, the foregoing first, second, and third executions may be implemented as follows:
  • the AMF adds the identification information of the network slice to the set of network slices allowed by the terminal, that is, the allowed NSSAI, and then sends the updated allowed NSSAI to the terminal.
  • the allowed NSSAI For specific implementation details of the implementation, refer to the related description in step 503 in the foregoing embodiment shown in FIG. 5, and details are not described herein again.
  • the PCF is determined first, and then the notification message is sent to the determined PCF, where the notification message is used to indicate that the PLMN supports the network slice, and then receives the notification.
  • the PCF of the message notifies the terminal that has requested the network slice but is rejected: the PLMN currently supports the network slice. Therefore, when the network slice update that is not supported by the PLMN is supported by the PLMN, the corresponding terminal is notified by the corresponding PCF, and then the terminal can use the network slice when there is a demand for the service corresponding to the network slice, which is helpful to improve.
  • the business capabilities of the terminal are examples of the terminal.
  • the method can be used to solve the problem of how the core network side notifies the terminal and which terminals are notified when the slice 3 that is not supported by the PLMN as shown in FIG. 4 is updated to support the PLMN.
  • the isolation rule is: slice 1, slice 2 and slice 3, slice 4 isolation, or called non-coexistence.
  • the slice 1 and the slice 2 belong to the AMF (ie, the AMF in the AMF set 1) do not coexist with the slice 3 and the AMF to which the slice 4 belongs (ie, the AMF in the AMF set 2).
  • the coexistence rule may be that when the terminal registers with the network, the network returns the coexistence rule to the terminal, or the coexistence rule is configured on the terminal.
  • the terminal initiates a registration process, and the core network side returns allowed NSSAI and rejected NSSAI, wherein the rejected NSSAI includes identification information of the slice (eg, slice 3) (eg, S-NSSAI3) and rejection.
  • the cause value, the reason value of the rejection indicates that the slice is a network slice that is not supported by the PLMN.
  • the coexistence rule is sent to the terminal, where the coexistence rule is: S-NSSAI1, S-NSSAI2 and S-NSSAI3, and S-NSSAI4 do not coexist (ie, slice 1, slice 2, slice 3, slice 4) Do not coexist).
  • the AMF currently registered by the terminal ie, the AMF serving the terminal
  • the information stored on the terminal includes: allowed NSSAI, rejected NSSAI (including S-NSSAI3), and reject reason values, coexistence rules.
  • the information stored on the AMF serving the terminal includes: the requested NSSAI of the terminal, and the NSSAI of the subscription of the terminal.
  • the rejected NSSAI returned by the core network side may actually include the identification information of the slice 4 (for example, S-NSSAI4) and the reason value of the rejection, the reason value of the rejection.
  • the network slice is not supported by indicating that the slice is the current registration area of the terminal.
  • description will be made only when the slice 3 indicated by the S-NSSAI3 in the rejected NSSAI is updated to be available for the PLMN.
  • the slice 4 indicated by the S-NSSAI4 in the rejected NSSAI is updated to be available for the current registration area of the terminal, refer to the related description of the embodiment shown in FIG. 8 .
  • the terminals In the network, there are one or more terminals as described above. Therefore, if the slice update that is not supported by the PLMN is subsequently supported by the PLMN, the terminals that have requested the network slice but are rejected should be notified.
  • the slice information update method shown in FIG. 7 includes the following steps:
  • step 701 the NSSF determines that the PLMN supports the network slice.
  • step 701 The specific implementation of the step 701 is the same as the step 601, and the foregoing description may be referred to.
  • step 702 the NSSF sends a notification message to the PCF, and the PCF receives the notification message from the NSSF.
  • step 702 The specific implementation of the step 702 is the same as the step 602, and the foregoing description may be referred to.
  • step 703 the PCF sends an update message to the AMF, and the AMF receives the update message from the PCF.
  • the update message can be, for example, a policy update message.
  • the update message includes indication information and identification information of the terminal, the indication information is used to indicate that the PLMN supports the network slice. The network slice was not supported by PLMN.
  • step 703 is the same as the implementation of the foregoing step 603a, and the foregoing description may be referred to.
  • Step 704 the AMF sends a NAS message to the terminal, and the terminal receives the NAS message from the AMF.
  • the terminal is the terminal indicated by the identification information of the terminal carried in the update message of the above step 703.
  • the NAS message includes identification information of the network slice, which is a network slice that is not supported by the PLMN for updating to the PLMN.
  • the NAS message further includes indication information indicating that the network slice is available, or understanding that the indication information is used to indicate that the network slice has been updated to PLMN support.
  • step 703 needs to be performed three times:
  • AMF1 informs terminal 1: PLMN supports slice 3 identified by S-NSSAI3.
  • the AMF notifies the terminal that the first, second, and third executions are performed in the following manner: the AMF sends a NAS message to the terminal, and the NAS message includes indication information, and the indication information is used. Indicates that the PLMN supports slice 3 identified by S-NSSAI3.
  • the main difference between the step 704 and the step 603b is that the AMF that provides the service for the terminal does not need to send the updated allowed NSSAI to the terminal, but only needs to notify the terminal that the network slice has been updated to the PLMN support, because the terminal is served.
  • the AMF is isolated from the AMF to which the network slice belongs (i.e., the above AMF1 and AMF2 are isolated from the AMF to which the slice 3 belongs), and thus the AMF of the terminal service does not have the capability to support the network slice.
  • AMF1 needs to notify terminal 1 and terminal 2 that slice 3 identified by S-NSSAI3 has been Updated to PLMN support, since AMF1 does not support slice 3, AMF1 cannot send updated allowed NSSAI to terminal 1 and terminal 2: ⁇ S-NSSAI1, S-NSSAI2, S-NSSAI3 ⁇ , but only to terminal 1 and terminal 2 Send an indication message indicating that the slice 3 identified by the S-NSSAI3 has been updated to be supported by the PLMN, and thus the information stored by the terminal 1 and the terminal 2 is:
  • AMF2 also needs to send indication information to terminal 3, and thus the information stored by terminal 3 is:
  • the PCF when the NSSF determines that the network slice update that the PLMN has not supported is supported, the PCF is first determined, and then a notification message is sent to the determined PCF, indicating that the PLMN supports the network slice, and then the PCF receives the notification message.
  • Sending an update message to the AMF the update message includes the identification information and the indication information of the terminal, and then the AMF sends the indication information to the terminal indicated by the notification message, so that the network slice of the notification terminal has been updated to be supported by the PLMN, and the terminal is in the network slice.
  • the network slice can be used to help improve the service capability of the terminal.
  • another slice information update method provided by the present application is provided.
  • the method can be used to solve the problem that when the slice 4 that is not supported by the current registration area of the terminal shown in FIG. 3 or the slice 4 that is not supported by the current registration area of the terminal shown in FIG. Notify the terminal, and which terminals are notified.
  • the following shows the scenario shown in FIG. 3 as an example.
  • the terminal initiates a registration process, and the core network side returns allowed NSSAI and rejected NSSAI, wherein the rejected NSSAI includes identification information of a slice (eg, slice 4 in FIG. 3) (eg, S- NSSAI4) and the reason value of the rejection, the reason value of the rejection indicates that the slice is a network slice that is not supported by the current registration area of the terminal.
  • the coexistence rule is sent to the terminal, where the coexistence rule is: S-NSSAI1, S-NSSAI2, S-NSSAI3, and S-NSSAI4 do not coexist (ie, slice 1, slice 2, slice 3, and slice 4) Do not coexist).
  • the AMF currently registered by the terminal (that is, the AMF serving the terminal) is an AMF in the AMF set (for example, AMF set1 in FIG. 3).
  • the information stored on the terminal includes: allowed NSSAI, rejected NSSAI (including S-NSSAI4), and reject reason values, coexistence rules.
  • the information stored on the AMF serving the terminal includes: the requested NSSAI of the terminal, and the NSSAI of the subscription of the terminal.
  • the rejected NSSAI returned by the core network side may actually include the identification information of the slice 3 (for example, S-NSSAI3) and the reason value of the rejection, the rejection.
  • the reason value indicates that the slice is a network slice that is not supported by the PLMN.
  • description will be made only when the slice 4 indicated by the S-NSSAI4 in the rejected NSSAI is updated as available.
  • the specific implementation method of the slice 3 update indicated by the S-NSSAI3 in the rejected NSSAI to be supported by the PLMN reference may be made to the related description of the embodiment shown in FIG. 5 to FIG. 7 .
  • the slice information update method shown in FIG. 8 includes the following steps:
  • Step 801 The AMF sends the identifier information of the terminal and the identifier information of the network slice to the PCF, and the PCF receives the identifier information of the terminal from the AMF and the identifier information of the network slice.
  • the AMF when the AMF that provides the service for the terminal determines in the registration process of the terminal that the core network rejects the request of the network slice that the terminal does not support in the current registration area of the terminal, the AMF sends the PCF to the AMF.
  • the notification message is sent, and the notification message includes the identification information of the terminal and the identification information of the network slice.
  • the PCF stores the association relationship between the identification information of the terminal and the identification information of the network slice.
  • the current registration area of the terminal 1 includes AMF1, but does not include AMF2.
  • the AMF1 is the AMF in AMF set1
  • the slice supported by AMF1 includes Slice 1, Slice 2, Slice 3 (assuming Slice 3 has been updated to PLMN support).
  • the AMF2 is the AMF in the AMF set2, and the slice supported by the AMF2 includes the slice 4.
  • the terminal 1 Since the registration area in which the terminal 1 is currently located does not include the AMF 2, the terminal 1 cannot currently use the slice 4, or it is understood that the slice 4 is a slice that is not supported by the current registration area of the terminal 1.
  • the AMF1 can determine that the slice 4 is a slice that is not supported by the current registration area of the terminal 1, and the AMF1 sends the identification information of the terminal 1 and the S-NSSAI4 to the PCF, and then the PCF stores the identification information of the terminal 1.
  • Step 802 The PCF acquires a service area corresponding to the network slice from the NSSF.
  • the PCF may send a request message to the NSSF for requesting a service area corresponding to the network slice.
  • the service area may be a cell list composed of one or more cells.
  • the PCF sends a request message to the NSSF, the request message includes S-NSSAI4, and then the NSSF returns the service area corresponding to the S-NSSAI4 to the PCF.
  • step 803 the PCF learns that the terminal moves to the service area.
  • the manner in which the PCF learns that the terminal moves to the service area may be:
  • the PCF subscribes to the AMF: When the location of the terminal is updated, the AMF sends the updated location of the terminal to the PCF.
  • the PCF may send a subscription request message to the AMF, where the subscription request message carries an identifier of the terminal, and the subscription request message is used to subscribe the location of the terminal to the AMF.
  • the PCF invokes the subscription service by transmitting the identity of the terminal to the AMF: when the location of the terminal is updated, the AMF sends the updated location of the terminal to the PCF.
  • the registration request message in the registration update process may carry the current location information of the terminal, and the AMF may obtain the current location information of the terminal. Since the location information carried in the last registration update process of the terminal is stored on the AMF, if the location of the terminal indicated by the current location information of the terminal is different from the location of the terminal indicated by the previous location information, the AMF will be the terminal. The latest location is reported to the PCF.
  • the PCF determines whether the current location of the terminal is within the service area of the slice corresponding to the network slice according to the current location of the obtained terminal and the service area of the slice corresponding to the network slice. If the PCF is located in the service area, the PCF learns the terminal. Move to the service area.
  • the PCF determines that the current location of the terminal 1 is located in the service area corresponding to the S-NSSAI4, it is determined that the terminal 1 moves to the service area corresponding to the S-NSSAI4.
  • step 804 the PCF notifies the terminal that the network slice is available.
  • the PCF may send indication information to the terminal by using the AMF registered by the terminal, where the indication information is used to indicate that the network slice is available.
  • the PCF sends an update message to the AMF registered by the terminal, and the update message carries the identifier information and the indication information of the terminal.
  • the update message further carries the identifier information of the network slice, where the network slice is updated by the terminal unavailable.
  • the AMF then sends a NAS message to the terminal.
  • the NAS message includes the indication information.
  • the AMF If the PCF sends the update message to the AMF that is registered by the terminal, the AMF carries the identifier information of the network slice, and the AMF also includes the identifier information of the network slice in the NAS. In the message, it is sent to the terminal.
  • the specific implementation manner of the PCF sending the update message to the AMF is the same as the foregoing step 703. Referring to the foregoing description, the specific implementation manner of the AMF sending the NAS message to the terminal is the same as the foregoing step 704.
  • the PCF sends an update message to the AMF1 after determining that the terminal 1 moves to the service area corresponding to the S-NSSAI4.
  • the update message includes the identification information of the terminal 1 and the indication information, and the indication information is used to indicate S- Slice 4 identified by NSSAI4 is currently available.
  • the AMF1 then sends a NAS message to the terminal 1, which includes the S-NSSAI4.
  • the NAS message further includes the indication information.
  • the PCF may notify the terminal that the network slice is currently available, wherein the network slice is requested by the terminal but is rejected, and the registration area where the mobile phone is located is not supported.
  • Network slice When the network slice update that is not supported by the terminal registration area is updated, the corresponding terminal can be notified in time, and then the terminal can use the network slice when there is a demand for the service corresponding to the network slice, which helps to improve the terminal. Operational capacity.
  • FIG. 5 to FIG. 8 described above may be implemented as separate embodiments or in combination with each other.
  • the embodiments shown in Figures 5-7 can be implemented in combination with Embodiment 8, respectively.
  • the embodiments illustrated in Figures 5-6 can be implemented in combination with the embodiment illustrated in Figure 7, respectively.
  • the embodiments shown in FIGS. 5, 7, and 8 are implemented in combination.
  • the embodiments shown in FIGS. 6, 7, and 8 are implemented in combination.
  • the specific combination of the embodiments is not limited, and may be combined according to actual needs.
  • notification message, the update message, the NAS message, the subscription request message, the configuration update message, and the like in the foregoing embodiment are only one name, and the name does not limit the message itself.
  • notification message, the update message, the NAS message, the subscription request message, and the configuration update message may also be other names, which are not specifically limited in the embodiment of the present application.
  • the present invention discloses a method for updating slice information, including:
  • the communication network element notifies the terminal that the PLMN supports the network slice, and the terminal is a terminal that has requested the network slice to fail and has signed the network slice.
  • the communication network element may be a mobility management network element or a policy control network element.
  • the communication network element determines the terminal according to a terminal context.
  • the method further includes: the mobility management network element adding the identification information of the network slice to the allowed connection of the terminal Incoming network slice set;
  • the communication network element notifying the terminal that the PLMN supports the network slice includes: the mobility management network element sending the updated network slice set that is allowed to access to the terminal.
  • the communication network element notifying the terminal that the PLMN supports the network slice further includes: the mobility management network element sending indication information to the terminal, where the indication information is used to indicate the PLMN support The network slice.
  • the method further includes: the policy control network element determining the mobility management network element registered by the terminal;
  • the communication network element notifying the terminal that the PLMN supports the network slice includes: the policy control network element sending, by using the mobility management network element, indication information to the terminal, where the indication information is used to indicate the The PLMN supports the network slice.
  • the operation of the mobility management network element may refer to the operation of the AMF in FIG. 5 and the related text description, and details are not described herein again.
  • the operation of the policy control network element may refer to the operation of the PCF in FIG. 6 and the related text description, and details are not described herein again.
  • the invention also provides a method for updating slice information, comprising:
  • the mobility management network element receives an update message from the policy control network element, where the update message includes indication information and identification information of the terminal, where the indication information is used to indicate that the public land mobile network PLMN supports the network slice;
  • the mobility management network element notifies the terminal that the PLMN supports the network slice, and the terminal is a terminal that has requested the network slice to fail and subscribes to the network slice.
  • the method further includes: adding, by the mobility management network element, the identifier information of the network slice to a network slice set of the terminal that is allowed to access;
  • the mobility management network element notifying the terminal that the PLMN supports the network slice includes: the mobility management network element sending the updated network slice set that is allowed to access to the terminal.
  • the mobility management network element notifying the terminal that the PLMN supports the network slice further includes: the mobility management network element sending indication information to the terminal, where the indication information is used by The PLMN is instructed to support the network slice.
  • the mobility management network element notifying the terminal that the PLMN supports the network slice includes: the mobility management network element sending a NAS message to the terminal, where the NAS message includes Indicate the indication information.
  • the operation of the mobility management network element may refer to the operation of the AMF in FIG. 7 and the related text description, and details are not described herein again.
  • the invention also provides a method for updating slice information, comprising:
  • the policy control network element receives the identification information of the terminal from the mobility management network element and the identifier information of the network slice, where the network slice is a network slice that is not supported by the current registration area of the terminal;
  • the policy control network element acquires a service area corresponding to the network slice from a network slice selection network element
  • the policy control network element notifying the terminal that the network slice is currently available includes: the policy control network element sending the indication information to the terminal by using the mobility management network element, The indication information is used to indicate that the network slice is available.
  • the operation of the policy control network element may refer to the operation of the PCF in FIG. 8 and the related text description, and details are not described herein again.
  • the invention also provides a method for updating slice information, comprising:
  • the network slice selection network element determines that the public land mobile network PLMN supports the network slice
  • the network slice selection network element sends a notification message to the communication network element, where the notification message includes identification information of the network slice, and the notification message is used to indicate that the PLMN supports the network slice.
  • the communication network element is a policy control network element or a mobility management network element.
  • the method further includes: the network slice selection network element receiving a subscription from the communication network element: when the PLMN supports the network slice, the network slice selects a network element notification The communication network element.
  • the method further includes: determining, by the network slice selection network element, a mobility management network element that supports the network slice according to a slice type supported by a mobility management network element in the PLMN The communication network element.
  • the operation of the network slice selection network element may refer to the operation of the NSSF in FIG. 5 to FIG. 7 and the related text description, and details are not described herein again.
  • the network side includes two AMF sets, AMF set 1 and AMF set 2.
  • the network slice supported by any AMF in the AMF set 1 is: ⁇ Slice 1, Slice 2, Slice 3 ⁇ , the service area of slice 1 is service area 1, and the service area of slice 2 is service area 2.
  • the service area of slice 3 is service area 3.
  • the network slice supported by any AMF in AMF set 2 is: ⁇ Slice 4, Slice 5 ⁇ , the service area of slice 4 is service area 4, and the service area of slice 4 is service area 5.
  • the slice 1, slice 2, slice 3, slice 4, and slice 5 in the above example may be identified by S-NSSAI1, S-NSSAI2, S-NSSAI3, S-NSSAI4, and S-NSSAI5, respectively. That is, S-NSSAI1 is the identification information of slice 1, S-NSSAI2 is the identification information of slice 2, S-NSSAI3 is the identification information of slice 3, S-NSSAI4 is the identification information of slice 4, and S-NSSAI5 is the identification information of slice 5. .
  • Each network slice corresponds to one or more SMFs and one or more UPFs.
  • slice 1 corresponds to SMF1 and UPF1
  • slice 2 corresponds to SMF2 and UPF2
  • slice 3 corresponds to SMF3 and UPF3
  • slice 4 corresponds to SMF4 and UPF4
  • slice 5 corresponds to SMF5 and UPF5.
  • the slice supported by any AMF in the AMF Set 1 is isolated from the slice supported by any AMF in the AMF Set2 (or a mutually exclusive relationship or a non-coexistence relationship), and the isolation relationship can be understood as not being simultaneously connected. Enter or access two different slices at the same time. Therefore, the terminal can only access the slice in slice 1, slice 2, slice 3, or can only access the slice in slice 4 and slice 5, but cannot access both the slice in slice 1, slice 2, slice 3 and access simultaneously. Slice 4, slice in slice 5.
  • a sliced service area refers to a range in which the slice can provide a service, that is, the slice can serve a terminal within the service range of the slice, or can be understood as a terminal that is within the service area of the slice can provide the use of the slice.
  • the service the terminal outside the service area of the slice, cannot use the service provided by the slice.
  • the service area may include one or more Tracking Areas (TAs), and one TA may use a Tracking Area Identity (TAI) unique identifier. Therefore, it can also be understood that one slice corresponds to one service area, or it is understood that one slice corresponds to one or more TAs.
  • TAs Tracking Areas
  • TAI Tracking Area Identity
  • the service areas of the slice 1 to the slice 5 respectively include 10 TAs, specifically:
  • the service area of slice 1 includes: TA1, TA2, ..., TA11;
  • the service area of slice 2 includes: TA2, TA3, ..., TA12;
  • the service area of slice 3 includes: TA3, TA4, ..., TA13;
  • the service area of slice 4 includes: TA4, TA5, ..., TA14;
  • the service area of slice 5 includes: TA5, TA6, ..., TA15.
  • the service area of any two slices includes overlapping TAs.
  • the service area of the slice 1 and the service area of the slice 2 include overlapping TAs of TA2, TA3, ..., TA11.
  • the service status in any TA within the service area of any slice can be divided into “available state” and "restricted state”. Wherein, if the slice can provide services for the terminal in a certain TA, the service status of the slice in the TA is “available state”. If the slice cannot serve the terminal in a certain TA, the service status of the slice in the TA is “restricted state”.
  • the “restricted state” may also be referred to as a "temporary unavailable state.”
  • the slice can be converted between two service states in a certain TA, for example, from “available state” to “restricted state”, or from “restricted state” to “available state”.
  • the TA may also be referred to as a TA that makes the slice in an “available state”, or a TA that the TA is available for the slice. If the service state of the slice in a TA is "restricted state”, the TA may also be referred to as a TA that causes the slice to be in a "restricted state”, or a TA that the TA is not available for the slice.
  • the NSSF may determine the service status of the slice currently in one or some TAs according to the load of the slice. For example, for a slice, if the number of users accessing the slice is large, so that the load of the slice exceeds a preset threshold, the NSSF may use the service state of the slice in one or some TAs from the "available state". Switch to "Limited Status". For another example, for a slice, if the number of users accessing the slice is small, so that the load of the slice is lower than a preset threshold, the NSSF may change the service status of the slice in one or some TAs from the limit. The status "turns to "available state".
  • a terminal registered to the network may use a certain slice, which means that any TA included in the registration area of the terminal satisfies the slice being in an "available state", in other words, the TA included in the registration area of the terminal
  • the terminal is always located in the registration area of the terminal, that is, the terminal has not moved out of the registration area of the terminal.
  • the update method of the slice information after the terminal removes the registration area reference may be made to the related description of the related art.
  • FIG. 10 As shown in FIG. 10, another method for updating slice information provided by the present application is provided.
  • the method includes the following steps:
  • step 1001 the AMF sends a request to the NSSF. Accordingly, the NSSF can receive the request.
  • the request may be, for example, an Nnssf_NSSAIAvailability_Update request or may be a request message.
  • the request is used to report the identification information of the slice supported by the AMF to the NSSF, and the service area corresponding to each slice (a service area may include one or more TAs).
  • the information reported to the NSSF for each AMF in the AMF set 1 shown in FIG. 9 includes:
  • the information reported to the NSSF for each AMF in the AMF set 2 shown in FIG. 9 includes:
  • step 1002 the terminal initiates a registration process, and the core network returns allowed NSSAI and rejected NSSAI.
  • the subscription NSSAI of the terminal is ⁇ S-NSSAI1, S-NSSAI2, S-NSSAI3, S-NSSAI4, S-NSSAI5 ⁇ , and the terminal is currently located at TA5.
  • the terminal does not know that the slice supported by AMF set 1 is isolated from the slice supported by AMF set 2.
  • the terminal initiates a registration request, and the requested NSSAI may include ⁇ S-NSSAI1, S-NSSAI2, S-NSSAI3, S-NSSAI4, and S-NSSAI5 ⁇ .
  • the RAN selects AMF according to the requested NSSAI, the S-NSSAI-1, S is found.
  • -NSSAI-2, S-NSSAI-3 is served by AMF set 1, but S-NSSAI-4, S-NSSAI-5 is served by AMF set 2, for example, RAN prefers AMF in AMF set 1 as service AMF (serving) AMF).
  • the network side determines the allowed NSSAI and the registration area RA of the terminal according to the requested NSSAI of the terminal.
  • the information sent by the service AMF to the terminal is as follows:
  • the allowed NSSAI includes the identification information of the network slice allowed to be accessed by the core network side, that is, the core network side allows the terminal to access the slice 1 and the slice 2.
  • the rejected NSSAI includes the identification information of the network slice that the core network side refuses to access, that is, the core network side rejects the terminal access slice 4 and slice 5.
  • the reason for rejecting the terminal access to slice 4 and slice 5 is 2.
  • the reason value 2 corresponding to the slice 4 indicates that the slice 4 is isolated from the slice in the allowed NSSAI
  • the cause value 2 corresponding to the slice 5 indicates that the slice 5 is isolated from the slice in the allowed NSSAI.
  • the service AMF can also store the following information in the context of the terminal:
  • RA ⁇ TA4, TA5, TA6 ⁇ ;
  • NSSAI Allowed NSSAI: ⁇ S-NSSAI1, S-NSSAI2, S-NSSAI 3 ⁇ .
  • the AMF also stores the service status of each TA in each of the allowed NSSAIs in the service area of the network slice.
  • the AMF records the service status of the slice 1 in each TA in TA1-TA13.
  • the recorded information is: slice 1 is in TA1-TA7. Available state", in TA8-TA13 in "restricted state” (ie temporarily unavailable state).
  • a similar method is also used for slice 2 and slice 3 to record the service state of the slice at each TA, which is not illustrated.
  • the service AMF may also send an isolation rule (or a coexistence rule) to the terminal: S-NSSAI1, S-NSSAI2, S-NSSAI3 and S-NSSAI4, and S-NSSAI5 are isolated from each other.
  • an isolation rule or a coexistence rule
  • the terminal knows that the slice supported by AMF set 1 is isolated from the slice supported by AMF set 2, and the service state of slice 3 in AMF set 1 is "restricted state".
  • the terminal is pre-configured with an isolation rule, and the isolation rule indicates that: NSSAI1, S-NSSAI2, and S-NSSAI3 are isolated from each other by S-NSSAI4 and S-NSSAI5. Therefore, the terminal does not request NSSAI1, S-NSSAI2, S-NSSAI3, S-NSSAI4, and S-NSSAI5 at the same time.
  • the terminal initiates a registration request, such as carrying a requested NSSAI including ⁇ S-NSSAI1, S-NSSAI2, S-NSSAI3 ⁇ , and when the RAN selects AMF according to the requested NSSAI, it finds S-NSSAI-1, S-NSSAI-2, S-NSSAI. -3 is served by AMF set 1, so the RAN can select an AMF from AMF set 1 as the serving AMF (serving AMF).
  • the network side determines the allowed NSSAI and the register area (RA) of the terminal according to the requested NSSAI of the terminal.
  • the information sent by the service AMF to the terminal is as follows:
  • RA ⁇ TA4, TA5, TA6 ⁇ , here it is assumed that the registration area of the terminal is composed of 3 TAs.
  • the allowed NSSAI includes the identification information of the network slice allowed to be accessed by the core network side, that is, the core network side allows the terminal to access the slice 1 and the slice 2.
  • the service AMF can also store the following information in the context of the terminal:
  • RA ⁇ TA4, TA5, TA6 ⁇ ;
  • NSSAI Allowed NSSAI: ⁇ S-NSSAI1, S-NSSAI2, S-NSSAI 3 ⁇ .
  • step 1003 the NSSF determines that the service status of one or more slices in one or more TAs is changed from "available state” to "restricted state”.
  • the terminal RA ⁇ TA4, TA5, TA6 ⁇ .
  • step 1003 slice 3 is available at all TAs, ie slice 3 is available at TA3 to TA13.
  • the NSSF determines that the load of the slice 3 is higher than a preset threshold, and the NSSF determines that the service state of the slice 3 in all TAs is changed from "available state" to "restricted state", and therefore, after the change, the slice 3 is All TAs are not available, ie slice 3 is not available from TA3 to TA13.
  • step 1003 slice 3 is available at all TAs, ie slice 3 is available at TA3 to TA13.
  • the NSSF determines that the load of the slice 3 is higher than a preset threshold, and the NSSF determines that the service state of the slice 3 in the partial TA is changed from the "available state" to the "restricted state", for example, determining that the slice 3 is at TA5, The service status of TA6 is changed from "available state" to "restricted state", so after the change, slice 3 is unavailable at TA5, TA6, and available at TA3, TA4, TA7 to TA13.
  • slice 3 is available at part TA, such as available at TA3 through TA10, and unavailable at TA11 through TA13.
  • the NSSF determines that the load of the slice 3 is higher than a preset threshold, and the NSSF determines that the service state of the slice 3 in all available TAs (ie, TA3 to TA10) is changed from "available state" to "restricted state", Therefore, after the change, slice 3 is not available at all TAs, that is, slice 3 is not available at TA3 to TA13.
  • slice 3 is available at part TA, such as available at TA3 through TA10, and unavailable at TA11 through TA13.
  • the NSSF determines that the load of the slice 3 is higher than a preset threshold, and the NSSF determines that the service state of the slice 3 in the partially available TA is changed from the "available state" to the "restricted state", for example, determining that the slice 3 is The service status of TA6 to TA10 is changed from "available state" to "restricted state", so after the change, slice 3 is unavailable in TA6 to TA13 and available in TA3 to TA5.
  • slice 3 is available at part TA, such as available at TA3 through TA10, and unavailable at TA11 through TA13.
  • the NSSF determines that the load of the slice 3 is higher than a preset threshold, and the NSSF determines that the service state of the slice 3 in the partially available TA is changed from the "available state" to the "restricted state", for example, determining that the slice 3 is The service status of TA7 to TA10 is changed from "available state" to "restricted state", so after the change, slice 3 is unavailable in TA7 to TA13 and available in TA3 to TA6.
  • step 1004 the NSSF sends a notification to the AMF. Accordingly, the AMF can receive the notification.
  • the notification may be, for example, Nnssf_NSSAIAvailability_Notify or may be a notification message.
  • the notification includes the identifier information of the slice and the identifier information of the at least one TA.
  • the identifier information of the at least one TA may be represented by a TA list in the specific implementation, that is, the identifier may include the identifier information of the slice and a TA list.
  • the TA list includes identification information of at least one TA.
  • the present application is described by taking the above notification including the identification information of the slice and a TA list as an example.
  • the slice here refers to a slice in which the service state of some or all of the TAs is changed from "available state” to "restricted state” determined in the above step 1003, such as slice 3 in each example of the above step 1003.
  • the TA list here includes one or more TAs, and the state of the above-described slice in any TA in the TA list is changed from "available state" to "restricted state”.
  • the slice here refers to slice 3, and the TA list includes TA3 to TA13.
  • the slice here refers to slice 3, and the TA list includes TA5, TA6.
  • the slice here refers to slice 3
  • the TA list includes TA3 to TA10.
  • the slice here refers to slice 3
  • the TA list includes TA6 to TA10.
  • the slice here refers to slice 3, and the TA list includes TA7 to TA10.
  • the service state of each TA in the service area of the network slice of each network slice in the allowed NSSAI is not stored in the AMF.
  • the service state of the slice in each TA of the service area of the slice may be carried in the notification, that is, the notification at the step 1004 for any of the four examples in the above step 1003.
  • the message may carry the identification information of the slice and the current service status of the slice within each TA of the slice.
  • Step 1005 The AMF determines, according to the allowed NSSAI in the context of the terminal, a slice that is unavailable to the terminal.
  • the information stored by the AMF in the context of a terminal includes:
  • RA ⁇ TA4, TA5, TA6 ⁇ ;
  • NSSAI Allowed NSSAI: ⁇ S-NSSAI1, S-NSSAI2, S-NSSAI3 ⁇ .
  • the notification in step 1004 carries the identifiers S-NSSAI3 of the slice 3 and the identifiers of TA3 to TA13. Since the service state of slice 3 in TA3 to TA13 is changed to "restricted state", and the RA of the terminal includes TA4, TA5 and TA6, the terminal cannot use the slice 3 at TA4 to TA6, and the terminal will not be able to use the slice 3, that is, The slice 3 in the allowed NSSAI of the terminal is currently not available, and thus the slice in which the determined terminal is unavailable includes the slice 3.
  • the notification in step 1004 carries the identifier of the slice 3, S-NSSAI3, and the identifiers of TA5 and TA6. Since the service status of slice 3 in TA5 and TA6 is changed to "restricted state", and the RA of the terminal includes TA4, TA5 and TA6, the terminal cannot use the slice 3 at TA5, TA6, and the terminal will not be able to use the slice 3, that is, The slice 3 in the allowed NSSAI of the terminal is currently not available, and thus the slice in which the determined terminal is unavailable includes the slice 3.
  • the notification in step 1004 carries the identifiers S-NSSAI3 of the slice 3 and the identifiers of TA3 to TA10. Since the service status of slice 3 in TA3 to TA10 is changed to "restricted state", and the RA of the terminal includes TA4, TA5 and TA6, the terminal cannot use the slice 3 at TA4 to TA6, and the terminal will not be able to use the slice 3, that is, The slice 3 in the allowed NSSAI of the terminal is currently not available, and thus the slice in which the determined terminal is unavailable includes the slice 3.
  • the notification in step 1004 carries the identifiers S-NSSAI3 of the slice 3 and the identifiers of TA6 to TA10. Since the service status of slice 3 in TA6 to TA10 is changed to "restricted state", and the RA of the terminal includes TA4, TA5 and TA6, the terminal cannot use the slice 3 at TA6, and the terminal will not be able to use the slice 3, that is, the determined Slice 3 in the allowed NSSAI of the terminal is currently unavailable, and thus the determined slice in which the terminal is unavailable includes slice 3.
  • the notification in step 1004 carries the identifiers S-NSSAI3 of the slice 3 and the identifiers of TA7 to TA10. Since the service state of slice 3 at TA7 to TA10 is changed to "restricted state", and the service state of slice 3 at TA3 to TA6 is "available state", and the RA of the terminal includes TA4, TA5 and TA6, the terminal can still use the terminal Slice 3, thus determining that slice 3 in the allowed NSSAI is still currently available. Based on this example 5, if slice 1 and slice 2 in the allowed NSSAI are still available, the AMF will determine the slice in the allowed NSSAI, and the terminal is available or accessible.
  • the terminal can use the slice or can be called the terminal can access the slice.
  • the terminal cannot use a certain slice in any TA of the registration area, it can be said that the slice cannot be used by the terminal.
  • step 1006 the AMF determines a new allowed NSSAI and a rejected NSSAI for the terminal, and stores the rejected NSSAI.
  • the AMF determines that the terminal is currently unable to use slice 3, and further determines that the terminal can still use slice 1 and slice 2, the new allowed NSSAI determined by the AMF for the terminal in step 1006 is ⁇ S-NSSAI1, S- NSSAI2 ⁇ , the rejected NSSAI determined for the terminal includes ⁇ S-NSSAI3 ⁇ . And, AMF also stores the rejected NSSAI.
  • step 1007A if the terminal is in the connected state, the AMF sends the new allowed NSSAI and the rejected NSSAI to the terminal through the configuration update process.
  • step 1007B if the idle state is in the idle state, the AMF may wait for the terminal to be in the connected state again (for example, waiting for the terminal to initiate a periodic registration update procedure), and the AMF sends the new allowed NSSAI and the rejected NSSAI to the terminal.
  • step 1008 the NSSF determines that the service status of one or more slices in one or more TAs is changed from "restricted state” to "available state.”
  • This step 1008 is the reverse of the above step 1003. Still taking the example in the above step 1003 as an example.
  • slice 3 is not available at all TAs, i.e. slice 3 is not available at TA3 to TA13.
  • the NSSF determines that the load of slice 3 is lower than a preset threshold, and the NSSF determines that the service state of the slice 3 in all TAs is changed from "restricted state" to "available state", and therefore, after the change, slice 3 is All TAs are available, ie slice 3 is available from TA3 to TA13.
  • step 1003 slice 3 is not available at TA5, TA6, and available at TA3, TA4, TA7 through TA13.
  • step 1008 the NSSF determines that the load of the slice 3 is lower than a preset threshold, and the NSSF determines that the service state of the slice 3 in the partially unavailable TA is changed from the "restricted state" to the "available state", such as determining the slice 3
  • the service status in TA6 is changed from "Restricted Status" to "Available Status", so after the change, slice 3 is available at TA3, TA4, TA6 to TA13, and unavailable at TA5.
  • step 1008 the NSSF determines that the load of the slice 3 is lower than a preset threshold, and the NSSF determines that the service state of the slice 3 in the partially unavailable TA is changed from the "restricted state" to the "available state", such as determining the slice 3
  • the service status in TA3 to TA8 is changed from "Restricted Status" to "Available Status", so after the change, slice 3 is available from TA3 to TA8, and is still unavailable at TA9 to TA13.
  • step 1008 the NSSF determines that the load of the slice 3 is lower than a preset threshold, and the NSSF determines that the service state of the slice 3 in all unavailable TAs is changed from "restricted state” to "available state", that is, the slice 3 is The service status in TA6 to TA13 is changed from "restricted state” to "available state”, so after the change, slice 3 is available at all TAs, that is, slice 3 is available from TA3 to TA13.
  • step 1009 the NSSF sends a notification to the AMF. Accordingly, the AMF can receive the notification.
  • the notification may be, for example, Nnssf_NSSAIAvailability_Notify or may be a notification message.
  • the notification includes the slice identification information and the identifier information of the at least one TA.
  • the identifier information of the at least one TA may be represented by a TA list in the specific implementation, that is, the notification may include the identifier information of the slice and a TA list.
  • the list includes identification information of at least one TA.
  • the present application is described by taking the above notification including the identification information of the slice and a TA list as an example.
  • the slice here refers to a slice in which the service state of some or all of the TAs is changed from “restricted state” to "available state” determined in the above step 1008, such as slice 3 in each example of the above step 1008.
  • the TA list here includes one or more TAs, and the state of the above-described slice in any TA in the TA list is changed from "restricted state" to "available state”.
  • the slice in the notification of step 1009 refers to slice 3, and the TA list includes TA3 to TA13.
  • the slice in the notification of step 1009 refers to slice 3 and the TA list includes TA6.
  • the slice in the notification of step 1009 refers to slice 3 and the TA list includes TA3 to TA8.
  • the slice in the notification of step 1009 refers to slice 3, and the TA list includes TA6 to TA13.
  • step 1010 the AMF determines a new allowed NSSAI for the terminal according to the rejected NSSAI stored in the context of the terminal.
  • the rejected NSSAI stored by the AMF for the terminal includes ⁇ S-NSSAI3 ⁇ , and in the notification of the above step 1009, the slice 3 and the TA list corresponding to the slice 3 are carried, then the AMF is in step 1010. It is necessary to judge whether the slice 3 can be currently used by the terminal, which will be described below in conjunction with the four examples of the above 1008.
  • the AMF determines that the slice 3 is currently in the "available state" at TA3 to TA13 according to the context of the stored terminal and the notification received through step 1009, and the registration area of the terminal includes TA4 to TA6, therefore, the terminal can use the slice 3.
  • the determined new allowed NSSAI includes ⁇ NSSAI1, NSSAI2, NSSAI3 ⁇ .
  • the AMF determines that the slice 3 is currently in the "available state" at TA3, TA4, TA6 to TA13 according to the context of the stored terminal and the notification received through step 1009, at TA5
  • the "restricted state", and the registration area of the terminal includes TA4 to TA6, and therefore, the slice 3 cannot be used by the terminal.
  • the AMF determines that the slice 3 is currently in the "available state” at TA3 to TA8 according to the context of the stored terminal and the notification received through step 1009, and is in the "restricted state" at TA9 to TA13. Status", and the registration area of the terminal includes TA4 to TA6, so the terminal can use the slice 3.
  • the determined new allowed NSSAI includes ⁇ S-NSSAI1, S-NSSAI2, S-NSSAI3 ⁇ .
  • the AMF determines that the slice 3 is currently in the "available state" at TA3 to TA13 according to the context of the stored terminal and the notification received through step 1009, and the registration area of the terminal includes the TA4. To TA6, therefore, the terminal can use the slice 3.
  • the determined new allowed NSSAI includes ⁇ S-NSSAI1, S-NSSAI2, S-NSSAI3 ⁇ .
  • step 1011 the AMF sends a new allowed NSSAI to the terminal.
  • This step 1011 may send a new allowed NSSAI to the terminal in the manner described in step 1007A or step 1007B above.
  • the AMF may also delete the slice identifier in the rejected NSSAI.
  • the S-NSSAI3 is included after the new allowed NSSAI is sent to the terminal, and then the AMF can delete the identifier S-NSSAI3 of the slice 3 in the rejected NSSAI.
  • the AMF stores the rejected NSSAI in the context of the terminal.
  • the AMF receives the notification from the NSSF and learns that the slice in the rejected NSSAI becomes available to the terminal again, the AMF includes the identifier of the slice in the new allowed NSSAI. Send to the terminal.
  • the re-enabling of the slice is implemented to improve resource utilization.
  • FIG. 11 another method for updating slice information provided by the present application is provided.
  • the embodiment shown in FIG. 11 is explained using the example in the embodiment shown in FIG. 10 described above.
  • the method includes the following steps:
  • Step 1101 - Step 1109 similar to steps 1001 - 1009 of the embodiment shown in FIG. 10, reference may be made to the foregoing description.
  • the AMF may not need to store the determined rejected NSSAI.
  • step 1110 the terminal sends a registration request message to the AMF. Accordingly, the AMF can receive the registration request message.
  • the registration request message includes a requested NSSAI.
  • the requested NSSAI includes the S-NSSAI in the rejected NSSAI obtained by the terminal in the above step 1107A or step 1107B.
  • the example employed in the step 1101 - the step 1109 of the embodiment shown in FIG. 11 is the same as the example adopted in the step 1001 - step 1009 of the embodiment shown in FIG. 10 described above, that is, in the step 1101 - the step 1109 It is determined that the service state of the slice 3 in part or all of the TAs of the slice 3 is changed from "restricted state" to "available state", and the AMF notifies the terminal through the rejected NSSAI in step 1007A or step 1007B, denying the terminal access (or using ) The slice 3.
  • the terminal Before the terminal initiates the step 1111, it is known that the slice 3 is a slice that was previously rejected by the network.
  • the terminal will carry the identification information of the slice that has been denied access in the requested NSSAI when the request is re-initiated.
  • the identification information carrying the slice 3 described above, that is, S-NSSAI 3 is carried.
  • the terminal does not move out of the registration area.
  • the terminal initiates a periodic registration request message in the registration area, carrying the requested NSSAI and the registration type.
  • the requested NSSAI includes the S-NSSAI in the rejected NSSAI obtained by the terminal in step 1107A or step 1107B, and the registration type indicates that the registration request is a Periodic Registration Update.
  • step 1111 the AMF determines a new allowed NSSAI for the terminal according to the requested NSSAI.
  • the requested NSSAI of the above-mentioned step 1110 carries the identifier of the slice 3, that is, the S-NSSAI3, in the step 1111, if the AMF determines that the terminal can currently use the slice 3, the AMF carries the S-NSSAI3 in the new allowed NSSAI.
  • the new allowed NSSAI can also carry the identifiers of other available slices.
  • step 1112 the AMF sends a registration accept message to the terminal, carrying the new allowed NSSAI.
  • the main difference between the embodiment shown in FIG. 11 and the embodiment shown in FIG. 10 is that the embodiment shown in FIG. 11 is that the terminal carries the identifier of the slice that was previously rejected in the registration request message, and then the AMF determines whether the terminal is currently The rejected slice can be used, and if it is available, the previously rejected slice identifier is included in the new allowed NSSAI and sent to the terminal.
  • the terminal carries the identifier of the temporarily rejected slice in the registration request message, so that the AMF can update the new allowed NSSAI of the terminal in time when the slice becomes available from the temporary unavailable.
  • the present invention discloses a method for updating slice information, including:
  • the mobility management network element receives a notification message from the network slice selection network element, where the notification message includes identification information of the network slice and identification information of the at least one tracking area, the network slice is available in the at least one tracking area, and the network slice is in the The at least one tracking area was previously unavailable;
  • the mobility management network element determines the updated network slice set that is allowed to access, and the updated network slice set that is allowed to access includes the identifier information of the network slice, where the terminal is located in the registration area of the terminal, and the terminal can access The network slice;
  • the mobility management network element sends the updated network slice set of the allowed access to the terminal.
  • the terminal can access the network slice, which means that the network slice is available in any tracking area in the registration area of the terminal.
  • the mobility management network element determines that the network slice is available in the registration area of the terminal, and determines that the terminal can access the network slice.
  • the mobility management network element before receiving the notification message from the network slice selection network element, the mobility management network element further stores a network slice set of the terminal that is denied access, and the network slice set of the denied access includes the foregoing network.
  • the identification information of the slice is not limited to the network slice set of the terminal that is denied access.
  • the terminal before the mobility management network element sends the updated network slice set that is allowed to access, the terminal further receives a registration request message from the terminal, where the registration request message includes the identifier information of the network slice.
  • the mobility management network element sends the updated network slice set that is allowed to access to the terminal, where the mobility management network element sends a registration accept message to the terminal, where the registration accept message includes the updated A set of network slices that are allowed to access.
  • the invention also discloses a method for updating slice information, comprising:
  • Receiving, by the terminal, an updated set of network slices allowed to access from the mobility management network element, the updated set of network slices allowed to access includes identification information of the network slice, the network slice being available in a registration area of the terminal The network slice was not available in the registration area of the terminal.
  • the terminal receives the updated set of network slices allowed to access from the mobility management network element, and specifically includes: receiving, by the terminal, a registration accept message from the mobility management network element, where the registration accept message includes The above updated set of network slices that allow access.
  • the operation of the terminal may refer to the operation of the terminal in FIG. 11 and the related text description, and details are not described herein again.
  • each of the foregoing network elements includes a hardware structure and/or a software module corresponding to each function.
  • the present invention can be implemented in a combination of hardware or hardware and computer software in combination with the elements and algorithm steps of the various examples described in the embodiments disclosed herein. Whether a function is implemented in hardware or computer software to drive hardware depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods for implementing the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present invention.
  • a schematic diagram of a device provided by the present application may be a mobility management network element, a policy control network element, a network slice selection network element, a terminal, or a chip, and the foregoing may be performed.
  • the apparatus 1200 includes at least one processor 1201, a communication line 1202, a memory 1203, and at least one communication interface 1204.
  • the processor 1201 may be a general central processing unit (CPU), a microprocessor, an application-specific integrated circuit (server IC), or one or more programs for controlling the execution of the program of the present application. Integrated circuit.
  • Communication line 1202 can include a path for communicating information between the components described above.
  • Communication interface 1204 using any type of transceiver, for communicating with other devices or communication networks, such as Ethernet, radio access network (RAN), wireless local area networks (WLAN), etc. .
  • RAN radio access network
  • WLAN wireless local area networks
  • the memory 1203 may be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (RAM) or other type that can store information and instructions.
  • the dynamic storage device may also be an electrically EEPROM programmable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disk storage.
  • EEPROM electrically EEPROM programmable programmable read-only memory
  • CD-ROM compact disc read-only memory
  • Optical disc storage including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.
  • magnetic disk storage media or other magnetic storage devices or capable of carrying or storing desired program code in the form of instructions or data structures and capable of Any other medium accessed by a computer, but is not limited thereto.
  • the memory may be stand-alone and connected to the processor via communication line 1202. The memory can also be integrated with the processor.
  • the memory 1203 is configured to store computer execution instructions for executing the solution of the present application, and is controlled by the processor 1201 for execution.
  • the processor 1201 is configured to execute computer execution instructions stored in the memory 1203, thereby implementing the slice information update method provided by the following embodiments of the present application.
  • the computer-executed instructions in the embodiment of the present application may also be referred to as an application code, which is not specifically limited in this embodiment of the present application.
  • the processor 1201 may include one or more CPUs, such as CPU0 and CPU1 in FIG.
  • apparatus 1200 can include multiple processors, such as processor 1201 and processor 1208 in FIG. Each of these processors can be a single-CPU processor or a multi-core processor.
  • a processor herein may refer to one or more devices, circuits, and/or processing cores for processing data, such as computer program instructions.
  • the device 1200 when the device 1200 is a terminal, the device 1200 may further include an output device 1205 and an input device 1206.
  • Output device 1205 is in communication with processor 1201 and can display information in a variety of ways.
  • the output device 705 can be a liquid crystal display (LCD), a light emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector. Wait.
  • Input device 1206 is in communication with processor 1201 and can receive user input in a variety of ways.
  • input device 1206 can be a mouse, keyboard, touch screen device, or sensing device, and the like.
  • the chip When the device shown in FIG. 12 is a chip, for example, a chip of a mobility management network element, a chip of a policy control network element, a chip of a network slice selection network element, or a chip of a terminal, the chip includes a processor 1201 (also A processor 1208), a communication line 1202, a memory 1203, and a communication interface 1204 can be included.
  • communication interface 1204 can be an input interface, a pin or a circuit, or the like.
  • the memory 1203 may be a register, a cache, or the like.
  • Processor 1201 and processor 1208 may be a general purpose CPU, microprocessor, ASIC, or one or more integrated circuits for controlling program execution of the slice information update method of any of the above embodiments.
  • the present application may divide a functional module into a device according to the above method example.
  • each functional module may be divided according to each function, or two or more functions may be integrated into one processing module.
  • the above integrated modules can be implemented in the form of hardware or in the form of software functional modules.
  • FIG. 13 shows a schematic diagram of a device, which may be a communication network element or a communication network element chip in the above embodiment, and a communication network element. Control network elements for mobility management network elements or policies.
  • the apparatus 1300 includes a receiving unit 1301 and a transmitting unit 1302.
  • a processing unit 1303 is further included.
  • the receiving unit 1301 is configured to receive a notification message from the network slice selection network element, where the notification message includes identifier information of the network slice, where the notification message is used to indicate that the public land mobile network PLMN supports the network slice, where the PLMN does not support the network slice.
  • the sending unit 1302 is configured to notify the terminal PLMN to support network slicing, where the terminal is a terminal that has requested network slice failure and has signed a network slice.
  • the processing unit 1303 is configured to determine the terminal according to the terminal context.
  • the device is a chip of a mobility management network element or a mobility management network element, and then:
  • the processing unit 1303 is further configured to add the identifier information of the network slice to the network slice set of the terminal that is allowed to access.
  • the sending unit 1302 is specifically configured to send, to the terminal, an updated network slice set that is allowed to access.
  • the sending unit 1302 is further configured to send, to the terminal, indication information, where the indication information is used to indicate that the PLMN supports the network slice.
  • the processing unit 1303 is configured to add the identifier information of the network slice to the network slice set of the terminal that is allowed to access; the sending unit 1302 is specifically configured to send a configuration update message to the terminal, where the configuration update message includes the updated allowed access Network slice collection.
  • the configuration update message further includes indication information.
  • the device is a chip of a policy control network element or a policy control network element, and then:
  • the processing unit 1303 is further configured to determine a mobility management network element that is registered by the terminal.
  • the sending unit 1302 is specifically configured to send, by using the mobility management network element, indication information to the terminal, where the indication information is used to indicate that the PLMN supports the network slice.
  • the receiving unit 1301 is further configured to receive the identifier information of the network slice sent by the mobility management network element, the identifier information of the mobility management network element, and the identifier information of the terminal.
  • the apparatus may be used to implement the steps performed by the AMF in the embodiment shown in FIG. 5 or the PCF in the embodiment shown in FIG. 6 to FIG. 7 in the method of the embodiment of the present invention. This article will not be repeated here.
  • the function/implementation process of the receiving unit 1301, the transmitting unit 1302, and the processing unit 1303 in FIG. 13 can be implemented by the processor 1201 in FIG. 12 calling the computer executing instructions stored in the memory 1203.
  • the function/implementation process of the processing unit 1303 in FIG. 13 can be implemented by the processor 1201 in FIG. 12 calling the computer execution instruction stored in the memory 1203, and the function/implementation of the receiving unit 1301 and the transmitting unit 1302 in FIG.
  • the process can be implemented by communication interface 1204 in FIG.
  • the function/implementation process of the receiving unit 1301 and the sending unit 1302 may also be implemented by a pin or a circuit or the like.
  • the memory 1203 may be a memory unit within the chip, such as a register, a cache, or the like.
  • the memory 1203 may be a storage unit located outside the chip in the communication network element, which is not specifically limited in this embodiment of the present application.
  • the present application may divide the functional modules of the device according to the above method example.
  • each functional module may be divided according to each function, or two or more functions may be integrated into one processing module.
  • the above integrated modules can be implemented in the form of hardware or in the form of software functional modules.
  • FIG. 14 shows a schematic diagram of a device, which may be the mobility management network element or the chip of the mobility management network element involved in the above embodiment.
  • the apparatus 1400 includes a receiving unit 1401 and a transmitting unit 1402.
  • the device 1400 further includes a processing unit 1403.
  • the device 1400 further includes a storage unit 1404.
  • the receiving unit 1401 is configured to receive an update message from the policy control network element, where the update message includes the indication information and the identifier information of the terminal, where the indication information is used to indicate that the public land mobile network PLMN supports the network slice, where The PLMN has not supported the network slicing; the sending unit 1402 is configured to notify the terminal PLMN to support the network slicing, and the terminal is the terminal that has requested the network slice failure and has signed the network slice.
  • the processing unit 1403 is configured to add the identifier information of the network slice to the network slice set of the terminal that is allowed to access.
  • the sending unit 1402 is specifically configured to send, to the terminal, an updated network slice set that is allowed to access.
  • the sending unit 1402 is further configured to send, to the terminal, indication information, where the indication information is used to indicate that the PLMN supports the network slice.
  • the processing unit 1403 is configured to add the identifier information of the network slice to the network slice set of the terminal that is allowed to access.
  • the sending unit 1402 is specifically configured to send a configuration update message to the terminal, where the configuration update message includes the updated network slice set that is allowed to access.
  • the configuration update message further includes indication information.
  • the sending unit 1402 is specifically configured to send a NAS message to the terminal, where the NAS message includes indication information.
  • the sending unit 1402 is further configured to send the identifier information of the terminal, the identifier information of the mobility management network element, and the identifier information of the network slice to the policy control network element.
  • the receiving unit 1401 is configured to receive a notification message from the network slice selection network element, where the notification message includes identifier information of the network slice and identification information of the at least one tracking area, where the network slice is in the The at least one tracking area is available, the network slice is unavailable in the at least one tracking area;
  • the processing unit 1403 is configured to determine an updated network slice set that is allowed to access, the updated network that allows access
  • the slice set includes the identifier information of the network slice, where the terminal is located in a registration area of the terminal, and the terminal is capable of accessing the network slice;
  • the sending unit 1402 is configured to send the Updated network slice set that allows access.
  • the processing unit 1403 is further configured to determine that the network slice is available in a registration area of the terminal, and determine that the terminal is capable of accessing the network slice.
  • the storage unit 1404 is configured to store, before the receiving unit 1401 receives the notification message from the network slice selection network element, the network slice set of the terminal that is denied access, and the rejecting The incoming network slice set includes identification information of the network slice.
  • the receiving unit 1401 is further configured to receive a registration request from the terminal before the sending unit 1402 sends the updated network slice set that is allowed to access to the terminal.
  • the message, the registration request message includes identification information of the network slice.
  • the sending unit 1402 is specifically configured to send a registration accept message to the terminal, where the registration accept message includes the updated network slice set that is allowed to access.
  • the apparatus may be used to implement the steps performed by the AMF in the embodiments shown in FIGS. 6-7 and 10-11 in the method of the embodiment of the present invention, and related features may be referred to above. No longer.
  • the function/implementation process of the receiving unit 1401, the transmitting unit 1402, and the processing unit 1403 in FIG. 14 can be implemented by the processor 1201 in FIG. 12 calling the computer executing instructions stored in the memory 1203.
  • the function/implementation process of the processing unit 1403 in FIG. 14 can be implemented by the processor 1201 in FIG. 12 calling the computer execution instruction stored in the memory 1203, and the function/implementation of the receiving unit 1401 and the transmitting unit 1402 in FIG.
  • the process can be implemented by communication interface 1204 in FIG.
  • the function/implementation process of the receiving unit 1401 and the transmitting unit 1402 may also be implemented by a pin or a circuit or the like.
  • the memory 1203 may be a memory unit within the chip, such as a register, a cache, or the like.
  • the memory 1203 may be a storage unit located outside the chip in the mobility management network element, which is not specifically limited in this embodiment of the present application.
  • the present application may divide a functional module into a device according to the above method example.
  • each functional module may be divided according to each function, or two or more functions may be integrated into one processing module.
  • the above integrated modules can be implemented in the form of hardware or in the form of software functional modules.
  • FIG. 15 shows a schematic diagram of a device, which may be a chip of a policy control network element or a policy control network element involved in the foregoing embodiment.
  • the apparatus 1500 includes a receiving unit 1501, a transmitting unit 1502, and a processing unit 1503.
  • the receiving unit 1501 is configured to receive the identifier information of the terminal from the mobility management network element and the identifier information of the network slice, where the network slice is a network slice that is not supported by the current registration area of the terminal;
  • the processing unit 1503 is configured to obtain, from the network slice selection network element, a service area corresponding to the network slice.
  • the transmitting unit 1502 notifies the terminal network slice that it is available.
  • the sending unit 1502 is further configured to subscribe to the mobility management network element: when the location of the terminal is updated, the mobility management network element sends the updated location of the terminal to the device.
  • the sending unit 1502 is specifically configured to: send, by the mobility management network element, indication information to the terminal, where the indication information is used to indicate that the network slice is available.
  • the device may be used to implement the steps performed by the PCF in the embodiment shown in FIG. 8 in the method of the embodiment of the present invention.
  • the device may be used to implement the steps performed by the PCF in the embodiment shown in FIG. 8 in the method of the embodiment of the present invention.
  • the function/implementation process of the receiving unit 1501, the transmitting unit 1502, and the processing unit 1503 in FIG. 15 can be implemented by the processor 1201 in FIG. 12 calling the computer executing instructions stored in the memory 1203.
  • the function/implementation process of the processing unit 1503 in FIG. 15 can be implemented by the processor 1201 in FIG. 12 calling the computer execution instruction stored in the memory 1203, and the function/implementation of the receiving unit 1501 and the transmitting unit 1502 in FIG.
  • the process can be implemented by communication interface 1204 in FIG.
  • the function/implementation process of the receiving unit 1501 and the transmitting unit 1502 may also be implemented by a pin or a circuit or the like.
  • the memory 1203 may be a memory unit within the chip, such as a register, a cache, or the like.
  • the memory 1203 may be a storage unit located outside the chip in the policy control network element, which is not specifically limited in this embodiment of the present application.
  • the present application may divide a functional module into a device according to the above method example.
  • each functional module may be divided according to each function, or two or more functions may be integrated into one processing module.
  • the above integrated modules can be implemented in the form of hardware or in the form of software functional modules.
  • FIG. 16 shows a schematic diagram of a device, which may be a chip of a network slice selection network element or a network slice selection network element involved in the foregoing embodiment. .
  • the apparatus 1600 includes a transmitting unit 1602 and a processing unit 1603.
  • a receiving unit 1601 is further included.
  • the processing unit 1603 is configured to determine that the public land mobile network PLMN supports the network slice, where the PLMN does not support the network slice;
  • the sending unit 1602 is configured to send a notification message to the communication network element, where the notification message includes identifier information of the network slice, where the notification message is used to indicate that the PLMN supports the network slice.
  • the communication network element is a policy control network element or a mobility management network element.
  • the receiving unit 1601 is configured to receive a subscription from the communication network element: when the PLMN supports the network slice, the network slice selects the network element to notify the communication network element.
  • the processing unit 1603 is further configured to determine, according to the slice type supported by the mobility management network element in the PLMN, the mobility management network element supporting the network slice as the communication network element. It should be understood that the device may be used to implement the steps performed by the NSSF in the embodiment shown in FIG. 5-7 in the method of the embodiment of the present invention. For related features, reference may be made to the above, and details are not described herein again.
  • the function/implementation process of the receiving unit 1601, the transmitting unit 1602, and the processing unit 1603 in FIG. 16 can be implemented by the processor 1201 in FIG. 12 calling a computer executing instruction stored in the memory 1203.
  • the function/implementation process of the processing unit 1603 in FIG. 16 can be implemented by the processor 1201 in FIG. 12 calling the computer execution instruction stored in the memory 1203, and the function/implementation of the receiving unit 1601 and the transmitting unit 1602 in FIG.
  • the process can be implemented by communication interface 1204 in FIG.
  • the function/implementation process of the receiving unit 1601 and the sending unit 1602 can also be implemented by using a pin or a circuit or the like.
  • the memory 1203 may be a memory unit within the chip, such as a register, a cache, or the like.
  • the memory 1203 may be a storage unit located outside the chip in the network slice selection network element, which is not specifically limited in this embodiment of the present application.
  • the present application may divide a functional module into a device according to the above method example.
  • each functional module may be divided according to each function, or two or more functions may be integrated into one processing module.
  • the above integrated modules can be implemented in the form of hardware or in the form of software functional modules.
  • FIG. 17 shows a schematic diagram of a device, which may be the chip of the terminal or terminal involved in the above embodiment.
  • the apparatus 1700 includes a receiving unit 1701, a transmitting unit 1702, and a processing unit 1703.
  • the receiving unit 1701 is configured to receive a network slice set of the terminal that is allowed to access from the terminal of the mobility management network element, and a network slice set that denies access, where the network slice set of the denied access includes an identifier of the network slice.
  • Information the terminal is located in the registration area of the terminal;
  • the sending unit 1702 is configured to send a registration request message to the mobility management network element, where the registration request message includes identifier information of the network slice;
  • the receiving unit 1701 is further configured to receive, by the mobility management network element, an updated set of allowed access network slices, where the updated set of network slices allowed to access includes the identifier information of the network slice,
  • the network slice is available within a registration area of the terminal, the network slice being unavailable in the registration area of the terminal.
  • the receiving unit 1701 is specifically configured to receive a registration accept message from the mobility management network element, where the registration accept message includes the updated set of network slices allowed to access. .
  • the device may be used to implement the steps performed by the terminal in the embodiment shown in FIG. 10 to FIG. 11 in the method of the embodiment of the present invention.
  • the device may be used to implement the steps performed by the terminal in the embodiment shown in FIG. 10 to FIG. 11 in the method of the embodiment of the present invention.
  • the function/implementation process of the receiving unit 1701, the transmitting unit 1702, and the processing unit 1703 in FIG. 17 can be implemented by the processor 1201 in FIG. 12 calling the computer executing instructions stored in the memory 1203.
  • the function/implementation process of the processing unit 1703 in FIG. 17 can be implemented by the processor 1201 in FIG. 12 calling the computer execution instruction stored in the memory 1203, and the function/implementation of the receiving unit 1701 and the transmitting unit 1702 in FIG.
  • the process can be implemented by communication interface 1204 in FIG.
  • the function/implementation process of the receiving unit 1701 and the sending unit 1702 may also be implemented by using a pin or a circuit or the like.
  • the memory 1203 may be a memory unit within the chip, such as a register, a cache, or the like.
  • the memory 1203 may be a storage unit located outside the chip in the terminal, which is not specifically limited in this embodiment of the present application.
  • the above embodiments it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • software it may be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions.
  • the computer program instructions When the computer program instructions are loaded and executed on a computer, the processes or functions described in accordance with embodiments of the present invention are generated in whole or in part.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • the computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be from a website site, computer, server or data center Transfer to another website site, computer, server, or data center by wire (eg, coaxial cable, fiber optic, digital subscriber line (DSL), or wireless (eg, infrared, wireless, microwave, etc.).
  • the computer readable storage medium can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or the like that includes one or more available media.
  • the usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (such as a Solid State Disk (SSD)) or the like.
  • a magnetic medium eg, a floppy disk, a hard disk, a magnetic tape
  • an optical medium eg, a DVD
  • a semiconductor medium such as a Solid State Disk (SSD)
  • a general purpose processor may be a microprocessor.
  • the general purpose processor may be any conventional processor, controller, microcontroller, or state machine.
  • the processor may also be implemented by a combination of computing devices, such as a digital signal processor and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a digital signal processor core, or any other similar configuration. achieve.
  • the steps of the method or algorithm described in the embodiments of the present application may 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 RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium in the art.
  • the storage medium can be coupled to the processor such that the processor can read information from the storage medium and can write information to the storage medium.
  • the storage medium can also be integrated into the processor.
  • the processor and the storage medium may be disposed in the ASIC, and the ASIC may be disposed in the terminal device. Alternatively, the processor and the storage medium may also be disposed in different components in the terminal device.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

Abstract

本申请提供一种切片信息更新方法及装置。该方法包括：当网络切片选择网元确定PLMN曾不支持的网络切片更新为支持时，向通信网元发送通知消息，通知消息用于指示PLMN支持该网络切片，然后通信网元通知曾请求网络切片失败且签约了网络切片的终端：PLMN当前支持该网络切片。从而实现了让相应的终端获知PLMN当前支持该网络切片。

Description

一种切片信息更新方法及装置
本申请要求在2017年12月20日提交中华人民共和国知识产权局、申请号为201711385748.8、发明名称为“一种切片信息更新方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。本申请要求在2018年12月10日提交中华人民共和国知识产权局、申请号为201811505349.5、发明名称为“一种切片信息更新方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及移动通信技术领域，尤其涉及一种切片信息更新方法及装置。
背景技术
当核心网部署了网络切片，终端初始附着到网络时，会触发网络切片的选择过程。网络侧根据终端请求的网络切片、终端的签约数据等信息，为终端选择允许接入的网络切片。
网络侧为终端选择允许接入的网络切片之后，向终端通知选择的网络切片。若网络侧确定终端的签约数据中包括公共陆地移动网络(Public Land Mobile Network，PLMN)不支持的网络切片，则网络侧还向终端通知这些PLMN不支持的网络切片。
在上述场景下，当上述PLMN不支持的网络切片更新为PLMN支持时，网络侧如何通知终端以及通知哪些终端，目前还没有相应的解决方案。
发明内容
本申请提供一种切片信息更新方法及装置，以实现当PLMN不支持的网络切片更新为PLMN支持时，通知相应的终端。
第一方面，本申请提供一种切片信息更新方法。该方法包括：首先，通信网元接收来自网络切片选择网元的通知消息，通知消息包括网络切片的标识信息，通知消息用于指示PLMN支持网络切片，其中，PLMN曾不支持网络切片。然后，通信网元通知终端PLMN支持网络切片，终端为曾请求网络切片失败且签约了网络切片的终端。其中，通信网元为移动性管理网元或策略控制网元。
上述方法，当网络切片选择网元确定PLMN曾不支持的网络切片更新为支持时，向通信网元发送通知消息，通知消息用于指示PLMN支持该网络切片，然后通信网元通知曾请求网络切片失败且签约了网络切片的终端：PLMN当前支持该网络切片。从而实现了让相应的终端获知PLMN当前支持该网络切片，进而终端在有该网络切片对应的业务的需求时，可以使用该网络切片，有助于提升终端的业务能力。
在一种可能的实现方式中，通信网元可根据终端上下文，确定上述终端。
在一种可能的实现方式中，通信网元为移动性管理网元。则进一步地还包括：移动性管理网元将网络切片的标识信息加入终端的允许接入的网络切片集合。则通信网元通知终端PLMN支持网络切片，具体包括：移动性管理网元向终端发送更新的允许接入的网络切片集合。进一步地，移动性管理网元向终端发送指示信息，指示信息用 于指示PLMN支持网络切片。
例如，作为一种具体实现方式，移动性管理网元向终端发送配置更新消息，配置更新消息包括更新的允许接入的网络切片集合。可选地，配置更新消息还包括指示信息。
上述方法，由移动性管理网元通过更新的允许接入的网络切片集合的方式，通知终端PLMN支持网络切片。
在另一种可能的实现方式中，通信网元为策略控制网元。则进一步还包括：策略控制网元确定终端注册的移动性管理网元。通信网元通知终端PLMN支持网络切片，具体包括：策略控制网元通过移动性管理网元，向终端发送指示信息，指示信息用于指示PLMN支持网络切片。可选地，策略控制网元还接收移动性管理网元发送的网络切片的标识信息、移动性管理网元的标识信息和终端的标识信息。
上述实现方式，由策略控制网元向终端发送指示信息，指示PLMN支持上述网络切片。
第二方面，本申请提供一种切片信息更新方法。该方法包括：移动性管理网元接收来自策略控制网元的更新消息，更新消息包括指示信息和终端的标识信息，指示信息用于指示公共陆地移动网络PLMN支持网络切片，其中，PLMN曾不支持网络切片。然后，移动性管理网元通知终端PLMN支持网络切片，终端为曾请求网络切片失败且签约了网络切片的终端。
上述方法，当移动性管理网元接收到来自策略控制网元的通知消息，通知消息用于指示PLMN支持该网络切片，则移动性管理网元向通知消息中指示的终端发送通知：PLMN当前支持该网络切片。从而实现了让相应的终端获知PLMN当前支持该网络切片，进而终端在有该网络切片对应的业务的需求时，可以使用该网络切片，有助于提升终端的业务能力。
在一种可能的实现方式中，还包括：移动性管理网元将网络切片的标识信息加入终端的允许接入的网络切片集合。移动性管理网元通知终端PLMN支持网络切片，具体包括：移动性管理网元向终端发送更新的允许接入的网络切片集合。可选地，移动性管理网元还向终端发送指示信息，指示信息用于指示PLMN支持网络切片。
例如，作为一种具体实现方式，移动性管理网元向终端发送配置更新消息，配置更新消息包括更新的允许接入的网络切片集合。可选地，配置更新消息还包括指示信息。
上述方法，由移动性管理网元通过更新的允许接入的网络切片集合的方式，通知终端PLMN支持网络切片。
在一种可能的实现方式中，移动性管理网元通知终端PLMN支持网络切片，包括：移动性管理网元向终端发送NAS消息，NAS消息包括指示信息。
在一种可能的实现方式中，进一步还包括：移动性管理网元向策略控制网元发送终端的标识信息、移动性管理网元的标识信息和网络切片的标识信息。
第三方面，本申请提供一种切片信息更新方法。该方法包括：策略控制网元接收来自移动性管理网元的终端的标识信息和网络切片的标识信息，网络切片为终端的当前注册区域不支持的网络切片。接着，策略控制网元从网络切片选择网元获取网络切片对应的服务区域。若策略控制网元获知终端移动至服务区域，则通知终端网络切片 可用。
上述方法，策略控制网元若确定终端移动至网络切片对应的服务区域，则通知该终端该网络切片当前可用。其中，该网络切片为终端未移动至该网络切片对应的服务区域之前所在的区域不支持的网络切片。从而实现了通知相应的终端：网络切片当前可用，进而终端在有该网络切片对应的业务的需求时，可以使用该网络切片，有助于提升终端的业务能力。
在一种可能的实现方式中，还包括：策略控制网元向移动性管理网元订阅：当终端的位置发生更新时，移动性管理网元向策略控制网元发送终端更新后的位置。
在一种可能的实现方式中，策略控制网元通知终端网络切片当前可用，具体包括：策略控制网元通过移动性管理网元向终端发送指示信息，指示信息用于指示网络切片可用。
第四方面，本申请提供一种切片信息更新方法。该方法包括：网络切片选择网元确定PLMN支持网络切片，其中，PLMN曾不支持网络切片。接着，网络切片选择网元向通信网元发送通知消息，通知消息包括网络切片的标识信息，通知消息用于指示PLMN支持网络切片。其中，通信网元为策略控制网元或移动性管理网元。
上述方法，当网络切片选择网元确定PLMN曾不支持的网络切片更新为支持时，向通信网元发送通知消息，通知消息用于指示PLMN支持该网络切片，然后可以由通信网元通知曾请求网络切片失败且签约了网络切片的终端：PLMN当前支持该网络切片。从而实现了让相应的终端获知PLMN当前支持该网络切片，进而终端在有该网络切片对应的业务的需求时，可以使用该网络切片，有助于提升终端的业务能力。
在一种可能的实现方式中，进一步还包括：网络切片选择网元接收来自通信网元的订阅：当PLMN支持网络切片时，网络切片选择网元通知通信网元。
在一种可能的实现方式中，还包括：网络切片选择网元根据PLMN中的移动性管理网元支持的切片类型，确定支持网络切片的移动性管理网元为需要发送通知消息的通信网元。
第五方面，本申请提供一种切片信息更新方法。该方法包括：移动性管理网元接收来自网络切片选择网元的通知消息，通知消息包括网络切片的标识信息和至少一个跟踪区域的标识信息，该网络切片在所述至少一个跟踪区域内可用，该网络切片在所述至少一个跟踪区域内曾不可用；移动性管理网元确定更新的允许接入的网络切片集合，该更新的允许接入的网络切片集合包括所述网络切片的标识信息，其中，终端位于终端的注册区域内，且终端能够接入该网络切片；移动性管理网元向终端发送所述更新的允许接入的网络切片集合。
其中，终端能够接入上述网络切片，指的是该网络切片在该终端的注册区域内的任意一个跟踪区域内都可用。
上述方法，当网络切片选择网元确定网络切片在至少一个跟踪区域由不可用更新为可用时，向移动性管理网元发送通知消息，通知消息包括该网络切片的标识信息和上述至少一个跟踪区域的标识信息，然后移动性管理网元确定更新的允许接入的网络切片集合，该更新的允许接入的网络切片集合包括所述网络切片的标识信息，以及向终端发送该更新的允许接入的网络切片集合。从而实现了使得相应的终端获知当前能够接入该网络切片，进而终端在有该网络切片对应的业务的需求时，可以使用该网络 切片，有助于提升终端的业务能力。
在一种可能的实现方式中，移动性管理网元确定上述网络切片在终端的注册区域内可用，则确定该终端能够接入上述网络切片。
在一种可能的实现方式中，移动性管理网元接收来自网络切片选择网元的通知消息之前，还存储该终端的拒绝接入的网络切片集合，该拒绝接入的网络切片集合包括上述网络切片的标识信息。
在一种可能的实现方式中，移动性管理网元向终端发送更新的允许接入的网络切片集合之前，还接收来自终端的注册请求消息，所述注册请求消息包括上述网络切片的标识信息。
在一种可能的实现方式中，移动性管理网元向终端发送更新的允许接入的网络切片集合，具体包括：移动性管理网元向终端发送注册接受消息，该注册接受消息包括上述更新的允许接入的网络切片集合。
第六方面，本申请提供一种切片信息更新方法。该方法包括：终端接收来自移动性管理网元的终端的允许接入的网络切片集合和拒绝接入的网络切片集合，所述拒绝接入的网络切片集合包括网络切片的标识信息，该终端位于该终端的注册区域内；终端向移动性管理网元发送注册请求消息，所述注册请求消息包括所述网络切片的标识信息；终端接收来自移动性管理网元的更新的允许接入的网络切片的集合，该更新的允许接入的网络切片的集合包括上述网络切片的标识信息，该网络切片在该终端的注册区域内可用，该网络切片在该终端的注册区域内曾不可用。
上述方法，终端可以在注册请求消息中携带该终端曾被拒绝接入的网络切片的标识信息，若移动性管理网元确定终端当前支持该网络切片，则将该网络切片的标识信息加入到更新的允许接入的网络切片的集合并将该更新的允许接入的网络切片的集合发送给终端，从而终端后续可以使用该网络切片。从而实现了使得相应的终端获知当前能够接入该网络切片，进而终端在有该网络切片对应的业务的需求时，可以使用该网络切片，有助于提升终端的业务能力。
在一种可能的实现方式中，终端接收来自移动性管理网元的更新的允许接入的网络切片的集合，具体包括：终端接收来自移动性管理网元的注册接受消息，该注册接受消息包括上述更新的允许接入的网络切片的集合。
第七方面，本申请提供一种装置，该装置可以是通信网元，也可以是芯片，该通信网元可以是移动性管理网元或策略控制网元。该装置具有实现上述第一方面的各实施例的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第八方面，提供了一种装置，包括：处理器和存储器；该存储器用于存储计算机执行指令，当该装置运行时，该处理器执行该存储器存储的该计算机执行指令，以使该装置执行如上述第一方面中任一所述的切片信息更新方法。
第九方面，本申请提供一种装置，该装置可以是移动性管理网元，也可以是芯片。该装置具有实现上述第二方面的各实施例的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第十方面，提供了一种装置，包括：处理器和存储器；该存储器用于存储计算机 执行指令，当该装置运行时，该处理器执行该存储器存储的该计算机执行指令，以使该装置执行如上述第二方面中任一所述的切片信息更新方法。
第十一方面，本申请提供一种装置，该装置可以是策略控制网元，也可以是芯片。该装置具有实现上述第三方面的各实施例的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第十二方面，提供了一种装置，包括：处理器和存储器；该存储器用于存储计算机执行指令，当该装置运行时，该处理器执行该存储器存储的该计算机执行指令，以使该装置执行如上述第三方面中任一所述的切片信息更新方法。
第十三方面，本申请提供一种装置，该装置可以是网络切片选择网元，也可以是芯片。该装置具有实现上述第四方面的各实施例的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第十四方面，提供了一种装置，包括：处理器和存储器；该存储器用于存储计算机执行指令，当该装置运行时，该处理器执行该存储器存储的该计算机执行指令，以使该装置执行如上述第四方面中任一所述的切片信息更新方法。
第十五方面，本申请提供一种装置，该装置可以是移动性管理网元，也可以是芯片。该装置具有实现上述第五方面的各实施例的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第十六方面，提供了一种装置，包括：处理器和存储器；该存储器用于存储计算机执行指令，当该装置运行时，该处理器执行该存储器存储的该计算机执行指令，以使该装置执行如上述第五方面中任一所述的切片信息更新方法。
第十七方面，本申请提供一种装置，该装置可以是终端，也可以是芯片。该装置具有实现上述第六方面的各实施例的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第十八方面，提供了一种装置，包括：处理器和存储器；该存储器用于存储计算机执行指令，当该装置运行时，该处理器执行该存储器存储的该计算机执行指令，以使该装置执行如上述第六方面中任一所述的切片信息更新方法。
第十九方面，本申请还提供一种计算机可读存储介质，所述计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机执行上述各方面所述的方法。
第二十方面，本申请还提供一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述各方面所述的方法。
第二十一方面，本申请还提供一种系统，该系统包括上述第七方面或第八方面的装置，和，第十三方面或第十四方面的装置。
第二十二方面，本申请还提供一种系统，该系统包括上述第九方面或第十方面的装置，和，第十三方面或第十四方面的装置。
第二十三方面，本申请还提供一种系统，该系统包括上述第十五方面或第十六方面的装置，和，第十七方面或第十八方面的装置。
附图说明
图1为本申请提供的一种可能的网络架构示意图；
图2为本申请提供的一种具体系统架构示意图；
图3为本申请提供的第一种应用场景示意图；
图4为本申请提供的第二种应用场景示意图；
图5为本申请提供的一种切片信息更新方法示意图；
图6为本申请提供的另一种切片信息更新方法示意图；
图7为本申请提供的另一种切片信息更新方法示意图；
图8为本申请提供的另一种切片信息更新方法示意图；
图9为本申请提供的第三种应用场景示意图；
图10为本申请提供的另一种切片信息更新方法示意图；
图11为本申请提供的另一种切片信息更新方法示意图；
图12为本申请提供的一种装置示意图；
图13为本申请提供的另一种装置示意图；
图14为本申请提供的另一种装置示意图；
图15为本申请提供的另一种装置示意图；
图16为本申请提供的另一种装置示意图；
图17为本申请提供的另一种装置示意图。
具体实施方式
为了使本申请的目的、技术方案和优点更加清楚，下面将结合附图对本申请作进一步地详细描述。方法实施例中的具体操作方法也可以应用于装置实施例或系统实施例中。其中，在本申请的描述中，除非另有说明，“多个”的含义是两个或两个以上。
本申请实施例描述的网络架构以及业务场景是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
如图1所示，为本申请适用的一种可能的网络架构示意图。该网络架构包括终端、移动性管理网元、策略控制网元和网络切片选择网元。其中，移动性管理网元和策略控制网元均可以称为通信网元，即本申请中通信网元为移动性管理网元，或为策略控制网元。
终端是一种具有无线收发功能的设备，可以部署在陆地上，包括室内或室外、手持或车载；也可以部署在水面上(如轮船等)；还可以部署在空中(例如飞机、气球和卫星上等)。所述终端可以是手机(mobile phone)、平板电脑(pad)、带无线收发功能的电脑、虚拟现实(virtual reality，VR)终端、增强现实(augmented reality，AR)终端、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程医疗(remote medical)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端等。
移动性管理网元，负责用户的移动性管理，包括移动状态管理，分配用户临时身 份标识，认证和授权用户。
策略控制网元，包含用户签约数据管理功能，策略控制功能，计费策略控制功能，服务质量(Quality of Service，QoS)控制等。
网络切片选择网元，负责确定网络切片实例，选择移动性管理网元等。
可以理解的是,上述功能既可以是硬件设备中的网络元件,也可以是在专用硬件上运行软件功能，或者是平台(例如,云平台)上实例化的虚拟化功能。
需要说明的是，移动性管理网元在5G可以称为接入与移动性管理功能(access and mobility management function，AMF)网元。策略控制网元在5G可以称为策略控制功能(Policy Control Function，PCF)网元。网络切片选择网元在5G可以称为网络切片选择功能(Network Slice Selection Function，NSSF)网元。当然，在未来通信，如6G中，移动性管理网元仍可以称为AMF网元或有其它的名称，策略控制网元仍可以称为PCF网元或有其它的名称，网络切片选择网元仍可以称为NSSF网元或有其它的名称，本申请不做限定。
为方便说明，本申请后续，以移动性管理网元称为AMF网元，策略控制网元称为PCF网元，网络切片选择网元称为NSSF网元为例进行说明。进一步地，将AMF网元简称为AMF，PCF网元简称为PCF，NSSF网元简称为NSSF。即本申请后续所描述的AMF均可替换为移动性管理网元，PCF均可替换为策略控制网元，NSSF均可替换为网络切片选择网元。
如图2所示，为基于图1所示的系统架构的一种具体系统架构示意图。该系统架构包括终端、无线接入网络(radio access network)设备、核心网的控制面网元。其中，核心网的控制面网元包括AMF、PCF和NSSF。
其中，终端、AMF、PCF和NSSF的功能的介绍可参考前述描述，这里不再赘述。
RAN设备，是一种为终端提供无线通信功能的设备。RAN设备例如包括但不限于：5G中的下一代基站(g nodeB，gNB)、演进型节点B(evolved node B，eNB)、无线网络控制器(radio network controller，RNC)、节点B(node B，NB)、基站控制器(base station controller，BSC)、基站收发台(base transceiver station，BTS)、家庭基站(例如，home evolved nodeB，或home node B，HNB)、基带单元(baseBand unit，BBU)、传输点(transmitting and receiving point，TRP)、发射点(transmitting point，TP)、移动交换中心等。
本申请中，RAN设备可用于转发终端与AMF之间通信的非接入层(Non Access Stratum，NAS)消息。
下面结合图1-图2，对本申请提供的切片信息更新做具体说明，以解决背景技术中提到的问题。需要说明的是，本申请并不限定于图1-图2所示的系统架构，还可以应用于未来其它的通信系统，例如6G系统架构等。并且，本申请上述所使用的各个网元的名称，在未来通信系统中，可以保持功能相同，但名称可能会改变。
在详细介绍本申请的方案之前，先对本申请要解决的技术问题的相关背景做简单介绍说明。
目前，多种多样的场景对第三代合作伙伴计划(3rd Generation Partnership Project，3GPP)生态系统提出了不同的需求，如计费、策略、安全、移动性等需求。3GPP强调了网络切片之间不相互影响，例如突发的大量的抄表业务不应该影响正常的移动宽 带业务。为了满足多样性需求和切片间的隔离，需要业务间相对独立的管理和运维，并提供量身定做的业务功能和分析能力。不同类型业务的实例部署在不同的网络切片上，相同业务类型的不同实例也可部署在不同的网络切片上。
当核心网部署了网络切片，用户初始附着(或称为注册)到网络时，会触发网络切片的选择过程。切片的选择过程取决于用户的签约数据，本地配置信息，漫游协议，运营商的策略等等。在网络切片的选择过程中，需要综合考虑以上参数，才能为终端选择最佳的切片类型。
当终端需要接入到某个网络切片时，终端可以提供请求的网络切片给核心网，用于核心网为终端选择网络切片实例。其中，终端请求的网络切片，可以用请求的网络切片选择辅助信息(requested network slice selection assistance information，requested NSSAI)来表示。requested NSSAI是由一个或多个单个网络切片选择辅助信息(single network slice selection assistance information，S-NSSAI)构成，每个S-NSSAI用于标识一个网络切片类型，也可以理解为，S-NSSAI用于标识网络切片，或者可以理解为S-NSSAI是网络切片的标识信息。
终端在注册入网之前，本地存储有预配置的(configured)NSSAI，其中，configured NSSAI包含的S-NSSAI与终端签约的NSSAI中包含的S-NSSAI都是HPLMN定义的S-NSSAI。一种可能的实现方法为，configured NSSAI包含的S-NSSAI是终端签约的NSSAI中包含的S-NSSAI中的子集或全集。例如，终端的签约的NSSAI为{S-NSSAI1、S-NSSAI2、S-NSSAI3、S-NSSAI4、S-NSSAI5}，则configured NSSAI为{S-NSSAI1、S-NSSAI2、S-NSSAI3、S-NSSAI4、S-NSSAI5}的子集或全集。
终端在初始注册入网时，携带一个requested NSSAI，其中，requested NSSAI是configured NSSAI中所包含的S-NSSAI的子集或全集。例如，configured NSSAI为{S-NSSAI1、S-NSSAI2、S-NSSAI3、S-NSSAI4}，则requested NSSAI为{S-NSSAI1、S-NSSAI2、S-NSSAI3、S-NSSAI4}的子集或全集。
终端注册到网络之后，核心网网元(如AMF或NSSF)根据终端的签约数据、终端的requested NSSAI、漫游协议以及本地配置等信息综合判断，为终端选择允许接入的网络切片集合。其中，允许接入的网络切片集合可以用允许的(allowed)NSSAI来表示，allowed NSSAI包含的S-NSSAI为终端的签约NSSAI中包含的S-NSSAI的子集或全集，或者allowed NSSAI为requested NSSAI中所包含的S-NSSA的子集或全集。然后，核心网网元将allowed NSSAI发送给终端，例如携带于注册接受消息中发送至终端。终端后续需要发起业务请求时，可从allowed NSSAI中选择S-NSSAI发起业务。
进一步地，核心网网元在向终端发送allowed NSSAI的同时，还会向终端返回拒绝的(rejected)NSSAI以及rejected NSSAI中的每个S-NSSAI被拒绝的原因。下面举例说明。
假设终端的签约NSSAI为{S-NSSAI1、S-NSSAI2、S-NSSAI3、S-NSSAI4}，且终端当前位于AMF set 1的服务范围。
下面结合附图3-图4，分两种应用场景进行说明。
需要说明的是，本申请中提到的切片，有时也称为网络切片，二者指代相同内容，具有相同含义，可以相互替换，后续不再特意说明。
参考图3，为本申请提供的第一种应用场景示意图。其中，网络侧包括两个AMF 集合(set)，分别为AMF set 1和AMF set 2。其中，AMF set 1中的任一AMF支持的网络切片(slicing)为：{切片1、切片2}，AMF set 2中的任一AMF支持的网络切片为：{切片4}，并且网络中还包括一个PLMN暂时不支持的切片3，暂时不支持的原因可能是暂时未部署或暂时关闭等。若后期该切片3更新为PLMN支持，即更新为可用，则该切片3归属AMF set 1。
其中，切片1、切片2、切片3、切片4，可以分别由S-NSSAI1、S-NSSAI2、S-NSSAI3、S-NSSAI4标识。即S-NSSAI1为切片1的标识信息、S-NSSAI2为切片2的标识信息、S-NSSAI3为切片3的标识信息、S-NSSAI4为切片4的标识信息。
每个网络切片对应一个或多个会话管理功能(Session Management Function，SMF)网元和一个或多个用户面功能(User Plane Function，UPF)网元。例如，如图3所示，切片1对应SMF1和UPF1，切片2对应SMF2和UPF2，切片3对应SMF3和UPF3，切片4对应SMF4和UPF4。
在图3所示的示例中，假设终端注册至网络后，当前接入的AMF(该AMF也称为为终端提供服务的AMF)为AMF set 1中的一个AMF，则为终端提供服务的AMF可以使用的切片为切片1和切片2。
针对切片3，该切片3可以称为PLMN不支持的网络切片，或者称为PLMN暂时不支持的网络切片，或者称为PLMN当前不支持的网络切片。当该切片3更新为PLMN支持时，则该切片3也可以由为终端提供服务的AMF使用。
针对切片4，如果终端的当前注册区域(register area，RA)(该注册区域即为为终端提供服务的AMF所覆盖的区域)内不包括AMF set 2中的任一AMF，则该切片4可以称为终端的当前注册区域不支持的网络切片。也可以理解为，终端在当前所在的位置无法使用该切片4。只有当终端移动至该切片4所能够服务的范围内时，终端才可以使用该切片4。例如，终端移动至AMF set 2中的某个AMF的覆盖范围时，只要终端注册至该AMF，终端即可使用该切片4，即可以使用该切片4发起业务流程。
在上述图3所示的示例中，切片4与切片1、切片2、切片3之间相互隔离。也可理解为，终端在使用切片4时，则不能使用切片1、切片2或切片3；终端在使用切片1、切片2或切片3时，则不能使用切片4。
在上述图3所示的示例中，切片3虽然在PLMN内无法使用，但由于切片1、切片2、切片3都归属AMF set1，因而切片3与切片1、切片2之间不是相互隔离的。
针对图3所示的场景，由于终端的签约NSSAI为{S-NSSAI1、S-NSSAI2、S-NSSAI3、S-NSSAI4}，且终端当前位于AMF set 1的服务范围，终端注册入网时携带的requested NSSAI为{S-NSSAI1、S-NSSAI2、S-NSSAI3、S-NSSAI4}，且S-NSSAI3标识的切片3为PLMN不支持的网络切片，S-NSSAI4标识的切片4为终端的当前注册区域不支持的网络切片。则核心网网元(如NSSF或AMF)发送给终端的信息如下：
Allowed NSSAI：{S-NSSAI1、S-NSSAI2}；
rejected NSSAI：{S-NSSAI3:1、S-NSSAI4:2}。
其中，allowed NSSAI包括核心网侧允许接入的网络切片的标识信息，即核心网侧允许终端接入切片1和切片2。
rejected NSSAI包括核心网侧拒绝接入的网络切片的标识信息，即核心网侧拒绝终端接入切片3和切片4。且拒绝终端接入切片3的原因值为1，拒绝终端接入切片4 的原因值为2。其中，原因值1表示：PLMN不支持，原因值2表示：终端的当前注册区域不支持。
进一步地，核心网网元还可以向终端发送隔离规则(或称为共存规则)：S-NSSAI1、S-NSSAI2、S-NSSAI3与S-NSSAI4相互隔离(或称为不共存)。
当然，该共存规则也可以是预配置在终端上的，本申请对此不作限定。例如，如果共存规则预配置在终端上，那么终端根据该共存规则可以获知：NSSAI1、S-NSSAI2、S-NSSAI3与S-NSSAI4相互隔离(或称为不共存)。那么，终端不会同时请求NSSAI1、S-NSSAI2、S-NSSAI3与S-NSSAI4。基于图3的场景，还有一种可能的实现方式是，终端的签约NSSAI为{S-NSSAI1、S-NSSAI2、S-NSSAI3、S-NSSAI4}且终端当前位于AMF set 1的服务范围，终端注册入网时携带的requested NSSAI为{S-NSSAI1、S-NSSAI2、S-NSSAI3}，则核心网网元(如NSSF或AMF)发送给终端的信息如下：
rejected NSSAI：{S-NSSAI3:1}。
rejected NSSAI包括核心网侧拒绝接入的网络切片的标识信息，即核心网侧拒绝终端接入切片3。原因值1表示：PLMN不支持。
上述只是为了方便说明给出的具体实现方式。当然，在实际应用中，并不限定于上述实现方式，也可以通过其它方式实现。
参考图4，为本申请提供的第二种应用场景示意图。该应用场景与图3所示的应用场景的主要区别在于：PLMN不支持的切片3归属于AMF set 2。因此，该应用场景下，切片1、切片2与切片4相互隔离。即终端在使用切片1或切片2时，不能使用切片4，当终端在使用切片4时，不能使用切片1或切片2。
当切片3更新为PLMN支持时，则切片1、切片2与切片3、切片4相互隔离。即终端在使用切片1或切片2时，不能使用切片3或切片4；当终端在使用切片3或切片4时，不能使用切片1或切片2。
针对图4所示的场景，由于终端的签约NSSAI为{S-NSSAI1、S-NSSAI2、S-NSSAI3、S-NSSAI4}且终端当前位于AMF set 1的服务范围，终端注册入网时携带的requested NSSAI为{S-NSSAI1、S-NSSAI2、S-NSSAI3、S-NSSAI4}，且S-NSSAI3标识的切片3为PLMN不支持的网络切片，S-NSSAI4标识的切片4为终端的当前注册区域不支持的网络切片。则核心网网元(如NSSF或AMF)发送给终端的信息如下：
allowed NSSAI：{S-NSSAI1、S-NSSAI2}；
rejected NSSAI：{S-NSSAI3:1、S-NSSAI4:2}。
其中，allowed NSSAI包括核心网侧允许接入的网络切片的标识信息，即核心网侧允许终端接入切片1和切片2。
rejected NSSAI包括核心网侧拒绝接入的网络切片的标识信息，即核心网侧拒绝终端接入切片3和切片4。且拒绝终端接入切片3的原因值为1，拒绝终端接入切片4的原因值为2。其中，原因值1表示：PLMN不支持，原因值2表示：终端的当前注册区域不支持。
进一步地，核心网网元还可以向终端发送隔离规则(或称为共存规则)：S-NSSAI1、S-NSSAI2与S-NSSAI3、S-NSSAI4相互隔离(或称为不共存)。
上述只是为了方便说明，给出了一种具体实现方式。当然，在实际应用中，并不限定于上述实现方式，也可以通过其它方式实现。
针对图3和图4的应用场景，当PLMN不支持的网络切片(如图3的切片3、图4的切片3)更新为PLMN支持时，或者，当终端的当前注册区域不支持的网络切片(如图3的切片4、图4的切片4)更新为可用(例如由于终端的移动导致终端当前所在的新的注册区域支持使用切片4)时，核心网侧需要如何通知终端，以及通知哪些终端，是本发明所要解决的。
为解决上述不同场景的不同问题，本申请提供多种切片信息更新方法，下面分别详细说明。
如图5所示，为本申请提供的一种切片信息更新方法。例如，该方法可用于解决当如图3所示的PLMN不支持的切片3更新为PLMN支持时，核心网侧如何通知终端，以及通知哪些终端的问题。
如图5所示，在步骤501之前，终端发起注册流程，核心网侧返回allowed NSSAI和rejected NSSAI，其中，rejected NSSAI包括切片(例如，图3中的切片3)的标识信息(例如，S-NSSAI3)以及拒绝的原因值，该拒绝的原因值指示该切片为PLMN不支持的网络切片。
其中，终端当前所注册的AMF(即为终端提供服务的AMF)为AMF set(例如，图3中的AMF set 1)中的某个AMF。终端上存储的信息包括：allowed NSSAI，rejected NSSAI(包括S-NSSAI3)及拒绝原因值。为终端提供服务的AMF上存储的信息包括：终端的requested NSSAI，终端的签约的NSSAI。
这里，需要说明的是，针对图3所示的示例，核心网侧返回的rejected NSSAI实际上还可以包括切片4的标识信息(例如，S-NSSAI4)以及拒绝的原因值，该拒绝的原因值指示该切片为终端当前注册区域不支持该网络切片。为方便说明，图5所示的实施例中，只针对rejected NSSAI中的S-NSSAI3所指示的切片3更新为PLMN可用时进行说明。对于rejected NSSAI中的S-NSSAI4所指示的切片4更新为终端当前注册区域可用的具体实施方法，可参考后续图8所示的实施例的相关介绍。
在网络中，有一个或多个如上所述的终端。因此，后续若PLMN不支持的切片更新为PLMN支持时，应该通知这些曾请求过该网络切片但被拒绝的终端。
如图5所示的切片信息更新方法包括以下步骤：
步骤501，NSSF确定PLMN支持网络切片。
例如，NSSF可从网络管理系统(operation，administration and maintenance，OAM)获知PLMN原先不支持的网络切片，更新为PLMN支持。例如，NSSF从网络管理系统获知图3的切片3由PLMN不支持更新为支持。一种可能的实现方式是，运营商在某一个时刻部署了切片3对应的网络资源，例如，该网络资源可以包括切片3对应的SMF网元、UPF网元等等。网络管理系统向NSSF发送通知消息，通知消息中包括切片3的标识信息以及指示信息：切片3由PLMN不支持更新为PLMN支持。从而，NSSF从网络管理系统获知切片3由PLMN不支持更新为PLMN支持。
步骤502，NSSF向AMF发送通知消息，AMF接收来自NSSF的通知消息。
该步骤中，NSSF需要向特定的AMF发送通知消息，通知消息包括上述步骤501中确定的网络切片的标识信息，通知消息用于指示PLMN支持网络切片。其中，PLMN曾不支持网络切片。例如，通知消息包括S-NSSAI3，用于指示PLMN当前支持切片3。
其中，可根据下列任一方法确定需要发送通知消息的AMF，即确定出需要向哪些 AMF发送通知消息：
方法一，NSSF根据PLMN中的AMF支持的切片类型，确定支持上述网络切片的AMF为需要发送通知消息的AMF。
例如，参考图3，则使用该方法，由于AMF set 1中的AMF均支持该切片3，因此，NSSF确定需要发送通知消息的AMF包括AMF set 1中的AMF，即NSSF确定需要向AMF set 1中的AMF(例如，所有AMF)发送通知消息。当然，作为一种实现方式，也可以确定需要发送通知消息的AMF包括AMF set 1中的部分AMF。
当然，如果还有其它AMF支持的切片类型包括该切片3，则NSSF确定的发送通知消息的AMF还包括这些AMF。
方法二，NSSF确定曾向NSSF订阅上述网络切片的AMF为需要发送通知消息的AMF。
其中，曾向NSSF订阅上述网络切片的AMF指的是，AMF向NSSF订阅：当PLMN支持该网络切片时，NSSF通知该AMF。该网络切片即为上述PLMN曾不支持，但目前已更新为支持的网络切片。例如，图3的切片3。
在一种可能的实现方式中，当为终端提供服务的AMF在终端的注册流程中，确定核心网网络拒绝终端对于某个PLMN不支持的网络切片的请求时，则该AMF向NSSF订阅：当PLMN支持该网络切片时，NSSF通知该AMF。例如，为终端提供服务的AMF可以是步骤501之前向NSSF订阅。例如，为终端提供服务的AMF向NSSF发送订阅请求消息，订阅请求消息包括AMF的标识和网络切片的标识信息，该网络切片即为核心网网络拒绝该终端请求使用的网络切片。或者，为终端提供服务的AMF通过向NSSF发送AMF的标识信息和网络切片的标识信息，来调用订阅服务：当PLMN支持该网络切片时，NSSF通知该AMF。当NSSF确定PLMN不支持的网络切片更新为支持时，则确定曾向该NSSF发送订阅请求消息或调用订阅服务的AMF为需要发送通知消息的AMF。
通过上述方法一或方法二，NSSF可确定需要发送通知消息的AMF。例如，若通过方法一，则确定的需要发送通知消息的AMF包括：支持上述网络切片的AMF。若通过方法二，则确定的需要发送通知消息的AMF包括：曾向NSSF订阅该网络切片的状态的AMF。
步骤503，AMF通知终端PLMN支持网络切片。
该步骤503中的AMF，即为上述步骤502中接收到通知消息的AMF。
AMF需要通知的终端包括曾请求上述网络切片失败且签约了上述网络切片的终端。例如，AMF可以根据AMF存储的终端的上下文，确定需要通知的终端。
例如，若某个终端曾在requested NSSAI中携带上述网络切片的标识信息，且该终端的签约的NSSAI中包括该网络切片的标识信息，并且，终端在请求使用该网络切片时，PLMN不支持，因而核心网网络拒绝了终端对于该网络切片的请求。因此，当该网络切片由PLMN不支持更新为PLMN支持时，该为终端提供服务的AMF需要通知该终端PLMN支持网络切片。
作为一种具体的实现方式，AMF可以通过下述方式通知终端：
AMF将网络切片的标识信息加入终端的允许接入的网络切片集合，即allowed NSSAI，然后向终端发送更新的allowed NSSAI。
例如，针对图3所示的示例。AMF之前发送给终端的allowed NSSAI为{S-NSSAI1、S-NSSAI 2}，发送给终端的rejected NSSAI包括S-NSSAI3。则当AMF需要通知该终端S-NSSAI3所标识的切片3已更新为可用时，可以生成更新的allowed NSSAI，包括{S-NSSAI1、S-NSSAI 2、S-NSSAI 3}，然后向终端发送更新的allowed NSSAI。例如可以将该更新的allowed NSSAI携带于终端的配置更新消息(configuration update message)中发送给终端，终端在接收到该配置更新消息后，从中获取到更新的allowed NSSAI，从而可以获知切片3已经由PLMN不支持更新为PLMN支持，因而后续可以使用该切片3发起业务请求流程。
作为一种实现方式，AMF可以立即将更新的allowed NSSAI发送给终端。例如，AMF根据本地的配置信息，在确定了更新的allowed NSSAI之后，即可将更新的allowed NSSAI发送给相应的终端。可选地，AMF在向终端发送更新的allowed NSSAI的同时，还向终端发送指示信息，该指示信息用于指示PLMN支持上述网络切片。其中，该指示信息可以是由AMF生成的，也可以是由NSSF生成并通过上述步骤502的通知消息发送给AMF的。
作为另一种实现方式，AMF也可以是不立即将更新的allowed NSSAI发送给终端。例如，AMF根据本地的配置信息，先存储该更新的allowed NSSAI，然后等待该终端主动发起注册更新流程，并在注册更新流程中将更新的allowed NSSAI发送给该终端。
上述实施例，当NSSF确定PLMN曾不支持的网络切片更新为支持时，则先确定AMF，然后向确定的AMF发送通知消息，该通知消息用于指示PLMN支持该网络切片，然后由接收到通知消息的AMF通知注册在该AMF且曾经请求过该网络切片但被拒绝的终端：PLMN当前支持该网络切片。从而实现了当PLMN不支持的网络切片更新为PLMN支持时，通过相应的AMF通知到相应的终端，进而终端在有该网络切片对应的业务的需求时，可以使用该网络切片，有助于提升终端的业务能力。
如图6所示，为本申请提供的另一种切片信息更新方法。例如，该方法可用于解决当如图3所示的PLMN不支持的切片3更新为PLMN支持时，核心网侧如何通知终端，以及通知哪些终端的问题。
如图6所示，在步骤601之前，终端发起注册流程，核心网侧返回allowed NSSAI和rejected NSSAI，其中，rejected NSSAI包括切片(例如，图3中的切片3)的标识信息(例如，S-NSSAI3)以及拒绝的原因值，该拒绝的原因值指示该切片为PLMN不支持的网络切片。
其中，终端当前所注册的AMF(即为终端提供服务的AMF)为AMF set(例如，图3中的AMF set1)中的某个AMF。终端上存储的信息包括：allowed NSSAI，rejected NSSAI(包括S-NSSAI3)及拒绝原因值。为终端提供服务的AMF上存储的信息包括：终端的requested NSSAI，终端的签约的NSSAI。
这里，需要说明的是，针对图3所示的示例，核心网侧返回的rejected NSSAI实际上还可以包括切片4的标识信息(例如，S-NSSAI4)以及拒绝的原因值，该拒绝的原因值指示该切片为终端当前注册区域不支持该网络切片。为方便说明，图6所示的实施例中，只针对rejected NSSAI中的S-NSSAI3所指示的切片3更新为PLMN可用时进行说明。对于rejected NSSAI中的S-NSSAI4所指示的切片4更新为终端当前注册 区域可用的具体实施方法，可参考后续图8所示的实施例的相关介绍。
在网络中，有一个或多个如上所述的终端。因此，后续若PLMN不支持的切片更新为PLMN支持时，应该通知这些曾请求过该网络切片但被拒绝的终端。
如图6所示的切片信息更新方法包括以下步骤：
步骤601，NSSF确定PLMN支持网络切片。
该步骤601的具体实现方式，与步骤501相同，可参考前述描述。
步骤602，NSSF向PCF发送通知消息，PCF接收来自NSSF的通知消息。
该步骤中，NSSF需要向特定的PCF发送通知消息，通知消息包括上述步骤601中确定的网络切片的标识信息，通知消息用于指示PLMN支持网络切片。其中，PLMN曾不支持网络切片。例如，通知消息包括S-NSSAI3，用于指示PLMN支持切片3。
作为一种实现方式，可根据下述方式确定需要发送通知消息的PCF：NSSF确定曾向NSSF订阅上述网络切片的PCF为需要发送通知消息的PCF，即确定出需要向哪些PCF发送通知消息。
若采用该实现方式确定发送通知消息的PCF，则在上述步骤601之前，还包括以下步骤：
步骤A，AMF向PCF发送通知消息，PCF接收来自AMF的通知消息。
在一种可能的实现方式中，当为终端提供服务的AMF在终端的注册流程中，确定核心网网络拒绝终端对于某个PLMN不支持的网络切片的请求时，则该AMF向该AMF归属的PCF发送通知消息，该通知消息用于触发PCF向NSSF订阅该网络切片的状态。通知消息包括终端的标识信息，AMF的标识信息和该网络切片的标识信息。然后PCF存储终端的标识信息，AMF的标识信息和该网络切片的标识信息的关联关系。
步骤B，PCF向NSSF订阅：当PLMN支持该网络切片时，NSSF通知该PCF。
作为一种实现方式，PCF可以向NSSF发送订阅请求消息，订阅请求消息包括PCF的标识和网络切片的标识信息，该网络切片即为核心网网络拒绝该终端请求使用的网络切片。或者，PCF通过向NSSF发送PCF的标识信息和网络切片的标识信息，来调用订阅服务：当PLMN支持该网络切片时，NSSF通知该PCF。当NSSF确定PLMN不支持的网络切片更新为支持时，则确定曾向该NSSF发送订阅请求消息或调用订阅服务的PCF为需要发送通知消息的PCF。
步骤603，PCF通知终端PLMN支持网络切片。
该步骤603中的PCF，即为上述步骤602中接收到来自NSSF的通知消息的PCF。
PCF需要通知的终端包括曾请求上述网络切片失败且签约了上述网络切片的终端。
作为一种实现方式，PCF可以通过AMF向终端发送指示信息，指示信息用于指示PLMN支持网络切片。即步骤603可替换为下述步骤603a-步骤603b：
步骤603a，PCF向AMF发送更新消息，AMF接收来自PCF的更新消息。
更新消息包括指示信息和终端的标识信息，指示信息用于指示PLMN支持网络切片。该PLMN曾不支持该网络切片。
PCF先根据PCF存储的终端的上下文，确定需要通知的终端及该终端注册的AMF。例如，在执行上述步骤A-步骤B的示例中，PCF在接收到AMF的通知消息时，通知消息中包括终端的标识信息，AMF的标识信息和该网络切片的标识信息，则PCF可 以存储终端的标识信息，AMF的标识信息和该网络切片的标识信息之间的关联关系。因而PCF可根据存储的该关联关系，确定步骤603a的更新消息中需要包括的终端的标识信息，以及确定该步骤603a需要向哪些AMF发送更新消息。
例如，上述在多次执行步骤A-步骤B之后，PCF存储了如表1所示的信息：
终端的标识信息 AMF的标识信息 网络切片的标识信息
终端1 AMF1 S-NSSAI3
终端2 AMF1 S-NSSAI3
终端3 AMF2 S-NSSAI3
表1
表1中，终端1和终端2注册在AMF1，终端3注册在AMF2，且AMF1和AMF2均为图3所示的AMF set1中的AMF。表1中的终端1-终端3，为PCF记录的曾请求过S-NSSAI3所标识的切片3且被拒绝的终端。
例如，上述步骤A-步骤B被执行过三次。假设AMF1和AMF2都归属PCF1管理，则：
第一次：
步骤A，AMF1向PCF1发送通知消息，通知消息包括：(终端1，AMF1，S-NSSAI3)。
步骤B，PCF向NSSF订阅：当PLMN支持该S-NSSAI3所标识的切片3时，NSSF通知PCF1。
其中，PCF1在向NSSF订阅的时候，还将PCF1的标识信息和S-NSSAI3发送至NSSF。
第二次：
步骤A，AMF1向PCF1发送通知消息，通知消息包括：(终端2，AMF1，S-NSSAI3)。
步骤B，PCF向NSSF订阅：当PLMN支持该S-NSSAI3所标识的切片3时，NSSF通知PCF1。
其中，PCF1在向NSSF订阅的时候，还将PCF1的标识信息和S-NSSAI3发送至NSSF。
第三次：
步骤A，AMF2向PCF1发送通知消息，通知消息包括：(终端3，AMF2，S-NSSAI3)。
步骤B，PCF向NSSF订阅：当PLMN支持该S-NSSAI3所标识的切片3时，NSSF通知PCF1。
其中，PCF1在向NSSF订阅的时候，还将PCF1的标识信息和S-NSSAI3发送至NSSF。
当然，由于上述三次执行的操作的步骤B都是相同的，因此在具体实现中，还可以是只在第一次时执行步骤B，第二次和第三次时不执行步骤B。
步骤603b，AMF通知终端PLMN支持网络切片，终端为曾请求网络切片失败且签约了网络切片的终端。
该AMF即为上述步骤603a中接收到来自PCF的更新消息的AMF，该终端即为上述步骤603a的更新消息中所携带的终端的标识信息所指示的终端。
仍以上述表1为例，则该步骤603b需要执行三次：
第一次：AMF1通知终端1：PLMN支持S-NSSAI3所标识的切片3。
第二次：AMF1通知终端2：PLMN支持S-NSSAI3所标识的切片3。
第三次：AMF2通知终端3：PLMN支持S-NSSAI3所标识的切片3。
作为一种具体的实现方式，AMF可以通过下述方式通知终端，即上述第一次、第二次、第三次的执行，均可以按照下述方式实现：
AMF将网络切片的标识信息加入终端的允许接入的网络切片集合，即allowed NSSAI，然后向终端发送更新的allowed NSSAI。该实现方式的具体实现细节，可参考前述图5所示的实施例中的步骤503中的相关描述，这里不再赘述。
上述实施例，当NSSF确定PLMN曾不支持的网络切片更新为支持时，则先确定PCF，然后向确定的PCF发送通知消息，该通知消息用于指示PLMN支持该网络切片，然后由接收到通知消息的PCF通知曾经请求过该网络切片但被拒绝的终端：PLMN当前支持该网络切片。从而实现了当PLMN不支持的网络切片更新为PLMN支持时，通过相应的PCF通知到相应的终端，进而终端在有该网络切片对应的业务的需求时，可以使用该网络切片，有助于提升终端的业务能力。
如图7所示，为本申请提供的另一种切片信息更新方法。例如，该方法可用于解决当如图4所示的PLMN不支持的切片3更新为PLMN支持时，核心网侧如何通知终端，以及通知哪些终端的问题。
在图4所示的场景下，隔离规则(或称为共存规则)为：切片1、切片2与切片3、切片4之间隔离，或称为不共存。或者可以理解为，切片1、切片2归属的AMF(即AMF set1中的AMF)与切片3、切片4归属的AMF(即AMF set2中的AMF)之间不共存。该共存规则可以是终端在注册到网络的时候，网络将共存规则返回给终端，或者是在终端上配置了共存规则。
如图7所示，在步骤701之前，终端发起注册流程，核心网侧返回allowed NSSAI和rejected NSSAI，其中，rejected NSSAI包括切片(例如切片3)的标识信息(例如，S-NSSAI3)以及拒绝的原因值，该拒绝的原因值指示该切片为PLMN不支持的网络切片。可选地，还将共存规则发送给终端，其中共存规则为：S-NSSAI1、S-NSSAI2与S-NSSAI3、S-NSSAI4之间不共存(即切片1、切片2与切片3、切片4之间不共存)。
其中，终端当前所注册的AMF(即为终端提供服务的AMF)为AMF set(例如，图4中的AMF set1)中的某个AMF。终端上存储的信息包括：allowed NSSAI，rejected NSSAI(包括S-NSSAI3)及拒绝原因值，共存规则。为终端提供服务的AMF上存储的信息包括：终端的requested NSSAI，终端的签约的NSSAI。
这里，需要说明的是，针对图4所示的示例，核心网侧返回的rejected NSSAI实际上还可以包括切片4的标识信息(例如，S-NSSAI4)以及拒绝的原因值，该拒绝的原因值指示该切片为终端当前注册区域不支持该网络切片。为方便说明，图7所示的实施例中，只针对rejected NSSAI中的S-NSSAI3所指示的切片3更新为PLMN可用时进行说明。对于rejected NSSAI中的S-NSSAI4所指示的切片4更新为终端当前注册区域可用的具体实施方法，可参考后续图8所示的实施例的相关介绍。
在网络中，有一个或多个如上所述的终端。因此，后续若PLMN不支持的切片更新为PLMN支持时，应该通知这些曾请求过该网络切片但被拒绝的终端。
如图7所示的切片信息更新方法包括以下步骤：
步骤701，NSSF确定PLMN支持网络切片。
该步骤701的具体实现方式，与步骤601相同，可参考前述描述。
步骤702，NSSF向PCF发送通知消息，PCF接收来自NSSF的通知消息。
该步骤702的具体实现方式，与步骤602相同，可参考前述描述。
步骤703，PCF向AMF发送更新消息，AMF接收来自PCF的更新消息。
该更新消息例如可以是策略更新消息。更新消息包括指示信息和终端的标识信息，指示信息用于指示PLMN支持网络切片。PLMN曾不支持该网络切片。
该步骤703的具体实现方式，与上述步骤603a的实现方式相同，可参考前述描述。
步骤704，AMF向终端发送NAS消息，终端接收来自AMF的NAS消息。
该终端即为上述步骤703的更新消息中所携带的终端的标识信息所指示的终端。
NAS消息包括网络切片的标识信息，该网络切片为由PLMN曾不支持更新为PLMN支持的网络切片。可选地，NAS消息还包括指示信息，指示信息用于指示该网络切片可用，或者理解为，指示信息用于指示网络切片已更新为PLMN支持。
若仍以上述表1为例，则该步骤703需要执行三次：
第一次：AMF1通知终端1：PLMN支持S-NSSAI3所标识的切片3。
第二次：AMF1通知终端2：PLMN支持S-NSSAI3所标识的切片3。
第三次：AMF2通知终端3：PLMN支持S-NSSAI3所标识的切片3。
例如，AMF通过下述方式通知终端，即上述第一次、第二次、第三次的执行，均可以按照下述方式实现：AMF向终端发送NAS消息，NAS消息包括指示信息，指示信息用于指示PLMN支持S-NSSAI3所标识的切片3。
该步骤704与上述步骤603b的主要区别在于：为终端提供服务的AMF无需向终端发送更新的allowed NSSAI，而只需要通知终端网络切片已更新为PLMN支持即可，这是因为为终端提供服务的AMF与该网络切片归属的AMF之间相互隔离(即上述AMF1和AMF2，与切片3所归属的AMF之间相互隔离)，因而终端服务的AMF不具备支持该网络切片的能力。以表1的示例为例，由于AMF1和AMF2均属于AMF set1，因而只支持切片1和切片2，而在步骤703中，AMF1需要通知终端1和终端2：S-NSSAI3所标识的切片3已更新为PLMN支持，由于AMF1不支持切片3，因而AMF1无法向终端1和终端2发送更新的allowed NSSAI：{S-NSSAI1、S-NSSAI2、S-NSSAI3}，而只能是向终端1和终端2发送一个指示信息，指示S-NSSAI3所标识的切片3已更新为PLMN支持，因而终端1和终端2存储的信息为：
allowed NSSAI：{S-NSSAI1、S-NSSAI2}；
S-NSSAI3所标识的切片3可用。
同样地，AMF2也需要向终端3发送指示信息，因而终端3存储的信息则为：
allowed NSSAI：{S-NSSAI1、S-NSSAI2}；
S-NSSAI3所标识的切片3可用。
上述实施例，当NSSF确定PLMN曾不支持的网络切片更新为支持时，则先确定PCF，然后向确定的PCF发送通知消息，用于指示PLMN支持该网络切片，然后由接收到通知消息的PCF向AMF发送更新消息，更新消息中包括终端的标识信息和指示信息，然后由AMF向通知消息所指示的终端发送指示信息，实现通知终端网络切片 已更新为PLMN支持，进而终端在有该网络切片对应的业务的需求时，可以使用该网络切片，有助于提升终端的业务能力。
如图8所示，为本申请提供的另一种切片信息更新方法。例如，该方法可用于解决当如图3所示的终端的当前注册区域不支持的切片4或如图4所示的终端的当前注册区域不支持的切片4更新为可用时，核心网侧如何通知终端，以及通知哪些终端的问题。
下面以图3所示的场景为例进行说明。
如图8所示，在步骤801之前，终端发起注册流程，核心网侧返回allowed NSSAI和rejected NSSAI，其中，rejected NSSAI包括切片(例如，图3中的切片4)的标识信息(例如，S-NSSAI4)以及拒绝的原因值，该拒绝的原因值指示该切片为终端的当前注册区域不支持的网络切片。可选地，还将共存规则发送给终端，其中共存规则为：S-NSSAI1、S-NSSAI2、S-NSSAI3与S-NSSAI4之间不共存(即切片1、切片2、切片3与切片4之间不共存)。
其中，终端当前所注册的AMF(即为终端提供服务的AMF)为AMF set(例如，图3中的AMF set1)中的某个AMF。终端上存储的信息包括：allowed NSSAI，rejected NSSAI(包括S-NSSAI4)及拒绝原因值，共存规则。为终端提供服务的AMF上存储的信息包括：终端的requested NSSAI，终端的签约的NSSAI。
这里，需要说明的是，针对图3或图4所示的示例，核心网侧返回的rejected NSSAI实际上还可以包括切片3的标识信息(例如，S-NSSAI3)以及拒绝的原因值，该拒绝的原因值指示该切片为PLMN不支持的网络切片。为方便说明，图8所示的实施例中，只针对rejected NSSAI中的S-NSSAI4所指示的切片4更新为可用时进行说明。对于rejected NSSAI中的S-NSSAI3所指示的切片3更新为PLMN支持的具体实施方法，可参考后续图5-图7所示的实施例的相关介绍。
在网络中，有一个或多个如上所述的终端。因此，后续若终端当前注册区域不支持的切片更新为可用，应该通知这些曾请求过该网络切片但被拒绝的终端。
如图8所示的切片信息更新方法包括以下步骤：
步骤801，AMF向PCF发送终端的标识信息和网络切片的标识信息，PCF接收来自AMF的终端的标识信息和网络切片的标识信息。
在具体实现中，当为终端提供服务的AMF在终端的注册流程中，确定核心网网络拒绝终端对于某个终端当前注册区域不支持的网络切片的请求时，则该AMF向该AMF归属的PCF发送通知消息，通知消息包括终端的标识信息和该网络切片的标识信息。然后PCF存储终端的标识信息和该网络切片的标识信息的关联关系。
作为示例，假设终端1当前的注册区域包括AMF1，但不包括AMF2。该AMF1为AMF set1中的AMF，则AMF1支持的切片包括切片1、切片2、切片3(假设切片3已更新为PLMN支持)。该AMF2为AMF set2中的AMF，则该AMF2支持的切片包括切片4。
由于终端1当前所在的注册区域不包括AMF2，因此终端1当前不能使用切片4，或者理解为，切片4为终端1当前的注册区域不支持的切片。
因此，AMF1可在终端1的注册流程中，确定切片4为终端1的当前注册区域不 支持的切片，则AMF1向PCF发送终端1的标识信息和S-NSSAI4，然后PCF存储终端1的标识信息和S-NSSAI4的关联关系。
步骤802，PCF从NSSF获取网络切片对应的服务区域。
作为一种具体的实现方式，PCF可以向NSSF发送请求消息，用于请求网络切片对应的服务区域。其中，该服务区域可以是由一个或多个小区构成的小区列表。
仍以上面的示例进行说明，则PCF向NSSF发送请求消息，请求消息包括S-NSSAI4，然后NSSF向PCF返回S-NSSAI4对应的服务区域。
步骤803，PCF获知终端移动至服务区域。
作为一种实现方式，PCF获知终端移动至服务区域的方式可以是：
PCF向AMF订阅：当终端的位置发生更新时，AMF向PCF发送终端更新后的位置。例如，PCF可以向AMF发送订阅请求消息，订阅请求消息中携带终端的标识，该订阅请求消息用于向AMF订阅该终端的位置。或者，PCF通过向AMF发送终端的标识，来调用订阅服务：当终端的位置发生更新时，AMF向PCF发送终端更新后的位置。
当终端发生移动并发起注册更新流程，则在注册更新流程中的注册请求消息中可以携带终端当前的位置信息，AMF可以获取到终端当前的位置信息。由于AMF上存储的有终端上一次注册更新流程中携带的位置信息，因此，若终端当前的位置信息指示的终端的位置与上一次位置信息所指示的终端的位置不同，则该AMF将终端的最新的位置上报给PCF。
然后，PCF根据获取到的终端的当前位置，和网络切片对应的切片的服务区域，判断终端的当前位置是否在网络切片对应的切片的服务区域内，如果位于该服务区域内，则PCF获知终端移动至服务区域。
仍以上面的示例进行说明，若PCF确定终端1的当前位置位于S-NSSAI4对应的服务区域内，则确定终端1移动至S-NSSAI4对应的服务区域。
步骤804，PCF通知终端网络切片可用。
作为一种具体的实现方式，PCF可以通过终端所注册的AMF，向终端发送指示信息，指示信息用于指示网络切片可用。例如，PCF向该终端所注册的AMF发送更新消息，更新消息携带终端的标识信息和指示信息，可选地，更新消息中还携带该网络切片的标识信息，该网络切片为由终端不可用更新为终端当前可用的网络切片，其中，指示信息用于指示网络切片可用。然后AMF向终端发送NAS消息，NAS消息中包括上述指示信息，如果PCF向该终端所注册的AMF发送更新消息中携带了该网络切片的标识信息，AMF将该网络切片的标识信息也包含在NAS消息中，一并发送至终端。其中，PCF向AMF发送更新消息的具体实现方式与前述步骤703相同，可参考前述描述，AMF向终端发送NAS消息的具体实现方式与前述步骤704相同，可参考前述描述。
仍以上面的示例进行说明，则PCF在确定终端1移动至S-NSSAI4对应的服务区域后，向AMF1发送更新消息，更新消息包括终端1的标识信息和指示信息，指示信息用于指示S-NSSAI4所标识的切片4当前可用。然后AMF1向终端1发送NAS消息，NAS消息包括S-NSSAI4。可选地，NAS消息还包括该指示信息。当终端1获取到该NAS消息后，即可确定终端在当前位置可以使用切片4，因而后续可以使用该切片4 发起业务流程。例如，先重新注册至AMF2，然后使用切片4发起业务流程。
上述方法，当终端移动至网络切片对应的服务区域，则PCF可以通知该终端：该网络切片当前可用，其中，该网络切片为终端曾请求过但被拒绝，且移动前所在的注册区域不支持的网络切片。实现了当终端注册区域不支持的网络切片更新为可用时，可以及时地通知到相应终端，进而终端在有该网络切片对应的业务的需求时，可以使用该网络切片，有助于提升终端的业务能力。
需要说明的是，上述图5-图8所示的实施例，既可以作为单独的实施例实施，也可以是相互结合实施。例如，图5-图7所示的实施例，可以分别与实施例8相结合实施。再比如，图5-图6所示的实施例可以分别与图7所示的实施例相结合实施。再比如，图5、图7、图8所示的实施例相结合实施。再比如，图6、图7、图8所示的实施例相结合实施。本申请对于各实施例的具体结合方式不做限定，可根据实际需求而结合。
需要说明的是，上述实施例中的通知消息、更新消息、NAS消息、订阅请求消息、配置更新消息等仅是一个名字，名字对消息本身不构成限定。在5G网络以及未来其它的网络中，通知消息、更新消息、NAS消息、订阅请求消息、配置更新消息也可以是其他的名字，本申请实施例对此不作具体限定。
因此，本发明公开了一种切片信息更新方法，包括：
通信网元接收来自网络切片选择网元的通知消息，所述通知消息包括网络切片的标识信息，所述通知消息用于指示公共陆地移动网络PLMN支持所述网络切片；
所述通信网元通知终端所述PLMN支持所述网络切片，所述终端为曾请求所述网络切片失败且签约了所述网络切片的终端。
其中，通信网元可以是移动性管理网元或策略控制网元。
作为一种实现方式，所述通信网元根据终端上下文，确定所述终端。
在一种可能的实现方式中，若所述通信网元为移动性管理网元；则该方法还包括：所述移动性管理网元将所述网络切片的标识信息加入所述终端的允许接入的网络切片集合；
所述通信网元通知终端所述PLMN支持所述网络切片，包括：所述移动性管理网元向所述终端发送所述更新的允许接入的网络切片集合。可选地，所述通信网元通知终端所述PLMN支持所述网络切片，还包括：所述移动性管理网元向所述终端发送指示信息，所述指示信息用于指示所述PLMN支持所述网络切片。
在另一种可能的实现方式中，若所述通信网元为策略控制网元；则所述方法还包括：所述策略控制网元确定所述终端注册的移动性管理网元；
所述通信网元通知终端所述PLMN支持所述网络切片，包括：所述策略控制网元通过所述移动性管理网元，向所述终端发送指示信息，所述指示信息用于指示所述PLMN支持所述网络切片。
上述切片信息更新方法中，例如，若通信网元为移动性管理网元，则移动性管理网元的操作可参考图5中AMF的操作及上述相关文字说明，这里不再赘述。例如，若通信网元为策略控制网元，则策略控制网元的操作可参考图6中PCF的操作及上述相关文字说明，这里不再赘述。
本发明还提供一种切片信息更新方法，包括：
移动性管理网元接收来自策略控制网元的更新消息，所述更新消息包括指示信息和终端的标识信息，所述指示信息用于指示公共陆地移动网络PLMN支持网络切片；
所述移动性管理网元通知终端所述PLMN支持所述网络切片，所述终端为曾请求所述网络切片失败且签约了所述网络切片的终端。
在一种可能的实现方式中，上述方法还包括：所述移动性管理网元将所述网络切片的标识信息加入所述终端的允许接入的网络切片集合；
所述移动性管理网元通知终端所述PLMN支持所述网络切片，包括：所述移动性管理网元向所述终端发送所述更新的允许接入的网络切片集合。
在一种可能的实现方式中，所述移动性管理网元通知终端所述PLMN支持所述网络切片，还包括：所述移动性管理网元向所述终端发送指示信息，所述指示信息用于指示所述PLMN支持所述网络切片。
在一种可能的实现方式中，所述移动性管理网元通知终端所述PLMN支持所述网络切片，包括：所述移动性管理网元向所述终端发送NAS消息，所述NAS消息包括所述指示信息。
上述切片信息更新方法中，例如，移动性管理网元的操作可参考图7中AMF的操作及上述相关文字说明，这里不再赘述。
本发明还提供一种切片信息更新方法，包括：
策略控制网元接收来自移动性管理网元的终端的标识信息和网络切片的标识信息，所述网络切片为所述终端的当前注册区域不支持的网络切片；
所述策略控制网元从网络切片选择网元获取所述网络切片对应的服务区域；
若所述策略控制网元获知所述终端移动至所述服务区域，则通知所述终端所述网络切片可用。
在一种可能的实现方式中，所述策略控制网元通知所述终端所述网络切片当前可用，包括：所述策略控制网元通过所述移动性管理网元向所述终端发送指示信息，所述指示信息用于指示所述网络切片可用。
在上述切片信息更新方法中，例如，策略控制网元的操作可参考图8中PCF的操作及上述相关文字说明，这里不再赘述。
本发明还提供一种切片信息更新方法，包括：
网络切片选择网元确定公共陆地移动网络PLMN支持网络切片；
所述网络切片选择网元向通信网元发送通知消息，所述通知消息包括所述网络切片的标识信息，所述通知消息用于指示所述PLMN支持所述网络切片。可选地，所述通信网元为策略控制网元或移动性管理网元。
在一种可能的实现方式中，上述方法还包括：所述网络切片选择网元接收来自所述通信网元的订阅：当所述PLMN支持所述网络切片时，所述网络切片选择网元通知所述通信网元。
在一种可能的实现方式中，上述方法还包括：所述网络切片选择网元根据所述PLMN中的移动性管理网元支持的切片类型，确定支持所述网络切片的移动性管理网 元为所述通信网元。
上述切片信息更新方法中，例如，网络切片选择网元的操作可参考图5-图7中NSSF的操作及上述相关文字说明，这里不再赘述。
参考图9，为本申请提供的第三种应用场景示意图。网络侧包括两个AMF集合(set)，分别为AMF set 1和AMF set 2。其中，AMF set 1中的任一AMF支持的网络切片(slicing)为：{切片1、切片2、切片3}，切片1的服务区域为服务区域1，切片2的服务区域为服务区域2，切片3的服务区域为服务区域3。AMF set 2中的任一AMF支持的网络切片为：{切片4、切片5}，切片4的服务区域为服务区域4，切片4的服务区域为服务区域5。
其中，上述示例中的切片1、切片2、切片3、切片4、切片5，可以分别由S-NSSAI1、S-NSSAI2、S-NSSAI3、S-NSSAI4、S-NSSAI5标识。即S-NSSAI1为切片1的标识信息、S-NSSAI2为切片2的标识信息、S-NSSAI3为切片3的标识信息、S-NSSAI4为切片4的标识信息、S-NSSAI5为切片5的标识信息。
每个网络切片对应一个或多个SMF和一个或多个UPF。例如，如图9所示，切片1对应SMF1和UPF1，切片2对应SMF2和UPF2，切片3对应SMF3和UPF3，切片4对应SMF4和UPF4，切片5对应SMF5和UPF5。
并且，AMF Set 1中的任一AMF支持的切片与AMF Set2中的任一AMF支持的切片之间是隔离关系(或者称为互斥关系或不共存关系)，隔离关系可以理解为不能同时接入或者同时访问两个不同的切片。因此，终端只能访问切片1、切片2、切片3中的切片，或者只能访问切片4、切片5中的切片，但不能同时既访问切片1、切片2、切片3中的切片，又访问切片4、切片5中的切片。
切片的服务区域指的是该切片可以提供服务的范围，即该切片可以为处于该切片的服务范围内的终端提供服务，或者理解为处于该切片的服务区域内的终端可以使用该切片提供的服务，处于该切片的服务区域外的终端不可以使用该切片提供的服务。作为一种实现方式，服务区域可以包括一个或多个跟踪区域(Tracking Area，TA)，一个TA可以使用跟踪区域标识(Tracking Area Identity，TAI)唯一标识。因此，也可以理解为，一个切片对应一个服务区域，或者理解为一个切片对应一个或多个TA。
作为示例，图9所示的实施例中，切片1至切片5的服务区域分别包括10个TA，具体为：
切片1的服务区域包括：TA1，TA2，……，TA11；
切片2的服务区域包括：TA2，TA3，……，TA12；
切片3的服务区域包括：TA3，TA4，……，TA13；
切片4的服务区域包括：TA4，TA5，……，TA14；
切片5的服务区域包括：TA5，TA6，……，TA15。
该示例中，任意两个切片的服务区域包括重叠的TA。比如，切片1的服务区域与切片2的服务区域包括的重叠的TA为TA2，TA3，……，TA11。
进一步的，可以将任一切片在的服务区域内的任一TA内的服务状态分为“可用状态”和“限制状态”。其中，若切片在某个TA内可以为终端提供服务，则该切片在该TA内的服务状态为“可用状态”。若切片在某个TA内不可以为终端提供服务， 则该切片在该TA内的服务状态为“限制状态”。“限制状态”也可以称为“临时不可用状态”。
需要说明的是，切片在某个TA内的两种服务状态之间是可以转换的，比如从“可用状态”转为“限制状态”，或者从“限制状态”转为“可用状态”。
需要说明的是，若切片在一个TA内的服务状态为“可用状态”，则该TA也可以称为使得切片处于“可用状态”的TA，或者称为该TA为该切片可用的TA。若切片在一个TA内的服务状态为“限制状态”，则该TA也可以称为使得切片处于“限制状态”的TA，或者称为该TA为该切片不可用的TA。
一种可能的实现方式中，NSSF可以根据切片的负载确定该切片当前在某个或某些TA内的服务状态。比如，针对一个切片，若接入该切片的用户数较多，使得该切片的负载超过预设的阈值，则NSSF可以将该切片在某个或某些TA内的服务状态从“可用状态“转为“限制状态”。再比如，针对一个切片，若接入该切片的用户数较少，使得该切片的负载低于预设的阈值，则NSSF可以将该切片在某个或某些TA内的服务状态从“限制状态“转为“可用状态”。
针对图9所示的应用场景，当某个切片在某个或某些TA内的服务状态为“限制状态”时，位于该TA内的终端请求接入该切片而被拒绝，后续该切片在该TA内的服务状态从“限制状态“转为“可用状态”时，网络侧如何通知终端，则是本申请将要解决的问题。
需要说明的是，注册到网络的终端可以使用某个切片，指的是该终端的注册区域包括的任一TA满足该切片处于“可用状态”，换句话说，该终端的注册区域包括的TA集合，是使得该切片处于“可用状态”的TA构成的集合的子集。比如，若终端的注册区域为RA＝{TA4，TA5，TA6}，针对上述切片3，若切片3在TA3至TA13均处于“可用状态”，由于TA4至TA6构成的集合是TA3至TA13构成的集合的子集，因此该终端可以使用该切片3。再比如，若终端的注册区域为RA＝{TA4，TA5，TA6}，针对上述切片3，若切片3在TA5至TA13均可用，在TA3、TA4不可用，由于TA4至TA6构成的集合不是TA5至TA13构成的集合的子集，因此该终端不可以使用该切片3。
作为示例，下面给出两种不同的实现方法，分别如图10和图11所示。下面分别说明。
需要说明的是，图10和图11所示的实施例中，终端始终位于该终端的注册区域内，即终端始终未移出该终端的注册区域。对于终端移出了该注册区域后的切片信息的更新方法的具体实现过程，可以参考现有技术的相关描述。
如图10所示，为本申请提供的又一种切片信息更新方法。该方法包括以下步骤：
步骤1001，AMF向NSSF发送请求。相应地，NSSF可以接收到该请求。
该请求例如可以是Nnssf_NSSAIAvailability_Update请求，或者可以是请求消息。
该请求用于向NSSF上报该AMF支持的切片的标识信息，以及每一个切片对应的服务区域(一个服务区域可以包括一个或多个TA)。
例如，针对图9所示的AMF set 1中的各个AMF，分别向NSSF上报的信息包括：
S-NSSAI1，TAI1-TAI11；
S-NSSAI2，TAI2-TAI12；
S-NSSAI3，TAI3-TAI13。
针对图9所示的AMF set 2中的各个AMF，分别向NSSF上报的信息包括：
S-NSSAI4，TAI4-TAI14；
S-NSSAI5，TAI5-TAI15。
步骤1002，终端发起注册流程，核心网返回allowed NSSAI和rejected NSSAI。
假设终端的签约NSSAI为{S-NSSAI1、S-NSSAI2、S-NSSAI3、S-NSSAI4、S-NSSAI5}，且终端当前位于TA5。
情形一，终端不知道AMF set 1支持的切片与AMF set 2支持的切片之间是隔离的。
终端发起注册请求，携带的requested NSSAI可以包括{S-NSSAI1、S-NSSAI2、S-NSSAI3、S-NSSAI4、S-NSSAI5}，RAN根据requested NSSAI选择AMF的时候，发现S-NSSAI-1，S-NSSAI-2，S-NSSAI-3由AMF set 1服务，但是S-NSSAI-4，S-NSSAI-5由AMF set 2服务，比如，RAN优先选择AMF set 1里面的AMF作为服务AMF(serving AMF)。
进一步的，网络侧根据终端的requested NSSAI确定allowed NSSAI以及终端的注册区域RA。例如，服务AMF发送给终端的信息如下：
allowed NSSAI：{S-NSSAI1、S-NSSAI2、S-NSSAI 3}；
rejected NSSAI：{S-NSSAI4:2、S-NSSAI5:2}；
RA＝{TA4，TA5，TA6}，这里假设终端的注册区域由3个TA组成。其中，allowed NSSAI包括核心网侧允许接入的网络切片的标识信息，即核心网侧允许终端接入切片1和切片2。
rejected NSSAI包括核心网侧拒绝接入的网络切片的标识信息，即核心网侧拒绝终端接入切片4和切片5。拒绝终端接入切片4和切片5的原因值为2。其中，切片4对应的原因值2表示：切片4与allowed NSSAI中的切片隔离，切片5对应的原因值2表示：切片5与allowed NSSAI中的切片隔离。
进一步的，服务AMF在该终端的上下文中还可以存储以下信息：
RA＝{TA4，TA5，TA6}；
allowed NSSAI：{S-NSSAI1、S-NSSAI2、S-NSSAI 3}。
并且，AMF中还存储有allowed NSSAI中的每个网络切片在该网络切片的服务区域中的每个TA的服务状态。以allowed NSSAI中的S-NSSAI1标识的切片1为例，AMF记录了该切片1在TA1-TA13中的每个TA中的服务状态，比如，记录的信息为：切片1在TA1-TA7处于“可用状态”，在TA8-TA13处于“限制状态”(即临时不可用状态)。对于切片2和切片3也采用类似方法记录切片在每个TA的服务状态，不再举例说明。
进一步地，服务AMF还可以向终端发送隔离规则(或称为共存规则)：S-NSSAI1、S-NSSAI2、S-NSSAI3与S-NSSAI4、S-NSSAI5相互隔离。
情形二，终端知道AMF set 1支持的切片与AMF set 2支持的切片之间是隔离的，且AMF set 1中的切片3的服务状态为“限制状态”。
比如，终端上预先配置有隔离规则，该隔离规则指示：NSSAI1、S-NSSAI2、S-NSSAI3与S-NSSAI4、S-NSSAI5相互隔离。因而，终端不会同时请求NSSAI1、 S-NSSAI2、S-NSSAI3与S-NSSAI4、S-NSSAI5。
终端发起注册请求，比如携带的requested NSSAI包括{S-NSSAI1、S-NSSAI2、S-NSSAI3}，RAN根据requested NSSAI选择AMF的时候，发现S-NSSAI-1，S-NSSAI-2，S-NSSAI-3均由AMF set 1服务，因而RAN可以从AMF set 1中选择一个AMF作为服务AMF(serving AMF)。
进一步的，网络侧根据终端的requested NSSAI确定allowed NSSAI以及终端的注册区域(register area，RA)。例如，服务AMF发送给终端的信息如下：
allowed NSSAI：{S-NSSAI1、S-NSSAI2、S-NSSAI 3}；
RA＝{TA4，TA5，TA6}，这里假设终端的注册区域由3个TA组成。
其中，allowed NSSAI包括核心网侧允许接入的网络切片的标识信息，即核心网侧允许终端接入切片1和切片2。
进一步的，服务AMF在该终端的上下文中还可以存储以下信息：
RA＝{TA4，TA5，TA6}；
allowed NSSAI：{S-NSSAI1、S-NSSAI2、S-NSSAI 3}。
上述示例只是为了方便说明给出的具体实现方式。当然，在实际应用中，并不限定于上述实现方式，也可以通过其它方式实现。
步骤1003，NSSF确定某个或某些切片在一个或多个TA内的服务状态由“可用状态”更改为“限制状态”。
以上述步骤1002的示例为例，终端当前位于TA5，终端的注册区域RA＝{TA4，TA5，TA6}。以上述切片3为例。
在第一个示例中，在步骤1003之前，切片3在所有TA均可用，即切片3在TA3至TA13均可用。在步骤1003中，NSSF确定切片3的负载高于预设阈值，则NSSF确定该切片3在所有TA内的服务状态由“可用状态”更改为“限制状态”，因此，更改之后，切片3在所有TA均不可用，即切片3在TA3至TA13均不可用。
在第二个示例中，在步骤1003之前，切片3在所有TA均可用，即切片3在TA3至TA13均可用。在步骤1003中，NSSF确定切片3的负载高于预设阈值，则NSSF确定该切片3在部分TA内的服务状态由“可用状态”更改为“限制状态”，比如，确定切片3在TA5、TA6的服务状态由“可用状态”更改为“限制状态”，因此，更改之后，切片3在TA5、TA6不可用，在TA3、TA4、TA7至TA13可用。
在第三个示例中，在步骤1003之前，切片3在部分TA可用，比如在TA3至TA10可用，在TA11至TA13不可用。在步骤1003中，NSSF确定切片3的负载高于预设阈值，则NSSF确定该切片3在所有可用的TA(即TA3至TA10)内的服务状态由“可用状态”更改为“限制状态”，因此，更改之后，切片3在所有TA均不可用，即切片3在TA3至TA13均不可用。
在第四个示例中，在步骤1003之前，切片3在部分TA可用，比如在TA3至TA10可用，在TA11至TA13不可用。在步骤1003中，NSSF确定切片3的负载高于预设阈值，则NSSF确定该切片3在部分可用的TA内的服务状态由“可用状态”更改为“限制状态”，比如，确定切片3在TA6至TA10的服务状态由“可用状态”更改为“限制状态”，因此，更改之后，切片3在TA6至TA13不可用，在TA3至TA5可用。
在第五个示例中，在步骤1003之前，切片3在部分TA可用，比如在TA3至TA10可用，在TA11至TA13不可用。在步骤1003中，NSSF确定切片3的负载高于预设阈值，则NSSF确定该切片3在部分可用的TA内的服务状态由“可用状态”更改为“限制状态”，比如，确定切片3在TA7至TA10的服务状态由“可用状态”更改为“限制状态”，因此，更改之后，切片3在TA7至TA13不可用，在TA3至TA6可用。
步骤1004，NSSF向AMF发送通知。相应地，AMF可以接收到该通知。
该通知例如可以是Nnssf_NSSAIAvailability_Notify，或者可以是通知消息。
该通知包括切片的标识信息和至少一个TA的标识信息，这里的至少一个TA的标识信息在具体实现中可以使用一个TA列表表示，即该通知中可以包括切片的标识信息和一个TA列表，该TA列表包括至少一个TA的标识信息。
为方便说明，本申请后续以上述通知包括切片的标识信息和一个TA列表为例进行说明。
这里的切片指的是上述步骤1003中确定的在部分或全部TA的服务状态由“可用状态”更改为“限制状态”的切片，如上述步骤1003的各个示例中的切片3。这里的TA列表包括一个或多个TA，且上述切片在该TA列表中的任一TA内的状态由“可用状态”更改为“限制状态”。
比如针对上述步骤1003中的第一个示例，这里的切片指的是切片3，TA列表包括TA3至TA13。再比如针对上述步骤1003中的第二个示例，这里的切片指的是切片3，TA列表包括TA5、TA6。再比如针对上述步骤1003中的第三个示例，这里的切片指的是切片3，TA列表包括TA3至TA10。再比如针对上述步骤1003中的第四个示例，这里的切片指的是切片3，TA列表包括TA6至TA10。再比如针对上述步骤1003中的第五个示例，这里的切片指的是切片3，TA列表包括TA7至TA10。
需要说明的是，若上述步骤1002中，AMF中没有存储allowed NSSAI中的每个网络切片在该网络切片的服务区域中的每个TA的服务状态。则该步骤1004中，在通知中可以携带该切片在该切片的服务区域的每个TA内的服务状态，即针对上述步骤1003中的四个示例中的任一示例，在该步骤1004的通知消息均可以携带切片的标识信息以及该切片在该切片的每个TA内的当前的服务状态。
步骤1005，AMF根据终端的上下文中的allowed NSSAI，确定该终端不可用的切片。
比如，在上述步骤1002的情形一或情形二中，AMF在某个终端的上下文中存储的信息包括：
RA＝{TA4，TA5，TA6}；
allowed NSSAI：{S-NSSAI1、S-NSSAI2、S-NSSAI3}。
针对上述步骤1003的第一个示例，则步骤1004中的通知中携带切片3的标识S-NSSAI3以及TA3至TA13的标识。由于切片3在TA3至TA13的服务状态更改为“限制状态”，而终端的RA包括TA4，TA5和TA6，因此终端在TA4至TA6不能使用该切片3，进而终端将不能使用该切片3，即确定的该终端的allowed NSSAI中的切片3当前不可用，因而确定的终端不可用的切片包括切片3。
针对上述步骤1003的第二个示例，则步骤1004中的通知中携带切片3的标识 S-NSSAI3以及TA5、TA6的标识。由于切片3在TA5、TA6的服务状态更改为“限制状态”，而终端的RA包括TA4，TA5和TA6，因此终端在TA5、TA6不能使用该切片3，进而终端将不能使用该切片3，即确定的该终端的allowed NSSAI中的切片3当前不可用，因而确定的终端不可用的切片包括切片3。
针对上述步骤1003的第三个示例，则步骤1004中的通知中携带切片3的标识S-NSSAI3以及TA3至TA10的标识。由于切片3在TA3至TA10的服务状态更改为“限制状态”，而终端的RA包括TA4，TA5和TA6，因此终端在TA4至TA6不能使用该切片3，进而终端将不能使用该切片3，即确定的该终端的allowed NSSAI中的切片3当前不可用，因而确定的终端不可用的切片包括切片3。
针对上述步骤1003的第四个示例，则步骤1004中的通知中携带切片3的标识S-NSSAI3以及TA6至TA10的标识。由于切片3在TA6至TA10的服务状态更改为“限制状态”，而终端的RA包括TA4，TA5和TA6，因此终端在TA6不能使用该切片3，进而终端将不能使用该切片3，即确定的该终端的allowed NSSAI中的切片3当前不可用，因而确定的终端不可用的切片包括切片3。
针对上述步骤1003的第五个示例，则步骤1004中的通知中携带切片3的标识S-NSSAI3以及TA7至TA10的标识。由于切片3在TA7至TA10的服务状态更改为“限制状态”，并且切片3在TA3至TA6的服务状态为“可用状态”，而终端的RA包括TA4，TA5和TA6，因而终端仍然可以使用该切片3，因而确定allowed NSSAI中的切片3当前仍然可用。基于该示例5，若allowed NSSAI中的切片1和切片2也仍然可用，则AMF将会确定allowed NSSAI中的切片，终端均可用或均可接入。
即，只要当终端在终端的注册区域内的所有TA内(即在任意一个TA内)均可以使用某个切片时，才可以称为该终端可以使用该切片或者称为该终端能够接入该切片。换句话说，只要终端在注册区域的任意一个TA内不可以使用某个切片，则可以称为该终端不可以使用该切片。
步骤1006，AMF为终端确定新的allowed NSSAI和rejected NSSAI，以及存储该rejected NSSAI。
基于上述示例，若AMF确定终端当前不能使用切片3，且进一步确定终端当前仍然可以使用切片1和切片2，则该步骤1006中AMF为终端确定的新的allowed NSSAI为{S-NSSAI1、S-NSSAI2}，为终端确定的rejected NSSAI包括{S-NSSAI3}。并且，AMF还存储该rejected NSSAI。
步骤1007A，若终端处于连接(connected)状态,则AMF通过配置更新流程，将新的allowed NSSAI和rejected NSSAI发送给终端。
步骤1007B，若处于空闲态(idle)状态，则AMF可以等待终端再次处于连接态时(例如等待终端发起周期性注册更新流程)，AMF再将新的allowed NSSAI和rejected NSSAI发送给终端。
上述步骤1007A和步骤1007B为二选一进行执行。
步骤1008，NSSF确定某个或某些切片在一个或多个TA内的服务状态由“限制状态”更改为“可用状态”。
该步骤1008与上述步骤1003是相反过程的步骤。仍然以上述步骤1003中的示例为例。
在上述第一个示例中，在步骤1003之后，切片3在所有TA均不可用，即切片3在TA3至TA13均不可用。在步骤1008中，NSSF确定切片3的负载低于预设阈值，则NSSF确定该切片3在所有TA内的服务状态由“限制状态”更改为“可用状态”，因此，更改之后，切片3在所有TA均可用，即切片3在TA3至TA13均可用。
在上述第二个示例中，在步骤1003之后，切片3在TA5、TA6不可用，在TA3、TA4、TA7至TA13可用。在步骤1008中，NSSF确定切片3的负载低于预设阈值，则NSSF确定该切片3在部分不可用的TA内的服务状态由“限制状态”更改为“可用状态”，比如确定该切片3在TA6内的服务状态由“限制状态”更改为“可用状态”，因此，更改之后，切片3在TA3、TA4、TA6至TA13均可用，在TA5不可用。
在上述第三个示例中，在步骤1003之后，切片3在TA3至TA13均不可用。在步骤1008中，NSSF确定切片3的负载低于预设阈值，则NSSF确定该切片3在部分不可用的TA内的服务状态由“限制状态”更改为“可用状态”，比如确定该切片3在TA3至TA8内的服务状态由“限制状态”更改为“可用状态”，因此，更改之后，切片3在TA3至TA8均可用，在TA9至TA13仍然不可用。
在上述第四个示例中，在步骤1003之后，切片3在TA3至TA5均可用，在TA6至TA13均不可用。在步骤1008中，NSSF确定切片3的负载低于预设阈值，则NSSF确定该切片3在所有不可用的TA内的服务状态由“限制状态”更改为“可用状态”，即该切片3在TA6至TA13内的服务状态由“限制状态”更改为“可用状态”,因此，更改之后，切片3在所有TA均可用，即切片3在TA3至TA13均可用。
步骤1009，NSSF向AMF发送通知。相应地，AMF可以接收到该通知。
该通知例如可以是Nnssf_NSSAIAvailability_Notify，或者可以是通知消息。
该通知包括切片标识信息和至少一个TA的标识信息，这里的至少一个TA的标识信息在具体实现中可以使用一个TA列表表示，即该通知中可以包括切片的标识信息和一个TA列表，该TA列表包括至少一个TA的标识信息。
为方便说明，本申请后续以上述通知包括切片的标识信息和一个TA列表为例进行说明。
这里的切片指的是上述步骤1008中确定的在部分或全部TA的服务状态由“限制状态”更改为“可用状态”的切片，如上述步骤1008的各个示例中的切片3。这里的TA列表包括一个或多个TA，且上述切片在该TA列表中的任一TA内的状态由“限制状态”更改为“可用状态”。
比如针对上述步骤1008中的第一个示例，则步骤1009的通知中的切片指的是切片3，TA列表包括TA3至TA13。再比如针对上述步骤1008中的第二个示例，则步骤1009的通知中的切片指的是切片3，TA列表包括TA6。再比如针对上述步骤1008中的第三个示例，则步骤1009的通知中的切片指的是切片3，TA列表包括TA3至TA8。再比如针对上述步骤1008中的第四个示例，则步骤1009的通知中的切片指的是切片3，TA列表包括TA6至TA13。
步骤1010，AMF根据终端的上下文中存储的rejected NSSAI，为终端确定新的allowed NSSAI。
比如，在上述步骤1006的示例中，AMF为终端存储的rejected NSSAI包括{S-NSSAI3}，并且在上述步骤1009的通知中携带切片3以及切片3对应的TA列表， 则AMF在步骤1010中，需要判断终端当前是否可以使用该切片3，下面结合上述1008的四个示例进行说明。
比如，针对上述步骤1008的第一个示例，AMF根据存储的终端的上下文以及通过步骤1009接收到的通知，确定切片3当前在TA3至TA13处于“可用状态”，而终端的注册区域包括TA4至TA6，因此，终端可以使用该切片3。因而针对该示例，确定的新的allowed NSSAI包括{NSSAI1、NSSAI2、NSSAI3}。
再比如，针对上述步骤1008的第二个示例，AMF根据存储的终端的上下文以及通过步骤1009接收到的通知，确定切片3当前在TA3、TA4、TA6至TA13处于“可用状态”，在TA5处于“限制状态”，而终端的注册区域包括TA4至TA6，因此，终端不可以使用该切片3。因而针对该示例，则不需要为终端确定的新的allowed NSSAI。
再比如，针对上述步骤1008的第三个示例，AMF根据存储的终端的上下文以及通过步骤1009接收到的通知，确定切片3当前在TA3至TA8处于“可用状态”，在TA9至TA13处于“限制状态”，而终端的注册区域包括TA4至TA6，因此，终端可以使用该切片3。因而针对该示例，确定的新的allowed NSSAI包括{S-NSSAI1、S-NSSAI2、S-NSSAI3}。
再比如，针对上述步骤1008的第四个示例，AMF根据存储的终端的上下文以及通过步骤1009接收到的通知，确定切片3当前在TA3至TA13处于“可用状态”，而终端的注册区域包括TA4至TA6，因此，终端可以使用该切片3。因而针对该示例，确定的新的allowed NSSAI包括{S-NSSAI1、S-NSSAI2、S-NSSAI3}。
步骤1011，AMF向终端发送新的allowed NSSAI。
该步骤1011可以采用如上述步骤1007A或步骤1007B所述的方式，向终端发送新的allowed NSSAI。
可选的，若新的allowed NSSAI包括AMF存储的rejected NSSAI中的切片，则该AMF还可以删除rejected NSSAI中的切片标识。例如，针对上述切片3，S-NSSAI3包含在新的allowed NSSAI发送至终端后，则AMF可以在rejected NSSAI中删除该切片3的标识S-NSSAI3。
基于该实施例，AMF在终端的上下文中存储rejected NSSAI，当AMF从NSSF接收通知，获知该rejected NSSAI中的切片再次变为终端可用后，则AMF将该切片的标识包含在新的allowed NSSAI中发送至终端。实现了切片的重新启用，可以提升资源利用率。
如图11所示，为本申请提供的又一种切片信息更新方法。为方便说明，图11所示的实施例中采用与上述图10所示的实施例中的示例进行说明。
该方法包括以下步骤：
步骤1101-步骤1109，与图10所示的实施例的步骤1001-步骤1009类似，可参考前述描述。
需要说明的是，在步骤1106中，AMF可以不需要存储确定的rejected NSSAI。
步骤1110，终端向AMF发送注册请求消息。相应地，AMF可以接收到该注册请求消息。
该注册请求消息包括requested NSSAI。该requested NSSAI包括终端在上述步骤 1107A或步骤1107B中获取到的rejected NSSAI中的S-NSSAI。
以该图11所示的实施例的步骤1101-步骤1109所采用的示例，与上述图10所示的实施例的步骤1001-步骤1009所采用的示例相同为例，即步骤1101-步骤1109中确定切片3在该切片3的部分或全部TA内的服务状态由“限制状态”改为“可用状态”，并且AMF在步骤1007A或步骤1007B中通过rejected NSSAI通知终端，拒绝终端接入(或使用)该切片3。
在终端发起步骤1111之前，已经知晓该切片3为之前被网络拒绝的切片，则在本实施例中，终端将在再次发起请求时，在requested NSSAI中携带曾被拒绝接入的切片的标识信息，比如携带上述切片3的标识信息，即S-NSSAI 3。
作为一种具体实现方式，终端未移出注册区域，当周期性注册更新的计时器超时后，终端在注册区域内发起周期性注册请求消息，携带requested NSSAI以及注册类型(registration type)。其中，requested NSSAI包括终端在上述步骤1107A或步骤1107B中获取到的rejected NSSAI中的S-NSSAI，注册类型指示本次注册请求为周期性注册更新(Periodic Registration Update)。
步骤1111，AMF根据requested NSSAI，为终端确定新的allowed NSSAI。以上述步骤1110的requested NSSAI中携带切片3的标识，即S-NSSAI3为例，则该步骤1111中，若AMF确定终端当前可以使用该切片3，则AMF在新的allowed NSSAI携带S-NSSAI3。当然，新的allowed NSSAI中还可以携带其他可以使用的切片的标识。
步骤1112，AMF向终端发送注册接受消息，携带新的allowed NSSAI。
图11所示的实施例与图10所示的实施例的主要区别在于：图11所示实施例是由终端在注册请求消息中携带之前被拒绝的切片的标识，然后由AMF判断终端当前是否可以使用该拒绝的切片，若可以使用，则之前被拒绝的切片标识包含在新的allowed NSSAI中发送至终端。
基于该实施例，终端在注册请求消息中携带临时拒绝的切片的标识，使得后续当该切片由临时不可用变为可用时，AMF可以及时地更新终端的新的allowed NSSAI。
因此，本发明公开了一种切片信息更新方法，包括：
移动性管理网元接收来自网络切片选择网元的通知消息，通知消息包括网络切片的标识信息和至少一个跟踪区域的标识信息，该网络切片在所述至少一个跟踪区域内可用，该网络切片在所述至少一个跟踪区域内曾不可用；
移动性管理网元确定更新的允许接入的网络切片集合，该更新的允许接入的网络切片集合包括所述网络切片的标识信息，其中，终端位于终端的注册区域内，且终端能够接入该网络切片；
移动性管理网元向终端发送所述更新的允许接入的网络切片集合。
其中，终端能够接入上述网络切片，指的是该网络切片在该终端的注册区域内的任意一个跟踪区域内都可用。
在一种可能的实现方式中，移动性管理网元确定上述网络切片在终端的注册区域内可用，则确定该终端能够接入上述网络切片。
在一种可能的实现方式中，移动性管理网元接收来自网络切片选择网元的通知消息之前，还存储该终端的拒绝接入的网络切片集合，该拒绝接入的网络切片集合包括 上述网络切片的标识信息。
在一种可能的实现方式中，移动性管理网元向终端发送更新的允许接入的网络切片集合之前，还接收来自终端的注册请求消息，所述注册请求消息包括上述网络切片的标识信息。
在一种可能的实现方式中，移动性管理网元向终端发送更新的允许接入的网络切片集合，具体包括：移动性管理网元向终端发送注册接受消息，该注册接受消息包括上述更新的允许接入的网络切片集合。
上述切片信息更新方法中，移动性管理网元的操作可参考图10或图11中AMF的操作及上述相关文字说明，这里不再赘述。
本发明还公开了一种切片信息更新方法，包括：
终端接收来自移动性管理网元的终端的允许接入的网络切片集合和拒绝接入的网络切片集合，所述拒绝接入的网络切片集合包括网络切片的标识信息，该终端位于该终端的注册区域内；
终端向移动性管理网元发送注册请求消息，所述注册请求消息包括所述网络切片的标识信息；
终端接收来自移动性管理网元的更新的允许接入的网络切片的集合，该更新的允许接入的网络切片的集合包括上述网络切片的标识信息，该网络切片在该终端的注册区域内可用，该网络切片在该终端的注册区域内曾不可用。
在一种可能的实现方式中，终端接收来自移动性管理网元的更新的允许接入的网络切片的集合，具体包括：终端接收来自移动性管理网元的注册接受消息，该注册接受消息包括上述更新的允许接入的网络切片的集合。
上述切片信息更新方法中，终端的操作可参考图11中终端的操作及上述相关文字说明，这里不再赘述。
上述主要从各个网元之间交互的角度对本申请提供的方案进行了介绍。可以理解的是，上述实现各网元为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本发明能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本发明的范围。
基于相同的发明构思，如图12所示，为本申请提供的一种装置示意图，该装置可以是移动性管理网元、策略控制网元、网络切片选择网元、终端或芯片，可执行上述任一实施例的方法。
该装置1200包括至少一个处理器1201，通信线路1202，存储器1203以及至少一个通信接口1204。
处理器1201可以是一个通用中央处理器(central processing unit，CPU)，微处理器，特定应用集成电路(application-specific integrated circuit，服务器IC)，或一个或多个用于控制本申请方案程序执行的集成电路。
通信线路1202可包括一通路，在上述组件之间传送信息。
通信接口1204，使用任何收发器一类的装置，用于与其他设备或通信网络通信，如以太网，无线接入网(radio access network，RAN)，无线局域网(wireless local area networks，WLAN)等。
存储器1203可以是只读存储器(read-only memory，ROM)或可存储静态信息和指令的其他类型的静态存储设备，随机存取存储器(random access memory，RAM)或者可存储信息和指令的其他类型的动态存储设备，也可以是电可擦可编程只读存储器(electrically er服务器able programmable read-only memory，EEPROM)、只读光盘(compact disc read-only memory，CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器可以是独立存在，通过通信线路1202与处理器相连接。存储器也可以和处理器集成在一起。
其中，存储器1203用于存储执行本申请方案的计算机执行指令，并由处理器1201来控制执行。处理器1201用于执行存储器1203中存储的计算机执行指令，从而实现本申请下述实施例提供的切片信息更新方法。
可选的，本申请实施例中的计算机执行指令也可以称之为应用程序代码，本申请实施例对此不作具体限定。
在具体实现中，作为一种实施例，处理器1201可以包括一个或多个CPU，例如图12中的CPU0和CPU1。
在具体实现中，作为一种实施例，装置1200可以包括多个处理器，例如图12中的处理器1201和处理器1208。这些处理器中的每一个可以是一个单核(single-CPU)处理器，也可以是一个多核(multi-CPU)处理器。这里的处理器可以指一个或多个设备、电路、和/或用于处理数据(例如计算机程序指令)的处理核。
在具体实现中，作为一种实施例，当装置1200为终端时，装置1200还可以包括输出设备1205和输入设备1206。输出设备1205和处理器1201通信，可以以多种方式来显示信息。例如，输出设备705可以是液晶显示器(liquid crystal display，LCD)，发光二级管(light emitting diode，LED)显示设备，阴极射线管(cathode ray tube，CRT)显示设备，或投影仪(projector)等。输入设备1206和处理器1201通信，可以以多种方式接收用户的输入。例如，输入设备1206可以是鼠标、键盘、触摸屏设备或传感设备等。
当图12所示的装置为芯片时，例如可以是移动性管理网元的芯片、策略控制网元的芯片、网络切片选择网元的芯片或终端的芯片，则该芯片包括处理器1201(还可以包括处理器1208)、通信线路1202、存储器1203和通信接口1204。具体地，通信接口1204可以是输入接口、管脚或电路等。存储器1203可以是寄存器、缓存等。处理器1201和处理器1208可以是一个通用的CPU，微处理器，ASIC，或一个或多个用于控制上述任一实施例的切片信息更新方法的程序执行的集成电路。
本申请可以根据上述方法示例对装置进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上 述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。比如，在采用对应各个功能划分各个功能模块的情况下，图13示出了一种装置示意图，该装置1300可以是上述实施例中所涉及的通信网元或通信网元的芯片，通信网元为移动性管理网元或策略控制网元。该装置1300包括接收单元1301、发送单元1302。可选地，还包括处理单元1303。
接收单元1301，用于接收来自网络切片选择网元的通知消息，通知消息包括网络切片的标识信息，通知消息用于指示公共陆地移动网络PLMN支持网络切片，其中，PLMN曾不支持网络切片。发送单元1302，用于通知终端PLMN支持网络切片，终端为曾请求网络切片失败且签约了网络切片的终端。
可选地，处理单元1303，用于根据终端上下文，确定终端。
作为一种实现方式，该装置为移动性管理网元或移动管理网元的芯片，则：
处理单元1303，还用于将网络切片的标识信息加入终端的允许接入的网络切片集合。发送单元1302，具体用于向终端发送更新的允许接入的网络切片集合。
进一步地，发送单元1302，还用于向终端发送指示信息，指示信息用于指示PLMN支持网络切片。
进一步地，处理单元1303，用于将网络切片的标识信息加入终端的允许接入的网络切片集合；发送单元1302，具体用于向终端发送配置更新消息，配置更新消息包括更新的允许接入的网络切片集合。可选地，配置更新消息还包括指示信息。
作为另一种实现方式，该装置为策略控制网元或策略控制网元的芯片，则：
处理单元1303，还用于确定终端注册的移动性管理网元。发送单元1302，具体用于通过移动性管理网元，向终端发送指示信息，指示信息用于指示PLMN支持网络切片。
进一步地，接收单元1301，还用于接收移动性管理网元发送的网络切片的标识信息、移动性管理网元的标识信息和终端的标识信息。
应理解，该装置可以用于实现本发明实施例的方法中由图5所示的实施例中的AMF或图6-图7所示的实施例中的PCF执行的步骤，相关特征可以参照上文，此处不再赘述。
具体的，图13中的接收单元1301、发送单元1302和处理单元1303的功能/实现过程可以通过图12中的处理器1201调用存储器1203中存储的计算机执行指令来实现。或者，图13中的处理单元1303的功能/实现过程可以通过图12中的处理器1201调用存储器1203中存储的计算机执行指令来实现，图13中的接收单元1301和发送单元1302的功能/实现过程可以通过图12中的通信接口1204来实现。
可选的，当该装置1300是芯片时，则接收单元1301和发送单元1302的功能/实现过程还可以通过管脚或电路等来实现。可选地，当该装置1300是芯片时，存储器1203可以为芯片内的存储单元，如寄存器、缓存等。当然，当该装置1300是通信网元时，存储器1203可以是通信网元内的位于芯片外部的存储单元，本申请实施例对此不作具体限定。
本申请可以根据上述方法示例对装置进行功能模块的划分，例如，可以对应各个 功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。比如，在采用对应各个功能划分各个功能模块的情况下，图14示出了一种装置示意图，该装置1400可以是上述实施例中所涉及的移动性管理网元或移动性管理网元的芯片。该装置1400包括接收单元1401、发送单元1402。可选地，该装置1400还包括处理单元1403。可选的，该装置1400还包括存储单元1404。
在第一个实施例中，接收单元1401，用于接收来自策略控制网元的更新消息，更新消息包括指示信息和终端的标识信息，指示信息用于指示公共陆地移动网络PLMN支持网络切片，其中，PLMN曾不支持网络切片；发送单元1402，用于通知终端PLMN支持网络切片，终端为曾请求网络切片失败且签约了网络切片的终端。
在一种可能的实现方式中，处理单元1403，用于将网络切片的标识信息加入终端的允许接入的网络切片集合。发送单元1402，具体用于向终端发送更新的允许接入的网络切片集合。
在一种可能的实现方式中，发送单元1402，还用于向终端发送指示信息，指示信息用于指示PLMN支持网络切片。
在一种可能的实现方式中，处理单元1403，用于将网络切片的标识信息加入终端的允许接入的网络切片集合。发送单元1402，具体用于向终端发送配置更新消息，配置更新消息包括更新的允许接入的网络切片集合。可选地，配置更新消息还包括指示信息。
在一种可能的实现方式中，发送单元1402，具体用于向终端发送NAS消息，NAS消息包括指示信息。
在一种可能的实现方式中，发送单元1402，还用于向策略控制网元发送终端的标识信息、移动性管理网元的标识信息和网络切片的标识信息。
在第二个实施例中，接收单元1401，用于接收来自网络切片选择网元的通知消息，所述通知消息包括网络切片的标识信息和至少一个跟踪区域的标识信息，所述网络切片在所述至少一个跟踪区域内可用，所述网络切片在所述至少一个跟踪区域内曾不可用；处理单元1403，用于确定更新的允许接入的网络切片集合，所述更新的允许接入的网络切片集合包括所述网络切片的标识信息，其中，所述终端位于所述终端的注册区域内，且所述终端能够接入所述网络切片；发送单元1402，用于向所述终端发送所述更新的允许接入的网络切片集合。
在一种可能的实现方式中，所述处理单元1403还用于确定所述网络切片在所述终端的注册区域内可用，则确定所述终端能够接入所述网络切片。
在一种可能的实现方式中，存储单元1404，用于在所述接收单元1401接收来自网络切片选择网元的通知消息之前，存储所述终端的拒绝接入的网络切片集合，所述拒绝接入的网络切片集合包括所述网络切片的标识信息。
在一种可能的实现方式中，所述接收单元1401，还用于在所述发送单元1402向所述终端发送所述更新的允许接入的网络切片集合之前，接收来自所述终端的注册请求消息，所述注册请求消息包括所述网络切片的标识信息。
在一种可能的实现方式中，所述发送单元1402，具体用于向所述终端发送注册接 受消息，所述注册接受消息包括所述更新的允许接入的网络切片集合。
应理解，该装置可以用于实现本发明实施例的方法中由图6-图7、以及图10-图11所示的实施例中的AMF执行的步骤，相关特征可以参照上文，此处不再赘述。
具体的，图14中的接收单元1401、发送单元1402和处理单元1403的功能/实现过程可以通过图12中的处理器1201调用存储器1203中存储的计算机执行指令来实现。或者，图14中的处理单元1403的功能/实现过程可以通过图12中的处理器1201调用存储器1203中存储的计算机执行指令来实现，图14中的接收单元1401和发送单元1402的功能/实现过程可以通过图12中的通信接口1204来实现。
可选的，当该装置1400是芯片时，则接收单元1401和发送单元1402的功能/实现过程还可以通过管脚或电路等来实现。可选地，当该装置1400是芯片时，存储器1203可以为芯片内的存储单元，如寄存器、缓存等。当然，当该装置1400是移动性管理网元时，存储器1203可以是移动性管理网元内的位于芯片外部的存储单元，本申请实施例对此不作具体限定。
本申请可以根据上述方法示例对装置进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。比如，在采用对应各个功能划分各个功能模块的情况下，图15示出了一种装置示意图，该装置1500可以是上述实施例中所涉及的策略控制网元或策略控制网元的芯片。该装置1500包括接收单元1501、发送单元1502和处理单元1503。
接收单元1501，用于接收来自移动性管理网元的终端的标识信息和网络切片的标识信息，网络切片为终端的当前注册区域不支持的网络切片；
处理单元1503，用于从网络切片选择网元获取网络切片对应的服务区域；
若处理单元1503获知终端移动至服务区域，则发送单元1502通知终端网络切片可用。
在一种可能的实现方式中，发送单元1502，还用于向移动性管理网元订阅：当终端的位置发生更新时，移动性管理网元向装置发送终端更新后的位置。
在一种可能的实现方式中，发送单元1502，具体用于：通过移动性管理网元向终端发送指示信息，指示信息用于指示网络切片可用。
应理解，该装置可以用于实现本发明实施例的方法中由图8所示的实施例中的PCF执行的步骤，相关特征可以参照上文，此处不再赘述。
具体的，图15中的接收单元1501、发送单元1502和处理单元1503的功能/实现过程可以通过图12中的处理器1201调用存储器1203中存储的计算机执行指令来实现。或者，图15中的处理单元1503的功能/实现过程可以通过图12中的处理器1201调用存储器1203中存储的计算机执行指令来实现，图15中的接收单元1501和发送单元1502的功能/实现过程可以通过图12中的通信接口1204来实现。
可选的，当该装置1500是芯片时，则接收单元1501和发送单元1502的功能/实现过程还可以通过管脚或电路等来实现。可选地，当该装置1500是芯片时，存储器 1203可以为芯片内的存储单元，如寄存器、缓存等。当然，当该装置1500是策略控制网元时，存储器1203可以是策略控制网元内的位于芯片外部的存储单元，本申请实施例对此不作具体限定。
本申请可以根据上述方法示例对装置进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。比如，在采用对应各个功能划分各个功能模块的情况下，图16示出了一种装置示意图，该装置1600可以是上述实施例中所涉及的网络切片选择网元或网络切片选择网元的芯片。该装置1600包括发送单元1602和处理单元1603。可选地，还包括接收单元1601。
处理单元1603，用于确定公共陆地移动网络PLMN支持网络切片，其中，PLMN曾不支持网络切片；
发送单元1602，用于向通信网元发送通知消息，通知消息包括网络切片的标识信息，通知消息用于指示PLMN支持网络切片。其中，通信网元为策略控制网元或移动性管理网元。
在一种可能的实现方式中，接收单元1601用于接收来自通信网元的订阅：当PLMN支持网络切片时，网络切片选择网元通知通信网元。
在一种可能的实现方式中，处理单元1603，还用于根据PLMN中的移动性管理网元支持的切片类型，确定支持网络切片的移动性管理网元为通信网元。应理解，该装置可以用于实现本发明实施例的方法中由图5-图7所示的实施例中的NSSF执行的步骤，相关特征可以参照上文，此处不再赘述。
具体的，图16中的接收单元1601、发送单元1602和处理单元1603的功能/实现过程可以通过图12中的处理器1201调用存储器1203中存储的计算机执行指令来实现。或者，图16中的处理单元1603的功能/实现过程可以通过图12中的处理器1201调用存储器1203中存储的计算机执行指令来实现，图16中的接收单元1601和发送单元1602的功能/实现过程可以通过图12中的通信接口1204来实现。
可选的，当该装置1600是芯片时，则接收单元1601和发送单元1602的功能/实现过程还可以通过管脚或电路等来实现。可选地，当该装置1600是芯片时，存储器1203可以为芯片内的存储单元，如寄存器、缓存等。当然，当该装置1500是网络切片选择网元时，存储器1203可以是网络切片选择网元内的位于芯片外部的存储单元，本申请实施例对此不作具体限定。
本申请可以根据上述方法示例对装置进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。比如，在采用对应各个功能划分各个功能模块的情况下，图17示出了一种装置示意图，该装置1700可以是上述实施例中所涉及的终端或终端 的芯片。该装置1700包括接收单元1701、发送单元1702、处理单元1703。
所述接收单元1701，用于接收来自移动性管理网元的所述终端的允许接入的网络切片集合和拒绝接入的网络切片集合，所述拒绝接入的网络切片集合包括网络切片的标识信息，所述终端位于所述终端的注册区域内；所述发送单元1702，用于向所述移动性管理网元发送注册请求消息，所述注册请求消息包括所述网络切片的标识信息；所述接收单元1701，还用于接收来自所述移动性管理网元的更新的允许接入的网络切片的集合，所述更新的允许接入的网络切片的集合包括所述网络切片的标识信息，所述网络切片在所述终端的注册区域内可用，所述网络切片在所述终端的注册区域内曾不可用。
在一种可能的实现方式中，所述接收单元1701，具体用于接收来自所述移动性管理网元的注册接受消息，所述注册接受消息包括所述更新的允许接入的网络切片的集合。
应理解，该装置可以用于实现本发明实施例的方法中由图10-图11所示的实施例中的终端执行的步骤，相关特征可以参照上文，此处不再赘述。
具体的，图17中的接收单元1701、发送单元1702和处理单元1703的功能/实现过程可以通过图12中的处理器1201调用存储器1203中存储的计算机执行指令来实现。或者，图17中的处理单元1703的功能/实现过程可以通过图12中的处理器1201调用存储器1203中存储的计算机执行指令来实现，图17中的接收单元1701和发送单元1702的功能/实现过程可以通过图12中的通信接口1204来实现。
可选的，当该装置1700是芯片时，则接收单元1701和发送单元1702的功能/实现过程还可以通过管脚或电路等来实现。可选地，当该装置1700是芯片时，存储器1203可以为芯片内的存储单元，如寄存器、缓存等。当然，当该装置1500是终端时，存储器1203可以是终端内的位于芯片外部的存储单元，本申请实施例对此不作具体限定。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本发明实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘(Solid State Disk，SSD))等。
本申请实施例中所描述的各种说明性的逻辑单元和电路可以通过通用处理器，数字信号处理器，专用集成电路(ASIC)，现场可编程门阵列(FPGA)或其它可编程逻辑装置，离散门或晶体管逻辑，离散硬件部件，或上述任何组合的设计来实现或操 作所描述的功能。通用处理器可以为微处理器，可选地，该通用处理器也可以为任何传统的处理器、控制器、微控制器或状态机。处理器也可以通过计算装置的组合来实现，例如数字信号处理器和微处理器，多个微处理器，一个或多个微处理器联合一个数字信号处理器核，或任何其它类似的配置来实现。
本申请实施例中所描述的方法或算法的步骤可以直接嵌入硬件、处理器执行的软件单元、或者这两者的结合。软件单元可以存储于RAM存储器、闪存、ROM存储器、EPROM存储器、EEPROM存储器、寄存器、硬盘、可移动磁盘、CD-ROM或本领域中其它任意形式的存储媒介中。示例性地，存储媒介可以与处理器连接，以使得处理器可以从存储媒介中读取信息，并可以向存储媒介存写信息。可选地，存储媒介还可以集成到处理器中。处理器和存储媒介可以设置于ASIC中，ASIC可以设置于终端设备中。可选地，处理器和存储媒介也可以设置于终端设备中的不同的部件中。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
尽管结合具体特征及其实施例对本发明进行了描述，显而易见的，在不脱离本发明的精神和范围的情况下，可对其进行各种修改和组合。相应地，本说明书和附图仅仅是所附权利要求所界定的本发明的示例性说明，且视为已覆盖本发明范围内的任意和所有修改、变化、组合或等同物。显然，本领域的技术人员可以对本发明进行各种改动和变型而不脱离本发明的精神和范围。这样，倘若本发明的这些修改和变型属于本发明权利要求及其等同技术的范围之内，则本发明也意图包含这些改动和变型在内。

Claims (44)

  1. 一种切片信息更新方法，其特征在于，包括：
    通信网元接收来自网络切片选择网元的通知消息，所述通知消息包括网络切片的标识信息，所述通知消息用于指示公共陆地移动网络PLMN支持所述网络切片；
    所述通信网元通知终端所述PLMN支持所述网络切片，所述终端为曾请求所述网络切片失败且签约了所述网络切片的终端。
  2. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    所述通信网元根据终端上下文，确定所述终端。
  3. 根据权利要求1或2所述的方法，其特征在于，所述通信网元为移动性管理网元；所述方法还包括：
    所述移动性管理网元将所述网络切片的标识信息加入所述终端的允许接入的网络切片集合；
    所述通信网元通知终端所述PLMN支持所述网络切片，包括：
    所述移动性管理网元向所述终端发送所述更新的允许接入的网络切片集合。
  4. 根据权利要求3所述的方法，其特征在于，所述通信网元通知终端所述PLMN支持所述网络切片，还包括：
    所述移动性管理网元向所述终端发送指示信息，所述指示信息用于指示所述PLMN支持所述网络切片。
  5. 根据权利要求1或2所述的方法，其特征在于，所述通信网元为策略控制网元；所述方法还包括：
    所述策略控制网元确定所述终端注册的移动性管理网元；
    所述通信网元通知终端所述PLMN支持所述网络切片，包括：
    所述策略控制网元通过所述移动性管理网元，向所述终端发送指示信息，所述指示信息用于指示所述PLMN支持所述网络切片。
  6. 一种切片信息更新方法，其特征在于，包括：
    移动性管理网元接收来自策略控制网元的更新消息，所述更新消息包括指示信息和终端的标识信息，所述指示信息用于指示公共陆地移动网络PLMN支持网络切片；
    所述移动性管理网元通知终端所述PLMN支持所述网络切片，所述终端为曾请求所述网络切片失败且签约了所述网络切片的终端。
  7. 根据权利要求6所述的方法，其特征在于，所述方法还包括：
    所述移动性管理网元将所述网络切片的标识信息加入所述终端的允许接入的网络切片集合；
    所述移动性管理网元通知终端所述PLMN支持所述网络切片，包括：
    所述移动性管理网元向所述终端发送所述更新的允许接入的网络切片集合。
  8. 根据权利要求7所述的方法，其特征在于，所述移动性管理网元通知终端所述PLMN支持所述网络切片，还包括：
    所述移动性管理网元向所述终端发送指示信息，所述指示信息用于指示所述PLMN支持所述网络切片。
  9. 根据权利要求6所述的方法，其特征在于，所述移动性管理网元通知终端所述 PLMN支持所述网络切片，包括：
    所述移动性管理网元向所述终端发送NAS消息，所述NAS消息包括所述指示信息。
  10. 一种切片信息更新方法，其特征在于，包括：
    策略控制网元接收来自移动性管理网元的终端的标识信息和网络切片的标识信息，所述网络切片为所述终端的当前注册区域不支持的网络切片；
    所述策略控制网元从网络切片选择网元获取所述网络切片对应的服务区域；
    若所述策略控制网元获知所述终端移动至所述服务区域，则通知所述终端所述网络切片可用。
  11. 根据权利要求10所述的方法，其特征在于，所述策略控制网元通知所述终端所述网络切片当前可用，包括：
    所述策略控制网元通过所述移动性管理网元向所述终端发送指示信息，所述指示信息用于指示所述网络切片可用。
  12. 一种切片信息更新方法，其特征在于，包括：
    网络切片选择网元确定公共陆地移动网络PLMN支持网络切片；
    所述网络切片选择网元向通信网元发送通知消息，所述通知消息包括所述网络切片的标识信息，所述通知消息用于指示所述PLMN支持所述网络切片。
  13. 根据权利要求12所述的方法，其特征在于，所述方法还包括：
    所述网络切片选择网元接收来自所述通信网元的订阅：当所述PLMN支持所述网络切片时，所述网络切片选择网元通知所述通信网元。
  14. 根据权利要求12或13所述的方法，其特征在于，所述通信网元为策略控制网元或移动性管理网元。
  15. 根据权利要求12所述的方法，其特征在于，所述方法还包括：
    所述网络切片选择网元根据所述PLMN中的移动性管理网元支持的切片类型，确定支持所述网络切片的移动性管理网元为所述通信网元。
  16. 一种切片信息更新方法，其特征在于，包括：
    移动性管理网元接收来自网络切片选择网元的通知消息，所述通知消息包括网络切片的标识信息和至少一个跟踪区域的标识信息，所述网络切片在所述至少一个跟踪区域内可用，所述网络切片在所述至少一个跟踪区域内曾不可用；
    所述移动性管理网元确定更新的允许接入的网络切片集合，所述更新的允许接入的网络切片集合包括所述网络切片的标识信息，其中，所述终端位于所述终端的注册区域内，且所述终端能够接入所述网络切片；
    所述移动性管理网元向所述终端发送所述更新的允许接入的网络切片集合。
  17. 根据权利要求16所述的方法，其特征在于，还包括：
    所述移动性管理网元确定所述网络切片在所述终端的注册区域内可用，则确定所述终端能够接入所述网络切片。
  18. 根据权利要求16或17所述的方法，其特征在于，还包括：
    所述移动性管理网元接收来自网络切片选择网元的通知消息之前，存储所述终端的拒绝接入的网络切片集合，所述拒绝接入的网络切片集合包括所述网络切片的标识信息。
  19. 根据权利要求16-18任一项所述的方法，其特征在于，所述移动性管理网元向所述终端发送所述更新的允许接入的网络切片集合之前，还包括：
    所述移动性管理网元接收来自所述终端的注册请求消息，所述注册请求消息包括所述网络切片的标识信息。
  20. 根据权利要求19所述的方法，其特征在于，所述移动性管理网元向所述终端发送所述更新的允许接入的网络切片集合，包括：
    所述移动性管理网元向所述终端发送注册接受消息，所述注册接受消息包括所述更新的允许接入的网络切片集合。
  21. 一种切片信息更新方法，其特征在于，包括：
    终端接收来自移动性管理网元的所述终端的允许接入的网络切片集合和拒绝接入的网络切片集合，所述拒绝接入的网络切片集合包括网络切片的标识信息，所述终端位于所述终端的注册区域内；
    所述终端向所述移动性管理网元发送注册请求消息，所述注册请求消息包括所述网络切片的标识信息；
    所述终端接收来自所述移动性管理网元的更新的允许接入的网络切片的集合，所述更新的允许接入的网络切片的集合包括所述网络切片的标识信息，所述网络切片在所述终端的注册区域内可用，所述网络切片在所述终端的注册区域内曾不可用。
  22. 根据权利要求21所述的方法，其特征在于，所述终端接收来自所述移动性管理网元的更新的允许接入的网络切片的集合，包括：
    所述终端接收来自所述移动性管理网元的注册接受消息，所述注册接受消息包括所述更新的允许接入的网络切片的集合。
  23. 一种装置，其特征在于，包括：接收单元和发送单元；
    所述接收单元，用于接收来自网络切片选择网元的通知消息，所述通知消息包括网络切片的标识信息，所述通知消息用于指示公共陆地移动网络PLMN支持所述网络切片；
    所述发送单元，用于通知终端所述PLMN支持所述网络切片，所述终端为曾请求所述网络切片失败且签约了所述网络切片的终端。
  24. 根据权利要求23所述的装置，其特征在于，所述装置还包括处理单元，用于根据终端上下文，确定所述终端。
  25. 根据权利要求23或24所述的装置，其特征在于，所述装置为移动性管理网元；所述装置包括处理单元；
    所述处理单元，用于将所述网络切片的标识信息加入所述终端的允许接入的网络切片集合；
    所述发送单元，具体用于向所述终端发送所述更新的允许接入的网络切片集合。
  26. 根据权利要25所述的装置，其特征在于，所述发送单元，还用于向所述终端发送指示信息，所述指示信息用于指示所述PLMN支持所述网络切片。
  27. 根据权利要求23或24所述的装置，其特征在于，所述装置为策略控制网元；所述装置包括处理单元；
    所述处理单元，用于确定所述终端注册的移动性管理网元；
    所述发送单元，具体用于通过所述移动性管理网元，向所述终端发送指示信息， 所述指示信息用于指示所述PLMN支持所述网络切片。
  28. 一种装置，其特征在于，包括：接收单元和发送单元；
    所述接收单元，用于接收来自策略控制网元的更新消息，所述更新消息包括指示信息和终端的标识信息，所述指示信息用于指示公共陆地移动网络PLMN支持网络切片；
    所述发送单元，用于通知终端所述PLMN支持所述网络切片，所述终端为曾请求所述网络切片失败且签约了所述网络切片的终端。
  29. 根据权利要求28所述的装置，其特征在于，所述装置还包括处理单元；
    所述处理单元，用于将所述网络切片的标识信息加入所述终端的允许接入的网络切片集合；
    所述发送单元，具体用于向所述终端发送所述更新的允许接入的网络切片集合。
  30. 根据权利要求29所述的装置，其特征在于，所述发送单元，还用于向所述终端发送指示信息，所述指示信息用于指示所述PLMN支持所述网络切片。
  31. 根据权利要求28所述的装置，其特征在于，所述发送单元，具体用于向所述终端发送NAS消息，所述NAS消息包括所述指示信息。
  32. 一种装置，其特征在于，包括：接收单元、发送单元和处理单元；
    所述接收单元，用于接收来自移动性管理网元的终端的标识信息和网络切片的标识信息，所述网络切片为所述终端的当前注册区域不支持的网络切片；
    所述处理单元，用于从网络切片选择网元获取所述网络切片对应的服务区域；
    若所述处理单元获知所述终端移动至所述服务区域，则所述发送单元通知所述终端所述网络切片可用。
  33. 根据权利要求32所述的装置，其特征在于，所述发送单元，具体用于：通过所述移动性管理网元向所述终端发送指示信息，所述指示信息用于指示所述网络切片可用。
  34. 一种装置，其特征在于，包括：处理单元和发送单元；
    所述处理单元，用于确定公共陆地移动网络PLMN支持网络切片；
    所述发送单元，用于向通信网元发送通知消息，所述通知消息包括所述网络切片的标识信息，所述通知消息用于指示所述PLMN支持所述网络切片。
  35. 根据权利要求34所述的装置，其特征在于，所述装置还包括接收单元，用于接收来自所述通信网元的订阅：当所述PLMN支持所述网络切片时，所述网络切片选择网元通知所述通信网元。
  36. 根据权利要求34或35所述的装置，其特征在于，所述通信网元为策略控制网元或移动性管理网元。
  37. 根据权利要求34所述的装置，其特征在于，所述处理单元，还用于根据所述PLMN中的移动性管理网元支持的切片类型，确定支持所述网络切片的移动性管理网元为所述通信网元。
  38. 一种装置，其特征在于，包括：
    接收单元，用于接收来自网络切片选择网元的通知消息，所述通知消息包括网络切片的标识信息和至少一个跟踪区域的标识信息，所述网络切片在所述至少一个跟踪区域内可用，所述网络切片在所述至少一个跟踪区域内曾不可用；
    处理单元，用于确定更新的允许接入的网络切片集合，所述更新的允许接入的网络切片集合包括所述网络切片的标识信息，其中，所述终端位于所述终端的注册区域内，且所述终端能够接入所述网络切片；
    发送单元，用于向所述终端发送所述更新的允许接入的网络切片集合。
  39. 根据权利要求38所述的装置，其特征在于，所述处理单元还用于确定所述网络切片在所述终端的注册区域内可用，则确定所述终端能够接入所述网络切片。
  40. 根据权利要求38或39所述的装置，其特征在于，所述装置还包括存储单元，用于：
    在所述接收单元接收来自网络切片选择网元的通知消息之前，存储所述终端的拒绝接入的网络切片集合，所述拒绝接入的网络切片集合包括所述网络切片的标识信息。
  41. 根据权利要求38-40任一项所述的装置，其特征在于，所述接收单元，还用于：
    在所述发送单元向所述终端发送所述更新的允许接入的网络切片集合之前，接收来自所述终端的注册请求消息，所述注册请求消息包括所述网络切片的标识信息。
  42. 根据权利要求41所述的装置，其特征在于，所述发送单元，具体用于向所述终端发送注册接受消息，所述注册接受消息包括所述更新的允许接入的网络切片集合。
  43. 一种装置，应用于终端，其特征在于，包括发送单元和接收单元；
    所述接收单元，用于接收来自移动性管理网元的所述终端的允许接入的网络切片集合和拒绝接入的网络切片集合，所述拒绝接入的网络切片集合包括网络切片的标识信息，所述终端位于所述终端的注册区域内；
    所述发送单元，用于向所述移动性管理网元发送注册请求消息，所述注册请求消息包括所述网络切片的标识信息；
    所述接收单元，还用于接收来自所述移动性管理网元的更新的允许接入的网络切片的集合，所述更新的允许接入的网络切片的集合包括所述网络切片的标识信息，所述网络切片在所述终端的注册区域内可用，所述网络切片在所述终端的注册区域内曾不可用。
  44. 根据权利要求43所述的装置，其特征在于，所述接收单元，具体用于接收来自所述移动性管理网元的注册接受消息，所述注册接受消息包括所述更新的允许接入的网络切片的集合。
PCT/CN2018/120415 2017-12-20 2018-12-11 一种切片信息更新方法及装置 WO2019120109A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
EP18892843.6A EP3709707B1 (en) 2017-12-20 2018-12-11 Slice information update method and apparatus
US16/905,383 US11425634B2 (en) 2017-12-20 2020-06-18 Slice information update method and apparatus
US17/880,457 US20220377653A1 (en) 2017-12-20 2022-08-03 Slice information update method and apparatus

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN201711385748.8 2017-12-20
CN201711385748 2017-12-20
CN201811505349.5 2018-12-10
CN201811505349.5A CN109951877B (zh) 2017-12-20 2018-12-10 一种切片信息更新方法及装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/905,383 Continuation US11425634B2 (en) 2017-12-20 2020-06-18 Slice information update method and apparatus

Publications (1)

Publication Number Publication Date
WO2019120109A1 true WO2019120109A1 (zh) 2019-06-27

Family

ID=66992990

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/120415 WO2019120109A1 (zh) 2017-12-20 2018-12-11 一种切片信息更新方法及装置

Country Status (2)

Country Link
US (1) US20220377653A1 (zh)
WO (1) WO2019120109A1 (zh)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112788704A (zh) * 2019-11-06 2021-05-11 华为技术有限公司 网络切片的使用控制方法、装置及系统
CN113709764A (zh) * 2020-05-21 2021-11-26 华为技术有限公司 一种通信方法及装置
CN115250510A (zh) * 2021-04-08 2022-10-28 维沃移动通信有限公司 选择网络的方法、装置、终端和网络设备
US11553408B2 (en) 2020-04-17 2023-01-10 Samsung Electronics Co., Ltd. Method and user equipment for managing failure in registration for accessing network slice

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021052603A1 (en) * 2019-09-20 2021-03-25 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for abstracting network resources in a mobile communications network

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106572516A (zh) * 2016-09-28 2017-04-19 华为技术有限公司 一种网络切片选择方法、终端设备及网络设备
CN106982458A (zh) * 2017-03-09 2017-07-25 华为技术有限公司 一种网络切片的选择方法及装置
CN107071799A (zh) * 2017-02-16 2017-08-18 北京小米移动软件有限公司 网络切片配置方法及装置、无线接入网ran节点和终端

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106572516A (zh) * 2016-09-28 2017-04-19 华为技术有限公司 一种网络切片选择方法、终端设备及网络设备
CN107071799A (zh) * 2017-02-16 2017-08-18 北京小米移动软件有限公司 网络切片配置方法及装置、无线接入网ran节点和终端
CN106982458A (zh) * 2017-03-09 2017-07-25 华为技术有限公司 一种网络切片的选择方法及装置

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112788704A (zh) * 2019-11-06 2021-05-11 华为技术有限公司 网络切片的使用控制方法、装置及系统
CN112788704B (zh) * 2019-11-06 2022-05-10 华为技术有限公司 网络切片的使用控制方法、装置及系统
US11553408B2 (en) 2020-04-17 2023-01-10 Samsung Electronics Co., Ltd. Method and user equipment for managing failure in registration for accessing network slice
CN113709764A (zh) * 2020-05-21 2021-11-26 华为技术有限公司 一种通信方法及装置
CN113709764B (zh) * 2020-05-21 2023-06-27 华为技术有限公司 一种通信方法及装置
CN115250510A (zh) * 2021-04-08 2022-10-28 维沃移动通信有限公司 选择网络的方法、装置、终端和网络设备

Also Published As

Publication number Publication date
US20220377653A1 (en) 2022-11-24

Similar Documents

Publication Publication Date Title
CN109951877B (zh) 一种切片信息更新方法及装置
EP3745645B1 (en) Method, device, and system for guaranteeing service level agreement of application
WO2019120109A1 (zh) 一种切片信息更新方法及装置
US20200187144A1 (en) Communication method, apparatus, and system
US20190373520A1 (en) Method and apparatus for complementary and equivalent network slice deployment in a network environment
CN110971421B (zh) 订阅更新方法、设备及系统
RU2763159C1 (ru) Способ и устройство связи
WO2019137553A1 (zh) 一种配置ue的策略的方法、装置和系统
WO2020168753A1 (zh) 一种通信方法及装置
WO2019192546A1 (zh) 一种定位方法及装置
US20220232455A1 (en) Service processing method, device, and system
WO2021134167A1 (zh) 一种漫游的方法、装置及系统
WO2019218762A1 (zh) 一种策略控制方法、装置及系统
WO2019052434A1 (zh) 一种基于用户设备位置的数据传输方法、装置和系统
US20230388908A1 (en) Network slice-based communication method and apparatus
WO2022022440A1 (zh) 网络重连方法、设备、系统及存储介质
WO2019223638A1 (zh) 一种api信息传输方法及装置
WO2021159415A1 (zh) 通信方法、装置及系统
WO2021134175A1 (zh) 一种漫游的方法、装置及系统
WO2020063789A1 (zh) 删除小区的方法及装置
WO2021159523A1 (zh) 通信方法、装置及系统
WO2023010995A1 (zh) 一种选择跟踪区域的方法、设备及系统
US20240080704A1 (en) System and method for reducing network component loads
JP2021016013A (ja) 通信制御方法
WO2019105156A1 (zh) 一种通信方法及装置

Legal Events

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

Ref document number: 18892843

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2018892843

Country of ref document: EP

Effective date: 20200611

NENP Non-entry into the national phase

Ref country code: DE