Patent Description:
In a current network architecture, a plurality of network slices (network slice) are obtained through division on a common network infrastructure of a core network by using technologies such as virtualization, and the network slices are used to implement network services required by one or more services. To indicate a network slice of a specific type, information about the network slice may include a type of the corresponding network slice. Types of the network slice include, for example, an enhanced mobile broadband (enhanced mobile broadband, eMBB) type and an ultra low latency (ultra low latency) type. In a next-generation communications network, different types of network slices will support different system features (system feature). How to enable network devices to obtain system features that can be used by the network device has not been resolved currently.

<CIT> relates to method and device for terminal attaching and creating home-routed PDU session in roaming environment supporting network slice.

Publication titled "<NPL>, relates to system architecture for the <NUM> system.

This application provides a negotiation method, and an apparatus to implement application of a system feature supported by a network slice.

In particular, the invention claimed in this application is the method described with reference to <FIG> and the apparatus, the terminal device and the network device described with reference to <FIG>. The remaining description should be construed as illustrative examples provided for understanding the invention as noted in the above paragraph.

A specific operation method in method implementations may also be applied to an apparatus implementation or a system implementation. In the descriptions of this application, unless otherwise stated, "a plurality" means two or more than two.

A network architecture and a service scenario described in the implementations of this application are intended to describe the technical solutions in the implementations of this application more clearly, and do not constitute a limitation on the technical solutions provided in the implementations of this application. A person of ordinary skill in the art may know that with the evolution of the network architecture and the emergence of new service scenarios, the technical solutions provided in the implementations of this application are also applicable to similar technical problems.

<FIG> is a schematic diagram of a possible network architecture according to this application. The network architecture includes a network slice management network element and a network device. In this application, the network slice management network element may be used to configure the network device, including configuring information about a network slice and a system feature supported by the network slice. The network device comprises an access network device, a mobility management network element, a session management network element, a network slice selection network element, or the like.

The access network device is a device that provides a wireless communication function for a terminal device. For example, the access network device includes but is not limited to: a next generation NodeB (gNodeB, gNB), an evolved NodeB (evolved NodeB, eNB), a radio network controller (radio network controller, RNC), a NodeB (NodeB, NB), a base station controller (base station controller, BSC), a base transceiver station (base transceiver station, BTS), a home base station (for example, a home evolved NodeB or a home NodeB, HNB), a baseband unit (baseBand unit, BBU), a transmitting and receiving point (transmitting and receiving point, TRP), a transmitting point (transmitting point, TP), a mobile switching center, and the like in <NUM>.

The mobility management network element is mainly used for mobility management, for example, user location update, registration of a user with a network, or user handover, in a mobile network. In 5th generation (5th generation, <NUM>) communication, the mobility management network element may be an access and mobility management function (access and mobility management function, AMF) network element. In future communication, for example, in 6th generation (6th generation, <NUM>) communication, the mobility management network element may still be an AMF network element or may have another name. This is not limited in this application.

The session management network element is mainly used for session management, for example, session establishment, modification, or release, in a mobile network. A specific function is, for example, allocating an internet protocol (internet protocol, IP) address to a user, or selecting a user plane network element that provides a packet forwarding function. In <NUM>, the session management network element may be a session management function (session management function, SMF) network element. In future communication such as <NUM>, the session management network element may still be an SMF network element or may have another name. This is not limited in this application.

The network slice selection network element is mainly used to store related information of a network slice, including identification information of the network slice, a system feature supported by the network slice, and the like. In <NUM>, the network slice selection network element may be a network slice selection function (network slice selection function, NSSF) network element. In future communication such as <NUM>, the network slice selection network element may still be an NSSF network element or may have another name. This is not limited in this application.

It may be understood that the foregoing functions may be network elements in a hardware device, software functions running on dedicated hardware, or virtualized functions instantiated on a platform (for example, a cloud platform).

For ease of description, an example in which the mobility management network element is an AMF network element, the session management network element is an SMF network element, and the network slice selection network element is an NSSF network element is used for description below in this application. Further, the AMF network element is referred to as an AMF for short, the SMF network element is referred to as an SMF for short, and the NSSF network element is referred to as an NSSF for short. In other words, in the subsequent descriptions of this application, all AMFs may be replaced with mobility management network elements, all SMFs may be replaced with session management network elements, and all NSSFs may be replaced with network slice selection network elements.

<FIG> is a schematic diagram of another possible network architecture according to this application. The network architecture includes an access network device, an AMF, an SMF, an NSSF, a first network slice management network element, and a second network slice management network element. The access network device, the AMF, the SMF, and the NSSF may be collectively referred to as a network device. Optionally, the network architecture may further include a terminal device.

The first network slice management network element is used to configure a network slice for the network device on a core network side, such as an AMF, an SMF, or an NS SF. The second network slice management network element is used to configure a network slice for the access network device. During specific implementation, the first network slice management network element and the second network slice management network element may be a same network element, or may be different network elements.

