Network slice-based communication method and apparatus
Patent Information
- Application Number
- IN202337055419
- Authority / Receiving Office
- IN · IN
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2021-02-09
- Filing Date
- 2023-08-18
- Publication Date
- 2026-10-26
- Estimated Expiration
- 2042-01-30
AI Technical Summary
In network slicing technology, terminals often fail to access network slices due to unsupported tracking areas during registration, leading to persistent access issues even when moving to supporting areas, affecting service performance and user experience.
A network slice-based communication method where a network device determines allowed and rejected network slices, and adjusts the registration area to exclude unsupported tracking areas, enabling terminals to re-initiate registration and access network slices when moving into supporting areas.
This method improves the success rate of accessing network slices, enhancing service performance and user experience by ensuring terminals can reconnect to supported network slices upon movement.
Abstract
Description
TECHNICAL FIELD
[0002] This application relates to the communications field, and in particular,to a network slice-based communication method and an apparatus.BACKGROUND
[0003] A network slicing technology provides mutually isolated networkenvironments for different application scenarios in a manner of virtualizingindependent logical networks on a same network infrastructure, so that networkfunctions and features of the different application scenarios can be customizedbased on respective requirements, and quality of service (QoS) requirements ofdifferent services can be effectively ensured. Generally, a network slice isidentified by single network slice selection assistance information (S-NSSAI), andnetwork slice selection assistance information (NSSAI) is a set of S-NSSAI.
[0004] A capability of a radio access network (RAN) to support a networkslice is divided by using a tracking area (TA) as a granularity. One TA maysupport one or more network slices, and cells in a same TA may support a samenetwork slice.
[0005] When network slices are deployed, a network slice may be selected ina registration procedure. For example, a core network sends allowed NSSAI to aterminal based on NSSAI requested by the terminal, subscription data of theterminal, a network slice supported by a TA in which the terminal is currentlylocated, and the like. The allowed NSSAI is NSSAI that can be accessed by theterminal.
[0006] However, in actual application, the following scenario may exist: In aregistration procedure, because a TA in which a terminal is currently located doesnot support a network slice that the terminal intends to access, the terminal doesnot access the network slice in this registration procedure. Subsequently, even ifthe terminal moves to a TA that supports the network slice, the terminal may stillbe unable to normally access the network slice.SUMMARY
[0007] This application provides a network slice-based communicationmethod and an apparatus, to improve a success rate of accessing a network sliceby a terminal, thereby improving service performance and user experience.
[0008] To achieve the foregoing objectives, the following technical solutionsare used in this application:
[0009] According to a first aspect, a network slice-based communicationmethod is provided. The method may be performed by a network device, or maybe performed by a component of a network device, for example, a processor, achip, or a chip system of the network device. In this application, an example inwhich the network device performs the method is used for description.
[0010] The method includes: The network device receives, via a first accessnetwork device in a first network, information about a network slice that aterminal requests to access, determines a network slice that the terminal is allowedto access and a registration area, and sends information about the registration areato the terminal. The information about the network slice that the terminal requeststo access includes identification information of a first network slice not supportedby a first tracking area and includes identification information of a secondnetwork slice; a second tracking area in the first network supports the firstnetwork slice, and the network slice that the terminal is allowed to access includesthe second network slice; and the registration area excludes a tracking area thatsupports the first network slice and the second network slice, or excludes atracking area of an access network device that supports the first network slice andthe second network slice.
[0011] Based on this solution, when determining the registration area, thenetwork device excludes the tracking area that supports the first network slice andthe second network slice, or excludes the tracking area of the access networkdevice that supports the first network slice and the second network slice.Therefore, when the terminal moves within the excluded tracking area, becausethe registration area of the terminal does not include the tracking area, and thetracking area supports the first network slice, the terminal may re-initiate aregistration procedure to request to access the first network slice, to increase asuccess rate of accessing the first network slice, thereby improving serviceperformance and user experience.
[0012] In some possible designs, the method further includes: The networkdevice determines a network slice that the terminal is rejected to access, where thenetwork slice that the terminal is rejected to access includes the first network slice.
[0013] Based on this possible design, when determining the registration area,the network device may exclude a tracking area that supports the network slicethat the terminal is rejected to access, or exclude a tracking area of an accessnetwork device that supports the network slice that the terminal is rejected toaccess.
[0014] According to a second aspect, a network slice-based communicationmethod is provided. The method may be performed by a network device, or maybe performed by a component of a network device, for example, a processor, achip, or a chip system of the network device. In this application, an example inwhich the network device performs the method is used for description. Themethod includes: The network device determines a network slice that a terminal isallowed to access and a network slice that the terminal is rejected to access,determines a registration area of the terminal based on the network slice that theterminal is allowed to access and the network slice that the terminal is rejected toaccess, and sends information about the registration area to the terminal.
[0015] Based on this solution, the network device may determine theregistration area of the terminal based on the network slice that the terminal isallowed to access and the network slice that the terminal is rejected to access, toconsider that tracking area supporting the network slice that the terminal isrejected to access is excluded from the registration area. For example, theregistration area excludes a tracking area that supports the network slice that theterminal is rejected to access, or a tracking area of an access network device thatsupports the network slice that the terminal is rejected to access. Therefore, whenthe terminal moves within the excluded tracking area, because the registrationarea of the terminal does not include the tracking area, and the tracking areasupports the first network slice, the terminal may re-initiate a registrationprocedure to request to access the first network slice, to increase a success rate ofaccessing the first network slice, thereby improving service performance and userexperience.
[0016] In some possible designs, the method further includes: The networkdevice receives, via a first access network device in a first network, informationabout a network slice that a terminal requests to access. The information about thenetwork slice that the terminal requests to access includes identificationinformation of a first network slice not supported by a first tracking area andincludes identification information of a second network slice supported by thefirst tracking area, and the first tracking area is a tracking area of the first accessnetwork device. The network slice that the terminal is allowed to access includesthe second network slice, and the network slice that the terminal is rejected toaccess includes the first network slice; and the registration area excludes atracking area that supports the first network slice and the second network slice, orthe registration area excludes a tracking area of an access network device thatsupports the first network slice and the second network slice.
[0017] With reference to the first aspect or the second aspect, in some possibledesigns, the first network slice is a network slice that the terminal is allowed toaccess in the first network.
[0018] With reference to the first aspect or the second aspect, in some possibledesigns, the method further includes: The network device determines a networkslice supported by the tracking area of the first access network device.
[0019] According to a third aspect, a network slice-based communicationmethod is provided. The method may be performed by a network device, or maybe performed by a component of a network device, for example, a processor, achip, or a chip system of the network device. In this application, an example inwhich the network device performs the method is used for description. Themethod includes: The network device determines a first network slice, where thefirst network slice does not belong to a network slice that a terminal is allowed toaccess in a first cell, and a registration area of the terminal includes the first celland a second cell; and the network device determines, when the terminal ishanded over from the first cell to the second cell, that the first network slice isavailable in the second cell, and notifies the terminal that the first network slice isavailable in the second cell.
[0020] In the current technology, the first network slice does not belong to thenetwork slice that the terminal is allowed to access in the first cell, that is, wheninitiating a registration procedure in the first cell, the terminal cannot access thefirst network slice. Because the registration area of the terminal includes the firstcell and the second cell, when the terminal is handed over from the first cell to thesecond cell, the terminal is not triggered to perform a re-registration procedure.Even if the first network slice is available in the second cell, because of initiatingno registration procedure in the second cell, the terminal still cannot access thefirst network slice in the second cell. Based on this solution, when the terminal ishanded over from the first cell to the second cell, and it is determined that the firstnetwork slice is available in the second cell, the network device notifies theterminal that the first network slice is available in the second cell, so that whenstill intending to access the first network slice, the terminal may initiate aregistration procedure to request to access the first network slice, therebyimproving a success rate of accessing the first network slice, and furtherimproving service performance and user experience.
[0021] In some possible designs, when the second cell belongs to the secondaccess network device, a target access network device is the second accessnetwork device; or when the second cell belongs to the first access network device,a target access network device is the first access network device. The first cellbelongs to the first access network device. Therefore, it may be understood thatthe second cell belongs to the second access network device (that is, the first celland the second cell belong to different access network devices) to correspond toan inter-eNodeB handover scenario; or the second cell belongs to the first accessnetwork device (that is, the first cell and the second cell belong to a same accessnetwork device) to correspond to an intra-eNodeB handover scenario. This is alsoapplicable to a design in another aspect of this application, and details are notdescribed below again. Based on this possible design, in either the intra-eNodeBhandover scenario or the inter-eNodeB handover scenario, a success rate ofaccessing the first network slice can be improved.
[0022] In some possible designs, when the network device is a mobilitymanagement device, that the network device determines that the first networkslice is available in the second cell includes: The network device queries a contextof the target access network device, where the context of the target access networkdevice indicates that a tracking area of the target access network device supportsthe first network slice, where the second cell is a cell in the tracking area of thetarget access network device. Based on this possible design, the network devicemay determine, through the locally stored context of the target access networkdevice, that the first network slice is available in the second cell, and does notneed to interact with another device, thereby reducing signaling overheads.
[0023] In some possible designs, when the network device is a mobilitymanagement device, that the network device determines that the first networkslice is available in the second cell includes: The network device sendsidentification information of the first network slice to the target access networkdevice, and learns, from the target access network device, that the first networkslice can access the terminal in the second cell.
[0024] In some possible designs, when the network device is a mobilitymanagement device, and the second cell belongs to the second access networkdevice, that the network device determines that the first network slice is availablein the second cell includes: The network device determines, when receiving a pathswitch request message from the second access network device, that the firstnetwork slice is available in the second cell; or the network device determines,when receiving a handover required message from the first access network device,that the first network slice is available in the second cell, where the handoverrequired message includes an identifier of the second access network device.
[0025] Based on this possible design, the network device may confirm, to atarget network device, whether the terminal can access the first network slicesupported by the tracking area of the target access network device, to prevent thenetwork device from notifying, when the target access network device supportsthe first network slice but the terminal cannot access the first network slice in thesecond cell, the terminal that the first network slice is available in the second cell,thereby improving a success rate of accessing the first network slice by theterminal in the second cell.
[0026] In some possible designs, when the network device is a mobilitymanagement device, the method further includes: The network device stores theidentification information of the first network slice; the network device receivesindication information from the terminal after the network device notifies theterminal that the first network slice is available in the second cell; and the networkdevice deletes the identification information of the first network slice based on theindication information.
[0027] In some possible designs, when the network device is a mobilitymanagement device, the indication information indicates that the terminal nolonger requests to access the first network slice.
[0028] Based on the foregoing two possible designs, when the indicationinformation indicates that the terminal no longer requests to access the firstnetwork slice, the network device deletes the identification information of the firstnetwork slice. When subsequently serving the terminal, the network device mayno longer notify the terminal of a cell that can access the first network slice,thereby reducing signaling overheads and reducing resource waste.
[0029] In some possible designs, when the second cell belongs to the secondaccess network device, the network device is the second access network device; orwhen the second cell belongs to the first access network device, the networkdevice is the first access network device. Based on this possible design, in eitherthe intra-eNodeB handover scenario or the inter-eNodeB handover scenario, asuccess rate of accessing the first network slice can be improved.
[0030] In some possible designs, when the second cell belongs to the firstaccess network device, that the network device determines the first network sliceincludes: The network device sends, to a mobility management device,information about a network slice that the terminal requests to access, where theinformation about the network slice that the terminal requests to access includesidentification information of the first network slice; and the network device learns,from the mobility management device, that the first network slice does not belongto a network slice that the terminal is allowed to access in the first cell. In otherwords, the network device may learn, from the mobility management device in theregistration procedure, that the first network slice does not belong to the networkslice that the terminal is allowed to access in the first cell. This is also applicableto a design in another aspect of this application, and details are not describedbelow again.
[0031] In some possible designs, when the second cell belongs to the secondaccess network device, that the network device determines the first network sliceincludes: When the terminal is handed over from the first access network deviceto the second access network device, the network device learns, from the mobilitymanagement device, that the first network slice does not belong to the networkslice that the terminal is allowed to access in the first cell. In other words, in theinter-eNodeB handover scenario, the network device may learn, from the mobilitymanagement device, that the first network slice does not belong to the networkslice that the terminal is allowed to access in the first cell. This is also applicableto a design in another aspect of this application, and details are not describedbelow again.
[0032] In some possible designs, that the network device determines that thefirst network slice is available in the second cell includes: The network devicedetermines that the first network slice can access the terminal in the second cell.
[0033] According to a fourth aspect, a network slice-based communicationmethod is provided. The method may be performed by a network device, or maybe performed by a component of a network device, for example, a processor, achip, or a chip system of the network device. In this application, an example inwhich the network device performs the method is used for description. Themethod includes: The network device determines a first network slice, where thefirst network slice does not belong to a network slice that a terminal is allowed toaccess in a first cell, and a registration area of the terminal includes the first celland a second cell; and the network device determines, when the terminal ishanded over from the first cell to the second cell, that the first network slice isavailable in the third cell, and notifies the terminal that the first network slice isavailable in the third cell, where physical coverage of the third cell partially orcompletely overlaps physical coverage of the second cell.
[0034] In the current technology, the first network slice does not belong to thenetwork slice that the terminal is allowed to access in the first cell, that is, wheninitiating a registration procedure in the first cell, the terminal cannot access thefirst network slice. Because the registration area of the terminal includes the firstcell and the second cell, when the terminal is handed over from the first cell to thesecond cell, the terminal is not triggered to perform a re-registration procedure.Even if the first network slice is available in the third cell whose physicalcoverage is the same as that of the second cell, because of initiating noregistration procedure again in the second cell, the terminal still cannot access thefirst network slice in a location of the second cell. Based on this solution, whenthe terminal is handed over from the first cell to the second cell, and it isdetermined that the first network slice is available in the third cell, the terminal isnotified that the first network slice is available in the third cell, so that when stillintending to access the first network slice, the terminal may access the firstnetwork slice in the third cell, thereby improving a success rate of accessing thefirst network slice, and further improving service performance and userexperience.
[0035] In some possible designs, when the second cell belongs to the secondaccess network device, a target access network device is the second accessnetwork device; or when the second cell belongs to the first access network device,a target access network device is the first access network device. Based on thispossible design, in either the intra-eNodeB handover scenario or the inter-eNodeBhandover scenario, a success rate of accessing the first network slice can beimproved.
[0036] In some possible designs, when the network device is a mobilitymanagement device, that the network device determines that the first networkslice is available in the third cell includes: The network device queries a contextof the target access network device, where the context of the target access networkdevice indicates that a tracking area in which the third cell is located supports thefirst network slice but a tracking area in which the second cell is located does notsupport the first network slice, where the second cell and the third cell are cells ofthe target access network device. Based on this possible design, the networkdevice may determine, through the locally stored context of the target accessnetwork device, that the first network slice is available in the third cell, and doesnot need to interact with another device, thereby reducing signaling overheads.
[0037] In some possible designs, when the network device is a mobilitymanagement device, that the network device determines that the first networkslice is available in the third cell includes: The network device sends identificationinformation of the first network slice to the target access network device, andlearns, from the target access network device, that the first network slice canaccess the terminal in the third cell.
[0038] Based on this possible design, the network device may confirm, to atarget network device, whether the terminal can access the first network slicesupported by the tracking area of the target access network device, to prevent thenetwork device from notifying, when the target access network device supportsthe first network slice but the terminal cannot access the first network slice in thethird cell, the terminal that the first network slice is available in the third cell,thereby improving a success rate of accessing the first network slice by theterminal in the third cell.
[0039] With reference to the third aspect or the fourth aspect, in some possibledesigns, when the network device is a mobility management device, that thenetwork device determines the first network slice includes: The network devicereceives, via the first cell, information about a network slice that the terminalrequests to access, where the information about the network slice that the terminalrequests to access includes identification information of the first network slice;and the network device determines a network slice that the terminal is allowed toaccess, and learns that the first network slice does not belong to the network slicethat the terminal is allowed to access in the first cell.
[0040] With reference to the third aspect or the fourth aspect, in some possibledesigns, the first network slice is included in a network slice configured by theterminal for a first network. In other words, the network device may perform theforegoing method for the first network slice that does not belong to the networkslice that the terminal is allowed to access in the first cell but is included in thenetwork slice configured by the terminal for the first network. That is to say,regardless of whether the network slice that the terminal requests to access carriesthe identifier of the first network slice, because the first network slice is includedin the network slice configured by the terminal for the first network, the terminalmay subsequently intend to access the first network slice. In this case, whenintending to access the first network slice, the terminal may access the firstnetwork slice in the second cell or the third cell, thereby improving a success rateof accessing the first network slice. This is also applicable to a design in anotheraspect of this application, and details are not described below again.
[0041] With reference to the third aspect or the fourth aspect, in some possibledesigns, the first network slice is included in a network slice that the terminalrequests to access in the first cell.
[0042] With reference to the third aspect or the fourth aspect, in some possibledesigns, the first cell belongs to a first access network device, and the second cellbelongs to a second access network device; or the first cell and the second cellbelong to a first access network device.
[0043] According to a fifth aspect, a network slice-based communicationmethod is provided. The method may be performed by a network device, or maybe performed by a component of a network device, for example, a processor, achip, or a chip system of the network device. In this application, an example inwhich the network device performs the method is used for description. Themethod includes: The network device determines a first network slice, where thefirst network slice does not belong to a network slice that a terminal is allowed toaccess in a first cell, and a registration area of the terminal includes the first celland a second cell; and the network device determines that the first network slice isavailable in the second cell, notifies the terminal that the first network slice isavailable in the second cell; and sends a cell identifier of the second cell to theterminal.
[0044] In the current technology, the first network slice does not belong to thenetwork slice that the terminal is allowed to access in the first cell, that is, wheninitiating a registration procedure in the first cell, the terminal cannot access thefirst network slice. Because the registration area of the terminal includes the firstcell and the second cell, when the terminal is handed over from the first cell to thesecond cell, the terminal is not triggered to perform a re-registration procedure.Even if the first network slice is available in the second cell, because of initiatingno registration procedure in the second cell, the terminal still cannot access thefirst network slice in the second cell. Based on this solution, when determiningthat the first network slice is available in the second cell, the network devicenotifies the terminal that the first network slice is available in the second cell, andsends the cell identifier of the second cell, so that when still intending to accessthe first network slice, the terminal may access the second cell, and initiate aregistration procedure to request to access the first network slice, therebyimproving a success rate of accessing the first network slice, and furtherimproving service performance and user experience.
[0045] In some possible designs, that the network device determines that thefirst network slice is available in the second cell includes: The network devicereceives the cell identifier of the second cell from a first access network device,where the second cell is a neighboring cell of the first cell, and the network devicedetermines that the first network slice can access the terminal in the second cell.
[0046] In some possible designs, that the network device determines that thefirst network slice is available in the second cell includes: The network devicereceives signal quality information of a neighboring cell of the first cell from afirst access network device, where the neighboring cell of the first cell includesthe second cell; and the network device determines, based on the signal qualityinformation of the second cell, that the first network slice can access the terminalin the second cell.
[0047] In some possible designs, the method further includes: The networkdevice stores the identification information of the first network slice; the networkdevice receives indication information from the terminal after the network devicenotifies the terminal that the first network slice is available in the second cell, anddeletes the identification information of the first network slice based on theindication information.
[0048] In some possible designs, the indication information indicates that theterminal no longer requests to access the first network slice.
[0049] Based on the foregoing two possible designs, when the indicationinformation indicates that the terminal no longer requests to access the firstnetwork slice, the network device deletes the identification information of the firstnetwork slice. When subsequently serving the terminal, the network device mayno longer notify the terminal of a cell that can access the first network slice,thereby reducing signaling overheads and reducing resource waste.
[0050] According to a sixth aspect, a network slice-based communicationmethod is provided. The method may be performed by a network device, or maybe performed by a component of a network device, for example, a processor, achip, or a chip system of the network device. In this application, an example inwhich the network device performs the method is used for description. Themethod includes: The network device determines a first network slice, where thefirst network slice does not belong to a network slice that a terminal is allowed toaccess in a first cell, and a registration area of the terminal includes the first celland a second cell; and the network device determines that the first network slice isavailable in the third cell, notifies the terminal that the first network slice isavailable in the third cell, and sends a cell identifier of the third cell to theterminal, where physical coverage of the third cell partially or completelyoverlaps physical coverage of the second cell.
[0051] In the current technology, the first network slice does not belong to thenetwork slice that the terminal is allowed to access in the first cell, that is, wheninitiating a registration procedure in the first cell, the terminal cannot access thefirst network slice. Because the registration area of the terminal includes the firstcell and the second cell, when the terminal is handed over from the first cell to thesecond cell, the terminal is not triggered to perform a re-registration procedure.Even if the first network slice is available in the third cell whose physicalcoverage is the same as that of the second cell, because of initiating noregistration procedure again in the second cell, the terminal still cannot access thefirst network slice in a location of the second cell. Based on this solution, whenthe neighboring cell of the first cell accessed by the terminal includes the secondcell, and the third cell whose physical coverage is the same as that of the secondcell exists, when determining that the first network slice is available in the thirdcell, the network device notifies the terminal that the first network slice isavailable in the third cell, and sends the cell identifier of the third cell, so thatwhen still intending to access the first network slice, the terminal may access thethird cell and request to access the first network slice, thereby improving a successrate of accessing the first network slice, and further improving serviceperformance and user experience.
[0052] With reference to the fifth aspect or the sixth aspect, in some possibledesigns, the first network slice is included in a network slice configured for theterminal in a first network.
[0053] With reference to the fifth aspect or the sixth aspect, in some possibledesigns, the first network slice is included in a network slice that the terminalrequests to access in the first cell.
[0054] With reference to the fifth aspect or the sixth aspect, in some possibledesigns, that the network device determines the first network slice includes: Thenetwork device receives, via the first cell, information about a network slice thatthe terminal requests to access, where the information about the network slice thatthe terminal requests to access includes identification information of the firstnetwork slice; and the network device determines a network slice that the terminalis allowed to access, and learns that the first network slice does not belong to thenetwork slice that the terminal is allowed to access in the first cell.
[0055] With reference to the fifth aspect or the sixth aspect, in some possibledesigns, the method further includes: The network device sends referencefrequency information corresponding to the first network slice to the first accessnetwork device.
[0056] According to a seventh aspect, a network slice-based communicationmethod is provided. The method may be performed by a terminal, or may beperformed by a component of a terminal, for example, a processor, a chip, or achip system of the terminal. In this application, an example in which the terminalperforms the method is used for description. The method includes: The terminallearns, from a network device, that a first network slice is available in a secondcell, and initiates a registration procedure for an application corresponding to thefirst network slice. The first network slice does not belong to a network slice thatthe terminal is allowed to access in a first cell, and a registration area of theterminal includes the first cell and the second cell.
[0057] In the current technology, because the first network slice does notbelong 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. Because theregistration area of the terminal includes the first cell and the second cell, even ifthe terminal moves from the first cell to coverage of the second cell, the terminalstill does not re-initiate a registration procedure, and therefore does not request toaccess the first network slice. Based on this solution, the terminal may learn, fromthe network device, that the first network slice is available in the second cell, andtherefore may initiate, when an application of the terminal corresponds to the firstnetwork slice, a registration procedure for the application to request to access thefirst network slice, thereby improving a success rate of accessing the first networkslice, and further improving service performance and user experience.
[0058] In some possible designs, the first network slice is included in aconfigured for the terminal in a first network.
[0059] In some possible designs, the first network slice is included in anetwork slice that the terminal requests to access in the first cell.
[0060] In some possible designs, the method further includes: The terminalreceives a cell identifier from the network device, where the cell identifier is usedfor the second cell.
[0061] In some possible designs, that the terminal initiates the registrationprocedure for the application corresponding to the first network slice includes:The terminal accesses the second cell, and initiates a registration procedure for theapplication via the second cell.
[0062] In some possible designs, that the terminal initiates the registrationprocedure for the application corresponding to the first network slice includes:The terminal determines whether the first network slice is a network slicecorresponding to the application in response to that a context of the terminal doesnot include a session used for the application and does not include a routeselection policy used for the application; and the terminal initiates the registrationprocedure for the application when the first network slice is the network slicecorresponding to the application.
[0063] In some possible designs, the method further includes: The terminalnotifies the network device that the terminal no longer requests to access the firstnetwork slice. Based on this possible design, when the terminal notifies thenetwork device that the terminal no longer requests to access the first networkslice, the network device may delete identification information of the first networkslice stored in the network device. When subsequently serving the terminal, thenetwork device may no longer notify the terminal of a cell that can access the firstnetwork slice, thereby reducing signaling overheads and reducing resource waste.
[0064] In some possible designs, that the terminal notifies the network devicethat the terminal no longer requests to access the first network slice includes:After first duration starting from a first moment, the terminal notifies the networkdevice that the terminal no longer requests to access the first network slice, wherethe first moment is a moment at which the terminal learns, from the networkdevice, that the first network slice is available in the second cell.
[0065] According to an eighth aspect, a communication apparatus is provided,to implement the foregoing methods. The communication apparatus may be thenetwork device in the first aspect to the sixth aspect, an apparatus including thenetwork device, or an apparatus included in the network device, for example, achip; or the communication apparatus may be the terminal in the seventh aspect,an apparatus including the terminal, or an apparatus included in the terminal, forexample, a chip. The communication apparatus includes a corresponding module,unit, or means for implementing the foregoing method. The module, unit, ormeans may be implemented by hardware, software, or hardware executingcorresponding software. The hardware or the software includes one or moremodules or units corresponding to the functions.
[0066] In some possible designs, the communication apparatus may include aprocessing module and a transceiver module. The transceiver module may also bereferred to as a transceiver unit, and is configured to implement a sending functionand / or a receiving function in any one of the foregoing aspects and any one of thepossible implementations of the foregoing aspects. The transceiver module mayinclude a transceiver circuit, a transceiver machine, a transceiver, or acommunication interface. The processing module may be configured toimplement a processing function in any one of the foregoing aspects and any oneof the possible implementations of the foregoing aspects.
[0067] In some possible designs, the transceiver module includes a sendingmodule and a receiving module, respectively configured to implement the sendingfunction and the receiving function in any one of the foregoing aspects and anyone of the possible implementations of the foregoing aspects.
[0068] The communication apparatus provided in the eighth aspect isconfigured to perform any one of the foregoing aspects or any one of the possibleimplementations of the foregoing aspects. For specific details, refer to any one ofthe foregoing aspects or any one of the possible implementations of the foregoingaspects. Details are not described herein again.
[0069] According to a ninth aspect, a communication apparatus is provided,including a processor and a memory. The memory is configured to store computerinstructions. When the processor executes the instructions, the communicationapparatus is enabled to perform the method according to any one of the foregoingaspects. The communication apparatus may be the network device in the firstaspect to the sixth aspect, an apparatus including the network device, or anapparatus included in the network device, for example, a chip; or thecommunication apparatus may be the terminal in the seventh aspect, an apparatusincluding the terminal, or an apparatus included in the terminal, for example, achip.
[0070] According to a tenth aspect, a communication apparatus is provided,including a processor and a communication interface. The communicationinterface is configured to communicate with a module other than thecommunication apparatus; and the processor is configured to execute a computerprogram or instructions, to enable the communication apparatus to perform themethod according to any one of the foregoing aspects. The communicationapparatus may be the network device in the first aspect to the sixth aspect, anapparatus including the network device, or an apparatus included in the networkdevice, for example, a chip; or the communication apparatus may be the terminalin the seventh aspect, an apparatus including the terminal, or an apparatusincluded in the terminal, for example, a chip.
[0071] According to an eleventh aspect, a communication apparatus isprovided, including an interface circuit and a logic circuit. The interface circuit isconfigured to obtain input information and / or output output information; and thelogic circuit is configured to perform the method according to any one of theforegoing aspects or any one of the possible implementations of the foregoingaspects, to perform processing based on input information and / or generate outputinformation. The communication apparatus may be the network device in the firstaspect to the sixth aspect, an apparatus including the network device, or anapparatus included in the network device, for example, a chip; or thecommunication apparatus may be the terminal in the seventh aspect, an apparatusincluding the terminal, or an apparatus included in the terminal, for example, achip.
[0072] When the communication apparatus is the network device in the firstaspect or the second aspect, an apparatus including the network device, or anapparatus included in the network device:
[0073] In some possible designs, the input information may be informationabout a network slice that the terminal requests to access, where the informationabout the network slice that the terminal requests to access includes identificationinformation of a first network slice not supported by a first tracking area andincludes identification information of a second network slice. The performingprocessing based on input information may be: determining a network slice thatthe terminal is allowed to access, or determining a registration area.
[0074] In some possible designs, the output information may be informationabout a registration area, where the registration area excludes a tracking area thatsupports the first network slice and the second network slice, or the registrationarea excludes a tracking area of an access network device that supports the firstnetwork slice and the second network slice.
[0075] When the communication apparatus is the network device in the thirdaspect, an apparatus including the network device, or an apparatus included in thenetwork device:
[0076] In some possible designs, the output information may be informationfor notifying the terminal that the first network slice is available in the second cell.
[0077] In some possible designs, the input information may be informationabout a network slice that the terminal requests to access, where the informationabout the network slice that the terminal requests to access includes identificationinformation of the first network slice. The performing processing based on inputinformation may be: determining a network slice that the terminal is allowed toaccess, or determining that the first network slice does not belong to a networkslice that the terminal is allowed to access in the first cell.
[0078] In some possible designs, the output information may be: identificationinformation of the first network slice.
[0079] In some possible designs, the input information may be informationused by the network device to learn that the first network slice can access theterminal in the second cell. The performing processing based on input informationmay be: learning that the first network slice can access the terminal in the secondcell.
[0080] In some possible designs, the input information may be: a path switchrequest message. The performing processing based on 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 handoverrequired message. The performing processing based on 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: indicationinformation. The performing processing based on input information may be:deleting the identification information of the first network slice based on theindication information.
[0083] When the communication apparatus is the network device in the fifthaspect, an apparatus including the network device, or an apparatus included in thenetwork device:
[0084] In some possible designs, the output information may be informationfor notifying the terminal that the first network slice is available in the second cell,and a cell identifier of the second cell.
[0085] In some possible designs, the input information may be informationabout a network slice that the terminal requests to access, where the informationabout the network slice that the terminal requests to access includes identificationinformation of the first network slice. The performing processing based on inputinformation may be: determining a network slice that the terminal is allowed toaccess, and learning that the first network slice does not belong to a network slicethat the terminal is allowed to access in the first cell.
[0086] In some possible designs, the input information may be: a cellidentifier of the second cell. The performing processing based on inputinformation may be: determining that the first network slice is available in thesecond cell.
[0087] In some possible designs, the input information may be: signal qualityinformation of a neighboring cell of the first cell, where the neighboring cell ofthe first cell includes the second cell. The performing processing based on inputinformation may be: determining, based on the signal quality information of thesecond cell, that the first network slice can access the terminal in the second cell.
[0088] In some possible designs, the output information may be: referencefrequency information corresponding to the first network slice.
[0089] In some possible designs, the input information may be: indicationinformation. The performing processing based on input information may be:deleting the identification information of the first network slice based on theindication information.
[0090] When the communication apparatus may be the terminal in the seventhaspect, an apparatus including the terminal, or an apparatus included in theterminal:
[0091] In some possible designs, the input information may be information forlearning that the first network slice is available in the second cell. The performingprocessing based on input information may be: initiating a registration procedurefor an application corresponding to the first network slice.
[0092] In some possible designs, the input information may be: a cellidentifier, where the cell identifier is used for the second cell. The performingprocessing based on input information may be: accessing the second cell.
[0093] In some possible designs, the output information may be informationfor notifying that the terminal no longer requests to access the first network slice.
[0094] According to a twelfth aspect, a communication apparatus is provided,including at least one processor. The processor is configured to execute acomputer program or instructions stored in a memory, to enable thecommunication apparatus to perform the method according to any one of theforegoing aspects. The memory may be coupled to the processor, or may beindependent of the processor. The communication apparatus may be the networkdevice in the first aspect to the sixth aspect, an apparatus including the networkdevice, or an apparatus included in the network device, for example, a chip; or thecommunication apparatus may be the terminal in the seventh aspect, an apparatusincluding the terminal, or an apparatus included in the terminal, for example, achip.
[0095] According to a thirteenth aspect, a computer-readable storage mediumis provided. The computer-readable storage medium stores instructions, and whenthe instructions are run on a communication apparatus, the communicationapparatus is enabled to perform the method according to any one of the foregoingaspects.
[0096] According to a fourteenth aspect, a computer program productincluding instructions is provided. When the computer program product is run ona communication apparatus, the communication apparatus is enabled to performthe method according to any one of the foregoing aspects.
[0097] According to a fifteenth aspect, a communication apparatus (forexample, the communication apparatus may be a chip or a chip system) isprovided. The communication apparatus includes a processor, configured toimplement the function in any one of the foregoing aspects.
[0098] In some possible designs, the communication apparatus includes thememory, and the memory is configured to store necessary program instructionsand data.
[0099] In some possible designs, when the apparatus is a chip system, theapparatus may include a chip, or may include a chip and another discretecomponent.
[00100] It may be understood that when the communication apparatus providedin any one of the eighth aspect to the fifteenth aspect is the chip, the foregoingsending action / function may be understood as the output information, and theforegoing receiving action / function may be understood as the input information.
[00101] For technical effects brought by any design manner in the eighth aspectto the fifteenth aspect, refer to technical effects brought by different designmanners in the first aspect to the seventh aspect. Details are not described hereinagain.
[00102] According to a sixteenth aspect, a communication system is provided.The communication system includes the network device and the terminalaccording to the foregoing aspects.BRIEF DESCRIPTION OF DRAWINGS
[00103] FIG. 1 is a schematic diagram of a 5G network architecture accordingto this application;
[00104] FIG. 2 is a schematic diagram of an application scenario of a networkslice according to this application;
[00105] FIG. 3 is a schematic diagram of a network slice supported by anaccess network device according to this application;
[00106] FIG. 4 is a schematic diagram of a registration procedure according tothis application;
[00107] FIG. 5 is a schematic diagram of a redirection procedure according tothis application;
[00108] FIG. 6 is a schematic flowchart of Xn handover according to thisapplication;
[00109] FIG. 7 is a schematic flowchart of N2 handover according to thisapplication;
[00110] FIG. 8a is a schematic diagram of a scenario according to thisapplication;
[00111] FIG. 8b is a schematic diagram of a scenario according to thisapplication;
[00112] FIG. 8c is a schematic diagram of a scenario according to thisapplication;
[00113] FIG. 9a is a schematic diagram of a structure of a communicationsystem according to this application;
[00114] FIG. 9b is a schematic diagram of a structure of anothercommunication system according to this application;
[00115] FIG. 9c is a schematic diagram of a structure of anothercommunication system according to this application;
[00116] FIG. 10 is a schematic diagram of a structure of a communicationdevice according to this application;
[00117] FIG. 11 is a schematic flowchart of a network slice-basedcommunication method according to this application;
[00118] FIG. 12 is a schematic flowchart of a network slice-basedcommunication method according to this application;
[00119] FIG. 13 is a schematic flowchart of a network slice-basedcommunication method according to this application;
[00120] FIG. 14 is a schematic flowchart of a network slice-basedcommunication method according to this application;
[00121] FIG. 15 is a schematic flowchart of a network slice-basedcommunication method according to this application;
[00122] FIG. 16 is a schematic flowchart of a network slice-basedcommunication method according to this application;
[00123] FIG. 17 is a schematic flowchart of a network slice-basedcommunication method according to this application;
[00124] FIG. 18 is a schematic flowchart of a network slice-basedcommunication method according to this application;
[00125] FIG. 19 is a schematic interaction flowchart of a network slice-basedcommunication method according to this application;
[00126] FIG. 20 is a schematic interaction flowchart of a network slice-basedcommunication method according to this application;
[00127] FIG. 21 is a schematic interaction flowchart of a network slice-basedcommunication method according to this application;
[00128] FIG. 22 is a schematic interaction flowchart of a network slice-basedcommunication method according to this application;
[00129] FIG. 23 is a schematic interaction flowchart of a network slice-basedcommunication method according to this application;
[00130] FIG. 24 is a schematic interaction flowchart of a network slice-basedcommunication method according to this application;
[00131] FIG. 25 is a schematic interaction flowchart of a network slice-basedcommunication method according to this application;
[00132] FIG. 26 is a schematic interaction flowchart of a network slice-basedcommunication method according to this application;
[00133] FIG. 27 is a schematic interaction flowchart of a network slice-basedcommunication method according to this application;
[00134] FIG. 28 is a schematic interaction flowchart of a network slice-basedcommunication method according to this application;
[00135] FIG. 29 is a schematic interaction flowchart of a network slice-basedcommunication method according to this application;
[00136] FIG. 30 is a schematic interaction flowchart of a network slice-basedcommunication method according to this application;
[00137] FIG. 31 is a schematic diagram of a structure of a network deviceaccording to this application;
[00138] FIG. 32 is a schematic diagram of a structure of a terminal according tothis application; and
[00139] FIG. 33 is a schematic diagram of a structure of a communicationapparatus according to this application.DESCRIPTION OF EMBODIMENTS
[00140] In the description of this application, unless otherwise specified, " / "indicates that associated objects are in an "or" relationship. For example, A / B mayrepresent A or B. "and / or" in this application is merely an association relationshipfor describing an associated object, and indicates that three relationships may exist.For example, A and / or B may represent that only A exists, both A and B exist, andonly B exists, where A and B may be singular or plural. In addition, in thedescriptions of this application, unless otherwise specified, "a plurality of" meanstwo or more than two. "At least one of the following items (pieces)" or similarexpressions refer to any combination of these items, including any combination ofsingular items (pieces) or plural items (pieces). For example, at least one of a, b,or c may represent: a, b, c, a and b, a and c, b and c, and a and b and c, where a, b,and c may be singular or plural. In addition, to clearly describe the technicalsolutions in embodiments of this application, terms such as "first" and "second"are used in embodiments of this application to distinguish between same items orsimilar items that provide basically same functions or purposes. A person skilledin the art may understand that the terms such as "first" and "second" do not limit aquantity or an execution sequence, and the terms such as "first" and "second" donot indicate a definite difference.
[00141] It should be noted that in this application, the terms such as "example"or "for example" are used to represent giving an example, an illustration, or adescription. Any embodiment or design scheme described as an "example" or "forexample" in this application should not be explained as being more preferred orhaving more advantages than another embodiment or design scheme. Exactly, useof the terms such as "example" or "for example" is intended to present a relativeconcept in a specific manner.
[00142] To facilitate understanding of the technical solutions in embodimentsof this application, the following briefly describes related technologies in thisapplication.
[00143] 1. 5th generation (5G) network architecture:
[00144] A 5G network architecture defined in the 3rd Generation PartnershipProject (3GPP) TS 23.501 standard is mainly divided into two parts: an accessnetwork (AN) and a core network.
[00145] The access network may include a radio access network (RAN), and isconfigured to implement a function related to radio access.
[00146] The core network mainly includes the following key logical networkelements: an access and mobility management function (AMF) network element,a session management function (SMF) network element, a user plane function(UPF) network element, a policy control function network element, and a unifieddata management (UDM) network element; and may additionally further includean authentication server function (AUSF) network element, a network sliceselection function (NSSF) network element, an application function (AF) networkelement, and the like.
[00147] FIG. 1 is a schematic diagram of a 5G network architecture. A terminalmay be user equipment (UE), for example, a mobile phone or an Internet ofThings terminal.
[00148] DN is a data network (DN), and is mainly configured to provide a datatransmission service for a user, for example, an Internet Protocol (IP) multimediaservice (IMS).
[00149] Access network devices that provide radio access for the user isdeployed in the RAN, and include but are not limited to an evolved NodeB(NodeB, eNB, or e-NodeB, evolved NodeB), wireless fidelity (Wi-Fi) access point(AP), and the like.
[00150] An AMF network element is mainly responsible for mobilitymanagement in a mobile network, such as user location update, user networkregistration, and user handover.
[00151] An SMF network element is mainly responsible for sessionmanagement in the mobile network, for example, session establishment,modification, and release. Specific functions include allocating an IP address tothe user, selecting a UPF that provides a packet forwarding function, and the like.
[00152] A PCF network element is mainly responsible for providing policiessuch as a quality of service (QoS) policy and a slice selection policy for the AMFand the SMF.
[00153] A UDM network element is mainly responsible for storing user datasuch as subscription information and authentication / authorization information.
[00154] An AF network element is mainly responsible for providing servicerequirements for a 3GPP network, for example, affecting a service route andinteracting with the PCF network element to perform policy control.
[00155] A UPF network element is mainly responsible for processing, forexample, forwarding and charging a user packet.
[00156] The terminal accesses the DN by establishing a protocol data unit(PDU) session from the terminal to the RAN, the UPF, and the DN.
[00157] An AUSF network element is mainly responsible for providing aterminal authentication service for the AMF network element.
[00158] An NSSF network element is mainly responsible for selecting anetwork slice that serves the terminal.
[00159] In addition, refer to FIG. 1. Nx represents a logical interface or aservice-based interface between two network elements, and is used forcommunication between network elements. For example, N1 is an interfacebetween the terminal and the AMF network element. N2 is an interface betweenthe access network device and the AMF network element. N3 is an interfacebetween the access network device and the UPF network element. N9 is aninterface between different UPF network elements. N6 is an interface between theUPF network element and the DN. N4 is an interface between the UPF networkelement and the SMF network element. N11 is an interface between the AMFnetwork element and the SMF network element. N7 is an interface between theSMF network element and the PCF network element. N5 is an interface betweenthe PCF network element and the AF network element. N14 is an interfacebetween different AMF network elements. N15 is an interface between the AMFnetwork element and the PCF network element. N22 is an interface between theNSSF network element and the AMF network element. N12 is an interfacebetween the AUSF network element and the AMF network element. N8 is aninterface between the UDM network element and the AMF network element. N13is an interface between the AUSF network element and the UDM network element.
[00160] 2. Network slice (or Slice for short):
[00161] In the 5G era, hundreds of billions of Internet of Things devices areconnected to the network. Different types of application scenarios have differentnetwork requirements, and some network requirements even conflict with eachother. If a single network is used to provide services for different types ofapplication scenarios, a network architecture is extremely complex, and networkmanagement efficiency and resource utilization efficiency are low.
[00162] A 5G network slicing technology provides mutually isolated networkenvironments for different application scenarios in a manner of virtualizingindependent logical networks on a same network infrastructure, so that networkfunctions and features of the different application scenarios can be customizedbased on respective requirements, and QoS requirements of different services canbe effectively ensured.
[00163] An objective of network slicing is to organically combine terminals,access network resources, core network resources, and network O&M andmanagement systems to provide different business scenarios or service types withcomplete networks that can be independently operated and maintained andmutually isolated.
[00164] Various scenarios pose different requirements for a 3GPP ecosystem:charging, policy, security, mobility, and the like. 3GPP emphasizes that networkslices do not affect each other. For example, a large quantity of sudden meterreading services should not affect normal mobile broadband services. To satisfydiversified requirements and isolate slices, independent management and O&M ofservices need to be performed, and customized service functions and analysiscapabilities need to be provided. Instances of different types of services aredeployed on different network slices, and different instances of a same servicetype may also be deployed on different network slices.
[00165] For example, as shown in FIG. 2, a mobile broadband service isprovided for a handheld terminal or the like via a mobile broadband (MBB) slice.A service is provided for a large quantity of meter reading services via a massivemachine type communications (mMTC) slice. A service is provided for a vehicleto everything (V2X) service via a critical MTC slice.
[00166] Details are as follows:
[00167] A network slice refers to a logical network that can provide specificnetwork capabilities and network characteristics.
[00168] A network slice instance refers to a group of network function entitiesand required resources that form a network slice, for example, computing, storage,and network resources.
[00169] Single network slice selection assistance information (S-NSSAI) maybe used as identification information of a network slice, to differentiate betweendifferent network slices.
[00170] The S-NSSAI may include slice / service type (SST) information. TheSST information describes expected network slice behavior, for example, is usedto describe a slice type / service type of a network slice. This is not limited.
[00171] For example, slice / service types (SST) of network slices may include:enhanced mobile broadband (eMBB), ultra-reliable low-latency communications(URLLC), massive Internet of Things (MIoT), vehicle to everything (V2X), andthe like. This is not limited.
[00172] Optionally, the S-NSSAI further includes slice differentiator (orreferred to as a slice differentiation identifier) (SD) information. The SDinformation is supplementary information of the SST information, and is used todifferentiate between different network slices with a same SST characteristic. Thatis to say, when the SST information points to a plurality of network slices, the SDinformation may assist in corresponding to a unique network slice.
[00173] In addition, a group of S-NSSAI may be identified via network sliceselection assistance information (NSSAI). That is to say, the NSSAI is a set of onegroup of S-NSSAI.
[00174] When being classified based on different types, NSSAI includessubscribed NSSAI, configured NSSAI, requested NSSAI, allowed NSSAI,rejected NSSAI, or pending NSSAI.
[00175] Examples are as follows:
[00176] Subscribed NSSAI: The subscribed NSSAI is unique to a home publicland mobile network PLMN (HPLMN), and refers to subscribed NSSAI thatallows a terminal to access.
[00177] Configured NSSAI: It is NSSAI of one or more PLMNs defined in theterminal. The configured NSSAI is determined by a serving PLMN based on acapability of the serving PLMN to support a network slice and a network slice towhich the terminal subscribes, and then sent to the terminal via a registrationaccept message in a registration procedure. For configured NSSAI, a PLMN orstand-alone non-public network (SNPN) is used as a granularity. DifferentPLMNs or SNPNs can correspond to different pieces of configured NSSAI.
[00178] Requested NSSAI: It refers to NSSAI provided by the terminal to theserving PLMN in the registration procedure. When the terminal stores theconfigured NSSAI corresponding to the serving PLMN, the requested NSSAIincludes S-NSSAI in the configured NSSAI corresponding to the serving PLMN.When the terminal does not store the configured NSSAI corresponding to theserving PLMN, for example, the terminal accesses for the first time or deletes theconfigured NSSAI corresponding to the serving PLMN for a reason such asrestarting, the requested NSSAI may include S-NSSAI in default configuredNSSAI, and the Default configured NSSAI is configured by the HPLMN. In thisscenario, the requested NSSAI may include S-NSSAI that does not belong to theconfigured NSSAI corresponding to the serving PLMN.
[00179] Allowed NSSAI: It refers to NSSAI provided by the serving PLMN in,for example, a registration procedure, and indicates a network slice that is of theserving PLMN, that the terminal is allowed to access in a current registration area(RA), and that is in a network slice corresponding to the requested NSSAI.
[00180] Rejected NSSAI: It refers to NSSAI provided by the serving PLMN in,for example, a registration procedure, and indicates a network slice that theterminal is rejected to access in a current RA and that is in a network slicecorresponding to the requested NSSAI.
[00181] Network slices corresponding to the rejected NSSAI may be classifiedinto the following two types: one type of network slices that are not allowed to beaccessed in the current RA but can be accessed in the serving PLMN; and theother type of network slices that are not allowed to be accessed in the entireserving PLMN.
[00182] Pending NSSAI: It is NSSAI provided by the serving PLMN in aregistration procedure, indicating S-NSSAI for which a network slice-specificauthentication and authorization procedure is pending. For details, refer to adefinition in the 3GPP 23.501 standard. Details are not described herein again.
[00183] 3. Capability of an access network to support network slices:
[00184] A capability of a RAN to support a network slice is divided by using atracking area (TA) as a granularity. One TA may support one or more networkslices, cells in a same TA support a same network slice, and one cell supports onlyone frequency band.
[00185] For example, it is assumed that an access network device supports afrequency (FR) 1 (FR 1) and a frequency 2 (FR 2). Because each cell supportsonly one frequency band, FR 1 and FR 2 are frequencies supported by differentcells. For example, FR 1 is a frequency supported by a cell 1, and FR 2 is afrequency supported by a cell 2. Further, it is assumed that the cell 1 supports anetwork slice 1 (corresponding to S-NSSAI 1), and the cell 2 supports a networkslice 2 (corresponding to S-NSSAI 2). Because cells in a same TA support a samenetwork slice, the cell 1 and the cell 2 are cells in different TAs.
[00186] In other words, as shown in FIG. 3, a cell 1 in a TA 1 supports anetwork slice 1 on an FR 1, and a cell 2 in a TA 2 supports a network slice 2 on anFR 2. In addition, it should be noted that physical coverage of the cell 1 andphysical coverage of the cell 2 completely or partially overlap.
[00187] The AMF network element perceives a network slice supported by theRAN also by using a TA as a granularity. When establishing or updating an N2connection to the AMF network element, the access network device may report, tothe AMF network element, S-NSSAI supported by each TA of the access networkdevice.
[00188] For example, the access network device may report, in a supported TAlist information element, a TA supported by the access network device; and report,in a tracking area identity (TAI) slice support list (TAI slice support list)information element, S-NSSAI supported by each TA in each PLMN or SNPN.
[00189] 4. Slice selection:
[00190] When network slices are deployed, a network slice may be selected ina registration procedure. For example, the terminal requests a network slice to beaccessed during registration, and the core network feeds back, to the terminal,allowed NSSAI that can be accessed by the terminal. When subsequentlyperforming service transmission, the terminal selects S-NSSAI from the allowedNSSAI, and establishes a session via a network slice corresponding to the SNSSAI.
[00191] Refer to FIG. 4, which shows a partial procedure related to sliceselection in a registration procedure, and the partial procedure specificallyincludes the following steps:
[00192] S401: A terminal sends a registration request to an access networkdevice. Correspondingly, the access network device receives the registrationrequest from the terminal.
[00193] The registration request includes NSSAI requested by the terminal,that is, requested NSSAI.
[00194] S402: The access network device forwards the NSSAI requested by theterminal to an initial AMF network element. Correspondingly, the initial AMFnetwork element receives the NSSAI that is requested by the terminal and that isforwarded by the access network device.
[00195] The access network device may forward, via an N2 message, theNSSAI requested by the terminal to the initial AMF network element.
[00196] S403: The initial AMF network element initiates a request to a UDMnetwork element, to obtain subscribed NSSAI of the terminal.
[00197] S404: When being incapable of determining allowed NSSAI of theterminal, the initial AMF network element requests slice selection from an NSSFnetwork element, and sends the NSSAI requested by the terminal, the NSSAI towhich the terminal subscribes, and location information of the terminal to theNSSF network element.
[00198] S405: The NSSF network element returns the allowed NSSAI of theterminal to the initial AMF network element.
[00199] In addition, if the AMF network element needs to be switched, theNSSF network element further returns, to the initial AMF network element, atarget AMF set (or list) and an identifier (ID) of a network repository function(NRF) network element corresponding to a target AMF network element.
[00200] S406: If the AMF network element needs to be switched, the initialAMF network element queries the corresponding NRF network element forinformation about the target AMF network element based on the NRF ID returnedby the NSSF network element.
[00201] S407: The initial AMF network element sends an AMF relocationrequest to the target AMF network element. The AMF relocation request includesthe allowed NSSAI that is of the terminal and that is returned by the NSSFnetwork element.
[00202] In a possible implementation, the initial AMF network element maysend the AMF relocation request to the target AMF network element via aninterface between the AMF network elements, for example, as shown in S407a.
[00203] In another possible implementation, the initial AMF network elementmay alternatively forward the AMF relocation request to the target AMF networkelement via the access network device.
[00204] For example, as shown in S407b, the initial AMF network elementsends an AMF relocation request to the access network device. In addition to theallowed NSSAI of the terminal returned by the NSSF network element, the AMFrelocation request further includes information about the target AMF networkelement. After receiving the AMF relocation request from the initial AMF networkelement, the access network device forwards the AMF relocation request to thetarget AMF network element based on the information about the target AMFnetwork element included in the AMF relocation request.
[00205] S408: The target AMF network element sends the allowed NSSAI ofthe terminal to the access network device.
[00206] S409: The access network device feeds back the allowed NSSAI of theterminal and a UE route selection policy (URSP) to the terminal.
[00207] The URSP is generated by a PCF in the registration procedure.
[00208] So far, the terminal may learn a network slice that can be subsequentlyaccessed and a URSP corresponding to the network slice.
[00209] In addition, based on the current 23.502 protocol, triggering scenariosof the registration procedure mainly include: (1): initial registration of theterminal with the core network; (2): mobility registration update caused bymovement of the terminal to a TA outside a registration area (RA); (3):registration update caused by capability change of the terminal; (4): periodicregistration update of the terminal in an inactive state; and (5): emergencyregistration. In other words, the terminal may select a network slice in theforegoing five scenarios. In other words, in the current technology, in otherscenarios than the foregoing five scenarios, the terminal does not initiate aregistration procedure.
[00210] 5. Redirection:
[00211] This application mainly describes a process in which a terminalinitiates a registration request in a cell in a TA 1 of an access network device, andthe terminal is redirected from the cell in the TA 1 to a cell in a TA 2 when the TA1 does not support a network slice requested by the terminal but the TA 2 of theaccess network device supports the network slice requested by the terminal. Referto FIG. 5. The process mainly includes the following steps:
[00212] S501: A terminal sends a registration request to an AMF networkelement via an access network device. Correspondingly, the AMF networkelement receives the registration request from the terminal via the access networkdevice.
[00213] That the terminal sends the registration request to the AMF networkelement via the access network device includes: The terminal sends theregistration request to the AMF network element via a cell 1 of the access networkdevice, where the cell 1 is a cell in a TA 1 of the access network device.
[00214] The registration request includes NSSAI requested by the terminal,that is, requested NSSAI.
[00215] S502: The AMF network element and an NSSAI network elementperform network slice selection, and determine allowed NSSAI of the terminal.For details, refer to steps S402 to S405, and details are not described herein again.
[00216] A description is made through an example in which first S-NSSAIincluded in the requested NSSAI does not belong to the allowed NSSAI, that is, anetwork slice corresponding to the first S-NSSAI does not belong to a networkslice that a serving PLMN allows the terminal to access in the TA 1, in otherwords, the TA 1 does not support the network slice corresponding to the first SNSSAI.In other words, when the terminal sends the registration request to theAMF network element via the cell 1 of the access network device, the first SNSSAIbelongs to rejected NSSAI.
[00217] In addition, in addition to the allowed NSSAI, at least one of therejected NSSAI and configured NSSAI of the terminal is further determined.
[00218] S503: The AMF network element sends an N2 message to the accessnetwork device, where the message includes the allowed NSSAI of the terminal.
[00219] Further, at least one of the rejected NSSAI and the configured NSSAImay be further included.
[00220] S504: The access network device sends a registration accept messageto the terminal, where the message includes the allowed NSSAI of the terminal.
[00221] Further, at least one of the rejected NSSAI and the configured NSSAImay be further included.
[00222] S505: The access network device determines an access frequency ofthe terminal based on information learned from the AMF network element.
[00223] For example, if a piece of S-NSSAI included in the requested NSSAIis not supported by the current TA, in addition to the allowed NSSAI and theconfigured NSSAI to the access network device, the AMF network elementfurther provides the rejected NSSAI to the access network device. In this way, theaccess network device can redirect or steer the terminal to an access frequencythat supports the S-NSSAI. After receiving the rejected NSSAI from the AMFnetwork element, the access network device may perform step S505 to determinethe access frequency of the terminal, so as to determine a frequency of aneighboring cell.
[00224] S506: The access network device sends a radio resource control (RRC)connection release message to the terminal, where the message includes thefrequency of the neighboring cell, an identifier of a network slice supported by theneighboring cell, and a cell reselection priority of the neighboring cell.
[00225] S507: The terminal performs RRC connection release to enter an RRCidle state, and performs cell reselection based on the cell reselection priorityconfigured by the access network device.
[00226] A description is made through an example in which the terminalaccesses a cell 2 in a TA 2 via cell reselection, the TA 2 does not belong to an RAin which the TA is located, and the TA 2 supports the network slice correspondingto the first S-NSSAI.
[00227] S508: The terminal re-initiates a registration procedure, and sends aregistration request to the AMF network element via the cell 2 of the accessnetwork device.
[00228] The registration request may include the first S-NSSAI.
[00229] S509: It is the same as step S502.
[00230] S510: The AMF network element sends a registration accept messageto the terminal via the cell 2 of the access network device, where the messageincludes the allowed NSSAI of the terminal, and the allowed NSSAI may includethe first S-NSSAI. In other words, when the terminal sends the registration requestto the AMF network element via the cell 2 of the access network device, the firstS-NSSAI belongs to the allowed NSSAI.
[00231] So far, the terminal may access, via the cell 2, the network slicecorresponding to the first S-NSSAI, and use a service provided by the networkslice.
[00232] 6. Xn Handover:
[00233] An Xn interface is an interface between access network devices (that is,between a source access network device from which handover is made and atarget access network device to which handover is made). When the Xn interfaceor an Xn connection exists between the access network devices, an example inwhich a terminal is handed over from the source access network device to thetarget access network device is used, and an Xn handover procedure is shown inFIG. 6 and specifically includes:
[00234] S600: An AMF network element delivers mobility control informationto the source access network device and the target access network device.
[00235] S601: The terminal reports measurement information to the sourceaccess network device.
[00236] For example, the measurement information includes reference signalreceived power (RSRP).
[00237] S602: The source access network device determines, based on themeasurement information reported by the terminal and a local policy, to hand overthe terminal to the target access network device in an Xn handover manner.
[00238] S603: The source access network device sends a handover requestmessage to the target access network device.
[00239] S604: The target access network device determines whether to acceptthe handover of the terminal. When the target access network device accepts thehandover of the terminal, the following steps continue to be performed.
[00240] S605: The target access network device sends a handover requestacknowledge message to the source access network device, to indicate that thehandover of the terminal is accepted. The handover request acknowledge messagemay further include a handover command, instructing the terminal to access thetarget access network device via a random access procedure.
[00241] S606: The source access network device sends a radio resource control(RRC) reconfiguration to the terminal, to indicate the terminal to release aconnection to the source access network device and attempt to access the targetaccess network device via a random access procedure.
[00242] Step S600 to step S606 may be a handover preparation phase. After thehandover preparation phase is completed, a handover execution phase isperformed. The handover execution phase mainly includes step S607 to step S609.
[00243] S607: The source access network device sends an SN status to thetarget access network device via a sequence number (SN) status transfer message,to perform packet data convergence protocol (PDCP) SN synchronization.
[00244] S608: The terminal interrupts the connection to the source accessnetwork device, and establishes a connection to the target access network devicevia a random access procedure.
[00245] In a process in which the terminal establishes a connection to the targetaccess network device, the source access network device forwards, to the targetaccess network device via a forwarding tunnel between the source access networkdevice and the target access network device, user data that is sent by a UPFnetwork element to the source access network device, and the target accessnetwork device buffers the forwarded user data.
[00246] S609: The terminal completes the random access procedure,establishes an air interface connection to the target access network device, andcompletes handover of an access network. Then, the target access network devicestarts to send the buffered data received from the source access network device.
[00247] So far, the handover of the access network is completed, and pathswitch of a core network to be subsequently performed mainly includes thefollowing steps:
[00248] S610: The target access network device sends a path switch request tothe AMF network element, to notify the AMF network element that the terminalhas been switched, where the path switch request may include a session that needsto be switched and AN tunnel port information for establishing a user planeconnection. Further, the path switch request may further include locationinformation of the terminal, for example, a current TAI of the terminal.
[00249] S611: The AMF network element, an SMF network element, the UPFnetwork element, and the like perform path switch of the UPF, and simultaneouslythe UPF network element delivers an end marker from an original path, to indicatethat transmission of data on the original path is completed and new data isdelivered from a path to which the switch is made.
[00250] S612: The AMF network element sends a path switch requestacknowledge message to the target access network device, to feed back a pathswitch status.
[00251] S613: The target access network device sends a UE context releasemessage to the source access network device, to indicate the source accessnetwork device to release a context of the terminal.
[00252] 7. N2 Handover:
[00253] The N2 handover is applicable to a scenario in which no Xn interfaceexists or no Xn connection exists between access network devices. An example inwhich a terminal is handed over from the source access network device to thetarget access network device is used, and an N2 handover procedure is shown inFIG. 7 and specifically includes:
[00254] S700: The source access network device determines to trigger N2handover.
[00255] The source access network device finds, by querying local information,that no Xn connection exists between the source access network device and thetarget access network device, and a control plane message of the handover needsto be forwarded via an N2 interface.
[00256] S701: The source access network device sends a handover requiredmessage to a source AMF network element.
[00257] The handover required message may include a target identifier (TargetID) and a to-be-handed-over session identifier set. The target identifier mayinclude an identifier of the target access network device and a target TAI, and thetarget TAI corresponds to a target TA that the terminal intends to access.
[00258] S702: The source AMF network element selects a target AMF networkelement.
[00259] If the target access network device is not within a service range of thesource AMF network element, the source AMF network element selects, based onidentification information of the target access network device, the target AMFnetwork element serving the target access network device.
[00260] S703: The source AMF network element sends a create UE contextrequest message to the target AMF network element, where the message mayinclude the target identifier and the to-be-handed-over session identifier set.
[00261] The create UE context request message may be, for example, anNamf_Communication_CreateUEContext Request message that is a type of N2message.
[00262] S704: The target AMF network element sends a session managementrequest message 1 to an SMF network element, where the message may includethe target identifier and the to-be-handed-over session identifier set.
[00263] The session management request message 1 may be, for example, anNamf_PDUSession_UpdateSMContext Request message that is a type of N2session management message.
[00264] S705: The SMF network element controls establishment of an uplinktunnel between a PDU session anchor (PSA) and a target UPF network element.
[00265] S706: The SMF network element sends a session managementresponse message 1 to the target AMF network element, where the messageincludes a session for which the target UPF network element accepts the handover,and QoS flow information.
[00266] The session management response message 1 may be, for example, anNamf_PDUSession_UpdateSMContext Response message.
[00267] S707: The target AMF network element monitors a sessionmanagement response message corresponding to a session management requestmessage sent to each SMF network element, and starts to send a handover requestto the target access network device after each session management responsemessage is received or a maximum waiting time is reached.
[00268] S708: The target AMF network element sends the handover request tothe target access network device, where the handover request includes the sessionfor which the target UPF network element accepts the handover, and the QoS flowinformation.
[00269] S709: The target access network device feeds back a handover requestacknowledge message to the target AMF network element. The handover requestacknowledge message includes a session for which the target access networkdevice accepts the handover, and QoS flow information.
[00270] S710: The target AMF network element sends a session managementrequest message 2 to the SMF network element based on a session status fed backby the target access network device, to feed back a session for which handover isaccepted by both the target access network device and the target UPF networkelement, and a QoS flow list.
[00271] The session management request message 2 may be, for example, anNamf_PDUSession_UpdateSMContext Request message.
[00272] S711: The SMF network element sends a session managementresponse message 2 to the target AMF network element based on a session statusfed back by the target AMF network element, where the message includesinformation about a QoS flow granularity.
[00273] The session management response message 2 may be, for example, anNamf_PDUSession_UpdateSMContext Response message.
[00274] S712: The target AMF network element sends a create UE contextresponse message to the source AMF network element, where the messageincludes a list of rejected sessions and corresponding rejection reasons.
[00275] The create UE context response message may be, for example, anNamf_Communication_CreateUEContext Response message.
[00276] S713: Continue to perform an N2 handover execution phase. Fordetails, refer to descriptions in an existing protocol. Details are not describedherein again.
[00277] The foregoing mainly describes a network slice and a network sliceselection process. In actual application, the following scenarios may exist: In aregistration procedure, because a TA in which a terminal is currently located doesnot support a network slice that the terminal intends to access, the terminal cannotaccess the network slice in this registration procedure. Subsequently, even if theterminal moves to a TA that supports the network slice, the terminal is still unableto normally access the network slice.
[00278] In a possible scenario, as shown in FIG. 8a, it is assumed that a TA 1 ofan access network device 1 supports a network slice 2 (corresponding to S-NSSAI2) on an FR 2; a TA 2 of an access network device 2 supports the network slice 2on the FR 2, a TA 3 of the access network device 2 supports a network slice 1(corresponding to S-NSSAI 1) on an FR 1, and physical coverage of the TA 2 andphysical coverage of the TA 3 completely or partially overlap; and a TA 4 of anaccess network device 3 supports the network slice 1 on the FR 1.
[00279] Currently, when dividing an RA corresponding to a terminal, an AMFnetwork element usually groups TAs supporting allowed NSSAI into a same RA.For example, the terminal requests access to the S-NSSAI 1 and the S-NSSAI 2via the access network device 1 in the TA 1, the allowed NSSAI determined on anetwork side is the S-NSSAI 2, and both the TA 1 and the TA 2 support the S10NSSAI 2. Therefore, the AMF network element groups the TA 1 and the TA 2 intoan RA 1.
[00280] For example, the terminal accesses a network via the access networkdevice 1 and performs a registration procedure, and the terminal intends to accessthe network slice 1. In a location of the TA 1, because the TA 1 of the accessnetwork device 1 does not support the network slice 1, the terminal cannot accessthe network slice 1, and finally access the network slice 2.
[00281] Subsequently, when the terminal moves into a service range of the TA2 of the access network device 2, because the TA 2 is grouped into a range of theRA 1, and the terminal does not move out of the range of the RA 1, the terminaldoes not re-initiate a registration procedure based on the foregoing five scenariosof triggering a registration procedure. Therefore, even if the TA 3 whose physicalcoverage is the same as that of the TA 2 can support the network slice 1, that is,even if the TA 3 that can support the network slice 1 exists in a current location ofthe terminal, the terminal still cannot access the network slice 1.
[00282] As the terminal moves, when the terminal moves into a service rangeof the TA 4 of the access network device 3, because of moving out of the range ofthe RA 1, the terminal may re-initiate a registration procedure to access thenetwork slice 1.
[00283] In other words, in the scenario shown in FIG. 8a, when the terminalmoves into the TA 2 that supports the network slice 1, the terminal still cannotnormally access the network slice 1. The terminal can normally access thenetwork slice 1 only when moving to a location of the TA 4, which affects userexperience and service performance.
[00284] In another possible scenario, as shown in FIG. 8b, it is assumed that aTA 1 of an access network device 1 supports a network slice 2 (corresponding toS-NSSAI 2); a TA 2 of an access network device 2 supports the network slice 2and a network slice 1 (corresponding to S-NSSAI 1); and a TA 3 of an accessnetwork device 3 supports the network slice 1.
[00285] When dividing an RA corresponding to a terminal, an AMF networkelement usually groups TAs supporting allowed NSSAI into a same RA. Similarly,for example, the terminal requests access to the S-NSSAI 1 and the S-NSSAI 2via the access network device 1 in the TA 1, the allowed NSSAI determined on anetwork side is the S-NSSAI 2, and both the TA 1 and the TA 2 support the SNSSAI2. Therefore, the AMF network element groups the TA 1 and the TA 2 intoan RA 1. Based on grouping of the RA 1, when moving into a service range of theTA 2 of the access network device 2, the terminal still cannot access the networkslice 1. For specific analysis, refer to the scenario shown in FIG. 8a. Details arenot described herein again.
[00286] In still another possible scenario, as shown in FIG. 8c, it is assumedthat a cell in a TA 1 of an access network device 1 supports a network slice 2(corresponding to S-NSSAI 2) on an FR 2; and a cell in a TA 2 of the accessnetwork device 1 supports a network slice 1 (corresponding to S-NSSAI 1) on anFR 1, and there is a non-overlapping area between physical coverage of the TA 1and that of the TA 2.
[00287] For example, the terminal accesses a network via the cell in the TA 1of the access network device 1 and performs a registration procedure, the terminalintends to access the network slice 1, and the terminal is not within the physicalcoverage of the TA 2. Because the TA 1 of the access network device 1 does notsupport the network slice 1, the terminal cannot access the network slice 1, andfinally access the network slice 2.
[00288] When the terminal enters the coverage of the TA 2, and is handed overfrom the cell in the TA 1 to the cell in the TA 2, cell handover within the accessnetwork device, or intra-eNodeB handover for short, occurs. In this scenario, evenif the cell in the TA 2 supports the network slice 1, the terminal device may still beunable to access the network slice 1 based on an existing procedure.
[00289] Based on this, this application provides a network slice-basedcommunication method, to reduce a probability that a terminal cannot normallyaccess a network slice, improve a network slice access success rate, and furtherimprove service performance and user experience.
[00290] The following describes the technical solutions provided inembodiments of this application with reference to the accompanying drawings.
[00291] The network slice-based communication method provided inembodiments of this application may be used in any communication system. Thecommunication system may be a 3GPP communication system, for example, a 5Gmobile communication system or a new radio (NR) system, an NR V2X system,or another next-generation communication system, or may be a non-3GPPcommunication system. This is not limited.
[00292] The network slice-based communication method provided inembodiments of this application may be applied to various communicationscenarios, for example, may be applied to one or more of the followingcommunication scenarios: enhanced mobile broadband (eMBB), ultra-reliable lowlatency communication (URLLC), machine type communication (MTC), massivemachine type communications (mMTC), device to device (D2D), vehicle toeverything (V2X), vehicle to vehicle (V2V), Internet of Things (IoT), and the like.
[00293] The following uses FIG. 9a as an example to describe a communicationsystem provided in an embodiment of this application. As shown in FIG. 9a, thecommunication system may include at least one terminal and at least one networkdevice.
[00294] In some embodiments, the network device in this application is amobility management device. In this scenario, the communication system mayfurther include a first access network device. Further, the communication systemfurther includes a second access network device.
[00295] In some other embodiments, the network device in this application is afirst access network device. In this scenario, the communication system mayfurther include a mobility management device. Further, the communicationsystem further includes a second access network device.
[00296] In still some embodiments, the network device in this application is asecond access network device. In this scenario, the communication system mayfurther include a mobility management device and a first access network device.
[00297] In other words, as shown in FIG. 9b, a communication system providedin this application may include one or more of a terminal, a first access networkdevice, a second access network device, and a mobility management device.
[00298] Optionally, as shown in FIG. 9c, a communication system may furtherinclude one or more of a session management network element, a policy controlnetwork element, a user plane network element, an application function networkelement, a slice selection function network element, a unified data managementnetwork element, or a data network (DN) connected to an operator network.
[00299] In this application, after accessing a network, the terminal mayestablish a protocol data unit (PDU) session, access an external data network DNvia the PDU session, and interact with an application server deployed in the DN.As shown in FIG. 9c, based on different DNs accessed by the terminal, thenetwork may select, based on a network policy, a user plane network element thataccesses the DN as a PDU session anchor, that is, a protocol data unit sessionanchor (PSA), to access the application server via an N6 interface of the PSA.Application servers of a same application may be deployed in a plurality oflocations. The network can select, based on an access location of the terminal, aPSA that is close to the terminal and that can support the terminal in accessing theDN, to reduce route recurvation and network delay.
[00300] The terminal in this application may be a device configured toimplement a wireless communication function, for example, a terminal or a chipthat can be used in a terminal. The terminal may be deployed on land, includingindoors or outdoors, handheld, or vehicle-mounted; may also be deployed on thewater surface (such as a ship); and may also be deployed in the air (for example,on aircraft, a balloon, and a satellite). The terminal may be user equipment (UE),an access terminal, a terminal unit, a terminal station, a mobile station, a remotestation, a remote terminal, a mobile device, a wireless communication device, aterminal agent, a terminal apparatus, or the like in a 5G network or a futureevolved public land mobile network (PLMN). The access terminal may be acellular phone, a cordless phone, a session initiation protocol (SIP) phone, awireless local loop (WLL) station, a personal digital assistant (PDA), a handhelddevice having a wireless communication function, a computing device or anotherprocessing device connected to a wireless modem, a vehicle-mounted device, awearable device, a virtual reality (VR) terminal device, an augmented reality (AR)terminal device, a wireless terminal in industrial control, a wireless terminal inself-driving, a wireless terminal in remote medical, a wireless terminal in a smartgrid, a wireless terminal in transportation safety, a wireless terminal in a smart city,a wireless terminal in a smart home, or the like. The terminal may be mobile orfixed.
[00301] The access network device in this application is a device forconnecting a terminal to a wireless network, and may be an evolved NodeB(evolved NodeB, eNB, or eNodeB) in LTE; or a base station in a 5G network or afuture evolved public land mobile network (PLMN), a broadband networkgateway (BNG), an aggregation switch, or a non-3GPP access device.Alternatively, the access network device in embodiments of this application maybe a radio controller in a cloud radio access network (CRAN); or a transmissionand reception point (TRP), a device including a TRP, or the like. This is notspecifically limited in embodiments of this application. Optionally, the basestation in embodiments of this application may include base stations in variousforms, for example, a macro base station, a micro base station (also referred to asa small cell), a relay station, or an access point. This is not specifically limited inembodiments of this application.
[00302] The mobility management device in this application is mainly used forattachment, mobility management, and tracking area update procedures of aterminal in a mobile network. The mobility management device terminates a nonaccessstratum (NAS) message, completes registration management, connectionmanagement, reachability management, allocation of a tracking area list (TA list),mobility management, and the like, and transparently routes a sessionmanagement (SM) message to the session management network element. In a 5Gcommunication system, the mobility management network element may be anAMF. In future communication such as 6th generation (6G) communication, themobility management network element may still be an AMF network element orhave another name. This is not limited in embodiments of this application.
[00303] The slice selection function network element in this application isconfigured to select a network slice for a terminal, and so on. In a 5Gcommunication system, the slice selection function network element may be anNSSF network element. In future communication such as 6G communication, thenetwork slice selection function network element may still be an NSSF networkelement or have another name. This is not limited in embodiments of thisapplication.
[00304] The policy control network element in this application includes a usersubscription data management function, a policy control function, a chargingpolicy control function, a QoS control function, and the like, and is configured toguide a unified policy framework of network behavior, provide policy ruleinformation for a control plane function network element (for example, an AMFnetwork element), and so on. In a 5G communication system, the policy controlnetwork element may be a PCF network element. In future communication suchas 6G communication, the policy control function network element may still be aPCF network element or have another name. This is not limited in embodimentsof this application.
[00305] The 5G communication system is used as an example. A schematicdiagram of a possible network architecture corresponding to the communicationsystem shown in FIG. 9c to which embodiments of this application are applicablemay be shown in FIG. 1.
[00306] It should be noted that the communication system and the servicescenario described in embodiments of this application are intended to describe thetechnical solutions in embodiments of this application more clearly, but constituteno limitation on the technical solutions provided in embodiments of thisapplication. A person of ordinary skill in the art may learn that the technicalsolutions provided in embodiments of this application are also applicable to asimilar technical problem as the network architecture evolves and a new servicescenario emerges.
[00307] Functions related to the terminal, the access network device, and thecore network element in this application may be implemented by one device, maybe jointly implemented by a plurality of devices, may be implemented by one ormore functional modules in one device, or may be implemented by one or morechips, a system-on-chip (SOC) or a chip system. The chip system may include achip, or may include a chip and another discrete component. This is notspecifically limited in embodiments of this application.
[00308] It may be understood that the foregoing function may be a networkelement in a hardware device, may be a software function running on dedicatedhardware, a combination of hardware and software, or a virtualized functioninstantiated on a platform (for example, a cloud platform).
[00309] For example, the functions related to the terminal, the access networkdevice, and the core network element in this application may be implemented by acommunication device 1000 in FIG. 10. FIG. 10 is a schematic diagram of astructure of a communication device 1000 according to an embodiment of thisapplication. The communication device 1000 includes one or more processors1001, a communication line 1002, and at least one communication interface (acommunication interface 1004 and one processor 1001 are merely used as anexample in FIG. 10 for description), and optionally may further include a memory1003.
[00310] The processor 1001 may be a general-purpose central processing unit(CPU), a microprocessor, an application-specific integrated circuit (ASIC), or oneor more integrated circuits configured to control execution of programs in thesolutions in this application.
[00311] The communication line 1002 may include a path for connectingdifferent components.
[00312] The communication interface 1004 may be a transceiver module,configured to communicate with another device or a communication network,such as the Ethernet, a RAN, or a wireless local area network (WLAN). Forexample, the transceiver module may be an apparatus such as a transceiver or atransceiver machine. Optionally, the communication interface 1004 mayalternatively be a transceiver circuit located in the processor 1001, and isconfigured to implement signal input and signal output of the processor.
[00313] The memory 1003 may be an apparatus with a storage function. Forexample, the memory may be a read-only memory (ROM) or another type ofstatic storage device capable of storing static information and instructions, may bea random access memory (RAM) or another type of dynamic storage devicecapable of storing information and instructions, or may be an electrically erasableprogrammable read-only memory (EEPROM), a compact disc read-only memory(CD-ROM) or other compact disc storage, optical disc storage (including acompressed optical disc, a laser disc, an optical disc, a digital versatile disc, a Bluraydisc, or the like), a magnetic disk storage medium or another magnetic storagedevice, or any other medium capable of carrying or storing expected programcode in a form of an instruction or a data structure and capable of being accessedby a computer, but is not limited thereto. The memory may exist independentlyand is connected to the processor through the communication line 1002.Alternatively, the memory and the processor may be integrated.
[00314] The memory 1003 is configured to store computer-executableinstructions for executing the solutions of this application, and the processor 1001controls the execution. The processor 1001 is configured to execute the computerexecutableinstructions stored in the memory 1003, to implement the networkslice-based communication method provided in embodiments of this application.
[00315] Alternatively, optionally, in this embodiment of this application, theprocessor 1001 may perform a processing-related function in the network slicebasedcommunication method provided in the following embodiments of thisapplication, and the communication interface 1004 is responsible forcommunicating with another device or a communication network. This is notspecifically limited in embodiments of this application.
[00316] Optionally, the computer-executable instruction in this embodiment ofthis application may also be referred to as application code. This is notspecifically limited in embodiments of this application.
[00317] During specific implementation, in an embodiment, the processor 1001may include one or more CPUs, such as a CPU 0 and a CPU 1 in FIG. 10.
[00318] During specific implementation, in an embodiment, thecommunication device 1000 may include a plurality of processors, for example,the processor 1001 and a processor 1008 in FIG. 10. Each of these processors maybe a single-core processor, or may be a multi-core processor. The processor hereinmay include but is not limited to at least one of the following: various computingdevices that run software, such as a central processing unit (CPU), amicroprocessor, a digital signal processor (DSP), a microcontroller unit (MCU),or an artificial intelligence processor. Each type of computing device may includeone or more cores for executing software instructions to perform an operation orprocessing.
[00319] During specific implementation, in an embodiment, thecommunication device 1000 may further include an output device 1005 and aninput device 1006. The output device 1005 communicates with the processor 1001,and may display information in a plurality of manners. For example, the outputdevice 1005 may be a liquid crystal display (LCD), a light emitting diode (LED)display device, a cathode ray tube (CRT) display device, or a projector. The inputdevice 1006 communicates with the processor 1001, and may receive user input ina plurality of manners. For example, the input device 1006 may be a mouse, akeyboard, a touchscreen device, or a sensor device.
[00320] Sometimes, the communication device 1000 may also be referred to asa communication apparatus, and may be a general-purpose device or a dedicateddevice. For example, the communication device 1000 may be a desktop computer,a portable computer, a network server, a palmtop computer (PDA), a mobilephone, a tablet computer, a wireless terminal device, an embedded device, theforegoing terminal, the foregoing network device, or a device having a structuresimilar to that in FIG. 10. A type of the communication device 1000 is not limitedin embodiments of this application.
[00321] In addition, the composition structure shown in FIG. 10 does notconstitute a limitation on the communication apparatus. In addition to the partsshown in FIG. 10, the communication apparatus may include more or fewer partsthan the parts shown in the figure, or some parts may be combined, or there maybe a different part layout.
[00322] The following describes a network slice-based communication methodprovided in an embodiment of this application with reference to thecommunication system shown in FIG. 9a, FIG. 9b, or FIG. 9c.
[00323] It should be noted that in the following embodiments of thisapplication, a name of a message between network elements, a name of eachparameter, a name of each piece of information, or the like is merely an example,and may be another name in another embodiment. This is not specifically limitedin the method provided in this application.
[00324] It may be understood that in this embodiment of this application, eachnetwork element may perform some or all of the steps in this embodiment of thisapplication. These steps or operations are merely examples. In this embodiment ofthis application, other operations or variations of various operations may befurther performed. In addition, the steps may be performed in different sequencespresented in embodiments of this application, and it is possible that not alloperations in embodiments of this application need to be performed.
[00325] FIG. 11 is a flowchart of a network slice-based communication methodaccording to an embodiment of this application. FIG. 11 is described withreference to scenarios in FIG. 8a and FIG. 8b. As shown in FIG. 11, the methodmay include:
[00326] S1101: A network device receives, via a first access network device ina first network, information about a network slice that a terminal requests toaccess.
[00327] In some embodiments, the network device may be a mobilitymanagement device. In a 5G system, the mobility management device may be, forexample, an AMF network element.
[00328] In some embodiments, the first network may be a PLMN, or may be anSNPN. This is not specifically limited in this application. For example, the firstnetwork may be the PLMN including the TA 1 to the TA 4 in FIG. 8a, or thePLMN including the TA 1 to the TA 3 in FIG. 8b. The first access network devicemay be the access network device 1 in FIG. 8a, or the access network device 1 inFIG. 8b.
[00329] The information about the network slice that the terminal requests toaccess includes identification information of a first network slice andidentification information of a second network slice. In other words, the firstnetwork slice and the second network slice are network slices corresponding torequested NSSAI of the terminal. For example, the identification information ofthe first network slice is S-NSSAI 1, and the identification information of thesecond network slice is S-NSSAI 2.
[00330] In an example, identification information of a slice may be S-NSSAI,or may be other information for identifying the slice. This is not specificallylimited in this application.
[00331] The first network slice is not supported by a first tracking area of thefirst access network device. In other words, the first tracking area does not supportthe first network slice.
[00332] In some embodiments, the first tracking area may be a tracking area inwhich the terminal is located when sending the information about the networkslice that the terminal requests to access. For example, the first tracking area maybe the TA 1 in FIG. 8a, or the TA 1 in FIG. 8b.
[00333] A second tracking area in the first network supports the first networkslice. In other words, the first network slice is a network slice that the terminal isallowed to access in the first network. In other words, there is at least one trackingarea that is in the first network and that supports the first network slice. Forexample, the second tracking area may be the TA 3 in FIG. 8a, or the TA 2 in FIG.8b.
[00334] In some embodiments, the network device may determine the networkslice supported by the tracking area of the first access network device, todetermine that the first tracking area of the first access network device does notsupport the first network slice. Further, the network device may further learnconfigured NSSAI of the terminal, to learn that there is a tracking area that is inthe first network and that supports the first network slice. For ease of description,in this application, the tracking area that is in the first network and that supportsthe first network slice is denoted as the second tracking area, that is, the secondtracking area in the first network supports the first network slice.
[00335] S1102: The network device determines a network slice that theterminal is allowed to access.
[00336] The network slice that the terminal is allowed to access is a networkslice corresponding to allowed NSSAI of the terminal, and includes the secondnetwork slice. In addition, the allowed NSSAI does not include the first networkslice. In other words, the first network slice does not belong to the network slicethat the terminal is allowed to access. That is to say:
[00337] The network slice that the terminal requests to access includes the firstnetwork slice and the second network slice.
[00338] The network slice that the terminal is allowed to access includes thesecond network slice.
[00339] The network slice that the terminal is rejected to access includes thefirst network slice.
[00340] It may be understood that the network slice that the terminal is allowedto access includes the second network slice, and therefore the second networkslice is also a network slice that the terminal is allowed to access in the firstnetwork.
[00341] In an example, the network device may independently determine anetwork slice that the terminal is allowed to access. Alternatively, the networkdevice may determine, by interacting with a network slice selection functionnetwork element (for example, an NSSF network element), a network slice thatthe terminal is allowed to access. This is not specifically limited in this application.
[00342] In some embodiments, in addition to a network slice that the terminalis allowed to access, the network device further determines a network slice thatthe terminal is rejected to access, so as to determine whether the first networkslice is the network slice that the terminal is rejected to access. The network slicethat the terminal is rejected to access is a network slice corresponding to rejectedNSSAI of the terminal. A description is made in this application through anexample in which the network slice that the terminal is rejected to access includesthe first network slice. That is to say:
[00343] The network slice that the terminal requests to access includes the firstnetwork slice and the second network slice.
[00344] The network slice that the terminal is allowed to access includes thesecond network slice. That is to say, the allowed NSSAI includes the S-NSSAI 2.
[00345] The network slice that the terminal is rejected to access includes thefirst network slice. That is to say, the rejected NSSAI includes the S-NSSAI 1.
[00346] S1103: The network device determines a registration area.
[00347] In different implementation scenarios of this application, ranges of theregistration area may be different. For example, in a possible implementationscenario, the registration area excludes a tracking area that supports the firstnetwork slice and the second network slice. The tracking area that supports thefirst network slice and the second network slice may be understood as: a trackingarea that supports both the first network slice and the second network slice; ormay be understood as a tracking area that supports the first network slice and thesecond network slice simultaneously. This is applicable to the scenario of FIG. 8b.For example, a tracking area that supports the first network slice and the secondnetwork slice may be the TA 2 in FIG. 8b.
[00348] In some embodiments, that the registration area excludes a trackingarea may be understood as that the registration area does not include the trackingarea; the tracking area is not in the registration area; or the tracking area isremoved from the registration area. Examples are as follows:
[00349] In a possible implementation, that the registration area excludes atracking area that supports the first network slice and the second network slicemay be understood as that the registration area does not include a tracking areathat supports the first network slice and the second network slice.
[00350] In a possible implementation, that the registration area excludes atracking area that supports the first network slice and the second network slicemay be understood as that a tracking area that supports the first network slice andthe second network slice is not in the registration area.
[00351] In a possible implementation, that the registration area excludes atracking area that supports the first network slice and the second network slicemay be understood as that a tracking area that supports the first network slice andthe second network slice is deleted from the registration area.
[00352] In a possible implementation, that the registration area excludes atracking area that supports the first network slice and the second network slicemay be understood as that a tracking area included in the registration areasupports the second network slice, but does not support the first network slice.Certainly, the tracking area included in the registration area may support thesecond network slice, and support another network slice other than the firstnetwork slice.
[00353] In a possible implementation, that the registration area excludes atracking area that supports the first network slice and the second network slicemay be understood as that a tracking area included in the registration areasupports the second network slice, and a tracking area supporting the first networkslice is excluded from the registration area.
[00354] For example, for the scenario shown in FIG. 8b, for example,identification information of the first network slice is S-NSSAI 1, andidentification information of the second network slice is S-NSSAI 2. It is assumedthat the TA 1 of the access network device 1 supports the second network slice;the TA 2 of the access network device 2 supports the first network slice and thesecond network slice; and the TA 3 of the access network device 3 supports thefirst network slice.
[00355] When the network device determines the registration area through themethod provided in the application, the registration area excludes a tracking areathat supports the first network slice and the second network slice. In other words,the registration area excludes the TA 2. Therefore, the registration area determinedby the network device does not include the TA 2. When the terminal subsequentlymoves from the cell in the TA 1 to the cell in the TA 2, because of moving to a TAoutside the registration area, when still intending to access the first network slice,the terminal may re-initiate a registration procedure to access the first networkslice and use a service provided by the first network slice.
[00356] In another possible implementation scenario, the registration areaexcludes a tracking area of an access network device that supports the firstnetwork slice and the second network slice. This is applicable to the scenario ofFIG. 8a. For example, an access network device that supports the first networkslice and the second network slice may be the access network device 2 in FIG. 8a,and tracking areas of the access network device 2 include the TA 2 and the TA 3.
[00357] It should be noted that in tracking areas of the access network device, atracking area that supports the first network slice and a tracking area that supportsthe second network slice may be a same tracking area. For example, a trackingarea 1 of the access network device supports the first network slice and the secondnetwork slice. Alternatively, a tracking area that supports the first network sliceand a tracking area that supports the second network slice may be differenttracking areas. For example, a tracking area 1 of the access network devicesupports the first network slice, and a tracking area 2 of the access network devicesupports the second network slice.
[00358] In an example, the registration area may exclude all tracking areas ofthe access network device that supports the first network slice and the secondnetwork slice. In other words, when one or more tracking areas supporting thefirst network slice exist in the access network device corresponding to the trackingarea supporting the second network slice, the tracking area supporting the secondnetwork slice is excluded from the registration area.
[00359] In a possible implementation, that the registration area excludes atracking area of the access network device that supports the first network slice andthe second network slice may be understood as that the registration area does notinclude a tracking area of the access network device that supports the firstnetwork slice and the second network slice.
[00360] In a possible implementation, that the registration area excludes atracking area of the access network device that supports the first network slice andthe second network slice may be understood as that a tracking area of the accessnetwork device that supports the first network slice and the second network sliceis not in the registration area.
[00361] In a possible implementation, that the registration area excludes atracking area of the access network device that supports the first network slice andthe second network slice may be understood as that a tracking area of the accessnetwork device that supports the first network slice and the second network sliceis deleted from the registration area.
[00362] For example, for the scenario shown in FIG. 8a, for example,identification information of the first network slice is S-NSSAI 1, andidentification information of the second network slice is S-NSSAI 2. It is assumedthat the TA 1 of the access network device 1 supports the second network slice;the TA 2 of the access network device 2 supports the second network slice, and theTA 3 supports the first network slice; and the TA 4 of the access network device 3supports the first network slice.
[00363] When the network device determines the registration area through themethod provided in the application, the registration area excludes a tracking areaof the access network device that supports the first network slice and the secondnetwork slice. In other words, the registration area excludes tracking areas of theaccess network device 2, that is, the TA 2 and the TA 3, and therefore theregistration area determined by the network device does not include the TA 2 orthe TA 3. It may be understood that because the TA 3 does not support the allowedNSSAI, the RA itself does not include the TA 3. However, for the TA 2, althoughthe TA 2 supports the S-NSSAI 2, the TA 3 still exists under the access networkdevice 2 corresponding to the TA 2, and TA 3 supports S-NSSAI 1. In this case,the TA 2 needs to be excluded from the RA when the RA is determined. When theterminal subsequently moves from the cell in the TA 1 to the cell in the accessnetwork device 2, because of moving to the TA 2 outside the registration area,when still intending to access the first network slice, the terminal may re-initiate aregistration procedure to access the first network slice and use a service providedby the first network slice.
[00364] S1104: The network device sends information about the registrationarea to the terminal.
[00365] In an example, the information about the registration area may includeidentification information of a tracking area in the registration area. Specificcontent of the information about the registration area is not specifically limited inthis application.
[00366] In an example, when receiving the information about the registrationarea and subsequently leaving the registration area, the terminal may triggermobility registration update, that is, re-perform a registration procedure, to re20request a network slice to be accessed.
[00367] For example, the scenario shown in FIG. 8a is used as an example. It isassumed that the terminal moves from the coverage of the TA 1 to the coverage ofthe TA 2. Because the TA 2 is not in the RA, the terminal re-initiates a registrationprocedure. It is assumed that in the re-initiated registration procedure, the terminalstill requests to access the first network slice (corresponding to the S-NSSAI 1).Because the TA 2 does not support the first network slice, the first network slice inthe registration procedure does not belong to the network slice that the terminal isallowed to access. However, the TA 3 whose physical coverage is the same as thatof the TA 2 supports the first network slice. Therefore, the access network devicemay send an RRC connection release message to redirect the terminal to a cell inthe TA 3, so that the terminal accesses the first network slice in the cell in the TA 3.For details, refer to the procedure shown in FIG. 5. Details are not describedherein again. It should be noted that the registration request in S501 in FIG. 5 maybe understood as a registration request initiated by the terminal in a cell in the TA2.
[00368] The scenario shown in FIG. 8b is used as an example. It is assumedthat the terminal moves from the coverage of the TA 1 to the coverage of the TA 2.Because the TA 2 is not in the RA, the terminal may re-initiate a registrationprocedure. It is assumed that in the re-initiated registration procedure, the terminalstill requests to access the first network slice (corresponding to the S-NSSAI 1).Because the TA 2 supports the first network slice, the terminal accesses the firstnetwork slice in the TA 2.
[00369] Based on this solution, when determining the registration area, thenetwork device excludes the tracking area that supports the first network slice andthe second network slice, or excludes the tracking area of the access networkdevice that supports the first network slice and the second network slice.Therefore, when the terminal moves within the excluded tracking area, becausethe registration area of the terminal does not include the tracking area, and thetracking area supports the first network slice, the terminal may re-initiate aregistration procedure to request to access the first network slice, to increase asuccess rate of accessing the first network slice, thereby improving serviceperformance and user experience.
[00370] FIG. 12 is a flowchart of another network slice-based communicationmethod according to an embodiment of this application. FIG. 12 is described withreference to FIG. 11. As shown in FIG. 12, the method may include:
[00371] S1201: A network device determines a network slice that a terminal isallowed to access and a network slice that the terminal is rejected to access.
[00372] In some embodiments, before step S1201, the method may furtherinclude: The network device receives, via a first access network device in a firstnetwork, information about a network slice that a terminal requests to access.
[00373] For related descriptions of the network device and the first network,refer to step S1101. Details are not described herein again.
[00374] The information about the network slice that the terminal requests toaccess includes identification information of a first network slice andidentification information of a second network slice. In other words, the firstnetwork slice and the second network slice are network slices corresponding torequested NSSAI of the terminal.
[00375] In some embodiments, that the network device determines the networkslice that the terminal is allowed to access and the network slice that the terminalis rejected to access may include: The network device receives, from a sliceselection function network element, information about the network slice that theterminal is allowed to access and information about the network slice that theterminal is rejected to access.
[00376] In this application, a description is made through an example in whichthe network slice that the terminal is allowed to access includes the secondnetwork slice, and the network slice that the terminal is rejected to access includesthe first network slice.
[00377] In some embodiments, the first network slice is not supported by a firsttracking area of the first access network device. In other words, the first trackingarea does not support the first network slice. The second network slice is anetwork slice supported by the first tracking area. In other words, the first trackingarea supports the second network slice.
[00378] In some embodiments, a second tracking area in the first networksupports the first network slice. In other words, the first network slice is a networkslice that the terminal is allowed to access in the first network.
[00379] In an example, the network device may determine the network slicesupported by the tracking area of the first access network device, to determine thatthe first tracking area of the first access network device does not support the firstnetwork slice. Further, the network device may learn configured NSSAI of theterminal, to learn that there is a tracking area that is in the first network and thatsupports the first network slice, that is, the first network slice is a network slicethat the terminal is allowed to access in the first network. In this application, thetracking area that is in the first network and that supports the first network slice isdenoted as the second tracking area.
[00380] S1202: The network device determines a registration area of theterminal based on the network slice that the terminal is allowed to access and thenetwork slice that the terminal is rejected to access.
[00381] in a possible implementation scenario, the registration area excludes atracking area that supports the first network slice and the second network slice.
[00382] In another possible implementation scenario, the registration areaexcludes a tracking area of an access network device that supports the firstnetwork slice and the second network slice.
[00383] For a detailed description, refer to the related description in step S1103.Details are not described herein again. This manner of determining the registrationarea may be understood as follows: When the registration area is determined, anetwork slice that is rejected by the network for access because the network sliceis not supported by the current TA is considered.
[00384] In another possible design, the registration area excludes a trackingarea that supports a network slice that the terminal is allowed to access and anetwork slice that the terminal is rejected to access, or the registration areaexcludes a tracking area of an access network device that supports a network slicethat the terminal is allowed to access and a network slice that the terminal isrejected to access. In other words, when the range of the registration area isdetermined, a reason why a network slice is rejected by the network for accessmay not be considered, provided that the network slice is rejected and belongs to anetwork slice that the terminal is rejected to access. Therefore, when the range ofthe registration area is determined, it is considered that a tracking area thatsupports a network slice that the terminal is allowed to access and a network slicethat the terminal is rejected to access, or a tracking area of an access networkdevice that supports a network slice that the terminal is allowed to access and anetwork slice that the terminal is rejected to access is excluded from theregistration area.
[00385] For example, it is assumed that the following scenario exists:
[00386] The network slice that the terminal requests to access includes the firstnetwork slice, the second network slice, and a third network slice.
[00387] The network slice that the terminal is allowed to access includes thesecond network slice.
[00388] The network slice that the terminal is rejected to access includes thefirst network slice and the third network slice.
[00389] Therefore, when the registration area is determined, it may beconsidered that a tracking area that supports the first network slice and the secondnetwork slice, a tracking area of an access network device that supports the firstnetwork slice and the second network slice, a tracking area that supports the thirdnetwork slice and the second network slice, a tracking area of an access networkdevice that supports the third network slice and the second network slice, atracking area that supports the first network slice, the second network slice, andthe third network slice, or a tracking area of an access network device thatsupports the first network slice, the second network slice, and the third networkslice is excluded from the registration area.
[00390] S1203: The network device sends information about the registrationarea to the terminal.
[00391] For details, refer to the related description in step S1104. Details arenot described herein again.
[00392] Based on this solution, the registration area of the terminal isdetermined based on the network slice that the terminal is allowed to access andthe network slice that the terminal is rejected to access, so that the registrationarea excludes a tracking area that supports the network slice that the terminal isallowed to access and the network slice that the terminal is rejected to access, or atracking area of an access network device that supports the network slice thatallows the terminal to access and the network slice that the terminal is rejected toaccess. Therefore, when the terminal moves within the excluded tracking area,because the registration area of the terminal does not include the tracking area,and the tracking area supports the first network slice, the terminal may re-initiate aregistration procedure to request to access the first network slice, to increase asuccess rate of accessing the first network slice, thereby improving serviceperformance and user experience.
[00393] The methods shown in FIG. 11 and FIG. 12 provide a registration areadivision manner. FIG. 13 is a flowchart of another network slice-basedcommunication method according to an embodiment of this application. Themethod provides another registration area division manner. As shown in FIG. 13,the method may include:
[00394] S1301: In a registration procedure of a first network, a network devicedetermines allowed NSSAI of a terminal.
[00395] For descriptions of the first network and the network device, refer tostep S1101. For the registration procedure and a method for determining theallowed NSSAI by the network device, refer to the procedure shown in FIG. 4.Details are not described herein again.
[00396] S1302: The network device determines a first-type network slice.
[00397] The first-type network slice is a network slice that does not belong tothe allowed NSSAI of the terminal in network slices that the terminal is allowedto access in the first network.
[00398] For example, it is assumed that the following scenario exists:
[00399] The network slice that the terminal requests to access includes the firstnetwork slice, the second network slice, and a third network slice.
[00400] The network slice that the terminal is allowed to access includes thesecond network slice.
[00401] The network slice that the terminal is rejected to access includes thefirst network slice and the third network slice.
[00402] Network slices that the terminal is allowed to access in the firstnetwork (for example, a current PLMN) include: the first network slice, thesecond network slice, and a fourth network slice. For example, a network slicethat the terminal is allowed to access in the first network may be represented viaconfigured NSSAI of the terminal in the first network.
[00403] A network slice that the terminal is allowed to access in a secondnetwork (for example, another PLMN) includes the third network slice.
[00404] In this scenario, the first-type network slice includes the first networkslice and the fourth network slice.
[00405] S1303: The network device determines a registration area.
[00406] In different implementation scenarios of this application, ranges of theregistration area may be different. For example, in a possible implementationscenario, the registration area excludes a tracking area that supports at least onenetwork slice corresponding to the allowed NSSAI and at least one first-typenetwork slice.
[00407] The tracking area that supports the at least one network slicecorresponding to the allowed NSSAI and the at least one first-type network slicemay be understood as: a tracking area that supports both the at least one networkslice corresponding to the allowed NSSAI and the at least one first-type networkslice; or a tracking area that supports the at least one network slice correspondingto the allowed NSSAI and the at least one first-type network slice simultaneously.
[00408] For example, based on the scenario of the assumption in S1302, theregistration area may exclude a tracking area that supports the second networkslice and the first network slice; may exclude a tracking area that supports thesecond network slice and the fourth network slice; or may exclude a tracking areathat supports the second network slice, the first network slice, and the fourthnetwork slice.
[00409] In another possible implementation scenario, the registration areaexcludes a tracking area of an access network device that supports at least onenetwork slice corresponding to the allowed NSSAI and at least one first-typenetwork slice.
[00410] It should be noted that in tracking areas of the access network device, atracking area that supports the at least one network slice corresponding to theallowed NSSAI and a tracking area that supports the at least one first-typenetwork slice may be a same tracking area. For example, a tracking area 1 of theaccess network device supports the at least one network slice corresponding to theallowed NSSAI and the at least one first-type network slice. Alternatively, atracking area that supports the at least one network slice corresponding to theallowed NSSAI and a tracking area that supports the at least one first-typenetwork slice may be different tracking areas. For example, a tracking area 1 ofthe access network device supports the at least one network slice corresponding tothe allowed NSSAI and a tracking area 2 of the access network device supportsthe at least one first-type network slice.
[00411] In an example, the registration area may exclude all tracking areas ofan access network device that supports at least one network slice corresponding tothe allowed NSSAI and at least one first-type network slice. In other words, whenone or more tracking areas supporting at least one first-type network slice exist inthe access network device corresponding to the tracking area supporting thesecond network slice, the tracking area supporting the second network slice isexcluded from the registration area.
[00412] For example, based on the scenario of the assumption in S1302, theregistration area may exclude a tracking area of an access network device thatsupports the second network slice and the first network slice; may exclude atracking area of an access network device that supports the second network sliceand the fourth network slice; or may exclude a tracking area of an access networkdevice that supports the second network slice, the first network slice, and thefourth network slice.
[00413] S1304: The network device sends information about the registrationarea to the terminal.
[00414] For details, refer to the related description in step S1104. Details arenot described herein again.
[00415] Based on this solution, for the first-type network slice that does notbelong to the network slice that the terminal is allowed to access in theregistration procedure of the first network but is included in the network slice thatthe terminal is allowed to access in the first network, regardless of whether thenetwork slice that the terminal requests to access in this registration procedurecarries the identifier of the first network slice, because the first-type network sliceis included in the network slice that the terminal is allowed to access in the firstnetwork, the terminal may subsequently intend to access a first-type network slice.In this case, the network device considers the first-type network slice whendetermining the registration area. For example, the registration area excludes atracking area that supports the at least one network slice corresponding to theallowed NSSAI and the at least one first-type network slice, or excludes a trackingarea of an access network device that supports the at least one network slicecorresponding to the allowed NSSAI and the at least one first-type network slice.Therefore, when the terminal moves into the excluded tracking area, because theregistration area of the terminal does not include the tracking area, and thetracking area supports the at least one first-type network slice, the terminal mayre-initiate a registration procedure when intending to access a first-type networkslice, and request to access the at least one first-type network slice, to improve asuccess rate of accessing the network slice, and further improve serviceperformance and user experience.
[00416] In the methods shown in FIG. 11 to FIG. 13, the registration area isdivided, so that a probability that a terminal cannot normally access a targetnetwork slice (for example, the foregoing first network slice) is reduced, and anetwork slice access success rate is improved. In addition, this application furtherprovides a method for improving a network slice access success rate in anothermanner.
[00417] FIG. 14 is a flowchart of a network slice-based communication methodaccording to this application. The method is applicable to a scenario in which aterminal is handed over from a first cell to a second cell, and a network devicenotifies the terminal of a network slice available in the second cell. The handoverscenario may be intra-eNodeB handover, that is, the first cell and the second cellbelong to a same access network device; or may be inter-eNodeB handover, that is,the first cell and the second cell belong to different access network devices. Forexample, the method shown in FIG. 14 is applicable to the scenario shown in FIG.8b or FIG. 8c. As shown in FIG. 14, the method includes the following steps:
[00418] S1401: A network device determines a first network slice.
[00419] In some embodiments, the network device may be a mobilitymanagement device. In a 5G system, the mobility management device may be, forexample, an AMF network element.
[00420] In some other embodiments, the network device may be an accessnetwork device. For example, when the first cell belongs to a first access networkdevice and the second cell belongs to a second access network device, the networkdevice is the second access network device; or when both the first cell and thesecond cell belong to a first access network device, the network device is the firstaccess network device.
[00421] The first network slice does not belong to a network slice that theterminal is allowed to access in the first cell. In other words, when the terminalinitiates a registration procedure in the first cell, a network slice corresponding toallowed NSSAI of the terminal does not include the first network slice. In thisapplication, a network slice that the terminal is rejected to access may be referredto as a target network slice, and there may be one or more target network slices.
[00422] A registration area of the terminal includes the first cell and the secondcell.
[00423] In some embodiments, the first cell is a cell in a first TA, the secondcell is a cell in a second TA, and the first TA and the second TA are different TAs.
[00424] In some embodiments, the first network slice is included in a networkslice that the terminal requests to access in the first cell. In other words, theterminal initiates the registration procedure in the first cell, and requests to accessthe first network slice. However, the first network slice does not belong to thenetwork slice that the terminal is allowed to access in the first cell, or the firstnetwork slice belongs to the network slice that the terminal is rejected to access inthe first cell. Therefore, the terminal cannot access the first network slice in thefirst cell. Based on subsequent steps, the terminal may access, in the second cell,the first network slice that cannot be accessed in the first cell.
[00425] In some embodiments, the first network slice is included in a networkslice configured for the terminal in a first network; or the first network slice isincluded in a network slice corresponding to configured NSSAI of the terminal, orthe first network slice is a network slice that the terminal is allowed to access inthe first network. That is to say, regardless of whether the terminal requests toaccess the first network slice when initiating the registration procedure in the firstcell, because the first network slice is included in the network slice configured forthe terminal in the first network, the terminal may subsequently intend to accessthe first network slice. Because the first network slice does not belong to thenetwork slice that the terminal is allowed to access in the first cell, the terminalcannot access the first network slice in the first cell. Based on subsequent steps,the terminal may access, in the second cell, the first network slice that cannot beaccessed in the first cell.
[00426] For example, based on the scenario shown in FIG. 8b, using anexample in which the first cell is a cell in the TA 1 of the access network device 1,the second cell is a cell in the TA 2 of the access network device 2, and theidentification information of the first network slice is S-NSSAI 1, the terminalrequests access to the S-NSSAI 1 and the S-NSSAI 2 via the access networkdevice 1 in the TA 1, the allowed NSSAI determined on a network side is the SNSSAI2, and both the TA 1 and the TA 2 support the S-NSSAI 2. Therefore, theregistration area RA 1 of the terminal includes the TA 1 and the TA 2.Alternatively, based on the scenario shown in FIG. 8c, using an example in whichthe first cell is a cell in the TA 1 of the access network device 1, the second cell isa cell in the TA 2 of the access network device 1, and the identificationinformation of the first network slice is S-NSSAI 1, the registration area RA 1 ofthe terminal similarly includes the TA 1 and the TA 2.
[00427] In the foregoing two scenarios, the terminal initiates a registrationrequest in the first cell, and requests to access the first network slice and thesecond network slice (for example, the identification information is S-NSSAI 2),the first network slice does not belong to a network slice that the terminal isallowed to access in the first cell, and the second network slice belongs to anetwork slice that the terminal is allowed to access in the first cell. Therefore, theterminal accesses the second network slice in the first cell.
[00428] S1402: The network device determines, when the terminal is handedover from the first cell to the second cell, that the first network slice is available inthe second cell.
[00429] In some embodiments, a reason why the network device determinesthat the first network slice is available in the second cell may be that the secondTA in which the second cell is located supports the first network slice.
[00430] For example, based on the scenario shown in FIG. 8b or FIG. 8c, thenetwork device may determine, when the terminal is handed over from the firstcell in the TA 1 to the second cell in the TA 2, that the first network slice isavailable in the second cell.
[00431] S1403: The network device notifies the terminal that the first networkslice is available in the second cell.
[00432] In some embodiments, when the network device is a mobilitymanagement device, the network device may notify, via a non-access stratum(NAS) message, the terminal that the first network slice is available in the secondcell.
[00433] In some other embodiments, when the network device is the firstaccess network device or the second access network device, the network devicemay notify, via the mobility management device, the terminal that the firstnetwork slice is available in the second cell. For example, the network devicenotifies, via the mobility management device, the terminal that the first networkslice is available in the second cell. Then, the mobility management device istriggered to notify, via a NAS message, the terminal that the first network slice isavailable in the second cell. Certainly, the network device may further notify theterminal in another manner. For example, the network device may notify, via anRRC message, the terminal that the first network slice is available in the secondcell. A notification manner is not specifically limited in this application.
[00434] In an example, the network device may send the identificationinformation of the first network slice to the terminal, to notify the terminal that thefirst network slice is available in the second cell. Further, the network device mayfurther send a cell identifier of the second cell to the terminal.
[00435] In the current technology, the first network slice does not belong to thenetwork slice that the terminal is allowed to access in the first cell, that is, wheninitiating a registration procedure in the first cell, the terminal cannot access thefirst network slice. Because the registration area of the terminal includes the firstcell and the second cell, when the terminal is handed over from the first cell to thesecond cell, the terminal is not triggered to perform a re-registration procedure.Even if the first network slice is available in the second cell, because of initiatingno registration procedure in the second cell, the terminal still cannot access thefirst network slice in the second cell. Based on the solution of this application,when the terminal is handed over from the first cell to the second cell, and it isdetermined that the first network slice is available in the second cell, the terminalis notified that the first network slice is available in the second cell, so that whenstill intending to access the first network slice, the terminal may initiate aregistration procedure to request to access the first network slice, therebyimproving a success rate of accessing the first network slice, and improvingservice performance and user experience.
[00436] As described above, the network device may be a mobilitymanagement device or an access network device. When the network device is amobility management device, refer to a specific implementation in FIG. 20 or FIG.21. When the network device is an access network device in an intra-eNodeBhandover scenario, refer to a specific implementation in FIG. 22. When thenetwork device is an access network device in an inter-eNodeB handover scenario,refer to a specific implementation in FIG. 23.
[00437] In addition to the method shown in FIG. 14, refer to FIG. 15. Thisapplication further provides a network slice-based communication methodapplicable to the following scenario: a method in a scenario in which a terminal ishanded over from a first cell to a second cell, and a third cell whose physicalcoverage is the same as that of the second cell exists. The handover scenario maybe intra-eNodeB handover, that is, the first cell and the second cell belong to asame access network device; or may be inter-eNodeB handover, that is, the firstcell and the second cell belong to different access network devices. For example,the method shown in FIG. 15 is applicable to the scenario shown in FIG. 8a. Asshown in FIG. 15, the method includes the following steps:
[00438] S1501: A network device determines a first network slice.
[00439] In some embodiments, the network device may be a mobilitymanagement device, a first access network device, or a second access networkdevice. For details, refer to related descriptions in step S1401. Details are notdescribed herein again.
[00440] The first network slice does not belong to a network slice that theterminal is allowed to access in a first cell, and a registration area of the terminalincludes the first cell and the second cell. Physical coverage of the third cellcompletely or partially overlaps physical coverage of the second cell.
[00441] In some embodiments, the third cell may be referred to as a cell whosephysical coverage is the same as that of the second cell.
[00442] In some embodiments, the first cell is a cell in a first TA, the secondcell is a cell in a second TA, the third cell is a cell in a third TA, and the first TA,the second TA, and the third TA are different TAs.
[00443] In some embodiments, the first network slice is included in a networkslice configured for the terminal in the first network, and / or the first network sliceis included in a network slice that the terminal requests to access in the first cell.For details, refer to related descriptions in step S1401. Details are not describedherein again.
[00444] For example, based on the scenario shown in FIG. 8a, using anexample in which the first cell is a cell in the TA 1 of the access network device 1,the second cell is a cell in the TA 2 of the access network device 2, the third cell isa cell in the TA 3 of the access network device 2, and the identificationinformation of the first network slice is S-NSSAI 1, the terminal requests accessto the S-NSSAI 1 and the S-NSSAI 2 via the access network device 1 in the TA 1,the allowed NSSAI determined on a network side is the S-NSSAI 2, and both theTA 1 and the TA 2 support the S-NSSAI 2. Therefore, the registration area RA 1of the terminal includes the TA 1 and the TA 2. The terminal initiates a registrationrequest in the first cell, and requests to access the first network slice and thesecond network slice (for example, the identification information is S-NSSAI 2),the first network slice does not belong to a network slice that the terminal isallowed to access in the first cell, and the second network slice belongs to anetwork slice that the terminal is allowed to access in the first cell. Therefore, theterminal accesses the second network slice in the first cell.
[00445] S1502: The network device determines, when the terminal is handedover from the first cell to the second cell, that the first network slice is available inthe third cell.
[00446] In some embodiments, a reason why the network device determinesthat the first network slice is available in the third cell may be that the third TA inwhich the third cell is located supports the first network slice.
[00447] For example, based on the scenario shown in FIG. 8a, when theterminal is handed over from the first cell in the TA 1 to the second cell in the TA2, because the TA 2 is grouped into a range of the RA 1, and the terminal does notmove out of the range of the RA 1, the terminal does not re-initiate a registrationprocedure. Therefore, the terminal still does not access the first network slice.However, because the cell of the access network device 2 includes the third cellwhose physical coverage partially or completely overlaps the physical coverage ofthe second cell, and the TA 3 in which the third cell is located supports the firstnetwork slice, the network device may determine that the first network slice isavailable in the third cell.
[00448] S1503: The network device notifies the terminal that the first networkslice is available in the third cell.
[00449] For a notification manner, refer to the manner in which the networkdevice notifies the terminal that the first network slice is available in the secondcell in step S1403. Details are not described herein again.
[00450] In the current technology, the first network slice does not belong to thenetwork slice that the terminal is allowed to access in the first cell, that is, wheninitiating a registration procedure in the first cell, the terminal cannot access thefirst network slice. Because the registration area of the terminal includes the firstcell and the second cell, when the terminal is handed over from the first cell to thesecond cell, the terminal is not triggered to perform a re-registration procedure.Even if the first network slice is available in the third cell whose physicalcoverage is the same as that of the second cell, because of initiating noregistration procedure again in the second cell, the terminal still cannot access thefirst network slice in a location of the second cell. Based on the solution of thisapplication, when the terminal is handed over from the first cell to the second cell,and it is determined that the first network slice is available in the third cell, theterminal is notified that the first network slice is available in the third cell, so thatwhen still intending to access the first network slice, the terminal may access thefirst network slice in the third cell, thereby improving a success rate of accessingthe first network slice, and using a service provided by the first network slice.
[00451] As described above, the network device may be a mobilitymanagement device or an access network device. When the network device is amobility management device, refer to a specific implementation in FIG. 24. Whenthe network device is an access network device in an intra-eNodeB handoverscenario, refer to a specific implementation in FIG. 25. When the network deviceis an access network device in an inter-eNodeB handover scenario, refer to aspecific implementation in FIG. 26.
[00452] In addition to the methods shown in FIG. 14 and FIG. 15, thisapplication further provides a network slice-based communication methodapplicable to the following scenario: a method in a scenario in which a terminalaccesses a first cell, and a neighboring cell of the first cell includes a second cell.The first cell and the second cell may belong to a same access network device; orthe first cell and the second cell may belong to different access network devices.For example, the method shown in FIG. 16 is applicable to the scenario shown inFIG. 8b or FIG. 8c. As shown in FIG. 16, the method includes the following steps:
[00453] S1601: A network device determines a first network slice.
[00454] Step S1601 is similar to step S1401. For details, refer to the relateddescription in step S1401. Details are not described herein again.
[00455] S1602: The network device determines that the first network slice isavailable in the second cell.
[00456] In some embodiments, a reason why the network device determinesthat the first network slice is available in the second cell may be that the secondTA in which the second cell is located supports the first network slice.
[00457] In some embodiments, a reason why the network device determinesthat the first network slice is available in the second cell may be that the secondTA in which the second cell is located supports the first network slice, cell signalquality of the second cell is greater than a first threshold, and the terminal mayaccess the second cell.
[00458] In some embodiments, the network device may determine that the firstnetwork slice is available in the second cell before the terminal is handed overfrom the first cell to the second cell.
[00459] S1603: The network device notifies the terminal that the first networkslice is available in the second cell.
[00460] Step S1603 is similar to step S1403. For details, refer to the relateddescription in step S1403. Details are not described herein again.
[00461] A difference between step S1603 and step S1403 lies in that stepS1403 is triggered by handover. In other words, in a handover scenario, thenetwork device notifies the terminal that the first network slice is available in thesecond cell. However, step S1603 does not depend on handover. For example,before a handover procedure occurs, the network device may notify the terminalthat the first network slice is available in the second cell.
[00462] S1604: The network device sends a cell identifier of the second cell tothe terminal.
[00463] In some embodiments, the cell identifier of the second cell may beused by the terminal to access the second cell, so as to access the first networkslice available in the second cell.
[00464] In the current technology, the first network slice does not belong to thenetwork slice that the terminal is allowed to access in the first cell, that is, wheninitiating a registration procedure in the first cell, the terminal cannot access thefirst network slice. Because the registration area of the terminal includes the firstcell and the second cell, when the terminal is handed over from the first cell to thesecond cell, the terminal is not triggered to perform a re-registration procedure.Even if the first network slice is available in the second cell, because of initiatingno registration procedure in the second cell, the terminal still cannot access thefirst network slice in the second cell. Based on the solution of this application,when the terminal is handed over from the first cell to the second cell, and it isdetermined that the first network slice is available in the second cell, the terminalis notified that the first network slice is available in the second cell, and the cellidentifier of the second cell is sent, so that when still intending to access the firstnetwork slice, the terminal may access the second cell, and initiate a registrationprocedure to request to access the first network slice, thereby improving a successrate of accessing the first network slice, and using a service provided by the firstnetwork slice.
[00465] In addition to the method shown in FIG. 16, refer to FIG. 17. Thisapplication further provides a network slice-based communication methodapplicable to the following scenario: A terminal accesses a first cell, a neighboringcell of the first cell includes a second cell, and a third cell whose physicalcoverage is the same as that of the second cell exists. The first cell and the secondcell may belong to a same access network device; or the first cell and the secondcell may belong to different access network devices. For example, the methodshown in FIG. 17 is applicable to the scenario shown in FIG. 8a. As shown in FIG.17, the method includes the following steps:
[00466] S1701: A network device determines a first network slice.
[00467] Step S1701 is similar to step S1501. For details, refer to the relateddescription in step S1501. Details are not described herein again.
[00468] S1702: The network device determines that the first network slice isavailable in the third cell.
[00469] In some embodiments, a reason why the network device determinesthat the first network slice is available in the third cell may be that the third TA inwhich the third cell is located supports the first network slice.
[00470] In some embodiments, the network device may determine that the firstnetwork slice is available in the third cell before the terminal is handed over fromthe first cell to the second cell.
[00471] S1703: The network device notifies the terminal that the first networkslice is available in the third cell.
[00472] For a notification manner, refer to the manner in which the networkdevice notifies the terminal that the first network slice is available in the secondcell in step S1403. Details are not described herein again.
[00473] S1704: The network device sends a cell identifier of the third cell tothe terminal.
[00474] In some embodiments, the cell identifier of the third cell may be usedby the terminal to access the third cell, so as to access the first network sliceavailable in the third cell.
[00475] In the current technology, the first network slice does not belong to thenetwork slice that the terminal is allowed to access in the first cell, that is, wheninitiating a registration procedure in the first cell, the terminal cannot access thefirst network slice. Because the registration area of the terminal includes the firstcell and the second cell, when the terminal is handed over from the first cell to thesecond cell, the terminal is not triggered to perform a re-registration procedure.Even if the first network slice is available in the third cell whose physicalcoverage is the same as that of the second cell, because of initiating noregistration procedure again in the second cell, the terminal still cannot access thefirst network slice in a location of the second cell. Based on the solution of thisapplication, when the neighboring cell of the first cell accessed by the terminalincludes the second cell, the third cell whose physical coverage is the same as thatof the second cell exists, and it is determined that the first network slice isavailable in the third cell, the terminal is notified that the first network slice isavailable in the third cell, and the cell identifier of the third cell is sent, so thatwhen still intending to access the first network slice, the terminal may access thethird cell and request to access the first network slice, thereby improving a successrate of accessing the first network slice, and using a service provided by the firstnetwork slice.
[00476] FIG. 11 to FIG. 17 describe the network slice-based communicationmethod provided in this application from a perspective of a network device, andthe following describes the method from a perspective of a terminal.
[00477] FIG. 18 shows a network slice-based communication method appliedto a terminal according to this application. The method may be applied to theforegoing process in which the network device notifies the terminal that the firstnetwork slice is available in the second cell. In other words, the method may beconsidered as implementation of the terminal after the network device notifies theterminal that the first network slice is available in the second cell in FIG. 14 orFIG. 16. The method includes the following steps:
[00478] S1801: The terminal learns, from a network device, that a first networkslice is available in a second cell.
[00479] The first network slice does not belong to a network slice that theterminal is allowed to access in a first cell, and a registration area of the terminalincludes the first cell and the second cell. For details, refer to the relateddescription in step S1401. Details are not described herein again.
[00480] S1802: The terminal initiates a registration procedure for anapplication corresponding to the first network slice.
[00481] In some embodiments, that the terminal initiates the registrationprocedure for the application corresponding to the first network slice may include:The terminal determines whether the first network slice is a network slicecorresponding to the application in response to that a context of the terminal doesnot include a session used for the application and does not include a routeselection policy used for the application; and the terminal initiates the registrationprocedure for the application when the first network slice is the network slicecorresponding to the application.
[00482] In some embodiments, the terminal further receives a cell identifierfrom the network device, where the cell identifier is used for the second cell. Inother words, the terminal receives the cell identifier of the second cell from thenetwork device. In this scenario, that the terminal initiates the registrationprocedure for the application corresponding to the first network slice may include:The terminal accesses the second cell, and initiates a registration procedure for theapplication corresponding to the first network slice via the second cell.
[00483] In the current technology, because the first network slice does notbelong 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. Because theregistration area of the terminal includes the first cell and the second cell, even ifthe terminal moves from the first cell to coverage of the second cell, the terminalstill does not re-initiate a registration procedure, and therefore cannot access thefirst network slice. Based on the solution of this application, the terminal maylearn, from the network device, that the first network slice is available in thesecond cell, and therefore may initiate, when an application of the terminalcorresponds to the first network slice, a registration procedure for the applicationto request to access the first network slice, thereby improving a success rate ofaccessing the first network slice.
[00484] In other words, compared with several scenarios in which the terminalis triggered to initiate a registration procedure in the current technology, a scenarioin which the terminal is triggered to initiate a registration procedure is added inthis application: After the network device notifies the terminal that the firstnetwork slice is available in the second cell, the terminal may initiate aregistration procedure based on an initiated application.
[00485] It may be understood that when the terminal learns, from the networkdevice, that the first network slice is available in the third cell, implementation ofthe terminal is similar to that of the method shown in FIG. 18, and the second cellmay be replaced with the third cell for understanding. For details, refer to theforegoing related description. Details are not described herein again.
[00486] The foregoing describes the network slice-based communicationmethod provided in this application from a perspective of each single device. Thefollowing describes how the foregoing method is applied to a specific procedurefrom a perspective of interaction between devices.
[00487] FIG. 19 is a schematic flowchart of a method for applying the methodsshown in FIG. 11 to FIG. 13 to a specific procedure according to this applicationthrough an example in which a network device is a mobility management device.The method shown in FIG. 19 is applicable to the scenario in FIG. 8a or FIG. 8b.The method includes the following steps:
[00488] S1901: A terminal sends a first message to a first access networkdevice. Correspondingly, the first access network device receives the first messagefrom the terminal.
[00489] The first access network device is an access network device in a firstnetwork. For the first network, refer to related descriptions in step S1101. Detailsare not described herein again.
[00490] In some embodiments, the first message may be an RRC message.
[00491] The first message includes a registration request, the registrationrequest includes information (for example, requested NSSAI) about a networkslice that the terminal requests to access, and the information about the networkslice that the terminal requests to access includes identification information of afirst network slice and identification information of a second network slice.
[00492] In this application, a description is made through an example in whichthe terminal accesses the first network in a first TA of the first access networkdevice and sends the first message to the first access network device. For example,in the scenario in FIG. 8a, the first TA is the TA 1 in FIG. 8a; and in the scenario inFIG. 8b, the first TA is the TA 1 in FIG. 8b.
[00493] S1902: The first access network device sends a registration request to amobility management device. Correspondingly, the mobility management devicereceives the registration request from the first access network device.
[00494] The registration request is received by the first access network devicefrom the terminal in step S1901. Therefore, step S1901 and step S1902 may beunderstood as that the mobility management device receives, via a first accessnetwork device in a first network, information about a network slice that aterminal requests to access.
[00495] In some embodiments, the mobility management device maydetermine a network slice supported by a TA of the first access network device.The network slice supported by the TA of the first access network device may bereported to the mobility management device by the first access network devicewhen establishing or updating an N2 connection to the mobility managementdevice. In this application, a description is made through an example in which themobility management device determines that the first TA of the first accessnetwork device does not support the first network slice but supports the secondnetwork slice.
[00496] S1903: The mobility management device performs slice selection.
[00497] For example, the mobility management device may perform sliceselection by interacting with a network slice selection function network element.
[00498] In step S1903, the mobility management device may determine anetwork slice that the terminal is allowed to access, and specifically maydetermine a network slice that the terminal is allowed to access in the first TA. Inthis application, a description is made through an example in which the networkslice that the terminal is allowed to access includes the second network slice andthe first network slice does not belong to the network slice that the terminal isallowed to access.
[00499] As described above, a network slice that the terminal is rejected toaccess may be referred to as a target network slice, and there may be one or moretarget network slices. For example, the network slice that the terminal requests toaccess further includes a third network slice, and the third network slice is anetwork slice that is allowed to be accessed in the second network. Therefore, inthe first TA of the first network, the third network slice does not belong to thenetwork slice that the terminal is allowed to access. In this scenario, targetnetwork slices include the first network slice and the third network slice.Alternatively, a target network slice may be a network slice that the terminal isrejected to access. For example, the target network slice includes the first networkslice.
[00500] In some embodiments, the mobility management device may storeinformation about the target network slice, and may send, when the mobilitymanagement device serving the terminal is subsequently handed over, theinformation about the target network slice to a mobility management device towhich the handover is made.
[00501] In some embodiments, in step S1903, the mobility management devicemay further determine a network slice that the terminal is rejected to access, andspecifically may determine a network slice that the terminal is rejected to accessin the first TA. In this application, a description is made through an example inwhich the network slice that the terminal is rejected to access includes the firstnetwork slice. Further, the network slice that the terminal is rejected to access mayfurther include the third network slice.
[00502] In some embodiments, in step S1903, the mobility management devicemay further determine a network slice that the terminal is allowed to access in thefirst network. In this application, a description is made through an example inwhich the network slice that the terminal is allowed to access in the first networkincludes the first network slice or the first network slice is a network slice that theterminal is allowed to access in the first network. Further, an example in which thesecond TA in the first network supports the first network slice is used fordescription.
[00503] In other words, the first network slice is a network slice that theterminal is allowed to access in the first network but does not belong to a networkslice that the terminal is allowed to access in the first TA.
[00504] In some embodiments, in step S1903, the mobility management devicemay further determine network slices that the terminal is allowed to access bysubscription. In this application, a description is made through an example inwhich the network slices that the terminal is allowed to access by subscriptioninclude: the first network slice, the second network slice, the third network slice,and a fourth network slice. The fourth network slice is also a network slice thatthe terminal is allowed to access in the first network.
[00505] S1904: The mobility management device determines a registration area.
[00506] For a feature of the registration area, refer to the description in themethod shown in FIG. 11, FIG. 12, or FIG. 13. Details are not described hereinagain.
[00507] In some embodiments, the mobility management device maydetermine the registration area based on the network slice that the terminal isallowed to access and the network slice that the terminal is rejected to access.Alternatively, the mobility management device may further determine theregistration area with reference to one or more of a network slice supportcapability of the access network device managed by the mobility managementdevice, a network slice that the terminal is allowed to access in the first network,and a network slice that the terminal is allowed to access by subscription.Alternatively, it may be understood that the mobility management device maydetermine the registration area based on the network slice that the terminal isallowed to access and the target network slice. A method for determining aregistration area by the mobility management device is not specifically limited inthis application.
[00508] S1905: The mobility management network element sends a secondmessage to the first access network device. Correspondingly, the first accessnetwork device receives the second message from the mobility managementnetwork element.
[00509] The second message includes information about the registration area.Further, the second message further includes information about the network slicethat the terminal is allowed to access.
[00510] In some embodiments, the second message may be an N2 message.
[00511] S1906: The first access network device sends information about theregistration area to the terminal. Correspondingly, the terminal receives theinformation about the registration area from the first access network device.
[00512] In some embodiments, the first access network device further sends, tothe terminal, the information about the network slice that the terminal is allowedto access.
[00513] S1907: Another registration procedure.
[00514] After step S1907, the registration procedure is completed, and theterminal accesses the second network slice.
[00515] S1908: Hand over the terminal to a second access network device dueto movement.
[00516] For example, the TA of the second access network device includes thesecond TA. As described in step S1903, the second TA supports the first networkslice. For example, in the scenario in FIG. 8a, the second TA is the TA 2 in FIG. 8a;and in the scenario in FIG. 8b, the second TA is the TA 2 in FIG. 8b. Because theregistration area excludes a tracking area that supports the first network slice andthe second network slice, or excludes a tracking area of an access network devicethat supports the first network slice and the second network slice, the second TA isoutside the registration area. In this case, the terminal may perform step S1909because of moving out of the RA.
[00517] S1909: Re-initiate a registration procedure.
[00518] In some embodiments, the re-initiated registration procedure isinitiated by the terminal, and in the re-initiated registration procedure, a networkslice that the terminal requests to access may include the first network slice.Certainly, the network slice that the terminal requests to access may alternativelynot include the first network slice. For example, after being handed over to thesecond access network device, the terminal no longer needs to access the firstnetwork slice. This is not specifically limited in this application.
[00519] Based on this solution, when determining the registration area, themobility management device excludes the tracking area that supports the networkslice that the terminal is allowed to access and the target network slice, orexcludes the tracking area of the access network device that supports the networkslice that the terminal is allowed to access and the target network slice. Therefore,when the terminal moves within the excluded tracking area, because theregistration area of the terminal does not include the tracking area, and thetracking area supports the target network slice, the terminal may re-initiate aregistration procedure to request to access the target network slice, to increase asuccess rate of accessing the target network slice.
[00520] FIG. 20 and FIG. 21 are schematic flowcharts of methods for applyingthe method shown in FIG. 14 to a specific procedure when a network device is amobility management device according to this application. The method shown inFIG. 20 or FIG. 21 is applicable to the scenario in FIG. 8b or FIG. 8c. The methodincludes the following steps:
[00521] S2001: A terminal sends a first message to a first access networkdevice. Correspondingly, the first access network device receives the first messagefrom the terminal.
[00522] The terminal sends the first message to the first access network devicevia a first cell of the first access network device. That is to say, the terminalaccesses a network in the first cell. The first cell is a cell in a first TA of the firstaccess network device.
[00523] The first message includes a registration request, the registrationrequest includes information (for example, requested NSSAI) about a networkslice that the terminal requests to access, and the information about the networkslice that the terminal requests to access includes identification information of afirst network slice. That is to say, the first network slice is included in a networkslice that the terminal requests to access in the first cell. Further, the informationabout the network slice that the terminal requests to access may further includeidentification information of the second network slice.
[00524] In some embodiments, the first access network device may be anaccess network device in a first network. For the first network, refer to theforegoing related description. Details are not described herein again.
[00525] S2002: The first access network device sends a registration request to amobility management device. Correspondingly, the mobility management devicereceives the registration request from the first access network device.
[00526] The registration request is received by the first access network devicefrom the terminal in step S2001. Therefore, step S2001 and step S2002 may beunderstood as that the mobility management device receives, via the first cell, theinformation about the network slice that the terminal requests to access.
[00527] S2003: The mobility management device performs slice selection.
[00528] For example, the mobility management device may perform sliceselection by interacting with a network slice selection function network element.
[00529] In step S2003, the mobility management device may determine anetwork slice that the terminal is allowed to access, and specifically maydetermine a network slice that the terminal is allowed to access in the first cell. Inthis application, a description is made through an example in which the networkslice that the terminal is allowed to access in the first cell includes the secondnetwork slice.
[00530] In some embodiments, after the mobility management devicedetermines the network slice that the terminal is allowed to access in the first cell,the mobility management device may determine whether the first network slicebelongs to the network slice that the terminal is allowed to access in the first cell.In this application, a description is made through an example in which themobility management device can learn that the first network slice does not belongto the network slice that the terminal is allowed to access in the first cell.
[00531] So far, the mobility management device may determine the firstnetwork slice. Therefore, S2001 to S2003 may be understood as specificimplementation of determining the first network slice by the mobilitymanagement device.
[00532] As described above, a network slice that the terminal is rejected toaccess in the first cell may be referred to as a target network slice, and there maybe one or more target network slices. For example, the network slice that theterminal requests to access in the first cell further includes a third network slice,and the third network slice is a network slice that is allowed to be accessed in thesecond network. Therefore, in the first cell of the first network, the third networkslice does not belong to the network slice that the terminal is allowed to access.Alternatively, a target network slice may be a network slice that the terminal isrejected to access. For example, the target network slice includes the first networkslice.
[00533] In some embodiments, in step S2003, the mobility management devicemay further determine a network slice configured for the terminal in the firstnetwork. In this application, a description is made through an example in whichthe network slice configured for the terminal in the first network includes the firstnetwork slice or the first network slice is included in the network slice configuredfor the terminal in the first network.
[00534] The mobility management device further determines a registration areaof the terminal. In this application, a description is made through an example inwhich the registration area of the terminal includes the first cell and the secondcell. The second cell may belong to the first access network device, that is, thefirst cell and the second cell belong to a same access network device; or thesecond cell may belong to the second access network device, that is, the first celland the second cell belong to different access network devices.
[00535] S2004: The mobility management device stores identificationinformation of a target network slice, where the target network slice includes afirst network slice.
[00536] In some embodiments, the mobility management device serving theterminal may send, when being subsequently handed over, the identificationinformation of the target network slice to a mobility management device to whichthe handover is made. When the mobility management device serving the terminalis handed over, the mobility management network element after step S2004 maybe considered as the mobility management network element to which thehandover is made.
[00537] S2005: The mobility management network element sends a secondmessage to the first access network device. Correspondingly, the first accessnetwork device receives the second message from the mobility managementnetwork element.
[00538] The second message includes information about the network slice thatthe terminal is allowed to access.
[00539] In some embodiments, the second message may be an N2 message.
[00540] It should be noted that step S2005 and step S2004 are not performed ina necessary sequence. Step S2004 may be performed first, and then step S2005 isperformed. Alternatively, step S2005 may be performed first, and then step S2004is performed. Alternatively, step S2004 and step S2005 may be simultaneouslyperformed. This is not specifically limited in this application.
[00541] S2006: The first access network device sends, to the terminal,information about a network slice that the terminal is allowed to access.Correspondingly, the terminal receives, from the first access network device, theinformation about the network slice that the terminal is allowed to access.
[00542] S2007: Another registration procedure.
[00543] After step S2007, the registration procedure is completed, and theterminal accesses the second network slice.
[00544] S2008: Perform handover, to hand over the terminal from a first cell toa second cell.
[00545] The second cell is a cell in the second TA.
[00546] In some embodiments, when the second cell belongs to the secondaccess network device, and the handover type is Xn handover, after step S2008,handover of the terminal in the access network is completed, and step S2009acontinues to be performed.
[00547] In some embodiments, when the second cell belongs to the secondaccess network device, and the handover type is N2 handover, after step S2008,the first access network device determines to trigger N2 handover, and stepS2009b continues to be performed.
[00548] It may be understood that when the second cell belongs to the firstaccess network device, steps S2009a and S2009b are not performed.
[00549] S2009a: The second access network device sends a path switch requestmessage to the mobility management device. Correspondingly, the mobilitymanagement device receives the path switch request message from the secondaccess network device.
[00550] After the mobility management device receives the path switch requestmessage from the second access network device, step S2011 may be performed.
[00551] S2009b: The first access network device sends a handover requiredmessage to the mobility management device. Correspondingly, the mobilitymanagement device receives the handover required message from the first accessnetwork device.
[00552] The handover required message includes the identifier of the secondaccess network device, so that the mobility management device can learn thesecond access network device to which the handover is made.
[00553] After the mobility management device receives the handover requiredmessage from the first access network device, step S2011 may be performed.
[00554] S2010: Remaining handover procedure.
[00555] For details, refer to the method procedure shown in FIG. 5 or FIG. 6, orrefer to the handover procedure defined in the protocol. Details are not describedherein again.
[00556] It should be noted that S2010 may be performed in parallel with stepS2011 to step S2014 and certainly may alternatively be performed in anothersequence. This is not specifically limited in this application.
[00557] S2011: The mobility management network element determines a targetnetwork slice available in the second cell.
[00558] It may be understood that the target network slice available in thesecond cell in step S2011 may be a subset of the target network slice in stepS2004. For example, the target network slice in step S2004 includes the firstnetwork slice and the third network slice, and the target network slice available inthe second cell in step S2011 is the first network slice. That is to say, in thisapplication, a description is made through an example in which the mobilitymanagement network element determines that the first network slice is availablein the second cell or determines that the target network slice available in thesecond cell includes the first network slice.
[00559] In other words, when the second cell belongs to the second accessnetwork device, and the handover type is Xn handover, that the mobilitymanagement device determines that the first network slice is available in thesecond cell may include: The mobility management network element determines,when receiving a path switch request message from the second access networkdevice, that the first network slice is available in the second cell.
[00560] When the second cell belongs to the second access network device,and the handover type is N2 handover, that the mobility management networkelement determines that the first network slice is available in the second cell mayinclude: The mobility management network element determines, when receivingthe handover required message from the first access network device, that the firstnetwork slice is available in the second cell.
[00561] In other words, when the second cell belongs to the second accessnetwork device, the path switch request message or the handover requiredmessage may be used as a trigger condition for the mobility management deviceto determine that the first network slice is available in the second cell.
[00562] In different embodiments of this application, manners in which themobility management device determines a target network slice available in thesecond cell may also be different. For example:
[00563] In some embodiments, that the mobility management devicedetermines a target network slice available in the second cell includes: Themobility management device queries the context of the target access networkdevice, and determines whether the network slice supported by the tracking areaof the target access network device includes the target network slice.
[00564] When the second cell belongs to the second access network device, atarget access network device is the second access network device; or when thesecond cell belongs to the first access network device, a target access networkdevice is the first access network device.
[00565] In this application, a description is made through an example in whichthe context of the target access network device indicates that the network slicesupported by the tracking area of the target access network device includes thefirst network slice or the context of the target access network device indicates thatthe tracking area of the target access network device supports the first networkslice. In this scenario, the second cell is a cell in the tracking area of the targetaccess network device. For example, the second cell is a cell in the second TA ofthe target access network device.
[00566] In some other embodiments, refer to FIG. 21. For example, the targetaccess network device is a second access network device. That the mobilitymanagement device determines a target network slice available in the second cellincludes:
[00567] S2011a: The mobility management device sends, to a target accessnetwork device, identification information of a target network slice supported by atracking area of the target access network device. Correspondingly, the targetaccess network device receives, from the mobility management device, theidentification information of the target network slice supported by the trackingarea of the target access network device.
[00568] It is assumed that the target network slice in step S2004 includes thefirst network slice and the third network slice. In this application, a description ismade through an example in which the tracking area of the target access networkdevice supports the first network slice but does not support the third network sliceand the identification information of the first network slice is sent by the mobilitymanagement device in step S2011a.
[00569] S2011b: The target access network device determines, based on ameasurement report reported by the terminal, whether the terminal can access thefirst network slice in the second cell.
[00570] In some embodiments, the target access network device firstdetermines whether the second TA in which the second cell is located supports thefirst network slice. In this application, an example in which the second TAsupports the first network slice is used for description. Then, the target accessnetwork device may determine, based on cell signal quality in the measurementreport, whether the terminal can access the first network slice in the second cell.
[00571] In an example, the cell signal quality may be measured through one ormore of received signal code power (RSCP), reference signal received power(RSRP), reference signal received quality (RSRQ), a signal to noise ratio (SNR), asignal to interference plus noise ratio (SINR), and a reference signal strengthindicator (RSSI). This is not specifically limited in this application.
[00572] In an example, when cell signal quality corresponding to the secondcell is greater than the first threshold, the target access network device determinesthat the terminal can access the first network slice in the second cell.
[00573] In an example, the target access network device may perform stepS2011b immediately after S2011a; or may perform step S2011b at any time afterS2011a, so that step S2011c is performed after step S2011b is performed at anytime.
[00574] S2011c: The target access network device sends notificationinformation to the mobility management device. Correspondingly, the mobilitymanagement device receives the notification information from the target accessnetwork device.
[00575] The notification information is for notifying that the terminal canaccess the first network slice in the second cell. Therefore, the mobilitymanagement device learns, from the target access network device, that theterminal can access the first network slice in the second cell.
[00576] In an example, when the target network slice supported by the trackingarea of the target access network device in step S2011a includes only the firstnetwork slice, the notification information may be information of 1 bit. Forexample, when a value of the bit is "1", the terminal is notified that the terminalcan access the first network slice in the second cell; or when a value of the bit is"0", the terminal is notified that the terminal can access the first network slice inthe second cell.
[00577] In another example, when the target network slice supported by thetracking area of the target access network device in step S2011a includes aplurality of network slices, the notification information may include identificationinformation of the first network slice.
[00578] In still another example, when the target network slice supported bythe tracking area of the target access network device in step S2011a includes aplurality of network slices, the notification information may include a bitmap. Aquantity of bits included in the bitmap is equal to a quantity of target networkslices supported by the tracking area of the target access network device, differentbits correspond to different target network slices, and a value of a bit is used tonotify, to the terminal, whether the terminal can access a corresponding targetnetwork slice in the second cell.
[00579] For example, the target network slices supported by the tracking areaof the target access network device in step S2011a include a network slice 1 and anetwork slice 2. The target access network device determines that the terminal canaccess the network slice 1 but cannot access the network slice 2 in the second cell.In this case, the bitmap may include two bits. The first bit corresponds to thenetwork slice 1, and the second bit corresponds to the network slice 2. Forexample, the bitmap may be "10", to notify the terminal that the terminal canaccess the network slice 1 but cannot access the network slice 2 in the second cell.
[00580] It may be understood that step S2011a to step S2011c are alsoapplicable to a scenario in which the target access network device is the firstaccess network device.
[00581] That is to say, that the mobility management device determines that thefirst network slice is available in the second cell includes: The mobilitymanagement device sends the identification information of the first network sliceto the target access network device, and learns, from the target access networkdevice, that the terminal can access the first network slice in the second cell.
[00582] Based on this solution, after determining the first network slicesupported by the tracking area of the target access network device, the mobilitymanagement device further confirms, to the target access network device, whetherthe terminal can access the first network slice supported by the tracking area ofthe target access network device, to prevent the mobility management device fromnotifying, when the target access network device supports the first network slicebut the terminal cannot access the first network slice in the second cell, theterminal that the first network slice is available in the second cell, therebyimproving a success rate of accessing the first network slice by the terminal in thesecond cell.
[00583] S2012: The mobility management device notifies the terminal that thefirst network slice is available in the second cell.
[00584] In some embodiments, the mobility management device may send aNAS message to the terminal, and notify the terminal via the NAS message thatthe first network slice is available in the second cell. For a notification manner,refer to step S2011c. Details are not described herein again.
[00585] Optionally, after step S2012, the network slice-based communicationmethod may further include steps S2013 and S2014:
[00586] S2013: The terminal sends indication information to the mobilitymanagement device. Correspondingly, the mobility management device receivesthe indication information from the terminal.
[00587] In some embodiments, the indication information indicates that theterminal no longer requests to access the first network slice.
[00588] S2014: The mobility management device deletes the identificationinformation of the first network slice based on the indication information.
[00589] In some embodiments, when the indication information indicates thatthe terminal no longer requests to access the first network slice, the mobilitymanagement device deletes the identification information of the first network slice.When subsequently serving the terminal, the mobility management device may nolonger notify the terminal of a cell that can access the first network slice, therebyreducing signaling overheads and reducing resource waste.
[00590] Based on this solution, when the terminal is handed over from the firstcell to the second cell, and the mobility management device determines that thefirst network slice is available in the second cell, the terminal is notified that thefirst network slice is available in the second cell, so that when still intending toaccess the first network slice, the terminal may initiate a registration procedure torequest to access the first network slice, thereby improving a success rate ofaccessing the first network slice, and using a service provided by the first networkslice.
[00591] FIG. 22 is a schematic flowchart of a method for applying the methodshown in FIG. 14 to a specific procedure when a second cell belongs to a firstaccess network device and a network device is the first access network deviceaccording to this application. The method shown in FIG. 22 is applicable to thescenario in FIG. 8c. The method includes the following steps:
[00592] S2201 to S2207: They are the same as steps S2001 to S2007 shown inFIG. 20. For details, refer to the foregoing related description. Details are notdescribed herein again.
[00593] S2208: Perform handover, to hand over the terminal from a first cell toa second cell.
[00594] The second cell is a cell in the second TA, and the second cell belongsto the first access network device. After S2208 ends, it may be considered that theterminal completes the handover from the first cell to the second cell.
[00595] S2209: The mobility management device sends, to the first accessnetwork device, the identification information that is of the target network sliceand that is stored in step S2204. Correspondingly, the first access network devicereceives the identification information of the target network slice from themobility management device.
[00596] For example, the target network slice stored in S2204 includes the firstnetwork slice and the third network slice. In S2209, the mobility managementdevice sends the identification information of the first network slice and theidentification information of the third network slice to the first access networkdevice.
[00597] It should be noted that step S2209 and step S2208 are not performed ina necessary sequence. Step S2208 may be performed first, and then step S2209 isperformed. Alternatively, step S2209 may be performed first, and then step S2208is performed. Alternatively, step S2208 and step S2209 may be simultaneouslyperformed. This is not specifically limited in this application.
[00598] For example, when step S2209 is performed before step S2208 isperformed, in step S2209, the first access network device may determine the firstnetwork slice. With reference to steps S2201 to S2209, that the first accessnetwork device determines the first network slice includes: The first accessnetwork device sends, to the mobility management network element, informationabout a network slice that the terminal requests to access, where the informationabout the network slice that the terminal requests to access includes identificationinformation of the first network slice; and then the first access network devicelearns, from the mobility management device, that the first network slice does notbelong to the network slice that the terminal is allowed to access in the first cell.In other words, the first access network device may learn, from the mobilitymanagement device in the foregoing registration procedure, that the first networkslice does not belong to the network slice that the terminal is allowed to access inthe first cell.
[00599] It may be understood that a feature of the first network slice and / or anoperation performed on the first network slice is also applicable to the thirdnetwork slice. For details, refer to the related description of the first network slice.Details are not described herein again.
[00600] S2210: The first access network device determines a target networkslice supported by a tracking area of the first access network device.
[00601] In some embodiments, the first access network device may determine,based on a network slice support capability that is recorded by the first accessnetwork device, the target network slice supported by the tracking area of the firstaccess network device.
[00602] In an example, when the target network slice in step S2209 includesthe first network slice and the third network slice, it is assumed that the trackingarea of the first access network device supports the first network slice but does notsupport the third network slice. In this case, the target network slice that issupported by the tracking area of the first access network device and that isdetermined by the first access network device in step S2210 is the first networkslice.
[00603] S2211: The first access network device determines that the firstnetwork slice is available in the second cell.
[00604] In some embodiments, that the first access network device determinesthat the first network slice is available in the second cell includes: The first accessnetwork device determines that the terminal can access the first network slice inthe second cell. For a method for determining, by the first access network device,that the terminal can access the first network slice in the second cell, refer torelated descriptions in step S2011b. Details are not described herein again.
[00605] S2212: The first access network device notifies the terminal that thefirst network slice is available in the second cell.
[00606] In some embodiments, that the first access network device notifies theterminal that the first network slice is available in the second cell includes: Thefirst access network device notifies, via the mobility management device, theterminal that the first network slice is available in the second cell. For example,step S2212 may include S2212a and S2212b:
[00607] S2212a: The first access network device sends notification informationto the mobility management device. Correspondingly, the mobility managementdevice receives the notification information from the target access network device.
[00608] For step S2212a, refer to the related description in step S2011c. Detailsare not described herein again.
[00609] S2212b: The mobility management device notifies the terminal that thefirst network slice is available in the second cell.
[00610] For step S2212b, refer to the related description in step S2012. Detailsare not described herein again.
[00611] In some other embodiments, the first access network device may notify,via an RRC message, the terminal that the first network slice is available in thesecond cell.
[00612] Optionally, after step S2212, the network slice-based communicationmethod may further include steps S2213 and S2214. Steps S2213 and S2214 arethe same as steps S2013 and S2014. For details, refer to related descriptions ofsteps S2013 and S2014. Details are not described herein again.
[00613] By using the method in FIG. 22, when determining that the firstnetwork slice is available in the second cell, the first access network devicenotifies the terminal that the first network slice is available in the second cell. Fora technical effect brought by the method shown in FIG. 22, refer to the technicaleffect brought by the method shown in FIG. 20. Details are not described hereinagain.
[00614] FIG. 23 is a schematic flowchart of a method for applying the methodshown in FIG. 14 to a specific procedure when a second cell belongs to a secondaccess network device and a network device is the second access network deviceaccording to this application. The method shown in FIG. 23 is applicable to thescenario in FIG. 8b. The method includes the following steps:
[00615] S2301 to S2310: They are the same as steps S2001 to S2010 shown inFIG. 20. For details, refer to the related description in FIG. 20. Details are notdescribed herein again.
[00616] S2311: The mobility management device sends, to the second accessnetwork device, the identification information that is of the target network sliceand that is stored in step S2304. Correspondingly, the second access networkdevice receives the identification information of the target network slice from themobility management device.
[00617] A manner in which the mobility management device sends theidentification information of the target network slice to the second access networkdevice is similar to the manner in which the mobility management device sendsthe identification information of the target network slice to the first accessnetwork device in step S2209 in FIG. 22. For details, refer to related descriptionsin step S2209. Details are not described herein again. A difference from FIG. 22lies in that in an inter-eNodeB handover scenario, the mobility managementdevice may send the identification information of the target network slice to thesecond access network device after receiving the path switch request message orthe handover required message.
[00618] S2312: The second access network device determines a target networkslice supported by a tracking area of the second access network device.
[00619] In some embodiments, the second access network device maydetermine, based on a network slice support capability that is locally recorded bythe second access network device, the target network slice supported by thetracking area of the second access network device.
[00620] In an example, when the target network slice in step S2311 includesthe first network slice and the third network slice, it is assumed that the trackingarea of the second access network device supports the first network slice but doesnot support the third network slice. In this case, the target network slice that issupported by the tracking area of the second access network device and that isdetermined by the second access network device in step S2312 is the first networkslice.
[00621] S2313: The second access network device determines that the firstnetwork slice is available in the second cell.
[00622] In some embodiments, that the second access network devicedetermines that the first network slice is available in the second cell includes: Thesecond access network device determines that the terminal can access the firstnetwork slice in the second cell. For a method for determining, by the secondaccess network device, that the terminal can access the first network slice in thesecond cell, refer to related descriptions in step S2011b. Details are not describedherein again.
[00623] S2314: The second access network device notifies the terminal that thefirst network slice is available in the second cell.
[00624] A manner in which the second access network device notifies theterminal that the first network slice is available in the second cell is similar to themanner in which the first access network device notifies the terminal that the firstnetwork slice is available in the second cell in step S2212 in FIG. 22. For details,refer to related descriptions in step S2212. Details are not described herein again.
[00625] Optionally, after step S2314, the network slice-based communicationmethod may further include steps S2315 and S2316. Steps S2315 and S2316 arethe same as steps S2013 and S2014. For details, refer to related descriptions ofsteps S2013 and S2014. Details are not described herein again.
[00626] By using the method in FIG. 23, when determining that the firstnetwork slice is available in the second cell, the second access network devicenotifies the terminal that the first network slice is available in the second cell. Fora technical effect brought by the method shown in FIG. 23, refer to the technicaleffect brought by the method shown in FIG. 20. Details are not described hereinagain.
[00627] FIG. 24 is a schematic flowchart of a method for applying the methodin FIG. 15 to a specific procedure when a network device is a mobilitymanagement device according to this application. The method shown in FIG. 24 isapplicable to the scenario in FIG. 8a. The method includes the following steps:
[00628] S2401 to S2407: They are the same as steps S2001 to S2007 shown inFIG. 20. For details, refer to the related descriptions of steps S2001 to S2007.Details are not described herein again.
[00629] S2408: Perform handover, to hand over the terminal from a first cell toa second cell.
[00630] The second cell is a cell in the second TA. A third cell whose physicalcoverage is the same as that of the second cell exists under the access networkdevice to which the second cell belongs, and the third cell is a cell in the third TA.
[00631] In some embodiments, when the second cell belongs to the secondaccess network device, and the handover type is Xn handover, after step S2408,handover of the terminal in the access network is completed, and step S2409acontinues to be performed.
[00632] In some embodiments, when the second cell belongs to the secondaccess network device, and the handover type is N2 handover, after step S2408,the first access network device determines to trigger N2 handover, and stepS2409b continues to be performed.
[00633] It may be understood that when the second cell belongs to the firstaccess network device, steps S2409a and S2409b are not performed.
[00634] S2409a: It is similar to step S2009a shown in FIG. 20. For details, referto related descriptions of step S2009a. Details are not described herein again.After the mobility management device receives the path switch request messagefrom the second access network device, step S2411 is performed.
[00635] S2409b: It is similar to step S2009b shown in FIG. 20. For details,refer to related descriptions of step S2009b. Details are not described herein again.After the mobility management device receives the handover required messagefrom the first access network device, step S2411 is performed.
[00636] S2410: It is the same as step S2010 shown in FIG. 20. For details, referto related descriptions of step S2010. Details are not described herein again.
[00637] S2411: The mobility management network element determines a targetnetwork slice available in the third cell.
[00638] For the description of the target network slice available in the third cell,refer to the description of the target network slice available in the second cell instep S2011. Details are not described herein again.
[00639] In different embodiments of this application, manners in which themobility management device determines a target network slice available in thethird cell may also be different. For example:
[00640] In some embodiments, that the mobility management devicedetermines a target network slice available in the third cell includes: The mobilitymanagement device queries the context of the target access network device, anddetermines whether the network slice supported by the tracking area of the targetaccess network device includes the target network slice.
[00641] When the second cell belongs to the second access network device, atarget access network device is the second access network device; or when thesecond cell belongs to the first access network device, a target access networkdevice is the first access network device.
[00642] In this application, a description is made through an example in whichthe context of the target access network device indicates that a tracking area (thatis, the third TA) in which the third cell is located supports the first network slicebut a tracking area (that is, the second TA) in which the second cell is located doesnot support the first network slice. The second TA and the third TA are TAs of thetarget access network device, and the second cell and the third cell are cells of thetarget access network device.
[00643] In some other embodiments, that the mobility management devicedetermines a target network slice available in the third cell includes:
[00644] S2411a: The mobility management device sends, to a target accessnetwork device, identification information of a target network slice supported by atracking area of the target access network device. Correspondingly, the targetaccess network device receives, from the mobility management device, theidentification information of the target network slice supported by the trackingarea of the target access network device.
[00645] For details, refer to the related description in step S2011a. Details arenot described herein again.
[00646] S2411b: The target access network device determines, based on ameasurement report reported by the terminal, whether the terminal can access thefirst network slice in the third cell.
[00647] In some embodiments, the target access network device firstdetermines whether the third TA in which the third cell is located supports the firstnetwork slice. In this application, an example in which the third TA supports thefirst network slice is used for description. Then, the target access network devicemay determine, based on cell signal quality in the measurement report, whetherthe terminal can access the first network slice in the third cell. For details, refer tothe related description in step S2011b. Details are not described herein again.
[00648] S2411c: The target access network device sends notificationinformation to the mobility management device. Correspondingly, the mobilitymanagement device receives the notification information from the target accessnetwork device.
[00649] The notification information is for notifying that the terminal canaccess the first network slice in the third cell. For a notification manner, refer tostep S2011c. Details are not described herein again.
[00650] That is to say, that the mobility management device determines that thefirst network slice is available in the third cell includes: The mobility managementdevice sends the identification information of the first network slice to the targetaccess network device, and learns, from the target access network device, that theterminal can access the first network slice in the third cell.
[00651] S2412: The mobility management device notifies the terminal that thefirst network slice is available in the third cell.
[00652] In some embodiments, the mobility management device may send aNAS message to the terminal, and notify the terminal via the NAS message thatthe first network slice is available in the third cell. For a notification manner, referto step S2012. Details are not described herein again.
[00653] In some embodiments, after the mobility management device notifiesthe terminal that the first network slice is available in the third cell, the terminallearns that the first network slice is available in the third cell. In this scenario, theterminal may perform cell reselection by itself, to access the third cell, and accessthe first network slice via the third cell; or the terminal may initiate a registrationrequest in the second cell to request to access the first network slice. Then, thetarget access network device redirects the terminal to the third cell via an RRCconnection release message, so that the terminal accesses the first network slicevia the third cell. For details, refer to the procedure shown in FIG. 5. Details arenot described herein again.
[00654] Optionally, after step S2412, the network slice-based communicationmethod may further include steps S2413 and S2414. Steps S2413 and S2414 arethe same as steps S2013 and S2014. For details, refer to the foregoing relateddescriptions. Details are not described herein again.
[00655] Based on this solution, when the terminal is handed over from the firstcell to the second cell, and the mobility management device determines that thefirst network slice is available in the third cell, the terminal is notified that the firstnetwork slice is available in the third cell, so that when still intending to accessthe first network slice, the terminal may access the first network slice in the thirdcell, thereby improving a success rate of accessing the first network slice, andusing a service provided by the first network slice.
[00656] FIG. 25 is a schematic flowchart of a method for applying the methodshown in FIG. 15 to a specific procedure when a second cell belongs to a firstaccess network device and a network device is the first access network deviceaccording to this application. The method includes the following steps:
[00657] S2501 to S2507: They are the same as steps S2201 to S2207 shown inFIG. 22. For details, refer to the related descriptions of steps S2201 to S2207.Details are not described herein again.
[00658] S2508: Perform handover, to hand over the terminal from a first cell toa second cell.
[00659] The second cell is a cell in the second TA. A third cell whose physicalcoverage is the same as that of the second cell exists under the first accessnetwork device to which the second cell belongs, and the third cell is a cell in thethird TA.
[00660] After S2508 ends, it may be considered that the terminal completes thehandover from the first cell to the second cell.
[00661] S2509: The mobility management device sends, to the first accessnetwork device, the identification information that is of the target network sliceand that is stored in step S2504. Correspondingly, the first access network devicereceives the identification information of the target network slice from themobility management device.
[00662] For details, refer to the related description in step S2209. Details arenot described herein again.
[00663] S2510: The first access network device determines a target networkslice supported by a tracking area of the first access network device.
[00664] For details, refer to the related description in step S2210. Details arenot described herein again.
[00665] S2511: The first access network device determines that the firstnetwork slice is available in the third cell.
[00666] In some embodiments, that the first access network device determinesthat the first network slice is available in the third cell includes: The first accessnetwork device determines that the terminal can access the first network slice inthe third cell. For a method for determining, by the first access network device,that the terminal can access the first network slice in the third cell, refer to relateddescriptions in step S2411b. Details are not described herein again.
[00667] S2512: The first access network device notifies the terminal that thefirst network slice is available in the third cell.
[00668] For a notification manner, refer to the manner in which the first accessnetwork device notifies the terminal that the first network slice is available in thesecond cell in step S2212. Details are not described herein again.
[00669] In some embodiments, after the first access network device notifies theterminal that the first network slice is available in the third cell, the terminallearns that the first network slice is available in the third cell. In this scenario, theterminal may perform cell reselection by itself, to access the third cell, and accessthe first network slice via the third cell; or the terminal may initiate a registrationrequest in the second cell to request to access the first network slice. Then, thetarget access network device redirects the terminal to the third cell via an RRCconnection release message, so that the terminal accesses the first network slicevia the third cell. For details, refer to the procedure shown in FIG. 5. Details arenot described herein again.
[00670] Optionally, after step S2512, the network slice-based communicationmethod may further include steps S2513 and S2514. Steps S2513 and S2514 arethe same as steps S2013 and S2014. For details, refer to related descriptions ofsteps S2013 and S2014. Details are not described herein again.
[00671] By using the method in FIG. 25, when determining that the firstnetwork slice is available in the third cell, the first access network device notifiesthe terminal that the first network slice is available in the third cell. For a technicaleffect brought by the method shown in FIG. 25, refer to the technical effectbrought by the method shown in FIG. 24. Details are not described herein again.
[00672] FIG. 26 is a schematic flowchart of a method for applying the methodshown in FIG. 15 to a specific procedure when a second cell belongs to a secondaccess network device and a network device is the second access network deviceaccording to this application. The method shown in FIG. 26 is applicable to thescenario in FIG. 8a. The method includes the following steps:
[00673] S2601 to S2607: They are the same as steps S2001 to S2007 shown inFIG. 20. For details, refer to the related descriptions of steps S2001 to S2007.Details are not described herein again.
[00674] S2608: Perform handover, to hand over the terminal from a first cell toa second cell.
[00675] The second cell is a cell in the second TA. A third cell whose physicalcoverage is the same as that of the second cell exists under the access networkdevice to which the second cell belongs, and the third cell is a cell in the third TA.
[00676] In some embodiments, when the second cell belongs to the secondaccess network device, and the handover type is Xn handover, after step S2608,handover of the terminal in the access network is completed, and step S2609acontinues to be performed.
[00677] In some embodiments, when the second cell belongs to the secondaccess network device, and the handover type is N2 handover, after step S2608,the first access network device determines to trigger N2 handover, and stepS2609b continues to be performed.
[00678] S2609a: It is similar to step S2009a shown in FIG. 20. For details, referto related descriptions of step S2009a. Details are not described herein again.After the mobility management device receives the path switch request messagefrom the second access network device, step S2411 is performed.
[00679] S2609b: It is similar to step S2009b shown in FIG. 20. For details,refer to related descriptions of step S2009b. Details are not described herein again.After the mobility management device receives the handover required messagefrom the first access network device, step S2411 is performed.
[00680] S2610: It is the same as step S2010 shown in FIG. 20. For details, referto related descriptions of step S2010. Details are not described herein again.
[00681] S2611: The mobility management device sends, to the second accessnetwork device, the identification information that is of the target network sliceand that is stored in step S2604. Correspondingly, the second access networkdevice receives the identification information of the target network slice from themobility management device.
[00682] S2612: The second access network device determines a target networkslice supported by a tracking area of the second access network device.
[00683] For details, refer to the related description in steps S2311 and S2312.Details are not described herein again.
[00684] S2613: The second access network device determines that the firstnetwork slice is available in the third cell.
[00685] In some embodiments, that the second access network devicedetermines that the first network slice is available in the third cell includes: Thesecond access network device determines that the terminal can access the firstnetwork slice in the third cell. For a method for determining, by the second accessnetwork device, that the terminal can access the first network slice in the third cell,refer to related descriptions in step S2411b. Details are not described herein again.
[00686] S2614: The second access network device notifies the terminal that thefirst network slice is available in the third cell.
[00687] For a notification manner, refer to the manner in which the first accessnetwork device notifies the terminal that the first network slice is available in thesecond cell in step S2212. Details are not described herein again.
[00688] In some embodiments, after the second access network device notifiesthe terminal that the first network slice is available in the third cell, the terminallearns that the first network slice is available in the third cell. In this scenario, theterminal may perform cell reselection by itself, to access the third cell, and accessthe first network slice via the third cell; or the terminal may initiate a registrationrequest in the second cell to request to access the first network slice. Then, thetarget access network device redirects the terminal to the third cell via an RRCconnection release message, so that the terminal accesses the first network slicevia the third cell. For details, refer to the procedure shown in FIG. 5. Details arenot described herein again.
[00689] Optionally, after step S2614, the network slice-based communicationmethod may further include steps S2615 and S2616. Steps S2615 and S2616 arethe same as steps S2013 and S2014. For details, refer to related descriptions ofsteps S2013 and S2014. Details are not described herein again.
[00690] By using the method in FIG. 26, when determining that the firstnetwork slice is available in the third cell, the second access network devicenotifies the terminal that the first network slice is available in the third cell. For atechnical effect brought by the method shown in FIG. 26, refer to the technicaleffect brought by the method shown in FIG. 24. Details are not described hereinagain.
[00691] FIG. 27 is a schematic flowchart of a method for applying the methodin FIG. 16 to a specific procedure when a network device is a mobilitymanagement device according to this application. The method includes thefollowing steps:
[00692] S2701: A terminal sends a first message to a first access networkdevice. Correspondingly, the first access network device receives the first messagefrom the terminal.
[00693] The terminal sends the first message to the first access network devicevia a first cell of the first access network device. That is to say, the terminalaccesses a network in the first cell. The first cell is a cell in a first TA of the firstaccess network device.
[00694] The first message includes a registration request, the registrationrequest includes information (for example, requested NSSAI) about a networkslice that the terminal requests to access, and the information about the networkslice that the terminal requests to access includes identification information of afirst network slice. That is to say, the first network slice is included in a networkslice that the terminal requests to access in the first cell. Further, the informationabout the network slice that the terminal requests to access may further includeidentification information of the second network slice.
[00695] In some embodiments, the first access network device may be anaccess network device in a first network. For the first network, refer to theforegoing related description. Details are not described herein again.
[00696] S2702: The first access network device sends a registration request to amobility management device. Correspondingly, the mobility management devicereceives the registration request from the first access network device.
[00697] The registration request is received by the first access network devicefrom the terminal in step S2701. Therefore, step S2701 and step S2702 may beunderstood as that the mobility management device receives, via the first cell, theinformation about the network slice that the terminal requests to access.
[00698] S2703: The mobility management device performs slice selection.
[00699] For example, the mobility management device may perform sliceselection by interacting with a network slice selection function network element.
[00700] In step S2703, the mobility management device may determine thefirst network slice, and the first network slice does not belong to the network slicethat the terminal is allowed to access in the first cell. Therefore, S2701 to S2703may be understood as specific implementation of determining the first networkslice by the mobility management device.
[00701] In step S2703, the mobility management device further determines aregistration area of the terminal. In this application, a description is made throughan example in which the registration area of the terminal includes the first cell andthe second cell. The second cell is a neighboring cell of the first cell, and maybelong to the first access network device, that is, the first cell and the second cellbelong to a same access network device; or may belong to the second accessnetwork device, that is, the first cell and the second cell belong to different accessnetwork devices.
[00702] S2704: The mobility management device stores identificationinformation of a target network slice, where the target network slice includes afirst network slice.
[00703] For example, in this application, a description is made through anexample in which the stored target network slice includes the first network sliceand the third network slice. To be specific, the terminal requests to access the firstnetwork slice, the second network slice, and the third network slice in the first cell,a network slice that the terminal is allowed to access in the first cell is the secondnetwork slice, and a network slice that the terminal is rejected to access includesthe first network slice and the third network slice.
[00704] In some embodiments, the mobility management device serving theterminal may send, when being subsequently handed over, the identificationinformation of the target network slice to a mobility management device to whichthe handover is made. When the mobility management device serving the terminalis handed over, the mobility management network element after step S2704 maybe considered as the mobility management network element to which thehandover is made.
[00705] S2705: The mobility management network element sends a secondmessage to the first access network device. Correspondingly, the first accessnetwork device receives the second message from the mobility managementnetwork element.
[00706] The second message includes information about the network slice thatthe terminal is allowed to access.
[00707] In some embodiments, the second message may be an N2 message.
[00708] It should be noted that step S2705 and step S2704 are not performed ina necessary sequence. Step S2704 may be performed first, and then step S2705 isperformed. Alternatively, step S2705 may be performed first, and then step S2704is performed. Alternatively, step S2704 and step S2705 may be simultaneouslyperformed. This is not specifically limited in this application.
[00709] S2706: The first access network device sends, to the terminal,information about a network slice that the terminal is allowed to access.Correspondingly, the terminal receives, from the first access network device, theinformation about the network slice that the terminal is allowed to access.
[00710] S2707: Another registration procedure.
[00711] After step S2007, the registration procedure is completed, and theterminal accesses the second network slice.
[00712] S2708: The mobility management device determines that the firstnetwork slice is available in the second cell.
[00713] In different embodiments of this application, methods for determining,by the mobility management device, that the first network slice is available in thesecond cell may be different. For example, in some embodiments, that themobility management device determines that the first network slice is available inthe second cell may include:
[00714] S27081a: The first access network device sends a cell identifier of thesecond cell to the mobility management device. Correspondingly, the mobilitymanagement device receives the cell identifier of the second cell from the firstaccess network device.
[00715] In a possible implementation, because the second cell is a neighboringcell 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. Themeasurement report may include an identifier of the neighboring cell of the firstcell and quality of the neighboring cell. After receiving the measurement reportfrom the terminal, the first access network device may perform step S27081awhen the measurement report includes the cell identifier of the second cell.
[00716] In an example, the first access network device may determine, throughthe following method, the cell identifier of the second cell that is reported to themobility management device:
[00717] Before step S27081a, the mobility management device may send, tothe first access network device, reference frequency information corresponding tothe first network slice. After receiving the measurement report reported by theterminal, the first access network device may determine the second cell based onthe reference frequency information, and therefore report the cell identifier of thesecond cell to the mobility management device. For example, the second cell is acell on a frequency indicated by the reference frequency information. When aplurality of cells exist on the frequency indicated by the reference frequencyinformation, the second cell may be a cell whose signal quality is greater than asecond threshold in the plurality of cells.
[00718] In addition, after receiving the reference frequency informationcorresponding to the first network slice, the first access network device mayconfigure the frequency indicated by the reference frequency information as ameasurement object and send the measurement object to the terminal, so that theterminal can measure the frequency.
[00719] S27082a: The mobility management device determines a network slicesupported by a second TA.
[00720] The second TA is a TA in which the second cell is located.
[00721] In a possible implementation, the mobility management device maydetermine the network slice supported by the second TA through informationabout the network slice that is reported by the first access network device whenestablishing or updating an N2 connection.
[00722] S27083a: When the network slice supported by the second TA includesthe first network slice, the mobility management device determines that theterminal can access the first network slice in the second cell.
[00723] In some embodiments, that the mobility management devicedetermines that the first network slice is available in the second cell may include:
[00724] S27081b: The first access network device sends signal qualityinformation of the neighboring cell of the first cell to the mobility managementdevice. Correspondingly, the mobility management device receives the signalquality information of the neighboring cell of the first cell from the first accessnetwork device.
[00725] The neighboring cell of the first cell includes the second cell, that is,the signal quality information of the neighboring cell includes signal qualityinformation of the second cell.
[00726] In a possible implementation, the first access network device sends, tothe mobility management device, signal quality information that is of allneighboring cells of the first cell and that is reported by the terminal.
[00727] In another possible implementation, the signal quality information thatis of the neighboring cell of the first cell and that is sent by the first accessnetwork device to the mobility management device may be signal quality of thecell on the frequency indicated by the reference frequency informationcorresponding to the first network slice. The reference frequency informationcorresponding to the first network slice may be sent by the mobility managementdevice to the first access network device before step S27081b.
[00728] S27082b: The mobility management device determines, based on thesignal quality information of the second cell, that the terminal can access the firstnetwork slice in the second cell.
[00729] In a possible implementation, the mobility management device mayfirst determine whether the second TA in which the second cell is located supportsthe first network slice; and further determine, when the second TA supports thefirst network slice, whether the cell signal quality indicated by the signal qualityinformation of the second cell is greater than the second threshold, and determine,when the cell signal quality of the second cell is greater than the second threshold,that the terminal can access the first network slice in the second cell.
[00730] Regardless of the manner of steps S27081a to S27083a or the mannerof steps S27082a and S27082b, the mobility management device may determinethat the first network slice is available in the second cell before the handoverprocedure occurs.
[00731] It may be understood that the mobility management device may alsodetermine whether the third network slice is available in the second cell. Anexample in which the third network slice is unavailable in the second cell is usedfor description in this application.
[00732] S2709: The network device notifies the terminal that the first networkslice is available in the second cell.
[00733] For a notification manner, refer to the manner in which the first accessnetwork device notifies the terminal that the first network slice is available in thesecond cell in step S2012. Details are not described herein again.
[00734] S2710: The mobility management device sends the cell identifier ofthe second cell to the terminal. Correspondingly, the terminal receives the cellidentifier of the second cell from the mobility management device.
[00735] In some embodiments, the cell identifier of the second cell may beused to hand over the terminal from the first cell to the second cell, so as to accessthe first network slice in the second cell.
[00736] In some embodiments, the cell identifier of the second cell andinformation for notifying the terminal that the first network slice is available inthe second cell may be carried in one message; or may be carried in differentmessages. This is not specifically limited in this application.
[00737] Optionally, after step S2710, the network slice-based communicationmethod may further include steps S2711 and S2712. Steps S2711 and S2712 arethe same as steps S2013 and S2014. For details, refer to related descriptions ofsteps S2013 and S2014. Details are not described herein again.
[00738] Based on the solution of this application, when determining that thefirst network slice is available in the second cell, the mobility management devicenotifies the terminal that the first network slice is available in the second cell, andsends the cell identifier of the second cell, so that when still intending to accessthe first network slice, the terminal may access the second cell, and initiate aregistration procedure to request to access the first network slice, therebyimproving a success rate of accessing the first network slice, and using a serviceprovided by the first network slice.
[00739] FIG. 28 is a schematic flowchart of a method for applying the methodin FIG. 17 to a specific procedure when a network device is a mobilitymanagement device according to this application. The method includes thefollowing steps:
[00740] S2801 to S2807: They are the same as steps S2701 to S2707 shown inFIG. 27. For details, refer to the related descriptions of steps S2701 to S2707.Details are not described herein again.
[00741] S2808: The mobility management device determines that the firstnetwork slice is available in the third cell.
[00742] Physical coverage of the third cell completely or partially overlapsphysical coverage of the second cell.
[00743] In some embodiments, the third cell may be referred to as a cell whosephysical coverage is the same as that of the second cell.
[00744] For a method for determining, by the mobility management device,that the first network slice is available in the third cell, refer to the method fordetermining, by the mobility management device, that the first network slice isavailable in the second cell in step S2708. Details are not described herein again.
[00745] It may be understood that when the first network slice is available inthe third cell, cells on the frequency indicated by the reference frequencyinformation corresponding to the first network slice include the third cell, but donot include the second cell.
[00746] S2809: The network device notifies the terminal that the first networkslice is available in the third cell.
[00747] For a notification manner, refer to the manner in which the first accessnetwork device notifies the terminal that the first network slice is available in thesecond cell in step S2012. Details are not described herein again.
[00748] S2810: The mobility management device sends the cell identifier ofthe third cell to the terminal. Correspondingly, the terminal receives the cellidentifier of the third cell from the mobility management device.
[00749] In some embodiments, the cell identifier of the third cell may be usedto hand over the terminal from the second cell to the third cell, so as to access thefirst network slice in the third cell.
[00750] Optionally, after step S2810, the network slice-based communicationmethod may further include steps S2811 and S2812. Steps S2811 and S2812 arethe same as steps S2013 and S2014. For details, refer to related descriptions ofsteps S2013 and S2014. Details are not described herein again.
[00751] Based on this solution, when the neighboring cell of the first cellaccessed by the terminal includes the second cell, the third cell whose physicalcoverage is the same as that of the second cell exists, and the mobilitymanagement device determines that the first network slice is available in the thirdcell, 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, so that when still intending to accessthe first network slice, the terminal may access the third cell and request to accessthe first network slice.
[00752] The foregoing describes application of the method implemented by thenetwork device in a specific procedure. The following describes in detail themethod implemented by the terminal shown in FIG. 18. The method may beapplied to the foregoing process in which the network device notifies the terminalthat the first network slice is available in the second cell. In other words, themethod may be considered as implementation of the terminal after the networkdevice notifies the terminal that the first network slice is available in the secondcell in FIG. 20 to FIG. 23 or FIG. 27.
[00753] FIG. 29 and FIG. 30 shows a network slice-based communicationmethod for a terminal according to this application. The method includes:
[00754] S2901: The terminal learns, from a network device, that a first networkslice is available in a second cell.
[00755] The first network slice does not belong to a network slice that theterminal is allowed to access in a first cell, and a registration area of the terminalincludes the first cell and the second cell. For details, refer to the foregoing relateddescriptions. Details are not described herein again.
[00756] In some embodiments, refer to FIG. 30. Step S2901 may be: A firstentity of the terminal learns, from a network device, that a first network slice isavailable in a second cell.
[00757] In an example, the first entity may be a hardware structure of theterminal.
[00758] S2902: The terminal stores identification information of the firstnetwork slice.
[00759] In some embodiments, refer to FIG. 30. Step S2902 may be: The firstentity of the terminal stores identification information of the first network slice.
[00760] S2903: An application of the terminal initiates a data transmissionrequest.
[00761] In some embodiments, refer to FIG. 30. Step S2903 may be: Theapplication of the terminal initiates a data transmission request to the first entity ofthe terminal.
[00762] S2904: The terminal queries a context of the terminal.
[00763] The context of the terminal includes a URSP and information about asession available to the terminal. When the context of the terminal does notinclude the URSP used for the application and does not include the session usedfor the application, it indicates that a network slice corresponding to the datatransmission request does not belong to the network slice that the terminal isallowed to access in the first cell, and therefore step S2905 is performed.
[00764] In some embodiments, refer to FIG. 30. Step S2904 may be: The firstentity of the terminal interacts with a second entity of the terminal to completequery of the context of the terminal.
[00765] In an example, the second entity may be a component that is includedin the terminal and that is configured to store the context of the terminal.
[00766] S2905: The terminal determines whether the first network slice is anetwork slice corresponding to the application.
[00767] In other words, the terminal determines whether the first network sliceis the network slice corresponding to the application in response to that thecontext of the terminal does not include the session used for the application anddoes not include the URSP used for the application.
[00768] When the first network slice is the network slice corresponding to theapplication, the application is an application corresponding to the first networkslice, and the terminal further performs step S2906a.
[00769] Alternatively, when the first network slice is not the network slicecorresponding to the application, step S2906b is performed.
[00770] In some embodiments, refer to FIG. 30. Step S2905 may be: The firstentity of the terminal determines whether the first network slice is a network slicecorresponding to the application.
[00771] S2906a: The terminal initiates a registration procedure for anapplication corresponding to the first network slice.
[00772] In some embodiments, refer to FIG. 30. Step S2906a may be: The firstentity of the terminal initiates a registration procedure for an applicationcorresponding to the first network slice.
[00773] In some embodiments, for example, when implementation of theterminal shown in FIG. 29 is applied to the scenario shown in FIG. 27, theterminal further receives a cell identifier from the network device, where the cellidentifier is used for the second cell. In other words, the terminal further receivesthe cell identifier of the second cell from the network device.
[00774] In this scenario, that the terminal initiates the registration procedure forthe application corresponding to the first network slice may include: The terminalaccesses the second cell, and initiates a registration procedure for the applicationvia the second cell.
[00775] In some embodiments, the terminal requests to access the first networkslice in the registration procedure initiated for the application.
[00776] S2906b: The terminal rejects the data transmission request initiated bythe application.
[00777] In some embodiments, refer to FIG. 30. Step S2906b may be: The firstentity of the terminal rejects the data transmission request initiated by theapplication.
[00778] Optionally, the network slice-based communication method providedin this application further includes step S2907:
[00779] S2907: The terminal notifies the network device that the terminal nolonger requests to access the first network slice. Correspondingly, the networkdevice learns, from the terminal, that the terminal no longer requests to access thefirst network slice.
[00780] In some embodiments, refer to FIG. 30. Step S2907 may be: The firstentity of the terminal notifies the network device that the terminal no longerrequests to access the first network slice.
[00781] In some embodiments, the terminal may send indication information tothe network device, where the indication information indicates that the terminalno longer requests to access the first network slice.
[00782] In some embodiments, after receiving the indication information, thenetwork device may delete, based on the indication information, the identificationinformation of the first network slice stored in the network device. For details,refer to the foregoing related descriptions. Details are not described herein again.
[00783] In some embodiments, after first duration starting from a first moment,the terminal notifies the network device that the terminal no longer requests toaccess the first network slice, where the first moment is a moment at which theterminal learns, from the network device, that the first network slice is available inthe second cell. In other words, if the application of the terminal does not requestto use the first network slice available in the second cell over a period of time, theterminal may notify the network device that the terminal no longer requests toaccess the first network slice.
[00784] Optionally, in some embodiments, when the terminal is handed overafter learning, from the network device, that the first network slice is available inthe second cell, and does not learn a new available network slice from the networkdevice after the handover, the terminal may delete the identification informationof the first network slice stored in the terminal.
[00785] Based on this solution, the terminal may learn, from the networkdevice, that the first network slice is available in the second cell, and thereforemay initiate, when an application of the terminal corresponds to the first networkslice, a registration procedure for the application to request to access the firstnetwork slice, thereby improving a success rate of accessing the first networkslice.
[00786] It may be understood that when the terminal learns, from the networkdevice, that the first network slice is available in the third cell, implementation ofthe terminal is similar to that of the method shown in FIG. 29 or FIG. 30, and thesecond cell may be replaced with the third cell for understanding. For details,refer to the foregoing related description. Details are not described herein again.
[00787] In embodiments of this application, unless otherwise stated or there isa logic conflict, terms and / or descriptions in different embodiments are consistentand may be mutually referenced, and technical features in different embodimentsmay be combined based on an internal logical relationship thereof, to form a newembodiment.
[00788] It may be understood that in the foregoing embodiments, methodand / or a step implemented by each device may alternatively be implemented by acomponent (for example, a chip or a circuit) that can be used for the device.
[00789] The foregoing mainly describes the solutions provided in thisapplication from the perspective of interaction between devices. Correspondingly,this application further provides a communication apparatus, and thecommunication apparatus is configured to implement the foregoing methods. Thecommunication apparatus may be the network device in the foregoing methodembodiments, an apparatus including the foregoing network device, or acomponent that can be used for the network device. Alternatively, thecommunication apparatus may be the terminal in the foregoing methodembodiments, an apparatus including the foregoing terminal, or a component thatcan be used for the terminal.
[00790] It may be understood that to implement the foregoing functions, thecommunication apparatus includes a hardware structure and / or a software modulefor performing a corresponding function. A person skilled in the art should beeasily aware that, based on the units and the algorithm steps in the examplesdescribed in embodiments disclosed in this specification, this application can beimplemented through hardware or a combination of hardware and computersoftware. Whether a function is performed by hardware or hardware driven bycomputer software depends on particular applications and design constraints ofthe technical solutions. A person skilled in the art may use different methods toimplement the described functions for each particular application, but it shouldnot be considered that the implementation goes beyond the scope of thisapplication.
[00791] In embodiments of this application, the communication apparatus maybe divided into functional modules based on the foregoing method embodiments.For example, each functional module may be obtained through division based oneach corresponding function, or two or more functions may be integrated into oneprocessing module. The integrated module may be implemented in a form ofhardware, or may be implemented in a form of a software function module. Itshould be noted that the module division in embodiments of this application is anexample, and is merely logical function division. There may be another divisionmanner in an actual implementation.
[00792] For example, the communication apparatus is the network device in theforegoing method embodiments. FIG. 31 is a schematic diagram of a structure of anetwork device 310. The network device 310 includes a processing module 3101and a transceiver module 3102.
[00793] In some embodiments, the network device 310 may further include astorage module (not shown in FIG. 31), configured to store program instructionsand data.
[00794] In some embodiments, the transceiver module 3102 may also bereferred to as a transceiver unit, and is configured to implement a sending functionand / or a receiving function. The transceiver module 3102 may include atransceiver circuit, a transceiver machine, a transceiver, or a communicationinterface.
[00795] In some embodiments, the transceiver module 3102 may include areceiving module and a sending module, respectively configured to performreceiving-type steps and sending-type steps performed by the network device inthe foregoing method embodiments, and / or configured to support another processof the technology described in this specification; and the processing module 3101may be configured to perform processing-type (for example, determining andobtaining) steps performed by the network device in the foregoing methodembodiments, and / or configured to support another process of the technologydescribed in this specification.
[00796] In some implementation scenarios, the transceiver module 3102 isconfigured to receive, via a first access network device in a first network,information about a network slice that a terminal requests to access, where theinformation about the network slice that the terminal requests to access includesidentification information of a first network slice not supported by a first trackingarea and includes identification information of a second network slice, the firsttracking area is a tracking area of the first access network device, and a secondtracking area in the first network supports the first network slice; the processingmodule 3101 is configured to determine a network slice that the terminal isallowed to access, where the network slice that the terminal is allowed to accessincludes the second network slice; the processing module 3101 is furtherconfigured to determine a registration area, where the registration area excludes atracking area that supports the first network slice and the second network slice, orthe registration area excludes a tracking area of an access network device thatsupports the first network slice and the second network slice; and the transceivermodule 3102 is further configured to send information about the registration areato the terminal.
[00797] In a possible implementation, the processing module 3101 is furtherconfigured to determine a network slice that the terminal is rejected to access,where the network slice that the terminal is rejected to access includes the firstnetwork slice.
[00798] In a possible implementation, the processing module 3101 is furtherconfigured to determine a network slice supported by the tracking area of the firstaccess network device.
[00799] In some implementation scenarios, the processing module 3101 isconfigured to determine a network slice that a terminal is allowed to access and anetwork slice that the terminal is rejected to access; the processing module 3101 isfurther configured to determine a registration area of the terminal based on thenetwork slice that the terminal is allowed to access and the network slice that theterminal is rejected to access; and the transceiver module 3102 is configured tosend information about the registration area to the terminal.
[00800] In a possible implementation, the transceiver module 3102 is furtherconfigured to receive, via a first access network device in a first network,information about a network slice that the terminal requests to access, where theinformation about the network slice that the terminal requests to access includesidentification information of a first network slice not supported by a first trackingarea and includes identification information of a second network slice supportedby the first tracking area, and the first tracking area is a tracking area of the firstaccess network device. The network slice that the terminal is allowed to accessincludes the second network slice, and the network slice that the terminal isrejected to access includes the first network slice; and the registration areaexcludes a tracking area that supports the first network slice and the secondnetwork slice, or the registration area excludes a tracking area of an accessnetwork device that supports the first network slice and the second network slice.
[00801] In a possible implementation, the processing module 3101 is furtherconfigured to determine a network slice supported by the tracking area of the firstaccess network device.
[00802] In some implementation scenarios, the processing module 3101 isconfigured to determine a first network slice, where the first network slice doesnot belong to a network slice that the terminal is allowed to access in a first cell,and a registration area of the terminal includes the first cell and a second cell; theprocessing module 3101 is further configured to determine, when the terminal ishanded over from the first cell to the second cell, that the first network slice isavailable in the second cell; and the transceiver module 3102 is further configuredto notify the terminal that the first network slice is available in the second cell.
[00803] In a possible implementation, that the processing module 3101 isconfigured to determine the first network slice includes: The processing module3101 is configured to control the transceiver module 3102 to receive, via the firstcell, information about a network slice that the terminal requests to access, wherethe information about the network slice that the terminal requests to accessincludes identification information of the first network slice; the processingmodule 3101 is further configured to determine a network slice that the terminal isallowed to access; and the processing module 3101 is further configured to learnthat the first network slice does not belong to the network slice that the terminal isallowed to access in the first cell.
[00804] In a possible implementation, that the processing module 3101 isconfigured to determine that the first network slice is available in the second cellincludes: The processing module 3101 is configured to query a context of thetarget access network device, where the context of the target access networkdevice indicates that a tracking area of the target access network device supportsthe first network slice, where the second cell is a cell in the tracking area of thetarget access network device.
[00805] In a possible implementation, that the processing module 3101 isconfigured to determine that the first network slice is available in the second cellincludes: The processing module 3101 is configured to control the transceivermodule 3102 to send identification information of the first network slice to thetarget access network device; and the processing module 3101 is furtherconfigured to learn, from the target access network device, that the terminal canaccess the first network slice in the second cell.
[00806] In a possible implementation, that the processing module 3101 isconfigured to determine that the first network slice is available in the second cellincludes: The processing module 3101 is configured to determine, when thetransceiver module 3102 receives a path switch request message from the secondaccess network device, that the first network slice is available in the second cell;or the processing module 3101 is configured to determine, when the transceivermodule 3102 receives a handover required message from the first access networkdevice, that the first network slice is available in the second cell, where thehandover required message includes an identifier of the second access networkdevice.
[00807] In a possible implementation, the processing module 3101 is furtherconfigured to store identification information of the first network slice; thetransceiver module 3102 is further configured to receive indication informationfrom the terminal; and the processing module 3101 is further configured to deletethe identification information of the first network slice based on the indicationinformation.
[00808] In a possible implementation, that the processing module 3101 isconfigured to determine the first network slice includes: The processing module3101 is configured to control the transceiver module 3102 to send, to a mobilitymanagement device, information about a network slice that the terminal requeststo access, where the information about the network slice that the terminal requeststo access includes identification information of the first network slice; and theprocessing module 3101 is further configured to learn, from the mobilitymanagement device, that the first network slice does not belong to a network slicethat the terminal is allowed to access in the first cell.
[00809] In a possible implementation, that the processing module 3101 isconfigured to determine the first network slice includes: When the terminal ishanded over from the first access network device to the second access networkdevice, the processing module 3101 is configured to learn, from the mobilitymanagement device, that the first network slice does not belong to the networkslice that the terminal is allowed to access in the first cell.
[00810] In a possible implementation, that the processing module 3101 isconfigured to determine that the first network slice is available in the second cellincludes: The processing module 3101 is configured to determine that the terminalcan access the first network slice in the second cell.
[00811] In some implementation scenarios, the processing module 3101 isconfigured to determine a first network slice, where the first network slice doesnot belong to a network slice that the terminal is allowed to access in a first cell,and a registration area of the terminal includes the first cell and a second cell; theprocessing module 3101 is further configured to determine, when the terminal ishanded over from the first cell to the second cell, that the first network slice isavailable in the third cell, where physical coverage of the third cell partially orcompletely overlaps physical coverage of the second cell; and the transceivermodule 3102 is further configured to notify the terminal that the first networkslice is available in the third cell.
[00812] In some implementation scenarios, the processing module 3101 isconfigured to determine a first network slice, where the first network slice doesnot belong to a network slice that the terminal is allowed to access in a first cell,and a registration area of the terminal includes the first cell and a second cell; theprocessing module 3101 is further configured to determine that the first networkslice is available in the second cell; the transceiver module 3102 is configured tonotify the terminal that the first network slice is available in the second cell; andthe transceiver module 3102 is further configured to send a cell identifier of thesecond cell to the terminal.
[00813] In a possible implementation, that the processing module 3101 isconfigured to determine the first network slice includes: The processing module3101 is configured to control the transceiver module 3102 to receive, via the firstcell, information about a network slice that the terminal requests to access, wherethe information about the network slice that the terminal requests to accessincludes identification information of the first network slice; the processingmodule 3101 is further configured to determine a network slice that the terminal isallowed to access; and the processing module 3101 is further configured to learnthat the first network slice does not belong to the network slice that the terminal isallowed to access in the first cell.
[00814] In a possible implementation, that the processing module 3101 isconfigured to determine that the first network slice is available in the second cellincludes: The processing module 3101 is configured to control the transceivermodule 3102 to receive the cell identifier of the second cell from a first accessnetwork device, where the second cell is a neighboring cell of the first cell, andthe network device determines that the terminal can access the first network slicein the second cell.
[00815] In a possible implementation, that the processing module 3101 isconfigured to determine that the first network slice is available in the second cellincludes: The processing module 3101 is configured to control the transceivermodule 3102 to receive signal quality information of a neighboring cell of the firstcell from a first access network device, where the neighboring cell of the first cellincludes the second cell; and the processing module 3101 is further configured todetermine, based on the signal quality information of the second cell, that theterminal can access the first network slice in the second cell.
[00816] In a possible implementation, the transceiver module 3102 is furtherconfigured to send reference frequency information corresponding to the firstnetwork slice to the first access network device.
[00817] In a possible implementation, the processing module 3101 is furtherconfigured to store identification information of the first network slice; thetransceiver module 3102 is further configured to receive indication informationfrom the terminal; and the processing module 3101 is further configured to deletethe identification information of the first network slice based on the indicationinformation.
[00818] In some implementation scenarios, the processing module 3101 isconfigured to determine a first network slice, where the first network slice doesnot belong to a network slice that the terminal is allowed to access in a first cell,and a registration area of the terminal includes the first cell and a second cell; theprocessing module 3101 is further configured to determine that the first networkslice is available in the third cell, where physical coverage of the third cellpartially or completely overlaps physical coverage of the second cell; thetransceiver module 3102 is configured to notify the terminal that the first networkslice is available in the third cell; and the transceiver module 3102 is furtherconfigured to send a cell identifier of the third cell to the terminal.
[00819] All related content of the steps in the foregoing method embodimentsmay be cited in function descriptions of a corresponding functional module.Details are not described herein again.
[00820] In this application, the network device 310 is presented in a form ofdividing functional modules in an integrated manner. The "module" herein may bean application-specific integrated circuit (ASIC), a circuit, a processor and amemory that execute one or more software or firmware programs, an integratedlogic circuit, and / or another device that can provide the foregoing functions.
[00821] In some embodiments, in terms of hardware implementation, a personskilled in the art may figure out that the network device 310 may be in a form ofthe communication device 1000 shown in FIG. 10.
[00822] In an example, a function / implementation process of the processingmodule 3101 in FIG. 31 may be implemented by the processor 1001 in thecommunication device 1000 shown in FIG. 10 by invoking the computerexecutableinstructions stored in the memory 1003. A function / implementationprocess of the transceiver module 3102 in FIG. 31 may be implemented via thecommunication interface 1004 in the communication device 1000 shown in FIG.10.
[00823] In some embodiments, when the network device 310 in FIG. 31 is achip or a chip system, a function / implementation process of the transceivermodule 3102 may be implemented via an input / output interface (or acommunication interface) of the chip or the chip system, and afunction / implementation process of the processing module 3101 may beimplemented through a processor (or a processing circuit) of the chip or the chipsystem.
[00824] The network device 310 provided in this embodiment may perform theforegoing network slice-based communication method. Therefore, for technicaleffects that can be achieved by the network device, refer to the foregoing methodembodiments. Details are not described herein again.
[00825] For example, the communication apparatus is the terminal in theforegoing method embodiments. FIG. 32 is a schematic diagram of a structure of aterminal 320. The terminal 320 includes a processing module 3201 and atransceiver module 3202.
[00826] In some embodiments, the terminal 320 may further include a storagemodule (not shown in FIG. 32), configured to store program instructions and data.
[00827] In some embodiments, the transceiver module 3202 may also bereferred to as a transceiver unit, and is configured to implement a sending functionand / or a receiving function. The transceiver module 3202 may include atransceiver circuit, a transceiver machine, a transceiver, or a communicationinterface.
[00828] In some embodiments, the transceiver module 3202 may include areceiving module and a sending module, respectively configured to performreceiving-type steps and sending-type steps performed by the terminal in theforegoing method embodiments, and / or configured to support another process ofthe technology described in this specification; and the processing module 3201may be configured to perform processing-type (for example, determining andobtaining) steps performed by the terminal in the foregoing method embodiments,and / or configured to support another process of the technology described in thisspecification.
[00829] Specifically, the transceiver module 3202 is configured to learn, from anetwork device, that a first network slice is available in a second cell, where thefirst network slice does not belong to a network slice that the terminal is allowedto access in a first cell, and a registration area of the terminal includes the first celland the second cell; and the processing module 3201 is configured to initiate aregistration procedure for an application corresponding to the first network slice.
[00830] In a possible implementation, the transceiver module 3202 is furtherconfigured to receive a cell identifier from the network device, where the cellidentifier is used for the second cell.
[00831] In a possible implementation, that the processing module 3201 isconfigured to initiate the registration procedure for the application correspondingto the first network slice includes: The processing module 3201 is configured toaccess a second cell; and the processing module 3201 is further configured toinitiate the registration procedure for the application via the second cell.
[00832] In a possible implementation, that the processing module 3201 isconfigured to initiate the registration procedure for the application correspondingto the first network slice includes: In response to that a context of the terminaldoes not include a session used for the application and does not include a routeselection policy used for the application, in a possible implementation, theprocessing module 3201 is configured to determine whether the first network sliceis a network slice corresponding to the application; and the processing module3201 is configured to initiate the registration procedure for the application whenthe first network slice is the network slice corresponding to the application.
[00833] In a possible implementation, the transceiver module 3202 is furtherconfigured to notify the network device that the terminal no longer requests toaccess the first network slice.
[00834] All related content of the steps in the foregoing method embodimentsmay be cited in function descriptions of a corresponding functional module.Details are not described herein again.
[00835] In this application, the terminal 320 is presented in a form of dividingfunctional modules in an integrated manner. The "module" herein may be anapplication-specific integrated circuit (ASIC), a circuit, a processor and a memorythat execute one or more software or firmware programs, an integrated logiccircuit, and / or another device that can provide the foregoing functions.
[00836] In some embodiments, in terms of hardware implementation, a personskilled in the art may figure out that the terminal 320 may be in a form of thecommunication device 1000 shown in FIG. 10.
[00837] In an example, a function / implementation process of the processingmodule 3201 in FIG. 32 may be implemented by the processor 1001 in thecommunication device 1000 shown in FIG. 10 by invoking the computerexecutableinstructions stored in the memory 1003. A function / implementationprocess of the transceiver module 3202 in FIG. 32 may be implemented via thecommunication interface 1004 in the communication device 1000 shown in FIG.10.
[00838] In some embodiments, when the terminal 320 in FIG. 32 is a chip or achip system, a function / implementation process of the transceiver module 3202may be implemented through an input / output interface (or a communicationinterface) of the chip or the chip system, and a function / implementation process ofthe processing module 3201 may be implemented through a processor (or aprocessing circuit) of the chip or the chip system.
[00839] The terminal 320 provided in this embodiment may perform theforegoing network slice-based communication method. Therefore, for technicaleffects that can be achieved by the terminal, refer to the foregoing methodembodiments. Details are not described herein again.
[00840] In a possible product form, the network device and the terminal inembodiments of this application may be further implemented through thefollowing: one or more field programmable gate arrays (FPGAs), programmablelogic devices (PLDs), controllers, state machines, gate logic, discrete hardwarecomponents, any other suitable circuitry, or any combination of circuits capable ofperforming various functions described throughout this application.
[00841] In some embodiments, an embodiment of this application furtherprovides a communication apparatus. The communication apparatus includes aprocessor, configured to implement the method in any one of the foregoingmethod embodiments.
[00842] In a possible implementation, the communication apparatus furtherincludes a memory. The memory is configured to store necessary programinstructions and necessary data. The processor may invoke program code stored inthe memory, to indicate the communication apparatus to perform the method inany one of the foregoing method embodiments. Certainly, the communicationapparatus may not include a memory.
[00843] In another possible implementation, the communication apparatusfurther includes an interface circuit. The interface circuit is a code / data read / writeinterface circuit, and the interface circuit is configured to receive computerexecutableinstructions (where the computer-executable instructions are stored ina memory, and may be directly read from the memory, or may be read via anothercomponent) and send the computer-executable instructions to the processor.
[00844] In still another possible implementation, the communication apparatusfurther includes a communication interface, and the communication interface isconfigured to communicate with a module other than the communicationapparatus.
[00845] It may be understood that the communication apparatus may be a chipor a chip system. When the communication apparatus is a chip system, thecommunication apparatus may include a chip, or may include a chip and anotherdiscrete component. This is not specifically limited in embodiments of thisapplication.
[00846] In some embodiments, an embodiment of this application furtherprovides a communication apparatus (for example, the communication apparatusmay be a chip or a chip system). The communication apparatus includes aninterface circuit and a logic circuit. The interface circuit is configured to obtaininput information and / or output output information; and the logic circuit isconfigured to perform the method in any one of the foregoing methodembodiments, to perform processing based on input information and / or generateoutput information.
[00847] When the communication apparatus is configured to implement afunction of the network device in the foregoing method embodiments:
[00848] In some implementation scenarios, in a possible implementation, theinput information may be information about a network slice that the terminalrequests to access, where the information about the network slice that the terminalrequests to access includes identification information of a first network slice notsupported by a first tracking area and includes identification information of asecond network slice. The performing processing based on input information maybe: determining a network slice that the terminal is allowed to access, ordetermining a registration area.
[00849] In a possible implementation, the output information may beinformation about a registration area, where the registration area excludes atracking area that supports the first network slice and the second network slice, orthe registration area excludes a tracking area of an access network device thatsupports the first network slice and the second network slice.
[00850] In some implementation scenarios, in a possible implementation, theoutput information may be information for notifying the terminal that the firstnetwork slice is available in the second cell.
[00851] In a possible implementation, the input information may beinformation about a network slice that the terminal requests to access, where theinformation about the network slice that the terminal requests to access includesidentification information of the first network slice. The performing processingbased on input information may be: determining a network slice that the terminalis allowed to access, or determining that the first network slice does not belong toa network slice that the terminal is allowed to access in the first cell.
[00852] In a possible implementation, the output information may be:identification information of the first network slice.
[00853] In a possible implementation, the input information may beinformation used by the network device to learn that the terminal can access thefirst network slice in the second cell. The performing processing based on inputinformation may be: learning that the terminal can access the first network slice inthe second cell.
[00854] In a possible implementation, the input information may be: a pathswitch request message. The performing processing based on input informationmay be: determining that the first network slice is available in the second cell.
[00855] In a possible implementation, the input information may be: ahandover required message. The performing processing based on inputinformation may be: determining that the first network slice is available in thesecond cell.
[00856] In a possible implementation, the input information may be: indicationinformation. The performing processing based on input information may be:deleting the identification information of the first network slice based on theindication information.
[00857] In some implementation scenarios, in a possible implementation, theoutput information may be information for notifying the terminal that the firstnetwork slice is available in the second cell, and a cell identifier of the second cell.
[00858] In a possible implementation, the input information may beinformation about a network slice that the terminal requests to access, where theinformation that the terminal requests to access includes identification informationof the first network slice. The performing processing based on input informationmay be: determining a network slice that the terminal is allowed to access, andlearning that the first network slice does not belong to a network slice that theterminal is allowed to access in the first cell.
[00859] In a possible implementation, the input information may be: a cellidentifier of the second cell. The performing processing based on inputinformation may be: determining that the first network slice is available in thesecond cell.
[00860] In a possible implementation, the input information may be: signalquality information of a neighboring cell of the first cell, where the neighboringcell of the first cell includes the second cell. The performing processing based oninput information may be: determining, based on the signal quality information ofthe second cell, that the terminal can access the first network slice in the secondcell.
[00861] In a possible implementation, the output information may be: referencefrequency information corresponding to the first network slice.
[00862] In a possible implementation, the input information may be: indicationinformation. The performing processing based on input information may be:deleting the identification information of the first network slice based on theindication information.
[00863] When the communication apparatus is configured to implement afunction of the terminal in the foregoing method embodiments:
[00864] In a possible implementation, the input information may beinformation for learning that the first network slice is available in the second cell.The performing processing based on input information may be: initiating aregistration procedure for an application corresponding to the first network slice.
[00865] In a possible implementation, the input information may be: a cellidentifier, where the cell identifier is used for the second cell. The performingprocessing based on input information may be: accessing the second cell.
[00866] In a possible implementation, the output information may beinformation for notifying that the terminal no longer requests to access the firstnetwork slice.
[00867] The communication apparatus provided in this embodiment mayperform the method in the foregoing method embodiments. Therefore, fortechnical effects that can be achieved by the communication apparatus, refer to theforegoing method embodiments. Details are not described herein again.
[00868] In a possible product form, the network device and the terminal inembodiments of this application may be implemented through a general busarchitecture.
[00869] For ease of description, refer to FIG. 33. FIG. 33 is a schematicdiagram of a structure of a communication apparatus 3300 according to anembodiment of this application. The communication apparatus 3300 includes aprocessor 3301 and a transceiver 3302. The communication apparatus 3300 maybe a network device, a terminal, or a chip in a network device or a terminal. FIG.33 shows only main components of the communication apparatus 3300. Inaddition to the processor 3301 and the transceiver 3302, the communicationapparatus may further include a memory 3303 and an input / output apparatus (notshown in the figure).
[00870] The processor 3301 is mainly configured to: process a communicationprotocol and communication data, control the entire communication apparatus,execute a software program, and process data of the software program. Thememory 3303 is mainly configured to store the software program and data. Thetransceiver 3302 may include a radio frequency circuit and an antenna. The radiofrequency circuit is mainly configured to: perform conversion between a basebandsignal and a radio frequency signal, and process the radio frequency signal. Theantenna is mainly configured to receive and send a radio frequency signal in aform of an electromagnetic wave. The input / output apparatus is, for example, atouchscreen, a display, or a keyboard, and is mainly configured to: receive dataentered by a user and output data to the user.
[00871] The processor 3301, the transceiver 3302, and the memory 3303 maybe connected through a communication bus.
[00872] After the communication apparatus is powered on, the processor 3301may read the software program in the memory 3303, interpret and executeinstructions of the software program, and process the data of the software program.When data needs to be sent wirelessly, the processor 3301 performs basebandprocessing on the data to be sent, and then outputs a baseband signal to a radiofrequency circuit. The radio frequency circuit performs radio frequencyprocessing on the baseband signal, and then sends out a radio frequency signalthrough the antenna in a form of an electromagnetic wave. When data is sent tothe communication apparatus, the radio frequency circuit receives a radiofrequency signal through the antenna, converts the radio frequency signal into abaseband signal, and outputs the baseband signal to the processor 3301. Theprocessor 3301 converts the baseband signal into data, and processes the data.
[00873] In another implementation, the radio frequency circuit and the antennamay be disposed independent of the processor that performs baseband processing.For example, in a distributed scenario, the radio frequency circuit and the antennamay be disposed remotely and independent of the communication apparatus.
[00874] It should be understood that sequence numbers of the foregoingprocesses do not mean execution sequences in various embodiments of thisapplication. The execution sequences of the processes should be determined basedon functions and internal logic of the processes, and should not be construed asany limitation on the implementation processes of embodiments of thisapplication.
[00875] Steps in a method in embodiments of this application may be adjustedin terms of sequence, combined, or deleted based on an actual requirement.
[00876] Modules in an apparatus in embodiments of this application may becombined, divided, or deleted based on an actual requirement.
[00877] All or some of the foregoing embodiments may be implementedthrough software, hardware, firmware, or any combination thereof. When asoftware program is used to implement the embodiments, all or a part of theembodiments may be implemented in a form of a computer program product. Thecomputer program product includes one or more computer instructions. When thecomputer program instructions are loaded and executed on the computer, theprocesses or functions based on embodiments of this application are all orpartially generated. The computer may be a general-purpose computer, adedicated computer, a computer network, or other programmable apparatuses. Thecomputer instructions may be stored in a computer-readable storage medium ormay be transmitted from a computer-readable storage medium to anothercomputer-readable storage medium. For example, the computer instructions maybe transmitted from a website, computer, server, or data center to another website,computer, server, or data center in a wired (for example, a coaxial cable, anoptical fiber, or a digital subscriber line (DSL)) or wireless (for example, infrared,radio, or microwave) manner. The computer-readable storage medium may be anyusable medium accessible by the computer, or a data storage device, for example,a server or a data center, integrating one or more usable media. The usablemedium may be a magnetic medium (for example, a floppy disk, a hard disk, or amagnetic tape), an optical medium (for example, a DVD), a semiconductormedium (for example, a solid-state drive (SSD)), or the like. In embodiments ofthis application, the computer may include the apparatus described above.
[00878] Although this application is described with reference to embodiments,in a process of implementing this application that claims protection, a personskilled in the art may understand and implement another variation of the disclosedembodiments by viewing the accompanying drawings, disclosed content, andappended claims. In the claims, the term "comprising" does not exclude anothercomponent or another step, and "a" or "one" does not exclude a case of plurality.A single processor or another unit may implement several functions enumerated inthe claims. Some measures are recorded in dependent claims that are differentfrom each other, but this does not indicate that these measures cannot becombined to produce a better effect.
[00879] Although this application has been described with reference to specificfeatures and embodiments thereof, it is obvious that various modifications andcombinations may be made to this application without departing from the spiritand scope of this application. Correspondingly, the specification and theaccompanying drawings are merely example descriptions of this applicationdefined in the appended claims, and are considered as any of or all modifications,variations, combinations or equivalents that cover the scope of this application. Itis clear that a person skilled in the art can make various modifications andvariations to this application without departing from the spirit and scope of thisapplication. This application is intended to cover these modifications andvariations of this application provided that they fall within the scope of protectiondefined by the following claims and their equivalent technologies.
Claims
1. A network slice-based communication method, wherein the method comprises: determining, by a network device, a network slice that a terminal is allowed to access and a network slice that the terminal is rejected to access; determining, by the network device, 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 rejected to access; and sending, by the network device, information about the registration area to the terminal.
2. The method according to claim 1, wherein the network slice that the terminal is rejected to access comprises a first network slice, the network slice that the terminal is allowed to access comprises a second network slice, and the registration area excludes a tracking area that supports both the first network slice and the second network slice, or the registration area excludes a tracking area of an access network device that supports both the first network slice and the second network slice.
3. The method according to claim 2, wherein the first network slice is a network slice not supported by the current tracking area.
4. The method according to claim 1, wherein the method further comprises: receiving, by the network device via a first access network device in a first network, information about a network slice that the terminal requests to access, wherein the information about the network slice that the terminal requests to access comprises identification information of a first network slice not supported by a first tracking area and comprises identification information of a second network slice supported by the first tracking area, and the first tracking area is a tracking area of the first access network device; the network slice that the terminal is allowed to access comprises the second network slice, and the network slice that the terminal is rejected to access comprises the first network slice; and the registration area excludes a tracking area that supports the first network slice and the second network slice, or the registration area excludes a tracking area of an access network device that supports the first network slice and the second network slice.
5. The method according to claim 4, wherein the first network slice is a network slice that the terminal is allowed to access in the first network.
6. The method according to claim 4 or 5, wherein the method further comprises: determining, by the network device, a network slice supported by the tracking area of the first access network device.
7. A network slice-based communication method, wherein the method comprises: learning, by a terminal from a network device, that a first network slice is available in a second cell or a tracking area in which a second cell is located, wherein the first network slice does not belong to a network slice that the terminal is allowed to access in a tracking area in which a first cell is located, and a registration area of the terminal comprises the first cell and the second cell; and initiating, by the terminal, a registration procedure for an application corresponding to the first network slice.
8. The method according to claim 7, wherein the first network slice is comprised in a network slice configured for the terminal in a first network.
9. The method according to claim 7 or 8, wherein the first network slice is comprised in a network slice that the terminal requests to access in the first cell.
10. The method according to any one of claims 7 to 9, wherein the method further comprises: receiving, by the terminal, a cell identifier from the network device, wherein the cell identifier is used for the second cell.
11. The method according to claim 10, wherein the initiating, by the terminal, a registration procedure for an application corresponding to the first network slice comprises: accessing, by the terminal, the second cell; and initiating, by the terminal, the registration procedure for the application via the second cell.
12. The method according to any one of claims 7 to 11, wherein the initiating, by the terminal, a registration procedure for an application corresponding to the first network slice comprises: determining, by the terminal, whether the first network slice is a network slice corresponding to the application in response to that a context of the terminal does not comprise a session used for the application and does not comprise a route selection policy used for the application; and initiating, by the terminal, the registration procedure for the application when the first network slice is the network slice corresponding to the application.
13. The method according to any one of claims 7 to 12, wherein the method further comprises: notifying, by the terminal, the network device that the terminal no longer requests to access the first network slice.
14. A network slice-based communication method, comprising: determining, by a network device, a first network slice, wherein the first network slice does not belong to a network slice that a terminal is allowed to access in a tracking area in which a first cell is located, and a registration area of the terminal comprises the first cell and a second cell; determining, by the network device when the terminal is handed over from the first cell to the second cell, that the first network slice is available in the second cell or a tracking area in which the second cell is located; and notifying, by the network device, the terminal that the first network slice is available in the second cell or the tracking area in which the second cell is located.
15. The method according to claim 14, wherein the notifying, by the network device, the terminal that the first network slice is available in the second cell or the tracking area in which the second cell is located comprises: sending, by the network device, identification information of the first network slice to the terminal.
16. The method according to claim 15, wherein the notifying, by the network device, the terminal that the first network slice is available in the second cell or the tracking area in which the second cell is located further comprises: sending, by the network device, a cell identifier to the terminal, wherein the cell identifier is used for the second cell.
17. The method according to any one of claims 14 to 16, wherein the first network slice is comprised in a network slice configured for the terminal in a first network.
18. The method according to any one of claims 14 to 17, wherein the first network slice is comprised in a network slice that the terminal requests to access in the first cell.
19. The method according to any one of claims 14 to 18, wherein the first cell belongs to a first access network device, and the second cell belongs to a second access network device; or the first cell and the second cell belong to a first access network device.
20. The method according to claim 19, wherein the network device is a mobility management device.
21. The method according to claim 20, wherein the determining, by a network device, a first network slice comprises: receiving, by the network device via the first cell, information about a network slice that the terminal requests to access, wherein the information about the network slice that the terminal requests to access comprises identification information of the first network slice; determining, by the network device, a network slice that the terminal is allowed to access; and learning, by the network device, that the first network slice does not belong to the network slice that the terminal is allowed to access in the first cell.
22. The method according to claim 19 or 20, wherein when the second cell belongs to the second access network device, a target access network device is the second access network device; or when the second cell belongs to the first access network device, a target access network device is the first access network device.
23. The method according to claim 22, wherein the determining, by the network device, that the first network slice is available in the second cell or the tracking area in which the second cell is located comprises: querying, by the network device, a context of the target access network device, wherein the context of the target access network device indicates that a 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.
24. The method according to claim 22 or 23, wherein the determining, by the network device, that the first network slice is available in the second cell or the tracking area in which the second cell is located comprises: sending, by the network device, identification information of the first network slice to the target access network device; and learning, by the network device from the target access network device, that the first network slice can access the terminal in the second cell.
25. The method according to any one of claims 22 to 24, wherein when the second cell belongs to the second access network device, the determining, by the network device, that the first network slice is available in the second cell or the tracking area in which the second cell is located comprises: determining, by the network device when receiving a path switch request message from the second access network device, that the first network slice is available in the second cell; or determining, by the network device when receiving a handover required message from the first access network device, that the first network slice is available in the second cell, wherein the handover required message comprises an identifier of the second access network device.
26. The method according to any one of claims 20 to 25, wherein the method further comprises: storing, by the network device, the identification information of the first network slice; receiving, by the network device, indication information from the terminal after the network device notifies the terminal that the first network slice is available in the second cell; and deleting, by the network device, the identification information of the first network slice based on the indication information.
27. The method according to claim 26, wherein the indication information indicates that the terminal no longer requests to access the first network slice.
28. The method according to claim 19, wherein 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.
29. The method according to claim 28, wherein when the second cell belongs to the first access network device, the determining, by a network device, a first network slice comprises: sending, by the network device to a mobility management device, information about a network slice that the terminal requests to access, wherein the information about the network slice that the terminal requests to access comprises identification information of the first network slice; and learning, by the network device from the mobility management device, that the first network slice does not belong to a network slice that the terminal is allowed to access in the first cell.
30. A network slice-based communication method, wherein the method comprises: receiving information about a registration area of a terminal from a network device, wherein a network slice that the terminal is rejected to access comprises a first network slice, a network slice that the terminal is allowed to access comprises a second network slice, and the registration area excludes a tracking area that supports both the first network slice and the second network slice, or the registration area excludes a tracking area of an access network device that supports both the first network slice and the second network slice; and performing, when the terminal moves into an tracking area outside the registration area, a mobility registration update procedure to request to access the first network slice, wherein the excluded tracking area supports the first network slice.
31. A communication apparatus, comprising: a processor, wherein the processor is configured to read a program from a memory and run the program, to implement the method according to any one of claims 1 to 6 or implement the method according to any one of claims 14 to 29.
32. A communication apparatus, comprising: a processor, wherein the processor is configured to read a program from a memory and run the program, to implement the method according to any one of claims 7 to 13 or implement the method according to claim 30.
33. A computer program product comprising instructions, wherein when the instructions are run on a computer, the computer is enabled to perform the method according to any one of claims 1 to 30.
34. A computer-readable storage medium, wherein the computer-readable storage medium stores instructions, and when the instructions are run on a computer, a processor is enabled to perform the method according to any one of claims 1 to 30.
35. A computer program, wherein when the computer program runs on a communication apparatus, the method according to any one of claims 1 to 30 is performed.
36. A communication apparatus, wherein the communication apparatus comprises: a logic circuit and an interface circuit; the interface circuit is configured to obtain input information and / or output output information; and the logic circuit is configured to perform the method according to any one of claims 1 to 6 or configured to perform the method according to any one of claims 14 to 29, to process the information input through the interface circuit and / or generate the information output through the interface circuit.
37. A communication apparatus, wherein the communication apparatus comprises: a logic circuit and an interface circuit; the interface circuit is configured to obtain input information and / or output output information; and the logic circuit is configured to perform the method according to any one of claims 7 to 13, to process the information input through the interface circuit and / or generate the information output through the interface circuit, or configured to perform the method according to claim 30.
