Communication method and device based on network slices

Abstract

The invention provides a communication method and device based on a network slice, which can improve the success rate of accessing the network slice by a terminal and further improve the service performance and the user experience. In the method, a terminal device knows that a first network slice is available in a second cell from a network device, the first network slice does not belong to a network slice allowing the terminal to access in a first cell, a registration area of the terminal comprises a first tracking area and a second tracking area, and the second cell is a cell in the second tracking area. The first cell is a cell in the first tracking area; and the terminal equipment initiates a registration process for the application corresponding to the first network slice in the second cell.

Description

[0001] This application is a divisional application. The application number of the original application is 202110176172.4, and the original application date is February 9, 2021. The entire content of the original application is incorporated into this application by reference. Technical Field

[0002] The present application relates to the field of communications, and in particular to a communication method and device based on network slicing. Background Art

[0003] Network slicing technology provides isolated network environments for different application scenarios by creating virtual independent logical networks on the same network infrastructure. This allows different application scenarios to customize network functions and features according to their needs, effectively ensuring the quality of service (QoS) requirements of different services. Typically, a network slice is identified by a single network slice selection assistance information (S-NSSAI), which is a collection of S-NSSAIs.

[0004] The radio access network (RAN)'s support capability for network slicing is divided into tracking areas (TAs). A TA can support one or more network slices, and cells within the same TA can support the same network slice.

[0005] When network slicing is deployed, network slice selection can be made during the registration process. For example, the core network sends the allowed NSSAI (Allowed NSSAI) to the terminal based on the NSSAI requested by the terminal, the terminal's subscription data, the network slices supported by the TA where the terminal is currently located, etc. The allowed NSSAI is the NSSAI that the terminal can access.

[0006] However, in actual applications, there may be the following scenario: during a registration process, because the TA currently in which the terminal is located does not support a network slice that the terminal wants to access, the terminal will not access the network slice during this registration process. Even if the terminal subsequently moves to a TA that supports the network slice, the terminal may still not be able to access the network slice normally. Summary of the Invention

[0007] The present application provides a communication method and device based on network slicing, which can improve the success rate of terminal access to network slicing, thereby improving service performance and user experience.

[0008] To achieve the above objectives, this application adopts the following technical solutions:

[0009] On the first aspect, a communication method based on network slicing is provided. The method can be executed by a network device or by a component of the network device, such as a processor, chip, or chip system of the network device. This application illustrates the method by taking a network device as an example.

[0010] The method includes: a network device receives, through a first access network device in a first network, information about a network slice that a terminal requests to access, determines the network slice and registration area that the terminal is allowed to access, and sends the registration area information to the terminal. The information about the network slice that the terminal requests to access includes identification information of a first network slice that is not supported by the first tracking area, and identification information of a second network slice; the second tracking area in the first network supports the first network slice, and the network slices that the terminal is allowed to access include the second network slice; the registration area excludes tracking areas that support the first network slice and the second network slice, or excludes tracking areas of access network devices that support the first network slice and the second network slice.

[0011] Based on this solution, when determining the registration area, the network device excludes the tracking area that supports the first network slice and the second network slice, or excludes the tracking area of ​​the access network device that supports the first network slice and the second network slice. Therefore, when the terminal moves within the excluded tracking area, since the registration area of ​​the terminal does not include the tracking area and the tracking area supports the first network slice, the terminal can re-initiate the registration process and request access to the first network slice, thereby improving the success rate of access to the first network slice, and thereby improving service performance and user experience.

[0012] In some possible designs, the method also includes: the network device determines a network slice to which the terminal is denied access, wherein the network slice to which the terminal is denied access includes the first network slice.

[0013] Based on this possible design, when determining the registration area, the network device can exclude the tracking area of ​​the network slice that supports denying terminal access, or exclude the tracking area of ​​the access network device that supports denying terminal access to the network slice.

[0014] In a second aspect, a communication method based on network slicing is provided. The method can be executed by a network device or by a component of the network device, such as a processor, chip, or chip system of the network device. This application takes the network device executing the method as an example for illustration. The method includes: the network device determines a network slice that the terminal is allowed to access and a network slice that the terminal is denied access to, and determines a registration area of ​​the terminal based on the network slice that the terminal is allowed to access and the network slice that the terminal is denied access to, and sends information about the registration area to the terminal.

[0015] Based on this solution, the network device can determine the registration area of ​​the terminal based on the network slice that the terminal is allowed to access and the network slice that the terminal is denied access to, thereby considering excluding the network slice that supports the denied terminal access in the registration area. For example, the registration area excludes the tracking area that supports the network slice that the terminal is denied access to, or the tracking area of ​​the access network device that supports the network slice that the terminal is denied access to. Therefore, when the terminal moves within the excluded tracking area, since the registration area of ​​the terminal does not include the tracking area and the tracking area supports the first network slice, the terminal can re-initiate the registration process and request access to the first network slice, thereby improving the success rate of access to the first network slice, and thereby improving service performance and user experience.

[0016] In some possible designs, the method further includes: the network device receiving, through a first access network device in the first network, information about a network slice that the terminal requests to access. The information about the network slice that the terminal requests to access includes identification information of a first network slice that is not supported by the first tracking area, and identification information of a second network slice that is supported by the first tracking area, the first tracking area being the tracking area of ​​the first access network device; the network slice that the terminal is allowed to access includes the second network slice, and the network slice that the terminal is denied access to includes the first network slice; the registration area excludes tracking areas that support the first network slice and the second network slice, or the registration area excludes tracking areas of access network devices that support the first network slice and the second network slice.

[0017] In combination with the first or second aspect above, in some possible designs, the first network slice is a network slice within the first network that allows the terminal to access.

[0018] In combination with the first or second aspect above, in some possible designs, the method also includes: the network device determines the network slice supported by the tracking area of ​​the first access network device.

[0019] In a third aspect, a communication method based on network slicing is provided. The method can be executed by a network device or by a component of the network device, such as a processor, chip, or chip system of the network device. This application takes the network device executing the method as an example for illustration. The method includes: the network device determines a first network slice, wherein the first network slice does not belong to a network slice that allows terminal access in a first cell, and the registration area of ​​the terminal includes the first cell and the second cell; when the terminal is switched from the first cell to the second cell, the network device determines that the first network slice is available in the second cell, and notifies the terminal that the first network slice is available in the second cell.

[0020] In the prior art, the first network slice does not belong to the network slice that the terminal is allowed to access in the first cell, that is, when the terminal initiates a registration process in the first cell, it cannot access the first network slice. Since the registration area of ​​the terminal includes the first cell and the second cell, when the terminal switches from the first cell to the second cell, the terminal will not be triggered to perform a re-registration process. Even if the first network slice is available in the second cell, the terminal will not initiate a registration process in the second cell, and thus cannot access the first network slice in the second cell. Based on this solution, when the terminal switches from the first cell to the second cell and determines that the first network slice is available in the second cell, the network device notifies the terminal that the first network slice is available in the second cell. Therefore, if the terminal still wants to access the first network slice, it can initiate a registration process to request access to the first network slice, thereby improving the success rate of accessing the first network slice, and thereby improving service performance and user experience.

[0021] In some possible designs, when the second cell belongs to the second access network device, the target access network device is the second access network device; when the second cell belongs to the first access network device, the target access network device is the first access network device. Among them, the first cell belongs to the first access network device, so it can be understood that the second cell belongs to the second access network device (that is, the first cell and the second cell belong to different access network devices) corresponds to the inter-station switching scenario; the second cell belongs to the first access network device (that is, the first cell and the second cell belong to the same access network device) corresponds to the intra-station switching scenario. This also applies to the design of other aspects of this application, which will not be repeated later. Based on this possible design, the success rate of accessing the first network slice can be improved in the scenarios of intra-station switching or inter-station switching.

[0022] In some possible designs, when the network device is a mobility management device, the network device determines that the first network slice is available in the second cell, including: the network device queries the context of the target access network device, the context of the target access network device indicating that the tracking area of ​​the target access network device supports the first network slice, wherein the second cell is a cell in the tracking area of ​​the target access network device. Based on this possible design, the network device can determine that the first network slice is available in the second cell through the locally stored context of the target access network device, without interacting with other devices, thereby reducing signaling overhead.

[0023] In some possible designs, when the network device is a mobile management device, the network device determines that the first network slice is available in the second cell, including: the network device sends identification information of the first network slice to the target access network device, and learns from the target access network device that the terminal can access the first network slice in the second cell.

[0024] In some possible designs, the network device is a mobility management device, and when the second cell belongs to a second access network device, the network device determines that the first network slice is available in the second cell, including: when the network device receives a path switching request message from the second access network device, determining that the first network slice is available in the second cell; or when the network device receives a switching requirement message from the first access network device, determining that the first network slice is available in the second cell, the switching requirement message including an identifier of the second access network device.

[0025] Based on this possible design, the network device can confirm with the target network device whether the terminal can access the first network slice supported by the tracking area of ​​the target access network device, thereby avoiding the situation where the network device supports the first network slice but the terminal cannot access the first network slice in the second cell. In this case, the terminal is notified that the first network slice is available in the second cell, which can improve the success rate of the terminal accessing the first network slice in the second cell.

[0026] In some possible designs, when the network device is a mobile management device, the method also includes: the network device saves identification information of the first network slice; after the network device notifies the terminal that the first network slice is available in the second cell, the network device receives indication information from the terminal; and the network device deletes the identification information of the first network slice according to the indication information.

[0027] In some possible designs, when the network device is a mobile management device, the indication information is used to instruct the terminal to no longer request access to the first network slice.

[0028] Based on the above two possible designs, the indication information is used to indicate that when the terminal no longer requests access to the first network slice, the network device deletes the identification information of the first network slice. When the network device subsequently serves the terminal, it may no longer notify the terminal of the cell that can access the first network slice, thereby reducing signaling overhead and reducing resource waste.

[0029] In some possible designs, when the second cell belongs to the second access network device, the network device is the second access network device; or, when the second cell belongs to the first access network device, the network device is the first access network device. Based on this possible design, the success rate of accessing the first network slice can be improved in both intra-site handover and inter-site handover scenarios.

[0030] In some possible designs, when the second cell belongs to the first access network device, the network device determines the first network slice, including: the network device sends information about the network slice that the terminal requests to access to the mobility management device, the information about the network slice that the terminal requests to access includes identification information of the first network slice; and the network device learns from the mobility management device that the first network slice is not a network slice that the terminal is allowed to access in the first cell. In other words, the network device can learn from the mobility management device during the registration process that the first network slice is not a network slice that the terminal is allowed to access in the first cell. This also applies to the designs of other aspects of the present application and will not be described in detail below.

[0031] In some possible designs, when the second cell belongs to the second access network device, the network device determines the first network slice, including: when the terminal is handed over from the first access network device to the second access network device, the network device learns from the mobility management device that the first network slice does not belong to the network slices allowed to be accessed by the terminal in the first cell. That is, in an inter-site handover scenario, the network device can learn from the mobility management device that the first network slice does not belong to the network slices allowed to be accessed by the terminal in the first cell. This also applies to the designs of other aspects of the present application and will not be described in detail below.

[0032] In some possible designs, the network device determines that the first network slice is available in the second cell, including: the network device determines that the terminal can access the first network slice in the second cell.

[0033] In a fourth aspect, a communication method based on network slicing is provided. The method can be executed by a network device or by a component of the network device, such as a processor, chip, or chip system of the network device. This application takes the network device executing the method as an example for illustration. The method includes: the network device determines a first network slice, wherein the first network slice does not belong to a network slice that allows terminal access in a first cell, and the registration area of ​​the terminal includes the first cell and the second cell; when the terminal is switched from the first cell to the second cell, the network device determines that the first network slice is available in a third cell, and notifies the terminal that the first network slice is available in the third cell, and the physical coverage of the third cell partially or completely overlaps with the physical coverage of the second cell.

[0034] In the prior art, the first network slice does not belong to the network slice that the terminal is allowed to access in the first cell, that is, when the terminal initiates the registration process in the first cell, it cannot access the first network slice. Since the registration area of ​​the terminal includes the first cell and the second cell, when the terminal switches from the first cell to the second cell, the terminal will not be triggered to perform the re-registration process. Even if the first network slice is available in the third cell that has the same physical coverage as the second cell, the terminal will not re-initiate the registration process in the second cell, and thus cannot access the first network slice at the location of the second cell. Based on this solution, when the terminal switches from the first cell to the second cell and determines that the first network slice is available in the third cell, the terminal is notified that the first network slice is available in the third cell. Therefore, if the terminal still wants to access the first network slice, it can access the first network slice in the third cell, thereby improving the success rate of accessing the first network slice, thereby improving service performance and user experience.

[0035] In some possible designs, when the second cell belongs to the second access network device, the target access network device is the second access network device; when the second cell belongs to the first access network device, the target access network device is the first access network device. Based on this possible design, the success rate of accessing the first network slice can be improved in both intra-site handover and inter-site handover scenarios.

[0036] In some possible designs, when the network device is a mobility management device, the network device determines that the first network slice is available in the third cell, including: the network device queries the context of the target access network device, the context of the target access network device indicates that the tracking area where the third cell is located supports the first network slice, and the tracking area where the second cell is located does not support the first network slice, and the second cell and the third cell are cells of the target access network device. Based on this possible design, the network device can determine that the first network slice is available in the third cell through the locally stored context of the target access network device, without interacting with other devices, thereby reducing signaling overhead.

[0037] In some possible designs, when the network device is a mobile management device, the network device determines that the first network slice is available in the third cell, including: the network device sends identification information of the first network slice to the target access network device, and learns from the target access network device that the terminal can access the first network slice in the third cell.

[0038] Based on this possible design, the network device can confirm with the target network device whether the terminal can access the first network slice supported by the tracking area of ​​the target access network device, so as to avoid the situation where the target access network device supports the first network slice, but the terminal cannot access the first network slice in the third cell. The network device notifies the terminal that the first network slice is available in the third cell, which can improve the success rate of the terminal accessing the first network slice in the third cell.

[0039] In combination with the third aspect or the fourth aspect above, in some possible designs, when the network device is a mobile management device, the network device determines the first network slice, including: the network device receives information about the network slice that the terminal requests to access through the first cell, and the information about the network slice that the terminal requests to access includes identification information of the first network slice; the network device determines the network slice that the terminal is allowed to access, and learns that the first network slice does not belong to the network slice that the terminal is allowed to access in the first cell.

[0040] In combination with the third aspect or the fourth aspect above, in some possible designs, the first network slice is included in the network slice configured by the terminal in the first network. That is, the network device can perform the above method for the first network slice that is included in the network slice configured by the terminal in the first network, although the first cell does not belong to the network slice that the terminal is allowed to access. That is to say, regardless of whether the network slice requested to be accessed by the terminal carries the identifier of the first network slice, since the first network slice is included in the network slice configured by the terminal in the first network, the terminal may subsequently want to access the first network slice. Then, when the terminal wants to access the first network slice, it can access the first network slice in the second cell or the third cell, thereby improving the success rate of accessing the first network slice. This also applies to the designs of other aspects of the present application and will not be described in detail later.

[0041] In combination with the third aspect or the fourth aspect above, in some possible designs, the first network slice is included in the network slice that the terminal requests to access in the first cell.

[0042] In combination with the third aspect or the fourth aspect above, in some possible designs, the first cell belongs to the first access network device, and the second cell belongs to the second access network device; or, the first cell and the second cell belong to the first access network device.

[0043] In a fifth aspect, a communication method based on network slicing is provided. The method can be executed by a network device or by a component of the network device, such as a processor, chip, or chip system of the network device. This application takes the network device executing the method as an example for illustration. The method includes: the network device determines a first network slice, wherein the first network slice does not belong to a network slice that allows terminal access in a first cell, and the registration area of ​​the terminal includes the first cell and the second cell; the network device determines that the first network slice is available in the second cell, notifies the terminal that the first network slice is available in the second cell, and sends a cell identifier of the second cell to the terminal.

[0044] In the prior art, the first network slice does not belong to the network slice that the terminal is allowed to access in the first cell, that is, when the terminal initiates the registration process in the first cell, it cannot access the first network slice. Since the registration area of ​​the terminal includes the first cell and the second cell, when the terminal switches from the first cell to the second cell, the terminal will not be triggered to perform a re-registration process. Even if the first network slice is available in the second cell, the terminal will not initiate a registration process in the second cell, and thus cannot access the first network slice in the second cell. Based on this solution, when the network device determines that the first network slice is available in the second cell, it notifies the terminal that the first network slice is available in the second cell and sends the cell identifier of the second cell. Therefore, if the terminal still wants to access the first network slice, it can access the second cell and initiate a registration process to request access to the first network slice, thereby improving the success rate of accessing the first network slice, thereby improving service performance and user experience.

[0045] In some possible designs, the network device determines that the first network slice is available in the second cell, including: the network device receives the cell identifier of the second cell from the first access network device, wherein the second cell is a neighboring cell of the first cell, and the terminal can access the first network slice in the second cell.

[0046] In some possible designs, the network device determines that the first network slice is available in the second cell, including: the network device receives signal quality information of the neighboring cells of the first cell from the first access network device, and the neighboring cells of the first cell include the second cell; the network device determines that the terminal can access the first network slice in the second cell based on the signal quality information of the second cell.

[0047] In some possible designs, the method also includes: the network device saves identification information of the first network slice; after the network device notifies the terminal that the first network slice is available in the second cell, the network device receives indication information from the terminal and deletes the identification information of the first network slice based on the indication information.

[0048] In some possible designs, the indication information is used to indicate that the terminal no longer requests access to the first network slice.

[0049] Based on the above two possible designs, the indication information is used to indicate that when the terminal no longer requests access to the first network slice, the network device deletes the identification information of the first network slice. When the network device subsequently serves the terminal, it may no longer notify the terminal of the cell that can access the first network slice, thereby reducing signaling overhead and reducing resource waste.

[0050] In a sixth aspect, a communication method based on network slicing is provided. The method can be executed by a network device or by a component of the network device, such as a processor, chip, or chip system of the network device. This application takes the execution of the method by a network device as an example for illustration. The method includes: the network device determines a first network slice, wherein the first network slice does not belong to a network slice that allows terminal access in a first cell, and the registration area of ​​the terminal includes the first cell and the second cell; the network device determines that the first network slice is available in a third cell, notifies the terminal that the first network slice is available in the third cell, and sends a cell identifier of the third cell to the terminal, wherein the physical coverage of the third cell partially or completely overlaps with the physical coverage of the second cell.

[0051] In the prior art, the first network slice does not belong to the network slices that the terminal is allowed to access in the first cell, that is, when the terminal initiates the registration process in the first cell, it cannot access the first network slice. Since the registration area of ​​the terminal includes the first cell and the second cell, when the terminal switches from the first cell to the second cell, the terminal will not be triggered to perform a re-registration process. Even if the first network slice is available in a third cell that is physically co-located with the second cell, the terminal will not re-initiate the registration process in the second cell, and thus cannot access the first network slice at the location of the second cell. Based on this solution, when the neighboring area of ​​the first cell accessed by the terminal includes the second cell and there is a third cell that is physically co-located with the second cell, when the network device determines that the first network slice is available in the third cell, it notifies the terminal that the first network slice is available in the third cell and sends the cell identifier of the third cell. Therefore, if the terminal still wants to access the first network slice, it can access the third cell and request access to the first network slice, thereby improving the success rate of accessing the first network slice, thereby improving service performance and user experience.

[0052] In combination with the above-mentioned fifth aspect or sixth aspect, in some possible designs, the first network slice is included in the network slice of the configuration of the terminal in the first network.

[0053] In combination with the above-mentioned fifth aspect or sixth aspect, in some possible designs, the first network slice is included in the network slice that the terminal requests to access in the first cell.

[0054] In combination with the above-mentioned fifth aspect or sixth aspect, in some possible designs, the network device determines the first network slice, including: the network device receives information about the network slice that the terminal requests to access through the first cell, and the information about the network slice that the terminal requests to access includes identification information of the first network slice; the network device determines the network slice that the terminal is allowed to access, and learns that the first network slice does not belong to the network slice that the terminal is allowed to access in the first cell.

[0055] In combination with the above-mentioned fifth aspect or sixth aspect, in some possible designs, the method also includes: the network device sends reference frequency information corresponding to the first network slice to the first access network device.

[0056] In a seventh aspect, a communication method based on network slicing is provided. The method can be executed by a terminal or by a component of the terminal, such as a processor, chip, or chip system of the terminal. This application takes the terminal executing the method as an example. The method includes: the terminal learns from a network device that a first network slice is available in a second cell, and initiates a registration process for an application corresponding to the first network slice. The first network slice does not belong to the network slice that the terminal is allowed to access in the first cell, and the registration area of ​​the terminal includes the first cell and the second cell.

[0057] In the prior art, since the first network slice does not belong to the network slices that the terminal is allowed to access in the first cell, the terminal cannot access the first network slice in the first cell. Since the registration area of ​​the terminal includes the first cell and the second cell, even if the terminal moves from the first cell to the coverage area of ​​the second cell, the terminal will not re-initiate the registration process and thus will not request access to the first network slice. Based on this solution, the terminal can learn from the network device that the first network slice is available in the second cell. Therefore, if the terminal's application corresponds to the first network slice, a registration process can be initiated for the application to request access to the first network slice, thereby improving the success rate of access to the first network slice, thereby improving service performance and user experience.

[0058] In some possible designs, the first network slice is included in a network slice of the terminal's configuration in the first network.

[0059] In some possible designs, the first network slice is included in the network slice that the terminal requests to access in the first cell.

[0060] In some possible designs, the method also includes: the terminal receiving a cell identifier from a network device, where the cell identifier is used for the second cell.

[0061] In some possible designs, the terminal initiates a registration process for the application corresponding to the first network slice, including: the terminal accesses the second cell and initiates a registration process for the application through the second cell.

[0062] In some possible designs, the terminal initiates a registration process for an application corresponding to the first network slice, including: in response to the terminal's context not including a session for the application and not including a routing selection policy for the application, the terminal determines whether the first network slice is the network slice corresponding to the application; in the case that the first network slice is the network slice corresponding to the application, the terminal initiates a registration process for the application.

[0063] In some possible designs, the method further includes: the terminal notifying the network device that the terminal no longer requests access to the first network slice. Based on this possible design, when the terminal notifies the network device that the terminal no longer requests access to the first network slice, the network device may delete the stored identification information of the first network slice. When the network device subsequently serves the terminal, it may no longer notify the terminal of cells that can access the first network slice, thereby reducing signaling overhead and reducing resource waste.

[0064] In some possible designs, the terminal notifies the network device that the terminal no longer requests access to the first network slice, including: after a first period of time starting from a first moment, the terminal notifies the network device that the terminal no longer requests access to the first network slice, and the first moment is the moment when the terminal learns from the network device that the first network slice is available in the second cell.

[0065] In an eighth aspect, a communication device is provided for implementing the various methods described above. The communication device may be the network device described in the first to sixth aspects, or a device including the network device described above, or a device included in the network device described above, such as a chip; or the communication device may be the terminal described in the seventh aspect, or a device including the terminal described above, or a device included in the terminal described above, such as a chip. The communication device includes modules, units, or means corresponding to the implementation of the above methods, and the modules, units, or means may be implemented by hardware, software, or by executing corresponding software implementations through hardware. The hardware or software includes one or more modules or units corresponding to the above functions.

[0066] In some possible designs, the communication device may include a processing module and a transceiver module. The transceiver module, also referred to as a transceiver unit, is configured to implement the transmitting and / or receiving functions described in any of the above aspects and any possible implementations thereof. The transceiver module may be comprised of a transceiver circuit, a transceiver, a transceiver, or a communication interface. The processing module may be configured to implement the processing functions described in any of the above aspects and any possible implementations thereof.

[0067] In some possible designs, the transceiver module includes a sending module and a receiving module, which are respectively used to implement the sending and receiving functions in any of the above aspects and any possible implementation methods.

[0068] Among them, the communication device provided in the eighth aspect is used to execute any one of the above aspects or any possible implementation of any one of the aspects. The specific details can be found in any one of the above aspects or any possible implementation of any one of the aspects, and will not be repeated here.

[0069] In the ninth aspect, a communication device is provided, comprising: a processor and a memory; the memory is used to store computer instructions, and when the processor executes the instructions, the communication device executes the method described in any of the above aspects. The communication device can be the network device in the above-mentioned first to sixth aspects, or a device including the above-mentioned network device, or a device included in the above-mentioned network device, such as a chip; or, the communication device can be the terminal in the above-mentioned seventh aspect, or a device including the above-mentioned terminal, or a device included in the above-mentioned terminal, such as a chip.