The terminal device is a device with a wireless transceiver function, and may be deployed on land, for example, an indoor device, an outdoor device, a handheld device, or a vehicle-mounted device; may be deployed on the water (for example, on a ship); or may be deployed in the air (for example, on a plane, a balloon, or a satellite). The terminal device may be a mobile phone (mobile phone), a pad (Pad), a computer with a wireless transceiver function, a virtual reality (virtual reality, VR) terminal device, an augmented reality (augmented reality, AR) terminal device, a wireless terminal device in industrial control (industrial control), a wireless terminal device in self driving (self driving), a wireless terminal device in telemedicine (remote medical), a wireless terminal device in a smart grid (smart grid), a wireless terminal device in transportation safety (transportation safety), a wireless terminal device in a smart city (smart city), a wireless terminal device in a smart home (smart home), or the like.

The following describes, with reference to <FIG>, a configuration method and a negotiation method according to this application.

<FIG> shows the configuration method according to this application. The method is used to configure related information of a network slice for a core network device. The core network device herein refers to an SMF, an AMF, or an NSSF. In other words, the SMF, the AMF, and the NSSF may all be configured according to the following method. The method includes the following steps:
Step <NUM>: A network slice management network element sends configuration information to the core network device, and correspondingly, the core network device receives the configuration information.

The network slice management network element herein may be the network slice management network element shown in <FIG> or the first network slice management network element shown in <FIG>.

The configuration information includes information about the network slice and a system feature supported by the network slice. The information about the network slice includes one or more pieces of single network slice selection assistance information (single network slice selection assistance information, S-NSSAI).

The system feature refers to a service provided by a network for a terminal device or an external application. In one network slice, one or more system features may be deployed based on a service requirement. Correspondingly, to support and implement the one or more services, a corresponding network element needs to be deployed in an access network and a core network, and the deployed network element implements a network function service related to a system feature. For example, the system features may include but is not limited to any one or a combination of multiple of an internet protocol (internet protocol, IP) protocol data unit session (protocol data unit session, PDU session), a short messaging service over non-access stratum (short messaging service over non-access stratum, SMS over NAS), a location service (location service, LCS), and the like.

The following provides a description with reference to a specific example. Table <NUM> shows an example of the configuration information.

Table <NUM> shows content included in the configuration information sent by the network slice management network element to the core network device. The configuration information specifically includes (the S-NSSAI <NUM>, the system feature A, and the system feature B), (the S-NSSAI <NUM>, the system feature A, the system feature B, and the system feature C), and (the S-NSSAI <NUM> and the system feature B).

During specific implementation, the system feature in the configuration information may be an identifier of the system feature, for example, an identifier of an SMS over NAS system feature may be a system feature short message service (system feature short message service, SF_SMS). A unified description is provided herein, and details are not described later.

Optionally, the configuration information may further include indication information, and the indication information is used to indicate whether the system feature supported by the network slice can be used by a terminal device in a roaming state. If the configuration information further includes the indication information, the configuration information sent by the network slice management network element may be, for example, shown in Table <NUM>.

As shown in Table <NUM>, for each system feature supported by the network slice, there is corresponding indication information used to indicate whether the system feature can be accessed by a terminal device in a roaming state. During specific implementation, one bit may be used to represent the indication information. For example, "<NUM>" indicates that a terminal device in a roaming state can access the system feature, and "<NUM>" indicates that a terminal device in a roaming state cannot access the system feature.

Step <NUM>: The core network device stores the configuration information.

Specifically, the core network device stores the configuration information locally, or stores the configuration information in an external server or a database system that is specially used for data storage.

Step <NUM>: The core network device sends a configuration completion indication to the network slice management network element, and correspondingly, the network slice management network element receives the configuration completion indication.

The configuration completion indication is used to indicate that the configuration is completed.

According to the foregoing method, the related information of the network slice can be configured for the core network device such as an AMF, an SMF, or an NSSF.

It should be noted that, if the network slice management network element configures only the NSSF, and does not configure the AMF and the SMF, after the network slice management network element configures the NSSF, the AMF and the SMF may separately request to obtain the configuration information from the NSSF. <FIG> shows still another configuration method according to this application, used by an AMF or an SMF to obtain configuration information from an NSSF. Specifically, the following steps are included.

Step <NUM>: The AMF/SMF sends information about a network slice to the NSSF, and correspondingly, the NSSF receives the information about the network slice.

The information about the network slice sent by the AMF is information about one or more network slices supported by a core network. For example, if the AMF supports a network slice identified by S-NSSAI <NUM> and a network slice identified by S-NSSAI <NUM>, the information about the network slice sent by the AMF is S-NSSAI <NUM> and S-NSSAI <NUM>.

The information about the network slice sent by the SMF is information about a network slice to which the SMF belongs. For example, if the SMF belongs to the network slice identified by the S-NSSAI <NUM>, the information about the network slice sent by the SMF is the S-NSSAI <NUM>.

