Slice processing method and device, and communication equipment

Obtaining and sending slice lists and effective conditions supported by multiple base stations through the core network solves the problem that terminals cannot carry out different slice services at the same time in the prior art, and improves the user experience and flexibility of wireless networks.

CN116133111BActive Publication Date: 2024-11-08CHINA MOBILE COMM LTD RES INST +1
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202111348448.9
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2021-11-15
Publication Date
2024-11-08
Estimated Expiration
2041-11-15

AI Technical Summary

Technical Problem

In the prior art, network slicing standards are strictly formulated, which makes it impossible for terminals to carry out different slicing services in the same area at the same time, resulting in poor user experience and increasing inconvenience in wireless network deployment and resource use.

Method used

The core network obtains the slice list supported by multiple base stations, determines the slice list and effective conditions allowed by the terminal, and sends it to the base station and terminal to realize flexible support for slice services.

Benefits of technology

It realizes that the terminals carry out different slice services in the same area at the same time, improves the user experience, and improves the flexibility and resource utilization efficiency of wireless networks.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN116133111B_ABST
    Figure CN116133111B_ABST
Patent Text Reader

Abstract

The present application discloses a slice processing method and apparatus, and a communication device, the method comprising: a core network obtains a first slice list supported by a first base station and a second slice list supported by a second base station; wherein the first base station is a base station accessed by a terminal; the core network determines a third slice list allowed by the terminal and / or the validity conditions of at least some slices in the third slice list; the core network sends the third slice list and / or the validity conditions of at least some slices in the third slice list to the first base station and / or the terminal.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of wireless communication technology, and in particular to a slicing processing method and apparatus, and communication equipment. Background Art

[0002] Generally, different network slices (also referred to as slices) correspond to different service requirements. Therefore, in actual deployment, different base stations or different frequencies or cells of the same base station often support different types of slices. In order to support multiple slice services concurrently in the same coverage area, cells with different frequencies need to be deployed to support different slices.

[0003] However, the network slicing standard formulated very strict and unfriendly guidelines for actual deployment on the wireless side at the beginning of its formulation, namely, the tracking area (TA) to which the cell belongs must be planned according to whether the slices supported by the cell are the same, and the slice types in the registration area configured by the core network for the terminal must be consistent, that is, the terminal moves between base stations in the registration area to ensure unified slice support. This guideline does bring a certain degree of flexibility from the perspective of core network management, but it brings great problems and inconveniences to the deployment of wireless networks and the flexible use of resources. Summary of the invention

[0004] In order to solve the above technical problems, the embodiments of the present invention provide a slice processing method and device, a communication device, a chip, and a computer-readable storage medium.

[0005] The slicing processing method provided in the embodiment of the present application includes:

[0006] The core network obtains a first slice list supported by a first base station and a second slice list supported by a second base station; wherein the first base station is a base station accessed by the terminal;

[0007] The core network determines a third slice list allowed by the terminal and / or a validity condition of at least some slices in the third slice list;

[0008] The core network sends the third slice list and / or the effectiveness conditions of at least some slices in the third slice list to the first base station and / or the terminal.

[0009] The slice processing device provided in the embodiment of the present application includes:

[0010] An acquisition unit, configured to acquire a first slice list supported by a first base station and a second slice list supported by a second base station; wherein the first base station is a base station accessed by a terminal;

[0011] A determining unit, configured to determine a validation condition of a third slice list and / or at least some slices in the third slice list allowed by the terminal;

[0012] A sending unit is used to send the third slice list and / or the effectiveness conditions of at least some slices in the third slice list to the first base station and / or the terminal.

[0013] The communication device provided in an embodiment of the present application includes: a processor and a memory, the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute any one of the above-mentioned slicing processing methods.

[0014] The chip provided in the embodiment of the present application includes: a processor, which is used to call and run a computer program from a memory, so that a device equipped with the chip executes any one of the above methods.

[0015] The core computer-readable storage medium provided in the embodiment of the present application is used to store a computer program, and the computer program enables a computer to execute any one of the above methods.

[0016] In the technical solution of the embodiment of the present application, the terminal can carry out different slice services at the same time, thereby improving the user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] Figure 1 It is a schematic diagram of an application scenario of an embodiment of the present application;

[0018] Figure 2 It is a schematic diagram of the end-to-end registration process of network slices;

[0019] Figure 3 It is a schematic diagram of the slice planning criteria;

[0020] Figure 4 It is a schematic diagram of the process of the slicing processing method provided in the embodiment of the present application;

[0021] Figure 5 is a schematic diagram of application example 1 provided in an embodiment of the present application;

[0022] Figure 6 It is a schematic diagram of application example 2 provided in the embodiment of the present application;

[0023] Figure 7 It is a schematic diagram of the structural composition of the slice processing device provided in an embodiment of the present application;

[0024] Figure 8 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

[0025] Fig. 9 It is a schematic structural diagram of the chip of an embodiment of the present application. DETAILED DESCRIPTION

[0026] The following will describe the technical solutions in the embodiments of the present application in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0027] Figure 1 It is a schematic diagram of an application scenario of an embodiment of the present application.

[0028] like Figure 1 As shown, the communication system 100 may include a terminal 110 and a network device 120. The network device 120 may communicate with the terminal 110 via an air interface. The terminal 110 and the network device 120 support multi-service transmission.

