CN109951877B

CN109951877B - Slice information updating method and device

Info

Publication number: CN109951877B
Application number: CN201811505349.5A
Authority: CN
Inventors: 朱方园; 李岩
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2017-12-20
Filing date: 2018-12-10
Publication date: 2023-06-02
Anticipated expiration: 2038-12-10
Also published as: US11425634B2; EP3709707B1; EP3709707A4; US20200322879A1; CN109951877A; EP3709707A1

Abstract

The application provides a slice information updating method and device. The method comprises the following steps: when the network slice selection network element determines that the network slice that is not supported by the PLMN is updated to be supported, sending a notification message to the communication network element, wherein the notification message is used for indicating the PLMN to support the network slice, and then notifying the communication network element of a terminal which has requested that the network slice fails and signs up for the network slice: the PLMN currently supports the network slice. Thereby realizing that the corresponding terminal knows that the PLMN supports the network slice currently.

Description

Slice information updating method and device

The present application claims priority from chinese patent application entitled "a slice information update method and apparatus" filed in the intellectual property office of the people's republic of China, application number 201711385748.8, and title of the invention, 12/20/2017, the entire contents of which are incorporated herein by reference.

Technical Field

The present disclosure relates to the field of mobile communications technologies, and in particular, to a slice information updating method and apparatus.

Background

When the core network deploys the network slice, the terminal is initially attached to the network, and the selection process of the network slice is triggered. The network side selects the network slice which is allowed to be accessed for the terminal according to the information such as the network slice requested by the terminal, the subscription data of the terminal and the like.

After the network side selects the network slice allowing access for the terminal, the terminal is informed of the selected network slice. If the network side determines that the subscription data of the terminal includes network slices not supported by the public land mobile network (Public Land Mobile Network, PLMN), the network side also informs the terminal of the network slices not supported by the PLMN.

In the above scenario, when the network slice that is not supported by the PLMN is updated to be supported by the PLMN, how the network side notifies the terminals and which terminals are notified, and no corresponding solution exists at present.

Disclosure of Invention

The application provides a slice information updating method and device, so as to inform corresponding terminals when network slices which are not supported by PLMN are updated to be supported by PLMN.

In a first aspect, the present application provides a slice information updating method. The method comprises the following steps: first, the communication network element receives a notification message from the network slice selection network element, the notification message including identification information of the network slice, the notification message being for indicating that the PLMN supports network slices, wherein the PLMN did not support network slices. The communication network element then informs the terminal PLMN that the network slice is supported, the terminal being a terminal that requested a network slice failure and signed up for a network slice. Wherein the communication network element is a mobility management network element or a policy control network element.

When the network slice selecting network element determines that the network slice which is not supported by the PLMN is updated to be supported, the method sends a notification message to the communication network element, wherein the notification message is used for indicating the PLMN to support the network slice, and then the communication network element notifies the terminal which has requested the network slice to fail and signs up for the network slice: the PLMN currently supports the network slice. Therefore, the corresponding terminal is enabled to know that the PLMN supports the network slice currently, and the terminal can use the network slice when the terminal has the service requirement corresponding to the network slice, so that the service capability of the terminal is improved.

In one possible implementation, the communication network element may determine the terminal according to a terminal context.

In one possible implementation, the communication network element is a mobility management network element. Then further comprising: the mobility management network element adds the identification information of the network slice to the set of network slices of the terminal that are allowed to be accessed. The communication network element informs the terminal that the PLMN supports network slicing, specifically including: the mobility management network element sends the updated set of allowed access network slices to the terminal. Further, the mobility management network element sends indication information to the terminal, where the indication information is used to indicate that the PLMN supports network slicing.

For example, as a specific implementation, the mobility management network element sends a configuration update message to the terminal, the configuration update message comprising an updated set of allowed access network slices. Optionally, the configuration update message further comprises indication information.

In the method, the mobility management network element informs the terminal PLMN of supporting network slices in the mode of updating the access allowed network slice set.

In another possible implementation, the communication network element is a policy control network element. Then further still comprising: the policy control network element determines a mobility management network element for terminal registration. The communication network element informs the terminal of supporting network slicing by PLMN, which specifically comprises: the policy control network element sends indication information to the terminal through the mobility management network element, wherein the indication information is used for indicating the PLMN to support network slicing. Optionally, the policy control network element further receives identification information of the network slice, identification information of the mobility management network element, and identification information of the terminal sent by the mobility management network element.

In the implementation manner, the policy control network element sends indication information to the terminal to indicate the PLMN to support the network slice.

In a second aspect, the present application provides a slice information updating method. The method comprises the following steps: the mobility management network element receives an update message from the policy control network element, the update message comprising indication information and identification information of the terminal, the indication information being used to indicate that the public land mobile network PLMN supports network slicing, wherein the PLMN does not support network slicing. The mobility management network element then informs the terminal PLMN that the network slice is supported, the terminal being a terminal that requested a network slice failure and signed up for a network slice.

According to the method, when the mobility management network element receives the notification message from the policy control network element, the notification message is used for indicating 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 slice. Therefore, the corresponding terminal is enabled to know that the PLMN supports the network slice currently, and the terminal can use the network slice when the terminal has the service requirement corresponding to the network slice, so that the service capability of the terminal is improved.

In one possible implementation, the method further includes: the mobility management network element adds the identification information of the network slice to the set of network slices of the terminal that are allowed to be accessed. The mobility management network element informs the terminal of supporting network slicing by PLMN, specifically comprising: the mobility management network element sends the updated set of allowed access network slices to the terminal. Optionally, the mobility management network element further sends indication information to the terminal, where the indication information is used to indicate that the PLMN supports network slicing.

In one possible implementation, the mobility management network element informs the terminal PLMN to support network slicing, including: the mobility management network element sends a NAS message to the terminal, wherein the NAS message comprises indication information.

In one possible implementation manner, the method further includes: the mobility management network element sends the identification information of the terminal, the identification information of the mobility management network element and the identification information of the network slice to the policy control network element.

In a third aspect, the present application provides a slice information updating method. The method comprises the following steps: the policy control network element receives the identification information of the terminal from the mobility management network element and the identification information of the network slice, wherein the network slice 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. And if the strategy control network element knows that the terminal moves to the service area, notifying the terminal that the network slice is available.

According to the method, if the strategy control network element determines that the terminal moves to the service area corresponding to the network slice, the strategy control network element informs the terminal that the network slice is currently available. The network slice is a network slice which is not supported by an area where the terminal is located before moving to a service area corresponding to the network slice. Thereby realizing the notification of the corresponding terminal: the network slice is currently available, so that the terminal can use the network slice when the service corresponding to the network slice is required, and the service capability of the terminal is improved.

In one possible implementation, the method further includes: the policy control network element subscribes to the mobility management network element: when the position of the terminal is updated, the mobility management network element sends the updated position of the terminal to the policy control network element.

In one possible implementation manner, the policy control network element informs the terminal that the network slice is currently available, specifically includes: the policy control network element sends indication information to the terminal through the mobility management network element, wherein the indication information is used for indicating that the network slice is available.

In a fourth aspect, the present application provides a slice information updating method. The method comprises the following steps: the network slice selection network element determines that the PLMN supports network slices, wherein the PLMN did not support network slices. Next, the network slice selection network element sends a notification message to the communication network element, the notification message including identification information of the network slice, the notification message being for indicating that the PLMN supports network slices. Wherein the communication network element is a policy control network element or a mobility management network element.

In the above method, when the network slice selecting network element determines that the network slice that is not supported by the PLMN is updated to be supported, a notification message is sent to the communication network element, where the notification message is used to instruct the PLMN to support the network slice, and then the communication network element may notify the terminal that requested the network slice to fail and signs up for the network slice: the PLMN currently supports the network slice. Therefore, the corresponding terminal is enabled to know that the PLMN supports the network slice currently, and the terminal can use the network slice when the terminal has the service requirement corresponding to the network slice, so that the service capability of the terminal is improved.

In one possible implementation manner, the method further includes: the network slice selection network element receives subscriptions from the communication network element: when the PLMN supports network slicing, the network slicing selection network element informs the communication network element.

In one possible implementation, the method further includes: and the network slice selection network element determines the mobility management network element supporting the network slice as a communication network element needing to send notification information according to the slice type supported by the mobility management network element in the PLMN.

In a fifth aspect, the present application provides a slice information updating method. The method comprises the following steps: the mobility management network element receives a notification message from a network slice selection network element, the notification message including identification information of a network slice and identification information of at least one tracking area, the network slice being available in the at least one tracking area, the network slice being unavailable in the at least one tracking area; the method comprises the steps that a mobility management network element determines an updated access-allowed network slice set, wherein the updated access-allowed network slice set comprises identification information of network slices, a terminal is located in a registration area of the terminal, and the terminal can access the network slices; and the mobility management network element sends the updated access allowed network slice set 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 method includes when the network slice selection network element determines that the network slice is available in at least one tracking area from unavailable update, sending a notification message to the mobility management network element, wherein the notification message comprises identification information of the network slice and identification information of the at least one tracking area, then the mobility management network element determines an updated set of network slices allowed to be accessed, the updated set of network slices allowed to be accessed comprises the identification information of the network slice, and sending the updated set of network slices allowed to be accessed to the terminal. Therefore, the corresponding terminal is enabled to know that the network slice can be accessed currently, and the terminal can use the network slice when the terminal has the service requirement corresponding to the network slice, so that the service capability of the terminal is improved.

In one possible implementation, the mobility management network element determines that the network slice is available in a registration area of the terminal, and determines that the terminal is able to access the network slice.

In one possible implementation, before the mobility management network element receives the notification message from the network slice selection network element, the mobility management network element further stores a set of network slices of the terminal that are denied access, where the set of network slices of the terminal that are denied access include identification information of the network slices.

In one possible implementation, before the mobility management network element sends the updated set of network slices allowed to access to the terminal, a registration request message from the terminal is also received, where the registration request message includes identification information of the network slices.

In one possible implementation manner, the mobility management network element sends the updated set of network slices allowed to be accessed to the terminal, specifically including: the mobility management network element sends a registration accept message to the terminal, the registration accept message comprising the updated set of allowed access network slices.

In a sixth aspect, the present application provides a slice information updating method. The method comprises the following steps: the method comprises the steps that a terminal receives a network slice set which is allowed to be accessed and a network slice set which is refused to be accessed from a terminal of a mobility management network element, wherein the network slice set which is refused to be accessed comprises identification information of the network slice, and the terminal is positioned in a registration area of the terminal; the terminal sends a registration request message to a mobility management network element, wherein the registration request message comprises identification information of the network slice; the terminal receives an updated set of access-allowed network slices from the mobility management network element, the updated set of access-allowed network slices including identification information of the network slices that were available in the registration area of the terminal and were not available in the registration area of the terminal.

In the above method, the terminal may carry the identification information of the network slice to which the terminal was denied access in the registration request message, if the mobility management network element determines that the terminal currently supports the network slice, the identification information of the network slice is added to the updated set of network slices allowed to access and the updated set of network slices allowed to access is sent to the terminal, so that the terminal may use the network slice subsequently. Therefore, the corresponding terminal is enabled to know that the network slice can be accessed currently, and the terminal can use the network slice when the terminal has the service requirement corresponding to the network slice, so that the service capability of the terminal is improved.

In one possible implementation, the terminal receives an updated set of allowed access network slices from the mobility management network element, specifically including: the terminal receives a registration accept message from the mobility management network element, the registration accept message comprising the updated set of allowed access network slices.

In a seventh aspect, the present application provides an apparatus, which may be a communication network element or a chip, where the communication network element may be a mobility management network element or a policy control network element. The device has the functions of implementing the embodiments of the first aspect described above. The functions can be realized by hardware, and can also be realized by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the functions described above.

In an eighth aspect, there is provided an apparatus comprising: a processor and a memory; the memory is configured to store computer-executable instructions that, when executed by the apparatus, cause the apparatus to perform the slice information updating method according to any one of the first aspect.

In a ninth aspect, the present application provides an apparatus, which may be a mobility management network element or a chip. The device has the function of implementing the embodiments of the second aspect described above. The functions can be realized by hardware, and can also be realized by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the functions described above.

In a tenth aspect, there is provided an apparatus comprising: a processor and a memory; the memory is configured to store computer-executable instructions that, when executed by the apparatus, cause the apparatus to perform the slice information updating method according to any one of the second aspects described above.

In an eleventh aspect, the present application provides an apparatus, which may be a policy control network element or a chip. The apparatus has the functions of implementing the embodiments of the third aspect described above. The functions can be realized by hardware, and can also be realized by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the functions described above.

In a twelfth aspect, there is provided an apparatus comprising: a processor and a memory; the memory is configured to store computer-executable instructions that, when executed by the apparatus, cause the apparatus to perform the slice information updating method according to any one of the third aspects described above.

In a thirteenth aspect, the present application provides an apparatus, which may be a network slice selection network element or a chip. The apparatus has functions of implementing the embodiments of the fourth aspect described above. The functions can be realized by hardware, and can also be realized by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the functions described above.

In a fourteenth aspect, there is provided an apparatus comprising: a processor and a memory; the memory is configured to store computer-executable instructions that, when executed by the apparatus, cause the apparatus to perform the slice information updating method according to any one of the fourth aspect described above.

In a fifteenth aspect, the present application provides an apparatus, which may be a mobility management network element or a chip. The apparatus has functions of implementing the embodiments of the fifth aspect described above. The functions can be realized by hardware, and can also be realized by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the functions described above.

In a sixteenth aspect, there is provided an apparatus comprising: a processor and a memory; the memory is configured to store computer-executable instructions that, when executed by the apparatus, cause the apparatus to perform the slice information updating method according to any one of the fifth aspects.

In a seventeenth aspect, the present application provides an apparatus, which may be a terminal or a chip. The apparatus has functions of implementing the embodiments of the sixth aspect described above. The functions can be realized by hardware, and can also be realized by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the functions described above.

In an eighteenth aspect, there is provided an apparatus comprising: a processor and a memory; the memory is configured to store computer-executable instructions that, when executed by the apparatus, cause the apparatus to perform the slice information updating method according to any one of the sixth aspects.

In a nineteenth aspect, the present application also provides a computer readable storage medium having instructions stored therein, which when run on a computer, cause the computer to perform the method of the above aspects.

In a twentieth aspect, the present application also provides a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method of the above aspects.

In a twenty-first aspect, the present application also provides a system comprising the apparatus of the seventh or eighth aspect described above, and the apparatus of the thirteenth or fourteenth aspect.

In a twenty-second aspect, the present application also provides a system comprising the apparatus of the ninth or tenth aspect described above, and the apparatus of the thirteenth or fourteenth aspect.