Step <NUM>: The NSSF sends a system feature supported by the network slice to the AMF/SMF, and correspondingly, the AMF/SMF receives the system feature supported by the network slice.

Using Table <NUM> as an example, if the information about the network slice sent by the AMF is the S-NSSAI <NUM> and the S-NSSAI <NUM>, the system feature sent by the NSSF to the AMF includes: (the S-NSSAI <NUM>, the system feature A, and the system feature B), and (the S-NSSAI <NUM>, the system feature A, the system feature B, and the system feature C).

If the information about the network slice sent by the SMF is the S-NSSAI <NUM>, the NSSF sends (the S-NSSAI <NUM>, the system feature A, and the system feature B) or (the system feature A and the system feature B) to the SMF.

According to the foregoing method, a network slice management network element first configures the related information of the network slice in the NS SF, and then each network element such as each SMF and each AMF obtains, from the NSSF, the system feature supported by the network slice. Therefore, the network slice management network element does not need to separately configure each SMF and each AMF, and system resources are saved.

<FIG> shows still another configuration method according to this application. The method is used to configure related information of a network slice for an access network device. The method includes the following steps:
Step <NUM>: A network slice management network element sends configuration information to the access network device, and correspondingly, the access network device receives the configuration information.

The network slice management network element herein may be the network slice management network element shown in <FIG> or the second network slice management network element shown in <FIG>.

In an implementation, the configuration information sent by the network slice management network element to the access network device may be the same as the configuration information sent by the network slice management network element to the core network device in step <NUM>. For details, refer to the foregoing description. For example, the sent configuration information is shown in Table <NUM> or Table <NUM>.

In another implementation, based on Table <NUM> or Table <NUM>, identification information of a public land mobile network PLMN (Public Land Mobile Network, PLMN) to which the network slice belongs may be further added to the configuration information sent by the network slice management network element to the access network device. For example, the configuration information sent by the network slice management network element to the access network device may be shown in Table <NUM>'. Alternatively, the configuration information sent by the network slice management network element to the access network device may be shown in Table <NUM>'.

In a scenario in which sharing of the access network device is supported, the network slice management network may add the identification information of the PLMN to the configuration information sent to the access network device, and set a system feature supported by a network slice in the specified PLMN. When the access network device is shared, the access network device may interact with a plurality of core networks, and each core network corresponds to a separate PLMN ID, so as to implement the system feature supported by the PLMN. In addition, each PLMN may support one or more network slices. According to the configuration information in Table <NUM>, the access network device may further determine, based on the PLMN ID corresponding to the core network, to provide the core network with configuration information corresponding to the PLMN ID.

Step <NUM>: The access network device stores the configuration information.

Specifically, the access network device stores the configuration information locally, or stores the configuration information in an external server or a database system that is specially used for data storage.

Optionally, the method further includes the following step <NUM> and step <NUM>.

Step <NUM>: The access network device determines, based on the system feature supported by the network slice, system features supported by the access network device.

In other words, after receiving and storing the configuration information sent by the network slice management network element, the access network device may further determine whether the access network device supports these system features.

Normally, the access network device can support these system features configured by the network slice management network element for the access network device. However, in some special cases, for example, in the case of a system fault, the access network device may not support these system features.

Step <NUM>: The access network device enables the system features supported by the access network device.

Specifically, the access network device enables functions, components, or the like corresponding to these system features.

Step <NUM>: The access network device sends a configuration completion indication to the network slice management network element, and correspondingly, the network slice management network element receives the configuration completion indication.

According to the foregoing method, the related information of the network slice can be configured for the access network device.

The following describes the negotiation method according to this application. Before the negotiation method is performed, related information of a network slice is configured on a terminal device, an access network device, and an AMF. A specific configuration method may be the configuration method in the foregoing implementations, or may be another configuration method. This is not limited in this application. A method for configuring the information about the network slice on the terminal device may be configured in a subscription process, or may be configured in a production process of the terminal device.

After the related information of the network slice is configured on the terminal device, the access network device, and the AMF, the following negotiation method provided in this application may be performed.

<FIG> shows a negotiation method according to this application. The method is used for negotiation between an access network device and an AMF. The method includes the following steps:
Step <NUM>: The access network device sends, to the AMF, information about a network slice supported by the access network device and a system feature supported by the network slice, and correspondingly, the AMF receives the information about the network slice supported by the access network device and the system feature supported by the network slice.

For example, the information about the network slice supported by the access network device in the access network device and the system feature supported by the network slice may be obtained by using the method in the implementation shown in <FIG>.