[0070] In a tenth aspect, a communication device is provided, comprising: a processor and a communication interface; the communication interface is configured to communicate with a module external to the communication device; and the processor is configured to execute a computer program or instruction to cause the communication device to perform the method described in any of the above aspects. The communication device may be the network device described in the first to sixth aspects, or a device including the network device, or a device included in the network device, such as a chip; or the communication device may be the terminal described in the seventh aspect, or a device including the terminal, or a device included in the terminal, such as a chip.

[0071] In an eleventh aspect, a communication device is provided, comprising: an interface circuit and a logic circuit, the interface circuit being configured to obtain input information and / or output output information; the logic circuit being configured to execute the method described in any of the above aspects or any possible implementation of any of the above aspects, processing the input information and / or generating output information. The communication device may be the network device described in any of the above aspects, or a device including the above network device, or a device included in the above network device, such as a chip; or the communication device may be the terminal described in the above aspect, or a device including the above terminal, or a device included in the above terminal, such as a chip.

[0072] When the communication device is the network device in the first or second aspect, or a device including the network device, or a device included in the network device:

[0073] In some possible designs, the input information may be: information about a network slice that the terminal requests to access, the information about the network slice that the terminal requests to access including identification information of a first network slice that is not supported by the first tracking area, and identification information of a second network slice. Processing based on the input information may include: determining a network slice that the terminal is allowed to access, or determining a registration area.

[0074] In some possible designs, the output information may be: information of a registration area, which excludes the tracking area supporting the first network slice and the second network slice, or the registration area excludes the tracking area of ​​the access network device supporting the first network slice and the second network slice.

[0075] When the communication device is the network device in the third aspect, or a device including the network device, or a device included in the network device:

[0076] In some possible designs, the output information may be: information used to notify the terminal that the first network slice is available in the second cell.

[0077] In some possible designs, the input information may be: information about a network slice that the terminal requests to access, where the information about the network slice that the terminal requests to access includes identification information of a first network slice. Processing based on the input information may include: determining that the terminal is allowed to access a network slice, or determining that the first network slice does not belong to a network slice that the terminal is allowed to access in the first cell.

[0078] In some possible designs, the output information may be: identification information of the first network slice.

[0079] In some possible designs, the input information may be information used by the network device to learn that the terminal can access the first network slice in the second cell. Processing according to the input information may be learning that the terminal can access the first network slice in the second cell.

[0080] In some possible designs, the input information may be: a path switching request message. Processing according to the input information may be: determining that the first network slice is available in the second cell.

[0081] In some possible designs, the input information may be a handover request message. Processing according to the input information may be determining that the first network slice is available in the second cell.

[0082] In some possible designs, the input information may be: indication information. Processing according to the input information may be: deleting identification information of the first network slice according to the indication information.

[0083] When the communication device is the network device in the fifth aspect, or a device including the network device, or a device included in the network device:

[0084] In some possible designs, the output information may be: information used to notify the terminal that the first network slice is available in the second cell, and the cell identifier of the second cell.

[0085] In some possible designs, the input information may be: information about a network slice that the terminal requests to access, where the information about the terminal's access request includes identification information of a first network slice. Processing based on the input information may include: determining a network slice that the terminal is allowed to access, and learning that the first network slice does not belong to a network slice that the terminal is allowed to access in the first cell.

[0086] In some possible designs, the input information may be: a cell identifier of the second cell. Processing based on the input information may be: determining that the first network slice is available in the second cell.

[0087] In some possible designs, the input information may include signal quality information of a neighboring cell of the first cell, where the neighboring cell of the first cell includes the second cell. Processing based on the input information may include determining, based on the signal quality information of the second cell, that the terminal can access the first network slice in the second cell.

[0088] In some possible designs, the output information may be: reference frequency information corresponding to the first network slice.

[0089] In some possible designs, the input information may be: indication information. Processing according to the input information may be: deleting identification information of the first network slice according to the indication information.

[0090] The communication device may be the terminal in the seventh aspect, or a device including the terminal, or a device included in the terminal:

[0091] In some possible designs, the input information may be information for obtaining information that the first network slice is available in the second cell. Processing based on the input information may be initiating a registration process for an application corresponding to the first network slice.

[0092] In some possible designs, the input information may be: a cell identifier, where the cell identifier is used for the second cell. Processing according to the input information may be: accessing the second cell.

[0093] In some possible designs, the output information may be: information used to notify the terminal that it no longer requests access to the first network slice.

[0094] In a twelfth aspect, a communication device is provided, comprising: at least one processor; the processor is configured to execute a computer program or instruction stored in a memory, so that the communication device performs the method described in any of the above aspects. The memory may be coupled to the processor, or may be independent of the processor. The communication device may be the network device described in aspects 1 to 6 above, or a device including the network device, or a device included in the network device, such as a chip; or the communication device may be the terminal described in aspect 7 above, or a device including the terminal, or a device included in the terminal, such as a chip.

[0095] In a thirteenth aspect, a computer-readable storage medium is provided, wherein instructions are stored in the computer-readable storage medium. When the computer-readable storage medium is run on a communication device, the communication device can execute the method described in any one of the above aspects.

[0096] In a fourteenth aspect, a computer program product comprising instructions is provided, which, when executed on a communication device, enables the communication device to execute the method described in any one of the above aspects.

[0097] In a fifteenth aspect, a communication device is provided (for example, the communication device may be a chip or a chip system), which includes a processor for implementing the functions involved in any of the above aspects.

[0098] In some possible designs, the communication device includes a memory for storing necessary program instructions and data.

[0099] In some possible designs, when the device is a chip system, it can be composed of a chip or include a chip and other discrete devices.

[0100] It can be understood that when the communication device provided in any one of the eighth to fifteenth aspects is a chip, the above-mentioned sending action / function can be understood as output information, and the above-mentioned receiving action / function can be understood as input information.

[0101] Among them, the technical effects brought about by any design method in the eighth to fifteenth aspects can refer to the technical effects brought about by the different design methods in the above-mentioned first to seventh aspects, and will not be repeated here.

[0102] In the sixteenth aspect, a communication system is provided, which includes the network device and terminal described in the above aspects. BRIEF DESCRIPTION OF THE DRAWINGS

[0103] Figure 1 A schematic diagram of a 5G network architecture provided for this application;

[0104] Figure 2A schematic diagram of an application scenario of network slicing provided in this application;

[0105] Figure 3 A schematic diagram of network slicing supported by an access network device provided in this application;

[0106] Figure 4 A schematic diagram of the registration process provided for this application;

[0107] Figure 5 A schematic diagram of a redirection process provided for this application;

[0108] Figure 6 A schematic diagram of an Xn switching process provided by this application;

[0109] Figure 7 A schematic diagram of an N2 switching process provided by this application;

[0110] Figure 8a A schematic diagram of a scenario provided for this application;

[0111] Figure 8b A schematic diagram of a scenario provided for this application;

[0112] Figure 8c A schematic diagram of a scenario provided for this application;

[0113] Figure 9a A schematic diagram of the structure of a communication system provided in this application;

[0114] Figure 9b A schematic diagram of the structure of another communication system provided by this application;

[0115] Figure 9c A schematic diagram of the structure of another communication system provided by this application;

[0116] Figure 10 A schematic diagram of the structure of a communication device provided in this application;

[0117] Figure 11 A flowchart of a communication method based on network slicing provided in this application;

[0118] Figure 12 A flowchart of a communication method based on network slicing provided in this application;

[0119] Figure 13 A flowchart of a communication method based on network slicing provided in this application;

[0120] Figure 14 A flowchart of a communication method based on network slicing provided in this application;

[0121] Figure 15 A flowchart of a communication method based on network slicing provided in this application;

[0122] Figure 16 A flowchart of a communication method based on network slicing provided in this application;

[0123] Figure 17 A flowchart of a communication method based on network slicing provided in this application;

[0124] Figure 18 A flowchart of a communication method based on network slicing provided in this application;

[0125] Figure 19 A schematic diagram of the interaction flow of a communication method based on network slicing provided in this application;

[0126] Figure 20 A schematic diagram of the interaction flow of a communication method based on network slicing provided in this application;

[0127] Figure 21 A schematic diagram of the interaction flow of a communication method based on network slicing provided in this application;

[0128] Figure 22 A schematic diagram of the interaction flow of a communication method based on network slicing provided in this application;

[0129] Figure 23 A schematic diagram of the interaction flow of a communication method based on network slicing provided in this application;

[0130] Figure 24 A schematic diagram of the interaction flow of a communication method based on network slicing provided in this application;

[0131] Figure 25 A schematic diagram of the interaction flow of a communication method based on network slicing provided in this application;

[0132] Figure 26 A schematic diagram of the interaction flow of a communication method based on network slicing provided in this application;

[0133] Figure 27 A schematic diagram of the interaction flow of a communication method based on network slicing provided in this application;

[0134] Figure 28 A schematic diagram of the interaction flow of a communication method based on network slicing provided in this application;

[0135] Figure 29 A schematic diagram of the interaction flow of a communication method based on network slicing provided in this application;

[0136] Figure 30 A schematic diagram of the interaction flow of a communication method based on network slicing provided in this application;

[0137] Figure 31 A schematic diagram of the structure of a network device provided in this application;

[0138] Figure 32 A schematic diagram of the structure of a terminal provided in this application;

[0139] Figure 33 A schematic structural diagram of a communication device provided in this application. DETAILED DESCRIPTION

[0140] In the description of this application, unless otherwise specified, " / " indicates that the objects associated before and after are in an "or" relationship, for example, A / B can represent A or B; "and / or" in this application is only a description of the association relationship of 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, where A and B can be singular or plural. In addition, in the description of this application, unless otherwise specified, "multiple" refers to two or more than two. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can represent: a, b, c, a and b, a and c, b and c, a and b and c, where a, b, c can be single or multiple. In addition, to facilitate the clear description of the technical solutions of the embodiments of the present application, in the embodiments of the present application, the words "first" and "second" are used to distinguish between identical or similar items with substantially the same functions and effects. Those skilled in the art will understand that the words "first" and "second" do not limit the quantity or execution order, and the words "first" and "second" do not necessarily mean different.

[0141] It should be noted that, in this application, words such as "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described in this application as "exemplary" or "for example" should not be construed as being preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner.

[0142] In order to facilitate understanding of the technical solutions of the embodiments of the present application, a brief introduction to the relevant technologies of the present application is given below.

[0143] 1. Fifth generation (5G) network architecture:

[0144] The 5G network architecture defined in the 3rd Generation Partnership Project (3GPP) TS23.501 standard is mainly divided into two parts: access network (AN) and core network.

[0145] The access network may include a radio access network (RAN), which is used to implement functions related to wireless access.

[0146] The core network mainly includes the following key logical network elements: access and mobility management function (AMF) network element, session management function (SMF) network element, user plane function (UPF) network element, policy control function (policy control function) network element, unified data management function (UDM) network element. In addition, it can also include authentication server function (AUSF) network element, network slice selection function (NSSF) network element, application function (AF) network element, etc.

[0147] See also Figure 1 , which is a schematic diagram of a 5G network architecture. The terminal may be a user equipment (UE), such as a mobile phone, an IoT terminal, etc.

[0148] DN stands for data network (DN), which is mainly used to provide data transmission services to users, such as Internet Protocol (IP) Multimedia Service (IMS).

[0149] Access network equipment that provides wireless access to users is deployed in the RAN, including but not limited to evolved base stations (NodeB or eNB or e-NodeB, evolutionaryNode B), wireless fidelity (WiFi) access points (AP), etc.

[0150] The AMF network element is mainly responsible for mobility management in the mobile network, such as user location update, user network registration, user switching, etc.

[0151] The SMF network element is responsible for session management in mobile networks, such as session establishment, modification, and release. Specific functions include allocating IP addresses to users and selecting the UPF that provides packet forwarding capabilities.

[0152] The PCF network element is mainly responsible for providing policies to AMF and SMF, such as quality of service (QoS) policy and slice selection policy.

[0153] The UDM network element is mainly responsible for storing user data, such as contract information and authentication / authorization information.

[0154] The AF network element is mainly responsible for providing service requirements to the 3GPP network, such as influencing service routing and interacting with the PCF network element for policy control.

[0155] The UPF network element is mainly responsible for processing user messages, such as forwarding and billing.

[0156] The terminal accesses the DN by establishing a protocol data unit (PDU) session (PDU session) between the terminal, the RAN, the UPF, and the DN.

[0157] The AUSF network element is mainly responsible for providing terminal authentication services for the AMF network element.

[0158] The NSSF network element is mainly responsible for selecting network slices to serve the terminal.

[0159] In addition, see Figure 1 Nx represents the logical interface or service-oriented interface between two network elements, which is used for communication between network elements. For example, N1 is the interface between the terminal and the AMF network element; N2 is the interface between the access network device and the AMF network element; N3 is the interface between the access network device and the UPF network element; N9 is the interface between different UPF network elements; N6 is the interface between the UPF network element and the DN; N4 is the interface between the UPF network element and the SMF network element; N11 is the interface between the AMF network element and the SMF network element; N7 is the interface between the SMF network element and the PCF network element; N5 is the interface between the PCF network element and the AF network element; N14 is the interface between different AMF network elements; N15 is the interface between the AMF network element and the PCF network element; N22 is the interface between the NSSF network element and the AMF network element; N12 is the interface between the AUSF network element and the AMF network element; N8 is the interface between the UDM network element and the AMF network element; and N13 is the interface between the AUSF network element and the UDM network element.

[0160] 2. Network Slice (or Slice for short):

[0161] In the 5G era, hundreds of billions of IoT devices will be connected to the network. Different application scenarios will have different, and sometimes even conflicting, network requirements. Providing services for these diverse application scenarios through a single network will lead to an extremely complex network architecture and inefficient network management and resource utilization.

[0162] 5G network slicing technology provides isolated network environments for different application scenarios by creating virtual independent logical networks on the same network infrastructure. This allows different application scenarios to customize network functions and features according to their respective needs, and can effectively guarantee the QoS requirements of different services.

[0163] The goal of network slicing is to organically combine terminals, access network resources, core network resources, and network operation and maintenance and management systems to provide independent and isolated complete networks for different business scenarios or business types.

[0164] A wide variety of scenarios present distinct requirements for the 3GPP ecosystem, including billing, policy, security, and mobility. 3GPP emphasizes that network slices should not interfere with each other. For example, a sudden surge in meter reading traffic should not impact normal mobile broadband services. To meet diverse needs and isolate services between slices, relatively independent management and operations are required for each service, along with tailored service functionality and analytical capabilities. Instances of different service types can be deployed on different network slices, and different instances of the same service type can also be deployed on different network slices.

[0165] For example, Figure 2 As shown in the figure, enhanced mobile broadband (MBB) slices are used to provide mobile broadband services for handheld terminals, etc.; massive machine type communications (mMTC) slices are used to provide services for a large number of meter reading services; and critical MTC slices are used to provide services for vehicles to everything (V2X) services.

[0166] Specifically:

[0167] Network slicing: refers to a logical network that can provide specific network capabilities and network characteristics.

[0168] Network Slice instance: refers to a set of network function entities and required resources that constitute a network slice, such as computing, storage, and network resources.

[0169] Single network slice selection assistance information (S-NSSAI) can be used as identification information of the network slice to distinguish different network slices.

[0170] Among them, S-NSSAI may include slice type / service type (SST) information, which is used to describe the expected network slicing behavior, such as the slice type / service type used to describe the network slice, etc., without restriction.

[0171] Exemplarily, the slice type / service type (SST) of the network slice may include: enhanced mobile broadband (eMBB), ultra-reliable low latency communications (URLLC), massive Internet of things (MIoT), vehicle to everything (V2X), etc., without limitation.

[0172] Optionally, S-NSSAI also includes slice differentiator (or slice differentiation identifier) ​​(slicedifferentiator, SD) information. The SD information is complementary information to the SST information and is used to distinguish different network slices with the same SST characteristics. That is, when the SST information points to multiple network slices, the SD information can assist in corresponding to a unique network slice.

[0173] In addition, a group of S-NSSAIs can be identified by network slice selection assistance information (NSSAI), that is, NSSAI is a collection of a group of S-NSSAIs.

[0174] Among them, if classified according to different types, NSSAI includes Subscribed NSSAI, Configured NSSAI, Requested NSSAI, Allowed NSSAI, Rejected NSSAI, or Pending NSSAI.

[0175] Exemplary:

[0176] Subscribed NSSAI: The subscribed NSSAI is unique to the home public land mobile network (HPLMN) and refers to the subscribed NSSAI that the terminal is allowed to access.

[0177] Configured NSSAI: The NSSAI of one or more PLMNs defined in the terminal. The Configured NSSAI is determined by the serving PLMN based on its own support capabilities for network slicing and the network slices subscribed to by the terminal. It is then sent to the terminal in the Registration Accept message during the registration process. Configured NSSAI is based on the granularity of PLMN or Stand-alone Non-Public Network (SNPN). Different PLMNs or SNPNs can correspond to different Configured NSSAIs.

[0178] Requested NSSAI: refers to the NSSAI provided by the terminal to the serving PLMN during the registration process. If the terminal has saved the Configured NSSAI corresponding to the serving PLMN, the Requested NSSAI includes the S-NSSAI in the Configured NSSAI corresponding to the serving PLMN. If the terminal does not save the Configured NSSAI corresponding to the serving PLMN, for example, when the terminal first accesses or deletes the Configured NSSAI corresponding to the serving PLMN due to reasons such as restart, the Requested NSSAI may include the S-NSSAI in the Default Configured NSSAI. The Default Configured NSSAI is configured by the HPLMN. In this scenario, the Requested NSSAI may include an S-NSSAI that does not belong to the Configured NSSAI corresponding to the serving PLMN.

[0179] Allowed NSSAI: refers to the NSSAI provided by the serving PLMN in, for example, the registration process, indicating the network slice of the serving PLMN that the terminal is allowed to access in the current registration area (RA) in the network slice corresponding to the RequestedNSSAI.

[0180] Rejected NSSAI: refers to the NSSAI provided by the serving PLMN in, for example, the registration process, indicating that the network slice corresponding to the RequestedNSSAI is not allowed to be accessed by the terminal in the current RA.

[0181] The network slices corresponding to Rejected NSSAI can be divided into the following two categories: one is the network slice that is not allowed to be accessed in the current RA but can be accessed in the serving PLMN; the other is the network slice that is not allowed to be accessed in the entire serving PLMN.

[0182] Pending NSSAI: The NSSAI provided by the serving PLMN during the registration process indicates the S-NSSAI for which the network slice-specific authentication and authorization process is still pending. For details, please refer to the definition in the 3GPP 23.501 standard and will not be repeated here.

[0183] 3. Access network support capabilities for network slicing:

[0184] RAN's support capability for network slicing is divided based on the granularity of tracking areas (TAs). A TA can support one or more network slices. Cells within the same TA support the same network slice, and a cell supports only one frequency band.

[0185] For example, assuming that a certain access network device supports frequency (FR) 1 (FR1) and frequency 2 (FR2), since each cell supports only one frequency band, FR1 and FR2 are frequencies supported by different cells, for example, FR1 is the frequency supported by cell 1, and FR2 is the frequency supported by cell 2. Furthermore, assuming that cell 1 supports network slice 1 (corresponding to S-NSSAI 1) and cell 2 supports network slice 2 (corresponding to S-NSSAI 2), since cells in the same TA support the same network slice, cell 1 and cell 2 are cells in different TAs.

[0186] That is to say, if Figure 3As shown, cell 1 in TA1 supports network slice 1 on FR1, and cell 2 in TA2 supports network slice 2 on FR2. In addition, it should be noted that the physical coverage areas of cell 1 and cell 2 overlap in whole or in part.

[0187] The AMF network element's perception of the network slices supported by the RAN is also based on the TA granularity. The access network device can report the S-NSSAI supported by each TA to the AMF network element when establishing or updating the N2 connection with the AMF network element.

[0188] Exemplarily, the access network device may report the TAs it supports in the TA support list (supported TA list) information element; and report the S-NSSAI supported by each TA in each PLMN or SNPN in the tracking area identity (TAI) slice support list (TAI slice support list) information element.

[0189] 4. Slice selection:

[0190] When network slicing is deployed, network slice selection can be performed during the registration process. For example, when a terminal registers, it requests the network slice it wants to access, and the core network provides the terminal with the Allowed NSSAIs it can access. Subsequently, when the terminal transmits services, it selects the S-NSSAI from the Allowed NSSAIs and establishes a session using the network slice corresponding to the S-NSSAI.

[0191] See also Figure 4 , which is the part of the registration process related to slice selection, and specifically includes the following steps:

[0192] S401: A terminal sends a registration request to an access network device. Correspondingly, the access network device receives the registration request from the terminal.

[0193] The registration request includes the NSSAI requested by the terminal, namely, Requested NSSAI.

[0194] S402: The access network device forwards the NSSAI requested by the terminal to the initial AMF network element (initial AMF). Correspondingly, the initial AMF network element receives the NSSAI requested by the terminal forwarded by the access network device.

[0195] Among them, the access network device can forward the NSSAI requested by the terminal to the initial AMF network element through the N2 message.

[0196] S403. The initial AMF network element initiates a request to the UDM network element to obtain the subscribed NSSAI of the terminal.

[0197] S404. When the initial AMF network element cannot determine the Allowed NSSAI of the terminal, it requests slice selection from the NSSF network element and sends the NSSAI requested by the terminal, the NSSAI subscribed by the terminal, and the location information of the terminal to the NSSF network element.

[0198] S405. The NSSF network element replies the terminal's Allowed NSSAI to the initial AMF network element.

[0199] In addition, if the AMF network element needs to be switched, the NSSF network element also replies to the initial AMF network element with the target AMF set (or list) and the identifier (ID) of the network repository function (NRF) network element corresponding to the target AMF network element.

[0200] S406. If the AMF network element needs to be switched, the initial AMF network element queries the corresponding NFR network element for the information of the target AMF network element based on the NFR ID replied by the NSSF network element.

[0201] S407. The initial AMF network element sends an AMF relocation request to the target AMF network element. The AMF relocation request includes the Allowed NSSAI of the terminal replied by the NSSF network element.

[0202] As a possible implementation method, the initial AMF network element can send an AMF relocation request to the target AMF network element through the interface between AMF network elements, as shown in S407a.

[0203] As another possible implementation method, the initial AMF network element can also forward the AMF relocation request to the target AMF network element through the access network device.

[0204] For example, as shown in S407b, the initial AMF network element sends an AMF relocation request to the access network device. In addition to the Allowed NSSAI of the terminal replied by the NSSF network element, the AMF relocation request also includes the information of the target AMF network element. After receiving the AMF relocation request from the initial AMF network element, the access network device forwards the AMF relocation request to the target AMF network element based on the information of the target AMF network element included therein.

[0205] S408. The target AMF network element sends the terminal's Allowed NSSAI to the access network device.

[0206] S409: The access network device feeds back the terminal's Allowed NSSAI and the terminal's route selection policy (URSP) to the terminal.

[0207] Among them, URSP is generated by PCF during the registration process.

[0208] At this point, the terminal can know the network slices that can be accessed later and their corresponding URSPs when transmitting services.

[0209] In addition, according to the current 23.502 protocol, the triggering scenarios of the registration process mainly include: (1) the initial registration of the terminal to the core network; (2) the mobile registration update caused by the terminal moving to a TA outside the registration area (RA); (3) the registration update caused by the change of terminal capabilities; (4) the periodic registration update of the terminal in the inactive state; (5) emergency registration. In other words, the terminal can select the network slice in the above five scenarios. In other words, in the existing technology, in scenarios other than the above five scenarios, the terminal will not initiate the registration process.

[0210] 5. Redirection:

[0211] This application mainly introduces the process of a terminal initiating a registration request in a cell in TA1 of an access network device. If TA1 does not support the network slice requested by the terminal and TA2 of the access network device supports the network slice requested by the terminal, the terminal is redirected from the cell in TA1 to the cell in TA2. Figure 5 , mainly includes the following steps:

[0212] S501. A terminal sends a registration request to an AMF network element via an access network device. Accordingly, the AMF network element receives the registration request from the terminal via the access network device.

[0213] Among them, the terminal sends a registration request to the AMF network element through the access network device, including: the terminal sends a registration request to the AMF network element through cell 1 of the access network device, and cell 1 is the cell in TA1 of the access network device.

[0214] The registration request includes the NSSAI requested by the terminal, namely, Requested NSSAI.