In a twenty-third aspect, the present application also provides a system comprising the apparatus of the fifteenth or sixteenth aspect described above, and the apparatus of the seventeenth or eighteenth aspect.

Drawings

FIG. 1 is a schematic diagram of one possible network architecture provided herein;

fig. 2 is a schematic diagram of a specific system architecture provided in the present application.

Fig. 3 is a schematic view of a first application scenario provided in the present application;

fig. 4 is a schematic view of a second application scenario provided in the present application;

fig. 5 is a schematic diagram of a slice information updating method provided in the present application;

FIG. 6 is a schematic diagram of another slice information updating method provided in the present application;

FIG. 7 is a schematic diagram of another slice information updating method provided in the present application;

FIG. 8 is a schematic diagram of another slice information updating method provided in the present application;

fig. 9 is a schematic diagram of a third application scenario provided in the present application;

FIG. 10 is a schematic diagram of another slice information updating method provided in the present application;

FIG. 11 is a schematic diagram of another slice information updating method provided in the present application;

FIG. 12 is a schematic view of an apparatus provided herein;

FIG. 13 is a schematic view of another apparatus provided herein;

FIG. 14 is a schematic view of another apparatus provided herein;

FIG. 15 is a schematic view of another apparatus provided herein;

FIG. 16 is a schematic view of another apparatus provided herein;

fig. 17 is a schematic view of another apparatus provided herein.

Detailed Description

For the purpose of making the objects, technical solutions and advantages of the present application more apparent, the present application will be described in further detail with reference to the accompanying drawings. The specific method of operation in the method embodiment may also be applied to the device embodiment or the system embodiment. In the description of the present application, unless otherwise indicated, the meaning of "a plurality" is two or more.

The network architecture and the service scenario described in the embodiments of the present application are for more clearly describing the technical solution of the embodiments of the present application, and do not constitute a limitation on the technical solution provided in the embodiments of the present application, and those skilled in the art can know that, with the evolution of the network architecture and the appearance of the new service scenario, the technical solution provided in the embodiments of the present application is also applicable to similar technical problems.

Fig. 1 is a schematic diagram of one possible network architecture applicable to the present application. The network architecture comprises 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.

The terminal is equipment with a wireless receiving and transmitting function, can be deployed on land, and comprises an indoor or outdoor device, a handheld device or a vehicle-mounted device; can also be deployed on the water surface (such as ships, etc.); but may also be deployed in the air (e.g., on aircraft, balloon, satellite, etc.). The terminal may be a mobile phone (mobile phone), a tablet computer (pad), a computer with a wireless transceiving function, a Virtual Reality (VR) terminal, an augmented reality (augmented reality, AR) terminal, a wireless terminal in industrial control (industrial control), a wireless terminal in unmanned driving (self driving), a wireless terminal in remote medical (remote medical), a wireless terminal in smart grid (smart grid), a wireless terminal in transportation security (transportation safety), a wireless terminal in smart city (smart city), a wireless terminal in smart home (smart home), and the like.

And the mobility management network element is responsible for mobility management of the user, and comprises mobility state management, user temporary identity identification distribution, user authentication and user authorization.

Policy control network elements including subscriber subscription data management functions, policy control functions, charging policy control functions, quality of service (Quality of Service, qoS) control, etc.

The network slice selection network element is responsible for determining network slice examples, selecting a mobility management network element, and the like.

It will be appreciated that the above described functionality may be either a network element in a hardware device, a software function running on dedicated hardware, or a virtualized function instantiated on a platform (e.g., a cloud platform).

It should be noted that the mobility management network element may be referred to as an access and mobility management function (access and mobility management function, AMF) network element in 5G. The policy control network element may be referred to as a policy control function (Policy Control Function, PCF) network element at 5G. Network slice selection network element the network slice selection function (Network Slice Selection Function, NSSF) network element may be referred to as at 5G. Of course, in future communications, such as 6G, the mobility management element may still be referred to as an AMF element or other name, the policy control element may still be referred to as a PCF element or other name, and the network slice selection element may still be referred to as an NSSF element or other name, which is not limited in this application.

For convenience of explanation, 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, and the network slice selection network element is referred to as an NSSF network element. Further, the AMF network element is abbreviated as AMF, the PCF network element is abbreviated as PCF, and the NSSF network element is abbreviated as NSSF. I.e. the AMFs described later in this application may each be replaced by a mobility management element, the PCFs may each be replaced by a policy control element, and the NSSFs may each be replaced by a network slice selection element.

FIG. 2 is a schematic diagram of a specific system architecture based on the system architecture shown in FIG. 1. The system architecture comprises a terminal, wireless access network (radio access network) equipment and a control plane network element of a core network. Wherein, the control plane network element of the core network comprises AMF, PCF and NSSF.

The description of the functions of the terminal, AMF, PCF, and NSSF may refer to the foregoing description, and will not be repeated herein.

RAN equipment is equipment that provides a wireless communication function for a terminal. RAN devices include, for example, but are not limited to: a next generation base station (gnodeB, gNB), evolved node B (eNB), radio network controller (radio network controller, RNC), node B (NB), base station controller (base station controller, BSC), base transceiver station (base transceiver station, BTS), home base station (e.g., home evolved nodeB, or home node B, HNB), baseBand unit (BBU), transmission point (transmitting and receiving point, TRP), transmission point (transmitting point, TP), mobile switching center, and the like in 5G.

In this application, the RAN equipment may be used to forward non-access stratum (Non Access Stratum, NAS) messages for communication between the terminal and the AMF.

The slice information update provided in the present application is specifically described below with reference to fig. 1-2, so as 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-2, and may be applied to other communication systems in the future, such as a 6G system architecture. Also, the names of the various network elements used in the present application may remain the same in future communication systems, but the names may change.

Before describing the solution of the present application in detail, a brief description will be made of the relevant background of the technical problem to be solved by the present application.

Currently, a wide variety of scenarios place different demands on the third generation partnership project (3rd Generation Partnership Project,3GPP) ecosystem, such as billing, policy, security, mobility, etc. The 3GPP emphasizes that the network slices do not affect each other, e.g., the large number of meter reading traffic bursts should not affect normal mobile broadband traffic. To meet the diversity requirements and isolation between slices, relatively independent management and operation between services is required, and custom-made service functions and analysis capabilities are provided. Instances of different types of traffic are deployed on different network slices, and different instances of the same traffic type may also be deployed on different network slices.

When the core network deploys a network slice, a user initially attaches (or registers) to the network, a selection process of the network slice is triggered. The selection process of the slice depends on the subscription data of the user, the local configuration information, the roaming agreement, the policy of the operator, etc. In the process of selecting the network slice, the parameters are comprehensively considered to select the optimal slice type for the terminal.

When a terminal needs to access a certain network slice, the terminal can provide the requested network slice to the core network for the core network to select a network slice instance for the terminal. The network slice requested by the terminal may be represented by requested network slice selection assistance information (requestednetwork slice selection assistance information, requested NSSAI). The Requested NSSAI is made up of one or more individual network slice selection assistance information (single network slice selection assistance information, S-NSSAI), each S-NSSAI being used to identify a network slice type, it being understood that S-NSSAI is used to identify a network slice, or it being understood that S-NSSAI is identification information of a network slice.

Before registering to network, the terminal stores a preconfigured NSSAI locally, wherein the S-NSSAI contained in the configured NSSAI and the S-NSSAI contained in the NSSAI subscribed by the terminal are both S-NSSAI defined by HPLMN. One possible implementation is that the configured nsai contains S-nsai that is a subset or a complete set of S-nsais contained in the nsai for the terminal subscription. For example, the subscribed NSSAI of the terminal is { S-NSSAI1, S-NSSAI2, S-NSSAI3, S-NSSAI4, S-NSSAI5}, then configured NSSAI is a subset or a complete set of { S-NSSAI1, S-NSSAI2, S-NSSAI3, S-NSSAI4, S-NSSAI5 }.

The terminal carries a requested NSSAI at initial registration with the network, wherein the requested NSSAI is a subset or a complete set of S-NSSAI contained in the configured NSSAI. For example, configured NSSAI is { S-NSSAI1, S-NSSAI2, S-NSSAI3, S-NSSAI4}, then requested NSSAI is a subset or a complete set of { S-NSSAI1, S-NSSAI2, S-NSSAI3, S-NSSAI4 }.

After the terminal is registered in the network, a core network element (such as an AMF or NSSF) comprehensively judges according to the subscription data of the terminal, the requested NSSAI of the terminal, the roaming protocol, the local configuration and other information, and selects a network slice set allowed to be accessed for the terminal. The set of network slices allowed to access may be represented by allowed (allowed) nsais, where the allowed nsais contains a subset or a whole set of S-nsais contained in the subscribed nsais of the terminal, or the allowed nsais is a subset or a whole set of S-nsaas contained in the requested nsais. The core network element then sends the allowed nsai to the terminal, e.g. carried in a registration accept message. And when the terminal needs to initiate a service request later, S-NSSAI can be selected from allowed NSSAI to initiate service.

Further, the core network element may send the allowed nsai to the terminal, and also return the reject (reject) nsai and the reason why each S-nsai in the reject nsai to the terminal. The following is an example.

Assume that the subscribed 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.

The following description is made in terms of two application scenarios with reference to fig. 3-4.

It should be noted that, in this application, slices, sometimes referred to as network slices, refer to the same content, have the same meaning, and may be replaced with each other, and are not specifically described later.

Referring to fig. 3, a schematic view of a first application scenario provided in the present application is provided. The network side includes two AMF sets (sets), namely AMF set 1 and AMF set 2. Wherein, the network slice (sliding) supported by any one of the AMFs set 1 is: { slice 1, slice 2}, any AMF in AMF set 2 supports the network slice: { slice 4}, and also includes a slice 3 in the network that is temporarily unsupported by the PLMN, the temporary unsupported reason may be temporary undeployment or temporary shutdown, etc. If the slice 3 is updated later to PLMN support, i.e. updated to available, the slice 3 is assigned AMF set 1.

Wherein, slice 1, slice 2, slice 3, slice 4 can be identified by S-NSSAI1, S-NSSAI2, S-NSSAI3, S-NSSAI4, respectively. Namely, S-NSSAI1 is identification information of slice 1, S-NSSAI2 is identification information of slice 2, S-NSSAI3 is identification information of slice 3, and S-NSSAI4 is identification information of slice 4.

Each network slice corresponds to one or more session management function (Session Management Function, SMF) network elements and one or more user plane function (User Plane Function, UPF) network elements. For example, as shown in fig. 3, slice 1 corresponds to SMF1 and UPF1, slice 2 corresponds to SMF2 and UPF2, slice 3 corresponds to SMF3 and UPF3, and slice 4 corresponds to SMF4 and UPF4.

In the example shown in fig. 3, assuming that an AMF currently accessed (also referred to as an AMF serving a terminal) is one of AMFs set 1 after the terminal is registered with the network, slices that can be used by the AMF serving the terminal are slice 1 and slice 2.

For slice 3, this slice 3 may be referred to as a network slice that is not supported by the PLMN, or as a network slice that is temporarily not supported by the PLMN, or as a network slice that is not currently supported by the PLMN. When the slice 3 is updated to be PLMN supported, then the slice 3 may also be used by the AMF serving the terminal.

For slice 4, if any AMF of AMF set 2 is not included in the current Registration Area (RA) of the terminal (the registration area is the area covered by the AMF serving the terminal), slice 4 may be referred to as a network slice that is not supported by the current registration area of the terminal. It will also be appreciated that the terminal cannot use the slice 4 at the current location. The terminal can use the slice 4 only when it moves within the range that the slice 4 can serve. For example, when the terminal moves to the coverage of a certain AMF in AMF set 2, the terminal can use the slice 4 as long as the terminal registers to the AMF, and can initiate a service flow using the slice 4.

In the example shown in fig. 3 described above, slice 4 is isolated from

slices

1, 2, and 3. It will also be appreciated that when slice 4 is used, the terminal cannot use slice 1, slice 2 or slice 3; when the terminal uses slice 1, slice 2 or slice 3, then slice 4 cannot be used.

In the example shown in fig. 3, although the slice 3 cannot be used in the PLMN, the slice 1, the slice 2, and the slice 3 are all AMF set1, and thus the slice 3 and the slice 1, and the slice 2 are not isolated from each other.

For the scenario shown in fig. 3, since the subscription nsai of the terminal is { S-nsai 1, S-nsai 2, S-nsai 3, S-nsai 4}, and the terminal is currently located in the service range of AMF set1, the requested nsai carried when the terminal registers to the network is { S-nsai 1, S-nsai 2, S-nsai 3, S-nsai 4}, and the slice 3 identified by S-nsai 3 is a network slice not supported by the PLMN, and the slice 4 identified by S-nsai 4 is a network slice not supported by the current registration area of the terminal. The information sent by the core network element (e.g. NSSF or AMF) to the terminal is as follows:

Allowed NSSAI：{S-NSSAI1、S-NSSAI2}；

rejected NSSAI：{S-NSSAI3:1、S-NSSAI4:2}。

the allowed NSSAI includes identification information of a network slice that the core network side allows access, that is, the core network side allows the terminal to access slice 1 and slice 2.

The rejected NSSAI includes identification information of the network slices to which the core network side denies access, i.e. the core network side denies the terminal access to slice 3 and slice 4. And the reason value of rejecting the terminal to access the slice 3 is 1, and the reason value of rejecting the terminal to access the slice 4 is 2. Wherein, the cause value 1 represents: PLMN is not supported, cause value 2 indicates: the current registration area of the terminal is not supported.

Further, the core network element may also send an isolation rule (or called coexistence rule) to the terminal: S-NSSAI1, S-NSSAI2, S-NSSAI3 and S-NSSAI4 are isolated from each other (or said to be non-coexisting).

Of course, the coexistence rule may be preconfigured on the terminal, which is not limited in this application. For example, if a coexistence rule is preconfigured on a terminal, the terminal can learn from the coexistence rule: NSSAI1, S-NSSAI2, S-NSSAI3 and S-NSSAI4 are isolated from each other (or said to be non-coexisting). Then the terminal does not request nsai 1, S-nsai 2, S-nsai 3 and S-nsai 4 simultaneously. Based on the scenario of fig. 3, another possible implementation manner is that the subscription nsai of the terminal is { S-nsai 1, S-nsai 2, S-nsai 3, S-nsai 4} and the terminal is currently located in the service area of AMF set 1, and the requested nsai carried when the terminal registers to the network is { S-nsai 1, S-nsai 2, S-nsai 3}, the information sent to the terminal by the core network element (such as NSSF or AMF) is as follows:

rejected NSSAI：{S-NSSAI3:1}。