[0029] It should be understood that the embodiments of the present application are only exemplified by the communication system 100, but the embodiments of the present application are not limited thereto. That is to say, the technical solutions of the embodiments of the present application can be applied to various communication systems, such as: Long Term Evolution (LTE) system, LTE Time Division Duplex (TDD), Universal Mobile Telecommunication System (UMTS), Internet of Things (IoT) system, Narrow Band Internet of Things (NB-IoT) system, enhanced Machine Type Communications (eMTC) system, 5G communication system (also called New Radio (NR) communication system), or future communication systems, etc.

[0030] exist Figure 1 In the communication system 100 shown, the network device 120 may be an access network device that communicates with the terminal 110. The access network device may provide communication coverage for a specific geographical area, and may communicate with the terminal 110 (eg, UE) located in the coverage area.

[0031] The network device 120 may be an evolved Node B (eNB or eNodeB) in a Long Term Evolution (LTE) system, or a Next Generation Radio Access Network (NG RAN) device, or a base station (gNB) in an NR system, or a wireless controller in a Cloud Radio Access Network (CRAN), or the network device 120 may be a relay station, an access point, a vehicle-mounted device, a wearable device, a hub, a switch, a bridge, a router, or a network device in a future evolved Public Land Mobile Network (PLMN), etc.

[0032] The terminal 110 may be any terminal, including but not limited to a terminal connected to the network device 120 or other terminals by wire or wireless connection.

[0033] For example, the terminal 110 may refer to an access terminal, a user equipment (UE), a user unit, a user station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent, or a user device. The access terminal may be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, an IoT device, a satellite handheld terminal, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal in a 5G network, or a terminal in a future evolution network, etc.

[0034] The terminal 110 may be used for device to device (D2D) communication.

[0035] The wireless communication system 100 may also include a core network device 130 for communicating with the base station, and the core network device 130 may be a 5G core network (5G Core, 5GC) device, for example, an access and mobility management function (Access and Mobility Management Function, AMF), and for example, an authentication server function (Authentication Server Function, AUSF), and for example, a user plane function (User Plane Function, UPF), and for example, a session management function (Session Management Function, SMF). Optionally, the core network device 130 may also be an evolved packet core (Evolved Packet Core, EPC) device of the LTE network, for example, a session management function + a data gateway (Session Management Function + Core Packet Gateway, SMF + PGW-C) device of the core network. It should be understood that SMF + PGW-C can simultaneously implement the functions that SMF and PGW-C can implement. In the process of network evolution, the above-mentioned core network device may also be called other names, or a new network entity may be formed by dividing the functions of the core network, which is not limited to the embodiments of the present application.

[0036] The functional units in the communication system 100 may also establish connections through next generation (NG) network interfaces to achieve communication.

[0037] For example, the terminal establishes an air interface connection with the access network device through the NR interface for transmitting user plane data and control plane signaling; the terminal can establish a control plane signaling connection with the AMF through the NG interface 1 (N1 for short); the access network device, such as the next-generation wireless access base station (gNB), can establish a user plane data connection with the UPF through the NG interface 3 (N3 for short); the access network device can establish a control plane signaling connection with the AMF through the NG interface 2 (N2 for short); the UPF can establish a control plane signaling connection with the SMF through the NG interface 4 (N4 for short); the UPF can exchange user plane data with the data network through the NG interface 6 (N6 for short); the AMF can establish a control plane signaling connection with the SMF through the NG interface 11 (N11 for short); the SMF can establish a control plane signaling connection with the PCF through the NG interface 7 (N7 for short).

[0038] Figure 1A base station, a core network device and two terminals are shown exemplarily. Optionally, the wireless communication system 100 may include multiple base station devices and each base station may include another number of terminals within its coverage area, which is not limited in the embodiments of the present application.

[0039] It should be noted that Figure 1 It is only to illustrate the system to which the present application is applicable in the form of an example. Of course, the method shown in the embodiment of the present application can also be applied to other systems. In addition, the terms "system" and "network" are often used interchangeably in this article. The term "and / or" in this article is only a description of the association relationship of the associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the associated objects before and after are in an "or" relationship. It should also be understood that the "indication" mentioned in the embodiment of the present application can be a direct indication, an indirect indication, or an indication of an association relationship. For example, A indicates B, which can mean that A directly indicates B, for example, B can be obtained through A; it can also mean that A indirectly indicates B, for example, A indicates C, B can be obtained through C; it can also mean that there is an association relationship between A and B. It should also be understood that the "correspondence" mentioned in the embodiment of the present application can mean that there is a direct or indirect correspondence relationship between the two, or it can mean that there is an association relationship between the two, or it can mean that there is an indication and being indicated, configuration and being configured, etc. It should also be understood that the "predefined" or "predefined rules" mentioned in the embodiments of the present application can be implemented by pre-saving corresponding codes, tables or other methods that can be used to indicate relevant information in devices (for example, including terminals and network devices), and the present application does not limit its specific implementation method. For example, predefined can refer to the definition in the protocol. It should also be understood that in the embodiments of the present application, the "protocol" may refer to a standard protocol in the field of communications, such as LTE protocols, NR protocols, and related protocols used in future communication systems, and the present application does not limit this.

[0040] To facilitate understanding of the technical solutions of the embodiments of the present application, the relevant technologies of the embodiments of the present application are described below. The following related technologies can be arbitrarily combined with the technical solutions of the embodiments of the present application as optional solutions, and they all belong to the protection scope of the embodiments of the present application.