In an example, if network slices supported by the access network device include a network slice <NUM> (an ID of the network slice <NUM> is S-NSSAI <NUM>), a network slice <NUM> (an ID of the network slice <NUM> is S-NSSAI <NUM>), and a network slice <NUM> (an ID of the network slice <NUM> is S-NSSAI <NUM>), and system features supported by the network slice <NUM> include a system feature A and a system feature B, system features supported by the network slice <NUM> include a system feature A and a system feature B, and a system feature supported by the network slice <NUM> includes a system feature B, the information sent by the access network device to the AMF may include (the S-NSSAI <NUM>, the system feature A, and the system feature B), (the S-NSSAI <NUM>, the system feature A, and the system feature B), and (the S-NSSAI <NUM> and the system feature B).

Step <NUM>: The AMF sends, to the access network device, information about a network slice supported by a core network and a system feature supported by the network slice, and correspondingly, the access network device may receive the information about the network slice supported by the core network and the system feature supported by the network slice.

To support a plurality of service scenarios, the core network may be divided into different network slices, and a corresponding network element and service are deployed in each network slice to support the system feature supported by the network slice. To support a terminal device in simultaneously accessing a plurality of network slices, an AMF network element may simultaneously serve a plurality of network slices of the core network, to provide access and mobility management services for these network slices.

For example, the information about the network slice supported by the core network and the system feature supported by the network slice in the AMF may be obtained by using the method in the implementation shown in <FIG>.

In an example, if network slices supported by the core network include a network slice <NUM> (an ID of the network slice <NUM> is S-NSSAI <NUM>), a network slice <NUM> (an ID of the network slice <NUM> is S-NSSAI <NUM>), and a network slice <NUM> (an ID of the network slice <NUM> is S-NSSAI <NUM>), and system features supported by the network slice <NUM> include a system feature A and a system feature B, system features supported by the network slice <NUM> include a system feature A, a system feature B, and a system feature C, and a system feature supported by the network slice <NUM> includes a system feature B, the information sent by the AMF to the access network device may include (the S-NSSAI <NUM>, the system feature A, and the system feature B), (the S-NSSAI <NUM>, the system feature A, the system feature B, and the system feature C), and (the S-NSSAI <NUM> and the system feature B).

According to the foregoing method, the access network device and the AMF may exchange the information about the network slice supported by the access network device or the AMF and the system feature supported by the access network device or the AMF, to complete system feature negotiation between the access network device and the AMF.

<FIG> shows another negotiation method according to this application. The method is used for negotiation between a terminal device and an AMF. The method includes the following steps:
Step <NUM>: The terminal device sends a first request message to the AMF, where the first request message includes information about a first network slice that the terminal device requests to access and a first system feature corresponding to the first network slice. Correspondingly, the AMF may receive the first request message.

The first request message may be a registration request message, a location update message, or the like.

A network slice that the terminal device requests to access is referred to as the first network slice, and a system feature corresponding to the first network slice is referred to as the first system feature.

For example, during subscription, the terminal device may obtain the information about the first network slice and the first system feature corresponding to the first network slice. In an example, the information about the first network slice obtained by the terminal device includes, for example, S-NSSAI <NUM> and S-NSSAI <NUM>. A first system feature corresponding to a network slice <NUM> includes a system feature A, a system feature B, and a system feature D; and a first system feature corresponding to a network slice <NUM> includes a system feature B and a system feature C. In this case, the first request message sent by the terminal device to the AMF may include (the S-NSSAI <NUM>, the system feature A, the system feature B, and the system feature D), and (the S-NSSAI <NUM>, the system feature B, and the system feature C).

Step <NUM>: The AMF obtains a second system feature supported by a network for the first network slice.

The network herein may be a core network or an access network.

In an implementation, the AMF may obtain a fourth system feature supported by the core network for the first network slice, obtain a fifth system feature supported by an access network device for the first network slice, and then determine, based on the fourth system feature and the fifth system feature, the second system feature supported by the network for the first network slice.

For example, the AMF may obtain, by using the method shown in <FIG>, the information about the first network slice and the fourth system feature supported by the first network slice. Specifically, the AMF may receive, from a network slice management network element or a network slice selection network element, information about a network slice supported by the core network and a system feature supported by the network slice, where the information about the network slice includes the information about the first network slice, and the system feature supported by the network slice includes the fourth system feature. For example, fourth system features supported by the first network slice (for example, a network slice <NUM> and a network slice <NUM>) obtained by the AMF are: a system feature A, a system feature B, and a system feature C that are supported by the network slice <NUM> and a system feature B that is supported by the network slice <NUM>.

The AMF may further receive, from the access network device, information about a network slice supported by the access network device and a system feature supported by the network slice, where the information about the network slice includes the information about the first network slice, and the system feature supported by the network slice includes the fifth system feature. For example, fifth system features supported by the first network slice (for example, the network slice <NUM> and the network slice <NUM>) obtained by the AMF are: the system feature A and the system feature B that are supported by the network slice <NUM> and the system feature B that is supported by the network slice <NUM>.