The rejected NSSAI includes identification information of the network slice to which the core network side denies access, i.e. the core network side denies the terminal access slice 3. The cause value 1 indicates: the PLMN is not supported.

The foregoing description of specific implementations has been presented only for the purpose of illustration. Of course, in practical application, the implementation is not limited to the above implementation, and may be implemented in other ways.

Referring to fig. 4, a schematic diagram of a second application scenario provided in the present application is provided. The main difference between this application scenario and the application scenario shown in fig. 3 is that: slice 3, which is not supported by the PLMN, is assigned to 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.

When slice 3 is updated to be PLMN supported, then slice 1, slice 2 is isolated from slice 3, slice 4. 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.

For the scenario shown in fig. 4, since the subscription nsai of the terminal is { S-nsai 1, S-nsai 2, S-nsai 3, S-nsai 4} and the terminal is currently located in the service range of AMF set 1, the requested nsai carried when the terminal registers to the network is { S-nsai 1, S-nsai 2, S-nsai 3, S-nsai 4}, and the slice 3 identified by S-nsai 3 is a network slice not supported by the PLMN, and the slice 4 identified by S-nsai 4 is a network slice not supported by the current registration area of the terminal. The information sent by the core network element (e.g. NSSF or AMF) to the terminal is as follows:

allowed NSSAI：{S-NSSAI1、S-NSSAI2}；

rejected NSSAI：{S-NSSAI3:1、S-NSSAI4:2}。

Further, the core network element may also send an isolation rule (or called coexistence rule) to the terminal: S-NSSAI1, S-NSSAI2 and S-NSSAI3, S-NSSAI4 are isolated from each other (or said to be non-coexisting).

The foregoing description has been presented for purposes of illustration only and for the purpose of providing a particular implementation. Of course, in practical application, the implementation is not limited to the above implementation, and may be implemented in other ways.

For the application scenario of fig. 3 and fig. 4, when a network slice (e.g. slice 3 of fig. 3, slice 3 of fig. 4) that is not supported by a PLMN is updated to be supported by the PLMN, or when a network slice (e.g. slice 4 of fig. 3, slice 4 of fig. 4) that is not supported by a current registration area of a terminal is updated to be available (e.g. a new registration area where the terminal is currently located supports use of slice 4 due to movement of the terminal), how the core network side needs to notify the terminal, and which terminals to notify are to be solved by the present invention.

In order to solve the above-mentioned different problems of different scenes, the present application provides various slice information updating methods, which are described in detail below.

As shown in fig. 5, a slice information updating method is provided in the present application. For example, the method can be used to solve the problem of how the core network side informs the terminals, and which terminals to inform, when the slice 3 that is not supported by the PLMN is updated to be supported by the PLMN as shown in fig. 3.

As shown in fig. 5, before step 501, the terminal initiates a registration procedure, and the core network side returns an allowed nsai and a rejected nsai, where the rejected nsai includes identification information (e.g., S-nsai 3) of a slice (e.g., slice 3 in fig. 3) and a reject cause value indicating that the slice is a network slice not supported by the PLMN.

The AMF currently registered by the terminal (i.e., the AMF providing the service to the terminal) is a certain AMF of AMF sets (e.g., AMF set 1 in fig. 3). The information stored on the terminal includes: allowed NSSAI, reject NSSAI (including S-NSSAI 3) and reject cause value. The information stored on the AMF serving the terminal includes: the requested NSSAI of the terminal, the subscribed NSSAI of the terminal.

Here, it should be noted that, for the example shown in fig. 3, the reject nsai returned by the core network side may actually further include identification information of the slice 4 (e.g., S-nsai 4) and a reject cause value, where the reject cause value indicates that the slice is not supported by the network slice for the current registration area of the terminal. For ease of illustration, in the embodiment shown in fig. 5, only the update of slice 3 indicated by S-nsai 3 in the rejected nsai is illustrated as being PLMN-enabled. For a specific implementation method for updating slice 4 indicated by S-nsai 4 in the reject nsai that is available for the current registration area of the terminal, reference is made to the following description of the embodiment shown in fig. 8.

In the network there are one or more terminals as described above. Thus, these terminals that requested the network slice but were rejected should be notified subsequently if the slice that was not supported by the PLMN is updated to PLMN support.

The slice information updating method as shown in fig. 5 includes the steps of:

in step 501, NSSF determines that PLMN supports network slicing.

For example, NSSF may learn from the network management system (operation, administration andmaintenance, OAM) that a PLMN is not originally supported by a network slice, updated to PLMN support. For example, NSSF knows from the network management system that slice 3 of fig. 3 is updated to supported by PLMN unsupported. One possible implementation is that the operator deploys the network resource corresponding to slice 3 at a certain time, which may include, for example, the SMF network element, the UPF network element, etc. corresponding to slice 3. The network management system sends a notification message to NSSF, wherein the notification message comprises identification information and indication information of slice 3: slice 3 is updated from PLMN unsupported to PLMN supported. Thus, NSSF knows from the network management system that slice 3 is not supported by PLMN to be updated to PLMN supported.

In step 502, the NSSF sends a notification message to the AMF, which receives the notification message from the NSSF.

In this step, the NSSF needs to send a notification message to a specific AMF, where the notification message includes the identification information of the network slice determined in the above step 501, and the notification message is used to indicate that the PLMN supports the network slice. Wherein the PLMN did not support network slicing. For example, the notification message includes S-nsai 3 for indicating that the PLMN currently supports slice 3.

The AMFs to which the notification message needs to be sent may be determined according to any of the following methods:

according to the method, NSSF determines the AMF supporting the network slice as the AMF needing to send the notification message according to the slice type supported by the AMF in the PLMN.

For example, referring to fig. 3, using this method, since the AMFs in AMF set 1 all support the slice 3, the AMFs for which NSSF determines that a notification message needs to be sent include the AMFs in AMF set 1, i.e., NSSF determines that a notification message needs to be sent to the AMFs (e.g., all AMFs) in AMF set 1. Of course, as an implementation, it may also be determined that the AMF that needs to send the notification message includes a part of the AMFs in AMF set 1.

Of course, if there are other AMF supported slice types including the slice 3, the AMF of the NSSF determined to send the notification message also includes the AMFs.

In a second method, the NSSF determines that the AMF subscribed to the network slice with the NSSF is the AMF that needs to send the notification message.

Wherein, the AMF subscribing to the NSSF refers to subscribing to the NSSF: when the PLMN supports the network slice, the NSSF informs the AMF. The network slice is a network slice that the PLMN has not supported, but has been updated to be supported. For example slice 3 of fig. 3.

In one possible implementation, when the AMF serving the terminal determines, in the registration procedure of the terminal, that the core network refuses the request of the terminal for the network slice not supported by a certain PLMN, the AMF subscribes to the NSSF: when the PLMN supports the network slice, the NSSF informs the AMF. For example, the AMF serving the terminal may be a subscription to NSSF prior to step 501. For example, the AMF serving the terminal sends a subscription request message to the NSSF, where the subscription request message includes an identification of the AMF and identification information of a network slice, where the network slice is a network slice that the core network refuses the terminal to request to use. Alternatively, the AMF providing the service to the terminal invokes the subscription service by transmitting identification information of the AMF and identification information of the network slice to the NSSF: when the PLMN supports the network slice, the NSSF informs the AMF. When the NSSF determines that the network slice update not supported by the PLMN is supported, then the AMF which sent the subscription request message to the NSSF or called the subscription service is determined to be the AMF which needs to send the notification message.

By either method one or method two described above, the NSSF may determine the AMF that needs to send the notification message. For example, if the first method is adopted, the determined AMF that needs to send the notification message includes: AMF supporting the above network slice. If the second method is adopted, the determined AMF needing to send the notification message comprises the following steps: AMFs that have subscribed to NSSF for the status of the network slice.

The amf informs the terminal that the PLMN supports network slicing, step 503.

The AMF in step 503 is the AMF that receives the notification message in step 502.

The terminals that the AMF needs to notify include terminals that have requested that the network slice failed and signed up for the network slice. For example, the AMF may determine the terminal that needs to be notified according to the context of the terminal stored by the AMF.

For example, if a terminal carries the identification information of the network slice in the requested nsai, and the nsai subscribed to the terminal includes the identification information of the network slice, and the PLMN does not support the terminal when requesting to use the network slice, the core network refuses the request of the terminal for the network slice. Thus, when the network slice is updated from PLMN-unsupported to PLMN-supported, the AMF serving the terminal needs to inform the terminal that the PLMN supports the network slice.

As a specific implementation, the AMF may notify the terminal by:

the AMF adds the identification information of the network slice to the set of allowed access network slices of the terminal, i.e. allowed nsais, and then sends updated allowed nsais to the terminal.

For example, for the example shown in fig. 3. The allowed NSSAI previously sent to the terminal by AMF is { S-NSSAI1, S-NSSAI2}, and the reject NSSAI sent to the terminal includes S-NSSAI3. Then when the AMF needs to inform the terminal that slice 3 identified by S-nsai 3 has been updated to be available, an updated allowed nsai may be generated, including { S-nsai 1, S-nsai 2, S-nsai 3}, and then the updated allowed nsai is sent to the terminal. For example, the updated allowed nsai may be carried in a configuration update message (configuration update message) of the terminal and sent to the terminal, and after receiving the configuration update message, the terminal obtains the updated allowed nsai from the configuration update message, so that it may be known that the slice 3 is already supported by the PLMN and is not supported by the PLMN, and thus the service request flow may be initiated later using the slice 3.

As one implementation, the AMF may immediately send the updated allowed nsai to the terminal. For example, the AMF may send the updated allowed nsai to the corresponding terminal after determining the updated allowed nsai according to the local configuration information. Optionally, the AMF sends the updated allowed nsai to the terminal, and also sends 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 step 502.

As another implementation, the AMF may also send the updated allowed nsai to the terminal not immediately. For example, the AMF stores the updated allowed nsai according to the local configuration information, and then waits for the terminal to actively initiate a registration update procedure, and sends the updated allowed nsai to the terminal in the registration update procedure.

In the above embodiment, when the NSSF determines that the network slice that is not supported by the PLMN is updated to be supported, the AMF is determined first, then a notification message is sent to the determined AMF, where the notification message is used to instruct the PLMN to support the network slice, and then the AMF that receives the notification message notifies the terminal registered in the AMF and that has requested the network slice but is rejected: the PLMN currently supports the network slice. Therefore, when the network slice which is not supported by the PLMN is updated to be supported by the PLMN, the corresponding terminal is notified through the corresponding AMF, and when the terminal has the service requirement corresponding to the network slice, the network slice can be used, so that the service capability of the terminal is improved.

As shown in fig. 6, another slice information updating method is provided in the present application. For example, the method can be used to solve the problem of how the core network side informs the terminals, and which terminals to inform, when the slice 3 that is not supported by the PLMN is updated to be supported by the PLMN as shown in fig. 3.

As shown in fig. 6, before step 601, the terminal initiates a registration procedure, and the core network side returns an allowed nsai and a rejected nsai, where the rejected nsai includes identification information (e.g., S-nsai 3) of a slice (e.g., slice 3 in fig. 3) and a reject cause value indicating that the slice is a network slice not supported by the PLMN.

The AMF currently registered by the terminal (i.e., the AMF providing the service to the terminal) is a certain AMF of AMF sets (e.g., AMF set1 in fig. 3). The information stored on the terminal includes: allowed NSSAI, reject NSSAI (including S-NSSAI 3) and reject cause value. The information stored on the AMF serving the terminal includes: the requested NSSAI of the terminal, the subscribed NSSAI of the terminal.

Here, it should be noted that, for the example shown in fig. 3, the reject nsai returned by the core network side may actually further include identification information of the slice 4 (e.g., S-nsai 4) and a reject cause value, where the reject cause value indicates that the slice is not supported by the network slice for the current registration area of the terminal. For ease of illustration, in the embodiment shown in fig. 6, only the update of slice 3 indicated by S-nsai 3 in the rejected nsai is illustrated as being PLMN-enabled. For a specific implementation method for updating slice 4 indicated by S-nsai 4 in the reject nsai that is available for the current registration area of the terminal, reference is made to the following description of the embodiment shown in fig. 8.

The slice information updating method as shown in fig. 6 includes the steps of:

in step 601, NSSF determines that PLMN supports network slicing.

The specific implementation of this step 601 is the same as that of step 501, and reference is made to the foregoing description.

Step 602, the NSSF sends a notification message to the PCF, which receives the notification message from the NSSF.

In this step, the NSSF needs to send a notification message to a specific PCF, where the notification message includes the identification information of the network slice determined in step 601, and the notification message is used to instruct the PLMN to support the network slice. Wherein the PLMN did not support network slicing. For example, the notification message includes S-nsai 3 for indicating PLMN support slice 3.

As one implementation, the PCF that needs to send the notification message may be determined according to the following: the NSSF determines the PCFs that have subscribed to the network slice above to the NSSF as PCFs that need to send notification messages, i.e., to which PCFs.

If the PCF that sends the notification message is determined by using this implementation, the method further includes, before step 601, the following steps:

Step A, the AMF sends a notification message to the PCF, which receives the notification message from the AMF.

In one possible implementation, when the AMF serving the terminal determines that the core network refuses the request of the terminal for the network slice not supported by a PLMN in the registration procedure of the terminal, the AMF sends a notification message to the PCF to which the AMF belongs, where the notification message is used to trigger the PCF to subscribe to the NSSF for the state 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. Then PCF stores the association relation between the identification information of the terminal, the identification information of AMF and the identification information of the network slice.

Step B, the PCF subscribes to NSSF: when the PLMN supports the network slice, the NSSF informs the PCF.

As an implementation manner, 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 a network slice, where the network slice is a network slice that the core network refuses the terminal to use. Alternatively, the PCF invokes the subscription service by sending identification information of the PCF and identification information of the network slice to the NSSF: when the PLMN supports the network slice, the NSSF informs the PCF. When NSSF determines that the network slice update not supported by PLMN is supported, then PCF which sent subscription request message to NSSF or call subscription service is determined as PCF which needs to send notification message.

Step 603, the pcf informs the terminal PLMN to support network slicing.

The PCF in step 603 is the PCF that receives the notification message from the NSSF in step 602.

Terminals that the PCF needs to notify include terminals that have requested that the network slice failed and signed up for the network slice.

As one implementation, the PCF may send, through the AMF, indication information to the terminal, the indication information being used to indicate that the PLMN supports network slicing. I.e. step 603 may be replaced by the following steps 603 a-603 b:

step 603a, the PCF sends an update message to the AMF, which receives the update message from the PCF.