[0215] In step S502, the AMF network element and the NSSAI network element perform network slice selection and determine the Allowed NSSAI of the terminal. For details, please refer to the above steps S402 to S405, which will not be repeated here.

[0216] For example, the first S-NSSAI included in the Requested NSSAI does not belong to the Allowed NSSAI. That is, the network slice corresponding to the first S-NSSAI does not belong to the network slice that the serving PLMN allows the terminal to access in TA1, or in other words, TA1 does not support the network slice corresponding to the first S-NSSAI. In other words, when the terminal sends a registration request to the AMF network element through cell 1 of the access network device, the first S-NSSAI belongs to the Rejected NSSAI.

[0217] In addition, in addition to the Allowed NSSAI, at least one of the Rejected NSSAI and the Configured NSSAI of the terminal is determined.

[0218] S503. The AMF network element sends an N2 message to the access network device, which includes the terminal's Allowed NSSAI.

[0219] Furthermore, it may also include at least one of Rejected NSSAI and Configured NSSAI.

[0220] S504: The access network device sends a Registration Accept message to the terminal, which includes the Allowed NSSAI of the terminal.

[0221] Furthermore, it may also include at least one of Rejected NSSAI and Configured NSSAI.

[0222] S505. The access network device determines the access frequency of the terminal based on the information obtained from the AMF network element.

[0223] For example, if a certain S-NSSAI included in the Requested NSSAI is not supported by the current TA, the AMF network element will provide the access network device with a Rejected NSSAI in addition to the Allowed NSSAI and Configured NSSAI, so that the access network device can redirect or steer the terminal to an access frequency that supports the S-NSSAI. After receiving the Rejected NSSAI from the AMF network element, the access network device can perform step S505 to determine the access frequency of the terminal, thereby determining the frequency of the neighboring cell.

[0224] S506. The access network device sends a radio resource control (RRC) connection release (RRC connection release) message to the terminal, which includes the neighboring cell frequency, the identifier of the network slice supported by the neighboring cell, and the cell reselection priority of the neighboring cell.

[0225] S507: The terminal executes RRC connection release and enters the RRC idle state, and performs cell reselection according to the cell reselection priority configured by the access network device.

[0226] Take the example where the terminal accesses cell 2 in TA2 through cell reselection, TA2 does not belong to the RA where the TA is located, and TA2 supports the network slice corresponding to the first S-NSSAI.

[0227] S508. The terminal re-initiates the registration process and sends a registration request to the AMF network element through cell 2 of the access network device.

[0228] The registration request may include the first S-NSSAI.

[0229] S509: Same as step S502.

[0230] S510. The AMF network element sends a Registration Accept message to the terminal through cell 2 of the access network device, including the terminal's Allowed NSSAI, which may include the first S-NSSAI. In other words, when the terminal sends a registration request to the AMF network element through cell 2 of the access network device, the first S-NSSAI belongs to the Allowed NSSAI.

[0231] At this point, the terminal can access the network slice corresponding to the first S-NSSAI through cell 2 and use the services provided by the network slice.

[0232] 6. Xn Handover:

[0233] The Xn interface refers to the interface between access network devices (i.e., between the source access network device before switching and the target access network device after switching). When there is an Xn interface between access network devices, or in other words, there is an Xn connection, taking the terminal switching from the source access network device to the target access network device as an example, the Xn switching process is as follows: Figure 6 As shown, specifically including:

[0234] S600, AMF network element sends mobility control information to the source access network device and the target access network device.

[0235] S601: The terminal reports measurement information to a source access network device.

[0236] For example, the measurement information includes reference signal receiving power (RSRP).

[0237] S602: The source access network device decides to switch the terminal to the target access network device through Xn switching according to the measurement information reported by the terminal and the local policy.

[0238] S603: The source access network device sends a handover request (Handover Request) message to the target access network device.

[0239] S604: The target access network device determines whether to accept the handover of the terminal. If the target access network device accepts the handover of the terminal, the following steps are continued.

[0240] S605: The target access network device sends a Handover Request Acknowledge message to the source access network device, indicating that the handover request is accepted. The Handover Request Acknowledge message may also include a Handover Command, instructing the terminal to access the target access network device through a random access procedure.

[0241] S606: The source access network device sends a radio resource control (RRC) reconfiguration (RRC Reconfiguration) message to the terminal, instructing the terminal to release the connection with the source access network device and attempt to access the target access network device through a random access procedure.

[0242] The above steps S600 to S606 may be referred to as the handover preparation phase. After the handover preparation phase is completed, the handover execution phase is performed, which mainly includes the following steps S607 to S609.

[0243] S607: The source access network device sends the SN status to the target access network device via a sequence number (SN) status transfer (SN StatusTransfer) message to synchronize the packet data convergence protocol (PDCP) SN.

[0244] S608: The terminal disconnects from the source access network device and establishes a connection with the target access network device through a random access process.

[0245] During the process of establishing a connection between the terminal and the target access network device, the source access network device forwards the user data sent by the UPF network element to the source access network device to the target access network device through the forwarding tunnel between the source access network device and the target access network device, and the target access network device caches the forwarded user data.

[0246] S609: The terminal completes the random access process, establishes an air interface connection with the target access network device, and completes the access network handover. Afterwards, the target access network device starts sending data received and buffered from the source access network device.

[0247] At this point, the access network switch is complete. The subsequent core network path switch mainly includes the following steps:

[0248] S610. The target access network device sends a Path Switch Request to the AMF network element, notifying the AMF network element that the terminal has been switched. The Path Switch Request may include the session to be switched and the AN tunnel port information used to establish the user plane connection. Furthermore, the Path Switch Request may also include the location information of the terminal, such as the current TAI of the terminal.

[0249] S611, AMF network element, SMF network element, UPF network element, etc. perform UPF path switching (PATH Switch). At the same time, the UPF network element sends an end marker (End Marker) from the original path, indicating that the data on the original path has been transmitted, and the new data will be sent from the switched path.

[0250] S612. The AMF network element sends a path switch request confirmation (PATH Switch Request Acknowledge) message to the target access network device to feedback the path switching status.

[0251] S613: The target access network device sends a UE Context Release message to the source access network device, instructing the source access network device to release the context of the terminal.

[0252] 7. N2 Handover:

[0253] N2 switching is applicable to scenarios where there is no Xn interface between access network devices, or in other words, no Xn connection. Taking the terminal switching from the source access network device to the target access network device as an example, the N2 switching process is as follows: Figure 7 As shown, specifically including:

[0254] S700: The source access network device decides to trigger N2 handover.

[0255] The source access network device finds that there is no Xn connection between it and the target access network device by querying local information, and the control plane message of the handover needs to be forwarded through the N2 interface.

[0256] S701. The source access network device sends a handover required message to the source AMF network element.

[0257] The handover request message may include a target identifier (Target ID) and a set of session identifiers to be handed over. The target identifier may include an identifier of a target access network device and a target TAI. The target TAI corresponds to a target TA that the terminal wants to access.

[0258] S702. The source AMF network element selects the target AMF network element.

[0259] If the target access network device is not within the service range of the source AMF network element, the source AMF network element selects the target AMF network element that serves the target access network device based on the identification information of the target access network device.

[0260] S703. The source AMF network element sends a create terminal context request message to the target AMF network element, which may include the target identifier and the session identifier set to be switched.

[0261] The create terminal context request message may be, for example, a Namf_Communication_CreateUEContext Request message, which is an N2 message type.

[0262] S704. The target AMF network element sends a session management request message 1 to the SMF network element, which may include the target identifier and the set of session identifiers to be switched.

[0263] The session management request message 1 may be, for example, a Namf_PDUSession_UpdateSMContextRequest message, which is an N2 session management message type.

[0264] S705. The SMF network element controls the establishment of an uplink tunnel between the PDU session anchor (PSA) and the target UPF network element.

[0265] S706. The SMF network element sends a session management response message 1 to the target AMF network element, which includes the session and QoS flow (QoS Flow) information accepted by the target UPF network element for switching.

[0266] The session management response message 1 may be, for example, a Namf_PDUSession_UpdateSMContextResponse message.

[0267] S707. The target AMF network element monitors the session management response message corresponding to the session management request message sent to each SMF network element. After receiving each session management response message or reaching the maximum waiting time, it starts to send a switching request to the target access network device.

[0268] S708. The target AMF network element sends a switching request to the target access network device. The switching request includes the session and QoS Flow information that the target UPF network element accepts switching.

[0269] S709: The target access network device feeds back a Handover Request Acknowledge message to the target AMF network element. The Handover Request Acknowledge message includes the session and QoS Flow information that the target access network device accepts the handover.

[0270] S710. The target AMF network element sends a session management request message 2 to the SMF network element based on the session status fed back by the target access network device, and feeds back the session and QoS Flow list that both the target access network device and the target UPF network element accept the handover.

[0271] The session management request message 2 may be, for example, a Namf_PDUSession_UpdateSMContextRequest message.

[0272] S711. The SMF network element sends a session management response message 2 to the target AMF network element based on the session status feedback from the target AMF network element, which includes information on the QoS Flow granularity.

[0273] The session management response message 2 may be, for example, a Namf_PDUSession_UpdateSMContextResponse message.

[0274] S712. The target AMF network element sends a create terminal context response message to the source AMF network element, which includes a list of rejected sessions and the corresponding rejection reasons.

[0275] The create terminal context response message may be, for example, a Namf_Communication_CreateUEContext Response message.

[0276] S713 , continuing the N2 handover execution phase, for details, please refer to the description in the existing protocol, which will not be repeated here.

[0277] The above mainly introduces network slicing and the network slice selection process. In actual application, the following scenario may occur: during a registration process, the terminal cannot access a network slice that the terminal wants to access because the TA it is currently in does not support it. Even if the terminal subsequently moves to a TA that supports the network slice, it still cannot normally access the network slice.

[0278] In one possible scenario, Figure 8a As shown, it is assumed that TA1 of access network device 1 supports network slice 2 (corresponding to S-NSSAI 2) on FR2; TA2 of access network device 2 supports network slice 2 on FR2, and TA3 of access network device 2 supports network slice 1 (corresponding to S-NSSAI 1) on FR1, and the physical coverage of TA2 and TA3 overlaps in whole or in part; TA4 of access network device 3 supports network slice 1 on FR1.

[0279] Currently, when assigning RAs to terminals, the AMF typically assigns TAs that support Allowed NSSAIs to the same RA. For example, a terminal in TA1 requests access to S-NSSAI 1 and S-NSSAI 2 through access network device 1. The network determines that the Allowed NSSAI is S-NSSAI 2, and both TA1 and TA2 support S-NSSAI 2. Therefore, the AMF assigns TA1 and TA2 to RA1.

[0280] Take the example of a terminal accessing the network through access network device 1 and completing the registration process, and the terminal wants to access network slice 1. At the location of TA1, since TA1 of access network device 1 does not support network slice 1, the terminal cannot access network slice 1 and finally accesses network slice 2.

[0281] Later, when the terminal moves into the service range of TA2 of access network device 2, since TA2 is divided into the range of RA1 and the terminal has not moved out of the range of RA1, according to the above five scenarios for triggering the registration process, the terminal will not re-initiate the registration process at this time. Therefore, even if there is a TA3 with the same physical coverage as TA2 that can support network slice 1, that is, even if there is a TA3 that can support network slice 1 at the current location of the terminal, the terminal still cannot access network slice 1.

[0282] As the terminal moves, when the terminal moves into the service range of TA4 of access network device 3, since the terminal has moved out of the range of RA1, the registration process can be re-initiated to access network slice 1.

[0283] That is to say, in Figure 8aIn the scenario shown, when the terminal moves to TA2 that supports network slice 1, the terminal still cannot access network slice 1 normally. It is not until it moves to TA4 that the terminal can access network slice 1 normally, affecting user experience and service performance.

[0284] In another possible scenario, Figure 8b As shown, it is assumed that TA1 of access network device 1 supports network slice 2 (corresponding to S-NSSAI 2); TA2 of access network device 2 supports network slice 2 and network slice 1 (corresponding to S-NSSAI 1); TA3 of access network device 3 supports network slice 1.

[0285] Because the AMF network element usually divides the TAs that support Allowed NSSAI into the same RA when dividing the RA corresponding to the terminal, similarly, for example, the terminal requests access to S-NSSAI 1 and S-NSSAI 2 through access network device 1 in TA1, and the Allowed NSSAI determined by the network side is S-NSSAI 2, and both TA1 and TA2 support S-NSSAI 2. Therefore, the AMF network element divides TA1 and TA2 into RA1. Based on the division of RA1, when the terminal moves to the service range of TA2 of access network device 2, it still cannot access network slice 1. For specific analysis, please refer to Figure 8a The scene shown will not be described in detail here.

[0286] In another possible scenario, Figure 8c As shown, it is assumed that the cell in TA1 of access network device 1 supports network slice 2 (corresponding to S-NSSAI 2) in FR2; the cell in TA2 of access network device 1 supports network slice 1 (corresponding to S-NSSAI 1) in FR1, and there is a non-overlapping area in the physical coverage of TA1 and TA2.

[0287] Take the example where the terminal accesses the network through the cell in TA1 of access network device 1 and goes through the registration process, and the terminal wants to access network slice 1, but the terminal is not within the physical coverage of TA2. Since TA1 of access network device 1 does not support network slice 1, the terminal cannot access network slice 1 and finally accesses network slice 2.

[0288] When a terminal enters the coverage area of ​​TA2 and switches from a cell in TA1 to a cell in TA2, a cell handover occurs within the access network device, or simply called an intra-site handover. In this scenario, even if the cell in TA2 supports network slice 1, the terminal device may still not be able to access network slice 1 according to the existing process.

[0289] Based on this, the present application provides a communication method based on network slicing, which can reduce the probability of the terminal being unable to access the network slice normally, increase the success rate of network slice access, and thereby improve service performance and user experience.

[0290] The technical solutions provided in the embodiments of the present application will be introduced below with reference to the accompanying drawings.

[0291] The network slicing-based communication method provided in the embodiments of the present application can be used in any communication system, which can be a 3GPP communication system, for example, a 5G mobile communication system, a new radio (NR) system, an NR V2X system, and other next-generation communication systems, or a non-3GPP communication system without limitation.

[0292] The network slicing-based communication method provided in the embodiments of the present application can be applied to various communication scenarios, for example, it can be applied to one or more of the following communication scenarios: enhanced mobile broadband (eMBB), ultra-reliable low latency communication (URLLC), machine type communication (MTC), massive machine type communication (mMTC), device to device (D2D), vehicle to everything (V2X), vehicle to vehicle (V2V), and internet of things (IoT), etc.

[0293] Below Figure 9a As an example, the communication system provided in the embodiment of the present application is described. Figure 9a As shown, the communication system may include at least one terminal and at least one network device.

[0294] In some embodiments, the network device involved in this application is a mobility management device. In this scenario, the communication system may also include a first access network device. Furthermore, the communication system may also include a second access network device.

[0295] In other embodiments, the network device involved in the present application is a first access network device. In this scenario, the communication system may further include a mobility management device. Furthermore, the communication system may also include a second access network device.

[0296] In some further embodiments, the network device involved in the present application is a second access network device. In this scenario, the communication system may further include a mobility management device and a first access network device.

[0297] That is to say, if Figure 9b As shown, the communication system provided in the present application may include one or more of a terminal, a first access network device, a second access network device, and a mobility management device.

[0298] Optional, such as Figure 9c As shown, the communication system may also include one or more of a session management network element, a policy control network element, a user plane network element, an application function network element, a slice selection function network element, a unified data management network element, or a data network (DN) connected to the operator network.

[0299] In this application, after accessing the network, the terminal can establish a protocol data unit (PDU) session, access the external data network DN through the PDU session, and interact with the application server deployed in the DN, such as Figure 9c As shown in the figure, depending on the DN accessed by the terminal, the network can select the user-plane network element accessing the DN as the anchor point of the PDU session, i.e., the protocol data unit anchor (PSA), according to the network policy, and access the application server through the N6 interface of the PSA. The application server of the same application can be deployed in multiple locations. The network can select a PSA that is close to the terminal and can support the terminal to access the DN according to the access location of the terminal, so as to reduce routing detours and reduce network delays.

[0300] The terminal involved in this application can be a device for implementing wireless communication functions, such as a terminal or a chip that can be used in a terminal, etc., which can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; can also be deployed on the water surface (such as a ship, etc.); can also be deployed in the air (such as an airplane, balloon, and satellite, etc.). Among them, the terminal can be user equipment (UE), access terminal, terminal unit, terminal station, mobile station, mobile station, remote station, remote terminal, mobile device, wireless communication equipment, terminal agent or terminal device in a 5G network or a future evolved public land mobile network (PLMN). An access terminal may be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, an in-vehicle device or a wearable device, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal used in industrial control, a wireless terminal used in self-driving vehicles, a wireless terminal used in remote medical care, a wireless terminal used in smart grids, a wireless terminal used in transportation safety, a wireless terminal used in smart cities, a wireless terminal used in smart homes, etc. The terminal may be mobile or fixed.

[0301] The access network device involved in this application is a device that connects a terminal to a wireless network, which can be an evolutionary Node B (eNB or eNodeB) in LTE; or a base station in a 5G network or a future evolved public land mobile network (PLMN), a broadband network gateway (BNG), an aggregation switch or a non-3GPP access device; or the access network device in the embodiment of this application can also be a wireless controller in a cloud radio access network (CRAN); or a transmission and reception point (TRP), or a device including a TRP, etc., which is not specifically limited in this embodiment of the application. Optionally, the base station in the embodiment of the present application can include various forms of base stations, such as: macro base stations, micro base stations (also called small stations), relay stations, access points, etc., which is not specifically limited in this embodiment of the present application.

[0302] The mobile management device involved in this application is mainly used for the attachment, mobility management, and tracking area update processes of terminals in mobile networks. The mobile management device terminates non-access stratum (NAS) messages, completes registration management, connection management, and reachability management, allocates tracking area lists (TA lists) and mobility management, and transparently routes session management (SM) messages to session management network elements. In a 5G communication system, the mobile management network element may be an AMF. In future communications such as sixth-generation (6G) communications, the mobile management network element may still be an AMF network element, or have other names, which is not limited in the embodiments of this application.

[0303] The slice selection function network element involved in this application is used to select a network slice for a terminal. In a 5G communication system, the slice selection function network element may be an NSSF network element. In future communications such as 6G communications, the network slice selection function network element may still be an NSSF network element or have other names, which is not limited in the embodiments of this application.

[0304] The policy control network element involved in this application includes user subscription data management functions, policy control functions, billing policy control functions, QoS control, etc., which are used to guide the unified policy framework of network behavior and provide policy rule information for control plane function network elements (such as AMF network elements, etc.). In the 5G communication system, the policy control network element can be a PCF network element. In future communications such as 6G communications, the policy control function network element can still be a PCF network element, or have other names, which is not limited in the embodiments of this application.

[0305] Taking the 5G communication system as an example, the embodiment of the present application is applicable to a possible Figure 9c The network architecture diagram corresponding to the communication system shown in FIG. Figure 1 shown.

[0306] It should be noted that the communication system and business scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. Ordinary technicians in this field can know that with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0307] The relevant functions of the terminal, access network equipment, and core network network elements involved in this application can be implemented by one device, or by multiple devices together, or by one or more functional modules within a device, or by one or more chips, or by a system on chip (SOC) or a chip system. The chip system can be composed of chips, or can include chips and other discrete devices. The embodiments of this application do not specifically limit this.

[0308] It is understandable that the above functions can be network elements in hardware devices, software functions running on dedicated hardware, or a combination of hardware and software, or virtualized functions instantiated on a platform (e.g., a cloud platform).

[0309] For example, the relevant functions of the terminal, access network equipment, and core network element involved in this application can be achieved through Figure 10 This is implemented by the communication device 1000 in FIG. Figure 10 FIG2 is a schematic diagram of the structure of a communication device 1000 provided in an embodiment of the present application. The communication device 1000 includes one or more processors 1001, a communication line 1002, and at least one communication interface ( Figure 10 The example in which the communication interface 1004 and a processor 1001 are included is merely exemplary), and a memory 1003 may also be included optionally.

[0310] The processor 1001 may be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of the program of the present application.

[0311] The communication line 1002 may include a path for connecting different components.

[0312] Communication interface 1004 can be a transceiver module for communicating with other devices or communication networks, such as Ethernet, RAN, and wireless local area networks (WLAN). For example, the transceiver module can be a device such as a transceiver or a transceiver. Alternatively, communication interface 1004 can be a transceiver circuit located within processor 1001, used to implement signal input and output to the processor.

[0313] The memory 1003 may be a device having a storage function. For example, it may be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, a random access memory (RAM) or other types of dynamic storage devices that can store information and instructions, or an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compact disc, laser disc, optical disc, digital versatile disc, Blu-ray disc, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto. The memory may be independent and connected to the processor via a communication line 1002. The memory may also be integrated with the processor.

[0314] Among them, the memory 1003 is used to store computer-executable instructions for executing the solution of this application, and the execution is controlled by the processor 1001. The processor 1001 is used to execute the computer-executable instructions stored in the memory 1003, thereby implementing the network slicing-based communication method provided in the embodiment of this application.

[0315] Alternatively, optionally, in an embodiment of the present application, the processor 1001 may also perform processing-related functions in the network slice usage control method provided in the following embodiment of the present application, and the communication interface 1004 is responsible for communicating with other devices or communication networks, which is not specifically limited in the embodiment of the present application.

[0316] Optionally, the computer-executable instructions in the embodiments of the present application may also be referred to as application code, which is not specifically limited in the embodiments of the present application.

[0317] In a specific implementation, as an embodiment, the processor 1001 may include one or more CPUs, such as Figure 10 CPU0 and CPU1 in.

[0318] In a specific implementation, as an embodiment, the communication device 1000 may include multiple processors, such as Figure 10 The processors 1001 and 1008 in FIG. 1 are processors 1001 and 1008. Each of these processors may be a single-core processor or a multi-core processor. The processors herein may include, but are not limited to, at least one of the following: a central processing unit (CPU), a microprocessor, a digital signal processor (DSP), a microcontroller unit (MCU), or an artificial intelligence processor, and other types of computing devices that run software. Each computing device may include one or more cores for executing software instructions to perform calculations or processing.

[0319] In a specific implementation, as an embodiment, the communication device 1000 may further include an output device 1005 and an input device 1006. The output device 1005 communicates with the processor 1001 and can display information in a variety of ways. For example, the output device 1005 can be a liquid crystal display (LCD), a light emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector. The input device 1006 communicates with the processor 1001 and can receive user input in a variety of ways. For example, the input device 1006 can be a mouse, a keyboard, a touch screen device, or a sensor device.

[0320] The communication device 1000 may also be referred to as a communication apparatus, which may be a general purpose device or a dedicated device. For example, the communication device 1000 may be a desktop computer, a portable computer, a network server, a personal digital assistant (PDA), a mobile phone, a tablet computer, a wireless terminal device, an embedded device, the above-mentioned terminal, the above-mentioned network device, or a Figure 10 The embodiment of the present application does not limit the type of the communication device 1000.

[0321] also, Figure 10 The structure shown in the figure does not constitute a limitation on the communication device, except Figure 10 In addition to the components shown, the communication device may include more or fewer components than shown, or combine certain components, or arrange the components differently.

[0322] The following combination Figure 9a or Figure 9b or Figure 9c The communication system shown describes the network slicing-based communication method provided in an embodiment of the present application.

[0323] It should be noted that in the following embodiments of the present application, the message names, parameter names, or information names between network elements are only examples. In other embodiments, they may also be other names, and the method provided in the present application does not make specific limitations on this.

[0324] It is understood that in the embodiments of the present application, each network element may perform some or all of the steps in the embodiments of the present application. These steps or operations are merely examples, and the embodiments of the present application may also perform other operations or variations of various operations. In addition, the steps may be performed in a different order than those presented in the embodiments of the present application, and it is possible that not all operations in the embodiments of the present application need to be performed.

[0325] See also Figure 11 , which is a flowchart of a communication method based on network slicing provided in an embodiment of the present application. Figure 11 Will combine Figure 8a and Figure 8b Describe the scenario. Figure 11 As shown, the method may include:

[0326] S1101. The network device receives information about the network slice that the terminal requests to access through the first access network device in the first network.

[0327] In some embodiments, the network device may be a mobility management device. In a 5G system, the mobility management device may be, for example, an AMF network element.

[0328] In some embodiments, the first network may be a PLMN or a SNPN, which is not specifically limited in this application. Figure 8a PLMNs including TA1 to TA4, or Figure 8b The first access network device may be Figure 8a Access network device 1 in, or Figure 8b Access network device 1 in.