The AMF may determine, based on the fourth system feature and the fifth system feature, the second system feature supported by the network for the first network slice. Specifically, the determined second system feature is an intersection set of the fourth system feature and the fifth system feature. A table is used below for description. As shown in Table <NUM>, the fourth system feature supported by the core network for the first network slice, the fifth system feature supported by the access network device for the first network slice, and the determined second system feature supported by the network for the first network slice are included.

Further, indication information may be added for each system feature in Table <NUM>, and the indication information is used to indicate whether the system feature can be accessed by a terminal device in a roaming state. For example, Table <NUM> to which the indication information is added may be shown in Table <NUM>'.

Step <NUM>: The AMF determines, based on the second system feature and the first system feature, a third system feature corresponding to the first network slice that can be used by the terminal device.

The AMF may determine, based on the second system feature and the first system feature, the third system feature corresponding to the first network slice that can be used by the terminal device. Specifically, the determined third system feature corresponding to the first network slice that can be used by the terminal device is an intersection set of the second system feature and the first system feature. A table is used below for description. As shown in Table <NUM>, the second system feature supported by the network for the first network slice, the first system feature corresponding to the first network slice supported by the terminal device, and the third system feature corresponding to the first network slice that can be used by the terminal device are included.

Further, if the terminal device is in a roaming state, and it is determined, based on the second system feature supported by the network for the first network slice, that the system feature A in the first system feature cannot be used by the terminal device in a roaming state (for example, may be determined based on Table <NUM>'), the AMF determines that the third system feature corresponding to the first network slice that can be used by the terminal device does not include the system feature A. For example, in table <NUM>, if the system feature A corresponding to the network slice <NUM> cannot be accessed by the terminal device, the determined third system feature corresponding to the first network slice that can be used by the terminal device includes the system feature B corresponding to the S-NSSAI <NUM> and the system feature B corresponding to the S-NSSAI <NUM>.

It should be noted that the system feature A, the system feature B, and the system feature C are merely names used for distinguishing purpose. In an actual application, the system features may be distinguished by using identification information of the system features.

Step <NUM>: The AMF sends, to the terminal device, the third system feature corresponding to the first network slice that can be used by the terminal device, and correspondingly, the terminal device may receive the third system feature corresponding to the first network slice that can be used by the terminal device.

In an implementation, after receiving the third system feature corresponding to the first network slice that can be used by the terminal device, the terminal device may perform the following operation: determining a system feature of the first network slice that can be used, thereby avoiding a case in which a system feature that is not allowed or a system feature that is not supported by the first network slice is requested for the first network slice after the terminal device accesses the network, and further avoiding a case in which a request for a system feature fails or is rejected, to ensure service reliability of the terminal device and reduce load of the network slices.

According to the foregoing method, negotiation, between the terminal device and the AMF, of a system feature that can be used by the terminal device can be completed.

It may be understood that to implement the foregoing functions, each network element includes a corresponding hardware structure and/or software module for implementing each function. A person skilled in the art should easily be aware that, in combination with the example units and algorithm steps described in the implementations disclosed in this specification, the present disclosure may be implemented by hardware or a combination of hardware and computer software. Whether a function is performed by hardware or hardware driven by computer software depends on particular applications and design constraints of the technical solutions. A person skilled in the art may use different methods to implement the described functions for each particular application, but it should not be considered that the implementation goes beyond the scope of the present disclosure.

When an integrated unit is used, <FIG> is a possible example block diagram of an apparatus according to an implementation of the present disclosure. The apparatus <NUM> may exist in a form of software. The apparatus <NUM> may include a processing unit <NUM> and a communications unit <NUM>. In an implementation, the communications unit <NUM> may include a receiving unit and a sending unit. The processing unit <NUM> is configured to control and manage an action of the apparatus <NUM>. The communications unit <NUM> is configured to support the apparatus <NUM> in communicating with another network entity. The apparatus <NUM> may further include a storage unit <NUM>, configured to store program code and data that are of the apparatus <NUM>.

The processing unit <NUM> may be a processor or a controller, for example, may be a general purpose central processing unit (central processing unit, CPU), a general purpose processor, a digital signal processor (digital signal processor, DSP), an application-specific integrated circuit (application specific integrated circuit, ASIC), a field programmable gate array (field programmable gate array, FPGA) or another programmable logic device, a transistor logic device, a hardware component, or any combination thereof. The controller/processor may implement or execute various example logical blocks, modules, and circuits described with reference to content disclosed in the present disclosure. Alternatively, the processor may be a combination of processors implementing a computing function, for example, a combination of one or more microprocessors, or a combination of the DSP and a microprocessor. The communications unit <NUM> may be a communications interface, a transceiver, a transceiver circuit, or the like. The communications interface is a general term. During specific implementation, the communications interface may include a plurality of interfaces. The storage unit <NUM> may be a memory.

The apparatus <NUM> may be an access network device, or may be a chip in an access network device. The processing unit <NUM> may support the apparatus <NUM> in performing the actions of the access network device in the foregoing method examples. For example, the processing unit <NUM> is configured to support the apparatus <NUM> in performing step <NUM> to step <NUM> in <FIG>, step <NUM> and step <NUM> in <FIG>, and/or another process used for the technology described in this specification. The communications unit <NUM> is configured to support the apparatus <NUM> in communicating with a mobility management network element, a network slice management network element, and a terminal device. For example, the communications unit is configured to support the apparatus <NUM> in performing step <NUM> and step <NUM> in <FIG>, step <NUM> and step <NUM> in <FIG>, and step <NUM> and step <NUM> in <FIG>.

Specifically, when the communications unit <NUM> includes the sending unit and the receiving unit, in an implementation, the receiving unit is configured to receive a first request message from a terminal device, where the first request message includes information about a first network slice that the terminal device requests to access and a first system feature corresponding to the first network slice;
the processing unit is configured to: obtain a second system feature supported by a network for the first network slice, and determine, based on the second system feature and the first system feature, a third system feature corresponding to the first network slice that can be used by the terminal device; and the sending unit is configured to send, to the terminal device, the third system feature corresponding to the first network slice that can be used by the terminal device.

In a possible implementation, the processing unit is specifically configured to: obtain a fourth system feature supported by a core network for the first network slice, and obtain a fifth system feature supported by an access network device for the first network slice; and determine, based on the fourth system feature and the fifth system feature, the second system feature supported by the network for the first network slice.

In a possible implementation, the receiving unit is further configured to receive, from a network slice management network element or a network slice selection network element, information about a network slice supported by the core network and a system feature supported by the network slice, where the information about the network slice includes information about the first network slice, and the system feature supported by the network slice includes the fourth system feature.

In a possible implementation, the receiving unit is further configured to receive, from the access network device, information about a network slice supported by the access network device and a system feature supported by the network slice, where the information about the network slice includes information about the first network slice, and the system feature supported by the network slice includes the fifth system feature.

In a possible implementation, if the terminal device is in a roaming state, and it is determined, based on the second system feature supported by the network for the first network slice, that a system feature A in the first system feature cannot be used by the terminal device in a roaming state, the processing unit is further configured to determine that the third system feature corresponding to the first network slice that can be used by the terminal device does not include the system feature A.

Specifically, when the communications unit <NUM> includes the sending unit and the receiving unit, in still another implementation, the sending unit is configured to send, to the mobility management network element, information about a network slice supported by the access network device and a system feature supported by the network slice; and the receiving unit is configured to receive, from the mobility management network element, information about a network slice supported by the mobility management network element and a system feature supported by the network slice.

The apparatus <NUM> may alternatively be the network slice management network element in this application, or may be a chip in the network slice management network element. The processing unit <NUM> may support the apparatus <NUM> in performing the actions of the network slice management network element in the foregoing method examples. The communications unit <NUM> may support the apparatus <NUM> in communicating with the access network device and the mobility management network element. For example, the communications unit <NUM> is configured to support the apparatus <NUM> in performing step <NUM> and step <NUM> in <FIG> and step <NUM> and step <NUM> in <FIG>.

Specifically, when the communications unit <NUM> includes the sending unit and the receiving unit, in an implementation, the sending unit is configured to send configuration information to a network device, where the configuration information includes information about a network slice and a system feature supported by the network slice; and the receiving unit is configured to receive a configuration completion indication from the network device.

In a possible implementation, the network device is an access network device, a mobility management network element, a session management network element, or a network slice selection network element.

In a possible implementation, the network device is an access network device, and the configuration information further includes identification information of a public land mobile network PLMN to which the network slice belongs.

In a possible implementation, the network device is a mobility management network element or a network slice selection network element; and the configuration information further includes indication information, and the indication information is used to indicate whether the system feature supported by the network slice can be used by a terminal device in a roaming state.

The apparatus <NUM> may alternatively be the terminal device in this application, or may be a chip in the terminal device. For example, the processing unit <NUM> may support the apparatus <NUM> in performing the actions of the terminal device in the foregoing method examples. The communications unit <NUM> may support communication between the apparatus <NUM> and an access network device. For example, the communications unit <NUM> is configured to support the apparatus <NUM> in performing step <NUM> and step <NUM> in <FIG>.

Specifically, when the communications unit <NUM> includes the sending unit and the receiving unit, in an implementation, the sending unit is configured to send a first request message to a mobility management network element, where the first request message includes information about a first network slice that the terminal device requests to access and a first system feature corresponding to the first network slice; and the receiving unit is configured to receive, from the mobility management network element, a third system feature corresponding to the first network slice that can be used by the terminal device.

The apparatus <NUM> may alternatively be the network device in this application, or may be a chip in the network device. The network device may be a mobility management network element, a session management network element, or an access network device. The processing unit <NUM> may support the apparatus <NUM> in performing the actions of the network device in the foregoing method examples. For example, the processing unit <NUM> is configured to support the apparatus <NUM> in performing step <NUM> in <FIG> and/or another process of the technology described in this specification. The communications unit <NUM> is configured to support communication between the apparatus <NUM> and a network slice management network element. For example, the communications unit is configured to support the apparatus <NUM> in performing step <NUM> and step <NUM> in <FIG>.

Specifically, when the communications unit <NUM> includes the sending unit and the receiving unit, in an implementation, the receiving unit is configured to receive configuration information from the network slice management network element, where the configuration information includes information about a network slice and a system feature supported by the network slice; the processing unit is configured to store the configuration information in the storage unit; and the sending unit is configured to send a configuration completion indication to the network slice management network element.

In a possible implementation, the network device is a network slice selection network element, and the receiving unit is further configured to receive, from a mobility management network element, the information about the network slice, to request to obtain the system feature supported by the network slice; and the sending unit is further configured to send the system feature supported by the network slice to the mobility management network element.

In a possible implementation, the network device is an access network device, and the processing unit is further configured to: determine, based on the system feature supported by the network slice, a system feature supported by the access network device; and enable the system feature supported by the access network device.

In a possible implementation, the system feature includes but is not limited to any one or more of the following: an internet protocol IP protocol data unit session PDU session, a short messaging service over non-access stratum SMS over NAS, and a location service LCS.

<FIG> is a schematic diagram of an apparatus according to this application. The apparatus may be the network slice management network element, the mobility management network element, or the session management network element. The apparatus <NUM> includes a processor <NUM>, a communications interface <NUM>, and a memory <NUM>. Optionally, the apparatus <NUM> may further include a bus <NUM>. The communications interface <NUM>, the processor <NUM>, and the memory <NUM> may be connected to each other by using the bus <NUM>. The bus <NUM> may be a peripheral component interconnect (peripheral component interconnect, PCI for short) bus, an extended industry standard architecture (extended industry standard architecture, EISA for short) bus, or the like. The bus <NUM> may be classified into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is used to represent the bus in <FIG>, but this does not mean that there is only one bus or only one type of bus.

The processor <NUM> may be a CPU, a microprocessor, an ASIC, or one or more integrated circuits configured to control program execution in the solutions of this application.

The communications interface <NUM> uses any apparatus such as a transceiver that is configured to communicate with another device or a communications network, such as the Ethernet, a radio access network (radio access network, RAN), a wireless local area network (wireless local area networks, WLAN), or a wired access network.

The memory <NUM> may be a read-only memory (read-only memory, ROM) or another type of static storage device that can store static information and instructions, or a random access memory (random access memory, RAM) or another type of dynamic storage device that can store information and instructions, or may be an electrically erasable programmable read-only memory (electrically erasable programmable read-only memory, EEPROM), a compact disc read-only memory (compact disc read-only memory, CD-ROM) or another compact disc storage, or an optical disc storage (including a compressed optical disc, a laser disc, an optical disc, a digital versatile disc, a Blu-ray disc, and the like), a magnetic disk storage medium or another magnetic storage device, or any other medium that can be used to carry or store expected program code in a form of an instruction or a data structure and that can be accessed by a computer, but is not limited thereto. The memory may exist independently, and is connected to the processor by using the bus <NUM>. Alternatively, the memory may be integrated with the processor.

The memory <NUM> is configured to store a computer-executable instruction for executing the solutions in this application, and the processor <NUM> controls the execution of the computer-executable instruction. The processor <NUM> is configured to execute the computer-executable instruction stored in the memory <NUM>, to implement the configuration method and the negotiation method that are provided in the foregoing implementations of this application.

Optionally, the computer-executable instruction in this implementation of this application may also be referred to as application program code, and this is not specifically limited in this implementation of this application.

<FIG> is a simplified schematic diagram of a possible design structure of a terminal device according to an implementation of the present disclosure. The terminal device <NUM> includes a transmitter <NUM>, a receiver <NUM>, and a processor <NUM>. The processor <NUM> may alternatively be a controller, and is represented as a "controller/processor <NUM>" in <FIG>. Optionally, the terminal device <NUM> may further include a modem processor <NUM>. The modem processor <NUM> may include an encoder <NUM>, a modulator <NUM>, a decoder <NUM>, and a demodulator <NUM>.

In an example, the transmitter <NUM> adjusts (for example, performs analog conversion, filtering, amplification, and up-conversion on) an output sample and generates an uplink signal. The uplink signal is transmitted to the access network device in the foregoing implementations through an antenna. On a downlink, the antenna receives a downlink signal transmitted by the access network device in the foregoing implementations. The receiver <NUM> adjusts (for example, performs filtering, amplification, down-conversion, and digitization on) the signal received from the antenna and provides an input sample. In the modem processor <NUM>, the encoder <NUM> receives service data and a signaling message that are to be sent over an uplink, and processes (for example, formats, encodes, and interleaves) the service data and the signaling message. The modulator <NUM> further processes (for example, performs symbol mapping and modulation on) encoded service data and an encoded signaling message and provides the output sample. The demodulator <NUM> processes (for example, demodulates) the input sample and provides symbol estimation. The decoder <NUM> processes (for example, de-interleaves and decodes) the symbol estimation and provides decoded data and a decoded signaling message that are to be sent to the terminal device <NUM>. The encoder <NUM>, the modulator <NUM>, the demodulator <NUM>, and the decoder <NUM> may be implemented by the combined modem processor <NUM>. These units perform processing based on a radio access technology (for example, an access technology of an LTE or another evolution system) used by a radio access network. It should be noted that when the terminal device <NUM> does not include the modem processor <NUM>, the foregoing functions of the modem processor <NUM> may alternatively be performed by the processor <NUM>.

The processor <NUM> controls and manages an action of the terminal device <NUM>, and is configured to perform a process performed by the terminal device <NUM> in the foregoing implementations of this application. For example, the processor <NUM> is further configured to perform the processes of the terminal device in the methods shown in <FIG> and/or another process of the technical solutions described in this application.

Further, the terminal device <NUM> may further include a memory <NUM>, and the memory <NUM> is configured to store program code and data of the terminal device <NUM>.

<FIG> is a possible schematic structural diagram of an access network device according to an implementation of the present disclosure. The access network device <NUM> includes a processor <NUM> and a communications interface <NUM>. The processor <NUM> may alternatively be a controller, and is represented as a "controller/processor <NUM>" in <FIG>. The communications interface <NUM> is configured to support the access network device in communicating with another network element (for example, a mobility management network element or a network slice management network element). Further, the access network device <NUM> may further include a transmitter/receiver <NUM>. The transmitter/receiver <NUM> is configured to support radio communication between the access network device and the terminal device in the foregoing implementations. The processor <NUM> may perform various functions for communicating with the terminal device. On an uplink, an uplink signal, from the terminal device received through an antenna, is demodulated (for example, a high frequency signal is demodulated into a baseband signal) by the receiver <NUM>, and is further processed by the processor <NUM> to restore service data and a signaling message that are sent by the terminal device. On a downlink, the service data and the signaling message are processed by the processor <NUM>, and are modulated (for example, a baseband signal is modulated into a high frequency signal) by the transmitter <NUM> to generate a downlink signal. The downlink signal is transmitted to the terminal device through the antenna. It should be noted that the foregoing demodulation or modulation function may alternatively be implemented by the processor <NUM>.

For example, the processor <NUM> is further configured to perform the processes of the access network device in the methods shown in <FIG> and/or another process of the technical solutions described in this application.

Further, the access network device <NUM> may further include a memory <NUM>, and the memory <NUM> is configured to store program code and data of the access network device <NUM>.

It may be understood that <FIG> shows only a simplified design of the access network device <NUM>. In actual application, the access network device <NUM> may include any quantity of transmitters, receivers, processors, controllers, memories, communications units, and the like, and all access network devices that can implement the implementations of the present disclosure fall within the protection scope of the implementations of the present disclosure.

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

The various illustrative logical units and circuits described in the implementations of this application may implement or operate the described functions through a general purpose processor, a digital signal processor, an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or another programmable logical apparatus, a discrete gate or transistor logic, a discrete hardware component, or a design of any combination thereof. The general-purpose processor may be a microprocessor. Optionally, the general-purpose processor may alternatively be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented by a combination of computing apparatuses, such as a digital signal processor and a microprocessor, a plurality of microprocessors, one or more microprocessors in combination with a digital signal processor core, or any other similar configuration.

Steps of the methods or algorithms described in the implementations of this application may be directly embedded into hardware, a software unit executed by a processor, or a combination thereof. The software unit may be stored in a RAM memory, a flash memory, a ROM memory, an EPROM memory, an EEPROM memory, a register, a hard disk, a removable magnetic disk, a CD-ROM, or a storage medium of any other form in the art. For example, the storage medium may connect to a processor so that the processor may read information from the storage medium and write information to the storage medium. Optionally, the storage medium may further be integrated into a processor. The processor and the storage medium may be disposed in an ASIC, and the ASIC may be disposed in a terminal device. Optionally, the processor and the storage medium may also be disposed in different components of a terminal device.

Claim 1:
A negotiation method, comprising:
receiving (<NUM>), by a mobility management network element, a first request message from a terminal device, wherein the first request message comprises information about a first network slice that the terminal device requests to access and a first system feature corresponding to the first network slice;
obtaining (<NUM>), by the mobility management network element, a second system feature supported by a network for the first network slice;
determining (<NUM>), by the mobility management network element based on the second system feature and the first system feature, a third system feature corresponding to the first network slice that can be used by the terminal device, wherein the determined third system feature is an intersection set of the second system feature and the first system feature; and
sending (<NUM>), by the mobility management network element, the third system feature corresponding to the first network slice that can be used by the terminal device to the terminal device.