The update message includes indication information for indicating that the PLMN supports network slicing and identification information of the terminal. The PLMN did not support the network slice.

The PCF firstly determines the terminal needing 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 executing the above steps a-B, when the PCF receives the notification message of the AMF, where the notification message includes the identification information of the terminal, the identification information of the AMF, and the identification information of the network slice, the PCF may store the association relationship between the identification information of the terminal, the identification information of the AMF, and the identification information of the network slice. The PCF may thus determine, based on the stored association, the identification information of the terminal that needs to be included in the update message of step 603a, and to which AMFs the update message needs to be sent by step 603 a.

For example, after performing steps a-B multiple times as described above, the PCF stores information as shown in table 1:

TABLE 1

In table 1, the terminal 1 and the terminal 2 are registered in the AMF1, the terminal 3 is registered in the AMF2, and both the AMF1 and the AMF2 are AMFs in the AMF set1 shown in fig. 3. Terminal 1-terminal 3 in Table 1 is the terminal recorded by the PCF that requested slice 3 identified by S-NSSAI3 and was rejected.

For example, the above steps a to B are performed three times. Assuming that both AMF1 and AMF2 are managed by PCF1, then:

the first time:

step A, AMF1 sends notification message to PCF1, notification message includes: (terminal 1, AMF1, S-NSSAI 3).

Step B, the PCF subscribes to NSSF: when the PLMN supports slice 3 identified by the S-NSSAI3, the NSSF informs PCF1.

The PCF1 also sends the identification information of the PCF1 and the S-NSSAI3 to the NSSF when subscribing to the NSSF.

Second time:

step A, AMF1 sends notification message to PCF1, notification message includes: (terminal 2, AMF1, S-NSSAI 3).

Third time:

Step A, AMF2 sends notification message to PCF1, notification message includes: (terminal 3, AMF2, S-NSSAI 3).

Of course, since the step B of the operations performed three times is the same, in a specific implementation, the step B may be performed only at the first time, and not performed at the second and third times.

In step 603b, the amf informs the terminal PLMN to support network slicing, and the terminal is a terminal that requested network slicing failed and signed up for network slicing.

The AMF is the AMF that receives the update message from the PCF in step 603a, and the terminal is the terminal indicated by the identification information of the terminal carried in the update message in step 603 a.

Taking table 1 as an example, the step 603b needs to be performed three times:

the first time: AMF1 notifies terminal 1: the PLMN supports slice 3 identified by S-NSSAI 3.

Second time: AMF1 notifies terminal 2: the PLMN supports slice 3 identified by S-NSSAI 3.

Third time: AMF2 notifies terminal 3: the PLMN supports slice 3 identified by S-NSSAI 3.

As a specific implementation manner, the AMF may notify the terminal by performing the first, second, and third times in the following manners:

the AMF adds the identification information of the network slice to the set of allowed access network slices of the terminal, i.e. allowed nsais, and then sends updated allowed nsais to the terminal. For specific implementation details of this implementation, reference may be made to the related description in step 503 in the embodiment shown in fig. 5, which is not described here again.

In the above embodiment, when the NSSF determines that the network slice that is not supported by the PLMN is updated to be supported, the PCF is determined first, and then a notification message is sent to the determined PCF, where the notification message is used to instruct the PLMN to support the network slice, and then the PCF that receives the notification 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 which is not supported by the PLMN is updated to be supported by the PLMN, the corresponding terminal is notified by the corresponding PCF, and when the terminal has the service requirement corresponding to the network slice, the network slice can be used, so that the service capability of the terminal is improved.

As shown in fig. 7, another slice information updating method is provided in the present application. For example, the method can be used to solve the problem of how the core network side informs the terminals, and which terminals to inform, when the slice 3 that is not supported by the PLMN is updated to be supported by the PLMN as shown in fig. 4.

In the scenario shown in fig. 4, the quarantine rule (or coexistence rule) is: the separation between slice 1 and slice 2 and slice 3 and slice 4 is otherwise referred to as non-coexistence. Alternatively, it is understood that the AMFs to which the slice 1 and the slice 2 belong (i.e., the AMFs in the AMF set 1) do not coexist with the AMFs to which the slice 3 and the slice 4 belong (i.e., the AMFs in the AMF set 2). The coexistence rule may be that the network returns the coexistence rule to the terminal when the terminal registers to the network, or that the coexistence rule is configured on the terminal.

As shown in fig. 7, before step 701, the terminal initiates a registration procedure, and the core network side returns an allowed nsai and a rejected nsai, where the rejected nsai includes identification information (e.g., S-nsai 3) of a slice (e.g., slice 3) and a reject cause value indicating that the slice is a network slice not supported by the PLMN. Optionally, a coexistence rule is also sent to the terminal, wherein the coexistence rule is: S-NSSAI1, S-NSSAI2 and S-NSSAI3, S-NSSAI4 do not coexist (i.e., slice 1, slice 2 does not coexist with slice 3, slice 4).

The AMF currently registered by the terminal (i.e., the AMF providing the service to the terminal) is a certain AMF of AMF sets (e.g., AMF set1 in fig. 4). The information stored on the terminal includes: allowed NSSAI, reject NSSAI (including S-NSSAI 3) and reject cause value, coexistence rules. The information stored on the AMF serving the terminal includes: the requested NSSAI of the terminal, the subscribed NSSAI of the terminal.

Here, it should be noted that, for the example shown in fig. 4, the reject nsai returned by the core network side may actually further include identification information of the slice 4 (e.g., S-nsai 4) and a reject cause value, where the reject cause value indicates that the slice is not supported by the network slice for the current registration area of the terminal. For ease of illustration, in the embodiment shown in fig. 7, only the update of slice 3 indicated by S-nsai 3 in the rejected nsai is illustrated as being PLMN-enabled. For a specific implementation method for updating slice 4 indicated by S-nsai 4 in the reject nsai that is available for the current registration area of the terminal, reference is made to the following description of the embodiment shown in fig. 8.

The slice information updating method as shown in fig. 7 includes the steps of:

in step 701, NSSF determines that PLMN supports network slicing.

The specific implementation of this step 701 is the same as that of step 601, and reference is made to the foregoing description.

Step 702, the NSSF sends a notification message to the PCF, which receives the notification message from the NSSF.

The specific implementation of this step 702 is the same as that of step 602, and reference is made to the foregoing description.

In step 703, the PCF sends an update message to the AMF, which receives the update message from the PCF.

The update message may be, for example, a policy update message. The update message includes indication information for indicating that the PLMN supports network slicing and identification information of the terminal. The PLMN did not support the network slice.

The specific implementation of this step 703 is the same as that of step 603a described above, and reference is made to the foregoing description.

In step 704, the AMF sends a NAS message to the terminal, and the terminal receives the NAS message from the AMF.

The terminal is indicated by the identification information of the terminal carried in the update message in step 703.

The NAS message includes identification information of a network slice that was not supported by the PLMN to be updated to be supported by the PLMN. Optionally, the NAS message further includes indication information, which indicates that the network slice is available, or understood that the indication information indicates that the network slice has been updated to PLMN support.

If table 1 is taken as an example, the step 703 needs to be performed three times:

For example, the AMF may notify the terminal by performing the first, second, and third times in the following manner: the AMF sends a NAS message to the terminal, where the NAS message includes indication information, where the indication information is used to indicate that the PLMN supports slice 3 identified by S-nsai 3.

The main difference between this step 704 and the above step 603b is that: the AMF serving the terminal does not need to send an updated allowed nsai to the terminal, but only needs to inform the terminal that the network slice has been updated to PLMN support, because the AMF serving the terminal and the AMF to which the network slice belongs are isolated from each other (i.e. the AMF1 and AMF2 are isolated from each other from the AMF to which the slice 3 belongs), and thus the AMF serving the terminal does not have the capability of supporting the network slice. Taking the example of table 1 as an example, since AMF1 and AMF2 both belong to AMF set1, only slice 1 and slice 2 are supported, whereas in step 703 AMF1 needs to notify terminal 1 and terminal 2: slice 3 identified by S-nsai 3 has been updated to PLMN support, and AMF1 is unable to send updated allowed nsai to terminal 1 and terminal 2 because AMF1 does not support slice 3: { S-NSSAI1, S-NSSAI2, S-NSSAI3}, but only one indication message can be sent to terminal 1 and terminal 2, indicating that the slice 3 identified by S-NSSAI3 has been updated to be PLMN supported, so the information stored by terminal 1 and terminal 2 is:

allowed NSSAI：{S-NSSAI1、S-NSSAI2}；

Slice 3 identified by S-NSSAI3 is available.

Similarly, the AMF2 needs to send instruction information to the terminal 3, and thus the information stored in the terminal 3 is:

allowed NSSAI：{S-NSSAI1、S-NSSAI2}；

slice 3 identified by S-NSSAI3 is available.

In the above embodiment, when the NSSF determines that the network slice that is not supported by the PLMN is updated to be supported, the PCF determines the PCF first, and then sends a notification message to the PCF that is determined to indicate that the PLMN supports the network slice, then the PCF that receives the notification message sends an update message to the AMF, where the update message includes identification information and indication information of the terminal, and then the AMF sends the indication information to the terminal indicated by the notification message, so as to notify the terminal that the network slice is updated to be supported by the PLMN, and further the terminal can use the network slice when there is a service requirement corresponding to the network slice, so as to help to promote the service capability of the terminal.

As shown in fig. 8, another slice information updating method is provided in the present application. For example, the method can be used to solve the problem of how the core network side notifies the terminals and which terminals to notify when a slice 4 not supported by the current registration area of the terminal as shown in fig. 3 or a slice 4 not supported by the current registration area of the terminal as shown in fig. 4 is available.

The following will take the scene shown in fig. 3 as an example.

As shown in fig. 8, before step 801, the terminal initiates a registration procedure, and the core network side returns an allowed nsai and a rejected nsai, where the rejected nsai includes identification information (e.g., S-nsai 4) of a slice (e.g., slice 4 in fig. 3) and a reject cause value indicating that the slice is a network slice not supported by the current registration area of the terminal. Optionally, a coexistence rule is also sent to the terminal, wherein the coexistence rule is: S-NSSAI1, S-NSSAI2, S-NSSAI3 and S-NSSAI4 do not coexist (i.e., slice 1, slice 2, slice 3 and slice 4 do not coexist).

The AMF currently registered by the terminal (i.e., the AMF providing the service to the terminal) is a certain AMF of AMF sets (e.g., AMF set1 in fig. 3). The information stored on the terminal includes: allowed NSSAI, reject NSSAI (including S-NSSAI 4) and reject cause value, coexistence rules. The information stored on the AMF serving the terminal includes: the requested NSSAI of the terminal, the subscribed NSSAI of the terminal.

Here, it should be noted that, for the example shown in fig. 3 or fig. 4, the reject nsai returned by the core network side may actually further include identification information of the slice 3 (e.g., S-nsai 3) and a reject cause value indicating that the slice is a network slice not supported by the PLMN. For ease of illustration, the embodiment shown in FIG. 8 is described only for when slice 4 indicated by S-NSSAI4 in the rejected NSSAI is updated as available. For a specific implementation of the update of slice 3 indicated by S-nsai 3 in the reject nsai for PLMN support, reference is made to the following description of the embodiments shown in fig. 5-7.

In the network there are one or more terminals as described above. Thus, subsequently, if a slice update is available that is not supported by the terminal's current registration area, those terminals that have requested the network slice but are rejected should be notified.

The slice information updating method as shown in fig. 8 includes the steps of:

in step 801, the AMF sends identification information of a terminal and identification information of a network slice to the PCF, and the PCF receives the identification information of the terminal and the identification information of the network slice from the AMF.

In a specific implementation, when an AMF providing a service for a terminal determines that a core network refuses a request of the terminal for a network slice which is not supported by a current registration area of a certain terminal in a registration flow of the terminal, the AMF sends a notification message to a PCF to which the AMF belongs, wherein the notification message comprises identification information of the terminal and identification information of the network slice. The PCF then stores the association of the identification information of the terminal and the identification information of the network slice.

As an example, it is assumed that the current registration area of the terminal 1 includes AMF1, but does not include AMF2. The AMF1 is the AMF in AMF set1, and then the slice supported by AMF1 includes slice 1, slice 2, and slice 3 (assuming slice 3 has been updated to be PLMN supported). The AMF2 is the AMF in AMF set2, and then the slice supported by the AMF2 includes slice 4.

Since the registration area where the terminal 1 is currently located does not include AMF2, 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.

Therefore, in the registration process of the terminal 1, the AMF1 may determine that the slice 4 is a slice that is not supported by the current registration area of the terminal 1, and then the AMF1 sends the identification information of the terminal 1 and the S-nsai 4 to the PCF, and then the PCF stores the association relationship between the identification information of the terminal 1 and the S-nsai 4.

In step 802, the pcf obtains a service area corresponding to the network slice from the NSSF.

As a specific implementation, the PCF may send a request message to the NSSF for requesting a service area corresponding to the network slice. Wherein the service area may be a cell list consisting of one or more cells.

Still further to the above example, the PCF sends a request message to the NSSF that includes S-nsai 4, and the NSSF returns the serving area corresponding to S-nsai 4 to the PCF.

Step 803, the pcf knows that the terminal moves to the service area.

As an implementation manner, the PCF may learn that the terminal moves to the service area by:

PCF subscribes to AMF: when the location of the terminal is updated, the AMF sends the updated location of the terminal to the PCF. For example, the PCF may send a subscription request message to the AMF, where the subscription request message carries an identifier of the terminal, where the subscription request message is used to subscribe the AMF to the location of the terminal. Alternatively, the PCF invokes the subscription service by sending the AMF an identification of the terminal: when the location of the terminal is updated, the AMF sends the updated location of the terminal to the PCF.

When the terminal moves and initiates a registration update flow, the current location information of the terminal can be carried in a registration request message in the registration update flow, and the AMF can acquire the current location information of the terminal. Because the AMF stores the location information carried in the last registration update procedure of the terminal, 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 last location information, the AMF reports the latest location of the terminal to the PCF.

Then, the PCF judges whether the current position of the terminal is in the service area of the slice corresponding to the network slice according to the obtained current position of the terminal and the service area of the slice corresponding to the network slice, and if so, the PCF knows that the terminal moves to the service area.

Still further to the above example, if the PCF determines that the current location of the terminal 1 is located in the service area corresponding to S-nsai 4, it is determined that the terminal 1 moves to the service area corresponding to S-nsai 4.

Step 804, the pcf informs the terminal that network slices are available.