[0329] The information about the network slice that the terminal requests to access includes identification information of the first network slice and identification information of the second network slice. In other words, the first network slice and the second network slice are network slices corresponding to the NSSAI requested by the terminal. For example, the identification information of the first network slice is S-NSSAI 1, and the identification information of the second network slice is S-NSSAI 2.

[0330] As an example, the slice identification information can be S-NSSAI or other information used to identify the slice, which is not specifically limited in this application.

[0331] In this case, the first network slice is not supported by the first tracking area of ​​the first access network device, or in other words, the first tracking area does not support the first network slice.

[0332] In some embodiments, the first tracking area may be the tracking area where the terminal is located when sending information about the network slice that the terminal requests to access. For example, the first tracking area may be Figure 8a TA1 in, or Figure 8b TA1 in.

[0333] The second tracking area in the first network supports the first network slice, that is, the first network slice is a network slice that the terminal is allowed to access in the first network. In other words, there is at least one tracking area in the first network that supports the first network slice. For example, the second tracking area can be Figure 8a TA3 in, or Figure 8b TA2 in.

[0334] In some embodiments, the network device may determine the network slice supported by the tracking area of ​​the first access network device, thereby determining that the first tracking area of ​​the first access network device does not support the first network slice. Furthermore, the network device may also obtain the Configured NSSAI of the terminal, thereby knowing that there is a tracking area in the first network that supports the first network slice. For ease of description, this application refers to the tracking area in the first network that supports the first network slice as the second tracking area, that is, the second tracking area in the first network supports the first network slice.

[0335] S1102. The network device determines the network slice that the terminal is allowed to access.

[0336] The network slice that the terminal is allowed to access is the network slice corresponding to the Allowed NSSAI of the terminal, including the second network slice. In addition, the Allowed NSSAI does not include the first network slice, or in other words, the first network slice does not belong to the network slice that the terminal is allowed to access, that is:

[0337] The network slices that the terminal requests to access: the first network slice and the second network slice.

[0338] Network slice that the terminal is allowed to access: the second network slice.

[0339] The network slice that does not allow the terminal to access: the first network slice.

[0340] It can be understood that the network slice that the terminal is allowed to access includes the second network slice, and thus, the second network slice is also the network slice that the terminal is allowed to access within the first network.

[0341] As an example, the network device can autonomously determine the network slice that the terminal is allowed to access; alternatively, the network device can determine the network slice that the terminal is allowed to access by interacting with a network slice selection function network element (such as an NSSF network element). This application does not make any specific limitations on this.

[0342] In some embodiments, in addition to determining the network slice to which the terminal is allowed to access, the network device also determines the network slice to which the terminal is denied access, thereby determining whether the first network slice is a network slice to which the terminal is denied access. The network slice to which the terminal is denied access is the network slice corresponding to the Rejected NSSAI of the terminal. This application takes the first network slice as an example for explanation, that is:

[0343] The network slices that the terminal requests to access include: a first network slice and a second network slice.

[0344] The network slice that the terminal is allowed to access includes: the second network slice. That is, the Allowed NSSAI includes S-NSSAI2.

[0345] The network slice to which the terminal is denied access includes: the first network slice. That is, the rejected NSSAI includes S-NSSAI1.

[0346] S1103: The network device determines the registration area.

[0347] In different implementation scenarios of this application, the scope of the registration area may be different, for example:

[0348] In a possible implementation scenario, the registration area excludes the tracking area that supports the first network slice and the second network slice. The tracking area that supports the first network slice and the second network slice can be understood as: a tracking area that supports both the first network slice and the second network slice; or it can also be understood as a tracking area that supports both the first network slice and the second network slice. This can be applied to Figure 8b For example, the tracking area supporting the first network slice and the second network slice can be Figure 8b TA2 in.

[0349] In some embodiments, the registration area excludes a tracking area, which can be understood as: the registration area does not include the tracking area; or the tracking area is not in the registration area; or the tracking area is deleted from the registration area.

[0350] As a possible implementation method, the registration area excludes the tracking area that supports the first network slice and the second network slice. It can be understood that: the registration area does not include the tracking area that supports the first network slice and the second network slice.

[0351] As a possible implementation method, the registration area excludes the tracking area supporting the first network slice and the second network slice, which can be understood as: the tracking area supporting the first network slice and the second network slice is not in the registration area.

[0352] As a possible implementation method, the registration area excludes the tracking area supporting the first network slice and the second network slice, which can be understood as: the tracking area supporting the first network slice and the second network slice is deleted from the registration area.

[0353] As a possible implementation, the registration area excludes the tracking area that supports the first network slice and the second network slice. It can be understood that the tracking area included in the registration area supports the second network slice and does not support the first network slice. Of course, the tracking area included in the registration area can support the second network slice and support other network slices in addition to the first network slice.

[0354] As a possible implementation method, the registration area excludes the tracking area that supports the first network slice and the second network slice. It can be understood that: the tracking area included in the registration area supports the second network slice, and the registration area excludes the tracking area that supports the first network slice.

[0355] For example, Figure 8bIn the scenario shown, taking the identification information of the first network slice as S-NSSAI 1 and the identification information of the second network slice as S-NSSAI 2 as an example, it is assumed that TA1 of access network device 1 supports the second network slice; TA2 of access network device 2 supports the first network slice and the second network slice; TA3 of access network device 3 supports the first network slice.

[0356] When the network device determines the registration area using the method provided in the application, the registration area excludes the tracking area that supports the first network slice and the second network slice. That is, the registration area excludes TA2. Therefore, the registration area determined by the network device does not include TA2. When the terminal subsequently moves from a cell in TA1 to a cell in TA2, since it moves to a TA outside the registration area, if the terminal still wants to access the first network slice, it can re-initiate the registration process to access the first network slice and use the services provided by the first network slice.

[0357] In another possible implementation scenario, the registration area excludes the tracking area of ​​the access network device supporting the first network slice and the second network slice. This can be applicable to Figure 8a For example, the access network device supporting the first network slice and the second network slice may be Figure 8a In the access network device 2, the tracking areas of the access network device 2 include TA2 and TA3.

[0358] It should be noted that, in the tracking area of ​​the access network device, the tracking area supporting the first network slice and the second network slice may be the same tracking area, for example, the tracking area 1 of the access network device supports the first network slice and the second network slice; or, the tracking area supporting the first network slice and the second network slice may also be different tracking areas, for example, the tracking area 1 of the access network device supports the first network slice, and the tracking area 2 of the access network device supports the second network slice.

[0359] As an example, the registration area may exclude all tracking areas of the access network device that supports the first network slice and the second network slice. In other words, when the access network device corresponding to the tracking area supporting the second network slice has one or more tracking areas supporting the first network slice, the tracking area supporting the second network slice is excluded from the registration area.

[0360] As a possible implementation method, the registration area excludes the tracking area of ​​the access network device that supports the first network slice and the second network slice. It can be understood that: the registration area does not include the tracking area of ​​the access network device that supports the first network slice and the second network slice.

[0361] As a possible implementation method, the registration area excludes the tracking area of ​​the access network device that supports the first network slice and the second network slice. It can be understood that the tracking area of ​​the access network device that supports the first network slice and the second network slice is not in the registration area.

[0362] As a possible implementation method, the registration area excludes the tracking area of ​​the access network device supporting the first network slice and the second network slice, which can be understood as: the tracking area of ​​the access network device supporting the first network slice and the second network slice is deleted from the registration area.

[0363] For example, Figure 8a In the scenario shown, taking the identification information of the first network slice as S-NSSAI 1 and the identification information of the second network slice as S-NSSAI 2 as an example, it is assumed that TA1 of access network device 1 supports the second network slice; TA2 of access network device 2 supports the second network slice, and TA3 supports the first network slice; TA4 of access network device 3 supports the first network slice.

[0364] When the network device determines the registration area using the method provided in the application, the registration area excludes the tracking areas of access network devices that support the first and second network slices. In other words, the registration area excludes the tracking areas of access network device 2, namely TA2 and TA3. Therefore, the registration area determined by the network device does not include TA2 or TA3. It is understandable that because TA3 does not support Allowed NSSAI, the RA itself will not include TA3. However, for TA2, although TA2 supports S-NSSAI 2, TA3 also exists under access network device 2 corresponding to TA2, and TA3 supports S-NSSAI 1. In this case, TA2 must be excluded from the RA when determining the RA. When the terminal subsequently moves from a cell in TA1 to a cell in access network device 2, since it moves to TA2 outside the registration area, if the terminal still wants to access the first network slice, it can re-initiate the registration process to access the first network slice and use the services provided by the first network slice.

[0365] S1104: The network device sends registration area information to the terminal.

[0366] As an example, the registration area information may include identification information of the tracking area in the registration area. The present application does not specifically limit the specific content of the registration area information.

[0367] As an example, when the terminal receives the information of the registration area and subsequently leaves the registration area, it can trigger a mobile registration update, that is, re-perform the registration process, and thus re-request the network slice it wants to access.

[0368] For example, Figure 8a Taking the scenario shown as an example, assuming that the terminal moves from the coverage of TA1 to the coverage of TA2, since TA2 is not within the RA, the terminal re-initiates the registration process. Assuming that the terminal still requests access to the first network slice (corresponding to S-NSSAI 1) in the re-initiated registration process, since TA2 does not support the first network slice, the first network slice in the registration process does not belong to the network slice that the terminal is allowed to access. However, TA3, which is physically covered by TA2, supports the first network slice, so that the access network device can send an RRC connection release message to redirect the terminal to the cell in TA3, so that the terminal can access the first network slice in the cell in TA3. For details, please refer to Figure 5 The process shown is not repeated here. Figure 5 The registration request in S501 may be understood as a registration request initiated by the terminal in the cell in TA2.

[0369] by Figure 8b Taking the scenario shown as an example, assuming that the terminal moves from the coverage of TA1 to the coverage of TA2, since TA2 is not in the RA, the terminal can re-initiate the registration process. Assuming that in the re-initiated registration process, the terminal still requests access to the first network slice (corresponding to S-NSSAI 1). Since TA2 supports the first network slice, the terminal accesses the first network slice in TA2.

[0370] Based on this solution, when determining the registration area, the network device excludes the tracking area that supports the first network slice and the second network slice, or excludes the tracking area of ​​the access network device that supports the first network slice and the second network slice. Therefore, when the terminal moves within the excluded tracking area, since the registration area of ​​the terminal does not include the tracking area and the tracking area supports the first network slice, the terminal can re-initiate the registration process and request access to the first network slice, thereby improving the success rate of access to the first network slice and thereby improving service performance and user experience.

[0371] See also Figure 12 , which is a flowchart of another network slicing-based communication method provided in an embodiment of the present application. Figure 12 Will combine Figure 11 Describe. Figure 12 As shown, the method may include:

[0372] S1201. The network device determines the network slices that the terminal is allowed to access and the network slices that the terminal is denied access to.

[0373] In some embodiments, before step S1201, the method may further include: the network device receives information about the network slice that the terminal requests to access through the first access network device in the first network.

[0374] For the related description of the network device and the first network, please refer to the above step S1101 and will not be repeated here.

[0375] The information of the network slice that the terminal requests to access includes the identification information of the first network slice and the identification information of the second network slice. In other words, the first network slice and the second network slice are the network slices corresponding to the terminal's requested NSSAI.

[0376] In some embodiments, the network device determines the network slices that the terminal is allowed to access and the network slices that the terminal is denied access to, which may include: the network device receives information about the network slices that the terminal is allowed to access and the network slices that the terminal is denied access to from the slice selection function network element.

[0377] Among them, this application is illustrated by taking the example that the network slice that allows the terminal to access includes the second network slice, and the network slice that denies the terminal access includes the first network slice.

[0378] In some embodiments, the first network slice is not supported by the first tracking area of ​​the first access network device, or in other words, the first tracking area does not support the first network slice; the second network slice is a network slice supported by the first tracking area, or in other words, the first tracking area supports the second network slice.

[0379] In some embodiments, the second tracking area in the first network supports the first network slice, that is, the first network slice is a network slice within the first network that the terminal is allowed to access.

[0380] As an example, the network device may determine the network slices supported by the tracking area of ​​the first access network device, thereby determining that the first tracking area of ​​the first access network device does not support the first network slice. Furthermore, the network device may obtain the Configured NSSAI of the terminal, thereby knowing that there is a tracking area in the first network that supports the first network slice, that is, the first network slice is a network slice within the first network that the terminal is allowed to access. In this application, the tracking area in the first network that supports the first network slice is recorded as the second tracking area.

[0381] S1202. The network device determines the registration area of ​​the terminal based on the network slices to which the terminal is allowed to access and the network slices to which the terminal is denied access.

[0382] In one possible implementation scenario, the registration area excludes the tracking areas supporting the first network slice and the second network slice.

[0383] In another possible implementation scenario, the registration area excludes the tracking areas of access network devices supporting the first network slice and the second network slice.

[0384] For detailed description, please refer to the relevant description in the above step S1103, which will not be repeated here. This method of determining the registration area can be understood as taking into account the network slices that are denied access by the network because the current TA does not support them when determining the registration area.

[0385] In another possible design, the registration area excludes tracking areas that support network slices that allow terminal access and network slices that deny terminal access, or the registration area excludes tracking areas of access network devices that support network slices that allow terminal access and network slices that deny terminal access. That is, when determining the scope of the registration area, it is not necessary to consider why a network slice is denied access by the network. As long as the network slice is denied access and belongs to a network slice that denies terminal access, then when determining the scope of the registration area, the tracking areas that support network slices that allow terminal access and network slices that deny terminal access, or the tracking areas of access network devices that support network slices that allow terminal access and network slices that deny terminal access, are considered to be excluded from the registration area.

[0386] For example, assume the following scenario:

[0387] The network slices that the terminal requests to access: the first network slice, the second network slice, and the third network slice.

[0388] Network slice that the terminal is allowed to access: the second network slice.

[0389] Network slices that the terminal is denied access to: the first network slice and the third network slice.

[0390] Therefore, when determining the registration area, it is possible to consider excluding from the registration area the tracking area that supports the first network slice and the second network slice, or the tracking area of ​​the access network device that supports the first network slice and the second network slice, or the tracking area that supports the third network slice and the second network slice, or the tracking area of ​​the access network device that supports the third network slice and the second network slice, or the tracking area that supports the first network slice, the second network slice and the third network slice, or the tracking area of ​​the access network device that supports the first network slice, the second network slice and the third network slice.

[0391] S1203: The network device sends registration area information to the terminal.

[0392] Here, please refer to the relevant instructions in the above step S1104, which will not be repeated here.

[0393] Based on this solution, the registration area of ​​the terminal is determined according to the network slices that the terminal is allowed to access and the network slices that the terminal is denied access to, so that the registration area excludes the tracking areas that support the network slices that the terminal is allowed to access and the network slices that the terminal is denied access to, or the tracking areas of the access network devices that support the network slices that the terminal is allowed to access and the network slices that the terminal is denied access to. Therefore, when the terminal moves within the excluded tracking area, since the registration area of ​​the terminal does not include the tracking area and the tracking area supports the first network slice, the terminal can re-initiate the registration process and request access to the first network slice, thereby improving the success rate of accessing the first network slice, and thereby improving service performance and user experience.

[0394] above Figure 11 and Figure 12 The method shown provides a way to divide the registration area, see Figure 13 , is a flowchart of another communication method based on network slicing provided in an embodiment of the present application, which provides another way to divide the registration area, such as Figure 13 As shown, the method may include:

[0395] S1301. In a registration process of a first network, a network device determines an Allowed NSSAI of a terminal.

[0396] The description of the first network and the network device can refer to the above step S1101, and the registration process and the method for the network device to determine the Allowed NSSAI can refer to Figure 4 The process shown will not be repeated here.

[0397] S1302. The network device determines a first type of network slice.

[0398] Among them, the first type of network slice is a network slice that the first network allows the terminal to access, which does not belong to the Allowed NSSAI network slice of the terminal.

[0399] For example, assume the following scenario:

[0400] The network slices that the terminal requests to access: the first network slice, the second network slice, and the third network slice.

[0401] Network slice that the terminal is allowed to access: the second network slice.

[0402] The network slices that do not allow terminal access are: the first network slice and the third network slice.

[0403] The network slices that the first network (e.g., the current PLMN) allows the terminal to access include: the first network slice, the second network slice, and the fourth network slice. For example, the network slices that the first network allows the terminal to access can be reflected by the configured NSSAI of the terminal in the first network.

[0404] The network slice that the second network (e.g., other PLMN) allows the terminal to access: the third network slice.

[0405] In this scenario, the first type of network slice includes the first network slice and the fourth network slice.

[0406] S1303: The network device determines the registration area.

[0407] In different implementation scenarios of this application, the scope of the registration area may be different, for example:

[0408] In one possible implementation scenario, the registration area excludes the tracking area that supports at least one network slice corresponding to the Allowed NSSAI and at least one network slice of the first type.

[0409] Among them, supporting the tracking area of ​​at least one network slice corresponding to Allowed NSSAI and at least one network slice of the first type can be understood as: supporting both the tracking area of ​​at least one network slice corresponding to Allowed NSSAI and at least one network slice of the first type; or, supporting the tracking area of ​​at least one network slice corresponding to Allowed NSSAI and at least one network slice of the first type at the same time.

[0410] Exemplarily, based on the scenario assumed in S1302, the registration area may exclude the tracking area that supports the second network slice and the first network slice; or, it may exclude the tracking area that supports the second network slice and the fourth network slice; or, it may exclude the tracking area that supports the second network slice, the first network slice, and the fourth network slice.

[0411] In another possible implementation scenario, the registration area excludes the tracking area of ​​the access network device that supports at least one network slice corresponding to the Allowed NSSAI and at least one first type of network slice.

[0412] It should be noted that, in the tracking area of ​​the access network device, the tracking area that supports at least one network slice corresponding to Allowed NSSAI and at least one first type of network slice may be the same tracking area, for example, tracking area 1 of the access network device supports at least one network slice corresponding to Allowed NSSAI and at least one first type of network slice; or, the tracking areas that support at least one network slice corresponding to Allowed NSSAI and at least one first type of network slice may also be different tracking areas, for example, tracking area 1 of the access network device supports at least one network slice corresponding to Allowed NSSAI, and tracking area 2 of the access network device supports at least one first type of network slice.

[0413] As an example, the registration area may exclude all tracking areas of access network devices that support at least one network slice corresponding to Allowed NSSAI and at least one first type of network slice. In other words, when the access network device corresponding to the tracking area supporting the second network slice has one or more tracking areas that support at least one first type of network slice as above, the tracking area supporting the second network slice is excluded from the registration area.

[0414] For example, based on the scenario assumed in S1302, the registration area may exclude the tracking area of ​​the access network device that supports the second network slice and the first network slice; or, it may exclude the tracking area of ​​the access network device that supports the second network slice and the fourth network slice; or, it may exclude the tracking area of ​​the access network device that supports the second network slice, the first network slice, and the fourth network slice.

[0415] S1304: The network device sends registration area information to the terminal.

[0416] Here, please refer to the relevant instructions in the above step S1104, which will not be repeated here.

[0417] Based on this solution, for a first-type network slice that is not included in the network slices permitted for terminal access during the registration process of the first network but is included in the network slices permitted for terminal access by the first network, regardless of whether the network slice requested by the terminal to access during this registration process carries the identifier of the first network slice, since the first-type network slice is included in the network slices permitted for terminal access by the first network, the terminal may subsequently desire to access a certain first-type network slice. Therefore, the network device considers this first-type network slice when determining the registration area. For example, the registration area excludes the tracking area that supports at least one network slice corresponding to the Allowed NSSAI and at least one first-type network slice, or excludes the tracking area of ​​the access network device that supports at least one network slice corresponding to the Allowed NSSAI and at least one first-type network slice. Therefore, if the terminal moves within the excluded tracking area, since the terminal's registration area does not include the tracking area and the tracking area supports at least one first-type network slice, when the terminal desires to access a certain first-type network slice, it can re-initiate the registration process and request access to at least one first-type network slice, thereby improving the success rate of network slice access and thereby improving service performance and user experience.

[0418] above Figures 11 to 13 The method shown reduces the probability of the terminal being unable to access the target network slice (such as the first network slice mentioned above) normally by dividing the registration area, thereby improving the success rate of network slice access. In addition, the present application also provides a method for improving the success rate of network slice access by other means.

[0419] See also Figure 14 , is a flow chart of a communication method based on network slicing provided by this application, which can be applied to the scenario where a terminal switches from a first cell to a second cell, and the network device notifies the terminal of the available network slices in the second cell. The switching scenario can be an intra-site switching, that is, the first cell and the second cell belong to the same access network device; or it can be an inter-site switching, that is, the first cell and the second cell belong to different access network devices. For example, Figure 14 The method shown can be applied to Figure 8b or Figure 8c The scene shown. Figure 14 As shown, the method includes the following steps:

[0420] S1401. The network device determines the first network slice.

[0421] In some embodiments, the network device may be a mobility management device. In a 5G system, the mobility management device may be, for example, an AMF network element.

[0422] In other embodiments, the network device may be an access network device. For example, when the first cell belongs to a first access network device and the second cell belongs to a second access network device, the network device is the second access network device; or when both the first cell and the second cell belong to the first access network device, the network device is the first access network device.

[0423] Among them, the first network slice does not belong to the network slice that the terminal is allowed to access in the first cell, or when the terminal initiates a registration process in the first cell, the network slice corresponding to the Allowed NSSAI of the terminal does not include the first network slice. In this application, the network slice that is not allowed to the terminal is referred to as the target network slice, and there may be one or more target network slices.

[0424] The registration area of ​​the terminal includes the first cell and the second cell.

[0425] In some embodiments, the first cell is a cell in a first TA, the second cell is a cell in a second TA, and the first TA and the second TA are different TAs.

[0426] In some embodiments, the first network slice is included in the network slice that the terminal requests to access in the first cell. That is, the terminal initiates a registration process in the first cell and requests access to the first network slice. However, the first network slice in the first cell is not a network slice that allows the terminal to access, or in other words, the first network slice in the first cell is a network slice that denies the terminal access. As a result, the terminal cannot access the first network slice in the first cell. According to subsequent steps, the terminal can access the first network slice that is inaccessible in the first cell in the second cell.

[0427] In some embodiments, the first network slice is included in the network slice configured by the terminal in the first network; in other words, the first network slice is included in the network slice corresponding to the Configured NSSAI of the terminal, or in other words, the first network slice is the network slice that the terminal is allowed to access in the first network. In other words, regardless of whether the terminal requests access to the first network slice when initiating the registration process in the first cell, since the first network slice is included in the network slice configured by the terminal in the first network, the terminal may subsequently want to access the first network slice. The first network slice does not belong to the network slices that the terminal is allowed to access in the first cell, and thus, the terminal cannot access the first network slice in the first cell. According to subsequent steps, the terminal can access the first network slice that is inaccessible in the first cell in the second cell.

[0428] For example, based on Figure 8bIn the scenario shown, the first cell is a cell in TA1 of access network device 1, the second cell is a cell in TA2 of access network device 2, and the identification information of the first network slice is S-NSSAI 1. The terminal requests access to S-NSSAI 1 and S-NSSAI 2 through access network device 1 in TA1. The Allowed NSSAI determined by the network side is S-NSSAI 2, and both TA1 and TA2 support S-NSSAI 2. Therefore, the registration area RA1 of the terminal includes TA1 and TA2. Or, based on Figure 8c In the scenario shown, the first cell is a cell in TA1 of access network device 1, the second cell is a cell in TA2 of access network device 1, and the identification information of the first network slice is S-NSSAI 1. Similarly, the registration area RA1 of the terminal includes TA1 and TA2.

[0429] In the above two scenarios, the terminal initiates a registration request in the first cell, requesting access to the first network slice and the second network slice (taking the identification information S-NSSAI 2 as an example). The first network slice does not belong to the network slices allowed to be accessed by the terminal in the first cell, and the second network slice belongs to the network slices allowed to be accessed by the terminal in the first cell. Thus, the terminal accesses the second network slice in the first cell.

[0430] S1402. When switching the terminal from the first cell to the second cell, the network device determines that the first network slice is available in the second cell.

[0431] In some embodiments, the reason why the network device determines that the first network slice is available in the second cell may be that the second TA in which the second cell is located supports the first network slice.

[0432] For example, based on Figure 8b or Figure 8c In the scenario shown, when the terminal switches from the first cell in TA1 to the second cell in TA2, the network device can determine that the first network slice is available in the second cell.

[0433] S1403. The network device notifies the terminal that the first network slice is available in the second cell.