[0041] Network slicing is a technology that provides an end-to-end logical "private network" based on a unified infrastructure and a unified network. It flexibly allocates network resources and flexibly combines network capabilities to virtualize multiple logical sub-networks with different characteristics based on a mobile communication network, providing on-demand customized network services for different scenarios. Network slicing can provide differentiated services for industries with different service requirements (such as latency, reliability, capacity, isolation, and other functions). The operator network will not only serve information consumption services with "best effort transmission" as the communication demand feature, but also meet production control services with "deterministic transmission" as the communication demand.

[0042] The end-to-end registration process of network slices is as follows: Figure 2 As shown, the following steps are included:

[0043] Step 201: The terminal has a single network slice selection assistance information (S-NSSAI) configuration corresponding to the Public Land Mobile Network (PLMN).

[0044] Step 202: The base station and the core network interact to obtain slice information supported by each other.

[0045] Step 203: The terminal sends a user registration request message to the base station, carrying a requested S-NSSAI (requested S-NSSAI).

[0046] Here, S-NSSAI is used to identify a network slice.

[0047] Here, the terminal may carry one or more requested S-NSSAIs in the user registration request message, wherein the one or more requested S-NSSAIs are used to identify one or more slices of interest to the terminal.

[0048] Step 204: The base station selects a core network element according to the requested S-NSSAI reported by the terminal.

[0049] Step 205: The base station sends a user registration request message to the selected core network element.

[0050] Step 206: The core network element requests the unified data management network element (UDM) to obtain the UE context (UEcontext) of the terminal. If not, the core network element initiates a request to the network slice selection function network element (Network Slice SelectionFunction, NSSF) to further obtain the AMF service set or IP address of the terminal.

[0051] Step 207: The core network element sends the S-NSSAI allowed by the terminal to the base station, and the base station forwards the S-NSSAI allowed by the terminal to the terminal.

[0052] Here, the core network element configures the list of slices allowed in the terminal registration area (corresponding to the S-NSSAI allowed by the terminal) to the terminal through a non-access stratum (NAS) message. When determining the list of slices allowed in the registration area, the core network element comprehensively considers information such as the slices of interest to the terminal, the slices supported by the base station connected to the core network element, and the slices subscribed by the terminal in the HSS.

[0053] Step 208: The core network element sends a user registration acceptance message to the terminal.

[0054] Step 209: The terminal saves the allowed S-NSSAI.

[0055] Step 210: The terminal sends a user registration completion message to the core network element.

[0056] In the above solution, the core network element may be an access and mobility management function (AMF) element.

[0057] Generally speaking, different network slices correspond to different business requirements. For example, enhanced Mobile Broadband (eMBB) and Ultra-Reliable Low-Latency Communications (URLLC) have different requirements for network frequency, bandwidth and parameter configuration. Therefore, in actual deployment, different base stations or different frequencies or cells of the same base station often support different types of slices. For example, 5G 2.6GHz needs to be synchronized with LTE to avoid interference between base stations, so it needs to configure a 5ms uplink and downlink conversion period. There is no problem in supporting eMBB slices, but the 5ms conversion period cannot meet the 1ms air interface delay of URLLC, so it cannot support some URLLC slices. It is necessary to configure a shorter conversion period through another frequency such as 4.9GHz to support URLLC slices.

[0058] Therefore, in order to support multiple slice services concurrently in the same coverage area, it is necessary to deploy cells with different frequencies to support different slices.

[0059] However, the network slicing standard was formulated in the early stage of formulation with very strict and unfriendly rules for actual deployment on the wireless side, that is, the TA to which the cell belongs must be planned according to whether the slices supported by the cell are the same, and the slice types configured by the core network for the terminal in the registration area must be consistent, that is, the terminal moves between base stations in the registration area to ensure uniform slice support. This rule does bring a certain degree of flexibility from the perspective of core network management, but it brings great problems and inconvenience to the deployment of wireless networks and the flexible use of resources.

[0060] As an example, Figure 3 As shown in the figure, the 700MHz or 2.6GHz cell of the macro station only supports eMBB slices (i.e., slice 1), and some cells in the coverage area deploy 4.9GHz frequency points to support URLLC slices (i.e., slice 2). The slices of interest to the terminal in the coverage area include slice 1 and slice 2. Figure 2 In the process shown, the terminal carries the requested S-NSSAI in the user registration request message, including S-NSSAI-1 (i.e., S-NSSAI of slice 1) and S-NSSAI-2 (i.e., S-NSSAI of slice 2). At the same time, cell 1 (i.e., macro cell) and cell 2 (i.e., small cell) inform the core network that they support slice 1 and slice 2 respectively. Since the terminal initiates access from cell 1, although the slices it is interested in include slice 1 and slice 2, the list of allowed slices sent by the core network to the terminal only includes slice 1. Therefore, even if the terminal moves to the coverage of cell 2, cell 1 and cell 2 have the ability to provide the terminal with services of slice 1 and slice 2 at the same time, it cannot be achieved according to the current mechanism because the terminal is not allowed to initiate services of slice 2. If the terminal wants to initiate services of slice 2, it can only be achieved by changing the registration area, which results in the terminal being unable to enjoy the services of slice 1 and slice 2 at the same time in this area, but in actual deployment, this demand is very urgent.

[0061] It should be noted that the above problem is only one of the problems existing in the current network slicing mechanism. In addition, the current network slicing mechanism may also have other problems. For example, even if the network can flexibly configure cell 2 to support both slices 1 and 2, if the terminal needs to carry out slice 1 and slice 2 services at the same time within cell 2, it needs to initiate switching across registration areas (RA), which brings additional signaling overhead.