As a specific implementation, the PCF may send, to the terminal, indication information through the AMF registered by the terminal, where the indication information is used to indicate that the network slice is available. For example, the PCF sends an update message to the AMF registered by the terminal, where the update message carries identification information and indication information of the terminal, and optionally, the update message also carries identification information of the network slice, where the network slice is updated from unavailable to currently available to the terminal, and the indication information is used to indicate that the network slice is available. And the AMF sends NAS information to the terminal, wherein the NAS information comprises the indication information, and if the PCF carries the identification information of the network slice in the AMF sending update information registered by the terminal, the AMF also comprises the identification information of the network slice in the NAS information and sends the NAS information 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, and the specific implementation manner of the AMF sending the NAS message to the terminal is the same as the foregoing step 704, and the foregoing description may be referred to.

Still referring to the above example, after determining that the terminal 1 moves to the service area corresponding to the S-nsai 4, the PCF sends an update message to the AMF1, where the update message includes identification information of the terminal 1 and indication information, where the indication information is used to indicate that the slice 4 identified by the S-nsai 4 is currently available. The AMF1 then sends a NAS message to the terminal 1, the NAS message comprising S-nsai 4. Optionally, the NAS message further includes the indication information. When the terminal 1 acquires the NAS message, it can be determined that the terminal can use the slice 4 at the current location, so that the service flow can be initiated by using the slice 4 later. For example, re-register with AMF2 and then initiate a business process using slice 4.

In the above method, when the terminal moves to the service area corresponding to the network slice, the PCF may notify the terminal: the network slice is currently available, wherein the network slice is one that the terminal requested but was rejected and was not supported by the registration area in which it was located before the mobile. When the network slice which is not supported by the terminal registration area is updated to be available, the corresponding terminal can be timely notified, and the terminal can use the network slice when the terminal needs the service corresponding to the network slice, so that the service capability of the terminal is improved.

The embodiments shown in fig. 5 to 8 may be implemented as separate embodiments or may be implemented in combination with each other. For example, the embodiments shown in fig. 5-7 may be implemented in combination with embodiment 8, respectively. For another example, the embodiments shown in fig. 5-6 may be implemented in combination with the embodiment shown in fig. 7, respectively. As another example, the embodiments shown in fig. 5, 7, 8 are implemented in combination. As another example, the embodiments shown in fig. 6, 7, 8 are implemented in combination. The specific combination modes of the embodiments are not limited in this application, and can be combined according to actual requirements.

Note that, in the above embodiments, the notification message, the update message, the NAS message, the subscription request message, the configuration update message, and the like are just one name, and the name does not limit the message itself. In the 5G network and other networks in the future, the notification message, the update message, the NAS message, the subscription request message, and the configuration update message may be other names, which are not specifically limited in the embodiments of the present application.

Accordingly, the present invention discloses a slice information updating method, comprising:

the communication network element receives a notification message from a network slice selection network element, wherein the notification message comprises identification information of a network slice, and the notification message is used for indicating a Public Land Mobile Network (PLMN) to support the network slice;

The communication network element informs a 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 up for the network slice.

Wherein the communication network element may be a mobility management network element or a policy control network element.

As an implementation manner, the communication network element determines the terminal according to the terminal context.

In one possible implementation, if the communication network element is a mobility management network element; the method further comprises: the mobility management network element adds the identification information of the network slice into a network slice set of the terminal which is allowed to be accessed;

the communication network element informing the terminal that the PLMN supports the network slice comprises: the mobility management network element sends the updated set of allowed access network slices to the terminal. Optionally, the communication network element notifies a terminal that the PLMN supports the network slice, and further includes: and the mobility management network element sends indication information to the terminal, wherein the indication information is used for indicating the PLMN to support the network slice.

In another possible implementation, if the communication network element is a policy control network element; the method further comprises: the policy control network element determines a mobility management network element registered by the terminal;

The communication network element informing the terminal that the PLMN supports the network slice comprises: and the policy control network element sends indication information to the terminal through the mobility management network element, wherein the indication information is used for indicating the PLMN to support the network slice.

In the slice information updating method, for example, if the communication network element is a mobility management network element, the operation of the mobility management network element may refer to the operation of the AMF in fig. 5 and the above related text descriptions, which are not repeated here. For example, if the communication network element is a policy control network element, the operation of the policy control network element may refer to the operation of the PCF in fig. 6 and the above description of related text, which are not repeated here.

The invention also provides a slice information updating method, which comprises the following steps:

the method comprises the steps that a mobility management network element receives an update message from a strategy control network element, wherein the update message comprises indication information and identification information of a terminal, and the indication information is used for indicating a Public Land Mobile Network (PLMN) to support network slicing;

the mobility management network element informs a 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.

In one possible implementation manner, the method further includes: the mobility management network element adds the identification information of the network slice into a network slice set of the terminal which is allowed to be accessed;

the mobility management network element informing the terminal that the PLMN supports the network slice comprises: the mobility management network element sends the updated set of allowed access network slices to the terminal.

In a possible implementation manner, the mobility management network element informs a terminal that the PLMN supports the network slice, and further includes: and the mobility management network element sends indication information to the terminal, wherein the indication information is used for indicating the PLMN to support the network slice.

In a possible implementation manner, the mobility management network element informs a terminal that the PLMN supports the network slice, including: and the mobile management network element sends NAS information to the terminal, wherein the NAS information comprises the indication information.

In the slice information updating method, for example, the operation of the mobility management network element may refer to the operation of the AMF in fig. 7 and the above related text descriptions, which are not repeated here.

The method comprises the steps that a policy control network element receives identification information of a terminal from a mobility management network element and identification information of a network slice, wherein the network slice is not supported by a current registration area of the terminal;

the strategy control network element selects a network element from a network slice to obtain a service area corresponding to the network slice;

and if the strategy control network element knows that the terminal moves to the service area, notifying the terminal that the network slice is available.

In one possible implementation, the policy control network element informs the terminal that the network slice is currently available, including: and the policy control network element sends indication information to the terminal through the mobility management network element, wherein the indication information is used for indicating that the network slice is available.

In the slice information updating method, for example, the operation of the policy control network element may refer to the operation of the PCF in fig. 8 and the above related text descriptions, which are not repeated here.

the network slice selection network element determines that the public land mobile network PLMN supports network slice;

the network slice selection network element sends a notification message to a communication network element, wherein the notification message comprises identification information of the network slice, and the notification message is used for indicating the PLMN to support the network slice. Optionally, the communication network element is a policy control network element or a mobility management network element.

In one possible implementation manner, the method further includes: the network slice selection network element receives a subscription from the communication network element: and when the PLMN supports the network slice, the network slice selection network element informs the communication network element.

In one possible implementation manner, the method further includes: and the network slice selection network element determines the mobility management network element supporting the network slice as the communication network element according to the slice type supported by the mobility management network element in the PLMN.

In the slice information updating method, for example, the operation of selecting a network element by a network slice may refer to the NSSF operation in fig. 5-7 and the above related text descriptions, which are not repeated here.