[0434] In some embodiments, when the network device is a mobility management device, the network device can notify the terminal that the first network slice is available in the second cell through a non-access stratum (NAS) message.

[0435] In other embodiments, when the network device is a first access network device or a second access network device, the network device may notify the terminal through a mobility management device that the first network slice is available in the second cell. For example, the network device notifies the terminal through the mobility management device that the first network slice is available in the second cell, and then triggers the mobility management device to notify the terminal through a NAS message that the first network slice is available in the second cell. Of course, the network device may also notify the terminal through other methods. For example, the network device may notify the terminal through an RRC message that the first network slice is available in the second cell. This application does not specifically limit the notification method.

[0436] As an example, the network device may send identification information of the first network slice to the terminal to notify the terminal that the first network slice is available in the second cell. Furthermore, the network device may also send a cell identifier of the second cell to the terminal.

[0437] In the prior art, the first network slice does not belong to the network slice that the terminal is allowed to access in the first cell, that is, when the terminal initiates the registration process in the first cell, it cannot access the first network slice. Since the registration area of ​​the terminal includes the first cell and the second cell, when the terminal switches from the first cell to the second cell, the terminal will not be triggered to perform the re-registration process. Even if the first network slice is available in the second cell, the terminal will not initiate the registration process in the second cell, and thus cannot access the first network slice in the second cell. Based on the solution of the present application, when the terminal switches from the first cell to the second cell and determines that the first network slice is available in the second cell, the terminal is notified that the first network slice is available in the second cell. Therefore, if the terminal still wants to access the first network slice, it can initiate a registration process to request access to the first network slice, thereby improving the success rate of accessing the first network slice, improving service performance and user experience.

[0438] As mentioned above, the network device can be a mobile management device or an access network device. When the network device is a mobile management device, please refer to the following Figure 20 or Figure 21 When the network device is an access network device and the switching is within the site, please refer to the following Figure 22 When the network device is an access network device and the switching is between stations, please refer to the following Figure 23 The specific implementation method.

[0439] Apart from Figure 14 In addition to the methods shown, see Figure 15, the present application also provides a communication method based on network slicing that can be applied to the following scenarios: a terminal switches from a first cell to a second cell, and there is a third cell that has the same physical coverage as the second cell. The switching scenario can be intra-site switching, that is, the first cell and the second cell belong to the same access network device; or, it can be inter-site switching, that is, the first cell and the second cell belong to different access network devices. For example, Figure 15 The method shown can be applied to Figure 8a The scene shown.

[0440] like Figure 15 As shown, the method includes the following steps:

[0441] S1501. The network device determines the first network slice.

[0442] In some embodiments, the network device may be a mobile management device, or a first access network device, or a second access network device. Please refer to the relevant description in the above step S1401 and will not repeat it here.

[0443] The first network slice does not belong to a network slice that allows the terminal to access in the first cell, the registration area of ​​the terminal includes the first cell and the second cell, and the physical coverage area of ​​the third cell fully or partially overlaps with the physical coverage area of ​​the second cell.

[0444] In some embodiments, the third cell may be referred to as a cell physically co-covered with the second cell.

[0445] In some embodiments, the first cell is a cell in a first TA, the second cell is a cell in a second TA, and the third cell is a cell in a third TA, and the first TA, the second TA, and the third TA are different TAs.

[0446] In some embodiments, the first network slice is included in the network slice configured by the terminal in the first network, and / or, the first network slice is included in the network slice that the terminal requests to access in the first cell. Please refer to the relevant description in the above step S1401 and will not repeat it here.

[0447] For example, based on Figure 8aIn the scenario shown, the first cell is a cell in TA1 of access network device 1, the second cell is a cell in TA2 of access network device 2, and the third cell is a cell in TA3 of access network device 2. The identification information of the first network slice is S-NSSAI 1. For example, the terminal requests access to S-NSSAI 1 and S-NSSAI2 through access network device 1 in TA1. The Allowed NSSAI determined by the network side is S-NSSAI 2, and both TA1 and TA2 support S-NSSAI 2. Therefore, the registration area RA1 of the terminal includes TA1 and TA2. The terminal initiates a registration request in the first cell, requesting access to the first network slice and the second network slice (taking the identification information as S-NSSAI 2 as an example). The first network slice is not a network slice that the terminal is allowed to access in the first cell, and the second network slice is a network slice that the terminal is allowed to access in the first cell. Therefore, the terminal accesses the second network slice in the first cell.

[0448] S1502. When switching the terminal from the first cell to the second cell, the network determines that the first network slice is available in the third cell.

[0449] In some embodiments, the reason why the network device determines that the first network slice is available in the third cell may be that the third TA in which the third cell is located supports the first network slice.

[0450] For example, based on Figure 8a In the scenario shown, when the terminal switches from the first cell in TA1 to the second cell in TA2, since TA2 is divided into the range of RA1 and the terminal does not move out of the range of RA1, the terminal will not re-initiate the registration process, and therefore the terminal will still not access the first network slice. However, since the cell of access network device 2 includes a third cell whose physical coverage area partially or completely overlaps with the physical coverage area of ​​the second cell, TA3 where the third cell is located supports the first network slice, so the network device can determine that the first network slice is available in the third cell.

[0451] S1503. The network device notifies the terminal that the first network slice is available in the third cell.

[0452] Among them, the notification method can refer to the method in which the network device notifies the terminal that the first network slice is available in the second cell in the above step S1403, and will not be repeated here.

[0453] In the prior art, the first network slice does not belong to the network slice that the terminal is allowed to access in the first cell, that is, when the terminal initiates the registration process in the first cell, it cannot access the first network slice. Since the registration area of ​​the terminal includes the first cell and the second cell, when the terminal switches from the first cell to the second cell, the terminal will not be triggered to perform the re-registration process. Even if the first network slice is available in the third cell that has the same physical coverage as the second cell, the terminal will not re-initiate the registration process in the second cell, and thus cannot access the first network slice at the location of the second cell. Based on the solution of the present application, when the terminal switches from the first cell to the second cell and determines that the first network slice is available in the third cell, the terminal is notified that the first network slice is available in the third cell. Therefore, if the terminal still wants to access the first network slice, it can access the first network slice in the third cell, thereby improving the success rate of accessing the first network slice and using the services provided by the first network slice.

[0454] As mentioned above, the network device can be a mobile management device or an access network device. When the network device is a mobile management device, please refer to the following Figure 24 When the network device is an access network device and the switching is within the site, please refer to the following Figure 25 When the network device is an access network device and the switching is between stations, please refer to the following Figure 26 The specific implementation method.

[0455] Apart from Figure 14 and Figure 15 In addition to the method shown, the present application also provides a network slicing-based communication method that can be applied to the following scenarios: a method in which a terminal accesses a first cell and the neighboring cell of the first cell includes a second cell. The first cell and the second cell may belong to the same access network device; or the first cell and the second cell may belong to different access network devices. For example, Figure 16 The method shown can be applied to Figure 8b or Figure 8c The scene shown. Figure 16 As shown, the method includes the following steps:

[0456] S1601. The network device determines the first network slice.

[0457] Among them, step S1601 is similar to step S1401. Please refer to the relevant instructions in step S1401 and will not be repeated here.

[0458] S1602. The network device determines that the first network slice is available in the second cell.

[0459] In some embodiments, the reason why the network device determines that the first network slice is available in the second cell may be that the second TA in which the second cell is located supports the first network slice.

[0460] In some embodiments, the reason why the network device determines that the first network slice is available in the second cell may be that the second TA where the second cell is located supports the first network slice, and the cell signal quality of the second cell is greater than the first threshold, and the terminal can access the second cell.

[0461] In some embodiments, the network device may determine that the first network slice is available in the second cell before the terminal switches from the first cell to the second cell.

[0462] S1603. The network device notifies the terminal that the first network slice is available in the second cell.

[0463] Among them, step S1603 is similar to step S1403. Please refer to the relevant instructions in step S1403 and will not be repeated here.

[0464] The difference between step S1603 and step S1403 is that step S1403 is triggered by handover, or in other words, in a handover scenario, the network device notifies the terminal that the first network slice is available in the second cell. However, step S1603 is independent of handover. For example, the network device can notify the terminal that the first network slice is available in the second cell before the handover process occurs.

[0465] S1604. The network device sends the cell identifier of the second cell to the terminal.

[0466] In some embodiments, the cell identifier of the second cell can be used for the terminal to access the second cell, thereby accessing the first network slice available in the second cell.

[0467] In the prior art, the first network slice does not belong to the network slice that the terminal is allowed to access in the first cell, that is, when the terminal initiates the registration process in the first cell, it cannot access the first network slice. Since the registration area of ​​the terminal includes the first cell and the second cell, when the terminal switches from the first cell to the second cell, the terminal will not be triggered to perform the re-registration process. Even if the first network slice is available in the second cell, the terminal will not initiate the registration process in the second cell, and thus cannot access the first network slice in the second cell. Based on the solution of the present application, when the terminal switches from the first cell to the second cell and determines that the first network slice is available in the second cell, the terminal is notified that the first network slice is available in the second cell, and the cell identifier of the second cell is sent. Therefore, if the terminal still wants to access the first network slice, it can access the second cell and initiate the registration process to request access to the first network slice, thereby improving the success rate of accessing the first network slice and using the services provided by the first network slice.

[0468] Apart from Figure 16 In addition to the methods shown, see Figure 17 , the present application also provides a network slicing-based communication method applicable to the following scenarios: a terminal accesses a first cell, the neighboring area of ​​the first cell includes a second cell, and there is a third cell that has the same physical coverage as the second cell. The first cell and the second cell may belong to the same access network device; or the first cell and the second cell may belong to different access network devices. For example, Figure 17 The method shown can be applied to Figure 8a The scene shown. Figure 17 As shown, the method includes the following steps:

[0469] S1701. The network device determines the first network slice.

[0470] Among them, step S1701 is similar to step S1501. Please refer to the relevant instructions in step S1501 and will not be repeated here.

[0471] S1702. The network determines that the first network slice is available in the third cell.

[0472] In some embodiments, the reason why the network device determines that the first network slice is available in the third cell may be that the third TA in which the third cell is located supports the first network slice.

[0473] In some embodiments, the network device may determine that the first network slice is available in the third cell before the terminal switches from the first cell to the second cell.

[0474] S1703. The network device notifies the terminal that the first network slice is available in the third cell.

[0475] Among them, the notification method can refer to the method in which the network device notifies the terminal that the first network slice is available in the second cell in the above step S1403, and will not be repeated here.

[0476] S1704. The network device sends the cell identifier of the third cell to the terminal.

[0477] In some embodiments, the cell identifier of the third cell can be used for the terminal to access the third cell, thereby accessing the first network slice available in the third cell.

[0478] In the prior art, the first network slice does not belong to the network slice that the terminal is allowed to access in the first cell, that is, when the terminal initiates the registration process in the first cell, it cannot access the first network slice. Since the registration area of ​​the terminal includes the first cell and the second cell, when the terminal switches from the first cell to the second cell, the terminal will not be triggered to perform the re-registration process. Even if the first network slice is available in the third cell that is physically co-covered with the second cell, the terminal will not re-initiate the registration process in the second cell, and thus cannot access the first network slice at the location of the second cell. Based on the solution of the present application, when the neighboring area of ​​the first cell accessed by the terminal includes the second cell, and there is a third cell that is physically co-covered with the second cell, when it is determined that the first network slice is available in the third cell, the terminal is notified that the first network slice is available in the third cell, and the cell identifier of the third cell is sent. Therefore, if the terminal still wants to access the first network slice, it can access the third cell and request access to the first network slice, thereby improving the success rate of accessing the first network slice and using the services provided by the first network slice.

[0479] above Figures 11 to 17 The network slicing-based communication method provided in this application is introduced from the perspective of network equipment. The method is introduced from the perspective of the terminal below.

[0480] See also Figure 18 , is a communication method based on network slicing applied to a terminal provided by the present application. The method can be applied to the process in which the above-mentioned network device notifies the terminal that the first network slice can be used in the second cell. That is, the method can be considered as Figure 14 or Figure 16 In the method, the network device notifies the terminal that the first network slice is available in the second cell, and the terminal implements the method.

[0481] S1801. The terminal learns from the network device that the first network slice is available in the second cell.

[0482] Among them, the first network slice in the first cell does not belong to the network slice that the terminal is allowed to access. The registration area of ​​the terminal includes the first cell and the second cell. For details, please refer to the relevant description in the above step S1401, which will not be repeated here.

[0483] S1802. The terminal initiates a registration process for the application corresponding to the first network slice.

[0484] In some embodiments, the terminal initiates a registration process for an application corresponding to a first network slice, which may include: in response to the terminal's context not including a session for the application and not including a routing selection policy for the application, the terminal determines whether the first network slice is the network slice corresponding to the application; in the case that the first network slice is the network slice corresponding to the application, the terminal initiates a registration process for the application.

[0485] In some embodiments, the terminal further receives a cell identifier from the network device, where the cell identifier is for the second cell. In other words, the terminal receives the cell identifier of the second cell from the network device. In this scenario, the terminal initiating a registration process for an application corresponding to the first network slice may include: the terminal accessing the second cell and initiating a registration process for the application corresponding to the first network slice through the second cell.

[0486] In the prior art, since the first network slice does not belong to the network slice that the terminal is allowed to access in the first cell, the terminal cannot access the first network slice in the first cell. Since the registration area of ​​the terminal includes the first cell and the second cell, even if the terminal moves from the first cell to the coverage area of ​​the second cell, the terminal will not re-initiate the registration process and thus cannot access the first network slice. Based on the solution of the present application, the terminal can learn from the network device that the first network slice is available in the second cell. Therefore, when the application of the terminal corresponds to the first network slice, a registration process can be initiated for the application to request access to the first network slice, thereby improving the success rate of access to the first network slice.

[0487] In other words, compared with the several scenarios in the prior art for triggering the terminal to initiate the registration process, the present application adds a scenario for triggering the terminal to initiate the registration process: when the network device notifies the terminal that the first network slice is available in the second cell, the terminal can initiate the registration process according to the initiated application.

[0488] It is understandable that when the terminal learns from the network device that the first network slice is available in the third cell, the implementation of the terminal is the same as Figure 18 The method shown is similar, and the second cell can be replaced by the third cell for further understanding. Please refer to the above related instructions and will not be repeated here.

[0489] Above, the network slicing-based communication method provided by this application is introduced from the perspective of each device. Below, from the perspective of interaction between each device, the above method is applied to a specific process for explanation.

[0490] See also Figure 19 , taking the network device as a mobile management device as an example, this application provides a method of Figures 11 to 13 The method shown is applied to a flow chart of a specific process. Figure 19 The method shown can be applied to Figure 8a or Figure 8b The method includes the following steps:

[0491] S1901: A terminal sends a first message to a first access network device. Correspondingly, the first access network device receives the first message from the terminal.

[0492] The first access network device is an access network device in the first network. For the first network, reference may be made to the relevant description in the above step S1101 and details will not be repeated here.

[0493] In some embodiments, the first message may be an RRC message.

[0494] The first message includes a registration request (Registration Request), which includes information about the network slice that the terminal requests to access (for example, Requested NSSAI), and the information about the network slice that the terminal requests to access includes identification information of the first network slice and identification information of the second network slice.

[0495] Here, this application is described by taking the example of a terminal accessing the first network in the first TA of the first access network device and sending the first message to the first access network device. Figure 8a In the scenario, the first TA is Figure 8a TA1 in Figure 8b In the scenario, the first TA is Figure 8b TA1 in.

[0496] S1902: The first access network device sends a registration request to the mobility management device. Correspondingly, the mobility management device receives the registration request from the first access network device.

[0497] The registration request is received by the first access network device from the terminal in step S1901. Thus, steps S1901 and S1902 can be understood as: the mobility management device receives information about the network slice that the terminal requests to access through the first access network device in the first network.

[0498] In some embodiments, the mobility management device may determine the network slices supported by the TA of the first access network device. The network slices supported by the TA of the first access network device may be reported to the mobility management device by the first access network device when establishing or updating an N2 connection with the mobility management device. This application is illustrated by taking the example of the mobility management device determining that the first TA of the first access network device does not support the first network slice but supports the second network slice.

[0499] S1903: The mobile management device selects a slice.

[0500] For example, the mobile management device can perform slice selection by interacting with the network slice selection function network element.

[0501] Among them, in step S1903, the mobility management device can determine the network slice that the terminal is allowed to access, specifically, it can determine the network slice that the terminal is allowed to access in the first TA. This application is explained by taking the example that the network slice that the terminal is allowed to access includes the second network slice, and the first network slice does not belong to the network slice that the terminal is allowed to access.

[0502] As described above, a network slice that is not allowed to be accessed by the terminal may be referred to as a target network slice, and there may be one or more target network slices. For example, the network slice to which the terminal requests access also includes a third network slice, and the third network slice is a network slice allowed to be accessed within the second network. Thus, within the first TA of the first network, the third network slice does not belong to the network slice to which the terminal is allowed to access. In this scenario, the target network slice includes the first network slice and the third network slice. Alternatively, the target network slice may be a network slice to which the terminal is denied access, for example, the target network slice includes the above-mentioned first network slice.

[0503] In some embodiments, the mobile management device can save the information of the target network slice. When the mobile management device serving the terminal is subsequently switched, the information of the target network slice can be sent to the switched mobile management device.

[0504] In some embodiments, in step S1903, the mobility management device may further determine a network slice to which the terminal is denied access. Specifically, the network slice to which the terminal is denied access in the first TA may be determined. This application is described by taking the example that the network slice to which the terminal is denied access includes the first network slice. Furthermore, the network slice to which the terminal is denied access may further include a third network slice.

[0505] In some embodiments, in step S1903, the mobility management device may further determine a network slice within the first network that the terminal is allowed to access. This application is described by taking as an example that the network slice within the first network that the terminal is allowed to access includes the first network slice, or in other words, the first network slice is a network slice within the first network that the terminal is allowed to access. Further, the description is given by taking as an example that the second TA in the first network supports the first network slice.

[0506] That is to say, the first network slice is a network slice that allows terminal access within the first network, but is not a network slice that allows terminal access within the first TA.

[0507] In some embodiments, in step S1903, the mobility management device may further determine the network slices that the terminal is allowed to access under the contract. This application uses the example of the network slices that the terminal is allowed to access under the contract including: a first network slice, a second network slice, a third network slice, and a fourth network slice. The fourth network slice is also the network slice that the terminal is allowed to access under the first network.

[0508] S1904: The mobility management device determines the registration area.

[0509] The characteristics of the registration area can refer to the above Figure 11 or Figure 12 or Figure 13 The description of the method shown will not be repeated here.

[0510] In some embodiments, the mobile management device may determine the registration area based on the network slices that the terminal is allowed to access and the network slices that the terminal is denied access to. Alternatively, the terminal device may further determine the registration area based on one or more of the support capabilities of the access network device managed by the mobile management device for network slices, the network slices that the terminal is allowed to access within the first network, and the network slices that the terminal is allowed to access under contract. Alternatively, it can also be understood that the mobile management device may determine the registration area based on the network slices that the terminal is allowed to access and the target network slice. This application does not specifically limit the method for the mobile management device to determine the registration area.

[0511] S1905: The mobility management network element sends a second message to the first access network device. Correspondingly, the first access network device receives the second message from the mobility management network element.

[0512] The second message includes information about the registration area. Furthermore, the second message also includes information about the network slice that the terminal is allowed to access.

[0513] In some embodiments, the second message may be an N2 message.

[0514] S1906: The first access network device sends the registration area information to the terminal. Correspondingly, the terminal receives the registration area information from the first access network device.

[0515] In some embodiments, the first access network device also sends the above-mentioned information about the network slice that allows the terminal to access to the terminal.

[0516] S1907. Other registration procedures.

[0517] Among them, after step S1907, the registration process is completed and the terminal accesses the second network slice.

[0518] S1908. The terminal switches to the second access network device due to mobility.

[0519] Taking the TA of the second access network device including the second TA as an example, as described in step S1903, the second TA supports the first network slice. Figure 8a In the scenario, the second TA is Figure 8a TA2 in Figure 8b In the scenario, the first TA is Figure 8b Since the registration area excludes the tracking areas supporting the first network slice and the second network slice, or excludes the tracking areas of the access network devices supporting the first network slice and the second network slice, the second TA is outside the registration area. In this case, the terminal may execute step S1909 because it moves out of the RA.

[0520] S1909. Re-execute the registration process.

[0521] In some embodiments, the re-registration process is initiated by the terminal. In the re-initiated registration process, the network slice that the terminal requests to access may include the first network slice. Of course, the network slice that the terminal requests to access may also not include the first network slice. For example, after switching to the second access network device, the terminal no longer needs to access the first network slice. This application does not specifically limit this.

[0522] Based on this solution, when determining the registration area, the mobile management device excludes the tracking area of ​​the network slice and target network slice that support terminal access, or excludes the tracking area of ​​the access network device that supports the network slice and target network slice that support terminal access. Therefore, when the terminal moves within the excluded tracking area, since the registration area of ​​the terminal does not include the tracking area and the tracking area supports the target network slice, the terminal can re-initiate the registration process and request access to the target network slice, thereby improving the success rate of access to the target network slice.

[0523] See also Figure 20 and Figure 21 , in the case where a network device provided by this application is a mobile management device, Figure 14 The method shown is applied to a specific process flow chart. Figure 20 or Figure 21 The method shown can be applied to Figure 8b or Figure 8c The method includes the following steps:

[0524] S2001: A terminal sends a first message to a first access network device. Correspondingly, the first access network device receives the first message from the terminal.

[0525] The terminal sends the first message to the first access network device through the first cell of the first access network device. That is, the terminal accesses the network in the first cell. The first cell is a cell in the first TA of the first access network device.

[0526] The first message includes a registration request (Registration Request), which includes information about the network slice that the terminal requests to access (e.g., Requested NSSAI), and the information about the network slice that the terminal requests to access includes identification information of the first network slice. That is, the first network slice is included in the network slice that the terminal requests to access in the first cell. Furthermore, the information about the network slice that the terminal requests to access may also include identification information of the second network slice.

[0527] In some embodiments, the first access network device may be an access network device within the first network. The first network may refer to the aforementioned related descriptions and will not be repeated here.

[0528] S2002: The first access network device sends a registration request to the mobility management device. Correspondingly, the mobility management device receives the registration request from the first access network device.

[0529] The registration request is received by the first access network device from the terminal in step S2001. Thus, steps S2001 and S2002 can be understood as: the mobility management device receives information about the network slice that the terminal requests to access through the first cell.

[0530] S2003. The mobile management device performs slice selection.

[0531] For example, the mobile management device can perform slice selection by interacting with the network slice selection function network element.

[0532] Among them, in step S2003, the mobility management device can determine the network slice that the terminal is allowed to access, specifically, it can determine the network slice that the terminal is allowed to access in the first cell. This application is explained by taking the example that the network slice that the terminal is allowed to access in the first cell includes the second network slice.

[0533] In some embodiments, after the mobile management device determines that the terminal is allowed to access the network slice in the first cell, the mobile management device can determine whether the first network slice belongs to the network slice that the terminal is allowed to access in the first cell. This application uses the example that the mobile management device can know that the first network slice does not belong to the network slice that the terminal is allowed to access in the first cell.

[0534] At this point, the mobile management device can determine the first network slice, and thus, S2001 to S2003 can be understood as the specific implementation of the mobile management device determining the first network slice.

[0535] As described above, the network slice that the terminal is not allowed to access in the first cell can be called a target network slice, and there can be one or more target network slices. For example, the network slice that the terminal requests to access in the first cell also includes a third network slice, and the third network slice is a network slice allowed to access in the second network. Therefore, in the first cell of the first network, the third network slice does not belong to the network slice that the terminal is allowed to access. Alternatively, the target network slice can be a network slice that the terminal is denied access to, for example, the target network slice includes the above-mentioned first network slice.

[0536] In some embodiments, in step S2003, the mobile management device may also determine the network slice configured by the terminal in the first network. This application takes the example that the network slice configured by the terminal in the first network includes the first network slice, or that the first network slice is included in the network slice configured by the terminal in the first network.

[0537] The mobility management device also determines a registration area of ​​the terminal. This application uses an example in which the terminal's registration area includes a first cell and a second cell. The second cell may belong to the first access network device, i.e., the first cell and the second cell belong to the same access network device; or the second cell may belong to a second access network device, i.e., the first cell and the second cell belong to different access network devices.

[0538] S2004. The mobile management device saves the identification information of the target network slice, which includes the first network slice.