[0062] To this end, the following technical solutions of the embodiments of the present application are proposed. The technical solutions of the embodiments of the present application mainly solve the problem that the TA to which the existing cell belongs must be planned according to whether the supported slices are the same, and the slice types in the registration area configured by the core network for the terminal must be consistent, which causes the terminal to be unable to carry out different slice services through the terminal at the same time through dual connection or switching within RA.

[0063] To facilitate understanding of the technical solutions of the embodiments of the present application, the technical solutions of the present application are described in detail below through specific embodiments. The above related technologies can be combined arbitrarily with the technical solutions of the embodiments of the present application as optional solutions, and they all belong to the protection scope of the embodiments of the present application. The embodiments of the present application include at least part of the following contents.

[0064] It should be noted that the technical solution of the embodiment of the present application can be applied to 5G networks, but is not limited to this, and can also be applied to other networks, such as 6G networks, future mobile communication networks, etc.

[0065] Figure 4 is a flow chart of a slicing processing method provided in an embodiment of the present application, such as Figure 4 As shown, the slicing processing method includes:

[0066] Step 401: The core network obtains a first slice list supported by a first base station and a second slice list supported by a second base station; wherein the first base station is a base station accessed by a terminal.

[0067] In the embodiment of the present application, the core network may obtain a first slice list supported by the first base station and a second slice list supported by the second base station in the following manner:

[0068] Method 1: The core network receives a first slice list supported by the first base station and a second slice list supported by the second base station, which are sent by the first base station.

[0069] Here, the first base station can obtain the second slice list supported by the second base station from the second base station, and then send the first slice list supported by the first base station and the second slice list supported by the second base station to the core network.

[0070] Method 2: The core network receives a first slice list supported by a first base station sent by a first base station, and receives a second slice list supported by the second base station sent by a second base station.

[0071] Here, the first base station sends the first slice list supported by itself to the core network, and the second base station sends the second slice list supported by itself to the core network.

[0072] In some optional implementations, the core network receives first information sent by the first base station or the second base station, and the first information is used to indicate that the second base station can be used as a secondary base station of the first base station and / or the first base station can be used as a primary base station of the second base station. Here, optionally, the first information can be called network topology information, and this application does not limit the name of the first information.

[0073] In some optional embodiments, the core network receives second information sent by the first base station or the second base station, where the second information is used to indicate the effectiveness condition of each slice in the second slice list.

[0074] In an embodiment of the present application, the first slice list supported by the first base station includes a slice list supported by each TA in one or more TAs supported by the first base station; the second slice list supported by the second base station includes a slice list supported by each TA in one or more TAs supported by the second base station.

[0075] Step 402: The core network determines the validity conditions of the third slice list allowed by the terminal and / or at least some slices in the third slice list.

[0076] In some optional embodiments, the core network determines the effectiveness conditions of the third slice list allowed by the terminal and / or at least some slices in the third slice list based on at least one of the first slice list, the second slice list, the first information and the second information; wherein the first information is used to indicate that the second base station can serve as a secondary base station of the first base station and / or the first base station can serve as a main base station of the second base station, and the second information is used to indicate the effectiveness conditions of each slice in the second slice list.

[0077] In this embodiment of the present application, at least some of the slices in the third slice list belong to the second slice list.

[0078] In the embodiment of the present application, the validity condition includes at least one of the following:

[0079] A signal quality of the second base station or a cell of the second base station is greater than or equal to a first threshold;

[0080] The terminal is located in the second base station or in a specific area covered by a cell of the second base station.

[0081] Step 403: The core network sends the third slice list and / or the effectiveness conditions of at least some slices in the third slice list to the first base station and / or the terminal.

[0082] In some optional implementations, the core network sends at least one of an initial context request message, a connection indication message, an AMF control plane reset message, a user information transfer message, a switching request message, a path switching request confirmation message, an initial UE message, a downlink NAS message, and a routing NAS request message to the first base station, and the message carries the validity condition of the third slice list and / or at least some slices in the third slice list; and / or,

[0083] In some optional implementations, the core network sends a user registration acceptance message to the terminal, and the user registration acceptance message carries the effectiveness conditions of the third slice list and / or at least some slices in the third slice list.

[0084] In the embodiment of the present application, after the core network sends the third slice list and / or the validity conditions of at least some slices in the third slice list to the first base station and / or the terminal through the above solution, the slice service can be carried out.

[0085] In the embodiment of the present application, when the effectiveness condition of the target slice in the second slice list is met, the core network sends a PDU session resource establishment request message to the first base station, and the PDU session resource establishment request message carries the PDU session resource request corresponding to the target slice; the core network receives a PDU session resource establishment reply message sent by the first base station, and the PDU session resource establishment reply message carries the address information of the PDU session corresponding to the target slice. Further, a reconfiguration message is sent by the first base station to the terminal, wherein the reconfiguration message carries the PDU session request reply message corresponding to the target slice.

[0086] In the above scheme, the PDU session resource establishment request message is used to trigger the establishment of a dual connection between the first base station and the second base station for the terminal, wherein the establishment of the dual connection includes: the establishment of air interface resources of the target slice on the second base station side. Further, the air interface resources here include SCG bearers and / or SCG offload bearers on the second base station side.

[0087] In some optional implementations, when the terminal triggers the service of the target slice (that is, the calling (MO) service of the target slice), the terminal determines whether the validity condition of the target slice is met. Specifically, if the terminal determines that the validity condition of the target slice is met, before the core network sends a PDU session resource establishment request message to the first base station, the method further includes: the core network receives a service request message sent by the terminal, and the service request message carries the PDU session request of the target slice.