Referring to fig. 9, a third application scenario schematic diagram provided in the present application is provided. The network side comprises two sets (sets) of AMFs, AMF set 1 and AMF set 2, respectively. Wherein, the network slice (sliding) supported by any one of the AMFs set 1 is: { slice 1, slice 2, slice 3}, the service area of slice 1 is service area 1, the service area of slice 2 is service area 2, and the service area of slice 3 is service area 3. The network slices supported by any one of the AMFs set 2 are: { 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.

Wherein, slice 1, slice 2, slice 3, slice 4, slice 5 in the above example may be identified by S-NSSAI1, S-NSSAI2, S-NSSAI3, S-NSSAI4, S-NSSAI5, respectively. Namely, S-NSSAI1 is identification information of slice 1, S-NSSAI2 is identification information of slice 2, S-NSSAI3 is identification information of slice 3, S-NSSAI4 is identification information of slice 4, and S-NSSAI5 is identification information of slice 5.

Each network slice corresponds to one or more SMFs and one or more UPFs. For example, as shown in fig. 9, 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, and slice 5 corresponds to SMF5 and UPF5.

Also, an isolation relationship (alternatively referred to as a mutual exclusion relationship or a non-coexistence relationship) is between a slice supported by any one of AMFs Set 1 and a slice supported by any one of AMFs Set2, and the isolation relationship may be understood as that two different slices cannot be accessed simultaneously or simultaneously. Thus, the terminal can only access a slice of

slices

1, 2, 3, or can only access a slice of slices 4, 5, but cannot access both a slice of

slices

1, 2, 3 and a slice of slices 4, 5.

The service area of a slice refers to a range in which the slice can provide services, i.e., the slice can provide services to terminals within the service range of the slice, or terminals within the service area of the slice can use the services provided by the slice, and terminals outside the service area of the slice cannot use the services provided by the slice. As one implementation, the service Area may include one or more Tracking Areas (TAs), and one TA may be uniquely identified using a Tracking Area identification (Tracking Area Identity, TAI). Thus, it is also understood that one slice corresponds to one service area, or that one slice corresponds to one or more TAs.

As an example, in the embodiment shown in fig. 9, the service areas of slice 1 to 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.

In this example, the service areas of any two slices include overlapping TAs. For example, the overlapping TA included in the service area of slice 1 and the service area of slice 2 are TA2, TA3, … …, TA11.

Further, the service status in any TA within the service area of any slice can be classified into "available status" and "limited status". If a slice can provide service for a terminal in a certain TA, the service state of the slice in the TA is "available state". If a slice cannot provide service for a terminal within a certain TA, the service state of the slice within the TA is "restricted state". The "restricted state" may also be referred to as a "temporary unavailable state".

It should be noted that, a slice may be transitionable between two service states within a certain TA, such as from "available state" to "limited state" or from "limited state" to "available state".

It should be noted that, if the service state of a slice in one TA is "available state", the TA may also be referred to as a TA that makes the slice in the "available state", or a TA that is available to the slice. If the service state of a slice within a TA is "restricted," the TA may also be referred to as a TA that places the slice in the "restricted state," or as a TA that is not available to the slice.

In one possible implementation, the NSSF may determine the service status of a slice currently within a certain TA or certain TAs based on the load of the slice. For example, for a slice, if the number of users accessing the slice is large, such that the load of the slice exceeds a preset threshold, the NSSF may change the service state of the slice in a certain TA or certain TAs from an "available state" to a "limited state". For another example, for a slice, if the number of users accessing the slice is small, such that the load of the slice is below a preset threshold, the NSSF may change the service state of the slice in one or more TAs from a "limited state" to an "available state".

For the application scenario shown in fig. 9, when the service state of a slice in a certain TA or certain TAs is "limited state", the terminal in the TA requests to access the slice and is rejected, and when the service state of the slice in the TA is subsequently changed from "limited state" to "available state", how the network side notifies the terminal is the problem to be solved by the application.

It should be noted that, a terminal registered to a network may use a slice, that means that any TA included in a registration area of the terminal satisfies that the slice is in an "available state", in other words, a TA set included in the registration area of the terminal is a subset of a set formed by TAs that make the slice be in the "available state". For example, if the registration area of the terminal is ra= { TA4, TA5, TA6}, for the slice 3, if the slice 3 is in the "available state" from TA3 to TA13, the terminal may use the slice 3 because the set formed from TA4 to TA6 is a subset of the set formed from TA3 to TA 13. For another example, if the registration area of the terminal is ra= { TA4, TA5, TA6}, for the slice 3, if the slice 3 is available in all of TA5 to TA13 and unavailable in TA3 and TA4, the terminal cannot use the slice 3 because the set formed by TA4 to TA6 is not a subset of the set formed by TA5 to TA 13.

As an example, two different implementation methods are given below, as shown in fig. 10 and 11, respectively. The following description will be given respectively.

It should be noted that, in the embodiments shown in fig. 10 and fig. 11, the terminal is always located in the registration area of the terminal, that is, the terminal is not always moved out of the registration area of the terminal. For a specific implementation procedure of the method for updating slice information after the terminal has moved out of the registration area, reference may be made to the related description of the prior art.

As shown in fig. 10, another slice information updating method is provided in the present application. The method comprises the following steps:

in step 1001, the amf sends a request to the NSSF. Accordingly, the NSSF may receive the request.

The request may be, for example, an nssf_nssaiaivailityupdate request, or may be a request message.

The request is used to report identification information of the AMF-supported slices to the NSSF, and a service area corresponding to each slice (a service area may include one or more TAs).

For example, for each AMF in AMF set 1 shown in fig. 9, the information reported to NSSF includes:

S-NSSAI1，TAI1-TAI11；

S-NSSAI2，TAI2-TAI12；

S-NSSAI3，TAI3-TAI13。

for each AMF in AMF set 2 shown in fig. 9, the information reported to NSSF includes:

S-NSSAI4，TAI4-TAI14；

S-NSSAI5，TAI5-TAI15。

in step 1002, the terminal initiates a registration procedure, and the core network returns an allowed nsai and a rejected nsai.

Assume that the subscribed NSSAI of the terminal is { S-NSSAI1, S-NSSAI2, S-NSSAI3, S-NSSAI4, S-NSSAI5}, and the terminal is currently located at TA5.

In case one, 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 carried requested nsai may include { S-nsai 1, S-nsai 2, S-nsai 3, S-nsai 4, S-nsai 5}, where when the RAN selects AMF according to the requested nsai, the RAN discovers that S-nsai-1, S-nsai-2, S-nsai-3 is served by AMF set 1, but that S-nsai-4, S-nsai-5 is served by AMF set 2, e.g., the RAN preferentially selects AMF in AMF set 1 as service AMF (serving AMF).

Further, the network side determines an allowed NSSAI and a registration area RA of the terminal according to the requested NSSAI of the terminal. For example, the information sent by the service AMF to the terminal is as follows:

allowed NSSAI：{S-NSSAI1、S-NSSAI2、S-NSSAI 3}；

rejected NSSAI：{S-NSSAI4:2、S-NSSAI5:2}；

ra= { TA4, TA5, TA6}, here it is assumed that the registration area of the terminal consists of 3 TAs. The allowed NSSAI includes identification information of a network slice that the core network side allows access, that is, the core network side allows the terminal to access slice 1 and slice 2.

The rejected NSSAI includes identification information of network slices to which the core network side denies access, i.e. the core network side denies the terminal access to slices 4 and 5. The reason for rejecting the terminal to access slice 4 and slice 5 has a value of 2. Wherein, the cause value 2 corresponding to slice 4 represents: slice 4 is isolated from slices in allowed NSSAI, and the cause value 2 corresponding to slice 5 represents: slice 5 is isolated from slices in allowed NSSAI.

Further, the service AMF may store the following information in the context of the terminal:

RA＝{TA4，TA5，TA6}；

allowed NSSAI：{S-NSSAI1、S-NSSAI2、S-NSSAI 3}。

also, the AMF stores the service status of each TA in the service area of each network slice in the allowed NSSAI. Taking slice 1 identified by S-nsai 1 in allowed nsai as an example, AMF records the service status of slice 1 in each of TA1-TA13, for example, the recorded information is: slice 1 is in a "usable state" at TA1-TA7 and in a "restricted state" (i.e., temporarily unavailable state) at TA8-TA 13. Similar methods are also used for slice 2 and slice 3 to record the service status of the slice at each TA, and are not illustrated.

Further, the service AMF may also send an isolation rule (or called coexistence rule) to the terminal: S-NSSAI1, S-NSSAI2, S-NSSAI3 and S-NSSAI4, S-NSSAI5 are isolated from each other.

In case two, the terminal knows that the slice supported by AMF set 1 is isolated from the slice supported by AMF set 2, and that the service state of slice 3 in AMF set 1 is "restricted state".

For example, the terminal is preconfigured with an isolation rule, and the isolation rule indicates: NSSAI1, S-NSSAI2, S-NSSAI3 and S-NSSAI4, S-NSSAI5 are isolated from each other. Thus, the terminal does not request NSSAI1, S-NSSAI2, S-NSSAI3 and S-NSSAI4, S-NSSAI5 at the same time.

The terminal initiates a registration request, for example, the carried request NSSAI includes { S-NSSAI1, S-NSSAI2, S-NSSAI3}, and when the RAN selects an AMF according to the request NSSAI, the RAN discovers that S-NSSAI-1, S-NSSAI-2, S-NSSAI-3 are served by AMF set 1, so that the RAN can select one AMF from AMF set 1 as service AMF (serving AMF).

Further, the network side determines an allowed NSSAI and a Registration Area (RA) of the terminal according to the requested NSSAI of the terminal. For example, the information sent by the service AMF to the terminal is as follows:

allowed NSSAI：{S-NSSAI1、S-NSSAI2、S-NSSAI 3}；

ra= { TA4, TA5, TA6}, here it is assumed that the registration area of the terminal consists of 3 TAs.

RA＝{TA4，TA5，TA6}；

allowed NSSAI：{S-NSSAI1、S-NSSAI2、S-NSSAI 3}。

the foregoing examples have been presented only to facilitate the description of specific implementations. Of course, in practical application, the implementation is not limited to the above implementation, and may be implemented in other ways.

In step 1003, the nssf determines that the service state of the slice or slices within one or more TAs is changed from "available state" to "limited state".

Taking the example of step 1002 as described above, the terminal is currently located in TA5, and the registration area ra= { TA4, TA5, TA6}, of the terminal. Take the above slice 3 as an example.

In a first example, slice 3 is available at all TAs, i.e., slice 3 is available at all TAs 3 through TA13, prior to step 1003. In step 1003, when the NSSF determines that the load of slice 3 is higher than the preset threshold, the NSSF determines that the service status of slice 3 in all TAs is changed from "available status" to "limited status", and therefore, after the change, slice 3 is not available in all TAs, i.e. slice 3 is not available in any of TA3 to TA 13.

In a second example, slice 3 is available at all TAs, i.e., slice 3 is available at TA3 through TA13, prior to step 1003. In step 1003, when the NSSF determines that the load of slice 3 is higher than the preset threshold, the NSSF determines that the service state of slice 3 in part TA is changed from the "available state" to the "limited state", for example, determines that the service state of slice 3 in TA5 and TA6 is changed from the "available state" to the "limited state", and therefore, after the change, slice 3 is not available in TA5 and TA6 and is available in TA3, TA4 and TA7 to TA 13.

In a third example, slice 3 is available at some of the TAs, such as TA3 through TA10, and not TA11 through TA13, prior to step 1003. In step 1003, when the NSSF determines that the load of slice 3 is higher than the preset threshold, the NSSF determines that the service status of slice 3 in all available TAs (i.e., TA3 to TA 10) is changed from "available status" to "limited status", and therefore, after the change, slice 3 is not available in all TAs, i.e., slice 3 is not available in TA3 to TA 13.

In a fourth example, slice 3 is available at some of the TAs, such as TA3 through TA10, and not TA11 through TA13, prior to step 1003. In step 1003, when the NSSF determines that the load of slice 3 is higher than the preset threshold, the NSSF determines that the service state of slice 3 in the partially available TA is changed from the "available state" to the "limited state", for example, determines that the service state of slice 3 in TA6 to TA10 is changed from the "available state" to the "limited state", and therefore, after the change, slice 3 is not available in TA6 to TA13 and is available in TA3 to TA 5.

In a fifth example, slice 3 is available at some of the TAs, such as TA3 through TA10, and not TA11 through TA13, prior to step 1003. In step 1003, when the NSSF determines that the load of slice 3 is higher than the preset threshold, the NSSF determines that the service state of slice 3 in the partially available TA is changed from the "available state" to the "limited state", for example, determines that the service state of slice 3 in TA7 to TA10 is changed from the "available state" to the "limited state", and therefore, after the change, slice 3 is not available in TA7 to TA13 and is available in TA3 to TA 6.

At step 1004, NSSF sends a notification to the AMF. Accordingly, the AMF may receive the notification.

The notification may be, for example, nnssf_nssaiaivailityjnotify, or may be a notification message.

The notification includes identification information of the slice and identification information of the at least one TA, where the identification information of the at least one TA may be represented in a specific implementation using a TA list, i.e. the notification may include the identification information of the slice and a TA list including the identification information of the at least one TA.

For convenience of explanation, the present application will be described later with reference to the above notification including identification information of a slice and a TA list.

The slice here refers to a slice in which the service status of some or all TAs determined in the above step 1003 is changed from the "available status" to the "limited status", as in slice 3 in the respective examples of the above step 1003. The TA list here includes one or more TAs, and the state of the slice within any TA in the TA list is changed from an "available state" to a "restricted state".

For example, for the first example in step 1003 above, where slice refers to slice 3, the TA list includes TA3 through TA13. For a second example of step 1003, as described above, the slice is slice 3 and the TA list includes TA5 and TA6. For a third example, as in step 1003 above, the slice here refers to slice 3 and the TA list includes TA3 to TA10. For example, as for the fourth example in step 1003 above, where slice refers to slice 3, the TA list includes TA6 through TA10. For example, as for the fifth example in step 1003 above, where slice refers to slice 3, the TA list includes TA7 through TA10.

It should be noted that, in the above step 1002, the service status of each TA in the service area of each network slice in the allowed NSSAI is not stored in the AMF. Then in this step 1004, the service status of the slice in each TA of the service area of the slice may be carried in the notification, i.e. for any of the four examples in step 1003 above, the notification message in this step 1004 may carry the identification information of the slice and the current service status of the slice in each TA of the slice.

In step 1005, the amf determines slices not available to the terminal based on the allowed nsais in the context of the terminal.

For example, in the first or second case of the above step 1002, the information stored in the context of a certain terminal by the AMF includes:

RA＝{TA4，TA5，TA6}；

allowed NSSAI：{S-NSSAI1、S-NSSAI2、S-NSSAI3}。

for the first example of step 1003 described above, the notification in step 1004 carries the identification of slice 3S-NSSAI 3 and the identifications of TA3 to TA 13. Since slice 3 changes to the "restricted state" at the service states of TA3 to TA13 and the RA of the terminal includes TA4, TA5 and TA6, the terminal cannot use this slice 3 at TA4 to TA6 and the terminal will not use this slice 3, i.e. slice 3 in the determined allowed nsai of this terminal is currently not available and thus the determined slice not available to the terminal includes slice 3.

For the second example of step 1003 described above, the notification in step 1004 carries the identification of slice 3S-NSSAI 3 and the identifications of TA5, TA 6. Since the service state of slice 3 at TA5, TA6 is changed to "limited state", and the RA of the terminal includes TA4, TA5 and TA6, the terminal cannot use this slice 3 at TA5, TA6, and the terminal will not use this slice 3, i.e. slice 3 in the determined allowed nsai of this terminal is currently unavailable, and thus the slice determined to be unavailable to the terminal includes slice 3.

For the third example of step 1003 described above, the notification in step 1004 carries the identification of slice 3S-NSSAI 3 and the identifications of TA3 to TA 10. Since slice 3 changes to the "restricted state" at the service states of TA3 to TA10 and the RA of the terminal includes TA4, TA5 and TA6, the terminal cannot use this slice 3 at TA4 to TA6 and the terminal will not use this slice 3, i.e. slice 3 in the determined allowed nsai of this terminal is currently not available and thus the determined slice not available to the terminal includes slice 3.

For the fourth example of step 1003 described above, the notification in step 1004 carries the identification of slice 3, S-NSSAI3, and the identification of TA6 through TA 10. Since slice 3 changes to the "restricted state" at the service states of TA6 to TA10 and the RA of the terminal includes TA4, TA5 and TA6, the terminal cannot use this slice 3 at TA6 and the terminal will not use this slice 3, i.e. slice 3 in the determined allowed nsai of this terminal is currently not available and thus the determined slice not available to the terminal includes slice 3.

For the fifth example of step 1003 described above, the notification in step 1004 carries the identification of slice 3S-NSSAI 3 and the identifications of TA7 to TA 10. Since the service state of slice 3 at TA7 to TA10 is changed to the "limited state" and the service state of slice 3 at TA3 to TA6 is the "available state", and the RA of the terminal includes TA4, TA5 and TA6, the terminal can still use this slice 3, thus determining that slice 3 in the allowed nsai is still currently available. Based on this example 5, if slice 1 and slice 2 in the allowed nsai are still available, the AMF will determine the slices in the allowed nsai that are available or accessible to both terminals.

That is, a slice may be said to be usable by a terminal or accessible to the terminal whenever the terminal is usable within all TAs within the registration area of the terminal (i.e., within any one of the TAs). In other words, a terminal may be said to be unable to use a slice as long as the terminal is unable to use the slice within any one TA of the registration area.

In step 1006, the AMF determines new allowed NSSAI and rejected NSSAI for the terminal and stores the rejected NSSAI.

Based on the above example, if the AMF determines that the terminal is currently unable to use slice 3, and further determines that the terminal is still currently able to use

slices

1 and 2, then the AMF determines that the new allowed nsai for the terminal is { S-nsai 1, S-nsai 2}, and the reject nsai determined for the terminal includes { S-nsai 3}. Also, the AMF stores the rejected NSSAI.

In step 1007A, if the terminal is in a connected (connected) state, the AMF sends the new allowed nsai and the rejected nsai to the terminal through the configuration update procedure.

In step 1007B, if the AMF is in an idle state, the AMF may wait for the terminal to be in a connected state again (e.g., wait for the terminal to initiate a periodic registration update procedure), and then send the new allowed nsai and the rejected nsai to the terminal.

The steps 1007A and 1007B are performed alternatively.

At step 1008, the nssf determines that the service state of the slice or slices within the TA or TAs is changed from "restricted state" to "available state".

This step 1008 is a step of the reverse process to the above step 1003. Still taking the example in step 1003 above as an example.

In the first example described above, slice 3 is not available at all TAs, i.e., slice 3 is not available at TA3 through TA13, after step 1003. In step 1008, when the NSSF determines that the load of slice 3 is below the preset threshold, the NSSF determines that the service status of slice 3 in all TAs is changed from "limited status" to "available status", and therefore, after the change, slice 3 is available in all TAs, i.e., slice 3 is available in all TAs 3 through TA 13.

In the second example described above, slice 3 is not available at TA5, TA6, and is available at TA3, TA4, TA7 to TA13 after step 1003. In step 1008, when the NSSF determines that the load of slice 3 is below the preset threshold, the NSSF determines that the service state of slice 3 in the partially unavailable TA is changed from the "limited state" to the "available state", for example, determines that the service state of slice 3 in TA6 is changed from the "limited state" to the "available state", and therefore, after the change, slice 3 is available in all of TA3, TA4, TA6 to TA13 and unavailable in TA 5.

In the third example described above, slice 3 is not available at TA3 to TA13 after step 1003. In step 1008, when the NSSF determines that the load of slice 3 is below the preset threshold, the NSSF determines that the service state of slice 3 in the partially unavailable TA is changed from the "limited state" to the "available state", for example, determines that the service state of slice 3 in TA3 to TA8 is changed from the "limited state" to the "available state", and therefore, after the change, slice 3 is available in TA3 to TA8 and still unavailable in TA9 to TA 13.

In the fourth example described above, slice 3 is available at TA3 through TA5 and is not available at TA6 through TA13 after step 1003. In step 1008, when the NSSF determines that the load of slice 3 is lower than the preset threshold, the NSSF determines that the service state of slice 3 in all the unavailable TAs is changed from the "limited state" to the "available state", that is, the service state of slice 3 in TA6 to TA13 is changed from the "limited state" to the "available state", and therefore, after the change, slice 3 is available in all the TAs, that is, slice 3 is available in TA3 to TA 13.

In step 1009, the nssf sends a notification to the AMF. Accordingly, the AMF may receive the notification.

The notification includes slice identification information and at least one TA identification information, where the at least one TA identification information may be represented in a specific implementation using a TA list, i.e., the notification may include slice identification information and a TA list including at least one TA identification information.

The slice here refers to a slice in which the service status of some or all TAs determined in the above step 1008 is changed from the "limited status" to the "available status", as in slice 3 in the respective examples of the above step 1008. The TA list here includes one or more TAs, and the status of the slice within any TA in the TA list is changed from a "restricted status" to an "available status".

For example, for the first example in step 1008 above, then the slice in the notification of step 1009 refers to slice 3 and the TA list includes TA3 through TA13. For a second example of step 1008, as described above, the slice in the notification of step 1009 refers to slice 3 and the TA list includes TA6. For another example, as in the third example in step 1008, above, the slice in the notification of step 1009 refers to slice 3 and the TA list includes TA3 through TA8. For another example, as for the fourth example in step 1008, above, then the slice in the notification of step 1009 refers to slice 3 and the TA list includes TA6 through TA13.

In step 1010, the AMF determines a new allowed NSSAI for the terminal based on the reject NSSAI stored in the context of the terminal.

For example, in the example of step 1006, the AMF includes { S-nsai 3} for the reject NSSAI stored by the terminal, and the notification of step 1009 carries slice 3 and the TA list corresponding to slice 3, then in step 1010, the AMF needs to determine whether the terminal can currently use slice 3, which is described below in conjunction with the four examples of 1008.

For example, for the first example of step 1008 described above, the AMF determines that slice 3 is currently in the "available state" at TA3 to TA13 based on the stored context of the terminal and the notification received through step 1009, and the registration area of the terminal includes TA4 to TA6, so the terminal can use this slice 3. Thus for this example, the new allowed NSSAI determined includes { NSSAI1, NSSAI2, NSSAI3}.

For another example, for the second example of step 1008, the AMF determines that slice 3 is currently in the "available state" at TA3, TA4, TA6 to TA13, and is in the "restricted state" at TA5, and the registration area of the terminal includes TA4 to TA6, based on the stored context of the terminal and the notification received through step 1009, so the terminal may not use slice 3. Thus for this example, a new allowed NSSAI determined for the terminal is not needed.

For another example, for the third example of step 1008, the AMF determines that slice 3 is currently in the "available state" at TA3 to TA8, in the "restricted state" at TA9 to TA13, and the registration area of the terminal includes TA4 to TA6, based on the stored context of the terminal and the notification received through step 1009, so the terminal can use slice 3. Thus for this example, the new allowed NSSAI determined includes { S-NSSAI1, S-NSSAI2, S-NSSAI3}.

For another example, for the fourth example of step 1008, the AMF determines that slice 3 is currently in an "available state" at TA3 to TA13 based on the stored context of the terminal and the notification received through step 1009, and the registration area of the terminal includes TA4 to TA6, so the terminal may use slice 3. Thus for this example, the new allowed NSSAI determined includes { S-NSSAI1, S-NSSAI2, S-NSSAI3}.

In 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 above for step 1007A or step 1007B.

Optionally, if the new allowed nsai includes a slice in the rejected nsai stored by the AMF, the AMF may also delete the slice identifier in the rejected nsai. For example, for the slice 3, the S-nsai 3 is included after the new allowed nsai is sent to the terminal, and the AMF may delete the identification S-nsai 3 of the slice 3 from the rejected nsai.

Based on this embodiment, the AMF stores the rejected nsai in the context of the terminal, and when the AMF receives a notification from the NSSF that the slice in the rejected nsai becomes available again to the terminal, the AMF sends the identity of the slice to the terminal included in the new allowed nsai. The re-starting of the slice is realized, and the resource utilization rate can be improved.

As shown in fig. 11, another slice information updating method is provided in the present application. For convenience of explanation, the embodiment shown in fig. 11 will be explained using an example similar to that in the embodiment shown in fig. 10 described above.

The method comprises the following steps:

steps 1101-1109, similar to steps 1001-1009 of the embodiment shown in fig. 10, reference is made to the foregoing description.

Note that in step 1106, the AMF may not need to store the determined reject nsai.

In step 1110, the terminal sends a registration request message to the AMF. Accordingly, the AMF may 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 in step 1107A or step 1107B above.

Taking the same example as the example taken by steps 1101-1109 of the embodiment shown in fig. 11 and the example taken by steps 1001-1009 of the embodiment shown in fig. 10 above, that is, the service state of the slice 3 in part or all of the TAs of the slice 3 is determined to be changed from the "limited state" to the "available state" in steps 1101-1109, and the AMF notifies the terminal to reject the terminal to access (or use) the slice 3 through the rejected nsai in step 1007A or 1007B.

Before the terminal initiates step 1111, it is already known that the slice 3 is a slice that was rejected by the network before, and in this embodiment, the terminal will carry the identification information of the slice that was rejected for access, such as the identification information of the slice 3 described above, i.e. S-nsai 3, in the requested nsai when it initiates the request again.

As a specific implementation, the terminal does not move out of the registration area, and after the timer of the periodic registration update expires, the terminal initiates a periodic registration request message in the registration area, carrying the requested NSSAI and the registration type (registration type). Wherein the requested NSSAI includes the S-NSSAI in the rejected NSSAI acquired in step 1107A or step 1107B, and the registration type indicates that the registration request is a periodic registration update (Periodic Registration Update).

At step 1111, the AMF determines a new allowed NSSAI for the terminal based on the requested NSSAI. Taking the requested NSSAI of step 1110 as an example, slice 3 is carried in the requested NSSAI, that is, S-NSSAI3, in step 1111, if the AMF determines that the terminal can currently use the slice 3, the AMF carries S-NSSAI3 in the new allowed NSSAI. Of course, the new allowed nsai may also carry the identification of other usable slices.

In 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 previously rejected slice in the registration request message, and then the AMF determines whether the terminal can use the rejected slice currently, and if so, the previously rejected slice identifier is included in the new allowed nsai and sent to the terminal.

Based on this embodiment, the terminal carries the identification 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 subsequently when the slice becomes available from temporarily unavailable.

the mobility management network element receives a notification message from a network slice selection network element, the notification message including identification information of a network slice and identification information of at least one tracking area, the network slice being available in the at least one tracking area, the network slice being unavailable in the at least one tracking area;

the method comprises the steps that a mobility management network element determines an updated access-allowed network slice set, wherein the updated access-allowed network slice set comprises identification information of network slices, a terminal is located in a registration area of the terminal, and the terminal can access the network slices;

And the mobility management network element sends the updated access allowed network slice set to the terminal.

In the slice information updating method, the operation of the mobility management network element may refer to the operation of the AMF in fig. 10 or fig. 11 and the above related text descriptions, which are not repeated here.

The invention also discloses a slice information updating method, which comprises the following steps:

the method comprises the steps that a terminal receives a network slice set which is allowed to be accessed and a network slice set which is refused to be accessed from a terminal of a mobility management network element, wherein the network slice set which is refused to be accessed comprises identification information of the network slice, and the terminal is positioned in a registration area of the terminal;

the terminal sends a registration request message to a mobility management network element, wherein the registration request message comprises identification information of the network slice;

the terminal receives an updated set of access-allowed network slices from the mobility management network element, the updated set of access-allowed network slices including identification information of the network slices that were available in the registration area of the terminal and were not available in the registration area of the terminal.

In the slice information updating method, the operation of the terminal may refer to the operation of the terminal in fig. 11 and the above related text descriptions, which are not repeated here.

The above description has been presented mainly from the point of interaction between the network elements. It will be appreciated that, in order to achieve the above-mentioned functions, each network element includes a corresponding hardware structure and/or software module for performing each function. Those of skill in the art will readily appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as hardware or combinations of hardware and computer software. Whether a function is implemented as hardware or computer software driven hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.

Based on the same inventive concept, as shown in fig. 12, a schematic diagram of an apparatus is provided in this application, where the apparatus 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 method of any of the foregoing embodiments may be performed.

The apparatus 1200 includes at least one processor 1201, communication lines 1202, a memory 1203, and at least one communication interface 1204.

The processor 1201 may be a general purpose central processing unit (central processing unit, CPU), microprocessor, application-specific integrated circuit (server IC), or one or more integrated circuits for controlling the execution of programs in accordance with aspects of the present application.

Communication line 1202 may include a pathway to transfer information between the aforementioned components.

The communication interface 1204, using any transceiver-like means for communicating with other devices or communication networks, such as ethernet, radio access network (radio access network, RAN), wireless local area network (wireless local area networks, WLAN), etc.

The memory 1203 may be, but is not limited to, a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (random access memory, RAM) or other type of dynamic storage device that can store information and instructions, an electrically erasable programmable read-only memory (EEPROM), a compact disc-only memory (compact disc read-only memory) or other optical disk storage, a compact disc storage (including compact disc, laser disc, optical disc, digital versatile disc, blu-ray disc, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. The memory may be separate and coupled to the processor via communication line 1202. The memory may also be integrated with the processor.

The memory 1203 is used for storing computer-executable instructions for executing the embodiments of the present application, and is controlled by the processor 1201. The processor 1201 is configured to execute computer-executable instructions stored in the memory 1203, thereby implementing the slice information updating method provided in the following embodiments of the present application.

Alternatively, the computer-executable instructions in the embodiments of the present application may be referred to as application program codes, which are not specifically limited in the embodiments of the present application.

In a particular implementation, the processor 1201 may include one or more CPUs, such as CPU0 and CPU1 in fig. 12, as one embodiment.

In a particular implementation, as one embodiment, apparatus 1200 may include multiple processors, such as processor 1201 and processor 1208 in fig. 12. Each of these processors may be a single-core (single-CPU) processor or may be a multi-core (multi-CPU) processor. A processor herein may refer to one or more devices, circuits, and/or processing cores for processing data (e.g., computer program instructions).

In a specific implementation, as an embodiment, when the apparatus 1200 is a terminal, the apparatus 1200 may further include an output device 1205 and an input device 1206. The output device 1205 is in communication with the processor 1201 and may display information in a variety of ways. For example, the output device 705 may be a liquid crystal display (liquid crystal display, LCD), a light emitting diode (light emitting diode, LED) display device, a Cathode Ray Tube (CRT) display device, or a projector (projector), or the like. The input device 1206 is in communication with the processor 1201 and may receive input from a user in a variety of ways. For example, the input device 1206 may be a mouse, keyboard, touch screen device, or sensing device, among others.

When the apparatus shown in fig. 12 is a chip, which may be, 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 (may also include a processor 1208), a communication line 1202, a memory 1203, and a communication interface 1204. In particular, the communication interface 1204 may be an input interface, a pin, or a circuit, etc. 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 configured to control the execution of the programs of the slice information updating method of any of the embodiments described above.

The present application may divide the functional modules of the apparatus according to the above method example, for example, each functional module may be divided corresponding to each function, or two or more functions may be integrated into one processing module. The integrated modules may be implemented in hardware or in software functional modules. It should be noted that the division of the modules in this application is illustrative, and is merely a logic function division, and other division manners may be implemented in practice. For example, in the case of dividing the respective functional modules by the respective functions, fig. 13 shows a schematic diagram of an apparatus, and the apparatus 1300 may be a communication network element or a chip of the communication network element, where the communication network element is a mobility management network element or a policy control network element. The apparatus 1300 includes a receiving unit 1301, a transmitting unit 1302. Optionally, a processing unit 1303 is also included.

A receiving unit 1301, configured to receive a notification message from a network slice selection network element, where the notification message includes identification information of a network slice, and the notification message is used to indicate that a public land mobile network PLMN supports the network slice, and the PLMN does not support the network slice. A sending unit 1302, configured to notify a terminal PLMN to support network slicing, where the terminal is a terminal that requested network slicing failed and signed up for network slicing.

Optionally, the processing unit 1303 is configured to determine the terminal according to the terminal context.

As an implementation manner, the device is a mobility management network element or a chip of the mobility management network element, and then:

the processing unit 1303 is further configured to add identification information of the network slice to a set of network slices allowed to access by the terminal. The sending unit 1302 is specifically configured to send the updated set of network slices allowed to access to the terminal.

Further, the sending unit 1302 is further configured to send indication information to the terminal, where the indication information is used to indicate that the PLMN supports network slicing.

Further, the processing unit 1303 is configured to add identification information of a network slice to a set of network slices allowed to be accessed by the terminal; the sending unit 1302 is specifically configured to send a configuration update message to the terminal, where the configuration update message includes the updated set of network slices allowed to be accessed. Optionally, the configuration update message further comprises indication information.

As another implementation manner, the device is a policy control network element or a chip of the policy control network element, and then:

the processing unit 1303 is further configured to determine a mobility management network element registered by the terminal. The sending unit 1302 is specifically configured to send, to the terminal, indication information through the mobility management network element, where the indication information is used to indicate that the PLMN supports network slicing.

Further, the receiving unit 1301 is further configured to receive identification information of a network slice, identification information of a mobility management network element, and identification information of a terminal, which are sent by the mobility management network element.

It should be understood that 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-7 in the method of the embodiment of the present invention, and the relevant features may be referred to above and will not be described herein.

Specifically, the functions/implementation procedures of the receiving unit 1301, the transmitting unit 1302, and the processing unit 1303 in fig. 13 may be implemented by the processor 1201 in fig. 12 calling computer-executed instructions stored in the memory 1203. Alternatively, the functions/implementation procedures of the processing unit 1303 in fig. 13 may be implemented by the processor 1201 in fig. 12 calling computer-executable instructions stored in the memory 1203, and the functions/implementation procedures of the receiving unit 1301 and the transmitting unit 1302 in fig. 13 may be implemented by the communication interface 1204 in fig. 12.

Alternatively, when the apparatus 1300 is a chip, the functions/implementation procedures of the receiving unit 1301 and the transmitting unit 1302 may also be implemented by pins or circuits, or the like. Alternatively, when the apparatus 1300 is a chip, the memory 1203 may be a storage unit in the chip, such as a register, a cache, or the like. Of course, when the apparatus 1300 is a communication network element, the memory 1203 may be a storage unit located outside the chip in the communication network element, which is not limited in detail in the embodiment of the present application.

The present application may divide the functional modules of the apparatus according to the above method example, for example, each functional module may be divided corresponding to each function, or two or more functions may be integrated into one processing module. The integrated modules may be implemented in hardware or in software functional modules. It should be noted that the division of the modules in this application is illustrative, and is merely a logic function division, and other division manners may be implemented in practice. For example, in the case of dividing the respective functional modules by the respective functions, fig. 14 shows a schematic diagram of an apparatus 1400, which may be a mobility management network element or a chip of the mobility management network element as referred to in the above embodiment. The apparatus 1400 includes a receiving unit 1401, a transmitting unit 1402. Optionally, the apparatus 1400 further comprises a processing unit 1403. Optionally, the apparatus 1400 further comprises a storage unit 1404.

In a first embodiment, a receiving unit 1401 is configured to receive an update message from a policy control network element, where the update message includes indication information and identification information of a terminal, and the indication information is used to indicate that a public land mobile network PLMN supports network slicing, where the PLMN does not support network slicing; a sending unit 1402, configured to notify a terminal PLMN to support network slicing, where the terminal is a terminal that requested network slicing failed and signed up for network slicing.

In a possible implementation, the processing unit 1403 is configured to add identification information of the network slice to a set of network slices of the terminal that are allowed to be accessed. A sending unit 1402 is specifically configured to send the updated set of network slices allowed to access to the terminal.

In a possible implementation manner, the sending unit 1402 is further configured to send indication information to the terminal, where the indication information is used to indicate that the PLMN supports network slicing.

In a possible implementation, the processing unit 1403 is configured to add identification information of the network slice to a set of network slices of the terminal that are allowed to be accessed. The sending unit 1402 is specifically configured to send a configuration update message to the terminal, where the configuration update message includes the updated set of network slices allowed to be accessed. Optionally, the configuration update message further comprises indication information.

In a possible implementation manner, the sending unit 1402 is specifically configured to send a NAS message to the terminal, where the NAS message includes the indication information.

In a possible implementation manner, the sending unit 1402 is further configured to send identification information of the terminal, identification information of the mobility management network element, and identification information of the network slice to the policy control network element.

In a second embodiment, a receiving unit 1401 is configured to receive a notification message from a network slice selection network element, where the notification message includes identification information of a network slice and identification information of at least one tracking area, where the network slice is available, and where the network slice is not available in the at least one tracking area; a processing unit 1403, configured to determine an updated set of access-allowed network slices, where the updated set of access-allowed network slices includes identification information of the network slices, and the terminal is located in a registration area of the terminal and is capable of accessing the network slices; a sending unit 1402, configured to send the updated set of allowed access network slices to the terminal.

In a possible implementation, 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.

In a possible implementation, the storage unit 1404 is configured to store, before the receiving unit 1401 receives the notification message from the network element for selecting a network slice, a set of network slices for which access is denied by the terminal, where the set of network slices for which access is denied includes identification information of the network slice.

In a possible implementation manner, the receiving unit 1401 is further configured to receive a registration request message from the terminal before the sending unit 1402 sends the updated set of network slices allowed to access to the terminal, where the registration request message includes identification information of the network slices.

In a possible implementation manner, the sending unit 1402 is specifically configured to send a registration accept message to the terminal, where the registration accept message includes the updated set of network slices allowed to be accessed.

It should be understood that the apparatus may be used to implement the steps performed by the AMF in the embodiments shown in fig. 6-7 and fig. 10-11 in the method of the embodiment of the present invention, and the relevant features may be referred to above and will not be described herein.

Specifically, the functions/implementation procedures 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 computer-executed instructions stored in the memory 1203. Alternatively, the functions/implementation of the processing unit 1403 in fig. 14 may be implemented by the processor 1201 in fig. 12 calling computer-executable instructions stored in the memory 1203, and the functions/implementation of the receiving unit 1401 and the transmitting unit 1402 in fig. 14 may be implemented by the communication interface 1204 in fig. 12.

Alternatively, when the apparatus 1400 is a chip, the functions/implementation procedures of the receiving unit 1401 and the transmitting unit 1402 may also be implemented by pins or circuits, or the like. Alternatively, when the device 1400 is a chip, the memory 1203 may be a storage unit within the chip, such as a register, a cache, or the like. Of course, when the apparatus 1400 is a mobility management network element, the memory 1203 may be a storage unit located outside the chip in the mobility management network element, which is not specifically limited in the embodiment of the present application.

The present application may divide the functional modules of the apparatus according to the above method example, for example, each functional module may be divided corresponding to each function, or two or more functions may be integrated into one processing module. The integrated modules may be implemented in hardware or in software functional modules. It should be noted that the division of the modules in this application is illustrative, and is merely a logic function division, and other division manners may be implemented in practice. For example, in the case of dividing the respective functional modules by the respective functions, fig. 15 shows a schematic diagram of an apparatus, and the apparatus 1500 may be a policy control network element or a chip of the policy control network element as referred to in the above embodiment. The apparatus 1500 includes a receiving unit 1501, a transmitting unit 1502, and a processing unit 1503.

A receiving unit 1501, configured to receive identification information of a terminal from a mobility management network element and identification information of a network slice, where the network slice is a network slice that is not supported by a current registration area of the terminal;

a processing unit 1503, configured to obtain a service area corresponding to a network slice from a network slice selection network element;

if the processing unit 1503 knows that the terminal moves to the service region, the transmitting unit 1502 notifies the terminal that the network slice is available.

In one possible implementation, the sending unit 1502 is further configured to subscribe to a mobility management network element: when the position of the terminal is updated, the mobility management network element sends the updated position of the terminal to the device.

In one possible implementation, the sending unit 1502 is specifically configured to: and sending indication information to the terminal through the mobility management network element, wherein the indication information is used for indicating that the network slice is available.

It should be understood that the apparatus 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, and the relevant features may be referred to above and will not be described herein.

Specifically, the functions/implementation procedures of the receiving unit 1501, the transmitting unit 1502, and the processing unit 1503 in fig. 15 may be implemented by the processor 1201 in fig. 12 calling computer-executable instructions stored in the memory 1203. Alternatively, the functions/implementation procedures of the processing unit 1503 in fig. 15 may be implemented by the processor 1201 in fig. 12 calling computer-executable instructions stored in the memory 1203, and the functions/implementation procedures of the receiving unit 1501 and the transmitting unit 1502 in fig. 15 may be implemented by the communication interface 1204 in fig. 12.

Alternatively, when the apparatus 1500 is a chip, the functions/implementation procedures of the receiving unit 1501 and the transmitting unit 1502 may also be implemented by pins or circuits, or the like. Alternatively, when the apparatus 1500 is a chip, the memory 1203 may be a storage unit within the chip, such as a register, a cache, or the like. Of course, when the apparatus 1500 is a policy control network element, the memory 1203 may be a storage unit located outside the chip in the policy control network element, which is not limited in detail in the embodiment of the present application.

The present application may divide the functional modules of the apparatus according to the above method example, for example, each functional module may be divided corresponding to each function, or two or more functions may be integrated into one processing module. The integrated modules may be implemented in hardware or in software functional modules. It should be noted that the division of the modules in this application is illustrative, and is merely a logic function division, and other division manners may be implemented in practice. For example, in the case of dividing each functional module by corresponding each function, fig. 16 shows a schematic diagram of an apparatus, and the apparatus 1600 may be a network slice selection network element or a chip of a network slice selection network element as referred to in the above embodiment. The apparatus 1600 includes a transmission unit 1602 and a processing unit 1603. Optionally, a receiving unit 1601 is also included.

A processing unit 1603 for determining that the public land mobile network PLMN supports network slicing, wherein the PLMN did not support network slicing;

a sending unit 1602, configured to send a notification message to the communication network element, where the notification message includes identification information of a network slice, and the notification message is used to instruct the PLMN to support the network slice. Wherein the communication network element is a policy control network element or a mobility management network element.

In one possible implementation, the receiving unit 1601 is configured to receive a subscription from a communication network element: when the PLMN supports network slicing, the network slicing selection network element informs the communication network element.

In a possible implementation manner, the processing unit 1603 is further configured to determine, according to a slice type supported by a mobility management network element in the PLMN, that the mobility management network element supporting the network slice is a communication network element. It should be understood that the apparatus may be used to implement the steps performed by the NSSF in the embodiments shown in fig. 5-7 in the method of the embodiments of the present invention, and the relevant features may be referred to above and will not be described herein.

Specifically, the functions/implementation procedures of the reception unit 1601, the transmission unit 1602, and the processing unit 1603 in fig. 16 may be implemented by the processor 1201 in fig. 12 calling computer-executable instructions stored in the memory 1203. Alternatively, the functions/implementation procedures of the processing unit 1603 in fig. 16 may be implemented by the processor 1201 in fig. 12 calling computer-executable instructions stored in the memory 1203, and the functions/implementation procedures of the receiving unit 1601 and the transmitting unit 1602 in fig. 16 may be implemented by the communication interface 1204 in fig. 12.

Alternatively, when the apparatus 1600 is a chip, the functions/implementation procedures of the reception unit 1601 and the transmission unit 1602 may also be implemented by pins or circuits or the like. Alternatively, when the device 1600 is a chip, the memory 1203 may be a storage unit within the chip, such as a register, cache, or the like. Of course, when the apparatus 1500 is a network slice selection network element, the memory 1203 may be a storage unit located outside the chip in the network slice selection network element, which is not limited in detail in the embodiment of the present application.

The present application may divide the functional modules of the apparatus according to the above method example, for example, each functional module may be divided corresponding to each function, or two or more functions may be integrated into one processing module. The integrated modules may be implemented in hardware or in software functional modules. It should be noted that the division of the modules in this application is illustrative, and is merely a logic function division, and other division manners may be implemented in practice. For example, in the case of dividing respective functional modules by corresponding respective functions, fig. 17 shows a schematic diagram of an apparatus 1700, which may be a terminal or a chip of a terminal as referred to in the above-described 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 set of network slices allowed to access and a set of network slices denied to access from the terminal of the mobility management network element, where the set of network slices denied to access includes identification information of the network slices, and the terminal is located in a 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 identification information of the network slice; the receiving unit 1701 is further configured to receive an updated set of access-allowed network slices from the mobility management network element, where the updated set of access-allowed network slices includes identification information of the network slices, and the network slices are available in a registration area of the terminal, and the network slices are not available in the registration area of the terminal.

In a possible implementation, 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 be accessed.

It should be understood that the apparatus may be used to implement the steps performed by the terminal in the embodiments shown in fig. 10 to 11 in the method of the embodiment of the present invention, and the relevant features may be referred to above and will not be described herein.

Specifically, the functions/implementation procedures of the receiving unit 1701, the transmitting unit 1702, and the processing unit 1703 in fig. 17 may be implemented by the processor 1201 in fig. 12 calling computer-executable instructions stored in the memory 1203. Alternatively, the functions/implementation procedures of the processing unit 1703 in fig. 17 may be implemented by the processor 1201 in fig. 12 calling computer-executable instructions stored in the memory 1203, and the functions/implementation procedures of the receiving unit 1701 and the transmitting unit 1702 in fig. 17 may be implemented by the communication interface 1204 in fig. 12.

Alternatively, when the apparatus 1700 is a chip, the functions/implementation procedures of the receiving unit 1701 and the transmitting unit 1702 may also be implemented by pins or circuits, or the like. Alternatively, when the apparatus 1700 is a chip, the memory 1203 may be a storage unit such as a register, a cache, or the like within the chip. Of course, when the apparatus 1500 is a terminal, the memory 1203 may be a storage unit located outside the chip in the terminal, which is not particularly limited in the embodiment of the present application.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, 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. When loaded and executed on a computer, produces a flow or function in accordance with embodiments of the present invention, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may be stored in or transmitted from one computer-readable storage medium to another, for example, by wired (e.g., coaxial cable, optical fiber, digital Subscriber Line (DSL)), or wireless (e.g., infrared, wireless, microwave, etc.). The computer readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains an integration of one or more available media. The usable medium may be a magnetic medium (e.g., a floppy Disk, a hard Disk, a magnetic tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a Solid State Disk (SSD)), or the like.

The various illustrative logical blocks and circuits described in the embodiments of the present application may be implemented or performed with a general purpose processor, a digital signal processor, an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in the alternative, the general purpose processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., 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.

The steps of a method or algorithm described in the embodiments of the present application may be embodied directly in hardware, in a software element executed by a processor, or in a combination of the two. The software elements may be stored in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. In an example, a storage medium may be coupled to the processor such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC, which may reside in a terminal device. In the alternative, the processor and the storage medium may reside in different components in a terminal device.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

Although the invention has been described in connection with specific features and embodiments thereof, it will be apparent that various modifications and combinations can be made without departing from the spirit and scope of the invention. Accordingly, the specification and drawings are merely exemplary illustrations of the present invention as defined in the appended claims and are considered to cover any and all modifications, variations, combinations, or equivalents that fall within the scope of the invention. It will be apparent to those skilled in the art that various modifications and variations can be made to the present invention without departing from the spirit or scope of the invention. Thus, it is intended that the present invention also include such modifications and alterations insofar as they come within the scope of the appended claims or the equivalents thereof.

Claims

1. A slice information updating method, comprising:

the communication network element receives a notification message from a network slice selection network element, wherein the notification message comprises identification information of a network slice, and the notification message is used for indicating a Public Land Mobile Network (PLMN) to support the network slice, and the PLMN does not support the network slice;

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

the communication network element determines the terminal according to the terminal context.

3. The method according to claim 1 or 2, wherein the communication network element is a mobility management network element; the method further comprises the steps of:

the mobility management network element adds the identification information of the network slice into a network slice set of the terminal which is allowed to be accessed;

the communication network element informing the terminal that the PLMN supports the network slice comprises:

the mobility management network element sends an updated set of allowed access network slices to the terminal.

4. A method according to claim 3, wherein the communication network element informs a terminal that the PLMN supports the network slice, further comprising:

and the mobility management network element sends indication information to the terminal, wherein the indication information is used for indicating the PLMN to support the network slice.

5. The method according to claim 1 or 2, wherein the communication network element is a policy control network element; the method further comprises the steps of:

the policy control network element determines a mobility management network element registered by the terminal;

and the policy control network element sends indication information to the terminal through the mobility management network element, wherein the indication information is used for indicating the PLMN to support the network slice.

6. A slice information updating method, comprising:

the method comprises the steps that a mobility management network element receives an update message from a strategy control network element, wherein the update message comprises indication information and identification information of a terminal, the indication information is used for indicating a Public Land Mobile Network (PLMN) to support network slicing, and the PLMN does not support the network slicing;

7. The method of claim 6, wherein the method further comprises:

the mobility management network element informing the terminal that the PLMN supports the network slice comprises:

8. The method of claim 7, wherein the mobility management network element informs a terminal that the PLMN supports the network slice, further comprising:

9. The method of claim 6, wherein the mobility management network element informing a terminal that the PLMN supports the network slice comprises:

and the mobile management network element sends NAS information to the terminal, wherein the NAS information comprises the indication information.

10. An apparatus, comprising: a receiving unit and a transmitting unit;

the receiving unit is configured to receive a notification message from a network slice selection network element, where the notification message includes identification information of a network slice, and the notification message is configured to instruct a public land mobile network PLMN to support the network slice, where the PLMN does not support the network slice;

the sending unit is configured to notify a terminal that the PLMN supports the network slice, where the terminal requests that the network slice fails and signs up for the network slice.

11. The apparatus of claim 10, further comprising a processing unit configured to determine the terminal based on a terminal context.

12. The apparatus according to claim 10 or 11, characterized in that the apparatus is a mobility management network element; the apparatus includes a processing unit;

the processing unit is used for adding the identification information of the network slice into a network slice set of the terminal which is allowed to be accessed;

the sending unit is specifically configured to send the updated set of network slices allowed to be accessed to the terminal.

13. The apparatus of claim 12, wherein the transmitting unit is further configured to transmit indication information to the terminal, the indication information being used to indicate that the PLMN supports the network slice.

14. The apparatus according to claim 10 or 11, wherein the apparatus is a policy control network element; the apparatus includes a processing unit;

the processing unit is used for determining a mobility management network element registered by the terminal;

the sending unit is specifically configured to send, through 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.

15. An apparatus, comprising: a receiving unit and a transmitting unit;

the receiving unit is configured to receive an update message from a policy control network element, where the update message includes indication information and identification information of a terminal, where the indication information is used to indicate that a public land mobile network PLMN supports a network slice, and the PLMN does not support the network slice;

16. The apparatus of claim 15, further comprising a processing unit;

17. The apparatus of claim 16, wherein the transmitting unit is further configured to transmit indication information to the terminal, the indication information being used to indicate that the PLMN supports the network slice.

18. The apparatus according to claim 15, wherein the sending unit is specifically configured to send a NAS message to the terminal, where the NAS message includes the indication information.