[0539] In some embodiments, when the mobility management device serving the terminal is subsequently switched, the identification information of the target network slice may be sent to the mobility management device after the switch. In the case where the mobility management device serving the terminal is switched, the mobility management network element after step S2004 may be considered to be the mobility management network element after the switch.

[0540] S2005: The mobility management network element sends a second message to the first access network device. Correspondingly, the first access network device receives the second message from the mobility management network element.

[0541] The second message includes the information of the network slice that the terminal is allowed to access.

[0542] In some embodiments, the second message may be an N2 message.

[0543] It should be noted that there is no necessary order between step S2005 and step S2004. Step S2004 can be executed first, and then step S2005; or, step S2005 can be executed first, and then step S2004; or, step S2004 and step S2005 can be executed at the same time. This application does not make any specific restrictions on this.

[0544] S2006. The first access network device sends information about the network slice that the terminal is allowed to access to the terminal. Correspondingly, the terminal receives information about the network slice that the terminal is allowed to access from the first access network device.

[0545] S2007. Other registration procedures.

[0546] Among them, after step S2007, the registration process is completed and the terminal accesses the second network slice.

[0547] S2008. Execute handover, and the terminal switches from the first cell to the second cell.

[0548] The second cell is a cell in the second TA.

[0549] In some embodiments, when the second cell belongs to a second access network device and the switching type is Xn switching, after step S2008, the switching of the terminal in the access network is completed, and the following step S2009a is continued to be executed.

[0550] In some embodiments, when the second cell belongs to the second access network device and the switching type is N2 switching, after step S2008, the first access network device decides to trigger N2 switching and continues to execute the following step S2009b.

[0551] It can be understood that, when the second cell belongs to the first access network device, the following steps S2009a and S2009b are not performed.

[0552] S2009a: The second access network device sends a path switch request (Path Switch Requested) message to the mobility management device. Correspondingly, the mobility management device receives the path switch request message from the second access network device.

[0553] After receiving the path switching request message from the second access network device, the mobility management device may execute the following step S2011.

[0554] S2009b: The first access network device sends a handover required message to the mobility management device. In response, the mobility management device receives the handover required message from the first access network device.

[0555] The switching requirement message includes the identifier of the second access network device, so that the mobility management device can learn the second access network device after switching.

[0556] After receiving the handover request message from the first access network device, the mobility management device may execute the following step S2011.

[0557] S2010: Remaining switching process.

[0558] For details, please refer to Figure 5 or Figure 6 The method flow shown, or the switching flow defined in the reference protocol, will not be repeated here.

[0559] It should be noted that S2010 can be executed in parallel with the following steps S2011 to S2014. Of course, they can also be executed in other orders. This application has specific limitations on this step.

[0560] S2011. The mobility management network element determines the target network slice available in the second cell.

[0561] It can be understood that in step S2011, the target network slice available in the second cell may be a subset of the target network slice in step S2004. For example, the target network slice in step S2004 includes the first network slice and the third network slice, and the target network slice available in the second cell in step S2011 is the first network slice, that is, this application takes the example of the mobility management network element determining that the first network slice is available in the second cell, or in other words, determining that the target network slices available in the second cell include the first network slice.

[0562] That is to say, when the second cell belongs to the second access network device and the switching type is Xn switching, the mobile management device determines that the first network slice is available in the second cell, which may include: when the mobile management network element receives a path switching request message from the second access network device, determining that the first network slice is available in the second cell.

[0563] When the second cell belongs to the second access network device and the switching type is N2 switching, the mobility management network element determines that the first network slice is available in the second cell, which may include: when the mobility management network element receives a switching request message from the first access network device, determining that the first network slice is available in the second cell.

[0564] In other words, when the second cell belongs to the second access network device, the path switching request message or the switching requirement message can serve as a trigger condition for the mobile management device to determine that the first network slice is available in the second cell.

[0565] In different embodiments of the present application, the manner in which the mobility management device determines the target network slice available in the second cell may also be different, for example:

[0566] In some embodiments, the mobile management device determines the target network slice available in the second cell, including: the mobile management device queries the context of the target access network device, and determines whether the network slices supported by the tracking area of ​​the target access network device include the target network slice.

[0567] In which, when the second cell belongs to the second access network device, the target access network device is the second access network device; when the second cell belongs to the first access network device, the target access network device is the first access network device.

[0568] In this application, the context of the target access network device indicates that the network slices supported by the tracking area of ​​the target access network device include the first network slice, or in other words, the context of the target access network device indicates that the tracking area of ​​the target access network device supports the first network slice. In this scenario, the second cell is a cell in the tracking area of ​​the target access network device. Exemplarily, the second cell is a cell in the second TA of the target access network device.

[0569] In other embodiments, see Figure 21 Taking the target access network device as the second access network device as an example, the mobility management device determines the target network slice available for the second cell, including:

[0570] S2011a. The mobility management device sends identification information of the target network slice supported by the tracking area of ​​the target access network device to the target access network device. Correspondingly, the target access network device receives identification information of the target network slice supported by the tracking area of ​​the target access network device from the mobility management device.

[0571] In which, assuming that the target network slice in step S2004 includes the first network slice and the third network slice, this application takes the tracking area of ​​the target access network device that supports the first network slice but does not support the third network slice, and the identification information of the first network slice sent by the mobile management device in step S2011a is used as an example for explanation.

[0572] S2011b. The target access network device determines whether the terminal can access the first network slice in the second cell based on the measurement report reported by the terminal.

[0573] In some embodiments, the target access network device first determines whether the second TA in which the second cell is located supports the first network slice. This application uses the example of the second TA supporting the first network slice as an example. Thereafter, the target access network device may determine whether the terminal can access the first network slice in the second cell based on the cell signal quality in the measurement report.

[0574] As an example, the cell signal quality can be measured by one or more of received signal code power (RSCP), reference signal receiving power (RSRP), reference signal receiving quality (RSRQ), signal-to-noise ratio (SNR), signal to interference plus noise ratio (SINR), and reference signal strength indication (RSSI). This application does not specifically limit this.

[0575] As an example, when the cell signal quality corresponding to the second cell is greater than the first threshold, the target access network device determines that the terminal can access the first network slice in the second cell.

[0576] As an example, the target access network device may execute step S2011b immediately after S2011a; or, may execute step S2011b at any time after S2011a, thereby executing step S2011c after executing step S2011b at any time.

[0577] S2011c: The target access network device sends notification information to the mobility management device. Correspondingly, the mobility management device receives the notification information from the target access network device.

[0578] The notification information is used to notify the terminal that it can access the first network slice in the second cell. Thus, the mobility management device learns from the target access network device that the terminal can access the first network slice in the second cell.

[0579] As an example, in step S2011a, when the target network slices supported by the tracking area of ​​the target access network device only include the first network slice, the notification information can be 1-bit information. For example, when the value of the bit is "1", the terminal is notified that it can access the first network slice in the second cell, or when the value of the bit is "0", the terminal is notified that it can access the first network slice in the second cell.

[0580] As another example, in step S2011a, when the target network slice supported by the tracking area of ​​the target access network device includes multiple network slices, the notification information may include identification information of the first network slice.

[0581] As another example, in the case where the target network slices supported by the tracking area of ​​the target access network device in step S2011a include multiple network slices, the notification information may include a bit map, the number of bits included in the bit map is equal to the number of target network slices supported by the tracking area of ​​the target access network device, different bits correspond to different target network slices, and the terminal is notified whether it can access the corresponding target network slice in the second cell through the value of the bit.

[0582] Exemplarily, in step S2011a, the target network slices supported by the tracking area of ​​the target access network device include network slice 1 and network slice 2. The target access network device determines that the terminal can access network slice 1 but cannot access network slice 2 in the second cell. Then, the bitmap may include two bits, the first bit corresponding to network slice 1, and the second bit corresponding to network slice 2. For example, the bitmap may be "10", notifying the terminal that it can access network slice 1 but cannot access network slice 2 in the second cell.

[0583] It is understandable that steps S2011a to S2011c may also be applicable to a scenario where the target access network device is the first access network device.

[0584] That is, the mobile management device determines that the first network slice is available in the second cell, including: the mobile management device sends the identification information of the first network slice to the target access network device, and learns from the target access network device that the terminal can access the first network slice in the second cell.

[0585] Based on this solution, after determining the first network slice supported by the tracking area of ​​the target access network device, the mobile management device further confirms with the target access network device whether the terminal can access the first network slice supported by the tracking area of ​​the target access network device. This avoids the situation where the target access network device supports the first network slice, but the terminal cannot access the first network slice in the second cell. The mobile management device notifies the terminal that the first network slice is available in the second cell, which can improve the success rate of the terminal accessing the first network slice in the second cell.

[0586] S2012. The mobile management device notifies the terminal that the first network slice is available in the second cell.

[0587] In some embodiments, the mobility management device may send a NAS message to the terminal, notifying the terminal through the NAS message that the first network slice is available in the second cell. The notification method can refer to the above step S2011c and will not be repeated here.

[0588] Optionally, after step S2012, the network slicing-based communication method may further include the following steps S2013 and S2014:

[0589] S2013: The terminal sends instruction information to the mobility management device. Correspondingly, the mobility management device receives the instruction information from the terminal, or in other words, the mobility management device receives the instruction information from the terminal.

[0590] In some embodiments, the indication information is used to indicate that the terminal no longer requests access to the first network slice.

[0591] S2014. The mobile management device deletes the identification information of the first network slice according to the instruction information.

[0592] In some embodiments, the indication information is used to indicate that when the terminal no longer requests access to the first network slice, the mobile management device deletes the identification information of the first network slice. When the mobile management device subsequently serves the terminal, it may no longer notify the terminal of the cell that can access the first network slice, thereby reducing signaling overhead and reducing resource waste.

[0593] Based on this solution, when the terminal switches from the first cell to the second cell, the mobile management device determines that the first network slice is available in the second cell, and notifies the terminal that the first network slice is available in the second cell. Therefore, if the terminal still wants to access the first network slice, it can initiate a registration process to request access to the first network slice, thereby improving the success rate of accessing the first network slice and using the services provided by the first network slice.

[0594] See also Figure 22 , a second cell provided by the present application belongs to a first access network device, and the network device is the first access network device. Figure 14 The method shown is applied to a specific process flow chart. Figure 22 The method shown can be applied to Figure 8c The method includes the following steps:

[0595] S2201 to S2207, same Figure 20 The steps S2001 to S2007 may refer to the above related descriptions and will not be repeated here.

[0596] S2208: Execute handover, and the terminal switches from the first cell to the second cell.

[0597] The second cell is a cell in the second TA, and the second cell belongs to the first access network device. After S2208 is completed, it can be considered that the terminal has completed the handover from the first cell to the second cell.

[0598] S2209. The mobility management device sends the identification information of the target network slice saved in step S2204 to the first access network device. Correspondingly, the first access network device receives the identification information of the target network slice from the mobility management device.

[0599] Taking the target network slice saved in S2204 as an example, including the first network slice and the third network slice, in S2209, the mobile management device sends the identification information of the first network slice and the identification information of the third network slice to the first access network device.

[0600] It should be noted that there is no necessary order between step S2209 and step S2208. Step S2208 can be executed first, and then step S2209; or, step S2209 can be executed first, and then step S2208; or, step S2208 and step S2209 can be executed at the same time. This application does not make any specific restrictions on this.

[0601] For example, in the case where step S2209 is performed first and then step S2208 is performed, in step S2209, the first access network device may determine the first network slice. In combination with the above steps S2201 to S2209, the first access network device determines the first network slice, including: the first access network device sends information about the network slice that the terminal requests to access to the mobility management network element, the information about the network slice that the terminal requests to access includes identification information of the first network slice, and then the first access network device learns from the mobility management device that the first network slice does not belong to the network slices that the terminal is allowed to access in the first cell. In other words, the first access network device may learn from the mobility management device in the above registration process that the first network slice does not belong to the network slices that the terminal is allowed to access in the first cell.

[0602] It can be understood that the characteristics of the first network slice and / or the operations performed on it are also applicable to the third network slice. Please refer to the relevant instructions of the first network slice and will not be repeated here.

[0603] S2210. The first access network device determines the target network slice supported by the tracking area of ​​the first access network device.

[0604] In some embodiments, the first access network device can determine the target network slice supported by its tracking area based on the network slice support capability recorded by the first access network device.

[0605] As an example, in the case where the target network slice in step S2209 includes the first network slice and the third network slice, assuming that the tracking area of ​​the first access network device supports the first network slice but does not support the third network slice, then the target network slice supported by the tracking area of ​​the first access network device determined by the first access network device in step S2210 is the first network slice.

[0606] S2211. The first access network device determines that the first network slice is available in the second cell.

[0607] In some embodiments, the first access network device determining that the first network slice is available in the second cell includes: the first access network device determining that the terminal can access the first network slice in the second cell. The method for the first access network device to determine that the terminal can access the first network slice in the second cell can be referred to the relevant description in step S2011b above and is not repeated here.

[0608] S2212. The first access network device notifies the terminal that the first network slice is available in the second cell.

[0609] In some embodiments, the first access network device notifies the terminal that the first network slice is available in the second cell, including: the first access network device notifies the terminal, through the mobility management device, that the first network slice is available in the second cell. Exemplarily, step S2212 may include S2212a and S2212b:

[0610] S2212a: The first access network device sends notification information to the mobility management device. Correspondingly, the mobility management device receives the notification information from the target access network device.

[0611] Among them, step S2212a can refer to the relevant instructions in the above step S2011c, which will not be repeated here.

[0612] S2212b. The mobile management device notifies the terminal that the first network slice is available in the second cell.

[0613] Among them, step S2212b can refer to the relevant instructions in the above step S2012 and will not be repeated here.

[0614] In other embodiments, the first access network device may notify the terminal through an RRC message that the first network slice is available in the second cell.

[0615] Optionally, after step S2212, the network slicing-based communication method may further include steps S2213 and S2214. Steps S2213 and S2214 are the same as the above-mentioned steps S2013 and S2014, and the relevant descriptions of steps S2013 and S2014 may be referred to, which will not be repeated here.

[0616] Among them, the use of Figure 22 According to the method, the first access network device determines that the first network slice is available in the second cell, and notifies the terminal that the first network slice is available in the second cell. Figure 22 The technical effects of the method shown can be referred to above Figure 20 The technical effects brought about by the method shown are not described in detail here.

[0617] See also Figure 23, a second cell provided by the present application belongs to a second access network device, and the network device is the second access network device. Figure 14 The method shown is applied to a specific process flow chart. Figure 22 The method shown can be applied to Figure 8b The method includes the following steps:

[0618] S2301 to S2310, and Figure 20 The steps S2001 to S2010 are the same as shown, and can be referred to Figure 20 The relevant description will not be repeated here.

[0619] S2311. The mobility management device sends the identification information of the target network slice saved in step S2304 to the second access network device. Correspondingly, the second access network device receives the identification information of the target network slice from the mobility management device.

[0620] Among them, the way in which the mobility management device sends the identification information of the target network slice to the second access network device is the same as Figure 22 The manner in which the mobile management device sends the identification information of the target network slice to the first access network device in step S2209 is similar, and the relevant description in the above step S2209 may be referred to and will not be repeated here. Figure 22 The difference is that in the inter-station switching scenario, the mobile management device can send the identification information of the target network slice to the second access network device after receiving the path switching request message or the switching requirement message.

[0621] S2312. The second access network device determines the target network slice supported by the tracking area of ​​the second access network device.

[0622] In some embodiments, the second access network device can determine the target network slice supported by its tracking area based on the network slice support capability locally recorded by the second access network device.

[0623] As an example, in the case where the target network slice in step S2311 includes the first network slice and the third network slice, assuming that the tracking area of ​​the second access network device supports the first network slice but does not support the third network slice, then the target network slice supported by the tracking area of ​​the second access network device determined by the second access network device in step S2312 is the first network slice.

[0624] S2313. The second access network device determines that the first network slice is available in the second cell.

[0625] In some embodiments, the second access network device determining that the first network slice is available in the second cell includes: the second access network device determining that the terminal can access the first network slice in the second cell. The method for the second access network device to determine that the terminal can access the first network slice in the second cell can be referred to the relevant description in step S2011b above and is not repeated here.

[0626] S2314. The second access network device notifies the terminal that the first network slice is available in the second cell.

[0627] The second access network device notifies the terminal that the first network slice is available in the second cell in a manner similar to Figure 22 The manner in which the first access network device notifies the terminal that the first network slice is available in the second cell in step S2212 is similar. Please refer to the relevant instructions in the above step S2212 and will not be repeated here.

[0628] Optionally, after step S2314, the network slicing-based communication method may further include steps S2315 and S2316. Steps S2315 and S2316 are the same as steps S2013 and S2014 above, and the relevant descriptions of steps S2013 and S2014 may be referred to, and will not be repeated here.

[0629] Among them, the use of Figure 23 According to the method, the second access network device determines that the first network slice is available in the second cell, and notifies the terminal that the first network slice is available in the second cell. Figure 23 The technical effects of the method shown can be referred to above Figure 20 The technical effects brought about by the method shown are not described in detail here.

[0630] See also Figure 24 , when a network device provided by itself is a mobile management device, Figure 15 Flowchart of the method applied to a specific process. Figure 24 The method shown can be applied to Figure 8a The method includes the following steps:

[0631] S2401 to S2407, and Figure 20 Steps S2001 to S2007 are the same as those shown. Please refer to the relevant descriptions of steps S2001 to S2007 and will not be repeated here.

[0632] S2408. Execute handover, and the terminal switches from the first cell to the second cell.

[0633] The second cell is a cell in the second TA. A third cell physically coexists with the second cell under the access network device to which the second cell belongs, and the third cell is a cell in the third TA.

[0634] In some embodiments, when the second cell belongs to the second access network device and the switching type is Xn switching, after step S2408, the terminal is switched in the access network and the following step S2409a is executed.

[0635] In some embodiments, when the second cell belongs to the second access network device and the switching type is N2 switching, after step S2408, the first access network device decides to trigger N2 switching and continues to execute the following step S2409b.

[0636] It can be understood that, when the second cell belongs to the first access network device, the following steps S2409a and S2409b are not performed.

[0637] S2409a、with Figure 20 The step S2009a is similar to the above, and the relevant description of step S2009a may be referred to, which will not be repeated here. After the mobility management device receives the path switching request from the second access network device, it executes the following step S2411.

[0638] S2409b, and Figure 20 The step S2009b is similar to the step S2009b, and the relevant description of the step S2009b may be referred to, which will not be repeated here. After the mobility management device receives the handover request from the first access network device, it executes the following step S2411.

[0639] S2410, and Figure 20 The step S2010 shown is the same as that shown in FIG. 1 , and the relevant description of step S2010 may be referred to, which will not be repeated here.

[0640] S2411. The mobility management network element determines a target network slice available in the third cell.

[0641] Among them, the description of the target network slice available in the third cell can refer to the description of the target network slice available in the second cell in the above step S2011, and will not be repeated here.

[0642] In different embodiments of the present application, the manner in which the mobility management device determines the target network slice available in the third cell may also be different, for example:

[0643] In some embodiments, the mobile management device determines the target network slice available in the third cell, including: the mobile management device queries the context of the target access network device, and determines whether the network slices supported by the tracking area of ​​the target access network device include the target network slice.

[0644] In which, when the second cell belongs to the second access network device, the target access network device is the second access network device; when the second cell belongs to the first access network device, the target access network device is the first access network device.

[0645] In this application, the context of the target access network device indicates that the tracking area where the third cell is located (i.e., the third TA) supports the first network slice, and the tracking area where the second cell is located (i.e., the second TA) does not support the first network slice. The second TA and the third TA are the TAs of the target access network device, and the second cell and the third cell are the cells of the target access network device.

[0646] In some other embodiments, the mobility management device determines the target network slice available to the third cell, including:

[0647] S2411a. The mobility management device sends identification information of the target network slice supported by the tracking area of ​​the target access network device to the target access network device. Correspondingly, the target access network device receives identification information of the target network slice supported by the tracking area of ​​the target access network device from the mobility management device.

[0648] Here, please refer to the relevant instructions in the above step S2011a, which will not be repeated here.

[0649] S2411b. The target access network device determines whether the terminal can access the first network slice in the third cell based on the measurement report reported by the terminal.

[0650] In some embodiments, the target access network device first determines whether the third TA in which the third cell is located supports the first network slice. This application uses the third TA supporting the first network slice as an example for description. Thereafter, the target access network device may determine whether the terminal can access the first network slice in the third cell based on the cell signal quality in the measurement report. For details, please refer to step S2011b and will not be repeated here.

[0651] S2411c: The target access network device sends notification information to the mobility management device. Correspondingly, the mobility management device receives the notification information from the target access network device.

[0652] Among them, the notification information is used to notify the terminal that it can access the first network slice in the third cell. The notification method can refer to the above step S2011c and will not be repeated here.

[0653] That is to say, the mobile management device determines that the first network slice is available in the third cell, including: the mobile management device sends the identification information of the first network slice to the target access network device, and learns from the target access network device that the terminal can access the first network slice in the third cell.

[0654] S2412. The mobile management device notifies the terminal that the first network slice is available in the third cell.

[0655] In some embodiments, the mobility management device may send a NAS message to the terminal, notifying the terminal through the NAS message that the first network slice is available in the third cell. The notification method can refer to the above step S2012 and will not be repeated here.

[0656] In some embodiments, after the mobility management device notifies the terminal that the first network slice is available in the third cell, the terminal learns that the first network slice is available in the third cell. In this scenario, the terminal can reselect the cell on its own to access the third cell and access the first network slice through the third cell; or, the terminal can initiate a registration request in the second cell to request access to the first network slice. After that, the target access network redirects the terminal to the third cell through an RRC connection release message, so that the terminal accesses the first network slice through the third cell. Please refer to the above Figure 5 The process shown will not be repeated here.

[0657] Optionally, after step S2412, the network slicing-based communication method may further include steps S2413 and S2414. Steps S2413 and S2414 are the same as the above steps S2013 and S2014. Please refer to the above related instructions and will not be repeated here.

[0658] Based on this solution, when the terminal switches from the first cell to the second cell, and the mobile management device determines that the first network slice is available in the third cell, it notifies the terminal that the first network slice is available in the third cell. Therefore, if the terminal still wants to access the first network slice, it can access the first network slice in the third cell, thereby improving the success rate of accessing the first network slice and using the services provided by the first network slice.

[0659] See also Figure 25 , a second cell provided by the present application belongs to a first access network device, and the network device is the first access network device. Figure 15 The method shown is applied to a specific process flow diagram, the method comprising the following steps:

[0660] S2501 to S2507, and Figure 22 Steps S2201 to S2207 shown are the same, and reference may be made to the relevant descriptions of the above steps S2201 to S2207, which will not be repeated here.

[0661] S2508. Execute handover, and the terminal switches from the first cell to the second cell.

[0662] The second cell is a cell in the second TA. A third cell physically co-exists with the second cell under the first access network device to which the second cell belongs, and the third cell is a cell in the third TA.

[0663] After S2508 is completed, it can be considered that the terminal has completed the handover from the first cell to the second cell.

[0664] S2509. The mobility management device sends the identification information of the target network slice saved in step S2504 to the first access network device. Correspondingly, the first access network device receives the identification information of the target network slice from the mobility management device.

[0665] Here, please refer to the relevant description in the above step S2209, which will not be repeated here.

[0666] S2510. The first access network device determines the target network slice supported by the tracking area of ​​the first access network device.

[0667] Here, please refer to the relevant description in the above step S2210, which will not be repeated here.

[0668] S2511. The first access network device determines that the first network slice is available in the third cell.

[0669] In some embodiments, the first access network device determining that the first network slice is available in the third cell includes: the first access network device determining that the terminal can access the first network slice in the third cell. The method for the first access network device to determine that the terminal can access the first network slice in the third cell can be referred to the relevant description in step S2411b above and is not repeated here.

[0670] S2512. The first access network device notifies the terminal that the first network slice is available in the third cell.

[0671] Among them, the notification method can refer to the above step S2212, where the first access network device notifies the terminal that the first network slice is available in the second cell, and will not be repeated here.

[0672] In some embodiments, after the first access network device notifies the terminal that the first network slice is available in the third cell, the terminal learns that the first network slice is available in the third cell. In this scenario, the terminal can reselect the cell on its own to access the third cell and access the first network slice through the third cell; or, the terminal can initiate a registration request in the second cell to request access to the first network slice. After that, the target access network redirects the terminal to the third cell through an RRC connection release message, so that the terminal accesses the first network slice through the third cell. Please refer to the above Figure 5 The process shown will not be repeated here.