[0088] In some optional implementations, when the core network triggers the service of the target slice (that is, the called (MT) service of the target slice), the core network determines whether the validity condition of the target slice is met. Specifically, the core network determines whether the validity condition of the target slice is met based on the first indication information sent by the first base station or the terminal.

[0089] The technical solution of the embodiment of the present application is illustrated below with reference to specific application examples.

[0090] Application Example 1

[0091] like Figure 5 As shown, the 700MHz or 2.6GHz cell of the macro station only supports eMBB slices (i.e., slice 1), and some cells in the coverage area deploy 4.9GHz frequency points to support URLLC slices (i.e., slice 2). The slices of interest to the terminal in the coverage area include slice 1 and slice 2. The terminal carries the requested S-NSSAI in the user registration request message, including S-NSSAI-1 (i.e., S-NSSAI of slice 1) and S-NSSAI-2 (i.e., S-NSSAI of slice 2). At the same time, cell 1 (i.e., macro station cell) and cell 2 (i.e., small station cell) respectively inform the core network that they support slice 1 and slice 2 respectively. The terminal initiates access from cell 1, and the slices of interest include slice 1 and slice 2. The allowed slice list sent by the core network to the terminal includes slice 1 and slice 2, as well as the corresponding validity conditions of slice 1 and slice 2. Therefore, when the terminal moves to the coverage of cell 2, cell 1 and cell 2 have the ability to provide services of slice 1 and slice 2 to the terminal at the same time, and the terminal is allowed to initiate services of slice 1 and slice 2 at the same time.

[0092] Application Example 2

[0093] Figure 6 is a flow chart of a slicing processing method provided in an embodiment of the present application, such as Figure 6 As shown, it includes the following processes:

[0094] Step 601: In addition to sending the list of slices supported by its cell TA to the core network, base station 1 also sends the identifier of the base station or cell that can potentially serve as its auxiliary node and the list of slices supported by its cell TA. Optionally, it can also send the trigger conditions for the terminal to carry out the slice service supported by the auxiliary node.

[0095] Here, the trigger condition may also be referred to as a validation condition. As an example, the trigger condition may be that the RSRP of the secondary node or the cell of the secondary node exceeds a certain threshold. As an example, the trigger condition may be that the terminal is located within the coverage of the secondary node or the cell of the secondary node.

[0096] In step 601, the base station exchanges slice information with the core network so that the core network can be informed of the TA and topology status on the wireless side.

[0097] As an implementation method, in addition to sending the list of slices supported by its cell TA to the core network, base station 1 also sends the identifier of the base station or cell that can potentially serve as its auxiliary node and the list of slices supported by its cell TA. Optionally, it can also send the trigger conditions for the terminal to carry out the slice service supported by the auxiliary node, such as the auxiliary node RSRP exceeding a certain threshold.

[0098] As another implementation method, base station 1 and base station 2 respectively send a list of slices supported by their cell TA to the core network, and base station 1 or base station 2 also sends the topological relationship between base station 1 and base station 2. For example, base station 1 sends to the core network that base station 2 can be used as the auxiliary base station of base station 1, or base station 2 informs the core network that base station 1 can be used as the main base station of base station 2.

[0099] Step 602: The terminal sends a user registration request message to base station 1, carrying the requested NSSAI (requestedNSSAI), such as NSSAI-1 (i.e., the NSSAI of slice 1) and NSSAI-2 (i.e., the NSSAI of slice 2).

[0100] Step 603: Base station 1 selects a core network according to the requested NSSAI.

[0101] Step 604: Base station 1 sends initial information to the selected core network.

[0102] Step 605: The core network determines the slices allowed by the terminal and determines the conditions for allowing the slices to take effect.

[0103] Here, when the core network decides the slices allowed by the terminal, it not only considers the slices supported by the access base station (ie, base station 1), but also considers the topology under the coverage range, such as the slices supported by the base station that can serve as an auxiliary base station and the conditions for the slices to take effect.

[0104] Here, the conditions for the effectiveness of the slice include at least one of the following: the signal quality of the base station or cell corresponding to the slice is greater than or equal to a specific threshold; the terminal is located within the coverage range of the base station or cell corresponding to the slice.

[0105] Step 606: The core network sends initial information feedback to base station 1, carrying the allowed slice list and the validity condition of each slice in the slice list.

[0106] As an example, the allowed slice list includes slice 1 and slice 2, where the effectiveness condition of slice 1 is that it can be carried out in the registration area of ​​slice 1, and the effectiveness condition of slice 2 is that the terminal measures that the RSRP of cell 2 corresponding to slice 2 is higher than a certain threshold.

[0107] Step 607: The core network sends a user registration acceptance message to the terminal, carrying a list of allowed slices and the validity conditions of each slice in the slice list.

[0108] As an example, the allowed slice list includes slice 1 and slice 2, where the effectiveness condition of slice 1 is that it can be carried out in the registration area of ​​slice 1, and the effectiveness condition of slice 2 is that the terminal measures that the RSRP of cell 2 corresponding to slice 2 is higher than a certain threshold.

[0109] Step 608: MO service of slice 2.

[0110] Specifically, 1) when the terminal determines that the conditions for the effectiveness of slice 2 are met, the terminal sends a service request message to the core network, carrying the PDU session request corresponding to slice 2; 2) The core network sends a PDU session resource establishment request message to base station 1, carrying the PDU session resource request corresponding to slice 2; 3) Base station 1 and the base station perform a dual connection establishment process (including the establishment of DRB and other resources for slice 2 in cell 2, including the selection of SCG or SCG diversion bearer); 4) Base station 1 sends a PDU session resource establishment reply message to the core network, carrying information such as the TNL address of the PDU session corresponding to slice 2; 5) Base station 1 sends a reconfiguration message to the terminal, carrying a PDU session request reply message corresponding to slice 2.

[0111] Here, the effectiveness condition of slice 2 is met, for example, the RSRP of the base station or cell corresponding to slice 2 measured by the terminal is higher than the threshold configured by the network, or the terminal moves to the area corresponding to slice 2 pre-configured by the network.

[0112] Step 609: MT service of slice 2.

[0113] Specifically, 1) the core network learns that the effectiveness conditions of slice 2 are met. Here, the core network can be informed by the base station or the terminal can directly inform the core network that the effectiveness conditions of slice 2 are met; 2) the core network sends a PDU session resource establishment request message to base station 1, carrying the PDU session resource request corresponding to slice 2; 3) base station 1 and the base station perform a dual connection establishment process (including the establishment of DRB and other resources for slice 2 in cell 2, including the selection of SCG or SCG diversion bearer); 4) base station 1 sends a PDU session resource establishment reply message to the core network, carrying information such as the TNL address of the PDU session corresponding to slice 2; 5) base station 1 sends a reconfiguration message to the terminal, carrying the PDU session request reply message corresponding to slice 2.

[0114] It should be noted that the above steps 608 and 609 are not limited in execution order, and only step 608 or only step 609 may be executed, or both steps 608 and 609 may be executed simultaneously.

[0115] Figure 7 Schematic diagram of the structure of the slice processing device provided in the embodiment of the present application, which is applied to communication equipment (such as a core network element). Figure 7 As shown, the slice processing device includes:

[0116] An acquisition unit 701 is configured to acquire a first slice list supported by a first base station and a second slice list supported by a second base station; wherein the first base station is a base station accessed by a terminal;

[0117] A determining unit 702 is configured to determine a validation condition of a third slice list and / or at least some slices in the third slice list allowed by the terminal;

[0118] The sending unit 703 is used to send the third slice list and / or the effectiveness conditions of at least some slices in the third slice list to the first base station and / or the terminal.

[0119] In some optional embodiments, the acquisition unit 701 is used to receive a first slice list supported by the first base station and a second slice list supported by the second base station sent by the first base station; or, to receive a first slice list supported by the first base station and a second slice list supported by the second base station sent by the first base station.

[0120] In some optional implementations, the acquisition unit 701 is further used to receive first information sent by the first base station or the second base station, where the first information is used to indicate that the second base station can serve as a secondary base station of the first base station and / or the first base station can serve as a primary base station of the second base station.

[0121] In some optional implementations, the acquisition unit 701 is further used to receive second information sent by the first base station or the second base station, where the second information is used to indicate a validity condition for each slice in the second slice list.

[0122] In some optional embodiments, the determination unit 702 is used to determine the effectiveness conditions of the third slice list allowed by the terminal and / or at least some slices in the third slice list based on at least one of the first slice list, the second slice list, the first information and the second information; wherein the first information is used to indicate that the second base station can be used as an auxiliary base station of the first base station and / or the first base station can be used as the main base station of the second base station, and the second information is used to indicate the effectiveness conditions of each slice in the second slice list.

[0123] In some optional embodiments, the sending unit 703 is used to send at least one of an initial context request message, a connection indication message, an AMF control plane reset message, a user information transfer message, a switching request message, a path switching request confirmation message, an initial UE message, a downlink NAS message, and a routing NAS request message to the first base station, wherein the message carries the validity condition of the third slice list and / or at least some of the slices in the third slice list; and / or, send a user registration acceptance message to the terminal, wherein the user registration acceptance message carries the validity condition of the third slice list and / or at least some of the slices in the third slice list.

[0124] In some optional embodiments, at least some of the slices in the third slice list belong to the second slice list.

[0125] In some optional implementations, the validation condition includes at least one of the following:

[0126] A signal quality of the second base station or a cell of the second base station is greater than or equal to a first threshold;

[0127] The terminal is located in the second base station or in a specific area covered by a cell of the second base station.

[0128] In some optional embodiments, the first slice list supported by the first base station includes a slice list supported by each TA in one or more tracking areas TA supported by the first base station; the second slice list supported by the second base station includes a slice list supported by each TA in one or more TAs supported by the second base station.

[0129] In some optional embodiments, the device further comprises:

[0130] A sending unit, configured to send a PDU session resource establishment request message to the first base station when a validation condition of a target slice in the second slice list is met, wherein the PDU session resource establishment request message carries a PDU session resource request corresponding to the target slice;

[0131] A receiving unit is used to receive a PDU session resource establishment reply message sent by the first base station, and the PDU session resource establishment reply message carries the address information of the PDU session corresponding to the target slice.

[0132] In some optional embodiments, the PDU session resource establishment request message is used to trigger the establishment of a dual connection between the first base station and the second base station for the terminal, wherein the establishment of the dual connection includes: establishing air interface resources of the target slice on the second base station side.

[0133] In some optional implementations, the air interface resources include an SCG bearer and / or an SCG offload bearer on the second base station side.

[0134] In some optional embodiments, a reconfiguration message is sent by the first base station to the terminal, wherein the reconfiguration message carries a PDU session request reply message corresponding to the target slice.

[0135] In some optional implementations, when the terminal triggers the service of the target slice, the terminal determines whether the validation condition of the target slice is met.