[0673] Optionally, after step S2512, the network slicing-based communication method may further include steps S2513 and S2514. Steps S2513 and S2514 are the same as the above-mentioned steps S2013 and S2014, and the relevant descriptions of steps S2013 and S2014 may be referred to, which will not be repeated here.

[0674] Among them, the use of Figure 25 According to the method, the first access network device determines that the first network slice is available in the third cell, and notifies the terminal that the first network slice is available in the third cell. Figure 25 The technical effects of the method shown can be referred to above Figure 24 The technical effects brought about by the method shown are not described in detail here.

[0675] See also Figure 26 , a second cell provided by the present application belongs to a second access network device, and the network device is the second access network device. Figure 15 The method shown is applied to a specific process flow chart. Figure 26 The method shown can be applied to Figure 8a The method includes the following steps:

[0676] S2601 to S2607, and Figure 20 Steps S2001 to S2007 are the same as those shown. Please refer to the relevant descriptions of the above steps S2001 to S2007 and will not be repeated here.

[0677] S2608: Execute handover, and the terminal switches from the first cell to the second cell.

[0678] The second cell is a cell in the second TA. A third cell physically coexists with the second cell under the access network device to which the second cell belongs, and the third cell is a cell in the third TA.

[0679] In some embodiments, when the second cell belongs to the second access network device and the switching type is Xn switching, after step S2608, the terminal is switched in the access network and the following step S2609a is executed.

[0680] In some embodiments, when the second cell belongs to the second access network device and the switching type is N2 switching, after step S2608, the first access network device decides to trigger N2 switching and continues to execute the following step S2609b.

[0681] S2609a, and Figure 20The step S2009a is similar to the above, and the relevant description of step S2009a may be referred to, which will not be repeated here. After the mobility management device receives the path switching request from the second access network device, it executes the following step S2411.

[0682] S2609b, and Figure 20 The step S2009b is similar to the step S2009b, and the relevant description of the step S2009b may be referred to, which will not be repeated here. After the mobility management device receives the handover request from the first access network device, it executes the following step S2411.

[0683] S2610, and Figure 20 The step S2010 shown is the same as that shown in FIG. 1 , and the relevant description of step S2010 may be referred to, which will not be repeated here.

[0684] S2611. The mobility management device sends the identification information of the target network slice saved in step S2604 to the second access network device. Correspondingly, the second access network device receives the identification information of the target network slice from the mobility management device.

[0685] S2612. The second access network device determines the target network slice supported by the tracking area of ​​the second access network device.

[0686] For details, please refer to the relevant instructions in the above steps S2311 and S2312, which will not be repeated here.

[0687] S2613. The second access network device determines that the first network slice is available in the third cell.

[0688] In some embodiments, the second access network device determining that the first network slice is available in the third cell includes: the second access network device determining that the terminal can access the first network slice in the third cell. The method for the second access network device to determine that the terminal can access the first network slice in the third cell can be referred to the relevant description in step S2411b above and is not repeated here.

[0689] S2614. The second access network device notifies the terminal that the first network slice is available in the third cell.

[0690] Among them, the notification method can refer to the above step S2212, where the first access network device notifies the terminal that the first network slice is available in the second cell, and will not be repeated here.

[0691] In some embodiments, after the second access network device notifies the terminal that the first network slice is available in the third cell, the terminal learns that the first network slice is available in the third cell. In this scenario, the terminal can reselect the cell on its own to access the third cell and access the first network slice through the third cell; or, the terminal can initiate a registration request in the second cell to request access to the first network slice. After that, the target access network redirects the terminal to the third cell through an RRC connection release message, so that the terminal accesses the first network slice through the third cell. Please refer to the above Figure 5 The process shown will not be repeated here.

[0692] Optionally, after step S2614, the network slicing-based communication method may further include steps S2615 and S2616. Steps S2615 and S2616 are the same as steps S2013 and S2014 above, and the relevant descriptions of steps S2013 and S2014 may be referred to, which will not be repeated here.

[0693] Among them, the use of Figure 26 According to the method, the second access network device determines that the first network slice is available in the third cell, and notifies the terminal that the first network slice is available in the third cell. Figure 26 The technical effects of the method shown can be referred to above Figure 24 The technical effects brought about by the method shown are not described in detail here.

[0694] See also Figure 27 , in the case where a network device provided by this application is a mobile management device, Figure 16 A flow chart of a method for applying the method to a specific process, the method comprising the following steps:

[0695] S2701: A terminal sends a first message to a first access network device. Correspondingly, the first access network device receives the first message from the terminal.

[0696] The terminal sends the first message to the first access network device through the first cell of the first access network device. That is, the terminal accesses the network in the first cell. The first cell is a cell in the first TA of the first access network device.

[0697] The first message includes a registration request (Registration Request), which includes information about the network slice that the terminal requests to access (e.g., Requested NSSAI), and the information about the network slice that the terminal requests to access includes identification information of the first network slice. That is, the first network slice is included in the network slice that the terminal requests to access in the first cell. Furthermore, the information about the network slice that the terminal requests to access may also include identification information of the second network slice.

[0698] In some embodiments, the first access network device may be an access network device within the first network. The first network may refer to the aforementioned related descriptions and will not be repeated here.

[0699] S2702: The first access network device sends a registration request to the mobility management device. Correspondingly, the mobility management device receives the registration request from the first access network device.

[0700] The registration request is received by the first access network device from the terminal in step S2701. Thus, steps S2701 and S2702 can be understood as: the mobility management device receives information about the network slice that the terminal requests to access through the first cell.

[0701] S2703: The mobile management device selects a slice.

[0702] For example, the mobile management device can perform slice selection by interacting with the network slice selection function network element.

[0703] In step S2703, the mobile management device can determine the first network slice, which does not belong to the network slice that the terminal is allowed to access in the first cell. Therefore, S2701 to S2703 can be understood as the specific implementation of the mobile management device determining the first network slice.

[0704] In step S2703, the mobility management device also determines the registration area of ​​the terminal. This application uses an example in which the registration area of ​​the terminal includes a first cell and a second cell. The second cell is a neighboring cell of the first cell and may belong to the first access network device, that is, the first cell and the second cell belong to the same access network device; or it may belong to the second access network device, that is, the first cell and the second cell belong to different access network devices.

[0705] S2704. The mobile management device saves the identification information of the target network slice, which includes the first network slice.

[0706] Exemplarily, the present application is illustrated by taking the example that the saved target network slices include the first network slice and the third network slice, that is, the terminal requests access to the first network slice, the second network slice, and the third network slice in the first cell. The network slice allowed to be accessed by the terminal in the first cell is the second network slice, and the network slices that are not allowed to be accessed by the terminal include the first network slice and the third network slice.

[0707] In some embodiments, when the mobility management device serving the terminal is subsequently switched, the identification information of the target network slice may be sent to the mobile management device after the switch. In the case where the mobility management device serving the terminal is switched, the mobility management network element after step S2704 can be considered to be the mobility management network element after the switch.

[0708] S2705: The mobility management network element sends a second message to the first access network device. Correspondingly, the first access network device receives the second message from the mobility management network element.

[0709] The second message includes the information of the network slice that the terminal is allowed to access.

[0710] In some embodiments, the second message may be an N2 message.

[0711] It should be noted that there is no necessary order between step S2705 and step S2704. Step S2704 can be executed first, and then step S2705; or, step S2705 can be executed first, and then step S2704; or, step S2704 and step S2705 can be executed at the same time. This application does not make any specific restrictions on this.

[0712] S2706. The first access network device sends information about the network slice that the terminal is allowed to access to the terminal. Correspondingly, the terminal receives the information about the network slice that the terminal is allowed to access from the first access network device.

[0713] S2707. Other registration procedures.

[0714] Among them, after step S2007, the registration process is completed and the terminal accesses the second network slice.

[0715] S2708. The mobile management device determines that the first network slice is available in the second cell.

[0716] In different embodiments of the present application, the method in which the mobility management device determines that the first network slice is available in the second cell may be different. For example:

[0717] In some embodiments, the mobility management device determining that the first network slice is available in the second cell may include:

[0718] S27081a: The first access network device sends the cell identifier of the second cell to the mobility management device. Correspondingly, the mobility management device receives the cell identifier of the second cell from the first access network device.

[0719] As a possible implementation, since the second cell is a neighboring cell of the first cell, the terminal may measure the neighboring cell of the first cell and report a measurement report to the first access network device. The measurement report may include the neighboring cell identifier and neighboring cell quality of the first cell. After the first access network device receives the measurement report from the terminal, if the measurement report includes the cell identifier of the second cell, step S27081a may be performed.

[0720] As an example, the first access network device may determine the cell identifier of the second cell reported to the mobility management device by the following method:

[0721] Prior to step S27081a, the mobility management device may send reference frequency information corresponding to the first network slice to the first access network device. After receiving the measurement report reported by the terminal, the first access network device may determine the second cell based on the reference frequency information, thereby reporting the cell identifier of the second cell to the mobility management device. For example, the second cell is a cell at the frequency indicated by the reference frequency information; if there are multiple cells at the frequency indicated by the reference frequency information, the second cell may be a cell among the multiple cells whose signal quality is greater than the second threshold.

[0722] In addition, after the first access network device receives the reference frequency information corresponding to the first network slice, it can configure the frequency point indicated by the reference frequency information as a measurement object and send it to the terminal, so that the terminal can measure the frequency point.

[0723] S27082a. The mobile management device determines the network slices supported by the second TA.

[0724] The second TA is the TA where the second cell is located.

[0725] As a possible implementation method, the mobile management device can determine the network slices supported by the second TA through the network slice information reported by the first access network device when establishing or updating the N2 connection.

[0726] S27083a. When the network slices supported by the second TA include the first network slice, the mobile management device determines that the terminal can access the first network slice in the second cell.

[0727] In some embodiments, the mobility management device determining that the first network slice is available in the second cell may include:

[0728] S27081b: The first access network device sends signal quality information of neighboring cells of the first cell to the mobility management device. Correspondingly, the mobility management device receives signal quality information of neighboring cells of the first cell from the first access network device.

[0729] The neighboring cell of the first cell includes the second cell, that is, the quality information of the neighboring cell includes the signal quality information of the second cell.

[0730] As a possible implementation manner, the first access network device sends to the mobility management device the signal quality information of all neighboring cells of the first cell reported by the terminal.

[0731] As another possible implementation, the signal quality information of the neighboring cell of the first cell sent by the first access network device to the mobility management device may be the signal quality of the cell at the frequency indicated by the reference frequency information corresponding to the first network slice. The reference frequency information corresponding to the first network slice may be the information sent by the mobility management device to the first access network device before step S27081b.

[0732] S27082b. The mobile management device determines, based on the signal quality information of the second cell, that the terminal can access the first network slice in the second cell.

[0733] As a possible implementation manner, the mobility management device may first determine whether the second TA where the second cell is located supports the first network slice. If the second TA supports the first network slice, it may further determine whether the cell signal quality indicated by the signal quality information of the second cell is greater than a second threshold. If the cell signal quality of the second cell is greater than the second threshold, it may be determined that the terminal can access the first network slice in the second cell.

[0734] Whether through the above steps S27081a to S27083a or through the above steps S27082a and S27082b, the mobile management device can determine that the first network slice is available in the second cell before the switching process occurs.

[0735] It can be understood that for the third network slice, the mobile management device can also determine whether it is available in the second cell. This application uses the example of the third network slice being unavailable in the second cell for illustration.

[0736] S2709. The network device notifies the terminal that the first network slice is available in the second cell.

[0737] Among them, the notification method can refer to the above step S2012, where the first access network device notifies the terminal that the first network slice is available in the second cell, and will not be repeated here.

[0738] S2710: The mobility management device sends a cell identifier of the second cell to the terminal. Correspondingly, the terminal receives the cell identifier of the second cell from the mobility management device.

[0739] In some embodiments, the cell identifier of the second cell can be used for the terminal to switch from the first cell to the second cell, thereby accessing the first network slice in the second cell.

[0740] In some embodiments, the cell identifier of the second cell and the information notifying the terminal that the first network slice is available in the second cell can be carried in one message; or, they can be carried in different messages, which is not specifically limited in this application.

[0741] Optionally, after step S2710, the network slicing-based communication method may further include steps S2711 and S2712. Steps S2711 and S2712 are the same as steps S2013 and S2014 above, and the relevant descriptions of steps S2013 and S2014 may be referred to, which will not be repeated here.

[0742] Based on the solution of the present application, when the mobile management device determines that the first network slice is available in the second cell, it notifies the terminal that the first network slice is available in the second cell and sends the cell identifier of the second cell. Therefore, if the terminal still wants to access the first network slice, it can access the second cell and initiate a registration process to request access to the first network slice, thereby improving the success rate of accessing the first network slice and using the services provided by the first network slice.

[0743] See also Figure 28 , in the case where a network device provided by this application is a mobile management device, Figure 17 A flow chart of a method for applying the method to a specific process, the method comprising the following steps:

[0744] S2801 to S2807, and Figure 27 Steps S2701 to S2707 shown are the same, and reference may be made to the relevant descriptions of the above steps S2701 to S2707, which will not be repeated here.

[0745] S2808. The mobile management device determines that the first network slice is available in the third cell.

[0746] The physical coverage of the third cell fully or partially overlaps with the physical coverage of the second cell.

[0747] In some embodiments, the third cell may be referred to as a cell physically co-covered with the second cell.

[0748] Among them, the method for the mobile management device to determine that the first network slice is available in the third cell can refer to the above step S2708, and the method for the mobile management device to determine that the first network slice is available in the second cell will not be repeated here.

[0749] It can be understood that when the first network slice is available in the third cell, the cells on the frequency indicated by the reference frequency information corresponding to the first network slice include the third cell, but not the second cell.

[0750] S2809. The network device notifies the terminal that the first network slice is available in the third cell.

[0751] Among them, the notification method can refer to the above step S2012, where the first access network device notifies the terminal that the first network slice is available in the second cell, and will not be repeated here.

[0752] S2810: The mobility management device sends a cell identifier of the third cell to the terminal. Correspondingly, the terminal receives the cell identifier of the third cell from the mobility management device.

[0753] In some embodiments, the cell identifier of the third cell can be used for the terminal to switch from the second cell to the third cell, thereby accessing the first network slice in the third cell.

[0754] Optionally, after step S2810, the network slicing-based communication method may further include steps S2811 and S2812. Steps S2811 and S2812 are the same as steps S2013 and S2014 above, and the relevant descriptions of steps S2013 and S2014 may be referred to, which will not be repeated here.

[0755] Based on this solution, when the neighboring area of ​​the first cell accessed by the terminal includes a second cell, and there is a third cell that has the same physical coverage as the second cell, the mobile management device determines that the first network slice is available in the third cell, notifies the terminal that the first network slice is available in the third cell, and sends the cell identifier of the third cell. Therefore, if the terminal still wants to access the first network slice, it can access the third cell and request access to the first network slice.

[0756] The above describes the application of the method of network equipment implementation in the specific process. Figure 18 The method implemented by the terminal shown in the figure is described in detail. The method can be applied to the process in which the above network device notifies the terminal that the first network slice can be in the second cell. That is, the method can be considered as Figures 20 to 23 ,or Figure 27 In the process, the network device notifies the terminal that the first network slice is available in the second cell, and then the terminal implements it.

[0757] See also Figure 29 and Figure 30 , a network slicing-based communication method for a terminal provided in this application, the method comprising:

[0758] S2901. The terminal learns from the network device that the first network slice is available in the second cell.

[0759] Among them, the first network slice in the first cell does not belong to the network slice that the terminal is allowed to access. The registration area of ​​the terminal includes the first cell and the second cell. Please refer to the above related description and will not repeat it here.

[0760] In some embodiments, see Figure 30 , step S2901 may be: the first entity of the terminal learns from the network device that the first network slice is available in the second cell.

[0761] As an example, the first entity may be a hardware structure of a terminal.

[0762] S2902. The terminal saves the identification information of the first network slice.

[0763] In some embodiments, see Figure 30 , step S2902 can be: the first entity of the terminal saves the identification information of the first network slice.

[0764] S2903: The application of the terminal initiates a data transmission request.

[0765] In some embodiments, see Figure 30 , step S2903 may be: the application of the terminal initiates a data transmission request to the first entity of the terminal.

[0766] S2904: The terminal queries the context of the terminal.

[0767] The context of the terminal includes the URSP and session information available to the terminal. If the context of the terminal does not include the URSP for the application and does not include the session for the application, it indicates that the network slice corresponding to the data transmission request does not belong to the network slice allowed to be accessed by the terminal in the first cell, and thus the following step S2905 is performed.

[0768] In some embodiments, see Figure 30 , step S2904 may be: the first entity of the terminal interacts with the second entity of the terminal to complete the query of the terminal context.

[0769] As an example, the second entity may be a component included in the terminal and used to save the terminal context.

[0770] S2905. The terminal determines whether the first network slice is the network slice corresponding to the application.

[0771] That is, in response to the fact that the context of the terminal does not include a session for the application and does not include a URSP for the application, the terminal determines whether the first network slice is the network slice corresponding to the application.

[0772] Among them, when the first network slice is the network slice corresponding to the application, the application is the application corresponding to the first network slice, and the terminal further executes the following step S2906a.

[0773] Alternatively, if the first network slice is not the network slice corresponding to the application, execute the following step S2906b.

[0774] In some embodiments, see Figure 30, the above step S2905 can be: the first entity of the terminal determines whether the first network slice is the network slice corresponding to the application.

[0775] S2906a. The terminal initiates a registration process for the application corresponding to the first network slice.

[0776] In some embodiments, see Figure 30 , step S2906a may be: the first entity of the terminal initiates a registration process for the application corresponding to the first network slice.

[0777] In some embodiments, for example, Figure 29 The implementation of the terminal shown is applied to Figure 27 In the scenario shown, the terminal also receives a cell identifier from the network device, where the cell identifier is for the second cell. In other words, the terminal also receives a cell identifier of the second cell from the network device.

[0778] In this scenario, the terminal initiates a registration process for the application corresponding to the first network slice, which may include: the terminal accesses the second cell and initiates a registration process for the application through the second cell.

[0779] In some embodiments, the terminal requests access to the first network slice in a registration process initiated by the application.

[0780] S2906b: The terminal rejects the data transmission request initiated by the application.

[0781] In some embodiments, see Figure 30 , step S2906b may be: the first entity of the terminal rejects the data transmission request initiated by the application.

[0782] Optionally, the network slicing-based communication method provided in this application further includes the following step S2907:

[0783] S2907: The terminal notifies the network device that the terminal no longer requests access to the first network slice. Accordingly, the network device learns from the terminal that the terminal no longer requests access to the first network slice.

[0784] In some embodiments, see Figure 30 , step S2907 may be: the first entity of the terminal notifies the network device that the terminal no longer requests access to the first network slice.

[0785] In some embodiments, the terminal may send indication information to the network device, where the indication information is used to indicate that the terminal no longer requests access to the first network slice.

[0786] In some embodiments, after receiving the indication information, the network device can delete the identification information of the first network slice it has stored according to the indication information. Please refer to the above-mentioned relevant instructions and will not repeat them here.

[0787] In some embodiments, after a first duration starting from a first moment, the terminal no longer requests access to the first network slice through the network device, where the first moment is the moment when the terminal learns from the network device that the first network slice is available in the second cell. In other words, if the first network slice available in the second cell has not been requested for use by an application of the terminal for a period of time, the terminal may notify the network device that the terminal no longer requests access to the first network slice.

[0788] Optionally, in some embodiments, when the terminal learns from the network device that the first network slice is switched after the second cell is available, and no new available network slice is learned from the network device after the switch, the terminal may delete the identification information of the first network slice it has saved.

[0789] Based on this solution, the terminal can learn from the network device that the first network slice is available in the second cell. Therefore, when the terminal's application corresponds to the first network slice, a registration process can be initiated for the application to request access to the first network slice, thereby improving the success rate of access to the first network slice.

[0790] It is understandable that when the terminal learns from the network device that the first network slice is available in the third cell, the implementation of the terminal is the same as Figure 29 or Figure 30 The method shown is similar, and the second cell can be replaced by the third cell for further understanding. Please refer to the above related instructions and will not be repeated here.

[0791] In the various embodiments of the present application, unless otherwise specified or there is a logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships.

[0792] It can be understood that in each of the above embodiments, the methods and / or steps implemented by each device can also be implemented by components (such as chips or circuits) that can be used in the device.

[0793] The above mainly introduces the solutions provided by this application from the perspective of interaction between various devices. Accordingly, this application also provides a communication device, which is used to implement the various methods described above. The communication device can be the network device in the above method embodiments, or a device that includes the above network device, or a component that can be used for a network device; alternatively, the communication device can be the terminal in the above method embodiments, or a device that includes the above terminal, or a component that can be used for a terminal.

[0794] It is understandable that, in order to realize the above functions, the communication device includes hardware structures and / or software modules corresponding to the execution of each function. It should be easily appreciated by those skilled in the art that, in combination with the units and algorithm steps of each example described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware 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.

[0795] The embodiment of the present application can divide the functional modules of the communication device according to the above method embodiment. For example, each functional module can be divided according to each function, or two or more functions can be integrated into one processing module. The above integrated modules can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of modules in the embodiment of the present application is schematic and is only a logical functional division. In actual implementation, there may be other division methods.

[0796] Taking the communication device as the network device in the above method embodiment as an example, Figure 31 FIG3 shows a schematic diagram of the structure of a network device 310. The network device 310 includes a processing module 3101 and a transceiver module 3102.

[0797] In some embodiments, the network device 310 may further include a storage module ( Figure 31 ), for storing program instructions and data.

[0798] In some embodiments, the transceiver module 3102, which may also be referred to as a transceiver unit, is configured to implement a transmitting and / or receiving function. The transceiver module 3102 may be composed of a transceiver circuit, a transceiver, a transceiver, or a communication interface.

[0799] In some embodiments, the transceiver module 3102 may include a receiving module and a sending module, which are respectively used to execute the receiving and sending steps performed by the network device in the above method embodiments, and / or used to support other processes of the technology described herein; the processing module 3101 may be used to execute the processing steps (such as determination, acquisition, etc.) performed by the network device in the above method embodiments, and / or used to support other processes of the technology described herein.

[0800] In some implementation scenarios:

[0801] The transceiver module 3102 is used to receive information about a network slice that the terminal requests to access through a first access network device in the first network. The information about the network slice that the terminal requests to access includes identification information of the first network slice that is not supported by the first tracking area, and includes identification information of the second network slice. The first tracking area is the tracking area of ​​the first access network device, and the second tracking area in the first network supports the first network slice. The processing module 3101 is used to determine the network slice that the terminal is allowed to access, wherein the network slice that the terminal is allowed to access includes the second network slice. The processing module 3101 is also used to determine a registration area, wherein the registration area excludes the tracking area that supports the first network slice and the second network slice, or the registration area excludes the tracking area of ​​the access network device that supports the first network slice and the second network slice. The transceiver module 3101 is also used to send information about the registration area to the terminal.

[0802] As a possible implementation method, the processing module 3101 is also used to determine the network slice to which the terminal is denied access, wherein the network slice to which the terminal is denied access includes the first network slice.

[0803] As a possible implementation method, the processing module 3101 is also used to determine the network slices supported by the tracking area of ​​the first access network device.

[0804] In some implementation scenarios:

[0805] The processing module 3101 is used to determine the network slice that the terminal is allowed to access and the network slice that the terminal is denied access to; the processing module 3101 is also used to determine the registration area of ​​the terminal based on the network slice that the terminal is allowed to access and the network slice that the terminal is denied access to; the transceiver module 3102 is used to send registration area information to the terminal.

[0806] As a possible implementation, the transceiver module 3102 is further configured to receive, through a first access network device in the first network, information about a network slice that the terminal requests to access, where the information about the network slice that the terminal requests to access includes identification information of a first network slice that is not supported by the first tracking area, and identification information of a second network slice that is supported by the first tracking area, where the first tracking area is the tracking area of ​​the first access network device. The network slice that the terminal is allowed to access includes the second network slice, and the network slice that the terminal is denied access to includes the first network slice; the registration area excludes tracking areas that support the first network slice and the second network slice, or the registration area excludes tracking areas of access network devices that support the first network slice and the second network slice.

[0807] As a possible implementation method, the processing module 3101 is also used to determine the network slices supported by the tracking area of ​​the first access network device.

[0808] In some implementation scenarios:

[0809] The processing module 3101 is used to determine the first network slice, which does not belong to the network slice allowed to be accessed by the terminal in the first cell, and the registration area of ​​the terminal includes the first cell and the second cell; when the terminal is switched from the first cell to the second cell, the processing module 3101 is also used to determine that the first network slice is available in the second cell; the transceiver module 3102 is also used to notify the terminal that the first network slice is available in the second cell.