[0136] In some optional embodiments, if the terminal determines that the effectiveness condition of the target slice is met, the device also includes: a sending unit and a receiving unit; wherein, before the sending unit sends a PDU session resource establishment request message to the first base station, the receiving unit receives a service request message sent by the terminal, and the service request message carries the PDU session request of the target slice.

[0137] In some optional implementations, when the core network triggers the service of the target slice, the core network determines whether the effectiveness condition of the target slice is met.

[0138] In some optional implementations, the determination unit 702 is further used to determine whether the effectiveness condition of the target slice is met based on the first indication information sent by the first base station or the terminal.

[0139] Those skilled in the art should understand that Figure 7 The functions implemented by each unit in the slice processing device shown can be understood by referring to the relevant description of the aforementioned method. Figure 7 The functions of each unit in the slice processing device shown can be implemented by a program running on a processor, or by a specific logic circuit.

[0140] Figure 8 800 is a schematic structural diagram of a communication device 800 provided in an embodiment of the present application. The communication device may be a terminal or a network device. Figure 8 The communication device 800 shown includes a processor 810, and the processor 810 can call and run a computer program from a memory to implement the method in the embodiment of the present application.

[0141] Alternatively, if Figure 8 As shown, the communication device 800 may further include a memory 820. The processor 810 may call and run a computer program from the memory 820 to implement the method in the embodiment of the present application.

[0142] The memory 820 may be a separate device independent of the processor 810 , or may be integrated into the processor 810 .

[0143] Alternatively, if Figure 8 As shown, the communication device 800 may further include a transceiver 830, and the processor 810 may control the transceiver 830 to communicate with other devices, specifically, may send information or data to other devices, or receive information or data sent by other devices.

[0144] The transceiver 830 may include a transmitter and a receiver. The transceiver 830 may further include an antenna, and the number of the antennas may be one or more.

[0145] Optionally, the communication device 800 may specifically be a network device of an embodiment of the present application, and the communication device 800 may implement the corresponding processes implemented by the network device in each method of the embodiment of the present application, which will not be described in detail here for the sake of brevity.

[0146] Optionally, the communication device 800 may specifically be a mobile terminal / terminal of an embodiment of the present application, and the communication device 800 may implement the corresponding processes implemented by the mobile terminal / terminal in each method of the embodiment of the present application, which will not be described in detail here for the sake of brevity.

[0147] Fig. 9 It is a schematic structural diagram of the chip of an embodiment of the present application. Fig. 9 The chip 900 shown includes a processor 910, which can call and run a computer program from a memory to implement the method in the embodiment of the present application.

[0148] Alternatively, if Fig. 9 As shown, the chip 900 may further include a memory 920. The processor 910 may call and run a computer program from the memory 920 to implement the method in the embodiment of the present application.

[0149] The memory 920 may be a separate device independent of the processor 910 , or may be integrated into the processor 910 .

[0150] Optionally, the chip 900 may further include an input interface 930. The processor 910 may control the input interface 930 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.

[0151] Optionally, the chip 900 may further include an output interface 940. The processor 910 may control the output interface 940 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.

[0152] Optionally, the chip can be applied to the network device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the network device in each method of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0153] Optionally, the chip can be applied to the mobile terminal / terminal in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the mobile terminal / terminal in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0154] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0155] It should be understood that the processor of the embodiment of the present application may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method embodiment can be completed by the hardware integrated logic circuit or software instructions in the processor. The above processor can be a general 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 other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general processor can be a microprocessor or the processor can also be any conventional processor. The steps of the method disclosed in the embodiment of the present application can be directly embodied as a hardware decoding processor to perform, or the hardware and software modules in the decoding processor are combined and performed. The software module can be located in a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, and other mature storage media in the art. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

[0156] It can be understood that the memory in the embodiments of the present application can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory can be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM bus random access memory (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0157] It should be understood that the above-mentioned memory is exemplary but not restrictive. For example, the memory in the embodiments of the present application may also be static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM), etc. That is to say, the memory in the embodiments of the present application is intended to include but not limited to these and any other suitable types of memory.

[0158] An embodiment of the present application also provides a computer-readable storage medium for storing a computer program.

[0159] Optionally, the computer-readable storage medium can be applied to the network device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0160] Optionally, the computer-readable storage medium can be applied to the mobile terminal / terminal in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the mobile terminal / terminal in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0161] An embodiment of the present application also provides a computer program product, including computer program instructions.

[0162] Optionally, the computer program product can be applied to the network device in the embodiments of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0163] Optionally, the computer program product can be applied to the mobile terminal / terminal in the embodiments of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the mobile terminal / terminal in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0164] The embodiment of the present application also provides a computer program.

[0165] Optionally, the computer program can be applied to the network device in the embodiments of the present application. When the computer program runs on a computer, the computer executes the corresponding processes implemented by the network device in the various methods in the embodiments of the present application. For the sake of brevity, they are not described here.

[0166] Optionally, the computer program can be applied to the mobile terminal / terminal in the embodiments of the present application. When the computer program runs on the computer, the computer executes the corresponding processes implemented by the mobile terminal / terminal in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0167] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0168] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0169] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0170] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0171] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0172] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application can be essentially or partly embodied in the form of a software product that contributes to the prior art. The computer software product is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0173] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A slicing method, characterized in that: The method comprises: The core network obtains a first slice list supported by a first base station and a second slice list supported by a second base station; wherein the first base station is a base station accessed by the terminal; The core network determines a third slice list allowed by the terminal and / or a validity condition of at least some slices in the third slice list; The core network sends the third slice list and / or the validity condition of at least some slices in the third slice list to the first base station and / or the terminal; The core network determines a third slice list allowed by the terminal and / or a validity condition of at least some slices in the third slice list, including: The core network determines the effectiveness conditions of the third slice list allowed by the terminal and / or at least some slices in the third slice list based on the first slice list, the second slice list, the first information and at least one of the second information; wherein the first information is used to indicate that the second base station can serve as a secondary base station of the first base station and / or the first base station can serve as a primary base station of the second base station, and the second information is used to indicate the effectiveness conditions of each slice in the second slice list.

2. The method according to claim 1, characterized in that The core network obtains a first slice list supported by the first base station and a second slice list supported by the second base station, including: The core network receives a first slice list supported by the first base station and a second slice list supported by the second base station sent by the first base station; or, The core network receives a first slice list supported by the first base station sent by a first base station, and receives a second slice list supported by the second base station sent by a second base station.

3. The method according to claim 1, characterized in that The method further comprises: The core network receives first information sent by the first base station or the second base station, where the first information is used to indicate that the second base station can serve as a secondary base station of the first base station and / or that the first base station can serve as a primary base station of the second base station.

4. The method according to claim 1, characterized in that: The method further comprises: The core network receives second information sent by the first base station or the second base station, where the second information is used to indicate the effectiveness condition of each slice in the second slice list.

5. The method according to any one of claims 1 to 4, characterized in that The core network sends the third slice list and / or the validity condition of at least some slices in the third slice list to the first base station and / or the terminal, including: The core network sends at least one of an initial context request message, a connection indication message, an AMF control plane reset message, a user information transfer message, a handover request message, a path switch request confirmation message, an initial UE message, a downlink NAS message, and a routing NAS request message to the first base station, where the message carries the validity condition of the third slice list and / or at least some slices in the third slice list; and / or, The core network sends a user registration acceptance message to the terminal, and the user registration acceptance message carries the effectiveness conditions of the third slice list and / or at least some slices in the third slice list.

6. The method according to any one of claims 1 to 4, characterized in that At least some of the slices in the third slice list belong to the second slice list.

7. The method according to any one of claims 1 to 4, characterized in that The validity conditions include at least one of the following: A signal quality of the second base station or a cell of the second base station is greater than or equal to a first threshold; The terminal is located in the second base station or in a specific area covered by a cell of the second base station.

8. The method according to any one of claims 1 to 4, characterized in that The first slice list supported by the first base station includes a slice list supported by each TA in one or more tracking areas TA supported by the first base station; The second slice list supported by the second base station includes a slice list supported by each TA in one or more TAs supported by the second base station.

9. The method according to any one of claims 1 to 4, characterized in that The method further comprises: When the validity condition of the target slice in the second slice list is met, the core network sends a PDU session resource establishment request message to the first base station, where the PDU session resource establishment request message carries a PDU session resource request corresponding to the target slice; The core network receives a PDU session resource establishment reply message sent by the first base station, and the PDU session resource establishment reply message carries the address information of the PDU session corresponding to the target slice.

10. The method according to claim 9, characterized in that The PDU session resource establishment request message is used to trigger the establishment of a dual connection between the first base station and the second base station for the terminal, wherein the establishment of the dual connection includes: establishing air interface resources of the target slice on the second base station side.

11. The method according to claim 10, characterized in that The air interface resources include the SCG bearer and / or the SCG offload bearer on the second base station side.

12. The method according to claim 9, characterized in that The reconfiguration message is sent by the first base station to the terminal, wherein the reconfiguration message carries a PDU session request reply message corresponding to the target slice.

13. The method according to claim 9, characterized in that When the terminal triggers the service of the target slice, the terminal determines whether the validity condition of the target slice is met.

14. The method according to claim 13, characterized in that If the terminal determines that the validity condition of the target slice is satisfied, Before the core network sends a PDU session resource establishment request message to the first base station, the method further includes: The core network receives a service request message sent by the terminal, where the service request message carries a PDU session request for the target slice.

15. The method according to claim 9, characterized in that When the core network triggers the service of the target slice, the core network determines whether the effectiveness condition of the target slice is met.

16. The method according to claim 15, characterized in that The method further comprises: The core network determines whether the effectiveness condition of the target slice is met based on the first indication information sent by the first base station or the terminal.

17. A slice processing device, characterized in that: The device comprises: An acquisition unit, configured to acquire a first slice list supported by a first base station and a second slice list supported by a second base station; wherein the first base station is a base station accessed by a terminal; A determining unit, configured to determine a validation condition of a third slice list and / or at least some slices in the third slice list allowed by the terminal; A sending unit, configured to send the third slice list and / or a validation condition of at least some slices in the third slice list to the first base station and / or the terminal; The determination unit is also used to determine the effectiveness conditions of the third slice list allowed by the terminal and / or at least some slices in the third slice list based on at least one of the first slice list, the second slice list, the first information and the second information; wherein the first information is used to indicate that the second base station can be used as a secondary base station of the first base station and / or the first base station can be used as a main base station of the second base station, and the second information is used to indicate the effectiveness conditions of each slice in the second slice list.

18. A communication device, characterized in that: include: A processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory to execute the method according to any one of claims 1 to 16.

19. A chip, characterized in that: include: A processor, configured to call and run a computer program from a memory, so that a device equipped with the chip executes a method as claimed in any one of claims 1 to 16.

20. A computer-readable storage medium, characterized in that: Used to store a computer program, wherein the computer program causes a computer to execute the method according to any one of claims 1 to 16.