[0810] As a possible implementation method, the processing module 3101 is used to determine the first network slice, including: the processing module 3101 is used to control the transceiver module 3102 to receive information about the network slice that the terminal requests to access through the first cell, and the information about the network slice that the terminal requests to access includes identification information of the first network slice; the processing module 3101 is also used to determine the network slice that the terminal is allowed to access; the processing module 3101 is also used to learn that the first network slice does not belong to the network slice that the terminal is allowed to access in the first cell.

[0811] As a possible implementation method, the processing module 3101 is used to determine that the first network slice is available in the second cell, including: the processing module 3101 is used to query the context of the target access network device, the context of the target access network device indicates that the tracking area of ​​the target access network device supports the first network slice, wherein the second cell is a cell in the tracking area of ​​the target access network device.

[0812] As a possible implementation method, the processing module 3101 is used to determine that the first network slice is available in the second cell, including: the processing module 3101 is used to control the transceiver module 3102 to send the identification information of the first network slice to the target access network device; the processing module 3101 is also used to obtain from the target access network device whether the terminal can access the first network slice in the second cell.

[0813] As a possible implementation method, the processing module 3101 is used to determine that the first network slice is available in the second cell, including: the processing module 3101 is used to determine that the first network slice is available in the second cell when the transceiver module 3102 receives a path switching request message from the second access network device; or, the processing module 3101 is used to determine that the first network slice is available in the second cell when the transceiver module 3102 receives a switching requirement message from the first access network device, and the switching requirement message includes an identifier of the second access network device.

[0814] As a possible implementation method, the processing module 3101 is also used to save the identification information of the first network slice; the transceiver module 3102 is also used to receive indication information from the terminal; the processing module 3101 is also used to delete the identification information of the first network slice according to the indication information.

[0815] As a possible implementation method, the processing module 3101 is used to determine the first network slice, including: the processing module 3101 is used to control the transceiver module 3102 to send information about the network slice that the terminal requests to access to the mobile management device, and the information about the network slice that the terminal requests to access includes identification information of the first network slice; the processing module 3101 is also used to obtain from the mobile management device that the first network slice does not belong to the network slice that the terminal is allowed to access in the first cell.

[0816] As a possible implementation method, the processing module 3101 is used to determine the first network slice, including: when the terminal is switched from the first access network device to the second access network device, the processing module 3101 is used to learn from the mobile management device that the first network slice in the first cell does not belong to the network slice allowed to be accessed by the terminal.

[0817] As a possible implementation method, the processing module 3101 is used to determine that the first network slice is available in the second cell, including: the processing module 3101 is used to determine that the terminal can access the first network slice in the second cell.

[0818] In some implementation scenarios:

[0819] The processing module 3101 is used to determine the first network slice, which does not belong to the network slice allowed to be accessed by the terminal in the first cell, and the registration area of ​​the terminal includes the first cell and the second cell; when the terminal is switched from the first cell to the second cell, the processing module 3101 is also used to determine that the first network slice is available in the third cell, and the physical coverage area of ​​the third cell partially or completely overlaps with the physical coverage area of ​​the second cell; the transceiver module 3102 is also used to notify the terminal that the first network slice is available in the third cell.

[0820] In some implementation scenarios:

[0821] The processing module 3101 is used to determine the first network slice, which does not belong to the network slice allowed to be accessed by the terminal in the first cell, and the registration area of ​​the terminal includes the first cell and the second cell; the processing module 3101 is also used to determine that the first network slice is available in the second cell; the transceiver module 3102 is used to notify the terminal that the first network slice is available in the second cell; the transceiver module 3102 is also used to send the cell identifier of the second cell to the terminal.

[0822] As a possible implementation method, the processing module 3101 is used to determine the first network slice, including: the processing module 3101 is used to control the transceiver module 3102 to receive information about the network slice that the terminal requests to access through the first cell, and the information about the network slice that the terminal requests to access includes identification information of the first network slice; the processing module 3101 is also used to determine the network slice that the terminal is allowed to access; the processing module 3101 is also used to learn that the first network slice does not belong to the network slice that the terminal is allowed to access in the first cell.

[0823] As a possible implementation method, the processing module 3101 is used to determine that the first network slice is available in the second cell, including: the processing module 3101 is used to control the transceiver module 3102 to receive the cell identifier of the second cell from the first access network device, wherein the second cell is a neighboring cell of the first cell, and the terminal can access the first network slice in the second cell.

[0824] As a possible implementation method, the processing module 3101 is used to determine that the first network slice is available in the second cell, including: the processing module 3101 is used to control the transceiver module 3102 to receive signal quality information of the neighboring cells of the first cell from the first access network device, and the neighboring cells of the first cell include the second cell; the processing module 3101 is also used to determine that the terminal can access the first network slice in the second cell based on the signal quality information of the second cell.

[0825] As a possible implementation method, the transceiver module 3102 is also used to send reference frequency information corresponding to the first network slice to the first access network device.

[0826] As a possible implementation method, the processing module 3101 is also used to save the identification information of the first network slice; the transceiver module 3102 is also used to receive indication information from the terminal; the processing module 3101 is also used to delete the identification information of the first network slice according to the indication information.

[0827] In some implementation scenarios:

[0828] The processing module 3101 is used to determine the first network slice, where the first network slice does not belong to the network slice that the terminal is allowed to access in the first cell, and the registration area of ​​the terminal includes the first cell and the second cell; the processing module 3101 is also used to determine that the first network slice is available in the third cell, and the physical coverage of the third cell partially or completely overlaps with the physical coverage of the second cell; the transceiver module 3102 is used to notify the terminal that the first network slice is available in the third cell; the transceiver module 3102 is also used to send the cell identifier of the third cell to the terminal.

[0829] Among them, all relevant contents of each step involved in the above method embodiment can be referred to the functional description of the corresponding functional module and will not be repeated here.

[0830] In this application, the network device 310 is presented in the form of various functional modules divided in an integrated manner. Here, "module" can refer to a specific application-specific integrated circuit (ASIC), circuit, processor and memory that executes one or more software or firmware programs, integrated logic circuit, and / or other devices that can provide the above functions.

[0831] In some embodiments, in terms of hardware implementation, those skilled in the art may understand that the network device 310 may adopt Figure 10 The communication device 1000 is shown in the form of.

[0832] As an example, Figure 31 The function / implementation process of the processing module 3101 can be achieved by Figure 10 The processor 1001 in the communication device 1000 shown calls the computer execution instructions stored in the memory 1003 to implement, Figure 31 The function / implementation process of the transceiver module 3102 can be achieved by Figure 10 The communication interface 1004 in the communication device 1000 is implemented as shown.

[0833] In some embodiments, when Figure 31 When the network device 310 is a chip or a chip system, the function / implementation process of the transceiver module 3102 can be implemented through the input and output interface (or communication interface) of the chip or the chip system, and the function / implementation process of the processing module 3101 can be implemented through the processor (or processing circuit) of the chip or the chip system.

[0834] Since the network device 310 provided in this embodiment can execute the above-mentioned communication method based on network slicing, the technical effects that can be obtained can refer to the above-mentioned method embodiments and will not be repeated here.

[0835] Taking the communication device as the terminal in the above method embodiment as an example, Figure 32 FIG3 shows a schematic diagram of the structure of a terminal 320. The terminal 320 includes a processing module 3201 and a transceiver module 3202.

[0836] In some embodiments, the terminal 320 may further include a storage module ( Figure 32 ), for storing program instructions and data.

[0837] In some embodiments, the transceiver module 3202, which may also be referred to as a transceiver unit, is configured to implement a transmitting and / or receiving function. The transceiver module 3202 may be composed of a transceiver circuit, a transceiver, a transceiver, or a communication interface.

[0838] In some embodiments, the transceiver module 3202 may include a receiving module and a sending module, which are respectively used to execute the receiving and sending steps performed by the terminal in the above-mentioned method embodiments, and / or used to support other processes of the technology described herein; the processing module 3201 may be used to execute the processing steps (such as determination, acquisition, etc.) performed by the terminal in the above-mentioned method embodiments, and / or used to support other processes of the technology described herein.

[0839] Specifically, the transceiver module 3202 is used to obtain information from the network device that the first network slice is available in the second cell, wherein the first network slice does not belong to the network slice allowed to be accessed by the terminal in the first cell, and the registration area of ​​the terminal includes the first cell and the second cell; the processing module 3201 is used to initiate a registration process for the application corresponding to the first network slice.

[0840] As a possible implementation manner, the transceiver module 3202 is further configured to receive a cell identifier from a network device, where the cell identifier is used for the second cell.

[0841] As a possible implementation method, processing module 3201 is used to initiate a registration process for the application corresponding to the first network slice, including: processing module 3201 is used to access the second cell; processing module 3201 is also used to initiate a registration process for the application through the second cell.

[0842] As a possible implementation manner, the processing module 3201 is used to initiate a registration process for the application corresponding to the first network slice, including: in response to the fact that the context of the terminal does not include a session for the application and does not include a routing selection policy for the application, as a possible implementation manner, the processing module 3201 is used to determine whether the first network slice is the network slice corresponding to the application; in the case that the first network slice is the network slice corresponding to the application, the processing module 3201 is used to initiate a registration process for the application.

[0843] As a possible implementation method, the transceiver module 3202 is also used to notify the network device terminal that it no longer requests access to the first network slice.

[0844] Among them, all relevant contents of each step involved in the above method embodiment can be referred to the functional description of the corresponding functional module and will not be repeated here.

[0845] In this application, the terminal 320 is presented in the form of various functional modules divided in an integrated manner. The "module" here can refer to a specific application-specific integrated circuit (ASIC), a circuit, a processor and memory that executes one or more software or firmware programs, an integrated logic circuit, and / or other devices that can provide the above functions.

[0846] In some embodiments, in terms of hardware implementation, those skilled in the art may imagine that the terminal 320 may use Figure 10 The communication device 1000 is shown in the form of.

[0847] As an example, Figure 32 The function / implementation process of the processing module 3201 can be achieved by Figure 10 The processor 1001 in the communication device 1000 shown calls the computer execution instructions stored in the memory 1003 to implement, Figure 32 The function / implementation process of the transceiver module 3202 can be achieved by Figure 10 The communication interface 1004 in the communication device 1000 is implemented as shown.

[0848] In some embodiments, when Figure 32 When the terminal 320 is a chip or a chip system, the function / implementation process of the transceiver module 3202 can be implemented through the input and output interface (or communication interface) of the chip or the chip system, and the function / implementation process of the processing module 3201 can be implemented through the processor (or processing circuit) of the chip or the chip system.

[0849] Since the terminal 320 provided in this embodiment can execute the above-mentioned communication method based on network slicing, the technical effects that can be obtained can refer to the above-mentioned method embodiments and will not be repeated here.

[0850] As a possible product form, the network device and terminal described in the embodiments of the present application can also be implemented using the following: one or more field programmable gate arrays (FPGAs), programmable logic devices (PLDs), controllers, state machines, gate logic, discrete hardware components, any other suitable circuits, or any combination of circuits capable of performing the various functions described throughout this application.

[0851] In some embodiments, an embodiment of the present application further provides a communication device, which includes a processor for implementing the method in any of the above method embodiments.

[0852] As a possible implementation, the communication device further includes a memory. The memory is used to store necessary program instructions and data. The processor can call the program code stored in the memory to instruct the communication device to execute any of the above-mentioned method embodiments. Of course, the memory may not be located in the communication device.

[0853] As another possible implementation, the communication device also includes an interface circuit, which is a code / data read / write interface circuit, and the interface circuit is used to receive computer execution instructions (computer execution instructions are stored in a memory, may be read directly from the memory, or may pass through other devices) and transmit them to the processor.

[0854] As another possible implementation, the communication device further includes a communication interface, where the communication interface is used to communicate with a module outside the communication device.

[0855] It can be understood that the communication device can be a chip or a chip system. When the communication device is a chip system, it can be composed of chips or include chips and other discrete devices. The embodiments of the present application do not specifically limit this.

[0856] In some embodiments, an embodiment of the present application also provides a communication device (for example, the communication device can be a chip or a chip system), which includes an interface circuit and a logic circuit, wherein the interface circuit is used to obtain input information and / or output output information; the logic circuit is used to execute the method in any of the above method embodiments, and process and / or generate output information based on the input information.

[0857] When the communication device is used to implement the functions of the network device in the above method embodiment:

[0858] In some implementation scenarios:

[0859] As a possible implementation, the input information may be: information about a network slice that the terminal requests to access, the information about the network slice that the terminal requests to access including identification information of a first network slice that is not supported by the first tracking area, and identification information of a second network slice. Processing based on the input information may include: determining a network slice that the terminal is allowed to access, or determining a registration area.

[0860] As a possible implementation method, the output information may be: information of a registration area, which excludes the tracking area supporting the first network slice and the second network slice, or the registration area excludes the tracking area of ​​the access network device supporting the first network slice and the second network slice.

[0861] In some implementation scenarios:

[0862] As a possible implementation method, the output information may be: information used to notify the terminal that the first network slice is available in the second cell.

[0863] As a possible implementation, the input information may be: information about a network slice that the terminal requests to access, where the information about the network slice that the terminal requests to access includes identification information of the first network slice. Processing based on the input information may include: determining that the terminal is allowed to access a network slice, or that the first network slice does not belong to a network slice that the terminal is allowed to access in the first cell.

[0864] As a possible implementation method, the output information can be: identification information of the first network slice.

[0865] As a possible implementation, the input information may be information used by the network device to learn that the terminal can access the first network slice in the second cell. Processing according to the input information may be: learning that the terminal can access the first network slice in the second cell.

[0866] As a possible implementation manner, the input information may be: a path switching request message. Processing according to the input information may be: determining that the first network slice is available in the second cell.

[0867] As a possible implementation manner, the input information may be: a handover request message. Processing according to the input information may be: determining that the first network slice is available in the second cell.

[0868] As a possible implementation manner, the input information may be: indication information. Processing according to the input information may be: deleting the identification information of the first network slice according to the indication information.

[0869] In some implementation scenarios:

[0870] As a possible implementation method, the output information may be: information used to notify the terminal that the first network slice is available in the second cell, and the cell identifier of the second cell.

[0871] As a possible implementation, the input information may be: information about a network slice that the terminal requests to access, where the information about the terminal's access request includes identification information of the first network slice. Processing based on the input information may include: determining a network slice that the terminal is allowed to access, and learning that the first network slice does not belong to a network slice that the terminal is allowed to access in the first cell.

[0872] As a possible implementation manner, the input information may be: a cell identifier of the second cell. Processing according to the input information may be: determining that the first network slice is available in the second cell.

[0873] As a possible implementation, the input information may be signal quality information of a neighboring cell of the first cell, where the neighboring cell of the first cell includes the second cell. Processing based on the input information may be: determining, based on the signal quality information of the second cell, that the terminal can access the first network slice in the second cell.

[0874] As a possible implementation method, the output information may be: reference frequency information corresponding to the first network slice.

[0875] As a possible implementation manner, the input information may be: indication information. Processing according to the input information may be: deleting the identification information of the first network slice according to the indication information.

[0876] When the communication device is used to implement the functions of the terminal in the above method embodiment:

[0877] As a possible implementation, the input information may be information for obtaining information that the first network slice is available in the second cell. Processing according to the input information may be initiating a registration process for an application corresponding to the first network slice.

[0878] As a possible implementation manner, the input information may be: a cell identifier, where the cell identifier is used for the second cell. Processing according to the input information may be: accessing the second cell.

[0879] As a possible implementation method, the output information may be: information used to notify the terminal that it no longer requests access to the first network slice.

[0880] Among them, the communication device provided in this embodiment can execute the method in the above method embodiment, so the technical effects that can be obtained can refer to the above method embodiment and will not be repeated here.

[0881] As a possible product form, the network device and terminal described in the embodiments of the present application can be implemented by a general bus architecture.

[0882] For ease of explanation, see Figure 33 , Figure 33 3 is a schematic structural diagram of a communication device 3300 provided in an embodiment of the present application, wherein the communication device 3300 includes a processor 3301 and a transceiver 3302. The communication device 3300 may be a network device or a terminal, or a chip therein. Figure 33 Only the main components of the communication device 3300 are shown. In addition to the processor 3301 and the transceiver 3302, the communication device may further include a memory 3303 and an input and output device (not shown).

[0883] The processor 3301 is primarily used to process communication protocols and communication data, control the entire communication device, execute software programs, and process software program data. The memory 3303 is primarily used to store software programs and data. The transceiver 3302 may include a radio frequency circuit and an antenna. The radio frequency circuit is primarily used to convert baseband signals into radio frequency signals and process radio frequency signals. The antenna is primarily used to transmit and receive radio frequency signals in the form of electromagnetic waves. Input and output devices, such as a touch screen, display, and keyboard, are primarily used to receive user input and output data to the user.

[0884] The processor 3301 , the transceiver 3302 , and the memory 3303 may be connected via a communication bus.

[0885] When the communication device is powered on, the processor 3301 can read the software program in the memory 3303, interpret and execute the instructions of the software program, and process the data of the software program. When data needs to be sent wirelessly, the processor 3301 performs baseband processing on the data to be sent and outputs the baseband signal to the radio frequency circuit. The radio frequency circuit performs radio frequency processing on the baseband signal and then transmits the radio frequency signal to the outside in the form of electromagnetic waves through the antenna. When data is sent to the communication device, the radio frequency circuit receives the radio frequency signal through the antenna, converts the radio frequency signal into a baseband signal, and outputs the baseband signal to the processor 3301. The processor 3301 converts the baseband signal into data and processes the data.

[0886] In another implementation, the RF circuit and antenna may be provided independently of the processor performing baseband processing. For example, in a distributed scenario, the RF circuit and antenna may be remotely arranged independent of the communication device.

[0887] It should be understood that in the various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0888] The steps in the method of the embodiment of the present application can be adjusted in order, combined and deleted according to actual needs.

[0889] The modules in the device of the embodiment of the present application can be merged, divided and deleted according to actual needs.

[0890] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using a software program, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from a website, computer, server or data center to another website, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center that contains one or more media that can be integrated. The available medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid state disk (SSD)). In the embodiment of the present application, the computer may include the aforementioned device.

[0891] Although the present application is described herein in conjunction with various embodiments, in the process of implementing the claimed application, those skilled in the art can understand and implement other changes to the disclosed embodiments by reviewing the drawings, the disclosure, and the appended claims. In the claims, the word "comprising" does not exclude other components or steps, and "a" or "an" does not exclude multiple situations. A single processor or other unit can implement several functions listed in the claims. Certain measures are recorded in different dependent claims, but this does not mean that these measures cannot be combined to produce good results.

[0892] Although the present application has been described with reference to specific features and embodiments thereof, it is apparent that various modifications and combinations may be made thereto without departing from the spirit and scope of the present application. Accordingly, this specification and the drawings are merely illustrative of the present application as defined by the appended claims and are deemed to cover any and all modifications, variations, combinations or equivalents within the scope of the present application. Obviously, those skilled in the art may make various modifications and variations to the present application without departing from the spirit and scope of the present application. Thus, the present application is intended to include such modifications and variations as fall within the scope of the claims of the present application and their equivalents.

Claims

1. A communication method, characterized in that: The method comprises: Learning from a network device that a first network slice is available in a second cell, wherein the first network slice does not belong to a network slice to which the terminal is allowed to access in the first cell, the registration area of ​​the terminal includes a first tracking area and a second tracking area, the second cell is a cell in the second tracking area, and the first cell is a cell in the first tracking area; Initiate a registration process for the application corresponding to the first network slice in the second cell.

2. The method according to claim 1, characterized in that The first network slice is included in a network slice configured by the terminal in the first network.

3. The method according to claim 1 or 2, characterized in that The first network slice is included in the network slice that the terminal requests to access in the first cell.

4. The method according to any one of claims 1 to 3, characterized in that The initiating a registration process for the application corresponding to the first network slice in the second cell includes: When the terminal switches from the first cell to the second cell, a registration process is initiated in the second cell for the application corresponding to the first network slice.

5. The method according to any one of claims 1 to 4, characterized in that The initiating a registration process for an application corresponding to the first network slice in the second cell includes: accessing the second cell; The registration process is initiated for the application through the second cell.

6. The method according to any one of claims 1 to 5, characterized in that The initiating a registration process for an application corresponding to the first network slice in the second cell includes: In response to the context of the terminal not including a session for the application and not including a routing policy for the application, determining whether the first network slice is a network slice corresponding to the application; In the case that the first network slice is the network slice corresponding to the application, the registration process is initiated for the application.

7. The method according to any one of claims 1 to 6, characterized in that The method further comprises: Notify the network device that the terminal no longer requests access to the first network slice.

8. A communication method, characterized in that: include: Determine a first network slice, where the first network slice does not belong to a network slice to which the terminal is allowed to access in a first cell, the registration area of ​​the terminal includes a first tracking area and a second tracking area, the second cell is a cell in the second tracking area, and the first cell is a cell in the first tracking area; Determining that the first network slice is available in the second cell; Notify the terminal that the first network slice is available in the second cell.

9. The method according to claim 8, characterized in that The first network slice is included in a network slice configured by the terminal in the first network.

10. The method according to claim 8 or 9, characterized in that The first network slice is included in the network slice that the terminal requests to access in the first cell.

11. The method according to any one of claims 8 to 10, characterized in that The method is executed by a mobile management device.

12. The method according to any one of claims 8 to 11, characterized in that: The determining the first network slice includes: receiving, through the first cell, information about the network slice that the terminal requests to access, where the information about the network slice that the terminal requests to access includes identification information of the first network slice; Determining a network slice that the terminal is allowed to access; It is learned that the first network slice in the first cell does not belong to the network slice that the terminal is allowed to access.

13. The method according to any one of claims 8 to 12, characterized in that: In the case where the second cell belongs to the second access network device, the target access network device is the second access network device; in the case where the second cell belongs to the first access network device, the target access network device is the first access network device.

14. The method according to claim 13, characterized in that The determining that the first network slice is available in the second cell includes: The context of the target access network device is queried, and the context of the target access network device indicates that the tracking area of ​​the target access network device supports the first network slice, wherein the second cell is a cell in the tracking area of ​​the target access network device.

15. The method according to claim 13 or 14, characterized in that The determining that the first network slice is available in the second cell includes: Sending identification information of the first network slice to the target access network device; It is learned from the target access network device that the terminal can access the first network slice in the second cell.

16. The method according to any one of claims 13 to 15, characterized in that In a case where the second cell belongs to the second access network device, the determining that the first network slice is available in the second cell includes: Upon receiving a path switching request message from the second access network device, determining that the first network slice is available in the second cell; or, When a switching requirement message is received from the first access network device, it is determined that the first network slice is available in the second cell, and the switching requirement message includes an identifier of the second access network device.

17. The method according to any one of claims 11 to 16, characterized in that The method further comprises: Saving identification information of the first network slice; After notifying the terminal that the first network slice is available in the second cell, receiving indication information from the terminal; According to the indication information, delete the identification information of the first network slice.

18. The method according to claim 17, characterized in that The indication information is used to instruct the terminal to no longer request access to the first network slice.

19. The method according to any one of claims 8 to 18, characterized in that The determining that the first network slice is available in the second cell includes: Before the terminal switches from the first cell to the second cell, it is determined that the first network slice is available in the second cell.

20. The method according to any one of claims 8 to 19, characterized in that The notifying the terminal that the first network slice is available in the second cell includes: Before the terminal switches from the first cell to the second cell, the terminal is notified that the first network slice is available in the second cell.

21. A communication device, characterized in that: Including processor; The processor is configured to read and execute a program from a memory to implement the method according to any one of claims 1 to 7, or to implement the method according to any one of claims 8 to 20.

22. A computer program product comprising instructions, characterized in that When the method is executed on a computer, the computer is enabled to execute the method according to any one of claims 1 to 7 or the method according to any one of claims 8 to 20.

23. A computer-readable storage medium, characterized in that The computer-readable storage medium stores instructions, which, when executed on a computer, enable a processor to execute the method according to any one of claims 1 to 7, or to execute the method according to any one of claims 8 to 20.

24. A communication device, characterized in that: The communication device includes: a logic circuit and an interface circuit; The interface circuit is used to obtain input information and / or output information; The logic circuit is used to execute the method according to any one of claims 1 to 7, or to execute the method according to any one of claims 8 to 20, to process information input by the interface circuit and / or to generate information output by the interface circuit.

Images